Database Users

Fastboot> Recovery dosen't find *.img file on SD card

Hi Guys!
I am trying to root my nexus, unlocked it, installed the right usb drivers, I can see the phone and everything looks right.
Downloaded Superboot for ERE27 with himem enabled and ran this. no problem.
I put the img file on the SD card and when I boot the phone in Fastboot / Recovery it does not find and img files on the SD card.
I tried 2 different cards and also different img files.
When I do this I get first the message no images found than I see the droid with a triangle and a ! in it. - Have to pull the battery.
Ideas anyone?
Thanks

What are you trying to do?
1) you had to unlock the bootloader which enables you to install a new recovery image (which is needed to allow you to install new roms)
2) you had to apply the recovery image Amon RA via a command prompt and a batch file if you use Windows. The phone's USB connection needs to be in development mode and once the batch file executes and successfully finishes you need to reboot the phone.
3) you restart the phone into bootloader mode, use the volume rocker to select the recovery console. If you end up with an andriod and exclamation symbol the Amon RA recovery file was not installed.
4) the new recovery console allows you to clean the SD card. Install roms from the SD card and some other commands. The Roms for the Andriod are in ZIP format and do not need to be unziped. In other words all you need to copy to the SD card is the full ZIP file (approx 75MB) and install that directly from the recovery console.
If your android stays in the booting sequence which is shown as the X with flying little pixels, it's most likely because you did not wipe the device clean first. That item is in the recovery console as well.
Hope this helps. I am just as new to this as you are.

You didn't unzip them did you?

You're trying to root with superboot. Great, but the recovery is not capable of flashing .img files, only .zip updates and roms and such. .img files have to be flashed using fastboot, not recovery, and are flashed from the connected computer.
If you read the superboot instructions from wherever you got the file, you'll see that you have to put the .img in the same directory ON YOUR COMPUTER as fastboot, connect via USB, boot the phone into fastboot, then enter the appropriate command line on the computer to flash the file.
If you've done that, then you are officially DONE with the rooting process.
Also, make damn sure that the superboot version matches the software version on your phone. They're both ERE27, right?
I'm not sure what anosis's post is talking about, but that looks more like the process for installing a custom rom (ie cyanogenmod), than rooting.
To root your phone, you DO NOT need Amon-RA's recovery. You only need that if you want to install custom roms, etc. It wont hurt to have it, as it includes many more functions than the stock recovery, but just to root, you don't need it.
Summary:
If you flashed the superboot.img from your computer via fastboot, your phone is rooted. Done.
You don't need to do anything in the recovery at all for rooting. Only for installing update.zips and custom rom.zips.

Hey, So I have been scouring the forums trying to find some answers about this and you seem to be the closet to my situation. Here is what I did:
So I was running a CM9 Aplha, reverted back to stock 2.3.6 [1ada25375426.signed-soju-ota-189904.1ada2537]) so that I could then apply ICS update [VQ8PQk_V]) which I sucessfully did. This was about a month ago and it was all going well.
Then yesterday I wanted to upgrade to 4.0.4 [hR7QFEtn] so I did and superuser wasn't working properly but then I reinstalled it and got it to work. However I got to the point where everything was working fine EXCEPT for the Google Play store kept on force closing. I spent hours trying last night and could not find a solution.
I tried restoring the previous ICS update that I had and it worked, and then I tried updating again. Also side: My clockwork was on the fritz lately so I was using Zedowmaxs force into clockwork recovery image [fastboot boot recovery3101.img] to force it in sometimes.
Anyway bottom line here is where my REAL ISSUE begins. I decided just to wipe everything and start anew. I factory reset/ wiped properly [cache partition and davliche cache] and then locked my bootloader again. Then tried rebooting. Got stuck on Google screen. Then I unlocked my bootloader again. Tried again, same issue.
So, here is where I am at. Cannot get into recovery from fastboot, takes me back to fastboot. AND, everything is wiped because I locked/unlocked my bootloader. All I can do is adb commands.
I don't know what to do from here and there is a lot of things going on. If you could help that would be great!? What I am going to try next is to flash some recovery on, but I don't know which one/ try to mount a file to my sd card from adb commands.

