Quote from: private73123 on Today at 01:34:29 PM

agree but i already pass over all , the controller is damaged.

Can still companies recover it , even if the controller is damaged/ and sdd is encrypted?

ok, so if you already know that's 100% the controller ok. (bad for this modell of SSD)
So we're not talking about the NANDs, we are talking about Sandforce SF-2281 (like that) controller and we're talking about AES256
encryption for firmware and NANDs.
So a readout of NANDs is only interessting to make a copy / backup of NAND image, which is encrypted. (nothing to do with the TrueCypt)
The main problem there is that encryption, which is made from the Sandforce controller. So the 1:1 copy of NAND and
change the baord/etc... is NOT possible/working.

As I wrote, there are some rar! companies which complain about restoring data with this controller type, which was not possible in the past AND for sure
won't be done by "normal" recovering company. (I am not connected to any of these nor I have expi. with them!)
I also don't got any info about how they do this, as they state it takes time, it could be, that they trying to "break" ?? or "calculate"?? the key from the "old" controller? from NAND data?? I have no idea yet, how it could be done.

@Base16: yes that's true, mkae copy, etc.. BUT not the solution. NAND copy of course is "not that problem" (either to desolder or just with "cables")... (-> Sandforce)

The Sandforce SF-2281 controller, is soldered as VFBGA on the board, which I read maybe has a connection/solding problem, I know this kind of connection problems from other kind of this chips on other devices, BUT... not in this case for try-n-error ;-))

I'm also not happy about giving data away, and this is not and recommondation, but there currently three? kind of encryption:
Controller -> AES256 to the the data in a "readbale format" after that you have to use
TrueType (AES256, etc...) to decrypt the image/diskdata and then there is the
wallet.dat encryption AES256-CBC+SHA512

Bye,

NAND pinout:

Controller