Database Users

Can you load a new recovery image via fastboot?

Something went haywire when trying to update Amon_RA's new recovery image. I now can't get into recovery and my ROM wont load. All I have is fastboot. I need to load a new recovery image to get into recovery but haven't been able to using the ADB. I've tried the various methods I've seen online with no success. Any advice?

I only rooted my phone around 6 hours ago, so I'm hoping this is what you meant. I was able to use fastboot to boot into a recovery ROM. Try using:
fastboot boot XXX.img
That should allow you to boot straight into it.

Yes I can...will you try copy recovery to SDK\tools?

Reavern said:
I only rooted my phone around 6 hours ago, so I'm hoping this is what you meant. I was able to use fastboot to boot into a recovery ROM. Try using:
fastboot boot XXX.img
That should allow you to boot straight into it.
Click to expand...
Click to collapse
Its a .zip file tho. I've tried "fastboot flash_image recovery..." command but it didn't work.
SarDroid...huh? What do you mean?

staunty said:
Its a .zip file tho. I've tried "fastboot flash_image recovery..." command but it didn't work.
SarDroid...huh? What do you mean?
Click to expand...
Click to collapse
I think you can only flash official images using fastboot. I'm you can use "fastboot boot recovery.img" to load something like Cyanogen's recovery image you will get ADB access. From there you should be able to flash anything.

put recovery in your sdk tools folder
and boot to fastboot
and
fastboot flash recovery recoveryxxxx.img
also check Amon_RA's post where you got the recovery from it tells you how to do it

sitimber said:
put recovery in your sdk tools folder
and boot to fastboot
and
fastboot flash recovery recoveryxxxx.img
also check Amon_RA's post where you got the recovery from it tells you how to do it
Click to expand...
Click to collapse
OK, I'm still not having any luck. Here is what I've done...I found the .img file for a previous recovery image. All the newer ones seem to be .zip files. For the recovery image, it won't recognize a .zip. So, I put the "recovery-RA-dream-v1.3.2.img" image in my AndroidSDK\tools\ folder. Then, in fastboot, I did "fastboot flash recovery..." and it said okay. Rebooted but it still didn't reboot to recovery when I held down home button.

staunty said:
OK, I'm still not having any luck. Here is what I've done...I found the .img file for a previous recovery image. All the newer ones seem to be .zip files. For the recovery image, it won't recognize a .zip. So, I put the "recovery-RA-dream-v1.3.2.img" image in my AndroidSDK\tools\ folder. Then, in fastboot, I did "fastboot flash recovery..." and it said okay. Rebooted but it still didn't reboot to recovery when I held down home button.
Click to expand...
Click to collapse
do
Code:
fastboot boot recovery.img
let the phone reboot, dont touch and anything. you could also try
Code:
fastboot flash recovery recovery.img

have you unzipped the zip files they mght just be .img inside

I have the same issue. but when I follow the steps to flash or boot the recovery.img cmd prompt just says
sending 'recovery' <4166 kb>... FAILED <remote: not allow> finished.
cd to sdk tools (placed recovery.img here)
fastboot boot recovery.img
fastboot flash recovery recovery.img
tried it again and

Install androidsdk and get a copy of a recovery image for your device. Copy the .img to the tools folder in \androidsdk and rename file to recovery.img (for simplicity later). Connect the phone to PC with USB. Power up phone while holding volume down. Get to fastboot USB, open up command prompt (elevated if vista or 7) and cd to androidsdk\tools. then "fastboot erase recovery" then "fastboot flash recovery recovery.img" then "fastboot reboot".

HI,
before begining you must put the android sdk in the root of the c;/, and suitch off your phone , and hold the back bouton and the end call bouton until you see the 3 android in your fone so ,you try this command to see if the pc reconize your phone :
C:\AndroidSDK>fastboot devices
List of devices attached
XXXXXXXXXXXX fastboot
if you cannot see your IMEI listed you must instal the drivers utilities on your pc
if you see the pc listed the IMEI ,then you can flash the recovery .img .
-Place the recovery image downloaded into the androidsk/tools folder and rename it to recovery.img and try with this command :
fastboot flash recovery recovery.img
that all good luke

Hi guys, how I can achieve this with S-ON? I can't flash SPL because I haven't sdcard and using ADB don't know, any help on this?

