Revision [558]

This is an old revision of MagiskModuleIssues made by didgeridoohan on 2019-01-01 14:27:02.

 


Module Issues


There are no modules

If the list of modules under "Downloads" is empty, clear the repo cache (in the Manager settings) and/or reload the modules list (pull down).

Modules are installed, but don't load

Make sure you haven't enabled "Magisk Core Only Mode" in the Manager settings. This option disables all modules and only keeps the core functions of Magisk active (MagiskSU and MagiskHide). If you do not have "Magisk Core Only Mode" enabled, there's likely something wrong with your Magisk installation and you need to figure out what. Post details and logs in the support thread (also see "Asking for help/reporting bugs").

Can't install modules

If there's an error installing a module, there's a couple of things to try.

Outdated template
It might be that you're trying to flash a module with an outdated module template. Usually Magisk supports one version backwards of the current module template. The current minimum module template is 1500. Most of the times you can tell that this is the issue by the error message telling you to install an older version of Magisk than the version you have installed.

Zip is not a Magisk module
If the error states that it's not a Magisk zip, or invalid zip in TWRP, the zip is not packaged correctly. Open up the zip and you'll likely see a folder (probably named something like <nameofmodule>-master or similar, or something completely different). Take all the contents of that folder and repack it to the root of the zip and try flashing it again.

Magisk Manager storage permission
If the Manager does not have storage permissions there will be issues with module installation. It should automatically ask for permission when needed, but if this doesn’t work, give the permission manually.

Process error
If there's a "process error" when installing a module it is usually caused by the Manager not having storage permission (see above). It might also be fixed by clearing data for the Manager.

Corrupt zip
Also make sure that there’s nothing wrong with the zip file (corrupt, etc). Try downloading the zip again.

Magisk image not mounted properly
Sometimes the Magisk image is mounted read-only (run the command “mount | grep “/sbin/.magisk/img” in terminal to see if it’s rw or ro. This can cause issues with installing modules. A different kernel is one possible solution.

It can also be caused by your device having a faulty f2fs implementation (also see "Issues with f2fs" below), or that the Magisk image is corrupt. Easiest way to fix this the last scenario is to run the Magisk uninstaller and start from the beginning.

merge.img failed
If there's an error when installing a module along the lines of "mounting merge.img failed" your device might have issues with the file system, possibly a known f2fs bug (see below).

Issues with f2fs
There are some devices that have a faulty implementation of the f2fs file system. 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 module installation log or the Magisk log:
mount /dev/block/loop->/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 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).

If you see the above error but don't have /data formatted to f2fs, there might be something wrong with how the Magisk image is mounted (see "Magisk image not mounted properly" above).

Unable to extract zip
If you keep getting an error stating “Unable to extract zip” when installing modules you might have to to a complete reinstallation of Magisk.

Logs, etc
If the error occurs when installing a module through the Downloads section of the Magisk Manager, save an install log by clicking on the “Save log” button after the install script has run. If the error just states something along the lines "error when installing", try flashing the zip through recovery instead. If this also fails, save the recovery log and post in the support thread together with your Manager install log (also see "Asking for help/reporting bugs").

Module will be updated at next reboot

If you install a module and after reboot it doesn’t work or it works but there’s a message in the Magisk Manager modules section that states “module will be updated at next reboot”, try this:

If the module works, just navigate to the module folder under /sbin/.magisk/img and delete the “update” file. If it keeps happening when installing modules post the installation logs, Magisk log and possibly a logcat from the installation in the support thread (also see "Asking for help/reporting bugs").

If the module doesn’t work and hasn’t installed properly. Navigate to /sbin/.magisk/img, delete the module folder and try again. If it still doesn’t work post the installation logs, magisk_debug.log and possibly a logcat from the installation in the support thread (also see "Asking for help/reporting bugs").

Module causing issues (Magisk functionality, bootloop, loss of root, etc)

If you have a working Magisk installation, but a module causes Magisk, the Magisk Manager or your device to not function properly (bootloop, loss of root, etc), here's a couple of tips:

No custom recovery
First of all, if you do not have a custom recovery installed on your device, it might be good idea to have one handy so you can at least boot it. When rooting, a custom recovery often makes life so much easier. If you do have a custom recovery, you can skip this part and keep reading below.

If your device do not have a functioning custom recovery available, you might not have many options. The only way out of an issue that causes the device not to boot is to alter the Magisk image in some way (see more below). For this you need to access /data/adb, something that you need root access to do. Without a custom recovery, that's likely not going to happen... The only viable option in this case is to reset your device and wipe /data so that the Magisk image in /data/adb is removed. After that you can again set everything up to your liking and install Magisk again. Pro tip: always keep a backup of any important data, especially rooting and modifying your device.

Uninstall/delete/disable modules from recovery
This is my prefered method, manually removing the troublesome module through a custom recovery. Boot to recovery and flash the SUmount script. This mounts the Magisk image to /magisk and it can be accessed as any other directory. You now have a couple of options to remove the module:



If you create the "remove" or "disable" files, Magisk will take care of removing or disabling the module on the next reboot.

You can also keep a copy of the corresponding disable or remove files on your device and copy them to the module folder as needed.

Another option is to use the Magisk Module Uninstaller, by veez21, from the Collection of Magisk modules v2 or the Magisk Manager for Recovery Mode by VR25.

If you get an error in recovery when flashing SUmount script it might mean your Magisk image has become corrupted. Check the recovery log for details. Easiest way to fix this is to run the Magisk uninstaller and start from the beginning. It might also be possible to use fsck in terminal in recovery or through ADB. Google it (and check the recovery log for details).

Disable all modules
You can also disable all Magisk modules by enabling "Magisk Core Only Mode" in Manager settings. This keeps only the core functions of Magisk active (MagiskSU and MagiskHide). If you can't boot your device, this can be done by placing a file in /cache (/data/cache on A/B devices) named ".disable_magisk" (without quotation marks and with the leading dot). This will enable Core Only Mode and you can boot up your device, uninstall the troublesome module and then go into the Manager settings, disable Core Only Mode and reboot. In TWRP you can create the file through the TWRP terminal with the touch command, see below for an example.

The drawback to the this method is that it will disable all your Magisk modules, not just the one causing issues. If you don't want to do this, you can use the following method to uninstall only the troublesome module.

Delete the Magisk image
If nothing else works, deleting the Magisk image (/data/adb/magisk.img) should. If you do not have proper access to /data, this can also be done by wiping the /data partition which in turn means that you'd better have a backup of anything important...

Installing/disabling/uninstalling modules through the Manager or recovery

If you’re experiencing problems with installing, disabling or uninstalling a module through the Manager, simply try it through recovery instead. For disabling or uninstalling a module through recovery, see the described methods above under “Module causing issues”.
Valid XHTML :: Valid CSS: :: Powered by WikkaWiki