MadOCer

Member
  • Content count

    37
  • Joined

  • Last visited

Community Reputation

0 Neutral

About MadOCer

  1. BTW, found a solution to your firmware problem yet?
  2. Yep. I know : http://www.msfn.org/board/index.php?showto...807&st=1776 But you cannot "counterattack" against voodoo with some more voodoo , from what we know the answer to whatever problem kang roy is having is "a suffusion of yellow": http://www.thateden.co.uk/dirk/ there is no way to know if (choose one) a simple DIY solution exists a non-simple DYI solution exists a "professional only" solution exists AND if: any of the above include opening the drive or not unless we know what the problem is. jaclaz I didn't say he shouldn't try to see if there was a simple solution. In no way did I mean that. But, this was just meant as a warning. There are no known big firmware BUGs, AFAIK, for the Western Digital drives. I might be wrong, I just don't know of any. I'm no professional in this field. As you said, without further details from his side, any help will be a guessing game.
  3. The accuracy of your crystal ball is amazing! We don't even understand what the problem is and you already know that the drive has to be opened? Come on, kang roy has obviously some problems in expressing himself in English what he wants to say, (and he seems like attempting to start a data recovery business learning from MSFN as he posted in two days about three different make/model failing hard drives): http://www.msfn.org/board/index.php?showto...mp;#entry906885 http://www.msfn.org/board/index.php?showtopic=141594&hl= (besides the present thread) and some ununderstandable (at least for me) comments on data recovery related threads: http://www.msfn.org/board/index.php?showtopic=141448&hl= http://www.msfn.org/board/index.php?showtopic=141687&hl= the only advice we can give right now is: @kang roy Please try to express better what you have to say, try using an online translator from your language to English and viceversa, if noone can actually understand the problem, you will never have an adequate advice or hopefully solution. Where are you from? What is your native language? jaclaz You misunderstood my posting I'm afraid! All I said was that there's no simple solution to ANY hdd problem out there and that it MIGHT be that a pure software solution can't fix the problem. That's what I meant. I posted that, because it seems that after the Seagate desaster, a lot of poeple tend to think that there is a simple solution to all hdd failures.
  4. i'm sorry.... to overcome problems such as WDC is not detected in the BIOS, the sound head and Short PCBs, probably from among you have a solution,,, help please,,, with a tutorial,,, And who told you this was a common problem, fixable by some DIY solution that is easily followed? I can't remember reading much about WD drives showing these symptoms. So it might just be hardware problem of your particular drive, that is not easily fixed, but needs opening the drive and replaceing or repairing some of it's part inside.
  5. Maybe there is away around the detection problem.
  6. You read my post correctly. I was able to restore the functionality of the drive which i365 claimed was inaccessible. I was then able to backup all the data and flash the new firmware. Shame on i365. Very strange indeed! One would think that Seagate's own data recovery service would know how to recover the data on their own products, especially when only looking at the label (7200.11 SD15) should ring all alarm bells.
  7. Does the drive sound "normal", when it is powered on, or does it exhibit any scratching or clicking noise or something like that? I mean does it spin up, like it used to when it was still working OK? yes it definately spins up. no strange noises or anything. just cant access the drive. appreciate if you're around london and able to fix it. I'm sorry, but I'd have quite a long way to London, from Bavaria, Germany . BUT, and that's the good news, your drive should be recoverable once the connection works. And that should definitely be possible to accomplish. Good luck! Just offer the poeple some money. Something like 10-20 pounds and I'm sure there will be someone to assist you with this.
  8. If you intend to keep using the drive in the future, then there's no way around the firmware update. Or do you want to wait for the integrated self-bricking-feature to strike again, forcing you to repeat the steps to recover your data once again? But back up all your needed data before attempting the FW upgrade. You never know what happens, before it happens.
  9. Just for fun so to speak: Anyone knows more about, or already used the following command (from the full comand list)? Level 4 u: Rev 0001.0000, Overlay, SetSkSpeed, u[Opts],[skSpeed] Looks like the not supported AAM function to me. But I could be wrong. Isn't accoustic management setting the seek speed in values from 0x80 (dec 128) to 0xFE (dec 254)? Would really like to try that one. But I think I won't do it on one of my good drives. And unfortunately I don't really know what the "Opts" stands for and what value to use for "SkSpeed". I did open up a defective 7200.11 today though (turned out to have a defective head on the upper platter that made the drive not spin up correctly and emmit a horrible whine while trying to spin up), which I could use for those kind of tests. Of course given it still somehow works more or less after I reassemble it.
  10. Does the drive sound "normal", when it is powered on, or does it exhibit any scratching or clicking noise or something like that? I mean does it spin up, like it used to when it was still working OK?
  11. BTW, I just unpacked the Seagate flash files for my ES.2 drive and from the looks of it the error message about "wrong model" etc. could be pretty simply circumvented. Didn't try it yet, because I don't need to ATM, but as I said, it looks pretty simple.
  12. AFAIK, you can view a full command list, by typing "/C" on the first prompt and then "Q" afterwards. No guarantee though that it works. I remember having used that once some months ago. Try it, if you can risk a failure.
  13. As I said, you can always try to contact Seagate. They should be able AND WILLING, to support you, considering it was THEIR fault that these drives drop like flies. They should be able to get you either the program for your specific firmware, or a flash-program that doesn't check for the part number AND FW revision. Maybe you'll have to be quite persistent, though, to make them help you.
  14. You simply cannot use the standard flash tool on drives that have other firmware versions than the ones listed on the seagate page. If the drive is OEM, you have to contact the OEM for a flash upgrade tool. Or Seagate and ask them, if they are willing to help, given the circumstances.
  15. I thought rather about shortcutting the predriver of the motor. And that's why I first will try to apply the cardboard in the moment described at the russian page. Ther is at a 80% chance that it makes the same job as the jumper ;-). I thought you already did that as this is the common method. Good luck! I fully understand that you don't want to risk you data, at least not any more than necessary.