Trust me am aware of this, but again not as easy as it looks. process requires preparation and manually extract it.
In addition I prefer the commercial ver. to make some $$$ out of this, the tool as you mentioned is not a good idea for commercial purpose but personal usage i Agree

_________________
Kuwait Data Recovery - UNIX GTC
The only reason for time is so that everything doesn't happen at once. By: Albert Einstein

Yes, I understand that. I just don't understand why you need to wire your patient to your donor.

You say you will be offering a commercial product. What will that entail?

_________________
A backup a day keeps DR away.

1. Sometimes PCB does not work, and moving MCU seems like an easier task than soldering tens of wires. This is maybe 5% of all recoveries.
2. Out of those cases when PCB is broken and after MCU is moved about 10% don't work, because the MCU itself has problems (the drive either clicks or does not come ready or similar). In these cases maybe this solution would work
3. What nobody mentioned here is that IF the keys can be extracted from the MCU, there is no need to write them to another MCU, data can be decrypted with software. So extracting keys seems like a move to the right direction.

_________________
SAN, NAS, RAID, Server, and HDD Data Recovery.

knowing the key is just the start, one needs to know other params of the encryption, like salt value, how these are used, which might be tricky in the case of a hw based encryption.
DEK is usually wrapped using some method using the KEK, which is usually some hash of user pwd. Pwd padding, hash count, hash algo, all these methods need perfect discovery. Of course ideally this is the way, but until all these are reversed, writing the MCU key to another mcu might be just as fine.
I was also into it in some extent, but yeah, lack of time...

_________________
Adatmentés - Data recovery

I can do all that for Chargers, just need to know the MCU keys

_________________
SAN, NAS, RAID, Server, and HDD Data Recovery.

nice then

_________________
Adatmentés - Data recovery

What does this mean, and why does the commercial product need a "bridge"? Or is your interpretation of "bridge" something other than the USB-SATA bridge? Once you release the product, everyone will see how it is constructed, so I can't see the point of obfuscation.

_________________
A backup a day keeps DR away.

I have to disagree with you here Doomer:

1- Removing the MCU Key will result in encrypted data
2- Moving Key to another MCU PCB works (tested)

_________________
Kuwait Data Recovery - UNIX GTC
The only reason for time is so that everything doesn't happen at once. By: Albert Einstein

I mean the new commercial product will be based on that, instead of wiring we use the jumper pins (similar to this image)

_________________
Kuwait Data Recovery - UNIX GTC
The only reason for time is so that everything doesn't happen at once. By: Albert Einstein

I understand you are using pogo pins, but I don't understand your reference to a bridge. The donor and patient PCBs have their own USB-SATA bridges, so are you saying that the donor PCB needs to use the patient's bridge? Otherwise you are mangling the terminology.

_________________
A backup a day keeps DR away.

@ fzabkar

As i said before, the point of the bridge is as a Ref. idea probably you didn`t get my point yet.

_________________
Kuwait Data Recovery - UNIX GTC
The only reason for time is so that everything doesn't happen at once. By: Albert Einstein

What is a "Ref. idea"? And no, I don't get why you are still referring to a bridge if there is none. Most of all, I don't understand your contribution to the project, other than pogo pins.

_________________
A backup a day keeps DR away.

Nobody noticed, what if the MCU is physically damaged or the entire native PCB is missing.

Is there a solution ?

https://forum.hddguru.com/viewtopic.php ... 33#p317233


i asked this question but i didn't get any answer about it!
At this point i believe that this is just a pogo connection between PCBs, useful when patient pcb is unrepairable but MCU is still working (in this case is much simple to just swap mcu).
With lost/damaged patient mcu this "solution" is not applicable, i believe

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

Sorry friend didn't see your reply.


Exactly.

@michael chiklis sorry i did not pay attention to that particular note,

I did not face any completely dead MCU and i believe its difficult to have one. (can try if i get one)
in case of pcb damaged and beyond repair i believe its possible to extract the key and write it back to donor pcb.

_________________
Kuwait Data Recovery - UNIX GTC
The only reason for time is so that everything doesn't happen at once. By: Albert Einstein

Quick for you guys:

Suppose someone replaced the "native usb3 pcb" with another and he wrote native rom to it

Anyone knows how to tell if this pcb is for that drive? (in case if both pcbs have the same native ROM)

_________________
Kuwait Data Recovery - UNIX GTC
The only reason for time is so that everything doesn't happen at once. By: Albert Einstein

Check the date codes on the ICs and compare with label. That's just one way.

_________________
A backup a day keeps DR away.

What if the MCU cannot be powered up, such as when the motor controller is burnt?

_________________
A backup a day keeps DR away.

Attached is sample drive with pcb, which date codes you are Ref. to?

_________________
Kuwait Data Recovery - UNIX GTC
The only reason for time is so that everything doesn't happen at once. By: Albert Einstein