after After replacing the board WD3200AAKS-75L9A0,flashed with wrong fw version(from tornado 2d).
How do I restore the original firmware (192kb) which I have (pinaclelite),with WDR, or some tips with jumpers...
Thanks

Before we sit down to analyse, please say which version of wdr has been used and what is hdd's module u have flashed.

I have version 3.0. Wrong firmware (flashed)=WD3200AAKS-00VYA0_12.01B02 (587S.bin), need to reflash with WD3200AAKS-75L9A0 (01CS.bin),The first thing I want to know,can I rewrite the firmware with a setting Jumer or through the serial port, there are probably serial pins as Samsung or Seagate,
Thanks

Have u tried reflashing with wdr + WD3200AAKS-75L9A0. wdr needs no jumper or serial port like sasung or seagate.

yes, and interesting, always is the same: "Erase Flash - FFFF=NOT_AN_ERR_VSC_CMD_EXEC_IN_BKG" folowing with: "Write Flash - FFFF=NOT_AN_ERR_VSC_CMD_EXEC_IN_BKG", but nothing happens with rom in backgroud "IN BKG"

Wrong. Jumpers have to be set in order to start the drive in safe mode.

Thanx bgman for the information.

What i know is win WDR5.3 no jumper setting is necessary. Will u please clarify for knowledge sake.

To flash a new ROM to a drive you need the drive to be in "safe" mode.
The easiest way to set a drive in safe mode is by using jumpers.

Not entirely correct.

With WDR you can flash the ROM to a WD drive even on "normal" mode. I have done this several times and it work.

I don't know if you can flash ROM in normal mode if you have a WRONG version of ROM on it, causing some incompatibility with SA code (mod 11).

On the mentioned case the OP is getting WDR errors while writting to ROM. So it's not writting at all.

OP could indeed try safe mode by setting jumpers or by insulating contacts.

But if ROM code can't be re-written by WDR OP will have to use external programmer and do like this :

http://malthus.zapto.org/viewtopic.php?f=117&t=865

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

Translates to :

FFFF Not an error. Vendor Specific Command Executing in the background.

Are you sure that it didn't work ? Maybe the problem is NOT ROM related.
Try to read rom again and compare with the one you are trying to write.


(of course this is an old thread and most likely the op already sorted out the problem).

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

WDR 5.3 uses exactly the same code as 3.0, etc to write ROM.
It's the same.
No safe mode needed unless SA modules are making the drive bsy or there are incomaptibility on SA modules with ROM, etc ....

Of course if ROM is damaged you can't flash it with WDR.

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

Write ROM by serial port :

If you have broken/damaged ROM in a way that you can't write it by VSC (the pcb is dead because of ROM with bad checksum) you can use a full version of U-Tool to write back the ROM by serial port (x-modem) using a TTL adaptor (like the one for seagate drives)

http://malthus.zapto.org/viewtopic.php?f=22&t=217

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