First open the utility with correct port and "safe mode" and only then apply power to PCB (and not the other way around

_________________
1Q9xrDTzTddUXeJAFRn37aqh1Yr6buDCdw - (Bitcoin Donations)
paypal.me/Spildit - (PayPal Donations)
The HDD Oracle - Platform for OPEN research on Data Recovery.

Nope.
The old PCB is defective

_________________
1Q9xrDTzTddUXeJAFRn37aqh1Yr6buDCdw - (Bitcoin Donations)
paypal.me/Spildit - (PayPal Donations)
The HDD Oracle - Platform for OPEN research on Data Recovery.

New PCB with it's original ROM without drive won't work with WDR. I'm not able to read out the ROM without drive.

Did you start the WDR first ? You should first start WDR in safe mode and oly then aply power to PCb.

_________________
1Q9xrDTzTddUXeJAFRn37aqh1Yr6buDCdw - (Bitcoin Donations)
paypal.me/Spildit - (PayPal Donations)
The HDD Oracle - Platform for OPEN research on Data Recovery.

Ok, if that is the case we don't have any diference from good pcb / possible bad pcb ......

_________________
1Q9xrDTzTddUXeJAFRn37aqh1Yr6buDCdw - (Bitcoin Donations)
paypal.me/Spildit - (PayPal Donations)
The HDD Oracle - Platform for OPEN research on Data Recovery.

I could log SPI communication from new PCB to verify.

Don't know what to think anymore .....
On Louis case wd2000jd-problem-t20346.html he was able to read ROM even with a drive that wasn't reading SA from platters, yet you only can read ROM on the drive that is working correctly ....

_________________
1Q9xrDTzTddUXeJAFRn37aqh1Yr6buDCdw - (Bitcoin Donations)
paypal.me/Spildit - (PayPal Donations)
The HDD Oracle - Platform for OPEN research on Data Recovery.

Some news. I tried WDR-4.0 from louis an attached bad PCB to good drive without contact to head stack and was able to read out EEprom. Log and bin files in attachment.
Here is the log from good PCB and drive:

WDC WD5000AAKS-00V1A0 FW:05.01D05 SN:WD-WMAWF2172998 (ROYL selected) port 0xFE00
Logical: Cyls 16383, Heads 16, Sectors 63, LBA 976773168, 500Gb
Controller Buffer Size: 16384Kb
Family: Tahoe_PL (Royl)

ROM Rev: 11.58C
Mod 0D : 00010000 (01.00)
Mod 4F : 00110058 (11.58)
DIR Rev: 00020000 (02.00)
OVL Rev: 00110059 (11.59)

Is it possible to upgrade firmware in good PCB? Is the EEprom from defective PCB corrupted?
Because of logged spi-communication, I would rather say, EEProm is ok.

Can't follow you. so, tell us..you have the donor with which ROM soldered now?

You should have had a rom backup/compare before unsoldering the ROMs...and one after...in this way you could have found if the firmware data lies inside the rom or inside mcu.

Please post ROM and LOG for the Bad PCB . Yes, you can try to "Flash" ROM of Old/Damaged PCB back to the New PCB using the WDR AT RISK OF DAMAGING DONNOR PCB, but as you stated that you can have access to an external programmer, i think it's ok.

But the problem will be the same, assuming tha you soldered ok the ROM on the first time, i would say that flashin the old ROM on the NEW PCB will not change the fact that the NEW PCB will not make the new drive to spin. The problem should be related to Head Stack, and when connected to Head Stack the drive will not spin at all (some pre-amp short). But yes, it's worth the risk because at any rate you will need the new PCB with the old ROM if you are trying to get the data, and that way you don't have to re-solder the ROM chip .....

_________________
1Q9xrDTzTddUXeJAFRn37aqh1Yr6buDCdw - (Bitcoin Donations)
paypal.me/Spildit - (PayPal Donations)
The HDD Oracle - Platform for OPEN research on Data Recovery.

I've got:

- one defective HDD with almost defective PCB with it's own EEprom
- one working HDD with its own PCB and its own EEprom

Status quo:

- defective HDD spins up and you hear some clicking, then it spins down
- working PCB with old EEprom doesn't work on defective drive - it doesn't either spin up
- same with working PCB and its own EEprom
- defective drive spins up withworking PCB and its own EEptom, but without head stack connection
- WDR is able to read out EEprom on working PCB with its own EEprom
- WDR isn't able to read out EEprom on defective HDD with defective PCB
- WDR isn't able to read out EEprom on any PCB without connected drive
- WDR is able to read out EEprom on good drive with goot PCB without connected head stack
- WDR is able to read out EEprom on good drive with bad PCB without connected head stack

Differences:

- Some different assembly on these PCBs
- Obviously different firmware versions

Does anyone have a schematic from this PCB?
So, I will try to reprogram working PCB with old ROM-Image.

Hi,
I flashed the bin from old ROM into new ROM and mounted new PCB to old drive - I wont' spin up.
But new drive is still working with old ROM, obviously.
Maybe, I should move R48, R68, R71 and R51 from old PCB to new PCB an remove R10, C48 and R50 from new PCB (all components near pads to heat stack)?!

As I can see, the problem is in head(s) or preamp so you can do nothing with working on PCB ("flashing", removing or changing components...).

Please, learn how hard drives work.

Clicking sound in your case is because of the heads can not find servo. Possible reasons can be: damaged servo, bad heads, bad preamp, bad reading channel, bad ROM content etc. In any of those cases you can not do anything without tools, knowledge and experience. Sorry for saying but you have nothing of those.

By now i'm sure the problem is with shorted pre-amp inside the drive and damaged original pcb.
New drive worked with ROM of original damaged drive, so Rom should be fine.
Can you confirm if you can use the new drive correctly, write and read files from it, using ROM (FLASHED BY WDR) from damaged drive ? If so ROM of the 2 drives are compatible !!! Amazing ! Yet Rom is fine and problem is pre-amp on head stack and original pcb.
DONT SWAP PCB COMPONENTS. Drive should have worked with new pcb with old ROM , AND by the look of things drive would have worked with new pcb even without rom swap !

_________________
1Q9xrDTzTddUXeJAFRn37aqh1Yr6buDCdw - (Bitcoin Donations)
paypal.me/Spildit - (PayPal Donations)
The HDD Oracle - Platform for OPEN research on Data Recovery.

If New drive + New Pcb with flashed ROM of old/damage drive works fine, then obviously ROM is fine and the problem is shorted pre-amp on damage drive (inside the drive) + damaged original pcb. Time to take the drive to a recovery lab for head stack replacement on a class 100 clean room... We have done by now way more then normal DIY solutions would solve. And we learned new things. Time to be aware of our limitations and take the drive to someone with better tools !

_________________
1Q9xrDTzTddUXeJAFRn37aqh1Yr6buDCdw - (Bitcoin Donations)
paypal.me/Spildit - (PayPal Donations)
The HDD Oracle - Platform for OPEN research on Data Recovery.

I honestly think that your chance to swap heads will be almost near 0% success rate. You should consider that carefully and consult with the owner of the drive now. If you decide to do it yourself its crazy. I will still try to help in what i can, but its pretty much game over...

_________________
1Q9xrDTzTddUXeJAFRn37aqh1Yr6buDCdw - (Bitcoin Donations)
paypal.me/Spildit - (PayPal Donations)
The HDD Oracle - Platform for OPEN research on Data Recovery.

There is no possibility for this because the fw versions are not the same in both drives:

- Old one: 12000M
- New one: 110058

I also thiok that you are correct on that one, despite the fact that op stated that new drive works with new pcb and flashed old rom. Maybe he wanted to say that drive spins... At any rate would mean that problem is not with Rom. What do you think ?

_________________
1Q9xrDTzTddUXeJAFRn37aqh1Yr6buDCdw - (Bitcoin Donations)
paypal.me/Spildit - (PayPal Donations)
The HDD Oracle - Platform for OPEN research on Data Recovery.

Yes, I suppose he wanted to say that drive spins up and calibrates but for sure it cannot be identified in bios. Most of end users say "bios/computer detects (see) the drive" but that often doesn't mean it is fully recognized. Just like statements: "it works but clicks", "it's good but not working" etc.