Maxtor STM3500418AS dead after failed firmware update

[Uncle Scrooge]

Hello to everybody, I'm new in this forum and I hope to find some help.
Excuse me if my english is not perfect, I write from Italy.

I got a STM3500418AS drive with original firmware version CC34, I downloaded the firmware update from here:
http://seagate.custkb.com/seagate/crm/s ... NewLang=en

The firmware update utility detected my drive and said it was eligible for the update, I proceeded but after a few seconds a "beep" sound came out from the PC and everything was frozen. After waiting 30 mins I had to reboot the PC and realize that my drive was no more recognized by the MB.

Yes, I know I did not 1 but actually 2 stupid things: updating the firmware of a perfectly working drive and not backing up my data before doing it. It's all my fault, but now I'm looking for the cheapest way to recover my data.

As a first attempt, I connected the PCB to a serial-to-TTL interface and I used Windows XP hyper terminal, trying to fix the drive using the procedure for the Barracuda 7200.11 in BSY state. My drive is the 7200.12 serie and so it didn't work. The PCB just responded with error messages.

I contacted some data recovery labs here in Italy, and they are asking for about 300 euros for "reconstructing" my firmware on the drive. Before spending that much money, I'm writing here wondering if you can suggest me something cheaper.

Do you think I can have any chance of success just swapping the PCB with a new one that is exactly the same model, with the same board number, main controller IC and motor combo IC?

Any other idea?
Thank you in advance

[drc]

I contacted some data recovery labs here in Italy, and they are asking for about 300 euros for "reconstructing" my firmware on the drive. Before spending that much money, I'm writing here wondering if you can suggest me something cheaper.

Do you think I can have any chance of success just swapping the PCB with a new one that is exactly the same model, with the same board number, main controller IC and motor combo IC?

No, and honestly, 300eur is a pretty cheap quote.

[Cleanroom]

Board swaps will not fix this issue. If the data is important I would refrain from trying other terminal commands to it since it is possible you could cause more damage.

300 is not bad

You can try and talk with BlackST he is in italy and may be able to help you for cheaper

[BlackST]

Do you think I can have any chance of success just swapping the PCB with a new one that is exactly the same model, with the same board number, main controller IC and motor combo IC?

Closer to the chances about being invited to have a dinner with Sharon Stone tonight.
(Replace Sharon Stone with favourite actress name just in case).

[Uncle Scrooge]

Board swaps will not fix this issue. If the data is important I would refrain from trying other terminal commands to it since it is possible you could cause more damage.

300 is not bad

You can try and talk with BlackST he is in italy and may be able to help you for cheaper

Why cant swap fix? What does it make each PCB "unique" to its own hard disk?
The firmware is not hosted on the PCB but anywhere else inside the drive?

Closer to the chances about being invited to have a dinner with Sharon Stone tonight.
(Replace Sharon Stone with favourite actress name just in case).

Ok, got the message Just trying to understand the reason.
Cleanroom suggested me to talk to you for help... do you have a recovery lab here in italy?

[BlackST]

The reason : something went wrong during update as it is always a RISKY procedure. Sum up that these drives are quite unstable by themselves.
FW is split PCB+disk. Try another PCB and see...

[Uncle Scrooge]

Oh I really trust your words, I don't need to try and see.
Do you have the right tools for making the firmware repairing job? I could pay you for the job instead of other data recovery labs.

[BlackST]

Need to know some details just to be extra sure. I will PM - in Italian.

[Uncle Scrooge]

Ok then, waiting for your PM, thank you very much

[Uncle Scrooge]

Still waiting for you, did I say anything that offended you?

[BlackST]

Absolutely no. You have PM (you missed a call and then day after I was out for 1 1/2 day ... emergency call) !

Best regards.

[Uncle Scrooge]

I dont get your PM, the last PM i got from you was on January 18th. Maybe PMs are not so reliable, Im gonna sending my personal email address to you so we can keep on communicating using emails. Im sending PM to you now with my email address.

[vigu34]

If you buy one identical HDD (second hand 30 euro aprox) and change their electronics??

[fzabkar]

Why cant swap fix? What does it make each PCB "unique" to its own hard disk?
The firmware is not hosted on the PCB but anywhere else inside the drive?

These articles should answer your questions.

Inside the firmware (Author: Aimtrading):
newbie-info- from-and-for-newbies-about-firmware-etc-t6562.html

HDD from inside: Tracks and Zones:
http://hddscan.com/doc/HDD_Tracks_and_Zones.html

[BlackST]

The problem is going to be analyzed... And solved.

[Uncle Scrooge]

If you buy one identical HDD (second hand 30 euro aprox) and change their electronics??

Everyone here is saying that swapping the electronic wont help, and from other experiences i read on the web, its true.
Each electronic of each drive of these series are unique in some way.

[Uncle Scrooge]

The problem is going to be analyzed... And solved.

You disappeared and stopped replying my PMs again. I don't understand your behaviour, dude, if you changed your mind about helping me, at least dont leave me waiting in vain.
Regards...

[lcoughey]

As a first attempt, I connected the PCB to a serial-to-TTL interface and I used Windows XP hyper terminal, trying to fix the drive using the procedure for the Barracuda 7200.11 in BSY state. My drive is the 7200.12 serie and so it didn't work. The PCB just responded with error messages.

Correct me if I'm wrong, but the firmware updates were for the 7200.11 series drives, not the 7200.12. So, if you ran a 7200.11 firmware update onto a 7200.12 drive, you likely killed your drive for good and it is going to take a very experienced data recovery tech to undo that mess.

[Uncle Scrooge]

No i updated with the correct firmware for my drive model, downloaded from here:
http://seagate.custkb.com/seagate/crm/s ... NewLang=en

[lcoughey]

As a first attempt, I connected the PCB to a serial-to-TTL interface and I used Windows XP hyper terminal, trying to fix the drive using the procedure for the Barracuda 7200.11 in BSY state. My drive is the 7200.12 serie and so it didn't work. The PCB just responded with error messages.

Correct me if I'm wrong, but the firmware updates were for the 7200.11 series drives, not the 7200.12. So, if you ran a 7200.11 firmware update onto a 7200.12 drive, you likely killed your drive for good and it is going to take a very experienced data recovery tech to undo that mess.

I guess I'm wrong...it would appear that the update you downloaded was for this drive. So, you definitely need someone who is good with Seagate firmware to see if they can pinpoint where things went wrong.