Related
I had to do a complete wipe from the computer and flashed clockwork mod recovery. Since it was likely an old version I had the double 0 partition problem which I fixed by manually moving the files. I tried to update the recovery to twrp, but it won't flash using goomanager. It downloads and says it's flashed but it's not there.
I also seem to have a weird problem where I have to push the power button to get it to boot past the Google screen. If I don't push power it gets stuck there forever.
Any ideas?
Sent from my Galaxy Nexus using Tapatalk 4
Follow the sticky at the top that says flashing a factory ROM using fastboot/return to stock. Start from scratch, get it working, and then flash whatever you want.
Sent from my Nexus 7(2012) that has zero issues.
SlowCobra96 said:
Follow the sticky at the top that says flashing a factory ROM using fastboot/return to stock. Start from scratch, get it working, and then flash whatever you want.
Sent from my Nexus 7(2012) that has zero issues.
Click to expand...
Click to collapse
That's what I did, that's why I'm stuck on the old recovery.
Sent from my Nexus 7 using Tapatalk 4
T-Keith said:
That's what I did, that's why I'm stuck on the old recovery.
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
This might be an odd question, but have you tried just updating CWM first, and THEN flashing TWRP? Sometimes the flash won't go smoothly with an older version of one recovery to a newer version of a different recovery- not sure why, but that's just been my experience. I would update CWM first then try flashing TWRP.
Also, if goo is not working for you, you could try Rom Manager to update CWM and then flash TWRP. It can flash either. (If you really want to flash via the device).
Otherwise, (me personally) I'd just use adb fastboot to flash a new recovery.
Hope that helps
Thanks I will try that.
Sent from my Galaxy Nexus using Tapatalk 4
T-Keith said:
Thanks I will try that.
Sent from my Galaxy Nexus using Tapatalk 4
Click to expand...
Click to collapse
No problem. Let us know how it works out for you.
Tried flashing with fastboot, now it won't boot into recovery, just hangs at the Google logo.
Still needs a bump from the power button to get it to boot normally.
Sent from my Galaxy Nexus using Tapatalk 4
T-Keith said:
Tried flashing with fastboot, now it won't boot into recovery, just hangs at the Google logo.
Still needs a bump from the power button to get it to boot normally.
Sent from my Galaxy Nexus using Tapatalk 4
Click to expand...
Click to collapse
Ahh, that sucks! How are you *attempting to* access recovery... via reboot menu, via adb, or via 3-button press? It shouldn't matter, but you could try all three methods to see if any way will give you recovery access. Then, if/when you manage to get in, you could reflash again straight from recovery. I'm going to do some digging to see if I can find a better solution. I KNOW I've read about the same issue before, I know there's a solution... I just have to find it again.
Worse comes to worse, you might have to reflash stock recovery then reflash custom recovery. Might be a corrupt recovery img, but I will check and try some things out and let you know what I find.
Edited to add:
Yes. there was a bug in the older bootloader that bypassed/refused access to recovery... so since you restored stock, you probably need to update your bootloader to at least to version 4.18 (via fastboot). THEN you should be able to access recovery. I can't add links, but I can give you a text link once I find just the IMG file instead of the full firmware. Honestly, I never do backups so I don't have the file on hand. However, I may do one backup at least so I can extract my boot img and give it to you.
OK, so I found the info I was looking for.
From Elsewhere:
Steps:
Install latest nexus 7 bootloader.
This fixes the boot loader bug and now you can enter recovery from the bootloader screen.
Update the bootloader to at least 3.18. Make sure NOT TO DELETE THE BOOTLOADER!!!!!!!!!!!!!
I cannot emphasize this enough!!!!!!!!!!! I bricked my first one this way.
Use
fastboot flash bootloader C:\>>>>>>\bootloader-grouper-3.18.IMG***
Click to expand...
Click to collapse
Do NOT erase bootloader before you flash the new one. And after you have flashed the new one type;
fastboot reboot bootloader
Click to expand...
Click to collapse
and check the bootloader version to make sure you succeeded.
Click to expand...
Click to collapse
***Or whatever you name the boot img file!***
https://dl.dropboxusercontent.com/u/19608328/boot.img.zip --> This is from MY Nexus 7. It's Bootloader version 4.23, and works with JB 4.2.2- it does NOT have the recovery access bug.
https://dl.dropboxusercontent.com/u/19608328/recovery.img.zip --> This is a copy of MY CWM, which I just updated to 6.0.3.6 yesterday.
I'd flash the bootloader, then flash your recovery of choice. Not being able to access recovery is a bootloader issue, not a recovery issue. The fact that you restored/reverted an older full firmware put you on an older bootloader that would not allow users to access recovery.
Try the new(er) bootloader, it should work. My device is a 16gb grouper Nexus 7 running 4.2.2. Before that, it ran 4.1.2 without any issues, so it should work to resolve the problem you're having.
I was running 4.4.3 Rooted with TWRP recovery. Bootloader was unlocked.
I accepted the 4.4.4 OTA update and when it was done I found I lost root.
Tried to go into recovery to install Supersu.zip but had also lost TWRP.
Just got the dead android with the ! mark.
My Boot loader is still unlocked. I ran fastboot. Verified that I got a device id with Fastboot devices.
Then used Fastboot to install openrecovery-twrp-2.6.3.1-manta.img
Completed with no errors. Rebooted the device and then shut it down.
Rebooted into Fastboot, selected recovery and I still get the dead Android with the ! mark.
What did I do wrong?
Len
If you want to stay stock here you go. Look at the last page or so and it also has a link to the newest TWRP which you need to get going again.
http://forum.xda-developers.com/showthread.php?t=2529492
sfobrien said:
If you want to stay stock here you go. Look at the last page or so and it also has a link to the newest TWRP which you need to get going again.
http://forum.xda-developers.com/showthread.php?t=2529492
Click to expand...
Click to collapse
No, I don't want to stay stock. I want to be able to install TWRP so I can flash SuperSu.zip and get root back. When I do a fast boot install of the TWRP Image, it completes with no errors but when I reboot into recovery, I get the dead Android with the exclamation point not TWRP
Lenster45 said:
No, I don't want to stay stock. I want to be able to install TWRP so I can flash SuperSu.zip and get root back. When I do a fast boot install of the TWRP Image, it completes with no errors but when I reboot into recovery, I get the dead Android with the exclamation point not TWRP
Click to expand...
Click to collapse
Since you took the OTA your bootloader may be locked. After you get it unlocked I gave you where to get the recovery you need, the one you have is not KitKat friendly.
Lenster45 said:
I was running 4.4.3 Rooted with TWRP recovery. Bootloader was unlocked.
I accepted the 4.4.4 OTA update and when it was done I found I lost root.
Tried to go into recovery to install Supersu.zip but had also lost TWRP.
Just got the dead android with the ! mark.
My Boot loader is still unlocked. I ran fastboot. Verified that I got a device id with Fastboot devices.
Then used Fastboot to install openrecovery-twrp-2.6.3.1-manta.img
Completed with no errors. Rebooted the device and then shut it down.
Rebooted into Fastboot, selected recovery and I still get the dead Android with the ! mark.
What did I do wrong?
Len
Click to expand...
Click to collapse
Well, you didn't do anything wrong per se. When you flash the OTA (which I assume you did in TWRP), you lose root and your custom recovery since it replaces it with stock. You did the right thing by fastboot flashing your custom recovery back. However, the only thing you did "wrong" was rebooting into the Android OS instead of booting into the newly flashed recovery first. After you flash the custom recovery, select the recovery option in the bootloader, and it will boot into your custom recovery. If you don't boot directly into your custom recovery, and instead boot into the OS, the recovery will revert back to stock, which is why you saw the dead Android with the ! mark (that is the stock recovery). Just fastboot flash TWRP again, and boot straight into it. Then, just flash the SuperSU zip and reboot system. You should be good to go.
EDIT: Oh, and having an unlocked bootloader has no effect on receiving an OTA or your ability to flash it. If your bootloader was unlocked before flashing an OTA, it will remain unlocked. The only way it would become locked again is if you locked it yourself. You can even completely flash the stock image, and the bootloader will remain unlocked.
charesa39;53763629
EDIT: Oh said:
Strange, had a friend who took the OTA awhile back and it locked the bootloader. It was a JB version maybe they changed it with KitKat ? ( he could have locked it prior to my getting it going who knows) Thanks for the info, have never used an OTA since I got my N10 when it first came out.
Click to expand...
Click to collapse
charesa39 said:
Well, you didn't do anything wrong per se. When you flash the OTA (which I assume you did in TWRP), you lose root and your custom recovery since it replaces it with stock. You did the right thing by fastboot flashing your custom recovery back. However, the only thing you did "wrong" was rebooting into the Android OS instead of booting into the newly flashed recovery first. After you flash the custom recovery, select the recovery option in the bootloader, and it will boot into your custom recovery. If you don't boot directly into your custom recovery, and instead boot into the OS, the recovery will revert back to stock, which is why you saw the dead Android with the ! mark (that is the stock recovery). Just fastboot flash TWRP again, and boot straight into it. Then, just flash the SuperSU zip and reboot system. You should be good to go.
EDIT: Oh, and having an unlocked bootloader has no effect on receiving an OTA or your ability to flash it. If your bootloader was unlocked before flashing an OTA, it will remain unlocked. The only way it would become locked again is if you locked it yourself. You can even completely flash the stock image, and the bootloader will remain unlocked.
Click to expand...
Click to collapse
That did it. Thanks
Hi,
Could you add a [SOLVED] tag to the title, as it is now solved ?
~Lord
"Dream On! Dream Until Your Dreams Come True!" - Dream On (Aerosmith)
Sent from my GT-I9505
Guys, I'm stuck.
So, I had my Nexus 4 wonderfully running the latest CM11 nightly. Then the Lollipop Factory Image for Nexus 4 came out. My bootloader was unlocked and had TWRP custom recovery. Then in fastboot mode, I flashed the new Lollipop factory images, except the userdata.img. By doing this, I replaced TWRP with stock recovery. Then I restarted the phone.
It stuck in the twirling colorful circles for 2+ hours. I heard it needed 10 minutes or so to fully load Lollipop. But 2 hours? So I then started troubleshooting. One of the first thread I stumbled upon suggested for me to re-lock the bootloader, which I stupidly did. It did not fix the problem. Now I'm stuck!
I'm unable to boot. Stuck in the twirling circles animation for hours.
I have no custom recovery, so I can't load custom ROMs.
I have no unlocked bootloader, so I can't reflash the factory images (or downgrade to stock 4.4.4).
And if I unlock the bootloader, I will lose ALL of my user data, including photos, music, and the Titanium Backups of all my app data, SMS, call logs, etc.
I tried flashing the latest CM11 nightly through ADB sideload within stock recovery, but I get the 'signature verification failed'. Is there a 'signed' ROM I could sideload through stock recovery?
Would ADB sideloading the Nexus 4 Lollipop OTA zip through stock recovery fix this problem? I'm downloading the OTA zip right now.
EDIT: Sideloading the OTA zip did the trick! I'm staring at Android is upgrading... right now. Thanks XDA for the thought process, wouldn't have solved it without posting this thread. Although, please note that at this time, I essentially have Android 5.0 installed, but having bootloop. I can't guarantee that this will work if you bootloop while having custom ROM or Kit Kat installed.
What else I could do to save my data? I'm out of ideas.
EDIT: To save my data, because now I'm able to boot to Lollipop (by flashing official Google Android 5.0 Lollipop OTA zip through stock recovery ADB sideload; see above solution), I'm gonna transfer all the files in storage/emulated/legacy (the internal sdcard) to my PC. I will then unlock the bootloader through fastboot, thus wiping all data on the phone. Then I'll just move everything back from PC to the phone. I should have done this in the first place!
HLEP.
You lost all data as soon as you locked it. Just saying.
Sent from my HTC One_M8 using Tapatalk
Misledz said:
You lost all data as soon as you locked it. Just saying.
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
This is untrue. I was unable to boot, but after flashing the OTA zip, I can boot to Lollipop and I still have everything, even my old apps, without needing to reinstall anything. Granted, there are errors here and there (probably due to dirty flash upgrade), but my data is intact.
As I said, I previously had TWRP, CyanogenMod 11, root and unlocked bootloader. Now I have Android 5.0 Lollipop, no root, a locked bootloader and all of my data. I wanted to show you my bootloader screen, but I have no other camera with me. The screenshots below should suffice.
Check attachment for proof.
Ah. I thought you were locked out being unable to boot. Anyways, you can back it up via Holo Backup, might wanna check it out
Sent from my HTC One_M8 using Tapatalk
Misledz said:
Ah. I thought you were locked out being unable to boot. Anyways, you can back it up via Holo Backup, might wanna check it out
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
Yes, I was unable to boot. Then, I replaced custom recovery with stock recovery. Then I stupidly locked the bootloader. It's all good now.
I've never heard of Holo Backup before. It seems like the perfect solution for me, as I don't have root right now! And transferring 13GB of files via MTP or Wi-Fi will take ages.
Thanks a lot for the suggestion. I'm giving it a shot.
My Nexus 6P comes with MDB08L and I rooted (traditional) with MDB08M. When I find my company email app (Good Work) does not work on rooted phone, I unrooted back to all stock MDB08M. Today I try to use recovery but I got Red Exclamation in middle of Recovery every time and the stock recovery seems dead. When I flash MMB29M and I flash the recovery again specifically but still got the Red Exclamation in middle of Recovery. I searched the see this video (https://www.youtube.com/watch?v=gzzYV1BjMNs) and tied but still no luck. But I do see the Android Recovery is the MMB29M version when I do the video thing. Can anyone please help to fix this? Thanks a million in advance!
VanGolfer said:
My Nexus 6P comes with MDB08L and I rooted (traditional) with MDB08M. When I find my company email app (Good Work) does not work on rooted phone, I unrooted back to all stock MDB08M. Today I try to use recovery but I got Red Exclamation in middle of Recovery every time and the stock recovery seems dead. When I flash MMB29M and I flash the recovery again specifically but still got the Red Exclamation in middle of Recovery. I searched the see this video (https://www.youtube.com/watch?v=gzzYV1BjMNs) and tied but still no luck. But I do see the Android Recovery is the MMB29M version when I do the video thing. Can anyone please help to fix this? Thanks a million in advance!
Click to expand...
Click to collapse
Why dont you try to revert back stock using a factory image?
chichu_9 said:
Why dont you try to revert back stock using a factory image?
Click to expand...
Click to collapse
I used MDB08M factory instead of MDB08L which originally from the phone, I am not sure this the course of the problem.
The red exclamation usually means either no recovery or incompatible recovery. Did you flash mmb29m recovery for mdb08m rom? If you get stuck too bad you can always enter fastboot and just reflash everything its not that hard to do.
dontbeweakvato said:
The red exclamation usually means either no recovery or incompatible recovery. Did you flash mmb29m recovery for mdb08m rom? If you get stuck too bad you can always enter fastboot and just reflash everything its not that hard to do.
Click to expand...
Click to collapse
Yes, I flashed whole mmb29m factory image over mdb08m. Still can't boot to recovery manu . I'm worried about OTA will fail.
Sent from my Nexus 6P using Tapatalk
VanGolfer said:
My Nexus 6P comes with MDB08L and I rooted (traditional) with MDB08M. When I find my company email app (Good Work) does not work on rooted phone, I unrooted back to all stock MDB08M. Today I try to use recovery but I got Red Exclamation in middle of Recovery every time and the stock recovery seems dead. When I flash MMB29M and I flash the recovery again specifically but still got the Red Exclamation in middle of Recovery. I searched the see this video (https://www.youtube.com/watch?v=gzzYV1BjMNs) and tied but still no luck. But I do see the Android Recovery is the MMB29M version when I do the video thing. Can anyone please help to fix this? Thanks a million in advance!
Click to expand...
Click to collapse
Once you're on that screen, you've held down the power button then pressed and released volume up right?
Sent from my SM-N920T using Tapatalk
VanGolfer said:
My Nexus 6P comes with MDB08L and I rooted (traditional) with MDB08M. When I find my company email app (Good Work) does not work on rooted phone, I unrooted back to all stock MDB08M. Today I try to use recovery but I got Red Exclamation in middle of Recovery every time and the stock recovery seems dead. When I flash MMB29M and I flash the recovery again specifically but still got the Red Exclamation in middle of Recovery. I searched the see this video (https://www.youtube.com/watch?v=gzzYV1BjMNs) and tied but still no luck. But I do see the Android Recovery is the MMB29M version when I do the video thing. Can anyone please help to fix this? Thanks a million in advance!
Click to expand...
Click to collapse
Get into fastboot, then "fastboot flash recovery xxxxxxxx.img" obviously replacing the x's with the file name. Just reflash the recovery for the same factory image you flashed. Very possible that you just need to reflash the recovery image.
spc_hicks09 said:
Get into fastboot, then "fastboot flash recovery xxxxxxxx.img" obviously replacing the x's with the file name. Just reflash the recovery for the same factory image you flashed. Very possible that you just need to reflash the recovery image.
Click to expand...
Click to collapse
Tried but doesn't work.
Sent from my Nexus 6P using Tapatalk
Flash the recovery via fastboot :
fastboot flash recovery xxx.img
fastboot reboot-bootloader
Now, when your phone reboots to bootloader, using the volume keys, find "recovery" and use the power button to confirm.
profit.
he has to press the power button and vol up on that screen to get into recovery just like guy in post 7 said...
factory recovery doesnt boot all the way into it by default, requires a user button input once it gets to that android exclamation screen
kauemelhado said:
Flash the recovery via fastboot :
fastboot flash recovery xxx.img
fastboot reboot-bootloader
Now, when your phone reboots to bootloader, using the volume keys, find "recovery" and use the power button to confirm.
profit.
Click to expand...
Click to collapse
I did this, the red little thing didn't go away
Sent from my Nexus 6P using Tapatalk
VanGolfer said:
I did this, the red little thing didn't go away
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Did you try downloading another recovery file?
That's really strange.
I was having this error when I tried to flash twrp and boot direclty to system (skipping the recovery boot).
Did you try to install twrp?
---------- Post added at 01:53 PM ---------- Previous post was at 01:48 PM ----------
Another thing..
The system boots up normaly?
To solve this, I did the procedure that I just told you + before booting into twrp, I flashed vendor.img..
Dunno if that could cause this issue
kauemelhado said:
Did you try downloading another recovery file?
That's really strange.
I was having this error when I tried to flash twrp and boot direclty to system (skipping the recovery boot).
Did you try to install twrp?
Click to expand...
Click to collapse
When I root I installed TWRP, revert back all to stock after unroot. I have to stay unroot because of the company app. Just want to be easy to update on OTA,
Sent from my Nexus 6P using Tapatalk
VanGolfer said:
When I root I installed TWRP, revert back all to stock after unroot. I have to stay unroot because of the company app. Just want to be easy to update on OTA,
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
I know that feel bro, my company also use an app that verifies for root..
I'm rooted, but on 6.0 I had only twrp w/ no root. no problems..
kauemelhado said:
I know that feel bro, my company also use an app that verifies for root..
I'm rooted, but on 6.0 I had only twrp w/ no root. no problems..
Click to expand...
Click to collapse
So you can install twrp without root as I understand. Then do you need to lock your phone after install twrp (unlock before install twrp, right?), and also how do you do the update OTA or upgrade to 6.0.1, etc..? Thx
VanGolfer said:
So you can install twrp without root as I understand. Then do you need to lock your phone after install twrp (unlock before install twrp, right?), and also how do you do the update OTA or upgrade to 6.0.1, etc..? Thx
Click to expand...
Click to collapse
I guess you can't lock your bootloader with Twrp.
Then, to take ota's just simply flash the img files.
;s
I had TWRP 3.0.1 so I downloaded the latest TWRP 3.0.2 IMG file and booted to Recovery and selected the image and then selected Recovery as to where to flash and it flashed no errors so I backed out and went to reboot and selected Recovery and it rebooted to bootloader and when I stroll volume keys to Recovery then power to select it just hangs there I have to do a power long press to get it to reboot back to Android. Any ideas why Recovery will not load now ?
I'm on MHC19l
Stock rooted no mods
System rooted
Sent from my Nexus 6P using Tapatalk
A bad flash, perhaps? Have you checked the MD5 after downloading?
Possible bad download but at this point I can't reflash the recovery until I can fast boot .. I gotta order another Type C to USB to connect the phone to the computer for fast boot grrrrr...
Thx
Sent from my Nexus 6P using Tapatalk
Glad to help! Next time make sure you check MD5 before flashing (even then an occasional bad flash could still cause trouble, but hey, what's the choice here?) You can still boot to Android normally, no?
Sidenote: anyone knows if a micro B to C adaptor would work with fastboot?
Yeah I can still boot to Android fine jus when I select recovery n bootloader it hangs in bootloader. I have to hard reset to get out of bootloader mode lol....
Jus sucks BC now I gotta wait until friday to order a Type C to USB cable to use the computer to fast boot TWRP to recovery.. :/
I jus got this 6P 4 days ago coming from the HTC M9 Developer Edition I decided to go with the 6P over the M10 even though I would have gotten $100 off the M10 for not using my UhOh protection.
But I'm currently Stock w/ root until I figure out or understand this whole Vender thing when flashing Roms.. Jus being very cautious.
With HTC you jus flash the ROM you want but here some say jus flash the ROM and some say flash the Vender matching the ROM.. Lol,..
Sent from my Nexus 6P using Tapatalk
About the vendor img... Not too sure about the whole technical details behind them, but I just flash them every time Google updates them (think monthly security updates), at the very least to get rid of the 'vendor img outdated' popup. You don't need to flash a new vendor img everytime you update/switch ROMs, but only when there's a new vendor.
I usually just flash recovery with flashify. Never had an issue doing it that way. Or fastboot.
Sent from my Nexus 6P using XDA-Developers mobile app
scoot0073 said:
I had TWRP 3.0.1 so I downloaded the latest TWRP 3.0.2 IMG file and booted to Recovery and selected the image and then selected Recovery as to where to flash and it flashed no errors so I backed out and went to reboot and selected Recovery and it rebooted to bootloader and when I stroll volume keys to Recovery then power to select it just hangs there I have to do a power long press to get it to reboot back to Android. Any ideas why Recovery will not load now ?
I'm on MHC19l
Stock rooted no mods
System rooted
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
People have been facing the same issue all around. Even I did, last night after updating to N Preview. Anyhow, the only solution I know right now is to have a decrypted filesystem (disable encryption), for TWRP to boot and work properly.
Yeah disable encryption I believe I read requires booting into recovery and wiping User Data or something alone those line's.
Unless there's a option in Android settings to disable it idk yet as I jus had the phone a few day's.
But so far I happy with my decision to get the 6P over the M10 even if the 6P is 4 or 5 moths old...
Sent from my Nexus 6P using Tapatalk
OK I got the latest TWRP Recovery flash . I used Flashify app and it flashed the recovery and I got a working recovery now..
Sent from my Nexus 6P using Tapatalk
Pain-N-Panic said:
I usually just flash recovery with flashify. Never had an issue doing it that way. Or fastboot.
Sent from my Nexus 6P using XDA-Developers mobile app
Click to expand...
Click to collapse
Thank u so much that fixed my borked recovery thank you again
Sent from my Nexus 6P using Tapatalk