Database Info

Wrong build?

So I was helping a friend with his Pixel he bought from the Google Store. He wanted to install the new update. However, when I took a look at his build number, it was NDE63X not NDE63V. I remind you that he bought his phone directly from Google and not from Verizon. I do remember that when he set it up and put his Verizon sim in, he had to uninstall a couple Verizon apps. Could this have anything to do with him being on the wrong build? Also how can I get him off the Verizon build? Can I just sideload the NDE63V OTA or do I have to use a factory image?

The November update sent X to google store phones if they had a Verizon sim in them.
Same thing here, play store device but on Verizon, when the OTA pushed it was X.

atlp99 said:
The November update sent X to google store phones if they had a Verizon sim in them.
Same thing here, play store device but on Verizon, when the OTA pushed it was X.
Click to expand...
Click to collapse
If we bought a phone from Google, have a Verizon sim, and are on build nde63x, can we and should we push a different build? Also, can we push the new build?

kenjoma said:
If we bought a phone from Google, have a Verizon sim, and are on build nde63x, can we and should we push a different build? Also, can we push the new build?
Click to expand...
Click to collapse
You can flash another build, but there isn't a reason to. Only reason I can think is relevant right now is you want to get to the new ota that got pushed to Canadian phones for the new features. In that case you would need to move to the nde63v build, then sideload ota. If you're not doing that, then there is no reason.
If you are concerned with the "Verizon Pixel vs Google Pixel" discussion, then you have bought into the internet hype. Tsst. Your Google store Pixel is identical to a Verizon Pixel. There is a server side whitelist / blacklist that gives users the ability to toggle oem unlock or not(based on CID I think). That is all. Firmware (nde63x vs nde63v) is independent of where you bought the phone from or whether you can unlock your bootloader. Nde63x likely has some minor changes in it that Verizon and Google think will work better on their network (wifi calling changes, advanced calling tweaks, or something else). Pop a ATT or Tmobile sim in your phone and you will eventually be prompted to update to the unlocked build. Pop your VZW sim back in and it will try to go back. No big deal.

I have a bl unlocked Verizon Pixel, flashed the V build over P, then sideloaded the Canadian J build just for the new features. Now I'm on J with root and unlocked bl on Verizon. . So yeah, you can do whatever you want.

dbrohrer said:
You can flash another build, but there isn't a reason to. Only reason I can think is relevant right now is you want to get to the new ota that got pushed to Canadian phones for the new features. In that case you would need to move to the nde63v build, then sideload ota. If you're not doing that, then there is no reason.
If you are concerned with the "Verizon Pixel vs Google Pixel" discussion, then you have bought into the internet hype. Tsst. Your Google store Pixel is identical to a Verizon Pixel. There is a server side whitelist / blacklist that gives users the ability to toggle oem unlock or not(based on CID I think). That is all. Firmware (nde63x vs nde63v) is independent of where you bought the phone from or whether you can unlock your bootloader. Nde63x likely has some minor changes in it that Verizon and Google think will work better on their network (wifi calling changes, advanced calling tweaks, or something else). Pop a ATT or Tmobile sim in your phone and you will eventually be prompted to update to the unlocked build. Pop your VZW sim back in and it will try to go back. No big deal.
Click to expand...
Click to collapse
So just to be clear (cause I don't wanna **** up my friend's phone) I can side load the NDE63v OTA on the NDE63x pixel? Or do I have to use some other method?

FrostedWaffle said:
So just to be clear (cause I don't wanna **** up my friend's phone) I can side load the NDE63v OTA on the NDE63x pixel? Or do I have to use some other method?
Click to expand...
Click to collapse
No. I haven't tried it myself but others reported side loading 63v from 63x errors out. YMMV on that. The otas that are available are good for moving from a certain build to another. Not any build to 63v. I don't think you can get the ota that takes you from 63x to 63v.
If it was my friends phone, I would flash the factory image if you want to move to the other build. Edit the flash all script so it doesn't wipe data if he wants to keep apps and settings.

dbrohrer said:
No. I haven't tried it myself but others reported side loading 63v from 63x errors out. YMMV on that. The otas that are available are good for moving from a certain build to another. Not any build to 63v. I don't think you can get the ota that takes you from 63x to 63v.
If it was my friends phone, I would flash the factory image if you want to move to the other build. Edit the flash all script so it doesn't wipe data if he wants to keep apps and settings.
Click to expand...
Click to collapse
OK thank you I will try that.

How to update your system if you're not using the carrier from your S8(+) version.

This tutorial is for you who bought a carrier S8(+) and is using a SIM from another carrier and, because of that, not being able to update your system through your phones.
Error: "Service Unavailable: Sorry, we are having trouble authenticating your device. Try again later"
So, that's actually pretty easy to do, but a PC (or Mac) will be necessary.
The only thing you have to do is to download Smart Switch from Samsung on your PC and sync it with your device.
After you've done that, Smart Switch is gonna show the option to update your system.
PS: Beware it takes a while to download the update, at least if your S8(+) is from VZW.
Download links (Samsung.com):
PC: Click here
Mac: Click here
Hope I could help those who were having this problem!

I am using vzw GS8 on att and I get OTA just fine. I don't understand why this is a concern

Whanksta said:
I am using vzw GS8 on att and I get OTA just fine. I don't understand why this is a concern
Click to expand...
Click to collapse
Many people are getting this error.

Alvincp said:
Many people are getting this error.
Click to expand...
Click to collapse
Yup, same error I was getting. Thanks for sharing this!

Thanks for the post, I was having the same issue. I wonder though, if it's possible to configure an S8 to get OTA updates despite this issue. This is probably a question for Verizon support, huh?

Thanks for the post, I was having the same issue. I wonder though, if it's possible to configure an S8 to get OTA updates despite this issue. This is probably a question for Verizon support, huh?
Click to expand...
Click to collapse
I'm guessing you have to flash the firmware to a different carrier however according to the other thread it's not possible yet: https://forum.xda-developers.com/showpost.php?p=72031437&postcount=75
I brought Verizon version on Ebay but I'm using it on Cricket network. I get the OTA error and I'm currently trying to update via Smart Switch.

Whanksta said:
I am using vzw GS8 on att and I get OTA just fine. I don't understand why this is a concern
Click to expand...
Click to collapse
You're using a vzw version on att? Any idea if that would work the other way around? Like a gsm version on cdma?
Sent from my LG-H918 using XDA-Developers Legacy app

steven1193 said:
You're using a vzw version on att? Any idea if that would work the other way around? Like a gsm version on cdma?
Click to expand...
Click to collapse
No, Verizon phones are carrier unlocked out of the box.

Whanksta said:
No, Verizon phones are carrier unlocked out of the box.
Click to expand...
Click to collapse
Even if its unlocked? I'm trying to use an tmobile one on verizon. Sorry if the answer is still the same and I'm wasting your time.

Benzillah said:
Thanks for the post, I was having the same issue. I wonder though, if it's possible to configure an S8 to get OTA updates despite this issue. This is probably a question for Verizon support, huh?
Click to expand...
Click to collapse
The reason people are seeing the error is because the phone is not activated through Verizon , so it is not in their server if you call it. another easy way to get OTA updates is to borrow a verizon sim from a friend, or even start a simple cheapest prepay plan. activate the phone with the sim, then everything will be ok, unless you wipe the phone. Friend of mine ,and myself tried on both his s8 and my s8+ , no problem at all.
we both are on ATT.

Alvincp said:
This tutorial is for you who bought a carrier S8(+) and is using a SIM from another carrier and, because of that, not being able to update your system through your phones.
Error: "Service Unavailable: Sorry, we are having trouble authenticating your device. Try again later"
So, that's actually pretty easy to do, but a PC (or Mac) will be necessary.
The only thing you have to do is to download Smart Switch from Samsung on your PC and sync it with your device.
After you've done that, Smart Switch is gonna show the option to update your system.
PS: Beware it takes a while to download the update, at least if your S8(+) is from VZW.
Download links (Samsung.com):
PC: Click here
Mac: Click here
Hope I could help those who were having this problem!
Click to expand...
Click to collapse
Will this change the model number so I can download different ROMs, after I get it unlocked? For example if I want a ROM that's popular for the verizon model, but I'm using the Tmo model? I think Tmo makes you wait a month after activating a device on their network before you're allowed to unlock it.

