VideoRipper Posted March 24, 2010 Share Posted March 24, 2010 About a week ago I helped another person over e-mail that also tried to install a CA-42 cable (but he didn't have the phone, so the installer failed).He has been tinkering along and finally succeeded, here's what he said (in Dutch):Het is gelukt!!!Ik heb uiteindelijk in een laatste poging en in een helder moment de juiste manier gevonden om de kabel te installeren. (oorzaak: op de installatie cd stond enkel een menu voor de installatie van de Nokiasuite; geen menu item voor de kabel driver. Na wat zoeken op de cd vond ik uiteindelijk een map met de juiste bestanden). Ik heb daarna netjes de commando's van Gradius kunnen ingeven en ik kan nu de HDD terug gebruiken.Translated to English:I did it!!!In a last attempt and in a bright moment I found the right way to install the cable.(Cause: on the installation CD there was only an installer for the Nokia suite;there wasn't a menu item to only install the driver for the cable.After browsing the CD I found a folder with the right files for the driver.Then I could perfectly perform the commands described by Gradius and am able to use the HDD again.I suggest you fully uninstall the Nokia drivers and suite, restart your computer(in case your COM-port is still left in use) and try to find that folder on the CDthis guy is talking about, to install the drivers manually.Then try to open a session in HyperTerminal again.To be on the safe side (and to check whether you're using the correct wires, RX andTX), do a loopback test first by joining the RX and TX leads together and typingsomething on the keyboard while in HyperTerminal: the characters you type should beechood back on the screen.Good luck,Peter. Link to comment Share on other sites More sharing options...
bigleg Posted March 25, 2010 Share Posted March 25, 2010 (edited) Cool, I'll give it a shot, thanks! Edited March 25, 2010 by bigleg Link to comment Share on other sites More sharing options...
bigleg Posted March 25, 2010 Share Posted March 25, 2010 (edited) Tried manually installing the driver and the result is the same. The cable driver appears to be installed correctly, it shows up in the device manager under PORTS as "Nokia CA-42 USB (COM2)", but I still get the "Unable to Open COM2. Please Check Your Port Settings" message. I've tried this on two different computers running windows xp.This is frustrating, I feel like I'm so close to getting all of my data back!UPDATE: Just noticed my cable doesn't have a "made in" sticker on it. I'm now ordering one that says "made in China". Edited March 25, 2010 by bigleg Link to comment Share on other sites More sharing options...
janko Posted March 25, 2010 Share Posted March 25, 2010 can i use diodes of 3 V for shema of rs232 to ttl ? or diodes must be 2.7 V ?thanx ! Link to comment Share on other sites More sharing options...
jaclaz Posted March 25, 2010 Share Posted March 25, 2010 can i use diodes of 3 V for shema of rs232 to ttl ? or diodes must be 2.7 V ?thanx !Which schematics?Which diodes?If you mean the poorman's way depicted here (among tens of others):http://picprojects.org.uk/projects/simpleSIO/ssio.htmhttp://www.uchobby.com/index.php/2007/06/11/ttl-to-rs232-adaptor-explained/http://techref.massmind.org/techref/io/serial/ttl2rs232.htmThere is ONE diode and it is a 1N4148 or 1N4001, the most "generic" diodes around, that you can replace with almost anythinghttp://www.epanorama.net/circuits/component_replacements.htmlPersonally:I wouldn't use a 1N4001 (i.e. any rectifying diode as it may be too slow)if I were you I would buy a pre-made interface or kit (if you have to ask about diodes it means you cannot build one by yourself) you already have a faulty HD, there is not much sense to risk to completely ruining it due to a half-***ed interface jaclaz Link to comment Share on other sites More sharing options...
janko Posted March 25, 2010 Share Posted March 25, 2010 these diode Link to comment Share on other sites More sharing options...
jaclaz Posted March 25, 2010 Share Posted March 25, 2010 these diode Sure , they are perfectly UNneeded, they are simply a (better be safe than sorry ) protection against surges or wrong connection/return currents, and CUT the TTL voltage to 2.7V.Compare with this:http://elisegt.interfree.it/html/nokia.htmlZener diodes DZ1 and DZ2 are VERY important to safety of Your phone. Normally are values of log. 1 about 3.3V and little overcross of this value can damage the phone - so power blast at turning on computer or connecting interface into computer. DZ1 and DZ2 diodes cuts-down this voltage to 2.7V - it is enough to log. 1 and it is hardly under maximal voltage value.Since the specs for TTL are for 3.3V BUT up to 5 V can be given, the 3V zeners will anyway protect the interface and device from accidents without causing any problem:http://www.interfacebus.com/voltage_threshold.htmlMost of the Commercial interfaces and of the Max232 schemes around don't have them.jaclaz Link to comment Share on other sites More sharing options...
VideoRipper Posted March 26, 2010 Share Posted March 26, 2010 but I still get the "Unable to Open COM2.That worries me a bit Normally, a COM-port is only opened when an application (like HyperTerminal) or a service(like MS ActiveSync or the Nokia Suite) is actively using it; if you would only installthe drivers without any program (or service) using it, you *should* be able to open thatport like any other ("real") COM-port, no matter where the USB-device was made...Are you sure it's using COM2, since with most desktops, these are already integrated ontothe motherboard and any external attached (USB)-ports get additional numbers (COM3..COMxx).Please check the settings in the computer's BIOS whether any on-board COM-ports are enabledor not and play with these settings.Good luck,Peter. Link to comment Share on other sites More sharing options...
bmoroschan Posted March 26, 2010 Share Posted March 26, 2010 I'm having a problem applying this fix:When I plug the sata power into my hdd, the entire system crashes. Am I doing something wrong? Link to comment Share on other sites More sharing options...
VideoRipper Posted March 26, 2010 Share Posted March 26, 2010 (edited) Apparently I hope you're not trying to apply power to your drive while it's connected to the SATA-port to your computer and your computer is turned on? Because that will most definitively crash your system (unless your motherboard supports hot-swapping).First do the fix with only the RS232 <=> TTL convertor connected.After you've un-bricked it (after carefully following the instructions on the first page of this topic), you have to power down your computer, connect the drive over SATA, power up yourPC and see if it's recognized in the BIOS.When it's recognized, see if the BIOS reports it as a 0GB drive.If it does report as a 0GB drive, do the LBA0 fix (first power off your PC, disconnect SATAand re-connect the RS232 convertor, then power on your system).If your BIOS sees it as it should, you will be able to access it again and you can backupthe drive (do this first before you do anything else).Greetz,Peter. Edited March 26, 2010 by VideoRipper Link to comment Share on other sites More sharing options...
janko Posted March 26, 2010 Share Posted March 26, 2010 I made it! with great passion!thanx everybody Link to comment Share on other sites More sharing options...
franklink Posted March 27, 2010 Share Posted March 27, 2010 I have two of these drives. I screwed up and used someones post here, which left out the REBOOT AFTER N1 step on the first one.For the second one I went back to page one and used those steps. Thanks! That drive is fine now.My question is about the first drive. The mis-step I took was issuing these two commands with no hdd reboot in between.N1F3 1>m0,2,2,,,,,22The disk now detects. I can see it in windows, but in disk management it shows up as an uninitialized drive. Is there anyway I can recover data from it now? What exactly did I do with the F3 1>m0,2,2,,,,,22?ANY help is appreciated!!! Link to comment Share on other sites More sharing options...
Simba7 Posted March 27, 2010 Share Posted March 27, 2010 (edited) I just used a cheap CA-42 cable off of eBay.. Just make sure you only use the Black (GND), Orange (RS232 TX), and Brown (RS232 RX) wires.This worked without a hitch on my relatives' 1TB Seagate that was in an Iomega External Case. I was able to recover ALL of the data (which amazed him). Unfortunately, I need to figure out how to force-flash this drive (since it seems to have some different firmware code) so I can reuse it instead of trashing it.BTW: The cable I bought is: http://cgi.ebay.com/ws/eBayISAPI.dll?ViewItem&item=110507181865 . The drivers for it are the Prolific PL-2303 Drivers (I found this out using Linux).As for "franklink".. You need to *WAIT* until the command prompt reappears. I found that out the hard way. If Windows still wants to reformat it, do the following:1. Fire up a System Rescue CD (sysresccd.org) on a separate box.2. Mount the drive and configure Samba to share the drive (if you want to dump via network).3. Copy everything off of it onto a network share or external drive.4. Pull it out of the other box and place it back inside your workstation (or server).5. Reformat and repartition the drive.6. Copy all the files back onto it (if you want to). Edited March 27, 2010 by Simba7 Link to comment Share on other sites More sharing options...
VideoRipper Posted March 27, 2010 Share Posted March 27, 2010 Unfortunately, I need to figure out how to force-flash this driveYou can try to play with the command-line options of SF.EXE or FDL464.EXE (the actualflasher-utils) inside a firmware update package, but procede on your own risk. Greetz,Peter.FLD464_usage.zip Link to comment Share on other sites More sharing options...
franklink Posted March 27, 2010 Share Posted March 27, 2010 (edited) I have two of these drives. I screwed up and used someones post here, which left out the REBOOT AFTER N1 step on the first one.For the second one I went back to page one and used those steps. Thanks! That drive is fine now.My question is about the first drive. The mis-step I took was issuing these two commands with no hdd reboot in between.N1F3 1>m0,2,2,,,,,22The disk now detects. I can see it in windows, but in disk management it shows up as an uninitialized drive. Is there anyway I can recover data from it now? What exactly did I do with the F3 1>m0,2,2,,,,,22?ANY help is appreciated!!!As a follow up, I just realized my bios is detecting this drive as 0MB. LBA fix doesn't seem to be helping. I don't think it's the same as the LBA problem since I started out with the BSY problem, and created this 0MB problem after the fact. Edited March 27, 2010 by franklink 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