How to Install LSPosed, or Its Successor Vector, and Enable Modules

The original LSPosed stopped at Android 14; its maintained fork Vector runs on 8.1 to 17. Which to install, the Zygisk setup you need, and how to enable modules.

LSPosed is the framework that runs Xposed modules on modern Android. Modules change how the system or individual apps behave, in memory, without modifying any APK, and turning one off and rebooting undoes it. Before installing, you need to know which LSPosed to get, because the original project has stopped.

Which one to install

LSPosed (original) Vector (maintained fork)
Latest release v1.9.2, October 2023 Ongoing (latest build September 2026)
Android versions 8.1 to 14 8.1 to 17 Beta
Root Magisk v24 or later Magisk or KernelSU
Needs Riru or Zygisk Zygisk (NeoZygisk, or ZygiskNext on KernelSU)

Android 15 or later: install Vector. The original LSPosed lists support only up to Android 14 and hasn’t had a release since 2023. Vector is the continuation of JingMatrix’s LSPosed fork, renamed, and keeps the same module API.

What you need first

  1. Root, with an unlocked bootloader: Magisk or KernelSU. The root solutions comparison helps you choose.
  2. Zygisk:
    • Magisk has Zygisk built in, as an option you enable in Magisk.
    • KernelSU has no built-in Zygisk. Its documentation points to ZygiskNext for running Zygisk modules, and Vector’s README suggests NeoZygisk. Install one of them first.

Install the framework

Following Vector’s README (the steps for the original LSPosed are the same apart from the download):

  1. Download the latest release zip from the project’s GitHub releases.
  2. Install it as a module in your root manager (Magisk or KernelSU).
  3. Make sure a Zygisk environment is active (see above).
  4. Reboot.
  5. Open the manager from the system notification that appears after boot.

Enable a module

Modules are ordinary APKs.

  1. Install the module’s APK, for example HideMockLocation or Global Icon Pack.
  2. In the LSPosed/Vector manager, open Modules and enable it.
  3. Choose its scope: the apps the module is allowed to hook. A module does nothing outside its scope. Many modules suggest a scope, and system-wide ones usually need the system framework.
  4. Reboot, or force-stop the apps in its scope, so they start again with the module loaded.

When a module doesn’t work

  • Check it’s enabled and the scope is right. This is the most common cause. A module that hooks Settings does nothing if only your launcher is in scope.
  • Reboot after changing a system-framework module. Hooks in system processes only take effect after a restart.
  • Check the module supports your Android version. Many modules target specific versions or ROMs, and the module’s own page says which.
  • Newer modules and older frameworks. Some modules use the newer libxposed API, for example HideMockLocation, Global Icon Pack and Pengeek on this site (we check the entry point inside each APK). If one of these doesn’t appear or doesn’t load, make sure you are running a current framework.
  • After a system update, check for a new module release before rebooting. Modules for manufacturer skins break most often.

The LSPosed modules list has nine open-source modules, each checked for the Xposed API and scanned for trackers.

Apps in this guide

Sources

Related topics