babyzone2 said:
The reason people are seeing the error is because the phone is not activated through Verizon , so it is not in their server if you call it. another easy way to get OTA updates is to borrow a verizon sim from a friend, or even start a simple cheapest prepay plan. activate the phone with the sim, then everything will be ok, unless you wipe the phone. Friend of mine ,and myself tried on both his s8 and my s8+ , no problem at all.
we both are on ATT.
Click to expand...
Click to collapse
Just to make sure I get this straight once the phone is activated with a Verizon SIM card you can take the Verizon SIM card out, put back ATT sim card, and the phone will still get OTA updates even with the ATT SIM card inside?

hoxbox said:
Just to make sure I get this straight once the phone is activated with a Verizon SIM card you can take the Verizon SIM card out, put back ATT sim card, and the phone will still get OTA updates even with the ATT SIM card inside?
Click to expand...
Click to collapse
Yes, that's it. In fact I tried with the Verizon Sim, no Sim, att Sim. All work fine. I have a friend also has a galaxy s8, borrowed a Verizon Sim, activated , removed Sim, att Sim work like a charm with OTA. There are two draw back for using the Verizon phone with Sim from other carriers. No OTA updates unless phone is activated through Verizon, especially for those use the phone over sea. 2nd, no full LTE performance due to lack of band used by your own carrier. For example, band 17 from AT&T, the Verizon phone doesn't have that . Your LTE works, but you likely have lower performance on LTE depends on your location. Verizon phone are unlocked and compatible with other GSM carriers , but not fully optimized.

info
steven1193 said:
Even if its unlocked? I'm trying to use an tmobile one on verizon. Sorry if the answer is still the same and I'm wasting your time.
Click to expand...
Click to collapse
If your tmobile version is unlocked it will work on Verizon

babyzone2 said:
Yes, that's it. In fact I tried with the Verizon Sim, no Sim, att Sim. All work fine. I have a friend also has a galaxy s8, borrowed a Verizon Sim, activated , removed Sim, att Sim work like a charm with OTA. There are two draw back for using the Verizon phone with Sim from other carriers. No OTA updates unless phone is activated through Verizon, especially for those use the phone over sea. 2nd, no full LTE performance due to lack of band used by your own carrier. For example, band 17 from AT&T, the Verizon phone doesn't have that . Your LTE works, but you likely have lower performance on LTE depends on your location. Verizon phone are unlocked and compatible with other GSM carriers , but not fully optimized.
Click to expand...
Click to collapse
Thanks for the info. This should work even with prepaid. I'm thinking about getting: https://www.walmart.com/ip/Verizon-BYOD-4FF-SIM-Card-Kit/40716598 and then activate it. I just hope Verizon doesn't deactivate your phone once the prepaid time is up lol.

hoxbox said:
Thanks for the info. This should work even with prepaid. I'm thinking about getting: https://www.walmart.com/ip/Verizon-BYOD-4FF-SIM-Card-Kit/40716598 and then activate it. I just hope Verizon doesn't deactivate your phone once the prepaid time is up lol.
Click to expand...
Click to collapse
I think you should just borrow a sim from a friend or family , no need to spend the money and there is no impact what so ever to their service.

I was able to update an S8 by simply removing the SIM and running it with no SIM. Not sure if that'll work for other people, I had to tap 'check for updates' a few times before it went through.

A_Car said:
I was able to update an S8 by simply removing the SIM and running it with no SIM. Not sure if that'll work for other people, I had to tap 'check for updates' a few times before it went through.
Click to expand...
Click to collapse
I just did this on my Galaxy S7, and it fixed the issue, and was able to download the latest system update for Android. I was using an AT&T SIM card.
I did have to restart my phone after I removed the AT&T SIM card though, just telling what I did.

Thanks for posting this man!

you all could just go here http://updato.com/firmware-archive-select-model?q=sm-g950t&exact=1&r=TMB&v=&rpp=100 download which firmware you want. flash in odin and enjoy new update. this will work every time without problems and it does not care who your provider is at all.

Bootloader unlock on NEW Verizon Pixels

