### List All Available AVDs and Command Examples

Source: https://context7.com/newbit1/rootavd/llms.txt

This command lists all installed AVD system images and provides example commands for various rootAVD operations, helping you identify the correct ramdisk.img path.

```bash
# List all installed AVDs with command examples
./rootAVD.sh ListAllAVDs
```

```text
# Output shows commands for each installed AVD:
# Command Examples:
# ./rootAVD.sh
# ./rootAVD.sh ListAllAVDs
# ./rootAVD.sh InstallApps
#
# ./rootAVD.sh system-images/android-33/google_apis_playstore/x86_64/ramdisk.img
# ./rootAVD.sh system-images/android-33/google_apis_playstore/x86_64/ramdisk.img FAKEBOOTIMG
# ./rootAVD.sh system-images/android-33/google_apis_playstore/x86_64/ramdisk.img DEBUG PATCHFSTAB GetUSBHPmodZ
# ./rootAVD.sh system-images/android-33/google_apis_playstore/x86_64/ramdisk.img restore
```

--------------------------------

### Basic rootAVD.sh Commands

Source: https://github.com/newbit1/rootavd/blob/master/README.md

These commands demonstrate basic operations like listing all AVDs and installing applications.

```bash
./rootAVD.sh
./rootAVD.sh ListAllAVDs
./rootAVD.sh InstallApps
```

--------------------------------

### Windows rootAVD.bat Script Examples for Android 33

Source: https://github.com/newbit1/rootavd/blob/master/README.md

Examples of using rootAVD.bat with specific Android image paths and commands for API level 33 on Windows.

```batch
rootAVD.bat system-images\android-33\google_apis_playstore\x86_64\ramdisk.img
```

```batch
rootAVD.bat system-images\android-33\google_apis_playstore\x86_64\ramdisk.img FAKEBOOTIMG
```

```batch
rootAVD.bat system-images\android-33\google_apis_playstore\x86_64\ramdisk.img DEBUG PATCHFSTAB GetUSBHPmodZ
```

```batch
rootAVD.bat system-images\android-33\google_apis_playstore\x86_64\ramdisk.img restore
```

```batch
rootAVD.bat system-images\android-33\google_apis_playstore\x86_64\ramdisk.img InstallKernelModules
```

```batch
rootAVD.bat system-images\android-33\google_apis_playstore\x86_64\ramdisk.img InstallPrebuiltKernelModules
```

```batch
rootAVD.bat system-images\android-33\google_apis_playstore\x86_64\ramdisk.img InstallPrebuiltKernelModules GetUSBHPmodZ PATCHFSTAB DEBUG
```

--------------------------------

### Install Custom Kernel Modules

Source: https://context7.com/newbit1/rootavd/llms.txt

Installs custom-built kernel and modules from local files. Ensure your bzImage (kernel) and initramfs.img (modules) are placed in the rootAVD folder before running this command.

```text
# First, place your custom kernel files in the rootAVD folder:
# - bzImage (custom kernel)
# - initramfs.img (kernel modules)
```

--------------------------------

### Starting Magisk from Terminal

Source: https://github.com/newbit1/rootavd/blob/master/README.md

Command to launch the Magisk application from the terminal using adb shell.

```bash
adb shell monkey -p com.topjohnwu.magisk -c android.intent.category.LAUNCHER 1
```

--------------------------------

### Install Prebuilt Kernel Modules

Source: https://context7.com/newbit1/rootavd/llms.txt

Downloads and installs AOSP prebuilt kernel and modules from Google's repository. This is useful for USB passthrough and custom device support. The AVD must be online for this operation.

```bash
# Download and install prebuilt kernel modules (AVD must be online)
./rootAVD.sh system-images/android-33/google_apis_playstore/x86_64/ramdisk.img InstallPrebuiltKernelModules
```

```text
# Interactive menu appears:
# [*] Fetching Kernel Data:
# [-]              Android: 13
# [-]                 Arch: x86-64
# [-]                Uname: 5.15.41-android13-8-xxxxx-ab9458697
# [-]              Version: 5.15
# [-]        Build Version: 9458697
# [!] Installed Kernel builds 9458697
# [?] Choose a Prebuild Kernel/Module Version
# [1] Update kernel to builds 9876543
# [2] Update kernel to builds 9765432
```

