The Storage Chip Isn't Responding

The decode

A portable SSD is a flash memory package behind a bridge, which frames the whole diagnosis. These drives contain NAND flash managed by an SSD controller, connected to USB through a bridge chip that translates between the two. A fault can sit at any of those layers — the bridge, the controller, or the memory itself — and "won't open" is the visible result of any of them failing. His suspicion of the storage chip is a reasonable read, and the assessment's job is to localise which layer actually failed.

The bridge is the first suspect, because it fails often and is the most recoverable case. The USB bridge is a common failure point on portable SSDs, and when it is the fault, the SSD and its data behind it are entirely intact — the drive simply cannot communicate through the failed bridge. Bypassing the bridge and addressing the SSD's controller directly then reaches the data. So a drive that "won't open" frequently has a healthy memory and a broken translator in front of it, which is the good outcome.

If the controller has faulted, the memory is still very likely intact. Should the fault be the SSD's own controller rather than the bridge, the data remains in the NAND that the controller can no longer present — reachable through the controller's service modes on professional equipment, or by reading the memory directly. As with any controller fault, the problem is access, not existence, and the photos or files sit in memory waiting to be reached.

Reading the memory directly is the last route, with an encryption caveat. Where the controller is genuinely dead, chip-off reading of the NAND is possible — but SanDisk portable SSDs commonly encrypt the flash internally, which means reading the memory around a dead controller can yield encrypted data rather than files. That makes reviving the bridge or controller the strongly preferred route, and it is an honest limitation stated up front rather than discovered late.

The honest prognosis follows which layer failed. A bridge fault is the best case and recovers fully; a controller fault with intact memory usually recovers; a dead controller against encrypted flash is the genuinely hard case. Which applies is established at assessment on professional equipment, and the prognosis stated plainly before any charge — but his data is intact behind whichever component failed, and the common bridge fault is entirely recoverable.

On the bench

The drive was opened and inspected under stereo microscope, the USB bridge and flash examined for damage. The bridge was bypassed and the SSD's controller addressed directly on PC-3000 SSD where the bridge was the fault, and controller service modes used to reach the flash where the controller part-responded. Where the controller was dead, the NAND was read by chip-off subject to SanDisk's internal encryption, and a full image taken at first stable access, hash-verified.

The outcome

The failed layer identified, the bridge bypassed or controller addressed to reach the memory, and a full image taken. The diagnostic costs nothing and completes within two working days of arrival, and the quote is one fixed written figure with VAT already in it; if the data can't be brought back, no charge is made. The decode: a portable SSD is flash behind a bridge, and "won't open" can be any layer — most often the bridge, in which case your data is fully intact behind a broken translator. Localised properly, the common faults recover, and your files come back.

Our case files are written up from genuine enquiries our lab has handled for customers across Swansea and South Wales, anonymised to protect client confidentiality. Each one describes the diagnostic and recovery approach our engineers apply to that fault, using the equipment listed.