Revision history for MagiskRootIssues


Revision [756]

Last edited on 2019-10-25 12:22:50 by didgeridoohan
Additions:
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.
Deletions:
On many 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 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.


Revision [755]

Edited on 2019-10-25 12:18:02 by didgeridoohan
Additions:
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.


Revision [754]

Edited on 2019-10-22 00:06:54 by didgeridoohan
Additions:
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.
Deletions:
From Android 10 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.


Revision [752]

Edited on 2019-10-17 16:25:17 by didgeridoohan
Additions:
For more info on how Magisk v20+ deals with SAR, take a look at the [[https://github.com/topjohnwu/magisk_files/blob/2d7ddefbe4946806de1875a18247b724f5e7d4a0/notes.md#new-system-as-root-implementation | Magisk v20.0 release notes]].


Revision [748]

Edited on 2019-10-16 06:46:43 by didgeridoohan
Additions:
===**Can't edit system files**===
From Android 10 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 many 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 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.


Revision [733]

Edited on 2019-10-15 15:40:04 by didgeridoohan
Deletions:
@@{{image url="https://img.shields.io/badge/-PayPal-blue.svg" title="" alt="PayPal"}}
Please don't hesitate to [[https://www.paypal.me/didgeridoohan | support the work involved]] in keeping this guide alive.@@
----


Revision [683]

Edited on 2019-07-27 15:54:35 by didgeridoohan
Additions:
Other reasons for this issue include a [[MagiskUpdating | failed update]] and having the [[MagiskIssues | Manager installed to external/adoptable storage]]


Revision [675]

Edited on 2019-07-27 06:46:55 by didgeridoohan
Additions:
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.
Deletions:
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.


Revision [661]

Edited on 2019-07-22 14:28:02 by didgeridoohan
Additions:
@@{{image url="https://img.shields.io/badge/-PayPal-blue.svg" title="" alt="PayPal"}}
Please don't hesitate to [[https://www.paypal.me/didgeridoohan | support the work involved]] in keeping this guide alive.@@
----


Revision [622]

Edited on 2019-05-27 03:39:00 by didgeridoohan
Additions:
===**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). This can be done by using the Magisk resetprop tool (see the [[https://topjohnwu.github.io/Magisk/ | Magisk Documentation]] for details), either by running it directly in a terminal emulator, in a late_start service [[https://topjohnwu.github.io/Magisk/guides.html#boot-scripts | boot script]], or by using the [[https://forum.xda-developers.com/apps/magisk/module-magiskhide-props-config-t3789228 | MagiskHide Props Config]] Magisk module's "Edit MagiskHide props" function.


Revision [541]

Edited on 2018-12-16 15:34:25 by didgeridoohan
Additions:
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 [[https://topjohnwu.github.io/Magisk/guides.html#scripts | boot script]] to service.d):
Deletions:
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):


Revision [522]

Edited on 2018-12-09 04:14:24 by didgeridoohan
Additions:
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%%
%%su -c "cp /sdcard/testscript.sh /data/adb/service.d/testscript.sh”%%
Deletions:
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%%
%%su -c "cp /sdcard/hosts /magisk/.core/hosts”%%


Revision [420]

Edited on 2018-09-04 01:54:10 by didgeridoohan
Additions:
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 [[https://github.com/topjohnwu/Magisk/blob/master/docs/modules.md | Magisk module]] that places the symlink in the appropriate location (which would be a systemless modification).
Deletions:
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 [[https://github.com/topjohnwu/Magisk/blob/master/docs/modules.md | Magisk module]] that places the symlink in the appropriate location.


Revision [419]

Edited on 2018-09-04 01:53:27 by didgeridoohan
Additions:
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.//
Deletions:
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.**


Revision [418]

Edited on 2018-09-04 01:53:13 by didgeridoohan
Additions:
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:
Deletions:
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:
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.


Revision [398]

Edited on 2018-08-26 09:45:33 by didgeridoohan
Additions:
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.


Revision [397]

Edited on 2018-08-26 02:13:20 by didgeridoohan
Additions:
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 [[https://forum.xda-developers.com/showpost.php?p=71862904&postcount=12243 | this Magisk module]] to enable Tasker root support. Reportedly, Secure Settings will also function with MagiskSU thanks to this module.
Deletions:
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 [[https://forum.xda-developers.com/showpost.php?p=71862904&postcount=12243 | this Magisk module]] to enable Tasker root support. Reportedly, Secure Settings will also function with MagiskSU thanks to this module.


Revision [327]

Edited on 2018-07-19 09:33:32 by didgeridoohan
Additions:
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 [[https://github.com/topjohnwu/Magisk/blob/master/docs/modules.md | Magisk module]] that places the symlink in the appropriate location.
Deletions:
Please note that doing this might have the effect of MagiskHide not being able to hide root.


Revision [326]

Edited on 2018-07-19 09:32:10 by didgeridoohan
Additions:
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%%
%%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.
Deletions:
Another way is to use “Run Shell” in Tasker and use shell commands to do what you want, prefaced by “/sbin/su -c”. Example (copy a new host file to Magisk):
%%/sbin/su -c cp /sdcard/hosts /magisk/.core/hosts%%
%%/sbin/su -c "cp /sdcard/hosts /magisk/.core/hosts”%%
If you’re using Tasker v5+ and it still can’t detect that your rooted with MagiskSU, it’s probably because you’ve hidden the Magisk Manager. Tasker looks for the Magisk Manager and uses this to know if you’re rooted or not. When the Manager is hidden, Tasker can’t find it and doesn’t know that your device is rooted. Use the “su -c” workaround mentioned above.


Revision [215]

Edited on 2018-03-01 03:00:13 by didgeridoohan
Deletions:
===**""MagiskSU"" doesn’t remember superuser access**===
Some devices have issues with the superuser database. You’ll probably see error lines in the log about sqlite3. It’s possible that this could be fixed by uninstalling and reinstalling the Manager. Do this from within the Manager by pressing “Uninstall” and then “Uninstall App”. If that doesn’t work, use the latest [[https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 | Magisk uninstall zip]] or do a comlete uninstall through the Manager //(“Uninstall” -> “Complete Uninstall”)//. If it still doesn’t work, provide logs… //(also see [[MagiskHelp | "Asking for help/reporting bugs"]])//.
===**""MagiskSU"" doesn’t work**===
If superuser access doesn’t work, there are probably issues with the superuser db //(also see “MagiskSU doesn’t remember superuser access” above)//. One of these issues might be a faulty implementation of f2fs. //See [[MagiskIssues | “Issues with f2fs”]]//.


Revision [184]

The oldest known version of this page was created on 2018-02-05 15:38:39 by didgeridoohan
Valid XHTML :: Valid CSS: :: Powered by WikkaWiki