Rocket · Rocket Q · Rocket 4 Plus · Rocket 5 · Rocket Nano
Sabrent SSD data recovery. Rocket on the box, Phison on the board.
Sabrent's Rocket range is Phison from end to end: the E12 in the original Rocket, the E16 and E18 in the Rocket 4 and 4 Plus, the E26 in the Rocket 5, and Phison's enterprise parts in the larger Rocket Q drives. Sabrent has revised drives under the same name more than once, so the free look identifies which board it is. The Rocket Nano portables are a Sabrent drive behind a USB bridge. No Sabrent-specific fault was documented in our research; the failures are the Phison E-series ones. One Sabrent 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 |
|---|---|---|
| Rocket NVMe | Rocket (E12), Rocket Q (E12S, QLC), Rocket 4 (E16), Rocket 4 Plus (E18), Rocket 4 Plus-G, Rocket 5 (E26), Rocket 2230 (E21T) | Phison |
| Portable | Rocket Nano, Rocket Nano V2, Rocket XTRM-Q Thunderbolt | Sabrent drive behind a USB or Thunderbolt bridge |
What tends to go wrong on a Sabrent.
Sabrent symptoms, and how long each gives you.
Not listed? Describe it on the form →What the message means on a Sabrent.
Describe yours to us →| What you see | The usual reason | Where that leaves you |
|---|---|---|
| Not in the BIOS, or listed at 2MB | Firmware not loaded on the Phison controller | Diagnostic-state work; the flash is usually intact |
| Vanishes under sustained writes, back after a reboot | A controller crash, or on PCIe 5.0 drives a thermal shutdown | Stop using it; image it before it gets worse |
| Read-only | Spare blocks exhausted; drive protecting itself | Usually fully readable |
| Dead straight after a firmware update | The write stopped half-way | Loader in RAM; map from the service area |
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
- Sabrent's Control Panel is for healthy drives. Do not run its firmware update on a drive that is already misbehaving.
- Phison's NVMe controllers are well understood on the bench, from the E12 and E13T of the budget drives to the E16 and E18 in the fast ones, which is good news for the badge that sits on top of them.
- The PCIe 5.0 E26 drives had a documented thermal shutdown when run without a heatsink, since addressed in firmware by the makers who use it. A drive that shuts down under load should be imaged, not updated.
- Do not put a failing NVMe stick in a USB enclosure. The bridge hides the messages we need and has its own ideas about power states.
What helps, and what harms.
Do this much first
- A full shutdown, please: neither sleep nor hibernate
- Write the full model and part number down
- Deleted something? Send the form the same day
- The stick travels on its own — no caddy, no enclosure
What sets us back
- Rebooting over and over hoping it turns up
- Pushing new firmware at a drive already misbehaving
- Letting Windows initialise it when it asks
- Running recovery software on a drive that keeps dropping out
Questions answered before you commit.
Is a Sabrent Rocket easier to recover because it is Phison?
It is a known quantity. Phison's E-series is well understood on the bench, which is good news for the badge on top. The failures are the E-series ones, and so are the routines.
Which controller does a Sabrent 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.