BluestacksRoot

Root BlueStacks 5 with Magisk — blueStackRoot (Android 9, 11 & 13)

Root BlueStacks 5 / MSI App Player with real Magisk — from one file, with no traces left behind. Run blueStackRoot.cmd as administrator, pick your Android version, and you’re rooted. A Magisk Delta (Kitsune v31) build is now bundled inside the .cmd itself — no separate Magisk download, no other files, nothing to install. Tested on BlueStacks 5.22.265.1013 (Android 9, 11 and 13).

⚡ Quick Start

Works on the 64-bit BlueStacks instances — Android 9, 11, and 13.

⬇️ Download blueStackRoot.cmd — one file (~20 MB) with the real Magisk APK embedded inside — nothing else to download. (All versions: Releases page.)

1. First, open the exact instance you want to root — launch it from the Multi-Instance Manager and let it boot once. The tool roots the instance of your chosen Android version that you opened most recently, so if you keep several of the same type, open the one you want last (this also finishes creating a brand-new instance).

2. Right-click blueStackRoot.cmd → Run as administrator. (If Windows shows a blue “Windows protected your PC” box, click More info → Run anyway — see Is this safe? below.)

3. A small menu opens. Find your instance’s Android version below, type that number, and press Enter:

   If your instance is…	Type	What happens
   Android 9 (Pie64)	1	Magisk is installed and set up automatically — just wait for VERIFY PASS ✅
   Android 11 (Rvc64)	2	Magisk is installed and set up automatically — just wait for VERIFY PASS ✅
   Android 13 (Tiramisu64)	3	Magisk is installed and set up automatically — just wait for VERIFY PASS ✅

That’s it — every version installs Magisk as the final root, fully automatically. Open the Magisk app to confirm it shows Installed, then grant root to any app you like. BlueStacks’ own “root access” toggle is safely turned back off, and no leftover files are left behind for games to detect.

💡 Not sure which Android version your instance is? It’s shown next to each instance in the BlueStacks Multi-Instance Manager (or open the instance → Settings → About phone).

💡 Seeing “Ramdisk: No” in Magisk? That’s totally fine and expected on BlueStacks — root works perfectly without it. Don’t go looking for a “ramdisk fix”.

Run a rooted and an unrooted Android instance side by side

Root each Android instance you want — every instance you don’t root stays 100% clean on its own (no root, no Magisk app, nothing for games to detect). Then launch them together from the Multi-Instance Manager and they run side by side. Want to unroot just one later? Undo that single instance all the others keep working, untouched.

📖 Full walkthrough & rollback: docs/RUNBOOK.md · Deep technical writeup: docs/BLUESTACKS_ROOTING_DEEP_DIVE.md

🛡️ Is this safe? Will my antivirus flag it?

Short answer: yes, it’s safe — and yes, your antivirus or SmartScreen might warn you anyway. That’s a false positive common to every rooting/emulator tool: the file is an unsigned .cmd that modifies BlueStacks and carries binaries inside it. Heuristic scanners flag that pattern. Here’s why you can trust it:

• 100% open source. The host logic is readable PowerShell, batch, and inline C# — right here in this repo. Read tools/bsr_magisk.ps1 and tools/bsr_engine.ps1, and the shared Windows helpers in tools/bsr_host.ps1; those are the scripts embedded in the .cmd. Nothing is obfuscated or “encrypted” — unlike the closed-source rooter binaries floating around.

• The big base64 blocks are not a virus — they’re just files, bundled so you only download one thing. The .cmd carries these components between clearly-labelled __BSR_*__ markers:

  Embedded blob	What it actually is	How to verify
  __BSR_ENGINE__ / __BSR_MAGISK__ / __BSR_HOST__	The PowerShell scripts above (plain text)	Diff against tools/*.ps1 in this repo
  __BSR_DFS__	debugfs from the standard Cygwin e2fsprogs suite	Standard open-source ext4 tool
  __BSR_SU__ / __BSR_BSRSU__	Tiny su binaries used only during install, then erased	Source in tools/su_src/
  __BSR_APK__	A custom, open-source build of Kitsune Mask (Magisk Delta) v31 — one small documented patch	SHA-256 + source below

• The Magisk APK is a custom, open-source build of Kitsune Mask v31 (magisk -c → 31.0-kitsune, versionCode 31000). SHA-256 fac319d2de262fcfff1684e13e1a5c61c486d2a773a7a8ffcfdbfe6f763a7fd4 (12,574,128 bytes). It is built from Jordan231111/KitsuneMagisk (commit 25fa2159f) — a fork of 1q23lyc45/KitsuneMagisk with a single 3-line source patch: the DenyList backend stores entries in the denylist table instead of hidelist, so apps you toggle in Magisk’s own DenyList UI are picked up by the Zygisk implementation (ReZygisk) that reads denylist — i.e. the in-app hide toggle finally hides root. Nothing else is changed. Don’t just trust me — read the one-commit diff and rebuild it yourself; the SHA-256 above is exactly what’s embedded in the .cmd (re-verifiable with tests/Check-Embedded-Sync.ps1).

• Verify it yourself in 30 seconds. Scan the file on VirusTotal, or extract any embedded blob and check its hash — open the .cmd in any text editor and the __BSR_*__ markers are right there. The whole point of this project is that you don’t have to trust a black box.

❓ “Android system has been illegally tampered with” — instance shuts down after rooting?

If BlueStacks shows “the Android system has been illegally tampered with and does not meet security requirements” (or “Android system doesn’t meet security and will be shutdown”) and your instance keeps closing the moment you enable root, that’s the disk-integrity / anti-tamper check added in BlueStacks 5.22+. Almost every other guide tells you to downgrade to 5.22.130.1019 — you don’t have to.

blueStackRoot applies a one-byte HD-Player anti-tamper patch that bypasses the disk-integrity check, so you can root the latest BlueStacks (5.22.210) without downgrading — and it installs real Magisk with no traces, not a detectable classic su. If bst.feature.rooting keeps reverting to 0 on launch, that’s the same anti-tamper system, and this tool handles it for you. Full technical breakdown: docs/BLUESTACKS_ROOTING_DEEP_DIVE.md §2 (the single-byte patch).

❓ Why does getenforce say Disabled? Do I need a permissive-mode option?

That is BlueStacks’ factory guest state; blueStackRoot does not change SELinux. Disabled already enforces no SELinux denials, while permissive loads a policy but only logs denials. setenforce 0 cannot turn a disabled subsystem into permissive—doing that would require a compatible guest kernel, boot configuration, and policy. Therefore there is no misleading menu toggle. A mod that only checks for the literal word Permissive should also accept Disabled; full evidence and caveats are in the technical deep dive.

🔧 How the Magisk path works (the hard part)

🧩 Optional: Zygisk + LSPosed + CorePatch (in modules/)

Once an instance is rooted with Magisk (above), you can optionally add the Zygisk → LSPosed → CorePatch stack to run Xposed modules and sideload modified / unsigned APKs. Compatible builds are bundled in modules/ so you don’t have to hunt for versions that work together on Magisk Delta:

Order matters: root with Magisk → flash ReZygisk (turn Zygisk on) → flash Vector / LSPosed → install CorePatch and enable it in LSPosed. Confirm each step works (Magisk shows the module active / LSPosed shows “Active”) before moving to the next, and reboot the instance between flashes.

⚠️ Android 9 (Pie64): the bundled Vector v2.0 (3043) won’t activate on Pie — flash Vector v1.11.0 instead (same step, right after ReZygisk). Android 11 & 13 are fine with the bundled build.

c953fb3effab897bd98d04ed9d91ac0b952acfe574e3af3136314dbba8107543  ReZygisk-v1.0.0-521-8034041-release.zip
94042fc223a00c7c3ab94193ad929c814b8309e00f5d25a29a1733f60165869a  Vector-v2.0-3043-Release.zip
1bdc47d5b48afffd37948a9f5638ae6a5f3d4d02ca01ae36143588284b979996  CorePatch-4.9.apk

💻 Requirements

Windows + BlueStacks 5 (nxt) or MSI App Player, run as Administrator. Nothing to download — PowerShell 5.1 (built into Windows) runs the embedded engine, and HD-Adb.exe ships with BlueStacks.

If Windows reports Access is denied when starting HD-Player.exe, that is a host launch failure before Android or ADB. If it reports virtual disk support provider not found, that is a Windows disk-mount failure. Neither message, by itself, proves antivirus interference. For any problem, download debug.cmd into the same folder as blueStackRoot.cmd, then double-click it and accept the Windows administrator prompt. No commands or options are needed. It automatically collects file, temporary-storage, cloud-file, payload-extraction, Windows, disk and ADB evidence in one report. It selects an instance automatically and restarts only that instance. Close other instances if you need the read-only disk probe. Logs normally go to %LOCALAPPDATA%\BlueStacksRoot\Logs; the final Full log line gives the location if a fallback was needed. Attach that log to your issue. User-directory names are masked while error details remain. See the investigations of #31/#32 and #36/#38 for findings and test limits.

🎥 Video tutorial

▶ Watch the walkthrough on YouTube — the current one-file Magisk flow (Android 9 / 11 / 13).

_{Earlier junction-based method (legacy BlueStacks ≤ 5.21.x): older video.}

🧰 For developers (build & tests)

The .cmd embeds tools/bsr_launcher.ps1 + tools/bsr_engine.ps1 + tools/bsr_magisk.ps1 + tools/bsr_host.ps1 + tools/debugfs/ + tools/su_src/bsr_su

• the Magisk APK between marker lines. To update them, edit the tools/*.ps1 and run tools/reembed.ps1 (re-splices the launcher, engine, orchestrator, and shared host helpers, including debug.cmd); swap the bundled Magisk with tools/reembed-apk.ps1 -Apk <new.apk> (byte-level splice + SHA-256 round-trip verify), then refresh the reference set with tools/extract-databin.ps1 -Apk <new.apk>. Maintained tests live in tests/: Run-Tests.ps1 covers engine/ext4 integration, Run-Live-E2E.ps1 tests an explicitly selected disposable instance, and Check-Embedded-Sync.ps1 checks embedded sources and payloads. Run-Launcher-Tests.ps1 checks locale and menu layout, Run-Console-Tests.ps1 checks real Windows console buffers at different font sizes, Run-Preflight-Tests.ps1 covers diagnostic file, temp and extraction failures, and Run-Diagnostic-Default-Tests.ps1 checks the full report with no diagnostic arguments. Retired probes and approaches (junctions, the integrity-bypass scripts, etc.) are kept for reference in archive/.

☕ Support / Donation

If this saved you time, a coffee is hugely appreciated — it keeps the last open-source BlueStacks rooter alive:

• https://ko-fi.com/yejordan
• https://buymeacoffee.com/yejordan

📌 Other information

• Contributing: open a PR with a clear explanation (and screenshots if relevant). Report issues with clear steps to reproduce and a video if possible.
• Supported instances (Android 9 / 11 / 13): the tool uses my bundled Kitsune Mask (Magisk Delta), or the build at 1q23lyc45/KitsuneMagisk. The Android-9 (Pie64), 11 (Rvc64), and 13 (Tiramisu64) paths are identical and fully automated — all three have been run end-to-end to a clean VERIFY PASS.
• Android 7 (Nougat32) is not supported. It is a 32-bit instance, and every binary this tool bundles (the su and all Magisk binaries) is 64-bit x86_64, so root cannot run there. If you need root, recreate the instance as a 64-bit Android (9/11/13) in the Multi-Instance Manager.
• Old/legacy files are archived here.
• Manual method this is based on: XDA forums. Note that the manual method may not work anymore due to hidden services that must be killed — this script handles that for you.

📄 License

Licensed under the Creative Commons Attribution-NonCommercial-NoDerivatives 4.0 International License. See LICENSE or visit http://creativecommons.org/licenses/by-nc-nd/4.0/.

_{Keywords: root BlueStacks, BlueStacks root, root BlueStacks 5, how to root BlueStacks, BlueStacks Magisk, Magisk Delta BlueStacks, Kitsune Magisk, BlueStacks Zygisk, root BlueStacks 5.22, BlueStacks 5 root 2026, root Android emulator, BlueStacks rooted, MSI App Player root, install unsigned APK on BlueStacks, BlueStacks illegally tampered, Android system doesn’t meet security requirements, BlueStacks tampering detected, BlueStacks instance keeps closing after root, BlueStacks disk integrity check bypass, root latest BlueStacks without downgrading, fix illegally tampered BlueStacks, bst.feature.rooting reverts to 0, “disk file have been illegally tampered with”, Verified the disk integrity, BlueStacks disk integrity check, root BlueStacks 5.22.169, root BlueStacks 5.22.210, root BlueStacks latest version 2026.}