Gradius2

The Solution for Seagate 7200.11 HDDs

4,868 posts in this topic

And BTW, it's not that dangerous! You are not shorting power supply pins (i.e. big sparks flying etc.), but low voltage and current signal pins.

I thought rather about shortcutting the predriver of the motor.

And that's why I first will try to apply the cardboard in the moment described at the russian page. Ther is at a 80% chance that it makes the same job as the jumper ;-).

I thought you already did that as this is the common method.

Good luck! I fully understand that you don't want to risk you data, at least not any more than necessary.

0

Share this post


Link to post
Share on other sites

Done!

Without jumper

And without cardbord! ;-).

*) I figured out that if you losen the screws, the PCB looses contact to the connector.

*) For each connector there is a screw to to press the PCB against the connector.

--> If you first losen all screws that affect one connector, than you can open and close the contact to the connector with screwing the connector screw in or out.

Attention:

I was wrong: It's not the motor that has to be blanked out, it's the heads (at least at my model).

(was pointed to by: "After the closure of these contacts, the head within 5 ~ 7 seconds klatsayut, then the engine itself stops")

So procedure is:

1) optional: Loosen all screws and lift PCB so far that you can be sure PCB is not stuck at the metal body of the HDD anywhere and remount the PCB

2) Loosen all screws so far that the head connector is dissconnected. Keep in mind that the PCB must not be bent.

3) Tighten only the head connector screw so that it get's contact again

4) Supply power to the disc, wait until you get the LED: blablabla message

5) Keep sending Ctrl Z until you see the F3 T> promt

6) Quickly loosen head connector screw to disconnect heads (it's important to make this very quickly otherwise heads could be at least stressed)

7) If you managed this you have all the time of the world. Continue like described in the guides -> send /2 to change to level 2 and wait 15s and so on

I used terminal V1.9b and made a Makro for each, Ctrl Z, /2, Z.

Regards

Chilli

0

Share this post


Link to post
Share on other sites

Hi guys, i successfully recovered my busy 7200.11 but trying 0 LBA error recovery on the other one i have, the hyperterminal doesn't prompt me the f3 t> beginning message! how can i do? thanks!

Edited by alexpalma83
0

Share this post


Link to post
Share on other sites

At the previous post I ment Strg z (low case) or ASCII(026 dec).

Now I have sucessfully recovered the HDD but the flashtool refuses to flash the drive (see attachment).

Maybe because it's an OEM drive?

I don't really know from which OEM vendor or model this is. It might be a coincitance that FSC is short for Fujitsu Siemsn Computers, but might also be that this comes from a charge detemined for FSC.

I guess there is a trick for reflashing OEM HDD?

Regards

Chilli

flashtool_output.bmp

0

Share this post


Link to post
Share on other sites

You simply cannot use the standard flash tool on drives that have other firmware versions than the ones listed on the seagate page. If the drive is OEM, you have to contact the OEM for a flash upgrade tool. ;) Or Seagate and ask them, if they are willing to help, given the circumstances.

0

Share this post


Link to post
Share on other sites

Unable to fix my 7200.11

MY HDD BARRACUDA 7200.11 500GB ST3500820AS FIRMWARE SD35

MADE IN THAILAND, ( WAS ATTACHED TO SEAGATE EXTERNAL FREEAGENT DESKTOP)

Steps Tried

1.> Verify it is stuck in busy state, downloaded victoria 4.2 and ran a PCI scan and the busy was blinking occasionally.

2.> Verify the serial interface cable is working properly

CA-42 Clone Chinese make, Blue, Red,Green White and Yellow, Ripped open the USB end connector and found that

Green -> TX

Red -> RX

Blue-> GND

Connected the cable to front USB connector of Desktop pc and it detected the USB -> UART and installed the driver from the cdrom which came with cable, the driver was Nokia CA-42 USB, no chip was mentioned.

Connected TX with RX for loopback test

Ran putty with 38400,8 N 1, none for hardware flow

the loopback was successfull as the letters were getting echoed back on screen and when i removed the loopback the characters were not getting echoed.

3.> Inserted a thick paper between PCB and Hdd contacts and

Connected TX from Cable to RX of HDD, Connected RX from Cable to TX of HDD and GND of cable to GND of HDD

tried pressing CTRL + Z ( uppercase) and CTRL + z ( lowercase) .....no response

Power cycle the system + HDD, no success

Tried swapping the RX and TX cables , No Success

Removed the paper between the PCB and HDD and Powercycle the system+HDD

the putty ( terminal ) window was displaying (LED: 000000CC Faddr.........) every 1 min

tried pressing CTRL + Z ( uppercase) and CTRL + z ( lowercase) .....no response

, I would like you comments

1.> Since i am getting LED message in terminal window, does this means my serial interface is properly connected

2.> Do I need to add power ( 3.3v) to other pins

