How to Install Zygisk Next on Magisk, KernelSU and APatch

Before you begin

• A rooted device with one of: Magisk 26402+, KernelSU 10940+ (ksud 11575+) or APatch 10700+
• A backup of your current boot image
• The official release ZIP (currently Zygisk-Next-1.5.2-864-a4a72ce-release.zip)

Step 1: Download and verify

Download the ZIP from the official GitHub. The button on our homepage fetches it directly. Then verify the hash:

sha256sum Zygisk-Next-1.5.2-864-a4a72ce-release.zip

For 1.5.2, the expected value is ce50b13fecb9e4456db69ef17b715f7cfbc094004dd9f30f7d6348dfab619a96.

Which root manager should you use?

If you're not rooted yet, the choice of root manager affects how you install Zygisk Next:

• Magisk: the most widely documented option, and it works on almost any device with an unlockable bootloader. It has its own Zygisk, so Zygisk Next is optional here.
• KernelSU: root at kernel level, popular on GKI devices. It has no built-in Zygisk, so Zygisk Next is the usual partner.
• APatch: patches the kernel image without needing kernel source. Like KernelSU, it needs a separate Zygisk implementation.

Rooting itself is outside the scope of this guide. Follow your root manager's official installation docs for your exact device.

Step 2 (Magisk only): turn off built-in Zygisk

1. Open Magisk → Settings.
2. Turn Zygisk off.
3. Reboot.

If Magisk's Zygisk and Zygisk Next are both active, Zygisk modules won't load correctly.

Step 3: Flash the module

Select the ZIP as it is. Don't extract it. Reboot when it finishes.

Step 4: Confirm it's working

After rebooting, the module description should show Zygisk Next's status for your device's 64-bit and 32-bit processes. From a root shell:

su -c znctl

On KernelSU and APatch, the module's WebUI shows the same information and your Zygisk Next modules.

Step 5: Add Zygisk modules

Now install the Zygisk modules you need, such as an LSPosed fork or a hiding module, then reboot. If something is wrong, Zygisk Next's WebUI flags modules that fail its checks (since 1.3.4) and tries to identify crashing ones (since 1.4.3).

APatch-specific notes

APatch patches the kernel directly and needs version 10700 or newer for Zygisk Next. Install the ZIP through APatch's module screen, reboot, and use the module's WebUI to check status. As on KernelSU, avoid mixing APatch's app-level settings with Zygisk Next's denylist modes in conflicting ways.

Verifying from a computer

Prefer to check from a PC? Download the ZIP on the computer and verify it, then push it to the phone:

sha256sum Zygisk-Next-1.5.2-864-a4a72ce-release.zip
adb push Zygisk-Next-1.5.2-864-a4a72ce-release.zip /sdcard/Download/

Then install it from your root manager as usual.

Common install mistakes

• Extracting the ZIP and trying to flash its contents. Always flash the ZIP as it is.
• Leaving Magisk's built-in Zygisk on.
• Having two root solutions installed (for example, remnants of Magisk on a KernelSU device).
• Installing a second Zygisk implementation "just in case".
• Flashing through custom recovery instead of the root manager. The module is designed to be installed from Magisk, KernelSU or APatch.

Frequently asked questions

Can I install Zygisk Next without root?

No. It's a root module and needs Magisk, KernelSU or APatch installed and working first.

Can I flash it in TWRP or another custom recovery?

Install it from your root manager instead. The module is built to be installed by Magisk, KernelSU or APatch, which set it up correctly.

How long does installation take?

Usually under a minute to flash, plus a reboot. The first boot after install can take slightly longer than normal.

Do I need to wipe data?

No. Installing a module doesn't wipe data. A backup is still wise in case something goes wrong.

How do I update to a new version?

Download the new ZIP, verify it, and install it over the existing one from your root manager. Then reboot. You don't need to uninstall first.

What's the fastest way to uninstall?

Remove it in your root manager's module list and reboot. If you're on Magisk and still want Zygisk, turn Magisk's built-in Zygisk back on afterwards.

Updating and uninstalling

• Update: flash the newer ZIP over the existing module and reboot.
• Uninstall: remove the module in your root manager and reboot. On Magisk, you can switch built-in Zygisk back on afterwards.
• Stuck in a bootloop? Use your root manager's safe mode or recovery to remove the faulty module.

On KernelSU? See the dedicated Zygisk Next KernelSU guide.