|
|
|
COD4 Backup From Ogirinal Fails Verification
|
|
Member
2 product reviews
|
19. June 2009 @ 23:54 |
Link to this message
|
I got COD4 about 2 months after it came out, and so did my friend. I just got my Kreon Drive in 2 days ago, and thought I would make him a copy of COD4 since his original broke about 3 weeks ago. I have a SH-D162D flashed with Kreon v1.00 firmware and I used Xbox Backup Creator v2.9 to make my COD4 backup. I had make a backup of The Orange Box and it passed all of the ABGX Test, but when I do my COD4 test I get this...
───────────────────────────────────────────────────────────────────────────────
\\//\\//\\//\\//\\/█\\//\ \ \/ /┌─┐┌─┐┌─┐\\//\\//\\//\\//\\//\\//\\//\\//\\//\\
//\\//\\//\\//\█▀█\█▀█\█▀█/ /\ \ ─┤├─┐│ │//\\//\\//\\//\\//\\//\\//\\//\\//\\//
───────────────▀▀▀─▀▀▀─▀▀█──────└─┘└─┘└─┘─v1.0.1───────[http://abgx360.net]────
▀▀▀
Checking for updates to GameNameLookup.csv and abgx360.dat...
Server file GameNameLookup.csv no newer than local file - not retrieving
Server file abgx360.dat no newer than local file - not retrieving
H:\Call Of Duty 4.dvd is valid
Checking Game
ISO: "H:\Call Of Duty 4.iso"
Size: 7835492352 bytes (SplitVid 2nd wave)
Files in ISO: 2596, Folders in ISO: 2
Total bytes used: 6943014822 (95.13%)
Game appears to have random padding
Checking default.xex
Original PE Filename: CoD3.exe
Original PE Timestamp: 2007/09/08 00:09:19
Game Name: Call of Duty 4
Developer: Infinity Ward
Publisher: Activision
Genre: First Person Action
Achievements: 37 Achievements totaling 1000 Gamerscore
XEX CRC = 336D09AC
XEX Media ID: 1EDFAC80440C6BD3DB843F83-15E8CF88
Call of Duty 4- Modern Warfare
Region Code: 0xFFFFFFFF
Region Free!
Checking SS
Timestamp of Authoring: 2007/09/10 00:00:00
Timestamp of Mastering: 2007/11/13 16:21:59
Caution: This SS contains a value (angle 359) that will cause older versions
of iXtreme to return a detectable bad response! Make sure your drive is flashed
with iXtreme version 1.4 or newer. Alternatively, you may enable the option to
adjust angle 359 for compatibility with iXtreme < v1.4
SS CRC = 8682A6F4 (RawSS = 28EC973E)
SS Media ID: 1EDFAC80440C6BD3DB843F83-15E8CF88 (matches game)
SS looks valid
Checking DMI
Timestamp of Authoring: 2007/09/10 00:00:00 (matches SS)
DMI CRC = 8F74F39B
DMI Media ID: 1EDFAC80440C6BD3DB843F83-15E8CF88 (matches game)
DMI looks valid
Checking PFI
PFI CRC = A4CFB59C
PFI matches known data (2nd wave)
Video partition found
Checking Video padding... Video is zero padded
Video CRC = 91410773 (V0 = 81DF6964, V1 = E47F6A94)
Video partition matches known data (2nd wave)
Stealth check passed!
Starting Verification
Looking for 8682A6F4336D09AC.ini in the online verified database
There is no verified rip of this Xex/SS combination in the online database
Failed to find a verified ini file for this Xex/SS combination
Verification failed
Set AutoFix Threshold to Level 3 if you want to try and find a verified SS and
Stealth files that match the Xex, and automatically patch them if found.
Press any key to exit . . .
I created it from an original, so I have no idea why it is says verification failed. Anybody else ever have this problem?
Thanks in advance.
WiiNewz Senior Member
Console Scene Staff Member
|
|
Advertisement
|
|
|
|
|
ck44
Junior Member
|
20. June 2009 @ 06:32 |
Link to this message
|
|
Read the error carefully.
"Set AutoFix Threshold to Level 3 if you want to try and find a verified SS and Stealth files that match the Xex, and automatically patch them if found."
Go ahead and do as told, set autofix threshold to level 3, and then it'll work.
|
Member
2 product reviews
|
20. June 2009 @ 08:19 |
Link to this message
|
If I verify with Xbox Backup Creator 2.8 it says everything is fully stealth patched. I have began to think, I made this straight from an original, so maybe the stealth files I have, are not the same as the same on the ABGX Data Base, but are still stealth. Can somebody back me up on this?
WiiNewz Senior Member
Console Scene Staff Member
|
AfterDawn Addict
|
20. June 2009 @ 08:37 |
Link to this message
|
Originally posted by cheez_cs:
If I verify with Xbox Backup Creator 2.8 it says everything is fully stealth patched. I have began to think, I made this straight from an original, so maybe the stealth files I have, are not the same as the same on the ABGX Data Base, but are still stealth. Can somebody back me up on this?
That's absolutely right. Most of the games I backed up from originals look that way.
Xbox 360: Slim untouched with a faked 320 GB harddrive for XBL, phat with LT 3.0, played Halo early, so going on live would be an instand ban, also with a faked 320 GB harddrive
PS3: Untouched 160 GB Slim, 60 GB Fat with latest Rogero and 160 GB internal harddrive.
PSVita: hardly ever play it
GameCube: Black with a Viper chip installed. With gameboy player. Trying to get a Wavebird controller.
|
|
ck44
Junior Member
|
20. June 2009 @ 08:37 |
Link to this message
|
|
always verify your games with abgx, just do what I told you, go ahead and set the autofix threshold to level 3 and it should verify correctly.
|
Member
2 product reviews
|
20. June 2009 @ 08:45 |
Link to this message
|
Originally posted by Eisherz:
Originally posted by cheez_cs:
If I verify with Xbox Backup Creator 2.8 it says everything is fully stealth patched. I have began to think, I made this straight from an original, so maybe the stealth files I have, are not the same as the same on the ABGX Data Base, but are still stealth. Can somebody back me up on this?
That's absolutely right. Most of the games I backed up from originals look that way.
I believe this response more than...
Quote:
always verify your games with abgx, just do what I told you, go ahead and set the autofix threshold to level 3 and it should verify correctly.
Reason I say that, is Eisherz stated he copied his games from originals. No, offense to ck44.
Thanks to both of you for your inputs and help.
WiiNewz Senior Member
Console Scene Staff Member
|
|
w4nker
Junior Member
|
20. June 2009 @ 08:47 |
Link to this message
|
|
If you made the retail copy yourself, leave it the way it is. ABGX is more for downloaders to compare against retail. I do my own rips and leave everything the same and i have never been BANNED... yet.
|
|
ck44
Junior Member
|
20. June 2009 @ 08:50 |
Link to this message
|
|
it's cool man, just trying to help. I also copy my own games and always use abgx seeing that everybody has told me it is the most trustable and the most updated of all, but yeah, it is important to set the autofix thresold to level 3 if you want good results, glad it worked out for you though!
|
|
w4nker
Junior Member
|
20. June 2009 @ 08:51 |
Link to this message
|
|
If you made the retail copy yourself, leave it the way it is. ABGX is more for downloaders to compare against retail. I do my own rips and leave everything the same and i have never been BANNED... yet.
|
Member
2 product reviews
|
20. June 2009 @ 08:55 |
Link to this message
|
I have only downloaded a couple games myself, before I got my Kreon Drive that was my only way of obtaining backups. When I download a game, I ALWAYS run it through ABGX360 and Xbox Backup Creator. If a friend lets me borrow a backup to test out before I go out and buy it, I always stealth check it. If it doesn't pass stealth, I don't even think about putting it in my 360.
I know how people say, "Well if it isn't stealth patched, then just make sure you play it offline." If a game doesn't stealth check, it does not enter my 360.
WiiNewz Senior Member
Console Scene Staff Member
|
AfterDawn Addict
|
20. June 2009 @ 18:06 |
Link to this message
|
Originally posted by ck44:
always verify your games with abgx, just do what I told you, go ahead and set the autofix threshold to level 3 and it should verify correctly.
If you rip your own games, why would you ever run it through abgx with autofix enabled?
I'm under the assumption that you don't fully understand the purpose of abgx. It's purpose is to verify that all the data matches what should be there... for a downloaded game.
If you ripped your own game that means you have the original right there in your hands... obviously all the data on that disc belongs together.
Why in the world would you need to verify that?
|
|
ck44
Junior Member
|
20. June 2009 @ 21:10 |
Link to this message
|
|
does it really hurt to run it through abgx? better be safe for everything. You're right, but it really doesnt hurt to run it through the program.
|
AfterDawn Addict
2 product reviews
|
20. June 2009 @ 21:14 |
Link to this message
|
|
Only thing I could think of would be a High or Low angle deviation. But then again, I'm pretty sure ix1.4 and higher will fix that on the fly.
|
|
Advertisement
|
|
|
AfterDawn Addict
|
21. June 2009 @ 12:29 |
Link to this message
|
Originally posted by ck44:
does it really hurt to run it through abgx? better be safe for everything. You're right, but it really doesnt hurt to run it through the program.
With autofix level 3... yes, you are hurting your rip. You're taking data which is 101% good (you have the original disc right there in front of you) and replacing it with some data downloaded from some database which you have to trust someone else saying it's good.
Every same game does not use the same specific set of info (dmi, pfi, etc.). That's why the op's CoD4 didn't verify. But that doesn't matter if the stealth didn't verify against the database because, like I keep saying, he ripped the game himself. He has the disc right there in front of him. So there is no possible doubt in the world that the dmi, pfi, ss, and vid iso belong on that disc.
In a nutshell, with autofix 3, he'd be taking a good (stealth-wise) rip and converting it in to an exact copy of the game he could have just downloaded from the web.
Now, it's been theorized before that MS could upload one of their own rips to the web, with specific dmi. etc., and then track consoles playing that game and ban them.
So the moral of the story is when making your own rips, check it with abgx WITH THE AUTOFIX OFF. All you want it to do is make your .dvd file, chech crc, and check that the dmi, pfi, ss, and video are present and do match the game data.
It does not matter if that info matched the database or not, it only matters that the info is present in the iso before you burn it.
This message has been edited since posting. Last time this message was edited on 21. June 2009 @ 12:32
|
|
