post-reboot-verification.md 1.5 KB

Post-Reboot Verification Checklist (JingMatrix Vector on A16)

Quick checklist for confirming LSPosed + modules are functional after a reboot.

Step 1: Daemon alive

su -c 'pidof lspd'

Expect: one or more PIDs. Empty = daemon crashed or never started → check zygote crash logs.

Step 2: Module in LSPosed DB

su -c 'strings /data/adb/lspd/config/modules_config.db | grep -i <module_package>'

Expect: package name + APK path. Missing = module was never registered or DB corrupted.

Step 3: Target app running

su -c 'pidof <target_package>'

If not running, launch it (am start or user opens manually).

Step 4: Module injected (memory-map check)

su -c 'cat /proc/$(pidof <target_package> | cut -d" " -f1)/maps | grep <module_name>'

Expect: lines mapping module's .so or .dex. Empty = module not injected.

Step 5: Module behavior check

The only definitive test. Check the module's own logcat output:

su -c 'logcat -d -s "<ModuleTag>:*" | tail -20'

Or test the module's actual function (e.g., if it hooks a method, trigger that method and check the result).

JingMatrix Vector quirks

  • verbose_*.log: only VectorZygiskBridge GET_BINDER debug lines — no module loading messages
  • modules_*.log: nearly empty (----part 1 start----) — useless for verification
  • logcat | grep lsposed: may not show anything useful on JingMatrix Vector
  • Module DB (modules_config.db) is the runtime source of truth — filesystem scope files are secondary