Database Users

[Q] Recovery boot fail after updating to 4.1.2

Before the problem, I had a 4.1.1 rooted unlocked N7 with original ROM. I decided to apply the OTA update (03a4eaf95f73.signed-nakasi-JZO54K-from-JRO03D.03a4eaf9.zip) from TWRP recovery using the option to manually install zip updates.
The tablet rebooted, and I used Voodoo OTA RootKeeper to regain root access. Everything worked fine, I had no error messages at any moment during the procedure and the 4.1.2 update was applied successfully, as I could verify in the info section and by testing the landscape mode.
But, when I try to reboot in recovery using the option in ROM Manager, all I get is the little robot on his back image without any message. The only way to get out of this screen is to press the power button for a few seconds until it reboots into Android. Everything is fine except the recovery mode.
I tried to reflash the recovery image using Wug's Toolkit to no avail. I tried CWM, TWRP and stock recoveries but none worked. I always get the same screen with the robot on his back when I try to boot into recovery. Booting normally is always fine, only recovery seems to be affected. If I use Wug's toolkit to boot a temporary TWRP recovery image, it works but I want to be able to boot as before, with ROM Manager.
Any ideas? Is there a solution other the wipe it all and restart from scratch?
[edit] I can start into Fastboot but if I try to go to recovery from there, the same thing happens...

I fixed it by flashing the older 3.34 bootloader. So something is wrong with the new 3.41 bootloader.

There is nothing wrong with the process.
Its the users interpretation of how it works.
After updating, the file that flashes the stock recovery on boot is put back.
So he flashed in custom recovery.
Booted at which point the custom recovery is replaced with stock
Then wonders why he can't access custom recovery anymore.
Just reflash custom recovery
Sent from my HTC One X using xda app-developers app

bagofcrap24 said:
There is nothing wrong with the process.
Its the users interpretation of how it works.
After updating, the file that flashes the stock recovery on boot is put back.
So he flashed in custom recovery.
Booted at which point the custom recovery is replaced with stock
Then wonders why he can't access custom recovery anymore.
Just reflash custom recovery
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Not true. I flashed the update through cwm and everything went fine. When you reboot the system, cwm asks if you want to flash recovery and keep root. I denied to flash the stock recovery and I kept the root. After that you can't get into recovery at all (stock or cwm or whatever). but if I downgrade my bootloader to 3.34 everything is ok. I also installed new bootloader through cwm manually again and after that I can't boot into recovery.
Btw... How to flash bootloader.raw with fast boot???
Sent from my Nexus 7 using Tapatalk 2

sikagoon7 said:
I think you are a bit misinformed. When you flash the OTA the recovery-from-boot.p is installed by default. It resets the recovery to stock every time you reboot. CWM does nothing to remedy this. The only way to fix it is to remove or rename the file to disable its function. After and ONLY after this will you be able to flash recoveries by choice and boot into them.
And while it is your choice to use whatever recovery you desire I personnaly think using stock recovery and adb sideload is the safest when it comes to signed stock OTA.zips. After that you can root and flash your recovery of choice as if you have a brand new device.
When it comes to the bootloader. Stock system, boot, and recovery verify which bootloader you are using. JRO03D looks for 3.34 and JZO54K looks for 3.41. I don't know the implications of switching them but I don't think I will test that. I've already had a bad experience with dismantling a bootloader. The bootloader is an IMG file. Download the JRO03D factory image from Google's website and extract it. Inside will be a file named bootloader-grouper-3.34.img. THAT is the stock JRO03D bootloader and that is what you need to flash using: fastboot flash bootloader bootloader-grouper-3.34.img.
Click to expand...
Click to collapse
Yes I know that and did that from the beginning (renamed the file) but the point is that you can't boot into recovery (stock or whatever). It tries to boot into recovery I think but it reboots again and loads the OS. I'm using 3.34 booatloader with 4.12 and haven't got any probs yet.

