Related
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
With it being Black Friday, Verizon is selling the Pixel for a great price. I was wondering if it's possible to unlock the bootloader, flash a stock update from Google (not Verizon) to the phone, all while keeping Android Pay and being able to update the day a new update comes out? If this is possible how would I go about it? If I can't have Android Pay I can live without, but will I still be able to have the unlocked bootloader permanently along with the Google updates? Thank you! :good:
tidall said:
With it being Black Friday, Verizon is selling the Pixel for a great price. I was wondering if it's possible to unlock the bootloader, flash a stock update from Google (not Verizon) to the phone, all while keeping Android Pay and being able to update the day a new update comes out? If this is possible how would I go about it? If I can't have Android Pay I can live without, but will I still be able to have the unlocked bootloader permanently along with the Google updates? Thank you! :good:
Click to expand...
Click to collapse
No, no, no and no.
bobby janow said:
No, no, no and no.
Click to expand...
Click to collapse
Was the bootloader unlock (dePixel8) patched?
Coronado is dead said:
Was the bootloader unlock (dePixel8) patched?
Click to expand...
Click to collapse
Not sure, but I believe at some point it will be. This is not the device to buy if you want an unlocked bootloader with root.
I just joined the $240 Verizon Nexus Pixel club and have always unlocked, rooted and used custom Roms for every single device I've bought from Google. If there is an easy way to convert a Verizon Pixel to a Google Pixel I would be all over it. But maybe this is that one time that I'm going to stay stock.
Coronado is dead said:
Was the bootloader unlock (dePixel8) patched?
Click to expand...
Click to collapse
No, it hasn't been patched as of the November update. I took the update and unlocked with no problem. http://theroot.ninja/depixel8.html Note that it says... "Unexpectedly, dePixel8 was not patched in NDE63X. Have fun". Do it now while you still can.
I can confirm that the Verizon Pixel can be unlocked. I got a 128gb today for $15/month. I have grandfathered unlimited data so this is the first Verizon promo phone I've bought in a while. Unlocked, flashed TWRP, rooted, and enabled tethering.
joshw0000 said:
I can confirm that the Verizon Pixel can be unlocked. I got a 128gb today for $15/month. I have grandfathered unlimited data so this is the first Verizon promo phone I've bought in a while. Unlocked, flashed TWRP, rooted, and enabled tethering.
Click to expand...
Click to collapse
So how would one go about doing this? And would you have to relock the bootloader and unroot to update?
Just download and run DePixel8 to unlock.
Your phone should update if you don't flash any roms or mods. But that's no fun. You'll get updates quicker by installing them manually.
Sent from my Pixel using Tapatalk
joshw0000 said:
Just download and run DePixel8 to unlock.
Your phone should update if you don't flash any roms or mods. But that's no fun. You'll get updates quicker by installing them manually.
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
Just a word of caution if you're going that route.
http://forum.xda-developers.com/pixel/how-to/psa-read-relocking-bootloader-t3494614
bobby janow said:
Just a word of caution if you're going that route.
http://forum.xda-developers.com/pixel/how-to/psa-read-relocking-bootloader-t3494614
Click to expand...
Click to collapse
Yes that's pretty common. Been that way since the original Nexus. You shouldn't ever re-lock unless you're returning for warranty. And if you do if should happen right after you flashed stock firmware.
Sent from my Pixel using Tapatalk
joshw0000 said:
Yes that's pretty common. Been that way since the original Nexus. You shouldn't ever re-lock unless you're returning for warranty. And if you do if should happen right after you flashed stock firmware.
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
No that's not correct. I unlocked, locked, unlocked and relocked my Nexus 5x recently. I was testing SafetyNet with an unlocked bootloader which failed all the time. So I finally relocked and left it that way. The Verizon Pixel is not like that. I think because you have to use a program to unlock and not just do it in bootloader.
However, you are correct in that you shouldn't relock your bl unless you have flashed the stock firmware, specifically recovery. Relocking and unlocking will wipe everything on your device, sdcard included.
joshw0000 said:
Just download and run DePixel8 to unlock.
Your phone should update if you don't flash any roms or mods. But that's no fun. You'll get updates quicker by installing them manually.
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
Will I be able to flash updates all while keeping the bootloader unlocked? Or will updates relock my bootloader and soft brick my phone?
tidall said:
Will I be able to flash updates all while keeping the bootloader unlocked? Or will updates relock my bootloader and soft brick my phone?
Click to expand...
Click to collapse
Updates won't relock.
Sent from my Pixel using Tapatalk
---------- Post added at 05:32 PM ---------- Previous post was at 05:30 PM ----------
bobby janow said:
No that's not correct. I unlocked, locked, unlocked and relocked my Nexus 5x recently. I was testing SafetyNet with an unlocked bootloader which failed all the time. So I finally relocked and left it that way. The Verizon Pixel is not like that. I think because you have to use a program to unlock and not just do it in bootloader.
However, you are correct in that you shouldn't relock your bl unless you have flashed the stock firmware, specifically recovery. Relocking and unlocking will wipe everything on your device, sdcard included.
Click to expand...
Click to collapse
I don't know for sure but I think the reasoning for not relocking is that Verizon/Google will likely patch the DePixel8 exploit in future builds.
Sent from my Pixel using Tapatalk
joshw0000 said:
Just download and run DePixel8 to unlock.
Your phone should update if you don't flash any roms or mods. But that's no fun. You'll get updates quicker by installing them manually.
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
joshw0000 said:
Updates won't relock.
Sent from my Pixel using Tapatalk
---------- Post added at 05:32 PM ---------- Previous post was at 05:30 PM ----------
I don't know for sure but I think the reasoning for not relocking is that Verizon/Google will likely patch the DePixel8 exploit in future builds.
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
Where will I be able to download updates and how would I flash them? ( sorry for all the questions I haven't had an Android in a while )
tidall said:
Where will I be able to download updates and how would I flash them? ( sorry for all the questions I haven't had an Android in a while )
Click to expand...
Click to collapse
Here on XDA. Probably with Fsstboot.
Sent from my Pixel using Tapatalk
joshw0000 said:
Here on XDA. Probably with Fsstboot.
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
Would I download the Verizon version or just the completely stock Google version?
I'm in a Verizon pixel and installed "v" version instead of "u" everything is working. What's different about the international version?
Just a fix for European carriers. I'm using the same on Verizon as well with no issues. You're good.
Nick_Gl said:
I'm in a Verizon pixel and installed "v" version instead of "u" everything is working. What's different about the international version?
Click to expand...
Click to collapse
Nothing it will work just fine. From what I understand just a slight difference for Europe. It will be fine.
What I'd like to know is if I were completely stock on V, bootloader relocked, what updates would I get, if any? Would I get the next version for Europe, or would it be the other? I'm in the US on Verizon (device from Google).
jesssiii said:
What I'd like to know is if I were completely stock on V, bootloader relocked, what updates would I get, if any? Would I get the next version for Europe, or would it be the other? I'm in the US on Verizon (device from Google).
Click to expand...
Click to collapse
You probably wouldn't get any updates. The trigger for that version probably wouldn't get to you. But I am not certain on that. Might be able to pull it via wifi with no SIM in it.
Do NOT relock your bootloader unless it is just before you are going to put it in a box to send back for warranty.
jesssiii said:
What I'd like to know is if I were completely stock on V, bootloader relocked, what updates would I get, if any? Would I get the next version for Europe, or would it be the other? I'm in the US on Verizon (device from Google).
Click to expand...
Click to collapse
Why would you think you'd get the European version if you are in the US? Did I miss something in your question? You'd get the U version if you're on Verizon and you can lock and relock the bootloader at your discretion since you have the Google Pixel. I mean if you want to keep wiping your data each time, that is.
bobby janow said:
Why would you think you'd get the European version if you are in the US? Did I miss something in your question? You'd get the U version if you're on Verizon and you can lock and relock the bootloader at your discretion since you have the Google Pixel. I mean if you want to keep wiping your data each time, that is.
Click to expand...
Click to collapse
He made it sound like his pixel is from Verizon. In that case he can't lock and unlock the bootloader whenever he wants.
To the OP. What are you trying to do? It doesn't matter if you are on V. If it makes you feel better just flash U then. As long as you don't have twrp or root you will still get OTAs. Why would you want to lock your bootloader? You can have an unlocked bootloader and still take normal OTAs just fine . it its a Verizon sold pixel you won't be able to unlock once you lock.
fritzgerald said:
Just a fix for European carriers. I'm using the same on Verizon as well with no issues. You're good.
Click to expand...
Click to collapse
Thanks wasn't sure. I'll just remember to side load the correct one in February.
aholeinthewor1d said:
He made it sound like his pixel is from Verizon. <snip>
Click to expand...
Click to collapse
It was certainly a little bit confusing, however, the last part of his post it said.. (device from Google) so I figured it was a GPixel activated on Verizon.
I unlocked the bootloader on my Verizon Pixel 2 - just because I could - but I don't really have any need for root and don't want to deal with the tripped safetynet and manual updates. What I'd like to do is flash a ROM that would convert this to a Google Pixel 2 (that gets OTAs directly from Google) and then relock the bootloader. Is this possible?
8.1 was unified so both Verizon and Google has the same firmware. Maybe that's why it "broke" the bootloader for us to be able to Unlock it.
I hope it'll continue to be unified so we get updates as fast as the Google Pixel 2.
guapinoy said:
8.1 was unified so both Verizon and Google has the same firmware. Maybe that's why it "broke" the bootloader for us to be able to Unlock it.
I hope it'll continue to be unified so we get updates as fast as the Google Pixel 2.
Click to expand...
Click to collapse
Thanks, I didn't realize they had merged. Your theory about why the bootloader broke is definitely possible, but if so I'm not sure why the XL wouldn't have received the same treatment.
These may be stupid questions but I have tried everything I can think of.
I am on a Verizon pixel 2, locked bootloader, running the current release of android 9.
I am unable to toggle the "OEM Unlocking" option in developer settings
I followed this guide to enable the toggle but ADB/Fastboot still gives me the "Flashing Unlock is not allowed" message when i try to run "fastboot oem unlock" or "fastboot flashing unlock".
Ultimately I would like to be able to root my Pixel 2, but right now I would settle for being able to downgrade Google Play Services to version 12.6.85 because reasons. There does not appear to be a compatible APK for this version of play services and Android 9 on the Pixel 2 (that I have been able to find yet)
Is anyone aware of how I could do the following:
1. unlock my bootloader?
or
2. downgrade to any android 8 version?
or
3. downgrade google play services to 12.6.85 on Pixel 2 Android 9?
The guide you posted is for the original Pixel.
Verizon Pixel 2 has a locked bootloader, and Verizon has disallowed the option of unlocking.
Early in the year, a user here stumbled upon a few commands that would bootloader-unlock the vzw p2. However, any firmware past January (I think) has been updated to protect against this exploit. So you missed the window on that.
I don't think android allows downgrading while the bootloader is locked.
I'm not sure about downgrading play services, but you could easily get the desired .apk from apk-mirror, and attempt to install it. I'm guessing you're going to get an error. In that case, considering you don't have system r/w permission, I don't see any way you'd be able to downgrade play services.
So, short of someone coming along and finding another way to bypass vzw's restrictions, you're stuck on 9.
use skipsoft android toolkit.
bmw9651 said:
use skipsoft android toolkit.
Click to expand...
Click to collapse
That won't work. You can't downgrade to an earlier version, and if you've taken any updates past the January VZW variant, nothing can be done. Sorry....
I was able to wipe system and install 8.1.0 after bricking on 9 pie.
bmw9651 said:
I was able to wipe system and install 8.1.0 after bricking on 9 pie.
Click to expand...
Click to collapse
With a locked bootloader on a Verizon Pixel 2?
yes I wiped it and went back to 810. bootloader has been unlocked as well. use fastboot and adb....... code: fastboot flash lock_critical. to unlock BL.
use skipsoft tool kit to wipe and reinstall OS to 8.1.,0.
bmw9651 said:
yes I wiped it and went back to 810. bootloader has been unlocked as well. use fastboot and adb....... code: fastboot flash lock_critical. to unlock BL.
use skipsoft tool kit to wipe and reinstall OS to 8.1.,0.
Click to expand...
Click to collapse
What I'm getting at is that your bootloader was unlocked _before_ you did everything. OP doesn't have that luxury.
DuckRuckus said:
What I'm getting at is that your bootloader was unlocked _before_ you did everything. OP doesn't have that luxury.
Click to expand...
Click to collapse
Yeah he's full of it if he's saying otherwise. There is no way it would let you downgrade bootloaders in stock recovery.
Yes BL was unlocked before doing the change. I just rooted it with the skipsoft toolkit Magsik way. after trying others on it. with the skipsoft toolkit you can wipe it and go back to jan 2018 builds of you wish. there are many options on it to choose from.
---------- Post added at 05:22 PM ---------- Previous post was at 05:13 PM ----------
when i got my pixel 2 first thing I did was unlock boot-loader. fastboot flash lock_critical. is the command to do this . To the OP don't worry too much the pixel 3 is coming out soon. BUY it From the Google Store. you will be able to unlock BL and do as you please. DO NOT Buy from Verizon.
bmw9651 said:
Yes BL was unlocked before doing the change. I just rooted it with the skipsoft toolkit Magsik way. after trying others on it. with the skipsoft toolkit you can wipe it and go back to jan 2018 builds of you wish. there are many options on it to choose from.
---------- Post added at 05:22 PM ---------- Previous post was at 05:13 PM ----------
when i got my pixel 2 first thing I did was unlock boot-loader. fastboot flash lock_critical. is the command to do this . To the OP don't worry too much the pixel 3 is coming out soon. BUY it From the Google Store. you will be able to unlock BL and do as you please. DO NOT Buy from Verizon.
Click to expand...
Click to collapse
unless you need to get an RMA, in which case you get a device that cannot be unlocked, like mine for example.
crixley said:
unless you need to get an RMA, in which case you get a device that cannot be unlocked, like mine for example.
Click to expand...
Click to collapse
By that do you mean that you submitted a warranty claim to google? You must not have. I am a Project Fi customer so I never have to think about such things. But yeah, if you bought your pixel from the google website, hooked it up to Verizon service and THEN called Verizon customer service and requested a warranty replacement or an Insurance claim then yeah. In that case you probably would receive a device with a locked bootloader because that's all Verizon deals with as far as I know. I submitted a warranty claim to Project Fi and The device they sent me came with an unlocked bootloader. I think I would have thrown a fit if they had sent a locked one. I would have been on the phone with a Supervisor stating that "the unlocked bootloader feature was 100% the reason I chose to buy the phone directly from google!" I would not have left them alone until I got my way. lol
KirkH420 said:
By that do you mean that you submitted a warranty claim to google? You must not have. I am a Project Fi customer so I never have to think about such things. But yeah, if you bought your pixel from the google website, hooked it up to Verizon service and THEN called Verizon customer service and requested a warranty replacement or an Insurance claim then yeah. In that case you probably would receive a device with a locked bootloader because that's all Verizon deals with as far as I know. I submitted a warranty claim to Project Fi and The device they sent me came with an unlocked bootloader. I think I would have thrown a fit if they had sent a locked one. I would have been on the phone with a Supervisor stating that "the unlocked bootloader feature was 100% the reason I chose to buy the phone directly from google!" I would not have left them alone until I got my way. lol
Click to expand...
Click to collapse
Yes, as have many others. I'm from Canada, device was bought through google and RMA'd through google. Has nothing to do with Verizon, there are tons of threads about it.
Another alternative, albeit a bit more convoluted, would be to update your current device to the latest update. Back up your user data as best you can, then factory reset, put it on Swappa, and then use the proceeds to purchase a secondhand Google variant with identical specs as the original. At least that way you won't have to deal with any more bootloader shenanigans. If your device is still in good shape and you're savvy enough about it, you may be able to come close to break-even.