Database Info

Could a kind soul please confirm if my bootloader is locked?

i know some one will say search or some such but i have and right now am so tired and exhausted so please, if someone could just confirm it the bootloader is locked or if im just being tired and stupid and missing something
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

The device says locked, so yes the bootloader is locked. That information at the very last line is referring to your bootloader.

mikeprius said:
The device says locked, so yes the bootloader is locked. That information at the very last line is referring to your bootloader.
Click to expand...
Click to collapse
Thank you, so that means no fast oem unlock and then rooting, correct? there is no easy bootloader unlocking is there?

mark2410 said:
so that means no fast oem unlock and then rooting, correct? there is no easy bootloader unlocking is there?
Click to expand...
Click to collapse
Correct if you have the Verizon version. Not correct if you bought your phone from Google. That screen just means that your bootloader is currently locked. But it's trivial to unlock (and then root, if desired), as long as you don't have the Verizon version.

mikeprius said:
The device says locked, so yes the bootloader is locked. That information at the very last line is referring to your bootloader.
Click to expand...
Click to collapse
jss2 said:
Correct if you have the Verizon version. Not correct if you bought your phone from Google. That screen just means that your bootloader is currently locked. But it's trivial to unlock (and then root, if desired), as long as you don't have the Verizon version.
Click to expand...
Click to collapse
well..... neither. i in the UK and i got it from CEX so, basically second hand but still a shop so it can be returned if i cant unlock it. I have tried unlocking the bootloader but have been unable and as i not done it since my nexus 5 i can tell im so tired that if ive just missed soemthing silly or i cant unlock its bootloader. "Enable OEM Unlock" is greyed out in the dev menu

mark2410 said:
Thank you, so that means no fast oem unlock and then rooting, correct? there is no easy bootloader unlocking is there?
Click to expand...
Click to collapse
No. the idea of having a locked bootloader is so your phone is protected from the get-go. If you could unlock it and root it then the bootloader would be useless.
If you have been trying to unlock it and haven't been able to 1 of 2 (or possibly both issues) are present:
1. You have Verizon and they have updated the patch so Verizon users are not able to unlock unless a new exploit comes out.
2. You do not have fastboot and/or your phone drivers are not working, so fastboot is not properly working on your computer.
3. Both 1 & 2.

mark2410 said:
well..... neither. i in the UK and i got it from CEX so, basically second hand but still a shop so it can be returned if i cant unlock it. I have tried unlocking the bootloader but have been unable and as i not done it since my nexus 5 i can tell im so tired that if ive just missed soemthing silly or i cant unlock its bootloader. "Enable OEM Unlock" is greyed out in the dev menu
Click to expand...
Click to collapse
What version is the software? If it is 7.1.1 you are done. If it is 7.1 you can use depixel8 on it.

mark2410 said:
well..... neither. i in the UK and i got it from CEX so, basically second hand but still a shop so it can be returned if i cant unlock it. I have tried unlocking the bootloader but have been unable and as i not done it since my nexus 5 i can tell im so tired that if ive just missed soemthing silly or i cant unlock its bootloader. "Enable OEM Unlock" is greyed out in the dev menu
Click to expand...
Click to collapse
I'm not sure what that means with it being greyed out. I've seen others with that issue. Here in the United States that's not a problem, so it's likely something with the UK or carrier, or something else. I don't know any information beyond that.
---------- Post added at 02:43 PM ---------- Previous post was at 02:42 PM ----------
TonikJDK said:
What version is the software? If it is 7.1.1 you are done. If it is 7.1 you can use depixel8 on it.
Click to expand...
Click to collapse
He's in the UK. Verizon depixel8 is not applicable.

mikeprius said:
He's in the UK. Verizon depixel8 is not applicable.
Click to expand...
Click to collapse
It is an EE phone, that is what CEX has been selling. So yes depixel8 is applicable.

mikeprius said:
No. the idea of having a locked bootloader is so your phone is protected from the get-go. If you could unlock it and root it then the bootloader would be useless.
If you have been trying to unlock it and haven't been able to 1 of 2 (or possibly both issues) are present:
1. You have Verizon and they have updated the patch so Verizon users are not able to unlock unless a new exploit comes out.
2. You do not have fastboot and/or your phone drivers are not working, so fastboot is not properly working on your computer.
3. Both 1 & 2.
Click to expand...
Click to collapse
2 well peretty sure it was working fine, could use adb to find the device and reboot the phone no problem so no driver issues im aware of
TonikJDK said:
What version is the software? If it is 7.1.1 you are done. If it is 7.1 you can use depixel8 on it.
Click to expand...
Click to collapse
tried it did not work, ran, then would fail after a little bit, it is on 7.1.1
tbh im pretty sure its one thats come from EE so basically the same thing as verizon but the UK version of the devil in telco form. i think im just going to ahve te suck it up and pay the ridiculous price google want for one from them directly

mark2410 said:
2 well peretty sure it was working fine, could use adb to find the device and reboot the phone no problem so no driver issues im aware of
tried it did not work, ran, then would fail after a little bit, it is on 7.1.1
tbh im pretty sure its one thats come from EE so basically the same thing as verizon but the UK version of the devil in telco form. i think im just going to ahve te suck it up and pay the ridiculous price google want for one from them directly
Click to expand...
Click to collapse
Yea, you are done as far as unlocking is concerned. Sorry man.

TonikJDK said:
Yea, you are done as far as unlocking is concerned. Sorry man.
Click to expand...
Click to collapse
np, oh well now if i can just go back in time two weeks and just order one from google because of course now they are currently out of stock. :crying:
why the FFFFFFFFFF do networks lock the f ing bootloader of a bloody device that the point of is that its not full of network shi..... poo???

mark2410 said:
np, oh well now if i can just go back in time two weeks and just order one from google because of course now they are currently out of stock. :crying:
why the FFFFFFFFFF do networks lock the f ing bootloader of a bloody device that the point of is that its not full of network shi..... poo???
Click to expand...
Click to collapse
In the United States most of the major networks would subsidize or pay for some type of incentive for users to use their networks. They have an interest in keeping the users on their network and prevent taking the device to another network esp after paying incentives for it. I have an old Nexus 6 that Sprint paid for that I got at a very low price that is network locked to Sprint despite it being a global compatible network device.

mikeprius said:
In the United States most of the major networks would subsidize or pay for some type of incentive for users to use their networks. They have an interest in keeping the users on their network and prevent taking the device to another network esp after paying incentives for it. I have an old Nexus 6 that Sprint paid for that I got at a very low price that is network locked to Sprint despite it being a global compatible network device.
Click to expand...
Click to collapse
well no, people still pay for the device they just two it over 2 years rather than upfront. but anyway my point was more that people wanting to a buy a pixel probably want to becaues they dont want the networks to have enhanced / ruined it.
im just annoyed that i now have to go return the thing and waste half a day

mark2410 said:
well no, people still pay for the device they just two it over 2 years rather than upfront. but anyway my point was more that people wanting to a buy a pixel probably want to becaues they dont want the networks to have enhanced / ruined it.
im just annoyed that i now have to go return the thing and waste half a day
Click to expand...
Click to collapse
You are referring to either a payment plan or leasing which is different. In the past carriers used to offer 2 yr contracts which immediately subsidized the phone's entire cost. The Nexus 6 I was able to get brand new under $200 because of this. Verizon is packing in credit over 24 months, but this is still money that is being used as a subsidy.
http://www.droid-life.com/2016/11/22/verizon-black-friday-deals-pixel-xl/
Anyways good luck with the phone

[Resolved] Can I Root My Phone? It Depends...

Any carrier-branded phone sold by Verizon or AT&T will not have an unlockable bootloader. If you'd prefer to buy on contract from a service provider and root is one of your must-haves, we recommend purchasing through Sprint or T-Mobile. However, some phones sold by the latter two carriers still have bootloaders that can't be unlocked, so the only sure-fire way is to buy direct from the manufacturer.
So in the final steps of finding out exactly why I stopped being able to Root:
Contacted Samsung Tech
Verified Carrier Requested removal of OEM UNLOCK - not Samsung Removal
Verified existence of Hybrid Android OS
Sometimes it takes a bit of time to get solid proof, however, this Article should sum up everyone looking for Root Status.
https://android.gadgethacks.com/how-to/list-phones-with-unlockable-bootloaders-0179751/
Hope this helps. Some phones are Effectively Perma-locked
-Khronik

Can I root my Samsung S7 and gert rid of "all things ATT"..?

So, I'll apologize if this has already been dealt with previously, but I just need to verify what I've been told by a friend who knows Android systems (and Samsung S7 phones) a LOT more than I will ever attempt to understand..
About a year ago, I bought a Samsung Galaxy S7 from a 'rebuilder' (my term) who mentioned at the time "... it was ATT phone..", and, yes, when I turn it on it does the ATT circle jerk logo and has an ATT logo on the back of the phone. This was of no real concern to me, because my service purveyor uses the ATT system (Consumer Cellular), so it's worked well enough. But unfortunately, it also has a boatload of 'semi-proprietary' ATT trash in the phone which I'd like to get rid of. To confuse the matter even more, it appears that I cannot 'unlock' the phone because it has not been associated with an actual active ATT account for close to two years, and it APPEARS that now they refuse to accommodate an unlock code for this phone.
So... according to my friend (Mr. Android Phone), I can 'root' this phone to 'factory original firmware' and make it (in essence) just a plain-old-vanilla Samsung S7 without this rather bogus ATT firmware and the myriad of craplets I'd like to get rid of..
So, I'm here looking for "expertise" in such things because I certainly don't want to 'brick' this pretty nice phone, but I also want to get this to a point where there is no association with ATT in any manner. So my question sorta comes down to: "can I root this and be rid of all things ATT?", and "will this allow me to achieve an 'unlock' without having to play ATT's games? (I had QUITE the discussion with an ATT 'support' dude a couple of hours ago when he flatly refused to give me an unlock code so I could simply ATTEMPT to see if Consumer Cellular's T-Mobile service might work better at my home, since CC tells me I'm right in the center of a brand new rebuilt 4G service area).
Does any of this make any sense to anyone? Pardon my ignorance, but if the IMEI # is somehow 'tethered' to ATT and they won't "release" it, how does rooting help with this? - or is this something more like an 'association' of the IMEI # AND the ATT firmware...? GAH!! I'd just like to be totally rid of all this ATT junk and have the freedom to choose whichever service I want.

CentennialMan said:
So, I'll apologize if this has already been dealt with previously, but I just need to verify what I've been told by a friend who knows Android systems (and Samsung S7 phones) a LOT more than I will ever attempt to understand..
I'd just like to be totally rid of all this ATT junk and have the freedom to choose whichever service I want.
Click to expand...
Click to collapse
Hi There that's a lot of words partner! I'll try make the answer easy to understand and I've cut out much of the post so my reply isn't huge.
1. Yes you can install vanilla firmware which will remove all branding from AT&T and you don't need to root the phone to do this. here is the firmware for your device >>here<< You can also use XAS or XAA. You will see the guide and the Odin you need to flash this firmware.
2. This is another version of Odin on this website if you have any issues with the one on Sammobile. >>here<<
3. Unfortunately you cannot unlock the phone unless the original cell phone provider gives you their half of the unlock key as a code to input to the phone. In the UK once a phone is out of the initial contract period it is illegal for the provider to refuse to give you this code whether your still with them or not. I know in the USA you guys gets ****ed over. The original account holder of the phone can ask for the unlock code but not you.
4. Changing the firmware and unlocking the phone to any network are two different things, flashing unbranded firmware will not unlock the phone the network is tied to. They don't make it that easy!
5. As far as i know T Mobile (USA) has also moved to G930U firmware so you could be lucky with a T Mobile SIM working once the phone is flashed with this firmware but don't hold your breath. Check Sammobile for the T Mobile firmware too.
6. IMEI number is tied to the phone so in theory it can be changed after the phone is rooted and you are able to modify the EFS partition but it is extremely difficult even for veterans like me and it causes lots of problems with cell network registration. Leave well alone if you don't want a completely useless device.
Things to make flashing go easier
1. Turn off FRP lock or sign out of the Google account on the phone or delete it before you do anything, you can put that account back on the phone after flashing.
2. If you enable Developer options make sure " usb debugging" is enabled and OEM unlock, not essential but can help when things go wrong.
3. Anything you want to keep, pics media etc back up or move to SD card, the SD card won't be touched when flashing firmware.
4. Please follow the guides on how to flash correctly.
Any other questions please ask.

It should be noted that if it's an ATT phone it's Snapdragon therefore permanently bootloader locked, OEM Unlock won't actually do anything, that setting only works on Exynos.
The only root method for Snapdragon is to use a leaked engineering bootloader to gain system access, and you can only install the leaked bootloader if your phone is already running old firmware. For up to date phones there is no root method.

Beanvee7 said:
It should be noted that if it's an ATT phone it's Snapdragon therefore permanently bootloader locked, OEM Unlock won't actually do anything, that setting only works on Exynos.
The only root method for Snapdragon is to use a leaked engineering bootloader to gain system access, and you can only install the leaked bootloader if your phone is already running old firmware. For up to date phones there is no root method.
Click to expand...
Click to collapse
Hello mate i'm not sure if your aware but AT&T were initially Qual comm but they've also been using Exynos for a while.

cooltt said:
Hello mate i'm not sure if your aware but AT&T were initially Qual comm but they've also been using Exynos for a while.
Click to expand...
Click to collapse
Source?

Beanvee7 said:
Source?
Click to expand...
Click to collapse
Don't be smart you know how to use Google?

I did google it, I wouldn't have asked for a source if I found something. But it doesn't matter, you're the one making unsubstantiated claims, the burden is on you to prove it. But since you asked for it:
AT&T's website says Snapdragon
https://i.imgur.com/TdV62Mq.jpg
https://www.att.com/buy/phones/samsung-galaxy-s7-32gb-black-onyx.html
GSM Arena says Snapdragon
https://www.gsmarena.com/samsung_galaxy_s7_(usa)-7960.php
Wikipedia says Snapdragon
https://en.wikipedia.org/wiki/Samsung_Galaxy_S7#Qualcomm_Snapdragon_820_Models
There isn't a single page when googling AT&T S7 Exynos that backs your claim up. The USA also uses completely different network technology than internationally, using the S7 Exynos in the USA is already known to cause issues with LTE, VoWiFi etc. They'd have to do a hardware refresh of the Exynos SoC if they wanted to support it in the USA, which they ain't going to do a for a 3 gen old phone.

Beanvee7 said:
I did google it, I wouldn't have asked for a source if I found something. But it doesn't matter, you're the one making unsubstantiated claims, the burden is on you to prove it. But since you asked for it:
AT&T's website says Snapdragon
https://i.imgur.com/TdV62Mq.jpg
https://www.att.com/buy/phones/samsung-galaxy-s7-32gb-black-onyx.html
GSM Arena says Snapdragon
https://www.gsmarena.com/samsung_galaxy_s7_(usa)-7960.php
Wikipedia says Snapdragon
https://en.wikipedia.org/wiki/Samsung_Galaxy_S7#Qualcomm_Snapdragon_820_Models
There isn't a single page when googling AT&T S7 Exynos that backs your claim up. The USA also uses completely different network technology than internationally, using the S7 Exynos in the USA is already known to cause issues with LTE, VoWiFi etc. They'd have to do a hardware refresh of the Exynos SoC if they wanted to support it in the USA, which they ain't going to do a for a 3 gen old phone.
Click to expand...
Click to collapse
lol ok.

General PSA: There is No OEM Unlock on US Galaxy A53's

Whether you get a carrier version or the factory unlocked U1 model, OEM unlock does not exist on this phone. So those in the US that were thinking of doing custom roms with this cheap new Android device, look elsewhere.

Samsung has blocked their bootloaders on U.S. phone variants for years now. The only way to unlock is with paid service unfortunately.

ShaDisNX255 said:
Samsung has blocked their bootloaders on U.S. phone variants for years now. The only way to unlock is with paid service unfortunately.
Click to expand...
Click to collapse
What service are you referring to? I'd love to unlock mine.

Jay1175 said:
What service are you referring to? I'd love to unlock mine.
Click to expand...
Click to collapse
Well, it was located here: https://forum.xda-developers.com/t/sampwnd-usa-model-bl-unlock-info-u-u1-w.4201689/
But I guess it's temporarily closed until the person in charge returns. Usually it's not worth it for lower end phones since the unlock process can end up costing just as much as the phone tbh.

on some devices it takes 7 days for the oem unlock to show in developer options, have you tried the time and date hack to see if it shows

gav83collins said:
on some devices it takes 7 days for the oem unlock to show in developer options, have you tried the time and date hack to see if it shows
Click to expand...
Click to collapse
This does not work on U.S. variants

SamPWNd is dead. Samsung patched it with firmware updates in 2021 (it is in the warnings not to install unpatched firware updates). The website is down. Unless they can find a new exploit in the new firmware, it is not possible.
Samsung has blocked BL unlock for a while. They seem to have shifted their target audience to a different group in recent years. If you really want BL unlock you should pick Pixel.

b1283822 said:
SamPWNd is dead. Samsung patched it with firmware updates in 2021 (it is in the warnings not to install unpatched firware updates). The website is down. Unless they can find a new exploit in the new firmware, it is not possible.
Samsung has blocked BL unlock for a while. They seem to have shifted their target audience to a different group in recent years. If you really want BL unlock you should pick Pixel.
Click to expand...
Click to collapse
it doesnt make sense from a business perspective, a regular audience doesnt even know about unlocking a bootloader, so they will be buying the phone regardless if samsungs advertising impress more than the competition, but for us lets say "power users" we know our warranty is void when we oem unlock, and buy making it easier to do it (oem unlock), they are more likely to shift more handsets to our side of the market, not only that but there is more chance of us breaking our devices which in turn gives them more income when we seek samsung official repairs or splash out on a new replacement, i really dont see the logic behind not allowing oem unlock unless its to test the abilities of the likes of chainfire in regards to exposing vulnerabilities

I bought the phone on sale just a few days before this thread was made (hoping to use it as a fun side-project / second phone to get back into modding- haven't been able to since my Note 5 since the Note 8 was locked). I had assumed getting a non-carrier one would be open but I haven't been able to get OEM Unlock to appear either : /. I even went with the A53 instead of A52 because I thought there was a better chance of having unlock on Exynos than Snapdragon. It's not too late to return but I'm still holding out hope someone can come up with something. I like Samsung hardware (for the most part) but without root... meh.
Willing to try ODINing tars and stuff if anyone has any ideas.

sidestream84 said:
I bought the phone on sale just a few days before this thread was made (hoping to use it as a fun side-project / second phone to get back into modding- haven't been able to since my Note 5 since the Note 8 was locked). I had assumed getting a non-carrier one would be open but I haven't been able to get OEM Unlock to appear either : /. I even went with the A53 instead of A52 because I thought there was a better chance of having unlock on Exynos than Snapdragon. It's not too late to return but I'm still holding out hope someone can come up with something. I like Samsung hardware (for the most part) but without root... meh.
Willing to try ODINing tars and stuff if anyone has any ideas.
Click to expand...
Click to collapse
Exploits could take years to even begin to surface. S8 and S9 come to mind, but their root is so limited with locked bootloaders that it's almost not worth the hassle. I would return it to be honest or try and get an international variant imported. I've traveled to the U.S. with a Mexico variant phone and I got signal just fine, but I don't know how the internet speed compares if you use a U.S. SIM.

sidestream84 said:
I bought the phone on sale just a few days before this thread was made (hoping to use it as a fun side-project / second phone to get back into modding- haven't been able to since my Note 5 since the Note 8 was locked). I had assumed getting a non-carrier one would be open but I haven't been able to get OEM Unlock to appear either : /. I even went with the A53 instead of A52 because I thought there was a better chance of having unlock on Exynos than Snapdragon. It's not too late to return but I'm still holding out hope someone can come up with something. I like Samsung hardware (for the most part) but without root... meh.
Willing to try ODINing tars and stuff if anyone has any ideas.
Click to expand...
Click to collapse
I switched over from Pixel line just for a Samsung specific feature and a quick google had me certain I would be able to unlock the bootloader and root it. It sucks that its not the case, but I blame awful tech journalism. So many articles that claim their method will work for ALL devices in a family, or even ALL ANDROID devices period.
ShaDisNX255 said:
Exploits could take years to even begin to surface. S8 and S9 come to mind, but their root is so limited with locked bootloaders that it's almost not worth the hassle. I would return it to be honest or try and get an international variant imported. I've traveled to the U.S. with a Mexico variant phone and I got signal just fine, but I don't know how the internet speed compares if you use a U.S. SIM.
Click to expand...
Click to collapse
Getting an international version isn't worth doing IMO because the 5G bands don't overlap the same way 4G does. I looked in to getting an international model but decided against it as it doesn't support one of the three 5G frequencies used in my town. I figure there's 0 chance of new frequencies being added to the hardware, but always a chance of finding a security flaw to unlock the bootloader.

there are still U.S. Bootloader unlock services, but as of right now the A53 is not supported.
and only certain versions of bootloaders are supported.
Not SamPWND

Question 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 and updated all the apps.
What can I do?
Best,
Mustkeg

Mustkeg said:
The option "OEM unlocking" is greyed out and it says "Connect to the internet or contact your carrier.".
Click to expand...
Click to collapse
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.

Badger50 said:
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.
Click to expand...
Click to collapse
That is exactly right. A warning to others, never buy a branded device even from Google.

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

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.

hello from store google in france .this and write unlock
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Mustkeg said:
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.
Click to expand...
Click to collapse
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.

V0latyle said:
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.
Click to expand...
Click to collapse
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.

Mustkeg said:
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.
Click to expand...
Click to collapse
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.

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.

V0latyle said:
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.
Click to expand...
Click to collapse
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.

Mustkeg said:
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.
Click to expand...
Click to collapse
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.

K0mraid3 said:
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.
Click to expand...
Click to collapse
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.
bobby janow said:
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.
Click to expand...
Click to collapse
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.

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

hochoch said:
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....
Click to expand...
Click to collapse
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.

Mustkeg said:
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.
Click to expand...
Click to collapse
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."

V0latyle said:
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.
Click to expand...
Click to collapse
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.

bobby janow said:
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.
Click to expand...
Click to collapse
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

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

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