WD palmer damaged rom file data recovery

[tarasheh]

Hi,
Modules 129 and 130 are not described in DIR.
These modules are described in ATA Ovl.
These modules can be read by ID.
Ctrl + Alt + 3 -> see photo.
To read these modules, ATA Ovl must be loaded into the memory.

With such limited knowledge, the easiest way is to find a drive with a very similar production date and get the ROM from it.

Thanks sorry i forgot i can do that . most of the time i full backup of all module in wd palmer

I upload those module 0x109 and 0x209 if still you need. thanks fzabkar for your help it's so importent for me

Attachments

module.zip

(330.49 KiB) Downloaded 7 times

[tarasheh]

sorry for this reply i forgot upload module 130

Attachments

130.zip

(4.47 KiB) Downloaded 10 times

[fzabkar]

I have regenerated your ROM. Module 0x130 produces an identical ROM.

Attachments

ROM_109_129.7z

(323.73 KiB) Downloaded 11 times

[fzabkar]

Are the supplied modules from the donor drive or the patient?

[tarasheh]

Thanks for rom. I couldn't test it I will test it and i will report the result

Are the supplied modules from the donor drive or the patient?

modules are from the donor drive. It's not from the drive I want to recover.
Should I put that ROM chip on the drive I want to recover?

[fzabkar]

You need the modules from the patient. Find some way to access the patient's SA using donor ROMs.

[tarasheh]

You need the modules from the patient. Find some way to access the patient's SA using donor ROMs.

HDD spin but no model and serial show up capacity is 0MB
I can't get any module because module directory is empty even i try to read module manually and i get this error "VSC ERR UNSUP ACTION CODE"

[Mikippp]

Hi,
What is the drive's production date (date designation on the label)?
Load a ROM-compatible loader into the memory and read modules 90 and 129/130 by ID.

Mikippp

[tarasheh]

Hi,
What is the drive's production date (date designation on the label)?
Load a ROM-compatible loader into the memory and read modules 90 and 129/130 by ID.

Mikippp

Hi, drive's production date is 27 JAN 2018

I try upload dir into hdd ram and i get this error: VSC ERR INV FUNC CODE REQ

today i search in pc-3000 and found option call Rom build from SA data and i never try that is it useful for this problem?

[Mikippp]

Hi,
I told you to load the Loader into memory, not the DIR – please read carefully what I'm writing.
Tests -> Service information -> Work with RAM -> LDR file loading
Load the files in the following order: 1B, 10, 11.
To work with the SA, you must use an unlocked ROM or an unlocked PCB.
You have a PC-3K and you haven't even read the manual for your WD Marvell drives.

Mikippp

[tarasheh]

Hi,
I told you to load the Loader into memory, not the DIR – please read carefully what I'm writing.
Tests -> Service information -> Work with RAM -> LDR file loading
Load the files in the following order: 1B, 10, 11.
To work with the SA, you must use an unlocked ROM or an unlocked PCB.
You have a PC-3K and you haven't even read the manual for your WD Marvell drives.

Mikippp

Hi, sorry I answer to late, I did everything you say but I don't have any compatible module or rom for this drive I only have one HDD similar to this and I uploaded it's rom and all modules here and i even try that upload that donor drive module 1B, 10, 11 to memory again not work. I unlocked sed of rom fzabkar uplosd here before try anything.

Hhd gru had one zip file with models looks like my drive and I try that again not work

[Mikippp]

i even try that upload that donor drive module 1B, 10, 11 to memory again not work.

Hi,
What's not working?
This can't not work.
Describe exactly what you're doing.
PS: Have you read the PC-3K manual for WD Marvell drives?

Mikippp

[Swiftdata]

Z10T is not mcu encrypted so donor ROM if same version may work assuming directory address is the same and version can be known (maybe is some part of original ROM is intact enough to read)
IF PC3000 was able to unlock ROM then must be some correct info inside it and not all corrupt
Better option is follow Mikippp advice and with donor ROM and loader in RAM read module 0x129 by SA to extract native modules, then use ROM rebuild from SA option, select ROM as source (not SA) then load extracted mods from 0x129
If LDR cannot load try some block mechanism in ROM like 0x411 or 0x30

[tarasheh]

Hi sorry i answer late too late i was looking other donor hard and i found one.

[quote="Mikippp"][/quote]

I backed up all the modules from the new donor hard drive, installed its ROM chip on the patient PCB, and uploaded the donor's LDR file into the patient drive's memory as you instructed. I then read modules 90, 129, and 130 from the menu opened with the shortcut Ctrl + Alt + 3.

Attachments

rom and modules.zip

(909.61 KiB) Downloaded 7 times

[tarasheh]

Z10T is not mcu encrypted so donor ROM if same version may work assuming directory address is the same and version can be known (maybe is some part of original ROM is intact enough to read)
IF PC3000 was able to unlock ROM then must be some correct info inside it and not all corrupt
Better option is follow Mikippp advice and with donor ROM and loader in RAM read module 0x129 by SA to extract native modules, then use ROM rebuild from SA option, select ROM as source (not SA) then load extracted mods from 0x129
If LDR cannot load try some block mechanism in ROM like 0x411 or 0x30

I tried to read and then build but i get can't read module 109

[Mikippp]

Hi,
Rebuilding the ROM on this drive must be divided into three stages.
What you've already done was stage 1.
Now you need to create a "hybrid" ROM –> ROM code from the donor ROM, and ROM modules from the patient's SA.
This can be done using PC-3K
-> Ctrl+Alt+4
-> Read from HDD ROM and selecting Code sections
-> Read from HDD SA and selecting ROM modules
-> then click Build ROM and save the ROM file.
This "hybrid" ROM file will allow you to read module 109 and build the patient's original ROM.

Mikippp

[tarasheh]

Hi Mikippp, Thank you that worked i get all info in pc-3k model, serial , capacity every thing is ok
But it has SED Locked and if i try to unlock that i get error " rom key data 5A not found " how can i fix that?

[tarasheh]

This the rom i build from pc-3k

Attachments

new rom genrated.zip

(653.87 KiB) Downloaded 9 times

[fzabkar]

I have generated a ROM from 0x109 in "New folder.zip" and 0x129 in "rom and modules.zip".

Attachments

rom.7z

(323.73 KiB) Downloaded 11 times

[tarasheh]

Hi everyone, and thanks (especially to Mikippp for the guidance).
I got the drive working with the newly generated ROM. It seems to be functioning. I also tried a ROM,module from another donor drive, built a new ROM, and this is the one that finally works.

thanks fzabkar for rom if i get problem i try your rom