Easily update your Jtagged or RGH Xbox 360 to Kernel / Dashboard 14699 with XeBuild

Note, this tutorial still works however is quite old, read the Easy Jtag Update version of it

This guide aims to cover everything required to update your Jtagged / Reset glitch hacked (RGH) Xbox 360 to the latest 14699 Kernel / Dashboard. I have tried to make the guide as detailed as possible so people of all skill levels can follow it successfully.

I have provided all the tools / files you will need to complete this guide, however there are a few things will you need to provide yourself as they are unique to your console, these are:

• A dump (copy) of your current Freeboot nand
• Your CPU key

The four main parts of this guide are:

1. How to dump (backup) your current Freeboot nand
2. How to findout my consoles CPU key
3. Building your new nand
4. Flashing the new nand to the Xbox 360

Quick Note: If you are a Jtag user upgrading from XBR 8955 you would be best off upgrading to FreeBoot 9199 first, people have had a lot more success updating to 9199 first, then going to the latest

14699 as covered in this tutorial. If you are on 8955 you can follow this tutorial here to update to 9199. If you are on 9199 or higher just proceed with this tutorial.

1. How to dump (backup) your current Freeboot nand:

We are going to take a copy of your consoles existing nand, xeBuild will now extract your current smc.bin, kv.bin and smc_config.bin straight from this backed up nand, it should also mirror any existing block remappings from the to the

new nand you are building.

This means you do not need to provide any additional files other than a backup or your nand, or worry about remapping bad blocks your self

Basically if you have a working Jtag you should be able to update very easily by following this guide.

To dump (copy) your nand from the Xbox 360, we will use a program called “Nand Flasher 360”. Note: This will work for Jtags, if you have a RGH console you would be advised to use your original nand dump, I have been informed not doing so will cause some people problems.

Download Nand Flasher 360

When you have Nand Flasher 360 downloaded, unzip it, then copy it to your USB drive



Connect the USB drive to your console and load Nand Flasher 360 with your favourite file manager.



When Nand Flasher 360 has loaded select Dump Nand / Flash on the right menu, the nand should then dump to your USB drive as a file called orig_nand.bin



Note: If you are unsure if your console is an Xenon, Zypher, Falcon, Jasper 16mb, Jasper 256mb or Jasper 512mb now would be a good time to make a note of it. As you can see in the image below the revision of

the console and nand size is displayed, you will need to know this later on:



Once the dump has finished you can connect the USB drive to your computer and copy the orig_nand.bin off it.



2. How to findout my consoles CPU key:

You should already know your consoles CPU key, however if you do not it's pretty easy to find it out.

1. First: Connect the 360 to the TV with the Component or VGA cable (Xell / Xellous do not not work with HDMI so you will just get a black screen)
2. Power on the console with the DVD eject button
3. Have a camera ready
4. Wait until the fuse sets are shown
5. Take a photo quickly as they will usually scroll off the screen fast
6. Combine fuse sets 3 and 5 or 4 and 6, this will give you the consoles CPU key

Fuse set example:



(Image found on Google)

Take line 3 and 5:

3= E42D681ED06A6D1C
5= 1FFD8E48C56A2058

So my CPU Key is: E42D681ED06A6D1C1FFD8E48C56A2058

Now you have your current nand and CPU key we can build an updated nand.

3. Setting XeBuild up and building your new nand:

You will need to download the following:

Xebuild 1.00 F1 - this is the program that will build your updated nand

14699 data - this is the data for the 14699 Microsoft Dashboard

First unzip XeBuild 1.0 – you should now have some files / folders like in the image below



Now go in to the 14699 folder, you want to unzip the 14699 data in to this folder. You should have the files in the 14699 folder as seen below.



Now in the xeBuild_1.00_f1 folder, open the 1blkey.txt and paste the correct 1blkey in there. The correct key is: DD88AD0C9ED669E7B56794FB68563EFA



Next go in to the mydata folder and open cpukey.txt

You need to paste YOUR cpu key in here, it will not be the same as mine.



Next copy the dump of your current nand in to the my data folder, this should be renamed to nanddump.bin

Note: XeBuild will now extract your current smc.bin, kv.bin and smc_config.bin straight from the nanddump.bin, it should also mirror any existing block remappings from the nanddump.bin to the new nand you are building.



You are now ready to build your new FreeBoot nand, to do this you need to open command prompt (windows key + r, type in cmd and press ok)



You need to navigate to the xeBuild_1.00_f1 folder, in my case this was on my desktop so all I had to do was type cd desktop (as the command prompt opened in my user folder) then type cd xeBuild_1.00_f1



Once in the xeBuild_1.00_f1 folder we can now build the nand

To build your hacked nand for a Jtag type:

xeBuild.exe -t jtag -c <your console revision> -f 14699 -d mydata updflash.bin

Type one of the following depending on which revision your console is, this can be: xenon, zephyr, falcon, jasper, jasper256, jasper512

To build your hacked nand for a Glitched console (RGH hack) type:

Note: if you do not know which revision your console is read the above part of the tutorial on dumping the nand for a way to findout, Nand Flasher 360 will show you the relevant information. Do not guess if you are unsure!

As my console was a Jtag Jasper 512 I typed:

My nand was then built without any errors:



We are now ready to flash the new updated nand to the Xbox 360.

Note: As i dont have a RGH hacked console im not sure if Nand Flasher 360 will flash the nand on a Slim, it should however if someone will confirm that would be great.

4. Flashing the new nand to the Xbox 360:

Download Nand Flasher 360 if you have not already, and unzip this to

your USB drive.

Now copy the updflash.bin you just built to the USB drive.



Now we need to load NAND Flasher 360 on the console, do so using your favourite file manager, XEX Menu or FreeStyle Dash will work fine.

Simply browse the files on the USB memory stick and load Nand Flasher 360:



On the right menu select “Write NAND / Flash”



This will bring up a file browser, select the USB drive



Now select your updflash.bin, you will be warned not to press anything on the console as it is flashing.



Press ok and the nand will be flashed to the console.



After the flashing has finished it will be verified, all been well your nand will have been flashed successfully.

Press the on-screen button “shutdown” to turn the console off.



Unplug the power brick and leave it disconnected for two minutes (or turn the 360 off at the plug)

Re connect the power brick, power the console on and if everything has gone ok your console should boot in to the 14699 Dash.

You can verify the console is on the 14699 by looking in system settings, however if you see the new metro dashboard that should be obvious.

As you can see XEX Menu, a homebrew application on the new metro dash:



Thats it your console should be updated! good luck and if you have any questions I will do my best to answer.

5. FAQ:

How do I restore the avatars?

Spoiler

Restoring the avatars is simply a case of you running the official Microsoft 14699 update, only do this after you have upgraded to the 14699 dashboard using this tutorial. If you run an update on a Jtag with a higher dashboard than you are currently running you will find that you no longer have a Jtag.

The Xbox 360 Kinect Dashboard Update 2.0.14699.0 With Avatars can be downloaded here

Simply extract the $SystemUpdate a Fat32 formatted USB drive, the USB drive should look like this:



Just insert the USB stick in to the 360 and you will be asked to update, say yes and the 360 will re start and your avatars will be restored.

There you go, you now have the 14699 dashboard on your Jtag with working avatars.

How do i format my USB drive to Fat 32?

Spoiler

Go to My Computer, right click on the USB drive and select format



Select Fat 32 and Default allocation size, then press start.

 

Yes that is normal, its for the system files only. The rest of the space is only used for the internal memory unit.
If you look at the screenshots i got exactly the same.

 

Have you re installed Dashlaunch?

Download it from here: https://digiex.net/downloads/downlo...ad-xebuild-1-00-dashboard-kernel-14699-a.html

Copy it to a USB drive then launch the installer for it with XEX Menu, after its installed if you still have your previous launch.ini it will pick your settings up for that and load directly in to FreeStyle Dash.

 

Yup i did mean 14699, this guide is based on my old 13604 one.
Thanks for letting me know, fixed it, and i'm glad it worked fine for you

 

Put XEX Menu in your COD folder and boot it with your working shortcut, you can then use that to copy the Live version of XEX Menu to the consoles internal hard drive and it will appear on your dashboard again under demos.

So if your external drive had \Games\Blackops\default.xex replace the default.xex with XEX Menu (and copy the other files in) and it will load with your shortcut.

 

I think the Metro Dash looks better, however the previous NXE is a lot easier to use and functions better.

If i want to launch a homebrew app under demos i now have to go to games, click the button to show other categories, click the demo's section then find the demo.

Where as before you went to games, clicked demos and it was there. Plus without the box art from Xbox Live it looks a bit rubbish, keep meaning to look in to adding that manually when i get a chance.

 

Basically to sum up a few scenarios for you:

1. If you have a dual nand setup, (slim only as the rgh hack can not be patched on that) it will only update your non hacked dashboard / kernel

2. If you did that on your RGH nand will not have an RGH hacked console after updating with an official update.

Explanation: Basically you have to update like this as you have a modified dashboard / kernel which has a lot of the restrictions removed, updating with an official update would re add all them restrictions, so your console would be just like one you can go in to a shop and buy.