Database Info

[stupid question] OTA update when on magisk and xposed?

Hello XDA!
It's been a while since I did 'modding' on phones, I think I started with the OP1 back in 2014 but have not really been keeping up ever since. I am now on 5.1.5 and running official OOS with magisk and xposed for gravitybox.. Can I just disable magisk and xposed, do the OTA update and then re-enable or do I have to uninstall them fully? Or can I just do the OTA right now?
Sorry for what might be a really obvious answer.
Thank you!

You can do the OTA but if you want magisk (and then xposed systemless) i suggest you to install TWRP after update and you need in all cases to re-do root process

Hitman478™ said:
You can do the OTA but if you want magisk (and then xposed systemless) i suggest you to install TWRP after update and you need in all cases to re-do root process
Click to expand...
Click to collapse
Ahh I see. Because xposed is now systemless it doesn't matter if I leave it enabled right? Is the new official TWRP without any dangerous bugs?
Thanks for your swift reply!!

maybe to help you all
me: 5.1.5, unlocked bootloader, unofficial TWRP from thread by wuxianlin, magisk 16.4
my procedure was to change to official twrp which can be done easily by
downloading the twrp installer from official site, put to internal storage
flash twrp official installer
still in recovery, select reboot: recovery
flash magisk
boot system
now download full 5.1.6 signed flashable zip
recovery: flash 5.1.6
reflash recovery
reboot recovery
flash magisk
boot system
now you have rooted 5.1.6 with official twrp and magisk, no wipe needed

oneplus6 ha a/b partition. so if you installed magisk 16.4 already. just OTA. when it's done don't reboot yet. enter magisk manager, choose install on the second partition. reboot.

trivita said:
oneplus6 ha a/b partition. so if you installed magisk 16.4 already. just OTA. when it's done don't reboot yet. enter magisk manager, choose install on the second partition. reboot.
Click to expand...
Click to collapse
This will useful only if don't have TWRP, in other case you'll lose twrp in this way
---------- Post added at 15:21 ---------- Previous post was at 15:19 ----------
TheHighLife said:
Ahh I see. Because xposed is now systemless it doesn't matter if I leave it enabled right? Is the new official TWRP without any dangerous bugs?
Thanks for your swift reply!!
Click to expand...
Click to collapse
TWRP official has no bug, the only thing i don't know is if backup/restore is working fine, if you install ota via TWRP and then flash (without reboot) twrp.zip and magisk, after reboot you'll find out that system is exactly the same it was before updating

The only thing u need to disable before updates are overlays through substratum, I also remove any security like finger prints, face unlock and pin or patterns too just in case. Once u flash update u will have to reflash magisk and xposed too

trivita said:
oneplus6 ha a/b partition. so if you installed magisk 16.4 already. just OTA. when it's done don't reboot yet. enter magisk manager, choose install on the second partition. reboot.
Click to expand...
Click to collapse
Did anyone try this?

defsix said:
Did anyone try this?
Click to expand...
Click to collapse
i did this myself
idontcare abt the twrp at all
im perfectly fine with stock recovery

trivita said:
i did this myself
idontcare abt the twrp at all
im perfectly fine with stock recovery
Click to expand...
Click to collapse
Same as that. I'll give it a try next update.
Sent from my Brain using my Keyboard

How do you install to second partition? I only get install or uninstall Magisk (16.70) on the screen. i AM NEW TO MAGISK.

SafetyNet Check in magisk failing

I have a rooted OP6 on 5.1.9. An app I want to use (blind) can somehow detect the fact that I'm rooted and won't let me use the app despite root being hidden from it in Magisk Hide. Upon investigating, I discovered my SafetyNet check in Magisk is failing.
It worked when I originally rooted it a few days ago. I do not have custom recovery or xposed.
Any ideas why safetynet check could be failing or how to go about troubleshooting it?

