WD Elements - how to get ROM and modules?

[AdasRip]

I have patients WD5000LMVW.

The hdd starts and reports via USB, but there is a problem with reading some of the surface.

I am trying to convert USB to SATA PCBs.
For this purpose, I tried to download the ROM and modules using WD Marvell USB utility.
Unfortunately, the hdd is not recognized and I receive a message "HDD's RAM reading error, unexpected error: Undefined SCSI error ASC: 0x00; SCQ: 0x1D".
Manual selection of the Hubble LT family also does not help.

I also tried to read by COM terminal. Then it's better.
The utility start up and I download the ROM without any problem.
Then I download the modules and unfortunately 47h and 30h are impossible to download.

What's the problem?

[DataMedics]

If you were able to read the full ROM via COM don't worry about the modules. Just write the ROM to a proper SATA board.

[AdasRip]

I've copied only ROM to the SATA PCB and the disk starts, it reaches RDY but there is no ID.

In the past, I have always been copying modules so that the new PCB will work properly.

In this case, I also tried to get these modules from SA but it is not accessible.

[northwind]

As said, the ROM contains the ROM modules.
So if your drive is spinning up and does not ID, it's something different.
You're sure you didn't click the Block SA option when you wrote the ROM to SATA PCB? That would cause your drive to get ready with no ID.
What happens when you upload dir and LDR to RAM?

[Maxim_TS]

Source of the post I've copied only ROM to the SATA PCB and the disk starts, it reaches RDY but there is no ID.

maybe the drive is locked somehow. Block module 02 access in Work with ROM, and restart the HDD. If heads are good, you'll see default XYZ ID and SA access.

[AdasRip]

... You're sure you didn't click the Block SA option when you wrote the ROM to SATA PCB? That would cause your drive to get ready with no ID.
What happens when you upload dir and LDR to RAM?

I'm sure I did not deliberately block SA. I didn't try fo upload LDR to RAM.

Source of the post maybe the drive is locked somehow. Block module 02 access in Work with ROM, and restart the HDD. If heads are good, you'll see default XYZ ID and SA access.

The disk normally reports on USB, so I do not think anyone blocks it.
Behavior during its operation in USB mode indicates that 1 head may be damaged.

[Maxim_TS]

Source of the post The disk normally reports on USB, so I do not think anyone blocks it.

USB bridge unlocks the drive. Via SATA it may be still locked.