FIXED Stubborn Trinity

[rghpro]

Let me just start by saying I have done many RGH's on phats and slims, mainly slims though. Anyway, for the first time, I'm having trouble getting a Trinity to glitch, using a CR4 XL, I have included a link to a dropbox folder with my images below.

https://www.dropbox.com/sh/5v47ytuhu03z3cm/AACUxz1FOzVVrzmNeCCWWTvRa?dl=0

I believe I have soldered everything correctly, as I have done many times before. As a matter of fact I have actually recycled this CR4 from a previous Trinity I RGh'd, it was pretty much instant boot all the time, until my nephew spilled a raumen soup on it, since then its a RDOD 0010, I suspect a short under the CGPU or any BGA component for that matter.

So unless the CR4 got damaged during the process above, I have no reason why this Trinity will not boot, if anyone can help it would be appreciated.

This is not actually the first time I've not been able to glitch an xbox 360, usually I don't have time to post about the experience, but I guess this time I will. Instead of just moving on to the next xbox 360 console.

If any more info or photos are needed, please ask.

 

[zcaps]

Try cleaning up your CR4 with some alcohol and Q-tips.
After that write the stock nand to the console and see if it will boot with the CR4 and all other wiring wired to the board.
If you still get 0010, desolder the red cable from the CR4 and try to boot.
If you get an error after the red cable is disconnected then it is not the CR4, it must mean something is bridged or wrong with your motherboard.

If the dashboard boots with the red cable desoldered, solder the red cable back to the CR4 and desolder all the points on the CR4 except the ground and red cable.

Solder the wires back one by one until you get the error again. Fix the soldering on the wire which caused the 0010 error.

 

[rghpro]

Thanks for the reply, but I think you got a bit confused there.

The Red dot 0010 is not the motherboard I'm working on, I'm just adding that to show the CR4 was re used from that board, which worked very nicely, instaboots pretty much all the time.

So anyway, I've found a possible issue, I noticed, after trying to RGH a Jasper too, using a CR4, that the CR4 option in the XEBuild area in Jrunner is missing, thus probably causing the problem..


I load the nand dumps and initialize them and under RGH2 I get glitch2M and R-Jtag only, I used to get a CR4 option too?

Could anyone shine any light on that, I've been looking but cant seem to find an answer, I got like 5 RGH consoles in queue and this just started happening, no idea why..

Thanks in Advanced anybody.

 

[Oggy]

You won't get an RJtag/CR4 check box as rjtag+ didnt contain anything bespoke. It just uses a different chip/post code.

 

[rghpro]

Okay, I got it figured out, well, kinda.

I thought I was up to date, on beta 5, but out of nowhere I got a notification for an update, ended up on beta 7, then file check kicked in and I got the CR4 option back.

As of this point, I just did a Jasper RJtag as it was in the queue. Just got done with that so I will try the trinity again, I'm sure it will work, if not I will post back once more. If it does, then case closed, lesson learned, ENABLE FILE CHECKS and Manually update to latest program version if not notified by J-runner, lol.

 

[ablegepu]

Yup that will probably fix it.

 

[rghpro]

Yep, it fixed it, now I finally got to it. I just followed normal procedure and it boots like a champ, as for the dead 0010 motherboard, well, that's another story.

 

[Oggy]

Closed at users request.