quantumcity said:
I have a rooted OP6 on 5.1.9. An app I want to use (blind) can somehow detect the fact that I'm rooted and won't let me use the app despite root being hidden from it in Magisk Hide. Upon investigating, I discovered my SafetyNet check in Magisk is failing.
It worked when I originally rooted it a few days ago. I do not have custom recovery or xposed.
Any ideas why safetynet check could be failing or how to go about troubleshooting it?
Click to expand...
Click to collapse
I had the same problem I uninstalled Xposed framework rebooted now the the safetynet check is Ok

airdi1 said:
I had the same problem I uninstalled Xposed framework rebooted now the the safetynet check is Ok
Click to expand...
Click to collapse
As I mentioned in the post, I do not have Xposed framework

quantumcity said:
I have a rooted OP6 on 5.1.9. An app I want to use (blind) can somehow detect the fact that I'm rooted and won't let me use the app despite root being hidden from it in Magisk Hide. Upon investigating, I discovered my SafetyNet check in Magisk is failing.
It worked when I originally rooted it a few days ago. I do not have custom recovery or xposed.
Any ideas why safetynet check could be failing or how to go about troubleshooting it?
Click to expand...
Click to collapse
What version of Magisk did you flash? Flash Magisk 16.4 only. Older versions don't support the OnePlus 6 and flashing newer versions has caused many weird problems. Flash Magisk uninstaller, reboot to TWRP, then flash Magisk 16.4. Once it gets going it will tell you that it can update the Magisk version. Let it update that way. Flashing newer versions causes many weird problems bit letting it update always seems to work.

run the uninstaller magisk .zip then check if safety net passed, might be something unrelated?
im on 5.1.9 with SN passing with TWRP and Magisk

tabletalker7 said:
What version of Magisk did you flash? Flash Magisk 16.4 only. Older versions don't support the OnePlus 6 and flashing newer versions has caused many weird problems. Flash Magisk uninstaller, reboot to TWRP, then flash Magisk 16.4. Once it gets going it will tell you that it can update the Magisk version. Let it update that way. Flashing newer versions causes many weird problems bit letting it update always seems to work.
Click to expand...
Click to collapse
I have magisk 16.7

virtyx said:
run the uninstaller magisk .zip then check if safety net passed, might be something unrelated?
im on 5.1.9 with SN passing with TWRP and Magisk
Click to expand...
Click to collapse
How do I do that? Do you have a link to this zip?

quantumcity said:
I have magisk 16.7
Click to expand...
Click to collapse
Google "Magisk uninstaller". Flash that file in TWRP. Then reboot to recovery. Then flash Magisk 16.4

quantumcity said:
How do I do that? Do you have a link to this zip?
Click to expand...
Click to collapse
its in the magisk official thread.

virtyx said:
its in the magisk official thread.
Click to expand...
Click to collapse
Yes

So for me, the safety net check passes in the Magisk app but I am not able to access Google tez which tells me that my device is rooted or custom ROM has been changed. Using Magisk v 16.0

16.4... notice the 4

Just fyi I'm on 5.19 and using Magisk 16.0 and safety net passes just fine. Use Google pay daily and play store shows certified.
I hide everything Google related in magisk hide just to be sure

Eric214 said:
16.4... notice the 4
Click to expand...
Click to collapse
I know. What I meant is safety net passes everywhere except for Google Tez app. Don't know why!

I have attached the screenshots below. And I understand that I'm using Magisk 16.0

skr975 said:
I know. What I meant is safety net passes everywhere except for Google Tez app. Don't know why!
Click to expand...
Click to collapse
Do you have it hidden in Magisk? Google Pay works here if you hide it.

Okay, so I have uninstalled magisk, don't have root, and I still can't use google pay, install netflix, use my bank's app, etc.
No root, no magisk, no xposed, no custom recovery.
How can I figure out why all these apps won't work?

quantumcity said:
Okay, so I have uninstalled magisk, don't have root, and I still can't use google pay, install netflix, use my bank's app, etc.
No root, no magisk, no xposed, no custom recovery.
How can I figure out why all these apps won't work?
Click to expand...
Click to collapse
In playstore / settings are you uncertified? After unlocking bootloader I was and couldn't use Google pay. I flashed magisk and it was still uncertified so I cleared playstore app data. Now the phone says certified and Google pay works for me.
I suggest you flash 16.4 magisk and clear app data in playstore to see if you can get them working. Also you will need a different app than magisk manager to check safety net ATM as it will come back with "invalid response"
Sent from my OnePlus6 using XDA Labs

