yashsingh1/xdaforums huggingface dataset:
[SuperSU] macasus76:
[MENTION=631273]Chainfire[/MENTION] Does this zip install as system or systemless?

I have issues with systemless and prefer a system root.
[SuperSU] edzamber:
Hi,

Flash this by Custom Recovery as TWRP

https://www.mediafire.com/download/ltw0b0o6kc67d64

Then directly SuperSu v2.79 update and Reboot.

It will be installed into System Mode.
[SuperSU] macasus76:
I already have it installed as a system app and updated, thanks for the link but I honestly prefer an official download from a trusted source when it comes to apps like this but thank you. My question was does this particular zip file that the author and or chainfire provided installs supersu as system app. Just backed up my phone and going to test myself lol.
[SuperSU] edzamber:
It is not a modified SuperSu but a System Mode enabler script that i have done. It write SYSTEMLESS=false into /data/.supersu

In this way, when you flashing Chainfire SuperSu update by Recovery it will be automaticly installed into System Mode
[SuperSU] macasus76:
And.......it's systemless. Thanks for the explanation to your file, I will have to give that a try.

Not sure why I hate systemless so much but I do......
[SuperSU] radz_:
Damn! It worked for me.. that was easy!

I have a kernel that only works with system mode.

My phone boot after flashing this..

Thanks a lot.. will this work for future updates?
[SuperSU] Portgas D. Ace:
If you are suspicious about flashing a script from an unknown source, you can manually create the ".supersu" file by using TWRP's terminal. Just type

echo SYSTEMLESS=false>>\data\.supersu

and confirm with enter button. Should set the installation mode to system instead of systemless.

I think the script from above does exactly this.
[SuperSU] radz_:
Folks, i can confirm the script from [MENTION=4507636]edzamber[/MENTION] works as system mode.

I have Samsung 6.0.1, my kernel only works with system mode supersu. If i flash Systemless my phone wont boot up at all..

The script works smooth....
[SuperSU] andu86:
if i have supersu 2.78 sr3 systemless, is it safe to update via google play ?

will it keep my supersu systemless ?
[SuperSU] Portgas D. Ace:
Yes, the Google Play Store update just updates the app itself, not the su files and binaries (which will stay in systemless mode).
[SuperSU] macasus76:
Thanks everyone for your help and explanations!
[SuperSU] Ja_som:
On my Nexus 5X it also updated binaries...
[SuperSU] culiacanazo:
But it won't change the mode that was already chosen before you hit update in the Play Store
[SuperSU] Ja_som:
Yes, but he wrote, that app will not update binaries, so I only said that on my device they was updated ;)
[SuperSU] A$h!$h:
flashable SuperSU_v2.79.zip

https://drive.google.com/file/d/0B0xYAxRQ4bajTnhpdlJ2Z0padmM/view?usp=drivesdk
[SuperSU] Ch3vr0n:
Why provide an unofficial mirror on a random Google drive when chainfire himself already provided an official download on his site in post 670?

Sent from my Nexus 6P with Tapatalk.
[SuperSU] Hell Hranica:
v2.79 STABLE Will this version work with RR5.8.0?
[SuperSU] :
2.79 doesn't work on my Galaxy s7 with nougat beta4. Brightness is set to high and can't be lowered and torch doesn't work
[SuperSU] beerbaronstatic:
Having issues installing 2.79, Pixel XL, flashed the latest boot.img from Google image, booted into TWRP RC1, flashed 2.79 (tried the one hosted at the AWS link and the link posted by Chainfire). No errors executing, says things completed successfully but when I reboot, no SuperSU anywhere. Things were working fine with RC5, any thoughts?

Edit:

Appears the solution is in TWRP go to Advanced -> File Manager -> delete fstab.marlin or sailfish (I just moved it in case I needed to restore), installed fine after that
[SuperSU] Xp3riaXpr3ss:
I'm currently using custom rom based on Nougat Beta-4 with SuperSU system-less root on S7 Edge. I tried to install v2.79 by flashing zip via TWRP but ended up breaking camera app and torchlight.

Eventually this is what worked for me.

1. Select 'Reinstall' under SuperSU settings. SuperSU will be cleaned up with app removed. Phone will auto-reboot.

2. Install SuperSU from Google Play. Update binaries when prompted.

S7 flat could be different but I hope the above helps.
[SuperSU] Onlyoncebutmaybetwice:
Works well on my boost mobile galaxy J7..
[SuperSU] Abnova:
Although im on android 6.0, super su always installs into system mode. Also is it normal for the super su app to be deleted Everytime you flash a super su zip through recovery?

Thanks
[SuperSU] :
I'll try, thanks man
[SuperSU] Portgas D. Ace:
Updating the binaries is done by the app itself, not by Play Store.
[SuperSU] Mesmurized:
Flashed the zip on system-mode 6.0.1. No problems.
[SuperSU] jdegreef:
No problem up until now :)
[SuperSU] Ch3vr0n:
[MENTION=631273]Chainfire[/MENTION] Exactly what i expected to happen with 2.79 DID happen after flashing with SuperSU. The installation updates my existing SR1 but the buck stops there. Every subsequent release since then doesn't work on my 6P. Root checker doesn't get root access (claims system is not responding), no apps do for that matter. The system is terribly slow as i reported in the past. I provided multiple logs but i never did see any response to it or a solution. So here i am again, reporting the same problem. Flashfire log & syslog attached. Reflashing SR1 instantly fixes the problem.

I'm running STOCK ANDROID on my 6P, no xposed, not any customisations other than twrp.

syslog link: https://drive.google.com/open?id=0B_kYcBALPkwEVF9kYUtzVjlIVG8

Flashfire log: attached.

The weird thing is: that updating the APK through the play store and updating the binairies through the NORMAL method DOES work and results in working root access. So far at least. Syslog after doing that attached in the following link: https://drive.google.com/open?id=0B_kYcBALPkwEVUwtWV83c3NYNkU
[SuperSU] FlyingHorseGA:
Can you provide MD5 and SHA1 checksums please? It helps me feel better ?
[SuperSU] drothenberger:
I am having a similar problem on my 6P running December 7.1.1.

When I updated to 7.1.1, I had to flash 2.78 to get root. That worked fine for me. This morning, SuperSU APK updated 2.79. I tried updating binaries through the app and that succeeded but I lost root.

I then tried flashing stock boot.img, system.img, and UnSU.zip, then flashing 2.78. Everything flashed fine, but I did not have root after reboot. SuperSU APK did not complain at all, but no apps could get root and eventually the system slowed to a halt.

I did eventually discover that I could get things working but setting SuperSU to grant root access to all apps instead of prompting me about it. This worked for me with 2.78 but not with 2.79. In this mode, the Apps tab in the SuperSU app does not show anything, although the logs do show applications getting root access. This may be expected behavior with this configuration - I'm not sure.

I'm out of ideas about what to do next short of a full wipe.
[SuperSU] jdegreef:
Did you ever try to completely unroot your phone and then flash the latest release ?

I have the feeling that flashing older version over newest version and then older version over newest version lead to a big mess.

I would never flash an older version over a newest one without first unrooting.

Following this thead since a few months I think it's what cause a lot of problems : upgrading, downgrading, flashing this and that without never starting from a clean situation.

BTW, if the Play Store version works ok why bother ?
[SuperSU] drothenberger:
I personally tried that and it didn't work for me. Also, for me, updating the binaries through the Play Store app didn't work either.
[SuperSU] jdegreef:
I don't see where you started flashing 2.79 from something clean.
[SuperSU] grep_i:
I don't think that's the problem as I do this myself all the time flashing different versions older than newer and than older without fresh cleaning and it always keeps working but my device is Nexus 5, the issue could be rom or device specific.
[SuperSU] lenoid:
I updated today via Playstore to v2.79 and updated the binary manually (normal mode) on my Galaxy Note 8.0 GT-N5110 (Android 4.1.2 Stock). After trying to install another app from Playstore my Note 8.0 rebooted by itself and now it's in a bootloop. It's booting up until the Samsung launcher, freezes for a minute an reboots. :crying:

Well, I updated some other apps too, but these were just simple normal apps. So I'm pretty sure that SuperSU is the problem.

How to solve this problem? :confused:
[SuperSU] shaggyskunk:
Doubt that it's SuperSU... No issues on 4 different devices.

If you're stuck in a loop - Factory Reset - Advanced in TWRP - Manually Wipe System - Data and Caches - Flash Rom (and Gapps if applicable)Flash SuperSU - Reboot and setup

Sent From My SM-N910W8 ??
[SuperSU] Ch3vr0n:
[MENTION=5504709]jdegreef[/MENTION] i never downgrade, upgrade, i always only went up. After failing SR2 i never even flashed the other ones figured next release might fix it. Guess not. Why bother? Cause i wanna know where the problem lies. Maybe there's a bug in the code routine somewhere.
[SuperSU] drothenberger:
I did a full uninstall from SuperSU, flashed UnSU.zip, and the stock boot.img and stock.img. I think that's as clean as I can get without wiping user data, right?
[SuperSU] lenoid:
But what could cause it?

Is there a way without factory reset? I don't wanna loose my data.
[SuperSU] shaggyskunk:
Could be anything that caused it - You could always try booting into Recovery and ONLY wiping System and Caches - Flash Rom and Gapps (if required) Flash SuperSU - Reboot and see what happens.

Sent From My SM-N910W8 ??
[SuperSU] Cares:
Does the Pixel upgrade from the Play Store?
[SuperSU] Respectful:
Compatability

Hi,

Is this rooting thread for "HTC 10 Android 7" please?

Thank you
[SuperSU] betahaedar:
is the latest 2.79 compatible with 7.1.1? or is it only compatible with 7.0?

thanks
[SuperSU] shaggyskunk:
No issues with v2.79 on multiple devices running 7.1.1 AOSP & CM14.1 Based Roms.

Sent From My SM-N910W8 ðŸ‡¨ðŸ‡¦
[SuperSU] neutronizer:
This is a newbie question :D

I already update supersu 2.79 from playstore, but failed to update binary.

I install supersu 2.79 from recovery TWRP (I don't understand the log but in the end it is "done"), wipe cache, and restart system, there is no problem when update.

But supersu still notif me to update binary and still failed (I think it will overwrite su playstore with su recovery but not) when I check root it is rooted but with supersu 2.78.

So I decided to uninstall supersu from playstore and install again from recovery, but the checker still said I use supersu 2.78 not 2.79, and there is no supersu GUI application on my android.

So for master, this newbie need the answer and solution for this problem.

Sorry for my english.

HTC Desire Eye, S.ROM 2.0.1
[SuperSU] ipdev:
[MENTION=6747155]neutronizer[/MENTION]

You can grab the .apk from the common folder inside of the .zip (Superuser.apk) and install it. If you are able to, select Full unroot in the app settings, reboot into twrp and wipe caches and reflash the SuperSU-v2.79-201612051815.zip.

(Some of my devices don't like wipes before or after flashing SuperSU.)

(By the way, it helps if you tell what device, rom, ect. you are running. ;) )
[SuperSU] king718:
I'm not sure what I am doing wrong. Flashed TWRP. Flashed supersu Zip file. Says :

-mounting /system, /data and rootfs

-extracting files

-system mode

-disabling ota survival

-removing old files

-creating space

-placing files

-restoring files

-post-installation script

-unmounting/system

-Done !

Updating partition details....

....done

But then there is no supersu app in my phone and there is no root...

What am i doing wrong?
[SuperSU] Portgas D. Ace:
Have a look at the HTC 10 subforum, there you'll find your answer:

HTC 10 Subforum

EDIT: saw that you already posted there and your device is set up properly (unlocked bootloader, S-OFF, TWRP). So just download the SuperSU.zip file (linked in first post) and flash it in recovery. But remember to make a backup before flashing.
[SuperSU] neutronizer:
[MENTION=7280276]ipdev[/MENTION]

Thanks for your help, the problem is wipe after reflash SuperSU 2.79. :laugh:
[SuperSU] Abnova:
You just need to reinstall the super user app
[SuperSU] neutronizer:
[MENTION=4699307]king718[/MENTION] Have you check with Root Verifier/Root Checker? Maybe your problem is same with me.

On TWRP, first wipe cache, reflash/install SuperSU 2.79, and the point is don't wipe, just restart your system.

If there is no SuperSU application on your device, just open the SuperSU 2.79 (zip file), go to common folder and install Superuser.apk :good:
[SuperSU] king718:
Still no app, Installed the apk from the zip like you said and got this:

"There is no SU binary installed, and superSU cannot install it. This is a problem! If you just upgraded to android 5.0 you need to manually re-root - consult the relevant lforums for your device!
[SuperSU] jja2000:
Are your using f2fs by any chance? Supersu doesn't seem to like that for some reason. I guess that's something Chainfire/CCMT needs to fix...
[SuperSU] thiago.net:
Works on Moto G4 XT1626 Andoid 7.0 NPJ25.93-11?
[SuperSU] king718:
How do I check and how can I change it ?
[SuperSU] jja2000:
What phone are you using?
[SuperSU] Ibuprophen:
Please correct me if I am wrong...

In order for SuperSU to install the required codes conventionally (via the app) doesn't SuperSU have to be able to temporarily change the systems selinux state from enforcing to permissive?

Sent from my D2VZW on the Bridge of the U.S.S. Enterprise.
[SuperSU] king718:
Pixel XL
[SuperSU] varazir:
Maybe someone has asked this before if not and this is not the correct forum please point me in the right direction.

Could you add to the app a way to download the latest stable or beta zip file like the gapps team have done?
[SuperSU] Sebastl:
For me 2.78sr5 -> 2.79 over playstore was also hanging at the binary update process. Had to activate namespace mounting again. Maybe it helps someone ;)
[SuperSU] Hedied4me:
Yeah I kept getting that hanging also when updating in the Playstore from 2.78 sr5 to 2.79. I ended up dirty flashing ROM with 2.79 zip no problems.
[SuperSU] D1stRU3T0R:
How I can install this? On google play it show me error 505, apk install fail... I have TWRP, but how i can update supersu whit it? (step by step flash)
[SuperSU] shaggyskunk:
Boot into TWRP Recovery and Flash the SuperSU zip... Reboot

Sent From My SM-N910W8 ??
[SuperSU] king718:
checked with the app "diskinfo" and the file system is called ext4
[SuperSU] D1stRU3T0R:
Lol, i flashed it whit twrp and nothing happend, still the old 2.78...and I used the link given in the first post... What i did wrong? Boot to twrp, install, selected that zip, wipe to flash, reboot..
[SuperSU] grep_i:
Yes you're wrong
[SuperSU] shaggyskunk:
Did you Flash this zip that Chainfire posted here:

http://xdaforums.com/showthread.php?p=70100680

In Recovery did TWRP say that you were successful in Flashing the zip?

There's nothing more to it than that.

Sent From My SM-N910W8 ??
[SuperSU] D1stRU3T0R:
I tried whit the zip from the first page, it said successful, but when I checked it, it was still 2.78, I installed the zip from your link, it said that it's done, rebooted, checked and still 2.78
[SuperSU] shaggyskunk:
What device and TWRP version are you using?

Sent From My SM-N910W8 ??
[SuperSU] D1stRU3T0R:
Huawei p8 lite, twrp 3.0.2.. I installed kernel via twrp, root via twrp and it worked
[SuperSU] Thomas_BA:
I am on Moto X Style with Stock 6 Rom. Have systemless root, flashed the 2.79 over 2.78, after that the systemless xposed and everything works as it should.

Thanks
[SuperSU] Respectful:
Compatability

Hi,

Is this 2.79 for Android 7 on Htc 10?

Thank you
[SuperSU] shaggyskunk:
Yeah I've no idea why it's not working for you - No issues on 3 Different Samsung devices running 7.1.1 and a Nexus device also running 7.1.1 - All using TWRP 3.0.2-0.

Maybe someone else will chime in.

