Database Info

USCC V20 (US996) Bootloader Unlock/Root Discussion

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

Updating Verizon Pixel unlocked bootloader with depixel8

I want to update everything except leave the bootloader on 7.1. Will this work?

LoliSmith said:
I want to update everything except leave the bootloader on 7.1. Will this work?
Click to expand...
Click to collapse
I don't​ believe that will work. Why do you want to do that? 7.1.1 won't relock it if that is what you are worried about....as long as you are already unlocked.

TonikJDK said:
I don't​ believe that will work..
Click to expand...
Click to collapse
I think I will try it.
TonikJDK said:
Why do you want to do that?
Click to expand...
Click to collapse
I want to be able to lock and unlock if I need to.

LoliSmith said:
I think I will try it.
I want to be able to lock and unlock if I need to.
Click to expand...
Click to collapse
Once you are unlocked it does not matter what version you are on you can lock and unlock all you want. I advise strongly against relocking. You very well might brick yourself. Has happened to a fair number of people already. Also remember unlocking or relocking will wipe your phone.

TonikJDK said:
Once you are unlocked it does not matter what version you are on you can lock and unlock all you want.
Click to expand...
Click to collapse
http://theroot.ninja/depixel8.html
"DO NOT RELOCK YOUR BOOTLOADER, unless you have restored it back to 100% stock and are sure you won't want it unlocked again."

TonikJDK said:
O I advise strongly against relocking. You very well might brick yourself. Has happened to a fair number of people already.
Click to expand...
Click to collapse
Were they still on 7.1 bootloader? Or had they upgraded to 7.1.1 bootloader?

LoliSmith said:
Were they still on 7.1 bootloader? Or had they upgraded to 7.1.1 bootloader?
Click to expand...
Click to collapse
Don't know, didn't pay that much​ attention.

TonikJDK said:
Don't know, didn't pay that much​ attention.
Click to expand...
Click to collapse
My guess is they upgraded to the 7.1.1 bootloader and that caused the issues relocking.

LoliSmith said:
My guess is they upgraded to the 7.1.1 bootloader and that caused the issues relocking.
Click to expand...
Click to collapse
It has nothing at all to do with the bootloader.
Sent from my Pixel using XDA-Developers Legacy app

bobby janow said:
It has nothing at all to do with the bootloader.
Click to expand...
Click to collapse
So what does it have to do with then?

LoliSmith said:
So what does it have to do with then?
Click to expand...
Click to collapse
No one knows for sure. Well some must know but they're not saying. Maybe imei. Depixel8 used an exploit which was closed in a November update. The bootloader versions are exactly the same for the Verizon and Google devices as are the system images.
Sent from my Pixel using XDA-Developers Legacy app

bobby janow said:
Depixel8 used an exploit which was closed in a November update. The bootloader versions are exactly the same for the Verizon and Google devices as are the system images.
Click to expand...
Click to collapse
Right but if I stay on 7.1 bootloader, then it doesn't matter.
I am on 7.1. still. I want the bootloader to stay on 7.1. I think people who experienced problems relocking had upgraded their bootloader to 7.1.1.

LoliSmith said:
Right but if I stay on 7.1 bootloader, then it doesn't matter.
I am on 7.1. still. I want the bootloader to stay on 7.1. I think people who experienced problems relocking had upgraded their bootloader to 7.1.1.
Click to expand...
Click to collapse
There has been posts about problems relocking before 7.1. Bottom line is if you have a Verizon Pixel, you don't want to do it unless you are completely stock. Regardless of the version of your bootloader. Why would you want to lock it again anyway? Under the context you are using here, it makes no sense. Keep an old bootloader so you can lock and unlock at your choosing. I can see reasons for relocking it but i can't see any reason why you'd want to unlock, then relock, then unlock, etc. Leave it unlocked and enjoy the benefits. I'm not really sure what it is you're wanting here. As has been said before, once unlocked, you'll remain unlocked. Regardless of any update with an updated bootloader. Once unlocked, the only way for you to end up with a locked bootloader is if you issue the necessary fastboot commands. Leave it unlocked. Enjoy. Just my two cents worth.

bobby janow said:
No one knows for sure. Well some must know but they're not saying. Maybe imei. Depixel8 used an exploit which was closed in a November update. The bootloader versions are exactly the same for the Verizon and Google devices as are the system images.
Click to expand...
Click to collapse
There's actually a total of 5 bootloaders

