Revision [398]

This is an old revision of MagiskRootIssues made by didgeridoohan on 2018-08-26 09:45:33.


Root issues

<insert app name here> can’t detect root

Some apps may have troubles detecting root when using Magisk. Usually this means the app in question is looking for root in a specific location and needs to be updated to work with MagiskSU or otherwise can’t detect MagiskSU.

You can try symlinking the su binary to the location where the troublesome app is looking for it. Here’s an example on how to do this in terminal:
ln -s /sbin/su /system/xbin/su

Please note that doing this might have the effect of MagiskHide not being able to hide root. A workaround for this would be to make a Magisk module that places the symlink in the appropriate location.

You'll likely also need to mount /system rw to be able to create the symlink. This will alter your system partition and you will not be able to update through an OTA afterwards. If you need to keep /system intact and untouched, don't use this method.

Tasker and MagiskSU

Any version before Tasker v5.0 will have issues detecting MagiskSU. If you by any chance feel that you cannot update to v5+, you can use this Magisk module to enable Tasker root support. Reportedly, Secure Settings will also function with MagiskSU thanks to this module.

Another way is to use “Run Shell” in Tasker and use shell commands to do what you want, prefaced by “su -c”. Example (copy a new host file to Magisk):
su -c cp /sdcard/hosts /magisk/.core/hosts

If the command doesn’t work, try putting quotation marks around the command, like so:
su -c "cp /sdcard/hosts /magisk/.core/hosts”

Magisk root detection has been fixed in Tasker v5.2. Previous to this version, there were issues with root detection if the Manager was hidden, but that should now be fixed. If you're still having issues with root and tasker, try the “su -c” workaround mentioned above.

Randomly losing root

Some devices seem to have issues with memory management where the Magisk Manager will not be kept in memory and as a result root management is lost. This can sometimes be fixed by clearing the Manager from memory (swipe it away from recent apps list) and opening it again. Make sure the Manager is removed from any battery optimisation.

If you can't find any way to get around this issue, try to capture a logcat of it actually happening (also see "Asking for help/reporting bugs") and post that together with a detail description in the general support thread. This is a recurring issue for some users and so far there have been very few useful logs provided.
Valid XHTML :: Valid CSS: :: Powered by WikkaWiki