Develop Bugs

Magisk on Pixel / Pixel XL - does it work yet?

So I've been trying to get magisk working for a while on Pixel XL and magisk version 11 still gives the unable to mount /system error.
Anyone find a workaround yet? Not being able to use Android Pay is annoying...

wireaudio said:
So I've been trying to get magisk working for a while on Pixel XL and magisk version 11 still gives the unable to mount /system error.
Anyone find a workaround yet? Not being able to use Android Pay is annoying...
Click to expand...
Click to collapse
Hey... Check the last paragraph of this post: https://forum.xda-developers.com/showpost.php?p=71502787&postcount=17 named "What's Next"
Cheers...

I've also been curious about this but everything I've read says it's just a matter of the dev of Magisk being able to implement into how the Pixel works. Looking forward to that *hopefully* happening sometime in the future!

bravesfan171 said:
I've also been curious about this but everything I've read says it's just a matter of the dev of Magisk being able to implement into how the Pixel works. Looking forward to that *hopefully* happening sometime in the future!
Click to expand...
Click to collapse
This is the exacts developer's words. It's been posted 23 hours ago:
topjohmwu said:
For the long awaited Pixel support, I think I'll start working on it, but the complexity of that device might take a very long time for me to understand, since I do not own the device. I can only borrow my friend's device for not that long of a period of time, so progress shall be really slow. I'll not get the Pixel device now, because I don't think it is worth the price and the hassle for me to import it into Taiwan, but I'll definitely get the Pixel 2 to replace my current daily driver lol.
Click to expand...
Click to collapse

Thanks guys! Much appreciated!

wireaudio said:
Thanks guys! Much appreciated!
Click to expand...
Click to collapse
Hello... Maybe take a look at this: https://forum.xda-developers.com/showpost.php?p=71573863&postcount=1029
Cheers...

Works perfectly. March Pure Nexus w/ PN kernel. Installed the V4A module too. Mario works. Pay works. Safety net passes 100%. Use TWRP RC2 and make sure to flash TWRP again after flashing Magisk.

funkybrunk said:
Works perfectly. March Pure Nexus w/ PN kernel. Installed the V4A module too. Mario works. Pay works. Safety net passes 100%. Use TWRP RC2 and make sure to flash TWRP again after flashing Magisk.
Click to expand...
Click to collapse
I'm getting an error when installing Magisk 11.6 on the Pixel, says:
"Updater process ended with Error: 1
Error installing zip file Magisk-v11.6-Pixel.zip"
Anyone else run into this with a fix?
----------------------------------------------------
Just wiped everything, still no go.
Getting the exact same error. This seems like an error with TWRP or the zip file I'm using.
The error pops up during the "Unpacking boot image" stage.

You need to used TWRP RC2. Your errors are because you are on RC1

funkybrunk said:
You need to used TWRP RC2. Your errors are because you are on RC1
Click to expand...
Click to collapse
So I'm using PN with EX kernel. Does magisk work with EX? Just flash the rc 2 zip while on RC 1?

318sugarhill said:
So I'm using PN with EX kernel. Does magisk work with EX? Just flash the rc 2 zip while on RC 1?
Click to expand...
Click to collapse
Yes it works on PN, and yes it will work with EX but EX doesn't give you the same options in aroma (as SuperSU) because it isn't recognizing magisk root.

pcriz said:
Yes it works on PN, and yes it will work with EX but EX doesn't give you the same options in aroma (as SuperSU) because it isn't recognizing magisk root.
Click to expand...
Click to collapse
Ok thanks. Will flashing the PN Rom switch the kernel back. or will I have to flash that manually

318sugarhill said:
Ok thanks. Will flashing the PN Rom switch the kernel back. or will I have to flash that manually
Click to expand...
Click to collapse
PN has its own kernel so I am assuming yes it will.

pcriz said:
PN has its own kernel so I am assuming yes it will.
Click to expand...
Click to collapse
Ok. Hopefully dirty flashing will just reset the kernel

