abgx360 v1.0.6 Posted by XanTium | January 3 15:51 EST | News Category: Xbox360

A new version of abgx360 has been released. What's new/fixed (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 Official Site: http://abgx360.net Download: here

Very Nice. Nice work Seacrest.

!!!! WOOT !!!!! Thank's

Always so late on news.

Next..

Always so late on trying to be cool...

Next...

Glad its now here Thank you and happy new year Seacrest

At least they put the news out dick head,what have YOU done for the scene again exactly?.
If you knew how the scene worked you would know why stuff is sometimes late .btw you get this stuff for free and do not even give one word of thank .

OT-thanks to all involved great work as always ..

This could have easily been fixed by hex editing the binary (assuming the source code is not available). It is just confusing people and there is no reason not to adjust the GUI revision, even when there are no changes.

Great work. Thanks guys

awesome! thanks for the update version. always feel a little better running my backups through abgx360 to make sure I didn't mess them up before burning

Is this the patching tool ? Like it was for ap25

Yes this will patch the ISO.

guys what are the set ups i have to do do i still add split vids if it does nto exists and so on let me know asap plz

finally been waiting for this, auto patching , didn't want to do the the other way.

A very big thank you to you guys for all the hard work you've done, you guys are superb.
Just cant thank you enough. Especially for working on this over the holiday period instead of spending more time with the family

As for the silly command line options...if someone has a problem with them, they shouldn't be using this program in the first place!

Does this version update automatically to SSV2 as standard now?

WOO! Thanks folks!

I assume this means you don't need to patch anything through XBC now as ABGX should do it instead?

Correct , This checks then patches the Topology Data so no need to inject it with XBC any longer.

If this is something that confuses you or anyone else for that matter then you should just toss your Pc out the window cause that new fangled mouse thingy is just way to hard to explain!

All of these changes and they still won't update the GUI rev number.

Should I be worried that my XBC rips aren't getting the thumbs up in ABGX? One rip in particular has Video CRC and V0 CRC that does not match, two copies ripped from different drives. Odd thing is, the ISOs passed when I ran them through, but the burned copies did not?! Can someone help?

do we still have to put autofix on level 3 like we used to do before or we have to use different settings

I don't think the answer to your inquiry is that hard....

I'm not worried about a yellow DMI here and there, I'm just befuddled as to why two different rips of the same original pass Video CRC as ISOs yet fail as DVDs

Update: A third copy, ISO ran through ABGX first, also passed ABGX as a DVD unlike the other two. Could my boxes possibly be safe since they only had the "vid crc not match" disc in them a couple times for one day?

The game-specific patches that were floating around seem to be re-patched, but not the generic one.

SSv2 is the standard for games ripped with 0800 firmware...that said, since XGD3 games must be ripped using 0800, they could only be SSv2.

If your autism is stopping you from using abgx360 just because the GUI revision number hasn't changed then you need to go back to your doctor.

Always so late on being a tool.

Next..

Thank you so much, Seacrest!


abgx360 has always been a command-line program that now is v1.0.6. The Graphical User Interface (GUI) that helps you use this program is still v1.0.2 because there's nothing new in it and has nothing to do with the main program. Is this so hard for you to understand?

hi all does this mean i dont have to rip my originals now will the iso ive recieved elsewhere by as safe once run through this program ??

my lite on drive laser is going i think and i dont want bad 2.5 angles

thanks

Tested on a backup w/ XBC patched topology data and it passed.
Tested this on a backup w/o topology data and it failed (writes disabled).
Tested this on a backup w/o topology data, auto-fixed/patched and passed (writes enabled).

Ran an MD5 on the XBC-patched vs. ABGX 1.0.6-patched and the hash was identical.

Very sweet

Nice surprise. Thanks for the hard work. Going to check it out soon.


edit: Patches topology data automatically just fine. Just like before, set it to Level 3.

nice

Is there any recommended settings we should use?

so no more imgburn ? am all confused i patched game with abgx (COD3) layer break 2133520 can i copy it don't wanna watse a dvd thanks. same thing for nhl12 as well wih abgx i have ixtreme 3.0 loaded

I second this.

The old gui and nw recommeneded advice makes things confusing to your regular person.

Any chance someone could give details / screenshots of the ideal settings?

WOuld be very much appreciated.

Thanks

Awesome release.

Just to add that if your burned DVD's are failing to verify through this then try scanning them using the iHAS iXtreme burner and not a different DVD drive, since for one the slim DVD burner in my laptop seems incapable of reading these discs properly, reporting an incorrect layerbreak and video partition size but through the iHAS drive everything works perfectly.

ummm if you want to use your patched iso, you'll beed to burn it to use it? in which case you need imgburn to burn it?

