Related
Because the Google Store is so back-dated to get a pixel xl, can I just go to Verizon, pay cash for a pixel xl, then flash the stock ROM to it and then get the factory updates?
The way I understand it Verizon updates will come the same time as Google's. Also the only are like 3 apps from Verizon, and they are uninstallable.
Sent from my Pixel XL using Tapatalk
I pre-ordered from Google, got 5 WEEK wait notice 2 weeks after ordering so, I cancelled the order. I went to a Verizon store picked up a pixel XL, while walking out the store uninstalled anything with verizon and put my AT&T Sim card in. Simple as that, No "Unlocking", No regrets.
evoschecter said:
I pre-ordered from Google, got 5 WEEK wait notice 2 weeks after ordering so, I cancelled the order. I went to a Verizon store picked up a pixel XL, while walking out the store uninstalled anything with verizon and put my AT&T Sim card in. Simple as that, No "Unlocking", No regrets.
Click to expand...
Click to collapse
Did you get the latest update? I'm on AT&T also and did not get the OTA, so I side loaded it.
Sent from my Pixel XL using XDA-Developers mobile app
The VZW bootloader can only be unlocked via depixel8 once that is done you can flash the Google factory image, which will also flash the Google bootloader, this way all your updates come from Google vs VZW. But hurry this will be patched in November security patch which is nov 7th.
Has anyone actually been successful in flashing the factory image? I was reading the unlock thread earlier and people were saying the flash was failing
Sent from my Pixel XL using Tapatalk
DualSportDad said:
Has anyone actually been successful in flashing the factory image? I was reading the unlock thread earlier and people were saying the flash was failing
Click to expand...
Click to collapse
Yes I flashed every image available. And the failures were due to having the wrong drivers. Including myself having the wrong drivers
treIII said:
Yes I flashed every image available. And the failures were due to having the wrong drivers. Including myself having the wrong drivers
Click to expand...
Click to collapse
Did you flash them 1 by 1 or use the flash all.bat? I looked inside the image zip folder and my god, there are a lot of files in there. I'm used to the Nexus which has the boot.img, system.img, userdata.img, recovery.img and cache.img. The Pixel folder has 19 IMG. Files.
Sent from my Pixel XL using XDA-Developers mobile app
jaxenroth said:
The VZW bootloader can only be unlocked via depixel8 once that is done you can flash the Google factory image, which will also flash the Google bootloader, this way all your updates come from Google vs VZW. But hurry this will be patched in November security patch which is nov 7th.
Click to expand...
Click to collapse
Apologizes, I'm new here. What is the benefit to flashing the factory image? Does the Google bootloader stay after going to the factory image or will you need to flash it again if i get an update from verizon?
DualSportDad said:
Has anyone actually been successful in flashing the factory image? I was reading the unlock thread earlier and people were saying the flash was failing
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
Could you link to the unlock thread. Unable to find it.
treIII said:
Yes I flashed every image available. And the failures were due to having the wrong drivers. Including myself having the wrong drivers
Click to expand...
Click to collapse
What do you mean by drivers? Which drivers are required? I assume they're for the computer side and not on the phone?
Zeroflucks said:
Apologizes, I'm new here. What is the benefit to flashing the factory image? Does the Google bootloader stay after going to the factory image or will you need to flash it again if i get an update from verizon?
Could you link to the unlock thread. Unable to find it.
What do you mean by drivers? Which drivers are required? I assume they're for the computer side and not on the phone?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=3484497
If you flash the factory image with the bootloader then you won't have the Verizon locked bootloader. You can lock and unlock.
Sent from my Pixel XL using Tapatalk
DualSportDad said:
http://forum.xda-developers.com/showthread.php?t=3484497
If you flash the factory image with the bootloader then you won't have the Verizon locked bootloader. You can lock and unlock.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
Has anyone confirmed this to actually work?
kest874 said:
Has anyone confirmed this to actually work?
Click to expand...
Click to collapse
No it is not confirmed to be true and I'm pretty sure no one has stated that in that thread. There are other things in play here such as the Cid.
Does it matter which factory image i try to flash to? NDE63N is currently on my phone. The ones listed on the site are NDE63H, NDE63L, NDE63P.
Zeroflucks said:
Does it matter which factory image i try to flash to? NDE63N is currently on my phone. The ones listed on the site are NDE63H, NDE63L, NDE63P.
Click to expand...
Click to collapse
P is the latest.
Mike02z said:
P is the latest.
Click to expand...
Click to collapse
Thank you
How do you know that its running the google version instead of the verizon version?
Sent from my iPad using Tapatalk
polo2883 said:
How do you know that its running the google version instead of the verizon version?
Sent from my iPad using Tapatalk
Click to expand...
Click to collapse
I just got my phone today so I assume that N is the verizon version since thats what was on my phone. Im now on P from the factory image on the google website.
Zeroflucks said:
I just got my phone today so I assume that N is the verizon version since thats what was on my phone. Im now on P from the factory image on the google website.
Click to expand...
Click to collapse
That's what I am on too. But the OEM unlocking is still not toggle-able in the developer section.
Sent from my iPad using Tapatalk
polo2883 said:
That's what I am on too. But the OEM unlocking is still not toggle-able in the developer section.
Sent from my iPad using Tapatalk
Click to expand...
Click to collapse
Same here but it does say that bootloader is already unlocked below it for me
NDE63P is the latest firmware, regardless of where the phone came from. I'm not sure where people are getting this "Google Firmware" thing from that is everywhere. There isn't any special firmware for any carrier or model.
Sent from my Pixel XL
Okay, as the title says I would like to know if you can use depixel8 to unlock the verizon pixel xl then fastboot flash the google play store version factory images. Essentially turning the Verizon version into a non-verizon version. From having shamu, which had different carrier images, I would say it is more than likely possible. But surprisingly I cannot find any threads confirming this after an hour of searching.
I just ordered the Verizon pixel xl 128gb today, taking advantage of the steep discount they are offering. I am taking the risk knowingly that it may be patched, but am hopeful I will still be able to use depixel8 once it arrives. From what I am seeing, it has not been patched yet. And as long as I don't accept an OTA before unlocking I should be fine either way. Super excited for it to arrive!
hlxanthus said:
Okay, as the title says I would like to know if you can use depixel8 to unlock the verizon pixel xl then fastboot flash the google play store version factory images. Essentially turning the Verizon version into a non-verizon version. From having shamu, which had different carrier images, I would say it is more than likely possible. But surprisingly I cannot find any threads confirming this after an hour of searching.
I just ordered the Verizon pixel xl 128gb today, taking advantage of the steep discount they are offering. I am taking the risk knowingly that it may be patched, but am hopeful I will still be able to use depixel8 once it arrives. From what I am seeing, it has not been patched yet. And as long as I don't accept an OTA before unlocking I should be fine either way. Super excited for it to arrive!
Click to expand...
Click to collapse
Yes, you can use depixel8 to unlock the bootloader. Yes, you can flash V instead of X via fastboot. However no one has yet been able to figure out your last, and most important part: how to turn a VZW device into a GS device. Go here for more information > http://forum.xda-developers.com/pixel-xl/how-to/verizon-pixel-xl-toggling-oem-unlock-t3498287
cam30era said:
Yes, you can use depixel8 to unlock the bootloader. Yes, you can flash V instead of X via fastboot. However no one has yet been able to figure out your last, and most important part: how to turn a VZW device into a GS device. Go here for more information > http://forum.xda-developers.com/pixel-xl/how-to/verizon-pixel-xl-toggling-oem-unlock-t3498287
Click to expand...
Click to collapse
Asked in another thread, but I'm wondering is it possible for VZ to relock the BL from a firmware update, or once it's unlocked they can't touch it?
theycallmerayj said:
Asked in another thread, but I'm wondering is it possible for VZ to relock the BL from a firmware update, or once it's unlocked they can't touch it?
Click to expand...
Click to collapse
I'll give you the same answer you're seen elsewhere: No one's ever seen this done before. And Google would have to do it (at VZW's request) since they push the updates.
I highly doubt it, but anything's possible I suppose.
Thanks!
theycallmerayj said:
Asked in another thread, but I'm wondering is it possible for VZ to relock the BL from a firmware update, or once it's unlocked they can't touch it?
Click to expand...
Click to collapse
cam30era said:
I'll give you the same answer you're seen elsewhere: No one's ever seen this done before. And Google would have to do it (at VZW's request) since they push the updates.
I highly doubt it, but anything's possible I suppose.
Click to expand...
Click to collapse
While theoretically possible, it is absolutely unprecedented.
Sent from my Nexus 6 using Tapatalk
I believe when you lock and/or unlock the bootloader in Android it completely wipes your device including internal storage. So relocking bootloader by force without your consent I could see leading to major backlash if that's always the case
Sent from my Pixel XL using Tapatalk
cam30era said:
Yes, you can use depixel8 to unlock the bootloader. Yes, you can flash V instead of X via fastboot. However no one has yet been able to figure out your last, and most important part: how to turn a VZW device into a GS device. Go here for more information > http://forum.xda-developers.com/pixel-xl/how-to/verizon-pixel-xl-toggling-oem-unlock-t3498287
Click to expand...
Click to collapse
It cant be done. The google version has different world wide bands. However for all intent and purposes the devices are identical and other than the bands (which I bet someone could unlock)!
hlxanthus said:
While theoretically possible, it is absolutely unprecedented.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
sfetaz said:
I believe when you lock and/or unlock the bootloader in Android it completely wipes your device including internal storage. So relocking bootloader by force without your consent I could see leading to major backlash if that's always the case
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
Click to expand...
Click to collapse
They would risk bricking devices if they ever tried that. I have a strong feeling you will never see it happen.
I know this thread is old but I am just curious about this. Has anyone or does anyone know if you can flash any of the factory images that say Verizon or Telekom on them onto a Pixel XL you purchased from Google? There was an article that was published stating that the Verizon version got some extra changes to help fix things with the device.
Jammol said:
I know this thread is old but I am just curious about this. Has anyone or does anyone know if you can flash any of the factory images that say Verizon or Telekom on them onto a Pixel XL you purchased from Google? There was an article that was published stating that the Verizon version got some extra changes to help fix things with the device.
Click to expand...
Click to collapse
Hello...
In the 7.1.2 beta thread I've seen people with Google version using Verizon firmware. :good:
Cheers...
5.1 said:
Hello...
In the 7.1.2 beta thread I've seen people with Google version using Verizon firmware. :good:
Cheers...
Click to expand...
Click to collapse
Im have a verizon pixel and flashed the Deutsche Ota on accident.
No issues.
JustusIV said:
Im have a verizon pixel and flashed the Deutsche Ota on accident.
No issues.
Click to expand...
Click to collapse
You should have quoted @Jammol
He is the one looking for this..!
Thank you though...
Jammol said:
I know this thread is old but I am just curious about this. Has anyone or does anyone know if you can flash any of the factory images that say Verizon or Telekom on them onto a Pixel XL you purchased from Google? There was an article that was published stating that the Verizon version got some extra changes to help fix things with the device.
Click to expand...
Click to collapse
You can flash any version on any Pixel XL as long as it is unlocked. If version is specific for the Verizon version it will still work it just a few things specific to fixes for the Verizon network.
5.1 said:
You should have quoted @Jammol
He is the one looking for this..!
Thank you though...
Click to expand...
Click to collapse
Im new here
I kid i kid..
yep missed opportunity hehe
nrage23 said:
You can flash any version on any Pixel XL as long as it is unlocked. If version is specific for the Verizon version it will still work it just a few things specific to fixes for the Verizon network.
Click to expand...
Click to collapse
Exactly, i have an unlocked pixel i clean flashed to 7.1.2 and i got a server unreachable error more than once then the verizon update came out so i flashed they new radio to fix that and i got better reception as well because its optimized for their Network
Just need to know if this is possible and if so what steps to take
Sent from my Pixel XL using Tapatalk
FUZER384 said:
Just need to know if this is possible and if so what steps to take
Click to expand...
Click to collapse
On beta O? I was rooted on beta but I had supersu so Android pay didn't work, but the steps were the same as any other firmware
sakumaxp said:
On beta O? I was rooted on beta but I had supersu so Android pay didn't work, but the steps were the same as any other firmware
Click to expand...
Click to collapse
Yeah Android Pay is a must for me, from researching it it seems like it's possible with Magisk and having 7.1.2 on another slot. I just can't put the right steps together for some reason
Sent from my Pixel XL using Tapatalk
FUZER384 said:
Yeah Android Pay is a must for me, from researching it it seems like it's possible with Magisk and having 7.1.2 on another slot. I just can't put the right steps together for some reason
Click to expand...
Click to collapse
I highly doubt that is possible since you need rc2 to flash magisk and it won't flash if one of your slots has an Android O boot.IMG.
pcriz said:
I highly doubt that is possible since you need rc2 to flash magisk and it won't flash if one of your slots has an Android O boot.IMG.
Click to expand...
Click to collapse
I have RC2 TWRP working fine on mine, problem is I locked my BL as a troubleshooting step and now VZW disabled the OEM unlocking toggle. This is balsy since I have a Google Play Pixel that I'm using on their network. Oh well I might end up just finding a way to buy another GP Pixel since VZW will never loosen their grip on our bootloaders
FUZER384 said:
I have RC2 TWRP working fine on mine, problem is I locked my BL as a troubleshooting step and now VZW disabled the OEM unlocking toggle. This is balsy since I have a Google Play Pixel that I'm using on their network. Oh well I might end up just finding a way to buy another GP Pixel since VZW will never loosen their grip on our bootloaders
Click to expand...
Click to collapse
Could be worse. You couldve bricked it locking your boot loader with modifications...
pcriz said:
Could be worse. You couldve bricked it locking your boot loader with modifications...
Click to expand...
Click to collapse
True
Sent from my Pixel XL using Tapatalk
FUZER384 said:
True
Click to expand...
Click to collapse
Whatever else you might say about the Pixel and how much harder it is to flash on this phone than others it seems to be virtual impossible to hard brick this phone. Any other phone I've ever used you would be screwed now. It sucks that Verizon locked your bootloader even though you have a Google Phone but if you have any flashing experience at all you should have known not to lock your bootloader when you weren't running full stock because on any other phone I know of that would result in an automatic bootloop. You might want to report to Pixel Support that you are having a problem with your phone--overheating and poor battery life are the two most common ones. They will RMA your phone and send you another Google version if that was what you originally bought--you just need to enable OEM unlocking before you accept any updates from Verizon. If you did a factory reset before returning the phone you might end up back on full stock or boot looping the phone--neither of which would really be bad in your case.
jhs39 said:
Whatever else you might say about the Pixel and how much harder it is to flash on this phone than others it seems to be virtual impossible to hard brick this phone. Any other phone I've ever used you would be screwed now. It sucks that Verizon locked your bootloader even though you have a Google Phone but if you have any flashing experience at all you should have known not to lock your bootloader when you weren't running full stock because on any other phone I know of that would result in an automatic bootloop. You might want to report to Pixel Support that you are having a problem with your phone--overheating and poor battery life are the two most common ones. They will RMA your phone and send you another Google version if that was what you originally bought--you just need to enable OEM unlocking before you accept any updates from Verizon. If you did a factory reset before returning the phone you might end up back on full stock or boot looping the phone--neither of which would really be bad in your case.
Click to expand...
Click to collapse
I locked my bootloader ON stock dp3 thinking because I have a GPE it wouldn't matter. For God's sake I got the package from the Google preview site, had nothing to do with Verizon. Big red must've worked something out with Google to allow them to lock the toggle by IMEI. I had not read this in all my research trying to root on dp3
Sent from my Pixel XL using Tapatalk
jhs39 said:
Whatever else you might say about the Pixel and how much harder it is to flash on this phone than others it seems to be virtual impossible to hard brick this phone. Any other phone I've ever used you would be screwed now. It sucks that Verizon locked your bootloader even though you have a Google Phone but if you have any flashing experience at all you should have known not to lock your bootloader when you weren't running full stock because on any other phone I know of that would result in an automatic bootloop. You might want to report to Pixel Support that you are having a problem with your phone--overheating and poor battery life are the two most common ones. They will RMA your phone and send you another Google version if that was what you originally bought--you just need to enable OEM unlocking before you accept any updates from Verizon. If you did a factory reset before returning the phone you might end up back on full stock or boot looping the phone--neither of which would really be bad in your case.
Click to expand...
Click to collapse
Isn't kind of against the rules to suggest users make false reports to return device?
Not to mention what it makes the user look like if they boot up the device and see what is running on it.
Smart thing to do first would be to side load an ota, or attempt to.
Inform them you purchased the one you purchased because you could unlock and youre not happy with the condition of the device.
This narrative may be helpful because it puts op down a path that may get him a true GPE device.
Seems that I have just the opposite with you. I deadly want my XL 8.0 OPP3 to be UNLOCKED......
Has anyone released a modified stock kernel for O Preview that bypasses unlocked bootloader checks? I don't care about root but I like my bootloader unlocked, still want Netflix and Android Pay though.
I installed DP2 and then re locked my phone. I installed from the factory image posted today.
Now when I open up Android pay and try to add a card it's saying that it can't be used on my device and my device might be rooted or unlocked.
It's not.
Is anyone else seeing this?
Sent from my Pixel 2 XL using Tapatalk
Give it a day or two, they have to approve the new image in the system. It happened with some other updates too.
Just a minor point about the subject: it should be "since installing DP2" or "after DP2".
When I saw your heading initially I was confused because DP2 has been out for seemingly less than a day. So I thought you meant "since DP1" or something else.
OK, end of the grammar patrol.
pilotgav said:
I installed DP2 and then re locked my phone. I installed from the factory image posted today.
Now when I open up Android pay and try to add a card it's saying that it can't be used on my device and my device might be rooted or unlocked.
It's not.
Is anyone else seeing this?
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
does not work for me either.
uicnren said:
does not work for me either.
Click to expand...
Click to collapse
OTA or flashed image?
Sent from my Pixel 2 XL using Tapatalk
This is an issue for everyone regardless of whether the update was received via OTA or flashing the factory image. Like Twitch175 said, it'll just take a few days to approve the new image and all should be good.
Meanwhile, there is an official Google Plus community for the Android Beta Program where lots of users are already discussing this issue, along with others.
Android Beta Program
It is working for me now, google must have fixed it.
Working now.. wasn't originally recognizing DP2 though
S0UTHPAWK1LLA said:
Working now.. wasn't originally recognizing DP2 though
Click to expand...
Click to collapse
Yaaaaay ?
pilotgav said:
OTA or flashed image?
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
dirty flashed factory image. it is working for me now. Play store still says device is uncertified however.
Took an OTA and now whenever I turn the device on it says in red letters: "Your device is corrupt. It can't be trusted and may not work properly". I can still boot into the OS normally. I can still access fastboot. I can still access recovery. I have done many searches and people keep saying to relock the bootloader or unlock the bootloader and flash stock firmware. There's no way to do either because this Verizon variant is locked down like Fort Knox. I don't understand why the bootloader has to be unlocked to flash STOCK firmware straight from Verizon. Smh. Anyways, does anyone have any ideas. about how to get rid of this message?
ClassickWORLD said:
Took an OTA and now whenever I turn the device on it says in red letters: "Your device is corrupt. It can't be trusted and may not work properly". I can still boot into the OS normally. I can still access fastboot. I can still access recovery. I have done many searches and people keep saying to relock the bootloader or unlock the bootloader and flash stock firmware. There's no way to do either because this Verizon variant is locked down like Fort Knox. I don't understand why the bootloader has to be unlocked to flash STOCK firmware straight from Verizon. Smh. Anyways, does anyone have any ideas. about how to get rid of this message?
Click to expand...
Click to collapse
You could side load the Google OTA image and see if that fixes it. Or just wait until next week and see if the March OTA fixes it. If your device is working properly, I wouldn't worry too much about it.
Badger50 said:
You could side load the Google OTA image and see if that fixes it. Or just wait until next week and see if the March OTA fixes it. If your device is working properly, I wouldn't worry too much about it.
Click to expand...
Click to collapse
I have moved on to the iPhone 8 Plus. I sold the device and had it returned because of that message... and now I want to sell it again. I just need to get rid of it. So you are saying that I can sideload via adb even on a Verizon device with a locked bootloader?
ClassickWORLD said:
I have moved on to the iPhone 8 Plus. I sold the device and had it returned because of that message... and now I want to sell it again. I just need to get rid of it. So you are saying that I can sideload via adb even on a Verizon device with a locked bootloader?
Click to expand...
Click to collapse
While I haven't done it personally, I've seen several people do just that from stock recovery. At worst, the install will fail and nothing will be changed. Unlocking the bootloader is mainly for flashing factory images and rooting, not OTA's. Just follow the instructions from Google and see what happens. In your current situation, you really have nothing to lose.
https://developers.google.com/android/ota
ClassickWORLD said:
I have moved on to the iPhone 8 Plus. I sold the device and had it returned because of that message... and now I want to sell it again. I just need to get rid of it. So you are saying that I can sideload via adb even on a Verizon device with a locked bootloader?
Click to expand...
Click to collapse
Yes, I have a Verizon version of the Pix2-XL, and I have run 4 or 5 times on it.
https://developers.google.com/android/ota
Use these instructions exactly, and be sure you have the newest Android Tools.
This should take care of your error message.
michaelbsheldon said:
Yes, I have a Verizon version of the Pix2-XL, and I have run 4 or 5 times on it.
https://developers.google.com/android/ota
Use these instructions exactly, and be sure you have the newest Android Tools.
This should take care of your error message.
Click to expand...
Click to collapse
Thanks for the conformation my friend. I kinda feel sorry for that poor guy, he went to an iphone!!.....oh the horror! ??????
michaelbsheldon said:
Yes, I have a Verizon version of the Pix2-XL, and I have run 4 or 5 times on it.
https://developers.google.com/android/ota
Use these instructions exactly, and be sure you have the newest Android Tools.
This should take care of your error message.
Click to expand...
Click to collapse
Hey thanks for that. The latest image I see for the Verizon Pixel XL 2 is for 8.0.0 from Nov 2017. I am on 8.1. So I have to downgrade? Is that even possible?
ClassickWORLD said:
Hey thanks for that. The latest image I see for the Verizon Pixel XL 2 is for 8.0.0 from Nov 2017. I am on 8.1. So I have to downgrade? Is that even possible?
Click to expand...
Click to collapse
Huh?? You have a P2XL right?? It's right there at the bottom of the P2XL section.
What build month are you currently on?
ClassickWORLD said:
Hey thanks for that. The latest image I see for the Verizon Pixel XL 2 is for 8.0.0 from Nov 2017. I am on 8.1. So I have to downgrade? Is that even possible?
Click to expand...
Click to collapse
You do want the February one. It's for all phones including Verizon.
Badger50 said:
Huh?? You have a P2XL right?? It's right there at the bottom of the P2XL section.
What build month are you currently on?
Click to expand...
Click to collapse
So I can flash that with no radio issues? I thought OPM1 is google, OPM2 is Telus only, and OPD3 is Verizon only? I have a Verizon P2XL
Edit: I think I've found my issue. The person who had the device before me must have sideloaded 8.1.0 (OPM1.171019.018, Feb 2018)" to this device and that may be the reason for the error. I am thinking because that's not the Verizon P2XL firmware but the Google P2XL device firmware.
michaelbsheldon said:
You do want the February one. It's for all phones including Verizon.
Click to expand...
Click to collapse
Ok gotcha. Downloading now as we speak.
Badger50 said:
Thanks for the conformation my friend. I kinda feel sorry for that poor guy, he went to an iphone!!.....oh the horror! ??
Click to expand...
Click to collapse
Lol I still have my trusty ol' Nexus 6P as my secondary device.
WoW this download link is really slow. Downloading at 50 KB/s. Says 9 hours left. I have fiber speeds for my internet. Anyone know of any alternative download locations for this OTA?
Edit: Rebooted my router and that fixed it. It downloaded in 2 minutes.
ClassickWORLD said:
WoW this download link is really slow. Downloading at 50 KB/s. Says 9 hours left. I have fiber speeds for my internet. Anyone know of any alternative download locations for this OTA?
Edit: Rebooted my router and that fixed it. It downloaded in 2 minutes.
Click to expand...
Click to collapse
Fixed and you're a happy camper, right?
P.S. try a factory reset to complete this
You guys are great. The sideload fixed the problem! I truly appreciate you guys. Thanks a lot.
ClassickWORLD said:
Lol I still have my trusty ol' Nexus 6P as my secondary device.
Click to expand...
Click to collapse
Ok bruh, your forgiven :laugh: Did you get your problem fixed?
Oooops....never mind. I see that you did :good:
Is this the method for unlocking a Verizon Pixel 2 XL? Or just to fix the message this person was receiving. I want to buy a verizon Pixel 2 XL today in the store and do this vs waiting on google to deliver it.
tradermatt said:
Is this the method for unlocking a Verizon Pixel 2 XL? Or just to fix the message this person was receiving. I want to buy a verizon Pixel 2 XL today in the store and do this vs waiting on google to deliver it.
Click to expand...
Click to collapse
There is no method to unlock the Verizon P2XL!!