7200.14 Repair Tx Rx Hyperterminal F3 T
Joined
·
2 Posts
Quote:
Originally Posted by BARBYBOY
I have the same issue with my Seagate 500GB 7200.12 hard drive
It just died one day and stopped being recognized by BIOS any more.The only way of booting the system from another drive with this one disconnected.
To make a story short. I read the whole thread here and there, did the cable, connected my drive but cannot go any further after the step where you remove plastic card and use U command in Putty (HyperTerminal)
My problem is:The error i am getting after removing plastic from the SPIDER and using U commnad is the following:
F3 T>/2F3 2>Z
HighPowerMode
Spin Down Complete
Elapsed Time 0.087 msecs
F3 2>UHighPowerMode
ExecuteSpinRequestDiagError 00006008
Spin Error
Elapsed Time 765.494 msecs
R/W Status 2 R/W Error 84150180
F3 2>AND NO ((((ANY SOUND))) IN HARD DEVICE
Who knows what is that and if it can be fixed?![redface.gif]()
??????
Joined
·
4 Posts
hello, i just picked up a ST31000340AS one TB sata drive with troubles.
it was recognized and somewhat usable in windows but the format process would not finish and kept knocking the drive offline completely.
there was some clicking at boot time and occasionaly other times but not really obsessive.
i would have to power off and back on to get it back.
i ran the current firmware update from seagates website.
the version was SD1a i think.
now the the bios reports the correct drive model and autodetect works but i cant find any software that sees the drive at all.
the firmware appears to have killed it.
apologies not having read this thread but it seems we're talking about the same drive at least.
the last few posts seems to discuss a direct hardware flash?
i dont think i need that.. i was able to run the firm update a second time so it works to that point.
anyone with some knowledge on this problem please give me a PM? or reply here if the topic permits.
thx.
Joined
·
3 Posts
hi ocn0417,
can you see the hard drive in your bios ?
Joined
·
4 Posts
Joined
·
3 Posts
right click "my computer", select "manage" and then from there "disk management".
see if you can see your drive, if yes then right click on it and select the option to assign a letter to it.
restart your pc and see how that goes
Joined
·
4 Posts
does not appear in drive manager.
i have hirems bootcd with drive and mbr utils etc.
i cannot write a new mbr with any of the mbr utils partition programs report no drive etc.
partition magic fdisk etc do not see it or cannot read /write to it.
Joined
·
4 Posts
"the label on the HD says ST31000528AS, but the older ones are actually ST31000523AS ."
that statement was something i just noticed in a google result thread but does sum up the question
i have about my drive.
the firmware update almost seems to be wrong.
the drive is worse after having installed it. my drive was working intermitantly before and not at all now.
so i am wondering if i have some earlier model that should probably use firmware from the previous model.
my part number is 9BX158-303.
does anyone know where i can get the previous firmware for THIS model and what is the next nearest
previos model of this model most likley to have the same architecture/ geometry?
dangerous idea i know but at this point the the drive is worthless anyway.
Joined
·
1 Posts
why is it, i get all the way up to the take power off part, wait 10 seconds then power back in.
when i plug it back in, i cant type anything in the hyper terminal?
Joined
·
2 Posts
Is this tutorial applicable for Seagate ST3000DM001 HDDs???
I readed somewhere that the parameter for 7200.14 drives is m0,5,1,10,3,,,22 instead the one shown at step 13, is that true?
Are all the other steps the same for that model?
I have some Seagate ST3000DM001 drives in BSY state and I want to fix them.
Joined
·
1 Posts
I only created an account to come here and say that this fix worked for me. Cost me about £10 or less for the cables , v easy to do albeit a bit fiddly and difficult to get right if cables won't play ball but it really worked and I did not think it would.
So to everyone who wrote here to post this solution and any amendments - THANK YOU
Joined
·
1 Posts
Hi everyone,
i just managed to revive a bricked seagate disk thanks to the effort and time of everyone here.
It was dead for more than three years.
First of all, I'd like to say to everyone that will try this: "READ EVERYTHING CAREFULLY"!!!
My notes on this:
1. I started at a 64bit win7 system on a macbook pro, could not get it to work, so i thought i 'd try it to a 32bit WinXP system... I dont know if this played any part to the procedure or not, but i got it working on WinXP.
2. I used this adaptor bought from ebay: http://www.ebay.com/itm/371175265028?_trksid=p2060778.m2749.l2649&ssPageName=STRK%3AMEBIDX%3AIT
3. If you are using a pc (desktop, with regular towercase), you do not have to plug the grnd from the adaptor to the disk. Just the two TX-RX, if you are powering the disk from the SAME pc. It just needs to share same ground as noted in: https://sites.google.com/site/seagatefix/
4. When you open the hyper terminal, maybe you have to set it up (from properties icon>settings tab: function arrows and ctrl keys act as) to windows keys option
5. If ctrl+z does not show F3 T> then switch RX TX cables on the adaptor.
Everything else is more or less the same. Check everything thoroughly over and over but the point is that if you get to command line on hyper terminal you have many chance to fix this.
Regards
Joined
·
1 Posts
I have a momentus 5400.6 320gb external hard disk ST9230320AS which is not recognised by windows and can be seen in disk management as disk unknown not initialised. It spins up fine and spins down again after a few seconds when it appears to not load. In diskpart it has a size of 0 bytes. This 0 bytes has led me to this thread. Does it sound possible that the firmware has got damaged and this fix will solve the problem? I am by no means a programmer so this will require quite a bit of effort by myself but I wanted to check with you guys that it would be worth a go if it sounds similar to all your hard drive problems? I don't have any of the cables that is mentioned in the walk through so will have to purchase them also. Thanks
Joined
·
1 Posts
I have got a Seagate Barracuda 7200.12 1 TB ST3100528AS with CP38 firmware. Is is broken a while and after saw your posts I decided to fix it.
I bought a "USB 2.0 to UART TTL Serial Converter Module CP2102 STC Programmer With 6PIN wire" for fixing. I wired the hard drive to my pc (Windows 7 ultimate x64) and opened HyperTerminal.
I followed your every recipe and after connecting with HyperTerminal I saw symbols on screen continuously. They didn't stop so I can't write anything. I changed RX DX combination but this time I have got only a white screen. I think I connected with my hard drive but something is wrong. Have you got any idea?
Joined
·
1 Posts
Just found out that this may be the problem with my 750 GB Barracuda 7200.11 with firmware SD15. I am waiting for an adapter from amazon.com and I'll post the results. The PCB on the drive does have a discoloured heat sink pad near the motor connection.
Joined
·
1 Posts
So I just got this issue for the second time in as many years, and rather than drop another $640 at the same data recovery place that apparently didn't update the firmware the last time this happened, I've decided to try and fix it myself, but I have a couple of questions:
1. Will any USB-to-TTL adapter work, like this one for Raspberry Pi, or this one from Amazon, or does it have to be a CP2102 chipset?
2. Does Step 13 wipe the drive? post 256 makes it sound like it doesn't, but I want to be sure.
Joined
·
1 Posts
Hello,
does anyone know how to connect the adapter to a USB TTL MAXTOR IDE hard disk pata. The connector for the jumpers are so SLAVE MASTER:
: : : . :
Do you know which is the channelS that the RX - TX GND channel?
I found nothing on the net !!
Joined
·
804 Posts
Check out http://www.hddoracle.com/viewtopic.php?f=6&t=193&p=3938
On that page is this pic:
BTW, I'm having my own ST3000DM001 "not recognized" issues. Two drives failed in my raid. One of them (disk 0) was making the clicking sounds, so I figured he was toast anyway. D#0 would start up, spin up, then click 10 or 11 times, give up, spin down. I took its cover off and the heads deteriorated and there's black dust everywhere. I swapped out a set of heads from another drive, blew out the dust and tried it. I figured it was probably dead anyhow, so nothing left to lose. Yeah, it's borked.
Serial port output when powering up disk:
Code:
Code:
Boot 0x40M Spin Up FAIL Servo Op=0100 Resp=0003 ResponseFrame 0780 004C 03B4 3400 0008 0000 0000 0000 0E53 0000 0000 0000 0000 0000 0000 0000 5274 4053 A858 DEF3 15B0 1B76 31CC 5880 6CDA 2B5A 0000 007F 0000 0000 001C 0004 0010 FAIL Servo Op=0100 Resp=0003 ResponseFrame 0000 004F 03B4 3480 0008 0000 0000 0000 0E37 0000 0000 0000 0000 0000 0000 0000 5274 4053 A858 DEF3 15B0 1B76 31CC 5880 6CDA 2B5A 0000 007F 0000 0000 001C 0004 0000 It doesn't look good...
Here's what linux's syslog says when trying to power up:
Code:
Code:
# grep "ata1[:\.]" /var/log/syslog Sep 20 18:45:01 kernel: [ 3.852972] ata1: SATA max UDMA/133 abar [email protected] port 0xfbf25100 irq 88 Sep 20 18:45:01 kernel: [ 4.172319] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Sep 20 18:45:01 kernel: [ 9.169463] ata1.00: qc timeout (cmd 0xec) Sep 20 18:45:01 kernel: [ 9.169469] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4) Sep 20 18:45:01 kernel: [ 9.489255] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Sep 20 18:45:01 kernel: [ 19.483537] ata1.00: qc timeout (cmd 0xec) Sep 20 18:45:01 kernel: [ 19.483544] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4) Sep 20 18:45:01 kernel: [ 19.483546] ata1: limiting SATA link speed to 3.0 Gbps Sep 20 18:45:01 kernel: [ 19.803351] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 320) Sep 20 18:45:01 kernel: [ 49.786187] ata1.00: qc timeout (cmd 0xec) Sep 20 18:45:01 kernel: [ 49.786199] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4) Sep 20 18:45:01 kernel: [ 50.106011] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 320) Sep 20 18:46:12 kernel: [ 74.570337] ata1: exception Emask 0x10 SAct 0x0 SErr 0x4090000 action 0xe frozen Sep 20 18:46:12 kernel: [ 74.570339] ata1: irq_stat 0x00400040, connection status changed Sep 20 18:46:12 kernel: [ 74.570341] ata1: SError: { PHYRdyChg 10B8B DevExch } Sep 20 18:46:12 kernel: [ 74.570344] ata1: hard resetting link Sep 20 18:46:12 kernel: [ 75.291601] ata1: SATA link down (SStatus 0 SControl 300) Sep 20 18:46:12 kernel: [ 75.307581] ata1: EH complete Next up I'll try and sort out the other drive, which was giving COMRESET errors and actually appears in BIOS... I'll see what that one's terminal says when it turns on.
Joined
·
1 Posts
This method did not work on my hard drive 1TB Barracuda 7200.12 ST31000524AS. Just a blinking cursor in the terminal.
Probably not the solution for my problem. Hard drive when you switch on knocking ~10 times and fades out. In the system is seen as 4 GB. I don't know what else to do (except throw).
Joined
·
6 Posts
Hoping someone's still around to help me with this. Had a Seagate usb GoFlex 1TB drive suddenly become unrecognizable. Disappeared from drive management.
Sent it for free diags, they said unrepairable - firmware is corrupt, so I'm trying to use this tutorial to rebuild the firmware. I have a USB/TTL converter wired up with gnd/TX/RX to the drive, and cable plugged in for power (paper insulating the data connector).
I plugged the drive in til it stopped powering up (I dont have any weird drive sounds). Plugged in the USB (installed drivers ok), then ran hyperterminal.
At hyperterminal it doesn't bring up F3 T>, just a blinking cursor. I swapped TX and RX thinking I got them crossed, still no effect.
The pictures in the thread are nonexistent now, can someone confirm the proper pinouts for Freeplay ST1000LM010 at least? I don't know why I'm not getting a response from Hyperterm.
Beyond that I'm lost, never used Hyperterm or tried to restore a drive. HELP!
7200.14 Repair Tx Rx Hyperterminal F3 T
Source: https://www.overclock.net/threads/seagate-bricked-firmware-drive-fix-with-pics.457286/page-14
0 Response to "7200.14 Repair Tx Rx Hyperterminal F3 T"
Post a Comment