Develop Bugs

[Q] Rogers GS3 ROM Questions...

Hello,
New to android... I have searched and searched and read in a LOT of threads trying to get Cyogenmod 10 working on my i747m on Rogers.
I have found many guides and have managed to root my phone and tried installing Cy10 but got an error 7. I read that this was because of the wrong recovery version. I was told to get ROM manager and update through there. For me, however, the GS3 doesn't show up in the options.
Could someone please link me the correct files that I need? I think I know the steps, but it seems that all the files have different versions and are not compatible.
I'm trying to be very careful and not brick my phone, so I am reluctant to try anything that I'm not sure will work... I think that's why this is difficult (Rogers = AT&T? or not?, etc.)
Thank you in advance to anyone who is willing to take the time to help me.

I had the exact same problem as you and what I did was flash, if I remember, cm9 and go to ROM manager and then it would show me Samsung Galaxy s3(att).

You need to update your recovery I flashed the touch recovery from the toolkit and that worked for me
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

First: Thank you both for your replies!
zap12341 said:
I had the exact same problem as you and what I did was flash, if I remember, cm9 and go to ROM manager and then it would show me Samsung Galaxy s3(att).
Click to expand...
Click to collapse
Do you remember which version of cm9? I tried that last night and I still got error 7, but maybe I used the wrong version. All I could find were nightlies, no stable ones for d2att (which is what I was told was our phone)
offwiththeface said:
You need to update your recovery I flashed the touch recovery from the toolkit and that worked for me
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
What version of the toolkit? I can only find 1.0 which gives me recovery 5.5

I'm in the same place. Rooted tried cmw and touch recovery both giving errors. Rom manager from the play store doesn't have an option for a different recovery for me.
Sent from my SGH-I747M using xda app-developers app

