yashsingh1/xdaforums huggingface dataset:
[Google Pixel 2 Guides, News, & Discussion] penciluser:
I'm confused about part 4.

What's the patched_boot.img? The snoke kernel? Or is magisk supposed to create the file?
[Google Pixel 2 Guides, News, & Discussion] Natakranta:
Stock 8.0 karnel
[Google Pixel 2 Guides, News, & Discussion] multi_rom_user:
When you patch the kernel you are on, magisk will output the file names 'patched_blot.img'. That's the IMG I'm referring to.
[Google Pixel 2 Guides, News, & Discussion] penciluser:
Any link to that?
[Google Pixel 2 Guides, News, & Discussion] xstokerx:
thisa worked for me as well follow all the steps in op just fastboot boot twrp then adb sideload magisk 14.4 boom rooted and saftey net intact on 8.1 DP thx man
[Google Pixel 2 Guides, News, & Discussion] sweteg:
Hey there. Does the first boot take a while after Magisk? I have 8.1 Preview and did the same. I didn't use Magisk on the OG Pixel when I rooted previously so not sure how long it should take.

1. fastboot boot twrp

2. adb sideload magisk 14.4 and it was a success

3. it reboot and stuck on the G logo loading screen.

Thanks!

[edit] I held power button and volume up to manually reboot from the loading screen and it loaded correctly after that.
[Google Pixel 2 Guides, News, & Discussion] xstokerx:
those are the same steps i took and no it didnt loop at all fired right up like a normal reboot.
[Google Pixel 2 Guides, News, & Discussion] constantin_frunza:
There's someone who knows where I can find "patched_boot.img"? I can not find it anywhere.

Thank you.

'
[Google Pixel 2 Guides, News, & Discussion] phonefreedom:
Can't find the boot.img
[Google Pixel 2 Guides, News, & Discussion] davemcm2:
Hi, sorry to be a pain but I've tried the method without using twrp, and can't see to get it working. Magisk manager still reports no root and not installed and it looks like the safety net check is failing.

I used Snoke-R8-P2.img then flashed the patched image successfully but all I see is this.

hxxps://photos.app.goo.gl/x52MEXWEIuLEvTJt2

Sorry about gphotos link for screenshots. Was only way I could find.
[Google Pixel 2 Guides, News, & Discussion] davemcm2:
Managed to do it with the first twrp method, all rooted and satefynet checks passing :D
[Google Pixel 2 Guides, News, & Discussion] multi_rom_user:
Just a heads up, your link should have https rather than hxxps.
[Google Pixel 2 Guides, News, & Discussion] lightningdude:
He's new, can't post links yet.
[Google Pixel 2 Guides, News, & Discussion] multi_rom_user:
Oh I see. I never knew about that rule.

---------- Post added at 12:48 AM ---------- Previous post was at 12:45 AM ----------

I think I prefer to post the pictures as thumbnails rather than hyperlinking to them anyways.
[Google Pixel 2 Guides, News, & Discussion] phonefreedom:
Google Fi Users Warning

Hello Team,

This is just an FYI in that I rooted my Pixel 2 using Magisk and TWRP successfully but have lost my Google Fi mobile data connection. Since I'm unclear if this is a one off problem and don't have a solution yet, I thought I'd better mention it here. I have a separate thread on this started.
[Google Pixel 2 Guides, News, & Discussion] multi_rom_user:
As I've stated before, DO NOT flash Snoke kernel on top of 8.1 DP!! I've gotten word directly from the OP of the kernel that it is NOT compatible with 8.1. OP please post this as a warning on your first post.
[Google Pixel 2 Guides, News, & Discussion] eevanskiteboards:
i have been rooted for a few days without any issue on FI
[Google Pixel 2 Guides, News, & Discussion] cb474:
So after you rooted, you just did the regular OTA style update, through the system settings in the phone? No side loading or anything like that?
[Google Pixel 2 Guides, News, & Discussion] multi_rom_user:
Yes correct. And same way visa versa to opt out.
[Google Pixel 2 Guides, News, & Discussion] Natakranta:
Magisk 14.5 ready to download from TheComputerGuy96 GitHub

Has anybody tried already on Pixel 2 8.0?

I'll check when.8m back at home in the evening.
[Google Pixel 2 Guides, News, & Discussion] petrus764:
https://xdaforums.com/pixel-2-xl/development/2017-11-6-root-pixel-2-xl-t3701176

[2017.11.6][Magisk] Root Pixel 2 (XL)

