yashsingh1/xdaforums huggingface dataset:
[SuperSU] Chainfire:
All BETAs have always been released right here in this thread first, and served from https://download.chainfire.eu/ . There have not been releases other than here and Google Play.

That is history starting this week though, as the release scheduled will be changed, but if in the past you have seen releases appear somewhere else first, they weren't mine.
[SuperSU] Chainfire:
v2.75

The v2.75 going around appears to be a CCMT build.

Both new Play as well as BETA releases were scheduled for the 24th, but I delayed them due to a couple of bad bugs I'm trying to fix. I suspect there has been some miscommunication there and CCMT's build got uploaded to one of the Asian distribution sites anyway, and that is this APK. Decompiling it, it contains code that isn't in any other released version of SuperSU, but is scheduled to be in the coming update. Combining that with the signature, all points to this being their build.

I will have to wait for them to get back into the office before being able to confirm this, though.

Either way, I would always recommend against installing any SuperSU version that came from anywhere else than Play or https://download.chainfire.eu/ !

EDIT: CCMT has confirmed this is their build, uploaded to Chinese app stores.
[SuperSU] egingell:
This thread and the stable thread are the *only* places official releases will ever be found.

Edit: I posted this without realizing there were two more pages of posts.

Sent from: SGS5 - MM 6.0.1 / SGS4 - LP 5.0.1
[SuperSU] hondansx:
Thanks for this. Lenovo Vibe P1 root working only with systemless root flashed via twrp.

Updates can also be done via twrp too.
[SuperSU] ldeveraux:
Initially, I tried installing them early, not knowing any better. It would always fail, so it was a moot point. It was just an indication that you were getting the next release ready
[SuperSU] Snowby123:
Yesterday I downloaded the latest beta and installed it through flashfire.

The download says it is version 2.74-2 yet when I launch the UI of the app it says 2.72.

Is this a problem? I was using version 2.71 before.
[SuperSU] Ja_som:
It should be 2.74
[SuperSU] osm0sis:
You left EverRoot enabled in FlashFire. EverRoot is currently at SuperSU 2.72. ;)
[SuperSU] Ch3vr0n:
No it shouldn't. If you install the beta and keep the flashfire built in everroot active then you will get 2.72 because everroot gets flashed after the beta and will replace the beta zip ones. the reason for that is that FF hasn't been updated to contain 2.74. that's all. superSU gets updated more than FF does. When FF will get an update it will contain the latest SU, but when superSU gets an update then, then there FF built in one will be 'out of date'.
[SuperSU] Chainfire:
How can it be an indication that I was getting the next release ready, if they don't have any connection to me, nor have I ever informed them of such things?

They are trying to scam you, plain and simple.
[SuperSU] ldeveraux:
That's great for them. My point was that when it popped up on Aptoide, your release usually came in a week or so. If the two aren't related, so be it, that's just my observation.
[SuperSU] zelendel:
To be honest Aptoide is your issue. They are a known warez site that messes with apks. I would avoid them completely
[SuperSU] Mrcactuseater:
Preach it

Tapatalk'd from my Twisted, Despaired Nexus 5x
[SuperSU] ldeveraux:
I hardly think I have any issue, I wasn't the first to mention aptoide in the first place. Next topic for God's sake...
[SuperSU] Chainfire:
This should be fixed in the upcoming release. Let me know if you're still having issues.
[SuperSU] NLBeev:
Now we are off topic, I want to change the subject to Tapatalk and links.

When a link ends with numbers 't=235679' Tapatalk gives an error. Adding a slash at the end will solve this issue.

Many OP's have that links. Do you know the way on XDA to publish this?

(Feedback to Tapatalk - no response)
[SuperSU] Ch3vr0n:
We're not of topic, it was related to some obscure supposedly updated superSU. Tapatalk link fixes has nothing to do with superSU. You need to contact either XDA forum / site staff, Tapatalk dev's themselves or both!
[SuperSU] NLBeev:
Discussion about that Aptoide is OT and we need to respect the XDA -rules. So I thought it was good to change the subject. Sorry if I am posting wrong stuff.
[SuperSU] Ch3vr0n:
It wasn't ot, as it informed chainfire about a releases he didn't authorize and could contain possible malware and in doing so endanger the reputation of superSU.
[SuperSU] NLBeev:
That was clear to me, but I won't talk/write about malware distribution.
[SuperSU] Ｈay。:
If it is the Asian region of China can use the CCMT Version 2.75？ or that all have to be downloaded in https://download.chainfire.eu/
[SuperSU] Chainfire:
Sure, everyone can use it. But at this moment, I don't have a list (yet) of all the stores/sites CCMT upload the APK to. Until I do, I can't tell you which sources are good.
[SuperSU] ianmacd:
I'm confused.

