Ubuntu can't detect device - Galaxy S I9000 Q&A, Help & Troubleshooting

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

Related

[Q] Galaxy Tab not showing up in adb devices on mac

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?

[Q] Another Driver Thread

Devs,
I have read everything I can to try to correct a darn driver issue with my AT&T Samsung Galaxy S SGH-I897 with Froyo 2.2. I know you all have read this countless times and I have read many forum threads similar to this one but I can not get this problem resolved.
When I install the Kies driver package (or the "usb_drivers_GalaxyS_x64.zip" package) I can no longer use my phone as a mass storage device and Superoneclick will not work.
When I uninstall the Kies driver package I can use my phone as a mass storage device but I can't turn on the Debug option to use Superoneclick because then those dev drivers have to install and thus disabling the mass storage device drivers.
I am super tired from busting my head on this all night so I apologize if i am not making any sense.
What is wrong with the driver situation for this phone? How many drivers have to be installed? I downloaded the drivers from Samsung, and other sites I saw posted in this forum.
No matter what I do I CAN NOT get Superoneclick or Droid explorer to see my phone.
I have enabled USB debugging, tried using different USB ports. I am completely lost at this point.
I have had easier times installing ISA hardware drivers for 1553-Bus cards on Win NT boxes!
Sorry for the rant and feel free to call me an idiot but any advice would be nice.
OS = Win 7 x64
-Neil
On another note. What are all of the devices that will come up when the phone is in Debugging and when it is not in Debugging Mode? I noticed there are 3 differant devices when it is in debugging and only 1 device if it isn't.
When in debugging mode do you mount the device as "Mass Storage" or "Kies Firmware Update" (I'm assuming you don't mount it as "Media Player".
Had to use the USB inputs on the rear and not on front. Sorry for wasting anyones time on something retarded

[Q] Problem with usb debugging galaxy s I9001

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.

[Q] How to connect 4x Hd to Ubuntu?

Hi everybody I received an LG optimus 4x HD, but the *** phone doesn't get recognized by Ubuntu as a storage device, seems to be because the cell phone have windows media player sync, and lg installer. Thus, I managed to recognized it with ADB is not a cool option. so, i need to know:
Is there any way to recognize it without using ADB that comes with android SDK on console?
It's possible with mtpd. There are some tutorials around on how to connect the Galaxy Nexus, and all the newer android devices use that mode. It's a bit tricky though, for me it didn't work on the first attemp and I haven't tried since. One workaround that many recommend is to use a ftp server on the phone; another way - preferrably for small files - would be using Dropbox/Google Drive or something like that.
re:solved
muellersmattes said:
It's possible with mtpd. There are some tutorials around on how to connect the Galaxy Nexus, and all the newer android devices use that mode. It's a bit tricky though, for me it didn't work on the first attemp and I haven't tried since. One workaround that many recommend is to use a ftp server on the phone; another way - preferrably for small files - would be using Dropbox/Google Drive or something like that.
Click to expand...
Click to collapse
thanks for the advice, I've searched this and is solved. I installed gMTP trough the Ubuntu software center, then I connected my cell phone. opened gMTP program. Pressed the connect icon and there I have a basic graphic interface to move files to my phone and from my phone,
Update:
now my pc detects it automatically. The trick was to create an udev rule for the cell phone like when you want to debug on the cell phone.
the idea is to create the file /etc/udev/riles-d/51-android.rules
on the file should be this line:
SUBSYSTEM=="usb", ATTR{idVendor}=="1004", MODE="0666", GROUP="plugdev"
give permissions to the file using $:chmod a+r
then rebooted my computer and now recognize it automatically when is it in MTP mode,

[Q] Issue with adb, device not listed, tried everything

Heya everybody ! So I got me a Galaxy gear yesterday and I was eager to get home and root it and put a custom rom on it, since I need it for some apps + I got a Htc m7. So I get home, connect it to my macbook, (noticed that the usb debugging was already switched on) and ran adb. I'm no stranger to adb and fastboot but far from a pro (I just read tons of instructions and learn simple commands) So After running ./adb devices I just get the List of devices : and an empty list.
I've tried it on another mac, same thing. On 2 different PC's with win 7 and 8, same thing.
On the macs I've deleted any apps that might have anything to do with such drivers like Android file transfer.
Updated the adb_usb.ini vendors.
on the pc's Ive uninstalled and installed over and over all the drivers and still get the same problem.
+ I've tried all types of adb's, downloading the sdk over and over again with no result.
I even tried restoring the device a couple of times and even reinstalled the stock rom with Odin.
I've done pretty much everything I can find on the net on how to fix this issue.
Can you guys please help me with some Ideas ?
P.S
in adb I've tried the ./adb kill-server about a 100 times, so have I restarted each pc/mac 100 times and changed between every usable usb port.
One this I notice that on my mac when I go to the "device manager"/"system report", Under USB it says TIZEN with this info :
Product ID: 0x6860
Vendor ID: 0x04e8 (Samsung Electronics Co., Ltd.)
Version: 4.00
Serial Number: 441f900f41018dc9
Speed: Up to 480 Mb/sec
Manufacturer: Samsung
Location ID: 0x1d110000 / 8
Current Available (mA): 500
Current Required (mA): 96
Oh the gear :
Model : SM-V700
Software version : V700XXuCNF1
I would appreciate any ideas and comments ! Thank you guys !!!
Add :
Oh and also Cydia Impactor can't find the device.(forgot to mention it)
Add 2 :
Oh and on the PC I installed and uninstalled Kies a couple of times.
Your gear isn't using android sdk. It's using Tizen. Download this sdk.
https://developer.tizen.org/downloads/tizen-sdk
440bro said:
Your gear isn't using android sdk. It's using Tizen. Download this sdk.
https://developer.tizen.org/downloads/tizen-sdk
Click to expand...
Click to collapse
Didn't see that one coming thank you.
P.s
I just installed it, and I'm kinda lost. Cant find anything in it which I know how to use ? Any pointers on what to do after installing this SDK ?
Edit:
I tried using the sdb as adb and still I get an empty list.
Did install it on both my mac and pc. and it's like nothings changed.
EDIT LAST :
Ok so I ran this : http://forum.xda-developers.com/showthread.php?t=2770183&page=13
from Odin to my device, and now my SDB finds my device. but I still cannot install apk files and not sure should i flash a recovery now and actually pretty confused on whats going on.
https://developer.tizen.org/documentation/articles/smart-development-bridge
440bro said:
https://developer.tizen.org/documentation/articles/smart-development-bridge
Click to expand...
Click to collapse
Thank you so much, finally got the hang of it after bricking it a couple of times
I was doing everything backwards and chaotic but now I understand whats what
got it to work and started flashing everything I need, THANK YOU SO MUCH !

Categories

Resources