I have the exact same issue.
I only have fastboot access however I always get remote: not allow. ( Perfect SPL )
Phone Stats
HTC Magic 32A S-ON H
HBOOT 1.76.0010 (SAPP50000)
CPLD-12
RADIO 6.35.16.19
I have created a gold card and tried flashing a sappimg.zip file but that gave me wrong model ID.
Anyone have any idea what I can do?

Help!! Bricked!!

Alright first off, I can boot into recovery and bootloader. However, I have no CWM backups or any ROMs on my sd card.
I have no ROM currently installed so it will not get past the splash screen. I went into bootloader, but doing the command "adb devices" nothing is found.
I have tried using the Toolkits but it still doesn't recognize my device. It would just say "waiting for device" and nothing happens.
Any help would be appreciated.

kkl1993 said:
Alright first off, I can boot into recovery and bootloader. However, I have no CWM backups or any ROMs on my sd card.
I have no ROM currently installed so it will not get past the splash screen. I went into bootloader, but doing the command "adb devices" nothing is found.
I have tried using the Toolkits but it still doesn't recognize my device. It would just say "waiting for device" and nothing happens.
Any help would be appreciated.
Click to expand...
Click to collapse
the bootloader is for fastboot. i dont know about cwm, but twrp recovery has an adb sideload option. you connect to adb, press the button, type the command shown, and load the rom from your desktop to your device. you can fastboot the twrp recovery via your bootloader and fastboot.

