Hello,
Some week ago I decided to update firmware on all my hard disks. I downloaded corresponding versions from Seagate KB website and applied them with bootable cds.
The only drive not updated was my ST3500418AS CC34 (model matched, firmware not matched) so I decided to update it forcibly to CC3E (and stupidly) using the FLD487... command prompt provided with the fw upgrade .ISO image. There were 3 .LOD image files (different files for different drive geometries and other) so I stuplidly tried one randomly. Flash has been applied correctly but after reboot drive cannot be seen by BIOS and unusable.
I got a spare PCB with same series and with CC34 on it, it can be seen by BIOS but on boot there is a S.M.A.R.T. status=BAD and drive is not visible under Windows OS.
I discovered that firmware goes on the PCB but a small part goes on the drive SA, so my CC34 PCB is not enough to make the drive working.
With a spare PCB and drive recognizeable by BIOS my HDD is still flashable (using FLD487... tool) but now I don't want to make some more mistakes. I'd need a CC34 firmware file so I can try the last chance.

Do you think it can be done following this way or it must be sent to a pro?

Thanks for your patience..

FYI, the correct firmware image for your drive is PHCC3E2H.LOD (2H = 2 heads).

You can also see it in the configuration file:
http://www.users.on.net/~fzabkar/HDD/PH-CC3E.TXT

BTW, you have it round the wrong way. That is, most, if not all of the firmware is written to a firmware zone on the platters. Very little, if any (?), is written to flash memory.

I suspect that your replacement board is not allowing the MCU to see the platters (because of mismatched "adaptive" information).

_________________
A backup a day keeps DR away.

Se quello che e' andato a finire sul disco (non la parte in ROM) ci e' finito davvero, e' un bel casino. E' molto improbabile che tu possa farlo "rivivere" IN MANIERA SICURA e far funzionare correttamente e stabilmente senza tutti gli strumenti che utilizziamo per la diagnosi profesisonale e piu' ci provi piu' e' possibile che fai altro danno. Inoltre in ROM ci sono alcune cose strettamente legate al TUO drive per cui se per qualsiasi motivo fai fuori anche quelle, e' ancora piu' complicato. A parte quello che e' stato fisicamente distrutto , nel recupero dati nulla e' impossibile, basta pagare
Curiosita', da dove e' arrivata l'idea di forzare un aggiornamento e dato che normalmente sarebbe bloccato sul nascere un aggiornamento forzato, chi ti ha dato l'idea ?

If the platter-resident part (not the ROM) has effectively reached the disk, it's a big mess. It's very unlike that you can make it SAFELY run stable and again without the pro gear that we use on professional diagnose, and the more you try the more potentially damage. Moreover, there is unique drive-dependent data on ROM - in case of damage it becomes even more complicated. Beside what has been physically destroyed, on data recovery nothing is impossible , it's just a matter of $$$. Out of curiosity, where did the idea of a forced update came from , and as a forceful update should have been blocked (NORMALLY !) , where exactly did the idea came from ?

I know I'd need pro service with pro gear but I also need the tons of money I don't have. That's why I'm trying to figure out about possible DIY methods before planning to send it to a pro.
About the idea of forcing... now the damage is done!

Thanks. I'm thinking to FORCE CC3E update (now with the right file) on a CC34 reprogrammed PCB.
Now I have to find PHCC3E2H.LOD file (Seagate removed it due to further updates). If anyone has it...
I suppose this is the only way before sending the unit to a pro.

E' un mito che il costo sia sempre elevato. Certo non te la cavi con 50 euro, ma se e' un problema di solo firmware e a patto di trovare dei compromessi circa i dati (le ragioni sono complesse e non posso spiegartele ne' qui in pubblico ne' in privato) i costi sono sempre molto ma molto meno rispetto a un intervento fisico.
A questo punto, spannometricamente, non c'e' nessuna possibilita' di soluzioni fai da te SICURE a parte soluzioni alla Wile E. Coyote.
Se vuoi fare da solo sei solo con te stesso, se ti va bene sarai felice, se piangerai piangerai da solo. Piu' che augurarti buona fortuna non si puo'.
Personalmente ho il sospetto che le informazioni che ti hanno portato a fare il danno le abbia prese da Internet , ecco perche' chiedevo da DOVE ESATTAMENTE hai preso i riferimenti giusto perche' cosi' metti in guardia eventuali altri utenti dal rifare lo stesso errore.
Se poi e' stata tutta una tua iniziativa.... consideralo un tentativo andato male di smanettare con aggeggi maligni come gli HDD.

The high cost of pro DR is a myth. Of course it is not a 50 EUR work, but when it is only a FW problem and eventually accepting some compromises about data (I cannot explain it neither in public nor in private) the cost is always a fraction / lower in comparison of physical recovery.
At this point there are almost no SAFE DIY options except WIle E. Coyote-ish ideas/solutions.
If you want to DIY you are alone with yourself : if it goes fine, you'll be happy otherwise you'll cry alone. The best I can do is to wish you GOOD LUCK.
Personally I suspected that the idea and how to do was taken from the internet, so posting EXACTLY where the idea and explanations came from should have been useful to warn other users about the potential damage they can face.
If it was you taking the initiative by yourself only.... consider it a badly ended tinkering attempt with malicious devices like HDDs are.

It was my idea. I documented it fully and it works flawlessly. The OP has confessed that he picked a firmware image at random, in which case he had only 1 chance in 3 of success. In retrospect, I'm sure Puppetnation regrets not posting to that thread. Unlike the "pros", I would have been only too pleased to respond to any requests for DIY assistance. So, sorry, but there's no intimidation opportunity for you there.

In fact here is one thread:
http://forums.seagate.com/t5/Barracuda- ... td-p/52066

I wrote ...

FDL486A -m Pharaoh -f PHCC3E2H.LOD -i ST3500418AS -s -x -b -v -a 20

... which is the correct procedure.

_________________
A backup a day keeps DR away.

Here is the 7200.12 CC3E update:
http://www.seagate.com/staticfiles/supp ... L-CC3E.exe

I strongly urge you not to apply it, though. I'm not a DR guy, but I would think that using a different PCB with different adaptives would mean that your firmware update would be written to the wrong area on the platters, assuming it could be applied at all. If so, then you'll only make things much worse. But that's only speculation on my part.

Anyway, assuming you don't receive a satisfactory response in this thread, I suggest you ask raptor_pa for his professional opinion at http://www.techsupportforum.com/hardwar ... ve-support.

_________________
A backup a day keeps DR away.

I'd use the SAME original PCB: a canadian guy is able to flash firmware on it again.

My distraction...

Mia iniziativa di smanettare in cose che non conosco bene e di averci messo poca attenzione... e ne pago le spese..
Sarà meglio che cominci ad informarmi per il recupero....

My decision on tweaking stuff I'm not skilled about and due to my lack of attention... now I'm paying the dues...
Now it's time to look for a DR service....

Thanks

Now I'm waiting for my bricked PCB to be re-programmed with CC34 firmware: this will make it re-flashable.
Now I'll be careful selecting the right LOD file, I hope this would be enough to access my hdd again.

Will let you know.
'til now... thanks to everyone!