yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6a] V0latyle:
This is a known issue with Google devices ever since the Nexus - Google branded devices purchased without a carrier plan are usually bootloader unlockable, while carrier branded devices, whether purchased from Google or from the carrier, are not. There is no known vulnerability that allows circumventing the bootloader lock.

Interesting, I hadn't heard of that. I have heard of some TMobile users being able to request a bootloader unlock through their carrier once the device is paid off.

The problem with the IMEI database theory is that it could be safely assumed that every device would not be unlockable until it was able to connect to the Internet. Most of us with unbranded devices have been able to unlock them right out of the box without even setting up WiFi.
[Google Pixel 6a] hochoch:
Just received mine, went into developer options (after connecting to wifi) and it's greyed out for me as well. no system update available so i went to check the factory images and there are only 2 for the 6a, one for japan and another for verizon. mine is a non-verizon model, but i plan to use it on their service, none for the generic device. i have not inserted my sim card yet.

I then tried updating all apps, play services, etc. and then restarted. still grayed out. factory reset, still grayed out.

very frustrating....dying to get rid of my 4a5g which overheats constantly....
[Google Pixel 6a] Mustkeg:
The first factory images are dated 220601.

My 6a runs a "220123" build.

Let's hope the international 6a factory builds are also newer and include the fix.
[Google Pixel 6a] hochoch:
Looks like we'll have to wait until after the weekend...finger's crossed: https://9to5google.com/2022/07/28/pixel-6a-factory-images/

