• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [Boost Mobile] Official CyanogenMod 11 Nightlies!

Your question is still useful for anyone else reading this.

1. Modem is personal choice. Also remember modem does not equal bootloader, it is just a way to access phone service and data. I am currently using MK5, MG2 was solid as well, and I have used the MK3 from Sprint no problem.

2. SELinux was introduced in 4.3, and was set to "Permissive" by default. In 4.4, the default is "Enforcing," which can mess with some root apps and their functionality unless it is manually set back to "Permissive." Think of it as Google's very light version of Knox, I can't think of any other comparison right now. My attempt to modify build.prop didn't stick, and I think this is an intentional design issue to prevent direct modification, as I have read about others having the same issue. To manually change: Open Terminal Emulator, and give it root access with the command "su" (don't use quotes), followed by the enter key. On the next line you will see it starts with # instead of $, this means root has been granted. On that next line, type "setenforce 0" (again, no quotes, and that is a zero not the letter O; this is just basic 0 or 1 meaning true or false in computer-land) and then hit enter key again. Make sure to close the program entirely after that or it will run in the background and consume battery. This has to be done after every reboot due to "Enforcing" being part of the build.prop.

SELinux has only given me problems a couple of times, so this is just more of a nerd thing than anything else, but I always feel there is no such thing as too much knowledge.

Just a follow up bro. I haven't set SELinux to permissive. I just check stats in About Phone and SELinux is set to enforcing. I haven't had any problems with it though. Apps ask for SU permission and have been granted each time with no noticeable ill effects.

What type of issues would it being set to enforce would I see? Thanks.
 
Just a follow up bro. I haven't set SELinux to permissive. I just check stats in About Phone and SELinux is set to enforcing. I haven't had any problems with it though. Apps ask for SU permission and have been granted each time with no noticeable ill effects.

What type of issues would it being set to enforce would I see? Thanks.

If you try to change certain things in /system it won't stick on reboot.
 
It's crazy they make so many nightlies. Oops maybe that's why they're called nightlies lol. Another one is up 12-16-2013 gummy
 
Hmmmmmm...did the debloated one, saw missing apps, got scared and flashed bloated one but due to user error I did a dalvik wipe and wipe cache partition in cwm thinking it would fix the issue of my phone not recognizing my ringtones, alarm tones, notifcations and that made me somehow have no signal at all.

Reflashed back to debloated and flashed gapps because I finally understood how DAT STUFF WORKZ. Use file manager to select tones for alerts. Stock media thingy doesn't work even when changing file to .ogg.

One thing I noticed on my way to work today is I had no data connection out in the street. I'm a little scared. Will check on it throughout the day. I don't think the signal was great either.
 
Just a follow up bro. I haven't set SELinux to permissive. I just check stats in About Phone and SELinux is set to enforcing. I haven't had any problems with it though. Apps ask for SU permission and have been granted each time with no noticeable ill effects.

What type of issues would it being set to enforce would I see? Thanks.

Just a follow-up to Rxpert's response I had apps fail to open and then received a toast notification about SELinux blocking something. It only happened probably two or three times, and once for sure it was ES File Explorer, but that was also early days of CM11.
 
Hmmmmmm...did the debloated one, saw missing apps, got scared and flashed bloated one but due to user error I did a dalvik wipe and wipe cache partition in cwm thinking it would fix the issue of my phone not recognizing my ringtones, alarm tones, notifcations and that made me somehow have no signal at all.

Reflashed back to debloated and flashed gapps because I finally understood how DAT STUFF WORKZ. Use file manager to select tones for alerts. Stock media thingy doesn't work even when changing file to .ogg.

One thing I noticed on my way to work today is I had no data connection out in the street. I'm a little scared. Will check on it throughout the day. I don't think the signal was great either.

Don't know if you've seen the advice before, but make a backup of current OS in recovery, flash back to a TouchWiz ROM, update PRL and profile, then back to your CM11 backup. Also, there are APN fixes needed in order to make data/MMS work for VM and Boost users piggybacking off of Sprint ROM's. Wetbiker7 has a sticky thread with all that info available; I am on VM so the APN fix is slightly different, one of the rare times we don't share a common fix. On the plus side, I haven't had to flash the zip with the fix for VM since coming to CM11, the settings have finally stuck, at least with dirty flashing.
 
Don't know if you've seen the advice before, but make a backup of current OS in recovery, flash back to a TouchWiz ROM, update PRL and profile, then back to your CM11 backup. Also, there are APN fixes needed in order to make data/MMS work for VM and Boost users piggybacking off of Sprint ROM's. Wetbiker7 has a sticky thread with all that info available; I am on VM so the APN fix is slightly different, one of the rare times we don't share a common fix. On the plus side, I haven't had to flash the zip with the fix for VM since coming to CM11, the settings have finally stuck, at least with dirty flashing.

The settings stuck for me too bro.

Also, good news so far on the SELinux set to enforce, I haven't had any issues with my rooted apps at all. Titanium, Root Explorer, KTweaker, Quickboot apps, etc are fully functional with no SELinux errors. Looking good bro.... looking very good! :D
 
