Questionable JTAG...

Discussion in 'Xbox 360 - Games & Content' started by overlord00, Dec 23, 2010.

Dec 23, 2010

Questionable JTAG... by overlord00 at 12:12 PM (1,356 Views / 0 Likes) 6 replies

  1. overlord00
    OP

    Member overlord00 A motherfucking birdplane

    Joined:
    Sep 12, 2009
    Messages:
    664
    Country:
    Australia
    Hey all,
    another brain teaser for you all;

    I have a friends 360 (phat) that i am considering testing for JTAG.
    However, there are several things I want to put forward to the people here first;

    I believe its a 512 Jasper as the onboard memory is "451MB" Capacity and "226MB" Free Space...
    and i've never done or attempted anything bigger than the 16mb consoles... (via LPT not usb)
    (12V DC, 12.1A ; 5VsB , 1A)

    secondly, the console is 8498 NXE... i know that everyone clams that the 8xxx kernel update fixed the smc exploit, but there are those amungst you that claim that there are some consoles that do not have the patched smc, and hence will jtag.

    i would like to know whats everyones take on this... worth trying to check? what would be the process?

    thanks all.
     
  2. FAST6191

    Reporter FAST6191 Techromancer

    pip
    Joined:
    Nov 21, 2005
    Messages:
    21,735
    Country:
    United Kingdom
    8498 is the summer (and presumably wave 5/6 update) and I would say not worth checking. What I suspect you or someone else read is that Xenon 8192 CD/CD is exploitable (note nothing to do with the dash).

    http://sites.google.com/site/radjnisharov/.../bootloader.png is probably worth looking at- it gives a rough overview of what goes and why things work.

    Process- same as any other JTAG. Wire up your NAND dumper, grab a couple of megs and check with that. You can dump the rest over LPT but that will take forever so most opt to rebuild it from parts like they do for smaller ones.
    https://docs.google.com/View?id=dnfmv5h_30dw33vpf4 covers how to do it.
     
  3. tk_saturn

    Member tk_saturn GBAtemp Psycho!

    Joined:
    Jan 26, 2010
    Messages:
    3,327
    Country:
    United Kingdom
    Your under no cirumstances is your console JTAG'able.

    There is no one who claims a 2.0.8498.0 is JTAG'able.

    Dashboard 2.0.8498.0 intentionally and specifically patched the JTAG exploit, and was released BEFORE the JTAG hack went public. This was no coincidence.

    The Last retail JTAG'ables came with 2.0.7363.0. Retail consoles which came with 2.0.7371.0 have the CB/CD patched and are not JTAG'able.

    As for 512MB, i've dumped one over LPT fine.
     
  4. mocalacace

    Member mocalacace GBAtemp Fan

    Joined:
    Sep 28, 2008
    Messages:
    322
    Location:
    127.0.0.1
    Country:
    United States
    It must have taken an eternity
     
  5. tk_saturn

    Member tk_saturn GBAtemp Psycho!

    Joined:
    Jan 26, 2010
    Messages:
    3,327
    Country:
    United Kingdom
    Not really, you only need to dump the first 2MB. 16MB Jaspers are still the better console to have though.
     
  6. hundshamer

    Member hundshamer GBAtemp Advanced Maniac

    Joined:
    May 22, 2009
    Messages:
    1,810
    Location:
    United States
    Country:
    United States
    Hey TK there are some 7371 consoles that are Jtaggable (my first was 7371). Fact is, 90% of the 7371 that came my way were hackable.

    As far as the whole 512MB I would suggest dumping the first 2MB, install xellous and dump the rest via firefox and combine it with the first 2MB you dumped earlier. It's much faster that way.
     
  7. tk_saturn

    Member tk_saturn GBAtemp Psycho!

    Joined:
    Jan 26, 2010
    Messages:
    3,327
    Country:
    United Kingdom
    "Retail consoles which came with 2.0.7371.0 have the CB/CD patched and are not JTAG'able" I'm certain of that, I have a JTAG from 19-06-2009 Lot 0925x, and even that had 2.0.7363. I've also had 2 consoles from Lot 0924x along with 3 from 0923x and likewise all had 2.0.7363.

    If you had a console which originally shipped with dashboard version 2.0.7363 or earlier (and manufactured before the cut off point), then updating those to 2.0.7371.0 wouldn't effect wether or not they are JTAG'able. But if they came from the factory with 2.0.7371, the CB/CD would have been patched preventing it from running the 4532 kernel.
     

Share This Page