Develop Bugs

MT7-TL10 Bootloader Unlocked BUT STILL LOCKED

Calling all the Huawei Experts to help me out on this!!
Short Summary of problem
On my Ascend Mate 7 MT7-TL10 (running Android 5.1.1 version B326) -The bootloader shows as unlocked but I still can't flash a custom recovery - It gives error 'FAILED (remote: image verification error)'. I am using the lastest version of ADB/Fastboot, I have USB drivers installed and I also have the Bootloader Unlock code from Huawei, which works and shows 'Done'
Please read the details below first and kindly see all attachments
Click to expand...
Click to collapse
Little bit more information
- On the Bootloader screen of my MT7-TL10 (Gold 32 GB, 3 GB RAM version), I see "Phone Unlocked" in red, which means that my bootloader is unlocked. (refer to attachment)
- When I run the command 'Fastboot OEM get-bootinfo', it returns 'UNLOCKED'.
- However, whenever I try to flash a custom recovery, it gives me an error 'FAILED: (remote: image verification error).
- At the same time, if I flash stock recovery, it is successful.
Detailed Information
- When I run the command 'fastboot oem get-bootinfo' it returns 'UNLOCKED'.
- However, when I run the command 'fastboot oem get-lockstate', it returns 'Locked'
- I rolled back to KitKat 4.4.2 - But the process of roll-back to KitKat 4.4.2 was not as simple as it was described in many forums and I first ended up soft-bricking the device
- I followed the restore process described on Huawei's website and ended up flashing a chinese ROM (JAZZ) on my MT7-TL10 and there were plethora of chinese apps
- Then, I unlocked the bootloader using (fastboot oem unlock <unlock code>) and on KitKat, both commands 'fastboot oem get-bootinfo' and 'fastboot oem get-lockstate' returned 'UNLOCKED' (Hurray!, That's what I thought but...)
- Realizing that the bootloader was finally unlocked, with the help of @acbka, I was finally able to restore Lollipop (version 5.1.1 - B326) and to my utter disgust, after upgrading, I found out that I was again not able to flash a custom ROM - On Lollipop, the command 'fastboot oem get-lockstate' again returned 'LOCKED' and the command 'fastboot oem get-bootinfo' returned 'UNLOCKED'
- As you can see, I was back to square 1 and I still can't unlock the bootloader and therefore, I cannot root my phone
Final statement
- When I rolled back to KitKat, the Bootloader showed as Unlocked and I was able to flash custom recovery TWRP
- After upgrading to Lollipop (5.1.1 B324 and B326), I am unable to flash custom recovery (somehow, the bootloader shows as 'Locked' when I run 'fastboot oem get-lockstate')
- If I flash stock recovery, it is successful
- The error 'FAILED (remote: image verification error)' implies that the bootloader is locked and that's why it forbids flashing of custom recovery BUT it allows flashing stock recovery
Please see the attached pictures, which will show what I mean.
I will really appreciate any help to enable me to flash a custom recovery!! Please help!

i also face the same problem any one can help us ?

try another bat file to flash recovery,
http://forum.xda-developers.com/mate-7/orig-development/tool-android-4-4-5-1-pc-t3186984

Thanks for replying. However, this won't help because I am directly running the fastboot command (not using a .bat file). The link that you posted is dead...
Please read this: I have explained in my post with scrrenshots that the fastboot command 'fastboot oem unlock CODE' works and shows 'Done', which means that it has unlocked the bootloader. If you repeat the command, it shows 'user already unlocked', which is a proof that the Fastboot command is working.
However, the problem is that flashing a custom Recovery shows a 'remote' error, which means that it is the bootloader, which is preventing the flashing of the custom recovery.
The problem is that on Android 5.1.1, the bootloader is appearing as locked even though the fastboot procedure shows that the bootloader was unlocked.
I have tried different fastboot binaries and also tried different procedures (including BAT files) but not able to beat this problem.
Sent from my HUAWEI MT7-TL10 using Tapatalk

prahastaabenk said:
try another bat file to flash recovery,
http://forum.xda-developers.com/mate-7/orig-development/tool-android-4-4-5-1-pc-t3186984
Click to expand...
Click to collapse
kingrk said:
Thanks for replying. However, this won't help because I am directly running the fastboot command (not using a .bat file). The link that you posted is dead...
Please read this: I have explained in my post with scrrenshots that the fastboot command 'fastboot oem unlock CODE' works and shows 'Done', which means that it has unlocked the bootloader. If you repeat the command, it shows 'user already unlocked', which is a proof that the Fastboot command is working.
However, the problem is that flashing a custom Recovery shows a 'remote' error, which means that it is the bootloader, which is preventing the flashing of the custom recovery.
The problem is that on Android 5.1.1, the bootloader is appearing as locked even though the fastboot procedure shows that the bootloader was unlocked.
I have tried different fastboot binaries and also tried different procedures (including BAT files) but not able to beat this problem.
Sent from my HUAWEI MT7-TL10 using Tapatalk
Click to expand...
Click to collapse
Edit: The link that you posted is not dead - it didn't open on my smartphone. The author of that post ACBKA helped me and we both tried it but could not beat the bootloader. While it shows that it is unlocked, it is still restrictive and doesn't allow flashing of custom recovery.

awzx_77 said:
i also face the same problem any one can help us ?
Click to expand...
Click to collapse
I have an idea!
I remember that when I was troubleshooting the problem (my smartphone was soft-bricked when I tried to rollback to KitKat and I ended up flashing Chinese 'Jazz' version on my TL10), I had realized that the bootloader was FULLY UNLOCKED on the chinese Jazz ROM and I could actually install a custom recovery. So, here is the idea:
a) First roll back to KitKat 4.4.2 --> I believe that there is a procedure on XDA to roll-back to KitKat
b) Change the phone's location to China
c) Install custom recovery and root phone by flashing superuser
d) Upgrade to Lollipop 5.1.1 (Chinese version)
e) Upgrade to Marshmallow beta (Chinese version)
f) Install custom recovery and root phone

same problem
just unlock the bootloader again using unlock code!
it worked for me

+1 for @xAghilx. Same here.

Rooting LG G4 H815 v29a with locked bootloader

Hello everyone.
Yesterday I decided to upgrade my G4 from MM to Nougat. I used a guide from xda (https://forum.xda-developers.com/g4/general/guide-upgrade-h815-locked-bootloader-to-t3684945) and it worked flawlessly.
However I want to root my G4 so I can install Xposed and Viper4Android but I have no clue how or if it's even possible to do it without downgrading my android version.
If anyone could link me a good guide or tell me how to do it I'd appreciate it a lot.

Just like in MM you can't root if your bootloader is locked.
Enjoy the N beta for now and just wait steadfasterX to release the unofficial BL unlock method

exermode said:
Hello everyone.
Yesterday I decided to upgrade my G4 from MM to Nougat. I used a guide from xda (https://forum.xda-developers.com/g4/general/guide-upgrade-h815-locked-bootloader-to-t3684945) and it worked flawlessly.
However I want to root my G4 so I can install Xposed and Viper4Android but I have no clue how or if it's even possible to do it without downgrading my android version.
If anyone could link me a good guide or tell me how to do it I'd appreciate it a lot.
Click to expand...
Click to collapse
First unlock Bootloader like in MM. YES its works in Nougat too !
Connect Phone via USB to PC with USB Debuggin in Developer option
In Terminal/ Console:
ADB Devices = Phone was detected
ADB reboot bootloader = Phone boot into Bootloader
FASTBOOT Devices = Phone was detected
FASTBOOT flash recovery twrp3.1.1-1-g4.img
Pull Battery out, put back and bootup Phone, first boot fails but the 2nd boot was okay.
After Phone boots up its in ADB Mode again.
ADB Devices = Phone was detected
ADB reboot recovery = Phone boot into TWRP
In TWRP, install TWRP and SU like you did in MM. Install Root Checker and check the root status, DONE
Finished, rooted Nougat !!

hello, I followed the guide step by step, I flashed the twrp recovery, but when I try to start the recovery mode, "no command" appears with the android symbol. I read online that just press a key combination I have tried many but I have not succeeded, if someone can help me thank him very much

vkoniv said:
hello, I followed the guide step by step, I flashed the twrp recovery, but when I try to start the recovery mode, "no command" appears with the android symbol. I read online that just press a key combination I have tried many but I have not succeeded, if someone can help me thank him very much
Click to expand...
Click to collapse
just do as how g7 goes in to recovery mode.

Gone to bootloop Please help me

My device is Redmi note 5 pro
I was on China miui10 with redwolf and want to flash fastboot rom via miflash but it was done in 1 sec and all gone to vain
So I took my phone to service centre and they said warrenty voids as u unlocked bootloader
So I thought to lock bootloader via commands as miflash didn't work
So I flashed mi recovery.....:crying:
It gone to bootloop:crying:
Even thought to flash a recovery but bootloader is not recognised by the pc
Flashed ADB drivers...
Please help me
It's just 10 days old

First I think you should flash TWRP of some sort and flash AOSP based custom ROM to at least be able to boot your phone. If that's done then you can lock your bootloader (if you still want to).

Kotesh koti said:
My device is Redmi note 5 pro
I was on China miui10 with redwolf and want to flash fastboot rom via miflash but it was done in 1 sec and all gone to vain
So I took my phone to service centre and they said warrenty voids as u unlocked bootloader
So I thought to lock bootloader via commands as miflash didn't work
So I flashed mi recovery.....:crying:
It gone to bootloop:crying:
Even thought to flash a recovery but bootloader is not recognised by the pc
Flashed ADB drivers...
Please help me
It's just 10 days old
Click to expand...
Click to collapse
post this in redmi note 5 pro forum

did you lock it or not ?
can you vol - and power to enter bunny screen fastboot ?
did you allowed usb debugging on device before bootloop ?
if still unlock with fastboot, try miflash tool with another version, seems that 1 second result is when tool do not know the phone model.
I used miflashsetupbeta
if relock than i guess it becomes very tricky if am not wrong (edl, testpin,...)here link
https://forum.xda-developers.com/redmi-note-5-pro/how-to/edl-mode-redmi-note-5-pro-t3779267

Hey you can still fix it if it's relocked. Just flash the proper recovery rom for your device.
https://forum.xda-developers.com/redmi-note-5-pro/how-to/tut-flashing-official-recovery-rom-t3798165
Or you can try to unlock the bootloader again with Miflash Unlock Tool.

sofrbrick/bootloop

Hi all,
I am new to this forum, but have some experience with rooting and custom roms(oneplus one and samsung)
Now with the Mi Max 3, which was unlocked, i have flashed the recovery twrp-3.2.3-0-nitrogen.img, but I did not realize that
i had to reboot into this recovery from the fastboot mode.
so I endet up with a locked bootloader and bottloop and am not able to unlock the bootloader again.
I think my only solution is the test-point method and a EDL authorized account.
Some help would be greatly appreciated.
thanks
Henry

You don't have to boot into the bootloader from fastboot mode, you can press the power button and volume up button like on almost all other Android phones to boot into TWRP recovery. Sometimes it takes a few attempts to get right, but you should learn how to do it eventually.
Unfortunately it sounds like you had one of the dodgy re-sold Chinese models that had been re-flashed with Global firmware and it's locked your bootloader again on reboot.
Your only option is to use the official Miui Flash tool to boot into fastboot mode, flash the latest Global Developer ROM, and then sign in with your account and apply to unlock the bootloader again using the Miui unlock program. It may be instant but, they'll probably make you wait 720 hours, as the entire point of the program was to stop phones like yours being re-sold outside China.
At least you'll have a usable, non-bricked device though.

Thanks for your answer.
now I have opened the backcover (yes was much work ( I succeded without destroying something) and could apply the test point method to get into the lde mode.
Win10 shows it as qualcomxx at com 3
what is the best way now to awake it to life again? even without unlocking.

hi,
with the test point method I could flash the chinese rom, and the mi max 3 is awaken to life again!
The bootloader is still locked.
I have applied for unlocking, but have to wait some 15 days.
One tip: if the case is open, one can apply a little bit of silicon grease to the small pins on the side of the plastic frame
before closing it. Opening it again is much easier then.
One question: if I replace the recovery.img of the chinese rom with a TWRP image (renamed to recovery.img)
and flash that modified rom with the test point method, could this probaly work?
With a working TWRP one could install other roms without unlocking bootloader.
If yes, which TWRP would you apply?
Thanks

freedoc said:
Hi all,
I am new to this forum, but have some experience with rooting and custom roms(oneplus one and samsung)
Now with the Mi Max 3, which was unlocked, i have flashed the recovery twrp-3.2.3-0-nitrogen.img, but I did not realize that
i had to reboot into this recovery from the fastboot mode.
so I endet up with a locked bootloader and bottloop and am not able to unlock the bootloader again.
I think my only solution is the test-point method and a EDL authorized account.
Some help would be greatly appreciated.
thanks
Henry
Click to expand...
Click to collapse
Flashing a recovery should not lock your bootloader, so I don't know how you did it. Note, that if you are using Xiaomi's firmware tool, you should not forget about unticking the box to lock the bootloader. But I would suggest to stay away from that tool and go command line instead with fastboot.
If you can access fastboot, I'd recommend to flash an official fastboot tgz ROM of your choice. Official ROM should boot even with an unlocked bootloader and you may start all over again more carefully.
So I think you might be able to avoid using EDL mode at this stage.

probally I forgot to untick that box. The bootloader is locked and I have to wait 319 hours.
I have got to love the test point EDL method which is simple and effective, and gave me control over the device again.
If I flash again the chinese fastboot rom (in which I have changed the original recovery.img into TWRP.img, named recovery.img) via the EDL
will that give me an installt TWRP (still with locked bootloader, but possible to install custom roms) or will i have a brick again?
thanks

freedoc said:
probally I forgot to untick that box. The bootloader is locked and I have to wait 319 hours.
I have got to love the test point EDL method which is simple and effective, and gave me control over the device again.
If I flash again the chinese fastboot rom (in which I have changed the original recovery.img into TWRP.img, named recovery.img) via the EDL
will that give me an installt TWRP (still with locked bootloader, but possible to install custom roms) or will i have a brick again?
thanks
Click to expand...
Click to collapse
Only you can answer that question by trying it out. Are you sure you have to wait for the unlocking again? Double check that! As I know you also need a priviliged xiaomi account to be able to resurrect a device in EDL mode.

Do GT310 need to be unlocked boot loader? How to?

Hi I have the wifi only gt310 and when I go to developer options there is no OEM unlock feature. I can get to recovery though using power and vol up on boot. Im just wondering if I can proceed to flash a new rom or if I need to unlock the bootloader - as I have not been successful with finding those instructions on how to do this
I was able to use adb to see my device but fastboot bootloader restart did not work. It seemed to hang on waiting for device.

You don't need to unlock bootloader on wifi only versions