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

CyanogenMod 10.1 Nightly Installation Error "Status 7"

Greetings! This is the first time I've felt compelled to post in the forums, so I apologize in advance if this happens to be in the wrong section. I've been running CyanogenMod 10.1 on my Samsung Galaxy S3 SGH-T999VVLLH2 (Mobilicity) for quite some time now, and have only recently been interested in downloading and installing the nightly installments that are released.
I haven't had any issues installing the new nightlies at all, until seemingly after revision 20130513. It seems that after this installment, I receive an "assert failed, get prop, status 7" error, upon the attempt at installing any newer nightly revisions. Now, I did a tremendous amount of digging around before I decided to make the post, and discovered that within the newer revisions, the updater-script now seems to flag certain Baseband versions of the phone, and prior to revision 20130513 (currently have), it didn't, and I had no issues installing.
When I go into the CyanogenMod settings, all of the nightly updates are available, as usual, up to the latest at the time of the post (20130524) but none will install. In the latest revisions the updater-script does show a similar version (T999VVLDLL1), which I've come to understand is an update for the software.
Am I required to do another update before installing the latest CyanogenMod 10.1 nightlies? Or is there another solution I haven't discovered yet? Any help regarding this would be greatly appreciated. Thanks!
On a side note, I am running the latest ClockWorkMod Recovery as well.

Im surprised that it happened to you on an AOSP recovery. Usually it happens when its a modded recovery with a kernel.
Try TWRP. Or check for an update.
Sent from my GT-I9505 using xda premium

You need to flash a firmware update that will update the bootloader. Not the UVDMD5 one though for sure because that's for T-Mobile. Maybe the other one. Lemme try linking you to the thread.
Edit : here read up on this before flashing http://forum.xda-developers.com/showthread.php?t=2290118
T999V VLDLL1 Bootloader + Modem (Flashable .zip)
Sent from my SGH-T999 using Tapatalk 2

TheLastSidekick said:
You need to flash a firmware update that will update the bootloader. Not the UVDMD5 one though for sure because that's for T-Mobile. Maybe the other one. Lemme try linking you to the thread.
Edit : here read up on this before flashing http://forum.xda-developers.com/showthread.php?t=2290118
T999V VLDLL1 Bootloader + Modem (Flashable .zip)
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
Correct. Once I flashed this my random reboots completely stopped.
Sent from my SGH-T999 using xda app-developers app

yanikd said:
Correct. Once I flashed this my random reboots completely stopped.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
I have same problem and same phone t-online Firmware is up to date but i rooted for first time with no problem but cyanagon wont instal status 7 error. Please help

The latest T999V firmware is VLDMF2. It's been out less than a week so many cm and aosp roms will not have added I to their asserts to allow install.
Downgrade to LL1 firmware for now and it should flash.
Or change the asserts in the updater script
Sent from my SGH-T999V using xda premium

DocHoliday77 said:
The latest T999V firmware is VLDMF2. It's been out less than a week so many cm and aosp roms will not have added I to their asserts to allow install.
Downgrade to LL1 firmware for now and it should flash.
Or change the asserts in the updater script
Sent from my SGH-T999V using xda premium
Click to expand...
Click to collapse
I have 4.1.2
Dunno i live in europe. thought firmware is different than us or so
First i used this i used "cm-10.1-20130716-NIGHTLY-d2tmo.zip" and "gapps-jb-20130301-signed" but Statuts 7 error than i tried : T999V_VLDLL1_noradio_v3 but there is also Status 7 error.
when i boot into recovery mods it says CWM-based Revovery v5.5.0.4 : : CF-v1.5 is this OK ?

yotaxd said:
I have 4.1.2
Dunno i live in europe. thought firmware is different than us or so
First i used this i used "cm-10.1-20130716-NIGHTLY-d2tmo.zip" and "gapps-jb-20130301-signed" but Statuts 7 error than i tried : T999V_VLDLL1_noradio_v3 but there is also Status 7 error.
when i boot into recovery mods it says CWM-based Revovery v5.5.0.4 : : CF-v1.5 is this OK ?
Click to expand...
Click to collapse
Well first thing you should do is update that old recovery. May be that's all you need.
The reason I mentioned the T999V firmware is because that's what the rest of the thread was for, so I assumed that's the model you had.
What model is your device? The T999 is a US only variant, the T999V is the Canadian variant. The European models should be the international ones, I9300.
If yours is international, do not flash anything you find here!
Sent from my SGH-T999V using xda premium

DocHoliday77 said:
Well first thing you should do is update that old recovery. May be that's all you need.
The reason I mentioned the T999V firmware is because that's what the rest of the thread was for, so I assumed that's the model you had.
What model is your device? The T999 is a US only variant, the T999V is the Canadian variant. The European models should be the international ones, I9300.
Sent from my SGH-T999V using xda premium
Click to expand...
Click to collapse
If yours is international, do not flash anything you find here!
i do not know if its internatianl oder t-mobile. but it should be t-mobile because starting the phone there is t-mobile logo and it is rent from t-mobile
anyway i installed new recovery 6. via google play but in recovery mode there is still Status 7. even its t-mobile. i can try every version because there is always status 7 so i can not damge phone installing wrong version i think. o the other hand i have always wipe chare/ factory before installing the cyanagenmod. i must restore data now and system setting by advanced backup thats kinda annoying. but next i should maybe try INT. now

If you don't know what model it is, don't flash anything!
Look under the battery.
Sent from my SGH-T999V using xda premium

They are adding the assert for T999VVLDMF2: http://review.cyanogenmod.org/#/c/45740/

[SOLVED!!]
i have this problem too when i want to install some roms like AOKP and JB 4.2.2 , i get same error !!
just go to recovery mode cwm then
go to mount and storage ---> unmount /system
now format /system and /data
try agian install cm rom , and it'l work :good:

HTC One
you guys got any ideas on the att M7 version of this problem. im almost positive i RUUd in order to flash CM but i couldnt get it to work. im on KitKat now cant get it to sideload or install from sd.
got any ideas?

