su -cn u:object_r:kernel:s0 -c "busybox mount -o rw,remount /system"
su -cn u:object_r:init_shell:s0 -c "busybox mount -o rw,remount /system"
su 0 -c "busybox mount -o rw,remount /system"
#!/system/bin/sh
setenforce 0
ro.build.selinux.enforce=0
su
setenforce 0
</li>does this ROM/kernel have init.d support? I've read elsewhere that you can use a script to auto setenforce 0
Create script as follows:
<ul style='margin-top:0; margin-bottom:0;'>
<li dir='ltr'><tt>#!/system/bin/sh </tt></li>
</ul>
<ul style='margin-top:0; margin-bottom:0;'>
<li dir='ltr'>setenforce 0 </li>
</ul>
<ul style='margin-top:0; margin-bottom:0;'>
<li dir='ltr'>  </li>
</ul>
<ul style='margin-top:0; margin-bottom:0;'>
<li dir='ltr'>[/LIST] (Note: If you're using an app to emulate init.d, use su -c setenforce 0 if just setenforce 0 doesn't work) </li>
</ul>
<ul style='margin-top:0; margin-bottom:0;'>
<li dir='ltr'>Save it as set_permissive.sh, move it to /system/etc/init.d/ directory and give it permissions 755. </li>
</ul>
<ul style='margin-top:0; margin-bottom:0;'>
<li dir='ltr'>ofcourse this is all assuming you've got a way to make things stick which is what we want... </li>
</ul>
<ul style='margin-top:0; margin-bottom:0;'>
<li dir='ltr'>if we can get things to stick we could add this: </li>
</ul>
<ul style='margin-top:0; margin-bottom:0;'>
<li dir='ltr'><tt>ro.build.selinux.enforce=0 </tt></li>
</ul>
<ul style='margin-top:0; margin-bottom:0;'>
<li dir='ltr'>[/LIST] to our build.prop </li>
</ul>
<ul style='margin-top:0; margin-bottom:0;'>
<li dir='ltr'>so for now, do this: </li>
</ul>
<ul style='margin-top:0; margin-bottom:0;'>
<li dir='ltr'><tt>su </tt></li>
</ul>
<ul style='margin-top:0; margin-bottom:0;'>
<li dir='ltr'>setenforce 0 </li>
</ul>
<ul style='margin-top:0; margin-bottom:0;'>
<li dir='ltr'>[/LIST] then try mouting the system as rw? hope any of your changes stick, also, look into dm-verity
Well, shit in a straw and call me ****stick.
I think there is a solution. One would have to recompile the kernel though. Source has been available for a year or more now. <span style='font-size:22px';>Thishttps://drive.google.com/open?id=0B7gazdzft5-oUHJsN2pkVW56aEU</span> <span style='font-size:15px';>is a link to boot and recovery. If I can find system I'll post it up. I've tried DD'ing boot to the recovery partition , but it just gets replaced when you try to boot to it. The dirty cow exploit was our best bet. I did get a root shell with it a a while back but I don't have time to mess with it now. It is possible though I think. </span>
Oh yeah I forgot lol the last time I used metamorphosis was on my mate35 haha it's been a while well any suggestions on where to start? Maybe toy with sending and receiving video files from messaging or hangouts and running kingroot I know it's not setup for stagefright however there could be other vulnerabilities that aren't yet discovered while hangouts is going through the interger overflow deal
Yes please I need my rooted
I have been checking both of the Moto E4 Plus forums on here. Not sure why there are 2 , but I don't see anything from you on either. Am I missing it? I sure would like for you to post the root instructions and such if you would please. Thank you.Come on down to the Moto E4 Plus forum (stock v7.1), we also have TWRP, Root, ROMs available..
We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.