Skip to main content

๐Ÿ“ฆ As a Module

DI supports installation as a Magisk or KernelSU module using the Magisk Space.

dynamic_installer.zip
โ””โ”€โ”€ META-INF
โ””โ”€โ”€ com
โ””โ”€โ”€ google
โ””โ”€โ”€ android
โ””โ”€โ”€ magisk # Magisk Space
โ””โ”€โ”€ customize.sh # Your Module Script
โ””โ”€โ”€ module.prop # Your Module Info (Check below)
info

Modules define their own environment variables such as MODPATH. Due to their operating mechanism, files to be replaced must be directed to that directory.

KernelSU / Magisk v28+ Supportโ€‹

Some Managers use a stricter module installation. Therefore, it's mandatory to include a customize.sh and module.prop files in the ZIP ROOT.

Standard versions of DI v5.4-b3+ already include these provisional files for convenience; however, you can download them here.

my_module.zip
โ”œโ”€โ”€ customize.sh # It is only provisional
โ”œโ”€โ”€ module.prop # KSU / Magisk v28+ module info
โ””โ”€โ”€ META-INF
โ””โ”€โ”€ com
โ””โ”€โ”€ google
โ””โ”€โ”€ android
โ””โ”€โ”€ magisk
โ”œโ”€โ”€ customize.sh # Your script for both KSU and Magisk.
โ””โ”€โ”€ module.prop # Magisk v20+ module info
note

This adjustment is necessary because customize.sh and module.prop are read from the ZIP root statically, unlike versions prior to Magisk v28. So, if these provisional files are not added or mistakenly removed, the Manager won't be able to start the installation and will treat it as an invalid ZIP.

Exampleโ€‹

The contents of the ZIP's system folder will be extracted to $MODPATH/system. Changes should be reflected after a reboot.

package_extract_dir "system" "$MODPATH/system"