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 likely 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. Mounting /system rw may even be impossible on Android 10+ devices. See "Can't edit system file" below.

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).

Superuser request prompt does not show

If the prompt to grant superuser access does not show on your device, first make sure that the setting for "Automatic Response" for superuser in the Magisk app settings is set to "Prompt". If it is and there still is no popup, check your Android settings. Some OEMs have a setting that you have to enable to allow background processes to display a popup window.

Or, the app simply can't detect root with Magisk (see above).

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 props like and ro.debuggable to their original values (userdebug and 1 respectively), and 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.

If your ROM is a "user" or "release" version, changing these values won't automatically enable adb root. It all depends on your ROM, so you'd have to ask there.

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/ /data/adb/service.d/

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

Magisk root detection has been fixed in Tasker v5.2. Previous to this version, there were issues with root detection if the app 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 an easy way of getting around that. 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, but this should be the last resort since it might be tricky mounting them rw.

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.

If you have a system that cannot be mounted rw but you really want to do things the old-fashioned way, you can use XDA Senior Member lebigmac's Universal Mount System read write script to change the partitions to being writable. You'll find it here:

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 Magisk app reporting that "Magisk is not installed".

This may be caused by memory management where the Magisk app will not be kept in memory and as a result root management is lost. This can sometimes be fixed by clearing the app from memory (swipe it away from recent apps list) and opening it again. Make sure the app is removed from any battery optimisation.

Other reasons for this issue include a failed update and having the Magisk app 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.

Magisk app was denied superuser access

Sounds weird, huh? How could the app responsible for superuser access suddenly be denied? The answer: it is very likely that you have two apps installed, one hidden and one not. See "There are two Magisk apps" for details on how to solve this.

If you do not find a second app, try deleting the Magisk database file (/data/adb/magisk.db). This will reset everything (including which apps have been given superuser access and the MagiskHide list) and you should be able to use the Magisk app again (you might have to uninstall it and install the apk again).
Valid XHTML :: Valid CSS: :: Powered by WikkaWiki