How to Fix ADB Cannot Connect To Daemon

Are you stepping into Android custom development but can’t get past the “cannot connect to daemon” error? Look no further. In this guide, we will outline several ways to fix the ADB cannot connect to daemon error.


ADB and fastboot commands are super useful when you try to connect your phone to a computer via ADB (Android Debug Bridge). You will need to use ADB commands when trying to install a custom ROM, boot your device to custom recovery, or root your Android phone. You could also remove bloatware (unnecessary apps) from your smartphone.

ADB commands have a lot of perks associated with them, but only when you can get past the “cannot connect to daemon” error.

The “cannot connect to daemon” error typically means that there’s some issue with the connection between your computer and the Android phone. Or, something is wrong with ADB services. While all this may sound too complicated (if you have just stepped inside the world of custom development), troubleshooting this error is easy.

Below, we have jotted down the effective ways of troubleshooting ADB cannot connect to daemon error. In most cases, the error has disappeared after restarting the ADB server (more on this in solution #1). However, if the problem persists, you would want to try other fixes as well.


During the process, your personal data on your phone (music, photos, videos, documents, etc) may get deleted. Hence, take a complete backup of your phone to avoid any data loss. You can either transfer your data to a PC or use cloud backup solutions such as IDrive, Google Drive, or BLACK BLAZE.

Here’s How to Fix ADB Cannot Connect to Daemon Error

1. Restart the ADB Server

As of now, the best workaround that is selling out success for most users involves restarting the ADB server.

Here are the steps to follow:

1. Make sure your computer has the original Android SDK Platform Tool. You can check out our guide on how to install Android SDK Platform Tools on your computer.

2. Extracting the Android SDK Platform Tools gives you a “platform-tools” folder.

3. In the Windows search box at the bottom, type “task manager” and press the “Enter” button. This should open the Task Manager window.

4. Right-click on “adb” and select “End task”. If you can’t find it, skip to the next step.

5. Open the “platform-tools” folder, type “CMD” in the address bar, and hit “Enter”.

6. You should see the “Command Prompt” on your screen.

7. Run the following command to kill the ADB server

adb kill-server

8. Now, execute the following command to restart the ADB server:

adb start-server

To verify if the error is fixed, connect your phone to the computer via a USB cable and run the command which was previously giving the “cannot connect to daemon” error.

2. Check Your USB Connection

If the above solution did not work, make sure your Android smartphone is properly connected to your computer via a USB cable. Gently push both ends of the USB cable to make sure the connection is not loose.

Further, you need to check if the USB cable or USB port is damaged. To check if the USB port is damaged, use a different port and run the command to check if the error message appears.

If the problem persists, try changing the USB cable as well. When getting such errors, changing the USB cable often does the trick. Get a high-quality USB cable and verify the problem.

3. Make Sure USB Debugging is Enabled

To run the ADB commands, it is required to enable USB debugging on your Android phone. It is located within the “Developer options”. If you can’t find Developer options within the Settings app, go to Settings > About phone section, and tap 7 times on the build version. It will enable Developer options.

Now, go to the Developer options, and check if USB Debugging is turned off. If yes, turn it on. Check if the problem is fixed.

If you have connected your Android device for the first time to the computer for ADB purposes, you’ll need to authorize the computer. This option should pop up as soon as you connect your phone to the computer via a USB cable and enable USB debugging.

4. Disable Firewall and Antivirus

A firewall or antivirus could be blocking the ADB connection. When there’s a problem with the ADB connection, you are likely to see a “cannot connect to daemon” error. To check if the firewall or antivirus is causing the problem, disable them temporarily.

Follow these steps to disable Windows Firewall:

  1. Type “Windows Security” in the search box at the bottom and hit “Enter”.
  2. Tap on “Firewall & network projection” from the left panel.
  3. Click “Domain network” and toggle off “Microsoft Defender Firewall”.
  4. Now, go back to the previous screen and click “Private network”.
  5. Turn off the “Microsoft Defender Firewall” for this as well.
  6. Do the same for “Public network”.

Now, connect your phone to the computer via a USB cable and run the command to check if the problem is fixed.


Do not forget to enable the firewall for the Domain network, Private network, and Public network. It will strengthen your device’s security. Also, if you disabled any antivirus software, turn them on.

If the error still shows up on your screen, disable all antivirus software on your PC and then verify the problem.

We hope this guide was helpful to you. Which one of the aforementioned solutions fixed the ADB cannot connect to daemon error on your computer? Share your valuable thoughts in the comments below.

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.