[Q] FLAC files disappearing from SD Card? - Sprint Samsung Galaxy S III

Hi guys I just purchased the Samsung 64gb micro sd card and I'm having some issues.
I just copied over ~45 gb of FLAC music to the sd card using two different methods. 1) Taking the sd card out and using a sd to usb adapter and 2) plugging the phone into my computer via usb.
Both times all of the files copied over without any error or interruptions and after I put the sd card in my phone and booted it up I can't detect any of the files from Shuffle or ES File Explorer
So I plugged the sd card back into my computer and both times all of the folders are empty and none of the FLAC files are present. I ran diskcheck on the sd card and it said it fixed all of the errors but all of the FLAC files are still missing... Now I just have a folder called FOUND.000 on the root with a bunch of .chk files in it that are about the size of an album of FLAC music (~300mb)
What is going on...?

Jessooca said:
Did you by any chance get an error when copying the files over ? Such as a semaphore error? Were you using Windows to copy files or teracopy?
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
I used Windows Explorer to copy the files over. It looks like I have either a counterfeit or defective card. I ran SD Insight and H2testw on it and both returned obviously suspicious results.
sdinsight:
Manufacturer: Invalid (0x00)
OEM/Application ID: Unknown
Product Name:
Product Revision: 0.0
Serial #: 0xbd0c
Manufacture Date: Jan 2014
CRC7: OK
Size: 67GB
SD Card Specification: SD Physical Layer Version 2.00
CPRM Security Support: No Securit
Click to expand...
Click to collapse
H2testw:
Warning: Only 63907 of 63998 MByte tested.
The media is likely to be defective.
3.5 GByte OK (7486168 sectors)
58.8 GByte DATA LOST (123395368 sectors)
Details:41.5 MByte overwritten (85104 sectors)
0 KByte slightly changed (< 8 bit/sector, 0 sectors)
58.7 GByte corrupted (123310264 sectors)
60 KByte aliased memory (120 sectors)
First error at offset: 0x00000000c65db000
Expected: 0x00000000c65db000
Found: 0x0000000000000000
H2testw version 1.3
Writing speed: 3.80 MByte/s
Reading speed: 6.64 MByte/s
H2testw v1.4
Click to expand...
Click to collapse

Here is a copy of the email I sent the eBay user:
I have reason to believe the Samsung 64gb micro sd card that you sold me is counterfeit.
I first had a hunch this item was counterfeit when I copied 45gb of data to the card two separate times just to have it all erased/corrupted immediately after putting it in my phone.
After this happened, I decided to download an Android app called sd insight to see if the card was fake or not. These are the results I received from running the app: http://pastebin.com/RfG0JREq
As you can see in that log file, the manufacturer, product name, revision number, etc are all null. This led me to believe that the card you sold me was certainly counterfeit. If this was a legitimate card the entries would have reported things such as SAMSUNG and MB-MGCGB/AM. (The supposed make and model of this sd card) Additionally, there would be at least 1 revision to this card to counter the data corruption issues that was occurring to S3 and S4 smart phones in 2013 since it was manufactured (supposedly) in January of 2014.
In order to be sure for certain before I contacted you with this claim, I used a program called H2testw. H2testw is a program that writes data files to your sd card and reads them off until every sector has been tested. If corruption occurs you have an sd card error. Additionally, you can see the actual size of the sd card and many other cool things. Here is the log file that the program returned to me: http://pastebin.com/X8e0R6TM
As you can see, this card is actually only 3.5GB instead of 62.4 like reported by Windows Explorer. This leads me to believe this card has been hacked to report the incorrect capacity size. 58.8GB of data was lost because it was written to sectors which actually don't exist... This is proven by the hex address given by the location of the first error.
As you can see, it expects to encounter 0x00000000c65db000 but instead encounters 0x0000000000000000 when trying to copy data to that specific location. This is because that location doesn't exist....
Finally, you can see that the writing speed is only 3.8mb/s instead of 7mb/s and the reading speed is only 6.64mb/s instead of 24mb/s. This is another clear sign of a fraudulent item.
You sold me a class 4 3.5GB sd card in disguise of a class 10 64gb sd card. I would like for this item to be replaced with a legitimate Samsung 64gb class 10 micro sd card at no extra expense to me. This includes reimbursing my return shipping fees if you desire the item to be returned to you before continuing.
Click to expand...
Click to collapse

