You are viewing our Forum Archives. To view or take place in current topics click here.
*Sticky* How to host Jtag Lobbies after patch !**READ** REP!
Posted:
*Sticky* How to host Jtag Lobbies after patch !**READ** REP!Posted:
Status: Offline
Joined: Feb 06, 201014Year Member
Posts: 373
Reputation Power: 18
Status: Offline
Joined: Feb 06, 201014Year Member
Posts: 373
Reputation Power: 18
Just incase you didnt know yet
you dont use xbr
you use freeBOOT 0.031
here is the [ Register or Signin to view external links. ] [ Register or Signin to view external links. ]
libeay32.dll error? Click [ Register or Signin to view external links. ] (Copy bin/libeay32.dll from the RAR into the same directory as ibuild)
Completely replaces XBR! No dual-nand (Cygnos) needed!
It is confirmed that older original NAND dumps are supported by ibuild. 7371 is preferred, but not required!
_________________________________________________________________________________________
[align=center]Ok guys I tried to build my own image to see how easy it is and I was successful but I didn’t flash my 360 so please correct me if something is wrong here
(my only concern is that I obtained the smc.bin from Cygnos360 V2 SMC Collection.zip)
This was done on Vista 32-bit
Tools needed:
1) Auto Xbins : Auto Xbins
2) freeBOOT-0.031.zip from xbins : /XBOX 360/development/freeBOOT/
3) 9199.zip from xbins: /XBOX 360/development/freeBOOT/
4) Cygnos360 V2 SMC Collection.zip from xbins: /XBOX 360/development/Cygnos360/
5) libeay32.zip libeay32
6) Your original nand image (**DOES NOT NEED TO BE 7371**)
7) Your CPU key
1. First things first open up freeBOOT-0.031.zip and extract it to your desktop
2. Open up the libeay32.zip and extract the libeay32.dll to the freeBOOT-0.031 folder:
3. Take your original nand dump and for the sake of the guide rename it to original.bin, after put that file original.bin into your freeboot-0.031 it should look like this:
4. Next you are going to go to your desktop, hold down shift and while holding shift down click open in command window here:
6. Now you are going to have to copy this line and paste it into the CMD window (just replace the CPUKEY line with your cpukey):
ibuild.exe x -d temp -p CPUKEY -b DD88AD0C9ED669E7B56794FB68563EFA original.bin and press enter.
This is what your window should look like the red is supposed to be your cpukey (I blocked out mine)
7. Now open up 9199.zip and put all the contents from the zip into the freeBOOT-0.031data folder
8. Now go to freeBOOT-0.031temp and take out these files from there and put them into the freeBOOT-0.031data folder
- crl.bin
- crl.bin.meta
- extended.bin
- extended.bin.meta
- kv.bin
- odd.bin
- odd.bin.meta
- secdata.bin
- secdata.bin.meta
- smc_config.bin
9. Now open up Cygnos360 V2 SMC Collection.zip and pick the file that’s associated for your console and extract it. After you extract it rename the file to smc.bin Now put the smc.bin file into the freeBOOT-0.031data folder
10. Now go to your CMD window and copy this line and paste it in and press enter:
ibuild.exe c freeBOOT -c CONSOLE -d data -p CPUKEY -b DD88AD0C9ED669E7B56794FB68563EFA binimage.bin binfuses.bin
- Replace CONSOLE with your console name one of these: xenon, zephyr, falcon, jasper, jasper256 or jasper512
- Once again replace CPUKEY with your cpukey
11. Your done now go to the freeboot-0.031bin folder and you should see image.bin, This is your newly built nand image now go and flash it the way you prefer.
**For flashing with XBR this should work (didnt test it): Take the image.bin that was created from the freeboot-0.031bin folder and rename it to updflash.bin Then put updflash.bin into a flash drive (USB Stick) Then run 360Flashtool from your 360 When in 360Flashtool press **Button A - Write updflash.bin to Nand** and thats it you should have a newly installed freeBOOT with 9199 kernal.
**If your avatars dont work after flashing freeBOOT from what I read (and what I assumed originally) you take the 9199 update and run it like any normal update. The xbox will recognize you have the 9199 update but that you are missing the avatar files so it will then just install the files needed for avatar support
Optional:
If you want xellous installed right before step 9 open up XeLLous_v1.0.zip XeLLous_v1.0 and extract xell-2f.bin and put that file into freeBOOT-0.031bin
(let it overwrite the old file) and then continue with step 10 and build your image.
I hope this helps clear the question for noobs such as me I just used some common sense to do this hope it helps enjoy freeboot and thanks to ikari for freeboot
*I am not responsible for ANYTHING that happens while following this guide*
If anything is incorrect please let me know so I can fix it I am in no way an expert at all and if I missed anything let me know. Cheers
OR
________________________________________________________________________________________
/ _|_ __ ___ ___| __ ) / _ / _ _ _|
| |_| '__/ _ / _ _ | | | | | | || |
| _| | | __/ __/ |_) | |_| | |_| || |
|_| |_| ___|___|____/ ___/ ___/ |_|
[v0.03 - coded by ikari]
I. Introduction
================
freeBOOT is a rebooter for the Microsoft Xbox 360. This version of freeBOOT
allows you to reboot into kernel 2.0.9199 on all Xenon, Zephyr, Falcon, and
Jasper consoles, which are vulnerable to the JTAG hack.
This version of freeBOOT no longer requires a second flash memory and will
thus work with all currently existing solutions.
II. Bug Fixes
=============
none
III. New Features
=================
- updated to kernel 2.0.9199
- now supports all consoles and flashing solutions (ikari)
- removed memory protections
Code can be executed and modified anywhere in the range from 0x80000000
to 0x9FFFFFFF. This can be used to create game trainers and will allow
for porting of emulators, which rely on dynamic compilation.
- encrypted DevKit XEXes are now working
- includes dash launch patch
- LIVE/PIRS/GOD content fully working
- internal security breach reports deactivated (Redline99)
- easier image generation process (ikari)
- ibuild can now also generate single flash XeLL and original images (ikari)
IV. Instructions
================
In contrast to previous freeBOOT releases, the image generation process has
been made a lot easier. As prerequisites you will need an image of your
console updated to kernel 2.0.7371 and an archive "9199.zip" available
at the usual places.
1. Extract your original image
Extract your original 7371 image with the following command:
> ibuild x -d temp -b 111ACTUALKEY111 -p 111ACTUALKEY111 7371.bin
2. Extract "9199.zip" archive
Extract the contents of the "9199.zip" archive into the "data"
directory.
3. Copy these files from "temp" to "data" directory
- crl.bin
- crl.bin.meta
- extended.bin
- extended.bin.meta
- kv.bin
- odd.bin
- odd.bin.meta
- secdata.bin
- secdata.bin.meta
- smc_config.bin
4. Patch SMC
Put a patched "smc.bin" in the "data" directory. For Cygnos360, a
patched SMC can be created with their software. Theres also a
collection of patched SMCs available at the usual places. Make sure
to pick the right one for your console.
For other solutions, a patched SMC can be extracted from previously
released XeLL images.
5. Create the freeBOOT image
Finally, create your freeBOOT image with this command:
> ibuild c freeboot -c <console> -d data -b 111ACTUALKEY111
-p 111ACTUALKEY111 binimages.bin binfuses.bin
Replace <console> with either "xenon", "zephyr", "falcon", "jasper",
"jasper256" or "jasper512". (Without quotes)
6. Flash result
Flash the entire resulting image using Nandpro, Flash360, or XeLLouS.
Power cycle (remove PSU for ~1 minute) before booting for the first time.
you dont use xbr
you use freeBOOT 0.031
here is the [ Register or Signin to view external links. ] [ Register or Signin to view external links. ]
libeay32.dll error? Click [ Register or Signin to view external links. ] (Copy bin/libeay32.dll from the RAR into the same directory as ibuild)
Completely replaces XBR! No dual-nand (Cygnos) needed!
It is confirmed that older original NAND dumps are supported by ibuild. 7371 is preferred, but not required!
_________________________________________________________________________________________
[align=center]Ok guys I tried to build my own image to see how easy it is and I was successful but I didn’t flash my 360 so please correct me if something is wrong here
(my only concern is that I obtained the smc.bin from Cygnos360 V2 SMC Collection.zip)
This was done on Vista 32-bit
Tools needed:
1) Auto Xbins : Auto Xbins
2) freeBOOT-0.031.zip from xbins : /XBOX 360/development/freeBOOT/
3) 9199.zip from xbins: /XBOX 360/development/freeBOOT/
4) Cygnos360 V2 SMC Collection.zip from xbins: /XBOX 360/development/Cygnos360/
5) libeay32.zip libeay32
6) Your original nand image (**DOES NOT NEED TO BE 7371**)
7) Your CPU key
1. First things first open up freeBOOT-0.031.zip and extract it to your desktop
2. Open up the libeay32.zip and extract the libeay32.dll to the freeBOOT-0.031 folder:
3. Take your original nand dump and for the sake of the guide rename it to original.bin, after put that file original.bin into your freeboot-0.031 it should look like this:
4. Next you are going to go to your desktop, hold down shift and while holding shift down click open in command window here:
6. Now you are going to have to copy this line and paste it into the CMD window (just replace the CPUKEY line with your cpukey):
ibuild.exe x -d temp -p CPUKEY -b DD88AD0C9ED669E7B56794FB68563EFA original.bin and press enter.
This is what your window should look like the red is supposed to be your cpukey (I blocked out mine)
7. Now open up 9199.zip and put all the contents from the zip into the freeBOOT-0.031data folder
8. Now go to freeBOOT-0.031temp and take out these files from there and put them into the freeBOOT-0.031data folder
- crl.bin
- crl.bin.meta
- extended.bin
- extended.bin.meta
- kv.bin
- odd.bin
- odd.bin.meta
- secdata.bin
- secdata.bin.meta
- smc_config.bin
9. Now open up Cygnos360 V2 SMC Collection.zip and pick the file that’s associated for your console and extract it. After you extract it rename the file to smc.bin Now put the smc.bin file into the freeBOOT-0.031data folder
10. Now go to your CMD window and copy this line and paste it in and press enter:
ibuild.exe c freeBOOT -c CONSOLE -d data -p CPUKEY -b DD88AD0C9ED669E7B56794FB68563EFA binimage.bin binfuses.bin
- Replace CONSOLE with your console name one of these: xenon, zephyr, falcon, jasper, jasper256 or jasper512
- Once again replace CPUKEY with your cpukey
11. Your done now go to the freeboot-0.031bin folder and you should see image.bin, This is your newly built nand image now go and flash it the way you prefer.
**For flashing with XBR this should work (didnt test it): Take the image.bin that was created from the freeboot-0.031bin folder and rename it to updflash.bin Then put updflash.bin into a flash drive (USB Stick) Then run 360Flashtool from your 360 When in 360Flashtool press **Button A - Write updflash.bin to Nand** and thats it you should have a newly installed freeBOOT with 9199 kernal.
**If your avatars dont work after flashing freeBOOT from what I read (and what I assumed originally) you take the 9199 update and run it like any normal update. The xbox will recognize you have the 9199 update but that you are missing the avatar files so it will then just install the files needed for avatar support
Optional:
If you want xellous installed right before step 9 open up XeLLous_v1.0.zip XeLLous_v1.0 and extract xell-2f.bin and put that file into freeBOOT-0.031bin
(let it overwrite the old file) and then continue with step 10 and build your image.
I hope this helps clear the question for noobs such as me I just used some common sense to do this hope it helps enjoy freeboot and thanks to ikari for freeboot
*I am not responsible for ANYTHING that happens while following this guide*
If anything is incorrect please let me know so I can fix it I am in no way an expert at all and if I missed anything let me know. Cheers
OR
________________________________________________________________________________________
/ _|_ __ ___ ___| __ ) / _ / _ _ _|
| |_| '__/ _ / _ _ | | | | | | || |
| _| | | __/ __/ |_) | |_| | |_| || |
|_| |_| ___|___|____/ ___/ ___/ |_|
[v0.03 - coded by ikari]
I. Introduction
================
freeBOOT is a rebooter for the Microsoft Xbox 360. This version of freeBOOT
allows you to reboot into kernel 2.0.9199 on all Xenon, Zephyr, Falcon, and
Jasper consoles, which are vulnerable to the JTAG hack.
This version of freeBOOT no longer requires a second flash memory and will
thus work with all currently existing solutions.
II. Bug Fixes
=============
none
III. New Features
=================
- updated to kernel 2.0.9199
- now supports all consoles and flashing solutions (ikari)
- removed memory protections
Code can be executed and modified anywhere in the range from 0x80000000
to 0x9FFFFFFF. This can be used to create game trainers and will allow
for porting of emulators, which rely on dynamic compilation.
- encrypted DevKit XEXes are now working
- includes dash launch patch
- LIVE/PIRS/GOD content fully working
- internal security breach reports deactivated (Redline99)
- easier image generation process (ikari)
- ibuild can now also generate single flash XeLL and original images (ikari)
IV. Instructions
================
In contrast to previous freeBOOT releases, the image generation process has
been made a lot easier. As prerequisites you will need an image of your
console updated to kernel 2.0.7371 and an archive "9199.zip" available
at the usual places.
1. Extract your original image
Extract your original 7371 image with the following command:
> ibuild x -d temp -b 111ACTUALKEY111 -p 111ACTUALKEY111 7371.bin
2. Extract "9199.zip" archive
Extract the contents of the "9199.zip" archive into the "data"
directory.
3. Copy these files from "temp" to "data" directory
- crl.bin
- crl.bin.meta
- extended.bin
- extended.bin.meta
- kv.bin
- odd.bin
- odd.bin.meta
- secdata.bin
- secdata.bin.meta
- smc_config.bin
4. Patch SMC
Put a patched "smc.bin" in the "data" directory. For Cygnos360, a
patched SMC can be created with their software. Theres also a
collection of patched SMCs available at the usual places. Make sure
to pick the right one for your console.
For other solutions, a patched SMC can be extracted from previously
released XeLL images.
5. Create the freeBOOT image
Finally, create your freeBOOT image with this command:
> ibuild c freeboot -c <console> -d data -b 111ACTUALKEY111
-p 111ACTUALKEY111 binimages.bin binfuses.bin
Replace <console> with either "xenon", "zephyr", "falcon", "jasper",
"jasper256" or "jasper512". (Without quotes)
6. Flash result
Flash the entire resulting image using Nandpro, Flash360, or XeLLouS.
Power cycle (remove PSU for ~1 minute) before booting for the first time.
#2. Posted:
Status: Offline
Joined: Apr 06, 201014Year Member
Posts: 2,933
Reputation Power: 124
Status: Offline
Joined: Apr 06, 201014Year Member
Posts: 2,933
Reputation Power: 124
ty for advise on how to do it
- 0useful
- 0not useful
#3. Posted:
Status: Offline
Joined: Apr 16, 201014Year Member
Posts: 2,132
Reputation Power: 200
Status: Offline
Joined: Apr 16, 201014Year Member
Posts: 2,132
Reputation Power: 200
this has been posted everywhere.
- 0useful
- 0not useful
#4. Posted:
Status: Offline
Joined: Mar 24, 200915Year Member
Posts: 1,411
Reputation Power: 88
Status: Offline
Joined: Mar 24, 200915Year Member
Posts: 1,411
Reputation Power: 88
why would someone sticky this ?
its already posted
its already posted
- 0useful
- 0not useful
#5. Posted:
Status: Offline
Joined: Feb 06, 201014Year Member
Posts: 373
Reputation Power: 18
Status: Offline
Joined: Feb 06, 201014Year Member
Posts: 373
Reputation Power: 18
Bump
- 0useful
- 0not useful
#6. Posted:
Status: Offline
Joined: Aug 07, 200915Year Member
Posts: 4,469
Reputation Power: 316
Status: Offline
Joined: Aug 07, 200915Year Member
Posts: 4,469
Reputation Power: 316
Why would you bump a topic you stole from someone..
- 0useful
- 0not useful
#7. Posted:
Status: Offline
Joined: Feb 01, 200915Year Member
Posts: 3,885
Reputation Power: 2122
Status: Offline
Joined: Feb 01, 200915Year Member
Posts: 3,885
Reputation Power: 2122
We appreciate you posting this, but it has been posted before.
Closed
Groovy
Closed
Groovy
- 0useful
- 0not useful
You are viewing our Forum Archives. To view or take place in current topics click here.