Topic: Team Jungle Tweets About The iXtreme LT Firmware (Read 7576 times)

xbox360sexual · « **Reply #120 on:** November 24, 2009, 10:36:00 AM »

An excellent explanation mate, thank you very much

newboxflash · « **Reply #121 on:** November 24, 2009, 11:06:00 AM »

QUOTE(Deihmos @ Nov 23 2009, 09:12 PM)

I can't wait for people to be banned because some guy said the firmware is undetectable like most of the previous firmwares.

cant see you making many friends with posts like this any firmware is installed at users risk a ban is always on the cards the guy give us his time and effort i really hope you dont even try installing the software to gain anything from it, what a c0ckhead you are

ive got 2 banned consoles and 90 games my maths says im ahead by a few grand so all is good this side of the pond (IMG:style_emoticons/default/cool.gif)

caster420 · « **Reply #122 on:** November 24, 2009, 11:40:00 AM »

QUOTE(Obveron @ Nov 24 2009, 10:36 AM)

Original disc: L1 data is in one place - L1

That is incorrect. An original Xbox360 disc has a video partition on both L0 and L1. Splitvid emulates this as much as possible. Original Xtreme fw was only capable of reading from L0 (reasoning and correction explained in Post #2), hence the original format. c4e has since corrected this.

Reference:

Post 1

another explanation of whats going on...

Post 2

Caster.

This post has been edited by caster420: Nov 24 2009, 07:58 PM

vinnycuz · « **Reply #123 on:** November 24, 2009, 11:50:00 AM »

QUOTE(Obveron @ Nov 24 2009, 11:59 AM)

Well it began in 2006 with old xtreme fw reading L1 from L0 due to technical difficulties making proper images and having the FW read it properly. Eventually that difficulty was overcome, but the xtreme FW of the day still expected L1 to be in L0 so ripping methods remained the same.

When ixtreme came out in 2007 alot of people expected this to change and L1 data to be read from L1, but this would cause everyone's xtreme (non splitvid rips) to not work.
I think c4eva and the team decided to continue to search for L1 data on L0 to stay compatible with the old rips. It was a compromise for compatibilty with the assumption that there was no technical way for MS to detect the difference.

Everyone was told that the FW would hide that the L1 data is being read from L0, and that MS would not be able to tell the difference - obviously that is no longer true.
(many people screamed about proper 1:1 support back then, saying it was the only safe way to do it, but alas it didn't happen)

So back in 2007, people started adding L1 data to the proper L1 spot, but they needed to also put it in the L0 spot to stay compatible with ixtreme. The belief was that if a new fw came out that needed the L1 data in the proper L1 spot, the disks will still be compatible. Problem is, the disks were still not 1:1, it had L1 in two spots, making total disc size too big. This is the current practiced splitvid method, L1 in two spots.

Still, we were told that the FW would ignore the extra video data on L1, meaning the extra data would be ignored and everything still appear legit to MS. Opinions divided on that issue, some insisting on making these types of splitvid rips, others sticking with the old non-splitvid method (most didn't know the diff).
Since neither were really 1:1, neither opinions were wrong, noone could say which was best.
We will have to see if the current splitvid method will be compatible and "safe" with the ixtreme LT. It is quite possible that we need to change the splitvid method to a 1:1 format. Or perhaps the new LT firmware will effectively hide the extra video partition. We need to wait to hear more from the team.

I know it's hard to follow, hopefully some of you can make sense of my brief splitvid history lesson.

If M$ detects the file size, a file size spoof could be added to the code this way every disk is the correct size. Or maybe ABGX can inject the file size to spoof it, hmmm...

caster420 · « **Reply #124 on:** November 24, 2009, 12:16:00 PM »

Meant to post that if you read through post 2, what you are discussing with L1 video on L0 is also discussed, outlines how XBC creates splitvid currently with only L1 on L1 and how the firmware was reporting L1 from L0 but was fixed.

Regards,
Caster.

This post has been edited by caster420: Nov 24 2009, 08:16 PM

CYRAX · « **Reply #125 on:** November 24, 2009, 12:46:00 PM »

Thanks caster. You the man.

WBones · « **Reply #126 on:** November 24, 2009, 12:48:00 PM »

QUOTE(Mexdog19 @ Nov 24 2009, 09:36 AM)

I greatly appreciate what C4E and others are doing but I don't understand why everyone is posting this stuff on Twitter or just putting this on blast so M$ can read what's going on. Do they not think M$ is planning something to counter attack this some how since people can't keep their mouth shut about it. It's just stupid to post something like this on a social network site. M$ can find anything and read about it just like us.

Yep. Because if we just kept it to a post on these forums we all know that MS is not able to make an account on here and read.... right..... ?

MS knows whats going on. Keeping it off twitter wont stop that. We dont have some super secret undergound network and if we did then none of this stuff would be free to do.

Its a good thing nobody at MS is able to run Xbins either because then we would be screwed!.....

Redline99 · « **Reply #127 on:** November 24, 2009, 12:58:00 PM »

Obveron, what are you talking about? Your explanation of splitvid is incorrect. Splitvid is created according to the PFI, it is not just placed in the locations for the sake of putting it somewhere. It is a recreation on how the PFI is telling us to make the data. The locked partition (video) is not "all on L1" it is on both L0 and L1 exactly as splitvid recreates. The older Xtreme firmware and the iso without splitvid used the L0 data correctly, the problem is that the L1 data was in the wrong spot. If the rules of the PFI were followed (as they were) the L1 part of the partition would be non visible, c4eva corrected the firmware to address this so that those types of iso's could be used. We currently create a hybrid that puts the L1 data in the "bad spot on L0" and in the correct location on L1 (the SplitVid).

MyDogAteIt · « **Reply #128 on:** November 24, 2009, 01:24:00 PM »

All this talk of banned xbox live 360's. LET'S THINK OUT OF THE BOX - instead of trying to find a work around to get back on live. Why not figure out a way to just use the internet capabilities of the 360 hardware and just connect to the web and start our OWN banned community where all banned consoles could easily access and play one another directly WITHOUT MICROTHUGS? What do we need?

Obveron · « **Reply #129 on:** November 24, 2009, 01:26:00 PM »

QUOTE(caster420 @ Nov 24 2009, 07:40 PM)

That is incorrect. An original Xbox360 disc has a video partition on both L0 and L1. Splitvid emulates this as much as possible. Original Xtreme fw was only capable of reading from L0 (reasoning and correction explained in Post #2), hence the original format. c4e has since corrected this.

Reference:

Post 1

another explanation of whats going on...

Post 2
Caster.

Woah, i didnt say there wasn't a L0 video partition! What i said is that the L1 video partition was found on L1! Obviously the L0 video partition is on L0 and has stayed on L0, I was only referring to the location of the L1 video partition. If you read again what i said i never even talked about the L0 video partition. I really can't see how you guys can conclude i don't know about L0 video. I never intended to offer a complete explanation of splitvid. Ofcourse, if i had intended to explain it all i would of talked about L0 video. My intent was to point out the locations of L1 video, and quantify current the splitvid method with respect to that partition alone. Nothing I said was incorrect, just incomplete.

This post has been edited by Obveron: Nov 24 2009, 09:36 PM

Midnight Tboy · « **Reply #130 on:** November 24, 2009, 01:30:00 PM »

QUOTE(Redline99 @ Nov 24 2009, 09:58 PM)

Obveron, what are you talking about? Your explanation of splitvid is incorrect. Splitvid is created according to the PFI, it is not just placed in the locations for the sake of putting it somewhere. It is a recreation on how the PFI is telling us to make the data. The locked partition (video) is not "all on L1" it is on both L0 and L1 exactly as splitvid recreates. The older Xtreme firmware and the iso without splitvid used the L0 data correctly, the problem is that the L1 data was in the wrong spot. If the rules of the PFI were followed (as they were) the L1 part of the partition would be non visible, c4eva corrected the firmware to address this so that those types of iso's could be used. We currently create a hybrid that puts the L1 data in the "bad spot on L0" and in the correct location on L1 (the SplitVid).

lol I keep "understanding" and them becoming more confused afterwards (IMG:style_emoticons/default/smile.gif)

So.....if we "currently" create a hybrid? Does that mean the "hybrid" is created when in ABGX the option to insert splitvid is selected.....or when it is not/ignored?

Obveron · « **Reply #131 on:** November 24, 2009, 01:39:00 PM »

QUOTE(Redline99 @ Nov 24 2009, 08:58 PM)

We currently create a hybrid that puts the L1 data in the "bad spot on L0" and in the correct location on L1 (the SplitVid).

This is exactly what i was describing.... pointing out that since L1 is in two spots, it's not 1:1. That's it.

dbldown768 · « **Reply #132 on:** November 24, 2009, 01:41:00 PM »

I know nothing.....

This post has been edited by dbldown768: Nov 24 2009, 09:43 PM

AnimeCommander · « **Reply #133 on:** November 24, 2009, 01:51:00 PM »

Skimmed this thread and am disappointed. All this effort to stay on Live and hide. Forget it. I just want a firmware that will play the games. I'm tired of having to recheck everything I've done to make some new firmware happy. People were content to keep their Xbox offline when modded, why can't you do the same with the dang 360?

Obveron · « **Reply #134 on:** November 24, 2009, 02:12:00 PM »

Ok i think the big issue with my posts I was sometimes using the quick term L1 or L1 data to mean "L1 video partition".
Quick comments like "read L1 from L0" can be confusing. Its just an easy way to communicate and experts like redline and caster do the same thing.
I also never mentioned that original disks have the video partition split across two layers. Which doesn't mean I'm unaware of that, but some have obviously interpreted it as such.

I wanted to only talk about the location of the L1 video partition. I only typed it in a short period of time (and used some sloppy technical language), hoping to enlighten a few noobs about a little bit of the issues.
It was never meant to be a 100% thorough explanation of splitvid, such a thing would require very deliberate and accurate terms which i didn't use.

If I am spreading misinformation, I'm very sorry.
I'm pretty sure i didn't say anything grossly off the mark (as i am accused of), merely my technical language and lack of describing the complete picture makes for easy confusion. For that i'm sorry.
No experts were jumping in to describe any of it, and I felt like making a few points to help out.

This post has been edited by Obveron: Nov 24 2009, 10:20 PM

Author Topic: Team Jungle Tweets About The iXtreme LT Firmware (Read 7576 times)