How do I get photos off my phone? - Atrix 4G Q&A, Help & Troubleshooting

How can I load photos from my phone to my PC? I want to go directly to my PC. I don't want to transfer photos via an intermediary service like picasa or gmail.
The only ports on the phone are an HDMI port and a USB port. When I connect the phone to my PC via the USB cable, it gets mounted, but the only directory I can see has some Windows files:
file:///media/Motorola/Autorun.inf
file:///media/Motorola/MotoHelper_2.0.40_Driver_4.8.0.exe
file:///media/Motorola/config.ini
file:///media/Motorola/setup.exe
I run Linux, so those setup files don't help.
i see the following in dmesg.
Code:
scsi 13:0:0:0: CD-ROM Motorola MB860 0000 PQ: 0 ANSI: 2
sr1: scsi3-mmc drive: 0x/0x caddy
sr 13:0:0:0: Attached scsi CD-ROM sr1
sr 13:0:0:0: Attached scsi generic sg7 type 5
scsi 13:0:0:1: CD-ROM Motorola MB860 0000 PQ: 0 ANSI: 2
sr2: scsi3-mmc drive: 0x/0x caddy
sr 13:0:0:1: Attached scsi CD-ROM sr2
sr 13:0:0:1: Attached scsi generic sg8 type 5
ISO 9660 Extensions: Microsoft Joliet Level 1
ISOFS: changing to secondary root
The df command shows /dev/sr1 mounted:
Code:
/dev/sr1 8414 8414 0 100% /media/Motorola
When I try to mount /dev/sr2, I get an error:
Code:
# mount /dev/sr2 /mnt/k1
mount: /dev/sr2: unknown device

I figured it out.
After connecting the phone to the PC via the USB cable (the one from the charger), pull down the white bar at the top of the screen, tap the "USB connection", then tap "USB Mass Storage". Then tap OK. The device should mount automatically on most systems and be visible via your PC system file manager.
If it mounts automatically, issue the df command and look for something like the following:
Code:
/dev/sdg 11231008 26048 11204960 1% /media/MB860
If not, review the last messages in your dmesg (Linux systems) and look for the device name it was associated with and then issue a mount for it.
Code:
# dmesg | tail
sd 14:0:0:1: Attached scsi generic sg8 type 0
sd 14:0:0:0: [sdg] 22467584 512-byte logical blocks: (11.5 GB/10.7 GiB)
sd 14:0:0:0: [sdg] Write Protect is off
sd 14:0:0:0: [sdg] Mode Sense: 03 00 00 00
sd 14:0:0:0: [sdg] Assuming drive cache: write through
sd 14:0:0:0: [sdg] Assuming drive cache: write through
sdg:
sd 14:0:0:1: [sdh] Attached SCSI removable disk
sd 14:0:0:0: [sdg] Assuming drive cache: write through
sd 14:0:0:0: [sdg] Attached SCSI removable disk
In the above case, the following mount command would work if you had a directory called /mnt/phone
mount /dev/sdg /mnt/phone
and a df command would show something like:
Code:
/dev/sdg 11231008 26048 11204960 1% /mnt/phone
Now that the phone is mounted, you can just copy the photos to some directory on your PC.

Related

16GB SDCard shrink to 11.3GB . Help needed

