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ś..

Help Huawei p8 lite Bricked and infinite boot-loop and only access to fastboot mode

hi guys i have found on my hand a huawei p8 lite in an infinite boot-loop and cant access to any thing only fastboot but the problem that the bootloader is locked and i have no way to unlock it and when i try to flash anything with fastboot i get this error
target max-download-size: 450MB
sending 'boot' (21706 KB)...
OKAY [ 0.469s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.484s
target max-download-size: 450MB
sending 'recovery' (34280 KB)...
OKAY [ 0.750s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.750s
target max-download-size: 450MB
sending 'cust' (218981 KB)...
OKAY [ 4.710s]
writing 'cust'...
FAILED (remote: Command not allowed)
finished. total time: 4.726s
target max-download-size: 450MB
Sparse-Flash is enabled!
sending sparse 'system' (460798 KB)...
OKAY [ 10.479s]
writing 'system'...
FAILED (remote: Command not allowed)
finished. total time: 10.479s
i tried to unlock the bootloader at https://emui.huawei.com/en/plugin/unlock/detail but i have no Product ID no serial number and no product number and it been a hell of tow days i calculated the product id with the huawei generator and the website tells me the imei is wrong try the second imei and i dont have anyone have an idea how to unbricke it cant flash i tried every possible firmware and i cant enter update mode with sdcard:crying::crying::crying:

AnonDz said:
hi guys i have found on my hand a huawei p8 lite in an infinite boot-loop and cant access to any thing only fastboot but the problem that the bootloader is locked and i have no way to unlock it and when i try to flash anything with fastboot i get this error
target max-download-size: 450MB
sending 'boot' (21706 KB)...
OKAY [ 0.469s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.484s
target max-download-size: 450MB
sending 'recovery' (34280 KB)...
OKAY [ 0.750s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.750s
target max-download-size: 450MB
sending 'cust' (218981 KB)...
OKAY [ 4.710s]
writing 'cust'...
FAILED (remote: Command not allowed)
finished. total time: 4.726s
target max-download-size: 450MB
Sparse-Flash is enabled!
sending sparse 'system' (460798 KB)...
OKAY [ 10.479s]
writing 'system'...
FAILED (remote: Command not allowed)
finished. total time: 10.479s
i tried to unlock the bootloader at https://emui.huawei.com/en/plugin/unlock/detail but i have no Product ID no serial number and no product number and it been a hell of tow days i calculated the product id with the huawei generator and the website tells me the imei is wrong try the second imei and i dont have anyone have an idea how to unbricke it cant flash i tried every possible firmware and i cant enter update mode with sdcard:crying::crying::crying:
Click to expand...
Click to collapse
Hold volume up while connected to PC......You should enter eRecovery....From there download firmware and install

no way to connect it i tried
and when i try to get the unlock code to the bootloader in the website it gives me this error
Please make sure the verification code and model number are correct. If your device has multiple IMEIs or MEIDs, please try another IMEI or MEID.

AnonDz said:
no way to connect it i tried
and when i try to get the unlock code to the bootloader in the website it gives me this error
Please make sure the verification code and model number are correct. If your device has multiple IMEIs or MEIDs, please try another IMEI or MEID.
Click to expand...
Click to collapse
I didn't say anything about unlock bootloader....
Just holds power and volume up button while connected to PC.......
BTW how did you end up in boot loop ?

and i just add that i couldn't unlock the bootloader and i already told you that i have access onlyn to fastboot and rescue mode bro

do you think i will be here if i could enter the recovery update

The only thing I can think of is to install Hisuite to a windows PC and try the recovery option in hi suite
---------- Post added at 08:43 PM ---------- Previous post was at 08:40 PM ----------
Oh another thing did you register your phone to a google account?
If you did log into Google dashboard and expand the Android section it will list all of your devices and the imei so you should be able to use that to unlock the bootloader

AnonDz said:
no way to connect it i tried
and when i try to get the unlock code to the bootloader in the website it gives me this error
Please make sure the verification code and model number are correct. If your device has multiple IMEIs or MEIDs, please try another IMEI or MEID.
Click to expand...
Click to collapse
I have unlock my bootloader using this video tutorial give a try

cristi.blidariu said:
I have unlock my bootloader using this video tutorial give a try
Click to expand...
Click to collapse
I already tried this method and yet nothing

ndg_2000 said:
The only thing I can think of is to install Hisuite to a windows PC and try the recovery option in hi suite
---------- Post added at 08:43 PM ---------- Previous post was at 08:40 PM ----------
Oh another thing did you register your phone to a google account?
If you did log into Google dashboard and expand the Android section it will list all of your devices and the imei so you should be able to use that to unlock the bootloader
Click to expand...
Click to collapse
And no I got the phone in this state so no I didn't connect it to my google account

Ok i searched for ways to find an IMEI number and found couple of ways...
1) Look under/in the sim tray. It may be there (I didn't check this out)
2) Find the IMEI/MEID using Google Dashboard. This is Google's control center that can be accessed from any computer with a web browser. You will need to log in with the Google account associated with your Android phone.You can access Google Dashboard by visiting www.google.com/settings/dashboard Expand the "Android" section by clicking the "Android" heading.Locate your phone in the list. If you have multiple devices associated with your account, all of the devices will be displayed. Find the device that you are trying to retrieve the IMEI/MEID number for. (This works)
3) At last, you can try to remove the back case and remove the battery. This can help you in 2 ways. Firstly, there should be IMEI code present under the battery. Secondly, this may cause you to get out of bootloop

How can oem unlock leEco le pro 3 x722///Is there a solution 2 ?

Hi guys
I destroyed my leEco le pro 3 x722
After passing the custom rom
Now the device is locked on fastboot only
There is no system and no recovery
The problem I have now is the decryption. If the oem unlock is I can update it. Please help oem unlock
The device does not respond to commands
Everything is written
PS C: \ adb> fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (39337 KB) ...
OKAY [0.895s]
writing 'recovery' ...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.940s
How can oem unlock in another way ?
Is there a solution?: EEK:

toufik_d said:
Hi guys
I destroyed my leEco le pro 3 x722
After passing the custom rom
Now the device is locked on fastboot only
There is no system and no recovery
The problem I have now is the decryption. If the oem unlock is I can update it. Please help oem unlock
The device does not respond to commands
Everything is written
PS C: \ adb> fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (39337 KB) ...
OKAY [0.895s]
writing 'recovery' ...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.940s
How can oem unlock in another way ?
Is there a solution?: EEK:
Click to expand...
Click to collapse
Go to 722 thread and you will find out how to
Sent from my SM-A730F using xda premium

Bootloader still locked when developer options have it disabled...

In developer options it says its OEM unlocked, but when i use fastboot , it tells me oem_locked and wont let me install twrp or anything. Any suggestions???

wbill2k said:
In developer options it says its OEM unlocked, but when i use fastboot , it tells me oem_locked and wont let me install twrp or anything. Any suggestions???
Click to expand...
Click to collapse
First you need to unlock your bootloader to install twrp. Here is the procedure to unlock bootloader
https://forum.xda-developers.com/g5-plus/how-to/unlock-bootloader-lenovo-motorola-moto-t3581133

Thanks man....
I got the bootloader unlocked, but this is what happens when i try to flash twrp...
PS C:\Users\wbill\Downloads\TWRP> fastboot flash recovery twrp-3.2.3-1-potter.img
target reported max download size of 534773760 bytes
sending 'recovery' (16316 KB)...
OKAY [ 0.422s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.375s]
finished. total time: 0.797s
PS C:\Users\wbill\Downloads\TWRP>
riyan65 said:
First you need to unlock your bootloader to install twrp. Here is the procedure to unlock bootloader
https://forum.xda-developers.com/g5-plus/how-to/unlock-bootloader-lenovo-motorola-moto-t3581133
Click to expand...
Click to collapse

wbill2k said:
I got the bootloader unlocked, but this is what happens when i try to flash twrp...
PS C:\Users\wbill\Downloads\TWRP> fastboot flash recovery twrp-3.2.3-1-potter.img
target reported max download size of 534773760 bytes
sending 'recovery' (16316 KB)...
OKAY [ 0.422s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.375s]
finished. total time: 0.797s
PS C:\Users\wbill\Downloads\TWRP>
Click to expand...
Click to collapse
That means it was successful. Boot into recovery after that

Trying to Root Magisk

I have a patched boot image, trying to root with Magisk android 10 Essential phone. I have bootloader and critical unlocked, and no pin or password. I keep getting C:\Users\johns\Desktop\Magisk 2.21.20>fastboot flash boot magisk_patched.img
target reported max download size of 536870912 bytes
sending 'boot_a' (24097 KB)...
OKAY [ 0.598s]
writing 'boot_a'...
FAILED (remote: Flashing is not allowed in Lock State)
finished. total time: 0.601s
What could possibly be locked at this point? I am trying to root with just magisk, don't want twrp. Is it possible?

Sure bootloader is unlocked? Does it say unlocked from the fastboot screen? You may have typed the unlock command but it may not have executed

gk1984 said:
Sure bootloader is unlocked? Does it say unlocked from the fastboot screen? You may have typed the unlock command but it may not have executed
Click to expand...
Click to collapse
Same problem Here. Anyone have the solution?