"Looking for USB interface device, Cannot continue"
- Thread starter Dixed
- Start date
- Status
I have the same issue. But the problem is it is not bad solder for me because I tried to use Nand-x to dump nand of a old JTAG xenon working I got and same error. So it could be nand code problem
I hope so...
Yesterday I tried to read the nand without the rf board connected (the psu was plugged in and orange) but I had the "no usb, can't continue" problem. So, I am hoping that by connecting the rol-rf board I will be able to read the nand eventually. I now am at work so I can't try... Anyone confirm?
I tried it but also with no luck!
Martin C (SUPER MOD) said that when he reads/writes to the NAND, he has nothing connected. It's able to have a board without a CPU and GPU and the NAND can still be read and written to! (see 13th post @ http://team-xecuter.com/forums/showthread.php?p=491901&posted=1#post491901)
Yes you do not need rf board. I just tried because someone got it working. I just bought a new NAND-X with v3 code, when it arrives I will have 100% sure if it was firmware upgrade issue or windows issue
So you did not upgrade?? And it does not work also? The problem is most people say it is bad soldering but I have a Xenon Jtag working I did a couple of months ago and I get the same error if I try to dump again. With this I am pretty sure it is not solder issues.
No, didn't upgrade Nand-X, as it already supposed to have V3. Truth is that it's the 1st time I solder anything, but I don't think that this is the problem or is it?
Last edited:
Same Problem here with a slim! I've tried everything posted in this thread so far. Yesterday I've succesfully read/wrote my phat console with and without QSB.
That sucks! Is there any alt way to read/write the nand with Nand-x?
Thanks!
That sucks! Is there any alt way to read/write the nand with Nand-x?
Thanks!
I have encountered the same issue with my NAND-X that many other users in this thread have. I have attempted to dump and write the NAND on 12 different consoles (jasper, falcon and zephyr) that have the original QSBs still installed, all with no result. NAND-X seems to have no problem upgrading/downgrading to the V2 or V3 firmware, and will program my coolrunners just fine (on V2 i get "Cannot detect flash controller" and on V3 I get "Looking for USB Device: Can not continue"). With the V3 firmware installed, I get the ARM version error on Nandpro20b, which made me think that the computer was still communicating with the NAND-X properly...
I have already determined that it is most likely a faulty device, and have contacted the seller for a replacement (NAND-X is only about a week old).
To [email protected]:
"I recently purchased a NAND-X from you guys, and it has stopped working. The device will still power on, install, and even update properly, however, it will no longer read/write any NANDs for me. Every time I attempt to do so, I am shown the "Looking for USB Device: Cannot Continue" error.
I have done about 12 of these nandx qsb/coolrunner installs so far, and all of the consoles which I was able to dump the NAND on before are no longer working with my NAND-X. The same QSBs which were used for the initial install are still there (which worked great with the NAND-X the first time I dumped it) are no longer working with the NAND-X (I have checked all points and it is not a soldering issue on the QSBs).
I have done lots of forum searching, re-installed the drivers multiple times (on multiple different computers, both Windows 7 and XP) all to no avail. I believe the part which I have received is now defective, and would like a replacement.
I did want to say, however, that my experience with your company has been nothing but pleasant and satisfying. Your customer service/support has answered my questions in a timely and complete manner, and you have shipped every single one of my orders within less than 24 hours of purchasing! I really appreciate the awesome service of your company, and look forward to doing more business with you guys in the future."
I have already determined that it is most likely a faulty device, and have contacted the seller for a replacement (NAND-X is only about a week old).
To [email protected]:
"I recently purchased a NAND-X from you guys, and it has stopped working. The device will still power on, install, and even update properly, however, it will no longer read/write any NANDs for me. Every time I attempt to do so, I am shown the "Looking for USB Device: Cannot Continue" error.
I have done about 12 of these nandx qsb/coolrunner installs so far, and all of the consoles which I was able to dump the NAND on before are no longer working with my NAND-X. The same QSBs which were used for the initial install are still there (which worked great with the NAND-X the first time I dumped it) are no longer working with the NAND-X (I have checked all points and it is not a soldering issue on the QSBs).
I have done lots of forum searching, re-installed the drivers multiple times (on multiple different computers, both Windows 7 and XP) all to no avail. I believe the part which I have received is now defective, and would like a replacement.
I did want to say, however, that my experience with your company has been nothing but pleasant and satisfying. Your customer service/support has answered my questions in a timely and complete manner, and you have shipped every single one of my orders within less than 24 hours of purchasing! I really appreciate the awesome service of your company, and look forward to doing more business with you guys in the future."
Modchips.ca was unable to give me a refund right off the bat, without first being able to verify that my device is faulty (they indicated there was a $15 testing fee). Since the NAND-X is only $40 (well worth it!), I went ahead and just ordered another one so that I could verify the first one was faulty.
Plugged in my new NAND-X, and it works like a champ! I did not change any drivers, cables, QSBs or anything else since I last tried with the faulty NAND-X. I can verify that there is indeed a problem with my original device.
I hope this helps some others, who are at wits end like I was!
If you are proficient at computers and confident in your soldering skills, and are receiving the same error as everyone else in this thread then....
YOUR DEVICE IS MOST LIKELY FAULTY!
It happened to me after programming my 12th coolrunner chip. I am going to use my new NAND-X to do only the reading/writing of the NANDs, and my old one to program the glitch chips (since it still works for that function).
Plugged in my new NAND-X, and it works like a champ! I did not change any drivers, cables, QSBs or anything else since I last tried with the faulty NAND-X. I can verify that there is indeed a problem with my original device.
I hope this helps some others, who are at wits end like I was!
If you are proficient at computers and confident in your soldering skills, and are receiving the same error as everyone else in this thread then....
YOUR DEVICE IS MOST LIKELY FAULTY!
It happened to me after programming my 12th coolrunner chip. I am going to use my new NAND-X to do only the reading/writing of the NANDs, and my old one to program the glitch chips (since it still works for that function).
the soldering on pic 2 is horrendus. have you tested all pads for continuity? I'm not even sure its soldered onto the board, and there is definitely solder splash bridging 2 points
Sent from my HTC Desire using Tapatalk
So when I first got my NAND-X it had v2.0d, I was able to read the NAND on my XBOX, though it didn't work when it came to programming the Coolrunner (obviously). So I updated my NAND-X to v3 and now I get this exact error.
So it's definitely not my my soldering. I have tried it on multiple computers now with the same problem. I have not come to a resolution yet, except I emailed Xconsoles and advised them that I think I have a faulty unit. Just have a feeling I am going to get the run around for a while before I get a new unit.
So it's definitely not my my soldering. I have tried it on multiple computers now with the same problem. I have not come to a resolution yet, except I emailed Xconsoles and advised them that I think I have a faulty unit. Just have a feeling I am going to get the run around for a while before I get a new unit.
Nate, were you able to flash your NAND-X to 2.0 and see the wrong version in NANDPRO3? Did you get a new cable with the new NAND-X?
I fixed mine and it turned out to be a problem with the QSB. I did a pad-pin continuity test and one pad wasn't right, I soldered a wire direct from the pad to the connector and all's good, not sure if the pad lifted off the trace or the trace burnt or broke while I was using it, either way the Zephyr is now glitching merrily away.
I'd suggest anyone test flashing 2.0 to the NAND-X and reading with NANDPRO3 to see if it shows the wrong version 1st, saves possibly paying a fee to the supplier if the device can be proven to work. I can't 100% say this rules out a faulty device but seems faily indicative to me.
I'd also suggest a top(pad)-bottom and bottom-pin (if using QSB) continuity test to 100% rule out issues with soldering or the QSBs
- Status