Android ADB troubleshooting commands: Step-by-step commands for resolving common ADB connection states, restarting the server, reconnecting transports and collecting diagnostic logs. This guide explains what each command does, its syntax, practical examples, useful options, and common mistakes. Commands are shown for typical installations; flags can vary across operating-system and tool versions.
Before you start
Open a terminal appropriate for the operating system shown in the examples. Check that the required tool is installed and that you are running it with the permissions needed for your task. Replace sample names, paths, hostnames and IDs with values from your own environment.
Syntax at a glance
Square brackets usually indicate optional arguments, while uppercase words such as FILE, HOST and PACKAGE are placeholders that you replace. Keep quotes around paths or text that contains spaces. Commands should be tested on a safe sample before being used in production.
Quick command reference
| Command | What it does | Example | Useful options |
|---|---|---|---|
adb kill-server | Stop the local ADB server | adb kill-server | Usually followed automatically by a restarted server command |
adb start-server | Start the local ADB server | adb start-server | The server normally starts when another ADB command needs it |
adb devices -l | Check device state and transport details | adb devices -l | unauthorized means approve the host on the phone; offline means transport is not ready |
adb reconnect | Reconnect ADB transports | adb reconnect device | Specific transport options vary by platform-tools version |
adb logcat -d | Save current device logs for diagnosis | adb logcat -d -t 500 > recent-log.txt | -t limits output to recent lines on supported versions |
Command syntax and examples explained
1. adb kill-server
Purpose: Stop the local ADB server.
Syntax
adb kill-serverExample
adb kill-serverOptions and notes: Usually followed automatically by a restarted server command.
Useful when ADB appears stuck; disconnect/reconnect USB if needed.
2. adb start-server
Purpose: Start the local ADB server.
Syntax
adb start-serverExample
adb start-serverOptions and notes: The server normally starts when another ADB command needs it.
Run from a terminal where the Android platform-tools are on PATH.
3. adb devices -l
Purpose: Check device state and transport details.
Syntax
adb devices -lExample
adb devices -lOptions and notes: unauthorized means approve the host on the phone; offline means transport is not ready.
Use a known data-capable USB cable and enable USB debugging.
4. adb reconnect
Purpose: Reconnect ADB transports.
Syntax
adb reconnectExample
adb reconnect deviceOptions and notes: Specific transport options vary by platform-tools version.
This can help with TCP/USB transport issues but cannot repair a bad cable.
5. adb logcat -d
Purpose: Save current device logs for diagnosis.
Syntax
adb logcat -d > adb-log.txtExample
adb logcat -d -t 500 > recent-log.txtOptions and notes: -t limits output to recent lines on supported versions.
Check logs for personal data and credentials before sharing them.
Common mistakes and troubleshooting
- Command not found: confirm the tool is installed and available on your PATH; open a new terminal after changing PATH.
- Permission denied: verify the current account, file permissions and target path. Use administrator/root privileges only when genuinely required.
- Unexpected output: check the command version, quoting, current directory and exact arguments. Consult the local help or manual for options supported by your build.
- Destructive operations: preview the target and keep a backup before deleting data, rewriting history, flashing a partition or changing system configuration.
Safety tips
Review every command before running it, especially commands that delete files, change permissions, flash firmware, alter a database or expose a network service. For network scanning and remote administration, work only on devices and systems you own or are authorized to test. Keep credentials, private keys, access tokens and log files private.
Frequently asked questions
Do these commands work on every system?
Not always. Some commands are specific to Windows, Linux, Android, a particular package manager or an installed tool version. Use the syntax shown for your platform and check local help when a flag is unavailable.
Can I copy and run every example exactly?
Use the examples as templates. Replace placeholders such as filenames, package IDs, hostnames and paths with your own values, and verify the effect before executing a command that changes data or system state.
Conclusion
Use this reference as a starting point, then confirm flags in the tool’s official help or manual for your installed version. A clear understanding of syntax, options and side effects makes command-line work more reliable.