.......right in the middle of a super demanding day, the message "damaged SD Card / Reformat" appeared on my Epic, when I least expected it (inopportune is the word)............ changing firmware is never without its more interesting moments, + this may or may not be a symptom (went froyo to gingerbread), however,........... am sharing this post to the Epic community, as i sense this to be an important enough issue...........no one really knows the specific cause of sd card corruption + failure: it's variable + always somewhat circumstantial (ie, saw it mentioned elsewhere that overheating from an overclocked cpu could cause damage as well)...................so, moving forward I simply want to contribute as a brief description, here, how i was able to recover (most) of the files from my 'damaged micro sd card:'
First, when i saw 'damaged sd card / format card' on the phone, when it became possible 4 me to do so many hours later, instead of 'formatting' I replaced the damaged card for a new one (pny 16gb sdhc class 10)...booted the phone everything was fine (15.91gb space available)........as expected, no files in the SD Card......................next:
(1) placed 'damaged' sd card into the reader that came w/ the device, and mounted to pc, selected the drive (followed by confirmation beep 'device detected' sound, then the language: 'd:\ not accessible. The file or directory is corrupted and unreadable' came on the screen..........went to RUN and typed CMD........from new window, I typed Chkdsk d: /r and the PC began reading the contents of the damaged SD card (most of the android zip files etcetera were there, as were a number of files w/ no content) + next i typed 'exit' (no quotations, just the letters) to return to the windows desktop.......OK, so now the only files missing are the pix + video mov's (far as I can remember).
..........(2) next, to recover pix + video, from the pc desktop i opened ZARecovery (if you do not already have it go to Data Recovery Software, Solutions, Tutorials, Forum - ZAR Data Recovery and download the free recovery program from that site).
.............(3) from the ZARrecovery main page, selected sd card as device, selected 'next', selected 'root' folder for all files that ZAR was able to detect as recoverable, entered destination folder name (for transfer of recovered pix + video to PC....note: NEVER to sd card itself!), + lastly, selected 'start copying selected files'.........and that was it, closed ZAR + began viewing the content of the recovery folder to get an assessment of what had actually been recovered, and what had been lost.................fortunately 4 me, the loss was minimal, as I tend to create backups (Nandroids, every half year; pic, videos, email attachments = pretty regularly).
Hope this helps those of you that have been experiencing microSD Card damage (from whatever source).
Remember, + not to speak to the Choir, but can not to overstate this: BACKUP............. BACKUP............. BACKUP.............BACKUP
MODS STICKY THIS!!!!
Sent from my SPH-D700 using xda premium
I see you took my advice, nice.
PLEASE STICKY!
Sent from my SPH-D700 using XDA App
Thank you to the Mod that stickied this. Sonarchist...you have arrived!
sonarchist said:
.......fortunately 4 me, the loss was minimal, as I tend to create backups (Nandroids, every half year; pic, videos, email attachments = pretty regularly).
Hope this helps those of you that have been experiencing microSD Card damage (from whatever source).
Remember, + not to speak to the Choir, but can not to overstate this: BACKUP............. BACKUP............. BACKUP.............BACKUP
Click to expand...
Click to collapse
Yikes! I make nandroids before I do anything I consider major like updating Superuser when the reviews are sketchy, or when I do something like apply a new patch, a new tweak, or anything that I think could give me trouble. As I have my phone tuned absolutely perfect, where I want to bring my phone back to normal with a minimum of work.
I guess I am lazy. I nandroid every 3 to 7 days.
mouseglider said:
I nandroid every 3 to 7 days.
Click to expand...
Click to collapse
.....you're awesome!.......my personal history, when I find stability, is to live w/ a perfect set-up for as long as i can surf that wave (hence: nandroid every 6 mo's)........but this is being idealistic.........for example, when testing a beta ROM, an average of at least 6-9 nandroids in the sd card thru several versions of the beta, and at least 3 in the Nandroid Folder in the pc (which is altogether another story: visualizing + creating a pc backup that is operative in a worse-case scenario.)
sonarchist said:
.....you're awesome!.......my personal history, when I find stability, is to live w/ a perfect set-up for as long as i can surf that wave (hence: nandroid every 6 mo's)........but this is being idealistic.........for example, when testing a beta ROM, an average of at least 6-9 nandroids in the sd card thru several versions of the beta, and at least 3 in the Nandroid Folder in the pc (which is altogether another story: visualizing + creating a pc backup that is operative in a worse-case scenario.)
Click to expand...
Click to collapse
I should add that one of the reason I nandroid so often, is that if I do it every 3 to 4 months (on my wife's epic because she travels) when she gets back, I have a ton of updates to catch up on - mine of course is always up to date.
mouseglider said:
I should add that one of the reason I nandroid so often, is that if I do it every 3 to 4 months (on my wife's epic because she travels) when she gets back, I have a ton of updates to catch up on - mine of course is always up to date.
Click to expand...
Click to collapse
Haha! Same with me and my GFs...she never updates! So if your sd card crashes you will seriously need this tutorial since all your nandroids are there.
Awesome info. Thanks for sharing!
kennyglass123 said:
Haha! Same with me and my GFs...she never updates! So if your sd card crashes you will seriously need this tutorial since all your nandroids are there.
Click to expand...
Click to collapse
I am so paranoid about sd crashes and corruption because I have had my share when upgrading to the next bigger card (had a 2,4,8,16, and now 32gb in each epic) that I sync my epic cards to my PC on two separate drives for both my wife and myself (my PC has three physical (not virtual)l hard drives C, D, E) every 3 to 4 weeks. So for her, I am pretty safe except for those long updates in between her trips home. I feel pretty safe in case I do something stupid, which I do from time to time.
I actually tried to convince her to get an iPhone, because I think there would be less updates than Android, but she won't give up the physical KB. Not that I don't like updates, but I set her epic to be a 98% clone of mine, so we each have a lot of apps and each app is eventually updated and often!
mouseglider said:
I should add that one of the reason I nandroid so often, is that if I do it every 3 to 4 months (on my wife's epic because she travels) when she gets back, I have a ton of updates to catch up on - mine of course is always up to date.
Click to expand...
Click to collapse
NITDH.......you don't want that!........(nandroid-in-the-dog-house)....lol
.........arrival of the backup evangelists!
kennyglass123 said:
Thank you to the Mod that stickied this. Sonarchist...you have arrived!
Click to expand...
Click to collapse
........a hi-5 to the Mods for Sticky'ing this: thanks guys!....... props to kennyglass123 + xopher.hunter for suggesting it to 'em.............nothing more stressful than going down that gopher hole attempting to recover data, it's no picnic!...........so am hopeful that we can salvage some valuable data + find ways to hinder that inevitable moment when the sd card reads 0%.............as they say, there's many more ways than 1 to skin a grape, or in this case, a corrupt microSD Card.
There is an undelete beta app on the market. Check it out.
Also, check out testdisk for when the partition table is fried.
Also, recuva. Pretty awesome, by the makers of ccleaner.
sent from my always aosp epic
mouseglider said:
I am so paranoid about sd crashes and corruption because I have had my share when upgrading to the next bigger card (had a 2,4,8,16, and now 32gb in each epic) that I sync my epic cards to my PC on two separate drives for both my wife and myself (my PC has three physical (not virtual)l hard drives C, D, E) every 3 to 4 weeks. So for her, I am pretty safe except for those long updates in between her trips home. I feel pretty safe in case I do something stupid, which I do from time to time.
I actually tried to convince her to get an iPhone, because I think there would be less updates than Android, but she won't give up the physical KB. Not that I don't like updates, but I set her epic to be a 98% clone of mine, so we each have a lot of apps and each app is eventually updated and often!
Click to expand...
Click to collapse
Gr8 backup regimen..........'best practices' worthy.........given the 1,000 cumulative hrs leading to your perfect setup, worth all the special handling to keep devices singing!
props on the recovery
Mine took a dump today but it may be a total failure. I just got home and this is what the preliminary tests show. I would appreciate any input.
chkdsk
The type of the file system is RAW.
CHKDSK is not available for RAW drives.
testdisk
Capacity incorrectly showed at 8225kb/8032kb (16gb card)
Analyze feature reports a Partition Rear Error
As a sidenote, the TitaniumBackup sync-to-Dropbox feature has probably saved my butt as far as apps/data goes. I highly suggest using it to protect against dead cards.
Sadly SD cards and USB sticks are very unreliable when it comes to data. They are easily damage and anything slight can cause them to be corrupted.
This is a great guide, glad you were able to restore your data!
Most data in flash type memory cards (excepting physical cracks in the microSD Card housing + damage to the memory chip itself) can be recovered w/ several DIY software programs available on the android market..........ugothkd shared a few of these, several posts up.........in the event that there is NO BACKUP available to you + having exhausted all personal DIY recovery avenues, there are still ways to step-up the process and very likely recover some of your data..........am quoting the following language from Recoverfab (maker of enterprise flash readers to the trade):
'In general, there are two reasons why the data on memory flash devices (cards, USB-sticks, SSD) becomes inaccessible.
Logical damage prevents access to the data/pictures on the drive, but the drive is still physically recognized by the computer operating system. In this case some specialized types of recovery software can help. Sometimes free recovery tools like Zero Assumption Recovery can also solve this problem.
Physical damage causes the drive to be unrecognized by the computer's operating system, making it impossible to access the contents of the flash-memory chip. This type of damage happens in more than 80% of all known cases. These are most frequently caused by electrical problems that lead to physical damage. Flash devices consist of a memory chip and a controller. The controller writes and reads the data from the memory chip. In most cases, recovery is possible from a flash device with a damaged controller and mostly undamaged memory chips.
Formatting is required? The controller of the memory card is not in the position to inform the PC operating system about the characteristics of the memory card. Therefore, the PC assumes that the memory card is not formatted and requests formatting. One might think that the memory card problems would be solved by formatting, but unfortunately it does not work due to the damaged controller. Instead, the computer will communicate that formatting is not possible. Such an error is a clear indicator that no kind of software (including special formatting or rescue software!!) will be able to access the memory card.
.....Recovery Process: If the flash storage device is not recognized in the computer or it is impossible to access the data on it, there is only one way to get the data: unsolder the memory chip from the printed circuit board and directly access the raw data with a programmable chip reader.' <end quote>
OK......that was a long quote!.....worth repeating, if only to begin to address the sort of things that can damage / corrupt SD Cards (+ also to give those of you that really want to recover your lost data super badly some HOPE).
Heat, liquid, dust, some of the things that WILL damage your SD Card (numerous other things can corrupt your data as well) .....then you hear cases of individuals that have NEVER HAD ANY DAMAGE WHATSOEVER...........some burnin' Q's: is the fragile nature of the card itself doomed to failure? ...If the card is going to fail eventually, what kind of data would you be willing to risk storing in there?...... if the data is that important to you, would you be willing to make a 'twin' copy? (twin SD Card could be swapped quickly in case of ER) ..... + lastly, has anyone here found a fail-safe or fairly sound way to run voluminous or frequent data transfers between your device's SD Card + pc?
sonarchist said:
Most data in flash type memory cards............. if the data is that important to you, would you be willing to make a 'twin' copy? (twin SD Card could be swapped quickly in case of ER) ..... + lastly, has anyone here found a fail-safe or fairly sound way to run voluminous or frequent data transfers between your device's SD Card + pc?
Click to expand...
Click to collapse
Yup, I have a spare twin identical card Lexar 32gb class 10 waiting in the wings as a backup.
I use a program that can transfer and/or sync in many different ways my card to my PC, which I do every three or four weeks. It is called FolderMatch v3.44. I am sure there is a newer version out, but the one I have does the job
I simply plug my USB cable into my PC and the other end into my epic and simply choose synchronize, then chose make left folder (my PC) to be the same as the right folder (my epic) - depending on how many files you are syncing determines the speed of the sync. Works good for me!
quick99si said:
Mine took a dump today but it may be a total failure. I just got home and this is what the preliminary tests show. I would appreciate any input.
chkdsk
The type of the file system is RAW.
CHKDSK is not available for RAW drives.
testdisk
Capacity incorrectly showed at 8225kb/8032kb (16gb card)
Analyze feature reports a Partition Rear Error
As a sidenote, the TitaniumBackup sync-to-Dropbox feature has probably saved my butt as far as apps/data goes. I highly suggest using it to protect against dead cards.
Click to expand...
Click to collapse
ZAR has an 'unformat' option for Raw File Systems, you may want to explore if there is data remaining in your SD Card that you may want to recover (there's a brief tutorial posted on their website) ........ here's a glimpse:
"Unformat is the process of data recovery from a storage device (which can be a hard drive, a camera memory card, an USB pen drive) that was formatted.
The step-by-step tutorial below describes the procedure to recover data when the drive was accidentally formatted and you want to unformat the drive Windows reports "raw filesystem", or the drive is "not formatted" <end quote>
The above makes reference to a specific type of recovery (accidental format of a drive, as an example), but the application will recover from a number of file types + systems............worth checking it out.
*edit* as another example, 'accidental format of a drive' can also refer to split-second decisions we make when we guickly hit 'reformat sd card' on our device the very first time we ever encounter a 'corrupted external card / reformat?' type of message........in the moment, life goes on + it's only later that we begin to think of the lost data..................however, chances are pretty good that the data is recoverable (files are still inside the 'reformatted' sd card, only unreadable, ie RAW).
I recently purchased a new Sony Vaio notebook that came with windows 8 preinstalled. It cam with a 1 tb HDD that was replaced with a 180 gb SSD and windows was reloaded using a recovery usb. I then wanted to mount the 1 tb HDD into dvd drive spot so I bought a caddy for it off of amazon. It was really easy to pull out the dvd drive and pop in the HDD in it's caddy and it fit perfectly. I turned on the notebook and it booted up and the drive was now recognized at D drive. I could see the windows os was still on there so I did the quick format option and then proceeded to transfer my music folder over from my external. I noticed through the whole process that the fan seemed to be running really high and I thought it was just because I was messing the new HDD but it never went away even when I was done with the transfer. The HDD seemed to always be spinning too even when I wasn't accessing files on it which didn't seem right if it's not being used. The fan is usually running but this was a full blast like I was playing a high end game. Windows gave me a blue error message about a kernel and rebooted. The fan immediately kicked in once it restarted so I turned it off and put the dvd drive back.
So my question is just if anybody has any experience doing something like this and has some suggestions? I want to try it again and figured it wouldn't hurt so ask for advice on here before I do. I figured I would try doing a different type of format as maybe there are still os traces on there that's messing things up. Thanks for reading.
ROORnNUGZ said:
I recently purchased a new Sony Vaio notebook that came with windows 8 preinstalled. It cam with a 1 tb HDD that was replaced with a 180 gb SSD and windows was reloaded using a recovery usb. I then wanted to mount the 1 tb HDD into dvd drive spot so I bought a caddy for it off of amazon. It was really easy to pull out the dvd drive and pop in the HDD in it's caddy and it fit perfectly. I turned on the notebook and it booted up and the drive was now recognized at D drive. I could see the windows os was still on there so I did the quick format option and then proceeded to transfer my music folder over from my external. I noticed through the whole process that the fan seemed to be running really high and I thought it was just because I was messing the new HDD but it never went away even when I was done with the transfer. The HDD seemed to always be spinning too even when I wasn't accessing files on it which didn't seem right if it's not being used. The fan is usually running but this was a full blast like I was playing a high end game. Windows gave me a blue error message about a kernel and rebooted. The fan immediately kicked in once it restarted so I turned it off and put the dvd drive back.
So my question is just if anybody has any experience doing something like this and has some suggestions? I want to try it again and figured it wouldn't hurt so ask for advice on here before I do. I figured I would try doing a different type of format as maybe there are still os traces on there that's messing things up. Thanks for reading.
Click to expand...
Click to collapse
Perhaps the new caddy is blocking airflow? Also, the drive may be pulling more power than the DVD drive would and causing something to get overloaded.
I did this with a Lenovo Ideapad y550p and I never noticed any issues like this.
I'd try checking if your manufacturer has a public support forum you can post on, this seems like it may be a device specific issue.
HDDs generate a lot of heat (for more than most SSDs, incidentally) and your laptop's cooling may not have been designed for this source of heat.
You also bought a Sony device, which makes it difficult for me to even speculate what other problems might be occurring.
Thanks for the replies. I tried looking around the sony website but can't find much. I'll give it another go and check for some airflow and if that doesn't work then I'll just live with the ssd because I'm not giving that speed up.
You could try swapping the SSD and HDD. The SSD should generate less heat, which may help out.
So I reinstalled and did a full format which took over two hours but I noticed there were still hidden partitions on this drive so I got rid of those and expanded the drive all the way. Then I unchecked the box to allow random indexing on this drive and changed the power options shut off disk to 1 min per someone's instructions from a google link and it seems to working now. Figured I would post in case someone else ever runs into this issue.
I was just this moment ago proceeding to move all the photos that had been saved to the MicroSD inside my GT-i9505 to the PC via USB connection. I was using the default MTP/PTP(?) explorer interface to find my photos.
I must've had something like 3GB worth of photos and videos on the card (I went a bit crazy with the camera in recent weeks!) and thought there would be nothing wrong with moving them off the card and onto my PC's hard disk. The whole moving process took quite a while so I thought I'd leave it to do its thing and then come back once it had finished.
But when I did, I noticed something bizarre - the folder was reported to come in at 2.55 TB (yes, *terabytes*!). I thought it was a silly Windows Explorer bug, but I reopened the window and checked Properties, and yup, still 2.55 TB. The drive partition I moved them to was compressed so I didn't actually need that much space, but it was still worrying. I checked some of the files and realised a fair amount of them were reported to be 3.42 GB each! The compressed size (size on disk) Windows 7 reported on the other hand was only 4 KB. Uh-oh. I tried to open them but Windows' own picture viewer had errors with them. I checked one file through a hex editor and noticed the majority of the file was just blank data followed by a smidgen of data at the very end, with no sign of headers.
So somehow, by doing something as innocent as moving photos and videos off of an S4-mounted MicroSD card, they got corrupted beyond repair in the process! What the hell?!
I'm gutted. Out of a total of 1,029 files and roughly 3GB, I managed to recover only 265 JPGs and 793 MB. Why did this happen? Is this a known issue with the phone or with MicroSD cards? I'm wondering whether it's anything to do with the MicroSD card I used - a non-brand specific 16GB one bought from my local Maplin and in a Maplin cardboard packet (online link at maplin.co.uk/micro-secure-digital-sdhc-memory-card-228011). The odd thing is that the phone and the OS reported no problems with the card, and the photos and videos saved to the card were fine and perfectly viewable on the phone just before I moved them off. As it is, I've now got 2 1/2 TBs worth of (presumably) permanently-damaged media files. Is there anything else I can do?
What I'm using, as follows:
Samsung Galaxy S4 GT-i9505
16GB Maplin-brand MicroSD card
Windows 7 32-bit
If you need any other specs, let me know.
No handy words of advice for next time, then?
This is what i do if i want to move ANY type of file from phone to other storage. I COPY, NOT MOVE files first to the destination that i want to and if they are successful then i will delete the other files from the phone. That way, if they do corrupt on destination, at least you still have originals because you copied only.
Hope this helps.
Yeah, sounds like something I'll have to remember for next time.
I wish I knew exactly what the cause was. It could've been anything - the drive partition and/or its compressed state, the MicroSD card, the rather crappy MTP interface forced upon by Google, the large volume of the media I was copying (like I said, it was over 1,000 files).
I have a small feeling it might be the last one somehow, as the photos stored directly on the phone (of which there weren't that many before I switched to MicroSD) moved across to PC in perfect condition, as did the screenshots I also captured. Furthermore, I decided to do a quick test with the MicroSD by picking a random spot and repeatedly pressing the camera button/icon to take as many photos as possible in a short period of time. I managed to make over 100 before I got bored, but when I moved them off the card in the same manner as before (phone mounted to USB, MTP interface) they came out unscathed and not in any ballooned size.
Has anyone else ever come across any issues with moving large amounts of files at once between PC and phone-mounted MicroSD? The only other time I did a very large mass transfer was with some various ROMs for emulator use to my Nexus 7 tablet's onboard storage, and as far as I know they all came out fine.
It's frustrating when it seems like a problem such as this one is totally alien and googling can't help with jack.
Guys.
I have a nexus 7 that i'm utilising in a car build.
It's running CM10.1 which I believe is based on 4.2.2, and Timurs custom Kernel.
I have a 175gb SSD dive, hooked up to a USB hub and OTG cable.
The SSD is recognised and mounts correctly on the Nexus.
I'm looking to speed up the mount process.
When I connect the SSD, the led activity light on the SSD will start to blink rapidly, any media on the drive is inaccessible until the drive activity has ceased.
This process takes around 30 seconds.
I've placed a number of .nomedia files inside the USBDISK folder amd SDCARD folder, but still mounting takes time.
Is there a way to speed up the mounting process.
Maybe moving the media folders inside a single folder, or some sort of file (like .nomedia) inside the folder structure to tell Android to not perform a file check.
Maybe a cache system.
The kernel is configured to have the drive in read only mode, so unless I manually add any files, then I have no need to scan for any file changes.
The drive could be in the car for months before I add any new media to it.
I guess no one else has experienced this, or I posted in the wrong forum, but i think i figured it out.
Just incase someone else has the same problem in the future, and in the vain hope that they stumble across this thread, I think it's only fair that I post my findings.
My SSD drive is formatted exFat for compatibilty between my PC, Tablet and S7 phone which is on Marshmallow.
I have 2 hard drives, I have a 2.5" SSD and a standard 2.5" Sata drive.
So something to experiment with.
Formatting the standard hard drive as NTFS and then copying a small number of my files on to it, i noticed that the mount time was instant, with hardly any drive activity.
All files are accessable.
It makes little sense, considering a standard mechanical drive is supposedly slower than SSD.
I then formatted it exFat, and copied roughly the same number of files, but now the mount time was about 5 seconds, with the drive light activity issue.
My SSD drive is taking 30-40 seconds to mount, which is annoying to say the least.
I reformatted my SSD as NTFS, copied my files back on to it, and the mount time is still almost instantaneous.
So it looks like whatever is causing the extended mount time is asscociated with exFat.
I've no idea why, so if anyone can explain, i'll be happy to learn.