Vector daemon crashed

[peasoft]

Steps to reproduce/复现步骤

1. Flash Vector from https://github.com/JingMatrix/Vector/actions/runs/25112885824
2. Reboot
3. Vector daemon crashed
4. Both Zygisk and ReZygisk don't work

Expected behaviour/预期行为

It should work.

Actual behaviour/实际行为

Vector daemon crashed.

Xposed Module List/Xposed 模块列表

N/A

Root implementation/Root 方案

Magisk

System Module List/系统模块列表

ReZygisk v1.0.0
TEESimulator v3.2
Vector v2.0

LSPosed version/LSPosed 版本

3043

Android version/Android 版本

Android 10 / ColorOS 7.1

Version requirement/版本要求

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

Logs/日志

verbose_2026-05-30T14:11:55.647.log

[saadtahir995]

got the same issue

[alienyang]

+1

[JingMatrix]

The logs show database corruption:

[ 2026-05-30T14:12:21.305 0: 1804: 1804 E/VectorDaemon ] Failed to inject VectorService into system_server
[ 2026-05-30T14:12:21.305 0: 1804: 1804 W/VectorDaemon ] Restarting system_server...
[ 2026-05-30T14:12:21.343 0: 1804: 1804 E/SQLiteLog ] (14) cannot open file at line 36937 of [68b898381a]
[ 2026-05-30T14:12:21.343 0: 1804: 1804 E/SQLiteLog ] (14) os_unix.c:36937: (13) lstat(/data/adb/lspd/config/modules_config.db) - 
[ 2026-05-30T14:12:21.346 0: 1804: 1804 E/SQLiteDatabase ] Failed to open database '/data/adb/lspd/config/modules_config.db'.
android.database.sqlite.SQLiteCantOpenDatabaseException: unknown error (code 14 SQLITE_CANTOPEN): Could not open database
	at android.database.sqlite.SQLiteConnection.nativeOpen(Native Method)
	at android.database.sqlite.SQLiteConnection.open(SQLiteConnection.java:215)
	at android.database.sqlite.SQLiteConnection.open(SQLiteConnection.java:197)
	at android.database.sqlite.SQLiteConnectionPool.openConnectionLocked(SQLiteConnectionPool.java:505)
	at android.database.sqlite.SQLiteConnectionPool.open(SQLiteConnectionPool.java:206)
	at android.database.sqlite.SQLiteConnectionPool.open(SQLiteConnectionPool.java:198)
	at android.database.sqlite.SQLiteDatabase.openInner(SQLiteDatabase.java:915)
	at android.database.sqlite.SQLiteDatabase.open(SQLiteDatabase.java:895)
	at android.database.sqlite.SQLiteDatabase.openDatabase(SQLiteDatabase.java:759)
	at android.database.sqlite.SQLiteDatabase.openDatabase(SQLiteDatabase.java:748)
	at android.database.sqlite.SQLiteOpenHelper.getDatabaseLocked(SQLiteOpenHelper.java:374)
	at android.database.sqlite.SQLiteOpenHelper.getReadableDatabase(SQLiteOpenHelper.java:341)
	at org.matrix.vector.daemon.data.PreferenceStore.getModulePrefs$default(PreferenceStore.kt:15)
	at org.matrix.vector.daemon.data.PreferenceStore.isVerboseLogEnabled(PreferenceStore.kt:95)
	at org.matrix.vector.daemon.ipc.ManagerService.isVerboseLog(ManagerService.kt:239)
	at org.matrix.vector.daemon.VectorDaemon.main(VectorDaemon.kt:103)
	at com.android.internal.os.RuntimeInit.nativeFinishInit(Native Method)
	at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:338)
[ 2026-05-30T14:12:21.347 0: 1804: 1804 E/SQLiteOpenHelper ] Couldn't open /data/adb/lspd/config/modules_config.db for writing (will try read-only):
android.database.sqlite.SQLiteCantOpenDatabaseException: unknown error (code 14 SQLITE_CANTOPEN): Could not open database
	at android.database.sqlite.SQLiteConnection.nativeOpen(Native Method)
	at android.database.sqlite.SQLiteConnection.open(SQLiteConnection.java:215)
	at android.database.sqlite.SQLiteConnection.open(SQLiteConnection.java:197)
	at android.database.sqlite.SQLiteConnectionPool.openConnectionLocked(SQLiteConnectionPool.java:505)
	at android.database.sqlite.SQLiteConnectionPool.open(SQLiteConnectionPool.java:206)
	at android.database.sqlite.SQLiteConnectionPool.open(SQLiteConnectionPool.java:198)
	at android.database.sqlite.SQLiteDatabase.openInner(SQLiteDatabase.java:915)
	at android.database.sqlite.SQLiteDatabase.open(SQLiteDatabase.java:895)
	at android.database.sqlite.SQLiteDatabase.openDatabase(SQLiteDatabase.java:759)
	at android.database.sqlite.SQLiteDatabase.openDatabase(SQLiteDatabase.java:748)
	at android.database.sqlite.SQLiteOpenHelper.getDatabaseLocked(SQLiteOpenHelper.java:374)
	at android.database.sqlite.SQLiteOpenHelper.getReadableDatabase(SQLiteOpenHelper.java:341)
	at org.matrix.vector.daemon.data.PreferenceStore.getModulePrefs$default(PreferenceStore.kt:15)
	at org.matrix.vector.daemon.data.PreferenceStore.isVerboseLogEnabled(PreferenceStore.kt:95)
	at org.matrix.vector.daemon.ipc.ManagerService.isVerboseLog(ManagerService.kt:239)
	at org.matrix.vector.daemon.VectorDaemon.main(VectorDaemon.kt:103)
	at com.android.internal.os.RuntimeInit.nativeFinishInit(Native Method)
	at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:338)
[ 2026-05-30T14:12:21.347 0: 1804: 1804 E/SQLiteLog ] (14) cannot open file at line 36937 of [68b898381a]
[ 2026-05-30T14:12:21.347 0: 1804: 1804 E/SQLiteLog ] (14) os_unix.c:36937: (13) lstat(/data/adb/lspd/config/modules_config.db) - 
[ 2026-05-30T14:12:21.348 0: 1804: 1804 E/SQLiteDatabase ] Failed to open database '/data/adb/lspd/config/modules_config.db'.
android.database.sqlite.SQLiteCantOpenDatabaseException: unknown error (code 14 SQLITE_CANTOPEN): Could not open database
	at android.database.sqlite.SQLiteConnection.nativeOpen(Native Method)
	at android.database.sqlite.SQLiteConnection.open(SQLiteConnection.java:215)
	at android.database.sqlite.SQLiteConnection.open(SQLiteConnection.java:197)
	at android.database.sqlite.SQLiteConnectionPool.openConnectionLocked(SQLiteConnectionPool.java:505)
	at android.database.sqlite.SQLiteConnectionPool.open(SQLiteConnectionPool.java:206)
	at android.database.sqlite.SQLiteConnectionPool.open(SQLiteConnectionPool.java:198)
	at android.database.sqlite.SQLiteDatabase.openInner(SQLiteDatabase.java:915)
	at android.database.sqlite.SQLiteDatabase.open(SQLiteDatabase.java:895)
	at android.database.sqlite.SQLiteDatabase.openDatabase(SQLiteDatabase.java:759)
	at android.database.sqlite.SQLiteDatabase.openDatabase(SQLiteDatabase.java:748)
	at android.database.sqlite.SQLiteOpenHelper.getDatabaseLocked(SQLiteOpenHelper.java:384)
	at android.database.sqlite.SQLiteOpenHelper.getReadableDatabase(SQLiteOpenHelper.java:341)
	at org.matrix.vector.daemon.data.PreferenceStore.getModulePrefs$default(PreferenceStore.kt:15)
	at org.matrix.vector.daemon.data.PreferenceStore.isVerboseLogEnabled(PreferenceStore.kt:95)
	at org.matrix.vector.daemon.ipc.ManagerService.isVerboseLog(ManagerService.kt:239)
	at org.matrix.vector.daemon.VectorDaemon.main(VectorDaemon.kt:103)
	at com.android.internal.os.RuntimeInit.nativeFinishInit(Native Method)
	at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:338)
[ 2026-05-30T14:12:21.349 0: 1804: 1804 D/AndroidRuntime ] Shutting down VM
[ 2026-05-30T14:12:21.350 0: 1804: 1804 E/AndroidRuntime ] FATAL EXCEPTION: main
PID: 1804
android.database.sqlite.SQLiteCantOpenDatabaseException: unknown error (code 14 SQLITE_CANTOPEN): Could not open database
	at android.database.sqlite.SQLiteConnection.nativeOpen(Native Method)
	at android.database.sqlite.SQLiteConnection.open(SQLiteConnection.java:215)
	at android.database.sqlite.SQLiteConnection.open(SQLiteConnection.java:197)
	at android.database.sqlite.SQLiteConnectionPool.openConnectionLocked(SQLiteConnectionPool.java:505)
	at android.database.sqlite.SQLiteConnectionPool.open(SQLiteConnectionPool.java:206)
	at android.database.sqlite.SQLiteConnectionPool.open(SQLiteConnectionPool.java:198)
	at android.database.sqlite.SQLiteDatabase.openInner(SQLiteDatabase.java:915)
	at android.database.sqlite.SQLiteDatabase.open(SQLiteDatabase.java:895)
	at android.database.sqlite.SQLiteDatabase.openDatabase(SQLiteDatabase.java:759)
	at android.database.sqlite.SQLiteDatabase.openDatabase(SQLiteDatabase.java:748)
	at android.database.sqlite.SQLiteOpenHelper.getDatabaseLocked(SQLiteOpenHelper.java:384)
	at android.database.sqlite.SQLiteOpenHelper.getReadableDatabase(SQLiteOpenHelper.java:341)
	at org.matrix.vector.daemon.data.PreferenceStore.getModulePrefs$default(PreferenceStore.kt:15)
	at org.matrix.vector.daemon.data.PreferenceStore.isVerboseLogEnabled(PreferenceStore.kt:95)
	at org.matrix.vector.daemon.ipc.ManagerService.isVerboseLog(ManagerService.kt:239)
	at org.matrix.vector.daemon.VectorDaemon.main(VectorDaemon.kt:103)
	at com.android.internal.os.RuntimeInit.nativeFinishInit(Native Method)
	at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:338)
[ 2026-05-30T14:12:21.350 0: 1804: 1804 E/VectorDaemon ] Uncaught exception in Daemon
android.database.sqlite.SQLiteCantOpenDatabaseException: unknown error (code 14 SQLITE_CANTOPEN): Could not open database
	at android.database.sqlite.SQLiteConnection.nativeOpen(Native Method)
	at android.database.sqlite.SQLiteConnection.open(SQLiteConnection.java:215)
	at android.database.sqlite.SQLiteConnection.open(SQLiteConnection.java:197)
	at android.database.sqlite.SQLiteConnectionPool.openConnectionLocked(SQLiteConnectionPool.java:505)
	at android.database.sqlite.SQLiteConnectionPool.open(SQLiteConnectionPool.java:206)
	at android.database.sqlite.SQLiteConnectionPool.open(SQLiteConnectionPool.java:198)
	at android.database.sqlite.SQLiteDatabase.openInner(SQLiteDatabase.java:915)
	at android.database.sqlite.SQLiteDatabase.open(SQLiteDatabase.java:895)
	at android.database.sqlite.SQLiteDatabase.openDatabase(SQLiteDatabase.java:759)
	at android.database.sqlite.SQLiteDatabase.openDatabase(SQLiteDatabase.java:748)
	at android.database.sqlite.SQLiteOpenHelper.getDatabaseLocked(SQLiteOpenHelper.java:384)
	at android.database.sqlite.SQLiteOpenHelper.getReadableDatabase(SQLiteOpenHelper.java:341)
	at org.matrix.vector.daemon.data.PreferenceStore.getModulePrefs$default(PreferenceStore.kt:15)
	at org.matrix.vector.daemon.data.PreferenceStore.isVerboseLogEnabled(PreferenceStore.kt:95)
	at org.matrix.vector.daemon.ipc.ManagerService.isVerboseLog(ManagerService.kt:239)
	at org.matrix.vector.daemon.VectorDaemon.main(VectorDaemon.kt:103)
	at com.android.internal.os.RuntimeInit.nativeFinishInit(Native Method)
	at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:338)
[ 2026-05-30T14:12:21.351 0: 1804: 1804 I/lspd ] System.exit called, status: 1
[ 2026-05-30T14:12:21.352 0: 1804: 1804 I/AndroidRuntime ] VM exiting with result code 1.
[ 2026-05-30T14:12:21.360 0: 1804: 2131 F/libc ] Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x44f97b7797d1f833 in tid 2131 (Jit thread pool), pid 1804 (main)

