Database Develop

Advanteges of Magisk?

I want to root my device.
But I'm unable to decide that I should root via supersu or Magisk.
I've read that magisk provide systemless root, but what the advanteges of systemless root/magisk?
Can someone help me that what's the use/advantage of Magisk?
is it much stable then supersu?
I don't want to risk my device as I'm app developer

akash.galaxy07 said:
I want to root my device.
But I'm unable to decide that I should root via supersu or Magisk.
I've read that magisk provide systemless root, but what the advanteges of systemless root/magisk?
Can someone help me that what's the use/advantage of Magisk?
is it much stable then supersu?
I don't want to risk my device as I'm app developer
Click to expand...
Click to collapse
If you are an app developer, use Magisk. Magisk allows you to pass google's safety tests (Safetynet) - which you should know about if you develop apps! but basically, google will not think your device is compromised is you use Magisk, but WILL think your device is compromised if you use SuperSU - even if SuperSU is installed in Systemless mode. Don't forget to enable magisk hide in the Magisk Manager app to make sure this works though.
Some app developers will check safetynet upon launching their app to see if the device is compromised, and if it is, either restrict features, or deny access entirely. A good example of this is Banking apps, though they usually use their own root detection - but that can be hidden with Magisk Hide. - No bank wants their app being used on a compromised device, where a virus with root access could collect information. The more you know

manor7777 said:
If you are an app developer, use Magisk. Magisk allows you to pass google's safety tests (Safetynet) - which you should know about if you develop apps! but basically, google will not think your device is compromised is you use Magisk, but WILL think your device is compromised if you use SuperSU - even if SuperSU is installed in Systemless mode. Don't forget to enable magisk hide in the Magisk Manager app to make sure this works though.
Some app developers will check safetynet upon launching their app to see if the device is compromised, and if it is, either restrict features, or deny access entirely. A good example of this is Banking apps, though they usually use their own root detection - but that can be hidden with Magisk Hide. - No bank wants their app being used on a compromised device, where a virus with root access could collect information. The more you know
Click to expand...
Click to collapse
Thanks bro, and, is it stable too? I mean, are there any risks involved?

akash.galaxy07 said:
Thanks bro, and, is it stable too? I mean, are there any risks involved?
Click to expand...
Click to collapse
There are risks with any kind of root on your phone, as an app developer, you should know that.
You could get a virus that takes advantage of root to encrypt all of your files.
Again, you should know this if you are an app developer, there is a difference between creating a single app, and developing applications as a whole!
Magisk is very stable though, more so on OxygenOS but it will be pretty stable with LineageOS too! I have had no problems whatsoever! I have been using android pay and all my root apps without my phone ever crashing! And if you are careful, you won't get a virus (root will not cause a virus, user stupidity gets virus') - enjoy

I'd like to add the main advantage to why I use Magisk.
All my system modifications (build.prop changes, debloating, changed/removed ui audio, etc) are still there after a system update. Even if I have to do a clean install with a wipe, all it takes is flashing a couple of extra zips and everything is right back were I want it.

Didgeridoohan said:
I'd like to add the main advantage to why I use Magisk.
All my system modifications (build.prop changes, debloating, changed/removed ui audio, etc) are still there after a system update. Even if I have to do a clean install with a wipe, all it takes is flashing a couple of extra zips and everything is right back were I want it.
Click to expand...
Click to collapse
Can you please link me to Magisk installation thread for Oneplus 3t. I can't find any on XDA. I found one thread that belongs to Magisk dev but it is very confusing with installing all the systemless SuperSU and such.

vipivj said:
Can you please link me to Magisk installation thread for Oneplus 3t. I can't find any on XDA. I found one thread that belongs to Magisk dev but it is very confusing with installing all the systemless SuperSU and such.
Click to expand...
Click to collapse
There's no specific 3T thread that I know of... It's all there in the Magisk forums. It's not as complicated as it might seem.
If you're unrooted, just flash the Magisk zip in TWRP. Done!
If you have systemless SuperSU installed and want to keep it, just flash the Magisk zip in TWRP. Done!
If you have systemless SuperSU installed and want to switch to MagiskSU, you'll need to first remove SuperSU. Use the full unroot option in the SuperSU app and say yes when asked if you want to restore the boot image backup. After that, flash the Magisk zip in TWRP. Done!
If you have any other root installed, just flash the Magisk zip in TWRP and the installation script will do it's best to remove it and install MagiskSU instead. Done!
Edit: There might be variations on the above, depending on if you're using stock ROM or not. Take a look at the link in my signature if you run into problems. I've tried to collect as much info, tips and tricks as possible in one place.

