Magisk modules: a maintained catalog and how to use them safely
A Magisk module is a zip of files and scripts that Magisk applies at boot without changing the system partition. Many popular modules have been abandoned or replaced by forks, so the catalog below lists who maintains each one, its latest release and whether it is still alive. Below that: how to install modules without getting stuck, and how to recover when one breaks your phone.
Last updated 10 sourcesHow we check pages
Updated to Magisk v31.1? Grant root to module managers first
Magisk v31.1, the current stable release (October 25, 2026), removed the pop-up root prompts: root is now granted ahead of time in the Superuser tab, so apps such as MMRL or Vector's manager need to be allowed there. It also removed the option to hide the Magisk app. v30.7, the previous release, still shows prompts.
The short version
Install modules only from their developers' GitHub releases, keep USB debugging on so you can remove them over adb, and check that a module is still maintained before trusting it with root. Magisk recovers from most bad modules by itself: after two failed boots it starts in Safe Mode with every module disabled.
Find a module
Every entry links to the project's own repository. Versions and dates are the latest releases on GitHub as of October 26, 2026.
-
PlayIntegrityFork
MaintainedSpoofs device properties to Google Play services. Restores the basic and legacy device verdicts; cannot give Android 13+ device integrity alone.
-
PlayIntegrityFix inject-s
MaintainedFork of chiteroman's removed original, configured with
pif.propand a WebUI. Install it or PlayIntegrityFork, not both. -
Tricky Store
Closed sourceChanges the key-attestation certificate chain using a hardware keybox. Closed source since 1.1.0; leaked keyboxes get revoked by Google.
-
Tricky Store OSS
MaintainedOpen-source (GPL-3.0) rewrite of Tricky Store that reads the same
/data/adb/tricky_storefiles. -
TEESimulator
MaintainedOpen-source software KeyMint that runs inside keystore. Without a keybox it does nothing.
-
Tricky Addon
MaintainedA WebUI for editing Tricky Store's target list. On Magisk it opens through the Action button and a WebUI app.
-
Vector (LSPosed fork)
MaintainedThe maintained continuation of LSPosed: runs Xposed modules through Zygisk, scoped to the apps you pick.
-
LSPosed (original)
UnmaintainedThe original Xposed framework for Zygisk. No release since 2023 and no support past Android 14; use Vector instead.
-
Zygisk Next
Closed sourceStandalone Zygisk with an “unmount only” DenyList mode. No longer GPL since v4-0.9.2. Most Magisk users don't need it.
-
ReZygisk
MaintainedOpen-source Zygisk rewritten in C, created because Zygisk Next's newer releases are not open source.
-
NeoZygisk
MaintainedOpen-source (GPL-3.0) Zygisk replacement with its own DenyList; v2.4 added Android 17 support.
-
Shamiko
InactiveHides Magisk, Zygisk and Zygisk modules from apps on the DenyList. No source code published; optional whitelist mode via
/data/adb/shamiko/whitelist. -
Zygisk Assistant
InactiveOpen-source (MIT) root-hiding module that also uses the DenyList. Named by PlayIntegrityFork as an alternative to Shamiko.
-
NoHello
InactiveOpen-source (MIT) Zygisk module to hide root, also named in PlayIntegrityFork's requirements.
-
Universal GMS Doze
UnmaintainedLets Doze restrict Google Play services. Also disables Find My Device on every boot; officially supports up to Android 15.
-
Universal GMS Doze (MarsPatrick fork)
MaintainedContinuation of Universal GMS Doze with a WebUI and a Find My Device toggle; lists Android 14 to 16 devices.
-
ViPER4Android (likelikeslike)
MaintainedOpen-source ViPER4Android app with an AIDL driver for Android 15 and later. AndroidAudioMods' ViPER4Android-RE has had no release since December 2023 and reports “driver not found” on Android 15 and 16.
-
BusyBox for Android NDK
MaintainedPuts a static BusyBox and its applets on your PATH for apps and terminal use. Magisk already runs every module script in its own BusyBox, so modules don't need it.
-
bindhosts
MaintainedSystemless hosts-file ad blocking, controlled from the module's Action button; its WebUI is not available on Magisk.
-
Magisk iOS Emoji
MaintainedReplaces the system emoji font with iOS emoji (Unicode 17). May conflict with other font modules.
-
Pixelify
ArchivedEnabled Pixel-exclusive features on other phones. Archived in April 2025; its README warns of bootloops on Realme UI and OxygenOS on Android 14.
No module matches. Try a broader word, or pick All.
Status: Maintained means a release or commit in 2026. Inactive means no release for over a year. Unmaintained or Archived means the author stopped or archived the project. Magisk no longer has a built-in module store; it was removed in v24.0.
How recently each module was updated
Maintenance matters more for root modules than for apps: each Android release and each Play Integrity change can break them.
Time since each module's latest release
How modules work
Installed modules live in /data/adb/modules/<id>. At boot Magisk mounts each module's system folder over the real /system with bind mounts (“magic mount”), so files are replaced or added without touching the partition. A module can also include:
| File | What it does |
|---|---|
module.prop | Name, version and author shown in the app. |
post-fs-data.sh | Runs early and blocks boot until it finishes (up to 40 seconds, scripts capped at 35). |
service.sh | Runs later in the background, after boot continues. |
action.sh | Adds an Action button to the module's card in the Magisk app (since v28.0). In v31.0 it runs in a built-in terminal. |
uninstall.sh | Runs when you remove the module, to undo changes made outside its folder. |
zygisk/ | Native libraries loaded into app processes through Zygisk. |
Every Magisk script runs in Magisk's own BusyBox shell. Module zips can only be flashed in a custom recovery such as TWRP if they include a META-INF installer; otherwise install them from the app. The full format is in Magisk and Zygisk module development.
Where to find modules now
Magisk removed its built-in module repository in v24.0. Download modules from their developers' GitHub releases, linked in each catalog card. Third-party manager apps exist, with very different health:
- MMRL: open source, supports Magisk, KernelSU and APatch, latest release March 8, 2026. On Magisk v31.1 or newer, grant it root in the Superuser tab first.
- Androidacy Module Manager: its README says it is in maintenance mode, and it is ad-supported.
- Fox's Magisk Module Manager: archived since May 2023.
- For Xposed modules, the Xposed module repository is active, with over 1,200 modules.
Install a module safely
Each step has a Done box so you can keep your place. Your progress is saved in this browser only.
-
Turn on USB debugging first
1 minuteIn Developer options, enable USB debugging and allow your computer once. If a module stops the phone from booting, you can then remove every module with one adb command.
-
Download from the developer, and check it is maintained
2 minutesA module runs as root, so take it only from its developer's own release page. Check the latest release date and the open issues for your Android version before installing; the catalog above shows both at a glance.
-
Install and reboot
2 minutesIn the Magisk app open Modules → Install from storage, pick the zip, then reboot. New and updated modules are staged in
/data/adb/modules_updateand only take effect after the reboot. Install one module at a time so you know which one caused a problem. -
Disable or remove properly
1 minuteThe switch on a module's card disables it at the next boot; Remove deletes it and runs its
uninstall.sh. Prefer Remove when you are done with a module: some modules, such as Universal GMS Doze, only undo their changes when removed.
If a module breaks your phone
Magisk has several ways back in. Start with the first that applies.
The phone bootloops after installing a module
Wait. Magisk's FAQ says that if the phone fails to finish booting twice in a row, the next boot starts in Magisk Safe Mode automatically, with every module and Zygisk disabled. Then remove the module that caused it and reboot.
Enter Magisk Safe Mode yourself
Press and hold Volume Down a few seconds before the boot animation and release it when the animation appears; Magisk needs it held for more than three seconds. Holding it until the phone has booted also triggers Android's own safe mode; pressing too late triggers only Android's, and modules stay on. If the phone still boots, the Magisk app's reboot menu also has a Safe Mode option.
Remove all modules over USB
With USB debugging on, run adb wait-for-device shell magisk --remove-modules. It removes every module and reboots; add -n to skip the reboot. See fixing a Magisk bootloop for more options.
A module manager app lost root after updating Magisk
Magisk v31.1 replaced root prompts with grants set ahead of time. Allow the app in the Magisk app's Superuser tab.
A module zip fails in TWRP
Recovery can only flash modules that ship a META-INF installer. Install the zip from the Magisk app instead.
A module installs but does nothing on KernelSU
On KernelSU 3.x, modules are only mounted once a metamodule such as meta-overlayfs is installed. Magisk mounts modules itself.
Questions people ask
What are the best Magisk modules?
It depends on the job, but start from maintained ones: PlayIntegrityFork for Play Integrity, Vector for Xposed modules, the MarsPatrick fork of Universal GMS Doze for battery, and bindhosts for ad blocking. The catalog above shows each one's status.
Does Magisk still have a module store?
No. Downloading from the central Magisk-Modules-Repo was removed in v24.0. Use the developers' GitHub releases or a third-party manager such as MMRL.
Is LSPosed dead?
The original has had no release since October 2023 and stops at Android 14. JingMatrix's fork, renamed Vector, is maintained and supports Android 8.1 to 17.
Do I need Zygisk Next on Magisk?
No. Magisk has Zygisk built in; Zygisk Next, ReZygisk and NeoZygisk mainly serve KernelSU and APatch, and on Magisk you must turn the built-in Zygisk off to use them.
Does Magisk hide root by itself?
No. Magisk's FAQ says it no longer handles root hiding, which is left to modules such as Shamiko, Zygisk Assistant or NoHello.
Do modules work with Hybrid Mount or metamodules?
Metamodules are a KernelSU feature, and Hybrid Mount describes itself as for KernelSU and APatch. Magisk mounts modules itself.
Can a module damage my phone?
A module runs as root and can break booting, but it does not modify the system partition, so removing it (or Safe Mode) restores the phone. Install modules one at a time and only from their developers.
Sources
This page is written from the sources below. If anything here disagrees with them, the upstream source is correct.
- Magisk developer guide: modules, scripts and BusyBox (topjohnwu)
- Magisk FAQ: Safe Mode and removing modules (topjohnwu)
- Magisk tools: magisk --remove-modules (topjohnwu)
- Magisk changelog: v24.0 to v31.1 (topjohnwu)
- MMRL module manager (MMRLApp)
- Androidacy Module Manager (Androidacy)
- Fox's Magisk Module Manager, archived (Fox2Code)
- KernelSU metamodules (KernelSU)
- Xposed module repository
- Shamiko releases (LSPosed)
Found a mistake or something out of date? Tell us and we will check it against the source and fix the page. Confirmed corrections are listed in the corrections log.
Report a problem with this page