Taking work now — the first look is freePosted in from anywhere in the UK, or handed in at ten drop-off pointsQuicker still, give us a ring:0800 6890668
SDCSD Memory Card Recovery 0800 6890668 Price my job
SDC / Whatever it is saying now / RAW, 0 bytes, or the wrong capacity

RAW · 0 bytes · no media · 30MB · wrong capacity · controller table · counterfeit · h2testw · F3

RAW, 0 bytes, or the wrong capacity. Three readings in Disk Management, and three different faults behind them.

Disk Management, Disk Utility and the camera's own information screen tell you more than the format dialogue does, and three of their readings arrive here constantly. RAW, next to a volume of the right size, means Windows found the card and could not read a file system on it; it is the format message by another name, a lower-band job of rebuilding the tables on an image. 0 bytes, or no media, means the controller answered the computer but could not find its own translation table in the flash, and is presenting an empty card because it has nothing else to present; the flash is intact behind it and is read directly. A capacity that is simply wrong, 30MB where 128GB should be, 8GB on a card sold as 256GB, means one of two things: a controller that has fallen back to a default identity after losing its table, or a counterfeit card whose controller was told to claim a size it never had. The free look measures what is really there, with the same tools, h2testw and F3, that anyone can run on a new card before trusting it. A card reading RAW at its right size is £149 + VAT after the free look; a card at 0 bytes or the wrong size is monolith work at £299 + VAT, fixed in writing either way.

Free first lookOne fixed figure in writingNo data, no bill on most jobsReturn postage paid

Rather talk it through? An engineer answers the bench line
0800 6890668

Take the card out and leave it out. Do not format it, however politely the computer or the camera asks. Do not run chkdsk, First Aid, a repair tool or a recovery program that offers to fix the card. Do not keep trying it in reader after reader, and do not put it back in the camera to see. A card that reads a little tonight may not read at all tomorrow; whatever is on it is recovered from an image, and the image comes first.

What each reading means inside the card.

A card presents itself to a computer in two steps. The controller first answers the host's identification with its registers, which include its capacity, and the host then reads the first sectors to find a partition table and a file system. RAW is a failure at the second step: the capacity is right, the sectors read, but what is in them is not a file system Windows recognises. The data area behind it is untouched and the tables are rebuilt on an image, or the files carved by signature, as on the format page. A card from a Steam Deck or a Pi shows RAW on Windows because its file system is ext4, and nothing is wrong with it.

0 bytes, or a device with no media, is a failure at the first step. The controller has answered the host, so it is alive, but it reports no capacity because it could not find or could not trust its own translation table, the map in the flash that turns the addresses a computer asks for into the physical pages where the data lives. Without the map the controller has nothing to present, and presents nothing. The flash still holds the data and the map's own history, and the bench reads the flash directly, through the chips on a board or the test pads on a monolith, and rebuilds the map in software. The makers' recovery tools for this state rebuild the map by erasing the card, which is why they are not run.

A wrong capacity on the small side, a few megabytes or a few hundred, is usually the controller in a fallback state: it has lost its table and is presenting its own tiny firmware area or a default identity. The same work recovers it. A wrong capacity on the large side, where the card claims more than any card of its kind holds, or where files written past a certain amount come back as garbage, is a counterfeit. Inside is a small flash chip and a controller programmed to claim a large one; it works until the real flash is full and then writes into nothing. One photography site's published test of a fake 32GB SanDisk Ultra with h2testw reported a few hundred megabytes OK and more than five gigabytes of data lost. Everything that was written to the real flash is recoverable and everything beyond it never existed, and the free look says which is which.

The one thing not to do with any of the three is to initialise, format or repair. Windows offers to initialise a disk that shows with no partition table; the camera offers to format a card it cannot read; the maker's tool offers to restore a card to factory state. Each writes to a card whose contents are intact, and each turns a recovery into a reconstruction.

What it says, and what it means.

Describe yours to us →
What you see The usual reason Where that leaves you
RAW, right sizeTorn tables, or ext4Image; rebuild or carve; or read on Linux
0 bytes, no mediaController alive, table lostFlash read directly; table rebuilt in software
30MB, or a few hundredController fallbackThe same work
Files vanish past a certain amountCounterfeitThe real flash recovered; the rest never stored
Right size, then 0 bytes on the next insertController failingImaged in short passes before it stops

From the envelope arriving to your files going back.

Work we have closed →
01

Logged the day it lands, and the first look costs nothing Free

