yashsingh1/xdaforums huggingface dataset:
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] dmarden:
Some EMR tag on the new files... not sure what EMR is.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] linezero:
I wonder what that EMR tag is. Anybody had luck with the November update?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] cwalker0906:
Beta is on a different site
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] chadhoard:
Is the "fastboot flashing unlock_critical" necessary?? I have seen that here, but people saying they didn't.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] shizat63:
Can we get step by step instructions for n00bs?

Here's what I have thus far. I'm lost on the actual rooting steps.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] joetheshmo:
You can probably skip it, I'm not sure. Just relaying what it says on the factory image page from Google.

---------- Post added at 08:06 PM ---------- Previous post was at 08:04 PM ----------

At the end after you have the patched_boot.img, transfer to a pc and flash it in fastboot mode with 'fastboot flash boot patched_boot.img" and enjoy
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Cowbell_Guy:
What is the appropriate apn file. to download for those of us with unlocked Google play store phones on Verizon?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Veritech:
I did not have to unlock_critical and am on 8.0.0, stock kernel. I just unlocked bootloader and followed the Magisk install instructions and enjoying the rooted life again. I have done several reboots and root remains in place.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Fenny:
Good call, I saw it got pulled, but I guess that was not for the pixel XL. Looks like I wasted a bunch of time making a boot image that would dump the stock boot for me xD.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] ilal2ielli:
Looks like what was mentioned earlier is true, modules are missing on the module page even after installed properly, but will still be active.

Got my PS4 Remote Play working on my Pixel 2 XL with the November OTA.

Root works perfectly as well even after a reboot.

Thanks [MENTION=4470081]topjohnwu[/MENTION]!
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] bggold:
Dirty flashed Nov factory over Magisk and all is well. Did have to go through the rooting steps and flash the patch_boot.img , but expected that.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] docluv01:
Nov Update

Hey guys,

What would be the proper way to apply Magisk and Snoke Kernel on the NOV Update?

If I crate a patched boot via magisk, do you simply sideload the kernel?

Thanks in advance
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] cooltranier13px:
Will this work on Android 11 beta?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Lughnasadh:
Yes, Magisk will work on Android 11 beta. Just make sure you use the latest Canary version. https://github.com/topjohnwu/Magisk
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Alxoom33:
Yes, working great!
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] bdr127:
The latest Magisk (v20.4) is not working for me on Android 11 on my Pixel 2 XL.

I flashed the Android 11 update. Then, as always, I installed TWRP and then installed Magisk from there. I'm now stuck in a boot loop.

I tried the Magisk install patch method from within Magisk Manager, but that results in a boot loop as well. (The only possible caveat here is that I'm running v7.5.1 because I can't find a working link to the "canary" version of Magisk Manager.)

Any help would be greatly appreciated!

EDIT: I found the debug version of Magisk Manager (in this post: https://xdaforums.com/showpost.php?p=83467991&postcount=3750), changed the setting to use canary, and installed the canary version. Then I used the patching method to install Magisk and everything works perfectly.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Lughnasadh:
1. You need to use Canary on R (both Manager and Magisk). Make sure you set the Canary Manager update channel to Canary.

2. You cannot install TWRP and use Magisk at the same time on R. You can only use TWRP by fastbooting it up, not installing it, when using Magisk.

3. Latest Canary Magisk Manager link seems to be working fine... https://github.com/topjohnwu/Magisk
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] bdr127:
Thanks for your reply. Please see my edit above. Got it working.

On the github page, where is the Magisk Manager apk, specifically? I see the link to the Magisk zip, but not the manager.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Lughnasadh:
See attachment...
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] bdr127:
I'm apparently blind. :p Thanks for your responses!
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] SketchSlayer:
So OP is clearly outta date, as you get a message in magisk saying this version does not support boot image file patching...

So yeah... GG

Anyone got up to date instructions for rooting this pile of burning trash?

Grabbed one of these that was going cheap to replace a beat up moto e5+ (honestly it was cheaper than fixing up the beautifully smashed screen) and am immediately reminded why I never buy google hardware, default encryption that requires rooting to turn off is a level of dumb I will never understand alongside other terrible default settings literally requiring risking bricking a device to put it on basic sensible settings...

I'd say cobains guitar shoulda said google employee not cop,

So yeah, could really use up to date instructions for rooting one of these dumpster fires so I can get on with fixing the default settings/removing bloatware/maybe replacing the whole crapshoot of a default android build it comes with... all my least favourite androids I've owned have been google made hilariously.

Even with the canary magisk the twrp flash crashes when you tell twrp to go into flash so clearly there is more to it that flashing the patched boot image, not even surprised the worst androids are made by google, their whole motto is "we're obviously evil"
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] 73sydney:
Hers a tip, a post like that is not going to get you a first rate response

Telling people in your first post how much you hate the device isnt going to win you friends...

Having said that, heres the top tips:

1) Dont install TWRP, fastboot to it when needed (known issue with boot loop if you install it, many have reported - its mentioned MANY times, would likely come up in a search)

fastboot boot twrp-xxx.img

If you have flashed TWRP, flash the original unpatched boot.img, and start over...fastbooting TWRP

2) You can rename the magisk-xxxx.apk to magisk-xxx.zip and flash via (fastbooted) TWRP and avoid boot image patching completely (information freely available in the main magisk post)

3) Maybe dont tell people how bad the device they (and others) spend a lot of time keeping working for others is....

4) Avail yourself of the search function and read opening posts of things like Magisk...
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] clothednblack:
I didn't unlock critical on 8.1 and rooted just fine
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] UpGrad3:
This is brilliant! just before i do this can someone share the link or the name of the correct boot image for me i have a UK unlocked Pixel 2 and i see there are a few different images on the image site

Also do i need to install TWRP first of can i literally just perform this process on a stock os ?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] tgrgrd00:
Just to make sure I'm doing this right coming from my Nexus 6. After unzipping the factory image there are a lot more .img files that what I was used to previous.

Which files did you flash?

I'm used to flashing boot, system, radio and recovery. (I don't even see a recovery img in here now) but I'm not sure if that is still the case or if there are additional files to flash now.

thanks!
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] bggold:
What are you trying to accomplish? Do you already have root and want to update to Nov?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] tgrgrd00:
Yep. I'm rooted with Magisk and want to install the November update. On my previous devices I would flash the files mentioned previous and keep the data. I'm just trying to figure out the best way to update nowadays and make sure I'm flashing the correct files.

thanks
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] MariuxReloaded:
What about monthly security patches?

Hi guys and hi [MENTION=4470081]topjohnwu[/MENTION], thank you very much for your efforts! :D

I've a question for all of you: when my Pixel 2 XL arrives (next week), I will root my phone with Magisk, but when there will be the new monthly security patches and, of course, I will have to patch the boot image again to reacquire root, can you tell me which parts of the new firmware will I have to flash, together with the patched boot image, in order to update my Pixel to the new security patch, without loosing data:

1-Patched boot

2-Recovery (Unless I'm using TWRP)

3-System

4-Vendor

5-Bootloader

6-Radio

And that's all, right?

I'm coming from a Nexus 6 and the firmware packages are different, so I need to know what to do.

Thank you very much in advance ;)
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] bggold:
All I did was extract the factory image and remove the -w from the flash-all.bat file.

Make sure to remove the -w or else it wipes the phone.

Booted to bootloader and ran it.

After it reboots go through the rooting steps again. Piece of cake.

By the way don't be alarmed with all the missing file messages when you run the batch file. Safe to ignore.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Larzzzz82:
How long does the first boot with the patched image take?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] docluv01:
Hi, I had used the method posted a few pages back, where you boot into twrp, sideload the kernel, and sideload the magisk zip, worked great

Will this method still work after taking the Nov update ? or do you have to fastfoot flash the patched boot.img? If so, how do u get the kernel updated?

Thanks
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] lucky_strike33:
LIke a normal reboot
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Larzzzz82:
something didn't go right then... lemme see where I messed up.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] mngdew:
The root works great! Made a small donation for your hardwork.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] bggold:
No sure I run stock kernel. You might want to check on that forum.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] FSMcas:
On my Pixel 2 when trying to patch the boot image, Magisk Manager gives me the error:

So, in the first post nothing about the need for a custom kernel is said. Do I still need one or is this error based on another problem?

(I use the bootloader.img and not the boot.img inside of it. Is this a problem?)
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] tgrgrd00:
flashing flash-all.bat without the -w worked perfect. Ran through making the patched_boot.img and viola rooted with Nov update. Thanks for your help!

Now if I could just figure out why no data is passing through the wireless tether on Sprint using the Magisk tether module (or build.prop edit) my device would be perfect.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Didgeridoohan:
That is exactly the problem. Bootloader and boot are two very different things... You need the boot.img.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] bd177:
You need to use the boot.img
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Golf c:
Those are for two separate partitions, that do different things.

Boot partition=boot image

The kernel resides in the boot image.

Bootloader partition =bootloader image

You should never flash a image too the wrong partition. It usually won't work anyway. You need the boot image for the boot partition.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] FSMcas:
Oh, okay. I could not manage to extract the boot.img on my Mac, but I'll try on Windows tomorrow. Better luck then :)

