ADB Error: Device Not Found – Complete Solution Guide

What the 'device not found' Error Means

The 'device not found' error in Android Debug Bridge (ADB) indicates that the tool cannot detect a connected Android device. This message appears when running commands like adb devices, where your device is missing from the list or the list is empty.

Such an error blocks the ability to interact with the device via ADB, which is critical for developers, testers, and enthusiasts using ADB to install apps, debug, or manage files.

Common Causes

Below are the most frequent reasons why ADB fails to see a device:

1. Faulty or non-data USB cable – many cables are charge-only and lack data lines. The cable may also be physically damaged.
2. USB debugging disabled – without the USB debugging option enabled in Developer Options, the device will not be accessible to ADB.
3. Missing or outdated ADB drivers – on Windows, specific drivers for the device manufacturer are required. Without them, the system does not recognize the device as a debug device.
4. Unauthorized device – on Android 4.2+, you must authorize the computer upon first connection. If this is not done, the device may appear as 'unauthorized' or not appear at all.
5. Incorrect USB mode – if the device is connected in "Charge only" mode, ADB cannot interact with it. MTP or PTP mode is needed.
6. USB port issues – the port on the computer may not provide sufficient power or may be faulty.
7. Conflict with other software – synchronization programs (Samsung Smart Switch, HTC Sync) can take control of the device, interfering with ADB.
8. Stuck ADB server – sometimes the ADB process can hang and needs to be restarted.

Solutions

Solution 1: Check USB Cable and Port

Start simple: ensure you are using a cable that supports data transfer (not just charging). Try replacing the cable with a known working one. Connect the device directly to the computer, bypassing USB hubs, as they can limit bandwidth or power.

Check if the device is detected by the system: on Windows in Device Manager, on macOS/Linux via lsusb (Linux) or System Information (macOS). If the device appears as unknown or with an error, the problem is likely driver-related.

Solution 2: Enable USB Debugging

USB debugging is a mandatory option for ADB work. To enable it:

1. On the device, go to Settings → About Phone.
2. Find Build Number and tap it 7 times until the message "You are now a developer" appears.
3. Go back to the main Settings menu and find Developer Options (or "For developers").
4. Toggle USB debugging on.
5. When connecting the device to the computer via USB, a dialog will appear requesting debugging permission. Tap Allow and check Always allow from this computer.

After this, run adb devices – the device should appear.

Solution 3: Install or Update ADB Drivers (Windows)

On Windows, drivers are often the main cause of the problem.

Solution 3.1: Install via SDK Manager

If you have Android Studio installed:

• Open SDK Manager (File → Settings → Appearance & Behavior → System Settings → Android SDK → SDK Tools).
• Ensure the Android SDK Platform-Tools package (contains ADB) and Google USB Driver are installed.
• Click Apply to install or update.

Solution 3.2: Manual Driver Installation

1. Download drivers for your device from the manufacturer's official website (Samsung, Huawei, Xiaomi, etc.) or use the generic drivers from Google USB Driver.
2. Connect the device to the computer.
3. Open Device Manager (Win + X → Device Manager).
4. Find the device with a yellow exclamation mark (usually under "Other devices" or "Portable Devices").
5. Right-click → Update driver → Browse my computer for drivers → Let me pick from a list of available drivers.
6. Point to the folder with the drivers (e.g., extras\google\usb_driver from the Android SDK folder).
7. Complete the installation and restart the computer.

After installing drivers, reconnect the device and check adb devices.

Solution 4: Authorize the Device

On Android 4.2+, every computer must be authorized. If you missed the dialog or clicked "Cancel", the device will not be accessible.

To fix this:

• Toggle USB debugging off and on in Developer Options.
• Reboot the device.
• When the dialog appears on the device, be sure to tap Allow.
• If the dialog does not appear, try changing the USB port or cable, as this sometimes affects detection.

You can also reset ADB authorization: in Developer Options on the device, find Revoke USB debugging authorizations (or "Reset USB debugging authorization") and enable it. Then reconnect and confirm again.

Solution 5: Restart ADB Server

The ADB server may be malfunctioning. Run in the command line or terminal:

adb kill-server
adb start-server

After starting the server, check devices:

adb devices

If the device is connected and authorized, it will appear in the list.

Solution 6: Change USB Mode

Some devices default to "Charge only" mode. Change the mode:

1. Connect the device to the computer via USB.
2. Pull down the notification shade on the device.
3. Tap the USB notification (e.g., "USB charging").
4. Select File Transfer (MTP) or PTP (depending on the device).
5. Check adb devices again.

On some devices (e.g., Samsung), you also need to enable the "USB debugging" option in Developer Options, even if USB debugging is already on.

After applying each solution, check the device list with adb devices. If the problem persists, move to the next solution.

Prevention

To avoid encountering the "device not found" error again:

• Use a high-quality USB cable that supports data. Avoid cheap charge-only cables.
• Always authorize when connecting the device to a new computer for the first time.
• Regularly update Android SDK Platform-Tools to the latest version for current drivers and fixes.
• On Windows, install drivers from the device manufacturer if standard ones fail. Manufacturers like Samsung, Xiaomi often provide specific ADB drivers.
• Do not run conflicting software simultaneously (Samsung Kies, HTC Sync, Mi PC Suite). Close them when using ADB.
• Check the USB mode – ensure MTP or PTP is selected when connecting, not "Charge only".

Following these guidelines will minimize the chances of facing device detection issues with ADB.