J-Runner (basic guide) build 279 J-Runner is a GUI that uses Xebuild, Xell-reloaded (full credit to their authors). Python has been replaced with code within the GUI. It Enables JTAG, Glitch & Retail images to be created. Nandpro is NOT required as J-Runner reads/writes to the nand itself. J-Runner has been designed to be used with Nand-X / JR-Programmer and T-X CoolRunner (if doing glitch hack). J-Runner relies on the fact you have already soldered in your CoolRunner or JTAG wiring – there are plenty of diagrams available online and within J-Runner to achieve this correctly. In addition you should already have installed your drivers for Nand-X / JR-Programmer and have it connected to both your motherboard and CoolRunner(if doing Glitch Hack).
Upon the first run of J-Runner it will automatically check that it is the latest version and ensure all the required files are correct (and download if required). J-Runner is designed to be simple and intuitive: The process runs from left to right (Glitch Selected)
And the same for JTAG (Obviously Flashing CoolRunner is not used)
1. Read Nand: The default is set to 2 dumps – dumps – this will automatically dump the nand 2 times then compare the dumps to ensure they are the same! (number of dumps is selectable in number box) 2. Flash CoolRunner: (not required for JTAG) This is a simple as it sounds, it flashes your coolrunner with the required file. If you have 2 matching nands –try nands –try to boot the console. If your console console doesn’t boot at this point – point – then your soldering isn’t correct! No changes have been made to your nand – so it should boot fine! then flash your CR. 3. Create ECC: / Create Xell-Reloaded: This uses the nanddump1.bin nanddump1.bin that is loaded in source box! It creates the file you need to flash to your nand – nand – this contains Xell-Reloaded and the glitch info(or Xell-Reloaded file with your keyvault) to allow you to boot your console to Xell-Reloaded and obtain your key. It then loads that file into Source box ready for writing. 4. Write ECC: / Write Xell-Reloaded: Does what it says on the tin – tin – writes the ECC/Xell-Reloaded file you created to your nand. Once written, remove power cable then re-plug and boot your console (fingers crossed) it will boot into xell-reloaded. This allows you to obtain your CPU Key (I suggest you open notepad and type it into that then save it as cpukey.txt – if you are not using network cable to grab your key.)
5. Create Image: This requires your nanddump1.bin to be reloaded into the source box. As well as the cpukey pasted/loaded into the CPU Key Box. If you have the correct key then the information should be displayed on the right hand boxes. 6. Write Image: This writes the bin file you have loaded into the source box to your nand.
Image selections
During creation of your final images You select what type of image you are trying to create JTAG, Glitch or Retail. Also which dashboard you wish to flash. Changing these buttons alters the option available to you!
DL Patches is if you wish to add the Dashlaunch Patches and Launch.ini file to flash Custom launch.ini can be created clicking on Launch.ini Options
Aud_Clamp selection is also available for JTAG images
Xebuild Options All the available options in Xebuild can be set here, this is for advanced users! Don’t change things you don’t know what it does!
Menu’s explained (updated for build 276)
Tools:
Restart:
Restarts the app (it’s nice to start things from fresh)
Get mb type:
You need Nand-x or JR-Programmer connected to motherboard for this one! – it
performs a quick read and determines your motherboard/nand type.
Save current files:
this was added for those doing purely key retrievals, once you have the key
– use this to save your nand and KV info into the same format as doing full RGH (folder named after console serial)
Save KV info:
Saves the KV.text into working folder
Extract Files:
Extract a load of files – required for different things including CB’s, KV.bin,
SMC_config, SMC etc (these extract into output folder)
Monitor POST: Does what it says on the tin (used for monitoring Power-On Self-Test - requires additional HW, google it)
Update JR-P fw:
If you need to reprogram the JR-P, select bootloader update switch, press
this! While its updating switch the update switch back to off
SMC Config Viewer: Exit:
allows you to see the config of SMC of any nand loaded into source.
Do I need to explain this one ?
Images:
Here you have handy reference pictures for wiring your JTAG/RGH
Xebuild Patches:
When you mess with configuration of a console ie removing mem modules, swapping dvd drives etc, you can utilise these patches to enable your console to still run.
Advanced Menu:
Custom Nand/CR Functions:
From here you can write/read/erase nand tailoring specific blocks to start and block length etc and flash custom xsvf files
Write Fusion:
This was added to allow the flashing of pre-made fusion.bins to console that have
bad blocks present. Just load your nand into source and select this!
Change Lock Down Value: If you have to alter your LDV simply select this option the LDV boxes on nand info tab become editable, alter one of them and return to this menu to confirm it. Replace first bytes of additional file with source file: This is here fo r those who did a small dump and then flashed xell-reloaded and grabbed remaining nand using xell-reloaded. This enables them to create a whole stock nand from the 2 files (initial dump and full dump with xell-reloaded at start.
Patch Nand: If I need to explain this – you shouldn’t be using it!
Create an image without nanddump.bin: A rather nice feature. If you have carelessly ended up with ecc on your console and no stock nand! –EEK! You need a KV.bin(rename kv_en.bin after an extract from ecc file), SMC.bin(rename SMC_en.bin from an extract), SMC_config.bin placed into Xebuild/data/ folder then enter your CPUKey into CPUKey box. Choose your dash and i mage type then select this option from menu.
Settings: J-Runner now has some audible indication o f things happening. It has some default embedded sounds for nand write/read complete, nand compare success and a failure sound! If you are not a fan of these sounds – you can set your own .wav files to play upon these 3 events from the settings menu on the toolbar. J-R Programmer Delay: if you experience lag whilst writing to the nand using a JR-Programmer try adding incrementing this Delay setting by 1 at a time. IP: The saved address to grab key from Xell. IP Ranges: The “to and from” IP range to use Scan IP R ange Button on main form XeBuild Image Name: choose the output name of the image (in case you want to use xenon.elf etc)
About:
If you like J-Runner please feel free to donate! – there is a button in the About screen!
CPU Key Database There is a Key database included in J-Runner this is automatically populated during the process and will store your key against console serial number. Next time you load that nand into sourcebox the key will auto populate from the database! Another new addition (build 276) is “Scan Folders”: press this and point to the folders you’d like to scan, it searches for keys and nands and add them to your database (once checking they match of course)
Quick Key Functions F1 -
Restarts the application
F2 -
Grabs the Config from the Nand (identify the nand)
Demon Hot keys F5 -
Toggle between Demon and Xbox
F6 -
Power Xbox360 On
F7 -
Power Xbox360 Off
F9 -
check source file against cpukeydb
F10 -
Select IP – Grab Key
F12 -
Forces a re-download of the application.
Read Nand: The default is 2 reads (this is to allow comparison to ensure you have a good dump) Ensure you have Nand-X or JR-Programmer all connected with drivers installed. Board plugged in but not powered on, then press the Read Nand button,
J-Runner will check the nand type upon starting read it will select the correct nand for you. The choice you make here will be displayed in the text box on app and remain until you manually alter it by clicking on textbox itself or restart the app or manually load a file into source.
Nand read is initialized and begins the first dump.
NOTE: For Big Block Jaspers you have 3 options (selected board only = 64mb Dumps, 2mb Dumps(only if advanced selected) or Full Dumps)
Once complete the second dump begins automatically. Upon both dumps being auto loaded into GUI for automatic comparison. Look in the log for the comparison result
With “Glitch” - Selected Flash CoolRunner At this point you should Flash the CoolRunner with relevant file Press the Flash Coolrunner button
You can now use LPT cable Programmer to program your CoolRunner
Now boot your console – if all wiring is correct it should boot fine with the stock nand.
Create ECC At this point press the create ECC button you should see a whole load of text appear in the log file.
Look at the log and ensure there are no error messages
NOTE: If you have bad blocks in the first 50 blo cks, J-Runner will remap these for you and create a fixed file from which to create the ECC file. The created image is now loaded into the source box ready for writing
At this point there have still been no changes made to your nand
Write ECC You now have to write the Xell-reloaded image with ECC data for your nand. Press write ECC
You will then see this
Once finished Unplug power cord, wait 10 seconds or so, replug it and boot the console With any luck you should see Xell-reloaded on your screen
Once fully loaded Open notepad on your PC and type in the cpu key (at bottom of screen) then save the file as cpukey.txt (or you can use Http Then copy your key and paste into the CPU Key box in J-Runner. If you network the Xbox to your router and connect to t he address shown at the bottom of the screen – you can then use the grab CPU Key function just enter the digits shown on the screen for the IP address.
For Corona motherboards Xell will not display video so you can use either “Scan IP Range” (This will scan the range you set in the Settings page and grab the CPUKey if it finds your Xbox running Xell) or “Monitor COM” (monitor com – explained HERE) J-Runner will then reload your nanddump1.bin into source box again in preparation of key validation and image creation Now you should have all the info in KV tab o n the right hand box and you will get a CPU Key verified message in the log! The log will also show your current LDV value of console!
At this point you now have all the info you need to create a Freeboot image. Shutdown the Xbox and proceed
With “JTAG” Selected Flash CoolRunner This Button is NOT USED as part of JTAG HACK – AS SUCH IS DISABLED - IGNORE IT
Create Xell-Reloaded At this point press the Create Xell-Reloaded button You should see a text appear in the log file. Look at this and ensure there are no error messages The created image is now loaded into the source box ready for writing At this point there have still been no changes made to your nand
Write Xell-Reloaded You now have to write the Xell-Reloaded image with your data to your nand. Press write Xell-Reloaded You will then see this
Once finished
Unplug power cord, wait 10 seconds or so, replug it and boot the co nsole With any luck you should see Xell-Reloaded on your screen
Once fully loaded Open notepad on your PC and type in the cpu key (at bottom of screen) then save the file as cpukey.txt Then copy your key and paste into the CPUKey box in J-Runner. (If you have your Xbox connected with network cable – use Grab CPU Key function or you can use either “Scan IP Range” (This will scan the range you set in the Settings page and grab the CPUKey if it finds your Xbox running Xell) or “Monitor COM” (monitor com – explained HERE))
Then J-Runner will reload your original nanddump1.bin into source box again Now you should have all the info in kv tab on right hand box ( if CPU key is correct) and you will get a “CPU Key verified” message in the log! The log will also show your current LDV value of console!
At this point you now have all the info you need to create a Freeboot image. Shutdown the Xbox and proceed
Create Image: You have to reloaded you original nand dump back into source box and have pasted in your cpu key. At this point you need to decide if you want dashlaunch installed There is a dashlaunch configurator included in J-Runner, if you want to include Dashlaunch remember to tick DL Patches Click the launch.ini Options Button
Configure each option as you wish. I have selected the default boot of Freestyle Dash from a USB stick (naming the freestyle folder as FSD) You can save the settings for future use (becomes the default ini). But click create to save your file for this image. Exit the window. Now click Create Image Button
You should now be faced with something in log like this
all your files from this hack are saved in a folder (console serial number) You now have 2 options to flash this image to your Nand You can either press Write Nand Or you can copy the Nandflash.bin and Xenon.elf to a USB stick – put into xbox and boot it!
Write Nand Is as simple as it sounds Press the button and Nand write will start
Once finished flashing Unplug power for a few seconds At this point I plugged in my USB with Freestyle Dash folder (\FSD) Then replug and boot it.
DemoN Usage J-Runner has now integrated DemoN commands to enable full control of the Team Xecuter DemoN from within J-Runner. With Demon attached using USB (and driver installed) the DemoN icon will appear and the demon details will appear at bottom right of screen.
Mode: shows up as bootloader if the DemoN has no firmware installed. FW: Displays Current firmware/bootloader version (will not show up if in bootloader mode) Flash: This displays the nand that is selected at time of DemoN detection or Toggle-Nand function is used. NOTE: If you swap nands manually using switch on console whilst J-Runner is running this display will not change – J-Runner will warn you if you select a nand function and the nand has been switched manually!
DemoN Menu When DemoN is detected a new menu will appear that relates purely to DemoN functions.
Toggle NAND: To switch nand between the one on DemoN and the one on the Xbox360 use Toggle NAND menu selection. Upon toggling the currently selected nand will be displayed on bottom bar and in the log window.
The Power On and Power Off function: only works if you have the optional wire connected for remote power. This enables you to power the xbox on and off!
Update DemoN: this allows you to update the firmware on the DemoN. Just select this and select the firmware file. All Read, Write and flash CoolRunner functions operate as normal within J-Runner using DemoN instead of Nand-X or J-R Programmer when DemoN is connected using USB. (so expect nand functions to occur a lot faster!)
Monitor COM This feature allows you to see what’s displayed on screen during booting of Xell.
To use the COM Port you must have additional wiring and Hardware to use this feature. Use an old DVD Drive power connector and utilize the wiring as shown below. Then just connect a CK3i or X360USBPro V2 or even a CK3 Pro RevD with the additional wire (same set up for upgrading Nand-x to ARM 3). Slim points shown below
For CK3i/X360USBPRO V2/CK3 Ver D (with wire)
To use simply open port and boot Xell-Reloaded! Xell output will be displayed in window!
Nand-X USB Update Cable
Credit for Picture “xslvry” (TX Forums)
HOW-TO Create a Nand from CPUkey and files Create an image without nanddump.bin What you’ll need:
your cpukey – that’s crucial and unique
kv.bin – encrypted or not
smc.bin – encrypted or not
smc_config.bin
read your nand (even though it contains ECC in first 50 blocks) (if you don’t have the files above)
You can get those files using the Extract Files option load as source then select Extract from the tools menu
Look in output folder
First, copy those on files on the xebuild/data folder, if you haven’t copied them, J -Runner will open the folder for you to copy them.
Copy the cpukey in the cpukey section Select the Dash Version you want
Select the type of hack you want – rgh, jtag or retail Press Advanced -> Create image without nanddump.bin
You need to select mobo type
You will be asked for LDV, you can find the current one by booting to xell
Your nand will be created and saved into folder
HOW-TO Change Lock down value Load Nand and cpu key Choose a dash version, nand type, and type of image you want (retail, glitch, jtag)
On advanced menu click Change Lock Down Value
The two CF/CG ldv boxes will be editable now allowing to input the current ldv value of your xbox
You can change either of them or both, it will get the highest value for ldv Programmer’s note: When you get the cpu key via Ethernet, current ldv will be mentioned in log
Now Press advanced-> Confirm Lock Down Value
and simply create an image as usual