Didgeridoohan said:
There's no specific 3T thread that I know of... It's all there in the Magisk forums. It's not as complicated as it might seem.
If you're unrooted, just flash the Magisk zip in TWRP. Done!
If you have systemless SuperSU installed and want to keep it, just flash the Magisk zip in TWRP. Done!
If you have systemless SuperSU installed and want to switch to MagiskSU, you'll need to first remove SuperSU. Use the full unroot option in the SuperSU app and say yes when asked if you want to restore the boot image backup. After that, flash the Magisk zip in TWRP. Done!
If you have any other root installed, just flash the Magisk zip in TWRP and the installation script will do it's best to remove it and install MagiskSU instead. Done!
Edit: There might be variations on the above, depending on if you're using stock ROM or not. Take a look at the link in my signature if you run into problems. I've tried to collect as much info, tips and tricks as possible in one place.
Click to expand...
Click to collapse
Thanks, it is clear now. Is it possible to 100% pass safety net with Magisk? I read somewhere that it's a hit and miss.
Apart from the Magisk modules what's the benefit of rooting with Magisk instead of superSU? I saw many people still support superSU than Magisk, does it mean that Magisk has some flows or bugs?

vipivj said:
Thanks, it is clear now. Is it possible to 100% pass safety net with Magisk? I read somewhere that it's a hit and miss.
Apart from the Magisk modules what's the benefit of rooting with Magisk instead of superSU? I saw many people still support superSU than Magisk, does it mean that Magisk has some flows or bugs?
Click to expand...
Click to collapse
I've had no issues passing SafetyNet on my OP3T. It depends on what ROM you're using and if you have any other modifications that Magisk Hide can't hide. Apart from Magisk Hide and systemless modifications Magisk is also open source, if you value that kind of stuff...
There might be apps out there that use specific SuperSU stuff and won't work fully with MagiskSU. I haven't had any issues though (apart from a couple of workarounds, like for Tasker - again, see my signature) and many app developers are starting to make their apps work with MagiskSU as well. Most work out of the box though.

MagiskHide
You can use apps like Android Pay or Snapchat on a rooted device

Didgeridoohan said:
I've had no issues passing SafetyNet on my OP3T. It depends on what ROM you're using and if you have any other modifications that Magisk Hide can't hide. Apart from Magisk Hide and systemless modifications Magisk is also open source, if you value that kind of stuff...
There might be apps out there that use specific SuperSU stuff and won't work fully with MagiskSU. I haven't had any issues though (apart from a couple of workarounds, like for Tasker - again, see my signature) and many app developers are starting to make their apps work with MagiskSU as well. Most work out of the box though.
Click to expand...
Click to collapse
Another noob question, what is the difference between normal and systeless SuperSU?
Considering current known problems Magisk have , isn't it a good idea to use Magisk superSU combo and SuperSU hide?

vipivj said:
Another noob question, what is the difference between normal and systeless SuperSU?
Considering current known problems Magisk have , isn't it a good idea to use Magisk superSU combo and SuperSU hide?
Click to expand...
Click to collapse
Systemless root doesn't alter /system... If you want a more in-depth explanation I'm sure your friend Google can explain it to you.
For OP3T on OxygenOS (I'm currently on 4.1.3) I've not experienced any issues with Magisk. I don't know what those "currently known problems" are that you're worried about...

Didgeridoohan said:
Systemless root doesn't alter /system... If you want a more in-depth explanation I'm sure your friend Google can explain it to you.
For OP3T on OxygenOS (I'm currently on 4.1.3) I've not experienced any issues with Magisk. I don't know what those "currently known problems" are that you're worried about...
Click to expand...
Click to collapse
I meant those issues happens with Tasker etc. Thank you for the answers, you've been very helpful.
I started googling and reading in XDA as well but you know the doubts that comes along ?

vipivj said:
I meant those issues happens with Tasker etc. Thank you for the answers, you've been very helpful.
I started googling and reading in XDA as well but you know the doubts that comes along
Click to expand...
Click to collapse
Ah... Ok. Those kind of issues are easy to work around and the next version of Tasker will have official MagiskSU support.

Use Magisk Manager
I also used Magisk Manager in my old device at it worked fine and as magisk allow you to root Android without effecting on system files I could also install root unsupported apps as well. So i think Magisk is the best solution for you.
link deleted by Moderator due to untrustworthy site will be a help full site to gather more info about magisk from one place.

Topjohnwu has strictly stated that any website which spreads Magisk is not official and cannot be trusted. The only official place is the XDA Thread. If you see any Member promoting an external site related to Magisk, please report the post.

need help!! how to use magisk in xperia M5 E5603

Hello i'm new in the forum :fingers-crossed: i have an xperia m5 E5603 and i try to install magisk so i can use apps that i can't use with a custom ROM my device is already rooted with super su and twrp recovery is installed any help please

Hello and welcome to XDA.
There's a lot of information about how to install Magisk (and how to replace SuperSU with MagiskSU) in this forum already. If you look around you'll find it. Number one rule on XDA is to search before posting (I'm not kidding, look at the rules).
To start you off I can tell you that you need to first uninstall SuperSU. You can do that through the SuperSU app (full unroot, select to restore boot image if you have systemless root), or with the unSU script and then manually flash a stock boot image (you can do this in TWRP). After that you should be able to install Magisk by flashing the zip in TWRP. Since you're new, I'd recommend to stick to the stable v12 release for now.
If you encounter issues, here's a troubleshooting guide for you:
https://forum.xda-developers.com/apps/magisk/magisk-magisk-hide-troubleshooting-tips-t3561828

Didgeridoohan said:
Hello and welcome to XDA.
There's a lot of information about how to install Magisk (and how to replace SuperSU with MagiskSU) in this forum already. If you look around you'll find it. Number one rule on XDA is to search before posting (I'm not kidding, look at the rules).
To start you off I can tell you that you need to first uninstall SuperSU. You can do that through the SuperSU app (full unroot, select to restore boot image if you have systemless root), or with the unSU script and then manually flash a stock boot image (you can do this in TWRP). After that you should be able to install Magisk by flashing the zip in TWRP. Since you're new, I'd recommend to stick to the stable v12 release for now.
If you encounter issues, here's a troubleshooting guide for you:
https://forum.xda-developers.com/apps/magisk/magisk-magisk-hide-troubleshooting-tips-t3561828
Click to expand...
Click to collapse
thank you fo reply after removing super su and install magisk do i need to install super su again for my device to be rooted again ? and is there any recommended version of magisc for my xperia?

Limoneytoo said:
thank you fo reply after removing super su and install magisk do i need to install super su again for my device to be rooted again ? and is there any recommended version of magisc for my xperia?
Click to expand...
Click to collapse
Magisk comes with it's own root, MagiskSU, no need for SuperSU (and for what you seem to want it for, SuperSU isn't compatible). You should probably start by reading through the release thread (the whole thing, it's not that long).
Some Sony devices have issues installing Magisk. This is known... If Magisk v12 doesn't work, you could give the v13.0 beta a go and pay close attention to the info in the TWRP output when flashing. If you do decide to go for the beta, please read through the first post carefully and follow any directions to gather logs to troubleshoot issues.
If you've read through all the info available (I've given you a few good links) and are still having issues, search the support thread for your issue (pretty much everything has already been covered). If you still can't get it going, make sure you post all possible details about your issue and lots of logs (there's also a section about "Asking for help" in the troubleshooting guide I posted earlier).

Didgeridoohan said:
Magisk comes with it's own root, MagiskSU, no need for SuperSU (and for what you seem to want it for, SuperSU isn't compatible). You should probably start by reading through the release thread (the whole thing, it's not that long).
Some Sony devices have issues installing Magisk. This is known... If Magisk v12 doesn't work, you could give the v13.0 beta a go and pay close attention to the info in the TWRP output when flashing. If you do decide to go for the beta, please read through the first post carefully and follow any directions to gather logs to troubleshoot issues.
If you've read through all the info available (I've given you a few good links) and are still having issues, search the support thread for your issue (pretty much everything has already been covered). If you still can't get it going, make sure you post all possible details about your issue and lots of logs (there's also a section about "Asking for help" in the troubleshooting guide I posted earlier).
Click to expand...
Click to collapse
After lot of attemps i always got the same result a bootloop :/ thats happened before when i was trying to install the latest version of super then i release that i can only install an old version of super su but i dont know what version of magisk is recommended for my sony m5