318sugarhill said:
Ok. Hopefully dirty flashing will just reset the kernel
Click to expand...
Click to collapse
I should've been more definitive in my answer. Yes it will replace the kernel when you flash the rom, my bad.

I was using pure Nexus with Ex kernel....I flashed PN Rom (dirty flash) just to reset kernel....Flashed TWRP RC1 zip zip....Reboot system, then reboot recovery and flashed TWRP RC2 zip, reboot system, reboot to recovery flashed Magisk then reboot system again. Reboot to recovery flashed vendor img for PN and all is good. Enabled magisk hide in magisk app settings.....Then under magisk hide I hid it from DirecTV Now app. All safety net tests pass. Needed a build prop edit for directTV now to work correctly but all other apps blocked because of root are now working.
Thanks for the assistance

Does magisk work on 7.1.2?
Sent from my Pixel XL using Tapatalk

bb12489 said:
Does magisk work on 7.1.2?
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
Working fine for me with Latest ElementalX Kernel

liam_davenport said:
Working fine for me with Latest ElementalX Kernel
Click to expand...
Click to collapse
Good deal. What do you think would be the best way to update to 7.1.2? I have TWRP recovery and elementalX at the moment. Should I flash stock boot.img, then update? I Imagine I would have to flash magisk again though.
Sent from my Pixel XL using Tapatalk

has anyone gotten any of the modules to work ?

root with Magisk on Oreo.

I was trying to get help on Reddit but I wasn't able to get any help.
I was able to find the Twrp image to Boot into but Magisk isn't installing when I go to try to install it.
I'm using 13.4 for my pixel XL and I tried 13.3
Any ideas why they aren't working? No errors in Twrp when installing.

DudeThatsErin said:
I was trying to get help on Reddit but I wasn't able to get any help.
I was able to find the Twrp image to Boot into but Magisk isn't installing when I go to try to install it.
I'm using 13.4 for my pixel XL and I tried 13.3
Any ideas why they aren't working? No errors in Twrp when installing.
Click to expand...
Click to collapse
Hello,
Not sure if Magisk is even working on O but you would want to flash a kernel like ElementalX first or the modified stock. Flash the kernel, then Magisk but again I am not sure if it is actually working yet. If you do get it installed and working be sure to report back to all. Also if you had SU + SUhide prior then you will want to flash the Magisk remover first, then kernel then Magisk.
Cheers

