Jtag Kernel Update, the old way, one final time...

Ok with both of my Jtags up for sale, I should probably update them to current levels before passing them on. Now, I've had a bad experience with an all-in-one GUI tool before, which resulted in me having to plug in a soldering iron in order to fix...so ever since then I just use the old fashioned command line method for updating. It's never once let me down, is nowhere near as complex as it might first appear, & because it's step by step I think you're less inclined to make a mistake.

So this will be my last time doing this, & thought I'd document it as such. I;ll be taking excerpts from Touching Virus' already written excellent write up, & adding in screengrabs & pics of the process along my way. So, without further ado, one last time....

For simplicity you need the following:

1) Your CPU Key
2) A copy of your nand (original or FreeBOOT) and SMC
3) Dashboard Data (Google for "xxxxx Dashboard data" where XXXXX is the version number e.g. 12611, 13599, 14699, 16197
4) xeBuild (xbins -> /XBOX 360/development/xeBuild/)

I've my cpu key contained within a text file, a copy of the most recent nand image for this console & the modified smc for this console type {Big Block Jasper}, the newest Dashboard Data {16203 as of now}, & the most recent xeBuild {1.07 as of now}.



Ok, onto step 2:

Download xeBuild and extract it to a folder - say C:\xeBuild

Open your dashboard data zip file and extract the contents to C:\xeBuild\<version_number> e.g. for 16203.zip, extract the contents to C:\xeBuild\16203. The folder should already exist in C:\xeBuild anyway.

Edit C:\xeBuild\1blkey.txt. On the first line is a dummy key - replace it with DD88AD0C9ED669E7B56794FB68563EFA.

Edit C:\xeBuild\mydata\options.ini. Scroll down until you see where the cpukey goes, paste it in there. You can also add the 1bl key to this file, it goes directly over the cpu key line. Both are filled with dummy codes, so just overwrite them with the 1bl key as provided, & your consoles cpu key. Close the text file then, saving any changes.

That's all just straight forward stuff, no need for any pics there. Just follow it exactly.

Step 3:

Extracting KV and SMC_CONFIG.bin
Open up 360 Flash Tool v0.97 and click Settings->Options. Tick the box that says "Extract ibuild compatible files". Then open your nand and click extract on the bottom. Tick the box for 'config blocks' and 'Keyvault' and click OK. Choose a folder for these files. When extraction is done, go to that folder and there'll be a folder called freeBOOT, click into it, then into data and you will find two files - kv.bin and smc_config.bin. Copy these two files to C:\xeBuild\mydata.

Ok, using the mentioned 360 Flash Tool program, I followed the above instructions. And as promised, the two needed files are where they should be:



So again, as per instructions, I move them to C:\xeBuild\mydata



Step 4:

Picking the right SMC (not for Xenon consoles)
This step is very important if your console is not a xenon - flashing the wrong SMC can end your JTAG If the nand file you used to extract the KV.bin and SMC_CONFIG.bin files in the previous step was taken from your previous dashboard updflash.bin, or was taken from a dump you took off your currently working JTAG, then use the same steps above but check the box labelled SMC. You'll find an SMC.bin in the same place you found KV/SMC_CONFIG.bin.

If you're using your original nand (not recommended unless you know your wiring scheme), then you will need to pick an SMC for the JTAG wiring in use. You can find SMC files for the AUD_CLAMP method of wiring (the preferred choice) in this file. Remember: Using the wrong SMC file can b0rk your JTAG, to play it super safe, take a dump of your nand using Flash360, and extract the SMC from that using 360 Flash Tool

Copy smc.bin to C:\xeBuild\mydata

This step never worked for me, I always just got two files called smc_dec.bin & smc_enc.bin which I'm not sure what to do with. So, knowing this Jasper console has had the boxddr method of jtag done, I use a pre-patched smc file specifically used for Jaspers, pictured above called jasperbb.smcio_v1.2. This is crucial, & can ruin the console if you use the wrong file, so if in doubt, ask for help or research it more. Make sure to rename the smc file you use to smc.bin, & move it to C:\xeBuild\mydata



Step 5:

Place an existing nand dump into the 'mydata' folder of xeBuild. This will allow xeBuild to determine various system variables. You need to rename the dump file to 'nanddump.bin' without the quotes.

Straight forward enough



Step 6 - Build Time:

Build freeBOOT

Open a command prompt, go to C:\xeBuild and type the following

Code:
xebuild -t <image type> -c <model> -d mydata -f <dashboard> updflash.bin
<image> is either glitch, jtag or retail
<model> is either xenon, falcon, zephyr, jaspersb, jasper256, jasper512 etc etc
<mydata> is where your per-console files are, cpukey.txt etc
<dashboard> is the name of the folder holding the dashboard files (e.g. 16197)

xeBuild will build freeBOOT as updflash.bin - copy it to USB, boot to Xellous and flash it.

I open an elevated command prompt, as the resulting file will need to be written to c:\ {root}. So in my specific case, the build instructions were:

xebuild -t jtag -c jasper512 -d mydata -f 16203 c:\updflash.bin

So -t was set to Jtag, as it's a Jtag image I'm looking to build.
-c was set as japser512, as it's a jasper chipset with 512MB memory
-d was set to mydata, as that's where I put my console specific files earlier
-f was set to 16203, as that's the version of dash we're looking to build.
& then I wanted the output file placed in c:\, & named as updflash.bin hence c:\updflash.bin.

If you've done everything right & placed everything where it should go, the build log will be error free:



Ok that's the build process finished. If you look where you set your output file to be placed, you should see a shiny new updflash.bin. Next step is to flash it to the console itself!