yashsingh1/xdaforums huggingface dataset:
[SuperSU] Nagato Yuki:
I just wanna to know, when supersu just temporary disabled (i.e. rm \system\xbin\su﻿ ), is there any necessary to keep \system\xbin\daemonsu﻿ ?
[SuperSU] MedNZ:
Like I said, I would if I could. Google is blocked here in China so I am not able to d/l the APK from there.
[SuperSU] Rinoceros:
But the apk is inside the zip (as already told numerous time) which can be downloaded from ChainFires Website.
[SuperSU] MedNZ:
Yes, I know.

there is China.
[SuperSU] michelsberg:
This conversation is becoming funny now... :good:

Did you attempt to download the zip file from chainfire's website, which is known by it's name https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip?
[SuperSU] MedNZ:
Yes. Got the APK from the common folder. Works fine as usual. Thanks!
[SuperSU] Bones519:
I saw on the first page of this thread that there is a version 2.49. In the Google Play Store the version is 2.46. There is an update to 2.49 on Aptoide. Should I update?
[SuperSU] Primokorn:
Forget Aptoide and go to the official beta thread: http://xdaforums.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
[SuperSU] garyfunk:
If you're having issues, yes, update.
[SuperSU] gotrandom:
I'm having an issue maybe someone can help me with. I'm on Nexus 6 using Chroma with SuperSU Pro 2.46. When I boot my phone I get a toast saying that the binaries need to be updated. When I tap this, it opens SuperSU Pro but does not ask to install the new binaries. This has happened on every clean flash. I am unsure if it is falsely being told it has an update or if I have done something incorrectly. My Nexus 6 is unlocked and rooted (I am able to make changes in the build.prop right from within the phone and the modifications stick.)

If anyone has any advice on this I would greatly appreciate it, thanks!
[SuperSU] Mike B.:
One simple way to remedy many installation quirks is to flash the current SuperSU ZIP file (currently 2.46 - link in the OP) from your custom recovery (preferably TWRP). You could also verify which binary you are running by executing "su -v" from a Terminal prompt. The current version should report "2.45:SUPERSU". If you see something else, it's possible that you have a forgotten other "su" but since you're rooted you should be able find/delete any strays, probably in /system/bin or /system/xbin. With any luck, simply flashing the update ZIP will straighten everything out.
[SuperSU] garyfunk:
Install 2.49 and it will update the binaries
[SuperSU] TheColin21:
best

best root app out there
[SuperSU] gotrandom:
I tried flashing 2.49 and am still getting the same issue. Its not a big deal to dismiss it or anything, it seems to popup at random, was just curious mostly. Seems the binaries are otherwise current and work fine. Just odd the update dialog pops up here and there.

I also tried doing su -v in terminal after the update and it says 2.49 as it should.
[SuperSU] garyfunk:
What ROM are you using and did it come with superuser?
[SuperSU] gotrandom:
Chroma, yes it came with it. However, I manually updated to 2.49 and still same issue.
[SuperSU] garyfunk:
You need to remove the superuser binaries then you won't have that problem.
[SuperSU] cat139lyleb:
Supersu 2.46, somehow it's worked but cannot update

My tablet is MX1080 from Kocaso, I got it from my family's gift for my birthday... It's already rooted from ROOTANDROID.COM helping me root my tablet but they cannot understand why my tablet won't update supersu... maybe can you help me? please? Thanks!

Any need info from my tablet, let me know!

PEACE!

Funny thing is that Supersu keeping ask me that need update... not make any sense... maybe you can find out why... please?
[SuperSU] atomomega:
There's a thread specifically made for su binary update problems. Now, I had the same problem some time ago. If you rooted using a tool or any other method different than recovery, then the problem is that the tool you used installed a very old binary. You need to check where the tool stores the su binary so you can manually update it and then push it through whatever tool you use.
[SuperSU] rwjack:
Unable to grant superuser to Android system SuperSU Pro

I have recently encountered a problem on my Galaxy S4 rooted, stock, 4.4.4 . When I long press the back button (kills foreground app Wanam Xposed function), supersu pro asks for root priveliges for Android system(UID 1000), however both the grant and deny buttons are inactive and timer counts down and access is denied, phone goes into loop to grant or deny.... Any suggestions how I can get around this? Is there a way to manually grant privileges to Android system? I have searched, but no results. Help, please.

Thanks.
[SuperSU] egingell:
Search.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] garyfunk:
Go into SuperSu and into settings, then uncheck tapjacking. Then you can use the Long Press. Once you grant access, you can check tapjacking again.

Or you can search.
[SuperSU] GroteBozewolf:
You should have searched.... It has been addressed over a 100 time answering people that don't want to search. Now it has been addressed 101 times.
[SuperSU] SecUpwN:
Maybe [MENTION=631273]Chainfire[/MENTION] should add such questions and the solutions to it to FAQ of the OP?
[SuperSU] rwjack:
As stated in my post, I have searched this thread and Google. I

always

search before posting. If my search terms are flawed, my bad.
[SuperSU] garyfunk:
Don't feel bad. When I had the problem I also searched and didn't find the answer either. Fortunately I understand how things work so I had an idea what to do.

XDA is so big, the search is mostly useless.
[SuperSU] egingell:
I searched this thread just now for "can't click grant" and there were numerous posts about this issue.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] SecUpwN:
[MENTION=631273]Chainfire[/MENTION], I've seen that several people liked my suggestion. I know that SuperSU is your "beloved baby", but maybe you could oprn source it on your GitHub account and add the suggested FAQ to that project? Here is an example of a FAQ of one of my own projects. GitHub makes it really easy maintaining these things and clear up any uncertainties amongst your users. As a bonus, people could publicly help you improve your app! Sounds good?
[SuperSU] kingvortex:
Chainfire has already said before that he won't open source SuperSU. For example here.

Sent from my C6603
[SuperSU] NeoLogY:
Also, I think he already know pro's and con's of open source and github. Don't get me wrong, I fully support open source, but even if I do, there will be some berries I would keep to myself, as the forest I had to go through make me do such decision.

But again, just self opinion, as Chainfire have his own reason to do so. As in future, only he can answer.:D

Sent from here to there
[SuperSU] shoey63:
There is no kernel, so no need for open source. Just imagine the buggy kangs if he did!:eek:
[SuperSU] j1gga84:
I have some problems with editing permissions of files under android 4.4.4 (SlimROM - AOSP).

I know that it worked before but when I try to set permissions to another value in root explorer, now I get an error (Warning! Changing permissions failed. Please be aware that some file systems (e.g. SD-Card) does not allow permission changes, also on my tablet (Android 4.4.2 stock).

What could be the reason for that? is this SuperSU related?

many thanks and regards
[SuperSU] shoey63:
Try fx explorer with root add on. Also nextapp sd card fix to sort out external sd card (if you have one)
[SuperSU] EVObastard:
I'm still having trouble with clean master. will not grant root permission. When I go to settings it is already set to grant but won't allow it from the app. Should something be set in the force user line?
[SuperSU] garyfunk:
Which version of SuperSU are you using?
[SuperSU] coukou:
Hello

I have a Galaxy Note4 N910C with lollipop 5.01. Three months ago, I had installed SuperSU 2.46 with Default access set to Prompt and Quick Boot (Reboot) and LBE security master were granted superuser permissions. Also, in SuperSu/Apps I got these 2 apps configured granted :).

For some reason that I can't explain, SuperSu no longer granted access. I uninstalled it properly and reinstalled it... same problem :mad:

In fact, the problem is the following: If SuperSu/Settings/Default access is set to Prompt, I get Superuser Request, I press Grant then I get Appsxxx has been denied superuser permissions (see bellow image).

On the other hand, if SuperSu/Settings/Default access is set to Grant, all apps has supersu permissions granted.

Moreover, in SuperSu/Apps NO apps configured granted.

I'll appreciate any help

Regards
[SuperSU] Rinoceros:
Try to flash the Beta of SuperSU
[SuperSU] shaggyskunk:
Yeah I agree with Rino - Flash the SuperSU zip - Are you running a Stock Rom or a Custom Rom - Reason that I'm asking - Is your use of LBE Security - I personally wouldn't use that app - Privacy Guard in CM & Slim based Roms is a far more comfortable choice... Imho...

Sent From my SM-N910W8 Running SlimLP 5.1.1 RRO Layers
[SuperSU] Rinoceros:
I am using LBE in the (Google) English translation and I am very happy with it. Using it already for years.

But indeed, it might be big pain in the a.. to configure.

You need to reboot twice before LBE is working in a proper way (second reboot after you grant is root access again).

But also he has problems with Quick Boot and that points out to some incompatibility issues with SuperSU 2.46 in Lollipop and should be solved in the Beta 2.49.
[SuperSU] coukou:
TNX for yr help;)

Yes I'm running a Stock Rom (Samsung original) XEH-N910CXXU1BOC3 Lollipop 5.01

I followed your advice and updated to SuperSu 2.49 beta via via TWRP recovery... same problem: If Default access is set to Prompt all apps denied superuser permissions. I may set the Default access to Grant to get superuser permissions.

What is weird is that it had worked well since 3 months until yesterday :confused: :rolleyes:

Is any how to configure apps granted?

Any suggestion be welcome
[SuperSU] garyfunk:
Uncheck Tapjacking, reboot the phone and see if you can Grant.
[SuperSU] shaggyskunk:
Are you running any apps with overlays - ie: Lux?

Sent From my SM-N910W8 Running SlimLP 5.1.1 RRO Layers
[SuperSU] garyfunk:
He has no idea what he installed or what an overlay is.

We will educate him.
[SuperSU] coukou:
Well done:good: It works :D

@shaggyskunk: I'm running Lux and Twilight..

Regarding SuperSU settings, do I've to check Enable su during boot?

what other settings to check/uncheck?

Regards
[SuperSU] shaggyskunk:
Did you add any apps Yesterday? SuperSU won't start giving you issues for no reason - It doesn't have a "best before" date ?

Sent From my SM-N910W8 Running SlimLP 5.1.1 RRO Layers
[SuperSU] garyfunk:
The only laugh I've had all day.

Thank you.
[SuperSU] Pkt_Lnt:
Now go into Lux and whitelist SuperSU so you do not have a security breach.
[SuperSU] shaggyskunk:
No - You shouldn't enable SuperSU during boot - And - It's better if you don't post the same questions in two different threads!

Sent From my SM-N910W8 Running SlimLP 5.1.1 RRO Layers
[SuperSU] garyfunk:
Why do tell him not to enable su at boot? If he has apps that need root at boot they won't load.
[SuperSU] coukou:
Are we speaking about this Lux?

So, I couldn't find/I don't know how to whitelist SuperSU :o

Regards
[SuperSU] Pkt_Lnt:
Settings, Advanced, Sleep List - add SuperSU
[SuperSU] shaggyskunk:
I've never seen anything that needs SuperSU enabled on Boot checked off - Having SuperSU enabled checked off is all that I have ever seen and used

Sent From my SM-N910W8 Running SlimLP 5.1.1 RRO Layers
[SuperSU] explorer-10:
Does Pseudopro have OTA survival mode?
[SuperSU] garyfunk:
Some of Chainfire's apps need su access at root. I have 4 apps that need access at root.
[SuperSU] coukou:
Done TNX:)

---------- Post added at 09:12 PM ---------- Previous post was at 09:04 PM ----------

Your image does show Enable Superuser checked

But does NOT show Enable su during boot into settings.

---------- Post added at 09:14 PM ---------- Previous post was at 09:12 PM ----------

Finally, do I have to check Enable su during boot ?
[SuperSU] shaggyskunk:
I don't have SU enabled during boot

Sent From my SM-N910W8 Running SlimLP 5.1.1 RRO Layers

---------- Post added at 03:26 PM ---------- Previous post was at 03:25 PM ----------

I don't have SU enabled during boot - But apparently some of Chainfire's other apps require it - I'm not running any of those apps

Sent From my SM-N910W8 Running SlimLP 5.1.1 RRO Layers
[SuperSU] egingell:
The short answer is that you can leave it unchecked unless you need it.

And I suspect init.d scripts might need root during boot.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] garyfunk:
Yes, init.d does need root.
[SuperSU] shaggyskunk:
The only other thing that I do - is in Developer Options - I have Root Access - Apps and ADB - BUT I have never had SuperSU settings with Allow on Boot checked - And I've never had any issues with Root or SuperSU

Sent From my SM-N910W8 Running SlimLP 5.1.1 RRO Layers
[SuperSU] garyfunk:
That's perfectly fine. No one is going call you out for not having it.
[SuperSU] shaggyskunk:
Oh - Thank god - I was worried that Chainfire was going to report me ?

Sent From my SM-N910W8 Running SlimLP 5.1.1 RRO Layers
[SuperSU] garyfunk:
Chainfire is no worry. It's StringIce you need to watch out for.
[SuperSU] mindmajick:
Always getting in trouble ;)

-> Sent from my mind to your screen
[SuperSU] shaggyskunk:
Hey majick - It's my reason for being ?

Sent From my SM-N910W8 Running SlimLP 5.1.1 RRO Layers

---------- Post added at 08:40 PM ---------- Previous post was at 08:39 PM ----------

What's a stringice? ?

Sent From my SM-N910W8 Running SlimLP 5.1.1 RRO Layers
[SuperSU] garyfunk:
StringIce is the opposite of ChainFire.
[SuperSU] coukou:
Sorry to bother you, What is init.d scropts and how to set it?

Regards
[SuperSU] egingell:
Flash a ROM that has it. You can do it manually, but I'm not about to explain how.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] EVObastard:
2.46
[SuperSU] It_ler:
This issue is fixed in v2.49 from beta thread.

My tapatalk signature:

Device:

SGS5 (SM-G900F)

ROM:

AllianceROM v8

Kernel:

Stock G900FXXU1BOC7

Recovery:

TWRP by Ktoonsez

Modem:

G900FXU1BOC7

If you have any question about or any issue with your SGS2, just ask in the New members friendly Q&A thread.

... for the SGS5, just ask in the Noob friendly S5 All in one support thread

If you need general help/assistence, please go to XDA-Assist.
[SuperSU] EVObastard:
Great that worked thank you.
[SuperSU] osjacob:
Anyone can help?

Heres the deal, i upgraded my galaxy gt-i9505 to android 5.0.1 official rom for galaxy s4. Everything is fine. But then I need root access so i followed the steps. Yes it did says rooted. So it should mean success but. Then when i use some apps it keeps asking me if my device got root access and these apps wont woRk. And its very frustrating my phone is like pseudo rooted. But i still want to use the official rom and i hope i dont have to restore to android 4.4

Tryed root checker snd they confirm my root access but i m not sure my device is fully rooted.

what should i do? How do I fully root my phone.

Ps. I ve spend now like a whole week working on it its still the same issue.

If anyone can help. Then please be gentle
[SuperSU] PIRATA!:
I'm sorry, where can I find the single SuperSU.apk of last version for manual installation from device?

No CWM, no PlayStore..

Tnx.
[SuperSU] Mike B.:
Have you tried flashing the stable SuperSU 2.46 available in the OP or the SuperSU 2.49 beta available in the beta thread?
[SuperSU] Pkt_Lnt:
removed
[SuperSU] Mike B.:
As mentioned countless times, the latest stable SuperSU installable ZIP is available from the link in the OP. If you don't want to flash the entire package, you can simply extract the files you want from that ZIP.

---------- Post added at 07:15 PM ---------- Previous post was at 07:12 PM ----------

Instead of using an unverified "mirror", it would be wiser/safer to simply use the official file from [MENTION=631273]Chainfire[/MENTION]'s own server, as shown in the OP.
[SuperSU] osjacob:
Indeed i flashed with success the update supersu 2.46 but its the same issue. Though i havnt tried the beta
[SuperSU] Mike B.:
The beta mostly addresses Lollipop-related issues and might solve your problem. You can find it THERE.
[SuperSU] osjacob:
Ok thanks. Im trying it now. First attempt failed. Which boot loader do u recomend?
[SuperSU] Pkt_Lnt:
Apk Mirror is run by Android Police and very reliable and trustworthy, otherwise I would not post it.
[SuperSU] Mike B.:
I'm very familiar with apkmirror, but with all due respect even though it is indeed generally "reliable and trustworthy" it might be best to get the file directly from [MENTION=631273]Chainfire[/MENTION]'s server, especially since they only mirror the apk and not the 'su' binary which may or may not be available to the user (we've all seen countless "I can't update the binary" posts). Considering how much trouble users seem to get into while installing/updating SuperSU, it seems wiser to go for the full official package. Just an opinion... ;)
[SuperSU] garyfunk:
Do you want the latest Stable version or Beta version?

---------- Post added at 21:31 ---------- Previous post was at 21:28 ----------

I think you want to use the 2.49 beta. There is an update to the binaries that fixed a few issues with Android 5.x.
[SuperSU] SecUpwN:
Thanks for letting me know. I fully understand it since he certainly has put an unbelievable amount of work into it.
[SuperSU] PIRATA!:
Both please.
[SuperSU] garyfunk:
You can't have both installed. Which one do you have now?
[SuperSU] PIRATA!:
But can I the install the SuperSU.apk regularly or copy/past manually in app folder??
[SuperSU] garyfunk:
What are you trying to do? You need to have the su binaries installed.
[SuperSU] PIRATA!:
I'd like to have both in my storage, as i have a device with KitKat with which I'd like to remain official, and a Lollipop device with which I'd like to put the beta.
[SuperSU] garyfunk:
I think you don't understand how SuperSu works.

However, just extract the SuperSU.apk from each file.
[SuperSU] Mike B.:
You can install SuperSU.apk as you would any other app, but it won't do you any good unless you're already rooted. SuperSU.apk is simply an optional tool to control which processes get root access but it can't root an unrooted device.
[SuperSU] shaggyskunk:
Yeah - looks like he's been around for a bit - But clearly needs to read more and have a much better understanding of what he's doing....

Sent From my SM-N910W8 Running SlimLP 5.1.1 RRO Layers
[SuperSU] PIRATA!:
Guys, I perfectly know what's SuperSU and when should it be installed.

I just want an version for installing it without having any internet connection, that it's not a CWM, but simple and classic .apk.

And I'd like last official and last beta, so both of them to install them respectively on two different devices.

I was asking only because I don't understand the differences between the one from PlayStore and the one inside the CWM package, as in this package there's also a lot of other stuff that I think it's not installed from the PlayStore.
[SuperSU] caldent:
Not understanding the issue with playstore. Its saying signature issue
[SuperSU] Mike B.:
Grab both the installable ZIP from the OP (v2.46) and the installable beta ZIP (2.49) from the beta thread. You now have 2 options, neither one of which requires an internet connection or access to the Play Store.

I'm not sure what you mean by "a CWM". CWM is, among other things, a slightly dated family of custom recoveries. If you have a custom recovery (CWM, Philz, TWRP, etc.), you can flash either one of your SuperSU packages from there. If your device is already rooted and you feel confident enough, you can move the su and supersu.apk files extracted from the ZIP in the correct locations but the script (the "other stuff") in the ZIP takes care of many other required steps that might be difficult to reproduce manually.

Once again: you cannot root a device from just downloading supersu.apk from the Store or installing it in any other way. I understand that you might want to try both the stable and beta versions but I think those of us attempting to help you in this thread wonder why you insist on asking about supersu.apk instead of simply using what's in the installable ZIPs.

I can only strongly suggest that you make a good dependable nandroid backup of your system before attempting to play with root issues unless you're absolutely positive that you fully understand the implications of what you're doing.

---------- Post added at 11:45 AM ---------- Previous post was at 11:42 AM ----------

No idea what you're talking about. What is having a signature issue with what? We can't even being to help you unless you tell us what the problem is.
[SuperSU] PIRATA!:
When I say "CWM file" I refer to a .zip file that can be flashed in a recovery console.

I need both of them because I would like to put the stable on my old rooted KitKat device and the beta on my Lollipop device that I'm going to root now.

I would like to be free to install Supersu without any recovery because I don't know if I'm going to install any on my S5 Prime.

I'm reading about FlashFire but would like to have an alternative solution in installing Supersu using some simple way with no recovery.

Last, as I'm attempting to use KingRoot or iRoot to roo tmy S5 Prime, after this I'd like to replace KingUser (formally Supersu compiled by another team) with official Supersu, I'm reading some procedures that involve the installation of the single SuperSU.apk with no any "other stuff" from the recovery .zip original file.

According to this, if I instal the only SUperSU.apk, then updating binaries using an internet connection, will all the "other stuff" be installed automatically?

I ask this because in this case I would end up with the same result.

Thank you.
[SuperSU] Mike B.:
I wish you'd simply look at the ZIP files we're all suggesting you grab. This might help you understand what "other stuff' they contain and do. Copying SuperSU.apk to the correct location is possibly the least relevant part. If, for whatever reason, you don't want to install TWRP or another custom recovery, you need to find some other method of rooting your device, such as CF-Auto-Root (requires Odin but restores a stock recovery afterwards).

The question you keep asking has been answered many times: the latest SuperSU.apk is readily available in the stable and beta ZIPs, but it won't do you any good to just install that apk. The remainder of this discussion probably belongs in a CF-Auto-Root thread or wherever your device is supported.
[SuperSU] caldent:
Well my superSu is in chinese and the one from playstore as well as are having signature issues
[SuperSU] Mike B.:
我不明白

What exact error message are you getting, from which application, when doing exactly what?

Based on my best guess: If an application won't install over another version because of conflicting signatures, it means that they were compiled by different people with different certificates. The solution is to uninstall the existing application first, then install the new one.The official SuperSU files can be obtained from either the Play Store or directly from [MENTION=631273]Chainfire[/MENTION]'s server. Any other version should be avoided, especially if it bears someone else's signature.
[SuperSU] caldent:
Well the update from Playstore didnt install and also unrooted my device. I will check whether just by installing the Su it can be done

---------- Post added at 11:48 PM ---------- Previous post was at 11:45 PM ----------

Btw any idea how to change language of the SuperSu app
[SuperSU] shaggyskunk:
The app on the store is in English

Sent From my SM-N910W8 Running SlimLP 5.1.1 RRO Layers