Magisk safety net fails not sure why.

Hi
I'm using a Samsung Galaxy S4
I rooted the stock Samsung rom with SuperSU prior to install Magisk
At first I couldn't install 13.3 I had to install 12.0 because of some unknown reason installing 13.3 I got the error image mount failed same with all previous 13. versions however now 13.3 is now installed and SuperSU isn't installed.
When I run the SafetyNet Check in Magisk it reports:
ctsProfile: false
basicIntegrity: false
I want to be able to use apps like Android pay and such
Can someone please help me with getting this to work
Thanks!

Magisk v12.0 can't pass SafetyNet without workarounds like Universal SafetyNet fix module (and since the last update to SafetyNet a few days ago I've no idea if that works either).
You can't use Magisk to pass SafetyNet with SuperSU installed.
Here's some reading for you:
https://forum.xda-developers.com/apps/magisk/magisk-magisk-hide-troubleshooting-tips-t3561828
Pro tip: Try using the search function and browse the stickied threads before posting. There are very few things that hasn't been covered already in one way or another...

Didgeridoohan said:
Magisk v12.0 can't pass SafetyNet without workarounds like Universal SafetyNet fix module (and since the last update to SafetyNet a few days ago I've no idea if that works either).
You can't use Magisk to pass SafetyNet with SuperSU installed.
Here's some reading for you:
https://forum.xda-developers.com/apps/magisk/magisk-magisk-hide-troubleshooting-tips-t3561828
Pro tip: Try using the search function and browse the stickied threads before posting. There are very few things that hasn't been covered already in one way or another...
Click to expand...
Click to collapse
I've got 13.3 installed and SuperSU isn't installed plus I've already read a lot on this subject and most of my searches did nothing for me that's why I thought I would make a thread to see if anyone could help me.

AyanamiRei0 said:
I've got 13.3 installed and SuperSU isn't installed plus I've already read a lot on this subject and most of my searches did nothing for me that's why I thought I would make a thread to see if anyone could help me.
Click to expand...
Click to collapse
That was not very clear from your first post...
If you haven't already, start by reading through the link I posted. You wan't post #4.

Didgeridoohan said:
That was not very clear from your first post...
If you haven't already, start by reading through the link I posted. You wan't post #4.
Click to expand...
Click to collapse
Interesting trying to start magiskhide manually does nothing.

You could have remnants of Su on your phone. Even if you use the full uninstall method you can have leftovers. Tried a complete fresh reinstall?

phuhcue said:
You could have remnants of Su on your phone. Even if you use the full uninstall method you can have leftovers. Tried a complete fresh reinstall?
Click to expand...
Click to collapse
Oh it's working fine now installing Lineage OS and then install Magisk and it works perfectly.

With me my experiments with magisk in the past left some files in my data partition behind which makes safetynet fail.
I found them by going into twrp recovery, starting and adb shell and then executing find . | grep -i magisk
the two files i found were:
data/data/com.google.android.gms/files/backup_diff_script/com.topjohnwu.magisk
data/property/persist.magisk.hide
i deleted them with rm and safety net worked again.
So I can confirm that for my phone, unlocked bootloader, custom modem and custom recovery does not matter at all. But if your filesystem still contains traces of magisk, is a nono for google safetynet, pretty silly this road they are taking here.

safety net
i have the same problem on galaxy note 3 with magisk 15.3 on my galaxy s7 everything is ok but in note 3 i have safety net false...
can anyone help me?

spanpana said:
i have the same problem on galaxy note 3 with magisk 15.3 on my galaxy s7 everything is ok but in note 3 i have safety net false...
can anyone help me?
Click to expand...
Click to collapse
Old device... If the kernel version is lower than 3.8 it'll likely not have support for mount namespace and MagiskHide won't work. A custom kernel or ROM might work...

Didgeridoohan said:
Old device... If the kernel version is lower than 3.8 it'll likely not have support for mount namespace and MagiskHide won't work. A custom kernel or ROM might work...
Click to expand...
Click to collapse
thank's for your reply...!
i have custom rom resurection remix v.5.8.2 but i didnt change the kernel can you explain me how to do that please because i don't know...?

spanpana said:
thank's for your reply...!
i have custom rom resurection remix v.5.8.2 but i didnt change the kernel can you explain me how to do that please because i don't know...?
Click to expand...
Click to collapse
Check your kernel version first (usually found in Settings - About Phone). If it's less than 3.8, ask for help in your device's forum for if there's any custom kernels or ROMs available with an updated kernel.

Didgeridoohan said:
Check your kernel version first (usually found in Settings - About Phone). If it's less than 3.8, ask for help in your device's forum for if there's any custom kernels or ROMs available with an updated kernel.
Click to expand...
Click to collapse
ok my friend thank you very much...!:laugh::good:

Didgeridoohan said:
Old device... If the kernel version is lower than 3.8 it'll likely not have support for mount namespace and MagiskHide won't work. A custom kernel or ROM might work...
Click to expand...
Click to collapse
That's interesting. I get the same message on my old phone (running the 3.4.113 kernel), but I'm unable to even open Mario Run if MagiskHide is disabled. But when it's enabled, the game runs just fine. Is that normal? I thought Mario Run made use of SafetyNet... I'm using microG + DroidGuard Helper. I've tried running Android Pay, but I get this error message. But I'm not even sure if Android Pay is supposed to work since I'm using microG... What other apps use SafetyNet so I can try them?
Thanks.

robotsrules said:
That's interesting. I get the same message on my old phone (running the 3.4.113 kernel), but I'm unable to even open Mario Run if MagiskHide is disabled. But when it's enabled, the game runs just fine. Is that normal? I thought Mario Run made use of SafetyNet... I'm using microG + DroidGuard Helper. I've tried running Android Pay, but I get this error message. But I'm not even sure if Android Pay is supposed to work since I'm using microG... What other apps use SafetyNet so I can try them?
Thanks.
Click to expand...
Click to collapse
MagiskHide can't do it's thing to hide itself on such an old kernel, but it can still hide sensitive prop values. That's why Mario Run works... IIRC it looks for ro.debuggable, on of the props changed to "safe" values by MagiskHide.

Didgeridoohan said:
MagiskHide can't do it's thing to hide itself on such an old kernel, but it can still hide sensitive prop values. That's why Mario Run works... IIRC it looks for ro.debuggable, on of the props changed to "safe" values by MagiskHide.
Click to expand...
Click to collapse
Oh, I get it now... Thanks

Disable Xposed Modules while Bootloop.

Hello
Flashed Xposed via Magisk Manager.
Tried several modules which worked until i got some outdated and now my phone is in bootloop.
Anyone know how i can deactivate Xposed?
Already tried the Xposed Disabler Zip and tried to delete the module list which doesn't exist on my phone.
I think thats cause i got "systemless Xposed".
What should i do now ? Maybe uninstalling Magisk so Xposed doesnt work anymore?
Thanks

Nico1300 said:
Hello
Flashed Xposed via Magisk Manager. Tried several modules which worked until i got some outdated and now my phone is in bootloop......
Click to expand...
Click to collapse
I don't use Magisk myself but, your best bet is to post this question within the following Magisk XPosed thread.
https://forum.xda-developers.com/showthread.php?t=3388268
If all else fails, and you don't receive any responses (within a reasonable amount of time) from the above thread, your next best bet is to ask for some member guidance within the following Magisk General Q&A thread.
https://forum.xda-developers.com/showthread.php?t=3432382
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.

Nico1300 said:
Hello
Flashed Xposed via Magisk Manager.
Tried several modules which worked until i got some outdated and now my phone is in bootloop.
Anyone know how i can deactivate Xposed?
Already tried the Xposed Disabler Zip and tried to delete the module list which doesn't exist on my phone.
I think thats cause i got "systemless Xposed".
What should i do now ? Maybe uninstalling Magisk so Xposed doesnt work anymore?
Thanks
Click to expand...
Click to collapse
Uninstalling magisk won"t help you much
Link below might help you out.
If modules are outdated or not working properly it would cause issues whether systemless or not.
https://www.didgeridoohan.com/magisk/MagiskModuleIssues
Sent from my Samsung Galaxy S8 using XDA Labs

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