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 23

post #221 of 279
has anyone been able to upgrade to the newest fixed firmware since unbricking? I unbricked mine a few months ago but still haven't been able to get the firmware to update on the drives, it goes through the DOS-based process then when I try to scan for ata drives it there are none detected that are compatible with the firmware update?

The drives I am trying to update are the 1 TB's(stm31000340as). They are still working as I type this.



ient55.jpg
Edited by SM0k3 - 9/22/12 at 6:18am
Da Beast
(13 items)
 
  
CPUMotherboardGraphicsRAM
i7 2600k @ 4.6ghz Asus P8Z68-V/GEN3 PNY GTX 570 -- 950/1900/2000 @ 1.100v 8GB Corsair XMS3 DDR3-1600 
Hard DriveOSMonitorKeyboard
2x Maxtor 1TB Sata Windows 7 64bit 24" samsung 2433bw ZBoard 
PowerCaseMouseMouse Pad
Corsair 850w Antec Nine Hundred Generic Black optical black mat 
  hide details  
Reply
Da Beast
(13 items)
 
  
CPUMotherboardGraphicsRAM
i7 2600k @ 4.6ghz Asus P8Z68-V/GEN3 PNY GTX 570 -- 950/1900/2000 @ 1.100v 8GB Corsair XMS3 DDR3-1600 
Hard DriveOSMonitorKeyboard
2x Maxtor 1TB Sata Windows 7 64bit 24" samsung 2433bw ZBoard 
PowerCaseMouseMouse Pad
Corsair 850w Antec Nine Hundred Generic Black optical black mat 
  hide details  
Reply
post #222 of 279
I get this after I do "U"

DiagError 00006008
Spin Error
Elapsed Time 32.172 secs
R/W Status 2 R/W Error 84150180
F3 2>

Any thoughts?
post #223 of 279
Quote:
Originally Posted by SM0k3 View Post

has anyone been able to upgrade to the newest fixed firmware since unbricking? I unbricked mine a few months ago but still haven't been able to get the firmware to update on the drives, it goes through the DOS-based process then when I try to scan for ata drives it there are none detected that are compatible with the firmware update?
The drives I am trying to update are the 1 TB's(stm31000340as). They are still working as I type this.
ient55.jpg
i couldnt update my drives with this system as well
so i used an older system (Asus Maximus III Formula board) and i could update it
seems like you cant use chipset drivers to make it work, it just doesnt work with the new motherboards
i recommend to use an older system
post #224 of 279
Quote:
Originally Posted by [T]yphoon View Post

i couldnt update my drives with this system as well
so i used an older system (Asus Maximus III Formula board) and i could update it
seems like you cant use chipset drivers to make it work, it just doesnt work with the new motherboards
i recommend to use an older system

I figured it out.

I had to change the SATA Configuration to IDE Mode instead of AHCI mode worked perfect that way, but one of the drives has developed the "click of death" so it's about time for replacements.
Da Beast
(13 items)
 
  
CPUMotherboardGraphicsRAM
i7 2600k @ 4.6ghz Asus P8Z68-V/GEN3 PNY GTX 570 -- 950/1900/2000 @ 1.100v 8GB Corsair XMS3 DDR3-1600 
Hard DriveOSMonitorKeyboard
2x Maxtor 1TB Sata Windows 7 64bit 24" samsung 2433bw ZBoard 
PowerCaseMouseMouse Pad
Corsair 850w Antec Nine Hundred Generic Black optical black mat 
  hide details  
Reply
Da Beast
(13 items)
 
  
CPUMotherboardGraphicsRAM
i7 2600k @ 4.6ghz Asus P8Z68-V/GEN3 PNY GTX 570 -- 950/1900/2000 @ 1.100v 8GB Corsair XMS3 DDR3-1600 
Hard DriveOSMonitorKeyboard
2x Maxtor 1TB Sata Windows 7 64bit 24" samsung 2433bw ZBoard 
PowerCaseMouseMouse Pad
Corsair 850w Antec Nine Hundred Generic Black optical black mat 
  hide details  
Reply
post #225 of 279
Okay people be nice now. I've been reading all over the internet about this BYS fix. I've bought DKU5 cable and I have drivers for it and everything. It even appears in device manager as COM3. I have bought female crimps and all that... I located GND, TX and RX on the cable .. nothing hard.. I connected TX to RX on HDD and RX to TX on HDD and GND to GND. I started Hyperterminal and did all that setting thing.. I tried to type CTRL+Z .. NO RESPONSE.. All I got was one black ARROW pointing to the right -->

I tried to switch their place but it was the same... What's the issue? I bought the cable a guy at YouTube linked and so on... I really need help with this... And now it is beeping when I connect the power cable to the drive..
post #226 of 279
I've done looping now again and I get communication BUT the hard drive starts to beep when I press CTRL+Z....HELP!mad.gif
Edited by NasSweden - 10/4/12 at 6:20am
post #227 of 279
Thanks for starting this thread!

Just a couple of notes from my recovery experience:
1. As per other posters, my CA-42 cable had blue, white and green wires, blue - connect to hdd gnd, green - to hdd tx , white - to hdd rx. I hacked off some pins from an old PC, but buying some might save someone a little bit of hassle.
2. My CA-42 connection to the hard drive wasn't very good, I had to kinda hold on to it, to ensure the pins where contacting...
3. In step 8, I wasn't sure whether or not I should power down the disk before removing the business card, and putting the screws back in, however, when I did that, I found that it wouldn't stop spinning... so I redid the steps and while the drive was still powered up, I pulled the card and put the screws in... I was afraid of frying the drive, but luckily nothing happened.
4. I did have to power down the drive in step 12 and wait 20 seconds... if I didn't do this, it wouldn't work!

Also, I would recommend doing this in a windows xp environment... I searched for quite some time for Prolific drivers that would work in win 7, but did not have any luck...

Thanks!
Edited by redpyl - 10/14/12 at 9:25am
post #228 of 279
I've lost faith in recovering the drive. Answer my question above please frown.gif
post #229 of 279
This is what I used: http://www.virtualvillage.com/usb-2-0-to-ttl-uart-module-serial-device-converter-6pin-bu2001-020.html (Note: This company SUCKS, it took more than 30 days to get to me and they constantly lied about its progress, YMMV)

I hooked it up per the instructions here RX -> TX and TX -> RX but it didn't work. I had to do RX -> RX and TX -> TX and then it got me in.

It took forever for me to get my data off. I did the above steps several times and was never able to get the drive to transfer. What I then did was upgraded to the latest firmware. Then I downloaded the seatools and ran a in depth scan (I forget what it's called). It only went so far and would crash, but after the crash, I was able to start transferring my files. I had to do that probably 20 times before I got everything off the drive, but in the end, it DID work.
post #230 of 279
I cannot even do that CTRL+Z thing otherwise it would go good.
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)