I have a some XGD3 ISOs that burned correctly, work on any LT 2.0 system, but when checking with ABGX, I get:
"Game partition CRC does not match the verified ini!"

The stealth check passes though. I checked abgx.net like it says too, but looking up the game database isn't a solution. Do we just wait for new rips?

Found this on team-xecuters forums. Its a step by step guide very helpful.
Thanks Xecuter Admin..


abgx360 setup

In the guide it states make sure you get Verbatim disks made in Singapore. How can you tell where the disks are made? Especially with on-line orders. I have been getting mine from NewEgg and have not had a problem. I have been using a Lite-on burner with cfr.

Thanks for all the hard work on this!

excellent work guys downloaded yesterday and working perfectly thanks guys!!

Like i said, set it to Level 3 and it will take care of the rest.

Shame it still doesn't automatically choose ssv2 over ssv1 for xgd2 games

Still, awesome release, thank you

I'm inclined to agree(except about the GUI revision changes.. I think ? 'No reason not to adjust if there is no changes'?.. sorry but that statement gave me a brain-sprain ;-) , the GUI is the front-end that drives the new CLI, it should be updated to support the various features (such as drive speed) and reflect as such,(yes I know you can add switches in that box if u want to but..)
They release the source (AFAIK) so ppl can do it themsleves, If anyone is keen to have a go and wants some support then pls start a new thread and post the link here(and I will do what I can to help)
As I would be keen to see some more features integrated into the GUI such as enable/disabale Topo patching and autofix levels based on topo deviation... Topo bounds testing etc..Topo SHA-1 matching also for quick mode? And the list goes on.. But just getting started on the GUI I'm sure would be a big help to those who work hard to put-out the CLI, If anyone has been working on topo analysis APP (betting it would be CLI also) perhaps could be integrated into the GUI's scripting perhaps?

Interesting, I'm inclined to say you have one of the usual issues with ripping, Your box should be fine unless it's some sort of new flagging system.. not likely though, we're a bit past deliberate CRC errors as AP (I would think...)





Agreed, I thought there was a checkbox for it somewhere... But it's been a while since I've had use for it..

I would mostly like to use it to integrate my AP2.5 sectors, Or maybe for checking for CRC errors... Plus it's nice to know how my local rips compare to the 'median' files.. (I still find it hard to believe they did several rips of my local region's titles for the median files, if u get my drift, that might be fine today... But I really want the piece of mind that comes from doing it yourself... wherever possible) In the old days, aftr I checked CRC's I didn't mind a few yellow miss-matches that I knew were due to regional (etc..) differences I have yet to have an issue (AFIK) with a topo I've done myself (Mind,you I'm carefull about the drive I'm using, how it's used , power-source, stability, not bumping it, etc.. Most ppl I guess wouldn't be able to do all that...)


EDIT: MY speed-reading sux, but on the second pass-thru I noticed it mentions that 'a new GUI is in the works' If anyone knows any of the switches to measure topo data pls let me/us know I'm still up fer helping-out with the GUI BTW

well

I ran an image of need for speed the run through the new agbx and at first i got a message in red saying there was 12 sectors of topology data missing which it then proceeded to patch succesfully. DMI passed and CRC passed and it all looked good.

burnt the disc and installed it to my offline xbox went to play it and got a message saying it was an unsuported disc.

i then switched the xbox off and moved my usb stick (with my profile on it) to my jtag booted it up and it didn't pick up the profile, checked on my stick and my profile was there but it's now corrupted.

i ran the console serial and xvalue from xval and got a message saying secdata decrytion error.

oh dear

looks like you can be get your console banned offline now.

Secdata decrytion error does not mean your console is flagged or banned, it simply means you typed the codes wrong (at least that's all it used to mean). Are you typing dashes as well? Is the uppercase/lowercase correct?

I have just tried mine, Secdata is clean. Put one letter in the wrong place and I get a Secdata decrytion error. Tried again with the correct code, Secdata is clean again.

Cant answer the whole corrupted profile thing though.

What did you burn it with?? IHAS on Overburn?? Also when did you last check your Xval??


I have noticed some odd behaviour which leads me to believe some sort of silent update has been slithered-out in the last day or so as my test machine is now telling me that previously perfect backups are now coming-up unreadable (Of course I am well aware it could be a lot of things that have nothing to do with XBAP) I make mention of this incase anyone else is experiencing the same or similar to get on to it quickly, Now I will check the drive and other things for means of causing this error on a disc with an immaculate surface that was working fine yesterday and the day before..

It would be nice if we had a way of generating our own topo's (for those of us with good reason and the patience to do so..)


Oh yeah: AFAIK the way Xval is done, keying-in a digit wrong will produce a result that doesn't indicate a security failing/flagging. Pretty sure it's some type of one-way hash, so miss-keying will just give u an error (from memory)