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?

[ravendrow]

xenons cannot be glitched because the system halts when you send the pulse to PLL_BYPASS instead of resetting the CPU at least that is what i have been told

This post has been edited by ravendrow: Jan 15 2012, 08:10 PM

[ziomal155]

I disagree. I use pulse PLL console release of the original NAND, it normally turns on the console. The console also will certainly slow down, because it lasts longer posts.

Any other ideas why it does not work with RGH xenon?

[Aldanga]

Either hop on #libxenon on EFNet or head over to Xbox-Hacker. You're more likely to get a sufficient answer there.

[RavenPhoenix]

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?

The Xenon can not be glitched because it does not have the HANA chip which is required to do the timing for the hack to actually work. Unless you can implement an external counter or method to do the timing accurately then I'm afraid your efforts will be in vain.

[2121oyoy]

The Xenon can not be glitched because it does not have the HANA chip which is required to do the timing for the hack to actually work. Unless you can implement an external counter or method to do the timing accurately then I'm afraid your efforts will be in vain.

The other day I read this, front page of xbox-scene cboug the 360glitch:

As you know Corona (New motherboard revision after Trinity) were not Glitch compatible because the HANA chip had been removed which were needed for Timing through the CLK_STBY Wire.
The x360Glitchip v2 is the first world chip which doesn't need this point, and so become Corona Ready.

And then theres also the XAIO deal:
External Oscillator (Wiring to HANA is no longer required)

EDIT: I have to add that I am NOT saying that these things will work on XENON. Just that some of the reasons above may have been negated.

This post has been edited by 2121oyoy: Jan 21 2012, 10:29 PM

[K3thunder]

xenons cannot be glitched because the system halts when you send the pulse to PLL_BYPASS instead of resetting the CPU at least that is what i have been told

there seems to be missing signals with xenon's maybe i have stumbled upon something "GND Breaking"

[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