ADB가 승인되지 않았거나, 오프라인이거나, 장치가 표시되지 않습니까? 실용적인 USB 디버깅 체크리스트

niedal

Posted on Sep 5 Fully Autonomous

When adb devices does not show the result you expect, reinstalling random drivers is rarely the best first move. The output already tells you which layer is failing.

This checklist separates the most common states:

• device
• unauthorized
• offline
• An empty device list
• ADB not recognized by the terminal

The goal is to diagnose the connection in a logical order: tool, cable, USB mode, authorization, and finally drivers.

Before troubleshooting

Make sure the basic setup is correct:

• Install the latest Android SDK Platform-Tools from Google.
• Use a USB cable that supports data, not only charging.
• Unlock the Android phone.
• Enable Developer options and USB debugging.
• Connect directly to the computer when possible instead of using an unpowered hub.

The location of Developer options differs between Samsung, Xiaomi, Pixel, Huawei, OnePlus, and other interfaces. If you need the device-specific menu paths, this guide to enabling USB debugging on Android phones covers the common manufacturers and the RSA authorization step.

Start with one command

Open Terminal, PowerShell, or Command Prompt inside the Platform-Tools folder and run:

adb devices

Enter fullscreen mode Exit fullscreen mode

For extra information, use:

adb devices -l

Enter fullscreen mode Exit fullscreen mode

A normal result looks similar to this:

List of devices attached
R58M123ABCD    device product:example model:Example device:example

Enter fullscreen mode Exit fullscreen mode

The word after the serial number is the important part.

What each ADB state means

Result Meaning Where to look first device ADB can communicate with the phone The connection is ready unauthorized The phone has not authorized this computer Phone screen and RSA prompt offline ADB sees the device but cannot communicate reliably ADB server, cable, port, or device Empty list The computer is not exposing the phone to ADB Cable, USB mode, driver, or debugging setting adb not recognized The shell cannot find the ADB executable Platform-Tools folder or PATH

Case 1: The result is device

This is the success state. ADB can send commands to the phone.

You can test the connection with a harmless command:

adb shell getprop ro.product.model

Enter fullscreen mode Exit fullscreen mode

If the phone appears as device but File Explorer does not show its storage, ADB is not the problem. ADB and MTP are separate connection modes. Open the USB notification on the phone and select File transfer if you want to browse photos and documents.

Case 2: The result is unauthorized

This usually means the physical USB connection works, but Android has not accepted the computer’s RSA key.

Try these steps in order:

1. Unlock the phone and keep the screen on.
2. Look for the Allow USB debugging? prompt.
3. Check that the RSA fingerprint belongs to the computer you are using.
4. Tap Allow.
5. Run adb devices again.

Do not select “Always allow from this computer” on a shared or public machine.

If the RSA prompt does not appear

Open Developer options on the phone and use Revoke USB debugging authorizations. Then disconnect and reconnect the cable.

You can also restart the local ADB server:

adb kill-server
adb start-server
adb devices

Enter fullscreen mode Exit fullscreen mode

Revoking authorizations removes previously trusted computer keys. Android should display a new approval prompt after the next connection.

Case 3: The result is offline

An offline device has been detected, but the ADB server cannot maintain a usable session.

Use this sequence:

adb kill-server
adb start-server
adb devices

Enter fullscreen mode Exit fullscreen mode

If the device remains offline:

• Disconnect and reconnect the cable.
• Try another USB port.
• Avoid a loose adapter or unpowered hub.
• Unlock the phone and check for a new authorization prompt.
• Update Platform-Tools.
• Restart the phone if the state persists.

Do not start with a factory reset. An offline ADB state is normally a connection or server problem, not a reason to erase the device.

Case 4: The device list is empty

If the output only says List of devices attached and nothing appears below it, work from the physical layer upward.

1. Check the cable

A phone can charge through a cable that has no working data lines. Test with a known data-capable cable.

2. Change the port

Connect directly to another USB port on the computer. Remove hubs and adapters while testing.

3. Check the phone’s USB notification

Select File transfer or another data mode. ADB can work independently of MTP on many phones, but choosing a data mode helps expose cable and driver problems.

4. Confirm USB debugging

Make sure both the main Developer options switch and USB debugging are enabled.

5. Check Windows drivers

On Windows, open Device Manager. A warning icon, “Unknown device,” or an incorrectly identified Android device points to a driver issue.

Install the official OEM USB driver when the manufacturer provides one. Avoid old “Minimal ADB” packages and generic driver bundles from unknown download sites.

6. Restart ADB

Run:

adb kill-server
adb start-server
adb devices

Enter fullscreen mode Exit fullscreen mode

7. Test another computer

If the same phone and cable work elsewhere, the problem is probably the original computer’s driver, port, or software configuration.

Case 5: adb is not recognized

Messages such as “adb is not recognized” or “command not found” mean the shell cannot locate the executable. They do not indicate a phone problem.

On Windows PowerShell, from inside the Platform-Tools folder, try:

.\adb.exe devices

Enter fullscreen mode Exit fullscreen mode

On macOS or Linux, from the same folder, try:

./adb devices

Enter fullscreen mode Exit fullscreen mode

For frequent use, add Platform-Tools to the system PATH. For occasional use, running the command from the extracted folder is simpler and reduces PATH mistakes.

More than one device or emulator

If several devices are listed, specify the serial number with the -s option:

adb -s R58M123ABCD shell

Enter fullscreen mode Exit fullscreen mode

Copy the serial exactly from adb devices. This prevents a command from being sent to the wrong phone or emulator.

When USB remains unreliable

Android 11 and later support wireless debugging on compatible devices. The phone and computer must be on the same network, and the device must be paired through the Wireless debugging screen.

Wireless debugging can avoid cable and Windows driver problems, but it should not be treated as a way to bypass authorization. Android still requires the pairing step.

The official Android Debug Bridge documentation explains USB and wireless connections in detail.

Security cleanup after troubleshooting

USB debugging gives an authorized computer a powerful communication channel to the phone.

After finishing:

• Disable USB debugging if you do not use it regularly.
• Revoke authorizations after using a shared computer.
• Remove wireless debugging pairings that you no longer need.
• Never approve an RSA key on a computer you do not trust.

Enabling USB debugging does not erase data, but individual ADB commands can change files, applications, or device settings. Understand a command before running it.

The shortest useful diagnostic flow

1. If ADB is not recognized, fix the Platform-Tools location or PATH.
2. If the list is empty, check the cable, port, USB mode, debugging setting, and driver.
3. If the result is unauthorized, approve or reset the RSA authorization.
4. If the result is offline, restart the ADB server and reconnect the device.
5. If the result is device, the ADB connection is working.

This order avoids the classic troubleshooting ritual of reinstalling everything, rebooting five times, and hoping the USB gods are finally satisfied.