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

Petr S. · 12-04-2017, 20:58

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. Here some outputs:

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.
fastboot devices
QHC0216327001941 fastboot

Now:
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

fastboot oem get-lockstate
...
(bootloader) locked
OKAY [ -0.000s]
finished. total time: -0.000s

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.

fehveiga · 12-04-2017, 23:07

I'm having the same problem, have you found a solution?

fehveiga · 12-05-2017, 01:05

I solved with the help of the firmware that recognized, but it did a good job to find out that even though it was OK when writing the firmware, it actually meant error because frp is active and can not disable it.
but as she showed me her original version with a great help from google and xda I managed to recover and yes

Petr S. · 12-05-2017, 09:40

Can you please write some good overview, which software/method did you usedto solve it? Can you be more specific? Cause .. i have no idea which direction should i go now. Can the HCU help?

Petr S. · 12-06-2017, 18:32

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

)

12-04-2017, 20:58	#1 (permalink)
Petr S. Junior Member Join Date: Dec 2017 Posts: 3 Member: 2785673 Status: Offline Thanks Meter: 0	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. Here some outputs: 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. fastboot devices QHC0216327001941 fastboot Now: 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 fastboot oem get-lockstate ... (bootloader) locked OKAY [ -0.000s] finished. total time: -0.000s 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.

12-04-2017, 23:07	#2 (permalink)
fehveiga Insane Poster Join Date: Feb 2009 Location: Brasil Posts: 83 Member: 971926 Status: Offline Thanks Meter: 13	I'm having the same problem, have you found a solution?

12-05-2017, 01:05	#3 (permalink)
fehveiga Insane Poster Join Date: Feb 2009 Location: Brasil Posts: 83 Member: 971926 Status: Offline Thanks Meter: 13	I solved with the help of the firmware that recognized, but it did a good job to find out that even though it was OK when writing the firmware, it actually meant error because frp is active and can not disable it. but as she showed me her original version with a great help from google and xda I managed to recover and yes

12-05-2017, 09:40	#4 (permalink)
Petr S. Junior Member Join Date: Dec 2017 Posts: 3 Member: 2785673 Status: Offline Thanks Meter: 0	Can you please write some good overview, which software/method did you usedto solve it? Can you be more specific? Cause .. i have no idea which direction should i go now. Can the HCU help?

12-06-2017, 18:32	#5 (permalink)
Petr S. Junior Member Join Date: Dec 2017 Posts: 3 Member: 2785673 Status: Offline Thanks Meter: 0	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 )