Yeah , as I was saying probably something temporary.. good try
unfortunately it was a premature from team Xecuter to say they fixed the slims RGH hack..cpu key is needed so only already RGH hacked consoles are save.. they probalby can fix it but cost more time
Just to clarify, If I buy a premodded slim from a reputable seller, with coolrunner already installed I wont have any problems with latest updates etc?
when i start the console sometimes it does not auto sign in to profile it happens 1/10 times what could be the issue ?
had it , its a corrupted file on your profile HDD ... to fix it , use XEXmenu and open FSD and in it go to config and then pick the profile your console will AUTO log in ... it fixes this error, then your original dash will auto log in to your default profile that FSD saved [FSD means FREE STYLE DASH] ... why it happens , well its FAT-32 and its fucking PMS that sometimes corrupts random files and crisscrosses its data
Introduction:
=============
After a lot of work, xeBuild brings together ggbuild and fbbuild into
a single application for building glitch, jtag and clean retail images.
What's New:
===========
- adds 14717
- trinity CB_B patches updated to allow glitch image booting on official 14717 updated slims,
requires having CPU key before building image. Updated fats will likely require new CPLD
timing, if you wish to continue to glitch a fat for the time being it's advised to not apply
any update > 14699.
- included xells updated to xell reloaded v0.991 built 2012-02-19. See xell_info folder for
usage info and changelog, or find newer builds at libxenon.org
-note that for xebuild, jtag images use xell-2f not xell-1f
- added devkit image building (WIP, see info below)
- added bigffs jasper type (see info below)
- added a small helper app, ini_creator.exe that will create a basic .ini file with crcs
for xebuild when batches of files are dropped onto it, ready for sorting
- bug fixes
Current Limitations:
====================
- STAY THE HELL OFF LIVE! Nuff said, we're not you're mum.
Dash Launch 2.30
================================================================================
ChangeLog
================================================================================
v2.30
- fixed uart debug output 0xD 0xA instead of 0xA 0xD
- STOP code 0x2B can now output stack info
- xex header revoke check (requires live to download revoke list) flag now ignored (hv and xam patch)
- add 14717
Updated fats will likely require new CPLD
timing, if you wish to continue to glitch a fat for the time being it's advised to not apply
any update > 14699
What are CPLD timings, and if we on 14699 wish to play the latest games (that when they are released will need a dash >14699), will we need to update or is there a workaround so that they would be playable on 14699?
many people confuse things but I can explain it first of all if you have an RGH console you are perfectly safe and can always play newest games as long as they can crack the new dashboards and you do not use offical ms update. so cracking new dashboard and fixing glitch are 2 different things.. fixing glitch is for people who are dumb enough who update their console with an microsoft update. or for the consoles that are nog glitched yet and have newest dash.
Ok my sex box hasn't been used for a year. I'm done with disks and would like to Glitch it.
Is there any easy way for me to do it, or do I need to find someone in the UK who'll do it for me on Xbox scene? Any advice welcomed... I wanna get back into my consoles
I have a ps3 too, but am I right in saying that not all modern games are playable on the hacked ps3 firmwares? I updated mine with mw3 so maybe I cannot mod it any way?
Ok my sex box hasn't been used for a year. I'm done with disks and would like to Glitch it.
Is there any easy way for me to do it, or do I need to find someone in the UK who'll do it for me on Xbox scene? Any advice welcomed... I wanna get back into my consoles
I have a ps3 too, but am I right in saying that not all modern games are playable on the hacked ps3 firmwares? I updated mine with mw3 so maybe I cannot mod it any way?
How about reading the thread that should've been stickied?
many people confuse things but I can explain it first of all if you have an RGH console you are perfectly safe and can always play newest games as long as they can crack the new dashboards and you do not use offical ms update. so cracking new dashboard and fixing glitch are 2 different things.. fixing glitch is for people who are dumb enough who update their console with an microsoft update. or for the consoles that are nog glitched yet and have newest dash.
Cool thanks - I am new to this so was a little worried..
So are the fats users screwed with the new dashboard update? or does this just mean more wait for the release of hacked dashboard?
its very hard to predict but the slim is 100% fixed now.. but fat is harder because cb_a has revocation fuses... but gligli (thats the creator of this hack) said that slim cb_a without refocation checks on the fuses work on fat.. this is a big security hole..(if it really works) that the slim bootloader works on fat.. microsoft messed up on the slim to put the fuse check in second bootloader (cb_b ).. with the glitch hack we can patch second bootloader but not the first. so thats why the first bootloader is so important. fuses are basicly some codes inside the cpu and we can never ever change those.. so the new update changes those codes then the first bootloader cb_a will detect that and if it does not match then it will halt the boot procces so this is how they prefent previous bootloaders to run.
Last edited by highstuff on Wed, 22nd Feb 2012 16:47; edited 4 times in total
We are very pleased to announce that we have fully decrypted CB_B and can now achieve a full RGH hack using a STOCK TX CoolRunner on slims with the 14717 dashboard even if they have no previous nand dump or CPU_KEY !
We are currently working on the Phat solution - we already have the dual CB_B 6752 glitching
its very hard to predict but the slim is 100% fixed now.. but fat is harder because cb_a has revocation fuses... but gligli (thats the creator of this hack) said that slim cb_a without refocation checks on the fuses work on fat.. this is a big security hole..(if it really works) that the slim bootloader works on fat.. microsoft messed up on the slim to put the fuse check in second bootloader (cb_b ).. with the glitch hack we can patch second bootloader but not the first. so thats why the first bootloader is so important. fuses are basicly some codes inside the cpu and we can never ever change those.. so the new update changes those codes then the first bootloader cb_a will detect that and if it does not match then it will halt the boot procces so this is how they prefent previous bootloaders to run.
Thank you for the explanation. Let's assume we get the next dashboard update, will it inherit the same security fix that this 14717 has, relating to the CB revocation? I mean, if we wait for the next dashboard, if it somehow focuses on some other security aspect, then we can skip this dashboard and jump straight to that one on the fat console. Does that make any sense?
BLaM! wrote:
Why do you need this dash ? Who cares , no need to update until something major comes up..they'll fix it..
I wouldn't give a rat's ass for this dashboard, if it weren't for the fact that there could be a way, by which Microshaft somehow figures out a way to block RGH. I'm speaking from our perspective, that is, people who are already on RGH and seem all dandy that MS can't do jack about it now. I'm just concerned about a hacked dashboard being available later or not, on the fat console, to be precise. Though it's too early to be worried about it, still, you never know.
Yeah , I have high hopes for RGH tho..I think every security measure is just temporary , ofc as you said we never know what M$ can actually do with their console. There is always flashing and discs.. ( no thank you )
Signature/Avatar nuking: none (can be changed in your profile)
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
first of all if you have an RGH console you are perfectly safe and can always play newest games as long as they can crack the new dashboards and you do not use offical ms update. so cracking new dashboard and fixing glitch are 2 different things.. fixing glitch is for people who are dumb enough who update their console with an microsoft update. or for the consoles that are nog glitched yet and have newest dash.
