Root Tools and Xposed Modules
Root solutions and the modules that run on them. KernelSU and APatch give you root from the kernel. The Xposed modules need root plus LSPosed, and each one changes one specific part of Android, from install rules to notification channels. We confirmed the Xposed API inside every module listed here.
The order to do it in
- Choose and install a root solution. All of them need an unlocked bootloader. Our guide on how to root Android covers unlocking it, brand by brand, and installing Magisk. Most start from your phone’s stock boot or init_boot image, which the app patches and you flash back to the phone; on kernels older than 5.10, KernelSU and KernelSU Next need a kernel built with their driver instead. Our comparison of KernelSU, APatch and Magisk explains which fits which kernel, and the guides on extracting a boot image and KernelSU’s LKM and GKI modes cover the first steps.
- Install Vector or LSPosed if you want Xposed modules. It is itself a module for your root solution, not an app from this list, and it runs on Zygisk: built into Magisk, a separate module such as NeoZygisk, ReZygisk or ZygiskNext on KernelSU and APatch. The open-source LSPosed stopped at version 1.9.2 and Android 14 in 2023. On Android 15 and later the choice is Vector, an open-source fork, or LSPosed 2.x, which the original team has released since March 2026 without its source code. Our guide to installing LSPosed or Vector compares the three and walks through the steps.
- Then pick modules. Enable each module in the framework’s manager for the apps it should change, then reboot, or force-stop those apps so they start again with the module loaded. Check that your framework loads the module’s API: Vector 2.1 and later and LSPosed 2.x no longer load modules built only for the early libxposed API 100. Our LSPosed modules list compares the modules.
What each one needs
Using root on any of these needs an unlocked bootloader: the root solutions to install, the modules and Neo Backup because they run on root. MMRL alone opens without root, to browse and download modules; installing them needs root.
| App | Needs | Android, kernel or device |
|---|---|---|
| Magisk | Unlocked bootloader | Android 7.0 and later |
| KernelSU | Unlocked bootloader | GKI kernel 5.10+, older only with a kernel you build; manager: Android 12+, 64-bit |
| KernelSU Next | Unlocked bootloader | GKI kernel 5.10+, or an older one built with its driver; manager: Android 8.0+, 64-bit |
| APatch | Unlocked bootloader | ARM64, kernel 3.18 to 6.1 |
| MMRL | Root, to install modules | Android 8.0 and later |
| Neo Backup | Root | Android 8.0 and later |
| Disable Target API Block | Root + LSPosed | Android 14 and later |
| NoStorageRestrict | Root + LSPosed | Android 11 and later |
| Free Notifications | Root + LSPosed | Android 8.0 and later |
| HideMockLocation | Root + Vector 2.1+ or LSPosed 2.x | Android 8.0 and later |
| Cirno | Root + LSPosed | Android 12 and later, kernel 5.0+ |
| KnoxPatch | Root + LSPosed | Samsung Galaxy, Android 9.0 and later |
| Pengeek | Root + Vector 2.1+ or LSPosed 2.x | Xiaomi on HyperOS, Android 15 and later |
Unlocking the bootloader usually wipes the phone, so back up first. On a Samsung Galaxy, rooting also trips Knox, a one-time fuse in the hardware, and some of Samsung’s own apps stop working; KnoxPatch makes those apps work again but can’t reset the fuse.
Root solutions
The step everything else here depends on. Each one needs an unlocked bootloader and installs through a patched boot image or kernel; the app is the manager you use afterwards. They differ mainly in which kernels they support.
-
Magisk Patches the boot image; the widest device support, with Zygisk built in for LSPosed.Download -
KernelSU Root inside the kernel, for GKI kernels 5.10 and newer; the manager needs Android 12.Download -
KernelSU Next A KernelSU fork that keeps a branch for older kernels; its manager runs on Android 8.0.Download -
APatch Patches the kernel image on ARM64 kernels 3.18 to 6.1, managed with a SuperKey.Download
Module manager
Root solutions install modules from zip files; this app finds and installs them from repositories.
LSPosed modules
Xposed modules each change one part of Android or of other apps. They need root plus an Xposed framework, LSPosed or its open-source fork Vector, running on Zygisk, and you enable each one for the apps it should change. HideMockLocation and Pengeek need a current framework: Vector 2.1 or later, or LSPosed 2.x.
-
Disable Target API Block Lets you install apps built for very old Android versions again, on Android 14 and later.Download -
NoStorageRestrict Lets apps pick the Download and Android folders again, blocked since Android 11.Download
-
Free Notifications Makes every notification channel editable, including locked system ones.Download
-
HideMockLocation Hides an active mock location from the apps you choose.Download -
Cirno Freezes apps left in the background so they use no CPU; Android 12 and later.Download -
KnoxPatch Gets Samsung apps and features working again on a rooted Galaxy phone.Download -
Pengeek System tweaks for Xiaomi phones on HyperOS with Android 15, successor to CustoMIUIzer.Download
Backup and other root tools
Apps that use root directly, without a module or LSPosed.
-
Neo Backup Backs up apps together with their data, one at a time, in batches or on a schedule.Download
Related topics
-
KernelSU vs APatch vs Magisk: Which Root Solution Fits Your Phone
KernelSU and APatch root Android from the kernel; Magisk patches the boot image. Kernel support, modules and requirements compared, with APKs checked.





-
LSPosed Modules: 9 Open-Source Xposed Modules Worth Installing
Nine open-source LSPosed and Xposed modules, from old-app installs and hidden mock locations to icon packs and app freezing. Every APK checked.