"Google told us that the August security patch is coming in a matter of days (i.e., Monday) and will be the first update."
[Google Pixel 6a] bobby janow:
I won't swear to it but my P6 was not unlockable until I connected to the internet via wifi or carrier. I"d be curious to see what others have experienced to either confirm or deny what I remember. But in the other instance a year or so ago it seemed to some of us that they had to update their IMEI database, factory reset and then it was registered to allow unlock. No one was entirely sure though but they fixed all of them with one back end update. What else could it have been? As you stated the devices and images are identical. That's why I don't think the August update will do anything at this point. They will have to do something similar, whatever that was, since there was no software update for those affected just a factory reset.
[Google Pixel 6a] hochoch:
As a last ditch effort, I popped in my sim card (verizon) and it triggered an update to the June security patch (40mb update that took forever). I was hopeful that this would fix things, but it still greyed out. :(

new build # is SD2A.220601.004
[Google Pixel 6a] greatgoogly:
Just received my "unlocked" Pixel 6a direct from Google and indeed the entry in Developer Options to unlock the bootloader is greyed out.
[Google Pixel 6a] stormcrank:
Just adding to the list that I also received an "unlocked," carrier agnostic, 6a from Google with the bootloader unlock grayed out.
[Google Pixel 6a] z0mghii:
Tried everything, side loading the verizon update throws some Footer error.
[Google Pixel 6a] FWC9696:
So, you are stuck on April software, or do you have another one that's on June software that can't unlock?
[Google Pixel 6a] z0mghii:
I'm on the june software `sd2a.220601.003`
[Google Pixel 6a] ctfrommn:
Have you tried signing up for and flashing the Beta?
[Google Pixel 6a] z0mghii:
Just flashed the beta, still greyed. On TPB4.220624.008.A2
[Google Pixel 6a] ctfrommn:
Factory reset on it yet?
[Google Pixel 6a] z0mghii:
Yup, still the same. Thanks for the help. Looks like it's going back in the box
[Google Pixel 6a] ritchea:
Thanks. I was just wondering about that.
[Google Pixel 6a] dbjungle:
Same thing here. I ordered every Pixel a phone and this is the first time I'm not able to select it. The one thing I did differently was I put my SIM in while doing the initial setup. Something I pretty much never do with new phones. I'll try to factory reset and see if that clears it up, but I needed to charge the battery up a bit. I pre-ordered the unlocked 6a version from Amazon DE in Europe.
[Google Pixel 6a] dbjungle:
Oh wow, I got this one last night in Europe and OEM unlocking is still grayed out.

EDIT: A factory reset resolved this for me on SD2A.220601.003. It's annoying, but it's good to have OEM unlocking enabled.
[Google Pixel 6a] dbjungle:
Some people, myself included, just enable OEM unlocking in case there is some botched update that causes a boot loop or something. Then you can go to fastboot, unlock the bootloader and flash some image to make your phone usable again. Otherwise you would be SOL with a bootloop.
[Google Pixel 6a] ctfrommn:
Correct, but OEM unlock is grayed out till you factory reset on this device, at least for now.
[Google Pixel 6a] ctfrommn:
Anyone with an unlocked device get prompted for an update today? The only one I see @ https://developers.google.com/android/images#bluejay is for T-Mobile. I am using a T-Mobile MVNO but this is an unlocked phone. Seems odd that that would be pushed to me.
[Google Pixel 6a] trita629:
Yes I got it too after I opted out of beta. Was hoping it would fix my oem unlock problem but it still isn't happening.
[Google Pixel 6a] ctfrommn:
I took the update and whatever it was was tiny and did nothing I could see, but also didnt affect anything either.
[Google Pixel 6a] FWC9696:
Well, did the "specialist" give him all the details?
[Google Pixel 6a] stormcrank:
Nope. I contacted support again after the 48 hour window had passed and was told that they are "looking into the issue" and they "may be in touch."
[Google Pixel 6a] FWC9696:
I contacted support and they said it will be addressed in a future update. When I asked if that would be the August update, they said "hopefully, maybe".

I do not trust them to actually fix this.
[Google Pixel 6a] stormcrank:
Your response was more useful than mine at least. I would have been happy with a "let's get you a replacement device out." I guess I'm just going to initiate a return today and maybe look for another device entirely. I'm not bothering with this we may fix it at a later date business.
[Google Pixel 6a] FWC9696:
If it weren't for the $300 trade in on a Pixel 3a, I'd have sent it back already. Just debating what to do. Maybe just keep the 3a for longer.
[Google Pixel 6a] ritchea:
FWIW, my phone came directly from Google, unlocked as they always have been. I use AT&T prepaid. The OTA pushed to my phone is the AT&T one: SD2A.220601.002. Also, I noticed the "Global" version (12.1.0 (SD2A.220601.003, Jun 2022) is no longer labeled as such. My last phone was Pixel 3a. Things were still fairly simple for it when it came. Oh, and the bootloaders were able to be unlocked from the get-go!
[Google Pixel 6a] bricky23:
Mine was greyed out. I opted in to android 13 beta. Used that for about a week. Then I opted out and checked for an update. Went back to android 12. In the process it wiped the phone. After setting up the phone, I looked, and it was not greyed out anymore. Had an esim and wifi on. It was an unlocked phone from Amazon.
[Google Pixel 6a] ctfrommn:
Very similar to what happened to me.
[Google Pixel 6a] epapsiou:
***FIXED***

Similar issue. Unlocked from google with trad ein.

Grayed out etc.

Then there was an update yday and it fixed it.

Now i can unlock bootloader.

SD2A.220601.002.B1

It is the B1 in the end that I think you need
[Google Pixel 6a] mbonus:
This worked for me
[Google Pixel 6a] stalker00:
Today I got an update (SD2A.220601.003.B1)

And now the OEM option is enabled.
[Google Pixel 6a] buffal0b1ll:
I sideloaded SD2A.220601.003.B1 OTA zip n recovery and now OEM unlocking isn't greyed out anymore. No factory reset needed.
[Google Pixel 6a] stormcrank:
Did you have to do a reset or anything? Mine just OTA'd me the 002.B1 update. I installed it and restarted, but it's still grayed out.
[Google Pixel 6a] natheux:
You may have to factory reset. I had to do it after the update came out.
[Google Pixel 6a] stormcrank:
Factory reset just now. Still gray. I think I'm on about my 40th factory reset since I received this thing trying to get OEM Unlock to work. This device is such a disappointment to me.
[Google Pixel 6a] natheux:
Might be a problem with your rom. Mine is 003.B1. You might have to try to update to 003.B1 using recovery factory image from Google's Pixel website
[Google Pixel 6a] stormcrank:
I'll try it. I'd tried to 002, 003, and 13 betas before the B1's came out. I'm not sure why it gave me the T-Mobile OTA. I don't have T-Mobile.
[Google Pixel 6a] ctfrommn:
B1 seems to fix this for a lot of people.
[Google Pixel 6a] bobby janow:
What's your return window? Also, where did you buy it?
[Google Pixel 6a] epapsiou:
no just became available after update.

I have not done a single reset since i got the phone.

Just waited and with that .B1 update I was fine
[Google Pixel 6a] FWC9696:
For the record, I returned mine already. I got so tired of this stuff.
[Google Pixel 6a] stormcrank:
I was kinda hoping you'd chime in with where you were at with it. I probably should've returned mine, but they're giving me $300 for a $150 phone. If the next round of updates doesn't fix it I'll probably just sell this and move on.
[Google Pixel 6a] FWC9696:
I was thinking I might still send the trade in for credit since it's a secondary phone, but then I would have to buy another 6a. It seems like too much trouble.
[Google Pixel 6a] TenPercentPower:
A little late, but I ran adb shell getprop ro.oem_unlock_supported and the command returns nothing. Ran adb shell getprop and that line does not exist. What does that mean?
[Google Pixel 6a] V0latyle:
I don't know enough about these commands to be of help. Perhaps one of our respected and knowledgeable contributors like @ipdev or @pndwal might have some insight?

I assume you have USB debugging enabled...
[Google Pixel 6a] TenPercentPower:
Yes. USB debugging is enabled.
[Google Pixel 6a] ipdev:
Some properties are hidden/restricted from user.

From my P6.

[ip@lost ip]$ adb shell getprop | grep 'unlock'
[sys.oem_unlock_allowed]: [1]

Running the command as root.

[ip@lost ip]$ adb shell su -c getprop | grep 'unlock'
[ro.oem_unlock_supported]: [1]
[sys.oem_unlock_allowed]: [1]
[ip@lost ip]$

Looks like sys.oem_unlock_allowed is still a user level prop.

This value is set from the toggle in developer settings.

0 - Not enabled

1 - Enabled​

Not too useful if the toggle is greyed out. 🙃

Cheers. :cowboy:

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.
[Google Pixel 6a] TenPercentPower:
Yeah I figured some lines would be hidden without root. Unfortunately my 6a is connected to internet and the option is still grey 😐
[Google Pixel 6a] bargainbums:
SHOUT OUT TO POST 160:

https://xdaforums.com/t/6a-from-google-cant-unlock-bootloader.4473669/post-87232385

Weighing in my experience with this stupid issue that really shouldn't have happened in the first place:

**NO SIM WAS EVER PLACED INTO THE DEVICE**

Opened box, turned on phone, connected to internet. DID NOT ADD GOOGLE ACCOUNT.

Enabled dev mode, OEM is locked.

Immediately updated system to June 2022 update - BUILD NUMBER: SD2A.220601.003.B1

Restarted. OEM unlock still grayed out.

Factory reset.

Did not connect to Wifi this time around during the set up.

After everything was "set up" , added Wifi and while that was running, immediately enabled dev mode, and OEM unlock was available.

Good luck to anyone else seeing issues.
[Google Pixel 6a] subbaak1968:
I bought pixel 6a and an Indian Pixel 6a bootloader can be unlocked.
[Google Pixel 6a] FWC9696:
Deleted
[Google Pixel 6a] TenPercentPower:
Anybody find any solutions? It's now August and I'm on Android 13, TP1A220624.021.A1 with no luck.
[Google Pixel 6a] ytsejam1138:
Same Android 13. Bought from the Google Store, selected Google Fi, shipped with a Google Fi SIM already installed and my OEM Unlock is still greyed out. Really don't want to factory reset, but that seems to be the only solution for now and even that's not a guarantee.
[Google Pixel 6a] TenPercentPower:
Yeah, factory resetting didn't do the trick for me. Glad to know I'm not the only one still having this issue
[Google Pixel 6a] bobby janow:
Perhaps a poll is in order just to determine what is really happening. @ytsejam1138 since you bought it from Google Fi then you will absolutely need to reset the device to get the OEM switch active. @TenPercentPower where did you buy it from? Even if you bought it from Google store and chose the Verizon version or perhaps some other carrier branded you will not be able to unlock the bl. If you can return it then I suggest you do so. If it's too late then either resell it or live with it. Sorry to say.
[Google Pixel 6a] TenPercentPower:
I bought it from the Google store as the unlocked version. I'm currently running a Visible eSIM and have put in an AT&T SIM and they have both worked .
[Google Pixel 6a] bobby janow:
Then you need to contact Google and get a return authorization. There is an obvious defect in your device. I wouldn't take a refurb either but that might be all you get if you are outside the return window.
[Google Pixel 6a] trita629:
Got this email today:

'The ability to access the OEM unlock settings in the bootloader was restored in the most recent software update for 6a. I request you to please wait for 1 week as it will take about a week before the OEM unlock is enabled. It is working as intended.

If you want an option immediately , you can do Factory data reset on your device in order to see the change in the bootloader. '
[Google Pixel 6a] mike.s:
Got a 6a for myself 2 weeks ago. Got one for my wife today. In both cases, the Allow Unlock toggle was grayed out as received. In both cases, I ended up being able to toggle it for unlock. Steps:

1) No SIM until after you can toggle (not sure this matters, just what I did)

2) Go through most basic setup you can - allow wifi only, no account, no transfer from old phone. Don't install recommended apps (probably not important, but saves time). Let it complete until you get to home screen.

