yashsingh1/xdaforums huggingface dataset:
[SuperSU] Chainfire:
Here is the v2.78 ZIP, compiled by me (binaries are still v2.77):

UPDATE-SuperSU-v2.78-20160905010000.zip

Since some of you have expressed concern, I have checked all code changes since last release and found nothing untoward. Additionally, decompiling both my own APK and the one from the Play store yields the same class files. The two releases are functionally identical.
[SuperSU] Mesmurized:
I am running Pure Nexus with SuperSU 2.76 installed as system mode. Can I just boot into TWRP and flash this latest version? Or must I reflash PN and ??
[SuperSU] Pkt_Lnt:
The quick easy way or the long involved unnecessary way? ;)
[SuperSU] Mesmurized:
Haha. Hopefully the quick easy way :)
[SuperSU] rdmd:
Can't get SuperSU zip to install

I'm having trouble with rooting my completely stock LG G3 d851 on Marshmallow 30d. I've been able to install TWRP by adb after temp rooting with Kingroot. I then use TWRP to try to install SuperSU's zip (2.7.6). This takes out Kingroot but doesn't install SuperSU. Any ideas on what's going wrong?

On the TWRP screen when I try to install the SuperSU zip I do see:

*********************

Boot image patcher

*********************

- Finding boot image

--- Boot image: /dev block/mmcblk0p18

- Extracting ramdisk

- Decompressing ramdisk

--- Failure, aborting

Not sure what that means, but it doesn't sound good...

Thanks.
[SuperSU] Pkt_Lnt:
Choice A it is.

---------- Post added at 04:57 PM ---------- Previous post was at 04:55 PM ----------

This is from the Beta thread, if you check, your boot image probably uses some other compression.

http://xdaforums.com/showpost.php?p=64410503&postcount=3879

Are you flashing this from the thread linked here?

http://xdaforums.com/tmobile-lg-g3/development/stock-d851-30d-kdz-flashable-zips-imgs-t3367371

LG-D85130D-Flashable.Boot-AUTOREPACK.zip
This is a repacked boot.img to work properly when flashing SuperSu in TWRP.
[SuperSU] AgentOrange96:
I just checked, and it does seem to be restarting the process, because the PID changes. According to GSAM it's part of "Kernel (Android OS)" although I'm not totally sure if that's what you're looking for. Thanks!

Note: This is a duplicate to my comment in the previous now closed thread.
[SuperSU] Chainfire:
What's the full output of 'ps' (as root) ?
[SuperSU] AgentOrange96:
http://pastebin.com/vM7ZAbzC

http://pastebin.com/ADbBBBkA

Here are a couple of runs of it. The first one seems to reference supolicy, but the second does not, so it may not be as interesting.
[SuperSU] Chainfire:
Interesting. For starters, I would suggest a full unroot and re-root. Then if the problem persists, pull your /sepolicy file and post it here, that might help.

What are your device details?
[SuperSU] AgentOrange96:
I was thinking it might be best to do a full restore on the phone anyway, but I'm too lazy to deal with that right now, so I'll try a re-root as you're suggesting as that shouldn't take as much time or involvement. I'll let you know how that goes! Again, thank you!

EDIT: So I unrooted and re-rooted, which was a bit of a pain actually because SuperSU didn't seem to be requesting root initially from Kingoroot's SuperUser app, but once it did everything went pretty smoothly. My terminal emulator broke, again. (For some reason it just won't display any text, and I forget how I fixed it before, but that's not related.) Once I installed a different terminal emulator, I didn't see supolicy at all, so it seems like the issue is resolved. I'll let you know if I encounter that again, though I hope I don't.

Also, I just got SuperSU Pro because thank you for your help and for your major contribution to the root community!
[SuperSU] gregfrankenstein:
Woah. I flashed the SuperSU Beta, as I read elsewhere that this is currently the best way to root the Nexus Player, and it provided a boot image like magic. Here I thought SuperSU was just for access control.

So my needs have already been met! And I thank Chainfire.