Daboxk said:
Hey, So I have been scouring the forums trying to find some answers about this and you seem to be the closet to my situation. Here is what I did:
So I was running a CM9 Aplha, reverted back to stock 2.3.6 [1ada25375426.signed-soju-ota-189904.1ada2537]) so that I could then apply ICS update [VQ8PQk_V]) which I sucessfully did. This was about a month ago and it was all going well.
Then yesterday I wanted to upgrade to 4.0.4 [hR7QFEtn] so I did and superuser wasn't working properly but then I reinstalled it and got it to work. However I got to the point where everything was working fine EXCEPT for the Google Play store kept on force closing. I spent hours trying last night and could not find a solution.
I tried restoring the previous ICS update that I had and it worked, and then I tried updating again. Also side: My clockwork was on the fritz lately so I was using Zedowmaxs force into clockwork recovery image [fastboot boot recovery3101.img] to force it in sometimes.
Anyway bottom line here is where my REAL ISSUE begins. I decided just to wipe everything and start anew. I factory reset/ wiped properly [cache partition and davliche cache] and then locked my bootloader again. Then tried rebooting. Got stuck on Google screen. Then I unlocked my bootloader again. Tried again, same issue.
So, here is where I am at. Cannot get into recovery from fastboot, takes me back to fastboot. AND, everything is wiped because I locked/unlocked my bootloader. All I can do is adb commands.
I don't know what to do from here and there is a lot of things going on. If you could help that would be great!? What I am going to try next is to flash some recovery on, but I don't know which one/ try to mount a file to my sd card from adb commands.
Click to expand...
Click to collapse
It looks like the time when you were locking-unlocking the bootloader, you messed up the recovery. Since your phone can get into bootloader menu, I think you can get out of this issue.
Here is what I would do.
1. Unlock the bootloader.
2. flash clockworkmod recovery using fastboot USB.
3. Download recovery-RA-passion-v2.2.1.img, put it in C:\fastboot\
4. Shut down your phone. Then start your Nexus One in Fastboot mode by holding down the Trackball and press the Power button.
5. Connect your phone to your computer. Open a Command Prompt (Start -> All Programs -> Accessories -> Command Prompt), and run the following commands:
cd C:\fastboot
fastboot devices
fastboot flash recovery recovery-RA-passion-v2.2.1.img
now see if you can get into recovery. If you can, just flash a custom rom using install zip from sd card option in the recovery

I didn't read all the replies but fastboot reads from your PC's disk not the sdcard, unless you are running it through shell or something?

[Q] bootloop help

i have a mytouch 4g that i had perma rooted with s off 0.85.2007 clockwork recovery and evil desire hd rom. I have had this setup since the evil rom was available with no problems at all. All of a sudden the phone is in a bootloop. I can get into the hboot but adb and fastboot will not recognize the phone. I had a spare mytouch so I switched to that perma rooted s off and 0.85.2007with clockwork and the newest version of the same rom with no problems at all. I let the older 4g sit for a day with no battery, sim or sd card then i put the sd card in and it booted up. I went thru rom manager and selected reboot to recovery and I am back to a bootloop. I have tried to to go thru the hboot and select recovery manually and as soon as i press power to select back to a bootloop. I did some reading and tried to go back to the pd15img file by placing the file on a formatted sd card using a card reader and then put it in the phone. It went thru the process bypasing #7 and #8 (they show TP next to them) the phone now shows S-on with 0.86.0000 with radio 26.03.02.26_m. I am still stuck in bootloop with no way to get to recovery and still not being reconized in adb.
I guess at this point I could just do an exchange on the phone since I do have the other 4g running with no issues. But was wondering if anyone had any ideas on getting the phone out of bootloop.
Sorry if its a little wordy just wanted to make sure that I listed the steps i took to help narrow it down.
Thanks in advance for the help.

Load the PD15IMG on your MyTouch4G (not 5G) and boot into Bootloader, the phone will ask if you want to update the system, press the up volume button to do so.

neidlinger said:
Load the PD15IMG on your MyTouch4G (not 5G) and boot into Bootloader, the phone will ask if you want to update the system, press the up volume button to do so.
Click to expand...
Click to collapse
sorry edited. I have done that already and since i did i went from s-off and 0.85.2007 to S-on with 0.86.0000 but still in bootloop.

boosted22 said:
sorry edited. I have done that already and since i did i went from s-off and 0.85.2007 to S-on with 0.86.0000 but still in bootloop.
Click to expand...
Click to collapse
Try reformatting the SD Card to entirely FAT32 and try again.
or since you can get into fastboot try flashing a Recovery image, then boot into HBoot then select recovery and flash a ROM. Try using Cyanogen CM6.1.2RC2.

neidlinger said:
Try reformatting the SD Card to entirely FAT32 and try again.
or since you can get into fastboot try flashing a Recovery image, then boot into HBoot then select recovery and flash a ROM. Try using Cyanogen CM6.1.2RC2.
Click to expand...
Click to collapse
ok tried formatting the sdcard and placing the file on the card. It went thru the process and bypassed the same two files and still in a bootloop.
I am able to get to the fastboot on the phone however adb and fastboot will not recognize the device.

boosted22 said:
ok tried formatting the sdcard and placing the file on the card. It went thru the process and bypassed the same two files and still in a bootloop.
I am able to get to the fastboot on the phone however adb and fastboot will not recognize the device.
Click to expand...
Click to collapse
Do you have the phone drivers installed on your PC?

Genocaust said:
Do you have the phone drivers installed on your PC?
Click to expand...
Click to collapse
yes the drivers are there. adb recognizes my spare 4g and just to test it out i adb pushed a file and was successful.

anybody have any ideas or suggestions?

What about flashing with fastboot? You don't need a working Android OS, only a working bootloader, a USB cable, and the sdk tools.

jggimi said:
What about flashing with fastboot? You don't need a working Android OS, only a working bootloader, a USB cable, and the ADB Drivers.
Click to expand...
Click to collapse
fixed for ya. See my signature for TrueBlue's ADB guide.

jggimi said:
What about flashing with fastboot? You don't need a working Android OS, only a working bootloader, a USB cable, and the sdk tools.
Click to expand...
Click to collapse
neidlinger said:
fixed for ya. See my signature for TrueBlue's ADB guide.
Click to expand...
Click to collapse
Thanks for the help.
I have the sdk installed and it is working properly on my other 4g however when i boot into fastboot it does not detect the 4g that loops but i can unplug the bad one and plug the good one in and it recognizes immediately and allows me to use both adb and fastboot.

[Q] Bricked my Desire Z

It seems I bricked my Desire Z. That'll teach me for messing with custom roms
I only get the bootloader (the white screen with coloured text). Everything I do from there either does nothing or just goes to a white screen with a green HTC logo and then hangs.
I tried flashing Cyanogenmod by renaming the zip pc10img.zip, this failed. I tried installing an official G2 rom from the SD, this also failed. When I turn the thing on I get a green HTC logo, when I try to go to recovery it's the same story.
Can anyone help me get my phone back to life?

When you get in to recovery are you getting any error messages?
Have you tried restoring a nandroid backup or trying a different sd card?
And re-naming a rom to PC10IMG.zip will never work

I don't get an error message, it just hangs at the HTC logo. Same when I reboot the phone.
I don't have a backup since the last time I tried using one, it didn't work. Besides, I don't have Clockwork so I wouldn't be able to restore it even if I had one

Neko Koneko said:
I don't get an error message, it just hangs at the HTC logo. Same when I reboot the phone.
I don't have a backup since the last time I tried using one, it didn't work. Besides, I don't have Clockwork so I wouldn't be able to restore it even if I had one
Click to expand...
Click to collapse
You cant get in to clockwork. have you tried using adb?

Not yet. Is it possible to flash a rom or even just clockwork through adb?
I'm sorry for being such a n00b about this, I'm just not that experienced yet with android devices. Used to change roms on my WinMo device all the time but Android's... quite different

If you have the ENG Hboot you can flash the recovery from fastboot....
If you have the sdk set up on your computer do the command (after putting the clockwork recovery in your sdk folder):
fastboot flash recovery recovery.img
then go to the recovery, wipe and flash

I now have the issue that ADB won't see the phone. The phone says HBOOT USB PLUG so it knows it's connected through USB, it shows up in my device manager but ADB won't recognise it. Any suggestions?

adb won't work in hboot/fastboot mode, you need to get the fastboot executable.
It might be in your tools folder for adb.
You can make sure its working by running 'fastboot devices'
-Nipqer

Nipqer said:
adb won't work in hboot/fastboot mode, you need to get the fastboot executable.
It might be in your tools folder for adb.
You can make sure its working by running 'fastboot devices'
-Nipqer
Click to expand...
Click to collapse
Thanks! Fastboot detects the device Now I can try to fix stuff.

It worked! I managed to install Clockwork Recovery using Fastboot and after that installing Cyanogenmod was a piece of cake Thanks you guys!

The most important thing I learned from playing with roms is how to read the manual. Be careful out there.
Sent from my HTC Vision using XDA Premium App

Ahem, guys, where can I find fastboot executable? I checked everywhere in the android-sdk directory but I can't find it. I even updated to the latest SDK tools, and yet fastboot is still MIA.