Stock Android 11

Just Posted
https://developers.google.com/android/images#sunfish

fronto said:
Just Posted
https://developers.google.com/android/images#sunfish
Click to expand...
Click to collapse
I just checked my 4a with the Check for Updates button under settings and Android 11 is there waiting for me to d/l and install.

I successfully applied the OTA update, then extracted the boot.img from the full image (both versions matching RP1A.200720.011), patched with Magisk, and then flashed it, but now phone wont boot. Just getting the G startup logo for over 10 min now. Has anyone had success with this method? Is there a better way to do it?

Just updated with no issues, but I'm not rooted yet. Only thing I really want is custom accent color (red), so not sure if it's worth rooting.
Sent from my Pixel 4a using XDA Labs

hate to say it but I think at this point that Magisk 20.4 (Manager 7.5.1) cannot root Android 11 on this phone. I have posted this finding on the rooting thread asking if anyone has had success:
https://forum.xda-developers.com/pixel-4a/how-to/guide-unlock-root-pixel-4a-t4153773/page4

I unrooted, applied update, installed Magisk Canary build, patched boot image from downloaded Factory Image, fastboot flash boot... and have successfully rooted my 4a on w/11.

Well I got an email from Google saying that android 11 was waiting for me to download. So I checked updates and it says my device is up to date. So I guess maybe verizon does hold up updates.

moeava said:
I unrooted, applied update, installed Magisk Canary build, patched boot image from downloaded Factory Image, fastboot flash boot... and have successfully rooted my 4a on w/11.
Click to expand...
Click to collapse
where did you find it? nvrmnd https://github.com/topjohnwu/magisk_files/tree/canary

@tcat007 @fronto
For anyone looking to root, you need magisk canary, latest build at time of writing (20424) works fine for me. Took the OTA from 10 to 11 following the magisk OTA update guide here worked like a charm: https://topjohnwu.github.io/Magisk/ota.html
However, somethings seemed to have changed in 11. For audio apps like jdsp and v4a, you'll need to run this in terminal (only needs done once):
Code:
su -c settings put global hidden_api_policy 1
Also note that sbin is gone too (least on pixel 4a) so v4a app install won't work properly (it's being worked on)

fronto said:
I successfully applied the OTA update, then extracted the boot.img from the full image (both versions matching RP1A.200720.011), patched with Magisk, and then flashed it, but now phone wont boot. Just getting the G startup logo for over 10 min now. Has anyone had success with this method? Is there a better way to do it?
Click to expand...
Click to collapse
You need to use latest canary
Stable doesn't yet support 11 afaik

tthalheim said:
You need to use latest canary
Stable doesn't yet support 11 afaik
Click to expand...
Click to collapse
You only need Canary to create the patched boot file. After it's been flashed, you can run Stable.
Just flash the pre-patched boot file and keep stable:
magisk_patched_sunfish-rp1a.200720.011.img

Yeah I dont like that canary Magisk so I used your advice and flashed the patched boot.img and then went back to stable Magisk. I am a little underwhelmed with Android 11 maybe its just me.
fronto said:
You only need Canary to create the patched boot file. After it's been flashed, you can run Stable.
Just flash the pre-patched boot file and keep stable:
magisk_patched_sunfish-rp1a.200720.011.img
Click to expand...
Click to collapse

good deal...yeah I figured with the pre-patched boot.img, a lot of people could avoid messing with canary alltogether and just keep normal stable.
Agreed 11 does not seem all that revolutionary. ...but all is working well now with no complaints

Archangel said:
Yeah I dont like that canary Magisk so I used your advice and flashed the patched boot.img and then went back to stable Magisk. I am a little underwhelmed with Android 11 maybe its just me.
Click to expand...
Click to collapse
If you’re running boot imaged patched with magisk canary then your running magisk canary
Sent from my iPad using Tapatalk

