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.
Related
I rooted my Bell Galaxy SIII this afternoon using Mr. Robinsons method.
All good. Have root. Installed CWM (LTE Variant and other newer listed on Mr. Robinsons thread. One at a time, same error)
Booted into recovery and tried to install CM10 after factory reset, dalvick wipe, yada, yada yada.
I get the error:
Assert Failed: getprop("ro.product.device*) =="E:Error in /SDCARD/cm-10-20120912-nightly-d2Att.zip (Status 7)
Might be some left out as not all of the error code is shown.
Tried multiple times to download CM using different browsers and directly on the phone.
I am able to restore factory rooted image no problem.
I then installed TWRP v2.2.2.0
Same error when trying to install CM10-current nightly
I'm assuming that this is related to device ID and I'm trying to install ROM's not suitable for it?
I've tried with AOKP version from Task and get same error.
http://forum.xda-developers.com/showthread.php?t=1766684
Pretty sure these are good for Bell version....
Any idea's or confirmation that these won't work with my phone.
Thanks
Mike
You need cwm 6.0.1.2
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Not sure what the issue is but I can tell you that I have installed task aokp with twrp and cwm recovery versions back to 5.5.0.4 with no problems on my Bell phone.
liltitiz said:
You need cwm 6.0.1.2
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Thanks,
Just so I learn something out of this...Why do I need this? I understand that both versions of CWM and TWRP I installed are used by people with the same hardware?
Just want to understand what I am missing.
Thanks,
Mike
EDIT: Okay, after doing some looking at the Build.prop file I see I have a D2Cann and the rom is listed as for D2ATT so the assumption I'm making is the older recoveries match that and won't proceed while CWM 6.012 doesn't? I'm downloading and going to install the latest CWM now to try and confirm this. Still not sure why this has worked for some people and not for me unless they are changing their build.prop but I haven't been able to find that to confirm it.
If you go in the cm10 thread in original developpenent, they specify which recovery to install with a link to download it.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
mikewestlake said:
EDIT: Okay, after doing some looking at the Build.prop file I see I have a D2Cann and the rom is listed as for D2ATT so the assumption I'm making is the older recoveries match that and won't proceed while CWM 6.012 doesn't? I'm downloading and going to install the latest CWM now to try and confirm this. Still not sure why this has worked for some people and not for me unless they are changing their build.prop but I haven't been able to find that to confirm it.
Click to expand...
Click to collapse
its not the recovery that does the actual check for the device. it's the assert in the updater-script of the rom that you're trying to flash. CM10 checks for "d2att" and if thats not what in your build.prop it will error out and refuse to flash. Either remove that line from the updater-script or edit your build.prop.
Also. you need to try your best to read the OPs of the roms you're thinking about flashing. In the CM10 thread they even give you the information of which recovery you need to use and where to get it.
task650 said:
its not the recovery that does the actual check for the device. it's the assert in the updater-script of the rom that you're trying to flash. CM10 checks for "d2att" and if thats not what in your build.prop it will error out and refuse to flash. Either remove that line from the updater-script or edit your build.prop.
Also. you need to try your best to read the OPs of the roms you're thinking about flashing. In the CM10 thread they even give you the information of which recovery you need to use and where to get it.
Click to expand...
Click to collapse
Thanks,
yeah, in this case, I thought I read everything and maybe got too much info. Still for coming from other devices (HTC DesireZ, Legend, couple of Asus transformers), having different device versions is a new step to tick off and learn.
Had the same issue with your rom too. Can I ask that you add a note to the OP about making sure Canadian versions change the build prop or only use CWM 6 cause I had the same issue with yours when trying to install. I'm not going to be the only guy that missed this.
Gonna install CWM 6 and change build prop to install your ROM. It looks good.
Thanks again.
Mike
mikewestlake said:
Thanks,
yeah, in this case, I thought I read everything and maybe got too much info. Still for coming from other devices (HTC DesireZ, Legend, couple of Asus transformers), having different device versions is a new step to tick off and learn.
Had the same issue with your rom too. Can I ask that you add a note to the OP about making sure Canadian versions change the build prop or only use CWM 6 cause I had the same issue with yours when trying to install. I'm not going to be the only guy that missed this.
Gonna install CWM 6 and change build prop to install your ROM. It looks good.
Thanks again.
Mike
Click to expand...
Click to collapse
Using ROM Manager helps you keep your CWM recovery up to date. You can find the app in the play store
-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-
Sent from my SAMSUNG-SGH-I747 CM10 + KT747, 96-2106 MHz, noop, ktoonservative, undervolted, 3150mAh battery.
Thanks to: Ktoonsez, Task650 and Cyanogen for their amazing works!
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?
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?/:
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
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