jschill31 said:
Hello,
Not sure if Magisk is even working on O but you would want to flash a kernel like ElementalX first or the modified stock. Flash the kernel, then Magisk but again I am not sure if it is actually working yet. If you do get it installed and working be sure to report back to all. Also if you had SU + SUhide prior then you will want to flash the Magisk remover first, then kernel then Magisk.
Cheers
Click to expand...
Click to collapse
Yup. Just verified it doesn't work. I booted into twrp, installed ElementalX, then Magisk 13.4 and rebooted, still doesn't work.
Then I booted into twrp, installed ElementalX and Magisk 13.3 and rebooted. Nothing.
I also installed TWRP RC2 and it works fine. If you want I can upload the bootable image for twrp and RC2 that I used. At least now I have a way of testing it out (well, to keep testing it out, when I'm at work).

DudeThatsErin said:
Yup. Just verified it doesn't work. I booted into twrp, installed ElementalX, then Magisk 13.4 and rebooted, still doesn't work.
Then I booted into twrp, installed ElementalX and Magisk 13.3 and rebooted. Nothing.
I also installed TWRP RC2 and it works fine. If you want I can upload the bootable image for twrp and RC2 that I used. At least now I have a way of testing it out (well, to keep testing it out, when I'm at work).
Click to expand...
Click to collapse
So you have twrp installed with no issues?

humdrum2009 said:
So you have twrp installed with no issues?
Click to expand...
Click to collapse
Correct

I'm using a 6p with a pixel on the way. I had it working on the 6p with Oreo. I'm pretty sure I had to download an apk as well as flash the zip. Have you done this?

the pixel has a special magisk version because of boot a/b system stuff from my understanding. So it doesn't matter if it works on any other google phone.
It sucks too because i heavily rely on magisk due to how good it is on hiding...goodwin_c is my only hope. hanging on a thread here...
If you mention other root hiding methods just know that no...they all suck lol

j_mullet said:
I'm using a 6p with a pixel on the way. I had it working on the 6p with Oreo. I'm pretty sure I had to download an apk as well as flash the zip. Have you done this?
Click to expand...
Click to collapse
Zizzy2020 said:
the pixel has a special magisk version because of boot a/b system stuff from my understanding. So it doesn't matter if it works on any other google phone.
It sucks too because i heavily rely on magisk due to how good it is on hiding...goodwin_c is my only hope. hanging on a thread here...
If you mention other root hiding methods just know that no...they all suck lol
Click to expand...
Click to collapse
What Zizzy2020 said. It is annoying. I can't wait for the next magisk to be released.

Check out this post, it works like a charm.

Where can i find a version of busybox that will work?

i installed busybox from the playstore and it doesnt seem to want to install. I'm currently on twrp 3.2.1, magisk 15 and magisk manager 15.

equlizer said:
i installed busybox from the playstore and it doesnt seem to want to install. I'm currently on twrp 3.2.1, magisk 15 and magisk manager 15.
Click to expand...
Click to collapse
Use the Magisk Module Busy Box for Android NDK. Works great.

felosisman said:
Use the Magisk Module Busy Box for Android NDK. Works great.
Click to expand...
Click to collapse
Where do i find it? thx
EDIT: NVM flashed it in magisk. Is it still normal to get the "theres an internal problem........"?

equlizer said:
Where do i find it? thx
Click to expand...
Click to collapse
Open Magisk Manager, go-to Downloads, find and download "BusyBox for Android NDK 1.27.2", reboot and profit.

Noob question but what is BusyBox and what's it's purpose

mackentosh said:
Noob question but what is BusyBox and what's it's purpose
Click to expand...
Click to collapse
Busybox allows programs to perform actions on your phone using Linux commands. So some apps require it to run some commands and wont work without it.

equlizer said:
Where do i find it? thx
EDIT: NVM flashed it in magisk. Is it still normal to get the "theres an internal problem........"?
Click to expand...
Click to collapse
You shouldn't be getting that error anymore if you're using the latest Magisk release. He released version 15.0(1500) a couple days ago, but that was actually fixed in the last beta 14.6.
You would have to reflash your Kernel boot and dtbo and repatch though with the new version. I just used the Magisk Uninstaller script in TWRP, flashed the latest zip of flash Kernel then latest Magisk in TWRP and all good.

Riru Core EdXposed Magisk

You got Magisk installed on the stock Android 9 ROM? Awesome! But wait, there is more! ?
This thread is meant for the exchange of everyone's experience with Riru and Xposed modules running with EdXposed.
The installation is pretty simple: 1) In Magisk, install "Riru - Core", reboot, 2) install "Riru - EdXposed" (SandHook), reboot, 3) install "EdXposed Manager" (github.com/ElderDrivers/EdXposedManager/releases).
Once everything is set up, install Xposed modules like crazy ... and prepare yourself for a hell of crashes and boot halts ?. Since we do not have TWRP with data decryption yet, you have to be prepared for those boot halts. Therefore, install only one Xposed module at a time, reboot and check if everything is working. If Android does not boot, you can fix your phone using two methods:
Recovering from a boot halt - Method 1
The most obvious way to get around a boot hang is to 1) flash the original boot.img, 2) boot into the UI and uninstall the Xposed module causing the boot halt, and 3) flash "magisk_patched.img" and re-install Magisk from within the Magisk Manager ("Direct install"). SU might stop working if you forget to re-install Magisk (not the Magisk Manager).
The only possible downside is that Magisk and Xposed modules, like XPrivacyLUA, will be inactive during step 2). However, potential privacy/usability issues are less painful than not being able too boot up Android ?.
Recovering from a boot halt - Method 2
If you do not want to disable Magisk and Xposed, flashing the "magisk_patched.img" may make Android boot into the UI ... and give you 10 to 20 seconds before crashing. As a precaution, before you install Xposed modules, 1) remove PIN/password log-on and 2) place a shortcut to the EdXposed Manager and Magisk Manager onto a convenient spot on your desktop. For both managers, you can place a link directly to the Modules tab (at least with Nova launcher).
If things go well, you have 10 to 20 seconds to open the EdXposed Manager and disable the module causing the boot process to fail. If the boot process gets stuck again, even though you flashed "magisk_patched.img", you might succeed by flashing the "magisk_patched.img" several times before rebooting. Even removing the SIM or SD-card may make Android boot up.
If/when you succeed to disable the Xposed module that blocks the boot process, you have to re-install Magisk from within the Magisk Manager ("Direct install"). Otherwise, SU might stop working for you.
Here are Xposed modules that prevent your Pro1 from booting into Pie:
MyAndroidToolsXposed (surely)
DisableFlagSecure (probably)
Screenshot Delay Remover - Mod (probably)
Working fine are:
GravityBox
XPrivacyLUA
AFWall+
Scoop
App Locale 2
InstallerOpt (doesn't crash but doesn't seem to work either)
FakeGApps

I want to install Xposed mainly for MinMinGuard to get ride of these empty ads areas, is this module working fine?
OP 7 Pro Magisk

Sorry for the late reply...
So far, either no one ever tried to run MinMinGuard on the Pro1, or no one ever gave feedback

The riru core update 21.3 seems to remove the play services on my gt-n7000 with lineageos 16 and opengapps pico.

Is this thread for Lineage OS only?
Sorry to post here... but to answer your question, no I do not have Magisk installed. lol. As far as I know, TWRP is for Sailfish only. Also, I can't locate the F(X) Tec Pro 1 Boot image anywhere. Build= QX1000_EEA20200825231443.
Kindly, if you installed Magisk using the F(X) Tec Pro 1 boot image and the Magisk "Select And Patch A File" option... Please tell me where you located the boot image?

Antinee said:
Is this thread for Lineage OS only?
Sorry to post here... but to answer your question, no I do not have Magisk installed. lol. As far as I know, TWRP is for Sailfish only. Also, I can't locate the F(X) Tec Pro 1 Boot image anywhere. Build= QX1000_EEA20200825231443.
Kindly, if you installed Magisk using the F(X) Tec Pro 1 boot image and the Magisk "Select And Patch A File" option... Please tell me where you located the boot image?
Click to expand...
Click to collapse
You can install the Magisk zip via LineageOS recovery

Antinee said:
Is this thread for Lineage OS only?
Click to expand...
Click to collapse
No, this thread is for the stock ROM only
I changed the first posting accordingly.
On LOS, Magisk, Riru and all Xposed modules (that I have installed) work without any problems.
Since I switched to LOS, I won't/can't update the list of working Xposed modules for the stock ROM any more.

im on a moto g power. stock. installed riru. but when i try to install edxposed it fails and tells me i need install riru-core first. just doesnt seem to recognize riru for some reason.

cnoevl21 said:
im on a moto g power. stock. installed riru. but when i try to install edxposed it fails and tells me i need install riru-core first. just doesnt seem to recognize riru for some reason.
Click to expand...
Click to collapse
This is about the Fxtec Pro1. Anyway, that's because Riru is v22 or newer. EdXposes currently needs an older riru

