Database Info

fastboot: FAILED (remote: image verification error) after DC Phoenix unbrick

Hello
after i succesfully used DC Phoenix to recover Huawei Mate 8 (NXT-L29C432) i cannot flash TWRP or anything on my phone , as im still getting the "FAILED (remote: image verification error)" from fastboot. So i also cannot root and use the device as before
Im sure im not alone with this issue, but i cannot find any clear solution for this. Can you please help or advice me further??
I spent 15€, recovered the phone, but with this, its still partial success.
I basicaly followed https://forum.xda-developers.com/mate-8/help/how-to-unbrick-l29-al10-stuck-fastboot-t3599775
Here some outputs:
c:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp-3.2.0-0-next.img
target reported max download size of 471859200 bytes
sending 'recovery' (22140 KB)...
OKAY [ 0.530s]
writing 'recovery'...
FAILED (remote: image verification error)
finished. total time: 0.562s
Before the use of DC Phoenix, i always get this number.
c:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
QHC0216327001941 fastboot
Now:
c:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
0123456789ABCDEF fastboot
In Fastboot mode, on phone screen i see:
PHONE Unlocked
FRP Lock
DC - Unlocker 2 Client 1.00.1308 reports:
FB LockState: UNLOCKED
USER LockState: LOCKED
unlocked
c:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem get-lockstate
...
(bootloader) locked
OKAY [ -0.000s]
finished. total time: -0.000s
c:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ -0.000s]
finished. total time: -0.000s
In Developer menu i have the
"Allow OEM unlock" grayed & disabled, im unable to swich it on..
Can you please explain what happend and how to fix this?
Thank you for further help.

Solved with mighty HCU client, i was able to import the just the SN back without problems. Then as usual.. unlock the bootloader, TWRP, SU... and now the phone is back in shape

I hope I can recover my Mate 9 Pro.
Maybe 15€ is have to spend but FunkyHuawei is more expensive.

Hi. I have same problem., I unlocked Huawei WAS-AL00 bootloader via Miracle Huawei Tool, it unlocked successfully. But, I can't flash TWRP, it says-FAILED (remote: image verification error)
Whent type fastboot oem lock-state info in CMD, it shows:
FB LockState: UNLOCKED
USER LockState: LOCKED
There is not FRP or OEM lock option in settings, becuse this is China version model and doesn't support Google Play.
What is USER LOCK STATE? Please help me. Thanks.

Remote:image verification error.
When i try to flash Mate 8 nxt l29 twrp recovery its says remote:image verification error..the phone fastboot is unlocked .i tried many twrp images but still the same problem

Bootloop after installing an Factory Image for Android 9.0

Hi, i just bought a Google Pixel from Ebay an tried to install an factory image for Android 9 from the Google Website. After fastboot the flash-all.sh (ive got Ubuntu) it got stuck a on the bootscreen (The Google Logo flashes in an instance and the Screen goes black again). Unfortunally the device is locked again (bootloader ist locked), so adb is not working. fastboot works but when i install some other factory images from the google website the problem with the flashing bootscreen reappears.
Loading into bootloader works:
Product/Variant: sailfish-US-PVT
Serial Number FA72H0300560
CPU: MSM8996SG-AB 0x10001
UFS: 32 GB Samsung
DRAM:4096MB Hynix LPDDR4
Boot-slot: a
Console: DISABLED
Secure Boot: PRODUCTION
Device is LOCKED
Could anyone help?
Thanks in advance.

Not sure but I think U can try booting into TWRP using "fastboot flash recovery twrp" command in CMD and than switch boot slot to b, my pixel is in the same situation - I can't boot into slot a and switching to b works
oh sry, the command is "fastboot boot path/to/twrp.img"

Thanks for your help, but it didn't work.
When I try to fastboot with following commands, it says:
sudo ./fastboot boot twrp-3.2.3-1-sailfish.img
Code:
Downloading 'boot.img' OKAY [ 0.785s]
booting (bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote: '')
Finished. Total time: 0.963s
sudo ./fastboot flash recovery twrp
Code:
fastboot: error: cannot load 'twrp': No such file or directory
I have Ubuntu with local platform-tools, so the commands look a little bit different...

Double-check the checksum of the downloaded file.
Open the flash-all.sh file in a text editor, and manually run each of the flash commands individually. See if any of them throw an error.
You might also try to install the OTA.

I tried the first command in the flash-all.sh with the same results:
sudo ./fastboot flash bootloader bootloader-sailfish-8996-012001-1808030001.img
Code:
Sending 'bootloader_a' (32384 KB) OKAY [ 0.951s]
Writing 'bootloader_a' (bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote: '')
Finished. Total time: 1.189s
I will try out the OTA tomorrow. Does anyone know how to handle the payload.bin in to OTA.zip under a Linux-System?
ADB seems not be working. SO adb sideload ota_file.zip, like its mentioned on the google website seems to be also no option....

