Error Code: error: device not found / no devices/emulators found

How to Fix "error: device not found" in ADB

Diagnose and resolve cases where ADB cannot detect or communicate with your connected Android hardware.

Common Symptoms

  • `adb devices` returns an empty "List of devices attached"
  • Device charges over USB but computer fails to register connection
  • WebUSB browser dialog shows "No compatible devices found"

Root Causes

  • USB Debugging is turned OFF in Developer Options on Android
  • Faulty or power-only USB cable (lacks data wiring)
  • Missing Windows OEM / Google USB drivers (WinUSB / ADB Interface)
  • Conflicting background ADB server instance or port 5037 collision
  • Missing udev permission rules on Linux distributions

Proven Solutions

Solution 1: Restart ADB Daemon & Reconnect USB Cable

Kills hanging server instances and forces fresh USB enumeration.

  1. Run `adb kill-server`
  2. Unplug the USB cable from phone and computer
  3. Plug cable into a direct motherboard USB port (avoid USB hubs)
  4. Run `adb devices`
adb kill-server
adb start-server
adb devices

Solution 2: Change USB Mode to File Transfer (MTP)

Many phones disable ADB when locked in "Charge Only" mode.

  1. Unlock your Android phone screen
  2. Pull down the notification shade
  3. Tap "Charging this device via USB"
  4. Select "File Transfer / Android Auto" (MTP)

Solution 3: Install Windows Google USB Driver

Ensure Windows recognizes the device as an Android Composite ADB Interface.

  1. Open Windows Device Manager
  2. Look for your phone under "Other devices" or "Portable Devices" with a yellow exclamation mark
  3. Right click > Update driver > Browse my computer for drivers
  4. Select the official Google USB Driver or use Windows Update Optional Updates