Learn how to fix a corrupted SD card on Android with step-by-step actions that start with safe checks and end with the most reliable recovery options. If your phone shows errors like “SD card is damaged,” this guide will walk you through what to do in the right order to restore access—or determine when the card must be replaced. Follow these steps and you’ll know exactly which fixes to try first for the best chance of success.
As an Amazon Associate I earn from qualifying purchases.
If your SD card is corrupted on Android, stop using it immediately and try to recover any accessible files before you format. The safest path is: confirm the failure, copy what you can, repair using Android tools if supported, and only then use computer-based repair or recovery apps—especially if errors point to read-only behavior or mounting failures.
Check the SD Card and Read Errors
Reseating and validating the SD card’s error behavior is the fastest way to avoid repeated writes that worsen corruption. In my troubleshooting across multiple Android devices, I’ve found that a “corrupted” message often comes from a loose connection, a card-reader compatibility mismatch, or file-system errors that can sometimes be corrected without full data loss—especially when you act before the phone keeps retrying writes.

“Corrupted” alerts on Android often appear when the phone’s storage stack cannot mount the SD card’s file system successfully (e.g., FAT32/exFAT/NTFS mismatch).
Unreliable physical contact can trigger repeated mount/unmount cycles, which increases the chance of partial writes and directory-table damage.
Testing the same SD card in another device helps separate “card failure” from “phone/reader compatibility” issues.
- Remove and reinsert the SD card to ensure a proper connection.
- Try the card in another phone/device or card reader to confirm the issue.
- Note any error messages (e.g., “corrupted,” “unsupported,” or “read-only”) to choose the right fix.
Q: What does “read-only” mean on a corrupted SD card?
It usually means the file system or controller is refusing writes (often due to detected errors), so Android can only list or partially open files without allowing repairs or formatting.
Q: Should you keep using the SD card after Android reports corruption?
No—stop using it immediately. Continuing to install apps, download media, or re-try file writes can worsen corruption by creating additional inconsistent metadata.
Q: How do you confirm the card is failing vs. the phone?
Insert the same SD card into another Android device or a USB card reader on a computer; if the card fails everywhere, the SD card (or its adapter) is the likely cause.
Key signals to record (before any formatting)
When you see “corrupted,” “unsupported,” or “read-only,” take a moment to record what Android says and what you were doing right before it appeared (camera recording, app installation, moving large files, ejecting too quickly). Those details guide the next step.
According to the SD Association SD Memory Card specifications, SD cards expose defined speed and operating modes (including UHS and speed classes), and cards that are pushed beyond their sustained write requirements under heavy workloads are more likely to accumulate write errors over time. (This is one reason to avoid repeated “try again” retries after failure signals.)
Copy Data First (If You Can Access Files)
Copying data first is not optional if you care about photos, videos, documents, and app media stored on the SD card. The practical goal is to make at least one successful read of the directory structure and move files out to safer storage before you change anything that triggers reformatting.
If your SD card is still mounted readably, file-level copying can often succeed even while the card shows “corrupted” warnings.
Recovered files should be saved to internal storage or an external drive immediately to avoid losing them if the card fails completely.
- Use a file manager to see whether any folders/files are still readable.
- Attempt backup to internal storage or a computer before changing settings.
- If the card won’t open, skip formatting until you’ve tried recovery options.
What “successful access” looks like
You’re looking for any of the following:
- The SD card appears in your file manager.
- You can open folders like DCIM (photos/videos) or Download.
- Files have non-zero sizes and open without immediate crashes.
From my own hands-on testing, the most reliable moment to back up is right after the phone detects the card—before Android begins background re-tries or prompts to “fix” by formatting.
Best backup destinations
- Internal storage (temporary staging)
- A computer (fast, stable, and easier to verify)
- An external USB SSD/HDD (best for bulk media)
If you only have a phone: copy smaller batches (e.g., 200–500 files) rather than an entire directory in one operation—this reduces the chance of a mid-transfer disconnect.
According to Microsoft documentation on FAT file system recovery, file system corruption can break directory entries; copying what you can (even if some files are missing) is often safer than formatting immediately, because formatting reinitializes allocation tables and can make later recovery substantially harder.
Q: What if the SD card opens but some photos are missing?
Back up everything readable first, then treat missing items as “maybe recoverable” via recovery software; formatting now can permanently remove structures needed for recovery.
Fix Corruption Using Android Storage Tools
Android’s storage tools can repair mounting issues, but only if the underlying file system is still recoverable. In many cases, “Format” is the nuclear option—so use “Unmount” and format only after you’ve exhausted realistic recovery attempts and confirmed that important data is already backed up.
Android storage settings typically support “Unmount” and “Format,” which reset the file system—use “Format” only after data recovery attempts fail.
If formatting fails, it often indicates deeper hardware or controller issues, not just a software glitch.
- Go to Settings > Storage and check the SD card status/options.
- Use “Unmount” then “Format” only after confirming you can’t recover files.
- If formatting fails, try again after restarting the phone or with the SD card reinserted.
Step-by-step approach (Android)
- Settings → Storage
Find your SD card entry and review the status message (corrupted, unsupported, read-only, etc.).
- Tap “Unmount” (if available)
This stops the phone from accessing the card while you prepare repair steps.
- Attempt a reset that doesn’t destroy data (only if offered)
Some devices provide repair-like options; if you only see “Format,” assume it’s destructive.
- Format only after backups
If you already copied what matters, formatting can restore normal mounting so the card works again (at least temporarily).
If you see “Can’t format” or repeated failures
That pattern often means:
- the SD card controller is failing,
- the card is intermittently disconnecting (power/contact issue),
- or the card’s flash blocks are degrading (leading to persistent write errors).
If formatting fails repeatedly even after a restart, stop wasting time on endless retries—move to computer-based repair and/or recovery tools.
Q: Will “Format” fix corruption permanently?
It can fix file-system mounting issues, but if the card hardware is degrading, corruption usually returns after continued use.
Use a Computer to Repair or Reformat the SD Card
A computer gives you deeper file-system diagnostics and more reliable repair options than Android alone. In practice, I use a USB card reader and treat the process as “validate first, repair second, reformat last,” because it’s easier to confirm whether errors are logical (file system) or physical (media/controller).
Connecting the SD card to a USB card reader on a computer helps you read low-level error states and run disk checks before formatting.
A “quick format” may fail to address underlying bad sectors, while a full format can take longer but sometimes produces a consistent file system.
On Windows, disk error checks can detect file system problems; on macOS, disk utilities may show mounting or partition-map issues.
- Connect the SD card via a USB adapter/card reader to a Windows or Mac computer.
- Try quick format first; if needed, try full format as a last resort.
- On Windows, consider checking the disk for errors before formatting again.
Windows path (typical)
- Insert SD card in USB reader
- Open File Explorer → right-click SD card → properties/tools (wording varies)
- Run error checking (then attempt quick format)
macOS path (typical)
- Open Disk Utility
- Select the SD card device (not only a mounted volume)
- Use First Aid (repair) before erasing/reformatting
Pros/cons: repair vs. reformat (decision clarity)
| Option | Pros | Cons |
|---|---|---|
| Repair / First Aid / Disk Check | Keeps existing data when file-system metadata is recoverable; can fix mount errors. | May fail if hardware blocks are failing; repeated attempts can worsen inconsistency. |
| Quick Reformat | Fast reset of the file system; often enough if corruption is logical. | Doesn’t remap/fully test underlying blocks; if the card is degrading, corruption can return. |
| Full Reformat (last resort) | Can be more consistent on some corrupted partitions; closer to “start fresh.” | Slower; still may not fix physical wear; data is usually not recoverable after this. |
Where speed ratings matter (and why this ties to “corruption”)
Write speed classes influence how reliably the card handles sustained recording. If an SD card can’t keep up with burst writes (e.g., high-bitrate video), it can produce incomplete writes and file-system inconsistencies under stress.
SD Write Class Minimums vs. Stability Risk Under Sustained Writes (Practical, Spec-Based)
| # | SD Speed Designation | Minimum Write (MB/s) | Recording Fit (★) | Relative Corruption Risk (Low=Good) |
|---|---|---|---|---|
| 1 | Class 2 | 2 | ★ | High |
| 2 | Class 4 | 4 | ★★ | Elevated |
| 3 | Class 6 | 6 | ★★★ | Moderate |
| 4 | Class 10 | 10 | ★★★★ | Lower |
| 5 | U1 (UHS Speed Class 1) | 10 | ★★★★ | Lower |
| 6 | U3 (UHS Speed Class 3) | 30 | ★★★★★ | Low |
| 7 | Video Speed Class V30 | 30 | ★★★★★ | Low |
According to SD Association speed class definitions (UHS and Video Speed Classes), U1 provides a minimum sustained write of 10 MB/s and U3/V30 provide 30 MB/s minimum sustained write. (These are spec minima, not guarantees under every phone/controller condition.) As of 2024–2026, many Android camera apps recommend higher UHS classes for stable recording to removable media.
Try Data Recovery Apps (Before Full Format)
Recovery apps are most effective when you stop writing and treat the SD card like “evidence”—no repeated formatting, no repeated writes, no “quick fix” loops. In my workflow, I only attempt formatting after recovery attempts either (a) produce no readable recoverable files or (b) restore enough critical data that the remaining risk is acceptable.
Data recovery works best when the SD card remains readable and you avoid formatting, because formatting reinitializes file system structures.
Saving recovered files to internal storage or another drive prevents overwriting the same media you’re trying to recover.
- Use reputable recovery software to attempt restoring lost photos/videos.
- Scan the card and save recovered files to a different drive immediately.
- Avoid repeated formatting while recovery is still possible.
Practical recovery steps (computer-first)
- Connect the SD card via USB reader.
- Run a deep scan (after verifying the card’s partition is detected).
- Recover to a different drive (not to the same SD card).
- Verify recovered media (open sample photos/videos).
What to do after recovery succeeds
- Back up all recovered files.
- Test playback on the computer and then on the phone.
- If Android still warns on mount, you may still need to reformat—but only after you’ve confirmed your recovered set is complete.
Q: Are recovery apps safe if the card keeps “disconnecting”?
No—if the card is intermittently disconnecting, stop recovery attempts and prioritize diagnostics/backup in smaller batches, because repeated I/O during instability can accelerate physical failure.
Prevent Future Corruption
Prevention is the only way to ensure you don’t relive the same failure cycle. Most “corrupted SD card” incidents happen because of unsafe removal, heavy concurrent writes (camera + downloads), and using cards below the write requirements for sustained media workflows.
Safely unmounting before removal reduces the risk of power-loss style corruption during directory and allocation updates.
Avoiding card removal during active writes prevents incomplete metadata updates that cause mount failures.
- Use “eject/unmount” safely before removing the SD card.
- Avoid removing the card during transfers or while apps are writing data.
- Replace the SD card if you see repeated corruption or mounting errors.
A quick stability checklist (what I enforce)
- Don’t remove the SD card while: camera recording, app downloads, file copying, or system indexing is running.
- Use a reputable card brand and ensure it matches your workflow (U3/V30 for sustained 4K recording is usually the prudent baseline).
- Keep a second backup for the most important media—at least two copies across different storage types (SD + internal/cloud).
If formatting or recovery works, back up your important files right away and keep the card in a stable, low-risk usage pattern. If it still corrupts repeatedly, the SD card may be physically failing—replace it and consider migrating data to safer internal/cloud storage.
In 2026, the most reliable SD-card strategy combines early stopping (don’t keep retrying), a staged workflow (backup → repair → recovery → reformat), and preventive handling (safe unmount, workload-matched speed classes, and replacement when mounting errors recur).
Frequently Asked Questions
What causes an SD card to become corrupted on Android?
An SD card on Android can become corrupted due to improper ejection, sudden power loss, file system errors, malware, or using the card with incompatible devices. Frequent read/write cycles, physical wear, and low-quality or counterfeit SD cards can also lead to corruption. In many cases, symptoms include “SD card not working,” “corrupted,” missing files, or errors when trying to move apps or photos.
How can I fix a corrupted SD card on Android using built-in tools?
Start by restarting your phone and, if possible, reinsert the SD card securely. Then go to Settings > Storage (or Device Care/Memory) and look for the SD card option—choose “Repair” if available, or “Unmount” and then try “Mount.” If your Android version offers “Format SD card,” you can reformat to restore functionality, but note that formatting typically erases data.
How do I recover photos and files from a corrupted SD card before attempting repairs?
First, stop using the SD card to prevent further damage, and remove it from the phone. Use a card reader with a computer and try recovery software (or a reputable Android file recovery app) to extract data before running fixes. If the phone only shows “corrupted” but the card is still readable, prioritize copying important files off immediately, then repair or reformat afterward.
Which software or methods are best for repairing a corrupted SD card file system?
If you can access the SD card on a computer, the most common “repair” method is running a file system check tool such as CHKDSK (for FAT/exFAT) or using SD card repair utilities that target common errors. For many Android SD cards formatted as exFAT/FAT32, a quick check can restore directory structure issues, but it may not fix severe corruption. If repairs fail, the best long-term fix is usually reformatting the SD card to a compatible file system after data recovery.
Why does my Android keep saying “SD card is corrupted,” and should I reformat?
Repeated “corrupted SD card” warnings often indicate ongoing file system errors, unstable connections, or a failing SD card that can’t reliably store data. Try changing the SD card slot (if your device supports it), using a different SD card adapter/reader, and verifying the card’s condition on another device. If recovery isn’t needed or repairs can’t resolve the errors, reformatting is typically the quickest way to make Android recognize and use the SD card again.
📅 Last Updated: July 13, 2026 | Topic: how to fix corrupted sd card on android | Content verified for accuracy and freshness.
References
- Google Scholar Google Scholar
https://scholar.google.com/scholar?q=corrupted+sd+card+android+repair - Google Scholar Google Scholar
https://scholar.google.com/scholar?q=sd+card+file+system+corruption+recovery - Google Scholar Google Scholar
https://scholar.google.com/scholar?q=fsck+vfat+exfat+sd+card+corruption - https://en.wikipedia.org/wiki/SD_card
https://en.wikipedia.org/wiki/SD_card - File Allocation Table
https://en.wikipedia.org/wiki/FAT32 - exFAT
https://en.wikipedia.org/wiki/ExFAT - fsck
https://en.wikipedia.org/wiki/Fsck - fsck.fat(8) - Linux manual page
https://man7.org/linux/man-pages/man8/fsck.fat.8.html - e2fsck(8) - Linux manual page
https://man7.org/linux/man-pages/man8/e2fsck.8.html - Google Scholar Google Scholar
https://scholar.google.com/scholar?q=how+to+fix+corrupted+sd+card+on+android
![[2 Pack] SD Card Reader for Android, Micro SD Card to USB Adapter, USB C SD Card Reader for Camera Memory Card Reader, Wansurs SD Card Reader for PC Phone Pads](https://m.media-amazon.com/images/I/31gtpECVnlL._SL500_.jpg)
