False-capacity flash recovery

A counterfeit or falsely programmed memory card can overwrite its own earlier files when real flash capacity is exceeded.

Some counterfeit cards report a larger logical capacity than the NAND physically provides. They may appear to save files normally until writes wrap, overwrite earlier blocks, or return corrupted folders, videos, and photos.

Understand the symptom

The controller can advertise addresses that map repeatedly onto a smaller physical flash area.

WHY

What is happening

A host trusts the capacity reported by the card controller. If firmware falsely maps logical blocks beyond real NAND, later writes can wrap onto earlier physical pages. Sony identifies unusually slow writes, corrupt reads, strange undeletable files, and inability to hold stated capacity as counterfeit warning signs.

What you may see

Symptoms that change the recovery path.

01

Card shows an unusually large capacity

The reported size may not match genuine models or physical NAND.

02

Older files corrupt after new recording

Writes beyond real capacity may have overwritten previous blocks.

03

Folders contain strange names

Invalid mappings or corrupted filesystem metadata are being returned.

04

Capacity tests fail near the same point

Only part of the advertised address space stores independent data.

Protect the source

Actions that can make the situation worse.

01

Fill tests overwrite surviving files

H2testw-style verification writes across the entire device.

02

Formatting hides the original map

New filesystem metadata replaces evidence of how files were allocated.

03

Continued capture wraps more blocks

Every new write can destroy older photos or video.

Do this now

Safe steps before evaluation.

01

Lock and remove the card

Stop the camera, phone, drone, or recorder without taking test media.

02

Preserve packaging and purchase details

Model, serial, seller, labels, and genuine-capacity references help interpret the card.

03

Record file chronology

Identify earliest good files, when corruption began, and the amount written.

04

Image before testing capacity

Any verification should happen only after a best-available read image exists.

NEPFOSYS process

How a data-first evaluation proceeds.

01

Identity and capacity review

NEPFOSYS compares reported geometry, controller behavior, labels, and failure pattern.

02

Best-available flash acquisition

Readable logical space is captured without a destructive fill test.

03

File-level reconstruction

Surviving directories, signatures, fragments, and thumbnails are validated.

A clear next step

Preserve the original device before another repair or recovery attempt.

Start a case with the exact symptoms, incident timeline, prior attempts, encryption details, and the files that matter most. NEPFOSYS will route the case to the appropriate DFW intake or nationwide mail-in path.

Start with a case review

Questions, answered

What customers ask before starting.

Can a fake card really show the advertised size?

Yes. Controller firmware can report a logical capacity larger than the physical NAND.

Should I run a full capacity test?

Not before recovery. These tests write the entire card and can overwrite remaining data.

Can overwritten photos be recovered?

No method can recreate blocks that were fully overwritten, but unaffected regions, previews, and fragments may remain.

DFW local · Nationwide mail-in

Protect the device. Start with the facts.

Start my recovery case