J Runner Tutorial

15
J-Runner (basic guide) J-Runner is a GUI that uses Xebuild, Xell-reloaded, Xellous (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 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 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). As you can see after opening the app J-Runner is designed to be simple and intuitive: The process runs from left to right (Glitch Selected)

Transcript of J Runner Tutorial

Page 1: J Runner Tutorial

J-Runner (basic guide)

J-Runner is a GUI that uses Xebuild, Xell-reloaded, Xellous (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 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 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).

As you can see after opening the app J-Runner is designed to be simple and intuitive:

The process runs from left to right (Glitch Selected)

Page 2: J Runner Tutorial

And the same for JTAG (Obviously Flashing CoolRunner is not used)

1. Read Nand:

The default is set to 2 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 – flash your CR and then try to boot the console. If your console doesn’t

boot at this point – then your soldering isn’t correct! No changes have been made to your

nand – so it should boot fine.

3. Create ECC: / Create Xellous:

This uses the nanddump1.bin that is loaded in source box! It creates the file you need to

flash to your nand – this contains xell and the glitch info(or xellous file with your keyvault) to

allow you to boot your console to xell/Xellous and obtain your key. It then loads that file into

Source box ready for writing.

4. Write ECC: / Write Xellous:

Does what it says on the tin – writes the ECC/Xellous 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 /Xellous. 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.

Page 3: J Runner Tutorial

Image selections

You select what type of image you are trying to create JTAG, Glitch or Retail. 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 text

Aud_Clamp selection is also available for JTAG images

Some additional Functions F1 - Restarts the application

F2 - Grabs the Config from the Nand (identify the nand)

F5 - Grab CPU Key over network

F6 - Custom commands for nand

F9 - check source file against cpukeydb

F12 - Forces a re-download of the application.

Read Nand: The default is 2 reads

Ensure you have Nand-X all connected with drivers installed. Board plugged in but not powered on,

then press the Read Nand button,

You are faced with an options box of nand type. 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. J-Runner will however check the nand type upon starting read –

so if you have selected incorrectly – it will select the correct nand for you.

Page 4: J Runner Tutorial

Select your nand and press OK. 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 or Full

Dumps)

Once complete the second dump begins automatically.

Page 5: J Runner Tutorial

Upon both dumps being auto loaded into GUI for automatic comparison.

Look in the log for the comparison result

Page 6: J Runner Tutorial

With “Glitch” - Selected

Flash CoolRunner At this point you should Flash the CoolRunner with relevant file

Press the Flash Coolrunner button

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 this and ensure there are no error messages

NOTE: If you have bad blocks in the first 50 blocks, J-Runner will remap these for you and create a

fixed file from which to create the ECC file.

Page 7: J Runner Tutorial

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 to your nand.

Press write ECC

You will then see this

Page 8: J Runner Tutorial

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

Page 9: J Runner Tutorial

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 the 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.

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 top right hand box and you will get a CPU Key verified message

in the log!

At this point you now have all the info you need to create a Freeboot image.

Shutdown the Xbox and proceed

Page 10: J Runner Tutorial

With “JTAG” Selected

Flash CoolRunner This Button is NOT USED as part of JTAG HACK – AS SUCH IS DISABLED - IGNORE IT

Create Xellous At this point press the Create Xellous 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 Xellous You now have to write the Xellous image with your data to your nand.

Press write Xellous

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 Xellous on your screen (remember Xellous wont work with HDMI

cable)

Page 11: J Runner Tutorial

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)

Then J-Runner will reload your original nanddump1.bin into source box again

Now you should have all the info in top right hand box ( if CPU key is correct) and you will get a “CPU

Key verified” message in the log!

Page 12: J Runner Tutorial

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 text

Page 13: J Runner Tutorial

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

Page 14: J Runner Tutorial

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

Page 15: J Runner Tutorial

Unplug power for a few seconds

At this point I plugged in my USB with Freestyle Dash folder (\FSD)

Then replug and boot it.

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!