[Q] Can't get ADB to work for Galaxy S2 - Galaxy S II Q&A, Help & Troubleshooting

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

Related

[Q] ADB Refusing to work

So I'm here ripping my hair out because ADB seemingly refuses to work. I have r14 of the Android SDK installed (and java), my tablet even shows up as an "Android Debug Bridge Interface" in Device Manager, but no matter what I do I cannot get ADB to connect to it.
I've tried on both x86 and x64 Win7, using the r4 USB driver. Everything from Tools, Extras and Android 2.3.3 (the version of VeganTab I'm running is 2.3.5, but I'm guessing there weren't many major changes) in the SDK Manger is installed.
What am I doing wrong? USB Debugging is enabled in settings, and the little debugging icon shows up whenever I connect via USB, but even if I run ADB as Admin, it just doesn't find anything.
Starting ADB with "adb usb" shows this;
Code:
E:\Android\android-sdk\platform-tools>adb usb
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
E:\Android\android-sdk\platform-tools>
I don't get it. I've even tried disabling my firewall. I'm simply out of ideas.
Well, I've gotten ADB to work over wifi using Remote ADB from the market.
I still have no idea why it's not working over usb... Nvflash works just fine (mind you, that's APX mode).
Any ideas are greatly appreciated.

[Q] Drivers & adb troubles, a little help

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.

Android ADB Devices Empty List

Hello XDA-Developers,
I have a problem
I have an android phone Jelly Bean 4.1.2
I already installed the drivers of my phone to my computer, when i plugged the cable i enable USB DEBUGGING.
after that i checked device manager and my phone is listed under Android Phone
After that i go the console and type adb devices it starts the server and returns an empty list
i tried everything
i also try kill-server and start-server still the same
PLEASE HELP
then
Maybe try a different usb slot. One directly on the motherboard, it sometimes helps.

[Q] [LG VS930] Unable to get ADB commands to work

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

Gear s not showing up in adb devices on windows 10

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

Categories

Resources