Next-Gen App & Browser Testing Cloud

Trusted by 2 Mn+ QAs & Devs to accelerate their release cycles

How to Open Android Debug Bridge?

There is no app icon to click for Android Debug Bridge. Opening ADB means launching a terminal or Command Prompt where the adb binary is available, starting the ADB server in the background, and confirming a device is connected. The three-step launch is the same on every operating system:

Open a terminal, Command Prompt, or PowerShell window.
Make sure ADB is reachable, either through your PATH or by changing into the platform-tools folder.
Start the server and confirm your device with adb devices.

adb start-server   # starts the ADB background daemon (server) if not already running
adb devices        # confirms ADB is open and lists connected devices

What Is Android Debug Bridge (ADB) and What Does "Opening" It Mean?

Android Debug Bridge (ADB) is a command-line tool that lets your computer communicate with an Android device or emulator. It is built on a client-server model with three moving parts: the client that runs each time you type an adb command, the server (a background process on your computer that manages communication and listens on port 5037), and the daemon called adbd that runs on the device and executes your commands.

Because of that architecture, "opening ADB" is not about launching a window. It means getting to a place where the client can run, the server is alive, and the daemon on the device trusts your machine. Once those three pieces are talking, ADB is open and ready for shell access, installs, log streaming, and automation.

Prerequisites Before You Open ADB

A few things need to be in place before any adb command will work:

platform-tools installed: ADB ships inside the Android SDK platform-tools package. Install it through Android Studio or download the standalone ZIP. For the full walkthrough, see the How to Setup Android Debug Bridge? guide.
USB Debugging enabled: on the device, open Settings, tap the build number seven times to unlock Developer Options, then switch on USB Debugging.
Device connected: plug the device in over USB in file-transfer (MTP) mode, or use Wi-Fi for wireless ADB on Android 11 and later.

A quick way to confirm the adb binary itself is found:

adb version

How to Open ADB on Windows

On Windows you have two paths depending on whether ADB is on your system PATH:

adb is on PATH: open Command Prompt or PowerShell from anywhere and run adb directly.
adb is not on PATH: open the platform-tools folder in File Explorer, Shift + right-click and choose "Open PowerShell window here," or change into the folder manually.

cd C:\platform-tools
adb devices

In PowerShell, if the current folder is not searched automatically, prefix the binary with ./ so it runs as ./adb devices.

How to Open ADB on macOS and Linux

Open the Terminal app. If ADB is on your PATH, run adb from any directory. If not, change into the platform-tools folder first. The default Android Studio location looks like this:

cd ~/Android/Sdk/platform-tools   # default Android Studio path on macOS/Linux
./adb devices

To avoid typing the path every time, add platform-tools to your PATH in ~/.zshrc (macOS) or ~/.bashrc (Linux) so that adb works from any directory. The setup guide linked above covers the exact lines to add.

Start, Stop, and Restart the ADB Server

The ADB server is the background process that brokers every connection. It binds to local port 5037 and stays alive until you stop it. Knowing how to control it is the difference between "ADB is open" and "ADB is stuck." These are the commands you reach for:

adb start-server                      # launch the ADB server (daemon) manually
adb kill-server                       # stop the server
adb kill-server && adb start-server   # restart to fix a stuck or flaky connection

Most commands, including adb devices, auto-start the server if it is not running, so you mainly call these explicitly to reset state when a device drops to offline or a command hangs.

Confirm ADB Is Open With adb devices and the Authorization Prompt

Running adb devices prints a table of every device the server can see, along with its state:

adb devices
# List of devices attached
# R58M1234ABC    device

The first time you connect, the device shows an Allow USB debugging? prompt with your computer's RSA key fingerprint. Tap Allow (and optionally "Always allow from this computer") to authorize the connection. The states you will see mean the following:

device: the device is authorized and ready for commands.
unauthorized: the RSA prompt has not been accepted yet, so accept it on the device.
offline: the connection dropped; reconnect the cable or restart the server.
no permissions: on Linux, your user lacks USB access, which is fixed with a udev rule.