onei0077 said:
I'm in the same place. Rooted tried cmw and touch recovery both giving errors. Rom manager from the play store doesn't have an option for a different recovery for me.
Sent from my SGH-I747M using xda app-developers app
Click to expand...
Click to collapse
I've been trying for 3 days.. I'll let you know if i find a solution (if this thread doesn't provide one that is)
(I'm in Ottawa too!)

Error 7 is means you don't have the right requirements to start with.
If you are trying to flash bell 4.1.1 on your Rogers device running 4.0.4, you must first install bell stock 4.0.4 from Sammy site or else things like will throw error 7 during install.
Read CM10 requirements carefully...

I had the same problem. I just upgraded the CWM version to the latest one using this (its the same step, just make sure you download the right recovery):
youtube.com/watch?v=rx8GuAKxzpA
Get recovery from the main CWM site:
clockworkmod.com/rommanager

I am having an extremely hard time installing Cyanogenmod.

Hi there,
I have a Galaxy SIII SGH-i747 from Virgin in Canada. As for as I know, its the same as Bell and every other SGH-i747. So tonight I tried flashing cyanogenmod 10.1 to no avail. I have rooted and installed CWM. When I try to install any ROM it comes up with the error "assert failed getprop status 7". I have searched around and have tried updating CWM recovery through ROM Manager from the play store, but the app doesn't allow me to select my phone model (says there is no official release of CWM for SGH-i747) and says the current version will do. This ROM does not want to install.
HELP!:crying:

disengage said:
Hi there,
I have a Galaxy SIII SGH-i747 from Virgin in Canada. As for as I know, its the same as Bell and every other SGH-i747. So tonight I tried flashing cyanogenmod 10.1 to no avail. I have rooted and installed CWM. When I try to install any ROM it comes up with the error "assert failed getprop status 7". I have searched around and have tried updating CWM recovery through ROM Manager from the play store, but the app doesn't allow me to select my phone model (says there is no official release of CWM for SGH-i747) and says the current version will do. This ROM does not want to install.
HELP!:crying:
Click to expand...
Click to collapse
Status 7 is an out of date recovery or incorrect recovery.
You need a d2att recovery. The Canadian models are d2can. Same phone but it is a system fail safe.
Flash either one in recovery, reboot back into recovery, wipe and enjoy cm10.1
http://d-h.st/8qP cwm
http://d-h.st/qft cwm touch
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

sending onalond
KorGuy123 said:
Status 7 is an out of date recovery or incorrect recovery.
You need a d2att recovery. The Canadian models are d2can. Same phone but it is a system fail safe.
Flash either one in recovery, reboot back into recovery, wipe and enjoy
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Just to be clear: Load the CWM you linked onto SD. Reboot into CWM, flash new CWM, reboot and wipe?
Also to clarify, I have a Canadian model SGHi747

disengage said:
Just to be clear: Load the CWM you linked onto SD. Reboot into CWM, flash new CWM, reboot and wipe?
Also to clarify, I have a Canadian model SGHi747
Click to expand...
Click to collapse
Yup. After flashing that zip and rebooting into recovery it'll reboot into the updated recovery.
Make a backup first of course.
I'm on Telus which is also a d2can phone. I've been running twrp for d2att since I bought the phone in Jan.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

KorGuy123 said:
Yup. After flashing that zip and rebooting into recovery it'll reboot into the updated recovery.
Make a backup first of course.
I'm on Telus which is also a d2can phone. I've been running twrp for d2att since I bought the phone in Jan.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Okay thanks, I will try later and reply with results.

KorGuy123 said:
Yup. After flashing that zip and rebooting into recovery it'll reboot into the updated recovery.
Make a backup first of course.
I'm on Telus which is also a d2can phone. I've been running twrp for d2att since I bought the phone in Jan.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Also should I flash with ODIN?

disengage said:
Also should I flash with ODIN?
Click to expand...
Click to collapse
No recovery.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

KorGuy123 said:
No recovery.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Hi there, I tried flashing from recovery, choosing zip from sdcard, and I got the same exact error assert failed: getprop(" ro.product.device") == "d2att" || getprop( " ro.build.product " ) == "d2att" E:Error in /sdcard/CWM-recovery_ATT-6.0.2.3_2.zip
(status 7)
Installation aborted.
I tried exactly what you said, still nothing.

Bump.

Did you have the most recent stock rom before flashing cyanogenmod? The newer versions of the nightlies require that you have the most recent bootloader. If you had ics, it'll fail to flash until you update your bootloader. The most recent build before the bootloader assert that you can flash is rc2.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 4 Beta

Domoo said:
Did you have the most recent stock rom before flashing cyanogenmod? The newer versions of the nightlies require that you have the most recent bootloader. If you had ics, it'll fail to flash until you update your bootloader. The most recent build before the bootloader assert that you can flash is rc2.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 4 Beta
Click to expand...
Click to collapse
I think so. i have no idea how to check, forgive the noobness plz. My stock firmware is 4.1.1

Bump? Does anyone know how I can flash an updated recovery?

disengage said:
Bump? Does anyone know how I can flash an updated recovery?
Click to expand...
Click to collapse
The link I gave you is the most up to date recovery. There is a thread here for most recent stock roms. Quick search will assist you.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

KorGuy123 said:
The link I gave you is the most up to date recovery. There is a thread here for most recent stock roms. Quick search will assist you.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
I understand that, but I cannot flash the updated CWM. What am I doing wrong?

Okay, so I see people are trying to help me but it's so vague. Every article or how to, or help page ive read on this site or others, suggest conflicting ways to perform these mods. Why can't anyone just tell me straight up, you do this, then this, then that? I feel it shouldnt be this much of a headache and before I've even started modding, I'm getting very turned off. I am already frustrated beyond comprehension. Like I said, I've searched, and searched and nothing is helping. Everything is too vague.
So my question stands: I flashed an outdated recovery by accident, and I want to flash a new, UPDATED recovery. KorGuy provided me with instructions and a link to a new, updated recovery, however I cannot flash that from my current recovery.
What can I do to flash an updated CWM?
Can someone give me a hand?

You need to flash the most recent STOCK firmware through ODIN so you will have the most recent bootloader, then flash your recovery of choice through ODIN, boot into recovery, not system as the recovery will be overwritten iirc. Then flash cm in recovery
Sent from my SGH-T999 using Tapatalk 2

disengage said:
Okay, so I see people are trying to help me but it's so vague. Every article or how to, or help page ive read on this site or others, suggest conflicting ways to perform these mods. Why can't anyone just tell me straight up, you do this, then this, then that? I feel it shouldnt be this much of a headache and before I've even started modding, I'm getting very turned off. I am already frustrated beyond comprehension. Like I said, I've searched, and searched and nothing is helping. Everything is too vague.
Can someone give me a hand?
Click to expand...
Click to collapse
If you can't follow a guide like this and figure things out, maybe flashing ROMs just isn't for you. I'm not trying to offend, but this isn't for everyone.

danieljordanmaddux said:
You need to flash the most recent STOCK firmware through ODIN so you will have the most recent bootloader, then flash your recovery of choice through ODIN, boot into recovery, not system as the recovery will be overwritten iirc. Then flash cm in recovery
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
Okay, I understand that I need to flash with ODIN. However, don't I need a .TAR recovery? I can't flash .img through ODIN...

Correct. Find the .tar of the recovery. I think you can find the TWRP .tar on their website
Sent from my SGH-T999 using Tapatalk 2

Root your phone and install a custom recovery. Most root guides will include instructions for flashing a custom recovery. Next buy "ROM toolbox" form android market, I say by because you will love this app so much you will want to buy it eventually anyway.
Open ROM toolbox and select cyanogen mod. ROM toolbox will flash your phone for you! It can also flash the custom recovery if you did not do this when you rooted your phone.
Annnother must have root app is titanium backup.
Hope this helps.
Sent from my Nexus 4 using xda app-developers app

[Q] CM 10.1 RC5 Wont Flash

Hey guys, right now im running CM 10 stable build, but when i flashed CM 10 i flashed the d2att, which worked fine for me. SO i decided to dirty flash CM 10.1 d2att since i flashed the att build last time, then i figured, maybe i got lucky last time, so i dirty flashed d2tmo and it still didnt work!
I dont wanna have to wipe everything and do a clean install all over again! SOMEONE PLEASE HELP!!!!!
Im with wind, so thats why the d2tmo made more sense, in case your wondering

Just to be sure, you do have the T999V model, correct?
If so, your answer is here:
http://forum.xda-developers.com/showthread.php?p=41701398
Sent from my SGH-T999L using xda premium

CM10 is 4.1.2 and CM10.1 is 4.2.2. You cannot dirty flash different Android versions, you have to wipe and start over, after backing up everything first of course.

Alright thanks!
Just a quick question before i flash, do i need to be on stock TW, cuz as i said im on CM10
And all i do is flash this, reboot and then flash CM 10.1 and gapps? right?

Nandroid backup first if you haven't. You will need to factory reset after flashing cm I'm pretty sure. Backup your internal sdcard too, just in case.
Sent from my SGH-T999L using xda premium

DocHoliday77 said:
Nandroid backup first if you haven't. You will need to factory reset after flashing cm I'm pretty sure. Backup your internal sdcard too, just in case.
Sent from my SGH-T999L using xda premium
Click to expand...
Click to collapse
You don't need to wipe data from CM 10 -> 10.1.
PSA: Upgrading from CM10 to CM10.1
As you may have noticed, we started updating some devices from cm10 (Android 4.1) to 10.1 (Android 4.2) during the weekend. The upgrade process has been tested extensively for the older devices (manta and mako didn't have that problem since they started out with 10.1), so you should be able to update directly without losing any data.
The single application known not to work is the Clock: Our changes to 4.1's clock to add the Stopwatch and Timer in CM10 aren't compatible with Google's own implementation of those features in 4.2 (which we're using in cm10.1); If your clock starts crashing after upgrading to 10.1, simply go into the Settings -> Apps menu, choose Clock from the All tab, and hit "Clear data".
Click to expand...
Click to collapse

Can somebody please tell me if it is safe to flash this http://forum.xda-developers.com/showthread.php?p=41701398 on CM10 or should i be on TW!?!? Pleaseeee, i wanna use CM 10.1 and this looks like it would help, im just afraid of bricking my phone

Jaz-Crahh said:
Can somebody please tell me if it is safe to flash this http://forum.xda-developers.com/showthread.php?p=41701398 on CM10 or should i be on TW!?!? Pleaseeee, i wanna use CM 10.1 and this looks like it would help, im just afraid of bricking my phone
Click to expand...
Click to collapse
Thats why I linked you to it. Just be sure you have a T999V and not a T999 model S3. Provided you do, it is safe to flash. many have already done so.
You can flash it while on TW or CM.

The assert is already there to include that bootloader in the latest CM10.1 Nightlies. I would suggest to flash CM10.1 & Gapps, then wipe cache & dalvik, then check your Baseband under Settings and About Phone, it may already be VLDLL1, because flashing a ROM shouldn't change those files (modem, etc.).

DJ_SpaRky said:
The assert is already there to include that bootloader in the latest CM10.1 Nightlies. I would suggest to flash CM10.1 & Gapps, then wipe cache & dalvik, then check your Baseband under Settings and About Phone, it may already be VLDLL1, because flashing a ROM shouldn't change those files (modem, etc.).
Click to expand...
Click to collapse
Cm won't flash, which is most likely because the phone isn't on LL1. Even if it is, its not going to hurt it to flash that firmware package.
If you want to be sure first though, what is your current baseband? Its under settings, about device.
Sent from my SGH-T999L using xda premium

yea, it is LL1 (T999VVLDLL1)

Did you ever flash just the modem?
Or have you ever updated via ota or by odin flashing the firmware?
Sent from my SGH-T999L using xda premium

The error msg i get is " E : Error in /sdcard/CM10/cm-10. 1. 0-RC5-d2att. zip (status 7) Installation aborted "
Same goes for when i flash d2tmo
I think ive heard of that status 7 error somewhere, could that be the reason?

ALSO, i can easily flash carbon rom 4.2.1
I just prefer CM and i like not losing my data, so yea, the fact that i can flash Carbon but not CM 10.1 shows that theres no problem with my version of CWM

Update your CWM if you are not using the latest version. Whether or not Carbon flashed is not relevant.
Also, don't flash AT&T ROMs. Just because you can doesn't mean you should. Flash T-Mobile ROMs. With d2tmo CWM. Link to the Odin .tar is in my signature. You flash the proper CWM, and CM will stop hassling you. When you attempt to flash CWM, it checks your bootloader version and recovery version. If either don't match what it's looking for - installation aborted.

Jaz-Crahh said:
ALSO, i can easily flash carbon rom 4.2.1
I just prefer CM and i like not losing my data, so yea, the fact that i can flash Carbon but not CM 10.1 shows that theres no problem with my version of CWM
Click to expand...
Click to collapse
First, I never said there was a problem with CWM, though if you aren't using the latest, I'd suggest updating it.
Second, you never answered my questions in my last post.
Third, I don't know how old Carbon 4.2.1 is but they are now on 4.2.2. When cm went to 4.2.2 is when they started checking your firmware, so just because you can flash that doesn't mean you can flash something newer.
So if you please, do the following and tell me what it says.
Open Terminal Emulator
Enter the following line:
getprop ro.bootloader
Let me know what it says please.
Also, everytime I've ever seen a Status 7 error, its been caused by the firmware not being up to date. So at this point I still believe flashing that firmware pkg I linked earlier will be your fix.
Sent from my SGH-T999L using xda premium

DocHoliday77 said:
First, I never said there was a problem with CWM, though if you aren't using the latest, I'd suggest updating it.
Second, you never answered my questions in my last post.
Third, I don't know how old Carbon 4.2.1 is but they are now on 4.2.2. When cm went to 4.2.2 is when they started checking your firmware, so just because you can flash that doesn't mean you can flash something newer.
So if you please, do the following and tell me what it says.
Open Terminal Emulator
Enter the following line:
getprop ro.bootloader
Let me know what it says please.
Also, everytime I've ever seen a Status 7 error, its been caused by the firmware not being up to date. So at this point I still believe flashing that firmware pkg I linked earlier will be your fix.
Sent from my SGH-T999L using xda premium
Click to expand...
Click to collapse
When i did the terminal thing, i got
"T999VVLALE6"

Ok, that's the problem then. Its scropted to not flash unless that reads VLDLL1. hou can either flash the firmware pkg I linked to, or odin flash the correct firmware. After that you should be able to flash cm.
The pkg I linked to would be the easiest to use.
Sent from my SGH-T999L using xda premium

DocHoliday77 said:
Ok, that's the problem then. Its scropted to not flash unless that reads VLDLL1. hou can either flash the firmware pkg I linked to, or odin flash the correct firmware. After that you should be able to flash cm.
The pkg I linked to would be the easiest to use.
Sent from my SGH-T999L using xda premium
Click to expand...
Click to collapse
Okay, will do, ill flash that pkg and get back to you when i attempt to flash CM 10.1 again

Jaz-Crahh said:
Okay, will do, ill flash that pkg and get back to you when i attempt to flash CM 10.1 again
Click to expand...
Click to collapse
Now this is gonna be awkward, but theres a couple of links there, which one exactly should i click?/:

All Custom Roms (Bad) or (Status 7)

I've been looking all over the forums, and still could have potentially missed the one forum that someone wrote and was replied to once that has the perfect solution but after 3 days of searching I give up. I have a Samsung Galaxy S3 AT&T which today I was finally able to use the CyanogenMod Installer they released the other day to get a custom rom on my phone. But I am really wanting to use the Slim Rom but no matter where I get the files from the zip is always corrupted and giving me the error (Bad) when I try to flash it, and other roms that gave me (Status 7) such as MROM 10.1 and another few, I would go in to the updater-script and remove the assert files only to have it tell me (Bad) or some other error. I'm still noobish once more although I used to do custom roms on my phones a couple years ago very very often to the point I wouldn't keep one more than a month so I'm simply stumped as to what the problem could be. And I can not post directly to the Slim forums because I do not have enough posts.

Mr.Rageface said:
I've been looking all over the forums, and still could have potentially missed the one forum that someone wrote and was replied to once that has the perfect solution but after 3 days of searching I give up. I have a Samsung Galaxy S3 AT&T which today I was finally able to use the CyanogenMod Installer they released the other day to get a custom rom on my phone. But I am really wanting to use the Slim Rom but no matter where I get the files from the zip is always corrupted and giving me the error (Bad) when I try to flash it, and other roms that gave me (Status 7) such as MROM 10.1 and another few, I would go in to the updater-script and remove the assert files only to have it tell me (Bad) or some other error. I'm still noobish once more although I used to do custom roms on my phones a couple years ago very very often to the point I wouldn't keep one more than a month so I'm simply stumped as to what the problem could be. And I can not post directly to the Slim forums because I do not have enough posts.
Click to expand...
Click to collapse
a simple search for status 7 would bring you a whole pile of threads.
Status 7 is one of a few possible issues.
A) You are using an out of date version of your recovery (CWM or TWRP)
B) You're on a Canadian carrier (like me) and you are using a d2can recovery instead of the necessary d2att
Second post on this one.
http://forum.xda-developers.com/showthread.php?t=2179330

