Data Recovery Case File · Solid State & Flash · A Different Kind of Drive

Storage That Cannot Be Removed

His enquiry identified the storage type precisely, which saves a great deal of guessing. His daughter's laptop has "a 64GB eMMC chip soldered to the system board. Are you able to recover the data on the eMMC device?" Yes, usually — and the reason is worth explaining, because eMMC sits in an unusual position. It is not a drive that can be unplugged, so every route runs through the board. But unlike the storage in a modern premium laptop, it is frequently not encrypted at all, which makes reading it directly a genuine option rather than a dead end. One question decides which of those two worlds applies.

The decode: what eMMC is, and the question that decides the case

What eMMC actually is: a single package containing both flash memory and its controller, soldered directly to the mainboard. It is what manufacturers use where a drive would be too expensive or too large — budget laptops, tablets, and a great many appliances. Functionally it behaves like a very small solid-state drive, but there is no connector, no caddy and nothing to unplug. That is why an ordinary repair shop cannot simply pull the drive and copy it.

Why it is nevertheless readable: eMMC packages expose a defined set of contacts, and manufacturers usually route those to test pads on the board. Where the machine can be powered enough to hold the storage in a readable state, the memory can be addressed directly through those pads without removing anything. Where it cannot, the package is removed and read on a programmer — a well-established procedure on this kind of device.

The question that decides everything: was device encryption switched on? This is the single fact that separates a straightforward job from an honest no. Many budget machines ship with storage unencrypted, in which case reading the memory directly returns an ordinary readable filesystem and the recovery is largely mechanical. But if encryption was enabled — and on some configurations it switches on automatically once an account is signed in — the key lives in the machine's security chip rather than in the storage, and a package read separately returns ciphertext. In that case the route has to keep the board alive and unlock against the owner's own credential instead.

What to establish before anything else: whether the machine ever showed a recovery-key prompt, whether the account was signed in to a cloud account, and whether a recovery key was ever saved. Those answers determine the plan and cost nothing to find out.

Why these devices fail in the first place: worth a note. A 64GB budget machine spends its life close to full, and system updates alone can consume most of the free space. eMMC has considerably less spare capacity and endurance than a proper solid-state drive, so it wears faster under that pressure — which is why these fail more often than their size suggests they should.

What not to do meanwhile: not attempt a reset or a reinstall to get the machine working. On an encrypted configuration a reset discards the key permanently, and on an unencrypted one a reinstall writes over the space holding the data.

On the bench

The encryption status was established before any route was proposed, since that single fact separates a readable filesystem from ciphertext and determines whether the board must be kept alive. Where the storage was unencrypted, the board service pads were probed and the memory addressed directly without removing anything; where that was not possible the package was removed and read on a programmer. Where encryption was in force, the route kept the board running and unlocked against the owner's own credential. The filesystem was reconstructed and the contents verified by opening.

The outcome

The encryption position established first, the memory read at board level and the contents reconstructed and verified. Free assessment, one fixed written figure including VAT, 50% of parts and labour upfront with the balance only on successful recovery. The decode, for anyone with soldered eMMC storage: there is no drive to remove, so every route runs through the board — but the package exposes defined contacts that manufacturers usually route to test pads, so it can be read directly or removed and read on a programmer; the deciding question is whether device encryption was on, because unencrypted eMMC returns an ordinary filesystem while an encrypted one returns ciphertext without the key from the machine's security chip. Don't reset or reinstall.

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.