yashsingh1/xdaforums huggingface dataset:
[SuperSU] ApriliaM3:
Gotcha... ok thanks again for the explanation.

It's not worth worrying about really.

I just thought it might be a simple fix to get rid of that annoying warning every time I boot :)
[SuperSU] KillersEnergy:
I think that it work like in the image:)
[SuperSU] The Saint Kopite:
Hello.

Just installed Super SU on my Redmi Note 3 - CyanogenMod 13. Can someone guide me what to do next? What script etc to add and other things? I am quite new to doing this stuff. So, I would be very thankful if someone can help a poor soul like me. :)

This is what I am getting now:-

Thanks a lot.
[SuperSU] It_ler:
Sorry for the late response.

Pulser_G2 has written something about it here: A Look at Marshmallow Root & Verity Complications

Maybe interesting to know more about the background of this warning message.
[SuperSU] KillersEnergy:
xposed framework for personalizzattion and maybe init.d for script on boot and you can try custom kernels compatible with your device AND your version of cyanogenmod ;)
[SuperSU] Strobi:
Problems with Andoid 6.0.1

Hello @ all,

I had problems with flashing the SuperSU V2.65 in combination with Android 6.0.1 at my Sony Tablet Xperia Z3 Compact:

h**p://show.picr.de/26088314xj.jpg.html

But the same SuperSu V2.65 is working with Android 5.1.1.

So can someone help me, why I couldn't install SuperSU with Android 6.0.1?

Thanks.
[SuperSU] fmc000:
Use the beta version, the stable cannot work on MM.
[SuperSU] BigMeanMachine:
Can someone help me please?

I just flashed my Moto G2014 2G XT1068 with CM13, today I tried to instal SuperSu:

Tried from GooglePlay and clicked in "Normal", but it failed.

And them i tried to install in TWRP, but now my device don't boot, it's stuck in CM13 logo, just the animation...

I don't really want to reflash or wipe/all. :(
[SuperSU] Darke5tShad0w:
In your picture it shows you flashing the beta (2.74-2)
[SuperSU] BigMeanMachine:
I think it's solved.

If someone have the same problem try:

1- Bootloader

2- Recovery » TWRP

3- Wipe Cache/Dalvik

4- Install Beta Version of SuperSu

5- Profit
[SuperSU] Jony B:
It works on Motorola XT1040 (Moto G 4G) CM13. Just installed from recovery TWRP. :good::good:
[SuperSU] lolle.santoso:
Saya mengalami kesulitan memperbarui binari
[SuperSU] egingell:
English.

Sent from: SGS5 - MM 6.0.1 / SGS4 - LP 5.0.1
[SuperSU] tzzeri:
According to google translate

I'm having trouble updating binary
[SuperSU] ktmom:
"having trouble updating binary"

1st - Google translate is your friend

2nd - to get help for your problem, please read post 1 and look for the instruction for when you have trouble with updating binaries

3rd - in general, you need to provide way more information than you have.
[SuperSU] lolle.santoso:
Are having trouble updating the binary
[SuperSU] Pkt_Lnt:
cek di sini

[SUPPORT] Update failures

http://xdaforums.com/apps/supersu/support-update-failures-t2907365
[SuperSU] doomscooter:
What is mean "cek di sini"
[SuperSU] Pkt_Lnt:
Google Translate of "check here" to Indonesian because that is what Google Translate identified from their first post.
[SuperSU] Strobi:
I tried it with both versions, but both failed. So in the first step I wrote it in the SuperSU 2.65 thread.

But when you said, SuperSU 2.65 wouldn't work with Android 6.0.1, I will write it in the SuperSU 2.74 BETA forum.

Thanks.
[SuperSU] Chainfire:
v2.76

v2.76 released !

Download: UPDATE-SuperSU-v2.76-20160630161323.zip

(Google Play release later today by CCMT)

Changelog: post #3

Notes:

