Standalone Zygisk API
Gives KernelSU and APatch users the full Zygisk API, and replaces Magisk's built-in Zygisk on Magisk.
coreZygiskNext is a standalone implementation of Zygisk, the code-injection layer that Zygisk modules depend on. It brings the full Zygisk API to KernelSU and APatch, and replaces Magisk's built-in Zygisk with extra controls: a dedicated module linker, Shamiko-style denylist handling, a WebUI and the znctl command line. It's built by Dr-TSNG and 5ec1cff, and supports Android 16 and 17 in the latest releases.
Every entry below comes from ZygiskNext's official release notes. The tag shows the release where each feature appeared.
Gives KernelSU and APatch users the full Zygisk API, and replaces Magisk's built-in Zygisk on Magisk.
coreA built-in loader for Zygisk modules, designed for better concealment. It's on by default since 1.3.3.
1.3.0+Includes most of Shamiko's features, including an 'unmount only' mode that keeps modules loaded while restoring mount changes.
1.3.0+ZygiskNext-specific modules can inject into more processes than standard Zygisk modules.
1.2.0+Check and control Zygisk and ZN module status from a root shell with the znctl command.
1.2.0+Change settings, view module status and export bug reports from the WebUI. It's translated into many languages and supports right-to-left layouts.
WebUIDetects broken Zygisk modules and tries to find modules that crash the system, then shows them in the WebUI.
1.3.4 / 1.4.3Supports multiple zygotes, SELinux-free environments, virtual machines, Meta Quest stub zygotes and, since 1.5.1, riscv64.
1.3.x–1.5.1The button downloads the official 1.5.2 release ZIP straight from the developers' GitHub. The download starts while you stay on this page. Release details were checked on 11 November 2026.
1.5.2STABLE
Direct file download from github.com/Dr-TSNG. You stay on this page.
Checksum as published by developer 5ec1cff on his official Telegram channel. Source: GitHub releases.
Six quick checks. Our button downloads the release ZIP from GitHub without opening a new tab. Nothing is re-hosted or modified.
You need a rooted device with Magisk, KernelSU or APatch. Only one root solution should be installed.
Use the -release.zip. There's one universal ZIP for every supported root manager and CPU architecture.
Our button pulls the file from github.com/Dr-TSNG/ZygiskNext. Avoid re-uploads on file-sharing sites.
Keep the ZIP in Downloads so your root manager's "Install from storage" can find it.
Compare the file's hash with the value above, using a hash app or sha256sum.
Keep a copy of your stock or patched boot image in case a module stops your device from booting.
Android starts every app from a single parent process called zygote. Zygisk is a way to load code into zygote so modules can change how apps behave. LSPosed-style frameworks and many root-hiding tools depend on it. Magisk ships its own Zygisk, but KernelSU and APatch don't. ZygiskNext fills that gap with a standalone implementation, and it can also replace Magisk's version.
It's built for experienced root users, module developers and anyone running Zygisk modules on KernelSU or APatch. Read about this site or our plain-English Zygisk explainer.
Run Zygisk modules that would otherwise need Magisk.
Swap the built-in Zygisk for ZN's linker, denylist modes and WebUI.
Use the ZN module API to reach processes that standard Zygisk modules can't.
Six steps for Magisk, KernelSU and APatch. Swipe or use the arrows.
Make sure exactly one root solution is installed: Magisk 26402+, KernelSU 10940+ (ksud 11575+) or APatch 10700+.
Open Magisk → Settings, switch Zygisk off and reboot. Running both at once stops modules from loading properly.
In your root manager's Modules screen, choose Install from storage and select the ZIP. Don't unzip it.
After rebooting, the module description should show the Zygisk status for your device's 64-bit and 32-bit processes. You can also check from a root shell:
su -c znctl
Install LSPosed forks, hiding tools or other Zygisk modules, then reboot. If one misbehaves, the WebUI points out modules with errors.
Use the WebUI or your manager's app list to choose which apps get mounts restored. The 'unmount only' mode keeps modules loaded.
Minimum versions come from the official README. Android version support is taken from the release notes. Website browser support isn't relevant here: ZygiskNext runs on the device itself.
| Configuration | Status | Requirement / note |
|---|---|---|
| KernelSU | Supported | KernelSU 10940+ and ksud 11575+ |
| Magisk | Supported | 26402+ with built-in Zygisk turned off |
| APatch | Supported | 10700+ |
| KernelSU forks (e.g. KernelSU Next) | Unconfirmed | Widely used by the community, but not listed in the official README |
| Two root solutions at once | Unsupported | README requires that no multiple root implementations are installed |
| Android 16 / 16 QPR2 | Supported | QPR2 support added in 1.3.2 |
| Android 17 / QPR2 | Supported | QPR2 Beta 2 in 1.4.5; fixes in 1.5.1 |
| Android 8 / 8.1 | Supported | Compatibility fixes in 1.4.2 |
| Architectures | ARM64, ARM32, riscv64 | riscv64 added in 1.5.1; VM and emulator environments improved over time |
| Unrooted device | Unsupported | Root is mandatory |
A balanced look, based on the release history and the trade-offs the developers themselves document.
Three standalone Zygisk implementations plus Magisk's built-in one, compared on the same criteria. Read the deep dives: vs ReZygisk and vs NeoZygisk.
| Criteria | ZygiskNext | ReZygisk | NeoZygisk | Magisk built-in |
|---|---|---|---|---|
| Developer | Dr-TSNG & 5ec1cff | PerformanC | JingMatrix | topjohnwu (Magisk) |
| License | Proprietary freeware | Open source (GPL/AGPL, BSD parts) | Open source (GPL-3.0) | Open source (GPL-3.0) |
| Magisk | Yes | Yes | Yes | Native |
| KernelSU | Yes | Yes | Yes | No |
| APatch | Yes | Listed as work in progress upstream | Yes | No |
| Approach | Standalone + ZN linker | Fork of ZN, rewrite in C | ptrace-based injection | Built into Magisk |
| WebUI | Yes | Unconfirmed | Unconfirmed | No |
Details for alternatives come from their public repositories. Features change often, so check each project before choosing.
The six problems we see most often. For anything else, export a bug report from the WebUI or module action (1.4.3+) and check the official release notes.
Magisk's built-in Zygisk is still switched on, or Magisk is older than 26402.
Turn off Zygisk in Magisk settings, update Magisk, reboot, then reflash ZygiskNext.
An incompatible Zygisk module crashes zygote.
Use your root manager's safe mode, or remove the module from recovery. Since 1.4.3, ZN tries to identify crashing modules and shows them in the WebUI.
The module fails ZN's checks, or isn't compatible with the ZN linker.
Update the module, check the ZN docs for linker compatibility, or switch the linker mode with zygiskd linker.
A bug in that specific build. 1.5.2 fixed app crashes on some systems.
Update to the latest release. If it continues, export a bug report and report it to the developers.
Your KernelSU or ksud is below 10940 / 11575.
Update KernelSU Manager and, if needed, the kernel, then reinstall.
ReZygisk, NeoZygisk or another implementation is installed alongside ZN.
Keep only one implementation. Remove the others, reboot, then reinstall ZygiskNext.
Best practice: update one module at a time, keep a backup of your working boot image, and read each release's notes before updating, especially across major Android updates.
Our editorial view of typical use cases. These aren't user reviews, quotes or ratings.
ZygiskNext is the most established way to get the full Zygisk API on KernelSU, with a WebUI that fits KernelSU's module system.
Strong fit, especially if you don't need open-source code.
The ZN linker and Shamiko-style denylist modes add control, at the cost of turning Magisk's own Zygisk off.
Good fit if you want those extra controls.
ZygiskNext's closed licence is a dealbreaker here. ReZygisk or NeoZygisk are the open alternatives.
Consider the open-source alternatives instead.
Short answers to common questions. For full walkthroughs, browse our ZygiskNext guides.
Yes. ZygiskNext is free to download and use from the developers' official GitHub releases. Since version v4-0.9.2 it's no longer open source: its copyright notice says all rights are reserved by the developers, but it's still distributed free of charge.
The official releases are on GitHub at Dr-TSNG/ZygiskNext, and co-developer 5ec1cff posts the same builds with SHA-256 checksums in his Telegram channel. Our download button fetches the 1.5.2 release ZIP directly from GitHub.
Flash the release ZIP (Zygisk-Next-1.5.2-864-a4a72ce-release.zip) as a module in your root manager: Magisk, KernelSU or APatch. Don't extract it first.
First turn off Magisk's built-in Zygisk in Magisk settings and reboot. Then install the ZIP from the Modules tab and reboot again. You need Magisk 26402 or newer.
Flash the newer release ZIP over the existing module in your root manager and reboot. Recent builds can also report problems through their WebUI, so check it after updating.
No. ZygiskNext is a root module. It needs a working Magisk, KernelSU or APatch installation, and only one root solution should be installed at a time.
No. Installing a module from Magisk, KernelSU or APatch doesn't wipe any data. Still, back up your data and your current boot image before changing anything at root level.
Download the newer ZIP from the official GitHub releases, verify its SHA-256, and install it over the current version from your root manager. Reboot, then check the WebUI or run znctl to confirm Zygisk is injected.
Remove it from your root manager's module list and reboot. On Magisk, you can switch Magisk's built-in Zygisk back on afterwards if you still need Zygisk modules.
It's made by well-known developers in the Android root community and is distributed through their official channels. It's closed source, though, so its code can't be independently audited. Download only from GitHub, check the SHA-256, and read our 'Is Zygisk Next safe?' guide for the full picture.
Yes. That's the main reason it exists. It needs KernelSU version 10940 or newer and KernelSU Manager (ksud) 11575 or newer, and it gives KernelSU users the Zygisk API that Zygisk modules depend on.
All three provide the Zygisk API. ZygiskNext is closed source and the most feature-rich. ReZygisk (PerformanC) is an open-source fork being rewritten in C. NeoZygisk (JingMatrix) is an open-source, ptrace-based implementation for KernelSU and APatch.
Yes. Release 1.3.2 added Android 16 QPR2 support, 1.4.5 added Android 17 QPR2 Beta 2, and 1.5.1 fixed Android 17 QPR2 support. Use the latest release for new Android versions.
Mostly. Since 1.3.0, ZygiskNext includes most of Shamiko's functions, such as the 'unmount only' denylist mode, and the developers announced that Shamiko would no longer be maintained.
No. ZygiskNext.com is an independent guide site. The developers distribute ZygiskNext through GitHub (Dr-TSNG/ZygiskNext) and their Telegram channels.
Yes. Standard LSPosed builds are Zygisk modules and load through ZygiskNext on Magisk, KernelSU and APatch. Install ZygiskNext first, reboot, then install LSPosed and reboot again.
Not on its own. Integrity results depend on your device, bootloader state, other modules and Google's current checks. ZygiskNext's denylist and hiding modes reduce what apps can see, but no setup is guaranteed to pass.
Boot into your root manager's safe mode or disable modules at boot, then remove the module you added last. ZygiskNext 1.4.3 and newer also try to identify the module behind a crash, which helps you find the culprit.
One ZIP for Magisk, KernelSU and APatch, with active updates for the newest Android releases.