The settings stuck for me too bro.

Also, good news so far on the SELinux set to enforce, I haven't had any issues with my rooted apps at all. Titanium, Root Explorer, KTweaker, Quickboot apps, etc are fully functional with no SELinux errors. Looking good bro.... looking very good! :D

Can you try uninstalling Google search and rebooting to see if it sticks?that gives me fits on the nexus 5

If Google search isn't a system app, try a few others . just have a nandroid lol
 
The settings stuck for me too bro.

Also, good news so far on the SELinux set to enforce, I haven't had any issues with my rooted apps at all. Titanium, Root Explorer, KTweaker, Quickboot apps, etc are fully functional with no SELinux errors. Looking good bro.... looking very good! :D

You may know something I don't with KT747 kernel-I have never been able to get it to boot it just hangs on boot screen. Funny thing is that KTweaker is installed once I flash back to dkp kernel. I follow the install instructions to a T, and I have seen other forum posts on XDA about the same thing. Apparently the age of the user's S3 may play a role is my understanding but have never seen a definitive answer or solution.
 
Can you try uninstalling Google search and rebooting to see if it sticks?that gives me fits on the nexus 5

If Google search isn't a system app, try a few others . just have a nandroid lol

Was able to get rid of it no problem with Titanium, and the deletion survived reboot, but wouldn't restore to save my life using several tricks. Had to reinstall from Play Store to get it functioning again.
 
You may know something I don't with KT747 kernel-I have never been able to get it to boot it just hangs on boot screen. Funny thing is that KTweaker is installed once I flash back to dkp kernel. I follow the install instructions to a T, and I have seen other forum posts on XDA about the same thing. Apparently the age of the user's S3 may play a role is my understanding but have never seen a definitive answer or solution.


This is the one I'm using. I wipe cache & Dalvik before flashing flash away! Worked the 1st time.

This is his AOSP 4.4 KitKat version

KT747-AOSP-KK-SPR-12-03-2013

I've also got a question pertaining to Philz recovery..... I cannot find where to fix permissions. lol. Guess I'll Google it. :p
 
This is the one I'm using. I wipe cache & Dalvik before flashing flash away! Worked the 1st time.

This is his AOSP 4.4 KitKat version

KT747-AOSP-KK-SPR-12-03-2013

I've also got a question pertaining to Philz recovery..... I cannot find where to fix permissions. lol. Guess I'll Google it. :p

Thanks, I will give it a shot. Think I might actually already have it downloaded, I tend to "collect" these things as I come across them just in case they are needed either immediately or in the future. There actually should be a zip posted on the KT747 thread on XDA that will wipe cache and Dalvik and fix permissions all in one go, haven't yet looked for the settings in Philz. Man, I could probably spend half a day just exploring the options available in that recovery!
 
OP updated with info and link for dkp kernel. Will add KT747 if I can get it to flash as well, if not will acknowledge that biker can get it running smooth on his phone.

Update: Same deal as has always happened with KT747, just hangs at boot. Once again, followed install instructions to a T; oh well, I absolutely love dkp, just like having alternatives to try out, being a flashaholic and all!
 
Don't know if you've seen the advice before, but make a backup of current OS in recovery, flash back to a TouchWiz ROM, update PRL and profile, then back to your CM11 backup. Also, there are APN fixes needed in order to make data/MMS work for VM and Boost users piggybacking off of Sprint ROM's. Wetbiker7 has a sticky thread with all that info available; I am on VM so the APN fix is slightly different, one of the rare times we don't share a common fix. On the plus side, I haven't had to flash the zip with the fix for VM since coming to CM11, the settings have finally stuck, at least with dirty flashing.

Did not follow through this whole thread. Only made sure to read and re-read the OP.

Cowinkamadentally, boost sent me a text saying they are improving the network. So I am guessing that no data crap had something to do with the network upgrade.

I will do that touchwiz rom trick you mentioned though.
 
Did not follow through this whole thread. Only made sure to read and re-read the OP.

Cowinkamadentally, boost sent me a text saying they are improving the network. So I am guessing that no data crap had something to do with the network upgrade.

I will do that touchwiz rom trick you mentioned though.

Very nice. Keep us all posted on what works and what doesn't.
 

Thanks for posting these buddy! Check PA GApps thread on XDA they have 12/15 up, and now only the complete stock package replaces AOSP features apparently.
 
Good deal it'll be nice to be able to move forward with the gapps. Testing this new build did a dirty flash over stock to see if that made any difference in my issues. So far been fine just same issues with APN settings and all that crap. Wish I could have MMS,lte, and my 3g all working as they do on stock but alas no luck yet.
 
Good deal it'll be nice to be able to move forward with the gapps. Testing this new build did a dirty flash over stock to see if that made any difference in my issues. So far been fine just same issues with APN settings and all that crap. Wish I could have MMS,lte, and my 3g all working as they do on stock but alas no luck yet.

Yeah, I wonder if PA had enough feedback on people not liking the replacement of the AOSP apps. Biker is having issues with his apn's and MMS too, I wonder if the slight differences between Boost and VM are causing issues because I have had zero issues personally.
 
Back
Top Bottom