If your 360 has suddenly stopped booting certain backups that previously worked fine, it's probably because your machine has failed an AP2.5 challenge. AP2.5 is the anti-piracy method that MS employ on certain games. This guide covers everything you need to know about checking if your console is flagged, how to avoid being flagged, and LT+ 3.0. Here's how to check if your console is flagged: - 1. Download XVal 2.0. You can get it from Xbox-Scene, HERE. 2. Fire up your 360 (it doesn't matter if you're connected to Live or not) and go to Console Settings - System Info in the dashboard. Here you'll find your console serial number and at the bottom of the screen, you'll see "X:" followed by a 16 character string. 3. Run XVal 2.0 and enter in your console serial number and the X value from the System Info page, then hit the Decrypt button. If your console is clean, you will see "Secdata is Clean" displayed as the result. If your console has been flagged for failing an AP2.5 challenge, you will see "Failed AP25 Challenge". You may see other messages, as your 360 may have failed a different challenge, but anything other than "Secdata is Clean" is not good. What does it mean if my console is flagged? If you're flagged for a failed AP2.5 challenge, then the following occurs: - 1. Backups protected by AP2.5 won't boot unless they are re-patched either with the correct AP2.5 data (LT+ 2.0) or with topology data (LT+ 3.0). In some cases, some AP2.5-protected games may still boot, while others won't, as MS have been disabling AP2.5 in certain titles with title updates. 2. Your console is revoked, which means it can no longer sign data in a way that other consoles can read. That means that if you have gamertags/game saves on a USB stick and you connect that stick to a different console, the gamertags and saves will show up as corrupt data. It does not necessarily mean that you will get banned as legit users have been flagged for failing AP2.5 challenges too, so it's not a 100% reliable method for only catching people playing backups. If I'm not flagged, am I safe? Not necessarily. XVal 2.0 checks to see if you've been flagged client-side, which means on your console. You may have been flagged for something server-side (i.e. on Xbox Live), but there's no reliable way to check for that. If my console is flagged, what can I do? If you have a clean backup of your 360's NAND, you can restore that and remove the flag, but you may still be flagged server-side if you've been using Xbox Live. How do I avoid getting flagged for failing an AP2.5 challenge? There are a couple of steps you should take: - 1. Make sure that any AP2.5 backups you have are fully patched and up to date. 2. Stay off Xbox Live if you're not on LT+ 3.0 with fully patched backups! If you connect to Live, your 360 will download an update to DAE.bin silently and then when you try and boot an AP2.5 game (either online or offline), your console will be flagged. How does LT+ 3.0 change this situation? LT+ 3.0 handles AP2.5 challenges differently to previous versions. With LT+ 2.0, the AP2.5 data is ripped and stored based on the current challenges only, so when the challenges change, you need to re-rip/re-patch and re-burn your games. This is impractical now that MS can update DAE.bin any time they like silently in the background. In LT+ 3.0, disc topology data is stored in the backup that enables the console to answer any AP2.5 challenges, even when the challenges change. Do I need to re-rip/re-patch/re-burn AP2.5 protected games for LT+ 3.0? Yes. LT+ 3.0 requires that the new topology data is stored on your backup disc. The good thing is, you will only have to do this once, then you will not have to worry about AP2.5 again (unless MS improve or change the system of course!). Xbox Backup Creator has been updated to enable you to rip/inject the topology data and a new version of abgx360 will be released that will patch this topology data into ISOs for you. How do I patch games for LT+ 3.0? Check the guide, HERE. What games need patching for LT+ 3.0? Check the list, HERE. Will games patched for LT+ 3.0 work OK on LT+ 2.0 and vice versa? Nope. Why is all of this necessary? Isn't my backup already a perfect copy of the original? Backups are not perfect copies of the original. Original discs are pressed in a factory and it's not possible to create perfect 1:1 backups of them using DVD burners and DVD+R DL media. In fact, that's what AP2.5 relies on. When will the new version of abgx360 be released? There is no ETA for the new version of abgx360, but it's in progress.