Jump to content

The Solution for Seagate 7200.11 HDDs


Recommended Posts

And finally before commands:

post-230434-1233749943_thumb.jpg

That's the head motor, nothing to do with SPIN motor. :whistle:

aviko is just trying to discredit a proven fine guide. :rolleyes:

We all have enough of it.

If you see, those guys have just 1 to 3 post max, and this is why they don't know this dirty play aviko is doing.

If he was right since start, he should just started long ago his own topic (or leave) in first place, and not trying to continue to discredit a proven fine guide.

This topic got so messed because of him, I'll just close it.

Edited by Gradius2
Link to comment
Share on other sites


Hi again,

Now i've tried the loopback test so my setup is correct.

I dont get any response from the terminal, I dont get "F3 T>", but i can type..

I placed a paper card between the motor connector and the harddiskmainboard like in post #1, attached the tx and rx cables, opened hyperterminal, and then powered on the drive, and then pushed CTRL+Z... But i don't get anything?

Anyone that can help me? Over msn maybe?

I have a 3500320AS with SD15 firmwire. And i bought i RS232-TTL usb-converter.

I have the same problem as Alexx86 the set up is right but I get nothing but the small arrow mark on hyper terminal. Any help would be greatly appreciated

I have the same drive and firmware version Thanks

try connect ground from your cable to pin 3 in terminal socket of disk. i think it finally solved Alexx86 problem. we did everything from scratch, step by step so hard to tell.

I can tell you that adding a ground got my terminal working (finally)...

Aviko, thanks so.......much it all worked like a charm backing up my data now as we speak.

The earth from the cable did the trick.

Thanks again you are definately my Hero!!! Cheers :thumbup

Link to comment
Share on other sites

And finally before commands:

post-230434-1233749943_thumb.jpg

That's the head motor, nothing to do with SPIN motor. :whistle:

aviko is just trying to discredit a proven fine guide. :rolleyes:

We all have enough of it.

If you see, those guys have just 1 to 3 post max, and this is why they don't know this dirty play aviko is doing.

If he was right since start, he should just started long ago his own topic (or leave) in first place, and not trying to continue to discredit a proven fine guide.

This topic got so messed because of him, I'll just close it.

of course its head CONNECTOR, heads doesnt have any motors. I explained why isolating heads is better solution few times in earlier posts. this method is one which will work with ES.2 series and work also with DM22 and 7200.11, New firmares doesnt open terminal if motor connector is isolated. thats why we seen so many people who cant open terminal. I can discredit your competence on every post which you type. But you immediately change your post and then I look as this bad guy. almost all your posts are EDITED. There are posts where its only a DOT and signature.

Stop lying mr Fernando Martinez

Link to comment
Share on other sites

BASICGUY

Hmmm not too sure, And you will need some more bits of cables etc.

This will definately work and the delivery is quick, and the guy there Rob is really helpfull (in an Electronics type way).

http://cgi.ebay.co.uk/RS232-to-3-3-Volt-TT...A1%7C240%3A1318

And its at least £10 cheaper.

A nokia 3210 fbus data cable is still the cheapest an easiest option, at around 2 quid and only needing the rx and tx connecting (no gnd or power)

Thanks for the reply...

How about a DCU-65 cable? - I'm sorta' on a time limit for this...

...anyway, the RS232-TTL adaptor turned out to be dead but I did manage to find a nokia 3210 fbus data cable. Couple of questions:

1. The Nokia cable has 4 pins - which are TX/RX - or how can I determine this?

2. Do I need the drivers for the nokia 3210 fbus data cable?

Thanks in advance.

Link to comment
Share on other sites

...anyway, the RS232-TTL adaptor turned out to be dead but I did manage to find a nokia 3210 fbus data cable. Couple of questions:

1. The Nokia cable has 4 pins - which are TX/RX - or how can I determine this?

2. Do I need the drivers for the nokia 3210 fbus data cable?

Thanks in advance.

If its USB you will need drivers. cable must be installed as COM port. If its connected via COM in PC - no drivers.

fourth wire is mbus which is not used here.

If DCU-65 is for sony ericsson and after plug to pc installs as usb-to-serial it will work.

pinout can be checked here just look what collors are soldered to pins rx tx and ground

Edited by aviko
Link to comment
Share on other sites

another question on CA-42.

Once the driver installed is there always 3V on tx/rx or only when HTerminal and connection is on?

Someone could test it for me?

Thanks.

