allelopath
asked on
Connect Samsung Continuum to Macbook Pro
I am trying to connect my Samsung Continuum android to my macbook pro via USB so that I may copy files from the phone to the mac.
I have enabled "Mass storage" under the USB settings on the phone. I have also enabled USB debugging on the phone. The phone has an 8gb memory card.
The Macbook Pro is running OS X 10.6.7. The mac has 2 USB ports, I have tried both of them with no success. I have no removable drives on the mac.
When I plug in the phone to the computer, an icon appears on the desktop entitled "Verizon Mobile". This icon is a folder that contains 4 files. After about 10 seconds or so, the icon disappears. The files are Autorun.inf, ToolLauncher-Bootstrap.exe , ModelName.txt, Samsung_Model_USB_Driver.e xe. These are obviously windows files and of no use here.
Then I pull the notification bar on phone home screen and tap on USB connected.
I get the choice of "Mount" or "Don't Mount"
I choose Mount
Then a message pops up saying:
"The disk you inserted was not readable by this computer"
with buttons:
"Initialize …" "Ignore" "Eject"
I choose Ignore. Nothing happens, I might expect to see an icon appear on the desktop, but nothing and I don't see anything, though. Under my "Macintosh HD" - DEVICES, it is not listed.
I restart the Mac without disconnecting the USB cable, but the phone still does not appear.
How can I solve this problem?
I have enabled "Mass storage" under the USB settings on the phone. I have also enabled USB debugging on the phone. The phone has an 8gb memory card.
The Macbook Pro is running OS X 10.6.7. The mac has 2 USB ports, I have tried both of them with no success. I have no removable drives on the mac.
When I plug in the phone to the computer, an icon appears on the desktop entitled "Verizon Mobile". This icon is a folder that contains 4 files. After about 10 seconds or so, the icon disappears. The files are Autorun.inf, ToolLauncher-Bootstrap.exe
Then I pull the notification bar on phone home screen and tap on USB connected.
I get the choice of "Mount" or "Don't Mount"
I choose Mount
Then a message pops up saying:
"The disk you inserted was not readable by this computer"
with buttons:
"Initialize …" "Ignore" "Eject"
I choose Ignore. Nothing happens, I might expect to see an icon appear on the desktop, but nothing and I don't see anything, though. Under my "Macintosh HD" - DEVICES, it is not listed.
I restart the Mac without disconnecting the USB cable, but the phone still does not appear.
How can I solve this problem?
ASKER
>>settings, applications, usb settings,
In Setting -> Applications, available selections are:
Unknown Sources
Manage applications
Running services
Development
There is Applications -> USB Settings, under which the choices are:
Media Player
Mass storage
Ask on Connection
I guess that's what you're talking about. I've been instructed to choose Mass storage, but will try Ask on Connection.
>>enable usb debugging while you're at it.
As originally posted, already done (under Setting -> Applications -> Development)
In Setting -> Applications, available selections are:
Unknown Sources
Manage applications
Running services
Development
There is Applications -> USB Settings, under which the choices are:
Media Player
Mass storage
Ask on Connection
I guess that's what you're talking about. I've been instructed to choose Mass storage, but will try Ask on Connection.
>>enable usb debugging while you're at it.
As originally posted, already done (under Setting -> Applications -> Development)
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Since the mac doesn't recognize the phone, I don't understand how performing these commands from the mac terminal will give information about the phone, but here it is:
15-MacBook-Pro:~ apple$ df -h
Filesystem Size Used Avail Capacity Mounted on
/dev/disk0s2 232Gi 123Gi 110Gi 53% /
devfs 109Ki 109Ki 0Bi 100% /dev
map -hosts 0Bi 0Bi 0Bi 100% /net
map auto_home 0Bi 0Bi 0Bi 100% /home
15-MacBook-Pro:~ apple$ fdisk -l
fdisk: illegal option -- l
usage: fdisk [-ieu] [-f mbrboot] [-c cyl -h head -s sect] [-S size] [-r] [-a style] disk
-i: initialize disk with new MBR
-u: update MBR code, preserve partition table
-e: edit MBRs on disk interactively
-f: specify non-standard MBR template
-chs: specify disk geometry
-S: specify disk size
-r: read partition specs from stdin (implies -i)
-a: auto-partition with the given style
-d: dump partition table
-y: don't ask any questions
-t: test if disk is partitioned
`disk' is of the form /dev/rdisk0.
auto-partition styles:
boothfs 8Mb boot plus HFS+ root partition (default)
bootufs 8Mb boot plus UFS root partition
hfs Entire disk as one HFS+ partition
ufs Entire disk as one UFS partition
dos Entire disk as one DOS partition
raid Entire disk as one 0xAC partition
That's fdisk -l where the "-l" is a lower case L, correct?
15-MacBook-Pro:~ man fdisk
NAME
fdisk -- DOS partition maintenance program
SYNOPSIS
fdisk [-ieu] [-f mbrname] [-c cylinders] [-h heads] [-s sectors]
[-S size] [-b size] device
DESCRIPTION
In order for the BIOS to boot the kernel, certain conventions must be
adhered to. Sector 0 of a bootable hard disk must contain boot code, an
MBR partition table, and a magic number (0xAA55). These MBR partitions
(also known as BIOS partitions) can be used to break the disk up into
several pieces.
The BIOS loads sector 0 of the boot disk into memory, verifies the magic
number, and begins executing the code at the first byte. The normal DOS
MBR boot code searches the MBR partition table for an ``active'' parti-
tion (indicated by a `*' in the first column), and if one is found, the
boot block from that partition is loaded and executed in place of the
original (MBR) boot block.
15-MacBook-Pro:~ apple$ df -h
Filesystem Size Used Avail Capacity Mounted on
/dev/disk0s2 232Gi 123Gi 110Gi 53% /
devfs 109Ki 109Ki 0Bi 100% /dev
map -hosts 0Bi 0Bi 0Bi 100% /net
map auto_home 0Bi 0Bi 0Bi 100% /home
15-MacBook-Pro:~ apple$ fdisk -l
fdisk: illegal option -- l
usage: fdisk [-ieu] [-f mbrboot] [-c cyl -h head -s sect] [-S size] [-r] [-a style] disk
-i: initialize disk with new MBR
-u: update MBR code, preserve partition table
-e: edit MBRs on disk interactively
-f: specify non-standard MBR template
-chs: specify disk geometry
-S: specify disk size
-r: read partition specs from stdin (implies -i)
-a: auto-partition with the given style
-d: dump partition table
-y: don't ask any questions
-t: test if disk is partitioned
`disk' is of the form /dev/rdisk0.
auto-partition styles:
boothfs 8Mb boot plus HFS+ root partition (default)
bootufs 8Mb boot plus UFS root partition
hfs Entire disk as one HFS+ partition
ufs Entire disk as one UFS partition
dos Entire disk as one DOS partition
raid Entire disk as one 0xAC partition
That's fdisk -l where the "-l" is a lower case L, correct?
15-MacBook-Pro:~ man fdisk
NAME
fdisk -- DOS partition maintenance program
SYNOPSIS
fdisk [-ieu] [-f mbrname] [-c cylinders] [-h heads] [-s sectors]
[-S size] [-b size] device
DESCRIPTION
In order for the BIOS to boot the kernel, certain conventions must be
adhered to. Sector 0 of a bootable hard disk must contain boot code, an
MBR partition table, and a magic number (0xAA55). These MBR partitions
(also known as BIOS partitions) can be used to break the disk up into
several pieces.
The BIOS loads sector 0 of the boot disk into memory, verifies the magic
number, and begins executing the code at the first byte. The normal DOS
MBR boot code searches the MBR partition table for an ``active'' parti-
tion (indicated by a `*' in the first column), and if one is found, the
boot block from that partition is loaded and executed in place of the
original (MBR) boot block.
take a look at this link there may be some useful info for you::
http://androidcommunity.com/forums/archive/index.php/t-37817.html
http://androidcommunity.com/forums/archive/index.php/t-37817.html
ASKER
roylong:
Reading that link. I've learned there are 2 types of USB cables (charge and/or data). The cable I am using is definitely charging, but I don't know how to tell if it is data.
Reading that link. I've learned there are 2 types of USB cables (charge and/or data). The cable I am using is definitely charging, but I don't know how to tell if it is data.
ASKER
The USB cable is good. I've connected the phone to an Win XP machine (after downloading drivers from Samsung).
do you know how your memory card is formatted? if it's not FAT or NTFS it may be formatted ext (linux filesystem); if it is then you may be able to mount using extFS from Paragon Software. they offer a ten day time limited demo for download here...
http://www.paragon-software.com/home/extfs-mac/download.html
http://www.paragon-software.com/home/extfs-mac/download.html
if this does work; I would suggest trying to copy you stuff off and then reformat the card as FAT format.
ASKER
How do I determine the memory card format?
ASKER
On the phone, under SD card & phone storage, there is;
External SD Card
Total Space: 7.39 gb
Available Space: 7.32 gb
Unmount SD card
Format SD card (this is greyed out, cannot select)
Internal phone Storage
Available Space: 1.25 gb
Nothing about specifying format of card
External SD Card
Total Space: 7.39 gb
Available Space: 7.32 gb
Unmount SD card
Format SD card (this is greyed out, cannot select)
Internal phone Storage
Available Space: 1.25 gb
Nothing about specifying format of card
ASKER
I have everything copied to my PC. I guess, referring to my original post, I could select "Initialize" and see what happens.
If you initialise make sure you have any data on there backed up.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
The manual is here:
http://www.samsung.com/us/support/downloads/SCH-I400ZKAVZW
On page 101, it gives instructions for formatting the SD card. I tried it, it doesn't give any choices of which file system format to use.
http://www.samsung.com/us/support/downloads/SCH-I400ZKAVZW
On page 101, it gives instructions for formatting the SD card. I tried it, it doesn't give any choices of which file system format to use.
Also, enable usb debugging while you're at it.