Hello everyone,
I am looking for any assistance with my problem. I was running CM 10.2 without any issues. I installed CM 11 M2 and began having LTE issue where download/upload speed is under 1mbps. I have been attempting to upgrade to newer versions of CM 11, however I keep getting “Status 7 error”
In an attempt to correct the problem I have done all the steps listed below, none of which have worked.
updated CWM recovery to 6.0.4.7
Edited the “Updater-Script” located in META-INF/com/google/android
a. Deleted everything from assert to first semi colon
b. Replaced M3 assert with assert from CM 11 Snapshot M2 (which included my baseband version)
c. Inserted my baseband version into CM 11 M3
Used ‘Toggle signature verification”
Selected ‘Fix Permissions” in CWM
Attempted CM 11 Nightlies dated after M3
Question- I have read that some users have had success using TWRP instead of CWM. However CWM backups wont work with TWRP. Is it worth the effort to transition to using only TWRP? I am considering flashing back to CM 10.2, then using TWRP to create a back up and then flash CM 11 M3.
I am using CWM version 5.5.3.7
Using a rooted GS3 on ATT (I747)
Current OS- CM 11-20140104-SNAPSHOT-M2-d2att
Baseband version- I747UCDLK3
I originally followed instructions listed here to backup/ root and flash my ROM- http://forum.xda-developers.com/showthread.php?t=2179330
Thanks in advance for any feedback.
I was in a similiar situation and this did the trick: http://forum.xda-developers.com/showthread.php?t=2321310
FWIW I updated bootloader AND modem to achieve LTE stability in my old daily driver (Slim) and install a newer CM variant. I believe only the bootloader is actually needed to get past your Error 7 Assert Failed situation.
Ghostnyc said:
Hello everyone,
I am looking for any assistance with my problem. I was running CM 10.2 without any issues. I installed CM 11 M2 and began having LTE issue where download/upload speed is under 1mbps. I have been attempting to upgrade to newer versions of CM 11, however I keep getting “Status 7 error”
In an attempt to correct the problem I have done all the steps listed below, none of which have worked.
updated CWM recovery to 6.0.4.7
Edited the “Updater-Script” located in META-INF/com/google/android
a.Deleted everything from assert to first semi colon
b.Replaced M3 assert with assert from CM 11 Snapshot M2 (which included my baseband version)
c.Inserted my baseband version into CM 11 M3
Used ‘Toggle signature verification”
Selected ‘Fix Permissions” in CWM
Attempted CM 11 Nightlies dated after M3
Question- I have read that some users have had success using TWRP instead of CWM. However CWM backups wont work with TWRP. Is it worth the effort to transition to using only TWRP? I am considering flashing back to CM 10.2, then using TWRP to create a back up and then flash CM 11 M3.
I am using CWM version 5.5.3.7
Using a rooted GS3 on ATT (I747)
Current OS- CM 11-20140104-SNAPSHOT-M2-d2att
Baseband version- I747UCDLK3
I originally followed instructions listed here to backup/ root and flash my ROM- http://forum.xda-developers.com/showthread.php?t=2179330
Thanks in advance for any feedback.
Click to expand...
Click to collapse
You're on the lk3 bootloader and modem, you need newer bootloaders try the MJ2 bootloader and the MJB modem. Avoid the MJB bootloader until necessary once you flash it you're stuck forever without Odin.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
theramsey3 said:
You're on the lk3 bootloader and modem, you need newer bootloaders try the MJ2 bootloader and the MJB modem. Avoid the MJB bootloader until necessary once you flash it you're stuck forever without Odin.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the quick response
I'm a relative newbie at this, but after looking into the bootloader as per your suggestion I have 2 questions
In CM 11 M3 updater script- my bootloader is listed in the asserts. This means it is supported, correct?
You suggested updating to MJ2, however I only found MG2, is this an appropriate bootloader to use?
jasapper said:
I was in a similiar situation and this did the trick: http://forum.xda-developers.com/showthread.php?t=2321310
FWIW I updated bootloader AND modem to achieve LTE stability in my old daily driver (Slim) and install a newer CM variant. I believe only the bootloader is actually needed to get past your Error 7 Assert Failed situation.
Click to expand...
Click to collapse
Thanks this worked for me and I was able to updated to the latest nightly on my i747m
idzy said:
Thanks this worked for me and I was able to updated to the latest nightly on my i747m
Click to expand...
Click to collapse
I need some clarification before I proceed - do I reinstall LK3 or install the next one in line which would be MG2.zip?
Ghostnyc said:
I need some clarification before I proceed - do I reinstall LK3 or install the next one in line which would be MG2.zip?
Click to expand...
Click to collapse
Are you getting assert errors (error 7) while trying to flash a new rom ?? if so, look at the list that is shown in the error when you try to install. Only upgrade the bootloader as far as you need to get a good install... also be sure that the bootloader you flash (if needed) is for your model of phone. I747 = AT&T. I747M is Canadian (Telus, Bell, Rogers....) I recently had to upgrade my bootloader to install 3.3 Quantum rom... went with MF1 Canadian bootloader as MK5(newest) will not let you downgrade without bricking your phone.....
Try the MJ2 (leaked 4.3 bootloader with no knox and you can downgrade with desktop Odin to whatever you want) it might be in the bootloader thread if not it is in the development section just search for MJ2.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
theramsey3 said:
Try the MJ2 (leaked 4.3 bootloader with no knox and you can downgrade with desktop Odin to whatever you want) it might be in the bootloader thread if not it is in the development section just search for MJ2.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
I finally got a moment to update my bootloader to MG2 and install CM11 M3 and both were done successfully. However I am still experiencing issue with LTE speeds crawling under 1mbps.
I have been researching this issue and on cyanogenmod forums someone mentioned that it could be a radio issue (RIL- Radio Interface Layer).
Does anyone have any thoughts or experience with this?
Related
As soon as I try to flash CM 10.2 to my phone I get this error assert failed getprop( ro.bootloader ) l710. Does anyone know how to fix this?
agonizing said:
As soon as I try to flash CM 10.2 to my phone I get this error assert failed getprop( ro.bootloader ) l710. Does anyone know how to fix this?
Click to expand...
Click to collapse
are you running the MD4 firmware?
(if you've taken the mk3 update, do not try to flash md4. you'll brick your phone)
jdelano said:
are you running the MD4 firmware?
(if you've taken the mk3 update, do not try to flash md4. you'll brick your phone)
Click to expand...
Click to collapse
MD4 should be a recognized bootloader in the updater-script for CM 10.2, which makes me think he probably has MK3. Removing the assert lines altogether will prevent an error involving the bootloader check, as long as it is a d2spr ROM (i.e. don't remove them from a ROM meant for a different carrier and then try to flash, bad things will happen, that is why the asserts are there in the first place). MK3 is included in the asserts for the new CM 11 builds by the way.
A point of clarification as well. Flashing is fine, there are no bootloader changes involved, it is when you try to push a .tar "return to stock" file via Odin which is designed to restore a non-Knox bootloader that causes major damage if you already have a phone cursed by the Knox bootloader. Therefore, if you are already OTA'd to the MK3 with Knox bootloader, DO NOT, under any circumstances, push a .tar that is based on the MD4 bootloader.
Mr. Struck said:
MD4 should be a recognized bootloader in the updater-script for CM 10.2, which makes me think he probably has MK3. Removing the assert lines altogether will prevent an error involving the bootloader check, as long as it is a d2spr ROM (i.e. don't remove them from a ROM meant for a different carrier and then try to flash, bad things will happen, that is why the asserts are there in the first place). MK3 is included in the asserts for the new CM 11 builds by the way.
A point of clarification as well. Flashing is fine, there are no bootloader changes involved, it is when you try to push a .tar "return to stock" file via Odin which is designed to restore a non-Knox bootloader that causes major damage if you already have a phone cursed by the Knox bootloader. Therefore, if you are already OTA'd to the MK3 with Knox bootloader, DO NOT, under any circumstances, push a .tar that is based on the MD4 bootloader.
Click to expand...
Click to collapse
I'm a newbie at this kind of stuff but yes i do have mk3. So can i not flash to cm 10.2? Or what do I have to do to get the flash to work properly?
agonizing said:
I'm a newbie at this kind of stuff but yes i do have mk3. So can i not flash to cm 10.2? Or what do I have to do to get the flash to work properly?
Click to expand...
Click to collapse
Flashing 10.2 is perfectly fine, or any other custom ROM for that matter. Remember, Android build number has nothing to do with your boot loader version. I will post later for you a link to instructions on how to modify or delete the assert lines to enable flash of CM 10.2, or I would also recommend just go straight to CM 11 official version, your boot loader is recognized by the newest updater-script. Let me know your preference.
Mr. Struck said:
Flashing 10.2 is perfectly fine, or any other custom ROM for that matter. Remember, Android build number has nothing to do with your boot loader version. I will post later for you a link to instructions on how to modify or delete the assert lines to enable flash of CM 10.2, or I would also recommend just go straight to CM 11 official version, your boot loader is recognized by the newest updater-script. Let me know your preference.
Click to expand...
Click to collapse
I got CM 11 to work last night, but it was too unstable for me. I'd rather use CM 10.2 since its a stable version. So can you teach me how to remove the assert lines?
agonizing said:
I got CM 11 to work last night, but it was too unstable for me. I'd rather use CM 10.2 since its a stable version. So can you teach me how to remove the assert lines?
Click to expand...
Click to collapse
http://androidforums.com/virgin-mobile-galaxy-s3-all-things-root/791952-all-in-one-guide-modifying-custom-sprint-roms-virgin-mobile-use.html
This link is for a tutorial I posted on Android Forums for the use of my fellow Virgin Mobile users who want to use Sprint ROM's. Ignore the VM specific items; the principle, though is universal in terms of modifying or deleting the assert lines once you know where to look for them. I would recommend just deleting that set of lines altogether, but if you want to replace one the current Sprint bootloader is L710VPUCMK3. Previous version of MD4 is already listed in the asserts if that happens to be your bootloader for anyone else interested, which would mean no modification needed. Too bad about CM 11, I have been running it since the official versions started being built, and it is beyond awesome for me. Currently on the first build for 4.4.2 from 12/12, with the newest test build of dkp kernel from 12/13 as well, and everything works virtually flawlessly.
I was on CM10 and noticed that OTA CM updates no longer work. So as usual, I installed the latest TWRP, downloaded the latest CM11 nightly and proceeded to install. Every time I get an error.. something about bootloader. There is no need for me to update my bootloader because I already have the correct one. I checked.
I thought maybe the problem is TWRP and tried Clockwork. Same error. assert failed: getprop("ro.bootloader")... and then it lists differnt I747 models... then gives (Status 7) on the bottom
Why cant I update to CM11?
Thanks.
If it helps my bootloader is I747UCDLK3.
I was about to ask this same question. I am unable to flash any 4.4 rom... Am currently using task AOKP 10/31 and wanted to try kit kat.
Every 4.4 rom has failed to flash. I tried flashing the new modem in the cm thread as well... What am I missing?
Sent from my SGH-I747 using xda app-developers app
Try installing with CWM and check the CM11 updater script to make sure your bootloader is supported.
You need to make sure that your exact bootloader is listed in the asserts or it will error out... If your bootloader is not listed, then you need to upgrade to a bootloader that is in the list.. one compatable with your model... recommend only upgrading as far as you need to... careful with some of the latest bootloaders as they will brick your phone if you later try to downgrade...
I believe you need to update your bootloader for a KitKat ROM. Look for I747UCDMG2.
I figured it out. I updated to the latest cwm version and everything worked fine. Running liquid smooth now.
Sent from my SGH-I747 using xda app-developers app
I am trying to flash GS3 (Canadian Rogers unlocked) i747m with cm10.2 d2att from SD through Philz Touch, but my install fails half thru "Installation aborted, please update binary"
I made 2 backups to SD card, so I easily recovered back, but trying to understand what has happened, first time doing it, and I am not sure why. Please help.
Model: SGH-I747M
Android: 4.4.2
Baseband: I747MVLUFNF2
Kernel: 3.4.0-1784548
Build: KOT49H.I747MVLUFNF2
Any particular reason you want cm10.2? Since you are on a KK bootloader and modem, I would go with a cm11 install for the d2lte.
Is your recovery up to date?
audit13 said:
Any particular reason you want cm10.2? Since you are on a KK bootloader and modem, I would go with a cm11 install for the d2lte.
Is your recovery up to date?
Click to expand...
Click to collapse
Only reason was that 10.2 is stable release and I wasn't sure if cm11 is compatible with my bootloader.
Philz Touch 6 Recovery , I believe was the last build for d2lte I found.
Philz Touch 6.48.4 ClockworkMod v6.0.5.0
Not sure why you're getting that error. CM10.2 is basically JB while CM11 is KK.
I suggest trying CM11.
audit13 said:
Not sure why you're getting that error. CM10.2 is basically JB while CM11 is KK.
I suggest trying CM11.
Click to expand...
Click to collapse
Thanks,
I tried cm11 and install was flawless.
Hi, I'm having issues flashing roms which aren't based off of 4.1.2 firmware. I am rooted on 4.1.2 JB and have flashed a few of the 4.1.2 roms on my tmobile s3 t999, when I attempt anything else it fails with "error 7" for example cm10 and 11 or 4.3/4.4. Please Help? Thanks.
1. Make sure you're on latest version of recovery.
2. You may need to ODIN to a newer version/bootloader.
ShernDog said:
1. Make sure you're on latest version of recovery.
2. You may need to ODIN to a newer version/bootloader.
Click to expand...
Click to collapse
I tried flashing over the bootloader update found here. http://forum.xda-developers.com/showthread.php?t=2282603
and am receiving a "status 7" error once again. I restored a backup which contained no mods, downloaded rootkeeper and booted into cwm tried flashing the updated zip, it returned a status 7 error. I'm not sure how to proceed. I am currently using 4.1.2 axis with trinity kernel. I cant seem to flash anything whatsoever aside from roms based off 4.1.2. Can someone help me step-by-step?
thanks
Update recovery
thanks guys. Success!!!
Hello,
Trying to install the custom ROM cyanogen mod 11.
http://forum.xda-developers.com/showthread.php?t=2682905
First time I ever attempt to flash a custom rom.
In the guide it asks to DL Bootloader & Modem. My baseband is:
I747MVLUFOB3
I can't find any baseband corresponding to this one.
Here I found a firmware that correspond to my base band.
http://www.sammobile.com/firmwares/database/SGH-I747M/
Not sure if it is useful...
Any way to install the custom room??
Cheers
Just a nickname said:
Hello,
Trying to install the custom ROM cyanogen mod 11.
http://forum.xda-developers.com/showthread.php?t=2682905
First time I ever attempt to flash a custom rom.
In the guide it asks to DL Bootloader & Modem. My baseband is:
I747MVLUFOB3
I can't find any baseband corresponding to this one.
Here I found a firmware that correspond to my base band.
http://www.sammobile.com/firmwares/database/SGH-I747M/
Not sure if it is useful...
Any way to install the custom room??
Cheers
Click to expand...
Click to collapse
Which variant of the galaxy s3 do you have? You should be able to flash any ROM compatible with your phone using TWRP or Phil touch recovery.
I have the i747m (rogers canada). I have TWRP 2.8.7.0 & rooted with Kingo root. Somehow it was the only way to root it. Tried Towel root & odin but both were doing nothing.
TWRP was installed a long time ago. I recently made an update on kies (what a mistake sign...). I was on 4.4.2 before and after the firmware update on kies.
I got a spare S3 motherboard (with cpu etc.) I might try on that one first but I need to disassemble & assemble everything... not very tempting.
I usually just use odin and http://www.sammobile.com/firmwares/ to start fresh and root again when I want to upgrade bootloader and modems.
As you saw at sammobile, OB3 is the latest official release for the i747. You do not need to do anything to your baseband (modem) to run CM11. You may want to verify that your bootloader (firmware) matches the modem. This can be done from within TWRP. Go to the advanced menu and in the terminal enter
Code:
getprop ro.bootloader
You should get a return ending in OB3.
I suspect the CM 11 updater-script has not been updated to account for the just released OB3 firmware. If that is the case, you could always edit the script in the roms zip file.
@dawgdoc
When I entered the command, it returned me:
I747MVLUFOB3
Secondly, I have not tried to install CM11 (or the newer version CM12?). I do not know if it works. I just want to make sure I can flash and not brick my phone.
My phone is not the d2att (i747), it is d2can (i747m). I believe these two are very similar but enough different to cause problem.
So, can I install CM11 or 12?
You are talking about changing a zip file... The newb I am know how to do that, but what exactly - that he doesn't know. So I would rather not mess with that. I guess TWRP checks if the firmware of the bootloader / modem matches to those from a compatible list and simply updating that list would allow me to install the build?
I was thinking about this ROM:
http://forum.xda-developers.com/galaxy-s3-att/development/unofficial-cyanogenmod-12-t2968854
Don't know the exact difference with the CM12 but it says d2can.
However, the BaNkS GAPPS - GAPPS link does not work... I don't know what that is.
Just a nickname said:
@dawgdoc
When I entered the command, it returned me:
I747MVLUFOB3
Secondly, I have not tried to install CM11 (or the newer version CM12?). I do not know if it works. I just want to make sure I can flash and not brick my phone.
My phone is not the d2att (i747), it is d2can (i747m). I believe these two are very similar but enough different to cause problem.
So, can I install CM11 or 12?
You are talking about changing a zip file... The newb I am know how to do that, but what exactly - that he doesn't know. So I would rather not mess with that. I guess TWRP checks if the firmware of the bootloader / modem matches to those from a compatible list and simply updating that list would allow me to install the build?
I was thinking about this ROM:
http://forum.xda-developers.com/galaxy-s3-att/development/unofficial-cyanogenmod-12-t2968854
Don't know the exact difference with the CM12 but it says d2can.
However, the BaNkS GAPPS - GAPPS link does not work... I don't know what that is.
Click to expand...
Click to collapse
The unofficial CM12 -5.1.1 by @matrixzone is good for the i747M, aka d2can. If you have any doubts, ask on that thread if it is updated to run on OB3? Matrixzone is active on the forums and should respond to your question. Also I just checked the updater-script for the latest CM11 official nightly and it is set up to run on the i747M.
So, either should run with no problems for you.
What is the bootloader and modem version needed and how do I get them without getting a locked bootloader? I'm on i747M with 4.1.1 Stock rom with DLK4 modem and bootloader. There are newer bootloaders and modems that can be flashed through recovery but some people have been getting bricks when messing with bootloader.
THey say to use Official firmwares to have it update the bootloaders but which one is the proper firmware version to get the proper bootloader and modem version to allow DATA 4g LTE after flashing CM12.1 Lollipop rom?
Chupacabra117 said:
What is the bootloader and modem version needed and how do I get them without getting a locked bootloader? I'm on i747M with 4.1.1 Stock rom with DLK4 modem and bootloader. There are newer bootloaders and modems that can be flashed through recovery but some people have been getting bricks when messing with bootloader.
THey say to use Official firmwares to have it update the bootloaders but which one is the proper firmware version to get the proper bootloader and modem version to allow DATA 4g LTE after flashing CM12.1 Lollipop rom?
Click to expand...
Click to collapse
I see audit13 is helping you in the other thread, therefore I will not confuse things and also reply here.
dawgdoc said:
I see audit13 is helping you in the other thread, therefore I will not confuse things and also reply here.
Click to expand...
Click to collapse
But the newest firmware is bad because it has evil bootloader.
Chupacabra117 said:
But the newest firmware is bad because it has evil bootloader.
Click to expand...
Click to collapse
Check my long post over there.