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...

[Q] Stock Recovery for 4.2.2?

In this thread I got a great answer about how to fix a sizing problem with the data partition on my Razr M. You'll need this if you are running CMod, are encrypting, reformat your data partition with TWRP, and want to re-encrypt after the reformat.
There is only one silly problem. I am running CM 10.1, which is 4.2.2. I am also running TWRP 2.6. I can change versions of TWRP as easy as anything, but I cannot for the life of me figure out how to return to stock recovery. I really do not want to RSD, since Motorola has been working on how to relock the bootloader, and I don't want to give them that chance. And, of course, if I do RSD back to 4.2.2 stock, I'll have no way to get root back.
What I'd love to do is just to get the 4.2.2 stock recovery image, and flash it with fastboot. But I cannot for the life of me find the 4.2.2 stock recovery image. I have Matt's 4.1.2 stock recovery image, and I actually tried it with his utility, but...yeah. Android with exclamation point. It did not end well.
So, here's the question: is there any way to flash the 4.2.2 stock recovery without RSDing back to stock? Where is that darn disc image?
Thanks!

Brokkn said:
In this thread I got a great answer about how to fix a sizing problem with the data partition on my Razr M. You'll need this if you are running CMod, are encrypting, reformat your data partition with TWRP, and want to re-encrypt after the reformat.
There is only one silly problem. I am running CM 10.1, which is 4.2.2. I am also running TWRP 2.6. I can change versions of TWRP as easy as anything, but I cannot for the life of me figure out how to return to stock recovery. I really do not want to RSD, since Motorola has been working on how to relock the bootloader, and I don't want to give them that chance. And, of course, if I do RSD back to 4.2.2 stock, I'll have no way to get root back.
What I'd love to do is just to get the 4.2.2 stock recovery image, and flash it with fastboot. But I cannot for the life of me find the 4.2.2 stock recovery image. I have Matt's 4.1.2 stock recovery image, and I actually tried it with his utility, but...yeah. Android with exclamation point. It did not end well.
So, here's the question: is there any way to flash the 4.2.2 stock recovery without RSDing back to stock? Where is that darn disc image?
Thanks!
Click to expand...
Click to collapse
In my goodies. Stock recov & a prerooted restore method!

Many thanks for the stock recovery. I installed it using Minimal Fastboot and ADB,
Code:
fastboot flash recovery recovery.img
When I reboot into recovery, I get the green dead android. I re-flashed TWRP 2.6, no problem. What's the catch here?
The only thing I can think of: I did not flash the .zip file from TWRP, but extracted it, got the disc image, and then installed it through Minimal Fastboot and ADB. Is that going to make any difference?
Thanks!

Brokkn said:
Many thanks for the stock recovery. I installed it using Minimal Fastboot and ADB,
Code:
fastboot flash recovery recovery.img
When I reboot into recovery, I get the green dead android. I re-flashed TWRP 2.6, no problem. What's the catch here?
The only thing I can think of: I did not flash the .zip file from TWRP, but extracted it, got the disc image, and then installed it through Minimal Fastboot and ADB. Is that going to make any difference?
Thanks!
Click to expand...
Click to collapse
Normally when you boot into stock recovery , you wont be presented with a nice menu. It's almost a hidden menu that you have to pull up...
When you go in and get the Triangle or whatever is there, you will have to press volume + and - and power button to get the menu to display.
Try a few combinations, volume + and - then power, or power then + and -, or all three at the same time. Eventually it will come up.

Brokkn said:
Many thanks for the stock recovery. I installed it using Minimal Fastboot and ADB,
Code:
fastboot flash recovery recovery.img
When I reboot into recovery, I get the green dead android. I re-flashed TWRP 2.6, no problem. What's the catch here?
The only thing I can think of: I did not flash the .zip file from TWRP, but extracted it, got the disc image, and then installed it through Minimal Fastboot and ADB. Is that going to make any difference?
Thanks!
Click to expand...
Click to collapse
I was going to offer the xt897 stock recovery. It glides into action & has apply from cache. In goodies also.

MF3 CWM not overwriting TWRP

I have a rooted MF3 to which I flashed CWM, but in seeing that it wouldn't let me do anything besides wipe data/factory reset I flashed TWRP. When I booted into recovery on TWRP I would get stuck with it saying "DOWNLOADING" and would bootloop back into TWRP recovery unless I restarted by hitting vol down + power + home button, then hitting cancel. Once I was able to get it to boot normal I figured I would reflash CWM, but once I flashed CWM and attempted to boot into recovery it would always boot into the stuck TWRP recovery. I am under the impression that since there is no stock rom I can flash, if I even had a means to flash, to get back to the stock recovery.
So my question is does anybody have an idea of how I might get CWM to properly flash over TWRP, since flashing with rom manager doesn't seem to work.

