Jump to content

ViniciusFerrao

Member
  • Posts

    46
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    Brazil

Everything posted by ViniciusFerrao

  1. I don't want to be banned, but I would like to shout really bad words to dlethe. BTW: My drive is fixed by ME.
  2. Just ignore the flamewar people, this is just stupid. Gradius method saved all of us.
  3. Check serial numbers with seagate update utility and confirm if is equal.
  4. Man this is insane! You cannot do this! o.O
  5. 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 the "good" disk is not really good it may be the cause. Perhaps the timeout time increased and screwed up Firmware update. Don't know if this is correct but can have some sense.
  6. Question, after you swap the PCB boards, and then you boot up, does the BIOS detect the HDD? Hello, I'm very happy now because I figured this out. :) :) When you swap the boards the "old" board should boot the new drive with 0Mb. Since the disk is not made for that PCB. Will be normally detected on BIOS. After this fireup firmware update. You'll some errors like Cylinder 0, assuming 63! Something like this. But just ignore and flash the drive. After the power cycle reswap PCB's and use the old drive. It should be fixed from BSY and from LBA=0! See details of what I've done in the Solution Thread. []'s I'm wondering if one can get away with not even attaching the PCB to the disk of the 2nd drive. The reason being is that when they make these at the factory, they probably just attach the PCB to a test machine which flashes the PCB and runs electrical tests on it. This would be easier to make these in mass and then ship a box of these to another site that attaches the PCBs to the actual disk that some other factory site made in mass. Then both are run through another test machine to make sure the PCB and drive heads and platters work together. Thus, for those with the PCB having LBA=0 and BSY, try just removing the PCB from the drive, attach the PCB to the power and IDE/SATA cable, and then reflash with the new firmware. It'd be interesting to see if this works. Maybe the BIOS doesn't need to detect them. This will also eliminate the possible damaging of the disk heads and platter of the drive that is incompatible since there isn't one. The most that will happen is there is no spinup, 0 heads, 0MB/GB, 0 cylinders etc or this method won't work. The only thing that will happen is that you are SOL! The other possiblilty to bypass the BIOS is to attach just the PCB to an external SATA or IDE to USB adaptor cable (see sabrent adaptors or equiv) and power cable ,then plug in the USB and flash thru the USB port. I'm not sure if one can flash thru the USB even if updating working drives, but without any knowledge about it working or not, the only way to attain knowledge is to experiment.....and hopefully the BIOS is too stupid. Using just the PCB without the disk simply fail. Since the PCB doesn't find a disk it waits for timeout. And this take an eternity. When finally Seagate Firmware Update launches it reports NO DISK. []'s Seagate replied my email regarding data recovery for free... Hmmm it appers that they are really interested in a good reputation after this lamentable firmware episode. []'s
  7. Actually it goes, I tried that well before RS232 to TTL solution (2 weeks ago or more), and didn't work, so I give up and buyed the adapter instead. I must confess that drive never was the same after that (and I only did for around 10sec), it does some strange sounds in a while. I trully don't recommend this method, is like the mechanicals parts inside were forced, besides is playing with luck because the heads can always scratch the plates at that crucial moment. Is too risky only to avoid $20 (or less) bucks. Well since my RS232 to TTL isn't working as should be and I more worried about the data in the old disk I see no problems at all. And anyway, 2 weeks ago the SD1A firmware won't even exists for our drives!
  8. I don't recommend this method, the reading/writing HEAD goes crazy and can kill the platters by scratching them. Actually it didn't go crazy. It try to align 8 times (I counted), and then the head disables and stop. []'s
  9. 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?
  10. Question, after you swap the PCB boards, and then you boot up, does the BIOS detect the HDD? Hello, I'm very happy now because I figured this out. :) :) When you swap the boards the "old" board should boot the new drive with 0Mb. Since the disk is not made for that PCB. Will be normally detected on BIOS. After this fireup firmware update. You'll some errors like Cylinder 0, assuming 63! Something like this. But just ignore and flash the drive. After the power cycle reswap PCB's and use the old drive. It should be fixed from BSY and from LBA=0! See details of what I've done in the Solution Thread. []'s
  11. Is your drive detected on BIOS? It should be with 0Mb.
  12. Sorry but it will not. Every PCB is married with HDA, they're unique. Flashing will never works if your HD isn't recognized by BIOS at POST time. You need to unlock the drive with RS232 to TTL solution, or spend $500, or just RMA. There is no other solution. Gradius see my reply in Solution Thread... appears that my insane workarround really works!
  13. Hey! I'm very happy reading your post! So flashing the PCB with other drive really works! Thanks for your feedback! If you wanna try fire up Firmware update utility in the bad board with the functional disk.
  14. I have done this! Since my RS232 to TTL isn't working I swapped PCB's with identical ST31000340AS and flashed the bad board on a new disk, and worked flawlessly. []'s
  15. My drive is back simply with firmware update to SD1A!
  16. WOOOOOOOOOOOOOOO!!!! It's working! Okay okay! I don't even needed the s***ty RS232 to any s*** or whatever. When I saw the desperate of null console I do something insane. I have 2x ST31000340AS. So I swapped the PCB's and I let the hard disk head beat insanely. Ok... Fired up the Seagate Firmware Utility to SD1A, and the update was done! Using the old board in the new disk. Reswapped the PCB and when I boot the machine? ST31000340AS SD1A 1000Gb O.O Disk is FIXED!!! I can't BELIEVE! Only with Firmware update from Seagate All my files are back online!
  17. It's possible to see the LED: 000000CC Error even with bad RX and TX? I've made a Circuit with a MAX232N IC and 4x 1uF caps and 1x 10uF Cap. Just a note: if I plug only the PCB, I got ST31000340AS AD14. The strange part is this. If the drive is BSY, is this correct? BIOS can detect the drive in this state? Thanks.
  18. Need some help please I've mounted a RS232 to TTL circuit connect the TX and RX to terminal and OK! I saw the: LED: 000000CC 00XXXXXX error. So with the terminal open, I switched off the disk, removed just the screws near the engine and powered the board again. I simply cannot get in terminal. There's no output and CTRL+Z don't do a thing under HyperTerminal. I really need help! PS: Showing LED: 000000CC blabla means that my circuit is working, right? Thx
  19. So this one will work on a bricked ST31000340AS SD15? Sorry for asking such a noob question. Since you cannot see the drive you cannot update it.
  20. Where is the new SD1A update? Damnit, removed files at Seagate KB. I have a brand new SD15 1Tb disk here and want to upgrade but I got a memory exception with old SD1A update.
  21. Gladius2 method works? O.O Amagod! \o/
  22. My HD S/N appears as not affected in Seagate Check. ¬¬
  23. Really cool, anyway... translation: http://translate.google.com/translate?prev...history_state0=
  24. I have found a direct link do Salvation DATA! \o/ If someone want send-me a PM.
  25. I ask again! Someone with access to SalvationDATA Foruns get the update for me please? I don't have access but I need to send the upgrade to a restore shop so they can fix my drive. Someone? Please?
×
×
  • Create New...