Revision [183]

This is an old revision of MagiskIssues made by didgeridoohan on 2018-02-05 15:38:18.

 


Magisk Issues


Bootloop

If you end up in a bootloop when installing Magisk, flash the 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.



If your system bootloops again and you're using a custom kernel, try starting over without installing that kernel. If there's still a bootloop your system might just not be compatible. One possibility is to try finding another custom kernel that is compatible.

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 "Asking for help/reporting bugs").

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


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 "Module Issues".

Some devices need special modifications to the boot image to not bootloop with Magisk. Sony is one of these manufacturers, where you may need to disable RIC.

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 logcat from the crash/freeze and post it in the support thread, with a detailed description of the problem (also see "Asking for help/reporting bugs").

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’ll likely see somthing like this in the Magisk log:
mount /dev/block/loop0->/sbin/.core/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 F2FS Loopback Bug Workaround module by 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).

Apps are force closing

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 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 "Reverting prop values set by MagiskHide").

It's also possible that removing and reinstalling Chrome stable or Google WebView (or simply installing one of them if it's not already installed) will fix the issue. If nothing else, installing Chrome Beta should work. After that you can go to Developer options -> WebView implementation and select the corresponding implementation.

It might also be possible to use Chromium. There are several Chromium installers available both in the Play Store and on F-Droid.

If it's not an issue with WebView, grab a logcat from the crash and post it together with lots of details in the support thread (also see "Asking for help/reporting bugs").

Developer options disappeared from settings

If Developer options suddenly disappeared from settings after installing Magisk, it's probably because MagiskHide changes ro.build.type from "userdebug" to "user" (known "safe" prop value). On some devices/ROMs this prop need to be set to "userdebug" to show the Developer options.

One solution is to temporarily disable MagiskHide, another is to use a boot script to revert the MagiskHide prop change (see "Reverting prop values set by MagiskHide")

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.

Wifi stopped working

If your Wifi stops working after installing Magisk, reflash your kernel.

Magisk isn't working

If you can boot up, but Magisk isn't working as expected (not detecting the Magisk installation, loss of root, etc), there are a few things you can try.


  1. Reboot. Sometimes this helps Magisk mount everything as it should.
  1. Try removing any installed modules to see if it's a faulty module causing issues. If that seems to fix it, install the modules one at a time to find which one causes issues.
  1. If nothing else works, try starting fresh with a new installation.

Also see "Other things to try" and "Asking for help/reporting bugs".
Valid XHTML :: Valid CSS: :: Powered by WikkaWiki