Slim Trinity isn't glitching with CR4XL

[dbour]

Hi. This is my first time trying to mod an xbox360, I spent a while reading up on it and trying to learn the terms before doing it but still don't quite get it all. I've already gone through one QSB and Mobo trying, soldering the points for a Trinity V2 QSB when I had a Trinity v3 QSB because I was referencing the images on the CR4XL install guide, ugh.

So I'm on the second motherboard, this time without a QSB. I can read the NAND just fine, create and write ECC, I get the solid red light on the CR4XL with a blinking green LED about every 5 seconds. I've left it running for 20 minutes, no Xell.

To troubleshoot, I restored the original NAND and it boots just fine. I've tried switching the CR4XL to Phat and tried jumpers 3/4 both on and off. There are no bad blocks after writing the ECC. I tried loading the Trinity ECC for RGH2+ (http://team-xecuter.com/forums/showthread.php?147878-Xecuter-CR4-XL-Magic-SMC-Files-for-RGH2). After about 6 hours, I don't know what else to try.

• Console Type: Zephyr/Falcon/Opus/Jasper/Trinity/Corona v1, v2, v3, v4, v5, v6

Trinity

• Programmer Used: NAND-X, JRP v1.1, JRP v2.0

JRP v2.0/NAND-X

• NAND Size: 16/256/512/4GB

16

• Dashboard version: e.g 2.0.14699

2.0.13599.0

• CB Version: e.g 5771

9188

• Screenshot of NAND details from J-Runner: (attach an image to your post)
• J-Runner log
• updflash.bin log (if applicable)
• Image of the CR4 XL
• Images of close-up soldering to motherboard (attach images to your post)
• Detailed Description of the Problem
• Was the console working before you started: Y/N

Yes

• Do you get a green debug light appear on the CR4 XL chip every 4-5 seconds: Y/N

Yes

• 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!!).

It just flashes. It does make a sound.

 

[Antalpromille]

Cut the wires down so they barely fit, and try the different dips.

 

[dbour]

Thank you! I cut down the yellow and blue wires and in the process of de-soldering, pulled up the pad that the blue wire connects to under the X clamp. I tried it on FT4R2 but still didn't get a flashing green. Is following this worthwhile (http://team-xecuter.com/forums/show...Fix-When-You-F-*k-up&highlight=alt. CPU_RST)?

Now I don't get the flashing green LED anymore. Unless there is an alt point for the blue wire, chalk this one up as a loss too, ya?

 

[Antalpromille]

Thank you! I cut down the yellow and blue wires and in the process of de-soldering, pulled up the pad that the blue wire connects to under the X clamp. I tried it on FT4R2 but still didn't get a flashing green. Is following this worthwhile (http://team-xecuter.com/forums/show...Fix-When-You-F-*k-up&highlight=alt. CPU_RST)?

Now I don't get the flashing green LED anymore. Unless there is an alt point for the blue wire, chalk this one up as a loss too, ya?

Even if you use an alternative point you will still need to repair the trace damaged when you ripped the pad, so start by doing that.

 

[dbour]

Got it. Thank you for the responses and help.

 

[briggs01]

• Dashboard version: e.g 2.0.14699

2.0.13599.0


- - - Updated - - -

Got it. Thank you for the responses and help.

did you get it to boot to xell