--------------------------------

### Windows rootAVD.bat Script Examples for Android 25 (armeabi-v7a)

Source: https://github.com/newbit1/rootavd/blob/master/README.md

Examples of using rootAVD.bat with specific Android image paths and commands for API level 25 (armeabi-v7a) on Windows.

```batch
rootAVD.bat system-images\android-25\google_apis_playstore\armeabi-v7a\ramdisk.img
```

```batch
rootAVD.bat system-images\android-25\google_apis_playstore\armeabi-v7a\ramdisk.img FAKEBOOTIMG
```

```batch
rootAVD.bat system-images\android-25\google_apis_playstore\armeabi-v7a\ramdisk.img DEBUG PATCHFSTAB GetUSBHPmodZ
```

```batch
rootAVD.bat system-images\android-25\google_apis_playstore\armeabi-v7a\ramdisk.img restore
```

```batch
rootAVD.bat system-images\android-25\google_apis_playstore\armeabi-v7a\ramdisk.img InstallKernelModules
```

```batch
rootAVD.bat system-images\android-25\google_apis_playstore\armeabi-v7a\ramdisk.img InstallPrebuiltKernelModules
```

```batch
rootAVD.bat system-images\android-25\google_apis_playstore\armeabi-v7a\ramdisk.img InstallPrebuiltKernelModules GetUSBHPmodZ PATCHFSTAB DEBUG
```

--------------------------------

### Install APKs to AVD

Source: https://context7.com/newbit1/rootavd/llms.txt

Installs all APK files placed in the Apps folder to the running AVD. The script automatically handles version conflicts by uninstalling incompatible versions before reinstalling.

```bash
cp MyApp.apk Apps/
cp AnotherApp.apk Apps/
```

```bash
./rootAVD.sh InstallApps
```

--------------------------------

### Install Kernel Modules for rootAVD

Source: https://context7.com/newbit1/rootavd/llms.txt

Installs kernel modules into the ramdisk. This process involves backing up the original kernel, extracting modules, installing them, and replacing the kernel with bzImage. Source files are deleted after installation.

```bash
./rootAVD.sh system-images/android-33/google_apis_playstore/x86_64/ramdisk.img InstallKernelModules
```

--------------------------------

### Modifying System Images with rootAVD.sh

Source: https://github.com/newbit1/rootavd/blob/master/README.md

Examples of using rootAVD.sh to modify system images, including patching and restoring.

```bash
./rootAVD.sh system-images/android-33/google_apis_playstore/x86_64/ramdisk.img
./rootAVD.sh system-images/android-33/google_apis_playstore/x86_64/ramdisk.img FAKEBOOTIMG
./rootAVD.sh system-images/android-33/google_apis_playstore/x86_64/ramdisk.img DEBUG PATCHFSTAB GetUSBHPmodZ
./rootAVD.sh system-images/android-33/google_apis_playstore/x86_64/ramdisk.img restore
./rootAVD.sh system-images/android-33/google_apis_playstore/x86_64/ramdisk.img InstallKernelModules
./rootAVD.sh system-images/android-33/google_apis_playstore/x86_64/ramdisk.img InstallPrebuiltKernelModules
./rootAVD.sh system-images/android-33/google_apis_playstore/x86_64/ramdisk.img InstallPrebuiltKernelModules GetUSBHPmodZ PATCHFSTAB DEBUG
./rootAVD.sh system-images/android-33/google_apis_playstore/x86_64/ramdisk.img AddRCscripts
```

--------------------------------

### Windows rootAVD.bat Script Examples for Android 25 (x86_64)

Source: https://github.com/newbit1/rootavd/blob/master/README.md

Examples of using rootAVD.bat with specific Android image paths and commands for API level 25 (x86_64) on Windows.

```batch
rootAVD.bat system-images\android-25\google_apis_playstore\x86_64\ramdisk.img
```

```batch
rootAVD.bat system-images\android-25\google_apis_playstore\x86_64\ramdisk.img FAKEBOOTIMG
```

