Develop Bugs

[ROOT] Magisk AutoRoot: Magisk + phh's SuperUser for Nougat (No TWRP required)

People are panicking about TWRP not working on the latest Nougat firmware.
As an advanced user like me, I cannot live with a device with no root, so here is my solution.
Oh, and of course, your device need to be either bootloader unlocked, S-OFFed, or both.
What Is Magisk
Maybe.... you live under a rock?
Magisk Subforum on XDA
What This Will Do
Following the instructions here will install Magisk v9.1 (nearly same as official v9 with some fixes for cache support) and phh's SuperUser to your device.
You DON'T need any custom recovery, and your system partition is NOT touched at all.
Files and binaries are stored in the cache image, Magisk will move them to /data in the next reboot.
You can upgrade Magisk, phh root, and install other Magisk Modules within the Magisk Manager app!
Instructions
If a prebuilt boot image is available:
Download "magisk+phh_arm64_cache.zip", your prebuilt boot image, and unzip both
You should get "patched_boot.img" and "magisk_cache.img"
Install Magisk Manager and phh's SuperUser app
Reboot your device to download mode (adb reboot download)
Manually flash the images:
Code:
fastboot flash boot patched_boot.img
fastboot flash cache magisk_cache.img
Reboot and you're done!
If you are using other bases, then grab your boot image from your OTA package, and follow the instructions:
Download "magisk+phh_arm64_cache.zip", "magisk_boot_patcher.zip", and unzip both
You should get "magisk_cache.img", and a folder with scripts and tools
Grab ANY rooted device >Android 5.0 to do the patching. Running the scripts on an unrooted device will create an unbootable boot image!
Follow the instructions in the README.txt of the tool, it shall guide you to patch your own boot image
Downloads:
Prebuilt Cache Images:
ARM64(HTC 10): magisk-v9.1+phh-r266-2_arm64_cache.zip ​Prebuilt Boot Images:
US Unlocked: US_Unlocked_2.28.617.8_boot.zip​Magisk Manager:
Latest Magisk Manager​phh's SuperUser app:
​phh's SuperUser (PunchUp Beta 9)​

Reserved
Reserved

Just installed on US Unlocked HTC 10 running Stock Android N. Works great. I now have root back. Thanks for doing this.
Also, @topjohnwu correct me if I'm wrong, but if you install a Magisk Module that prevents your phone from booting, you can just re-flash the cache image. That would remove all modules you may have added and start back with just root.
And as an added bonus, I am also passing SafetyNet which I was not before do to the unlocked bootloader. Great work.

Sorry if it's already been answered in a different form it has been a while since I've been on here butt Am I able to just pull the boot image file out of the roms zip I am using or could I use the backed up boot image from the nand backup I have. Or do I have to do the Adb method. Thanks in advance.

Works great! Thanks for your work and share! @ topjohnwu
---------- Post added at 05:02 PM ---------- Previous post was at 05:02 PM ----------

This works well thank you. Has anyone been able to get xposed to work within it? I've tried to download all 3 and it will not install them - says Can't load the content at the
moment
EDIT - didn't know Xposed need SDK 24 for N... So disregard last bit

Will this work with Viper10 rom based on 2.28.401.6?

sardroid said:
Will this work with Viper10 rom based on 2.28.401.6?
Click to expand...
Click to collapse
it already has magisk/phh superuser. so there is no need to try this.

Excellent, device rooted..
Question : Now, can i delete Magisk Manager ??

Followed instructions using prebuilt 2.28.617.8. I'm getting a bootloop at green HTC logo.
Sent from my Nexus 9 using Tapatalk

I don't understand how to proceed if not US version :/

..
---------- Post added at 12:40 AM ---------- Previous post was at 12:37 AM ----------
GhastlyTT said:
Followed instructions using prebuilt 2.28.617.8. I'm getting a bootloop at green HTC logo.
Sent from my Nexus 9 using Tapatalk
Click to expand...
Click to collapse
Do you have any MicroSD inserted ? If yes, remove it.

psicobelico said:
..
---------- Post added at 12:40 AM ---------- Previous post was at 12:37 AM ----------
Do you have any MicroSD inserted ? If yes, remove it.
Click to expand...
Click to collapse
Thanks for the reply. I had thought of that and removed it-still boot looping.

@topjohnwu Any idea how to fix? I am also getting stuck on the green htc logo and it is just bootlooping.

serophia said:
@topjohnwu Any idea how to fix? I am also getting stuck on the green htc logo and it is just bootlooping.
Click to expand...
Click to collapse
I have to ask, what Rom are you using? Did you update to N OTA? Are you on Viper or one of the beta ICE or LeeDroid versions?

jsaxon2 said:
I have to ask, what Rom are you using? Did you update to N OTA? Are you on Viper or one of the beta ICE or LeeDroid versions?
Click to expand...
Click to collapse
I fixed the bootloop by extracting the stock OTA boot.img and flashing that. I did update OTA from M using TWRP then SD card flashing the firmware.zip. Really want your stock dialer module back lol.

jsaxon2 said:
I have to ask, what Rom are you using? Did you update to N OTA? Are you on Viper or one of the beta ICE or LeeDroid versions?
Click to expand...
Click to collapse
I OTA to Android N and wanted to try this out. Just flashed a stock boot.img and will see if that fixes the bootloop.

GhastlyTT said:
I fixed the bootloop by extracting the stock OTA boot.img and flashing that. I did update OTA from M using TWRP then SD card flashing the firmware.zip. Really want your stock dialer module back lol.
Click to expand...
Click to collapse
serophia said:
I OTA to Android N and wanted to try this out. Just flashed a stock boot.img and will see if that fixes the bootloop.
Click to expand...
Click to collapse
We're either of you using Magisk prior to OTA? I'm wondering if the magisk.img file was still in /data after you updated.
I RUU'd prior to taking the OTA so I was coming from a clean phone and did not have any problems installing this.

GhastlyTT said:
I fixed the bootloop by extracting the stock OTA boot.img and flashing that. I did update OTA from M using TWRP then SD card flashing the firmware.zip. Really want your stock dialer module back lol.
Click to expand...
Click to collapse
jsaxon2 said:
We're either of you using Magisk prior to OTA? I'm wondering if the magisk.img file was still in /data after you updated.
I RUU'd prior to taking the OTA so I was coming from a clean phone and did not have any problems installing this.
Click to expand...
Click to collapse
I was in fact using Magisk. I took the OTA with Magisk and Root installed. In fact, i have the AOSP lockscreen still lol.

jsaxon2 said:
We're either of you using Magisk prior to OTA? I'm wondering if the magisk.img file was still in /data after you updated.
I RUU'd prior to taking the OTA so I was coming from a clean phone and did not have any problems installing this.
Click to expand...
Click to collapse
Yes I was but i thought flashing stock boot.img will remove magisk seeing as how it allowed me to ota onto Android N perfectly fine.

Magisk on Nougat

Anyone have any luck getting Magisk 11.1 working on Nougat? Have done a ton of searching and a bunch of experimenting and nothing seems to work. I've always used traditional root, so if there's some obvious trick to getting it working, sorry in advance!

xxBrun0xx said:
Anyone have any luck getting Magisk 11.1 working on Nougat? Have done a ton of searching and a bunch of experimenting and nothing seems to work. I've always used traditional root, so if there's some obvious trick to getting it working, sorry in advance!
Click to expand...
Click to collapse
First flash the kernel with f2fs fixes v2 by tomparr than magisk 11.1 via twrp.
But safety net is not working didn't try it with magisk su instead of supersu.

prins29 said:
First flash the kernel with f2fs fixes v2 by tomparr than magisk 11.1 via twrp.
But safety net is not working didn't try it with magisk su instead of supersu.
Click to expand...
Click to collapse
Not OP, but last I checked that resulted in a kernel not found error at boot and that was like two days ago with the same exact versions you've mentioned. Has anything changed since then or I'm missing something?

lpchaim said:
Not OP, but last I checked that resulted in a kernel not found error at boot and that was like two days ago with the same exact versions you've mentioned. Has anything changed since then or I'm missing something?
Click to expand...
Click to collapse
He updated the file with changes .. and there is new update of TWRP by Alberto which is released today .With f2fs fixes. so u can check it out too.

prins29 said:
He updated the file with changes .. and there is new update of TWRP by Alberto which is released today .With f2fs fixes. so u can check it out too.
Click to expand...
Click to collapse
I've just tried again with the new TWRP and redownloaded files on my phone to be doubly sure, result is the same error others are reporting. Mind detailing how you managed to get Magisk running exactly? I've been looking around for a few days and never found consistent reports of it working on Nougat specifically, so it'd come in pretty handy.

Bump. Anybody succeed yet?

Try the Magisk 12 Snapshot. For me it works.

-=MoRpH=- said:
Try the Magisk 12 Snapshot. For me it works.
Click to expand...
Click to collapse
Can you write a guide please?

Here is how i got it working:
1. Make sure u have a clean unrooted Nougat Installation
2. Flash the TWRP from Alberto and make a full Backup
3. Flash magisk 12 (From here )
4. Reboot and Install the Magisch Manager 5.0
5. If no root there boot into recovery and flash the f2s Kernel
6. Flash magisk again and reboot...
7. Magisch should work now.
If not idk what if done right. My Setup is working fine.

-=MoRpH=- said:
Here is how i got it working:
1. Make sure u have a clean unrooted Nougat Installation
2. Flash the TWRP from Alberto and make a full Backup
3. Flash magisk 12 (From here )
4. Reboot and Install the Magisch Manager 5.0
5. If no root there boot into recovery and flash the f2s Kernel
6. Flash magisk again and reboot...
7. Magisch should work now.
If not idk what if done right. My Setup is working fine.
Click to expand...
Click to collapse
V12 definitely doesn't have an error when flashing like v11.1 did, but still doesn't pass safety check even after clean flashing flashallthetime's retbr build. Anyone get this to work with any other roms? One thing I noticed that was odd after clean flashing was viper and Dolby were installed but Dolby crashed and viper said drivers weren't installed. Weird.
Edit: Reflashed several different roms without zip. Tried using unSU zip + epsilon. No way to safetynet to pass, I give up. No androidpay/pokemongo is a small price to pay for working notification sounds, adblock, and greenify.

Hello not working for me ROM stock Nougat Épsilon
Regards
Enviado desde mi XT1635-02 mediante Tapatalk

iron maiden said:
Hello not working for me ROM stock Nougat Épsilon
Regards
Enviado desde mi XT1635-02 mediante Tapatalk
Click to expand...
Click to collapse
I'm pretty sure Epsilon is pre-rooted, as it says in his OP.

xxBrun0xx said:
I'm pretty sure Epsilon is pre-rooted, as it says in his OP.
Click to expand...
Click to collapse
yep, but i delete de supersu zip from the rom

So i did it again, and it works
1. Flash the f2fs Kernel
2. Flash SuperSU R3
3. Flash Magisk v12
4. Clear Cache
5. Reboot

-=MoRpH=- said:
So i did it again, and it works
1. Flash the f2fs Kernel
2. Flash SuperSU R3
3. Flash Magisk v12
4. Clear Cache
5. Reboot
Click to expand...
Click to collapse
How do you pass safetynet with SuperSU? Magisk v11.1 and up has SuperSU built in, why flash it?
Not trying to give you a hard time, just trying to understand. Really appreciate the help!

Dont aks xD
Without that it won't work. Magisch patch the SuperSU away and replace it with MagiskSU and pass SaftyNet fine.

-=MoRpH=- said:
Dont aks xD
Without that it won't work. Magisch patch the SuperSU away and replace it with MagiskSU and pass SaftyNet fine.
Click to expand...
Click to collapse
Did you take a nougat OTA? I didn't, so I wonder if my problem is that I'm still on the marshmallow bootloader/modem?

Yes im on the Stock Nougat. But the bootloader or modem shouldn't make a difference.
But there could be a problem with the Custom roms.

-=MoRpH=- said:
Yes im on the Stock Nougat. But the bootloader or modem shouldn't make a difference.
But there could be a problem with the Custom roms.
Click to expand...
Click to collapse
I'll see if I can find a completely stock nougat rom that doesn't come pre-rooted. Think flashallthetime still has one on his devhost.

xxBrun0xx said:
I'll see if I can find a completely stock nougat rom that doesn't come pre-rooted. Think flashallthetime still has one on his devhost.[/QUOTE
I'll pm you with the right one
---------- Post added at 10:00 PM ---------- Previous post was at 09:56 PM ----------
xxBrun0xx said:
I'll see if I can find a completely stock nougat rom that doesn't come pre-rooted. Think flashallthetime still has one on his devhost.
Click to expand...
Click to collapse
Here https://www.androidfilehost.com/?fid=529152257862701536
Click to expand...
Click to collapse

Latest Magisk Canary builds can root EMUI9

https://mobile.twitter.com/topjohnwu/status/1077067871660855296?s=20
From the man himself.
Seems as though it's only a matter of time now.

https://github.com/topjohnwu/magisk_files/blob/master/canary_builds/notes.md
Or boot into twrp and adb sideload magisk-release.zip.
I'll try later.

It is possible to root without recovery for Ota updates?

Supzztar said:
It is possible to root without recovery for Ota updates?
Click to expand...
Click to collapse
OTA updates will fail if root is detected.

zgomot said:
OTA updates will fail if root is detected.
Click to expand...
Click to collapse
Is this due to emui 9? Because in 8.1 I've had OTA updates without a problem. Even when rooted with magisk.

curtricias said:
Is this due to emui 9? Because in 8.1 I've had OTA updates without a problem. Even when rooted with magisk.
Click to expand...
Click to collapse
That's strange, I could never take OTA updates while rooted, on any EMUI.

Hi,
I try this "How to" from P20 PRO forum : p20-pro/guide-how-to-finally-root-emui9-t3883295 using P20 twrp_p20_0.1.img by Pretoriano80 here : p20/recovery-twrp-3-2-1-0-t3778585
It works fine, my P20 whith Pie UMUI9 is rooted.
Be carefull :
To have root working, at each start, you have to Boot your phone with holding vol-up button.
Regards

zgomot said:
That's strange, I could never take OTA updates while rooted, on any EMUI.
Click to expand...
Click to collapse
Has to do with the custom recovery not the fact that it was rooted

Titioz said:
Hi,
I try this "How to" from P20 PRO forum : p20-pro/guide-how-to-finally-root-emui9-t3883295 using P20 twrp_p20_0.1.img by Pretoriano80 here : p20/recovery-twrp-3-2-1-0-t3778585
It works fine, my P20 whith Pie UMUI9 is rooted.
Be carefull :
To have root working, at each start, you have to Boot your phone with holding vol-up button.
Regards
Click to expand...
Click to collapse
It is possible to root without custom recovery?

Titioz said:
Hi,
I try this "How to" from P20 PRO forum : p20-pro/guide-how-to-finally-root-emui9-t3883295 using P20 twrp_p20_0.1.img by Pretoriano80 here : p20/recovery-twrp-3-2-1-0-t3778585
It works fine, my P20 whith Pie UMUI9 is rooted.
Be carefull :
To have root working, at each start, you have to Boot your phone with holding vol-up button.
Regards
Click to expand...
Click to collapse
Wow. It's so easy.
Can't seem to flash modules, though, but having root on EMUI 9 is just great!

Supzztar said:
It is possible to root without custom recovery?
Click to expand...
Click to collapse
I don't know.
With this method, you need to patch a recovery_ramdisk image to boot the system with root access
And then, you can't access to twrp anymore with patched image (but anyway, for me, this twrp version does not work anymore with EMUI9 ! => touch screen doesn't work).
Regards

