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.
Newbie to the 'Dark Side of the Android World' and just curious.
well, after rooting your phone you only need to flash custom recovery once then you can access it as many times as you want
Your question is a little bit weird. Can you link me to a place of reference? Or at least explain what you are actually wanting to do?
Flashing TWRP is a one-time action, once flashed it remain on your Xperia SP. However, FlashTool doesn't offer flashing TWRP to other partitions via fastboot other than the "boot" partition. So far, the only way to correctly flash TWRP is via a recovery.
If you indeed flashed TWRP image via FlashTool, then you are actually putting TWRP into your boot partition, and this makes your device to only boot into TWRP infinitely until you flash a ROM (which will of course again override the boot partition).
The reason why I asked is because this method of accessing recovery is posted in my custom ROM guide, so I want to know if you get this kind of idea from my guide.
Thanks
I unlocked boot loader and tried to install twrp from system,it says its installed but i cant enter it
How to flash twrp the best way
And can i remove twrp if i need to restore factory state and how to delete it?
Thank you
You could always try XperiaZdual-recovery, as long you don't flash another kernel. Its actually a tool that can help you flash the recovery (if not rooted yet, you must be on 5.0.2) using only a one-click solution. It does not give you root access and you should allow usb debugging in order to be able to flash. It installs TWRP and Philz recovery, during boot you can select either one of them using volume down for the first and volume up for the latter. Have fun.
How to remove twrp from xperia xz(f8332)
Hi there, I am currently running B383 on my P9, and really want to root it. However when I do, will I still be able to get future updates to the software? Do I need to unroot and lock bootloader first?
Also when the bootloader is unlocked, a message is displayed at boot about your phone being unsecured and non-trustworthy, is it possible to remove this message? (I used to have a moto g with an unlocked bootloader, and I flashed some file to remove the warning).
Thanks
I don't think there is a way to remove that message every time the phone is turned on. Mine does that too as I've unlocked the bootloader.
Did you unlock the bootloader yet? Because when you need to unlock it, the phone will basically be factory reset when bootloader is switched from locked to unlock (vice-versa).
And for OTA updates the best way is to do it manually, downloading the MV-PV file via Huawei Firmware finder (Full PV file which contains two files update.zip and hweu..zip, update.zip (system firmware) is flashed first then hweu.zip (The system apps).
You will need a custom recovery. The one you will need to use is TWRP (This one specifically - twrp-3.1.1-0-eva.img) to flash OTA's via custom recovery (To repeat you flash update.zip first then hweu.zip) You can ignore the errors if it prints any while flashing the OTA files as I did the same and it worked fine no problem.
When you want to root your phone, make sure to flash 'SuperSU-v.2.82-EMUI5-SELEnforcing.zip' via TWRP recovery to root your phone.
For the other questions, you do not need to unroot the phone to install the OTA updates. The phone will just unroot itself when the OTA update is flashed onto phone. You simply just need to re-root it again by re flashing the SuperSU zip as mentioned above.
When you need to boot the custom TWRP recovery you need to turn the phone off and hold power + volume up until Huawei Logo / text is displayed you must release both keys immediately after 0.5-1 second which is a short time frame to get the phone to boot to custom recovery or else it will boot the Huawei eRecovery instead.
SuperSU here: https://forum.xda-developers.com/p9/development/root-supersu-2-81-emui-5-t3612258
TWRP here: https://forum.xda-developers.com/p9/development/twrp-t3565703
Best to follow the instructions from those links. The information above is to guide you through the processes.
..
benjamen50 said:
I don't think there is a way to remove that message every time the phone is turned on. Mine does that too as I've unlocked the bootloader.
Did you unlock the bootloader yet? Because when you need to unlock it, the phone will basically be factory reset when bootloader is switched from locked to unlock (vice-versa).
And for OTA updates the best way is to do it manually, downloading the MV-PV file via Huawei Firmware finder (Full PV file which contains two files update.zip and hweu..zip, update.zip (system firmware) is flashed first then hweu.zip (The system apps).
You will need a custom recovery. The one you will need to use is TWRP (This one specifically - twrp-3.1.1-0-eva.img) to flash OTA's via custom recovery (To repeat you flash update.zip first then hweu.zip) You can ignore the errors if it prints any while flashing the OTA files as I did the same and it worked fine no problem.
When you want to root your phone, make sure to flash 'SuperSU-v.2.82-EMUI5-SELEnforcing.zip' via TWRP recovery to root your phone.
For the other questions, you do not need to unroot the phone to install the OTA updates. The phone will just unroot itself when the OTA update is flashed onto phone. You simply just need to re-root it again by re flashing the SuperSU zip as mentioned above.
When you need to boot the custom TWRP recovery you need to turn the phone off and hold power + volume up until Huawei Logo / text is displayed you must release both keys immediately after 0.5-1 second which is a short time frame to get the phone to boot to custom recovery or else it will boot the Huawei eRecovery instead.
SuperSU here: https://forum.xda-developers.com/p9/development/root-supersu-2-81-emui-5-t3612258
TWRP here: https://forum.xda-developers.com/p9/development/twrp-t3565703
Best to follow the instructions from those links. The information above is to guide you through the processes.
Click to expand...
Click to collapse
Thanks for the quality answer, I have no doubts anymore!
Solution: Not sure why or how, but I got it to actually boot into the new system that I flashed. Now all is good and working as it should
So rooted stock ROM, but with TWRP, unlocked boot loader and USB debugging enabled... I'm No stranger to flashing custom ROMs in TWRP and flashing stock ROMS longhand by fastboot commands.
Using MacOS with latest platform-tools...
So today I decided to flash resurrection remix. Downloaded it to storage as usual for flashing via TWRP, flashed it successfully. Only it would not boot. It started going to the stock boot screens and said it could not decrypt... or something.
Anyway where I am right now is that I can boot into TWRP or boot loader just fine. But in boot loader I can't get get it to see my phone using
Code:
./adb devices
Only... for some reason in TWRP if I do ./adb devices, it sees my phone and reports back the correct device ID.
What now? I want to flash back to stock again, but I don't know how to flash line by line without being in boot loader. But in boot loader I can't see the phone?
I know there has to be hope if I can see it in TWRP. But I have no system I can boot to.
-Peter
Great that it works for you now.
For what it's worth, I think that the reason it didn't boot was that the stock rom had encrypted your phone. Current custom roms unfortunately use a different encryption, so that the whole data partition needs to be formatted. I assume that's what you ended up doing.
As to the bootloader, it was never intended to work with adb, only with fastboot.