Xbox 360 Reset Glitch Hack patched on Phat consoles

[Fudge]

Just got done soldering, dumping, updating, dumping, starting games, and dumping again. This was on my Xenon console that was unbanned by MS. There's some serious changes going on with the bootloader and CB. Here are before and after dumps in 360 Flash Dump Tool.

2BL [CB] has changed from 7373 to 7377. This value has the final say whether your console can be Jtag'd/RGH'd. The 2BL number depends on the motherboard revision.

4BL [CD] shows up empty.

5BL [CE] has changed from 1888 to 5968. 5BL has been the same on every console and dash version since Adam walked out of the Garden of Eden. It's never changed. 360FDT also shows the Nand as "Retail Unknown Model" instead of "Retail Xenon (v1.0)".

The latest version of 360FDT is from 2010. So I started thinking, "Maybe MS changed the format of the Nand a little so that 360FDT can't fully read it anymore."

For those few of us who have played around with the newest RGLoader (turns your RGH console into a DevKit), a newer tool came with it called RGBuild2. I opened the 14717 dump in it and I was right.

RGBuild2 shows a 2-stage CB along with the following values:
CB_A (2BL) = 7377
CB_B (2BL) = 7377
CD (4BL) = 7377
CE (5BL) = 1888 (Still the same)
6BL and 7BL are still the same. 360FDT now reads a wrong value for 4BL and 5BL.

For illustration, here's a Nand dump from my MS-refurbished Jasper with a 2-stage CB. It has an 3BL [CB] value (2BL[CBv1] = CB_A; 3BL[CBv2] = CB_B).

360FDT should have showed something similar from my Xenon 14717 Nand dump, so MS obviously changed some things around in the bootloader. 2-Stage CB's prevent PHAT consoles from being RGH'd. This could very well be the start of MS cutting down on the number of RGH-able consoles.

I know the above is little over most of your heads and you just want to know if anything has changed as far as backups go. This console was flag-free before I updated. After updating, I started a couple of XGD3 games offline and online and dumped the Nand again. Still no flags.

I don't have the CPU key of this console, so even if did know what to look for as far as new security scheme changes, I couldn't decrypt the KV anyway. As of 3:30 PM MST, none of my other online consoles (3 of them) still haven't asked for the update.

My instinct says there's nothing in this to try to counter LT+ 3.0 but I'm no authority on anything so take it with a grain of salt.

It is currently unknown if Slim consoles are affected by this update. In any case though, if you plan on RGHing in the future you should probably stay of LIVE.

 

[notmeanymore]

Unless that patch occurred in the last 3 hours, I never received it. Odd.

 

[Fudge]

Unless that patch occurred in the last 3 hours, I never received it. Odd.

Not everyone has received the update yet. You'll likely have it sometime tomorrow.

 

[431unknown]

And the cat n' mouse game goes on some more. Sucks that they can patch it on phats.

 

[FireEmblemGuy]

I saw people talking about a small update that didn't seem to do anything. Didn't figure it was just MS pulling a Nintendo, though.

Wasn't it claimed that the RGH couldn't be patched out?

 

[FAST6191]

An interesting development, I think I might make a news post.

Those wishing to reread how it all works http://gbatemp.net/topic/306685-x360-the-reset-glitch-hack/ has some on the underlying theory.

 

[shakirmoledina]

if there is something i always think about its HW v SW. Any type of software can be done/hacked and prevented/secured but hardware... not possible if only hardware is used.
For example, tony hawks required a peripheral, can u remake a software for that? but many games require a higher software/firmware version, and u can bypass that.

we can transport so many software across the world in a few seconds but can we do the same for a simple thing such as a needle?

if there is a more reliable hack then it has to be hardware and that even can be hacked but only by its incomplete software implementation. its just an opinion but i think it is the way of life.

 

[FAST6191]

Not wishing to be the one that sends this right off topic

Hardware- there is programmable hardware these days ranging from simple programmable chips (they are still awesome though- see how many little electronics projects contain something like an arduino) to CPLDs to full on FPGA devices that at the cost of extra power (as in energy) and expense (although far cheaper ones exist) can and do operate in the same realms as dedicated hardware (if no dedicated chip exists it is often cheaper to stick a FPGA in there rather than set up a fab for said chips). For my money this has blurred the line between hardware and software and will continue to do so for the foreseeable future.
As for the peripherals- many things have been cloned but I look to the likes of the guitar hero patches for the DS where the addon was converted to buttons.

As for sending stuff might I direct you towards CNC in the various forms it takes, 3d printing, selective laser sintering and that whole world ( http://www.shapeways.com/ might be of interest). I try to avoid those that have a tendency to gush about it but I would say it would be hard to underestimate the potential.

On the matter of firmware unless it is truly tied to the likes of an FPGA as mentioned above (in which case it is probably just a lot trickier) most of what happens in consoles is either a simple check for new but using old methods (remember games take a while to develop) or still possible by various means. Indeed I am going to suggest that after implementation and troubleshooting most of computing revolves around making sure legacy stuff carries on working. Granted aspects of this are often considered some of the harder areas of computing/engineering in general but there are loads playing in that world.

 

[cory1492]

I won't go too far into it, but providing the details in the OP are true for all versions (CB updated, and I say provided because every update since the JTAG blocking CB update someone has come up with 'OMG CB has been updated!' posts which have proven inaccurate every time so far)... so long as you have your CPU key before you update you won't permanently lose your chance to use RGH, but it could take a great deal of time before a solid solution is released again for machines that are updated with a new CB.

M$ kinda shot theirselves in the foot on ever blocking RGH like they did with JTAG by giving us some CB code that doesn't have any lockdown check (trinity/slim CB_A can work on all revisions and as proven with trinity can also be glitched)... but you still need to know your CPU key to take adavantage of it.

 

[Armadillo]

I saw people talking about a small update that didn't seem to do anything. Didn't figure it was just MS pulling a Nintendo, though.

Wasn't it claimed that the RGH couldn't be patched out?

The claim of it not being patchable was for the slim I think.

 

[DjoeN]

I'm So gonna update my Xbox 360 Slim! with Kinect
(It's not modded in anyway and no intend to do so in the near future)
(I'm not talking about my Xbox360 Phat wit X360Key in it )

 

[DinohScene]

CB gets glitched so it "shouldn't" be patchable since it's the 1BL is stored in OTP and cannot be changed at all.

It's kind of similar to the old Wii's with a vulnerable boot1.
But we'll see if it is truly patchable.

I'm going to update my flashed box anyway since I already got a glitched Falcon

 

[codezer0]

Has there been any word on whether this has been verified okay for those of us using LT+ 3.0 ? Among other things, wondering whether this means I'll need to do my patching routine again. Strangely enough, never had success flashing from putting system update on a USB flash drive, but never had a problem with updating from online... then again, always took the precaution of flashing back to stock and ensuring it works before signing in and getting the system updates.

 

[DinohScene]

Afaik, you can update safely with LT 3.0 installed.

This just seems to be an RGH blocking update.

While the new dash seems safe for CFWs, it does however currently make the RGH impossible. But people are working on a solution and Team Xecuter already announced they will probably have a fix ready for SLIM consoles soon.

Source: Xbox scene