I am curious... This tool claims to be able to unlock several phones' bootloaders. does it do this by calling HTC's own bootloader unlocking service, or did someone reverse engineer the unlock codes based on the device ID?
My initial guess would be yes since the megathread on the tool (where I tried to ask this question to no avail) indicates that it can unlock more phones than the HTC tool supports.
I just recieved my phone and before I installed anything, I was going thru it and saw that it has the option to enable oem unlock? Anyone else get this or able to further a rooting process since it has it enabled?
OEM unlock in the settings just sets a bit in frp partition.
This would allow you to unlock the bootloader IF you could
1) access the bootloader in the first place
2) it would have the necessary commands available
2a) fastboot oem unlock (android standard)
2b) fastboot flash unlock unlock.bin (or so, for LG) with the unlock.bin provided by lg, generated by device id and imei (aka needs to be whitelisted by them)
on the sd845 devices, those that flash an engineering bootloader from someone with an octoplus box, use 2a because thats available there (after they had to wipe laf to enter fastboot)
but for that to try you would need
1) someone with an octoplux box, capable of flashing to sd855 LG devices
2) some leaked engineering bootloader (or create your own via reverse engineering, but one wrong step here, and brick basically)
I appreciate the return and detailed response. I am moving from the samsung galaxy s8 active to this V50. So I got excited about seeing the enable oem switch in developers mode, being that the s8 doesnt even display it. I miss being able to tinker with a device since the nexus 5x. This one is a beaut tho. So we'll see if life can adjust to it. the S8 was good, overall, for what it was. But having a secure, or at least ipi68+mil std, is not for one who enjoys to tinker. You mentioned about LG whitlisting it. Is there such a way to have that requested, or is it a result of a form of consequence?
As Mr.mayb2 requested...here a rooted boot.img from the US Verizon LG Velvet.
Pulled the original boot.img directly from the kdz that was provided to me via
http://lgegdmswdl.s.llnwi.net/dn/do...5CAIKAED3DRMO/G900VM10e_00_VZW_US_OP_1009.kdz
Then did un'kdz and un'dz.
loaded it into magisk and patched the file.
Please note that LG Velvet has 2 bootloader partitions. so be sure that you patch it to a/b.
How to unlock bootloader
29y6145 said:
How to unlock bootloader
Click to expand...
Click to collapse
Thats the thing where everything will stand and fall.
To unlock the bootloader you need an unlock-code from the vendor.
For the EU-Version i got that via mail from LG.
But i've no clue if LG does this for US too.
Does that come down to LG or to the carriers (Verizon, ATT, etc)?
WELCOMETOOCEANIA said:
Does that come down to LG or to the carriers (Verizon, ATT, etc)?
Click to expand...
Click to collapse
Got it this way.
LG Developer
The official developer resources for LG products and platforms.
developer.lge.com
MikGx said:
Got it this way.
LG Developer
The official developer resources for LG products and platforms.
developer.lge.com
Click to expand...
Click to collapse
Yes, but it only supports the EU variants as of now. Would the decision to not unlock US variants come down to an LG decision or the carriers not allowing it?
However, when I did try to use that tool I could only get my IMEI and not my device ID. It says "OK" when I enter my IMEI too so I'm wondering whether it would also accept my device ID and work anyway.
But, I'm having difficulties finding my device ID (or at least the full 64 character one they want). The ones I get from apps that pull it are only 16 character. The fastboot/bootloader method they give on that page doesn't work for me (to get the device ID). Possibly because rebooting to bootloader in ADB does nothing but reboot the phone. Rebooting to fastboot works but the commands don't work to get the device ID.
Do you know how to find the device ID otherwise?
WELCOMETOOCEANIA said:
Yes, but it only supports the EU variants as of now. Would the decision to not unlock US variants come down to an LG decision or the carriers not allowing it?
However, when I did try to use that tool I could only get my IMEI and not my device ID. It says "OK" when I enter my IMEI too so I'm wondering whether it would also accept my device ID and work anyway.
But, I'm having difficulties finding my device ID (or at least the full 64 character one they want). The ones I get from apps that pull it are only 16 character. The fastboot/bootloader method they give on that page doesn't work for me (to get the device ID). Possibly because rebooting to bootloader in ADB does nothing but reboot the phone. Rebooting to fastboot works but the commands don't work to get the device ID.
Do you know how to find the device ID otherwise?
Click to expand...
Click to collapse
Sry.
Dont know about lg´s politics concerning this.
Just reacted on the request to produce an rooted boot.img.
Maybe plead lg via mail to the bones givin other regions possibility to root...?
WELCOMETOOCEANIA said:
Yes, but it only supports the EU variants as of now. Would the decision to not unlock US variants come down to an LG decision or the carriers not allowing it?
However, when I did try to use that tool I could only get my IMEI and not my device ID. It says "OK" when I enter my IMEI too so I'm wondering whether it would also accept my device ID and work anyway.
But, I'm having difficulties finding my device ID (or at least the full 64 character one they want). The ones I get from apps that pull it are only 16 character. The fastboot/bootloader method they give on that page doesn't work for me (to get the device ID). Possibly because rebooting to bootloader in ADB does nothing but reboot the phone. Rebooting to fastboot works but the commands don't work to get the device ID.
Do you know how to find the device ID otherwise?
Click to expand...
Click to collapse
Maybe try getting into fastbootd by rebooting in fastboot to fastbootd
Fastboot reboot fastbootd
Worth a shot.
you cant root without a bootloader unlock and you arent getting it with the verizon version. the velvet is down to $120 and although its tempting, i wouldnt do it without the unlock.
Anyone with unlocked abl or eng abl for Velvet G900EM, EMW or Wing F100EM, EMW I can unlock bootloader and root device, just have unlocked abl or eng abl
Mr.PvT said:
Anyone with unlocked abl or eng abl for Velvet G900EM, EMW or Wing F100EM, EMW I can unlock bootloader and root device, just have unlocked abl or eng abl
Click to expand...
Click to collapse
Hava you been able to unlock yours? Im on Korea version and if you can unlock yours with exploit then I can also do the same with LG token
I can't unlock bootloader for my lg velvet LM-G900VM
Please suggest how to root?
I recently used the correct msm tool to flash back to android 10 stock for this device and everything worked perfectly it showed IN2017 all is well , however even with auto update disabled the phone is auto updating to android 11 and in the process of this its changing the model number to IN2015. i was trying to unlock my bootloader but fastboot oem get_unlock_code is just saying it doesnt understand the command, so i cant get a code at all , the only command it will take is fastboot oem oproot which gives an "unlock code" but it says incorrect on the oneplus site also. If i use msm tool to go back to 10 all these commands work and give me an unlock code but the oneplus website is still saying incorrect code, what can i do i dont understand how its changing models because of an OTA update
Hi--did you ever figure this out? I'm looking to buy an OP8 and am going to want to root; there's a 2017 available at a good price in that gorgeous shimmery color, but I'm wondering if I should stick with the IN2015. Any advice (I'll actually need it if I do get the IN2017, not just to piggyback on your thread, but since no one was responding...)?
Thx and gl
Hello,
PROBLEM:
I have a phone, and it has an option in Settings -> System -> Developer options, called "OEM unlocking", and I have activated it.
But there is NO way in reality, to do that (all the adb or fastboot commands say that the device is closed, including the one that unlocks the bootloader), so... with no firmware available, and no TWRP, it is impossible to unlock the bootloader, root and of course, install any custom roms.
ASSUMPTION:
IF the manufacturer sells a phone with that option available, should we, the users, be always allowed to do that ? Is the seller violating any customer laws or terms of service by not doing that ?
SELLER ANSWER:
I've received from the seller this justification:
"
Please be advised that open Bootloader as well as other technical specifications of the OS were being designed by Google, the developer of the AndroidTM project. For more details, please consult Google Support for Android: https://support.google.com/android/topic/7651524?hl=en&ref_topic=7311597
In order to perform a fresh install of the proprietary software, you can use our direct service process by our authorized service partner, blablablah"
NOTES:
That phone I'm talking about is an Alcatel 3 2019, so nothing really remarkable, I know... but I'm asking a generic question for all the devices.
Thanks in advance !
I wouldn't blame the seller. I don't know anything about Alcatel devices, but if OEM Unlocking is toggleable in Developer Options, you should be able to unlock the bootloader via fastboot. Exactly how to do that may depend on the device.
This article details how it works. You essentially have 3 components at play here:
ro.oem.unlock.supported, which is baked into the ROM, determines whether OEM Unlocking is available in Developer Options.
get_unlock_ability is the state of OEM Unlocking. Off is 0, on is 1.
If get_unlock_ability=1, the bootloader can be unlocked via fastboot, usually by using fastboot flashing unlock, but in Alcatel's case, may be fastboot oem unlock
Hope this helps.
V0latyle said:
I wouldn't blame the seller. I don't know anything about Alcatel devices, but if OEM Unlocking is toggleable in Developer Options, you should be able to unlock the bootloader via fastboot. Exactly how to do that may depend on the device.
This article details how it works. You essentially have 3 components at play here:
ro.oem.unlock.supported, which is baked into the ROM, determines whether OEM Unlocking is available in Developer Options.
get_unlock_ability is the state of OEM Unlocking. Off is 0, on is 1.
If get_unlock_ability=1, the bootloader can be unlocked via fastboot, usually by using fastboot flashing unlock, but in Alcatel's case, may be fastboot oem unlock
Hope this helps.
Click to expand...
Click to collapse
Thanks ! but...
fastboot flashing get_unlock_ability -> FAILED (remote: 'unknown command')
fastboot flashing unlock -> same
fastboot oem unlock -> same
observingman said:
Hello,
PROBLEM:
I have a phone, and it has an option in Settings -> System -> Developer options, called "OEM unlocking", and I have activated it.
But there is NO way in reality, to do that (all the adb or fastboot commands say that the device is closed, including the one that unlocks the bootloader), so... with no firmware available, and no TWRP, it is impossible to unlock the bootloader, root and of course, install any custom roms.
ASSUMPTION:
IF the manufacturer sells a phone with that option available, should we, the users, be always allowed to do that ? Is the seller violating any customer laws or terms of service by not doing that ?
SELLER ANSWER:
I've received from the seller this justification:
"
Please be advised that open Bootloader as well as other technical specifications of the OS were being designed by Google, the developer of the AndroidTM project. For more details, please consult Google Support for Android: https://support.google.com/android/topic/7651524?hl=en&ref_topic=7311597
In order to perform a fresh install of the proprietary software, you can use our direct service process by our authorized service partner, blablablah"
NOTES:
That phone I'm talking about is an Alcatel 3 2019, so nothing really remarkable, I know... but I'm asking a generic question for all the devices.
Thanks in advance !
Click to expand...
Click to collapse
What soc in that device?
observingman said:
Thanks ! but...
fastboot flashing get_unlock_ability -> FAILED (remote: 'unknown command')
fastboot flashing unlock -> same
fastboot oem unlock -> same
Click to expand...
Click to collapse
It looks like the OEM uses different commands for its bootloader. What exact model of device do you have?
Try fastboot -i 0x1bbb oem unlock
V0latyle said:
It looks like the OEM uses different commands for its bootloader. What exact model of device do you have?
Try fastboot -i 0x1bbb oem unlock
Click to expand...
Click to collapse
Thanks again... it didn't work:
C:\WINDOWS\system32>fastboot -i 0x1bbb oem unlock
fastboot: unknown option -- i
The model is the alcatel 3 2019 5053Y
PizzaG said:
What soc in that device?
Click to expand...
Click to collapse
For the device (alcatel 3 2019 5053Y), the soc is the Qualcomm SDM439 Snapdragon 439 (12 nm):
alcatel 3 (2019) - Full phone specifications
www.gsmarena.com
Google didn't help much, so you might be SOL with this device.
V0latyle said:
Google didn't help much, so you might be SOL with this device.
Click to expand...
Click to collapse
Ouch ! Yep, it's sad... Anyway, thanks
By the way, I can access the shell (no root of course) by using 'adb shell' ... Is there any way then, to dump the boot partition without root and locked bootloader?) I assume you must be LOL right now
observingman said:
By the way, I can access the shell (no root of course) by using 'adb shell' ... Is there any way then, to dump the boot partition without root and locked bootloader?) I assume you must be LOL right now
Click to expand...
Click to collapse
Unfortunately no, without root access it is not possible to dump partition contents, with the exception of /data.