robocuff said:
Bottom line is if you have a Verizon Pixel, you don't want to do it unless you are completely stock.
Click to expand...
Click to collapse
I would never try to relock without being completely stock.
robocuff said:
Why would you want to lock it again anyway?
Click to expand...
Click to collapse
More secure.

LoliSmith said:
I would never try to relock without being completely stock.
More secure.
Click to expand...
Click to collapse
I can't argue with that but how much security are losing by staying on that version and not installing the monthly updates? They are mostly security related updates. Seems to me you'd be trading one security issue for a whole bunch more. That said, if you stay on 7.1 you should be able to lock it and unlock it again in the future if that's what you want to do.

robocuff said:
I can't argue with that but how much security are losing by staying on that version and not installing the monthly updates?
Click to expand...
Click to collapse
As long as they are released as flashable files, I can flash them. But if not then yeah, I am missing out on those.
robocuff said:
That said, if you stay on 7.1 you should be able to lock it and unlock it again in the future if that's what you want to do.
Click to expand...
Click to collapse
Yes, that is what I want to do. The only thing I am not sure on is if I flash everything else, will the phone work with an older bootloader version. It always worked with my motorola and nexus phones but of course, that doesn't mean it will work with a Pixel.
With motorola I did have to keep the partition table consistent with the bootloader version and that could create a problem if the system partition of later versions was larger.
I plan on staying on Nougat with this phone so it shouldn't be a problem.

LoliSmith said:
As long as they are released as flashable files, I can flash them. But if not then yeah, I am missing out on those.
Yes, that is what I want to do. The only thing I am not sure on is if I flash everything else, will the phone work with an older bootloader version. It always worked with my motorola and nexus phones but of course, that doesn't mean it will work with a Pixel.
With motorola I did have to keep the partition table consistent with the bootloader version and that could create a problem if the system partition of later versions was larger.
I plan on staying on Nougat with this phone so it shouldn't be a problem.
Click to expand...
Click to collapse
I don't really know what to tell you about it. The bootloader may work fine but who's to say the vulnerability that depixel8 exploits is in the bootloader? It could be software related, it could be hardware related. I really have no idea. Also, I did a bit of searching about this and from what I read, it sounds as if it might not be possible to unlock it again if you've already taken the security patch that patched the exploit. I could be wrong but it sounds as if that may be the case. Look, at the last paragraph of this article . From what that says, it sounds as though it isn't possible to unlock even on an older version of Nougat once you've taken that security patch. If that's the case, it would seem the the exploit must have targeted something at a very low level. Something other than the OS or the bootloader.
Also, even if you can do what you want to do, I don't know if you can install the updates without installing the one that patches the exploit. I really have no idea. I've seen it said that they are cumulative and in order to install the newest updates, you have to install all the previous ones first. I really have no idea if that is correct or not but if it were me, I'd tread lightly on this one unless you're willing to risk the possibility of not being able to unlock it again. These are just some of my thoughts about it all. I don't have the answers to my thoughts but if it were me, I wouldn't lock it again without knowing for sure it can be unlocked again.

robocuff said:
I could be wrong but it sounds as if that may be the case. Look, at the last paragraph of this article . From what that says, it sounds as though it isn't possible to unlock even on an older version of Nougat once you've taken that security patch.
Click to expand...
Click to collapse
Right because it updated both the bootloader and the kernel. I would only be updating the kernel, not the bootloader. And I am assuming that as long as the bootloader is on 7.1, I can downgrade the kernel, system, etc. as long as the files are signed.
robocuff said:
If that's the case, it would seem the the exploit must have targeted something at a very low level. Something other than the OS or the bootloader.
Click to expand...
Click to collapse
I am not going to ever take any OTAs. Presumably aboot.img is the bootloader but I am not sure what bootlocker.img and keymaster.img are so I would need to research that further. Do you know what they are?
robocuff said:
I've seen it said that they are cumulative and in order to install the newest updates, you have to install all the previous ones first.
Click to expand...
Click to collapse
Are you talking about flashing or taking OTAs?
robocuff said:
I really have no idea if that is correct or not but if it were me, I'd tread lightly on this one unless you're willing to risk the possibility of not being able to unlock it again. These are just some of my thoughts about it all. I don't have the answers to my thoughts but if it were me, I wouldn't lock it again without knowing for sure it can be unlocked again.
Click to expand...
Click to collapse
Thanks. I am OK with not being able to unlock again.

