[GUIDE] Unlock/Flash/Root for the Pixel 2 (walleye)

jd1639

Recognized Contributor
Sep 21, 2012
16,836
5,398
0
Minnesota
is it at all possible to root the pixel 2 without a PC anybody ???

---------- Post added at 06:36 PM ---------- Previous post was at 06:31 PM ----------


that is absolutely the best advice on this thread as understanding what something does when pressing is the key to fixing any issues in future if they ever arise :)
Not the first time. It's possible to take ota's and then re-root without a PC but you need to be rooted and have magisk installed to do that.
 

junkjunker

New member
Apr 18, 2015
1
0
0
Can I RE-lock the bootloader after this?

I have successfully gotten root on a Google Pixel 2 walleye with these instructions. After unlocking bootloader, flashing TWRP and Magisk, and getting root, can I RE-lock the bootloader?

Right now on every boot I get a large orange warning that the bootloader is unlocked and insecure. I have read that this can be a security risk if I lose my phone and someone savvy enough picks it up. I would like to remove this warning.

Can I do that by relocking the bootloader? Or will that cause problems? Is there an alternative to remove the warning display?

THANKS
 

rishabh56

Senior Member
Apr 21, 2013
261
78
0
Hi,
I flashed twrp on my pixel 2 running android 11 dp3 however when i try to flash Magisk it fails.I do get failure to mount /system as well as /vendor
 
Last edited:

CMPI5O

Member
May 3, 2020
7
0
0
Hello! I am new to rooting, as this my first time doing it. under the Windows section near the top, there are steps that I am stuck on. those steps are as follows:
"Go to the folder containing the adb and fastboot files and type "cmd" in the path bar at the top.
A command prompt should open with the current folder showing on the prompt."

By path bar, do you mean the bar that says what folders you went through to get to your current folder? If so, i typed, cmd, and even tried "cmd", i pressed enter, and got an error saying, " Windows can't find 'C:\platform-tools cmd'. Check the spelling and try again."

Am i doing something wrong? Or do i just not have the right computer running Windows 10?
 

Pete02

Senior Member
Dec 6, 2011
742
231
63
Hello! I am new to rooting, as this my first time doing it. under the Windows section near the top, there are steps that I am stuck on. those steps are as follows:
"Go to the folder containing the adb and fastboot files and type "cmd" in the path bar at the top.
A command prompt should open with the current folder showing on the prompt."

By path bar, do you mean the bar that says what folders you went through to get to your current folder? If so, i typed, cmd, and even tried "cmd", i pressed enter, and got an error saying, " Windows can't find 'C:\platform-tools cmd'. Check the spelling and try again."

Am i doing something wrong? Or do i just not have the right computer running Windows 10?
What I usually do is while your in the platform-tools folder hold down the shift key and right click the mouse. That should open a window that has the option to open a cmd prompt however in Windows 10 I believe its called Power Shell.
 

CMPI5O

Member
May 3, 2020
7
0
0
What I usually do is while your in the platform-tools folder hold down the shift key and right click the mouse. That should open a window that has the option to open a cmd prompt however in Windows 10 I believe its called Power Shell.

Thanks. I found out I just had to delete the path in the path bar and type cmd, then hit enter.

But now I'm stuck on the part where I type "fastboot flashing unlock" into the command prompt. I get a whole bunch of text. I'll post a pic later, I'm not home rn
 

CMPI5O

Member
May 3, 2020
7
0
0
What I usually do is while your in the platform-tools folder hold down the shift key and right click the mouse. That should open a window that has the option to open a cmd prompt however in Windows 10 I believe its called Power Shell.

For some reason it won't let me upload an image.

Basically after I hit enter after typing in "fastboot flashing unlock", it says commands, and lists the following:

update <filename>
flashall