Hey everyone,
I wanted to share a bit of a test that I just did on three Verizon Pixels. Specifically, when I got them from Verizon I did so via direct fulfillment (not a retail store). Doing this method I was able to boot loader unlock all three Verizon Pixels out of the box. The last one was about five minutes ago.
Here's what you'll need:
A new, in box Verizon Pixel - Important: Must be new in box!
A non-Verizon SIM card.
A Laptop
So, here's the rub. With these tests I was able to confirm that the Pixel does in fact use the SIM inserted into the phone at initial boot to determine boot loader lock ability. Long story short, if the Pixel is booted the first time with a Verizon SIM then the phone will be boot loader locked, and the OEM Unlock Toggle grayed out.
To unlock each of them I did the following:
Take the phone out of the box and inserted a co-workers AT&T SIM.
Booted the phone for the first time, and skipped all of the setup steps.
Enabled Developer Options, USB Debugging, and OEM Unlocking.
Accepted the RSA key and issues the command "adb reboot bootloader".
In bootloader mode issued the command "fastboot oem unlocking".
Flashed TWRP, and root.
Profit
The key to success here is ensuring the phone never gets booted initially with a VZW SIM inserted. This isn't so much phone hack as really a life/policy/process hack. Hope this helps!

Update: I've talked to a few knowledgeable folks on the topic who think the phones I got may have been part of a batch that wasn't loaded correctly. Having said that, Im sharing my experiences and would be curious to see what everyone else's experiences are. I'd also be curious to see the following, if anyone wants to try:
Place a non VZW SIM in the phone, factory default it, and see if its enabled again.
Take a brand new out of box VZW phone and ensure it doesn't connect to ANY network, rather it be wifi or Cell. See if OEM unlock is enabled.
Also, another added benefit is that the phones don't auto-download the few Verizon turdware apps.

Interesting...

Can confirm this works, my Google Pixel Verizon arrived yesterday as an RMA and I followed similar steps to unlock my Bootloader, although you can simply boot the phone without a SIM Card and these instructions will work the same.

deadlydecision said:
Can confirm this works, my Google Pixel Verizon arrived yesterday as an RMA and I followed similar steps to unlock my Bootloader, although you can simply boot the phone without a SIM Card and these instructions will work the same.
Click to expand...
Click to collapse
I have questions, the devil is in the details. Just trying to nail it down.
What version was it on when you got it?
Did you hook it to wifi for a few minutes and try the slider before it updated?

deadlydecision said:
Can confirm this works, my Google Pixel Verizon arrived yesterday as an RMA and I followed similar steps to unlock my Bootloader, although you can simply boot the phone without a SIM Card and these instructions will work the same.
Click to expand...
Click to collapse
Definitely did NOT work for my RMA from verizon, so this isn't a certain method.

TonikJDK said:
I have questions, the devil is in the details. Just trying to nail it down.
What version was it on when you got it?
Did you hook it to wifi for a few minutes and try the slider before it updated?
Click to expand...
Click to collapse
7.1. October version. Had to hook it up to Wi-fi to enable the OEM Unlock option, but I didn't allow the phone to update at all.
JAYNO20 said:
Definitely did NOT work for my RMA from verizon, so this isn't a certain method.
Click to expand...
Click to collapse
It was an RMA directly through Google, they just provided me with a NEW Verizon edition Pixel.

deadlydecision said:
7.1. October version. Had to hook it up to Wi-fi to enable the OEM Unlock option, but I didn't allow the phone to update at all.
It was an RMA directly through Google, they just provided me with a NEW Verizon edition Pixel.
Click to expand...
Click to collapse
I did the same thing with an RMA through Google after the Verizon one was a bust and got a BRAND NEW GOOGLE version of the Pixel so it was definitely unlockable. Are you sure your's was a Verizon version? Check your my verizon account and see if it shows it as a "NON-VZW Device." That's what mine shows as because it is actually a Google version.

deadlydecision said:
7.1. October version. Had to hook it up to Wi-fi to enable the OEM Unlock option, but I didn't allow the phone to update at all.
It was an RMA directly through Google, they just provided me with a NEW Verizon edition Pixel.
Click to expand...
Click to collapse
So it didnt get entered in the database properly as a locked phone. Or Google is so far behind they are just shipping what they can.This happens rather often and is not part of what the OP is saying.
Congrats, I am happy for you and TYVM for clearing it up.

TonikJDK said:
So it didnt get entered in the database properly as a locked phone. Or Google is so far behind they are just shipping what they can.This happens rather often and is not part of what the OP is saying.
Congrats, I am happy for you and TYVM for clearing it up.
Click to expand...
Click to collapse
What if you take a Google version, put in a VZW sim, connect, update. With it be grayed out? I doubt it.
Sent from my Pixel using XDA-Developers Legacy app

