Data Recovery Case File · Mac & Apple Ecosystem · The Photos She Deleted
"I think it's a lost cause — I thought I'd ask just in case": the emptied bin decoded, the four places the photos could still live, and a recovery that meets a hard story with a map instead of a verdict
Some enquiries deserve their answer to begin with the tone. Hers was candid and braced for disappointment: about half a year of photos from an old iPhone, backed up in their day onto a MacBook and, she believed, imported to an earlier MacBook as well. Then, during a period of personal crisis — her words, and they'll stay hers — the photos were deleted from the newer MacBook, and the Recently Deleted bin emptied too. Checking later: the older MacBook holds only fragments; iCloud's library "only starts from January 2022 — no further"; the old phone is two phones ago. "I really want them back but I think it's a lost cause. I thought I'd ask here just in case." The answer this page gives, before any decoding: asking was right, and a lost cause is not what this is. Deletions made in hard moments are among the most common recoveries this trade performs, they are met here without a flicker of judgement — and "deleted everywhere" almost never means what it feels like it means, for reasons the map below walks through, place by place.
| Media | Two MacBooks (a newer one from which the photos were deleted and the bin emptied; an older one holding partial imports) — plus a superseded iPhone and an iCloud library beginning years after the photos' era |
| Reported situation | Photo set deleted and Recently Deleted emptied during a difficult period, as the owner describes it · older machine holds fragments · iCloud coverage starts too late · owner enquiring despite expecting a no |
| Fault class | Multi-device deletion with emptied bin — disk-level recoverability on the deletion machine governed by subsequent use; secondary sources (imports, device-backup containers) independently in play |
| Equipment used | Both MacBooks imaged write-blocked (Atola TaskForce 2, in parallel) · deleted-entry recovery and photo-library analysis on the deletion machine's image · device-backup container hunt and parsing across both machines (OSForensics) · recovered sets reconciled, dated, verified by opening |
The decode: what emptying the bin really does, and the four places that remain
The emptied bin, decoded honestly: the step that felt final — deleting, then emptying Recently Deleted — is the step this archive decodes the same way every time: emptying the bin removes the listings, not, at that moment, the photographs. The image data remains written on the MacBook's storage, unreferenced, until ordinary use gradually writes over it — which makes recoverability there a question of how the machine has been used since, not of how the deletion felt. An "old laptop" that has sat lightly used is exactly the hopeful case: much of a deleted photo set typically survives on such a disk for a long time, reachable by imaging the machine and recovering at disk level, beneath everything the interface shows. Her instinct that emptying the bin sealed it is the natural one; the disk's arithmetic is kinder than the interface's.
The map — four places, checked in order: and the deletion machine is only place one. Place two, the older MacBook: "missing pieces" visible there means an import genuinely happened — and partial visibility often reflects a library's surface, not its depths: photo-library packages hold masters, originals and previous versions inside structures casual browsing never shows, so the fragments she can see may be the lobby of a fuller archive. Place three, the backup containers: an iPhone that backed up "automatically at the time" onto a MacBook left device-backup containers — the sealed, unbrowsable archives this volume has decoded before — and a 2018-era backup surviving on either machine would hold the photos as the phone held them, unpicked by any later deletion of the library. These containers are exactly what people never think to search, and exactly what a proper sweep parses. Place four, honestly bounded: the iCloud start-date she found is simply the library's sync horizon — nothing hidden behind it — and the long-gone phone is noted and released. The recovery, then, is not one long shot; it is four independent chances, two of them good ones, reconciled into a single dated set.
Said once, and warmly: people delete things in hard moments; it is one of the oldest reasons this trade exists, and it changes nothing about the welcome or the work. The only practical urgency is the gentle one: the deletion machine should now rest — every further session spends the disk-level odds — and the rest is the lab's to carry.
On the bench
Both MacBooks were imaged write-blocked in parallel on the Atola TaskForce 2, the deletion machine's odds frozen where they stood. On its image, disk-level recovery swept beneath the emptied bin — deleted photo data identified, carved and validated; on both images, OSForensics ran the search that matters most in this map: the device-backup containers hunted through their tucked-away homes, the era's backups located and parsed, the photographs extracted from inside them with their dates intact. The older machine's library packages were opened properly — masters and originals beneath the visible fragments gathered in. The sets were reconciled, de-duplicated, ordered by date, and verified by opening: the half-year reassembled from every place it had quietly persisted — and delivered without a single question she hadn't already answered.
The outcome
The photo set reassembled from disk-level recovery and backup containers, reconciled, dated, verified and delivered. Free assessment, one fixed written figure including VAT, no recovery, no fee. For everyone carrying a deletion they made in a hard moment and a certainty that it's everywhere-gone: emptied bins remove listings, not photographs; imports and device backups persist in places casual checking never reaches; "just in case" is exactly the right instinct — and the only thing a lab worth its name will hand you, alongside the map, is the work done kindly and no verdict on the moment at all.
Deleted photos in a difficult period — bin emptied, backups coming up short
Be gentler with the odds than you're being with yourself: emptying Recently Deleted removes the listings, not the pictures — the data typically survives on the disk until ordinary use overwrites it, so rest the machine now and the chances hold. Then widen the search beyond the places you've checked: old device-backup containers on any computer the phone ever backed up to hold the photos as the phone held them, untouched by later deletions; photo libraries on older machines often hold masters beneath the fragments you can see; and a cloud library's start-date is a sync horizon, not a wall with something behind it. Bring the whole map to one assessment — and expect, from anywhere decent, exactly no judgement about how the deletion happened.
There are more places than the ones you've checked — call Edinburgh Data Recovery on 0131 202 0491; both machines imaged, bins and backups swept, the set reassembled and verified — one figure, no recovery, no fee.
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.