Flash Google store Pixel image over Verizon Pixel phone??? - Google Pixel Questions & Answers

Hey guys, I'm wondering if anyone has done this, or knows if it's possible to (after unlocking bootloader) flash the Google stock Pixel system image instead of the Verizon one? I'm assuming the hardware and firmware are identical, but am not sure and am not skilled enough (or at all) in code to know if its possible. I bought my phone through Verizon, only because nowhere else had stock. I use it on T-Mobile, but fear there may be some behind the scenes Verizon stuff going on that may hinder my phone on T-Mobile. I haven't experienced any issues yet, but with the Nov security update mentioning a specific fix for wifi calling in New Mexico only on the Verizon pixels, it makes me weary that there is more happening beneath the surface than I am aware of. Thanks for any and all help! Appreciate it.

newbienic said:
Hey guys, I'm wondering if anyone has done this, or knows if it's possible to (after unlocking bootloader) flash the Google stock Pixel system image instead of the Verizon one? I'm assuming the hardware and firmware are identical, but am not sure and am not skilled enough (or at all) in code to know if its possible. I bought my phone through Verizon, only because nowhere else had stock. I use it on T-Mobile, but fear there may be some behind the scenes Verizon stuff going on that may hinder my phone on T-Mobile. I haven't experienced any issues yet, but with the Nov security update mentioning a specific fix for wifi calling in New Mexico only on the Verizon pixels, it makes me weary that there is more happening beneath the surface than I am aware of. Thanks for any and all help! Appreciate it.
Click to expand...
Click to collapse
I did yesterday, bought mine from Best Buy and I unlock the BL. Sideload the OTA yesterday and I used NDE63V that comes with new radio. oh I'm also on Tmobile

jay661972 said:
I did yesterday, bought mine from Best Buy and I unlock the BL. Sideload the OTA yesterday and I used NDE63V that comes with new radio. oh I'm also on Tmobile
Click to expand...
Click to collapse
Awesome! Thanks for the info... Really glad to know I can convert if need be. Thanks again!

jay661972 said:
I did yesterday, bought mine from Best Buy and I unlock the BL. Sideload the OTA yesterday and I used NDE63V that comes with new radio. oh I'm also on Tmobile
Click to expand...
Click to collapse
Interesting side note on this...
I went ahead and unlocked my bootloader and flashed Google's stock Pixel image. All went well, no problems... Until I tried to use Android Pay. It's telling me my software can't be verified. And I out of curiosity checked, and the "allow OEM unlocking" in developer options is still greyed out, and not selectable, even though my BL is unlocked. Hoping this doesn't mean that we can't take an OTA. Weird, I guess we'll have to wait and see when next month's security update comes out...

newbienic said:
Interesting side note on this...
I went ahead and unlocked my bootloader and flashed Google's stock Pixel image. All went well, no problems... Until I tried to use Android Pay. It's telling me my software can't be verified. And I out of curiosity checked, and the "allow OEM unlocking" in developer options is still greyed out, and not selectable, even though my BL is unlocked. Hoping this doesn't mean that we can't take an OTA. Weird, I guess we'll have to wait and see when next month's security update comes out...
Click to expand...
Click to collapse
Just having an unlocked bootloader trips SafetyNet now and you can't use Android Pay without a custom kernel.

ITGuy11 said:
Just having an unlocked bootloader trips SafetyNet now and you can't use Android Pay without a custom kernel.
Click to expand...
Click to collapse
And the OEM unlock option appears to be dependent on device ID (imeid? Ccid?), And not the software. So don't relock it, and you're fine
Sent from my Pixel using Tapatalk

danaff37 said:
And the OEM unlock option appears to be dependent on device ID (imeid? Ccid?), And not the software. So don't relock it, and you're fine
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
One thing I just realized, is in Developer Options, its greyed out like I mentioned, but also says "Bootloader is already unlocked". Which I actually remember seeing on my Nexus 5x when the bootloader was unlocked. It's got me really curious about re locking the bootloader. Mainly cause I actually use Android Pay. Had no idea bootloader unlocks are actually tripping safety net now. Major bummer. If anyone has gone through this process with a Verizon pixel and has actually relocked their bootloader with no issues I'd certainly appreciate any info you have. Otherwise, I may have to dive in blind and hope for the best.

If you want to use Android pay, flash a custom kernel but don't root. Works for me.
Don't relock if you ever want to have it rooted, custom, etc. The unlock method isn't going to survive another security update.
Sent from my Pixel using Tapatalk

danaff37 said:
If you want to use Android pay, flash a custom kernel but don't root. Works for me.
Don't relock if you ever want to have it rooted, custom, etc. The unlock method isn't going to survive another security update.
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
Hypathetically, if I didn't want root or anything custom at all, do you think that relocking the bootloader could cause an issue while using the Stock Google image on a Verizon Pixel? I wish I had more knowledge on this, but I'm pretty in the dark on this stuff as of late... Thanks for your help!

Should be fine if all stock I think, just know that you may not be able to unlock later.
Sent from my Pixel using Tapatalk

newbienic said:
One thing I just realized, is in Developer Options, its greyed out like I mentioned, but also says "Bootloader is already unlocked". Which I actually remember seeing on my Nexus 5x when the bootloader was unlocked. It's got me really curious about re locking the bootloader. Mainly cause I actually use Android Pay. Had no idea bootloader unlocks are actually tripping safety net now. Major bummer. If anyone has gone through this process with a Verizon pixel and has actually relocked their bootloader with no issues I'd certainly appreciate any info you have. Otherwise, I may have to dive in blind and hope for the best.
Click to expand...
Click to collapse
Contrary to what people are saying. You CAN relock your bootloader and then unlock it again later. However, keep in mind that at some point there will likely be an update that blocks the use of dePixel8 and you will no longer be able to unlock the bootloader unless someone writes another exploit.
I would like to find a way to permanently unlock VZW Pixels but until I get one from the Google Store to compare with my Verizon one I don't think I will make much progress.
Relocking your bootloader is as simple as running the "fastboot oem lock" command from the terminal window.
Lastly. If you want to relock the bootloader, make sure your phone is 100% stock image or you risk bricking the phone

If I were to buy the Verizon pixel and flash the unlocked (non European) image. How do you think updates would work? Would I get seamless updates from Google or would I need to flash every Ota manually. Might be too early to tell

b316kane said:
If I were to buy the Verizon pixel and flash the unlocked (non European) image. How do you think updates would work? Would I get seamless updates from Google or would I need to flash every Ota manually. Might be too early to tell
Click to expand...
Click to collapse
This is exactly what I did, and I am curious as well... We'll see next month I guess, but I'm guessing it will take the OTA just fine. My wife has a Pixel from the Google store, and mine is from Verizon. I've compared everything (including booloaders) since flashing the Google store Pixel image, and every informational detail is identical. Not sure if there is some other place hidden to me that might indicate a difference, but I'm thinking that Verizon's Pixel is only different in its official software image... And, that may be it. Please don't take my word for it, I'm no developer, and know very little about any of this, but in my comparisons, they are identical now since flashing Googles official (Non Verizon, Non European) image.
Sidenote, I have yet to try this, but I'm thinking that since I am on Googles image, that if I re-lock my bootloader, that I WILL be able to unlock again after locking. I think Verizon used Googles "Allow OEM Unlocking" software toggle in developer options as the only method to actually keep people from unlocking the bootloader (again speculative), and now that I'm on Googles image, that software "block" should no longer be present, so I should in theory, be free to lock/unlock the same as Pixels purchased from the Google store... Again, I've got no proof, or actual skill to back this up, but it's a theory I have, and if I end up locking my BL again, I'll post what I find...

newbienic said:
I have yet to try this, but I'm thinking that since I am on Googles image, that if I re-lock my bootloader, that I WILL be able to unlock again after locking.
Click to expand...
Click to collapse
In the Verizon unlocking threads the people that tried relocking reported that they were unable to unlock again without depixel8, which is the same as how the Verizon phone typically works. Some people seem to have gotten into situations that could have been corrected with an unlocked bootloader, but because they had a locked bootloader that couldn't be unlocked using depixel8 they had no easy solution to get their phone working again at this time.
http://forum.xda-developers.com/pixel-xl/how-to/psa-read-relocking-bootloader-t3494615

alluringreality said:
In the Verizon unlocking threads the people that tried relocking reported that they were unable to unlock again without depixel8, which is the same as how the Verizon phone typically works. Some people seem to have gotten into situations that could have been corrected with an unlocked bootloader, but because they had a locked bootloader that couldn't be unlocked using depixel8 they had no easy solution to get their phone working again at this time.
http://forum.xda-developers.com/pixel-xl/how-to/psa-read-relocking-bootloader-t3494615
Click to expand...
Click to collapse
Thanks for the heads up!!! Like I said, I really know nothing, just speculating. Appreciate you looking out.

