How to Install LSPosed in 2026: Vector, Zygisk, Magisk, KernelSU and APatch

You searched for LSPosed, found a 2023 tutorial that tells you to flash a zip, and now you are not sure that zip will even run on your Android version. That doubt is justified.

The short answer: in 2026 you install Vector, the maintained continuation of LSPosed, from its GitHub releases page, after your root manager has a working Zygisk environment. The original LSPosed v1.9.2 zip dates from October 2023 and its README stops at Android 14. Vector states support for Android 8.1 through 17 (its README says "17 Beta").¹⁴

The part most guides skip: KernelSU and APatch have no built-in Zygisk. On those you add a separate Zygisk module first, and you run only one Zygisk implementation at a time.¹¹¹⁶

Sources checked November 5, 2026. This is a documentation-based guide, not a claim that DroidRooter tested every phone, ROM or module mentioned. Where a menu label is not verified, the text says so.

Jump to: What changed · Do you need it? · Requirements · Which build · Before you start · Magisk · KernelSU · APatch · Zygisk choices · Open and verify · Modules and scopes · Updating · Troubleshooting · Removal · Security · DRVCAM · FAQ

What LSPosed is, and what changed by 2026

LSPosed is an ART hooking framework: it lets small add-on programs called modules change how apps and system services behave, using the original Xposed API. It is delivered as a Zygisk module, so it runs inside processes that your root manager's Zygisk layer starts.¹

The useful property is that hooks live in memory. No app APK is rewritten, so disabling a module and rebooting undoes the behaviour change. (Modules can still write files of their own, so "reversible" describes the hook, not everything a module might do.)⁴

Here is what happened to the project, with dates you can check:

• The original LSPosed repository has had no release since v1.9.2 on 2023-10-11 and no commit to its default branch since 2024-01-07. It is not archived, and other branches still receive pushes, so a GitHub visit may look busier than the releases page suggests. Its README lists "Android 8.1 ~ 14".¹²
• Vector is the former JingMatrix fork of LSPosed. Release v2.0 (2026-03-22) states that the project was renamed from LSPosed to Vector, with a rewritten Zygisk architecture. v2.1 (2026-08-02) is the first build on the modern libxposed API 101 and states Android 8.1 through 17, with a rebuilt manager. v2.2 (2026-08-04) is a hotfix for 2.1 that adds API 102 hot reload.⁵
• Only Vector states support for Android 15, 16 and 17. The original project has no statement for those versions, which is not the same as proof that it fails there.⁴¹

Xposed, EdXposed, LSPosed, Vector: one table

You will also see forks and rebrands named only in video titles. We could not verify them and do not recommend any.

Legacy API versus libxposed API

Vector supports both the legacy Xposed API and the newer libxposed API.⁴ For you that means older modules keep loading, while newer modules may be written for libxposed and expect Vector specifically. The module's own page says which.

Do you need this? What it can and cannot do

LSPosed-family frameworks need root and Zygisk. That means a rooted phone, and rooting through Magisk or KernelSU needs an unlocked bootloader. Magisk's install guide says so directly, and so does the KernelSU FAQ.¹⁰¹¹

Warning before you chase root for the first time: unlocking a bootloader normally erases the phone. On Samsung phones, Magisk's own documentation says first-time installation requires a full data wipe and permanently trips the Knox warranty bit.¹⁰ Back up first. If you are not rooted yet, read our Android rooting guide before anything else, and check your exact phone, because not every device can be rooted.

What a framework gives you is the ability to run modules that hook apps. What it does not give you:

• No guarantee that a given module works with a given app or Android build. Modules break when apps and Android change.
• No invisibility. Root and hooking can be detected, and some apps refuse to run. We make no undetectability claim and no promise about Play Integrity or banking apps.
• No "Xposed without root". Patched-APK and virtual-container tools exist and are a different technique with different trade-offs. We have not verified them and do not cover them.

If you want to know which modules exist, our Magisk and Xposed modules guide owns that question. This page stays on installing and fixing the framework.

Requirements by Android version and root manager

Read the row for your phone. "No maintained statement" is not a failure report.

The root layer matters just as much:

KernelSU's FAQ answers the framework question itself: you can use LSPosed or another modern Xposed derivative with Zygisk Next.¹¹ APatch's FAQ says it has no built-in Riru or Zygisk and that you add Zygisk through APatch modules.¹⁶

Which build to install

Naming pattern, so you can spot the real file: Vector stable assets look like Vector-v2.2-3080-Release.zip and Vector-v2.2-3080-Debug.zip. The original project's last assets were LSPosed-v1.9.2-7024-zygisk-release.zip and a Riru twin.⁵² If the release page lists a checksum, compare it with your download.

Release or Debug? Vector's README recommends Debug builds for people troubleshooting and says bug reports are accepted only from the latest debug build. For daily use, take Release.⁴ Canary builds are CI prereleases; most readers should run stable.⁵

Before you start: backup and recovery

A framework runs inside every ticked app's process, and a bad module can stop the phone from booting. Prepare the way back first.

1. Back up your data. Do this regardless of the framework, since you are about to flash modules as root.
2. Keep the stock boot or init_boot image for your exact build. Our guide to getting the correct boot or init_boot image shows how, and Magisk flash failed recovery covers the usual rescue.
3. Know your Safe Mode route.
4. Magisk: its FAQ says two failed boots in a row put it into a Safe Mode that disables all modules and Zygisk. You can also run magisk --remove-modules over adb, or reboot to Safe Mode from the app's reboot menu. The FAQ describes the key-combination timing, which can be fiddly.⁹
5. KernelSU: its rescue page says to press and release volume-down more than three times after the first boot screen. The page warns that the timing may not trigger on fast-booting devices, that a bad init rc line still runs in Safe Mode, and that you should never install modules from unknown sources.¹³
6. If you do end up in a loop, our Android boot loop guide and boot loop without losing data are the next stops.

Install on Magisk

Magisk has Zygisk built in, so this is the shortest path. Menu labels shift between Magisk versions; the Settings toggle below is the one our DRVCAM install guide documented with screenshots on a Magisk 31.x phone.²⁰

1. Turn Zygisk on. Open Magisk → Settings, find the Zygisk switch in the Magisk section and enable it. Magisk asks for a reboot.
2. Reboot, and confirm that Magisk's Home screen now reports Zygisk: Enabled.
3. Download Vector from the project's releases page (github.com/JingMatrix/Vector/releases): the stable Release.zip, not "Source code".
4. Modules → Install from storage, pick the zip, and let it finish.
5. Reboot.
6. Open the manager using one of the three routes in the next section.

Vector's README gives the same sequence in its own words: install through your root manager, make sure a Zygisk environment exists, reboot, then reach the settings through the system notification.⁴

Do not also install a standalone Zygisk module while Magisk's built-in Zygisk is on. ReZygisk's README tells Magisk users to disable the built-in one because the two conflict, and Zygisk Next's requirements say Magisk's built-in Zygisk must be off.¹⁸¹⁷

One version note: Magisk v31.1 removed reactive superuser prompts, so apps are granted access ahead of time in the Superuser tab.⁸ That matters for the Shell-root step in the troubleshooting matrix.

Install on KernelSU

