ugur2323 Posted July 12, 2014 Share Posted July 12, 2014 Hi . i have a bricked ST3500418AS drive with CC38FW .i cannot enter F3 T> , because it is locked..which pins are read channel (short circuit pins) ?how long i must be short circuitPCB :Thanks so much.. Link to comment Share on other sites More sharing options...
jaclaz Posted July 12, 2014 Share Posted July 12, 2014 Difficult to say about "how long", reports vary, and may be not entirely reliable. Check if your PCB is the same as one of those whose images were posted here:http://forum.hddguru.com/viewtopic.php?t=18907&start=20If not read ATTENTIVELY this thread:http://www.msfn.org/board/topic/157329-barracuda-lp-no-not-a-720011-nor-a-720012/and/or post pictures of BOTH sides of the PCB. jaclaz Link to comment Share on other sites More sharing options...
ugur2323 Posted July 12, 2014 Author Share Posted July 12, 2014 The other side ; . i have read these topics but i cant find solution. Link to comment Share on other sites More sharing options...
ugur2323 Posted July 12, 2014 Author Share Posted July 12, 2014 i have shorted read channels but not working..i am shorting while powering up drive.my board is different Link to comment Share on other sites More sharing options...
jaclaz Posted July 12, 2014 Share Posted July 12, 2014 If you are positive about having identified the "read channel" (and two corresponding points on the upper side of the PCB to be shorted), you might be shorting them "at the "wrong" time.At least here (for the 7200.11 ES2 drive):http://www.msfn.org/board/topic/129551-unlocking-terminal-of-seagate-es2-in-bsyled000000cc-state/the shorting had to take place after you get the connection and the F3 T> prompt and before you get the "LED:000000CC..." message.(and it is seemingly very difficult to get the right timing, or at least everyone had to make several attempts to succeed). jaclaz Link to comment Share on other sites More sharing options...
ugur2323 Posted July 12, 2014 Author Share Posted July 12, 2014 Boot 0x10M Spin Up[0x00000000][0x00000000]ZZZZMMMMMMMMMMMMMMMZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMddddddWWWWMMMMMMx[0x00025CB4][0x00025CB4]ZZZZMMMMMMMMMMMMMMMZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMddddddWYWYWWMMMMMMx[0x0000B319][0x0000B319]ZZZZMMMMMMMMMMMMMMMZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMddddddWYWYWWMMMMMMx[0x00030FCD][0x00030FCD]ZZZZMMMMMMMMMMMMMMMZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMddddddWWWWMMMMMMx LED:000000EE FAddr:0010289C i can see just this only... i have tried the method you posted but wasnt work again..and there is only just one "LED:000000E" error. Link to comment Share on other sites More sharing options...
jaclaz Posted July 12, 2014 Share Posted July 12, 2014 BUT, do you get the terminal prompt pressing CTRL+z?Does the disk actually spin up? The "ZZZZMMMMMMMMMMMMMMMZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ ..." seem like an issue with connection (grounding/adapter/etc.). IF you are having *anything* different from the LED:000000CC" error (that presumably can be worked around by shorting the read channel), WHAT made you think that you needed t short the read channel? I mean, it is entirely possible that you are applying the right cure to the wrong disease or the wrong cure for the right disease. jaclaz Link to comment Share on other sites More sharing options...
ugur2323 Posted July 12, 2014 Author Share Posted July 12, 2014 (edited) i cant get terminal prompt. i can just see. sometimes showns in bios but capacity is 3-4 gb and it has different model name.disk spins up. clicks 4-5 time (after every clicks , prints" [0x00000000][0x00000000]ZZZZMMMMMMMMMMMMMMMZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMddddddWWWWMMMMMMx" )Then head stops , after few minutes it shows LED : 0000000EEi cant understand what is wrong with this disk P.S , thats happens when i didnt short read channels Edited July 12, 2014 by ugur2323 Link to comment Share on other sites More sharing options...
ugur2323 Posted July 12, 2014 Author Share Posted July 12, 2014 Link to comment Share on other sites More sharing options...
jaclaz Posted July 12, 2014 Share Posted July 12, 2014 I believe that the 3/4 Gb capacity (+different model name) is an altogether different issue from the ones (BSY and/or LBA0) that can (hopefully) be solved by the known procedures here. See if any of the good guys here:http://malthus.zapto.org/index.php? can help you, but please, try not to fall (again) in the XY issue:http://homepage.ntlworld.com./jonathan.deboynepollard/FGA/put-down-the-chocolate-covered-banana.htmljust provide the most info and as wide as you can description of the issue you are having (as opposed to asking help about how to perform a specific procedure that is not appropriate):http://homepage.ntlworld.com./jonathan.deboynepollard/FGA/problem-report-standard-litany.html jaclaz 1 Link to comment Share on other sites More sharing options...
ugur2323 Posted July 12, 2014 Author Share Posted July 12, 2014 thanks... i have asked hdd oracle and hddguru forums but no answers seems to be st3500418as disks are closed for any terminal operations . somebody says that wrong model name and capacity problem can solved with same solution of bsy and 0 lba problems. main problem is i cant enter any commands from terminal data is not important actually. but i was want to make some experience points for my hdd information thanks for your helps. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now