```batch
rootAVD.bat system-images\android-25\google_apis_playstore\x86_64\ramdisk.img DEBUG PATCHFSTAB GetUSBHPmodZ
```

```batch
rootAVD.bat system-images\android-25\google_apis_playstore\x86_64\ramdisk.img restore
```

```batch
rootAVD.bat system-images\android-25\google_apis_playstore\x86_64\ramdisk.img InstallKernelModules
```

```batch
rootAVD.bat system-images\android-25\google_apis_playstore\x86_64\ramdisk.img InstallPrebuiltKernelModules
```

```batch
rootAVD.bat system-images\android-25\google_apis_playstore\x86_64\ramdisk.img InstallPrebuiltKernelModules GetUSBHPmodZ PATCHFSTAB DEBUG
```

--------------------------------

### Linux rootAVD Script Examples

Source: https://github.com/newbit1/rootavd/blob/master/README.md

Execute rootAVD script with different commands and image paths on Linux systems.

```bash
./rootAVD.sh system-images/android-30/android-automotive-playstore/x86_64/ramdisk.img AddRCscripts
```

```bash
./rootAVD.sh system-images/android-29/android-automotive-playstore/x86/ramdisk.img
```

```bash
./rootAVD.sh system-images/android-29/android-automotive-playstore/x86/ramdisk.img FAKEBOOTIMG
```

```bash
./rootAVD.sh system-images/android-29/android-automotive-playstore/x86/ramdisk.img DEBUG PATCHFSTAB GetUSBHPmodZ
```

```bash
./rootAVD.sh system-images/android-29/android-automotive-playstore/x86/ramdisk.img restore
```

```bash
./rootAVD.sh system-images/android-29/android-automotive-playstore/x86/ramdisk.img InstallKernelModules
```

```bash
./rootAVD.sh system-images/android-29/android-automotive-playstore/x86/ramdisk.img InstallPrebuiltKernelModules
```

```bash
./rootAVD.sh system-images/android-29/android-automotive-playstore/x86/ramdisk.img InstallPrebuiltKernelModules GetUSBHPmodZ PATCHFSTAB DEBUG
```

```bash
./rootAVD.sh system-images/android-29/android-automotive-playstore/x86/ramdisk.img AddRCscripts
```

--------------------------------

### Add Custom RC Scripts to AVD

Source: https://context7.com/newbit1/rootavd/llms.txt

Installs custom init.rc scripts into the ramdisk's overlay.d directory. Place your *.rc files in the rootAVD folder before running. Scripts are added to ramdisk.img/overlay.d/, and files in the sbin/ folder are also included.

```bash
cat > init.custom.rc << 'EOF'
on boot
    setprop my.custom.property 1

service myservice /system/bin/myservice
    class main
    user root
    group root
EOF
```

```bash
./rootAVD.sh system-images/android-33/google_apis_playstore/x86_64/ramdisk.img AddRCscripts
```

--------------------------------

### Fake Boot Image Patching for Magisk 26+

Source: https://context7.com/newbit1/rootavd/llms.txt

Use this method for Magisk versions 26.x and above, which require a fake boot.img to be patched directly via the Magisk app due to sepolicy.rule changes. The script creates a minimal boot image and guides you through patching it within the Magisk app.

```bash
# Root AVD using fake boot.img method (required for Magisk 26+)
./rootAVD.sh system-images/android-33/google_apis_playstore/x86_64/ramdisk.img FAKEBOOTIMG
```

```text
# Process:
# 1. Script creates a fake boot.img with minimal header
# 2. Launches Magisk app automatically
# 3. You have 60 seconds to patch the fake boot.img in Magisk
# 4. Select "Install" -> "Select and Patch a File"
# 5. Navigate to /sdcard/Download/fakeboot.img
# 6. Press Enter when patching is complete

# The patched file will be at /sdcard/Download/magisk_patched_*.img
```

--------------------------------

### Windows rootAVD.bat Basic Commands

Source: https://github.com/newbit1/rootavd/blob/master/README.md

Basic commands for the rootAVD.bat script on Windows, including listing AVDs and installing apps.

```batch
rootAVD.bat
```

```batch
rootAVD.bat ListAllAVDs
```

```batch
rootAVD.bat InstallApps
```

--------------------------------