newbienic said:
Thanks for the heads up!!! Like I said, I really know nothing, just speculating. Appreciate you looking out.
Click to expand...
Click to collapse
I forget where, but I saw written or implied that the "checking for updates" screen about third of way through initial setup of first boot uses WiFi AND sim carrier data to install Verizon custom restrictions and settings that among other effects make depixel8 required.
Even on "non Verizon phones" (which you are saying use the same build images byte to byte?)... You have to either use a SIM card or wifi and google account to allow the developer options to enable OEM unlock.
My theory: In other words, if you don't allow via SIM and a network wifi or data connect, for Verizon to mark your phone, or another carrier, then the phone can not be unlocked. So carrier models may indeed be differentiated from current factory images AFTER boot and setup.
There is a post in Q&A of someone trying to unlock bootloader without loading into the device, not having luck. This is why oem unlock toggle is so important and why people are bricking from locked bootloaders that won't unlock (so no wipe and factory images cannot be flashed.)
Another thing to consider: SIM network lock will not be flashed over.
Sent from my sailfish using XDA Labs

Related

[Q] I want to get my hotspot enabled, so do I need to root to do this?

Hey all, just got my pixel. Wanna stay on stock, but maybe root? I want to get my hotspot enabled, so do I need to root to do this? I'm on sprint. Any guidance! Thank you!
If you don't or can't get hotspot enable you may have to root to get it. Plenty of info on how.
FYI
Since you are on Sprint I'm going to guess you bought directly from Google. To my knowledge you can disregard any convos about updates locking you down. That only seems to affect devices bought through Verizon.
FernBch said:
If you don't or can't get hotspot enable you may have to root to get it. Plenty of info on how.
FYI
Since you are on Sprint I'm going to guess you bought directly from Google. To my knowledge you can disregard any convos about updates locking you down. That only seems to affect devices bought through Verizon.
Click to expand...
Click to collapse
Yes sprint and bought directly from play store.
Guess I'll start with this tool eH?
forum.xda-developers.com/pixel/development/tool-skipsoft-android--google-t3482761
Problem is, I already updated via OTA to latest version. Am I screwed?
Screwed?? If you mean BL locked, no. I have the Verizon branded variant but unlocked, rooted, and flashed SU. When I saw NMF26Q was available from Google I downloaded it, installed via flash-all from fastboot, then rerooted and flashed SU again no problem.
chugger93 said:
Hey all, just got my pixel. Wanna stay on stock, but maybe root? I want to get my hotspot enabled, so do I need to root to do this? I'm on sprint. Any guidance! Thank you!
Click to expand...
Click to collapse
Please look at OP install instructions in this thread.
Please look at OP install instruction in TWRP thread.
I guess you aren't on Telus in Canada or your hotspot would work. When you give no information, too hard to help. But I read this forum so even though I don't have Sprint or Verizon as my provider, I know there are many threads about turning hotspot on for unlimited data plans. Guidance: read those threads too!
Then ask for specific guidance. I don't want to reread for 25 min to find and copy and paste to spoonfeed when you should read. Much nicer to fill in a few missing spots than hold your hand not having a clue of your technical knowledge and skills.
Happy holidays.
Specific guidance: update SDK tools before you start!
Sent from my sailfish using XDA Labs
so I managed to unlock and run the fastboot command to push SuperSU to my new pixel. All seems good so far...but when I restart my device I get a "your device software cant be checked for corruption" message. What is that all about? Assuming from unlocking the bootloader. Is this permanent? or can I now relock bootloader since I'm rooted?
chugger93 said:
so I managed to unlock and run the fastboot command to push SuperSU to my new pixel. All seems good so far...but when I restart my device I get a "your device software cant be checked for corruption" message. What is that all about? Assuming from unlocking the bootloader. Is this permanent?
Click to expand...
Click to collapse
It just means your bootloader is unlocked and isn't anything to be worried about. As long as your bootloader is unlocked it will show.
Sent from my Pixel using Tapatalk
chugger93 said:
so I managed to unlock and run the fastboot command to push SuperSU to my new pixel. All seems good so far...but when I restart my device I get a "your device software cant be checked for corruption" message. What is that all about? Assuming from unlocking the bootloader. Is this permanent?
Click to expand...
Click to collapse
joetheshmo said:
It just means your bootloader is unlocked and isn't anything to be worried about. As long as your bootloader is unlocked it will show.
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
Nothing to worry about. I just ignore it.
joetheshmo said:
It just means your bootloader is unlocked and isn't anything to be worried about. As long as your bootloader is unlocked it will show.
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
That's Verizon's equivalence of "Sorry sucka, you're on your own!"
chugger93 said:
so I managed to unlock and run the fastboot command to push SuperSU to my new pixel. All seems good so far...but when I restart my device I get a "your device software cant be checked for corruption" message. What is that all about? Assuming from unlocking the bootloader. Is this permanent? or can I now relock bootloader since I'm rooted?
Click to expand...
Click to collapse
Do not relock your bootloader unless you are fully 100% stock or you run the risk of bricking your phone
Sent from my Pixel using Tapatalk
joetheshmo said:
Do not relock your bootloader unless you are fully 100% stock or you run the risk of bricking your phone
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
That makes sense. Ya havnt used a ROM or anything, do not plan on it. So for now I'm stock. So I can relock it though, get rid of that message but still maintain SuperSU/root right?
My only goal is to get hotspot working (sprint)
chugger93 said:
That makes sense. Ya havnt used a ROM or anything, do not plan on it. So for now I'm stock. So I can relock it though, get rid of that message but still maintain SuperSU/root right?
My only goal is to get hotspot working (sprint)
Click to expand...
Click to collapse
If you're rooted and have done the tether hack you're no longer stock. Don't lock the bootloader unless you are COMPLETELY stock.
robocuff said:
If you're rooted and have done the tether hack you're no longer stock. Don't lock the bootloader unless you are COMPLETELY stock.
Click to expand...
Click to collapse
Which tether hack? This one? http://forum.xda-developers.com/pixel-xl/themes/mod-tethermod-systemless-install-guide-t3501448
If so, I have not done any tether hack yet....still reading since there are multiple ways to do it. (sprint variant/google play store)
chugger93 said:
That makes sense. Ya havnt used a ROM or anything, do not plan on it. So for now I'm stock. So I can relock it though, get rid of that message but still maintain SuperSU/root right?
My only goal is to get hotspot working (sprint)
Click to expand...
Click to collapse
No, having SuperSU means you are no longer stock. You need all stock images to lock bootloader.
If you need a locked bootloader for Android Pay or some other apps. Install one of the customer kernels, they hide it. You still need to remove SuperSU though. From what I've seen its a bit harder to hide that for now. So you can root, make change for hotspot and remove root.
Otherwise nothing hurts to have your bootloader unlocked. It gives you more options if anything ever goes wrong. You need unlocked bootloader to even load Google factory images.
PS. I'd recommend Franco kernel as it imporoves battery life.
Sent from my Pixel using Tapatalk
chugger93 said:
Hey all, just got my pixel. Wanna stay on stock, but maybe root? I want to get my hotspot enabled, so do I need to root to do this? I'm on sprint. Any guidance! Thank you!
Click to expand...
Click to collapse
No you don't have to root to have hotspot enabled, it's a build-in function. Simply set it up in “wireless & networks” and you are ready to go:laugh:
eos9d said:
No you don't have to root to have hotspot enabled, it's a build-in function. Simply set it up in �wireless & networks� and you are ready to go[emoji23]
Click to expand...
Click to collapse
Depending on his plan, he may not have that option. Many do not, hence still need the tether hack.

