Question 6a from Google: Can't unlock bootloader

[Mustkeg]

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 and updated all the apps.

What can I do?

Best,
Mustkeg

 

[Badger50]

The option "OEM unlocking" is greyed out and it says "Connect to the internet or contact your carrier.".

You just answered your own question. While you may have purchased the device from Google, is it a "carrier" branded device for Big Red, AT&T, T-mobile..etc?

If so, then you'll have to contact the carrier to see if they will let you unlock it once it's paid off. Best bet is to return it for an "unlocked" model. Best of luck to you.

 

[bobby janow]

You just answered your own question. While to may have purchased the device from Google, is it a "carrier" branded device for Big Red, AT&T, T-mobile..etc?

If so, then you'll have to contact the carrier to see if they will let you unlock it once it's paid off. Best bet is to return it for an "unlocked" model. Best of luck to you.

That is exactly right. A warning to others, never buy a branded device even from Google.

 

[soundgarden104]

I'm actually in the same boat here, purchased the Unlocked non-carrier branded Google Pixel 6a directly from the Google Store and "OEM Unlocking" is greyed out...contacted Google support about it and they had no idea why, transferred to a specialist and still no answers...they said they're going to look into it more and get back to me

 

[Mustkeg]

I do not even have the choice to buy crappy "Verizon et al." locked variants in my country via the Google Store. I paid it in full up front and without any carrier bloat.

Just had a support chat with Google, they told me it's a bug and will be fixed in an update. Soon...ish.

 

[jejemc]

hello from store google in france .this and write unlock

 

[V0latyle]

I do not even have the choice to buy crappy "Verizon et al." locked variants in my country via the Google Store. I paid it in full up front and without any carrier bloat.

Just had a support chat with Google, they told me it's a bug and will be fixed in an update. Soon...ish.

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 the ro.oem_unlock_supported property is set to 0.
If ro.oem_unlock_supported=1 then OEM Unlocking will be available in Developer Options. This toggles the get_unlock_ability property 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.

 

[Mustkeg]

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 the ro.oem_unlock_supported property is set to 0.
If ro.oem_unlock_supported=1 then OEM Unlocking will be available in Developer Options. This toggles the get_unlock_ability property 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.

You're right. I definitely bought an unlocked device, but ADB getprop says [sys.oem_unlock_allowed]: [0].
I'll hold out for an eventual update for some days and if the end of the return window turns near, I'll return it.

Maybe other users will chime in soon and tell about their experiences with unlocking the 6a. There are not even factory images available at this point.

 

[V0latyle]

You're right. I definitely bought an unlocked device, but ADB getprop says [sys.oem_unlock_allowed]: [0].
I'll hold out for an eventual update for some days and if the end of the return window turns near, I'll return it.

Maybe other users will chime in soon and tell about their experiences with unlocking the 6a. There are not even factory images available at this point.

To be honest, this has been a mystery for more than a decade. I cut my teeth on the OG Motorola Droid, back when the most common recovery was ClockWorkMod, and CyanogenMod was still in its infancy. Still, we haven't quite figured out exactly what sets the ro.oem_unlock_supported property, especially in circumstances like the Pixel series, where unlocked devices from Google are seemingly identical to carrier branded devices, and even run the exact same firmware - yet the latter remains locked. It's entirely possible that this property is set in hardware, and that Google manufactures devices specifically for carriers who don't want the devices to be unlockable.

 

[K0mraid3]

Do you have Fastboot? If so, look up how to unlock bootloader with fastboot.

You can bypass Bootloader restrictions in some cases. What OS version are you on? What Version of Linux Kernel? You can find these answers in the "About" section.

 

[bobby janow]

To be honest, this has been a mystery for more than a decade. I cut my teeth on the OG Motorola Droid, back when the most common recovery was ClockWorkMod, and CyanogenMod was still in its infancy. Still, we haven't quite figured out exactly what sets the ro.oem_unlock_supported property, especially in circumstances like the Pixel series, where unlocked devices from Google are seemingly identical to carrier branded devices, and even run the exact same firmware - yet the latter remains locked. It's entirely possible that this property is set in hardware, and that Google manufactures devices specifically for carriers who don't want the devices to be unlockable.

If you recall this happened once before. I'm not sure which Pixel it was, perhaps the 3 or 4 but Google must have reset their IMEI database and then asked users to do a factory reset. That fixed it but it did require a wipe so beware once they fix it. It has to be the IMEI that allows or disallows the OEM switch since no one can find any other reason and how can they just globally reset the switch other than that. But I defer to the experts on this one.

 

[K0mraid3]

You're right. I definitely bought an unlocked device, but ADB getprop says [sys.oem_unlock_allowed]: [0].
I'll hold out for an eventual update for some days and if the end of the return window turns near, I'll return it.

Maybe other users will chime in soon and tell about their experiences with unlocking the 6a. There are not even factory images available at this point.

just saw this part - so there are a few options to try then. Let me read the rest of the post to see whats already been done and ill list a few other options. Also, check out my post on BruteRoot for a collection of ways you can get temp root in order to go and edit the build prop. or unlock BL.

 

[V0latyle]

Do you have Fastboot? If so, look up how to unlock bootloader with fastboot.

You can bypass Bootloader restrictions in some cases. What OS version are you on? What Version of Linux Kernel? You can find these answers in the "About" section.

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.

If you recall this happened once before. I'm not sure which Pixel it was, perhaps the 3 or 4 but Google must have reset their IMEI database and then asked users to do a factory reset. That fixed it but it did require a wipe so beware once they fix it. It has to be the IMEI that allows or disallows the OEM switch since no one can find any other reason and how can they just globally reset the switch other than that. But I defer to the experts on this one.

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.

 

[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....

 

[Mustkeg]

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....

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.

 

[hochoch]

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.

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."

 

[bobby janow]

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.

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.

 

[hochoch]

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.

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

 

[greatgoogly]

Just received my "unlocked" Pixel 6a direct from Google and indeed the entry in Developer Options to unlock the bootloader is greyed out.

 

[stormcrank]

Just adding to the list that I also received an "unlocked," carrier agnostic, 6a from Google with the bootloader unlock grayed out.