adb: no devices/emulators found / error: device not found
adb can’t see any connected device or running emulator.
Seen on:
Android
Meaning
USB debugging off, a charge-only cable, missing Windows USB drivers, the phone in “charging only” mode, or the emulator not started yet.
Common causes
- USB debugging disabled
- Charge-only cable or USB mode
- Missing OEM USB driver (Windows)
- Emulator not running
- Multiple adb versions fighting
⚡ Quick fix
- Enable Developer options → USB debugging
- Use a data cable; choose File transfer mode
- Install the Google USB driver / OEM driver on Windows
Detailed fix by platform
ADB
- kotlin
adb devices -l adb kill-server && adb start-server
How to diagnose
- List — adb devices
- USB — Device appears in OS device list?
- Emulator — Running?
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
- ActivityNotFoundException ActivityNotFoundException: Unable to find explicit activity class; have you declared this activity in your AndroidManifest.xml?
- adb server version doesn't match adb server version (41) doesn't match this client (39); killing...
- adb unauthorized adb: device unauthorized. This adb server's $ADB_VENDOR_KEYS is not set
Most viewed in Android
Other ways to find it
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
Was this page helpful?
Report a correction or suggest an improvement
Last updated 7 Oct 2026