The "Review Version" leaks are most likely not to blame for this. If you want to know why, I'll try to explain but english is not my first language so be gentle.
Remember when the first banning wave occured in 2006? Back then, it was agreed upon that bad game dumps were to blame (corrupted and/or missing security files). It was also discovered, that anti copy protection software which installs ring 0 level drivers into your system to circumvent stuff like DVD Movie copy protection or PC-Game copy protection could corrupt the iso file structure.
Therefore, C4Eva created iExtreme, to at least prevent the booting of bad burns with missing security files and everyone thought that was actually the underlying problem. It was not, but I'll come to that in a bit.
Then, in late 2007, the second banning wave began. Initially, this was -again- blamed to bad game dumps. C4Eva himself speculated, that "contaminated/marked" ISOs got released, which Microsoft used to tag modified consoles. Only weeks later, C4Eva retracted this statement, and revealed an error in iExtreme, which was of course also present in the old Xtreme Firmwares - the disc jitter correction. In short, the firmware produced a detectable error with 359° Angle security sectors.
In fact, this error was most likely the cause for all pre IExtreme 1.4 ban waves . I checked all my retail games, and the earliest game which had a 359° Angle in its security sector was Project Gotham Racing 3 (PAL) - a launch title. So it is likely that Microsoft used the angle detection all along, "we" just did not know about it. When each ban wave hit, initially tampered isos were always assumed to be the culprit, but they never were to blame for the bans. It was a bug in the modified firmware which simply remained undiscovered for nearly 2 years until iextreme 1.4.
Hence it is most logical to assume that instead of leaked review copies, another bug in the iextreme 1.4 firmware is being abused to detect the consoles this time around as well. C4Eva just has to discover the underlying cause, if he is even still interested in xbox360 hacking, who knows.
This post is not intended to criticise C4Eva, he has done excellent work and is in no way to blame for any of the things that happened. He provided useful software free of charge under great personal risk, so (still) kudos to him and if he ever reads this: Thanks for all you did.
