1

It's my android phone SD card which was indicated damaged by android yesterday night, out of the blue! I put it directly to a USB port with a USB SD card holder case, so in that way I can recover it with TestDisk, which I had experienced before on a similar situation.

I also noticed that there is a change in file system and capacity:

File System : RAW
Capacity : 0 (unknown capacity)

Also TestDisk doesn't show it on its partitions list. A 2 GB SD card is not that important in price but I've a lot of files and medias which I need them.

Used a mini card reader, TestDisk displayed it on its list but a quick search and or a deep search doesn't have any results No partition found or selected for recovery and then I should quit the program.

Your help is appreciated.

Update #2

lsusb output:

Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 002: ID 04f3:0234 Elan Microelectronics Corp. 
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 002: ID 058f:6366 Alcor Micro Corp. Multi Flash Reader
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 009 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 008 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 007 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 006 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
27
  • Okay, this is Ask UBUNTU - Linux Mint is not ubuntu. So this is off topic, and should be asked on Unix & Linux
    – Tim
    Aug 20, 2014 at 8:14
  • @Tim Okay, it's not linux mint. I deleted that part.
    – revo
    Aug 20, 2014 at 8:19
  • Okay, can you edit to include the output of lsusb
    – Tim
    Aug 20, 2014 at 8:21
  • @Tim output added.
    – revo
    Aug 20, 2014 at 8:27
  • Does it change if you remove the device?
    – Tim
    Aug 20, 2014 at 8:27

2 Answers 2

1

Have you looked to see what the Kernel is saying about the device. Plug the device into your computer and run the command dmesg. May shed some light on the situation. You should see references to sdx at the end of the output.

Edit to reflect OP's comment below...

Fire up a terminal. Stick the card in and then run dmesg look at the last few lines of output you should see references to sdx (x being another letter.)

As an example this is what I get:-

[67680.024208] sd 4:0:0:0: [sdb] 7778304 512-byte logical blocks: (3.98 GB/3.70 GiB)
[67680.026448] sd 4:0:0:0: [sdb] No Caching mode page found
[67680.026453] sd 4:0:0:0: [sdb] Assuming drive cache: write through
[67680.029934] sd 4:0:0:0: [sdb] No Caching mode page found
[67680.029939] sd 4:0:0:0: [sdb] Assuming drive cache: write through
[67680.031738]  sdb: sdb1
[67820.022977] sdb: detected capacity change from 3982491648 to 0
[67825.064523] sd 4:0:0:0: [sdb] 7778304 512-byte logical blocks: (3.98 GB/3.70 GiB)
[67825.066735] sd 4:0:0:0: [sdb] No Caching mode page found
[67825.066740] sd 4:0:0:0: [sdb] Assuming drive cache: write through
[67825.069400] sd 4:0:0:0: [sdb] No Caching mode page found
[67825.069405] sd 4:0:0:0: [sdb] Assuming drive cache: write through
[67825.071265]  sdb: sdb1

[67825.445884] FAT-fs (sdb1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.

I can see my card is detected and assigned as sdb with a FAT partition as sdb1.

Edit 2...

Have you tried to force a mount?

Create mount point. sudo mkdir /media/mysdcard try a force mount. sudo mount /dev/sdc1 /media/mysdcard -o force

You may need to specify the filesystem type with the -t flag. I don't know what filesystem Android uses. I guess it may be an ext? (Turns out the sdcard is vfat) In any case add the -t filesytemtype flag immediately after mount. As in sudo mount -t vfat /dev/sdc1 /media/mysdcard -o force

Have a look at this article https://help.ubuntu.com/community/Mount/USB

If it works grab all the data you can off the card.

3
  • Exactly what should I look at there?
    – revo
    Aug 24, 2014 at 10:37
  • Yes, [ 1905.643578] sd 13:0:0:0: [sdc] Device not ready [ 1905.643592] sd 13:0:0:0: [sdc] [ 1905.643596] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE [ 1905.643599] sd 13:0:0:0: [sdc] [ 1905.643602] Sense Key : Not Ready [current]
    – revo
    Aug 24, 2014 at 10:38
  • It's in /dev/sdc. It's in Disk but not in gparted as it gives error.
    – revo
    Aug 24, 2014 at 10:39
0
+100

So as discussed in the comments of the question itself newer android devices use the Media Tranfer Protocol or MTP for short. Using testdisk to restore a MTP sdcard will not work since testdisk (as far as I know) does not support MTP.
Instead you should use a tool that can restore MTP sdcards.

CWM (ClockWorkMod) Recovery is such a tool. Doing a formatting using this tool is a method to fix your sdcard.

You'll need to do is install it onto your phone. Next up is booting into CWM recovery and selecting "mounts and storage" -> "format sdcard".
Let it run and you're done.

CWM recovery screen 1
CWM recovery screen 2

1
  • I should add that, I had recovered my most important data with EaseUs after formatting. Thanks
    – revo
    Aug 25, 2014 at 5:49

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .