WD6400AAKS-00A7B0 firmware fail

[nikaragva]

Hi all,

I have problem with that hdd in the title. I already bring it to the date recoery service, but they can't find FW for that hdd.

Is there any posibility to find that firmware, maybe from someone personal hdd, to copy or something.

Sticker number on hdd back side is: 2061-701537-E00 07PD3

I was found one, almost all number are same, but only difference is 00A7B0 => 75A7B0.

I found on the internet Repair Station, but I don't know if they can help me.
Wich software I can use to get firmware from a donor hdd, and put them on the my hdd?


Thanks!

[fzabkar]

My first suggestion is to find a different data recovery "service".

Otherwise here is your firmware:

http://www.datadonor.net/HD%20Western%2 ... 00A7B0.rar

http://www.datadonor.net/HD%20Western%2 ... 75A7B0.rar

As for retrieving firmware modules and ROM data from a donor HDD, see the MHDD scripts here:
http://yura.projektas.lt/files/wd/mhdd/index.html

Your drive is a ROYL, and you will need MHDD ver 4.5.

[irs]

hi
i think you can contact user helpdisc on this forum, he's in Beograd and is a respected professional.
Bye
Luca

[nikaragva]

Thanks all for information.

@irs
HDD is already in service, but if they do not fix it, I will contact helpdisc.

@fzabkar
Thanks for that files!
I will bring that to service to see if that can help them to retrieve data.

[drc]

That is most likely not "your" firmware. Hopefully the data recovery service you are dealing with understands the difference. IMO fzabkar's post was extremely irresponsible.

[fzabkar]

@fzabkar
Thanks for that files!
I will bring that to service to see if that can help them to retrieve data.

Your DR shop needs to confirm that the firmware version of your drive matches the downloaded modules. If they are not a match, then let us know and someone will hopefully be able to help you. In any case at least you now know what they are looking for.

BTW, my post was illuminating, not irresponsible. The MHDD scripts that I linked to will read the modules, not write them. So you should be safe. If your DR shop needs a particular module, then the script can be modified to retrieve it. Of course this begs the question, why is the DR shop asking you to do their work for them?

[drc]

why is the DR shop asking you to do their work for them?

I agree

BTW, my post was illuminating, not irresponsible. The MHDD scripts that I linked to will read the modules, not write them. So you should be safe.

I disagree. Obviously OP and many (most?) other people posting here for the first time have the wrong idea about how HD firmware works.

Will you take responsibility when someone who doesn't understand takes the files you have provided (with a helpful "here is your firmware") which are most likely not even the same version, incorrectly writes them to their drive using information you (or someone else with only half of the understanding) have found elsewhere on the internet and then repeated without important or necessary warnings, and renders their data completely destroyed beyond any hope of anyone to retrieve?

[nikaragva]

They do not asking me to do they work. I just want to help somehow.
HDD is in the DR service for a about two weeks, and they try with all fw in their firmware database and do ~90% of job. But still missing something.
And I can't understand why is so hard to find identical firmware. My disc is probably produced in thousands and thousands of copies ...

I was "broke" in the same time two discs WD320 and WD640. But only WD640 contain important information - family photos - and that is why I can't afford more expensive DR service for retrieving data. That is not wiki leaks information's important for states, just regular photos

What is cause for that failure? Electric shock, bad electricity, ...? All other hardware work perfect after that.

[BlackST]

why is the DR shop asking you to do their work for them?

I agree

BTW, my post was illuminating, not irresponsible. The MHDD scripts that I linked to will read the modules, not write them. So you should be safe.

I disagree. Obviously OP and many (most?) other people posting here for the first time have the wrong idea about how HD firmware works.

Will you take responsibility when someone who doesn't understand takes the files you have provided (with a helpful "here is your firmware") which are most likely not even the same version, incorrectly writes them to their drive using information you (or someone else with only half of the understanding) have found elsewhere on the internet and then repeated without important or necessary warnings, and renders their data completely destroyed beyond any hope of anyone to retrieve?

This is an old problem....

In any case the files are useless without "A" tool and in this case most probably are useless at all, otherwise the problem would have been pointed out differently.
The story about MHDD and scripts is identical on other thread. Unfortunately, in this very case it doesn't work either. Guess why ?

They do not asking me to do they work. I just want to help somehow.
HDD is in the DR service for a about two weeks, and they try with all fw in their firmware database and do ~90% of job. But still missing something.
And I can't understand why is so hard to find identical firmware. My disc is probably produced in thousands and thousands of copies ...

Because they probably didn't find the exact problem or they don't know exactly how to handle it.
OR the problem is elsewhere, OR they have limited resources, OR they don't know how to handle the problem itself so they're going on with trial-and-error scheme. Just guessing.

[fzabkar]

They do not asking me to do they work. I just want to help somehow.
HDD is in the DR service for a about two weeks, and they try with all fw in their firmware database and do ~90% of job. But still missing something.

FYI, the firmware is stored in a "System Area" on the platters. It is divided into modules (MOD) that perform a specific function. There are two copies of each module (see the RAR archives). Sometimes these modules become unreadable. A standard check involves reading each module and computing a checksum over its contents. AFAICT, this checksum should be zero, and is calculated by summing the module's 32-bit words in little endian format.

A typical repair involves identifying the bad module and rewriting it with a compatible one. This procedure requires Vendor Specific ATA Commands (VSC) which are not publicly documented.

Some freeware exists to verify the integrity of the MODs in certain WD models:
http://nazyura.newmail.ru/000006.htm

Two of the less expensive professional tools are Salvation Data's HD Doctor for WD (~US$600) and WDR-UDMA (~US$200).

[nikaragva]

If anyone knows something about AFF Repair Station?
They say they can fix firmware for (one licence) disc for 49.95$, that is not too much money.
Whether someone may have used their services?

[fzabkar]

It appears that a remote diagnosis is free. Let us know what the software tells you. If AFF Repair Station does what it claims, then a great many people could benefit from it. In fact I'm kicking myself for not having noticed this before.

[nikaragva]

This is response from aaf repair station for my hdd. Firmware is still broken.

http://www.dodaj.rs/f/37/eX/46arBaHY/aaf.png

[nikaragva]

HDD is successfully repaired HelpDisc.
Problem was in hdd head, not in FW.

o/