### Clone rootAVD Repository

Source: https://github.com/newbit1/rootavd/blob/master/README.md

Use git clone to download the rootAVD script and its associated files. Ensure you have Git installed on your system.

```bash
git clone https://github.com/newbit1/rootAVD.git
```

--------------------------------

### Launch AVD with Writable System (Windows)

Source: https://github.com/newbit1/rootavd/blob/master/README.md

Use this command to launch an Android Virtual Device (AVD) with a writable system partition, which is often required for rooting processes. Ensure your Android SDK emulator is added to your system's PATH.

```bash
set PATH=%LOCALAPPDATA%\Android\Sdk\emulator;%PATH%
emulator -list-avds
	Pixel_4_API_29
emulator -avd Pixel_4_API_29 -writable-system
```

--------------------------------

### Basic AVD Rooting with Magisk

Source: https://context7.com/newbit1/rootavd/llms.txt

Use this command to root an AVD with the default Magisk version. The script backs up the original ramdisk, pushes Magisk files, prompts for Magisk version selection, patches the ramdisk, and pulls the modified image back.

```bash
# Basic usage - root an AVD with the default Magisk version
./rootAVD.sh system-images/android-33/google_apis_playstore/x86_64/ramdisk.img
```

```text
# The script will:
# 1. Create a backup of ramdisk.img
# 2. Push Magisk files to the AVD
# 3. Present a menu to select Magisk version (Stable/Canary/Alpha)
# 4. Patch the ramdisk with Magisk
# 5. Pull the patched ramdisk back
# 6. Shut down the AVD
```

```text
# Expected output:
# [-] Magisk installer Zip exists already
# [*] Push ramdisk.img into /data/data/com.android.shell/Magisk
# [!] Checking available Magisk Versions
# [?] Choose a Magisk Version to install and make it local
# [1] local stable 25.2(25200) (ENTER)
# [2] stable 25.2(25200)
# [3] canary 25211(25211)
# [4] alpha 25212(25212)
```

--------------------------------

### rootAVD.sh Commands for Android 25 System Images

Source: https://github.com/newbit1/rootavd/blob/master/README.md

Demonstrates various operations on Android 25 system images, including ARM and x86 architectures.

```bash
./rootAVD.sh system-images/android-25/google_apis/armeabi-v7a/ramdisk.img
./rootAVD.sh system-images/android-25/google_apis/armeabi-v7a/ramdisk.img FAKEBOOTIMG
./rootAVD.sh system-images/android-25/google_apis/armeabi-v7a/ramdisk.img DEBUG PATCHFSTAB GetUSBHPmodZ
./rootAVD.sh system-images/android-25/google_apis/armeabi-v7a/ramdisk.img restore
./rootAVD.sh system-images/android-25/google_apis/armeabi-v7a/ramdisk.img InstallKernelModules
./rootAVD.sh system-images/android-25/google_apis/armeabi-v7a/ramdisk.img InstallPrebuiltKernelModules
./rootAVD.sh system-images/android-25/google_apis/armeabi-v7a/ramdisk.img InstallPrebuiltKernelModules GetUSBHPmodZ PATCHFSTAB DEBUG
./rootAVD.sh system-images/android-25/google_apis/armeabi-v7a/ramdisk.img AddRCscripts

./rootAVD.sh system-images/android-25/google_apis/x86_64/ramdisk.img
./rootAVD.sh system-images/android-25/google_apis/x86_64/ramdisk.img FAKEBOOTIMG
./rootAVD.sh system-images/android-25/google_apis/x86_64/ramdisk.img DEBUG PATCHFSTAB GetUSBHPmodZ
./rootAVD.sh system-images/android-25/google_apis/x86_64/ramdisk.img restore
./rootAVD.sh system-images/android-25/google_apis/x86_64/ramdisk.img InstallKernelModules
./rootAVD.sh system-images/android-25/google_apis/x86_64/ramdisk.img InstallPrebuiltKernelModules
./rootAVD.sh system-images/android-25/google_apis/x86_64/ramdisk.img InstallPrebuiltKernelModules GetUSBHPmodZ PATCHFSTAB DEBUG
./rootAVD.sh system-images/android-25/google_apis/x86_64/ramdisk.img AddRCscripts
```

