Simple answer - no its not an easy fix. I hope this will explain to those who have the newer phones like myself and what to expect.
Status 7 is an assert error. You I suspect have a factory MG2 phone. ROM makers add some code to the top of the install scripts to make sure you are flashing to the correct phone.
Here is the assert lines from a CM 10.2 ROM:
assert(getprop("ro.product.device") == "d2spr" || getprop("ro.build.product") == "d2spr" ||
getprop("ro.product.device") == "d2spi" || getprop("ro.build.product") == "d2spi");
assert(getprop("ro.bootloader") == "L710VPBLJ7" ||
getprop("ro.bootloader") == "L710VPBMA6" ||
getprop("ro.bootloader") == "L710VPBMB1" ||
getprop("ro.bootloader") == "L710VPBMD4" ||
getprop("ro.bootloader") == "L710VPAMD7");
See how its looking for "d2spr" (Sprint GS3) or a bootloaders of "L710VPBMD4" (MD4) or L710VPAMD7 (MD7)
MD4 = last Samsung Sprint ROM
MD7 = first(?) Virgin Mobile phone
My build (newer Virgin Mobile phone) is: L710VPAMG2 (or MG2)
Since the "assert" sees your (or mine) phone as a MG2 and its not on its approved list - it wont install and gives you a Status 7 error.
Now how to fix it.
Possible fix #1
Flash the Sprint MD4 Bootloaders. IMO flashing bootloaders is no joke. Flash a normal ROM built for your device and 99.9% of the time no matter how bad the flash you can recover - this is because you can still boot the device (at least to recovery). If an error occurs during the flash of a bootloader - you have a brick and time to find someone with a Jtag.
The link you went to tells you how to flash the Sprint Bootloaders. You can go that way or - I believe the Midnight ROM also flashes the Sprint MD4 bootloaders along with the ROM.
MAKE SURE YOU HAVE A SPH-L710 phone!
Possible Fix #2
Remove the assert lines for each ROM you plan to flash. This is the route I take. I also customize the ROM, repackage, then flash.
For how to do that check here:
How To Fix Status 7 Error with CWM Recovery on Rooted Android! | HighOnAndroid.com
Hope it helps
