QUOTE(Choochoo @ Nov 4 2009, 05:34 PM)

(pure speculation on my part), given all the data here, wouldn't it make sense for them to detect the actual firmware, then do random bannings to make the firmware developers scramble their heads on what exactly is being detected?
The ideal method for MS would be to directly detect the modified firmware. It would seem in the past they had difficulty in doing this. Hence why they had other methods which all relied on detecting backups themselves, opposed to firmware.
For the Samsung Drives/BenQ Drives, to mod them you need to read the original firmware to get the drive key. You can't just read it, you have to trick the drives into recovery mode. I've always assumed microsoft would have to do the samething. If they tried to boot them into recovery mode it would probably cause issues on the console.
If they were smart they integrate it with dashboard updates. The system has to reboot anyways when its done.. why not make that process take an extra 30 seconds, dump the firmware, see if passes hashcheck? then reboot it back to normal. all under the guise of the dashboard update installing.