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?

I bricked my Nexus S. Please help.

I tried looking around the forums to see if someone has had this problem before. Couldn't find something similar.
I had stock 4.0.3 installed and I saw today that 4.0.4 was being pushed out. Since 4.0.3 wasn't a stock build I tried to downgrade to 2.3.6 in order to keep everything stock. I rooted the phone, installed the ROM Manager and flashed 2.3.6 through Clockworkmod Recovery. Everything went smoothly but when I powered on the phone force quit messages kept popping up and I can't get past the welcome screen. When I go into Fastboot mode and try to go in Recovery mode it just shows the Android symbol and a warning sign. I tried flashing a recovery .zip file I found online through fastboot but couldn't manage to do it (I'm on Mac OSX)
Can someone please help me? I'm completely desperate and wouldn't care about erasing everything (I think I already did, actually).
Thanks in advance.

flash a recovery.img
that multiple fc happened to me when i installed a i9023 rom on my i9020a.
unzip the recovery.zip and flash the .img file through fastboot and make sure you have the right rom for your model

Thank man, but that's what I tried to do. I got confused and wrote that it was a .zip up there. I'm really confused and couldn't flash the .img. Could you walk me through it? or point me to a thread that shows me how to do it?

im not sure how a mac is set up, i can walk you through flashing it on windows through command prompt ...

Please do that. I guess I can try to work it out.
Thanks

http://nexusshacks.com/nexus-s-root/how-to-root-nexus-s-or-nexus-s-4g-on-ics-or-gingerbread/
memorize that lol it saved me.
you can skip the root part, but it explains how to set up the pc so it'll read the nexus with the correct drivers and whatnot, and what commands to run to flash the recovery. then when youre in the recovery, mount as usb, copy over 2.3.6 (the right one!) and install from zip.

I just tried that. I get this message: "error: cannot load 'twrp-crespo-2.0.0RC0.img'" I don't know what to do!

Can you get into boot loader mode?
Have you tried to use Odin?
http://forum.xda-developers.com/showthread.php?t=947950&highlight=odin
Sent from my Nexus S 4G using XDA Premium App

colettamiguel said:
I just tried that. I get this message: "error: cannot load 'twrp-crespo-2.0.0RC0.img'" I don't know what to do!
Click to expand...
Click to collapse
Did you unlock your bootloader?
Code:
fastboot oem unlock

Stuck in AP Fastboot It says Load kernel (boot) failed Fastboot Reason: Boot Failure

Hi all
Well I bricked my phone and I'm stuck in AP Fastboot. When I try to start the phone (boot it up from off) It gets as far as the M logo then enters AP fastboot or it might even go directly to fastboot.
What I was doing: I was trying to use Matt's Droid RAZR M utility 1.20 option 1 to go back to stock 4.1.2. That's when my problems started. I had nearly 70% battery when i started (now it says "low battery").
Phone set up: Droid RAZR M 4.1.2; Rooted; Locked bootloader; Safestrap 3.12 and backed up; stock slot was still stock and ROM slot 1 was running Eclipse Custom ROM. To be honest I cant remember if i was back in stock ROM slot or ROM slot 1 when I attempted to use Matt's Utility. And I didn't uninstall Safestrap nether prior to using the utility. Don't know how much those factors played into causing my problem.
What I have tried: I have tried RSD Lite 6.1.4 with xml.zip files from the Droid-Developers SBF web site. But i keep getting this fail message, "Failed flashing process. 1/19 flash partition "gpt_main0.bin" -> Phone returned Fail."
I have tried manually pushing the recovery.img, boot.img and system.img file onto the phone via cmd.exe and it fails with this message for all three attempts, "Battery Low!!" "FAILED (remote failure)".
I have tried Matt's Utility option 1 I get multiple fail messages, "Failed to erase partition", "FAILED (remote failure)", "Failed to flash partition boot", "Failed to write mmc".
I even purchased one of Team Black Hats Factory Programing Adapters (little red adapter) That acts like a factory programing cable (they said they don't sell the cable any more cause the red adapter does the same thing for cheaper).
With the adapter connected I still get the same fail messages in RSD Lite, Matt's Utility, and cmd.exe prompt. I was under the impression that the factory programing cable (adapter) would solve my low battery issue.
Any help would be great. Thank you in advance.
PS: Also, I did not take the last OTA update from a few weeks ago. I was planning to unlock my bootloader. And my computer is a Windows XP (sp3). Thanks Again.

SARM1084 said:
Hi all
Well I bricked my phone and I'm stuck in AP Fastboot. When I try to start the phone (boot it up from off) It gets as far as the M logo then enters AP fastboot or it might even go directly to fastboot.
What I was doing: I was trying to use Matt's Droid RAZR M utility 1.20 option 1 to go back to stock 4.1.2. That's when my problems started. I had nearly 70% battery when i started (now it says "low battery").
Phone set up: Droid RAZR M 4.1.2; Rooted; Locked bootloader; Safestrap 3.12 and backed up; stock slot was still stock and ROM slot 1 was running Eclipse Custom ROM. To be honest I cant remember if i was back in stock ROM slot or ROM slot 1 when I attempted to use Matt's Utility. And I didn't uninstall Safestrap nether prior to using the utility. Don't know how much those factors played into causing my problem.
What I have tried: I have tried RSD Lite 6.1.4 with xml.zip files from the Droid-Developers SBF web site. But i keep getting this fail message, "Failed flashing process. 1/19 flash partition "gpt_main0.bin" -> Phone returned Fail."
I have tried manually pushing the recovery.img, boot.img and system.img file onto the phone via cmd.exe and it fails with this message for all three attempts, "Battery Low!!" "FAILED (remote failure)".
I have tried Matt's Utility option 1 I get multiple fail messages, "Failed to erase partition", "FAILED (remote failure)", "Failed to flash partition boot", "Failed to write mmc".
I even purchased one of Team Black Hats Factory Programing Adapters (little red adapter) That acts like a factory programing cable (they said they don't sell the cable any more cause the red adapter does the same thing for cheaper).
With the adapter connected I still get the same fail messages in RSD Lite, Matt's Utility, and cmd.exe prompt. I was under the impression that the factory programing cable (adapter) would solve my low battery issue.
Any help would be great. Thank you in advance.
PS: Also, I did not take the last OTA update from a few weeks ago. I was planning to unlock my bootloader. And my computer is a Windows XP (sp3). Thanks Again.
Click to expand...
Click to collapse
http://www.droidrzr.com/index.php/t...not-going-into-recovery-no-os-on-phone/page-2
Found by
https://www.google.com/search?num=1...j1.6.0....0...1c.1.26.serp..6.0.0.Dd8aoiu_UJI

Thank you for offering help. Will try your suggestions.
Sent from my XT907 using Tapatalk 2

[SOLVED] I was able to get some more help on another forum. My problem was a corrupted utility. I was instructed to perform a md5 check sum on my version if Matts utility. I compared my results to the original file on batakang Web site. That's when I realized my file was no good. So I deleted it an downloaded a clean uninterrupted copy of Matts utility 1.20 and it worked perfectly. I hope this will help other people too. Thanks for your help my friend.
Sent from my XT907 using Tapatalk 2

[Q] In Bootloop, Can you Help?

I was having some pretty serious radio issues with cyanogenmod so I attempted to use RSD Lite which had previously worked like a charm to go back to stock rom (using what came pre-bundled with matt's script v. 1.2)
My phone is unlocked at the bootloader
I have it rooted.
I get the original droid boot loop.
I can definitely get it into a status code 3 AP Fastboot, but none of the tools for the script or RSD lite have gotten me past the droid eye bootloop.
I'm presuming a wipe of the cache will do the trick, but either my googling skills are gone or I'm just too tired after 6 hours.... but I'm unable to get any type of recovery flashed.
My first question is if I am in AP Fastboot, who knows how to get a recovery image flashed so I can see if it's just a cache issue of trying to go from cyanogenmod to stock firmware.
My second question is - Does anyone have a link to a guide to "re-lock" my bootloader in case I need to get this to tech support?
Thanks

matthew1429 said:
I was having some pretty serious radio issues with cyanogenmod so I attempted to use RSD Lite which had previously worked like a charm to go back to stock rom (using what came pre-bundled with matt's script v. 1.2)
My phone is unlocked at the bootloader
I have it rooted.
I get the original droid boot loop.
I can definitely get it into a status code 3 AP Fastboot, but none of the tools for the script or RSD lite have gotten me past the droid eye bootloop.
I'm presuming a wipe of the cache will do the trick, but either my googling skills are gone or I'm just too tired after 6 hours.... but I'm unable to get any type of recovery flashed.
My first question is if I am in AP Fastboot, who knows how to get a recovery image flashed so I can see if it's just a cache issue of trying to go from cyanogenmod to stock firmware.
My second question is - Does anyone have a link to a guide to "re-lock" my bootloader in case I need to get this to tech support?
Thanks
Click to expand...
Click to collapse
First off, after you flash the firmware via fastboot, go back into recovery and do a factory reset. Second, you can't relock the bootloader.

thanks for responding. I wish it was this easy - it's been caught in a loop after trying factory again. I think I'd be able to resolve this if there were a way to wipe everything clear and build from scratch

RikRong said:
Second, you can't relock the bootloader.
Click to expand...
Click to collapse
No you cannot relock the bootloader...
Download this http://forum.xda-developers.com/showthread.php?p=40682385 chose option one... once flashed boot into recovery factory reset... boot up device... once booted root... install voodoo protect root install update restore root... install custom recovery if desired... I have boot looped I've been stuck at boot logo I've also been stuck with no data n WiFi this has saved me on more times then I can count on 3 separate devices and his utility n what I described has saved me more times then I can count...
Sent from my XT907 using xda app-developers app

I had some issues with aftermarket recoveries and formatting. I'm not sure if you've had any luck or if this is even helpful but assuming you are in fastboot and have the SDK set up...
Extract the stock sbf/XML and grab the recovery image.
At command line enter: "fastboot flash recovery recovery.img"
Reboot with all three buttons and select recovery.
Do factory reset.
Get back into fastboot
And repeat the command above (with different recovery obviously) to reflash a recovery of your choice.
(The official Philz cwm touch posted recently in development subforum works very well with the new 4.3 ROMs)
Hope that helps...if its too basic, please disregard! Good luck.
Sent from my XT907 using Tapatalk 2

[Q] Recovery Broken (Secure Booting Error)

Hello, I had been using my AT&T g2 with TWRP 2.6.3.2 just fine for months but since attempting to upgrade to 2.6.3.3 (for Kit Kat) I have been unable to boot into recovery. I tried to do the automatic install as shown in http://forum.xda-developers.com/showthread.php?t=2472223 and began to receive a "secure booting error" upon attempting to boot to recovery, followed by what I assume to be a download mode where the screen turns black and connects as an unformatted drive to my computer. I then attempted manual install on my phone via terminal emulator as described in aforementioned thread with no luck, and have even downloaded the CWM recovery from the play store, installed that recovery, and still have the same problem with being unable to boot into recovery. I have attempted to flash the recovery file with flashify as well, to no avail.
After getting stuck at the black screen instead of a welcome recovery menu, I am able to hold down my power button, shut off my phone, and reboot into CM where everything works just fine.
I'd appreciate help as to how I might be able to restore my recovery partition. Thank you.
Edit: The exact error is "Boot Certification Verify" which appears in the upper left corner on the LG logo boot screen.
The TWRP Recovery Auto Installer shows this in the command prompt when trying to install:
Install Recovery...
1410 KB/s (67688 bytes in 0.046s)
4189 KB/s (67020 bytes in 0.015s)
3696 KB/s (8931328 bytes in 2.359s)
/dev/block/platform/msm_sdcc.1/by-name/aboot: cannot open for read: Permission d
enied
Unable to chmod /data/local/tmp/aboot.img: No such file or directory
[+] loki_patch v2.1
[-] Failed to open /data/local/tmp/aboot.img for reading.
[+] loki_flash v2.0
[-] Failed to open aboot for reading.
Press any key to Reboot into recovery or disconnect USB cable from PC now...
Click to expand...
Click to collapse

I'm having the same issue for my ATT G2. Someone please help.
Sent from my KFTT using xda app-developers app

Fixed!
Follow the thread attached below this response and you'll be all set. The link to the LG flash tools is the incorrect file, but a quick google search will give you what you need (top 3 results for me proved fruitful).
I restored to the stock firmware following the instructions of the thread and then rooted, installed TWRP, and flashed CM quite easily.
http://forum.xda-developers.com/showthread.php?t=2432476
Click to expand...
Click to collapse
:good:
The Lg mobile launcher technique described below led to nothing but wasted time, as the application would crash on windows 8.1 & XP. I do not advise even attempting this one, linked below.
http://forum.xda-developers.com/showthread.php?t=2471370&highlight=lg+tool
Click to expand...
Click to collapse

I currently have this identical problem as described in OP. Is there any way to fix this without having to completely restore stock, reroot and install twrp again? It seems somewhat overkill.
EDIT: Nevermind, I figured it out. I found the old version of twrp 2.6.3.2 still on my computer. Re-flashed that, using the option 2 from http://forum.xda-developers.com/showthread.php?t=2449670. It then worked fine when I rebooted in to recovery. I then flashed the zipped version of 2.6.3.3 from within twrp.

I have an odd issue, it's like the opposite of this. I can get into recovery but I cannot boot.
I have the Sprint G2. I downgraded to ZVE then OTA'd to ZVH.
I then rooted it.
I then flashed the zv7-aboot.img and used Flashify to flash twrp_2.6.3.3_loki-ls980.img
It rebooted into recovery, I flashed xposed-uninstaller-20160829-arm.zip
I rebooted and I got a Secure Boot Error, and it then goes to that grayish/black screen that people talk about, and shows up as the unformatted drive.
Any ideas?

I would guess that you'd be able to flash a different ROM since you can get into recovery.
For me, I had an issue where I couldn't get into download mode (I'd get the secure boot error), couldn't get into recovery, couldn't boot the device and Windows was showing it as a bunch of unformatted drives. Now, there's a large guide you'll find on here about using Linux to push images (boot.img etc.) to your device to repair whatever happened to it to get it into that state.
That didn't work for me at all (there's probably something I was doing wrong since it worked for a lot of other people). However, there's a tool called SRKTool (http://forum.xda-developers.com/lg-g2/development/tools-srk-tool-useful-toos-lg-root-twrp-t3079076) that I used to do this from Windows that did work for me. You might want to give it a shot.
mxpxboi said:
I have an odd issue, it's like the opposite of this. I can get into recovery but I cannot boot.
I have the Sprint G2. I downgraded to ZVE then OTA'd to ZVH.
I then rooted it.
I then flashed the zv7-aboot.img and used Flashify to flash twrp_2.6.3.3_loki-ls980.img
It rebooted into recovery, I flashed xposed-uninstaller-20160829-arm.zip
I rebooted and I got a Secure Boot Error, and it then goes to that grayish/black screen that people talk about, and shows up as the unformatted drive.
Any ideas?
Click to expand...
Click to collapse