How did you install Vector ? It might be resulted from an overwriting installation.

Youy may quickly fix it by deleting the folder /data/adb/lspd/config and reboot.

[jiggs82]

I had troubles creating new issue so I'll have to post it here but lsposed isn't working correctly on a17 qpr1 beta 4 that just came out.

P10PROXL

[solirf]

I had troubles creating new issue so I'll have to post it here but lsposed isn't working correctly on a17 qpr1 beta 4 that just came out.

P10PROXL

Lastest Action version ( Vector-v2.0-3043-Release.zip ) works perfect

[peasoft]

You may quickly fix it by deleting the folder /data/adb/lspd/config and reboot.

I've tried these commands before but no luck:

rm -rf /data/adb/lspd/config/*
# reboot
chmod -R 777 /data/adb/lspd/config
# reboot

[peasoft]

BTW, tried https://github.com/JingMatrix/Vector/actions/runs/23718226859 (3027). I can open LSPosed Manager, the Module page says 10 modules enabled but the module list is empty. Running /data/adb/lspd/cli will get Aborted.

[ashir6892]

Same issue on OnePlus CPH2653EEA / Android 16 / KernelSU

Device: OnePlus CPH2653EEA, Android 16 (Kernel 6.6.89), KernelSU 32525, Zygisk Next 1.4.3, Vector v2.0 (3048)

Problem

After hard reboot, the lspd daemon enters a crash loop with StackOverflowError in libunwindstack.so (__cxa_demangle infinite recursion on binder threads). This causes:

1. Daemon crashes on binder thread with SIGSEGV (SEGV_ACCERR) — stack pointer near top of stack
2. system_server dies as a result
3. Daemon detects death and attempts reinjection → new daemon instance spawns
4. New daemon also crashes with the same StackOverflowError → infinite loop
5. The manager shows the bug report warning UI instead of the framework UI

After soft reboot (zygote restart), the issue does not occur — only after full hard reboot.

Tombstone signature

Process: lspd (uid 0)
signal 11 (SIGSEGV), code 2 (SEGV_ACCERR)
Cause: stack pointer is close to top of stack; likely stack overflow.
Abort message: JNI FatalError called: java.lang.Error thrown during binder transaction:
 (Error was StackOverflowError) (toString() error was StackOverflowError)
#00 libunwindstack.so itanium_demangle::AbstractManglingParser::parseClassEnumType()

system_server also crashes during the loop:

Process: system_server (uid 1000)
Failed to recognize implicit suspend check; thread state = Runnable

Root cause (workaround found)

Stale reinjection state files from the previous boot session persist across hard reboots and cause the daemon to enter a bad state during initialization:

• vector_reinjection_owner
• vector_reinjection_owner.lock
• vector_reinjection_restart.lock
• vector_reinjection_round
• lock

Workaround

Cleaning these files in a KernelSU module post-fs-data.sh (runs before Zygote) prevents the crash loop:

#!/system/bin/sh
rm -f /data/adb/lspd/vector_reinjection_owner
rm -f /data/adb/lspd/vector_reinjection_owner.lock
rm -f /data/adb/lspd/vector_reinjection_restart.lock
rm -f /data/adb/lspd/vector_reinjection_round
rm -f /data/adb/lspd/lock

Suggested fix

The daemon should clean stale reinjection state on startup if the previous owner PID no longer exists, or add a timeout/expiry to these state files so they do not persist across reboots.

Note: Modifying the daemon script with -Xss8m to increase Java thread stack size caused system_server to crash with Failed to recognize implicit suspend check (ART mutator lock corruption), so that is not a viable fix.

[JingMatrix]

@peasoft, your build 3043 predates #793: on Android 10 the daemon never claimed the serial service name, so the Zygisk module could not find it and aborted the injection, and the SQLite error is only the daemon dying afterwards. The same failure was reported in #773 and has been fixed on master since build 3050. Could you try the latest build from GitHub Actions and tell me if it works now?

[JingMatrix]

@ashir6892, the vector_reinjection_* files do not come from Vector — that string appears nowhere in the source, and the daemon keeps its re-injection state in memory only. You seem to be using a fork.