Sent From My SM-N910W8 ðŸ‡¨ðŸ‡¦
[SuperSU] Crazy Chuckster:
Just so I have this correct if I am on 2.78 SR5 on my Nexus 5x I can just update via Google Play and it will be fine?
[SuperSU] _alexndr:
Same here @ G935F :( and also camera doesn't work

IMHO it is only weak "workaround" - you skipped kernel re-patching using the newest sukernel/supolicy contained in 2.79 ZIP so it is NOT a complete update according to [MENTION=631273]Chainfire[/MENTION]'s recommendations
[SuperSU] drothenberger:
I was able to solve my problem using the hint from [MENTION=6747155]neutronizer[/MENTION]. I flashed unsu.zip, the stock boot.img, wiped cache, then installed 2.79. Everything is now working fine.
[SuperSU] Xp3riaXpr3ss:
Fair point, nonetheless, it serves as a temp workaround to revive sensors until devs mod 2.79 to work with their respective roms.

The camera and torchlight are important functions.
[SuperSU] ulxerker:
yes, you can use it on that device.
[SuperSU] _alexndr:
[MENTION=631273]Chainfire[/MENTION], one more thing - I noticed that original file_contexts.bin has binary format while patched file_contexts.bin (containing context for /su(/.*)?) has text format despite the file extension. Is it intended?
[SuperSU] Xp3riaXpr3ss:
Tested over a couple of Nougat-based ROMs on G935FD. Selected permanent unroot option in SuperSU settings, reinstalled by flashing the zip in recovery mode and didn't break anything. Camera, torchlight, brightness working fine.
[SuperSU] Chainfire:
[MENTION=5150393]_alexndr[/MENTION] [MENTION=6713660]Black_Focus_X[/MENTION] [MENTION=7792208]Xp3riaXpr3ss[/MENTION]

Re: the Samsung Nougat Beta issues, please report to the BETA thread - http://xdaforums.com/showpost.php?p=70146088&postcount=8450
[SuperSU] denilriveraa:
Already running on Asus Zenfone 2 MM?
[SuperSU] techguy348:
the latest version of supersu is very broken on my samsung galaxy note 4 on cyanogenmod 13.1... Once in a while when an app opens or does a task, it freezes the phone and crashes it to thr bootloader.
[SuperSU] scottfreeze:
I'm having the identical problem on Nexus 5x, stock ROM with elementalX kernel. Apps fail to get root and the system slows to a crawl on 2.78 SR3 and later, including 2.79 stable (I never tried SR1 or SR2, so I don't know if those were problematic). Reflashing 2.78 stable works fine, solves the problem. Guess I'll stick with 2.78 until this gets resolved.
[SuperSU] ddrum2000:
I have a similar issue as well. I have a Nexus 5X, 7.1.1, NMF26F, stock rooted, TWRP 3.0.2-3. The flashable zip seems to install fine but upon rebooting the system can't access SU. I guess maybe the binary isn't being installed properly. This has happened with all versions SuperSU after 2.78 SR1 (which does work correctly for me). Any pieces of advice?
[SuperSU] CrazyCypher:
Hy guys, I am using SuperSU pro on my HTC 10 and I want OTA survival to be working... Is anyone already successfully had SuperSU still working after OTA? On HTC 10?

I have stock ROM with TWRP (for now) and SuperSU, Magisk and Xposed. If I flash stock recovery, will I be able to normally receive OTA and apply it and after a reboot still have SuperSU? That way I can re-install Magisk with Xposed without flashing SuperSU again?

Thank you for your answers, I really appreciate it
[SuperSU] Ch3vr0n:
[MENTION=3151044]scottfreeze[/MENTION] I reflashed sr1, then updated to 2.79 though the play store and let the apk update the binaries the 'normal' way. Still no issues. I've got no idea why anything beyond 2.78 SR1 makes the device lock up. Still hoping [MENTION=631273]Chainfire[/MENTION] will find something in the logs I've provided a few times now.
[SuperSU] scottfreeze:
[MENTION=1754043]Ch3vr0n[/MENTION] Thanks for the reply. I'll try again, but after I diverted the problem the first time with SR3, I downgraded to 2.78 stable. I was running 2.78 stable until the SU app notified me of the updated binary. I let the app update to 2.79, and upon reboot I had all the same problems with the system being unusably slow and no apps being able to get root.
[SuperSU] Chainfire:
It's hard to be exactly sure from these logs, but it seems like something is calling 'su' in a loop, yet never getting access.

Those are usually permission errors. You could try manually uninstalling the apk ('adb uninstall eu.chainfire.supersu'), manually removing /data/su.img, reflashing stock boot/recovery images, then rooting again with TWRP and the ZIP, just to see if that helps.

I've looked again at all the code changes between SR1 and SR2, but nothing obvious stands out that could cause this.

Other than that, which exact 6P firmware are you running? And which root apps do you have installed? I can try to replicate your setup as close as possible.

Additionally, as root, see if this command makes any difference:

supolicy --live "allow shell shell capability dac_override"
[SuperSU] Lennoard:
I might be wrong but latest v2.79 is taking 3 days to grant root access.

And something for [MENTION=631273]Chainfire[/MENTION]

Is the LibSuperUser being affected by SuperSU updates?

Android 7.
[SuperSU] matlala:
I have the same problem like some other people: device very slowly and unusable after upgrade. I can't get supersu prompt window for grant root acces.

I tried upgrade binary from regular updated app from play store and after I tried reflash in latest twrp. Both have same effect. Finally, i tryed on clean install (reflash all partitions, format data for decrypt, reboot to twrp and flash supersu zip). I have nexus: 6P (without problem - update binary from app and flash zip, both is working). N7 2013 and N5X is very lagging after update (binary or flash zip in twrp).

On N5X i tried clean flash, install in TWRP and it is working. Why? Whitch folders i can try delete from TWRP? If i unistall supersu from android app, reboot into twrp and delete /supersu folder, reboot recovery and flash. But is not working yet.
[SuperSU] ddrum2000:
So what do you mean by clean flash? I can flash boot, cache, system, vendor, TWRP for recovery, but I dont want to wipe data. I there something that I need to delete out of /data?
[SuperSU] matlala:
Yes, reflash system, vendor, boot, twrp, format userdata with fastboot command, go to twrp and flash supersu and format cache in twrp (it is the same like flash cache.img). Now it is working on my backup phone (N5X), but I need all on my data partition. I don't format it.
[SuperSU] Chainfire:
I need reliable series of steps to get from a fully clean device to this laggy state. Including exact firmware versions flashed.
[SuperSU] ddrum2000:
So what happens if you don't format /data, does it not work? Are there some files that we can delete out of /data to make it work properly? Thanks.
[SuperSU] Ch3vr0n:
[MENTION=631273]Chainfire[/MENTION] I'm running STOCK ROM as Google issues it. No customizations whatsoever, not even a custom kernel. Right now that would be NMF26F and kernel as Google issues it. I have a nandroid backup with TWRP from November security patch running 701, made before I updated to 701. If you want I would be happy to make the entire nandroid backup available to you. Then all you'd need to do is flash a build newer than SR1 and watch it happen (or hell, even try to use the root checker app on the device).

The loop as you say it is likely the checker which request root upon button press but doesn't get it. Then it tries again,... And ultimately fails. Flash SR1 and it instantly gets root again when requested.
[SuperSU] culiacanazo:
The answer lies in "as GOOGLE issues it"!
[SuperSU] silvercat:
Hi [MENTION=631273]Chainfire[/MENTION], SuperSU (any version) bootloops in Stock nougat roms for Moto Z.
[SuperSU] ban.codrut:
Have you tried forcing systemless install method ?

SuperSU doesn't detect Moto X Clark as systemless neither , installing itself as system root resulting in a bootloop. Also be patient on the first boot with systemless systemless root, might take some minutes and maybe also it will reboot by itself during the bootup, just let it do its magic!!

echo SYSTEMLESS=true >> /data/.supersu

(!! THE SYNTAX MIGHT BE SLIGHTLY WRONG !! also go ahead and research a bit before trying, I can't remember everything)

Update: corrected syntax

Update 2: added more insights on systemless