• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

Maybe a stupid question about Verizon Pixel 2's and rooting

Search This thread

enzyne

Senior Member
May 4, 2007
203
48
Montana
It's strange because on first boot it was in the off posisiont and greyed out but said bootloader already unlocked but now after a reboot and magisk install it says this.

https://ibb.co/dvyNRb
 
Last edited:

mamarcac

Senior Member
Sep 29, 2016
109
29
Would it be possible to modify the .bin in an OTA sideload for a root? Am I missing a key point in how this works? Or is it just, no one's done it yet?

Edit: I guess it just took a passion and a situation. See thread for unlock.

Edit Part 2: Electric Boogaloo: Just a quick recap of what's happened here. From the bootloader screen on my Pixel 2 (Walleye) I ran the
Code:
 Fastboot flashing lock-critical
command, which then gave me a menu asking if I really want to lock it, or unlock it, I clicked unlock, and here we are. So far, only @zinchalk has confirmed this working. I would love for more people to try this out on their Verizon Pixel 2's and come back with the results. This was either the weirdest fluke of all time, or the best mistake Verizon has ever made. Either way, I hope it works for you :)

Any chance you can post the screenshot of the Developer Options "OEM Unlocking" now that you're unlocked and rooted? I'm going to test this on my Walleye P2 tonight as well. Thank you so much for sharing man, very exciting stuff!
 
  • Like
Reactions: EstiR86

abs0lute

Member
Jun 20, 2007
8
2
Would it be possible to modify the .bin in an OTA sideload for a root? Am I missing a key point in how this works? Or is it just, no one's done it yet?

Edit: I guess it just took a passion and a situation. See thread for unlock.

Can confirm that it is working. Still need to either root or install a kernel that bypasses SafetyNet, but just bought a Verizon P2 Walleye about an hour and a half ago, ran the adb command and was prompted with this:
https://photos.app.goo.gl/fGiwzVZ5HvgTaAp42

Phone was wiped, set up phone as new, checked developer settings and OEM unlocking was disabled/greyed out.

However, attempting to set up Android Pay shows a SafetyNet failure message. Fairly positive that Verizon made a pretty neat mistake here.
 
  • Like
Reactions: EstiR86

TonikJDK

Senior Member
Dec 9, 2012
2,692
1,368
Google Pixel 6 Pro
Can confirm that it is working. Still need to either root or install a kernel that bypasses SafetyNet, but just bought a Verizon P2 Walleye about an hour and a half ago, ran the adb command and was prompted with this:
https://photos.app.goo.gl/fGiwzVZ5HvgTaAp42

Phone was wiped, set up phone as new, checked developer settings and OEM unlocking was disabled/greyed out.

However, attempting to set up Android Pay shows a SafetyNet failure message. Fairly positive that Verizon made a pretty neat mistake here.

Google made the mistake. Seen them make many on the OG too. Congrats! If you is Magisk for root it will get all set on safety net without a kernel.
 

Lightn1ng

Senior Member
Mar 31, 2015
1,879
715
Washington, D.C.
I'm gonna do some digging into whether this is permanent.

I have a suspicion that the device locks itself if you set it up with a Verizon SIM card - am I wrong about that?
 

bobby janow

Senior Member
Jun 15, 2010
5,876
1,980
I'm gonna do some digging into whether this is permanent.

I have a suspicion that the device locks itself if you set it up with a Verizon SIM card - am I wrong about that?
I'd like to see a screen shot of the toggle after you do this unlock method. Also I'd like to see if it's now possible to relock it and then perhaps unlock it again via the same method or by the simple bootloader oem unlock command.
 

Lightn1ng

Senior Member
Mar 31, 2015
1,879
715
Washington, D.C.
I'd like to see a screen shot of the toggle after you do this unlock method. Also I'd like to see if it's now possible to relock it and then perhaps unlock it again via the same method or by the simple bootloader oem unlock command.

Just tried. Relocking works, and it goes back to the state it was before. Unlocking via the same method works. oem unlock does not.

You can try yourself if you want
 

SWATre

New member
Dec 29, 2017
1
0
FAILED (remote: Device already : locked!)

Based on mine and other experiences, I'm going to guess this doesn't work for 8.1 XL version.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 13
    Would it be possible to modify the .bin in an OTA sideload for a root? Am I missing a key point in how this works? Or is it just, no one's done it yet?

    Edit: I guess it just took a passion and a situation. See thread for unlock.


    Edit Part 2: Electric Boogaloo: Just a quick recap of what's happened here. From the bootloader screen on my Pixel 2 (Walleye) I ran the
    Code:
     Fastboot flashing lock_critical
    command, which then gave me a menu asking if I really want to lock it, or unlock it, I clicked unlock, and here we are. So far, only @zinchalk has confirmed this working. I would love for more people to try this out on their Verizon Pixel 2's and come back with the results. This was either the weirdest fluke of all time, or the best mistake Verizon has ever made. Either way, I hope it works for you :)

    Edit 3: Well there's the January Patch This looks like it 'fixes' the bypass.
    Correction: Nevermind, nothing is confirmed yet. And the people have decided there is no way this could be patched that quickly.

    Edit 4: I'm seeing way too many people posting about bricked phones. Please don't do this UNLESS YOU KNOW WHAT YOU ARE DOING. I cannot live knowing that someone ruined their phone with this method. Please be safe.
    @SoloTSi97 has confirmed this does work on the January 5th security patch!

    Edit 5: There it is, we have people confirming the Verizon OTA being pushed this late January is patching the fastboot unlock method. Keep this in mind down the road guys.
    4
    Holy smokes. We know it works, enough already. What a bore fest.

    Sent from my Pixel 2 using XDA-Developers Legacy app

    Oh let them have their fun, every confirm is a good thing.
    4
    Final Update

    So that worked. Currently rooted with TWRP on my Verizon Pixel 2. Spread the word, or don't.
    3
    I'll come right out and say it.... I don't care one bit about the security implications this exploit revealed. If someone has stolen my phone, then the last thing I am worried about is how easy or hard it is for them to bypass FRP. My phone is gone and it's not coming back either way.

    It feels like we're all worried about something in theory but it doesn't have any practical effect. Let's just enjoy the benefits of it as device owners who have the right to do whatever we want to a product we own... Before it's too late and gets patched.

    I think the people afraid of the implications are actually more afraid for companies than themselves. I can say with 99% certainty, because this was released and is not public information, someone is getting fired. Which may lead to stricter lock procedures. Or (for what i'm hoping) Verizon will give up on locking bootloaders. But it's really up in the air right now
    3
    What are the (if any) downsides to doing this? I don't plan to flash a new rom or anything, but I don't want to lose the opportunity to in the future. Does this open me up to security holes? Is there a way to save my data so after unlocking I still have everything?

    Edit: Also, how much time do I have to do this? Is this something that Verizon/Google can fix without me knowing? Or would I need to take an OTA update for it to be fixed?

    Edit 2: A more general question: Does the Pixel 2 do OTA updates automatically or will I be prompted to have it update? In other words, if Verizon pushes an update in the middle of the night, will my phone automatically update?

    You can use the backup feature on the pixel 2 to reload your apps and settings.

    Rooting always exposes you to some level of security risk, but so does driving a car. Hasn't stopped me from doing either.

    You can take as much time as you need to decide if you want to do this, but if you update past the December security patch, there is no guarantee you can get it to unlock.

    OTA updates will still be pushed to your device, but will not relock your bootloader.

    Correction:
    They will fail to install automatically if you have root. You will have to side load from the Google OTA repository online.