--------------------------------

### rootAVD.sh Commands for Android 30 System Images

Source: https://github.com/newbit1/rootavd/blob/master/README.md

Illustrates various operations on Android 30 system images, including playstore and automotive variants.

```bash
./rootAVD.sh system-images/android-30/google_apis_playstore/x86/ramdisk.img
./rootAVD.sh system-images/android-30/google_apis_playstore/x86/ramdisk.img FAKEBOOTIMG
./rootAVD.sh system-images/android-30/google_apis_playstore/x86/ramdisk.img DEBUG PATCHFSTAB GetUSBHPmodZ
./rootAVD.sh system-images/android-30/google_apis_playstore/x86/ramdisk.img restore
./rootAVD.sh system-images/android-30/google_apis_playstore/x86/ramdisk.img InstallKernelModules
./rootAVD.sh system-images/android-30/google_apis_playstore/x86/ramdisk.img InstallPrebuiltKernelModules
./rootAVD.sh system-images/android-30/google_apis_playstore/x86/ramdisk.img InstallPrebuiltKernelModules GetUSBHPmodZ PATCHFSTAB DEBUG
./rootAVD.sh system-images/android-30/google_apis_playstore/x86/ramdisk.img AddRCscripts

./rootAVD.sh system-images/android-30/android-automotive-playstore/x86_64/ramdisk-qemu.img
./rootAVD.sh system-images/android-30/android-automotive-playstore/x86_64/ramdisk-qemu.img FAKEBOOTIMG
./rootAVD.sh system-images/android-30/android-automotive-playstore/x86_64/ramdisk-qemu.img DEBUG PATCHFSTAB GetUSBHPmodZ
./rootAVD.sh system-images/android-30/android-automotive-playstore/x86_64/ramdisk-qemu.img restore
./rootAVD.sh system-images/android-30/android-automotive-playstore/x86_64/ramdisk-qemu.img InstallKernelModules
./rootAVD.sh system-images/android-30/android-automotive-playstore/x86_64/ramdisk-qemu.img InstallPrebuiltKernelModules
./rootAVD.sh system-images/android-30/android-automotive-playstore/x86_64/ramdisk-qemu.img InstallPrebuiltKernelModules GetUSBHPmodZ PATCHFSTAB DEBUG
./rootAVD.sh system-images/android-30/android-automotive-playstore/x86_64/ramdisk-qemu.img AddRCscripts

./rootAVD.sh system-images/android-30/android-automotive-playstore/x86_64/ramdisk.img
./rootAVD.sh system-images/android-30/android-automotive-playstore/x86_64/ramdisk.img FAKEBOOTIMG
./rootAVD.sh system-images/android-30/android-automotive-playstore/x86_64/ramdisk.img DEBUG PATCHFSTAB GetUSBHPmodZ
./rootAVD.sh system-images/android-30/android-automotive-playstore/x86_64/ramdisk.img restore
./rootAVD.sh system-images/android-30/android-automotive-playstore/x86_64/ramdisk.img InstallKernelModules
./rootAVD.sh system-images/android-30/android-automotive-playstore/x86_64/ramdisk.img InstallPrebuiltKernelModules
./rootAVD.sh system-images/android-30/android-automotive-playstore/x86_64/ramdisk.img InstallPrebuiltKernelModules GetUSBHPmodZ PATCHFSTAB DEBUG
```

--------------------------------

### Windows Usage of rootAVD.bat

Source: https://context7.com/newbit1/rootavd/llms.txt

The Windows batch file provides equivalent functionality for Windows users with similar command syntax. It supports basic rooting, FAKEBOOTIMG method, combined options, restoring the original system, and listing all AVDs.

```batch
set PATH=%LOCALAPPDATA%\Android\Sdk\platform-tools;%PATH%
```

```batch
rootAVD.bat system-images\android-33\google_apis_playstore\x86_64\ramdisk.img
```

```batch
rootAVD.bat system-images\android-33\google_apis_playstore\x86_64\ramdisk.img FAKEBOOTIMG
```

```batch
rootAVD.bat system-images\android-33\google_apis_playstore\x86_64\ramdisk.img DEBUG PATCHFSTAB GetUSBHPmodZ
```

```batch
rootAVD.bat system-images\android-33\google_apis_playstore\x86_64\ramdisk.img restore
```

```batch
rootAVD.bat ListAllAVDs
```

--------------------------------

### Restore Original Ramdisk from Backup

Source: https://context7.com/newbit1/rootavd/llms.txt

This command restores the original ramdisk.img from its backup file. The backup files are preserved, allowing for easy reversion of changes without deleting them. The AVD does not need to be running for this operation.

```bash
# Restore original ramdisk.img from backup
./rootAVD.sh system-images/android-33/google_apis_playstore/x86_64/ramdisk.img restore
```

```text
# Output:
# [!] Restoring ramdisk.img.backup to ramdisk.img
# [*] Backups still remain in place

# Note: The AVD doesn't need to be running for this operation
# The .backup files are preserved for future use
```

--------------------------------

### Disable AVD Verification and Remount (Windows)

Source: https://github.com/newbit1/rootavd/blob/master/README.md

These commands are used in sequence to disable Android Verified Boot (AVB) and remount the system partition as read-write after an AVD has been launched with the -writable-system flag. This is a common step for rooting.

```bash
set PATH=%LOCALAPPDATA%\Android\Sdk\platform-tools;%PATH%
adb root
adb shell avbctl disable-verification
 adb disable-verity
 adb reboot
 adb root
 adb remount
 adb shell
generic_x86_64:/ #
```

--------------------------------

### Switch User for Granting Permissions

Source: https://github.com/newbit1/rootavd/blob/master/README.md

To grant Superuser permissions on an automotive AVD, you typically need to switch to user 0 and then back to user 10. This command performs the switch to user 10.

```bash
adb shell am switch-user 10
```

--------------------------------

### Patch fstab for USB Device Mounting

Source: https://context7.com/newbit1/rootavd/llms.txt

Patches fstab.ranchu to enable automatic mounting of USB block devices. This requires a custom kernel with Mass-Storage and SCSI support. The script adds a specific line to fstab.ranchu for USB device management.

```bash
./rootAVD.sh system-images/android-33/google_apis_playstore/x86_64/ramdisk.img PATCHFSTAB
```

```bash
./rootAVD.sh system-images/android-33/google_apis_playstore/x86_64/ramdisk.img InstallPrebuiltKernelModules GetUSBHPmodZ PATCHFSTAB
```

--------------------------------

### rootAVD Script Usage

Source: https://github.com/newbit1/rootavd/blob/master/README.md

This is the main usage syntax for the rootAVD script. It outlines the primary arguments and options available for operating the script.

