8.0 Update on Verizon Unlocked Bootloader - is it Safe? - Google Pixel XL Questions & Answers

Hello,
I ordered an unlocked Pixel XL on Amazon (sold out of Google store) after my old Nexus finally kicked the bucket. Lo and behold, they sent me a Verizon one instead.
It was version 7.1, and someone my complete technologically inept self managed to figure out how to unlock it using dePixel8, and now I'm using T-Mobile.
I'd like to know if it's safe to update from 7.1 -> 8.0, and whether the bootloader will remain unlocked. I have no desire to root my phone or anything in the future, I'm just an honest guy who wants to use whatever carrier they wish.
Thanks everyone!

The bootloader will remain unlocked. To move to 8.0, simply flash the latest 8.0 factory image from Google's developer site.
You didn't have to unlock the bootloader to use the phone on T-Mobile.

Related

Verizon pixel xl bootloader and bootloader images

If you end up unlocking the bootloader of a Verizon pixel XL correctly using depixel8, couldn't you install the system.img provided by Google that will,when relocking the bootloader, revert you to the locked stock bootloader version of the pixel XL instead of going back to the Verizon based factory bootloader?
Maybe I am misunderstanding the issue? Can anyone clarify this?
rester555 said:
If you end up unlocking the bootloader of a Verizon pixel XL correctly using depixel8, couldn't you install the system.img provided by Google that will,when relocking the bootloader, revert you to the locked stock bootloader version of the pixel XL instead of going back to the Verizon based factory bootloader?
Maybe I am misunderstanding the issue? Can anyone clarify this?
Click to expand...
Click to collapse
It's not that simple. 1st, if one's VZW device bootloader is unlocked using dePixel8, it will in all likelyhood remain unlocked in the future when flashing updates. 2nd, the bootloader.img file is identical between VZW and Google Store versions. It appears that there is something hardcoded in the IMEI on VZW devices that identifies them, then the bootloader software becomes "unlockable" when it sees that flag.
Repeating old ground, dePixel8 works on devices that are on 7.1. But the exploit has been patched by Google on 7.1.1 (December update).
cam30era said:
It's not that simple. 1st, if one's VZW device bootloader is unlocked using dePixel8, it will in all likelyhood remain unlocked in the future when flashing updates. 2nd, the bootloader.img file is identical between VZW and Google Store versions. It appears that there is something hardcoded in the IMEI on VZW devices that identifies them, then the bootloader software becomes "unlockable" when it sees that flag.
Repeating old ground, dePixel8 works on devices that are on 7.1. But the exploit has been patched by Google on 7.1.1 (December update).
Click to expand...
Click to collapse
It's the Cid. Verizon models have the Verizon Cid. I think it's like VZW001
toknitup420 said:
It's the Cid. Verizon models have the Verizon Cid. I think it's like VZW001
Click to expand...
Click to collapse
Pretty sure it's not the cid. If I recall right most of all this has been covered in this long thread over in the Guides & News section. Where I recall reading at least one person that was able to confirm that it isn't the CID alone, if at all.
Thanks guys.. it makes my decision easier not to buy the VZW version easier. The deal they have is good, but not worth my time if I can't unlock it like the Google version.
rester555 said:
Thanks guys.. it makes my decision easier not to buy the VZW version easier. The deal they have is good, but not worth my time if I can't unlock it like the Google version.
Click to expand...
Click to collapse
If you hurry up and get one soon it won't be on 7.1.1 yet. Probably not till the end of January will they actually ship with it. They won't unbox phones to install the update. People are still getting them now with 7.1
I much prefer not to have to deal with that BS and wait for price decreases for the Google store version or through other means.

Is my model unlocked or not, and other stuff

Hi all,
I have a HTC that when I bought it, they SAID it should have been unlocked but I don't know if that means my bootloader is unlocked or something else. how can I tell if my model is unlocked model (model is just HTC 10 and I don't have any provider software installed on it either) ... I mainly ask as Android 7 was released to unlocked HTC 10 last year but I got no OTA notifications that it is ready for me.
Also if this doesn't mean that the bootloader unlocked and I need to go through it at HTCDev, then I believe this will wipe the phone... so I need to backup my stuff before I can unlock the bootloader, so I can root my phone, so I can install my backup stuff (Titanium Backup) any help on this one? i'm used to Samsung so the changes in how things work I'm still getting my head around.
Nobody knows? Is this the correct part of the forums to ask this sort of question? I didn't want to post in the wrong section and this seemed to be the closest fit.
aerospyke said:
Hi all,
I have a HTC that when I bought it, they SAID it should have been unlocked but I don't know if that means my bootloader is unlocked or something else. how can I tell if my model is unlocked model (model is just HTC 10 and I don't have any provider software installed on it either) ... I mainly ask as Android 7 was released to unlocked HTC 10 last year but I got no OTA notifications that it is ready for me.
Also if this doesn't mean that the bootloader unlocked and I need to go through it at HTCDev, then I believe this will wipe the phone... so I need to backup my stuff before I can unlock the bootloader, so I can root my phone, so I can install my backup stuff (Titanium Backup) any help on this one? i'm used to Samsung so the changes in how things work I'm still getting my head around.
Click to expand...
Click to collapse
When you buy a phone and if seller says that phone is unlocked it usually means "carrier/sim unlocked". Your phone might be carrier unlocked, but bootloader unlock is different. When you unlock bootloader than phone gets wiped. Google servers usually backup your apps and some data, but videos/music/photos I backup on my PC by connecting phone to a computer and copying files to a folder.
If you bought directly from HTC w/o purchasing through a carrier (such as Sprint, AT&T, Verizon), then you have an "Unlocked Model". That's completely different from having an unlocked bootloader, which is not necessary to get the Nougat update. If you have an unlocked (carrier-free) HTC 10, then you should be able to get the update. I restored mine to stock, and was able to update to 7.0. It's possible that it's not available in your country yet, or that there's some funny software glitches occurring.
Hope that helps!
Thanks all for the confirmation. So from that I do know from when I got my phone, which was only 4 weeks ago, and no modifications to it whatsoever
a) my phone is carrier unlocked
b) I need to unlock my bootloader but to do that I need to backup my app data, Google didn't backupt he app data when I migrated phones, so all my apps were empty and brand new when it all restored to my new phone... oh well.
c) whilst i SHOULD be eligible for nougat as I have a carrier unlocked HTC 10, perhaps it isn't available in Australia for HTC yet. My colleague who has a pixel XL is still rubbing it in my face that he has 7.1.1 already
Thanks
aerospyke said:
Thanks all for the confirmation. So from that I do know from when I got my phone, which was only 4 weeks ago, and no modifications to it whatsoever
a) my phone is carrier unlocked
b) I need to unlock my bootloader but to do that I need to backup my app data, Google didn't backupt he app data when I migrated phones, so all my apps were empty and brand new when it all restored to my new phone... oh well.
c) whilst i SHOULD be eligible for nougat as I have a carrier unlocked HTC 10, perhaps it isn't available in Australia for HTC yet. My colleague who has a pixel XL is still rubbing it in my face that he has 7.1.1 already
Thanks
Click to expand...
Click to collapse
c) Yeah Nougat is only available for U.S Unlocked (and tmobile as of today) thus far.
Tarima said:
c) Yeah Nougat is only available for U.S Unlocked (and tmobile as of today) thus far.
Click to expand...
Click to collapse
Rats..... i'll just keep waiting, or wipe my device unlocking the bootloader so I can flash a custom ROM like Viper or the like. Decisions. Wonder when the rest of the world will get the update
aerospyke said:
Rats..... i'll just keep waiting, or wipe my device unlocking the bootloader so I can flash a custom ROM like Viper or the like. Decisions. Wonder when the rest of the world will get the update
Click to expand...
Click to collapse
Australia is usually last to get the update.

Possible to root the Pixel on 7.1.2?

Hi All,
I got a bestbuy/verizon pixel xl and am unable to unlock my bootloader to install TWRP and Root my pixel
So, while i was searching for methods to root without unlocking bootloader, i found articles on rooting without TWRP. Is this method still supported on 7.1.2 and Verizon set pixel?
tornado6 said:
Hi All,
I got a bestbuy/verizon pixel xl and am unable to unlock my bootloader to install TWRP and Root my pixel
So, while i was searching for methods to root without unlocking bootloader, i found articles on rooting without TWRP. Is this method still supported on 7.1.2 and Verizon set pixel?
Click to expand...
Click to collapse
You can not root it unless you unlock the bootloader. It has always been that way.
tornado6 said:
Hi All,
I got a bestbuy/verizon pixel xl and am unable to unlock my bootloader to install TWRP and Root my pixel
So, while i was searching for methods to root without unlocking bootloader, i found articles on rooting without TWRP. Is this method still supported on 7.1.2 and Verizon set pixel?
Click to expand...
Click to collapse
I got a new one from Google but mine came from Google warehouse in Carol Illinois it's on October update tho so I can unlock mine if you ever get replacement device that's where it's coming from
Badazzmenc said:
I got a new one from Google but mine came from Google warehouse in Carol Illinois it's on October update tho so I can unlock mine if you ever get replacement device that's where it's coming from
Click to expand...
Click to collapse
If yours is a Google version then it doesn't matter what update you are on, it will still be unlockable.
How do you know what version you have? I got my phone from Verizon but there is no bloat or Verizon anything on it. Could I possibly have a variant that can be unlocked?
Sent from my Pixel using Tapatalk
lowvolt1 said:
How do you know what version you have? I got my phone from Verizon but there is no bloat or Verizon anything on it. Could I possibly have a variant that can be unlocked?
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
Simple, go to Setting/About phone, and tab the Build number text 5 times. Go back to Setting and select Developer options. If the OEM unlocking option is grayed out, it's a Verizon Pixel/XL, if you can toggle the slidder on and off, it's a Google Pixel/XL and can be bootloader unlocked anytime you want, regardless of update.
Seeing as how you purchased it directly from Verizon, I'm fairly certain it's a Verizon Pixel/XL. Any phone purchased directly from Google's Online Store, will always have the option to unlock their bootloader whenever they want.
Thank you. Unfortunately it is gray.
Sent from my Pixel using Tapatalk
lowvolt1 said:
Thank you. Unfortunately it is gray.
Click to expand...
Click to collapse
What version of Android are you on. If it's on 7.1 still then you can still unlock.

