Database Users

Can't flash TWRP with unlocked bootloader

Hiii,
I've read many threads but didn't find my answer, I have an unlocked bootloader but can't flash TWRP recovery.
Tried many different versions but all tries give me an "remote: image verification error"
Device is fastboot mode:
C:\Temp>fastboot devices -l
4<serial hidden>7 fastboot
Bootloader unlocked with official unlock code:
C:\Temp>fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.006s]
finished. total time: 0.007s
Flash TWRP (failed) and flash STOCK (success):
C:\TEMP>fastboot flash recovery recovery_twrp.img
target reported max download size of 471859200 bytes
sending 'recovery' (28928 KB)...
OKAY [ 0.617s]
writing 'recovery'...
FAILED (remote: image verification error)
finished. total time: 0.634s
C:\TEMP>fastboot flash recovery recovery_stock.img
target reported max download size of 471859200 bytes
sending 'recovery' (32960 KB)...
OKAY [ 0.701s]
writing 'recovery'...
OKAY [ 1.102s]
finished. total time: 1.805s
Any ideas... what can I do/ what should try?
Thx!
Strange is when I :
C:\Temp>fastboot oem get-lockstate
...
(bootloader) locked
OKAY [ 0.004s]
finished. total time: 0.005s
it say's it's locked, but when I try to unlock with correct code, it gives a message wrong password, so it's unlocked :|

roelprincen said:
Hiii,
I've read many threads but didn't find my answer, I have an unlocked bootloader but can't flash TWRP recovery.
Tried many different versions but all tries give me an "remote: image verification error"
Device is fastboot mode:
C:\Temp>fastboot devices -l
4<serial hidden>7 fastboot
Bootloader unlocked with official unlock code:
C:\Temp>fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.006s]
finished. total time: 0.007s
Flash TWRP (failed) and flash STOCK (success):
C:\TEMP>fastboot flash recovery recovery_twrp.img
target reported max download size of 471859200 bytes
sending 'recovery' (28928 KB)...
OKAY [ 0.617s]
writing 'recovery'...
FAILED (remote: image verification error)
finished. total time: 0.634s
C:\TEMP>fastboot flash recovery recovery_stock.img
target reported max download size of 471859200 bytes
sending 'recovery' (32960 KB)...
OKAY [ 0.701s]
writing 'recovery'...
OKAY [ 1.102s]
finished. total time: 1.805s
Any ideas... what can I do/ what should try?
Thx!
Strange is when I :
C:\Temp>fastboot oem get-lockstate
...
(bootloader) locked
OKAY [ 0.004s]
finished. total time: 0.005s
it say's it's locked, but when I try to unlock with correct code, it gives a message wrong password, so it's unlocked :|
Click to expand...
Click to collapse
same with me ?

Try to relock and then unlock. I've had this problem too after downgrade to mm by official Huawei rollback package. Then phone and other tools shows than phone is unlocked and it was unable to flash recovery.

if it says wrong password it means you got the wrong password. it will say it's already unlocked if you try unlocking it while it's unlocked