[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.

(Q) can some help with this!!!!

Okay, Heres the thing. I was on TW Stock 4.3 Debloated Odex v1.0. I wanted to try something different plus the TW was getting old, so I wanted to go to a CM based ROM. I tried to flash Liquids ROM and it didnt go through. Ive tried Task's ROM and that didnt work. I want to try and flash the bootloaders but Im scared to brick my phone can someone give me some advice?

I personally have tried everything I know to flash something other than TW on my phone since I got it, with no luck finding anything that will flash and it never made any difference when I was on 4.1.1 or now that I am on 4.3, I really like my SIII but the lack of freedom enforced by Samsung and the carriers has turned me totally against Samsung, my next phone will be a Nexus 5, I am even having trouble with the TW roms I make with now with Android Kitchen, maybe someone else will be able to explain and why nothing, I can find that's being developed for I747M, in the 8 months I had this phone have not been able to find 1 working rom that will flash on the I747M, I am not in Canada though I am in Mexico
Sent from my SGH-I747M using Tapatalk

jimchee said:
I personally have tried everything I know to flash something other than TW on my phone since I got it, with no luck finding anything that will flash and it never made any difference when I was on 4.1.1 or now that I am on 4.3, I really like my SIII but the lack of freedom enforced by Samsung and the carriers has turned me totally against Samsung, my next phone will be a Nexus 5, I am even having trouble with the TW roms I make with now with Android Kitchen, maybe someone else will be able to explain and why nothing, I can find that's being developed for I747M, in the 8 months I had this phone have not been able to find 1 working rom that will flash on the I747M, I am not in Canada though I am in Mexico
Sent from my SGH-I747M using Tapatalk
Click to expand...
Click to collapse
My thing is, I flash a ROM containing 4.3 cause my phone has TWRP installed. I want to ODIN the bootloaders and see if I want can flash CM ROMs but I dont know if Ill brick my phone. which I hope I dont, Im not going to try it. I guess Im stuck on 4.3 till I figure out something

Ljdd said:
Okay, Heres the thing. I was on TW Stock 4.3 Debloated Odex v1.0. I wanted to try something different plus the TW was getting old, so I wanted to go to a CM based ROM. I tried to flash Liquids ROM and it didnt go through. Ive tried Task's ROM and that didnt work. I want to try and flash the bootloaders but Im scared to brick my phone can someone give me some advice?
Click to expand...
Click to collapse
"It didn't go through" is not giving us much information. You probably got an error, write it down.

polobunny said:
"It didn't go through" is not giving us much information. You probably got an error, write it down.
Click to expand...
Click to collapse
It didnt flash. I tried multiple times, but when I did Task's ROM, it kept saying bootloaders.

Ljdd said:
It didnt flash. I tried multiple times, but when I did Task's ROM, it kept saying bootloaders.
Click to expand...
Click to collapse
What bootloader do you have?

If I am not mistaken you have to update the bootloader to do it
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

I assume you have the canadian samsung s3 i747m.
I had this problem as well but I managed to do some digging and fix the problem. The problem was that the developers forgot to add I747MVLUEMK5 as a bootloader in the "updater-script". The updater script is responsible to make sure you don't flash the wrong rom with the wrong samsung model. Since i747mvluemk5 was not added, the phone failed the inspection. To solve this, add the bootloader "I747MVLUEMK5" into the d2att cyanogenmod zip file. Basically, this is what you do:
1) Download the d2att stable 10.2 cyanogenmod
2) unzip the d2att stable 10.2 cyanogenmod
3)And then open META-INF>com>google>android>updater-script
4)Once you found updater-script, open it with notepad
5)Then you must add this bootloader script since it is missing: || getprop("ro.bootloader") == "I747MVLUEMK5"
6)Obviously, don't just copy exactly like mine, but make sure I747MVLUEMK5 is there. Not sure, but i think you can delete one of the bootloaders such as I747MUMBLL1 and replace it with I747MVLUEMK5 instead.
7)after you made your change of the updater-script, rezip the files and flash it.

polobunny said:
What bootloader do you have?
Click to expand...
Click to collapse
I remember one of the 4.3 Roms needed to flash the boot loader, kernel and the Rom.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

I went to custom 4.4 ROM and never did the ota so I'm not really sure. Dig through the forums you'll find the solution.
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app

[Q] Need help. Can't get phone to boot.

Hey all, I've been in the android game for a long time now, so I'm not new to any of this, but this s3 here has me totally stumped.
It is my cousins (telus i747m), and we had it stock rooted 4.1.1 until yesterday.
I updated it to 4.3 with kies, and then he opted for a custom rom. So I flashed TWRP in Odin, and tried to flash gummy 4.4.2
It failed with a assert fail as well as a status 7. I tried old TWRP, New TWRP, Old CWM, New CWM, many different roms ranging from 4.3 and upwards. Still failing with the stupid status 7.
Kies no longer connects to the phone, so I can't restore through there. I will have to install through Odin and the download is horribly and painfully slow.
So is there any way to get a custom rom flashed? I have searched and no one seems to have an answer. Any help appreciated.

What assert failure were you getting?

I'd start back from scratch so go back to stock, then root and flash latest version of TWRP or CWM. Make sure when you flash a Rom it's for that specific device for example if its for the AT&T it's for the AT&T. Also make sure to do a factory wipe before installing any me roms
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app

xSharpi said:
I'd start back from scratch so go back to stock, then root and flash latest version of TWRP or CWM. Make sure when you flash a Rom it's for that specific device for example if its for the AT&T it's for the AT&T. Also make sure to do a factory wipe before installing any me roms
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
See my posts #2 & #5 here: http://forum.xda-developers.com/showthread.php?t=2585493

pc103 said:
See my posts #2 & #5 here: http://forum.xda-developers.com/showthread.php?t=2585493
Click to expand...
Click to collapse
Also see THIS post for a more detailed description of the updater-script and bootloader assert.