CCMT is starting to take over development, and will soon also take over support in these XDA threads as well. The ZIPs linked from the XDA threads for download from my server (chainfire.eu) have always been checked, built and uploaded by myself. It may well be that v2.76 is the last version where this is the case.
[SuperSU] GabbyWC:
I flashed SuperSU v2.76 to my Nexus 5 earlier today (using FlashFire) and when my phone rebooted, it went through the "optimizing apps" sequence. This appears to have been because Systemless Xposed v85.7 was erased or disabled so I had to flash Xposed afterward and go through the "optimizing apps" procedure again. Did anyone else here encounter the same results?
[SuperSU] osm0sis:
End of an era. :(
[SuperSU] papero68:
????

Inviato dal mio P9000 utilizzando Tapatalk
[SuperSU] Shyciii:
The new version (2.76) works with Nexus 5X Android N DP4? Or use 2.74-2?
[SuperSU] dechronic:
Thanks for all your work until now and that which is to come. I hope you see the at least the same success in your future projects that you intend to pursue.
[SuperSU] BartVCD:
time to make a new donation, thx a lot for all your work here chainfire ;)
[SuperSU] ianmacd:
I experienced the same results on an S7 Edge, except that it didn't even cleanly reboot after flashing SuperSU 2.76 with FlashFire. It entered a bootloop and I had to turn the device off to break the cycle.

When I turned the device back on, it properly booted and went into the optimising apps sequence, as you describe; after which I had to reinstall systemless Xposed.
[SuperSU] deadgirlcorpse:
Can't install update!
[SuperSU] dechronic:
I believe this may be related to the change "- ZIP/Systemless: /data/su.img resized from 32M to 96M, to make sure enough space is available for systemless modes such as xposed" and although it will be an inconvenience to reinstall xposed for the time being, I believe it is Chainfire's intention to future proof it.
[SuperSU] Ja_som:
Yes, I have no issue with 2.76

You really can't share less informations...
[SuperSU] acultr:
layers manager Fcs after updated SuperSU.

any idea? thanks
[SuperSU] Ja_som:
No issue on my N5X with Android N and on N7II with 6.0.1. Layers manager works fine...

Try to reboot, then if still FCs try to delete app data for Layers Manager...
[SuperSU] kamesh_kraken:
2.76 Confirmed working with Moto G (2013) XT_1033. With Krexus-CAF.
[SuperSU] Guizão BR:
Version 2.76 working very well in my mtk deive on android 6.0 :D

Quantum GO mt6753
[SuperSU] ianmacd:
This thread would probably be a lot shorter if people reported only their failures, not their successes. ;)
[SuperSU] BHUSHAN7988:
Hey i know some apps don't work on new SuperSu like esfile and selinux changer but Anyway to make it work
[SuperSU] t-ryder:
-del-
[SuperSU] :
Man, i just saw the update and was surprised it was SuperSU doing the memory leak. I was going crazy asking myself why is the system app's RAM increasing slowly. Thanks for the fix!
[SuperSU] Mesmurized:
Personally, I appreciate success stories.
[SuperSU] egingell:
Yes. Drop a symlink of /su/bin/su into /system/bin.

Please note that doing this will break OTA integrity.

Me, too.

Sent from: SGS5 - MM 6.0.1 / SGS4 - LP 5.0.1
[SuperSU] HorstiG:
Works great on LG G4 H815 Stock M 6.0 and Galaxy S7 herolte M 6.01 Stock.

Thank you.
[SuperSU] osm0sis:
Mine was resized to 64M before from another mod and updating to 2.76 didn't resize to 96M; no issues on my N5 before or after resizing manually though.
[SuperSU] tvisforme:
Hello, thank you for the update. I'm not sure if this was the issue you were looking to fix but I am still seeing multiple (as in eventually dozens) of instances of apparently SU-related processes. Most of them relate to AFWall+; every time a connection changes (ie WiFi to mobile data) there are two new SU processes generated. I'm going to inquire about this in the AFWall+ discussion as well; I'd be happy to supply any information you might need if you are following up on this matter.

Nexus 4

CyanogenMod 13

Hellspawn kernel

SuperSU 2.76
[SuperSU] DarkWolf:
I tried a su versions including beta but not got root

"Installation aboarted signature varification failed"

I am using samsung galaxy on5 sm-g550fy with

android version 6.0.1

and i extremely want to root because need some changes in phone.
[SuperSU] Chainfire:
Regarding bootloop, note that SuperSU ZIP install can reboot twice.

Unfortunately, sometimes one of the reboots inside the cycle may cause a file on /data to become corrupted, which in turn can cause another reboot and/or a boot freeze, which you can get out of by manually rebooting. I've only seen this happen on Samsung devices, by the way.

Additionally, xposed may trigger a reboot and automatically disabled itself in case of some issue as well. This might be a cause for an extra loop as well as the reason you needed to reinstall it.

Good news coming on that front soon.

Hearing about successes is good, especially from users that have seen problems in the past.

I wish I wrote bugfree code, but alas I do not. Memory leak tracking is tricky and time-consuming with su's daemon, and the big leak fixed in this case originates in libc, so allocation trackers didn't even catch it.

Enable compatibility mode (BINDSYSTEMXBIN flag), modify /system and touch /system/xbin/su, or wait for an update. ES File Explorer update is coming soon, at least.

To be updated to 96M your su.img needs to be exactly the original size, and you need to update SuperSU through the ZIP installer.
[SuperSU] ianmacd:
Yes, at first I didn't even realise I was in a bootloop. I was watching the LiveBoot messages whizz by for quite some time before it dawned on me that I was seeing some repeats.

I left the device for a further 20 minutes, at which point it was still booting and now red-hot. At that point, the SuperSU update had lasted much longer than any I have previously done, so I called time on it and pulled the plug. I was pleasantly surprised that a manual boot cleared things up. I felt sure that I'd be renewing my acquaintance with Odin this afternoon.

Incidentally, is it technically possible to produce a systemless LiveBoot? It's the one thing I would sorely miss if I were to go fully systemless.
[SuperSU] Chainfire:
LiveBoot was systemless last time I checked... :)
[SuperSU] ianmacd:
The app features an Uninstall option whose description reads: Removes the boot script from /system. Does not uninstall the app.

I assumed that meant I had a modified /system. Am I wrong?
[SuperSU] egingell:
Successfully updated SGS4 official stock TW LP (Play Store "Normal" mode) and SGS5 official stock TW MM (flashed ZIP from here via TWRP).

The boot script is put into wherever init.d files live. Whether that be /system/etc/init.d or /su/su.d. Verbiage is arbitrary.

Sent from: SGS5 - MM 6.0.1 / SGS4 - LP 5.0.1
[SuperSU] ianmacd:
I see. Thanks.

However, if LiveBoot is always systemless, it seems a good idea to remove the reference to /system.
[SuperSU] christantoan:
For SELinuxModeChanger, try using version from F-Droid. It's working fine here with the new SuperSU
[SuperSU] Chainfire:
It isn't.
[SuperSU] ianmacd:
OK. Well, I suppose the clearest option of all would be to use the actual install path in the app, rather than to generically refer to /system, which gives the impression that /system is used on all devices.
[SuperSU] Dr.SAM88:
Only 2.68 is compatible with ES File manager, all others give error.
[SuperSU] MrKaon:
Give up on the ancient app, lol
[SuperSU] Pkt_Lnt:
There are probably a hundred posts here of how to fix that. Some no more than 10 posts above yours.
[SuperSU] Younex:
I've been getting binary update failure and root loss (and mount fail) for months, but binary update works on stable 2.76 ! Thanks alot :) ?

https://plus.google.com/+YounesLayachi/posts/hjws4gM3Rzv
[SuperSU] Michael Carleone:
After updating to 2.76, I have an issue with one app called Earthquake and I uninstalled it. SuperSu wouldn't allow Cleanmaster to block the app from autostarting. Greenify was ok in hibernating the app though.
[SuperSU] Christendom...:
I updated SuperSu to v2.76 and all is working well. I did have to update binaries but that was it.

I'm using:

Oppo Find 7

OmniRom 6.0.1

Finally, thank you Chainfire for all of your hard work: I value you dearly.
[SuperSU] Long Island NOOBIE:
"THANK YOU!"

