yashsingh1/xdaforums huggingface dataset:
[SuperSU] vn00914361:
You could try the latest binary only without installing any applets and see how it goes
[SuperSU] egingell:
Or use the previous version of busybox. Secure Settings doesn't require updating busybox.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] pemell:
Yeah thanks. I've got it working. As I felt let down I changed app to busybox x. :)
[SuperSU] gffmac:
Hi Guys, Im currently returning my phone (HTC One M7) to stock to go back to htc for repair. Everything went fine s-on/locked/recovery restored etc last step to do a Full unroot via supersu and a factory reset.

Supersu uninstalled fine but after factory reset then setup, supersu installer pops up prompting to install supersu again??

So obviously Ive still got root is there something I can remove with root explorer to stop re installation then Full unroot via supersu again?

Thanks
[SuperSU] Pons:
Sounds like you need to find a RUU/return to stock thread for the m7. I'm mobile right now, so I can't dig up a link for you.
[SuperSU] poffsoft:
superSU disabled at boot

Hello,

I've a rooted chinese kidtablet, rk3028 SoC

At every boot the SuperSU disabled somehow, and i can only enable via play/superSU.

My question, how can i find what is disable it at boot, and how to enable superSU permanently? i've tried to install as system app, but doesn't working (after install the superSU is missing, install again via play).
[SuperSU] DSA:
Run a log via adb or an app from the play store is probably your best starting point
[SuperSU] FlanjeUK:
Anyone on PA having issues flashing SuperSU, have you tried v1.86? It works fine for me when flashed over SuperUser (SlimKat) then update the binary through the PlayStore to 1.94... Could be worth a shot
[SuperSU] poffsoft:
you mean:

ADB shell

log

?

alogcat after every reboot is empty...

sorry, i'm newby.

MOD:

the log:

W/PackageManager( 383): Trying to update system app code path from /system/app/eu.chainfire.supersu.apk to /system/app/Superuser.apk

W/PackageManager( 383): Code path for pkg : eu.chainfire.supersu changing from /system/app/eu.chainfire.supersu.apk to /system/app/Superuser.apk

W/PackageManager( 383): Resource path for pkg : eu.chainfire.supersu changing from /system/app/eu.chainfire.supersu.apk to /system/app/Superuser.apk

...

I/PackageManager( 383): /system/app/eu.chainfire.supersu.apk changed; collecting certs

D/dalvikvm( 383): GC_FOR_ALLOC freed 213K, 12% free 6123K/6924K, paused 32ms, total 32ms

...

D/dalvikvm( 383): WAIT_FOR_CONCURRENT_GC blocked 15ms

D/PackageManager( 383): No files in app dir /vendor/app

W/PackageManager( 383): Application package eu.chainfire.supersu already installed. Skipping duplicate.

MOD2:

Thanks, solved.
[SuperSU] tamingsarix:
Is this normal?? No apps ikon
[SuperSU] aavvaallooss:
No
[SuperSU] gothicasshole:
OK there's 2 types of root one is perm root 2 is temp root sounds like you have a temp root you might need to find an exploit to make it perm root otherwise every time you reboot you loose root go back to the thread where you got it and also check your system.bin and super.su should be there if not try moving it??
[SuperSU] claytonjn:
Are the apps with the missing icons still installed on your device?

-Sent from my Developer Edition Galaxy S4 using Tapatalk
[SuperSU] jorceshaman:
That's where my mind went but I figured it was too obvious for someone that knows how to root so I didn't end up putting it. Lol
[SuperSU] Holmes.Sherlock:
I am having SuperSU 1.94 installed. Is it possible to configure it in a way such that when a pop-up asking root access will be displayed, by default, Ask Again in 15 minutes remains checked to minimize the chance of granting permanent access by mistake?
[SuperSU] NZgeek:
This will happen if you give root access to an app, then later remove that app. SuperSU stores the package name, but because the app isn't there any more, it can't display the icon or friendly name of the app.
[SuperSU] DecypherT:
So suddenly supersu tells me my pincode is wrong. I'm 100% sure I'm using the right one.

Is this a know issue and/or latest busy box related?

Supersu v1.94 & busy box Pro v 13

Send from my Nexus 4
[SuperSU] egingell:
I don't know where the password is stored, but it might be where one expects it to be. Have you tried clearing SuperSU's data?

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] DecypherT:
well using that method is fixed in a previous release.

' Clear data no longer clears PIN code'

Send from my Nexus 4
[SuperSU] egingell:
Bummer. It has to be somewhere, though. Maybe /data/system (don't delete this folder)?

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] DecypherT:
found a superuser.cfg but can't open it :banghead:

Send from my Nexus 4
[SuperSU] egingell:
If its in SuperSU's data directory, is not what you're looking for. That would be deleted when the data is cleared.

We'll probably have to wait for [MENTION=631273]Chainfire[/MENTION] or anybody else more knowledgeable.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] :
Working on my c1505

working fine !!

thanks !!
[SuperSU] Chainfire:
Remove /system/.pin through adb shell in recovery
[SuperSU] DecypherT:
thanks!

EDIT: Confirmed working.

Send from my Nexus 4
[SuperSU] poffsoft:
Permaroot is ok. Superuser.apk is ok . Just superSu.apk disabled every boot. I've not idea, not knowledge, so changed to superuser...
[SuperSU] fdecker:
Version mismatch

I installed SuperSU 1.4 and that is what shows in the about screen for SuperSU. But if I go to Root Checker it shows:

su found

[/system/xbin]

Version:1.93:SuperSU

Do I have to SUs? Or is the issue with root checker or that maybe the internal signature of the file wasn't updated for 1.94?

---------- Post added at 04:44 PM ---------- Previous post was at 04:37 PM ----------

I am not sure if the issue is with SuperSU or ES FE. It says that it's root test fails. I only have seen this issue with this and File Manager. Logs seem to show

connect failed:java.io.IOException: Connection refused

try to create su proc

successfully get the SU shell proc

chmod estool succ

start root server succ, try connect

connect failed:java.io.IOException: Permission denied

SU Check result:false
[SuperSU] jazzruby:
1.93 is the SuperSU (su binary)

1.94 is the SuperSU (su app)

Both are current versions

-JR-
[SuperSU] soulkyo:
Hi, sorry for the noob question but is this supersu compatible with my I8190L galaxy s3 mini model? Is this compatible with all the models? Thanks for the kind answer.

Sent from my GT-I9300
[SuperSU] NZgeek:
SuperSU should work on pretty much everything. It's been a while since I saw any problems regarding a Samsung phone, so it should be a safe install.

One thing to remember is that just installing the app from the Play Store is not enough. SuperSU needs to install its own copy of the su command, and this requires either existing root access, or for you to flash a zip file from a custom recovery (e.g. CWM, TWRP, PhilZ).

If you need a copy of the zip, there's a link in the first post. This takes you to a download page, from where you can download the zip. The download page confuses some download managers, and they treat it as if the page was the actual zip file. The page is only a few KB in size, and the zip is larger than 1MB.
[SuperSU] merquise:
HI,

Just to say that when trying to adb sideload flashable SuperSu 1.94 zip on my stock 4.1.2 Samsung Galaxy S2 it gave me Error 255. Here on xda it says that the error means that the

http://xdaforums.com/showpost.php?p=35429627&postcount=2

Don't know why...anyway i solved the problem by sideloading the older SuperSu v 1.43 and then it updated itself through Play Store...
[SuperSU] C_M@#u77:
SuperSU installation.

Hi Chainfire and other guys,

I would much want to install your SuperSU on my GalaxyS4, but, i need some little help, please :confused::(. I have my phone rooted with CyanogenMod CM11 rom, which has the superuser app into system menu. I want to install your SuperSU :good: over the superuser:rolleyes: . What will happen if i will do that :confused: ? I won't brick my phone :confused: ? I have been searching for this answer in few sites, but not a full answer explanation :crying: ...! How do i install the SuperSU and get rid of superuser :confused:. My phone is GalaxyS4 i9505 rooted, with CM11 rom on it.

Your help is very appreciated and needed.

Thank you very much in advance.
[SuperSU] Vonnegut:
Noob question

Today i've studied how the supersu.zip works.

I hope you'll be forgiving if i'm going write anything stupid.

As far as i can see, supersu takes advantage on the init.d support to launch the deamon on boot.

ROM with stock kernels which do not support init.d runs the deamon through install-recovery.sh (did i get that right?)

What if a ROM has neither init.d support nor does have the install-recovery.sh?

Rumors say that in a few weeks from now, all of the MTK based smartphone will get updated to kitkat (even my THL W200) and i'm pretty sure the ROMs will be in that situation.

I guess we will need to flash a custom boot.img supporting init.d then, right?
[SuperSU] jong31:
I am assuming you have a custom recovery since you are on cyanogen. All you need to do is download the supersu zip from chainfires website and flash it with your custom recovery. It will become your "default" su manager within cm. It won't completely get rid of cm's superuser implementation, but it will work over top of it.
[SuperSU] C_M@#u77:
Thanks

Thank you very much for the info, jong31.:highfive::highfive::highfive::highfive::good:
[SuperSU] jeswinjv:
Was feeling disturbd with previous versn....hopng diz will .....:)

via XDA Premium developer's-app
[SuperSU] jcicora:
Had there been any success flashing with TWRP 2.7.0.0? Every time I try it immediately fails.
[SuperSU] michierusama:
I always flash it with 2.7.0 and all is good.
[SuperSU] TDSJR:
Same here.

Sent from my ARTistically, Mahdified LG-D801 (dr87 4.4.2)
[SuperSU] Vonnegut:
No reply?

I'm also curious about a thing i found in the bash script, namely the su --install command.

Let's say that we're talking about a device like mine: a THL W200 running JB 4.2.1

In this case i could root my phone even with ADB, with the following commands:

adb push ./from_whatever_dir/Superuser.apk /system/app/

adb push ./from_whatever_dir/su /system/xbin

adb shell rm /system/bin/su

adb shell ln -s /system/xbin/su /system/bin/su

adb shell chmod 6755 /system/xbin/su

Would that be right or i should add the line adb shell /system/bin/su --install ?

What does exactly the su --install command do?
[SuperSU] jcicora:
Well crap, I wonder what's wrong now...
[SuperSU] jeppuda:
im having the same problem. Every time I reboot my phone and click on supersu app it says I need to update binary. I install supersu zip through custom recovery and eveything works. Every time I reboot, I have to go back in recovery and reinstall supersu. I have a sprint galaxy s3. Can you explain how to move super.su into system .bin. Can anyone give me a solution to this problem. Thanks
[SuperSU] blaz1nr:
Take any flashable zip you have lying around. Open it with 7zip or whatever. If a system folder is present ,then inside that. Make a bin folder. Drop the su.binary in it. Then flash it. Don't use chainfires zip because it installs a totally different way,from other zips. Make sure to remove the zips contents before installing. That way you only install the binary. Not the meta-info folder only what's in the system folder.
[SuperSU] jazzruby:
Let's try and figure out what's going on.

Reboot your device and run the following commands from Terminal Emulator:

su -v

ls -la /system

ls -la /system/app

ls -la /system/priv-app

ls -la /system/bin

ls -la /system/xbin

ls -la /system/etc

copy/paste results for each command here

-JR-
[SuperSU] egingell:
Typo alert... Forth command - la -la /system/priv-app

Edit: Is fixed.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] daveid:
You don't necessarily need root, with an unlocked bootloader you can flash a custom recovery and thus a custom rom without having root access (except through the recovery which was loaded with fastboot).
[SuperSU] dimebagdan65:
If you can dodge a wrench, you can dodge a ball. If you can flash a recovery/rom, you can flash SuperSU (dunno how relevant that is, just wanted to use that quote lol)
[SuperSU] signumized:
I have some ideas for improving the app's usability (only if they can be implemented, of course :) )

1. There should be a possibility to filter logs by app.

You can open an app and see there via another button the logs associated with it.

2. The user could swipe in order to pass to the next log in the list.

This way its simpler to follow some app's logs.

3. Also, an export log would be useful, for better analyzing logs, search through them etc

Thanks for the fixed bugs so far :).
[SuperSU] pdppdp:
Great ideas.

+1

Gesendet von meinem GT-P1000 mit Tapatalk
[SuperSU] BULL3TPR00F:
yeah tried that too no luck
[SuperSU] dimebagdan65:
Dang, worst case scenario, try emailing the developer of the app in question. They may not be aware of SuperSU yet
[SuperSU] theone10:
Mine works fine
[SuperSU] dimebagdan65:
le sigh...

Will Root Explorer never die and go away...?

FAR superior alternatives:

ES File Explorer (Free)

Script Manager (Free and paid version, cheaper than Root Explorer)

I could go on, but I know it won't do any good. I just wish all those folks that are just needlessly throwing away money would shoot some my way... Somebody, PLEASE, convince me, educate me, prove me wrong, I'm begging you! What advantages (If any) does Root Explorer have over either of the two alternatives I listed? >.< smh...
[SuperSU] PMGRANDS:
I'd also like to know... Lol!
[SuperSU] Fallen Spartan:
Tbh, I've always used root explorer, and if you use something which isn't broke, no need to change. I'll try ES File Explorer and Script Manager for comparison
[SuperSU] bsoplinger:
Try using either of those to change owner and permissions on a file or ten.

Sent from my PG41200 using Xparent Purple Tapatalk
[SuperSU] DarkhShadow:
FX with root module

Sent from my ice cream powered Nexus S
[SuperSU] dimebagdan65:
ES File Explorer or recovery can handle that with ease, but good point! Anytime I need to fix permissions I just boot to recovery, wipe cache and dalvik, fix permissions, wipe c/d again, reboot, profit. Almost forgotten what a force close its nowadays lol
[SuperSU] vlt96:
I use xplore... it has all the features and also you can open zips without unpacking ;)
[SuperSU] mike1986.:
Works great, as expected! :)
[SuperSU] vlt96:
OMG I looked at your thanks count :eek::eek::eek::eek::eek::eek::eek::eek::eek::eek::eek::eek::eek::eek::eek::eek::eek::eek::eek::eek::eek::eek::eek::eek::eek::eek::eek::eek::eek::eek::eek::eek::eek::eek::eek::eek:

I thought chainfire was amazing!!!
[SuperSU] mike1986.:
Believe me, I'm nobody compared to chainfire ;)
[SuperSU] vlt96:
You have a lot of phones ;)
[SuperSU] mike1986.:
Those are links to the ROMs threads, I don't have all those phones, but most :p ok let's get back to the main topic ;)
[SuperSU] Fallen Spartan:
I know (jk) :p:D;)
[SuperSU] jazzruby:
:good:
[SuperSU] Frank Westlake:
I think another useful test would be to write a file in '/system/bin' and see if it survives reboot:

su

mount -o remount,rw /system

echo "It's OK to delete this test file" >'/system/bin/testfile'

mount -o remount,ro /system

A copy and paste of that will work well if 'su' has already been run in the terminal and then the next three lines are pasted into that.

This test intended to see if the provider for this device has implemented some level of self-repair; it might be, each boot, completely restoring all executables or removing unknown files from executable directories.

Frank
[SuperSU] jazzruby:
[MENTION=5066176]jeppuda[/MENTION]

It appears all su required files are in the right places and indeed the su binary and Superuser app (judging by size) are pretty old.

Just to be clear; do you (not) get a root shell at su prompt?

Open/run Terminal Emulator:

$ su

#

Download the latest SuperSU zip pkg:

http://download.chainfire.eu/supersu

or

http://download.chainfire.eu/396/SuperSU/UPDATE-SuperSU-v1.94.zip

flash from recovery and boot up the device.

Open/run Terminal Emulator:

su -v

should return

1.93: SUPERSU

-JR-
[SuperSU] vanessaem:
Hello everyone,

Just a general reminder to all, please show some consideration to other users and make use of the hide tags conveniently located in your post text editor if you want to post a lot of text or for some reason want to quote the OP. It's also ok to link your large amount of text using external sources.

Thanks for your cooperation.
[SuperSU] kermage:
:good:
[SuperSU] Shinkoku:
Couple of easy questions:

1 SuperSu was a system app after rooting, but after upgrading to 1.94 version, I cannot convert SuperSu to system app through the app itself anymore. Choose "install into system", reboot and repeat it few times - nothing! What could be the reason?

2 Is there a step-by-step guide on how would it be possible to make SuperSu a system app manually?

Thanks!
[SuperSU] Pons:
1)Does flashing the update supersu zip (linked in OP) not work for you?

2)open the update-binary of that zip, and do what it does.
[SuperSU] TDSJR:
Try this: https://play.google.com/store/apps/details?id=de.j4velin.systemappmover

Sent from my ARTistically, Mahdified (Beta 4 v6) LG-D801, courtesy of dr87
[SuperSU] bovirus:
Shinkoku

Use SupeSU version for recovery in first post....
[SuperSU] jeppuda:
Sorry for the late response. Been a little busy lately. I used a fitting version of philz and flashed supersu version 1.65. Everything works fine. When I flash 1.94 in recovery, I get the message about binary needing to be updated on every reboot. I think I'm just going to stay with 1.65. Thank you for your help
[SuperSU] Pons:
That's ill-advised due to [SECURITY] Multiple Android Superuser vulnerabilities which exists prior to v1.69. It's generally always better to fix a problem upstream, than to rely on older/outdated versions.
[SuperSU] NZgeek:
I know that PhilZ recovery often includes a copy of SuperSU, and this can be used to fix root if it's not working. If you're not running a recent version of the recovery, you might find that your root is being automatically "fixed" for you, and this is causing your problem.

There are 2 things you can try:

1) Get the latest version of PhilZ for your device. This should include SuperSU 1.94 for you. Current build can be found at: http://goo.im/devs/philz_touch/CWM_Advanced_Edition

2) Reboot into recovery and see if there's an option for automatically fixing root. If there is, turn it off.

Hopefully one of these solves your problem.
[SuperSU] pappschlumpf:
Respect CM root settings not showing up on AICP/AOKP

Hi [MENTION=631273]Chainfire[/MENTION],

is this option still available in 1.94 and if it is, why it's not shown on AICP/AOKP ROM? I've installed SuperSU instead of the included Superuser. If a new app needs SU many other apps fc, could that happen because of this settings isn't show and set the wrong way?
[SuperSU] Pons:
I'm not seeing it currently, but I'm not on CM for the moment. I swear I remember seeing it for CM, though. But neither of us is on it, which is probably the reason.

As for FCs, I'd verify Superuser is uninstalled, then reboot. That way SuperSU takes priority. You could also take the cheap way out, and try running a root checker to see what's not right. A logcat would also help.
[SuperSU] pappschlumpf:
Thx for the answer, but how do you uninstalled superuser, that is integrated in cm/aokp/aicp settings? What ROM are you on?

Don't missunderstand me, super su is working an granting root access, but if a new app needs su access a bunch of apps fc's. Things like google play service, calendar provider, etc. Sometimes Supersu itself.
[SuperSU] DroidGnome:
:good:

That option in Philz seems to be labeled "Verify Root on Exit"..

This fixed my issue as well. Seems I had an older version of Philz and never knew about that setting.. so when I updated SU from Google Play, Philz kept trying to update with an older version causing an compatibility problem.
[SuperSU] jeppuda:
Same here. Thanks for the help guys
[SuperSU] 777.300:
Flashed the latest ParanoidAndroid beta 3 and still missing the SuperSU icon in the app drawer after SuperSU zip flash.

Is there a way to get the app icon back.

Can acces SuperSU on my N4 by code *"*"1234"*"* but on my N7 I cannot access SuperSU at all.

It is working normally on the N7 but I cannot change the settings.

Hope to find a solution in the near future. (same question asked in the ParanoidAndroid thread)

Verstuurd vanaf mijn Nexus 7 met Tapatalk
[SuperSU] jazzruby:
Try launching the app from terminal with Activity Manager

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

-JR-

Sent from my Nexus 7
[SuperSU] Skaldinho:
This morning i got message about granting SuperSu[UID] root access. Should i be concerned? Never had this before nor google seem to find anything about it.
[SuperSU] 777.300:
Thanks for this great advice.

Terminal command working fine.

Finally I can acces SuperSU on my Nexus 7.

Great.

Verstuurd vanaf mijn Nexus 7 met Tapatalk
[SuperSU] pappschlumpf:
Could that be a problem?

type=1400 audit(1399471588.106:225): avc: denied { read } for pid=13539 comm="su" name="urandom" dev=tmpfs ino=661 scontext=u:r:untrusted_app:s0 tcontext=u:object_r:device:s0 tclass=chr_file

<5>[ 238.764267] c2 type=1400 audit(1399471588.106:226): avc: denied { open } for pid=13539 comm="su" name="urandom" dev=tmpfs ino=661 scontext=u:r:untrusted_app:s0 tcontext=u:object_r:device:s0 tclass=chr_file

<5>[ 238.764719] c2 type=1400 audit(1399471588.106:227): avc: denied { read } for pid=13539 comm="su" name="/" dev=selinuxfs ino=1 scontext=u:r:untrusted_app:s0 tcontext=u:object_r:selinuxfs:s0 tclass=dir

<5>[ 238.764859] c2 type=1400 audit(1399471588.106:228): avc: denied { search } for pid=13539 comm="su" name="/" dev=selinuxfs ino=1 scontext=u:r:untrusted_app:s0 tcontext=u:object_r:selinuxfs:s0 tclass=dir

<5>[ 238.765044] c2 type=1400 audit(1399471588.111:229): avc: denied { read } for pid=13539 comm="su" name="enforce" dev=selinuxfs ino=4 scontext=u:r:untrusted_app:s0 tcontext=u:object_r:selinuxfs:s0 tclass=file

<5>[ 238.765143] c2 type=1400 audit(1399471588.111:230): avc: denied { open } for pid=13539 comm="su" name="enforce" dev=selinuxfs ino=4 scontext=u:r:untrusted_app:s0 tcontext=u:object_r:selinuxfs:s0 tclass=file

<5>[ 238.765248] c2 type=1400 audit(1399471588.111:231): avc: denied { getattr } for pid=13539 comm="su" path="/sys/fs/selinux/enforce" dev=selinuxfs ino=4 scontext=u:r:untrusted_app:s0 tcontext=u:object_r:selinuxfs:s0 tclass=file
[SuperSU] johny.mnemonic:
Loosing root with SElinux

We are having weird issue on S4 Mini Duos (GT-I9192) where we are loosing root after using Wanam exposed app.

I just ran into the same issue while manually triggering setenforce 0 from terminal.

Terminal app still has root and I can see /system/xbin/su is still there, but other apps report no root and SuperSU reports SU binary missing. I am really confused.

I am afraid it's somehow connected to either Knox or SElinux.

I tried to stay as close to stock as possible, so I have CWM recovery and root with Stock ROM and stock Kernel. Which means Android 4.2.2 with SElinux in enforcing mode.

My report in Wanam thread:

http://xdaforums.com/showpost.php?p=52346529&postcount=3680

Edit: I tried to execute setenforce 1 to return to enforcing SELinux mode and root is back. So it is definitely SElinux issue.
[SuperSU] dirtyreturn:
Hi. Anyone here use Orbot and also having some trouble? An sh .. out error. I am no dev so sorry for lack of description.

Edit - it happens more often than not. I'm using the latest Orbot version from the playstore and SU v.1.93 on 05/07 cm11 gsm nexus.
[SuperSU] darkghost568:
I use orbot paired with orweb often and no errors here. SuperSU 1.94 and Nexus 5 Stock rooted.
[SuperSU] rasengan82:
What are the main difference between SuperSU and Clockworkmod Superuser? I've been googling but cannot find any good explanations. Thanks!