Revision history for MagiskIssues


Revision [1016]

Last edited on 2021-03-20 02:31:29 by didgeridoohan
Additions:
Some devices might need a more hands-on approach to disable dm-verity, or the device will bootloop when installing Magisk. See //[[MagiskInstallationIssues | Working with dm-verity and forced encryption]]// for more details.
Deletions:
Some devices might need a more hands-on approach to disable dm-verity, or the device will bootloop when installing Magisk. See //[[MagiskInstallationIssues | Working with dm-verity and forced encryption]] for more details.

Revision [1014]

Edited on 2021-03-20 02:27:00 by didgeridoohan
Additions:
If you end up in a bootloop when installing Magisk, flash the [[https://github.com/topjohnwu/Magisk/releases | Magisk app renamed to uninstall.zip]] in recovery (you migth also have to flash a clean boot image, which will help if there's something wrong with the boot image on your device) and start over. If the uninstaller fails or you do not have access to a custom recovery on your device, just flash your unmodified copy of the boot image and you should be good to go. There will probably be some leftover files and folders from Magisk laying around in /cache and /data/adb, but that shouldn't be an issue.
Some devices might need a more hands-on approach to disable dm-verity, or the device will bootloop when installing Magisk. See //[[MagiskInstallationIssues | Working with dm-verity and forced encryption]] for more details.
Deletions:
If you end up in a bootloop when installing Magisk, flash the [[https://github.com/topjohnwu/Magisk/releases | Magisk app renamed to uninstall.zip] in recovery (you migth also have to flash a clean boot image, which will help if there's something wrong with the boot image on your device) and start over. If the uninstaller fails or you do not have access to a custom recovery on your device, just flash your unmodified copy of the boot image and you should be good to go. There will probably be some leftover files and folders from Magisk laying around in /cache and /data/adb, but that shouldn't be an issue.

Revision [982]

Edited on 2021-02-23 08:32:38 by didgeridoohan

No Differences

Revision [981]

Edited on 2021-02-23 08:32:12 by didgeridoohan

No Differences

Revision [980]

Edited on 2021-02-23 08:32:02 by didgeridoohan
Additions:
If you end up in a bootloop when installing Magisk, flash the [[https://github.com/topjohnwu/Magisk/releases | Magisk app renamed to uninstall.zip] in recovery (you migth also have to flash a clean boot image, which will help if there's something wrong with the boot image on your device) and start over. If the uninstaller fails or you do not have access to a custom recovery on your device, just flash your unmodified copy of the boot image and you should be good to go. There will probably be some leftover files and folders from Magisk laying around in /cache and /data/adb, but that shouldn't be an issue.
After installing Magisk, if the app still reports that Magisk is not installed, check if the app has been installed to the external or adoptable storage. This is known to cause all kinds of issues, so make sure that the app is installed to the internal storage and check again.
This might also be happen when the Magisk app update doesn't go as planned and you end up with two app installed or the app doesn't actually update. Something that might lead to issues... See [[ManagerIssues | "There are two Magisk apps"]] or [[MagiskUpdating | "Magisk not installed"]] for further details.
Deletions:
If you end up in a bootloop when installing Magisk, flash the [[https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 | Magisk uninstaller zip]] in recovery (you migth also have to flash a clean boot image, which will help if there's something wrong with the boot image on your device) and start over. If the uninstaller fails or you do not have access to a custom recovery on your device, just flash your unmodified copy of the boot image and you should be good to go. There will probably be some leftover files and folders from Magisk laying around in /cache and /data/adb, but that shouldn't be an issue.
After installing Magisk, if the Manager still reports that Magisk is not installed, check if the Manager has been installed to the external or adoptable storage. This is known to cause all kinds of issues, so make sure that the Manager is installed to the internal storage and check again.
This might also be happen when the Magisk Manager update doesn't go as planned and you end up with two Managers installed or the Manager doesn't actually update. Something that might lead to issues... See [[ManagerIssues | "There are two Managers"]] or [[MagiskUpdating | "Magisk not installed"]] for further details.

Revision [953]

Edited on 2020-11-20 04:53:30 by didgeridoohan
Additions:
If you end up in a bootloop when installing Magisk, flash the [[https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 | Magisk uninstaller zip]] in recovery (you migth also have to flash a clean boot image, which will help if there's something wrong with the boot image on your device) and start over. If the uninstaller fails or you do not have access to a custom recovery on your device, just flash your unmodified copy of the boot image and you should be good to go. There will probably be some leftover files and folders from Magisk laying around in /cache and /data/adb, but that shouldn't be an issue.
Deletions:
If you end up in a bootloop when installing Magisk, flash the [[https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 | Magisk uninstaller zip]] in recovery (you migth also have to flash a clean boot image, which will help if there's something wrong with the boot image on your device) and start over. If the uninstaller fails or you do not have access to a custom recovery on your device, just flash your unmodified copy of the boot image and you should be good to go. There’ll probably be some leftover files and folders from Magisk laying around in /cache and /data/adb, but that shouldn't be an issue.

Revision [920]

Edited on 2020-11-03 02:54:59 by didgeridoohan
Additions:
==**Android 11**==
Bootloop on Android 11 is also often caused by having TWRP installed (just as above). Boot it, don't install.

Revision [919]

Edited on 2020-11-03 02:52:40 by didgeridoohan
Additions:
If you end up in a bootloop when installing Magisk, flash the [[https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 | Magisk uninstaller zip]] in recovery (you migth also have to flash a clean boot image, which will help if there's something wrong with the boot image on your device) and start over. If the uninstaller fails or you do not have access to a custom recovery on your device, just flash your unmodified copy of the boot image and you should be good to go. There’ll probably be some leftover files and folders from Magisk laying around in /cache and /data/adb, but that shouldn't be an issue.
Another big cause for bootloops are modules that are incompatible with your device/system. Keep reading below.
Another thing to try if your device ends up in a bootloop when flashing Magisk, is to keep dm-verity and force encrypt enabled (be very careful when working with modern Android devices though, you might cause more issues). By default Magisk might remove these flags from your boot image which on some setups have been reported to cause a bootloop. See [[MagiskInstallationIssues | "Working with dm-verity and forced encryption"]] for more details.
Deletions:
If you end up in a bootloop when installing Magisk, flash the [[https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 | Magisk uninstaller zip]] in recovery (you migth also have to flash a clean boot image, which will help if there's something wrong with the boot image on your device) and start over. If the uninstaller fails, just flash your unmodified copy of the boot image and you should be good to go. There’ll probably be some leftover files and folders from Magisk laying around in /cache and /data/adb, but these can be removed manually.
Another thing to try if your device ends up in a bootloop when flashing Magisk, is to keep dm-verity and force encrypt enabled. By default Magisk might remove these flags from your boot image which on some setups have been reported to cause a bootloop. Keeping these flags is done by running the two following commands in your recovery's terminal before flashing the Magisk zip (or, if you're upgrading from a working version of Magisk, by checking the two options in the Magisk Manager before installing):
%%echo KEEPVERITY=true>>/data/.magisk
echo KEEPFORCEENCRYPT=true>>/data/.magisk%%
Also see //[[MagiskInstallationIssues | "Keeping/Disabling dm-verity and forced encryption"]]//.

Revision [793]

Edited on 2020-01-29 04:38:07 by didgeridoohan
Additions:
Also see //[[MagiskInstallationIssues | "Keeping/Disabling dm-verity and forced encryption"]]//.

Revision [753]

Edited on 2019-10-19 16:40:37 by didgeridoohan
Additions:
If your device bootloops after installing a Magisk module, or after updating your device (there might be an incompatible module installed), see //[[https://www.didgeridoohan.com/magisk/MagiskModuleIssues#hn_Module_causing_issues_Magisk_functionality_bootloop_loss_of_root_etc | "Module causing issues"]].//
Deletions:
If your device bootloops after installing a Magisk module, or after updating your device (there might be an incompatible module installed), see [[https://www.didgeridoohan.com/magisk/MagiskModuleIssues#hn_Module_causing_issues_Magisk_functionality_bootloop_loss_of_root_etc | "Module causing issues"]].//

Revision [736]

Edited on 2019-10-15 15:41:15 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 [722]

Edited on 2019-10-12 05:34:50 by didgeridoohan
Additions:
==**Bootloop after module installation or device update**==
If your device bootloops after installing a Magisk module, or after updating your device (there might be an incompatible module installed), see [[https://www.didgeridoohan.com/magisk/MagiskModuleIssues#hn_Module_causing_issues_Magisk_functionality_bootloop_loss_of_root_etc | "Module causing issues"]].//
Deletions:
If your device bootloops installing a Magisk module, or after updating your device (there might be an incompatible module installed), see [[https://www.didgeridoohan.com/magisk/MagiskModuleIssues#hn_Module_causing_issues_Magisk_functionality_bootloop_loss_of_root_etc | "Module causing issues"]].//

Revision [721]

Edited on 2019-10-12 05:33:29 by didgeridoohan
Additions:
If you end up in a bootloop when installing Magisk, flash the [[https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 | Magisk uninstaller zip]] in recovery (you migth also have to flash a clean boot image, which will help if there's something wrong with the boot image on your device) and start over. If the uninstaller fails, just flash your unmodified copy of the boot image and you should be good to go. There’ll probably be some leftover files and folders from Magisk laying around in /cache and /data/adb, but these can be removed manually.
If your device bootloops installing a Magisk module, or after updating your device (there might be an incompatible module installed), see [[https://www.didgeridoohan.com/magisk/MagiskModuleIssues#hn_Module_causing_issues_Magisk_functionality_bootloop_loss_of_root_etc | "Module causing issues"]].//
Deletions:
If you end up in a bootloop when installing Magisk, flash the [[https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 | Magisk uninstaller zip]] in recovery (you migth also have to flash a clean boot image, which will help if there's something wrong with the boot image on your device) and start over //(for bootloops occurring after installing a Magisk module, see [[https://www.didgeridoohan.com/magisk/MagiskModuleIssues#hn_Module_causing_issues_Magisk_functionality_bootloop_loss_of_root_etc | "Module causing issues"]])//. If the uninstaller fails, just flash your unmodified copy of the boot image and you should be good to go. There’ll probably be some leftover files and folders from Magisk laying around in /cache and /data/adb, but these can be removed manually.

Revision [705]

Edited on 2019-08-06 14:44:55 by didgeridoohan
Additions:
If your Wifi stops working after installing Magisk and you're using a custom kernel, try reflashing said kernel.
Deletions:
If your Wifi stops working after installing Magisk, try reflashing your kernel.

Revision [681]

Edited on 2019-07-27 06:58:42 by didgeridoohan
Additions:
Some users seems to experience this issue randomly, where Magisk seems to uninstall by itself. See [[RootIssues | "Randomly losing root"]] for more details.
Deletions:
Some users seems to experience this issue randomly, where Magisk seems to uninstall by itself. See [[RootIssues | "Randomly loosing root"]] for more details.

Revision [680]

Edited on 2019-07-27 06:58:22 by didgeridoohan
Additions:
Some users seems to experience this issue randomly, where Magisk seems to uninstall by itself. See [[RootIssues | "Randomly loosing root"]] for more details.
Deletions:
Some users seems to experience this issue randomly, where Magisk seems to uninstall by itself. See [[MagiskIssues | "Randomly loosing root"]] for more details.

Revision [678]

Edited on 2019-07-27 06:54:11 by didgeridoohan
Additions:
This might also be happen when the Magisk Manager update doesn't go as planned and you end up with two Managers installed or the Manager doesn't actually update. Something that might lead to issues... See [[ManagerIssues | "There are two Managers"]] or [[MagiskUpdating | "Magisk not installed"]] for further details.
Some users seems to experience this issue randomly, where Magisk seems to uninstall by itself. See [[MagiskIssues | "Randomly loosing root"]] for more details.
Deletions:
This might also be happen when the Magisk Manager update doesn't go as planned and you end up with two Managers installed or the Manager doesn't actually update. Something that might lead to issues... See [[ManagerIssues | "There are two Managers"]] or [[MagiskUpdate | "Magisk not installed"]] for further details.
Some users seems to experience this issue randomly, where Magisk seems to uninstall by itself. See //[[MagiskIssues | "Randomly loosing root"]]// for more details.

Revision [677]

Edited on 2019-07-27 06:53:18 by didgeridoohan
Additions:
Some users seems to experience this issue randomly, where Magisk seems to uninstall by itself. See //[[MagiskIssues | "Randomly loosing root"]]// for more details.
Deletions:
Some users seems to experience this issue randomly, where Magisk seems to uninstall by itself. See //[MagiskIssues | "Randomly loosing root"]]// for more details.

Revision [676]

Edited on 2019-07-27 06:52:52 by didgeridoohan
Additions:
Some users seems to experience this issue randomly, where Magisk seems to uninstall by itself. See //[MagiskIssues | "Randomly loosing root"]]// for more details.

Revision [658]

Edited on 2019-07-22 14:26:51 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 [625]

Edited on 2019-05-27 07:01:41 by didgeridoohan
Additions:
In the Magisk log you'll sometimes see """---------"" beginning of crash". This is perfectly normal and unless you experience issues with Magisk it is nothing to worry about. Since Magisk uses Android's logcat for collecting logs this will appear in the log as soon as there is any kind of crash occuring on your device, regardless if it has anything to do with Magisk or not.
Deletions:
In the Magisk log you'll sometimes see "--------- beginning of crash". This is perfectly normal and unless you experience issues with Magisk it is nothing to worry about. Since Magisk uses Android's logcat for collecting logs this will appear in the log as soon as there is any kind of crash occuring in your system, regardless if it has anything to do with Magisk or not.

Revision [624]

Edited on 2019-05-27 07:00:23 by didgeridoohan
Additions:
===**Beginning of crash**===
In the Magisk log you'll sometimes see "--------- beginning of crash". This is perfectly normal and unless you experience issues with Magisk it is nothing to worry about. Since Magisk uses Android's logcat for collecting logs this will appear in the log as soon as there is any kind of crash occuring in your system, regardless if it has anything to do with Magisk or not.

Revision [607]

Edited on 2019-05-02 02:48:28 by didgeridoohan
Additions:
A bootloop might also be because you’ve installed a module that Magic Mounts new files or folders to the root of /system, etc. On some devices this will cause a bootloop. Contact the creator of the module you’re trying to install and let them know… //Also see [[MagiskModuleIssues | "Module Issues"]]//.
This might also be happen when the Magisk Manager update doesn't go as planned and you end up with two Managers installed or the Manager doesn't actually update. Something that might lead to issues... See [[ManagerIssues | "There are two Managers"]] or [[MagiskUpdate | "Magisk not installed"]] for further details.
If your system suddenly becomes unstable, with reboots and system processes stopping, make sure you haven't added any system apps or processes to the MagiskHide list. Because of the way MagiskHide works, it might kill off some pretty important parts of the running system if this kind of apps/processes are on the list, causing all kinds of havok.
Deletions:
A bootloop might also be because you’ve installed a module that Magic Mounts new files or folders to the root of /system. On some devices this will cause a bootloop. Contact the creator of the module you’re trying to install and let them know… //Also see [[MagiskModuleIssues | "Module Issues"]]//.
This might also be happen when the Magisk Manager update doesn't go as planned and you end up with two Managers installed. Something that might lead to issues... See [[ManagerIssues | "There are two Managers"]] for further details.
If your system suddenly becomes unstable, with reboots and system processes stopping, make sure you haven't added any system apps or processes to the MagiskHide list. Because of the way MagiskHide works, it will kill off some pretty important parts of the running system if this kind of apps/processes are on the list, causing all kinds of havok.

Revision [593]

Edited on 2019-02-19 12:27:08 by didgeridoohan
Additions:
This might also be happen when the Magisk Manager update doesn't go as planned and you end up with two Managers installed. Something that might lead to issues... See [[ManagerIssues | "There are two Managers"]] for further details.
Deletions:
This might also be caused by updating the Manager while it is repackaged with a random package name. If the update doesn't go right, you might end up with two Managers installed, which will lead to issues... Also see [[ManagerIssues | "There are two Managers"]].

Revision [592]

Edited on 2019-02-19 12:25:19 by didgeridoohan
Additions:
This might also be caused by updating the Manager while it is repackaged with a random package name. If the update doesn't go right, you might end up with two Managers installed, which will lead to issues... Also see [[ManagerIssues | "There are two Managers"]].

Revision [564]

Edited on 2019-01-16 02:26:32 by didgeridoohan
Additions:
Many users are reporting about bootloops on Pixel and other A/B devices. Often this is caused by having TWRP installed at the same time as installing Magisk. Since the recovery now resides in the boot image, having these two modifications to the same partition may cause issues. If you want to use TWRP, use fastboot to only __boot__ it, don't install:
Deletions:
Many users are reporting about bootloops on Pixel devices. Often this is caused by having TWRP installed at the same time as installing Magisk. Since the recovery now resides in the boot image, having these two modifications to the same partition may cause issues. If you want to use TWRP, use fastboot to only __boot__ it, don't install:

Revision [563]

Edited on 2019-01-16 02:26:08 by didgeridoohan
Additions:
==**A/B devices (Pixel, etc)**==
Many users are reporting about bootloops on Pixel devices. Often this is caused by having TWRP installed at the same time as installing Magisk. Since the recovery now resides in the boot image, having these two modifications to the same partition may cause issues. If you want to use TWRP, use fastboot to only __boot__ it, don't install:
%%fastboot boot twrp.img%%

Revision [550]

Edited on 2018-12-22 02:54:09 by didgeridoohan
Deletions:
===**Issues with f2fs**===
There are many devices that have a faulty implementation of f2fs. These may include Motorola, Lenovo and others. These devices can’t mount the Magisk image properly leading to issues with module installation and possibly superuser access. You might see something like this in the Magisk log:
%%mount /dev/block/loop0->/sbin/.magisk/img failed with 13: Permission denied%%
Finding a kernel with the f2fs bug fixed is one solution and if possible probably the best one. Formating your /data partition as ext4 is another, but some devices won’t be able to boot if /data isn’t formated with f2fs. There’s also the [[https://forum.xda-developers.com/apps/magisk/guide-magisk-official-version-including-t3577875 | F2FS Loopback Bug Workaround module]] by [[https://forum.xda-developers.com/member.php?u=5228676 | VR25]] that you can try. It moves the Magisk image to the /cache partition instead of /data and may solve issues like this (won't work if /cache is f2fs).

Revision [546]

Edited on 2018-12-19 07:14:20 by didgeridoohan
Additions:
If you end up in a bootloop when installing Magisk, flash the [[https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 | Magisk uninstaller zip]] in recovery (you migth also have to flash a clean boot image, which will help if there's something wrong with the boot image on your device) and start over //(for bootloops occurring after installing a Magisk module, see [[https://www.didgeridoohan.com/magisk/MagiskModuleIssues#hn_Module_causing_issues_Magisk_functionality_bootloop_loss_of_root_etc | "Module causing issues"]])//. If the uninstaller fails, just flash your unmodified copy of the boot image and you should be good to go. There’ll probably be some leftover files and folders from Magisk laying around in /cache and /data/adb, but these can be removed manually.
Deletions:
If you end up in a bootloop when installing Magisk, flash the [[https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 | Magisk uninstaller zip]] in recovery, flash a clean boot image (the uninstaller restores a copy of the untouched boot image, so this step is “just in case”) and start over //(for bootloops occurring after installing a Magisk module, see [[https://www.didgeridoohan.com/magisk/MagiskModuleIssues#hn_Module_causing_issues_Magisk_functionality_bootloop_loss_of_root_etc | "Module causing issues"]])//. If the uninstaller fails, just flash your unmodified copy of the boot image and you should be good to go. There’ll probably be some leftover files and folders from Magisk laying around in /cache and /data/adb, but these can be removed manually.

Revision [545]

Edited on 2018-12-17 06:41:30 by didgeridoohan
Additions:
===**Magisk not installed**===
After installing Magisk, if the Manager still reports that Magisk is not installed, check if the Manager has been installed to the external or adoptable storage. This is known to cause all kinds of issues, so make sure that the Manager is installed to the internal storage and check again.

Revision [542]

Edited on 2018-12-16 15:36:03 by didgeridoohan
Additions:
If a bunch of apps suddenly start force closing after installing Magisk, your ROM might have issues with ""WebView"". More precisely with the signatures for Chrome and Google ""WebView"". You can take a [[https://www.xda-developers.com/guide-sending-a-logcat-to-help-debug-your-favorite-app/ | logcat]] when one of the apps crash and see if there's anything about ""WebView"" in there. The reason is that MagiskHide sets ro.build.type to "user" and this enables the signature check. Ask your ROM developer to fix the signature error... Meanwhile, you can fix it temporarily by disabling MagiskHide, use the Magisk module [[https://forum.xda-developers.com/apps/magisk/module-magiskhide-props-config-t3789228 | MagiskHide Props Config]] to revert the prop value, or use a [[https://topjohnwu.github.io/Magisk/guides.html#scripts | boot script]] to revert the MagiskHide prop change //(see [[MagiskHideMore | "Reverting prop values set by MagiskHide"]])//.
Deletions:
If a bunch of apps suddenly start force closing after installing Magisk, your ROM might have issues with ""WebView"". More precisely with the signatures for Chrome and Google ""WebView"". You can take a [[https://www.xda-developers.com/guide-sending-a-logcat-to-help-debug-your-favorite-app/ | logcat]] when one of the apps crash and see if there's anything about ""WebView"" in there. The reason is that MagiskHide sets ro.build.type to "user" and this enables the signature check. Ask your ROM developer to fix the signature error... Meanwhile, you can fix it temporarily by disabling MagiskHide, or using a [[https://topjohnwu.github.io/Magisk/guides.html#scripts | boot script]] to revert the MagiskHide prop change //(see [[MagiskHideMore | "Reverting prop values set by MagiskHide"]])//.

Revision [540]

Edited on 2018-12-16 15:34:06 by didgeridoohan
Additions:
If a bunch of apps suddenly start force closing after installing Magisk, your ROM might have issues with ""WebView"". More precisely with the signatures for Chrome and Google ""WebView"". You can take a [[https://www.xda-developers.com/guide-sending-a-logcat-to-help-debug-your-favorite-app/ | logcat]] when one of the apps crash and see if there's anything about ""WebView"" in there. The reason is that MagiskHide sets ro.build.type to "user" and this enables the signature check. Ask your ROM developer to fix the signature error... Meanwhile, you can fix it temporarily by disabling MagiskHide, or using a [[https://topjohnwu.github.io/Magisk/guides.html#scripts | boot script]] to revert the MagiskHide prop change //(see [[MagiskHideMore | "Reverting prop values set by MagiskHide"]])//.
You can use the Magisk module [[https://forum.xda-developers.com/apps/magisk/module-magiskhide-props-config-t3789228 | MagiskHide Props Config]] to revert the prop value, use a [[https://topjohnwu.github.io/Magisk/guides.html#scripts | boot script]] to revert the MagiskHide prop change, or temporarily disable MagiskHide //(also see [[MagiskHideMore | "Reverting prop values set by MagiskHide"]])//
Deletions:
If a bunch of apps suddenly start force closing after installing Magisk, your ROM might have issues with ""WebView"". More precisely with the signatures for Chrome and Google ""WebView"". You can take a [[https://www.xda-developers.com/guide-sending-a-logcat-to-help-debug-your-favorite-app/ | logcat]] when one of the apps crash and see if there's anything about WebView in there. The reason is that MagiskHide sets ro.build.type to "user" and this enables the signature check. Ask your ROM developer to fix the signature error... Meanwhile, you can fix it temporarily by disabling MagiskHide, or using a boot script to revert the MagiskHide prop change //(see [[MagiskHideMore | "Reverting prop values set by MagiskHide"]])//.
You can use the Magisk module [[https://forum.xda-developers.com/apps/magisk/module-magiskhide-props-config-t3789228 | MagiskHide Props Config]] to revert the prop value, use a boot script to revert the MagiskHide prop change, or temporarily disable MagiskHide //(also see [[MagiskHideMore | "Reverting prop values set by MagiskHide"]])//

Revision [520]

Edited on 2018-12-09 04:11:34 by didgeridoohan
Additions:
%%mount /dev/block/loop0->/sbin/.magisk/img failed with 13: Permission denied%%
Deletions:
%%mount /dev/block/loop0->/sbin/.core/img failed with 13: Permission denied%%

Revision [463]

Edited on 2018-10-03 09:28:58 by didgeridoohan
Additions:
1) If you still can't get things working, check here: [[MagiskHelp | "Asking for help/reporting bugs"]].
Deletions:
//Also see [[MagiskOther | "Other things to try"]] and [[MagiskHelp | "Asking for help/reporting bugs"]]//.

Revision [460]

Edited on 2018-09-28 05:15:53 by didgeridoohan
Additions:
There are many devices that have a faulty implementation of f2fs. These may include Motorola, Lenovo and others. These devices can’t mount the Magisk image properly leading to issues with module installation and possibly superuser access. You might see something like this in the Magisk log:
Deletions:
There are many devices that have a faulty implementation of f2fs. These may include Motorola, Lenovo and others. These devices can’t mount the Magisk image properly leading to issues with module installation and possibly superuser access. You’ll likely see somthing like this in the Magisk log:

Revision [452]

Edited on 2018-09-11 13:00:46 by didgeridoohan
Additions:
If your system suddenly becomes unstable, with reboots and system processes stopping, make sure you haven't added any system apps or processes to the MagiskHide list. Because of the way MagiskHide works, it will kill off some pretty important parts of the running system if this kind of apps/processes are on the list, causing all kinds of havok.
Deletions:
If your system suddenly becomes unstable, with reboots and system processes stopping, make sure you haven't added any system apps or processes to the MagiskHide list. Because of the way MagiskHide works, it will kill off some pretty important parts of the running system, causing all kinds of havok.

Revision [451]

Edited on 2018-09-11 13:00:03 by didgeridoohan
Additions:
If apps on the MagiskHide list are force closing, simply remove them from the list. You should only add the apps and processes that actually detect root. Adding anything else to the list, that doesn't need to be there, may cause instabilities in your system (also see //"System instabilities"// above) Note: It's not about the number of apps on the list, but which apps are added.
Deletions:
If apps on the MagiskHide list are force closing, simply remove them from the list. The MagiskHide list should be kept to a bare minimum, which means you should only add the apps that actually detect root on the list. Adding anything else to the list, that doesn't need to be there may cause instabilities in your system. Note: It's not about the number of apps on the list, but which apps are added.

Revision [448]

Edited on 2018-09-11 11:40:34 by didgeridoohan
Additions:
It is also possible that the device is refusing to boot because you've added system apps or processes to the MagiskHide list. That's not a good idea... Only add the apps detecting root to the Hide list. Also see //"System instabilities"// below.
If your system suddenly becomes unstable, with reboots and system processes stopping, make sure you haven't added any system apps or processes to the MagiskHide list. Because of the way MagiskHide works, it will kill off some pretty important parts of the running system, causing all kinds of havok.
Only add the apps and processes that actually detect root to the MagiskHide list.
Deletions:
It is also possible that the device is refusing to boot because you've added system apps or processes to the ""MagiskHide"" list. That's not a good idea... Only add the apps detecting root to the Hide list. Also see //"System instabilities"// below.
If your system suddenly becomes unstable, with reboots and system processes stopping, make sure you haven't added any system apps or processes to the ""MagiskHide"" list. Because of the way ""MagiskHide"" works, it will kill off some pretty important parts of the running system, causing all kinds of havok.
Only add the apps and processes that actually detect root to the ""MagiskHide"" list.

Revision [447]

Edited on 2018-09-11 11:38:47 by didgeridoohan
Additions:
It is also possible that the device is refusing to boot because you've added system apps or processes to the ""MagiskHide"" list. That's not a good idea... Only add the apps detecting root to the Hide list. Also see //"System instabilities"// below.
===**System instabilities**===
If your system suddenly becomes unstable, with reboots and system processes stopping, make sure you haven't added any system apps or processes to the ""MagiskHide"" list. Because of the way ""MagiskHide"" works, it will kill off some pretty important parts of the running system, causing all kinds of havok.
Only add the apps and processes that actually detect root to the ""MagiskHide"" list.

Revision [416]

Edited on 2018-09-04 01:49:21 by didgeridoohan
Additions:
It's also possible that removing and reinstalling [[https://play.google.com/store/apps/details?id=com.android.chrome | Chrome stable]] or [[https://play.google.com/store/apps/details?id=com.google.android.webview | Google WebView]] (or simply installing one of them if it's not already installed) will fix the issue. If nothing else, installing [[https://play.google.com/store/apps/details?id=com.chrome.beta | Chrome Beta]] should work. After that you can go to //Developer options -> ""WebView"" implementation// and select the corresponding implementation.
If it's not an issue with MagiskHide or ""WebView"", grab a [[https://www.xda-developers.com/guide-sending-a-logcat-to-help-debug-your-favorite-app/ | logcat]] from the crash and post it together with lots of details in the [[https://forum.xda-developers.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382 | support thread]] //(also see [[MagiskHelp | "Asking for help/reporting bugs"]])//.
Deletions:
It's also possible that removing and reinstalling [[https://play.google.com/store/apps/details?id=com.android.chrome | Chrome stable]] or [[https://play.google.com/store/apps/details?id=com.google.android.webview | Google WebView]] (or simply installing one of them if it's not already installed) will fix the issue. If nothing else, installing [[https://play.google.com/store/apps/details?id=com.chrome.beta | Chrome Beta]] should work. After that you can go to //Developer options -> WebView implementation// and select the corresponding implementation.
If it's not an issue with MagiskHide or WebView, grab a [[https://www.xda-developers.com/guide-sending-a-logcat-to-help-debug-your-favorite-app/ | logcat]] from the crash and post it together with lots of details in the [[https://forum.xda-developers.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382 | support thread]] //(also see [[MagiskHelp | "Asking for help/reporting bugs"]])//.

Revision [415]

Edited on 2018-09-04 01:48:43 by didgeridoohan
Additions:
==**Apps on the ""MagiskHide"" list**==
If apps on the MagiskHide list are force closing, simply remove them from the list. The MagiskHide list should be kept to a bare minimum, which means you should only add the apps that actually detect root on the list. Adding anything else to the list, that doesn't need to be there may cause instabilities in your system. Note: It's not about the number of apps on the list, but which apps are added.
==**""WebView"" issues**==
If a bunch of apps suddenly start force closing after installing Magisk, your ROM might have issues with ""WebView"". More precisely with the signatures for Chrome and Google ""WebView"". You can take a [[https://www.xda-developers.com/guide-sending-a-logcat-to-help-debug-your-favorite-app/ | logcat]] when one of the apps crash and see if there's anything about WebView in there. The reason is that MagiskHide sets ro.build.type to "user" and this enables the signature check. Ask your ROM developer to fix the signature error... Meanwhile, you can fix it temporarily by disabling MagiskHide, or using a boot script to revert the MagiskHide prop change //(see [[MagiskHideMore | "Reverting prop values set by MagiskHide"]])//.
==**Other**==
If it's not an issue with MagiskHide or WebView, grab a [[https://www.xda-developers.com/guide-sending-a-logcat-to-help-debug-your-favorite-app/ | logcat]] from the crash and post it together with lots of details in the [[https://forum.xda-developers.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382 | support thread]] //(also see [[MagiskHelp | "Asking for help/reporting bugs"]])//.
Deletions:
If a bunch of apps suddenly start force closing after installing Magisk, your ROM might have issues with WebView. More precisely with the signatures for Chrome and Google WebView. You can take a [[https://www.xda-developers.com/guide-sending-a-logcat-to-help-debug-your-favorite-app/ | logcat]] when one of the apps crash and see if there's anything about WebView in there. The reason is that MagiskHide sets ro.build.type to "user" and this enables the signature check. Ask your ROM developer to fix the signature error... Meanwhile, you can fix it temporarily by disabling MagiskHide, or using a boot script to revert the MagiskHide prop change //(see [[MagiskHideMore | "Reverting prop values set by MagiskHide"]])//.
If it's not an issue with WebView, grab a [[https://www.xda-developers.com/guide-sending-a-logcat-to-help-debug-your-favorite-app/ | logcat]] from the crash and post it together with lots of details in the [[https://forum.xda-developers.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382 | support thread]] //(also see [[MagiskHelp | "Asking for help/reporting bugs"]])//.

Revision [414]

Edited on 2018-09-04 01:48:01 by didgeridoohan
Additions:
If your Wifi stops working after installing Magisk, try reflashing your kernel.
Deletions:
If your Wifi stops working after installing Magisk, reflash your kernel.

Revision [413]

Edited on 2018-09-04 01:42:28 by didgeridoohan
Additions:
If there’s just been a new Magisk release it’s also possible that there might be something with Magisk causing the issue. Just keep calm, restore your device like described above //(also see [[MagiskUpdating | Updating]])//, but first make sure to provide proper logs //(see [[MagiskHelp | "Asking for help/reporting bugs"]])//.
Deletions:
If there’s just been a new Magisk release it’s also possible that there might be something with Magisk causing the issue. Just keep calm, restore your device like described above, but first make sure to provide proper logs //(see [[MagiskHelp | "Asking for help/reporting bugs"]])//.

Revision [362]

Edited on 2018-07-19 15:41:02 by didgeridoohan
Additions:
==**Custom kernel**==
==**Magisk update**==
==**DM-verity and Forced encryption**==
==**Module issues**==
==**Special cases**==
Deletions:
**Custom kernel**
**Magisk update**
**DM-verity and Forced encryption**
**Module issues**
**Special cases**

Revision [357]

Edited on 2018-07-19 15:30:48 by didgeridoohan
Additions:
**Custom kernel**
**Magisk update**
**DM-verity and Forced encryption**
**Module issues**
**Special cases**

Revision [348]

Edited on 2018-07-19 14:12:32 by didgeridoohan
Additions:
You can use the Magisk module [[https://forum.xda-developers.com/apps/magisk/module-magiskhide-props-config-t3789228 | MagiskHide Props Config]] to revert the prop value, use a boot script to revert the MagiskHide prop change, or temporarily disable MagiskHide //(also see [[MagiskHideMore | "Reverting prop values set by MagiskHide"]])//
Deletions:
You can use the Magisk module [[https://forum.xda-developers.com/apps/magisk/module-magiskhide-props-config-simple-t3765199 | MagiskHide Props Config]] to revert the prop value, use a boot script to revert the MagiskHide prop change, or temporarily disable MagiskHide //(also see [[MagiskHideMore | "Reverting prop values set by MagiskHide"]])//

Revision [321]

Edited on 2018-07-19 09:26:45 by didgeridoohan
Deletions:
===**Magisk Manager crashes/freezes**===
If you're having issues with the Magisk Manager force closing/crashing/freezing at any point, clear data for the Manager or uninstall it and install it again. //Uninstall the Manager by clicking on the “Uninstall” button in the Manager and choosing “Uninstall App”.// This way all Manager related files will be removed.
The Manager crashing might also be caused by using a theme engine to theme the Manager (Substratum, etc). Disable it and reapply after an update to the Manager.
Another reported reason for the Manager crashing is if you've for some reason added the Magisk Manager as a system app. Try de-systemising it and see if that fixes the issue.
If there still are issues, capture a [[https://www.xda-developers.com/guide-sending-a-logcat-to-help-debug-your-favorite-app/ | logcat]] from the crash/freeze and post it in the [[https://forum.xda-developers.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382 | support thread]], with a detailed description of the problem //(also see [[MagiskHelp | "Asking for help/reporting bugs"]])//.

Revision [285]

Edited on 2018-04-30 04:31:09 by didgeridoohan
Additions:
If you're having issues with the Magisk Manager force closing/crashing/freezing at any point, clear data for the Manager or uninstall it and install it again. //Uninstall the Manager by clicking on the “Uninstall” button in the Manager and choosing “Uninstall App”.// This way all Manager related files will be removed.
Deletions:
If you're having issues with the Magisk Manager force closing/crashing/freezing at any point, clear data for the Manager or uninstall it and install it again. Uninstall the Manager by clicking on the “Uninstall” button in the Manager and choosing “Uninstall App”. This way all Manager related files will be removed.

Revision [260]

Edited on 2018-04-03 12:18:37 by didgeridoohan
Additions:
You can use the Magisk module [[https://forum.xda-developers.com/apps/magisk/module-magiskhide-props-config-simple-t3765199 | MagiskHide Props Config]] to revert the prop value, use a boot script to revert the MagiskHide prop change, or temporarily disable MagiskHide //(also see [[MagiskHideMore | "Reverting prop values set by MagiskHide"]])//
Deletions:
One solution is to temporarily disable MagiskHide, another is to use a boot script to revert the MagiskHide prop change //(see [[MagiskHideMore | "Reverting prop values set by MagiskHide"]])//

Revision [238]

Edited on 2018-03-25 09:42:03 by didgeridoohan
Additions:
A bootloop might also be because you’ve installed a module that Magic Mounts new files or folders to the root of /system. On some devices this will cause a bootloop. Contact the creator of the module you’re trying to install and let them know… //Also see [[MagiskModuleIssues | "Module Issues"]]//.
Deletions:
A bootloop might also be because you’ve installed a module that Magic Mounts new files or folders to the root of /system. On some devices this will cause a bootloop. A common cause is that the module creator have left the “placeholder” file in the module’s system folder. Contact the creator of the module you’re trying to install and let them know… //Also see [[MagiskModuleIssues | "Module Issues"]]//.

Revision [237]

Edited on 2018-03-25 09:40:32 by didgeridoohan [Fixed reference to "Module causing issues&quo;]
Additions:
If you end up in a bootloop when installing Magisk, flash the [[https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 | Magisk uninstaller zip]] in recovery, flash a clean boot image (the uninstaller restores a copy of the untouched boot image, so this step is “just in case”) and start over //(for bootloops occurring after installing a Magisk module, see [[https://www.didgeridoohan.com/magisk/MagiskModuleIssues#hn_Module_causing_issues_Magisk_functionality_bootloop_loss_of_root_etc | "Module causing issues"]])//. If the uninstaller fails, just flash your unmodified copy of the boot image and you should be good to go. There’ll probably be some leftover files and folders from Magisk laying around in /cache and /data/adb, but these can be removed manually.
Deletions:
If you end up in a bootloop when installing Magisk, flash the [[https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 | Magisk uninstaller zip]] in recovery, flash a clean boot image (the uninstaller restores a copy of the untouched boot image, so this step is “just in case”) and start over //(for bootloops occurring after installing a Magisk module, see "Module causing issues" below)//. If the uninstaller fails, just flash your unmodified copy of the boot image and you should be good to go. There’ll probably be some leftover files and folders from Magisk laying around in /cache and /data/adb, but these can be removed manually.

Revision [219]

Edited on 2018-03-01 03:19:41 by didgeridoohan [Fixed reference to "Module causing issues&quo;]
Additions:
Or, there's a much better solution... You can ask your ROM developer to add [[https://github.com/DirtyUnicorns/android_packages_apps_Settings/commit/5a647d96432abcb1276fab695600c5233e88b8d3 | this]] commit.
Deletions:
Or, there's a much better solution... You can ask your ROM developer to add this commit: https://github.com/DirtyUnicorns/android_packages_apps_Settings/commit/5a647d96432abcb1276fab695600c5233e88b8d3
===**magisk_daemon -post-fs use a lot of CPU**===
If you suddenly start experiencing high CPU usage and see that a process named magisk_daemon -post-fs is using a lot of your CPU, it's probably caused by having disabled Android logging with an app like Kernel Adiutor or by some other process. Enable logging again and the issue should disappear.

Revision [183]

The oldest known version of this page was created on 2018-02-05 15:38:18 by didgeridoohan [Fixed reference to "Module causing issues&quo;]
Valid XHTML :: Valid CSS: :: Powered by WikkaWiki