Hi everyone,
I have 16GB ADATA microSD card. After reformating through the recovery image to ext2,swapm and fat 14GB i used apps2sd for a while now. Today i wanted to wip my phone and all data on the microsd, so booted up recovery image and used Part SD to only fat32. I wanted to use the whole 16GB as a Fat32 drive again. But then I only got 14GB recognized in windows.
So i Tried to reformat again to swap,ext2 and Fat 12GB. But after trying to format back to 16GB FAT32 i lost another 2GB. I cant get the card to work in Windows anymore the only way i can access is through ADB.
Can someone help me to get my 16GB back?
j_love
update: i get the following when using parted
/dev/block # parted mmcblk0 print
parted mmcblk0 print
Model: SD SD (sd/mmc)
Disk /dev/block/mmcblk0: 12.0GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 32.3kB 12.0GB 12.0GB primary fat32 lba
What is the output of
Code:
parted -l
parted -l doesnt give me any output.
/ # parted -l
parted -l
/ #
Sounds like you have a corrupt partition table on your card. It's probably best to delete all the partitions on this card and start over BUT you should use a decent partitioning tool. Without meaning to be rude, it sounds like you are using Windows' built in (i.e. very basic) drive formatting tools and that you probably aren't that familiar with using parted on the command line. I would recommend using gparted, a graphical tool. You can use this either from a USB key http://gparted.sourceforge.net/liveusb.php or an Ubuntu live cd (appears as 'partition editor'). I find that disc partitioning is a great deal easier with graphics, i.e. in this case you can see what you are doing.
Thanks but I already used the liveCD of gparted. The main problem here is that my SDCARD is not recognized in Windows or in Linux. Also tryed Ubuntu and knoppix. I am not very familiar with linux but have some experience with command line tools.
The only way i can access the SDCARD is via adb on my Hero. Do you know any commands i could test? I already wiped the partition table and tried to make new partitions. But im stuck at 12GB.
The thing is that in Linux, you don't mount a device, you mount a file system. In this case that would translate to partitions (there are other cases but they are not relevant here). I would ask: if you cannot 'see' the card in windows or in linux and parted -l gives no output, where is this 12GB figure coming from?
Windows typically won't show a drive in 'my computer' if it doesn't recognise the partition format so you won't see any ext2 or ext3 partitions. You won't get any pop-ups on your desktop for unformatted space in Ubuntu either. Please could you confirm that you have tried the following:
In Ubuntu connect phone via USB to PC via (on phone) 'USB/ USB connected/ mount'. This won't affect adb.
Bring up Gparted and do 'gparted/refresh devices'
Select '/dev/sdb' or whatever your memory card appears as there- your main hard drive will be shown by default.
Tell us what you see now
I am attaching a screenshot of my SD card in my phone seen like this. It shows as sdc because I have two hard drives on my PC
ok done that. I got the following
/dev/sdf1 11.21GiB
/dev/sdf1 fat32 /media/disk 11.21GiB 11.26MiB 11.20GiB lba
/dev/sdf1 11.21GiB
/dev/sdf1 fat32 /media/disk 11.21GiB 11.26MiB 11.20GiB lba
Click to expand...
Click to collapse
If I understand correctly the above appears to show a single FAT32 partition on this device of 11.21GiB with 11.26MiB used. My suggestion is to use Gparted to delete all the partitions on this card (don't forget to hit 'apply') and then see how much unformatted space you have. Bear in mind that you must unmount your filesystem (mounting/unmounting can be done within gparted) before playing around with any of the partitions on it. You can then create new partitions on the card (again, don't forget to 'apply changes'). You will likely have to reboot your phone to seem them there.
Does this work?
ok. I can delete create resize partitions but the diskspace is still 11.21GiB
If you delete all the partitions on the device, how much 'unallocated space do you have after 'apply changes'? when you unmount and the remount the card?
unallocated space is 11.21GiB
okay try creating a single new partition on the card and then using the 'check' option in gparted. What happens then?
Created a ext2 partition and checked it. Check was fine without errors but space is still 11.21GiB
Okay, assuming your card is still on /dev/sdf1 please try the following:
Code:
sudo fdisk /dev/sdf
This enters the fdisk shell. Then type
Code:
p
and paste the output here. You can exit fdisk with the command
Code:
quit
Got the following output
[email protected]:~$ sudo fdisk /dev/sdf
The number of cylinders for this disk is set to 1463.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)
Command (m for help): p
Disk /dev/sdf: 12.0 GB, 12035555328 bytes
255 heads, 63 sectors/track, 1463 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00065e4e
Device Boot Start End Blocks Id System
/dev/sdf1 1 1463 11751516 83 Linux
Command (m for help): quit
does anyone have the output of fdisk->p of there ADATA 16GB microSD CARD???
I tried to change the clyinders but need the correct value
Code:
Disk /dev/sdf: 12.0 GB, 12035555328 bytes
255 heads, 63 sectors/track, 1463 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00065e4e
Device Boot Start End Blocks Id System
/dev/sdf1 1 1463 11751516 83 Linux
Click to expand...
Click to collapse
Well that's interesting. This appears to show a single ext3 partition toward the end of the card (unless I've got this completely wrong). What do you get for
Code:
parted
print
with the same partion(s)?
for reference on my 8GB card I get (on laptop):
Code:
sudo fdisk
p
gives
Code:
Disk /dev/sdb: 7948 MB, 7948206080 bytes
255 heads, 63 sectors/track, 966 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x000beb03
Device Boot Start End Blocks Id System
/dev/sdb1 * 1 902 7245283+ c W95 FAT32 (LBA)
/dev/sdb2 903 966 514080 83 Linux
and
Code:
sudo parted /dev/sdb
print
gives
Code:
Model: HTC Android Phone (scsi)
Disk /dev/sdb: 7948MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 32.3kB 7419MB 7419MB primary fat32 boot, lba
2 7419MB 7946MB 526MB primary ext2
Im Not at home right now but will post the Output tomorrow.
But I think you got it wrong. The start cylinder is 1 and the end is at 1463.
I can use fdisk to manipulate the cylinders but the size stays the same. This is really a big problem. There ar3 more users on the net with similar problems but without a solution. Hope we can get this back to normal.
I get the following for :
[email protected]:/# parted /dev/sdf
GNU Parted 1.8.8
Using /dev/sdf
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
Model: SD/MMC Card Reader (scsi)
Disk /dev/sdf: 12.0GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 32.3kB 12.0GB 12.0GB primary fat32 lba
(parted)
(parted) quit
and the following for
[email protected]:/# fdisk /dev/sdf
The number of cylinders for this disk is set to 1463.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)
Command (m for help): p
Disk /dev/sdf: 12.0 GB, 12035555328 bytes
255 heads, 63 sectors/track, 1463 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x0005c05a
Device Boot Start End Blocks Id System
/dev/sdf1 1 1464 11753440 c W95 FAT32 (LBA)
Cheers, any chance of posting that again and using the 'code' tags in the message editor? It's a bit hard to read in the body of your post like this
thanks

