Sunday, 18 September 2011
Xbox TV launching this holiday season
Modern Warfare 3 Devs Concerned About Franchise Momentum
Modern Warfare 3 Sees No Prestige This November
Halo: Combat Evolved Beta Coming October 4th
Battlefield 3 has Jets in Rush Mode for PS3, Xbox 360, and PC
Xbox Live on Windows 8: True Cross Platform Gaming
Developer Refutes Claims that Xbox 360 Offers Inferior Tech
Friday, 16 September 2011
Battlefield 3 Will Feature 9 Maps with 45 Variations
Thursday, 15 September 2011
Medal of honor disc required to play Battlefield 3 beta early
Dead Island Devs Push Back DLC, Refocus Energy on Bug Squashing
Dead Island ships 1million first week,2million worldwide expected by week's end
Nyko Zoom for Kinect available now, works
Goldeneye: Reloaded Hits PS3, Xbox 360 In November
Gears of War 3 midnight launch plans detailed
Max Payne 3: First Trailer
Wednesday, 14 September 2011
Modern Warfare 3 Game Security a Top Priority
Battlefield 3 Two Disc Breakdown on Xbox 360
Activision claims CoD XP was second most-watched livestream ever
FIFA 12 demo released now available on Xbox LIVE
Xbox Live, Xbox.com currently down
EA Community Manager Weighs In On Battlefield 3 Leak
Max Payne 3 development cost $105m, estimates Analyst
Watch an Elder Scrolls V: Skyrim Video Dem
Monday, 12 September 2011
EA: We don’t expect Battlefield 3 to beat Modern Warfare 3
Battlefield 3 Beta Running on Xbox 360
Saturday, 10 September 2011
Infinity Ward's day in court: May 7, 2012
Xbox 360 dashboard update beta coming in October
Modern Warfare 3 to Discourage Campers
“When we looked at that with MW3, we decided that we wanted to get the cool part of verticality and the cool kind of engagements, but we didin’t want to make it so complicated that anywhere you ran you were under fire or that there was danger from every single point. We wanted to have a really good flow to match, and I think that is something CoD4 had nailed really well. I think Crash is still considered one of the best multiplayer maps in any FPS. It has good flow, so our designers spent a lot of time going back to the old Call of Duty maps and other older games to look at the great maps from other games... “Having a map with good flow makes you feel comfortable moving through the map,” he said. “If the flow is not good, people won’t move as much because they are paranoid of getting shot. So, having a good flow is one thing, the other thing is to try not to put – well, you always put these points in because it is impossible to test as much as the public will on day one, honestly when the game ships, during the first 10 minutes you will have more test time on the game than we have in the entire two years of development because of the numbers. Map flow is great and all, but one of the major reasons why people camp in Call of Duty is because of the overpowered Killstreak perks that reward you for doing so. We'll see how Call of Duty's multiplayer finishes up come November, but Infinity Ward and Sledgehammer have been quite public about this war on campers in Modern Warfare 3.
Expect Quicker Updates and Patches in Modern Warfare 3
'Consoles have hit their peak' - say analysts
Battlefield 3 preorders hit 1.25 million
Max Payne 3 Release Date
Modder creates PC case with both PS3 and Xbox 360 inside
First Gears of War 3 Console Unboxing
Blu-ray Coming To Xbox 360 - Rumor
Sunday, 4 September 2011
September Game Release Roster
Volume wise September is a mammoth month for new and re-released titles – come and check out the full roster here:
Click to View September Roster
Xbox finally joins PS3 with new 3D update
Wednesday, 31 August 2011
Dead Island launch trailer released
MS: New dashboard not just for Kinect users
He added: "I think it's a pretty happy medium and that's been our goal since the launch of Kinect, to make sure we're creating great content like Star Wars, Sports and great family content, but also making sure we're not losing the Gears of War, Halo and Call of Duty fans that really built the Xbox brand.
"So making sure we've got great content for both audiences in a combined platform is a big challenge. I think the new dashboard is still super-fast to navigate around."
Microsoft's official philosophy for the new dash is "all the entertainment you want, with the people you care about, made easy."
3D support confirmed for Halo Anniversary
The news follows last week’s announcement that fellow Xbox 360 exclusive Gears of War 3 would ship with full stereoscopic 3D support.
With games like Crysis 2 and Call of Duty: Black Ops also boasting 3D visuals on the system, Xbox 360 is slowing building a catalogue of titles that offer the functionality – though it still falls far behind Sony and its widespread 3D support.
Gears 3 passes 1.3 million pre-orders
DICE: Don’t worry about Battlefield 3 on console
Monday, 29 August 2011
Call of Duty Modern Warfare 3 multiplayer modes leaked
The massive world of Skyrim to fit on one disc for Xbox 360
Walmart to honor 360 4GB Kinect bundle @ $249 error this week
First Adroit accessible controller, 'Switchblade,' revealed
The Switchblade is built for Xbox 360, but adapters will be available for use on PC and PS3. There's no date yet, and no official price, but Thrifty Nerd reports that it'll be "a few hundred dollars." It's pricey, but not compared to the cost of having your own customized controller built.
Gears of War 3 Season Pass Announced
Xbox 360 Slim Models Hacked And JTagged
**********************************
* The Xbox 360 reset glitch hack *
**********************************
Introduction / some important facts
===================================
tmbinc said it himself, software based approaches of running unsigned code on the 360 mostly don’t work, it was designed to be secure from a software point of view.
The processor starts running code from ROM (1bl) , which then starts loading a RSA signed and RC4 crypted piece of code from NAND (CB).
CB then initialises the processor security engine, its task will be to do real time encryption and hash check of physical DRAM memory. From what we found, it’s using AES128 for crypto and strong (Toeplitz ?) hashing. The crypto is different each boot because it is seeded at least from:
- A hash of the entire fuseset.
- The timebase counter value.
- A truly random value that comes from the hardware random number generator the processor embeds. on fats, that RNG could be electronically deactivated, but there’s a check for “apparent randomness” (merely a count of 1 bits) in CB, it just waits for a seemingly proper random number.
CB can then run some kind of simple bytecode based software engine whose task will mainly be to initialise DRAM, CB can then load the next bootloader (CD) from NAND into it, and run it.
Basically, CD will load a base kernel from NAND, patch it and run it.
That kernel contains a small privileged piece of code (hypervisor), when the console runs, this is the only code that would have enough rights to run unsigned code.
In kernel versions 4532/4548, a critical flaw in it appeared, and all known 360 hacks needed to run one of those kernels and exploit that flaw to run unsigned code.
On current 360s, CD contains a hash of those 2 kernels and will stop the boot process if you try to load them.
The hypervisor is a relatively small piece of code to check for flaws and apparently no newer ones has any flaws that could allow running unsigned code.
On the other hand, tmbinc said the 360 wasn’t designed to withstand certain hardware attacks such as the timing attack and “glitching”.
Glitching here is basically the process of triggering processor bugs by electronical means.
This is the way we used to be able to run unsigned code.
The reset glitch in a few words
===============================
We found that by sending a tiny reset pulse to the processor while it is slowed down does not reset it but instead changes the way the code runs, it seems it’s very efficient at making bootloaders memcmp functions always return “no differences”. memcmp is often used to check the next bootloader SHA hash against a stored one, allowing it to run if they are the same. So we can put a bootloader that would fail hash check in NAND, glitch the previous one and that bootloader will run, allowing almost any code to run.
Details for the fat hack
========================
On fats, the bootloader we glitch is CB, so we can run the CD we want.
cjak found that by asserting the CPU_PLL_BYPASS signal, the CPU clock is slowed down a lot, there’s a test point on the motherboard that’s a fraction of CPU speed, it’s 200Mhz when the dash runs, 66.6Mhz when the console boots, and 520Khz when that signal is asserted.
So it goes like that:
- We assert CPU_PLL_BYPASS around POST code 36 (hex).
- We wait for POST 39 start (POST 39 is the memcmp between stored hash and image hash), and start a counter.
- When that counter has reached a precise value (it’s often around 62% of entire POST 39 length), we send a 100ns pulse on CPU_RESET.
- We wait some time and then we deassert CPU_PLL_BYPASS.
- The cpu speed goes back to normal, and with a bit of luck, instead of getting POST error AD, the boot process continues and CB runs our custom CD.
The NAND contains a zero-paired CB, our payload in a custom CD, and a modified SMC image.
A glitch being unreliable by nature, we use a modified SMC image that reboots infinitely (ie stock images reboot 5 times and then go RROD) until the console has booted properly.
In most cases, the glitch succeeds in less than 30 seconds from power on that way.
Details for the slim hack
=========================
The bootloader we glitch is CB_A, so we can run the CB_B we want.
On slims, we weren’t able to find a motherboard track for CPU_PLL_BYPASS.
Our first idea was to remove the 27Mhz master 360 crystal and generate our own clock instead but it was a difficult modification and it didn’t yield good results.
We then looked for other ways to slow the CPU clock down and found that the HANA chip had configurable PLL registers for the 100Mhz clock that feeds CPU and GPU differential pairs.
Apparently those registers are written by the SMC through an I2C bus.
I2C bus can be freely accessed, it’s even available on a header (J2C3).
So the HANA chip will now become our weapon of choice to slow the CPU down (sorry tmbinc, you can’t always be right, it isn’t boring and it does sit on an interesting bus
So it goes like that:
- We send an i2c command to the HANA to slow down the CPU at POST code D8 .
- We wait for POST DA start (POST DA is the memcmp between stored hash and image hash), and start a counter.
- When that counter has reached a precise value, we send a 20ns pulse on CPU_RESET.
- We wait some time and then we send an i2c command to the HANA to restore regular CPU clock.
- The cpu speed goes back to normal, and with a bit of luck, instead of getting POST error F2, the boot process continues and CB_A runs our custom CB_B.p>
When CB_B starts, DRAM isn’t initialised so we chose to only apply a few patches to it so that it can run any CD, the patches are:
- Always activate zero-paired mode, so that we can use a modified SMC image.
- Don’t decrypt CD, instead expect a plaintext CD in NAND.
- Don’t stop the boot process if CD hash isn’t good.
CB_B is RC4 crypted, the key comes from the CPU key, so how do we patch CB_B without knowing the CPU key?
RC4 is basically:
crypted = plaintext xor pseudo-random-keystream
So if we know plaintext and crypted, we can get the keystream, and with the keystream, we can encrypt our own code. It goes like that:
guessed-pseudo-random-keystream = crypted xor plaintext
new-crypted = guessed-pseudo-random-keystream xor plaintext-patch
You could think there’s a chicken and egg problem, how did we get plaintext in the first place?
Easy: we had plaintext CBs from fat consoles, and we thought the first few bytes of code would be the same as the new CB_B, so we could encrypt a tiny piece of code to dump the CPU key and decrypt CB_B!
The NAND contains CB_A, a patched CB_B, our payload in a custom plaintext CD, and a modified SMC image.
The SMC image is modified to have infinite reboot, and to prevent it from periodically sending I2C commands while we send ours.
Now, maybe you haven’t realised yet, but CB_A contains no checks on revocation fuses, so it’s an unpatchable hack !
Caveats
=======
Nothing is ever perfect, so there are a few caveats to that hack:
- Even in the glitch we found is pretty reliable (25% success rate per try on average), it can take up to a few minutes to boot to unsigned code.
- That success rate seems to depend on something like the hash of the modified bootloader we want to run (CD for fats and CB_B for slims).
- It requires precise and fast hardware to be able to send the reset pulse.
Our current implementation
==========================
We used a Xilinx CoolRunner II CPLD (xc2c64a) board, because it’s fast, precise, updatable, cheap and can work with 2 different voltage levels at the same time.
We use the 48Mhz standby clock from the 360 for the glitch counter. For the slim hack, the counter even runs at 96Mhz (incremented on rising and falling edges of clock)
The cpld code is written in VHDL.
We need it to be aware of the current POST code, our first implementations used the whole 8 bits POST port for this, but we are now able to detect the changes of only 1 POST bit, making wiring easier.
Conclusion
==========
We tried not to include any MS copyrighted code in the released hack tools.
The purpose of this hack is to run Xell and other free software, I (GliGli) did NOT do it to promote piracy or anything related, I just want to be able to do whatever I want with the hardware I bought, including running my own native code on it.
Credits
=======
GliGli, Tiros: Reverse engineering and hack development.
cOz: Reverse engineering, beta testing.
Razkar, tuxuser: beta testing.
cjak, Redline99, SeventhSon, tmbinc, anyone I forgot… : Prior reverse engineering and/or hacking work on the 360.
1)Method to Run unsigned code on Slim!