Don't have root on cm12

coldconfession13

Senior Member
Oct 10, 2010
1,410
187
0
seems I don't have root access on cm12. I did previously on 2/2 build then I flashed a 2/4 and it messed up my os so had to format and install 2/2. I have root access to apps and adb in developers options but for some odd reason my apps say I don't have root. What can I do to fix this.
 

doitright

Senior Member
Oct 31, 2014
1,512
861
0
Built in superuser has been flaky on lollipop. SuperSU works much better and has a higher compatibility with apps that Superuser. Personally I prefer to use the one that works best
That's silly.
This is something that either works, or doesn't.

As much as I dislike CM, they do have su down VERY well. Its even integrated with appops.

Its also open source. For something with that kind of security implications, I *absolutely would NEVER* trust a blob, which is what supersu is.
 

danarama

Senior Member
Aug 22, 2010
31,287
18,810
0
Oxenhope, West Yorkshire, UK
That's silly.
This is something that either works, or doesn't.

As much as I dislike CM, they do have su down VERY well. Its even integrated with appops.

Its also open source. For something with that kind of security implications, I *absolutely would NEVER* trust a blob, which is what supersu is.
Does it now do all the stuff that SuperSU does to prevent the requirement for permissive mode?
 

doitright

Senior Member
Oct 31, 2014
1,512
861
0
Does it now do all the stuff that SuperSU does to prevent the requirement for permissive mode?
It absolutely does NOT require selinux to be set permissive.
Also FYI: what you refer to as "all the stuff" is actually a pretty simple little adjustment to the selinux configuration.
...
CM actually has the whole selinux issue a lot simpler than SuperSU does, since as the system builder, you have the freedom to set your own selinux policies, whereas SuperSU had to hack around existing policies set by AOSP.
 
Last edited:

danarama

Senior Member
Aug 22, 2010
31,287
18,810
0
Oxenhope, West Yorkshire, UK
It absolutely does NOT require selinux to be set permissive.
Also FYI: what you refer to as "all the stuff" is actually a pretty simple little adjustment to the selinux configuration.
All I'm asking is "back in the day", when we first got our hands on Lollipop developer previews, we had to use permissive mode. Over time, through various SuperSU beta's - there was a point where the modifications to selinux were sufficient for *most* apps to not need permissive. Sure, some apps that have not been updated still require permissive mode to be set... So you're saying Superuser does that now?

Personally, I've always found superuser the lesser of the 2 root providers and was a long way behind in the early lollipop days and if they've got to a useful point now, great - though I dare say not without a lot of input from chainfire.
 

doitright

Senior Member
Oct 31, 2014
1,512
861
0
All I'm asking is "back in the day", when we first got our hands on Lollipop developer previews, we had to use permissive mode. Over time, through various SuperSU beta's - there was a point where the modifications to selinux were sufficient for *most* apps to not need permissive. Sure, some apps that have not been updated still require permissive mode to be set... So you're saying Superuser does that now?

Personally, I've always found superuser the lesser of the 2 root providers and was a long way behind in the early lollipop days and if they've got to a useful point now, great - though I dare say not without a lot of input from chainfire.
"superuser", if you're referring to Koush's su setup, was actually booted from CM some time ago.
Opensource is ALWAYS the superior option when dealing with security. ALWAYS WITHOUT EXCEPTION. You can't trust what you can't AUDIT.

... there wouldn't have been any *need* for input from chainfire. This isn't rocket science, its root. Every top tier Linux distro in existence has root with selinux set to enforcing.
 
Last edited: