yashsingh1/xdaforums huggingface dataset:
[SuperSU] Cookie Ninja:
The correct syntax is...

echo SYSTEMLESS=true>>/data/.supersu

For forcing systemless root and

echo SYSTEMLESS=false>>/data/.supersu

For forcing system root
[SuperSU] Chainfire:
That would be very useful.
[SuperSU] BulletBrusher:
Sorry, can anyone repost the unsu.zip I don't find it

Thanks in advance
[SuperSU] Portgas D. Ace:
See here:

http://xdaforums.com/showthread.php?t=2239421
[SuperSU] hanygrandaton:
why not working with Huawei Mate 8 Android 7.0 and gives me Installtion failed
[SuperSU] jdegreef:
I have seen this problem too from time to time but it disappeared. I think my phone was too busy and then it took time for Supersu to reply.
[SuperSU] hanygrandaton:
Thanks For Your Great Efforts , But Why Not Working On Huawei mate 8 NXT L29 Android 7.0 . And Gives me Installation Failed , Please Reboot And Try Again
[SuperSU] Portgas D. Ace:
Have you rooted your device or does your ROM come pre-rooted? If you don't have root access, then installing SuperSU from Play Store wouldn't root your device. You could flash the .zip file from the first post by using a custom recovery (TWRP for example) to root your device.
[SuperSU] Chainfire:
Testing out this lag issue is the last thing holding back v2.79 SR1, which has a boatload of fixes and changes, so I hope we can figure it out soon.
[SuperSU] dug3001:
Hello

Now we have an operational recovery custom in huawei mate9. Do you think that it's possible to root it whit flashing the supersu 2.79?

Envoyé de mon MHA-L29 en utilisant Tapatalk
[SuperSU] ShouriX:
does it support f2fs?
[SuperSU] jcmm11:
It doesn't know or care what the underlying file system is.
[SuperSU] Pkt_Lnt:
http://xdaforums.com/showpost.php?p=64410503&postcount=3879
[SuperSU] nicholaelaw:
SuperSU could not install correctly on devices with f2fs data, without forcing it into to system mode. Can it be fixed?
[SuperSU] kamikaze702k:
SuperSU!!
[SuperSU] thebrainkafka:
Nixe. Thx
[SuperSU] 2159687:
留空楼的做法跟百度贴吧相似。Interesting.
[SuperSU] grep_i:
So the one I already installed SuperSU-v2.78-201609011115.zip is exactly the same as the one we can download from your site compiled by you ?
[SuperSU] ktmom:
"Blank floor practice with similar Baidu Post Bar" (courtesy Google translate)

WTF?
[SuperSU] Ja_som:
This forum is English only...
[SuperSU] Chainfire:
Functionally identical - if you decompile it, the code is the same. If you directly compare the two ZIPs, you'll find some differences.
[SuperSU] tohtorin:
[MENTION=631273]Chainfire[/MENTION] can you guarantee that we can use this new companys supersu without even slightest concern about security or malware? Why supersu pro play store comments people say that the new key app has malware detected? Are you still implementing new features and can you control what gets deployed? Are you going to make a new features for supersu?

Is your systemless code open source so we folio hats can implement it to open source alternatives?

Whats this fuss is all about?
[SuperSU] Golf c:
How can a former owner guarantee anything in regards to the new owners? SuperSu is closed source code.
[SuperSU] jorceshaman:
I'm sad that chainfire will stop development on the project but unlike others, I don't think there's anything to be concerned about. He wouldn't have handed this project over to just anyone. And if he trusts them then I do.

Thank you, Chainfire, for all of the time you put into this project and will continue to put in during the transition!
[SuperSU] Chainfire:
I cannot guarantee anything about what anybody else may do at any time; nobody can.

What I can say is that both 2.78 Free and Pro from the Play store as they have been downloaded to my phone do not contain any malware. Various scanners detect SuperSU itself as malware because it is root - this has been the case for years. Especially for the Pro version it's easy to confirm it isn't - decompile it and you will find only a dozen lines of code; its an empty package serving only as an unlock key.

