Everyone faces this problem at least once: you connect your smartphone or tablet to your computer via a USB cable, but nothing happens other than charging. The computer does not see the phone or identifies it as an unknown device. The situation is common, but ambiguous, and there are quite a few reasons why it occurs. Today we will figure out what causes such problems and how to deal with them.
Software and hardware failures lead to a situation where the PC does not recognize the mobile device connected to it:
- Lack of device driver in the PC operating system.
- The driver does not match the device model.
- There is no USB driver in the system or it is malfunctioning.
- Connection with a cable that is not suitable for data transmission or is damaged.
- Malfunction of the USB socket (both on the computer and on the phone), group of sockets or USB controller on the PC.
- Failure of any of the computer equipment, blocking by static electricity.
- Error in phone system settings.
- Blocking access to the phone using security programs running on a PC (including if the gadget is infected with a virus).
- The application used to synchronize your phone and PC (if you are using) has crashed.
In case of software problems, the computer, as a rule, does not display the contents of the phone’s memory, but the device charges normally when connected to it. If the problem is due to a physical malfunction, charging most often does not work either, but there are exceptions when only the data lines do not work.
An analysis of the previous situation—what happened before the problem arose—helps outline the range of possible causes. For example:
- You have reinstalled the operating system on your computer or removed some of the drivers (the reason is that the required driver is missing).
- The phone (tablet) was no longer detected after flashing the firmware, cleaning it from viruses, deleting applications, optimizing and other manipulations with the OS (the operating system of the mobile device malfunctioned).
- The device has been subjected to mechanical damage (the USB socket is damaged) or has been repaired (after replacing parts, a driver of a different version is needed or the fault has not been completely eliminated).
- You are using a USB cable that you have never used to connect your phone to a computer before (the cable is only for charging or is damaged), etc.
We quickly determine the culprit of the problem
Tracing a cause-and-effect relationship makes it much easier to localize the problem, but in about half of the cases there is nothing specific that precedes it. If this is the case for you, the following steps will help you determine where the failure occurred - in your mobile device, PC or USB cable.
- Move the cable in the area of the connectors (kinks most often form in these places) and see if the phone (tablet) is detected in the explorer or device manager of the computer. Or connect the devices with another cable that is known to work and is suitable for data transmission.
- Connect your phone to another computer, as well as another mobile device to this PC. If the phone is not detected anywhere, the problem is definitely in it. The same is the case with a computer.
- If the problem seems to be in the computer, check the phone in all USB sockets; perhaps the problem is in one or more of them (for example, only in the front group).
If you conclude that the cable is the source of the problem, simply replace it. What to do in other cases, read on.
The culprit of the failure is the phone. What to do?
If the diagnostics clearly indicate a problem with your mobile device, perform the following steps in order. After each step, check to see if the problem is resolved. If not, move on to the next one.
- Reboot your device.
- Connect your phone to your computer. Once connected, slide down the quick settings menu bar and make sure that the “Connect as” list does not include “charge only,” or “camera” or “media device.” Select the "USB storage" option.
- Open Android system settings (in older versions, “Options”). Go to the "Wireless Networks" section. Turn on modem mode. Or vice versa, if it is on, turn it off. In some editions of Android, this parameter controls not only the modem, but also the connection of the gadget to the PC as a drive.
- Experiment with putting your device into USB debugging mode. Open the “System” and “For Developers” sections in the settings. Uncheck or check the box next to “USB Debugging”.
- Disconnect the phone from the computer, turn it off and remove the battery from it (the phone) (of course, if it is removable). After 5 minutes, replace the battery, turn on the device and try connecting again.
- Remove applications that failed after installation. If the connection doesn't work in a particular sync app, clear its cache. If it doesn’t help, reinstall (both on your mobile device and on your PC) or try using an analogue.
- Scan your device with an antivirus.
- Reset the device's operating system to factory settings.
The culprit of the failure is the computer. What to do?
- Shut down the OS, turn off the PC from the outlet (or press the key on the power supply) and hold down the power button for 15-20 seconds. This will discharge the capacitors and remove stray static charge, which may block detection of the connected device.
- If the phone is not recognized by only one group of USB ports, open the cover of the system unit and make sure that they are connected securely. By the way, normal charging of a mobile device through the port does not mean that the second one is working properly.
- Boot the operating system. Open Device Manager and check if portable devices are listed in the equipment list, and your phone is among them. If it is present, but marked with a black arrow in a circle (disabled), right-click on the line and select the “Enable device” command from the menu.
- If there are unknown devices in the equipment list (indicated by an exclamation point in a yellow triangle), one of them may be the phone. To make sure it is him, disconnect your mobile device from USB. If the unknown device disappears from the list, then that’s it. And the reason for the failure is the lack of the required driver in the system. We will tell you below how to reinstall and where to download the driver for your phone.
- The problem with recognizing connected devices may also be due to boot failure, damaged or missing USB drivers. In this case, the exclamation marks will be in the “USB Controllers” section.
- Reinstalling drivers didn't help? Scan your computer disks with an antivirus and then temporarily disable security programs. By the way, the latter can block access to a mobile device as a storage medium if it contains suspicious or clearly malicious software. So it’s worth checking your phone for viruses too.
- Uninstall the programs whose installation caused the problem, or perform a system restore to a checkpoint created on a day before the problem occurred.
- If, in addition to the phone, the computer does not recognize other devices connected via USB - a mouse, keyboard, printer, flash drives, etc. (whether they are charged or not is not indicative), the source of the failure may be any faulty component of the system unit or something then from the periphery. You can determine the culprit at home by turning off the equipment one by one or replacing it with a known good one.
How to Reinstall Mobile Device Driver and USB on Windows Computer
iPhone
- Connect iPhone to PC.
- Open the folder %CommonProgramW6432%\Apple\Mobile Device Support\Drivers (to avoid typing the command manually, copy it from here, paste it into the address bar of any folder and click the go button). It contains 2 files (out of four) with the .inf extension - usbaapl.inf and usbaapl64.inf.
- Open the context menu of each of these files and run the “Install” command.
- After installation, restart your computer.
Android
Smartphones and tablets for Android, such as Samsung, Xiaomi, Lenovo, Meizu, HTC, etc., as a rule, do not create separate folders for storing their drivers, and they are often not found on official websites so you can just download and reinstall. Therefore, to begin with, you should trust the reinstallation of the drivers already present in the system by Windows itself.
How to do it:
- Open the context menu of the problematic device in Device Manager. Select the "Update Driver" option.
- In the next window, first select automatic search for updates. If Windows does not find anything suitable, check the second item - installing and searching for drivers manually.
- Next, click “Select from the list available on your computer.” A new window will display all mobile device drivers that are already installed on the PC.
- To narrow your search, in the “Select a driver for this device” section, check “Compatible only.” Check the one that best suits your request (if there is more than one item in the list) and click “Next” to proceed to the installation.
For the driver to work correctly, restart your computer.
If reinstalling the driver already installed in the system did not help, you will have to look for something else on the Internet (with the risk of downloading a virus instead of the one you are looking for), so download them only from reliable and trusted sites, like w3bsit3-dns.com, and check with an antivirus before installation.
Drivers for the most common models of mobile gadgets are also collected in the “USB Drivers for Android” application, which is available for free download on Google Play.
USB drivers for Windows can usually be easily found on the websites of laptop or desktop PC motherboard manufacturers. Sometimes they are included in the chipset driver.
If the phone is not recognized in firmware mode
The fact that the computer and phone do not see each other in fastboot mode is indicated by the message “Waiting for device” that appears in the firmware program. Most often, this error occurs due to the lack of a mobile device driver in the system, so first of all, do what is written above - reinstall the driver or download and install it again.
If it doesn't help:
- Make sure that you follow the instructions for working with the firmware installation program exactly and that it is running as an administrator.
- Check if USB debugging is enabled on your smartphone (if not, enable it), and the device itself is in bootloader mode. If this mode is blocked, find instructions online for unlocking the bootloader specifically for your device model.
- Connect the phone to the rear USB socket as short as possible and with a known good cable, without using any adapters or hubs.
- Your phone may not support USB 3 (blue socket), so only connect it to USB 2.0 (black sockets).
- Install all released Windows updates on your computer.
If the problem persists even after doing this, try flashing the phone on another PC. And better - with a different version of the operating system.
When the problem is a broken physical interface
It is advisable not to use faulty physical interfaces, especially on a mobile gadget, at all (do not load them with current to avoid worsening the breakdown), even if the phone or tablet retains the ability to charge through them. You can organize content transfer either wirelessly (Wi-Fi, bluetooth) or through cloud services that are available on both devices. In particular, iTunes and iCloud for Apple technology, Google Drive, Yandex Disk, Dropbox, Microsoft OneDrive and many others - for everyone.
Cloud services are convenient to use for transferring photos, videos, music, documents and other types of files. To synchronize contacts on Android and PC, the capabilities of Gmail are sufficient. And to control your phone directly from your computer, you can install an application like MyPhoneExplorer (consists of 2 parts - for the phone and for the PC), which supports both wired and wireless connections of devices without requiring driver installation. Very comfortably.
In short, there is always a way out and it is often much simpler than it seems at first glance.
A fairly common problem in Android is the waiting for device error when working with ADB or Fastboot, in this article we will learn how to fix it!
What is this waiting for device?
This error is not really an error, if we literally translate this phrase - waiting for the device to connect. That is, when you try to do something in ADB or FASTBOT and you get the message waiting for device in the command line, it means that your Android smartphone or tablet is not visible!
Message - adb or fastboot does not see the connected Android device!
To make it clear what this article is about and to understand what we are talking about, it is advisable to read the following articles:
- Otladka via USB
Although almost all the reasons for the message are solved in the same way, for convenience, the article will be divided into the solution “waiting for device in adb” and “waiting for device in fastboot”.
Solution waiting for device in ADB
1. The first thing you should pay attention to is whether you have the driver installed?
You can download the driver here page how to install find out on this link. If the driver is unsigned, then Windows must be restarted by disabling verification. Certain devices require a special ADB driver.
Have you installed the driver? Restart your computer!
2. Make sure that the device is in bootloader mode, otherwise fastboot will not see your Android!
3. Use an original and undamaged microUSB cable! Everything should be clear here, if the cable is damaged, hence the visibility problem, perhaps you can transfer or receive files from this cable, but you won’t be able to work with Fastboot! Also, do not use a damaged USB port on your computer!
4.Use only USB 2.0 port! Despite the fact that the USB 3.0 standard has already existed for several years, it is still too early to talk about large-scale implementation. Fastboot working with USB 3.0, although possible, is still not desirable!
5. Do not use USB hubs! Never, under any circumstances, use USB hubs; working with Fastbot becomes like luck - you'll be lucky or unlucky.
7. Try connecting Android to a different USB port.
9. Open a command prompt as “administrator”.
If you once had a similar problem “waiting for device” and solved it in your own way, not from the methods listed, then do not hesitate to write in the comments!
That's all! Read more articles and instructions in the section. Stay with the site, it will be even more interesting!
Question: ADB does not see the device
Hello. So I decided to test the application on a real device. But as in most cases, ADB does not see the device. The computer sees the device, developer mode is turned on. In all connection instructions it says that Manage should have Android Composite ADB Interface, I don’t see it in mine. What am I doing wrong? I am attaching a photo of Manage
Answer: Thanks for the answer, I already figured it out. I turned off the device, turned off debugging and turned it on again. Then I connected the device again and everything worked
Question: Genymotion: When launching an application from AS, virtual devices are not displayed
Hello,
Android Studio does not see the Genymotion device((The plugin is installed in Studio. Through Genymotion the device starts, but when you start the application only the built-in device appears, and I don’t see the Genymotion device(In the Geny settings I set the path to the sdk folder, and that didn’t help(What can be a reason?
Answer:
Message from Pablito
literally
- launch the device in gemymotion
- we look in the studio - you can see him
- start the application
I'll check it and report back!
Question: Android SDK does not recognize the device
I'm trying to run a project on my Chinese tablet (Go clever insigma 800m), is it possible that this is due to the fact that the compile SDK in the project is installed 5.0 and on the tablet 4.2 but the min and target SDK are installed as 4.2. Developer mode is enabled, USB debugging is enabled. When I try to reduce complie sdk, a compilation error occurs "R" -cannot resolve symbol, after build\\clean it points to a system file with errors around the material of the themes, Please help
Answer: Are all devices detected normally in Device Manager? If not, install Composite ADB Interface for your Android tablet
Question: Resetting the device descriptor request in fastboot mode
Here's the thing. One day my Google nexus 7 2013 wifi froze and did not freeze. I, of course, held the shutdown button for about ten seconds until he finally died. When I tried to turn it on, I was surprised to find that it was stuck on the screensaver, and the Android system itself did not load (the screensaver with the inscription Google and the icon of the unlocked bootloader). I switched to fastboot and decided to go into the recovery menu, but that didn’t help either. Same problem. Hangs on the screen saver. Okay, I decided to just flash it through fastboot. But here's the problem - windows 8.1 x64 defines the device as "Unknown device (reset device descriptor request)". Code 43. And then I grabbed my face, because I had a similar problem before, but it somehow resolved itself.
I scoured the Internet, rearranged the adb/fastboot drivers, unchecked the checkboxes in the menu for powering the usb ports, downloaded the kb2967917 update, turned off the laptop so that the static electricity went away. Nothing helps. I have no idea what the problem is.
1) USB cable from Lenovo p780, which has a 2A/h power supply, maybe this is the problem?
2) Perhaps the adb/fastboot drivers are sloppy, how can I find out if this is the problem?
3) I connect the tablet in fastboot mode, because there is no other way. USB debugging seemed to be turned off before the incident, maybe that’s the problem?
I don’t understand this matter very well myself, so I’m asking for your advice.
Answer: No, the fastboot does not see it, nor does the computer itself.
The fact is that literally the day before yesterday I was already in despair, because many people promised me that my memory had died, and I decided to take it apart and see what happened inside.
He opened it, ran his finger along the trains to make them fit snugly, and OH MIRACLE! after that he turned on.
Apparently the cable has left the memory, I don’t know what or how it works inside.
It is noteworthy that a couple of years ago I encountered a problem with phantom clicks when the device heated up from heavy applications. I also took it apart, poked my finger at the cables and the phantoms disappeared.
Question: The tablet does not see the USB drive via OTG
Lenovo A5500-H tablet. One day the tablet didn’t want to see the USB flash drive, although everything was fine before, and I decided to reboot it, but in the end it wouldn’t turn on. I did a hard reset and after that it turned on, but the USB drive still doesn’t see it at all. Tell me what to do?
Answer: I haven’t tried it on other devices, but I bought myself a flash drive with two usb and micro usb inputs and it doesn’t work either.
Added after 1 minute
Added after 27 seconds
I haven’t tried it on other devices, but I bought myself a flash drive with two usb and micro usb inputs and it doesn’t work either
Question: The studio does not see the phone
There is a device LG L90 Dual D410 and when it is connected, the studio does not see this device for debugging (It is not in the list of available devices). What should I do? How to install drivers for it and where to get it?
Answer: yura91, in the sense that “how many devices are supported by the same driver” is not a completely correct question for those who have been looking at this issue for a very long time)
Question: ADB does not see meizu m1 note
ADB does not see meizu m1 note, and this makes me very sad. The driver doesn't see it. What to do?
on ADB devices answer:
List of devices attached
Here is a screenshot of the device manager:
What did you do:
;M79
%CompositeAdbInterface% = USB_Install, USB\VID_2A45&PID_0C02&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_2A45&PID_0C02
%CompositeAdbInterface% = USB_Install, USB\VID_2A45&PID_0C02&MI_01
Answer: Windows 8 doesn’t see my Chinese either. I use PdaNet.
Question: There is not enough space on the device
Can you tell me why, after the play store is automatically updated and I try to install the application through it, the error “There is not enough space on the device” appears, although there seems to be enough space judging by the memory indicators in the settings. And after I delete the play market updates, you can install the application. Why does this happen?
Answer: It could be whatever the phone developers came up with.
I've seen such models. but can you use music or photos from the map?
the same question again: if you remove the card, does Phone Storage and Internal Storage not turn off? Can you copy something on them and view the structure? Or does one of them stop working when you pull out the card?
Question: Organizing direct network interaction between devices
Hello.
Subject For example, for media communications.
Considering that the addresses of mobile devices are dynamic and change every session, it is clear that an intermediate server is needed. There are several questions:
1. Is it possible to use the server only for updating addresses (client applications connect when opening or changing a network connection and inform the server of their current IP address) and further data exchange occurs directly between clients?
2. In applications like Skype (or any other well-known product, such as whatsapp, viber, etc.), does streaming traffic go entirely through the server or between clients? Does anyone know how this is implemented?
3. Not good at socket communication, so the question is ip. If several devices are connected to one router, then their external address is the same (at least, various services for determining ip told me this). How then do servers (google firebase or the same instant messengers for example) find the desired device?
I'm probably missing something in the routing.
Thank you.
Answer: GDjedi, the packet contains source and distantion, source is then returned back, and this changes from router to router and the final server does not actually know about your mac or ip or port, everything along the chain.
I can’t go into more detail, I’m afraid I’ll make a mistake and confuse you.
I have approximately the same task, to connect 2 devices with each other, I came to the conclusion that I need a VDS, through it I will connect 2 phones/tablets, the server is an intermediary between them.
Question: The application displays an error if GPS is disabled on the device
The application determines the coordinates, then determines the city using the coordinates. But, if you turn off the GPS on the device, the application crashes. How to correctly create a listing so that if the GPS on the device is turned off, the application will not crash, but the activity will simply start without identifying the city.
Here's the listing:
|
||
By the way, without the following section of code, the application does not crash, but, unfortunately, it does not detect the city.
| Java(TM) 2 Platform Standard Edition 5.0 Code | ||
|
||
Answer: How can I include this in the listing?
Added after 15 minutes
I did this check. When the coordinates on the device are determined only by GPS (without wi-fi and networks), the application receives coordinates 0.0. That's probably why it crashes. But how to fix this?
If you use a phone that runs on the Android operating system, you should know that there is a huge field for customization, or, in popular parlance, customization. In most cases, you will probably not be happy with the firmware of your device. If you perform incorrect manipulations, you can stop the device from working in such a way that only professionals can restore its functionality.
To prevent this from happening, you should use fastboot mode. What it is? On Android devices, this mode was added for developers. A literal translation can be given if you break the word into its components: fast - “fast”, and boot does not have exact analogues in Russian, but is roughly translated as “loading”. Fastboot mode allows you not only to install new firmware, but also to reset your phone settings to standard values (which is extremely useful if you forgot the password to your own device and accidentally locked it).
Basic information
In general, this mode is most often used by developers as alternative to recovery mode. It is also extremely important to realize that not all devices support this feature. If your smartphone has this capability, you can enable this mode even before the phone boots, which simplifies the process of installing firmware or resetting settings.
Preparing a personal computer
If you are using a fastboot, you must connect the device to your computer via a USB cable. Using bios you can understand whether the device is recognized by the computer. After this you can start installing new drivers on your device. It is recommended to do this in this order:
Enabling fastboot on different devices
In the future, you should find out exactly how this mode is turned on on your phone. For example, we will take phones from two Chinese manufacturers: meizu and xiaomi.
- In phones that were developed by Xiaomi, you need to simultaneously hold down two buttons with the phone turned off: power and volume up. This will bring up a menu in which there will be an item indicating the mode we need. As soon as you click on the required button, you will be taken to it.
- In order to get into this mode using a phone made by Meizu, you must do similar steps, but this time you will need to hold down the Volume Down and Power buttons. And entering this mode takes a little longer than in Xiaomi phones - you will need to hold these buttons down at the same time for about 15 seconds.
For further manipulations, you will need to connect your device to a computer or laptop. It makes absolutely no difference whether msi or other companies made the parts for your computers. If your computer is running a Windows operating system, you can control your phone via USB.
Control commands
As soon as you use the previously opened fastboot debugging program and enable the same mode on your phone, you will be able to use commands to achieve the desired result. Below is sample list of commands:
It's also worth mentioning that you won't notice the difference using a phone or tablet: if your device uses the Android operating system, then you'll most likely be able to use this fastboot.
