I know it sounds noobish but hear me out. I want to use the coolrunner just to do the RGH to unflag my secdata using this tut : http://team-xecuter.com/forums/showthread.php?t=74138 But I kinda want to leave it connected for future use without the hassal of reinstalling it, but still get on live. So if just reinstall a clean retail Nand image and some how disable the coolrunner during live use by like putting a toggle switch on the 3.3v red wire on the coolrunner would that disable it for live use?
GENERAL Coolrunner and Live question?
- Thread starter jayfig
- Start date
Martin C
VIP Member
If you have a clean NAND image, the coolrunner won't be active. I don't believe it should affect the booting of the console. If it does, you could fit a switch to disable the 3.3v VCC.
How could you tell if it affects the booting of the console, would it be anything out of the ordinary? The reason I want to leave it connected is because since I bought it I already have it now I have a reason to jtag in case I get banned from live for some reason in the future.
the console would either not boot or give a RROD error I would imagine, but as Martin says - don't see it being an issue
Martin C
VIP Member
Just bear in mind that it may be possible for MS to remove the ability to RGH.
In this case, a dual booting NAND is pretty pointless.
In this case, a dual booting NAND is pretty pointless.
there's a point - is efuse protection relevant for phat RGH xboxes - I know it isn't for slims - but they can change the CB on phats can't they?
Martin C
VIP Member
I remove the R6T3 resistor as a matter of course. You're not going to be taking any more official updates and if you did, nothing stops you manually rebuilding a retail image yourself.
In the future if the RGH is going to be eliminated by an update we'll know cause c4e will tell us what the update contains right? So when that happens Ill jtag it lol.
So removing this resistor can protect the RGH in the future? Wheres the tut on that?
Here you go.So removing this resistor can protect the RGH in the future? Wheres the tut on that?
http://team-xecuter.com/forums/showthread.php?t=62331
But aren't you doing all this to get back on Live? Someone correct me if I'm wrong, but wouldn't the lack of the above mentioned resistor raise a flag of some sort once he goes on?
Martin C
VIP Member
No - all this does is stop the eFuse being burned should an update be taken by MS. If such a thing happens, you only need write your RGH image back to the console.
Martin C
VIP Member
You're only on a current dashboard as long as there's no newer one out!
I don't understand the question.
So the tut for protecting efuses is still useful on the current dashboard now?
Or like you said all I have to do is make a backup of my current nand if a later update disables the RGH.You mean as far as preventing the burnout of eFuses on a board that already has them burnt because it took the updates that do it?
According to ROGERO, the Fall Preview Dashboard updates the CB to 6752 (Jaspers). As of now, a stage 2 CB can not be RGHed. Eventually it will because with the HANA Chip, the exploit is permanant (unless M$ replaces the chipset).