New 2.0.14717 Dashboard Affects RGH - Fixed for Slim Posted by XanTium | February 16 22:09 EST | News Category: Xbox360

From team-xecuter.com: [QUOTE] The new 2.0.14717 dashboard is being rolled out globally this week and so far we have seen possible changes to the CB that may affect RGH consoles. As always we suggest that you do NOT update until it has been investigated further. UPDATE: As you know the CB on Phat and Slim were updated with the recent 14717 update, disabling the RGH Glitch mod. While the Phat solution is a much more in-depth problem (work on CB_B has been ongoing for several weeks in anticipation of this so we are well placed to have news very soon), we have already been able to patch the Slim RGH to be fully functional again. Didn't take long thanks to Old Skool The fix has been confirmed by a number of team members and we are waiting for feedback from some European testers too and will get the files packed up for release asap. I'd just like to say what a sweet tool J-Runner was for doing all this [/QUOTE] News-Source: team-xecuter.com

Wow! Did MS really think that changing the CB would put a stop to the RGH??

I thought they did a lot more than just changing the CB, I read somewhere (can't remember where) that they even change the way the bootloader works and other stuff.

I do hope you know that all CB´s on phats (even before the update) couldn´t be RGH:ed as it was split into CB_A and CB_B.

The people involved are also raising a cautious finger, telling us, that even though the new 2BL might be circumvented it isn´t sure that you can get your CPU key. So if you do not have it you might be SoL...

So yeah, MS might stop RGH on phats, and thats a pitty, as they are often faster to glitch then slims...

Does this mean if you have an unmodded system with the new updated, it is now impossible to RGH it? i thought they had said that this hack would not be patchable by microsoft with software updates and require a hardware revision?

If I don't care about RGH (interested only in backups), is it confirmed that it's safe (meaning safe on LIVE) to update?

On slims it is looking good, but nothing is set in stone right now. For the time being, all and all, it is "wait and see"




No, no word from C4E yet if it is safe to update or not, so just wait.

On slims they said that, its always been said that it could be patched on phat consoles. So we will just have to wait and see. No one ever expected another homebrew hack so we were lucky to get the RGH.

Thanks!!!!

Or to be 100% correct:

Wait for TX and Team Jungle to CONFIRM. You´ll see it on TJ´s twitter before it´s on c4espeaks in 99% of the cases...

Thats the first I've heard about that. That sucks, I have 3 phats and no slims.
Can you buy new slims that are still RGH-able? Or have they 'fixed' it on the new ones?

don't read much do you? in the initial release readme by gligli he stated this (trinity can't be patched). On slims its unpatchable as theres no revocation fuses (eFuses if you will), so we can just flash the 'older' CB to the unit and we're good (assume thats no longer possible as speculated).

New slims since the RGH was released are not glitchable. They are corona boards and don't have the HDMI chip. Aside from that MS merged a bunch of chips together.. May not be possible to slow the HANA or CPU down to get good timing.

Right now any unit on the latest 717 dash is NOT glitchable!
MS did a LOT of work under the hood of this dashboard. Staggered release is also major notice that somethings up - they want everyone to get this.
Theres a reason TX, TJ, C4E, TMT, Xk3y and others haven't said much on it.

Hopefully the $$$ made from the RGH and replacement PCBs will help fund R&D for the masses and not be capitalized on by the groups.

Your best bet is to glitch them and get your CPU keys ASAP.

ahh that sucks.

This is what I have read from all over the place and I thought I would some it all up here so here goes.

The new update 2.0.14717.0 updates the CB of the Phats and the Dual CB of the Slim also bowing an efuse which updates the CB LDV. These new CB's have the POST disabled, for the RGH to work the CPLD has to know the XBOX’s current POST. This is because the CPLD uses the POST so it can time the glitch correctly and reset the CPU at the correct time, plus know when the console has restarted. This is so if the glitch fails the CPLD will know when to try and glitch again.

So why slims still work

This is because the slim has a dual CB, CB_A and CB_B this is different to the Phats consoles which only have CB. (But some Phats have dual CB's as well so I will come back to that in a bit this is for the slim)

Now what is the CB anyway why are we glitching it for the RGH, the CB is a boot loader that is encrypted with the 1BL key. So we don't need the CPU key to decrypt it, but it is still signed by the private key so we can't just go and edit it to do what we want. There is not much information on this boot loader apart from it is stored in the NAND and it checks, decrypts then loads the next boot loader, which for Phats it is CD for slims it is CB_B.

Now because the slim’s changed the boot chain and added an extra boot loader, by splitting the CB in to two parts. They gave us a place in the boot chain to glitch that has a boot loader that is writable because it’s stored in the nand it can be decrypted with the 1BL key which they didn’t change, when they know that we still have it from the last exploit. Also now doesn’t have a Lock Down Value because it has been moved to CB_B so it doesn’t matter what the efuse values are this boot loader will always load. This is why the RGH is not patchable on trinity boards at least.

Now for the slim RGH we glitch the CB_A check of the CB_B SHA hash to return true when the hash is wrong because we have a patched CB_B. This CB_B has been patched so we can run own CD which loads the CE which is the base kernel and hypervisor, so we can do anything from there. So to some up you can just go and update the slim’s to the newest dash it doesn’t matter. All you will have to do is change the CF Lock Down Value because even in the hacked kernel it still has to match fuse line 7.

So why do Phats get patched

Because the Phats only have the CB boot loader which does have a Lock Down Value they can’t still run the old 6750 CB. Now we still can edit the CB because it is stored in the nand we do it for the RGH any way by making the CB zero-paired, this is so we can use a modified SMC image. But doing this doesn’t break the signature if we edited the LDV to match the new CB LDV it would break the signature. So the old CB 6750 CB won’t run anymore because the Lock Down Value isn’t going to match the fuse line 2 anymore because it was updated when the efuse was blown. And if were run the new CB that matches the efuses POST is disabled.

Now for Phat dual CB’s, there is the 6751 and the 6752 CB now there isn’t much information on these CB’s and I have never had a console with one. So I haven’t seen or looked at them but there are some reports of some XBOX’s with the 6751 CB’s being downgraded, to the 6750 CB and glitching. So that means the LDV wasn’t updated for the 6751 CB and it is the same as the 6750 CB, but there aren’t any reports of the 6752 being downgraded to the 6750 CB. But anyway the dual CB for Phats would have mean updated as well. Hell the new CB on all the Phats could be dual now I haven’t seen one only read that the POST has been disabled. (Will update when I get more information on this)

But it isn’t over for Phats

Gligli said himself that apparently CB 9188 can run on fats, so we could still glitch the Phats using the slim’s dual CB. Plus the glitch would work better on the Phats because we wouldn’t have to use the HANA to slow down the CPU we can use CPU_PLL_BYPASS. Which slows the CPU more than HANA PLL’s can do. And the slower the CPU the better the CPLD can time the glitch and reset the CPU. So we will just have to wait and see what happens for Phats.

No posts come on this tuck a while to research and write

The all mighty claimed that the new dash is safe for LT3.0
http://c4evaspeaks.com/c4eva-2012-02-18-c4e/

Would we have to reprogram our Coolrunners whenever M$ rollout a new CB update even on Slims?

UPDATE - Since I don't think the LDV in CB_B has been patched out because it didn't matter till now, you will have to update this as well. But if you did patch it out of the CB_B then the hack would always work for slim, and the only thing you have to update is the CF/CG and the freeboot patches to the kernel. Plus I don't see why they don't just patch the CF LDV would make things easier.

Are you merged my topic in to this one cool.

ive been trying to find a post i was reading yesterday the update killed his glitch/dual boot
in that post he states nothing he has tried has worked changing ldv etc all he can get is new dash stock nand nothing else will boot!
ive been waiting for this since christmas i said msoft would knee jerk already had two regulars with jtags cancel rgh upgrades two brothers actually to quote"if were goin to have to patch dashes/games theres no point upgrading" a lot of those attracted to rgh liked the fact it ran the current dash non techicals dont like patching games/dashes
what they have done is killed the hack stone dead!
the truth is its probably going to have to be fully reworked even on slims
im just glad that ive got five coolrunners and non updated 360s to go with them
if your about we could use your input cos this wont be easy to fix

I wasn't going to bother removing R6T3 on my RGH mods but now it sounds like I probably should. I'm doing a Jasper with CB 6750 today, going to write protect those fuses! To hell with live and dual boot!

.. those aren't conflicting goals: build a retail image with xebuild just like you would for a modified image.

thats what we will have to do now till we know what the score is
untill users report back here its all up in the air again!

Whaaaaaat?

I can build a live image and go online with an old protected CB?

I don't see why 2 people with JTAG's are cancelling RGH orders.

For a JTAG, you had to build a custom freeboot image of the latest dash and flash it to your NAND. The RGH is no different, even with this dashboard update. Those of us with RGH images just have to wait for a freeboot release so we can update to 14717 (if we wanted to). All this means is that currently updated FAT's cannot be glitched at this point in time.

I believe slim's can't right now either, unless you have the CPU key. There was some talk on the TX forums that the updated CB has somehow stopped Xell from loading on a slim, but if you got your key prior to the update, then you're fine.

i agree...

right i should have been more clear the two rgh were for dual boot which is dead now
even if you build a dual boot 360 from an uncontaminated rgh when the stock goes live it updates
you wont be able to refuse the update for ever eventually it will be mandatory for live(real reason for two nands)

someone found a way to decrypt SLIM cb_b on dash 14717
so need for a previous dump + cpukey!

Shakes head this is what i get for not keeping up with forums

spent a while wondering why xell wouldnt boot when i have never had an issue with slims .... do a small search to find this update crap lol .....hate wasting time

shrugs guess buddy sol