Yeah brother all I was saying is that I dont like the canary design for Magisk Manager so I went back to stable for manager only.
jrkruse said:
If you’re running boot imaged patched with magisk canary then your running magisk canary
Sent from my iPad using Tapatalk
Click to expand...
Click to collapse

Archangel said:
Yeah brother all I was saying is that I dont like the canary design for Magisk Manager so I wet went back to stable for manager only.
Click to expand...
Click to collapse
Oh ok
Sent from my iPhone using Tapatalk

fronto said:
You only need Canary to create the patched boot file. After it's been flashed, you can run Stable.
Just flash the pre-patched boot file and keep stable:
magisk_patched_sunfish-rp1a.200720.011.img
Click to expand...
Click to collapse
Thank you for the upload. Can this be flashed in magisk? I presume no.
Can you clarify the steps? I'm already on android 10 rooted.
1. Uninstall magisk / Restore image
2.. Download install Android 11 / no reboot
3..... ? Then with patched boot.
Thank you

mustbevick said:
Thank you for the upload. Can this be flashed in magisk? I presume no.
Can you clarify the steps? I'm already on android 10 rooted.
1. Uninstall magisk / Restore image
2.. Download install Android 11 / no reboot
3..... ? Then with patched boot.
Thank you
Click to expand...
Click to collapse
Its not flashed in Magisk. Its flashed using fastboot via a computer connection. With that file, you never need to touch Canary manager.
1. uninstall Magisk but you keep Magisk Manager
2. update to Android 11 via OTA or with full image provided you revise the flash-all to not wipe, or just manually issue each command.
3. make sure your 11 is up and running
4. reboot to bootloader, connect PC
5. fastboot flash boot magisk_patched_sunfish-rp1a.200720.011.img
6. reboot and open regular stable Magisk Manager
enjoy

I've rooted my 4a with magisk with the Aug factory image (android 10). I have the both Titanium Pro and Mybackup Pro - Do either of those programs create an image backup similar to the image I create of my PC using a program like Acronis, so that I could just re-install the Android 10 system if I don't like Android 11? If those programs don't do that is there any program that will do that?

Has anyone else noticed x google enrollment then updating message every (re) boot? I must have done something wrong. I got magisk working nicely. Can install itself, modules, ctsProfile is true, whatevs... But nothing else gets a su toast. Not too worried with it this first week or so.. I'll stab again weekend after next.
Sent from my Pixel 4a using Tapatalk

How to Root OnePlus 8T Build 11.0.6.8.KB05AA

I previously had Magisk installed and rooted my 8T with Build 11.6.5.KB05AA. I followed some instructions on how to install an OTA update. I uninstalled Magisk and ran the OTA update. The instructions advise me to install Magisk on the inactive slot. However, I do not have this option. Instead, I only have Preserve AVB 2.0/dm-verify and Recovery Mode. I don't have TWRP installed so I don't think this will work. I've tried selecting Preserve and not selecting Preserve and selecting Next in Magisk. My next option is to "select and patch a file". I downloaded the bin for 11.0.6.8 and extracted it using payload_dumper and Python and copied it to my phone. However, whenever I try to patch it, Magisk states installation failed.
So, I figured I would finish the install of 11.0.6.8 and rebooted the phone using the update installation reboot button. I figured I'd just start from scratch and root following the original root instructions. My bootloader is already unlocked. I copied the boot.img from 11.0.6.8 to my phone and tried to patch using Magisk (again, I only have the options above). Again, it failed.
What am I doing wrong? Why won't Magisk patch the boot.img file? Shouldn't it work like an original attempt to root it?
Thanks.