Works on both Pixel phones.
[Google Pixel 2 Guides, News, & Discussion] gbennett:
Can someone clarify for me.....if I am able to root the pixel 2, i will be able to bypass any tethering restrictions placed on my phone by my carrier (Total Wireless/Verizon)....is that correct?
[Google Pixel 2 Guides, News, & Discussion] rootuser11:
works fine on mine.

after updating to November Security patched version, I used TWRP Alpha 1 to sideload Magisk 14.5. All works fine.
[Google Pixel 2 Guides, News, & Discussion] cb474:
I think so, because then you can edit the build.prop and disable the carrier check the phone does to see if you are allowed to tether. If you search around, there are a lot of threads about Verizon and tethering.
[Google Pixel 2 Guides, News, & Discussion] Natakranta:
Hm, 14.5 doesn't work for me neither on 8.0 Sept security patch nor on today's 8.0 November security patch.

Sideloading 14.5 in booted alfa twrp says it patched the boot (see picture) but after rebooting system there is no Magisk Manager nor root.

Sideloading Friday's Magisk 14.4 works for me on both Sept. And Nov. 8.0

It's late here. I need to get some rest. Will keep on checking tomorrow.
[Google Pixel 2 Guides, News, & Discussion] cb474:
It was already reported in this thread (and copied into the OP of this thread) that the Pixel 2 could be rooted this way with the regular Magisk Manger. What's different about the special version of Magisk Manager in that thread?
[Google Pixel 2 Guides, News, & Discussion] peikojose:
Hi, will this work the stock boot.img extracted from Nov. Security patch (Pixel 2).

By the way, the version I got is OPD1.170816.025 which is not anywhere in the internet... Posted versions by google are OPD1.170816.0015 , OPD1.170816.016 and OPD1.170816.018
[Google Pixel 2 Guides, News, & Discussion] JayBlack_686:
Hi, thanks everyone for the help. I had some issues with method #1 (more below). I tried method #2, but never got it working until I updated to Magisk Manager 5.4.1 (OP here points to 5.4.0). It's working now, but I encountered something that I hadn't seen before when attempting method #1 via TWRP:

as I booted into TWRP, my (Win7) PC decided that it doesn't recognize my device - it shows up as "AOSP Walleye" in Device Manager. I selected "update driver" from there, pointed it to the folder in android_sdk with the latest USB drivers, which I had just downloaded over the weekend. No success. So basically, once I'm in TWRP, I can enable ADB sideload, but the PC no longer recognizes the issue, so...you see the problem.

Any thoughts? Has anyone seen this? Thanks.
[Google Pixel 2 Guides, News, & Discussion] peikojose:
Are you running stock kernel?
[Google Pixel 2 Guides, News, & Discussion] Archangel:
Yeah 14.5 didnt work for me either on the Nov update. I side loaded the Nov update then uninstalled magisk manager and followed the first set of directions, not the second in the OP however, I stayed on the stock Kernel now all is good and on Nov update rooted and magisk 14.3 is passing all checks.
[Google Pixel 2 Guides, News, & Discussion] multi_rom_user:
I would recommend not attempting method 2 with stock kernel at all. I've personally tried it and failed many times. If you want stock kernel patched with magisk, please use method 1. I can guarantee that you can get many failed attempts if you use my method on stock rom.

---------- Post added at 04:16 AM ---------- Previous post was at 04:14 AM ----------

@giant22000 please include in your post to always use the latest magisk manager version just for future reference.
[Google Pixel 2 Guides, News, & Discussion] ajrty33:
Worked fine for me using the Magisk Manager from this thread.

https://xdaforums.com/showthread.php?t=3701176

I downloaded the Nov image and flashed it (without -w), then used the boot.img from the zip in Magisk Manager. Worked just fine.
[Google Pixel 2 Guides, News, & Discussion] JayBlack_686:
(this is re: my "PC can't see the phone when I'm in TWRP" post earlier)

No and yes:

-OP's method 1 called for snoke, so I used -R7 on first attempt. Actually, I didn't mention - when I couldn't connect to the phone any more, I gave up and rebooted...got stuck on the Google boot screen. I ended up flashing the factory image and starting over.

