QUOTE(OriginalCompGeek @ Sep 29 2006, 01:08 PM)

There are rare instances in which this would be useful.
Example, you get a totally new drive for your 360 and its an MS28. This would be assuming you have your drive key from your old drive.
No, it still wouldn't help with that. This patch is only for firmware. It is applied to firmware. Ok, let's say you get a brand new MS28 drive with the MS28 firmware on it. How are you going to flash it? Of course, you're saying you could patch your firmware, but you need to read/write using the original MS28 firmware. The only way this would be good is if you bought the drive from somebody who patched this beforehand. In other words, a pre-patched original MS28 drive. But that person would still have to have done the VCC/Bad flash for you. So yes, it would be good if you were selling an MS28 to anotehr person and you pre-flashed their drive with the "MS25" firmware. There is still no way to get around the VCC/Bad Flash the first time.
Firmware on drive = MS28
In order to use this patch = need to read/write to drive
MS28 and read/write = need VCC or Bad-Flash
^ just think about it, the drive STILL needs to be messed with at least once. This is not "an essential patch" as quoted by Xecuter. It's nothing. It's cool he figured out what exactly was causing the lockout, but it still doesn't help, because MS isn't going to ship drives with this "patch" now are they?