My phone was unlocked with Potato v2.0.1, with working TWRP, rooted etc...
I solved this problem that arose after unsuccesfully install custom Rom, restore backup of stock rom, install update through dload and many many other attempts at improvement of my smartphone :-( No more time again!!!
Probably installing update through Dload will relock bootloader, but in the fastboot mode it says bootloader still unlocked.
Before I did all this, I had an original stock rom.
1: Relock bootloader with PotatoNV v2.0.1 (You need to open case and connect tespoint by wire - look on Youtube, i´ve find it there, also you need "Huawei testpoint drivers")
2: Factory reset
3: Install any update stock rom with Dload (Vol up + Vol down + power)
4: Factory reset
5: Developer options-turn on OEM unlock and USB debbuging
6:Unlock bootloader with PotatoNV v2.0.1 - keep password generated by Potato
7:Multitool 8 for Huawei - in the bootloader state unlock bootloader again - use password generated by Potato
8:Multitool 8 for huawei - install TWRP - it says "Succesfully installed" - TWRP works, root is possible. Yeah!!!
May be this is not right way to solve this, but for me it workś..

Huawei P8Lite ALE-L21 C432B584 TWRP Help

Hi all.
Problem with my Huawei Ale-l21
Ive unlocked bootloader atleast it shows Phone Unlocked.
But everythime i want intall costum twrp recovery it shows in CMD
target reported max download size of 471859200 bytes
sending 'recovery' (12644 KB)...
OKAY [ 1.368s]
writing 'recovery'...
FAILED (remote: image verification error)
finished. total time: 1.371s
Tryed lots of twrp images. Noting works. Is that possible that B584 version does not support it or whats the problem ?

Fastboot Drivers

Hello guys,
I know this question is very common but I have looked many posts and couldn't find any that solved my problem.
I am trying to flash the stock moto X pure edition (xt1575) again in my device. The trouble starts because fastboot doesn't work.
I already installed Motorola device manager (2.5.4) and booted windows without driver signature enforcement.
I tried adb-setup-1.4.3.exe and installing android SDK, but still get same trouble.
The phone works and get normally funcional when android is loaded, but no responde in fastboot screen!
I am using windows 10.15063.296 (creators update). When I open device manager, now I see "Motorola adb device" with an exclamation.

A lot of windows, especially windows 10, users seem to struggle with drivers. I use Linux and never have any problems.
Maybe you could give this a try. https://www.xda-developers.com/forget-windows-use-linux-is-a-usb-bootable-distro-for-your-android-recovery-needs-xda-spotlight/

jason2678 said:
A lot of windows, especially windows 10, users seem to struggle with drivers. I use Linux and never have any problems.
Maybe you could give this a try. https://www.xda-developers.com/forg...or-your-android-recovery-needs-xda-spotlight/
Click to expand...
Click to collapse
Thanks. After hours trying, I could get fastboot working.
The issue now is that I got "preflash failed" when trying the officially image available.
Enviado de meu XT1575 usando Tapatalk

Belotto said:
Thanks. After hours trying, I could get fastboot working.
The issue now is that I got "preflash failed" when trying the officially image available.
Enviado de meu XT1575 usando Tapatalk
Click to expand...
Click to collapse
Just on bootloader and gpt.bin, or everything?
That happens when you try to downgrade the partition table, but usually as long as you flash all the other parts successfully it works. Keep a close eye on the output when you flash modem; it tends to fail on the first try.

https://forum.xda-developers.com/showthread.php?t=2588979
This is the one... I had this on my window's 10. I upgraded to creators update and i doubted that this might not work but it did work for me

jason2678 said:
Just on bootloader and gpt.bin, or everything?
That happens when you try to downgrade the partition table, but usually as long as you flash all the other parts successfully it works. Keep a close eye on the output when you flash modem; it tends to fail on the first try.
Click to expand...
Click to collapse
I really wasn´t successful...
PS C:\Android\sdk\platform-tools\CLARK_RETUS_MPH24.49-18_18_retus_US> adb reboot-bootloader
PS C:\Android\sdk\platform-tools\CLARK_RETUS_MPH24.49-18_18_retus_US> fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.016s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.370s
PS C:\Android\sdk\platform-tools\CLARK_RETUS_MPH24.49-18_18_retus_US> fastboot flash motoboot motoboot.img
error: cannot load 'motoboot.img'
PS C:\Android\sdk\platform-tools\CLARK_RETUS_MPH24.49-18_18_retus_US> fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s
PS C:\Android\sdk\platform-tools\CLARK_RETUS_MPH24.49-18_18_retus_US> fastboot flash logo logo.bin
target reported max download size of 536870912 bytes
sending 'logo' (3687 KB)...
OKAY [ 0.137s]
writing 'logo'...
OKAY [ 0.200s]
finished. total time: 0.337s
PS C:\Android\sdk\platform-tools\CLARK_RETUS_MPH24.49-18_18_retus_US> fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (40960 KB)...
OKAY [ 1.518s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.888s
PS C:\Android\sdk\platform-tools\CLARK_RETUS_MPH24.49-18_18_retus_US> fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (41040 KB)...
OKAY [ 1.534s]
writing 'recovery'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.887s
PS C:\Android\sdk\platform-tools\CLARK_RETUS_MPH24.49-18_18_retus_US> fastboot flash system system.img
target reported max download size of 536870912 bytes
sending sparse 'system' (509631 KB)...
OKAY [ 17.857s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 18.357s
PS C:\Android\sdk\platform-tools\CLARK_RETUS_MPH24.49-18_18_retus_US> fastboot reboot
rebooting...
finished. total time: 0.016s
PS C:\Android\sdk\platform-tools\CLARK_RETUS_MPH24.49-18_18_retus_US> fastboot erase userdata
erasing 'userdata'...
OKAY [ 6.423s]
finished. total time: 6.423s
PS C:\Android\sdk\platform-tools\CLARK_RETUS_MPH24.49-18_18_retus_US> fastboot erase cache
erasing 'cache'...
OKAY [ 0.031s]
finished. total time: 0.031s
PS C:\Android\sdk\platform-tools\CLARK_RETUS_MPH24.49-18_18_retus_US> fastboot oem lock
...
(bootloader) Please run fastboot oem lock begin first!
OKAY [ 0.015s]
finished. total time: 0.015s
PS C:\Android\sdk\platform-tools\CLARK_RETUS_MPH24.49-18_18_retus_US> fastboot oem lock begin
...
(bootloader) Not supported command in current status!
FAILED (remote failure)
finished. total time: 0.017s
PS C:\Android\sdk\platform-tools\CLARK_RETUS_MPH24.49-18_18_retus_US> fastboot oem lock
...
(bootloader) Please run fastboot oem lock begin first!
OKAY [ 0.000s]
finished. total time: 0.000s
PS C:\Android\sdk\platform-tools\CLARK_RETUS_MPH24.49-18_18_retus_US>

jason2678 said:
Just on bootloader and gpt.bin, or everything?
That happens when you try to downgrade the partition table, but usually as long as you flash all the other parts successfully it works. Keep a close eye on the output when you flash modem; it tends to fail on the first try.
Click to expand...
Click to collapse
Sagar_1401 said:
https://forum.xda-developers.com/showthread.php?t=2588979
This is the one... I had this on my window's 10. I upgraded to creators update and i doubted that this might not work but it did work for me
Click to expand...
Click to collapse
I have tried it before... wasn't working but i realized that i needed to push "allow oem unlock" and "usb debugging" buttons ... LOL.

Honor 8 Lite Hard-Bricked in BOOTLOADER mode.

Hi all, Please help me.
Just yesterday, I screwed my Honor 8 Lite.
By hoping to solve issue missing fingerprint option, I've flashed my Honor 8 Lite PRA-TL10 Russian to PRA-LA1C185B101(MiddleEast).
Flashing steps that I did:
- Unlock bootloader
- Flash Elite-TWRP and boot into TWRP
- Flash PRA-LA1C185's OEMINFO from TWRP.
- Flash StockRecovery.img from TWRP.
- Put SDCard that contains "dload" from PRA-LA1C185101 firmware
- Disconnect and Power off device.
- Force Update firmware by pressing Volume_UP + Volume_Down + Power.
- Firmware updating process began.. and I left it running...
- 10 minutes later I check the phone and IT IS DEAD! OMG!!!
Phone's screen remain black/dark, no vibration, no response to combinations buttons press, no sign of life. Then I try to connect to PC, device still detected as "ADB Sooner Single ADB Interface", and it is in bootloader mode. I can and have use fastboot command to "flash" boot/recovery/system/cust/userdata, but it failed to bring my Honor 8 Lite alive..
The screen still remain black/dark, no matter what button I pressed, it keeps rebooting into bootloader mode.
When I check from fastboot:
C:\Huawei\ROM\Restore>fastboot getvar rescue_phoneinfo
rescue_phoneinfo: PRA-LA1C185B165
finished. total time: 0.012s
C:\Huawei\ROM\Restore>fastboot devices
DUPNW17XXXXXXXX3 fastboot
C:\Huawei\ROM\Restore>fastboot oem check-rootinfo
...
(bootloader) old_stat: NULL
(bootloader) now_stat: NULL
(bootloader) change_time: NULL
OKAY [ 0.020s]
finished. total time: 0.021s
Click to expand...
Click to collapse
My fastboot flashing results:
C:\Huawei\ROM\Restore>fastboot flash boot boot.img
target reported max download size of 471859200 bytes
sending 'boot' (15520 KB)...
OKAY [ 2.728s]
writing 'boot'...
OKAY [ 0.300s]
finished. total time: 3.030s
C:\Huawei\ROM\Restore>fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (35568 KB)...
OKAY [ 5.787s]
writing 'recovery'...
OKAY [ 0.669s]
finished. total time: 6.458s
C:\Huawei\ROM\Restore>fastboot flash cust cust.img
target reported max download size of 471859200 bytes
sending 'cust' (111459 KB)...
OKAY [ 2.794s]
writing 'cust'...
OKAY [ 0.811s]
finished. total time: 3.607s
C:\Huawei\ROM\Restore>fastboot flash system system.img
target reported max download size of 471859200 bytes
sending sparse 'system' 1/6 (460796 KB)...
OKAY [ 12.158s]
writing 'system' 1/6...
OKAY [ 3.654s]
sending sparse 'system' 2/6 (457285 KB)...
OKAY [ 12.152s]
writing 'system' 2/6...
OKAY [ 3.055s]
sending sparse 'system' 3/6 (458042 KB)...
OKAY [ 12.358s]
writing 'system' 3/6...
OKAY [ 3.507s]
sending sparse 'system' 4/6 (430632 KB)...
OKAY [ 11.429s]
writing 'system' 4/6...
OKAY [ 2.938s]
sending sparse 'system' 5/6 (460799 KB)...
OKAY [ 12.158s]
writing 'system' 5/6...
OKAY [ 2.952s]
sending sparse 'system' 6/6 (456400 KB)...
OKAY [ 12.178s]
writing 'system' 6/6...
OKAY [ 2.989s]
finished. total time: 91.539s
C:\Huawei\ROM\Restore>fastboot flash userdata userdata.img
target reported max download size of 471859200 bytes
sending sparse 'userdata' 1/2 (458754 KB)...
OKAY [ 12.080s]
writing 'userdata' 1/2...
(bootloader) success to erase cryypt info in oeminfo
OKAY [ 3.300s]
sending sparse 'userdata' 2/2 (290817 KB)...
OKAY [ 7.655s]
writing 'userdata' 2/2...
(bootloader) success to erase cryypt info in oeminfo
OKAY [ 1.884s]
finished. total time: 24.924s
C:\Huawei\ROM\Restore>fastboot flash oeminfo oeminfo
target reported max download size of 471859200 bytes
sending 'oeminfo' (65536 KB)...
OKAY [ 7.512s]
writing 'oeminfo'...
FAILED (remote: Command not allowed)
finished. total time: 7.522s
Click to expand...
Click to collapse
Bricked conditions:
- Screen remain OFF, no Light, no Image. I believe this is NOT LCD DAMAGED issue.
- Detected(Stuck) as bootloader device.
- Updatable/flashable from fastboot.
- No responses to buttons pressed, except POWER_LONG_PRESSED to reboot... into bootloader again and again.
- Bootloader unlocked.
Please any body help me..
EDIT:
I've revived my device with DC Phoenix flashing tool, using firmware PRA-TL10C10B170.
Thanks to Mr. HasanMirza01 for his great supports. I won't be able to revive this device without him.
For others who facing this same issue, just buy service from DC(cost you min. 4 credits to 15 credits) and just flash it using DC-Phoenix and your original model's firmware. It will bring your Honor 8 Lite back to life once again.
NOTE:
NEVER convert PRA-AL00/PRA-TL00 model to PRA-LX1/PRA-LA1. Doing so will brick your device.

MultiTool Unbricking results
08:09:33: All images are found, everything is ready for the unbricking process.
08:10:10: Unbricking started. Your computer may freezes during the process.
08:10:10: flash boot "C:\Huawei\ROM\Restore\boot.img"
08:10:11: The Boot image is flashing successfully
08:10:11: flash system "C:\Huawei\ROM\Restore\system.img"
08:14:01: The System image is flashing successfully
08:14:01: flash cust "C:\Huawei\ROM\Restore\cust.img"
08:14:04: The Cust image is flashing successfully
08:14:04: flash recovery "C:\Huawei\ROM\Restore\recovery.img"
08:14:06: The Recovery image is flashing successfully
08:14:06: flash userdata "C:\Huawei\ROM\Restore\userdata.img"
08:15:18: target reported max download size of 471859200 bytes
sending sparse 'userdata' 1/2 (458754 KB)...
OKAY [ 12.109s]
writing 'userdata' 1/2...
(bootloader) success to erase cryypt info in oeminfo
OKAY [ 3.284s]
sending sparse 'userdata' 2/2 (272385 KB)...
OKAY [ 7.168s]
writing 'userdata' 2/2...
(bootloader) success to erase cryypt info in oeminfo
OKAY [ 1.802s]
finished. total time: 24.363s
08:15:18: Error#1
08:15:18: Completed
08:15:18: Something went wrong (((

DC - Unlocker 2 Client detection..
DC - Unlocker 2 Client 1.00.1390
Detecting phone :
selection :
manufacturer - Huawei phones
model - Auto detect (recommended)
Found Phone : PRA-LA1
Model : Huawei phone in fastboot mode
IMEI : 86xxxxxxxxxxxx3
Serial NR. : DUPNWxxxxxxxxxx3
Firmware : PRA-LA1C185B165
IMEI1:86xxxxxxxxxxxx6
FB LockState: LOCKED
USER LockState: UNLOCKED
unlocked
Battery state: 0

Can u access Erecovery??
by pressing vol up with power button.. release power button when phone b0ot up...
usb cable should be connected.... phone should be in shutdown state while using these steps.
2nd way to erecovery is hold volume up & power... when bootup release both buttons then press n hold volume up...

liboct87 said:
Can u access Erecovery??
by pressing vol up with power button.. release power button when phone b0ot up...
usb cable should be connected.... phone should be in shutdown state while using these steps.
2nd way to erecovery is hold volume up & power... when bootup release both buttons then press n hold volume up...
Click to expand...
Click to collapse
Unfortunately, no sir. It can not boot into eRecovery mode.
It can only boot into fastboot mode with screen off, no light at all.
This is strange, since I did not messing with bootloader.

I have the same problem, flashed OEM-info PRA-LX1C432 on my PRA-AL00C00
I thing no way out

eifeldragon said:
I have the same problem, flashed OEM-info PRA-LX1C432 on my PRA-AL00C00
I thing no way out
Click to expand...
Click to collapse
strange!!!!!
i did this before
i have PRA-LA1C185
flashed chinese oem than europe oem info... now m back to chinese....
try to get into erecovery ur problem will be solved br0
best of luck man

eifeldragon said:
I have the same problem, flashed OEM-info PRA-LX1C432 on my PRA-AL00C00
I thing no way out
Click to expand...
Click to collapse
liboct87 said:
strange!!!!!
i did this before
i have PRA-LA1C185
flashed chinese oem than europe oem info... now m back to chinese....
try to get into erecovery ur problem will be solved br0
best of luck man
Click to expand...
Click to collapse
I think there's are differences between the PRA-LA1/PRA-LX1 with PRA-AL00/PRA-TL10/PRA-TL00 devices..
I think those devices have different board firmware.
PRA-LA1 can be converted to PRA-LX1, may be, never tested..
PRA-AL00 can be converted to PRA-TL10. TESTED..
PRA-AL00 can not be converted to PRA-LA1.. like my case.. it BRICKED
PRA-TL10 can not be converted to PRA-LX1, it will bricked, like my case too.
Beware of Honor regions conversion..
I haven't test conversion with DC-HCU tool, may be it will work since it rebuild the whole board firmware..
Note: I've recover my bricked Honor 8 Lite. Thanks to Mr. HassanMirza01 that giving me a lot of supports. I'll never able to recover my Honor 8 Lite without him. He is really my life saviour.

Unlucky for us there's no free flashing tool to use in this case.
May be some expert can sniff on usb connections with paid tool, to see what commands send to the device. To see how that paid tool can flash our phone even if it is on bootloader mode, which we certainly couldn't do that with "fastboot". And willing to put works on it to provide Huawei users a powerful enough flashing tool, that could bring phone alive..
So we no need to worry about this hard-brick issue..

Sorry, double post..

So what service from DC-Unlocker exactly did you use?

My OP2 is bricked

My OP2 is bricked, just only use fastboot mode, when i use "fastboot oem unlock" command, it show ok & complete, and then offline suddenly.
So i try fastboot mode again, flash recovery, it show the phone is locked.
Can anyone help me ?
C:\WINDOWS\system32>fastboot oem unlock
...
OKAY [ 0.118s]
finished. total time: 0.118s
C:\WINDOWS\system32>fastboot flash recovery c:\twrp-3.2.1-0-oneplus2.img
target reported max download size of 536870912 bytes
sending 'recovery' (22180 KB)...
OKAY [ 0.653s]
writing 'recovery'...
FAILED (remote: device is locked. Cannot flash images)
finished. total time: 0.673s