I know that this is all speculation and such, and I am not to familiar with the inner workings of the 360, but throwing crap into the wind, how about this..... So far, as far as we know, everything on the 360 is ran from either straight from chip or memory, including hypervision (which is why we can run the 360 without the HD, all the HD is used for is gamesaves, and if space allows it, swap file usage to reduce game loading times).
Knowing this, would it not be possible to directly attack the memory location where hypervision is at, disabling hypervision, in a manner, then running a buffer overflow to allow unsigned code?
If this is not how hypervision works, then sorry for the pointless rambles.
EDIT: I just noticed a flaw in my idea, the only way that this would work is if something could be launched before hypervision, anything afterwards would be pointless......just an idea I had...
This post has been edited by BlackWar: Nov 5 2007, 04:10 AM