Data Recovery Case File · Phones & Cards · The Adoption Trap

"Internal" means encrypted: the storage choice nobody explains, the move that couldn't be moved back — and a photo library recovered with its losses honestly named

Her enquiry told the whole story in the order it happened, which is the order that decodes it. The phone: an Android handset at 127GB of a 128GB limit, warning her daily. The sensible fix, on advice: a new 128GB SD card. Then the fork nobody explains: "the phone asked to format the card, so we formatted it to internal memory, and moved all my photos and videos across." Then the horror in two acts: "When I tried to open the files again, they wouldn't open. So I moved the photos and videos back to the phone's internal memory — files still wouldn't open." Nothing about that sequence was careless — every step followed the phone's own suggestions — and the trap it walked into is one of Android's least-signposted: formatting a card "as internal" encrypts it to that phone, and everything downstream of her problem flows from that hidden word.

The decode: what "internal" secretly does, why the files broke — and what the move-back cost

The hidden word, explained: Android offers a new card two lives. "Portable" keeps it an ordinary card — readable in any computer, files plain. "Internal" adopts it: the phone formats and encrypts the card as an extension of itself, keyed to that one handset — faster integration, total lock-in. The dialog says "internal"; it does not say "encrypted, unreadable anywhere else, dependent on this phone's keys forever." Her choice was the one the phone was nudging toward, and the consequence was invisible until it wasn't. Why the files wouldn't open — the honest anatomy: an adopted card working properly serves files normally on its own phone; hers didn't, which means the migration itself went wrong inside the encrypted container — a near-full phone shovelling its entire library across in one marathon move is exactly the high-load, low-space operation where transfers fault: files landing incomplete or with their encrypted envelopes damaged, unopenable even by the phone that holds the keys. And the move-back, decoded gently: returning the files copied the broken results — a second migration of already-damaged goods, adding a second generation of transfer to whatever the first had harmed, and scattering the library across two stores in mixed condition. Entirely reasonable as an instinct; costly as an operation — and the standing counsel it writes: when files won't open after a move, stop moving them — every further transfer copies the damage, not the cure. The recovery's real hope lived in three places her restraint preserved: the phone's key material (intact — the handset works), the card's underlying territory (including remnants of the original transfer), and the phone's own storage (holding both returned copies and traces of the pre-move originals).

The recovery — keys, layers, and an honest ledger

The work ran forensically across both stores: the card and the handset's storage imaged, the adopted-storage keys recovered from the phone itself — the one place they exist — and the encrypted container opened properly offline. Then the triage her double move demanded: every recoverable generation of every file assessed — the card's transferred copies, the phone's returned copies, and the surviving traces of pre-migration originals in the handset's territory — with the best intact version of each photo and video selected, decrypted where needed, and verified by opening. The result was the honest shape this genre produces: the substantial majority of the library recovered whole across the generations, with a bounded set — files caught worst by the faulting migration in all their copies — itemised as damaged or lost rather than glossed. Delivery went out on new media in duplicate, organised as her library had been, with the report closing on the acquittal she was owed: every step followed the device's own prompts; the trap was the unexplained word; the losses belong to a hidden design choice, not to her.

Outcome

The library home in the main, the losses named, the trap documented — and the filings the adoption genre urgently needs. Choose "portable" unless you know why you're choosing "internal": adoption encrypts, locks the card to one handset, and turns every future migration and failure into a keys problem — for photo libraries, portable is almost always the right life. Stop at the first unopenable file: moving broken files back, onward, or around copies the breakage — freeze both stores and ask. And keep the phone safe throughout: on adopted storage, the handset is the keyring — no factory resets, no trade-ins, no repairs that wipe it, until the data's out. She did everything the phone suggested and paid for the word it didn't explain. The explanation is now on the record — and the photos, most of every one of her years of them, are back in plain, portable, twice-stored daylight.

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.