What is ADB (Android Debug Bridge)?

If you have ever searched for how to install an APK from a PC, enable wireless screen mirroring, or read Android logs without rooting, you have almost certainly run into ADB. It is the backbone of Android device management on a computer, used by developers, QA testers, and power users worldwide. According to Google's Android developer documentation, ADB has been part of the Android SDK Platform Tools since Android 1.0 and remains the primary command-line interface for Android device communication.

This guide explains what ADB is, how it actually works under the hood, what you can do with it, and how tools like Andora wrap it in a graphical interface so you never have to touch a terminal.

How ADB Works

ADB uses a client-server architecture with three components working together:

• ADB client — the program you run on your PC. Every time you type an adb command, you are invoking the client.
• ADB daemon (adbd) — a background process that runs on your Android device itself. It listens for commands from the ADB server and executes them on the device.
• ADB server — a background process on your PC that manages communication between clients and connected devices. It starts automatically when you run your first adb command.

The client and server communicate over TCP port 5037 on your local machine. The server then talks to the device daemon either over USB or over a TCP/IP connection on your network — the latter is what makes wireless ADB possible.

When you connect an Android device via USB with USB debugging enabled, the device shows an RSA key fingerprint prompt. Once you tap "Always allow from this computer," the device trusts that PC's ADB server and commands flow freely.

What Can You Do With ADB?

ADB is surprisingly capable. Here is a breakdown of the major things it lets you do:

Install and manage apps

The most common use case. You can install any APK file directly from your PC without touching the device's screen. This is called sideloading. You can also uninstall apps, clear app data, and grant or revoke permissions — all from your computer.

Transfer files

ADB lets you push files from your PC to the device and pull files from the device to your PC. This works even on devices where MTP file transfer is unreliable or not available.

Read system logs

The adb logcat command streams live log output from every process running on the device. Developers use this extensively to debug crashes and unexpected behavior. Power users use it to see what apps are doing in the background.

Run shell commands

ADB gives you a Unix shell on your Android device via adb shell. From there you can navigate the file system, inspect running processes, modify system settings, and a great deal more — depending on what your device allows without root.

Screen mirroring and input

Tools like scrcpy (and Andora's Pro screen mirroring feature) use ADB to capture the screen and relay touch input back to the device. Because it goes over ADB rather than WiFi casting protocols, latency is very low. See our guide on what screen mirroring is for the full comparison.

Common ADB Commands

Below are the commands you will use most often. These assume you have ADB on your PATH and a device connected with USB debugging on.

# List all connected devices
adb devices

# Install an APK
adb install path\to\app.apk

# Install, replacing an existing version
adb install -r path\to\app.apk

# Copy a file from PC to device
adb push C:\file.txt /sdcard/file.txt

# Copy a file from device to PC
adb pull /sdcard/DCIM/photo.jpg C:\photo.jpg

# Open a shell on the device
adb shell

# Run a single shell command
adb shell pm list packages

# Stream live logs
adb logcat

# Stream logs filtered to one app
adb logcat --pid=$(adb shell pidof -s com.example.app)

# Reboot the device
adb reboot

# Switch to wireless ADB on port 5555
adb tcpip 5555
adb connect 192.168.1.100:5555

You can also learn more in our dedicated tutorial on how to install APKs from a PC, which walks through the ADB install flow step by step.

Who Uses ADB?

ADB is not just for developers. Here are the main groups that rely on it regularly:

• Android developers — testing builds during development, reading crash logs, profiling performance, automating test suites with tools like UIAutomator.
• QA testers — installing builds on multiple devices, capturing logs when a bug is reproduced, scripting test device setup.
• IT administrators — provisioning corporate Android devices, pushing configuration files, managing app installations in bulk.
• Power users and enthusiasts — sideloading apps, enabling hidden settings, backing up data, debloating manufacturer software.
• Gamers and streamers — using screen mirroring tools to stream Android games on a PC display or capture gameplay.

The Problem With Raw ADB

ADB is powerful, but the setup friction is real. To use it on Windows you need to:

1. Download the Android SDK Platform Tools package from Google.
2. Extract it somewhere and add the folder to your system PATH, or navigate to it in every terminal session.
3. Install the correct USB driver for your device (often a manufacturer-specific driver that is frustratingly hard to find).
4. Enable USB debugging on the device.
5. Deal with the RSA fingerprint prompt.
6. Remember the exact command syntax every time you want to do something.

For developers this is a one-time setup they do and forget. For everyone else — a parent trying to install an app on their child's device, someone sideloading a streaming app, a tester who is not primarily technical — it is a significant barrier.

How Andora Wraps ADB in a GUI

Andora bundles ADB internally. There is no SDK to download, no PATH to configure, and no driver hunting. You install Andora, plug in your device (or connect wirelessly), and everything just works.

The free version of Andora covers the most common ADB use cases through a clean interface:

• APK Installer — drag and drop an APK file and Andora runs adb install behind the scenes. Read the full guide: how to install APK from PC.
• File Browser — push and pull files with a two-panel file manager, no commands needed.
• Logcat viewer — live log streaming with filtering and color coding, equivalent to adb logcat but readable.
• Device Info — hardware specs, Android version, connected state, all in one place.

Andora Pro adds screen mirroring with touch control and wireless ADB connection, which lets you do everything over WiFi without a cable. See the wireless ADB explainer for how that works.

ADB Security Considerations

ADB access is protected by the RSA key prompt — your device will ask you to authorize each new computer. That said, a few things are worth knowing:

• An authorized ADB connection gives the computer broad access to your device's file system and processes. Only connect to computers you trust.
• USB debugging should be turned off when you are in public places and plugging into unknown USB ports (e.g., public charging stations), because a malicious host could attempt to exploit an open ADB connection.
• On devices running Android 4.4.2 and later, the RSA fingerprint requirement makes it much harder for unauthorized connections to succeed, even if USB debugging is enabled.
• Wireless ADB is only as secure as your network. Use it on a trusted home or office network, not on public WiFi.