OpenADB Shell is a simple, open source command-line interface for interacting with ADB (Android Debug Bridge) on Windows. It provides a user-friendly shell with custom commands, configuration options, and direct access to standard ADB commands.

• Run any standard ADB command (no need to prefix with adb.exe)
• Custom commands for common tasks (list apps, connect/disconnect, clear, etc.)
• Configuration window to enable/disable custom commands
• Persistent configuration saved to config.dat
• Error handling for missing ADB tools
• Open source and easy to extend
• Discord Rich Presence support (optional)
• Mod support for custom functionality (e.g., rich presence)
• Portable - run from any non-protected directory without installation
• Windows Terminal integration guide
• Autoconnect to chosen devices on shell start
• Custom device management (save, connect, disconnect, remove)
• WSA (Windows Subsystem for Android) support for ADB connections
• Local ADB server connection support

1. Download the latest release zip from GitHub Releases.
2. Unzip the file into a folder (e.g., your Documents folder). Note: This app is fully portable and can be run from any non-protected directory.
3. Download the latest Android SDK Platform Tools for Windows: Platform Tools Download
4. In your openadbshell directory, create a folder named adb.
5. Unzip the platform tools and move all files directly into the adb folder (so you have adb/adb.exe, etc.).
6. Run openadbshell.exe to start the shell.

Your directory structure should look like this:

openadbshell/
  openadbshell.exe
  adb/
    adb.exe
    ...other platform tools files...
  mods/
    running.dat (created after first run)
    devices.dat (created after first run)
    rich_presence/
      mod.exe
      presence.exe
      enabled.dat (created after first run)
      _internal/
        ...internal files...
  config.dat (created after first run)
  README.md
  LICENSE
  _internal/
    ...internal files...

1. Follow the installation steps above.
2. Open Windows Terminal > Settings > Add a new profile (duplicate Command Prompt).
3. Set the name to "OpenADB Shell".
4. Set the command line executable to the path of openadbshell.exe.
5. Set the starting directory to your openadbshell folder.
6. Save and launch from Windows Terminal.

• Type help for a list of available custom commands.
• Type any standard ADB command (without the adb.exe prefix) to run it directly.
• Type config to open the configuration window and enable/disable custom commands and manage custom devices saved.
• If custom commands are disabled, only standard ADB commands will work (except all config commands).

• The shell saves your custom command preference in config.dat.
• You can change this at any time by running the config command or running one of the dedicated config commands above for particular settings.
• The config commands are never affected by the do_cust_command setting.

• OpenADB Shell supports Discord Rich Presence integration.
• If Discord is running, it will show this app as running in your status and how many devices are connected.
• You can disable this feature in the configuration window (Enabled by default) or by one of the config commands.
• You can also permanently remove it by deleting the rich_presence folder in the mods directory or running the config delete command.

• OpenADB Shell supports mods. Mods are custom executables that are run when the shell starts. Their output is displayed in the shell.
• All functions of the shell are paused while a mod is running. If the mod is meant to run in the background, I recommend mod.exe simply being the launcher for your mod, which then runs in the background (to avoid blocking the shell).
• To create a mod, name your executable mod.exe and place it with any dependencies in a unique folder inside the mods directory.
• The shell will automatically detect and run any executables named "mod.exe" in folders inside the mods folder.
• Mods are disabled by default but can be enabled in the configuration window or by one of the config commands.
• Mods are just what I decided to call them. They are more like scripts that run on startup. Example structure:

openadbshell/
  mods/
    mymodfolder/
      mod.exe
      

• Mods function as described above. Refer to the included rich presence mod for an example.
• Note: The working directory for all mods is the directory of the shell executable (i.e., where openadbshell.exe is located).
• There are two data files that may be useful to makers (both are found in the mods directory):
  • running.dat - The shell writes the current datetime() to this file every 10 seconds while the shell is running. If the shell stops writing to this file, it means the shell has exited.
  • devices.dat - The shell writes the number of connected devices to this file every 10 seconds while the shell is running.

• Windows OS
• Android SDK Platform Tools (in the adb folder)
• Python (for running the script directly) or use the provided EXE

See LICENSE.

Not affiliated with Android, Google, Microsoft, Discord, or Windows.

Created by lukbrew25