How to Enable Root in VMOS Pro Without Unlocking the Bootloader

You want SuperSU or Magisk apps, but you do not want to unlock your real phone or void the warranty. This page shows how to enable root in VMOS Pro inside the virtual machine only — VMOS Pro root without unlocking bootloader is the whole point of the app. Follow the steps in order: turn the per-VM switch on, check it with Root Checker, then grant su to the apps that need it.

Table of Contents

Before You Start: Requirements

Root is a switch inside one virtual machine. It does nothing if the VM has never finished a first boot.

Check Minimum Recommended
Host Android 5.1 9–13 (14/15 work, extra boot fixes)
VM ROM Any with a Root switch, or Geek / 9.0 64-bit Android 9.0 64-bit if you will use Magisk later
Free storage 8 GB 16 GB
RAM for the VM 2 GB 3 GB
Battery 50% Charged + Wi-Fi
  1. Finish setup first: VMOS Pro setup guide after install.
  2. Pick a ROM that actually offers root. Lite images often hide or lock the switch. Geek and many 9.0 images include it.
  3. Export the VM before you turn root on if you already installed WhatsApp, Play Store, or games. Some apps crash the moment they see su.
  4. Back up photos and chats on your real phone. VMOS Pro does not unlock the host bootloader, but a backup still takes five minutes.

How VMOS Pro Root Works (No Bootloader Unlock Needed)

On a normal phone, “root” means you patched the host system: unlocked bootloader, custom recovery, Magisk on the real /boot. That is slow, risky, and often kills the warranty.

VMOS Pro does not do that. It runs a second Android in an app window. The Root switch (or Magisk inside that ROM) gives superuser only to the guest system. Your real Android stays stock. Fastboot, OEM unlock, and custom recoveries on the host are not required.

What you get:

  • su / Superuser / Magisk inside the VM for root apps in VMOS Pro (Root Explorer, AdAway, Magisk modules).
  • Isolation: a bad module can brick the virtual ROM. It should not brick the phone.
  • A second identity: you can keep root off on one VM (Play Store, banking tests) and on in another (mods).

What you do not get:

  • Root of the host phone.
  • A guarantee that every bank or game will run. Many apps look for root and close. That is a detection problem, not a “toggle failed” problem.

If you later want Xposed, root must be on first: install Xposed modules in VMOS Pro.

Turning On the Root Toggle Per-VM

This is the main path for how to enable root in VMOS Pro on stock and Geek images. Each VM has its own switch. Turning it on for VM A does not root VM B.

  1. If the virtual Android is running, open the floating ball → Shutdown (do not only swipe the window away).
  2. On the VMOS Pro home screen, tap the gear on that VM, or the three-dot menu → VM settings.
  3. Find Root (sometimes “ROOT permissions” or a padlock icon). Read the line under it: many builds say it cannot be turned off later.
  4. Turn the switch on.
  5. Start the VM and wait for a full boot (2–5 minutes the first time after the change).
  6. After boot, look on the home screen for SuperSU, Superuser, or Magisk. One of these should appear on Geek / GApps-root images.

Warning: if the subtitle says the option cannot be closed after opening, treat root as permanent for that VM. Export a copy before you flip it if you still need a clean, unrooted clone for messengers.

On Android 9.0 64-bit, some ROMs use Magisk instead of a simple switch. If there is no Root row, install Magisk inside the VM (same flow as the LSPosed guide) rather than hunting for a missing toggle.

Verifying Root (Root Checker Inside the VM)

Do this inside the virtual Android, not on the host.

  1. Open Play Store in the VM (or sideload an APK into the VM).
  2. Install Root Checker (or “Root Checker Basic”).
  3. Open it → Verify Root.
  4. When Superuser pops up, tap Allow (or Grant) and, if you want, Don’t ask again for that app.
  5. Root Checker should show that the device is rooted.

If Superuser never appears:

  • Root is off, or the ROM has no su binary.
  • You installed Root Checker on the real phone by mistake.
  • Battery savers killed the Superuser app; disable optimization for VMOS Pro on the host, then retry inside the VM.

A green Root Checker result is enough for most root apps in VMOS Pro. You do not need a computer or adb root on the host.

Granting Root to Specific Apps

Root is not “all apps are root.” Each app must ask, and you must allow it.

  1. Open the root app inside the VM (Root Explorer, Titanium Backup, AdAway, Magisk, and so on).
  2. When the Superuser / Magisk prompt appears, tap Allow.
  3. Open SuperSU or Magisk → Superuser (or DenyList opposite) and confirm the app is in the allow list.
  4. If a prompt was dismissed or timed out, open Superuser → tap the app → set Grant, then open the app again.

Do not grant root to Play Store, WhatsApp, or banking apps unless you know why. Those apps do not need su, and a grant can make detection worse. Work chats belong on an unrooted VM: second WhatsApp account with VMOS Pro. A clicker for AFK is the exception — grant su to the clicker only, never to the game: AFK farming with VMOS Pro.