Always and I mean ALWAYS create backups of your working roms, I cannot stress this enough.
You can copy files onto your sdcard using adb then force boot into cwm. Thank goodness for adb
Sent from Space using Tapatalk Pro

Help! Can't boot / cant get into recovery. ..

I was unlocked and rooted and ready to install CM7. I followed all the instructions in the Official Atrix CM7 OP to the T, but when it rebooted, I got stuck on the boot screen with "unlocked" and the red M logo.
I tried to repeat the process several times and ended kind of giving up, factory wiping, and then trying to restore my backup. It appeared to restore successfully, but when I rebooted the phone now wont boot at all. I can't even get it into recovery. No combination or order of button presses or battery pulls / usb plugins will turn it on. I just have a green light like it's charging but nothing is working.
Is it possible to brick your phone even after you have been successfully unlocked and rooted just while you are trying to install CM7?
Please help. I am really desperate here. . .

jimjenkins said:
I was unlocked and rooted and ready to install CM7. I followed all the instructions in the Official Atrix CM7 OP to the T, but when it rebooted, I got stuck on the boot screen with "unlocked" and the red M logo.
I tried to repeat the process several times and ended kind of giving up, factory wiping, and then trying to restore my backup. It appeared to restore successfully, but when I rebooted the phone now wont boot at all. I can't even get it into recovery. No combination or order of button presses or battery pulls / usb plugins will turn it on. I just have a green light like it's charging but nothing is working.
Is it possible to brick your phone even after you have been successfully unlocked and rooted just while you are trying to install CM7?
Please help. I am really desperate here. . .
Click to expand...
Click to collapse
are you using the right recovery? romracer or rom manager!

i am using the tenfar CWM included in the Atrix 4G Automatic Unlock script package. will this not work?
if not, how do I replace it with the right recovery if I cant even get into the phone?

jimjenkins said:
i am using the tenfar CWM included in the Atrix 4G Automatic Unlock script package. will this not work?
if not, how do I replace it with the right recovery if I cant even get into the phone?
Click to expand...
Click to collapse
no, that the old recovery you can use the rom manager if you have , or romracer latest recovery you can find that in the development section, also ther was instruction in the cm7 thread.

you should have left it alone at the M boot screen because it takes about 5-10min to boot after unlock and flash...
everything you do now will have to be through fastboot DO NOT SBF FLASH ANYTHING!!!
Go here to use Fastboot
then download the system.img and boot.img from here
use fastboot to push the boot.img and system.img to your phone
if it gets stuck at the M boot screen let it sit for at least 10min
EDIT: get Romracer recovery from here and push that through to your phone through fastboot

Yeah youre going to have to fastboot wipe recovery then fastboot flash recovery recovery.img
Just download rom racers and rename it..recovery.img
Sent from my GT-I9100 using xda premium

Great. Sorry to be such a noob, but do I decompress the CWM-recovery-atrix5.zip file and push the recovery.img file that's inside it? or push the CWM-recovery-atrix5.zip itself?
Also - every time I am able to get my phone into fastboot mode, it says my battery is too weak to flash anything. I cant seem to get the battery to charge enough to execute any fastboot commands. Any way around this? a powered usb hub?

jimjenkins said:
Great. Sorry to be such a noob, but do I decompress the CWM-recovery-atrix5.zip file and push the recovery.img file that's inside it? or push the CWM-recovery-atrix5.zip itself?
Also - every time I am able to get my phone into fastboot mode, it says my battery is too weak to flash anything. I cant seem to get the battery to charge enough to execute any fastboot commands. Any way around this? a powered usb hub?
Click to expand...
Click to collapse
If you can borrow another Atrix user's battery, or take yours to an AT&T store and see if they can charge it for you.
If you're able to get back into recovery then you can just flash the zip.
If not, you'll need to extract the recovery.img to use it with fastboot, or just download it directly from the OP in romracer's thread. (The left hand link is just the .img, the right hand side is the CWM .zip) Then place it in the same directory as fastboot.

So I can literally flash a different recovery from within another?

jimjenkins said:
So I can literally flash a different recovery from within another?
Click to expand...
Click to collapse
yes but it MUST be working proper first ! its ok to use rom managers cwm but i just prefer the otherone alawys have but n e way there are only 2 that are current (uptodate )
thoughs 2 and with romracers you can. chose
a color that you like not just blue
Sent from my MB860 using xda premium

Its the recovery from tenfar CWM. When I can get it into recovery it seems to be working - with the obvious exception of successfully installing CM7
So I can flash romracer recovery from inside tenfar recovery?
sorry if im being redundant - just dont want to screw it up!
thanks

Just download rom racers cwm. Img, head into fastboot and then fastboot flash recovery recovery-****** (whatever yer recovery image color u chose is)
Sent from my MB860 using Tapatalk

I was able after a full day of leaving the phone plugged in, to charge it up. Then I flashed the rom racer recovery, rebooted into recovery (new version), installed CM7, installed gapps, and voila! A working CM7 Atrix. thank you soo soo much guys.

Can't boot android/recovery
ClearFire said:
you should have left it alone at the M boot screen because it takes about 5-10min to boot after unlock and flash...
everything you do now will have to be through fastboot DO NOT SBF FLASH ANYTHING!!!
Go here to use Fastboot
then download the system.img and boot.img from here
use fastboot to push the boot.img and system.img to your phone
if it gets stuck at the M boot screen let it sit for at least 10min
EDIT: get Romracer recovery from here and push that through to your phone through fastboot
Click to expand...
Click to collapse
Please help!!!
The phone stuck in boot screen and overheat, then restart.
In recovery mode is just black screen.
Phone has Neutrino 2.6GT+ ROM whit Clemsyn's OC kernel 1.6GHz and it has unlocked bootloader.
Can I change the kernel without booting in os or recovery?
This problem show after I was extracting very big zip file and phone overheat.

firecode95 said:
Please help!!!
The phone stuck in boot screen and overheat, then restart.
In recovery mode is just black screen.
Phone has Neutrino 2.6GT+ ROM whit Clemsyn's OC kernel 1.6GHz and it has unlocked bootloader.
Can I change the kernel without booting in os or recovery?
This problem show after I was extracting very big zip file and phone overheat.
Click to expand...
Click to collapse
I am actually having this same problem.

My warranty-replacement (unrelated ear-piece failure) had 2.3.6 pre-installed. Thinking little of it, I unlocked the BL and rooted the phone as usual. After this, I tried to install a couple of the ROM's (Neutrino and Morrisoft) which I was most happy with on my previous Atrix.
After flashing either Neutrino or Morrislee's ROM, the phone hung on the M screen. Waiting approximately 30 minutes with no change, I pulled the battery.
When trying to enter recovery mode, the phone would state, "entering recovery mode..." Then go black.
I ended up using RSDLite and sbf flashing the stock 2.3.6 sbf file back to the phone. Then, I had to re-unlock the bootloader and re-root.
This never happened up to, and including 2.3.4, but did twice last night on these ROM's using 2.3.6, and I've flashed many ROM's and Kernels.
It happened to a lesser extent when trying to flash Clemsyn's stock enhanced kernel to the stock ROM, as I was able to enter recovery mode. Entering recovery mode, it would give errors: mounting cache, mounting system errors, and errors to accessing recovery and recovery log files.
Restore recovery would fail in this state, giving me the above errors as well.
Trying to mount the cache and system in recovery would fail. Trying to format cache and system then mounting these could occur temporarily, but would revert back to unmounted when a restore was attempted.
For these problems I pushed a recovery through fastboot.

Just one word: Fastboot. See if Fastboot works and flash everything from there. Or, as Alterna suggested, flash through RSDLite, but that a little dangerous and can brick your phone if you don't know what you are doing. Hope it helps.

Problem sloved!!!
Alterna said:
My warranty-replacement (unrelated ear-piece failure) had 2.3.6 pre-installed. Thinking little of it, I unlocked the BL and rooted the phone as usual. After this, I tried to install a couple of the ROM's (Neutrino and Morrisoft) which I was most happy with on my previous Atrix.
After flashing either Neutrino or Morrislee's ROM, the phone hung on the M screen. Waiting approximately 30 minutes with no change, I pulled the battery.
When trying to enter recovery mode, the phone would state, "entering recovery mode..." Then go black.
I ended up using RSDLite and sbf flashing the stock 2.3.6 sbf file back to the phone. Then, I had to re-unlock the bootloader and re-root.
This never happened up to, and including 2.3.4, but did twice last night on these ROM's using 2.3.6, and I've flashed many ROM's and Kernels.
It happened to a lesser extent when trying to flash Clemsyn's stock enhanced kernel to the stock ROM, as I was able to enter recovery mode. Entering recovery mode, it would give errors: mounting cache, mounting system errors, and errors to accessing recovery and recovery log files.
Restore recovery would fail in this state, giving me the above errors as well.
Trying to mount the cache and system in recovery would fail. Trying to format cache and system then mounting these could occur temporarily, but would revert back to unmounted when a restore was attempted.
For these problems I pushed a recovery through fastboot.
Click to expand...
Click to collapse
My problem like that and I use automated unlock tool to recover recovery, this recovery show some errors but I successfully flash cwm touch and reinstall Nutrition 2.6GT+

