Figuring out Motherboard Type: The Diagram only shows the generation. This is how to figure out which one of the two it is. Xenon - NON-HDMI - Type 1 and Type 2 Keyvaults Zephyr - HDMI - Type 2 Keyvaults Falcon - HDMI - Type 2 Keyvaults Opus - NON-HDMI - Type 2 Keyvaults Jasper - HDMI - Type 2 Keyvaults 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. 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 you know if your 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 to have the patched CB and will not be able to get JTAGGED. CB Versions: Now this check really isnt 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. Exploitable CB versions: Xenon: 1888, 1902, 1903, 1920,1921 Zephyr: 4559 Falcon/Opus: 5761, 5766, 5770 Jasper: 6712, 6723 Non-Exploitable CB Versions (CD = 8453 for all of them) Xenon: 1922, 1923, 1940 Zephyr: 4571, 4572, 4578, 4579 Falcon/Opus: 5771 Jasper: 6750 Credit to Exzib for original post
is there a diffrence between jtag & rgh? like if an updated phat console can get a rgh. or its just the slims.
RGH is a Jtag Only difference between old and new style is one was done on a old style kernal ir 7379 (or something like that) and the new RGH style of jtaging can be done on any kernal all consoles slims and phats
ooh . so if i have a er74 console 1ring?? newest kernel & recient updates .? it could be rgh. might just get it fixed cause it,s been good to me. 5 years 4 months 2 weeks & 7 days. ( gamer too. how easy is it to fix the er74 prob?
3 questions 1:where would i get this done? 2: what,s the max size for x360 slim 3: where can i get a jtag/rgh slim 360 w newest dash preety cheap?
Great tutorial! It is actually very handy to know what type of Xbox you're wanting to RGH or Jtag, also very handy if your buying one from someone else.
You have either a Corona or a Trinity Slim. Those aren't jtaggable, but if your on the right DB, you can RGH it.
I have a Corona 4g and it says glitch 2.0 in dashlaunch 3.17 on 17502. Is it jtagged? Also bit confuse about console type..mine was retail type..can anybody give a clue?? Thanks...
