aviko
Content Type
Profiles
Forums
Events
Posts posted by aviko
-
-
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.
0 -
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 ?
0 -
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
0 -
what is model and fw of that 1tb?
It's a ST31000340AS
Here is a photo of the drive. I'm also trying to do this on another computer now just to see if that makes a differance.
Try this. Mount pcb back on drive. Just as in normal work. After power up drive you should got something on terminal (CC) then you will know that everything is connected properly.
I have to go. Maybe my friend will guide you...
0 -
heh, so change tx with rx. yellow is TX from adapter so need to be connected to RX whis is pin1, white ir RX to adapter so needs to be connected to pin 2 , then pin 3 is gnd. if it will not work i think i am I-D-I-O-T or you are doing something wrong.
Nope, don't think your an id***. Just trying to narrow down where the fault is at my end. Your helping out big time
but the error is at this end since I get the same problem with both the good drive (500 gig) and the bad drive, the 1TB PCB.Ok so I switched the wires to the pins on the drive and now none of the lights come on. I'm at a loss and trying to review all the steps again and again.
what is model and fw of that 1tb?
0 -
When new firmware SD1A fails, you will be at point when rat race started.
Aviko,
Ok, I'm making progress but I think I might have still one more issue. The Cable.
Now the lights come on to the rs232ttl board since I hooked the third cable up to the ground. This did not happen before.
When hook the rs232ttl to the serial port, the green tx light goes out.
When I also hook the rs232ttl board up to the null modem cable I have, the light goes out.
It still does not talk to the PCB.
I did not hook up the main power supply from the computer yet as I wanted to make sure it would at least talk to the PCB. Any ideas?
EDIT I also hooked this up to another 500 gig drive and still does not talk to the drive via terminal.
heh, so change tx with rx. yellow is TX from adapter so need to be connected to RX whis is pin1, white ir RX to adapter so needs to be connected to pin 2 , then pin 3 is gnd. if it will not work i think i am I-D-I-O-T or you are doing something wrong.
Maybe you have any Seagate drive older that 7200.11 ?
0 -
Here is something interesting to think about.
The Bios would not see the drive but get this, when I took the PCB off the HDA and hooked the PCB up to the computer just to see what would happen (yes I'm in fark it mode now) the Bios saw the drive.
It was a 0GB hard drive but the Bios saw the PCB.
Now with the Zero Gig drive on the PCB, could one do the upgrade from seagate without the HDA hooked up and then just attach the HDA to the PCB after the firmware upgrade?
I noticed that about recognizing only pcb by bios with 0lba issue. Im too lazy to search my posts and insert link to it. But finally I searched HERE i noticed this
no you cant, firmware upgrade works on working drive. id applies to pcb and service area which is on platters. But I REALLY suggest NOT to upgrade firmware. In new terminal can be locked. If main reason to upgrade firmware was to prevent issues which this topic is all about. So what? If you already fixed it once, you will fix it again in future if its needed.
When new firmware SD1A fails, you will be at point when all this rat race started.
HEH First victim, and unfortunately not last. its in polish but all know how to use google translator.
translated:
Post 05 Feb 2009 03:02 Seagate 7200.11 after update to SD1A not detected in the terminalWelcome
Days ago has failed me hdd firmware SD15 from st3500320as known as BSY. After you've built the system I fixed this problem without losing data, and I did update to SD1A. Hard work week and again there was an error BSY. To fix this problem as before, hdd connected to the same device as the first time, however, Hyper Terminal did not react and did not display any information. Hence my question: Does anyone met with this problem after firmware update the drive is read at a terminal?
I really considering start to play lotto or sth.
0 -
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
So, this is just as simple as make a third wire from the ground on the RS232 Board where the power is connected and connect that third wire to the ground pin on the PCB. Thats It? That Simple?
yep.
noticed here noone listen
15 bucks for this s***? LOL Hi end converter
as in cheapest COM cables for siemens C250 -
I still get the Arrow Yes, a Arrow and I have pictures and screen caps.
I purchased 2 different RS232 TTL boards with the second being from the company in first post of this topic.
I can't get the terminal to talk to the hard drive. I also tried a second seagate drive that has the same firmware (SD15) and still nothing.
NOTE, I do not have the RS232 TTL setup hooked up via cable. This is connected straight to the back of the laptop using Hyper Terminal. I tried it with a Null Modem Cable and could not get anything ether.
Here is the whole setup powered by the two AA.
Here is a close up of the RS232TTL that I bought.
Here is the pins and cables hooked up to the PCB
And here is the Farking Arrow on the screen. Arrow, Not > but ARROW. Sorry getting p***ed off that I can't get any further then this step of the process.
I have a ton of video stuff for work on this drive and I was in the middle of backing it up when it crashed into BSY from what I can tell.
HELP, at my wits end here.
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
0 -
Drive is busy example, not solution: drive ST3500320AS SD15
remove 3 screws nearest heads connector, motor connected, put something between pcb and hda to lift pcb and prevent contact.
power on, wait until drive stops motor, if you dont wait at this moment you got 000000CE error after next command
(ctrl+z)
F3 T>/2
F3 2>Z
Spin Down Complete
Elapsed Time 0.146 msecs
remove isolation and mount pcb as normal
F3 2>U
Spin Up Complete
Elapsed Time 6.864 secs
this part is not necessary, just checking is everything ok, use when first try fails (F712 work only on 500g 7200.11 with firmware SD15, when you updated f/w just skip this partF3 2>/
F3 T>F712
Byte:0712: RealTimeUpdatedFlags = 00 00
Byte:0712: Bit:0, HPA_SET_BY_SETMAX = 0
Byte:0712: Bit:1, HPA_SET_BY_SETMAX_EXT = 0
Byte:0712: Bit:2, DCO_SET_ACTIVE = 0
Byte:0712: Bit:3, CONGEN_READ_FROM_MEDIA = 0 <- configuration not loaded from surface
F3 T>F,,22
Drive Configuration restored to defaults.
F3 T>F712
Byte:0712: RealTimeUpdatedFlags = 08 00
Byte:0712: Bit:0, HPA_SET_BY_SETMAX = 0
Byte:0712: Bit:1, HPA_SET_BY_SETMAX_EXT = 0
Byte:0712: Bit:2, DCO_SET_ACTIVE = 0
Byte:0712: Bit:3, CONGEN_READ_FROM_MEDIA = 1 <- done
F3 T3>/1
F3 1>N1
F3 1>/
F3 T>m0,2,2,0,0,0,0,22
Max Wr Retries = 00, Max Rd Retries = 00, Max ECC T-Level = 00, Max Certify Rewrite Retries = 0000
User Partition Format 5% complete, Zone 00, Pass 00, LBA 00008DED, ErrCode 00000080, Elapsed Time 0 mins 05 secs
User Partition Format Successful - Elapsed Time 0 mins 05 secs
F3 T>
(finished, power off, connect disk to pc and check your data)
when, finally, my HD will communicate with HyTerm I think I will follow the instruction above... but is all that sequence does with something between pcb and hda?
Overlooked this step, I thought it was obvious. You need to remove isolation before spin up. (U command)
0 -
First I have removed my slightly nasty post I made a few days back about aviko. I apologize.
It did look like he was provoking a flamewar, but after being away for a few days, I have returned to see all the helpful posts he has made.
Sorry Aviko! (PS:where were you 2 months ago when this all started?
)2 months ago I had a lot work I havent time for anything else.
(Edit due to violation of the arrangements in the contract of employment)
0 -
-
Can anyone provide me with the following info about the Nokia 3210 cable:
1. The NKI 3210 cable has 4 pins - anyone know which is RX/TX?
2. Anyone know where I can get the drivers for this cable (if they are, in fact required)?
Thanks in advance.
http://pinouts.ru/CellularPhones-Nokia/nok...10_pinout.shtml
0 -
I've read all the stuff on that topic. The 2 solutions are nearly identical, but the differences are not only the ones you list : one isolates the heads, one the motor, and that is pretty much a difference.
I just need a working solution, period.
The aviko one, taking in account only the commands, seems to be less disruptive, but I really don't know which part should be isolated, motor or heads. It's impossible to get the truth between 2 people whose words to each other are insults and "you are all wrong".
Why do they fight like that ? The only result of all this will be in people's mind : "DO NOT TRUST DATA RECOVERY COMPANIES, THEY'LL TRY TO FOOL YOU IN SAYING THAT THE COMPETITOR IS LYING".
I really want to hear (or read) what is wrong in version which I suggest. Everyone who asked me got answer based on my knowledge as best as I could. All i wanted was information about real author who published these commands. Yura (also known as Okzo) worked really hard for last months to find out how to solve problem with that black series of seagate. All people who succesfully fixed own disks used commands which he publish. Of course there are commercial solutions which was developed and you can buy it or go to someone who buyed it. They worked independly and noone (as I know) grab solution from another. I am really sad because all that happened here. So much prosecution by one guy to another. Yura decided to publish these command with his own motives. I dont want to judge him is that good or not. Personally, as I work in DR company, I have much less cases with these disk after solution was published. Solution spreaded in internet and now everyone who search enough can find it and try to solve his problem. I tryed to aware you there are sifnificant errors in solution which Gradius copied and pasted here. I dont want to judge him too. He posted (or pasted) here this tutorial. Good for him. Many people could read it and fix bricked drive. He did much work too, but when someone quote another person it is nice (and should) to inform about source. Initialy he did it, but someday removed this info. Then many people who knows truth (including me) decided to something. It was not fair to pretend as author this tutorial. He compiled it and give in pill. But this pill should be good at least as in source was good. It wasnt, I tryed to change it but anything that I tryed to say was challenged by him that his tutorial is best and the only. Well if anyone who tryed "his" tutorial didnt get good results can try to contact me by instant messenger, Im using few it should be enough, all is in my profile. Thank you for reading my post to the end because I think it is my last one here. Good luck with your data. As few posts appear while i write this text I will give you all last advice. Isolating motor contacts prevents opening terminal in ES.2 and as I see new all versions of firmware rest of drives based on F3 architecture. See ya!
0 -
Thank you, very kind!
Now I know my new chinese cable is not working!
:realmad: take a picture, can you see any electronics or its sealed in rubber ?
0 -
another question on CA-42.
Once the driver installed is there always 3V on tx/rx or only when HTerminal and connection is on?
Someone could test it for me?
Thanks.
tested, i my cable (which is installed as OTi U&SB-to-Serial Comm Port) gnd - rx = 3,021, gnd - tx = 2,403
no matter is terminal connected or not. always.
0 -
...anyway, the RS232-TTL adaptor turned out to be dead but I did manage to find a nokia 3210 fbus data cable. Couple of questions:
1. The Nokia cable has 4 pins - which are TX/RX - or how can I determine this?
2. Do I need the drivers for the nokia 3210 fbus data cable?
Thanks in advance.
If its USB you will need drivers. cable must be installed as COM port. If its connected via COM in PC - no drivers.
fourth wire is mbus which is not used here.
If DCU-65 is for sony ericsson and after plug to pc installs as usb-to-serial it will work.
pinout can be checked here just look what collors are soldered to pins rx tx and ground
0 -
And finally before commands:
That's the head motor, nothing to do with SPIN motor.
aviko is just trying to discredit a proven fine guide.
We all have enough of it.
If you see, those guys have just 1 to 3 post max, and this is why they don't know this dirty play aviko is doing.
If he was right since start, he should just started long ago his own topic (or leave) in first place, and not trying to continue to discredit a proven fine guide.
This topic got so messed because of him, I'll just close it.
of course its head CONNECTOR, heads doesnt have any motors. I explained why isolating heads is better solution few times in earlier posts. this method is one which will work with ES.2 series and work also with DM22 and 7200.11, New firmares doesnt open terminal if motor connector is isolated. thats why we seen so many people who cant open terminal. I can discredit your competence on every post which you type. But you immediately change your post and then I look as this bad guy. almost all your posts are EDITED. There are posts where its only a DOT and signature.
Stop lying mr Fernando Martinez
0 -
And finally before commands:
it seems ok to me. i just put something (eg pen) to bent pcb enough to prevent connection
0 -
Hi again,
Now i've tried the loopback test so my setup is correct.
I dont get any response from the terminal, I dont get "F3 T>", but i can type..
I placed a paper card between the motor connector and the harddiskmainboard like in post #1, attached the tx and rx cables, opened hyperterminal, and then powered on the drive, and then pushed CTRL+Z... But i don't get anything?
Anyone that can help me? Over msn maybe?
I have a 3500320AS with SD15 firmwire. And i bought i RS232-TTL usb-converter.
I have the same problem as Alexx86 the set up is right but I get nothing but the small arrow mark on hyper terminal. Any help would be greatly appreciated
I have the same drive and firmware version Thanks
try connect ground from your cable to pin 3 in terminal socket of disk. i think it finally solved Alexx86 problem. we did everything from scratch, step by step so hard to tell.
0 -
Aviko,
Thank you for the clarified post on page 27 - that should be on the first page so people can find it and have the correct information.
I'll let you know how it works out for me, hopefully my data cable will be here tomorrow.
sure, but i dont want to be mentioned in any form.
0 -
avico,
What hardware do you recommend I buy from ebay, I'm in Europe, to perform the bsy fix?
I'm not familiar with electronics so the simplest the better. Thanks.
just search at home any usb to gsm phone cable. when you find one, connect it to usb port, if it detects as new hardware (and install after giving drivers) as USB-to-serial port with COMx where x is number, it will work. Did you find any cable?
0 -
Hi again,
Now i've tried the loopback test so my setup is correct.
I dont get any response from the terminal, I dont get "F3 T>", but i can type..
I placed a paper card between the motor connector and the harddiskmainboard like in post #1, attached the tx and rx cables, opened hyperterminal, and then powered on the drive, and then pushed CTRL+Z... But i don't get anything?
Anyone that can help me? Over msn maybe?
I have a 3500320AS with SD15 firmwire. And i bought i RS232-TTL usb-converter.
my msn id: aviko A-T op.pl (u know what to do, i dont want spam on my email)
It seems Gradius's guide was posted a little over 24 hours after aviko's (in polish). Gradius should be giving credit (at the very least) to aviko and link to his original posts, otherwise I will edit the post.Yura (aka okzo) posted it, not me. I just wanted justice.
0 -
Hi,
I tried to fix ST3500620AS with HP12 firmware (HP OEM), initially showing LED:000000CC FAddr:002493D1.
All went fine but after the last step
F3 T>m0,2,2,,,,,22
nothing happens, even after 10 minutes. Drive is still not recognized by BIOS.
I tried several times, the initial LED:000000CC FAddr:002493D1 does not show up anymore.
So has anyone an idea ora link or ...
Thanks!
And now can you enter to terminal or its locked?
0
but the error is at this end since I get the same problem with both the good drive (500 gig) and the bad drive, the 1TB PCB.
)
:realmad: 
The Solution for Seagate 7200.11 HDDs
in Hard Drive and Removable Media
Posted
connect to terminal, dont take off pcb. ctrl+z then F,,22 then m0,6,2,0,0,0,0,22