Your drive is asking to be formatted. Here is what to do instead.

You plug in a USB stick or an external disk and get one of these:

• Windows: “You need to format the disk in drive E: before you can use it.”
• macOS: “The disk you inserted was not readable by this computer.”
• Android: “Corrupt USB drive” or “This USB drive isn’t supported”, usually with a helpful Format button right next to it.

The drive that worked yesterday now claims to be blank. Almost always, it is not.

What the message actually means

A drive stores two different things: your files, and a map that says where each file lives. The map is small, it sits in a fixed place near the start of the drive, and it is written to constantly. Your files are large, spread across the whole surface, and are only written when you save something.

That asymmetry is why this failure is so common. Pull a drive out mid-write, lose power during a copy, or let a cable wobble at the wrong moment, and the map takes the damage. The operating system reads the map, cannot make sense of it, and concludes the drive has no usable filesystem. It has no way to tell the difference between “this drive is blank” and “this drive’s index is corrupt”, so it offers the only thing it knows how to do: write a fresh, empty map.

Your files are still on the surface. What is broken is the thing that finds them.

Why formatting is the wrong button

Formatting writes a new, empty filesystem over the old one.

A quick format only replaces the map, and leaves the file contents alone - which is why files are often still recoverable afterwards. But it destroys the old map, and the old map is what a quick scan reads to bring your files back with their real names, folders and dates. Format, and you drop from “recovery with names intact” to “carve the contents back out and hope you recognise them”.

A full format is worse. It writes over the entire surface. After that, nothing recovers anything, on any platform, at any price.

Android’s Format button does not tell you which one it is doing. Do not find out the hard way.

What not to do

Everything in this list writes to the drive, and every write risks landing on top of a file you have not recovered yet.

• Do not format, quick or otherwise.
• Do not run chkdsk /f on Windows. It repairs the filesystem by discarding the parts it cannot reconcile, which are precisely the parts a recovery scan wants to read. chkdsk is for a working drive with minor inconsistencies, not for one that will not mount.
• Do not run First Aid in macOS Disk Utility, for the same reason.
• Do not let Android “repair” the drive when it offers.
• Do not copy anything onto it, and do not save recovered files back to it.
• Do not keep replugging it hoping it mounts this time. If the drive is failing mechanically rather than logically, every power cycle costs you.

What to do instead

Read the drive with something that does not need the broken map, and does not write to the drive at all.

1. Install USB Data Recovery on your Android phone. Scanning and previewing are free, so this costs nothing to try.
2. Connect the drive - straight in for USB-C, or through a USB-OTG adapter for USB-A. A large bus-powered hard disk may need a powered hub.
3. Run the quick scan. Even on a drive the system calls corrupt, the old records are often still readable. When they are, files come back with names and folders intact. The app reads the drive directly through its own filesystem engines and its own USB stack, so it does not need Android to mount the volume - which is the whole reason it can look at a drive Android has given up on.
4. If that finds nothing, run the deep scan. It ignores the filesystem entirely and rebuilds files from their contents. Slower, and files come back numbered rather than named, but it works when there is no map left at all.
5. Preview before you commit to anything. Photos and videos show at full size, free, and each file is labelled intact, partly overwritten or likely gone.
6. Save to the phone. Never back to the drive being recovered.

After you have your files back

Only once your data is safely off the drive is it worth asking whether the drive itself is still trustworthy.

If the drive corrupted because of one bad unplug, reformatting it now - on purpose, with everything already recovered - usually gives you a perfectly good drive back. If it has corrupted more than once, or if it disconnects during reads, it is failing and it should be replaced rather than trusted with anything you care about.

To reformat it and use it normally afterwards, NTFS Reader handles Windows formats and APFS Reader handles Mac ones - though for a drive you suspect is dying, the right answer is a new drive.

When the data really is gone

Be realistic about the cases where nothing will help: the drive was fully formatted, it has been written to heavily since the loss, it is an SSD that has TRIMmed the deleted blocks, or it is failing at the hardware level - clicking, overheating, vanishing mid-scan. That last case is a job for a recovery lab, and powering it on repeatedly makes their work harder.

Everything else is worth a free scan before you touch that Format button.