Palmer with ROM module errors

[fixdata]

Hello

I have a Western Digital Palmer model WD10SPZX-60ZT1T0 with possible firmware failure.
The original ROM has already been changed to an unlocked PCB.

When reading the ROM modules, I get an error in modules 0A, 47, 1A2, 1B6.
I have a donor disk with the same firmware version.
If I write the donor modules on the PCB with the original ROM, is it possible to fix the error?

Thanks for your help.

[DataMedics]

Does the donor give the same errors when you read it's ROM modules? It wouldn't surprise me if the utility just doesn't properly recognize the modules of the ROM and is miscalculating the checksum. These are still really new.

And NO, you don't want donor modules in your ROM. Those modules are the parts of the code that is unique to your specific drive. If anything, you'd be doing the opposite and injecting patient modules into a donor ROM.

[fixdata]

Hi, thanks for your help.

By placing the unlocked PCB with the original donor ROM, I can save all the fimrware with no problems.

It has happened to me in the USB disks of the families: FBLite, Shrek and Sherk LT, it is not possible to read the 4F module of the ROM, so these cases the 4F module of a donor is recorded (on a SATA PCB along with the others modules and patient ROM) and this solves the problem.

Any suggestion?

Thank you

[d_d_recovery]

It looks like the ROM might have corrupted when copying. Especially if it has happened to you before. You might want to check with a different reader.

[AJ2008]

you can see ROM version. Write donor ROM of same version. Modules 0B, 20B read so check this for directory address and ammend to donor ROM if needed.

Otherwise, if SA reads then restore from SA.

[AJ2008]

Source of the post It looks like the ROM might have corrupted when copying. Especially if it has happened to you before. You might want to check with a different reader.

My guess is ROM programmer was used that was not configured correct or does not properly support chip

[AJ2008]

Source of the post Does the donor give the same errors when you read it's ROM modules? It wouldn't surprise me if the utility just doesn't properly recognize the modules of the ROM and is miscalculating the checksum. These are still really new.

And NO, you don't want donor modules in your ROM. Those modules are the parts of the code that is unique to your specific drive. If anything, you'd be doing the opposite and injecting patient modules into a donor ROM.

Only thing of importance on this is directory address and ROM version - if these match on complete donor ROM then HDD will operate fine

[300ddr]

Great to know Alyn, thanks for sharing!