Apps that crash when root is on — hiding root

This is the practical VMOS Pro root detection bypass: you hide root from one app, you do not “hack” the app.

Typical crash pattern: the app opens, then closes, or says “rooted device not allowed.” Three usual fixes, lightest first:

  1. Turn Root off on a second VM used only for that app. Easiest if the switch can still be turned off. Clone via export/import if the switch is one-way.
  2. Magisk DenyList (Zygisk): Magisk → Settings → Zygisk on → Enforce DenyList → add the crashing app → reboot the VM.
  3. Hide My Applist (LSPosed): hide Magisk, SuperSU, and LSPosed from that package. Full stack: LSPosed in VMOS Pro.

Warning: hiding root to break a game’s or bank’s security may violate that app’s terms and can get the account banned. Use a throwaway account inside the VM. Do not put real banking credentials in a rooted sandbox.

If the app still dies with root off, the cause is often RAM or 32-bit vs 64-bit ROM, not root. See the setup RAM rules and the apps crashing in VMOS Pro guide.

Root Toggle Greyed Out / Not Sticking — Fixes

When people search vmos pro root toggle not working, they usually hit one of these.

Greyed out (cannot tap it):

  1. The VM is still running. Shut it down fully, then open settings again.
  2. You are on a Lite or VIP-locked ROM. Switch to Geek / 9.0 with root, or import a ROM that includes su.
  3. Host Android 11+ blocked storage. Grant All files access to VMOS Pro, then reopen settings.
  4. The ROM already baked root in and removed the switch (common on some custom images). Verify with Root Checker instead of hunting a toggle.

Toggle turns on, then jumps back to off after boot:

  1. Do not swipe VMOS Pro from Recents during the first reboot after enabling root.
  2. Disable battery optimization for VMOS Pro on the host (Xiaomi / Samsung / Honor kill the process mid-write).
  3. Repair a half-written VM: settings → Repair virtual machine file, then try the switch again. If boot hangs at 99%, use the stuck at 99% boot fix.
  4. Delete that VM and download the ROM again if repair fails. A corrupted su install will never stick.

Toggle is on but Root Checker fails:

  • Wrong checker (installed on the host).
  • Need a reboot of the VM after the switch.
  • 9.0 image expects Magisk additional setup — open Magisk and complete it, then reboot the VM.

Warning: do not factory-reset your real phone to “fix” a grey Root switch. That only wipes the host. Fix the VM or replace the ROM.

Troubleshooting

Superuser prompt never shows. Open SuperSU/Magisk and grant the app manually. If neither app exists, root is not installed on that ROM.

“su not found” in a terminal. You are in a host terminal, or the VM has no su. Use a terminal inside the VM after a successful Root Checker test.

Play Store says device is not certified after root. Normal on many rooted VMs. Use a secondary Google account. Clearing Play Services data inside the VM sometimes helps; it can also sign you out.

Root worked once, then vanished after a VMOS Pro update. Updates can replace ROM files. Export VMs before updating. Re-enable the switch or restore the export.

Host Android 14/15: settings won’t open. Pair VMOS Assistant / wireless debugging if the app requires it, then retry. Host map: does VMOS Pro work on Android 14. Boot bugs: stuck at 99% boot fix.

FAQ

How do I enable root in VMOS Pro without unlocking the bootloader?

Open that VM’s settings, turn Root on, start the VM, then verify with Root Checker inside the virtual Android. The host phone stays locked and unrooted.

Does VMOS Pro root my real phone?

No. Root exists only in the guest system. Fastboot OEM unlock is not part of this process.

Why is the VMOS Pro root toggle not working?

The VM is still running, the ROM has no root (Lite), storage permission is missing, or the VM file is corrupt. Shut down the VM, use a Geek/9.0 image, grant all-files access, or repair/re-download the ROM.

How do I run root apps in VMOS Pro?

Enable root, install the app inside the VM, tap Allow on the Superuser prompt, then confirm the app in SuperSU or Magisk. Host-installed root apps cannot see the VM’s su.

Can I hide root so WhatsApp or a game does not crash?

Use a second unrooted VM, or Magisk DenyList / Hide My Applist on the rooted VM. This is app-level hiding, not a host unlock. Accounts can still be banned.

Can I turn root off later?

Only if the settings text allows it. Many VMOS Pro builds make Root one-way. Export a clean VM before you enable it if you need both modes.

Conclusion

You now know how to enable root in VMOS Pro: it is a per-VM switch (or Magisk on 9.0), not a bootloader unlock. Verify with Root Checker inside the guest, grant su per app, and hide or split VMs when detection kills Play Store or games.

Need the app first? Download the latest VMOS Pro version from vmospro.net, finish one clean boot, then turn Root on for that VM only.