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. Contact the developer.

You can try symlinking the su binary to the location where the troublesome app is looking for it. You'll 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.

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 (which would be a systemless modification).

ADB cannot run as root in production builds

If you're having issues running the ADB root command after installing Magisk this is because of MagiskHide setting a few prop values to known "safe" values. You can get ADB root working again by turning of MagiskHide and rebooting, but if you need MagiskHide for some app or service this could quickly become annoying.

A more convenient solution is to reset ro.build.type and ro.debuggable to their original values (userdebug and 1 respectively), or possibly other props that MagiskHide alters (it sometimes depends on what ROM you're using). This can be done by using the Magisk resetprop tool (see the Magisk Documentation for details), either by running it directly in a terminal emulator, in a late_start service boot script, or by using the MagiskHide Props Config Magisk module's "Edit MagiskHide props" function.

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 boot script to service.d):
su -c cp /sdcard/testscript.sh /data/adb/service.d/testscript.sh


If the command doesn’t work, try putting quotation marks around the command, like so:
su -c "cp /sdcard/testscript.sh /data/adb/service.d/testscript.sh”


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.

Can't edit system files

From Android 9 a lot has changed in Android, and if you can't edit system files anymore it is not because root is broken or not fully working.

On some system-as-root (SAR) devices you can no longer mount the system partition as read-write and doing systemless modifications through Magisk is the only way. If you do want to do actual edits of the system, and if it is even possible (from Android 10 it's actually impossible on some devices), you need to mount the root directory, /, as rw and not /system. You can also try editing the partition mirrors that Magisk keeps in /sbin/.magisk/mirror.

From v20.0, Magisk is also following the design laid down by Google, which is why you might suddenly start to experience this "issue" after updating from earlier Magisk versions.

For more info on how Magisk v20+ deals with SAR, take a look at the Magisk v20.0 release notes.

Randomly losing root

Some devices seem to have issues with loosing root randomly and the Manager reporting that "Magisk is not installed".

This may be caused by 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.

Other reasons for this issue include a failed update and having the Manager installed to external/adoptable storage

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