Data Recovery Case File · Cameras, Drones & Cards · The Structure Copied, the Content Did Not
Empty Folders on the Destination Mean the Copy Started and Never Delivered
Her enquiry describes a transfer that half-happened. Photo folders moved from a phone card to an external drive, where "the folders are on the external drive but they have no photos inside, and some have a zero-byte file in them." That pattern is specific and informative: creating folders is a different operation from writing files, and the first succeeded while the second did not.
| Media | External hard drive holding a folder structure copied from a phone memory card — folders present and empty, some containing zero-length placeholder entries; source card status to be established |
| Reported situation | Photograph folders transferred from a phone memory card to an external drive via a laptop · folder structure present on the destination · folders containing no photographs · some folders containing a zero-length file · source card condition not stated · photographs required |
| Fault class | Transfer incomplete with directory entries created and content not written — destination structure present without data; source likely retaining content |
| Equipment used | Destination structure treated as evidence of an interrupted transfer rather than absent source content · source card identified as the priority and removed from use · both devices imaged write-blocked before any scanning · destination unallocated regions examined for partially written content · recovered images validated against the folder structure |
The decode: what the pattern means, and where the photographs are
How a copy actually proceeds: in two kinds of step. It creates the destination folders first, walking the structure, and then writes the files into them — which is why a failure between the two produces exactly what she sees.
What the empty folders establish: the operation began and read the source structure successfully. Something enumerated every folder on the card and reproduced it, so the card was readable at least that far.
What their emptiness establishes: the file-writing stage did not complete. Either the source stopped returning content, the destination stopped accepting it, or the operation was interrupted — all of which leave the structure behind as a shell.
What the zero-length entries add, and they are the most specific detail: a file that was created and never written. Copying typically creates the destination file first and then fills it, so a zero-byte entry marks the exact point where the transfer stopped.
Why that is genuinely useful: it identifies which file was in progress. Everything before it in the order transferred successfully or not at all, and the boundary is visible rather than guessed.
Why the source card is the priority rather than the destination: the photographs were never removed from it by this operation. A copy reads the source and does not delete, so unless the transfer was a move, the card still holds everything.
Why that has to be confirmed rather than assumed: some transfer operations delete after copying, and a move that copied nothing but deleted anyway is the bad case. Establishing which was performed is the first question, and the card's current contents answer it.
Why the card must come out of the phone now: if the photographs are still there, they are exposed to everything the phone does. A phone writes continuously, and a card left in one after a failed transfer is losing the very thing being recovered.
What the destination is still worth examining for: partially written content. Where large files were being written when the transfer stopped, fragments may exist in unallocated space — usually less useful than the source, but worth checking.
What the general lesson is: a folder structure appearing on a destination is not evidence that a transfer succeeded. The check that matters is whether the files are there and open, and folder counts match long before file counts do.
On the bench
Destination structure was treated as evidence of an interrupted transfer rather than absent source content — a copy creating destination folders by walking the source structure before writing files into them, so folders present and empty indicate the first stage completing and the second not, while zero-length entries mark files created and never filled, identifying the exact point of interruption. The source card was identified as the priority and removed from use, a copy reading without deleting.
The outcome
Destination structure read as an interrupted transfer, the source card removed from use as the priority, and both devices imaged before scanning. Free assessment, one fixed written figure including VAT; on cards where content has been deleted or overwritten, the figure is payable upfront. The decode: the empty folders tell us the copy started and stopped between two stages. Unless it was a move, your card still holds the photographs — which makes the card the urgent item rather than the drive.
A transfer that produced folders and no files
Take the source card out of the phone now, because unless the operation was a move rather than a copy, it still holds your photographs — and a phone writes continuously to a card left inside it. Read the pattern on the destination as informative: a copy creates the folder structure first by walking the source, then writes files into it, so empty folders mean the first stage completed and the second didn't. A zero-length file marks the exact point where it stopped. And note the general lesson: folder counts match long before file counts do, so structure appearing is not evidence a transfer succeeded.
Secure the source card first — call Manchester Data Recovery on 0161 871 0788; destination structure read as an interrupted transfer, both devices imaged before scanning, unallocated regions examined for partial content.
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.