Skip to content

Vector not activated on Android 17 with KernelSU-Next, root starts after boot #1056

Closed

Description

@Bdeerb

Steps to reproduce/复现步骤

  1. Reboot the phone. Root (KernelSU-Next) is not available until it's launched manually.
  2. Launch KernelSU-Next and confirm NeoZygisk and Vector are enabled.
  3. Open the Vector app. It shows "Not activated."
  4. Restart zygote with su -c "setprop ctl.restart zygote". Vector still shows "Not activated."

Expected behaviour/预期行为

Vector shows as activated, and its framework is injected into system_server.

Actual behaviour/实际行为

Vector shows "Not activated." The status page shows Framework "—", Xposed API "—", SELinux policy "Not loaded", System framework "Not injected." Logcat shows NeoZygisk running but no Vector injection or SELinux-patch lines.

Xposed Module List/Xposed 模块列表

None

Root implementation/Root 方案

KernelSU-Next v3.4.2-98-g48501dad (33453-6)

System Module List/系统模块列表

NeoZygisk v2.4 (298-edfa820-debug)
Vector (3116-b28c4e0f-JingMatrix-Vector)

Vector version/Vector 版本

3116

Android version/Android 版本

Android 17 (API 37), Samsung Galaxy S26 Ultra (SM-S948B), stock Samsung firmware

Version requirement/版本要求

Logs/日志

Activity

  1. JingMatrix commented on Nov 5, 2026

    @JingMatrix
    Owner

    Please read #123 and upload logs, this is unlikely to be an issue of Vector.

  2. Bdeerb commented on Nov 5, 2026

    @Bdeerb
    Author

    Please read #123 and upload logs, this is unlikely to be an issue of Vector.

    I figured it out already, yes turned out not to be vector issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions