[Solved] Cannot mount Android device via USB in Linux

[Slated]

I signed up to these forums to ask a question, but found the answer (by trial and error) even before my first post!

Android device: Samsung Galaxy S GT-I9000 (8GB + 8GB).
OS: Fedora 12 i686 (GNU/Linux).

I connected the phone to my laptop, expecting to be able to mount the two storage devices from the phone, but nothing happened, or to be more precise, this happened (syslog):

Jul 5 13:28:10 localhost kernel: usb 1-3: new high speed USB device using ehci_hcd and address 16
Jul 5 13:28:10 localhost kernel: usb 1-3: New USB device found, idVendor=04e8, idProduct=6877
Jul 5 13:28:10 localhost kernel: usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jul 5 13:28:10 localhost kernel: usb 1-3: Product: SAMSUNG_Android
Jul 5 13:28:10 localhost kernel: usb 1-3: Manufacturer: SAMSUNG
Jul 5 13:28:10 localhost kernel: usb 1-3: SerialNumber: [censored]
Jul 5 13:28:10 localhost kernel: usb 1-3: configuration #4 chosen from 1 choice
Jul 5 13:28:10 localhost kernel: cdc_acm 1-3:4.0: This device cannot do calls on its own. It is not a modem.
Jul 5 13:28:10 localhost kernel: cdc_acm 1-3:4.0: ttyACM0: USB ACM device
Jul 5 13:28:10 localhost modem-manager: (ttyACM0) opening serial device...
Jul 5 13:28:10 localhost kernel: cdc_acm 1-3:4.0: This device cannot do calls on its own. It is not a modem.

No mention at all of USB Mass Storage devices.

Even as a long-term experienced GNU/Linux user, this one had me completely stumped, and I initially assumed the problem was a lack of a fully functional Linux driver for this device.

I even made sure that I'd "mounted" the SD cards within Android, using the USB icon in the menu ("USB connected"), but again, nothing happened, in fact syslog showed no events at all when I did that.

I was so desperate that, at one point, I actually considered rooting the phone just to figure out the problem. But then...

Seconds before I was about to post the question here, I randomly discovered something by accident. I have an application installed on the phone called "Quick System Info", and whilst trawling through its various menus, I found an entry here: Basic Info -> More Information -> USB Settings, which gives the following five options:

• Samsung Kies
• Media player
• Mass storage
• PC Internet
• Ask on connection

This was currently set to "Samsung Kies". I have no idea what that is, but after changing it to "Mass storage" I got this (syslog):

Jul 5 13:45:33 localhost kernel: usb 1-3: new high speed USB device using ehci_hcd and address 17
Jul 5 13:45:33 localhost kernel: usb 1-3: New USB device found, idVendor=04e8, idProduct=681d
Jul 5 13:45:33 localhost kernel: usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jul 5 13:45:33 localhost kernel: usb 1-3: Product: SAMSUNG_Android
Jul 5 13:45:33 localhost kernel: usb 1-3: Manufacturer: SAMSUNG
Jul 5 13:45:33 localhost kernel: usb 1-3: SerialNumber: [censored]
Jul 5 13:45:33 localhost kernel: usb 1-3: configuration #2 chosen from 1 choice
Jul 5 13:45:33 localhost kernel: scsi12 : SCSI emulation for USB Mass Storage devices
Jul 5 13:45:35 localhost kernel: btusb_intr_complete: hci0 urb f16a1b00 failed to resubmit (1)
Jul 5 13:45:35 localhost kernel: btusb_bulk_complete: hci0 urb f16a1600 failed to resubmit (1)
Jul 5 13:45:35 localhost kernel: btusb_bulk_complete: hci0 urb f16a1c80 failed to resubmit (1)
Jul 5 13:45:38 localhost kernel: scsi 12:0:0:0: Direct-Access SAMSUNG GT-I9000 Card 0000 PQ: 0 ANSI: 2
Jul 5 13:45:38 localhost kernel: scsi 12:0:0:1: Direct-Access SAMSUNG GT-I9000 0000 PQ: 0 ANSI: 2
Jul 5 13:45:38 localhost kernel: sd 12:0:0:0: [sdc] 15650816 512-byte logical blocks: (8.01 GB/7.46 GiB)
Jul 5 13:45:38 localhost kernel: sd 12:0:0:0: [sdc] Write Protect is off
Jul 5 13:45:38 localhost kernel: sd 12:0:0:0: [sdc] Assuming drive cache: write through
Jul 5 13:45:38 localhost kernel: sd 12:0:0:0: Attached scsi generic sg1 type 0
Jul 5 13:45:38 localhost kernel: sd 12:0:0:0: [sdc] Assuming drive cache: write through
Jul 5 13:45:38 localhost kernel: sdc:
Jul 5 13:45:38 localhost kernel: sd 12:0:0:1: Attached scsi generic sg2 type 0
Jul 5 13:45:38 localhost kernel: sd 12:0:0:0: [sdc] Assuming drive cache: write through
Jul 5 13:45:38 localhost kernel: sd 12:0:0:0: [sdc] Attached SCSI removable disk
Jul 5 13:45:38 localhost kernel: sd 12:0:0:1: [sdd] 12124096 512-byte logical blocks: (6.20 GB/5.78 GiB)
Jul 5 13:45:38 localhost kernel: sd 12:0:0:1: [sdd] Write Protect is off
Jul 5 13:45:38 localhost kernel: sd 12:0:0:1: [sdd] Assuming drive cache: write through
Jul 5 13:45:38 localhost kernel: sd 12:0:0:1: [sdd] Assuming drive cache: write through
Jul 5 13:45:38 localhost kernel: sdd:
Jul 5 13:45:38 localhost kernel: sd 12:0:0:1: [sdd] Assuming drive cache: write through
Jul 5 13:45:38 localhost kernel: sd 12:0:0:1: [sdd] Attached SCSI removable disk

And suddenly two windows appeared on my desktop, one for each filesystem.

WOOT!

Hope somebody finds this useful.

(PS: transferring a 700MB AVI over Bluetooth is not fun).

 

[koodawg]

I'm new to android, just spent some time searching for answers, found solution and wanted to share my findings;

I have a new Samsung Skyrocket. First time I plugged it into Windows and Mac the drives appeared and I was able to begin copying music. Days later I couldn't get this to work and it took me numerous hours to resolve.

I saw posts referring to a procedure like this; connect phone to usb port, option to use usb storage appears on phone, hit ok, and you're good to go.

This doesn't happen on my version of gingerbread. I have to go into the the usb utilities, choose to use usb mass storage, then it tells me to connect to usb port on computer, I do so then phone says to click ok to continue and if it's successful then phone screen says USB storage in use. That's how it goes when it works. I had this work on Windows and Mac. Drives appeared in file browsers of both OSs.

Now what happened for the past 2 days is that I'd connect phone usb cable computer (and get a notification chirp) but I wouldn't get that succeeding screen on the phone saying ok to continue. Instead it went back to the original usb utility. I jacked around with this on and off for two days, trying, searching for clues.

I also tried connected to a linux box since that's where I really wanted to connect anyway - directly to my music host. Same thing occurred on the phone which connecting to linux (FC14). Odd thing was that I was at first not getting any output in dmesg at all. No indication of any usb device being connected. Weird. Much searching. Nothing.

I ran across some posts about Kies. Looked at that app - it's for copying over wifi. Don't want that. Then I read something about how a guys phone was set with the usb attached to Kies and he had to unattach it. I couldn't find a way to do that exactly so I just rebooted and things started to get good.

Now when I connected to linux I was getting the appropriate usb device messages in dmesg. But I still could not mount the devs. fdisk even failed to display any info at all. Weird. Then I realized I need to go into the usb utils and enable usb mass storage use. Did that and all is well.

Now when I connect phone usb to computer (win, mac, linux) it's mounting and the world is right again.

 

[Rush]

Hopefully this will come handy for other users having this sort of problem.

<thread moved>