You are viewing our Forum Archives. To view or take place in current topics click here.
how to check if your console is Jtag-able
Posted:
how to check if your console is Jtag-ablePosted:
Status: Offline
Joined: Jan 16, 201113Year Member
Posts: 119
Reputation Power: 5
Status: Offline
Joined: Jan 16, 201113Year Member
Posts: 119
Reputation Power: 5
I see alot of threads asking "How do I know if my 360 is JTAG-able?". Well here is the guide to find out. This will not require anything other than you reading a few numbers in your dashboard and possibly your Manufacture Date from the sticker on the back of the console.
Figuring out Motherboard Type:
[ Register or Signin to view external links. ]
The Diagram only shows the generation. This is how to figure out which one of the two it is.
Xenon - NON-HDMI
Zephyr - HDMI
Falcon - HDMI
Opus - NON-HDMI
Jasper - HDMI
Finding the Kernel Version:
In the dashboard go to System Settings then go to 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 console is not vulnerable.
[ Register or Signin to view external links. ]
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.(Explained Below)
Kernels 7357/7363/7371
These 3 Kernels are what you may call the "iffy" kernels. Some contain a patched CB which makes the console un-exploitable.
How do I know if my console has the patched CB?
1. If the console manufacture date is BEFORE 6-1-2009 then the CB in the 360 will not be patched and you can perform the JTAG hack on it.
2. If the console manufacture date is AFTER 6-1-2009 then it is going to have the patched CB and will not be able to get JTAG'd.
CB Versions
Now this check really isn't needed. But if you get a console past 6-1-2009 and it has one of the iffy kernels then you could always dump the nand and check the CB version on it. Maybe you would be super lucky and got a exploitable box past the date. Chances are 99.99% you will get a patched box. But if you want to entertain yourself then here are the CB version's.
Open your NAND image in either Degraded or 360 Flash Tool and check the CB version. Here is a picture of Degraded. Any CB version past the one shown in the "Non-Exploitable" Section will not be exploitable. Only the ones in the Exploitable CB versions are JTAG-able.
[ Register or Signin to view external links. ]
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 have not created this, it is from EclipseModz, on S7
Figuring out Motherboard Type:
[ Register or Signin to view external links. ]
The Diagram only shows the generation. This is how to figure out which one of the two it is.
Xenon - NON-HDMI
Zephyr - HDMI
Falcon - HDMI
Opus - NON-HDMI
Jasper - HDMI
Finding the Kernel Version:
In the dashboard go to System Settings then go to 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 console is not vulnerable.
[ Register or Signin to view external links. ]
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.(Explained Below)
Kernels 7357/7363/7371
These 3 Kernels are what you may call the "iffy" kernels. Some contain a patched CB which makes the console un-exploitable.
How do I know if my console has the patched CB?
1. If the console manufacture date is BEFORE 6-1-2009 then the CB in the 360 will not be patched and you can perform the JTAG hack on it.
2. If the console manufacture date is AFTER 6-1-2009 then it is going to have the patched CB and will not be able to get JTAG'd.
CB Versions
Now this check really isn't needed. But if you get a console past 6-1-2009 and it has one of the iffy kernels then you could always dump the nand and check the CB version on it. Maybe you would be super lucky and got a exploitable box past the date. Chances are 99.99% you will get a patched box. But if you want to entertain yourself then here are the CB version's.
Open your NAND image in either Degraded or 360 Flash Tool and check the CB version. Here is a picture of Degraded. Any CB version past the one shown in the "Non-Exploitable" Section will not be exploitable. Only the ones in the Exploitable CB versions are JTAG-able.
[ Register or Signin to view external links. ]
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 have not created this, it is from EclipseModz, on S7
The following 1 user thanked Evilmodder for this useful post:
dingdongwill (01-24-2011)
#2. Posted:
Status: Offline
Joined: Dec 22, 200914Year Member
Posts: 5,352
Reputation Power: 461
Status: Offline
Joined: Dec 22, 200914Year Member
Posts: 5,352
Reputation Power: 461
Good tut, should help some people out 8)
- 0useful
- 0not useful
#3. Posted:
Status: Offline
Joined: Jan 16, 201113Year Member
Posts: 119
Reputation Power: 5
Status: Offline
Joined: Jan 16, 201113Year Member
Posts: 119
Reputation Power: 5
Cheers pal, glad to help
- 0useful
- 0not useful
#4. Posted:
Status: Offline
Joined: Sep 08, 201014Year Member
Posts: 419
Reputation Power: 17
Status: Offline
Joined: Sep 08, 201014Year Member
Posts: 419
Reputation Power: 17
Evilmodder wrote I see alot of threads asking "How do I know if my 360 is JTAG-able?". Well here is the guide to find out. This will not require anything other than you reading a few numbers in your dashboard and possibly your Manufacture Date from the sticker on the back of the console.i updated my one so im goin to buy my mates rrod xbox that is not updated
Figuring out Motherboard Type:
[ Register or Signin to view external links. ]
The Diagram only shows the generation. This is how to figure out which one of the two it is.
Xenon - NON-HDMI
Zephyr - HDMI
Falcon - HDMI
Opus - NON-HDMI
Jasper - HDMI
Finding the Kernel Version:
In the dashboard go to System Settings then go to 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 console is not vulnerable.
[ Register or Signin to view external links. ]
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.(Explained Below)
Kernels 7357/7363/7371
These 3 Kernels are what you may call the "iffy" kernels. Some contain a patched CB which makes the console un-exploitable.
How do I know if my console has the patched CB?
1. If the console manufacture date is BEFORE 6-1-2009 then the CB in the 360 will not be patched and you can perform the JTAG hack on it.
2. If the console manufacture date is AFTER 6-1-2009 then it is going to have the patched CB and will not be able to get JTAG'd.
CB Versions
Now this check really isn't needed. But if you get a console past 6-1-2009 and it has one of the iffy kernels then you could always dump the nand and check the CB version on it. Maybe you would be super lucky and got a exploitable box past the date. Chances are 99.99% you will get a patched box. But if you want to entertain yourself then here are the CB version's.
Open your NAND image in either Degraded or 360 Flash Tool and check the CB version. Here is a picture of Degraded. Any CB version past the one shown in the "Non-Exploitable" Section will not be exploitable. Only the ones in the Exploitable CB versions are JTAG-able.
[ Register or Signin to view external links. ]
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 have not created this, it is from EclipseModz, on S7
- 1useful
- 0not useful
#5. Posted:
Status: Offline
Joined: Jan 16, 201113Year Member
Posts: 119
Reputation Power: 5
Status: Offline
Joined: Jan 16, 201113Year Member
Posts: 119
Reputation Power: 5
Hopefully you will be able to jtag it then. I recently updated a RROD, once fixed and it had the blades old dash i was wounded lol.
- 0useful
- 0not useful
#6. Posted:
Status: Offline
Joined: Feb 02, 201113Year Member
Posts: 664
Reputation Power: 28
Status: Offline
Joined: Feb 02, 201113Year Member
Posts: 664
Reputation Power: 28
nice post , helped me taaa
- 0useful
- 0not useful
You are viewing our Forum Archives. To view or take place in current topics click here.