What on Earth is someone else doing uploading your software to third-party sites?

Presumably, neither CCMT nor anyone else can get hold of your pre-release code without your approval, so why is this happening?

The question isn't meant to sound as if I'm blaming you for anything. I just genuinely don't understand why this situation has even arisen.
[SuperSU] tet-bundy:
off topic: what is the non Asian region of China?

Gesendet von meinem ONE E1003 mit Tapatalk
[SuperSU] Chainfire:
CCMT owns the rights to SuperSU, has access to all sources, and pays me.
[SuperSU] ianmacd:
Thank you. I couldn't have asked for a clearer answer.

I still find it odd, however, that they would effectively leak versions of your code that aren't yet ready for release; and without your knowledge or approval, too. That doesn't seem to be serving anyone's best interests.

Whatever the machinations behind this situation, users can ensure their devices' security by downloading only from the Play Store, your posts here on XDA, and your own web site.
[SuperSU] nicolap8:
You're right, it's very odd because this superficiality can be very dangerous for common users.
[SuperSU] grep_i:
Correct me if I'm wrong.

They own the code and pay Chainfire so they are entitled to release a new version whenever they like without consulting Chainfire first.

Why is that dangerous to common users ?

Personally I find it odd but business wise it ain't.
[SuperSU] Chainfire:
Please, let's drop the subject. As I said, it was a simple miscommunication. Releases will be synced going forward.
[SuperSU] NLBeev:
#6521 - 6570 could be cleared.
[SuperSU] toraj13:
Hello, someone help me install SuperSU via adb please.. My device no custom recovery, use kernel only root access adb, I tried but no Su binary..
[SuperSU] snickler:
As chainfire said,

End of conversation on the previous topic.. PLEASE stick on the topic at hand and keep this thread clean.

Thank you all :)
[SuperSU] manibengood:
I'm having one issue that I can not seem to fix. My Nexus 9 volantis wifi is showing that it is rooted when I check the root checker by Super user from the google play store. It says Root Access: Device is rooted. The next line down says Super User: SU NOT FOUND. I am using the current 2.74 beta. I have the latest vendor image MOB3OM. I am running the latest Pure Nexus 6-21-2016 build. I'm running the latest GAPPS and fire and ice kernel. When I go to an app that needs SU permission I get the pop up that ask me to grant permission. So I know that my device is partly rooted. When I try to turn on the root explorer function in ES file explorer it says, "Sorry test failed. This feature can not run on your device." I originally started with stock factory image. I rooted and installed recovery with Nexus Root Toolkit. What am I doing wrong?
[SuperSU] Pkt_Lnt:
PN is systemless root and the dumb apps are hard coded to look in /system only and fail. Have the devs update their dumb apps. ES file explorer has been discussed here ad nauseum, 1000s of times.
[SuperSU] manibengood:
Sorry if I missed the ES file explorer discussion. I have been searching and searching threads for 2 days now trying to find an answer on my own. Is there a way to fix the "SU not found" or am I just stuck with what I've got? I didn't have this problem with the last build of PN from 5-6. At least not that I noticed.
[SuperSU] Pkt_Lnt:
The May build of PN was system root.

The June build of PN is systemless root.

Look at the FAQ in post #2 of the Nexus 6 thread for the solution. The FAQ is probably linked in the other PN Nexus device threads.

There is a file in PN that you just have to edit for compatibility mode.
[SuperSU] 000001a:
supersu doesn't work on my LG G3 D855 16GB, CM13 20160628.

(i'm comming from a lolipop stock rom)

because it paching the boot.img, but it triggers a secureboot issue, because it isn't bump'd anymore.

is there no other way to installing supersu? because i think you will not make for every device in the world a seperate supersu, like cyanogenmod or twrp.

edit:

my intention is to update cyanogenmod whithout reflashing supersu.

this cannot work, if you must pach the boot.img every time.
[SuperSU] Ch3vr0n:
Wrong section. Use your device forum and check how to bump the kernel. Multiple topics about bumping kernels
[SuperSU] 000001a:
i will not bump anything, or playing around with the kernel.

i just saw in the twrp-log supersu playing with my boot.img

my intention is to update cyanogenmod whithout reflashing supersu.

this cannot work, if supersu must pach the boot.img every time.

edit:

this error exist since december 2015 (link)

and it is on the "to-do-list".
[SuperSU] Ch3vr0n:
You don't have to play around anything. Bumping the kernel is as simple as running a script. No bumping, no superSU. Updating your cm: flash rom, flash SuperSU zip, flash kernel bump script, done.

Make your choice. Works just fine for others.
[SuperSU] 000001a:
hm... maybe it could work for me, but not for my friends.

they need an "out of the box" working concept,

because they not skilled in computers, and i am not there every day.

(off topic)

if you ask why i give my friends cyanogenmod-sellphones.

because updates for security. this is way better,

than get 2 updates in the whole sellphone lifetime.

it works for my friends, but the cyanogenmod-su-gui sux.

it has no whitelist, just on or off...

...but this is not the topic here...

(/off topic)
[SuperSU] manibengood:
Got it. Some reason my brain want connecting the word systemless with where the root WA'S not in. Feeling pretty stupid. Thanks for the answer. :o
[SuperSU] Ch3vr0n:
Now, since you apparantly won't do the search, i'll do it for you. Here: http://xdaforums.com/lg-g2/general/bump-supersu-t3273251 LG bump script, 5 second google search. Keep that script on the internal storage. and you're set for every time you flash an updated rom.

1. Boot into recovery

2. Flash updated rom

3. Flash bump script

4. Flash SuperSU

5. Done.

Everything you need to know is in that link.
[SuperSU] Perseus:
Let's not discuss the merits of Whether or not to quote a Post here. That is Off Topic for this thread. There's always Off-topic for such discussions.
[SuperSU] Yudh:
[MENTION=631273]Chainfire[/MENTION]

A request (or possibly a bug)

When an app requests root permission and the timeout of 10 seconds is over the app is denied from root permission.

The log shows this app's entry where as the apps panel in SuperSU 2.74-2 beta doesn't show any info about this app.

According to me it should show prompt request option.

2nd request to guide me

i am on Resurrection Remix v5.7.0 Marshmallow based on cm 13 r46 which comes with inbuilt cm superuser but i need SuperSU.

So when should i flash SuperSU during a clean flash

i)after flashing the rom or

ii)after flashing the gapps

And do i need to clear dalvik and cache

✌
[SuperSU] knpk13:
[MENTION=7150737]Yudh[/MENTION]

Doesn't matter.

You can flash SuperSU at anytime after the rom flash. No need to wipe anything. But if you flash a custom kernel, it's generally best to reflash SuperSU as there are variations between different custom kernels, so require a reflash and some don't. Consult your kernel dev for that.

If root access is automatically denied, the app will show in the list with a red # sign next to it. Click on it to choose from prompt, deny, grant, or delete the permission/rule.

You can also check the ask again option if you want SuperSU to prompt you again for root access, even after automatic timeout/denial.

If that is not the behavior you experience, then something is wrong and more details are required. But it works for everyone else. So post in your ROM thread about this issue as it is probably specific to it.

I prefer SuperSU to cm superuser as well, but functionally Im not sure if there is a difference. All that changes is the management options and interface. :)

PS: IMO you don't need to mention chainfire for every little thing.
[SuperSU] magnamentis:
for most kernels it's recommended to flash the kernel AFTER SSU because in many cases the SSU backup script would overwrite the just flashed kernel, hence your recommendation may be true for some cases but totally wrong in other cases. for each kernel this has to be verified/checked separately

generally, and i'm using 4 different kernels right now, none of them has issues with being flashed after SSU whiel 3 of the 4 definitely will be overwritten when SSU is flashed after the kernel.

for further and perhaps more sophisticated information on the matter i recommend to read what [MENTION=4684315]flar2[/MENTION] the developer of quite a few of the top kernels for HTC, Nexii and now Oneplus has to say on the matter. i think best chance to find his posts on the matter will be the Nexus 5 and/or Nexus 6 threads.
[SuperSU] fackamato:
Freeze on Preview N4

Hi,

N6P running Preview 4 here. See https://code.google.com/p/android/issues/detail?id=213682 , having Supersu installed causes freezes / hickups. Uninstalling Supersu fixes the issue.

Any idea how to circumvent / troubleshoot?

Thanks
[SuperSU] ktmom:
http://xdaforums.com/showthread.php?p=67456091
[SuperSU] Chainfire:
There is a new release scheduled for next Tuesday that should fix a memory leak, that _could_ be responsible for this.

However, this memory leak only becomes severe in a short time if there's an app that absolutely hammers the su binary (su is a very heavy call, an app that calls su very often is usually designed badly, and wasting your phone's resources such as cpu and battery). Otherwise, it may take days or even weeks before becoming noticable.

