LSPosed, Shamiko, and dozens of the most powerful Magisk modules all share one dependency: Zygisk. When Zygisk Next — the de-facto standalone Zygisk implementation for KernelSU and APatch — went closed-source, the Android rooting community lost the ability to audit a module running with full root access to the entire system. ReZygisk by PerformanC is the open-source answer: a fully auditable, FOSS-licensed fork of Zygisk Next, codebase being rewritten to C for maximum efficiency, providing complete Zygisk API compatibility across Magisk, KernelSU, APatch, and KSUNext.
Why ReZygisk?
Open source. Auditable. Rewritten in C. The transparent Zygisk implementation the community deserves.
Fully Open Source (AGPL / GPL)
Every line of ReZygisk is publicly auditable under GPL (Dr-TSNG's original code) and AGPL 3.0 (PerformanC's rewritten components). A module that runs with root access to your entire system should always be open to scrutiny — ReZygisk makes that non-negotiable.
C Codebase Rewrite
PerformanC is rewriting the Zygisk daemon codebase (ReZygiskd) in pure C — replacing the original C++ implementation. C provides lower runtime overhead, tighter memory control, and a smaller binary footprint while maintaining the same Zygisk API compatibility.
Universal Root Manager Support
Provides Zygisk API support across all major root managers simultaneously: Magisk (Official), Magisk Kitsune/Delta, KernelSU, APatch, and KSUNext. A single unified Zygisk implementation that works anywhere you are rooted.
Built-in WebUI
ReZygisk ships with a WebUI accessible from within the root manager's module list. It shows real-time daemon status — monitor, zygote64/32 injection state, and daemon running state — with multi-language support via Crowdin translations.
SoInfo Hiding
Implements SoInfo hiding — drops information about libzygisk.so by hooking into pthread_attr_setstacksize. This conceals ReZygisk's presence at the native library level, reducing detectability for apps that scan for Zygisk injection artifacts.
64-bit & 32-bit Support
Deploys separate daemon instances for 64-bit and 32-bit processes simultaneously. Modules that hook into 32-bit apps (required on some older or dual-environment devices) are fully supported alongside native 64-bit module operations.
What Is Zygisk — And Why Everything Depends on It
Zygote is the first user-space process started by the Android kernel after boot. Every Android application is a fork of Zygote — when you launch an app, Android forks the Zygote process and uses that fork as the new app's process. This means Zygote is the parent of every app on the device.
Zygisk (Zygote + sk) exploits this architecture by injecting code into the Zygote process itself. Because every app is a Zygote fork, any code injected into Zygote is automatically present in every app process that is subsequently launched. This is how LSPosed can hook into the framework of any app at startup — it doesn't need to patch each app individually; Zygisk does the delivery at the fork level.
Magisk originally shipped Zygisk as a built-in feature. Zygisk Next (by Dr-TSNG and 5ec1cff) later provided a standalone version for KernelSU and APatch users who don't use Magisk. When Zygisk Next went closed-source, ReZygisk stepped in as the open-source fork — carrying the same complete Zygisk API so that all existing Zygisk modules continue to work without modification.
ReZygisk vs Zygisk Next
| Feature | Zygisk Next | ReZygisk |
|---|---|---|
| Open source / auditable | Closed source | AGPL/GPL |
| Magisk (Official) support | ||
| KernelSU support | ||
| APatch support | ||
| KSUNext support | ||
| Built-in WebUI | ||
| SoInfo hiding | ||
| Codebase language | C++ | C (rewrite in progress) |
Installation Guide
Always download the Release build for daily use. Use the Debug build only when collecting logs for a bug report.
- Open Magisk Manager → Settings
- Toggle Zygisk OFF
- Reboot
- Flash ReZygisk-release.zip via Magisk Modules
- Reboot
- Open your root manager's module section
- Flash ReZygisk-release.zip
- Reboot
- No prior Zygisk disable needed
[monitor: 😋 tracing, zygote64: 😋 injected, daemon64: 😋 running (...)]. Or open the WebUI from the module entry to see status visually.
Frequently Asked Questions
module.prop. No module changes are needed when switching from Magisk's built-in Zygisk or Zygisk Next to ReZygisk.