ABGX360 V1.0.2 Download
Onofre Alamillo
Sorry for the downtime over the past couple of days but the site has now been moved to a new host. Thanks to our friends at Team Xecuter for graciously providing the bandwidth from now on!
However, the domain abgx360.net has not been pointed to the new host yet. To get the abgx360 app working again you will need to download this abgx360.ini file and extract it from the zip archive to the folder directly above your StealthFiles folder. To find out where your StealthFiles folder is, open abgx360 GUI v1.0.2 or later and press Ctrl+F (and click yes to have it opened for you). Then go one folder up to where you see the abgx360.dat file and put that abgx360.ini file you extracted in there right next to it.
When we can get in contact with the owner of the domain and point it to this new host, and you are viewing this text on , you should delete that .ini file in case the IP address of this server changes (although it probably won't change for a long time).
Sorry for the downtime over the past couple of weeks, but the site has now been moved to a new server. Our many thanks to our friends at Team-Xecuter for graciously providing the bandwidth from now on!
However, our original first domain abgx360.net has been completely different site for a few years now. As such to get the abgx360 app working again you will need to download this abgx360.ini file and extract it from the zip archive to the folder directly above your StealthFiles folder. To find out where your StealthFiles folder is, open abgx360 GUI v1.0.6 and press Ctrl+F (and click yes to have it opened for you). Then go one folder up to where you see the abgx360.dat file and put that abgx360.ini file you extracted in there right next to it.
Note: The way video is checked/fixed is now a little different for both XGD2 and XGD3. The previous way was to check/fix both L0 video and L1 video off of L0, and then to check/fix "SplitVid" (L1 video on L1) afterwards by comparing it to L1 video on L0. Since XGD3 has no room for L1 video on L0, and to keep things consistent, video will now always be checked/fixed according to L0 on L0 and L1 on L1, and the "SplitVid" check is now gone (nominally). The only effective difference is that L1 video on L0 is no longer checked, but this is not a problem... it's not even supposed to be there and it's not visible to the host console when using a "safe" custom firmware. You can rest assured that only old and unsafe custom firmwares will read L1 video from L0; newer ones will read it properly from L1 (this is necessary in order to replicate the read/seek performance of an original disc).
There is also a big annoying yellow message if you have "Check/Fix Video padding" enabled and you check an XGD2 game with L1 video on L0 (or any data in that area). To make the message go away you will need to either add command line option "--pL0" to confirm that you want to blank it out (XGD2 ISOs without L1 video on L0 will appear to have bad video data when checked with older versions of abgx360), or you can simply disable "Check/Fix Video padding", as it still makes no difference in terms of stealth... this option only exists as a way to make sure ISOs are "clean", with no extra data in areas that aren't CRC checked. Note that this version of abgx360 doesn't care about L1 video on L0... it will pad L0 video with zeroes whenever video is autofixed or manually patched.
Any of these failures will probably flag your console for a ban in the next banwave. As always you should be very wary of system updates and carefully follow the news here as well as on c4evaspeaks.com, team-xecuter.com and xbox-scene.com.
DAE.bin is being silently updated through Xbox Live with an additional challenge table! This happens on the current public dashboard version 2.0.13604.0 and there is no confirmation dialog or any known means to prevent it besides disconnecting your console from the internet.
If your DAE.bin has already been silently updated, AP25 backups that are patched with current AP25 replay data will fail the normal AP25 challenges outright! Note that all XGD3 games use AP25.
The Fall 2011 preview dashboard version 2.0.14692.0 is now rolling out. If you are in the preview and accept the update, it will now actively use the additional DAE challenge table and AP25 backups that are patched with current AP25 replay data will fail the normal AP25 challenges outright!
All AP25 replay data in the database has been updated as of 2011-06-14. See Defosho's AP25 games list and AP25 FAQ for details. Note that this replay data is meant for dashboard version 2.0.13146.0 and will not work if you haven't updated. For information and recommendations about the update, read Defosho's System Update FAQ and stefanou's FAQ 1 2 3.
Sorry for the long release interval but v1.1.0 is taking much longer than expected and hopefully this interim update will address the main concern people were having, even though v1.0.2 was designed to support new PFI/Video waves as long as the game was verified, v1.0.3 gets rid of the yellow text and also allows you to check SplitVid on newer games that haven't been verified yet. It does not, however, add automatic searching/patching of SS v2 files. That's something that isn't even finished in v1.1.0 yet, and there's still the matter of SS v3 to deal with.
Note 2: XBL safety is very uncertain at the moment... The latest LT firmware for Samsung drives is considered by many to be fairly safe (since the TS-H943A ms25/ms28 original firmware doesn't support AP 2.5) but owners of other drives need to be very careful and upgrade to LT+ when it becomes available.
Note 3: Just because the source code for abgx360 is made available, it does not imply a right to make changes and/or distribute source or binaries. Permission to do so is granted on a case-by-case basis. This is necessary to prevent people from distributing buggy code or binaries which may adversely affect the online database, or distributing potentially virus infected binaries on sites that appear official but are not. If you only need to make a small change to enable compilation on your system, permission is hereby granted to do so, as long as it does not affect the way abgx360 communicates with its online database in any way.
Looks like we were wrong in assuming that iXtreme v1.51 was fully compatible with 4th Wave PFI/Video. Turns out that only Hitachi iXtreme v1.51 will boot 4th Wave backups, and BenQ/LiteOn/Samsung iXtreme v1.51 will NOT boot 4th Wave. It would have been fully compatible if only the Video data had changed but not with the change in PFI (capacity). So currently the only safe option for booting 4th Wave backups on a BenQ/LiteOn/Samsung drive is to use iXtreme v1.6 and the one shot boot disc.
A regular, retail Xbox 360 disk is split into several sections or "partitions". One of these partitions is known as the "video partition". Before March 2009, this partition simply contained a video that would play if you inserted the disk into a regular DVD player, the video would basically tell you that you were an idiot and need to put it into an Xbox 360 to play it.
One of the ways Microsoft can detect you being a dirty, filthy pirate is to scan this video to make sure it matches with what is supposed to be on the disk, so to protect you, the firmware itself does a quick checksum of it and if it doesn't match with known video data, it wont boot. Every now and then, this video changed, with each change being called a "wave".
Normally, system updates (dashboard updates) are stored on a different part of the disk, taking up about 8Mb of space, however in November 2008 Microsoft launched the "NXE", a completely new Dashboard for the system. Along with the new dash came Avatars, making the whole update substantially larger (somewhere in the region of 130MB). This meant the update wouldn't fit on the disk in the same partition that previous updates were located and so instead the update was placed within the video partition. This was known as "wave 3" and hit around March 2009.
As Microsoft now distributes new Dashboard updates in the same partition, each time the 360 gets a software update, we will see a new "wave" a few months later. There was a Dashboard update in August 2009 and that is now being distributed with the latest games. This is known as Wave4. Its identical to Wave3, except the video partition now contains the August 09 Dash update. The first known game to have this was Cars Race-o-rama.
Now, its important to remember that iXtreme was designed to PROTECT you and part of that protection is the "video partition" check. When this video partition changes, the firmware doesn't know if its just a new "wave" or if its a bad rip and thus opts to not boot it.
When wave 3 hit, iXtreme 1.51 was quickly released to tackle the problem. This was a temporary fix only, the firmware simply does not do the video partition check and thus boots was supposed to boot ANY wave, up to wave 4 and beyond.
However, this in itself is "unsafe". If the disk is fine, then you'll be fine, but if the video partition is in any way corrupt, iXtreme 1.51 will still boot it and thus you could be detected by Microsoft and banned. This also is not helped by the fact that some impatient, idiotic people decided to "patch" Wave3 games with Wave2 data in order to get iXtreme 1.5 or below to boot it. This is a great way to get yourself banned and thus iXtreme 1.6 was created.
ix1.6 will only boot games that have the CORRECT video partition, up to and including wave 3. This means that if you have a Wave 3 game that was patched with a Wave 2 video partition (aka a great big bullseye for Microsoft to target), iXtreme 1.6 will not boot it but ix1.51 will.
IF you are on iXtreme 1.51 (Hitachi), then ANY wave will boot fine, including Wave4 however you must be EXTRA careful as you are not protected against corrupt or incorrect video partitions. This is one of the many reasons to always use abgx360. If a game is fully verified, playing it on iXtreme 1.51 is just as safe as playing it on iXtreme 1.6 - this includes Wave4 games.
b1e95dc632