Just thought i would start a thread for those of us playing around with Xbox360 homebrew (Hopefully i'm not the only one).
I'm one of those few lucky people who got brand new exploitable jasper arcade.. Lot#0924 and manufacturing date is 12th june 09.
I'm extremely thankful to Jshak and Adam for doing all these jtag stuff on my 360.
List of JTAG owners.
1.TheGoldenTouch: Jasper 512mb
2.muhd86: Jasper 512mb
3.faizy: Jasper 256mb
4.CerebralTiger: Falcon
5.obaid: Jasper 512mb
6.saqib126: Jasper 512mb
7.Game Addi: Falcon
8.Sliyk: Jasper
9.hashimzain: Jasper 256mb
10.pindiboy: Falcon
11.manigamer: Jasper 256mb
12.XecutionerX: Jasper 512mb
13.rayed: Xenon
14.coolerthannos: Jasper 256mb
15.M AzeeM K: Jasper
16.Goldenhawk: Xenon
17.Jshak: Jasper 256mb
18.CoLd FuSiOn: Jasper
How to run unsigned content (XBLA games/ DLC/) on your JTAG Xbox 360 by CerebralTiger
How To Patched Region-Lock Games by ViRuS ZianTi
How To Make Your Console Region Free
JTAG F.A.Q (Registration Required)
The ultimate tutorial to setup your j-tag (Registration Required)
JTAG and You! A Newbie's Guide (Registration Required)
All these infos are taken from xbox360iso.com and special credit goes to tmbinc, Tiros, Ruley, Sandungas, Phoney, Tony Bologna, kote aka logi, Phillip and anyone else I have missed.
Before you even Start:
Can this be done to all motherboard revisions?
Yes, all motherboard revisions are vulnerable to this hack. But the dashboard update on August 10, 2009 patched this hack. Some consoles that were manufactured or refurbished around June/July already have the patch applied. Which is why some kernels are not vulnerable.
How do I know what kernel version I have?
In the dashboard go to System Settings>Console Settings then scroll down to System Info. Your kernel version is shown here. In this picture the 360 has the 8955 kernel applied. This example is not vulnerable.
Kernel Vulnerability:
8498 and Higher - Any console with a kernel 8498 and higher have been patched to stop the hack.
7371 and lower - Any console with the 7371 kernel or a lower version of the kernel are most likely vulnerable to the hack.
7363 & 7371 - These the "iffy" kernels. With this kernels you have to dump your NAND to make sure that you have a vulnerable CB. Some consoles with this kernel already have the patch applied to them and cannot be JTAG'd. This would be if the console was repaired or manufactured since June/July. If repaired or manufactured before that should be exploitable.
Those consoles you see in tuts or on youtube that say they are on 8955 dash is because before the update they were on a less than 8XXX dash.
XBRebooter it is a modified version of 8955 and will display as 8955 in the system menu.
But again they are on this dash AFTER the mod but NOT before.
As of now if you are already on Stock 8955 there is no way to JTAG your system, but have hope for future.
What is the JTAG Hack?
This is a new hack which can boot homebrew code in less than 5 seconds. For now, all we need to know is that this is a new way to exploit the well-known 4532 kernel, in a way which also works on updated machines, unless they have been updated by the summer '09 update. It also works on all hardware types.
What does the JTAG Hack require?
1. The hack requires a console that has not been updated to the August09 dashboard. Although some consoles with the 7371 kernel have already been patched to stop the JTAG hack.
2. Some soldering skills.
3. A computer with a LPT(printer) port.
What does the JTAG hack allow me to do?
The JTAG hack unlocks your 360 and gives full control over it. Allowing.
- Linux
- Homebrew
- Unsigned Code
- Use a Re-booter(Freeboot or XBReboot)
Exploitable CB versions:
1888, 1902, 1903, 1920,1921: exploitable xenon
4558: exploitable Zephyr
5761, 5766, 5770: exploitable falcon
6712, 6723: exploitable jasper
Non-Exploitable CB Versions (CD = 8453 for all of them)
Xenon: 1922, 1923, 1940
Zephyr: 4571, 4572, 4578, 4579
Falcon/Opus: 5771
Jasper: 6750
I'm one of those few lucky people who got brand new exploitable jasper arcade.. Lot#0924 and manufacturing date is 12th june 09.
I'm extremely thankful to Jshak and Adam for doing all these jtag stuff on my 360.
List of JTAG owners.
1.TheGoldenTouch: Jasper 512mb
2.muhd86: Jasper 512mb
3.faizy: Jasper 256mb
4.CerebralTiger: Falcon
5.obaid: Jasper 512mb
6.saqib126: Jasper 512mb
7.Game Addi: Falcon
8.Sliyk: Jasper
9.hashimzain: Jasper 256mb
10.pindiboy: Falcon
11.manigamer: Jasper 256mb
12.XecutionerX: Jasper 512mb
13.rayed: Xenon
14.coolerthannos: Jasper 256mb
15.M AzeeM K: Jasper
16.Goldenhawk: Xenon
17.Jshak: Jasper 256mb
18.CoLd FuSiOn: Jasper
How to run unsigned content (XBLA games/ DLC/) on your JTAG Xbox 360 by CerebralTiger
How To Patched Region-Lock Games by ViRuS ZianTi
How To Make Your Console Region Free
JTAG F.A.Q (Registration Required)
The ultimate tutorial to setup your j-tag (Registration Required)
JTAG and You! A Newbie's Guide (Registration Required)
All these infos are taken from xbox360iso.com and special credit goes to tmbinc, Tiros, Ruley, Sandungas, Phoney, Tony Bologna, kote aka logi, Phillip and anyone else I have missed.
Before you even Start:
Can this be done to all motherboard revisions?
Yes, all motherboard revisions are vulnerable to this hack. But the dashboard update on August 10, 2009 patched this hack. Some consoles that were manufactured or refurbished around June/July already have the patch applied. Which is why some kernels are not vulnerable.
How do I know what kernel version I have?
In the dashboard go to System Settings>Console Settings then scroll down to System Info. Your kernel version is shown here. In this picture the 360 has the 8955 kernel applied. This example is not vulnerable.
Kernel Vulnerability:
8498 and Higher - Any console with a kernel 8498 and higher have been patched to stop the hack.
7371 and lower - Any console with the 7371 kernel or a lower version of the kernel are most likely vulnerable to the hack.
7363 & 7371 - These the "iffy" kernels. With this kernels you have to dump your NAND to make sure that you have a vulnerable CB. Some consoles with this kernel already have the patch applied to them and cannot be JTAG'd. This would be if the console was repaired or manufactured since June/July. If repaired or manufactured before that should be exploitable.
Those consoles you see in tuts or on youtube that say they are on 8955 dash is because before the update they were on a less than 8XXX dash.
XBRebooter it is a modified version of 8955 and will display as 8955 in the system menu.
But again they are on this dash AFTER the mod but NOT before.
As of now if you are already on Stock 8955 there is no way to JTAG your system, but have hope for future.
What is the JTAG Hack?
This is a new hack which can boot homebrew code in less than 5 seconds. For now, all we need to know is that this is a new way to exploit the well-known 4532 kernel, in a way which also works on updated machines, unless they have been updated by the summer '09 update. It also works on all hardware types.
What does the JTAG Hack require?
1. The hack requires a console that has not been updated to the August09 dashboard. Although some consoles with the 7371 kernel have already been patched to stop the JTAG hack.
2. Some soldering skills.
3. A computer with a LPT(printer) port.
What does the JTAG hack allow me to do?
The JTAG hack unlocks your 360 and gives full control over it. Allowing.
- Linux
- Homebrew
- Unsigned Code
- Use a Re-booter(Freeboot or XBReboot)
Exploitable CB versions:
1888, 1902, 1903, 1920,1921: exploitable xenon
4558: exploitable Zephyr
5761, 5766, 5770: exploitable falcon
6712, 6723: exploitable jasper
Non-Exploitable CB Versions (CD = 8453 for all of them)
Xenon: 1922, 1923, 1940
Zephyr: 4571, 4572, 4578, 4579
Falcon/Opus: 5771
Jasper: 6750
Last edited: