Android 4.3 gets harder run applications with root permissions

When rooting we do our Android device to run applications with root privileges to access the default functions are protected by the system. Well, Google has put a bit more difficult to root permissions from Android 4.3 (Jelly Bean).

Since the new version of Android and are missing access permissions setuid and setgid to allocate them to applications and so run as root. Google explains it in the Android code. This means that the methods used to date for rooting our devices have to be modified to allow applications as SuperUser or SuperSU working again, because if not about all that work would be the ADB shell.

The good thing is that there is already a solution to give superuser permissions from Android 4.3, and is modifying the recovery to add a demon, a process that will always run in the background that will allow us to access to setuid and setgid give elevated privileges to applications that require them to function properly.

Chainfire of SuperSU already has the new process root for Nexus to re-run your application, and ClockworkMod Koushik Dutta of SuperUser also look to implement this method in your recovery and try to find another way to get back to superuser without relying on a daemon process.

The good thing is that being open source Android this problem does not have the ROMs to not have to rely on a demon to work SuperUser applications, corrected this problem. For example, 10.2 CyanogenMod have already corrected this problem root. Actually the "problem" of this change are for Android devices with standard firmware, now no longer rooting the device without changing the recovery to run root applications, or at least for now.