rcbjr2 said:
I previously had Magisk installed and rooted my 8T with Build 11.6.5.KB05AA. I followed some instructions on how to install an OTA update. I uninstalled Magisk and ran the OTA update. The instructions advise me to install Magisk on the inactive slot. However, I do not have this option. Instead, I only have Preserve AVB 2.0/dm-verify and Recovery Mode. I don't have TWRP installed so I don't think this will work. I've tried selecting Preserve and not selecting Preserve and selecting Next in Magisk. My next option is to "select and patch a file". I downloaded the bin for 11.0.6.8 and extracted it using payload_dumper and Python and copied it to my phone. However, whenever I try to patch it, Magisk states installation failed.
So, I figured I would finish the install of 11.0.6.8 and rebooted the phone using the update installation reboot button. I figured I'd just start from scratch and root following the original root instructions. My bootloader is already unlocked. I copied the boot.img from 11.0.6.8 to my phone and tried to patch using Magisk (again, I only have the options above). Again, it failed.
What am I doing wrong? Why won't Magisk patch the boot.img file? Shouldn't it work like an original attempt to root it?
Thanks.
Click to expand...
Click to collapse
Make sure you download the latest canary magisk manager. It sound like you might be on an older magisk version.

Qnorsten said:
Make sure you download the latest canary magisk manager. It sound like you might be on an older magisk version.
Click to expand...
Click to collapse
I seem to have the Canary Update channel set already (I thought it was set to Stable, but I guess not). Doesn't that mean I already have the latest Canary build? Manager shows that latest is 6951d926 (21402) (16) but Installed shows 658d74e0 (21402) (16). I assume this means they are different? Install doesn't seem to update it. Maybe grab the latest APK from Github? Thanks.
Later: Can I install it on my phone by download Magisk v21.4 zip and changing extension to APK and installing it? I thought I read everything is now in the zip/apk? Thanks.
FINAL UPDATE: OK, I downloaded the latest MagiskManager, not the one from Canary. I was then able to patch the boot file. The phone rebooted, but it's not working just right yet. None of my icons show up on my home screen, although if I press the recent apps list, it shows a bunch of apps, although selecting one doesn't do anything. I might have to put the original boot image back on just to get it to boot and worry about rooting later. Sigh. It's always something.

Have you tried following this guide it should work perfectly
[Guide] OnePlus 8T EASY ROOT (for all unlocked variants)
DO NOT FOLLOW THIS GUIDE IF YOU HAVE ANDROID 12 Visit this thread for more information ________________________________________________________ CAVEAT I've only tested this on my device running Android 11 (KB2005 / KB05AA), but it should be...
forum.xda-developers.com
In the latest canary apk released today he moved over to that the apk bundle magisk as well and don't need to download it anymore but it shouldn't matter for this case. There is no working custom recovery for Oneplus 8T right now. But if there was and it was updated you would be able to flash the apk.

You did not have to uninstall Magisk. When you would complete the OTA, instead of rebooting you should go into Magisk and select install to inactive slot. As you uninstalled magisk, you're not getting this option. Uninstalling magisk is different from disabling the modules.
Now you need to root it again using the same method given in other thread. Rooting 11.0.6.8 is no different from the rooting process for previous OOS versions.

alanzaki073 said:
Now you need to root it again using the same method given in other thread. Rooting 11.0.6.8 is no different from the rooting process for previous OOS versions.
Click to expand...
Click to collapse
I was able to patch the new boot image and flashed it but when I rebooted nothing worked quite right. None of my apps would run. I could get into settings but couldn't get out of it. I flashed the unrooted boot image and am able to use the phone. I'll try again tomorrow.
The instructions I followed said to uninstall Magisk first. Now wish I hadn't. I suppose worse comes to worse I can figure out how to reinstall 6.5 cause I was able to root that. Thanks for the reply.

Qnorsten said:
Have you tried following this guide it should work perfectly
[Guide] OnePlus 8T EASY ROOT (for all unlocked variants)
DO NOT FOLLOW THIS GUIDE IF YOU HAVE ANDROID 12 Visit this thread for more information ________________________________________________________ CAVEAT I've only tested this on my device running Android 11 (KB2005 / KB05AA), but it should be...
forum.xda-developers.com
In the latest canary apk released today he moved over to that the apk bundle magisk as well and don't need to download it anymore but it shouldn't matter for this case. There is no working custom recovery for Oneplus 8T right now. But if there was and it was updated you would be able to flash the apk.
Click to expand...
Click to collapse
I was looking at a different guide, but will try the one you recommend. I'm aware there is no TWRP for the 8T. I did use that method for my prior OP6. I did patch and flash the patched boot image, but none of my apps appeared on my home page so I flashed the unrooted boot image so I could at least use the phone. Thanks.