Related

[Q] "SD Card blank or has unsupported file system"

So I downloaded the latest OTA update last night, and it installed just fine (phone worked fine, etc). I went to bed later last night, then when I woke up this morning, I got a "SD Card blank or has unsupported file system" message!
The first message I got was actually something a bit different. Unfortunately, I can't remember exactly what it was, but I clicked on the notification and it tried to do something with the SD Card (probably remount it or something), and ever since I've been getting the "SD Card blank or has unsupported file system" thing.
Now my only option given when I click on this notification is to format the SD Card. This is really annoying; I don't want to format my card and lose all the data! Are there any 'fixes' for this? I noticed a lot of people had this problem with the original HTC Desire.
P.S. I haven't rooted my phone or anything like that, so that wouldn't be an issue.
Edit: I tried all the usual stuff such as rebooting, taking the battery out, reseating the mem card, etc, numerous times to no avail. I got so tired of it that I just tried the format option, but it won't even let me format it! It just does nothing after I click it.
Have you tried the card on your PC using an external reader?
sent using my thumbs
maddler said:
Have you tried the card on your PC using an external reader?
sent using my thumbs
Click to expand...
Click to collapse
Yep, it just says "Insert a disk into Drive F", but it even says that with a backup card which does work with my phone... so I'm thinking there's a driver or a hardware problem with my USB micro SDHC adapter.
So I put the card into a regular SD adapter, then put that into my laptop's SD card reader and it recognised it. I'm now trying to recover any files I can, as the partition seems to be messed up (needs reformating). Anyone know what the best software for recovering data is?
Same thing happened too mee. Dont know why.
Got off the phone with a HTC rep a few hours ago. HTC will be sending me a new SD Card tomorrow, and have escalated this problem as well as that of the text messages up to the engineering department.
UK customers, try contacting them through here first (no spaces): htc.com /uk/ cs_mail.aspx
Make sure you inform them that other SD cards work fine with your phone, and that the SD card is unreadable in other readers too. That way they know it's not your phone.
Hey all,
I had the same Problem: SD Card blank / unsupported filesystem...
This happened when I used the factory restore option and checked the CheckBox to wipe all data on SD Card...
Phone rebooted - problem was there
Long research...
What I figured out so far:
there seems to be an issue on the DHD with the "format SD" option as far as I read, this is caused due a Software bug...
I am using the following Custom ROM: Modified CyanogenMod 7.0 Beta Nightly #31 (Feb. 9, 2011) Download (Server DE, Europe) | MIRROR (Server DK, Europe) which can be found @ http://forum.xda-developers.com/showthread.php?t=918639
But other users stated they had the issue also with the "Official" release....
Here the solution worked for me:
just put the SD Card in a BlackBerry Phone and format it using the BB (it was poping up when I inserted the card stating no filesystem and it asked me to format the SD Card - i did so...) - action took me less than 2 mins and Card is now accepted again in my DHD.
I would advice not to use the internal functions of DHD to format any SD card - best way I presume is using the USB-Data connection and format it from the PC.
--------------------------------------------
following Post I found at some other forum (not tested as I have no card reader) thanks @flopasques (autor):
1) Install this tool on your computer : http://www.sdcard.org/consumers/formatter_3
1) Mount the SD card (notifications on the HTC).
2) Don't click any button if Windows displays a pop-up (where it asks you if you want to format). Let this pop-up opened.
3) Open the Panasonic tool and format your SD Card (Quick format is working well).
4) Close the pop-up (if applicable).
5) Unmount the card from the notifications.
6) Remove the card and reinsert it in the phone.
7) Now, it should be correctly detected.
--> Never use the format option on HTC phones, that's my only advice !
Hope this bring some light into the darkness
Posts regarding this I found on XDA forum (not all of them are for the DHD but might contain some helpfull info):
http://forum.xda-developers.com/sho....xda-developers.com/showthread.php?p=11072352
http://forum.xda-developers.com/showthread.php?t=698193
http://forum.xda-developers.com/showthread.php?t=588766
many tnx for your efford but didnt work for me
the card was formatted with the blackberry but neither my pc or my htc managed to reckognise it
greetings
karlanal said:
many tnx for your efford but didnt work for me
the card was formatted with the blackberry but neither my pc or my htc managed to reckognise it
greetings
Click to expand...
Click to collapse
Try formatting with windows, select type of filesystem as fat instead of fat32.. Works for me, and i noticed even faster write access speed.. about 4-5MB/sec on class 2 sandisk 4gb..
The problem in my case was the SD card didn't have a valid partition table. Here's how I solved the problem on a rooted Samsung Captivate running Cyanogen 7 (it should work on other versions):
Enter adb shell, insert the SD card into the slot and type:
# dmesg
This returns kernel messages. Look at the end, it will tell you what device was inserted with additional information:
<7>[22821.137721] sdhci: card inserted.
<7>[22821.336235] Universal : Card status 1
<6>[22822.591613] mmc2: new high speed SDHC card at address b368
<6>[22822.598715] mmcblk1: mmc2:b368 46608 15.4 GiB
<6>[22822.601085] mmcblk1: unknown partition table
Take note of the device, in this case it's "mmcblk1"
Now use fdisk to create a new partition table like this:
# fdisk /dev/block/mmcblk1
Create a new empty DOS partition table:
Command (m for help): o
Create a new primary partition:
Command (m for help): n
Command action
e extended
p primary partition (1-4)
p
Partition number (1-4): 1
First cylinder (1-505824, default 1): enter
Last cylinder or +size or +sizeM or +sizeK (1-505824, default 505824): enter
Print the partition table and review the changes:
Command (m for help): p
Disk /dev/block/mmcblk1: 16.5 GB, 16574840832 bytes
4 heads, 16 sectors/track, 505824 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk1p1 1 505824 16186360 83 Linux
Note that mmcblk1p1 is partition 1 on mmcblk1.
Write the partition table to disk and exit:
Command (m for help): w
Power cycle your phone so it properly re-reads the partition table and go into Settings, Storage and format/mount your card.
or the easiest u guys can do is "FULL FORMAT" not quick format but full format ur sd card using FAT32
Resolved!
In case you want to recover data from your "dead" SD card:
This morning I was also surprised with the evil "SD Card blank or has unsupported file system" message. Restarting my Desire HD did not fix the issue. So I removed the SD card and put it in a Windows PC, but even the PC did not recognise the card. Windows simply persisted that the drive was empty. I began to fear that many MANY great pictures of my kids would be lost forever...
A friend of mine suggested trying the "GetDataBack" tool for Windows. So I installed it and started it while my SD was in the PC (even though Windows thought is was not). After a long wait the tool actually noticed that there was indeed a volume in the SD drive! I continued on to the next step and "GetDataBack" actually started reading my SD card! It reported a few broken sectors, and then it really got busy! After half an hour (16GB card) I was presented a complete directory structure of my SD. I could even view all the pictures I took
I quickly purchased "GetDataBack" so I could copy the files from my SD. This worked perfectly! I was able to recover ALL my files!
So then I was still stuck with this dead SD card. Clicking "format" on my phone simply did nothing. Windows wouldn't format it either, as it was convinced that there was no disk in the drive. I tried an old Nokia phone, an old digital camera without success. I finally put the SD card in my relatively new digital camera (Canon Powershot SX200) and it was able to format my SD card without any problems!!! After that Windows would happely accept my SD card, so I formatted it again. Finally I copied all my files back on the SD card, and that was all...
Back in business! All I need to do now, is get a decent backup application ASAP.
If you intend to use "GetDataBack" to do the same as I did... make sure to wait as long as it takes, even when the application (or even Windows) may seem stuck.
Good luck!
rett78 said:
The problem in my case was the SD card didn't have a valid partition table. Here's how I solved the problem on a rooted Samsung Captivate running Cyanogen 7 (it should work on other versions):
Enter adb shell, insert the SD card into the slot and type:
# dmesg
This returns kernel messages. Look at the end, it will tell you what device was inserted with additional information:
<7>[22821.137721] sdhci: card inserted.
<7>[22821.336235] Universal : Card status 1
<6>[22822.591613] mmc2: new high speed SDHC card at address b368
<6>[22822.598715] mmcblk1: mmc2:b368 46608 15.4 GiB
<6>[22822.601085] mmcblk1: unknown partition table
Take note of the device, in this case it's "mmcblk1"
Now use fdisk to create a new partition table like this:
# fdisk /dev/block/mmcblk1
Create a new empty DOS partition table:y
Command (m for help): o
Create a new primary partition:
Command (m for help): n
Command action
e extended
p primary partition (1-4)
p
Partition number (1-4): 1
First cylinder (1-505824, default 1): enter
Last cylinder or +size or +sizeM or +sizeK (1-505824, default 505824): enter
Print the partition table and review the changes:
Command (m for help): p
Disk /dev/block/mmcblk1: 16.5 GB, 16574840832 bytes
4 heads, 16 sectors/track, 505824 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk1p1 1 505824 16186360 83 Linux
Note that mmcblk1p1 is partition 1 on mmcblk1.
Write the partition table to disk and exit:
Command (m for help): w
Power cycle your phone so it properly re-reads the partition table and go into Settings, Storage and format/mount your card.
Click to expand...
Click to collapse
Hi I have a question, does this works for internal or external sd cards? I have the same trouble with internal sd card, but the only way I can connect it to pc is through the cellphone
I dropped my Desire HD, and there was a big dent on the back over, exactly where the SD card sits. Since then, I've had this problem. I figured that the SD card probably got shock damage, so I bought another one. It was a Sandisk 8Gb, and when I put it in, all was well. 10min later I checked my phone, and the same thing happened!
Now I'm thinking that there is something wrong with my phone. I was going to claim on insurance, but I tried the 2Gb card from my old Hero (Sandisk 2Gb) and it works fine.
Is there any differences between the 2Gb and 8Gb that would make the 8Gb not work?
Is my phone buggered?
hammernl said:
In case you want to recover data from your "dead" SD card:
If you intend to use "GetDataBack" to do the same as I did... make sure to wait as long as it takes, even when the application (or even Windows) may seem stuck.
Good luck!
Click to expand...
Click to collapse
Hey, thanks for the tip. I've tried a few, and this seems by far the best one out there.
The problem is, it takes too long, and I mean TOOOOO long. I left it overnight and it was still going. So I came back in the evening....... still going!
I've set the options to 'Recover deleted files', and it is scanning now. When I set the options that you use for a new operating system installation, it takes forever.
It recognises my SD card, but only sees an 8Gb card as being 500Mb :-(
In case you need to recover the data, this small green ware will do the work for you.
Enjoy!
I am facing similar problem in unrooted HTC desire S
rett78 said:
The problem in my case was the SD card didn't have a valid partition table. Here's how I solved the problem on a rooted Samsung Captivate running Cyanogen 7 (it should work on other versions):
Enter adb shell, insert the SD card into the slot and type:
# dmesg
This returns kernel messages. Look at the end, it will tell you what device was inserted with additional information:
<7>[22821.137721] sdhci: card inserted.
<7>[22821.336235] Universal : Card status 1
<6>[22822.591613] mmc2: new high speed SDHC card at address b368
<6>[22822.598715] mmcblk1: mmc2:b368 46608 15.4 GiB
<6>[22822.601085] mmcblk1: unknown partition table
Take note of the device, in this case it's "mmcblk1"
Now use fdisk to create a new partition table like this:
# fdisk /dev/block/mmcblk1
Create a new empty DOS partition table:
Command (m for help): o
Create a new primary partition:
Command (m for help): n
Command action
e extended
p primary partition (1-4)
p
Partition number (1-4): 1
First cylinder (1-505824, default 1): enter
Last cylinder or +size or +sizeM or +sizeK (1-505824, default 505824): enter
Print the partition table and review the changes:
Command (m for help): p
Disk /dev/block/mmcblk1: 16.5 GB, 16574840832 bytes
4 heads, 16 sectors/track, 505824 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk1p1 1 505824 16186360 83 Linux
Note that mmcblk1p1 is partition 1 on mmcblk1.
Write the partition table to disk and exit:
Command (m for help): w
Power cycle your phone so it properly re-reads the partition table and go into Settings, Storage and format/mount your card.
Click to expand...
Click to collapse
I'm also having the same problem like this guy. my HTC desire S once showed "micro SD card removed unexpectedly and after that it shows Blank SD card. I checked the card in laptop and in other mobile,it runs. but I've tried 3 cards in my mobile but it shows Blank SD card again and again. I've done master reset and also tried following codes on SDK tool as a guy from androidforums.com suggested me:
fastboot OEM enableqxdm 0
fastboot reboot
though I don't know what are they intend to do.
now my question is, will your method work on my unrooted desire S?
pls check my post here: http://forum.xda-developers.com/showthread.php?t=1607368
SAPPH1RE said:
Try formatting with windows, select type of filesystem as fat instead of fat32.. Works for me, and i noticed even faster write access speed.. about 4-5MB/sec on class 2 sandisk 4gb..
Click to expand...
Click to collapse
Windows 7 does not have an option to format with fat, only fat32
ri123 said:
Windows 7 does not have an option to format with fat, only fat32
Click to expand...
Click to collapse
there's an app called cardtrick used to format digital cam's sdcard to install hack and that has the fat format...
http://chdk.wikia.com/wiki/CardTricks
Format the sd card using your computer. After you do this you may find that the phone still has the same notification. Reboot phone and try formatting again. If your sdcard is in Raw format this should work.

[Q] App2SD Broke / Corrupt SD Card?

I've flashed back to standard FroYo with RUU -RUU_Bravo_Froyo_HTC_WWE_2.29.405.5_Radio_32.49.00.32U_5.11.05.27_release_159811_signed - and all seemed well but I've noticed that when I now move an app over to the SD card using the standard FroYo APP2SD feature the app works fine until I reboot my phone and then it just has a standard android grey icon so it knows its on the SD - but it won't work again...
It's as if my SD card is mounted all the time...
Any thoughts on what I can do to fix this?
How frustrating...
I think this might be down to the new SD card I put in my phone...
Kingston 16GB class 6...
switched back to the SanDisk 8GB class 2 - and apps2sd seems to be working.
google sky maps is still on there after two reboots anyway which the 16gb wasn't.
Does anyway know of any tools to check the SD card for faults before I try and send it back?
someone suggested a chkdsk on it...
chkdsk from windows recovered a FOUND.000 folder with 1530 File(s) 2,805,137,408 bytes of file fragments!
any one have any suggestions of decent SD card checking tools or such or should I just try and send it back?
[edit: just noticed that the 1530 were all my photos and contacts on the SD card ]
[edit2: Anyone know if these tools are any good:
http://www.softwinter.com/storagetools.html ]
[edit3: just saw its for WM only]
done a full windows7 format on it (instead of a quick) and it might, might just be working...
got RAC Traffic on the SD and managed to do a reboot and its still there - which is further than I got before...
nope - still not working - second reboot and it has gone...
interestingly though if i unmount and re-mount the SD it does come back and work...
tried the above again - rebooting (not there) - unmount - re-mount - still not there - annoying...
Sd card test
h2testw: http://mympx.org/Downloads/p13_sectionid/2/p13_fileid/13
results for 1024mb:
Code:
Warning: Only 1024 of 15986 MByte tested.
The media is likely to be defective.
486 MByte OK (995328 sectors)
538 MByte DATA LOST (1101824 sectors)
Details:0 KByte overwritten (0 sectors)
0 KByte slightly changed (< 8 bit/sector, 0 sectors)
538 MByte corrupted (1101824 sectors)
0 KByte aliased memory (0 sectors)
First error at offset: 0x000000001d6b8000
Expected: 0x000000001d6b8000
Found: 0x0000000000000000
H2testw version 1.3
Writing speed: 1.79 MByte/s
Reading speed: 5.56 MByte/s
H2testw v1.4
I'm going to guess from that it's broke'd
A lot of guys on this site have had problems with Kingston cards (you can search for the other topics). Sandisk seems to make good cards, and on the advice of several people here, i purchased a 16gb class 6 A-DATA card and am quite happy with it so far.
Yeah, the more I had problems trying to get it sorted the more research I did into it - Patriot / A-Data / SanDisk seem like the best choices for MicroSD cards ...
I thought Kingston were a pretty decent manufacturer too!
I'm a bit frustrated as I wanted something bigger than the 8gb I had currently, and something that'll last a little while - 16gb/c6 seemed perfect for a decent price too - backed up and wiped my phone...
8 hours later I am flashing back to stock only to spend another few hours confused before going back to my 8gb/c2

Mystery waiting for solution! [MicroSDHC]

Hi well respected xda community!
Recently i faced with a very uncommon card reading/writing problem. Here is the story:
I'm using a Sandisk Micro SDHC Class 4 8Gb card with my HTC Legend (Android 2.2)
When i'm trying to write/copy data to the card i got the "unexpectedly removed SD card" message. Of course at first i thought it just need a format. I did it with default windows 7 format (FAT32 default allocation unit size) but nothing changed.
Here comes the interesting part:
It's not a common card failure, when the card connected to the PC with SD adapter+card reader i can fully use it, write, read, and copy without errors. I made some analysis with proper programs and no bad sector was found. Everything went fine. If i copy data to the card from the PC with card reader its functional with the phone. I can read pdfs, listen to music from SD Card but! if i try to copy an app from the phone or write random data on the card it's get "removed" and i get the error. It's the same on Samsung Monte.
I tried to format it with NTFS, FAT32 32k,16k, 8k, 4k allocation unit size. Tried several applications like: SD Formatter 3.1, MiniTool Partition Wizard etc. to format. And of course i did format with the phone.
Here is what may help:
1.) A good and trusted memory card analyzing program.
2.) Format tips and tricks for android, HTC. (Maybe some awesome free format program will do the trick)
3.) A fully functional microSDHC 8 Gb class 4 - Sector, Cylinder and allocation size log file. (So i can format mine with the exact same numbers.)
4.) A Genius who knows whats the solution If it's you, please let me know!
Later i'll attach the log file from the analyzer and some information about the card. (Currently i'm at work.)
///Sorry if posted in the inappropriate topic, but found this the most related.///
Solving my own problem.
As soon as i get home i'll try this program:
http://www.makeuseof.com/tag/chkflsh-checks-your-flash-drives-on-windows/
And this:
http://crystalmark.info/software/CrystalDiskMark/index-e.html
Also, i found and interesting post:
http://forum.xda-developers.com/showthread.php?t=1010228
Maybe i have to change something with the LBA thingy.
found it
I found a sector error on the memory card. Used Flash Drive/Card Tester and Chkflsh programms. Mystery solved
Closing thread.

