ADB Command Reference

Find an ADB command by task or syntax

This ADB command reference is a searchable collection of 76 records for common Android Debug Bridge and Android shell commands. Use it when you know the task—such as checking a connection, installing an APK, reading logs, or moving a file—but need a syntax reminder or a worked command line. ADB itself is a command-line tool used from a computer to communicate with an Android device or emulator. Its commands can be handled by the computer-side client or sent to the device, depending on the command. Android Developers’ ADB documentation describes these roles and the main command groups.

The reference groups records into device connection, device information, app management, file transfer, log debugging, shell operations, screen capture, system operations, network and ports, and performance debugging. Each record presents a command name, short description, syntax, and example; some include a note about options or conditions. The collection is a practical index, not an exhaustive inventory of every command in every Platform Tools release or every shell command available on Android.

Read placeholders and examples correctly

In a syntax line, text in angle brackets such as <serial>, <package>, <local>, or <remote> stands for a value you supply. Replace it with a real serial number, package name, or path before running the command. Brackets around an option commonly mark it as optional in the displayed syntax; the command’s own help is the authority for exact grammar. Example values are illustrative and may need to match your computer, device, Android release, and shell.

For instance, adb devices -l asks ADB to list connected devices with additional details. In a multi-device setup, adb -s emulator-5554 shell pm list packages makes the target explicit. The -s selector takes a device serial; confirm the value in your own device list before using it. The ADB project’s command manual documents the command-line options and syntax.

What the reference filters and returns

Type a command name or a task-related word in the keyword field. Matching is case-insensitive and checks the record’s command name, description, syntax, example, and any note. You can combine a keyword with one category to narrow the list; choose All to search across categories again. The result area shows the number of matches and the matching command cards, or an empty-state message when nothing matches.

Each card has separate copy actions for the command name, syntax, and example. Copying places that text on your clipboard for review in a terminal or script. The page is a reference only: it does not connect to a phone, inspect your installed ADB version, validate a command against your device, or execute commands for you.

A quick workflow for choosing a command

1. Start with the outcome you need. Search a command such as adb pull, or a task word such as logcat, install, or screenshot.

2. Use a category if the results are broad. For example, choose File Transfer for push or pull, or Log Debugging for log collection and filtering.

3. Read the description and syntax together, then check the example and note. Replace placeholders with your actual values; do not paste angle-bracket placeholders literally.

4. Copy the syntax or example, inspect the target device and paths, then run it in a terminal where ADB is installed. If several devices are connected, first check adb devices -l and add adb -s <serial> to commands that need a specific target.

5. If no record matches, try a command fragment, a shorter task word, or another category. Consult the help for your installed ADB build for commands or flags that are not listed.

Pair common tasks without assuming one device setup

For a basic connection check, search devices. For an APK install, look up adb install and use the path to the APK on your computer. For a device-to-computer file copy, look up adb pull; for a computer-to-device copy, use adb push. These commands use different path directions, so verify which side each path belongs to before execution.

For logs, search logcat and inspect the filter syntax and shell quoting note. A filter that works in one terminal may need different quoting in another. When collecting output to a local file, the redirection operator is interpreted by your computer’s shell, not by the reference page.

Questions that come up while using an ADB reference

Check the target, version, and side effects

ADB commands can change or remove data, alter system settings, stop apps, reboot a device, or expose diagnostic information. Before executing a copied line, verify the device serial, package, destination path, flags, and shell interpretation. Be especially careful with commands that clear app data, remove files, remount partitions, change settings, or run as root. Use debugging only on devices you own or are authorized to administer, and review logs or bug reports before sharing because they may contain sensitive information.

Command availability and behavior depend on the ADB version, Android release, device build, permissions, and host shell. Entries in this reference are examples for lookup, not a guarantee that a command will work or be safe in every environment. For exact current syntax, inspect the help from your installed ADB tools and the Android project documentation.