ArchArch said:
I tried the first command in the flash-all.sh with the same results:
sudo ./fastboot flash bootloader bootloader-sailfish-8996-012001-1808030001.img
Code:
Sending 'bootloader_a' (32384 KB) OKAY [ 0.951s]
Writing 'bootloader_a' (bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote: '')
Finished. Total time: 1.189s
I will try out the OTA tomorrow. Does anyone know how to handle the payload.bin in to OTA.zip under a Linux-System?
ADB seems not be working. SO adb sideload ota_file.zip, like its mentioned on the google website seems to be also no option....
Click to expand...
Click to collapse
You need to re-unlock your bootloader first, then. Try fastboot flashing unlock .

No luck.
sudo ./fastboot flashing unlock
Code:
FAILED (remote: 'oem unlock is not allowed')
Finished. Total time: 0.007s
sudo ./fastboot oem unlock
Code:
FAILED (remote: 'oem unlock is not allowed')
Finished. Total time: 0.038s

ArchArch said:
sudo ./fastboot flash recovery twrp
Code:
fastboot: error: cannot load 'twrp': No such file or directory
I have Ubuntu with local platform-tools, so the commands look a little bit different...
Click to expand...
Click to collapse
Did U opened CMD from the folder in which the TWRP file is located? Just type in CMD: "fastboot boot", and after "boot" type "twr" and press TAB button, program will locate the file itself.

Levan_i said:
Did U opened CMD from the folder in which the TWRP file is located? Just type in CMD: "fastboot boot", and after "boot" type "twr" and press TAB button, program will locate the file itself.
Click to expand...
Click to collapse
He's using linux. The reason his flashes have been unsuccessful is because the bootloader is locked.

Tanks for your efforts so far...
Just for clarification: The initial plan was to root my device, according to the XDA-Guide for rooting an Pixel XL Android 9.0 (with the Files for my "Sailfish"-Pixel) https://forum.xda-developers.com/pixel-xl/how-to/guide-pixel-xl-android-9-0-pie-unlock-t3825866
First when I bought the Pixel the "OEM Unlock"-Option in the Developers-Menu was greyed out.
So i tried out, beneath some other guides, the XDA-Guide for unlocking a Verizon Pixel and it worked. https://forum.xda-developers.com/pixel-xl/how-to/how-to-unlock-bootloader-verizon-pixel-t3796030
So I thought its an VerizonPixel, installed an Verizon Image from the Google Website, got always the message at bootup that an unlocked bootloader is some sort of threat, closed the Bootloader and the flashing bootscreen-problem began…

FAILED (remote: 'Download is not allowed on locked devices')

i wnat to root https://www.xda-developers.com/root/
when i try
D:\platform-tools>fastboot flash boot D:\platform-tools/magisk_patched-25100_1VYTU.img
it show
Code:
Sending 'boot' (98304 KB) FAILED (remote: 'Download is not allowed on locked devices')
fastboot: error: Command failed

i also try
fastboot oem unlock
it show
Code:
FAILED (remote: 'Unable to open fastboot HAL')
fastboot: error: Command failed
what should i do ??

chatofking said:
i wnat to root https://www.xda-developers.com/root/
when i try
D:\platform-tools>fastboot flash boot D:\platform-tools/magisk_patched-25100_1VYTU.img
it show
Code:
Sending 'boot' (98304 KB) FAILED (remote: 'Download is not allowed on locked devices')
fastboot: error: Command failed
Click to expand...
Click to collapse
Rename the patched boot.img to "boot.img", then place the patched .img in your fastboot folder on PC then type:
fastboot flash boot boot.img
When you place the file in your fastboot folder, you don't need to include the path to the file in the command, it automatically looks for the file in the fastboot folder by default when you do not enter a path. Renaming the file to "boot.img" isn't necessarily required, but, it does simplify things for fastboot and makes the command easier to remember and type.
The same applies if you want to flash a system.img, recovery.img, etc.. Just change the name of the file to "system.img" or "recovery.img" and place it/them in your fastboot folder and it simplifies your commands to:
fastboot flash system system.img
And
fastboot flash recovery recovery.img
Also, try this for the failed command
FAILED (remote: Unable to open fastboot HAL): Unlock Bootloader Fix
In this tutorial, we will show you the steps to fix the FAILED (remote: Unable to open fastboot HAL) error when unlocking the bootloader.
www.droidwin.com

now i got same message
D:\platform-tools>fastboot flash boot boot.img
Code:
Sending 'boot' (98304 KB) FAILED (remote: 'Download is not allowed on locked devices')
fastboot: error: Command failed

Droidriven said:
Also, try this for the failed command
FAILED (remote: Unable to open fastboot HAL): Unlock Bootloader Fix
In this tutorial, we will show you the steps to fix the FAILED (remote: Unable to open fastboot HAL) error when unlocking the bootloader.
www.droidwin.com
Click to expand...
Click to collapse
im already try this verify cmd location, install fastboot driver & boot fastboot mode nothing change.
Code:
D:\platform-tools>fastboot oem unlock
FAILED (remote: 'Unable to open fastboot HAL')
fastboot: error: Command failed
what should i do ??

chatofking said:
i wnat to root https://www.xda-developers.com/root/
when i try
D:\platform-tools>fastboot flash boot D:\platform-tools/magisk_patched-25100_1VYTU.img
it show
Code:
Sending 'boot' (98304 KB) FAILED (remote: 'Download is not allowed on locked devices')
fastboot: error: Command failed
Click to expand...
Click to collapse
You've to unlock device's bootloader. Hence 1st of all if you want to manage the / operate on the bootloader you have to move device into fastboot mode and then run on device if it's launched 2015 or later
Code:
fastboot flashing unlock
[code]
instead of the outdated
[code]
fastboot oem-unlock

xXx yYy said:
You've to unlock device's bootloader. Hence 1st of all if you want to manage the / operate on the bootloader you have to move device into fastboot mode and then run on device if it's launched 2015 or later
Code:
fastboot flashing unlock
[code]
instead of the outdated
[code]
fastboot oem-unlock
Click to expand...
Click to collapse
when i try
D:\platform-tools>fastboot flashing unlock
it show
Code:
FAILED (remote: 'Unrecognized command flashing unlock')
fastboot: error: Command failed
i use https://developer.android.com/studio/releases/platform-tools
what should i do ??

The platform tools you actually use are meant to be used with Google devices only.
Use the Android USB-tools provided by your device's manufacturer.

xXx yYy said:
The platform tools you actually use are meant to be used with Google devices only.
Use the Android USB-tools provided by your device's manufacturer.
Click to expand...
Click to collapse
i use mtp driver
update Portable Devices to MTP USB Device
but when i enter fastboot mode
it become Android Device Android Bootloader Interface.

where is extracted the driver package folder ?? https://www.xda-developers.com/download-android-usb-drivers/

I'm having simular issue with my specter 8 tablet. I unlock the bootloader and give me the normal prompt. I go back do everything else and will execute reboot devices ect. However won't flash patch_boot.img brings up message
FAILED (remote: 'Download is not allowed on locked devices').

Question help please

hello, i want to root my phone with magisk, adb and fastboot, i get this error when i want to root it in fastboot mode
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot magisk_patched_pEtAo.img
downloading 'boot.img'...
FAILED (remote: unknown command)
finished. total time: 0.009s
I even wanted to download twrp recovery and still the same thing appeared in fastboot mode

yukan2007 said:
hello, i want to root my phone with magisk, adb and fastboot, i get this error when i want to root it in fastboot mode
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot magisk_patched_pEtAo.img
downloading 'boot.img'...
FAILED (remote: unknown command)
finished. total time: 0.009s
I even wanted to download twrp recovery and still the same thing appeared in fastboot mode
Click to expand...
Click to collapse
Follow the root tutorials in the forum, rooting by flashing using the terminal is a deprecated method

tecno unlock bootloader?

so i am trying to unlock bootloader in my device tecno spark 8c i enter the fastboot mode and tried the command fastboot oem unlock it say message ok but nothing happenes if i try to flash the vbmeta it says the bootloader locked and need to be unlocked how to unlock it?

What happened is that you got a OK, means phone's bootloader now got unlocked.
To deal with bootloader you run Fastboot commands from the Windows shell, either CMD or PowerShell.

no it didnt get unlock it only say message ok
i tried this command fastboot getvar unlocked
which give me message unlocked:no and i am running linux so i am using its commandline working with it and as i say it didnt get unlocked what is the problem i cant figure it out
jwoegerbauer said:
What happened is that you got a OK, means phone's bootloader now got unlocked.
To deal with bootloader you run Fastboot commands from the Windows shell, either CMD or PowerShell.
Click to expand...
Click to collapse

[[email protected]]-[~]
>>> adb reboot bootloader
* daemon not running; starting now at tcp:5037
* daemon started successfully
error: no devices/emulators found
[[email protected]]-[~]
>>> adb reboot bootloader
error: insufficient permissions for device
See [http://developer.android.com/tools/device.html] for more information
[[email protected]]-[~]
>>> adb reboot bootloader
[[email protected]]-[~]
>>> fastboot oem unlock
< waiting for any device >
FAILED (remote: 'Unlock bootloader fail.')
fastboot: error: Command failed
[[email protected]]-[~]
>>> fastboot reboot fastboot
Rebooting into fastboot OKAY [ 0.018s]
< waiting for any device >
Finished. Total time: 17.010s
[[email protected]]-[~]
>>> fastboot oem unlock
OKAY [ 0.001s]
Finished. Total time: 0.001s
[[email protected]]-[~]
>>> fastboot getvar unlocked
unlocked: no
Finished. Total time: 0.001s
[[email protected]]-[~]
>>>
here is the commands and the output as u see and i already enabled oem in the developer options

Reboot Android to make changes permanent

jwoegerbauer said:
Reboot Android to make changes permanent
Click to expand...
Click to collapse
u mean reboot after i did the command?
i did it nothing change

try this method
https://forum.xda-developers.com/t/is-my-life-really-worth-it.4217751/post-84295797

fastboot flashing unlock