yashsingh1/xdaforums huggingface dataset:
[Google Pixel 2 Questions & Answers] giant22000:
Seems like I heard in the past that even play store pixel devices had to be bootloader unlocked prior to jumping on Verizon's network as it was making devices non bootloader unlockable.

So in other words, if your phone was on the vzw network prior unlocking the bootloader regardless if it is a play store pixel, you might be hosed... rma
[Google Pixel 2 Questions & Answers] owner232:
Having the same issue, I bought this phone and it works on ATT's network but i cannot unlock the bootloader. Kind of strange. oem unlock is greyed out. Ive reset it 10 times. trying after every update connecting to the internet and not from sept 2017 all the way to latest update. nothing changed the adb unlock command just says unable to unlock
[Google Pixel 2 Questions & Answers] munchy_cool:
if you are on Sep 2017 update, dont worry about OEM unlock.

Side load the jan update, and unlock the bootloader.

details here - https://xdaforums.com/pixel-2/how-to/unlock-bootloader-verizon-pixel-2-t3730076

read carefully.
[Google Pixel 2 Questions & Answers] owner232:
Unfortunately I already updated to the latest Version, I contacted the seller i got the phone from they said its a refurbished Verizon phone unlocked for any carrier and it has nothing verizon on the os.

Crap.... Can i at least get root on this thing?
[Google Pixel 2 Questions & Answers] ajrty33:
That's not true.
[Google Pixel 2 Questions & Answers] munchy_cool:
nopes...nothing.
[Google Pixel 2 Questions & Answers] robocuff:
If it's a truly a Google phone, you can put any SIM in it you want to and the unlock slider will be available. Putting a Verizon SIM in it won't lock it down. I've unlocked mine and a couple others for other people. All of them had a Verizon SIM in them at the time and the unlock slider was still available. If it's a Google phone (or supposed to be) and you've already tried factory resetting it, your best bet is to RMA it. Something isn't right with it.
[Google Pixel 2 Questions & Answers] fishsupreme:
I have the same problem - phone unlocked but needed warranty replacement, can't unlock the warranty replacement due to exactly the same behavior where the option is greyed out, and even if I flash an image and turn the option on, I still can't do a fastboot flashing unlock and trying to do so greys out the option again.

However, I am not even on Verizon. I've tried with a T-Mobile SIM and with no SIM. So the Verizon SIM is probably not even the issue.

Google couldn't figure it out and sent me a second warranty replacement phone... which has the same issue.
[Google Pixel 2 Questions & Answers] bartolo5:
Hello there. Experiencing the same issue. It's clearly a software problem. I have a Google Store, non Verizon, and I have RMA'ed it twice and both units CAN't be OEM unlocked. It's clearly a software problem because:

On factory reset OEM unlock options shows up and can be toggled

But when you go to fastboot, issuing 'fastboot flashing unlock' will return an error saying it's not allowed to be unlocked

On the next reboot OEM unlock toggle is now disabled. Only way to get it back is through factory reset with wifi connection, but that brings us back to 1 and the cycle repeats.

I guess it's pointless to RMA the device again. Reading here other people are experiencing the same problem. None of the devices have ever been on Verizon and are straight out from Google Store.
[Google Pixel 2 Questions & Answers] fishsupreme:
Despite it clearly being a software problem, Google is sending me a 4th phone now. It's obvious they don't know what's going on.
[Google Pixel 2 Questions & Answers] bobby janow:
Conspiracy theorist here.. What if you are a guinea pig for the inevitable "bootloader can't be unlocked no matter where you buy it from" that might be coming down the pike? I'd love to see how many people actually unlock their devices these days. So what if they lose those developers and tinkerers? A thousand maybe at the most? Verizon has it nailed down now with no unlock in sight. What if other companies, i.e. ATT, Sprint, want to sell the Pixel 2 or 3 to their corporate clients but can't because the bootloader can be unlocked and that is against company policy? Now Google can say the bl can't be unlocked any longer even if you buy directly from us. I think those thousand users would be dwarfed by one company's purchase alone.

Probably not true but I guess we'll see soon enough. Maybe they actually do know what is going on but are not telling you.
[Google Pixel 2 Questions & Answers] coolsoundingme:
I had to RMA my first Pixel 2 for the USB-C port not working. They sent me a refurbished phone with this problem - there are bug reports on the issue tracker that they're ignoring.

I went through the RMA for this issue, where they sent me another refurbished. Same problem. On the fourth phone now, which they sent new, and it unlocked immediately.

Refurbished won't unlock. New will. Go through the RMA steps until they send you a new one because that's what it takes.
[Google Pixel 2 Questions & Answers] bartolo5:
They are just lazy fixing low priority bugs and like you say few people OEM unlock their devices. There was a problem with the OEM toggle, that they fixed if you factory reset, but they still didn't completely fix the whole thing.
[Google Pixel 2 Questions & Answers] bobby janow:
Yes, I remember that. Right after the phone came out there were a bunch of complaints and they fixed it within a week or two but you had to factory reset. So basically someone has the key to the toggle but they're not letting it out. Gotta be a boat load of corporate money on the line for that one. I'm not sure about the new vs refurb theory though. More examples would be needed to either confirm or deny that.
[Google Pixel 2 Questions & Answers] atxhardrocker23:
Fixing to get a pixel XL 2 from Verizon..sure hope I don't have this issue with unlocking
[Google Pixel 2 Questions & Answers] b00ster23:
Just a quick note about your comments above to get you into the correct location for more detailed information.

1.) Your comments above are referencing an XL version of the phone. Might want to move over to the XL portion of XDA

2.) If you buy a VZW phone...YES, you WILL have issues unlocking. If you want to ensure you can unlock your bootloader, you will want to buy the Google version of the device.

Good luck.
[Google Pixel 2 Questions & Answers] atxhardrocker23:
Sorry about that ..yes did a lot of reading about that..not cool how they not letting you unlock the bootloader..can't get financed through Google tho..ive tried... thanks..
[Google Pixel 2 Questions & Answers] cobrajet7:
Maybe you got yourself a Verizon model
[Google Pixel 2 Questions & Answers] fishsupreme:
This looks to be a problem with the "refurbished" Pixel 2s they send out for warranty replacement. After sending me 3 "refurbished" ones, they now said I qualify for an exception to receive a new phone, and got the new one -- which worked immediately without any problems. Notably, in Developer Options, the "OEM Unlocking" slider is off after a factory reset, not on as on the refurbs.

Also curious: if you do a adb shell getprop ro.boot.cid, you should see VZW__001 on a Verizon phone and 11111111 on a Google phone. My refurbished phones, as well as the new one I just received, all returned 00000000.

The refurbished phones all shipped with a 3/2018 patch date, whereas the new one shipped with a 9/2017 patch date. That might also be part of the issue.
[Google Pixel 2 Questions & Answers] bartolo5:
My google store refurbished phones did have ro.boot.cid=00000000 and still didn't unlock. I think you are onto something saying Google has taken Verizon returns into refurbs but there are doing something wrong with the OEM unlocking
[Google Pixel 2 Questions & Answers] b00ster23:
I was under the same impression as well. It's been a well traveled theory that the toggle for OEM_UNLOCKING on VZW phones are due to the IMEI. If the scenario is that VZW hardware is being used for refurbishing of the PIX2 phones, then I wonder if the IMEI carries over on the system/logic board with refurbished phones? I would think so. This might explain why the support staff are unable to assist. The 'list' of VZW only phones (locked BL) is sealed tighter than....well.....:rolleyes:
[Google Pixel 2 Questions & Answers] bartolo5:
Who knows. Only Google knows, but this directly impacts the resell value of our phones if they can't be OEM unlocked when they should... I'll try to see if Google can send me a brand new one instead of a refurb. So annoying!
[Google Pixel 2 Questions & Answers] bobby janow:
The resale value? For whom, a few XDA users? No one cares about bl unlock any longer and it's going to go away. The resale value is due to it's great support in terms of updates, the camera and the device itself. Don't think that bl unlock will continue for any length of time at this point. Here's an article for you that portends what is coming down the pike. Get used to it, sorry to say.

https://www.androidpolice.com/2018/05/24/huawei-halts-bootloader-unlock-program-indefinitely/
[Google Pixel 2 Questions & Answers] b00ster23:
Agree that it's probably going away... But disagree "no one cares about BL unlock". I care... LOL:p
[Google Pixel 2 Questions & Answers] bobby janow:
Yes, I misspoke a little. I certainly don't mean no one cares, I actually do even though I don't unlock, I just mean there are not enough that care to really matter to Google or the carriers. I would have hoped they could figure out a way to allow us unlock, agree to some weird disclaimer, and then do what we want, ie Google pay etc.

But alas that is not to be. Root allowed full access and bypassing corporate restrictions. I can see their point and I can see ours. Unfortunately they won. We just need to figure out how to live with it.
[Google Pixel 2 Questions & Answers] b00ster23:
I like the idea of a the disclaimer, and voiding warranty. Run at your own risk... Problem is environment control here. When you refer to networks, although someone may have a 'rogue' handset and root, considerations of the effects to the whole network are taken.

In my corporate environment, if root exists on the phone, the MDM automatically detects it and warns you're out of compliance and wipes the phone. BOOM!
[Google Pixel 2 Questions & Answers] bobby janow:
Wow, that's cold. But understandable. With mobile devices now ubiquitous it makes sense that network admins would have very granular control these days. And if a rogue app just so happened to contain a network worm or ransomware then your scenario of a device wipe before that happens is totally appropriate.

Nonetheless, I'd still like the option for my own personal device. I have a VZW Pixel refurb that came bl unlockable with the OEM switch active. I haven't flipped it since the phone is in use still with banking apps and GP. But when the Pixel 3 comes out and my Pixel 2 goes hand me down I will unlock the OG and root it just to play around on wifi. That option does not exist on my current Pixel 2. Just thought of something they could do with the disclaimer. Once you bl unlock you need to agree to warranty voiding and then you can't relock it again. Bet that would make a few people think long and hard.. lol

Quick question. If you unlock, root and a malicious app gets in due to root access, can you then unroot, relock but still have that app on the phone doing damage? If the answer is yes, then I can see why Verizon has it locked down. They need to be able to tell their corporate clients that no device that starts with the letters Pixel can't be rooted.
[Google Pixel 2 Questions & Answers] bartolo5:
So I contacted Google and tried to convince them to send me a NEW replacement straight out of Google to avoid more RMAs, but no dice. They are sending me a refurbished unit again. Maybe I'll get lucky and this third one will be able to be OEM unlocked...

I personally don't have a problem with their refurbished units in general. The ones that they've sent are indistinguishable from a new unit, I've carefully looked for scratches and never been able to find any on the refurbs. They just can't be OEM unlocked.....
[Google Pixel 2 Questions & Answers] bartolo5:
3rd RMA just arrived today and exact same thing. Boot up, turn on OEM unlock in developer settings then:

$ fastboot flashing unlock
...
FAILED (remote: Flashing Unlock is not allowed
)
finished. total time: 0.002s

