Wiki source for MagiskModuleIssues

Show raw source

@@[[Magisk | -- To the top/main article --]]@@
=====**{{color text="Module Issues" c="blue"}}**=====

===**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 [[MagiskHelp | "Asking for help/reporting bugs"]])//.

===**Modules seem to install, but aren't there after rebooting**===
Often caused by the module using an outdated module template. //See "Outdated template" below.//

If that's not the case, looking at the [[MagiskHelp | Magisk and module installation logs]] might give a clue as to what's going on.

===**Can't install modules**===
If there's an error installing a module or the module seems to install fine but doesn't show up as installed after a reboot, 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. Magisk modules templates used to have a version number (seen in the modules module.prop file), but now all installation logic is centralised to the Magisk module installation script. If the module you are trying to install has a minMagisk entry in the module.prop file it is very likely that it is too old to be able to install on a recent version of Magisk.

Most of the times you can tell that the issue is an outdated template by an error message telling you to install an older version of Magisk than the version you have installed. If there is no such message, look at the [[MagiskHelp | module installation log]], since it might show why things didn't install properly. One thing to look for is:
%%mount_magisk_img: not found%%
That means the installer is trying to use a Magisk image, something that was deprecated in Magisk v19.0.

You can also look in the module.prop file in the zip. If there's a line looking something like minMagisk=1500 it is a good hint that the module installer is too old (that kind of check isn't used anymore).

In other words, the module installer used in the zip needs an update.

==**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.

==**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 [[MagiskHelp | "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 /data/adb/modules 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 [[MagiskHelp | "Asking for help/reporting bugs"]])//.

If the module doesn’t work and hasn’t installed properly. Navigate to /data/adb/modules, 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 [[MagiskHelp | "Asking for help/reporting bugs"]])//.

===**Can't uninstall module**===
If a module, for some reason, can't be uninstalled from the Manager toy can do this manually. See //Uninstalling modules manually// below.

===**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), see //Disabling/uninstalling modules manually// below.

===**Disabling/uninstalling modules manually**===
==**No custom recovery**==
The tips below all rely on having a custom recovery, like TWRP, for your device. If you do not have one installed (or don't want one installed) but there is one available for your device it's a good idea to keep it handy to at least be able to fastboot boot it.

Since Magisk v19.4, there's an adb command that can be used to uninstall all modules on your device. If the device is bootlooping or simply haning on the boot animation you have a good chance that you can use this command to get up and running again.

Hook your device up to a computer (or other device you can run adb from) and execute the following command:
%%adb wait-for-device shell magisk --remove-modules%%
After that you can start your device and as soon as adb is available the command will activate, the modules will be removed and the device will reboot. Hopefully to a working system, sans modules. There's of course a chance that the troublesome module has done something that the command can't remove...

Another option is to build your own custom version of Magisk that has Core Only Mode enabled by default. Here's an example of how to do that, by XDA Recognised Contributor [[ | Tulsadiver]]:

It's also possible that someone's already built a Core Only Magisk and is providing a patched boot image for your device. Check out your device forum on [[ | XDA]].

Other than that, one of the only options available to you if no custom recovery is available, is to wipe /data (factory reset).

==**Uninstall/delete/disable modules from recovery**==
This is my prefered method, manually removing a troublesome module through a custom recovery. Boot to recovery and use the file explorer to navigate to /data/adb/modules (if you don't have access to /data in recovery, try using the //"Disable all modules"// method below). You now have a couple of options to remove the module:
- Navigate to the module's directory under /data/adb/modules and rename any file in there to "remove" (or "disable", just remember the file name in case you want to return to normal before actually removing the module).
- In terminal you can use the [[ | touch command]]: type (without quotation marks) "touch /data/adb/modules/<module folder>/remove" (or “/data/adb/modules/<module folder>/disable”, depending on your preference).
- Simply delete the module's folder under /data/adb/modules. **This is the last resort since it won't run any uninstall script that the module might use.**

If you create the "remove" or "disable" files, Magisk will take care of removing or disabling the module on the next reboot. __**Uninstalling the module this way is the preferred way, since it will also run any uninstall script that the module is using.**__

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.

There are also several available terminal/Aroma based recovery type managers available for handling this. Take a look in the Magisk forums.

==**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.

==**Recovery Module Managers**==
There are also a few different module managers for custom recoveries available (take a look over at [[ | XDA]]). These might make it easier for you to manage any installed modules when you can't boot your device, but personally I feel that it's easier to do all this yourself through the recovery file manager.

===**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