Adb devices no devices found windows

I am attempting to install an Android app on my brand new Nexus 10. I have a .apk file. I have downloaded the Android SDK, installed "Android SDK Tools", "Android SDK Platform-tools", and Google USB

For the Blu Studio 5.5s ADB drivers, you have to go through this hoop. I am certain it is the same with all Blu phones or maybe for all non-Google mfg phones, I am not sure. First of all if you connect the Blu device with USB cable and USB Debuggin off, you will see that Windows 7 loads a generic driver for you to copy on/off files to the phone and SD storage. This will appear when the USB cable is first plugged in and appears as a device icon under Control Panel, Device Manager, Portable Devices, BLU STUDIO 5.5 S (or the device you are working with). Do not bother getting the hardware ID yet — just observe that this happens (which indicates you are good so far and don’t have a bad cable or something).

Go to the phone and switch on USB Debugging in the Developer section of your phone. Notice that an additional item appears as an undefined device now in the device manager list, it will have the yellow exclamation mark and it may have the same name of the phone listed as you saw under Portable Devices. Ignore this item for the moment. Now, without doing anything to the phone (it should be already in USB debug mode) go back to the Portable Devices in Device Manager and right-click the BLU STUDIO 5.5 S or whatever phone you are working with that is listed there without the exclamation mark (listed under Portable Devices). Right click on the icon under Portable Devices, in this example the name that appears is BLU STUDIO 5.5 S. On that icon select Properties, Details, and under the pull down, select Hardware IDs and copy down what you see.

For BLU STUDIO 5.5 S I get:

USBVID_0BB4&PID_0C02&REV_0216&MI_00
USBVID_0BB4&PID_0C02&MI_00

(Note if you do this out of turn, the HW ID will be different with the phone USB debugging turned off. You want to copy the value that it changes to when the USB debugging is ON)

Now do as the instructions say above, of course customizing the lines you add the the INF file with those relating to your own phone, not the Nexus 10. Here is what to customize; when you downloaded the SDK you should have a file structure expanded from the ZIP such as this:

adt-bundle-windows-x86_64-20140321sdkextrasgoogleusb_driver

Find the file named: android_winusb.inf in the usb_driver folder
Make a copy of it and name it anything, such as myname.inf
Edit the myname.inf and add the lines as instructed above only modified for your particular phone. For example, for the BLU STUDIO 5.5 S, I added the following 2 lines as instructed in the 2 locations as instructed.

;BLU STUDIO 5.5 S
%SingleAdbInterface%        = USB_Install, USBVID_0BB4&PID_0C02&REV_0216&MI_00
%CompositeAdbInterface%     = USB_Install, USBVID_0BB4&PID_0C02&MI_00

Note that you add these lines to both the 32 and 64 bit sections, matching how the example in the tutorial reads.

Now go back up to the unknown device that appeared in Device Manager when you switched on device USB debugging and right click on this item (has yellow exclamation mark), right click on it and then select Update Driver Software, and then Browse My Computer, Let Me Pick, click on the Have Disk button and browse to find the myname.inf. Continue to agree to all the prompts warning you it might not be the right driver. As the final step, Windows should have identified the device as Android ADB Interface and once that is done, you should be able to go back, open your CMD window and run the command «adb devices» as instructed in this tutorial and now you should see that the phone is now discovered and communicating.

Now you can go have fun with the adb command.

  • MiniTool

  • MiniTool News Center

  • How to Fix ADB Device Not Found Error in Windows 10? (4 Ways)

By Vera | Follow |
Last Updated March 30, 2022

google search

ADB device not found is a common issue that may happen on your Windows 10 PC when trying to use ADB, Android Debug Bridge to communicate with a device. If you get the error, how can you fix it? Don’t worry and you can find many useful solutions from this post given by MiniTool Solution.

ADB Error Device Not Found Windows 10

ADB, short for Android Debug Bridge, is a command-line utility that allows you to communicate with a device. To be specific, you can control your device over USB from a computer, install and uninstall apps, run shell commands, etc. with ADB. ADB is included with Google’s Android SDK.

However, when you use it, you may get an annoying thing. On the computer screen, you may see a message saying “error: device not found”. Sometimes, you get the error “ADB no devices/emulators found”.

The ADB error can be triggered by various reasons, for example, the ADB driver is not updated, USB debugging is disabled, the connection mode is incorrect, etc. The good news is you can easily fix the issue of ADB no devices emulators found on your Windows 10 PC. Just try the in-depth solutions below.

How to Fix ADB Device Not Found

Enable USB Debugging

To make sure ADB works perfectly, you should enable USB debugging on your Android device. Or else, the ADB error device not found appears.

Step 1: On your Android phone, go to Settings > About.

Step 2: Tap on Build number seven times to activate Developer options.

Step 3: Enable USB debugging.

enable USB debugging on Android

Tip: If you want to know much information about USB debugging, refer to our previous post — What Is USB Debugging & How to Enable/Disable It.

Change Connection Mode

MTP (Media Transfer Protocol) is required for ADB. If your Android phone doesn’t use this connection mode, the issue of ADB device not found may appear on your Windows 10 PC. Just change the connection mode as shown below.

Step 1: Connect your phone to your computer.

Step 2: Swipe down to open the notification panel and select USB connection notification.

Step 3: Choose Media device (MTP).

Update ADB Interface Driver

An outdated ADB interface driver can result in the error — device not found or ADB no devices/emulators found in Windows 11/10. To help you out, it is necessary to install a new version for that driver. Here is what you should try:

Step 1: You need to get a Google USB driver first — directly download that driver or get it via Android SDK Manager. Android gives you a simple guide on Get the Google USB Driver.

Step 2: Run Device Manager in Windows 10 via the Win + X menu.

Step 3: Expand Other devices, USB Device, Android Device, etc., right-click on Android ADB Interface or Android Phone and choose Update driver.

update Android ADB Interface

Step 4: Click Browse my computer for drivers > Let me pick from a list of available drivers on my computer.

Step 5: Click Have Disk and tap on Browse to the directory which includes the Google USB driver you have downloaded before. Usually, the location is C:Program FilesAndroidandroid-sdkextrasgoogleusb_driver.

Step 6: Double-click on Android ADB Interface to install the driver on your PC.

Tip: Sometimes you can fix ADB device not found via installing Universal ADB Windows Driver. You can search for one in Google, then download and install it on your computer.

Reset the ADB Process

If none of the above ways to fix ADB device not found emulator, you can choose to reset the ADB process to fix the issue in Windows 10.

Step 1: Launch Command Prompt on your PC.

Step 2: Type in the following commands and press Enter after each one:

ADB kill-server

ADB start-server

ADB kill-sever command

Final Words

These are all the useful solutions to fix ADB device not found or ADB no devices/emulators found in Windows 10. If you find some other useful ways to fix the ADB error, share your ideas with us in the comment below. Thanks.

About The Author

Vera

Position: Columnist

Vera is an editor of the MiniTool Team since 2016 who has more than 5 years’ writing experiences in the field of technical articles. Her articles mainly focus on disk & partition management, PC data recovery, video conversion, as well as PC backup & restore, helping users to solve some errors and issues when using their computers. In her spare times, she likes shopping, playing games and reading some articles.

Nowadays, Android is one of most leading mobile operating systems and is in nearly installed in all smartphones ranging from extremely affordable to highly paid mobiles. Also, ADB nothing but Android Debug Bridge, is a command-line utility. It helps you control your android smartphone from your computer. It is also used when you may want to debug certain apps or install new ones etc. on your smartphone. But it’s frustrating when you face this device not found error message as ‘adb: error: failed to get feature set: no devices/emulators found‘ when you try to use it. No worries, here in this post, I have listed a couple of solutions which will help you resolve this ADB Device Not Found Error.

Solved ADB Device Not Found Error

People used to find answers on adb tools by searching about; How do I get ADB to recognize my device? How do I connect to ADB devices? How do I find ADB devices on Windows? How do I update ADB drivers? How do you check if ADB is installed or not? How do I uninstall ADB drivers? How do I enable ADB? What is the best APK download site? How do I restart ADB? And so on…

Fixing “error: device not found” when you try to use ADB is not a big issue. Moreover, you can also solve «ADB: error: failed to get feature set: no devices/emulators found error» easily. This guide is published as because one of the readers was asking about ‘ADB devices not showing my device windows 10’ when installing the Microsoft User-Mode Driver Framework on PC. Even you have updated adb driver, many users encounter this when they try to do the adb commands like ADB shell in CMD and it shows device not found error.

You don’t require any technical knowledge in USB debugging windows 10 process this adb toolkit is really easy to try and optimize your Android device. This guild not only helps you to fix no connected devices android studio but also for the android adb install procedure to solve «adb devices empty» kind of issues.

ADB Device Not Found Error is one of the driver issues. And such an issue is most likely due to a problem with your ADM Device driver itself. Due to this issue, even though you have done everything right, you are not being able to connect to your smartphones. Check out below the causes due to which this issue occurs.

Fix ADB Device Not Found Error — Find answers on adb tools by How do I get ADB to recognize my device? How do I connect to ADB devices? How do I find ADB devices on Windows? How do I update ADB drivers? How do you check if ADB is installed or not? How do I uninstall ADB drivers? How do I enable ADB? What is the best APK download site? How do I restart ADB? You dont require any technical knowledge in USB debugging windows 10 process this adb toolkit is really easy to try and optimize your Android device. This guild not only helps you to fix no connected devices android studio but also for the android adb install procedure to solve adb devices empty kind of issues. Just follow below steps to solve this ADB error: device not found error quickly.

Fix ADB Device Not Found Error — Find answers on adb tools by How do I get ADB to recognize my device? How do I connect to ADB devices? How do I find ADB devices on Windows? How do I update ADB drivers? How do you check if ADB is installed or not? How do I uninstall ADB drivers? Fixing ‘adb: error: failed to get feature set: no devices/emulators found’ easyily? How do I enable ADB? What is the best APK download site? How do I restart ADB? You dont require any technical knowledge in USB debugging windows 10 process this adb toolkit is really easy to try and optimize your Android device. This guild not only helps you to fix no connected devices android studio but also for the android adb install procedure to solve adb devices empty kind of issues. Just follow below steps to solve this ADB error: device not found error quickly.

{tocify} $title={Table of Contents}

Why “error: device not found” occur?

For solving the problem of adb no devices/emulators found error you need to know some base.

Causes due to which this ADB device is not found issue occurs:

  1. USB Debugging Disabled: It could be the case that, USB debugging option is not Enabled yet on your Android smartphone.
  2. Incorrect Connection Mode: You might have choosen incorrect connection mode for type of transfer you wanted.
  3. Driver not updated: As discussed above, the issue is most likely because of the problem with your ADM Device driver itself. Thus you have to keep your driver up-to-date.

Anyways, move ahead as I’ve explained the quick solutions for the above possible causes which trigger such errors. I’ve listed a couple of steps below which will help you resolve this ADB Device Not Found Error quickly.

Easily fixing Adb sideload/adb devices not found issue here.

Just follow below steps to solve this ADB «error: device not found» error quickly:

Step 1: Check connection mode.

Android operating system comes with difference connection modes like Mobile Device (MTP) or Camera (PTP). But for ADB, we have to make use of Mobile Device (MTP).

  1. Connect your device to your computer.
  2. Swipe down to access Notification center/panel.
  3. Tap on USB Debugging connected option.
  4. Select Mobile Device (MTP) option.
  5. That’s all, check if your problem gets solved by following this step.
    If NOT, please proceed further to next solutions.
  6. Note: You may try the same by selecting Camera (PTP) option, many of my viewers solved their problem by using PTP as well.

You may also like to know; [Fix] Make Computer Run 10x Faster By Using Virtual Memory

Step 2: Enable USB Debugging through Developer Option.

USB Debugging is a developer option and it helps your Android device to communicate with your computer which has Android SDK installed. It further opens up advanced operations as a developer.

  1. Open Settings on your Android smartphone.
  2. Navigate to About device option.
  3. Tap 7 times on Build Number option.
  4. This will then enable Developer Options.
  5. Now access Developer Options and tap on USB Debugging option.
  6. Try reconnecting your mobile device and check if this could solve your problem.
    If this step too does not solve your problem, please proceed further to the next solutions.

Step 3: Update ADB Driver on your computer.

Since ADB Device Not Found Error is one of the driver issues, you have to keep your driver up-to-date. And for this, follow below steps:

  1. Right click on start button and click Device Manager option.
  2. Expand Other devices option.
  3. Right click on ADB Interface or Androie Phone option.
  4. Click on Update Driver Software option.
  5. When prompted, select ‘Browse my computer for driver software’ option.
  6. Choose Let me pick from a list of device drivers on my computer option.
  7. Select Show all devices option and hit Next button.
  8. Choose Have Disk option.
  9. Browse and locate your SDK. Usually it kept at below location:
    C:Program FilesAndroidandroid-sdkextras\googleusb_driver
  10. Double click on android_winusb.inf file.
  11. Now choose ADB Interface from the list and hit Next button.
  12. Allow the installation to be finished.
  13. Now, try reconnecting your mobile and check if this solves your problem.
    Still no luck? Please proceed further to next solutions.

