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?

Cannot Boot TWRP Recovery After Unlocking Bootloader and Successful Flashing Recovery

Hi, I'm having issues with booting recovery.
I've successfully rooted my phone before, but because of an OTA update, had to revert back to the flashing of recovery (TWRP), booting recovery, then flashing Magisk steps.
So, I have my recovery.img file which I renamed to "twrp.img" (no double twrp.img.img file extensions). It looks like I'm able to flash it successfully, giving something that looks like this when I run "fastboot flash recovery twrp.img" (in the directory where the recovery image is located):
target reported max download size of 536870912 bytes
sending 'recovery' (24496 KB)...
OKAY [ 0.530s]
writing 'recovery'...
OKAY [ 0.156s]
finished. total time: 0.691s
Click to expand...
Click to collapse
​
However, after I try the "fastboot boot recovery twrp.img" command, it gives me:
cannot load 'recovery': No such file or directory
Click to expand...
Click to collapse
​
When I try to restart into recovery, it just boots into stock recovery, and not TWRP.
Any help would be super useful, I'm really not able to figure this out. I've done a lot of research, even going through disabling/uninstalling the Kedacom USB drivers and turning airplane mode on and installing adb/fastboot drivers from XDA.
Thanks!

Why are you flashing two recovery images? Maybe I'm missing something but I'm not understanding what it is that you are doing.
Your problems could also be related to whatever version of TWRP you are flashing on whatever OS you are running. Maybe there is a compatibility issue between the two but without more specific information it's pretty much impossible to say.

I'm just flashing one recovery.img file (TWRP), which doesn't display any errors in the flashing in command line. But when I try to boot it in command line, it gives me the above error that the recovery doesn't exist. When I try to boot it by advanced restart -> recovery, it just takes me to the stock recovery.
I'm on Oxygen 4.5.14. Let me know if there's anything else I can provide.

Rename your Recovery file to twrp.img
Seems like you forgot to do that according to your command
k0byf1ch said:
Hi, I'm having issues with booting recovery.
I've successfully rooted my phone before, but because of an OTA update, had to revert back to the flashing of recovery (TWRP), booting recovery, then flashing Magisk steps.
So, I have my recovery.img file which I renamed to "twrp.img" (no double twrp.img.img file extensions). It looks like I'm able to flash it successfully, giving something that looks like this when I run "fastboot flash recovery twrp.img" (in the directory where the recovery image is located):
​
However, after I try the "fastboot boot recovery twrp.img" command, it gives me:
​
When I try to restart into recovery, it just boots into stock recovery, and not TWRP.
Any help would be super useful, I'm really not able to figure this out. I've done a lot of research, even going through disabling/uninstalling the Kedacom USB drivers and turning airplane mode on and installing adb/fastboot drivers from XDA.
Thanks!
Click to expand...
Click to collapse
Edit:Sorry I kind of Missed that its already Done
Please Ignore My Upper Message
Possible another Solution:
Download Another Recovery File and Do the Same again

I've renamed the file since, and it still has been a problem.
Both recovery.img and twrp.img and the original name of the file "twrp-3.1.1-cheeseburger-84-20170820-194433-CEST.img" wouldn't take.

The file name is irrelevant. But it seems like your command to boot into recovery is the problem: fastboot boot only takes one argument (the file to boot into) whereas the fastboot flash command takes two arguments (partition and file to flash).
fastboot flash recovery twrp.img
fastboot boot twrp.img

Okay, I'll give that a shot but I'm still booting into the stock recovery when I advance restart into recovery.

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

Cant boot twice to Official twrp 3.3.1.0

After flashing from adb, shows twrp image not signed or corrupt
but when give command fastboot boot twrp it take to twrp.
From bootloader cant reach to twrp again, shows no command.
what to do?
pls help

markmywordz said:
After flashing from adb, shows twrp image not signed or corrupt
but when give command fastboot boot twrp it take to twrp.
From bootloader cant reach to twrp again, shows no command.
what to do?
pls help
Click to expand...
Click to collapse
The message not signed or corrupt is normal because TWRP is signed with an not official signed key.
After flashing official TWRP by fastboot
Code:
fastboot flash recovery name-of-recovery.img
you should immediately boot again to TWRP to make it stick.
You can do that by typing
Code:
fastboot reboot recovery
or if that doesn't work by the key command (power and vol down).

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