Zygisk next crashes after flashing and rebooting lsposed

[xCaptaiN09]

Steps to reproduce/复现步骤

1. Flash zygisk next
2. Reboot
3. Now zygisk next will be working fine
4. Flash lsposed (any version) jingmatrix here
5. Reboot
6. Now after reboot zygisk next will be crashed

Expected behaviour/预期行为

Sometimes bootloop 1 or 2 times, or zygisk next crashes, zygisk won't work

Actual behaviour/实际行为

Check these logs pls.. my zygisk next also crashes after flashing lsposed. Every versions of lsposed.
I asked ai and all.. most says it's not kernel problem. Lsposed is not updated to latest android 16 qpr2 . I will paste below:

CONFIG_STRICT_MEMORY_RWX is not set — that's not the issue then.

The SEGV_ACCERR on write to a specific address in zygote64 is lsplant trying to patch ART methods in memory that's mapped read-only by the ART runtime itself, not the kernel. This is an ART version mismatch issue between lsplant and Android 16 QPR2's ART.

This is not fixable from the kernel side. JingMatrix's v1.11.0 claims Android 16 support but the lsplant version bundled in it may not match the exact ART build in Evolution X Android 16 QPR2.

Check the syscall 142 issue separately — that's fixable:

grep "CONFIG_SECCOMP\b" arch/arm64/configs/cupida_defconfig

For LSPosed — your options are:

1. Wait for JingMatrix to push a build specifically tested against Evolution X Android 16 QPR2. The beta support in v1.11.0 was tested against AOSP Android 16 Beta 3, not Evolution X which may have different ART patches.

2. Report the crash to JingMatrix's GitHub issues with your logcat — they actively fix these.

3. Use root without LSPosed for now — Tricky Store + integrity modules cover most detection bypass needs without LSPosed.

The kernel itself is not the problem here. LSPosed simply hasn't caught up with Evolution X's specific Android 16 ART build.

Xposed Module List/Xposed 模块列表

Nothing

Root implementation/Root 方案

Sukisu ultra

System Module List/系统模块列表

Zygisk next, lsposed jingmatrix

LSPosed version/LSPosed 版本

Lsposed v1.11.0

Android version/Android 版本

Android 16 qpr2

Version requirement/版本要求

• I am using the latest debug build from GitHub Actions./我正在使用 GitHub Actions 中最新的调试版本。

Logs/日志

log.txt

[JingMatrix]

To exlude the possiblility that your are encountering a ZygiskNext bug, please test if NeoZygisk works with you.

[xCaptaiN09]

To exlude the possiblility that your are encountering a ZygiskNext bug, please test if NeoZygisk works with you.

•ReZygisk fails due to submodule version check
•NeoZygisk v2.3 flashed successfully
•NeoZygisk also crashes zygote — monitor: stopped(zygote crashed)
•This rules out Zygisk Next as the cause
•The crash is consistent across all Zygisk implementations on this ROM

[Dev4Mod]

Send the logs that are in the /data/adb/lspd/logs folder.

[xCaptaiN09]

tombstone_49.txt

Device: Realme X7 Max (RMX3031, MT6893)
ROM: Evolution X Android 16 QPR2 (ART build: March 2, 2026)
Kernel: Linux 4.19.325, SukiSU Ultra v40538, Tracepoint Hook
LSPosed: v1.9.2-7299 Irena / JingMatrix v1.11.0 — both crash
Zygisk: Zygisk Next 1.3.2

Crash:

signal 11 (SIGSEGV), code 2 (SEGV_ACCERR), fault addr 0x00000072e641e000 (write)
#00 pc __memcpy_aarch64_simd+48 /apex/com.android.runtime/lib64/bionic/libc.so
#1 pc 0x5346c /data/adb/modules/zygisk_lsposed/zygisk/arm64-v8a.so

Summary:
lsplant is attempting to write to a read-only ART memory region. This causes SIGKILL on zygote after ~5 seconds. Tested with both Zygisk Next and NeoZygisk — same crash on both, ruling out Zygisk implementation as the cause.

Also confirmed via dmesg:

avc: denied { read } for comm="main" dev="nsfs" scontext=u:r:zygote:s0 tcontext=u:object_r:unlabeled:s0
init: Service 'zygote' received SIGKILL

Possibly Evolution X QPR2 enforces stricter read-only ART memory mapping than other ROMs/devices. Only MT6893 Evo X user reporting this — small userbase may explain no prior reports.

[JingMatrix]

@xCaptaiN09 Please upload your logs as suggested by @Dev4Mod . It is a waste of time reading AI-generated rubbish.

[xCaptaiN09]

@xCaptaiN09 Please upload your logs as suggested by @Dev4Mod . It is a waste of time reading AI-generated rubbish.

KernelSU_bugreport_2026-03-08_09_19.tar.gz

lspd.zip

[JingMatrix]

Closing it as explained here: #560 (comment)