Xenon Glitch :(:( Stby_clk Found Options

[ziomal155]

Hello
I'm new here. I know little English. I have a few questions.

First Why can not glich xenon? - I have plugged all the cables including STBY_CLK that I found.

Second *. I built using multibuilder ecc 0.7. I added a line to build.py:
[0xb92ed1ba, "Xenon, version 1.51", [[0x1180, 0x00, 0x00]]],
Is it good?

Third I changed the file in VHDL. Timing is 1550 + X. X is from 0 to 256 at 10xglich. Unfortunately they failed to run Xella: (Why? This is a wine VHDL'a or *. ecc?

[ziomal155]

I am writing again! STBY_CLK is xenonie. It is exactly 48MHz.

[ruciz]

I am writing again! STBY_CLK is xenonie. It is exactly 48MHz.

From what I gathered the Xenon couldn't be done because the ANA chip wasn't scalable.
Yes It would slow down, Yes it would glitch/pulse correctly, But then you are stuck.
Only way to regain full speed was a reboot - in which, you of course are not glitched - cycle repeats.

Hitting it at full speed would be possible, I think some people had succeeded at one point or another - maybe dealt with the slow clock to get their CPU key, but its not as reliable as newer mainboard revs are.
The developers sat on the glitch waiting for the right time to release. Im sure in that time they considered all logical angles to adapt it without success.

Considering how glitchy those boards themselves are its likely for the best anyway.
Heres further reading http://www.xboxhacker.org/index.php?topic=...33083#msg133083

hopefully it is indeed the CPU and not able to be replicated by code that MS could have put in the latest dashboard

This post has been edited by ruciz: Feb 17 2012, 11:28 PM

[tyiphius]

From what I gathered the Xenon couldn't be done because the ANA chip wasn't scalable.
Yes It would slow down, Yes it would glitch/pulse correctly, But then you are stuck.
Only way to regain full speed was a reboot - in which, you of course are not glitched - cycle repeats.

Hitting it at full speed would be possible, I think some people had succeeded at one point or another - maybe dealt with the slow clock to get their CPU key, but its not as reliable as newer mainboard revs are.
The developers sat on the glitch waiting for the right time to release. Im sure in that time they considered all logical angles to adapt it without success.

Considering how glitchy those boards themselves are its likely for the best anyway.
Heres further reading http://www.xboxhacker.org/index.php?topic=...33083#msg133083

hopefully it is indeed the CPU and not able to be replicated by code that MS could have put in the latest dashboard

I think Team-x already has a way to glitch xenons and they'll probably release it when they release the demon.
http://team-xecuter.com/forums/showpost.ph...p;postcount=429