Revision [279]

This is an old revision of MagiskModuleIssues made by didgeridoohan on 2018-04-25 04:25:31.

 


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

Can't install modules

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

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.

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.

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. This is also true if you see a “process error” when trying to install a module.

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

Another issue when installing modules may be that your device has a faulty f2fs implementation (see "Issues with f2fs"), that the Magisk image is mounted read-only (run the command “mount | grep “/sbin/.core/img” in terminal to see if it’s rw or ro. A different kernel might fix this) or that the Magisk image is corrupt. Easiest way to fix this is to run the Magisk uninstaller and start from the beginning, or use fsck. Google it…

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

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/.core/img and delete the “update” file. If it keeps happening when installing modules 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").

If the module doesn’t work and hasn’t installed properly. Navigate to /sbin/.core/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:

First, you can disable all Magisk modules by enabling "Magisk Core Only Mode" in Manager settings. This disables all modules and only keeps the core functions of Magisk active (MagiskSU, MagiskHide, systemless hosts). 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 above 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.

Boot to recovery and flash the Mount Magisk zip (see “Things to keep on your device”). 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 Mount Magisk zip 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).

If nothing else works, deleting the Magisk image (/data/adb/magisk.img) should.

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 method above under “Module causing issues”.
Valid XHTML :: Valid CSS: :: Powered by WikkaWiki