I tried to fix SEAGATE ST3750330AS, as it was not recognized by Computer BIOS. I was able to connect to it using terminal software but as I tried to spin it UP, after I had been spinning it down before removing the piece of paper from between the HDA and the PCB, so as I tightened the screws and tried to spin the hard disk up using F3>U command, so it didn't spin up and soon afterwards as I tried to tighten the screw that went inside the HDA, so error message came up and the procedure halted!

After that, I haven't been able to spin up the drive, although I have tried it many many times and I haven't been able to get terminal connection to the drive.

As I have tried to make connection, so as the terminal windows has been opened and I have given it CTRL+z command, nothing has happend and nothing has been showing in the terminal window.

What could have caused this? Is it possible that some static electricity shock has taken place and has taken its toll on TVS diodes or what might have cause this problem?

My friend has several 100 Gigabytes of vital information on the HDD, so I am desperate to find help to this problem!

Looking forward to replies as the matter is urgent

I guess you need to buy your friend a data recovery service as a Christmas gift since you f-up the drive

_________________
SAN, NAS, RAID, Server, and HDD Data Recovery.

I did as I was instructed by Gradius2 or somebody else who had the proper information on how to fix the BSY STATE issue. The HDD was not recognized before I began to work on it!

I have already proceeded in the matter, sending a "I would like to purchase so and so HDD" information through a certain channel in order to swap the PCB and also to remove the EPROM from the faulty PCB to the PCB of another HDD, HDD that is up to the requirements that has to be met, in order for the PCB swapping to be succesful!

This is what I intend to do, I am going to look for a PCB to replace the faulty PCB of my Seagate ST3750330AS

The information concerning that ST3750330AS is as follows!

S/N: 9QK1CWD5
P/N: 9BX156 – 568
PRODUCT OF THAILAND
Firmware: SD81
Date Code: 09077

But I am only going to do it, if it becomes evident that the PCB is broken, and it can't be fixed through the advices given by the members of this, very rich in information and valuable discussion forum!

Nobody told you that there is no "one fits all" solution , that one wrong letter in command DOES fuck up the drive AND that the problem could also be somewhere else ?!?

(NOW you know, anyway...)

And you still persist in DIY?

_________________
PC Image Data Recovery
http://www.pcimage.co.uk

New!! HDD-PCB.COM for all your PCB and donor HDD requirements!

Repetita juvant , and "no guts, no glory" .

Sending the spin down/up commands in terminal can't do any harm on their own so you must have messed up something else. Best you describe what you think went wrong.
Are you saying the drive dosn't spin any more?
Or maybe you need to look at your set up, ttl adapter and connections.

I followed the advice very carefully and the HDD was receiving them until I told the HDD to Spin down with Z command and after that I remove the paper that had isolated the PCB from HDA and things were still all right and the clock was running in the lower left-hand corner of my Terminal Programme. Then I inserted 3 screws, that I had picked out before and tightened them one by one. The last screw was the one that was located there where the HDA was, and I tightened it also.

I was prior to me tightening the screw when things were still OK but then when I gave the command U, in order to spin up, so after a short while an error message came up with something like this "Error 1009 DETSEC" and then shortly afterwards as I tightened the screw located at the other side of the PCB there where the HDA was, error message appered and terminal program stopped reacting.

I later on tried to connect to the HDD through Terminal Programme, but it was of no avail, as I could not connect it and the Hard Disk didn't spin up afterwards. I tried it with other computer's powersource and the outcome was the some, no spin up.

And so as to provide my answer to PCIMAGE!

It is not up to me to decide whether my friend is willing to revert to Data Recovery company, such as You represent, but if we find out, that that's the only way to get the Data back, so in that case It would be possible.