f2b05674dc
Windows gives a very bad habit: not checking the permissions of executable files. |
||
---|---|---|
.github | ||
arm64 | ||
linker | ||
scripts | ||
wine | ||
x64 | ||
xml | ||
.gitattributes | ||
.gitignore | ||
LICENSE | ||
README.md |
Magisk on WSA (with Google Apps)
Pre-request
- Ubuntu (you can use WSL2)
Features
- Integrate Magisk and OpenGApps in a few clicks within minutes
- Keep each build up to date
- Support both ARM64 and x64
- Support all OpenGApps variants except for aroma (aroma does not support x86_64, please use super instead)
- Fix VPN dialog not showing (use our VpnDialogs app)
- Unattended installation
- Automatically activates developers mode in Windows 11
- Update to the new version while preserving data with a one-click script
- Merged all language packs
- Support managing start menu icons (manually installing WSAHelper to use this feature)
Text Guide
-
Star (if you like)
-
Clone the repo to local
-
Run
scripts/run.sh
-
Select the version of Magisk and select the OpenGApps variant you like, select the root solution (none means no root), select the WSA version and its architecture (mostly x64)
-
Wait for the script to complete and the artifact will be in the
output
folder -
Move the artifact to a place you like
-
Right-click
Install.ps1
and selectRun with PowerShell
- If you previously have a MagiskOnWSA installation, it will automatically uninstall the previous one while preserving all user data and install the new one, so don't worry about your data.
- If you have an official WSA installation, you should uninstall it first. (In case you want to preserve your data, you can backup
%LOCALAPPDATA%\Packages\MicrosoftCorporationII.WindowsSubsystemForAndroid_8wekyb3d8bbwe\LocalCache\userdata.vhdx
before uninstallation and restore it after installation.) (If you want to restore the icons to the start menu, please install and use WSAHelper.) - If the popup windows disappear without asking administrative permission and WSA is not installed successfully, you should manually run
Install.ps1
as administrator:- Press
Win+x
and selectWindows Terminal (Admin)
- Input
cd "{X:\path\to\your\extracted\folder}"
and pressenter
, and remember to replace{X:\path\to\your\extracted\folder}
including the{}
, for examplecd "D:\wsa"
- Input
PowerShell.exe -ExecutionPolicy Bypass -File .\Install.ps1
and pressenter
- The script will run and WSA will be installed
- If this workaround does not work, your PC is not supported for WSA
- Press
-
Magisk/Play store will be launched. Enjoy by installing LSPosed-zygisk with zygisk enabled or Riru and LSPosed-riru
FAQ
-
Can I delete the installed folder?
No.
-
How can I update WSA to a new version?
Delete the
download
folder Rerun the script, replace the content of your previous installation and rerunInstall.ps1
. Don't worry, your data will be preserved. -
How can I get the logcat from WSA?
%LOCALAPPDATA%\Packages\MicrosoftCorporationII.WindowsSubsystemForAndroid_8wekyb3d8bbwe\LocalState\diagnostics\logcat
-
How can I update Magisk to a new version?
Do the same as updating WSA
-
How to pass safetynet?
Like all the other emulators, no way.
-
Virtualization is not enabled?
Install.ps1
helps you enable it if not enabled. After rebooting, rerunInstall.ps1
to install WSA. If it's still not working, you have to enable virtualization in BIOS. That's a long story so ask Google for help. -
How to remount the system as read-write?
No way in WSA since it's mounted as read-only by Hyper-V. You can modify the system by making a Magisk module. Or directly modify the system.img. Ask Google for help.
-
I cannot
adb connect localhost:58526
Make sure developer mode is enabled. If the issue persists, check the IP address of WSA on the setting page and try
adb connect ip:5555
. -
Magisk online module list is empty?
Magisk actively removes the online module repository. You can install the module locally or by
adb push module.zip /data/local/tmp
andadb shell su -c magisk --install-module /data/local/tmp/module.zip
. -
Can I use Magisk 23.0 stable or a lower version?
No. Magisk has bugs preventing itself from running on WSA. Magisk 24+ has fixed them. So you must use Magisk 24 or higher version.
-
How can I get rid of Magisk?
Choose
none
as the root solution. -
Github script is updated, how can I synchronize it?
Credits
- StoreLib: API for downloading WSA
- Magisk: The most famous root solution on Android
- The Open GApps Project: One of the most famous Google Apps packages solution
- WSA-Kernel-SU and kernel-assisted-superuser: The kernel
su
for debugging Magisk Integration - WSAGAScript: The first GApps integration script for WSA