Zygisk Next on KernelSU: Requirements, Setup and Tips

Why KernelSU users need Zygisk Next

KernelSU provides root from inside the kernel and has its own module system, but no built-in Zygisk. Without a Zygisk implementation, popular Zygisk modules simply don't load. Zygisk Next adds the Zygisk API on top of KernelSU so those modules work as they would on Magisk.

Minimum requirements

Check your versions in KernelSU Manager's home screen. Zygisk Next has also kept pace with KernelSU's newer interfaces in releases like 1.3.2 and 1.4.4.

GKI and non-GKI kernels

KernelSU works best on devices with a GKI (Generic Kernel Image) kernel, which most phones launched with Android 12 or later use. On those, you patch or flash a boot image and you're done. Older non-GKI devices need a custom kernel with KernelSU built in. Zygisk Next itself doesn't care which path you took, as long as KernelSU meets the minimum version and is working correctly. Confirm KernelSU shows as "Working" in its manager before installing Zygisk Next.

Installing on KernelSU

1. Download the release ZIP from the official GitHub.
2. Open KernelSU Manager → Modules → Install and pick the ZIP.
3. Reboot.
4. Open the module's WebUI (the KernelSU module list shows a WebUI entry) to confirm status.

You can also check from a shell:

su -c znctl

Unmount and app settings

KernelSU has per-app root and module settings, including an option to unmount modules for selected apps. Zygisk Next's WebUI also shows warnings about kernel unmount conflicts (added in 1.3.2). Use one consistent approach for each app: either KernelSU's unmount or Zygisk Next's denylist modes. Configuring both differently can cause confusing results.

Using hiding and framework modules

Many hiding modules list KernelSU-specific instructions, such as "install Zygisk Next and make sure the unmount setting is enabled for the target app in KernelSU Manager". Follow each module's own README, because instructions differ between modules and versions.

KernelSU forks and variants

The community maintains several KernelSU forks and variants. The official Zygisk Next README lists requirements for KernelSU itself, not for each fork. Many users run Zygisk Next on forks without problems, but compatibility isn't guaranteed. If you use a fork, check its documentation and its version numbering, because some forks use their own version schemes that may not map directly to KernelSU's 10940/11575 minimums.

Recommended KernelSU workflow

• Keep KernelSU Manager updated before updating Zygisk Next.
• Install Zygisk Next first, reboot, then add Zygisk modules one at a time.
• Use the module's WebUI after each change to confirm nothing is flagged.
• Export a bug report from the WebUI (1.4.3+) if you need help.

Useful commands

From an adb shell with root, or a terminal app:

su
znctl                      # Zygisk / ZN module status
ls /data/adb/modules/zygisksu

If znctl isn't found, the module isn't active. Check the KernelSU module list and reboot.

Frequently asked questions

Does KernelSU need Zygisk Next to work?

No. KernelSU gives you root without it. You only need Zygisk Next, or another Zygisk implementation, if you want to run Zygisk modules such as LSPosed.

Can I use KernelSU Next with Zygisk Next?

Many users run Zygisk Next on KernelSU forks like KernelSU Next. Check the fork's own notes on Zygisk support and version numbers, because forks may number versions differently from official KernelSU.

Why does the WebUI say Zygisk isn't injected?

The usual causes are a second Zygisk implementation installed, a KernelSU version below the minimum, or a missed reboot. Remove extras, update KernelSU Manager, then reboot.

Do I need to reinstall Zygisk Next after a KernelSU update?

Usually not. Modules normally survive KernelSU updates. Reboot and check the WebUI to be sure.

Does an OTA update remove Zygisk Next?

An OTA typically replaces the boot or init_boot image, which removes KernelSU root until you patch again. Your modules usually remain in place and start working again once root is restored.

Is KernelSU better than Magisk for Zygisk Next?

Both are supported. KernelSU users need a Zygisk implementation anyway, while Magisk users can choose between Magisk's built-in Zygisk and Zygisk Next.

KernelSU troubleshooting

Using Magisk or APatch instead? See the full install guide.