I can't connect to my phone with ADB. I've tried with SE's adb drivers and the ones from Android SDK, but none of them work, it starts the daemon but it's unable to recognise any device.
I'm on Android 2.1 with "USB dbg" enabled. My system is a XP64 SP2 with the correct drivers. Any ideas?
_SpAiK_ said:
I can't connect to my phone with ADB. I've tried with SE's adb drivers and the ones from Android SDK, but none of them work, it starts the daemon but it's unable to recognise any device.
I'm on Android 2.1 with "USB dbg" enabled. My system is a XP64 SP2 with the correct drivers. Any ideas?
Click to expand...
Click to collapse
Does it not recognise it at all or will just not mount?
I can mount it, but if I type "adb devices" in cmd it returns a blank list. I've switched of my firewall and antivirus, but it does not resolve anything. I've seen that when running adb, it loads two instances of adb.exe and then kills one, also when trying to root with SuperOneClick it loads and maintains two instances.
I've had trouble with it most of the day but seem to have sorted it now, but it does show with adb devices for me so not sure.
Once you update to 2.1, you need to update the drivers.
The easiest way is to install Sony Ericsson's PC Companion (and update): http://www.sonyericsson.com/cws/support/softwaredownloads/detailed/pccompanion/xperiax10
I was wondering about this too. Sony Ericsson Update Service would detect the phone in flash mode, but not ADB or SuperOneClick. Once I installed PC Companion, it was fine.
Check your Device Manager. I'd bet you have a yellow exclamation mark.
Hi,
I need help to get ADB working on my PC with the Galaxy S2.
I have installed the drivers coming along Kies, I think under sub folder "25_escape".
The drivers appear correctly as "Samsung ADB interface" under the device manager.
When I run "adb devices" I get the following logs
>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
** daemon still not runningerror: cannot connect to daemon
I'm wondering if it is a driver issue, or something else.
I have several other android phones that are working just fine (HTC, Motorola, Samsung Galaxy S1 even works) but that issue is happening on the Galaxy S2 (and Tab 10.1 as well).
Help is really appreciated!
Thanks!!
Hi.
Busy rooting my new S2.
Problems with SuperOneClick because of ADB drivers.
- download + install Kies from the Samsung site
- run Kies and select Tools / Install driver
This worked for me !
Good luck.
Are you using USB or ADB wireless?
Ian
I have installed the drivers, but it did not help. It seems that either ADB is crashing when I run any command, or its connection to the device fails in some ways.
I am using a regular USB connection.
Any idea?
thanks!
Ok.
Do you use ADB from the Android SDK platform-tools directory ?
Which ADB version are you using. i got 1.0.26
>adb version
Android Debug Bridge version 1.0.26
Older version ? upgrade the SDK.
Otherwise, give Wifi ADB a try.
Install it and connect with : adb connect <host>:<port>
good luck, Bromco
I promise that I've combed through threads and I know google is my friend but i swea to freekin god I'm stumped.
I cant get adb devices to list my device.
I'm running WIN 7 x64
I have:
installed and reinstalled drivers. Device manager shows my device as working properly when connected. It is listed as HTC6435LVW under Portable devices.
I even installed HTC sync and it finds my device just fine.
I have my DNA set to USB debugging mode on.
But when I go to a command prompt and run adb devices it says
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
and thats it. nothing listed.
If i run it again I just get
"List of devices attached"
still nothing listed
can someone tell me what i can try next?
Thanks
pda net
jayba420 said:
I promise that I've combed through threads and I know google is my friend but i swea to freekin god I'm stumped.
I cant get adb devices to list my device.
I'm running WIN 7 x64
I have:
installed and reinstalled drivers. Device manager shows my device as working properly when connected. It is listed as HTC6435LVW under Portable devices.
I even installed HTC sync and it finds my device just fine.
I have my DNA set to USB debugging mode on.
But when I go to a command prompt and run adb devices it says
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
and thats it. nothing listed.
If i run it again I just get
"List of devices attached"
still nothing listed
can someone tell me what i can try next?
Thanks
Click to expand...
Click to collapse
One thing that worked for me was to install pda nets drivers (google pdanet and it should be the first thing that comes up) it will ask you if you want to replace current android usb drivers and you tell it yes. Hope this helps!
jayba420 said:
I promise that I've combed through threads and I know google is my friend but i swea to freekin god I'm stumped.
I cant get adb devices to list my device.
I'm running WIN 7 x64
I have:
installed and reinstalled drivers. Device manager shows my device as working properly when connected. It is listed as HTC6435LVW under Portable devices.
I even installed HTC sync and it finds my device just fine.
I have my DNA set to USB debugging mode on.
But when I go to a command prompt and run adb devices it says
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
and thats it. nothing listed.
If i run it again I just get
"List of devices attached"
still nothing listed
can someone tell me what i can try next?
Thanks
Click to expand...
Click to collapse
Remove HTC sync, this should solve your problem. Also try a different port and reboot your computer.
If neither of these works then resinstall ADB you might have a dated version allthough that would NOT prevent it from functioning entirely
http://dl.google.com/android/installer_r21-windows.exe then choose download platform tools once the sdk opens.
I am on win7 x64 and have had 0 problems.
Good luck!
make sure the usb port you're using is 2.0 and not 3.0
it may be something as simple as that as well.
jayba420 said:
I promise that I've combed through threads and I know google is my friend but i swea to freekin god I'm stumped.
I cant get adb devices to list my device.
I'm running WIN 7 x64
I have:
installed and reinstalled drivers. Device manager shows my device as working properly when connected. It is listed as HTC6435LVW under Portable devices.
I even installed HTC sync and it finds my device just fine.
I have my DNA set to USB debugging mode on.
But when I go to a command prompt and run adb devices it says
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
and thats it. nothing listed.
If i run it again I just get
"List of devices attached"
still nothing listed
can someone tell me what i can try next?
Thanks
Click to expand...
Click to collapse
Thank you guys.
It was both using PdaNet to reset the drivers and also switching to USB2.0 ports that did the trick. Thank you for the help.
adb now sees my device Yay!
jayba420 said:
Thank you guys.
It was both using PdaNet to reset the drivers and also switching to USB2.0 ports that did the trick. Thank you for the help.
adb now sees my device Yay!
Click to expand...
Click to collapse
I am having the same issue. Which manufacturer did you select when you installed pdanet. I am stuck on the skip usb driver installation dialog. Have enabled usb debugging n all but it still can't detect my device.
Hi, I have already had my USB debugging enabled and from my device manager I can see my device there showing "ASUS Android Devices" > "Asus Android Composite ADB Interface".
But when I reboot my tablet as USB mode and from my laptop I run cmd as Administrator, and run "adb devices" command, it just show me "List of devices attached" and then the command prompt.
I have already unlock and rooted my tablet.
Why I can't see my device id ? Please help
Try: Connect/disconnect device from USB. Kill adb server (adb.exe) from DeviceManager, and then run "adb devices" again. Also make sure that correct USB drivers are installed for your device.
knutson said:
Try: Connect/disconnect device from USB. Kill adb server (adb.exe) from DeviceManager, and then run "adb devices" again. Also make sure that correct USB drivers are installed for your device.
Click to expand...
Click to collapse
Yeah this process is correct. Even I've experienced this.
What I did is:
Removed the USB cable connection and reconnect.
Kill adb.exe
Restart adb.
Then device was shown to be connected.
knutson said:
Try: Connect/disconnect device from USB. Kill adb server (adb.exe) from DeviceManager, and then run "adb devices" again. Also make sure that correct USB drivers are installed for your device.
Click to expand...
Click to collapse
Yes, I did that but still the same. Any other suggestions?
If on windows make sure your driver's are installed.
Type in cmd
adb kill-server
adb start-server
If that doesn't work try a different usb slot. You could also try moving adb and it's dependencies to your system32 folder. It's where all your commands are stored for cmd. You won't have to navigate to the android sdk tools.
Sent from my SPH-L710 using Tapatalk 2
Have you enabled Debugging on in your phones Developer settings?
ngaisteve1 said:
Yes, I did that but still the same. Any other suggestions?
Click to expand...
Click to collapse
it's so easy, just turn off your android device, then hold down both "Volume Down" key and "Power" at the same time, wait a few seconds till it start in recovery mode, done.
now type adb devices, and you'll see your device.
no need for that.
close any adb process either from task manager or by typing: "adb kill-server" in adb console
close everything and use this customized adb file I attached, it'll show your device.
it also has instructions and necessary files for rooting your device.
Problem
knutson said:
Try: Connect/disconnect device from USB. Kill adb server (adb.exe) from DeviceManager, and then run "adb devices" again. Also make sure that correct USB drivers are installed for your device.
Click to expand...
Click to collapse
I have LG Optimus G (E975) i wipped all from the device and now i can't put cm11 on it, adb sideload do not work, and list of devices attached is empty. what must i do to put CM11 on my phone?:crying:
I'm having the same issue but I have a ! triangle on my Nexus 5 under Other Devices. Any suggestions???
I have the same issue on my nexus 4. Yesterday it showed up with adb devices, now it's an empty list. I have USB debugging enabled and tried restarting the server. Nothing works. Any ideas?
ldemon360 said:
I'm having the same issue but I have a ! triangle on my Nexus 5 under Other Devices. Any suggestions???
Click to expand...
Click to collapse
unplug the device and adb kill-server then replug the device and try
turn debugging off and then on again
I had the same problem. In my case, i had forgot to enable usb debugging after new rom.
ngaisteve1 said:
Hi, I have already had my USB debugging enabled and from my device manager I can see my device there showing "ASUS Android Devices" > "Asus Android Composite ADB Interface".
Click to expand...
Click to collapse
In your case just disable USB debugging and then enable again.
fix the driver
I had this issue.
In my case when I went to device manager I could see the Device and wasn't installed correctly and could not load the drivers even after having installed them on the PC.
SO I clicked update drivers.
Select that will chose the drivers to install and select the Android Devices - ADB driver.
You will get a warning, but just ignore it and load the ADB driver for the phone.
Ensure you are in the sideload option of the recovery
Now
adb devices
it should show up as Sideload
Now sideload
Cheers
Dirk
knutson said:
Try: Connect/disconnect device from USB. Kill adb server (adb.exe) from DeviceManager, and then run "adb devices" again. Also make sure that correct USB drivers are installed for your device.
Click to expand...
Click to collapse
Thanks, this worked for me.
Just add ur device id in adb.ini
Same issue was faced by me on my micromax Q334 and xolo era, I search lot for that and finally just adding hardware id the device are detected under adb.The steps are clearly shown in my video below..
It will definitely going to sort this problem..
For that just right click on adb driver ,navigate to detail tab and search for hardware id then add to adb.INI
I have also uploaded video on that YouTube: Fix adb connection issue(Adb driver installed, but device not listed)
device listed as "? recovery"
hey,
am trying to connect honor 6(h60-L04) but am not able to see the proper name for my device is just showing "? recovery" and am trying to update the android version coz of the device is in reboot-loop so help me out here
if there is any other option to recover device give me link.
knutson said:
Try: Connect/disconnect device from USB. Kill adb server (adb.exe) from DeviceManager, and then run "adb devices" again. Also make sure that correct USB drivers are installed for your device.
Click to expand...
Click to collapse
not work my friend, the list of devices is empty
Put your phone in PTP mode... just found this. When it was on charge or MTP nothing would connect, but when it was in PTP adb.exe said "error: device offline", but on phone it asked if I wanted to trust the computer!!! Ohhhkay, now we're getting somewhere. Clicked trust and ran adb devices and there it is
See below... I found there are two versions of adb.exe I was using. PTP is not the problem, but adb.exe has to be the right one or it just says offline.
vern.zimm said:
Put your phone in PTP mode... just found this. When it was on charge or MTP nothing would connect, but when it was in PTP adb.exe said "error: device offline", but on phone it asked if I wanted to trust the computer!!! Ohhhkay, now we're getting somewhere. Clicked trust and ran adb devices and there it is
Click to expand...
Click to collapse
ALSO!! Get the newest driver pack from LG "LGMobileDriver_WHQL_Ver_4.1.1". The driver packs in the roots that I downloaded aren't new enough. After Windows got the right drivers I was able to see the COM ports properly.
I'm not sure if I have the root working currently. The "Newest root method V03" where you click on root.bat seems to pick the wrong COM port. When I try to do it manually with Send_command.exe using the other COM port it seems like the root process doesn't work properly. It eventually completes, but no info about what it did etc.
I'm using an LG Transpyre VS810PP with Android 5.1.1 currently, and a Windows 10 64-bit machine.
Alright, I've tried installing the drivers from Verizion and also using the drivers from the Android SDK and either way I have the same problem. ADB devices shows my phone, however whenever I try to push, pull, or reboot (the only commands I have any use for atm) the command prompt hangs like it's trying to access the device but no matter how long I leave it the device will not reboot, nor will any files appear in the correct folders on either the device or my computer.
I'm trying to root my phone and this is a pretty major roadblock.
Note:
USB Debugging enabled
ADB drivers installed
Phone shows up on "adb devices"
There is no error or any other output in the console. The best way to describe this problem is that ADB hangs.
I'm running Windows 8.1 and my phone is running Android 4.1.2
Also, I don't know if this is normal but, In order to get the notification that "USB debugging connecting" I have to use the internet connection option on the phone. When using MTP, Charge only and PTP that message doesn't appear and I don't see an ADB device show up in device man.
Things I've Tried
Uninstalling all Android drivers and redownloading/installing them after restart
Restarting my phone multiple times
Running adb kill-server / adb start-server
Changing USB ports7
Thanks!
Try installing drivers from LG. This seems the right one but double check:
http://www.lg.com/us/support-mobile/lg-LGVS930