A case number goes on the envelope and a number on the card the day it is opened, with both sides photographed. The card goes into a reader on a hardware imager that controls how long each read may take, never a laptop slot, and what it presents is read first: its capacity, its identity registers, its file system. That decides whether it is a card a reader can see with a fault in the data, or a card whose controller has stopped, and which band it falls in. The first look is free, and you can stop there owing nothing.

Nothing to pay for lookingA single figure, put in writingNo formats, no repairs, nothing written
02

Imaged, sector by sector, before anything else

A card that answers at all is imaged in full on hardware that limits every read and retries on its own terms, weak areas last, with a map kept of what could not be read. A card that is slow, that drops out, or that has locked itself read-only is imaged the same way, in short passes with the power cycled between them. Nothing is written to the card at any stage, and every later step happens on the image.

Sector by sector, weak areas lastNothing written to the card
03

The flash read through the test pads when the controller has stopped

A card no reader sees is a monolith job. The coating is removed to expose the internal test pads, the pinout is matched against a database or mapped by hand, a needle adapter is fitted, and the raw flash is read out around the dead controller. The scrambling, the error-correction layout and the page and block order are then solved in software, and a virtual image of the card assembled from the raw dump.

Pinout, needles, raw dumpDescrambled and reassembled in software
04

The file system rebuilt, or the files carved, on the image

On the image, the FAT or exFAT tables are rebuilt where they are damaged and read where they are not, deleted entries are brought back, and where the tables are gone the photographs and video are carved out by their own signatures. Video files cut short by a dead battery are rebuilt from a reference clip from the same camera. Every photograph is opened before it goes on the list; a file that will not open is not counted.

Tables rebuilt, or files carvedEvery file opened before it is listed
05

You see the file list before you pay

What was recovered is listed for you first, and only then does a bill exist. Approve the list and it is invoiced; turn it down and it is not, and where nothing has come back, most jobs carry no charge at all. The files go home on fresh media with the card, tracked, with the postage paid here, and your case stays open until you have opened them yourself.

No charge until you accept the figureFresh media, supplied with the job3–5 days at the bench

From the bench

  • Say exactly what Disk Management or Disk Utility shows, or photograph it. RAW, 0 bytes and 30MB are three jobs.
  • Say where the card was bought. Marketplace cards under a big name are the counterfeits.
  • Do not initialise. Windows offers it on every card that has lost its table, and it writes a partition table over the start of the data.

1 in 3 cards that arrive here were formatted, repaired or rescanned by their owner first; nearly all of those would have been the lower band untouched.

One job, followed all the way through.

UK · SDC-2026-0717JOB LOGGED ✓

A SanDisk Extreme 128GB microSD from a GoPro that showed 30.6MB in Disk Management after the camera reported an error, with a fortnight's climbing footage on it and a Windows offer to initialise

The owner did not initialise. On the bench the card identified at 30.6MB in every reader; the controller had lost its translation table and fallen back to its firmware area. The flash was read through the test pads with a needle adapter, the dump descrambled, the table rebuilt in software, and the exFAT volume mounted from the virtual card. The footage was copied out and the last clip rebuilt from a reference.

98% of the footage recovered9 days here, and back by post
Illustrative example — replace with a genuine case

What helps, and what harms.

Do this much first

  • Photograph what Disk Management or Disk Utility shows
  • Say where the card was bought and what it claimed to be
  • Take it out and leave it out
  • Send it tracked; the first look is free

What sets us back

  • Initialising the disk when Windows offers
  • Running the maker's restore or format tool
  • Formatting in the camera
  • Writing a test file to see if it sticks

Questions answered before you commit.

Disk Management says RAW. Is that the same as needing a format?

Yes. Windows cannot read the file system; the data is behind it. Rebuilt on the image, lower band. If the card is from a Steam Deck or a Raspberry Pi it is ext4 and nothing is wrong with it.

The card shows 0 bytes. Is it empty?

No. The controller cannot find its table and is presenting nothing. The flash is read directly and the table rebuilt. Monolith work at £299 + VAT.

The card shows a tiny size. Is it a fake?

A tiny size is usually the controller in a fallback state and is recovered the same way. A fake shows its full claimed size and loses files past the real flash. The free look measures what is really there.

What does it cost?

£149 + VAT for a RAW card at its right size after the free look; £299 + VAT for 0 bytes or the wrong size. Fixed in writing, and on most jobs no data means no bill.

Nothing gets worse while the card is out of the device.

Looking at it is free. Back comes a list of what opened and what did not, together with a single price to finish, set down in writing while you are still free to say no. Until that list reaches you, leave the card in its bag and format nothing.

0800 6890668