:(
[Google Pixel 2 Questions & Answers] Snorp09:
I'm having this problem too! It feels super good knowing I'm not alone.
[Google Pixel 2 Questions & Answers] coolsoundingme:
I went through this twice. Immediately contacted support and told them the 2nd refurb phone they sent phone was *ALSO* defective. Expressed that I was very displeased as the person I spoke to in getting this replacement assured me that the refurbs are "fully tested and working" - despite me being pretty sure that another refurb would fail. They elected on the third try to send me a new one.

Moral of the story: You paid for a phone which includes a specific feature. They failed to make good on said feature. Keep sending it back until they get it right. Eventually the cost offset for them is cheaper to send you a brand new one - a cost they would not have to incur if only I could have unlocked the first refurb.
[Google Pixel 2 Questions & Answers] DuckRuckus:
So, after following this thread since it's inception, I decided to pop over to the XL thread. Unless I missed it, this is not an issue with that device, so it's highly unlikely that it is software/firmware based. My thought is that G is either unaware, or denying knowledge that HTC is locking the bootloaders of their refurbs, because of too many RMAs from folks that bricked their devices in an unlocked state. HTC is struggling, as noted in the unimpressive 12+, or whatever it's called. They can't absorb the losses that LG can, so they are covering themselves. Just a thought.
[Google Pixel 2 Questions & Answers] tutech:
I'm currently going through this. My wife's phone microphone failed and quit working so I got an under-warranty refurbished replacement that was physically defective with the volume button cover not attached. The second refurbished warranty replacement cannot be bootloader unlocked, just as in this thread. I've been very disappointed with the warranty service I've received. I'm still waiting on the link to order the third replacement 5 days later. My case has been escalated and it's just further delayed things. I've been insistent that I get a new replacement this time instead of refurbished but I have my doubts that'll happen. I expressed repeatedly that I would gladly PAY for expedited shipping, but that is an impossible task for them. Meanwhile my wife's at 13 days since the issue arose and counting.
[Google Pixel 2 Questions & Answers] ridedalightnin:
Hey everyone. Any latest updates on this? I have another one to add to the pile. I just got my replacement today and to my surprise I had this issue and I am on Project Fi. Then I found this thread. My broken pixel 2 BL unlocks just fine with newest patch. Just has loose charging port. Might just have authorized repair fix it and see if I can send back my replacement and cancel RMA.

---------- Post added at 12:43 AM ---------- Previous post was at 12:33 AM ----------

Well, I tried this command on the pixel2 i am sending back and it came up with all 0000000. I can go in and unlock the bootloader no problem on the newest update. The replacement the sent me, refurbished... Also all 00000000 Flashing Unlock Failed. :eek:
[Google Pixel 2 Questions & Answers] bartolo5:
Any tips on how/what to ask to get a *new* RMA replacement? I did ask on my 3rd that I wanted a new replacement, and google representative assured me that "refurbished device would not have the issue" which of course it did... There's just something about the way Google is refurbishing these units that's making them OEM NOT-unlockable.
[Google Pixel 2 Questions & Answers] okiejtruax:
I think there using more advance algorithms and are able to qauntum entangled programs through there servers to certain devices. Just a guess
[Google Pixel 2 Questions & Answers] bunklung:
Please post ALL your feedback to the issue tracker. Please also star this issue so you get updates:

https://issuetracker.google.com/u/1/issues/73217322
[Google Pixel 2 Questions & Answers] somnambulantdead:
I had a similar problem with a fresh device from Google. I think what actually got it working was to set a password during setup. Because it asks for a password to unlock I guess it just stays greyed out until you set one.
[Google Pixel 2 Questions & Answers] keanon:
Google has no fixes in their issue tracker nor if you call/chat for support. I had to go through 3 RMA devices before they made an exception for me and sent me a brand new piece of hardware to correct the issue.
[Google Pixel 2 Questions & Answers] bartolo5:
"Priority P3 / Severity S3"

If it's like the panorama blurriness issue, which has the same priority and severity, this will never get fixed. Pano bug has been assigned for months and Google hasn't bothered.
[Google Pixel 2 Questions & Answers] allcaps33:
This is getting out of hand...

Glad to know my research efforts won't go unnoticed

P.S. there are several threads related to this:

https://xdaforums.com/pixel-2/help/bought-pixel-2-directly-google-verizon-t3808161

https://xdaforums.com/pixel-2/help/google-pixel-2-july-update-verizon-oem-t3811680

There may be more, but this thread and another are the ones that popped up since I asked pretty much the same question.

Anybody with ideas as to what's going on?

Do we think it's Verizon related, or Google related?

Anyone know how to petition Google so we can get a direct answer
[Google Pixel 2 Questions & Answers] bunklung:
Was this refurbished?

---------- Post added at 08:15 PM ---------- Previous post was at 08:00 PM ----------

This did not work for me.

---------- Post added at 08:18 PM ---------- Previous post was at 08:15 PM ----------

Are you "ke.. [MENTION=5499064]gmail.com[/MENTION]" from the issue tracker? Curious if you are the same person. If so, it sounds like this is a refurbished issue. I have another Pixel 2, but I don't dare try to lock and unlock it again.
[Google Pixel 2 Questions & Answers] allcaps33:
[MENTION=3829405]bunklung[/MENTION]

It doesn't matter if the phone is new or refurbished.

It happens regardless of its initial condition.

I think that it's caused when 2 conditions are met:

1) the phone's bootloader was already unlocked

2) the phone has a Verizon Sim card *in* the phone. Seeing as how there is no validation or signature check, Verizon variants of the firmware are auto downloaded and installed. This is what causes the lockout.
[Google Pixel 2 Questions & Answers] bunklung:
I never placed a Verizon SIM in my phone until after I tried unsuccessfully to unlock three times (factory resets). So I don't think this has anything to do with VZ SIM usage.
[Google Pixel 2 Questions & Answers] allcaps33:
Indeed, I'm going to update my other posts. Further searching has revealed this is not new, actually.

---------- Post added at 08:38 PM ---------- Previous post was at 08:32 PM ----------

