[Unlocking terminal of Seagate ES.2 in BSY/LED:000000CC state]

You've ruined your drive in your haste to fix it...

On what grounds do you base this conclusion?...

Cant get this...The drive was working well before pcb swap...

As I wrote, both pcb boards ought to be compatible with each drive with a rom swap...

Even AceLab discuss this possibility...

Appendix 1. Replacement of the controller board

ATTENTION! ROM of the drives (ROM label is 25FW406A) contains adaptive information. Therefore, during

replacement of the controller board you have to move the ROM data from the damaged board to the donor one (resolder

the ROM chip from the damaged board to the borrowed one). Please see Figure 19.

Please keep in mind that if you need to restore a drive using a non-native controller board, the drive at the start

will be unable to access the firmware data on disk surface. That behaviour can be erroneously recognized as a problem

with the heads or reading channel, so please check carefully to ensure that the controller board matches the HDA. To do

that, you can even use a board disconnected from HDA, which returns HDD ID information via the ATA interface

anyway. Having read HDD ID, you can compare the model and its serial number to the information printed on HDA

label1.

[The Solution for Seagate 7200.11 HDDs]

Not much about Barracuda ES2 drives here...

Anything ES2 is NOT on the present thread, but here:

jaclaz

Moved my q over to ther other thread...

[Unlocking terminal of Seagate ES.2 in BSY/LED:000000CC state]

Hey..

...

My issue....

I have this ST31000340NS ES2 drive who was working well until as a test I did a pcb board and rom chip swap and tested it on an ST3750330NS ES2 drive, both have identical board no, but different revision, but ought to be compatible as long as I do the rom chip swap...

After this test ST31000340NS drive spins up clicks 11 times spins down..My humble hope, maybe its been stuck in busy state, not ruined by this silly swap attempt..

It show up after a while when pc initialize, but not detected by BIOS, and off course neither by Windows, SeaTools etc..

ES2 disks has as you sure know terminal lock so I cant enter any commands after hitting CTRL+Z and getting F3 T> prompt without unlocking terminal...

I've been shorting read channels, lifting board from HDA contacts as soon as I get F3 T> promp for days and hours,.but F3 T> will stand forever when I do this, but as soon as I go on and hit the command 2 + enter this "FlashLED - Failure Code 000000CC Failure Adress 0025c8af" pops up over 2 lines in Hyperterminal, and repeats itself every 60 second or so..

I'm stuck, and hopefully someone can give some advice..

[The Solution for Seagate 7200.11 HDDs]

Hey..

Have been reading this thread all the way up to page 100, had to let it rest now and ask for help...

Not much about Barracuda ES2 drives here...

My issue....

I have this ST31000340NS ES2 drive who was working well until as a test I did a pcb board and rom chip swap and tested it on an ST3750330NS ES2 drive, both have identical board no, but different revision, but ought to be compatible as long as I do the rom chip swap...

After this test ST31000340NS drive spins up clicks 11 times spins down..My humble hope, maybe its been stuck in busy state, not ruined by this silly swap attempt..

It show up after a while when pc initialize, but not detected by BIOS, and off course neither by Windows, SeaTools etc..

ES2 disks has as you sure know terminal lock so I cant enter any commands after hitting CTRL+Z and getting F3 T> prompt without unlocking terminal...

I've been shorting read channels, lifting board from HDA contacts as soon as I get F3 T> promp for days and hours,.but F3 T> will stand forever when I do this, but as soon as I go on and hit the command 2 + enter this "FlashLED - Failure Code 000000CC Failure Adress 0025c8af" pops up over 2 lines in Hyperterminal, and repeats itself every 60 second or so..

I'm stuck, and hopefully someone can give some advice..