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

Search This thread
Jun 25, 2019
11
4
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.
 
  • Wow
Reactions: roirraW "edor" ehT

bobby janow

Senior Member
Jun 15, 2010
6,461
2,431
Perhaps you can close this redundant thread since you cross posted to this one and it already has over 200 posts.

 

tcat007

Senior Member
Jul 3, 2011
5,442
2,014
Austin, TX
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.
 

ritchea

Senior Member
Sep 6, 2011
833
177
okeechobee
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.
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.
 

benji

Senior Member
Jan 13, 2009
73
27
Have you tried factory resetting after updating? That's what worked for me.
 

mmead1143

Senior Member
Dec 27, 2010
119
35
I did the factory reset from the setting app and that did the trick. I had 13 plus the update before I did this.
 

tcat007

Senior Member
Jul 3, 2011
5,442
2,014
Austin, TX
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.
 
  • Like
Reactions: Lughnasadh

bobby janow

Senior Member
Jun 15, 2010
6,461
2,431
What list are you talking about?
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.
 
Last edited:

roirraW "edor" ehT

Forum Moderator
Staff member
@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.


Although the first search result only lists:

Google Pixel 6a model numbers​

The four model numbers are as follows:
  • A4RGB62Z
  • A4RG1AZG
  • A4RGX7AS
  • A4RGB17L

GSMArena only lists three:
ModelsGX7AS, GB62Z, G1AZG
 
Last edited:

hammered58

Senior Member
Nov 4, 2017
483
132
Wisconsin
Google Pixel 6a
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.
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
 

arfarfdan

Member
Feb 24, 2020
7
6
HTC Rezound
Nexus 6

HEY THIS MIGHT WORK FOR U!


Was having the same issue, nothing seemed to be working.
I had success finally, though!
  1. Be sure you realize your phone will be wiped, etc.
  2. Airplane Mode & No SIM inserted.
  3. Remove All Accounts From Phone (to prevent issues with locks, etc)
  4. 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.
 

Attachments

  • Screen Shot 2022-09-19 at 6.45.22 PM.png
    Screen Shot 2022-09-19 at 6.45.22 PM.png
    3.5 MB · Views: 49
  • Screen Shot 2022-09-19 at 6.45.47 PM.png
    Screen Shot 2022-09-19 at 6.45.47 PM.png
    2.7 MB · Views: 47
  • Screen Shot 2022-09-19 at 6.46.20 PM.png
    Screen Shot 2022-09-19 at 6.46.20 PM.png
    1.4 MB · Views: 46
Last edited:

varoyzf

Member
Aug 14, 2012
7
1
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...

1.png
 

Top Liked Posts

  • 1
    Implying the fingerprint reader doesn't work on A12? Haven't had issues with it since I've got my device.


    Yeah, I'm sure there totally is a major security flaw, and they didn't just do this as another step to make modding more difficult. :D
    Some, like yourself, never had problems with the FPR. However, many did until the September update or the QPR1 beta. Personally I went from about 30% success to now close to 100%. That is pretty common for those, like me, who were saddled with a faulty unlock mechanism.

    As for modding, I'm not a conspiracy theorist though there are some in your camp saying Google is playing games. I don't mod these days so I was just reporting what has been documented.
  • 3

    HEY THIS MIGHT WORK FOR U!


    Was having the same issue, nothing seemed to be working.
    I had success finally, though!
    1. Be sure you realize your phone will be wiped, etc.
    2. Airplane Mode & No SIM inserted.
    3. Remove All Accounts From Phone (to prevent issues with locks, etc)
    4. 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.
    2
    I bought my 6a from the Google Store. I live in Hungary, unfortunately Google doesn't ship to Hungary, so I had a friend of mine ship the device to me from Germany.
    I booted up the phone, put my Hungarian Telekom SIM card in, set up everything normally. There was an update with a size of about 50 MB. Even after installing that + rebooting, in developer settings OEM unlocking is still greyed out, saying "Connect to the internet or contact your carrier." The second half of this message got me worried a bit - thinking it can only be unlocked with a German SIM? (That's probably nonsense though).

    I'm not super keen on rooting yet. I want to use the phone for a few weeks/months, just to see if everything is in order. Realistically, I'd only use Magisk to be able to use Advanced Charging Controller.

    --

    Apologies if this is super off-topic, but I've just noticed that there is a system update available that would upgrade me to Android 13. I've read about some nasty stuff about it (especially how the new bootloader (?) makes it basically impossible to root/unlock), so I'd rather postpone it for a while. Is my phone going to automatically download and install this update? If so, is there any way for me to prevent that from happening?
    First thing you need to do is factory reset after the 50 mb update. That will allow OEM unlock. After that upgrade to A13 it's a needed update. Don't worry about root yet.
    2
    I'm unsure what this number means. I assume you can tell by the model number whether or not your device is carrier locked?
    I see. I simply used a Google Search. Several search hits say:
    • Google PIXEL 6a 5G (Charcoal) G1AZG 128GB + 6GB RAM - GSM Unlocked (No CDMA)
    • Google Pixel 6A 5G 128GB/6GB RAM (G1AZG) GSM Unlocked International Version
    So, carrier unlocked, but GSM only - no CDMA.
    1
    Hi folks. Jumping into the thread here as well with some info.

    Basic context: Carrier unlocked Pixel 6a phone purchased in the US. Carrier unlock status confirmed by Google via IMEI check and by swapping out SIM cards in device. Multiple SIMs work fine. Have had multiple conversations with Google, no help at all. Been told it is a "software issue", to wait for the next update, but that next software update might** not solve it. Tons of circular logic while talking with Google reps, but I digress... I have updated to the September security release, Android 13, done factory resets from the OS, and followed other instructions listed. EOM Unlocking is still greyed out.

    Without OEM Unlocking available, phone is basically no useless for me.

    ***Here is the potentially interesting bit...I seems like there are errors during the factory reset process.

    While trying to perform a factory reset from "Android Recovery" screen, I get the following output:

    --Wiping data
    ERROR: recovery: [libfs_mgr] Unable to enable ext4 verity on /dev/block/platform/14700000.ufs/by-name/metadata because /system/bin/tune2fs is missing
    Formatting /data...
    Formatting /metadata...
    Wiping Titan M...
    Wiping key...
    ERROR: recovery: gto_eseha1 SecureElement:t1_recv_window_append free 261
    ERROR: recovery: gto_eseha1 SecureElement:t1_recv_window_append free 261
    ERROR: recovery: gto_eseha1 SecureElement:t1_recv_window_append free 261
    ERROR: recovery: gto_eseha1 SecureElement:t1_recv_window_append free 261
    Data wipe complete

    Is it possible that these errors are resulting in EOM Unlocking not being available?

    Don't want to sound conspiratorial but after multiple conversations with Google reps, it sounds like they have a sense of what is wrong but don't want to share for some reason.
    Looks like the os is corrupt. Tune2fs missing possibly means either faulty flash etorage or they didn't image it correctly from the start. Either way, replace it
    1
    Implying the fingerprint reader doesn't work on A12? Haven't had issues with it since I've got my device.


    Yeah, I'm sure there totally is a major security flaw, and they didn't just do this as another step to make modding more difficult. :D
    Some, like yourself, never had problems with the FPR. However, many did until the September update or the QPR1 beta. Personally I went from about 30% success to now close to 100%. That is pretty common for those, like me, who were saddled with a faulty unlock mechanism.

    As for modding, I'm not a conspiracy theorist though there are some in your camp saying Google is playing games. I don't mod these days so I was just reporting what has been documented.
  • 3

    HEY THIS MIGHT WORK FOR U!


    Was having the same issue, nothing seemed to be working.
    I had success finally, though!
    1. Be sure you realize your phone will be wiped, etc.
    2. Airplane Mode & No SIM inserted.
    3. Remove All Accounts From Phone (to prevent issues with locks, etc)
    4. 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.
    2
    Perhaps you can close this redundant thread since you cross posted to this one and it already has over 200 posts.

    2
    I bought my 6a from the Google Store. I live in Hungary, unfortunately Google doesn't ship to Hungary, so I had a friend of mine ship the device to me from Germany.
    I booted up the phone, put my Hungarian Telekom SIM card in, set up everything normally. There was an update with a size of about 50 MB. Even after installing that + rebooting, in developer settings OEM unlocking is still greyed out, saying "Connect to the internet or contact your carrier." The second half of this message got me worried a bit - thinking it can only be unlocked with a German SIM? (That's probably nonsense though).

    I'm not super keen on rooting yet. I want to use the phone for a few weeks/months, just to see if everything is in order. Realistically, I'd only use Magisk to be able to use Advanced Charging Controller.

    --

    Apologies if this is super off-topic, but I've just noticed that there is a system update available that would upgrade me to Android 13. I've read about some nasty stuff about it (especially how the new bootloader (?) makes it basically impossible to root/unlock), so I'd rather postpone it for a while. Is my phone going to automatically download and install this update? If so, is there any way for me to prevent that from happening?
    First thing you need to do is factory reset after the 50 mb update. That will allow OEM unlock. After that upgrade to A13 it's a needed update. Don't worry about root yet.
    2
    I'm unsure what this number means. I assume you can tell by the model number whether or not your device is carrier locked?
    I see. I simply used a Google Search. Several search hits say:
    • Google PIXEL 6a 5G (Charcoal) G1AZG 128GB + 6GB RAM - GSM Unlocked (No CDMA)
    • Google Pixel 6A 5G 128GB/6GB RAM (G1AZG) GSM Unlocked International Version
    So, carrier unlocked, but GSM only - no CDMA.
    1
    Same here - same issue