Check; What’s QoS? How To Boost & Increase The Internet Speed by QoS | Make Router Faster

Step 4: Install Universal ADB Windows Driver.

If none of the above solutions work for you, you have to install Universal ADB Windows Driver on your computer. Just open their official website and download and install it. This installation might be the solution for you. Just try it and check. Otherwise, proceed further to the next solutions.

Download link: Universal ADB Windows Driver Installer.

Step 5: Restart ADB Process.

It could be the case that, you have already implemented the above steps like, USB Debugging enabled, drivers are up-to-date, the universal driver is in place, etc. But do you still facing this issue?

If Yes, you will have to restart entire ADB process and for this you have to use below commands; one for to Kill the process first followed by another command to Start it back again.

Just Open command prompt and run below commands:

  1. adb kill-server: To kill running ADB process.
  2. adb start-server: To start it back again.

You may also like to know; How To Disable Skype Ads

Step 6: Try with different cable.

Sometimes, there could be the problem with your USB cable itself. As you all know, all USB cables are going through endless flexing and curling states. Due to this, your USB cable might get damaged. You also try to purchase dummy cable from the market just to keep our original cable safe and we keep using that cable for charging and for data transfer as well.

I know it sounds silly and you obviously did this already, but I still would like to recommend you to try connecting your phone with another but authentic USB cable rather than dummy cables and check that if it solves your problem.

Bottom Line

I’m sure by following any one of the methods from listed ones will help you resolve this ADB Device Not Found Error.

If you are facing this error or something you want to suggest apart from the above points, feel free to use below comment section below to get in touch with me anytime. Happy to hear from you and to implement the suggestions for helping others.

ADB, or Android Debug Bridge, is a command-line program that allows users to control devices through USB from their computer. The Google Android SDK includes the utility. Several customers complained about receiving the “device not found” message. Alternatively, some users also experienced a sudden lack of ADB and no emulator.

Luckily, the post will help fix the ADB with no device/emulator problem. To troubleshoot the issue, you must first check for updates for ADB drivers. Updated drivers help smooth communication with Windows. You can update drivers manually or use Advanced Driver Updater to update them seamlessly. We recommend the automatic way as it’s safe, quick, and requires minimal technical knowledge.

To get the tool, click the download button below:

download

Reasons for error: device not found.

  • Disabled USB Debugging
  • Incorrect Connection Mode
  • Obsolete Driver

How To Fix ADB Device Not Found Error?

To fix no device emulator found, just follow the steps given below:

Solution1: Enable USB Debugging

To operate the ADB device from the computer, ensure the USB debugging option on your Android device is enabled.

1. On your Android phone, go to Settings > About.
2. In the About section, press “Build number” seven times in succession.

androdid version
3. This will enable the Developer Options.
4. Now access Developer Options > select USB Debugging.

developer option

Now try reconnecting the device with the PC and check if this solves the problem. If this, too, doesn’t work, move to the next step.

Read Also : Download and Update PCI Device Drivers for Windows 11,10

Solution 2: Change ADB Device Connection Mode

Ensure the Android phone’s connection mode is set correctly to identify the ADB device. You must pick the Media Transfer Protocol connection option here (MTP). Otherwise, the “ADB no emulators or devices detected” error will display.

1. Connect the Android phone to the PC.
2. Tap the notification window for more USB choices.
3. Tap USB Debugging connected option
4. Set the connection mode to the Media device (MTP).

device

Now, check the “ADB error: device not found” warning should be gone. If it does, select PTP (Picture Transfer Protocol). It will help get rid of the ADB device not recognized error.

Read This: Download Apple Mobile Device USB Driver for Windows 11,10,8,7

Solution 3: Update Android ADB Interface

  • Manually install the right driver for your ADB device using Device Manager.

1) Select your SDK manager from the Start menu > Run as administrator.

run as a admin
2) When the SDK manager launches, navigate and expand the Extras folder > select Google USB Driver> click Install 1 package.

packages
3) After installing the driver, connect your Android smartphone.
4) Hit the Windows logo + R keys.
5) In the box, type devmgmt.msc and click Enter to launch Device Manager.

run command
6) Look for your Android smartphone. It will be in the Other devices area > right-click it and select Update Driver Software.

update driver
7) Select Browse my computer for drivers.

search automatically
8) Move forward and click Let me pick from a list of device drivers on my computer.

driver software
9) Select the Have Disk option.

select device
10) Click Browse to choose the Google USB Driver you downloaded earlier. Alternatively, you may type the following address into the field.

C:Program Files (x86)Androidandroid-sdkextrasgoogleusb_driver

Then press the OK button.

install disk

11) Select Android ADB Interface and double-click it.

android model
12) Follow the simple on-screen directions to finish installing the driver.

After that, restart the computer to allow the updated driver to take effect.

  • Automatically install the right driver for your ADB device using Advanced Driver Updater.

If you prefer to keep things simple, use Advanced Driver Updater. To use the application and update drivers use the steps below:

1. Install it Advanced Driver Updater.

download

2. Go to Advanced Driver Updater > Scan Now > and wait for the scan results.

Advanced Driver Updater
3. Verify that the drivers are up to date by checking the scan results.

Advanced Driver Updater Scan
4. Click Update driver next to the driver you want to update (If using the application’s FREE version). If you’re a registered user, you may update all of your outdated drivers with the Update All option.

update all outdated driver
5. After the driver has been updated, restart the computer.

Solution 4: Reset the ADB

If the ADB device is not recognized using any of the ways described above, you can reset the ADB process. Enter the following commands into the ADB tool to reset it.

ADB kill-server

ADB start-server

After rebooting the ADB process, try re-using this command line & check whether it works properly and allows you to control the Android phone from the computer or not.

Conclusion:-

In this blog, we have seen how to fix ADB Device Not Found Error on Windows using several methods discussed. Updating drivers is one of the methods to resolve this issue, and updating them automatically by using Advanced Driver Updater is the best way. Use these methods in fixing ADB Device Not Found Error on Windows, and let us know about your views in the comment section below.

Related: Download USB Mass Storage Device Driver on Windows 11

With smartphones being present everywhere, the need for transferring files from your personal computer to your smartphone and vice versa arises. Not only that, you might need to debug certain apps or install new ones, etc. for which a command-line utility called ADB or Android Debug Bridge is often used.

Occasionally, people end up with the issue of not being able to connect to their smartphones, even though, according to them, they’ve done everything right. Well, don’t worry, this is what we’re here for. This guide will let you in on how to solve the ‘Error: device not found’ problem — so sit back, relax and follow the instructions.

ADB Device not found

What Causes the ADB Device Not Found Error?

