Call us — 0113 322 3083
Mon–Fri · 9am–5:30pm · No fix, no fee
Start a free diagnostic →

Data Recovery Case File · Cameras, Drones & Cards · Stop Putting It Back in the Camera

SD Card Cannot Be Read: Not Initialised, and What That Means

Her account is a short sequence of events, and the order of them matters. "I have an SD card that was in a camera and I tried uploading the photos to my iPhone with a card reader. It wouldn't work, so I put the SD card back into the camera — when it started saying the card can't be read and it wouldn't let me see the photos. It also said not initialised sometimes." Three things happened in a row, and each one narrows the picture. But the most important thing on this page is not a decode at all — it is a warning about what she has been doing between the events. Every time that card goes back into the camera, it is being offered to the one device most likely to destroy it, because cameras respond to unreadable cards by proposing to format them, and some do so with very little ceremony. The photographs are almost certainly still there. The camera is now the biggest threat to them.

MediaCamera SD card — failed to read through a phone card reader; subsequently reported by the camera as unreadable, intermittently as not initialised; photographs inaccessible
Reported situationTransfer attempt via phone reader unsuccessful · card returned to camera, which then reported it unreadable · intermittent not-initialised message · photographs sought
Fault classFilesystem or partition-structure damage with intermittent presentation — image data intact behind unreadable structures; format prompts the principal risk
Equipment usedCard imaged write-blocked (DeepSpar USB Stabilizer 10Gb) · partition and filesystem structures reconstructed on the image · signature carving with format-aware handling for any structures beyond repair · photographs validated by rendering and delivered

The decode: two different messages, and why the camera is the danger

What "cannot be read" means: the camera powered the card, the card answered, and the camera then failed to make sense of the filesystem on it. Note what that rules out: the card is not electrically dead — a dead card produces no response at all, and the camera would say there was no card present. So the memory is alive and talking, and the problem is the structures that organise the photographs into files and folders.

What "not initialised" means, and why it appears only sometimes: this message is the more alarming of the two and the more informative. It means no valid partition structure could be found — the very first structures on the card, which say where the volume begins and how large it is, are unreadable or damaged. The fact that it appears sometimes rather than always is diagnostic in itself: intermittent behaviour means the card is not returning consistent data on every read, so on some attempts enough is read to recognise a volume and on others it is not. That points at unreliable reads in the region where those structures live, rather than at a card that has been wiped.

Why the phone reader attempt matters: the sequence began there, and it is worth naming as a possibility rather than a certainty. Phone-connected card readers are bus-powered from a device that manages its power carefully, and a card that is already marginal can behave worse under a supply that is less generous than a camera's. That does not mean her attempt caused the damage — cards fail on their own schedule — but a card that was already struggling and then had a difficult session is a very ordinary way for a marginal fault to become an obvious one.

Why the camera is now the enemy: the practical heart of this page. A camera meeting a card it cannot read has one built-in response: offer to format it. That prompt can be a single button press away from an on-screen menu, it is worded reassuringly, and on some cameras it appears automatically as part of preparing the card for use. Accepting it writes fresh, empty structures over precisely the damaged ones that a reconstruction would rebuild from — turning a routine recovery into a much harder carving job. So the instruction is unambiguous: the card does not go back in the camera again, not to check, not to see if it has recovered, and certainly not to try the built-in repair. There is nothing further the camera can tell her, and one wrong menu selection is all it takes.

On the bench

The card was imaged write-blocked behind the DeepSpar USB Stabilizer 10Gb with per-sector timeouts enforced, so that the intermittent region her not-initialised message pointed at could be worked patiently rather than skipped — repeated reads recovering structure data that a camera would never have waited for. On the completed image the partition and filesystem structures were reconstructed until the volume stood up with its folder tree intact; where damage had gone beyond repair, format-aware signature carving recovered the images directly from the card's contents regardless of any catalogue. Every photograph was validated by rendering at full size, the set ordered by embedded capture time, and delivered on fresh media.

The outcome

The photographs recovered by structure reconstruction and validated carving, delivered on fresh media. Free assessment, one fixed written figure including VAT; on cards and sticks where content has been deleted or overwritten, the figure is payable upfront. The decode, for anyone whose card is giving mixed messages: "cannot be read" means the card is alive and answering but its filesystem will not parse, which is a good sign rather than a bad one; "not initialised" means the partition structures themselves are damaged, and its appearing only intermittently means the card is returning inconsistent reads rather than having been wiped; and the single most dangerous thing you can now do is put the card back in the camera, because a camera's answer to an unreadable card is to offer a format, and accepting it destroys the very structures a recovery rebuilds from.

Card unreadable, and sometimes reported as not initialised

Take the card out of the camera and leave it out. Cameras respond to unreadable cards by offering to format them, often behind a friendly prompt or as part of preparing a card for use — and accepting that writes empty structures over exactly the damaged ones a recovery would rebuild from. Don't use the camera's built-in repair or check function either. Read your messages as evidence: "cannot be read" means the card is alive and answering but its filesystem won't parse, which is genuinely good news, and an intermittent "not initialised" means the structures at the very start are returning inconsistent data rather than being erased. Don't run repair utilities on a computer either, and don't accept Windows' offer to format. The card wants imaging once, patiently, with the structures rebuilt on the copy.

Camera saying the card can't be read?
Don't let it format anything — call Leeds Data Recovery on 0113 322 3083; imaged write-blocked under timeout control, structures rebuilt on the copy, photographs validated by rendering.
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.

0113 322 3083