I'm on Verizon and have an unlocked bootloader (still unrooted) with TWRP as my recovery. I received the OTA notification earlier and kicked off the update, but all my phone is doing is showing the TWRP splash screen (TeamWin), then flashing black, then back to the TeamWin, then black.
Any thoughts on what i should be doing? I don't know why it is even entering recovery.
Some more info in case it helps: I can power off the device, then power back on and it will load my normal 5.1.1 instance. Then, after about a minute, it will power off and re-enter the recovery loop.
I can't imagine that this recovery loop is what SHOULD be happening as the update is being applied, right? I also can't imagine that having TWRP would impact the OTA MM install at all- yet it definitely appears to be the case. Do I need to change my recovery back to stock?
chuck-fu said:
I'm on Verizon and have an unlocked bootloader (still unrooted) with TWRP as my recovery. I received the OTA notification earlier and kicked off the update, but all my phone is doing is showing the TWRP splash screen (TeamWin), then flashing black, then back to the TeamWin, then black.
Any thoughts on what i should be doing? I don't know why it is even entering recovery.
Click to expand...
Click to collapse
If you "kicked it off" while never changing back to stock recovery is why you are bootlooping.
Flash stock recovery and you should be good to go.
Dunka said:
If you "kicked it off" while never changing back to stock recovery is why you are bootlooping.
Flash stock recovery and you should be good to go.
Click to expand...
Click to collapse
Thanks- that did it!
Where can I find the stick recovery img? I'm having the same problem
Looking for a flashable stock recovery as well...
Check here in this thread for stock recovery and any other firmware
http://forum.xda-developers.com/showthread.php?t=3224833
Related
Hey Guys,
I just rooted my nexus 4 again, after taking a sabbatical from this stuff.
I did the same thing as usual, unlocked bootloader, flashed twrp, rooted.
And it was working fine on stock.
Then I got a notification for the 4.4 update, and I made the mistake of doing that OTA.
Now my phone won't boot to recovery. I see a picture of an android with a red exclamation mark whenever I try to do that.
Anyone know what I should do?
J-Boxer said:
Hey Guys,
I just rooted my nexus 4 again, after taking a sabbatical from this stuff.
I did the same thing as usual, unlocked bootloader, flashed twrp, rooted.
And it was working fine on stock.
Then I got a notification for the 4.4 update, and I made the mistake of doing that OTA.
Now my phone won't boot to recovery. I see a picture of an android with a red exclamation mark whenever I try to do that.
Anyone know what I should do?
Click to expand...
Click to collapse
You have the stock recovery on your phone. Just hit vol up to access it. If you want twrp just flash the image in fastboot
fastboot flash recovery recovery.img, where recovery.img is the twrp image file
Sent from my Nexus 5 using XDA Free mobile app
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
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 think I am having a similar issue to the OP in the following thread http://forum.xda-developers.com/showthread.php?t=3267539
I have unlocked my boot-loader and rooted a flashed factory image of mdb08m using skipsoft.
So I want to flash the new OTA but despite unrooting and using the the function in skipsoft to unroot, remove files, and restore stock recovery the OTA failed. I have since then downloaded the the factory image and re-flashed the stock recovery but every time I go into recovery (to try and sideload) I get the red exclamation with the words "No command" underneath. I then can not do anything.....
Thankfully the phone boots and runs like normal yet I can not do the update ?
Any ideas please?
indyjonesUK said:
I think I am having a similar issue to the OP in the following thread http://forum.xda-developers.com/showthread.php?t=3267539
I have unlocked my boot-loader and rooted a flashed factory image of mdb08m using skipsoft.
So I want to flash the new OTA but despite unrooting and using the the function in skipsoft to unroot, remove files, and restore stock recovery the OTA failed. I have since then downloaded the the factory image and re-flashed the stock recovery but every time I go into recovery (to try and sideload) I get the red exclamation with the words "No command" underneath. I then can not do anything.....
Thankfully the phone boots and runs like normal yet I can not do the update ?
Any ideas please?
Click to expand...
Click to collapse
the ota will likely still fail if you were able to sideload it.
its been my experience with previous devices, you cant really remove root properly and make the phone 100% like it was. that probably why the update is failing.
frequently you need to flash the full stock img to make the phone clean enough for ota's.
i cant guarantee thats the case here, but is very likely.
If you get the 'No command' thingy you should try fastboot flashing the recovery.
That's what did the trick for me.
Casmo said:
If you get the 'No command' thingy you should try fastboot flashing the recovery.
That's what did the trick for me.
Click to expand...
Click to collapse
Yeah I tried that but has not changes things
Did you hold power, tap VOL UP and release both? That is how you enter stock recovery.
fury683 said:
Did you hold power, tap VOL UP and release both? That is how you enter stock recovery.
Click to expand...
Click to collapse
Can't believe I could not find that anywhere! thank you worked first time....
indyjonesUK said:
Can't believe I could not find that anywhere! thank you worked first time....
Click to expand...
Click to collapse
You need to see whether your stock recovery can work with OTA successfully.
Thanks!
fury683 said:
Did you hold power, tap VOL UP and release both? That is how you enter stock recovery.
Click to expand...
Click to collapse
OMG can't believe you have to do this while stuck in "No command", thanks a lot!
Hello.
My mobile ver 25.93.14.4 is rooted and twrp is installed. Today I got update for my device which is npjs 25.93.14.8 I downloaded this update and after downloading i click on install button a message appears that phone will restart in 10 seconds after restarting the mobile stuck in recovery mode. I again try to restart but again automatically i log into recovery mode. what should I do to install new update.
Thanks in advance.
abhi212b said:
I think since you are rooted and you tried installing the OTA, the boot.img is replaced by the original one, that breaks the phone if flashed on root. so you can try 2 things:
1. Try flashing the EX kernel again. Flash the Uninstaller 1st and then flash it again and then normal boot from TWRP.. if it loops to TWRP, use point 2 procedure.. if it works...
2. If you are being re-directed to the TWRP. press and hold power + Vol down to go to bootloader and then use normal mode.
Personally, I would flash EX kernel again and then boot...
Hope it helps!
If Nothing helps..Make a Nandroid backup, Boot to bootloader by Power+Vol down. and then flash stock from PC..
u can restore the nandroid backup by Titanium Pro..
Click to expand...
Click to collapse
Try the steps that abhi212b suggested (this was for users that had TWRP installed and took the March OTA when it was available).
As an aside, OTA updates will only install properly on the stock recovery with a stock system and kernel. Thus you'll have to remove root, flash a stock kernel and stock recovery and then you should be able to install the OTA. If you have a custom logo.bin, you'll have to flash the stock logo.bin too.
Thanku so much.
echo92 said:
Try the steps that abhi212b suggested (this was for users that had TWRP installed and took the March OTA when it was available).
As an aside, OTA updates will only install properly on the stock recovery with a stock system and kernel. Thus you'll have to remove root, flash a stock kernel and stock recovery and then you should be able to install the OTA. If you have a custom logo.bin, you'll have to flash the stock logo.bin too.
Click to expand...
Click to collapse
Thank you so much buddy...
solved my problem:good: