yashsingh1/xdaforums huggingface dataset:
[Google Pixel Questions & Answers] ItWasAllIntended:
I'm not sure if this is relevent or not but after getting my EE Pixel on 7.1.1 iirc I was unable to unlock bootloader. A few days later a security patch was pushed and after updating the option to unlock bootloader was no longer greyed out and I could unlock through normal means. I'd think this isn't the reason it happened but I tried following the dePixel8 instructions even though I was on 7.1.1 for it to fail. I doubt this is helpful but yeah, that.
[Google Pixel Questions & Answers] mypalmike:
So, this is a random data point that might interest someone.

I bought a Pixel at Target with a Verizon plan (upgrade from existing plan - I've had Verizon for a couple years) with the intent of switching to Project Fi. Target was giving away $200 gift certificates for buying the phone there. I was not aware that there might be a difference in bootloader or I probably would not have bought it. I admit, I did not do my research.

But there may be good news. Even though the phone had been upgraded to 7.1.2, I was able to enable OEM unlocking. It was not greyed out.
[Google Pixel Questions & Answers] :
I decided to put bootlocker.img analysis asides for now (there's no ARM64 disassembly support in most disassemblers.... Except for when you fork over $2,600 for the stupid license in IDA Pro... Argh.), instead focusing on disassembled system APK files to try and find out whose responsibilities of the OEM Unlock toggle and whose is to blame for disabling it.

And... It's tiresome. A lot of XML files....
[Google Pixel Questions & Answers] DroidFanJL:
My original Verizon Pixel broke and was replaced within the warranty. The refurbished Verizon Pixel (based upon model number on the back G-2PW4100-021-A) came with a non-Verizon version of the Factory Image 7.1.2 (NJH47D, Jul 2017) . I booted my phone with a Verizon SIM and used it for over a month and even took the August update (NJH47F non-verizon). The "OEM unlocking" toggle in the Developer Options was not grayed out. I was able to unlock the bootloader and put the OREO Factory image on and then re-locked the bootloader. I have hear of other cases where the replacement device from Verizon did not have the Verizon version and was therefore able to be unlocked.
[Google Pixel Questions & Answers] :
I would strongly recommend to never relock the bootloader if you hold the Verizon SIM card, as the Verizon update will definitely remove the ability to re-unlock the bootloader as a few folks have discovered the hard way.

Locked bootloader creates boatload of security headaches anyways (even if you don't think so right now, wait until Google stops uploading security fixes, which is why the custom ROMs exist in the first place).
[Google Pixel Questions & Answers] Nick80835:
Look at the code and commands used in dePixel8
[Google Pixel Questions & Answers] :
I would look into that, however I wonder if jcase and the others have obfuscated the whole thing just to discourage the others from... Say, have their piece of the pie.

However, the commands therein may no longer be relevant in Android 8.0 Oreo because the whole thing actually change over the time, now with Verizon taking advantage of the remaining Google-only stocks, and reflashing them to their specification (at least it's how Google's getting rid of the remaining Pixel stocks now). Meaning we might have to reinvent the wheel if we're to be successful with the rootless bootloader unlock method, in almost the same manner as the root (I would be surprised if anyone root the Verizon Pixel running Android Oreo within a season, since we're finding new commands we can exploit - and it could potentially lead us closer to the bootloader unlock).
[Google Pixel Questions & Answers] Nick80835:
I mean the commands in dePixel8 to enable unlocking AFTER getting temporary root which is proving difficult.
[Google Pixel Questions & Answers] negativzeroe:
Dude what are you finding for temp root? I've seen nothing.
[Google Pixel Questions & Answers] Nick80835:
There don't seem to be any known exploits that can be used.. Google seriously locked these phones tight.. which I guess is good and bad. :eek:
[Google Pixel Questions & Answers] IM0001:
I can confirm this with a new Replacement Pixel fulfilled through Verizon (Shipped next day from an in-store visit). However you don't even need a SIM card. Just connect to WiFi and wait a minute or two. The toggle went active and I was able to swipe it and ADB Unlock it.

This was also on the NHG47O Verizon ROM out of the Box.

I have always assumed that the Verizon SIM itself was the major curse once it was inserted as if you get the device from Verizon In Store, they either put it in there, or I am guessing if ordered online they come with the SIM Pre Installed in the box? (Not sure, I don't personally have Verizon).
[Google Pixel Questions & Answers] hypnotiqphil:
That's interesting. I just received an RMA Pixel from Google and I wasn't able to unlock it. I popped the Verizon sim out and used my TMobile sim. It was on 7.1.2 and still can't unlock it.
[Google Pixel Questions & Answers] IM0001:
Once you put in the Verizon SIM, it's game over. You have to do the unlock before you put in anything related Verizon.
[Google Pixel Questions & Answers] hypnotiqphil:
Maybe that's where I messed up. I booted it up then popped the Verizon sim out. Oh well. The pixel 2 looks promising and im going to get straight from Google this time
[Google Pixel Questions & Answers] HACK3DANDR0ID:
I had a Verizon Pixel XL i purchased from a Verizon Sales Rep to use with my T-Mobile SIM card. I attempted a factory data reset with the TMO SIM inside on 7.1.2. So then i did the 8.0.0 update with the TMO SIM and still a no go. So then i contacted Google....

I let them know i purchased the phone through a Verizon Sales Rep not knowing this would be an issue. Bottom line, i sent my 32GB Verizon Pixel on this past Friday. I day later i got a tracking number for my return device, 128GB Google Pixel XL.. I should receive the upgraded device on this Tuesday the 17th. We'll see what happens...
[Google Pixel Questions & Answers] PGHammer:
Old Trick (And Why It Works)

This is a variant on a very old trick (that we all mostly use when installing a new (community) ROM - or doing a self-enroll with a phone purchased online - but before actually enrolling the phone with a carrier).

This would, in fact, likely work with a phone purchased in a VZW store as long as it doesn't get unboxed and activated before you leave (either by an associate or by you) - yes; this is not only permissible, but doable - you just need to not be in a rush to get started.

Remember - except in VERY limited cases (so far, the LG Lucid is the ONLY smartphone that even VZW has ever sold to NOT permit this) you can set up your phone sans SIM; this is just as true with smartphones that are exclusive to VZW. (While my S7 is an exclusive-to-VZW model, it has never had a VZW SIM in it since I got it; until I put a Tracfone SIM in it last week, in fact, it has been running SIMless - and that was, in fact, the condition it was in when I set it up. If I purchase a Pixel retail, it would, in fact, likely be from VZW (with in-store pickup), however, I would likely take it to Tracfone (VZW-based MVNO), as they are my current carrier of choice. While Tracfone uses VZW's towers, they don't subscribe to VZW's nitpicks (nor do they charge VZW's prices).
[Google Pixel Questions & Answers] big_bake:
Here's my experience from last night.

my wife's phone is a Pixel XL bought from verizon online back in dec 2016. I used depixel8 back then to unlock the bootloader. phone was great until last week when the earpiece stopped working. Could only make calls with BT or headphones. Go through verizon for warranty and they determine it's defective. They send her a certified like new device.

I boot this thing up with no sim in it (how it ships), pass through setup. It's on 7.1.2 (forgot to catch the build number) and OEM unlocking was greyed out. I then connected it to my wifi. Waited a few minutes, no dice. Then I back out of settings, go back in and OEM unlocking was live. I ticked the switch on. Plugged it in and issued the commands from the OP and was able to unlock the bootloader. I popped the SIM in and then connected the new pixel to the old to set it up. Wife is happy and so am I.

Now hopefully verizon doesn't give me any heartache over shipping them back the defective one with an unlocked bootloader. I could have relocked since it was stock, but didn't want to chance anything.
[Google Pixel Questions & Answers] fzr-r4:
What ro.boot.cid value do you guys get (such as through the CID Getter app)?
[Google Pixel Questions & Answers] spaghettiAlready:
[ro.boot.cid]: [VZW_001]
[Google Pixel Questions & Answers] jakegub:
I received a replacement through Google that is a Verizon version. I made sure to remove the SIM prior to first boot and connected to wifi. The unlock phone option is still grayed out.

Next step for me will be to borrow a Cricket Wireless SIM from a neighbor to see if that changes anything.

It's possible the phone had been previously active. I don't know for sure that it's a new replacement. It came in the retail packaging, but the box wasn't shrink wrapped if I remember correctly. Also my original box wasn't shrink wrapped either, so no way of knowing.
[Google Pixel Questions & Answers] TonikJDK:
The SIM has nothing to do with bootloader unlocking. That is an urban myth here on XDA. If it's a VZ phone and it hasn't unlocked by now it isn't going to.
[Google Pixel Questions & Answers] rc0801:
will cricket sim work?

i have an available cricket sim as they arew now sub att will it work when attempting this initial boot on the pixel?

Tx in advance for your advice!
[Google Pixel Questions & Answers] iluhin:
I do not understand the difficulties and problems in unlocking those people who have 7.1! there is dePixel8 !!! use it!

now ota update (8.1) gives an error after reboot. at the time of the first pre-cut, the recovery version becomes 8.1 can at this point you can unlock oem?
[Google Pixel Questions & Answers] joshw0000:
I've owned about 10 Pixels/XL's and I've checked the unlock option in all of them (buy/sale online). From what I've seen, the Google version won't have the unlock option available until you connect to WiFi or LTE. At that point, the option is no longer grayed out. I've tested the same with multiple Verizon versions and no combination of booting without sim (or with ATT/T-MO/Sprint sim), connecting to WiFi or LTE has ever enabled the unlock option.

This whole thread is just the luck of the draw. My buddy had a Pixel XL with a speaker issue. His was a 32GB Verizon model. He sent it in for a return and Google shipped him a 128GB new Google version, in the box with new accessories. I wouldn't have believed it if he didn't send me pictures. Google is pulling whatever they have available for replacements. I assume the same happens at Verizon for new and/or replacements. If they're out of Verizon models it's better to sell Google models then to announce they're out of stock.

https://photos.app.goo.gl/Wln7OiJM8Az2BJEv2
[Google Pixel Questions & Answers] big_bake:
I believe it's luck of the draw. I just wanted to toss my experience out there since I doubted a "certified like new" device from a verizon warranty claim would be able to be unlocked. So I am to believe that I was shipped a refurb Google version then? It's fine with me.
[Google Pixel Questions & Answers] joshw0000:
It might be a refurb. Or it might be brand new. I believe Google/Verizon is pulling whatever they have available to ship.
[Google Pixel Questions & Answers] big_bake:
very true. The phone looked super clean and arrived with 7.1.2. Had the IMEI and stuff on a sticker on the back of the device. Only wrapped in the factory plastic folding thing. Other than that it was just the shrink wrap cardboard insert holding it. No accessories or factory packaging. Is there a specific part number or someway to identify a Google version vs VZW version?
[Google Pixel Questions & Answers] joshw0000:
Try going to https://www.google.com/android/beta and logging in. Unless you've renamed your device I believe it'll be called a Google Pixel if it's a Google version or just a Pixel if it's Verizon. So far in all of my phone deals I've ended up with one Pixel and one Pixel XL that were unlockable, plus my Verizon Pixel that I unlocked with DePixel8 at release. All of the others were Verizon.

Again, my personal theory. Refer back to the screenshot I posted.
[Google Pixel Questions & Answers] big_bake:
Good call. I went to the link and she had two Google Pixel Xl's listed. One is presumably the first phone that was depixel8ed and sent back last week.
[Google Pixel Questions & Answers] Minh Dao:
Awww,how about factory reset an used Pixel Verizon and then use a different carrier SIM card?
[Google Pixel Questions & Answers] TonikJDK:
SIM card has nothing to do with the bootloader being locked
[Google Pixel Questions & Answers] SoonerLater:
FWIW.... this article https://www.droid-life.com/2017/10/09/which-google-pixel-2-verizon-or-unlocked/ states that for the Pixel

2

and Pixel

2

XL the Verizon version is

unlocked.

Yes, I know that this thread is about the original Pixel and original Pixel XL. Yes, the author of the cited article may be wrong.

Just FYI...

YMMV
[Google Pixel Questions & Answers] roirraW "edor" ehT:
All Verizon phones are SIM unlocked, meaning you can use them with any carrier (if the phone's radio works with the necessary frequencies needed). This isn't the same as bootloader unlock.

Quote from the article:
[Google Pixel Questions & Answers] RustyzDX2:
I was able to unlock before I inserted the SIM card as well. I rooted & completed all of the updates before adding the SIM card. Probably overkill but I did it anyhow. I sideloaded the latest security patch (11/17) as well. No problems so far. My "OEM Unlock" isn't greyed out though; still blue. I won't dare mess with it.

It came new in the box with all of the accessories on 7.1.1. I'm on 8.0.0 now with Magisk.
[Google Pixel Questions & Answers] tigglet:
I have this issue now too.

The developer option for OEM unlock is greyed out on Pixel (1), and says "OEM unlocking" Connect to the Internet or contact your carrier")

I just bought the phone from amazon refurbished, and it implies carrier egnostic gsm unlock.

The phone has never seen a SIMcard, has wifi working, just setup, came on OS 7.1.2. and as far as versions looks the same as the one I got from google a year ago.

adb shell getprop: (with greyed out oem unlock)

[ro.boot.cid]: [VZW__001]

[ro.boot.oem_unlock_support]: [0]

[ro.oem_unlock_supported]: [1]

[sys.oem_unlock_allowed]: [0]

[ro.bootimage.build.fingerprint]: [google/sailfish/sailfish:7.1.2/NHG47Q/4146032:user/release-keys]

[ro.bootloader]: [8996-012001-1704121145]

adb shell getprop: (with my working google device)

[ro.boot.cid]: [11111111]

[ro.bootimage.build.fingerprint]: [google/sailfish/sailfish:7.1.2/NJH47B/4021576:user/release-keys]

[ro.bootloader]: [8996-012001-1704121145]

[ro.boot.oem_unlock_support]: [1]

[ro.oem_unlock_supported]: [1]

trying:

$ adb -d shell setprop ro.oem_unlock_supported 1

$ adb -d shell setprop ro.boot.oem_unlock_support 1

$ adb -d shell sys.oem_unlock_allowed 1

/system/bin/sh: sys.oem_unlock_allowed: not found

[sys.oem_unlock_allowed]: [1]

I assume this is because I don't have root, but I don't know a way around this, and this thread doesn't imply solutions. I'll try a simcard from google fi or other country. Has anyone tried contacting the carrier aka verizon to ask?
[Google Pixel Questions & Answers] TonikJDK:
It is SIM unlocked, but based on your description it is a Verizon version. If it is 7.1.1 or higher you are done, you won't bootloader unlock it. It has nothing to do with SIMs or anything. It is controlled by Google over the internet, it is in their database and allowed to unlock, or it isn't and you can't. The implications in this and other threads that it is SIM related are flat out wrong. And Google just confirmed it by how they fixed the Pixel 2's that wouldn't unlock. They did it all on their end, no software update.

Sorry for the bad news but it is what it is.
[Google Pixel Questions & Answers] nc12683:
A clue?

/vendor/overlay/framework-res__auto_generated_rro.apk
[Google Pixel Questions & Answers] b00ster23:
Just ordered the VZW Pixel from VZW on a Black Friday special ($0) Will look to apply PIXEL8, so long as it is still on 7.1. Will let folks know which version is currently being shipped and if a success. Just in case others wanted to unlock the bootloader on newly ordered Pixels. I currently have 3 in the household and has been a fantastic phone thus far :)

***EDIT***

It appears that VZW is shipping the Pixel's with 7.11 now. Not sure if this was posted anywhere else but wanted to give folks the information just in case they were in hopes of unlocking the new Pixels. Of course with 7.11 that a big NO
[Google Pixel Questions & Answers] abranson:
I had to get a warranty replacement,and it came with 7.1.2. Turned off auto updates, but still updated itself to 8.0. Second phone on Verizon that has updatwd, despite disabling.

---------- Post added at 06:35 PM ---------- Previous post was at 06:30 PM ----------

I prolly should add that the first pixel I had, took an update, yet was on the latest, rebooted, and then screen just flickered. Was able to get to bootloader, but not recovery. If only vzw allowed that oem toggle. Btw, FCC stated that the disabling of that toggle violates the block C law, as it is a built in feature that has been disabled. Verizon don't care
[Google Pixel Questions & Answers] bobby janow:
You're wrong. FCC says nothing of the sort.
[Google Pixel Questions & Answers] abranson:
I never said word for word. https://www.law.cornell.edu/cfr/text/47/27.16

Handset locking portion. FCC agreed with me on it, but it takes 30 + days after submitting a complaint to get it going
[Google Pixel Questions & Answers] bobby janow:
You're confusing things. Mixed metaphors if you will.
[Google Pixel Questions & Answers] TonikJDK:
You are skipping the fine print. That section says except for section b. If you read section b you will see the exception for security and such.

In 30 days you will get a response from VZ that claims that exception. The FCC will accept that exception, and then you can hire a lawyer and go through the formal complaint process, if you have the cash to do that. I hope you do.

You are now going to argue with me that there is no security concern. Don't bother, don't matter what I think (In fact I agree with you), you will need to convince the FCC. And for that you need the formal complaint process which requires a lawyer and years to do.

What you are doing has been tried many times.
[Google Pixel Questions & Answers] abranson:
Now, heres something I just noticed, and it puzzles me....if we look at new pixel model numbers, and I see there are 4 different ones, but I'll just refer to our 5 inch, the one bought straight from the google store, does anyone know that particular model number? I did some looking around, and what i found, and please correct me if I am wrong, but the one from google store and Verizon are same model number. I have a fi sim on the way, but if I were to pop that in, factory reset, network settings reset, and check for updates, I assume the oem unlock toggle will be grey still.I guess what I'm trying to wonder is, how is it determined that it's a Verizon variant, and not Google store one, if model numbers are the same. And now, they went back to a unified image for 8.1, vs 2 different for the same device,
[Google Pixel Questions & Answers] TonikJDK:
Most of us believe it is IMEI driven.

What know for sure is that when it starts up the all phone home to Google, a server we have not seen before. Shortly after that happens the Google version slider is useable.

The 2's were broken at first, no one could not the slider. A few weeks later Goggle said do a factory reset and let it connect and they started working. No software update involved.

So it is clearly database driven off of something in the phone. iMEI makes the most sense to me.
[Google Pixel Questions & Answers] abranson:
I agree. Giving it one last shot with Google calling big red. Rap just said they have to remove the lock on our bootloader, also, and so I am on hold with em, while they get vzw on. I'll update when we get done.
[Google Pixel Questions & Answers] TonikJDK:
Your Google Rep thinks you are talking about SIM lock.
[Google Pixel Questions & Answers] abranson:
No, this one is actually knowledgeable. Told them activated AT&T, T-Mobile and other Sims, and she said she wants to make sure I am referring to bootloader. Said yes. Been on hold since

---------- Post added at 06:10 PM ---------- Previous post was at 05:58 PM ----------

No, this one is actually knowledgeable. Told them activated AT&T, T-Mobile and other Sims, and she said she wants to make sure I am referring to bootloader. Said yes. Been on hold since
[Google Pixel Questions & Answers] abranson:
2 hours of holding, and signal crapped out
[Google Pixel Questions & Answers] bobby janow:
You've been had. Happens to the best of us.
[Google Pixel Questions & Answers] abranson:
I had Wi-Fi calling on, and forgot, and left Wi-Fi...now, according to Google, as of the other day, for Verizon, it IS imei based, and they did shed one hint that nobody else has...tier 2 can't do it, but tier 3, allegedly can...they said Verizon tier 3 has done it to a few already. They think it's a matter of removing the imei from system, since it's a network lock.
[Google Pixel Questions & Answers] bobby janow:
That makes sense but what do you tell them to allow you to unlock the bl? I don't think it's a viable option at this point although I've been surprised before.
[Google Pixel Questions & Answers] abranson:
Told them that I've already had a corrupt update, and was unable to flash the factory firmware, and needed to have it enabled to fix future issues
[Google Pixel Questions & Answers] bobby janow:
Yeah but you're still locked. So what's plan B?
[Google Pixel Questions & Answers] abranson:
Ticket has been submitted to tier 3.. Say give 7 days to get any type of response

---------- Post added at 11:37 PM ---------- Previous post was at 11:25 PM ----------

Oh, that call and ticket was done 2 hours ago...maybe 3. What I'm thinking is, if they purge my imei from the databases, I can prolly factory reset, or even remove sim, and network reset, and then toggle the oem unlock toggle, run fastboot unlock commands and be good. I'll have to update when I have more details. Have my ticket number for tier 3, which is engineering, who are the ones who deal with the imei stuff and the ones who made the patch which rendered dePixel8 No good anymore. They have made it happen for a few users, who managed to get the info out of Google. On 12/7, a Google super informed me that vzw tier 3 is the one to do this, and they don't tell anyone. Only reason I was apparently told was because I got irate and threatened a lawsuit. Confirmed what Google said with vzw tier 2, and so they created ticket. If enough people call to have tier 3 tickets made, they may be forced to make a new patch to enable, since they are now the only carrier to keep it locked down. Ee makes users pay after 6 months, and confirms on their site, but Verizon refuses. So, enough threats, and they may just enable for all...THE ONLY ONE THAT STILL HAS OEM UNLOCKING GREYED OUT. HOW'S THAT FOR MONOPOLIZING?
[Google Pixel Questions & Answers] abranson:
This was an email with what one Google rep was told in November by vzw. He told me what he was told Verizon's reason for locking bootloader was...that's their reason, but the other Verizon phones can be rooted. Where is the logic?
[Google Pixel Questions & Answers] bobby janow:
Until I see Verizon release their device to a few users I'm skeptical. Blowing smoke.. they might be having a chuckle at your expense as well. Grain of salt at this point.
[Google Pixel Questions & Answers] abranson:
Probable, but if it is done, it'll be nice. I'll have to update when I know