You're SUPPOSED to power the ck3 with molex. How did you expect it to work otherwise ? lolJust got my CK3i to Nand-X cable today.
Ended up being super easy on Win7 64 bit with your tutorial Ubergeek. Thanks.
I used a MOLEX power supply to power my CK3i. For anyone having issues with powering thru their USB port or a powered USB hub, try a MOLEX power supply connected to your CK3i.
sorry i did not tell what was mi problem lol :facepalm: flash magic failed autobaud step-1:facepalm::facepalm::facepalm:hello i am having the same problem try ck3pro/ck3pro-d/ck3i no success turn the ck3i( side note the ck3i was assemble wrong the end plastic casing on the ck3i end was backwards the nand x was not turning on i switch cables to the same position and nandx on ) on off multiple times try different computer ueber any sugestions :mad2::facepalm: ps try the video from carolina gamer nothing also about side note try to email xecuter store down for maintenance
I was under the impression this wasn't necessary for the non rev D version as I've been reading, but maybe it really is necessary. Can anyone else confirm if this is true?For All That are having the Failed autobaoud whit an old CK3 Pro, (NOT REV D ONE). Just Put the Cable Jumper like you put on The REV D. For Me It works like a charm!!!
Hope It helps anyone.
i'm not sure if my revision d is a clone but the PL2303 chip doesn't have pin 1 on mine (mostl likely a clone)... no pin 1 at all very weird... i suppose that's why i was getting the failed to autobaud error on mine. but then i have an old non-rev d (no com-usb switch), and i couldn't do the update properly with flashmagic either, finally i managed to update it with xtractor2.3I was under the impression this wasn't necessary for the non rev D version as I've been reading, but maybe it really is necessary. Can anyone else confirm if this is true?
I'm getting the same error here. Updated and verified everything just fine, even read every single post here to see if anyone else was having a similar problem. I also tried another NAND-x that was NIB and un-updated. NandPro v3.0 throws out the, "Incompatible ARM firmware for this version of NandPro!" error. I was getting the Autobaud error, until I flicked the power on and immediately started the update through flashmagic as per OP.Updated my nandx to ArmV3 and now when I try to use NandPro3.0 I get "Looking for USB Device can not continue.." It worked just fine with NandPro 2.0.. Any ideas?
It is recognized in Device manager, even nandpro 2.0 recognizes but gives you a arm error. I just dont know why it doesnt go past looking for usb device.
I just used this thread to triple check my update cable and I do have everything wired correctly. Thanks for the heads up, I'll definitely fix my ordered cables as necessary. Unfortunately, I am still having my issue. It just has to be down to something that I am doing wrong. Oh well, I'll sleep on it and attack it from another angle in the morning, who knows, maybe I'll figure it out in my sleep. It wouldn't be the first time!
I used CK3i in all process. I first realized from the connection picture shown I should connect both molex and USB to make sure every step in the process will not have anything wrong accidentally happens.Relax2010 did you use a ck3i or a ck3pro ? im considering to buy a ck3i but if that gives me that autobaud error too i can better wait for the USB update cable :redface: