This thread says it's just supposed to work on mac.
I have 'USB debugging' enabled.
I can see virtual devices if I create and start one from eclipse in the device list. But no Galaxy Tab.
On Mac OS X 10.5.6
Wanted to do some Galaxy Tab development, but if this doesn't work I guess I wont. :/
Command I used: ./adb devices
Result:
List of devices attached
I think it was because the device was asleep. Works now.
adb stopped working after upping to gingerbread
I can't get adb to see my galaxy tab (7/sprint) after upgrading to gingerbread.
Anyone know what happened?
Related
Hey guys,
I have been trying to get my phone connected to my pc for a few days now.
I am having major issues with getting adb to work. I have googled pretty much every solution, tried the drivers posted on here, everything.
It seems that turning on USB debugging on my phone does nothing. I get no new notifications in windows (7), no new hardware, no ADB Composite Interface showing up.
I really don't know what to do next - anyone else have this problem?
Are you able to try plugging it into another computer to check the usb interface isn't faulty?
I have tried it on both my work pc (vista) and my home pc, with the same result.
When I type the command adb devices I just get a empty list.
I put it into fastboot mode and was able to get fastboot devices to list the serial, which is why I think theres something wrong with USB debugging mode on the phone.
Would a factory reset fix a problem like this?
Well I have fully reformatted my pc, and restored the phone and still have the same issue.
You have to install the ADB drivers.
I attached the drivers you need.
If you need more help, let me know.
Still not working - I tried the drivers you attached, as well as previously the drivers from the android adk.
I can get a Android ADB Interface to show up in Device Manager, but the adb devices command just gives me a blank list.
Why is it that I only get Android ADB Interface, and everywhere else on the web I see Android ADB Composite Interface?
W7 x64 and using the SDK drivers mine shows up as Android ADB Composite Interface (at the top, in it's own Android Phone category) with USB debugging enabled.
If I boot the phone into recovery mode, i get Android ADB Composite Interface, adb devices lists my phone, and Android ADB Interface is disconnected.
But when the phone is running, the composite interface is disconnected, and the Android ADB Interface is connected, but adb devices lists nothing.
I have just put on cyanogen mod 6 tonight, and its still the same. Is there any other part of the phone that might cause this?
Tonight I tried on my mates pc, it didn't work, but his desire showed up right away.
It's really frustrating buying a 'developer' phone which I can't develop on.
Well look's like this is a froyo problem with certain devices -
http://code.google.com/p/android/issues/detail?id=9437
So from reading the previous link it seems it's an issue with non 00 mac address's, like the wifi issue. My mac address on my nexus starts with 38.
But the updated broadcom driver in cyanogen mod 6 fixes wifi issuse I have, but not the adb issue.
What is the best way to try get something done about this?
Hello,
before you delete this post as duplicate let me say it is not the case.
I have a problem that I can't debug from eclipse my Samsung galaxy s+.
First of all I must say that under windows I have installed latest kies with drivers for I9001 and device is visible on windows (in devices) in both mode kies or mass storage.
After I installed all explained in "Android Development Tutorial" my device couldn't be found in eclipse.
Than I searched for similar posts and tried all explained in post "[Q] Problem with usb debugging mode miui.us in eclipse".
Again no positive result.
Than I connected Samsung galaxy s I9000 from my friend and his device was found without problem.
Than again I tried to find mine but again without any progress.
I also tried with another device from another friend which also have I9001 and his device also can't be found.
I'm using windows XP and latest drivers and eclipse as explained in your "Android Development Tutorial".
I still think that something with drivers for eclipse is problematic. Can you please help?
Thanks!
Kind regards,
Beco_os
What about the normal adb command line interface?
What happens when you use "adb kill-server" and then try a "adb shell"?
If the above commands do not work: if you use windows OS, what is displayed in device manager while the phone is connected in USB debug mode?
wintel_mac said:
What about the normal adb command line interface?
What happens when you use "adb kill-server" and then try a "adb shell"?
If the above commands do not work: if you use windows OS, what is displayed in device manager while the phone is connected in USB debug mode?
Click to expand...
Click to collapse
Hello,
I tried in both usb modes on Galaxy S+.
1) Mode when Galaxy S+ was in mass storage mode:
d:\Downloads\SamsungMobile\android-sdk-windows\platform-tools>adb kill-server
d:\Downloads\SamsungMobile\android-sdk-windows\platform-tools>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
On Windows in devices I found 2 mass storage:
*Disk drives
- SAMSUNG GT-I9001 Card USB device
- SAMSUNG GT-I9001 Card USB device
2) Mode when Galaxy S+ was in Kies mode:
d:\Downloads\SamsungMobile\android-sdk-windows\platform-tools>adb kill-server
d:\Downloads\SamsungMobile\android-sdk-windows\platform-tools>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
On Windows in devices I found:
*Modems
- SAMSUNG Android USB Modem
*Universal Serial Bus Controllers
- SAMSUNG Android USB Composite Device
So it seems that still adb drivers doesn't work for GT-I9001.
Kind regards,
Berislav
And USB Debugging is enabled on the phone? Settings - Applications Development - USB Debugging
It works fine for me on both XXKPS and XXKPU.
Hi,
thanks for support, but it seems I'm special case
I have 2.3.6 XXKPH version, maybe that can be the cause of problem.
I'm left without idea. I tried reinstallation of all drivers on my PS but nothing is working.
Never the less my friend have galaxy s plus with firmware 2.3.5 XXKPG (this is originally installed on phone when you buy it in Croatia) and have same problem.
Is it possible that someone who don't have problem test this versions of firmware for debugging?
KR,
Berislav
I red somewhere that low powered USB could cause this on i9001, so I bought powered USB Hub and issue is still there. Tried it on Mac OS/X 10.6.8 and no way, Ubuntu 10.10 and no way. I tried XXKPH and XXKPI, editting ~/.android/adb_usb.ini and added Samsung Vendor and/or device id without any approach.
Galaxy S II and Galaxy S are detected properly on these computers.
Bad news
Plysovej_Kaktus said:
I red somewhere that low powered USB could cause this on i9001, so I bought powered USB Hub and issue is still there. Tried it on Mac OS/X 10.6.8 and no way, Ubuntu 10.10 and no way. I tried XXKPH and XXKPI, editting ~/.android/adb_usb.ini and added Samsung Vendor and/or device id without any approach.
Galaxy S II and Galaxy S are detected properly on these computers.
Click to expand...
Click to collapse
I have some bad news about this. I tried another gt-i9001 and it was perfectly detected without doing anything special ( XXKPH ). Visually, this device differs from non working model by missing caption "with Google TM" on the backside and added sticker "DIGITAL BY QUALCOMM" on the top side between jack connector and usb connector. Below battery, both has same information:
MODEL: GT-I9001
SSN: -I9001GSMH
RATED: 3.7 V; 1000 mA
FCC ID: A3LGTI9001
MADE BY SAMSUNG
Non working device has note R176 on sdcard slot, properly working one has G140 there.
... so it seems, we are ****ed. This is something hardware-based.
Same problem here
Hello,
before you delete this post as duplicate let me say it is not the case.
I have a problem that I can't debug from eclipse my Samsung galaxy s+.
First of all I must say that under windows I have installed latest kies with drivers for I9001 and device is visible on windows (in devices) in both mode kies or mass storage.
After I installed all explained in "Android Development Tutorial" my device couldn't be found in eclipse.
Than I searched for similar posts and tried all explained in post "[Q] Problem with usb debugging mode miui.us in eclipse".
Again no positive result.
Than I connected Samsung galaxy s I9000 from my friend and his device was found without problem.
Than again I tried to find mine but again without any progress.
I also tried with another device from another friend which also have I9001 and his device also can't be found.
I'm using windows XP and latest drivers and eclipse as explained in your "Android Development Tutorial".
I still think that something with drivers for eclipse is problematic. Can you please help?
Thanks!
Kind regards,
Beco_os
Hello, I have a same problem, I ve opened back case and the number on sd card slot reads 512S. Could this really be the hardware issue?
I ve bought my phone in Serbia.
BR
Dragan
Hello
I have similar problem but I found that my computer see ”Samsung Android Composite ADB Interface” in device manager when phone is power off. So command ”adb devices” finds my device. But when I power my phone on, at the moment when Samsung logo is shown, my device manager detects change of hardware reloads and ADB interface is missing. It is the same behavior on other computers with Win 7 x64 and Ubuntu 32bit.
At Windows I tried both Google drivers from SDK and Samsung KIES which detects ADB as I wrote. By the way KIES normally detects my phone when the device is on. I have USB Debugging mode enabled, but it seems it doesn't work. I have i9001 European distribution and I'm using stock rom I9001XXKPK, before I was using I9001XXKI2 but the problem was the same.
Have you got any ideas what to do? Where is the problem? Is there any command to force enable USB debugging through ADB?
Thanks for advices.
Hi guys, I've got a problem with regards to the Galaxy Note not being detected on Eclipse. I run command prompt on my PC and typed "adb devices" and my Galaxy Note is shown as attached and connected but when I install my program using Eclipse in Run Configurations > Target, I can't find my Galaxy Note in one of the devices to be installed.
Any help? I already installed Samsung Kies, Checked USB Debugging, Path environment variables to platform-tools, and updated my drivers
Hi guys,
I'd just like to point out that I have searched about 10 times before making this thread.
As the title states, I am using Ubuntu, and I have my Samsung Galaxy S connected. I have enabled USB debugging, and Mass Storage. I have selected the Mount option on the phone too.
Despite all this Ubuntu doesn't show the device. It works fine with my Samsung Galaxy S3.
I have the Android SDK installed too.
Upon running:
Code:
adb devices
and
Code:
fastboot devices
I get no results.
Could somebody please be kind enough to give me a hand?
If there is any questions you need to ask, then, don't hesitate. I am also pretty sure that I am talking about the international SGS too.
Thanks in advance
Hello everyone, i have a problem, since upgraded to android 6.0.1,
i can not connect my Tab S2 SM-T812 on Ubuntu 16.04 LTS.
Have enabled usb debugging mode. Have ADB installed. $ adb shell...error:device not found.
$ lsusb...no Galaxy Tab is listed
Latest software- update Actual Version T813XXU2APK6/T813OXA2APK6
Can you help me
Best regards