ext2 support?

Specifically, what do I need to install on my gtab so that it can read an sdcard formatted to ext2?
I've already installed Clockworkmod and Vegan-Tab Ginger. Maybe I need a different kernel too? I know very little about kernels - Are they device specific? Are they interchangeable? Can I change the kernel without wiping my files?
Has anyone ever had success with ext2 on the gtab?
deadfraggle said:
Specifically, what do I need to install on my gtab so that it can read an sdcard formatted to ext2?
Click to expand...
Click to collapse
Nothing.
I know very little about kernels - Are they device specific?
Click to expand...
Click to collapse
They have to be--that's their function after all.
Are they interchangeable?
Click to expand...
Click to collapse
They should be. For the gTablet, you can use either the Clemsyn or Pershoot kernels. Both have native extn support.
Can I change the kernel without wiping my files?
Click to expand...
Click to collapse
Yes.
Has anyone ever had success with ext2 on the gtab?
Click to expand...
Click to collapse
ext2/3/4 are all natively supported by the linux kernel, and issuing a mount command will work if you do it on the command line. However, the automounter program, called vold, likes to have ext4 or VFAT (aka FAT32) filesystems on the SD card. If your ext2 formatted SD card is not automatically mounted, format it again as ext4.
Formatted the sdcard to ext4, but still cannot read anything off it.
As for mounting through the terminal, if I use
fdisk -l
it shows nothing, not even an error. Is there another way to list disks so I know what to mount?
What I'm trying to do is use the Debian installer for Android, but the only version I could find is 2 years old. It's probably based on Lenny or earlier which does not have native ext4 support.
deadfraggle said:
Formatted the sdcard to ext4, but still cannot read anything off it.
Click to expand...
Click to collapse
What ROM are you on? Are you running Android or something else?
As for mounting through the terminal, if I use
fdisk -l
it shows nothing, not even an error. Is there another way to list disks so I know what to mount?
Click to expand...
Click to collapse
Code:
$ su
# /system/xbin/fdisk -l /dev/block/mmcblk3
Disk /dev/block/mmcblk3: 16.0 GB, 16097738752 bytes
255 heads, 63 sectors/track, 1957 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk3p1 1 1709 13720703 c Win95 FAT32 (LBA)
/dev/block/mmcblk3p2 1709 1958 1999744+ 83 Linux
Use /dev/block/mmcblk2 for the external SD card. Mount it as:
Code:
$ su
# mount /dev/block/mmcblk2p1 /some/path
or
Code:
$ su
# mount -t ext4 /dev/block/mmcblk2p2 /some/path
rajeevvp said:
What ROM are you on? Are you running Android or something else?
Click to expand...
Click to collapse
Vegan-Tab Ginger edition
rajeevvp said:
Code:
$ su
# /system/xbin/fdisk -l /dev/block/mmcblk3
Click to expand...
Click to collapse
This gives me similar results to yours.
rajeevvp said:
Use /dev/block/mmcblk2 for the external SD card. Mount it as:
Code:
$ su
# mount /dev/block/mmcblk2p1 /some/path
Click to expand...
Click to collapse
My result:
Code:
$ su
# mount /dev/block/mmcblk2p1 /micro
mount: mounting /dev/block/mmcblk2p1 on /micro failed: No Such file or directory
Also tried
mount /dev/block/mmcblk2p2 /micro
with the same result.
rajeevvp said:
or
Code:
$ su
# mount -t ext4 /dev/block/mmcblk2p2 /some/path
Click to expand...
Click to collapse
My result:
Code:
$ su
# mount -t ext4 /dev/block/mmcblk2p2 /micro
mount: mounting /dev/block/mmcblk2p2 on /micro failed: No Such file or directory
Edit:
If I insert a ext2 formatted sdcard, I get a notice that it is being scanned for errors. It goes away after a minute or so.
If I go to /sdcard2 in Root Explorer, the folder is empty but the stats show a correct 2 gb of used space and the correct amount of free space.
(Also in Root Explorer, if I try to create a test file, it says 'successful' but no file is created.)
If someone here owns a gtab and can access a ext2/4 sdcard, please let me know what setup/Rom you are using. Or if you own an extra sdcard you can format to ext2, and use some other aftermarket ROM/different kernel on your gtab, please test and post your results.
The commands I gave were just examples, you'll have to adjust them to suit your system.
deadfraggle said:
If I insert a ext2 formatted sdcard, I get a notice that it is being scanned for errors. It goes away after a minute or so.
Click to expand...
Click to collapse
That looks like the correct behaviour. The external SD card is being fsck'd and then automounted.
If I go to /sdcard2 in Root Explorer, the folder is empty but the stats show a correct 2 gb of used space and the correct amount of free space.
Click to expand...
Click to collapse
This, again, is correct, except that on a newly created filesystem, Root Explorer should've shown a lost+found directory.
(Also in Root Explorer, if I try to create a test file, it says 'successful' but no file is created.)
Click to expand...
Click to collapse
Reformat the filesystem again and try creating a file using the command line:
Code:
$ su
# echo test > /mnt/sdcard2/test.txt
# cat /mnt/sdcard2/test.txt
test
#
My external SD card is formatted as ext3 and I have no problem using Root Explorer. With other file managers, you'll have to be careful because of the standard Unix permissions that come into effect on all extn filesystems. If you want to use file managers other than Root Explorer, just create a new directory on your ext2 filesystem and give that directory a user of "system" and a group of "sdcard_rw", and give (at least) the group "rwx" permissions. Use the user, group and permissions of the /mnt/sdcard directory as a guide:
Code:
$ ls -ld /mnt/sdcard
d---rwxr-x 22 system sdcard_rw 8192 Jan 1 1970 /mnt/sdcard
$ su
# mkdir /mnt/sdcard2/user-dir
# chmod 0775 /mnt/sdcard2/user-dir [I]#or 0075 to exactly match /mnt/sdcard[/I]
# chown system.sdcard_rw /mnt/sdcard2/user-dir
If you don't want to bother with all this, just format the SD card as VFAT, and Android will automatically mount the VFAT filesystem with an owner of "system" and a group of "sdcard_rw". And since (all?) file managers belong to the "sdcard_rw" group, they get automatic read-write permissions to that filesystem. BTW, the Terminal Emulator app also belongs to the "sdcard_rw" group, so you can freely write onto VFAT formatted SD cards on the command line without resorting to the 'su' command (the example above).
Granted, it's been a while since I researched this - but I learned many months ago that the version of VOLD in Froyo does not support anything else but vFAT - so it just won't mount EXT2, or NTFS for that matter.
the mount command would bypass VOLD and we know that NTFS should work, if it's a custom kernel. Conceivably EXT2 should also work, but since it was all manual scripting I just stopped researching it - mainly because I'd still have issues using the card with other devices so it wouldn't really be a portable solution anymore.
As much as I detest FAT32 for its file size limitations, it's still the "standard" between portable devices. The various vendors have yet to figure out a replacement, since they can't seem to agree on anything.
rajeevvp said:
My external SD card is formatted as ext3 and I have no problem using Root Explorer.
Click to expand...
Click to collapse
Figures. Never tried ext3, mainly because it's not a readily available option in Ubuntu. Tried to format to ext3 via the terminal but got a weird error, even after unmounting the drive:
"/dev/sdb is apparently in use by the system; will not make a filesystem here!"
So I booted in to Parted Magic with my netbook, wiped the sdcard, and created a new ext3 partition.
Success!!
The sdcard auto-mounts, and is accessible by Root Explorer, ES File Explorer and File Manager.
Ext3 will suit my purposes just fine. Sorry to make you write all the rest of your post, but it will be a handy reference.
Thank you a million times over!
@ roebeet
I'm humbled this post got your attention. Thanks for the great work!
deadfraggle said:
Figures. Never tried ext3, mainly because it's not a readily available option in Ubuntu.
Click to expand...
Click to collapse
The ext3 format was the default filesystem of Ubuntu, until just recently. It is generally considered better to use ext2 on a SD card. Since a SD card has a limited number of read/writes, a journaling filesystem like ext3/ext4 would use up the limited number of read/writes faster than using ext2. Also, never create a swap partition on a flash drive or SD card.
To format a SD card in Ubuntu, first determine the device name:
Code:
[email protected]:~$ sudo fdisk -l
[sudo] password for paul:
Disk /dev/sda: 64.6 GB, 64609058816 bytes
255 heads, 63 sectors/track, 7854 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x0000d996
Device Boot Start End Blocks Id System
/dev/sda1 * 1 3890 31246393+ 83 Linux
/dev/sda2 3891 7854 31840830 83 Linux
Disk /dev/sdb: 16.4 GB, 16437477376 bytes
255 heads, 63 sectors/track, 1998 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000b3366
Device Boot Start End Blocks Id System
/dev/sdb1 1 1998 16048903+ 83 Linux
My EEEPC has a 64 GB hard drive, and a 16 GB SDHC card. So the card I want to format is /dev/sdb1. Use fdisk again for the formatting, here are the steps copied directly from my terminal:
Run commands with root privileges (sudo).
Find the disk:
# sudo fdisk -l
Format the disk (sdb1):
# sudo fdisk /dev/sdb1
Command (m for help):d (delete any existing partitions)
Command (m for help):n (create a new partition)
Command action
e extended
p primary partition (1-4)
p
Partition number (1-4):1
Command (m for help):w (to write the changes to the disk)
Format the card. You may need to unmount it first:
# sudo umount /dev/sdb1
# sudo mkfs -t ext3 /dev/sdb1

How to mount external usb hdd

I have a small seagate 350gb drive that is formated ntfs by default and whenever I connect it to my gtabcomb. 3.3 g tab it says unknown file size etc, under the settings menu. How can I get my gTablet to recognize my external hard drive? Do I have to type something in terminal? Or install a specific kernel module? (Not even sure what modules are lol)
Sent from my SPH-D700 using XDA Premium App
See this post of mine.
rajeevvp said:
See this post of mine.
Click to expand...
Click to collapse
Hey thanks a bunch for the link, every time i searched in the forums search field for your post it wouldn't show up. I will take a look tonight and try what you suggest in your post from the link.
OK so gtab comb comes with modules already installed, for anyone who needs assistance on using an external hard drive here is a tip.
Read instructions on the link provided in 2nd post, using root explorer I searched for the 2 module files and copied them to my /mnt/sdcard. Then I typed the mount command. You do not have to type the insmod commands fyi those with the modules already moved in your sd card directory. My only problem was that I could not unmount the drive.
not sure why but the command unmount and the /mnt/usbdisk did nothing. I'm going to try again to unmount tomorrow. For the time being I'm just turning tablet off and disconnecting the drive. Hopefully that doesn't mess up my mount commands later on.
Sent from my SPH-D700 using XDA Premium App
juanaraya92679 said:
using root explorer I searched for the 2 module files and copied them to my /mnt/sdcard.
Click to expand...
Click to collapse
Since GtabComb beta already loads the kernel modules required to mount NTFS partitions at boot time, you don't need to copy the .ko files anywhere. Use only the mount command. Note also that NTFS write support is still considered experimental. Periodically check the volume on a Windows machine.
My only problem was that I could not unmount the drive. not sure why but the command unmount and the /mnt/usbdisk did nothing.
Click to expand...
Click to collapse
The command is umount. Did you type unmount instead?
Note: If you can't unmount filesystems on any Unix for any reason, at least issue the sync command a couple of times before you remove disks.
I just realized I typed that wrong, your right I didn't have to copy the files, i just typed the mount command from your post in my terminal.
I have no Idea though why my unmount command doesn't work. Its odd.
juanaraya92679 said:
I have no Idea though why my unmount command doesn't work. Its odd.
Click to expand...
Click to collapse
Did you run the umount command as root?:
Code:
$ [B]su[/B]
# [B]umount /mnt/usbdisk[/B]
rajeevvp said:
Did you run the umount command as root?:
Code:
$ [B]su[/B]
# [B]umount /mnt/usbdisk[/B]
Click to expand...
Click to collapse
New problems. My mount command is working sometimes but I can't access the files for more then five minutes and the drive is only read only. Also is theresomething wrong with wah I'm doing? If I type the first command, mine doesn't look like yours
This is my result.
dmesg | tail -n 20
5042.426489] sd 5:0:0:0: [sdb] Mode Sense: 1c 00 00 00
5042.426508] sd 5:0:0:0: [sdb] Assuming drive cache: write through
5042.440326] sd 5:0:0:0: [sdb] Assuming drive cache: write through
5042.446470] sdb: detected capacity change from 0 to 320072932864
5042.452566] sdb: sdb1
5042.553502] sd 5:0:0:0: [sdb] Assuming drive cache: write through
5042.561727] sd 5:0:0:0: [sdb] Attached SCSI disk
5042.628100] usb-storage: device scan complete
5044.098157] CPU1: Booted secondary processor
5044.098236] CPU0 attaching NULL sched-domain.
5044.147888] CPU0 attaching sched-domain:
5044.147898] domain 0: span 0-1 level CPU
5044.147905] groups: 0 1
5044.147918] CPU1 attaching sched-domain:
5044.147923] domain 0: span 0-1 level CPU
5044.147929] groups: 1 0
5050.434094] CPU0 attaching NULL sched-domain.
5050.434148] CPU1 attaching NULL sched-domain.
5050.548048] CPU0 attaching NULL sched-domain.
5050.549682] CPU1: clean shutdown
I have been using seagate 500gb and it works best when the charger is plugged into the tablet, I thing it needs the extra power to keep it operating smoothly. You would not think that the power would be an issue, but it works for me. I was experiencing the same issues.
I had the power plugged in and still it would recognize the drive for only like 5 minutes and then it wouldn't let me access the files on the drive after. The unmount and mount commands keep saying invalid directory. Doesnt make sense. I'm no pro at command prompts but i know how to copy now paste which i'm doing pretty well. One other issue I found was that my drive shows as read only when i mount it for the 5 minutes that im allowed to. How do I mount it as read/write? My goal here is to transfer pictures and movies to and from my tablet.
Is there a way to make scripts that auto mount so i don't have to type in the commands manually everytime i connect the stupid drive?
Sent from my SPH-D700 using XDA Premium App
If the device name has changed from /dev/block/sda1 to /dev/block/sdb1, then you'll have to change the mount command in the example to follow suit.
The fact that the kernel changed the device name on its own is troubling. Linux does this for only 2 reasons.
1. When somebody unplugs a disk drive without first unmounting it. Then, when the disk is replugged, the kernel will assign a new device name because the old one is still being used (not unmounted).
2. The drive disconnects on its own due to some kind of hardware fault or peculiarity (external drives going to sleep without informing the kernel properly is a good example) and then reconnects on it own. In this case too, a new device will be assigned to the same device.
In either case, I would like to see some error messages. When you notice problems, rerun that dmesg command without the tail and send me the dmesg.txt that results:
Code:
$ [B]dmesg | tee /mnt/sdcard/dmesg.txt[/B]
However, I would suggest you do this if you want to read and write files on your external USB HDD.
1. Connect the drive to a Windows PC, then run a chkdsk or equivalent on it immediately.
2. Keep it connected to the Windows PC, but, share the drive.
3. Access the drive on the gTablet using CIFS Manager. You get both proper read and write access this way. As I mentioned in my post, you can read things just fine using the NTFS kernel module, but, writing could be dangerous.
Coming to automounting:
It's fairly easy to modify the vold program to automount NTFS filesystems too, just like it automatically mounts the extn and VFAT filesystems. The problem is checking the filesystem before mounting it. For both the latter 2 filesystem types, the filesystem checker programs are present on the gTablet and they are run prior to the filesystems being mounted. Native, full-featured, NTFS checkers do not yet exist anywhere except on Windows, so you would be taking a risk mounting an unchecked NTFS filesystem with a modified vold. Your best bet is to go with what I suggested: connect the HDD to a Windows or Linux PC and then use CIFS or NFS to access it.

How to partition Bootable SDcard from Windows 7

Here is a paste of the command line instructions to format a bootable sd card for the nook tablet for use with CWM recovery image. It uses only Native Windows 7 tools and nothing that does not ship with windows 7.
This tool is called diskpart and is a little known command line partitioning tool similar to Fdisk that ships with Windows 7.
I though this might help people who are not good with Linux.
Microsoft DiskPart version 6.1.7601
Copyright (C) 1999-2008 Microsoft Corporation.
On computer: MYLAPTOP
DISKPART> list disk
Disk ### Status Size Free Dyn Gpt
-------- ------------- ------- ------- --- ---
Disk 0 Online 232 GB 0 B
Disk 1 Online 238 MB 0 B
DISKPART> list disk
Disk ### Status Size Free Dyn Gpt
-------- ------------- ------- ------- --- ---
Disk 0 Online 232 GB 0 B
Disk 1 Online 238 MB 0 B
DISKPART> select disk 1
Disk 1 is now the selected disk.
DISKPART> clean
DiskPart succeeded in cleaning the disk.
DISKPART> create part primary size=50
DiskPart succeeded in creating the specified partition.
DISKPART> list part
Partition ### Type Size Offset
------------- ---------------- ------- -------
* Partition 1 Primary 50 MB 64 KB
DISKPART> select part 1
Partition 1 is now the selected partition.
DISKPART> format
100 percent completed
DiskPart successfully formatted the volume.
DISKPART> list part
Partition ### Type Size Offset
------------- ---------------- ------- -------
* Partition 1 Primary 50 MB 64 KB
DISKPART> list volume
Volume ### Ltr Label Fs Type Size Status Info
---------- --- ----------- ----- ---------- ------- --------- --------
Volume 0 E DVD-ROM 0 B No Media
Volume 1 C laptopboot NTFS Partition 158 GB Healthy Boot
Volume 2 G NTFS Partition 73 GB Healthy
Volume 3 System NTFS Partition 1500 MB Healthy Hidden
* Volume 4 D FAT Removable 50 MB Healthy
DISKPART> active
DiskPart marked the current partition as active.
DISKPART> rescan
Please wait while DiskPart scans your configuration...
DiskPart has finished scanning your configuration.
DISKPART>

[Q] How to mount (exFAT?) sd card that isn't being recognized automatically anymore?

I bought this 64GB SanDisk sd card (http://www.amazon.com/SanDisk-microSDXC-Memory-Adapter-SDSDQUA-064G-U46A/dp/B007WTAJTO) which was working fine in my stock ROM for a few weeks. I then flashed a custom ROM (latest stable Resurrection Remix) that didn't recognize it. When I immediately flashed back to the stock ROM it also didn't recognize the card anymore. Surely that's not an issue of physical damage, as the timing would be quite coincidental! Something happened while installing that custom ROM to change maybe partition tables or whatever on that sd card.
What tells me for sure that the card is NOT physically damaged is that I can successfully store nandroid backups to it and restore from nandroid backups on it, but only from ClockworkMod Recovery 5.5.*. I've tried many other recoveries (even the newer, touch-based ClockwordMod Recoveries), as well as a couple more ROMs and nothing else recognizes the drive at all. But clearly the drive itself isn't damaged. Unfortunately ClockworkMod Recovery 5.5.* doesn't have any sort of ability to let me connect to my computer in USB mass storage mode or otherwise get the data off of the card
I was able to restore data from the a disk dump of the card using 'photorec' recovery but it restored every one of the 90,000 files on that card (even though only about 1,000 are the ones I actually need and not 'system' or 'backup' files) into a restore directory where every file name is named like f3728467371291.gz and with all the same timestamps, so it would take me forever to figure out which files are mine, so mounting the drive would really help.
I also realize using this card with my Android may have been risky in the first place, see http://www.transformerforums.com/forum/general-discussion/28678-sandisk-64gb-microsd-woes.html, but it was working successfully and the card itself isn't damaged so there must be a way to get the data off in a sane way. (I won't use this card in future with my Android.)
I put the sd card into my Ubuntu 12.04 laptop and it didn't get recognized automatically like what happens with other sd cards. So I dig some digging and it says that the card (at /dev/mmcblk0, with partition /dev/mmcblk0p1) is 'HPFS/NTFS/exFAT' in the output below (but first I took a 'dd' disk images of both the whole card, mmcblk0, and the partition, mmcblk0p1).
Any help you could provide would be greatly appreciated. Thanks!
Code:
$ sudo dd if=/dev/mmcblk0 of=~/mmcblk0
$ sudo dd if=/dev/mmcblk0p1 of=~/mmcblk0p1
$ sudo fdisk -l ~/mmcblk0
Disk mmcblk0: 63.9 GB, 63864569856 bytes
255 heads, 63 sectors/track, 7764 cylinders, total 124735488 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
mmcblk0p1 32768 124735487 62351360 7 HPFS/NTFS/exFAT
Trying to mount as NTFS but get error:
Code:
$ sudo mount -t ntfs ~/mmcblk0p1 /mnt/sdcard
NTFS signature is missing.
Failed to mount '/dev/mmcblk0p1': Invalid argument
The device '/dev/mmcblk0p1' doesn't seem to have a valid NTFS.
Maybe the wrong device is used? Or the whole disk instead of a
partition (e.g. /dev/sda, not /dev/sda1)? Or the other way around?
Trying to mount as exFAT but get error:
Code:
$ sudo apt-add-repository ppa:relan/exfat
$ sudo apt-get update
$ sudo apt-get install fuse-exfat
$ sudo mount -t exfat ~/mmcblk0p1 /mnt/sdcard
FUSE exfat 0.9.8
ERROR: exFAT file system is not found.
Getting some info about the whole card:
Code:
$ sudo file -s ~/mmcblk0
/dev/mmcblk0: x86 boot sector; partition 1: ID=0x7, starthead 10, startsector 32768, 124702720 sectors, extended partition table (last)\011, code offset 0x0
Getting some info about the partition:
Code:
$ sudo file -s ~/mmcblk0p1
/dev/mmcblk0p1: x86 boot sector, code offset 0x52
Do you have any idea how I could mount this card successfully?
Hi,
could you find a solution for your problem? It seems I have a similar one. My 32GB SD is perfectly working when I use ext3/4 but not using exfat.
I have no idea how to fix it. Using ext3/4 is not the best solution due to different ownerships, permissions ecc.
Regards,
Enkidu

Categories

Resources