Edited by Magico
Link to comment
Share on other sites

another question on CA-42.

Once the driver installed is there always 3V on tx/rx or only when HTerminal and connection is on?

Someone could test it for me?

Thanks.

tested, i my cable (which is installed as OTi U&SB-to-Serial Comm Port) gnd - rx = 3,021, gnd - tx = 2,403

no matter is terminal connected or not. always.

Link to comment
Share on other sites

another question on CA-42.

Once the driver installed is there always 3V on tx/rx or only when HTerminal and connection is on?

Someone could test it for me?

Thanks.

I think there's always voltage in it once the drivers are properly installed...but:

It seems there are 2 type of nokia cables. One is self-powered thru USB, one needs an external 3.3v power to work. Usually, the latter has more wires (tx, rx, data gnd, 3.3v in, 3.3v gnd, and maybe other stuff). So, maybe you just need to connect a 3v battery to it.

There is a great guide here that show you how identify and check your Nokia cable. I already posted this link so many times, I hope this would be the last one. Please take a look at older posts or do some searches, most of the common problems are already covered in this thread.

Here're my own 2 general little advices:

1. Always double check your terminal connection before plug any wire to the Seagate drive. I see many people here connecting random wires from random cables they found in their drawers. Connecting a standard straight USB cable to your HD is not a good idea.

2. If you get strange characters in the terminal window after connecting the drive, be careful at what you type in it! In my first attemp to recover my drive I got only random characters because I didn't connected the ground wire on the drive third pin, but actually, what I was typing were sent to the drive. I tested it: I was able to spin off the motor (/2 & Z) even without see nothing readable in the terminal window...

Be patient and good luck with the fix!

It seems that the post made by aviko yesterday (here points to two links that appear (from my very basic grasp of polski) to be what Gradius2 has posted. Can anyone confirm the published date on either of these two URLs, as in, were they up on the internet before January 18th 2009?

I follow this soap opera since the first early posts at the original 7200.11 Falling down thread on seagate forums.

So, chronologically:

Till 16 January 2009 we were all lost and confused and angry and many other things, then Shuky posted this on elektroda.pl forum:

http://www.elektroda.pl/rtvforum/viewtopic...6012404#6012404

As you can see there Nirvanowiec give him a link to:

http://yura.projektas.lt/files/seagate/720011_ES2.html

where, for the first time, were given a solution for fix the 7200.11 CC and BSY errors, by Yura. In that page (in Polish) there's no date, I think it was up since early January 2009.

Then, one day later, 17 January 2009, Shuky alias Gsustek, posted the first solution in english, based on Yura's page above, in the hddguru forum. The thread was deleted and reposted two days later. In the google cache there's still the original one:

http://209.85.129.132/search?q=cache:c_-5M...t=clnk&cd=2

I posted myself in that thread, as well as Aviko. (who also contacted me with a Pm for give help, I never answered him back, there was a bad mood there in that forum and many people were trying to misinform about those info. Still now some of them are doing that. Now I'm very sorry about it, Aviko, I was wrong. Thank you for that pm)

So we arrived at 18 January 2009, when Gradius posted his solution on this thread (based on the Shuky (gsustek)' one posted the day before) also adding that aesthetically pleasant graphic with TX and RX legend instead of ugly ascii art (the pic with the drive and tx/rx arrows insted was first posted by fatlip in the previous '7200.11 Troubles' thread) and original credit links to Yura and Shuky post, now removed.

So this are the fact by my point of view. Personally, I don't give a thing about donations or other stuff like that (actually, Gradius was and is very helpfull with many people and in many circumstances in this thread), I only think that should be right to give credit to people who saved us all.

A noticeable thing is that, now, Gradius and Aviko solutions are quite the same. Don't be confused, the only difference is that Aviko removed the command i4,1,22 because, as he explained, it isn't essential and it can damage data on the drive in some cases. He also added other commands for testing purposes only (F712,F,,22).

As you can see, this was a very long story. I really wish that there'll be a happy end now. We recovered out data, other people will recover their drive with this thread and this is really beautiful.

So, make love not war :wub:

Happy fixing!

Edited by dskbrk
Link to comment
Share on other sites

As you can see, this was a very long story. I really wish that there'll be a happy end now. We recovered out data, other people will recover their drive with this thread and this is really beautiful.

So, make love not war :wub:

Happy fixing!

Bravo

are good with you.

Edited by Tristano_74
Link to comment
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.
×
×
  • Create New...