Guide · Open source
How to use awesome-adb: ADB commands by task
Updated · written with AI from the project's own documentation and checked against our catalogue data
awesome-adb is a curated, Chinese-language guide to ADB (Android Debug Bridge), the command-line tool that lets a computer talk to an Android device or emulator. It is written for Android developers, testers and hobbyists who need the exact command for a task. After reading this page you will know how the guide is organised, how to pick a target device, and how to run the most common connection, app and log commands it lists.
Quick start
- 1Install Platform-Tools. Install Android SDK Platform-Tools so the adb command is available on your computer.
- 2Enable USB debugging. On the Android device, turn on developer options and USB debugging.
- 3Connect and check. Connect the device by USB and run adb devices. Look for the state device next to the serial number.
- 4Find the command you need. Open the guide and find the section for your task, such as app management, logs or device information.
- 5Add a target if needed. If more than one device is connected, add -s with the serial number from adb devices to your command.
- 6Run and check output. Run the command and compare the output with the example shown in the guide.
What you need before you start
The guide assumes you have the Android SDK Platform-Tools installed, since that package includes the adb tool. You also need USB debugging enabled on the Android device, which is found under Settings, then Developer options, then Android debugging.
- Android SDK Platform-Tools (includes adb)
- USB debugging enabled on the Android device
- Optional: an Android emulator or a device on the same Wi-Fi network for wireless use
Get a copy of the awesome-adb guide
The project is read online, but you can also keep a local copy of the repository. Clone it with the command below, then open the README in the repository folder.
The main README is in Chinese. An English version is linked from it as README.en.md.
git clone https://github.com/mzlogin/awesome-adbLearn the basic command syntax and target a device
The general form of an adb command is shown in the guide. If only one device or emulator is connected, you can leave out the device selector. When several are connected, use -s with a serial number, which you can get from adb devices.
The guide lists -d for the only USB-connected Android device, -e for the only running emulator, and -s <serialNumber> for a specific device.
- -d targets the only device connected over USB
- -e targets the only running emulator
- -s <serialNumber> targets a device with that serial number
adb -s cf264b8f shell wm sizeConnect a device and check its status
Run adb devices to list connected devices. The state column matters: device means connected, offline means the device is not connecting or not responding, and an empty list means nothing is connected. A device can show as device while Android is still booting, so wait until the system is fully usable.
For USB, the guide asks you to check hardware, USB debugging, and on Windows the driver status in Device Manager.
- device: connected (system may still be starting)
- offline: not connected or not responding
- no output after the header: no device connected
adb devicesManage apps and read logs
The guide groups app commands under listing, installing, uninstalling, enabling and disabling, clearing data, and checking the foreground activity. For logs, it covers filtering by level, filtering by tag and level, and clearing the log. Kernel logs are covered in their own section.
Command support can vary by Android version and custom ROM, so if a command fails, try the alternatives listed in the same section.
- Install an APK with adb install
- List apps, including system and third-party apps
- Filter Android logs by level or by tag and level
- Clear the log buffer
adb -s 10.129.164.6:5555 install test.apkUse wireless debugging
On Android 11 and later, the guide describes pairing with a pairing code and then connecting with the IP address and port shown in Wireless debugging. Older setups are covered too: you first connect with USB, enable TCP/IP on port 5555, unplug, then connect by IP address.
If the connection fails, make sure both devices are on the same Wi-Fi network, then run adb kill-server and try again.
- Android 11 and later: adb pair, then adb connect with ip:port
- Older devices: adb tcpip 5555 while connected by USB, then adb connect
- Disconnect with adb disconnect
adb connect <device-ip-address>What people use it for
- Install a test APK onto a device or emulator from the command line
- Read Android logs filtered by tag and level while reproducing a bug
- Copy files from a device to your computer or back again
- Take a screenshot or record the screen for a bug report
- Check device details such as model, Android version, screen density and battery status
Frequently asked questions
Is awesome-adb free to use?
The repository is released under the MIT licence. The guide is read online, and you can clone the repository from GitHub to keep a local copy.
Is there an English version of awesome-adb?
The main README is in Chinese. The project links to an English version, README.en.md, from the top of the README.
What are the requirements for using ADB with awesome-adb?
You need Android SDK Platform-Tools, which includes adb, and USB debugging enabled on the Android device. The guide also expects you to type commands in a terminal.
Why does my device show offline in adb devices?
The guide says offline means the device is not connected successfully or is not responding. Check the cable and hardware, confirm USB debugging is on, then run adb kill-server and reconnect.
Will every command work on my phone?
No. The README warns that some command support depends on the Android version and on custom ROM implementation, so a command may behave differently on your device.
What are alternatives to awesome-adb?
The project lists comparable tools including scrcpy, Genymotion and adb-shell. awesome-adb is a command reference, while those tools cover other workflows such as screen mirroring or emulation.
New agent skills, repos and AI tools — every week
The best new skills and open-source projects, the fastest-growing repos, and one free prompt. Five minutes to read. Unsubscribe anytime.
Our verdict
awesome-adb suits Android developers, testers and hobbyists who want a quick, copyable reference of ADB commands, and Chinese-speaking readers will find it easiest to use. It is not a good fit if you need an English guide, a graphical tool, or guaranteed results on every phone, since command support varies by Android version and ROM.
Install options & downloads