Problem with WD Marvel Demo

[tomset]

HDD is not ruined by a password.
He has a different protection.

What - it's hard to say without excavation FW.

[locarno]

So, we can't rescue this hdd ?

Only for trash ?

[tomset]

HDD send Vlad.
He will understand, will return to you HDD and tells you end everyone, how HDD it was protected.

[locarno]

@locarno, attached is an HDDHackr UNDO.BIN file which I have created from your resource dumps. I have changed only two data records in MOD 02, namely the model number (which had been filled with ASCII spaces) and the capacity. Since you will be using HDDHackr to restore your MODs rather than modifying them, the question of compatibility should not arise.

Please ensure that there is no other WD drive that could become the target for HDDHackr.

WARNING: The attached UNDO.BIN must NOT be applied to other drives, not even the same model or firmware version (01.01A01). Doing so will very likely brick the drive. That's because MOD 02 has an internal version number "00080000" which must match the original firmware.

UNDO.bin
http://www9.zippyshare.com/v/82473656/file.html

I started HDDhacker.exe. See HDD. When I started restore UNDO.bin i get this:

Can't write firmware to drive!
DRQ Error: 0x0816

[tomset]

HDDHackr - Bad software.
Often kills HDD.
because they do not take into account the FW version and revision.

[tomset]

FW modifications of WD have not just a lot , but very much

[locarno]

What tool I must use to flash mod02.bin ?

[tomset]

Try to play in MHDD command CONFIG

[Vlad]

mod02 is not in flash
You should prevent reading of locked firmware when drive startup
Then, you need to put the necessary modules into RAM of the drive
It will provide you read your locked SA
After that, it will be possible to analyze how the drive is locked

[tomset]

What tool I must use to flash mod02.bin ?

in any not
module uses himself HDD.
And slip him a stranger, often kills HDD.