Before we jump into the solutions, you might want to know what causes this problem. Well, many things can result in this issue —

  • The drivers are not updated. The drivers are the actors responsible for communicating with the interface and your OS. If it is not updated, you might encounter this error.
  • USB debugging is not enabled. This mode is necessary for ADB to work on your Android device.
  • Selection of wrong connection mode. A correct connection mode should be selected for the type of transfer you want to initiate.

Note: Make sure that you have ADB installed.

Method 1: Enable Developer Options and USB Debugging

To start, make sure you’ve enabled USB Debugging on your device since ADB doesn’t work otherwise. To do that:

  1. Go to your phone Settings and select About.
  2. In About menu, tap on ‘Builder number’ seven times which enables Developer Options.
  3. After that, go back and select Developer options.
    Enable Developer Options
  4. Scroll down and tap ‘USB Debugging’.

Method 2: Change Connection Mode

Android has different connection modes which can sometimes cause this problem. In the case of adb, we need MTP (Media Transfer Protocol). One thing to note is that your smartphone might have Transfer files instead of MTP which is the same. For this, what you have to do is:

  1. Make sure your device is correctly plugged in.
  2. Pull down the notification window and select the USB connection notification.
  3. There, select MTP as the connection mode.
    Select MTP as the connection mode

    Note: Some people have reported that selecting the PTP mode worked for them, make sure to try that as well.

Method 3: Update ADB Interface

Sometimes, the issue is due to an outdated ADB interface driver. To update the driver, what you have to do is:

  1. On your computer, right-click on ‘My Computer’ and select Device Manager.
  2. Under Other Devices, you’ll see ‘Android ADB Interface’ or ‘Android Phone’. Right-click it and select ‘Update Driver Software’.
    ADB Interface Driver Update
  3. After that, select ‘Browse my computer for driver software’.
  4. Then, select ‘Let me pick from a list of device drivers on my computer’.
  5. A window will pop up, make sure ‘Show all devices’ is highlighted and click Next.
    Highlight Show All Devices
  6. Click the ‘Have Disk’ option.
  7. Go to where you’ve installed your SDK which is usually
    C:Program FilesAndroidandroid-sdkextras\googleusb_driver

    where you’ll have to double click android_winusb.inf

  8. Select ‘Android ADB Interface’ from the list.
    Select Android ADB Interface
  9. Click ‘Yes’ and then click ‘Install’.
  10. Wait for the installation to complete and then close the window.

You can try reconnecting your device if it doesn’t recognize it already.

Method 4: Install Universal ADB Windows Driver

If you are sure that the above-mentioned solutions are not going to work for you or didn’t work for you, installing Universal ADB Windows Driver might be the solution for you. It is pretty simple, download the driver from their official website and install it.

Method 5: Reset the ADB Process

It sometimes happens that everything else is working but you still can’t list your smartphone – meaning you have installed the USB driver, enabled USB debugging, etc. In such cases, killing the server and starting it again might help you out. To do that, type the following commands in the command line

adb kill-server

adb start-server

ADB Kill/Start Server

Method 6: Change the Cable

Finally, if nothing works out for you, getting a new cable might be the way for you. The chances of your cable being faulty are high which means no matter what you do, your problem will remain as the problem is not with your driver but rather with the hardware. To check whether your cable is faulty or not, try the following:

  1. Connect your cable to a port on a charger.
  2. Try charging your smartphone with that cable.

If it doesn’t start charging, this means your cable is at fault and you’ll have to get another.

Photo of Kevin Arrows

Kevin Arrows

Kevin is a dynamic and self-motivated information technology professional, with a Thorough knowledge of all facets pertaining to network infrastructure design, implementation and administration. Superior record of delivering simultaneous large-scale mission critical projects on time and under budget.

In this guide, we will show you the steps to fix the ADB Device not found error. In some instances, the Command or PowerShell window might also show blank under the list of devices attached. Along the same lines, there are a few other common ADB Errors that few have already covered before. These include: Fix adb is not recognized Error and Fix Unauthorized Device with ADB Commands [3 methods]. As of now, our focus will be on fixing the ADB device not found error that shows a blank result under the List of Devices Attached section. Follow along for the detailed instructions.

Android devices, thanks to their open-source ecosystem allows you to carry out a plethora of tweaks. Now, these tweaks encompass two different domains. The first one is the everyday users who customize their device using numerous themes, icon packs, launchers, etc. Then comes the tech enthusiasts, who take these customizations one step ahead. They unlock the device’s bootloader, flash custom ROMs and custom recoveries, or even root their devices via Magisk.

But no matter to which domain you belong, one thing stands in common: the use of ADB and Fastboot Commands. The general users might use these commands to boot their device to Fastboot/Bootloader or Recovery Mode, Apply Update via ADB Sideload, installing/uninstalling apps, among other tasks. Then the geeks could make use of these commands to unlock the bootloader (fastboot oem unlock), boot their device to TWRP (fastboot boot twrp.img), flash ZIPs, and IMG files (fastboot flash boot magisk_patched.img), and the list goes on.

However, sometimes these commands just fail to execute. It could take the shape of quite a few errors (as already discussed in the introductory paragraph). Among them, the most common one seems to be the ADB Device not found and the List of Devices Attached section would be blank. In this guide, we will make you aware of all the plausible reasons for this error, and more importantly how to fix it. Follow along.


  • Fix Magisk Module Bootloop without TWRP Recovery
  • How to Fix TWRP Error 20 GApps after flashing LineageOS
  • Fix Mi Account Authorization | Unbrick Xiaomi | EDL Mode
  • How to Fix Error: Cannot load recovery.img

So when and why this error happens? Answering the ‘when’ part first, well it happens when you execute the adb devices command in CMD or PowerShell window. Upon typing in this command, in general cases, you would have got your device ID followed by the device keyword. However, when you are facing this issue, the CMD/PowerShell window wouldn’t result in any value. Rather they would start off with a new line. If it is a little bit more caring, then you might get the <waiting for device> message, which again doesn’t do any good to the end-user.

adb device not found error list of devices attached is blank

With that said, this guide will list out all the possible methods to fix the ADB Device not found [List of Devices Attached is blank]. Do keep in mind that there isn’t any universal fix for this error. You will have to try all the below-mentioned methods one by one until you achieve success. Furthermore, we will start off with the most basic tweak first followed by the slightly advanced ones. So without further ado, let’s get on with this guide.

fix adb missing error

Fix 1: Reverify ADB Installation

First and foremost, make sure that you have the proper ADB and Fastboot binaries installed. There’s nothing much that you need to do- just install the Android SDK Platform Tools provided by Google [Windows | Linux | macOS]. If you have installed any other ADB and Fastboot tools, then please uninstall them and only use the one provided by Google. The reason?

android sdk

Credit: Android Developer Forum

