Another 'could not detect' thread

[frazzeld]

whats the underside look like (pin headers)

 

[OilyD]

whats the underside look like (pin headers)

Post #15 :smile:

 

[bonsc]

if you have xell installed this worked for me http://team-xecuter.com/forums/showthread.php?t=74632

 

[OilyD]

if you have xell installed this worked for me http://team-xecuter.com/forums/showthread.php?t=74632

Cheers,I'll have look at that when I get back from work this afternoon.

 

[DaRkO]

or try shorting your nand, that will make it go into recovery mode and you'll be able to read/write to it agian

sounds drastic but it works and has saved my ass plenty of times

see how to do it here: http://team-xecuter.com/forums/showthread.php?t=52213

Thanks to big_ted for the guide.

 

[OilyD]

if you have xell installed this worked for me http://team-xecuter.com/forums/showthread.php?t=74632

Just read your thread in the link and I can't do this as it doesn't boot into xell and nothing appears on my screen.
But thanks for your help

 

[OilyD]

I'm going have to wait to finish this as I sat on the RF board t'other night :rolleyes2:

 

[ramaro125]

ok i was having the same problem fist, no usb interface device so i flash the nand-x whit flash magic use the Ubergeek tutorial http://team-xecuter.com/forums/showthread.php?t=74259 and the hex file from nandpro 20d at this time im not using jtatool im doing it old ways http://team-xecuter.com/forums/showthread.php?t=55189( side note after trying a million times:rolleyes2: and different ways side ways up down and ubergeek telling evrione that it was pebkac error:rolleyes2:send the unit to xconsoles paid for the update but they seend me a new unit wich i thank them for imagin mi surprise the unit programs with flash magic at first try ) after i program the nandx i was getting the could not detect a flash controller so i re solder the red cable for the jtag (im ussing the alternate points as per tutorial 55189) and voila working

 

[demonic69]

Have you checked the continuity from the underside to the nand-x end of the cable? Could be something as simple as a poor connection that was made worse when you disconnected from the board

 

[Ubergeek]

As you have called this 'another....' thread, what makes you think the answers are going to be any different than all the others that you have read so thoroughly ?

 

[Ubergeek]

ubergeek telling evrione that it was pebkac error:rolleyes2:send the unit to xconsoles paid for the update but they seend me a new unit wich i thank them for imagin mi surprise the unit programs with flash magic at first try )

Guess who xconsoles sends all those nandx to?

Guess what I do to fix them? lol

 

[OilyD]

As you have called this 'another....' thread, what makes you think the answers are going to be any different than all the others that you have read so thoroughly ?

Because it seems it isn't 100% of members soldering skills(as suggested by the threads/stickies I've read) that's the problem but something else.
Also considering this thread is almost 2 months old it still must be a problem with something other than peoples soldering skills

 

[ramaro125]

Guess who xconsoles sends all those nandx to?

Guess what I do to fix them? lol

lol dont get me wrong your posts and your tutorials HAVE help me immensely and y RESPECT YOU but my point is that after a lot of people where having the same problem and trying a lot of different ways to program the unit i personally two different cpu two versions of windows two update cables (which i paid for the first had the cables wrong) also this http://www.team-xecuter.com/forums/showthread.php?t=75777&page=5 an also this http://www.team-xecuter.com/forums/showthread.php?t=75777 and this http://team-xecuter.com/forums/showthread.php?t=7425 you still when someone ask tell them that was PEBKAC error and i think that some unit are faulty again i do thank you and xconsoles for the new unit

 

[OilyD]

Just thought I'd update my problems with this Nand X I've got.
I've updated it to V3 and tried it on a known jtag box,i.e already flashed,running FSD etc and it's still showing up as 'looking for usb interface..........'
Would be nice if the honesty went the other way,people have admitted in some cases their soldering wasn't up to scratch but there's also a lot of people who've proved their soldering is up to par.

 

[OilyD]

Well took my Nand X to a friends today and tried to read my nand with it,wouldn't work.Tried his and read it straight away.

So there you have it,a faulty Nand X,not a soldering issue,not a driver issue and not a end user issue.

 

[Ubergeek]

Your friend probably didn't program the CoolRunner while it was installed to the Xbox and the switch set incorrectly hence causing the NAND-X to blow......or incorrectly programming of the v3 arm.

These threads are totally useless and a waste of time.

You are told what this error is and what causes it.

If you think it's faulty after going through everything advised already then send it back to your supplier for test/repair/replacement

Thread should be titled 'Another useless thread about the same stuff that's answered a thousand times'

 

[Ubergeek]

Because it seems it isn't 100% of members soldering skills(as suggested by the threads/stickies I've read) that's the problem but something else.
Also considering this thread is almost 2 months old it still must be a problem with something other than peoples soldering skills

Yeah out of tens of thousands shipped you get the odd faulty unit, but 99% of the time it's user error. No where does it say 100% so that shows you didn't read much at all.

Guys like you seem to think because a dozen people post an error then it must be a huge epidemic issue

It's 0.001% of sales.

The error is explained. The solutions are explained.

The retailer can detect if the nandx has been misused or programmed incorrectly (hence void warranty) so if it is a genuine faulty unit then there is absolutely nothing to worry about as its under warranty.