KPatch Next Module provides standalone KPM support for Magisk and KernelSU, including ARM64 boot-image patching, KPM lifecycle controls, application exclusions, and a companion WebUI.
Standalone KPM Management
Patch a compatible kernel, manage KPM files, and control exclusions without using APatch as the root solution.
Boot-Image Tools
The WebUI can locate and inspect the active boot image, apply KPatch Next, embed selected KPM files, or run the included unpatch workflow.
KPM Lifecycle
Lists loaded KPMs and provides load, unload, control, and boot-persistence functions through the packaged kpatch binary.
Application Exclusions
Reads a persistent package configuration after boot and sends excluded application UIDs to KPatch.
Requirements and Runtime
- The installer supports ARM64 only and aborts on other architectures.
- Magisk and KernelSU are the documented root environments; the installer explicitly aborts when APatch is detected.
- The module action opens KSU WebUI Standalone. If that application is absent, it opens the application's release page instead.
- Persistent KPM files are stored under
/data/adb/kp-next/kpmand loaded during the service phase. - If
kpatch hellodoes not return a working runtime, the module marks the state unresolved and skips KPM loading.
Operational Sequence
- Download the release ZIP and install it through Magisk or KernelSU on an ARM64 device.
- Reboot, then open the module action with KSU WebUI Standalone.
- Inspect the detected boot image and kernel status before selecting a patch or unpatch operation.
- After a successful boot-image change, reboot and confirm that the KPatch runtime responds.
- Add compatible
.kpmfiles through the WebUI; a file that fails boot-time loading is removed by the service script.