This only requires to do some PRs to add a device, or on updated firmwares describes a firmware, nothing device-specific). You still need to install the APK afterwards. It should be able to root any device supported by super-bootimg from TWRP (and possibly other custom recoverys) All Nexus-es, including Pixel C (if some Nexus is missing, just ask!) Here are some devices, but there are many more ! You need to install the APK from PlayStore afterwards: Supporting new devices might mean some additional work on if they are using non-standard boot.img format, but the aim is to support as many devices as possible. I did this build bot in a way so it is easy to add new ROMs, so don't hesitate asking for new ROM/devices support. I setup a build bot, which generates boot.img based on my solution, and pushes them to Please note that user is in heavy development and isn't up to its promises at the moment. su-apps won't be able to access to your Android Pay (for instance) informations, or keep persistent su access without your consent "nocrypt" is eng, dm-verity and dm-crypt disabled "noverity" is eng and dm-verity disabled This does NOT put SELinux in permissive mode. This is the most compatible mode, but you should trust the apps you give root to. "eng" which puts "su" in permissive mode. If you have an application that requires root, and which needs specific SELinux configuration please ask!Ĭurrently, four flavors of su are available on the build-bot: So I would like your help to make this SuperUser a proud opensource SU app! Here is a thread about my fork of Koush's Superuser, to handle SELinux:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |