Jump to content

timha

Member
  • Posts

    14
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United States

Posts posted by timha

  1. Hello, after doing the good drive bad drive pcb switch. I successfully flashed the bad board on good drive to SD1A but after returning the now "good" board back to the bad disk it clicks 8 times on power up and stops. any ideas? did the drive get damaged?

    Wow...i thought this would work for everybody else...but just in case, i can see some mistakes people could make though..

    1. if you flash badpcb/gooddisk it should be the only hd in the computer, just in case your flashing the wrong hd ...haahahha :whistle:

    2. your trying to flash the goodpcb/baddisk instead of the badpcb/gooddisk ...just remember your fixing the bad pcb.

    3. you correctly flash the badpcb/gooddisk but do not swap it back to the original flavor badpcb/baddisk...

    this is a good fix though, i am looking at all my files right now and coming from the busy issue before.

    good luck

  2. some more details, the bad pcb/good drive is detected in the bios. although it hangs for ages at the bios.

    the firmware then boots and when i select option A to update the firmware, it thinks about it for while and then returns the error message

    error: specific model not found. st3500320as expected

    all help appreciated Vinicus

    Strange... If I plug only the PCB without the Disk I got your symptoms. Check if your Frankenstein disk is spinning (even with head beat; my case).

    Are you sure that your both ST3500340AS are identical and running SD1A firmware on the working one?

    both drives are defo identical, and I updated the good drive with the latest firmware. i then take the bad pcb and put it on the good drive. i then get the symptoms as described above.

    i should have also said that the good drive (with good pcb) isnt working 100%. it has another fault but it is working although it is running slow. this is a less common fault with these wastes of money!

    If i can add ,

    make sure your SD1A cd is good, i made mine with PowerIso and writing at x4, and i made sure all my HD 's in my tower were disconnected and the only one connected was the badpcb/good disk ....you press A in the flash area and wait .... and put badpcb/ to bad disk ....and you will see it resurrected.

    i happen to have 3 barracuda st300320AS, it would probably work on any two different models, when you swap the bad pcb to a good disk it is seen in the bios and that gets you half there.....flash the new firmware and your done....remember to flash the other hard disk as well when you swap back.. i used PowerISo to make the firmware cd....

    as a note i've been swapping that pcb back and forth and tinkering with it so much with that dang rs232 that it should be broke but it isnt, dont be scared of it use torx6 screwdriver , but dont break it either ....good to have my hd back

  3. Hey guys,

    ...its true the new fix is good...thanx Vinicius, i too was having issues with the hyperterminal....i dont reccomend for others to persue it...though at the time it was necessary as the firmware was not available....this is what i did as did Vinicius

    1. swap pcb boards on 2 like hd's ...flash the bad pcb with the new SD1 firmware

    2. swap back the pcb's

    voila !! full recovery from bsy hd with no LB0.

    this post is for real, my brick is fully recovered.....i know you all paid for the rs232, as did i, but it is a real hard fix compared to doing it this way

    as far as i know you do need to 7200.11's though .. .

    Should I just buy a new 7200.11, try this, then return it and give them an excuse to return it? Anyone here happen to be from orange county, CA? =/

    i happen to have 3 barracuda st300320AS, it would probably work on any two different models, when you swap the bad pcb to a good disk it is seen in the bios and that gets you half there.....flash the new firmware and your done....remember to flash the other hard disk as well when you swap back.. i used PowerISo to make the firmware cd....

    as a note i've been swapping that pcb back and forth and tinkering with it so much with that dang rs232 that it should be broke but it isnt, dont be scared of it use torx6 screwdriver , but dont break it either ....good to have my hd back

  4. Hey guys,

    ...its true the new fix is good...thanx Vinicius, i too was having issues with the hyperterminal....i dont reccomend for others to persue it...though at the time it was necessary as the firmware was not available....this is what i did as did Vinicius

    1. swap pcb boards on 2 like hd's ...flash the bad pcb with the new SD1 firmware

    2. swap back the pcb's

    voila !! full recovery from bsy hd with no LB0.

    this post is for real, my brick is fully recovered.....i know you all paid for the rs232, as did i, but it is a real hard fix compared to doing it this way

    as far as i know you do need to 7200.11's though .. .

  5. Hey guys,

    ...its true the new fix is good...thanx Vinicius, i too was having issues with the hyperterminal....i dont reccomend for others to persue it...though at the time it was necessary as the firmware was not available....this is what i did as did Vinicius

    1. swap pcb boards on 2 like hd's ...flash the bad pcb with the new SD1 firmware

    2. swap back the pcb's

    voila !! full recovery from bsy hd with no LB0.

  6. hey everybody,

    glad the fix is working out for everybody , i'm going to try it here in a day, thanks again to the guys who figured it out....

    what i was thinking though was that one thing we never documented with all the bricks was " how full were they at , at the time of failure, mine was at 450/500 gb when it died and i had it since last april 2008 primarily empty i guess.....was wondering if it becomes unrecognized when it reached a certain amount, or did we scratch that off the list before?

  7. FWIW, for my recovery the price I paid for my serial to sata cable + software was $500.

    Can you please post a picture of the Serial to SATA cable? I've never seen one of these before. :blink:

    Mine is not that straight forward. There's a separate console that connects to the PC via USB. The serial cable is then connected to the console. It's definitely something I could NOT put together. The repair kit I got came with this and a whole bunch of adapters. The documentation and support was a bit painful and patience is definitely needed.

    Someone suggested teaming up in our locales and splitting the cost of the kit. As I doubt Seagate is going to do anything about it (they can't, really. The liability alone in this economic climate?) I would say this is probably the easiest method for anybody who needs their data back. I myself already have a couple people online shipping their drives to me to unbrick. I called a couple of Data Recovery sites and the cheapest quote started at $1500 low priority. I don't mind referring to these guys if you've dropped your hard drive while it was on or flooded it in the basement but for a simple firmware fix that should never have been there in the first place it seems like using a chainsaw when all you need is a pocket knife.

    For what it's worth I know someone who's trying to get Italy up and running but no repair kit yet. I'm in Toronto, Canada with a kit and a rescued ST31000AS SD15.

    ---

    Rule #1 Always back up your data

    Rule #2 Always back up your data (This is a backup to Rule #1)

    hey FUZZBY,

    can you give us detail pics of what the hardware setup looks like, for some of us willing to tinker :hello: thanks

  8. Hmm.. all listed 7200.11 models coincidentally appear to have that 0,34% annualized failure rate.. 0,34% of how many drives in total would that be?

    Well, my drive 100% failed in 4 months, so that's and Annualized Failure Rate of 300% !! I Win !!

    Awwwsommmme !!! i think we should all throw in and get Fuzzy a WD Black as a first place drive, for real, that really is bad luck dude............

    and Laz , i seriously want to choke you out.....hahhahah....really.

  9. The best method to complain isn't the "S/N list", it is say the problem. Send email to your friends, you say that you have had the problem.

    Make backups if you already have these drives infected and not to buy more.

    So you will help to your friends and their friends too.

    Summary:

    1 .- The manufacturer make a virus "timebomb".

    2 .- To kidnap your data.

    3 .- To retrieve only two companies: A. and S. (other companies are intermediates) or the manufacturer.

    4 .- Or you pay the ransom or not you ever see photos of your travels, your marriage, your works, you docs, your videos, etc..

    5 .- They say that this is legal? The warranty "yes", the kidnap "no"!!!!!.

    I don't buy your theory; they lose far far much more knowingly shipping a defective product.

    Laz, u ignorant b***h i personally think they knew a year ago ,, worst yet they definitely knew before shipping out 1T and 1.5T , wait until all those poor saps poor all their 80gb's,60gb,100gb and combine them into the big one's , and then blammo....it will be ugly....sorry for calling you a b***h but dont ever assume, just look at chronological events...

  10. I haven't spoken to Timha about the dates, his hard drive may be some sort of terminator sent back from the future to unleash epic fail upon humanity... Which really wouldn't surprise me.

    Fixed:

    SerialNumber:Model:P/N:Firmware:DateCode:SiteCode:PurchaseDate:FailedDate:USername:Country Origin

    ======================================================================

    9QM7VZBP:ST3500320AS:9BX154-303:SD15:09146 (09/Oct/2008):KRATSG:Oct2008:24Dec2008:poolcarpet:Malaysia

    9QM6X90B:ST3500320AS:9BX154-303:SD15:09115 (17/Sep/2008):KRATSG:Oct2008:28Dec2008:DaftMule

    9QM6W2JE:ST3500320AS: - :SD15: - : - :5Dec2008:19Dec2008:DerSnoezie: Netherlands (no detect in bios)

    9QM4G4PK:ST3500320AS:9BX154-303:SD15:08503 (16/Jun/2008):KRATSG:Aug2008:Nov2008:dskbrk

    9QM3RWHJ:ST3500320AS:9BX154-568:SD81:08464 (20/May/2008):KRATSG:Aug2008:23Dec2008:ToKuRo:Chile (no detect in bios, reboot of death)

    9QM7KSQJ:ST3500320AS:9BX154-501:SD15:09134 (30/Sep/2008):KRATSG:28Oct2008:07Jan2009:jeroen__online

    9QM2MFS6:ST3500320AS:9BX154-303:SD15:08406 (10/Apr/2008):KRATSG:12Apr2008:23Dec2008:quattro150:Malaysia

    9QJ0XJ01:ST31000340AS:9BX158-303:SD15:08496 (12/Jun/2008):KRATSG:Aug/Sep2008:8Jan2009:Nichev

    9QM717SF:ST3500320AS:9BX154-303:SD15:09114 (16/Sep/2008):KRATSG:13Oct2008:14Dec2008:PrOdiGy1

    9QJ1LESR:ST31000340AS:9BX158-303:SD15:09063 (11/Ago/2008):KRATSG:Nov2008:27Dec2008:AVINNC

    9QJ1AGEV:ST31000340AS:9BX158-303:SD15:08515 (2/Jul/2008):KRATSG:Aug2008:4Jan2009:Ruddrage

    9QM6354J:ST3500820AS:9BX134-505:SD15:09084 (26/Ago/2008):KRATSG:July2008:20Dec2008:rainshower

    9QM33FL8:STM3500320AS:9GT154-325:MX15:08396 (03/Abr/2008):KRTASG:Sep2008:30Dec2008:fabio.cillo

    9QM*****:ST3500320AS:9BX154-303:SD15:08367 (14/Mar/2008):KRATSG:Dec2007:Dec2008:Death_Angel:Malaysia

    9QK*****:ST3750630AS:9BX146-621:HP24:08511 (21/Jun/2008):TK:Oct2008:7Jan2009:Taiketo

    5QJ*****:ST1000340AS:9BX158-303:SD15:09121 (20/Sep/2008):WUXISG:October2008:28Dec2008:Styleman

    9QM8DRHL:ST3500320AS:9BX154-303:SD15: - (13/Oct/2008):KRATSG:06Dec2008:24Dec2008:roadstarter

    9QM6****:ST3500320AS:9BX154-303:SD15:09076 (21Aug2008):KRATSG:15Oct2008:29Dec2008:labraticmp3

    9QM6****:ST3500320AS: - : SD15 - : - : Oct2008:2Jan2008:eli2k

    9QM5****:ST3500320AS:9BX154-303:SD15:09063 (11/Ago/2008):KRATSG:6Nov2008:27Nov2008:poim76

    9QM2CHR4:ST3500320AS:9BX154-303:SD15:08382 (23/Mar/2008):KRATSG:August-08:Nov-Dec-08:caba212

    9QJ15ZBN:ST31000340AS:9BX158-303:SD15:08496 (05/Jun/2008):KRATSG:July2008:26Dec2008:GrayGhost

    9QM27S5F:ST3500320AS:9BX154-303:SD15:08381:DEC 08:JAN 09: timha

    9QJ0****:ST31000340AS:9BX158-303:SD15:08495:KRATSG:Oct2008:02Jan2009:viniciusferrao:Brazil

    yes Nichev ,

    me and my barracuda are from the future, it is quite bleak, Seagate and their moderators (his name is Alan and his beeetchh Brad, or is it the other way) have taken over the world, they use Thailand as a homebase base, ....the future is dismal with absolutely no DATA to be had....where once we had 21Gb of tera patrick now we jerk-off to public television....we no longer have photos of our families we now have to rely on our kids stick figure drawings ...the Seagate future is quite bleak and BUSY

  11. Hi all and especially Fatlip if you are here,

    I would really like to know how to build the serial -> SATA interface to connect to the hard disk. I was searching more and more about this and I have found a document which lists down the exact steps/commands to free up the BSY mode. You DO NEED TO DISCONNECT the PCB from HDA before doing it, just as I suspected back in the Seagate forum.

    However, I'm not sure if the steps alone will totally free it up or it will leave it detectable by BIOS but with 0 size (the second problem faced by others). If it's the 0 size, then it's something else that we need to search for further, but at least we can unset the BSY mode.

    But I need to know how to connect to the SATA interface....

    hey poolcarpet,

    do you have a link to the document you mentioned ? i too am interested in building the interface and unlocking the bsy.

    thanks

×
×
  • Create New...