Related
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.
Hello All,
Sorry if this has already been solved before, and thanks in advance for help. (I tried to post this in the ARHD41.0 thread, but as a newbie I cannot post there.)
I have an HTC One (AT&T) that had been updated to 4.3 OTA, then unlocked via htcdev, flashed with CWM 6.0.4.3 recovery, and then rooted with the Superuser zip on the CWM site. The device remained S-On. Made a backup through CWM recovery, transferred that to my PC, then figured I might as well celebrate the holidays by flashing my first ROM.
I downloaded the Android Revolution HD 41.0 ROM (forum.xda-developers.com/showthread.php?t=2183023), transferred to the SD, and then installed the zip through the CWM ROM manager (it seemed at least from what I read in the posts that followed that the ROM worked just fine with CWM). After going through the option selection process (I believe that this was the Aroma installer), I opted to wipe data since I was starting from a different ROM altogether (of course, silly me, this also wiped the backup on the SD). Seemed to install just fine, booted into what appears to be some part of the recovery where it asked if I wanted to root, I selected yes, and the phone rebooted.
Or, at least, tried to. It has been stuck at the beginning of the boot, where there is a white background with the HTC logo and "quietly brilliant" underneath, and it remains stuck there. If I press power and volume down for an abnormally long time, I can get into the bootloader and the recovery from there, but rebooting from there just leaves me at the boot screen again. As I said, there is no backup on the SD for me to restore. When in bootloader, I connected to the PC and fastboot turns to fastboot USB, but adb isn't showing anything when I enter abd devices.
I'm sure I probably did something very silly and am missing something very simple, but given that this is my first time, I have no idea what it is and how to go about fixing it.
Thanks again for all your help!
lyciansarpedon said:
Hello All,
Sorry if this has already been solved before, and thanks in advance for help. (I tried to post this in the ARHD41.0 thread, but as a newbie I cannot post there.)
I have an HTC One (AT&T) that had been updated to 4.3 OTA, then unlocked via htcdev, flashed with CWM 6.0.4.3 recovery, and then rooted with the Superuser zip on the CWM site. The device remained S-On. Made a backup through CWM recovery, transferred that to my PC, then figured I might as well celebrate the holidays by flashing my first ROM.
I downloaded the Android Revolution HD 41.0 ROM (forum.xda-developers.com/showthread.php?t=2183023), transferred to the SD, and then installed the zip through the CWM ROM manager (it seemed at least from what I read in the posts that followed that the ROM worked just fine with CWM). After going through the option selection process (I believe that this was the Aroma installer), I opted to wipe data since I was starting from a different ROM altogether (of course, silly me, this also wiped the backup on the SD). Seemed to install just fine, booted into what appears to be some part of the recovery where it asked if I wanted to root, I selected yes, and the phone rebooted.
Or, at least, tried to. It has been stuck at the beginning of the boot, where there is a white background with the HTC logo and "quietly brilliant" underneath, and it remains stuck there. If I press power and volume down for an abnormally long time, I can get into the bootloader and the recovery from there, but rebooting from there just leaves me at the boot screen again. As I said, there is no backup on the SD for me to restore. When in bootloader, I connected to the PC and fastboot turns to fastboot USB, but adb isn't showing anything when I enter abd devices.
I'm sure I probably did something very silly and am missing something very simple, but given that this is my first time, I have no idea what it is and how to go about fixing it.
Thanks again for all your help!
Click to expand...
Click to collapse
Hey,
Not to worry just run this command from fastboot (Power button +vol down while booting-> fastboot) plug your phone in and run
fastboot erase cache
Click to expand...
Click to collapse
and if its not fixed, just flash again. Make a back up next time! BTW if you need adb just get it from HERE (hint clickn 'here') if you need more help PM me, im always available
You need TRWP 2.6.3.3 or latest version (2.6.3.4) recovery!
Some members successfully flashed by CWM but also some of them face problems, so its better to you to follow FAQ to get good results : )
http://forum.xda-developers.com/showpost.php?p=48035061&postcount=62237
Ba7rani said:
You need TRWP 2.6.3.3 or latest version (2.6.3.4) recovery!
Some members successfully flashed by CWM but also some of them face problems, so its better to you to follow FAQ to get good results : )
http://forum.xda-developers.com/showpost.php?p=48035061&postcount=62237
Click to expand...
Click to collapse
I actually just saw the posts about the CWM issue a little while ago - that's what I get for not reading all the posts! I flashed with TWRP, the ROM installed, and the phone booted.
Now, this is where things get interesting. My backup that I had made with CWM before I initially tried to flash the ROM was still in \data\media\clockworkmod (where it had initially backed up to), and I wanted to check if I was still able to restore from it. TWRP doesn't recognize it as a backup folder/file (not sure if it would be compatible; this is also my first time restoring), and I flashed back to CWM recovery (phone still boots fine after that)...which doesn't recognize it either. I tried moving it to \sdcard\clockworkmod (where the md5 checksum file was originally generated), \sdcard (just in case, since the recovery option says "restore from \sdcard"), as well as \mnt\shell\emulated\clockworkmod (that's where the CWM ROM manager says that it would have backed up to), but the recovery says "No files found" for any of those as well. Any thoughts on where the backup ought to be located?
lyciansarpedon said:
I actually just saw the posts about the CWM issue a little while ago - that's what I get for not reading all the posts! I flashed with TWRP, the ROM installed, and the phone booted.
Now, this is where things get interesting. My backup that I had made with CWM before I initially tried to flash the ROM was still in \data\media\clockworkmod (where it had initially backed up to), and I wanted to check if I was still able to restore from it. TWRP doesn't recognize it as a backup folder/file (not sure if it would be compatible; this is also my first time restoring), and I flashed back to CWM recovery (phone still boots fine after that)...which doesn't recognize it either. I tried moving it to \sdcard\clockworkmod (where the md5 checksum file was originally generated), \sdcard (just in case, since the recovery option says "restore from \sdcard"), as well as \mnt\shell\emulated\clockworkmod (that's where the CWM ROM manager says that it would have backed up to), but the recovery says "No files found" for any of those as well. Any thoughts on where the backup ought to be located?
Click to expand...
Click to collapse
If you have Titanium backup pro you can restore from nandroid file
Menu > restore from Nandroid ..
* Its not recommended to restore system apps or data by Titanium
Found my mistake:
lyciansarpedon said:
\mnt\shell\emulated\clockworkmod\backup (that's where the CWM ROM manager says that it would have backed up to)
Click to expand...
Click to collapse
Missed that I needed to create that directory, oy. Recovery found it just fine, and restored it just as I left it.
Thanks all!
TMobile 6006
How do I get into recovery without being able to boot into system and the hardware recovery method doesn't work?
New to this device. Had no problem rooting, installing CWM 6028 and getting into CWM either via hardware or booting recovery from the rooted stock.
I installed [ROM][LB][UB] eXistenZ v7.0.0 and it came up great with no problems. Installed Root Explorer and TiBu w/o problem. Booted into CWM recovery from system without problem. Restored some files system data with TiBu. Rebooted and went into a boot loop where the boot animation comes up and then the phone reboots. I managed to turn the phone off by holding power and vol+. But, on reboot I can no longer into CWM recovery. I want to reflash the rom, or restore a backup either to stock or the working new rom.
I can get fastboot to recognize the phone but don't know a command to boot into recovery. I'm certain that the CWM Recovery is still valid. I just need to get into CWM one time!
HELP!
TWRP in general for me has been a mixed bag. I remember using it back when I had my Galaxy S4, and it had problems making nandroids for Touchwiz, but not CM. Typically there was a problem with the kernel. Lately with my Nexus 6 periodically it will either freeze/stall. Tonight I created a nandroid and for whatever reason when I was trying to restore it, it showed it was restored then when I tried to reboot system, the phone rebooted into bootloader mode. I could not reboot the phone it just kept cycling into bootloader mode no matter what I did.
I did not have internet, all I had was a copy of the most recent TWRP and a custom ROM zip. I recommend always keeping a copy of these files. At any rate, there's something wrong with TWRP. Initially I went into fastboot and just re-flashed TWRP. Still had problems. Then I used fastboot to erase recovery, then reflash via fastboot the copy I had then used adb pull to pull in the custom ROM into the sdcard and started up.
Has anyone else encountered this?
flash factory image,flash twrp and restore nandroid backup
I tried to boot into recovery to make a backup but TWRP has disappeared - no recovery whatsoever. Phone boots to system only. How can this have happened? I've been using Omni for the past month or so with no problems and updating every Sunday.
To recap, I have not done any modifications since the last opdate.Tried to boot into recovery and it is gone. Since only using Omini ROM I thought it was a ROM issue but no one in the Omni thread as been able to help so posting it here.
I can probably flash it again but am puzzled why is should just vanish.
The recovery might have got updated and the last update has overwritten TWRP, so it may be the cause of disappearance, but I'm not sure. You should've got standard recovery bundled with ROM.
And yes, just flash TWRP and it should work again. No need to flash Magisk or custom kernel, since you're on custom ROM.
Recovery partitions may have been corrupted. Try fastboot erase cache, and then fastboot flash recovery (TWRP). See if it boots into TWRP then.
TRWP installed again
Many thanks to all.
Recovery back! Still don't know why it disappeared.