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.
I have a Win 8.1 machine with the HTC drives installed and when I run ADB with the phone booted to the ROM everything is fine. ADB returns the device ID and it is recognized. When I boot into the fastboot, I get fastboot usb but ADB does not recognize the device, I get List of devices attached and then nothing. I have rebooted both the phone and computer, uninstalled and reinstalled the drivers but no luck. Anyone ever seen this behavior?
Please close thread.
Hello,
It is not my tablet and i don't know why it crashed but when i try to turn on the device it stops on producent logo.
Hard reset - not working, recovery mode - doesnt show. At first i could connect it to my computer(without drivers it appeared as "Android") and do stuff with adb. I used a couple of commands from this thread http://forum.xda-developers.com/showthread.php?t=2277765 and now i can't do anything(without drivers it appeared as "usb developer with drivers as "adb interface"), adb shows nothing after adb devices command.
what i can do more or what i did wrong?
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
hi everyone
i have been trying to fix an issue for days with my gear s1 sm-r750a (software r750aucu2apc1) not show up in the cmd adb devices so this is what ive try that has not worked:
reinstalled my samsung and google drivers multiple times
factory reset
my gear s is unlocked as i have a virgin mobile sim inserted and i have made a call that worked
unpaired and paired with a samsung phone
turned on usb debuging on my gear
updating my gear s firmware
updating drivers manually in device manager
15 seconds adb installer
googling it and youtube videos
adb kill-server
adb start-server
adb devices
recovery mode
android sdk software
eclipse software
disable digitally signed driver
updated to the lastest java
restarted my pc multiple times
tried mobilego by wondershare
impactor
odin
vroot
samsung kies
smartswitch pc
naked adb drivers 0.73
universal adb drivers
simple adb installer
tried different usb cables and ports on my laptop
it only shows up if i use cmd sdb which i have installed opera mini using this method
my LG G3 works fine and it shows up in the cmd adb and in android devices and portable devices in device manager where as my gear s only shows up in portable devices. my lg g3 is rooted with Xposed Installer on it. with my gear s im trying to root it but having no success with it. i like the tizen ui but its a real pain in the butt so i can change to android if need be.
if anyone one knows any over way to root or make it show up in cmd adb please help me
thanks for any help