i am getting oem unlocking in dev option grayed out. my device may be a verizon one (how to check it). Please guide to unlock the bootloader or guide me to downgrade from Q to Pie, so may be OEM bootloader option will become enable.
Related
First of all: Is it normal for my OEM unlocking to be greyed out with status "Bootloader already unlocked" on this device after unlocking the bootloader? On my pixel2xl the option is not greyed out even after unlocking the bootloader, so I'm confused.
More info: Trying to set up a Pixel 2 64GB unlocked version from google store, it came on 8.0 November update. I was able to unlock the bootloader, had trouble flashing to the latest February 8.1 straight from November 8.0, but was able to boot back into 8.0 and let it do the OTA to 8.1 February update successfully. I factory reset after updating to 8.1 February update and have been connected to wifi and have a sim card in while setting up (if that matters), and now the option for OEM unlocking is still greyed out with status "Bootloader already unlocked". Not that it really matters I guess since I want the bootloader to remain unlocked, but the fact that it's different on my 2 pixel devices makes me think I did something wrong somewhere or misconfigured something.
KnifeSkills said:
First of all: Is it normal for my OEM unlocking to be greyed out with status "Bootloader already unlocked" on this device after unlocking the bootloader? On my pixel2xl the option is not greyed out even after unlocking the bootloader, so I'm confused.
More info: Trying to set up a Pixel 2 64GB unlocked version from google store, it came on 8.0 November update. I was able to unlock the bootloader, had trouble flashing to the latest February 8.1 straight from November 8.0, but was able to boot back into 8.0 and let it do the OTA to 8.1 February update successfully. I factory reset after updating to 8.1 February update and have been connected to wifi and have a sim card in while setting up (if that matters), and now the option for OEM unlocking is still greyed out with status "Bootloader already unlocked". Not that it really matters I guess since I want the bootloader to remain unlocked, but the fact that it's different on my 2 pixel devices makes me think I did something wrong somewhere or misconfigured something.
Click to expand...
Click to collapse
Dont worry, its normal.
shagbag913 said:
Dont worry, its normal.
Click to expand...
Click to collapse
But what if I need to re-lock my bootloader? Don't I need this switch available?
lucasdeeiroz said:
But what if I need to re-lock my bootloader? Don't I need this switch available?
Click to expand...
Click to collapse
Nope.
To lock the bootloader, connect via USB to a computer that has the SDK Platform Tools on it, and reboot to the bootloader.
Open a command prompt in your "platform tools" folder and type:
Code:
fastboot flashing lock
This will lock your bootloader and wipe the device. I believe this also sets the "get_unlock_ability" flag to 0 (which the OEM unlock switch corresponds to).
To explain this a little more simply:
There are three components in play here.
First, there is a firmware flag that determines whether the device can be unlocked at all: "ro.oem_unlock_supported". If this is set to 0, OEM Unlocking will be greyed out and unlocking is not possible.
Second, there is another firmware flag that determines whether the bootloader can be unlocked:
"get_unlock_ability". This corresponds to the OEM Unlocking switch - off is 0, on is 1. If the switch is on/flag is set to 1, the bootloader may be unlocked.
Third, there's the bootloader itself. If the "get_unlock_ability" flag is set to 0, the bootloader will refuse unlock commands. If the bootloader is already unlocked, it will override the flag.
Hope this helps and makes sense!
KnifeSkills said:
First of all: Is it normal for my OEM unlocking to be greyed out with status "Bootloader already unlocked" on this device after unlocking the bootloader? On my pixel2xl the option is not greyed out even after unlocking the bootloader, so I'm confused.
More info: Trying to set up a Pixel 2 64GB unlocked version from google store, it came on 8.0 November update. I was able to unlock the bootloader, had trouble flashing to the latest February 8.1 straight from November 8.0, but was able to boot back into 8.0 and let it do the OTA to 8.1 February update successfully. I factory reset after updating to 8.1 February update and have been connected to wifi and have a sim card in while setting up (if that matters), and now the option for OEM unlocking is still greyed out with status "Bootloader already unlocked". Not that it really matters I guess since I want the bootloader to remain unlocked, but the fact that it's different on my 2 pixel devices makes me think I did something wrong somewhere or misconfigured something.
Click to expand...
Click to collapse
SkipSoft Download Page | SkipSoft.net
skipsoft.net
i came here just to say that i love you, great tips
Is it possible to root the t-mobile version on the latest rom? "OEM Unlocking" is greyed out for me. It seems like most content on this forum is for the international version so I'm a little weary of trying anything without clarification. All I want is for usb tethering to work properly.
You need to get SIM unlock before starting anything. Permanent SIM unlock. Then you can use a couple of guides around here to bootloader unlock (after checking OEM unlock AFTER you get SIM unlock), then from there you can use other guides here to root/magisk.
I'm not asking how, I already know that part. I have an unlocked TMobile/Sprint phone, but from reading TMobile roms are a bit different as they do thier own or modified oos.
I have checked and I can toggle the oem locking in settings. I own the phone outright but I don't have an unlocked sim. I've heard with TMobile you have to call and have the sim unlocked , which in turn let's you then toggle the oem unlock so you can unlock the bootloader.
So my question is, since I bought the phone unlocked, and I can toggle the oem unlock feature, can I just unlock the bootloader now and proceed with root or does it sim need to be unlocked too??
You have to go into fastboot to check if you have it toggled on in dev options go into bootloader and do fastboot oem unlock from command prompt it will unlock or it won't you may have to get an unlock token from one plus also TMobile locks bootloader you need an unlock token file
Help! I got the unlocked version and i updated it to android 11 and now oem unlock is greyed out. It says connect to internet or contact carrier and even though the internet is connected it is still greyed out someone please help me
smartasiankid said:
Help! I got the unlocked version and i updated it to android 11 and now oem unlock is greyed out. It says connect to internet or contact carrier and even though the internet is connected it is still greyed out someone please help me
Click to expand...
Click to collapse
Why is OEM Unlocking greyed out?
In theory, because you are already unlocked.
This happened to me flashing the stock 11 image over a DIY lineageos build (with the bootloader unlocked). The OEM unlock was in the "allow" position before flashing the stock image but, while running stock 11, I oberved it in the greyout "deny" position with text below it saying the the bootloader was unlocked.
After flashing lineageos, relocking my bootloader (this is a custom lineageos build that allows relocking), I could then toggle the allow OEM unlock back to the "allow" position.
Given that experience, you might be able to reboot into the bootloader, do `fastboot flashing lock` (which will wipe your data - be sure to back up before doing this), reboot and then toggle the OEM unlock to the "allow" position, and then unlock the device with `fastboot flashing unlock` (which will wipe data again). I doubt you will need any unlock code (if you have previously unlocked your device).
Note that I have NOT done this lock/OEM toggle/unlcok process with stock so proceed at your own risk.
Or you could just wait and see if moto does an update that "fixes" this behavior.
Edit: you don't say if your device was already unlocked before you updated to 11. If you never unlocked it, then just wait for a few days with your device connected to the carrier.
notmyrealhandle said:
This happened to me flashing the stock 11 image over a DIY lineageos build (with the bootloader unlocked). The OEM unlock was in the "allow" position before flashing the stock image but, while running stock 11, I oberved it in the greyout "deny" position with text below it saying the the bootloader was unlocked.
After flashing lineageos, relocking my bootloader (this is a custom lineageos build that allows relocking), I could then toggle the allow OEM unlock back to the "allow" position.
Given that experience, you might be able to reboot into the bootloader, do `fastboot flashing lock` (which will wipe your data - be sure to back up before doing this), reboot and then toggle the OEM unlock to the "allow" position, and then unlock the device with `fastboot flashing unlock` (which will wipe data again). I doubt you will need any unlock code (if you have previously unlocked your device).
Note that I have NOT done this lock/OEM toggle/unlcok process with stock so proceed at your own risk.
Or you could just wait and see if moto does an update that "fixes" this behavior.
Edit: you don't say if your device was already unlocked before you updated to 11. If you never unlocked it, then just wait for a few days with your device connected to the carrier.
Click to expand...
Click to collapse
i unlocked it on 10, got the retus 11 update, then locked it on 11. and now its greyed out
smartasiankid said:
i unlocked it on 10, got the retus 11 update, then locked it on 11. and now its greyed out
Click to expand...
Click to collapse
I'm not sure then.
If I was in your situation and I didn't mind wiping my data, I'd probably try booting into the bootloader and trying `fastboot flashing unlock` just to see what happens. If this command works, it will wipe your data so be sure about your backups. If it does unlock, you could try rebooting, check the OEM lock (I expect it will still be greyed out with an unlocked bootloader), and then relock and check again. Regardless if you can unlock inspite of the OEM toggle you shouldn't have much to worry about (at least until the next update).
If this doesn't work then I'd just wait a week or so. Alternatively, you could try the moto site, request your unlock key (again) and then wait a few days. It would be silly if this works, but maybe moto just needs to send a reminder to your device to enable the OEM unlocking toggle.
If none of this works, then I'd try posting to the moto official forums.
HTH
Never mind guys!! Just wait three maybe four days and it will automatically be toggle able again!! Thanks to all of those who tried to help me out!
Also a side note: to those of you who are looking to update to android 11, dont because you will not be able to change your preferred network type unlike on android 10 where you could.
smartasiankid said:
Also a side note: to those of you who are looking to update to android 11, dont because you will not be able to change your preferred network type unlike on android 10 where you could.
Click to expand...
Click to collapse
Click phone dialer
Dial. *#*#4636#*#*
A diagnostics menu will show
Choose phone information
Preferred network is in there
Default is the global setting
If your not sure what your doing, then don't change anything.
MrCamby said:
Click phone dialer
Dial. *#*#4636#*#*
A diagnostics menu will show
Choose phone information
Preferred network is in there
Default is the global setting
If your not sure what your doing, then don't change anything.
Click to expand...
Click to collapse
it is greyed out for me. i am on at&t network. it has been greyed out ever since android 11. not sure why that is happening.
To admin : please delete my post from flip3 forum.
Hi. I have SM-S908B/DS and SM-F711B On both phones same situation. There is no OEM Unlock option in the developer options. I came across this article (https://www.droidwin.com/boot-into-recovery-from-fastboot-mode/) in which nothing is written about the need for Oem Unlock. Can I install TWRP, root or custom kernel this way?