RGH Falcon "Phat" NAND Read Problem

Dixed

VIP Member
Nov 8, 2011
225
0
Aberdeen, Scotland UK
Hi guys, I've already Jtag'd a few consoles and have already RGH'd my own console so i have a bit of experience.

A friend gave me his console and all appropriate equipment to RGH his console because he had no idea what to do :p.

Components: Phat QSB's, TX Coolrunner, Coolrunner to NAND-X update cable, NAND QSB cable to NAND-X and NAND-X V3 with newest drivers.

Computer/ Software: Windows 7 x86 (32bit) and CoolShrimp's latest version of Jtag Tool.

Equipment: 30W Soldering Iron, Low temp Solder, No-clean Flux, Solder tip cleaner (Brass wool).





Problem:
After soldering the QSB's and Coolrunner I connected all appropriate cables, connected xbox 360 power cable and AV cable. I then connected the cables to the NAND-X and then connected NAND-X to PC and opened Jtag Tool.

Read the NAND twice and wrote .ecc image without any problems what so ever.

Disconnected everything and power cycled. Changed Coolrunner to "Normal" mode and booted into Xell Reloaded and noted down CPU key.

Power cycled once more and connected all cables to NAND-X and back to the Computer. Changed Coolrunner pack to "Program" before doing so.

Now Jtag tool cannot detect NAND chip.


I've checked the NAND-X and cables with my own RGH'd xbox and everything worked fine.
I have now re-flowed all of the solder joints and checked again. Still the same problem.

Any help would be much appreciated. Thanks.

I will add photo's of ALL solder connections when i get home from work in a few hours.
 
Last edited:

Martin C

VIP Member
Jan 10, 2004
35,981
0
Scotland, UK
www.team-xecuter.com
I need to understand the thinking behind this:

Power cycled once more and connected all cables to NAND-X and back to the Computer. Changed Coolrunner pack to "Program" before doing so.
Do you not understand what you're doing with the switch? This is to program the COOLRUNNER, which you've already done.

Back on topic, what command did you use to write the ecc image?
 
Last edited:

Dixed

VIP Member
Nov 8, 2011
225
0
Aberdeen, Scotland UK
I need to understand the thinking behind this:



Do you not understand what you're doing with the switch? This is to program the COOLRUNNER, which you've already done.

Back on topic, what command did you use to write the ecc image?
I understand this switch is just to program the Coolrunner. To be honest, once the Coolrunner has been programed it doesn't matter if it is on "Normal" or "Program" when reading NAND so this isn't an issue.

I didn't use cmd to write ecc image. I used Jtag Tool. I just followed the step by step RGH walkthrough.
 

Martin C

VIP Member
Jan 10, 2004
35,981
0
Scotland, UK
www.team-xecuter.com
I mention it as had you left it in PRG mode, your console wouldn't have glitched at all afterwards. Also for the fact that nowhere should it state you need to mess with the switch once it's programmed and set to NOR.

So all you've done here is write to the NAND and fired it up (working, got CPU key).

Confirm you haven't written anything else to the NAND after doing this. If you have already written something and now it doesn't work, now's the time to mention it.

Pics of your soldering will be useful around now.
 

Dixed

VIP Member
Nov 8, 2011
225
0
Aberdeen, Scotland UK
I mention it as had you left it in PRG mode, your console wouldn't have glitched at all afterwards. Also for the fact that nowhere should it state you need to mess with the switch once it's programmed and set to NOR.

So all you've done here is write to the NAND and fired it up (working, got CPU key).

Confirm you haven't written anything else to the NAND after doing this. If you have already written something and now it doesn't work, now's the time to mention it.

Pics of your soldering will be useful around now.
All i have done is write the ecc file to the NAND, booted into Xell for the CPU key. I haven't written anything else.
Re-connected all cables and attempted to read the NAND for the third time (just for verification before i write the final ggBuild image). But no "usb devices" detected.

I will post photo's as soon as i get home. i finish work at 4:30pm.
 

daretogo

