This NAND pins are grounded:
2 - 13 - 23 - 25 - 27 - 33 - 36 - 40 - 46 -48

_________________
My firmware database:
https://mega.nz/folder/O01DkBRI

ISTM that your NAND array must be powered from both the 3.3V and 1.8V supplies. The Vcc supply (3.3V) would power the logic and the NAND cells, while the VccQ (1.8V) supply would power the I/O section.

Capacitor C168 would provide local bypassing of the VccQ supply for all NANDs. However, if the NAND chips follow the ONFI 2.2 spec, then we would expect that pins 34 and 39 would be connected together.

http://www.onfi.org/~/media/onfi/specs/ ... .pdf?la=en

That said, your latest measurements would suggest that C168 is no longer shorted. Are you certain that your original measurement was correct?

_________________
A backup a day keeps DR away.

Yes i'm sure that pin 34 and 39 are not connected together.
C168 is still shorted.

_________________
My firmware database:
https://mega.nz/folder/O01DkBRI

Sorry, I can't understand the function of C168, nor can I suggest a suitable replacement. It might be interesting to see if the short persists after removing the capacitor.

_________________
A backup a day keeps DR away.

I removed C168, short persist

_________________
My firmware database:
https://mega.nz/folder/O01DkBRI

Does anybody of you know how to JTAG this SSD so that i will be able to see terminal log?

_________________
My firmware database:
https://mega.nz/folder/O01DkBRI

I can't tell if C145 is populated. If not then JTAG probably disabled by removed components, probably some resistors elsewhere. Then JTAG might be disabled in the system as well. Usually companies like Sandforce don't leave JTAG open at the front door.
JTAG and Terminal log are 2 separate things. Terminal Log is from the serial port. I would be interested to see just what is available on the JTAG Port though.

RDT stands for a number of things.. one is "Remote Distributed Testing" and Sandisk would have some software custom for this.
or it could be based on something like this:
which could be more likely.
http://www.google.com.au/url?sa=t&rct=j&q=&esrc=s&source=web&cd=50&ved=0CLUCEBYwMQ&url=http%3A%2F%2Farxiv.org%2Fpdf%2F1203.1536&ei=cfnfVNW_MsSF8gX-3YJI&usg=AFQjCNETSf1r2ZC45XKMblIkGp_oIkIEaA&sig2=oz3DvuW9BmcWMV6hX0AR9A
I have a JTAGulator which would be very good for quickly figuring out the layout/operability of the JTAG port.

Could you please post pictures of the front and back of case so I can try and buy the same SSD and do some testing?

Hi HaQue, thank you for your help.
C145 is populated, C145 tracks are connected to a NAND chip.

Here the pics you asked:

_________________
My firmware database:
https://mega.nz/folder/O01DkBRI

The whole existence of this forum pretty much assumes this advice has already been ignored.

While a philosophical look at encryption might be interesting, it does not in any way address recovering DATA from these devices.. which is what we are trying to do.

Another point, suppose you did have the Key? then what? has anyone figured out steps to use a key to recover customer DATA?

There are problems that can be fixed to recover DATA such as electrical issues.

While I don't disagree with you, I think your post doesn't address the issues of OP and others with similar cases, and is a little off topic.

Old post I know, but it appears the JTAGOTRACER pads may sport a Mictor connector :
http://www.malwaretech.com/2015/04/hard-disk-firmware-hacking-part-3.html

Have you finally solved the ssd repair? Because I have an identical ssd, dead , and I'm sure it can be brought to life somehow.

@alindumitru46, can you provide better photos of both sides of the PCB?

_________________
A backup a day keeps DR away.

Of course, in the last days I was very busy. Now I'll test the option to edit the post

These are the best pictures I can make.

These are the best pictures I can make.
The short story: I purchased 4 Sandisk X100 SSD with a "strange" SMART issue 5 years ago . Only 1 died, after 1 month, the others 3 pcs run fine with max performances in 2 laptops and 1 NUC.
After running for about 1 month, the next day he was not recognized in the BIOS, then by any motherboard I checked.

Can use MHDD or Victoria.

_________________
Hard Disk Drive (HDD), Solid State Drive (SSD, SATA, NVMe, etc), USB Flash Drive and RAID Data Recovery Specialist in Massachusetts

Can you measure the voltages at V1, V2 and V3?


88PG877, Marvell, Field Programmable DSP Switcher, 1 MHz, 7.5A Step-Down Regulator, marking G77, QFN-18, Vin = 3V - 5.5V, Vout = 0.72V - 3.63V:
http://www.marvell.com.cn/selector_guide/downloads/ds/88pg8x7.pdf

ADT7302, Analog Devices, +/-2degC Accurate, Micropower Digital Temperature Sensor, marking T02:
http://www.analog.com/media/en/technical-documentation/data-sheets/ADT7302.pdf

TPS62590, Texas Instruments, 1A, 2.5V to 5.5V, Step Down Converter, 2.25-MHz, marking OAL:
http://www.ti.com/lit/ds/symlink/tps62590.pdf

_________________
A backup a day keeps DR away.

I just finished measuring the voltages at those points, according to the scheme, using a no-name PSU and a UNI-T UT139B digital multimeter.
[URL=http://www.imagebam.com/image/287e99855409024]

Most of those voltages don't make sense. Are you using an appropriate PCB ground reference?? Does your meter have a weak battery??

_________________
A backup a day keeps DR away.

I used the pcb ground
I'll try right now with ground from power connector