adb fastboot command failed - Android Q&A, Help & Troubleshooting

Erasing 'system' FAILED (remote: 'Check device console.')
fastboot: error: Command failed
Erasing 'system_ext' FAILED (remote: 'Check device console.')
fastboot: error: Command failed
Erasing 'odm' FAILED (remote: 'Check device console.')
fastboot: error: Command failed
Erasing 'product' FAILED (remote: 'Check device console.')
fastboot: error: Command failed
Can someone help? i downloaded the new adb drivers, adb is updated. bootloader is unlocked.

1.
ADB and Fastboot are different drivers that serve different purpose
2.
How Fastboot commands are implemented depends on manufacturer. In any case download and install the "Android USB Driver" suitable to your Android device.

jwoegerbauer said:
1.
ADB and Fastboot are different drivers that serve different purpose
2.
How Fastboot commands are implemented depends on manufacturer. In any case download and install the "Android USB Driver" suitable to your Android device.
Click to expand...
Click to collapse
The thing is fastboot works for other things but when I try to flash this from which formats it, it fails on erasing system and the other images. I've always used the adb 15 second installer on xda.

I'm pretty sure the Fastboot you've installed is for Google devices. If your device isn't a Google one then install, as by me suggested earlier, the driver provided by your device's manufacturer.

Related

My son killed xiaomi mi a3

