Database Develop

[SOLVED] Can I really switch from SuperSU ?

Hi there fellows ! ^^
First of all, I want you all to know that I really am sorry if this is something that has been asked before. I tried, but couldn't find an answer by myself and I don't want to damage my phone again (I may have been waaaaay too hasty in the past...). So here goes.
I have a Honor 5C NEM-L51 (European variant) which I rooted a while ago (two or three months ago maybe ? Can't remember for sure) by unlocking the bootloader, installing TWRP from ADB, flashing the SuperSU zip file... You know, the usual thing. After that I went ahead and installed Xposed Framework, Busybox and several applications and modules which needed root like many of you I guess. Everything went fine. And still is, for the record.
Now I realize that I may have been living under a rock because I discovered very recently that not only SuperSU can be downloaded from the Play Store but also that there is Magisk, an open-source alternative with more functionnalities. Guess what ? I want it.
Soooo I did some research and read this https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 along with other articles here and there on the web and it seems that I'd just have to install some Magisk Manager app' from the Play Store... Is that really all there is to do ?!
I'm worried because it says "If you're already rooted with MagiskSU or Latest Official Systemless SuperSU". Yep, the "Systemless" part get me worried. While I do understand what it means, I can't help but wonder : since I installed SuperSU from a flashable zip file, is it Systemless ? How can I tell ?
Plus the whole thing is kinda confusing to me. If I do that, will Magisk remove SuperSU ? But if so, won't there be a problem with Xposed and other apps that need root ? Same question applies if I first manually remove SuperSU (assuming I can actually do that) before installing anything else.
In short, how should I proceed ? Do I have to remove anything ? Can I do anything ?
Again, sorry if things had been told already. I really want to take my shot, but I don't wanna soft brick my device again by being too carefree one more time.
Thank you for your time and your help.

When super su is installed magisk will make it automatically systemless. But it can't guarantee that it can always hide it. If super su isn't installed /you are unrooted then magisk will install and use magisk su.
Also since you mentioned them: soft bricks can be resolved by just reflashing your Rom, no need to wipe (lose your data) in most cases
Gesendet von meinem SM-G925F mit Tapatalk

ken2802 said:
When super su is installed magisk will make it automatically systemless. But it can't guarantee that it can always hide it. If super su isn't installed /you are unrooted then magisk will install and use magisk su.
Click to expand...
Click to collapse
Thank you for your answer. Can I uninstall SuperSU to install Magisk su instead then ? Do I need to remove Xposed module and my root apps too ?
ken2802 said:
Also since you mentioned them: soft bricks can be resolved by just reflashing your Rom, no need to wipe (lose your data) in most cases
Gesendet von meinem SM-G925F mit Tapatalk
Click to expand...
Click to collapse
Yeah, I do know that, but I really do need my phone at the moment, so I'd kinda be in a world of pain if I brick it.

You can Uninstall super su if you want but it isn't a must if you don't care magisk su. I would remove xposed before installing magisk and after having installed magisk you can install the systemless version. As for your apps that use root, you don't need do deinstall them

ken2802 said:
You can Uninstall super su if you want but it isn't a must if you don't care magisk su. I would remove xposed before installing magisk and after having installed magisk you can install the systemless version. As for your apps that use root, you don't need do deinstall them
Click to expand...
Click to collapse
Sorry for the late reply.
I do want to use Magisksu instead of SuperSU. So basically, what I have to do is :
1 - Uninstall Xposed by flashing the uninstaller from TWRP
2 - Uninstall SuperSu (by the app menu ? Is it enough to remove root ?
3 - Install Magisk from the store
4 - Install systemless Xposed from the store
And I'll be all set, correct ? Nothing should go wrong ?

Zarou said:
Sorry for the late reply.
I do want to use Magisksu instead of SuperSU. So basically, what I have to do is :
1 - Uninstall Xposed by flashing the uninstaller from TWRP
2 - Uninstall SuperSu (by the app menu ? Is it enough to remove root ?
3 - Install Magisk from the store
4 - Install systemless Xposed from the store
And I'll be all set, correct ? Nothing should go wrong ?
Click to expand...
Click to collapse
I'll add a couple of points to your list:
2.5 - Make sure to restore the stock boot image.
3.5 - Flash magisk.zip in recovery. You can't install through the Manager if not rooted.
If you want to use Magisk Hide to pass SafetyNet you'll have to disable Xposed. Magisk can't hide it, even if it's systemless.

Didgeridoohan said:
I'll add a couple of points to your list:
2.5 - Make sure to restore the stock boot image.
3.5 - Flash magisk.zip in recovery. You can't install through the Manager if not rooted.
If you want to use Magisk Hide to pass SafetyNet you'll have to disable Xposed. Magisk can't hide it, even if it's systemless.
Click to expand...
Click to collapse
Thank you for this clarification. Can you also tell me how can I restore the stock boot image only ? Or Do I have no choice but to re-flash the whole ROM in order to do so ?

Zarou said:
Thank you for this clarification. Can you also tell me how can I restore the stock boot image only ? Or Do I have no choice but to re-flash the whole ROM in order to do so ?
Click to expand...
Click to collapse
Just flash the boot image from an near stock custom Rom. You can flash it through a recovery menu

ken2802 said:
Just flash the boot image from an near stock custom Rom. You can flash it through a recovery menu
Click to expand...
Click to collapse
Well, all I can find with Huawei Firmware Finder seems to be full or OTA ROM updates. I can't download the boot image only.
However, within the SuperSU app settings, there are two options : one to change superuser app and a second one to completely remove root. By any chance, does one of these options clear the boot image by itself ?

Zarou said:
Well, all I can find with Huawei Firmware Finder seems to be full or OTA ROM updates. I can't download the boot image only.
However, within the SuperSU app settings, there are two options : one to change superuser app and a second one to completely remove root. By any chance, does one of these options clear the boot image by itself ?
Click to expand...
Click to collapse
You can try but if magisk complain while instalation you need to flash a fresh boot image/Rom
Gesendet von meinem SM-G925F mit Tapatalk

Zarou said:
Well, all I can find with Huawei Firmware Finder seems to be full or OTA ROM updates. I can't download the boot image only.
However, within the SuperSU app settings, there are two options : one to change superuser app and a second one to completely remove root. By any chance, does one of these options clear the boot image by itself ?
Click to expand...
Click to collapse
It can be a bit of a bother getting the boot image from inside a Huawei factory image...
SuperSU can restore your boot image when you do the full unroot. That was actually what I was referring to with my 2.5.

Didgeridoohan said:
It can be a bit of a bother getting the boot image from inside a Huawei factory image...
SuperSU can restore your boot image when you do the full unroot. That was actually what I was referring to with my 2.5.
Click to expand...
Click to collapse
Thank you, I managed to get by the whole thing with no issue. Problem solved !

Didgeridoohan said:
I'll add a couple of points to your list:
2.5 - Make sure to restore the stock boot image.
3.5 - Flash magisk.zip in recovery. You can't install through the Manager if not rooted.
If you want to use Magisk Hide to pass SafetyNet you'll have to disable Xposed. Magisk can't hide it, even if it's systemless.
Click to expand...
Click to collapse
Hi all,
Yesterday I've unlocked my Oneplus 3T bootloader and installed TWRP.
After that I flashed Lineage 14.1, Open Gapps, addonsu-14.1-arm64-signed.zip and finally Magisk. Reboot and install SuperSu.
But I'm wondering if I still need to flash the Lineage addonsu and SuperSu.

tutabeier said:
Hi all,
Yesterday I've unlocked my Oneplus 3T bootloader and installed TWRP.
After that I flashed Lineage 14.1, Open Gapps, addonsu-14.1-arm64-signed.zip and finally Magisk. Reboot and install SuperSu.
But I'm wondering if I still need to flash the Lineage addonsu and SuperSu.
Click to expand...
Click to collapse
What are you doing mixing all those root solutions? Pick one... If you want Magisk, you do not need the other two.

Didgeridoohan said:
What are you doing mixing all those root solutions? Pick one... If you want Magisk, you do not need the other two.
Click to expand...
Click to collapse
Thanks. I probably missed something when reading the threads. I understood Magisk can root my devices, but didn't understood that simply installing it would root my device. So that's why I was flashing su binary and using SuperSU app.
Thanks a lot.

First of all I'm sorry for answering this post so late but I needed to do it.
Well, according to all I've seen about magisk, and obviously with this post, everything I must do to use magisk is:
1. Unlock Bootloader
2. Flash Official Stock ROM
3. Flash Magisk.zip
4. Install Magisk Manager
Is it all? Really? Shouldn't I do anything else, because I'm too worried about it. I've ever used SuperSU until now, and this things of MagiskSU, Magisk Manager and Magisk Hide option are really new for me.
If someone could answer me, including the owner of this post it'd be VERY APPRECIATED and I would thank you all a lot!
Thanks haha

xdaVTU said:
First of all I'm sorry for answering this post so late but I needed to do it.
Well, according to all I've seen about magisk, and obviously with this post, everything I must do to use magisk is:
1. Unlock Bootloader
2. Flash Official Stock ROM
3. Flash Magisk.zip
4. Install Magisk Manager
Is it all? Really? Shouldn't I do anything else, because I'm too worried about it. I've ever used SuperSU until now, and this things of MagiskSU, Magisk Manager and Magisk Hide option are really new for me.
If someone could answer me, including the owner of this post it'd be VERY APPRECIATED and I would thank you all a lot!
Thanks haha
Click to expand...
Click to collapse
It's not quite apparent from your post if you have rooted with SuperSU already and now want to use Magisk instead. But, considering that you're posting in a thread that deals with moving from SuperSU I'm gonna go with that... Kind of...
You will need an unlocked bootloader, yes.
If you've rooted with SuperSU you can reflash your ROM, or use something like @osm0sis unSU zip and then flash the stock boot image only. Depends on your setup which option is easier. If you're not already rooted, this step is unnecessary.
Installing Magisk is just as easy as that, yes.
The Manager is also installed when flashing the Magisk zip, so this step is unnecessary. However... In rare cases the Manager doesn't install with the zip. If that happens you just have to install it manually.
The only step I'd like to add is to have a backup of all important data and files on your device. That's always good practice when tinkering with your device...
The release thread and the installation/troubleshooting thread (I'm hoping to have time to update it for Magisk v15.2 tonight) are good resources when setting everything up and if you encounter issues. Searching through the general support thread is also a good idea if issues arise. Most questions have been answered numerous times already.

I'm new to Magisk but have a couple of questions. I have a pixel XL running Dirty UNICORNS rooted with SuperSU. If I want to use Magisk can I just flash my dirty UNICORNS rom, gapps and then the magisk.zip?
Sent from my Pixel XL using Tapatalk

Hi ..I am using Nexus 6 stock rom , super su, and with all kind root apps Xposed modules .
My questions is do I need to uninstall all the root apps first before flashing the UN su zip ?? Pls help sir

jc1266 said:
Hi ..I am using Nexus 6 stock rom , super su, and with all kind root apps Xposed modules .
My questions is do I need to uninstall all the root apps first before flashing the UN su zip ?? Pls help sir
Click to expand...
Click to collapse
No. You merely need to uninstall SuperSU, either through the SuperSU app (complete uninstall) or by using the unSU zip. You'll also have to make sure that you restore the stock unpatched boot image.
After that you can flash Magisk and you'll be good to go.

Magisk V16 can't install on Android 5.0

Has anyone has success in installing this on Android 5.0 samsung S4 ? I followed the instructions and the manager just says not installed.

Unless you provide more details and installation logs it's gonna be hard to help...

Didgeridoohan said:
Unless you provide more details and installation logs it's gonna be hard to help...
Click to expand...
Click to collapse
What details would you like to know? I flash it and then later restart but the manager was not there so I tried to install it from saving the apk file that I downloaded. But it just said it was not installed and later I found out I lost root from trying to flash Xposed on my phone.
I am very new to this and tried to follow the tutorials and videos but its not working cause I thought using Magisk I can install the seamless Xposed.

Those recovery/installation logs would be a good start.
You're muddling up the details a bit...
Was the Manager not installed or did it report that Magisk wasn't installed? And you lost root? But you said you couldn't install Magisk... Are you already rooted? That might cause issues.
Being nice and clear and detailed (what is being flashed, version numbers, what's already done, what works, what doesn't work, with logs, etc) in your descriptions would help.

Didgeridoohan said:
Those recovery/installation logs would be a good start.
You're muddling up the details a bit...
Was the Manager not installed or did it report that Magisk wasn't installed? And you lost root? But you said you couldn't install Magisk... Are you already rooted? That might cause issues.
Being nice and clear and detailed (what is being flashed, version numbers, what's already done, what works, what doesn't work, with logs, etc) in your descriptions would help.
Click to expand...
Click to collapse
I hope this is clearly for you!
1. I flash the file with TWRP with success
2. The phone got stuck on samsung logo
3. Root was removed.
4.I had to re flash stock and it is working again.
5. How do I get the logs of Magisk if my phone keeps looping?
I wanted to use Magisk to see if Xposed would work but it looks like i can't even get Magisk to work on my samsung i9500 with original rom. This same thing happens with Xposed where everything goes smoothly with flashing it in recovery and then a boot loop on the logo. Others on this forum have been complaining about this too and perhaps the developer might have not considered odexed rom like samsung for these wonderful apps to work?
I am going back to Kitkat where i don't have these issues and I can use Xposed.

Phone stuck on booting screen after install

Hello,
first off, sorry. I was stupid and didn't read into it before installing (or trying to install) Xposed to my Samsung S8. Yes, i've read now that it doesn't work with the official ROM, but now it's a bit to late.
So. After rooting my S8 today (using TWRP) i wanted to install Xposed. I downloaded an installer from this site because.. umm, i had a brain fart. For some reason my brain took that site as the official website, so i downloaded it from a 3rd Party site instead of the actual website.
I installed the apk and granted root access. After that i clicked on install and Xposed installed successfully. After that it obviously asked me to reboot my device, which i did. But now i am stuck on the Samsung screen of the boot progress. I know i could technically just wipe the phone (again) and start anew, but i'd like to avoid that if possible. I can access TWRP, but if i try to access the system files in the file browser, it shows "0MB" and i can't access them.
I tried downloading an uninstaller linked in this thread, but i don't know which one i should download.
Sorry again for me being so stupid and not reading into it and downloading from some weird 3rd Party site.
Thanks in advance for the help!
EDIT: And yea, of course i didn't create a backup before installing Xposed. So if there is no way to properly uninstall it, i gotta wipe everything once again

Emilia-Chan said:
Hello, first off, sorry. I was stupid and didn't read into it before installing (or trying to install) Xposed to my Samsung S8.......
Click to expand...
Click to collapse
I don't have this device but, I believe that you should be able to flash (via TWRP) the Framework Uninstaller located on the following Official XPosed link. Just select the correct ARCH (ARM, ARM64, etc...) for your device.
http://dl-xda.xposed.info/framework/uninstaller/
If necessary, you can always try to obtain some additional member guidance and support from the following Q&A thread that's specific to your device and variants.
https://forum.xda-developers.com/showthread.php?t=3582142
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.

In the link provided by @lbuprophen use the arm64 zip uninstaller (latest version) to uninstall exposed.
Just curious how long did you let it try to boot for,mine took 10-15 minutes for it to do it's thing and boot up.
Sent from my Samsung Galaxy S8 using XDA Labs

Ibuprophen said:
I don't have this device but, I believe that you should be able to flash (via TWRP) the Framework Uninstaller located on the following Official XPosed link. Just select the correct ARCH (ARM, ARM64, etc...) for your device.
Click to expand...
Click to collapse
I tried that before, unfortunately without success. It also may be noteworthy that my brain turned off and downloaded the XPosed installer off some 3rd Party site. I know. Stupid. But it happened.
spawnlives said:
In the link provided by @lbuprophen use the arm64 zip uninstaller (latest version) to uninstall exposed.
Just curious how long did you let it try to boot for,mine took 10-15 minutes for it to do it's thing and boot up.
Click to expand...
Click to collapse
I waited over an hour for my phone to boot, before and after flashing the uninstaller. I also tried wiping it and even completely formatting the data, everything without any success. It kept on not passing the Samsung screen and eventually bootlooping.
I fixed the issue by just flashing the stock rom with odin and then reinstalling TWRP and rooting my device again. Will stay away from XPosed with this phone for now.
Thanks for the advice anyways!

Emilia-Chan said:
.... I fixed the issue by just flashing the stock rom with odin and then reinstalling TWRP and rooting my device again. Will stay away from XPosed with this phone for now. Thanks for the advice anyways!
Click to expand...
Click to collapse
You did what I would have probably done myself in this situation by starting from scratch.
I just wanted to let you know that I believe that I had saw somewhere (within the dedicated area of the forum for your device) that individuals were successful with Magisk XPosed.
Though I do understand if you want to stay away from XPosed until your ready again and I'm happy to see that your at least up and running again.
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.

I got the same even just after the installation of the apk for Systemless Xposed on an Xperia (XposedInstaller_3.1.5-Magisk.apk) found here: https://forum.xda-developers.com/xposed/unofficial-systemless-xposed-t3388268
I made a reboot as I like to isolate the issues while they happen. That was it: bootloop..

How to safely unroot?

I had installed edexposed yahfa, for gravitybox. And I rooted by having magisk patch the stock boot pulled from the factory image.
I have uninstalled gravitybox from edexposed, and uninstalled riru core and edexposed from magisk.
I just don't want to cause any problems. At this step, what is the correct procedure to unroot and get back to stock? Thank you!

finshan said:
I had installed edexposed yahfa, for gravitybox. And I rooted by having magisk patch the stock boot pulled from the factory image.
I have uninstalled gravitybox from edexposed, and uninstalled riru core and edexposed from magisk.
I just don't want to cause any problems. At this step, what is the correct procedure to unroot and get back to stock? Thank you!
Click to expand...
Click to collapse
Search is always your friend! :good:
https://forum.xda-developers.com/pixel-4-xl/help/unroot-relock-pixel-4-xl-t4009313/amp/

Badger50 said:
Search is always your friend! :good:
https://forum.xda-developers.com/pixel-4-xl/help/unroot-relock-pixel-4-xl-t4009313/amp/
Click to expand...
Click to collapse
Thanks but I did search. In general, random posts like that are totally unreliable and have caused me more than one brick in the past.
For example, I wouldn't know that I needed to disable edexposed modules then also disable all magisk modules and then specifically uninstall magisk VIA MAGISK if I hadn't read more recent instructions which I can't find in a search now.
So I was hoping this Q/A section would kindly help A my Q with the most current and comprehensive instructions—even if it's only a link to an existing current and complete answer.
Please don't redirect people to random unpredictable search results for anything regarding root.

finshan said:
Thanks but I did search. In general, random posts like that are totally unreliable and have caused me more than one brick in the past.
For example, I wouldn't know that I needed to disable edexposed modules then also disable all magisk modules and then specifically uninstall magisk VIA MAGISK if I hadn't read more recent instructions which I can't find in a search now.
So I was hoping this Q/A section would kindly help A my Q with the most current and comprehensive instructions—even if it's only a link to an existing current and complete answer.
Please don't redirect people to random unpredictable search results for anything regarding root.
Click to expand...
Click to collapse
What badger has provided is all you need and is correct. No point us repeating what is already explained in that thread

finshan said:
Thanks but I did search. In general, random posts like that are totally unreliable and have caused me more than one brick in the past.
For example, I wouldn't know that I needed to disable edexposed modules then also disable all magisk modules and then specifically uninstall magisk VIA MAGISK if I hadn't read more recent instructions which I can't find in a search now.
So I was hoping this Q/A section would kindly help A my Q with the most current and comprehensive instructions—even if it's only a link to an existing current and complete answer.
Please don't redirect people to random unpredictable search results for anything regarding root.
Click to expand...
Click to collapse
Well then, how about this. Uninstall all magisk modules, then let Magisk manager uninstall itself, then either clean or dirty fastboot the factory image build that your currently on depending if you want to wipe your internal data or not. If on the other hand, you just want to be non-rooted, without uninstalling all your magisk modules, then all you would have to do is fastboot the stock boot.img to both slots with: fastboot flash boot boot.img --slot=all. Just make sure your platform-tools are up to date before you start. Thank you, and have a pleasant day.

Magisk Update from 2.30 to 2.4.1 Guide for dummies

The new Magisk is here and with it some major changes. One of the most important is the removal of support for "MagiskHide". There are many advanced users who have figured this all out already and few (maybe more) like me who are just kind of lost not knowing what should be exactly done to be able to update and be able to use Magisk as they were, before the update.
I was hoping that a kind soul would put up an easy step by step guide to help these users and at the same time it will avoid a lot of repetitive questions on the main thread. I personally spent a long time reading many pages and was not able to fully understand what should be done.
In my case all I want to achieve is to update and be able to hide Magisk like it was in the previous version. Should I start by un-hiding it first before doing the update?
(what and how and from where) should I add something that will replace the hiding function? Viola! these are the kind of simple questions that will help some of us get going
I hope that someone will bring his precious help

Yeah I unfortunately did my upgrade and fought with the whole process for 6 hours straight (lol) and I still don't know what I did exactly to even begin to write any instructions - other than 6 hours straight of reading and trying and hoping .....
Not sure if you have been able to refer to this which helped me.... But, I also have an very basic understanding of how my device (OnePlus 7T) works with Magisk... Hope this helps. May be see if your specific device has the instructions already posted in the device specific forum here?
Installation
The Magic Mask for Android
topjohnwu.github.io
I've not used the Magisk hide cause I haven't needed it - BUT, it's still available in the latest Magisk Manager (24.1) in the Magisk Manager settings. I'm only using the systemless hosts module (included in Magisk manager settings) for Adaway, and the universal safety net fix to get Google Play store to say my device is certified.
But I don't know what device you have nor do I know the specific ROM you are using.
Sounds like you have root already so I'm thinking that's the worst of this behind you if you've already done that much yourself. Sounds like it's a basic case of update the Magisk Manager app from itself then determine the method appropriate for root to update which could be through the Manager app or like I chose to use the boot IMG then patch that then install since my device has no working TWRP. That, and once I updated the manager app and panicked so I uninstalled it to try and downgrade to v23 .... Good luck and may be just don't update just yet if there is no specific need to at this time. Take your time and read and proceed when comfortable.
Please:
Start with your preferred method of backing up everything first.
Also, may be consider if it's necessary to update and why??? I'm on stock Andriod 11 and this Magisk update make me think it's intended to be more for those on Android 12 - but I could also assume wrongly.
[Discussion] Magisk - The Age of Zygisk.
This is a discussion and help thread for the newer versions of Magisk. The main goal of this thread is to help users migrate to Magisk v24+ SafetyNet Basic integrity Pass CTS profile match Pass Play Protect certification Device is certified...
forum.xda-developers.com
That's the thread I'm reading now...

Thanks a lot for your reply wugga3. I also on my side found two very helpful posts. They explain the basics (just to get started) and to make the update . I hope with the information gathered I will be able to do the update without messing things up!
[Discussion] Google Pay Magisk Discussion Thread
This thread is inspired by the PoGo Magisk discussion thread. It's meant to keep the clutter of "Google Pay doesn't work" posts out of the main Magisk threads. Please use this to discuss issues with Google Pay and possible solutions. There's a...
forum.xda-developers.com
[Discussion] Magisk - The Age of Zygisk.
This is a discussion and help thread for the newer versions of Magisk. The main goal of this thread is to help users migrate to Magisk v24+ SafetyNet Basic integrity Pass CTS profile match Pass Play Protect certification Device is certified...
forum.xda-developers.com

Good and good luck...
One problem and probably the only problem I really had was self inflicted for not following the instructions properly and that was to uninstall any Magisk modules first or at that the appropriate step.
Other than that... still don't know your device or rom etc. Your device specific or rom specific forums may be able to provide you with much better assistance from members that have the same rom/device as you.

wugga3 said:
Good and good luck...
One problem and probably the only problem I really had was self inflicted for not following the instructions properly and that was to uninstall any Magisk modules first or at that the appropriate step.
Other than that... still don't know your device or rom etc. Your device specific or rom specific forums may be able to provide you with much better assistance from members that have the same rom/device as youI
Click to expand...
Click to collapse
I am using LineageOS 18.1 Android 11 for Samsung Galaxy Note 3 and I have twrp as recovery. Magisk 2.30 is already installed and device is rooted. I have no modules installed and in Magisk settings I have only MagiskHide enabled. All other settings are set to default. On Samsung Note3 forum there is no talk about this (understandable as the device is very old).

Ok great and is there any discussion for lineage 18.1 and root/update?
Since it's lineage 18 and based on Andriod 11 - I have to wonder if there is even the need to update Magisk as my limited understanding is that the Magisk update is aimed at Andriod 12? Other than that... I should expect from my prior understandings of Samsung that nothing much has changed with respect to root and updates of Magisk. Not much help but hopefully enough. May be best to wait until for now and usually I do also wait until all the facts are in and the bugs are sorted out (if any...) before I update if unnecessary.

Thanks wugga3,
I disabled "Check for updates" in Magisk app and decided to keep the older 2.30 version for now. Everything is working fine and so there is no reason to fix something which is not broken. The only reason I thought That I should update was a real advantage over the older version or a security weakness being fixed in the new one.
I am even seeing some people asking for help on how to downgrade! Anyway as you said wisely, it;s not after all a bad idea to wait a little to see how things work out for those who have upgraded and have new issues fixed before taking the jump.

Moving from 23.0 to 24.1 is straightforward
1. Update app
2. Update boot (Magisk) to 24.1, reboot
3. Enable Zygisk, reboot
4. Enforce Deny List, reboot
5. Install module USNF, reboot
6. Configure Deny List. Don't worry about Play Service because USNF will take care of it. Add any app detected root into it, and reboot every time it's updated
7. Install Fox Module manager and pick module you want

mingkee said:
Moving from 23.0 to 24.1 is straightforward
1. Update app
2. Update boot to 24.1, reboot
3. Enable Zygisk, reboot
4. Enforce Deny List, reboot
5. Install module USNF, reboot
6. Configure Deny List. Don't worry about Play Service because USNF will take care of it. Add any app detected root into it, and reboot every time it's updated
7. Install Fox Module manager and pick module you want
Click to expand...
Click to collapse
Thanks a lot for your post mingkee,
I am sure many like me will be happy and appreciate reading this instead of having to go through many pages and still not be totally sure what to do
Allow me to just ask one question as I did not understand the second option of your instruction:
I update Magisk from the application itself. Once updated what do you mean by update boot to 24.1? This is to be done in Magisk itself?

rezpower said:
Thanks a lot for your post mingkee,
I am sure many like me will be happy and appreciate reading this instead of having to go through many pages and still not be totally sure what to do
Allow me to just ask one question as I did not understand the second option of your instruction:
I update Magisk from the application itself. Once updated what do you mean by update boot to 24.1? This is to be done in Magisk itself?
Click to expand...
Click to collapse
After updated app to 24.1, you will see another update on top of the app (Magisk). Direct install would be the simplest method

mingkee said:
Moving from 23.0 to 24.1 is straightforward
1. Update app
2. Update boot (Magisk) to 24.1, reboot
3. Enable Zygisk, reboot
4. Enforce Deny List, reboot
5. Install module USNF, reboot
6. Configure Deny List. Don't worry about Play Service because USNF will take care of it. Add any app detected root into it, and reboot every time it's updated
7. Install Fox Module manager and pick module you want
Click to expand...
Click to collapse
this should be pinned somewhere, very simple and worked fine on my Poco F3 using miui.eu & android 11
thanks a lot