Data Recovery Case File · Cameras, Drones & Cards · You Probably Don't Need Us
Nothing Is Wrong With Your Card
Her enquiry contains its own proof and the answer costs nothing. Importing photographs from a camera card to a phone using an adapter: "the phone indicates there are no photos to import, but when the SD card is in the camera, it shows photos. I'm seeking advice on whether I can fix this myself or if there's any way to recover the photos." Yes, and almost certainly herself. The card displaying photographs in the camera is conclusive — the media is readable and the files are present. What has failed is the import, and phones are unusually fussy about what they will accept.
| Media | SD card from a digital camera — contents displaying normally in the camera; phone import reporting no photographs available |
| Reported situation | Card in use in a digital camera · photographs displaying correctly in the camera · card connected to a phone via a camera adapter · phone reporting no photographs to import · owner seeking a self-service remedy |
| Fault class | No media fault — host import constraints on folder structure, file format, filesystem support or supplied current |
| Equipment used | Card confirmed readable in the originating device · import constraints eliminated in order before any bench work · card imaged write-blocked only where a genuine fault remained · photographs validated by rendering |
The decode: why the phone sees nothing, and the four things to try
Why the camera's display settles it: for the camera to show images, it has read the card's filesystem, located the files and decoded them. That is the whole chain working. Any explanation involving a damaged card is inconsistent with what she is already seeing.
The first and most likely reason — file format. Phone import functions only offer files they can decode. If the camera is set to record in its manufacturer's raw format rather than standard photographs, the phone frequently cannot interpret them and reports nothing to import, even though the files are plainly there. Cameras set to record raw only, or raw plus a small preview, produce exactly this. Checking the camera's quality setting is the single most useful thing to do.
The second — folder structure. Phone imports look in the standard camera folder path and expect standard naming. A camera writing to a custom folder, or one whose card has been reorganised on a computer, may hold perfectly good photographs somewhere the import function never looks.
The third — the filesystem. Large cards are commonly formatted in a way that phones and their adapters do not always mount, particularly older adapters. The card is fine; the host will not read that arrangement through that accessory.
The fourth — power. Camera adapters supply current from the phone, and some cards draw more than a phone will provide, especially on a low battery. A card that mounts on a charged phone and not a flat one is a power problem wearing a fault's clothing.
What to do instead, and it solves this most of the time: use a computer. A card reader on a laptop or desktop reads any folder structure, any format and any filesystem, and copies everything regardless of what a phone is willing to display. The photographs can then be moved to the phone afterwards if she wants them there. This is a fifteen-minute job and requires no professional involvement at all.
When it would become a real case: only if the card subsequently stops working in the camera too. Until then there is no fault to fix, and saying so is the honest answer.
On the bench
The card was confirmed readable in its originating device, since a camera displaying images has already read the filesystem, located the files and decoded them — which is inconsistent with any media fault. Import constraints were eliminated in order before any bench work: recording format, folder structure, filesystem support and supplied current, each of which produces an identical no-photographs result from an entirely healthy card. Imaging write-blocked was reserved for the case where a genuine fault remained, and photographs validated by rendering.
The outcome
The card confirmed healthy, the import constraint identified and the photographs transferred without bench work. Free assessment, and no charge where no recovery is required. The decode, for anyone whose phone reports no photographs to import: your card is fine — the camera displaying images proves the filesystem is readable and the files are present and decodable. Phone import functions are fussy in four specific ways: they only offer formats they can decode, so raw files often show as nothing; they look only in the standard camera folder; they cannot always mount the filesystem on large cards through an adapter; and they supply limited current. Use a computer and a card reader instead.
Phone reporting no photos to import from a card
Use a computer and a card reader instead — that solves this most of the time, and there's nothing wrong with your card. The camera showing your photographs proves the filesystem is readable and the files are present, so any explanation involving a damaged card doesn't fit what you're already seeing. Phones are just fussy importers. They only offer files they can decode, so a camera set to record raw files rather than standard photographs produces exactly this message. They look only in the standard camera folder, so a custom folder structure is invisible to them. They can't always mount the filesystem used on large cards through an adapter. And camera adapters draw current from the phone, so a low battery can look like a fault. A computer ignores all four.
Try a computer and a card reader first — or call Newcastle Data Recovery on 0191 406 1051; free assessment, and no charge where no recovery is needed.
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.