If booting an AP25 title without AP25 SS game will not boot but will still be protected from logging AP25 violation on current dash 2.0.12611.0. If LT+ encounters an unknown AP25 challenge, game will not boot but console will still be protected from logging AP25 violation on current dash 2.0.12611.0.

You don't need to reburn older games that don't have the AP25 security. AP25 is an additional security sector on the disc. The first game that had this physically different disc was Fable III, followed by NFS Hot Pursuit and Assassin's Creed: Brotherhood.

For any games before that, the retail disc did not have an AP25 sector. The only games that you would need to reburn would be one of the new AP25 games (the three I mentioned plus whatever other new games) that you burnt before abgx360 was updated with the ability to do AP25 patching, because those won't pass AP25 checks and will result in your xbox being flagged.

All older games work perfectly since those did not have AP25 to begin with (and it can't be added in unless the game was re-released, with newly pressed discs).

Well then get a look into the source of abgx and see what it checks. It does not and it can not verify that the sp25 sector is correct for your image...

Latest news is that c4e does not release a new 0800 firmware because it would allegedly "to be too complex for the user to
handle it and it would allegedly reveal a protected security hole." They are now asking for a fund to buy all originals...

HAHA... Let me have a laugh about that.

Like I wrote before. The rip off is already starting. There is in fact no real reason that is hindering c4e to insert a new command byte into the 0800 fw command dispatcher to produce the new sector. This is acually the same procedure already done with the 1st security sector. The drive initiates the challenges that would normally be initiated by the 360 and stores the resulting data in the so called security sector. That would alsow have to be done for the ap25 sector. There is nothing special about that. They just do not want to give this feature out of their hands. That's it.