3) Check for system updates, and "update now". Wait until it completes, and "reboot now". This took both phones from the initial 12.1(?) release to the last 12.1 release.

4) After it reboots to new firmware, factory reset.

5) Same as #2

6) Enable Developer Options

7) Toggle is available. Enable it.

8) If you're going to actually unlock the bootloader, enable adb, adb reboot bootloader, and unlock it. Boot.

9) Factory reset to start setup from scratch.

10) Done. Do a complete setup as you wish, insert SIM, copy from old phone, etc. You should be able to check for updates and install 13 now.

YMMV.
[Google Pixel 6a] rc420head:
Same here, bought 6a unlocked though the Google store (via google financing ) and oem unlock was grayed out. updated to android 13 via system update still grayed out. decided to do a full factory reset and now i can unlock. Thanks to all who suggested the factory reset. fyi i'm on T-Mobile and had my sim in.
[Google Pixel 6a] lukegvoigt:
I got mine today - unlocked variant directly from Google. It came with Android 12. Upgraded to Android 13. OEM lock was greyed out. So I reset the phone, and when I set it back up, the option is now available.
[Google Pixel 6a] ctfrommn:
You have to do a factory reset to get it to show up.
[Google Pixel 6a] tibl37:
Hi! I've managed to switch «OEM Unlocking» (with updating to Android 13 and then factory reset; it's definitely not carrier-locked), however, it doesn't work :(

❯ ANDROID_PRODUCT_OUT=./ fastboot flashall
--------------------------------------------
Bootloader Version...: bluejay-1.2-8893284
Baseband Version.....: <removed>
Serial Number........: <removed>
--------------------------------------------
Checking 'product' OKAY [ 0.000s]
Setting current slot to 'a' FAILED (remote: 'set_active command is not allowed on locked devices')

Any ideas on how to fix it?
[Google Pixel 6a] ctfrommn:
What doesnt work? Clicking the toggle is only step one, you still have to unlock the bootloader. The toggle just allows you to.

fastboot flashing unlock
[Google Pixel 6a] tibl37:
My bad, forgot about this step, but:

> fastboot flashing unlock
FAILED (remote: 'Unrecognized command flashing unlock')
fastboot: error: Command failed
[Google Pixel 6a] ctfrommn:
So my next best guess is youre on an old adb/fastboot. Is this Windows or Linux?
[Google Pixel 6a] tibl37:
❯ fastboot --version
fastboot version 33.0.3-8952118

I'm on macOS (12.5.1, Apple Silicon).

// It works fine with Pixel 3
[Google Pixel 6a] ctfrommn:
Boot back up and recheck that the OEM unlock toggle is actually set.
[Google Pixel 6a] tibl37:
Already checked, it's on

