failed-to-find-path-log-evidence.md 2.2 KB

LSPosed Vector: "Failed to find path" — Log Evidence

Environment

  • Device: Pixel 10 Pro Fold, Android 16
  • LSPosed: JingMatrix Vector (zygisk_vector module), daemon PID 1326
  • Module: com.example.wechathook (mid=42), APK at /data/app/~~UoAjGgM7d2OcyZ0ticf8eQ==/com.example.wechathook-nb7rrKopzyLkRLnyLrr1ww==/base.apk
  • Target: com.tencent.mm (WeChat 8.0.74)

Boot Sequence (verbose log)

12:08:48.648  VectorLogcat daemon starting
12:08:48.648  New log file: verbose_2026-07-04T12:08:48.648208.log
12:08:49.060  VectorNative: System server process detected. Marking for injection.
12:08:49.181  VectorNative: JNI table runtime size: %zu (compile-time: %zu)
12:08:49.186  VectorNative: IPC Bridge JNI hook installed successfully.
12:08:49.210  VectorNative: Injected Vector framework into system_server.
12:08:50.787  VectorZygiskBridge: Vector daemon service binder linked.
12:08:50.788  VectorDaemon: Successfully injected Vector IPC binder for applications.
12:08:51.549  VectorZygiskBridge: GET_BINDER, callerUid=10275
12:08:51.549  VectorConfigCache: System services are ready. Mapping modules and scopes.
12:08:51.570  VectorConfigCache: Failed to find path of com.example.wechathook  ← ROOT CAUSE

Key Observations

  1. Timing: "Failed to find path" occurs at 12:08:51.570 — only ~3 seconds after daemon start (12:08:48). PackageManager may not be fully ready for path resolution this early in boot.

  2. APK actually exists: pm path com.example.wechathook returns the correct path. The file is on disk with correct permissions (system:system, 644).

  3. Caching behavior: After the initial failure, lspd never retries. Subsequent GET_BINDER calls for com.tencent.mm (UID 10275 and others) do NOT trigger re-resolution. The negative result is cached.

  4. Module stays in DB: The module record in modules_config.db is correct (mid=42, enabled=1, scoped to com.tencent.mm). No DB fix needed.

  5. Recovery: Force-stop + reopen the target app. The fresh process start triggers a new GET_BINDER, and this time path resolution succeeds.

Verification After Recovery

# Should show the module .so or DEX in the app's memory map:
su -c 'cat /proc/$(pidof com.tencent.mm)/maps | grep wechathook'