Xecuter RGH2.0 JED Files & Other Updates

[BraveH43]

If your slim trinity is on dash 147xxx
and no cpu key you have to use rgh2.0
RGH2.0 IS FOR SLIMS!!!

The XSVF/JED trinity file and wiring for Slim is identical to original RGH!


The Trinity slim has been working with normal RGH for weeks :facepalm:

 

[playingmax]

Thanks for the update u guys ROCK!!!!

 

[RROD!]

thanks for the update and sod the haters you cant put brains where there is none lol

 

[badwigga]

you guys are the best

 

[sthetix]

1st of all I'd like to thank T-X for all the hard work and testing over and over that they do, it's can't be an easy process.

I have a Falcon 5773 CB and I seem to have everything spot on, the coolrunner tries to glitch but no boot.

~14719 Dash
~x2 Dumps
~Made ECC (took some time to get sorted because of the CB
~Removed cap from Coolrunner RevB
~Added 10 ohm resister to coolrunner
~All wiring

Is there any extra advice for the 5773 CB?

EDITED : IT Glitch now..in 5 minutes with TX_RGH2_A.xsvf

Falcon 5773 , 14719 dash


Falcon 5773 NAND, 14719 dash : http://www.qfpost.com/file/d?g=g2UGur5bx

build.py log :

* found flash image, unpacking...
ECC'ed - will unecc.
Found 2BL (build 5773) at 00008000
Found 2BL (build 5773) at 00009fc0
Found 4BL (build 5773) at 00013640
Found 5BL (build 1888) at 000186c0

* we found the following parts:
SMC: 1.6
CB_A: 5773
CB_B: 5773
CD (image): 5773
CD (decrypted): missing

* checking for proper 1BL key... ok
* decrypting...
* checking if all files decrypted properly... ok
* checking required versions...
** Decrypted CD not found! Loading xell CD from co
** Xell binary not found! Loading xell from common
* found XeLL binary, must be linked to 1c000000
ok

* patching SMC...
Patching Falcon version 1.6 SMC at offset 0x12a3
* Replacing CD...

* XOR HACK NEEDED FOR Falcon CB 5773
* patching CB_B 5772...
patchset for 5772 found, 4 patch(es)
* Applying XOR Hack to CB_B 5773
* Replacing CB_A 5773 with 5772

* constructing new image...
455088
* base size: 70000
* No separate recovery Xell available!

* Falcon Image Flash Layout:
0x00000000..0x000001ff (0x00000200 bytes) Header
0x00000200..0x00000fff (0x00000e00 bytes) Padding
0x00001000..0x00003fff (0x00003000 bytes) SMC
0x00004000..0x00007fff (0x00004000 bytes) Keyvault
0x00008000..0x00009abf (0x00001ac0 bytes) CB_A 5772
0x00009ac0..0x0001313f (0x00009680 bytes) CB_B 5772
0x00013140..0x0001913f (0x00006000 bytes) CD 9452
0x00019140..0x000bffff (0x000a6ec0 bytes) Padding
0x000c0000..0x000fffff (0x00040000 bytes) Xell (back
0x00100000..0x0013ffff (0x00040000 bytes) Xell (main
* Encoding ECC...
------------- Written into output/tx_rgh2_image.ecc

Thanks guys!

 

[CheaterTheHax]

hate to be the noob, but which one is for which console?

 

[Wretched]

hate to be the noob, but which one is for which console?

I found some info here
http://www.team-xecuter.com/forums/showthread.php?t=82702

just use jed files the same way

 

[sdboltdude]

The XSVF/JED trinity file and wiring for Slim is identical to original RGH!


The Trinity slim has been working with normal RGH for weeks :facepalm:

even for 14719 with no cpu key?


i know wires are same

thought xell would not boot in 14179(or give key)

sorry for noob just want to clairify

 

[jsinger47]

The XSVF/JED trinity file and wiring for Slim is identical to original RGH!


The Trinity slim has been working with normal RGH for weeks :facepalm:[/Q

even for 14719 with no cpu key?


i know wires are same

thought xell would not boot in 14179(or give key)

sorry for noob just want to clairify

i'm not sure how you thought this thread was the best place to clarify....as the CBs that are important are mentioned in the first post. notice they are all phat cbs

i would highly recommend you read up on the technical explanation on why slims (trinity) don't need a RGH2

this thread is not the place, as it is a discussion on RGH2

 

[Ubergeek]

even for 14719 with no cpu key?

nothing said about slim?

The Xecuter RGH Development Team are pleased to announce the official release of the RGH2.0 hack for all CoolRunner Rev A and Rev B dev boards. All Phat consoles have now been defeated and are totally glitch-able without having a previous NAND dump or CPU KEY (the same applies to Slim Trinity that have been updated to 14717/14719).

We have included all of the build.py and xebuild scripts for your convenience. Please give the correct credits if you use our work.

Xecuter RGH2.0 Features introduced:

• Hack now works on new CB's (14717/14719 update)
• Hack now works with all Refurbished Split CB's (4577, 5772, 6752)
• Zephyr CB 4578, 4575, 4577
• Falcon/Opus CB 5771, 5772, 5773
• Jasper CB 6750, 6752, 6753
• Trinity (Slim) CB 9188, 9230

ty for pointing out what cb i should be looking for
answer questions

IT WAS ALREADY RELEASED WEEKS AGO !
http://team-xecuter.com/j-runner-build-264-includes-14719-slim-rgh/

 

[big_ted]

I have a feeling that Team Xecuters team sleeps with their eyes open...that way they don't miss a thing.

Nah just lots of eyes, I've saw Ubers eyes closed normally with the line "never again":rolleyes2:

Ted

 

[redman2k1]

Great update and a little clarification!

 

[Mungus]

Thanks for all the hard work!

 

[qamRQ]

Nice clarification. Keep up the good work.

 

[wessam]

goog warke tx thanks

---------- Post added at 14:24 ---------- Previous post was at 14:23 ----------

good warke tx thaaaaaaaaaaaaaanks

---------- Post added at 14:25 ---------- Previous post was at 14:24 ----------

nice work tx

 

[asiangrafx]

thanks, we finally has all phats!

 

[Vest1ge]

Link to the timing JED files seems borken.

 

[jsinger47]

Link to the timing JED files seems borken.

still works for me

did you hit that shiny "download" button on the bottom of the screen?

 

[EMM386]

We know who leaked and we know who stole the code, it's also been admitted to behind the scenes.

Not trying to stir up a hornet's nest or anything.

Just being inquisitive, or nosey if you prefer.

Was the thief at least apologetic or were they smug B*****ds?

Cause that would be seriously apalling.

This bit may get me flamed but.......

I know XBox modding/repairs are viewed with dubious legality in certain circles.

You're a business. Do your staff/volunteers sign NDAs etc.

Can you not take legal action against the person/company distributing your code?

I know it's probably be fraught with difficulties/expense and most folk would probably view it with irony given the pre-conception that your equipment is used for piracy (not something I condone)

 

[wmb88]

i know this is Xecutor forum, but just wondering if the jed files are good to use to program other xilinx based chips ?