The owner of this memory stick had reasoned their way to a fork and stopped, honestly, at the junction. The stick was "no longer registering on any of my devices"; testing had "confirmed that it is a fault with the memory stick" itself; but was it "a physical issue" or "an internal connection problem"? A fair question with a liberating answer: at the bench, the fork rejoins. Both a physically failing component and a broken internal connection disable the same thing — the stick's ability to present its memory — and both are bypassed the same way. Whichever way the coin fell inside the casing, the memory chip is read directly, and the distinction becomes a finding in the report rather than a fork in the road.
| Media | A USB memory stick — no longer registering on any device; fault confirmed as the stick's own, nature (physical vs connection) unknown. |
| Reported situation | Memory stick · registers on nothing · fault confirmed within the stick · owner unsure: physical damage or internal connection · files wanted back. |
| Fault class | Failed controller or severed internal connection — either fully explains universal non-registration, and the bench distinguishes them under magnification. Data ordinarily intact in the NAND either way; reached by chip-level reading past whichever fault is found. |
| Equipment used | Opened and examined under the stereo microscope — controller, bond wires, traces and memory each inspected, the actual fault identified; the NAND lifted under hot air and read completely on a specialist programmer; the controller's arrangement reconstructed and reversed; files carved by content in PhotoRec, opened and checked, returned on fresh media. |
The two candidate faults are real and distinct. A 'physical issue' in the working sense means a component that has died — almost always the controller, the chip that manages the memory and speaks to the computer. An 'internal connection problem' means the components live but a pathway between them has broken: a cracked trace, a fatigued joint, a bond wire gone. Under the microscope they look nothing alike, and the report will say which it was. But notice what both leave alone: the memory chip's contents. One fault kills the spokesman, the other cuts his phone line. Neither touches the archive he was speaking for.
This is why the fork doesn't need resolving before the recovery is planned — a rare mercy in diagnostics. The chip-level route reads the memory directly, and it works identically whether the obstacle was silicon or solder: the NAND comes off the board and onto a programmer, and the failed part — whichever it was — is simply no longer in the path. The owner's question gets answered because it's interesting and because it goes in the report. The files get recovered regardless of the answer.
The raw read has one more stage worth understanding: nothing on a NAND chip is stored the way a computer would show it. Controllers scatter, interleave and encode as they write, each family its own way, so a raw dump is a jigsaw with a private sorting rule. Reconstructing that rule — from the dump's own internal evidence — is the craft in flash recovery; once it's reversed, filesystems and files reappear, and each file is opened to prove the puzzle was solved right.
The stick opened and the question answered first, under the stereo microscope — component death or broken pathway, noted for the report. Then the route that serves both: NAND lifted under hot air, read in full on the programmer, the controller's scattering reconstructed and reversed. PhotoRec carves the files by content; each is opened and verified before delivery on fresh media.
Both of the owner's possibilities led to the same door, and the door opened. Finding out which it was costs nothing — free diagnostic, answered inside two working days of arrival, with one fixed written figure attached. Chip-level work takes half up front as physical work always does here, the balance strictly on success. The fork in the road turned out to be a scenic detail. The destination didn't move.
Don't resolve it yourself — that's the honest summary. Opening the casing to look tells you little without magnification and risks the pathways that survived; flexing the stick to 'test the connection' can finish a crack that was halfway; and one more device-registration attempt adds wear, not information. You've established the essential fact already: the fault is in the stick. Write down what the stick held, pack it rigid, send it whole. The microscope settles your question in the first ten minutes, and neither answer costs you the files.
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
Half-seen is not half-recovered — the computer's nagging loop ends at chip level, past the broken part
Free diagnostic inside 2 working days of arrival, one fixed quote, no fix no fee on logical faults — start online or ring the freephone.