Topic: Free60 JTAG/SMC XeLL Hack for Jasper-16mb Motherboards (Read 828 times)

Pedroshin · « **Reply #30 on:** November 09, 2009, 10:09:00 AM »

QUOTE(NoseBreaker @ Nov 9 2009, 02:58 PM)

I'm just angry at myself, but with a quick search all I found was that Cars-O-Rama was the first wave 4 with 8498 NXE update, no mention of JTAG.

While WPA2 Live update said "Note: As always, update at own risk and don't do it if u still wanna run the JTAG Hack."

Try this "Removing System Updates".

Hoescout · « **Reply #31 on:** November 09, 2009, 12:59:00 PM »

GOOD news is that the new MW2 xbox 250 gb bundle has Kernel 2.0.7363.0 on it so its good to go for jtag.

modslave · « **Reply #32 on:** November 09, 2009, 01:00:00 PM »

I am WELL happy to see this release and excited that hopefully the 256 and 512 might get released someday too (as mine is 256).

Just a pity that the bann thread is nearly 50 pages and this thread you can count on one hand

I bet everyone wish thay had a moddable console now instead of a banned one (I now have both

) - Dam you MS

phiberoptix · « **Reply #33 on:** November 09, 2009, 01:17:00 PM »

I am one of those (few?) that stopped connecting to live after reading the news here about the jtag exploit.

Good things comes to those who wait, i hope. Now my jasper is finally exploitable

Artlover · « **Reply #34 on:** November 09, 2009, 01:36:00 PM »

QUOTE(Pedroshin @ Nov 9 2009, 12:09 PM)

Try this "Removing System Updates".

This has been floating around for nearly a year (atleast as far back as Jan'09 on teamxbox, which is the earliest reference to this I could find).

Anywho, the problem with this is that it's not going to do what people think it will.

#1: Many system updates trigger eFuses to prevent downgrading. How does this get around that? I know eFuses can be reset, but I doubt MS was dumb enough to embed the necessary JTAG code into the console to allow for that. If they were, it's a shame no one has discovered it yet, because that would solve a whole lot of problems for people.

#2: It could only possibly remove minor updates not major ones, and not on all consoles.

2a: If we assume system updates are simply add-ons to a base core, then it would seem only older xboxen with the smaller NAND's that required HDD/MemCard to store the rest of the system could do this and only back as far as the existing base core that is currently installed on the NAND. Newer systems like the Jaspers with the larger NAND's that store the whole system there I don't see as being able to do this at all.

2b: If we assume system updates are complete (as in actually patching the base core code itself), then the ability to remove said updates would mean that the system is creating backups of previous system versions. Again, this limits it to consoles with HDD's/MemCards since the NAND doesn't have the storage to hold any such backups and would still be subject to the eFuse limitations created by #1.

In other words, this is not going to revert your console back to pre August 09 if you already updated. Seriously, since this is old news, one would think the freeBoot and JTAG Hack guys (and all the other hackers) would have mentioned this as an option for people who already installed the August 09 update if this worked and did anything useful.

Sarek · « **Reply #35 on:** November 09, 2009, 05:00:00 PM »

QUOTE(phiberoptix @ Nov 9 2009, 09:17 PM)

I am one of those (few?) that stopped connecting to live after reading the news here about the jtag exploit.

Good things comes to those who wait, i hope. Now my jasper is finally exploitable

I wanted to hold out, but I was in the middle of a couple of games I wanted to play, and couldn't wait. Fortunately, I found one brand new Jasper Arcade unit at a Meijer store with a Feb 2009 manufacture date (I assume it's still safe) and bought another on Ebay for $95 which includes 2 Wireless controllers and a game, and had never been on Live.

I second the earlier comment about the shame of their being more attention on the bans than this. I've not modded my units at all yet, and don't plan to in order to pirate games.

blipidy · « **Reply #36 on:** November 09, 2009, 09:55:00 PM »

i just bought a used jan 09 console today that i had planned on using for live as a backup incase anything happens to my current console. i havent logged that one into live yet today, but last night i was still playing on live w/ no issues.

i booted the console i got today up and saw that it was still on the 7371 dashboard, so now im torn on what to do. it is a jasper arcade unit. i dont believe that the console has ever been connected to live either. my original intention was to use it on live, but seeing as it has the pre summer 09 dash, im thinking its going to sit on a shelf while i follow up on what is happening with xell and jtag. i think im going to have to go and look for another console now to use as a backup lol

Rad0x · « **Reply #37 on:** November 10, 2009, 05:00:00 AM »

QUOTE(Hoescout @ Nov 9 2009, 09:59 PM)

