Fix Corrupted Files and Incomplete Downloads on Android

A corrupted file is one that has been damaged or incompletely written — it either won't open at all, opens with errors, or shows partial/garbled content. The most common causes are interrupted downloads, unstable network transfers, failing storage media, and insufficient disk space during writes. The fix depends on the type of corruption: incomplete downloads should be re-downloaded with a stable connection, damaged archives can sometimes be repaired, and files from failing SD cards should be recovered immediately before the card dies completely.

Identifying File Corruption

Signs a File Is Corrupted

Quick Checks

1. File size check: In AnExplorer, look at the file's size. Compare with the expected size:
   • A 0-byte file = nothing was downloaded
   • A file significantly smaller than expected = incomplete transfer
   • A file matching expected size = may still be corrupted internally, but transfer was complete
2. Checksum verification: If the download source provides MD5 or SHA256 checksums:
   • Note the provided checksum from the website/source
   • In AnExplorer, check file properties which may show the file's hash
   • Compare the two — if they match, the file is intact
   • If they differ, the file is corrupted and needs to be re-downloaded

Causes of File Corruption

During Download

• WiFi disconnection: Connection drops mid-download, leaving an incomplete file
• Mobile data switch: Moving from WiFi to mobile data (or vice versa) can interrupt downloads
• Server timeout: The source server closed the connection before the download finished
• Battery optimization: Android killed the download app to save battery
• Storage full: Device ran out of space during the download — file is truncated
• Browser crash: The browser or download manager crashed before completing the write

During Transfer (Copy/Move)

• USB disconnection: Cable pulled or loose connection during MTP transfer
• Network interruption: WiFi drop during SMB/FTP transfer
• Source device removed: SD card ejected, USB drive unplugged during copy
• App crash: File manager crashed during a copy/move operation
• Power loss: Phone died during a file operation

Storage Media Failure

• SD card bad sectors: Failing SD cards produce corrupted reads/writes
• SD card wear: Cards with exceeded write cycles produce data errors
• Internal storage failure: Rare but possible — eMMC/UFS errors on older devices
• Filesystem corruption: Improper ejection of storage, or crash during write, can corrupt the filesystem structure

Fixing Corrupted Files

Solution 1: Re-download from Source (Best Option)

For files downloaded from the internet:

1. Delete the corrupted file
2. Ensure stable WiFi connection (5 GHz preferred, stay close to router)
3. Ensure sufficient free storage (at least 2x the file size available)
4. Re-download from the original source
5. Verify the new download's size matches the expected size
6. If checksum is available, verify it

Solution 2: Resume Incomplete Downloads

Some servers support download resumption:

1. If the download was interrupted, check if your browser/download manager shows a "Resume" option
2. If resumable, continue the download from where it stopped
3. If not resumable (server doesn't support range requests), delete and start fresh
4. AnExplorer's FTP/SFTP client may support resuming interrupted transfers

Solution 3: Repair Corrupted Archives

ZIP and RAR files can sometimes be repaired:

RAR with recovery record: If the RAR was created with a recovery record:

• A recovery-enabled archive can fix small amounts of corruption
• Use a RAR-compatible tool to attempt repair
• Success depends on the extent of corruption vs. the recovery record size

ZIP files: Standard ZIP files have no built-in repair mechanism, but:

• If only part of the archive is corrupted, some tools can extract the uncorrupted files
• The corrupted portion is lost, but you may recover most of the archive's contents
• Try extracting with AnExplorer — it may skip corrupted files and extract what it can

Solution 4: Partially Recover Video Files

Corrupted video files (incomplete downloads or transfers) may be partially watchable:

1. Try opening the video in VLC for Android — it handles corruption better than most players
2. The video may play up to the corruption point (e.g., first 80% plays fine)
3. Seeking past the corruption point may work or may crash the player
4. If the header is corrupted (first few KB), the file may not play at all — header repair tools exist for MP4/MKV

Solution 5: Recover Photos

Partially corrupted photos:

• JPEGs may show the top portion correctly with grey/distorted lower portion
• This means the file was truncated — the first part is valid, the rest is missing
• No repair is possible for the missing portion
• If the photo was in a cloud backup, restore from cloud (Google Photos, etc.)

Solution 6: Document Recovery

For corrupted Office documents or PDFs:

• Try opening in Google Docs/Sheets (handles some corruption gracefully)
• Check for auto-save or temporary copies:
  • Google Docs: automatic version history
  • Microsoft Office: look for ~$filename temp files
  • LibreOffice: check backup directory
• PDF viewers like Adobe Reader may partially render corrupted PDFs

Preventing Future Corruption

For Downloads

1. Stable connection first: Ensure WiFi signal is strong before starting large downloads
2. Free storage: Keep at least 1-2 GB free at all times (3-5 GB is better)
3. Disable battery optimization for download apps: Settings → Apps → Browser/Download Manager → Battery → Unrestricted
4. Don't switch networks mid-download: Stay on the same WiFi until downloads complete
5. Use download managers: They support resumption if connections drop

For File Transfers

1. Verify after transfer: Compare file sizes between source and destination
2. Stable connection: For network transfers, ensure both devices have strong WiFi
3. Don't interrupt: Never unplug USB cables, eject SD cards, or kill apps during active transfers
4. Check SD card health: If transfers to/from SD card frequently corrupt, the card may be failing
5. Avoid filling storage completely: Leave 10% free on any storage — full storage increases corruption risk

For SD Card Health

1. Use reputable brands: Samsung, SanDisk, Kingston — avoid no-name cards that fail early
2. Format periodically: Every 6-12 months, back up card contents, format it, and restore — this refreshes the filesystem
3. Watch for warning signs: Slow read/write, files randomly disappearing, repeated corruption → card is failing
4. Buy A1/A2 rated cards: Higher endurance for frequent write operations
5. Don't remove while writing: Always "eject" through Android Settings before physically removing

Verifying File Integrity with Checksums

When downloading important files (firmware, large software, ISOs):

1. The download source should provide MD5, SHA1, or SHA256 checksums
2. After downloading, verify the checksum matches
3. In AnExplorer, check file properties for hash information
4. If the checksums match perfectly, the file is 100% intact
5. If they differ even by one character, the file is corrupted — re-download

When Files Are Unrecoverable

Accept that a file is lost when:

• No original source exists to re-download from
• No backup copy exists anywhere (cloud, NAS, computer)
• The file is on a physically damaged SD card that cannot be read
• Corruption is too extensive for partial recovery

Prevention (backups) is always better than recovery. Use cloud storage or NAS backups via AnExplorer for irreplaceable files.

Related Guides

• Fix File Download Issues — prevent download failures
• Corrupt SD Card — handle failing storage media
• Slow File Transfer — prevent timeout-related corruption
• Move Files to Cloud — back up files to prevent loss