abgx360 v1.0.7 [Hadzz Fork] released!

Changes affecting Windows and Linux/BSD:
- No more abgx360.ini needed for online functions! Internal URLs have been updated to http://abgx360.hadzz.com
- Video CRC is recalculated with the new PFI in autofix, meaning "redump style" ISOs no longer require manual patching or having the video ISO locally.

If you're on Mac, or still want to use the official v1.0.6, the abgx360.ini below will still work.


abgx360 has a new (unofficial) home!

After many years since its first release in 2009, abgx360's official domains have come and gone. In late 2020, abgx360.cc went down, taking with it thousands of stealth files, patches and checksum data. But thanks to the help of the community over at r/360hacks, the database was rebuilt in early 2021. Thank you to everyone who helped recover files that otherwise would've been lost to time!

To get the app online again, download the updated abgx360.ini and extract it from the zip 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.

There is also a new fork called abgx360 Reloaded started by the user Bakasura, with many GUI updates and more. We are working to integrate an updated CLI for future releases.

IMPORTANT: I am not in any way affiliated with the original developer. The intention of this site is to provide a relacement database and useful code changes. All credit goes to Seacrest for his incredible hard work and dedication over the years.

- Hadzz


abgx360 v1.0.6 released!

Changes affecting all platforms:

- XGD3 support.
- Replaced AP25 replay sector support with support for topology data (for consoles which do AP25 checks -- make sure you have LT+ v3.0 or later).
- Added "Min Kernel Required" (to boot the game) when checking an XEX.
- Added improvements to AutoUpload (used by uploaders) including extended C/R for SS (using the original disc) to make sure files uploaded to the database have very accurate angle measurements.
- Added optional command line argument "--speed" for setting drive speed when checking a burned DVD. Example: "--speed 12" will attempt to set the drive speed to 12x. You can try to set any speed you like, but setting a speed higher than what your media supports may cause read errors if the drive's firmware doesn't govern it. "--speed 0" will set the drive's default speed.
- Added optional command line argument "--showsstable" for when you want to see the SS C/R data but you still prefer medium or low verbosity. The SS C/R table has also been updated with "Mod?" being split into "Tol" (response tolerance) for the CCRT entry and "Mod" (response modifier) for the drive entry, also "Pad?" has been renamed to "Typ" (type). Thanks Redline99!
- Added vendor specific additional info and bus type when displaying optical drive names (bus type displayed on Windows only).
- Updated the list of optical drive sense code errors.
- Updated the game ratings definitions.
- Fixed a bug which negated the ability to recover from a write error when rebuilding an ISO using the low disk space method. It's unlikely that a write error would be recovered on subsequent retries, but at least now it will write the data in the correct place if it does recover.
- Fixed a bug which caused "Unknown Media: 0x00000000" to be displayed if the "Secure Virtual Optical Device" media flag was set and the "XGD2 Media Only" image flag was not set (The "XGD2 Media Only" flag has also been renamed to "Original Media Only" in abgx360 since they are using the same flag for XGD3).
- The archaic caution message about angle 359 was removed, but you are still able to "fix" it if you still have iXtreme < v1.4 (really old and not suitable for XBL anyway).
- Ability to "extract entire video partition (253 MB)" was removed; this doesn't make sense for XGD3 and isn't even very useful for XGD2 since it was just including a bunch of padding data that isn't even part of the real video partition... it was only needed for very old methods of concatenating with stealth files and a game partition to make a working backup.

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.

Sorry if the command line options are annoying (you can add them under the "Misc" tab of the GUI), but you can be sure that an improved v1.1.0 GUI is in the works...

Note: The GUI has not been changed and will still display version 1.0.2, don't worry about it as long as the CLI app displays v1.0.6

Show Old News