Database Users

[Q] can't get to recovery mode after unlocking

Hi, a bit of noob but i did googled alot
My plan was:
Unlock and root with nexus 4 toolkit.
Do nandroid backup
Flash PA rom.
step 1 went okay,
afterwards i tried to go to recovery mode inorder to backup but i got the lying android with the red warning sign.
I did backup using Rom Manager and nexus 4 toolkit but I'm worried I can't get to recovery mode if something goes wrong.
How shall I proceed before flashing the rom?

The robot lying on it's back is the stock recovery. You need to flash CWM/TWRP before you can do a Nandroid

itayze said:
Hi, a bit of noob but i did googled alot
My plan was:
Unlock and root with nexus 4 toolkit.
Do nandroid backup
Flash PA rom.
step 1 went okay,
afterwards i tried to go to recovery mode inorder to backup but i got the lying android with the red warning sign.
I did backup using Rom Manager and nexus 4 toolkit but I'm worried I can't get to recovery mode if something goes wrong.
How shall I proceed before flashing the rom?
Click to expand...
Click to collapse
Do yourself a favour and learn how to use ADB instead of toolkits that do more harm than good if used by inexperienced users and you`ll learn to do it the right way.
Look here http://forum.xda-developers.com/showthread.php?t=1474956 for how to.
Youtube tutorial link http://www.youtube.com/watch?v=ZY4KSrgi-rE.

itayze said:
Hi, a bit of noob but i did googled alot
My plan was:
Unlock and root with nexus 4 toolkit.
Do nandroid backup
Flash PA rom.
step 1 went okay,
afterwards i tried to go to recovery mode inorder to backup but i got the lying android with the red warning sign.
I did backup using Rom Manager and nexus 4 toolkit but I'm worried I can't get to recovery mode if something goes wrong.
How shall I proceed before flashing the rom?
Click to expand...
Click to collapse
If you have Rom Manager Installed and are rooted you should be able to install CWM thru it.

don't have flash recovery on rom manager
I don't have the the "Flash CWM" recovery option on rom manager,
I've attached a screen of what I do have,
I did explore the Recovery Setup but wasn't able to do anything usefull.
Any advice?

itayze said:
I don't have the the "Flash CWM" recovery option on rom manager,
I've attached a screen of what I do have,
I did explore the Recovery Setup but wasn't able to do anything usefull.
Any advice?
Click to expand...
Click to collapse
according to ROM Manager you already have CWM installed and its up to date. Have you tried booting into recovery using ROM Manager?

When I press reboot to recovery directly from rom manager it works...
I'm just affraid that in case that I brick or mess up something I won't be able to get to stock recovery mode.

volume down + power button = bootloader (android on his back) also called fastboot mode
use volume buttons to scroll to recovery then press power button to select it
you should then be in CWM recovery if its installed correctly.
If you are using a custom recovery your stock recovery is gone. You would have to use fastboot to flash the stock recovery image back onto the phone. Its rather simple to do as is flashing the stock image file back onto the phone.

that is why I started this thread.
After I Unlocked and rooted I wasn't able to fastboot and go to recovery mode, it showed my the android on his back.
I've tried it again now and it still doesn't work.
but when I boot directly from rom manager it works...
Edit: I posted before you edited your comment.
even though I don't know adb, should I learn and follow this guide?
http://www.androidauthority.com/nexus-4-clockworkmod-recovery-134114

itayze said:
that is why I started this thread.
After I Unlocked and rooted I wasn't able to fastboot and go to recovery mode, it showed my the android on his back.
I've tried it again now and it still doesn't work.
but when I boot directly from rom manager it works...
Click to expand...
Click to collapse
There is a bug that restores the stock recovery after a reboot and there should be an option in the root toolkit to fix it. Not saying this is what happened but it may have. The stock recovery is stored in system memory somewhere and the bug fix just removes it so it won't restore itself after reboot.
Follow efrants guide for ADB and fastboot
http://forum.xda-developers.com/showthread.php?t=2010312

kzoodroid said:
There is a bug that restores the stock recovery after a reboot and there should be an option in the root toolkit to fix it. Not saying this is what happened but it may have. The stock recovery is stored in system memory somewhere and the bug fix just removes it so it won't restore itself after reboot.
Follow efrants guide for ADB and fastboot
http://forum.xda-developers.com/showthread.php?t=2010312
Click to expand...
Click to collapse
Its not a bug. Its a script. Intended feature.
Sent from my Nexus 4 using xda premium

El Daddy said:
Its not a bug. Its a script. Intended feature.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
I call it a bug because its an annoying feature. There are a number of threads no how to remove it but using a toolkit to do it is just as easy.

thank you,
but after I've read what you wrote about the bug I open the nexus root tool kit and then I realized what I should have done.
I pressed Custom recovery checkbox and rooted again.
now it works !

itayze said:
thank you,
but after I've read what you wrote about the bug I open the nexus root tool kit and then I realized what I should have done.
I pressed Custom recovery checkbox and rooted again.
now it works !
Click to expand...
Click to collapse
Glad you got it working. I would still learn adb and fastboot. Though I too use the tool kit every now and then out of convenience.

Recovery won't flash

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.

[Q] Trouble installing custom recovery on D800

I rooted using ioroot12 and tried installing recovery using both play store CWM installer for D800 as well as a manual install using the method shown in a thread in the D800 development forum. Both methods appear to install successfully but when I reboot to recovery I get a black screen (can tell black light is lit though) and nothing else. Holding the power eventually reboots phone back into the stock os. When in the broken recovery status and connected to computer via USB I get a slew of drive letters all prompting to format.
I'm guessing those are all the directories on the phone which are formatted android fs?
Any ideas what is happening? ioroot12 contains some changes to be compatible with the latest OTA, maybe the stock recovery file structure changed a little after the OTA?

arie001 said:
I rooted using ioroot12 and tried installing recovery using both play store CWM installer for D800 as well as a manual install using the method shown in a thread in the D800 development forum. Both methods appear to install successfully but when I reboot to recovery I get a black screen (can tell black light is lit though) and nothing else. Holding the power eventually reboots phone back into the stock os. When in the broken recovery status and connected to computer via USB I get a slew of drive letters all prompting to format.
I'm guessing those are all the directories on the phone which are formatted android fs?
Any ideas what is happening? ioroot12 contains some changes to be compatible with the latest OTA, maybe the stock recovery file structure changed a little after the OTA?
Click to expand...
Click to collapse
i repeatedly tried over and over after the ota.... it wont work you have to go back to stock reset. root then install twrp or cwm. twrp worked for me and cwm messed up my device causing a complete wipe of everything including logos and everything just a black screen that wouldnt power on. 30 minutes later it booted back up??? be careful.

Thanks
podagee said:
i repeatedly tried over and over after the ota.... it wont work you have to go back to stock reset. root then install twrp or cwm. twrp worked for me and cwm messed up my device causing a complete wipe of everything including logos and everything just a black screen that wouldnt power on. 30 minutes later it booted back up??? be careful.
Click to expand...
Click to collapse
Thanks, probably saved my phone from certain destruction. I followed the steps to go back to stock and successfully rooted and was able to install custom recovery finally.
I seem to recall the OTA taking a long time for being so small, I wonder if they played with partition sizing or something on the "o" firmware.

arie001 said:
Thanks, probably saved my phone from certain destruction. I followed the steps to go back to stock and successfully rooted and was able to install custom recovery finally.
I seem to recall the OTA taking a long time for being so small, I wonder if they played with partition sizing or something on the "o" firmware.
Click to expand...
Click to collapse
i only seen that the att apps were updated after the update as well as a security update tightening up their security for their bootloader.as far as partitioning uncertain on that.
glad it worked for you.

I spent a few hrs last night into the am trying to root and flash a working recovery. Just realized my phone auto updated to the OTA and, think I need to go back to the pre-ota. For whatever reason, I can't get twrp to update, no matter how I try to flash it.
Sent from my LG-D800 using Xparent Red Tapatalk 2

bzmotoninja83 said:
I spent a few hrs last night into the am trying to root and flash a working recovery. Just realized my phone auto updated to the OTA and, think I need to go back to the pre-ota. For whatever reason, I can't get twrp to update, no matter how I try to flash it.
Sent from my LG-D800 using Xparent Red Tapatalk 2
Click to expand...
Click to collapse
I got mine to root using ioroot 12. I got twrp by usint freegee app. The only thing is my recovery is 2.6.3.0. Trying to figure 9ut how to get a newer version of recovery now.
Sent from my LG-D800 using XDA Premium 4 mobile app

Check with the guys on the webchat If you get stuck. I gotta flash pre-OTA personally. Something that I flashed stuck and won't let twrp update.
Sent from my LG-D800 using Xparent Red Tapatalk 2

bzmotoninja83 said:
Check with the guys on the webchat If you get stuck. I gotta flash pre-OTA personally. Something that I flashed stuck and won't let twrp update.
Sent from my LG-D800 using Xparent Red Tapatalk 2
Click to expand...
Click to collapse
If you're on 10o now, try using FreeGee from the Play Store, as mentioned, to get twrp installed.

heres what youre failing to realize..... with 2.6.3.0 I cant flash anything other than, nothing. Everything fails..... I cannot upgrade to the later versions of twrp, any way shape form or fashion. thanks tho

btm fdr said:
If you're on 10o now, try using FreeGee from the Play Store, as mentioned, to get twrp installed.
Click to expand...
Click to collapse
I couldn't get the 10o OTA to install but I used FreeGee to install TWRP and it was incredibly easy/simple. I've seen a few people now that have said they were also able to flash TWRP after upgrading to 10o using FreeGee as well.
fountain79 said:
I got mine to root using ioroot 12. I got twrp by usint freegee app. The only thing is my recovery is 2.6.3.0. Trying to figure 9ut how to get a newer version of recovery now.
Sent from my LG-D800 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
If you have TWRP installed already you can just boot into recovery, flash a new TWRP or CWM recovery zip and then go to the "Advanced" menu and select Reboot>Recovery to boot into recovery again and you'll be in the new recovery you just flashed.

I tried that like 30 times over the last 2 days. I finally got flashtool to go back pre ota and now I'm running PA and have 2.6.3.3 for twrp. My reason for things not working is, I think that when I flashed something, it stuck making the code all jacked. Please next time, don't ASSume that because its supposed to work that it always will. There will always be human error.
Sent from my LG G2 using Xparent Red Tapatalk 2

Stuck in recovery after OTA.

So my phone is rooted and i got the att ota update which just came automatically. And now my phone is stuck in twrp, and when i try to flash a recovery and reboot system it doesn't work it just keeps going back to the twrp. I saw that people are using adb shell and putting in some commands but my phone isn't recognized. And also i saw some people try to do it straight in the phone by putting in the commands but i can't do that. Also now when i try to reboot recovery now it says your phone does not seem to be rooted, swipe to install superuser.....i already rooted and have superuser, so when i do swipe it just goes back to the previous screen. Any help or advice is appreciated.

I think only option now is to kdz back to stock.
Sent from my LG-D802 using Tapatalk

Nexus 6p Root Failure / Boot Loop / Android 6.0.1

I tried to root my Nexus 6P and now I'm stuck. It won't finish booting. I followed instructions found on the web. I unlocked bootloader with no problem. I copied the latest SuperSU file to the phone. I installed TWRP recovery. However, I could not find the SuperSU file when using TWRP. Nevertheless, when I went to exit, TWRP asked if I wanted to instal SuperSU. I recall reading somewhere that it will install the wrong version of SuperSU (not the one for 6.0.1). Somehow I must have hit the wrong selection because it installed it anyway. Now I have an infinite loop.
I have tried to factory reset with TWRP. That fails. I downloaded the 6.0.1 images files from Google. I tried to run flash-all.bat, but that doesn't work. I have pushed images and ZIPs to the /sdcard/ folder with ADB. ADB recognizes the device, but fastboot does not (when connected to my laptop) (which is why flash-all doesn't work). I have tried to install the images/zips with TWRP. However, I always get "failed" messages. I get messages that partitions won't load.
Stupidly, I do not have a nandroid backup (yes, I know, a dumb move).
Any suggestions on what to try next? I'm at my wit's end with this. I've searched the web all morning and found all kinds of helpful info, but I can't find anything to get me past this point. I am perfectly willing to wipe it all out and start over again if I could just force it to do that. I just bought it so I suppose I could return it (I think there's a 30-day return policy), but Google might not like it if it comes back in this state, I suppose. I had an AT&T Galaxy Note 5 for half a day but found out, after the fact, that I can't root it.
Thanks for any help or suggestions.

Why did you follow instructions found on "Web" when u have the beautiful guide by our @Heisenberg? Read this thread. Instead of running flash - all. Bat file, follow the instructions in this guide. http://forum.xda-developers.com/showthread.php?t=3206928

jaidev.s said:
Why did you follow instructions found on "Web" when u have the beautiful guide by our @Heisenberg? Read this thread. Instead of running flash - all. Bat file, follow the instructions in this guide. http://forum.xda-developers.com/showthread.php?t=3206928
Click to expand...
Click to collapse
I saw that post. I wish I had followed it. However, the instructions are very similar to what I tried, although not exact. Where I went wrong is letting TWRP install SuperSU for me. I didn't mean to but when I touched the phone it installed it (of course, I hit something, but I don't know what). Fastboot does not recognize the phone in recovery. I can follow Heisenberg's instructions to get back to stock IF fastboot would recognize the phone. ADB recognizes the phone. Would it be possible to use ADB Sideload instead? How can I force fastboot to recognize the phone? If I could do that, I would be able to flash images back to the phone. Thanks!

U should try fastboot in bootloader / download mode instead of recovery mode..

OK, two comments: Duh (as I slap my head) and Bless You! That worked. I'm back to stock. At least the phone works now. I'll try again to root following Heinsenberg's instructions! Thanks. Where do I sent the beer money?

jaidev.s said:
U should try fastboot in bootloader / download mode instead of recovery mode..
Click to expand...
Click to collapse
Well, I'm back to a stock phone, anyway. Flashing SuperSU per Heinsenberg's instructions did not give me root. Oh well. I'll keep trying. It did install and it did reboot just fine. However, root checker says I have no root and Titanium Backup won't run, either. Thanks.