[WeatherPaparazzi]

DUDE, hooked it back up to the HDA, It's coming back to life now with the power hooked up from the power supply from the computer!!!

I finally got it to say

F3 T>

LED:000000CC FAddr:0024A051

I will be reviewing the older posts to figure out what to do from here.

THANK YOU, YOU ROCK!!!

And I know there are others that have to be having this same problem so I think this will help since this was a long part of several pages of this topic.

If I can get my data back, it will save my life!!!

[pichi]

WeatherPaparazzi, on Feb 5 2009, 08:37 AM, said:

DUDE, hooked it back up to the HDA, It's coming back to life now with the power hooked up from the power supply from the computer!!!

I finally got it to say

F3 T>

LED:000000CC FAddr:0024A051

I will be reviewing the older posts to figure out what to do from here.

THANK YOU, YOU ROCK!!!

And I know there are others that have to be having this same problem so I think this will help since this was a long part of several pages of this topic.

If I can get my data back, it will save my life!!!

You have BSY and LBA0 problems. First: You need unmount your PCB with torx 6 screwdriver to repair BSY problem.

[WeatherPaparazzi]

SUCCESS, YES IT WORKS!!!!!!!

HAPPY HAPPY JOY JOY
HAPPY HAPPY JOY JOY
HAPPY HAPPY JOY JOY

Thanks you Aviko for helping me out!!!!!

You just saved my life!!! Seriously!!! I am a freelance videographer on a tight budget and this drive had all of my best raw storm chasing footage from 2008 on it that I thought was lost forever.

I was in the middle of backing everything up and building a raid setup to house all the files when this thing crashed.

So thank you AVIKO for taking the ball on this and holding my hand to get this to work. And thank you to Gradius2 for starting this topic in the first place. You all get some major credit for helping everyone out to put this thing together.

So, for future readers here is what happened to me and!! what I did to fix it thanks to the help from this forum.

If you get the ARROW, you need to follow AVIKO's advice and add in the second ground.

I used an older laptop that we had in storage that had an RS232 port and took the face plate off the RS232 TTL board and plugged it right into the port on the back of the computer.

If you still can't get the board to talk to you in hyper terminal, hook up the board to the power supply in the computer and the 3v power supply on the RS232 TTL board and then start hyper terminal You should get the real text on the screen that Aviko and the rest are talking about.

NOTE, when I hooked this up to the power supply in my computer, I pulled the SATA and power cables off of all the other drives so I did not risk hurting any more data when I tried this.

I'm back up and running and copying all the data over to a 1tb western digital USB drive.

THANK YOU GUYS!!!!!

This post has been edited by WeatherPaparazzi: 05 February 2009 - 02:29 AM

[basicguy]

aviko, on Feb 5 2009, 04:08 AM, said:

connect wire from pin 3 in terminal socket to gnd of rs232ttl board. next time read carefully what i suggest. I'm wonder when Gradius will fix his tutorial and add this 3rd wire. come on guys this is so boring explaining it all time. noone listens if its not on 1st post

I'm getting the same arrow -> and would like a bit of confirmation if possible, please.

Where you say 'pin 3 in terminal socket' - do you mean pin 3 on the seagate PCB?

[WeatherPaparazzi]

basicguy, on Feb 5 2009, 07:29 AM, said:

aviko, on Feb 5 2009, 04:08 AM, said:

connect wire from pin 3 in terminal socket to gnd of rs232ttl board. next time read carefully what i suggest. I'm wonder when Gradius will fix his tutorial and add this 3rd wire. come on guys this is so boring explaining it all time. noone listens if its not on 1st post

I'm getting the same arrow -> and would like a bit of confirmation if possible, please.

Where you say 'pin 3 in terminal socket' - do you mean pin 3 on the seagate PCB?

Pin 3 on the PCB needs to be grounded. I just used the ground from the RS232 TTL power source (3.3v) and made a third jumper wire to go to the third pin on the PCB.

Then per Aviko, I then with the power supply off to the computer plugged in the power from the PS to the HDA with PCB attached like normal but no SATA cable and turned the power on to the computer PS.

Then I put the battery to the 3.3v into the holder to power the RS232 TTL with everything hooked up to my computer serial port and hit connect in hyper termial.

I went from the farking arrow to the actual text.

Once I did that, I knew I had the right setup and everything was talking.

Then turned off hyper terminal, turned off the computer PS (CPS) and pulled out the battery from the TTL board.

THEN I removed the PCB and put thick paper under BOTH the contacts and then replaced most of the screws except for the one that goes to the motor and the PCB board to HDA.

Then I restarted the CPS and then put the battery back in and restarted hyper terminal and then followed the instructions to fix the BSY HDA problems.

Then I felt whole again because this saved my arse big time!

[maxjix]

HELP ~~~

I disconnect PCB board from HDA

and

F3 T>/2 (enter)

F3 2>z (enter)

LED:000000CC FAddr:0025BF67
LED:000000CC FAddr:0025BF67
LED:000000CC FAddr:0025BF67
LED:000000CC FAddr:0025BF67

and not response

any idea ?

help ~~~

[aviko]

maxjix, on Feb 5 2009, 03:52 PM, said:

HELP ~~~

I disconnect PCB board from HDA

and

F3 T>/2 (enter)

F3 2>z (enter)

LED:000000CC FAddr:0025BF67
LED:000000CC FAddr:0025BF67
LED:000000CC FAddr:0025BF67
LED:000000CC FAddr:0025BF67

and not response

any idea ?

help ~~~

ehhhh try Z not z and wear glasses

[bp2411]

maxjix I had the same problem as you mine was happening because I was typing the commands in wrong.

[PoTTeRKaTz]

bp2411, on Feb 5 2009, 02:59 PM, said:

maxjix I had the same problem as you mine was happening because I was typing the commands in wrong.

hi guys i might try this, as seagate still not getting back to me.
I cant see my HDD in windows or bios and the victoria prog that fatlip suggested worked first but now avg says its a trojan so i didnt even get to try it with my affected HDD.

I have a Mator diamondmax22 500gb STM3500320AS and aviko assures me that this technique here for the seagate will work for me also. as they're both the same drives. i cant see my HDD in windows or bios.

where can I get the parts I need in the UK. Any british people here who have done this with success post back here?

thanks

[basicguy]

WeatherPaparazzi, on Feb 5 2009, 01:44 PM, said:

basicguy, on Feb 5 2009, 07:29 AM, said:

aviko, on Feb 5 2009, 04:08 AM, said:

connect wire from pin 3 in terminal socket to gnd of rs232ttl board. next time read carefully what i suggest. I'm wonder when Gradius will fix his tutorial and add this 3rd wire. come on guys this is so boring explaining it all time. noone listens if its not on 1st post

I'm getting the same arrow -> and would like a bit of confirmation if possible, please.

Where you say 'pin 3 in terminal socket' - do you mean pin 3 on the seagate PCB?

Pin 3 on the PCB needs to be grounded. I just used the ground from the RS232 TTL power source (3.3v) and made a third jumper wire to go to the third pin on the PCB.

Then per Aviko, I then with the power supply off to the computer plugged in the power from the PS to the HDA with PCB attached like normal but no SATA cable and turned the power on to the computer PS.

Then I put the battery to the 3.3v into the holder to power the RS232 TTL with everything hooked up to my computer serial port and hit connect in hyper termial.

I went from the farking arrow to the actual text.

Once I did that, I knew I had the right setup and everything was talking.

Then turned off hyper terminal, turned off the computer PS (CPS) and pulled out the battery from the TTL board.

THEN I removed the PCB and put thick paper under BOTH the contacts and then replaced most of the screws except for the one that goes to the motor and the PCB board to HDA.

Then I restarted the CPS and then put the battery back in and restarted hyper terminal and then followed the instructions to fix the BSY HDA problems.

Then I felt whole again because this saved my arse big time!

I tried this...


and am still getting that same bloody arrow. Zero response from the terminal. This is the 2nd RS232-TTL adaptor I have tried now.

I have just found out that the owner of the drive tried to update the firmware. Apparently the update found the drive (LBA 0) and continued with the update - the firmware I get back from the diagnostics is: SD1A. Is the drive now unrecovable - and how come the firmware update went through anyway, without apparently fixing the drive?

This post has been edited by basicguy: 05 February 2009 - 09:23 AM

[bp2411]

PoTTeRKaTz, on Feb 5 2009, 03:14 PM, said:

bp2411, on Feb 5 2009, 02:59 PM, said:

maxjix I had the same problem as you mine was happening because I was typing the commands in wrong.

hi guys i might try this, as seagate still not getting back to me.
I cant see my HDD in windows or bios and the victoria prog that fatlip suggested worked first but now avg says its a trojan so i didnt even get to try it with my affected HDD.

I have a Mator diamondmax22 500gb STM3500320AS and aviko assures me that this technique here for the seagate will work for me also. as they're both the same drives. i cant see my HDD in windows or bios.

where can I get the parts I need in the UK. Any british people here who have done this with success post back here?

thanks

Im British and I done it successfully had a bit of a problem at first but a member on here "Anth" guided me through it whos also from GB. He recommended me a 3210 data cable (must be a manual switch 1 not auto) I bought 1 of these which was listed as manual but was an auto switching cable so it was no good so Anth sent me a cable he had. I just used the RX & TX and powered the hdd from another pc psu.

[Laz]

basicguy, on Feb 5 2009, 10:19 AM, said:

and am still getting that same bloody arrow. Zero response from the terminal. This is the 2nd RS232-TTL adaptor I have tried now.

I have just found out that the owner of the drive tried to update the firmware. Apparently the update found the drive (LBA 0) and continued with the update - the firmware I get back from the diagnostics is: SD1A. Is the drive now unrecovable - and how come the firmware update went through anyway, without apparently fixing the drive?

you can communicate with the drive via diagnostics ? the seagate iso ?

[jp77]

Please help me!!!! see the pic...



What Can I do?

[basicguy]

Laz, on Feb 5 2009, 06:32 PM, said:

basicguy, on Feb 5 2009, 10:19 AM, said:

and am still getting that same bloody arrow. Zero response from the terminal. This is the 2nd RS232-TTL adaptor I have tried now.

I have just found out that the owner of the drive tried to update the firmware. Apparently the update found the drive (LBA 0) and continued with the update - the firmware I get back from the diagnostics is: SD1A. Is the drive now unrecovable - and how come the firmware update went through anyway, without apparently fixing the drive?

you can communicate with the drive via diagnostics ? the seagate iso ?

Negative. My BIOS finds the drive intermitently - 1 in 5 reboots and always with LB0 - and when I tested the Firmware update disk made from the "MooseDT-SD1A-3D4D-16-32MB.ISO" it displays the current firmware as SD1A... so I'm assuming that the update went through at some point. He told me that he'd tried it several times!
I still cannot make any kind of connection with the hard disk via TTL - despite following the instructions to the letter. I have tried 2 TTL Convertors and 1 Nokia Cable (3210) with the same negative results. The only on-screen response has been that arrow. (Not the '>' cursor)

[aviko]

basicguy, on Feb 5 2009, 09:25 PM, said:

Laz, on Feb 5 2009, 06:32 PM, said:

basicguy, on Feb 5 2009, 10:19 AM, said:

and am still getting that same bloody arrow. Zero response from the terminal. This is the 2nd RS232-TTL adaptor I have tried now.

I have just found out that the owner of the drive tried to update the firmware. Apparently the update found the drive (LBA 0) and continued with the update - the firmware I get back from the diagnostics is: SD1A. Is the drive now unrecovable - and how come the firmware update went through anyway, without apparently fixing the drive?

you can communicate with the drive via diagnostics ? the seagate iso ?

Negative. My BIOS finds the drive intermitently - 1 in 5 reboots and always with LB0 - and when I tested the Firmware update disk made from the "MooseDT-SD1A-3D4D-16-32MB.ISO" it displays the current firmware as SD1A... so I'm assuming that the update went through at some point. He told me that he'd tried it several times!
I still cannot make any kind of connection with the hard disk via TTL - despite following the instructions to the letter. I have tried 2 TTL Convertors and 1 Nokia Cable (3210) with the same negative results. The only on-screen response has been that arrow. (Not the '>' cursor)

how about downgrade it to AD15 ? when you connect to terminal you have only pcb or disk with pcb ?

[dskbrk]

jp77, on Feb 5 2009, 03:18 PM, said:

Please help me!!!! see the pic...



What Can I do?

I hope you removed the isolation before giving U command...

[aviko]

jp77, on Feb 5 2009, 09:18 PM, said:

Please help me!!!! see the pic...



What Can I do?

Here is what you can do:

Tell whats Model, F/W ? Do you have connected terminal to pcb or pcb with hdd?
What you do between send Z and U ? Describe everything. Screenshot doesnt tell much. As I think you did nothing after Z and before U.

[basicguy]

aviko, on Feb 5 2009, 08:30 PM, said:

basicguy, on Feb 5 2009, 09:25 PM, said:

Laz, on Feb 5 2009, 06:32 PM, said:

basicguy, on Feb 5 2009, 10:19 AM, said:

and am still getting that same bloody arrow. Zero response from the terminal. This is the 2nd RS232-TTL adaptor I have tried now.

I have just found out that the owner of the drive tried to update the firmware. Apparently the update found the drive (LBA 0) and continued with the update - the firmware I get back from the diagnostics is: SD1A. Is the drive now unrecovable - and how come the firmware update went through anyway, without apparently fixing the drive?

you can communicate with the drive via diagnostics ? the seagate iso ?

Negative. My BIOS finds the drive intermitently - 1 in 5 reboots and always with LB0 - and when I tested the Firmware update disk made from the "MooseDT-SD1A-3D4D-16-32MB.ISO" it displays the current firmware as SD1A... so I'm assuming that the update went through at some point. He told me that he'd tried it several times!
I still cannot make any kind of connection with the hard disk via TTL - despite following the instructions to the letter. I have tried 2 TTL Convertors and 1 Nokia Cable (3210) with the same negative results. The only on-screen response has been that arrow. (Not the '>' cursor)

how about downgrade it to AD15 ? when you connect to terminal you have only pcb or disk with pcb ?

I have tried - PCB totally detached, PCB Raised from motor contacts using non-conductive card & PCB attached.
I'll try and find a copy of the AD15 firmware. At this point, I am not holding out much hope. Could be other things that he's tried that I've not been told.

[jp77]

aviko, on Feb 5 2009, 09:36 PM, said:

jp77, on Feb 5 2009, 09:18 PM, said:

Please help me!!!! see the pic...



What Can I do?

Here is what you can do:

Tell whats Model, F/W ? Do you have connected terminal to pcb or pcb with hdd?
What you do between send Z and U ? Describe everything. Screenshot doesnt tell much. As I think you did nothing after Z and before U.

Ok, STM3500320AS firmware MX15 problem BSY error, HDD not recognized.
I have connected terminal to pcb (only).
Between Z and U I have simply mounted PCB on HDD with power connected.

[jls2]

Gradius/Aviko,

Firstly thanks for your efforts on this issue.

I performed all the steps as in the first post (Had BSY problem) .

after last command F3 T>m0,2,2,,,,,22 (enter)

the response i get is only 2 lines instead of 3 and says completed successfully in 0 seconds.

when i connect the drive to SATA, it's now recognized by BIOS, SMART test passes ok, but:

1. Can't boot from drive.
2. Can't install OS on drive, OS installation can't find and drives.
3. when connecting as secondary drive, I can see the drive in the device manager, but drive doesn't show up in active drives.

in all cases computer is extremely slow, and takes a long time to boot.

Any ideas?