rcbjr2 said:
I was able to patch the new boot image and flashed it but when I rebooted nothing worked quite right. None of my apps would run. I could get into settings but couldn't get out of it. I flashed the unrooted boot image and am able to use the phone. I'll try again tomorrow.
The instructions I followed said to uninstall Magisk first. Now wish I hadn't. I suppose worse comes to worse I can figure out how to reinstall 6.5 cause I was able to root that. Thanks for the reply.
Click to expand...
Click to collapse
The instructions definitely lied to you...
Now:
1. Take the 11.0.6.8 boot image
2. Patch it with magisk (latest beta is fine, you don't need alpha anymore)
3. Boot the patched image
4. Install magisk manager in case it's not installed
5. Check it for root, if all is fine do install --> direct install
6. Reboot

Kollachi said:
The instructions definitely lied to you...
Now:
1. Take the 11.0.6.8 boot image
2. Patch it with magisk (latest beta is fine, you don't need alpha anymore)
3. Boot the patched image
4. Install magisk manager in case it's not installed
5. Check it for root, if all is fine do install --> direct install
6. Reboot
Click to expand...
Click to collapse
When you say Boot the patched image, I assume you mean fastboot flash it to the device?
I tried updating Magisk using a beta channel, but then manager wouldn't work at all. I just wouldn't run. So I reinstalled Manager 8.0.7 from the APK I downloaded and now I don't have Canary as an update channel. I keep alternative between having a Magisk icon and a separate manager icon. Weird. I'm trying to only wind up with latest manager installed so I can re-root the phone. Thanks.
LATER: Success! I followed the steps here: https://forum.xda-developers.com/t/guide-oneplus-8t-easy-root-for-all-unlocked-variants.4210775/. And everything worked (which was linked in a prior message). Thanks to all!

rcbjr2 said:
When you say Boot the patched image, I assume you mean fastboot flash it to the device?
I tried updating Magisk using a beta channel, but then manager wouldn't work at all. I just wouldn't run. So I reinstalled Manager 8.0.7 from the APK I downloaded and now I don't have Canary as an update channel. I keep alternative between having a Magisk icon and a separate manager icon. Weird. I'm trying to only wind up with latest manager installed so I can re-root the phone. Thanks.
LATER: Success! I followed the steps here: https://forum.xda-developers.com/t/guide-oneplus-8t-easy-root-for-all-unlocked-variants.4210775/. And everything worked (which was linked in a prior message). Thanks to all!
Click to expand...
Click to collapse
Nope i mean "fastboot boot xxxxx.img"

Kollachi said:
Nope i mean "fastboot boot xxxxx.img"
Click to expand...
Click to collapse
I figured out that's what you meant when I followed the instructions linked in another message. I had never booted that way previously. Thanks!

I am about to root my 8t using the guide someone linked above. My question is.. I'm on ver. 11.0.5.6.KB05AA will I still be able to root if I update or will it take away the ability to root.. also, will it affect the quality of the root ? Thanks in Advance.

Lost root after installing TWRP. Can anyone share patched boot image for 11.0.5.1.GM21AA?

As above, I would appreciate it if someone could share a copy of a Magisk patched 11.0.5.1.GM21AA boot image. Thanks!
P.S. - Do not update to Magisk 24 or 24.1 unless you want to have to mess around with your phone!

Here you go.
Patched with 24.1 Magisk. Rom Zip downloaded from here
[OnePlus 7 Pro (5G)][ROM][OTA][Oxygen OS] Repo of Oxygen OS Builds
As OnePlus doesn't always provide download links for all of their OxygenOS ROMs & OTA update zips, we've created an index to put the links in one post so that they're easy to find. Note: this is not a support thread for issues you may have with...
forum.xda-developers.com
File on MEGA
mega.nz
I also had problems with updating Magisk trough the app. No root after reboot.
Could not get root access with flashing magisk in twrp. I tried several version of magisk but nothing worked. Ended up using the patched boot.img
Dont know what the problem is.

Dan3ll1 said:
Here you go.
Patched with 24.1 Magisk. Rom Zip downloaded from here
[OnePlus 7 Pro (5G)][ROM][OTA][Oxygen OS] Repo of Oxygen OS Builds
As OnePlus doesn't always provide download links for all of their OxygenOS ROMs & OTA update zips, we've created an index to put the links in one post so that they're easy to find. Note: this is not a support thread for issues you may have with...
forum.xda-developers.com
File on MEGA
mega.nz
I also had problems with updating Magisk trough the app. No root after reboot.
Could not get root access with flashing magisk in twrp. I tried several version of magisk but nothing worked. Ended up using the patched boot.img
Dont know what the problem is.
Click to expand...
Click to collapse
Thanks a lot!
I managed to get Magisk 23 installed, would the patched boot image be different from yours?

benengyj said:
Thanks a lot!
I managed to get Magisk 23 installed, would the patched boot image be different from yours?
Click to expand...
Click to collapse
How did you do??
I tried to downgrade Magisk to 23.0 due to the lack of Magisk Hide but now my OnePlus 7 Pro is no longer rooted. So I tried to re-root it in several ways (flashing boot.img previously patched with Magisk Manager or by directly installing Magisk.zip with TWRP) but nothing to do, still without root...
I would like to try to use another boot.img but I would need one taken from a rom 11.0.5.1.GM21BA and patched with Magisk 23. I can't find it on the net.

Frodolo said:
How did you do??
I tried to downgrade Magisk to 23.0 due to the lack of Magisk Hide but now my OnePlus 7 Pro is no longer rooted. So I tried to re-root it in several ways (flashing boot.img previously patched with Magisk Manager or by directly installing Magisk.zip with TWRP) but nothing to do, still without root...
I would like to try to use another boot.img but I would need one taken from a rom 11.0.5.1.GM21BA and patched with Magisk 23. I can't find it on the net.
Click to expand...
Click to collapse
Once you've upgraded to 24 or 24.1 it seems that the only way to go back to an older version is to use the built-in uninstall button in the Magisk app. Just trying to flash a new boot image over it doesn't seem to stick.
In my case, I had to:
Uninstall any version of the Magisk app
Install 24.1
Extract the boot image using Payload Dumper
Creating a 24.1 patched boot image to re-root my device
Uninstalling 24.1 using the uninstall button in the Magisk app
Install Canary Magisk (23 should work too)
Create a new 23 patched boot image and root using it
Still have not gotten around to fixing my MagiskHide and SafetyNet failing though, I think that requires some cache clearing and other steps to resolve. Also somehow managed to get rid of my TWRP accidentally along the way too, so I'll have to reinstall that again.

Thanks a lot!

benengyj said:
Uninstalling 24.1 using the uninstall button in the Magisk app
Click to expand...
Click to collapse
I only see an "Install" button in the Magisk 24.1 app. I don't see an "Uninstall" button.
Were you already rooted when you saw the Uninstall button?

¿GotJazz? said:
I only see an "Install" button in the Magisk 24.1 app. I don't see an "Uninstall" button.
Were you already rooted when you saw the Uninstall button?
Click to expand...
Click to collapse
See steps 1-4. You have to temporarily root it by flashing a patched boot image (that was patched with 24.1) so that you can use the root privileges to uninstall Magisk. It's kinda ass-backwards I know...lol

benengyj said:
See steps 1-4. You have to temporarily root it by flashing a patched boot image (that was patched with 24.1) so that you can use the root privileges to uninstall Magisk. It's kinda ass-backwards I know...lol
Click to expand...
Click to collapse
Yep, that's weird. I was having (a ton of) trouble getting my phone rooted at the time, so that's why I didn't see it.