Confused07

I'm actually seeking professional help as opposed to software for DIY. The drive seems dead.

I'm looking for the best professional data recovery solution, I checked out this one: http://www.ontrackdatarecovery.ca/data-recovery-portal/ But I'm not able to find a lot of positive reviews which makes it uneasy for me. Preferably one that is within Canada. Thanks.

Ah well, I already consider the DIY jobs done for. I've been looking at the professional data recovery ones, might be a while until I have the money to pay for one of those. Over 1000+.

I don't know "which" clicking, one of the sources I read said it's because the header or whatever it is, is trying to access the platter's firmware and failing, the clicking is each time it tries and failing. I think it's somewhere between 8 - 10 times, I haven't plugged it back in. It detects as ST_M13FQBL, with 3.86GB of space. On Windows, it shows as a "Not Initialized" disk. It does sound like it spins up, then tries to read the platter firmware, after the clicking, it winds down.

Unfortunately there doesn't seem to be success in mine. When I first plugged it into the SATA Docking station I had, it made no clicks, and detected a new device. But it installed it like a USB Drive, and I couldn't access the data or view the total size of the drive. When I turned it off & on, nothing happened after that. So then I tried the USB cable method again, and I only got the black arrow in Hyper Terminal, when I put the drive back together and powered it on again, the clicking came back, and it detects as an unknown drive that's not initialized.

When I get the replacement PCB, should I try accessing the drive normally, or should try to communicate with it again through Hyper Terminal?

Okay, I've contacted OnePCBSolution.com, see if they can help. Hopefully I can buy a replacement board from them (exact match) and mail them my current one so they can do the donor transfer. EDIT: Here's the reply from OnePCBSolution: Will give it a shot, beats the last resort if it works out.

I tried the same cable on an old ST31000340AS, and it worked on Hyper Terminal. I got the, "F3 T>", message upon pressing CTRL+Z. But it won't work on my ST31500341AS, any idea as to why ?

Connecting the RX to TX cables directly, it did loop back the messages on the Putty screen. I was able to see what I was typing. When plugged correctly to the drive, a lot of times nothing happens. Sometimes on Hyper Terminal I can see what I'm typing, and if I press CTRL + Z, I would get a black arrow. Does this mean the issue is with the PCB?

I didn't actually read all 182 pages, the pages that I did read, gotta tell you, never saw one warning. But even so, I found this thread/forum after I already tried the PCB solution.

*Sigh* Unfortunately. I came across this thread & this forum by googling the problem I was directed to about half way through this thread. I didn't venture out beyond that. I only made an account and began posting after I already done testing. Other google results suggested trying to switch the PCB, so that's what I did. I'm sure many others experiencing the HD faults are discovering this place just the same. They're landing in the middle of this thread.

I aimed at the right pins at first but when it didn't work I thought they could've been wrong, and read elsewhere that I'd have to trial & error. I already tried a board swapped, I have multiple of these units. Which BTW, are being replaced by Western Digitals now. But I really need the data off this one I'll try the loopback test and will report how that goes. EDIT: I'm a little confused by the loop back. I have the wires connected to these pins, so does the RX & TX just need to be touching each other? Should the ground be plugged in?

Hi, I need some help please. I have a ST31500341AS, Barracuda 7200.11, Firmware: CC1H I went through all the steps, I've actually done this before succesfully to recover from a Seagate 1TB, unfortunately it's not working out the same this time around. On either Hyper Terminal or Putty, CTRL+Z doesn't seem to do anything. I've tried it with caps lock on & off. I've tried every pin combination as well. Someone please help