Hello,

I got an interesting case. small USB-C ADATA fall and now the LED is steady green (not flashing at all) and W10 see it as "working properly - Unspecifed device". After 4 min, it will make the "disconnect" noise but will not disconnect it.

It's SM2258H controller and VIA VL716 - USB3.1 to SATA.

I wonder it's USB-C disonnection on one/some traces.
VIA chip issue or Controller.

The fact that it's seen as "unspecifed" is telling me it's no the controller. Most of the time with controller issue, we see the device as "storage device" but no access to memory, here's it slightly different.

I've checked USB-C connection and they seems to be ok. I've also put voltage of VLI USB-SATA Chip if someone has a similar SSD.

If you have any idea... I am thinking of soldering 4 wires on VL716 SATA pin to SATA connector and try this way

thanks
Claude

If the failure was caused by the fall, then the only other possibility I can think of is a shattered crystal. If you shake it next to your ear, do you hear any rattling?

_________________
A backup a day keeps DR away.

Thanks

it's this guy on the red arrow ? No, I hear nothing. the only way to test it is with oscilloscope ?

Reflow the connector pins and the larger inductors in case any of the joints are cracked. Is the disconnect time always the same at 4 minutes ?

_________________
Data Recovery Services in the UK.
https://www.usbrecovery.co.uk/

1. Remove the ROM of the USB-SATA controller.
2. Short the ROM of the SATA controller.
3. Run SMI_flash_ID_ATA.exe and send me the report in the form of a screenshot.

_________________
Auxiliary Tool Used For MonoLith Data Recovery, featuring the industry's most extensive Monolith pinouts
http://flash-matrix.com/

Isn't it sufficient to short the Data Out pin of the bridge ROM to ground rather than removing it?

_________________
A backup a day keeps DR away.

Thank you.

v0.567a
Drive: 2(USB)
OS: 10.0 build 19045
Model: SM2258AB-80-10000000
Fw : 20141211
Size : 0 MB [0.0 GB]
Controller : SM2258AA in ROM Mode
Bank00: 0x2c,0xc4,0x8,0x32,0xa6,0x0,0x0,0x0 - Micron 64L(B17A) TLC 512Gb/CE 512Gb/die
Bank01: 0x2c,0xc4,0x8,0x32,0xa6,0x0,0x0,0x0 - Micron 64L(B17A) TLC 512Gb/CE 512Gb/die
Bank02: 0x2c,0xc4,0x8,0x32,0xa6,0x0,0x0,0x0 - Micron 64L(B17A) TLC 512Gb/CE 512Gb/die
Bank03: 0x2c,0xc4,0x8,0x32,0xa6,0x0,0x0,0x0 - Micron 64L(B17A) TLC 512Gb/CE 512Gb/die
Bank04: 0x2c,0xc4,0x8,0x32,0xa6,0x0,0x0,0x0 - Micron 64L(B17A) TLC 512Gb/CE 512Gb/die
Bank05: 0x2c,0xc4,0x8,0x32,0xa6,0x0,0x0,0x0 - Micron 64L(B17A) TLC 512Gb/CE 512Gb/die
Bank06: 0x2c,0xc4,0x8,0x32,0xa6,0x0,0x0,0x0 - Micron 64L(B17A) TLC 512Gb/CE 512Gb/die
Bank07: 0x2c,0xc4,0x8,0x32,0xa6,0x0,0x0,0x0 - Micron 64L(B17A) TLC 512Gb/CE 512Gb/die
Bank08: 0x0,0xff,0xff,0xff,0xff,0xff,0x0,0x0 -
Bank09: 0x0,0xff,0xff,0xff,0xff,0xff,0x0,0x0 -
Bank10: 0x0,0xff,0xff,0xff,0xff,0xff,0x0,0x0 -
Bank11: 0x0,0xff,0xff,0xff,0xff,0xff,0x0,0x0 -
Bank12: 0x0,0xff,0xff,0xff,0xff,0xff,0x0,0x0 -
Bank13: 0x0,0xff,0xff,0xff,0xff,0xff,0x0,0x0 -
Bank14: 0x0,0xff,0xff,0xff,0xff,0xff,0x0,0x0 -
Bank15: 0x0,0xff,0xff,0xff,0xff,0xff,0x0,0x0 -
Bank16: 0x2c,0xc4,0x8,0x32,0xa6,0x0,0x0,0x0 - Micron 64L(B17A) TLC 512Gb/CE 512Gb/die
Bank17: 0x2c,0xc4,0x8,0x32,0xa6,0x0,0x0,0x0 - Micron 64L(B17A) TLC 512Gb/CE 512Gb/die
Bank18: 0x2c,0xc4,0x8,0x32,0xa6,0x0,0x0,0x0 - Micron 64L(B17A) TLC 512Gb/CE 512Gb/die
Bank19: 0x2c,0xc4,0x8,0x32,0xa6,0x0,0x0,0x0 - Micron 64L(B17A) TLC 512Gb/CE 512Gb/die
Bank20: 0x2c,0xc4,0x8,0x32,0xa6,0x0,0x0,0x0 - Micron 64L(B17A) TLC 512Gb/CE 512Gb/die
Bank21: 0x2c,0xc4,0x8,0x32,0xa6,0x0,0x0,0x0 - Micron 64L(B17A) TLC 512Gb/CE 512Gb/die
Bank22: 0x2c,0xc4,0x8,0x32,0xa6,0x0,0x0,0x0 - Micron 64L(B17A) TLC 512Gb/CE 512Gb/die
Bank23: 0x2c,0xc4,0x8,0x32,0xa6,0x0,0x0,0x0 - Micron 64L(B17A) TLC 512Gb/CE 512Gb/die
Bank24: 0x0,0xff,0xff,0xff,0xff,0xff,0x0,0x0 -
Bank25: 0x0,0xff,0xff,0xff,0xff,0xff,0x0,0x0 -
Bank26: 0x0,0xff,0xff,0xff,0xff,0xff,0x0,0x0 -
Bank27: 0x0,0xff,0xff,0xff,0xff,0xff,0x0,0x0 -
Bank28: 0x0,0xff,0xff,0xff,0xff,0xff,0x0,0x0 -
Bank29: 0x0,0xff,0xff,0xff,0xff,0xff,0x0,0x0 -
Bank30: 0x0,0xff,0xff,0xff,0xff,0xff,0x0,0x0 -
Bank31: 0x0,0xff,0xff,0xff,0xff,0xff,0x0,0x0 -

There's 4 NAND on this SSD.

I have checked the datasheet, and the NW917 single chip contains 4 CE. This SSD has 4 physical chips, and the software shows a CE map with 16 CE. This at least indicates a good connection between the flash memory and the controller. Sometimes, when the SSD accidentally falls, it can cause BGA solder balls to detach, leading to the SSD not being recognized. Now, you can remove the short circuit point, remove the capacitors on the SATA differential signal lines, and connect them to the SATA connector. If the power supply is functioning correctly, you can still use the USB interface to power the SSD, saving additional work to power the SSD controller. After completing the above operations, if you are lucky, you may find the hard drive on your computer. I recommend using PC3000 or MRT devices because the soldered wires may not comply with differential rules, and your computer may not recognize the device, but professional data recovery tools can tolerate such situations.

_________________
Auxiliary Tool Used For MonoLith Data Recovery, featuring the industry's most extensive Monolith pinouts
http://flash-matrix.com/

Thank you for your help. I need to remove short and solder ROM as well ?

If you have bypassed the USB-SATA bridge controller by removing capacitors and connecting wires, there is no need to solder the ROM, as the bridge controller won't be able to communicate with the SSD controller. The ROM chip provides microcode to support features like UASP and sleep for the bridge controller. If you remove the ROM chip, it will revert to its most basic functionality. Removing the previously shorted ROM jumper cap is necessary, as shorting the ROM puts the SSD into factory debug mode.

_________________
Auxiliary Tool Used For MonoLith Data Recovery, featuring the industry's most extensive Monolith pinouts
http://flash-matrix.com/

Thanks for your help !.

Now I am getting drive in ready state in PC-3000 but when I run utility it's stuck in BSY

If the SSD firmware is not damaged, the current failure symptom is likely due to the soldered wires not complying with the SATA differential rules. Please try to minimize the length of the connecting wires and twist the differential lines into a helical shape. Then, wrap them with copper foil or aluminum foil and ensure proper grounding. Adjust the communication protocol speed in the PC3000 utility program, aiming for the lowest possible communication rate. Let's see if these steps result in any improvement.

_________________
Auxiliary Tool Used For MonoLith Data Recovery, featuring the industry's most extensive Monolith pinouts
http://flash-matrix.com/

Thank you very much for all your help. . I will try again tomorrow and see if I get a better result.

I wish I knew more about this kind of stuff. Care to share a photo of what you did?

_________________
Joep - http://www.disktuna.com - video & photo repair & recovery service

Pictures are worth 1000 words but .... Its the same principle as converting a usb 2.5" hdd. find the sata in channels - for the usb -> sata chip they're listed on the data sheet but they're obvious to spot. 2 pairs of 2 tracks running parallel. Remove the inline caps breaking the connection and reroute the signal with short wires directly to sata adapter.

I'll be interested to see if this gets anywhere now theres access to the controller even though there's no support in pc3K for it.

_________________
Data Recovery Services in the UK.
https://www.usbrecovery.co.uk/

VL716 datasheet:
https://datasheet.lcsc.com/lcsc/1805251219_VIA-Tech-VL716-Q4_C69727.pdf

Silicon Motion SSD reference circuits and datasheets:
http://www.hddoracle.com/viewtopic.php?f=46&t=3175

NW917 = MT29F2T08EMHAFJ4-3R:A
https://www.micron.com/support/tools-and-utilities/fbga?fbga=NW917

_________________
A backup a day keeps DR away.

Yeah, I realized that 5 minutes after asking

_________________
Joep - http://www.disktuna.com - video & photo repair & recovery service

If it's on the interwebs, Franc will find it!

_________________
Joep - http://www.disktuna.com - video & photo repair & recovery service

I think it's a FW issue. Cabling looks ok.

I am trying to upload ADATA loader from PC-3000, uploading it working, I get Physical access but some settings are incorrect.