Death_Angel

Member
  • Content count

    17
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Death_Angel

  1. Hi Gygun, From what I observed, it could be: 1. Did you download the correct firmware update from: This is mine (ST3500320AS): hxxp://www.seagate.com/staticfiles/support/downloads/firmware/MooseDT-SD1A-2D-8-16-32MB.ISO This should be yours (ST3750330AS): hxxp://www.seagate.com/staticfiles/support/downloads/firmware/MooseDT-SD1A-3D4D-16-32MB.ISO Can you confirm that you are using the correct ISO? 2. It could be that the MooseDT-SD1A-3D4D-16-32MB.ISO HDD detection is different from MooseDT-SD1A-2D-8-16-32MB.ISO. Maybe my method only works for HDD model using MooseDT-SD1A-2D-8-16-32MB.ISO. Thx for the data Death_Angel! I have 2 identical HD (seagate st3750330as), one of wich is dead (BSY), and the other one is new and with the firmware updated. I tried switching the PCB from one disk to another but when power up the hds (bios screen), the disc starts to make that particular "clicking sound" (cycling). And no luck with the detection. Now that i read your post i'll try your method. Any other advices are welcome. Thanks! EDIT: Death_Angel, i did exactly as u wrote When I power up the "Good HD" with the "Bad PCB" it starts making the "clicking". After 30 secs it stops. But no mater how many times I press "S" (to do a search in the firm utl), it doesn't recognize the HD. "0 devices found" I dont know what else can i do... Any suggestion are welcome
  2. Hi everyone, I have already successfully recovered my data without RS232 TTL or using Hyper Terminal. I did it using an identical HDD which was a ST3500320AS, SD15 Thailand. Ok, I successfully recovered my HDD (ST3500320AS, SD15 Thailand) with the help of my friend who has a working (ST3500320AS, SD15 Thailand). I told him about Seagate having firmware issue so he was afraid and he when to update his HDD. He was using MooseDT-SD1A-2D-8-16-32MB.ISO from hxxp://seagate.custkb.com/seagate/crm/selfservice/search.jsp?DocId=207951 (Change hxxp to http). So now his HDD is using the SD1A firmware and working fine. Below is quick reference that I'll be using in my guide. Y: Bad HDD (SD15), Bad PCB (SD15) * Z: Good HDD (SD1A), Bad PCB (SD15) * Place the Bad PCB on the updated HDD (SD1A, remember my friend's updated HDD) Connect Z to your computer but do not let BIOS detect the HDD by either disconnect the SATA or power cable or in my case using external power cable to turn on/off the HDD. If Z is connected and powered up, your HDD light will permanently stay on and may stuck at the BIOS screen. Make sure ONLY this HDD is connected to the computer. You won't want this firmware to screw up your other HDD. Insert the SD1A firmware CD and make sure BIOS boot from it. After the Firmware menu appears, reconnect Z and power on, and press 'S' to do a search for the HDD. When Z is powered up, you will hear clicking sound but its ok just let the firmware do the search. After some time the search will fail to find any matching HDD and returns to the menu screen but the clicking sound of the Z is gone. Do the search again by pressing 'S'. This time it will detect Z and return to the menu screen. Now, depending on your HDD model (I press 'A' for mine), press either 'A','B', or 'C' and cross your fingers while the update takes place. I waited about 10-15 minutes then message stating that firmware update was successful appears. Shutdown the computer and put back the Bad PCB on the Bad HDD thus making back Y. Boot up your OS and pray that your HDD is working again. Cheers! ================================================================ You may try different approach from the steps that I took but this is what I did and it worked for me.
  3. Hi everyone, Notice that everyone has been recovering their precious data. Good for all of you. Just want to know, can we still RMA this cursed hdd of ours after that or do we need to re-bricked them and use that as a reason to RMA?
  4. I suspect this thread will grow to at least 50 pages long before any new progress will be gained. Sorry I don't mean to shoot down Fatlip, pichi or any other people who are working on this issue. You guys are the best keep up the good work. Just stating that more and more new people will come in and say "Hi i am also a victim" or rant about how to destroy/curse/boycott Seagate. Thats good actually in a way to gather more people with the same problem but soon it will be difficult for us and new victims to actually follow the progress in how to recover our beloved data.
  5. Ok i'll start the Country Origin, poolcarpet,quattro150, i'll add yours as well. Then we'll know where do Seagate shipped all their defect products. This might be a problem for those who order online, since the hdd may come from anywhere in the world. 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 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 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 (??):KRATSG:Aug/Sep2008:8Jan2009:Nichev 9QM717SF:ST3500320AS:9BX154-303:SD15:09114:KRATSG:13Oct2008:14Dec2008:PrOdiGy1 9QJ1LESR:ST31000340AS:9BX158-303:SD15:09063:KRATSG:Nov2008:27Dec2008:AVINNC 9QJ1AGEV:ST31000340AS:9BX158-303:SD15:08515(2/Jul/2008):KRATSG:Aug2008:4Jan2009:Ruddrage 9QM6354J:ST3500820AS:9BX134-505:SD15:09084:KRATSG:July2008:20Dec2008:rainshower 9QM33FL8:STM3500320AS:9GT154-325:MX15:08396:KRTASG:Sep2008:30Dec2008:fabio.cillo 9QM*****:ST3500320AS:9BX154-303:SD15:08367:KRATSG:Dec2007:Dec2008:Death_Angel:Malaysia 9QK*****:ST3750630AS:9BX146-621:HP24:08511:TK:Oct2008:7Jan2009:Taiketo 5QJ*****:ST1000340AS:9BX158-303:SD15:09121: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
  6. Oh s***, i have one ST31000340AS:9BX158-303:SD15:CHINA bought on the last week on Dec 2008. I hope it won't die on me, but i only use it for external backup purpose only.
  7. poolcarpet, you're the hero. We need to make this matter more publicize like writing to local newspaper (In-Tech@Star, Malaysia perhaps) and once this matter can no longer be kept by Seagate, then perhaps they might do something. Imagine their shareholders found out about this mass firmware defects hdds. Expose their ugly head to the world. Say, is there any progress on getting our precious data back?
  8. KRATSG seems to be from Thailand, Korat Factory. Just search Seagate Thailand. Maybe someone can question the people there on the problem? Add my HD information below: SerialNumber:Model:P/N:Firmware:DateCode:SiteCode:PurchaseDate:FailedDate:USername =========================================================== 9QM7VZBP:ST3500320AS:9BX154-303:SD15:09146 (09/Oct/2008):KRATSG:Oct2008:24Dec2008:poolcarpet 9QM6X90B:ST3500320AS:9BX154-303:SD15:09115 (17/Sep/2008):KRATSG:Oct2008:28Dec2008:DaftMule 9QM6W2JE:ST3500320AS: - :SD15: - : - :5Dec2008:19Dec2008:DerSnoezie 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 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 9QJ0XJ01:ST31000340AS:9BX158-303:SD15:08496 (??):KRATSG:Aug/Sep2008:8Jan2009:Nichev 9QM717SF:ST3500320AS:9BX154-303:SD15:09114:KRATSG:13Oct2008:14Dec2008:PrOdiGy1 9QJ1LESR:ST31000340AS:9BX158-303:SD15:09063:KRATSG:Nov2008:27Dec2008:AVINNC 9QJ1AGEV:ST31000340AS:9BX158-303:SD15:08515(2/Jul/2008):KRATSG:Aug2008:Dec2008:Ruddrage 9QM6354J:ST3500820AS:9BX134-505:SD15:09084:KRATSG:July2008:20Dec2008:rainshower 9QM33FL8:STM3500320AS:9GT154-325:MX15:08396:KRTASG:Sep2008:30Dec2008:fabio.cillo 9QM*****:ST3500320AS:9BX154-303:SD15:08367:KRATSG:Dec2007:Dec2008:Death_Angel I don't think the last 5 digit of my serial matters in this case. haha, fabio.cillo, you broken the firmware combo chain. I guess my date of purchase is the earliest among all, I bought on Dec 2007 PC fair.
  9. Hmm... so it happens in Nov 08, Dec 08, Jan 09, anymore?
  10. Mine happen between Nov and Dec. I realize this as well, so i though its a timebomb issue. I tried changing the BIOS clock to a few months back and connect the hdd again but still cannot detect. I guess what is bombed is bombed. Wish I could time travel back and backup my data.
  11. Does your computer hdd led stay constantly on all the time when this hdd is plugged in?
  12. I wonder if this affects China version of these models? I have two China ones, a 1TB and a 500GB. I hope they won't experience the same problem as the Thailand one. Any of you guys out there, having this problem and is NOT made in Thailand?
  13. Hmm, sound promising, anyone willing to use their hdd as a guinea pig?
  14. Fuzzy_3D, Where did you get that RS232 part?
  15. To hoggiee, Are you sure they charge only RM700-800 for recovering data from hdd with this problem? What method are they using? May I know what is the name of the company and how to contact them?