I had a mostly-stock Nexus 7 running 4.1.1 - unlocked, rooted, TWRP installed, but no major /system changes. When the update came in, I figured "what the heck, I'll just see if it applies - worst case I lose root and my recovery console, but it's a nexus, it's easy to get those back". I applied the update, and it worked! It applied and rebooted, worked fine - but it did lose root and recovery as I expected.
So I tried to get recovery back. It won't come back. Here are the ways I tried:
Hold down VolUp+VolDown+Power to get to fastboot mode. Ran
Code:
fastboot boot recovery.img
(using a number of different copies of both clockwork and TWRP recovery). Each time, the screen went black, google logo came up, but then it booted to AndroidOS
Tried to do
Code:
fastboot flash recovery recovery.img
The flash seemed to look like it did fine, but when I selected "Boot Recovery", it didn't. It booted Android OS
I can get into STOCK recovery using the normal method of selecting it from the menu just fine.
Stock recovery doesn't have ADB running. Fastboot mode doesn't have adb running. Fastboot doesn't have any command for rebooting into recovery apart from the method I mentioned (fastboot boot recovery.img). Booting into AndroidOS reflashes the recovery console with the stock console (I tried to race it running adb reboot recovery, but lost).
I tore my hair out for hours. Nothing I tried would let me boot into a custom recovery. I eventually backed everything up as best as I could using adb (Since luckily Android OS still worked), and reflashed to stock everything. PROBLEM IS STILL HERE! Then I decide to revert the bootloader from 3.41 to 3.34. SUCCESS. 3.34 booted to recovery without any problems at all.
Any idea what the heck is going on here? Anybody else seen this? All the threads I've seen with people having problems booting into recovery end with somebody suggesting "Just get app xyz that will reboot into recovery" - but that is NOT an option if A). you cannot get it to boot or B). you are not rooted/are running stock, because you can't be in AndroidOS and still have the custom recovery flashed UNTIL you are able to get into recovery to actually fix it.
Here's a video of me trying to flash recovery, since nobody will believe me that it doesn't work. Turn off the audio, the bell noise is obnoxious, sorry.
http://www.youtube.com/watch?v=zhHWiu7pO34
I brought up the same concerns when I did a manual flash to 4.1.2 and went through a mess eventually reverting to 4.1.1, using OTA rootkeeper than updating again because on bootloader 3.41 *NO* custom recoveries successfully boot.
how do you flash the old bootloader? if you don't mind me asking.
I have been on boot loader 3.41 for a few days and no issues with twrp. I have flashed a few things since and all is good? Sorry not sure why its not working for some.
ls3c6 said:
I brought up the same concerns when I did a manual flash to 4.1.2 and went through a mess eventually reverting to 4.1.1, using OTA rootkeeper than updating again because on bootloader 3.41 *NO* custom recoveries successfully boot.
Click to expand...
Click to collapse
Huh? I have 3.41 and can go from bootloader to recovery with no problems. Even got a video of it if you don't believe me
Sent from my Galaxy Nexus
You are not alone in this issue, me too, and others more, http://forum.xda-developers.com/showthread.php?t=1932063
I update to 4.1.2 using CWM, didn't lose root. Then changed back to TWRP 2.2.2.0 with bootloader 3.41, now I just updated to TWRP 2.2.3. Everything went smooth even though I'm android noobie.
anotherxyz said:
how do you flash the old bootloader? if you don't mind me asking.
Click to expand...
Click to collapse
Code:
fastboot flash bootloader bootloader-3.34-grouper.img
(or whatever the actual filename is). Then you do:
Code:
fastboot reboot-bootloader
You should at that point see the correct version listed in fastboot
masully84 said:
Huh? I have 3.41 and can go from bootloader to recovery with no problems. Even got a video of it if you don't believe me
Click to expand...
Click to collapse
I think the issue comes from going back to stock recovery without a rooted AndroidOS. Either one by itself seems to be fine. If you still have the CWR or TWRP recovery already flashed, 3.41 can boot to that. If you have root in AndroidOS, you can always re-flash recovery from ROM Manager or something, and that will work fine. And you can boot to recovery from Android OS (so long as you have root).
If you have stock recovery and no root, your only option is fastboot. And that fastboot flash and boot commands do not work. They look like they work - but they don't. So if you already HAVE a custom recovery, it probably won't even break it.
If you really want to do a proper test / prove this, go back to stock recovery with 3.41. Turn the tablet off completely. Boot up holding the three buttons and go into recovery to see that it can go into the stock recovery console. Then reboot with the three buttons again (don't boot AndroidOS), and run the fastboot boot command to run a custom recovery. If that works, I'll eat my hat.
(well, really all that means is that the problem isn't occurring on all systems. Doesn't mean it's not happening to me and many others)
The problem might not be that 3.41 can't boot to recovery -it might just be that 3.41 can't FLASH or BOOT a recovery console through fastboot. Many people will never notice that because:
A). They already have a recovery console flashed, so it still works
B). They flash their recovery from ROM Manager, GooManager, or whatever
If you lose root, you no longer have B as an option. If you also lose your recovery console, you can't get root access back without fastboot, so you have to use fastboot.
Se7enLC said:
Code:
I think the issue comes from going back to stock recovery without a rooted AndroidOS. Either one by itself seems to be fine. If you still have the CWR or TWRP recovery already flashed, 3.41 can boot to that. If you have root in AndroidOS, you can always re-flash recovery from ROM Manager or something, and that will work fine. And you can boot to recovery from Android OS (so long as you have root)[...]
[/QUOTE]
Not sure you've got it right. At least on my N7. My first try was flashing the update.zip in another thread without updating my ROM at all. Running Paranoid Android (2.1799 then) and TWRP. Not sure when in the mix I updated TWRP though.
Thought it might have been a problem with the update.zip, so downloaded the full update.zip from google and tried installing bootloader*.img from that via fastboot.
No change. Reverted to 3.34 without any playing around with deleting files and all is good.
Click to expand...
Click to collapse
Se7enLC said:
I had a mostly-stock Nexus 7 running 4.1.1 - unlocked, rooted, TWRP installed, but no major /system changes. When the update came in, I figured "what the heck, I'll just see if it applies - worst case I lose root and my recovery console, but it's a nexus, it's easy to get those back". I applied the update, and it worked! It applied and rebooted, worked fine - but it did lose root and recovery as I expected.
So I tried to get recovery back. It won't come back. Here are the ways I tried:
Hold down VolUp+VolDown+Power to get to fastboot mode. Ran
Code:
fastboot boot recovery.img
(using a number of different copies of both clockwork and TWRP recovery). Each time, the screen went black, google logo came up, but then it booted to AndroidOS
Tried to do
Code:
fastboot flash recovery recovery.img
The flash seemed to look like it did fine, but when I selected "Boot Recovery", it didn't. It booted Android OS
I can get into STOCK recovery using the normal method of selecting it from the menu just fine.
Stock recovery doesn't have ADB running. Fastboot mode doesn't have adb running. Fastboot doesn't have any command for rebooting into recovery apart from the method I mentioned (fastboot boot recovery.img). Booting into AndroidOS reflashes the recovery console with the stock console (I tried to race it running adb reboot recovery, but lost).
I tore my hair out for hours. Nothing I tried would let me boot into a custom recovery. I eventually backed everything up as best as I could using adb (Since luckily Android OS still worked), and reflashed to stock everything. PROBLEM IS STILL HERE! Then I decide to revert the bootloader from 3.41 to 3.34. SUCCESS. 3.34 booted to recovery without any problems at all.
Any idea what the heck is going on here? Anybody else seen this? All the threads I've seen with people having problems booting into recovery end with somebody suggesting "Just get app xyz that will reboot into recovery" - but that is NOT an option if A). you cannot get it to boot or B). you are not rooted/are running stock, because you can't be in AndroidOS and still have the custom recovery flashed UNTIL you are able to get into recovery to actually fix it.
Here's a video of me trying to flash recovery, since nobody will believe me that it doesn't work. Turn off the audio, the bell noise is obnoxious, sorry.
http://www.youtube.com/watch?v=zhHWiu7pO34
Click to expand...
Click to collapse
Found the solution to the the issue (sorta), I too went through all this trouble as you did in your OP.
I did not have to do anything other then straight up flash this version "recovery-clockwork-touch-6.0.1.5.b8147-grouper.img" via fastboot and bam! recovery works. Link - http://forum.xda-developers.com/showpost.php?p=32810167&postcount=228
Problem is with previous versions of 6.0.1.0 (Official) and TWRP 2.3.1
I still prefer TWRP, but hey This is better then the alternative (No recovery at all)
Now we need to figure out what changed between CWM 6.0.1.0 and 6.0.1.5 and get the other guys (TWRP) to fix their **** for us poor saps that seem to be a minority in the Nexus 7 world having this issue.
I would love to know what actually the fix is and why only some have these issues with older versions of CWM and TWRP.
Whenever my recovery is TWRP I am not able to boot into any type of ROM. Every time I reboot my phone it will be past the "your bootloader is unlock" and always boots straight into TWRP. When I flash stock recovery I am stuck at a image of a Android and it just stays at "erasing..." till it reboots itself. I have attempted to flash different types of roms by sideloading through TWRP and also attempted to flash stock recovery through fastboot with no luck at all.
The issue started whenever I was on stock 6.0 and flashed TWRP. Once I was in TWRP at the end when I was rebooting my phone I said yes to install supersu, which I know now was a mistake. Afterwards I was stuck in a bootloop were I finally attempted to do a factory reset which seemed to have made things worse. That was when I was stuck at the "erasing..." whenever I attempted to boot through stock recovery. Not sure what else to try at this point.
Any help would be great at this point.
I'm in the same boat. Exact same problem with no idea how to fix. I can get into fastboot screen, but that's it. Suggestions? Thanks in advance.
Hello,
I used oneplus 3t toolkit to force decryption and then was able to boot into rom
But when I go to TWRP it just gives black screen with continuous led light on.
I tried flashing twrp again with same toolkit, ends with success message but still not able to get into twrp.
Please help
Same Problem here...
Alter flashing twrp I First was able to Start it and Flash supersu and debloat. Now I just get a white LED.
Booting to oos 4.0 works fine.
Gesendet von meinem ONEPLUS A3003 mit Tapatalk
Freeze on Pecovery screen
I am running leaked version Nougat (build 19-12-2016) and phone starts normal. Phone is rooted. When I start in recovery...phone freezes on recovery logo image (team-win) screen. So no more possible to get in menu of recovery. I also flashed other recovery via fastboot (3.0.2.0, 3.0.2.1 and 3.0.3.0) but same issue. What to do??
Edit...after more than 1 minut waiting time on recovery screen 3.0.3.0 got further in menu.
Solex49 said:
I am running leaked version Nougat (build 19-12-2016) and phone starts normal. Phone is rooted. When I start in recovery...phone freezes on recovery logo image (team-win) screen. So no more possible to get in menu of recovery. I also flashed other recovery via fastboot (3.0.2.0, 3.0.2.1 and 3.0.3.0) but same issue. What to do??
Edit...after more than 1 minut waiting time on recovery screen 3.0.3.0 got further in menu.
Click to expand...
Click to collapse
Did you do anything other than flash the older version of TWRP? After the Nougat update when I boot into recovery it only boots to the stock recovery. I've flashed numerous versions of TWRP and even run the following command to force the boot into TWRP (this worked for me last time) 'fastboot boot twrp-3.0.3-0-oneplus3t.img'. Still no luck. All I get is the TWRP splashscreen for 15+ minutes.
AustinVillan said:
Did you do anything other than flash the older version of TWRP? After the Nougat update when I boot into recovery it only boots to the stock recovery. I've flashed numerous versions of TWRP and even run the following command to force the boot into TWRP (this worked for me last time) 'fastboot boot twrp-3.0.3-0-oneplus3t.img'. Still no luck. All I get is the TWRP splashscreen for 15+ minutes.
Click to expand...
Click to collapse
Nil...can't remember anymore what I have done more. Maybe better to install original full Rom 4.0.2 and thereafter root again..
Hi,
Recently I updated my EMUI firmware via the official OTA system.
I had the bootloader unlocked prior to installing the update however afterwards the bootloader was locked. I have verified this in Fastboot.
I wish to flash Magisk on my P9 Plus, however, I have a bootloader unlock code (back when Huawei gave them out freely) however I don't want to unlock the bootloader as it will factory reset (I spent a long time setting everything up).
I tried flashing a TWRP image however the bootloader prevents it as it is not unlocked.
The only other method would to boot the custom recovery image however when executing fastboot boot recovery TWRP twrp-3.1.1-1-vie.img it gives FAILED (remote: Command not allowed). I had noticed this inability to boot images even when I had the bootloader unlocked (I did not want to overwrite the stock recovery or eRecovery for easier OTA updates).
I have the Chinese variant of the P9 Plus : VIE-AL10 Full Netcom Edition.
Is anyone else having this problem? Please let me know if or how to fix this.
Thanks
It's been a while since I last used fastboot boot but if i remember correctly the command is "fastboot boot recovey.img, without that" recovery" in between
if the bootloader is locked you cant flash magisk or any other, also you cant boot with any images
I have my phone rooted. I have the twrp image on my phone and can fastboot into it. But it does not flash as my recovery. I have no recovery at all. Phone boots fine but has screen I have to press the power button twice on before it will boot. Saying unlocked bootloader and unsafe phone don't have any personal data.. Ect. I downgrade from a13 to a12 and an currently running the fsociety kernel. What can I do to A. Get my recovery back and B. Get rid of the boot error screen everutime I boot.
The Pixel series do not have a recovery partition; you cannot permanently install a custom recovery. If you are not using a custom ROM, there is no reason to use TWRP.
Do not try to remove the bootloader warning screen. It is part of Android functioning as intended, and trying to remove it may corrupt your bootloader.