issues

I am unable to partion my new 32GB class 10 sd card to ext3/4. I need to partion it for apps2sd but when I do it it will run the process but will format as other instead of ext3/4. any advise. Aslo I have flashed my phone over to the cricket wireless network and I keep getting a hands free actvation screen run every boot, I think it has something to do with sprint. Does anyone know what it is and how to delete so I don't receive that every boot.
Thanks is advance...
bump and over 100 views and no one has an idea ?
So no one has ever had a issue with there sd card not formatting to ext3
32 GB SD Cards done't play well with this phone. It's posted in a lot of places
HipKat said:
32 GB SD Cards done't play well with this phone. It's posted in a lot of places
Click to expand...
Click to collapse
Thanks for the reply, I would under stand that if I was using my phone to partition,but I'm using my computer and when its done it says other format instead of ext3. So I have not got to the phone issue yet lol
jmh033089 said:
Thanks for the reply, I would under stand that if I was using my phone to partition,but I'm using my computer and when its done it says other format instead of ext3. So I have not got to the phone issue yet lol
Click to expand...
Click to collapse
try formating it in recovery. i used the latest smelkus mod recovery to partition my 16gb class 4 about 2 days ago. see if it will work for your card. if it doesn't work there then its probably a card issue
PhxkinMassacre said:
try formating it in recovery. i used the latest smelkus mod recovery to partition my 16gb class 4 about 2 days ago. see if it will work for your card. if it doesn't work there then its probably a card issue
Click to expand...
Click to collapse
did that before I posted, thanks. I have contacted the seller and if I don't get a new one I will get my money back and buy a name brand this time lol
The media is likely to be defective.
1.8 GByte OK (3952533 sectors)
5.4 GByte DATA LOST (11341931 sectors)
Details:0 KByte overwritten (0 sectors)
0 KByte slightly changed (< 8 bit/sector, 0 sectors)
5.4 GByte corrupted (11341931 sectors)
0 KByte aliased memory (0 sectors)
First error at offset: 0x00000000778f2a00
Expected: 0x00000000778f2a00
Found: 0x0000000000000000
H2testw version 1.3
Reading speed: 9.86 MByte/s
H2testw v1.4
might be the card ROFLMAO
HipKat said:
32 GB SD Cards done't play well with this phone. It's posted in a lot of places
Click to expand...
Click to collapse
I have a PNY 32GB class 10 card and had no issues with it.
with out a dought its the card, I'm having so many issues its not even funny...
What is the brand?
Sent from my NookColor using Tapatalk 2

After the root sd card not identified "Samsung sd card corrupted"

I rooted my phone LG G3 D855 6.0 with kingroot&MM.
after the rooted I got error "Samsung sd card corrupted" also the sd card changes from FAT32 to EXFAT.
How can I slove this problem?
Connect your card to PC using card reader then open cmd (command prompt) then type chkdsk your_card_drive /f then press enter. Good Luck [emoji106]
not helped
Is your card opening in PC?
no
I just connect him with adapter
Now the only way i know is you have to recover your data using any good data recovery software then format your card.
---------- Post added at 07:35 PM ---------- Previous post was at 07:32 PM ----------
Or you also can try this method, download AutorunExterminator in your pc and run it while your card is connected then run cmd and type attrib -h -r -s /s /d your_card_letter\*.* press enter.
---------- Post added at 07:38 PM ---------- Previous post was at 07:35 PM ----------
Make sure adapter is not locked it makes your card write protected.
Alexnoj said:
I rooted my phone LG G3 D855 6.0 with kingroot&MM.
after the rooted I got error "Samsung sd card corrupted" also the sd card changes from FAT32 to EXFAT.
How can I slove this problem?
Click to expand...
Click to collapse
Again format it to fat32 see what happen....
I got the very same error, Lg g3 d855 16 Gb . While booted android 6.0 can't see SD card anymore, and I get the same error samsung SD card corrupted. Strange thing is that I can see the card and all files from within TWRP recovery. I can even do back ups to the SD card from TWRP. So I put the SD card into pc and rund cmd.exe and hit the command chkdsk d: / f
As you can see from out put SD card looks good.
From my pc I can read and access all files and folders. No one is missing, and it appears the file paths are ok, as are the sectors.
Any idea how I can read the SD card from within android 6.0?
output:
Code:
C:\Users\joppy>chkdsk d: /f
The type of the file system is exFAT.
Volume Serial Number is 0000-0000
Windows is verifying files and folders...
File and folder verification is complete.
Windows has checked the file system and found no problems.
62480384 KB total disk space.
52065408 KB in 4207 files.
61056 KB in 477 indexes.
0 KB in bad sectors.
256 KB in use by the system.
10353664 KB available on disk.
131072 bytes in each allocation unit.
488128 total allocation units on disk.
80888 allocation units available on disk.
So I did a deeper look and did chkdsk d: / r
Output:
Code:
C:\Users\joppy>chkdsk d: /r
The type of the file system is exFAT.
Volume Serial Number is 0000-0000
Windows is verifying files and folders...
File and folder verification is complete.
Windows is verifying free space...
80888 free clusters processed.
Free space verification is complete.
Windows has checked the file system and found no problems.
62480384 KB total disk space.
52065408 KB in 4207 files.
61056 KB in 477 indexes.
0 KB in bad sectors.
256 KB in use by the system.
10353664 KB available on disk.
131072 bytes in each allocation unit.
488128 total allocation units on disk.
80888 allocation units available on disk.
The only strange thing my eyes spots are the missing of Volume Serial Number. Could that along make card unreadable for android? Seems strange that I can read and access the content of the SD card on my pc, and even back up to the SD card from TWRP recovery.
Any ideas what to do make this SD card work?
joppy said:
I got the very same error, Lg g3 d855 16 Gb . While booted android 6.0 can't see SD card anymore, and I get the same error samsung SD card corrupted. Strange thing is that I can see the card and all files from within TWRP recovery. I can even do back ups to the SD card from TWRP. So I put the SD card into pc and rund cmd.exe and hit the command chkdsk d: / f
As you can see from out put SD card looks good.
From my pc I can read and access all files and folders. No one is missing, and it appears the file paths are ok, as are the sectors.
Any idea how I can read the SD card from within android 6.0?
output:
Code:
C:\Users\joppy>chkdsk d: /f
The type of the file system is exFAT.
Volume Serial Number is 0000-0000
Windows is verifying files and folders...
File and folder verification is complete.
Windows has checked the file system and found no problems.
62480384 KB total disk space.
52065408 KB in 4207 files.
61056 KB in 477 indexes.
0 KB in bad sectors.
256 KB in use by the system.
10353664 KB available on disk.
131072 bytes in each allocation unit.
488128 total allocation units on disk.
80888 allocation units available on disk.
So I did a deeper look and did chkdsk d: / r
Output:
Code:
C:\Users\joppy>chkdsk d: /r
The type of the file system is exFAT.
Volume Serial Number is 0000-0000
Windows is verifying files and folders...
File and folder verification is complete.
Windows is verifying free space...
80888 free clusters processed.
Free space verification is complete.
Windows has checked the file system and found no problems.
62480384 KB total disk space.
52065408 KB in 4207 files.
61056 KB in 477 indexes.
0 KB in bad sectors.
256 KB in use by the system.
10353664 KB available on disk.
131072 bytes in each allocation unit.
488128 total allocation units on disk.
80888 allocation units available on disk.
The only strange thing my eyes spots are the missing of Volume Serial Number. Could that along make card unreadable for android? Seems strange that I can read and access the content of the SD card on my pc, and even back up to the SD card from TWRP recovery.
Any ideas what to do make this SD card work?
Click to expand...
Click to collapse
If you root on MM you must format your sd card as fat32
Anik49 said:
If you root on MM you must format your sd card as fat32
Click to expand...
Click to collapse
MM = marshmallows? don't know the lingo...
Could it be chkdsk / r changed the file system to exfat? SD card was read able in marshmallows until I soft bricked phone. But even after soft bricked was fixed I was able to see and read all files on SD card and back up to SD card from TWRP.
So from working in mm to not working in mm. Will try different solutions during the day and I will make sure to post later here so we either know whats works or don't.

Categories

Resources