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.
Hey guys, I'm in need of some help....
I was flashing an update to my ROM on my unlocked HTC One using CWM touch recovery. The aroma update process appeared to complete correctly and i rebooted the phone however, it failed to get past the bootloader screen trying to boot the rom. When it bootlooped back into recovery I discovered I have a pretty major problem, the bootloader attempted to boot into recovery, flashed up the CWM recovery screen, but then that bootlooped too. I can reboot into HBOOT/fastboot but nothing else. I have tried fastboot flash recovery to TWRP and CWM but they are still flashing up and then rebooting. Any ideas on what I can do to dry and rectify this? I don't really fancy a £600 paperweight a couple of weeks after getting it...
Cheers
I was running ARHD 10.1 and flashed TeamSeven's kernel in Clockwork Recovery. Went to reboot and the phone just boot loops, no big deal right. So when I put the phone back into bootloader screen and tried to boot into recovery it boots for about .50 seconds into my custom recovery then boots back to the Fastboot HTC Screen. Im unable to get into my custom recovery. Ive tried using the All in one tool to flash different recoverys and have been successful in doing so, I know this because they boot for the .50 seconds into TWRP or Clockwork then goes back into the HTC Fastboot screen. Does anybody have any ideas? How can I fix this? I tried to sideload a rom but it seems it will not let me until im able to get into my custom recovery.
Have you used ADB to delete cache, Then re-flash a recovery ? Then full wipe etc and clean install a Rom ?
Sent from my HTC One using Tapatalk 2
jthornton71707 said:
I was running ARHD 10.1 and flashed TeamSeven's kernel in Clockwork Recovery. Went to reboot and the phone just boot loops, no big deal right. So when I put the phone back into bootloader screen and tried to boot into recovery it boots for about .50 seconds into my custom recovery then boots back to the Fastboot HTC Screen. Im unable to get into my custom recovery. Ive tried using the All in one tool to flash different recoverys and have been successful in doing so, I know this because they boot for the .50 seconds into TWRP or Clockwork then goes back into the HTC Fastboot screen. Does anybody have any ideas? How can I fix this? I tried to sideload a rom but it seems it will not let me until im able to get into my custom recovery.
Click to expand...
Click to collapse
type fastboot erase cache from PC while phone is in fastboot. you should be able to get into recovery afterwards. If not, flash another recovery from fastboot. fastboot flash recovery RECOVERYNAME.img
I rooted and flashed CM14 ROM for the H811 G4. had to use fastboot boot recovery command because flashing recovery didn't work. ROM loaded/worked totally fine, went to flash Super SU in recovery, phone flashed it, rebooted and then didnt boot up again. Stuck on the CM14 logo, tried flashing stock KDZ, kept getting errors like unable to connect. Any ideas on how to get this thing back up and running?
Hello Guys,
Yesterday I tried to root my Moto 2g.
Unlocked it's bootloader,Installed Twrp and installed supersu. Also downloaded a custom mod(the most famous one I guess) and installed it,only to find out that the phone would no longer boot
but keep looping on the unlocked bootloader warning screen.While thinking that I had downloaded a non-compatible mod I Installed another one.After that,booting the phone would Instantly
take me to the recovery mode and keep looping the Teamwin logo.
I decided not to mess anymore with it and reinstall the stock firmware for moto 2g. After Installing it the Motorola logo comes up and then I am taken to the fastboot screen once again with the error saying:
"Fastboot reason,Fell through from boot recovery mode".Tried to flash CWM to see If I could get into recovery mode from there but I would get CWM logo loops exactly the same way they appeared with Teamwin logo.
Seems like phone is dead to me but still have a bit of hope,although the only place I can get is fastboot.
Edit:I tried to fastboot flash boot boot.img the stock image and I got and error saying that boot.img(10mb) exceeded the partition limit
shatterbb said:
Hello Guys,
Yesterday I tried to root my Moto 2g.
Unlocked it's bootloader,Installed Twrp and installed supersu. Also downloaded a custom mod(the most famous one I guess) and installed it,only to find out that the phone would no longer boot
but keep looping on the unlocked bootloader warning screen.While thinking that I had downloaded a non-compatible mod I Installed another one.After that,booting the phone would Instantly
take me to the recovery mode and keep looping the Teamwin logo.
I decided not to mess anymore with it and reinstall the stock firmware for moto 2g. After Installing it the Motorola logo comes up and then I am taken to the fastboot screen once again with the error saying:
"Fastboot reason,Fell through from boot recovery mode".Tried to flash CWM to see If I could get into recovery mode from there but I would get CWM logo loops exactly the same way they appeared with Teamwin logo.
Seems like phone is dead to me but still have a bit of hope,although the only place I can get is fastboot.
Edit:I tried to fastboot flash boot boot.img the stock image and I got and error saying that boot.img(10mb) exceeded the partition limit
Click to expand...
Click to collapse
try flashing the whole Stock Firmware
It might help,
U said u flashed a MOD over stock ROM?
If so, u should have boot first Just After unlocking the bootloader before Flashing any MODs
raj_45 said:
try flashing the whole Stock Firmware
It might help,
U said u flashed a MOD over stock ROM?
If so, u should have boot first Just After unlocking the bootloader before Flashing any MODs
Click to expand...
Click to collapse
I did boot after unlocking and normally flashed whole stock firmware.This morning I woke up and the error message in fastboot is 'boot up failed' for bot normal and recovery mode
shatterbb said:
I did boot after unlocking and normally flashed whole stock firmware.This morning I woke up and the error message in fastboot is 'boot up failed' for bot normal and recovery mode
Click to expand...
Click to collapse
is this your problem
raj_45 said:
is this your problem
Click to expand...
Click to collapse
Ok let me explain the situation better.Last night I used a stock firmware I found and flashed it.When I tried to boot I would see motorola logo once
fore boot mode,Then it would go to recovery so I would see it for a second time and then I would see teamwin logo looping so the phone was not
able to get into recovery mode but only into bootloader.
After That I flashed CWM and the same thing would happen with CWM logo looping now in recovery mode.
Today I woke up and flashed CWM again,and for some reason I could get into CWM and use it normally
So what I did is Installed Supersu and a mod for my xt1068 and tried to boot but phone stuck in the same endless loop again and I also cant get
into CWM again as its logo keeps flashing instead of taking me into the menu.
I believe there is an error with my data folder or partition or w/e.
Most of all I want to be able to get into CWM again
shatterbb said:
Ok let me explain the situation better.Last night I used a stock firmware I found and flashed it.When I tried to boot I would see motorola logo once
fore boot mode,Then it would go to recovery so I would see it for a second time and then I would see teamwin logo looping so the phone was not
able to get into recovery mode but only into boot loader.
After That I flashed CWM and the same thing would happen with CWM logo looping now in recovery mode.
Today I woke up and flashed CWM again,and for some reason I could get into CWM and use it normally
So what I did is Installed Supersu and a mod for my xt1068 and tried to boot but phone stuck in the same endless loop again and I also cant get
into CWM again as its logo keeps flashing instead of taking me into the menu.
I believe there is an error with my data folder or partition or w/e.
Most of all I want to be able to get into CWM again
Click to expand...
Click to collapse
So u are not able to get into Recovery
And u can get to Fast boot Mode?
If yes Flash TWRP latest(3..1.0-0)
Boot into TWRP
Reset or Install any Custom ROM like LiniageOS or AOSP
I think it's the problem with SuperSU?
Which MOD did u install?
raj_45 said:
So u are not able to get into Recovery
And u can get to Fast boot Mode?
If yes Flash TWRP latest(3..1.0-0)
Boot into TWRP
Reset or Install any Custom ROM like LiniageOS or AOSP
I think it's the problem with SuperSU?
Which MOD did u install?
Click to expand...
Click to collapse
Thanks for the replies,I managed to solve the problem and install Cyanogenmod.I guess everything came up to this:
After the first time I installed twrp I decided to wipe my data folder but somehow it was deleted and the partition became raw type which caused
all the bootlooping problems.
Using CWM I was able to get into recovery mode and then I chose to format my data folder and sd card(as ext4 I guess) and the data folder was
recreated.
After that I normally flashed Cyanogenmod and device booted just fine