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

JayBlack_686

Member
Nov 23, 2012
49
6
0
Dallas
I'm not sure if this is the answer you are looking for, though this is what I did.

Rebooted to recovery > updated to December update via OTA
(flashing factory image was unsuccessful due to bootloader being mw8998-002.0059.00 and not mw8998-002.0066.00)
Pulled December update boot.img
Patched with Magisk 5.4.3 / V14.5

Everything is working correctly.
(other than Viper4Android)


Sent from my Pixel 2 using Tapatalk
Hi, when you say: updated to December update via OTA
Is this following the instructions on Google's page: adb sideload ota_file.zip

When you say: Pulled December update boot.img
Are you grabbing the boot.img from the December full factory image?

Also, before you do the sideload, are you using Magisk Manager to "un-root?"

Would you consider posting your command line instructions for the above steps? Thanks!
 

Diesel_Jeremiah

Senior Member
Feb 7, 2014
194
59
0
Hi, when you say: updated to December update via OTA
Is this following the instructions on Google's page: adb sideload ota_file.zip

When you say: Pulled December update boot.img
Are you grabbing the boot.img from the December full factory image?

Also, before you do the sideload, are you using Magisk Manager to "un-root?"

Would you consider posting your command line instructions for the above steps? Thanks!
I'll lay it out clearly with links and commands when I get home to my computer.

Sent from my Pixel 2 using Tapatalk
 
  • Like
Reactions: JayBlack_686

Silarn

Senior Member
Nov 5, 2014
87
14
0
Houston
I'm also unable to patch the December boot properly (With Magisk 14.5). Stuck on that google loading screen. Unless someone has a reliable method for patching the boot image, it sounds like we'll have to wait for a new Magisk version.

I made sure to delete any old boot.img and patched-boot.img files BEFORE pushing to my phone and patching with Magisk.

I can only assume it didn't patch the correct boot image or perhaps didn't overwrite the old patched image.

Redoing this clean worked for me.
 
Last edited:

xluryan

Senior Member
Nov 21, 2008
73
7
0
I'm also stuck at the Google logo boot screen. Tried several reboots now; no dice.

I followed the instructions for Magisk OTA update to retain boot. Those are clearly not working for this 8.1.0 OTA.

What can I do now to fix my phone? I've tried fastboot flash boot back to the factory boot.img, but that didn't fix it.

Update #1: I've also tried flashing the full factory image, but things are starting to look bad:
Code:
C:\Users\Ryan\Desktop\walleye-opm1.171019.011>fastboot update image-walleye-opm1.171019.011.zip
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
--------------------------------------------
Bootloader Version...: mw8998-002.0066.00
Baseband Version.....: g8998-00164-1710262031
Serial Number........: REDACTED
--------------------------------------------
checking product...
OKAY [  0.002s]
checking version-bootloader...
OKAY [  0.004s]
checking version-baseband...
OKAY [  0.001s]
sending 'boot' (32768 KB)...
OKAY [  0.927s]
writing 'boot'...
OKAY [  0.001s]
sending sparse 'system' (524284 KB)...
OKAY [ 15.506s]
writing 'system'...
OKAY [  0.002s]
sending sparse 'system' (524284 KB)...
FAILED (remote: No such partition.)
finished. total time: 16.798s
Update #2: Now I'm getting this error when trying to enter download mode:


Update #3: After more research, I'm starting to think this is due to me using outdated platform-tools (adb and fastboot). I've tried updating them and reflashing everything, but now I'm getting a screen similar to the screen above, but it says "ERROR: LoadImageAndAuth Failed: Load Error".

I've tried switching active slots between a and b, but neither is booting. Any ideas?
 
Last edited:

Diesel_Jeremiah

Senior Member
Feb 7, 2014
194
59
0
Hi, when you say: updated to December update via OTA
Is this following the instructions on Google's page: adb sideload ota_file.zip

When you say: Pulled December update boot.img
Are you grabbing the boot.img from the December full factory image?

Also, before you do the sideload, are you using Magisk Manager to "un-root?"

Would you consider posting your command line instructions for the above steps? Thanks!
After typing all this up, I realized it's very long. I apologize if it's too long, I just don't want someone to take my info and brick their phone.

This is exactly how I got the December update on my phones.
I did not "unroot" before I performed this. I did this twice on both of my Pixel 2 phones successfully.
I'm on Magisk 5.4.3 and V14.5 (under settings you can select Update Channel: Beta)
I do not have TWRP since it's still Beta
I'm using a Windows 10 computer

1) Ensure you have the most up to date SDK Platform Tools and current drivers
2) Optional Insert the SDK Platform Tools zip contents into a folder like: "C:\Android\platform-tools"
3) Optional Right click on your desktop, select new shortcut, paste "C:\Windows\System32\cmd.exe" into the path bar, name it "cmd" (This creates a shortcut to a cmd prompt on your desktop)
4) Create a folder on your desktop titled "Pixel 2" (or something similar)
5) Download 8.1.0 (OPM1.171019.011, Dec 2017) from here: Full OTA Images for Nexus and Pixel Devices. Move from downloads to created file folder "Pixel 2. ZIP will be titled "Pixel 2.walleye-ota-opm1.171019.011-xxxxxxxx"
6) Download 8.1.0 (OPM1.171019.011, Dec 2017) from here: Factory Images for Nexus and Pixel Devices. Move from downloads to created file folder "Pixel 2. ZIP will be titled "walleye-opm1.171019.011-factory-xxxxxxxx"
7) Extract the Factory image into your Pixel 2 folder
8) Drill down into the folders to find a zip named image-walleye-opm1.171019.011
9) Double click the zip to open the contents and find boot (you might have to extract this zip as well)
10) Copy this image to your Pixel 2 folder for future use and place on your phone into the Download folder
11) With your phone plugged into an USB-A to USB-C cable (I have read USB-C to USB-C don't like to work, also USB 2.0 not USB 3.0 on your computer), fire up your cmd short cut
12) Once loaded comand: adb devices > You should see your device serial number
13) Command : adb reboot recovery
14) Once the recovery loads you will see an "Android logo with red exclamation mark"
15) Hold power and press volume up once, you will see a menu. With your volume down button go to Apply update from ADB, press the power button
16) In your Pixel 2 folder, go to the OTA zip "walleye-ota-opm1.171019.011". On the top menu you should see "copy path" or alternatively you can right click > properties > Location. Copy that string (IE "C:\Users\you\desktop\...")
17) command: adb sideload and *Ctrl +v* to paste or you must type out the "adb sideload C:\Users\you\desktop\..."
18) The phone and computer will do their thing, your command window will give you a progress percentage 0-100% twice
19) Once complete, on the phone the Reboot system now should already be highlighted, press the power button to select

You should then be on 8.1 with the December updates after the phone restarts.

20) Once phone is booted, go into Magisk and select install, Patch Boot Image File, this will take you to the phone's download folder and select the boot image
21) Let Magisk do it's thing, once it's done you will get a notification that the patched_boot.img is stored in your phone's /sdcard/MagiskManager/ folder
22) Copy patched_boot.img off your phone to your Pixel 2 folder on your computer.
23) From your cmd shortcut, comand: adb devices > You should see your device serial number
24) Command: adb reboot bootloader > phone will reboot into bootloader
25) In your Pixel 2 folder, go to the patched_boot.img. On the top menu you should see "copy path" or alternatively you can right click > properties > Location. Copy that string (IE "C:\Users\you\desktop\...")
26) Command: fastboot flash boot and *Ctrl +v* to paste or you must type out the "fastboot flash boot C:\Users\you\desktop\Pixel 2\patched_boot.img"
27) It will not take very long, and then command: fastboot reboot
28) On the reboot, Magisk will give you a message "DTBO has been modified and needs to reboot." > Reboot
29) On the reboot you will get a message "There's an internal problem with your device. Contact your manufacturer for details". Look here for info: [Tut]Fix DTBO message "There's an internal problem with your device. The message doesn't harm anything.

You will now have Root via Magisk and pass Safetynet
 

Attachments

Last edited:

JayBlack_686

Member
Nov 23, 2012
49
6
0
Dallas
After typing all this up, I realized it's very long. I apologize if it's too long, I just don't want someone to take my info and brick their phone.

.......

20) Once phone is booted, go into Magisk and select install, Patch Boot Image File, this will take you to the phone's download folder and select the boot image
21) Let Magisk do it's thing, once it's done you will get a notification that the DTBO has been modified and needs to reboot.
22) On the reboot you will get a message "There's an internal problem with your device. Contact your manufacturer for details". Look here for info: [Tut]Fix DTBO message "There's an internal problem with your device. The message doesn't harm anything.

You should then be on 8.1 with the December updates.
Thanks so much for doing this. Maybe this is obvious, but after patching the boot.img, do we need to copy it to the PC, then flash it via adb? Thanks again, this is very helpful.
 

depii

Senior Member
Dec 10, 2010
111
80
0
Was mw8998-002.0059.00 before, now mw8998-002.0066.00 via the ota.
hm, i'am exactly on the same versions, but my phone didn't boot with patched_boot.img, like described here https://forum.xda-developers.com/showpost.php?p=74770017&postcount=121

EDIT: i pressed long power while stucked at the G logo and tried booting again. Now it works. wtf.

I tried flash patched_boot and reboot two times before. But after stucking G logo i bootet into bootloader and flashing the original boot.img. I never tried reboot again after stucking G logo.
 
Last edited:

tango650

Member
Nov 9, 2017
6
3
0
Okay just managed to successfully root 8.1 on my Pixel 2. These are the steps if anybody's interested:
[bootloader must be unlocked]
Youll need to download (search on XDA and online, all files are easy to find):
  • latest snoke kernel R1 zip: Snoke.R1
  • latest twrp: twrp-pixel2-installer-walleye-3.2.0-0
  • latest magisk: Magisk-v14.5(1456)
  • youll also need latest adb and fastboot.
Then follow these steps , :
1. Reboot phone to bootloader. : .\adb.exe reboot bootloader
2 fastboot boot twrp-3.1.1-alpha1-walleye.img: .\fastboot.exe boot ..\twrp-3.2.0-0-walleye.img
3. Enter twrp and start adb sideload
4 Sideload snoke kernel: .\adb.exe sideload ..\Snoke.R1.zip
5. you may need to restart into bootloaded and fastboot twrp again then go to adb sideload again (not sure if this step is necessary, i had to do it as my adb sideload got stuck after loading Snoke, but you may be able to go ahead and install magisk straight after Snoke):
6 Install magisk: .\adb.exe sideload '..\Magisk-v14.5(1456).zip'
7. Youre in business.

Most credit to this post: https://forum.xda-developers.com/pixel-2/how-to/how-root-magisk-pixel-2-t3698713
 
  • Like
Reactions: GTOJim and PhilipTD

ZappiestOyster

Senior Member
Dec 23, 2010
61
5
0
Guys, I'm rooted and unlocked on 8.0. Just received the notification from the mothership to upgrade to 8.1. I am a little new to the process, but can I update now without losing any data and also assume root/unlock will continue to work after the update?

Thanks for any guidance!
 

clcdev

Senior Member
Feb 5, 2016
69
17
18
Pittsburgh

Duhman72

Member
Mar 11, 2011
22
5
23

clcdev

Senior Member
Feb 5, 2016
69
17
18
Pittsburgh
Has anyone gotten this Magisk OTA installation method to work successfully? When I tried it, it caused a boot loop, so I abandoned using it. It could have been I missed a step or something.. but was just wondering if anyone has successfully updated using this method.

Thanks!
I'll give it a shot if google ever get's around to fixing their check for updates button. I get too impatient waiting for the OTA to be pushed and just end up sideloading it.
 

nonato

Member
May 7, 2009
22
22
0
**need unlocked bootloader**

patching boot.img (via magisk) didnt work for me using latest 8.1.0 (OPM1.171019.011, Dec 2017) what did work was:

download https://dl.twrp.me/walleye/twrp-3.2.0-0-walleye.img.html
download Latest Magisk Beta: v14.5 (code: 1456) https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589

put both in your adb folder.

-adb reboot bootloader
-fastboot boot twrp-3.2.0-0-walleye.img
-enable adb sideload in twrp
-adb sideload Magisk-v14.5(1456).zip

only issue im getting is that magisk is installed passes safetynet etc but no modules will install says magisk is not activated. root works though.
edit: seems there's been a change to magisk in the beta. modules will need to be updated otherwise they'll fail to install.
 
Last edited:
  • Like
Reactions: GTOJim