pyler

Sure, but until we dont know what it checks, we cant bypass it.

They can check everything.. it is very easy to see where new implementation goes and then check for new files. Sadly, not many people work on this.

I even know a few lines of code which disables any Xposed modification on the app with that code.

https://code.google.com/p/android/issues/detail?id=93752 Shit, looks like Lollipop has wraping screwed up.. Now I know why I could make it working on JB, Kitkat, MM (emulator, but has it disabled selinux?) but but...

Maybe we could hook (not sure if possible even) WrapperInit main() beforeHookedMethod - disable selinux afterHookedMethod - enable selinux or hook onCreate and then re-enable selinux. Currently I will simple...

Instead of disabling SELinux, we could use supolicy to use specific supolicy to enable wrapping and keep SELinux enforced. https://su.chainfire.eu/#selinux-policies Edit: ok, nice fixed.

https://github.com/devadvance/rootcloak/pull/93 @devadvance please merge and re-release beta :) thanks

I will re-test it.

Sadly, still not work. Genymotion Nexus 6P Android 6.0 still seg fault.

Latest NDK and build tools 23... Please build APK for me to check even this.