Start To Finish Tutorial For Jtag Users To Get On

How to get Xlink Kai to work for Jtag Users OnlyIím writing this hoping to get rid of the ďwhy canít connectĒ questions when people join arenas.Things you will need:1. Your original nand dump (Have your CPU Key and 1BL Key ready)2. Freeboot .032 files (xbins)3. 9199 files from xbins4. The correct hacked smc.bin for your motherboard (get an xbr image for your motherboard, extract the smc_dec.bin)5. Dashlaunch 1.0 Patches (located in development  system apps at xbins)6. The ping patch (located in development  system apps at xbins)7. Xlink Kai

Step 1. Building your new Freeboot ImageA) Unzip the freeboot .032 file and then unzip the 9199.zip into the data of the previously unzipped freeboot .032 folder. Unzip the dashlaunch file into its own folder. Once unzipped, copy the patches located in the freeboot patches folder of the dashlaunch folder into the bin folder of the previously unzipped freeboot .032 folder. Copy a cmd.exe into the root of the freeboot .032 folder. Finally, copy your orig.bin (or whatever you named it) into the root of the freeboot .032 folder. Once you have completely finish part 1, open the command prompt that you copied into the root of the freeboot .032 folder and type in the following command: a. ibuild.exe x -d temp\ -p [cpu key] -b [1bl key] orig.bini. You must replace [cpu key] with your cpu key (remove the brackets)ii. You must replace [1bl key] with the 1bl key which can be found by googling (remove brackets)b. If the command is successful you will not get an error. Now go into the temp folder located inside of the freeboot .032 folder and you will see that your orig.bin has been extracted. You need to copy the following 10 files from the temp folder to the data folder: crl.bin, crl.bin.meta, extended.bin, extended.bin.meta, kv.bin, odd.bin, odd.bin.meta, secdata.bin, secdata.bin.mata, smc_config.binc. Copy the smc_dec.bin you extracted earlier from the correct xbr image for your motherboard, to the data folder located in the freeboot .032 folder. Rename it to smc.bind. Now that you have all of the files located in the correct folder, build the image with this command:i. ibuild.exe c freeBOOT -c [console] -d data\ -p [cpu key] -b [1bl key] bin\image.bin bin\fuses.bin1. Replace console with your motherboard type ie xenon, falcon, jasper (remove the brackets)2. Replace [cpu key] with your own just like before, and do the same for the 1BL just like you did before (remove the brackets)e. Your image is now rebuilt and it is located in the bin folder of the freeboot .032 folder. It is called image.bin. Rename it to updflash.binf. Flash your new updflash.bin using xellous to avoid having to worry about bad blocks.Step 2. Preparing Your Console After You Have Flashed Your New Freeboot Image.Now that you have flashed your new freeboot image, you are almost done preparing your console. 1. Unzip the systempingcheck.zip and transfer kxam.patch to the root of hdd1 and you can also transfer it to your usb hdd. Do both to be safe.2. Located inside of the Dashlaunch folder you extracted earlier, is a folder called flash_installer. Transfer that folder to your xbox 360.3. Located inside of the Dashlaunch folder you extracted earlier is a file called samplelaunch.ini. Configure it (Case sensitive hard drive is LHdd and usb is LUsb0) to your liking (read the dashlaunch readme if you canít understand what to do just by looking) and transfer it to the root of hdd1 and/or usb. 4. Run the launch.xex from the flash_installer folder. Follow the prompt to put it into the flash, exit, then reboot your console. If you set your ini up correctly you will auto launch fsd or xexmenu or whatever you set it to auto launch.5. Get all of the newest title updates for the games you want to use xlink with. There are a few websites that have title updates (which I wonít list here) and you can also use title downloader 1.2. You will need your content.xml from freestyle dash to use that program.Step 3. Setting Up Xlink and Your System Link SetupPeople use different setups but Iím only going to explain connecting to xlink through a laptop with a wireless internet connection. If you canít figure out how to portforward for your setup go to xlinkís website www.teamxlink.co.uk.1. Download/install xlink, create a tag etc.2. Open the Xlink Kai Configuration, switch option to ui, enter in your username/password, hit save and exit.3. Make sure you have disabled xbox live using the family access settings on your 3604. On your 360 go to network settings, switch the ip settings to manual, give it an ip, set the subnet mask to 255.255.255.0, and the default gateway to your routerís ip address5. On your laptop give the Ethernet port of that your 360 is using an ip address (different ip then the one you used in system settings of your 360), subnet mask 255.255.255.0 and set the default gateway and dns to the ip of your router.6. Open an internet page and type the ip address of your router. Find the settings for portforwarding and forward port 30000 to your laptopís ip address not the 360ís address (this only applies using the setup Iím describing).YOU ARE DONE AND SHOULD BE ABLE TO CONNECT, IF YOU CANíT ITíS YOUR OWN FAULT AT THIS POINTYOUR FRIEND JPARKER AKA SOULWARRIOR AKA SOULWARRIOR 71K

You do know that this can made way easier.1. get nand dump and cpu key from xellous.2. download freeboot toolbox3. get dashlaunch4. open freeboot toolbox and click make custom image (if you have a bb console disable autodetect)5. pick nand where it says dashlaunch6. click create freeboot7. around 80% it will open a folder called freeboot. pick the dashlaunch patch for your specific console and copy it to the bin folder inside the freeboot folder that opened up.8. go back to freeboot toolbox and click ok.9. it will say done. go to where you told it to save your image, rename it to updflash.bin and put it on a usb stick.10. a(1).start up your xbox, then unplug it, plug the usb stick in and plug it back in.a(2) press eject to start xellous. it will update the 360.b(1) start up flash360 and let it flash your console.11. open the flash_installer folder in your dashlaunch folder, edit the launch.ini in there to your liking.for it to launch nxe set it to the following (you can delete the but_x part if you dont want to launch freestyle dash with x):[QuickLaunchButtons]BUT_X = LHdd:\Freestyle\FreestyleDash.xexDefault =

for it to launch freestyle dash, set it to the following (it will launch nxe if you hold x):[QuickLaunchButtons]BUT_X = Default = LHdd:\Freestyle\FreestyleDash.xex

if you want xexmenu, set it to the following (it will launch fsd if you press x):[QuickLaunchButtons]BUT_X = LHdd:\Freestyle\FreestyleDash.xexDefault = LHdd:\Content\0000000000000000\C0DE9999\00080000\C0DE99990F586558

12. ftp the flash_installer folder to your 360 and launch it from xexmenu/fsd and press a for it to install dashlaunch.13. go on xlink kai and add theninjaway because you are done.

doing it manually also allows for mistakes that wouldn't be made usually with an auto builder.ive never had problems with the toolbox.however i've e79'd a couple of times building a custom image because of smc issues.

There are plenty of people who have run into problems using autobuilders. Doing it manually consists of copy and pasting a few files, and copying 2 commands into a command prompt. If people can follow directions, doing it manually is quite simple. On top of that, telling people to use flash 360 instead of xellous to flash their image is also not smart either. Flash 360 does not handle bad blocks correctly, but xellous does. Trust me my friend, there is a reason I wrote the tutorial the way I did.

my console is on XBR3 and im looking at updating to freeboot with dashlaunch/ping removal. If I dont have my original nand, am I able to dump the nand with xellous and use he"flashump.bin" it creates instead of the original nand?

my console is on XBR3 and im looking at updating to freeboot with dashlaunch/ping removal. If I dont have my original nand, am I able to dump the nand with xellous and use he"flashump.bin" it creates instead of the original nand?

Then you should probably use freeboot toolbox. I have to ask, why don't you have your original nand? If you jtagged it yourself did you not back it up? If you bought it jtagged, you should ask the seller to give you the original nand because there was no reason for the seller not to give it to you.

Then you should probably use freeboot toolbox. I have to ask, why don't you have your original nand? If you jtagged it yourself did you not back it up? If you bought it jtagged, you should ask the seller to give you the original nand because there was no reason for the seller not to give it to you.

Thanks. the console was already jtagged and the seller didnt have the orig nand.