Hi,
I've installed Magisk 20.4 and Manager 8.0.3 on my lineage os 17.1 (samsung SM-520F) and I'm trying to install Riru Core EdXposed Magisk.
But I can't find any riru-core module Manager: Riru, Riru-EdXposed (Sandhook or YAHFA) but no Riru-core ...
So I've installed Riru, but when I try to install Riru-EdXposed, magisk complains about Riru-core missing.
Where can I find Riru-core ?
Thanks

peperu said:
Hi,
I've installed Magisk 20.4 and Manager 8.0.3 on my lineage os 17.1 (samsung SM-520F) and I'm trying to install Riru Core EdXposed Magisk.
But I can't find any riru-core module Manager: Riru, Riru-EdXposed (Sandhook or YAHFA) but no Riru-core ...
So I've installed Riru, but when I try to install Riru-EdXposed, magisk complains about Riru-core missing.
Where can I find Riru-core ?
Thanks
Click to expand...
Click to collapse
https://github.com/RikkaApps/Riru/releases
But im in the same boat as you. Im not sure how far back we need to go to get a riru version that works with edxposed. nor do i know how to install it, since it wont be in magisk manager.

peperu said:
Hi,
I've installed Magisk 20.4 and Manager 8.0.3 on my lineage os 17.1 (samsung SM-520F) and I'm trying to install Riru Core EdXposed Magisk.
But I can't find any riru-core module Manager: Riru, Riru-EdXposed (Sandhook or YAHFA) but no Riru-core ...
So I've installed Riru, but when I try to install Riru-EdXposed, magisk complains about Riru-core missing.
Where can I find Riru-core ?
Thanks
Click to expand...
Click to collapse
1. Riru Core has been renamed to Riru
2. you need to use Version 21
---------- Post added at 10:14 PM ---------- Previous post was at 10:12 PM ----------
cnoevl21 said:
https://github.com/RikkaApps/Riru/releases
But im in the same boat as you. Im not sure how far back we need to go to get a riru version that works with edxposed. nor do i know how to install it, since it wont be in magisk manager.
Click to expand...
Click to collapse
Version 21 of Riru at that link. You can install it via the flash from storage button in the download modules page
EDIT: Direct link to the correct ZIP: https://github.com/RikkaApps/Riru/releases/download/v21.3/magisk-riru-v21.3.zip

nift4 said:
1. Riru Core has been renamed to Riru
2. you need to use Version 21
---------- Post added at 10:14 PM ---------- Previous post was at 10:12 PM ----------
Version 21 of Riru at that link. You can install it via the flash from storage button in the download modules page
EDIT: Direct link to the correct ZIP: https://github.com/RikkaApps/Riru/releases/download/v21.3/magisk-riru-v21.3.zip
Click to expand...
Click to collapse
Thank you. i did get it to work. but now the phone doesnt pass safetynet. Looks like canary fixes this, but it says its not stable. so i worry installing it would brick the phone.
Maybe i just need to get over having back button kill and double tapping recent for screenshot lol

cnoevl21 said:
Thank you. i did get it to work. but now the phone doesnt pass safetynet. Looks like canary fixes this, but it says its not stable. so i worry installing it would brick the phone.
Maybe i just need to get over having back button kill and double tapping recent for screenshot lol
Click to expand...
Click to collapse
Did you enable Pass SafetyNet in EdXposed settings

nift4 said:
Did you enable Pass SafetyNet in EdXposed settings
Click to expand...
Click to collapse
I did. still fails

cnoevl21 said:
I did. still fails
Click to expand...
Click to collapse
If App List mode is enabled, I can't help you

Hi,
Riru 23.1 (Magisk module) ignores the screen timeout. This makes battery drained. This should be resolved.
I use it on my Redmi Note 8 Pro (Android 10).
Does any one a fix or advice for that?
Thank you!

Rezazahmad01 said:
Hi,
Riru 23.1 (Magisk module) ignores the screen timeout. This makes battery drained. This should be resolved.
I use it on my Redmi Note 8 Pro (Android 10).
Does any one a fix or advice for that?
Thank you!
Click to expand...
Click to collapse
I just checked i have 23.2 installed not sure if the same issue is here

For some time, the riru core continues to have a very horrible bug for Samsung devices with Snapdragon, it is that once installed it affects the installation of apks and applications from the play store and also in the uninstallation of applications the "installer of packages stays frozen and does not advance "is a very random and very annoying error and you have to restart the device and sometimes it does not work. That's why I ask you to correct that error. It was tested on a S9 + g9600 and a note 9 N9600 both with a Snapdragon processor and latest riru core 25.4.2.

daniel_m said:
No, this thread is for the stock ROM only
I changed the first posting accordingly.
On LOS, Magisk, Riru and all Xposed modules (that I have installed) work without any problems.
Since I switched to LOS, I won't/can't update the list of working Xposed modules for the stock ROM any more.
Click to expand...
Click to collapse
Working also on Lineage 18.1?
I become an error Riru Core not found in memory

Oxygen OS 10.0.11HD65AA

Hey i share new update for op7t global.

I have not signal after the upgrade this are the specs that I followed
1 downloaded and installed from local upgrade
2 before reboot open magisk and install masgisk in the inactive partition
3 reboot and after my device first boot I got no signal and also the settings were kind of buggy, so I reboot like 3 times and everything is okey except for the missing signal

akuma48465 said:
I have not signal after the upgrade this are the specs that I followed
1 downloaded and installed from local upgrade
2 before reboot open magisk and install masgisk in the inactive partition
3 reboot and after my device first boot I got no signal and also the settings were kind of buggy, so I reboot like 3 times and everything is okey except for the missing signal
Click to expand...
Click to collapse
I use Oneplus 7T without root and everything is fine with the update. I have been using the update for a couple of hours and until now it seems that the heating that sometimes occurred with the battery was corrected.

akuma48465 said:
I have not signal after the upgrade this are the specs that I followed
1 downloaded and installed from local upgrade
2 before reboot open magisk and install masgisk in the inactive partition
3 reboot and after my device first boot I got no signal and also the settings were kind of buggy, so I reboot like 3 times and everything is okey except for the missing signal
Click to expand...
Click to collapse
What channel did you pull it from?
Sent from my HD1907 using Tapatalk

Hello guys, I also received the update via an external program to request updates, not through my device, and I am surprised that my device is slow to show updates, but I have a problem with the root file (OOS 10.0.9 magisk_patched.img) will it succeed this time because it no longer works for me after the last update I hope you answer my problem and thank you to everyone

Silly question, can an EU version of the phone (living in the UK) be transferred to the global ROM without losing functionality?

maddoguk said:
Silly question, can an EU version of the phone (living in the UK) be transferred to the global ROM without losing functionality?
Click to expand...
Click to collapse
Yes

Kollachi said:
Yes
Click to expand...
Click to collapse
Just straight forward flashing over the current ROM?

Karl said:
What channel did you pull it from?
Sent from my HD1907 using Tapatalk
Click to expand...
Click to collapse
Official update (stable) through settings

Use Canary
Sent from my HD1907 using Tapatalk

akuma48465 said:
I have not signal after the upgrade this are the specs that I followed
1 downloaded and installed from local upgrade
2 before reboot open magisk and install masgisk in the inactive partition
3 reboot and after my device first boot I got no signal and also the settings were kind of buggy, so I reboot like 3 times and everything is okey except for the missing signal
Click to expand...
Click to collapse
after apply the update once again without install magisk in the inactive partition I got my signal bars again, Im wating for the patched boot.img file of this oxygen os version to try to boot and directly install magisk

akuma48465 said:
after apply the update once again without install magisk in the inactive partition I got my signal bars again, Im wating for the patched boot.img file of this oxygen os version to try to boot and directly install magisk
Click to expand...
Click to collapse
were you have call recording module Installed ?

Snake.s9 said:
were you have call recording module Installed ?
Click to expand...
Click to collapse
yes
---------- Post added at 09:47 AM ---------- Previous post was at 09:17 AM ----------
Snake.s9 said:
were you have call recording module Installed ?
Click to expand...
Click to collapse
Now I understand Why ask that question
First I got the the magisk boot img of OS 10.0.11HD65AA and boot the file
I got root but without signal, also I update magisk to the canary channel
after turning of the call recorder module I got signal bars again thanks

I downloaded the update from the oxygen updater and installed locally, then after reading here I uninstalled the Recording module (because I had no signal) but I'm getting error when trying to access Settings (stop stopped working) I'm downloading the update file from here and reinstall it, any more guesses?
Thanks

I upgraded my wife's OnePlus 7T last night through the regular process right on the phone.
1. The phone has automatic system updates disabled through developer options.
2. Go to Magisk Manager click uninstall, select restore images, and do not reboot.
3. Go to settings on device, select system, system updates, let it update, do not reboot.
4. Got to Magisk Manager, select install next to Magisk, select install, install to Inactive Slot (after OTA), and now reboot phone.
It took a minute or so to reboot. The device booted up and everything works great, no issues at all. The only issue I have, my phone another 7T does not have the upgrade available.
Update: Forgot to mention, I am using regular Magisk 20.4 (20400) with Magisk Manager 7.5.1 (267).

agtsoul said:
I upgraded my wife's OnePlus 7T last night through the regular process right on the phone.
1. The phone has automatic system updates disabled through developer options.
2. Go to Magisk Manager click uninstall, select restore images, and do not reboot.
3. Go to settings on device, select system, system updates, let it update, do not reboot.
4. Got to Magisk Manager, select install next to Magisk, select install, install to Inactive Slot (after OTA), and now reboot phone.
It took a minute or so to reboot. The device booted up and everything works great, no issues at all. The only issue I have, my phone another 7T does not have the upgrade available.
Update: Forgot to mention, I am using regular Magisk 20.4 (20400) with Magisk Manager 7.5.1 (267).
Click to expand...
Click to collapse
Hi.
Can you explain step 2 in more detail? Is this step necessary? I have 10.0.9 rooted with Magisk 20.4 and several Magisk modules including Renovate Ice. Does step 2 delete all modules? Do I need to uninstall them manually before step 3? I read Renovate Ice hasn't been updated yet to be compatible with 10.0.11 yet.

Starzboy77 said:
Hi.
Can you explain step 2 in more detail? Is this step necessary? I have 10.0.9 rooted with Magisk 20.4 and several Magisk modules including Renovate Ice. Does step 2 delete all modules? Do I need to uninstall them manually before step 3? I read Renovate Ice hasn't been updated yet to be compatible with 10.0.11 yet.
Click to expand...
Click to collapse
From my understanding, step 2 just restores the patched boot image to the regular boot image. However, you still have root access because you have not rebooted yet. I did not delete or disable any modules on my wife's phone. She is only running systemless host for AdAway. I still have not received the update on my phone. But, the only modules I run on it are sytemless host and YouTube Vanced black themed v14.21.54.

Do you have new clocks in settings->lockscreen?

akuma48465 said:
after apply the update once again without install magisk in the inactive partition I got my signal bars again, Im wating for the patched boot.img file of this oxygen os version to try to boot and directly install magisk
Click to expand...
Click to collapse
I recently also got the 10.0.11 OTA update on the Global variant. While it was downloading and installing, a snuck a copy of it off the phone and extracted the image files from it.
the unpatched and Magisk Patch bootimage can be found here: Google Drive OnePlus 7T HD65AA Global v10.0.11
Note, this one was patched using the latest (at the time) canary build of Magisk (cd6eca1d) 20415.
Cyberstorm

arindam112 said:
Do you have new clocks in settings->lockscreen?
Click to expand...
Click to collapse
I don't see any new clocks.