1. Confirm your KernelSU manager shows working root. KernelSU officially supports GKI 2.0 kernels 5.10 and above.¹⁴
2. Do not run Magisk alongside it. KernelSU's documentation says its module system conflicts with Magisk's magic mount: if any module is enabled in KernelSU, Magisk stops working entirely.¹¹
3. Decide about a metamodule. KernelSU 3.x introduced metamodules, and its page says that without one, modules are not mounted. The FAQ qualifies this: a metamodule is needed for modules that modify files under /system, while scripts, sepolicy and system.prop work without one.¹²¹¹ We have not isolated whether Vector needs a mounted module. Our own DRVCAM install guide documents a KernelSU phone running Zygisk Next and Vector without mentioning a metamodule.²⁰ If any of your other modules touch /system, install a metamodule as the KernelSU page describes (for example meta-overlayfs, through the manager's add button, then reboot; only one at a time).
4. Install one Zygisk implementation from the Modules tab (Zygisk Next, ReZygisk or NeoZygisk; see the comparison). Reboot.
5. Install the Vector Release zip the same way. Reboot.
6. Open the manager (next section).

Zygisk Next's README lists a minimum KernelSU of 10940 and a minimum KernelSU manager (ksud) of 11575.¹⁷ Current KernelSU v3.3.1 is well past both, but check the README of whichever implementation you choose.

Install on APatch

1. APatch must be arm64, and your kernel must fall inside its stated 3.18 to 6.12 range.¹⁵
2. In the APatch manager, open the module list (APM), install one Zygisk implementation zip and reboot. Labels vary by version.
3. Install the Vector Release zip and reboot.
4. Open the manager (next section).

Three APatch notes. First, its FAQ lists a project called Zloader as an alternative but says it has had no commits since v0.1.3, no longer recommends it, and that it is incompatible with any Zygisk implementation. We do not recommend it either.¹⁶ Second, APatch's README states that the SuperKey has higher privileges than root access, so treat it like a root password.¹⁵ Third, if a module install fails with a shell-related error, the APatch FAQ advises removing root from the Shell app. That is the opposite of one Vector troubleshooting step, covered in the matrix below.¹⁶⁶

Choosing the Zygisk implementation

Vector, KernelSU and APatch all name these three without ranking them. The one rule they share: install exactly one.⁴¹¹¹⁶

Which one you pick is a trust and licensing preference as much as a technical one. The licence row is a fact you may want when choosing software that runs as root, not a quality ranking. If you already have a working setup, you do not need to change it.

Open the manager and verify it works

There is no separate manager APK to download. Vector's manager ships inside the module.⁶ Three ways to reach it, from the maintainer's own troubleshooting guide:

1. The system notification after reboot (the README route).
2. The root manager's Action button on the Vector module, if the notification does not show. Update Magisk or KernelSU first.
3. Install the manager as an ordinary app from the module folder over adb:

adb shell su -c cp /data/adb/modules/zygisk_vector/manager.apk /data/local/tmp && adb pull /data/local/tmp/manager.apk && adb install ./manager.apk

If the manager still will not open, the same guide says to grant root to the system Shell (com.android.shell) first. Read the warning in the troubleshooting matrix before doing that.⁶

The v2.1 manager was rebuilt in Jetpack Compose, so this guide describes screens by function rather than quoting labels.⁵

The checklist: pass or fail

• [ ] Your root manager shows Zygisk enabled (Magisk Home), or lists exactly one Zygisk module as enabled (KernelSU and APatch).
• [ ] The Vector module is listed and enabled in the root manager.
• [ ] The Vector manager opens and its home screen reports the framework as active.
• [ ] A real test. Install one small module you trust and whose source you can read, enable it, tick one target app as its scope, force-stop that app and reopen it. If the module's effect appears, the whole chain works.

If any line fails, jump to the matrix. The last line matters because a framework can report "active" while a module still does nothing.

Modules and scopes: how activation works

Three conditions must hold together before a module acts on an app:

1. The module is enabled in the manager.
2. The target app is ticked in the module's scope.
3. The target process was restarted after both.

The LSPosed wiki describes the same flow: modules install as regular apps, you switch the module on, then choose where it applies. Many modules display a recommended scope, which the manager selects automatically. Modules that do not hook system services only need the target app restarted; modules that hook the system framework need a reboot. LSPosed deliberately has no "Select All" for obsolete modules, and ticks should stay narrow: LSPosed injects only into ticked apps and leaves the rest in a clean environment.³

Multiple users: the wiki says the manager lives on the primary user and shows a tab per user. Install a module in the user profile where it should work.³

Hot reload: Vector v2.2 added hot reload for libxposed API 102 modules, so such modules can be swapped without killing the target process. Older modules still follow the restart rule.⁵

The manager also has a Repository page for finding modules. We do not list modules here; use the modules guide for choice and caution.

Updating, and switching from original LSPosed to Vector

Updating Vector: install the new zip over the old one through your root manager's Modules screen, then reboot. If you installed the manager as a separate app on 2.1, the v2.2 notes say to uninstall it before updating.⁵ If something breaks after an update, try the latest Debug build before filing a report, as the README asks.⁴

Switching from LSPosed v1.9.2:

1. Disable your modules in the old manager, remove the old LSPosed module in the root manager, and reboot.
2. Install Vector as described above. Do not run two frameworks.
3. Re-check every module's scope afterwards. We could not verify that module configuration carries over from LSPosed to Vector, so assume it does not.

After an Android or security update: update the root layer first, then the framework. The Magisk changelog shows that Zygisk support for new Android releases arrived in specific versions (16 QPR2 in v30.7, Android 17 in v31.0).⁸ We have not verified why any particular update broke any particular phone; check the projects' issue trackers for your build.

Troubleshooting matrix

The "likely cause" entries are our synthesis of what the documentation implies, not a ranking by frequency. Evidence tiers: P is a project document, C is a user report.

If Zygisk itself crashed, the maintainer's guide includes a command that pulls Vector's daemon logs from the data directory; copy it from the source rather than from memory.⁶

On GrapheneOS and other hardened systems: Vector v2.1's notes mention a fix for its manager under GrapheneOS's dynamic-code-loading restrictions.⁵ Community posts describe switching off further protections to get it working. That lowers the security of a hardened OS on the strength of one person's report, so we do not recommend it.⁶

Safe removal and rollback

Order matters.

1. In the Vector manager, disable the modules (or all modules), then reboot. This alone usually returns apps to normal, because hooks are applied in memory.⁴
2. In the root manager, disable or remove the Vector module, then reboot.
3. Remove the Zygisk implementation only if nothing else on the phone needs it. On Magisk you can simply turn the built-in Zygisk toggle off.
4. In an emergency, use the Safe Mode routes from Before you start.

Some modules write their own files and settings. Removing the framework does not undo those.

Security cautions

You are combining root with software that injects into other apps. Treat that seriously.

• Modules run with the reach of root. KernelSU's documentation warns that modules have root privileges and can cause irreversible damage, and tells readers not to install modules from unknown sources.¹³
• Download from the project's GitHub releases page only. Match the asset name to the pattern in Which build. Vector's README warns that CI builds from pull requests are often unstable and potentially unsafe; stick to master-branch builds. GitHub requires a login to download CI artifacts.⁴
• "LSPosed APK" sites are a poor source. There is no standalone manager APK in the normal flow, so a page offering one is not offering what the project distributes. The top video results for install queries also link zips on file-sharing hosts. We say that as an observation about the search results, not about any uploader's intent.
• Privacy. A module can read what the hooked app sees. Tick only the apps a module needs.
• APatch SuperKey is as sensitive as root itself.¹⁵

Using the framework for DRVCAM

DRVCAM is a virtual camera for rooted Android. Its product page says it runs on rooted Android 9 to 17 with an Xposed framework such as LSPosed, and our DRVCAM install guide uses Vector in that role, with screenshots from a Magisk phone and a KernelSU phone that end in the same state.²¹²⁰ What happens after the framework is in place is covered in the DRVCAM user manual and in how a virtual camera works on rooted Android.

The honest limits are DRVCAM's own: it needs root, and compatibility depends on your phone, your Android build and the apps you point it at. A working framework guarantees none of that. Use it only on your own phone and for lawful purposes.

The bottom line

In 2026, "install LSPosed" means: confirm your root manager, give it exactly one Zygisk, install Vector from its GitHub releases, open the manager, and prove it with one scoped test.

Do not install the 2023 zip because a tutorial said so. Do not stack two Zygisk implementations. Know your Safe Mode route before you flash anything. And treat every module as software with root-level reach, because it is.

Next step: if you are setting up DRVCAM, continue with our DRVCAM install guide and the DRVCAM page. It needs a rooted phone, and results depend on your phone, Android build and apps. If you are stuck in a bootloop or cannot get root working, DroidRooter offers remote rooting and recovery help. The service checks the exact device first and says plainly when a path is not safe to attempt. Not sure your phone can be rooted at all? Start with the rooting guide, and back up first.

Last verified, November 5, 2026 (re-check before relying on these): Vector v2.2 (2026-08-04), Magisk v31.1, KernelSU v3.3.1 (2026-10-12), APatch 11282 (2026-10-15), ReZygisk v1.0.0, NeoZygisk v2.4, Zygisk Next v1.5.2 (2026-10-15).

Sources and project documentation