As for your other questions: Obviously I am legally barred from contributing to competing softwares, open source or otherwise, while I'm working for CCMT.
[SuperSU] jerethi:
I'm on a stock 5X with Nougat - can I simply flash this version with TWRP and it will give me root?
[SuperSU] NLBeev:
Probably he/she will not understand your post.

G-translate: 本次论坛是唯一的英语...

When doubts about software ...... don't use it.
[SuperSU] tohtorin:
So you work for CCMT and continue to work with SuperSU?
[SuperSU] Clark789:
I doubt it very much...
[SuperSU] Chainfire:
It's been practically a year already...
[SuperSU] a g bell:
Was running 2.78 fine on my nexus 5 updated 2.79 through play store now some apps can't get root properly like viper have gone back to a factory image and back to my custom rom and still the same issue am l missing something is the a su file on my device that would remain after flashing a factory imageðŸ¤”
[SuperSU] Ch3vr0n:
[MENTION=631273]Chainfire[/MENTION] Uploading right now but it'll take a couple hours. It's a 9.45GB zip file
[SuperSU] Ch3vr0n:
[MENTION=631273]Chainfire[/MENTION] Please check your PM's. I have sent you a PM containing the download URL on my google drive (as i didn't want to put my nandroid backup publicly available for everyone to download, privacy & all) and some device details from the backup and to reproduce. Let me know if you need anything else

[MENTION=631273]Chainfire[/MENTION] forgot to mention in that PM something about the device security in place. See another PM for details.
[SuperSU] Chainfire:
I think that lagging issue has been found and solved. Discussion should move to the BETA/SR thread, as SR1 will be released soon.
[SuperSU] Jole7:
[MENTION=631273]Chainfire[/MENTION] please take a look with the next update the problem that Super SU cannot be install with F2FS filesystem on data device OnePlus 3. Thanks in advance.
[SuperSU] championc:
Is a particular version of TWRP needed ? I appear to have bricked my LG G3 after flashing 2.79. My TWRP is 2.8.0.0. I now have "Secure Boot Error"
[SuperSU] Einwod:
I think your twrp version is well out of date.
[SuperSU] championc:
I got it fixed by flashing 2.78 SR1 followed by Mr. Bump (not sure as to what that's for exactly) so i suppose there is a questionmark over 2.79 on an LG-G3
[SuperSU] zaibansari20:
I installed 2.79 zip through recovery and su was installed in system-less mode.

After few days I lost root. Supersu was running good but after some time it asked me to update binary but failed.

I reflashed the zip to get root.

It happened to me twice.

---------- Post added at 07:47 AM ---------- Previous post was at 07:24 AM ----------

Just lost root after restart

What should be the problem [MENTION=631273]Chainfire[/MENTION]
[SuperSU] championc:
I've just been prompted to update the SuperSU binary. At this moment in time, i'm going to leave things alone.

But is there a way to stop it from trying to update itself ?
[SuperSU] grep_i:
Maybe you can try and install 2.79 via ADB sideload
[SuperSU] arifincaesar:
not work

why not working on my phone vivo y28..

i want to root please help me ;)
[SuperSU] Demicro:
I install SuperSu 2.79 systemless mode

But now I do not have root access, with the beta had no problem

Previously

I delete Su.img and restore default kernel

Samsung Galaxy J510FN MM stock rom
[SuperSU] shaggyskunk:
Google is your friend - Helping yourself by Searching the Thread and Google is a good way to start ;)

Sent From My SM-N910W8 ??
[SuperSU] jdegreef:
What did you do during these few days ?

You probably made something that causes root to be lost.

Reflashing the latest zip via TWRP should solve your problem.
[SuperSU] championc:
I flashed 2.79 and it bricked my phone. I got it back with 2.78 sr1. So i really don't want to try 2.79 again right now
[SuperSU] shaggyskunk:
Obviously v2.79 didn't "brick" your phone.... Just sayin'.

Sent From My SM-N910W8 ??
[SuperSU] Demicro:
The problem is in the custom_ramdisk_patch.sh

