Waiting for Device Error in ADB or Fastboot Commands, How to Fix?

Being open-source in nature, Android OS offers an insane level of customizations. You can literally redesign your phone and add new features by installing a new custom ROM. Moreover, to take the customization onto a new level you can root your phone to overclock the processor speed or add advanced features. In between the process, you’ll need to use the command prompt to perform various operations that’s where many people get stuck. The most common error message is “Waiting for Device” which you’ll have to fix to reach the next step. In this article, we’ll be going through various methods to fix the “waiting for device” error in ADB or fastboot commands.

Be it flashing custom ROMs via custom recoveries such as TWRP or rooting the device via Magisk, you’ll have to use ADB commands. And if you’re getting the waiting for device error, don’t worry, there are proven ways to fix it. The error message appears when your PC is failing to detect your smartphone connected through Android Debug Bridge (ADB). This could happen due to various regions. Some of the most common reasons include not using USB 2.0 ports, USB Debugging is not turned on, and driver issues. If you are aware of the problem, navigate to the particular section otherwise go through each solution step-by-step to fix the issue.

Waiting for Device Error in ADB or Fastboot Commands

How to Fix Waiting for Device Error in ADB or Fastboot Commands

After trying out every solution, run the command where you get the waiting for device error to check if the problem is fixed. If not, move on to the next solution and see which one does the trick for you.

Solution 1: Use USB 2.0 Ports

It might sound strange to you but the USB 3.0 ports, as reported by many users, is the real culprit when performing ADB commands. Leave other users, my IdeaPad 5 which has two USB 3.0 ports also throws the same error. So, if your PC has a USB 2.0 port, use that while performing ADB commands. In my case, there’s no USB 2.0 port on my laptop, so I ended up purchasing a USB 2.0 hub and the problem got rid of that error message.

Solution 2: Make Sure USB Debugging is Enabled

If the USB Debugging is disabled on your phone, you won’t be able to run ADB or fastboot commands from your computer. Enabling this option is important in order for your computer to recognize the phone in ADB mode. By default, USB Debugging is disabled on your phone. You’ll need to manually enable the option before running any commands.

Advertisements

You can find the USB Debugging option under the Settings app. After opening the Settings app, find the Developer settings and turn on USB Debugging. If you don’t see Developer settings, tap 7 times on the build number to activate it.

Solution 3: Install Android SDK Platform-Tools From Original Source

If you are using the minimal ADB & Fastboot installer and getting waiting for the device error message, you should use the original version of Android SDK Platform tools. By using the official Platform-tools, you can be sure it is not infected with any malware or virus.

After downloading the Android SDK Platform tools on your computer, use the following steps to run ADB or fastboot commands:

Advertisements
  1. Open the Platform-tools folder.
  2. type cmd in the address bar and press Enter.
  3. The command prompt window will open. Now, you can run commands.

On the command prompt window, run the commands and check if the issue is solved. If you still get the same error message, apply the next solution.

Solution 4: Use Another USB Cable

The USB cable you use to connect your phone to the PC might be defective. To eliminate this possibility, use another USB cable and check if the issue persists.

Solution 5: Install Universal ADB Drivers

Sometimes, you’ll also need universal ADB drivers to run ADB and fastboot commands. You can download it by clicking here

Advertisements

Solution 6: Install Android Bootloader Interface Drivers

If the above methods have not worked out for you, installing Android Bootloader Interface Drivers could fix the issue. These are designed for ADB and fastboot purposes and are related to the android_winusb.inf file.

Advertisement

Here’s how you can install Android Bootloader Interface drivers on your PC:

  1. Download the Android USB Driver using this link.
  2. Extract the file at your desired location. You’ll get the usb_driver folder. Within that, you will see android_winusb.inf file.
  3. Connect your phone to the PC using a USB cable.
  4. Open Device Manager on your PC.
  5. Expand the Other devices option, right-click on the device name with the yellow exclamation mark, and select Update Driver.
  6. Tap on Browse my computer for driver software.
  7. Click Let me pick from a list of available drivers on my computer.
  8. Select Show All Devices and tap on the Next button.
  9. Tap on Have Disk and click Browse.
  10. Select the android_winusb.inf file we found in step 2.
  11. Click Open and tap on the OK button.
  12. Select Android ADB Interface and click Next.
  13. On the pop-up warning message, select Yes and tap on Install.

So, in this article, we saw various ways to fix the waiting for device error message while running ADB or fastboot commands. I hope that you’ve successfully fixed the problem. Do let us know your thoughts in the comment section below.

Leave a Reply

Your email address will not be published.

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