[BUG]: Zygisk Failing

[waterpolo]

Version

1.0.0

Reproducible since version

1.0.0 RC8

System Information

Samsung Galaxy S23

Root Implementation Information

Magisk 30.7

Modules

The modules which are failing are listed below:

• Integrity box
• Zygisk - LSPosted
• Integrity box zygisk-detach

Description

After the reboot, when the latest release 1.0.0 is installed, the modules which use Zygisk are failing. The give an error that Zygisk isn't detected.

Steps to reproduce

Installed multiple times. Also RC9 was failing.
Revert back to previous release RC7 which is working fine.

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]

Logs..?

[waterpolo]

Edit: Deleted log

[Cris--]

Same here with some modules. Don't know if it is the same bug...

magisk_log_2026-05-20T12.06.36.log

[ThePedroo]

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.

Please read carefully next time. The checkboxes are not to be ignored, I wrote them for good reasons

[Cris--]

Debug Assistent log:

... deleted.

[ThePedroo]

Are those with -debug ReZygisk?

You also shouldn't be sending MDA publicly, as stated -- they, even through Secure Censor, could still include sensitive information.

[Cris--]

Without -debug.

[ThePedroo]

utilizing the debug version of ReZygisk

😭😭😭😭😭😭😭😭😭😭😭

[Cris--]

ok, uninstall ReZygisk, reboot, install ReZygisk debug, reboot, grab log from Debug Assistent?

How can i prevent sensible informations in the log?

[lubozzz]

If I'm right, it is somehow connected with module zygisk-detach. I had same problem and if I disabled/removed zygisk-detach, rezygisk starts work.

[ThePedroo]

ok, uninstall ReZygisk, reboot, install ReZygisk debug, reboot, grab log from Debug Assistent?

How can i prevent sensible informations in the log?

Can only be reduced, not fully removed. Not with 100% certainty, at least.

[waterpolo]

If I'm right, it is somehow connected with module zygisk-detach. I had same problem and if I disabled/removed zygisk-detach, rezygisk starts work.

I can confirm that by disabling the zygisk-detach module that Zygisk is working. The other modules which using Zygisk are working properly.
The question is in which module the issue is.

[waterpolo]

I created an issue by zygisk-detach, but the owner closed the issue directly with comment 'do not report issues of zygisk modules'
The modules has to work together.
I am revert to V10.0 RC7 which is working with Zygisk-detach.