BlouBul

See if anything here helps or here (but DON'T use Nail polish remover, rather ethyl/isopropyl alcohol http://www.msfn.org/...ndpost&p=916757). http://www.msfn.org/...ndpost&p=957157

Didn't you get a driver cd with the cable? That is normally the best place. Just disable your antivirus and firewall to stop that message. If you are worried, just disconnect from internet as well, then there should be zero risk.

Hi r3nni32000, Not sure what is wrong. Do you have right driver/settings in Hyperterminal? ALL GNDs connected? Powered @3.3V? All connections secure & not shorting?

Hi marchy70, That is strange, AFAIK SD3B is suppose to be immune to this bug (as it is after SD1A). You are the first report of problems after update. You can try the extra (optional) commands given by Aviko and see if it makes a difference.

Try connecting to GND of power supply as well (Read-me-First # 7)

Hi cuudulieu datasg, See here: http://www.msfn.org/...post__p__936490 The same questions WILL yield the same answers (even if you change your user name) The answer is still NO.

Do you still have loopback? (do a quick test just to be sure you selected the right port in HyperTerminal and everything is still working?) Just goes to show that even the authors of some of the guides get confused (or he just showed which wires to connect there, which, of course, would then be correct). That's why it is recommended to switch them anyway if it didn't work, just to be sure Guess you mean converter, but yes, that is correct. I cannot really see anything wrong with the way you described it. Maybe just repeat everything again carefully, or if that still doesn't work, AND you are feeling adventurous, repeat the whole fix with your Nokia cable instead of the converter (although it might just yield the same result)

Did you try switching Tx and Rx? Did you read FGA #4 again?

OK now we know for certain you passed the loopback test. Next you can see if you can connect it to your hdd (with pcb disconnected) and see if you get a prompt with Ctrl Z.

Just want to make sure: Do you see what you type on the screen of HyperTerminal when you connect Rx and Tx together and nothing when it is not connected (loopback)? Now we will hopefully start to make progress. Remember to only try it one step at a time.

See here for sketch. See link in FGA #6 to determine which wires is which in your Nokia converter. Do NOT use colors, but count pins on Nokia end of cable that you cut off (hope you kept it )

Try switching Rx and Tx around. Also see FGA #4 (excerpt just above your first post)

Ok use batteries then. Did it happened only once? What happen if you first connect your usb and then put power on hdd?

Good. That is a successful loopback test. What stopped? ser2pl.sys is usually related to the usb to serial driver. Are you using original drivers? Also try it without externally powering your Nokia cable (might just work) or just try it again

Which com port did you choose in HyperTerminal? Make sure it matches the Port in Device Manager (if there are a port next to your converter cable) Also see FGA #4 and 5 just for good measure In other words, first get your loopback sorted out before you connect it to your hdd.

Yes, I suspected he might say something like that (actually, I expected worse ) Thanks for the reality check From what I could gather, the firmware shown as 77ZL could be because of an incorrect attempt at unbricking That is why I tried to understood what exactly happened during the first attempted fix, but since there was apparently no comms with the hdd during that, it was probably done by the data recovery "experts" Apparently it can be forced flashed to a later version after the fix. That is where the problem lies. The way understand your situation, you got a converter that didn't work originally (although you do seem to have loopback now with that converter) and replaced it with a Nokia CA-42 data cable (but forgot to replace it and are still using the original converter).

Just remember you are using a CA-42 Nokia converters normally do not need to be powered, try without powering the converter (see if loopback works) Not sure about it being seen in Disk management (or in your friends bios), might not be BSY. Try the procedure once more without powering the converter, and if the same, let's wait to see what jaclaz says (might be something else).

Yes, see what happens

Thanks Now I have a better idea of what is going on. I was not sure if you did half a fix before and that was the reason for the strange things. That said, there are a couple of strange things that I am not sure about. Let us do it one at a time. The first one is that it is seen on your friends pc in BIOS and not on yours. One possibility is that your sata power cable is damaged (that would also explain why your converter is not seen by your hdd) Check all cables and connections thoroughly (use different cables if you can).

A couple more questions (try to answer them all) 1.So your loopback was successful? 2. What kind of converter did you use? Is it powered at 3.3V or 5V? 3. Did you put SATA power on your hdd? 4. Is it now seen in BIOS? 5. Did you have comms with your hdd before?

OK corkyblue, Just try for once to answer specific questions. Each time I ask you a question, you come back with an answer for a different question I am still trying to understand how far you came with the fix and what happen there, what error commands you got if any and if you actually had communication with your hdd through hyperterminal. Please, just FIRST answer those questions and then we can look at the rest.

Did you get any response from hyperterminal when you tried to fix it. Check the three links given earlier for help (FGA, Read-me-first, and guide by CarterinCanada). Not sure what is exactly wrong, but you can't update the firmware on a bricked drive - you have to first do the whole procedure correctly before updating. Just try everything again carefully. and report what goes wrong (or attach log file from hyperterminal)

First tell us exactly what you committed with your hdd during the attempted fix. The more detailed info you give, the better the chance that we can understand what went wrong.

OK, let me just understand exactly what you did as the reports are very conflicting... 1. Did you do a loopback test? 2. Did you get a response in Hyperterminal when you issued commands? If the response to these questions are "YES", then your converter is powered and your hdd as well and you do not need to worry about that. If not, we have to look for the problem. Funny firmware version is not a major issue and can be flashed to SD1A/B after the fix. http://www.msfn.org/board/index.php?showtopic=128807&view=findpost&p=892154