Zygisk Next is a standalone implementation of the Zygisk API for KernelSU and APatch, and an alternative to Magisk's built-in Zygisk for modules that load code into Android Zygote processes.
A Standalone Zygisk Runtime
Provides a shared injection and module API across multiple root frameworks while remaining separate from their internal feature sets.
Zygisk API
Loads compatible Zygisk modules into selected Zygote-derived processes and exposes the expected module callbacks.
Cross-Root Support
Supports current Magisk, KernelSU-family, and APatch environments when each framework meets its documented requirements.
Crash Recovery
Includes safe-mode handling for repeated Zygote startup failures caused by an incompatible injected module.
Role in the Root Stack
Android starts application processes from Zygote. Zygisk Next integrates at that point so compatible modules can execute initialization code before a target app runs. This is the foundation used by modules for instrumentation, compatibility layers, process-specific modifications, and root-environment management.
Zygisk Next aims to reproduce Zygisk API behavior, not every internal Magisk feature. A module that depends on Magisk-specific implementation details beyond the public API may behave differently.
Environment Requirements
| Environment | Requirement |
|---|---|
| All frameworks | Use exactly one active root implementation. Multiple root frameworks are unsupported. |
| KernelSU | Upstream documentation lists kernel-side KernelSU 10940+, manager/ksud 11424+, and full SELinux patch support. |
| Magisk | Use Magisk 26402+ and disable Magisk's built-in Zygisk before enabling Zygisk Next. |
| APatch | Use a supported APatch release and avoid loading another standalone Zygisk implementation at the same time. |
Compatibility Details
- Install the release build that matches the supported Android architecture and root environment, then reboot before evaluating dependent modules.
- Denylist behavior depends on the active root manager. Upstream notes that
PROCESS_ON_DENYLISTcannot currently be reported correctly for isolated processes on Magisk's DenyList. - If the device has more than one root implementation, denylist and injection state cannot be considered reliable.
- When Zygote repeatedly crashes after adding a module, use the documented safe-mode path, disable the newest dependent module, and reboot before further testing.
Distribution Terms
Beginning with the upstream license change identified as v4-0.9.2, Zygisk Next is distributed under all-rights-reserved terms. The project prohibits modification, redistribution, component extraction, and forks claiming succession. Obtain packages from the official release channel and do not repackage the binary in another project.