Is there a way to update without locking the bootloader? - Google Pixel 2 XL Questions & Answers

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.

Related

Android Toolkit updated my phone to 7.1.1...Am I boned?

So, I was installing ADB and such with android toolkit, It rebooted my phone into FASTBOOT in order to check the status of bootloader. Got the info I needed, then the phone rebooted, I went to download depixel8 and get ready to unlock and start the root shenanigans...and boom. The phone installs the NMF26U update without me even telling it to/letting it. Am I completely screwed on here as far as now being able to root and unlock my phone?
SomeFknGuy said:
So, I was installing ADB and such with android toolkit, It rebooted my phone into FASTBOOT in order to check the status of bootloader. Got the info I needed, then the phone rebooted, I went to download depixel8 and get ready to unlock and start the root shenanigans...and boom. The phone installs the NMF26U update without me even telling it to/letting it. Am I completely screwed on here as far as now being able to root and unlock my phone?
Click to expand...
Click to collapse
The toolkit updated your phone, or your phone took an ota? The toolkit should not have been able to update if you weren't already unlocked. Unless there's something I'm missing here..
k.s.deviate said:
The toolkit updated your phone, or your phone took an ota? The toolkit should not have been able to update if you weren't already unlocked. Unless there's something I'm missing here..
Click to expand...
Click to collapse
The OTA update notification was there, but I've been avoiding and ignoring it. When ADB/Toolkit rebooted my phone to check the status of the bootloader all was good, the second my phone rebooted from all that the notification bar showed that it was finishing the update. Went into the settings window to check the build version and it is now showing 7.1.1 and NMF26U. I'm without a solid hotspot work around now since foxfi is dead and I'm too lazy to pull my phone case constantly to remove and replace the sim heh. Just wondering what toolkit triggered to allow and instigate the update install
SomeFknGuy said:
The OTA update notification was there, but I've been avoiding and ignoring it. When ADB/Toolkit rebooted my phone to check the status of the bootloader all was good, the second my phone rebooted from all that the notification bar showed that it was finishing the update. Went into the settings window to check the build version and it is now showing 7.1.1 and NMF26U. I'm without a solid hotspot work around now since foxfi is dead and I'm too lazy to pull my phone case constantly to remove and replace the sim heh. Just wondering what toolkit triggered to allow and instigate the update install
Click to expand...
Click to collapse
I'm pretty sure the ota automatically downloads, when the toolkit rebooted the device it finished the install. If your device is Verizon then yes I think you're boned.
k.s.deviate said:
I'm pretty sure the ota automatically downloads, when the toolkit rebooted the device it finished the install. If your device is Verizon then yes I think you're boned.
Click to expand...
Click to collapse
oy... i was afraid of that... maybe someone can find a work around to at least get my hot spot working...
Is there no way to change the boot slot? Old system is still on the now not active bootslot.
So my question is there a way to change the bootslot without twrp.
mikaole said:
Is there no way to change the boot slot? Old system is still on the now not active bootslot.
So my question is there a way to change the bootslot without twrp.
Click to expand...
Click to collapse
There is. "fastboot --set-active=_a" (or _b). Here is a list of all known fastboot commands. https://forum.xda-developers.com/pixel-xl/how-to/pixel-xl-fastboot-commands-t3490080
mikaole said:
Is there no way to change the boot slot? Old system is still on the now not active bootslot.
So my question is there a way to change the bootslot without twrp.
Click to expand...
Click to collapse
Isn't the old system partition updated in the background then after the update is complete? Even if it isn't, the radio and bootloader are still updated.
Sent from my Pixel XL
imnuts said:
Isn't the old system partition updated in the background then after the update is complete? Even if it isn't, the radio and bootloader are still updated.
Sent from my Pixel XL
Click to expand...
Click to collapse
Nope, they aren't updated until a new update comes. Also there are two slots for radio and bootloader just like everything else so in theory if he could use fastboot he could switch boot slots.
Sent from my Pixel XL using Tapatalk
superchilpil said:
Nope, they aren't updated until a new update comes. Also there are two slots for radio and bootloader just like everything else so in theory if he could use fastboot he could switch boot slots.
Click to expand...
Click to collapse
Unfortunately this won't help. If he installed the update his bootloader is now locked and there is no way to unlock it.
aholeinthewor1d said:
Unfortunately this won't help. If he installed the update his bootloader is now locked and there is no way to unlock it.
Click to expand...
Click to collapse
I sry to say..but I completely agree. If your on 7.1.1 and still locked your stuck locked.
SomeFknGuy said:
oy... i was afraid of that... maybe someone can find a work around to at least get my hot spot working...
Click to expand...
Click to collapse
Pop the sim card, push it back in, wait 4 seconds, turn on hotspot.
No there is a way past this it happened to me, @jcase knows the command you need to get by this.
mwalt201 said:
Pop the sim card, push it back in, wait 4 seconds, turn on hotspot.
Click to expand...
Click to collapse
actually been doing just this. just a little bit of a pain to do with the cover that I'm running. worth it though, until verizon figures out a fix for that :|

Unlocked & Rooted on OPP3 (Android Pay working)

Just need to know if this is possible and if so what steps to take
Sent from my Pixel XL using Tapatalk
FUZER384 said:
Just need to know if this is possible and if so what steps to take
Click to expand...
Click to collapse
On beta O? I was rooted on beta but I had supersu so Android pay didn't work, but the steps were the same as any other firmware
sakumaxp said:
On beta O? I was rooted on beta but I had supersu so Android pay didn't work, but the steps were the same as any other firmware
Click to expand...
Click to collapse
Yeah Android Pay is a must for me, from researching it it seems like it's possible with Magisk and having 7.1.2 on another slot. I just can't put the right steps together for some reason
Sent from my Pixel XL using Tapatalk
FUZER384 said:
Yeah Android Pay is a must for me, from researching it it seems like it's possible with Magisk and having 7.1.2 on another slot. I just can't put the right steps together for some reason
Click to expand...
Click to collapse
I highly doubt that is possible since you need rc2 to flash magisk and it won't flash if one of your slots has an Android O boot.IMG.
pcriz said:
I highly doubt that is possible since you need rc2 to flash magisk and it won't flash if one of your slots has an Android O boot.IMG.
Click to expand...
Click to collapse
I have RC2 TWRP working fine on mine, problem is I locked my BL as a troubleshooting step and now VZW disabled the OEM unlocking toggle. This is balsy since I have a Google Play Pixel that I'm using on their network. Oh well I might end up just finding a way to buy another GP Pixel since VZW will never loosen their grip on our bootloaders
FUZER384 said:
I have RC2 TWRP working fine on mine, problem is I locked my BL as a troubleshooting step and now VZW disabled the OEM unlocking toggle. This is balsy since I have a Google Play Pixel that I'm using on their network. Oh well I might end up just finding a way to buy another GP Pixel since VZW will never loosen their grip on our bootloaders
Click to expand...
Click to collapse
Could be worse. You couldve bricked it locking your boot loader with modifications...
pcriz said:
Could be worse. You couldve bricked it locking your boot loader with modifications...
Click to expand...
Click to collapse
True
Sent from my Pixel XL using Tapatalk
FUZER384 said:
True
Click to expand...
Click to collapse
Whatever else you might say about the Pixel and how much harder it is to flash on this phone than others it seems to be virtual impossible to hard brick this phone. Any other phone I've ever used you would be screwed now. It sucks that Verizon locked your bootloader even though you have a Google Phone but if you have any flashing experience at all you should have known not to lock your bootloader when you weren't running full stock because on any other phone I know of that would result in an automatic bootloop. You might want to report to Pixel Support that you are having a problem with your phone--overheating and poor battery life are the two most common ones. They will RMA your phone and send you another Google version if that was what you originally bought--you just need to enable OEM unlocking before you accept any updates from Verizon. If you did a factory reset before returning the phone you might end up back on full stock or boot looping the phone--neither of which would really be bad in your case.
jhs39 said:
Whatever else you might say about the Pixel and how much harder it is to flash on this phone than others it seems to be virtual impossible to hard brick this phone. Any other phone I've ever used you would be screwed now. It sucks that Verizon locked your bootloader even though you have a Google Phone but if you have any flashing experience at all you should have known not to lock your bootloader when you weren't running full stock because on any other phone I know of that would result in an automatic bootloop. You might want to report to Pixel Support that you are having a problem with your phone--overheating and poor battery life are the two most common ones. They will RMA your phone and send you another Google version if that was what you originally bought--you just need to enable OEM unlocking before you accept any updates from Verizon. If you did a factory reset before returning the phone you might end up back on full stock or boot looping the phone--neither of which would really be bad in your case.
Click to expand...
Click to collapse
I locked my bootloader ON stock dp3 thinking because I have a GPE it wouldn't matter. For God's sake I got the package from the Google preview site, had nothing to do with Verizon. Big red must've worked something out with Google to allow them to lock the toggle by IMEI. I had not read this in all my research trying to root on dp3
Sent from my Pixel XL using Tapatalk
jhs39 said:
Whatever else you might say about the Pixel and how much harder it is to flash on this phone than others it seems to be virtual impossible to hard brick this phone. Any other phone I've ever used you would be screwed now. It sucks that Verizon locked your bootloader even though you have a Google Phone but if you have any flashing experience at all you should have known not to lock your bootloader when you weren't running full stock because on any other phone I know of that would result in an automatic bootloop. You might want to report to Pixel Support that you are having a problem with your phone--overheating and poor battery life are the two most common ones. They will RMA your phone and send you another Google version if that was what you originally bought--you just need to enable OEM unlocking before you accept any updates from Verizon. If you did a factory reset before returning the phone you might end up back on full stock or boot looping the phone--neither of which would really be bad in your case.
Click to expand...
Click to collapse
Isn't kind of against the rules to suggest users make false reports to return device?
Not to mention what it makes the user look like if they boot up the device and see what is running on it.
Smart thing to do first would be to side load an ota, or attempt to.
Inform them you purchased the one you purchased because you could unlock and youre not happy with the condition of the device.
This narrative may be helpful because it puts op down a path that may get him a true GPE device.
Seems that I have just the opposite with you. I deadly want my XL 8.0 OPP3 to be UNLOCKED......
Has anyone released a modified stock kernel for O Preview that bypasses unlocked bootloader checks? I don't care about root but I like my bootloader unlocked, still want Netflix and Android Pay though.

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

