ADB Commands: Complete Cheat Sheet for Android (2026)

Introduction

ADB (Android Debug Bridge) is a powerful command-line tool for interacting with Android devices. It allows developers, testers, and advanced users to install apps, manage files, obtain system logs, execute shell commands on the device, and perform low-level operations. This cheat sheet compiles the most frequently used ADB and Fastboot commands to simplify debugging, administration, and everyday management of Android devices.

Requirements

Before you begin, ensure the following conditions are met:

• Android SDK Platform-Tools are installed on your computer (they contain adb and fastboot). Download from the official Google website.
• USB debugging is enabled on the Android device: Settings → About phone → Build number (tap 7 times) → Settings → Developer options → USB debugging.
• The device is connected to the computer via a USB cable (original or high-quality alternative recommended).
• For Windows, ADB/Fastboot drivers may be required (usually installed automatically or manually from the usb_driver folder).
• The PATH environment variable must include the platform-tools folder (or run commands from within that folder).

Basic Device Interaction Commands

These commands form the foundation for any interaction with a device via ADB. They allow you to check connectivity, manage device state, copy files, and install apps.

App Management

These commands allow you to manage the app lifecycle, obtain information about apps, and perform actions without a graphical interface.

File System Operations

Commands for navigating, viewing, and manipulating files and folders on the device.

Debugging and Logs

Commands for obtaining system information, monitoring activity, and analyzing logs.

Fastboot Commands

Fastboot is used when the device is booted into the bootloader. Commands are executed via the fastboot utility (included in Platform-Tools). To enter fastboot: adb reboot bootloader.

⚠️ Important: Fastboot commands can render a device unusable (brick). Always read the documentation for your specific model, ensure image compatibility, and have sufficient battery charge (at least 50%).

Verifying Results

After executing any ADB/Fastboot command, the result is displayed in the terminal:

• Success: Many commands produce no output on success (e.g., adb install). Verify indirectly (app installed, file appeared).
• Device status: adb devices should list your device with status device. If unauthorized — confirm the prompt on the device.
• Logs: For commands that should produce output (e.g., adb shell getprop), check that the output matches expectations.
• Permissions: Some commands require superuser (root) privileges. If you get Permission denied, try adb root (on user builds) or adb shell su -c <command> (if the device is rooted).

Common Issues

Device not showing up in adb devices

• Cause: USB debugging not enabled or confirmed, faulty cable/port, missing drivers.
• Solution:
  1. Check if USB debugging is enabled in Developer options.
  2. Reconnect the cable, try a different port or cable.
  3. On Windows: install ADB drivers (e.g., via Universal ADB Drivers) or restart the ADB server: adb kill-server && adb start-server.
  4. On the device, change the USB mode to "File Transfer (MTP)" or "PTP".

"device offline" error

• Cause: ADB server cannot establish a connection with the device.
• Solution:
  1. Disconnect and reconnect the device, confirm the debugging prompt.
  2. Restart ADB: adb kill-server && adb start-server.
  3. Reboot both the device and the computer.

"error: closed" or "no devices/emulators"

• Cause: ADB server is not running or port 5037 (default for ADB) is in use.
• Solution: Run adb start-server or terminate processes using port 5037.

Fastboot does not recognize the device

• Cause: Device not in fastboot mode, missing drivers (Windows), cable does not support data transfer.
• Solution:
  1. Ensure the device screen shows the fastboot logo (usually a black screen with text).
  2. For Windows: install fastboot drivers (e.g., from the usb_driver folder in Platform-Tools or via Zadig).
  3. Try a different USB port (USB 2.0 preferred) and cable.

"Permission denied" when running commands in adb shell

• Cause: Command requires superuser (root) privileges, but the device is not rooted.
• Solution:
  1. Obtain root access on the device (if supported).
  2. Use adb shell su -c "<command>" to execute the command as root.
  3. For some system commands (e.g., setprop), a reboot into ADB root mode is required: adb root (works only on user builds like AOSP).

APK installation does not complete

• Cause: Insufficient storage, permission conflict, or corrupted APK.
• Solution:
  1. Check free space: adb shell df.
  2. Install with the -r flag to reinstall: adb install -r app.apk.
  3. Ensure the APK is compatible with the device's architecture and Android version.
  4. Use adb logcat during installation for debugging.