FIXED Trinity RGH w/CR4 XL install in progress but stuck.

Jago151

Full Member
Jan 6, 2014
68
0
Here's what I've used so far:

-QSB Trinity V3
-CR4 XL
-TX J-R Programmer

So I was able to dissemble my Trinity and solder on the QSB Trinity V3 to read my NAND with J-R Programmer, which was successful 2 times. After that I installed the CR4 XL and then tried to read my NAND again just to test that everything is still working and I got the following error from JRunner:

J-Runner v0.3 Beta (5) Started

Checking Files
Finished Checking Files
Version: 10
Flash Config: 0x00023010
Error: 201 reading block 1
Error: 201 reading block 2
00023010
Trinity, Jasper 16MB
CB Version: 9231
Trinity

I'm sure something is wrong but I'm not entirely sure. JRunner was able to read my NAND when I just had the QSB Trinity V3 installed, so what could be the cause of the issue? Thanks in advance.

And yes this is my first rodeo...managed to not lift a point so far so that's progress :smile:
 

chase

VIP Member
Apr 11, 2004
1,073
28
Toronto, Canada
possibly a connection error.. did you have power connected to the 360 ?

post pics of all your soldering

also, once you have a few dump of your nand and they are matching, there is no need to read it again :)
 

Jago151

Full Member
Jan 6, 2014
68
0
Yes I did have power connected to the 360. The red light was lit up on the CR4 XL. I can post some pics in a few minutes.
 

Jago151

Full Member
Jan 6, 2014
68
0
I know my soldering isnt ideal for the green, yellow & blue wires but i was hoping it would do the trick:

IMG_0301.jpgIMG_0302.jpgIMG_0303.jpgIMG_0305.jpg
 

Jago151

Full Member
Jan 6, 2014
68
0
OK so I reinspected my soldering and redid a few points. Was able to get the J-R programmer to read the NAND again with both the QSB Trinity V3 & the CR4 XL installed. But now my issue is that after using JRunner to Create the ECC & Write the ECC my Xbox will not boot into XELL so that I can grab my CPU Key. Any thoughts?
 

gavin_darkglide

VIP Member
Dec 14, 2012
2,303
118
Clean up the soldering, and remove the cap. Tuning doesnt come in until after you glitch the system. It should boot, as soon as you get to your center timing settings with the dips, then you tune from there.
 

Jago151

Full Member
Jan 6, 2014
68
0
Believe it or not I think I cleaned up the soldering the second time around but I can take another look. Aside from that i'm not entirely sure what the issue is. BTW, you dont have to program the CR4 XL in JRunner right? I didn't do it since I assumed that it was already pre-programed and was worried that might render the chip useless.
 

Jago151

Full Member
Jan 6, 2014
68
0
OK I've redone the POST, DB2G3 & CPU_RST pads:

IMG_0309.jpgIMG_0310.jpgIMG_0312.JPG

My trinity still wont boot into Xell to get my CPU key. Up until now this is what I have done:

1 - install Trinity QSB V3 to read NAND with J-R Programmer v2.
2 - install CR4 XL
3 - wrote TRINITY.ecc file in JRunner from http://team-xecuter.com/forums/showthread.php/147878-Xecuter-CR4-XL-Magic-SMC-Files-for-RGH2

I know my soldering is far from perfect but I would imagine it doesnt need to be in order to get the chip to glitch. Any suggestions at this point would be greatly appreciated.
 

A5u5Ra23rH3r0

Full Member
Sep 15, 2014
26
0
I am having the same problem. I have neat soldering. I Dumped Nands and compared, all is good. I have Written a dump back onto my xbox. I have created a ECC and then used the magic files ECC to get into Xell but it never POSTS! I just have the solid Red LED on CR4. I have rechecked my soldering, I recheck Nand Dumps, rewrote Nands. Redid the ECC image Creating and Loading. And it still wont POST.

Regards,
A5u5Ra23rH3r0.
 

Jago151

Full Member
Jan 6, 2014
68
0
I am having the same problem. I have neat soldering. I Dumped Nands and compared, all is good. I have Written a dump back onto my xbox. I have created a ECC and then used the magic files ECC to get into Xell but it never POSTS! I just have the solid Red LED on CR4. I have rechecked my soldering, I recheck Nand Dumps, rewrote Nands. Redid the ECC image Creating and Loading. And it still wont POST.

Regards,
A5u5Ra23rH3r0.
I see. Well I guess my first question is Did you get the ECC magic files from the thread I mentioned earlier? I had a hell of a time finding that page.

My next question is even though you have the solid red light on your chip when the unit is on, is the green debug light flashing at all? Mine seems to flash every so often, trying to glitch I guess. I remember reading on a thread yesterday that you need connections to POST & CPU_RST to get a green light, but dont quote me on it. I can't seem to find that thread today.

I know my soldering isnt perfect but I think it should be enough. What I think could have really helped in this situation is if the CR4 XL chip had a diagnostic port on it...modern cars have them and it makes troubleshooting that much easier. Imagine if you're having problems with glitching and you can't figure out what the issue is...all you would have to do is plug a cable to the diagnostic port and then see whatever the standard error code is...just like a car.
 
Last edited:

Jago151

Full Member
Jan 6, 2014
68
0
Here's the most recent NAND dump:

===================================================
Sunday, November 09, 2014 11:32:53 AM

J-Runner v0.3 Beta (5) Started



Checking Files
Finished Checking Files
Version: 10
Flash Config: 0x00023010
00023010
Trinity, Jasper 16MB
CB Version: 9188
Trinity
Reading Nand to C:\Users\Ronin\Downloads\output\nanddump1.bin
Reading Nand
Done!
in 3:44 min:sec

Reading Nand to C:\Users\Ronin\Downloads\output\nanddump2.bin
Initializing nanddump1.bin..
Header is wrong..
Trinity
RGH2 Selected
Nand Initialization Finished
Reading Nand
Done!
in 3:44 min:sec

Comparing...
Nands are the same

Wait....it says my header is wrong?
 
Last edited:

Jago151

Full Member
Jan 6, 2014
68
0
Here is a summary of my install using the CR4 help request sticky:

Console Type: Trinity
Programmer: JRP v2.0
NAND Size: 16MB
Dashboard version: e.g 2.0.16756.0
CB Version: 9188
Was the console working before you started: Y
Do you get a green debug light appear on the CR4 XL chip every 4-5 seconds: Y
How long is the light on for each time (be aware that if you're trying to work on a faulty console, this is not a T-X product issue!!): About 3.35 seconds

Screenshot of NAND details from J-Runner:
NAND_INFO.jpg


J-Runner log:
===================================================
Sunday, November 09, 2014 2:02:45 PM

J-Runner v0.3 Beta (5) Started



Checking Files
Finished Checking Files
Version: 10
Flash Config: 0x00023010
00023010
Trinity, Jasper 16MB
CB Version: 9188
Trinity
Reading Nand to C:\Users\Ronin\Downloads\output\nanddump1.bin
Reading Nand
Done!
in 3:44 min:sec

Reading Nand to C:\Users\Ronin\Downloads\output\nanddump2.bin
Initializing nanddump1.bin..
Header is wrong..
Trinity
RGH2 Selected
Nand Initialization Finished
Reading Nand
Done!
in 3:45 min:sec

Comparing...
Nands are the same


Image of the CR4 XL:
CR4_XL.jpg


Images of close-up soldering to motherboard:
POST.jpgCPU_RST.jpgDB2G3.JPG


Detailed Description of the Problem:
My trinity still wont boot into Xell to get my CPU key. Up until now this is what I have done:

1 - install Trinity QSB V3 to read NAND with J-R Programmer v2.
2 - install CR4 XL
3 - wrote TRINITY.ecc file in JRunner from http://team-xecuter.com/forums/showt...Files-for-RGH2

I know my soldering is far from perfect but I would imagine it doesnt need to be in order to get the chip to glitch. Any suggestions at this point would be greatly appreciated.
 

BL4K3Y

VIP Member
Jul 7, 2010
13,721
118
Colne, Lancashire (UK)
Can you confirm that you now have two good NAND reads from the console?

I don't want you to do anything else until we know that you have a good NAND dump you can use to recover if things go wrong.
 

Jago151

Full Member
Jan 6, 2014
68
0
Can you confirm that you now have two good NAND reads from the console?

I don't want you to do anything else until we know that you have a good NAND dump you can use to recover if things go wrong.
Yes I do. I saved them from when I first ran JRunner.