Yes!

curtricias said:
Yes!
Click to expand...
Click to collapse
could you tell me how to do that? thanks

Ducati87 said:
could you tell me how to do that? thanks
Click to expand...
Click to collapse
Download latest magisk build.
Manually change update channel to canary build
https://www.google.com/amp/s/forum....sk-canary-channel-bleeding-edge-t3839337/amp/
Install magisk : patch your recovery_ramdisk
Then reboot bootloader.
Fastboot flash recovery_ramdisk patched_boot.img
When reboot, hold volume up button. As if you want to go to recovery.
But in stead recovery ,your system will boot. And magisk is installed ?

curtricias said:
Download latest magisk build.
Manually change update channel to canary build
https://www.google.com/amp/s/forum....sk-canary-channel-bleeding-edge-t3839337/amp/
Install magisk : patch your recovery_ramdisk
Then reboot bootloader.
Fastboot flash recovery_ramdisk patched_boot.img
When reboot, hold volume up button. As if you want to go to recovery.
But in stead recovery ,your system will boot. And magisk is installed ?
Click to expand...
Click to collapse
what you mean for patch your recovery_ramdisk? thank you.
edit: could be compatible with this: https://forum.xda-developers.com/huawei-p20/how-to/magisk-root-t3777612

Ducati87 said:
what you mean for patch your recovery_ramdisk? thank you.
edit: could be compatible with this: https://forum.xda-developers.com/huawei-p20/how-to/magisk-root-t3777612
Click to expand...
Click to collapse
Did you ever root your device with magisk?

ducati8701 said:
Unfortunately no
Click to expand...
Click to collapse
I suggest that you first read about magisk. And especially how to use it.
When you root your device many things can go wrong and your device can end up bricked.

Problem
So did this on my p20 and all worked well untill some module is causing the phone not to boot. I can boot without magisk but there is no way now to disable the faulty module. even reflashed the modified recovery boot image and the modules are still stuck. Any idea where i can delete all the modules?

Grumps said:
So did this on my p20 and all worked well untill some module is causing the phone not to boot. I can boot without magisk but there is no way now to disable the faulty module. even reflashed the modified recovery boot image and the modules are still stuck. Any idea where i can delete all the modules?
Click to expand...
Click to collapse
Remove magisk. Then reinstall magisk. Should work.

Villa Curtricias said:
Remove magisk. Then reinstall magisk. Should work.
Click to expand...
Click to collapse
Doesnt
But i got it right
adb shell
su
then deleted the magisk.img in data\adb i think it was

How to root US OnePlus 8 Pro

1: Unlock your bootloader
2: Reboot to fastboot
3: Via fastboot on a PC, flash the attached boot IMG (fastboot flash boot "directory to boot IMG, can drag and drop")
4: Done!
Ill try to keep this img up to date but always verify the version before you flash
Current version: 10.5.4.IN11AA
https://drive.google.com/open?id=18fbWNm1ZLFA1dsJkiQJrcEn-unJA1UDQ

nima0003 said:
1: Unlock your bootloader
2: Reboot to fastboot
3: Via fastboot on a PC, flash the attached boot IMG (fastboot flash boot "directory to boot IMG, can drag and drop")
4: Done!
Ill try to keep this img up to date but always verify the version before you flash
Current version: 10.5.4.IN11AA
https://drive.google.com/open?id=18fbWNm1ZLFA1dsJkiQJrcEn-unJA1UDQ
Click to expand...
Click to collapse
Do you have update to 10.5.5.IN11AA ?

