Перейти к содержимому

Device null not found adb что делать

  • автор:

How to Fix ADB Device Not Found Error on Windows 11, 10, 8 and 7

How-to-fix-ADB-Device-Not-Found-Error-on-Windows-11,-10,-8-and-7-

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.

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.

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)\Android\android-sdk\extras\google\usb_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.

About The Author

Not everything can be communicated verbally, certain things are to be documented for future purposes, with this idea in mind, Aayush Yadav writes content at Systweak Software. He loves writing troubleshooting, how-to articles that will help users fix their problems on their own. He loves Windows and iOS and writes most about them.

Related Posts

NVMe Driver Download and Install in Windows

NVMe Driver Download/Install/Update in Windows (All Version)

January 8, 2024 Dishank Sharma

Wake-On-LAN-Not-Working-on-Windows

How to Fix Wake ON LAN not Working from Sleep on Windows

January 7, 2024 Dishank Sharma

Leave a comment

Seen on

All product names and registered trademarks belong to their respective owners. All the names of the products, companies and services used in this website are for identification purposes only. Use of brand names and trademarks doesn not imply endorsement. Systweak does not have any relationship with any of the companies, products, or services in any form. Being an independent website, Systweak has not been authorized, sponsored, or otherwise approved by Apple Inc. Also, Systweak is not affiliated with Microsoft Corporation, nor does it claim any such implied or direct affiliation. Disclaimer (Last updated on September 16, 2021), the content published on the systweak.com (the “Service”) is for purpose of imparting general information only. Systweak.com undertakes no responsibility for any errors or omissions in the contents of the Service. Under no circumstances shall systweak.com be liable for any direct, indirect , special, consequential, or incidental damages. Systweak.com also does not assume any liability for any damages whatsoever, whether in an action of contract, negligence or another sort, arising out of or in connection with the use of the Service or the contents of the Service. Systweak.com reserves the right to make additions, deletions, or modifications to the contents of the Service at any time without prior notice. Systweak.com does not warrant that the website is free of viruses or other harmful components. External links disclaimer: Systweak.com website may contain links to external websites that are not provided or maintained by or may not be in any way affiliated with systweak.com. Please note that systweak.com does not guarantee the accuracy, relevance, timeliness, or completeness of any information on these external websites. Please note that systweak.com may receive commissions when you click our links and make purchases. However, this does not impact our reviews and comparisons. We try our best to keep things fair, objective and balanced, to help you make the best choice for yourself.

Copyright © Systweak Software, 1999-2024 All rights reserved.

How to fix: Error device not found with ADB.exe

In cmd when I try to do the command: adb shell it shows device not found error. Can someone help me please. It’ll be appreciated.

asked May 22, 2012 at 15:24
MethodManX MethodManX
969 1 1 gold badge 8 8 silver badges 16 16 bronze badges

Did it work before, then quit working? What device are you using and have you installed the proper ADB drivers for it?

May 22, 2012 at 15:25

For ms. windows environment: I had same problem when updated to new android sdk. The driver want support my devices. Go in the system properties and look at the hardware devices. If your device have a yellow icon and missing driver you have to force manual installation of the lastest driver.

May 22, 2012 at 15:32
@Guaido79: Where do I get those drivers? Thank you.
May 22, 2012 at 16:40
@Tim: it never worked. And where do I get the drivers to install. Thanks for the help.
May 22, 2012 at 16:45

@MethodManX it depends entirely on what device you have. Some devices are able to use the driver that ships as part of the SDK, others require specific drivers made by their manufacturers. Hence why I asked originally: What device are you using?

May 22, 2012 at 16:47

21 Answers 21

Don’t forget to go to your device and enable Settings->Developer Options->USB debugging.

answered May 1, 2013 at 22:58
6,066 12 12 gold badges 61 61 silver badges 79 79 bronze badges
This caught me out. See here for how to enable the Developer Options menu: technewscentral.co.uk/…
Sep 8, 2014 at 22:45

This worked for me. I’d previously enabled it and it somehow became disabled, so anyone else who’s having this issue should double check that USB debugging is enabled.

Jun 9, 2018 at 20:36
combined with @ChiragMS’s solution4 to show the options, that was the solution I needed! ty both
Nov 20, 2019 at 15:41

In case someone can’t find the Developer Options on Android 9, here it explains how to enable them: youtube.com/watch?v=5fXQ2Gwg1FY

Feb 26, 2020 at 18:21

Well this answer resolved it for me; due to the fact I subsequently realised I couldn’t check settings of an emulator that isn’t running! Whoops.

Apr 12, 2023 at 16:10

Try any of the following solutions. I get errors with adb every now and then. And one of the following always works.

Solution 1
Open command prompt as administrator and enter

  1. adb kill-server
  2. adb start-server

Solution 2
Install drivers for your phone if you’re not testing on emulator.

Solution 3
Open android sdk manager and install «Google USB Driver» from extras folder. (attached screenshot)

