• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Samsumg 16gb Micro SD Card gets damaged afrer every restart

R

robertjw4688

Member
I'm using a rooted ZTE Force with clockword mod recovery and a Samsung Ultra 16gb micro sd card. I was putting some files on my old pc and halfway through the transfer, it stopped. After reattempting it, the phone shut off and when it came back on, my Sd Card was damaged. I ran chkdsk on a friend's laptop and it fixed it temporarily but it became damaged again. So I formatted it and downloaded some backups from gcloud and halfway through the download, my phone shut off and my sdcard was damaged again. I downloaded Aparted to fix the errors and it didn't seem to work. Reformatting helps until the phone reboots. Then it's damaged again. I can't use my computer to run chkdsk because it doesn't have a port for sdcards and the only other computer I have is a chrome book. Anything else I can do?
I've enclosed a screenshot of Aparted attempting a recovery on the damaged sd card.
ne7usata.jpg
 
I've got a similar problem and am looking for a solution (that's why I'm reading this post actually) the conventional wisdom seems to be that fat32 is the most stable file system to format to. 1 suggestion that I read suggested changing the allocation size to 8kb.
I can tell u for a fact that fat32 last longer than exFat and the various ext formats. Still throws the error after a while though. I am going to try changing the allocation size the next time it errors so I can't tell you if that helps yet. And don't hesitate to let me any solutions u find.
 
I already bought a new one ( so I now have 2 unstable 64gb cards) . I'm trying the allocation fix as we speak so I'll let you know. I'll tell you that the SD card format software that I got didn't work. (just Google sd formatter... It's the first one) it only formats to exFat and that format goes defunct automatically (first time every time) lime I said fat32 works for a while but eventually errors too. I'll let you know how it goes.
1day later: found a workaround but no solution. Workaround is to format to ntfs on pic then mount with third party app (I found a couple in the store, there may be more) set the mount location in the app to the place where your ext_card usually is (or anywhere convenient to for you) then boom! One working storage location and set to ntfs too!
I will keep looking for a solution but this is the best I have so far.
 
You must log in or register to reply here.
Back
Top Bottom