I tried to install lineage OS 17.1 on a Moto-Z with Android 6.0.1, and failed.
Here is one error I'd like to solve - this command:
fastboot flash recovery twrp-3.3.1-0-griffin.img
Results in:
(bootloader) has-slot:recovery: not found
(bootloader) is-logical:recovery: not found
Sending 'recovery' (20536 KB) OKAY [ 0.443s]
Writing 'recovery' (bootloader) Image not signed or corrupt
OKAY [ 0.481s]
Finished. Total time: 0.932s
twrp-3.3.1-0-griffin.img is the lastest image, from here.
The same error appears when I try to flash the lineage recovery:
fastboot flash recovery lineage-17.1-20201211-recovery-griffin.img
So what is wrong here?
I've been flashing a Moto e5 Plus today, and the ADB messages were the same, except without the "has slot" line. I think they are standard.
I also had trouble getting TWRP to "stick". What ended up working was booting into the bootloader, flashing TWRP and instead of rebooting I selected "recovery" with the volume buttons.
The TWRP site says this in its instructions:
Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install.
Click to expand...
Click to collapse
but holding Power + Volume Up after reboot didn't seem to work for me.
mfs-ness said:
What ended up working was booting into the bootloader, flashing TWRP ...
Click to expand...
Click to collapse
How did you flash TWRP - from the bootloader?
Or from the PC via fastboot - in which case there is always the above error, not just with TWRP images.
This is how I flashed TWRP from a linux desktop:
Code:
./adb -d reboot bootloader
sudo ./fastboot flash recovery ~/Downloads/twrp-3.4.0-0-hannah.img
(bootloader) is-logical:recovery: not found
Sending 'recovery' (19798 KB) OKAY [ 0.795s]
Writing 'recovery' (bootloader) Image not signed or corrupt
OKAY [ 0.552s]
Finished. Total time: 1.352s
The first line results in the screen with the open-chested android. Then I ran the fastboot command. Then I selected "recovery mode" on the phone.
mfs-ness said:
This is how I flashed TWRP from a linux desktop:
...
Click to expand...
Click to collapse
Not different from my technique.
So we seem to have different conditions on the phone, firmware, whatever.
Related
I followed @neo.ank's all-in-one guide and am having trouble flashing a custom recovery (twrp-2.7.1.0-condor.img). My bootloader is unlocked and fastboot flash recovery recovery.img works without problems:
Code:
C:\Folder>fastboot flash recovery recovery.img
target reported max download size of 268435456 bytes
sending 'recovery' (7300 KB)...
OKAY [ 0.235s]
writing 'recovery'...
OKAY [ 0.232s]
finished. total time: 0.471s
I then use my volume up and down buttons to select "Recovery mode," which returns me to the bootloader (the logs say "Boot up failed"). So I boot up into Android and adb reboot recovery, which works.
Now I see the "dead robot" with "No command." Huh, oh well, pressing power and volume up shows the "Android system recovery." A step ahead, but where is TWRP?
I think the guide I followed may be outdated. Has anyone had success using it to flash recovery on the 2015 Moto E?
TL;DR: Successfully flashed TWRP recovery, but it seemingly disappeared when trying to boot into it.
Fixed. I used the wrong recovery.img. Using the surnia recovery instead of condor works: http://forum.xda-developers.com/devdb/project/dl/?id=11449
Hi all,
Firstly, excuse my english...
I'm in OOS in version 2.1.3 (yea, old) with custom recovery and root. I have followed this guide : http://forum.xda-developers.com/oneplus-x/general/discussion-how-to-root-oneplus-x-t3242830
I have recently decided to upgrade in OOS 3.x and suprised...... Impossible to boot on TWRP.
$ adb reboot bootloader
Click to expand...
Click to collapse
→ fastboot mode OK
$ sudo fastboot devices
[sudo] Mot de passe de torlik :
4c6f1504 fastboot
Click to expand...
Click to collapse
detected, nice !
$ sudo fastboot boot twrp-2.8.7.0-onyx_f2fs_r9.img
downloading 'boot.img'...
OKAY [ 0.605s]
booting...
FAILED (remote: Device not unlocked cannot boot)
finished. total time: 0.606s
Click to expand...
Click to collapse
WOOT ?
$ sudo fastboot flash recovery twrp-2.8.7.0-onyx_f2fs_r9.img
target reported max download size of 1073741824 bytes
sending 'recovery' (12130 KB)...
OKAY [ 0.684s]
writing 'recovery'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 0.686s
Click to expand...
Click to collapse
WHAT ?
With VOL- (+) POWER, I boot in Oxygen Recovery, nothing else.
$ sudo fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) console_enabled: 0
(bootloader) exec_console_unconsole: 0
OKAY [ 0.006s]
finished. total time: 0.006s
Click to expand...
Click to collapse
(bootloader) Device unlocked: false
How my unlock has been lost ? My phone is yet rooted. SuperSu works correctly.
Can you tell me how it is possible to lost twrp ? I have never upgrade since my unlock.
And now, my only solution is to do a 'fastboot oem unlock' and lost my data ?
Thank you
Not sure whats going on there but easy way is to fastboot flash old stock recovery. Then install 3.1.3 with no problems. Rename file and delete .tar .
Your device bootloader is locked.
Why do you want to flash old TWRP.
To install OOS 3.1.3, you should better flash old OOS stock recovery.
But not sure it wil work.
Now, when you try to reboot recovery, on what recovery are you?
Always TWRP? None?
You should flash Oxygen one, so you can try to flash OOS 2.2.3 full rom zip to start.
Kéno40 said:
Your device bootloader is locked.
Why do you want to flash old TWRP.
To install OOS 3.1.3, you should better flash old OOS stock recovery.
But not sure it wil work.
Now, when you try to reboot recovery, on what recovery are you?
Always TWRP? None?
You should flash Oxygen one, so you can try to flash OOS 2.2.3 full rom zip to start.
Click to expand...
Click to collapse
Thanks for answers.
The issue is exactly that:
"Now, when you try to reboot recovery, on what recovery are you?"
I boot on stock recovery... oxygen recovery instead of twrp. Why?? How??
However I had flash my recovery with twrp last months ago and root my phone.
My problem is I do not want to lost my data... Indeed I can unlock again bootloader but all data will be lost.
How could you flash TWRP if your bootloader is locked? :-S
I don't think you ever get re-locked upon any update..
And yes, you probably have to unlock boot and lose all your user data.. Unless you don't have a backup handy of course :I
You can flash oos 3.1.1 through stock recovery no matter if your bootloader locked or unlocked.
Just download the full rom zip of oos 3.1.1 and place this zip in internal storage and flash with stock recovery. After installing oos3.1.1 you can backup your data and after that you have to go to the developer settings and allow the OEM Unlocking and now you can follow same procedure to unlock bootloader.
Hi Friends...
my phone had an unlocked bootloader with custom recovery sultan's TWRP 3.02
and recently i installed stock oxygenOS flashable zip 3.1.4 version..
everything was fine..
today i tried to install cyanogenmod 14 nightly build..
i downloaded the zip , gapps pico , superSu 2.78
went into twrp -> factory reset -> advanced-> wipe everything...
flashed os -> gapps -> super su and rebooted ..
after that my phone got stuck in oneplus logo for quite a long time ..so i switched it off and tried to switch On again..
.............................................bootloop...........................................
showed oneplus logo blinked again vibrated oneplus logo............it didnt boot up
i cant go into the newly installed OS ..and the recovery didnt boot also..
but fastboot worked though...
i tried to reflash the sultan recovery again ..using fastboot commands ..it got flashed but cant boot ...
then i tried to install original oxygen recovery MM version ..
later it showed the error that my device is not unlocked and cannot flash or erase...
i have told everything i did ..its my favorite phone ..one and only........
please help me guys...!!
prasannazx said:
Hi Friends...
my phone had an unlocked bootloader with custom recovery sultan's TWRP 3.02
and recently i installed stock oxygenOS flashable zip 3.1.4 version..
everything was fine..
today i tried to install cyanogenmod 14 nightly build..
i downloaded the zip , gapps pico , superSu 2.78
went into twrp -> factory reset -> advanced-> wipe everything...
flashed os -> gapps -> super su and rebooted ..
after that my phone got stuck in oneplus logo for quite a long time ..so i switched it off and tried to switch On again..
.............................................bootloop...........................................
showed oneplus logo blinked again vibrated oneplus logo............it didnt boot up
i cant go into the newly installed OS ..and the recovery didnt boot also..
but fastboot worked though...
i tried to reflash the sultan recovery again ..using fastboot commands ..it got flashed but cant boot ...
then i tried to install original oxygen recovery MM version ..
later it showed the error that my device is not unlocked and cannot flash or erase...
i have told everything i did ..its my favorite phone ..one and only........
please help me guys...!!
Click to expand...
Click to collapse
Use mega unbrick guide if you tried all other procedure.
I was caught up in the same situation. Follow the mega unbrick guide and your phone will be back to normal.
link to the mega unbrick please..
Asmmahin said:
link to the mega unbrick please..
Click to expand...
Click to collapse
Here you go
http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108
Is mega unbrick or hard unbrick is same ?
amgh said:
Is mega unbrick or hard unbrick is same ?
Click to expand...
Click to collapse
Both are same.some call it hard unbrick or some mega that's it.
1.) Make sure driver signature enforcement is disabled.
2) Download this :- http://www.mediafire.com/download/4aqwyi3g1d6wc67/Qualcomm 1.00.11.rar
Keep phone disconnected from PC.
Open the folder "qc" and install the Test Certificate in the following Stores: Trusted Root, Trusted Publisher, Third-Party Root and Personal
Run the Qualcomm setup wizard (also located in the qc folder)
When completed, restart your PC again with Driver Signature Disabled. (Optional but preferred)
4) press vol up button for 10s and plug it in pc keeping pressed
The driver should now automatically install. If not, go to device manager and right click "Unknown Device" and click "Update Driver" Search up the QC folder and press ok. The driver should now install.
5) now flash it with msmtool u can downloa th 47mb one in comments
http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108
6) the phone now should have the stock recovery
---------- Post added at 10:08 PM ---------- Previous post was at 10:07 PM ----------
sabrinano24 said:
1.) Make sure driver signature enforcement is disabled.
2) Download this :- http://www.mediafire.com/download/4aqwyi3g1d6wc67/Qualcomm 1.00.11.rar
Keep phone disconnected from PC.
Open the folder "qc" and install the Test Certificate in the following Stores: Trusted Root, Trusted Publisher, Third-Party Root and Personal
Run the Qualcomm setup wizard (also located in the qc folder)
When completed, restart your PC again with Driver Signature Disabled. (Optional but preferred)
4) press vol up button for 10s and plug it in pc keeping pressed
The driver should now automatically install. If not, go to device manager and right click "Unknown Device" and click "Update Driver" Search up the QC folder and press ok. The driver should now install.
5) now flash it with msmtool u can downloa th 47mb one in comments
http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108
6) the phone now should have the stock recovery
Click to expand...
Click to collapse
ps= remove the space in the frist link
Ok so i've the same problem but my phone can't boot after fix the brick it's the same:
C:\Android>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: true
(bootloader) Display panel:
(bootloader) console_enabled: 0
(bootloader) exec_console_unconsole: 0
OKAY [ 0.017s]
finished. total time: 0.019s
C:\Android>fastboot flash recovery recovery.img
target reported max download size of 1073741824 bytes
sending 'recovery' (15920 KB)...
OKAY [ 0.507s]
writing 'recovery'...
OKAY [ 0.303s]
finished. total time: 0.817s
C:\Android>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.516s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.556s
Bjr49000 said:
Ok so i've the same problem but my phone can't boot after fix the brick it's the same:
C:\Android>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: true
(bootloader) Display panel:
(bootloader) console_enabled: 0
(bootloader) exec_console_unconsole: 0
OKAY [ 0.017s]
finished. total time: 0.019s
C:\Android>fastboot flash recovery recovery.img
target reported max download size of 1073741824 bytes
sending 'recovery' (15920 KB)...
OKAY [ 0.507s]
writing 'recovery'...
OKAY [ 0.303s]
finished. total time: 0.817s
C:\Android>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.516s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.556s
Click to expand...
Click to collapse
did you install a rom after the fix ?
After fix, it's the official ROM so déveloper > OEM and USB debuging
adb reboot bootloader
Adb oem unlock ans After the command i write
prasannazx said:
Hi Friends...
my phone had an unlocked bootloader with custom recovery sultan's TWRP 3.02
and recently i installed stock oxygenOS flashable zip 3.1.4 version..
everything was fine..
today i tried to install cyanogenmod 14 nightly build..
i downloaded the zip , gapps pico , superSu 2.78
went into twrp -> factory reset -> advanced-> wipe everything...
flashed os -> gapps -> super su and rebooted ..
after that my phone got stuck in oneplus logo for quite a long time ..so i switched it off and tried to switch On again..
.............................................bootloop...........................................
showed oneplus logo blinked again vibrated oneplus logo............it didnt boot up
i cant go into the newly installed OS ..and the recovery didnt boot also..
but fastboot worked though...
i tried to reflash the sultan recovery again ..using fastboot commands ..it got flashed but cant boot ...
then i tried to install original oxygen recovery MM version ..
later it showed the error that my device is not unlocked and cannot flash or erase...
i have told everything i did ..its my favorite phone ..one and only........
please help me guys...!!
Click to expand...
Click to collapse
That is because the kernel and boot loader used for 14.1 is different you need to update the kernel.
Follow Mega unbrick guide carefully to unbrick the phone.
sabrinano24 said:
did you install a rom after the fix ?
Click to expand...
Click to collapse
After the fix, i've OOS, and that all.
Bjr49000 said:
Ok so i've the same problem but my phone can't boot after fix the brick it's the same:
C:\Android>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: true
(bootloader) Display panel:
(bootloader) console_enabled: 0
(bootloader) exec_console_unconsole: 0
OKAY [ 0.017s]
finished. total time: 0.019s
C:\Android>fastboot flash recovery recovery.img
target reported max download size of 1073741824 bytes
sending 'recovery' (15920 KB)...
OKAY [ 0.507s]
writing 'recovery'...
OKAY [ 0.303s]
finished. total time: 0.817s
C:\Android>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.516s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.556s
Click to expand...
Click to collapse
I had same issue you need to flash different TWRP. If your on 2.X.X TWRP 3.0.2 . If you have updated to 3.X.X then 3.0.3. If you have issues with 3.0.3 you can try twrp 3.0.2-0 or bluesparks 3.0.2-1 V41.
just flash the arsenic-kernel everything will be fine.. https://forum.xda-developers.com/oneplus-x/development/kernel-arsenic-kernel-r2-t3422020
The problem is not the kernel but the bootloader so how to change/update recovery?
Bjr49000 said:
The problem is not the kernel but the bootloader so how to change/update recovery?
Click to expand...
Click to collapse
If you did not unlocked bootloader properly then also you might face the problem...
to unlock bootloader: https://forum.xda-developers.com/oneplus-x/general/discussion-how-to-root-oneplus-x-t3242830
make sure you follow all the step. (If you didn't followed these steps then lock bootloader {fastboot oem lock} and unlock using this mathod.)
Falsh this kernal after flashing rom and gapps, https://forum.xda-developers.com/oneplus-x/development/kernel-arsenic-kernel-r2-t3422020
Don't forget to hit :good:
Bjr49000 said:
Ok so i've the same problem but my phone can't boot after fix the brick it's the same:
C:\Android>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: true
(bootloader) Display panel:
(bootloader) console_enabled: 0
(bootloader) exec_console_unconsole: 0
OKAY [ 0.017s]
finished. total time: 0.019s
C:\Android>fastboot flash recovery recovery.img
target reported max download size of 1073741824 bytes
sending 'recovery' (15920 KB)...
OKAY [ 0.507s]
writing 'recovery'...
OKAY [ 0.303s]
finished. total time: 0.817s
C:\Android>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.516s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.556s
Click to expand...
Click to collapse
I used to have this problem. You need to flash the new bootloader, sometimes updates and whatnot doesn't flash it for you. If the zip doesn't work you can try finding the fastboot partition image and flashing to aboot (instead of fastboot flash recovery recovery.img when flashing a twrp build for example, it would be fastboot flash aboot emmc_appsboot.mbn). There was a post on the oneplus forums where the files could be found, just google dtb not found error.
Hi all,
I have an LG G5 H850. I'm trying to install TWRP using ADB. I've had it previously and it worked fine. I'm pretty sure the bootloader is unlocked. Anyway, when I do "fastboot flash recovery twrp-3.1.1.1-0-h850.img" I get the following output:
target reported max download size of 536870912 bytes
sending 'recovery' (19076 KB)...
OKAY [ 0.431s]
writing 'recovery'...
OKAY [ 0.345s]
finished. total time: 0.781s
To me, that looks as though thats worked fine. Now when I try fastboot boot twrp-3.1.1.1-0-h850.img I get the following:
downloading 'boot.img'...
OKAY [ 0.432s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.456s
Has anyone got any ideas on this?
Same here
I am having the same problem, please help
Had this issue a while back. I resorted to doing complete flash with LGUP to the latest version and then it worked. I had been messing around with various ROMS on different android versions.
lywyn said:
Had this issue a while back. I resorted to doing complete flash with LGUP to the latest version and then it worked. I had been messing around with various ROMS on different android versions.
Click to expand...
Click to collapse
Don't happen to know where I could get a rom that it would work with do you?
Managed to solve this. Flashed the TWRP image using fastboot flash recovery <img> via adb. Then I unplugged from USB, and got into recovery mode by doing power + volume down buttons and quickly release and repress ont he LG logo. Answered yes to both questions and got into TWRP.
Barsbeh said:
Managed to solve this. Flashed the TWRP image using fastboot flash recovery <img> via adb. Then I unplugged from USB, and got into recovery mode by doing power + volume down buttons and quickly release and repress ont he LG logo. Answered yes to both questions and got into TWRP.
Click to expand...
Click to collapse
That is the required way of doing it. You have to boot into recovery after flashing the recovery or it gets reset.
Hi,
Having a similar problem since trying to update my ROM ... and the Magisk install failed. Now I can only get to fastboot, can't get to recovery. And, tried this,
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp-3.1.1-0-h830.img
target reported max download size of 536870912 bytes
sending 'recovery' (18644 KB)...
OKAY [ 0.439s]
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 0.461s
Help!?! ... and thanks!
Hi,
my Xperia Z2 (runs on Android 4.4.2) is rooted with Kingroot app, the bootloader is unlocked and I flashed recovery with fastboot to TWRP and got the notify flashing was finished.
[email protected] ~ $ fastboot flash recovery /home/mint/Desktop/twrp.img
sending 'recovery' (13302 KB)...
OKAY [ 0.528s]
writing 'recovery'...
OKAY [ 0.879s]
finished. total time: 1.408s
Click to expand...
Click to collapse
When I open the ROM manager app it says my recovery system is TWRP.
My problem: I can't boot in TWRP!?! Intention is to flash system to Lineage OS 17.1.
Not with Volume down+power, not via adb command "reboot recovery" and not with some apps I tried with reboot options, nothing works.
Meanwhile I flashed 3 different TWP images, 3.0.2-0, 3.2.3-0 and 3.3.1, always with the same results like listed above. Booting in TWRP is not possible. Of course I would try it with an similiar image like clockworkmod, but couldn't find one for my device.
I've the same problem in the moment...
Do you've a solution for me?