GOOD news is that the new MW2 xbox 250 gb bundle has Kernel 2.0.7363.0 on it so its good to go for jtag.

But does it also have the old 1BL?

infidelity · « **Reply #38 on:** November 10, 2009, 07:40:00 AM »

I'm starting to get really confused on what type of Jasper I have.

I bought a brand new arcade 360 from walmart, (no HDD, just a controler, and some game I can't remember off the top of my head) 2 days after the first reports of the jtag hack to enable homebrew back in August.

First off, I know for a fact that my 360 is a Jasper. I know this from doing the power voltage check near the barcode on the back of the 360. My numbers matched what was described as to having a Jasper.

Now, as for telling if I have 16mb, 256mb, or 512mb, I have no clue.

And here's another confusing part. I read online that the Jasper has an internal MU (memory unit). I read that you have to goto Settings, and Memory, and it should show up. So, with no HDD, and no external memory card inserted, I went into Settings, and Memory, and nothing was there. There was no icon of the 360 machine, with any description or anyhting. The screen was just blank......

So, do I have a 16mb, 256mb, or 512mb??

Thanks for the help.

-infidelity

p.s. my dashboard is 2.0.7357

Poopchute · « **Reply #39 on:** February 03, 2020, 10:43:00 AM »

Someone correct me if Im wrong but...cant a person do this JTAG hack while they have a 7371 or lower kernel...Then Upgrade to a 8xxx kernel and then be able to play wave 4 games? Its just if you upgrade before the hack then youre screwed...

HotKnife420 · « **Reply #40 on:** November 10, 2009, 11:46:00 AM »

QUOTE(modslave @ Nov 9 2009, 09:00 PM)

I am WELL happy to see this release and excited that hopefully the 256 and 512 might get released someday too (as mine is 256).

Just a pity that the bann thread is nearly 50 pages and this thread you can count on one hand

I bet everyone wish thay had a moddable console now instead of a banned one (I now have both

) - Dam you MS

They're up on xbins, now.

QUOTE(infidelity @ Nov 10 2009, 03:40 PM)

I'm starting to get really confused on what type of Jasper I have.

I bought a brand new arcade 360 from walmart, (no HDD, just a controler, and some game I can't remember off the top of my head) 2 days after the first reports of the jtag hack to enable homebrew back in August.

First off, I know for a fact that my 360 is a Jasper. I know this from doing the power voltage check near the barcode on the back of the 360. My numbers matched what was described as to having a Jasper.

Now, as for telling if I have 16mb, 256mb, or 512mb, I have no clue.

And here's another confusing part. I read online that the Jasper has an internal MU (memory unit). I read that you have to goto Settings, and Memory, and it should show up. So, with no HDD, and no external memory card inserted, I went into Settings, and Memory, and nothing was there. There was no icon of the 360 machine, with any description or anyhting. The screen was just blank......

So, do I have a 16mb, 256mb, or 512mb??

Thanks for the help.

-infidelity

p.s. my dashboard is 2.0.7357

You have a 16MB Jasper.

QUOTE(Poopchute @ Nov 10 2009, 06:43 PM)

Someone correct me if Im wrong but...cant a person do this JTAG hack while they have a 7371 or lower kernel...Then Upgrade to a 8xxx kernel and then be able to play wave 4 games? Its just if you upgrade before the hack then youre screwed...

WRONG! Updating to the 8x dash will also change the bootloader code to one that doesn't have a vulnerability (at least, that we know of).

infidelity · « **Reply #41 on:** November 10, 2009, 05:23:00 PM »

where are the installation diagrams for the jasper jtag? can't find them anywhere online

Poopchute · « **Reply #42 on:** November 10, 2009, 10:51:00 PM »

Can anyone confirm that its really out for the 256 and 512 on xbins? Is that for real?

HotKnife420 · « **Reply #43 on:** November 11, 2009, 07:36:00 AM »

QUOTE(infidelity @ Nov 11 2009, 01:23 AM)

where are the installation diagrams for the jasper jtag? can't find them anywhere online

JTAG wiring for reading/writing nand is the same on all board revisions.

Wiring for Xell to run is the same on all non-xenon consoles (same wiring as a falcon or zephyr)

lenselijertje · « **Reply #44 on:** November 11, 2009, 08:47:00 AM »

cygnos doesnt work with 256/512mb jasper consoles (yet), but they are working on it

i'm building a jtag flasher with usb, because reading a 512mb nand file using lpt port would take too long.
I read with usb it takes only about 1 hour

Author Topic: Free60 JTAG/SMC XeLL Hack for Jasper-16mb Motherboards (Read 828 times)