An adb device not found error (current ADB versions print adb: no devices/emulators found) means the ADB program on your computer cannot see any phone that is ready to take commands. If your phone shows up but is marked unauthorized, the phone is connected but has not approved your computer yet. Run adb devices first: the word next to your phone tells you which fix below you need.

What adb devices Is Telling You

Open a Command Prompt or Terminal in your Platform-Tools folder and run:

adb devices -l

This only lists connected devices. It does not change anything on the phone. Match the result to this table:

What you see What it means Where to start
Empty list, or adb: no devices/emulators found ADB cannot see any phone at all Quick checks, then Fixes 1, 5, 6 and 7
unauthorized The phone has not accepted your computer’s RSA key Fixes 2, 3 and 4
offline Google: the device “is not connected to adb or is not responding” Fix 1
no permissions (Linux only) Your Linux user cannot open the USB device Fix 8
adb: more than one device/emulator Two or more devices are connected and ADB does not know which one to use Fix 9
device ADB is connected and working Nothing to fix

On an unauthorized phone, ADB commands fail with a message ending “Otherwise check for a confirmation dialog on your device.” Look at the phone screen.

Quick Checks

  • Is the phone booted into Android? In fastboot (bootloader) mode the phone talks to fastboot, not ADB. Our fastboot commands list covers that mode.
  • Is USB debugging on? Open Settings > About phone and tap Build number seven times until you see “You are now a developer!”. On Samsung Galaxy phones, Build number is under Settings > About phone > Software information. Then turn on USB debugging in Developer options.
  • Is the phone unlocked? The approval prompt needs an unlocked screen.
  • Is it a data cable? Google warns that not all USB cables can transfer files. Try a second cable and a different USB port on the computer.
  • Is your ADB up to date? Run adb version. The newest stable Platform-Tools release is 37.0.1 (July 2026); 37.0.3 is still a Canary build. Version 36.0.2 fixed a bug where Samsung devices were not properly detected, so very old copies are worth replacing. Download it from Google’s SDK Platform-Tools page.

Step-by-Step Fixes

These fixes are ordered from the quickest to the most involved. None of them erases data on your phone.

Fix 1: Restart the ADB Server

The ADB server runs in the background on your computer. Restarting it makes ADB scan for devices again. These commands only restart the program on your PC:

adb kill-server
adb start-server
adb devices

If your phone shows offline or unauthorized, you can also try adb reconnect offline. The ADB manual describes it as resetting offline and unauthorized devices to force a reconnect.

Fix 2: Approve the USB Debugging Prompt

  1. Unplug the cable and unlock the phone.
  2. Plug the cable back in and watch the screen. You should see Allow USB debugging? with your computer’s RSA key fingerprint.
  3. If this is your own computer, tick Always allow from this computer.
  4. Tap Allow, then run adb devices again. The state should now be device.

If no prompt appears, turn USB debugging off and on again, then reconnect the cable with the screen unlocked.

Fix 3: Revoke Old Authorizations and Approve Again

A stored key can go stale. Since Android 10, the phone automatically revokes the approval of a computer that has not reconnected within 7 days. To start fresh:

  1. Open Developer options and tap Revoke USB debugging authorizations. Confirm the message. This removes access for every computer you approved before.
  2. Run adb kill-server on the PC.
  3. Reconnect the phone and approve the prompt as in Fix 2.

Android 11 and newer also offer Disable adb authorization timeout, which stops the 7-day revocation. The timeout protects you, so only use it on your own computer.

Fix 4: Reset the Computer’s ADB Key (Advanced)

ADB keeps your computer’s key pair as adbkey and adbkey.pub in the .android folder of your user folder. If they are damaged, approval never sticks. When the key is missing, ADB creates a new pair at the next start, so renaming the old files is enough. On Windows:

adb kill-server
ren "%USERPROFILE%\.android\adbkey" adbkey.old
ren "%USERPROFILE%\.android\adbkey.pub" adbkey.pub.old
adb start-server

On macOS or Linux, rename the same two files in ~/.android with mv. After this, every phone you use with this computer must approve it again.

Fix 5: Install or Repair the Windows USB Driver

Only Windows needs a USB driver for ADB. Open Device Manager with the phone connected. A yellow warning icon under Other devices or Portable Devices means the ADB driver is missing. Pixel phones use the Google USB Driver; other brands use the maker’s own driver. Our Android USB driver for Windows 11 guide lists the official driver for each brand and explains Device Manager errors such as Code 28 and Code 43.

Also try switching the USB mode to File transfer in the USB notification. Google notes that the USB configuration decides how the computer identifies the phone.

Fix 6: Remove Duplicate Copies of ADB

Some phone suites, flashing tools and old “ADB installer” packages ship their own adb.exe. Google notes that all ADB clients use TCP port 5037, so a different copy can end up restarting the server. The sign is a message like this:

adb server version (40) doesn't match this client (41); killing...

The numbers on your PC may be different. To see every adb.exe that Windows finds on your PATH, run:

where adb

Close the other tools and keep only Google’s latest Platform-Tools on your PATH.

Fix 7: Check Auto Blocker on Samsung Galaxy Phones

Samsung’s Auto Blocker includes “Blocks commands by USB cable”, and Samsung says it is on by default on Galaxy devices released with One UI 6.1.1. Owners in Samsung’s community have reported USB debugging greyed out until they turned Auto Blocker off. Check Settings > Security and privacy > Auto Blocker. If you turn it off for ADB work, turn it back on when you finish.

Fix 8: Fix “no permissions” on Linux

Google’s setup steps for Ubuntu need two things. First, add your user to the plugdev group, then log out and back in. Check the result with id:

sudo usermod -aG plugdev $LOGNAME

Second, install the community-maintained udev rules for Android devices:

sudo apt-get install android-sdk-platform-tools-common

Fix 9: Pick One Device When Several Are Connected

Run adb devices -l to see each serial number, then add -s to your command. Use -d when only one device is connected by USB:

adb -s SERIAL_NUMBER shell
adb -d shell

Replace SERIAL_NUMBER with the serial shown in the list.

Fix 10: Try Wireless Debugging Instead

Android 11 and newer can use ADB over Wi-Fi, which skips the cable and driver. With the phone and computer on the same Wi-Fi, open Developer options > Wireless debugging, allow it, and tap Pair using pairing code. Run this with the IP address and port shown, then enter the code:

adb pair IP_ADDRESS:PORT

You pair only once. With Android 17 and ADB 37.0.0 or newer, Google says the phone reconnects automatically on a trusted network.

When It Is a Hardware Problem

  • Not detected on any computer. If neither file transfer nor ADB works on two computers with two good data cables, suspect the phone’s USB port. Google’s test is to try the phone on another computer and another device on the same port.
  • Wireless debugging works but USB does not. That points to the cable or the USB port, not your settings.
  • Loose or damaged port. Visit an authorized service centre for your brand.
  • Broken screen. Google explains that ADB cannot run unless you unlock the phone and accept the prompt. If this computer was never approved, repair the screen first.

Related Guides

FAQ

Why does ADB still say unauthorized after I tapped Allow?

The ADB server may still be holding the old connection state. Run adb kill-server, revoke USB debugging authorizations on the phone, reconnect and approve again. If that fails, reset the computer’s ADB key as in Fix 4.

Do I need a USB driver for ADB on a Mac or Linux PC?

No. Google says macOS, Linux and ChromeOS need no USB driver. On Ubuntu Linux you may need the plugdev group and udev rules from Fix 8.

Why does adb devices show nothing when my phone is in fastboot mode?

Fastboot mode is a bootloader mode that works with the fastboot tool, not ADB. Run fastboot devices instead, or restart the phone into Android to use ADB.

Will any of these fixes erase my phone?

No. Restarting the server, revoking authorizations, resetting the computer’s key and changing drivers do not touch your photos, apps or files. You only need to approve the computer again.

https://droid-developers.com/wp-content/uploads/2026/11/adb-device-not-found-unauthorized-fix-featured-1024x538.jpghttps://droid-developers.com/wp-content/uploads/2026/11/adb-device-not-found-unauthorized-fix-featured-150x150.jpgFahim MahmudDriverHelp & TroubleshootingHow ToAn adb device not found error (current ADB versions print adb: no devices/emulators found) means the ADB program on your computer cannot see any phone that is ready to take commands. If your phone shows up but is marked unauthorized, the phone is connected but has not approved your...Android Help,Troubleshooting  & Stock Rom