ADB Not Responding: Causes and Fixes for the Error

What the "ADB not responding" Error Means

The "ADB not responding" error occurs when Android Debug Bridge (ADB) stops reacting to commands. This typically manifests when running commands in the terminal, such as adb devices, adb shell, or others: the command hangs, returns no result, or outputs an error message. ADB is a tool for debugging and managing Android devices from a computer, and if it's not working, you won't be able to install apps, retrieve logs, or interact with the device via the command line.

Common Causes

A non-responsive ADB can be triggered by several specific issues:

1. Stuck or crashed ADB server – ADB runs as a server (background process), and occasionally it can freeze due to code errors or conflicts with other processes.
2. Device not connected or USB debugging disabled – if the USB cable doesn't support data transfer, the device isn't authorized, or the "USB debugging" option is turned off, ADB cannot establish a connection.
3. Corrupted or outdated USB drivers (on Windows) – on Windows, ADB requires specific drivers. If they are outdated, corrupted, or conflict with other drivers, ADB fails to communicate with the device.
4. Port 5037 conflict – ADB defaults to port 5037. If another application (e.g., another ADB instance or a program using the same port) occupies it, ADB cannot start.
5. Incorrect PATH environment variable settings – if the path to the platform-tools folder (where adb.exe or adb resides) isn't added to PATH, the system may not find the executable, or an incorrect version might be used.
6. Blocking by antivirus or firewall – some antivirus programs and system firewalls may mistakenly identify ADB as malicious and block its network or device access.
7. Corrupted Android SDK Platform-Tools files – if files in the platform-tools folder were damaged during download or update, ADB may malfunction.

Solutions

Method 1: Restart the ADB Server

This is the simplest and often most effective method. Restarting the ADB server clears stuck processes and re-establishes the connection.

1. Open a terminal (Command Prompt, PowerShell on Windows; Terminal on macOS/Linux).
2. Run the command to stop the server:

   adb kill-server
   

3. Then start the server again:

   adb start-server
   

4. After seeing "daemon started successfully", check if ADB works:

   adb devices
   

If the issue was a stuck server, it should now be resolved.

Method 2: Verify Device Connection

Ensure both physical and software-level device connectivity is correct.

1. Connect your Android device to the computer using a USB cable that supports data transfer (not just charging).
2. On the device, enable USB debugging: Settings → Developer options (if not visible, tap "Build number" in "About phone" 7 times) → USB debugging.
3. On first connection, an authorization prompt will appear on the device – confirm it.
4. In the terminal, run:

   adb devices
   

   • If the device appears as device – connection is established.
   • If offline – try reconnecting the cable, rebooting the device, or restarting the computer.
   • If the device isn't listed – check the cable, USB port, and drivers (see Method 3).

Method 3: Update USB Drivers (for Windows)

On Windows, ADB drivers frequently cause issues, especially after system or Android Studio updates.

1. Open Device Manager (Win + X → Device Manager).
2. Locate your device:
   • Usually under "Portable Devices" or "Other devices".
   • May appear as "Android" or with a yellow exclamation mark.
3. Right-click the device → "Update driver".
4. Select "Browse my computer for drivers".
5. Point to your Android SDK's platform-tools folder. Typically:

   C:\Users\Имя_пользователя\AppData\Local\Android\Sdk\platform-tools
   

   Or, if installed via Android Studio, locate it through SDK Manager.
6. If drivers fail to install, download ADB drivers from your device manufacturer's website (e.g., Samsung, Xiaomi) or use Google's universal driver (included in Platform-Tools).
7. After installation, restart the computer and check adb devices.

Method 4: Check and Configure the PATH Environment Variable

If ADB isn't found system-wide or the wrong version is used, it can cause hangs.

Check current PATH:

• Windows (Command Prompt or PowerShell):

  echo %PATH%
  