-I tried method 1 again, this time skipping snoke kernel flash, but had the same issue (PC doesn't recognize the phone) when I booted TWRP.

-Eventually I gave up and went to method 2 and finally got that working. I think it's working, anyway; Magisk Manager says that I pass Safety Net checks, and I was able to install Titanium Backup, so...guess I'm rooted. I still haven't inserted a SIM or anything; I'm planning to set up Project Fi.
[Google Pixel 2 Guides, News, & Discussion] multi_rom_user:
You have to enable usb debugging and unlocked bootloader. Please check and make sure you have these enabled. And make sure you use 'adb devices' command in CMD to make sure it's authorized for your PC. You will have to enable it every time you reflash any rom image unless it's a custom rom tht enable it by default.
[Google Pixel 2 Guides, News, & Discussion] rootuser11:
Magisk 14.5 + stock kernel + november ota + twrp alpha

Works fine as in the attached
[Google Pixel 2 Guides, News, & Discussion] peikojose:
Hey guys, can you share this screen ?

I am really concerned, first this is the information I got before rooting the phone.

As you can see kernel was compiled on October 26th and build ends in 025 (it is not available to download from Google Factory Images)

I downloaded 018 version from Google, extracted boot.img and used it to get root.. now the kernel says "Mon Sept 18"
[Google Pixel 2 Guides, News, & Discussion] Archangel:
Mine says the same thing for the Kernel date Sept 18th and I side loaded the .016 Nov Verizon version.
[Google Pixel 2 Guides, News, & Discussion] JayBlack_686:
I did...I started with unlocking the bootloader. Without the USB debugging enabled, I wouldn't have been able to get it to boot TWRP at all. I always run "adb devices" first, and my device showed up...until I booted into TWRP, at which point my PC basically acted like I pulled the cable, plugged it back in, and then it didn't recognize the phone.

No big deal, I'm rooted now...but I had never seen this before.

---------- Post added at 07:55 AM ---------- Previous post was at 07:53 AM ----------

Did you get the November OTA before rooting? I had understood that we have to uninstall Magisk before we can take any OTA updates. True? In the past I always went with custom ROMs, so have never had to deal with OTA updates before.
[Google Pixel 2 Guides, News, & Discussion] bryantjopplin:
So you can boot into twrp with the new update? How about 8.1 preview??? XL can not hmmm
[Google Pixel 2 Guides, News, & Discussion] fjm568:
I've been having this same issue. Trying to root, I fastboot boot twrp, tap the advanced button, then the ADB Side load button, swipe to start sideload, then type adb sideload Magisk command and it fails. It seems after twrp runs, my PC doesn't recognize my Pixel 2. It doesn't show up as an attached device. Tried different cables, different USB ports(laptop is pre-3.0 USB). Using current ADB platform tools. Boot loader is unlocked, USB debugging is on. It looks like the phone goes into charge only mode, instead of allowing file transfers. Is there an adb command to change that? I've tried to make sure that the correct settings are checked on the phone so that it isn't in charge only mode before I start the process, but once in twrp, can't do anything about it. What am I missing?

I've rooted all my phones in the past by following directions here on xda, but I'm a noob when it starts getting technical. I just want to be able to run Titanium backup so that I can backup app data reliably.

Thanks.
[Google Pixel 2 Guides, News, & Discussion] TaintedByte:
For anyone here having issues, I can confirm that following the steps in the Magisk release for the Pixel 2 XL worked perfectly for me on both of the November images using just the stock kernel.

You can find the instructions on topjohnwu's post in the Pixel 2 XL forum: https://xdaforums.com/pixel-2-xl/development/2017-11-6-root-pixel-2-xl-t3701176

It requires a different version of the Magisk Manager as well as a different build of 14.4 (all located in the thread).
[Google Pixel 2 Guides, News, & Discussion] xda890:
This still works after the nov update for Pixel 2?

---------- Post added at 03:43 PM ---------- Previous post was at 03:11 PM ----------

When I open Magisk Manager and choose Install and patch boot img option, my phone just opens the Download app and I do not get any further?
[Google Pixel 2 Guides, News, & Discussion] Ashyford:
November 5 OTA (successful)

adb reboot bootloader (successful)

fastboot flashing unlock_critical (successful; required to unlock bootloader; erases all personal data)

fastboot boot twrp-3.1.1-alpha1-walleye.img (successful)

sideload "Magisk-v14.4.zip" (successful)

./adb pull /sdcard/recovery.log (failed on multiple attempts including data/media/0/recovery.log)

I have root. However, I experience a "SafetyNet API Error" when checking if I pass "Safetynet" even after rebooting, hiding Magisk, and unhiding Magisk. I also can't hide Magisk Manager (it fails). I did not flash the Snoke Kernel. Any ideas as to what I should look into? I searched this thread but didn't find clues on what to do next.

Unrelated: I backed up to Google Drive yet my pictures, latest text messages, and at least 19 apps did not restore. Annoying.
[Google Pixel 2 Guides, News, & Discussion] bryantjopplin:
Are you using the magisk apk that [MENTION=4470081]topjohnwu[/MENTION] posted labeled as 14.4.1 believe?
[Google Pixel 2 Guides, News, & Discussion] xda890:
Never mind, I am just stupid.. Guess it just asks me which boot image to patch.... :-|
[Google Pixel 2 Guides, News, & Discussion] Ashyford:
Thanks! I read that some people had issues with 14.5 and didn't know there was another zip. I see a Magisk-v14.4(1444).zip in topjohnwu's thread. I'll read up on it to see if this is the right direction.
[Google Pixel 2 Guides, News, & Discussion] bryantjopplin:
Also use the app there as well
[Google Pixel 2 Guides, News, & Discussion] JayBlack_686:
One question, in case I end up having to do this again sometime - Magisk Manager asks if I want to install. I say yes, patch boot image, pick the image, and Magisk Manager then downloads whatever version of the magisk zip it wants; I did not see any way that I could instruct it to use the Magisk-v14.4(1444).zip. How do you tell it to use that particular zip?
[Google Pixel 2 Guides, News, & Discussion] bryantjopplin:
That's actually it twrp worked on Nov update and 8.1. kinda pointless at this point. The app is the only way if on these. Just fastboot flash the patched image it makes.
[Google Pixel 2 Guides, News, & Discussion] Xxnoobkiller420xX:
can't find patched_boot.img

I can't find patched_boot.img . I don't get it. Who the hell is snoke? Should I use the .img in the google drive that somebody posted? And if so, for the Pixel 2, is it the R7 P2 or the R8P2.

"Irrational self-confidence will get you more ***** than rational defeatism." -Neil Degrasse Tyson.
[Google Pixel 2 Guides, News, & Discussion] xda890:
I followed this:

But after flashing the patched boot image, Magisk Manager still says Magisk is not installed. Does this "recipe" not work anymore? I am on the latest nov release, 025.
[Google Pixel 2 Guides, News, & Discussion] penciluser:
you need to download your factory image and extract the boot.img.

Then use Magisk Manager 5.4.1 to patch it
[Google Pixel 2 Guides, News, & Discussion] xda890:
Where can one find Magisk Manager 5.4.1?

---------- Post added at 11:07 PM ---------- Previous post was at 10:22 PM ----------

ok, never mind.. Did a more detailed search and found the version 5.4.1. And I now have root.. :)
[Google Pixel 2 Guides, News, & Discussion] csxt8142:
Getting error message in Magisk app:

Unable to Repack boot image!

Failed!

Can't seem to find this error repeated anywhere

EDIT: ran it again and it worked. Random

---------- Post added at 08:24 PM ---------- Previous post was at 07:43 PM ----------

Not sure what's going on, but this did not work for me. I received no error messages--everything stated it flashed correctly. But upon reboot, I do not have root. When loading Magisk app, I get

Latest Magisk Verson v14.0 (green/check)

Magisk is not installed (red/X)

Not rooted (red/X)

Safety Check Success

ctsProfile: false (red/X)

basicintegrity: true (green/check)

From what I can tell, the only thing that changed after flashing the patched_boot.image is that my "ctsProfile: false" was Green/Check prior to flashing. Not sure what steps I need to take from here...?

EDIT: WORKED!! Had to update magisk app from 4.5.0 to 4.5.1 and repeat the process. THANKS!!
[Google Pixel 2 Guides, News, & Discussion] hawkinsst7:
People have been asking that since the trailers for Episode 7!

Here I am reading about the best way to root my p2 and I just couldn't resist the star wars joke.
[Google Pixel 2 Guides, News, & Discussion] ljbrenes:
Quick question, can you unlock bootlader and root the pixel 2 even if it came from Verizon? Thanks.
[Google Pixel 2 Guides, News, & Discussion] multi_rom_user:
No not at the moment.
[Google Pixel 2 Guides, News, & Discussion] ljbrenes:
Shoot! is it because of Knox? if so, then it probably never will get root. I have an S6 and it never got root because of Knox. I was looking to having a new phone again that could be rooted.
[Google Pixel 2 Guides, News, & Discussion] multi_rom_user:
I don't recall having Knox on the Pixel devices. But Verizon is the culprit for the bootloader remaining locked and I can understand why they put that in place.
[Google Pixel 2 Guides, News, & Discussion] Telperion:
Has anybody gotten DP1 rooted? The XL2 users are able to use the Magisk patch method, but P2 doesn't have an image on Google's dev page. Is there any current way to pull the existing boot image from DP1 and patch it? Perhaps a 'dd if' from TWRP Alpha to pull the image to the /system/ partition, then adb pull to get it to a computer, reboot to system, push to phone, patch with Magisk, then flash from bootloader.

I'm back on 8.0.0 Nov after a failed attempt at hybrid patching P2's DP1 boot image, this was a piece of cake to get working with Magisk.
[Google Pixel 2 Guides, News, & Discussion] lightningdude:
I booted TWRP Alpha on my 8.1 and sideloaded the Magisk 14.4 zip. Worked like a charm, patched the boot image directly from the phone.
[Google Pixel 2 Guides, News, & Discussion] phonefreedom:
Hung at the "G"

Hello Team,

This is driving me nuts. I have been able to step through the short cut and create a "patched_boot" and then issue to the fastboot command for it per the instructions. After re-booting the device is stuck at the "G" screen and never recovers further.After waiting for 25 minutes I even tried issuing the "fastboot flash boot" command a second time for the patched_boot without any different results.

What should be my next steps?
[Google Pixel 2 Guides, News, & Discussion] Natakranta:
Download factory image from Google, unpack it, insidebis another zip, there is boot.img file

Flash it to both slots A and B. It must be the same version/update your phone was on.

fastboot flash boot_a boot.img

fastboot flash boot_b boot.img

If you're not sure which exactly stock rom build your phone is on, use the flash_all.bat to flash the whole image on your phone, to be sure you have no mismatch between system and boot. Just remove "-w" from the bat file so it doesn't erase your user data
[Google Pixel 2 Guides, News, & Discussion] phonefreedom:
Hello Natakranta,

Thank you. I wasn't aware of that I could just flash the boot.img to both partitions. I have that in my notes for the future. I ended up re-flashing all to recover out of this.

I'm baffled the rooting process didn't work though. I guess i'm on hold till something better comes along as a process.
[Google Pixel 2 Guides, News, & Discussion] Natakranta:
So you last all your data using flash_all.bat?

Remember next time the trick with removing "-w" from the script.

Rooting process is fairly simple, especially now when you have bootloader unlocked and just flashed full factory image. It means fastboot on your PC works good. You can root it now in 3 easy steps.

Extract boot.img file from the factory image you have just flashed and copy it to your phone.

On phone install latest Magisk Manager app and chose install Magisk, patch boot.img and chose the one you have just copied to your phone. Magisk Manager will use it to create you patched_boot.img file and save it in sd/Magisk Manager folder. Copy this patched_boot.img file to your pc.

On PC open command promot/power shell from within the PC folder where you have just copied the patched_boot.img file and type

adb reboot bootloader

Phone will reboot to bootloader (aka fastboot mode). Now check on phone screen which slot is active, A or B, and type

fastboot flash boot_a patched_boot.img

or

fastboot flash boot_b patched_boot.img

Then after it finishes type

fastboot reboot

and phone will reboot to system on patched boot img. Magisk Manager should now display that phone is rooted and be able to grant root access to apps you want.

Do print screens on PC power shell, it will be easier to help you if you show what you are doing.
[Google Pixel 2 Guides, News, & Discussion] phonefreedom:
Hello Natakranta,

Thank you for the three step approach. I learned something new in that the patch needed to be flashed to a specific slot. But... there always seem to be a "but", my result was still stuck at the "G" screen. Before flashing, I did verify that I was on slot A and that is where I flashed the patch to.

In the instructions provided, it was mentioned that both slot A and B needed to have boot.img matching to recover from this. Wouldn't that be the same for patched_boot.img? I'm trying to figure out why this simple approach isn't working correctly.

BTW, Flashing the stock boot.img to A and B didn't recover my device, as I had to use the flash_all.bat to recover again. :(
[Google Pixel 2 Guides, News, & Discussion] Natakranta:
Hard to say as I don't see what was going on in the command prompt. It worked for me so there's something you are doing different. Are you using USB 2 port on PC? USB 3 port was not working for me.

Since you are clean flashed after doing flash all again, try traditional method. Boot TWRP and side load Magisk 14.5 zip

Or if twrp decryption works and you can see phones storage just fash Magisk 14.5 zip saved on the phone. This will install Magisk Manager app, take a copy of your current unmodified boot.img, save it for the future (if unroot needed) and use it to create a copy of it patched, then it will replace stock boot with patched boot on te boot partition. After you tap reboot on twrp, it should boot system on new patched boot (karnel).

If it doesn't work for you, your phone is cursed :D

Which Magisk Manager are you using?

Use latest Magisk zip 15.5 from official beta thread

https://xdaforums.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589
[Google Pixel 2 Guides, News, & Discussion] VadimTk:
Get unlocked (not Verizon model) phone from Google - you will be able to root it and it still works on Verizon.