Database Info

Google Direct Phone - OEM Bootloader Greyed Out

So I picked up a backup a non-Verizon Pixel today New - it is my backup phone - I went to unlock the bootloader and the OEM Bootloader is greyed out under Developer Options. I did stick my VZW sim card in to make a phone call - it is on 7.1.1 and on the February NOF26V - I would liek to root it - is it possible or am I SOL

If it is Google phone it should unlock. You got it from a reliable source? Sometimes that slider needs an internet connection before it will work.
And grab an app from the play store called Get CID. Dig through the output and tell us what the CID is? All 1's or does it start with VZW?

cannot find that app - there was no bloatware on the phone at all - got an app called CID Getter- digging though it what am I looking for it- I do not have my SIM in this phone

bturkel said:
cannot find that app - there was no bloatware on the phone at all - got an app called CID Getter- digging though it what am I looking for it- I do not have my SIM in this phone
Click to expand...
Click to collapse
Bloat doesn't count, both are bloat free
That's a the app. About 60 percent down frim the top. The top line in the pic below ro.boot.cid
Is it all 1's or is does it start with VZW?

needs internet connection for the oem bootloader unlock option to become "ungrayed" unless its really the verizon version. Just connect it to wifi and make sure....

It is the Verizon version - how did it get all the bloatware removed?

Connect to a WiFi router make sure you have enabled security pin password or pattern. Should ungrey

Noe a VZW version on 7.1.1

bturkel said:
It is the Verizon version - how did it get all the bloatware removed?
Click to expand...
Click to collapse
Doesn't have bloatware. Doesn't matter of the phone is from google or Verizon if you activate with a Verizon sim it will download 3 Verizon apps. Other than that the only difference is the google pixel bootloader can be unlocked. If you have a CID of a Verizon pixel then you can't unlock the bootloader if its already on 7.1.1

DELETE

aholeinthewor1d said:
Doesn't have bloatware. Doesn't matter of the phone is from google or Verizon if you activate with a Verizon sim it will download 3 Verizon apps. Other than that the only difference is the google pixel bootloader can be unlocked. If you have a CID of a Verizon pixel then you can't unlock the bootloader if its already on 7.1.1
Click to expand...
Click to collapse
Not true. My CID indicates it's a Verizon version but it's unlockable without dePixel8. This is a Google Play version with a Verizon CID. I'm not alone in this.

PsiPhiDan said:
Not true. My CID indicates it's a Verizon version but it's unlockable without dePixel8. This is a Google Play version with a Verizon CID. I'm not alone in this.
Click to expand...
Click to collapse
aholeinthewor1d said:
Doesn't have bloatware. Doesn't matter of the phone is from google or Verizon if you activate with a Verizon sim it will download 3 Verizon apps. Other than that the only difference is the google pixel bootloader can be unlocked. If you have a CID of a Verizon pixel then you can't unlock the bootloader if its already on 7.1.1
Click to expand...
Click to collapse
Same here. I am on the same boat with PsiPhiDan. I got (VZW__001) Verizon pixel replacement from google customer services rep. Here is what I did, I took the sim card out when i got then phone one hand, and power on, run the update without sim card (updated to 7.1.1 NOF26V). Now I am on 7.1.1 (NOF26V) with ATT, but i am still able to unlock bootloader via OEM method. What wrong with you guy phone ???
My phone show CID = VZW__001
[ro.boot.cid]:[VZW__001]
Following steps:
Unlocked developer mod -> CHECKed OEM unlocking -> CHECKed USB debugs
THEN CMD:
adb reboot bootloader
fastboot flashing unlock
Volume Up + power button = YES
fastboot reboot
Done!

Pixel 4 XL Unlocked bootloader

I just unlocked the bootloader on my shiny new Pixel 4 XL. It is the Verizon variant as it was purchased directly from Verizon themselves. I'm unsure whether this is a coincidence, whether Google is no longer offering cell phone service providers a locked bootloader option, or did I just get lucky. The steps I took are...
1: Removed the pre-installed sim card
2: Went through the set-up process via Wi-Fi
3: Immediately turned on Developer options
4: Turned on OEM Unlock
5: Used the "fastboot flashing unlock" command via ADB/Fastboot
Normally the OEM unlock option would be greyed out as it was on my original Pixel XL that I also bought through Verizon but was able to use DePixel to unlock, then flash the Google Factory Image, the bootloader. I was then able to re-lock the bootloader for security and mobile payment reasons while retaining the "OEM unlock" option in the developer settings. I will now attempt to do the same thing when Google releases the Factory Image for the Pixel 4 XL.
It also could be because I removed the sim card before the phone had the opportunity to activate.
I am interested whether anyone else has been able to do this.
BTW: Model# G020J

Kool19 said:
I just unlocked the bootloader on my shiny new Pixel 4 XL. It is the Verizon variant as it was purchased directly from Verizon themselves. I'm unsure whether this is a coincidence, whether Google is no longer offering cell phone service providers a locked bootloader option, or did I just get lucky. The steps I took are...
1: Removed the pre-installed sim card
2: Went through the set-up process via Wi-Fi
3: Immediately turned on Developer options
4: Turned on OEM Unlock
5: Used the "fastboot flashing unlock" command via ADB/Fastboot
Normally the OEM unlock option would be greyed out as it was on my original Pixel XL that I also bought through Verizon but was able to use DePixel to unlock, then flash the Google Factory Image, the bootloader. I was then able to re-lock the bootloader for security and mobile payment reasons while retaining the "OEM unlock" option in the developer settings. I will now attempt to do the same thing when Google releases the Factory Image for the Pixel 4 XL.
It also could be because I removed the sim card before the phone had the opportunity to activate.
I am interested whether anyone else has been able to do this.
BTW: Model# G020J
Click to expand...
Click to collapse
Did this just now on my AT&T Pixel 4 XL 128GB. Nada... Screw this; I'm returning this.

Kool19 said:
I just unlocked the bootloader on my shiny new Pixel 4 XL. It is the Verizon variant as it was purchased directly from Verizon themselves. I'm unsure whether this is a coincidence, whether Google is no longer offering cell phone service providers a locked bootloader option, or did I just get lucky. The steps I took are...
1: Removed the pre-installed sim card
2: Went through the set-up process via Wi-Fi
3: Immediately turned on Developer options
4: Turned on OEM Unlock
5: Used the "fastboot flashing unlock" command via ADB/Fastboot
Normally the OEM unlock option would be greyed out as it was on my original Pixel XL that I also bought through Verizon but was able to use DePixel to unlock, then flash the Google Factory Image, the bootloader. I was then able to re-lock the bootloader for security and mobile payment reasons while retaining the "OEM unlock" option in the developer settings. I will now attempt to do the same thing when Google releases the Factory Image for the Pixel 4 XL.
It also could be because I removed the sim card before the phone had the opportunity to activate.
I am interested whether anyone else has been able to do this.
BTW: Model# G020J
Click to expand...
Click to collapse
What is DePixel?

DePixel8
Who-Lep said:
What is DePixel?
Click to expand...
Click to collapse
It was software that would unlock the bootloader of the Google Pixel and Google Pixel XL that had the bootloader locked to Verizon. The catch was it only worked on Android 7.1.0 I believe. It was patched shortly after so if you updated your device, no luck.

KillerBytes said:
Did this just now on my AT&T Pixel 4 XL 128GB. Nada... Screw this; I'm returning this.
Click to expand...
Click to collapse
Sorry to hear that. Was your model number different. I am truly interested in why I was able to do this so easily.

Kool19 said:
Sorry to hear that. Was your model number different. I am truly interested in why I was able to do this so easily.
Click to expand...
Click to collapse
Model number is G020J as well.

got mine from vzw and was able to unlock bootloader as well, removed sim before turning on, set up phone on wifi and check oem unlocking in dev settings before popping in sim card

I am hoping I am in the same boat. I couldn't pass up getting 450 for a pixel xl so I bought the verizon variant it's coming Monday. I have seen where this has worked in the past with the pixel 2. Here is hoping the toggle gets grayed out when it's sees your on verizon's network. I plan on removing sim booting up and getting to developer options taking the least path of resistance and then trying to unlock. If I am successful I will report back.

Well I'm beat my is locked

bigv5150 said:
Well I'm beat my is locked
Click to expand...
Click to collapse
I'm waiting on a 128 GB white from Verizon, but I tried it on my dad's black 64 GB. His is locked as well unfortunately.

Working root instructions for Verizon Pixel 4 XL

VERIZON PIXEL 4 XL Root Instructions
NOTE: You must do this PRIOR to activating the phone with Verizon. On my phone once I activated it the OEM bootloader unlock switch became greyed out. (Edit - after rebooting once activated the OEM lock is available again).
Steps I took:
1. Turn on the phone, do not activate the SIM with the carrier.
2. Update to the latest firmware version.
3. Reboot.
4. Enable developer settings, turn on OEM unlock
5. Boot in fastboot mode, run fastboot flash unlock in a shell, reboot.
6. Set up and activate (mine required a chat with Verizon to activate, it wouldn’t activate through the app).
7. Reboot into fastboot, flash a boot.img that has been patched (magisk_patched.img). You can find instructions on this elsewhere.
8. Reboot.
9. Install magisk manager (canary builds). It will say it needs to download a zip to fully install. Allow.
10. Reboot. You’re now rooted.
11. Magisk manager and magisk install may want to upgrade, feel free.
Enjoy!
NOTE: There are several who this has worked for, and some who haven't been able to get it to work. Suggest reading the thread and providing info on phones that do and don't unlock for whatever reason.

Any idea if this would work with the Pixel 4? Thanks
Sent from my [device_name] using XDA-Developers Legacy app

Menardo said:
Any idea if this would work with the Pixel 4? Thanks
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
I can't say for certain, but I think it would just the same. I don't know of any reason it wouldn't.

Im......just going to wait patiently for TWRP to be released for Pixel 4/XL then I will flash Magisk. Suck for now because I so use to adaway, and build.prop tether. The struggle is real.

mr.marcus said:
Im......just going to wait patiently for TWRP to be released for Pixel 4/XL then I will flash Magisk. Suck for now because I so use to adaway, and build.prop tether. The struggle is real.
Click to expand...
Click to collapse
Did they ever get TWRP working correctly on the 3xl??

mr.marcus said:
Im......just going to wait patiently for TWRP to be released for Pixel 4/XL then I will flash Magisk. Suck for now because I so use to adaway, and build.prop tether. The struggle is real.
Click to expand...
Click to collapse
TWRP isn't working on Android 10 currently. It'll need a lot of time to develop, as Google moved a lot of things related to recovery to new sections.
If you really want to root you should definitely patch the appropriate boot image (found here: https://developers.google.com/android/images) and follow the above mentioned steps.
Regarding AdAway: I'm using DNS66 since years. You can download an active the AdAway DNS serting to this app as well an AdBlock will work like a charm. No root needed.
Sent from my HTC U12+ using XDA Labs

Man I wish I saw this first. Well I hope another method comes along for those of us who activated already.

billydroid said:
Man I wish I saw this first. Well I hope another method comes along for those of us who activated already.
Click to expand...
Click to collapse
Well don't feel bad I tried it today before activating and it didn't work. It may wind up being a random occurrence with units that didn't have the IMEI's registered. That's probably why he had to contact Verizon to get the phone to work on their network.

CyberpodS2 said:
Did they ever get TWRP working correctly on the 3xl??
Click to expand...
Click to collapse
Not that I know of. I have been patching boot files for my 3 xl.

wolfu11 said:
Well don't feel bad I tried it today before activating and it didn't work. It may wind up being a random occurrence with units that didn't have the IMEI's registered. That's probably why he had to contact Verizon to get the phone to work on their network.
Click to expand...
Click to collapse
Perhaps. It knew it was a Verizon phone, it had a Verizon activation app. I was very careful to skip activation of any type at the store or when taking it home, so it might be that you need to tell Verizon that you'll activate it later to have the chance to unlock it.
Also, the OEM bootloader unlock has remained available after reboot. I think if it's unlocked in the way I describe it stays unlocked.

mr.marcus said:
Im......just going to wait patiently for TWRP to be released for Pixel 4/XL then I will flash Magisk. Suck for now because I so use to adaway, and build.prop tether. The struggle is real.
Click to expand...
Click to collapse
You might be waiting awhile.
https://www.androidpolice.com/2019/10/24/android-10-twrp-pixel-3-4/?amp

Nice!
madscribblerz said:
VERIZON PIXEL 4 XL Root Instructions
NOTE: You must do this PRIOR to activating the phone with Verizon. On my phone once I activated it the OEM bootloader unlock switch became greyed out. (Edit - after rebooting once activated the OEM lock is available again).
Steps I took:
1. Turn on the phone, do not activate the SIM with the carrier.
2. Update to the latest firmware version.
3. Reboot.
4. Enable developer settings, turn on OEM unlock
5. Boot in fastboot mode, run fastboot flash unlock in a shell, reboot.
6. Set up and activate (mine required a chat with Verizon to activate, it wouldn’t activate through the app).
7. Reboot into fastboot, flash a boot.img that has been patched (magisk_patched.img). You can find instructions on this elsewhere.
8. Reboot.
9. Install magisk manager (canary builds). It will say it needs to download a zip to fully install. Allow.
10. Reboot. You’re now rooted.
11. Magisk manager and magisk install may want to upgrade, feel free.
Enjoy!
Click to expand...
Click to collapse
I was able to do this a couple days ago. I have heard conflicting reports regarding whether this is possible or not but it certainly worked for me. I don't really have any interest in root access on pixel devices so I will just flash the Google store variant factory image (which I think is the one without the C4 in it's build number) and relock it. Maybe I'll play around with it later

Just did the patched boot image method using Magisk to root my 4XL.
Works perfectly with Magisk Canary, exactly the same process I used to do with my Pixel 3

Just an FYI - while Magisk canary builds were required when Android 10 was first released, the Magisk stable version 20 works on Android 10. So while you may use beta or canary builds if you want to, it is no longer a requirement. You can use the latest stable build and be fine.

madscribblerz said:
Perhaps. It knew it was a Verizon phone, it had a Verizon activation app. I was very careful to skip activation of any type at the store or when taking it home, so it might be that you need to tell Verizon that you'll activate it later to have the chance to unlock it.
Also, the OEM bootloader unlock has remained available after reboot. I think if it's unlocked in the way I describe it stays unlocked.
Click to expand...
Click to collapse
I brought it home sealed in the box .
Removed the sim card and powered into bootloader. From there went to recovery mode and did a factory reset. Set it up without signing into my Google account or WiFi and then went to developer options it was grayed out stating"locked carrier device". Did a factory reset as normal and set it up without signing in then took the updates from WiFi. Rebooted and checked developer options still grayed out with same message. I have yet to put a Verizon sim it but did try a different carrier but still no luck. I did have luck with this procedure with one of my Verizon 2xl so I'm pretty sure I did it right. But anyway I didn't see the app you speak of. Where is it located? I only bought this phone because of the discount Verizon gave. I'll be selling it but was curious if it could be unlocked.
Did you unlock your bootloader or just flip the toggle?

wolfu11 said:
I brought it home sealed in the box .
Removed the sim card and powered into bootloader. From there went to recovery mode and did a factory reset. Set it up without signing into my Google account or WiFi and then went to developer options it was grayed out stating"locked carrier device". Did a factory reset as normal and set it up without signing in then took the updates from WiFi. Rebooted and checked developer options still grayed out with same message. I have yet to put a Verizon sim it but did try a different carrier but still no luck. I did have luck with this procedure with one of my Verizon 2xl so I'm pretty sure I did it right. But anyway I didn't see the app you speak of. Where is it located? I only bought this phone because of the discount Verizon gave. I'll be selling it but was curious if it could be unlocked.
Did you unlock your bootloader or just flip the toggle?
Click to expand...
Click to collapse
Both. I'm rooted using a patched magisk boot image, which I couldn't have flashed otherwise.
There does seem to be some mystery sauce here though. I didn't do anything with my SIM, I left it as it was. The app was carrier setup (in notifications prompting to activate) which I didn't launch until after having turned on the toggle, and having run fastboot flashing unlock, then fastboot flash boot magisk_patched.img. I did update to the .C4 release beforehand though, but didn't think that in any way related.
Maybe it was something to do with misconfiguration on the Verizon side - but that seems pretty unlikely given that they didn't even try to activate it and said when I got home to do so - so like you, I came home with it sealed in the box.
Maybe someone else can shed some light - as it seems we're about 50/50 on the unlocks. I bought mine retail at a verizon store. I essentially got it free, as I traded in a Galaxy 5 for $450, which pays out $18.50 a month, and cancelled Fi, which covers the phone's monthly with money coming in.

Damn my device didn't unlock

I wonder if this will work with Spectrum/Charter Wireless since they use Verizon's towers....If anyone knows or has any thoughts I would appreciate it.

wolfu11 said:
I brought it home sealed in the box .
Removed the sim card and powered into bootloader. From there went to recovery mode and did a factory reset. Set it up without signing into my Google account or WiFi and then went to developer options it was grayed out stating"locked carrier device". Did a factory reset as normal and set it up without signing in then took the updates from WiFi. Rebooted and checked developer options still grayed out with same message. I have yet to put a Verizon sim it but did try a different carrier but still no luck. I did have luck with this procedure with one of my Verizon 2xl so I'm pretty sure I did it right. But anyway I didn't see the app you speak of. Where is it located? I only bought this phone because of the discount Verizon gave. I'll be selling it but was curious if it could be unlocked.
Did you unlock your bootloader or just flip the toggle?
Click to expand...
Click to collapse
Did almost the same procedure with my dad's 64 GB black XL. I didn't go into bootloader but I took out the sim, set it up without signing in, and it gave me a greyed out message to turn on WiFi before I could do anything. Tried a factory reset, got the same message. Did another factory reset, set it up without any account but signed into my Wifi network, and it gave me the greyed out message that I can't OEM unlock on carrier locked devices.
When I get my phone I'm thinking about trying a quick WiFi toggle going back to developer settings and trying to unlock before it can communicate with Verizon. I doubt it'll work, but it's worth a shot.
madscribblerz said:
Both. I'm rooted using a patched magisk boot image, which I couldn't have flashed otherwise.
There does seem to be some mystery sauce here though. I didn't do anything with my SIM, I left it as it was. The app was carrier setup (in notifications prompting to activate) which I didn't launch until after having turned on the toggle, and having run fastboot flashing unlock, then fastboot flash boot magisk_patched.img. I did update to the .C4 release beforehand though, but didn't think that in any way related.
Maybe it was something to do with misconfiguration on the Verizon side - but that seems pretty unlikely given that they didn't even try to activate it and said when I got home to do so - so like you, I came home with it sealed in the box.
Maybe someone else can shed some light - as it seems we're about 50/50 on the unlocks. I bought mine retail at a verizon store. I essentially got it free, as I traded in a Galaxy 5 for $450, which pays out $18.50 a month, and cancelled Fi, which covers the phone's monthly with money coming in.
Click to expand...
Click to collapse
I'm a bit confused by the last part, so are you on a Verizon monthly payment plan?

bosox284 said:
Did almost the same procedure with my dad's 64 GB black XL. I didn't go into bootloader but I took out the sim, set it up without signing in, and it gave me a greyed out message to turn on WiFi before I could do anything. Tried a factory reset, got the same message. Did another factory reset, set it up without any account but signed into my Wifi network, and it gave me the greyed out message that I can't OEM unlock on carrier locked devices.
When I get my phone I'm thinking about trying a quick WiFi toggle going back to developer settings and trying to unlock before it can communicate with Verizon. I doubt it'll work, but it's worth a shot.
I'm a bit confused by the last part, so are you on a Verizon monthly payment plan?
Click to expand...
Click to collapse
I am on a 24 month payment plan, but those payments are negated by the trade in and extra money I save having only verizon without Fi.

OEM unlocked pixel don't want to to detect any sim card installed.

Hi. My Pixel 3a Xl doesn't want to detect any sim card installed (tried 3 different). I tried to update it and made factory reset a couple of times. Earlier it was used in Sprint network but now it is paid off and should be unlocked. OEM unlocking in developer options is enabled: photos.app.goo.gl/SAppndY1abwSkVec8

MrCuttlefish said:
Hi. My Pixel 3a Xl doesn't want to detect any sim card installed (tried 3 different). I tried to update it and made factory reset a couple of times. Earlier it was used in Sprint network but now it is paid off and should be unlocked. OEM unlocking in developer options is enabled: photos.app.goo.gl/SAppndY1abwSkVec8
Click to expand...
Click to collapse
I figured out the problem - the reason turned out to be in the sim reader or sim tray. Today added esim from my carrier - it started up without any problems and the phone saw the network. Besides it, unlocked the bootloader - everything went smoothly.

General Pixel 6a OEM Unlocking Greyed Out STILL in August Update

Got an unlocked Pixel 6a delivered yesterday from the Google Store. Was planning to root it immediately upon setup but the "OEM Unlock" option in Dev settings is greyed out, saying "Connect to the internet or contact your carrier". I am connected to the internet, have a Visible SIM installed, and am on the most recent Android 13 update available for the 6a. I have tried all of the options, including factory resetting, going through setup without SIM or internet, etc. Google support has been of little to no help.
Pulled the build.prop using adb shell getprop and the value ro.oem_unlocking_supported does not exist.

Same here - same issue

this is super annoying, i wanted to root also! they need to fix this ASAP

Perhaps you can close this redundant thread since you cross posted to this one and it already has over 200 posts.
6a from Google: Can't unlock bootloader
Hi all, just received my 6a directly from Google and I seem to be unable to unlock the bootloader. The option "OEM unlocking" is greyed out and it says "Connect to the internet or contact your carrier.". I connected it to the internet via Wifi...
forum.xda-developers.com

Odd, when I got June update it became available. But I haven't received any update since, just waiting for ota. I think I'll wait rather than sideload, maybe it will stick.

tcat007 said:
Odd, when I got June update it became available. But I haven't received any update since, just waiting for ota. I think I'll wait rather than sideload, maybe it will stick.
Click to expand...
Click to collapse
Not for me. Just loaded stable 13 via beta; checked the unlock switch; still gray. So, I did the reset (but not the sim-removal-turn off wifi, etc) and still no bootloader unlock. What I haven't done is try the fastboot unlock anyway. It seems it would simply not work. However, trying to sideload the June OTA put my phone into a bootloop (which would have been so easy to fix with an unlocker BL) so not really going to mess around much.

Have you tried factory resetting after updating? That's what worked for me.

Yeah, I have, several times, but unfortunately to no avail.

I did the factory reset from the setting app and that did the trick. I had 13 plus the update before I did this.

mmead1143 said:
I did the factory reset from the setting app and that did the trick. I had 13 plus the update before I did this.
Click to expand...
Click to collapse
Yeah, for whatever reason that hasn't been working for me.

Just a guess, maybe go to settings/about phone/regulatory labels, and check your model number. Make sure they didn't mistakenly send you a locked to carrier phone.

Do you know of a list like that? That would be so helpful to so many.

I did the sign up for beta, get ota 13, sign out of beta, thing. Got 13 instantly (although takes 45 minutes to install), and unlock bootloader is still available.

bobby janow said:
Do you know of a list like that? That would be so helpful to so many.
Click to expand...
Click to collapse
What list are you talking about?

roirraW edor ehT said:
What list are you talking about?
Click to expand...
Click to collapse
A list of model numbers and which is Verizon, unlocked, ATT, Google unlocked etc. Things like that so if someone can't unlock the bl they can check their version/model. For instance I bought a BB unlocked and the model is:
GA03715-US
and in Regulatory Labels is shows GX7AS So I'm pretty much at a loss as to which devices are which if it even matters. I just see so many people that still can't unlock the bl even after updates and factory reset that maybe there is a pattern or versions that will not allow it.

@bobby janow You forgot to type a response when you quoted me. It just seemed like when you said something about a list that maybe you had posted that in the wrong thread, since I didn't notice anything else in the thread that made sense for that response.
Edit: Oh, you edited it now. Nevermind. I understand now.
list of pixel 6a models - Google Search
Although the first search result only lists:
Google Pixel 6a model numbers​The four model numbers are as follows:
A4RGB62Z
A4RG1AZG
A4RGX7AS
A4RGB17L
Click to expand...
Click to collapse
GSMArena only lists three:
ModelsGX7AS, GB62Z, G1AZG
Click to expand...
Click to collapse

tcat007 said:
I did the sign up for beta, get ota 13, sign out of beta, thing. Got 13 instantly (although takes 45 minutes to install), and unlock bootloader is still available.
Click to expand...
Click to collapse
Just received 6a today, straight outta the box set it up no sim installed checked version, it was 12 , OEM unlock greyed out, did a factory reset , no help, still greyed out, took the ota update , it's was just a newer version of 12, oem still greyed out, factory reset this version and it worked, oem unlock granted

HEY THIS MIGHT WORK FOR U!​
Was having the same issue, nothing seemed to be working.
I had success finally, though!
Be sure you realize your phone will be wiped, etc.
Airplane Mode & No SIM inserted.
Remove All Accounts From Phone (to prevent issues with locks, etc)
Make sure you can put the phone in fastboot & adb modes
I put the phone in various modes to test, and ended up doing this:
[ REBOOT PHONE INTO SIDELOAD MODE VIA: ]
Code:
$ adb reboot sideload
Once the phone is ready to accept the side load OTA package, push that happy bullsh1t right on down the USB cable to the phone via:
Code:
adb sideload ~/MagicalGarbageDump/bluejay-ota-sd2a.220601.003-ddfde1f7.zip
From the OTA file downloaded directly from Google at THIS SITE. It's this one:
12.1.0 (SD2A.220601.003, Jun 2022)Linkddfde1f7edcdbb2b3de41d24f6c3f31587f836f387cab4cc6d16adee32bcab8a
After downloading and flashing that OTA, I had to "reset to factory settings" about two more times, seemingly randomly, and then it worked!
I made sure to have:
- NO SIM CARD IN THE PHONE.
- NO WIRELESS NETWORKS CONNECTED.
I am kind of annoyed it seemingly randomly decided to work, but also grateful that it finally unfzcked itself.

Also no luck over here. I bought my Pixel 6a directly from Google store as a "non locked device". It was sent from France Google store to Spain.
I'm in the 5th September security update under Android 13.
Tried all the tricks posted before: factory reset from settings and from recovery, sideload OTA, tried with sim and without it... No luck, OEM unlock still greyed out.
I wrote to Google about it. They asked me for the imei. After all, no help received from them to solve it.
Still waiting for "magically" disappear the greyed option...

l would send it back and get the p6 pro. For a few dollars more you get a better phone and no unlock issues.