Develop Bugs

OTA Updates in Oz ?

Does anyone know if we can get OTA updates for Galaxy Nexus in Oz yet? Got my GN from Mobicity this week and it is running 4.01. If I go into settings and hit 'check for updates', it says my device is up to date. Would the update be coming from the Provider (optus)? If so, I guess I will have to wait until the are supplying the phones (next few days).
Any information appreciated.

I think the says one is the same as euro check if its yakuju or not.
Mine is an import so I can't say for sure
Sent from my Galaxy Nexus using Tapatalk

There's an app on the Android market which will tell you if you're getting updates direct from Google or waiting for it to go through Samsung. I'd post the link, but apparently I need to make a few other posts first... </rant>
Anyway, it's on the market, named 'GN Official Update Checker'.
If you don't have a Yakju build you can always flash it back to one. Location doesn't matter for Yakju builds, so long as your phone can reach the Google servers, you'll get updates.

Thanks for that. I had already downloaded and ran that App. It says I DONT get my updates from Google.
Not overly keen to unlock the bootloader and flash it at this point in time. Will wait a while and see what comes out in the coming weeks.
Cheers.

Mine actually came with an unlocked bootloader. I wasn't getting updates from Google, but I flashed back to stock 4.0.2 and everything's been fine since. I was a bit nervous about doing so, since I've never done anything like this before, but with the guides here on XDA it was a remarkably simple and easy process.

Milamber33 said:
Mine actually came with an unlocked bootloader.
Click to expand...
Click to collapse
How can I tell if it is already unlocked?

Foxxy74 said:
How can I tell if it is already unlocked?
Click to expand...
Click to collapse
When you boot up if you have a lock under google and it is unlocked then your bootloader is unlocked
Sent by me, for me and i love you

I have a mobicity yakju thus updated by google when it pleases them
Still on 4.01. unadulterated at this point, but getting impatient........

BlackHoleSlam said:
When you boot up if you have a lock under google and it is unlocked then your bootloader is unlocked.
Click to expand...
Click to collapse
Nope, no lock under Google at boot, so I am guessing mine is locked...bugga

You do get OTA updates in Australia. Mine was bought from Clove in the UK and came with the yakju build. Got the volume bug fix a few weeks ago. You just have to be patient I guess.

drahyrt said:
I have a mobicity yakju thus updated by google when it pleases them
Still on 4.01. unadulterated at this point, but getting impatient........
Click to expand...
Click to collapse
Try going into settings and manually checking for an update. Sometimes it's available, your phone just hasn't found it yet.
---------- Post added at 04:46 PM ---------- Previous post was at 04:41 PM ----------
Foxxy74 said:
Nope, no lock under Google at boot, so I am guessing mine is locked...bugga
Click to expand...
Click to collapse
It's easy and pretty risk-free to unlock, and just as easy to re-lock again if you're so inclined.

if you bought the nexus in aus and want direct google updates just convert your phone to the yakuju build from the google nexus factory image site http://code.google.com/android/nexus/images.html
just flash with fastboot, i did this on mine cause i cbf waiting for the ota;s

+1 Amen brother.

My SGN was also purchased from mobicity and I'm in WA, I received both the volume bug and 4.0.2 update on the first day it was released. It's also a yakju build. Just lucky I guess
Sent from my Galaxy Nexus using Tapatalk

I bought from mobicty too but i already got 4.0.2 maybe 3 or 4 days ago
Sent from my Galaxy Nexus using XDA App

KK XML/FXZ is now Live! Thx to stras1234! Notice, 2 different ota's

XML.
https://drive.google.com/file/d/0Byyu7DY1fJ31cVFzSGdsb1RrOXM/edit?usp=sharing
Thanks @stras1234
From
http://forum.xda-developers.com/showthread.php?p=52747840
If you be on 98.18.94 do the OTA of the same name!
....98.30.1 do the OTA likewise.
More:
http://forum.xda-developers.com/showpost.php?p=52716429&postcount=25

I was on 98.18.94 and updated to KK 182. I froze system apps and it refused to boot. Then i RSD'd to 98.30.1 and that gave me the KK 183. update. NOTHING on the phone changed. Bootloader still unlocked and everything. I believe they're pretty much identical and it doesnt matter which update you take.

I was kind in the same situation, I was on 98.18.94, but was rooted and couldn't take the OTA. Used House of Moto to go to 98.30.1 and then was able to take OTA. I still have the original KitKat OTA Blur_Version.98.18.94.XT907.Verizon.en.US.zip that I pulled before going to 98.30.1. Are you saying I should be using that version 182.46.10.xt907 instead of 183.46.10.xt907 since I originally had the 98.18.94? Any idea what the difference is between the 2 versions?

Murph28 said:
I was kind in the same situation, I was on 98.18.94, but was rooted and couldn't take the OTA. Used House of Moto to go to 98.30.1 and then was able to take OTA. I still have the original KitKat OTA Blur_Version.98.18.94.XT907.Verizon.en.US.zip that I pulled before going to 98.30.1. Are you saying I should be using that version 182.46.10.xt907 instead of 183.46.10.xt907 since I originally had the 98.18.94? Any idea what the difference is between the 2 versions?
Click to expand...
Click to collapse
I no longer have a M. I did check the recoveries & they have different md5's.
There have been just too many borks associated with this neglect of name/build subtlety to ignore it.

Since I have the original OTA could I either down grade and apply the correct OTA or since I have an unlocked bootloader would I be able to reinstall the original without the down grade step?

Murph28 said:
Since I have the original OTA could I either down grade and apply the correct OTA or since I have an unlocked bootloader would I be able to reinstall the original without the down grade step?
Click to expand...
Click to collapse
Consult @SamuriHL
But just a do over seems best.

If you're unlocked, just downgrade using the UNIVERSAL RSD script back to 9.30.1, then install the OTA zip for 9.30.1. See here:
http://www.droidrzr.com/index.php/topic/45495-how-to-xt907-upgrade-to-kitkat-ota/

stras1234 posted the full XML for the KK update in this thread this morning.
http://forum.xda-developers.com/showthread.php?t=2751212&goto=newpost
The file is good. Folks should go and thank him.
This makes life easier and gives us a safety net...Yay!

cellzealot said:
stras1234 posted the full XML for the KK update in this thread this morning.
http://forum.xda-developers.com/showthread.php?t=2751212&goto=newpost
The file is good. Folks should go and thank him.
This makes life easier and gives us a safety net...Yay!
Click to expand...
Click to collapse
I can update my thread on droidrzr now. Thanks for checking that. No sign of the RAZR HD FXZ yet huh?

Nope, and I was told by someone who would absolutely know that they hadn't been pushed to the servers yet...
This guy popped up out of the clear blue sky and said he had the file almost as soon as the OTA started going live.
That is all I can tell you...manna from heaven...I wouldn't *****!

Click-able XML link in op.

cellzealot said:
Nope, and I was told by someone who would absolutely know that they hadn't been pushed to the servers yet...
This guy popped up out of the clear blue sky and said he had the file almost as soon as the OTA started going live.
That is all I can tell you...manna from heaven...I wouldn't *****!
Click to expand...
Click to collapse
Yes, I talked to our mutual friend about it a few days ago and was told the same thing. How stras1234 managed to acquire the FXZ so quickly is beyond me but truly amazing. We were highly skeptical when he posted that he had it on droidrzr. I guess we should have looked into it a bit further. LOL. But that's what prompted me to ask our mutual friend about it and when he said it wasn't out, my skepticism grew. Ah well. Most impressive!

SamuriHL said:
Yes, I talked to our mutual friend about it a few days ago and was told the same thing. How stras1234 managed to acquire the FXZ so quickly is beyond me but truly amazing. We were highly skeptical when he posted that he had it on droidrzr. I guess we should have looked into it a bit further. LOL. But that's what prompted me to ask our mutual friend about it and when he said it wasn't out, my skepticism grew. Ah well. Most impressive!
Click to expand...
Click to collapse
Well...it gets thickerer and thickerer...but ya, I was also rather skeptical and spoke to another friend about it and our buddy stras1234 is a resourceful fellow indeed!
I am always grateful for new sources of valuable files.

cellzealot said:
Well...it gets thickerer and thickerer...but ya, I was also rather skeptical and spoke to another friend about it and our buddy stras1234 is a resourceful fellow indeed!
I am always grateful for new sources of valuable files.
Click to expand...
Click to collapse
Hell yea! Completely appreciated. This update has been a nightmare given the multiple OTA updates depending on previous version. The FXZ makes all that go away.

SamuriHL said:
If you're unlocked, just downgrade using the UNIVERSAL RSD script back to 9.30.1, then install the OTA zip for 9.30.1. See here:
http://www.droidrzr.com/index.php/topic/45495-how-to-xt907-upgrade-to-kitkat-ota/
Click to expand...
Click to collapse
I was originally on 98.18.94 and rooted. I ended up using House of Moto to install the 98.30.1 because OTA failed. I was then able to get the OTA. The OP is saying I should be using 182.46.10.xt907 version and not 183.46.10.xt907. So if I go back to 98.30.1 can I then install the correct OTA, or is there a place to get the file to downgrade to my original version? I went to http://sbf.droid-developers.org/ and it did not have my version to download.

Murph28 said:
I was originally on 98.18.94 and rooted. I ended up using House of Moto to install the 98.30.1 because OTA failed. I was then able to get the OTA. The OP is saying I should be using 182.46.10.xt907 version and not 183.46.10.xt907. So if I go back to 98.30.1 can I then install the correct OTA, or is there a place to get the file to downgrade to my original version? I went to http://sbf.droid-developers.org/ and it did not have my version to download.
Click to expand...
Click to collapse
Since the FXZ for KK was posted, I've updated my thread with instructions on how to use it. I'd just flash that and call it good. The whole 182 vs 183 nonsense is a red herring. There's no difference between the builds except the build number and signing keys. Personally if I still had a Moto phone I'd be sticking with the FXZ path regardless of what anyone says.

im currently running KK, get kitkat from ota update and my KK version is 183.46.10. can i reflash to this FXZ??it is save? my phone is unlocked bootloader.. need your help. thank you

You CAN but the question is what do you hope to gain?
Sent from my SM-P600 using Tapatalk

SamuriHL said:
You CAN but the question is what do you hope to gain?
Sent from my SM-P600 using Tapatalk
Click to expand...
Click to collapse
I dont now why..but i found bug with version 183..sometimes i got my phone cant turn on from lockscreen..and can only fix it using hard reboot (press vol up+vol down+power in the same time)..i hope with version 182 can be solved..and another question is after ota update my model number is XT905 NOT XT907 OR Razr M..dunno why
Sent from my XT907 using XDA Free mobile app

That's odd about XT905 (since neither the Electrify M, nor the Aussie Razr M got KitKat yet - they're both can be XT905 for some reason), but yes, you could try to flash again via RSD Lite for a cleaner system. It doesn't matter if it's 182 or 183 though, as it's the same version.
OT: But for the Electrify M which is XT901 an update is announced at Moto's site now.

If I buy from Verizon, can I flash stock and get stock updates?

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

[Q] Flash verizon with non-verizon factory images

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

Pixel XL 2 - "Your device is corrupt" after OTA.

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!!