explaingit

dr-tsng/zygisknext

9,446Audience · developerComplexity · 4/5Setup · hard

TLDR

ZygiskNext is a standalone Zygisk implementation for Android that lets Magisk modules run on KernelSU-rooted devices, or replaces Magisk's built-in Zygisk on standard Magisk setups.

Mindmap

mindmap
  root((repo))
    What it does
      Standalone Zygisk
      Module code injection
      Startup hooking
    Use with KernelSU
      Fills missing Zygisk
      Magisk modules work
      Kernel version needed
    Use with Magisk
      Drop-in replacement
      Disable built-in first
      v26402 minimum
    Limitations
      No DenyList isolated
      No extra Magisk features
      SELinux patch required
Click or tap to explore — scroll the page freely

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

Things people build with this

USE CASE 1

Enable Magisk modules that depend on the Zygisk API to work on a KernelSU-rooted Android device.

USE CASE 2

Replace Magisk's built-in Zygisk with this standalone implementation on a standard Magisk-rooted phone.

Tech stack

AndroidKernelSUMagisk

Getting it running

Difficulty · hard Time to first run · 1h+

Requires a KernelSU-rooted Android device with a kernel that has full SELinux patch support, README does not include step-by-step installation instructions.

In plain English

ZygiskNext is a standalone implementation of Zygisk for Android devices. To understand what this means, some background helps. Magisk is a widely used tool for rooting Android phones, and Zygisk is a feature built into Magisk that lets add-on modules inject code into apps at startup. It works by hooking into Zygote, the Android process that launches every app, so modifications can apply across the whole system. KernelSU is an alternative rooting approach that works at the Linux kernel level rather than through Magisk. Because it is a separate project, it does not include Zygisk natively. ZygiskNext fills that gap by providing a standalone Zygisk implementation that works with KernelSU. This means Magisk modules that rely on the Zygisk API can run on KernelSU-rooted devices through ZygiskNext. The project also works as a drop-in replacement for Magisk's own built-in Zygisk, for users who prefer to run the standalone version even on Magisk-rooted devices. When used this way, Magisk's built-in Zygisk option must be turned off. The README is brief and focused on requirements. For KernelSU, you need a minimum kernel version and KernelSU manager version, and the kernel must have full SELinux patch support. For Magisk, you need at least version 26402 with built-in Zygisk disabled. The README also notes one known limitation: isolated processes on Magisk's DenyList are not handled correctly. ZygiskNext guarantees Zygisk API compatibility but does not replicate all of Magisk's internal features. The repository does not include license or installation instructions in the README provided.

Copy-paste prompts

Prompt 1
I have KernelSU installed on my Android device and want to use a Magisk module that requires Zygisk, how do I install and configure ZygiskNext step by step?
Prompt 2
My ZygiskNext module is not injecting into some apps. How do I verify that my kernel has full SELinux patch support as required?
Prompt 3
How do I disable Magisk's built-in Zygisk option and switch to ZygiskNext as a standalone drop-in replacement?
Prompt 4
What are the exact minimum KernelSU manager version and kernel patch requirements to run ZygiskNext without issues?
Open on GitHub → Explain another repo

← dr-tsng on gitmyhub — every repo by this author, as a profile.

Verify against the repo before relying on details.