Somehow it became invalid in the Android phone. no real idea why.? Problem with low voltage? phone mechanical shock? Do such brand cards simply fail electrically after so few years? Or likely Android bugs or voltage problems?
It asked to be formated in Android and also in Windows PC -> Aborted. Chkdsk /f wont start - no partition / RAW detected.
PhotoRec already recovered some thousands of files - but very messy quite without names. jpg's, gpx, mp3, txt, html, pdf, zip ... many types. Maybe 2/3 of stuff. Most mp3 data broken up in unusuable multiple pieces ....
Is there a chance for better recovery with TestDisk + chkdsk or so?
Starting key question: What is the typical preformatted partition table type of such 32GB Samsung microSD card? "Intel" or "None" ? What is "None"?
"Analyses" with both types fail to see anything reasonable with Quick & Deeper search.
"Intel" doesnt see a partition at all.
Code: Select all
Disk /dev/sdb - 32 GB / 29 GiB - CHS 3891 255 63
Current partition structure:
Partition Start End Size in sectors
Partition sector doesn't have the endmark 0xAA552
"None" parti type shows:
Code: Select all
Disk /dev/sdb - 32 GB / 29 GiB - CHS 3891 255 63
Partition Start End Size in sectors
> P Unknown 0 0 1 3891 197 18 62521344
Code: Select all
Disk /dev/sdb - 32 GB / 29 GiB - CHS 3891 255 63
Partition Start End Size in sectors
P FAT32 0 0 1 3891 197 18 62521344
Boot sector
Bad
Backup boot sector
Bad
Sectors are identical.
A valid FAT Boot sector must be present in order to access
any data; even if the partition is not bootable.
In expert mode and "None" type a manual FAT sector selection (0 ... 4BIGNUMER) + "Proceed" is offered after "Rebuild BS".
Code: Select all
Potential FAT location
FAT - sector - score
>[Proceed ]
Set FAT table location
Code: Select all
Disk /dev/sdb - 32 GB / 29 GiB - CHS 3891 255 63
Partition Start End Size in sectors
P FAT32 0 0 1 3891 197 18 62521344
FAT : 32
Search subdirectory 4882432<upcounting slowly>/62521344 0
--- Then suddenly:
cluster size (0-128) :64 ---> ENTER for default
Disk /dev/sdb - 32 GB / 29 GiB - CHS 3891 255 63
Partition Start End Size in sectors
P FAT32 0 0 1 3891 197 18 62521344
FAT : 32
Search root cluster 12288<upcounting slowly>/976514 1%
--- Then :
P FAT32 0 0 1 3891 197 18 62521344
Cluster 95052, Directory / found ?
Answer Y(es), N(o), Q(uit) or A(bort interactive mode). N or A if not sure.
>drwxr-xr-x 0 0 0 1-Feb-2021 22:20 files
---> Yes
FAT : 32
cluster_size 64 255
reserved 32 65535
sectors 0 65535
total_sect 62521344 4294967295
fat32_length 12272 4294967295
root_cluster 95052 4294967295
free_count uninitialised uninitialised
next_free uninitialised uninitialised
Extrapolated boot sector and current boot sector are different.
Rebuild Boot sector Boot sector
0000 eb3c904d 5357494e .<.MSWIN ffffffff ffffffff ........
0008 342e3100 02402000 4.1..@ . ffffffff ffffffff ........
0010 02000000 00f80000 ........ ffffffff ffffffff ........
0018 3f00ff00 00000000 ?....... ffffffff ffffffff ........
0020 0000ba03 f02f0000 ...../.. ffffffff ffffffff ........
0028 00000000 4c730100 ....Ls.. ffffffff ffffffff ........
0030 01000600 00000000 ........ ffffffff ffffffff ........
0038 00000000 00000000 ........ ffffffff ffffffff ........
0040 800029ac 22c07400 ..).".t. ffffffff ffffffff ........
0048 56b40ebb 0700cd10 V....... ffffffff ffffffff ........
0050 5eeb4641 54333220 ^.FAT32 ffffffff ffffffff ........
0058 2020fe54 68697320 .This ffffffff ffffffff ........
0060 6973206e 6f742061 is not a ffffffff ffffffff ........
0068 20626f6f 7461626c bootabl ffffffff ffffffff ........
0070 65206469 736b2e20 e disk. ffffffff ffffffff ........
0078 20506c65 61736520 Please ffffffff ffffffff ........
0080 696e7365 72742061 insert a ffffffff ffffffff ........
0088 20626f6f 7461626c bootabl ffffffff ffffffff ........
0090 6520666c 6f707079 e floppy ffffffff ffffffff ........
0098 20616e64 0d0a7072 and..pr ffffffff ffffffff ........
00A0 65737320 616e7920 ess any ffffffff ffffffff ........
00A8 6b657920 746f2074 key to t ffffffff ffffffff ........
00B0 72792061 6761696e ry again ffffffff ffffffff ........
00B8 202e2e2e 200d0a00 ... ... ffffffff ffffffff ........
00C0 00000000 00000000 ........ ffffffff ffffffff ........
00C8 00000000 00000000 ........ ffffffff ffffffff ........
00D0 00000000 00000000 ........ ffffffff ffffffff ........
00D8 00000000 00000000 ........ ffffffff ffffffff ........
00E0 00000000 00000000 ........ ffffffff ffffffff ........
00E8 00000000 00000000 ........ ffffffff ffffffff ........
00F0 00000000 00000000 ........ ffffffff ffffffff ........
00F8 00000000 00000000 ........ ffffffff ffffffff ........
0100 00000000 00000000 ........ ffffffff ffffffff ........
0108 00000000 00000000 ........ ffffffff ffffffff ........
0110 00000000 00000000 ........ ffffffff ffffffff ........
0118 00000000 00000000 ........ ffffffff ffffffff ........
0120 00000000 00000000 ........ ffffffff ffffffff ........
0128 00000000 00000000 ........ ffffffff ffffffff ........
P FAT32 0 0 1 3891 197 18 62521344
Directory /
>drwxr-xr-x 0 0 0 1-Feb-2021 22:20 files
Directory /files
drwxr-xr-x 0 0 0 31-Jan-2021 13:00 .
drwxr-xr-x 0 0 0 31-Jan-2021 13:00 ..
>-rwxr-xr-x 0 0 0 6-Feb-2021 00:52 sdcard
There is a emty file "sdcard", which however should be a folder perhaps?
The dates may have indeed been the last usage/modification times?
Dead end? Or a chance to somehow reconstrunct the filesystem?
Wise to use "Write boot sector"?
Or better bet on "Intel" parti type?
After more recovery or not: Is it wise to format the card and use it further? Or is it likely electrically impaired?