I'm using a sim-unlocked Verizon pixel 3 on Fi and (though I've hit the 'check for update' button, which should now get the update whether it was automatically available via OTA or not) I still haven't received the December security patch. I would just flash it, but the Verizon model has a locked bootloader so unfortunately that isn't an option. Is anyone else having this same issue? I know some over on Reddit were.
jacobsface said:
I'm using a sim-unlocked Verizon pixel 3 on Fi and (though I've hit the 'check for update' button, which should now get the update whether it was automatically available via OTA or not) I still haven't received the December security patch. I would just flash it, but the Verizon model has a locked bootloader so unfortunately that isn't an option. Is anyone else having this same issue? I know some over on Reddit were.
Click to expand...
Click to collapse
Nothing wrong with your phone. Since you are BL locked you are just somewhere in the queue of the phased roll-outs and they complete 2-3 weeks after the first Monday every month. It's unfortunate because with some other GSM carriers, when you pay the phone off you can unlock the BL. The Red Devil does not work like that and there is no workaround.
v12xke said:
Nothing wrong with your phone. Since you are BL locked you are just somewhere in the queue of the phased roll-outs and they complete 2-3 weeks after the first Monday every month. It's unfortunate because with some other GSM carriers, when you pay the phone off you can unlock the BL. The Red Devil does not work like that and there is no workaround.
Click to expand...
Click to collapse
Dang it sucks that the rollout can take that long. Someone on Reddit had said it should be out to all by yesterday because the patch is dated the 5th, but that obviously didn't happen. The thing is I didn't even buy it from Verizon, I got it from someone on Ebay who just said it was the unlocked version. At the time I didn't realize Verizon variants were bootloader locked and didn't think to ask for clarification on the bootloader. There's a whole other thread here for trying to unlock it that I've been following but there hasn't been much luck besides luck rma's. It'd be a lot easier if I didn't live in rural West Virginia with service only from a few locked down carriers who barely support any phones besides Galaxies and iPhones. Oh well!
Yeah, I haven't received Dec OTA either. I have a BL unlocked 3XL from Google Fi and normally flash the FULL factory image but I took the OTA last month and like that process better so I'll keep waiting...
jacobsface said:
Dang it sucks that the rollout can take that long. Someone on Reddit had said it should be out to all by yesterday because the patch is dated the 5th, but that obviously didn't happen. The thing is I didn't even buy it from Verizon, I got it from someone on Ebay who just said it was the unlocked version. At the time I didn't realize Verizon variants were bootloader locked and didn't think to ask for clarification on the bootloader. There's a whole other thread here for trying to unlock it that I've been following but there hasn't been much luck besides luck rma's. It'd be a lot easier if I didn't live in rural West Virginia with service only from a few locked down carriers who barely support any phones besides Galaxies and iPhones. Oh well!
Click to expand...
Click to collapse
Hear ya. True statement, the images really *are** out to all who can flash it the first Monday of each month, and YES you can manually flash the OTA image with a locked bootloader. You should read up on getting ADB/Fastboot running on your PC. Instructions on how to flash OTA's are on Google's developer page. Get the latest toolkit you need HERE.* Getting ADB/Fastboot up and running on your PC is a necessary lifesaving skill and really just takes reading and paying attention. Off you go.
Just giving my 2 cents. Stock 3XL. No update here yet either.
v12xke said:
Hear ya. True statement, the images really *are** out to all who can flash it the first Monday of each month, and YES you can manually flash the OTA image with a locked bootloader. You should read up on getting ADB/Fastboot running on your PC. Instructions on how to flash OTA's are on Google's developer page. Get the latest toolkit you need HERE.* Getting ADB/Fastboot up and running on your PC is a necessary lifesaving skill and really just takes reading and paying attention. Off you go.
Click to expand...
Click to collapse
It worked finally! See, Verizon hid their recovery mode behind a button combination on the bootloader. That, and forcing anything to happen from the bootloader screen itself via adb was a no go. But, you have to do a button combination on it to be able to select to apply update from ADB
jacobsface said:
It worked finally! See, Verizon hid their recovery mode behind a button combination on the bootloader. That, and forcing anything to happen from the bootloader screen itself via adb was a no go. But, you have to do a button combination on it to be able to select to apply update from ADB
Click to expand...
Click to collapse
Happy to see you were able to get it done. After a couple of times it just becomes routine. As for recovery button press, we can't blame that one on Verizon. That is the how the stock recovery works even on unlocked phones directly from Google. Don't feel bad, lots of people get tripped up on that too. Cheers :good:
Related
Got my 5X earlier last week, but I haven't been able to get the MDB08I OTA update. Anyone else not getting it? Is there anyway to force it?
Thanks!
You can sideload it if you can download the ota file. Google rolls it out based on some algorithm based on IMEI. You'll get it eventually.
Still waiting for my USB-C to A cable to come in. Just wasn't sure if something else was up with my phone. Didn't know the rollout was based on IMEI; the more you know =)
Thanks!
i havent gotten it yet either :/
i cant even sideload it.. whenever i do "adb devices" when the phone is in recovery mode.. i do not see the device..
on linux & windows. :/
so lame.
Mine was telling me there was an update as soon as I unboxed it and turned the WiFi on. Weird that you aren't getting the update.
On another side note. I've had no problem with getting adb to work.
I've had my 5x since last Monday (19th October) and I don't have it yet either. I'm in the UK.
I'm on MDA89E after getting from cpw yestaday and unboxing didn't get any update yet but loving the 5x so far
Sent from my Nexus 5X using Tapatalk
I think updates are delivered depending on which carrier you are with (as determined by which company's SIM is inserted in the device). It's possible that there isn't one associated with the carrier you are with.
myphone12345 said:
I think updates are delivered depending on which carrier you are with (as determined by which company's SIM is inserted in the device). It's possible that there isn't one associated with the carrier you are with.
Click to expand...
Click to collapse
I thought the point of Nexus range was there was no delay due to carriers?
myphone12345 said:
I think updates are delivered depending on which carrier you are with (as determined by which company's SIM is inserted in the device). It's possible that there isn't one associated with the carrier you are with.
Click to expand...
Click to collapse
Nope. I had no SIM installed when I was alerted to the update. Has nothing to do with SIM or carrier.
Does the bootloader have to be locked to get otas?
nyjumpman said:
Does the bootloader have to be locked to get otas?
Click to expand...
Click to collapse
Probably it's OK to be unlocked, but probably it's not OK to have a custom recovery if you want OTA's. (and want them installed). Best bet is to download B08I and install it via the batch file.
To some other poster in this thread asking about being unable to see phone from adb when recovery is booted up: If it's stock recovery, that makes sense, but if it's custom recovery, you should see adb devices having output.
oxfordmark said:
I thought the point of Nexus range was there was no delay due to carriers?
Click to expand...
Click to collapse
From what I understand, Google has now also started sending out mini updates which are contingent on what company's SIM is in the phone.
myphone12345 said:
From what I understand, Google has now also started sending out mini updates which are contingent on what company's SIM is in the phone.
Click to expand...
Click to collapse
Like I posted earlier. I was alerted to the update and had no SIM installed.
myphone12345 said:
From what I understand, Google has now also started sending out mini updates which are contingent on what company's SIM is in the phone.
Click to expand...
Click to collapse
Oh right, must be for things like wifi calling.
manilaboy1vic said:
i havent gotten it yet either :/
i cant even sideload it.. whenever i do "adb devices" when the phone is in recovery mode.. i do not see the device..
on linux & windows. :/
so lame.
Click to expand...
Click to collapse
Its early and I haven't had my coffee yet so maybe I'm mistaken, but if you are in recovery mode I believe you should be using the command "fastboot devices" to check if your computer can see your phone.
http://www.droid-life.com/2015/10/21/nexus-5x-receiving-update-today-to-build-mdb08i/
Just followed these instructions and the associated links and 30 minutes later ... updated FTW.
Was having problems, at first, with my phone to being recognized. Either the initial usb 2.0 port was jacked or not, I switched to another port and made sure the cable was seated properly and it was picked up right away.
My N5X on AT&T got this update last Tuesday when I got the phone. My girlfriends N5X on Verizon did not yet get the update OTA. Might have to do with carrier?
I always set my phone up without a SIM. Got the update right away during the set up process.
Jexx11 said:
Its early and I haven't had my coffee yet so maybe I'm mistaken, but if you are in recovery mode I believe you should be using the command "fastboot devices" to check if your computer can see your phone.
Click to expand...
Click to collapse
thanks.. that cmd worked..
Android is upgrading... (w00t)
was easier for me to get it going on linux ubuntu.. now onto the hotspot tutorial
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
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!!
I unlocked the bootloader on my Pixel 2 XL and rooted, while being on security patch May 2018, I'm wanting to update to July 2018's security patch but don't want to risk locking the bootloader.
It's a Verizon phone.
Anyone know if I can go about it and how exactly? Really nervous and don't really like my device without being rooted.
Any help is appreciated
ryanispd said:
I unlocked the bootloader on my Pixel 2 XL and rooted, while being on security patch May 2018, I'm wanting to update to July 2018's security patch but don't want to risk locking the bootloader.
Anyone know if I can go about it and how exactly? Really nervous and don't really like my device without being rooted.
Any help is appreciated
Click to expand...
Click to collapse
You won't lock the bootloader unless you manually enter the commands in fastboot.
You can update to July by either: fastbooting the factory image with the -w removed to preserve data. Flashing the OTA.zip in twrp. Or side load the OTA :good:
Badger50 said:
You won't lock the bootloader unless you manually enter the commands in fastboot.
You can update to July by either: fastbooting the factory image with the -w removed to preserve data. Flashing the OTA.zip in twrp. Or side load the OTA :good:
Click to expand...
Click to collapse
My device is a Verizon phone, I was in luck when getting the phone for it being on an older security update just really worried that I will lock it if I try to update it.
Are you 100% sure this won't do so?
Is this guide fine to follow: https://forum.xda-developers.com/pixel-2-xl/how-to/guide-how-to-install-google-software-t3760535
or do I need to leave anything out while doing it? I thought I'd need to leave the bootloader-taimen-tmz12g-.img out or something to prevent it.
Apologizes if I sound dumb, I'm new to all this and only recently moved from Samsung to Pixel so I appreciate the help.
ryanispd said:
My device is a Verizon phone, I was in luck when getting the phone for it being on an older security update just really worried that I will lock it if I try to update it.
Are you 100% sure this won't do so?
Is this guide fine to follow: https://forum.xda-developers.com/pixel-2-xl/how-to/guide-how-to-install-google-software-t3760535
or do I need to leave anything out while doing it? I thought I'd need to leave the bootloader-taimen-tmz12g-.img out or something to prevent it.
Apologizes if I sound dumb, I'm new to all this and only recently moved from Samsung to Pixel so I appreciate the help.
Click to expand...
Click to collapse
You made no mention that it was a Verizon phone in your post. Therefore, I'm not sure now. Have you run the IMEI checker to see if it's truly a Verizon phone.
Sorry, my bad, you did mention it.
Badger50 said:
You made no mention that it was a Verizon phone in your post. Therefore, I'm not sure now. Have you run the IMEI checker to see if it's truly a Verizon phone.
Sorry, my bad, you did mention it.
Click to expand...
Click to collapse
I've read that the only way to lock the bootloader once its unlocked is to manually do so via the commands, this should be the same regardless of if being Verizon I would assume but not sure and don't want to go through with updating without knowing.
What's a good IMEI checker to check which network, imei.info doesn't seem to show
ryanispd said:
I've read that the only way to lock the bootloader once its unlocked is to manually do so via the commands, this should be the same regardless of if being Verizon I would assume but not sure and don't want to go through with updating without knowing.
What's a good IMEI checker to check which network, imei.info doesn't seem to show
Click to expand...
Click to collapse
This is the only one I know of.
http://www.imeipro.info/check_lg.html
Badger50 said:
This is the only one I know of.
http://www.imeipro.info/check_lg.html
Click to expand...
Click to collapse
I checked via verizon's imei checker (https://www.verizonwireless.com/prospect/bring-your-own-device#/checkDevice)
looks like it isn't actually a verizon model, I'm in luck I guess.
ryanispd said:
My device is a Verizon phone, I was in luck when getting the phone for it being on an older security update just really worried that I will lock it if I try to update it.
Are you 100% sure this won't do so?
Is this guide fine to follow: https://forum.xda-developers.com/pixel-2-xl/how-to/guide-how-to-install-google-software-t3760535
or do I need to leave anything out while doing it? I thought I'd need to leave the bootloader-taimen-tmz12g-.img out or something to prevent it.
Apologizes if I sound dumb, I'm new to all this and only recently moved from Samsung to Pixel so I appreciate the help.
Click to expand...
Click to collapse
It will not relock. I am 100 percent sure. There are several reasons it wont. One is that relock will wipe your data, can you imagine the lawsuits if Google and Verizon send an update that they knew would wipe your data.
The second reason is that it is technologically impossible. You are thinking of when a VZ update breaks root o other phones. This phone is way different. It won't happen.
Relax, update.
You will lose root when you update. Easy enough to restore though.
ryanispd said:
I unlocked the bootloader on my Pixel 2 XL and rooted, while being on security patch May 2018, I'm wanting to update to July 2018's security patch but don't want to risk locking the bootloader.
It's a Verizon phone.
Anyone know if I can go about it and how exactly? Really nervous and don't really like my device without being rooted.
Any help is appreciated
Click to expand...
Click to collapse
I also have a Verizon phone that randomly let me unlock the bootloader. I was running DU and just flashed the OTA in TWRP. Booted right up. No issues with it relocking the bootloader or any other nonsense.
Hey, trying to use skipsoft to unlock my bootloader, install twrp, etc. I select the unlock bootloader option, it reboots to fastboot, notes that the bootloader is locked, but then says bootloader already unlocked no data will be wiped rebooting to android. What can I try to get around this? Thanks
GunnermanBill said:
Hey, trying to use skipsoft to unlock my bootloader, install twrp, etc. I select the unlock bootloader option, it reboots to fastboot, notes that the bootloader is locked, but then says bootloader already unlocked no data will be wiped rebooting to android. What can I try to get around this? Thanks
Click to expand...
Click to collapse
Which phone variant do you have? What is the status of the "Allow OEM Unlocking toggle" under Developer Settings? That has to be toggled on first. It should be clearly "on" and not greyed out. If you have the 2XL, you can run the IMEI through this link to verify the variant you have. Under Buyer Name It should say "Google_Open_64GB" or similar.
v12xke said:
Which phone variant do you have? What is the status of the "Allow OEM Unlocking toggle" under Developer Settings? That has to be toggled on first. It should be clearly "on" and not greyed out. If you have the 2XL, you can run the IMEI through this link to verify the variant you have. Under Buyer Name It should say "Google_Open_64GB" or similar.
Click to expand...
Click to collapse
variant is GOOGLE_VRZ_128G
Allow Oem Unlocking Toggle is greyed out for some reason.
GunnermanBill said:
variant is GOOGLE_VRZ_128G
Allow Oem Unlocking Toggle is greyed out for some reason.
Click to expand...
Click to collapse
Well unfortunately there is your reason. Your bootloader cannot be unlocked because your variant is Verizon. Verizon's are bootloader locked and this cannot be overcome. As such you will not be able to flash a custom recovery, flash full Google factory images, or root the phone.
v12xke said:
Well unfortunately there is your reason. Your bootloader cannot be unlocked because your variant is Verizon. Verizon's are bootloader locked and this cannot be overcome. As such you will not be able to flash a custom recovery, flash full Google factory images, or root the phone.
Click to expand...
Click to collapse
Well that's new as far as google phones go
GunnermanBill said:
Well that's new as far as google phones go
Click to expand...
Click to collapse
Sorry to say but it's not new for Verizon variants of Pixel or Nexus (or almost any other phone Verizon sells with very few exceptions). Verizon refuses to allow their users to unlock their own bootloader- including Google phones. Your Verizon phone is bootloader-locked and there is nothing you can do about it. Verizon phones are sometimes sold at deep discounts with the hook of a multi-year service agreement. Have you ever heard the term "The Red Devil" used for Verizon? It's not new either. Sorry to bring you the bad news, but it is true. There are many threads here on XDA which will confirm this. Best of luck.
v12xke said:
Sorry to say but it's not new for Verizon variants of Pixel or Nexus (or almost any other phone Verizon sells with very few exceptions). Verizon refuses to allow their users to unlock their own bootloader- including Google phones. Your Verizon phone is bootloader-locked and there is nothing you can do about it. Verizon phones are sometimes sold at deep discounts with the hook of a multi-year service agreement. Have you ever heard the term "The Red Devil" used for Verizon? It's not new either. Sorry to bring you the bad news, but it is true. There are many threads here on XDA which will confirm this. Best of luck.
Click to expand...
Click to collapse
It's no big deal, my gf took the upgrade to Pie and hates it and I was just gonna root mine before it started prompting me. Someone will get it unlocked in a year or something like always. As far as I can tell the pixel line is the first that Verizon did this with, we had Galaxy Nexus' a long time ago and those weren't locked.
GunnermanBill said:
It's no big deal, my gf took the upgrade to Pie and hates it and I was just gonna root mine before it started prompting me. Someone will get it unlocked in a year or something like always. As far as I can tell the pixel line is the first that Verizon did this with, we had Galaxy Nexus' a long time ago and those weren't locked.
Click to expand...
Click to collapse
Verizon users have been hoping for an unlock method since the 2XL's release.
Look at this thread for more information on that.
xunholyx said:
Verizon users have been hoping for an unlock method since the 2XL's release.
Look at this thread for more information on that.
Click to expand...
Click to collapse
i mean it only happened for the regular pixels in 2016. I'm in no rush, like i said NBD
I'm also trying to relock, just used your link. I'm on the google version running android p. I unlocked a long time ago, but never ended up doing anything with it. I have an RMA coming and the option is grayed out and wugs is failing ... .. Thought about trying to downgrade to O and trying my luck on "android o"
kickenwing13 said:
I'm also trying to relock, just used your link. I'm on the google version running android p. I unlocked a long time ago, but never ended up doing anything with it. I have an RMA coming and the option is grayed out and wugs is failing ... .. Thought about trying to downgrade to O and trying my luck on "android o"
Click to expand...
Click to collapse
You may not have unlocked critical. There are two separate commands. Anyway, since your RMA is on the way just wait until it arrives, update it to Pie and then do a data transfer for all your settings/data. Once your new phone is set up, just do a FDR before sending it back. You do NOT need to relock the phone. They do not care. Just FDR to wipe your personal data off the phone. Lastly, you want to de-register or remove that old phone from your Google account before sending it back. Best of luck.
v12xke said:
You may not have unlocked critical. There are two separate commands. Anyway, since your RMA is on the way just wait until it arrives, update it to Pie and then do a data transfer for all your settings/data. Once your new phone is set up, just do a FDR before sending it back. You do NOT need to relock the phone. They do not care. Just FDR to wipe your personal data off the phone. Lastly, you want to de-register or remove that old phone from your Google account before sending it back. Best of luck.
Click to expand...
Click to collapse
Thank you so much dude. I know you're right . I used the toolkit and nothing after unlocking ever worked and I'm assuming it's because of that .... I've been telling myself I need to learn it the old fashioned way but have never been able to properly install adb and all that stuff..
kickenwing13 said:
Thank you so much dude. I know you're right . I used the toolkit and nothing after unlocking ever worked and I'm assuming it's because of that .... I've been telling myself I need to learn it the old fashioned way but have never been able to properly install adb and all that stuff..
Click to expand...
Click to collapse
I would encourage you to just "install" adb/fastboot. It is literally opening a zip file and extracting everything into a new folder. Then adding that folder to your path statement (Windows) means you can use the command from anywhere. For example I created a folder c:\adb and just dumped the files in there. I see you already have opened the flash-all.bat script and are poking around ... so in the beginning you can just cut and paste those commands if you want to do things manually -or- just run the script. You can always get the latest standalone binaries direct from Google. Ditch the toolkits and you will be glad you did. It is just not that hard, and you will know how to get yourself out of a jam later. :good:
I DID IT!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! It was cake. Thanks for the awesome directions. I just opened up through cmd insead of your second step, but dude! clutch . I relocked it.. took 2 seconds once my buddy helped me tpye my first command. But thank you again! Now debating getting more into it. This is the first phone i haven't installed a custom ROM on because the unlock and root stuff absolutely failed...