Skip to main content

ADB Frequently Asked Questions

Navigation bar

Common questions about ADB:


Basic Questions​


Common Issue: ADB Crashes​

Crash

Crash

Incorrect Usage:​

Directly entering adb shell in the Win + R run dialog. If the device is not properly connected via USB, you won't enter the ADB shell. Windows will directly close the cmd window, making it impossible to diagnose the device status.

This is normal behavior in Windows.

Correct Usage​

First, enter cmd in the Win + R run dialog. Then, execute adb shell. This allows you to see error messages for further troubleshooting.

If the device is not properly connected and recognized, you will see:

adb.exe: no devices/emulators found

After successful recognition:

C:\Users\admin>adb devices
List of devices attached
a56d31dfb177858c device


C:\Users\admin>adb shell

Common Issue: ADB Not Working​

When multiple ADB instances might exist on the system, they can conflict, resulting in errors like:

error:cannot connect to daemon

You can resolve this by executing adb kill-server:

adb kill-server

# Should work normally now
C:\Users\admin>adb devices
List of devices attached
a56d31dfb177858c device

Image


AI Translation Notice

This page was translated into English by AI and is provided for reference only. The original document is written in Chinese. If there is any discrepancy, the Chinese version prevails.

本页英文内容由 AI 自动翻译生成,仅供参考;原文为中文,如有差异请以中文原文为准。

查看中文原文 / View the Chinese original →