"Looking for USB interface device, Cannot continue"

[SixTSix]

I had this same error. I found the PSU had a red light. I unplugged it and plugged it back in. Then it worked.

 

[mousey01]

I have had the same problem with my nand x i updated it to V3 and it flashed the coolrunner no problem, but it just wont dump the nand on my 256mb jasper using coolshrimps jtag tool, i cant get nandpro 3.0 to work it just flashes on for a second then goes off. I have tried 2 computers 1 with windows 7 64bit and the other 32bit vista and still no luch Grrrrrrrrr lol.

 

[Akilles]

I have had the same problem with my nand x i updated it to V3 and it flashed the coolrunner no problem, but it just wont dump the nand on my 256mb jasper using coolshrimps jtag tool, i cant get nandpro 3.0 to work it just flashes on for a second then goes off. I have tried 2 computers 1 with windows 7 64bit and the other 32bit vista and still no luch Grrrrrrrrr lol.

To open nandpro just use shift and right click then click open command window here or just open cmd and navigate to the folder

 

[mousey01]

Thanks for that its easy when you know how isnt it lol?

 

[XxPOYSONxX]

Have the same problem. NAND-X was working fine when I dumped the nand then it flashed xell perfectly and I unplugged it, once I plugged it back in it wouldnt detect in nandpro3 :/ and the driver manager says something along the lines of 'not suitable for this platform' even after reinstalling the drivers multiple times :/

 

[ConsolePro]

Had same "problem"/error message yesterday on a Slim install (with QSB). When removing the QSB I discovered this problem was caused by a solder bridge on J2C1 pin 2 causing it to ground.

Although we also analysed NEO_X's returned Nand-X (from the posts above) and it is indeed faulty, so this error message could in theory be caused by a faulty Nand-X as well (far less likely tho, this is the first RMA of a Nand-X we have received so far over hundreds sold)

 

[jsw98765]

I was having a weird problem with my 512 Jasper last night. I could dump part of the NAND then all the sudden I would get read errors in the 2BXX area. It wasn't the same each time, but always started around 2B. After I would get the read errors, it would give me the looking for USB, then cannot detect error. I then would have to reset nandx pull the power on the xbox, and after a few runs at this it would detect again.

I started with qsb, the moved to pin headers, both same results. Eventually I pulled out the pin headers, to look at the traces, everything looked good. Not wanting to resolved the pin headers, I direct wired it. Still same issue. I saw another post from someone else about using a different psu. I tried it with an old xenon (203w) psu and to my surprise it worked just fine. Maybe my ground was just barely making a connection, but it worked for me so I didn't keep messing with it.

 

[mod_dude]

this seems to be a bug in nandpro 3

I am getting same error. I flashed NAND-X back to v2 , BOOM worked no issues.

Flashed back to armv3.hex same issue, NO USB detected

back to 2.0 works

back to 3.0 same issue :facepalm:

 

[arpsachin2]

How did you downgrade to 2.0??

 

[callum]

hi has anyone figured out this problem yet ive been getting the same error on my new nandx 3.0 it programmed the coolrunner and when i installed the qsbs it read but came up with loads of errors so now ive done a direct wire install and all i get is looking for
usb interface can not continue

 

[callum]

right i desolderd the wires and tryed them on an old xenon motherboard and it worked first time dumped it 5 times no bad blocks what so ever so for me it luks like ive burned a trace or bridged a point so im guna try a alternative method of dumping the nand on my falcon for me this error was due to bad soldering and not my setup :facepalm:

 

[Ubergeek]

This error is ALWAYS due to bad soldering. Few admit it tho so thanks for the honesty.

 

[callum]

haha i know this is my first reset glitch so my soldering is terrible lm going to try cut-in the trace and tht ive burned and fix em but will practice on a spare box, just need to find a good tut for repairing bad soldering would be lol

 

[edenstar]

I seem to have hit a roadblock here. I've finally finished soldering the QSB's and connecting everything up.

I connected the NAND-X to my computer and installed the appropriate driver exactly as the tutorial explains.

When i run Jtag Tool as administrator and click read nand i get the following error message;

Link To Image

Any help here would be appreciated. I've noticed people needing help with reading the NAND but I'm failing even before that.

i had the same problem as to window 7 x64 not installing the nandpro_20d_drivers this is what i did:-

THAT IF YOU ALL READY HAVE THE USBPRO DRIVER

Goto:-

Control Panel\System and Security\Device Manager= other devices-Memory Access\Update Driver
Software\Browse my computer for driver software\Let me pick from a list of device drivers on
my computer\libusb-Win32 Devices

use this driver and your up and runing? it did the trick for me, the funny thing is after when i
update the driver to the the orginal nandpro_20d_drivers it work?

 

[jordan1545]

I got mine to work after a few hours

i have done many jtags ect.. but lol i made a noob mistake and forgot to plug in the rf board derp after i plugged it in it worked just fine

 

[WarezRat]

Hey All. I have the same problem with "Looking for USB interface device, Cannot continue" but I have a twist. When I first installed the Nand-x I was able to read ok(I think), then when I went o do another dump things went south?? The Nand-x I got is the older version with a yellow light and the box says new V3 code and I was able to install ARMv3 on it no problems using Win7 32, Everything seemed ok BUT when I use the NandPro30 pack drivers it shows like this:
LibUSB-Win32 Devices > Memory Access

When I remove and reinstall ver 20d drivers it shows this:
PRUFTECHNIK USB DEVICES > XECUTER NAND-X USB

Now if I "update" the 20d drivers to the 30 drivers it seems to stay as a NAND-X USB but it really doesn't seem to take the update. I am lost now because it did work (i think) at first but now this:facepalm: Anybody have any ideas on WTF I am doing wrong? (besides everything) I have read numerous threads and have tried all kinds of things to get this to work.:redface:

 

[keil423]

Man this post is just flooding with Hijacks!

 

[jordan1545]

This error is ALWAYS due to bad soldering. Few admit it tho so thanks for the honesty.

Your wrong tbh i do not think 45235 ppl are all soldering bad lol in my case my solder was just fine it ended up with me forgetting to put the rf board on the slim i was rgh hacking lol so its not Always due to bad soldering just saying

 

[WarezRat]

This error is ALWAYS due to bad soldering. Few admit it tho so thanks for the honesty.

Once again Uber YOU were right.:redface: I read and read and read until I decided that I should reinstall so I went and desoldered then resoldered the joints on the QSB and the "Looking for USB interface device, Cannot continue" error went away! I ran the Nandpro30 numerous times, compared and now have multiple nands! THANKS! I am still confused about the Nand-X showing up as a "memory Device" and not the "Executer Nand-X" but hey, that's another thread!:wink: Thanks to all who posted relevant posts, this is what it is about.:biggrin: Slow as a turtle but I will get to where I want to go!

 

[VitalPros]

Have you ever used nandpro 3 before? have you turned on your console with the Nand X still connected?

Are you Jtagging or RGH?