I should mention I can only replicate this fiasco with VZW Sims. What carrier were you using?

Perhaps it's the *type* of network Sim?
[Google Pixel 2 Questions & Answers] bunklung:
No sim, I just used Wifi.
[Google Pixel 2 Questions & Answers] somnambulantdead:
Mine was a brand new device. I did update to the June security patch before I finally got it to work. I refused to install my SIM card (which is Verizon) until I managed to get the bootloader unlocked.
[Google Pixel 2 Questions & Answers] crixley:
Canadian, no Verizon sim ever inserted. All RMA phones are having this issue. I'm not sure what they're doing that's causing this.
[Google Pixel 2 Questions & Answers] plgonzalezrx8:
Because they can

Let me put on my tinfoil hat.

But I think something fishy is going on here, not with Google, but with their refurbishing/RMA company, bought a brand new Pixel 2 (extreme solution), to see if it was unlocked, and I was able to unlock it within minutes. However, my RMAed phone (3rd one mind you) is unlockable. I think the RMA company is ****ing over Google and they are not aware of the widespread issue because, lets face it, we are a small group of folks complaining, vs the thousands of happy customers who got a replacement phone in 2 days and it is working as intended (They don't need unlock).
[Google Pixel 2 Questions & Answers] bobby janow:
You might need a little more tin for your hat. What if making the phone not unlockable is not an accident?
[Google Pixel 2 Questions & Answers] crixley:
If you mean by google, they will RMA for it so I highly doubt that would be the case since it would be costing them a decent amount of money. The people I've spoken to from support seem very surprised and almost as if they don't believe it or think it is user error.
[Google Pixel 2 Questions & Answers] bobby janow:
For the sake of argument only.. not entirely sure I subscribe to my own theory but, well here goes. So what if they're testing it out to see exactly how many are returned due to an unlockable bl? Out of 1000 RMAs maybe 5? Even let's say 20 which I think is high but we can go with that. How much will that cost them? Maybe 2 grand? But now they have some stats about how many people actually unlock their bl or wish to. Data mining..

Ok so now with the Pixel 3 or even the 4 they can go to a corporation and say you don't need to get the device from Verizon (although we at Google really like their service lol) but you can buy it at any provider and now even the Google variant is locked down. No bl unlock, no root, corporate secrets and policies stay in effect. And now they sell 1000 devices to 100 corporations. I think that negates the fact of 20 devices that need another RMA or take up a CSRs time who usually has no idea or will not admit it. Then we get frustrated, post on XDA and they data mine that too. It's a win-win for them and a lose-lose for developers and those that want root. </brain cooking with this hat on-off> Whew.. that was scary. I think it kind of compares to Apple and jail breaking. I know of only one person who routinely jail breaks out of all the iPhone users that I've seen. Perhaps Google is trying out that model, i.e. the Notch? lol (picking off the remaining tin foil that stuck to my head)
[Google Pixel 2 Questions & Answers] crixley:
Has anyone tried the method for the verizon pixel 1? I was wondering if that might work for us since we are not with verizon, it would bypass the OEM unlock check I believe. I was thinking about trying it but I don't want to factory reset if someone had already tried unsucessfully
[Google Pixel 2 Questions & Answers] crixley:
Has anyone looked into this app?
[Google Pixel 2 Questions & Answers] crixley:
Actually upon further inspection and snooping, this is the app causing the issues, I'm 99% certain

"com.android.omadm.service"
[Google Pixel 2 Questions & Answers] crixley:
**can't delete message**
[Google Pixel 2 Questions & Answers] crixley:
I have an idea.

Factory reset, do not connect to any network and skip through settings. With adb enabled, delete all possible carrier apps (I have a few that are linked through that app I mentioned), then run the unlock before ever connecting to a network.

---------- Post added at 08:16 PM ---------- Previous post was at 07:27 PM ----------

One more thing I found "Android secret code = 3282 33284”

Haven't been able to figure out how to enter it into the dialer though
[Google Pixel 2 Questions & Answers] k.s.deviate:
I have the same issue, refurbished replacement from Google. The option is available on first boot after factory reset but fastboot command does nothing. After reboot, option is greyed out. Has there been any developement on this? Or am i stuck in their RMA cycle until they wise up and send a new one... Ive reached out to them and requested a new device based on the info provided here and reddit etc.. its been escalated to management but i highly doubt its going to be resolved to my satisfaction..