Database Info

[Q] FAILED (remote: signature verify fail) unlock bootloader via htcdev.com

Hi guys ;
i tried to unlock bootloader on my desire s via htcdev.com. i got file Unlock_code.bin. On the next step
C:\Android>fastboot flash unlockten Unlock_code.bin
sending 'unlockten' (0 KB)...
OKAY [ 0.018s]
writing 'unlockten'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 0.034s
i got this. i couldn't unlock bootloader. i tried on different usb ports Do you have any idea How can i fix this ?

qurshot said:
Hi guys ;
i tried to unlock bootloader on my desire s via htcdev.com. i got file Unlock_code.bin. On the next step
C:\Android>fastboot flash unlockten Unlock_code.bin
sending 'unlockten' (0 KB)...
OKAY [ 0.018s]
writing 'unlockten'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 0.034s
i got this. i couldn't unlock bootloader. i tried on different usb ports Do you have any idea How can i fix this ?
Click to expand...
Click to collapse
fixed. I tried different computers and usb ports. Finally fixed. :good:

qurshot said:
fixed. I tried different computers and usb ports. Finally fixed. :good:
Click to expand...
Click to collapse
Make sure fastboot is unchecked in the settings. Menu, settings, power options than uncheck fastboot and ensure usb debugging is enabled

qurshot said:
fixed. I tried different computers and usb ports. Finally fixed. :good:
Click to expand...
Click to collapse
It was because you used "unlockten" instead of "unlocktoken". The error message is not helpful since it says signature is invalid because it tried to flash a partition such as boot or recovery or whatever. But our Unlock_code.bin is not signed this kind of way.

Rooting and unlocking bootloader with newest miui version

Hello,
i cant figure out how is it possible to unlock the bootloader & root after having the newest update.
I cant flash anything using fastboot - it says my device is locked
the version - MIUI-V7.2.3.0.LXKCNDA
any solution? :crying:

first you must unlock bootloader.

dani9998 said:
Hello,
i cant figure out how is it possible to unlock the bootloader & root after having the newest update.
I cant flash anything using fastboot - it says my device is locked
the version - MIUI-V7.2.3.0.LXKCNDA
any solution? :crying:
Click to expand...
Click to collapse
You got the answer, first unlock the bootloader, then flash whatever you want https://youtu.be/ZkBLrn0Dzt4
Enviado desde mi Mi-4c mediante Tapatalk

i get following error:
C:\fastboot>fastboot devices
8c718fed fastboot
C:\fastboot>fastboot oem edl
...
OKAY [ 0.001s]
finished. total time: 0.004s
C:\fastboot>fastboot oem unlock bootloader
...
FAILED (remote: Token verification failed, reboot the device)
finished. total time: 0.011s
C:\fastboot>fastboot oem unlock bootloader
...
FAILED (remote: Token verification failed, reboot the device)
finished. total time: 0.014s
C:\fastboot>fastboot oem unlock bootloader
...
FAILED (remote: Token verification failed, reboot the device)
finished. total time: 0.017s
Click to expand...
Click to collapse

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

Is it possible to reunlock a relocked bootloader without the unlock code?

I have an honor 9 (stf-l09). Yesterday I flashed the stock firmware via HURU. Now I have the bootloader locked but when I go in bootloader mode it says "Phone Unlocked / FRP Unlock" but when I try to flash something via adb it says :
[email protected]:~$ fastboot flash recovery_ramdisk '/home/me/desktop/stf-twrp-zxz-0.3.img'
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (27144 KB)...
OKAY [ 0.903s]
writing 'recovery_ramdisk'...
FAILED (remote: Command not allowed)
finished. total time: 0.910s
What can I do?
I'm on ubuntu 18.04 but it does the same on windows.

AirPl said:
I have an honor 9 (stf-l09). Yesterday I flashed the stock firmware via HURU. Now I have the bootloader locked but when I go in bootloader mode it says "Phone Unlocked / FRP Unlock" but when I try to flash something via adb it says :
[email protected]:~$ fastboot flash recovery_ramdisk '/home/me/desktop/stf-twrp-zxz-0.3.img'
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (27144 KB)...
OKAY [ 0.903s]
writing 'recovery_ramdisk'...
FAILED (remote: Command not allowed)
finished. total time: 0.910s
What can I do?
I'm on ubuntu 18.04 but it does the same on windows.
Click to expand...
Click to collapse
Are you sure that you have USB debugging enabled in developer options on the device? Do you have OEM unlock enabled?
Sent from my LGL84VL using Tapatalk

Droidriven said:
Are you sure that you have USB debugging enabled in developer options on the device? Do you have OEM unlock enabled?
Click to expand...
Click to collapse
Yes, I've already done that but nothing happens, same command and same result

Trouble with G110A (NOT Verizon) bootloader

Trying to root my phone to flash Alexndr ROM. Phone is Google purchased (NOT verizon) pixel 2 G011A . USB Debug and OEM unlocking are toggled "on."
From the bootloader screen, and connected to the computer, this is the result from the following commands:
fastboot flashing unlock
FAILED (remote: 'Flashing Unlock is not allowed') fastboot: error: Command failed
Click to expand...
Click to collapse
fastboot flashing unlock_critical
FAILED (remote: 'unknown command') fastboot: error: Command failed
Click to expand...
Click to collapse
It is communicating with the device:
fastboot devices
{{device serial number}} fastboot
Click to expand...
Click to collapse
and unlocking the bootloader seems to be enabled on the phone
fastboot flashing get_unlock_ability
(bootloader) get_unlock_ability: 1
OKAY [ 0.000s]
Finished. Total Time: 0.000s
Click to expand...
Click to collapse
I've tried all the USB ports on several computers with both Win10 and linux, with the same result.
On the phone itself, developer options are enabled, USB debugging is enabled, and OEM unlocking is enabled. Curiously, OEM unlocking becomes grayed out and disabled after enough failed attempts, but I've been fixing this with a factory reset.
The Android version is 11, build RP1A.201005.004A1
What am I missing here? Why wont this bootloader unlock? Thanks!

I have the same problem. Can someone please explain how to fix this?