Martin C
VIP Member
Provided the CB update and eFuse burn doesn't prevent the previous CB from booting, yes.
Already passed yours on!
New 2.0.14717 Dashboard - Security Changes
- Thread starter Xecuter
- Start date
Thats all results i can give you. This console no longer has CR installed as it was only to retrieve dvd key and put it back to stock.It's not my console. I was looking at the screens posted by axee44 on the previous page of this thread.
We'd like to know his results
thanks i was confused for a moment as to if the slims were not getting this or it just didnt affect them. so if they did this to the phat's does anyone think they can do this in a different way to the slim's??
---------- Post added at 09:06 ---------- Previous post was at 09:03 ----------
sorry uber i did read those but as i said i got confused as to if i should even see the update and if so what it would do. i understand it now!! thanks
Thanks Martin. I'm just talking about booting Xell - the exact same ecc file you built from your previous NAND image, so the new CB should be out of the equation.
Anyway, I'm looking forward to learning the details!
Martin C
VIP Member
It's irrelevent - if the eFuse burned was to stop previous CBs from booting then it won't work. It's the same situation as when JTAG'd consoles were blocked out and older CBs were unavailable.
So has it been 100% proven yet RGH has been blocked out on both slims and phats just for the record.....
Martin C
VIP Member
It's not looking good - CB has changed so eFuse would have been burned and therefore irreversable.
I wonder how many people now wish they would have applied eFuse protection on their phat RGH console!
Martin C
VIP Member
What's interesting is that 360 Flash Dump Tool reports the PD for CB to be 0x000000 (zero-paired), but this obviously can't be the case.
---------- Post added at 14:52 ---------- Previous post was at 14:51 ----------
---------- Post added at 14:52 ---------- Previous post was at 14:51 ----------
They said that 2 stage CB didn't affect slims. If MS have released a new CB, it'll need to be patched before it can boot.so wait everyone was saying this didnt affect the slims?
xbox360 hacker
BANNED
This is the very reason i sorted the eFuse protection on my rgh phat
cant be to carefull. Am not allowing my slim unmodded console on line till i know if they will still be able to rgh after the update. If push comes to shove i will be just getting a new slim next week for my live account.
Martin C
VIP Member
I remove R6T3 on all phat consoles I RGH and JTAG for this reason.This is the very reason i sorted the eFuse protection on my rgh phat
Even if you are dual-booting, you're better to build a retail NAND with the right tools rather than let MS do it for you.
I just built a glitch image with ldv at 13, stuck it on my falcon, the coolrunner wont even flash now, it just sits there with a red light.
re flashed to latest update, booted first time, with coolrunner se to prg, (turned off)
switch it back to normal it just sits there with solid green and red lights.
re flashed to latest update, booted first time, with coolrunner se to prg, (turned off)
switch it back to normal it just sits there with solid green and red lights.
Last edited:
Just curious what other tools you looked at it with. RGBuild2 showed different values on my Xenon dumps for CD and CE than 360FDT did.
That really sucks. I was hoping that wouldn't be the case.
Last edited:
it's not that bad,
I have a retail console for someone now,
and a spare coolrunner for use another day.
someone has to take one for the team, otherwise there wont be any progress made.
lol so much for microsoft NOT being able to kill it with an update
Last edited:
Martin C
VIP Member
From what I can see it's confirmed: MS have rolled out CB_B (2nd stage bootloader) to non CB_B consoles. See attached images for before and after.
Last edited:
Lol, I wasn't taking any pity on you as I'm sure you knew it was a risk. I was planning on doing it with my RGH Falcon before I saw your post. We all saw a preview of this with the beta dash, then nothing happened in 14699. MS was just being a big cock-tease.it's not that bad,
I have a retail console for someone now,
and a spare coolrunner for use another day.
someone has to take one for the team, otherwise there wont be any progress made.
lol so much for microsoft NOT being able to kill it with an update
I am going to take before and after dumps of a Zephyr I reverted back to retail. I wasn't happy with it's 35% boot rate. (Yes I know I was lucky for it to even boot to FreeBOOT in the first place.)
so does that mean were screwed full stop, or is it possible to find a way round it with the dumps and cpu keys?
Martin C
VIP Member
Not sure - CB_B on phat consoles wasn't possible previously, but more focus may be on it now that it appears all consoles will be taking it.