Advertisement
Help Keep Boards Alive. Support us by going ad free today. See here: https://subscriptions.boards.ie/.
If we do not hit our goal we will be forced to close the site.
Current status: https://keepboardsalive.com/
Annual subs are best for most impact. If you are still undecided on going Ad Free - you can also donate using the Paypal Donate option. All contribution helps. Thank you.
If we do not hit our goal we will be forced to close the site.
Current status: https://keepboardsalive.com/
Annual subs are best for most impact. If you are still undecided on going Ad Free - you can also donate using the Paypal Donate option. All contribution helps. Thank you.
https://www.boards.ie/group/1878-subscribers-forum
Private Group for paid up members of Boards.ie. Join the club.
Private Group for paid up members of Boards.ie. Join the club.
Xbox 360 Reset Glitch Hack - Unsigned Code on current Kernels incl. X360 SLIM
Comments
-
-
-
-
-
-
Advertisement
-
-
-
-
-
-
Advertisement
-
-
-
Its to do with the lack of HDMI port I read (The glitch uses the HDMI chip)
Nick
The glitch uses a call on the HANA/ANA to slow the clock of the CPU to get the timing right but the Xenon has a HANA/ANA chip so I can't see why that's the problem
Oh well, either way a Xenon version doesn't look likely since they're the most abundant version available cheaply and the guys didn't release one initially 0 -
TouchingVirus wrote: »The glitch uses a call on the HANA/ANA to slow the clock of the CPU to get the timing right but the Xenon has a HANA/ANA chip so I can't see why that's the problem Oh well, either way a Xenon version doesn't look likely since they're the most abundant version available cheaply and the guys didn't release one initially
Could be due to different pinouts? The xenons have a surface mount style ANA chip while the HDMI versions are mounted by BGA0 -
-
Could be due to different pinouts? The xenons have a surface mount style ANA chip while the HDMI versions are mounted by BGA
Ah yes, I suppose I could change around my original hypothesis that it was a difference in CPU revision to a difference in HANA/ANA revision preventing the lowering of the clock in Xenon models. I would read more into it but the bottom line doesn't change, no Xenon exploits
0 -
-
-
Just don't update the box :P:P
Nick
Indeed, once a console is jtagged there's very very little that can't be done on it with regards future games/security etc.
New hardware revision? Unlikely.
New mandatory dash? Highly likely.
Patchable? Maybe not, but with added security I'm sure MS will find a way to compensate?
Will it matter? The XBL users will have to go with it. It's buy a 2nd console time in my eyes though
0 -
New hardware revision isn't likely? Nah, of course it is. If this can be defeated with a hardware solution they'll see what they can do in future slim revisions - it's Microsoft and they're changing up the DVD drives often enough to let you know they mean business
If they have a software solution to fix it then yes, they'll be releasing a new dash so don't update.
Get your glitchable xbox and get your virgin for Live; the homebrew train is here and isn't going anywhere :P0 -
Advertisement
-
TouchingVirus wrote: »New hardware revision isn't likely? Nah, of course it is. If this can be defeated with a hardware solution they'll see what they can do in future slim revisions - it's Microsoft and they're changing up the DVD drives often enough to let you know they mean business If they have a software solution to fix it then yes, they'll be releasing a new dash so don't update.
Get your glitchable xbox and get your virgin for Live; the homebrew train is here and isn't going anywhere :P
I don't know, you'd really have to be privvy to the $$$ figures to make a good guess at their strategy. Would it pay to r&d different cpu architecture, implement the change at the manufacturing level, & possibly re-engineer the current dash kernel for the new architecture...as opposed to investing more in the successor which is roughly due in around a years time. Maybe it would pay off, maybe economically, it won't really affect MS & could in fact boost sales 0 -
I don't know, you'd really have to be privvy to the $$$ figures to make a good guess at their strategy. Would it pay to r&d different cpu architecture, implement the change at the manufacturing level, & possibly re-engineer the current dash kernel for the new architecture...as opposed to investing more in the successor which is roughly due in around a years time. Maybe it would pay off, maybe economically, it won't really affect MS & could in fact boost sales
You're mad about the E3 2012 successor bit
Of course it would make no sense to R&D if that's the case, but I really don't think it is. Maybe a name/architecture announcement, very early prototype in E3 2012 is what I'd put my own money on, with the Xbox reaching EOL around late 2013/early 2014. It wouldn't be a CPU architecture change either, just hardware changes necessary to alter the POST boot process with updated CBs to block glitching is all that'd stop this attack vector. 0 -
-
-
-
-
TouchingVirus wrote: »You're mad about the E3 2012 successor bit Of course it would make no sense to R&D if that's the case, but I really don't think it is. Maybe a name/architecture announcement, very early prototype in E3 2012 is what I'd put my own money on, with the Xbox reaching EOL around late 2013/early 2014. It wouldn't be a CPU architecture change either, just hardware changes necessary to alter the POST boot process with updated CBs to block glitching is all that'd stop this attack vector.
I didn't mean to imply that in a year we'd all be looking to jtag 720's, just its announcement & a timescale for introduction. A new hardware revision is a fairly massive deal though, particularly with the slim so new still. I would imagine MS will probably point investment heavily towards a newer platform, especially with XBL unscathed by this...who knows though 0 -
-
So can someone very basically sum up whats involved in this? Everything I find is far too detailed and fragmented for someone who's just a bit curious about it.
Is there extra hardware involved?
Is there soldering needed?
Yes & Yes
Basically:- Dump the nand using a nand programmer
- Install Python & variables on your pc (programmimg language/scripts)
- Use a Python command to modify your dumped nand image
- Use the nand reader to flash the newly modified nand image, back onto the 360.
- Additional hardware required, for precise execution of the glitch, programme this new hardware over lpt with your pc via Impact.
- Solder additional hardware to necessary points on the 360's board.
- Boot the console
0 -
Advertisement
-
Advertisement