Alternatively if you have an otg cable and a flash drive you should be able to flash the ROM through recovery via external SD.
Also on other devices I have flashed ROMs via fastboot, haven't tried on this but I'm sure it easy. If you have a nandroid on PC in the yaffs2 format then you can use this (most recoveries make tar backups which won't work through fastboot.
Boot to fastboot and open cmd in the folder of the nandroid, then type
fastboot erase system -w
fastboot erase boot
fastboot flash userdata data.img
fastboot flash system system.img
fastboot flash boot boot.img
fastboot reboot
If you don't have a nandroid on PC or its not yaffs2 then flash a update.zip
fastboot erase system -w
fastboot erase boot
fastboot update superawesomerom.zip
(Replace superawesomerom with the name of the ROMs .zip)
Again I've both methods with plenty of other android devices and it should work just fine with the nexus7 but haven't bothered to try. Will soon if anyone needs confirmation
Sent from my Nexus 7 using xda premium

demkantor said:
Alternatively if you have an otg cable and a flash drive you should be able to flash the ROM through recovery via external SD.
Also on other devices I have flashed ROMs via fastboot, haven't tried on this but I'm sure it easy. If you have a nandroid on PC in the yaffs2 format then you can use this (most recoveries make tar backups which won't work through fastboot.
Boot to fastboot and open cmd in the folder of the nandroid, then type
fastboot erase system -w
fastboot erase boot
fastboot flash userdata data.img
fastboot flash system system.img
fastboot flash boot boot.img
fastboot reboot
If you don't have a nandroid on PC or its not yaffs2 then flash a update.zip
fastboot erase system -w
fastboot erase boot
fastboot update superawesomerom.zip
(Replace superawesomerom with the name of the ROMs .zip)
Again I've both methods with plenty of other android devices and it should work just fine with the nexus7 but haven't bothered to try. Will soon if anyone needs confirmation
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
I tried to do that but it seems like it wont communicate with my computer. all it says is fastboot: command not found

demkantor said:
Alternatively if you have an otg cable and a flash drive you should be able to flash the ROM through recovery via external SD.
Also on other devices I have flashed ROMs via fastboot, haven't tried on this but I'm sure it easy. If you have a nandroid on PC in the yaffs2 format then you can use this (most recoveries make tar backups which won't work through fastboot.
Boot to fastboot and open cmd in the folder of the nandroid, then type
fastboot erase system -w
fastboot erase boot
fastboot flash userdata data.img
fastboot flash system system.img
fastboot flash boot boot.img
fastboot reboot
If you don't have a nandroid on PC or its not yaffs2 then flash a update.zip
fastboot erase system -w
fastboot erase boot
fastboot update superawesomerom.zip
(Replace superawesomerom with the name of the ROMs .zip)
Again I've both methods with plenty of other android devices and it should work just fine with the nexus7 but haven't bothered to try. Will soon if anyone needs confirmation
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
also i do have an OTG cable and obviously a flash drive, how do i install a ROM through it

For fastboot you will either need to add a path for adb.exe and fastboot.exe in environmental variables or put files needed in same folder as fastboot.exe and of course have proper drivers
Haven't used clockwork for any android in years (not the biggest fan) but I believe when you choose to flash a zip it will allow you to choose where to, including an external SD.
if it doesn't use fastboot to flash twrp and that definitely does have the option. Of course you will need to get fastboot up and running
Sent from my Nexus 7 using xda premium

Nexus 7 Bricked??/Broken

Nexus 7 was rooted,unlocked bootloader and was running paranoid anroid 3.90+ i think . i plugged it into the computer to get a new rom using nexus root toolkit v1.7.2. i was asked to update a few things, so i clicked yes. i then tried to flash stock + unroot and chose 4.3 cause i wanted to try the new OS. but i guess something happened because when i turned my nexus 7 back on i was stuck on the load screen (GOOGLE image with a unlocked lock) i could cycle thru a few options using volume keys (start,recovery,power off) .all of them seemed useless as they would just bring me back to where i was.when clicking start "booting failed" come up on the upper left side. when trying to flash stock +unroot using NRT i get up to the sending "bootloader" part and my nexus 7 just freezes, how do i fix this. please and thanks

download the factory image from the google factory image and extract the archive.
try flashing the bootloader manualy with fastboot.
locate your fastboot binary and copy the bootloader image to that directory.
open a commandline in that directory and type
fastboot flash bootloader name-of-bootloader.img
after that you can try to flash the whole factory image with the flash-all.sh script.

Simple
dieselmonkeyy said:
i could cycle thru a few options using volume keys (start,recovery,power off) .all of them seemed useless as they would just bring me back to where i was.when clicking start "booting failed" come up on the upper left side.
Click to expand...
Click to collapse
Boot failed??? That's a bad flash of the stock ROM. I had the same problem at my first attempt trying to flash Stock ROM, but don't worry! Let's do this:
WARNING: Before you continue you are accepting that I'm not responsible of anything can happen to your Nexus and your battery is fully charged.
When you download the stock ROM you have to uncompress the zip file. You will find the bootloader and another zip.
Uncompress that zip file, put fastboot program, the bootloader and the files together.
Then start your Nexus into bootloader mode, connect it to your PC, open a console (cmd for Windows, Terminal for Linux and Mac OS X) and type this:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
WARNING: Your Nexus is FULLY EMPTY!!! Don't reboot it because it can get a full brick (It will not turn on any more).
Now type this:
fastboot flash bootloader bootloader-grouper-X.XX.img
NOTE: Replace X.XX with your version.
Now type:
fastboot reboot-bootloader
Your Nexus will reboot.
Type this:
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash system system.img #Will take a very long time. DON'T INTERRUPT THE PROCESS!!!!!
fastboot flash userdata userdata.img
Now reboot again with:
fastboot reboot-bootloader
Re-unlock bootloader to get a full wipe:
fastboot oem lock
Reboot again:
fastboot reboot-bootloader
And then unlock the bootloader:
fastboot oem unlock
Press "Yes" to the petition screen and reboot:
fastboot reboot
Ready the Nexus!
I had the same problem and I did this.
I hope I can help you.
Sorry for my bad English. I'm from Argentina and I'm learning.
Well,
Good luck!

MlucianoEze said:
Boot failed??? That's a bad flash of the stock ROM. I had the same problem at my first attempt trying to flash Stock ROM, but don't worry! Let's do this:
WARNING: Before you continue you are accepting that I'm not responsible of anything can happen to your Nexus and your battery is fully charged.
When you download the stock ROM you have to uncompress the zip file. You will find the bootloader and another zip.
Uncompress that zip file, put fastboot program, the bootloader and the files together.
Then start your Nexus into bootloader mode, connect it to your PC, open a console (cmd for Windows, Terminal for Linux and Mac OS X) and type this:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
WARNING: Your Nexus is FULLY EMPTY!!! Don't reboot it because it can get a full brick (It will not turn on any more).
Now type this:
fastboot flash bootloader bootloader-grouper-X.XX.img
NOTE: Replace X.XX with your version.
Now type:
fastboot reboot-bootloader
Your Nexus will reboot.
Type this:
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash system system.img #Will take a very long time. DON'T INTERRUPT THE PROCESS!!!!!
fastboot flash userdata userdata.img
Now reboot again with:
fastboot reboot-bootloader
Re-unlock bootloader to get a full wipe:
fastboot oem lock
Reboot again:
fastboot reboot-bootloader
And then unlock the bootloader:
fastboot oem unlock
Press "Yes" to the petition screen and reboot:
fastboot reboot
Ready the Nexus!
I had the same problem and I did this.
I hope I can help you.
Sorry for my bad English. I'm from Argentina and I'm learning.
Well,
Good luck!
Click to expand...
Click to collapse
what do i type into cmd inorder to be able to type
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
and get it to work. im a noob . thanks in advance

You have to be in the folder with fastboot inside else those commands will not work.
It will be easier if you put the images extracted from the zip into the zip together with the fastboot program.
If you don't understand yet I'll try to be more specific.
Sent from my Nexus 7 using xda app-developers app

dieselmonkeyy said:
what do i type into cmd inorder to be able to type
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
and get it to work. im a noob . thanks in advance
Click to expand...
Click to collapse
It can be intimidating... and the so-called tool-kits don't help you learn
I assume you are using Windows.
follow the unzip instructions from the previous poster. (not quoted here). note the directory.
find the directory containing your android tools... ADB.exe and FASTBOOT.exe.
transfer your unzipped files to this directory. Open your CMD prompt window and change to this directory if necessary.
plug in your Nexus.
type fastboot device at the prompt. MAKE SURE YOUR NEXUS 7 is listed (serial number)
proceed with the complete instructions from the previous poster.
that should do it.

YES!!!
thanks alot for the instructions, it worked!!! i hope people use ur instructions as reference if they have the same problem. THANKS ALOT!!!

dieselmonkeyy said:
thanks alot for the instructions, it worked!!! i hope people use ur instructions as reference if they have the same problem. THANKS ALOT!!!
Click to expand...
Click to collapse
I'm glad the problem is solved. Do not forget to click the THANKS button.
Sent from my Nexus 7 using xda app-developers app

Hello. My brother's Nex 7 is also has this issue. I cannot follow any of the steps as it gets stuck on erasing any of the partitions. I tried erasing those partitions in any order and they still get stuck. His device was stock and bootloader locked too. When I try to unlock the bootloader, it gets stuck as well at the erasing userdata part. I suspect a bad memory chip. Anyone else experience this?

Yes, mine is sticking on the (bootloader) erasing userdata on bootloader unlock as well.
It also sticks on any fastboot ERASE command.
Factory reset had a bunch of errors and no longer comes up. none of the FLASH commands work because the BOOTLOADER is locked.
And since it freezes on the unlocking bootloader commands I believe I am screwed.
This was a factory installed, never flashed, unlocked or rooted Nexus 7 wifi 2nd gen. After installing the 4.4.2 that popped up it loaded once then crashed and never loaded again
I have tried every tool I can find. They all stick on the erase part.

jophisdrazin said:
Yes, mine is sticking on the (bootloader) erasing userdata on bootloader unlock as well.
It also sticks on any fastboot ERASE command.
Factory reset had a bunch of errors and no longer comes up. none of the FLASH commands work because the BOOTLOADER is locked.
And since it freezes on the unlocking bootloader commands I believe I am screwed.
This was a factory installed, never flashed, unlocked or rooted Nexus 7 wifi 2nd gen. After installing the 4.4.2 that popped up it loaded once then crashed and never loaded again
I have tried every tool I can find. They all stick on the erase part.
Click to expand...
Click to collapse
Send your device for repair. My brother did so. My suspicions were correct. A faulty chip. They replaced the whole board, according to my brother.
Sent from my Nexus 7 using Tapatalk

Stuck in Fastboot

Hi! Seems like there are many different reasons why a Mi A1 can be stuck in Fastboot. I found others having the same symptom but the proposed solutions didn’t work for me.
Not matter what I do, my A1 won’t leave Fastboot:
- holding power button reboots to Fastboot
- holding power and volume up button reboots to Fastboot
- holding power and volume down button reboots to Fastboot
- `fastboot boot twrp.bin` does nothing (`sending`, `booting`, nothing)
- `fastboot flash recovery twrp.bin` complains `partition table doesn’t exist`
- `fastboot flash boot twrp.bin` complains `partition table doesn’t exist`
I basically followed the installation guide to install Lineage OS, used CosmicDan’s TWRP though. That didn’t work. Found out that I had to partition the storage for Treble. Flashed TWRP. Used “tissot manager” to partition. No I am stuck in Fastboot.
Any clues what is happening here?

There is a mistake in syntax for the flash command.
After the fastboot command you have to provide the slot for flashing boot.img
example: fastboot flash boot_a boot.img
In order to not screw up your device, download stock boot.img and write to both A and B slots then execute the reboot command.
This should do it

punktnet said:
There is a mistake in syntax for the flash command.
After the fastboot command you have to provide the slot for flashing boot.img
example: fastboot flash boot_a boot.img
In order to not screw up your device, download stock boot.img and write to both A and B slots then execute the reboot command.
This should do it
Click to expand...
Click to collapse
Thank you so much, this sounds promising. Where can I get the stock boot.img from?

punktnet said:
There is a mistake in syntax for the flash command.
After the fastboot command you have to provide the slot for flashing boot.img
example: fastboot flash boot_a boot.img
In order to not screw up your device, download stock boot.img and write to both A and B slots then execute the reboot command.
This should do it
Click to expand...
Click to collapse
tzyac said:
Thank you so much, this sounds promising. Where can I get the stock boot.img from?
Click to expand...
Click to collapse
I just flashed TWRP. And it is working. Thanks again!

My pleasure.
Just remember that this phone is almost impossible to brick

Cannot flash anything < waiting for device > but found in fastboot devices

Hello, I am trying to flash TWRP to my zenfone, I managed to do it once by some miracle with the exact same setup as I have now.
by typing fastboot devices I get K6AXB7616289*** fastboot
but if I try to flash anything with the phone connected I get no output at all.
If I try to flash with the phone disconnected I get <waiting for any device> and no change when I connect it.
In both of these cases when I disconnect the phone I get:
Sending 'recovery' (31332 KB) FAILED (Write to device failed (No such device))
fastboot: error: Command failed
It is overall wonky and seems to change depending on nothing. Sometimes while writing sudo fastboot reboot bootloader I get to the bootloader as expected, but sometimes I get an error but still manage to get to the bootloader and other times it boots up normally.
I am running ParrotOS from a USB
I also posted in here as my problem is very similar but I hope this post resurrects this particular topic: https://forum.xda-developers.com/t/...but-fastboot-devices-is-working-fine.4295449/

What commands are you using?
Fastboot flash boot boot.img?
The boot.img could be the twrp.img renamed to boot. Img but it should be to recovery I believe.
Fastboot flash recovery twrp.img

Yeah im writing fastboot flash recovery and then the path to my twrp.img. I managed to flash it once after a lot of struggle but now I can't do it again.
After posting I saw that I'm using a USB 3 port and my laptop doesn't have a usb 2 one so I think that might be the issue.
Considering I can get three different outputs from the same command in the span of a couple seconds I think that the problem might be hardware related. I can update once I get my hands on a USB 2 port.

Kaynejulian said:
What commands are you using?
Fastboot flash boot boot.img?
The boot.img could be the twrp.img renamed to boot. Img but it should be to recovery I believe.
Fastboot flash recovery twrp.img
Click to expand...
Click to collapse
I have now tried with a USB 2 port and there is no change.

I have had issue when the phones in fastboot and I'm able to flash via his method. Using platform tools I copy all my IMg's into the folder then open a command prompt window in that folder and fastboot reboot bootloader or fastboot reboot fastboot. Which I learned the hardway is fastbootd mode and then and only then did it actually flash. I also learned the hardway that you boot directly from in fastboot mode or it all just cycles back.
Fastboot reboot.
What version zenfone model and what is system is it running?

If your device is running android 10 or newer then is a different process as you'll need to flash the super.img rather than individual imgs like system vendor product ect
Tue shore image also means it matters where you flash the img
Get a fastboot getvar all printout to me and I'll do what I can to help u get it running again