gaww said:
Do you have update to 10.5.5.IN11AA ?
Click to expand...
Click to collapse
If all you're looking for is the patched boot image, you can find it here, https://forum.xda-developers.com/oneplus-8-pro/how-to/magisk-patched-10-5-5-image-t4088333.

spotmark said:
If all you're looking for is the patched boot image, you can find it here, https://forum.xda-developers.com/oneplus-8-pro/how-to/magisk-patched-10-5-5-image-t4088333.
Click to expand...
Click to collapse
Just got the phone and it updated to .5, and late at night, .6 showed up. It installed without all the trouble with TMo 7.
It unrooted, and I used the .5 magisk patched.img above without any problems, but will use .6 when available.

Careful with the fingerprint enrollment, factory wiping with root has been known to break fingerprint. Just a heads up.
Theres a thread about this, there isn't a currently known fix either.
Has happened to EU BA devices but you never know.

dladz said:
Careful with the fingerprint enrollment, factory wiping with root has been known to break fingerprint. Just a heads up.
Theres a thread about this, there isn't a currently known fix either.
Has happened to EU BA devices but you never know.
Click to expand...
Click to collapse
Thanks. I didn't wipe and I don't use fingerprint.

gaww said:
Thanks. I didn't wipe and I don't use fingerprint.
Click to expand...
Click to collapse
Right ok, might want to check it if you ever do. Just in case

Will this work on the Verizon compatible phone?

skateguy1234 said:
Will this work on the Verizon compatible phone?
Click to expand...
Click to collapse
If you're using an unlocked 8 Pro, sure. If you're using an 8, purchased directly from Verizon, no.

skateguy1234 said:
Will this work on the Verizon compatible phone?
Click to expand...
Click to collapse
Check your pms if you want to tinker with the Verizon model with

I'm using a US 8 Pro running 10.5.10.IN11AA. Can I use this 10.5.4.IN11AA boot image, or do I need to wait for an update? Is there a newer way to install magisk?

Ecna said:
I'm using a US 8 Pro running 10.5.10.IN11AA. Can I use this 10.5.4.IN11AA boot image, or do I need to wait for an update? Is there a newer way to install magisk?
Click to expand...
Click to collapse
No - don't use old one. If you search, you should find 10.5.10 boot image.

Thanks, I couldn't find a new one so I downgraded to 5.9.

Ecna said:
Thanks, I couldn't find a new one so I downgraded to 5.9.
Click to expand...
Click to collapse
Now you can upgrade back to 5.10 and reinstall magisk before booting up the update. Works real easy.

^ @gaww
I've been able to unlock the bootloader on my Oneplus 8 Pro and am trying to locate a magisk patch compatible with 10.5.1.in11aa, yet can't locate this version. However, there's an OTA update available for my phone at takes it to 10.5.10. If I first perform that OTA update, where can I then find a compatible version of magisk?
TIA!

Deckardmac said:
^ @gaww
I've been able to unlock the bootloader on my Oneplus 8 Pro and am trying to locate a magisk patch compatible with 10.5.1.in11aa, yet can't locate this version. However, there's an OTA update available for my phone at takes it to 10.5.10. If I first perform that OTA update, where can I then find a compatible version of magisk?
TIA!
Click to expand...
Click to collapse
Don't make things complicated, update to 10.5.10, boot twrp, install magisk from the zip

^ Pardon my noobness, but does the Magisk version have to match the OxygenOS version, or can I simply use the latest Magisk version? Lots of chatter about getting the Magisk that matches.

Deckardmac said:
^ Pardon my noobness, but does the Magisk version have to match the OxygenOS version, or can I simply use the latest Magisk version? Lots of chatter about getting the Magisk that matches.
Click to expand...
Click to collapse
Use 20.4

^ Thanks guys. It worked flawlessly.

how to fix cts profile false on 10.5.10

Root Google pixel 2 xl - android 11

Hello everyone
Please can you help me to root pixel 2 xl - android 11
And is there any custom rom with android 11

We could, but it's important to note that if you have a Verizon Pixel 2 XL, root is NOT POSSIBLE.
Anyway, assuming you have the correct P2XL, the rooting instructions we give here in the forums haven't changed appreciably since they were written. For Android 11, they still apply, with the caveat that you currently have to use the "Canary" version of Magisk (i.e. the development channel version of Magisk) in order for root to work.

How about ????

abughassan said:
How about ????
Click to expand...
Click to collapse
That' indicates you have a Google variant, not a Verizon variant. So you're good to go with unlocking your bootloader, etc.
You should delete that picture as it shows your CSN number.
Guides:
https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418
https://github.com/topjohnwu/Magisk

Thanks pro
After install magisk I can't boot system .. always reboot !!!!
How can fix it

abughassan said:
Thanks pro
After install magisk I can't boot system .. always reboot !!!!
How can fix it
Click to expand...
Click to collapse
Make sure you are using Canary Magisk Manager and flashing Canary Magisk.

Thank you very much for your help brothers
It's done

abughassan said:
Thank you very much for your help brothers
It's done
Click to expand...
Click to collapse
Awesome

abughassan said:
Thanks pro
After install magisk I can't boot system .. always reboot !!!!
How can fix it
Click to expand...
Click to collapse
Lughnasadh said:
Make sure you are using Canary Magisk Manager and flashing Canary Magisk.
Click to expand...
Click to collapse
Just to point out the obvious to @abughassan, but I thought I made the point @Lughnasadh brings up clear in my previous post. You must have missed it, but it's all good as you got things working.

@Strephon Alkhalikoi
yes pro .. you are right I didn't notice it .. that's my fault thank you very much for your help

Brothes :
Is it possible to change font on P2XL11 ??

abughassan said:
Brothes :
Is it possible to change font on P2XL11 ??
Click to expand...
Click to collapse
You are rooted now mate and android is full of possibilities. Search internet you will surely find a way.

@rajkatiyar07 : Thanks mate ... I tried many ways but it didn't succeed

abughassan said:
@rajkatiyar07 : Thanks mate ... I tried many ways but it didn't succeed
Click to expand...
Click to collapse
Check in magisk thread. I am not rooted now but if i remember correctly there were plenty fonts related modules.

Just not able to root my Pixel 2 XL running Android 11
Lughnasadh said:
Make sure you are using Canary Magisk Manager and flashing Canary Magisk.
Click to expand...
Click to collapse
Brother please help me out. I've tried everything but I am just unable to root my pixel 2 xl running the latest android version (11).
I tried patching the boot image with latest canary build and it always outputs an image file which is of 0 bytes.
Then I tried patching the boot image with latest magisk manager (not canary), it was able to output a file which was around 25 MB in size but flashing it always results in boot loop.
Finally, I tried to patch my boot image using some other device with magisk canary (latest) and the output image was about 25 MB in size but again after flashing it, the device goes into boot loop.
--UPDATE--
I was finally able to root my device by simply flashing the latest magisk zip file (v 21.0) via TWRP

MridulDR said:
--UPDATE--
I was finally able to root my device by simply flashing the latest magisk zip file (v 21.0)
Click to expand...
Click to collapse
Yes, just to clarify for others reading this, topjohnwu pushed Magisk 21 to the beta channel. It should be on the stable channel shortly, so there will soon be no need to deviate from the established rooting instructions we have in the forums.

abughassan said:
Thanks pro
After install magisk I can't boot system .. always reboot !!!!
How can fix it
Click to expand...
Click to collapse
I had that happen. Unfortunately, the only solution I found was to use the online Google flash tool and flash back to the previous install. Fortunately, it worked. I updated to 11 from there. I may leave it uprooted because currently the Pixel 2 XL is a backup phone and I don't need root currently.