[SuperSU][System-Mode][2.82 SR5]

.

  • .

    Votes: 188 55.3%
  • .

    Votes: 209 61.5%

  • Total voters
    340
Search This thread

mauam

Senior Member
Jan 26, 2011
7,203
12,390
This is SuperSU that installs always in System-Mode.

Instructions
1 - Download zip
2 - Go in recovery & make a backup (optional, but recommended)
3 - Flash zip

Changelogs here & here

Special thanks to @aufarxda (the original creator of this thread) @Chainfire @CCMT
 

Attachments

  • UPDATE-SuperSU-v2.76-SYSTEMMODE.zip
    4.1 MB · Views: 88,519
  • SR3-SuperSU-v2.79-SYSTEMMODE.zip
    5.6 MB · Views: 74,381
  • SuperSU-v2.82-SYSTEMMODE.zip
    5.6 MB · Views: 34,314
  • SR1-SuperSU-v2.82-SYSTEMMODE.zip
    6 MB · Views: 19,366
  • SR2-SuperSU-v2.82-SYSTEMMODE.zip
    6 MB · Views: 6,484
  • SR3-SuperSU-v2.82-SYSTEMMODE.zip
    6.6 MB · Views: 15,048
  • SR4-SuperSU-v2.82-SYSTEMMODE.zip
    6.5 MB · Views: 11,205
  • SR5-SuperSU-v2.82-SYSTEMMODE.zip
    6.5 MB · Views: 103,327
Last edited:

fpqc

Member
Jan 6, 2016
22
28
Nightly comes with problems.Look Angler's XDA thread and ask others which nightly is the most stable build.
Hope that helps.

The reason I think is that this is the first update with the newest vendor.img. That's the only thing that seems out of the ordinary.
 

aufarxda

Senior Member
Oct 18, 2015
76
189
Jakarta
I have the Verizon SCH-I545, MDK bootloader, and am running JDC Team's AOSP 6.0.

I am unable to install any version of SU above 2.52. TWRP 2.8.7.0 and 2.8.7.2 by Antaresone and the official 2.8.7.0 all fail with the same message.

Recovery.log

https://www.dropbox.com/s/kmc3bafuvlfq20v/recovery.log?dl=0
Solution 1(Tricky, and may not work) :
Try to mount data and system using mount option and remove mounting script on the updater-binary.
Then, use TWRP file manager to remove /supersu manually.
At last, install the zip again.
Solution 2 (not really a solution) :
If you really cant mount data or system, ask the rom dev or someone on your phone's forum for solution.
Solution 3 (1% chance of working) :
Dont bother about the bootloader.
Check your boot image instead.
Solution 4 :
Check if you have chcon on system/bin.
If not download this file and move it into system/bin.
Link :Drive
 
Last edited:

krazyace35

Senior Member
Mar 11, 2012
660
218
Can this be flashed over systemless root to convert to system root or will I have to flash my system.img backup then this. I'm running systemless root on Htc M9 Marshmallow dev edition

Sent from my HTC One M9 using Tapatalk
 
Last edited:

aufarxda

Senior Member
Oct 18, 2015
76
189
Jakarta
Can this be flashed over systemless root to convert to system root or will I have to flash my system.img backup then this. I'm running systemless root on Htc M9 Marshmallow dev edition

Sent from my HTC One M9 using Tapatalk

No, full unroot first.
Then, remove /su
Replace the kernel with new custom one.
And then, flash the system mode zip.
 

krazyace35

Senior Member
Mar 11, 2012
660
218
No, full unroot first.
Then, remove /su
Replace the kernel with new custom one.
And then, flash the system mode zip.
Cool thanks for the info

Sent from my HTC One M9 using Tapatalk

---------- Post added at 06:00 PM ---------- Previous post was at 05:30 PM ----------

@aufarxda I'm guessing there are no custom kernels yet for Marshmallow? I can't find one I also noticed flar2 said the kernel source hasn't been released yet

Sent from my HTC One M9 using Tapatalk
 

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    This code compatible with LGE R-31 OS10 OCTA CORE?

    The only way to know for sure is to try it yourself. Just make sure you flash a permissive kernel BEFORE flashing the SuperSU system mode zip, or else you will certainly encounter a stalled boot/boot loop.

    The best way for you to test:

    Flash custom kernel zip, WITHOUT flashing SuperSU zip. Boot into Android, open a terminal app, type "getenforce", without quotes. If it returns 0 or permissive as the result, you should be good to flash SuperSU zip.

    If you get 1 or enforcing:

    Flash the kernel_permissive_patcher.zip from:

    Kernel permissive patcher

    After that, reboot and run the terminal commands again. If you get 1 or permissive, try the SuperSU zip. Even after all this, it's still not guaranteed that you'll be able to boot with SuperSU in system mode, but it will likely work. It just depends on the installed ROM/kernel.

    Note: if you get "permission denied" when using the getenforce command, use the su command, then getenforce. This of course requires that you be temp rooted with something else.

    Edit: you can also check SELinux status in in the About (or similarly named) section of the Settings app. An app called TeMeFi can also retrieve the status. I only suggested the terminal way first, because I'm so used to using commands in a terminal to do many things.
  • 357
    This is SuperSU that installs always in System-Mode.

    Instructions
    1 - Download zip
    2 - Go in recovery & make a backup (optional, but recommended)
    3 - Flash zip

    Changelogs here & here

    Special thanks to @aufarxda (the original creator of this thread) @Chainfire @CCMT
    15
    14
    13
    13
    And 2.71 system mode, for people that can't grab the Mega link, just like me:)
    Tested on CM12.1
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone