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?

Help with a unique D802T brick? (bad partition?)

So I've got my (recently purchased T_T) Australian G2 (D802T) in a bit of a pickle. Here's the story of my rapid descent into idiocy: Rooted with ioroot (went fine), installed TWRP via autorec (whoops!). From here I installed several roms but none would boot past optimizing apps - after some further reading this is apparently a known issue with the D802T.
From here I followed the instructions at http://forum.xda-developers.com/showthread.php?t=2432476 and successfully reset back to stock firmware using a D802T kdz I found online. On first boot the phone asked for a decryption pin, which I fixed by booting to the stock recovery and letting it do its thing. However, it seems that the image was for the 16GB version - I was left with only 10GB accessible space.
This is where I got double stupid - I followed about half of http://www.droidviews.com/your-32gb-lg-g2-shows-only-16gb-storage-space-heres-the-fix/ to fix the issue, but rather than copying over the blank images and re-imaging the firmware again, I tried to get clever by growing the userdata partition manually. Unfortunately it seems that I screwed up, since on next boot I once again had the decryption lock, and now neither the factory reset nor re-flashing the firmware will fix it. The last thing I tried tonight was installing the LG Mobile Support Tool and letting it automatically download and install the firmware, but it seems to be in the exact same condition. Apparently the kdz re-imaging (even CSE Flash) doesn't actually reformat anything... :/
Any ideas? I have access to:
download mode
stock recovery/factory reset screen
bootable stock ROM that locks me out due to thinking it's encrypted, when in fact it's just an incorrect partition table.
Is there any way to get adb access back? Or perhaps to get the phone in to some kind of usb mass storage mode as described in http://forum.xda-developers.com/showthread.php?t=2582142 ? As it is it's only recognized by linux as a serial device - if I could get rw access to the raw storage I think I could fix it up pretty easily.

Does anyone know of any way to get adb or fastboot working in this situation? All I can think of is to flash the kdz again and pull the usb out in attempt to break it even further, as I've read that the phone goes to fastboot or qhsusb_bulk when a boot partition is corrupted; but this seems very foolhardy.
How exactly do kdz flashes work? Is there any way to feed it a kdz file that will reformat the userdata partition correctly, or is that just never going to happen?

amdpox said:
Does anyone know of any way to get adb or fastboot working in this situation? All I can think of is to flash the kdz again and pull the usb out in attempt to break it even further, as I've read that the phone goes to fastboot or qhsusb_bulk when a boot partition is corrupted; but this seems very foolhardy.
How exactly do kdz flashes work? Is there any way to feed it a kdz file that will reformat the userdata partition correctly, or is that just never going to happen?
Click to expand...
Click to collapse
maybe you should first try downloading your kdz from here and trying that.
You don't want to be in qhsusb bulkmode, but if you want fastboot access you could run this command in your terminal
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/laf
to nuke your laf partition and get fastboot through your button combination. But then you might be asking for a hardbrick.

Art Vanderlay said:
maybe you should first try downloading your kdz from here and trying that.
Click to expand...
Click to collapse
Doubt it'll be much different but I'll give it a shot, thanks.
You don't want to be in qhsusb bulkmode, but if you want fastboot access you could run this command in your terminal
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/laf
to nuke your laf partition and get fastboot through your button combination. But then you might be asking for a hardbrick.
Click to expand...
Click to collapse
I don't have adb access or a custom recovery, so I can't run that command - in fact if I can get a shell open on the device at all I think I'd be most of the way to a fix. Why don't I want to be in bulkmode? It seems to me like exactly what I need - raw access to the internal memory as a block device.

amdpox said:
Doubt it'll be much different but I'll give it a shot, thanks.
I don't have adb access or a custom recovery, so I can't run that command - in fact if I can get a shell open on the device at all I think I'd be most of the way to a fix. Why don't I want to be in bulkmode? It seems to me like exactly what I need - raw access to the internal memory as a block device.
Click to expand...
Click to collapse
It's a last resort and it leaves very little margin for error. If you try to force your way into it by yanking out your cable or something you might find yourself hardbricked.
If you flashed a 20D kdz the method for entering hard reset is vol - power then vol up + vol - on lg logo maybe thats why you can't get in now.

Art Vanderlay said:
It's a last resort and it leaves very little margin for error. If you try to force your way into it by yanking out your cable or something you might find yourself hardbricked.
If you flashed a 20D kdz the method for entering hard reset is vol - power then vol up + vol - on lg logo maybe thats why you can't get in now.
Click to expand...
Click to collapse
Fair enough. It feels like I'm at the point of last resort, though.
I tried that 20D kdz, seems to be in the same state. (I'm guessing that's exactly the image that the automated support tool downloaded and flashed.)

Is this fixed ?

bender_007 said:
Is this fixed ?
Click to expand...
Click to collapse
Sadly not. Totally stuck for ideas here... anyone know anything more sensible to try than the cable-pulling?

OP2 no system and no roms on the sd card(adb doesnt find device/fastboot does)

Hi guys,
yesterday I accidentally wiped my phone and the rom's in it. So now I have to somehow get a rom on the sd card so I can flash it. Recovery works (twrp), fastboot mode works, however I can't use adb to push zips on to my sd card, I've tried on 3 different PC's 2xWindows and one mac
fastboot finds my device and adb doesn't. I've tried configuring the adb_usb.ini file with the Vendor ID of my device which I found, but adb still doesn't find it. My system is wiped so I don't have a system to go in and transfer files the normal way and my backups have been deleted so that isnt working either. I've also tried to return my phone to 100% stock with a tool I found on the OnePlus forums Thread from forum , however this didn't work fastboot crashes midway. My only option is to flash an .img file containing some system rom(which I didn't find) so I can then load files to my sd card or to get adb to work in some way so I can push the zips on to the sd card. If you can help in any way because I'm all out of ideas. It's been two hard days and this is the last thing I'm trying, otherwise I have to buy a new phone.

It's not soft bricked but I think the first method shown here could work:
https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/

Sounds like your trying to access your phone using ADB in fastboot, this will not work. For ADB recovery, you have to enter TWRP or CWM and choose ADB sideload mode to activate phone for receiving of ROM zip using adb sideload romfile.zip. Fastboot is like EFI or BIOS boot prompt on a PC, and ADB is like a variant of GRUB bootloader with support for PXE installing the phones OS by ways of adb sideload (as reference).

Stuck in fastboot loop-HELP!

I was in the middle of a restore in twrp and the phone shut off in the middle of the restore (while restoring recovery), and had such, my android system will no longer boot, nor can I get into recovery. It simply goes into fastboot mode and that's all. Is there a way to flash twrp (Archlinux?) using fastboot/adb?
Thank you in advance!

533y4 said:
I was in the middle of a restore in twrp and the phone shut off in the middle of the restore (while restoring recovery), and had such, my android system will no longer boot, nor can I get into recovery. It simply goes into fastboot mode and that's all. Is there a way to flash twrp (Archlinux?) using fastboot/adb?
Thank you in advance!
Click to expand...
Click to collapse
Depends on what variant you have. If its a dirtysanta one while in fastboot do
Code:
fastboot flash recovery (twrpimgnamehere).img
and it will install the twrp image you have downloaded. If you are on TMO you need to revert to stock using a KDZ and then re root.

Fastboot commands aren't working on the H918? My model... -_-
What's the difference between recowvery and dirtysanta?

OK. So let me ask this then. If fastboot commands don't seem to do much on the H918, then how does one go about backing up the internal storage before being formatted? Is there like a dd command to copy everything over? Or will the phone still attach storage to the PC when attached, even in fastboot?
In other words, how can I backup my internal storage before reseting to stock?

533y4 said:
Fastboot commands aren't working on the H918? My model... -_-
What's the difference between recowvery and dirtysanta?
Click to expand...
Click to collapse
The difference between recowvery and dirtysanta is multiple things. One thing is the fact that recovery goes after the recovery directly and dirtysanta replaces the bootloader itself. IF you use dirtysanta on a H918 you WILL BRICK. non recoverable. Dirtysantas boatloader is a debug bootloader that has full access to the phone. H918 bootloader only has limited commands available.
The other difference is how the methods goes about actually doing everything. Jcadduonos recowvery attacks recovery uses scripts to start a factory recovery installer/updater but makes it install a temp root instead of a recovery then the device has access to fully install a twrp image. Dirtysanta skips that and attacks the bootloader directly by replacing a higher level function of the phone temporarily that has access to the phones bootloader(for some unknown reason) and replaces it with the debug one. Once the debug one is in the device is able to be rooted like any other device with an unlocked bootloader since it has full access.
533y4 said:
OK. So let me ask this then. If fastboot commands don't seem to do much on the H918, then how does one go about backing up the internal storage before being formatted? Is there like a dd command to copy everything over? Or will the phone still attach storage to the PC when attached, even in fastboot?
In other words, how can I backup my internal storage before reseting to stock?
Click to expand...
Click to collapse
You don't. you can copy everything manually but If you backup the data partition(which has your internal storage inside) it will not be usable on the device after you root. If you do manage to back it up then restore it afterward since the device itself is normally encrypted and is now decrypted the settings and stuff will cause crashes and force closes.

me2151 said:
The difference between recowvery and dirtysanta is multiple things. One thing is the fact that recovery goes after the recovery directly and dirtysanta replaces the bootloader itself. IF you use dirtysanta on a H918 you WILL BRICK. non recoverable. Dirtysantas boatloader is a debug bootloader that has full access to the phone. H918 bootloader only has limited commands available.
The other difference is how the methods goes about actually doing everything. Jcadduonos recowvery attacks recovery uses scripts to start a factory recovery installer/updater but makes it install a temp root instead of a recovery then the device has access to fully install a twrp image. Dirtysanta skips that and attacks the bootloader directly by replacing a higher level function of the phone temporarily that has access to the phones bootloader(for some unknown reason) and replaces it with the debug one. Once the debug one is in the device is able to be rooted like any other device with an unlocked bootloader since it has full access.
You don't. you can copy everything manually but If you backup the data partition(which has your internal storage inside) it will not be usable on the device after you root. If you do manage to back it up then restore it afterward since the device itself is normally encrypted and is now decrypted the settings and stuff will cause crashes and force closes.
Click to expand...
Click to collapse
Very interesting how different the two are and how they work. Very interesting indeed.
As for the data partition, mine is already decrypted as is (was rooted already and tried to install a cm rom to test; ended up glitches during restore). But I have no intentions on restoring an backups. I simply want my photos, saves, books, etc off the actual internal SD storage (not my external SD card, obviously).
My question here I guess is, will the internal storage mount while in fastboot mode the same as if the phone was on normal (adds a new drive (win)/mtp link (unix))?
I just want to copy and paste all the files off the internal storage on to my unix desktop. Then format the whole phone and start fresh again.

*bump*
I have tried to access the SD card while in fastboot mode. Absolutely nothing I do can make the PC see the internal storage on my V20. I have some files for my job on my internal SD card (NOT my external SD card, but the actual built in storage), that I absolutely, positively cannot afford to loose. These files are for my job. If I loose these files, I will loose my job.
Please, can someone tell me how to access the SD card in fastboot mode? It's really really important.
If anyone, at all, has any clue or any ideas on how to access the internal storage or how to restore my v20 without a full reset, then please please please help. Hell, I'll even be willing to donate some money to whoever can figure this out for me. Seriously, it's really that important that I get my files off the internal storage.
Thanks to anyone who can help.
P.s. I have access to Windows and Linux computers.

533y4 said:
*bump*
I have tried to access the SD card while in fastboot mode. Absolutely nothing I do can make the PC see the internal storage on my V20. I have some files for my job on my internal SD card (NOT my external SD card, but the actual built in storage), that I absolutely, positively cannot afford to loose. These files are for my job. If I loose these files, I will loose my job.
Please, can someone tell me how to access the SD card in fastboot mode? It's really really important.
If anyone, at all, has any clue or any ideas on how to access the internal storage or how to restore my v20 without a full reset, then please please please help. Hell, I'll even be willing to donate some money to whoever can figure this out for me. Seriously, it's really that important that I get my files off the internal storage.
Thanks to anyone who can help.
P.s. I have access to Windows and Linux computers.
Click to expand...
Click to collapse
can you let it boot up and will it just hang on the lg logo or is it rebooting into fastboot?
really my only advice would be try letting it hang on lg logo and see if adb is present, furthermore you can get a adb always moded boot.img and push that to the phone using fastboot then see if adb is a option.
If so you can do the adb commands to pull the userdata portion off the device the same way the system dumps are done i believe, but the sad fact is its probably all currupted anyway from your restore you were trying.
The other option is push recovery again to device, and then try a dirty flash of the stock rom, in hopes it can get the system partition back up and running,
furthermore, worst case wipe all and flash the rom, once its back up and running, download diskdigger from playstore and see if it can recovery the deleted stuff, or try the phonedoctor program for windows that runs against your internals and trys to recocvery stuff..
The biggest question is why were you flashing your device without saving stuff thats "soooo important and can cost you your job" ? seems like a oversight on your part really, and a lesson learned. Backup work stuff always, and dont play with roms during work days lol, not to be mean but really, why risk your job and lively hood over some unsaved stuff?

I did actually have a back up on my S6, which I dropped and broke a mere hour before this. So it's not at all an oversight. There were backups in place. And it won't boot at all or I'd had been able to get adb Atleast. ADB won't see the v20 and I tried to flash recovery using fastboot flash recovery recovery.img command. It says unknown.
How can one going about flashing such a boot.img in the H918? Where can one find such things? I assume you mean a kernel of some sort, right?
I truly appreciate the reply. Has I said, it's not like I didn't have backups. I did. It really is an issue of bad luck. : (

i tried this it worked https://forum.xda-developers.com/v20/help/lg-v20-access-to-fastboot-t3557328

Have you tried power on and volume down to go through the factory reset screens.
A bunch of us had this problem and it was because an update downloaded on it's own and the bootloader snoops it out and forces recovery to boot.
Just do the volume down + power button - as soon as you see the lg logo release power only then immediately re-press power and continue holding power and volume down until the factory reset screen pops up. Select yes and yes, (don't worry - if you have twrp recovery it can't reset). It will boot you into TWRP and I'm pretty sure it will delete the update files in fota folder.
In TWRP select reboot - system and it should boot normally like nothing happened.

[SOLVED] zc553kl - Does not open recovery mode

Well, as every good person was trying to get root access from my device and all the tutorials I was seeing told me that it would be necessary to unlock the bootloader so that I could install a superior room, android 8, and unlock the cell phone - so I followed my walk and I was trying various tutorials, I could list the links here, but it would not work.
Well, what was the game change was this:
https://eusouandroid.co/voltar-zenfone-3-para-o-android-marshmallow-6-0/
Which is basically based on running a flash recovery and a flash boot. After the procedure the cell decided to stay a reboot loop, that is, it loaded the android screen, loaded the asus screen and rebooted.
Searching in the forums I saw that it would be necessary to perform an update via recovery mode, so I downloaded the version correctly for my boot and recovery, I passed the data to the memory card and went to access my recovery mode, however, Access keys to recovery mode is the same as doing nothing.
The cell phone has decided that it will no longer open recovery mode and I do not know how to solve it.
In the middle of the way I realized one:
fastboot erase cache
fastboot erase recovery
fastboot erase boot
And without wanting a fastboot erase system.
I think my solution starts by putting the system files back into the phone and following this tutorial here:
https://forum.xda-developers.com/zenfone-3/help/unbricking-zenfone-3-ze552kl-dm-verity-t3563970
I created the files and would perform the procedure as described, however by the time I should open the recovery mode saint nothing happens while holding the keys and I do not know what options I have anymore.
Does anyone know of any way to regain access to recovery?
I already tried to flash the twrp indicated for the device in the tutorials, but the recovery still does not open.
At the moment I have an electronic block that sheer lack of knowledge has arrived in this state.
At the moment I only have access to fastboot
Thanks in advance!
EDIT: It looks like I was sabotaging myself, the model of the device is zc553kl. I still could not figure it out, but I was headed in the wrong direction.
EDIT: I was using the incorrect version of the device to flash the information, after updating the post with the version of the device I was able to find the correct information on how to recover the cell and perform the root.
Thank you very much.