Related
Is it possible to downgrade to NDE63P from NDE63X? Wanting to root now that TWRP is available...
Bootloader IS still locked...
nozzleman_85 said:
Is it possible to downgrade to NDE63P from NDE63X? Wanting to root now that TWRP is available...
Bootloader IS still locked...
Click to expand...
Click to collapse
Not if you have a locked bootloader
Cozzeck said:
Not if you have a locked bootloader
Click to expand...
Click to collapse
How would I go about doing this, I have a Verizon pixel xl that's unlocked and I am on the X update and would like to revert to P
shibbnasty said:
How would I go about doing this, I have a Verizon pixel xl that's unlocked and I am on the X update and would like to revert to P
Click to expand...
Click to collapse
What's the point of returning to P?
Sent from my Pixel XL using Tapatalk
david.degraw54 said:
What's the point of returning to P?
Click to expand...
Click to collapse
Well I'm trying to fix and issue I'm having with the camera flash, ever since the update it will only flash once and then will not work again with any app no matter what until I do a restart. It worked before the update and nothing happened to the phone so I wanted to see if going back might fix it before I have to get a refurbished one from Verizon.
shibbnasty said:
Well I'm trying to fix and issue I'm having with the camera flash, ever since the update it will only flash once and then will not work again with any app no matter what until I do a restart. It worked before the update and nothing happened to the phone so I wanted to see if going back might fix it before I have to get a refurbished one from Verizon.
Click to expand...
Click to collapse
Well first you need to unlock your bootloader: http://theroot.ninja/depixel8.html
After that, download the P factory image from Google's site and follow instructions to install. Just remember to backup stuff you want (photos, files, anything saved on storage) because unlocking will perform a factory reset.
Sent from my Pixel XL using Tapatalk
david.degraw54 said:
Well first you need to unlock your bootloader: http://theroot.ninja/depixel8.html
After that, download the P factory image from Google's site and follow instructions to install. Just remember to backup stuff you want (photos, files, anything saved on storage) because unlocking will perform a factory reset.
Click to expand...
Click to collapse
Already unlocked and downloaded the images and tried to install as the directions but during the process it says boot.img and recovery.img is missing even though I did exactly what it said.
---------- Post added at 12:59 AM ---------- Previous post was at 12:54 AM ----------
Not really sure what I'm doing wrong at this point and I'm stuck
Did you copy the files into the fastboot and adb program file?
They need to be in there for it to work.
shibbnasty said:
Already unlocked and downloaded the images and tried to install as the directions but during the process it says boot.img and recovery.img is missing even though I did exactly what it said.
---------- Post added at 12:59 AM ---------- Previous post was at 12:54 AM ----------
Not really sure what I'm doing wrong at this point and I'm stuck
Click to expand...
Click to collapse
Your using an outdated ADB and Fastboot (like 99% of the people on this forum).
Here is the latest: https://dl.dropboxusercontent.com/u/31360541/platform-tools-version_1.0.36-API_25.zip
Scott said:
Your using an outdated ADB and Fastboot (like 99% of the people on this forum).
Here is the latest: https://dl.dropboxusercontent.com/u/31360541/platform-tools-version_1.0.36-API_25.zip
Click to expand...
Click to collapse
Thank you, worked after that and I am back to P but unfortunately my flash is still not working correctly. Sucks in passed the 14 day return so I'll get a refurbished when the phone is practically brand new.
shibbnasty said:
Thank you, worked after that and I am back to P but unfortunately my flash is still not working correctly. Sucks in passed the 14 day return so I'll get a refurbished when the phone is practically brand new.
Click to expand...
Click to collapse
There might not be any refurbished phones to send you so you might luck out. Better to try now than later when they have a big stock of returned phones. Or I'm crazy and you'll get one either way...
Jacobk85 said:
There might not be any refurbished phones to send you so you might luck out. Better to try now than later when they have a big stock of returned phones. Or I'm crazy and you'll get one either way...
Click to expand...
Click to collapse
Yea I'm really hoping not to get a refurbished. I'm gonna do my best to see that I get a new one but if not I guess oh well. I have a 32g really blue model so not sure if they even have any new ones.
shibbnasty said:
Yea I'm really hoping not to get a refurbished. I'm gonna do my best to see that I get a new one but if not I guess oh well. I have a 32g really blue model so not sure if they even have any new ones.
Click to expand...
Click to collapse
Thanks for hijacking my thread dude....
nozzleman_85 said:
Thanks for hijacking my thread dude....
Click to expand...
Click to collapse
Sorry man....
shibbnasty said:
Well I'm trying to fix and issue I'm having with the camera flash, ever since the update it will only flash once and then will not work again with any app no matter what until I do a restart. It worked before the update and nothing happened to the phone so I wanted to see if going back might fix it before I have to get a refurbished one from Verizon.
Click to expand...
Click to collapse
Doubt you'd get a refurbished unit at this point, you'd still get one from replacement stock set aside for early issues.
nozzleman_85 said:
Is it possible to downgrade to NDE63P from NDE63X? Wanting to root now that TWRP is available...
Bootloader IS still locked...
Click to expand...
Click to collapse
You will need to unlock your bootloader. Why do you need to downgrade though? You can root and install TWRP on nde63x.
cambunch said:
You will need to unlock your bootloader. Why do you need to downgrade though? You can root and install TWRP on nde63x.
Click to expand...
Click to collapse
I realized that after a little research.. that's my fault..
I have installed the adb drivers and it recognized my device and installed drivers. I have enabled debugging. I use the commands for dpixel8. adb push dePixel8 /data/local/tmp
adb shell chmod 755 /data/local/tmp/dePixel8
adb shell /data/local/tmp/dePixel8
It reboots the device but does not reboot into bootloader as it is suppose to. It just reboots into normal mode. Any suggestions. Please give me a step by step on how to unlock and root my phone. Thanks
You have to tick that OEM unlock thing under Dev settings where you enabled debugging. And the command to reboot in bootloader is adb reboot bootloader!
PS: Sorry never mind.
ithehappy said:
You have to tick that OEM unlock thing under Dev settings where you enabled debugging. And the command to reboot in bootloader is adb reboot bootloader!
Click to expand...
Click to collapse
No he does not. He clearly just stated he's using depixel8 which means he's on a vzw pixel. Which means no switching on OEM unlock. Hence using depixel8.
Have you tried doing it a second time.
I take it you're not on 7.1.1 though?
toknitup420 said:
No he does not. He clearly just stated he's using depixel8 which means he's on a vzw pixel. Which means no switching on OEM unlock. Hence using depixel8.
Have you tried doing it a second time.
Click to expand...
Click to collapse
Yes. I have tried it several times. It keeps telling me it did not work please try again.
DaveHTC200 said:
I take it you're not on 7.1.1 though?
Click to expand...
Click to collapse
Yes. It is 7.1.1. I am wondering if google came out with another security update to counter dpixel8
mewilson666 said:
Yes. I have tried it several times. It keeps telling me it did not work please try again.
Click to expand...
Click to collapse
Are you on 7.1.1???
mewilson666 said:
Yes. It is 7.1.1. I am wondering if google came out with another security update to counter dpixel8
Click to expand...
Click to collapse
depixel8 can not unlock the bootloader of a Verizon Pixel once 7.1.1 is flashed onto it, either at the factory or by the update.
Downgrading to 7.1 will not restore the bootloader to the one that depixel8 can exploit.
aholeinthewor1d said:
Are you on 7.1.1???
Click to expand...
Click to collapse
Yes I am on 7.7.1
pTeronaut said:
depixel8 can not unlock the bootloader of a Verizon Pixel once 7.1.1 is flashed onto it, either at the factory or by the update.
Downgrading to 7.1 will not restore the bootloader to the one that depixel8 can exploit.
Click to expand...
Click to collapse
Anyone or anything that can?
mewilson666 said:
Yes I am on 7.7.1
Click to expand...
Click to collapse
That would explain it. You can't unlock your bootloader now. The exploit dePixel8 uses was patched with the 7.1.1 update.
mewilson666 said:
Anyone or anything that can?
Click to expand...
Click to collapse
At this moment in time, nothing can unlock the bootloader of a Verizon sold Pixel once 7.1.1 is flashed onto it.
If there was, or will be, you can bet that there will be a thread on XDA about it.
pTeronaut said:
At this moment in time, nothing can unlock the bootloader of a Verizon sold Pixel once 7.1.1 is flashed onto it.
If there was, or will be, you can bet that there will be a thread on XDA about it.
Click to expand...
Click to collapse
Not what I wanted to hear. Haha. Anybody know how I can change the font size? I can not see that little stuff
mewilson666 said:
Not what I wanted to hear. Haha. Anybody know how I can change the font size? I can not see that little stuff
Click to expand...
Click to collapse
Settings - Display - Text size
quangtran1 said:
Settings - Display - Text size
Click to expand...
Click to collapse
Haha Duh! Thanks
mewilson666 said:
Haha Duh! Thanks
Click to expand...
Click to collapse
LOL.
Hello Guys,
First sry for my bad English im from Germany
Today i have downgraded my Google Pixel 2 XL 8.1 (DEZ. PATCH) to 8.0 (SEP. PATCH)
I know this isnt possible but i do it.
Here is what i do:
First i search here in the Forums a fix for the multitouch Bug since 8.1, i try all methods but nothing have work for me...
So i try to downgrade my Pixel 2 xl from 8.1 to 8.0 with the official Factory Image Files from Google but it isnt work for me because my Phone say (after i try the OTA Update via sideload) that i have already an newer Version of Android installed.
So what to do?
I Install the latest Factory Image from Google (8.1 Jan.Patch)
After the Install i stoped the First Start of my Phone and Go Back to bootloader, than i try to Lock my bootloader via ADB. After the Lock i See an Message in my Phone Like "there is noch System installed on your device, device cant Start" Or something Like that.
Now i Boot Back to bootloader and unlock my Phone again but that error stay there and my Phone will not Boot.
I think OK there noch System installed on my Phone now and maybe i can flash the factory Image from the Google Developer Site.
I downloaded the First Image File "8.0.0 (OPD1.170816.010, Sep. 2017)
Booted my Phone to bootloader and run the Script "flash-all.bat"
The installation finished without any errors and my Phone booted without any Problems.
I think "OK cant be" but i Go to settings and Check the Android Version i have installed, and i See im Back to Android 8.0.0
Ok
blaze9090 said:
Ok
Click to expand...
Click to collapse
I have a Question:
After the downgrade to 8.0 i checked the System Update in the settings, but it says that im on the latest Version of Android
Any Fix for that?
Flash latest factory images...
imex1 said:
... I think "OK cant be" but i Go to settings and Check the Android Version i have installed, and i See im Back to Android 8.0.0
Click to expand...
Click to collapse
What a very long post for nothing. Go to the Google developer website, download the latest full January build and flash it with the script according to the instructions given on the same page. Then drink a beer. Prost. :good:
alia5 said:
Flash latest factory images...
Click to expand...
Click to collapse
I dont wanna Go to 8.1 yet because of the Multitouch Bug in Games, waiting for an official fix by Google
I try to Upgrade Googles OTA Image via sideloade after the fix, Thanksgiving you
v12xke said:
What a very long post for nothing. Go to the Google developer website, download the latest full January build and flash it with the script according to the instructions given on the same page. Then drink a beer. Prost. :good:
Click to expand...
Click to collapse
Ehm thanks for the Info but i Post my way to DOWNGRADE from 8.1 to 8.0, because its NOT official possible...
But thx
imex1 said:
Ehm thanks for the Info but i Post my way to DOWNGRADE from 8.1 to 8.0, because its NOT official possible...
But thx
Click to expand...
Click to collapse
FFS, my grandmother can downgrade from 8.1 to 8.0, mate. Was this supposed to be a tutorial? haha! Again, drink another beer. Prost. :good:
v12xke said:
FFS, my grandmother can downgrade from 8.1 to 8.0, mate. Was this supposed to be a tutorial? haha! Again, drink another beer. Prost. :good:
Click to expand...
Click to collapse
Ah okay, thx for the Info, all i knew ist that its NOT possible to downgrade from 8.1 to 8.0
But seems im wrong, but hey thx to know
Now i can deleat my Post, thx Guys for Help.. good Community in XDA! Cheers
No worries mate! Ayinger Oktober Fest-Märzen | Privatbrauerei. Prost. My favorite. Still have one full case / 20 L. In Texas!
v12xke said:
FFS, my grandmother can downgrade from 8.1 to 8.0, mate. Was this supposed to be a tutorial? haha! Again, drink another beer. Prost. :good:
Click to expand...
Click to collapse
So, tell us how you're supposed to downgrade from 8.1 to 8.0? Especially since Google added safeguards to prevent this. Maybe I'm missing something, but to my knowledge it's not 'supposed' to be possible.
stumpy352 said:
So, tell us how you're supposed to downgrade from 8.1 to 8.0? Especially since Google added safeguards to prevent this. Maybe I'm missing something, but to my knowledge it's not 'supposed' to be possible.
Click to expand...
Click to collapse
Unlock bootloader, unlock critical, flash 8.0 image
TheSt33v said:
Unlock bootloader, unlock critical, flash 8.0 image
Click to expand...
Click to collapse
Is that all that's needed? Unlocking the critical partition?
Does that circumvent Google's anti roll back?
stumpy352 said:
Is that all that's needed? Unlocking the critical partition?
Does that circumvent Google's anti roll back?
Click to expand...
Click to collapse
Yes. I don't know the details of Google's anti rollback measures, but I don't think they were meant to apply to unlocked bootloaders. Google allows bootloader unlock to be friendly to developers who probably want to test their apps on different firmware versions. What would be the point of locking them out of various firmwares? In fact, what's the point of an unlockable bootloader at all if you're going to still put restrictions on flashing?
The reason why the OP thought he needed to find out a clever downgrade method was because he was trying to use an OTA to downgrade. OTAs never allow downgrading, and I don't think they ever have. This is nothing new. The factory images, however, will always work as long as both "fastboot flashing unlock" and "fastboot flashing unlock_critical" have been performed beforehand with the latest version of fastboot.
TheSt33v said:
Yes. I don't know the details of Google's anti rollback measures, but I don't think they were meant to apply to unlocked bootloaders. Google allows bootloader unlock to be friendly to developers who probably want to test their apps on different firmware versions. What would be the point of locking them out of various firmwares? In fact, what's the point of an unlockable bootloader at all if you're going to still put restrictions on flashing?
The reason why the OP thought he needed to find out a clever downgrade method was because he was trying to use an OTA to downgrade. OTAs never allow downgrading, and I don't think they ever have. This is nothing new. The factory images, however, will always work as long as both "fastboot flashing unlock" and "fastboot flashing unlock_critical" have been performed beforehand with the latest version of fastboot.
Click to expand...
Click to collapse
The only reason why i open this thread is, that after i try to downgrade to 8.0 my devise go to bootloop, after i flash back to 8.1 it works fine...so with my post i downgraded to 8.0 and its still work fine, im now on 8.0 with nov patch, the only reason why i downgrade is the stupid Multitouch Bug in games, so im waiting for official fix by google
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.