Burst · Burst Elite · P300 · P400 · Viper VP4300
Patriot SSD data recovery. Burst, Burst Elite, and a familiar fault.
Patriot's Burst and Burst Elite are budget Phison S11 drives, with the SATAFIRM S11 failure that brings, and they are among the drives most often named alongside the Kingston A400 in recovery-laboratory reports of that fault. The P300 and P310 NVMe drives run the Phison E13T and E21T, the P400 and the Viper VP4300 the E16 and E18. No Patriot-specific fault was documented in our research; the failures belong to the Phison families inside. One Patriot SSD is £300 + VAT after the free look, fixed in writing, 3–5 days at the bench.
Rather talk it through? An engineer answers the bench line
0800 6890668
Models we see, family by family.
Which kind of drive is it →| Family | Models | Controller commonly reported |
|---|---|---|
| SATA | Burst, Burst Elite, P210, P220, Blast, Ignite, Torch | Phison S11 · Silicon Motion SM2259XT · Maxio, by revision |
| NVMe | P300, P310, P400, P400 Lite, Viper VPN100, VP4100, VP4300, VP4300 Lite | Phison E13T, E21T, E12, E16, E18 · InnoGrit on some VP4300 Lite |
| Portable | PXD, Transporter, Supersonic Rage | Patriot drive behind a USB bridge |
What tends to go wrong on a Patriot.
Patriot symptoms, and how long each gives you.
Not listed? Describe it on the form →What the message means on a Patriot.
Describe yours to us →| What you see | The usual reason | Where that leaves you |
|---|---|---|
| It now reports as SATAFIRM S11 | A Phison S11 controller running from ROM; the map is still on the flash | Recoverable on the bench; keep well away from the factory tool |
| 0GB, or a small placeholder size | Fallback firmware, translation table not loaded | Loader in RAM; map rebuilt |
| Not detected at all | Firmware will not load, or the power stage has failed | Diagnostic-state work, or board repair |
| Full size but empty after a tool was run | The drive was regenerated | Only a carve of unreferenced pages is possible |
From the box arriving to your files going back.
Work we have closed →Logged the day it lands, and the first look costs nothing Free
A case number goes on it the day the parcel is opened, and an engineer settles what has actually failed before anything else happens. The drive is read on our own equipment, never in a computer that might send it a TRIM command. Back to you come two things together: a straight note of what is liftable and what is not, plus one figure, fixed and written down. Accept it, or decline and owe us nothing.
Powered on our terms
Every power-on gives a failing SSD another chance to run its own housekeeping. Here the drive is brought up in the controller's diagnostic state instead, which lets the bench speak to the flash directly and keeps damaged firmware out of the conversation.
Past the fault, to the map
Working code is loaded into the controller's memory rather than onto the flash, the service area is read, and the translation table is rebuilt from what is there. Where the controller itself is dead, the chips are read one by one and the controller's scrambling and error correction are undone in software.
A full image, then the volume
Nothing is worked on live. The whole drive is imaged once, weak pages retried in their own passes, and the file system is put back together on the image. Encrypted volumes are unlocked there too, with the key you supply, and never on the original.
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. Recovered data travels home on fresh media bought in for your job, with the postage at our end. Your case is not closed until you have opened the files on a machine of your own.
From the bench
- A Burst that has been fixed with a factory tool and now shows its full size but is empty has been initialised. Say so on the form; a carve may still find a great deal.
- The forum fix ends the recovery. The Phison mass-production tools regenerate the drive and discard the map. If one has already been run, say so; a carve may still find a great deal.
- No DRAM means an exposed map. The S11 keeps its whole translation table on the flash and rewrites parts of it constantly, which is why a bad shutdown so often leaves it in ROM mode.
- One controller, a dozen badges. The method is the same whatever the label, which is why the name on the screen matters more than the name on the drive.
What helps, and what harms.
Do this much first
- Unplug it and leave it unplugged
- Note the badge and the model number
- Tell us if a tool has already been run
- Send the bare drive in an anti-static bag
What sets us back
- Running MPTool or any factory tool
- Flashing firmware from the maker's site
- Letting Windows initialise it
- Trying it in one machine after another
Questions answered before you commit.
My Patriot Burst says SATAFIRM S11. Is the data gone?
No. The Phison S11 controller has fallen back to its ROM because it could not load its firmware, and the data is still on the flash. Unplug it, do not download the fix, and send the form.
Which controller does a Patriot SSD use?
More than one, depending on the model and the year. The free look identifies the controller family before anything is attempted, and that decides the route in: a Phison drive, a Silicon Motion drive and an in-house design are each recovered differently.
What does it cost?
£300 + VAT for one drive after the free look, fixed in writing before any chargeable work. On most jobs no data means no bill.
How long does it take?
3–5 days at the bench after the free look. Priority handling is quoted separately when you ask for it.
Begin here if yours is doing the same thing.
Nothing gets worse while the power is off.
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. On most jobs an invoice only follows the data. Until that list reaches you, leave the drive switched off.