I have G710EMW and want to unlock bootloader. As may u aware LG officially not supported unlocking bootloader for Indian devices. So I tried to unlock bootloader via edl mode and v35 image.
I tried multiple times to flash the V35 image on abl_a and its always flashed and reflected operational successful. But somehow it does not make any change and due to that "fastboot oem unlock" not working (unknown command)
I tried many times with different PC also but don't know what is the issue.
Tired with different versions of the Qualcomm flash tool also.
Is there any other flashing tool available that can flash abl-a? Any alternative?
Or any alternative method for bootloader unlock?
Related
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.
Anyone know how to lock the bootloader successfully? Clarification - I can lock the bootloader successfully but then can't boot normally.
I have a Frankenstein LG G7 emw from Aliexpress.
I have crossflashed it with an open EUR 10 Q kdz (G710EM)
After flashing the V35 onto abl_a and using "fastboot oem lock" the command is successful.
If I then restore my backed up original abl_a I then get a red triangle bootloop. I also sometimes get an unpatched fastboot screen with correct model type (G710EMW instead of the V35 one)
However I am unable to boot normally and then have to restore the V35, unlock the bootloader again, restore original abl, get into download mode and then reflash kdz using LGUP.
What do I need to lock the the bootloader and then boot normally? I want to be able to use Google pay and banking apps
Any help, ideas, tips or clues appreciated
I did relock the bootloader and successfully booted into system, but in between for 10 days my phone was like a dead hardware before coming into original working state.
sourabh7625 said:
I did relock the bootloader and successfully booted into system, but in between for 10 days my phone was like a dead hardware before coming into original working state.
Click to expand...
Click to collapse
When using fastboot to relock bootloader did you use the V35 abl_a or the G7 abl_a?
I'm thinking this may be where I'm going wrong but I haven't had time to test it out yet
gridmuncher said:
When using fastboot to relock bootloader did you use the V35 abl_a or the G7 abl_a?
I'm thinking this may be where I'm going wrong but I haven't had time to test it out yet
Click to expand...
Click to collapse
It was running on competely stock just booted into fastboot from using "adb reboot bootloader" and entered "fastboot oem lock" and everything worked fine.
What's state your phone currently in ? And what is your desired state ?
I have cross flashed the phone with an Android 10 kdz (european 30f). The bootloader is unlocked, but I cannot relock the bootloader. I have erased the laf_a partition to enable fastboot, but then "fastboot oem lock" doens't work. If I flash the v35 to abl_a then th command works but then the phone is in a red triangle bootloop.
I have tried extensively to google it but I have no idea how to make it work. I backed up numerous partitions using QFIL and tried to restore them once bootloader was locked but nothing seemed to help. The only way out of the bootloop was to return to download mode a reflash a kdz using LGUP
Hello!
So, I've purchased a T-Mobile LG G8 ThinQ phone for use in Canada and wanted to remove the T-Mobile splash.
After reading a bit on the forums here, it seems like it'll be too complex for someone like me. (I'm lazy)
So, I uninstalled Magisk, which supposedly uninstalls root and I'm looking to relock my boot loader.
Just I'm having a hard time getting back into bootloader with the vol- and power button method, and using adb to reboot into bootloader doesn't seem to give the desired results.
The phone just reboots like normal with the unlocked bootloader warning.
Reason I wanna relock it is so that I can use Android Pay again and using Magisk Hide or the alternative would require them to give a guaranteed result.
One day it could be patched and I won't be near a PC to resolve the issue and I personally don't like carrying my wallet.
cheddarest said:
Hello!
So, I've purchased a T-Mobile LG G8 ThinQ phone for use in Canada and wanted to remove the T-Mobile splash.
After reading a bit on the forums here, it seems like it'll be too complex for someone like me. (I'm lazy)
So, I uninstalled Magisk, which supposedly uninstalls root and I'm looking to relock my boot loader.
Just I'm having a hard time getting back into bootloader with the vol- and power button method, and using adb to reboot into bootloader doesn't seem to give the desired results.
The phone just reboots like normal with the unlocked bootloader warning.
Reason I wanna relock it is so that I can use Android Pay again and using Magisk Hide or the alternative would require them to give a guaranteed result.
One day it could be patched and I won't be near a PC to resolve the issue and I personally don't like carrying my wallet.
Click to expand...
Click to collapse
I'm not an expert (or even that experienced with phone flashing), but a li'l Googling gives this result. The relevant part being:
Re-locking the bootloaderTo re-lock the bootloader:
For newer devices (2015 and higher):
fastboot flashing lock
For older devices (2014 and lower):
fastboot oem lock
Note: Re-locking the bootloading on a Motorola Xoom erases all user data (including the shared USB data).
blaacksheep said:
I'm not an expert (or even that experienced with phone flashing), but a li'l Googling gives this result. The relevant part being:
Re-locking the bootloaderTo re-lock the bootloader:
For newer devices (2015 and higher):
fastboot flashing lock
For older devices (2014 and lower):
fastboot oem lock
Note: Re-locking the bootloading on a Motorola Xoom erases all user data (including the shared USB data).
Click to expand...
Click to collapse
Sure, I'll try that if you can help me figure out why I can't get back into the bootloader.
You need to use QFIL to put flash back the engineering abl file to get fastboot. Then you can run the command.
armodons said:
You need to use QFIL to put flash back the engineering abl file to get fastboot. Then you can run the command.
Click to expand...
Click to collapse
Thank you! That worked, I was flashing abl_a and abl_b with the backup images to see if that did anything.
I’ve unlocked my bootloader and rooted previously on the stock A10 ATT rom. I’ve then cross flashed to the A11 CAN version. Bootloader is still obviously unlocked but root is gone. I understand how to root again but I can’t get into bootloader mode to see if I have an active boot_a or boot_b. Does anyone know how to do this or any other way to see which is active? I’ve tried button combinations and ADB reboot bootloader command with no luck. It was working fine previously but I can no longer get into it after crossflashing.
BWA_Dallas said:
I’ve unlocked my bootloader and rooted previously on the stock A10 ATT rom. I’ve then cross flashed to the A11 CAN version. Bootloader is still obviously unlocked but root is gone. I understand how to root again but I can’t get into bootloader mode to see if I have an active boot_a or boot_b. Does anyone know how to do this or any other way to see which is active? I’ve tried button combinations and ADB reboot bootloader command with no luck. It was working fine previously but I can no longer get into it after crossflashing.
Click to expand...
Click to collapse
You probably don't have the engineering abl flashed to the appropriate abl slot. Using that abl is what gives you fastboot. But once you've used it, you have to flash the original back, so that the phone will boot. The engineering abl is based on an earlier version of android.
This is exactly what I needed. Thank you!
Hello, I have a device, iqoo10. I want to unlock the BootLoader for better use, but I find that all methods cannot be unlocked, such as using fastboot vivo or directly using Google's official unlocking command fastboot flashing unlock. Because vivo has modified the boot, it must use the vivo tool to unlock. A more difficult problem arises. The vivo unlocking tool only supports iqoo9, so I cannot unlock