Related
So, I just got my shiny, new Pixel, and immediately went to unlock the bootloader prior to booting it up for the first time. I was not pleased to be greeted with the following message:
FAILED (remote: oem unlock is not allowed)
What I've found online is that with newer Android phones, you *have* to boot the phone first and enable USB debugging/OEM unlocking from the developer settings. Is there no way around this? I don't want to waste all that time doing that, only to wipe data a minute later.
If I am forced to do it this way, is there a way to get into the developer settings without first adding my google account, etc.? This is really, frustratingly difficult, especially for such an obscenely expensive phone!
Edit: Okay, you can get into settings without adding a Google account, but the "OEM unlocking" option is greyed out, with the message "Connect to the internet or contact your carrier." WTF? I don't even have a SIM in this phone yet. What gives, Google?
hackel said:
So, I just got my shiny, new Pixel, and immediately went to unlock the bootloader prior to booting it up for the first time. I was not pleased to be greeted with the following message:
FAILED (remote: oem unlock is not allowed)
What I've found online is that with newer Android phones, you *have* to boot the phone first and enable USB debugging/OEM unlocking from the developer settings. Is there no way around this? I don't want to waste all that time doing that, only to wipe data a minute later.
If I am forced to do it this way, is there a way to get into the developer settings without first adding my google account, etc.? This is really, frustratingly difficult, especially for such an obscenely expensive phone!
Click to expand...
Click to collapse
I can't answer the main part of the question, but you can skip adding a google account and still enable OEM unlock ability in dev options.
EDIT: regarding your edit, hackel, that is frustrating they make you "activate" it on a carrier or via google before allowing OEM unlock. Very Apple-ish.
hackel said:
Edit: Okay, you can get into settings without adding a Google account, but the "OEM unlocking" option is greyed out, with the message "Connect to the internet or contact your carrier." WTF? I don't even have a SIM in this phone yet. What gives, Google?
Click to expand...
Click to collapse
Did you buy the phone from Verizon or Best Buy? The only ones that support bootloader unlocking are sold direct from Google. The ones from Vz and BB will have "OEM Unlocking" greyed out.
FWIW, I just set mine up this morning. I skipped through most of the settings, didn't add a google app, enabled OEM unlocking, and then unlocked with fastboot with no issues.
EDIT: hmm, I may have put my SIM in it first. Can't remember.
dmbfan36_23 said:
[snip]
Did you buy the phone from Verizon or Best Buy? The only ones that support bootloader unlocking are sold direct from Google. The ones from Vz and BB will have "OEM Unlocking" greyed out.
Click to expand...
Click to collapse
Do you have confirmation of this? We know about Verizon, but where did you see that devices sold through BestBuy or other carriers would not allow unlocking?
dmbfan36_23 said:
Did you buy the phone from Verizon or Best Buy? The only ones that support bootloader unlocking are sold direct from Google. The ones from Vz and BB will have "OEM Unlocking" greyed out.
Click to expand...
Click to collapse
Are you sure? Ars Technica, for instance, among many, are reporting that the Verizon variant can indeed have the BL unlocked. The default for all versions is greyed out until you change it.
dmbfan36_23 said:
FWIW, I just set mine up this morning. I skipped through most of the settings, didn't add a google app, enabled OEM unlocking, and then unlocked with fastboot with no issues.
Click to expand...
Click to collapse
Did you have your phone connected to the internet and/or have a SIM in it when you enabled OEM unlocking?
dmbfan36_23 said:
Did you buy the phone from Verizon or Best Buy? The only ones that support bootloader unlocking are sold direct from Google. The ones from Vz and BB will have "OEM Unlocking" greyed out.
Click to expand...
Click to collapse
No, purchased directly from Google Store. I didn't add a working wifi network the first time (intentionally). I finally just caved in and added one, and after a few seconds the OEM unlocking option became available. I really wish I didn't have to allow the device to check-in with Google simply in order to unlock it.
Oh well, thanks!
efrant said:
Do you have confirmation of this. We know about Verizon, but where did you see that devices sold through BestBuy or other carriers would not allow unlocking?
Click to expand...
Click to collapse
Best Buy is selling the Verizon version. Google has stated that only the ones sold directly from them have unlockable bootloaders.
---------- Post added at 02:07 PM ---------- Previous post was at 02:03 PM ----------
dispatch said:
Are you sure? Ars Technica, for instance, among many, are reporting that the Verizon variant can indeed have the BL unlocked. The default for all versions is greyed out until you change it.
Click to expand...
Click to collapse
Where did they say that? Everything I've seen says it's not unlockable:
http://www.androidpolice.com/2016/10/04/confirmed-verizon-pixels-bootloader-will-not-unlockable/
All of the phones ship locked, but on non-Google versions the option to enable OEM unlocking remains greyed out.
All phones, including those sold by Vz, are carrier unlocked though.
dmbfan36_23 said:
Best Buy is selling the Verizon version. Google has stated that only the ones sold directly from them have unlockable bootloaders.
Click to expand...
Click to collapse
You're absolutely right. I must've read that the Verizon variant will be carrier unlocked and interpreted that as BL.
Still garbage that you have to phone home before the google variant will allow an OEM unlock.
dmbfan36_23 said:
Best Buy is selling the Verizon version. Google has stated that only the ones sold directly from them have unlockable bootloaders.
Click to expand...
Click to collapse
Ok, I think you are talking specifically about the U.S. then. I'm pretty sure Pixel devices sold through carriers here in Canada have unlockable bootloaders. My device hasn't arrived yet, so I haven't personally verified.
Out of curiosity... Has anyone tried removing the Verizon sim card and replacing it with a T-Mobile or AT&T sim before or after first boot to see if it changes the unlock option?
efrant said:
Ok, I think you are talking specifically about the U.S. then. I'm pretty sure Pixel devices sold through carriers here in Canada have unlockable bootloaders. My device hasn't arrived yet, so I haven't personally verified.
Click to expand...
Click to collapse
Please let us know when you do especially if you're on Bell. Thanks!
dmbfan36_23 said:
Did you buy the phone from Verizon or Best Buy? The only ones that support bootloader unlocking are sold direct from Google. The ones from Vz and BB will have "OEM Unlocking" greyed out.
FWIW, I just set mine up this morning. I skipped through most of the settings, didn't add a google app, enabled OEM unlocking, and then unlocked with fastboot with no issues.
EDIT: hmm, I may have put my SIM in it first. Can't remember.
Click to expand...
Click to collapse
Does anyone know for sure that the phones from best buy are locked and have a locked bootloader? I contacted best buy and they said the phones are locked but when I contacted Google support, they said those phones along with the Google store phones are unlocked with a unlocked bootloader. Don't know who to believe? I would like to buy the phone from best buy only if it's unlocked with a unlocked bootloader because the Google stores shipping and logistics are all screwed up. Ordered placed later are getting shipped before earlier orders. Not happy with Google.
Sent from my LGLS990 using Tapatalk
hackel said:
No, purchased directly from Google Store. I didn't add a working wifi network the first time (intentionally). I finally just caved in and added one, and after a few seconds the OEM unlocking option became available. I really wish I didn't have to allow the device to check-in with Google simply in order to unlock it.
Oh well, thanks!
Click to expand...
Click to collapse
Hackel, you don't need to enter your google account info or insert your sim. Just connect to wifi and then go to developer settings to disable OEM unlock.
Source: Me cause I did it, duh
tjarvis said:
Out of curiosity... Has anyone tried removing the Verizon sim card and replacing it with a T-Mobile or AT&T sim before or after first boot to see if it changes the unlock option?
Click to expand...
Click to collapse
That's a no go, the VZW model has a different CID.
I can't speak for why we have to connect to the internet before you can OEM unlock, but toggling this setting before you can unlock the bootloader is a security measure and its a really good thing.
Think about it, if your Pixel was a corporate phone or you actually cared about security, you would want the bootloader to be locked.
Without the need to boot the phone and enter a password:
1. I could steal / borrow your phone when you aren't looking
2. unlock the bootloader with ANY PC
3. then sideload a kernel that did something bad, or fastboot boot to twrp and install some malware
4. then give it back to you
OR
I could just steal your phone and wipe / flash it and keep it or sell it.
Nothing could stop me from doing either if you got your wish. In its current setup, your pin / password / fingerprint can still protect the phone from getting unlocked. You are in control.
I know anyone who wants to unlock the bootloader here does not care about security. I've been there. But you also have to think about who these phones are really made for. They were built to be mainstream phones for everyone. These aren't strictly developer phones. Even Nexus phones had this feature. My 5x and 6p required me to OEM unlock before I could unlock the bootloader. I don't remember if the Nexus 4, 5, 6 made me do this. It may have started with device encryption. I don't remember.
dbrohrer said:
I can't speak for why we have to connect to the internet before you can OEM unlock, but toggling this setting before you can unlock the bootloader is a security measure and its a really good thing.
Think about it, if your Pixel was a corporate phone or you actually cared about security, you would want the bootloader to be locked.
Without the need to boot the phone and enter a password:
1. I could steal / borrow your phone when you aren't looking
2. unlock the bootloader with ANY PC
3. then sideload a kernel that did something bad, or fastboot boot to twrp and install some malware
4. then give it back to you
OR
I could just steal your phone and wipe / flash it and keep it or sell it.
Nothing could stop me from doing either if you got your wish. In its current setup, your pin / password / fingerprint can still protect the phone from getting unlocked. You are in control.
I know anyone who wants to unlock the bootloader here does not care about security. I've been there. But you also have to think about who these phones are really made for. They were built to be mainstream phones for everyone. These aren't strictly developer phones. Even Nexus phones had this feature. My 5x and 6p required me to OEM unlock before I could unlock the bootloader. I don't remember if the Nexus 4, 5, 6 made me do this. It may have started with device encryption. I don't remember.
Click to expand...
Click to collapse
In the past, when you purchased a Nexus device, you could pull it out of the box, boot directly into the bootloader, and unlock the bootloader without booting into Android. Starting with the Nexus 6, if (and only if) you booted into Android before unlocking the bootloader, then you needed to enable the "Allow OEM unlock" setting to unlock the bootloader. (This was done as part of Google's factory reset protection, so that if you lost your device, someone wouldn't be able to just wipe it and use it.) So, having to enable the "Allow OEM unlock" setting is nothing new. However, now, apparently, what is new, is that you cannot unlock the bootloader when you take it out of the box for the first time, without booting into Android first. I fail to see how this is a security measure, as a brand new phone has nothing on it, and anyone can boot into Android anyway when taking it out of the box.
efrant said:
In the past, when you purchased a Nexus device, you could pull it out of the box, boot directly into the bootloader, and unlock the bootloader without booting into Android. Starting with the Nexus 6, if you booted into Android before unlocking the bootloader, then you needed to enable the "Allow OEM unlock" setting. (This was done as part of Google's factory reset protection, so that if you lost your device, someone wouldn't be able to just wipe it and use it.) So, having to enable the "Allow OEM unlock" setting is nothing new. However, now, apparently, what is new, is that you cannot unlock the bootloader when you take it out of the box for the first time, without booting into Android first. I fail to see how this is a security measure, as a brand new phone has nothing on it, and anyone can boot into Android anyway when taking it out of the box.
Click to expand...
Click to collapse
Ok. That sounds correct. I nevered tried to unlock out of the box. I assumed it was the same as after the first boot.
Thanks for the clarification.
efrant said:
In the past, when you purchased a Nexus device, you could pull it out of the box, boot directly into the bootloader, and unlock the bootloader without booting into Android. Starting with the Nexus 6, if (and only if) you booted into Android before unlocking the bootloader, then you needed to enable the "Allow OEM unlock" setting to unlock the bootloader. (This was done as part of Google's factory reset protection, so that if you lost your device, someone wouldn't be able to just wipe it and use it.) So, having to enable the "Allow OEM unlock" setting is nothing new. However, now, apparently, what is new, is that you cannot unlock the bootloader when you take it out of the box for the first time, without booting into Android first. I fail to see how this is a security measure, as a brand new phone has nothing on it, and anyone can boot into Android anyway when taking it out of the box.
Click to expand...
Click to collapse
It hinders someone from loading malware before the phone is booted. It also makes you clearly aware of the "risks".
Sent from my Pixel using XDA Labs
This is the dumbest complain thread that I've read in awhile honestly. You're complaining about a 1 minute inconvenience? Just login and OEM unlock and you're done...it took you longer to type up this thread and find a way around it.
Cares said:
This is the dumbest complain thread that I've read in awhile honestly. You're complaining about a 1 minute inconvenience? Just login and OEM unlock and you're done...it took you longer to type up this thread and find a way around it.
Click to expand...
Click to collapse
Well, there are other reasons for wanting to be able to unlock the bootloader without ever having booted into Android, so I wouldn't call this a complaint thread. For example, getting a complete backup of all the partitions in a (mostly) untouched condition (e.g., partitions like frp, persist, etc.).
Calling someone's question/observation a "dumbest complain thread" isn't really contributing to the discussion.
efrant
Senior Moderator
As stated above, I just purchased a refurbished Samsung Galaxy S6 off Woot.com last week. It was advertised as Verizon/GSM Unlocked. As I have found out, EVERY SINGLE Verizon Samsung S6 is always unlocked from the factory.. except mine.
I use Ting Wireless running a T-Mobile style SIM, coming from a Blue R1 HD. I confirmed the IEMI with my ting rep, they confirmed the compatibility of my current SIM, but because somehow this phone is locked, I am SOL at the moment.
My theory lies in the fact that maybe the phone was refurbished overseas, and was then set to different band settings and is not quite factory default.
Any information is welcome. My next plan was reflashing the firmware to the oldest setting, trying the card then, then updating if successful. Thank you in advance.
umph1348 said:
As stated above, I just purchased a refurbished Samsung Galaxy S6 off Woot.com last week. It was advertised as Verizon/GSM Unlocked. As I have found out, EVERY SINGLE Verizon Samsung S6 is always unlocked from the factory.. except mine.
-snip
Click to expand...
Click to collapse
Have you done a factory reset through the bootloader?
If your device is frp / samsung or google locked then read below.
I had just spent the last 2 days trying to figure out what the hell I could do to remove the frp lock on my device. After alot of XDA and Youtube browsing I have found a solution, and I guarantee it will work for you! First off, the Google Account FRP lock is different than the Samsung Account Reactivation Lock (Samsung FRP) So if it is asking you to sign into google account, then theres a much easier way around it.
What you need is Z3x Box, You can get the program via PM'ing me, the program does not require you to have a box with it.
You want to then put your phone into download mode (Home key, volume down, and power) While phone is off. Press Vol Up to continue.
Back to Z3x, once you start the program, connect your device
Now once it successfully connects and you choose your phone model (Make sure its the correct one) go to the UNLOCK tab, and select Reset/Frp/React/EE
if successful you will see what is shown in the image link below.
If not, Factory reset / Wipe with the bootloader and go back into download mode.
https://i.imgur.com/5nwGZUy.png
I just recently a few days upgraded my phone from an older Samsung to a Pixel 3 XL., and I am on sprint.
And while still getting used to the Pixel vs Samsung, today I let the phone take the update to Android 10, and not really feeling the love and want to go back to Pie if I can. Already miss having the back button moved to the right side and a few other things.
I did buy the phone used, online, and is not under any lease etc. I do own it.
But unfortunately, I believe because it was probably a Sprint phone originally, OEM Unlock under the developer options is greyed out. I think this means I am currently SOL until there is a way to unlock it?
Thanks,
PT
ptmuldoon said:
I just recently a few days upgraded my phone from an older Samsung to a Pixel 3 XL., and I am on sprint.
And while still getting used to the Pixel vs Samsung, today I let the phone take the update to Android 10, and not really feeling the love and want to go back to Pie if I can. Already miss having the back button moved to the right side and a few other things.
I did buy the phone used, online, and is not under any lease etc. I do own it.
But unfortunately, I believe because it was probably a Sprint phone originally, OEM Unlock under the developer options is greyed out. I think this means I am currently SOL until there is a way to unlock it?
Thanks,
PT
Click to expand...
Click to collapse
Contact Sprint, give them the IMEI number, they will look up the phone to verify that there is no balance on it and then they will send you an unlock code. Or at least I know AT&T used to do that bank when I had Samsung phones. AT&T had a link you could go to and do it, but I'm not sure about Sprint.
FilthyFord said:
Contact Sprint, give them the IMEI number, they will look up the phone to verify that there is no balance on it and then they will send you an unlock code. Or at least I know AT&T used to do that bank when I had Samsung phones. AT&T had a link you could go to and do it, but I'm not sure about Sprint.
Click to expand...
Click to collapse
I actually called them last night There tech support guy although rather nice seemed to not understand what I wanted. And after he got help was telling me I need to call google for it, which makes no sense to me.
In reading today here, it mentions Sprint will unlock a phone after 50 days on their network. But I think this is just referring to a Sim/Carrier unlock and not the OEM unlock ability?
https://www.sprint.com/en/legal/unlocking-your-sprint-device.html
EDIT......
How very strange, and perhaps my phone call last night got elevated. I just received a notification on my phone that is has been carrier unlocked and can not enable OEM Unlock. So I hope tonight to reinstall Pie.
ptmuldoon,
So effectively, are you saying that your previously Sprint (sim) locked phone is now (sim) unlocked, BUT that the OEM Unlock option is STILL greyed out?
Based on my reading, I've seen some folks mention that once the phone is (sim) unlocked, you should be able to OEM unlock the bootloader as well. And maybe that isn't necessarily saying that the OEM unlock option will become available, but that you can fastboot unlock bootloader. I'm not sure, but just confirming with you since you seem to be in that situation. Have you not been able to unlock the bootloader?
Thanks,
The model is G020E, but does not have any Verizon branding on it; everything just says Google. I was told it was a Sprint phone, but I don't know if that means Sprint sold it, or if it was just moved to Sprint network at some point. Either way, the only branding (physical and software) is Google.
When I go into Developer Options, OEM unlocking is greyed out and says "Connect to the internet or contact your carrier." (Connecting to the internet doesn't change anything.)
From what I've read, there's no way to unlock the bootloader on the Verizon version. Does it sound like this phone is in that group?
Also, I've read some people saying that Verizon will unlock the phone after it's been activated for a couple months. It seems like they are talking about SIM unlocking, but I've also seen claims that people got the bootloader unlocked by just waiting the 60 or so days. Anyone have any experience with that?
Thanks
lemminman said:
The model is G020E, but does not have any Verizon branding on it; everything just says Google. I was told it was a Sprint phone, but I don't know if that means Sprint sold it, or if it was just moved to Sprint network at some point. Either way, the only branding (physical and software) is Google.
When I go into Developer Options, OEM unlocking is greyed out and says "Connect to the internet or contact your carrier." (Connecting to the internet doesn't change anything.)
From what I've read, there's no way to unlock the bootloader on the Verizon version. Does it sound like this phone is in that group?
Also, I've read some people saying that Verizon will unlock the phone after it's been activated for a couple months. It seems like they are talking about SIM unlocking, but I've also seen claims that people got the bootloader unlocked by just waiting the 60 or so days. Anyone have any experience with that?
Thanks
Click to expand...
Click to collapse
I Googled the model and it said it's an unlocked model. But once you boot it with that Verizon SIM card in it, Verizon will lock you out of OEM unlocking. Remove your SIM card and factory reset. Go through the setup, then try the OEM unlocking again (remember after you flip that switch, you still need to go through fastboot to actually unlock). Then factory reset again, this time with your SIM card installed.
That 60 days thing is definitely SIM unlocking. It will be a cold day in hell before Verizon consciously allows the bootloader to be unlocked.
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.