Skipsoft unable to unlock my bootloader? Trying to root

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

Questions about updating

So I've had my unlocked Note 10+ since it launched. I have held back on updating the software just in case we are able to get some type of root. What if anything am I missing out on? I've seen articles here and there but I'd rather ask those of you that have updated. I haven't had any issues that made me feel the need to update.
smuvman said:
So I've had my unlocked Note 10+ since it launched. I have held back on updating the software just in case we are able to get some type of root. What if anything am I missing out on? I've seen articles here and there but I'd rather ask those of you that have updated. I haven't had any issues that made me feel the need to update.
Click to expand...
Click to collapse
Security update is not important for you?
smuvman said:
So I've had my unlocked Note 10+ since it launched. I have held back on updating the software just in case we are able to get some type of root. What if anything am I missing out on? I've seen articles here and there but I'd rather ask those of you that have updated. I haven't had any issues that made me feel the need to update.
Click to expand...
Click to collapse
1., We won't get root on Snapdragon.
2. Until they advance the bootloader version, you can always roll back. We're still on bootloader v1.
3. We won't get root on Snapdragon.
Mr. Orange 645 said:
1., We won't get root on Snapdragon.
2. Until they advance the bootloader version, you can always roll back. We're still on bootloader v1.
3. We won't get root on Snapdragon.
Click to expand...
Click to collapse
Lol I know there's prolly no root coming for some time if at all but I'm optimistic. I was basically wanting to know if the updates so far have made any difference since I'm not having any issues.
torickray said:
Security update is not important for you?
Click to expand...
Click to collapse
Nah not really to be honest.

Categories

Resources