Updated my nexus devices with flawless results! Thank you sir, all your years of dedicated service and contributions in development for our community. Wish you well in all your chosen future endeavors. God Bless and be well!
[SuperSU] UnixSlayer:
Concerning this update..... i am using your rigged SuperSU for the ENGboot for the U.S. variant of Samsung Galaxy S7/S7 Edge... i know you said not to install, or use SuperSU with this.... or it will break the root... Does this release fix that, and can i hit the SU binary update on 2.76? Will it unroot the phone? Thanks.....

Sent from my rooted Samsung Galaxy S7 Edge - SM-G935T
[SuperSU] Darke5tShad0w:
It wasnt me that said that as it did work.

But hey theres a new version now.
[SuperSU] osm0sis:
Ah, makes sense. Well if anyone else needs to manually set it to 96M from something less, they can use the following from in recovery (and Xposed's installer zip should probably do something similar).

fix_suimg.sh:

#!/sbin/sh

suimg=/data/su.img;
e2fsck -yf $suimg;
resize2fs $suimg 96M;

The main thing I wasn't sure about would be how to easily check the free space inside the .img and increase accordingly. You figure anything like that out already in your work with su.img? That's really what all systemless mods using su.img should do.
[SuperSU] Fentadroid:
Sorry for the stupid question. I have to update supersu on my oneplus 3. Is the flashable zip...systemless?
[SuperSU] ktmom:
Not a stupid question [emoji4] in the beta thread this had been discussed http://xdaforums.com/showthread.php?p=67135909

--------------- edit --------------------

Ok, you changed your question. The latest stable release zip file (2.76) will install systemless if either:

* all the conditions are met requiring/allowing it (there is a long discussion in the beta thread)

- or -

* steps are taken to 'force' the install as described in the link I posted above

The installer goes through a series of checks to determine whether to install in system or systemless mode. e.g. a custom ROM with a modified system partition will install in system mode unless forced to install in systemless.
[SuperSU] brossovitch:
The stable has always worked on MM.

6.0 & 6.0.1 STOCK LG and CM13 and Samsung MM ROMs. At least for me..
[SuperSU] Technical:
Thanks for the stable.

I was becoming impatient with the "bugs" in latest beta, as SuperSu was not opening the dialog, I lost root until reboot...

Now everything is working again :good:
[SuperSU] Dudebowski:
Woot W00t for root rooter supersu, long live the chainfire king! Thank you for all these years of service. I hope to see your further exploits for many years to come.
[SuperSU] knpk13:
Hey, I was just wondering why SU isn't open source, and I searched and read all related posts in the thread.(seems to be a hot topic) I understand you have stated multiple times that this will not be discussed here, and I respect that. I am just curious to the reasons and would appreciate if someone could link me to the correct place where I can find the debate or reasons for closed source vs open source(specific to SuperSU), because I have not been able to find the relevant information myself in this thread or elsewhere, and I do not where I'm supposed to ask this. Thank you.

PS: Please don't reply with reasons or off topic debate here. I don't want to start a war. Kindly just redirect me. I am aware that CCMT owns SuperSU now (and I was wondering why not open source instead of CCMT), is it a for profit company? (Not that it's wrong) Not much info on CCMT, but I won't ask that here, and I'll wait until the takeover.

Edit: [MENTION=791219]fmc000[/MENTION] already read all those posts and I know there is no obligation. [MENTION=631273]Chainfire[/MENTION] said "I see more drawbacks than benefits"(open source) Asking for reasons(the drawbacks and benefits for my own knowledge) No discussion here as chainfire requested.(just please link me to correct place if you know)
[SuperSU] fmc000:
http://xdaforums.com/showpost.php?p=57034904&postcount=7468
[SuperSU] Andy8477:
I'm running Supersu with TWRP on my note5. I have the update for the supersu in Google play, but since I'm a new Android user, I'm not sure if I could just update it from Google Play. Anyone knows how to update it safely? I've been searching for a way to update supersu, but wasn't lucky to get the results I want.
[SuperSU] aavvaallooss:
Flash de zip of the first post using TWRP
[SuperSU] Andy8477:
Do I need to uninstall it first? Or straight fishing ?
[SuperSU] h4ck54w.sense:
hi did update SuperSU apk over GPlaystore.

ask for update binary and I pressed twrp/cwm. It has done sometging. After reboot I checked in the apk that is 2.76 working.

It does.

today I recognized that none of my MusicApps are working anymore.

and it reboots after a while.

tried to delete that cache and data from the MusicApps and also SuperSUApp over settings, but the problem is still present.

cause it was the only thing I changed yesterday I downloaded SuperSu.zip over this thread and flashed it again over twrp.

It does install in systemmode for me?!??

and after a reboot I had to install SuperSu apk over GPlaystore, cause it was away.

Device:

HTC 10

JANJAN deodexded Stock rom

1.80.401.1
[SuperSU] x92:
Hello there,

I got a request. Can [MENTION=631273]Chainfire[/MENTION] or CCMT team help to root Samsung Galaxy Tab 4 7.0 LTE (SM-T235) latest 5.1.1 firmware T235XXU1BPC2 ? Supersu (even with latest 2.76) doesn't work after it was successfully flashed via TWRP. It's running on universal3470 platform same as Samsung Galaxy S5 mini (G800F/M/Y).
[SuperSU] Fentadroid:
My oneplus 3 has the stock rom with TWRP and SuperSU 2.74 systemless.

Ok, thanks. So, to be *SURE* the usual commands:

echo SYSTEMLESS=true>>/data/.supersu

echo BINDSYSTEMXBIN=false>>/data/.supersu

And then i'll flash the zip... right?

Thanks again :highfive:
[SuperSU] DarKAngel1234:
Why and who is CCMT?
[SuperSU] osm0sis:
Search please. Chainfire's G+ has a big post explaining it when it was announced last year.
[SuperSU] akarol:
Do we need to flash via TWRP if binaries within app successfully updated?
[SuperSU] elandroido:
Thanks!!! The symlink did work... :)
[SuperSU] egingell:
Of course. That's how I got Secure Settings to work. :)

Sent from: SGS5 - MM 6.0.1 / SGS4 - LP 5.0.1
[SuperSU] guhvanoh:
I guess that if everything is saying you're on 2.76 and everything is working fine, then you're good to go. No need to flash via TWRP.
[SuperSU] moormann:
SuperSu 2.76 on Huawei GX8

Hallo together,

i am new on this board, hope my question ist not stupid.

I use SuperSu 2.64 flashed with TWRP on Huawei G8, lollipop 5.1.

Is SuperSu 2.76 compatible with my Phone? Has i to flash again with TWRP?

Can i update the Pro Version with Google Play Store? And have i to reinstall xposed also?

Many Questions... Has someone experiences about this?

Thanks for an answer.

Christian
[SuperSU] Artieza:
After update something weird happened with Link2SD. All apps from second partition of SD disappeared, but /data/sdext2/ don't (I checked it via File Explorer). Then apps goes back. On the next day they dissappeared again. Then goes back... Installed back SuperSU 2.65. Any confirmation or explanation?

LG G3 S (D724), Stock Lollipop.
[SuperSU] egingell:
This is not the place to seek support for apps other than SuperSU.

Sent from: SGS5 - MM 6.0.1 / SGS4 - LP 5.0.1
[SuperSU] Artieza:
The problem happened only after SuperSU update, so I guess that new build of SuperSU compiled with something missed.
[SuperSU] DACATA:
Works perfect on oneplus two OOS 3.02 Android 6.01.. ?
[SuperSU] dito33:
I can't find working link to download flashable (twrp) su
[SuperSU] Ja_som:
All links for download in first post works...
[SuperSU] egingell:
Your problem is with one particular app which hasn't been updated in forever. Frankly, I'm surprised it still works at all.

Sent from: SGS5 - MM 6.0.1 / SGS4 - LP 5.0.1
[SuperSU] nevernat_theoriginal:
compatibility issue

I found a compatibility problem with two file manager apps: "ES File Explorer/Manager PRO" and "Solid Explorer Classic". These apps are not able to obtain the root privileges with this version of supersu.

Some solutions?

Thanks in advance.
[SuperSU] Ja_som:
Yes, use the search function in this thread...
[SuperSU] moormann:
SuperSu 2.76 on Huawei GX8

Huawei G8, Lollipop 5.1.

Now i tried update to SuperSu 2.76. Installed was SuperSu 2.65 Pro.

I flashed by TWRP 3.0.2-0. I tried twice, the second time with delete Dalvik/Cache.

Second time after starting Phone its updated apps while booting.

Twice nothing changed, SuperSu 2.65 has still installed.

Has someone an idea?
[SuperSU] YasuHamed:
i am having same thing

also the line https://download.chainfire.eu/969/SuperSU/UPDATE-SuperSU-v2.76-20160630161323.zip (the 20160630 doest not match with google play)

mine is stuck on 2.74

device z5p rooted / twrp recovery
[SuperSU] ktmom:
Have y'all looked at the recovery log? If you can't find the explanation there, upload the log to pastebin (or equivalent) and post a link to the log here. You need to help people help you.
[SuperSU] drooplug:
I had the same experience on my LG Power. Went back to 2.65 and everything was normal again.
[SuperSU] Artieza:
Yea, weirdness. I know that not all users of Link2SD faced with this after SuperSU update.
[SuperSU] grep_i:
Maybe you should try another app as this one is not being updated for almost a year now.

There are plenty of others in the playstore with same functionality but still being maintained.

Also don't blame it on Supersu but just the app, you could look if it has hardcoded Supersu path in it than you can make the ancient app still work by forcing a system mode install of Supersu.

But if I were you I would look for another app that is still being maintained
[SuperSU] yplim2300:
does it work for Android 6.0?
[SuperSU] daitalos:
Yes , you need...

a flashable zip & flash via recovery(twrp) from the beginning of thread ...the latest test release flashable zip is this : http://download.chainfire.eu/969/SuperSU/UPDATE-SuperSU-v2.76-20160630161323.zip
[SuperSU] Ja_som:
OMG, do not post the whole log here, use pastebin or add logfile as attachment...
[SuperSU] Artieza:
No, only two: Link2SD & Apps2SD.

Chainfire didn't manifest any global changes that lead developers to update root capability libraries for some ROMs.
[SuperSU] YasuHamed:
oh sorry, fixed
[SuperSU] ldeveraux:
Are you serious? Don't post the log, attach the log file...
[SuperSU] grep_i:
OK that's great did you try App2SD which has been updated recently June 21 2016 ?
[SuperSU] YasuHamed:
Hmm
[SuperSU] iceorfire95:
I can see an update notification from Google Play for SuperSU. My device runs on COS 12.1 and I seem to vaguely remember reading somewhere that you can only get SuperSU to work on Android Lollipop based devices if it's flashed through the recovery. So should I directly update from Google Play or flash the .zip file through TWRP?
[SuperSU] egingell:
The Play Store app can only update an already rooted device, but it works just fine... or should.

Sent from: SGS5 - MM 6.0.1 / SGS4 - LP 5.0.1
[SuperSU] gracenguyen11:
Hi, I'm trying to root my HTC M9, rebooting my device right now after installing SuperSU but the phone keep rebooting over and over again. What do I do?
[SuperSU] Pkt_Lnt:
Start in the right place.

http://www.xda-developers.com/root/
[SuperSU] Black-FR:
On the m9, you should use SuperSU 2.65...

The newer versions lead to boot loops.

Might be good, if you grab a log of the boot loop, for [MENTION=631273]Chainfire[/MENTION]

BTW. You could later update to the latest SuperSu, via the playstore update.

Gesendet von meinem HTC 10
[SuperSU] YasuHamed:
simply installing supersu wont give you bootloops

what else you did?

also what android version are you on?
[SuperSU] Iceberger:
No problems here with v2.76 + M9
[SuperSU] Black-FR:
You flashed the zip or updated via the play store?

Gesendet von meinem HTC 10
[SuperSU] waledakmal:
download.chainfire.eu : down

please upload supersu stable or latest
[SuperSU] mobileman88:
I just tested. It's working. Do try again
[SuperSU] waledakmal:
still down here

supersu page not https://autoroot.chainfire.eu/
[SuperSU] Pkt_Lnt:
It opens here. What browser are you using to access it?
[SuperSU] waledakmal:
download any file from site. can you? downloads down :rolleyes:

firefox and explorer
[SuperSU] Pkt_Lnt:
yes, download done. Chrome on Windows 7