Thank you, all of you! :o
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] nibblet787:
Slightly off topic, but has anyone gotten Tasker to recognize root with this version of Magisk? When I create a task that requires ticking the Use Root box (such as the Kill App option), Tasker says "Your device doesn't appear to be rooted". I tried uninstalling/reinstalling and clearing data, but no luck.

Since Magisk is so shiny and new on our device, I thought I'd start my troubleshooting here, before heading over to the Tasker forums.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] docluv01:
Hmm, is the kernel even needed ?

I thought it was needed for ANdroid Pay?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] bggold:
Nope pass safety net no problem.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] sharkie405:
I don't use Tasker, but I use automate. When I use this version of magisk, my automate flows that needed root didn't work. My particular issue was to do with selinux needing to be set to permissive instead of enforcing. I never had that problem with SuperSU, so maybe SuperSU does that, whereas Magisk does not? In any event, maybe that's your issue? If so, check out Selinux Switch by Ibuprophen. That worked for me on Oreo 8.1.0.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] nathanchance:
Everything is working fine with the November security update.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] abuttino:
When I flashed the factory image, I get System Is corrupt and it hangs at the G with the unlocked icon. Had to go back to 010, then use ADB sideload for the OTA.

Anyone else experience this?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] sharkie405:
Did you use the newest platform tools? Version 16.0.2...I think.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] elreydenj:
Flash kernel not ready for us to try out yet??!!
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] bjrmd:
No problem for me, shell scripts are working, all root options.

I am running stock everything, 8.0

Perhaps try some other type of operations to pin the issue down. Tasker can be finicky.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] bggold:
No problem, glad it worked.

Sorry cant help with the tether. I'm on verizon with hotspot enabled.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] piccit:
You have to use ' su -c "cmd" ' instead of the use root option. It might be worth bringing up in Tasker forums tho, it would be nice if it could be updated to check for root in a more generic way
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] nathanchance:
Will be out when 4.4.97 drops ;)
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] davidcw6:
I thought remote play broke some months back

Either way. Going to try this with Nov patch now
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] abuttino:
My sdk is having problems with a hash of the latest platform-tools. I guess I'll uninstall/reinstall it tomorrow and try again. Not that I like soft-bricking my phone but, it's an easy fix.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] chadhoard:
I believe something went wrong. How can get all the way back to stock 8.0?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] g3v0:
My general steps to update though were:

Fastboot flash boot, system, vendor imgs from stock factory image.

Reboot and do OTA update.

Download the new factory image from Google, extract boot.img and replace the zImage with the one from R10.

Flashed the modified boot.img (not sure if necessary).

Reboot and patch boot image in MagiskManager.

Now for some reason, the newly created patched_boot.img file is not visible when I connect my phone to my PC (it showed and transferred the old one when I tried). I used a file manager app to copy and paste /sdcard/MagiskManager/patched_boot.img into /sdcard, where it was visible, and transferred it to my computer.

Fastboot flash the patched_boot.img

Reboot with Magisk/root and Snoke's R10 permissive

I experienced the audio cutting out and general instability when I was trying to run dolby or am3d. Make sure you have no other equalizers enabled and disabled the builtin MusicFX app in settings.

I'm running R10 (not se); that might have something to do with it. Maybe try installing this module (haven't tried it myself): https://xdaforums.com/apps/magisk/module-magisk-selinux-permissive-script-t3577549

After you install viper, turn on the "master power" before playing a song, or turn it on after and change the song.

If it still doesn't work, worst case just go into viper settings -> FX Compatible -> Compatible, though I've found that not all of the effects fully work.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] js042507:
Check out your superuser list in Magisk Manager. If you see Tasker, single click and hit the trash can to remove it. Now go in Tasker and create a new task. I call mine 'Root Test'. For the task, select Code --> Run Shell. Then for the command use 'su' for superuser, and check the 'use root' checkbox. Now run the task and you should get a toast notification to grant root privileges.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] dr_rick13:
can anybody shed some light on how I can root if I'm already on November security update?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] chadhoard:
I downloaded taimen-opd1.170816.010-factory-c796ddb4.zip. Fastboot flashed the boot, system, and vendor from this. When I reboot, I got a couple errors about being corrupt. Now it is stuck on the Google logo screen with an unlocked symbol on the bottom of the screen.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] ilal2ielli:
Just need to install Sony Framework Module in Magisk, install most recent Remote Play apk, then before running it remember to hide it in Magisk.

Same steps as in OP but use November images that are now posted by Google.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] TaintedByte:
FWIW to anyone with a Pixel 2 (non XL) browsing this thread, I can confirm that this method worked for me 100% on both of the November images Google released yesterday and today. This is on stock kernel even.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] zachman1750:
Viper4Android working

Thank you so much for your response (viper means a ton to me). I was able to get Viper4Android working (the magisk 14+ version in the modules download section) by repeating the steps I outlined earlier in this thread, but using R10 kernel (NON-SE) instead of the R9se kernel. The permissive linux mode must have done the trick.

Thanks to [MENTION=2955144]bryantjopplin[/MENTION] for the initial tip on getting the correct Viper module and disabling the MusicFX app!
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] g3v0:
First, make sure you have run "fastboot flashing unlock_critical" at some point before. I think for the 2XL, we need the unlock_critical. (note this wipes user data)

My other suggestion for going back to stock is extract the zip and everything in it. Edit the flash-all.bat (for windows) or .sh (for linux) file. I used Sublime Text, notepad should be fine too. At the end of the file, look for a fastboot command and remove the "-w" flag there (this is the wipe flag). Save then run the file with your phone in fastboot.

Though at this point, might as well do the above with the latest factory image (Nov security update).

Np, glad I was able to help. Viper's like my #1 reason for rooting :p
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] bggold:
Just follow the OP it works just fine. No TWRP needed.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] dr_rick13:
Thanks boss. And if I wanna flash a custom kernel?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] nibblet787:
I tried this first, using the app you mentioned, but it didn't seem to work. It sounds like it should, so I'm not sure why it didn't.

DING DING DING!! Winner winner, chicken dinner! This worked perfectly! I put this in a shell script and now I can stop pulling out what's left of my hair. Thank you!

This is typically my problem, but this time Magisk wasn't even acknowledging that Tasker existed and vice versa. But yeah, putting 'su' in the shell script instead checking the Use Root box is EXACTLY what I needed. Thank you as well!
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] bggold:
Check out the kernel forum for that info. There is a special magisk for snoke.

---------- Post added at 03:20 AM ---------- Previous post was at 03:16 AM ----------

Had the same problem with automate and I had to set selinux to permissive also. The dev mentions that when running magisk set to permissive. That very well could be true with Tasker.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] zachman1750:
Viper4Android + SnokeKernel guide

FYI I put together a simple Magisk/Root + Snoke + Viper4Android guide for 8.0 only in this thread for those of you still having issues.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] tm1238:
Did anyone use either of the advanced settings in Magisk (Keep force encryption, Keep dm-verity)? Any advantage/disadvantage to checking these options? I'm assuming the device won't boot if "Keep dm-verity" is selected. Thanks for any help, haven't rooted in several years and first time Magisk user.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] nexus_man12:
I've been running Magisk for a while on my 6P with PureNexus installed and never had an issue with Blackberry Work app. But I've never been able to "hide" it from being detected when on stock using Magisk. I just tried again on my 2 XL earlier today when I woke up to the news of Magisk working, but the app immediately detected root after set up even though I had it selected in Magisk Hide.

Does anyone here use Blackberry Work for their work emails and has gotten it to work with Magisk?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] MariuxReloaded:
So, in this way, we can update our device to the new monthly security patches without loosing Magisk root or do we have to patch again the boot image with Magisk Manager after every update?

And when the TWRP recovery will become stable and we'll be able to flash Magisk.zip through it, will the procedure be always the same or will it change?

Thank you very much in advance :good:
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] TheDude:
I have not unlocked critical. Everything works fine for me. I may regret it in the future if I must unlock critical and wipe but at the moment I see no reason why. This stuff seems a bit criptic ATM (you may need to etc) according to the Google factory image page. But I cannot find any real documentation on it. So I have held back on critical unlock and everything thus far is golden. The one kernel flashes fine, root works perfect (Thank you!) And I can flash factory images. I suspect critical pertains to bootloader level modifications / trustzone shizzle that I (and most) will never have a need to modify. When I see Google offer 2 levels of unlocking... And they call one critical... I for a security piece of mind hold off on the critical part until absolutely necessary. That's my two cents, everything works fine. All these posts suggesting unlock critical is necessary is total bull shizzle. If you are having problems, it is not your solution. Bark up a different tree.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Lawlrus:
Root is contained in your kernel, which you update by flashing the newest image.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] MariuxReloaded:
Ok, so we'll have to patch boot image very time, thanks :good:
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] TheDude:
Man, we don't even have a solid recovery yet. Your jumping the gun. There will be goodies down the road. Eg. Flashfire etc. I understand this example is not magisktically appropriate but it's my example... You are asking for automation with no twrp. Not yet bro, hold on and it will come. In order to automate an ota update you got to flash factory boot, install ota, repatch and re flash... This is twrp stuff.