[BUG]: ReZygisk only shows monitor as working

[DexterEnigma]

Version

v1.0.0 (454-b5f0aa5-debug)

Reproducible since version

v1.0.0

System Information

OnePlus 13 (CPH2649_16.0.3.501(EX01), OxygenOS 16 Based on Android 16, January 2026 Security Patch)

Root Implementation Information

KernelSU Next v3.0.0 (32966)

Modules

☝️ Here are the modules installed. All Enabled.

Description

☝️ Says not working in the webui

☝️ Also only gives 1 green tick.

Even though, modules requiring zygisk like relsposed is working? Didn't notice any issues.

Steps to reproduce

1. Go to ksu next modules list
2. Find and open rezygisk web ui

Confirmations

• I am currently using the latest CI version of ReZygisk while reporting this Issue
• My environment meets the minimum requirements.
• I have ASSURED that no other Issue has been made about the same topic.
• I have acquired the MDA redacted log, utilizing the debug version of ReZygisk, and after creating this Issue, I will send it to performancorg@gmail.com or one of the project maintainers, with the GitHub Issue link included in the e-mail and the log attached.
• I have written, in all the fields above, using English, and I will be able to provide more information in English if required by the maintainers.

Code of Conduct

• I agree to follow this project's Code of Conduct

[ThePedroo]

I've analyzed the logs, and confirmed that such issues are specific to Magisk, since that might happen with a corrupt/improper installation, that leads to Magisk not set the selinux rules that ReZygisk requires to work.

You can verify that by collecting the MDA logs, and grepping for: "Failed to open remote". If a ReZygisk log appears, it is that, hence requiring a reinstallation.

[ThePedroo]

I really am not feeling well recently, I mixed up Issues 😭

[DexterEnigma]

I really am not feeling well recently, I mixed up Issues 😭

No worries 😄 I was just confused. Take your time. Thank You for your work

[ThePedroo]

Where did you send the logs? I will check the emails later, if you haven't sent yet

[DexterEnigma]

Where did you send the logs? I will check the emails later, if you haven't sent yet

Seems to have fixed by flashing rom's unpatched init_boot.img! Recommended by wild kernel support. Ig it was kernel related! Thank you for your support.