"Looking for USB interface device, Cannot continue"

Status
Not open for further replies.

ishahzad

Noob Account
Nov 8, 2011
2
0
Hi Guys I am facing the same issue. I installed the drives in nand-pro2 and updated my NAND-X to v3 code (ARMv3.hex). Everything went well and then I installed the timing file on my cool runner using updated NAND-X and nandpro3.

But when I installed the QSB on my slim I am getting the same error as mentioned in the post and unable to read my NAND. I have plugged in the power cable on my Xbox slim before reading the nand. Can anyone please confirm regarding the bug in nand-pro3 mentioned in this thread. I am using Win7 64Bit but the drivers are installed from x64 Nand-pro2 package which I downloaded from this website. Do I have to install nand-pro3 drivers to read my nand (where I can find them). Also can anyone guide me how to check for bridging and soldering issues, everything appears correctly just wanted to confirm before I desolder my QSB
 

frazzeld

VIP Member
Jun 21, 2007
1,670
0
UK
Hi Guys I am facing the same issue. I installed the drives in nand-pro2 and updated my NAND-X to v3 code (ARMv3.hex). Everything went well and then I installed the timing file on my cool runner using updated NAND-X and nandpro3.

But when I installed the QSB on my slim I am getting the same error as mentioned in the post and unable to read my NAND. I have plugged in the power cable on my Xbox slim before reading the nand. Can anyone please confirm regarding the bug in nand-pro3 mentioned in this thread. I am using Win7 64Bit but the drivers are installed from x64 Nand-pro2 package which I downloaded from this website. Do I have to install nand-pro3 drivers to read my nand (where I can find them). Also can anyone guide me how to check for bridging and soldering issues, everything appears correctly just wanted to confirm before I desolder my QSB
You have to use NandPro 3.0 to read the nand now
It is available on this forum just put a search in

Edit: http://www.team-xecuter.com/forums/showthread.php?t=74259&highlight=Nandpro3.0
 
Last edited:

ishahzad

Noob Account
Nov 8, 2011
2
0
You have to use NandPro 3.0 to read the nand now
It is available on this forum just put a search in

Edit: http://www.team-xecuter.com/forums/showthread.php?t=74259&highlight=Nandpro3.0
Yes I am using nandpro3 but the windows dirvers were installed from nandpro2 since nandpro3 doesn't contain drivers for NAND-X. Also I just verified the continuity check and it appears that two points are not properly soldered. I will fix it and provide you the updates.

Updates:
It was indeed soldering issue. Thanks everyone
 
Last edited:

Ubergeek

Xecuter Groupie
Feb 24, 2003
6,259
0
California, USA
Yeah it is the new V3 code. So do i need different driver's? i am currently using nandpro_20d_drivers
You should be using the Xecuter NAND-X Drivers. The same ones that were released 2 years ago. Nothing else.

I believe much of the bullshit that guys go though is because they dont use these as instructed.

---------- Post added at 08:01 ---------- Previous post was at 08:00 ----------

Updates:
It was indeed soldering issue. Thanks everyone
of course it was :rolleyes2:
 

S1RuS

Junior Member
Nov 5, 2011
13
0
Austria
Moved to rgh support Hey Guys,
here is what i did so far:

- checked solder points several times -no bridges, look shiny as it should be - used lots of flux and flux cleaner afterwards (using 15W Iron and 0.5mm Sn60Pb40 Lead solder)

- up and downgraded nand-x several times used cK3i no errors

- used nandpro 2.0e and 3.a as well as Jtag tool

- installed, deinstalled and reinstalled drivers several times - nand-x is shown correctly in device manager

- triple checked that front board is attached and power brick got orange light

- tried every usb port for Nand-x connection

- read nearly every thread about nand-x problems

- coolrunner programming of 2 went flawlessly

nothing of those things helped still get the "Looking for USB interface device, Cannot continue" error in every tool.

Will post pics as soon as my girl brings the camera.

Update: Just fit my Box together to play a bit, removed Nand x cabel from qsbs, fitted dvd, fan and airduct, connected power, av, hdmi, tried to power up console but didnt do anything.

Rechecked solderpoints for grounding, only one grounding is where the yellow wire sits when using direct wire install of nand-x (isn't it supposed to ground?)

I'm sure i didn't burn anything cause i was really really carefull

Now i'm really lost.....
 
Last edited:

demonic69

Full Member
Feb 26, 2007
36
0
Barnsley, UK
I've just done the same with mine, have you checked the solder points from bottom to top?
It can't be the NAND-X, NANDPro even detects the wrong Arm version for me, so it's reading the NAND-X just fine.
 

x360ccm

BANNED
Jan 18, 2011
3,616
0
south coast UK
I've just done the same with mine, have you checked the solder points from bottom to top?
It can't be the NAND-X, NANDPro even detects the wrong Arm version for me, so it's reading the NAND-X just fine.
unplug the usb from nand x leave it out for a few seconds.then plug it back in.
 

demonic69

Full Member
Feb 26, 2007
36
0
Barnsley, UK
Are there any alternate points we can use to check the soldering? I know it's fine top to bottom but would be handy to check it's actually got contact with the PCB.

dgenx, tried that a million times, I'm not convinced it's anything to do with the NAND-X, it's either the QSB, wires, Solder Points or an actual NAND issue.

Did any of you use the JTAG tool to flash before you got this problem? I was fine before I used the JTAG tool I think, using multibuilder read and wrote several times no problem.
 

mickeyvilla

Full Member
Mar 30, 2011
78
0
birmingham WM UK
i've been having the same problem i started a thread myself on this,http://team-xecuter.com/forums/showthread.php?t=76236

at first i installed qsb & did a good job even if i do say so myself,but was told numerous of times to check my soldering.
from the very begining i knew it was nothing to do with my soldering,so i removed qsb inspected mobo & everything looked ok to me no burnt tracks,bridges or anything.
so i soldered wires direct to board inspected again for any loose/cold joints,burnt tracks & all seems to be fine.
tried reading nand but still get same error "cant not find usb device".

now i've come to the conclusion its either the nand-x flasher or computer compatability issues running these flash programes on win 7 64 bit.


it can not be anything els as i've checked & doubled checked.

i did forget to say when i first set it up it let me read & dump my nand twice & even wrote xell to nand,then after that i had "could not find usb interface device" error.

which i find realy weird because after it reading nand twice & writting xell it just came up with that error yet i did'nt do anything to mobo or soldered points,SO WHY?????????????????????????????????????
 
Last edited:

diaboliq20

VIP Member
Jun 23, 2011
3,497
0
Scotland
it's not windows - I used the same OS - works fine - did you use the drivers form TX or from Nandpro - if you used the ones included with Nandpro, there is your problem
 

mickeyvilla

Full Member
Mar 30, 2011
78
0
birmingham WM UK
it's not windows - I used the same OS - works fine - did you use the drivers form TX or from Nandpro - if you used the ones included with Nandpro, there is your problem
tried as u said & i've even tried it the other day but i get the message as u'll see in post.

i've asked it to run in compatability mode for win 7 & even ran NandPro as admin

thats why i said its gotto be down to compatability issues especially with me running win 7 64 bit
 
Last edited:

S1RuS

Junior Member
Nov 5, 2011
13
0
Austria
wont let me insdtall a there is no .inf file, windows refuses to accept, tried reflash nand x to v2 code, used nandpro and got could not detect flash controller
 

demonic69

Full Member
Feb 26, 2007
36
0
Barnsley, UK
If it's telling you the arm version is wrong using v3 software with v2 hex or vice-versa it's obviously reading the NAND-X so the drivers must be fine.
 

E_NICE

Full Member
Aug 3, 2010
82
8
Bronx NY
There are 2 different messeges that can appear apart from the actual reading of the nand. A no usb device found and a cannot continue error.

I have a macbook pro with windows 7 x64 ran through parallels.

I was first getting a no device found error just like a lot of people with the nand-x version 3. But what i did was completely erase the drivers and downloaded the "nandx_x64_signed" drivers and used that instead. Now I get a cannot continue message which i assume is the error you want to get if your xbox is not connected to the nand-x.

Also according to ubers guide...if the nand x is connected to the usb port by itself it should light up red and a green light(yellow for older) to verify that the nand-x is v3.

Hope that helps.
 
Last edited:
Status
Not open for further replies.