einstein9 wrote:
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)
:!:
It looks like nobody wants to play your game.
I'm guessing that simply trying each PCB to see which one starts the drive and decrypts the data is not an acceptable solution? Obviously I don't have any experience in this area, but I'll start by identifying security-related objects.
There are these 3 ROM resident ROYL adaptive modules:
Code:
1A2 : SED KEY
1B6 : Digital signature
1B0 : Digital Signature
The ROM boot block is digitally signed at the end of the block.
One of the ROM's PCMBlocks is a compressed 0xDDDD ROYL module. I have attached an example from a SpyGlass3. If I understand correctly, 0xDDDD is required for initialising the drive's crypto-engine.
I expect that the digital signatures may have no relationship to the MCU key. One way to find out would be to compare two drives that have identical firmware and check whether their identical boot blocks have the same signature.
Another test would be to install a donor PCB with identical firmware on a patient HDA, after transferring the ROM adaptives one by one.
Another test might be to execute an ATA 90h Execute Drive Diagnostic command and observe any error code.
FAQ
Search
Login
Register
HDDGURU FILES
