OEM Unlocking grayed out

[pclewis]

I have the 30 Pixel 3 that I bought from Google. It has a FI Sim and the boot unlock is not greyed out.

 

[mattbeau]

I just got mine in today from Google, it's not greyed out and I'm on verizon

 

[ktdt00]

I'm coming from a decade of rooted Verizon HTC's so I'm a PIxel noob but here's my story... I got the P3 unlocked from Google, powered on, skipped all of setup, enabled dev options, and OEM unlock was greyed out. I enabled wifi, connected to Internet, waited 2 minutes, still greyed out. I rebooted the phone, went back to dev options and OEM unlock was available. Then I unlocked and rooted following the guides and using the posted patched boot image in the XL thread. I did some root testing, then powered off, installed my Verizon SIM, powered on, connected to VZW. About 10 minutes later I got a notice that a system update couldn't be installed, retried and failed again, so I guess there's some OTA pending but otherwise everything is perfect. Thanks to all who contributed and helped!

 

[TonikJDK]

I'm coming from a decade of rooted Verizon HTC's so I'm a PIxel noob but here's my story... I got the P3 unlocked from Google, powered on, skipped all of setup, enabled dev options, and OEM unlock was greyed out. I enabled wifi, connected to Internet, waited 2 minutes, still greyed out. I rebooted the phone, went back to dev options and OEM unlock was available. Then I unlocked and rooted following the guides and using the posted patched boot image in the XL thread. I did some root testing, then powered off, installed my Verizon SIM, powered on, connected to VZW. About 10 minutes later I got a notice that a system update couldn't be installed, retried and failed again, so I guess there's some OTA pending but otherwise everything is perfect. Thanks to all who contributed and helped!

You can download the full image for Verizon from Google. Edit the flash-all bat file and remove the -w from the end. Be sure to save that change. That will let you flash the while phone but save data and setup. Boot into fastboot mode and run the flash all file.

That will get you up to date but save your data. You will have to reroot by patching the VZ boot.img and flashing it. The boot.img flashing is about to get easier, TWRP is working just not released yet.

That is how I update each month. I would wait until next week when the Oct. update comes out.

 

[Cenex22]

I just got mine in today from Google, it's not greyed out and I'm on verizon

Same with me, I ordered the unlocked version, put in my Verizon sim immediately before even booting up, have version .031, and can still freely unlock the bootloader. Maybe it's a lottery?

 

[cswithxda]

Unlocked version directly from Google Store. The option is greyed out no matter what I do...

Wifi is connected, reset a couple of times, restarted a ton, even finally activated it on Fi and the option is still greyed out. The build used to end with 30 and now after November patch ends in 17 (universal). I don't want to give up this device because it has a good screen with minimal tint :crying::crying::crying:

 

[jascolli]

Well I see I'm not the only one having issues. I'm really disgusted. Ordered the non-carrier branded Google unlocked version from the Google store and have the greyed out OEM Unlock switch... Booted initially with the Verizon sim installed. I've tried everything with no luck. I don't know what to do. If anyone finds a solution be sure to let us know. Thanks Jason

 

[bobby janow]

Unlocked version directly from Google Store. The option is greyed out no matter what I do...

Wifi is connected, reset a couple of times, restarted a ton, even finally activated it on Fi and the option is still greyed out. The build used to end with 30 and now after November patch ends in 17 (universal). I don't want to give up this device because it has a good screen with minimal tint :crying::crying::crying:

It was only a matter of time. Everyone at Google is disavowing knowledge of bl unlock or even of what the bootloader is. I think at this point if you get an unlockable one you're one of the lucky ones. It's slowly coming to an end for Google branded devices. Unfortunately I don't think it will end there either. They tested it out on the Pixel OG, refined it on the Pixel 2s, and nailed it on the 3s. Don't even think of an RMA if you get an unlockable one unless you don't care one way or the other.

 

[cswithxda]

Remembering how I jumped onto the Google's reference phone wagon... When I saw the Nexus 4 was so cheap I sold my Note 2 at heavy discount and didn't expect much out of the phone. Turns out it was an underdog and all positive surprises. Now? Still full of surprises, just the bad ones. Golden old days of Nexus 4 and even Nexus 5 are gone

 

[Xaikar]

Remembering how I jumped onto the Google's reference phone wagon... When I saw the Nexus 4 was so cheap I sold my Note 2 at heavy discount and didn't expect much out of the phone. Turns out it was an underdog and all positive surprises. Now? Still full of surprises, just the bad ones. Golden old days of Nexus 4 and even Nexus 5 are gone

I feel you there, I know 0 about development but I am looking to see if I can add a circle style notification at the bottom like the Nexus 4 had, now that the LED is totally gone
Also have the OEM locked out and getting the client=ms-android-verizon when searching in Chrome. So frustrating. I want NOTHING to do with Verizon.

 

[schalacker]

Glad to see I'm not the only one as well and that it's not as uncommon as i thought.

Ordered 2 Pixel 3's through the Project Fi store 2-3 weeks ago (for the "buy 2 pixel 3's get $800 Fi credit" promotion), both at the same time. Also ordered a new Project Fi SIM for the new account (I have my current Fi account on SIM in a N5X).
Wifes came in first (not pink) pre-loaded with .030. Loaded up the SIM, activated the account and then went about messing around rooting hers, updating to the Nov OTA, etc. Everything went fine with that one.
The 2nd one came in (just black, my replacement) with .030 and went through the same process (loaded my Fi SIM in, activated the account on that unit, etc) except the "OEM Unlocking" feature was still greyed out. Tried loading the Nov update, factory resetting, etc with no luck of getting the OEM Unlocking feature enabled (same notification, "Please connect to the internet or contact your wireless carrier") even though the account was active and i was connected through WiFi.
I ended up going through Project Fi support to try and get a RMA as i had read that that was the only real resolution to the problem. And yes, Fi support was very confused as to what issue i was reporting, why it was necessary to fix, etc. It took several explanations to resolve the issue before a RMA was issued. I'm currently waiting for FedEx to pick up the defective unit while the replacement P3 is in transit. Hopefully the new one that arrives has the feature enabled.

I have to agree with the other posters, this is frustrating either as a blatant Google QA problem or deceptive trend on their part of trying to block the feature going forward.

Update: Wow, the new unit came in much faster than anticipated, they overnighted the replacement.
Immediately powered it up, connected to WiFi but avoided setting up the account. Went straight to check Build, which was pre-loaded with .030. Went to developer options and the "OEM Unlocking" feature was available, which i enabled immediately. Glad that worked out. Will work on messing around with this unit to bootloader unlock, Nov update, Magisk, etc.

 

[kaoticfyre]

Well I see I'm not the only one having issues. I'm really disgusted. Ordered the non-carrier branded Google unlocked version from the Google store and have the greyed out OEM Unlock switch... Booted initially with the Verizon sim installed. I've tried everything with no luck. I don't know what to do. If anyone finds a solution be sure to let us know. Thanks Jason

Got an RMA on mine. Had to escalate to a manager.

 

[cswithxda]

Got an RMA on mine. Had to escalate to a manager.

Please let us know if your replacement suffer from this issue. We see many people including myself who had original device unlockable but not the replacement. Maybe the newer batches suffer from this issue.

 

[VermontKindBud]

FWIW, I have the unlocked version of the 3 from Google, and had no issue whatsoever unlocking the bootloader. It was as simple as enabling the developer options, enabling OEM unlocking in developer options, rebooting to bootloader and executing the command "Fastboot flashing unlock" in ADB.

 

[jascolli]

I got an RMA on mine too for this issue. New one will be here in a couple of days. I'll keep you all posted.

So once the new one arrives, what is the best way to initially boot it up to minimize risk of greyed out OEM Unlock? Boot with no sim, don't sign into Google then go straight to Developer options?

Thanks

 

[TonikJDK]

I got an RMA on mine too for this issue. New one will be here in a couple of days. I'll keep you all posted.

So once the new one arrives, what is the best way to initially boot it up to minimize risk of greyed out OEM Unlock? Boot with no sim, don't sign into Google then go straight to Developer options?

Thanks

How you boot it does not matter. It's only a matter of if your IMEI is in the database to unlock or not.

 

[Phil_Chambers]

I was also approved for the RMA. Hopefully they'll send me the right one this time.

Also my build # ends with .A1, not .30 or .31 like everyone else here. Any significance to that?

 

[jascolli]

I was also approved for the RMA. Hopefully they'll send me the right one this time.

Also my build # ends with .A1, not .30 or .31 like everyone else here. Any significance to that?

Yeah my build number ends with . A1 too...

 

[TonikJDK]

The build number is the software. 30 was the firtst Google version, 31 was Verizon and A1 is November for both.

 

[Phil_Chambers]

The build number is the software. 30 was the firtst Google version, 31 was Verizon and A1 is November for both.

It should still be unlockable though correct?