Team Xecuter's Xenon Reset Glitch Hack and Build.py Script Options

[Xbox-Scene]

Team Xecuter's Xenon Reset Glitch Hack and Build.py Script Posted by XanTium | March 7 22:26 EST | News Category: Xbox360

From team-xecuter.com: [QUOTE] We are happy to finally release the Xenon RGH Hack. This is by no means meant to be used for an everyday RGH as its as bad if not worse than a Zephyr, however it does work and will be perfect for those who have a Xenon where they lost their DVD key or an unbanned key vault. Here is the readme included with the release: * Wiring Generate your ecc image using the latest version of J-Runner and flash to your NAND (+w16 just like a regular RGH). Program your TX CoolRunner (or whatever flavor RGH mod you are using) with the tx-xenon.xsvf or tx-xenon.jed file. The Xenon has a capacitor on CPU_RST that was removed in later models. C7R112 (located near the xclamp under the CPU) must be de-soldered, and the CPU_RST wire from the TX CoolRunner(D) must be soldered to the left pad (non grounded pad). A 47nf ( 0.047uf) capacitor needs to be added between PLL_BYPASS(+) and GND(-). (If you have a genuine TX CoolRunner REV B you can use the on-board by bridging the CAP jumper) A 220-270pf capacitor should be added between CPU_RST(+) and GND(-) on the cpld. (If you have a genuine TX CoolRunner REV B this is already included in the design so not required) An easy to follow picture guide can be found here: http://www.team-xecuter.com/coolrunner/install/phat_xenon.jpg * Troubleshooting Using a TX CoolRunner Rev B, and after applying various troubleshooting measures we have had glitches ranging from instant to 20 minutes. The debug LED should flash on for less than a second and repeat every 5 seconds. If your LED stays on or does not come on at all, it is usually because of something being wrong with PLL_BYPASS. Try different values of capacitors and wires. If you have enabled the CAP on REV B of the TX CoolRunner, simply un-bridge it and try a 47nF cap instead as per the instructions above. If it still has not glitched after several hours, try different values of capacitors on CPU_RST of your RGH mod. A longer wire / low-loss 50 ohm double shielded cable may also help with this. To help increase boot times and stability (on all RGH installs not just Xenon) we recommend that you try Low-Loss Double Shielded 50 ohm cable. It's very cheap to use and quite effective – so a quick shout out to www.xconsoles.com who supplied a batch of high quality cable for our development team to use. It's less than 75 cents a foot – not bad. NOTE: Remember when programming the TX CoolRunner that the Xbox power is NOT connected and that the switch is set to PRG before you connect the JTAG cable. If you connect the JTAG cable and it is set to NOR with the Xbox power connected, it can damage your NAND-X and/or CoolRunner. When you have finished programming, switch it back to NOR and then power on the Xbox. * The Xenon Hack Please note that this hack is not available on consoles updated to dashboards 14717 or 14719. If you are seeing the debug led it means that the cpu is probably not crashing and the issue addressed by gligli/tiros has been fixed (This can of course be a false positive as sometimes the CPU could be crashing but the SMC restarts fine – we can never be 100% sure) So far, this is really only useful for a one time cpu_key dump. There will undoubtedly be ways of optimizing this hack in the future and who knows, it may become a reliable glitch one day. We would appreciate that you give as much feedback to our support forums as possible to help others achieve better results and to improve this method. For now we can leave this and go back to RGH2.0 for Zephyr, Falcon, Jasper and also of course, the Corona. TX CoolRunner Support Forums: http://www.team-xecuter.com/forums/forumdisplay.php?f=174 Enjoy! Xbox 360 Xenon RGH Hack brought to you by the Xecuter RGH Development Team www.team-xecuter.com * Thanks Thanks are extended to Tiros & Gligli, without your work none of this would have been possible. A special thanks goes out to cOz – your work on Dashlaunch proved to be an invaluable contribution and we look froward to your next exciting project. Greets: Team Jungle, Team FSD, Freeboot, Libxenon & RGLoader. [/QUOTE] From team-xecuter.com: [QUOTE] Here is the build.py for Xecuter's Xenon RGH Hack J-Runner has no use for build.py as it doesn't use Python (or Nandpro) but figured there would be some guys out there who still use this method. * Thanks to: RF1911 for the XENON SMC GliGli & Tiros for the original build.py cOz for the Universal patch To the Xecuter RGH team – you know who you are. * Greets to: #libxenon #FreeStyleDash #freeboot #rgloader #J-Runner #JungleFlasher #c4e Also one of our forum members nitramb released a much better 14717/14719 python script than the one released by those Italian guys. Again, none of this is required for the J-Runner app. Remember, when running to be first you should instead think about walking to be best [/QUOTE] Official Site: http://team-xecuter.com Download: here

[rastaman108037]

This is useful, for all those people that haven't used their xenons for target practice with an assault rifle.

I mean, surely those four people will truly benefit from having their POS first gen xbox hacked.

[ddxcb]

This is useful, for all those people that haven't used their xenons for target practice with an assault rifle.

I mean, surely those four people will truly benefit from having their POS first gen xbox hacked.

Not all xenon's are created alike.

Ref MFD May of 09, xenon with no RROD nor any issure. Hell my jasper have GPU lag/freeze issues.

[Weirdjerz3y]

Finally, i can get the dvd keys for two of my xexons.

[phrozenfeonix]