```bash
rootAVD A Script to root AVD by NewBit XDA

Usage:  rootAVD [DIR/ramdisk.img] [OPTIONS] | [EXTRA ARGUMENTS]
or:     rootAVD [ARGUMENTS]

Arguments:
        ListAllAVDs                     Lists Command Examples for ALL installed AVDs

        InstallApps                     Just install all APKs placed in the Apps folder

Main operation mode:
        DIR                             a path to an AVD system-image
                                        - must always be the 1st Argument after rootAVD

ADB Path | Ramdisk DIR| ANDROID_HOME:
        [M]ac/Darwin:                   export PATH=~/Library/Android/sdk/platform-tools:$PATH
                                        export PATH=$ANDROID_HOME/platform-tools:$PATH
                                        system-images/android-$API/google_apis_playstore/x86_64/

        [L]inux:                        export PATH=~/Android/Sdk/platform-tools:$PATH
                                        export PATH=$ANDROID_HOME/platform-tools:$PATH
                                        system-images/android-$API/google_apis_playstore/x86_64/

        [W]indows:                      set PATH=%LOCALAPPDATA%\Android\Sdk\platform-tools;%PATH%
                                        system-images\android-$API\google_apis_playstore\x86_64\

        ANDROID_HOME:                   By default, the script uses %LOCALAPPDATA%, to set its Android Home
                                        directory, search for AVD system-images and ADB binarys. This behaviour
                                        can be overwritten by setting the ANDROID_HOME variable.
                                        e.g. set ANDROID_HOME=%USERPROFILE%\Downloads\sdk

        $API:                           25,29,30,31,32,33,34,UpsideDownCake,etc.

Options:
        restore                         restore all existing .backup files, but doesn't delete them
                                        - the AVD doesn't need to be running
                                        - no other Argument after will be processed

        InstallKernelModules            install custom build kernel and its modules into ramdisk.img
                                        - kernel (bzImage) and its modules (initramfs.img) are inside rootAVD
                                        - both files will be deleted after installation

        InstallPrebuiltKernelModules    download and install an AOSP prebuilt kernel and its modules into ramdisk.img
                                        - similar to InstallKernelModules, but the AVD needs to be online

Options are exclusive, only one at the time will be processed.

Extra Arguments:
        DEBUG                           Debugging Mode, prevents rootAVD to pull back any patched file

        PATCHFSTAB                      fstab.ranchu will get patched to automount Block Devices like /dev/block/sda1
                                        - other entries can be added in the script as well
                                        - a custom build Kernel might be necessary

        GetUSBHPmodZ                    The USB HOST Permissions Module Zip will be downloaded into /sdcard/Download

        FAKEBOOTIMG                     Creates a fake Boot.img file that can directly be patched from the Magisk APP
                                        - Magisk will be launched to patch the fake Boot.img within 60s
                                        - the fake Boot.img will be placed under /sdcard/Download/fakeboot.img

Extra Arguments can be combined, there is no particular order.

Notes: rootAVD will
- always create .backup files of ramdisk*.img and kernel-ranchu
- replace both when done patching
- show a Menu, to choose the Magisk Version (Stable || Canary || Alpha), if the AVD is online
- make the choosen Magisk Version to its local
- install all APKs placed in the Apps folder
- use %LOCALAPPDATA%\Android\Sdk to search for AVD system images
```

--------------------------------

### Switch User on Automotive AVD

Source: https://github.com/newbit1/rootavd/blob/master/README.md

After patching the ramdisk.img and cycling power on an automotive AVD, you need to switch to user 0 to access Magisk. This command facilitates that switch.

```bash
adb shell am switch-user 0
```

--------------------------------

### Configure ANDROID_HOME for SDK Location

Source: https://context7.com/newbit1/rootavd/llms.txt

Configures the ANDROID_HOME environment variable to specify a custom SDK location, overriding default paths. It's recommended to verify ADB connection before running the script.

```bash
export PATH=~/Library/Android/sdk/platform-tools:$PATH
```

```bash
export PATH=~/Android/Sdk/platform-tools:$PATH
```

```bash
export ANDROID_HOME=~/Downloads/custom-sdk
./rootAVD.sh system-images/android-33/google_apis_playstore/x86_64/ramdisk.img
```

```bash
adb devices
```

--------------------------------

### Root BlueStacks on macOS

Source: https://context7.com/newbit1/rootavd/llms.txt

Roots BlueStacks 4 emulator on macOS by patching its ramdisk. This process requires the built-in su binary to be accessible. Note that Zygisk does not work on BlueStacks.

```bash
./rootAVD.sh BLUESTACKS
```

```bash
adb shell monkey -p com.topjohnwu.magisk -c android.intent.category.LAUNCHER 1
```

--------------------------------

### Remove Users Higher Than 0

Source: https://github.com/newbit1/rootavd/blob/master/README.md

When using the Magisk Single User Mod, you may need to remove user IDs higher than 0. Use these commands to remove specific user IDs.

```bash
adb shell pm remove-user 13
 adb shell pm remove-user 10
```

--------------------------------

### Run rootAVD in Debug Mode

Source: https://context7.com/newbit1/rootavd/llms.txt

Prevents rootAVD from pulling patched files back, which is useful for testing modifications without affecting the actual AVD system image. Debug mode output shows all flag states.

```bash
./rootAVD.sh system-images/android-33/google_apis_playstore/x86_64/ramdisk.img DEBUG
```

```bash
./rootAVD.sh system-images/android-33/google_apis_playstore/x86_64/ramdisk.img DEBUG PATCHFSTAB GetUSBHPmodZ
```

=== COMPLETE CONTENT === This response contains all available snippets from this library. No additional content exists. Do not make further requests.