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
Related
Hi, I'm sort of new to this so I'm just wondering if I need to flash CM10.1 when I install it?
I'm currently running CM10 and installing the OTA nightly versions and those don't need to be flashed, or so I was told. They work fine.
So I decided to check for updates and there was 10.1 available, so I'm just wondering that if I got the OTA update and installed it, would I need to to anything else?
Thanks for the help
Yes, you need to have hboot version higher or equal to 1.28.
You also need to flash the boot.img and do a full wipe before flashing.
Flash new 4.2.2 gapps as well.
Sent from my One X using xda premium
So I rooted my phone and installed the latest CWM recovery but every time I try to install any custom rom I get a status 7 error and it says something along the line of asserts failed ro.product.drvice == d2att. I've tried using TWRP, I've unrooted and installed stock, nothing seems to work. Last week I was running Jellybam fine for about 2 days, got stuck in bootloop, tried numerous ways to fix it, ended up returning to stock but now I cannot flash anything. Help me please
The status 7 error happens when the ROM ur about to flash, checks to see if the model of ur phone is compatible with said ROM. Its a good thing(safety mechanism) but can be a pain at the same time. What version of cwm are u using? Download the latest cwm recovery thru the ROM manager app and that can sometimes fix the issue. What ROM are you trying to install?
Sent from my SAMSUNG-SGH-I337 using xda premium
I think 6.0.2.3? not 100% sure though.. and I need to be rooted in order for rom manager to work... I tried using it but it kept saying the flash failed.. I'm using the root recovery. I've tried flashing CM 10.1 and RC5 as well as the latest and 3 before that Jellybam Roms
shewantsmyduck said:
I think 6.0.2.3? not 100% sure though.. and I need to be rooted in order for rom manager to work... I tried using it but it kept saying the flash failed.. I'm using the root recovery. I've tried flashing CM 10.1 and RC5 as well as the latest and 3 before that Jellybam Roms
Click to expand...
Click to collapse
Latest cwm is at 6.0.3.1
I think you're getting a little confused.
You need to be rooted to have any custom recovery installed, so right off the bat you are rooted. You shouldn't flash anything with rom manager, it can cause serious harm to your phone. Tom manager is best for just updating your recovery.
There are two main reasons for a status7 error, out of date recovery or an out of date bootloader.
Update your recovery to 6.0.3.1 and he to flash it again, if it comes back you'll need to update your bootloader a two second search in these threads will provide you with a large handful of threads where people had identical issues as you
Sent from my SGH-I747 using xda app-developers app
Checked my bootloader and it says i747UCDLK3 and I think that's the latest... I'll root and install latest CWM through rom manager once I get home
And one question though... I tried using TWRP 2.5 (the latest) and I still got the status 7 error...?
shewantsmyduck said:
So I rooted my phone and installed the latest CWM recovery but every time I try to install any custom rom I get a status 7 error and it says something along the line of asserts failed ro.product.drvice == d2att. I've tried using TWRP, I've unrooted and installed stock, nothing seems to work. Last week I was running Jellybam fine for about 2 days, got stuck in bootloop, tried numerous ways to fix it, ended up returning to stock but now I cannot flash anything. Help me please
Click to expand...
Click to collapse
Can you flash any stock modded rom's ? You state you went back to stock but what method did you use to go back to stock ?
Why oh why were you using jellybam...
My cousin has it on his Verizon GS3 and it works perfectly fine so I thought I'd give it a shot. To go back to stock I followed some unroot and return to stock I found online.. not sure of the link. It basically consisted of flashing it in Odin and returned it back to stock 4.0.4 which I then updated to 4.1.1 using att ota. I'm not sure if it was a a modded stock rom or not. And I really don't feel like going back through that mess again only to flash it and get stuck in another boot loop I want to be pretty positive that it will work :/
shewantsmyduck said:
My cousin has it on his Verizon GS3 and it works perfectly fine so I thought I'd give it a shot. To go back to stock I followed some unroot and return to stock I found online.. not sure of the link. It basically consisted of flashing it in Odin and returned it back to stock 4.0.4 which I then updated to 4.1.1 using att ota. I'm not sure if it was a a modded stock rom or not. And I really don't feel like going back through that mess again only to flash it and get stuck in another boot loop I want to be pretty positive that it will work :/
Click to expand...
Click to collapse
The ODIN flash to stock 4.0.4 probably installed the old ics bootloaders, and the ota update to 4.1.1 may not have included the new jb bootloaders.
Ok so what is the newest bootloader? I downloaded the root checker that allows you to see your bootloader version and it's on i747UCDLK3.
shewantsmyduck said:
Ok so what is the newest bootloader? I downloaded the root checker that allows you to see your bootloader version and it's on i747UCDLK3.
Click to expand...
Click to collapse
That's the right one
Sent from my SGH-I747 using xda premium
So what should I do now then :s
You're trying to flash the wrong rom for your device, or you're not using the right recovery for your device. What Galaxy S3 model do you have? On which carrier are you and where did you buy the phone?
I have an AT&T i747 that I got at an AT&T store. The Rom is correct as I've downloaded it numerous times and I've tried the latest TWRP recovery and still received the error.
I'm going to try and flash a factory image tomorrow from the development section and root afterwards. As Michael3214 pointed out in a pm, the issue may be that my phones id has changed, hopefully a factory image will fix that.
Hello,
I'm new to rooting and I softbricked my phone last night. After reading Docs thread on the t-mobile sgh-t999l I was able to restore it to the factory settings.
I am currently running jellybean 4.3. My phone is rooted and I downloaded a CWM custom and flashed it through ODIN (computer).
When I try and install any custom roms through boot recovery I get a status 7 error code. Ive tried everything that Ive read in the other threads as far as readjusting the scripts etc.
Device info:
Baseband Version
T999LUVUBMK4
Kernel
3.031-210647
The phone itself is a T-Mobile refurbish but it might have been a sprint buy back.
When I opened the scripts for the PACMAN installer my UVUBMK wasnt even listed, so I'm not sure whether that is even an issue.
Any help is appreciated.
This seems like an awesome forum and I appreciate everyones input.
Donny
Can i just add my baseband, T999LUVUBMK4, into the script?
D
Flash the latest recovery ?
Sent from my SGH-T999 using xda app-developers app
Sorry for not fully understanding....
What recovery?
I've got the latest nightly of the PAC rom. I updated my CWM to the latest version as well.
Thanks
Donny
So I reset my phone at stock, ran superuser and disabled knox.
Flashed the latest TWRP and tried to reflash the zip.
It hangs on the asserts.
If I try and flash the file with the asserts deleted it wont work either.
Any help?
D
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?
Hello all. I just received a galaxy s3 from my sister in law running 4.4.2. I am aware I can't downgrade the complete firmware using Odin. The phone it's rooted. My question is what can I do with this thing as far as playing with roms and what not? Can I only install 4.4.2 based roms? Can I even unroot? I have been rooting and installing roms for years now but never have a phone felt more unfriendly before this. Thanks in advance.
Is the phone running stock 4.4.2?
You can install a custom recovery to the phone, copy some custom ROMs to an external SD card, and try out a bunch of ROMs.
Yeah its stock 4.4.2 rooted with clockwork mod recovery. Do the roms have to be 4.4 or 4.4.2 based? Tried cyanogenmod 4.3 and failed. I pretty much would like to flash via odin to go back to stock unrooted but 4.4.2 was over the air. Got 4.3 via sammobile but that fails. Kies won't show my device for firmware recovery. Shows it as normal to sync.
What error did you get when trying to flash CM10.2? Is your CWM up to date?
I would have assumed that CM10.2 would be comaptible with your KK bootloader and modem.
Do not make anymore attempts to flash 4.3 via Odin. This could result in a bricked phone because a KK modem on a 4.3 bootloader cannot be fixed using any method available on XDA.
Yeah I'm aware of the boot loader and modem downgrade issue. Tried odin once and just left it as is.
Is your CWM up to date? What error did you get when trying to flash CM10.2?
I don't remember the error. According to Rom manager, my recovery is up to date
What version is the cwm? I prefer to manually flash a custom recovery instead of relying on ROM manager.
Cwm 6.0.4.7. I've always used rom manager except for my galaxy nexus. Flashed with windows terminal and fastboot.
Since CWM is up to date, try flashing the most recent CM11.
Older cm roms, and any older roms should run fine on NE4. Some may not flash though, such as cm10. This is because the updater script doesn't include NE4 as it wasn't out when the rom was built. If you edit the script to make it flash, any of the available roms should run just fine.
As it stands though, the easiest thing would be to do as audit13 suggested and flash cm11. That and most other recent roms should flash just fine w/o any extra work.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
well, after downloading the most recent cm11 nightly and gapps, rebooted into recovery and wiped. when trying to flash cm11, sd card not mounting. couldn't mount, restored a backup only to be greeted to a display that would not go to sleep and a fury of app and processes stopping pop ups. settings-accounts-backup and reset-factory data reset-etc did nothing but ask for a password. did it through recovery to a perfectly working phone with baseband version: unknown, IMEI: unknown, IMEISV: unknown. flashed the NE4 modem Doc posted in another forum, no dice. same message from cm as before. this time i remember. it was a bunch of basebands not including NE4.
And getprop ro.bootloader says NE4. first said unknown but maybe i typed it wrong.
Got it all back running. tried the S3Rx NE4 aroma zip that would end with installation aborted. found enewman17's post on updating using a stock-rooted 4.4.2 zip after flashing Doc's modem zip. all is well! So thank you DocHoliday77, and thank you enewman17!
Glad you got it working!
Sent from my SAMSUNG-SGH-I747 using Tapatalk