SD card not recognized? Showing "needs to be formatted"? Physically broken after being forced into a slot? We recover data from full-size SD cards used in DSLRs, mirrorless cameras, camcorders, and audio recorders. PCB repair, controller bypass, and direct NAND chip reading when needed.
Full-size SD cards contain a separate controller chip and NAND memory chip on a PCB. When the controller fails, the NAND can be desoldered and read directly using PC-3000 Flash. MicroSD cards are monolithic, with both components sealed in a single package, requiring spider-board adapters or precision micro-soldering to access the memory.
Unlike hard drive data recovery, which involves replacing physical read/write heads inside a 0.02µm ULPA-filtered clean bench, SD card recovery addresses electronic faults at the controller and NAND chip level. No moving parts means no clean bench requirement, but the recovery still demands precision soldering and specialized flash reading hardware.
Most full-size SD cards use a PCB-based design with a separate controller chip and NAND flash memory. UHS-II cards require a second row of pins using low-voltage differential signaling (LVDS), which typically requires a multi-layer PCB to route those traces. Some ruggedized full-size SD cards (such as the Sony TOUGH series) use monolithic construction where the controller and NAND are sealed together under epoxy, but this is the exception, not the norm. All MicroSD cards are monolithic. Whether a full-size SD card is PCB-based or monolithic depends on the card's age, capacity, speed class, and manufacturer.
On older PCB-based cards, the NAND chip is a separate component that can be desoldered and read directly using PC-3000 Flash. This is standard chip-off recovery, and it works even when the controller is completely dead. On modern monolithic cards, recovery requires precision epoxy sanding and microscopic wiring to exposed test points, identical to the process used for microSD cards.
Monolithic recovery requires either precision spider-board adapters (using needle-like pins pressed against exposed test points) or manual micro-soldering to tap into the sealed package. That process is more time-intensive and typically costs more than standard chip-off. We handle both microSD recovery and monolithic full-size SD recovery.
SD vs MicroSD Architecture
Feature
SD Card
MicroSD
Internal design
PCB + separate chips
Monolithic
NAND removable
Yes (desolder)
No (sealed)
Recovery method
Chip-off or PCB repair
Spider-board soldering
Common use
Cameras, camcorders
Phones, drones, dashcams
What Is SD Express Data Recovery?
SD Express cards use the PCIe bus and NVMe protocol instead of the legacy SD interface, reaching speeds up to 3,940 MB/s. Recovery of a failed SD Express card follows SSD recovery procedures rather than traditional flash card chip-off workflows, requiring PCIe-capable hardware like the PC-3000 Portable III.
The SD 7.0 specification introduced SD Express, which replaces the legacy SD bus with PCI Express lanes and the NVMe protocol. These are the same interfaces used in modern laptop and desktop SSDs.
SD 7.0 uses a single PCIe Gen 3 lane (up to 985 MB/s). SD 8.0 added PCIe Gen 4 x2 support for theoretical throughput up to 3,940 MB/s. The newer SD 9.0 specification focused on enterprise features (Fast Boot, TCG Storage encryption) rather than additional speed increases.
From a recovery standpoint, an SD Express card is functionally a miniature NVMe SSD. The traditional SD pinout is retained for backward compatibility, but when operating in Express mode, the card communicates over PCIe. A dead SD Express card cannot be recovered using standard SD card readers or legacy chip-off workflows. Instead, recovery requires PCIe-capable hardware adapters, such as the PC-3000 Portable III with its PCIe interface module. The diagnostic and imaging process mirrors NVMe SSD recovery rather than traditional flash card recovery.
SD Express cards are still uncommon in consumer cameras as of 2026, but CFexpress Type B (which also uses PCIe/NVMe) is already standard in professional cinema cameras and flagship mirrorless bodies. As SD Express adoption grows, expect recovery costs and procedures to align with SSD-class work rather than traditional flash card pricing.
SD Express Controller Architecture
Current SD Express cards use either the Silicon Motion SM2708 (PCIe Gen 3 x2, SD 8.0) or the Phison PS5017 (PCIe Gen 3 x1, SD 7.0), both using the NVMe protocol. The SM2708 pairs with 3D TLC or QLC NAND and handles wear leveling, ECC, and NVMe command queuing internally. The PS5017 supports similar configurations on a single PCIe lane with Phison's own firmware stack.
Both controllers require 1.8V on the VDD2 power pin to enter PCIe Express mode. If the host device doesn't supply VDD2 (common with older card readers), the controller defaults to legacy UHS-I fallback, limiting speeds to ~104 MB/s. A dead SD Express card can't be imaged through standard SD card readers at all; recovery requires M.2/PCIe bridging adapters on the PC-3000 Portable III to communicate over the PCIe bus. Legacy TSOP-48 flash readers can't access the NVMe command set these controllers use.
What Types of SD Card Failures Can Be Recovered?
SD cards fail differently from hard drives and SSDs. No moving parts, but the PCB, controller, and NAND flash are all vulnerable to physical stress, electrical faults, and wear. The four recoverable failure types are physical PCB damage, controller failure, electrical damage, and file system corruption.
Physical PCB Damage
SD cards are thin and fragile. Forcing a card into a slot at an angle, stepping on it, or bending it can snap the internal PCB or sever traces between the controller and NAND chip.
Recovery approach: Desolder the NAND chip from the damaged board and read it directly with PC-3000 Flash. If the PCB crack is minor, we bridge the broken traces with jumper wires.
Controller Failure
The controller chip manages communication between your camera and the NAND flash. When it fails, the card may not be detected, show 0 bytes, or prompt "needs to be formatted."
Recovery approach: Bypass the controller entirely. Desolder the NAND chip, read the raw data, and reconstruct the file system from the dump.
Common SD card controllers: Full-size SD cards typically use microcontrollers from Silicon Motion (SM2703, SM2706) or Phison (PS8035). Each controller model applies a unique XOR scrambling key to the stored data. During chip-off recovery, the raw NAND dump appears as scrambled noise until the technician identifies and reverses the exact XOR key for that controller. PC-3000 Flash maintains a database of known controller/key combinations, but less-common or newer controllers sometimes require manual key extraction from the controller firmware.
Electrical Damage
Faulty card readers, USB hubs with poor voltage regulation, or static discharge can fry the controller or damage the NAND interface. The card may work intermittently or stop responding entirely.
Recovery approach: Test for short circuits on the PCB. If the controller is dead but NAND is intact, proceed with chip-off recovery.
File System Corruption
Pulling a card from a camera mid-write, power loss during file transfer, or a camera firmware bug can corrupt the FAT or exFAT file system. The card may appear empty, show as RAW, or produce read errors.
Recovery approach: Create a forensic sector-level image of the card. Rebuild the file system from the image or carve files using header signatures.
How Is Data Recovered from a Failed SD Card?
SD card recovery starts with a forensic image of the NAND memory, then progresses through controller bypass, XOR descrambling, and file system reconstruction. The approach is always image-first: we secure a copy of the raw data before attempting any repair.
Unlike hard drive recovery where the primary challenge is mechanical head failure, SD card recovery addresses electronic and firmware-level faults at the controller and NAND chip level. The steps vary depending on failure type.
1
Visual Inspection and Damage Assessment
Inspect the card under magnification for cracked housing, bent contacts, broken PCB traces, or signs of electrical damage (burn marks, discoloration). Test with a known-good reader to confirm whether the controller responds.
2
PCB Repair or Controller Bypass
If the controller still functions, we image the card directly. If the controller is dead or the PCB is damaged, we either bridge broken traces or desolder the NAND chip for direct access. SD cards use standard NAND packages (TSOP-48, BGA, or LGA/TLGA) that can be cleanly removed with a hot-air rework station.
3
NAND Imaging with PC-3000 Flash
The desoldered NAND chip is placed in a reader adapter and connected to PC-3000 Flash. We read the raw memory contents page by page, applying multiple passes to ensure a clean dump. This raw dump includes all data currently stored on the NAND. Note: some camera firmware issues a full erase sequence (SD spec CMD38) during formatting rather than a quick format, physically wiping NAND cells before rewriting the filesystem. If your camera performed a full format, recovery is unlikely regardless of card condition.
Monolith Bus Line Autodetection
Monolithic SD cards (and all microSD cards) seal the controller & NAND in one package with no published pinout diagram. We use the PC-3000 Flash Spider Board Adapter, which presses needle-like pins against exposed bus line test points on the chip surface. PC-3000 Flash's automatic pin sequence detection (introduced in firmware update 7.5.11) resolves the correct bus line order without destructive trial-and-error soldering. The technician sets the spider board needles, selects "Read Chip ID" for the current configuration, and the software identifies the NAND die type & data bus width automatically. This eliminates guesswork on undocumented monoliths where the controller chip marking has been laser-etched off by the manufacturer.
4
Data Reconstruction
Apply ECC correction to fix bit errors, decode any XOR scrambling used by the controller, and reassemble the logical block layout. Once the logical image is reconstructed, we mount the file system (FAT32 or exFAT) and extract files. If the file system is too damaged, we carve files using header and footer signatures.
FAT32 Reconstruction for Legacy Controllers
Older SD cards using AU, SSS, or FC controllers store data without standard translator or block number metadata in the NAND firmware. On these controllers, PC-3000 Flash can't use the usual block-mapping approach to rebuild a logical image. Instead, we use the FAT32 image assembling algorithm (available since PC-3000 Flash update 7.5.14), which performs RAW recovery directly on the last string of the transformation graph. This bypasses the need to manually align blocks based on file system allocation tables, preventing the corrupt folder structures that plague high-capacity FAT32 recoveries on these legacy controllers. The result is a mountable filesystem image with intact directory trees rather than a flat pile of carved files.
5
Verification and Delivery
Spot-check recovered files: open sample photos, scrub through video clips, verify file counts against directory metadata. Deliver recovered data on a new USB drive or external hard drive. We provide a file listing before delivery so you can confirm we recovered what you need.
Recovery for Photographers and Videographers
SD cards are the primary storage medium for professional camera systems. A card failure during a wedding shoot, commercial production, or documentary project means lost revenue and work that cannot be re-created. We recover RAW photos, 4K/8K video, and professional audio from all SD card formats used in DSLR, mirrorless, and cinema cameras.
We recover all professional file formats written by camera systems:
•Audio: WAV, BWF, AIFF from field recorders (Zoom, Sound Devices, Tascam)
RAW and high-bitrate video files are large files written sequentially by the camera. On a freshly formatted card, they tend to be stored contiguously, which aids carving from a raw NAND dump. After cycles of deleting and reshooting, fragmentation increases as the filesystem reuses freed clusters. Formatting the card before each shoot minimizes this effect.
Time-Sensitive Recovery
Wedding photographers and production crews often face delivery deadlines. We offer rush turnaround for professional recovery cases. Standard SD card recovery: 3 to 5 business days. Rush service: 1 to 2 business days for qualifying cases. Contact us to discuss your timeline.
What NOT to Do
✗Do not format the card when prompted by your camera or computer
✗Do not write new photos or video to the card
✗Do not run consumer recovery software on a physically damaged card
✓Remove the card, store it safely, and send it for professional evaluation
Drone and Action Camera SD Card Recovery
Action cameras and drones write MP4 and MOV video in two separate components: the raw video data and the index that maps timestamps to byte positions. When a drone crashes or a GoPro loses power mid-recording, the index is never finalized. Professional recovery reconstructs the container index from the raw video stream to restore playable footage.
Action cameras (GoPro Hero series, DJI Action, Insta360) and drone-mounted cameras (DJI Mavic, Air, Mini series) write video data differently from traditional cameras. These devices simultaneously record a high-resolution MP4 or MOV file, a low-resolution proxy file (LRV), and thumbnail metadata (THM) in parallel streams across the SD card.
MP4 and MOV files use a container format with two critical components: the mdat atom (the raw video and audio binary data) and the moov atom (the index that maps timestamps to byte offsets within the mdat). The moov atom is typically written last, when recording stops. If a drone crashes, a GoPro loses battery, or the card is ejected mid-recording, the moov atom is never finalized. The raw video data exists on the card, but no index tells a media player how to read it.
Consumer recovery software cannot handle this scenario because it relies on intact file system metadata and container headers. Professional recovery uses frame-cadence analysis to reconstruct the container index from the raw mdat stream, reassembling playable video from what appears to be unstructured binary data.
Action Camera Recovery Considerations
•GoPro chaptered recording: GoPro splits long recordings into ~4 GB chapters (GP01, GP02, etc.) on FAT32. A mid-recording failure may leave the final chapter without its moov atom while earlier chapters remain intact.
•DJI thermal cycling: Drone SD cards experience temperature swings from cold altitude air to warm electronics. Repeated thermal cycling accelerates solder joint fatigue on PCB-based cards, which can cause intermittent contact failures between the controller and NAND.
•High write endurance demands: Action cameras writing continuous 4K/5.3K video push SD cards toward their rated write cycles faster than typical photo use. Cards rated for lower endurance (standard TLC) may develop bad blocks and read errors sooner.
NAND Chip-off Workflow on the PC-3000 Flash Bench
Once a full-size SD card is classified as a chip-off candidate (dead controller, shorted PCB, or broken traces between controller and NAND), the card moves to the soldering bench. A $1,200–$1,500 chip-off recovery involves four sequential stages: NAND package identification, controller family routing, multi-die merging, and bad block map reconstruction.
NAND Package Identification
SD card NAND is packaged in one of a few standard form factors, and the package dictates the desolder method. Legacy and industrial cards use TSOP-48, which comes off with a conventional hot-air station at roughly 300°C under a polyimide protective film. Modern high-density discrete NAND uses BGA-132 or TLGA-52, which require a Zhuo Mao or equivalent precision BGA rework station with bottom heat and a thermal ramp profile matching the original reflow.
Monolithic SD cards are a different problem entirely: the controller die and NAND die share a single epoxy-sealed package with no exposed NAND chip to desolder. Monoliths require epoxy sanding to expose the NAND die test points, followed by spider-board probing rather than chip removal.
Controller Family Routing
Every chip-off job begins with controller identification before desolder, because the controller model determines which PC-3000 Flash utility module handles the reconstruction. Silicon Motion SM270x cards route to the SM utility module, which ships with a pre-built XOR key database for most SM270x firmware revisions. Phison PS803x cards route to the Phison utility, which uses a different Flash Translation Layer structure and often requires runtime key extraction from the controller ROM before the NAND dump becomes decodeable.
Samsung and SanDisk-branded cards using in-house controllers have their own modules with controller-specific bad block reservation patterns. Skipping this identification step and applying a generic XOR mask produces files that appear to open but fail checksum validation.
Multi-Die and Multi-Plane NAND
Higher-capacity SD cards (128GB and above) frequently stack two or four NAND dies inside a single package using wire-bonded chip-enable (CE) lines. Each die must be read independently through its own CE pin, then merged into a single logical image in the correct interleave order. PC-3000 Flash reads each die to a separate .bin file; the technician then uses the utility's die-merge tool to combine them according to the interleave pattern specified by the controller family.
Dual-plane NAND (where each die contains two independent planes that can read in parallel) adds a second layer of interleaving within each die dump. Misaligning the interleave pattern by even one page shifts the entire logical image out of alignment and turns recoverable files into noise.
Bad Block Map Reconstruction
Every flash controller reserves a percentage of NAND capacity for bad block replacement. When a block is marked bad during the controller's lifetime, a replacement block from the reserve area takes over its logical address. That mapping lives in the controller's own firmware area and is lost the moment the controller dies.
On chip-off recovery, the reserved blocks appear as fragments of in-order data surrounded by discontinuous offsets. PC-3000 Flash includes heuristic reconstruction that identifies reserved-block candidates based on FAT32 or exFAT allocation hints; stubborn cases require manual bad block map rebuilding using a hex editor and knowledge of the specific controller's reservation policy.
This step is why some chip-off jobs push past the 4 to 8 week baseline window. Rush service (+100) moves a card to the front of the bench queue, but chip-off turnaround is bounded by the reconstruction steps above, not by queue position alone.
Data Recovery Standards & Verification
Our Austin lab operates on a transparency-first model. We use industry-standard recovery tools, including PC-3000 and DeepSpar, combined with strict environmental controls to make sure your hard drive is handled safely and properly. This approach allows us to serve clients nationwide with consistent technical standards.
Serving clients nationwide via mail-in service since 2008. Our lead engineer holds PC-3000 and HEX Akademia certifications for hard drive firmware repair and mechanical recovery.
Our "No Data, No Charge" policy means we assume the risk of the recovery attempt, not the client.
LR
Technical Oversight
Louis Rossmann
Louis Rossmann's well trained staff review our lab protocols to ensure technical accuracy and honest service. Since 2008, his focus has been on clear technical communication and accurate diagnostics rather than sales-driven explanations.
We believe in proving standards rather than just stating them. We use TSI P-Trak instrumentation to verify that clean-air benchmarks are met before any drive is opened.
SD card data recovery starts at $200 for logical file system repair and reaches $1,200–$1,500 for chip-off recovery on monolithic cards. Final pricing depends on the failure type, card architecture (PCB-based vs. monolithic), and the complexity of the NAND reconstruction.
Your flash drive or SD card works, you just need the data moved off it. Rush available: +$100
File System Recovery
$300–$600
Your flash drive or SD card isn't showing up, but it's not physically damaged. Starting price; final depends on complexity
PCB Repair
$600–$900
Your flash drive or SD card has shorted components or won't power on. May require a donor drive (additional cost)
Chip-off Data Recovery
$1,200–$1,500
Your flash drive or SD card needs physical NAND chip extraction to recover the data. 50% deposit required
Detailed Pricing Breakdown
Simple Copy
Low complexity
Your flash drive or SD card works, you just need the data moved off it
$200
3-5 business days
Functional media; data transfer to new storage
Rush available: +$100
File System Recovery
Low complexityMost Common
Your flash drive or SD card isn't showing up, but it's not physically damaged
$300–$600
2-4 weeks
File system corruption. Visible to recovery software (R-Studio, UFS) but not to OS
Starting price; final depends on complexity
PCB Repair
Medium complexity
Your flash drive or SD card has shorted components or won't power on
$600–$900
3-6 weeks
PCB issues: simple shorts, failed components on the drive's circuit board
May require a donor drive (additional cost)
Chip-off Data Recovery
High complexity
Your flash drive or SD card needs physical NAND chip extraction to recover the data
$1,200–$1,500
4-8 weeks
NAND chip extraction via soldering, pin-out identification, and raw data reconstruction
50% deposit required
50% deposit required
Hardware Repair vs. Software Locks
Our "no data, no fee" policy applies to hardware recovery. We do not bill for unsuccessful physical repairs. If we replace a hard drive read/write head assembly or repair a liquid-damaged logic board to a bootable state, the hardware repair is complete and standard rates apply. If data remains inaccessible due to user-configured software locks, a forgotten passcode, or a remote wipe command, the physical repair is still billable. We cannot bypass user encryption or activation locks.
No data, no fee. Free evaluation and firm quote before any paid work. Full guarantee details. Chip-off recovery requires a 50% deposit because the extraction process is destructive to the original media.
Rush fee: +$100 rush fee to move to the front of the queue.
All prices are plus applicable tax.
Flash media pricing covers SD cards, microSD cards, and USB flash drives. For hard drive data recovery or SSD recovery, see those service pages for tier-specific pricing.
SD Card Recovery in Action
MicroSD and SD card recovery share the same NAND chip-off and spider-board techniques. This video shows the process on a monolithic flash card using PC-3000 Flash and ACELAB adapters.
SD Card Recovery Terminology
SD card recovery involves controller bypass, XOR descrambling, and NAND chip-off. These are the key terms referenced during evaluation and throughout the recovery process.
Chip-off
Desoldering the NAND flash chip from the card's PCB and reading it directly with a flash reader (PC-3000 Flash or similar). Used when the controller is dead or the board is physically destroyed.
PCB (Printed Circuit Board)
The thin fiberglass board inside a full-size SD card that connects the controller chip, NAND chip, and contact pads. Cracked PCBs sever electrical traces between components.
Controller
The IC that manages read/write operations, wear leveling, ECC, and communication between the host device and the NAND flash. When it fails, the card is not detected even though data remains on the NAND.
NAND Flash
The non-volatile memory chip that stores your data. SD cards typically use MLC or TLC NAND. The data persists on NAND even after the controller fails or the PCB is damaged.
ECC (Error Correction Code)
An algorithm applied by the controller to detect and correct bit errors in NAND pages. During chip-off recovery, the correct ECC parameters must be identified and applied to produce a clean data dump.
XOR Scrambling
A data transformation applied by nearly all modern SD card and flash memory controllers. XOR scrambling converts stored data into noise-like patterns to prevent repetitive bit sequences that accelerate cell wear in TLC and QLC NAND. The scrambling key is specific to the controller model and must be identified and reversed during chip-off recovery before the file system becomes readable.
SD Card Recovery: Common Questions
Can data be recovered from a broken SD card?
In most cases, yes. Full-size SD cards contain a small PCB with separate NAND flash and controller chips. If the plastic housing is cracked or the PCB has snapped traces, we can often repair the board or desolder the NAND chip and read it directly using PC-3000 Flash. The limiting factor is whether the NAND die itself is physically shattered. If the silicon is intact, recovery is likely.
How much does SD card recovery cost?
SD card recovery starts at $200 for simple data transfers and goes up to $1,200-$1,500 for chip-off NAND extraction. File system recovery (corruption, accidental format) starts from $250. PCB repair for shorted components or broken traces costs $450. We provide a firm quote after a free evaluation; no data, no charge.
Can you recover RAW photos from a corrupted SD card?
Yes. RAW image files (CR2, NEF, ARW, RAF, ORF) are large files that cameras write sequentially. On a freshly formatted card this results in contiguous storage; after cycles of deleting and reshooting, fragmentation increases as the filesystem reuses freed clusters. We image the NAND, reconstruct the flash translation layer to rebuild a logical filesystem image, and extract files directly. If the filesystem metadata is too damaged for reconstruction, we fall back to file carving using known file-type signatures. All recovered RAW files are verified to open correctly before delivery.
What is the difference between SD card and MicroSD recovery?
Architecture. Full-size SD cards use a PCB with a separate NAND chip and controller. The NAND can be desoldered and read with standard chip-off equipment. MicroSD cards are monolithic: controller and NAND are sealed together in a single inseparable package. MicroSD recovery requires precision spider-board adapters or manual micro-soldering to access the die directly, which is more time-intensive and typically costs more.
Do you offer rush turnaround for wedding photo recovery?
Yes. Standard turnaround for SD card recovery is 3 to 5 business days. Rush service can reduce this to 1 to 2 business days depending on the failure type and current lab workload. Contact us to discuss your timeline.
My SD card says it needs to be formatted. What should I do?
Do not format the card. That prompt means the file system metadata (FAT/exFAT table, directory entries) is damaged, but your files are likely still written on the NAND. Do not format the card. On older cameras, this only clears metadata. However, many modern cameras (like Sony Alpha) send an 'SD_ERASE' command during format, which permanently wipes the data from the memory chips. Never format a card you need to recover.
Which camera SD cards do you recover?
All of them. Canon, Nikon, Sony, Fujifilm, Panasonic, Olympus/OM System, Leica, Hasselblad, Blackmagic, RED. The camera brand does not affect recovery; what matters is the SD card's controller chip and NAND type. Common SD card manufacturers include SanDisk, Lexar, Samsung, Sony, Kingston, and ProGrade Digital.
Can data be recovered from an SD card dropped in water or saltwater?
In most cases, yes. The NAND flash chip inside an SD card is sealed in an epoxy or plastic package that resists short-term water exposure. Saltwater is more corrosive and can damage the copper contact pads and PCB traces if the card is not dried quickly. Our process involves ultrasonic cleaning to remove corrosion, isopropyl alcohol displacement of residual moisture, and mechanical cleaning of oxidized test points or contacts. If the controller is damaged by corrosion, we proceed with chip-off NAND recovery. Do not attempt to power on a wet card; short circuits from residual moisture can destroy the controller or NAND die.
Can you recover video from a crashed drone or GoPro?
Yes. Drone and action camera SD cards often fail due to mid-recording power loss (crash, battery depletion, or ejection). When recording stops unexpectedly, the MP4/MOV container's index (the moov atom) is never written, which makes the video file unplayable even though the raw data exists on the card. We reconstruct the container index from the raw binary data using frame-cadence analysis. If the card is also physically damaged from the impact, we combine chip-off NAND recovery with video container reconstruction.
Can deleted files be recovered from an SD card?
In most cases, yes. Standard SD cards and cameras do not use the TRIM command that modern SSDs use to erase data blocks immediately after deletion. When you delete a photo or video from an SD card, the file system marks those clusters as available but the NAND cells retain the data until new files overwrite them. Recovery via file carving is effective as long as the sectors have not been rewritten. Stop using the card immediately to maximize recovery chances.
Should I run chkdsk or recovery software on a failing SD card?
Not if the card has physical symptoms: not detected, wrong capacity, or freezing during reads. chkdsk and file system repair utilities force aggressive read/write cycles across the entire card. On degraded NAND, those extra cycles push failing memory cells past the point of recovery. Software tools are safe only when the card is physically healthy and the data loss is purely logical (accidental deletion, quick format). If the card shows intermittent detection or gets hot during use, stop powering it and send it for professional chip-off evaluation with PC-3000 Flash.
Why don't SD card recoveries require a cleanroom?
SD cards contain solid-state NAND flash chips and a controller IC. No moving read/write heads, no magnetic platters, no spinning disks. Airborne particulate control (cleanrooms, clean benches) protects exposed platters during hard drive head swaps. SD card recovery is entirely electronic: micro-soldering, NAND chip desoldering with hot-air rework, and firmware-level imaging with PC-3000 Flash. A competitor claiming 'ISO 5 Class 100 cleanroom' for SD card work is billing you for overhead that has zero effect on the recovery outcome.
Why do monolithic SD cards take longer to recover than PCB-based cards?
On a full-size PCB card, the NAND and controller are separate packages soldered to a circuit board. We can desolder the NAND with hot-air rework, read it in a TSOP-48 or BGA-152 socket on PC-3000 Flash, then reconstruct the flash translation layer in software. Work typically completes in 4 to 6 weeks. Monolithic cards (nearly all MicroSD and some branded full-size cards) fuse the controller, NAND die, and wire bonds into a single epoxy package with no external NAND pins. We have to grind or etch the package down to expose internal test points, then land the card on a spider-board adapter whose precision needles make contact under mechanical pressure. Pinout discovery alone can consume several days per card family. Total turnaround runs 6 to 10 weeks for monolithic work.
Do you recover data from SD Express cards that use NVMe and PCIe?
Yes, but the recovery path is different from classic SD. SD Express cards (SD 7.0 and later) add a second row of pins that carries a PCIe Gen3 x1 or Gen4 x1 lane running NVMe, on top of the legacy UHS-I bus on the first row. When an SD Express card fails, we first test the legacy SD bus: if the card still enumerates over UHS-I, standard controller imaging often works without touching the PCIe side. When the PCIe side is dead (bent pins on the second row, damaged PCIe PHY, controller firmware corruption on the NVMe side), chip-off is a last resort. The NAND inside SD Express cards uses the same 3D TLC silicon as consumer NVMe SSDs, which means it relies on LDPC error correction and soft-decision decoding that the original controller performs by issuing retry reads at shifted voltage thresholds. Raw chip-off bypasses the controller and cannot reproduce the soft-decision data, so LDPC-protected dumps frequently cannot be corrected offline. In most SD Express failure modes the path that actually recovers data is firmware-level intervention to revive the original controller, not raw chip-off.
Why are Sony TOUGH SD cards harder to open than standard SD cards?
Sony TOUGH cards are molded as a single solid polymer block with no seams, no write-protect switch, and no ribs. The marketing purpose is IP68 sealing and 18x bend resistance; the side effect for recovery is that there is no plastic housing to pry apart. We cannot access the PCB without destroying the shell. Standard opening techniques (nylon spudger along the seam) do not apply. For logical recovery over the SD bus, the sealed construction is an advantage because water intrusion is rare. For physical recovery (dead controller, cracked NAND, shorted caps), we mill the TOUGH shell down on a CNC fixture to expose the internal PCB without damaging the components underneath, then proceed with standard PCB-level or chip-off recovery. This adds roughly a day of fixture and milling time compared with a conventional SD card.
My UHS-II card works in a USB 3.0 reader but not in my camera. What failed?
Almost always the second row of pins. UHS-I cards have one row of 9 contacts and run up to 104 MB/s over a single-ended bus. UHS-II adds a second row of 8 contacts that carry sub-LVDS (low-voltage differential signaling) lanes: a transmit differential pair, a receive differential pair, and a reference clock pair running up to 312 MB/s. The second row is physically recessed and is the first thing to wear out: bent pins from rough insertion, corrosion from humidity or salt, or damaged pads from repeated card swaps. Many cheap USB readers only implement the UHS-I row, so a card with a dead UHS-II row appears healthy to the reader but fails in a camera that negotiates UHS-II first and refuses to fall back. We inspect the second row under a stereo microscope, clean oxidation with isopropyl alcohol and a fiberglass scratch brush, and in some cases rebuild individual pads with UV-curable solder mask and a laser-structured copper patch. If the LVDS transceiver inside the controller has failed silicon-side, we move to chip-off.
How does recovery differ for Canon CR3, Sony ARW, and Nikon NEF files?
Each manufacturer uses a distinct container structure, which affects how file carving rebuilds broken files. Canon CR3 uses the ISO Base Media File Format (the same box-and-atom container family as MP4 and HEIF) with custom Canon boxes (CMT1, CMT2, CRAW) carrying sensor data and maker notes; when a CR3 is truncated we rebuild the container by parsing the static Canon metadata boxes and relinking the image data blocks, not by video-style frame-cadence carving. Sony ARW is a TIFF/EP variant: recoverable ARWs need a valid IFD offset and Sony-specific maker-note tags, so partial ARW carving often returns files that open only in Sony Imaging Edge and not in Adobe Camera Raw. Nikon NEF is also TIFF-based but uses a compressed NEF sensor block with a Nikon-proprietary Huffman table; when the Huffman tree is truncated, demosaicing fails and the file opens as a green frame. We detect the camera model during carving using the first-byte signature plus EXIF MakerNote, then apply the manufacturer-specific container rebuild rules. Canon R5 CR3, Sony A7R V ARW, and Nikon Z8 NEF files all recover with different tools and different failure rates.
What is the difference between chip-off and spider-board recovery in turnaround time?
Chip-off applies when the NAND is a separate package on a PCB card. Setup, preheat, and controlled reflow on an Atten 862 hot-air station at a safe profile (typically 370 to 400 degrees C for roughly 40 seconds at the joints) lift the NAND cleanly; the full bench operation including fixturing and cooldown takes about 10 to 20 minutes. We then place the chip in a TSOP-48 or BGA-152 socket on PC-3000 Flash and start dumping raw NAND pages within the same work session. Translation layer reconstruction adds a few days. Spider-board applies when the card is monolithic: there is no NAND package to remove. We expose internal test points by grinding or laser-etching the epoxy, then land a Spider Board adapter whose precision needles contact those test points without solder for routine cases, or solder a custom fanout board when a card family has no working needle pinout. Building a spider for a new card family can take 2 to 4 days of pinout discovery, and many cards require a unique spider per controller revision. In practice, chip-off cases complete 1 to 3 weeks faster than spider-board cases on comparable tiers. Rush service is available for either path.
Secure Mail-In from Anywhere in the US
Transit Time
1 Business Day
FedEx Priority Overnight delivers to Austin by 10:30 AM the next business day from most US addresses.
Major Origins
New York City1 Business Day
Los Angeles1 Business Day
Chicago1 Business Day
Seattle1 Business Day
Denver1 Business Day
Security & Insurance
Fully Insured
Use FedEx Declared Value to cover hardware costs. We return your original drive and recovered data on new media.
Packaging Standards
✓Use the box-in-box method: float a small box inside a larger box with 2 inches of bubble wrap.
✓Wrap the bare drive in an anti-static bag to prevent electrical damage.
✗Do not use packing peanuts. They compress during transit and allow heavy drives to strike the edge of the box.
MicroSD cards use monolithic architecture requiring specialized chip-off techniques via solderless spider-board adapters or manual micro-soldering. CompactFlash uses a 50-pin PATA interface common in industrial equipment. See our MicroSD recovery or CompactFlash recovery pages.
“All I can say is.. WOW. I spilled water on my laptop and couldn't find anywhere that would fix it, I kept thinking I would have to pay $1000+ for data recovery (always backup your files, kids) and thankfully I found Rossmann! I mailed it in right away!
They do water damage, no problem. Patrick was great and super helpful through the process and made everything smooth sailing. They also fixed my Mac within 48 hours and shipped it right back out to me. It was like all I did was shutdown the computer!”
“They are the best! My daughter spilled water on her keyboard. Apple store would charge $750 even though we still are in warranty saying they don't cover water damage. Rossmann group fixed it would Q-tips and didn't charge me anything! just told me "next time bring in something really broken". Will tell all my friends to go here for tech need!”
“These guys are awesome! Called a bunch of shops around San Antonio and they all said the whole motherboard would need to be replaced after I spilled water on mine and it would cost me around 1000$ to fix it, not only that, all my data would be lost (might as well buy a new laptop).”