• macOS/Linux (Terminal):

  echo $PATH
  

  Look for the path to platform-tools (e.g., C:\...\Sdk\platform-tools or /Users/.../Library/Android/sdk/platform-tools) in the output.

Add to PATH (if missing):

• Windows:
  1. Open Control Panel → System → Advanced system settings → Environment Variables.
  2. Under "System variables", find Path, select "Edit".
  3. Click "New" and add the full path to the platform-tools folder.
  4. Click OK and restart all open terminals.
• macOS/Linux:
  1. Open ~/.bashrc, ~/.zshrc, or ~/.profile in a text editor.
  2. Add a line (replace /path/to with your actual path):

     export PATH=$PATH:/path/to/android-sdk/platform-tools
     

  3. Save the file and run:

     source ~/.bashrc  # or source ~/.zshrc
     

  4. Or simply restart the terminal.

After configuring PATH, verify which ADB version is in use:

adb version

Ensure it's the expected version (e.g., 1.0.41 or higher).

Method 5: Temporarily Disable Antivirus and Firewall

Antivirus software and system firewalls may block ADB, especially if it's unsigned or uses network ports.

1. Temporarily disable your antivirus (e.g., Windows Defender, Avast, Kaspersky) and Windows Firewall.
   • For Windows Defender: Windows Settings → Update & Security → Windows Security → Virus & threat protection → Manage settings → turn off real-time protection.
   • For Firewall: Control Panel → Windows Defender Firewall → Turn Windows Firewall on or off.
2. Try running the ADB command again (e.g., adb devices).
3. If the problem disappears, the antivirus/firewall was the culprit.
4. Configure exceptions:
   • In your antivirus, add the platform-tools folder (e.g., C:\Users\Имя\AppData\Local\Android\Sdk\platform-tools) to exclusions.
   • Also add an exclusion for the adb.exe (Windows) or adb (macOS/Linux) executable.
   • In the firewall, allow inbound/outbound connections for adb.exe.
5. Re-enable your antivirus and firewall.

Method 6: Reinstall Android SDK Platform-Tools

If ADB files are corrupted or outdated, reinstalling Platform-Tools often fixes the issue.

1. Download the latest version of Android SDK Platform-Tools from the official site: developer.android.com/studio/releases/platform-tools.
2. Extract the archive to a temporary folder.
3. Replace the platform-tools folder in your Android SDK:
   • Default path on Windows: C:\Users\Имя\AppData\Local\Android\Sdk\platform-tools
   • On macOS: /Users/Имя/Library/Android/sdk/platform-tools
   • On Linux: /home/Имя/Android/Sdk/platform-tools or /usr/lib/android-sdk/platform-tools Delete the old platform-tools folder and copy the new one from the archive.
4. Alternatively, if you use Android Studio:
   • Open Android Studio → SDK Manager (icon in top-right or File → Settings → Appearance & Behavior → System Settings → Android SDK).
   • Go to the SDK Tools tab.
   • Uncheck "Android SDK Platform-Tools", click Apply → OK to uninstall.
   • Then re-check the box and click Apply to reinstall.
5. After installation, restart your computer and test ADB:

   adb version
   adb devices
   

Prevention

To minimize the risk of the "ADB not responding" error recurring, follow these best practices:

• Regularly update Android SDK Platform-Tools via SDK Manager or the official site. New versions often include stability fixes.
• Use high-quality USB cables and ports – cheap cables may support charging only, not data. Connect directly to the computer, avoiding USB hubs.
• Avoid port conflicts – if you have multiple development tools installed (e.g., Genymotion, BlueStacks), they may use port 5037. If needed, change ADB's port with adb -P 5038 start-server and configure other tools to use the new port.
• Add ADB exceptions in antivirus and firewall immediately after installation to prevent blocking.
• Monitor the PATH environment variable – ensure only one version of platform-tools is in PATH to avoid version conflicts.
• Periodically verify SDK file integrity – especially after Android Studio or other tool updates. If strange errors arise, reinstall Platform-Tools.