Related
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...
Guys I know there are a ton of threads with this problem but no matter what I try, i'm still stuck on a boot loop.
So basically I had PA Rom 3.99 RC2 on my nexus and everything was fine. I then tried to flash PA AOSP kit kat build
but my phone would not boot so I went with a factory image occam 4.3 Phone booted and all was good. I was liking the
stock experience and then about 4 days later after a reboot, phone got stuck on the boot animation X. It would not get out of it
so I decided to flash PA Rom 3.99 rc2 again via ADB push zip. factory reset, installed the rom and gapps, wiped caches and thought i was good to go. Well the phone again would not get past the boot animation of PA.
i then decided to go with the Factory image occam 4.3 via fastboot and installed it and everything. Again stuck on the X. So then I tried PSX rom 4.3 again via adb push, did my factory reset and flashed the rom and gapps and superSu. Also got stuck on the boot animation. Left it for over 2 hours bootlooping and nothing.
Going crazy I went and fastboot the 4.2.2 JDQ39 img and downgraded bootloader, baseband. Installed it and again, stuck on the X animation. just hangs there.
Any help? i don't know what else to try, currently using my HD2 and it is sooo slow :cyclops:
Make sure to use latest cwm recovery. Avoid using twrp recovery. Use the toolkit and flash stock image. It will wipe everything in the phone but it will fix it.
Sent from my Nexus 4 using Tapatalk
badboy47 said:
Make sure to use latest cwm recovery. Avoid using twrp recovery. Use the toolkit and flash stock image. It will wipe everything in the phone but it will fix it.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Thanks for the suggestion but still nothing. Updated CWMR to 6.0.4.3 and tried the 4.3 stock image. Still hangs on bootup. android file transfer recognizes the device is plugged in via usb but just gives me the error "could not connect to device"
Oh man I don't know what's wrong with my nexus
bump bump
I'm having this same issue, and it happened just like you. I flashed CM 10.2 nightly 20131114 this morning and I tested it to make sure everything was working. I decided to reboot the phone, and after that I keep getting stuck at the boot animation no matter what I did. To no avail, I reflashed a working zip, restored a backup, restored another backup, flashed the 4.4 factory image (wiping the entire phone), the 4.3 factory image, and then I read that the 4.2 baseband can fix it, so I flashed the 4.2 factory image. That 4.2 image gets it to boot, but without baseband. Right now I'm trying different radios just to see if I can get service again. If it matters, I was running the hybrid 33/84 radio for T-Mobile's LTE when this happened. Very, very peculiar situation here. I've never had anything like this happen, and especially remain an issue after wiping the entire device. I'm hoping it's not a sudden hardware issue.
i jst flash factory image of 4.4 n nw my phone is stuck o the boot animation screen plz help
Hmmy 4444 said:
i jst flash factory image of 4.4 n nw my phone is stuck o the boot animation screen plz help
Click to expand...
Click to collapse
just re-flash 4.2, it'll work. I've been doing that since Monday. but I want kitkat too!!
my device is stuck on the boot animation too. is there a way to reinstall the default 4.3 recovery and just rerun the update or something basic like that? my device was almost at stock before running the update. the only two things: twrp and rooted via recovery. so i thought everything will work fine and now there is no backup...
badboy47 said:
Avoid using twrp recovery.
Click to expand...
Click to collapse
Why?
Just fastboot flash all the image files (boot.img,recovery.img....) from the factory image.
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!
I was between roms, was testing out MIUI 8 before going back to Pure Nexus. After wiping I flashed pure nexus vendor img (nbd90x) and then the rom and gapps. I try to boot afterward and I just keep bootlooping from the google logo. I went back and used a 6.0 vendor img (mtc20l) and I'm able to boot into the rom but receive the message to flash the correct vendor img. But I can't since the phone won't boot with the vendor img I'm supposed to be using! I also tried using the stock image for 6.0 and 7.0 from google and neither of them are booting now. Is there something I should do differently or any other steps I can take?
Odd
DreamJohn said:
I was between roms, was testing out MIUI 8 before going back to Pure Nexus. After wiping I flashed pure nexus vendor img (nbd90x) and then the rom and gapps. I try to boot afterward and I just keep bootlooping from the google logo. I went back and used a 6.0 vendor img (mtc20l) and I'm able to boot into the rom but receive the message to flash the correct vendor img. But I can't since the phone won't boot with the vendor img I'm supposed to be using! I also tried using the stock image for 6.0 and 7.0 from google and neither of them are booting now. Is there something I should do differently or any other steps I can take?
Click to expand...
Click to collapse
Hmm I just did what u did came from miui v8 to pure nexus and I didn't bootloop running the same vendor.
DreamJohn said:
I was between roms, was testing out MIUI 8 before going back to Pure Nexus. After wiping I flashed pure nexus vendor img (nbd90x) and then the rom and gapps. I try to boot afterward and I just keep bootlooping from the google logo. I went back and used a 6.0 vendor img (mtc20l) and I'm able to boot into the rom but receive the message to flash the correct vendor img. But I can't since the phone won't boot with the vendor img I'm supposed to be using! I also tried using the stock image for 6.0 and 7.0 from google and neither of them are booting now. Is there something I should do differently or any other steps I can take?
Click to expand...
Click to collapse
Factory reset and wipe system in TWRP then try again. Then download the PN 7.0 zip if you still bootloop. I'm guessing you are referring to PN 7.0. If not, fastboot flash the vendor that matches the PN 6.0.1 base.
Sent from my Nexus 5X using Tapatalk
Already been unlocked and running pure nexus for a while, during flashing paranoid android I ran into some trouble and tried to reboot into TWRP, it did not load into TWRP because I forgot to flash the recovery again the last time before rebooting, no biggie.
I fastboot boot TWRP.img from my PC and then flashed rc2 zip from my internal storage, restore my backup and reboot. No luck, I get sent right back to TWRP every time and it never ask me to decrypt my partition.
So now I'm stuck with and encrytpted partition that I can't access, and even trying to fastboot boot TWRP and then flash rc2 from OTG is not fixing the issue, sends me right back to TWRP without decrypt prompt no mater if I choose power off, reboot, bootloader.
I can get to boot loader running adb bootloader from cli.
I'm not sure what to do from here, am I really bricked?
Any help is really appreciated.
Thank you.
Just try to flash TWRP, reboot recovery only, then go to wipe, advanced, and format internal storage, wipe everything once more and restore and boot your nandroid. RC2 has issues with restoring nandroid by the way, use RC1. You probably just have corrupt storage.
It's not possible to fastboot boot twrp and install twrp when you are not on stock boot on both slots. This will always leeds you to a twrp bootloop.
Just fastboot stock boot to slot a and b and then install twrp again and you should be fine.
mikaole said:
It's not possible to fastboot boot twrp and install twrp when you are not on stock boot on both slots. This will always leeds you to a twrp bootloop.
Just fastboot stock boot to slot a and b and then install twrp again and you should be fine.
Click to expand...
Click to collapse
I just did the same darn thing. I was trying to flash PN July update and I always knock it out no problem. However, for some reason, I rebooted right after flashing the July PN and forgot to reflash twrp. I'm rebooted into the ROM, but how do I get twrp recovery back on the device?
whodatfan said:
I just did the same darn thing. I was trying to flash PN July update and I always knock it out no problem. However, for some reason, I rebooted right after flashing the July PN and forgot to reflash twrp. I'm rebooted into the ROM, but how do I get twrp recovery back on the device?
Click to expand...
Click to collapse
The same way you got it on there the first time....
I booted RC1 and flashed RC2. I mistyped fastboot an it failed first go. Lol
Sent from my Pixel XL using Tapatalk
boostedduece said:
Already been unlocked and running pure nexus for a while, during flashing paranoid android I ran into some trouble and tried to reboot into TWRP, it did not load into TWRP because I forgot to flash the recovery again the last time before rebooting, no biggie.
I fastboot boot TWRP.img from my PC and then flashed rc2 zip from my internal storage, restore my backup and reboot. No luck, I get sent right back to TWRP every time and it never ask me to decrypt my partition.
So now I'm stuck with and encrytpted partition that I can't access, and even trying to fastboot boot TWRP and then flash rc2 from OTG is not fixing the issue, sends me right back to TWRP without decrypt prompt no mater if I choose power off, reboot, bootloader.
I can get to boot loader running adb bootloader from cli.
I'm not sure what to do from here, am I really bricked?
Any help is really appreciated.
Thank you.
Click to expand...
Click to collapse
Just flash a factory image and start over.