Dead nvme Intel 600p -> Data Recovery -> now part is missing

[fzabkar]

I suspect that this is the power distribution layout:

Code:

               .------.
               | 1.2V |
  +3.3V o------|  reg |------.
               '------'      |
                          .-----.
                          | I/O |
                          |-----|
                          | NAND|
                          |-----|
                          |cells|
                          '-----'
                load SW      |
               .------.      |
           Vin |      | Vout |
  +3.3V o------|--/ --|------+
               '------'      |
                   |         |
                PG |         |
                   |      .-----.
                   '----->| I/O |
                          |-----|
                          | cont| SM2260
                          |-----|
                          |core |
                          '-----'
               .------.      |
               | 1.1V |      |
  +3.3V o------|  reg |------'
               '------'

               .------.    .-----.
               | 1.35V|    |     |
  +3.3V o------|  reg |--->|SDRAM|
               '------'    '-----'

[legija]

How about moving controller chip from donor to patient drive ?

It's logical to conclude that controller chip has died as it's not detected, neither in ROM or normal mode.
Though, it might be not bad idea to cut the NAND power and check again, if controller is okay it must enumerate in ROM mode.

[fzabkar]

How about moving controller chip from donor to patient drive ?

It's logical to conclude that controller chip has died as it's not detected, neither in ROM or normal mode.

Read the OP's last post. The load switch has been resoldered (one of the DR shops desoldered it), now the SSD is able to reach ROM mode.

It appears that the load switch controls power to both the NAND array and the flash controller. You can see this is my diagram.

[legija]

Haven't seen that one

Is it also possible that OP didn't soldered it right and NAND array is now disconnected ?

Maybe off topic, but once I killed laptop drive by writing qualcomm phone image, it would try to spin up few times and then nothing, never got it to work again. Incredible that drive controller tried to execute arm code from user area. Did the same to some usb flash drive for fun, and amazingly same happened.

[P.F.]

I wonder if the "data recovery" shops are responsible for the missing resistor AND the load switch problem? If so, then I would have a closer look at your SSD.

BTW, if you have a CCD scanner (not CIS), you can make high resolution images of both drives. Then we can examine them for differences.

..

Unfortunately I do not posses a CCD scanner. I don't posses any equipment to do work of this kind in a efficient way .
To clarify:
The resistor was definitely taken off manually.
Regarding the load switch, it does not look as if anything was done manually.
But the conections are poor, unlike on the donor ssd where the connections look solid and good.
It looks as if it came from the factory with the poor connections and at some point during use maybe a poor connection got disconnected.
Also, maybe a reflow was tried, which resulted in even more broken connections.

Right now I am still looking at the board under the microscope. I've found a cracked resistor and also the Vout connections from the load switch
look as if only 1 of 4 pins is juuust connected. I don't know if it matters, I get the 3.3 volts on the junction. I will rework the Vout connections nethertheless and measure the cracked resistor.

[fzabkar]

Right now I am still looking at the board under the microscope. I've found a cracked resistor and also the Vout connections from the load switch
look as if only 1 of 4 pins is juuust connected. I don't know if it matters, I get the 3.3 volts on the junction.

As long as all 4 pins are wired to a common point on the PCB, then I don't see a problem. However, if the 3.3V supply to the NANDs and the 3.3V supply to the flash controller are connected at the IC rather than the PCB, then it could be that the controller is receiving power but the NAND array is not. This would be unlikely, though. You might like to verify the voltages on the tiny bypass capacitors at the perimeters of each of the big chips just to be sure.

[P.F.]

I've found a cracked resistor ...

No, what appeared to be a crack was just a shadow.
All Vout pins are connected to the same point on the pcb.
and the NANDS get warm. I will make voltage comparisons with the donor ssd.

As far as I understand, PC3000 is of no use with intel ssds which only reach ROM mode?

[P.F.]

I have an IT background. (I managed to reverse engineer the first petya ransom ware
and provided a solution to decrypt victim drives.)

So, if I can't get the drive to work, there are still UART and JTAG ports.
Has the community already the pinouts for those?
Would dumping the firmware help in any way?

[fzabkar]

As far as I understand, PC3000 is of no use with intel ssds which only reach ROM mode?

PC-3000 SSD Systems. The List of Supported SSDs (regularly updated, ver. 2.9.3):
https://blog.acelaboratory.com/pc-3000-ssd-list-of-supported-ssd-drives-regularly-updated.html

PC-3000 Portable III SSD System. How to Recover Data and Evidence from NVMe Drives. Silicon Motion Family (SM2260, SM2263XT, HPH8068):
https://blog.acelaboratory.com/how-to-recover-data-and-evidence-from-nvme-drives.html

The blog doesn't specifically exclude the SM2260 with "Intel modifications", but it doesn't explicitly state that it is supported, either:

This statement would suggest that there is probably no support, even though it refers to a different SM controller:

+ many other drives based on SM2246 (except for the Intel modifications which are not supported!)