(This is a duplicate of thread to reach more people, original thread : https://forum.xda-developers.com/mi-a3/help/son-killed-xiaomi-mi-a3-t4060735)
So I bought a son new phone.
As he told he installed magisk first, flashing "magisk_patched.img" through windows shell, everything was fine. Then He flashed twrp and magisk, everything was almost fine, he noticed that he cant play audio. He was trying to fix it first through installing magisk audio mods like viper and sauron. It didn't fixed anything, he unistalled it, everything was still in the same state, so he decided to flash stock frimware. He flashed through mi flashing tool, unfortunetaly It was image for "global xiaomi version" I mean "PFQMIXM" when as far as I know It should be "PFQEUXM". It didn't work and he was stuck in a bootloop. He found "MiUi 11 " image and for still unknown to me reason thought that it is going to fix everything. He flashed It again through mi flashing tool. It didn't work. He did that second time but at last he just closed the flashing tool while it was doing its thing.
At last he found eu firmware but now after all of that when i try to flash it or single files like crc list i get this:
flash crclist "E:\ModCR\adb\images\crclist.txt"
Sending 'crclist' (0 KB) FAILED (Write to device failed (Unknown error))
fastboot: error: Command failed
Device only boots to fastboot (no recovery/twrp either).
I tried erasing cache:
./fastboot erase cache
Erasing 'cache' FAILED (Write to device failed (Unknown error))
fastboot: error: Command failed
I tried to check slots:
./fastboot getvar active-slot
getvar:active-slot FAILED (Write to device failed (Unknown error))
Finished. Total time: 5.003s
I tried to change slot:
./fastboot set_active b
fastboot: error: Device does not support slots
When i typed "fastboot devices" It appeared as "??????"
./fastboot devices
???????????? fastboot
I don't know how to fix it, If anyone knows or has any kind of even small idea please write it down. I would be very greatfull.
Thread closed as duplicate of https://forum.xda-developers.com/mi-a3/help/son-killed-xiaomi-mi-a3-t4060735
Do not make duplicates "to reach more people"..

The system has been destroyed - Pocophone F1

Hi Guys!
So I got a phone from a friend to assist him with a problem.
When I opening the phone, the phone showing an error message "The system has been destroyed".
I tried to use Fastboot but when I running any command an error message received, for example:
Example1:
fastboot flash recovery "twrp-3.3.0-0-beryllium (1).img"
Sending 'recovery' (31068 KB) FAILED (Write to device failed (Invalid argument))
fastboot: error: Command failed
Example2:
fastboot devices -l
???????????? fastboot
Example 3:
fastboot flashing unlock
FAILED (Write to device failed (Unknown error))
fastboot: error: Command failed
fastboot oem device-info -v
< waiting for any device >
FAILED (Write to device failed (Too many links))
fastboot: error: Command failed
Any ideas??
Please help!
Thanks!

partition table broken

Hi all,
when installing lineage 18.1 I successfully screwed up my MOTO G8. When rebooting after all installalation steps being successfull, it says
​No valid operation system could be found. The device will not boot.​
Booting to fastboot again I tried to flash again, but this time I get
​fastboot set_active a​Setting current slot to 'a' FAILED (remote: '')
fastboot: error: Command failed​​Trying to to flash something does not work as well, e.g.
fastboot flash recovery recovery.img​ending 'recovery' (24924 KB) OKAY [ 0.752s]​Writing 'recovery' (bootloader) Invalid partition name recovery
FAILED (remote: '')
fastboot: error: Command failed​​Apperently the partition table appears to be broken. Can I restore it?
badkey212 said:
Hi all,
when installing lineage 18.1 I successfully screwed up my MOTO G8. When rebooting after all installalation steps being successfull, it says
​No valid operation system could be found. The device will not boot.​
Booting to fastboot again I tried to flash again, but this time I get
​fastboot set_active a​Setting current slot to 'a' FAILED (remote: '')​fastboot: error: Command failed​​Trying to to flash something does not work as well, e.g.
​fastboot flash recovery recovery.img​ending 'recovery' (24924 KB) OKAY [ 0.752s]​Writing 'recovery' (bootloader) Invalid partition name recovery​FAILED (remote: '')​fastboot: error: Command failed​​Apperently the partition table appears to be broken. Can I restore it?
Click to expand...
Click to collapse
Does the bootloader say "flashing_locked" now?
Try
Code:
fastboot flash partition gpt.bin
sd_shadow said:
Does the bootloader say "flashing_locked" now?
Try
Code:
fastboot flash partition gpt.bin
Click to expand...
Click to collapse
That helped, thank you!

'fastboot oem get_unlock_data' failure with Motorola

Hello, I've been struggling with this for hours and nothing seems to be working.
I have a Motorola DROID RAZR XT912 running Android 4.1.2 JB, it's already rooted but I'm attempting to unlock the bootloader using this guide.
I've installed the Android SDK as well as the latest USB Drivers.
I enter my mobile device into "AP Fastboot Flash Mode (S)" by holding power + volume down.
I plug my device into my laptop, the phone says "USB Connected".
I open a terminal in Windows 11 in my SDK tools directory [C:\Users\FOS11\AppData\Local\Android\Sdk\platform-tools]
I use the command "fastboot devices" to test if fastboot is working and detecting my device.
It properly returns with "014FFB290D006013 fastboot"
I attempt to use the command "fastboot oem get_unlock_data"
It returns with an error:
"FAILED (remote: 'unsupported command')
fastboot: error: Command failed"
I have followed the guide exactly up to this point with no errors, I have not found any forum or guide saying anything about this error, I must be missing something very simple, right? please let me know if any additional information is needed.
some moto/lenovo do not require unlock code. such old device maybe isn't even locked. just curious what happen for?
Code:
fastboot flashing get_unlock_ability
fastboot flashing unlock
fastboot oem unlock
fastboot getvar all
could be also possible it's non-unlockable bootloader (not intended by manufacturer, unofficial methods might exist)
"Your device is NOT eligible for bootloader unlock if the CID value returned is one of these: 0x0001, 0x0002, 0x0004, 0x0005, 0x0006, 0x0008, 0x000A, 0x000F, 0x0010, 0x0011"
aIecxs said:
some moto/lenovo do not require unlock code. such old device maybe isn't even locked. just curious what happen for?
Code:
fastboot flashing get_unlock_ability
fastboot flashing unlock
fastboot oem unlock
fastboot getvar all
could be also possible it's non-unlockable bootloader (not intended by manufacturer, unofficial methods might exist)
"Your device is NOT eligible for bootloader unlock if the CID value returned is one of these: 0x0001, 0x0002, 0x0004, 0x0005, 0x0006, 0x0008, 0x000A, 0x000F, 0x0010, 0x0011"
Click to expand...
Click to collapse
"fastboot flashing get_unlock_ability"
returns
"FAILED (remote: 'unsupported command')
fastboot: error: Command failed"
"fastboot flashing unlock"
returns
"FAILED (remote: 'unsupported command')
fastboot: error: Command failed"
"fastboot oem unlock"
returns
"(bootloader) fastboot oem unlock disabled!
FAILED (remote: '')
fastboot: error: Command failed"
"fastboot getvar all"
returns
"getvar:all FAILED (remote: 'unsupported command')
Finished. Total time: 0.000s"
Additional info: phone has no SIM card inserted (Not sure if this is useful)
(bootloader) fastboot oem unlock disabled!
probably means this bootloader cannot unlocked.
But last cmd shouldn't fail.. try special mfastboot.exe or more recent platform-tools
Code:
fastboot getvar unlocked
fastboot getvar securestate
fastboot getvar sku
fastboot getvar cid
or just try if unlocked by doing something invasive (does not harm on cache)
Code:
fastboot oem fb_mode_set
fastboot format cache
fastboot oem fb_mode_clear
aIecxs said:
(bootloader) fastboot oem unlock disabled!
probably means this bootloader cannot unlocked.
But last cmd shouldn't fail.. try special mfastboot.exe or more recent platform-tools
Code:
fastboot getvar unlocked
fastboot getvar securestate
fastboot getvar sku
fastboot getvar cid
or just try if unlocked by doing something invasive (does not harm on cache)
Code:
fastboot oem fb_mode_set
fastboot format cache
fastboot oem fb_mode_clear
Click to expand...
Click to collapse
Using your attached platform-tools version,
'mfastboot.exe' is not recognized as an internal or external command,
operable program or batch file.
fastboot getvar unlocked
returns
unlocked: no
fastboot getvar securestate & fastboot getvar sku
returns
FAILED (remote: 'unsupported command')
fastboot getvar cid
returns
cid: 2
fastboot oem fb_mode_set
returns
OKAY [ 0.016s]
fastboot format cache
returns
FAILED (remote: 'protocol error')
fastboot oem fb_mode_clear
returns
OKAY [ 0.016s]
Additional info: phone was rooted with a tool called "RAZR Blade"
Thank you for your help so far.
cid: 0x0002 "Your device is NOT eligible for bootloader unlock"
Frequently Asked Questions - Motorola Razr [XT912, XT910, XT908] (2015)
Frequently Asked Questions Motorola Razr [XT912, XT910, XT908] This a short list of frequently asked questions in this device forum and the answers often given as a response. It should serve as a starting point for gathering knowledge and...
forum.xda-developers.com
hi, i received other error, xt-2239-16 moto e22i,
C:\Users\Rosaly\Desktop\platform-tools>fastboot getvar unlocked
unlocked: no
Finished. Total time: 0.000s
C:\Users\Rosaly\Desktop\platform-tools>fastboot getvar securestate
getvar:securestate FAILED (remote: 'Unknown variable')
Finished. Total time: 0.016s
C:\Users\Rosaly\Desktop\platform-tools>fastboot getvar securestate
getvar:securestate FAILED (remote: 'Unknown variable')
Finished. Total time: 0.000s
C:\Users\Rosaly\Desktop\platform-tools>fastboot getvar sku
getvar:sku FAILED (remote: 'Unknown variable')
Finished. Total time: 0.016s
C:\Users\Rosaly\Desktop\platform-tools>fastboot getvar cid
getvar:cid FAILED (remote: 'Unknown variable')
Finished. Total time: 0.016s
C:\Users\Rosaly\Desktop\platform-tools>fastboot oem fb_mode_set
FAILED (remote: 'Unable to open fastboot HAL')
fastboot: error: Command failed
C:\Users\Rosaly\Desktop\platform-tools>
C:\Users\Rosaly\Desktop\platform-tools>fastboot format cache
FAILED (remote: 'Invalid partition')
fastboot: error: Command failed
C:\Users\Rosaly\Desktop\platform-tools>fastboot oem fb_mode_clear
FAILED (remote: 'Unable to open fastboot HAL')
fastboot: error: Command failed
i m not read cid, could be help me, please.
tks
Rocha

(Nokia 2.3) How to install a GSI on a Nokia 2.3?

Hello everyone, this is my first time posting in XDA!
I know that you can't unlock the bootloader on a "official" way but I was able to do it with the help of mtkclient and some posts around XDA, now I was wondering if someone tried or what is the procedure to install a GSI on this device because I have tried but it won't boot (reboots over and over or gets stuck in logo), I've seen some posts (on Nokia official forums) saying that they were able to do this using the latest LineageOS GSI and I tried this but it didn't work too!.
What have I tried?​So far I tried to flash the GSI with fastboot and SP Flash Tool and none of them worked but there were some errors on the fastboot procedure:
When doing
Code:
fastboot delete-logical-partition product_a
It showed me:
Code:
Deleting 'product_a' FAILED (remote: 'unknown command')
fastboot: error: Command failed
So I just continued anyways and the flashing went with no errors using
Code:
fastboot flash system (Path to rom)
but when trying to do a userdata wipe (fastboot -w), fastboot says this:
Code:
Erasing 'userdata' OKAY [ 0.078s]
CreateProcess failed: The system cannot find the specified file. (2)
fastboot: error: Cannot generate image for userdata
So I thought that maybe that was the problem of why it wasn't working.
Any help is really appreciated, thanks!

Categories

Resources