Any possibilities to UNLOCK OEM/Bootloader on Android O (Opp3.170518.006)?

Need help here!
Bought an XL via eBay. Found that it's been flashed anyhow. And I can't root/flash ROM or even unlock the bootloader.
Now below is the situation:
1. It's a Verizon, XL, 128GB.
2. It's locked. And OEM unlocking in developer options is GREY.
3. It's stuck in Android O (Opp3.170518.006).
4. dePixel8 doesn't work. Every time I entered the commands "adb shell /data/local/tmp/dePixel8", it ended up with an error.
5. Because of 1., I can't flash TWRP or any bootloader.
I've heard of so-called "FRP Unlock Tool". But it seemed only working on 7.1.2 below and is considered risky for 8.0.
Though 8.0_DP3 is 90% perfect for daily use, I still want to take a chance. But the question is HOW?
doctorm89 said:
Need help here!
Bought an XL via eBay. Found that it's been flashed anyhow. And I can't root/flash ROM or even unlock the bootloader.
Now below is the situation:
1. It's a Verizon, XL, 128GB.
2. It's locked. And OEM unlocking in developer options is GREY.
3. It's stuck in Android O (Opp3.170518.006).
4. dePixel8 doesn't work. Every time I entered the commands "adb shell /data/local/tmp/dePixel8", it ended up with an error.
5. Because of 1., I can't flash TWRP or any bootloader.
I've heard of so-called "FRP Unlock Tool". But it seemed only working on 7.1.2 below and is considered risky for 8.0.
Though 8.0_DP3 is 90% perfect for daily use, I still want to take a chance. But the question is HOW?
Click to expand...
Click to collapse
The only time you could unlock the bootloader on a Verizon Pixel XL was before the operating system updated to Android 7.1.1. Android 7.1.1 was patched so the dePixel8 exploit would no longer work and nobody has found a new way to unlock the bootloader on the Verizon models since then. If you want to downgrade from Android O I think your only option is to deregister your phone from the Android Beta Program. Eventually you will get an OTA that will downgrade your phone back to Nougat but it will also completely wipe your phone including the user data and stored files. You will be starting over from scratch and have to download your user apps again. Unless someone comes up with a new exploit you will not be able to unlock the bootloader or custom flash anything on that phone.
If you wanted to unlock bootloader/flash roms/root etc... you should've come here first to check, then checked with the seller on ebay.
however, your options are:
1) put up with phone in stock (it's really not that bad - which is why development isn't into multiple pages of current roms)
2) sell it and get a google version rather than Verizon

Pixel XL Bootloader unlocking scenario

Hello,
Just want quick help from the experts to ensure I dont end up buying a Verizon unit > 7.1 and end up with a brick which cannot be unlocked and rooted.
So I am on the hunt for a Google branded set. Just inform please ,
1. If it is a google branded set, then can the bootloader be unlocked on it regardless of any locking/unlocking done in the past, even if it is upgraded to the current 8.1 version ROM.
2. I have been eyeing a Google branded unit for which the bootloader was unlocked, then locked again then was flashed with the Beta version of the 8.1 ROM and finally the production version of the 8.1 stock ROM. Would it still be able to unlock the bootloader.
Thanks for filling my knowledge gaps.
Yes to both of your questions.
HyperEscape said:
Hello,
Just want quick help from the experts to ensure I dont end up buying a Verizon unit > 7.1 and end up with a brick which cannot be unlocked and rooted.
So I am on the hunt for a Google branded set. Just inform please ,
1. If it is a google branded set, then can the bootloader be unlocked on it regardless of any locking/unlocking done in the past, even if it is upgraded to the current 8.1 version ROM.
2. I have been eyeing a Google branded unit for which the bootloader was unlocked, then locked again then was flashed with the Beta version of the 8.1 ROM and finally the production version of the 8.1 stock ROM. Would it still be able to unlock the bootloader.
Thanks for filling my knowledge gaps.
Click to expand...
Click to collapse
I can't speak for the Verizon version but if you pay for the EE version to be similar unlocked the toggle to unlock bootloader in developer options stops being greyed out

Categories

Resources