Originally posted by Jinkazuya: I am just wondering if 2009-06-18 jasper console is jtaggeable as I would like to get one jasper console and have it jtagged.
If you have connected to XBOX live and updated since you bought it, the efuses have been blown and you will not be able to jtag.. If you haven't updated, you're probably ok. If you have revision 8955, it's too late. Check your revision in the system properties menu and go from there.
"All drives should be updated to Lite Touch + (LT+) firmware if playing on XBOX live. Samsung drives and pre-78/79 Hitachi drives do not utilize AP 2.5. All other drives are considered to be detectable by Microsoft (YMMV). Make sure all rips are ABGX verified, contain SSv2, and patched AP2.5 (where needed). XGD3 must currently be burned on new drive with PC Burner Max firmware for 100% rip. All modded consoles can be potentially unsafe for use on XBOX live."
Come talk with us on efnet at #elitemods !!! or just click ME
ALSO, DO NOT SEND ME MESSAGES ON LIVE REGARDING MODDING CONSOLES, OR HOW I PLAYED A CERTAIN GAME EARLY. I WILL NOT RESPOND. I WILL INSTEAD DELETE YOUR MESSAGE, AND BLOCK ALL COMMUNICATION FROM YOU. JUST SEND ME A PM ON HERE.
But the console I'd like to get is 2009-06-18...And I heard that this is the cutoff date that the xbox360 is able to be jtaggeable. So I just wanna sure make if it could be jtagged before I make my purchase.
it could be. i just go by the rule of anything after june is a no-go. but if the seller states it jtagable and its not, just file a complaint or ask for your $$ back.
Come talk with us on efnet at #elitemods !!! or just click ME
ALSO, DO NOT SEND ME MESSAGES ON LIVE REGARDING MODDING CONSOLES, OR HOW I PLAYED A CERTAIN GAME EARLY. I WILL NOT RESPOND. I WILL INSTEAD DELETE YOUR MESSAGE, AND BLOCK ALL COMMUNICATION FROM YOU. JUST SEND ME A PM ON HERE.
All of the "June" boxes I came across had dashboard 7367 on them, but the CB was not exploitable (like wabashman said "patched"). So even if it's a 7367 i doubt it can be tagged.
I had to do quite a bit of reading on this before making my purchase. I purchased a brand new Jasper MFR date 6-11-2009. It had the 2.0.7367.0 dash with a CB 6723, so it was exploitable. Where you need to find out additional info is the TEAM and LOT number. Right off the top of my head I can't remember my LOT number but the TEAM was FDOU. I had read a post with someone purchasing a Jasper brand new made on 5-29-2009 thinking it was exploitable. It had the 2.0.7367.0 dash but it's CB was 6750... already patched. The TEAM was CSON.
So I'm pretty confident to say if you find a Jasper made before 6-18-2009 and the TEAM is FDOU, you should have an exploitable CB. This info is all U.S.A. based. I'm sure TEAM, LOT numbers, and the "cut-off" date differ else where.
"All drives should be updated to Lite Touch + (LT+) firmware if playing on XBOX live. Samsung drives and pre-78/79 Hitachi drives do not utilize AP 2.5. All other drives are considered to be detectable by Microsoft (YMMV). Make sure all rips are ABGX verified, contain SSv2, and patched AP2.5 (where needed). XGD3 must currently be burned on new drive with PC Burner Max firmware for 100% rip. All modded consoles can be potentially unsafe for use on XBOX live."
Originally posted by leerage: I had to do quite a bit of reading on this before making my purchase. I purchased a brand new Jasper MFR date 6-11-2009. It had the 2.0.7367.0 dash with a CB 6723, so it was exploitable. Where you need to find out additional info is the TEAM and LOT number. Right off the top of my head I can't remember my LOT number but the TEAM was FDOU. I had read a post with someone purchasing a Jasper brand new made on 5-29-2009 thinking it was exploitable. It had the 2.0.7367.0 dash but it's CB was 6750... already patched. The TEAM was CSON.
So I'm pretty confident to say if you find a Jasper made before 6-18-2009 and the TEAM is FDOU, you should have an exploitable CB. This info is all U.S.A. based. I'm sure TEAM, LOT numbers, and the "cut-off" date differ else where.
From UK - My Jasper was by FDOU, cant remember date but was early-mid 2009. Was taggable.