LoliSmith said:
keymaster.img
Click to expand...
Click to collapse
Yeah, definitely won't be updating that:
https://source.android.com/security/keystore/

Response from Nokia on unlocking bootloader

I can't say I am surprised, but I thought I'd ask and see what they say. Here's an email and the response I received.
Me:
Hello, Before I order the 8, I'd like to know if you provide the means / process to unlock the bootloader for your devices. I typically run stock Android, which I know you provide, but occasionally like to run custom ROM's as well. An unlocked bootloader will allow flexibility, and providing the ability to unlock will gain you a following in the modding community. Thanks!
Nokia:
Regarding your inquiry about the bootloader unlock for the Nokia 8, please be informed that we may not provide this information.
Additionally, please note that unlocking the bootloader for the device will void the warranty and we therefore do not recommend it.
If you have any further questions, please do not hesitate to contact us again.
Best regards,
Nokia Mobile Care team
Now, I am really having a hard time coming up with a NEED for the bootloader to be unlocked... unless I need it to flash another region to add bands that aren't available on my device... maybe?

lorditler said:
If you want to root it, duuuh. Like installing SuperSU, dude. :silly:
Click to expand...
Click to collapse
Well, the question specifically was not about root, but about unlocking the bootloader, which entirely different... dude.:silly:

This is so God damn bad news!
Really thinking about selling this phone right now...

Alttu said:
This is so God damn bad news!
Really thinking about selling this phone right now...
Click to expand...
Click to collapse
I wouldn't jump ship yet. Fact is, it still may be very easy to unlock the bootloader and gain root, as the device is runing bone stock Android. Frankly, there is not much left that I need root for.
For me, however, the 8 presents a specific problem. I live in the US, and the bands that are listed as supported are missing some LTE bands I really need (12 specifically). I am aware that there are ways to enable available bands for some devices, but I think you NEED an unlocked bl to get that done.
Thats likely a deal breaker for me. :crying:

charlatan01 said:
I wouldn't jump ship yet. Fact is, it still may be very easy to unlock the bootloader and gain root, as the device is runing bone stock Android. Frankly, there is not much left that I need root for.
Click to expand...
Click to collapse
Well we will see about that...
Thanks for reassuring!

Just taught to have a little chat with support too...

Maybe there's still a way to flash TWRP without unlocking the bootloader. They did it for example on the Nokia 6 by booting into what they call 9008 port mode (EDL in other words) and flashed the recovery with a tool named MiFlash in that mode. (Link to Nokia 6 thread)

Alttu said:
Just taught to have a little chat with support too...
Click to expand...
Click to collapse
This is simply ridiculous and not treating the customers serious enough.

Hi all,
i found an option in Developer Options -> OEM unlocking ->allow the bootloader to be unlocked.
To get developer options tap 8 times "Build number" in About Phone section of settings.
I hope this is the right way for unlocking bootloader.
Daniel

Orca74 said:
Hi all,
i found an option in Developer Options -> OEM unlocking ->allow the bootloader to be unlocked.
To get developer options tap 8 times "Build number" in About Phone section of settings.
I hope this is the right way for unlocking bootloader.
Daniel
Click to expand...
Click to collapse
We already know that. Enabling that setting doesn't do anything.

anyone tried unlocking bootloader via fastboot?
before i get flamed for being a noob, yes i know you need to enter a code or something to unlock bootloaders unlike pixel/google phones.
no harm trying right?

Hmm. I know some devices in my past have not required an unlocked bootloader to allow root, but I'm not savvy enougb to figure out if its possible on this device.

And rooting will NOT void warranty in EU.
http://matija.suklje.name/rooting-and-flashing-your-device-does-not-void-the-warranty-in-eu
Hasn't a case like this have already been handled by a court. Consumer was right.

frostmore said:
anyone tried unlocking bootloader via fastboot?
before i get flamed for being a noob, yes i know you need to enter a code or something to unlock bootloaders unlike pixel/google phones.
no harm trying right?
Click to expand...
Click to collapse
I could only get the 8 into Download mode and could not install it as a FastBoot device.

Sure sucks that they seemingly won't allow this. I was interested in a Nokia phone as well. HMD have even said they want their phones to be like the new Nexus. They really need to support the custom ROM community if so!

Ok so, I can get the device to boot into bootloader(download mode) and somekind of a recovery, trough ADB in windows.
But no luck on "fastboot oem unlock" command. --FAILED <remote : flashing unlock is not allowed

Orca74 said:
Hi all,
i found an option in Developer Options -> OEM unlocking ->allow the bootloader to be unlocked.
To get developer options tap 8 times "Build number" in About Phone section of settings.
I hope this is the right way for unlocking bootloader.
Daniel
Click to expand...
Click to collapse
Hi Daniel,
Does unlocking bootloader violates the guarantee/warranty?
I just purchased Nokia 8 5 days ago.
Thanks.

TorpodeBaas said:
Hi Daniel,
Does unlocking bootloader violates the guarantee/warranty?
I just purchased Nokia 8 5 days ago.
Thanks.
Click to expand...
Click to collapse
If you are in the EU, no unlocking the bootloader does not void your warranty. It's protect under EU laws. Someone mentioned that in earlier posts. Unless you are in asia or some other parts of the world where they screw consumers in favor of big businesses.
and if you had read through, there is currently no way to unlock the bootloader on the nokia 8. If there was a way and devs are willing to move over to this beautiful device, i'd get it in a heartbeat.

frostmore said:
If you are in the EU, no unlocking the bootloader does not void your warranty. It's protect under EU laws. Someone mentioned that in earlier posts. Unless you are in asia or some other parts of the world where they screw consumers in favor of big businesses.
and if you had read through, there is currently no way to unlock the bootloader on the nokia 8. If there was a way and devs are willing to move over to this beautiful device, i'd get it in a heartbeat.
Click to expand...
Click to collapse
hehe, i like the way you articulated the answer.
Thank you.
I miss FM radio now, i guess have to do something about it

Ok it seems With luck Nokia opens the bootloader after the **** storm...
Gesendet von meinem HTC 10 mit Tapatalk

Can I unlock a previously unlocked bootloader?

I had my bootloader unlocked since the pixel came out, and just recently re-locked it through SkipSoft Android ToolKit. I needed to use the Android Pay and didn't have the time to figure out and install Magdisk. I had foolishly assumed that since it was already unlocked that I could easily unlock it again. I was wrong lol. I tried several times in the toolkit with no success.
Is there any hope for this pixel?

wheelbarrel said:
I had my bootloader unlocked since the pixel came out, and just recently re-locked it through SkipSoft Android ToolKit. I needed to use the Android Pay and didn't have the time to figure out and install Magdisk. I had foolishly assumed that since it was already unlocked that I could easily unlock it again. I was wrong lol. I tried several times in the toolkit with no success.
Is there any hope for this pixel?
Click to expand...
Click to collapse
If it's a Verizon one probably not. If it's a Google store pixel, Yes just unlock it again. It will wipe again.

Why did you relock it in the first place

KittyRgnarok said:
Why did you relock it in the first place
Click to expand...
Click to collapse
I needed to use Android Pay, the Tap 'n Go feature. I didnt have time to figure out how to hide root so the app would work. I just thought since it was already unlocked it could easily unlock. I guess I am staying stock lol
And it was purchased through verizon but is now on T-Mobile.

wheelbarrel said:
I needed to use Android Pay, the Tap 'n Go feature. I didnt have time to figure out how to hide root so the app would work. I just thought since it was already unlocked it could easily unlock. I guess I am staying stock lol
And it was purchased through verizon but is now on T-Mobile.
Click to expand...
Click to collapse
Magisk very easily fixes Android pay not working with an unlocked phone. There are like 3 different threads specifically saying hey there is no real reason to ever relock this phone and if you do to be extremely careful
---------- Post added at 06:46 PM ---------- Previous post was at 06:45 PM ----------
Also you purchased it through Verizon so no it isn't easy to reunlock. You will be stuck with the locked bootloader for the foreseeable future. For future reference do not ever buy a phone you intend to mod from Verizon or AT&T

KittyRgnarok said:
Magisk very easily fixes Android pay not working with an unlocked phone. There are like 3 different threads specifically saying hey there is no real reason to ever relock this phone and if you do to be extremely careful
---------- Post added at 06:46 PM ---------- Previous post was at 06:45 PM ----------
Also you purchased it through Verizon so no it isn't easy to reunlock. You will be stuck with the locked bootloader for the foreseeable future. For future reference do not ever buy a phone you intend to mod from Verizon or AT&T
Click to expand...
Click to collapse
Yeah, it does appear that you'll be stuck with a locked bootloader on the Verizon branded phone. I believe that BigRed is using the IMEI number so regardless of SIM, the 'mothership' sends out the command to lock it down. However, I would be interested to see what would happen if you send the OEM Unlock command.
And as far as saying that "do not ever buy a phone you intend to mode frrom VZW or AT&T" not sure I agree entirely...but certainly have to know the risks and limitations, especially if exploits are found. That's one of the reasons I don't use automated kits. I need to know exactly what's happening and commands being sent to my VZW phones. I've been on Verizon and AT&T for quite some time. However, I always find a phone that has an exploit for root. Good luck!

b00ster23 said:
Yeah, it does appear that you'll be stuck with a locked bootloader on the Verizon branded phone. I believe that BigRed is using the IMEI number so regardless of SIM, the 'mothership' sends out the command to lock it down. However, I would be interested to see what would happen if you send the OEM Unlock command.
And as far as saying that "do not ever buy a phone you intend to mode frrom VZW or AT&T" not sure I agree entirely...but certainly have to know the risks and limitations, especially if exploits are found. That's one of the reasons I don't use automated kits. I need to know exactly what's happening and commands being sent to my VZW phones. I've been on Verizon and AT&T for quite some time. However, I always find a phone that has an exploit for root. Good luck!
Click to expand...
Click to collapse
Using them as a carrier is (almost) fine, but it shouldn't be necessary to use an exploit to unlock your phone and they do shady custom bootloader **** on almost all of their phones

KittyRgnarok said:
Using them as a carrier is (almost) fine, but it shouldn't be necessary to use an exploit to unlock your phone and they do shady custom bootloader **** on almost all of their phones
Click to expand...
Click to collapse
Yup... agreed. Shouldn't be necessary, but unfortunately the law is in their side. They lock bootloaders to offset reduced hardware pricing, in an effort to cut support cost and limiting possible bricked phones. Trust me don't like it, but if I can get a significantly reduced cost on the phone, and have full admin rights....uhhhh thank u...

b00ster23 said:
Yup... agreed. Shouldn't be necessary, but unfortunately the law is in their side. They lock bootloaders to offset reduced hardware pricing, in an effort to cut support cost and limiting possible bricked phones. Trust me don't like it, but if I can get a significantly reduced cost on the phone, and have full admin rights....uhhhh thank u...
Click to expand...
Click to collapse
Tru Tru

wheelbarrel said:
I needed to use Android Pay, the Tap 'n Go feature. I didnt have time to figure out how to hide root so the app would work. I just thought since it was already unlocked it could easily unlock. I guess I am staying stock lol
And it was purchased through verizon but is now on T-Mobile.
Click to expand...
Click to collapse
My pixel passed safety net without any issues with an unlocked bootloader running a custom kernel without root. I don't think safety net checks the bootloader (could be wrong)

Poebat said:
My pixel passed safety net without any issues with an unlocked bootloader running a custom kernel without root. I don't think safety net checks the bootloader (could be wrong)
Click to expand...
Click to collapse
Yes Safety Net does check the BL. The reason yours passes is because of the custom kernel. I seen a post for an 'almost' stock kernel for the PIXEL2 that passes SN, without root if that's all u need. The kernel has a patch for only the Safety Net. But again that's the PIXEL2

b00ster23 said:
Yes Safety Net does check the BL. The reason yours passes is because of the custom kernel. I seen a post for an 'almost' stock kernel for the PIXEL2 that passes SN, without root if that's all u need. The kernel has a patch for only the Safety Net. But again that's the PIXEL2
Click to expand...
Click to collapse
Ah. I figured that might be the case.

b00ster23 said:
Yes Safety Net does check the BL. The reason yours passes is because of the custom kernel. I seen a post for an 'almost' stock kernel for the PIXEL2 that passes SN, without root if that's all u need. The kernel has a patch for only the Safety Net. But again that's the PIXEL2
Click to expand...
Click to collapse
I mean almost every custom kernel for pixel og has proper safety net support

I appreciate all your input everyone! Unfortunately I am going to have to wait until it's time to buy a Pixel 2 lol, which is getting close
This is proof you should read EVERYTHING first lol

Android 9: Pixel 2 Downgrading questions

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.