I specifically mention this because I've seen a report on this before, and that user's problems went away when returning to Marshmallow. The interesting thing about that is, that to the best of my knowledge the leak is present and identical both on M as on N. In other words, aside from this SuperSU issues, there might be a root app on your device misbehaving significantly due to incompatibility with N, causing it to call su in a loop.

OR, it could be something different entirely. Unfortunately, these issues are very hard to find unless they can be reproduced.

If you have a reliable way of reproducing this problem, please get your phone in a bad state, then paste the output of the 'ps' command here. That may hint at something.
[SuperSU] fackamato:
Thanks, Chainfire. I'll install the new build and monitor the behavior and grab some logs / output when I see the issues again.
[SuperSU] Hobadee:
I see that many people have posted about the HTC One M9, but I figured I would jump in and re-iterate as well.

SuperSU 2.74 Beta will cause an endless bootloop on the M9. If you were smart and created a backup before installing SuperSU (You *DO* create backups, right? RIGHT?!) all you need to do is restore the BOOT partition ONLY and your bootloop will be fixed. (You won't have root, but bootloop will be gone.)

I installed 2.64 without issue, although looking through this thread it appears 2.65 works as well.
[SuperSU] Didgeridoohan:
I did have some problems with freezing and hiccups with 2.74 when it was released, but didn't have time to investigate so I just flashed back to 2.72 and forgot about it.

Don't know if the memory leak is present in 2.72, but it would definitely explain the problems with 2.74 because I see in the logs that I do have a couple of app that sometimes call SU quite frequently.

Running stock 6.0.1 build MOB30M on a Nexus 6.
[SuperSU] pkelly517:
Gah!

I rebooted my Pixel C running NP4 not two hours ago because of this. It was definitely in a bad state. I would guess that it happens every 4-7 days.

It's the only device I have stock or on N. It's also the only device I need to reboot periodically. I'll keep an eye out for it over the long US weekend.
[SuperSU] kylepsp:
If it helps, the only root app I installed was Adaway. I tried several times, factory resetting, and various levels of stock. However, I did try for some time with the phone rooted, but without Adaway installed, and the same issue popped up again and again. I originally thought adaway to be the cause but seems it is SuperSU
[SuperSU] Chainfire:
Well, if it's not caused by su being called in a loop by another program, then it becomes less likely that the fixed leak is the same problem you are seeing.

I have not run into any issues so far on my NP4 devices...
[SuperSU] Tecalote:
I saw there is a new version 2.75, will the zip be available for Download on xda soon?
[SuperSU] kingvortex:
http://xdaforums.com/showthread.php?p=56878545

Sent from my C6603
[SuperSU] thereassaad:
Link not working for v2.24 ?? Please [MENTION=631273]Chainfire[/MENTION] fixed & thanks for ur hard work thanks

Enjoy life. It comes with expiry date.
[SuperSU] iall5tar:
Here go what he said.
[SuperSU] kingvortex:
I posted the reason why right above your post.

Here it is again - http://xdaforums.com/showthread.php?p=56878545

It's a good idea to read the last few pages of a thread before asking questions as it stops threads being filled up with repeated questions. :)

Sent from my C6603
[SuperSU] thereassaad:
Sorry mate that my mistake sorry again

Enjoy life. It comes with expiry date.
[SuperSU] Chainfire:
v2.25 out now, supposed to fix the same thing v2.24 did. Please test and let me know!
[SuperSU] Pkt_Lnt:
You should read back a few posts.

http://xdaforums.com/showpost.php?p=56878545&postcount=630
[SuperSU] DaBigFreak:
Just flashed 2.23 because 2.25 is too young, many here reported 2.23 is working.

Now on my nexus 4 i flashed,all went right, trwp latest version gave me zero errors. But opening supersu app sais no binaries found.

Any help for that? Am i half rooted now? Or am i at least save? :D
[SuperSU] Raz12:
its good thanks man
[SuperSU] redsnake80:
It's Perfect in Nexus 5 Stock!! Thanks!
[SuperSU] Gu$houn*:
[MENTION=631273]Chainfire[/MENTION] v2.25 working flawlessly on nexus4 on both 4.4.4 and 5.0. Thanks. :good:

P.
[SuperSU] DaBigFreak:
Are you on stock 5.0 or on modified with custom kernel? Because now I tried 2.25 and now I am stuck in bootloop!
[SuperSU] Fadtydawg:
[MENTION=631273]Chainfire[/MENTION] beta v2.25 works flawless on Galaxy Sg4 sch-I545 NG6 4.4.2 stock verizon. Great work!! Thank you!
[SuperSU] daverup:
2.25 is good on Nexus 4 Lollipop, thanks:good:

Stock rom and kernel, CF auto rooted, TWRP 2.8.1.0
[SuperSU] DaBigFreak:
Guys with the Nexus4, whats your current setup? Fully stock with TWRP, or some heavy tweaked 5.0 port? Any other kernel used?

Solved: Wiped /system, flashed stock 5.0. Then plugged my Nexus4 to PC, opened WugFreshToolKit, hit root, after 2 minutes, now I have fully running SuperSU2.23 :)
[SuperSU] Murshad007:
No Issue on 2.24

No Issue on 2.25 yet

Sent from my LG G Flex F340K on LTE network, Stock KitKat 4.4.2 Rooted

using XDA mobile app
[SuperSU] Gu$houn*:
On b22s by [MENTION=1050103]sykopompos[/MENTION] with stock kernel.

P.
[SuperSU] JulianJenner:
No problem with 2.24, no problem with 2.25, everything is OK on LGE-P760 Android 5.0 Lollipop by Artas182x

LGE-P760 Lollipop Android 5.0 by Artas182x
[SuperSU] Nicknoxx:
I'm on Nexus 4 LRX21T Hells-core SU 2.25 everything working except Secure Settings.
[SuperSU] dannyella:
Link??
[SuperSU] Mrcactuseater:
Are you joking? Please read the last few pages.

Tapatalk'd from my Franco'Twisted Nexus 5
[SuperSU] sonwon:
I respectfully suggest in the OP that a blurb be added that explains where the valid sources for SuperSU are located.
[SuperSU] Tecalote:
Thanks I found the information on page 657. [MENTION=919113]sonwon[/MENTION] Yes this would be good, links to valid sources.. I have a Huawei p8. One App I use, is Huawei HiApp (Huawei Market like Playstore) - the App offered me Updates to Huawei Apps, but not only, also Updates for Playstore Apps... I was wondering, because I saw an Update for SuperSU in there... So I used Google and found no information to this Version. I allready use the latest 2.74 from the first site of this page and didn't like to search in 660 sites... But now I know, what's happened... I don't like the Chinese Version of the Original one. I find this also dangerous. So thanks for information. I wait until a new original version from Chainfire will released from a official source :)
[SuperSU] fackamato:
FWIW

I did a full unroot from the app. Initially the phone seemed better, but when using spotiify, adguard, messenger, whatsapp, maps navigation and launching youtube the phone started freezing up.

This is with the "Elite Angler" kernel.
[SuperSU] silvertrain78:
Flash your kernel again
[SuperSU] gothicVI:
Can you elaborate why this is the case - just out of curiosity. Thanks.

Gesendet von meinem Moto G 2014 LTE mit Tapatalk
[SuperSU] Chainfire:
Each time you call su a lot of work has to be done to set up the root shell. Processes launched, threads started, sockets created, credentials checked, communications between native su binary called by the client app and the Java part of the SuperSU app (which may have to be launched in the background), toasts created, logs written, etc.

Sounds like a lot? It is. And aside from the CPU cycles it takes, there are also latencies involved (waiting for other threads/processes without burning through CPU cycles). The 'su' call on Android is far more complicated than a 'su' call on your standard Linux box. Of course, all those things together still only take the blink of an eye, but calling su many times to execute a command is still much slower than opening the su shell, keeping it open, and running commands whenever you need inside the existing shell.

How much slower? That wholly depends. In the end it simply comes down to that it is faster, cleaner, less resource intensive and thus better if you reduce the frequency of su calls (keep the su call open if you need that).

Compare it to loading your car before going on a road trip. Do you get your parked car from the street, back it up on your drive way towards your front door, put one item in the car, drive the car back to the street, and repeat this until all your stuff is loaded? No, you get the car once, then you load all your stuff in one go, and then you leave.
[SuperSU] NLBeev:
Great metaphor; thx
[SuperSU] g2uzer:
Thank you, thanks for all the Work and time you put in to this.!!
[SuperSU] Strobi:
Problems with SuperSU 2.74 on Andoid 6.0.1 at Sony Xperia Z3 Tablet (SGP621)

Hello @ all,

I had problems with flashing the SuperSU V2.74-2 BETA in combination with Android 6.0.1 at my Sony Tablet Xperia Z3 Compact LTE (SGP621):

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

Does anyone know, why it is not working? I had no idea, what I was making wrong.

So can someone help me, to install SuperSU in combination with Android 6.0.1?

Thanks very much.
[SuperSU] Chainfire:
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] 1112ee:
Dumb question: how does updating through play store work?
[SuperSU] Robot76:
[DEL]