FORUMS
Remove All Ads from XDA

[AOSP] sepolicy patch for Marshmallow ROMs

3,690 posts
Thanks Meter: 54,284
 
Post Reply Email Thread
3rd January 2016, 02:01 PM |#11  
danieldmm's Avatar
Senior Member
Flag France
Thanks Meter: 8,916
 
Donate to Me
More
the link in OP its no longer working...

Also in CM13 tree we have:
Code:
# Reload policy upon setprop selinux.reload_policy 1.
# Note: this requires the following allow rule
#   allow init kernel:security load_policy;
and over my builds have no problem with SuperSU system less...
 
 
4th January 2016, 05:28 PM |#12  
BeansTown106's Avatar
OP Recognized Developer / Contributor
Flag BeanTown USA
Thanks Meter: 54,284
 
Donate to Me
More
Quote:
Originally Posted by Chainfire

Starting 2.64, I think this addition to init.te is all that is needed:

Code:
allow init kernel:security load_policy;
Confirmation needed though. The original patch will also work with 2.64, and the ZIP installer should default to /system installation mode.

Of course, this also requires that /system isn't verified by dm-verity, and init reloads sepolicy from the standard /data/security/current location.

will build and test with only load policy enabled, is this for system, and systemless root?

Quote:
Originally Posted by danieldmm

the link in OP its no longer working...

Also in CM13 tree we have:

Code:
# Reload policy upon setprop selinux.reload_policy 1.
# Note: this requires the following allow rule
#   allow init kernel:security load_policy;
and over my builds have no problem with SuperSU system less...

updated link, so your saying systemless supersu works with no selinux modifications?
4th January 2016, 05:54 PM |#13  
danieldmm's Avatar
Senior Member
Flag France
Thanks Meter: 8,916
 
Donate to Me
More
Quote:
Originally Posted by BeansTown106

updated link, so your saying systemless supersu works with no selinux modifications?

Over my builds yes, no issues at all in cm13, although my kernel it's in permissive mode. Maybe it's why it works all good?

Enviado do meu A0001 através de Tapatalk
8th January 2016, 03:57 AM |#14  
BeansTown106's Avatar
OP Recognized Developer / Contributor
Flag BeanTown USA
Thanks Meter: 54,284
 
Donate to Me
More
Quote:
Originally Posted by danieldmm

Over my builds yes, no issues at all in cm13, although my kernel it's in permissive mode. Maybe it's why it works all good?

Enviado do meu A0001 através de Tapatalk

that is why, these patchs are to allow you to run in enforcing
The Following User Says Thank You to BeansTown106 For This Useful Post: [ View ]
30th May 2016, 05:49 PM |#15  
Junior Member
Flag Massamagrell, Valencia
Thanks Meter: 1
 
More
I dont know if a should post here this question: there is any way to fix this problem with the rom already installed?

Thanks
19th October 2016, 04:23 PM |#16  
Ibuprophen's Avatar
Senior Member
Flag Upstate New York
Thanks Meter: 1,843
 
Donate to Me
More
Quote:
Originally Posted by Garzla

I dont know if a should post here this question: there is any way to fix this problem with the rom already installed?

Thanks

Try the following. It works for me when needed...

http://forum.xda-developers.com/show....php?t=3574688
22nd October 2016, 08:29 AM |#17  
Junior Member
Thanks Meter: 1
 
More
Thank you for your work!
20th April 2017, 07:40 AM |#18  
Member
Thanks Meter: 11
 
More
Link in OP its no longer working...

Is there any actual guide how to add SU directly to AOSP build. I have found bits and pieces but those are mainly 4.x releases.
I'm using Android M release and quite much struggling to get it working.
29th April 2017, 08:15 AM |#19  
Member
Thanks Meter: 11
 
More
I have tried to make SU default on AOSP 6.0 by using this guide.
http://forum.khadas.com/t/gapps-and-su-on-soc/118/3
I'm using user build and enabled selinux permissive on that.
i have made also ro.secure=0 ro.debuggable=1 and security.perf_harden=0 (Not sure if needed)
I have also modified to change the su permissions in fs_config.c
I managed to get this work so that when flashing rom SuperSu ask for updating su binary and after that su works.
but i then cleaned work area to verify build by deleting out dir and recompiled. No go anymore.
Why it's so hard to add su by default on AOSP rom. I woud like to have it by default so i would not need to do any tricks everytime i flash new rom.
Post Reply Subscribe to Thread

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes