The readings were after I had soldered the nand x wires, then de soldered them.
EDIT: Someone requested pictues of my QSB install, here are the QSBs installed:
Last edited:
RGH Problem: Looking for USB interface device
- Thread starter mechgamer123
- Start date
EDIT: Someone requested pictues of my QSB install, here are the QSBs installed:
Martin C
VIP Member
Are you power cycling the NAND-x each time you plug in the PSU?
You're using way too much solder as well. Need about half than that or you run the risk of interference (bad blocks).
Have you used this NAND-x before successfully?
You're using way too much solder as well. Need about half than that or you run the risk of interference (bad blocks).
Have you used this NAND-x before successfully?
By power cycling, do you mean unplugging the nand x then plugging it back in? if so then yes.
Ok, thanks for the tip.
I've used this nand x to read the nand off of about 10 consoles since I ordered it from VGCrepairs.com on November 4th.
Should I have the nand x plugged into the computer before I plug in the xbox power supply or vice versa? Also, should I try pressing the reset button on the nand x?
Also, if it makes any difference, the console still boots fine, no RROD errors or anything like that, even after soldering and de soldering the wires/QSBs
Last edited:
Martin C
VIP Member
I would always do it in this order : PSU first, then plug NAND-x into USB.
You shouldn't need to reset the NAND-x.
I'm assuming these consoles work ok?
I'm still worried about that point which should be 3v. Can you measure J2B1.7 and see if your meter picks it up as 3.3v?
You shouldn't need to reset the NAND-x.
I'm assuming these consoles work ok?
I'm still worried about that point which should be 3v. Can you measure J2B1.7 and see if your meter picks it up as 3.3v?
Martin C
VIP Member
Which means that your 2.4v reading is sub-par and may indicate an issue with either solder or the point itself.
Unless you have another known working NAND-x there, it's hard to say either way.
Unless you have another known working NAND-x there, it's hard to say either way.
I'm probably going to order another nand x soon, to see if that is the issue. Do you know of any retailers that just sell the nand x itself without any of the qsbs or accessories?
Martin C
VIP Member
unfortunately not.
I'm assuming you get the nice "connected" sound from Windows when you plug it in?
I'm assuming you get the nice "connected" sound from Windows when you plug it in?
Ubergeek
Xecuter Groupie
I'm finding people are getting this error from one of only 2 causes
1. Poor soldering of the qsb / wires / pin headers.
2. Programming a CoolRunner while it's installed to an Xbox. Either it's not switched to prg (which would screw everything up) or the Xbox was powered on or the power was simply sh*t quality.
As we have said before, DO NOT program the CR using a nandx while it's installed to the Xbox !! That method us for lpt jtag only !
1. Poor soldering of the qsb / wires / pin headers.
2. Programming a CoolRunner while it's installed to an Xbox. Either it's not switched to prg (which would screw everything up) or the Xbox was powered on or the power was simply sh*t quality.
As we have said before, DO NOT program the CR using a nandx while it's installed to the Xbox !! That method us for lpt jtag only !
I did not program the CR while it was installed in the nand x, I only have 1 cable plugged into the nand x at a time. Also, the CR was set to PRG when I programmed it!
I've also tried dumping the nand with 2 different power supllies, so I doubt the PSU is the issue either.
Yes I get the "connected" sound in windows and the nand x still shows up under PRUFTECHNIK USB DEVICES as XECUTER NAND-X USB
And thanks martin and ubergeek and anyone else who helped me, I'll order another nand x soon and try it. If it doesn't work, we'll know it was my soldering, and if it works, we'll know it was the nand x
Edit: I contacted Ed from VGCrepairs and he said the following:
[FONT="]
[/FONT]
[FONT="]Here is the problem the glitcher programming is killing the arm 7[/FONT]
[FONT="] [/FONT]
[FONT="]Here is what people are doing know, they have 2 NAND-X’s[/FONT]
[FONT="] [/FONT]
[FONT="]1 for programming and 1 for R/W nand[/FONT]
[FONT="][/FONT]
Last edited:
Programming CR somehow kills nand-X. and the phenomenon are these. Please I request to resellers, don't pre-program CR through your stocked nsnd-x. Thanks
I got a new nand-x today, hooked it up to the existing wires, and read the nand fine...
keil423
VIP Member
did you ever try just reseting the old nandX. Plug it in and press the reset button for 5 seconds.
Statecowboy
BANNED
Uber - is there a fix for this? I did exactly what you've described above, already ordered another nand-x, but was curious if you guys can recommend a fix to at least salvage my old nand-x.
homegrown
VIP Member
Yeah I would like to know if there is a fix for this also. I have programmed 20+ coolrunners and now the same problem. I can still program coolrunners but when I try to read/write to the nand I get "looking for usb interface device"
Martin C
VIP Member
homegrown
VIP Member
Yeah I did, I have tried 2 different sets plus the pin header cable. I am going to take my nand-x with me tonight to work and test it just to see if I can find anything that might be fried.
Statecowboy
BANNED
I have not, I will tomorrow when my new nand-x arrives...:facepalm:
However, I did check the connection from the wrie tip to the connector sleeve and it was good, so I'm also assuming there's something fried on my nand-x.
I have tried all the above suggestions but still no luck. I have ordered another Nand-x. Hopefully this will solve the issue.