Windows subsystem android github
Some computer have the system requirements but not let you install android so here is a simple script to download and install the WSA. (Windows Subsystem for Android)
with the the latest version WSA is going to be install with gapps 🙂
RUN THE SCRIPT IN ADMIN .
if you have a error use this to update the link : https://pastebin.com/heFukQix (i try to find a way to have a static link)
| Minimum | Recommended |
|---|---|
| Windows 10 version 22000.63 or higher | Windows 10 version 22000.63 or higher |
| ARM64, x64 | ARM64, x64 |
| 8 GB | 16 GB |
| Availability: Only available to Windows 11 Insiders on Beta Channel in the US. |
I have a error when i run the script why ?
Post the error in the issues section or contact me on twitter
The ADB command is not working why ?
Run the WSA once (by running a app like the file app or amazon or play store)
I can’t connect to my Google account why ?
This is a «bug» and you need to fix it by using my script and choose the «fix Google sign in» option or by using adb manually (after every reboot of the WSA you need to fix it)
You’r english is sh*t
Yeah i know and i am tired sorry lol
About
Some computer have the system recommendation but not let you install android so here is a simple script to download and install the WSA (Windows Subsystem Android)
Источник
Windows subsystem android github
Windows Subsystem for Android™ Toolbox
An awesome Windows Application to easily install and use the Windows Subsystem For Android™.
About The Project
A full rewrite of this project will happen soon. I’ve just gone back to school, so I probably won’t be able to respond to issues for a few weeks. Please do not expect any changes or updates for a few weeks.
This project includes tools to install and use the Windows Subsystem For Android™ platform on Windows 11. These tools include:
- Installation of any APK file in one click.
- Access to the ADB Shell.
- Installation of Windows Subsystem For Android™ in unsupported regions.
- Installation of the Aurora Store as an alternative to the Google Play Store.
- Installation of a simple app launcher for easy access to other apps.
- Installation of any APK file by just double clicking on it
- Drag and drop functionality for APK on the window.
- Add a file queue to queue up installations
This tool was inspired by the Fire Toolbox application, which was used to gain unintended functionality on Amazon Fire Tablets, easily and safely.
This project is built using the HTA HTML Application platform developed by Microsoft, as well as the simple scripting language, VBScript and the use of batch files. It also uses ADB for connection with the virtual device and winhttpjs for downloading files. It is all packaged up into an EXE file with the help of The Batchman.
This project also uses a customised version of the Simple Android Launcher project by Simple Mobile Tools which provides a launcher for your installed Android applications. The Application name has been changed to Android Apps to work better with the Windows Start Menu.
See the releases tab for the latest versions of this application, available in an EXE file. Simply run the file to start the tool.
Make sure you enable «Developer Options» in the Windows Subsystem for Android Settings App to make this toolbox function.
You can get installation instructions for installing the Windows Subsystem for Android package here.
To see how to build this app, read on:
- Run the .hta file inside the folder created.
Distributed under the GNU GPLv3 license. See LICENSE for more information.
About
A Windows 11 application to easily install and use the Windows Subsystem For Android™ package on your computer.
Источник
Windows subsystem android github
This project is Work-In-Progress
This project is being updated without schedule (though frequently). This README might not be completely clear right now, it will be fixed ASAP.
As for potential questions — please open Discussions instead of Issues.
Issues are needed in cases if you have an actual issue that prevents you from using this project.
By using the tools (scripts, but not limited to) provided by this project, you agree with the terms of Unlicense License, which states that «THE SOFTWARE IS PROVIDED «AS IS»».
To end user this serves as a warning, though we currently don’t have any explicit confirmations — such way of installing Google Services and Google Play Store may potentially be in a legal gray area.
Any product or trademark referenced in this document (or project as whole) belongs to their respective owners. No copyright infringement is intended.
As a temporary measure and additional information (especially if README remains unclear, @ADeltaX provides a video-tutorial hosted on YouTube
Click on the image to see the video
Install Windows Subsystem for Linux (Version 2)
Q & A for WSL Installation
If you have never used WSL, please do check the following:
- You must be running Windows 10 version 2004 and higher (Build 19041 and higher) or Windows 11
Fastest way to check your build version is to run winver command in Windows Search or via «Run. » (Right-click the Start button to access «Run. «)
Because of the way Android as an operating system is built — specific tools to do the modifications that we are doing are only available on Linux-based OSes. The fastest way to get access to these tools is via WSL.
How to install WSL
- Open Windows PowerShell as an Administrator
- Run wsl —install : this will install Ubuntu 20.04 LTS in WSL (Version 2) and all necessary components required to run as it is default (this is recommended)
Your PC may restart several times when downloading and installing required components. After that — follow installation wizard instructions to proceed. If you have any questions, official documentation from Microsoft for WSL will help you.
- Check with wsl —list —verbose to be sure that you have a Linux Distro installed with WSL2 version. If for some reason you have receieved WSL1 kernel (or you have trouble running this command in general) — follow instructions in the section below to perform conversion.
How to convert WSL1 to WSL2 (and manual installation)
If you have trouble installing WSL2 with wsl —install in general — follow this instruction from Microsoft.
If you have already used WSL, have trouble installing with wsl —install or for some reason have received a WSL1 version installation, this section is for you.
Follow these steps:
- Download WSL2 kernel for manual installation. Use the Microsoft Docs link above (Manual Installation) and check Step 4 to receive the kernel package.
- Open Windows PowerShell as Administrator and run:
- wsl —shutdown to stop all WSL related processes (if any are running).
- Install the kernel package from the step above.
- Return to Windows PowerShell and run:
- wsl —list —verbose to get your installed distribution name. In case of Ubuntu, it most likely will look like Ubuntu-20.04 .
- wsl —set-version 2 , replace with the one that you have.
- Optional: if you would like to automatically install only WSL2 version builds in future. wsl —set-default-version 2 . To be sure about the difference, check Microsoft Docs: WSL — Compare versions
Install unzip, lzip
For now, we are assuming that you have went with default installation (Ubuntu), terminal commands will be provided for Ubuntu. Commands provided for the most part will work for other Linux Distributions but there may be some that use other package managers. Check how to correctly install applications for your chosen distribution on the internet.
Run following in the WSL Terminal (If you are unsure what is WSL Terminal, refer to the video, Microsoft Docs, or search Ubuntu in your start menu to be sure):
Attention! For new users who have never used Linux Terminals — when you are being asked for your password (which you’ve set up when installed WSL) — it will NOT be displayed in the terminal as part of security measures. You should enter it blindly and then press enter. If password was entered incorrectly system will give you two more attempts, after which you will need to run the command again and try entering password again.
We have checked availability of updates and requested installation of two packages which are required for execution of scripts provided by this project. They may be already present at your installation, but it is better to check anyway.
Prepare folder structure
For the sake of simplicity, create a folder in the root of C Drive, so you will have C:\WSA\ . You may use other location if you would like, be sure to adjust commands below for new location.
Attention! The folder where you will place the files which we will be downloading is going to become an installation folder. DO NOT delete that folder!
Attention! At the time of last update for this README, attempt to run scripts if they are located in path that contains spaces (like «Zulu Storage» in D:\Zulu Storage\WSA ) will result in an error. Be sure to use paths with no spaces as long as fix have not been implemented.
Hint: You can also open any folder (even those that are located within Linux WSL Filesystem, by typing explorer.exe . (Yes, with the dot) in the WSL Terminal, to move files around.
Download Windows Subsystem for Android ™️ Installation Package
As we need to modify installation files, we cannot download WSA from the Microsoft Store. To download it directly we will use this service
- ProductID: 9P3395VX91NR
- Ring: SLOW
Click the checkmark, and locate file which has size of approx.
1.2GB (usually at the bottom of the page) and has .msixbundle extension.
Click the filename to begin downloading. You may be warned by your web-browser that «The file cannot be downloaded securely». Disregard the warning and force the download (use buttons like «Keep anyway» or similar, depending on your web-browser)
Save the file at our prepared directory C:\WSA\
- Download 7zip or a similar archival program and use it to extract downloaded file. Do not mind that this file does not bear any archival extensions (like .zip).
- After extraction open C:\WSA\MicrosoftCorporationII.WindowsSubsystemForAndroid_versionnumber_neutral___identifier\ . This folder will contain a lot of .msix files, use «Sort by size» to locate two biggest files.
- Extract the one that is valid for your architecture, like this one WsaPackage_1.8.32822.0_x64_Release-Nightly.msix
- Open the extracted folder
- Locate and delete files AppxBlockMap.xml , AppxSignature.p7x and \[Content_Types\].xml
- Locate and delete AppxMetadata folder
Do not close this folder — we will return here to collect *.img files.
Download «GApps» via OpenGApps Project
To install Play Store, we need to get it from somewhere. Use OpenGApps.
- Platform: x86_64 if you are running Windows on a traditional laptop/PC, otherwise choose ARM64
- Android: 11.0
- Variant: Pico (at the time of writing this README, only minimal functionality with Pico variant have been confirmed working).
For the time being save the .zip file at C:\WSA\gapps-zip-file-name.zip . Do not extract it.
Clone this repository and populate the directories
As we have used C:\WSA , you will be able to use Windows Explorer to move files around.
Reminder: commands provided are for Ubuntu
Attention! To be sure that you can access your Windows filesystem from inside of WSL, you can run cd FolderName to change to another directory and ls to list what files and folders you have there. Typically, Windows Filesystem is available by «/mnt/$DriveLetter/», so /mnt/c/Users will be your Windows C:\Users
Wait for the command to finish running.
At the Extract step (in Download Windows Subsystem for Android ™️ Installation Package) of this Guide we have got a folder that contains four *.img files which are product, system, system_ext and vendor. Move those files into C:\WSA\WSAGAScript\#IMAGES
We also have C:\WSA\gapps-zip-file-name.zip . Copy this .zip file into C:\WSA\WSAGAScript\#GAPPS . Do not extract it, just move the file.
If you are using this project on a device with ARM architecture (e.g., Qualcomm Snapdragon), please edit VARIABLES.sh and set the correct architecture. Hint is in the file.
Set executable permissions for the scripts
You should still be in the same directory within the WSL Terminal, if not use cd /mnt/c/WSA to get back. Set executable permissions for the scripts:
Verify that your scripts are executable by running ls -l and checking that you have -rwxrwxrwx at the start of lines that contain files: VARIABLES.sh , apply.sh , extend_and_mount_images.sh , extract_gapps_pico.sh , unmount_images.sh .
Running the scripts
Make sure you’re in the same directory as in the step before, the run:
Copy the edited images
After successful execution, you can now copy edited images from C:\WSA\WSAGAScript\#IMAGES back to C:\WSA\MicrosoftCorporationII.WindowsSubsystemForAndroid_1.8.32822.0_neutral___8wekyb3d8bbwe\WsaPackage_1.8.32822.0_x64_Release-Nightly (example, the folder from where you have taken the images).
Registering the edited Windows Subsystem for Android ™️ Installation Package
- Use Windows Search to find «Developer Settings», when PC Settings app opens, enable «Developer Mode» on that page.
- Uninstall any other installed versions of WSA (if you had any, uninstall exactly the main WSA app, all Android apps that have been added to Start Menu will be removed automatically)
- Open Windows PowerShell as Administrator and run Add-AppxPackage -Register path-to-extracted-msix\AppxManifest.xml
Where path-to-extracted-msix , use path from «Copy the edited images» section (right above) as example.
WSA will install with GApps, make sure to sign in to Play Store and install «Android System WebView» or most apps will crash without that component.
- Locate Windows Subsystem for Android ™️ in your Start Menu, right-click, uninstall. This will uninstall Android and all Android Apps will vanish from Start as they are just shortcuts wired in from the WSA. You don’t need to uninstall all Android Apps one-by-one beforehand.
- Locate the directory where you have placed the files (in the example of this README it would be C:\WSA ) — remove it.
Gaining Root Access
You can get root access by replacing the kernel. (This step is no longer required to sign in GApps.)
(ADB SHELL ROOT WITH su)
Copy the kernel file from this repo (in misc folder) and replace the kernel file inside the Tools folder of your extracted msix (make sure WSA is not running, use Stop button inside WSA Settings, and close settings).
Kernel files inside misc are named for their respective architectures, do not forget to rename the file you took to kernel before placing it back into Tools .
This will allow you to use su inside the adb shell . Enter into the adb shell and run the following commands:
Источник