I have the newest CWM Touch 6.0.4.3 and I can't imagine I'm on a Canadian Carrier I'm on AT&T and I live in Louisiana granted the phone could be from there but it shows up as an I747 and if I'm not mistaken should the Canadian show as M747?
(Model: Samsung-SGH-I747)
(Android Version: 4.3.1)
(Baseband Version: I747UCDMG2)
(Kernel Version 3.4.66-cyanogenmod-g32e69bc [email protected] #1)
(CyanogenMod Version: 10.2-20131114-SNAPSHOT-InstallerWPPQ46R-d2att)
(Buildnumber: cm_d2att-userdebug 4.3.1 JLS361 or I acf96e183e dev-keys)

Mr.Rageface said:
I have the newest CWM Touch 6.0.4.3 and I can't imagine I'm on a Canadian Carrier I'm on AT&T and I live in Louisiana granted the phone could be from there but it shows up as an I747 and if I'm not mistaken should the Canadian show as M747?
(Model: Samsung-SGH-I747)
(Android Version: 4.3.1)
(Baseband Version: I747UCDMG2)
(Kernel Version 3.4.66-cyanogenmod-g32e69bc [email protected] #1)
(CyanogenMod Version: 10.2-20131114-SNAPSHOT-InstallerWPPQ46R-d2att)
(Buildnumber: cm_d2att-userdebug 4.3.1 JLS361 or I acf96e183e dev-keys)
Click to expand...
Click to collapse
Canadian is I747m yes.
You can try flashing TWRP
Also make sure your bootloader is up to date. (Should be in the link I posted also)

I tried TWRP already and had the same errors and the bootloader is up to date with the newest I could find which came out July 15th of this year I believe.

Mr.Rageface said:
I tried TWRP already and had the same errors and the bootloader is up to date with the newest I could find which came out July 15th of this year I believe.
Click to expand...
Click to collapse
I've heard of instances of people having to downgrade their recovery a version or two to get things to flash. I also recommend a fresh install of a ROM, sometimes messing with an updater can cause some real issues.

Ok the next thing I will try will be an version or two older of CWM and see if that changes anything and if not I'll post again. Thanks for the assistance.

Check bootloaders mg2 not baseband. You need a boot loader checker. You could have mg2 baseband but not mg2 bootloaders.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

blaker13 said:
Check bootloaders mg2 not baseband. You need a boot loader checker. You could have mg2 baseband but not mg2 bootloaders.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Yea I went and grabbed the app Root Checker to double check my Bootloader and it is I747UCDMG2 as well. Board is MSM8960 tho I don't imagine thats any different than any other S3 from ATT Device: d2att Product shows as d2uc not sure if that has anything to do with anything but I am still unable to use any rom I download other than using the CyanogenMOD installer that they released this week or last week. 14th I think..
I have also noticed that whenever I try to extract one of the zipped Roms when I go to remove the assert code that supposedly causes Status 7 that Winrar goes on a tangent about the files being corrupted. So I am wondering if it is possible that they are all being corrupted as I download them tho I do not have the problem with anything else I download. So I am still at a loss and unable to figure out what exactly is happening.
EDIT: Not sure why but its working now, running Quantum from Pwn. Thanks for the info anyways =P Mr.Rageface

BTW we can mark this as solved as well. When I had started putting custom ROMs up last month my SSD was failing but not giving me warnings so all the files I would download to it were corrupting.
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app

[Q] Bootloader Problem?

I have a Sprint Galaxy S3 that I have been running CyanogenMod 10.1 ROM. I have tried to install a new ROM via TeamWin but I keep getting
"assert failed: getprop("ro.bootloader") == "L710VPBMA6/L710VPBMB1/L710VPBMD4/L710VPBMD7 Error executing updater binary in zip"
I was under the impression from much XDA reading that I need to upgrade the modem/radio. I downloaded a Modem Flasher and installed several different radios and I still get the same message.
Any Help?
Update from OP
I downloaded a MD4 firmware, wiped, flashed CM11 and newest GApps and I am up and running.

If you're on Sprint then you shouldn't have anything labeled md7, what carrier are you using? I only ask because md7 was never a build number for sprint, something doesn't seem right.

metalfan78 said:
If you're on Sprint then you shouldn't have anything labeled md7, what carrier are you using? I only ask because md7 was never a build number for sprint, something doesn't seem right.
Click to expand...
Click to collapse
I have Sprint as my carrier. I agree that there is something is not right. Not getting any answers so I plan on reverting back to stock, rooting again and then putting on CM11.

What rom were you trying to install?

I am just trying to update from Cyanogen 10.1 to 10.2.
Sent from my SPH-L710 using xda app-developers app

androidkevlar said:
I am just trying to update from Cyanogen 10.1 to 10.2.
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
Did you double check you downloaded the right version for your Galaxy S III and not for like T-Mo or AT&T...
http://download.cyanogenmod.org/?device=d2spr <- Sprint Galaxy S III
And best way to do is just go back to stock and start from scratch..

The original assert failed message is just listing all possible bootloaders it is looking for, it doesn't mean MD7 is part of what the author has installed. By the way, that particular one is a Virgin Mobile/Boost bootloader, as are MG2 and MK5. More likely, the author has MK3, which is not recognized by the updater-script in the older CM versions. CM 11 has the newest bootloaders recognized in the updater-script. Also, modem is not bootloader, even though the nomenclature is the same (MD4, MK3, etc.). Flashing a different modem will not make the updater-script recognize your actual bootloader. If you really want CM 10.2 and not CM 11 (CM 11 is awesome in my opinion, absolutely loving it!), then removing the assert lines altogether should allow for a successful flash, just be sure you have a d2spr ROM if you are going to remove this security feature from within the .zip file.
P.S. Try switching to Philz Touch as well, it is an awesome recovery.