CardDataRecovery.org All articles
Technical Deep Dive

What Actually Dies Inside an SD Card: NAND Wear, Controller Faults, and the Limits of DIY Recovery

CardDataRecovery.org
What Actually Dies Inside an SD Card: NAND Wear, Controller Faults, and the Limits of DIY Recovery

Photo by Photo by Syed kumail Haider on Unsplash on Unsplash

An SD card that stops mounting feels like a software problem. The computer does not show a drive letter, the camera reports a card error, and the immediate instinct is to try a recovery utility. In many cases, however, the fault is inside the card: worn NAND flash, a corrupted controller table, a cracked solder joint, or a failing package. Understanding what actually dies helps users choose the right recovery path and avoid making a bad situation worse.

The Anatomy of a Modern SD Card

A typical SD or microSD card contains NAND flash memory, a controller, a small printed circuit board, and passive components, all sealed in a plastic or epoxy package. In many modern cards, the controller and NAND are stacked in a monolithic package. The controller manages wear leveling, error correction, bad-block mapping, and the logical-to-physical translation table that tells the host device where each block of data resides.

That translation layer is why a card can appear empty even when the flash still holds data. The host sees a logical address space, not the raw NAND. Recovery software reads through the controller, so it depends on the controller remaining functional enough to expose the card and return data. This distinction is central to every recovery decision.

Failure Mode 1: NAND Wear and Bad Blocks

NAND flash has a finite number of program and erase cycles. As blocks wear out, the controller marks them bad and remaps data to spare blocks. A healthy card hides this process. A worn card exhausts its spare area, and errors begin to escape the controller's error-correction capability. Symptoms include slow writes, files that disappear after a reboot, capacity that appears to shrink, and intermittent read errors.

Recovery software can sometimes retrieve files from a card with early NAND wear because the controller still exposes the logical data. The software cannot repair the worn NAND. If the card is still detected, imaging it promptly is the best option. If imaging stalls or produces repeated read errors, a professional recovery lab may need to read the NAND directly with specialized hardware.

Failure Mode 2: Controller Corruption and Firmware Faults

Controller corruption is common in sudden-death cases. The card may be physically intact, but the firmware table that maps logical addresses to NAND blocks becomes inconsistent. The card may report zero capacity, appear as an unknown device, or mount only after repeated attempts. In some cases, the controller enters a protective state and refuses all reads.

This is where consumer recovery software often reaches its limit. Software can scan for file signatures if the controller exposes raw sectors, but it cannot reflash proprietary firmware or rebuild a translation table without vendor tools that are rarely public. Some cards can be revived temporarily by professional tools, but the procedure is model-specific and not a DIY task. Repeated power cycling can worsen controller damage and should be avoided.

Failure Mode 3: Electrical and Mechanical Faults

Bad solder joints, cracked PCBs, damaged contacts, and heat damage can prevent a card from being detected at all. A card that works intermittently when pressure is applied to the reader is showing a mechanical symptom, not a software one. Cleaning the contacts with isopropyl alcohol is reasonable, but bending, baking, or reflowing a card is not. Those techniques can destroy the package and make professional recovery impossible.

If the card is not detected in multiple known-good readers and devices, the fault is likely electrical or controller-level. At that point, software scans are usually pointless. A recovery lab can inspect the board, access test points, and in some cases read the NAND directly in a clean-room environment.

What Recovery Software Can Fix

Recovery software is effective for logical failures: accidental deletion, formatting, file-system corruption, partition-table damage, and some cases of controller-visible bad sectors. Tools such as PhotoRec and TestDisk can carve files from raw data, while Recuva and similar utilities can recover deleted files when the file system is still partly intact. The key is to work from a byte-for-byte image whenever possible.

Software can also recover files from a card that mounts but reports errors, provided the controller remains stable long enough to image the card. It cannot repair NAND wear, rebuild a failed controller, or recover data from a card that never enumerates. Users should expect declining returns as physical symptoms increase.

What It Cannot Fix

No consumer utility can fix a dead controller, severe bad-block exhaustion, or a physically cracked package. Encryption adds another layer: if the card was used in a device with hardware encryption and the key is lost, raw NAND recovery may yield encrypted data. Monolithic packages also limit direct NAND access, which raises the cost and complexity of professional recovery.

A practical rule is simple. If the card is detected and can be imaged without repeated errors, software recovery is worth one careful attempt. If the card is not detected, or if imaging repeatedly disconnects, stop. Further attempts can reduce the chances of a successful lab recovery.

Deciding When to Stop

The decision should be based on data value, not on pride. For a few replaceable files, a free scan and a formatted card may be enough. For irreplaceable photos, legal evidence, or business records, professional service is often justified. US labs commonly quote several hundred to more than one thousand dollars for flash recovery, depending on the failure mode and turnaround time. Ask for a diagnosis and a no-recovery, no-fee policy before shipping the card.

Teardown videos are useful for understanding construction, but they are not a recovery method. Most cards are potted or monolithic, and opening one usually destroys it. CardDataRecovery.org recommends treating any physical intervention as a last resort and documenting every step if a card is being sent to a lab. The goal is not to prove that a card can be opened; it is to recover the memories inside it.

All Articles

Related Articles

Cheap Cards, Real Risks: A 2026 Black Friday Capacity-Testing and Recovery Playbook

Cheap Cards, Real Risks: A 2026 Black Friday Capacity-Testing and Recovery Playbook

Ten Free Recovery Utilities, One Corrupted 128GB Card: A 2026 Test Bench Report

Ten Free Recovery Utilities, One Corrupted 128GB Card: A 2026 Test Bench Report