I get the same error when I try upgrading from beta to stable, but strangely, once I boot up the app says I'm on 2.78. So problem solved?
[SuperSU] wogooo:
My rom has a built-in Superuser. Now i installed SuperSU. Do i now need to disable the built-in root?
[SuperSU] pyrmd:
I had previously rooted my phone. It was working fine.. unfortunately I had to clear the data. I found the supersu gone. And I decided to flash SuperSU 2.78. it caused bootloop. And finally i wiped data. It had booted by then. Ive got battery issues. Screen touch doesn't work when battery drop to 15%. Somebody plz help me fix this.
[SuperSU] Ibuprophen:
When it comes to the number of applications that can be installed that manages the root access to a device? I think a quote from the movie Highlander says it all.. "There Can Be Only One!" :laugh:

I'll give you a brief explanation as to why that is...

The purpose of Superuser apps, like SuperSU, is to manage access requests from other applications to the root system files.

With that stated, having more than one Superuser application to manage root access will ultimately/eventually result in an unfavorable conflict.

You should remove one Superuser management application in order to appropriately install another.

I tried to explain it as brief and to the point as i possibly could.

If I'm correct, then can someone please let me know?

And if I'm wrong with any or all of this, can someone please correct me so I know what it was that I was wrong about?

Good Luck!
[SuperSU] pyrmd:
Wrong thread?
[SuperSU] shaggyskunk:
I include Flashing SuperSU whenever I Flash a Custom Rom & I haven't had any issues if I've forgotten to disable a Built-In Superuser - But that's not to say that you won't - Built-In Superuser can often be disabled by simply going to Settings - Developer Options - Root Access and Select Disabled.

Sent From My SM-N910W8 ðŸ‡¨ðŸ‡¦
[SuperSU] Ibuprophen:
I did notice these within the logs:

***************************************************

- Mounting /system, /data and rootfs

mount: mounting /dev/block/mmcblk0p28 on /data failed: Device or resource busy

MtpServer::run fd: 25

E:request read returned -1, errno: 22, exiting MtpServer::run loop

/tmp/updater: line 841: /system/toolbox: not found

- Extracting files

***************************************************

MtpServer::run fd: 25

E:request read returned -1, errno: 22, exiting MtpServer::run loop

Archive: /sdcard/ADM/SuperSU-v2.78-201609011115.zip

***************************************************

(Android M policy compatibility mode)

MtpServer::run fd: 25

E:request read returned -1, errno: 22, exiting MtpServer::run loop

supolicy v2.77 (ndk:armeabi-v7a) - Copyright (C) 2014-2016 - Chainfire

***************************************************

- Detecting system compatibility

MtpServer::run fd: 25

E:request read returned -1, errno: 22, exiting MtpServer::run loop

sukernel v2.77 (ndk:armeabi-v7a) - Copyright (C) 2014-2016 - Chainfire

***************************************************

The above information holds the gist of it, though, the bottom 2 blocks, are repetitive within a few additional places.

Something did go wrong... Hmmm...

Bump?
[SuperSU] pyrmd:
Can I root it.. what's causing battery issues?

I'm still in stock rom.

Thank you...
[SuperSU] Ibuprophen:
Please excuse me for asking...

But, why disable it (I'm truly not stating that your wrong at all)?

Why not recommend uninstall it first then flash the SuperSU?

Am i wrong or am i just stating an additional option?

Just wondering... :fingers-crossed:
[SuperSU] wogooo:
Built-in superuser cant be removed

---------- Post added at 05:31 PM ---------- Previous post was at 05:29 PM ----------

Hmm...what i did...i installed SuperSU. Then disabled built-in superuser.

Then rebooted, and again it doesnt boot. I only see CM logo flashing but nothing happens. It happend a couple of time, also without disabling built-in superuser.

Can someone help me? Now i need to flash rom again :eek:

I have Android 7.1 / CM 14.1

Samsung Galaxy S5 mini
[SuperSU] shaggyskunk:
It's what has always worked for me - I've never had any issues with just disabling built-in Superuser (not 100% sure if I even need to) But regardless I always Flash SuperSU.

Sent From My SM-N910W8 ??
[SuperSU] wogooo:
Now i reinstalled rom. Then when i start SuperSU it says it needs the new binaries again. Guess SuperSU doesnt work on 7.1
[SuperSU] Ibuprophen:
Once he disabled his built in Superuser, shouldn't he then flash SuperSU?
[SuperSU] shaggyskunk:
Anecdotally speaking - I haven't noticed any difference - But my routine is Factory Reset - Advanced in TWRP 3.0.2-0 - Manually Wipe System - Data and Caches - Flash Rom and Gapps - Flash SuperSU - Wipe Caches - Reboot and Setup - Most Roms that have Superuser built in have it disabled by default (but not all) - And in many cases you have to go to Settings - Developer Options - Root Access and Select Apps & Adb if you want to use the built-in Superuser - Since I don't I don't enable it in Dev Options.

Who knows my process may be incorrect from a technical point of view - But it's working for me.

Sent From My SM-N910W8 ðŸ‡¨ðŸ‡¦

---------- Post added at 12:38 PM ---------- Previous post was at 12:35 PM ----------

SuperSU certainly works on 7.1 - Don't install it from the store - Flash the SuperSU v2.78 zip ;)

Sent From My SM-N910W8 ??
[SuperSU] HakanCelikMK1:
Thanks for your time, I will give those a try.
[SuperSU] Einwod:
So what thread should he be in? Your answer tells him nothing. So where should he be?

---------- Post added at 12:57 AM ---------- Previous post was at 12:55 AM ----------

Your last 2 lines says it all. You really think your device is capable?
[SuperSU] Ibuprophen:
I do, in fact, perform pretty much all of your installation process.

After i perform a fresh install of CM13, the first thing I do (before my other customizations) is going into the Developer Options (after i enable it) and under Root access i select the Apps and ADB. After that, i then configure SuperSU, and when I get to the Respect CM Root Settings option, i leave it unchecked. This reflects that, though CM is open to them all, SuperSU then takes over because, if i selected the Respect CM Root Settings option, both of them would be left open.

I hope i explained this okay...
[SuperSU] shaggyskunk:
I'm sure that's fine - I just don't see the need to use any of CM's Superuser since I Flash SuperSU v2.78 during the process of Flashing the Rom - Gapps and anything else - ie: V4A and SuperSU.

Sent From My SM-N910W8 ðŸ‡¨ðŸ‡¦
[SuperSU] wogooo:
? What do you mean? Why wouldnt it be?

---------- Post added at 01:45 PM ---------- Previous post was at 01:42 PM ----------

you mean this file, right? SuperSU-v2.78-201609011115.zip

ah nevermind! obvious, lol
[SuperSU] shaggyskunk:
Yes that is the stable Supers v2.78

Sent From My SM-N910W8 ??
[SuperSU] jdegreef:
Of course it can.

And I think it should in the case the rom root is in system (like CM /system/xbin/su /system/bin/su) and you flash Supersu systemless. Just disabling in developer settings don't remove the binaries. See http://j.mp/2gM9Sv6

In your case a would make a backup of my data, apps, everything important, wipe everything and restart from scratch. Sometime it's faster to restart from scratch than trying to fix a situation that's gone awol...

Well... only if he wants root :D
[SuperSU] wogooo:
Thx!! SuperSU seems to work now as it should, via flashable zip.

(Nontheless Toggle Network Type 5.0 widget still doesnt work ;( )
[SuperSU] shaggyskunk:
The link posted only indicates that built-in Superuser can be detected by a Banking app - I don't believe that this means that the built-in Superuser is actually active - All apps that require Root Access request it from SuperSU.

Sent From My SM-N910W8 ??
[SuperSU] jdegreef:
You're rigth, I just wanted to show that rom su can be removed.
[SuperSU] aloknm:
How do I install this as systemless?
[SuperSU] Einwod:
It automatically will flash as systemless.
[SuperSU] ban.codrut:
Not on all devices !!

For example a

I have a MXPE and it always detects mine as system mode compatible , which is not as it goes in bootloop.

As for the answer on HOW TO, you have to go in TWRP terminal and enter this command before you flash:

echo SYSTEMLESS=true >> /data/.supersu

This way you'll put the SYSTEMLESS sting as true in the config file and will force the installation to go on this mode.

Also if you already have SuperSU I think you'd have to uproot first from the app before changing mode (I'm not sure that the install script will do the cleanup for you, maybe the dev could clarify [MENTION=7678190]SuperSU Release[/MENTION]s)
[SuperSU] Hermankzr:
I have successfully rooted my Galaxy Note 4 MM 6.0.1 1st Nov patch with SuperSU-v2.78-201609011115.zip via TWRP.

Just flash it and don't worry it would be fine and yeah, it's installed as systemless
[SuperSU] olejonbj:
Does this work on CyanogenMod 14.1 Android 7.1 when flashing with TWRP?
[SuperSU] BumRush:
I am trying to update SU binaries because it keeps saying it's outdated. But it fails everytime. Is there another way to do it?
[SuperSU] shaggyskunk:
Just Flash SuperSU v2.78 zip

Sent From My SM-N910W8 ðŸ‡¨ðŸ‡¦
[SuperSU] culiacanazo:
Flashing it (as opposed to installing/twrping it from within the UI) will get it done, but I've read that it will kill WiFi for some in CM14.1 (but uninstalling/unrooting from within the UI will restore it, albeit you will have lost root access even from the built in super user...)

Just so you know if you didn't/it applies to ya
[SuperSU] BumRush:
I flashed the zip in the original post but I am still getting the update binaries notifications and it still fails when I try. I've also tried SR5 beta but also no luck.
[SuperSU] culiacanazo:
Depending on your device, build, and what you're coming from (previous android version), along with what you had installed (xposed, magisk, kernels, access management apps, etc) you just might have conflicting .imgs remnants somewhere... (/data?)

I'm not too sure as i don't have that (or any) problem, but as I've stated earlier, "I've read" this & that, but maybe I'm wrong.

Also, someone mentioned above that manually deleting prior binaries helped... Give it a go
[SuperSU] BumRush:
How would I go about doing that?
[SuperSU] jdegreef:
I have the feeling something went wrong when you flashed 2.78 from this thread. I don't see how it would say it need to be upgraded as it is the latest release...

AFAIK, to remove stock su you should delete /system/bin/su and /system/xbin/su from TWRP. That's what I did for CM13 here. I also disabled it in Devolopper Stettings prior to flashing 2.78.
[SuperSU] culiacanazo:
I have a feeling he just might be throwing a pop corn into the air to catch it with his mouth while reading this, for i find it hard to believe he wouldn't understand my last post being a "senior" member...

Of course, i could be wrong...

I should make that line my signature...
[SuperSU] CyberZeus1977:
Does it work on 7.1.1?

Sent from my interstellar 6P!
[SuperSU] ulxerker:
most likey not, use version SR5 instead which is working with 7.1.1
[SuperSU] CyberZeus1977:
Thanks, do you have a link for downloading it?

Found, never mind[emoji6]

Sent from my interstellar 6P!
[SuperSU] Ibuprophen:
The link is located on the very first post of this thread.

Any time a new SuperSU SR is released, the Dev always updates and places the download link on the first post of this thread.
[SuperSU] CyberZeus1977:
Thanks, the first post doesn't have any link to SR5

Sent from my interstellar 6P!
[SuperSU] Ibuprophen:
My apologies... Here's the thread:

[BETA][2016.11.30] SuperSU v2.78 SR5 by Chainfire

Good Luck my Friend!
[SuperSU] CyberZeus1977:
No problem [emoji6]

Sent from my interstellar 6P!
[SuperSU] olejonbj:
I flashed SR5 in TWRP without problems on CyanogenMod 14.1 Nexus 5 CAF official. Expect reboot or two after rebooting system after the flashing. That's normal.
[SuperSU] anshsharma123:
Does this version break sensors? Like the previous ones?
[SuperSU] jdegreef:
Never had any problem with sensors here (Moto G 4G/LTE, preregrine, xt1039).
[SuperSU] jenil1428569:
My OnePlus 3 is stuck at booting after flashing SuperSU 2.78 through TWRP and rebooting.

Current Rom is OxygenOS 3.2.8 which was just released on December 5th.
[SuperSU] olejonbj:
Yesterday I went to bed turning off Wi-Fi and Cellular. When I woke up this morning, SuperSU told me the binary needs to be updated, which I didn't understand, since I was already running SR5 (this version). Some investigation in ES File Explorer showed /system/bin/su and /system/xbin/su was removed, I think. I didn't investigate much, just booted into TWRP, took a backup and flashed SR5 again and now it's back to normal (updating the binary in the app itself I only have bad experiences with on my CyanogenMod 14.1 Nexus 5 CAF ROM (official). Developer: Why did this happen during the night??
[SuperSU] mU$!c:
[MENTION=631273]Chainfire[/MENTION] Do you have a method to replace KingRoot w/your SuperSU, or root with your SuperSU after I just unroot and uninstall KingRoot???
[SuperSU] culiacanazo:
Dud-o! Has been answered before, check forums

PS chainfire is not in charge of this forum any longer
[SuperSU] Ibuprophen:
I just want to know if there is anyone who had success or failure, specifically, who has a Verizon Samsung Galaxy S3 (D2VZW), who flashed this Stable version of SuperSU 2.78 when installing the new CM14.1 Nightly?

I just wanted to get feedback somehow from someone who has this specific device as asked above.

Thank you all!
[SuperSU] mU$!c:
Nevermind, i figured it out.
[SuperSU] pyrmd:
I have a oneplus one. To get it rooted I flashed superSU 2.78. And initially it was working fine. After using the phone for about half an hour, it automatically restarted. And the super su binary( root access) was gone.. And tried to flash it again. But it couldn't help.. Also there is no super su installed after flashing. Plz help..
[SuperSU] counterfeit187:
On which ROM? I recommend the sr5 version of supersu
[SuperSU] pyrmd:
Thank you for the reply.

I'm still in stock cm 13.

I tried all the version right from 2.76 to the latest build.

Error something like "checking for stock backup. No backup. Restore failed" occurs and continues to success , but I have no root access no su installed.[emoji29]
[SuperSU] grep_i:
Did you remove the preinstalled cm superuser prior to flashing SuperSU ?
[SuperSU] pyrmd:
It is a stock ROM.

And even though I flash the su, app won't be installed.

Maybe data was cleared accidentally after first flash. Then again I flashed, it was working.. Problem raised after automatic reboot..

Is there a way to fix it?
[SuperSU] culiacanazo:
Stock cm13? :confused:
[SuperSU] pyrmd:
What do I do.?
[SuperSU] grep_i:
As far as I know CM is automatically a custom rom with built in root.

So I guess you have to remove the built in root first before you flash another root.
[SuperSU] pyrmd:
Mine is a one plus one with stock cm13.. I didn't flash any other ROMs
[SuperSU] culiacanazo:
Then it's not cm, it's cyanogen (no "m" there)

As far as what you can do, read and research (because it's hard someone will help you for two reasons, first you don't even know what you're running therefore can't provide necessary info thus resulting in ppl shying away; second, it's info that's been asked and answered before)
[SuperSU] pyrmd:
Ya? In the boot animation i see cyanogen mod.? Anyway its off topic. Plz tell me how to fix it.. [MENTION=7182553]culiacanazo[/MENTION] I have clearly specified what I'm running. And I believe what I see is true..
[SuperSU] culiacanazo:
Then to further "help" you would be to mislead you, as im lost
[SuperSU] pyrmd:
Yes u have.
[SuperSU] grep_i:
You clearly don't understand a thing about your rom and will therefore say that good advice is not right.

To save both of our time I let you be but give you one advice, learn to use the search function of this forum and read carefully the log files of what you have flashed.

I'm not going to spoon fed you, please figure it out yourself it is not hard to do this.
[SuperSU] jdegreef:
[MENTION=7813184]pyrmd[/MENTION], to make this clear, post a screenshot of About Phone.
[SuperSU] pyrmd:
Deleting binary didn't help. As it was previously suggested. It is then I posted my issue here. Is there way to solve with out reinstalling the system? I don't know if boot.img or system to be flashed.. [MENTION=6952047]grep_i[/MENTION] I saw your previous suggestions. Try to be polite with strangers. And you lose nothing if you do.
[SuperSU] Malkemid:
i'm using htc one m8 marshmallow GPE costume rom and i tried many supersu zip s and none of them can root the device...should i mount or unmount something in TWRP?
[SuperSU] jdegreef:
What does recovery.log say ?

To help I asked you to post a screenshot of About Phone so we'll be certain what rom you use but you didn't...
[SuperSU] pyrmd:
Thank you for the reply.

Is that cm or cyanogen. I didn't really get it.. I see mod everywhere but not in os
[SuperSU] jdegreef:
[OT]This is clearly a Cyanogen OS rom, based on Cyanogenmod and with a Cyanogenmod based kernel compiled by the guys who build the Cyanogen OS.

It differs from Cyanogenmod rom by the modifications that have been made to it.[/OT]

I have no knowledge of Cyanogen OS but your recovery.log should give information about your problem.
[SuperSU] pyrmd:
Recovery log
[SuperSU] grep_i:
- Flashing boot image

dd: writing '/dev/block/mmcblk0p7': No space left on device

This is /boot so patching is not succeeding I guess.

If you follow the forum rules and be very specific in your posts than I have not to be so not polite in your eyes, to me it is just a means to get more information from you as you clearly hold back, you don't give the required information yourself.

We all have to beg multiple times for the required information.

I will stop right now as you clearly will see this as impolite too.
[SuperSU] Ibuprophen:
Just providing you all with what I do with my configuration of CM13 and SuperSU...

I go into the Developer Options, select Root Access then Apps and ADB.

Then as I customize the SuperSU settings, and get to the "Respect CM Root Settings" option, i leave it Unchecked.

This way CM Root Access is left open that allows SuperSU to manage it.

If SuperSU's "Respect CM Root Settings" option is selected, then Root is left open in SuperSU deferring to CM that is left open.

This customization has always worked for me without removing anything from CM.

Just putting out what works for me but, i don't guarantee that it will work for everyone (though, personally, I don't see any reason why it won't).

I'm not one to gossip, so you ain't heard this from me... LOL!

Happy Holidays!
[SuperSU] ErvinSoliven:
Is the super su update support for huawei emui 5.0 android nougat 7 will also be provided by chainfire? I hope there will be an update. Cant live without root haha
[SuperSU] culiacanazo:
You don't have to...
[SuperSU] Poppeye0:
2.79 stable now in Play store.
[SuperSU] funfun99999:
Today the supersu got updated to 2.79 over play store.

There is a recovery flashable ZIP that I can download?
[SuperSU] radz_:
Wheres the zip?
[SuperSU] shaggyskunk:
Yeah I think that the previous post was a question - And not a "I have the zip to download".

I'm sure that the Thread will be updated to v2.79 Stable.

Sent From My SM-N910W8 ??
[SuperSU] radz_:
Yeah, thats what i thought..[emoji4]

Patiently waiting for zip..
[SuperSU] neutronizer:
I update supersu on playstore but failed to update, do you have the zip file, so I can update from recovery?
[SuperSU] shaggyskunk:
Looking at the few posts immediately above yours didn't provide an answer?

Like everyone else - We just have to wait for the updated zip on this Thread.
[SuperSU] waledakmal:
2.79.zip

https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.79-201612051815.zip
[SuperSU] jdegreef:
Sometimes we should search instead of waiting.

Supersu 2.79 zip

---------- Post added at 11:44 AM ---------- Previous post was at 11:43 AM ----------

We posted at the same time ;)
[SuperSU] Chainfire:
As requested, v2.79 STABLE ZIP compiled on my computer from my verified sources:

https://download.chainfire.eu/1016/SuperSU/UPDATE-SuperSU-v2.79-20161211114519.zip