mirror of
https://github.com/MustardChef/WSABuilds.git
synced 2024-11-10 21:55:11 +01:00
Update README.md
This commit is contained in:
parent
995a403b4f
commit
bff41befd9
38
README.md
38
README.md
@ -1,5 +1,9 @@
|
||||
# Magisk on WSA (with Google Apps)
|
||||
|
||||
## Pre-request
|
||||
|
||||
- Ubuntu (you can use WSL2)
|
||||
|
||||
## Features
|
||||
|
||||
- Integrate Magisk and OpenGApps in a few clicks within minutes
|
||||
@ -9,7 +13,7 @@
|
||||
- Fix VPN dialog not showing (use our [VpnDialogs app](https://github.com/LSPosed/VpnDialogs))
|
||||
- Unattended installation
|
||||
- Automatically activates developers mode in Windows 11
|
||||
- Update to new version while preserving data with one-click script
|
||||
- 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](https://github.com/LSPosed/WSAHelper/releases/latest) to use this feature)
|
||||
|
||||
@ -18,13 +22,13 @@
|
||||
1. Star (if you like)
|
||||
1. Clone the repo to local
|
||||
1. Run `scripts/run.sh`
|
||||
1. Select the version of Magisk and select the [OpenGApps variant](https://github.com/opengapps/opengapps/wiki#variants) you like, select the root solution (none means no root), select WSA version and its architecture (mostly x64)
|
||||
1. Wait for the script to complete and the artifact will in `output` folder
|
||||
1. Select the version of Magisk and select the [OpenGApps variant](https://github.com/opengapps/opengapps/wiki#variants) you like, select the root solution (none means no root), select the WSA version and its architecture (mostly x64)
|
||||
1. Wait for the script to complete and the artifact will be in the `output` folder
|
||||
|
||||
1. Move the artifact to a places you like
|
||||
1. Move the artifact to a place you like
|
||||
1. Right-click `Install.ps1` and select `Run with PowerShell`
|
||||
- If you previously have a MagiskOnWSA installation, it will automatically uninstall the previous while **preserving all userdata** 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 start menu, please install and use [WSAHelper](https://github.com/LSPosed/WSAHelper/releases/latest).)
|
||||
- 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](https://github.com/LSPosed/WSAHelper/releases/latest).)
|
||||
- If the popup windows disappear **without asking administrative permission** and WSA is not installed successfully, you should manually run `Install.ps1` as administrator:
|
||||
1. Press `Win+x` and select `Windows Terminal (Admin)`
|
||||
2. Input `cd "{X:\path\to\your\extracted\folder}"` and press `enter`, and remember to replace `{X:\path\to\your\extracted\folder}` including the `{}`, for example `cd "D:\wsa"`
|
||||
@ -38,14 +42,14 @@
|
||||
- Can I delete the installed folder?
|
||||
|
||||
No.
|
||||
- How can I update WSA to new version?
|
||||
- How can I update WSA to a new version?
|
||||
|
||||
Delete `download` folder
|
||||
Delete the `download` folder
|
||||
Rerun the script, replace the content of your previous installation and rerun `Install.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 new version?
|
||||
- How can I update Magisk to a new version?
|
||||
|
||||
Do the same as updating WSA
|
||||
- How to pass safetynet?
|
||||
@ -54,26 +58,26 @@
|
||||
- Virtualization is not enabled?
|
||||
|
||||
`Install.ps1` helps you enable it if not enabled. After rebooting, rerun `Install.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 system as read-write?
|
||||
- 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 system by making a Magisk module. Or directly modify system.img. Ask Google for help.
|
||||
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 in the setting page and try `adb connect ip:5555`.
|
||||
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 remove online module repository. You can install module locally or by `adb push module.zip /data/local/tmp` and `adb shell su -c magisk --install-module /data/local/tmp/module.zip`.
|
||||
- Can I use Magisk 23.0 stable or lower version?
|
||||
Magisk actively removes the online module repository. You can install the module locally or by `adb push module.zip /data/local/tmp` and `adb 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 running on WSA. Magisk 24+ has fixed them. So you must use Magisk 24 or higher 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 root solution.
|
||||
Choose `none` as the root solution.
|
||||
- Github script is updated, how can I synchronize it?
|
||||
|
||||
1. In your fork repository, click `fetch upstream`
|
||||
![fetch](https://docs.github.com/assets/cb-33284/images/help/repository/fetch-upstream-drop-down.png)
|
||||
1. Then and click `fetch and merge`
|
||||
1. Then click `fetch and merge`
|
||||
![merge](https://docs.github.com/assets/cb-128489/images/help/repository/fetch-and-merge-button.png)
|
||||
|
||||
## Credits
|
||||
|
Loading…
Reference in New Issue
Block a user