yashsingh1/xdaforums huggingface dataset:
[SuperSU] Chainfire:
For those who keep getting popups (I've flashed the firmwares stated to have this issue and unfortunately have not been able to reproduce), please let me know the outputs of these commands from adb shell:

$ pm path eu.chainfire.supersu
$ su
# ls -lZ /data/data/eu.chainfire.supersu
# ls -lZ /data/data/eu.chainfire.supersu/files
# ls -lZ /system/app/Superuser.apk
# ls -lZ /data/app/*supersu*.apk
# ps | grep supersu
[SuperSU] Braxos:
[MENTION=631273]Chainfire[/MENTION] here is a SS of the commands above hope they are OK.
[SuperSU] Zen Arcade:
V2.02 - installed on i317 t0lteatt - 4.4.2 UCUCNE5 - stock - no issues found.
[SuperSU] Chainfire:
Seems absolutely fine ...
[SuperSU] Braxos:
[MENTION=631273]Chainfire[/MENTION] when I used $ su it prompted for root access and I granted it even I had SuperSU on grant and not prompt. So something is wrong. I think

If I flash update of nightly omni SuperSU must be flashed too? It doesn't survive
[SuperSU] Chainfire:
Well yes, obviously something is wrong, but we're no close to finding what that is :)

Install the backup script from SuperSU settings.
[SuperSU] Braxos:
Isn't it always on if you flash SuperSU via recovery? I remember it asked to install it after clean flash of ROM. But never after that, even if I flash the ROM and SuperSU doesn't survive and i reboot to recovery to flash SuperSU. It never asks again for the script to installed.

Hint dunno if it has something to do with this.

If I flash the ROM without gapps I get FC from chrome always no way to open it. I have to reflash gapps with the ROM. ATM I am flashing all together every time .

Omni+gapps+SuperSU, so that all will work.
[SuperSU] greogory:
I'm sorry for my long delayed reply. My work week went to hell the next morning and I didn't have a chance to do fun stuff until this evening. Anyway...

This definitely feels like a simple flashing problem going from <=2.0.1 to 2.0.2. I'm using Philz' latest recovery. Maybe upgrading to SuperSU 2.0.2 using an earlier version of Philz, TWRP or straight CWM won't have the issue.

If I "forget" an app that was already approved by 2.0.1, 2.0.2 still needs it manually approved even with "grant" as my default. The behavior is basically the same as if re-authentication is on, or that all apps are unknown to 2.0.2, and "prompt" is selected. 2.0.2 seems to simply ignore the settings from 2.0.1, even though they still appear to be the same in settings.

Note that 2.0.2 only requires re-approval once for each qpp, so as I said before this isn't a big deal.

I also just finished testing 2.0.2 installed to a freshly rooted stock NE5. The symptoms did <i>not</i> occur, and "grant" worked as expected. I didn't have to approve anything other than Busy Box, and it simply ran something before I remembered to change "prompt" to "grant" after I rebooted.

Thanks again for all you do,

Greg
[SuperSU] mike2587:
Hello all, can someone share latest supersu 2.02 apk? I need it because it crashes all the time on my galaxy note 8 using the zip upgrade...Thank you
[SuperSU] egingell:
It's in the zip file.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] mike2587:
Yea I've just seen it, anyway installing the apk manually it works, but it can't remove the samsung knox...
[SuperSU] Paget96:
I have problem, I flashed zip for latest version, app works,but after restart app disappear from launchers drawer :(

I look in apps, app is installed,and work, ask me for grant or deny, but hidden, I try to run it with link2sd but,app say could not launch, I try to reinstall apk, same thing ,after rebot,app disappear :/ ehat to do??

I have LG p700

running CrystalPA based on latest paranoid android
[SuperSU] Pkt_Lnt:
Doesn't PA have a superuser section under settings? It should be there.
[SuperSU] Paget96:
have, but ,when I go,nothing is there :(

In fact, the supers works, but it does not have to Launcer
[SuperSU] angusc:
Hi chainfire,

I just wanted to give some feedback on the latest update, I have applied it twice to my HTC ONE dual SIM phone but each time after a reboot my device will keep rebooting. It boots into the operating system but then after about 1 minute it will reboot again. The first-time it happened I did not know what caused it as I has made changes in sense toolbox, I had to use a NANDROID to fix it. But the second time when I updated SU and rebooted

it started again, I then uninstalled the SU update and was back to normal again.

have the dual SIM fringe UK which is stock ROM and rooted only.
[SuperSU] devilex94:
[MENTION=631273]Chainfire[/MENTION] This one is important comment Chainfire.

There is a bug i am facing in SuperSU but not in Superuser by Clockworkmod. (Could be su binary or app)

The bug is that i have root access and mounted /system as rw but when i copy any file to /system it fails . but adb push works.

I tried different root explorer apps but result is same. but on SuperSU it fails. I love SuperSU the most so please fix this problem as soon as possible ;)

EDIT: I am not facing the problem in Chinese Root app "VRoot" also . it's only in SuperSU . And i was using SuperSU v2.02
[SuperSU] Chainfire:
Does this fix the issue? BETA-SuperSU-v2.03.zip
[SuperSU] frans-jan:
I have the same problem. Su works, asking permission etc. but there is no app icon, and I can not open it in app manager. installed update 2.02 but no change.

running stock android on galaxy tab pro 10.1

what can I try?
[SuperSU] MattBooth:
I've held off having this whinge for a long time... But "the SU binary needs updating" NEVER works. Not the normal way, nor the TWRP way. EVER. On multiple devices.

I also just updated using the flashable zip (2.03) and it still shows the SU binary needs updating :/
[SuperSU] Chainfire:
Point to the download of a specific firmware exhibiting this behavior on a clean flash for a device I actually have (see signature) and I can check it out. If not, your comment is useless.
[SuperSU] Chainfire:
Sometimes this is caused by Android having conflicting information about the SuperSU APK being installed.

From a root shell on your device:

pm uninstall eu.chainfire.supersu

Or with adb:

adb uninstall eu.chainfire.supersu

And reboot. May have to re-install SuperSU from Play. Might fix the issue.
[SuperSU] dmagician:
Now all is working

On my old

I9100

with

Resurrection Remix v5.1.5

on it, the latest SuperSU v2.0.2 is not working on it ("su binary needs update" loop).

The same version is working flawlessly (since firstly updated) on my second device - Nexus 4.

I Just now saw this BETA-SuperSU-v2.03.zip -- tried it and

No "su binary needs update" looping

.

Thanks you!
[SuperSU] MattBooth:
See my signature for my i9505 ROMs ;)

Also, you, once upon a time, had an i9300. It never worked. Honestly, not over the 2 years I've ahd the device :( Not on my own, or Wanam ROMs (when he did ROMs). I always had to clean flash with it integrated or flash the zip from your site. This is how I integrate today: https://github.com/Kryten2k35/UltimaROM-i9300/commit/ffd2451e372e06fdcccb745cd319ea868b95d9a4 since it's easier to simply use your install script and dump the files in an installer folder. It works well.

EDIT: I'm trying 2.03 now

EDIT:

2.03 exactly the same, flashed zip from the link you posted. Still tells me I need to update the SuperSU binary.

EDIT:

Root apps still work. I just can't use the SuperSU app to manage access.
[SuperSU] Chainfire:
So I just downloaded your latest version for the i9505, which comes with SuperSU v1.94.

- Reboot recovery

- Wipe system, data, cache

- Flash ROM

- Reboot

- Install SuperSU via APK

- Allow binary update "normal"

- Reboot

- SuperSU working as expected

- Reboot recovery

- Wipe system, data, cache

- Flash ROM

- Reboot

- Install SuperSU via APK

- Allow binary update "twrp/cwm"

- Reboot (automatic)

- Install SuperSU (automatic)

- Reboot (automatic)

- SuperSU working as expected

- Reboot recovery

- Wipe system, data, cache

- Flash ROM

- Reboot

- Reboot into recovery again

- Flash SuperSU ZIP

- Reboot

- SuperSU working as expected

So... yeah...
[SuperSU] MattBooth:
Fair enough, but I was using 2.01 without a problem, flashed form your site. I cannot get 2.02 or 2.03, flashed through your site, to work.
[SuperSU] Chainfire:
Is it possibly you have installed something that might be interfering? Thinking things like busybox (also works for me, but perhaps specific installer/settings?). I'm not saying your report is invalid, just that I can't reproduce the case, and thus I can't really do anything about it.
[SuperSU] MattBooth:
No I understand :) I've tried a factory reset and then to flash on top, but no dice. Next I'll try a totally clean installed version. It worked for you, so, I should be good then :)

While I have your attention... SuperSU has changable app icons. I wanted to add this to my AOSP Mms (and probably Email and such later), and Iv'e tried a couple of ways with no luck. Would you mind sharing how you achieved this?
[SuperSU] Chainfire:
http://www.chainfire.eu/articles/133/_TUT_Supporting_multiple_icons_in_your_app/
[SuperSU] MattBooth:
Brilliant, thanks :)
[SuperSU] nexusmaniac:
I can confirm that 2.02 works fine with the new L preview update :) And by fine, I mean there isn't fire bursting out of my phone ;)
[SuperSU] pyrogoggles:
Do most apps work with it? (and not cause bootloops)
[SuperSU] typos1:
Hello, I spent ages trying to get the su binary updated on my Find5 running OmniROM, that was at the weekend, but I did it in the end.

Just updated the ROM to the latest build and now I m getting the "su binary needs to be updated message" again, it doesnt reboot and if I do it manually nothing happens.

I really cannot remember what it was I did in the end to make it work at the weekend and I ve gone all through my browser history to try and jog my memory, but cant find anything, just thought it might be easier to ask on here.

Thanks in advance.
[SuperSU] nexusmaniac:
Yep, all of the root apps I have installed work just fine :) no bootloops and no FC's (yet)
[SuperSU] Einwod:
Same problem on my HTC One M8. Have reinstalled many times, set the programme how I want it and still get the permission requests. Is there no fix for this yet? :confused:
[SuperSU] chajang:
Hi. Have you try Greenify and Titanium Backup?

Android L on Nexus 5 will go to bootloop when using Greenify as rooted mode and Titanium Backup seems like cannot find SU binary.

Thank so much!
[SuperSU] devilex94:
Nope problem is still there
[SuperSU] Chainfire:
Reboot for Greenify is likely not a SuperSU problem, it just doesn't support L properly yet. Have you tried the 2.03 version for Titanium Backup? Not sure if TiBu has been updated for L either, but they're usually pretty quick with these things...

Are you sure you're not just doing it wrong? Mounting system r/w with ADB has no effect on file explorers. You need to remount via the file explorer itself.
[SuperSU] devilex94:
I am definitely sure i am not doing anything wrong. i even tried mounting system through terminal. system get mounted as rw but when i try copying any file to system every root browser fails but while having Superuser (clockworkmod) and vRoot there are no problems and i get success message :confused:
[SuperSU] Chainfire:
Which explorer app have you tried - is there a button inside the app itself to mount r/w?

Mounting system through terminal will not make it r/w for file explorers.... just for the terminal. You don't have this with CWM SU or vRoot (which is based on CWM SU) because that doesn't have mount namespace isolation - which is a security feature.
[SuperSU] devilex94:
ohk now i tried an explorer with mount r/w button ( root explorer ) . first tried Superuser (clockworkmod) - No problem

Now i tried Beta-SuperSU 1.0.3 with same root explorer with r/w button. mounted system to r/w . But this again time it failed :(

Weird thing is that i have root and mounted system folder as r/w still any file is not getting copied :confused:
[SuperSU] Skhulile:
Hello guys, can someone help me here, I keep getting the message saying SuperSU binary needs to be updated. So i decided to use the Full Unroot option so I can start afresh in the hope that I'll get rid of the annoying msg. I flashed SuperSU V2.02 via CWM Recovery. things seem to work well, didn't get that error again but after some time it is back what's annoying is the fact that whether I choose NORMAL install or CWM/TWRP Recovery install the msg keeps coming up, it seems like the Binary never gets updated please help. I'm using the Galaxy Note 10.1 running a Custom ROM, Gnabo V6 based on Android 4.4.2
[SuperSU] HaiPBM:
HELP!

I am trying to add root and SuperSU to my own rom but after the installtion of the rom the supersu always need to update the binar and i dont know why but it always cant update!

what I need to do?

I put the apk in system/app and "su" in xbin folder

(Galaxy S4 I9500 rom 4.4.2)
[SuperSU] Pons:
Read the updater script/Binary in the OP's and do what it says. It does more than just puts the app and Binary in their respective locations.
[SuperSU] zezoassiri:
root doesn't work if the language is Arabic on 4.4.2 kitkat

is this issue is known ?

And Any fix or update to this annoying problem ?
[SuperSU] HaiPBM:
i added this lines to my update script:

set_perm_recursive(0, 2000, 0755, 0755, "/system/xbin");

set_perm(0, 0, 06755, "/system/xbin/su");

symlink("/system/xbin/su", "/system/bin/su");

and its not working
[SuperSU] Skhulile:
Hello guys how can i update the SU Binary, it seems like the "Normal" and "CWM/TWRP"

options are not working coz I then get a msg when I reboot my device that says I have to uodate SU Binary, BTW i'm using the Galaxy Note 10.1 Android 4.4.2
[SuperSU] Pkt_Lnt:
Five hours, seriously? Did you read all the other posts about this problem and why there is no instant fix?
[SuperSU] Skhulile:
I hadn't but it's cool now, after flashing the 2.03 beta I only get that error when a new app asks for root access and when I choose "Normal" and the error is still there, I go to the other option and then it gets fixed
[SuperSU] NZgeek:
If you want to integrate SuperSU into your ROM, you'll need to do everything in the install script, not just parts of it. You're missing several files that are needed to make things run.

If you can't get SuperSU working as part of your ROM, try going into recovery and flashing it manually. If this makes SuperSU start working, it means you're still not doing everything the script does.
[SuperSU] dtronx:
Having a problem after I hide my supersu icon. I tried all the codes as suggested on my T-Mobile Galaxy S5

Launch from dialer: *#*#1234#*#* or *#*#7873778#*#* (*#*#SUPERSU#*#*)

NOTE: Not all phones take both codes. On some phones you need to use single *# instead of double *#*#

Nothing seems to bring it back up so I can make it visible again any help please
[SuperSU] jazzruby:
Try launching the app from terminal with Activity Manager

am start -a android.intent.action.MAIN -n eu.chainfire.supersu/.MainActivity

-JR-
[SuperSU] abilash10:
How may i unroot grand 2?
[SuperSU] Primokorn:
Select the unroot feature from SuperSU settings
[SuperSU] abilash10:
Will it unroot sucessfully?? And take it in to orginal state..And may i again able to root my phone if i want??
[SuperSU] Primokorn:
Yep but you may have a counter flash to reset for warranty purpose.

You can root and unroot 100 times a day :)
[SuperSU] abilash10:
Thanks for reply.how may i can do flash count zero?
[SuperSU] darkluna:
You can use chainfire's "triangle away" app. You can search it here or get it from the play store.
[SuperSU] abilash10:
Thanks i done unroot by super su setting and it unroot but my device showing following mesaage while updates..
[SuperSU] abilash10:
In recovery mode .
[SuperSU] shibadoo:
Running CM11 on my Samsung Galaxy S Plus (I-9001), SuperSU worked fine for a long time. Yesterday I wanted to check which apps already have root privileges, and when starting SuperSU, it wanted to update the su binary. The "normal" mode did not work at all, via TWRP it seemed to work. But when rebooting, the phone freezes at the homescreen so that I can only switch it off. Any ideas why updating the su binary causes the phone to freeze?
[SuperSU] Phil3759:
[MENTION=631273]Chainfire[/MENTION]

I did not find any info about chattr.pie file you include in new packages

What do they offer in addition to chattr file? Wondering as I am updating the recovery builds with your latest installer
[SuperSU] jazzruby:
Could be related [MENTION=631273]Chainfire[/MENTION] G+ post here:

https://plus.google.com/+Chainfire/posts/ZtXAhw164QD - scroll down to PIE

-JR-
[SuperSU] WR3CCKL3SS:
[MENTION=631273]Chainfire[/MENTION] having an issue with SuperSu v2.02...i keep getting silent denials when starting up Googy's STweaks and it's preventing me from accessing the app. I have it set for all apps requesting root access to be granted but for some reason on this version it's not letting this particular app have root access... Now here's the funny part... As soon as I downgrade to v2.01 everything is completely fine and the app is granted root access and automatically opens up.. Idk what it is about v2.02 but it does not like the latest Googy's STweaks . I have already posted about this in the kernel thread to see if anyone else has had this issue... I'm going to stick to v2.01 til a resolution is found... I have to have this app to control the kernel.... Thanks in advance for any help

OH btw I'm running the latest AICP jflte nightly and also the latest Googy revamped CM kernel build {8/13} v1.1.5
[SuperSU] Phil3759:
Ok

I understand better the new chattr.pie file

However, I still have a question: since recovery (cwm) comes with its own kernel and busybox chattr, I guess I can safely not include the chattr and pie files in recovery image. I'd still use the installer, but rely on busybox binaries
[SuperSU] Rom:
When Play Store verison is update ? :)
[SuperSU] frans-jan:
tried it, but get the mesaage :failed to connect to dumpstate service

hmm, strange, after this I uninstalled the update, and the program icon is back and working.
[SuperSU] :
Sometimes just update zip for trying experimental versions of android (like android l) and play store for the rest of us
[SuperSU] Rom:
Ok so its beta version of SuperSU thanks for informations :)
[SuperSU] marcran75:
Also for future reference, it's against forum rules to ask for ETA's or updates.
[SuperSU] Rom:
Sorry but i have don't understand :rolleyes:

Can explain me again please ?

Thanks
[SuperSU] kingvortex:
A message from the moderators.

Does that help? You should also read the Forum rules. :)
[SuperSU] dtronx:
Tried what you said and am getting this response:

ava.lang.SecurityException: Permission Denial: startActivity asks to run as user -2 but is calling from user 0; this requires android.permission.INTERACT_ACROSS_USERS_FULL at android.os.Parcel.readException(Parcel.java:1425)

at android.os.Parcel.readException(Parcel.java:1379)

at android.app.ActivityManagerProxy.startActivityAsUser(ActivityManagerNative.java:1921)

at com.android.commands.am.Am.runStart(Am.java:494)

at com.android.commands.am.Am.run(Am.java:109)

at com.android.commands.am.Am.main(Am.java:82)

at com.android.internal.os.RuntimeInit.nativeFinishInit(Native Method)

at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:235)

at dalvik.system.NativeStart.main(Native Method)

---------- Post added at 01:43 PM ---------- Previous post was at 01:39 PM ----------

Ok thanks got it open finally running terminal as root
[SuperSU] Solace50:
using golden eye v38 with everything stock on fresh installs with the current version of SU you are unable to set anything else other then "prompt" for default user permissions. i had the same issue on 4.3 v20 but was able to work around it by just disable/re-enabling su in the ui. doing that as of now does nothing and apps will still request access despite it should approve by default.
[SuperSU] bearusa:
I'm having a problem with v 2.02

I have searched and can't find anything. If I select grant in settings it stills throws a pop up for prompt although it's set to grant. I've reverted back to v 2.01 and reinstalled 2.02 and same happens again. Any Advice. Note 3 running GNG1 Alexandr Dev base
[SuperSU] h00ligan:
Weird issue on replacement note 8

I rooted a first note 8 got the expected super su stopped and upgraded via play store v 2.0.1, no problem worked like a champ.

Second replacement device rooted and passed, getting super su stopped message but the latest play version is showing installed and there's no update.

The on,y thing I can ink is using Odin 3.0.7 vs 3.0.9 installed a newer version but the upgrade to the play version works while the same version installed is giving me the quit message.

Any advice on how to proceed? I'm new to android and in the process of removing all apple devices from my life. Unfortunately that means despite some past dabbling I don't know much about how to correct this issue.

Or even how to revert to stock to maybe use Odin 3.0.7 and then upgrade again. I did not allow google to restore apps to the new device as I have titanium oro and was planning on using that for a full transfer. So I don't think during device setup it was installed. Root check fails presumably because it can't get su permission but opine 3.0.7 and 3.0.9 have flashed with a pass

It's odd the same device gave no issues and the upgrade solved the issue but the same version didn't.

My best guess is I have made a mistake and there's some conflict for the item, I just don't know how to remedy.

Thanks for any guidance and reading.

Fixed

I used the fantastic unified toolkit root options which reinstalled an old version then updated and no more issues.
[SuperSU] Chainfire:
This issue has been reported by several users, however I have still not been able to replicate the issue at all, so I still don't know what the cause is ... have you tried cleaning Dalvik/ART cache?
[SuperSU] JaviR:
Hi, I'm making my ROM with Android 4.4.2 and it's possible to root the device and use SuperSU.

My problem is, I don't want SuperSU asks every time if allow the APK to get root and that countdown. I need SuperSU gives ROOT BY DEFECT always. I know I can go to settings and choose this, but I need to do it by defect because I want this configuration on my ROM.

Is there any way to change the "by defect" options before add SuperSU to my ROM?

I'm working on a Rockchip RK3188 device and Android 4.4.2

Best regards
[SuperSU] bearusa:
I will wipe dalvik re install v 2.02 and see what happens.
[SuperSU] Frank Westlake:
When your "ROM" is first booted you could write a defect preferences file to the data directory.

Frank
[SuperSU] Solace50:
thats weird given it occurs on a fresh install of the rom it should be able to be reproduce. i believe dalvik was at least wiped once after flashing ktoonz kernel. i suppose it cant hurt to try it again.

also older versions had the issue but re-loading SU in the settings seemed to be a workaround. maybe i can try to use an older version in the meantime, the only thing is im not sure if there's any issues/lack of support for older revisions since its 4.4.2 and not 4.3 anymore.
[SuperSU] Chainfire:
Isn't it. I've followed instructions from others installing a few dozen firmwares and I have never been able to replicate it. If you can do a fresh ROM install without any personal info, but with SuperSU and some root app that demonstrates the problem, then do a backup with TWRP that I can restore on one of my own devices, so I can replicate the issue ... you are on an i9505, right?
[SuperSU] bearusa:
I can gladly report that a dalvik wipe then reinstall 2.02 through Cwm has worked this time.. Su pro now working properly again. Thanks chainfire
[SuperSU] JaviR:
Do you mean run a bash script (as example) from the init.rc file?

---------- Post added at 02:05 PM ---------- Previous post was at 01:47 PM ----------

I found the settings are in:

/data/data/eu.chainfire.supersu/shared_prefs/eu.chainfire.supersu_preferences.xml

and the label in the xml is:

<string name="config_defaul_access">prompt</string>

after manually change from APP settings now it is:

<string name="config_defaul_access">grant</string>
[SuperSU] Solace50:
done, i need an ftp or something to upload to due to the file size.