yashsingh1/xdaforums huggingface dataset:
[Google Pixel Questions & Answers] changoland:
I had the exact same luck.

I had to sadly RMA my perfect rooted Pixel due to charger no longer functioning fully expecting a locked bootloader and 7.1.2. Verizon sent me one overnight. It had 7.1.2 but in developer options it had the same Allow OEM Unlocking slider NOT greyed out. I was then able to adb restart bootloader and adb bootloader unlocking and the phone prompted me and that was that. Adb booted to TWRP, installed RR Rom, vendor image, magick, TWRP, root. Can not believe the incredible luck.

Also wanted to say that I used my Verizon SIM card to do this and connected to WiFi on initial setup and I STILL managed to unlock it in time before anything locked itself.
[Google Pixel Questions & Answers] JAYNO20:
What does it say on your my Verizon account?
[Google Pixel Questions & Answers] deadlydecision:
Not using it on Verizon, just using the Verizon edition on T-Mobile.
[Google Pixel Questions & Answers] TCPDump:
Thats great information, thanks! It seems like Google is being less careful to lock the VZW versions. Maybe they will stop the stupidity on the Pixel 2 and not even try.
[Google Pixel Questions & Answers] seshaz:
You just need to remove the sim and update to 7.1.2. No need for the other carrier sim
[Google Pixel Questions & Answers] wilnotdie:
Hmmm. If it's a whitelist of sorts, someone should man in the middle something. Wish I had one to test. I almost feel like trying to exchange mine lol
[Google Pixel Questions & Answers] aholeinthewor1d:
This has been looked into multiple times before. Some people just get lucky and get ones that are unlockable. Has nothing to do with the SIM unfortunately. Assuming it's just because they are rushing them out
[Google Pixel Questions & Answers] torontomark:
Wondering if this has been tried...

I am on O preview, if I opt out, it is supposed to return the phone to 7.1.2? (not sure) but if that happens, do you think the sim not being Verizon will allow for the rooting at that point?

Opinion? thx
[Google Pixel Questions & Answers] bill12690:
curious of this as well...
[Google Pixel Questions & Answers] TonikJDK:
My opinion... no if you can't unlock now none of that is going to make any difference. This whole thread is smoke and mirrors. People are not paying attention to the details as they​ get a VZ phone that is unlockable. There are only 2 ways to unlock a VZ phone.

1 Get it while it is on 7.1 and hit it with depixel8 before it updates.

2 Get one that Google messed up on and forgot to enter in the master database as a VZ phone.

That is it gang. There is nothing new here. We have tested and researched this ad nauseum.
[Google Pixel Questions & Answers] ian_mcxa:
I got lucky with an RMA. Replacement came in a cardboard box although it appears to be new. Popped in a T-mobile sim, booted and unlocked.
[Google Pixel Questions & Answers] 42grand:
I got my replacement from Google on Monday. I had no clue that they shipped me a Verizon branded phone with a preinstalled sim. I booted, saw it was on the first build of 7 so I quickly tried to unlock it. First I turned off the automatic updating but I didn't realize there was a sim in it. It didn't work the first time so it rebooted and in the background I didn't know it had downloaded the 7.1.1 update and installed it. The oem unlock was always greyed out. Since it has the patched update I'm thinking I'm out of luck. What do you all think? Is there any way I can get around this??
[Google Pixel Questions & Answers] krazah:
Totally worked!

Thanks! this totally worked though I failed to follow it exactly because I didn't find this post until after unboxing my RMA Verizon Pixel XL (its running NOF26V, Feb 2017) so here is what I did and here is what happened. I opened the box pulled the sim card booted it and went past all the setup skipping internet connections all the way. I enabled Dev options and the OEM locking was grayed out. I started looking into my options and thought I was SOL I came across this post and poped in the project FI card from my brothers account. after 10 minutes I found a message on the phone saying project fi not completely activated and when I went in to developer settings I found that the oem unlocking was available. I toggled it on and ran adb reboot bootloader, then fastboot flashing unlock, approved the unlock on the device. I am in the processing of installing TWRP now.
[Google Pixel Questions & Answers] Nick80835:
Old thread, I know.. but popping a Verizon sim into a Google version and updating the device may render unlocking unavailable as well.

Some people have also found that putting in a sim from any carrier but Verizon and applying a system update will allow unlocking again.

This is not confirmed or guaranteed but it's worth a shot. Also, if anyone has a Verizon pixel and wants to go to the O preview via OTA can you take the sim out before opting for the beta program and downloading the update via WiFi. After it is installed I'm wondering if it will be OEM unlockable again.

The reason I suspect this may allow unlocking again is because the Nougat software has a separate branch of updates for Verizon. The O preview however has a unified branch that will apply the same bootloader, radio, modem and other partitions as that of a Google version of the device.

Just some food for thought. ;)

[MENTION=5878486]TCPDump[/MENTION]

Oh, and I purchased a Verizon pixel on contract and it came with a Verizon sim card preinstalled. I didn't let the people at the Verizon store to turn on the device, they allow this sometimes. I took the sim out and set up the device without connecting to WiFi. I opened settings, checked my software version which was 7.1.1 December. At that moment my heart kinda dropped.

I enabled developer options and to a very pleasant surprise the slider was not greyed out and I flipped it and unlocked the bootloader with my desktop and put the Verizon sim back in. My device also has the VZW CID. :p

Ah, and one last thing to anybody who reads this. Once the bootloader is unlocked, do not relock it if you are using a Verizon sim even if you got the device from Google. There's a risk that it could not allow you to unlock it again after relocking. For you people who have unlocked and are on Verizon, rest assured that the device cannot relock itself via an update or any other means unless you issue the command to do so via fastboot.

Once it's unlocked, it's always unlocked and only you have the power to lock it back! :laugh:
[Google Pixel Questions & Answers] TonikJDK:
Log into your My Verizon account and look at your device please. But do it from a web browser so you can see its details, not the app. What does it list it as? A VZW Pixel or a Non VZW
[Google Pixel Questions & Answers] Nick80835:
It doesn't really say either of those, just "Google Pixel 32GB in Quite Black" :confused:
[Google Pixel Questions & Answers] JAYNO20:
If it reads anything OTHER than "NON-VZW Device" then it's the Verizon version of the phone. He was just making sure you didn't get a Google version.
[Google Pixel Questions & Answers] TonikJDK:
Sorry, my mistake in the way I worded it. That is a VZ phone.
[Google Pixel Questions & Answers] ipeedalil:
Can confirm

Received my warranty claim today and was able to unlock bootloader.

My method:

Skipped inserting sim

Connected to wifi

Restored Google account

Upon completion of setup checked build no. and enabled developer options

Was able to select OEM unlock

Booted Into bootloader

Connected to PC and opened a command window and entered the following commands

ADB fastboot

Fastboot oem unlock

Then was greeted with a selection to unlock device
[Google Pixel Questions & Answers] bobby janow:
Who cares? Another scam or lucky? Either way this is getting tired.
[Google Pixel Questions & Answers] piperx:
That OEM unlocking looks greyed out to me.
[Google Pixel Questions & Answers] ipeedalil:
Grayed out because it says the bootloader is already unlocked
[Google Pixel Questions & Answers] TonikJDK:
That is what I was going to say. Then I looked at mine, which is unlocked.
[Google Pixel Questions & Answers] ipeedalil:
Yeah that is a bit odd I wonder why mine doesn't show up like yours. What build are you on
[Google Pixel Questions & Answers] TonikJDK:
Google phone on the July VZ version. I don't get why mine is like that. In the past they were grayed out I believe until you relocked via Fastboot. Exactly what the other poster was saying.

There is so much going on here we don't know.
[Google Pixel Questions & Answers] sliding_billy:
My Verizon unlocked bootloader is greyed out and has shown that way as already unlocked since using depixel on it.
[Google Pixel Questions & Answers] bobby janow:
I'm pretty sure but not positive about this: When you use depixel8 the oem toggle is grayed out (it's always grayed out on the Verizon models) but it's in the off position, i.e. the left toggle. On a Google version the oem switch is active but it turns gray with the oem unlock toggle in the on position (to the right) once you unlock the bootloader with fastboot. That only makes sense right? You don't want to turn the switch off if your bootloader is already unlocked.

If you want the switch to be active you need to relock the bootloader in fastboot.
[Google Pixel Questions & Answers] sliding_billy:
Yeah, I was just thinking that the person who had it greyed out might have had Depixel ran on their phone.
[Google Pixel Questions & Answers] bobby janow:
Unless things have changed with the Pixel or the latest 7.x updates (I have a Verizon model with a locked bootloader so I can't really check) I am not so sure what you say is correct. I believe with depixel8 the switch is always grayed out but on the other side and it doesn't say OEM unlock, your bootloader is already unlocked. It shows nothing to inform you that the bl is unlocked. I believe the person got lucky (or unlucky since his bl is now unlocked ;) ) and got a Google version. It will probably remain unlocked until he locks it for whatever reason. Then it will gray out and he's back to where he should be. I certainly hope this was not another "oh my Pixel has xyz problem and I need a replacement... oh and can you send me the Google one.."

As you know there has been multiple threads regarding this so I won't rehash it. As for the above unlock statements I'm going by my 5X which is now on beta O, oem unlock enabled but bootloader locked atm.
[Google Pixel Questions & Answers] sliding_billy:
Looking at developer options right now and I was certainly depixel unlocked last fall. Grey, OEM unlocking, Bootloader is already unlocked. I'm thinking he got a Verizon replacement that had depixel ran on it before.
[Google Pixel Questions & Answers] TonikJDK:
+1
[Google Pixel Questions & Answers] piperx:
Well I guess it's a verizon exclusive, I am unlocked, rooted and mine is not greyed out (bought from google store)
[Google Pixel Questions & Answers] bobby janow:
Rats.. there goes my theory. Can you actually toggle the switch while unlocked? What would be the point to allow that?
[Google Pixel Questions & Answers] piperx:
Yes I can

---------- Post added at 07:35 PM ---------- Previous post was at 07:29 PM ----------

The point would be to flip the switch then fastboot oem unlock/fastboot flashing unlock

---------- Post added at 07:38 PM ---------- Previous post was at 07:35 PM ----------

There's a lot of commands you can do with oem
[Google Pixel Questions & Answers] bobby janow:
What? That makes no sense. Oh well whatever you like is fine.
[Google Pixel Questions & Answers] piperx:
I take it your on verizon
[Google Pixel Questions & Answers] ipeedalil:
No I don't think it was when I opened the box the Android splash didn't display the unlocked symbol nor did I get the warning about not being able to check for corruption. Booted into the newest vzw firmware build and the option to unlock the bootloader was selectable in Dev options so I went through the rest of the process praying I didn't brick it.
[Google Pixel Questions & Answers] Nick80835:
The reason the switch is greyed out is because you're not supposed to be able to toggle it on Verizon. If you unlock the bootloader and the switch becomes greyed out after inserting SIM then your device is Verizon locked but you already unlocked the bootloader so it doesn't matter. The OEM unlock toggle is accessable on a normal Google Pixel on any carrier besides Verizon despite the bootloader unlock state. You can toggle that switch off even if the bootloader is unlocked but it won't change anything about the unlock state. If you got a device from Google thinking it's a "Verizon model" it isn't. If you insert a Verizon SIM into any Pixel it's becomes a Verizon model automagically. :eek:
[Google Pixel Questions & Answers] TonikJDK:
Below is the screenshot of my Google bought phone with a Verizon SIM running the latest verizon image.
[Google Pixel Questions & Answers] Nick80835:
Moist.
[Google Pixel Questions & Answers] bobby janow:
Incorrect.

---------- Post added at 11:56 AM ---------- Previous post was at 11:55 AM ----------

Yes, I am. But my 5x is not so I'm curious what you mean. If you're bootloader unlocked, the oem switch is still active? That's new but I can't argue because I don't have a Pixel outside the VZW network.
[Google Pixel Questions & Answers] :
Decided to gamble and ordered Google Pixel from Verizon's internet store (128 GB model Google Pixel Sailfish) - I know it's the wrong thread to post but this thread convinced me to try and unlock the bootloader on this one (I loathe Verizon's stupid bootloader lockdown policy - but let's say it's more of a "Challenge accepted" thing).

EDITED: Whoops, it was actually the correct thread as it's under "Google Pixel", I thought it was under "Google Pixel XL".
[Google Pixel Questions & Answers] RRRRyan:
You will be a lot of peep's hero if you find an exploit, even if you can just get 7.1.2 back down to 7 and let depixel8 do the rest. I have one (NHG47O) that has the notorious microphone problem & I gave up on Google's Q/A for an S8, was hoping to go nuts with root & roms, but already at 7.1.2. Don't mind bricking the piece of junk. Everything works BUT using it as a phone. Even speaker phone works, but not regular phone. Ever taken a call from sig-other with only option speaker phone? Yeah... no good. I got 6 months out of it, my S5 lasted me more than 3 years.
[Google Pixel Questions & Answers] :
Ok, I am now completely confused. I booted up Verizon Google Pixel the first time without the SIM card and updated the OS via WiFI (under NJH47D which is outside of Verizon's control and IS supposed to have unlockable bootloader), and have tried several things including factory reset to ensure I do it right this time around - no dice.

I quote; "Que?"
[Google Pixel Questions & Answers] piperx:
The whole key to unlocking the bootloader is NOT to buy a verizon phone

People had months warning before the phone went on sale and now people are regretting it.

Perhaps a lesson learned.
[Google Pixel Questions & Answers] :
I'd hate to say it but almost all new Google Pixel straight from Google store are actually Verizon phones nowadays as Google want to get rid of remaining stock, in preparation of Google Pixel 2, so the argument "Do not buy Verizon phones", while perfectly valid a few months back, no longer hold water. CID Getter will tell you the truth whether it's in fact a Verizon phone.
[Google Pixel Questions & Answers] bobby janow:
You're missing the point. Both phones are identical. The only difference is that Verizon phones are bootloader locked whereas the Google store one is unlockable. The bootloaders are the same, the radios are the same and the software is the same. There is a slight difference in the images lately but I'm not sure, other than some network specific tweaks, what they are. But they are certainly not earth shattering.

Now what is it that makes one unlockable and one not unlockable is beyond me. I still hold to the IMEI belief but it's not been confirmed. CID means absolutely nothing when it comes to bootloader unlock.
[Google Pixel Questions & Answers] piperx:
I would like for you to prove your theory

I call Bull$hit
[Google Pixel Questions & Answers] :
I didn't miss the point - the point is, even the update or SIM check confirmation can actually change bit value in CID tablet - it's how the bootloader works nowadays (it's also so Google can save on remaining resource, so they don't have to go out and make more, only to have way too much leftover Pixel phones upon sales EOL). Would you say I am wrong if I successfully unlock the bootloader on the Google Pixel straight from Verizon with AT&T SIM inserted (I avoid Verizon's crappy factory image because I just don't trust it)?

* EDITED: Calling me bull****? That's rich. I am just surprised that some of you guys just attack me without any explanation whatsoever. Whatever, if it keeps up, I am taking my business elsewhere.
[Google Pixel Questions & Answers] jmartin72:
I believe it is the IMEI as well. I was one of the many that bought a VZW phone originally, and had it RMA'd by Google because of a hardware issue. When it came the bootloader was unlockable, and it showed up on my VZW account website as a NON-Verizon phone. It was this way for several month. Then last month I tried to change my data package online, and it would not let me. I called the VZW support, and told her what I wanted to do, and what was happening to me. She put me on hold, and a few minutes later she told me I was all set. It wasn't until the next day I logged onto the VZW website, and I noticed that my device said Google Pixel instead of NON-Verizon phone. at that point I went to the developer options, and sure enough, the option to unlock the bootloader was grayed out, and has been ever since. I theorize that the support person I talked to added the IMEI from my phone to the their list allowing her to change my plan, and it turn locked my bootloader. I called back a day later, and asked them to put it all back, and they said I would have to call Google. The number they gave me was for Developers, and asked for some number. Without said number the recording would not let you continue. I don't really care about it because I run stock anyway. I don't root anymore since I've owned Nexus, and Pixel phones. I don't feel the need. I just thought it was interesting.
[Google Pixel Questions & Answers] bobby janow:
Man you nailed it. Great post.
[Google Pixel Questions & Answers] TonikJDK:
We went through this in huge detail at the beginning. The CID is just any easy identifier. And sometimes Google messes up and mis-tags them. The lock comes from the IMEI being in a database. And sometimes Google messes that up and a VZ phone is unlockable.

They would have unlocked with a VZ SIM. And they would have unlocked without an update.

We know this because a Google phone won't unlock when you first start it up. It has to connect to get auth'd based on its IMEI.

And that is the deal with these VZ phones where the claim is they unlock with a non VZ SIM after they update with a non-VZ SIM. It isnt the SIM, it isnt the update. It is Google mis tagging them in the database.

And here is the final nail in this claims coffin. If you have an EE phone it is locked both SIM and bootloader until you finish your contract. Then you call EE and they release the phone on their end.

No new SIM, no software update.....blammo it's bootloader is unlocked.

How do you think that is done without an IMEI database?
[Google Pixel Questions & Answers] y2grae:
The EE release is after six months of the contract you can (as I've done it)

The EE release is due solely to it being network locked - as the OEM slider states "cannot unlock network locked device" (or very similar wording)

EE and Verizon are locked out in the same end user way, but by different methods.
[Google Pixel Questions & Answers] TonikJDK:
Great info, appreciate the clarification. Details like this matter while we try and figure this out.
[Google Pixel Questions & Answers] bkdezalia:
Okay, just want to say Thank you to everyone out here and everything they do to help the community! I've read this entire thread and haven't seen my situation...completely that is. I just got a Refurb Pixel 128 Gb, I'm attaching screenshots to show...

It came with 7.1, battery was too low to update, I turned on Developer options, and Auto update...

OEM Unlock slider was grayed out - "Connect to the internet or contact your carrier" (slider is to the left)

This morning I was going to charge it, and dePixel8 to unlock the bootloader...

I powered the phone off, plugged it in, it started to boot up, went back over 5 mins later, phone Auto updated to 7.1.2 "NJH47D", OEM Unlock slider still says the same thing!

According to what folks are saying here I have a VZW phone based on CID and OEM Unlock status....?
[Google Pixel Questions & Answers] alluringreality:
If you've confirmed the phone has a data connection, which I'd expect may be possible due to the OTA update, and you still get this message then I figure the phone cannot be unlocked.

There is also a SKU in small writing on the bottom back of the Pixel, and G-21W4100-021 is a Verizon Pixel (-A, -B, or -C at the end indicates color).
[Google Pixel Questions & Answers] bkdezalia:
Thanks! On the data connection, I haven't put a SIM in it yet as I was trying to avoid the update, but it seems it was already downloaded, and even though I turned off Auto Update, it installed 7.1.2.

On the SKU, from what I can make out, it looks like "G-21W4100-022-A",

Definitely not a -021 !

So what's the explanation for the grayed out OEM Unlock? Run over to a T-Mobile store, have them put a SIM in it, slide the bar to 'unlock', power off, run home and unlock the bootloader?
[Google Pixel Questions & Answers] alluringreality:
Whoops I typed it wrong, and the -21 part is the 32GB Verizon model. G-2PW4100-022-A is the black Verizon 128GB SKU.

I think that's the message they all have until they're connected with a data network. People in this thread have mostly reported that they either used non-Verizon sims or Wi-Fi to get a data connection. I didn't see anything discussed here that wasn't reportedly tried when the phone was new, so I'd side with the people that suggest if the phone unlocks or not probably depends on a database. It's entirely possible I might have missed something, similar to my SKU typing, but I think the thread primarily talks about getting a data connection by something other than a Verizon sim and seeing if the phone allows unlocking the bootloader.
[Google Pixel Questions & Answers] bkdezalia:
Something to note, I have connected to wifi through all of this, so not sure if it takes a SIM to check into whatever 'database'...
[Google Pixel Questions & Answers] :
Having seeing that EE releasing the bootloader lock kind of confirmed to me that the bootloader in Verizon phones can still be unlocked somehow - it's handled by bootloader locker (under the SSD image named "bootlocker.img") meaning IMEI database have nothing to do with it but rather the BIOS ID and carrier provisioning service - I am skimming through some part of bootlocker.img in hex editor (And yes, Google Pixel is actually a HTC phone as some component of bootloader (BIOS) is plastered all over with "HTC Corp" trademark). I flashed on non-Verizon OTA factory image - NJH47F build number, it works just fine here on Verizon phone meaning the BIOS just ignore the software ID at the signature suffix which identify who holds the phone "hostage" - in this case Verizon - only the BIOS ID is what the updater is interested in, and that's it.

And I agree; rooting may be necessary to get the bootlocker utility to let go of its death grip.
[Google Pixel Questions & Answers] :
Yes - bootloader lock is handled by bootlocker.img in Google Pixel factory image which you can find it once you unzip the factory image ZIP file - if we can find a way to exploit this software, we can actually unlock the phone one way or another.
[Google Pixel Questions & Answers] TonikJDK:
You need temp root to do this, that is the hard part. After that it will be easy.