Hi @all,
i just messed something up while testing several custom roms for my Zenfone5 so actually i cant write system neither by "sideload" nor by "fastboot flash system". i always get the a mistake like:
Code:
FAILED (remote: flash_cmds error!)
Actually i cant find a mistake by myself. Is it located in my PC or in my phone? i already searched for an errorlist for fastboot but that doesn't get me any results...
and as we say in germany:
Vielen Dank im Vorraus!
Vere'Athor
You're trying to flash a wrong file.
What's the command you're running?
I get the same error running this command:
fastboot.exe flash recovery recovery.img
I cant erase this partition too. When i run this:
fastboot.exe erase recovery
I get this:
FAILED (remote: unable to format)
¨
Please Help
Waërloga666 said:
I get the same error running this command:
fastboot.exe flash recovery recovery.img
I cant erase this partition too. When i run this:
fastboot.exe erase recovery
I get this:
FAILED (remote: unable to format)
¨
Please Help
Click to expand...
Click to collapse
Can you post a link to recovery you are trying to flash? (I will test it)
Can anyone help me out? I tried to install CM 13.1 in Zenfone 5 but when it gets to "writing boot" the following message appears:
FAILED (remote: flash_cmds error!)
How could i solve this? txs everyone
(If any of you guys could text in Portuguese i would be very pleasant)
if u want to flash custom rom
all u need is to unlock bootloader
take a look on this thread using auto.bat for unlock bootloader!
https://forum.xda-developers.com/zenfone-5/general/recovery-twrp-2-8-6-0-asus-zenfone-5-t3136263
after unlocked try flash TWRP again
to confirm success unlocked not!
if fail it will show error failed
just follow step by step read thru!
hope it helps
good luck !
I am Having The Same Error (FAILED (remote: flash_cmds error!)
What To do
Related
First of all, I would like to apologize if this question has been answered in another thread. I have searched the xda forums and others with no success.
My situation is the following:
Running on Windows 8.1
1. Rooted Nexus 4 on 4.4 (if I remember correctly)
2. OTA update to 4.4.2 (loosing root, but device remains unlocked) (I think I also tried flashing the factory image manually, but failed, I don't remember exactly)
I rooted my phone when Kitkat was fresh and found there were no custom roms on 4.4 yet so I went back to stock because it was the easiest way to get the update. Right now I can not flash a custom recovery.
fastboot oem unlock
...
FAILED (remote: Already Unlocked)
finished. total time: 0.002s
===================================================
fastboot flash recovery.img
unknown partition 'recovery.img'
error: cannot determine image filename for 'recovery.img'
This is the same for both TWRP and CWM. I am very sure I did NOT misspell the name.
Does anyone have any idea why this is happening and how to fix it?
Thank you for taking the time to read this post!
You have to use this
fastboot flash recovery recovery.img
wrong syntax, must be: fastboot flash recovery recovery.img
Wow.... I am ashamed with myself. I cannot believing I missed that.
Thank you for the quick reply guys.
I was just doing the same here thanks!
command doesnt work for me
jd1639 said:
You have to use this
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
I've tried to use that command but this is all i get after:
Sending 'recovery' (22432 KB) OKAY [ 0.579s]
Writing 'recovery' FAILED (remote: '(recovery_b) No such partition')
fastboot: error: Command failed
Is there that is wrong and that i may need to fix?
FastSl0th said:
I've tried to use that command but this is all i get after:
Sending 'recovery' (22432 KB) OKAY [ 0.579s]
Writing 'recovery' FAILED (remote: '(recovery_b) No such partition')
fastboot: error: Command failed
Is there that is wrong and that i may need to fix?
Click to expand...
Click to collapse
In the xda forum, check carefully whether you are asking a question in the appropriate Q&A section for your device, because you are certainly not writing about Nexus 4.
.
FastSl0th said:
command doesnt work for me
I've tried to use that command but this is all i get after:
Sending 'recovery' (22432 KB) OKAY [ 0.579s]
Writing 'recovery' FAILED (remote: '(recovery_b) No such partition')
fastboot: error: Command failed
Is there that is wrong and that i may need to fix?
Click to expand...
Click to collapse
Hopefully you may have already asked or solved this question. I am assuming you are issuing command from platform-tools folder. If you have a Windows 10 OS system then, I too could not found USB drivers for my system with windows 10. If 'fastboot devices' command returning some device id then maybe I have guessed wrong reason.
I entered "fastboot flash XXX.img" Too. hahaha
After i see this article, I entered "fastboot flash recovery flash XXX.img"
Thank you anyway.
unsolved
dan60 said:
unsolved
Click to expand...
Click to collapse
fastboot: error: cannot determine image filename for 'bootC:\Android Development\platform-tools\magisk_patched-24300_NP5BG.img' How To Solve This Problem Brother..Please Tell me
fastboot: error: cannot determine image filename for 'bootC:\Android Development\platform-tools\magisk_patched-24300_NP5BG.img' How to Solve This Problem Brother...Please Tell Me
d4_daman_ said:
fastboot: error: cannot determine image filename for 'bootC:\Android Development\platform-tools\magisk_patched-24300_NP5BG.img' How to Solve This Problem Brother...Please Tell Me
Click to expand...
Click to collapse
Hi there!
It didn't work for me but you can try it >>>
jd1639 said:
You have to use this
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Hi guys, I found the same error when I've tried to install TWRP on mi Xiaomi Mi A3 by FASTBOOT on Linux Terminal.
After a lot of searching, I solved my problem using the syntax below:
"fastboot flash boot XXX.img"
"boot" is the partition about FASTBOOT are asking for.
Hope to be usefull.
Hi
I have Lenovo Tablet 2 Pro 1380L. I have simpley bricked it by flashing wrong firmware.
the problem is that when I boot it into FASTBOOT I cannot flash any IMG file and I get an error message that says "FAILED (remote command unknown)"
any idea why I'm getting such message ?
good morning if someone could help me ..I want to go back to rom stock from lineage so .. I miss the flash of a file and now it stays in erecovery without giving me another option, I tried to fastboot in install but I get this error FAILED ( remote: Command not allowed) .. and I have the frp lock ..
rodriguez86 said:
good morning if someone could help me ..I want to go back to rom stock from lineage so .. I miss the flash of a file and now it stays in erecovery without giving me another option, I tried to fastboot in install but I get this error FAILED ( remote: Command not allowed) .. and I have the frp lock ..
Click to expand...
Click to collapse
Try
Code:
sudo fastboot flash recovery twrp.zip
Replace twrp.zip with the actual file that contains the custom recovery
Hello
i have followed all the guides in order to install the latest version of TWRP in mi X Compact in order to Magisk, but im having this issue on the fastboot comand:
Sending 'recovery' (21552 KB) OKAY [ 0.724s]
Writing 'recovery' FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
i have serched for solutions but nothing seems to work, its the first time i try to install TWRP on this phone so its never been rooted (Bootloader is not unlocked) and everyting has alredy been updated to the latest version, any help?
Thanks in advance!
i just unlocked the bootloader, and still gives me the "FAILED (remote: Command not allowed)" error when flashin TWRP trough fastboot HELP PLEASE
Black Swift said:
i just unlocked the bootloader, and still gives me the "FAILED (remote: Command not allowed)" error when flashin TWRP trough fastboot HELP PLEASE
Click to expand...
Click to collapse
Try fastboot boot twrp.img
just tried it, i got a message on my phone screen:
"your device has failed verification and will not work properly"
then phone restarts
in the windows power shell i get this message:
FAILED (Status read failed (Too many links))
I just seem to be unable to install TWRP on this phone :C
Help please!!!
i just tried a different cable, im still getting the "comand not allowed" message, can anyone help me please??
Hello,
I have a Nothing Phone 1 that hangs in bootloader/fastboot mode.
The bootloader is unlocked.
Unfortunately, the phone can no longer be booted into recovery mode.
With fastboot the device is still recognized.
So you could still flash files via fastboot.
The phone was not rooted.
The phone previously ran with the original stock firmware 1.1.7 hotfix.
It is an EEA device.
Is there anything that can be done?
Or is it now an expensive paperweight?
Try running "fastboot reboot recovery" in the terminal with your phone connected.
Unfortunately this does not work.
Thanks for the quick reply.
The device then boots back into the bootloader
It looks like they have Nothing OS downloads here. You could just try reflashing the phone through fastboot.
Looks like someone else is having the same problem. Keep an eye on that thread in case a solution comes up there.
so, i have the unpacked payload.bin image files. Here fastboot tells me several errors with odm.img FAILED (remote: '(odm_b) No such partition'), with product.img FAILED (remote: 'Partition not found'), with system.img FAILED (remote: 'Partition not found'), with system_ext.img FAILED (remote: '(system_ext_b) No such partition') and with vendor.img FAILED (remote: 'Partition not found').
After a restart, the error remains.
There is also the fastbootD mode, but this does not work or does not boot.
After this command the device hangs in bootlogo (nothing).
Unfortunately very sad that there is still no solution for this. let's hope that there is soon a solution for this.
Sapphire86 said:
so, i have the unpacked payload.bin image files. Here fastboot tells me several errors with odm.img FAILED (remote: '(odm_b) No such partition'), with product.img FAILED (remote: 'Partition not found'), with system.img FAILED (remote: 'Partition not found'), with system_ext.img FAILED (remote: '(system_ext_b) No such partition') and with vendor.img FAILED (remote: 'Partition not found').
After a restart, the error remains.
There is also the fastbootD mode, but this does not work or does not boot.
After this command the device hangs in bootlogo (nothing).
Unfortunately very sad that there is still no solution for this. let's hope that there is soon a solution for this.
Click to expand...
Click to collapse
Type "fastboot reboot fastboot" in the terminal, with your phone connected, and then run "fastboot flash <yourimagename>.img".
yes, when i enter this command the device restarts and hangs in the bootlogo and in the terminal it says then wait for any device. That means the Nothing Phone does not start the fastbootD mode.
And if he doesn't do this, I think it looks really bad.
Are you using Windows to flash it?
Yes windows 11 with the latest drivers, but I have already considered using linux.
Which linux distribution would be best. Then I will download it and try it out.
I would recommend Ubuntu, if you have a spare computer to install it on (or dual boot). Just make sure you install the tools needed from here (Scroll down to the "Command line tools only" section and download the Linux version)
I only use Linux, so let me know if you have any questions.
Ok thanks. I will have a look and install it on a notebook later.
You have to be very careful. I had the same problem (bootloop in fastboot) and by dint of manipulation, no more fastboot, my smartphone is hard brick (black screen with logo and message key to shutdown)
ziptric1805 said:
You have to be very careful. I had the same problem (bootloop in fastboot) and by dint of manipulation, no more fastboot, my smartphone is hard brick (black screen with logo and message key to shutdown)
Click to expand...
Click to collapse
If your phone has a Qualcomm processor, you still have EDL mode.
It is not bricked. Just flash any cutom rom, I recommend Paranoid Android. Then revert back to stock NOS.
@MakDroid
I just installed Topaz 1 (A13) to save my bricked phone. How can i revert back to stock NOS from A13? There is any option or i have to wait for full rom with A13?
Ostry10 said:
@MakDroid
I just installed Topaz 1 (A13) to save my bricked phone. How can i revert back to stock NOS from A13? There is any option or i have to wait for full rom with A13?
Click to expand...
Click to collapse
Download NOS 1.1.7 full from here.
Extract payload.bin and place all the extracted .img files inside a folder named "images".
Copy the images folder and the attached bat file (extract the zip to get the bat file) to the platform-tools folder.
Run the bat file and it will start flashing. Wait for it to complete and then simply update to latest version using stock updater.