Code:
X:\Program Files\ANDROID\SDK\platform-tools>fastboot oem unlock
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.013s
Any suggestions? My device is recognized by and trusting my PC. I also tried the Device Unlock app by T-Mobile USA which says it isn't compatible with my device.
Go to developer options first then enable oem unlocking. Should work now
Thanks sooooooo much. I feel dumb yet don't remember this step on other devices. Guess I never had to unlock a Marshmallow phone? Also not mentioned in this thread I was searching http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930.
Edit: Nor google.
echardcore said:
Thanks sooooooo much. I feel dumb yet don't remember this step on other devices. Guess I never had to unlock a Marshmallow phone? Also not mentioned in this thread I was searching http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930.
Edit: Nor google.
Click to expand...
Click to collapse
This is a new, surprisingly under-the-radar thing you have to do. It got me at first, too when I tried to unlock it before first boot.
Another question.
I accidentally tapped and disabled Developer Options. When I reenabled it, the OEM Unlocking option was disabled. Did just RELOCK it?
EDIT:
It seems like its still unlocked.
Ok so I was reading an article and now I'm confused. I see there are two ways to unlock a phone...the regular unlock command and an unlock critical command. From what I understand the unlock critical command is for updating the bootloader? When would I want to do this? I was on the Android P final beta and because official Pie release was delayed here in Canada I decided to just unlock and flash Pie manually. I did this and then relocked the bootloader. But is my bootloader outdated now? Confused. ?
If you keep the bootloader unlocked your bootloader will never go out of date, otherwise the bootloader will not be updated on subsequent stock ROM updates. I personally recommend unlocking the bootloader using both commands and keeping it unlocked. You'll have a minor annoyance in that you'll have a warning pop up prior to boot about the bootloader being unlocked, but I believe avoid a major annoyance in Factory Reset Protection being disabled with the bootloader unlock.
Ok. So just unlock using both commands? Do I just enter in right after the other? How does the bootloader get updated?
Also does leaving the bootloader unlocked stop Google Pay and some banking apps from working?
Enter both commands, one after the other. The bootloader, even if it has no updates, is included with every copy of the stock ROM you download from Google. It will also be included with any OTAs that come directly to the device. You'll have to discover for yourself whether Google Pay and your banking app are affected, because I simply do not know. I don't use my device for banking.
Is it too soon to start a bounty for a bootloader unlock? Do we even have any devs using this device(Lm-G710TM)? Im good for $100+.
It's not soon for USA unlocked (G710ULM) because 11th July was the release, till now why there's no bootloader for this unlocked variant! Already European variant enjoying root.
I usually give it like two months before I expect activity to pick up for new phones; even when owning Nexus phones. But, it's very discouraging to see how dead this place is, especially for any US variants. If there's no encouraging development for this phone by the time the Pixel 3 drops, I might just ditch this phone for that instead. This is a solid phone, but it could be absolutely great with a custom ROM/kernel.
totally agree, this is a great and solid phone. Could use a few tweaks and it'll be even better!
Alcolawl said:
I usually give it like two months before I expect activity to pick up for new phones; even when owning Nexus phones. But, it's very discouraging to see how dead this place is, especially for any US variants. If there's no encouraging development for this phone by the time the Pixel 3 drops, I might just ditch this phone for that instead. This is a solid phone, but it could be absolutely great with a custom ROM/kernel.
Click to expand...
Click to collapse
Now that I took care of the H932 V30 getting root, it is time to move on to you guys....
So, since I don't own this phone, I need some details if you guys would like me to help you get it rooted.
1 - Did T-Mobile pull fastboot oem unlock, or can you still at least unlock your bootloader?
2 - If they did pull the ability, how do other G7s unlock their bootloader?
3 - Can someone provide me with a dump of laf? Maybe there is a KDZ around here that I missed, but it is early, and I am not going searching just yet.
-- Brian
runningnak3d said:
Now that I took care of the H932 V30 getting root, it is time to move on to you guys....
So, since I don't own this phone, I need some details if you guys would like me to help you get it rooted.
1 - Did T-Mobile pull fastboot oem unlock, or can you still at least unlock your bootloader?
2 - If they did pull the ability, how do other G7s unlock their bootloader?
3 - Can someone provide me with a dump of laf? Maybe there is a KDZ around here that I missed, but it is early, and I am not going searching just yet.
-- Brian
Click to expand...
Click to collapse
I know VZW it's all locked The OEM switch is missing also. I'm assuming for at least Verizon there needs to be an exploit if ever found.
For now, I am just talking about the TMO version.
-- Brian
runningnak3d said:
Now that I took care of the H932 V30 getting root, it is time to move on to you guys....
So, since I don't own this phone, I need some details if you guys would like me to help you get it rooted.
1 - Did T-Mobile pull fastboot oem unlock, or can you still at least unlock your bootloader?
2 - If they did pull the ability, how do other G7s unlock their bootloader?
3 - Can someone provide me with a dump of laf? Maybe there is a KDZ around here that I missed, but it is early, and I am not going searching just yet.
-- Brian
Click to expand...
Click to collapse
https://forum.xda-developers.com/lg-g7-thinq/help/t-mobile-oem-unlock-t3833156
runningnak3d said:
For now, I am just talking about the TMO version.
-- Brian
Click to expand...
Click to collapse
Welcome aboard mate, been looking for your presence here but was doubting it as you don't have this device as of yet. I'm happy to see you and say that I was wrong, can't thank you enough for the work you have done on other devices.
Will be more than willing to help anyway I can, although I am currently on the sprint variant for the moment.
Hey @ps3hacker3 Long time no speak
Yea, I have learned enough that it is getting a lot easier even if I don't have the phone. However, I am going to need some info from people that DO have the G710TM.
-- Brian
runningnak3d said:
Hey @ps3hacker3 Long time no speak
Yea, I have learned enough that it is getting a lot easier even if I don't have the phone. However, I am going to need some info from people that DO have the G710TM.
-- Brian
Click to expand...
Click to collapse
LG G710ULM owner here. I know it's not specifically a T-Mobile version but it does allow OEM unlocking by default. I could be wrong, but I'm guessing the differences between the G710TM and G710ULM aren't that big (if any at all). If you need any info from my end, let me know. I'd love to get the ball rolling on bootloader unlocks for this phone. Lots of untapped potential here.
So you have the slider in developer options for "Allow OEM Unlocking" .. do you have fastboot oem unlock?
-- Brian
runningnak3d said:
So you have the slider in developer options for "Allow OEM Unlocking" .. do you have fastboot oem unlock?
-- Brian
Click to expand...
Click to collapse
Upon rebooting into Bootloader I'm presented with a quick guide for unlocking the phone:
1) Read Device ID
:fastboot oem device-id
2) Write Unlock Key
:fastboot flash unlock unlock.bin
3)Check bootloader is unlocked
:fastboot getvar unlocked
fastboot oem unlock results in a FAILED (remote: 'unknown command') message. Screenshot attached. My first attempt didn't work because I guess I didn't have the right bootloader drivers installed.
So it looks like even the unlocked models are in the same boat as everyone else, except Europe.
runningnak3d said:
So you have the slider in developer options for "Allow OEM Unlocking" .. do you have fastboot oem unlock?
-- Brian
Click to expand...
Click to collapse
The T-Mobile version has the oem unlock slider.
Edit: if I run the fastboot oem unlock command, nothing happens. The phone when using reboot bootloader, gives me 3 options. Get ID, check unlock, I forget the wording on the other, but it's basically to input your unlock file I think.
20degrees said:
The T-Mobile version has the oem unlock slider.
Edit: if I run the fastboot oem unlock command, nothing happens. The phone when using reboot bootloader, gives me 3 options. Get ID, check unlock, I forget the wording on the other, but it's basically to input your unlock file I think.
Click to expand...
Click to collapse
On my Windows 10 machine, when this phone is in Bootloader and plugged in via USB, Device Manager showed it as just "Android" with a warning symbol next to it. Had to grab the latest Google ADB and Fastboot drivers and force install the drivers (Choose from list, Have Disk..., Android Bootloader Interface, etc.) in order for the computer to actually recognize the phone properly when in the Bootloader. Otherwise issuing Fastboot commands just resulted in <waiting for any device> or whatever. Strange, because I haven't touched this OS install in probably a year and I had no problems issuing commands to my Pixel XL in Bootloader this spring.
Anyways, looks like until LG decides they want to support unlocking other variants, we're dead in the water.
Alcolawl said:
On my Windows 10 machine, when this phone is in Bootloader and plugged in via USB, Device Manager showed it as just "Android" with a warning symbol next to it. Had to grab the latest Google ADB and Fastboot drivers and force install the drivers (Choose from list, Have Disk..., Android Bootloader Interface, etc.) in order for the computer to actually recognize the phone properly when in the Bootloader. Otherwise issuing Fastboot commands just resulted in <waiting for any device> or whatever. Strange, because I haven't touched this OS install in probably a year and I had no problems issuing commands to my Pixel XL in Bootloader this spring.
Anyways, looks like until LG decides they want to support unlocking other variants, we're dead in the water.
Click to expand...
Click to collapse
Be forewarned, I've noticed that fastboot doesn't always work, despite latest drivers. As of late, the Pixel has been known to hang on these same commands at times as well. My Moto Z2 Force suffers from this error as well.
---------- Post added at 04:11 AM ---------- Previous post was at 04:04 AM ----------
runningnak3d said:
Now that I took care of the H932 V30 getting root, it is time to move on to you guys....
So, since I don't own this phone, I need some details if you guys would like me to help you get it rooted.
1 - Did T-Mobile pull fastboot oem unlock, or can you still at least unlock your bootloader?
2 - If they did pull the ability, how do other G7s unlock their bootloader?
3 - Can someone provide me with a dump of laf? Maybe there is a KDZ around here that I missed, but it is early, and I am not going searching just yet.
-- Brian
Click to expand...
Click to collapse
I hope you know many are INCREDIBLY excited to have you on board! I'm not advanced, but once I receive my computer back, I'll definitely be available to help with providing info and helping test, as I have a TMO variant (I may or may not work for TMO as well, so yeah... )
runningnak3d said:
So you have the slider in developer options for "Allow OEM Unlocking" .. do you have fastboot oem unlock?
-- Brian
Click to expand...
Click to collapse
Own a TMobile variant, oem unlocking option is there, fastboot commands do not work (or are extremely limited)
getprop | grep unlock (if it means anything)
[Ro.oem_unlock_supported]: [1]
[Sys.oem_unlock_allowed]: [1]
I know I probably didn't help out much, if you have any other questions feel free to ask I'll help out as much as I can. thank you for contributions and congrats on the V30 root.
runningnak3d said:
Now that I took care of the H932 V30 getting root, it is time to move on to you guys....
So, since I don't own this phone, I need some details if you guys would like me to help you get it rooted.
1 - Did T-Mobile pull fastboot oem unlock, or can you still at least unlock your bootloader?
2 - If they did pull the ability, how do other G7s unlock their bootloader?
3 - Can someone provide me with a dump of laf? Maybe there is a KDZ around here that I missed, but it is early, and I am not going searching just yet.
-- Brian
Click to expand...
Click to collapse
I have the tmobile variant. Let me know what you might need.
Unlock Slider is present in developer settings and is not greyed out. Unlock command just hangs.
runningnak3d said:
So you have the slider in developer options for "Allow OEM Unlocking" .. do you have fastboot oem unlock?
-- Brian
Click to expand...
Click to collapse
Sprint variant also has "Allow OEM unlocking" available and it is changeable
So you can issue fastboot flashing unlock_critical but not fastboot flashing unlock -- that is just weird.
If you issue the unlock_critical, do you get the warning that your phone is possibly corrupt, but will continue to boot?
-- Brian
i went through the process of aquiring the unlock code via motorola website and i got an alert message saying it didnt qualify for bootloader unlock, is there any way around this? idc if i have to erase everything as its an old phone anyway, any help would be appreciated
cam9293 said:
i went through the process of aquiring the unlock code via motorola website and i got an alert message saying it didnt qualify for bootloader unlock, is there any way around this? idc if i have to erase everything as its an old phone anyway, any help would be appreciated
Click to expand...
Click to collapse
No way around it.
Although the unlock site is very buggy.
Many people get that message, but later are able to unlock.
I suggest running getvar all
Code:
fastboot getvar all
And then compare the cid code from getvar all, with the list of cids.
There's a link in my bootloader unlock thread.
[Guide]Un/locking Motorola Bootloader
UnLocking and ReLocking Motorola Bootloader https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a Moto Bootloader Unlocking site Re-Locking see Post #4 More about bootloader UnLocking Post #2 Can my...
forum.xda-developers.com
sd_shadow said:
No way around it.
Although the unlock site is very buggy.
Many people get that message, but later are able to unlock.
I suggest running getvar all
Code:
fastboot getvar all
And then compare the cid code from getvar all, with the list of cids.
There's a link in my bootloader unlock thread.
[Guide]Un/locking Motorola Bootloader
UnLocking and ReLocking Motorola Bootloader https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a Moto Bootloader Unlocking site Re-Locking see Post #4 More about bootloader UnLocking Post #2 Can my...
forum.xda-developers.com
Click to expand...
Click to collapse
verified, unlockable. would i be able to root my device somehow still?
cam9293 said:
verified, unlockable. would i be able to root my device somehow still?
Click to expand...
Click to collapse
No rooting Moto devices unless the bootloader is unlocked.
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 bootloader​To 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 bootloader​To 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.