N7 stuck at loading screen, fastboot doesn't work, recovery mode doesn't boot.

I was running ParanoidAndroid perfectly until it crashed and not it gets stuck at the loading screen of the ROM (not the Google logo). I'm able to turn it off and get into Bootloader. From there if I choose Recovery mode, it gets stuck at Google logo.
If I plug it into the PC while in booatloader, it gets detected as "Android" but no driver (I'm sure I installed it before with the Toolkit). Toolkit just won't detect the device anymore, keeps getting stuck at the <waiting for device> command.
If I plug it into the PC while stuck at the ParanoidAndroid loading screen, I see MTP and Nexus in Device Manager but w/o drivers.
What can I do now? Any input is appreciated.
Thanks.

Bump.

Itaintrite said:
Bump.
Click to expand...
Click to collapse
Have you tried fastboot from the bootloader? Try this(assuming Windows):
-copy your recovery image of choice to your fastboot folder on your PC.
-boot to the bootloader with usb connected.
-open cmd window and navigate to fastboot folder
-type: fastboot boot insertrecoverynamehere.img
It should boot into the recovery from there. Make sure it's the same recovery you used for your latest backup.
Edit: I just read the subject line saying fastboot didn't work. Odd that it would just stop working from the bootloader like that. Have you tried manually updating the driver? Or maybe adb when it recognizes the device as MTP?

Xentar712 said:
Have you tried fastboot from the bootloader? Try this(assuming Windows):
-copy your recovery image of choice to your fastboot folder on your PC.
-boot to the bootloader with usb connected.
-open cmd window and navigate to fastboot folder
-type: fastboot boot insertrecoverynamehere.img
It should boot into the recovery from there. Make sure it's the same recovery you used for your latest backup.
Edit: I just read the subject line saying fastboot didn't work. Odd that it would just stop working from the bootloader like that. Have you tried manually updating the driver? Or maybe adb when it recognizes the device as MTP?
Click to expand...
Click to collapse
Thanks for the suggestion, but I figured out the problem. I'm such a dumbass. I forgot that last time I did this on a friend's computer. Apparently, the toolkit doesn't work properly on Windows 8 64-bit... (at least not on mine). I plugged it into a friend's laptop running W7 and was able to flash recovery again. Smooth sailing from there. Wonder what corrupted recovery.

Itaintrite said:
Thanks for the suggestion, but I figured out the problem. I'm such a dumbass. I forgot that last time I did this on a friend's computer. Apparently, the toolkit doesn't work properly on Windows 8 64-bit... (at least not on mine). I plugged it into a friend's laptop running W7 and was able to flash recovery again. Smooth sailing from there. Wonder what corrupted recovery.
Click to expand...
Click to collapse
I've never been able to cold boot my recovery - only through the goomanager app(for TWRP). I believe it's a known bug. I can only boot recovery from the bootloader when my N7 is plugged into my laptop via usb. Power or another laptop don't count. Oddly enough, It also works if I plug it into my Galaxy Nexus via USB+OTG.

Xentar712 said:
I've never been able to cold boot my recovery - only through the goomanager app(for TWRP). I believe it's a known bug. I can only boot recovery from the bootloader when my N7 is plugged into my laptop via usb. Power or another laptop don't count. Oddly enough, It also works if I plug it into my Galaxy Nexus via USB+OTG.
Click to expand...
Click to collapse
Hm, perhaps that was the problem? But I was able to cold boot into recovery after reflashing TWRP... Anyhow, I'm glad I didn't have to restore a recovery image as I haven't made a backup since the last PA update

Itaintrite said:
Hm, perhaps that was the problem? But I was able to cold boot into recovery after reflashing TWRP... Anyhow, I'm glad I didn't have to restore a recovery image as I haven't made a backup since the last PA update
Click to expand...
Click to collapse
It worked for me only once after reflashing the recovery. Never again after that. Hopefully it gets fixed soon, but until then, I carry my USB cables with me if I'm flashing new roms
Sent from my Nexus 7 using Tapatalk 2