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.
Related
Just a thread for the few USCC people here - I've tried to UL the bootloader using TMO instructions - no go. It will reboot into the bootloader but it asks for the unlock.bin key (fastboot oem unlock returns an unknown command error). So at least theirs that much
Phone will also boot into recovery, and I get the associated normal options there (clear, mount /system, wide device/cache, load update via ADB, load update via SD, view recovery logs, etc). Interesting thing happens when I select "run graphics test" from the recovery menu - it gives an error, then the "no command" icon, then multicolor circles rotating - but it says "erasing" then "installing system update" then goes back to the recovery menu. Not sure if it's normal, but it's interesting.
I'm not a dev or a software guy really, but would like to hear some thoughts on the USCC version...would love to have root like the TMO - especially since it will get into the fastboot menu. Wish I knew more so I could be more help.
Same I'd like to here more about this since the unlocked version comes with an unlocked bootloader. I think it's because the T-Mobile version got released first so they had the jump start, and the unlocked version took till the 11th to be released so it's like we're late.
Killah1994 said:
Same I'd like to here more about this since the unlocked version comes with an unlocked bootloader. I think it's because the T-Mobile version got released first so they had the jump start, and the unlocked version took till the 11th to be released so it's like we're late.
Click to expand...
Click to collapse
you are talking about three different devices lol.. apparently USCC v20 is locked like everyone else.. TMobile typically allows BL unlocks, not because it was out first? and the unlocked variant is obviously from LG and unlockable by default...
elliwigy said:
you are talking about three different devices lol.. apparently USCC v20 is locked like everyone else.. TMobile typically allows BL unlocks, not because it was out first? and the unlocked variant is obviously from LG and unlockable by default...
Click to expand...
Click to collapse
There you go, knew I was getting something mixed up.
us996 comes with an unlocked bootloader? what? I'm pretty sure mines locked like the rest...
Sent from my LG-US996 using Tapatalk
jayochs said:
us996 comes with an unlocked bootloader? what? I'm pretty sure mines locked like the rest...
Click to expand...
Click to collapse
if u read my previous post u can see i said the uscc BL is locked lol like everyone else
I seem to have a US996, but I got it early on. I believe it to be bootloader locked though, even though it's a developers device. I'm almost 100% sure it's the sim unlocked version as I tried a few sims and they worked. Anything I can do to help?
Abumarf said:
I seem to have a US996, but I got it early on. I believe it to be bootloader locked though, even though it's a developers device. I'm almost 100% sure it's the sim unlocked version as I tried a few sims and they worked. Anything I can do to help?
Click to expand...
Click to collapse
I recommended the officially unlocked variant of the V20 to @Abumarf believing he'd have no issues whatsoever in unlocking the bootloader. He purchased one off eBay before the phone was officially released and I believe it came with a user debug kernel. It seems similar to the engineering kernels for Samsung devices, as he has root access through the adb shell. Unlike the temporary root method that @me2151 had posted, it can survive reboots. Yet I'm surprised the fastboot command to unlock the bootloader returns with failure.
Ephemera said:
I recommended the officially unlocked variant of the V20 to @Abumarf believing he'd have no issues whatsoever in unlocking the bootloader. He purchased one off eBay before the phone was officially released and I believe it came with a user debug kernel. It seems similar to the engineering kernels for Samsung devices, as he has root access through the adb shell. Unlike the temporary root method that @me2151 had posted, it can survive reboots. Yet I'm surprised the fastboot command to unlock the bootloader returns with failure.
Click to expand...
Click to collapse
does he have a copy of the debug kernel? you can pm me a link if possible thatd be great so we can take a look at it.. if it is an eng kernel, it could potentially help to root other variants with locked BLs
---------- Post added at 02:41 AM ---------- Previous post was at 02:40 AM ----------
Ephemera said:
I recommended the officially unlocked variant of the V20 to @Abumarf believing he'd have no issues whatsoever in unlocking the bootloader. He purchased one off eBay before the phone was officially released and I believe it came with a user debug kernel. It seems similar to the engineering kernels for Samsung devices, as he has root access through the adb shell. Unlike the temporary root method that @me2151 had posted, it can survive reboots. Yet I'm surprised the fastboot command to unlock the bootloader returns with failure.
Click to expand...
Click to collapse
can you upload your aboot and kernel etc? if theyre eng or debug files im interested to check them out
---------- Post added at 02:41 AM ---------- Previous post was at 02:41 AM ----------
Abumarf said:
I seem to have a US996, but I got it early on. I believe it to be bootloader locked though, even though it's a developers device. I'm almost 100% sure it's the sim unlocked version as I tried a few sims and they worked. Anything I can do to help?
Click to expand...
Click to collapse
can you upload your aboot and kernel etc? if theyre eng or debug files im interested to check them out
@elliwigy I will most likely be selling the phone or handing it over to @Ephemera as I can't use it as a daily driver. We'll update you on what happens. If we do decide to sell, I'll see if we can extract and send them your way before we do.
Abumarf said:
@elliwigy I will most likely be selling the phone or handing it over to @Ephemera as I can't use it as a daily driver. We'll update you on what happens. If we do decide to sell, I'll see if we can extract and send them your way before we do.
Click to expand...
Click to collapse
hopefully you are able to as it shouldnt really take any time at all lol.. it would really help a lot of ppl out if it is in fact a debug kernel..
the root we have is a temp tcp root shell using a context we cant really do anything we need to do at all so it was pretty much a dead end so far
Abumarf said:
@elliwigy I will most likely be selling the phone or handing it over to @Ephemera as I can't use it as a daily driver. We'll update you on what happens. If we do decide to sell, I'll see if we can extract and send them your way before we do.
Click to expand...
Click to collapse
I will pay you for the debug files
I'm no developer or modder. I don't know too much about all that. I would rather not play with it, and that's the reason I'm selling it.
Abumarf said:
I'm no developer or modder. I don't know too much about all that. I would rather not play with it, and that's the reason I'm selling it.
Click to expand...
Click to collapse
you wont b doing anything to the phone.. if u have an adb root shell would just be copying a few files from the phone.. we can even tell you exactly what commands to use to make it easy.. we can invite you to a google hangout even so we can explain each step
Abumarf said:
I'm no developer or modder. I don't know too much about all that. I would rather not play with it, and that's the reason I'm selling it.
Click to expand...
Click to collapse
Whay are you asking for the phone?
I was looking to get what I spent for it, around $800
elliwigy said:
if u read my previous post u can see i said the uscc BL is locked lol like everyone else
Click to expand...
Click to collapse
yeah, the US cellular us996. it's different from the American unlocked us996. according to LG anyway, it lists it as two different phones.
I'm not on a US cellular one. I'm in an unlocked one with Verizon. the post above you said unlocked had unlocked bootloader. mines as unlocked as you get, and it doesn't have an unlocked bootloader.
Sent from my LG V20 US996
http://developer.lge.com/community/...nuId=38&contsTypeCode=QUE&prodTypeCode=MOBILE
Make yourselves heard. Let LG know we want the bootloader to be unlockable on the US996. I've talked to their live chat and they claim that they "didn't know people would want to unlock their bootloader". Show them we do.
Abumarf said:
I was looking to get what I spent for it, around $800
Click to expand...
Click to collapse
Ok if you download terminal emulator and type in get prop and send me the screen shots so i can verify it is indeed a debug kernel i will buy it from you but i would like to have proof of debug kernel
Sure, here it is: https://drive.google.com/file/d/0BwI6DTQJV37Ob1BwRkRab0xPRkk/view?usp=drivesdk
Also the phone is already up on Swappa
---------- Post added at 08:45 PM ---------- Previous post was at 08:36 PM ----------
@rickberg forgot to tag you
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
Hey, I have a OnePlus 3 so I have messed around a lot with my phone, today I saw a Google Pixel at sale for a pretty low price but the guy selling it says that the phone has a Google account on it from the previous owner but it doesn't have a security pattern pin or password to get into the phone, it just has swipe to unlock. He says he can't use the play store but he has downloaded apks directly and can use the phone with some limitations. My question is, I use an OnePlus 3 and in that situation I could unlock my bootloader and flash a different ROM and fully unlock it. Is that not possible on the Pixel? I can't just go into the developer settings, enable oem unlocking, boot into fastboot and unlock the bootloader and flash a different rom or factory reset it without triggering FRP? How does that work? Given the circumstances is there any way to factory reset or flash a different rom on that pixel without issues? Thanks!
Hello, the Verizon version of the Pixel has a locked bootloader and can NOT be unlocked, some people have bought a Verizon version but were lucky to get it with 7.1 which is the only version that can have the bootloader unlocked. If the Pixel is the unlocked version (Google Store) or Verizon version, it can be unlocked using different methods until it reaches the December 5th Security Patch, at that point there is only one method right now to bypass the frp for the December 5th patch - current patch.
If I understand correctly, the phone already has frp, you need to find out what version the pixel is and what security patch does it have.
The seller might of used dirty-c0ws method to install a home launcher and other apps but none of the google apps work and you can't add your google account to it until you completely remove frp.
droid4lif3 said:
Hello, the Verizon version of the Pixel has a locked bootloader and can NOT be unlocked, some people have bought a Verizon version but were lucky to get it with 7.1 which is the only version that can have the bootloader unlocked. If the Pixel is the unlocked version (Google Store) or Verizon version, it can be unlocked using different methods until it reaches the December 5th Security Patch, at that point there is only one method right now to bypass the frp for the December 5th patch - current patch.
If I understand correctly, the phone already has frp, you need to find out what version the pixel is and what security patch does it have.
The seller might of used dirty-c0ws method to install a home launcher and other apps but none of the google apps work and you can't add your google account to it until you completely remove frp.
Click to expand...
Click to collapse
It hasn't been reset yet, it's on 7.1.1 so I believe the security patch on it is later than December. I can't access developer options, enable oem unlocking and proceed with the steps to flash a custom ROM?
It's in May Security patch, but the phone isn't yet locked, the guy selling it has access to the phone, he just can't remove the Google account. Is there no way to enable OEM unlocking, open the bootloader, flash twrp and a different ROM? Does any of these steps require the Google account password? The device doesn't seem to have any pattern pin or password, just swipe up to unlock.
Your phone is in FRP state. You can use the phone with the above patch, just you can't get the Google service on it.
imGomez said:
Hey, I have a OnePlus 3 so I have messed around a lot with my phone, today I saw a Google Pixel at sale for a pretty low price but the guy selling it says that the phone has a Google account on it from the previous owner but it doesn't have a security pattern pin or password to get into the phone, <snip>
Click to expand...
Click to collapse
That's why it's such a low price. It's a bogus deal and you should just move on. Could be a lost or stolen device in which case one day it will be blacklisted and you are out of luck. Pay the extra money and buy a legit device.
bobby janow said:
That's why it's such a low price. It's a bogus deal and you should just move on. Could be a lost or stolen device in which case one day it will be blacklisted and you are out of luck. Pay the extra money and buy a legit device.
Click to expand...
Click to collapse
Yeah I figured, I didn't pull the trigger on it. I'll stick with my loyal oneplus 3. Thanks for the heads up tho
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
Anyone root the Pixel 4 XL from Google Play store yet?
Can the Pixel 3 XL Android 10 root method be used for Pixel 4 XL Android 10 root?
*Update2 (10/24/2019 6:00PM): Factory Images have been released!
They are available at below links. Multiple users say they have root working now.
*Note: Multiple images are listed. For my Pixel 4 XL 128GB purchased directly from Google Play store, the image is the first one "10.0.0 (QD1A.190821.007, Oct 2019)". You can verify in "Settings" >> "About Phone"... near bottom you will see "Build Number"
Factory: https://developers.google.com/android/images#coral
OTA: https://developers.google.com/android/ota#coral
According to @Samg381 the method to gain root is to follow the guide outlined here: https://topjohnwu.github.io/Magisk/install.html#boot-image-patching
Below are steps I personally followed:
Download latest Magisk Manager - https://github.com/topjohnwu/Magisk/releases/download/manager-v7.3.5/MagiskManager-v7.3.5.apk
Install Magisk manager on my Pixel 4 XL
Download latest factory image with build number that matches my phone's version from this URL: https://developers.google.com/android/images#coral
Extract the zip file contents
You will see one more zip file, extract those contents
Copy the boot.img file to your phone (you can plugin USB to your PC and put it in your "Downloads" folder
Open Magisk Manager, click "Advanced" >> "Recovery Mode"
Click the top "Install" button
When prompted click Install again, then "Select and Patch a file" >> Select the boot.img file you copied to your pixel 4 xl earlier.
it will create a new file "/storage/emulated/0/Download/magisk_patched.img"
Plugin your phone to your PC again via USB, copy this new file in same folder as your adb sdk files.
open cmd prompt type:
adb devices
*Note: unlock your phone and approve ADB access if prompted
adb reboot bootloader
fastboot devices
fastboot flash boot magisk_patched.img
If it works you should get somthing like
fastboot flash boot magisk_patched.img
target reported max download size of 268435456 bytes
sending 'boot_a' (32092 KB)...
OKAY [ 1.167s]
writing 'boot_a'...
OKAY [ 0.325s]
finished. total time: 1.494s
Reboot your phone, open Magisk manager again, and verify it shows you now have root!
I would recommend everyone who plans to root unlock their bootloader NOW as it does wipe your data just like other Pixel phones have when unlocking bootloader... I already unlocked my bootloader.
FYI, the process to unlock Pixel 4 XL bootloader is easy:
Boot Pixel 4 XL, go through initial setup guide (do not bother adding account as you will wipe data shortly)
"Settings" >> "About Phone" >> Tap "build number" about 10 times till "You are a developer"
"Settings" >> "System" >> "Advanced" >> "Developer Options"
Check "OEM unlocking"
If "OEM Unlocking" is greyed out, either "Bootloader is already unlocked", or you need to do factory reset, then go through steps 1-4 again. On my phone I had to wipe data once, then OEM Unlock
Check "USB Debugging"
Connect Pixel 4 XL to your PC with SDK tools installed
adb devices
unlock your Pixel 4 XL... you will see a prompt asking for ADB permissions, say yes
adb reboot bootloader
fastboot devices
fastboot flashing unlock
Pixel 4 XL will now ask if you want to unlock bootloader, press volume up or down once... then power button once to confirm. WARNING it will wipe all your data...
You didn't try since you have unlocked your bootloader
Mine is still locked.
Waiting for John to root his first.
It's not possible to root without the factory image. We probably won't see the factory image until the 24th.
And if we bought through carrier will there be any way to root? I've always bought from Google, but I couldn't afford it this time, so I went with the T-Mobile jump plan. Then went to unlock the bootloader on it today and says not available for carrier devices. Feel like I'm dying a bit on the inside
Maybe there will be an unlock method in the future, but I wouldn't count on it anytime soob
Unlocked my google version right out of the gate through settings. No ADB required. Waiting on a root method now.
Samg381 said:
Unlocked my google version right out of the gate through settings. No ADB required. Waiting on a root method now.
Click to expand...
Click to collapse
That only enabled your ability to unlock. You still have to do it through fastboot and wipe your data.
jruizdesign said:
And if we bought through carrier will there be any way to root? I've always bought from Google, but I couldn't afford it this time, so I went with the T-Mobile jump plan. Then went to unlock the bootloader on it today and says not available for carrier devices. Feel like I'm dying a bit on the inside
Click to expand...
Click to collapse
Verizon is a different animal, they apparently won't allow you to unlock it at all. But the other companies, I don't see why, after you pay it off, that you couldn't unlock it. Carrier locked = sim locked. You pay off a device, you get the sim unlocked. I'm actually rather surprised that there are that many people out there that would expect carriers to allow their devices to be unlocked, even if they're not paid for. You may have to wait a bit, but I see no reason why they won't let you unlock after it's paid off.
mitchdickson said:
That only enabled your ability to unlock. You still have to do it through fastboot and wipe your data.
Click to expand...
Click to collapse
Ah, gotcha. It's been a while. Thanks.
mitchdickson said:
That only enabled your ability to unlock. You still have to do it through fastboot and wipe your data.
Click to expand...
Click to collapse
Lol, must be a noob ?
---------- Post added at 02:09 AM ---------- Previous post was at 02:08 AM ----------
Looks like the process is fairly straightforward for this device as well. about as easy as any other unlocked device, I would say
ZeroKool76 said:
Lol, must be a noob
---------- Post added at 02:09 AM ---------- Previous post was at 02:08 AM ----------
Looks like the process is fairly straightforward for this device as well. about as easy as any other unlocked device, I would say
Click to expand...
Click to collapse
Be humble.
No luck unlocking my Verizon XL. With a quick glance at the VZ 3 XL posts - I'm assuming I shouldn't hold my breath?
vanydotk said:
It's not possible to root without the factory image. We probably won't see the factory image until the 24th.
Click to expand...
Click to collapse
Oh? I was not aware that was required. Thanks for the information.
Looking forward to root so I can re-enable Google's Daydream View app. Dumb Google, why would you bother to set the phone as not supported? If Google does not support Daydream View, why not "let it free" for anyone to use, especially phones like Pixel 4 XL with 90Hz display!
I did manually install the APK and while it does the prompt saying not supported, it does still render smoothly (did not try forcing 90hz, feel like it should have been smoother... it rendered without any issues, but not sure if it was 90hz smooth or not).
Anyone try any of the other VR apps like VR Ridge? I had tried that with my original Pixel XL but the framerate was never very good, I wonder if Pixel 4 XL is good enough to make the purchase worth it (of VR Ridge that is)
boneriffic said:
No luck unlocking my Verizon XL. With a quick glance at the VZ 3 XL posts - I'm assuming I shouldn't hold my breath?
Click to expand...
Click to collapse
People on the Verizon pixel 2 and P2XL are still holding their breath....so yeah!
Please heed my warning, I have spent months of my life waiting on XDA for root methods on Verizon phones.
Don't expect root anytime soon (if at all) if you have the Verizon version. I hate to be defeatist, but I don't want others to suffer as I have in the past.
Your best bet is to return, or sell your verizon phone and purchase a google version.
Picture 24th, the factory images should drop, we can then patch the boot.img and obtain root. Version users probably are getting the shaft again...
What about other carriers? T-Mobile shows OEM unlocking is not available for carrier devices
None of you guys tried pulling your boot.img and patching it in magisk?
---------- Post added at 12:09 AM ---------- Previous post was at 12:08 AM ----------
jruizdesign said:
What about other carriers? T-Mobile shows OEM unlocking is not available for carrier devices
Click to expand...
Click to collapse
On similar devices such as OnePlus you have to get it carrier unlocked and then you can unlock the bootloader afterwards, this one is likely going to be the same.
krabman said:
None of you guys tried pulling your boot.img and patching it in magisk?
---------- Post added at 12:09 AM ---------- Previous post was at 12:08 AM ----------
On similar devices such as OnePlus you have to get it carrier unlocked and then you can unlock the bootloader afterwards, this one is likely going to be the same.
Click to expand...
Click to collapse
As far as I can tell we need factory images or a working custom recovery to grab it from the phone and we have neither at the moment.
In order to allay concerns about security, the major carriers don't want their phones to have an unlocked bootloader. This is an effort to be more enterprise user friendly.