My launch 360 RRoD'ed finally about 4 months ago, never had any RRoD or fixes before it, only a JTAG. Since then I've replaced it with a slim (RGH), and never looked back. Still haven't attempted and RRoD repairs on my launch, it had a good run, and I'm happy with that.

[xiaNaix]

This is useful, for all those people that haven't used their xenons for target practice with an assault rifle.

I mean, surely those four people will truly benefit from having their POS first gen xbox hacked.

This is super useful. Thousands of Xenon's are out there not running due to loss of DVD key or an unbanned KV ripe for the picking.

If this is no use for you then why comment ? Just to post some troll flame on something that's a perfectly good release.

This post has been edited by xiaNaix: Mar 8 2012, 07:21 AM

[NYCXBOX]

he's just pissed cause he had 100's of xenons he could have done this to back when he was doing Jtags and he gave up cause his reball skills blew and most likely got rid of everything at a loss. With this he could have revived quite a few systems and made some more scratch. OH WELL....

[deilzfcjk]

thanks

[kdallas]

Awesome news, thanks!

"* The Xenon Hack
Please note that this hack is not available on consoles updated to dashboards 14717 or 14719."

I'm curious if this is just a temporary setback? I mean they've apparently got slims on 14719 glitching which would seem to be more difficult particularly corona.

I'd love to know the technical details of why this is so... as the process with the J-runner is the same, albeit with different jed timing files. Is it not?

[KirovAir]

Awesome news, thanks!

"* The Xenon Hack
Please note that this hack is not available on consoles updated to dashboards 14717 or 14719."

I'm curious if this is just a temporary setback? I mean they've apparently got slims on 14719 glitching which would seem to be more difficult particularly corona.

I'd love to know the technical details of why this is so... as the process with the J-runner is the same, albeit with different jed timing files. Is it not?

I'm also wondering this.

Also, I don't really see the fuss about how 'bad' Xenon's are, fixed one a year ago and it's still running like a charm.

[warbeast]

as i understand it there may well be a 2.0 for xenon above 14717+ but it wont be released before the other models as it could just be patched

the main difference between fat and slim is that fats slows the clock with the CPU_PLL_BYPASS signal
slim apart from corona slow the clock using the HANA chip witch has configurable PLL registers to do the job
corona without the HANA needs to find another way to do the above
xenon could be slowed down with CPU_PLL_BYPASS like other fats but would crash if they bring the CPU back up (untill now i guess)
the slim way on a xenon also wouldnt work as it uses ana without PLL registers instead it has a fixed frequency chip

this is just the basics of it witch i understand lol so as i said i cant see why any fix for other fats in the future wouldnt now work on xenon now tx has fixed the issues even if the end result is slower times on xenon

This post has been edited by warbeast: Mar 8 2012, 03:51 PM

[fratslop]

as i understand it there may well be a 2.0 for xenon above 14717+ but it wont be released before the other models as it could just be patched

the main difference between fat and slim is that fats slows the clock with the CPU_PLL_BYPASS signal
slim apart from corona slow the clock using the HANA chip witch has configurable PLL registers to do the job
corona without the HANA needs to find another way to do the above
xenon could be slowed down with CPU_PLL_BYPASS like other fats but would crash if they bring the CPU back up (untill now i guess)
the slim way on a xenon also wouldnt work as it uses ana without PLL registers instead it has a fixed frequency chip

this is just the basics of it witch i understand lol so as i said i cant see why any fix for other fats in the future wouldnt now work on xenon now tx has fixed the issues even if the end result is slower times on xenon

Lol

TX said they wanted to focus on corona, not xenon. Not because xenon "could just be patched"

Also, about the hana on corona: "hint: the hana is still there"

http://www.xboxhacker.org/index.php?topic=17701.0

Does nobody read anymore?

[warbeast]

Does nobody read anymore

i guess not as if you read my post i replied about why this isnt 14717+ and thats because rgh 2.0 is needed that isnt out on any fat yet and wouldnt be included in this release if it could be patched and stop 2.0 on all fats

this has nothing to do with tx comments to focus on corona instead of finding better boot times on the current rgh xenon

and let me adjust my cornoa comment to make you happy
"corona without the current HANA point"

why is everyone here looking to bitch these days

This post has been edited by warbeast: Mar 8 2012, 08:38 PM

[iwanttheagrocrag]

NOTE: Remember when programming the TX CoolRunner that the Xbox power is NOT connected and that the switch is set to PRG before you connect the JTAG cable. If you connect the JTAG cable and it is set to NOR with the Xbox power connected, it can damage your NAND-X and/or CoolRunner. When you have finished programming, switch it back to NOR and then power on the Xbox.

I don't think this applies if you have a LPT cable to program your coolrunner, because I've been reading out the NAND with my NAND-x and programming the coolrunner at the same time for awhile to save a little time.

[fratslop]

i guess not as if you read my post i replied about why this isnt 14717+ and thats because rgh 2.0 is needed that isnt out on any fat yet and wouldnt be included in this release if it could be patched and stop 2.0 on all fats

The method was released for KEY RECOVERY. How many ppl here made sure they got the brand new official updates applied to their xenons that don't have usable dvd drives in them? Common sense says not many, if any.

and let me adjust my cornoa comment to make you happy
"corona without the current HANA point"

Please, dont hurt yourself trying to make me happy, but its nice to be accurate rather than convey misinformation, is it not?

why is everyone here looking to bitch these days

hmmm, i stated a useful fact, posted a useful link, and asked a rhetorical question using you as an example.
Please dont take it personally, definitely not trying to argue w/ you. This can all be done in PM, no?