vector-v2-a16-crash-log.md 2.44 KB

Vector v2.0 Crash on Android 16 — Field Notes

Date: 2026-06-28
Device: Google Pixel 10 Pro Fold
Android: 16 (API 36)
Module: zygisk_vector (Vector v2.0, versionCode=3021, JingMatrix fork)
Zygisk .so size: 1,219,416 bytes (installed at /data/adb/modules/zygisk_vector/zygisk/arm64-v8a.so)

Verdict: STILL BROKEN ❌

Despite claiming "Android 8.1 ~ 16" support, Vector v2.0 crashes zygote on A16 with the same pattern as official LSPosed v1.9.2.

Crash Chain

The crash does NOT happen at initial boot — it's triggered when LSPosedService tries to restart system_server after the bridge fails to respond:

[2026-06-28T17:28:43] LSPosedService: system restarted...
[2026-06-28T17:28:43] LSPosedService: no response from bridge, retry in 1s
[2026-06-28T17:28:44] LSPosedService: no response from bridge, retry in 1s
[2026-06-28T17:28:45] LSPosedService: no response from bridge, retry in 1s
[2026-06-28T17:28:46] LSPosedService: no response from bridge
[2026-06-28T17:28:46] LSPosedService: System server injection fails, trying a restart
[2026-06-28T17:28:46] Magisk: ** zygote restarted
[2026-06-28T17:28:46] Magisk: zygote crashed too many times, rolling-back
[2026-06-28T17:28:46] LSPosedService: service activity is dead.
[2026-06-28T17:28:46] LSPosedService: clear ServiceManager
[2026-06-28T17:28:46] LSPosedService: system server died
[2026-06-28T17:28:46] LSPosedService: service activity is not started, wait 1s.
... (loops forever)

Post-Crash State

  • Zygisk: Rolled back by Magisk (disabled)
  • lspd daemon: Not running (pidof lspd → empty)
  • LSPosed .so in zygote64 maps: Not present
  • xhshook module: Config exists but never injects
  • Magisk DB: Zygisk entry missing from policies table

Root Cause (Hypothesis)

The crash happens during nativeForkSystemServer when LSPosedService restarts system_server. This is the same negative buffer capacity in NewDirectByteBuffer JNI error seen with official v1.9.2. JingMatrix's ART compatibility fixes in v1.10+ did not resolve this for Pixel 10 Pro Fold on A16.

Magisk Daemon Crash Side Effect

After attempting magisk --sqlite "INSERT OR REPLACE INTO policies..." to re-enable Zygisk, the Magisk daemon became completely unresponsive. All su commands returned:

Cannot connect to daemon: Connection refused (os error 111)

This persisted across all su paths (/debug_ramdisk/su, default su). Only a manual reboot restores the daemon.