Data Recovery Case File · Cameras, Drones & Cards · Card or Phone Storage?

Phone Memory Card Stopped Working: What Was Actually On It?

His enquiry was brief and asked for everything he had lost. "My microSD card which was in my phone has stopped working and I need to recover back all of my photos and documents. I would like to ask how much it will cost please?" The card can be recovered, and how that works is set out below. But there is a question worth settling before any money is spent, and it surprises people: a phone's photographs and documents are frequently not on the memory card at all. Modern phones default to their own internal storage for the camera and for downloads, and a card is often used only for what the owner explicitly moved onto it — or, on some devices, for nothing much at all. Establishing what was genuinely on the card, and what may still be sitting safely in the phone or in a cloud account, costs nothing and occasionally makes the recovery unnecessary.

The decode: where phone data actually lives, then what the card needs

Why the question matters: phones handle storage in ways their owners rarely see. The camera app writes to internal storage by default on most devices, and only saves to a card if that has been deliberately changed in settings. Downloads, documents received in messages and files saved from the web usually land internally too. App data — messages, notes, anything inside an application rather than in a folder — is almost always internal and cannot be moved to a card at all. So a card that failed may hold a great deal, a modest amount, or comparatively little, and the difference determines whether this is an urgent recovery or a minor inconvenience.

The free checks worth doing first: if the phone still works, look at what is present without the card in it — photographs in the gallery, documents in the file manager. Anything visible there is safe and needs no recovery. Check whether photographs were syncing to a cloud account, since a synced library means the pictures already exist elsewhere regardless of what happened to the card. And look at the phone's storage settings, which usually show what has been placed on the card and how much space it was using. Those three checks take minutes, cost nothing, and define the job properly.

What the card itself needs: once the scope is real, the route depends on how the card behaves. If it is detected but unreadable — appearing as a device that will not open, or prompting to be formatted — the filesystem is damaged over intact memory, and the answer is a write-blocked image with the structures rebuilt on the copy. If it is entirely silent, not appearing at any level in any reader, its controller has stopped and the memory is read at chip level through internal pads, then descrambled, error-corrected and reassembled. Both are routine; they differ considerably in effort, which is why the behaviour is established at assessment rather than assumed.

Why phone cards fail: worth knowing for afterwards. A card in a phone lives the hardest life in flash storage — powered continuously, written to constantly by apps and caches rather than occasionally by a camera, and kept warm in a pocket. Sudden failure after ordinary service is their characteristic ending, and it is a reason to treat a phone card as working space rather than as an archive.

On the bench

The scope was established before anything was quoted: what the phone still held without the card, whether a cloud library covered the photographs, and what the card had actually been used for — which narrowed the job to the material genuinely at risk. The card was then assessed for behaviour rather than assumed: imaged write-blocked behind the DeepSpar USB Stabilizer 10Gb where it enumerated, with its filesystem rebuilt on the copy; read at chip level on the PC-3000 Flash with pinout confirmation from the Rusolut VNR database where it did not. Photographs were validated by rendering and documents by opening before delivery on fresh media.

The outcome

The scope confirmed at no cost, the card read at the level its fault required, and the contents validated and delivered. 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 question worth asking first: how much of what you have lost was ever on the card? Phones write photographs and downloads to internal storage by default and keep app data there permanently, so a failed card may hold far less than you fear — check the phone without the card in it, check whether your photographs were syncing to an account, and check the storage settings. Then, if the card genuinely matters, its behaviour decides the route: detected but unreadable is a filesystem rebuild, and silent is a chip-level read.

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.