Abgx..database "verification" Facts And Myths Explained
Aug 23, 2014 6:03:44 GMT
BL, nojnojnoj, and 1 more like this
Post by alienedd on Aug 23, 2014 6:03:44 GMT
Originally posted by sarcastixx from original forum
Recently, I have spotted an increasing number of people concerned about releases not being verified in the abgx database, so I decided to create a thread to address that concern specifically.
For those new to console modfiying, abgx is a command line launching GUI that performs various checks on a downloaded image of a game. The file you will be checking will be in ISO format.
There are 3 main crucial checks that abgx will perform.
These are done after the initial display of the general game information and check/creation of the small .dvd file needed to specify the layerbreak for your burning program:
1. It first checks that the topology data is actually present and correct. Topology data is the all important sector of the ISO that lets a console flashed with LT+3 or LTU custom firmware answer all AP (Anti Piracy) checks that are performed when a game is booted.
2. It will then go onto check that the ISO security sectors (SS) are fully "stealthed", which means that the game will play safely on a console (if burnt to a decent quality dual layer disc).
The security sectors are checked in combination with the DMI, PFI, and Video Layers by performing another CRC (Cylic Redundancy Check) against them.
A CRC is a general count of the data bits presents present which is then presented in hexadecimal format. Although important, a CRC does not verify the actual contents of the data.
3. ********See after part 4 for this********
4. It will then finally run a CRC on the all important game data partition which will determine if the backup will play through the whole game properly.
Now you are probably wondering at this stage whether I can count or not; you may have noticed that I mentioned that there were only 3 main checks performed and actually listed 4.
The reason for this is that as I have listed the main checks in the order that they are performed, but there is one outstanding non essential check left over that seems to be getting a lot of people in a tizz.
This is the abgx database "verification" check. Before an official release date of a game, every database verification check will report as having failed.
First, I must add that I have no problem whatsoever with abgx program and the idea of having a verified database of releases. The program is essential in keeping all our XBL accounts safe!
However the problem is that because a game is never "verified" on the database before the official release date, people are seeing the "verification failed" message just before the game partition CRC check is performed. (Part 4 above). This is what is constantly causing confusion whenever a game gets leaked early. I still see people who genuinely believe that they simply cannot play a game until it has been verified on the database.
Apart from what some people may think this is absolutely unnecessary. I am not telling anyone what to do here, simply pointing out facts so if you still think you must wait until verification appears, be my guest.
But I can guarantee that the only thing that you need to worry about when checking an ISO is that parts 1,2, and 4 described above give green successful notifications.
You will see the verification check having failed as in the example below:
See the yellow text? For information only. Simple as that. Nothing more, or less. The game simply hasn't been officially released yet. And more importantly, you can IGNORE IT!!!
The all important text is in green saying "Basic Stealth Check Passed". And then at the end saying "AnyDVD style corruption was not detected" .
These are essential and you need to look for these before even thinking about looking out your blank discs.
Thankfully, abgx is a very intuitive program that is filled with tips when an error is found.
If you read them carefully you can hopefully avoid going on every forum and asking around, which generally gets on peoples' nerves as they know you haven't taken any action to research and resolve whatever problem you have.
So long as you follow these rules of determining whether an ISO is safe to burn:
Green text = Good: NO ACTION NEEDED
Yellow Text= Information only: NO ACTION NEEDED
Red Text= Unsafe: ACTION NEEDED! (do not burn until fixed unless you have a topology data error because you have created a converted LT+2 ISO)
And yes, although not relevant to this tutorial, the exact same rules apply for the SplitVid messages that occasionally appear.
I sincerely hope that people will take the time to read the above and take in what is being said.
And for those that are still being asked by others about whether a game is safe or not because of a database verification failure, simply point them to this thread and let them make an educated guess.
Happy gaming!
Recently, I have spotted an increasing number of people concerned about releases not being verified in the abgx database, so I decided to create a thread to address that concern specifically.
For those new to console modfiying, abgx is a command line launching GUI that performs various checks on a downloaded image of a game. The file you will be checking will be in ISO format.
There are 3 main crucial checks that abgx will perform.
These are done after the initial display of the general game information and check/creation of the small .dvd file needed to specify the layerbreak for your burning program:
1. It first checks that the topology data is actually present and correct. Topology data is the all important sector of the ISO that lets a console flashed with LT+3 or LTU custom firmware answer all AP (Anti Piracy) checks that are performed when a game is booted.
- Topology data itself is not relevant to this thread so I will not go into more detail about it.
If the topology check is good then it will tell you and go onto step 2... - List item 2
2. It will then go onto check that the ISO security sectors (SS) are fully "stealthed", which means that the game will play safely on a console (if burnt to a decent quality dual layer disc).
The security sectors are checked in combination with the DMI, PFI, and Video Layers by performing another CRC (Cylic Redundancy Check) against them.
A CRC is a general count of the data bits presents present which is then presented in hexadecimal format. Although important, a CRC does not verify the actual contents of the data.
3. ********See after part 4 for this********
4. It will then finally run a CRC on the all important game data partition which will determine if the backup will play through the whole game properly.
Now you are probably wondering at this stage whether I can count or not; you may have noticed that I mentioned that there were only 3 main checks performed and actually listed 4.
The reason for this is that as I have listed the main checks in the order that they are performed, but there is one outstanding non essential check left over that seems to be getting a lot of people in a tizz.
This is the abgx database "verification" check. Before an official release date of a game, every database verification check will report as having failed.
First, I must add that I have no problem whatsoever with abgx program and the idea of having a verified database of releases. The program is essential in keeping all our XBL accounts safe!
However the problem is that because a game is never "verified" on the database before the official release date, people are seeing the "verification failed" message just before the game partition CRC check is performed. (Part 4 above). This is what is constantly causing confusion whenever a game gets leaked early. I still see people who genuinely believe that they simply cannot play a game until it has been verified on the database.
Apart from what some people may think this is absolutely unnecessary. I am not telling anyone what to do here, simply pointing out facts so if you still think you must wait until verification appears, be my guest.
But I can guarantee that the only thing that you need to worry about when checking an ISO is that parts 1,2, and 4 described above give green successful notifications.
You will see the verification check having failed as in the example below:
See the yellow text? For information only. Simple as that. Nothing more, or less. The game simply hasn't been officially released yet. And more importantly, you can IGNORE IT!!!
The all important text is in green saying "Basic Stealth Check Passed". And then at the end saying "AnyDVD style corruption was not detected" .
These are essential and you need to look for these before even thinking about looking out your blank discs.
Thankfully, abgx is a very intuitive program that is filled with tips when an error is found.
If you read them carefully you can hopefully avoid going on every forum and asking around, which generally gets on peoples' nerves as they know you haven't taken any action to research and resolve whatever problem you have.
So long as you follow these rules of determining whether an ISO is safe to burn:
Green text = Good: NO ACTION NEEDED
Yellow Text= Information only: NO ACTION NEEDED
Red Text= Unsafe: ACTION NEEDED! (do not burn until fixed unless you have a topology data error because you have created a converted LT+2 ISO)
And yes, although not relevant to this tutorial, the exact same rules apply for the SplitVid messages that occasionally appear.
I sincerely hope that people will take the time to read the above and take in what is being said.
And for those that are still being asked by others about whether a game is safe or not because of a database verification failure, simply point them to this thread and let them make an educated guess.
Happy gaming!