Solution 4
Go to settings > Developer Options > Enable USB Debugging.
(If you don’t see Developer Options, Go to Settings > About Phone > Keep tapping «Build number» until it says «You’re a developer!»

answered Jun 15, 2016 at 23:10
515 5 5 silver badges 12 12 bronze badges

Can you please give an example about drivers and how to install them for Oneplus 2? — — I think it may be about Android 6.0 (API 23) if your system is running Android 6.0.

Aug 18, 2016 at 8:34

@hhh sorry for the late reply but you can always find drivers for your device by a bit of googling. click here please

Jul 20, 2020 at 16:43
Solution 1 works for me. Thanks!
Dec 6, 2023 at 19:55

It depends on windows system but usually:

  1. you go to system properties
  2. look at hardware devices
  3. Right click on the yellow (has to be yellow if it’s driver problem) icon representing your mobile device
  4. select property
  5. Then go on the driver tab
  6. select update driver
  7. choose the bottom selection find on local computer
  8. then choose manually
  9. From the windows opened look for driver disk the bottom right button
  10. Choose the driver from the folder \extras\google\usb_driver\i386 (or amd64 for and).
  11. Remember to uncheck the show only compatible hardware.
  12. Then choose the driver
  13. When windows warn your about possible incompatibility go on.

For my mobile it works, but depend on your mobile if it work or not.

Hope this help, bye.

1,392 2 2 gold badges 29 29 silver badges 38 38 bronze badges
answered May 22, 2012 at 18:19
1,261 11 11 silver badges 18 18 bronze badges
is the driver called: android_winusb.inf ?
May 22, 2012 at 18:35
‘The specified location does not contain information about your device driver’ =<=[ May 22, 2012 at 18:37 I chose : C:\Program Files\Android\android-sdk\extras\google\usb_driver\android_winusb.inf May 22, 2012 at 18:40

very strange, i see the option. From Ms. Doc: Open Device Manager by clicking the Start button Picture of the Start button, clicking Control Panel, clicking System and Maintenance, and then clicking Device Manager.‌ Administrator permission required If you are prompted for an administrator password or confirmation, type the password or provide conn Device Manager, locate the device you want to update, and then double-click the device name. Click the Driver tab, and then click Update Driver. From here select the bottom option, search manually or some similar (my win7 is traslated)

May 23, 2012 at 10:37

@MethodManX I doubt you’re still trying, but I couldn’t see that option either. From the «Browse for driver software on your computer» window, click «Let me pick from a list of device drivers on my computer», then «Have Disk. «, and from there, you can specify the .inf file directly.

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

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 Files\Android\android-sdk\extras\google\usb_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.

How to Open Command Prompt (CMD) in Windows 11? (7 Ways)

How to Open Command Prompt (CMD) in Windows 11? (7 Ways)

How to open Command Prompt (CMD) in Windows 11? If you are looking for methods to open this tool, read this post and you can find some ways.

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.

  • facebook
  • twitter
  • linkedin
  • reddit

About The Author

Vera is an editor of the MiniTool Team since 2016 who has more than 7 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.

Если adb не видит ваше устройство

Если вы тестируете свои программы на реальном устройстве, нужно иметь подходящие драйвера, чтобы Android Studio могла устанавливать вашу программу на устройство. В некоторых телефонах используются стандартные драйвера и Windows без проблем видит ваше устройство (так было у меня с планшетами Nexus 7). В некоторых случаях требуется скачать драйвер у производителя и только тогда всё заработает (например, Samsung S2).

Недавно столкнулся с третьим случаем — устройство Megafon Login+. Студия не видела устройство. Драйверов нет, служба поддержки оператора ответила, что их это не касается. Лучи поноса Мегафону.

На сайте 4PDA можно скачать драйвера для Login+, компьютер видит устройство, а студия по-прежнему не видит его. Пичалька.

Итак, вы установили режим «Отладка по USB» (меню «Для разработчиков»), установили драйвера для Android Composite ADB Interface (может называться несколько иначе). Диспетчер устройств ADB-интерфейс аппарата видит, но при вводе команды adb devices список подключенных устройств остаётся пуст.

Причин может быть несколько, но наиболее вероятная — компьютер не понимает, что за устройство к нему подключено. Довольно часто наблюдается при работе с различными китайскими брендами и «no-name» аппаратами. Решение проблемы простое и избавит Вас от многократных и бесполезных установок-переустановок различных версий драйверов. Нужно просто «познакомить» ваш гаджет с компьютером.

Надо узнать Vendor ID (VID) устройства. В диспетчере устройств щёлкаем два раза по Android Composite ADB Interface (может называться несколько иначе) и переходим на вкладку «Сведения».

Нас интересует, что находится между знаками «_» и «&» — это может четырёхзначное число. Запоминаем его, у меня это было 1271. Далее идём по пути C:\Users\Ваше имя пользователя\.android и открываем файл adb_usb.ini текстовым редактором. Вставляем строку с вашим VID в следующем виде (пример для Login+):

# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT. # USE 'android update adb' TO GENERATE. # 1 USB VENDOR ID PER LINE. 0x1271

Перезагружаем компьютер, запускаем студию, подключаем устройство — Вуаля — всё работает!

Добавить комментарий

Ваш адрес email не будет опубликован. Обязательные поля помечены *