Finally Got it Working
I tried one last thing yesterday. I got into ROM Manager and used the option to flash CWM Recovery. Then I rebooted in CWM (using the ROM Manager option). All was fine and when I chose the option to reboot, CWM asked me if I would like to make the custom recovery permanent because it would otherwise be rewritten at boot (this is what caused my problems, I believe). I choose to do so and it worked normally after that.
I then downloaded the TWRP recovery (http://www.teamw.in/project/twrp2/103) and installed it with Wug's Toolkit using the option to flash a permanent Recovery from a file. I didn't modify the "recovery-from-boot.p" file because I thought that CWM already did that. Tested booting into recovery again and all is finally OK with TWRP.
One of the benefits of the 4.1.2 update is that I can now boot into recovery from the Fastboot menu.

I'm in the same boat, ended up flashing the factory image for jz054k (which included the new bootloader) to try and fix.. now I'm without root and without a recovery..
I'm unlocked, but flashing alternative recoveries just doesn't work right now.. can't boot them up.
Did the original author ever get this resolved?
-m

diomark said:
I'm in the same boat, ended up flashing the factory image for jz054k (which included the new bootloader) to try and fix.. now I'm without root and without a recovery..
I'm unlocked, but flashing alternative recoveries just doesn't work right now.. can't boot them up.
Did the original author ever get this resolved?
-m
Click to expand...
Click to collapse
There are mixed reports on bootloader 3.41 and booting recovery. I have not been able to properly boot recovery from 3.41 under any circumstances. If you have this issue as well, flash the 3.34 bootloader from JRO03D. Doing this has allowed me to use recovery again.

I was running 4.1.2 with old bootloader 3.34 and had a SOD while my Nexus was charging last night.
In Faux123's kernel thread, he told me:
You should use the new boot loader and stick with CWM for now until TWRP get their stuff compatible with 4.1.2. Boot loader initialize the power regulators to some know state for the machine to boot until the kernel takes over.. and the new kernel is expecting it to be initialize certain ways... This was the biggest difference between 4.1.1 and 4.1.2... so I HIGHLY recommend using the matching bootloader...
Click to expand...
Click to collapse
Steps I had to take to get 4.1.2 (rooted, stock rom, custom kernel):
flash stock 4.1.1 boot.img and recovery.img
flash 4.1.1 bootloader 3.34
flash recovery TRWP recovery
flash SuperSU (regain root)
flash CWM lastest recovery 6.0.1.5 (beta) based on Faux123 advice above
flash 4.1.2 bootloader 3.41
No problems so far. This whole process has taken days...
I'm finally where I want to be.

Oops, wrong thread...

D802 Bricked. Please Help

While trying ti install CM 11 from TWRP i managed to brick the phone. I dont want to waste time sharing the details unless it's need to solve the problem. The main thing is that my phone is now stuck at the LG logo. Previously i was running the CM 10.2 Stable Build.
How can i get back to working condition? Either CM or Genuine LG Rom, I just want my phone to be up and running.
Please Help. I am really scared at this moment.

You don't share any details so I have to guess...
Enter recovery like this http://www.youtube.com/watch?v=ifi-ArGeTzQ , restore your Backup or flash another ROM, done.

muEcke* said:
You don't share any details so I have to guess...
Enter recovery like this http://www.youtube.com/watch?v=ifi-ArGeTzQ , restore your Backup or flash another ROM, done.
Click to expand...
Click to collapse
I can enter both the modes shown in the video.
The thing is i was running CM 10.2 with a TWRP installed of version 2.6.3.2. I downloaded the CM 11 and went into TWRp to flash it but it couldnt flash the CM11. Then after searching the net i found out that TWRP 2.6.3.3 or higher is required to install CM11. The problem is that i wiped my dalvic, data, cache and system and did not keep a backup. So when the Cm11 wont install i was stuck in the TWRP as i didn not have the 10.2 rom file in the phone.
Then downloaded the TWRP 2.6.3.3 and also a CWM zip (just in case). Using ADB i tried to update the TWRM but still some other error shows up. Tried installing the CWm still some error shows up. i tried installing again and this time the recovery asked me to install superuser (though i was rooted). I selected YES and after that i am boot looping in the lg logo.
Anyways thats basically what happened. Now how do i get further and make my phone work again?
Please help brother. I am in deep trouble.
Thank You

Man... always keep a backup, you know, just in case
Shouldn't be a problem at all. You have ADB access right? So here is TWRP 2.6.3.4 those are flashable ZIPs.
Push the file, flash with recovery, reboot to recovery again and you should be on 2.6.3.4. Then flash CM11 and you are good to go...
http://forum.xda-developers.com/showthread.php?t=2469995

muEcke* said:
Man... always keep a backup, you know, just in case
Shouldn't be a problem at all. You have ADB access right? So here is TWRP 2.6.3.4 those are flashable ZIPs.
Push the file, flash with recovery, reboot to recovery again and you should be on 2.6.3.4. Then flash CM11 and you are good to go...
http://forum.xda-developers.com/showthread.php?t=2469995
Click to expand...
Click to collapse
But I am stuck in the LG logo now as i mentioned. I cannot access custom recovery mode (as in TWRP).

in_core said:
But I am stuck in the LG logo now as i mentioned. I cannot access custom recovery mode (as in TWRP).
Click to expand...
Click to collapse
So you can't enter the recovery like shown in the video? And the command adb reboot recovery doesn't work either?

At this point your only option is to return back to stock and start over but with a recovery from the link I provided in the other thread.
http://forum.xda-developers.com/showthread.php?t=2432476
LG G2 Stock Firmware (Go Back to Stock)
Follow the instructions in this thread
Sent from my LG-LS980 using Tapatalk

hellot1M said:
At this point your only option is to return back to stock and start over but with a recovery from the link I provided in the other thread.
http://forum.xda-developers.com/showthread.php?t=2432476
LG G2 Stock Firmware (Go Back to Stock)
Follow the instructions in this thread
Sent from my LG-LS980 using Tapatalk
Click to expand...
Click to collapse
Ok then i will follow this process and hopefully be successful in getting my phone up and running.
Thanks for the help. Downloading 2Gb will take some time. So will post the result tomorrow.
Regarding rooting and installing custom recovery again, i will do that later. For now i just want my phone alive.
Anyways Thanks again everyone for the helpful information

Try getting to download mode right now. Because if you can't get to download mode you can't use the back to stock method
from my Note Thrizzle

Thanks everyone for the help and support. I have successfully reverted back to Stock LG Firmware.
I have some questions.
1. Do i have root access anymore?
2. Is my previous custom recovery still in my system?
3. If no for both then please help me with the appropriate article to root, install custom recovery and then install CM11, as my previous recovery was not able to install CM 11.
Thank You

[Q] problem with LG [email protected] recovery

I have installed android 5.0.2 Cynagenmod.
I tried to go back to cloudy g3 2.1 ( previously installed but no backup) via philz recovery.
I have recoveries installed cwm twrp and even philz.
Now whenever i try to go to recovery it says error boot certification verify.. Then if i long press power it will boot normally and works.
Problem is i cant go to recovery.. Cant flash.
i flashed kitkat baseband also.Tried Autorec app.. nothing working.
any suggestions plz.

shakirsuman said:
I have installed android 5.0.2 Cynagenmod.
I tried to go back to cloudy g3 2.1 ( previously installed but no backup) via philz recovery.
I have recoveries installed cwm twrp and even philz.
Now whenever i try to go to recovery it says error boot certification verify.. Then if i long press power it will boot normally and works.
Problem is i cant go to recovery.. Cant flash.
i flashed kitkat baseband also.Tried Autorec app.. nothing working.
any suggestions plz.
Click to expand...
Click to collapse
go to download mode, install KDZ (back to stock), use autorec

Unable to boot into recovery (lollipop i9505)

I have TWRP installed and I booted into recovery, backed up my rom and everything was fine. A few minutes later I tried booting into TWRP again but it only rebooted the phone. It shows booting recovery above the Samsung logo then reboots the phone. I used apps like quick boot but yet still reboots the phone

Have you tried turning it off and then booting into recovery with the key combo?

GDReaper said:
Have you tried turning it off and then booting into recovery with the key combo?
Click to expand...
Click to collapse
Yup, reboots back

Try reflashing recovery. Or flash a different version.

NeosHaruki said:
I have TWRP installed and I booted into recovery, backed up my rom and everything was fine. A few minutes later I tried booting into TWRP again but it only rebooted the phone. It shows booting recovery above the Samsung logo then reboots the phone. I used apps like quick boot but yet still reboots the phone
Click to expand...
Click to collapse
Did you root it at first ? If not do so ,i also had that issue and was solved by rooting,normally root is not required for Flashing TWRP but still...

The same problem... I think the rom issue

Flash the latest stock ROM and try to enter recovery.

TWRP recover unresponsive after OTA update

I'm running Optimized CyanogenMod 12.1 rom from the Jflte DevConnection Team.
After trying to flash the last OTA update for the rom my TWRP recovery has become unresponsive, stuck on its boot screen (TWRP logo).
What happen was that I downloaded the update via the OTA app and then pressed the Install button to reboot the device and flash the update.
But after the device booted into the recovery TWRP never opened up a process window or its menu but just stayed on the boot screen appearing to do nothing. It did not respond to any commands (buttons or touch). I waited half an hour before forcing a shot down.
But at this point I was in a manual boot loop, the device would boot into recovery instead of the Rom and I was unable to use the phone.
I managed to flash TWRP again using Heimdall which allowed me to boot again into the Rom, but if I tried manually going into recovery it was still unresponsive.
I tried flashing older version of TWRP using Flashy app, I clicked on a option in the app to reboot into recovery. This cost the origin boot loop problem again.
I than flashed CyanogenMod Recovery and was able to boot into that.
Tried once more to flash TWRP but the problem persists.
Anybody that could know what is going on or how to fix this issue. I'm hoping not to have to format the phone to Stock to fix this.

I had same issue with TWRP in the past and never found a solution, to run into the ROM directly and escape the loop thing try
Power Button and volume -
Then continue and it will boot up normally.
I had to change to Clockwork-mod recovery after this.

einsiol said:
I'm running Optimized CyanogenMod 12.1 rom from the Jflte DevConnection Team.
After trying to flash the last OTA update for the rom my TWRP recovery has become unresponsive, stuck on its boot screen (TWRP logo).
What happen was that I downloaded the update via the OTA app and then pressed the Install button to reboot the device and flash the update.
But after the device booted into the recovery TWRP never opened up a process window or its menu but just stayed on the boot screen appearing to do nothing. It did not respond to any commands (buttons or touch). I waited half an hour before forcing a shot down.
But at this point I was in a manual boot loop, the device would boot into recovery instead of the Rom and I was unable to use the phone.
I managed to flash TWRP again using Heimdall which allowed me to boot again into the Rom, but if I tried manually going into recovery it was still unresponsive.
I tried flashing older version of TWRP using Flashy app, I clicked on a option in the app to reboot into recovery. This cost the origin boot loop problem again.
I than flashed CyanogenMod Recovery and was able to boot into that.
Tried once more to flash TWRP but the problem persists.
Anybody that could know what is going on or how to fix this issue. I'm hoping not to have to format the phone to Stock to fix this.
Click to expand...
Click to collapse
look at the twrp thread... i posted a fixed twrp there (look at last 2 pages)
try that one
Sent from my Xperia T using XDA Free mobile app

SdtBarbarossa said:
look at the twrp thread... i posted a fixed twrp there (look at last 2 pages)
try that one
Sent from my Xperia T using XDA Free mobile app
Click to expand...
Click to collapse
All I could find was recovery for I9305, is that one you ment? I tried it out but was not able to reboot into that.
But I tried now using the dd to flashed version 2.8.4 and got it to work finally.
dd if=/sdcard/twrp.img of=/dev/block/mmcblk0p21
Found this option on the TWRP page for I9505

einsiol said:
All I could find was recovery for I9305, is that one you ment? I tried it out but was not able to reboot into that.
But I tried now using the dd to flashed version 2.8.4 and got it to work finally.
dd if=/sdcard/twrp.img of=/dev/block/mmcblk0p21
Found this option on the TWRP page for I9505
Click to expand...
Click to collapse
i meaned the one i posted in s4 twrp page :-O NOT i9305 (wich is s3lte not s4)
Sent from my Xperia T using XDA Free mobile app