You shouldn't be trying to flash any recoveries what so ever considering you have a stock mf3 firmware. You definitely don't want to cause more damage.
Sent from my GT-I9505G using Tapatalk 2

A best buy Samsung experience booth would be your best bet if you need to go to stock, they can reflash mf3 firmware
Sent from my SAMSUNG-SGH-I337 using xda app-developers app

Mortorojo said:
I have a rooted MF3 to which I flashed CWM, but in seeing that it wouldn't let me do anything besides wipe data/factory reset I flashed TWRP. When I booted into recovery on TWRP I would get stuck with it saying "DOWNLOADING" and would bootloop back into TWRP recovery unless I restarted by hitting vol down + power + home button, then hitting cancel. Once I was able to get it to boot normal I figured I would reflash CWM, but once I flashed CWM and attempted to boot into recovery it would always boot into the stuck TWRP recovery. I am under the impression that since there is no stock rom I can flash, if I even had a means to flash, to get back to the stock recovery.
So my question is does anybody have an idea of how I might get CWM to properly flash over TWRP, since flashing with rom manager doesn't seem to work.
Click to expand...
Click to collapse
As said, the samsung booth at best buy is your only choice right now. mf3 phones are bootlocked.. flashing recovies = killed phone (unless the before mentioned booth can help you out).

Lack of recovery

Hey guys, I'm a longtime XDA browser but hardly ever post. I have the MXPE rooted with the newest TWRP build and has been running great since I got it. last night flashed the Deodexed 6.0 build from AICPs 5.1.1. I had some issues with the SD card being mounted as internal storage and erasing something so I tried to flash back to stock as my nandroids weren't seen as usable.
Long story short when I flashed back to stock, the recovery would never take. I've flashed the stock recovery and twrp to no avail. For some reason it wont actually stick. Everything else is back to stock but that. When I used the win toolkit and tried to flash twrp again it said something about the folder locations so I'm wondering if I messed something in the partitions.
Question is, have you guys ran into this issue or have any insight on where to go from here? I've looked around but I couldn't find a post that the same as this issue. As a side note, I can get into the bootloader just fine.
I appreciate any info that someone can provide.

Flash twrp. Reboot back to recovery from recovery. Reboot system.
Hopefully it's that easy. Stock os flashes stock recovery on boot. Rebooting recovery from recovery prevents that from happening.
From TWRP:
"Note many devices will replace your custom recovery automatically during first boot.... Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install."
mxpe 6.0

Thanks for the info ffejy462. What happens when I try to flash TWRP and it doesnt stick? I know for a fact that I can boot into it temporarily with fastboot boot and the recovery file. Should I just flash it from there?

THEFILLTER said:
Thanks for the info ffejy462. What happens when I try to flash TWRP and it doesnt stick? I know for a fact that I can boot into it temporarily with fastboot boot and the recovery file. Should I just flash it from there?
Click to expand...
Click to collapse
I'm sorry I didn't see this sooner. Flash recovery with fastboot. Boot into recovery. From reboot menu in recovery, select reboot recovery. Twrp will patch so recovery isn't lost again.
mxpe 6.0

That did it. thanks alot ffejy462!

Flashing TWRP not working after updating EMUI

I updated the EMUI version on my ALE-L02 from 3.1 to 4.1 using TWRP recovery. The disadvantage of this is that I lost TWRP afterwards as it was replaced by the stock recovery.
I tried to flash TWRP to the phone again using ADB, which said that the flash was successful. However, when rebooting into recovery mode, it boots into the stock recovery. Why is it doing this/how do I fix it?

You need to follow the instructions to get TWRP to boot after install. https://forum.xda-developers.com/showpost.php?p=71429023&postcount=73

JpegXguy said:
You need to follow the instructions to get TWRP to boot after install. https://forum.xda-developers.com/showpost.php?p=71429023&postcount=73
Click to expand...
Click to collapse
Thanks! Will try later on

mackelbot said:
I updated the EMUI version on my ALE-L02 from 3.1 to 4.1 using TWRP recovery. The disadvantage of this is that I lost TWRP afterwards as it was replaced by the stock recovery.
I tried to flash TWRP to the phone again using ADB, which said that the flash was successful. However, when rebooting into recovery mode, it boots into the stock recovery. Why is it doing this/how do I fix it?
Click to expand...
Click to collapse
Try just pressing vol. up+ power, that happened to me sometimes. Also, as a tip, when flashing EMUI from TWRP first backup recovery than flash it. After that, don't reboot, go back and restore the recovery. Much easier for me.