Whats weird is my nand-x and ck3 pro non-rev d is recognized by my pc and I can flash dvd firmware with my ck3 pro and I can also read my nand with my nand-x (using nandpro v2.0) but I cant update it to v3.0 using my ck3.
CK3 to NANDX AutoBaud Errors - Read For Fix
- Thread starter Xecuter
- Start date
Ubergeek
Xecuter Groupie
I thought I had a non rev-d ck3pro. Which didn't need the wire.
My earlier post with pictures (Ignore the wiring. Those are old pictures. I've since fixed the wiring for the cables.)
Oh, well. I'll add the wire this evening when I get home from work and try it out. Thanks Uber.
Last edited:
You guys do know you can move the pins around to the right position, just by lifting the little plastic piece up a bit and pulling out gently, then just push back in the right hole, just in case you didn't know
Ubergeek
Xecuter Groupie
yes this is explained in the OP - however you have detailed it a little further thanks
---------- Post added at 11:21 ---------- Previous post was at 11:20 ----------
It doesn't hurt to add the wire to the REV D - just in case. If that doesn't work then it has to be something wrong with your PC setup.
xbox360 hacker
BANNED
Uber could that problem cause a faulty nand-x.A user on here has sent his nand-x for me to update as he could not update it. So i tried to update his nand-x and i get the same autobaud error i thought it might be me so i connected my nand-x up left all settings the same and it updated mine.
I would say it doesn't because I tried numerous times to update it and was getting the autobaud error. But I was still able to read the nand with my nand-x using nandpro v2.0. After reading the nand, of course I was still getting the autobaud error. That's just my experience. :smile:. I'm not a pro tho. Just learning. So Uber can most likely give you a more definite answer.
Of course I´m SUPPOSED to, just saying that the light is on and that I can´t get the nand-x updated (autobaud error) or seen in device manager anymore.
Ubergeek
Xecuter Groupie
It wont be seen in device manager as whatever code you have sent to it has corrupted it.
My guess is that you've erased the bootloader.
---------- Post added at 14:36 ---------- Previous post was at 14:33 ----------
however ive had a few back today and it turns out that they erased the bootloader = bad settings in flash magic
---------- Post added at 14:40 ---------- Previous post was at 14:36 ----------
My guess is that you've erased the bootloader.
---------- Post added at 14:36 ---------- Previous post was at 14:33 ----------
No it wouldn't cause the error no
however ive had a few back today and it turns out that they erased the bootloader = bad settings in flash magic
---------- Post added at 14:40 ---------- Previous post was at 14:36 ----------
Check soldering around the JTAG points on the NANDX
I haven´t send anything at all cause of the autobaud error, any other suggestions?
Ubergeek
Xecuter Groupie
Nothing that hasnt already been posted
the only way i can get autobaud error is if
1. The cables wires are incorrect
2. the ARM file is not loaded correctly
3. The baud rate is above 9600
4. the CK3 drivers are not installed correctly
5. the com port is not happy
6. there is not enough power through USB
7. try a powered usb hub
the only way i can get autobaud error is if
1. The cables wires are incorrect
2. the ARM file is not loaded correctly
3. The baud rate is above 9600
4. the CK3 drivers are not installed correctly
5. the com port is not happy
6. there is not enough power through USB
7. try a powered usb hub
So you´re saying that I should be able to program nand-x even if it doesn´t show in device manager or get recognized as a new device on any other computers?
My CK3 USB cable was faulty, replaced it and CK3 isn't recognized by windows. Uninstalled drivers, restarted, installed drivers, plugged in CK3 and it still does not work. Tried both CK3 Pro drivers. Even tried on a laptop which the CK3 was never connected to before. Anyone else ever had this problem?
explorer66
VIP Member
i tryed for 3 days going over all these steps but i kept getting that autobaud error
so i got a friend from work to bring his nand x in for me to try and update it
ive just plugged it in the settings were already saved in flash magic so clicked start
and it updated straight away
plugged mine back in clicked start, straight back to the autobaud error
so for me it has to be the nand x
Have you tried reading you nand with your nand-x using nandpro v2.0? I'm curious to see if it reads. Also is your nand-x new?i tryed for 3 days going over all these steps but i kept getting that autobaud error
so i got a friend from work to bring his nand x in for me to try and update it
ive just plugged it in the settings were already saved in flash magic so clicked start
and it updated straight away
plugged mine back in clicked start, straight back to the autobaud error
so for me it has to be the nand x
Ok, Im really frustrated. I've been at this for a week. Ive tried everything. I started with a ck3 pro non-rev d
and got this autobaud error on the following pc setups:
windows 7 64bit ultimate
windows home server
windows xp mode
windows 7 home 64bit (macbook vm)
windows vista business 32bit (macbook vm)
Then I thought does this nand-x even work? So, I tried to read my nand using nandpro v2. And it read fine. Came to this thread and found that my cables were part of the bad batch. So, I fixed it. See attached picture. Still same error. So, I ordered a CK3i thinking the ck3 pro was the issue. Got my CK3i today. Got the same dead blasted error with all the same pc setups from above. I just dont know. Any suggestions anyone????
and got this autobaud error on the following pc setups:
windows 7 64bit ultimate
windows home server
windows xp mode
windows 7 home 64bit (macbook vm)
windows vista business 32bit (macbook vm)
Then I thought does this nand-x even work? So, I tried to read my nand using nandpro v2. And it read fine. Came to this thread and found that my cables were part of the bad batch. So, I fixed it. See attached picture. Still same error. So, I ordered a CK3i thinking the ck3 pro was the issue. Got my CK3i today. Got the same dead blasted error with all the same pc setups from above. I just dont know. Any suggestions anyone????
Ubergeek
Xecuter Groupie
Yes your registry usbstor is messed up you need to fix it. If you don't know how to fix basic windows issues like this, use google and there is an app in misc downloads section on 360mods.net
That or send your gear to whoever you bought it from and ask them to do it for you.
explorer66
VIP Member
the nand pro works perfectly doing a normal jtag it just wont update, all i get is the autobaud error
yet i updated my friends perfectly with the same cables and the same settings that were saved in flash magic
im not the 1st person to say they have updated a nand x to version 3 but cant get another to update with the same cables / settings
so it has to be a problem with the nand x
as a last resort i tryed soldering the cables to the nand x before i updated my friends so i cant return it either
try and return your nand x to the place you bought it
stick with it as it is worth it in the end
Last edited:
I am in the same boat as Modster. My Original release rev Nand-X that has worked forever is now no longer seen in Windows and I can't do squat with it. So, that said, I'm rather pissed. Can we please get some focus on how people like us can get back up and working again. I do have a USBJTAGNT if that will help us in any way. Please don't leave loyal folks hanging.
Im in Leeds, I was wondering if someone could try programming my nand-x, Ive got the right cables, and a CK3 Pro (Not Revd) tried with the wire and without, no joy. Everything works ok but not re-programming nand-x :-(