Well, all these tools are proving to be among the most lite-weights end up missing a few important files, especially those related to the device storage partition. Hence, install the Android SDK Platform Tools on your PC and see if it fixes the ADB Device not found [List of Devices Attached is blank] error or not.


  • How to Boot into Recovery (TWRP/Stock) from Fastboot Mode
  • Fix TWRP Error 7 (While Flashing Custom ROM via TWRP)
  • How to Fix FAILED (remote: unknown command) Error
  • Mi Unlock Tool Errors and their Fixes

Fix 2: Launch Command Prompt where ADB is installed

This is one fact that many users end up missing. You should only launch the Command Prompt window inside the folder where ADB and Fastboot binaries are present. Since we have recommended the installation of Android SDK Platform Tools, hence you should launch the CMD window inside the platform-tools only. Now there are two different ways of doing so:

The Direct Approach:

As is evident from the name, this method tells you to directly open the CMD window inside the ADB folders. Here’s how it could be done:

command prompt

  1. Head over to the platform-tools folder on your PC.
  2. Then type in CMD in the folder’s address bar and hit Enter.
  3. This will launch the Command Prompt inside the platform-tools folder itself.

The Indirect Approach

In this method, you could launch CMD normally from the Start menu and then change its directory to the folder where ADB is installed. Here are the instructions for the same:

change adb directory cmd fix adb device not found

  1. Head over to the Start menu and search for CMD.
  2. Launch the Command Prompt window as an administrator.
  3. Now type in cd followed by the ADB installation directory.
  4. For example, I have installed Android SDK platform Tools on my desktop, hence the command in my case would be
    cd C:UsersusernameDesktopplatform-tools

Once you have changed the directory to the ADB installation location, check if it fixes the ADB Device not found [List of Devices Attached is blank] error or not.

Fix 3: Make sure USB Debugging is Enabled

While it is mostly along the obvious lines, but this is usually among the biggest culprits for this issue. USB Debugging is needed to be enabled so that your PC recognized your device in the ADB Mode. So you should reverify that the USB Debugging is indeed enabled. Here are the required instructions for the same:

usb debugging oneplus

  1. Head over to Settings on your device. Then go to About Phone and tap on Build Number 7 times. Xiaomi users should tap on MIUI Number 7 times.
  2. You will then get a toast message that Developer Options is enabled.
  3. So now go back to Settings followed by System.
  4. Now go to Developer Options (in some devices it might be under the Advanced section) and enable the USB Debugging toggle.

Once done, connect your device to PC via USB cable and see if it is able to fix ADB Device not found [List of Devices Attached is blank] error. [Don’t Miss: How to Enable USB Debugging on a Broken Android Device’s Screen?]


  • How to Install OTA Updates in Rooted Android Device
  • How to Install Substratum Themes on any Android (Oreo 8.0 and above)
  • Permanently Install TWRP without TWRP ZIP File (only using TWRP.img file)
  • Root Android Devices Without TWRP Recovery

Fix 4: USB Connection should be Authorized

Enabling the USB Debugging is just half the done work. The first time you connect your device to the PC in ADB Mode you will have to verify the device’s fingerprint with your PC. The best bet, in this case, is to revoke the USB Debugging permission of your device and then re-verify it. Here is how it could be done:

  1. First off, head over to the Developer Options on your device. If you haven’t enabled it yet, then go to Settings > About Phone > Tap on Build Number 7 times > Go back to Settings > System > Advanced > Developer Options.
  2. Once you reach Developer Options, scroll to the Debugging section and tap on Revoke USB Debugging Authorizations. Tap on OK in the confirmation dialog box that appears.
    revoke usb debugging adb unauthorized
  3. Now launch the CMD window inside the platform-tools folder (as mentioned in Fix 2).
  4. Then type in the below command in the CMD window:
    adb devices
  5. You will now get an Allow USB Debugging on your device, tap on Allow.
    authorize usb fingerprint fix adb device missing error
  6. Furthermore, if this is your own trusted PC, then you could also tick-mark the Always allow from this computer option. Doing so will save you from allowing the USB Debugging every time you connect the device to your PC.
  7. Once that is done, see if it fixes the ADB Device not found [List of Devices Attached is blank] error.

Fix 5: Change USB Connection Mode

Some users have reported success after changing the USB Connection Mode to MTP from USB storage mode (or File Transfer mode). So as soon as you connect your device to the PC via USB cable, you should see the current USB connection mode. Select MTP from the list (if it is not there, then you may also switch to PTP mode). Once you do so, you may see the setup notification on your PC, as shown below:

android device setup pc fix adb device not found

However, if you don’t see the option to change the USB Connection Mode, then you could manually carry out this step as well. For that, go to Settings > System > Developer Options > Default USB Configurations (see below image). Then select MTP (or PTP) from the options. Now check whether it fixes the ADB Device not found [List of Devices Attached is blank] error or not.

default usb connection fix adb device not found error


  • How to Pass Magisk SafetyNet on Rooted Android 11
  • Root Android 11 via Magisk Patched boot.img (without TWRP)
  • Fix Android stuck in Recovery Mode: No Command screen
  • Fix Magisk patched boot.img issue while Rooting Android 11

Fix 6: Manually Install Drivers

Most Android devices come baked in with their own USB Drivers. As a result, as soon as you connect your device to your PC via USB cable, the drivers would automatically be installed on your PC. But if that doesn’t happen you may manually install them as well. Google provides the required android_winusb file on its Android Developers website.

google usb drivers fix adb device not found

You just need to download and add it via your PC’s Device Manager. And as opposed to what you might have read till now, this USB driver file is universally accepted by all Android devices. Even if you see sites hosting USB drivers for individual phones, it’s just to increase clicks, the resulting file will be the same (android_winusb). So download this file and proceed with the below steps.

  1. To begin with, extract the contest of the downloaded driver file and you should get the following files:
  2. Right-click on the Windows icon and select Device Manager from the menu.
  3. Within that, go to the Other devices section and you should see your Android device listed there. In some cases, it might be under the Ports section or the Portable Device section as well.
  4. Once you find the device, right-click on it, and select Update Drivers.
    update android usb drivers fix adb device not found
  5. In the next popup that appears, select Browse my computer for driver software.
    browse pc for manual android usb adb driver installation
  6. Now click on the Browse button, navigate to the extracted driver folder, and select the usb_driver folder. Yes, you don’t need to select the individual driver file, just select the driver folder and your PC will take care of the rest.
  7. Once you have selected the USB Driver folder, hit Next and proceed with the on-screen instructions to install it.
    install android_winusb drivers
  8. After the installation is complete, unplug and then replug your device to the PC via USB Cable. See if it fixes the ADB Device not found [List of Devices Attached is blank] error.

Fix 7: Add ADB System Variable Path

In some cases, the system isn’t able to decide which ADB Drivers do it needs to use. This usually happens if you have more than one copy of ADB/Fastboot Drivers installed on your PC. This usually might conflict with the environmental system variable related to the Android SDK. The fix for that is to manually add the ADB installation directory, i.e, the platform-tools folder’s location to the System Environment Variables. here are the required instructions for the same:

  1. Head over to the Start menu and search for View Advanced System Settings.
    view-advanced-system-settings
  2. Go to the Advanced tab and click on the Environmental Variables button.
    view-advanced-system-settings
  3. You should now see two sections: User Variables and System variables. As for this guide, we would be dealing with the latter.
  4. So select Path from the System Variables and click on Edit.
    system-variable-adb-path
  5. It will bring up the Edit environment variable option, click Browse from the right-hand side.
    edit-environmental-variable-adb-not-recognized
  6. Now navigate to the location where you have installed the ADB and Fastboot binaries and select the platform-tools folder and click OK.
    platform-tool-path-environmental-variables
  7. You should now see this directory successfully added to the environment variables. Click OK to close the dialog box.
    adb-not-recognized-path-added
  8. Likewise, the path will also be visible in System variables under Environment Variables, as shown in the below image. Click OK to close this dialog box as well. That’s it. Your error now stands rectified.
    adb-not-recognized-path-added-platform-tools
  9. Once the path has been added, plug in your device via USB cable to your PC, and the issue would have been fixed by now.

So with this, we conclude the guide on how to fix the ADB Device not found [List of Devices Attached is blank] error. We have shared seven different fixes for the same, any one of which should work out in your favor. Do let us know in the comments if you have any queries concerning the aforementioned steps. We will get back to you with a solution at the earliest.


  • [GUIDE] Flash ROMs/Magisk/TWRP/Kernels on A/B Partition Devices
  • Everything About Magisk- Manager, Modules and More
  • Best Magisk Modules of 2020 [PART-1]
  • [3 METHODS] Unroot any Android Device-Uninstall Magisk

About Chief Editor

Sadique Hassan

administrator

A technical geek by birth, he always has a keen interest in the Android platform right since the birth of the HTC Dream. The open-source environment always seems to intrigue him with the plethora of options available at his fingertips. “MBA by profession, blogger by choice!”

В этом руководстве мы покажем вам, как исправить ошибку «Устройство ADB не найдено». В некоторых случаях окно Command или PowerShell также может быть пустым под списком подключенных устройств. В том же духе есть несколько других распространенных ошибок ADB, которые уже были рассмотрены ранее. К ним относятся: Исправление adb не распознается Ошибка и Исправление несанкционированного устройства с помощью команд ADB [3 methods]. На данный момент мы сосредоточимся на исправлении ошибки «Устройство ADB не найдено», которая показывает пустой результат в разделе «Список подключенных устройств». Следуйте инструкциям.

Устройства Android благодаря своей экосистеме с открытым исходным кодом позволяют выполнять множество настроек. Теперь эти настройки охватывают два разных домена. Первый — это обычные пользователи, которые настраивают свое устройство с помощью многочисленных тем, пакетов значков, средств запуска и т. д. Затем идут технические энтузиасты, которые делают эти настройки на шаг впереди. Они разблокируют загрузчик устройства, прошивают пользовательские ПЗУ и пользовательские восстановления или даже рутируют свои устройства через Magisk.

Но независимо от того, к какому домену вы принадлежите, есть одна общая черта: использование команд ADB и Fastboot. Обычные пользователи могут использовать эти команды для загрузки своего устройства в режим Fastboot/Bootloader или Recovery Mode, применения обновлений через ADB Sideload, установки/удаления приложений и других задач. Затем гики могут использовать эти команды, чтобы разблокировать загрузчик (разблокировка fastboot oem), загрузить свое устройство в TWRP (fastboot boot twrp.img), прошить ZIP-файлы и файлы IMG (fastboot flash boot magisk_patched.img) и список продолжается.

Однако иногда эти команды просто не выполняются. Это может принять форму довольно большого количества ошибок (как уже обсуждалось во вступительном абзаце). Среди них наиболее распространенным является устройство ADB, не найденное, и раздел «Список подключенных устройств» будет пустым. В этом руководстве мы сообщим вам обо всех возможных причинах этой ошибки и, что более важно, о том, как ее исправить. Следуйте вместе.

Итак, когда и почему возникает эта ошибка? Отвечая сначала на часть «когда», ну, это происходит, когда вы выполняете adb устройства команду в окне CMD или PowerShell. После ввода этой команды, как правило, вы получите идентификатор вашего устройства, за которым следует ключевое слово устройства. Однако, когда вы сталкиваетесь с этой проблемой, окно CMD/PowerShell не приводит к каким-либо значениям. Скорее они начнут с новой строки. Если немного повнимательнее, вы можете получить сообщение , что опять же не приносит никакой пользы конечному пользователю.

adb устройство не найдено ошибка список подключенных устройств пуст

С учетом сказанного, в этом руководстве будут перечислены все возможные способы исправления не найденного устройства ADB. [List of Devices Attached is blank]. Имейте в виду, что универсального решения этой ошибки не существует. Вам придется попробовать все нижеперечисленные методы один за другим, пока вы не добьетесь успеха. Кроме того, мы начнем с самых простых настроек, а затем добавим немного продвинутых. Итак, без лишних слов, давайте продолжим это руководство.

исправить ошибку отсутствия adb

Исправление 1: повторная проверка установки ADB

Прежде всего, убедитесь, что у вас установлены правильные двоичные файлы ADB и Fastboot. Вам не нужно ничего делать — просто установите инструменты платформы Android SDK, предоставленные Google. [Windows | Linux | macOS]. Если вы установили какие-либо другие инструменты ADB и Fastboot, удалите их и используйте только тот, который предоставлен Google. Причина?

андроид SDKПредоставлено: Форум разработчиков Android.

Что ж, все эти инструменты оказались одними из самых облегченных, в конечном итоге отсутствуют несколько важных файлов, особенно тех, которые относятся к разделу хранилища устройства. Следовательно, установите Android SDK Platform Tools на свой ПК и посмотрите, исправит ли он не найденное устройство ADB. [List of Devices Attached is blank] ошибка или нет.

Исправление 2: Запустите командную строку, где установлен ADB

Это один факт, который многие пользователи упускают из виду. Вы должны запускать окно командной строки только в папке, где присутствуют двоичные файлы ADB и Fastboot. Поскольку мы рекомендовали установить Android SDK Platform Tools, вам следует запускать окно CMD только внутри инструментов платформы. Теперь есть два разных способа сделать это:

Прямой подход:

Как видно из названия, этот метод предлагает вам напрямую открыть окно CMD внутри папок ADB. Вот как это можно сделать:

командная строка

  1. Перейдите в папку platform-tools на вашем ПК.
  2. Затем введите CMD в адресную строку папки и нажмите Enter.
  3. Это запустит командную строку внутри самой папки инструментов платформы.

Косвенный подход

В этом методе вы можете запустить CMD в обычном режиме из меню «Пуск», а затем изменить его каталог на папку, в которой установлен ADB. Вот инструкции для того же:

изменить каталог adb cmd исправить устройство adb не найдено

  1. Перейдите в меню «Пуск» и найдите CMD.
  2. Запустите окно командной строки от имени администратора.
  3. Теперь введите cd, а затем каталог установки ADB.
  4. Например, я установил инструменты платформы Android SDK на свой рабочий стол, поэтому команда в моем случае будет C:UsersusernameDesktopplatform-tools

После того, как вы изменили каталог на место установки ADB, проверьте, исправляет ли он ошибку «Устройство ADB не найдено». [List of Devices Attached is blank] ошибка или нет.

Исправление 3: убедитесь, что отладка по USB включена

Хотя в основном это происходит по очевидным направлениям, но обычно это одна из главных причин этой проблемы. Отладка по USB должна быть включена, чтобы ваш компьютер распознал ваше устройство в режиме ADB. Поэтому вам следует еще раз убедиться, что отладка по USB действительно включена. Вот необходимые инструкции для того же:

отладка по usb oneplus

  1. Перейдите в Настройки на вашем устройстве. Затем перейдите в «О телефоне» и нажмите «Номер сборки» 7 раз. Пользователи Xiaomi должны нажать на номер MIUI 7 раз.
  2. Затем вы получите всплывающее сообщение о том, что параметры разработчика включены.
  3. Итак, теперь вернитесь в «Настройки», а затем «Система».
  4. Теперь перейдите в «Параметры разработчика» (на некоторых устройствах он может находиться в разделе «Дополнительно») и включите переключатель «Отладка по USB».

После этого подключите свое устройство к ПК через USB-кабель и посмотрите, сможет ли оно исправить ADB Device not found. [List of Devices Attached is blank] ошибка. [Don’t Miss: How to Enable USB Debugging on a Broken Android Device’s Screen?]

Исправление 4: USB-соединение должно быть авторизовано

Включение отладки по USB — это только полдела. При первом подключении устройства к ПК в режиме ADB вам необходимо будет проверить отпечаток пальца устройства на ПК. В этом случае лучше всего отозвать разрешение USB-отладки вашего устройства, а затем повторно проверить его. Вот как это можно сделать:

  1. Прежде всего, перейдите к параметрам разработчика на вашем устройстве. Если вы еще не включили его, перейдите в «Настройки»> «О телефоне»> «Семь раз нажмите на номер сборки»> «Вернитесь в «Настройки»> «Система»> «Дополнительно»> «Параметры разработчика».
  2. Когда вы дойдете до параметров разработчика, прокрутите до раздела «Отладка» и нажмите «Отменить авторизацию отладки по USB». Нажмите OK в появившемся диалоговом окне подтверждения.
    отозвать несанкционированную отладку usb через adb
  3. Теперь запустите окно CMD в папке инструментов платформы (как указано в исправлении 2).
  4. Затем введите приведенную ниже команду в окне CMD: устройства adb.
  5. Теперь вы получите «Разрешить отладку по USB» на своем устройстве, нажмите «Разрешить».
    авторизовать отпечаток пальца usb, исправить ошибку отсутствия устройства adb
  6. Кроме того, если это ваш собственный доверенный компьютер, вы также можете отметить параметр «Всегда разрешать с этого компьютера». Это избавит вас от необходимости разрешать отладку по USB каждый раз, когда вы подключаете устройство к компьютеру.
  7. Как только это будет сделано, посмотрите, исправит ли это устройство ADB, не найденное [List of Devices Attached is blank] ошибка.

Исправление 5: изменить режим USB-подключения

Некоторые пользователи сообщают об успешном изменении режима USB-подключения на MTP из режима USB-накопителя (или режима передачи файлов). Поэтому, как только вы подключите свое устройство к ПК через USB-кабель, вы должны увидеть текущий режим USB-подключения. Выберите MTP из списка (если его нет, то вы также можете переключиться в режим PTP). Как только вы это сделаете, вы можете увидеть уведомление об установке на вашем ПК, как показано ниже:

Настройка устройства Android ПК исправить Устройство adb не найдено

Однако, если вы не видите возможность изменить режим USB-подключения, вы также можете выполнить этот шаг вручную. Для этого перейдите в «Настройки» > «Система» > «Параметры разработчика» > «Конфигурации USB по умолчанию» (см. изображение ниже). Затем выберите MTP (или PTP) из вариантов. Теперь проверьте, исправляет ли это устройство ADB, не найденное [List of Devices Attached is blank] ошибка или нет.

Исправление USB-соединения по умолчанию Ошибка устройства adb не найдена

Исправление 6: установка драйверов вручную

Большинство Android-устройств поставляются со своими собственными USB-драйверами. В результате, как только вы подключите свое устройство к компьютеру через USB-кабель, драйверы будут автоматически установлены на ваш компьютер. Но если этого не произойдет, вы также можете установить их вручную. Google предоставляет необходимые android_winusb на веб-сайте разработчиков Android.

Драйверы Google USB исправляют устройство adb, не найденное

Вам просто нужно загрузить и добавить его через Диспетчер устройств вашего ПК. И в отличие от того, что вы, возможно, читали до сих пор, этот файл драйвера USB универсально принимается всеми устройствами Android. Даже если вы увидите сайты, на которых размещены USB-драйвера для отдельных телефонов, это просто для увеличения кликов, результирующий файл будет таким же (android_winusb). Поэтому загрузите этот файл и выполните следующие шаги.

  1. Для начала извлеките конкурс из скачанного файла драйвера и у вас должны получиться следующие файлы:
  2. Щелкните правой кнопкой мыши значок Windows и выберите в меню Диспетчер устройств.
  3. В нем перейдите в раздел «Другие устройства», и вы должны увидеть свое устройство Android в списке. В некоторых случаях он может находиться в разделе «Порты» или в разделе «Переносное устройство».
  4. Найдя устройство, щелкните его правой кнопкой мыши и выберите «Обновить драйверы».
    обновить драйверы usb для android исправить устройство adb не найдено
  5. В следующем появившемся всплывающем окне выберите Поиск драйверов на моем компьютере.
    просмотрите компьютер для ручной установки драйвера android usb adb
  6. Теперь нажмите кнопку «Обзор», перейдите к извлеченной папке драйвера и выберите папку usb_driver. Да, вам не нужно выбирать отдельный файл драйвера, просто выберите папку с драйвером, а ваш ПК позаботится обо всем остальном.
  7. Выбрав папку с USB-драйвером, нажмите «Далее» и следуйте инструкциям на экране, чтобы установить его.
    установить драйверы android_winusb
  8. После завершения установки отключите и снова подключите устройство к ПК через USB-кабель. Посмотрите, исправляет ли это устройство ADB, не найденное [List of Devices Attached is blank] ошибка.

Исправление 7: добавьте путь к системной переменной ADB

В некоторых случаях система не может решить, какие драйверы ADB ей нужно использовать. Обычно это происходит, если на вашем ПК установлено более одной копии драйверов ADB/Fastboot. Обычно это может конфликтовать с системной переменной среды, связанной с Android SDK. Исправление для этого состоит в том, чтобы вручную добавить каталог установки ADB, т. е. расположение папки инструментов платформы в переменные системной среды. вот необходимые инструкции для того же:

  1. Перейдите в меню «Пуск» и найдите «Просмотр дополнительных параметров системы».
    просмотр-расширенные-системные-настройки
  2. Перейдите на вкладку «Дополнительно» и нажмите кнопку «Переменные среды».
    просмотр-расширенные-системные-настройки
  3. Теперь вы должны увидеть два раздела: пользовательские переменные и системные переменные. Что касается этого руководства, мы будем иметь дело с последним.
  4. Поэтому выберите «Путь» в системных переменных и нажмите «Изменить».
    системная переменная-adb-путь
  5. Появится параметр «Изменить переменную среды», нажмите «Обзор» с правой стороны.
    редактировать-экологической-переменной-adb-не-признано
  6. Теперь перейдите в место, где вы установили двоичные файлы ADB и Fastboot, выберите папку с инструментами платформы и нажмите «ОК».
    платформа-инструмент-путь-переменные среды
  7. Теперь вы должны увидеть, что этот каталог успешно добавлен в переменные среды. Нажмите OK, чтобы закрыть диалоговое окно.
    adb-не-признанный-путь-добавлен
  8. Точно так же путь также будет виден в системных переменных в разделе «Переменные среды», как показано на изображении ниже. Нажмите OK, чтобы закрыть и это диалоговое окно. Вот и все. Теперь ваша ошибка исправлена.
    adb-не-распознанный-путь-добавленные-платформенные-инструменты
  9. После добавления пути подключите устройство через USB-кабель к компьютеру, и проблема уже будет решена.

Итак, на этом мы завершаем руководство о том, как исправить не найденное устройство ADB. [List of Devices Attached is blank] ошибка. Мы поделились семью различными исправлениями для одного и того же, любое из которых должно сработать в вашу пользу. Дайте нам знать в комментариях, если у вас есть какие-либо вопросы относительно вышеупомянутых шагов. Мы вернемся к вам с решением в ближайшее время.

I have LG G3 with android 5.0 lollipop and I want to connect it to my laptop with windows 8.1 OS (For using unity remote).

When I connect my phone I can access to storage but I can't see my device in adb.exe. I tried many solution like this and this but nothing work for me.

For now in developer mode I checked these:

  • Stay awake
  • USB debugging
  • Allow mock locations

And I installed the driver from lg website. This is output for adb usb command:

shell@g3:/ $ adb usb
adb usb
error: device not found

Actually I really confused because I think it recognize my device and show g3 name but I don’t know why it can’t show my device name in attached device!!!

This is windows command prompt screenshot:
adb

Without lg driver installed, my device in device manager is like image below and when I try to update the driver using Androidandroid-sdkextrasgoogleusb_driver it say: Windows could not find driver software for your device

without lg driver

And when I install lg driver, my device is like image below and again i can’t update driver and it say: Windows has determine the driver software for your device is up to date

My device with LG driver installed

Recently I bought Nexus 5 Android phone and was excited to write my first How-to tutorial about Android screencast. In order to screencast your android, the device has to be connected to your computer. Of course, there are several apps for screencasting your rooted device, but the method that I was planning to write doesn’t require any app to be installed or device rooting. Ok, now back to connecting my device to the Windows 7 laptop. Oops! Now I have a problem, the Windows did not detect my device and just thrown an error “Driver not Installed”.

I googled for few minutes and finally found the solution, which I like to share it with you all.

Step 1: Install Android SDK on Windows 7

  • Just to go Android.com and download the SDK bundle.
  • Once downloaded, unzip the package.
  • Start ‘SDK Manager.exe‘. This step might take few minutes depending upon the speed of your computer.
  • Once the SDK Manager is launched, scroll down to expand “Extras” folder. Now, select “Google USB Driver” and click “Install <total_no_of_packages_selected> packages…” button.

Install Google USB Driver

  • Wait until the SDK Manager completes the installation process.
  • You may close the “SDK Manager”. Now you will find a new folder called ‘google’ under ‘sdk’ (unzipped folder in step 1)

Step 1: Install/Update USB driver

  • Connect your device to the computer.
  • Right click on “My Computer” and choose Manage.
  • Double click “Device Manager” from the left side menu
  • Right click on the yellow icon displayed next to your mobile device and choose “Update Driver Software

Install Android device driver

  • In the next dialog, choose “Browse my computer for driver software”

Install nexus usb driver

  • Browse to ADT folder and select ‘adt\sdk\extras\google\usb_driver’ and click “Next”

Install Android ADB interface

  • Now Windows should install “Android Composite ADB Interface” for your device.

Android adb interface

Step 2: Enable USB Debugging on Android

  • Jump to “Settings” and tap “About Phone
  • Tap “Build Number” seven times to enter “Developer Options”
  • Go back to “Settings > Developer Options” and enable “USB Debugging
  • You may also have to switch between MTP to Camera PTP. To do that, go to “Settings > Storage” and tap menu at the top and switch between “Media device (MTP)” to “Camera (PTP)”

Connect android to computer

That’s it. Now your device should connect properly to Windows.

Step 3: Verify if the device is connected properly to the computer

Launch the command prompt and navigate to the ADT directory unzipped at the step 1. You will have to change directory to ‘sdk\platform-tools\’ and run the below command.

adb.exe devices

ADB daemon will be started and it will listen for any device connected to your system. The above command will then list the devices connected.

Still have a problem? Post in our comment section.

Like this post? Please share to your friends:
  • Adamview скачать бесплатно для windows 10
  • Adam 4561 драйвер для windows 10 скачать
  • Adam 4561 driver windows 10 скачать
  • Ad1888 soundmax audio driver windows 7
  • Activinspire promethean скачать бесплатно для windows 10