I have A wd2000jd-22hbco, dcm: dsbhctjah, date: 06jul2005 SATA desktop drive that is suffering from firmware issues.
The modules that are bad are:

01: 0 : B : -2: 0: 638: 12:Yes :Error: Ok : 42 : : :Loaded part of microprogram code
01: 1 : B : -2: 1: 638: 12:Yes :Error: Ok : 42 : : :Loaded part of microprogram code
10: 0 : B : -2: 0: 658: 48:Yes :Error:Error: 89/AD : : :Loaded part of microprogram code
10: 1 : B : -2: 1: 658: 48:Yes :Error:Error: 89/AD : : :Loaded part of microprogram code
22: 0 : B : -2: 0: 714: 6:Yes :Error: Ok : 30 : : :Translator
22: 1 : B : -2: 1: 714: 6:Yes :Error: Ok : 30 : : :Translator
23: 0 : B : -2: 0: 723: 6:Yes :Error: Ok : F4 : : :Translator
23: 1 : B : -2: 1: 723: 6:Yes :Error: Ok : F4 : : :Translator
46: 0 : As : -2: 0: 730: 15:Yes :Error: Ok : A4 : : :Adaptive data
46: 1 : As : -2: 1: 730: 15:Yes :Error: Ok : A4 : : :Adaptive data
45: 0 : : -3: 0: 570: 15:Yes :Error: Ok : 46 : : :
45: 1 : : -3: 1: 570: 15:Yes :Error: Ok : 46 :
2F: 0 : B : -3: 0: 642: 8:Yes :Error: Ok : AA : : :S.M.A.R.T. Log (reserved)
2F: 1 : B : -3: 1: 642: 8:Yes :Error: Ok : AA : : :S.M.A.R.T. Log (reserved)
30: 0 : : -3: 0: 98: 12:Yes :Error: Ok : 2E : : :
30: 1 : : -3: 1: 98: 12:Yes :Error: Ok : 2E
38: 0 : : -3: 0: 71: 6:Yes :Error: Ok : B2 : : :
38: 1 : : -3: 1: 71: 6:Yes :Error: Ok : B2
3C: 0 : : -2: 0: 541: 6:Yes :Error: Ok : 8A : : :
3C: 1 : : -2: 1: 541: 6:Yes :Error: Ok : 8A

I tried writing them over with using modules from a drive of the same family and the same firmware version 08.02d08. The writing procedure completed successfully and when SA structure test was executed, all the module for fine. I tried to access data but was getting the busy light signal and abr and amn signal errors.

I even scanned the drive's sectors using MHDD. All the sectors were displaying the character "A" as in meaning ABRT.
I got this result from writing over all bad modules except for Module "46 As", which you can't overwrite from another drive. Then when I got the "A" character, I written over module 46. I scanned the drive again with MHDD, and now I am getting ABRT and UNC errors with MHDD.

What type of drive should I use as a donor and what modules should I concentrate on writing?

You overwrote the translator and adaptives. Offcourse you cannot read any data.
Try to regenerate the translator, but i'm afraid that without the proper adaptives, it will not be enough.
Did you try to backup the modules using composite reading ?
Without the correct adaptives, this could be a very difficult case.

Dobre

_________________
Murphy was an optimist

Datarecovery in Belgium, Holland, France and Germany
Datarecoverytools http://www.drtools.eu

Before I written over the translator and adaptives, I regenerated the translator. The translator is fine, but the other translators and the adaptive data were still bad. The translator modules had the B next to it meaning you can write them over using the same modules from a drive of the same family.

Before I did anything to the drive a backed up all the modules from both copies. All the modules were fine when I backed them up.

The drive was actually accessible. When data was being recovered, the os gave a write error. Then drive then struggled to mount. This is when I checked the modules. Those particular modules were bad.

I tried to write over the modules with the modules I previous backed up. Nothing was working. The only way I was able to fix the modules was to overwrite them using modules from a drive of the same family and same firmware version.

Do you think that because of the translator and adaptive data are bad and that the adaptive data can't be overwritten using modules from another drive, this drive cannot be repaired?

Well, the translator can always be regenerated, but the adaptives are more difficult.
If you backed them up before writing to the disk, check them with a hex editor and if they are ok then write them back to the drive. Then check if you can access the data again.

Dobre

_________________
Murphy was an optimist

Datarecovery in Belgium, Holland, France and Germany
Datarecoverytools http://www.drtools.eu

What Im I looking for in hexeditor to determine if the modules are bad and what do i compare them to?

Unfortunately, I wasn't able to repair the adaptives and the customer closed the case. For future references, I will try my best to study firmware module's physical structures in hexeditor to determine what is a working module and what is not, and then try to repair them within the editor.

Any suggestions greatly appreciated.

Yes, always learn, learn and leard


Dobre

_________________
Murphy was an optimist

Datarecovery in Belgium, Holland, France and Germany
Datarecoverytools http://www.drtools.eu