A few days ago, the community of advanced users in Android has been at war for a very simple reason: it seems they will touch one of the things that come with freedom of the operating system, the root of that well-known you count everything in our section went to be in danger because of the arrival of Android Lollipop.
The Voice alert has been giving us the familiar Chainfire countless times: it is not the first time that an update to Android endangers the existence of the root, but community has always managed to avoid these problems to give more freedom to the Android users . However, this time may be somewhat different, but we have solutions for the community, and I will clarify everything so that you enteréis well what has happened in the last days
The alarm.: LPX13D
For you who have no idea what I’m talking about, LPX13D is the latest version of Android 5.0 Preview Lollipop at hand, and assume that is the closest to the version end of Android Lollipop . Developers have already been playing with version and Chainfire a man who is not at all new in these matters, and has been researching and tinkering with this version.
The fact is that his discovery has been quite clear: Google has worked to strengthen Android with tools like SELinux , and this has made all the services start to operate in its own context and not in init SELinux, which is how it worked so far everything this root. This is incompatible with the current idea of root, and the guys who work in this code have made a titanic effort to close all the holes that allowed its use.
+ Chanfire The conclusion of all this shows is that from now, it will be mandatory to use a custom kernel for the possible root , since we need to ensure from the start that can work. But, if we have the closed (and unable to open it) bootloader, it’s like the snake that bites its tail: can not install the kernel, so we will not have root, just what they want the guys who are responsible for security Android. That, or disable SELinux / put it in permissive mode, which is a pretty bad idea for obvious reasons.
franco.Kernel gives us the solution
Leaving aside that this under some pretty specific conditions, we can not do root, Francisco Franco has been ahead of the curve and has already released a version of its famous kernel (and of which we have spoken in El Android Libre) that is compatible with Android Lollipop (Preview) . This particular version is exclusive to Nexus 5 for obvious reasons, and gives extra features such as increased battery life a failure to adapt new GPU drivers.
However, it also has a very important detail: allows us to flash Chainfire SuperSu.zip without any problem or complication , satisfying the requirement of custom Kernel that something becomes mandatory by Chainfire. Use custom Kernels is not new, and probably already make many of you as one of the reasons for rooting your Android, but it can be complicated for users who have just arrived in this root.
Anyway, This decision will not end up rooting or falling on manufacturers : it is they who decide whether to lock the bootloader, and from Android Lollipop will rely on that to do anything. But that does not mean that things are as bad as they have said, why not be the first time that the community surprised us with simple solutions to all these problems. Anyway, Safety first or freedom to do what we want with our device
Via |? + Chainfire, + Francisco Franco, XDA-Developers
No comments:
Post a Comment