I think that we are making it harder then it should be.
I can see two problems with our procedure.
1 - ROM on your donor PCB might be completly diferent from initial one (not just adaptives) and somehow incompatible with the SA code making it impossible to gain access to SA with that PCB.
Can you upload a photo of the donor PCB and the original PCB somewhere and post here ?
2 - PCB have EXTERNAL ROM CHIP, corret ? If so there are BIG CHANCES that there is NO COPY with valid data of ROM MODULES on SA and if there is a copy they will only be a "template" file without valid/correct data.
Normally only on drives without ROM chip (ROM embeded on MCU) you will get the valid data from the SA modules 102, 103, 105, 107 and 109 to generate the new ROM.
Please read this AceLab PC-3000 article :http://blog.acelaboratory.com/pc-3000-f ... l-rom.html
The procedure allows to recover full image of original ROM and all ROM modules.
The procedure is applicable to almost all WD Marvell architecture drives with internal (integrated into processor) ROM, that has SA modules 102, 103, 105, 107 and 109. Some firmwares has SA module 109 that doesn’t contain necessary data – ROM image. If we open such 109 module in HEX-editor we’ll see that it is filled with zeroes. In such cases the utility can’t built the image and gives error.
This procedure is not applicable to drives with external ROM IC (U12) as well as to classical WD Caviar architecture drives(non-Marvell).
With that in mind and if you don't want to move the ROM chips from one PCB to the other i would :
1 - MAKE SURE that the donnor PCB is in working conditions and it's compatible with the original PCB. Also if the original PCB have a ROM chip the donor PCB must have a ROM chip as well, because if you move the ROM from your original PCB to the donor one and the donor doesn't have ROM then it will still read it's native ROM embeded on the MCU and not the ROM from the rom chip unless you mess up with some resistors on the PCB .... Or unlessyou write the ROM content to the embeded MCU ROM space and you can't do that as you can't read ROM on the damaged PCB.
2 - Move the ROM chip or use external programmer + SOIC 8 clip to write ROM :http://www.hddoracle.com/viewtopic.php?f=117&t=865
Hope this helps you out !
_________________The HDD Oracle
- Platform for OPEN research on Data Recovery.