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
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
My micro sd card seems to not be working at all.
Have been googling this problem for about a good 2 weeks now.
Reason this happened: was installing a ROM on phone, and I have no idea what happened.
Weird enough though, I was listening to music randomly one night no problem. Morning after I had some blank/unsupported fiel system error on sd card.
Tried many things:
fdisk (gave bad file descriptor error)
DD (read-only file system)
Disk management in windows (shows up, but no options availble. Won't even let me format.)
Device Manager in Windows says I need to troubleshoot USB MASS Storage (Using Microsd card adapter), troubleshoot to no avail.
Diskpart in windows
ChkDsk in Windows as well
fdisk -l output
Code:
Disk /dev/sda: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders, total 976773168 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: 0x000255e5
Device Boot Start End Blocks Id System
/dev/sda1 2048 67583 32768 83 Linux
/dev/sda2 67584 1116159 524288 82 Linux swap / Solaris
/dev/sda3 1116160 976773167 487828504 83 Linux
Disk /dev/sdd: 15.8 GB, 15829303296 bytes
256 heads, 63 sectors/track, 1916 cylinders, total 30916608 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
/dev/sdd1 * 2048 30916607 15457280 c W95 FAT32 (LBA)
When I try mounting /dev/sdd
Code:
mount /dev/sdd /media/usb1
mount: block device /dev/sdd is write-protected, mounting read-only
mount: you must specify the filesystem type
flash back to odin...
I had a S3 i9300 and I want to check if I can recover some files from data partition
after a hard reset.
I have been able to get an image of data partition with
Code:
adb pull /dev/block/mmcblk0p12 mmcblk0p12.img
My problem is to mount this image on linux.
I tried of course:
Code:
mount -o loop,ro -t auto mmcblk0p12.img ./galaxys3/
but I get ..
mount: wrong fs type, bad option, bad superblock on /dev/loop0,
missing codepage or helper program, or other error
I tried to understand what was going on with fdisk ...
Code:
# fdisk -l mmcblk0p12.img
Disk mmcblk0p12.img: 11.5 GiB, 12381585408 bytes, 24182784 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
and it doesn't seem to find a partition and give the offset.
anyway android mount that block like that ...
Code:
/dev/block/mmcblk0p12 /data ext4 rw,nosuid,nodev,noatime,barrier=1,journal_async_commit,data=ordered,noauto_da_alloc,discard 0 0
any suggestions?
Anyway my goal is to run testdisk (photorec) on it.
TIA.
The fs will be in ext*. Android isnt linux, thats why it works on android and not linux. That's why android needs busybox.
Sent from my HTC One M9 using Tapatalk
shivadow said:
The fs will be in ext*. Android isnt linux, thats why it works on android and not linux. That's why android needs busybox.
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
Actually I manage to mount it on linux. I forgot to unmount the data partition
before make the image so it wasn't consistent ... I made a e2fsck and now I can easily
mount it.
Howdy. Just a question: if I select "use as internal memory" for my 128 GB SD card I inserted in my Nokia 1, does that mean I won't be able to access the said SD card if I try to plug the Nokia 1 to a PC?
Jem2291 said:
Howdy. Just a question: if I select "use as internal memory" for my 128 GB SD card I inserted in my Nokia 1, does that mean I won't be able to access the said SD card if I try to plug the Nokia 1 to a PC?
Click to expand...
Click to collapse
Hi,
I've used an 8 Gig SanDisk MicroSD card as internal memory on my Nokia 1.
The short answer to your question is no, probably not. at least not without a bit of effort.
I just plugged the SD card into a Linux box, which give me the below data
Code:
[[email protected] ~]$ sudo fdisk -l /dev/sdc
Disk /dev/sdc: 7.4 GiB, 7948206080 bytes, 15523840 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
Disklabel type: gpt
Disk identifier: 98FA1F61-0482-4F31-A074-73550CC9B369
Device Start End Sectors Size Type
/dev/sdc1 2048 34815 32768 16M unknown
/dev/sdc2 34816 15523806 15488991 7.4G unknown
[[email protected] ~]$
[[email protected] ~]$
[[email protected] ~]$
[[email protected] ~]$ sudo gdisk -l /dev/sdc
GPT fdisk (gdisk) version 1.0.3
Partition table scan:
MBR: protective
BSD: not present
APM: not present
GPT: present
Found valid GPT with protective MBR; using GPT.
Disk /dev/sdc: 15523840 sectors, 7.4 GiB
Model: USB3.0 CRW -SD
Sector size (logical/physical): 512/512 bytes
Disk identifier (GUID): 98FA1F61-0482-4F31-A074-73550CC9B369
Partition table holds up to 128 entries
Main partition table begins at sector 2 and ends at sector 33
First usable sector is 34, last usable sector is 15523806
Partitions will be aligned on 2048-sector boundaries
Total free space is 2014 sectors (1007.0 KiB)
Number Start (sector) End (sector) Size Code Name
1 2048 34815 16.0 MiB FFFF android_meta
2 34816 15523806 7.4 GiB FFFF android_expand
When I plugged it into one of my Win10 boxes and it just offered to format it for me.
I'm not sure what file system is in use as it was reported as unknown. You'll need to figure out what file system is in use and install whatever tools your PC OS needs to work with that file system.