VIP Member
Feb 4, 2011
294
33
Denver, CO
While we are waiting for Dixed to get back (and hoping not to be scolded for thread hijacking) I was wondering if programming the coolrunner HAS to be done with the switch in the prog state?

I have a NandX upgraded to v3 and am using the official Xecuter NandX to coolrunner program cable and can only seem to get it to program with the switch in the normal state. I program using the normal nandpro command and the xvsf files. I've done this on two separate installs now, with no issue. I wonder why I can't program in the 'prog' position?
 

litnin

Full Member
Nov 30, 2011
53
0
Derry
If you've got another console try wiring it up and reading the nand of it. I had the same sort of problem a few weeks bk and it turned out the my nandx was buggered. sent it of and got a new on returned.
 

Dixed

VIP Member
Nov 8, 2011
225
0
Aberdeen, Scotland UK
To be honest i haven't really switched the Coolrunner to "Nor" before programing it. I don't see why it shouldn't work. I think the only difference between "Nor" and "Prog" is that the Coolrunner runs off the 3v line from console in normal and in "Prog" it takes power from the NAND-X.

If it works in normal then keep doing what you're doing :).
 

Martin C

VIP Member
Jan 10, 2004
35,981
0
Scotland, UK
www.team-xecuter.com
Soldering looks ok.

Do me a favour and make sure you've connected the right colour connections to the QSBs?

the green and blue connectors are very similar in colour.
 

Dixed

VIP Member
Nov 8, 2011
225
0
Aberdeen, Scotland UK
Soldering looks ok.

Do me a favour and make sure you've connected the right colour connections to the QSBs?

the green and blue connectors are very similar in colour.
I have double checked and triple checked. I'm starting to think it might be a problem with the NAND-X QSB itself.

I have another on with me right now. I will just replace it and let you know.
 

Dixed

VIP Member
Nov 8, 2011
225
0
Aberdeen, Scotland UK
Only problem is, I don't have a meter and cannot really justify buying one just to use it once or twice.
Would i be able to send it to you Martin? I've read your jtag/RGH/repair service thread.
How much would it cost for you to just fault find and possible replace anything that needs replacing?
 

Martin C

VIP Member
Jan 10, 2004
35,981
0
Scotland, UK
www.team-xecuter.com
What's baffling me is your solder looks fine and since you've been able to read/write to it, the only thing I can think of is the cable itself to the NAND-x.

Of course I'm happy to take a look for you - repairs start at £30 on a no-fix no-fee basis. PM me if you're interested.
 

Dixed

VIP Member
Nov 8, 2011
225
0
Aberdeen, Scotland UK
What's baffling me is your solder looks fine and since you've been able to read/write to it, the only thing I can think of is the cable itself to the NAND-x.

Of course I'm happy to take a look for you - repairs start at £30 on a no-fix no-fee basis. PM me if you're interested.
I've done a bit of fault finding. I have my own RGH'd xbox and i have tested all of the cables with my own xbox. Everything works fine. I am able to read and write to the NAND no problem at all.

I will have a talk with my friend to see if he wants to send it to you since it isn't my xbox.
Thanks for your help so far.
 

Moi140

Junior Member
Aug 19, 2010
15
0
Québec
I don't know if it can help you, but in my case, I got a lot of problem using the qsb. I solder and desolder it more than 4 time but nothing worked... I tried it with direct wires and it work the first time. Dont know if the problem was the qus or if I am to stupid to use them correctly, but direct wires was my final solution.

(Sorry if my English is not perfect)
 

Martin C

VIP Member
Jan 10, 2004
35,981
0
Scotland, UK
www.team-xecuter.com
No worries.

If you have a meter, these are the readings you should get from the NAND-x points when the console is plugged in but not switched on:

J1D2.1 ~1v
J1D2.2 ~3.3v
J1D2.3 ~0.13v
J1D2.4 ~3.3v
J1D2.6 ~0 (should be GND)

J2B1.5 ~0
J2B1.6 ~3v

I took these from a Xenon board but the debug headers are the same on all consoles.