flash <partition> [<filename>]
erase <partition>
format[:[<fs type>][:[<size>]] <partition>

getvar <variable>
boot <kernal> [ <ramdisk> [ <second> ] ]
flash:raw boot <kernal> [ <ramdisk> [ <seconds> ] ]

devices
continue
reboot
reboot-bootloader
help






It also says "options" underneath the commands and lists the following:

-w

-u

-s <specify device>

-l
-p <product>
-c <cmdline>
-i <vendor id>
-b <base_addr>

-n <page size>

-S <size>[K|M|G]








If you want the descriptions as well let me know. Idk what to do at this point.
 

dave31g

Senior Member
Aug 27, 2017
51
7
0
Chicago
Hello. I've been out of the flashing game for a couple years now. Excellent guide but I have one question. When doing a clean flash using a factory image, do i have to unzip it to the platform-tools folder? Tried using "flash-all" and i got an error along the lines of "fastboot not found" couldn't get the exact message because command prompt closed right after.
 
Last edited:

an21281

Senior Member
May 6, 2011
866
257
0
Dix Hills
Hello. I've been out of the flashing game for a couple years now. Excellent guide but I have one question. When doing a clean flash using a factory image, do i have to unzip it to the platform-tools folder? Tried using "flash-all" and i got an error along the lines of "fastboot not found" couldn't get the exact message because command prompt closed right after.
Yes, unzip to platform tools then there's a second zip file to unzip inside.

Sent from my Pixel 2 XL using Tapatalk
 

dave31g

Senior Member
Aug 27, 2017
51
7
0
Chicago
Yes, unzip to platform tools then there's a second zip file to unzip inside.

Sent from my Pixel 2 XL using Tapatalk
Thanks for your reply. I managed to get as far as patching the boot image with magisk but now I'm stuck on the Google logo. I patched the same boot image I used to flash-all, which was the latest image. Not sure where I went wrong. Was able to revert back by using flash-all again but idk where to go from here to achieve root.

EDIT: I managed to achieve root by booting to TWRP and just flashing the Magisk zip.
 
Last edited:

patomovil

New member
Dec 29, 2017
0
0
0
cannot unlock bootloader

I bought two Pixel 2 phones on Swappa, listed as Unlocked, one white and one black. Neither will unlock using the adb and fastboot commands listed on this forum. In one, I manage to get the OEM unlock option to say it's enabled, but then at the boot screen it still says locked. The other (white) has the option greyed out. They were both on the last Android 10 security update while I tried this, and then I update the white one to Android 11, but that didn't work either.

The black one's boot screen says this (in case this gives any hints about what model it is or what might be going on):
Bootloader: mw8998-002.0083.00
Baseband: g8998-00023-2004070200
Product revision: walleye MP1
Serial Number: FA7A****2495
UFS: 128GB Hynix
DRAM: 4096MB Samsung LPDDR4
Boot-slot: b
Console: DISABLED
Secure Boot: yes (PRODUCTION)
Device State: locked

So, should I assume that Pixel 2 devices cannot have their bootloaders unlocked anymore? Have we reached the end of the road for anyone who didn't already unlock their bootloader?
 

Pixelguy2

New member
Oct 4, 2020
1
0
0
Unlock - Greyed Out Option Still?

I bought two Pixel 2 phones on Swappa, listed as Unlocked, one white and one black. Neither will unlock using the adb and fastboot commands listed on this forum. In one, I manage to get the OEM unlock option to say it's enabled, but then at the boot screen it still says locked. The other (white) has the option greyed out. They were both on the last Android 10 security update while I tried this, and then I update the white one to Android 11, but that didn't work either.

The black one's boot screen says this (in case this gives any hints about what model it is or what might be going on):
Bootloader: mw8998-002.0083.00
Baseband: g8998-00023-2004070200
Product revision: walleye MP1
Serial Number: FA7A****2495
UFS: 128GB Hynix
DRAM: 4096MB Samsung LPDDR4
Boot-slot: b
Console: DISABLED
Secure Boot: yes (PRODUCTION)
Device State: locked

So, should I assume that Pixel 2 devices cannot have their bootloaders unlocked anymore? Have we reached the end of the road for anyone who didn't already unlock their bootloader?
Same here... It's been some time since I flashed ROMS (And also a Newbie to this forum.) I too purchased a Pixel 2 from Swappa under the impression this would be an extremely easy phone to root. - Nope!
Tried numerous commands in ADB and read numerous posts on how much of a problem this is. Not sure what I can do at this point and very frustrated I cannot get the the greyed-out developer "unlock Bootloader" to appear. All my phone does is basically say "Waiting on Device". Running Android 11. Ugh.... I'm sure there has got to be an answer. And yes... I appreciate everyones help and this forum!
 

jeddyfire

New member
Nov 9, 2020
3
0
0
Can't root Pixel 2 on android 11 final build.

Hello everyone. I have a pixel 2 running the final version of Android 11...rp1a.201005.004. I have tried to root it on stock firmware by patching the boot image and flashing said patched image. On rebooting, it kicks me back to fastboot screen from the Google boot up screen. I installed TWRP and flagged Magisk 21.0. No luck there either. I can install TWRP on android 10, install Pixel Dust, reboot to recovery, flash Magisk and everything works fine. I can also use the patch method on my Pixel 2xl and my Pixel 3 that are both on Android 11. Any ideas why I can't root Android 11 on my Pixel 2? Thanks.
 

jeddyfire

New member
Nov 9, 2020
3
0
0
:cyclops:
Hello everyone. I have a pixel 2 running the final version of Android 11...rp1a.201005.004. I have tried to root it on stock firmware by patching the boot image and flashing said patched image. On rebooting, it kicks me back to fastboot screen from the Google boot up screen. I installed TWRP and flagged Magisk 21.0. No luck there either. I can install TWRP on android 10, install Pixel Dust, reboot to recovery, flash Magisk and everything works fine. I can also use the patch method on my Pixel 2xl and my Pixel 3 that are both on Android 11. Any ideas why I can't root Android 11 on my Pixel 2? Thanks.
:cyclops: NM. Found the answer on a different thread. Temp "boot" twrp.img then flash the "canary" build of magisk. then reboot system. I love XDA. Thanks everyone for sharing.