I had previously connected my Asus X00TD to my laptop for transferring files. The phone doesn't connect to PC from yesterday. Only charging happens after connection, and device doesn't show up on the device manager(no change on list of devices after connection), and no notification sound of device being connected either. There is no notification in my phone as well. Here are the following workarounds I have tried, but failed:
Changing USB cable
Changing PC/laptop
Installing ADB and Qualcomm drivers and again uninstalling them(error code 10 on ADB Driver)
enabling and disabling USB debugging
changing connection mode(nothing works)
Going into safe mode
restarting and connecting multiple times
Kindly help me if possible, and your help will be kindly appreciated
I had a similar problem recently. What ended up working for me was to install some generic Android driver published by Google. I already had the ADB package installed, but without the generic Android driver published by Google, my phone could charge and transfer files, but I could not issue ADB commands through the Windows command prompt.
The package I needed was called "usb_driver_r13-windows.zip"
Related
I can't for the life of me connect to my TP2 running XDANDROID via ADB.
Here's what I've tried
-Connect via Linux in a VM(Ubuntu)
-Connect via Linux (for real, also Ubuntu)
-Connect via Windows.
The problem is the connection to the phone. In Linux, the USB0 network connection does show up, but when I try to connect to it, it fails everytime without any specific error message.
On Windows, I managed to install the Android SDK USB driver, but once again ADB can't seem to connect.
The error message is the same on both platforms btw. When I try to run adb shell, it starts the Daemon and then quits saying that there is no device to be found.
The phone itself indicates it's in USB debugging mode and the USB cable is connected.
What could I be doing wrong?
Whoops, wrong subforum. Could a mod please move this to 'Software and Hacking General'?
My Win10 Insider Preview machine did not recognize the phone. Nothing happened when I connected the phone and I could not access storage of the phone.
Below is the solution for it:
Go to Control Panel - Device Manager - LeMobile Android Device (could be under a different name. Choose the one that is your phone) - Update Driver - Manually Install a Driver - Let me pick a list of available drivers on my computer - MTP USB .
4K2K said:
My Win10 Insider Preview machine did not recognize the phone. Nothing happened when I connected the phone and I could not access storage of the phone.
Below is the solution for it:
Go to Control Panel - Device Manager - LeMobile Android Device (could be under a different name. Choose the one that is your phone) - Update Driver - Manually Install a Driver - Let me pick a list of available drivers on my computer - MTP USB .
Click to expand...
Click to collapse
Uhm ... when you connected the phone to computer you changed the mode on phone from USB charging to MTP mode ?
In my Win10 x64 build 14392.447 not problem to see the phone in MTP mode after changing mode on phone.
Alternative solution is to use KDE Connect app over Wifi. Bonus is that once set up, it is possible to push files from the phone to the PC without any interaction on the PC side - e.g. useful if the PC doubles as a file server.
losteagle said:
Uhm ... when you connected the phone to computer you changed the mode on phone from USB charging to MTP mode ?
In my Win10 x64 build 14392.447 not problem to see the phone in MTP mode after changing mode on phone.
Click to expand...
Click to collapse
Both of my home & works computer (Win10 14959) failed to detect it as MTP or PTP drive. Might have been due to those having previous phone's drivers.
But I faced same problem with fresh out of the box Win8 laptop.
No issue with the MTP, however I can't seem to get adb to work. list of devices attached is showing empty.
ksj0823 said:
No issue with the MTP, however I can't seem to get adb to work. list of devices attached is showing empty.
Click to expand...
Click to collapse
I had the same issue, i reinstalled minimal ADB and removed the drivers from my pc, rebooted my pc. Plugged the phone into a different USB port and voilá ADB could see it
Citroon said:
I had the same issue, i reinstalled minimal ADB and removed the drivers from my pc, rebooted my pc. Plugged the phone into a different USB port and voilá ADB could see it
Click to expand...
Click to collapse
Wanted to add my voice here too that I did the same - I had to clean up previous drivers I had installed over time for varios phones and different ADB versions like the one from clockworkmod - once I cleaned that out and installed google drivers from SDK PTP worked and I was able to do Helium restores
I had issue on my Win10 PC, but I found that after I disabled USB debugging, it would work as MTP/PTP, but not for ADB of course. So apparently, I have to toggle USB debugging ON/OFF to switch back and forth from MTP and ADB.
Small pain in the butt.
Solution.
I had the same issue. Drove me NUTS for about an hour. In the end, simply unchecked the USB DEBUGING in developer settings. This will make it pop up immediately.
Update:
I clearly should have read the post above mine first.
I downloaded latest ADB/Fastboot package to my Win 7 PC.
I installed the Zadig drivers exec to load drivers (as seen in another thread).
Enabled USB debug
Connected phone
ADB devices ... doesn't show phone
Phone shows ADB icon in task bar
In device manager I can see libusbK USB Devices .. ADB Interface (Interface 1) .. when I plug the phone in
I have revoked previous computers and rebooted both PC and phone with no changes
... now I am a bit lost
* Bump * .. I can't do much without ADB ... could someone at least point me to the correct drivers - what I have downloaded from Zadig do't seem to work.
I'm currently having the same problem of not being detected when I type in "ADB devices" in Windows 10 after an auto-update which can't be stopped screwed up my drivers. I found this thread while searching for an answer myself. I tried reinstalling all Qualcomm and fastboot drivers and even though my phone can be detected in Windows again (after manually selecting "MTP USB Device" as a driver update for the A7 in the device manager) I still get nothing when I type in ADB devices. Though I tried flashing something to it anyway (same TWRP recovery I already have since the file was already there) and it seemed to work? Have you tried flashing something to your phone anyway?
Here's the situation. LG G6 us997, oem unlocked but not rooted. USB debugging is enabled and File Transfer (MTP) is the selected mode.
When I connect via USB to my MacBook pro (running osx 10.12), I am able to use adb to connect to my phone (push/pull files, etc). I am also able to connect to LG Bridge to initiate wifi file transfer (i.e. it recognizes my phone via USB).
However, when I open Android File Transfer it gives me a No Device Found error. If I switch the USB mode on the phone to "charging" and open AFT, I am given an error that suggests it sees the phone but knows it's not in File Transfer mode. It tells me to switch to MTP and reconnect, but then I again get the No Device Found error.
Here's the really strange thing. I performed two experiments. First, I plugged my G6 into another Mac (a mini) that had Android File Transfer installed, and instantly the file explorer popped up, working perfectly. That suggests to me that my cable isn't bad, and that my phone settings are probably okay.
But then I plugged my friend's Samsung Galaxy S6 into MY computer, and Android File Transfer popped open as it should, working perfectly. I'm not sure what this suggests. The weird thing about THAT is that plugging that same S6 into the afformentioned Mac Mini does NOT work!
So I'm stumped. I can always push/pull files via adb, but sometimes I want the simplicity of a drag and drop GUI, you know? A little more info: I think LG Bridge and AFT (and LG pc suite which doesn't work) can conflict, so I've definitely uninstalled those applications to minimize variables, rebooting between tests. I've also rebooted my phone between changes, and locked and unlocked it, and toggled File Tansfer to Charging modes repeatedly, and plugged and unplugged the cable, tried different usb ports, and switched cables.
Any ideas?
Not sure If I missed it with searching or if anyone has made a post about this, sorry for repeating.
I just recently bought the Essential phone and for some reason had issues getting the USB debugging authorization to show up. Nothing seemed to fix it, tried numerous cables, usb ports, removed and reinstalled drivers, still nothing.
I realized that there is a file located in C:\Users\Current User Name(whatever the current user is)\.android called adb_usb.ini. It list device IDs of other android devices and for some reason my phone wasn't listed. After adding my device ID (the file just opens in notepad) and saving, I went back to terminal and sure enough my phone got the allow usb debugging rsa key prompt and my phone finally showed up when typing ADB devices.
The device ID is 0x2e17
Also, even though I downloaded the lasted platform tools from google, in order to issue commands in fastboot I need to type fastboot -i 0x2e17
So for example in order to unlock the bootloader I needed to type fastboot -i 0x2e17 flashing unlock. I modified Essentials flashall.sh file and added the device id to all commands in order to get DP4 installed.
Didn't work for me...however windows just gives me an error when i even connect my phone to the PC.
Update: switching usb-c cables DEFINITELY works.
Try another computer will sure fix this, or just install another system like windows 10 or Ubuntu something like that.
I was having problems when i connected my essential phone to the pc and nothing was showing up. After a lot of frustration i decided to plug my usb cable to a usb 2 port instead of a usb 3.0 and that made everything work.
So if you're having problems connecting to the pc try using a regular usb port and not a 3.0 port.