A computer that keeps asking for the same thing has usually stopped being useful. This USB stick was "physically broken", and the machine it met was stuck in a loop: it "recognises there is something in the port", then "says to remove and re-insert" — and doing as it asked changed nothing, however many times the ritual ran. Half-detection like this means the stick's presence registers electrically while the part that should present the memory — the controller, or the damaged connection feeding it — never completes the job. You can't re-insert your way past broken hardware; the files are reached by reading the memory chip directly, and the nagging dialogue box never gets a say again.
| Media | A physically broken USB flash drive, half-detected — the computer registers something in the port and endlessly requests removal and re-insertion. |
| Reported situation | USB flash drive · physically broken · something detected in the port · 'remove and re-insert' loop · reconnecting achieves nothing · files wanted. |
| Fault class | Failing controller or break-damaged connection — enough electrical presence to register, not enough function to present the memory. Data ordinarily intact in the NAND; reached at chip level past the fault. Further insertion cycles are the risk. |
| Equipment used | Opened and mapped under the stereo microscope — the break, the traces and the controller each assessed; NAND lifted under hot air and read on a specialist programmer, the broken pathway bypassed entirely; controller translation reconstructed, files carved by content in PhotoRec, verified, delivered on fresh media. |
'Remove and re-insert' is the computer admitting it's confused. It felt a device arrive — the electrical presence is there — but the conversation that should follow keeps collapsing, so it assumes a bad connection and asks you to try again. On a stick that's been physically broken, the advice is exactly wrong: the connection isn't loosely seated, it's damaged, and each re-insertion flexes a cracked board or a lifting joint one more time. The computer means well. It's also asking you to waggle the patient.
Where the damage sits — a fractured trace behind the plug, a strained joint under the controller, or a controller knocked into half-function — determines nothing about the files. They live in the memory chip, filed away before the accident and indifferent to it. The broken part is the messenger between chip and computer, and this recovery simply retires the messenger.
At chip level the loop has no power. The NAND is lifted from the damaged board and read directly, every page of it, into an image. The controller kept its own scrambled arrangement of that data, so the arrangement is reconstructed and reversed, and the files are carved from the result by content and proof-read. No port, no plug, no dialogue box — just the chip, read on its own terms.
Under the stereo microscope first, the physical break traced across board, joints and controller so the failure is understood rather than assumed. Then the memory chip comes off under hot air and goes into the programmer for a complete raw read. The scrambling is unpicked, PhotoRec carves the files out by content, and each recovered file is opened and checked before the set is written to fresh media for return.
The files off the chip, the remove-and-re-insert ritual over for good. Assessment is free, reported within two working days of the stick arriving, and produces a single fixed quote in writing. Because chip-level recovery is physical work on the hardware, half the figure is due before the bench begins; the balance is only owed on success, and never for an attempt that fails.
Break the loop yourself: take it out and leave it out. Every re-seat of a broken stick flexes whatever has cracked, and the failure that follows the first one is usually worse. Don't be tempted to squeeze or brace the stick in the port to hold a connection — a momentary read that dies partway is how half-written filesystems happen. Bag it, box it, and send it with a line about how it broke. The diagnostic costs nothing and settles what's actually damaged.
Every case file on this site is written up from a genuine enquiry handled for customers across York and North Yorkshire, anonymised to keep client confidence. Each one sets out the diagnostic reasoning and the recovery method our engineers apply to that fault, on the equipment named.
The pin is the doorway, not the data — rebuilt where the board allows it, read at chip level where it doesn't
The chime is the doorbell; the controller never answers — so the memory is read directly, past it
Names without pictures means the index outlived the links — the photos are rebuilt from a read-only image
Free diagnostic inside 2 working days of arrival, one fixed quote, no fix no fee on logical faults — start online or ring the freephone.