Overclock.net › Forums › Components › Hard Drives & Storage › Seagate Bricked Firmware Drive Fix (With Pics)
New Posts  All Forums:Forum Nav:

Seagate Bricked Firmware Drive Fix (With Pics) - Page 9

post #81 of 279
Anyone else, like Superking get only a small arrow in hyperterminal when entering CTRL-Z?

Working with a ST3500320AS HDD w/ BSY problem (or at least I believe that was it since it wasn't recognized on boot up one day, no sounds, just no longer accessible).

Got all the way thru step 11 (entering N1) after successfully completing 1-8 of the guide as well as the optional F712 commands. Then things went to heck.

The terminal response when I entered N1 was a beta character on the same line, then the F3 T> prompt.

Figuring it might be okay, I continued and at step 12 received the F3 T> prompt also.

I powered the HDD down for 20 seconds while still connected, then powered back up.
The caret remained underneath the F in the last F3 T> prompt. But I went ahead and typed in the m0,2,2,0,0,0,0,22 command and enter. The HDD simply continued to spin, no hyperterminal response. Finally after 10-20 minutes I powered it down and disconnected the hyperterminal session.

I then re-placed the business card blocking data connection on the PCB and disconnected the USB (CA-42) cable readying for another attempt.

This time hyperterminal responded to the CTRL-Z with a small arrow and nothing more.

So, I'm wondering
(1) Did anyone else get the beta character after N1 was entered?
(2) Anyone else get the small arrow?
(3) Is the HDD now toast for some reason?
(4) Should there have been a CTL-Z *before* the m0,2,2,0,0,0,0,22 command to 'wake up' and get you back to the F3 T> prompt after power down of the HDD for 10-20secs?
(5) Any hope for my data??

Thanks to all those who've generously provided instructions and troubleshooting on this and other forums. Your assistance is invaluable!
post #82 of 279
I'm get the arrow because of miss switching pin between Rx and Ground ,after corrected it return to F3 T> when presss CTRL+Z

I have some question
Are commands for Seagate Barracuda 7200.11 same as 7200.12?
My disk is [Seagate Barracuda 7200.12 ST3500418AS]
after I had completed the solution, it shown the message

F3 T>m0,2,2,0,0,0,0,22
Max Wr Retries = 00, Max Rd Retries = 00, Max ECC T-Level = 00, Max Certify Rewr
ite Retries = 0000

Update Cap and Save
User Partition Format Successful - Elapsed Time 0 mins 00 secs
Zone re-format was skipped.
F3 T>

It's not show % of format like that they describe.
Max Wr Retries = 00, Max Rd Retries = 00, Max ECC T-Level = 00, Max Certify Rewrite Retries = 0000

User Partition Format 5% complete, Zone 00, Pass 00, LBA 00008DED, ErrCode 00000080, Elapsed Time 0 mins 05 secs
User Partition Format Successful - Elapsed Time 0 mins 05 secs

F3 T>

and my com can't read it in windows explorer but can see in recovery program such as;hard disk regeneration, the easy recovery program show I/O error on disk test but pass on simple mode.

How can I get the data back? please!
Edited by success - 3/3/10 at 1:11pm
post #83 of 279
So after stumbling along I can get all the way to the end and hyperterminal says everything it is supposed to.

The cable works, the codes work, spin down, spin up, everything shows up on hyperterminal exactly as laid out by Cyberguy on :http://www.overclock.net/hard-drives...ix-pics-5.html

Then when I plug the hard drive in, nothing. The hard drive is spinning now, but just no connection. Tried 2 different computers and 2 different cables. Nothing, nothing, nothing. Seagate Barracuda, 7200.11, 500GB Firmware SD25. I've spent over 10 hours screwing around with this thing. Getting pretty angry over here. Any help would be appreciated.
post #84 of 279
Hey all,

I am running WindowsXP, and I'm attempting this using the Nokia CA-42 cable. The cable installed correctly and shows up in the device manager. I have cut the end off the cable and crimped jumper wires to each of the three leads.

Unfortunately, Hyperterminal won't connect using the com port the cable is set to. The error message I get reads "Unable to Open ComX. Please check your port settings." Where X is the port number as shown in the device manager. I've tried this with all other "COM" items disabled in BIOS and all of them on (serial and parallel ports). My cable is the only com port listed in device manager.

I have tried:

Changing the port number for the cable in the device manager.
Disabling all non-essential startup and service items using msconfig.
Connecting with the cable leads attached to the drive and unattached (although I think this wouldn't affect my error).


I used a program called "portmon" to log the communication between hyperterminal and my port. Here's the report:

0.16314122hypertrm.exeIRP_MJ_CREATESerial2 SUCCESSOptions: Open
0.00000381hypertrm.exeIOCTL_SERIAL_SET_QUEUE_SIZESerial2SUCCESSInSize: 8192 OutSize: 8192
0.00000040hypertrm.exeIOCTL_SERIAL_CONFIG_SIZESerial2 SUCCESSSize: 0
0.00000034hypertrm.exeIOCTL_SERIAL_GET_BAUD_RATESerial2SUCCESS
0.00000036hypertrm.exeIOCTL_SERIAL_GET_LINE_CONTROLSerial2SUCCESS
0.00000043hypertrm.exeIOCTL_SERIAL_GET_CHARSSerial2 SUCCESS
0.00000044hypertrm.exeIOCTL_SERIAL_GET_HANDFLOWSerial2SUCCESS
0.00000030hypertrm.exeIOCTL_SERIAL_GET_BAUD_RATESerial2SUCCESS
0.00000029hypertrm.exeIOCTL_SERIAL_GET_LINE_CONTROLSerial2SUCCESS
0.00000029hypertrm.exeIOCTL_SERIAL_GET_CHARSSerial2 SUCCESS
0.00000030hypertrm.exeIOCTL_SERIAL_GET_HANDFLOWSerial2SUCCESS
0.05402632hypertrm.exeIOCTL_SERIAL_SET_BAUD_RATESerial2SUCCESSRate: 38400
0.00285265hypertrm.exeIOCTL_SERIAL_SET_RTSSerial2 SUCCESS
0.00299006hypertrm.exeIOCTL_SERIAL_SET_DTRSerial2 SUCCESS
0.00399649hypertrm.exeIOCTL_SERIAL_SET_LINE_CONTROLSerial2SUCCESSStopBits: 1 Parity: MARK WordLength: 8
0.00299053hypertrm.exeIOCTL_SERIAL_SET_CHARSerial2 SUCCESSEOF:0 ERR:0 BRK:0 EVT:0 XON:11 XOFF:13
0.00698539hypertrm.exeIOCTL_SERIAL_SET_HANDFLOWSerial2SUCCESSShake:80000001 Replace:80000040 XonLimit:80 XoffLimit:200
0.00000032hypertrm.exeIOCTL_SERIAL_SET_TIMEOUTSSerial2CANCELLEDRI:10 RM:0 RC:0 WM:0 WC:5000
0.02991895hypertrm.exeIRP_MJ_CLEANUPSerial2SUCCESS
0.02508913hypertrm.exeIRP_MJ_CLOSESerial2SUCCESS


Note the cancelled command three lines from the bottom. I have no idea what the information means. Any ideas would be greatly appreciated!
Edited by BigLeg - 3/23/10 at 10:13pm
post #85 of 279
I have the cable - made as needed
Windows XP will not recognize it at all and I can not find a driver either
Who can help?
I have 2 500GB bricked drives here as I just leared the hard way of the glitch
1 was the backup of the other (not raid though) so one failed and thought I was good still then the other went a few days later go figure.

Can I download the usb driver for the CA-42 cable somewhere?
Thanks
post #86 of 279
There is a Ctrl z comand missing just before the F3 T> m0,2,2,0,0,0,0,22 line.

After the s.m.a.r.t. erase...

the Ctrl z gets back the F3 T>

clay
post #87 of 279
Quote:
Originally Posted by bearrcat View Post
I have the cable - made as needed
Can I download the usb driver for the CA-42 cable somewhere?
Thanks

You should be able to download it from nokia themselves as well. Just install the driver not the entire suite.
post #88 of 279
Thread Starter 
If I can find the damn driver disk I'll upload it and post a link for you guys
Sexy Lexy
(15 items)
 
  
CPUMotherboardGraphicsRAM
Phenom II 955 Black Edition Asus M3N-HT Deluxe XFX GTX280 @ Stock Speeds 4GB OCZ Platinum DDR2-1066 
Hard DriveOptical DriveOSMonitor
1TB WD Black Edition LG SATA DL-DVD Lightscribe Windows 7 x64 Ultimate 23" Samsung LED 2ms 
KeyboardPowerCaseMouse
Saitek Eclipse Corsair 850w NZXT Lexa Silver OCZ Equalizer 
Mouse PadAudioOther
Huge Cyber Snipa pad X-Fi Xtreme Music A slice of love 
  hide details  
Reply
Sexy Lexy
(15 items)
 
  
CPUMotherboardGraphicsRAM
Phenom II 955 Black Edition Asus M3N-HT Deluxe XFX GTX280 @ Stock Speeds 4GB OCZ Platinum DDR2-1066 
Hard DriveOptical DriveOSMonitor
1TB WD Black Edition LG SATA DL-DVD Lightscribe Windows 7 x64 Ultimate 23" Samsung LED 2ms 
KeyboardPowerCaseMouse
Saitek Eclipse Corsair 850w NZXT Lexa Silver OCZ Equalizer 
Mouse PadAudioOther
Huge Cyber Snipa pad X-Fi Xtreme Music A slice of love 
  hide details  
Reply
post #89 of 279
I had a Raid 0 array setup using two seagate 500gb hard drives. One of the drives started to not get recognized by the bios. I used the cable and hyperterminal and now the bios recognizes my drive and when booting the bios tells me I have a healthy array. My system won't boot. When I boot using alternate drive containing windows the raid array seems to hang up the pc. Anyone have any ideas? I need to recover some data really bad. Thanks in advance.
post #90 of 279
Well..I hope that this Thread is not still dead.Hi guys...good to know that there are people who really care and share their knowledge to solve over's burduins.I got a Seagate Barracuda ES.2 (engineering sample).Same diagnostics: after a restart the computer hangs a lot at POST and doesn't recognise it at all.The problem happend to me about 5 months ago,I went to warranty but there it was said to me that the warranty does not recover the data.I can't give my HDD for a new one because Ihave my Diploma Project on it.I read this thread and decided to take my chance.I buyed a Ca-42 cable.Unfourtanetly I can't get it work.My cable is Made in Thailand (CM09083821) with 5 wires (ble,red,white,black and yellow).Even if i strip it the internal structure is molded,there a better chances to destroy it than to see what it is inside.I read over the internet and the required setups doesn't work for me.But I managed to do something.
My setup:I put the plastic between the PCB and the rectangular connector so when the HDD is powerd on it must not spindle,only the PCB must work.Here it comes my confusion:the only way to make my CA-42 to be seen in the device manager is the following:the red and blue wire must be connected to the TX and RX of the PCB (it doesn't matter how: blue-TX and red-RX or red-TX and blue-rx ) AND the Sata power cable from the Power supply must be conected to the PCB of the HDD.If the power supply connector is not connected the recognise in the device manager does not work.Does this mean that I had discovered the RX and TX terminal of the CA-42?I tried to disconnect the power supply,the blue and red wire connected and to see if the CA-42 cable can be supplyed with power from a 3V battery (round battery from a motherboard).I tried different configurations with the remaining 3 wired (white,black and yellow) but i get so far no result.From this comes my confusion.How did it work with the Power supply cable?Do I require more thatn 3V?I tried also to make the followingower supply connected to the PCB and to short the blue and red...but no sound...no CA-42 in device manager.I don't know if it make sense i just thought that the RX and TX terminal of the CA-42 when connected will trigger the CA-42 to appear in Device Manager.But my conffusion is:how it works on the PCB connected.Do the 2 wires do another phenomena in that moment?
Thank You.
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Hard Drives & Storage
Overclock.net › Forums › Components › Hard Drives & Storage › Seagate Bricked Firmware Drive Fix (With Pics)