RGH Tutorial - How to update your RGH to 14699

neophyte5001

Senior Member
Nov 5, 2011
113
0
Missouri
Okay, after a LOT of reading I finally found out just how easy this process is. So easy, in fact, I guess most just assumed it was common sense. But I like to have to-the-letter understanding before I go screwing with my hardware, and I'm sure lots of you out there new to the modding scene feel the same way.

Before I begin I need to make one thing clear: This *should* work for furure updates also, but there's never any telling what MS has in store so always, ALWAYS make sure future updates are *safe* to use before you go to it. We can't go on live anyway with these systems so there's no point being all bleeding edge about it, and winding accidentally jacking up your precious system that you worked so hard to glitch!

This means that for now, this TUT is for 14699 only, for those of us with RGH consoles. It might be the same for JTAG but since I don't own one I can't claim that it will work, or that there isn't some additional steps involved with those. I only know that this worked perfectly on my RGH'd Phat Jasper 512 with no issues whatsoever.

1) First, get ahold of 360 multi builder 0.5 <-- Pay attention, that version number is what you want, not an earlier one. It has all the 14699 goodness built-in. :D

EDIT: 360 multi-builder 0.6 is out now, if you have any issues with 0.5 try then new one. Rogero says 0.5 is still fine to use however. For more info see the 360 multi-builder thread (stickied).

2) You can use either your original nand dump, or the nandflash.bin that you have from the last time you used 360 multi builder. Rename it to nanddump.bin and place it into 360 multi builder/data/my360
You also want a text file containing only your cpu key, call it cpukey.txt and put it in the same folder as your nanddump.bin

3) If you are familiar with 360 multi builder than you know how easy this step is. Just run the run.exe and follow the instructions. Choose glitch image, then let it build an image with dashlaunch patches.

4) In your 360_muti_builder_0.5/data folder you will now have nandflash.bin. Copy it and the file xenon.elf onto the root of a blank flash drive.

5) Plug it into your 360 and boot into xell (that means power on the 360 with the eject button) and let it do it's thing. Once it's done it'll say power off now or some such, just shut it off for now.

6) Unplug the flash drive, and THIS PART IS IMPORTANT! Power cycle your xbox. This means unplugging the power from the back of the 360 and waiting like a minute. Plug the power back in, power on, and

7) You should now be in new dash. But wait, why are the avatars just sillhouettes? We'll fix that right now.

8) Take your flash drive (the one you just used) plug it into your computer and delete the xenon.elf and nandflash.bin, then put the official ms update (you know where to get that, right?) onto the flash drive. Note that you have to unzip the update after download, and put the extracted folder renamed to $$ystemUpdate on the flash drive.
Dashlaunch ignoressystem updates so we need to rename it so dashlaunch can see it to EXACTLY this:
$$ystemUpdate
^^^^^ this needs to be the only thing on your flash drive
Unplug from computer and plug into your 360
(I didn't power my 360 off when I stuck in the usb and it saw the update right away. If that doesn't happen to you, reboot into nxe and it should pick it up and prompt you)
If it STILL won't detect the update, try $systemupdate <--- If this works, your dashlaunch.ini is not configured to block MS updates, and you should look into changing that! (Thanks goes to frayed for pointing this out)

9) It does it's thing, restarts automagically, and BOOM! Your in the new dash, and your avatars look like they did before now. :)

10) Explore the new dash! I really like it, it's much better for larger screens.

Hope this helps someone out there!
 
Last edited:

H3rmaN

Full Member
Dec 4, 2011
97
0
NE Scotland
8) Take your flash drive (the one you just used) plug it into your computer and delete the xenon.elf and nandflash.bin, then put the official ms update (you know where to get that, right?) onto the flash drive.
Dashlaunch ignoressystem updates so we need to rename it so dashlaunch can see it to EXACTLY this:
$$ystemUpdate
Unplug from computer and plug into your 360
(I didn't power my 360 off when I stuck in the usb and it saw the update right away. If that doesn't happen to you, reboot into nxe and it should pick it up and prompt you)

9) It does it's thing, restarts automagically, and BOOM! Your in the new dash, and your avatars look like they did before now. :)

10) Explore the new dash! I really like it, it's much better for larger screens.

Hope this helps someone out there!
I'm getting stuck at this point, I have updated through XeLL and all was fine, etc. I have the new dash on my 360, but when I go to run the official update to sort the avatars nothing happens.

I have renamed the $SystemUpdate folder to $$ystemUpdate, but the console just doesn't do anything when I plug in the memory stick or boot up with the stick already in the slot.

Any ideas??
 

neophyte5001

Senior Member
Nov 5, 2011
113
0
Missouri
I'm getting stuck at this point, I have updated through XeLL and all was fine, etc. I have the new dash on my 360, but when I go to run the official update to sort the avatars nothing happens.

I have renamed the $SystemUpdate folder to $$ystemUpdate, but the console just doesn't do anything when I plug in the memory stick or boot up with the stick already in the slot.

Any ideas??
Is the update the only thing on the stick? When you downloaded the update, did you unzip it first? Other than that, maybe try $$ystemupdate.
 

neophyte5001

Senior Member
Nov 5, 2011
113
0
Missouri
The stick does have other crap on it, will format it and put just the update on and see if it works.

Cheers!
Yes it needs to be the only thing on the drive. The update, once downloaded, also needs to be extracted. The extracted folder is what you want to rename and place on the drive.

Let us know when you have success! :)
 

TheGlichter

Full Member
Dec 8, 2011
90
0
Europe
Nice tut! I can confirm that it works. I have done somthing similar... Yesterday i had an slim to glitch with had 13604 stock on it and never been updated, read the nand, glitched it...booted to Xell.Then i made a mistake to use multiB 0.5 wich obviously has the 14699 on it, to make the boot image. flashed it with rawflash and there were no errors, just went fine en did a cold boot afterwards. Big surprise to see the metro dash! Wtf took a couple of seconds before i realised where i went wrong haha.

Anyway could this cause any problems??

The only thing i noticed was that on freestyle dash the retail 360 discs wouldn't play, went straight to the NXE dash? Maybe something to do with dashlaunch settings??

Great forum btw!!
 

astr4twin

Full Member
Nov 28, 2010
77
0
Thank's for the tutorial. Made it really easy.

I have one question though. If i ever update in the future do i use my orginal nanddump.bin or the new one i just created in Multi_builder ?

In other words, do i need to keep this one safe or is my original one only needed to be kept safe?

Thank you.
 

gargoyle67

VIP Member
Feb 4, 2011
231
0
Thank's for the tutorial. Made it really easy.

I have one question though. If i ever update in the future do i use my orginal nanddump.bin or the new one i just created in Multi_builder ?

In other words, do i need to keep this one safe or is my original one only needed to be kept safe?

Thank you.
You can update with either as per the tut but you should always keep your original safe.