Open ADB Wirelessly (Android 11+)

On Android 11 and later you can open ADB entirely over Wi-Fi. Turn on Wireless debugging in Developer Options, choose "Pair device with pairing code," then pair and connect from your terminal:

adb pair 192.168.1.50:37123     # enter the 6-digit pairing code shown on the device
adb connect 192.168.1.50:5555   # connect over Wi-Fi
adb devices

On older devices there is no pairing step. Connect once over USB, switch the device into TCP/IP mode, then connect over the network:

adb tcpip 5555
adb connect 192.168.1.50:5555

Common ADB Commands to Run Once It's Open

With ADB open and a device authorized, these are the launch-essential commands you will use most:

adb shell                 # open an interactive shell on the device
adb install app.apk       # install an APK
adb uninstall <package>   # remove an app by package name
adb logcat                # stream device logs in real time
adb push file /sdcard/    # copy a file from computer to device
adb pull /sdcard/file .   # copy a file from device to computer

For the complete catalog across install, shell, logcat, backup, and fastboot, see How to Use ADB Android Debug Bridge?.

Troubleshooting: ADB Opens but No Device Shows

If ADB launches but adb devices is empty or shows the wrong state, work through these in order:

Empty list: check the USB cable and port, confirm the connection is set to file transfer (MTP), and verify USB Debugging is still enabled on the device.
unauthorized: accept the RSA prompt on the device. If it never appears, run adb kill-server and reconnect, or revoke USB debugging authorizations in Developer Options and try again.
Device not recognized on Windows: open Device Manager and install the OEM or Google USB driver for the handset.
adb: command not found or not recognized: the binary is not on your PATH, so cd into platform-tools or add the folder to PATH.
Server stuck or port 5037 in use: run adb kill-server followed by adb start-server to free the port and start fresh.

Skip Local ADB Setup: Open Real Android Devices in the Cloud

Configuring ADB, drivers, and PATH on every machine gets tedious when you only need to run a quick test. Instead of wiring up local ADB, you can run Appium and real-device app sessions on a cloud of real Android handsets, where ADB shell commands are supported inside the session. With TestMu AI's Real Device Cloud you upload an APK, pick a physical device, and interact with it in your browser without configuring anything locally.

Frequently Asked Questions

What does opening ADB actually do?

There is no graphical app to open. Opening ADB means launching a terminal or Command Prompt where the adb binary is reachable and making sure the ADB server is running. Running adb start-server launches that server, and adb devices confirms ADB is open by listing every connected device.

What is the difference between adb start-server and adb devices?

adb start-server launches the ADB server process on your machine, which listens on port 5037 and manages communication with devices. adb devices queries that server and prints attached devices and their states. In practice adb devices auto-starts the server, so you rarely call start-server manually except to reset a stuck connection.

Why does my device show as unauthorized when I open ADB?

An unauthorized state means the device has not yet trusted your computer's RSA key. Unlock the device and tap Allow on the "Allow USB debugging?" prompt, optionally checking "Always allow from this computer." If the prompt never appears, run adb kill-server and reconnect, or revoke USB debugging authorizations in Developer Options.

Can I open and use ADB without a USB cable?

Yes. On Android 11 and later you can enable Wireless debugging in Developer Options, pair with adb pair, and connect over Wi-Fi with adb connect. On older devices you start once over USB, switch the device to TCP/IP mode with adb tcpip 5555, then run adb connect with the device IP address.

Do I need Android Studio to open ADB?

No. ADB ships inside the Android SDK platform-tools package, which you can download as a standalone ZIP without installing Android Studio. Unzip it, open a terminal in that folder or add it to your PATH, and you can run adb commands immediately.

How do I restart ADB if it stops responding?

Stop and restart the server. Run adb kill-server to shut down the daemon, then adb start-server to launch a fresh one. This clears a stuck or flaky connection and frees port 5037, and is the first thing to try when devices show as offline or commands hang.