Hi,
I have this defective Corsair Flash Voyager 64GB USB 2.0 key for data recovery. (P/N:
CMFUSBHC-64GB)
Attachment:
File comment: Corsar Flash Voyager 64GB USB 2.0
Corsair-Flash-Voyager-64GB.jpg [ 28.82 KiB | Viewed 4558 times ]
This flash drive use several kind of circuit boards, with 4 NAND chips, 2 on each face.
Was initially briefly detected but froze, could not be ejected, and had to be unplugged manually.
Then when plugged, had the diode flashing every 5 seconds as shown in this video:
https://imgur.com/mvW7bvoOn the back face, I found a defective resistor 2.2Ω at the location R22, which was swapped from a working one, same value.
I also soldered a new inductor at location L1 on the back face, as the original one was absent. I assume there was some broken solder here.
Not sure however what the inductor value should be.
The USB connector appeared in good condition ; was replaced so that I could check the tracks below it.
I could no observe any defect at the tracks.
The controller pins were tinned again and checked as properly soldered to the boards.
The flash diode is no longer emitting any light.
When plugging the flash drive, an "unkown device" is detected, but only after about 12 seconds.
Looks like the flash drive is underpowered in some way.
The controller is a SiliconMotion SM
3252R BA.
There is some info about it on Flash Extractor and PC-3000 websites, but I could not find a datasheet with the pinout.
The PCB is labelled 201ZZZA1. I could not find any info about it.
I measured the voltages on both sides of the PCB, which are shown in the pictures attached.
The continuity of all resistors, capacitors, inductor and diode was checked.
Attachment:
File comment: Not working PCB 201ZZZA1 with controller SM3252R BA, top face, with measured voltages.
PCB-201ZZZA1-of-Corsair-Flash-Voyager-64GB_ANNOTATED.jpg [ 343.05 KiB | Viewed 4558 times ]
Attachment:
File comment: Not working PCB 201ZZZA1 with controller SM3252R BA, back face, with measured voltages.
back-of-PCB-201ZZZA1-Corsair-Flash-Voyager-64GB_ANNOTATED.jpg [ 310.58 KiB | Viewed 4558 times ]
I still assume likely that the problem comes from the circuit board or the controller.
If possible to avoid a chip off, would be nice.