0

Share this post


Link to post
Share on other sites
1.> Since i am getting LED message in terminal window, does this means my serial interface is properly connected

Yes.

2.> Do I need to add power ( 3.3v) to other pins

No, if the loopback tests work and you get the messages the thingy is working. (unless for some reason the interfacce TTL levels is not adequate, i.e. the Rx "understands" the data sent by the PCB, but the "Tx" is not understood by the PCB. :unsure:)

You should be able to check the peak levels of the interface with a multimeter:

http://www.interfacebus.com/voltage_threshold.html

(i.e. is it possible that you are sending 5V TTL/CMOS levels instead of 3.3 V TTL ones :blink: )

AFAICR you should be able to establlish a connection also with the PCB completely detached from the HD.

Which contacts did you try insulating (there are two ways, one insulating the Head contacts and one insulating the Motor ones).

Try the other way:

http://www.msfn.org/board/index.php?showtopic=133387

Take your time reading the thread, there are several reports about CA-42 (or seemingly CA-42 cables) you may be able to find a report of success with one exactly like yours (and possibly some more connection details).

jaclaz

0

Share this post


Link to post
Share on other sites

No luck with FSC :(

FSC gave it's HDD business to Toshiba and Toshiba has just OEM business (no customer support).

I'll keep searching, but things don't look good.

Maybe need to crack flash software ;-).

Regards

Chilli

0

Share this post


Link to post
Share on other sites
2.> Do I need to add power ( 3.3v) to other pins

No, if the loopback tests work and you get the messages the thingy is working. (unless for some reason the interfacce TTL levels is not adequate, i.e. the Rx "understands" the data sent by the PCB, but the "Tx" is not understood by the PCB. :unsure:)

Yes and no. In this casewhere you already do receive it should also work the other way.

If the power you use for the HDD and the PC with the USB cable is not the same you propably do not have a common ground.

I connected my Srerial TTL cable to the HDD GND (the jumper pin right next to the Rx TX pins of the HDD).

Ofcourse you can olny do that if you have potential free power supplies (which is standard) otherwise *BOOM*

Regards

Chilli

0

Share this post


Link to post
Share on other sites

I measured the Voltates

GND and TX - 3.2 Volts

GND and RX - 3.1 Volts

The Power to HDD is coming from PC's SMPS, and USB is connected to Same PC, also I have connected the USB Cable GND to HDD GND

When i Put a insulation between PCB and HDD, i.e. for Motor Pins or Other Pins ( rectangular set) , I am not getting any data from the HDD to terminal

Only when i remove the insulation i keep getting

LED: 000000CC FAddr:0024900D from Hdd every minute.....

0

Share this post


Link to post
Share on other sites

@sunlit

Than pls go back just a few posts to my stepwise instruction,.

You might have the same problem I had.

Regards

Chilli

0

Share this post


Link to post
Share on other sites

I tried

1) Loosen all screws and lift PCB and remount the PCB

2) Loosen all screws so far that the head connector is dissconnected.

3) Tighten only the head connector screw so that it get's contact again

4) Supply power to the disc, wait until you get the LED: blablabla message

5) Keep sending Ctrl z ( z in lowercase) had also tried Z in uppercase

( i kept sending for 3 minutes but i could not see the prompt at all )

the prompt keeps on alluding me.......

0

Share this post


Link to post
Share on other sites

So you never see a prompt, not even (all connectors connected) when sending countinously CTRL z at startup?

If you use Hyperterminal, Ctrl z should be fine.

If you are using another terminal, can you send ASCII (026) dec? Not that some terminal emulation does not allow Ctrl z...

As far as I see there only three possibilities:

1) Your drive can not "hear" you

2) You do not physikally send Ctrl z

3) Your drive has a problem that has nothing to do with the BSY bug even if symptoms are similar.

What you can try:

Use another terminal programm or play with terminal adjustments (emultaion adjusttmens - baud rate etc. must be OK if you can receive

Use another cable for serial level conversion (or check yours with Osci/level converter to insure it sends what you want to send)

Send the drive to me ;-)

0

Share this post


Link to post
Share on other sites

Has anybody flahed a OEM drive with Seagate firmware yet?

Is there a tool to read out SW?

Since you can update firmware at all, configuration data for seagate firmware seems always to be at the same addresses.

I would guess that the same applies also for OEM firmaware. But a risk is still there.

I'm afraid this topic has to wait for the next weekend :) (Spent much too much time on in this one).

Greeetings

Chilli

0

Share this post


Link to post
Share on other sites

As I said, you can always try to contact Seagate. They should be able AND WILLING, to support you, considering it was THEIR fault that these drives drop like flies. They should be able to get you either the program for your specific firmware, or a flash-program that doesn't check for the part number AND FW revision.

Maybe you'll have to be quite persistent, though, to make them help you.

0

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.