Also checked on Linux:

$ sudo $(which fastboot) oem unlock
FAILED (remote: 'Unknown OEM command')
fastboot: error: Command failed

$ sudo $(which fastboot) flashing unlock
FAILED (remote: 'Unrecognized command flashing unlock')
fastboot: error: Command failed
[Google Pixel 6a] ctfrommn:
No idea then....someone smarter than me will need to answer
[Google Pixel 6a] dcarvil:
What is the output of "sudo $(which fastboot) --version"?
[Google Pixel 6a] tibl37:
$ fastboot --version
fastboot version 33.0.2-8557947
[Google Pixel 6a] dcarvil:
That is different than you posted earlier.

fastboot --version

fastboot version 33.0.3-8952118

You have multiple versions of fastboot installed, so the first thing to do would be to remove all except the latest version. Also, you should not need sudo to run fastboot. If it will not run without sudo, you should setup a udev rule so sudo is not necessary. That is not the cause of your problem, though.
[Google Pixel 6a] tibl37:
They are different because these are different computers — first one is Mac, second one is PC with Linux :)
[Google Pixel 6a] mike.s:
Is the phone in the bootloader (not in fastboot or fastbootd) when you're trying this?

adb reboot bootloader
(wait)
fastboot flashing unlock
[Google Pixel 6a] TenPercentPower:
Just did. New one should be in tomorrow. Sending in the broken one soon :)
[Google Pixel 6a] PeterImmel:
Today suddenly my bootloader is unlockable...

I did nothing...no factory reset, etc.

A13/Germany/Bought from Google.

Question: Unlocking wipes all my data, right?
[Google Pixel 6a] mike.s:
Flipping the allow unlocking switch in developer options doesn't. Actually unlocking the bootloader does.

Flipping the switch is considered a good thing to do, because it may allow you to recover from some future issue which would otherwise "brick" your phone, despite the need to wipe at that time.
[Google Pixel 6a] Lughnasadh:
Yes, it wipes your data.
[Google Pixel 6a] ctfrommn:
It should, yes. Ironically mine didnt, which was very odd.
[Google Pixel 6a] bobby janow:
I've seen reports, like yours, of that. So you flipped the OEM switch, went into fastboot and oem unlocked, rebooted and you were unlocked? Wow, what a security flaw.
[Google Pixel 6a] ctfrommn:
Yep, and indeed. I intended to see if I could reproduce it, but never tried again.
[Google Pixel 6a] bobby janow:
Yeah quit while you're ahead.
[Google Pixel 6a] ctfrommn:
LMAO....you dont know me very well
[Google Pixel 6a] bobby janow:
Haha well then you should really go for it. If you can unlock without a wipe then report it or sell the phone for a grand. At least!
[Google Pixel 6a] mike.s:
Did you unlock while using the older (pre-13) bootloader? Perhaps that's related to the security issue Google addressed.
[Google Pixel 6a] ctfrommn:
Yeah, and you could 100% be correct.
[Google Pixel 6a] zubair1836:
Had same problem with mine, Solved this way:

1.Connected to Wi-Fi

2.Inserted SIM Card

3.Updated the security patch (~ 51.70 MB)

Waited for a day and it wasn't greyed out anymore.
[Google Pixel 6a] gazhay:
I had this problem, Google went as far as to replace my original handset with another that also had the issue.

They asked for the IEMI and after the last security update the option is available....
[Google Pixel 6a] varoyzf:
Did you factory reset or it just was available after the security update?
[Google Pixel 6a] Bypassme:
try to connect it to your pc via adb debugging and force it to reboot to bootloader or recovery type adb reboot bootloader or adb reboot recovery
[Google Pixel 6a] gazhay:
I tried all the factory resets and different methods of connecting to wifi / sim card, etc on the 2nd handset they gave me - never changed the OEM status.

Gave them the IEMI of my original handset which was still locked, after the latest security update and reboot OEM unlocking was able to be toggled from dev menu.

Suggests to me they can push out OEM unlocking and it either requires an update and/or reboot for handset to pick it up.
[Google Pixel 6a] arfarfdan:
Hi this is a cross-post potentially, but this is what worked for me:

https://xdaforums.com/t/pixel-6a-oe...still-in-august-update.4480839/#post-87455909
[Google Pixel 6a] argonauts12:
This worked for me - the exception being that i updated the phone to the september android 13 release.

Thanks!
[Google Pixel 6a] Syntaxerror_s:
Does it have to do with OEM citadel ?
[Google Pixel 6a] V0latyle:
What do you mean?
[Google Pixel 6a] andybones:
A mystery indeed.

(Heck I remember testing root for the HTC Rezound using a paperclip to unlock the device!)

To me it reminds me of unlocking HTC devices through the htcdev website.

you get an "unlock token" off the device, flash it in fastboot, and are presented with the screen for options to unlock the bootloader.

(Google did buy half of HTC)

HTC 10 was my last HTC device, and was my last carrier (Verizon) device.

This was the first phone that started realizing was being made (or they always were?) basically identical.

Thus a Verizon HTC (once set to S-OFF (Security Off)) could then flash the Developer firmware and be fully converted.

Once unlocked it was the same as an "unlocked" HTC 10 from Google.
[Google Pixel 6a] thebitjuggler:
Okay you will need to reset your phone to factory settings.

Go to Settings > Password & accounts

Remove Accounts for Owner.

Go to Settings > System > Reset options

Erase all data (factory reset)

Check Erase downloaded SIMs, then press Erase all data.

Erase all data.

Don't do any initial setup. Don't add any accounts, don't connect to WiFi (Connect to it afterwards)

Go to Settings > System > Date & time.

Toggle Set time automatically so that it is off.

Set the Date to a date in 2018.

OEM unlocking should now not be greyed out anymore and you can set it.
[Google Pixel 6a] k4tfish:
Doesnt work here. Date will be changed back to 1. Sept. 2022 right after reboot, even with disabled networks (to prevent ntp etc)
[Google Pixel 6a] thebitjuggler:
Updated my steps above. That should now work. Please backup any data you have beforehand.
[Google Pixel 6a] sabresfan:
Awesome just worked. Thank You Thank You Thank You
[Google Pixel 6a] mixedupfiles:
I've followed this thread since August, following every suggestion in hopes of finding a solution which would un-gray OEM Unlocking on my unlocked 6a. To date, I have tried every single recommendation I've encountered but none of the have worked. I really got my hopes up with the steps above, but, alas, my phone still has OEM unlocking grayed out.

Can you expand on this slightly? Should the SIM card be inserted at some point and if so, when? At what point should I activate developer options? When should I join a wi-fi network? Are there any restarts other than the one that takes place after the factory reset?

Thanks in advance.
[Google Pixel 6a] mixedupfiles:
How did you contact Google to give them the IEMI? Is there a number to call or an email address to use?