JAYNO20 said:
I did the same thing with an RMA through Google after the Verizon one was a bust and got a BRAND NEW GOOGLE version of the Pixel so it was definitely unlockable. Are you sure your's was a Verizon version? Check your my verizon account and see if it shows it as a "NON-VZW Device." That's what mine shows as because it is actually a Google version.
Click to expand...
Click to collapse
Definitely a Verizon version as it came with a pre-installed Verizon sim, which I removed before booting. Phone box also says the model is "g-2pw4100-021-b" which AFAIK is a Verizon one.

TonikJDK said:
I have questions, the devil is in the details. Just trying to nail it down.
What version was it on when you got it?
Did you hook it to wifi for a few minutes and try the slider before it updated?
Click to expand...
Click to collapse
It seems like the trick is to catch it BEFORE it ever gets Internet. When it comes online the first time it "phones home" and checks the IMEI blacklist. I think for this to work, most often, it needs to have never been connected to the Internet.

JAYNO20 said:
Definitely did NOT work for my RMA from verizon, so this isn't a certain method.
Click to expand...
Click to collapse
Had your phone by chance ever gotten connected to the Internet? As in, did you boot it with the VZW SIM?

TCPDump said:
It seems like the trick is to catch it BEFORE it ever gets Internet. When it comes online the first time it "phones home" and checks the IMEI blacklist. I think for this to work, most often, it needs to have never been connected to the Internet.
Click to expand...
Click to collapse
Its the other way around. It is grayed out until you connect and it finds out it is authorized to unlock. It isn't a blacklist, its a whitelist of sorts.
Thats why the ones you updates unlocked. It wasn't the update, it was the connection while it pulled the update. I am very sure of this. Seen a ton of VZ phones that can be unlocked the last couple of months. Their system is falling apart.
Early on we went through a ton of scenerios paying attention to when and how it became slidable.
This is the only explanation for what we have seen.

TonikJDK said:
Its the other way around. It is grayed out until you connect and it finds out it is authorized to unlock. It isn't a blacklist, its a whitelist of sorts.
Thats why the ones you updates unlocked. It wasn't the update, it was the connection while it pulled the update. I am very sure of this. Seen a ton of VZ phones that can be unlocked the last couple of months. Their system is falling apart.
Early on we went through a ton of scenerios paying attention to when and how it became slidable.
This is the only explanation for what we have seen.
Click to expand...
Click to collapse
I actually wondered if it was the fact that Google is EOLing them, and trying to eradicate their stockpile of VZW Pixels.

TCPDump said:
I actually wondered if it was the fact that Google is EOLing them, and trying to eradicate their stockpile of VZW Pixels.
Click to expand...
Click to collapse
Either way, long story short - Always check your pixel.

TCPDump said:
I actually wondered if it was the fact that Google is EOLing them, and trying to eradicate their stockpile of VZW Pixels.
Click to expand...
Click to collapse
Excellent thought. Maybe they are tired of VZ's too and are faking all these mistakes. That would be cool.
But yea, with the 2 comming this fall maybe they night be getting​ nervous.

TCPDump said:
Had your phone by chance ever gotten connected to the Internet? As in, did you boot it with the VZW SIM?
Click to expand...
Click to collapse
Nope. Pulled the Sim before boot.

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.

deadlydecision said:
Definitely a Verizon version as it came with a pre-installed Verizon sim, which I removed before booting. Phone box also says the model is "g-2pw4100-021-b" which AFAIK is a Verizon one.
Click to expand...
Click to collapse
What does it say on your my Verizon account?

google pixel on verizon won't OTA???

Was with ATT, no issues updating. Went over to Verizon Pre-paid. Phone will not OTA. Have spent 6 hours on phone with Verizon and google, nobody can figure it out. Not rooted, ever. We removed sim, no OTA. Wiped Network settings, nope. Safe boot, nope, factory reset, nope. My nexus 6p with "no carrier" (wifi calling only) updating perfect, my wife's 5x on cricket updating perfect, but not the pixel. Refuses ever since put on Verizon.
My theory is since Verizon sells a pixel, Google knocked me off OTA thinking Verizon supports it. Verizon says they didn't sell it, unlocked, so they won't push updates. Getting nowhere.
Anyone have thoughts or experience doing this same thing?

What about pulling the SIM and manually check for updates via wireless? If that fails you could also ADB sideload it.
https://developers.google.com/android/ota
Or flash the whole image if you arw unlocked.

Sideload it. Then you'll get next months OTA.
Sent from my Pixel using XDA-Developers Legacy app

bobby janow said:
Sideload it. Then you'll get next months OTA.
Sent from my Pixel using XDA-Developers Legacy app
Click to expand...
Click to collapse
This will work.
Sent from my Pixel using Tapatalk

Side load may work. Will try it "next" time. After 2 mores hours with Google and Verizon, new sims, No sims, reboots... Google is sending a new phone. REally strange only started when put Verizon pre-paid sim in.

MLT2004 said:
Side load may work. Will try it "next" time. After 2 mores hours with Google and Verizon, new sims, No sims, reboots... Google is sending a new phone. REally strange only started when put Verizon pre-paid sim in.
Click to expand...
Click to collapse
They are sending you a refurbished phone. If you like your original device why not sideload the OTA now before you replace it. You can return the refurb if the ota sideload works. Seems to me like you had a very nice working Pixel until you didn't get one security update. Throwing the baby out with the bathwater? Just an opinion, do as you feel necessary.

Well, it also refused Oreo 8 update, and some other minor issues, and yea, I want to keep it, but my phone is watched/tracked by my broker-dealer (securities licensed) and I am forbidden to side load or root. This is to protect Clients. real bummer. Equifax has no repercussions, but I'm so locked down on cell phones and computers you can't believe it.

MLT2004 said:
Well, it also refused Oreo 8 update, and some other minor issues, and yea, I want to keep it, but my phone is watched/tracked by my broker-dealer (securities licensed) and I am forbidden to side load or root. This is to protect Clients. real bummer. Equifax has no repercussions, but I'm so locked down on cell phones and computers you can't believe it.
Click to expand...
Click to collapse
Oh, that's another story then. So they pay for your phone, usage and any replacements? Might be time to get a personal device with your own phone number. I'd never trust that kind of stuff. So when you get another device then they won't want to track that one? Didn't you say that it was on ATT and everything including updates was working fine? I think I'm missing some of the story. Either way, good luck with the replacement.

bobby janow said:
Oh, that's another story then. So they pay for your phone, usage and any replacements? Might be time to get a personal device with your own phone number. I'd never trust that kind of stuff. So when you get another device then they won't want to track that one? Didn't you say that it was on ATT and everything including updates was working fine? I think I'm missing some of the story. Either way, good luck with the replacement.
Click to expand...
Click to collapse
I'm an independent and pay 100% for all expenses. I loose my ability to do business if I don't let them control my electronics. I have a nexus 6p for personal on ATT, updates perfect. I wanted to move all svc to Verizon since I travel a lot to areas ATT has no coverage.

Got ya. Let them control the 6p and keep the Pixel pristine! Lol. Hope it works out for you. Curious, let us know.
Sent from my Pixel using XDA-Developers Legacy app

MLT2004 said:
Well, it also refused Oreo 8 update, and some other minor issues, and yea, I want to keep it, but my phone is watched/tracked by my broker-dealer (securities licensed) and I am forbidden to side load or root. This is to protect Clients. real bummer. Equifax has no repercussions, but I'm so locked down on cell phones and computers you can't believe it.
Click to expand...
Click to collapse
I had a very similar situation...I am on VZW and regularly got OTAs until about 6 months ago then they stopped. I also use a SIM from Project FI when I travel abroad. Somehow switching between the two caused OTAs to be ignored. My device is unrooted, bootloader locked and for corporate security purposes we have Aiwatch Agent to monitor violations. I am able to sideload via ADB and it is quite easy....it is definitely not the security risk that flashing a ROM is on an unlocked phone. Might be worth a shot.
Weirdly, OTAs came back to me after I registered for the O beta. Good luck.

OEM Unlocking Grayed out on non-VZW Pixel 2.

Hi!
I originally bought an unlocked phone from Google and I had zero issues unlocking the bootloader, rooting, etc. I was issued a warranty replacement for an unrelated issue.
I inserted my VZW sim and booted up this new phone. I was able to check the OEM unlocking slider and enter my pin. When I rebooted to fastboot and tried to unlock, I was unsuccessful. Booting back into android showed the OEM unlocking option grayed out.
What gives? What can I try?
Thanks!
*Edit: Also worth noting - If I do a factory reset, the OEM unlocking option will be enabled already. If you try to unlock it in fastboot, it will fail. Rebooting again results in it being grayed out again.

What build number are you on?

DuckRuckus said:
What build number are you on?
Click to expand...
Click to collapse
I'm on OPM2.171019.029

mtpease said:
I'm on OPM2.171019.029
Click to expand...
Click to collapse
So, it came with the latest build then, or did you update via OTA?
Something to try: factory reset, turn it off, remove the SIM card, and give it another shot without connecting to wifi and skipping all the setup stuff. It's a long shot, but worth a try.

DuckRuckus said:
So, it came with the latest build then, or did you update via OTA?
Something to try: factory reset, turn it off, remove the SIM card, and give it another shot without connecting to wifi and skipping all the setup stuff. It's a long shot, but worth a try.
Click to expand...
Click to collapse
It came with something older, but it wasn't working with that either.
I tried the factory reset thing with no sim, but still on WiFi. The settings app kept crashung.
It seems like the VZW sim somehow permenantly locked my phone. I've done like 5 resets, and sometimes the OEM unlock slider is already off, sometimes it lets me toggle it back and forth. No matter what happens, after running the fastboot command (and failing), it will be grayed out. Rinse and repeat.

Have you called google with your IMEI number to confirm that it isn't a Verizon phone?
I just returned an Amazon refurbished Pixel 2 for this reason. They claimed it was factory unlocked, but I contacted Google who informed me that it was actually a Verizon phone that had probably had been unlocked for different carriers during the refurbishing process. I am exchanging it for another. They are not able to check the phone before it is delivered to me, so I am just going to hope I get a non-Verizon one this time or try the exploit mentioned on the forums immediately before connecting to WiFi or Cellular data.

mtpease said:
It came with something older, but it wasn't working with that either.
I tried the factory reset thing with no sim, but still on WiFi. The settings app kept crashung.
It seems like the VZW sim somehow permenantly locked my phone. I've done like 5 resets, and sometimes the OEM unlock slider is already off, sometimes it lets me toggle it back and forth. No matter what happens, after running the fastboot command (and failing), it will be grayed out. Rinse and repeat.
Click to expand...
Click to collapse
The only other thing I can suggest is to sideload that same build's OTA without the SIM in. That might get rid of any changes that the Verizon SIM may have made, as it will format everything before it installs. If that works, do everything you want to (root, recovery, kernel) before putting the SIM back in. That's all I can think of doing.
---------- Post added at 10:56 PM ---------- Previous post was at 10:19 PM ----------
joelphilippage said:
Have you called google with your IMEI number to confirm that it isn't a Verizon phone?
I just returned an Amazon refurbished Pixel 2 for this reason. They claimed it was factory unlocked, but I contacted Google who informed me that it was actually a Verizon phone that had probably had been unlocked for different carriers during the refurbishing process. I am exchanging it for another. They are not able to check the phone before it is delivered to me, so I am just going to hope I get a non-Verizon one this time or try the exploit mentioned on the forums immediately before connecting to WiFi or Cellular data.
Click to expand...
Click to collapse
All of Verizon's phones are carrier unlocked from the factory, and have been for quite some time. But, as far as being bl unlockable, that's a whole nother animal. Definitely good advice to check the IMEI with Google. Verizon can also do that for you, and it might be faster. I thought of that too, but it was my understanding that warranty claims we're filled with brand new units, but repairs potentially got you a refurbished one, so I ruled that out. I've been wrong before :silly:

DuckRuckus said:
The only other thing I can suggest is to sideload that same build's OTA without the SIM in. That might get rid of any changes that the Verizon SIM may have made, as it will format everything before it installs. If that works, do everything you want to (root, recovery, kernel) before putting the SIM back in. That's all I can think of doing.
---------- Post added at 10:56 PM ---------- Previous post was at 10:19 PM ----------
All of Verizon's phones are carrier unlocked from the factory, and have been for quite some time. But, as far as being bl unlockable, that's a whole nother animal. Definitely good advice to check the IMEI with Google. Verizon can also do that for you, and it might be faster. I thought of that too, but it was my understanding that warranty claims we're filled with brand new units, but repairs potentially got you a refurbished one, so I ruled that out. I've been wrong before :silly:
Click to expand...
Click to collapse
I opened a chat window with Google, and they confirmed that it is in fact an unlocked device. He also had me "screen share" so he could see the problem. So far, no resolution. I sideloaded the current OTA twice, to make sure it was in the a and b slots. Then I tried setting up the phone without a sim or wifi, which didn't work. I also tried wifi with no sim, that didn't work either.
If I try the fastboot flashing unlock command, when I boot up, the OEM unlocking option will be grayed out. Any time I boot up from a factory reset, the OEM unlocking option is already selected on.

mtpease said:
I opened a chat window with Google, and they confirmed that it is in fact an unlocked device. He also had me "screen share" so he could see the problem. So far, no resolution. I sideloaded the current OTA twice, to make sure it was in the a and b slots. Then I tried setting up the phone without a sim or wifi, which didn't work. I also tried wifi with no sim, that didn't work either.
If I try the fastboot flashing unlock command, when I boot up, the OEM unlocking option will be grayed out. Any time I boot up from a factory reset, the OEM unlocking option is already selected on.
Click to expand...
Click to collapse
First of all, could Google confirm whether your device was new, or refurbished? The second thing I would ask of Verizon is, whether the IMEI of your device has been registered to their network before you received it. I know it's a Google phone, but the previous owner, if refurbished, might have applied a VZW update from Google, rather than a global stock image or OTA, thinking that it would be a good thing. Then, realizing that they screwed up, relocked it and tried their best to return it to stock and send it back for replacement under whatever guise they chose. That's my best guess as of now.
My P2 came from VZW with the Dec patch, and the bl unlock wasn't greyed out. Didn't really matter because I could use the exploit out of the box without toggling it. But, once I unlocked it, the toggle went grey, and the phone still remains unlocked, even after the April factory image update (skipped Feb and Mar).
In summary, if your device is truly stock Google, you shouldn't be having these issues, which is a valid reason for a replacement. If it isn't, you have a valid reason for yet another replacement, refurbished or not, that IS stock Google. Press the issue...you paid a lot of money for it!

DuckRuckus said:
First of all, could Google confirm whether your device was new, or refurbished? The second thing I would ask of Verizon is, whether the IMEI of your device has been registered to their network before you received it. I know it's a Google phone, but the previous owner, if refurbished, might have applied a VZW update from Google, rather than a global stock image or OTA, thinking that it would be a good thing. Then, realizing that they screwed up, relocked it and tried their best to return it to stock and send it back for replacement under whatever guise they chose. That's my best guess as of now.
My P2 came from VZW with the Dec patch, and the bl unlock wasn't greyed out. Didn't really matter because I could use the exploit out of the box without toggling it. But, once I unlocked it, the toggle went grey, and the phone still remains unlocked, even after the April factory image update (skipped Feb and Mar).
In summary, if your device is truly stock Google, you shouldn't be having these issues, which is a valid reason for a replacement. If it isn't, you have a valid reason for yet another replacement, refurbished or not, that IS stock Google. Press the issue...you paid a lot of money for it!
Click to expand...
Click to collapse
I spoke with Verizon. The only time this phone has been used on their network is when it was activated on my account a few days ago. Google says it's unlocked. I'm still waiting for their response. My current theory is that it some how got locked when it recognized the verizon sim, but I really can be sure.

mtpease said:
I spoke with Verizon. The only time this phone has been used on their network is when it was activated on my account a few days ago. Google says it's unlocked. I'm still waiting for their response. My current theory is that it some how got locked when it recognized the verizon sim, but I really can be sure.
Click to expand...
Click to collapse
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

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

owner232 said:
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
Click to expand...
Click to collapse
if you are on Sep 2017 update, dont worry about OEM unlock.
Side load the jan update, and unlock the bootloader.
details here - https://forum.xda-developers.com/pixel-2/how-to/unlock-bootloader-verizon-pixel-2-t3730076
read carefully.

munchy_cool said:
if you are on Sep 2017 update, dont worry about OEM unlock.
Side load the jan update, and unlock the bootloader.
details here - https://forum.xda-developers.com/pixel-2/how-to/unlock-bootloader-verizon-pixel-2-t3730076
read carefully.
Click to expand...
Click to collapse
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?

giant22000 said:
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
Click to expand...
Click to collapse
That's not true.
Sent from my Pixel 2 using Tapatalk

owner232 said:
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?
Click to expand...
Click to collapse
nopes...nothing.

mtpease said:
I spoke with Verizon. The only time this phone has been used on their network is when it was activated on my account a few days ago. Google says it's unlocked. I'm still waiting for their response. My current theory is that it some how got locked when it recognized the verizon sim, but I really can be sure.
Click to expand...
Click to collapse
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.

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.

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.

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.