Magisk Module Logo
MagiskModule
ReZygisk logo

ReZygisk

Developed by @PerformanC

Dls
Ver
v1.0.0
Size
707.84 KB
Date
27 Jul 2026
rezygisk-2.md

ReZygisk (Standalone API Implementation)

ReZygisk is an open-source, standalone implementation of the Zygisk API framework designed for modern Android development environments like KernelSU, APatch, and Magisk. It integrates safely into the Android Zygote process, allowing developers and system administrators to apply UI tweaks and systemless modifications efficiently in an isolated manner.

I have been running this on my daily driver after migrating to KernelSU to maintain a stable operating system environment while utilizing my favorite system tweaks. Under the hood, it serves as an excellent open-source alternative to closed-source solutions, providing the security of a highly auditable codebase while flawlessly hooking standard systemless modules.

Core Features

  • Fully Open Source: Guarantees community-driven transparency and security, ensuring that the framework is highly auditable for developers and power users.
  • Advanced Process Isolation: Pairs flawlessly with APatch or KernelSU to provide a clean, isolated environment for testing and applying system-level modifications safely.
  • Direct Module Compatibility: Allows you to run standard Zygisk performance scripts and system UI tweaks smoothly without relying on traditional framework implementations.
  • Flexible Build Options: Choose the release zip for daily stability and optimized binaries, or grab the debug version if you are a developer needing to pull heavy system logs for troubleshooting.

Support & Requirements

  • Root Type: KernelSU, APatch, or Magisk (Magisk users must disable the built-in Zygisk option in settings to prevent conflicts).
  • Requirements: Android NDK environment.

How to Install

  1. Download the stable release zip from the GitHub repository.
  2. Open your preferred root manager (KernelSU, APatch, or Magisk), go to the Modules section, and flash the zip file.
  3. Reboot your phone and check the module description to verify the daemons (like 64-bit/32-bit monitors) are actively running.