st500dm002-1bd142 hp73

[stfungayi]

Hello
I have a st500dm002-1bd142 sn/z3tw3xw7 that will not spin up with the original PCB. I tried another pcb from a working hdd and it spins but is detected as wrong size 4.GB and will not show my data...if I put the ROM on another good pcb then it will not spin also .So i figured that the ROM may be corrupted.
I have attached the ROM dump if anyone can help me find what is wrong with the code in the ROM.
The pcb is the original one and the rom is the original one.

Attachments

EN25F40_20181225_204243 - Copy.rar

st500dm002-1bd142 dead

(138.58 KiB) Downloaded 483 times

[digisupport]

Full terminal output from original drive / pcb would helt a lot more.

[E123]

Original ROM has corrupt BOOT_FW in copy 0. Try this.

Attachments

new_rom.zip

(215.04 KiB) Downloaded 448 times

[bcometa]

@E123 could you explain how you determined this error and fixed it? I imported the "bad" ROM into PC3K and verified parts of the ROM are corrupt (error message when trying to "Show Information"). But, even after importing CAP+RAP+SAP+IAP to a donor ROM, it was still corrupt. Perhaps moving the Head Adaptives to a donor ROM could work, but I think you did something else. Just curious.
Thanks,
Brian

[fzabkar]

@E123 could you explain how you determined this error ...

F3romExplorer :
http://www.hddoracle.com/viewtopic.php?f=22&t=2534

The first copy of the BOOT_FW segment (ID = 0x10) is located at 0x404D0 - 0x5F4CF.

Code:

Offset(h) 00       04       08       0C

00040000  D50D0000 D8040000 F0030000 400D0400  Õ...Ø...ð...@...
00040010  63736944 00003625 FFFFFFFF 20FFFFFF  csiD..6%ÿÿÿÿ ÿÿÿ
00040020  16380000 15400000 0E400200 10D00400  .8...@...@...Ð..
                                     ^^^^^^^^
00040030  00D0F401 00000000 00000000 407F0000  .Ðô.........@...\
          ^^^^^^^^

The second copy of the BOOT_FW segment (ID = 0x10) is located at 0x604D0 - 0x6F4CF.

Code:

Offset(h) 00       04       08       0C

00060000  D50D0000 D8040000 F0030000 400D0400  Õ...Ø...ð...@...
00060010  63736944 00003625 FFFFFFFF 20FFFFFF  csiD..6%ÿÿÿÿ ÿÿÿ
00060020  16380000 15400000 0E400200 10D00400  .8...@...@...Ð..
                                     ^^^^^^^^
00060030  00D0F401 00000000 00000000 407F0000  .Ðô.........@...
          ^^^^^^^^

Comparing these two segments reveals a difference in one bit.

[bcometa]

THANK YOU fzabkar! I managed to figure it out and repair the ROM.

[fzabkar]

THANK YOU fzabkar! I managed to figure it out and repair the ROM. :)

@E123 is the author of F3romExplorer. All credit should go to him.

[bcometa]

Thanks to E123! Very cool tool to have!

[stfungayi]

Thank you E123 for your expertise and fzabkar for explaining.The hdd is now spinning and detectable in bios.
Would it have been possible to repair the Rom file by copying a BOOT_FW segment from another working HDD if both segments are corrupt.

[fzabkar]

Would it have been possible to repair the Rom file by copying a BOOT_FW segment from another working HDD if both segments are corrupt.

Yes, but I would think that you would need to ensure that the code is compatible.