I would check if New HDD still works fine (copy files to it and read them).
WDR needs windows and works by SATA. USB doesn't support VSC.

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

Thanks for your help.
I was able to read out the flash from the new HDD with the bad soldered EEprom. But I wasn't able to read out the defective one.
Next, I would try to desolder the EEprom and read it out with a Galep, shouldn't I?
Should I try to mount new PCB with wrong EEprom on defective HDD? Should it spin up?

BTW: New HDD seems to work fine. I copied files to it and copied them back.

Let's think first :

here - wd2000jd-problem-t20346.html

Louis was able to read the ROM even on a damaged drive (drive that couldn't read firmware on platters), so even if your drive have head problems, and so the clik sound, you should have been able to read ROM from that board too.

Did you checked if "SAFE MODE" was enabled when you selected the port ?
Did the drive spin (the good one) when you started it to read ROM ?

Let's for now assume that something on MCU of original board is broken and you can't read ROM using software, or ROM itself is damaged.

I would try to dump the firmware of the original damaged board with external programmer, and compare with the ROM of new working PCB.

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

I'm starting to think that ROM might be damaged, and that would explain why drive doesn't spin on good PCB with the damage ROM .... But the strange is that drive spins with damaged ROM on damaged PCB (assuming ROM is damaged). Only way to be sure is to read it with external programer.

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

I think original board PCB ROM is damaged and so new PCB doesn't make the damage drive spin because MCU try to read contents of rom and fail (damage ROM).
I think original board MCU is damaged, or masked ROM or whatever, and PCB isn't even trying to load ROM and aborting the process, instead is just powering the spindle and cliking.
I would go for a damaged PCB and damaged ROM.
That would explain why when you swap ROM drive doesn't spin (MCU is good and figures out that ROM is bad and doesn't load firmware) and explains why drive spins with damaged ROM (PCB have more damage and it's not even checking rom, un-aware that it's damaged try to spin the drive) .....
Does it make any sense ?

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

Can you Dump the ROM to a file and post here ?
Thanks.

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

BlackST told :



Maybe it's a case of damage PCB and ROM at the same time !

But if so the problem will be to re-create adaptive for your ROM / Drive .... Meaning, somehow making the drive to work with the new/good PCB by re-creating the part of ROM that is specific to the drive and got lost if original rom is indeed damaged. Maybe Louis can assist further ....

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

New PCB with its original ROM on the bad drive should spin up. Try that and see what you get. Maybe you are lucky and the ROM are close to the original and .... you get the picture .. i tought you had tryed that already.

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

I attached the .bin-files from the new ROM (do you mean the EEprom?). The HDD is spinning all the time, still while reading out the EEprom. "SAFE MODE" was checked.
I'm able to use an external programmer to read out the EEprom on this weekend.
I changed new PCB with it's own ROM to defective HDD and it doesn't make any noise and doesn't spin up.

BTW: Primary failure was the power supply. The person told me, he saw some smoke out of the power supply. Then he shut it off and tried to reboot, but PC fails to boot while recognition of HDD.

Ok.
Try the following
Connect the damage PCB (pcb from the damaged drive) to the sata port and put power on it, but without the drive attached. Try to read ROM with WDR.

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

Ok .... lets think of power surge killing the PCB and the Pre-amp inside the drive ... if pre-amp is shorted, somehow it prevents the good PCB from spining the drive, but on damaged PCB it just spins .....

It doesn't make senseeeee ......

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

Ok, if the good PC with it's good ROM doesn't spin the bad drive, then IT HAVE TO be damaged at a pre-amp level, because at that point, while it is not spinning firmware can't be read.

So, if you place the pcb with incompatible rom, no matter what, the drive have to spin first, and only then will try to read firmware on the platters, up untill that point (spinning) PCB doens't know a thing about firmware on platters, and the only way to know is to start spinning the drive.

If you place a know good PCB on the damage drive and the drive doesn't spin at all, i guess it must be a short on the pre-amp inside head assembly.

The question is, why does the native pcb make the drive spin then .....

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

Let's see, you are saying that new PCB with New original ROM on bad drive doesn't make the drive spin ......
As a last test can you repeat that but putting plastic tape or card on the contacts of the pcb to the head stack ? Let the PCB do the contact with the spindle but prevent it from doing the contact with the head stack ..... It should spin now, if so you have a damaged original pcb + damaged original head stack (pre-amp chip).

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

I WOULDN'T put the damaged pcb on the new drive, it can kill the pre-amp on the new drive, but there is another thing that you can do.

Swap the ROM chips again, like you have done on the first place.
Then use WDR to read the new working drive with the ROM chip of the original failed drive !!!!! If it reads ok then you can confirm that ROM is ok without programer. DON'T put original pcb of the damage disk on the new disk, because it can damage the pre-amp on the new drive, but new pcb with ROM of the old one should be ok.

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

I put the old PCB without HDD into my PC and now, the PC was able to boot. Before, with HDD, the PC wasn't able to boot. Nevertheless, I wasn't able to read out EEprom.

Defective HDD with new PCB but without contact to head stack, spins HDD up. It sound like the old PCB, but without clicking. The HDD spins up, stops an tries to spin up, again. After that, it stops.

I thought of swapping old PCB to new HDD. But I thought it wouldn't be a great idea because it could break the new HDD.
I will change the EEproms another time.

So head stack is in short circuit or damage in a way that prevents the PCB from start to boot/spin Damage head stack, almost for sure. Power supply damaged the PCB and the pre-amp inside the drive, or so i think. Now if the contacts to Head Stack are made to a good pcb, it's shorted and PCB doesn't even spin. Maybe something on the other PCB is broken making the frive to spin even with damage head stack ?

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

Do you mean the new PCB from the new working HDD is defective?

If you swap the rom of your damaged drive to the new PCB you should be able to read it too.

At this point my conclusion is Shorted/Damaged pre-amp inside the drive and damaged original PCB.

I don't know about ROM. If ROM is OK (yet to be tested) you would need to swap it (old rom on new PCB) and then swap heads ...... and deal with aligment problem ..... so ..... i think it's game over anyhow. At least we learn something. And we got bad luck, because if head stack was ok (and the problem was only with PCB) by now you would have your data back ...

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

Thank you very much for your help. I will think about that tomorrow. For now, I have to finish.
But I logged SPI communication on old PCB. For watching it, you need Salea Software: http://www.saleae.com/downloads

Other simple thing to try - New PCB with it's original ROM - Plug it without the drive to WDR and try to read ROM. If you manage to do that (despite the fact that you can't do it with the other PCB) then PCB is 100% sure dead.

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