Verizon Pixel XL - unlocking bootloader on Oreo

Hi,
I have Oreo on Pixel XL, and was wondering if there's any way to unlock the bootloader with dePixel8 or otherwise so I can install TWRP/root?
Thanks!
No
I was given the phone from a family member. I'm assuming it was Verizon, but I use it on Sprint now. Under developer options, OEM unlocking is greyed out, and it says to go online or talk to carrier.
Surely there's a way to root this phone?
H0wdy said:
I was given the phone from a family member. I'm assuming it was Verizon, but I use it on Sprint now. Under developer options, OEM unlocking is greyed out, and it says to go online or talk to carrier.
Surely there's a way to root this phone?
Click to expand...
Click to collapse
If it's a Verizon phone (sounds like it is), no. There is currently no way to root. If it's a Google phone, it can be done. However, for the option in developer options to not be greyed out, you need to be connected to the internet one way or another. If you are connected and it's still greyed out, it's almost certain that it's a Verizon phone.
robocuff said:
If it's a Verizon phone (sounds like it is), no. There is currently no way to root. If it's a Google phone, it can be done. However, for the option in developer options to not be greyed out, you need to be connected to the internet one way or another. If you are connected and it's still greyed out, it's almost certain that it's a Verizon phone.
Click to expand...
Click to collapse
Robocuff,
Thank you. That seems to be my situation, but I was wondering why this isn't an option?
https://www.xda-developers.com/verizon-pixelpixel-xl-bootloader-unlock-has-been-released/
Does it no longer work? I understand it probably doesn't, but I didn't know if there was another way.
H0wdy said:
Robocuff,
Thank you. That seems to be my situation, but I was wondering why this isn't an option?
https://www.xda-developers.com/verizon-pixelpixel-xl-bootloader-unlock-has-been-released/
Does it no longer work? I understand it probably doesn't, but I didn't know if there was another way.
Click to expand...
Click to collapse
dePixel8 doesn't work anymore. It only worked for a couple months. Google patched the hole that dePixel8 exploited in the December security update. So, any Verizon phone that was updated in December or anytime after and wasn't all ready unlocked, became unlockable after that.
robocuff said:
dePixel8 doesn't work anymore. It only worked for a couple months. Google patched the hole that dePixel8 exploited in the December security update. So, any Verizon phone that was updated in December or anytime after and wasn't all ready unlocked, became unlockable after that.
Click to expand...
Click to collapse
Thanks. I guess I'll wait to see if something else occurs.
I wonder if overwriting the Verizon Pixel's bootloader with a non-Verizon bootloader from one of the factory images would work. The logic behind this is that all G-2PW2100s seemd to have identical hardwares, and factory images contain all the bootloader/radio partition images; so in theory, flashing a non-Verizon factory image should make the device non-Verizon.
(Please note that this is just a theory & I have not tested this. There's a chance that doing this will brick the device.)
AncientDeveloper said:
I wonder if overwriting the Verizon Pixel's bootloader with a non-Verizon bootloader from one of the factory images would work. The logic behind this is that all G-2PW2100s seemd to have identical hardwares, and factory images contain all the bootloader/radio partition images; so in theory, flashing a non-Verizon factory image should make the device non-Verizon.
(Please note that this is just a theory & I have not tested this. There's a chance that doing this will brick the device.)
Click to expand...
Click to collapse
I don't believe this will work. The accepted theory is that Verizon locks the bootloader by IMEI number, so if your phone has an IMEI that is on the list, it will be locked no matter what. However, I'm not sure if anyone has tried to change their IMEI to test this theory. I'm also not sure if you can change your IMEI without root. That would require an unlocked bootloader, so probably no way to test.
jmartin72 said:
I don't believe this will work. The accepted theory is that Verizon locks the bootloader by IMEI number, so if your phone has an IMEI that is on the list, it will be locked no matter what. However, I'm not sure if anyone has tried to change their IMEI to test this theory. I'm also not sure if you can change your IMEI without root. That would require an unlocked bootloader, so probably no way to test.
Click to expand...
Click to collapse
But the bootloader is still locked locally. So even the phone sends the IMEI to Verizon, and Verizon sends some command back to the phone to lock it, it shouldn't require changing the IMEI to unlock.
AncientDeveloper said:
But the bootloader is still locked locally. So even the phone sends the IMEI to Verizon, and Verizon sends some command back to the phone to lock it, it shouldn't require changing the IMEI to unlock.
Click to expand...
Click to collapse
I wish someone could figure out how to get it done.
Hi - My Verizon Pixel XL is on Oreo OPR3 and OEM unlocking is *not* greyed out but bootloader status is LOCKED. Is it possible with my setup?
Edit: OEM unlocking is *not* greyed out even on Wifi
nyisles said:
Hi - My Verizon Pixel XL is on Oreo OPR3 and OEM unlocking is *not* greyed out but bootloader status is LOCKED. Is it possible with my setup?
Click to expand...
Click to collapse
Yep, Google has messed up on quite a few phones. Hit that slider now. That won't unlock it, you still have to issue the fastboot command. But moving that slider now will future proof you if you want to unlock.
jmartin72 said:
I wish someone could figure out how to get it done.
Click to expand...
Click to collapse
While I haven't figured out a way to gain the ability to write to the eMMC, it seems that the last byte on the eMMC controls whether the device is unlockable.
Pixxlman said:
What if we could overwrite the bootloader and leave the sim out of the phone and activate it with wifi then verizon can't check the imei and can't lock it? i have a verizon pixel XL i can try this with if someone could walk me through overwriting a bootloader
Click to expand...
Click to collapse
There are multiple problems with that theory. First, Verizon does not lock them. They all come locked, when they start up they phone home to Google and get permission to unlock. And two, the SIM has nothing to do with locking.
What is the point of Google shipping the phones with two different bootloaders and unlocked and locked states.
Some hope with the clkscrew exploit? Sounded like the phone needed to be rooted to work, but being able to pull trustzone keys from a Google variant could possibly enable a workable patch for the Verizon variant.
Have no idea, but sure sounds plausible.
H0wdy said:
Robocuff,
Thank you. That seems to be my situation, but I was wondering why this isn't an option?
https://www.xda-developers.com/verizon-pixelpixel-xl-bootloader-unlock-has-been-released/
Does it no longer work? I understand it probably doesn't, but I didn't know if there was another way.
Click to expand...
Click to collapse
robocuff said:
dePixel8 doesn't work anymore. It only worked for a couple months. Google patched the hole that dePixel8 exploited in the December security update. So, any Verizon phone that was updated in December or anytime after and wasn't all ready unlocked, became unlockable after that.
Click to expand...
Click to collapse
Google did not close the exploit. Verizon did with the release of 7.1.2 in November 2016.
AncientDeveloper said:
I wonder if overwriting the Verizon Pixel's bootloader with a non-Verizon bootloader from one of the factory images would work. The logic behind this is that all G-2PW2100s seemd to have identical hardwares, and factory images contain all the bootloader/radio partition images; so in theory, flashing a non-Verizon factory image should make the device non-Verizon.
(Please note that this is just a theory & I have not tested this. There's a chance that doing this will brick the device.)
Click to expand...
Click to collapse
The package will probably fail to install after modifying because of improper signature. It has been tried before....
AncientDeveloper said:
While I haven't figured out a way to gain the ability to write to the eMMC, it seems that the last byte on the eMMC controls whether the device is unlockable.
Click to expand...
Click to collapse
Probably encrypted, you don't have access to the correct tools, or both.
Would flashing the original image from Google onto the phone and running depixel then. Would that work? Or has that been tried?
Sent from my Pixel using Tapatalk
gobi42 said:
Would flashing the original image from Google onto the phone and running depixel then. Would that work? Or has that been tried?
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
No. You can't downgrade with a locked bootloader.

Buying Verizon Pixel, have some questions

Hello guys.
I'm going to buy used and bootloader unlocked Verizon Pixel tomorrow and I'm interested in couple of things:
1. Can I flash all the ROMs that are available for Pixel on Verizon version too?
2. Can I properly install TWRP, root using Magisk, etc?
3. Can I properly flash (and downgrade if needed) official system images (and are they ever available for Verizon models?)
4. Can I take part in Android Beta program?
5. Is there anything I should be afraid of?
Thanks in advance.
Make sure it is bootloader unlocked, and not just SIM unlocked. There are not many VZ ones around that are bootloader unlocked. You need that to do the items on you list.
TonikJDK said:
Make sure it is bootloader unlocked, and not just SIM unlocked. There are not many VZ ones around that area bootloader unlocked. You need that to do the items on you list.
Click to expand...
Click to collapse
As I already stated, bootloader is already unlocked.
No one has an answer?
If it's bootloader u locked then yeah u can do all those things. Just do not ever for any reason ever relock the bootloader. Also I believe there have been a few cases where ppl have had semibricks or other issues which required locked stock to fix or somehow resulted in locked stock
I got a replacement about a month ago on my small Pixel and that one was unlocked. However, the one I got from Verizon in store did not have an unlocked bootloader. I'm not sure what the deal is, but maybe getting a replacement from an "accidental" break might do the trick. just to clarify, my first Pixels' usb port got completely fried and started to smell bad whenever it charged, and the phone would get really hot. I am now on 8.1 with an unlocked bootloader but have yet to actually root the phone
KittyRgnarok said:
If it's bootloader u locked then yeah u can do all those things. Just do not ever for any reason ever relock the bootloader. Also I believe there have been a few cases where ppl have had semibricks or other issues which required locked stock to fix or somehow resulted in locked stock
Click to expand...
Click to collapse
Thank you!
gb_14 said:
Thank you!
Click to expand...
Click to collapse
Np

Unlocked Verizon Pixel XL 128GB Bootloader. Is it same as google ver. at that point?

I've been looking for a google purchased Pixel XL 128GB locally for a little while now and I've come across a verizon version that was unlocked when they were first released and is now updated to the latest OS.
Since the bootloader is unlocked is there any difference now between the verizon version and the google purchased version? Any chance to revert back on updated or once the bootloader is loaded it is good to go and nothing to worry about from that point forward?
Thanks for any input on this. I've searched, but couldn't find anything regarding this topic.
live4soccer7 said:
I've been looking for a google purchased Pixel XL 128GB locally for a little while now and I've come across a verizon version that was unlocked when they were first released and is now updated to the latest OS.
Since the bootloader is unlocked is there any difference now between the verizon version and the google purchased version? Any chance to revert back on updated or once the bootloader is loaded it is good to go and nothing to worry about from that point forward?
Thanks for any input on this. I've searched, but couldn't find anything regarding this topic.
Click to expand...
Click to collapse
Nothing to worry about going forward except on thing. If YOU relock it you won't be able to unlock it again. They won't relock it.
TonikJDK said:
Nothing to worry about going forward except on thing. If YOU relock it you won't be able to unlock it again. They won't relock it.
Click to expand...
Click to collapse
Thanks! Is there a failsafe I could add in so that it WON'T LET ME LOCK IT?
live4soccer7 said:
Thanks! Is there a failsafe I could add in so that it WON'T LET ME LOCK IT?
Click to expand...
Click to collapse
It requires a manual command in fastboot. Doubt you'll do that accidently.
you definitely dont need a failsafe to avoid relocking it as its really not something you can do accidentally. since you are getting an unlocked version i also assume you will be loading custom firmware in which case it is common sense not to relock it or you will literally brick the phone anyways
KittyRgnarok said:
you definitely dont need a failsafe to avoid relocking it as its really not something you can do accidentally. since you are getting an unlocked version i also assume you will be loading custom firmware in which case it is common sense not to relock it or you will literally brick the phone anyways
Click to expand...
Click to collapse
Thanks everyone, that's exactly what I was looking for. I'm curious, what happens if I toggle the OEM unlock option on/off?
live4soccer7 said:
I'm curious, what happens if I toggle the OEM unlock option on/off?
Click to expand...
Click to collapse
That switch has been grayed out after the Verizon unlock, and it reads "Bootloader is already unlocked", so as far as I know it's not possible to toggle.
Thanks! Much appreciated.
Enjoy your Pixel and happy modding mate

Can I unlock a previously unlocked bootloader?

I had my bootloader unlocked since the pixel came out, and just recently re-locked it through SkipSoft Android ToolKit. I needed to use the Android Pay and didn't have the time to figure out and install Magdisk. I had foolishly assumed that since it was already unlocked that I could easily unlock it again. I was wrong lol. I tried several times in the toolkit with no success.
Is there any hope for this pixel?
wheelbarrel said:
I had my bootloader unlocked since the pixel came out, and just recently re-locked it through SkipSoft Android ToolKit. I needed to use the Android Pay and didn't have the time to figure out and install Magdisk. I had foolishly assumed that since it was already unlocked that I could easily unlock it again. I was wrong lol. I tried several times in the toolkit with no success.
Is there any hope for this pixel?
Click to expand...
Click to collapse
If it's a Verizon one probably not. If it's a Google store pixel, Yes just unlock it again. It will wipe again.
Why did you relock it in the first place
KittyRgnarok said:
Why did you relock it in the first place
Click to expand...
Click to collapse
I needed to use Android Pay, the Tap 'n Go feature. I didnt have time to figure out how to hide root so the app would work. I just thought since it was already unlocked it could easily unlock. I guess I am staying stock lol
And it was purchased through verizon but is now on T-Mobile.
wheelbarrel said:
I needed to use Android Pay, the Tap 'n Go feature. I didnt have time to figure out how to hide root so the app would work. I just thought since it was already unlocked it could easily unlock. I guess I am staying stock lol
And it was purchased through verizon but is now on T-Mobile.
Click to expand...
Click to collapse
Magisk very easily fixes Android pay not working with an unlocked phone. There are like 3 different threads specifically saying hey there is no real reason to ever relock this phone and if you do to be extremely careful
---------- Post added at 06:46 PM ---------- Previous post was at 06:45 PM ----------
Also you purchased it through Verizon so no it isn't easy to reunlock. You will be stuck with the locked bootloader for the foreseeable future. For future reference do not ever buy a phone you intend to mod from Verizon or AT&T
KittyRgnarok said:
Magisk very easily fixes Android pay not working with an unlocked phone. There are like 3 different threads specifically saying hey there is no real reason to ever relock this phone and if you do to be extremely careful
---------- Post added at 06:46 PM ---------- Previous post was at 06:45 PM ----------
Also you purchased it through Verizon so no it isn't easy to reunlock. You will be stuck with the locked bootloader for the foreseeable future. For future reference do not ever buy a phone you intend to mod from Verizon or AT&T
Click to expand...
Click to collapse
Yeah, it does appear that you'll be stuck with a locked bootloader on the Verizon branded phone. I believe that BigRed is using the IMEI number so regardless of SIM, the 'mothership' sends out the command to lock it down. However, I would be interested to see what would happen if you send the OEM Unlock command.
And as far as saying that "do not ever buy a phone you intend to mode frrom VZW or AT&T" not sure I agree entirely...but certainly have to know the risks and limitations, especially if exploits are found. That's one of the reasons I don't use automated kits. I need to know exactly what's happening and commands being sent to my VZW phones. I've been on Verizon and AT&T for quite some time. However, I always find a phone that has an exploit for root. Good luck!
b00ster23 said:
Yeah, it does appear that you'll be stuck with a locked bootloader on the Verizon branded phone. I believe that BigRed is using the IMEI number so regardless of SIM, the 'mothership' sends out the command to lock it down. However, I would be interested to see what would happen if you send the OEM Unlock command.
And as far as saying that "do not ever buy a phone you intend to mode frrom VZW or AT&T" not sure I agree entirely...but certainly have to know the risks and limitations, especially if exploits are found. That's one of the reasons I don't use automated kits. I need to know exactly what's happening and commands being sent to my VZW phones. I've been on Verizon and AT&T for quite some time. However, I always find a phone that has an exploit for root. Good luck!
Click to expand...
Click to collapse
Using them as a carrier is (almost) fine, but it shouldn't be necessary to use an exploit to unlock your phone and they do shady custom bootloader **** on almost all of their phones
KittyRgnarok said:
Using them as a carrier is (almost) fine, but it shouldn't be necessary to use an exploit to unlock your phone and they do shady custom bootloader **** on almost all of their phones
Click to expand...
Click to collapse
Yup... agreed. Shouldn't be necessary, but unfortunately the law is in their side. They lock bootloaders to offset reduced hardware pricing, in an effort to cut support cost and limiting possible bricked phones. Trust me don't like it, but if I can get a significantly reduced cost on the phone, and have full admin rights....uhhhh thank u...
b00ster23 said:
Yup... agreed. Shouldn't be necessary, but unfortunately the law is in their side. They lock bootloaders to offset reduced hardware pricing, in an effort to cut support cost and limiting possible bricked phones. Trust me don't like it, but if I can get a significantly reduced cost on the phone, and have full admin rights....uhhhh thank u...
Click to expand...
Click to collapse
Tru Tru
wheelbarrel said:
I needed to use Android Pay, the Tap 'n Go feature. I didnt have time to figure out how to hide root so the app would work. I just thought since it was already unlocked it could easily unlock. I guess I am staying stock lol
And it was purchased through verizon but is now on T-Mobile.
Click to expand...
Click to collapse
My pixel passed safety net without any issues with an unlocked bootloader running a custom kernel without root. I don't think safety net checks the bootloader (could be wrong)
Poebat said:
My pixel passed safety net without any issues with an unlocked bootloader running a custom kernel without root. I don't think safety net checks the bootloader (could be wrong)
Click to expand...
Click to collapse
Yes Safety Net does check the BL. The reason yours passes is because of the custom kernel. I seen a post for an 'almost' stock kernel for the PIXEL2 that passes SN, without root if that's all u need. The kernel has a patch for only the Safety Net. But again that's the PIXEL2
b00ster23 said:
Yes Safety Net does check the BL. The reason yours passes is because of the custom kernel. I seen a post for an 'almost' stock kernel for the PIXEL2 that passes SN, without root if that's all u need. The kernel has a patch for only the Safety Net. But again that's the PIXEL2
Click to expand...
Click to collapse
Ah. I figured that might be the case.
b00ster23 said:
Yes Safety Net does check the BL. The reason yours passes is because of the custom kernel. I seen a post for an 'almost' stock kernel for the PIXEL2 that passes SN, without root if that's all u need. The kernel has a patch for only the Safety Net. But again that's the PIXEL2
Click to expand...
Click to collapse
I mean almost every custom kernel for pixel og has proper safety net support
I appreciate all your input everyone! Unfortunately I am going to have to wait until it's time to buy a Pixel 2 lol, which is getting close
This is proof you should read EVERYTHING first lol

Categories

Resources