| Device | Flash drive |
|---|---|
| Manufacturer | PNY |
| Model | USB flash drive (Phison PS2251-17 / U17) |
| Capacity | 512 GB |
| Interface | USB 3.2 (native USB controller, no bridge chip) |
| Outcome | Full recovery |
Serial numbers and any customer-identifying details are deliberately omitted.
What came in
A 512 GB PNY USB flash drive that had stopped being recognized. Plugged in, it did nothing a computer could see: no drive letter, no device, and the activity light stayed dark.
What we found
The drive is built on a Phison PS2251-17 (U17), a controller that talks USB directly, next to a single NAND package. The board itself was healthy: at 5 volts it drew about 0.08 to 0.10 amps, which is what a powered, running controller looks like, and every supply rail measured where it should (5 V in, about 3.3 V, 1.8 V and about 0.93 V for the controller core). The USB connector pins tested clean in diode mode, the resistors around the controller measured consistent values, and the crystal showed a normal bias voltage. On our USB recovery hardware the drive gave one brief flash of activity and then dropped off, the same at USB 2.0 as at USB 3. The controller was starting its firmware and stopping partway through boot, at the stage where it reads its own startup data and translation tables back from the NAND. The root cause was the NAND: it was failing, with bad pages.
What we did
We measured current draw and every supply rail, tested the USB connector pins and the resistors around the controller, swapped the crystal as a test and refitted the original, cooled the controller and retried, and tried the drive at both USB 3 and USB 2.0 only. We did not run any manufacturer reformatting or "repair" utility: on this kind of controller those tools rebuild the drive from scratch and would have destroyed the data. The recovery came from repairing the drive's firmware, then reconstructing the file system to extract the data.
Outcome
Full recovery.
This is the case behind our post on Phison U17 flash drives that power on but aren't detected. When we wrote it, this drive was still open and we couldn't say whether it was recoverable. It was, in full. One drive is not a prediction about another with the same symptoms, but it shows why the advice in that post matters: no format or mass-production tool had been run on this drive, so the data was still there to recover once the firmware was repaired.
Dealing with something similar? See our flash drive data recovery service, browse more cases in the case log, or read about what makes recovery hard.
Have a flash drive in similar shape? Start with a free evaluation — we'll tell you honestly what's possible with your device.
Request free evaluation →Free evaluation · No data, no fee · Talk directly with a technician.