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
Does latest Twrp & root together work well with latest 7.1.1. just got my real blue pixel, read some posts and found the new device differs from the old ones.
But I have to root to use the TitaniumBackup and to enable location report and brevent.
and how to tell whether the device is from google store or it is a verizon based device. As I found Verizon login APP under app settings
Yes to first post and as for second check the purchase receipt.
Not kidding. Factory Verizon >is flashed with a Verizon firmware or euro or other, but it is possible to flash any factory image to any Pixel so unclear ultimately without receipt. Check Build Number in settings and compare to factory image list on Google
Latest firmware is for all carriers, so no way to tell without just knowing.. Maybe!
(BTW I do NOT have a Verizon Pixel, but i do have those apps. They install more stuff and enable features if your carrier is Verizon)
Sent from my sailfish using XDA Labs
I manually updated to 26Q with the Google image so I'm not sure how to tell anymore (have VZW Pixel). The way it works is Google will issue the security patches and Verizon will handle the firmware updates. I believe the VZW build will have a different code than the Google updates. That's why the Verizon branded units will get locked down with 7.1.1 and the Play editions won't.
As for TWRP/SU I have the latest and so far I see no issues.
FernBch said:
I manually updated to 26Q with the Google image so I'm not sure how to tell anymore (have VZW Pixel). The way it works is Google will issue the security patches and Verizon will handle the firmware updates. I believe the VZW build will have a different code than the Google updates. That's why the Verizon branded units will get locked down with 7.1.1 and the Play editions won't.
As for TWRP/SU I have the latest and so far I see no issues.
Click to expand...
Click to collapse
Here is my theory.
Google will post the code and it will be the same as Google's, there won't be any separate builds. The locking is some trickery in the code. Based on CID or IMEI.
Sent from my Pixel XL using XDA Labs
TonikJDK said:
Here is my theory.
Google will post the code and it will be the same as Google's, there won't be any separate builds. The locking is some trickery in the code. Based on CID or IMEI.
Sent from my Pixel XL using XDA Labs
Click to expand...
Click to collapse
The locking isn't trickery in the code. Verizon will do as they always have. The update they push will have a locked, AKA different, bootloader. Since that component is different the build will be different. Same old story......
If they were the same builds there would be no way to differentiate between the Verizon and Google versions.
---------- Post added at 01:10 PM ---------- Previous post was at 12:54 PM ----------
You may want to read more here. Pay particular attention to items 5&6. There is no guarantee that the updates for the Pixel/Pixel XL sold by Verizon will get an OS update at the same rime or on the same schedule as the Google sold devices. This will like lead to different build numbers so the two devices can be distinguished. Google will push security updates to all devices but Verizon has control over OS updates to the devices they sell.
https://www.google.com/url?sa=t&sou...SEx8oJKWAQNk7lueQ&sig2=AWtYaP2LMe9rsKQeDjdviQ
FernBch said:
The locking isn't trickery in the code. Verizon will do as they always have. The update they push will have a locked, AKA different, bootloader. Since that component is different the build will be different. Same old story......
If they were the same builds there would be no way to differentiate between the Verizon and Google versions.
---------- Post added at 01:10 PM ---------- Previous post was at 12:54 PM ----------
You may want to read more here. Pay particular attention to items 5&6. There is no guarantee that the updates for the Pixel/Pixel XL sold by Verizon will get an OS update at the same rime or on the same schedule as the Google sold devices. This will like lead to different build numbers so the two devices can be distinguished. Google will push security updates to all devices but Verizon has control over OS updates to the devices they sell.
https://www.google.com/url?sa=t&sou...SEx8oJKWAQNk7lueQ&sig2=AWtYaP2LMe9rsKQeDjdviQ
Click to expand...
Click to collapse
The bootloaders are the same. It's more likely verizon phones are recognized by the IMEI and or CID. If the difference was in the bootloader, you could unlock, flash a Google bootloader (if there was a difference between the Google and Verizon bootloaders) and then relock, update to 7.1.1 and then unlock again. Something you can't do. If you tried it, you'd wish you hadn't.
A simple way to know if your phone is a Verizon or Google phone is to look in developer options and see if OEM unlocking is available to you. If it's grayed out and you can't select it, it's a Verizon device. If not grayed out and you are able to select it, it's a Google device.
Thank you all, the phone is from Google store as the bootloader can easily be unlocked.
FernBch said:
I manually updated to 26Q with the Google image so I'm not sure how to tell anymore (have VZW Pixel). The way it works is Google will issue the security patches and Verizon will handle the firmware updates. I believe the VZW build will have a different code than the Google updates. That's why the Verizon branded units will get locked down with 7.1.1 and the Play editions won't.
As for TWRP/SU I have the latest and so far I see no issues.
Click to expand...
Click to collapse
Hi there. Verizon builds were different than Google's pre 7.1.1 but now they're the same. Reference my post here (applicable part quoted below) and the Google Nexus/Pixel firmware page https://developers.google.com/android/images.
roirraW "edor" ehT said:
One question I've been wondering about and haven't noticed if it's been addressed anywhere, the 7.1.1 builds are all the same for Verizon and non-Verizon. They're all NMF26O for the first release of 7.1.1 and NMF26Q for the second OTA of it.
So I'm wondering if putting a Verizon SIM in does anything anymore if you're on a stock 7.1.1 image. I could relatively easily find out, but it's not a huge priority.
Also, as long as you already unlocked the bootloader, nothing will re-lock it, even Verizon OTAs, unless you manually do so.
No idea if there'll be Verizon-specific builds again later.
Click to expand...
Click to collapse
Might soon find out, reportedly there's a new update for Verizon soon: NMF26U. It's not on Google's page, at least yet. http://forum.xda-developers.com/pixel/how-to/verizon-update-nmf26u-t3527199/post70281819#post70281819
roirraW "edor" ehT said:
Hi there. Verizon builds were different than Google's pre 7.1.1 but now they're the same. Reference my post here (applicable part quoted below) and the Google Nexus/Pixel firmware page https://developers.google.com/android/images.
Might soon find out, reportedly there's a new update for Verizon soon: NMF26U. It's not on Google's page, at least yet. http://forum.xda-developers.com/pix...ate-nmf26u-t3527199/post70281819#post70281819
Click to expand...
Click to collapse
This would fit the pattern for Verizon. In the past, irregardless of device/manufacturer, Verizon would issue a new build. The new build would have a different bootloader that had whatever exploit patched to prevent the new bootloader from being unlocked. The build number would also be different so the different variants could be distinguished from each other. Been on Big Red for a number of years and have watched this game play out time after time.
The details are not exactly clear but the original story from Google/VZW was Google will update all Google sold devices and issue security patches to all devices no matter where bought from. Any OS updates to Verizon devices would come from Verizon. They get the next build from the OEM and make sure it is up to their requirements (and patch if needed) then push it to their devices. Somewhere in the process I am guessing that there is a way to tell what Google sold from what Verizon sold. This would prove or disprove that only Verizon sold devices can actually get locked down if still locked.
Google may have tried to say no to VZW control like that but when it all settles out money is the key. And Google is going to make a bunch......
---------- Post added at 12:07 AM ---------- Previous post was at 12:00 AM ----------
Reading the article and the linked article inside it seems to point out that NMF26U is targeted towards the UK carrier and is supposed to address MMS issues.
FernBch said:
This would fit the pattern for Verizon. In the past, irregardless of device/manufacturer, Verizon would issue a new build. The new build would have a different bootloader that had whatever exploit patched to prevent the new bootloader from being unlocked.
Reading the article and the linked article inside it seems to point out that NMF26U is targeted towards the UK carrier and is supposed to address MMS issues.
Click to expand...
Click to collapse
Regarding the bootloader, it's not handled the same way as on some other devices. The bootloader is the same on both Google Store and Verizon Pixels.
Also from my understanding, the vulnerability wasn't in the bootloader itself.
Take good care of installing TWRP
According to the guide from the developer, I install TWRP step by step,
after fastboot boot path/to/twrp.img, the lockscreen pin/pattern/password did not get prompted.
So I have to reboot, then lost all my data.
Therefore, it is necessary to clear all your locksreen pin/pattern/password before using TWRP
roirraW "edor" ehT said:
Regarding the bootloader, it's not handled the same way as on some other devices. The bootloader is the same on both Google Store and Verizon Pixels.
Also from my understanding, the vulnerability wasn't in the bootloader itself.
Click to expand...
Click to collapse
Ah. That I did not understand.
So, I guess there is something else I need to learn.
bush911 said:
According to the guide from the developer, I install TWRP step by step,
after fastboot boot path/to/twrp.img, the lockscreen pin/pattern/password did not get prompted.
So I have to reboot, then lost all my data.
Therefore, it is necessary to clear all your locksreen pin/pattern/password before using TWRP
Click to expand...
Click to collapse
I don't believe it matters whether or not there was a password. I've tested this with security on one Pixel, and without on a XL. I flashed stock to both phones prior to testing. I used a PIN password on the Pixel, and never ever installed any type of security on the XL. The key is whether or not the phone is encrypted. I don't have a Google store phone as both of mine came from Verizon. On mine, they were encrypted out of the box. You can see this status under Security, Encryption. Both phones have troubles, but only one out of 6 entrances into TWRP RC1, that they were not successfully decrypted. I then used the Reboot to Recovery from within TWRP, still couldn't decrypt after several reboots. However, in my experiments, if I powered off the devices completely, my very next execution of TWRP decrypted successfully. I don't recall a case in which I had problems after a power off. Just does not make sense. When TWRP doesn't decrypt, you'd see that warning right at the first screen, unless you had previously checked the "Do not warn me again" box. Then you'll see your folders and files all understandably garbled.
I then attempted a couple methods to decrypt the phones from the get-go to see if TWRP would behave if there was no encryption. However, both methods require Magisk which no longer works with 7.1.1. So my attempt to decrypt went nowhere.
All that said, you should never lose your data though. If TWRP doesn't decrypt the phone, and you don't do any file management, the data is still there untouched.
Maybe you are right, I did not catch you very well.
My Pixel was from Google store I tried twice to install TWRP RC1 strictly following the guidelines by the developer.
For the first time, the phone with pattern set up, TWRP did not get me prompted to enter the pin and ended up losing all my personal data.
After rebooted several times, I cleared the pattern and succeeded.
My point is whether TWRP prompts you to enter pin or not, as I never saw this.
quangtran1 said:
I don't believe it matters whether or not there was a password. I've tested this with security on one Pixel, and without on a XL. I flashed stock to both phones prior to testing. I used a PIN password on the Pixel, and never ever installed any type of security on the XL. The key is whether or not the phone is encrypted. I don't have a Google store phone as both of mine came from Verizon. On mine, they were encrypted out of the box. You can see this status under Security, Encryption. Both phones have troubles, but only one out of 6 entrances into TWRP RC1, that they were not successfully decrypted. I then used the Reboot to Recovery from within TWRP, still couldn't decrypt after several reboots. However, in my experiments, if I powered off the devices completely, my very next execution of TWRP decrypted successfully. I don't recall a case in which I had problems after a power off. Just does not make sense. When TWRP doesn't decrypt, you'd see that warning right at the first screen, unless you had previously checked the "Do not warn me again" box. Then you'll see your folders and files all understandably garbled.
I then attempted a couple methods to decrypt the phones from the get-go to see if TWRP would behave if there was no encryption. However, both methods require Magisk which no longer works with 7.1.1. So my attempt to decrypt went nowhere.
All that said, you should never lose your data though. If TWRP doesn't decrypt the phone, and you don't do any file management, the data is still there untouched.
Click to expand...
Click to collapse
bush911 said:
Maybe you are right, I did not catch you very well.
My Pixel was from Google store I tried twice to install TWRP RC1 strictly following the guidelines by the developer.
For the first time, the phone with pattern set up, TWRP did not get me prompted to enter the pin and ended up losing all my personal data.
After rebooted several times, I cleared the pattern and succeeded.
My point is whether TWRP prompts you to enter pin or not, as I never saw this.
Click to expand...
Click to collapse
No big deal. I'm saying there are two different components at play here. One is the built-in encryption structure on the phone. The other is the user-assigned password (PIN, pattern, fingerprint). The PIN, pattern, fingerprint are used to access your phone -- we all recognize that. However, whether or not that password is set, the phone's encryption setting is set elsewhere. Namely, it's under Settings - Encryption. My phone can be passworded, but its data is not encrypted. Or vice versa, it can be encrypted but does not require an unlock to access it.
I'm also making the observation that TWRP sometimes, for whatever reason, does not decrypt the Pixel successfully. Many times I've entered the correct PIN on the TWRP screen, it advanced to the menu screen, but folders and docs were still garbled by encryption. Same thing would also happen on my XL without any password. After I powered off both phones, TWRP magically decrypted both phones, with and without PIN code, successfully by the fact that they now show folders and files properly. So, in my logic, once TWRP irons out its decrypting glitches, this issue goes away. Either that or whenever I figure out how to disable encryption permanently.
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.
Hey all,
Picked up a Pixel 2 back in August from the Verizon Store. November OTA came through and it went bad - real bad. Bricked the device. I contacted Google and they confirmed it was indeed a brick. So I RMA'd it.
They replaced it with what seems like a brand new Pixel 2. Black 128GB. Same phone.
I didn't hook it up to WiFi. I didn't pop in my old SIM. Powered it up and enabled Developer Options.
Unlock Bootloader is NOT greyed out! :good:
I understand people can get lucky and cop an older VZW Pixel 2, not hook it to WiFi or mobile and sideload the stock image, but here's the deal with this RMA'd device:
Android Version: 8.1.0
Android Security Patch Level: May 5, 2018
Build Number: OPM2.17019.029.B1
Isn't that build too high to be a VZW phone w/ that unlockable bootloader option toggle? Shouldn't VZW have patched the developer option by now? Shouldn't Unlock Bootloader be greyed out if this was a VZW phone? Did I get an unlocked, Play Store Pixel 2 in return?
How else can I verify? If I run the bootloader, it does say:
Console: DISABLED
Secure Boot: yes (PRODUCTION)
Device State: locked
Is this okay?
How do I make sure I keep it unlocked if it still could become a VZW phone? Should I flash the latest stock image from Google or is that overkill?
Thanks very much for your help in advance.
-D
dbilodeau said:
Hey all,
Picked up a Pixel 2 back in August from the Verizon Store. November OTA came through and it went bad - real bad. Bricked the device. I contacted Google and they confirmed it was indeed a brick. So I RMA'd it.
They replaced it with what seems like a brand new Pixel 2. Black 128GB. Same phone.
I didn't hook it up to WiFi. I didn't pop in my old SIM. Powered it up and enabled Developer Options.
Unlock Bootloader is NOT greyed out! :good:
I understand people can get lucky and cop an older VZW Pixel 2, not hook it to WiFi or mobile and sideload the stock image, but here's the deal with this RMA'd device:
Android Version: 8.1.0
Android Security Patch Level: May 5, 2018
Build Number: OPM2.17019.029.B1
Isn't that build too high to be a VZW phone w/ that unlockable bootloader option toggle? Shouldn't VZW have patched the developer option by now? Shouldn't Unlock Bootloader be greyed out if this was a VZW phone? Did I get an unlocked, Play Store Pixel 2 in return?
How else can I verify? If I run the bootloader, it does say:
Console: DISABLED
Secure Boot: yes (PRODUCTION)
Device State: locked
Is this okay?
How do I make sure I keep it unlocked if it still could become a VZW phone? Should I flash the latest stock image from Google or is that overkill?
Thanks very much for your help in advance.
-D
Click to expand...
Click to collapse
Don't get too excited, my pixel 2 was RMA'd 2x and can not unlock bootloader. By all accounts I should be able too. I am able to toggle oem unlock, and everything else indicates that I can...however, once I try it fails and on developer settings it's greyed out. Only way to know for sure is to try
AsuraDas said:
Don't get too excited, my pixel 2 was RMA'd 2x and can not unlock bootloader. By all accounts I should be able too. I am able to toggle oem unlock, and everything else indicates that I can...however, once I try it fails and on developer settings it's greyed out. Only way to know for sure is to try
Click to expand...
Click to collapse
Thanks for the reply, AsuraDas. That's disappointing. I'm going to give this a go today. I'll let you know what I find.
I'm debating on what stock image I should push. The same one that's on the device? The newest? What did you do? I see another thread that is similar to mine - I'm going to poke around that one and wing it if I don't hear from anyone more familiar with this than I.
NOPE!
Ha. I definitely have a locked bootloader. How deceptive.
I tried to flash the stock google image, same build that's on there now. No luck.
Tried to fastboot and unlock bootloader. Not allowed.
Oh well!
VERIZON PIXEL 4 XL Root Instructions
NOTE: You must do this PRIOR to activating the phone with Verizon. On my phone once I activated it the OEM bootloader unlock switch became greyed out. (Edit - after rebooting once activated the OEM lock is available again).
Steps I took:
1. Turn on the phone, do not activate the SIM with the carrier.
2. Update to the latest firmware version.
3. Reboot.
4. Enable developer settings, turn on OEM unlock
5. Boot in fastboot mode, run fastboot flash unlock in a shell, reboot.
6. Set up and activate (mine required a chat with Verizon to activate, it wouldn’t activate through the app).
7. Reboot into fastboot, flash a boot.img that has been patched (magisk_patched.img). You can find instructions on this elsewhere.
8. Reboot.
9. Install magisk manager (canary builds). It will say it needs to download a zip to fully install. Allow.
10. Reboot. You’re now rooted.
11. Magisk manager and magisk install may want to upgrade, feel free.
Enjoy!
NOTE: There are several who this has worked for, and some who haven't been able to get it to work. Suggest reading the thread and providing info on phones that do and don't unlock for whatever reason.
Any idea if this would work with the Pixel 4? Thanks
Sent from my [device_name] using XDA-Developers Legacy app
Menardo said:
Any idea if this would work with the Pixel 4? Thanks
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
I can't say for certain, but I think it would just the same. I don't know of any reason it wouldn't.
Im......just going to wait patiently for TWRP to be released for Pixel 4/XL then I will flash Magisk. Suck for now because I so use to adaway, and build.prop tether. The struggle is real.
mr.marcus said:
Im......just going to wait patiently for TWRP to be released for Pixel 4/XL then I will flash Magisk. Suck for now because I so use to adaway, and build.prop tether. The struggle is real.
Click to expand...
Click to collapse
Did they ever get TWRP working correctly on the 3xl??
mr.marcus said:
Im......just going to wait patiently for TWRP to be released for Pixel 4/XL then I will flash Magisk. Suck for now because I so use to adaway, and build.prop tether. The struggle is real.
Click to expand...
Click to collapse
TWRP isn't working on Android 10 currently. It'll need a lot of time to develop, as Google moved a lot of things related to recovery to new sections.
If you really want to root you should definitely patch the appropriate boot image (found here: https://developers.google.com/android/images) and follow the above mentioned steps.
Regarding AdAway: I'm using DNS66 since years. You can download an active the AdAway DNS serting to this app as well an AdBlock will work like a charm. No root needed.
Sent from my HTC U12+ using XDA Labs
Man I wish I saw this first. Well I hope another method comes along for those of us who activated already.
billydroid said:
Man I wish I saw this first. Well I hope another method comes along for those of us who activated already.
Click to expand...
Click to collapse
Well don't feel bad I tried it today before activating and it didn't work. It may wind up being a random occurrence with units that didn't have the IMEI's registered. That's probably why he had to contact Verizon to get the phone to work on their network.
CyberpodS2 said:
Did they ever get TWRP working correctly on the 3xl??
Click to expand...
Click to collapse
Not that I know of. I have been patching boot files for my 3 xl.
wolfu11 said:
Well don't feel bad I tried it today before activating and it didn't work. It may wind up being a random occurrence with units that didn't have the IMEI's registered. That's probably why he had to contact Verizon to get the phone to work on their network.
Click to expand...
Click to collapse
Perhaps. It knew it was a Verizon phone, it had a Verizon activation app. I was very careful to skip activation of any type at the store or when taking it home, so it might be that you need to tell Verizon that you'll activate it later to have the chance to unlock it.
Also, the OEM bootloader unlock has remained available after reboot. I think if it's unlocked in the way I describe it stays unlocked.
mr.marcus said:
Im......just going to wait patiently for TWRP to be released for Pixel 4/XL then I will flash Magisk. Suck for now because I so use to adaway, and build.prop tether. The struggle is real.
Click to expand...
Click to collapse
You might be waiting awhile.
https://www.androidpolice.com/2019/10/24/android-10-twrp-pixel-3-4/?amp
Nice!
madscribblerz said:
VERIZON PIXEL 4 XL Root Instructions
NOTE: You must do this PRIOR to activating the phone with Verizon. On my phone once I activated it the OEM bootloader unlock switch became greyed out. (Edit - after rebooting once activated the OEM lock is available again).
Steps I took:
1. Turn on the phone, do not activate the SIM with the carrier.
2. Update to the latest firmware version.
3. Reboot.
4. Enable developer settings, turn on OEM unlock
5. Boot in fastboot mode, run fastboot flash unlock in a shell, reboot.
6. Set up and activate (mine required a chat with Verizon to activate, it wouldn’t activate through the app).
7. Reboot into fastboot, flash a boot.img that has been patched (magisk_patched.img). You can find instructions on this elsewhere.
8. Reboot.
9. Install magisk manager (canary builds). It will say it needs to download a zip to fully install. Allow.
10. Reboot. You’re now rooted.
11. Magisk manager and magisk install may want to upgrade, feel free.
Enjoy!
Click to expand...
Click to collapse
I was able to do this a couple days ago. I have heard conflicting reports regarding whether this is possible or not but it certainly worked for me. I don't really have any interest in root access on pixel devices so I will just flash the Google store variant factory image (which I think is the one without the C4 in it's build number) and relock it. Maybe I'll play around with it later
Just did the patched boot image method using Magisk to root my 4XL.
Works perfectly with Magisk Canary, exactly the same process I used to do with my Pixel 3
Just an FYI - while Magisk canary builds were required when Android 10 was first released, the Magisk stable version 20 works on Android 10. So while you may use beta or canary builds if you want to, it is no longer a requirement. You can use the latest stable build and be fine.
madscribblerz said:
Perhaps. It knew it was a Verizon phone, it had a Verizon activation app. I was very careful to skip activation of any type at the store or when taking it home, so it might be that you need to tell Verizon that you'll activate it later to have the chance to unlock it.
Also, the OEM bootloader unlock has remained available after reboot. I think if it's unlocked in the way I describe it stays unlocked.
Click to expand...
Click to collapse
I brought it home sealed in the box .
Removed the sim card and powered into bootloader. From there went to recovery mode and did a factory reset. Set it up without signing into my Google account or WiFi and then went to developer options it was grayed out stating"locked carrier device". Did a factory reset as normal and set it up without signing in then took the updates from WiFi. Rebooted and checked developer options still grayed out with same message. I have yet to put a Verizon sim it but did try a different carrier but still no luck. I did have luck with this procedure with one of my Verizon 2xl so I'm pretty sure I did it right. But anyway I didn't see the app you speak of. Where is it located? I only bought this phone because of the discount Verizon gave. I'll be selling it but was curious if it could be unlocked.
Did you unlock your bootloader or just flip the toggle?
wolfu11 said:
I brought it home sealed in the box .
Removed the sim card and powered into bootloader. From there went to recovery mode and did a factory reset. Set it up without signing into my Google account or WiFi and then went to developer options it was grayed out stating"locked carrier device". Did a factory reset as normal and set it up without signing in then took the updates from WiFi. Rebooted and checked developer options still grayed out with same message. I have yet to put a Verizon sim it but did try a different carrier but still no luck. I did have luck with this procedure with one of my Verizon 2xl so I'm pretty sure I did it right. But anyway I didn't see the app you speak of. Where is it located? I only bought this phone because of the discount Verizon gave. I'll be selling it but was curious if it could be unlocked.
Did you unlock your bootloader or just flip the toggle?
Click to expand...
Click to collapse
Both. I'm rooted using a patched magisk boot image, which I couldn't have flashed otherwise.
There does seem to be some mystery sauce here though. I didn't do anything with my SIM, I left it as it was. The app was carrier setup (in notifications prompting to activate) which I didn't launch until after having turned on the toggle, and having run fastboot flashing unlock, then fastboot flash boot magisk_patched.img. I did update to the .C4 release beforehand though, but didn't think that in any way related.
Maybe it was something to do with misconfiguration on the Verizon side - but that seems pretty unlikely given that they didn't even try to activate it and said when I got home to do so - so like you, I came home with it sealed in the box.
Maybe someone else can shed some light - as it seems we're about 50/50 on the unlocks. I bought mine retail at a verizon store. I essentially got it free, as I traded in a Galaxy 5 for $450, which pays out $18.50 a month, and cancelled Fi, which covers the phone's monthly with money coming in.
Damn my device didn't unlock
I wonder if this will work with Spectrum/Charter Wireless since they use Verizon's towers....If anyone knows or has any thoughts I would appreciate it.
wolfu11 said:
I brought it home sealed in the box .
Removed the sim card and powered into bootloader. From there went to recovery mode and did a factory reset. Set it up without signing into my Google account or WiFi and then went to developer options it was grayed out stating"locked carrier device". Did a factory reset as normal and set it up without signing in then took the updates from WiFi. Rebooted and checked developer options still grayed out with same message. I have yet to put a Verizon sim it but did try a different carrier but still no luck. I did have luck with this procedure with one of my Verizon 2xl so I'm pretty sure I did it right. But anyway I didn't see the app you speak of. Where is it located? I only bought this phone because of the discount Verizon gave. I'll be selling it but was curious if it could be unlocked.
Did you unlock your bootloader or just flip the toggle?
Click to expand...
Click to collapse
Did almost the same procedure with my dad's 64 GB black XL. I didn't go into bootloader but I took out the sim, set it up without signing in, and it gave me a greyed out message to turn on WiFi before I could do anything. Tried a factory reset, got the same message. Did another factory reset, set it up without any account but signed into my Wifi network, and it gave me the greyed out message that I can't OEM unlock on carrier locked devices.
When I get my phone I'm thinking about trying a quick WiFi toggle going back to developer settings and trying to unlock before it can communicate with Verizon. I doubt it'll work, but it's worth a shot.
madscribblerz said:
Both. I'm rooted using a patched magisk boot image, which I couldn't have flashed otherwise.
There does seem to be some mystery sauce here though. I didn't do anything with my SIM, I left it as it was. The app was carrier setup (in notifications prompting to activate) which I didn't launch until after having turned on the toggle, and having run fastboot flashing unlock, then fastboot flash boot magisk_patched.img. I did update to the .C4 release beforehand though, but didn't think that in any way related.
Maybe it was something to do with misconfiguration on the Verizon side - but that seems pretty unlikely given that they didn't even try to activate it and said when I got home to do so - so like you, I came home with it sealed in the box.
Maybe someone else can shed some light - as it seems we're about 50/50 on the unlocks. I bought mine retail at a verizon store. I essentially got it free, as I traded in a Galaxy 5 for $450, which pays out $18.50 a month, and cancelled Fi, which covers the phone's monthly with money coming in.
Click to expand...
Click to collapse
I'm a bit confused by the last part, so are you on a Verizon monthly payment plan?
bosox284 said:
Did almost the same procedure with my dad's 64 GB black XL. I didn't go into bootloader but I took out the sim, set it up without signing in, and it gave me a greyed out message to turn on WiFi before I could do anything. Tried a factory reset, got the same message. Did another factory reset, set it up without any account but signed into my Wifi network, and it gave me the greyed out message that I can't OEM unlock on carrier locked devices.
When I get my phone I'm thinking about trying a quick WiFi toggle going back to developer settings and trying to unlock before it can communicate with Verizon. I doubt it'll work, but it's worth a shot.
I'm a bit confused by the last part, so are you on a Verizon monthly payment plan?
Click to expand...
Click to collapse
I am on a 24 month payment plan, but those payments are negated by the trade in and extra money I save having only verizon without Fi.