After you had tried all the steps but the "OEM Unlocking" option still greyed out, turn the "Use developer options" off and then the "OEM Unlocking" will be enabled which you just need to slide to turn it on.
Question 6a from Google: Can't unlock bootloader
- Thread starter Mustkeg
- Start date
Hey I didn't have a sim inserted into the phone. If you have any specific questions please let me know.
Thanks for the suggestion. Didn't work for me. I had to try a reset for other issues so I just did 5 (because 1-4 didn't enable OEM unlocking--neither did #5) factory resets without my AT&T prepaid sim. First two were from within system, last 3 were from recovery. I have just reported the fails in another thread on similar topic.
It was worth the try. NO go. I'm on Oct update. Thanks for yet another suggestion.
Thank you very much. In your 11 step instructions, between which steps should I connect to wi-fi and at which point do you enable developer options?
After receiving the Dec update with OEM unlocking still greyed out, I contacted Google. Note, every "OEM greyed out" thread on Google forums has been closed to further comments. This is part of the chat regarding the issue. While I still swear Google is doing absolutely nothing about it (I hope I am wrong), they are claiming to be "working on it." I will contact them each month after an update if necessary. Earlier, on one of the threads re OEM unlocking, I'd posted that I hadn't checked my son's phone (we ordered at the exact same time under the exactly same conditions shipped from the same location). I checked last week. His OEM unlocking is NOT grey out.
This (hack) is a new one for me. I got the checkin succeeded, but OEM unlock is still grayed out. I will look into it. My 6a was ordered as unlocked not carrier connected.
I've tried the resets with/without sim/internet (at least a dozen) but not until I'd updated to 13.
Getprop gives me
I've been ordering unlocked phones (and a few tablets) from Google since the Galaxy nexus (only Samsung phone I've ever had). This is the only one I've ever received with this issue.
I had the same issue with my wife's Pixel 3. Google support was responsive as long as i was very clear on my error (OEM Unlocking greyed out, no BL unlock possible). It took a RMA via a chat session but the issue was resolved (after ~10 days of waiting and returning the original P3). Some phones just get released as bad units.
The same issue also cropped up with her 6a. I factory reset that unit and upgraded from sd2a.220601.003.b1 (A12, from factory) to tp1a.221105.002 (A13, factory image upgrade via adb). That cleared her error and i went through the "usual" BL-unlock & root process. No SIM, no internet, skip through all the setup steps, etc. Hopefully the support team can help you out or at least get you a new unit!
Just posted here (https://xdaforums.com/t/pixel-6a-oe...-still-in-august-update.4480839/post-87891013) that I received a new phone which, after doing a factory reset and toggling Developer Options switch, did open up the OEM unlock toggle.
Bought a new pixel 6a, was on september patch, updated it to december patch . Now when i wanted to attempt root, oem option is greyed out. Any help?
New from Google? Is it a carrier variant or unlocked? Did you check the OEM Unlocking toggle before updating?
I am not sure if it is from google, bought it from hong kong reseller and they claim it is japan set.
I dont think it is carrier locked as I have tested with 2 sim card from different telco and both works.
I did not check the oem unlocking toggle before updating.
The only way I can think of to check whether it's a locked variant is via the model number, but I'm only familiar with US devices.
The only thing you can really do is connect to the Internet and see if OEM Unlocking becomes available after a bit of time.
The only thing you can really do is connect to the Internet and see if OEM Unlocking becomes available after a bit of time.
Thanks, I've also saw somewhere saying it will automatically allow us to unlock oem after using the phone for few days/ a week.
Guess that's what I'll do. Else, will have to just live with no root for this phone.
Once it's connected to the Internet, it should check the servers within a short time to see if the IMEI is whitelisted, and if so, will set
sys.oem_unlock_allowed to 1, making the OEM Unlock toggle available.
I had the same issue on pixel 4a.. untill I removed a screen lock... remove finger print, lock pattern and try again
Last edited:
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
7
In some cases, the device just needs to be connected to the Internet for a while for OEM Unlocking to become available.
It is true that they can remedy this with a software update.
If OEM Unlocking is unavailable, this means that thero.oem_unlock_supportedproperty is set to 0.
Ifro.oem_unlock_supported=1then OEM Unlocking will be available in Developer Options. This toggles theget_unlock_abilityproperty to 1, which informs the bootloader that unlocking is allowed.
I would request an RMA if this issue does not resolve itself. You paid for an unlocked device from Google; they should have sent you an unlocked device. When I ordered my Pixel 5, I unlocked it straight out of the box without even connecting to WiFi.5Can confirm bootloader unlock is working If you have a verizon sim installed in the device. I ordered the pixel 6a from Google directly, installed a non activated verizon sim and checked system updates. Security update was available and installed, did a factory reset and bootloader unlock option no longer greyed out.5
Some properties are hidden/restricted from user.
From my P6.
Code:[ip@lost ip]$ adb shell getprop | grep 'unlock' [sys.oem_unlock_allowed]: [1]
Running the command as root.
Code:[ip@lost ip]$ adb shell su -c getprop | grep 'unlock' [ro.oem_unlock_supported]: [1] [sys.oem_unlock_allowed]: [1] [ip@lost ip]$
Looks likesys.oem_unlock_allowedis still a user level prop.
This value is set from the toggle in developer settings.Not too useful if the toggle is greyed out.
0 - Not enabled
1 - Enabled
Cheers.
PS.
I quickly skimmed this thread a bit.
Glad my device budget was too light to buy a P6a.
If I remember correctly..
My P6 had to be connected to WiFi to allow OEM unlocking under developer options.
No sim card was installed.3I am yet another who received a pixel 6a yesterday. Bootloader in dev options is greyed out at well.
The reason for this post today is just to let you know to keep a eye on your return dates if you can't live without the bootloader unlocked.
I spent over a hour and a half on the phone with both google fi and google this morning. Google was not able to do anything. I was sent back to google fi and we both agreed the carrier would be responsible to unlock the phone.
Well once again when I spoke with the google fi rep I was informed of two things. First she tried to tell me cause I elected to use the upgrade plan it couldn't be unlocked for two years. I then informed her this is incorrect as first I already have a 5a on a upgrade plan and that has been unlocked from day one. Also I informed her I have 7 Pixel phones and everyone of them is bootloader unlockable and in fact are unlocked.
I got two responses from this rep, she informed me that they do not consider the unlocking of the bootloader either a hardware or software issue, and then she said she didn't want to argue with me. lol
She had me so heated that I asked for a return label to send the phone back. Didn't matter, she didn't care.
So anyway for me I'm ready to return my 6a if nothing happens by monday.
Again keep a eye on your return dates cause I have no idea what is going on with this.
P.S.: I could be wrong however I have a feeling they sent out a bunch of verizon carrier phones.3
I was able to unlock mine. I bought the unlocked version on the Google store and Verizon is my carrier. It was greyed out at first too. After a few hours I had security update available. Around 40mb and the June patch I think. Reboot to finish the update and still greyed out. Then I decided to factory reset because I remember that happening on the Pixel 2 I think. Reboot and I was able to toggle it. I got Magisk and AOSP mods running now.
