Zygote crash on Pixel 10 Pro A17 beta3

[nezorflame]

Steps to reproduce/复现步骤

• Freshly reset Pixel 10 Pro, build CP21.260306.017
• SukiSU_v4.1.2_40545-release app
• ShirkNeko v2.1.0-r1 android15-6.6.102-2025-10 image

Expected behaviour/预期行为

System loads fine, SukiSU manager opens, NeoZygisk shows successful status, Vector can be opened

Actual behaviour/实际行为

System seemingly has 2-3 SystemUI crashes before load, SukiSU manager opens, NeoZygisk shows error "stopped(zygote crashed)"

Xposed Module List/Xposed 模块列表

None

Root implementation/Root 方案

SukiSU v4.1.2_40545

System Module List/系统模块列表

- Latest debug master CI build `Vector-v2.0-3032-Debug`
- Latest debug master CI build `NeoZygisk-v2.3-281-42715ff-debug`

LSPosed version/LSPosed 版本

3032

Android version/Android 版本

Pixel 10 Pro, A17 beta3 (build CP21.260306.017)

Version requirement/版本要求

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

Logs/日志

KernelSU_bugreport_2026-04-06_01_27.tar.gz

[nezorflame]

Same happens if Zygisk implementation is changed to Zygisk-Next-1.3.3-731-1193e46-release (didn't find any debug version for it):
error Stop inject zygote due to crash

[JingMatrix]

Please upload the folder /data/adb/lspd/log as logs.
Zygisk-Next is a closed source project, we cannot get useful debug logs.

[nezorflame]

kmsg.log
modules_2026-04-06T15:00:50.566548.log
props.txt
verbose_2026-04-06T15:00:50.565088.log

[nezorflame]

@JingMatrix do you want me to switch back to NeoZygisk instead so that we can get more logs? Atm I can experiment with the phone since it's not my daily driver yet

[JingMatrix]

It is problem of your KernelSU installation. Patch your boot image anew and update KSU managers.

[nezorflame]

Do you have any suggestion as for which variant is best for Vector compatibility-wise? Or just try them all until one works?

[JingMatrix]

Simply use the official KernelSU.

Your problem is not that certain variants don't work, but it is you didn't install them correctly.

[nezorflame]

Weird, I assumed PixelFlasher would do the job correctly.
Thanks again for your feedback!