I deleted it from /data

#!/system/bin/sh

SYSTEMLIB=/system/lib

if [ -d /system/lib64 ]; then

SYSTEMLIB=/system/lib64

fi

# extract files

LD_LIBRARY_PATH=$SYSTEMLIB /su/bin/sukernel --cpio-extract $1 init.environ.rc /sutmp/init.environ.rc

LD_LIBRARY_PATH=$SYSTEMLIB /su/bin/sukernel --cpio-extract $1 sbin/launch_daemonsu.sh /sutmp/launch_daemonsu.sh

# patch init.environ.rc

sed '/export PATH \/su\/bin/s/^/#/g' -i /sutmp/init.environ.rc

# patch launch_daemonsu.sh

sed '3iexport PATH=/su/bin:/sbin:/vendor/bin:/system/sbin:/system/bin:/su/xbin:/system/xbin' -i /sutmp/launch_daemonsu.sh

# push back files

LD_LIBRARY_PATH=$SYSTEMLIB /su/bin/sukernel --cpio-add $1 $1 750 init.environ.rc /sutmp/init.environ.rc

LD_LIBRARY_PATH=$SYSTEMLIB /su/bin/sukernel --cpio-add $1 $1 750 sbin/launch_daemonsu.sh /sutmp/launch_daemonsu.sh

# link supolicy to /su/xbin_bind

ln -s /su/bin/supolicy /su/xbin_bind/supolicy

exit 0
[SuperSU] championc:
I ended up with a "secure boot error" and the phone wouldn't boot. Agreed, you were technically correct :)
[SuperSU] zaibansari20:
I Installed Magisk v9

It also do boot modification

Do you think this can be causing the problem?
[SuperSU] hanygrandaton:
Rooting MATE 8

Thanks For Your Reply , But I Want To Tell you that I Have Done What You said , I Used TWRP To Flash The Supersu Zip File , But It Exits Without Completing The Flash Process
[SuperSU] Chainfire:
G3's need to run a 'bump' script after flashing a custom boot image, which is what SuperSU does. This is well known and has nothing to do with SuperSU.
[SuperSU] Portgas D. Ace:
Could you post a screenshot and/or the recovery log so that we can have a closer look?
[SuperSU] jdegreef:
I understand. :D

I think this is for someone with a better knowledge of Supersu then.

Your recovery.log might be of some help.

---------- Post added at 05:18 PM ---------- Previous post was at 05:07 PM ----------

This IS the cause.

AFAIK Magisk need a special su (phh superuser). It don't work with Supersu

Re-read the OP of Magisk.
[SuperSU] championc:
Ok. So 2.79 should be ok with Mr.Bump yes ?
[SuperSU] zaibansari20:
Magisk thread says that you either need supersu system-less or phh superuser
[SuperSU] maximusmullivan:
You should have just updated from the play store. Now you'll have to TOT or KDZ to fix your phone.
[SuperSU] Ch3vr0n:
afaik no he doesn't. All he needs to do is flash that LG kernel bump script and he should be good to go. LG kernels need to be "bumped" to boot after flashing SU
[SuperSU] jdegreef:
Yes but if you use Supersu it seems you should flash it BEFORE you install Magisk.
[SuperSU] Elanza_48:
Sir I'm unable to set pin on the superSU v2.79 running on cm 14.1. please help
[SuperSU] zaibansari20:
yeah I flashed it before Magisk v9 zip

but after some time of Power On root is gone
[SuperSU] jdegreef:
Well In your place I would make a backup and start afresh in the right order (noting each point of the process for memory) and see if you can reproduce the problem and at which step it happens. I would also keep the recovery.log of each step.
[SuperSU] vygavedha:
Can i install the latest zip in CM 14.1 ? Any guidelines for flashing it?
[SuperSU] Ibuprophen:
Unless you're well versed with the Android system, I, personally, would recommend you flashing the Stable SuperSU 2.79 and only flash the SR1 if you really need to.

The SR's are actually an alpha version for testing purposes for those who are experiencing some type of issues with the Stable release.

This is only my, personal, recommendation. You can flash it if you want since it is compatible with the Nougat.

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

Sent from my Communicator (SCH-I535) on the Bridge of the U.S.S. Enterprise (N.C.C. 1701).
[SuperSU] silvercat:
Flashing SuperSU in system mode ends up in bootloop and forcing it to flash in systemless mode (correct syntax : echo "SYSTEMLESS=true" >>/data/. supersu) fail to patch boot.img and no root after reboot. [emoji52]
[SuperSU] zaibansari20:
I got an Update for CM 14.1 yesterday, so I flashed it and went to system-mode of SuperSu cause I was facing the same problem before.

I think the v2.79 is not so good in systemless mode.
[SuperSU] jdegreef:
I never had any problem with systemless mode, neither on CM 13 and 14.x or RR 5.8.0. But I don't use Magisk (yet).
[SuperSU] PeterMayers08:
Update/ clear log icons disappear

There is a little glitch in the su gui. When changing from log tab to settings tab and switching back to log tab, the icons for refresh and clear log are gone. The only way to get them back is restarting the app. Thank you for all the efforts you are putting in maintaining and improving this essential tool! Really appreciate it.
[SuperSU] permutations:
My Nexus 10 said that SuperSU needed to be updated. I let it update. Now my Nexus 10 is in a bootloop. This just happened, so I assume it was your latest version (2.79) that killed it. I haven't updated SuperSU since v2.65, so I'm not sure which version contained the Nexus 10 killing change. Since v2.65 worked just fine, I'm going to try to figure out how to reinstall that. Not sure why you decided to "fix" something that wasn't broken. :(

----------

Edit: I reinstalled SuperSU v2.65, and now my Nexus 10 is booting up again. :)
[SuperSU] Ch3vr0n:
Well, had you kept up with the SuperSU versions it would have been a lot easier to figure out where things went wrong for you. I know there have been a few versions greater than 2.65 that were issued through the play store. No clue how you could have stuck with 2.65 unless you reverted every time.

Sent from my Nexus 6P with Tapatalk.
[SuperSU] Ibuprophen:
I also had Bootloop issues with my GS4 when the SuperSU 2.78 was flash installed and then the app had updated from the Play Store then the Scripts were installed via the app.

I couldn't locate anything weather or not [MENTION=4419114]rovo89[/MENTION] had addressed any issues as to when the SuperSU is flashed as a system app and, when it updates via the Play Store, it updates the app as as user app that can result with any issues if the scripts were updated via the app.

Tried my best to explain it. Basically the SuperSU originally is flashed, with the scripts. Then the updated SuperSU, from the Play Store, updates it and changes it from a system app to a user app. Then updating the scripts via the app results in a bootloop.

Sent from my Communicator (SCH-I535) on the Bridge of the U.S.S. Enterprise (N.C.C. 1701).
[SuperSU] swallowingled:
I've had no issues with 2.79 on my Nexus 10 but I upgraded from 2.78.
[SuperSU] Ch3vr0n:
I'm pretty sure the play store updates the app exactly as it is. If system, it updates and it's still a system app. If user app it remains a user app. I'm by no means an expert but I can't imagine a play store app update changing from system to user. That could cause a while crapload of space issues on low storage devices that use an SD card for expansion. I'd be the one that decides what goes on SD. Not the play store.
[SuperSU] m0han:
try deleting supersu folder from recovery and flashing the latest zip. you should get systemless mode that way. once i forgot to delete supersu folder, but i still got 'systemless'. no need to type any codes :D

---------- Post added at 09:40 AM ---------- Previous post was at 09:39 AM ----------

this is true for me too.
[SuperSU] permutations:
I have a worse problem than I realized. I resolved the boot-loop problem by flashing the SuperSU 2.65 zip in TWRP. But I'm no longer rooted. I've done it 3 times now, and no joy. I re-downloaded the file and cleared davlik and cache, but still no SuperSU icon (or root access) when I reboot, though TWRP reports successful installation. I can't figure out what's going on. I've done this many times before with no problems. The bootloader is unlocked and I want root access. What could be wrong?

---------- Post added 25th December 2016 at 12:09 AM ---------- Previous post was 24th December 2016 at 11:53 PM ----------

Hmmm... I flashed SuperSU in system mode (not knowing there was any other kind of mode) and ended up in a bootloop, too. So I wonder if your advice is relevant to me. Did boot.img get patched when I innocently okayed the upgrade? I don't want boot.img to be touched. That's probably why nothing is working anymore. Maybe I need to use TWRP to replace a corrupted boot.img, delete the supersu folder, and THEN reinstall v2.65. I don't need or want the changes in the versions that came later. A change to boot.img is too intrusive. I don't want that. It was working fine. I don't want the core OS files to be touched.
[SuperSU] culiacanazo:
It's not a change, it's a PATCH.

Magisk will patch it too, and the way things are looking up as of late, if you hope to upgrade AND continue to remain rooted you will have to at least patch sooner or later here or there
[SuperSU] permutations:
Saying "It's not a change, it's a PATCH" is like saying, "It's not a fruit, it's an APPLE".

A patch is a kind of change - a particularly dangerous kind if you're patching a binary and don't own the original code because it's made relatively blind (basically through trial and error). For my purposes, the cost of that risk isn't worth the benefit.

I like to have root access because every once in a while, there's something specific that I want to do that I can't do without root. For example, right now I want to to text from my Nexus 10 (which has no cellular connection) using the latest iOS emojis. I have never liked the Android emojis. PushBullet lets me text from the Nexus 10, thought it's not a phone, and if I have root access, I can give it system-wide access to iOS emojis. I've used root access for a variety of other things as well. But I'm not one of those people who installs Xposed with no purpose in mind and spends hours pouring over pointless tweaks. I've never wanted to do something that I couldn't do with system rooting, versus a risky system patch that hides root. The only app that ever had complained about my Nexus 10 being rooted was the Playstation Vue Mobile app, and I found a workaround. I forgot how I did it.

As for updates... The Nexus 10 is ancient. Android 5.1.1 is the last system update it will ever get. I bought it the day it was released, and it's now so old that the battery can't hold a change - at all. But I still love it. There aren't very many 10" Android notebooks on the market anymore - if any. It has the perfect form factor for watching movies, it's super light-weight, and it's has a fantastic display.

I reflashed boot.img, then reflashed SuperSU 2.65 and rewiped the davlik and cache. I've been writing all this while waiting for the Nexus 10 to reboot and... No joy. (((sob))) Why can't I root it anymore???? :(

---------- Post added at 01:26 AM ---------- Previous post was at 01:17 AM ----------

Well, this is a nightmare, and a really sucky way to spend Christmas Eve. Whatever v2.79 did to my Nexus 10, I can't go backwards. I'll try installing v2.79 again. Probably I'll end up in another boot loop. I'm hating SuperSU right now. Does the author provide support?
[SuperSU] culiacanazo:
Well, having a collector's device i wouldn't risk it either.

Once you do boot back into android do not upgrade supersu as it's mostly being developed with the nougat changes in mind, and since you're lollipop i personally see no benefit...

Did you manually erase the su.img from /data?

Added: Did you have no nandroid?
[SuperSU] jcmm11:
He's not patching the binary. It's the ramdisk.

If you want to go backwards and make sure it's all clean flash Osmosis's unSU file, wipe boot and system, dirty flash your ROM, go from there.
[SuperSU] permutations:
After 6+ attempts with v2.65, which appeared to flash successfully but no SuperSU icon and no root, I gave up and flashed v2.79. Happily no bootloop, but also no root. I guess I'll never have root again. Plus I had a horrible Christmas Eve. :(

---------- Post added at 04:31 AM ---------- Previous post was at 04:19 AM ----------

Oh good. That makes me feel a lot better about it. Except for the fact that it's not working, of course. :confused:

I've been deleting the SuperSU directory before reinstalling. I thought there might be more to it. I'll look for Osmosis's unSU file, thanks.

By "wipe boot and system" do you mean reflash boot.img and system.img? I reflashed boot.img, but not system.img.

What do you mean by "dirty flash your ROM"?

Thanks for your help!!

---------- Post added at 04:34 AM ---------- Previous post was at 04:31 AM ----------

(I'm going with v2.79 now, since it's no longer causing a bootloop and it doesn't modify system files.)
[SuperSU] coukou:
Hello,

I've a Samsung Galaxy Note 4 SM-910C ROM XEH-N910CXXU2DPE6_N910COXX2DPE2 v6.0.1. I'm using SuperSU since while and installed it with TWRP.

Today, SuperSU invite me installing the v2.79 update through the play store. Since I updated SuperSU I've the here bellow message "Samsung KNOX has been detected. This might limit root capabilities and cause annoying popups. Try to disable KNOX ?"

What that message means?

For the moment I press "CANCEL". I did not disable KNOX for fear of blocking/freezing my smartphone.

Do I've to disable KNOX?

I'll appreciate any help
[SuperSU] Sojourner353:
Yes best to disable it, won't cause any issues.
[SuperSU] jcmm11:
Wipe boot partition, wipe system partition, flash ROM, flash boot, do not wipe data partition. That equals dirty flash. Clean flash you also wipe data partition, which means reinstalling all apps.
[SuperSU] culiacanazo:
Or before taking that bigger step he could just have a look at his/data folder... I know no root, but just a peek... Won't hurt, and it can help.

As long as you got a custom recovery you're cool, could try king's solution just to deposit the binaries, and then change to SuperSU or whatever rocks your boat
[SuperSU] egingell:
Deleting the SuperSu folder? From TWRP? The folder that only exists in TWRP? That folder is only used when you let TWRP install its version of root. It doesn't exist otherwise.

Dirty flash = flashing the ROM without wiping data.

Sent from: LG G4 MM 6.0 / SGS5 MM 6.0.1
[SuperSU] culiacanazo:
Most likely it'll be "blocked/frozen" if you DON'T (disable it).

I'll go ahead and take advantage of this space to rant/"educate" some ppl just a little.

When you get your phone out of the box for the first time, and turn it on and get this "Congratulations, we love you so much and you mean so much to us that we've (yes, already!) sent you an update!!" They're not doing it because you (we) mean the world to them.

Sure, for some (or most) it's a good thing because all it's doing it's protecting your phone from the biggest danger, YOU! But being that you're here (at XDA) tells me you want to take full ownership of your device (at your responsibility)... So! This is where Google, the OEMs, and the carriers, start to stink.

To cut to the chase, if they REALLY cared about us users, don't you think they'd give is ALL THE updates? for example, if it weren't for the developing scene, my S5 would forever have been stuck in Marshmallow! Why? Buy a new one!

If they really cared about you and not just their pockets disguised as "it's about you", they would give you a way out of all that bloat.

Why conceal features that, the manufacturer assigns to a given model, when they're built in? (One example is me having native video calling in a STOCK TW for an S4 when T-mobile was telling me that to get it, i would have had to get the S6)... Just to name a few.... And when i say a few, i mean exactly that.... I won't go over the (ALL NATIVE - device dependant) tunable (offline) radio, tether, call recording, caller Id blocking, WiFi calling, download booster, sip integration, (system-wide vs just divert to vm or silencing it) call blocking, network locking (subsidies being irrelevant!), vpn (remember, the keyword here is NATIVE!)

So in short, no! KNOX is not really looking out for you, just like "outlook" and especially Google core aren't either when they repel apps such as towelroot, for example... KNOX isn't, at least not in this case anyway!
[SuperSU] coukou:
TNX both Sojourner353 and culiacanazo for yr advice ;)
[SuperSU] jdegreef:
@Chainfire

I can reproduce this too. It's definitely a bug. A small bug :)

Thanks for your work.
[SuperSU] grep_i:
Okay so this happens to more people, I thought I f-ed something up.