How to Install Xposed Modules in VMOS Pro (LSPosed Guide)

You want GravityBox, Hide My Applist, or another module, but you do not want to unlock your real bootloader. This guide shows how to install Xposed modules in VMOS Pro — first with the built-in framework toggle, then with a full LSPosed VMOS Pro tutorial on the 64-bit ROM. Follow the order below so the VM boots again after you enable a module.

Table of Contents

Before You Start: Requirements

Xposed sits on top of a working VM. Do not start here if the virtual Android has never booted.

Check Minimum Recommended
Host Android 5.1 9–13 (14/15 need extra boot fixes)
VM ROM Geek 7.1 or 9.0 64-bit Android 9.0 64-bit for LSPosed
Free storage 8 GB 16 GB+ (Magisk ZIP + modules)
RAM for the VM 2 GB 3 GB
Root in the VM Required Confirm with Root Checker first
Battery 50% Charged + Wi-Fi
  1. Finish a clean first boot. Use the VMOS Pro setup guide after install if the VM is not stable yet.
  2. Turn on root inside the VM only. Your real phone stays unrooted. See how to enable root in VMOS Pro.
  3. Export the VM before you flash anything. A bad module can bootloop the virtual system. Export is your undo button.
  4. Back up photos and chats on the host phone anyway. VMOS Pro does not rewrite your real system, but you still should not skip a backup.

Xposed vs LSPosed vs Built-in Framework Toggle

Three tools share a similar job: they let modules change app or system behaviour without a custom recovery on your real phone. They are not the same binary.

Built-in Xposed toggle (VMOS Pro settings). Some Geek / Dual ROMs include “Xposed” next to Root and Google services. You flip it, reboot the VM, and install the old Xposed Installer APK. This is the VMOS Pro Xposed framework enable path. It is the easiest option, and it usually matches Android 5.1 / 7.1 Geek images — not every 9.0 ROM.

Classic Xposed. The original rovo89 framework. It fits old Android (especially 7.x). Modules must match that Android version. A GravityBox for Android 11 will not work here.

LSPosed (via Magisk). On Android 9 inside the VM, classic Xposed is the wrong stack. You install Magisk in a VMOS Pro virtual machine, turn on Zygisk, then install LSPosed. Modern modules (Hide My Applist, many Android 9+ hooks) expect this path.

Pick one stack per VM. Do not enable the built-in Xposed toggle and Magisk/LSPosed on the same machine. Two frameworks fighting over Zygote is a common bootloop.

Enabling the Built-in Xposed Toggle

Use this if your ROM already shows an Xposed switch. This is still the fastest way to install Xposed modules in VMOS Pro on Geek 7.1.

Which ROMs usually support it:

  • Official Geek 5.1 and 7.1 (often VIP on stock lists; some free custom images include it).
  • Some “Dual” / pre-rooted images with Xposed already in /system.
  • Usually not: lightweight Lite ROMs and many stock 9.0 images. Those need Magisk + LSPosed instead.

Steps:

  1. Shut down the VM from the floating menu (do not only swipe it away).
  2. Open VM settings (gear on the window, or three-dot menu → settings).
  3. Enable Root if it is off. Reboot the VM once if the ROM asks you to.
  4. Enable Xposed. On many builds this cannot be turned off later. Read the subtitle under the switch.
  5. Start the VM and wait for a full boot.
  6. Install Xposed Installer (the APK that matches your VM Android version — 89 for Nougat-era). Open it and confirm the framework is active (green / “Xposed is active”).
  7. Reboot the VM once more if the installer says the framework is not loaded yet.

If the switch is missing or greyed out, skip this section and use Magisk + LSPosed on the 9.0 64-bit ROM.

Installing Magisk + LSPosed on the 64-bit ROM

This LSPosed VMOS Pro tutorial is for Android 9.0 64-bit. You work inside the virtual machine, as if it were a normal rooted phone. You never unlock the host bootloader.

What you need inside the VM:

  • A working 9.0 64-bit VM with root already on (or Magisk will provide su).
  • Magisk APK + matching Magisk ZIP (same version).
  • LSPosed ZIP built for Zygisk (not the old Riru-only package).
  • A file manager with root, or Magisk’s own Modules page.

Step-by-step flashing inside the VM

  1. Copy Magisk APK, Magisk ZIP, and LSPosed ZIP into the VM (shared folder, Import from host, or download with the VM browser from a source you trust).
  2. Install the Magisk APK and open it. If it says “Requires Additional Setup,” tap it and let Magisk reboot the VM (not your real phone).
  3. After reboot, open Magisk → Settings → enable Zygisk. Reboot the VM again.
  4. Optional but useful: enable Enforce DenyList and add Play Store / your banking test apps if you will hide root later.
  5. In Magisk, open Modules → Install from storage → select the LSPosed Zygisk ZIP. Wait until it says success.
  6. Reboot the VM. After boot, you should see an LSPosed Manager (or a notification to install the manager APK — install it if asked).
  7. Open LSPosed. Status should show the framework loaded, with Zygisk as the provider.

Warning: flash only ZIPs you downloaded yourself into this VM. Random “Magisk for VMOS” packs from unknown Telegram channels often include extra modules you did not ask for.

If Magisk install hangs at 99% or the VM never returns, treat it like a ROM boot hang: stuck at 99% boot fix. If the VM is corrupted, delete that VM and import your export — do not keep flashing on a half-dead image.

How to Install Xposed Modules in VMOS Pro

Same idea for classic Xposed and for LSPosed: install the APK, activate it in the manager, reboot the VM.

  1. Download the module APK that matches your stack (Xposed module for 7.1 vs LSPosed / API for Android 9).
  2. Install the APK inside the VM.
  3. Classic Xposed: open Xposed Installer → Modules → tick the module.
    LSPosed: open LSPosed → Modules → enable the module → tick only the apps it should hook (do not enable “System Framework” unless the module docs say so).
  4. Reboot the VM from Magisk, LSPosed, or the VMOS floating Shutdown, then start again.
  5. Open the module’s own app (if it has one) and set options. Test one change at a time.

Enable one new module per reboot. If the VM dies, you will know which APK caused it.

Modules That Work Well in VMOS Pro

These are typical best Xposed modules for VMOS Pro picks because they are light and do not need real hardware (camera HAL, RIL, and Widevine often fail in a VM anyway).

Module Stack What it is good for in a VM
Hide My Applist LSPosed Stop apps seeing Magisk, LSPosed, or other “mod” packages
XPrivacyLua Xposed / some LSPosed ports Restrict permissions and fake identifiers in the sandbox
GravityBox (LP / N) Classic Xposed on 5.1 / 7.1 Quick tiles, navbar, status bar — version must match the ROM
Disable FLAG_SECURE LSPosed Allow screenshots in apps that block them (use only on apps you own / test)
MinMinGuard / similar ad hooks Classic Xposed In-app ads; can break WebView — keep a backup

Skip modules that patch Play Store licensing, “premium unlock,” or game servers. They get accounts banned and often trip Play Protect inside the VM.

Bootloop after installing a module — recovery

A bootloop here means the virtual Android restarts forever. Your real phone should still work. Close the VM window and use VMOS Pro, not the host recovery.

  1. Wait 2 minutes. First boot after LSPosed can look like a loop.
  2. If the logo never ends, force-stop VMOS Pro, then start the same VM again. Sometimes one retry is enough.
  3. Magisk / LSPosed: if you can get a short window into the system, open Magisk → Modules → disable the last module → reboot. If you cannot enter Android at all, use Magisk’s core-only / safe behaviour if your build offers it after a few failed boots (not all VM images do).
  4. Built-in Xposed: you often cannot turn the framework switch off. Disable modules only if Xposed Installer still opens. Otherwise restore the export.
  5. Last resort: delete the broken VM → Import the backup you made before flashing. Then install modules again, one by one.

Warning: do not factory-reset your real phone to “fix Xposed.” That will not repair the VM, and you will lose host data.

Troubleshooting

LSPosed says “framework not installed.” Zygisk is off, you installed a Riru LSPosed ZIP on a Zygisk Magisk, or you skipped the reboot after the module ZIP. Enable Zygisk, reinstall the correct ZIP, reboot the VM.

Xposed Installer says framework is not active. Wrong installer version for the ROM, or the built-in toggle never survived a reboot. Re-enable Xposed in VM settings while the VM is shut down.

Play Store / WhatsApp crash after a module. That module hooked the wrong app. In LSPosed, uncheck it for that package. Root + Xposed together also trigger SafetyNet-style checks — hide Magisk or turn the module off for those apps. If it still dies with modules off, use the apps crashing in VMOS Pro checks (RAM, root, 64-bit ROM).

Magisk app missing after reboot. Reinstall the Magisk APK inside the VM. The ZIP patches the virtual boot image; the app is separate.

Host Android 14/15: VM stuck at 99% after Magisk. Repair the VM file first, then treat Magisk as a second problem. Guide: stuck at 99% boot fix.

FAQ

Can I install Xposed modules in VMOS Pro without rooting my real phone?

Yes. Root and Xposed run only inside the virtual machine. Your host Android stays unmodified and does not need an unlocked bootloader.

Should I use LSPosed or the built-in Xposed toggle?

Use the built-in toggle on Geek 5.1/7.1 ROMs that show the switch. Use Magisk + LSPosed on Android 9.0 64-bit. Do not run both on one VM.

Why is Magisk needed for LSPosed in VMOS Pro?

LSPosed for Android 9 injects through Magisk Zygisk. The old Xposed installer does not replace that stack on the 64-bit 9.0 ROM.

What are the best Xposed modules for VMOS Pro?

Start with Hide My Applist (LSPosed) or XPrivacyLua (classic Xposed). Add GravityBox only on 5.1/7.1 with the matching GravityBox package. Avoid license-crack modules.

How do I recover from a bootloop after a module?

Disable the last module in Magisk or Xposed Installer if the VM still starts. If it does not, delete the VM and import the export you made before flashing. See bootloop recovery.

Does Xposed work on Android 14 hosts?

The host version does not run Xposed. Only the VM ROM matters. Android 14/15 hosts can still run a 7.1 or 9.0 VM; they just hit more boot bugs. Host matrix: does VMOS Pro work on Android 14.

Conclusion

You now have two clean paths to install Xposed modules in VMOS Pro: the built-in framework toggle on Geek ROMs, and Magisk + LSPosed on Android 9.0 64-bit. Export first, enable one module per reboot, and restore the backup if the virtual system loops.

Need a working VM first? Download the latest VMOS Pro version from vmospro.net, finish setup, then come back to this LSPosed VMOS Pro tutorial.