Data Recovery Case File · Solid State & Flash · The Right Question, Precisely Asked
Yes to the Procedure, and Two Things Decide Whether the Result Is Readable
His enquiry asks exactly the right question in exactly the right terms. A dead mainboard with storage soldered onto it: "would you be able to remove the memory device from the board, remount it on an adapter that I can then plug into another computer, and access the data?" The procedure exists and is established work. Whether it produces something he can read depends on two things worth settling before anybody unsolders anything.
| Media | Embedded memory device soldered to a failed mainboard — removal and independent reading requested; encryption binding and presentation both to be established |
| Reported situation | Mainboard failed · storage present as an embedded memory device soldered to the board · owner requesting removal and remounting for independent access · owner technically informed · contents required |
| Fault class | Board failure with storage physically separable — removal viable; readability governed by device-bound encryption and by the interpretation the raw contents require |
| Equipment used | Encryption binding established from the platform before any removal · package removed under controlled reflow with the board retained · raw contents read on a matched adapter · boot and user areas presented separately · filesystem interpreted from the image rather than assumed |
The decode: yes, and the two qualifications
Why the answer to the procedure is straightforwardly yes: embedded memory packages are removed under controlled heat and read on dedicated adapters. It is routine work in this field, and it is exactly the right approach for storage on a board that has failed.
The first qualification, and it must be settled first: whether the storage is encrypted to the board. Many systems bind their storage to a security component on the mainboard, so a package removed from it yields data that is present, complete and uninterpretable — because the thing that could decrypt it stayed behind.
Why that has to be established before removal rather than after: if the binding exists, the board is not scrap. It is part of the key, and the approach changes entirely — the board is worked on rather than abandoned, or key material is recovered from it before anything is desoldered.
How to find out: from the platform and configuration rather than from the chip. Whether device encryption was enabled, whether the system carries a security module, and what the machine was used for all bear on it, and none of them requires touching the hardware.
The second qualification, which concerns his phrasing rather than his plan: he describes plugging the adapter into a computer and accessing the data, as though the result will present as an ordinary drive. It generally will not.
Why not: reading a package of this kind returns its raw contents, and such devices are divided internally into boot areas and a main user area. An adapter may present those separately, or present the whole device without partition information a computer recognises — so what arrives is an image requiring interpretation rather than a browsable disk.
What that means practically: the deliverable is the contents plus the work of interpreting them — locating the partitions, identifying the filesystem, and extracting files. For somebody able to work with a raw image that may be exactly what is wanted, and it is worth agreeing which he expects.
What must not happen: the board should not be discarded once the package is removed. Until the encryption question is settled it may be essential, and it costs nothing to keep.
On the bench
Encryption binding was established from the platform before any removal — many systems binding embedded storage to a security component on the mainboard, so a removed package yields complete but uninterpretable data if the key material remained behind, which makes the board part of the key rather than scrap. The package was removed under controlled reflow with the board retained, boot and user areas presented separately, and the filesystem interpreted from the image rather than assumed.
The outcome
Encryption binding established before any removal, the board retained throughout, and the filesystem interpreted from the image. Free assessment, one fixed written figure including VAT; where a chip has to be removed, 50% of parts and labour is payable upfront with the balance only on success — otherwise no recovery, no fee. The decode: yes to the procedure. Two things decide whether it produces something readable — whether the storage is encrypted to the board, and the fact that a removed package returns raw contents rather than a browsable drive.
Removing soldered storage from a failed board
Keep the board — that's the one thing to get right before anything is desoldered. Many systems bind embedded storage to a security component on the mainboard, so a package removed from it yields data that's complete and uninterpretable because the key stayed behind. If that binding exists, the board isn't scrap, it's part of the key, and the whole approach changes. Establish it from the platform and configuration rather than from the hardware. Then expect the result to be a raw image rather than a drive you can browse: these devices divide internally into boot areas and a user area, so the partitions and filesystem need interpreting.
Keep the board — call Easy Data Recovery on 028 9002 0144; encryption binding established before any removal, package removed under controlled reflow, filesystem interpreted from the image rather than assumed.
Request a quote online →
Our case files are drawn from genuine enquiries received by our laboratory over the past ten years, anonymised to protect client confidentiality. Each one describes the diagnostic and recovery procedure our engineers apply to that fault, using the equipment listed.