WD Green SSD 20-82-00469-2 (SM2258XT) Short pins

[alphageeks]

Hello

Can someone please tell me where short pins (safe mode) are located.

Photo attached

Thank you

[Roman_TS]

Hello.

WD Green can be based on 5 different CPU platforms:

1. SM2258XT
2. Maxiotech
3. Sandisk 82-00-469
4. Lexar DM918
5. Realtek RTK

We can deal with SM2258XT modification, while Maxio and Sandisk modifications are not supported.
Sandisk 82-00469 is a native Sandisk CPU which isn't connected with SM2258XT controller.

[alphageeks]

Thanks for you response, any idea when it may be supported?

[Roman_TS]

It's still possible to recover data via Chip-Off, but:

1. NAND chips must be configured in PC-3000 Flash for a correct CE for LUN reading. As the result, you may get a dump with 50% zero sectors after first 50% of DA.
2. There would be a massive number of bit errors, so we should prepare for rereading;
3. Image Building will not be possible, because CPU algorithm is using a lot of different sub-blocks, update-blocks and translator tables to address everything;
4. The only possible result - is a RAW recovery, without Folder Structure. And most likely a lot of data will be damaged with ECC.

At this moment, our developers are working under Sandisk CPU researching to add the native Sandisk CPU-based drives into support list. But at this moment, I'm afraid, we don't have an approximate time when it would be ready.

[c.vogl@solution.at]

Hello,

is it also possible to swp the controller? or is it encrypted unique?

[Roman_TS]

The main problem of the failed SSD is a damaged Firmware (translator part). So, the question is - how the controller swap will help you?

All unique information is located inside the NAND chips (firmware is located in Service Area - reserved pool for storing service structures and the main firmware). If the problem is inside the FW, then CPU swap will not help you - damaged firmware would be still the main reason of the SSD fault.

NAND swap from damaged SSD to a good donor is recommended only in case if the original PCB has serious issues with the electronic components.

[gameboybin]

Source of the post It's still possible to recover data via Chip-Off, but:

1. NAND chips must be configured in PC-3000 Flash for a correct CE for LUN reading. As the result, you may get a dump with 50% zero sectors after first 50% of DA.
2. There would be a massive number of bit errors, so we should prepare for rereading;
3. Image Building will not be possible, because CPU algorithm is using a lot of different sub-blocks, update-blocks and translator tables to address everything;
4. The only possible result - is a RAW recovery, without Folder Structure. And most likely a lot of data will be damaged with ECC.

At this moment, our developers are working under Sandisk CPU researching to add the native Sandisk CPU-based drives into support list. But at this moment, I'm afraid, we don't have an approximate time when it would be ready.

Hey Roman! Should the chips be automatically ID in the PC3000 Flash. Just wanted to get the dumps out

[Roman_TS]

There is no ID at all in your case. Chips are not reading. I recommend you to clean the bottom side of the NAND and try again.