I'm sorry, I wouldn't know, I'm not a dev ...
I'm a Windows type of guy, sometimes using a little linux/unix like on the command prompt of vmware esx, and there my knowledge stops ...
What seems to be the case is that not all of the system rom folders/locations are changed to have all the rights needed for root I suppose, but that's only an assumption based on the failure messages I get when working with the failing apps.
The only conclusion I could make on what I've tested is that the current root process used here is not 'complete' because of the reboots that happen with some application's that do work perfectly on other, older types of smartphone's ...
Avast Anti-Theft root-install does work on all other phones I've rooted, but not on this one.
With Titanium Backup, this also happens with certain scripts within the app.
Like removing apps you never use.
When SuperSu updates through Google Play, it will also fail completely. Root will be gone, and when trying to install the binary, the phone will show a failure message and reboot within 10 seconds, leaving you rootless.
Until now these three apps are the only ones that reboot the phone because some parts fail ...
For example, Droidwall is working like a charm.
AutomateIt Pro and MacroDroid also.
Regards,
Phoenix007
And is there any way how to "complete" the root process?
