yashsingh1/xdaforums huggingface dataset:
[SuperSU] Bexton:
Just fyi: Not yet merged, but the kernel and init domains will most likely be switched from unconfined_domain() to permissive_or_unconfined() soon: https://android-review.googlesource.com/#/c/112060/

Edit: Oh, and another change, that might be interesting especially for SuperSU?! But you should better read the long commit message yourself: This change defines a new sandbox_app domain: https://android-review.googlesource.com/#/c/111744/

Edit2: And onee more related change which should be relevant to SuperSU as well: This change (already merged) fixed the (accidendatl) exclusion of symlinks being writable for recovery: https://android-review.googlesource.com/#/c/111865/
[SuperSU] Pkt_Lnt:
http://xdaforums.com/showpost.php?p=56271009&postcount=7081
[SuperSU] rhodyvik:
SU Binary

Hey guys...hoping someone can help me out. After updating the SuperSu Pro app today, the app now says "The SU binary needs to be updated."

Edit: I figured it out. Sorry.
[SuperSU] Cyrus_94:
2.16 not working for my lenovo a850+ there is no su binary installed.
[SuperSU] :
Flash the zip in CWM/TWRP
[SuperSU] xda___:
can't update?

hi, have an htc v1

jb 4.

cwmr

su binary needs update, but i can't seem to do it.

it won't do it automatically, and if i go into recovery to maunally install .zip update, nothing happens?
[SuperSU] cbendan:
I have the same problem/issue but with a Oneplus One. My wife's one can update supersu via Playstore and the version showed there is good (2.16), but the version showed in playstore with my Opo is 2.01, with the version update date 25/10/2014.

If I reinstall again with the .apk, the result is the same.

I installed SuperSU via TWRP in both 1+1.
[SuperSU] kmcphee:
If you are coming from 2.15 it uses same binary you wont see it
[SuperSU] KrewsialNL:
Here's what I did and for the life of me, I can't get it to work.

1. Flashed Lollipop Preview via fastboot

2. Flashed Chainfire's kernel

I don't have recovery anymore and I cannot install it either because it says "FAILED: Image is not a boot image"

What am I doing wrong? :S
[SuperSU] magnamentis:
easy (smile)

probably you have just a black out, this is a zip file which is meant to be flashed from recovery and not and .img which has to be flashed through fastboot and/or flashify and the likes. so boot into recovery and flash away like you would do with any rom, kernel and other flashable zip.
[SuperSU] KrewsialNL:
Sh*t. Better start over again then :')

Thanks!
[SuperSU] hard91:
Plz tell me equivalent command for

ch_con /system/xbin/daemonsu

In adb

And also

set_perm 0 0 0777 /system/bin/.ext

In adb
[SuperSU] egingell:
I don't know what "ch_con" is but "set_perm" in that context =

chmod 0777 /system/bin/.ext
chown 0:0 /system/bin/.ext

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] hard91:
set_perm() { chown $1.$2 $4 chown $1:$2 $4 chmod $3 $4 } ch_con() { /system/bin/toolbox chcon u:object_r:system_file:s0 $1 chcon u:object_r:system_file:s0 $1 } ch_con_ext() { /system/bin/toolbox chcon $2 $1 chcon $2 $1 }

set_perm 0 0 0644 /system/app/GMS_Maps.apk

set_perm 0 0 0644 /system/app/YouTube.apk ch_con /system/bin/.ext/.su

ch_con /system/xbin/su

---------- Post added at 12:29 AM ---------- Previous post was at 12:26 AM ----------

Can you now help me.....

How to send these by adb

Thanks 4 your rply
[SuperSU] egingell:
Shell functions just make a command (essentially). Just take the contents of the function (between the braces), replace $1 with the first argument, $2 with the second, etc., and execute them.

E.g.

do_echo() {
echo "$1, $2.";
}

do_echo Hello world;

Becomes:

echo "Hello, world.";

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] hard91:
Thank you sir can you just make one example of

ch_con /system/etc/install-recovery.sh
[SuperSU] egingell:
No. Because then I'd be making "examples" of every line. We try to feed ourselves here.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] hard91:
Actually i am noob in andriod

O just making a .bat file to root moto e so thats why i am asking you only one instruction will let me work on 20 lines of code

Thank you for your cooperation....

---------- Post added at 01:09 AM ---------- Previous post was at 01:07 AM ----------

What i am doing is converting an update-binary of supersu to .bat file so we do't need it to flash
[SuperSU] Conan179:
Hello@all

I have a little problem with Supersu Pro. When I run it on my N910F, supersu KNOX want to remove. Wen I let it run, it runs forever and never stops. Wen I then, after a restart. Want Supersu KNOX remove again.
[SuperSU] egingell:
I've given you everything you need to do it - replace $n with its corresponding argument after copying the function body.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] Viper_21:
The other day, I flashed UPDATE-SuperSU-v2.16.zip over SuperSU 2.01 via Philz recovery on my Samsung Galaxy S3 (stock ROM 4.3 with Boeffla kernel). It totally screwed up my phone (most apps, but not all, fail to ask for root, some get root some don't even when they request it, and phone eventually reboots or dies after a few minutes). I didn't do a Nandroid or Titanium before that so I am in bad shape here (normally I do, but it worked no problems on my wife's phone before so I figured no risk on my phone).

I then uninstalled root via the SuperSU app, reflashed CF-Auto-Root-m0-m0xx-gti9300.tar.md5 (via ODIN), and then UPDATE-SuperSU-v2.01.zip (via Philz recovery) -- but same issues as before.

Currently I have uninstalled the root and SuperSU app (I did this via the SuperSU app) and now the phone functions fine (but without root-based apps and functionality).

I figured the best thing is to do now is a full wipe, and reinstall everything from scratch (recovery, kernel, SuperSU, Xposed, apps etc.). Problem is I can't do a new Titanium backup 'coz I don't have root. :( By the way, I do have an older ~2-3 month old Nandroid and Titanium backup on my PC.

My questions -- and crossing my fingers here for some helpful get-me-out-of-jail tips (I am dreading having to reinstall everything from scratch):

1. Before I do so, any creative ideas how I can get a re-working root and SuperSU on to my current setup and to get out of this terrible mess? I read something about restoring old Nandroid just system partition - could that help?

2. And a general question... let's say I go the route of a full wipe and reinstallation of a fresh Sammy 4.3 ROM, do I have to the flash "CF-Auto-Root-m0-m0xx-gti9300.tar.md5" first and then the "UPDATE-SuperSU-v2.01.zip", or can I flash the "UPDATE-SuperSU-v2.01.zip" directly without first flashing the CF-Auto-Root?

Thanks!!
[SuperSU] hard91:
Correct me if i am wrong

Adb /system/toolbox chcon u:object_r:system_file:so <name of apk or file>

---------- Post added at 01:39 AM ---------- Previous post was at 01:36 AM ----------

File name of apk and file will be

/system/etc/install-recovery.sh
[SuperSU] egingell:
Yup.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] hard91:
Thank you so much for your help

At last a quick question can i give command to cwm or twrp while installing/flashing (twrp/cwm) to install a specific zip on reboot into recovery

Acco to me it will not work because setting recovery inn command mode in cache/recovery/command

Before installing will not work
[SuperSU] jazzruby:
'chcon' - change security context - used/applied in SELinux

Have a look HERE

and

Wikipedia HERE

HTH,

-JR-
[SuperSU] Chainfire:
If you can get back to v2.16 and the bad behavior, make a logcat of the failing system... that might give a clue what is actually going on. Might even be fixable without starting from scratch!
[SuperSU] sjmiller:
Disregard, sorry.
[SuperSU] Viper_21:
Will do in the next couple of days. Need to figure out how to get a logcat via adb. I've done some reading, but it's news territory for me. Thanks for giving a ray of hope.
[SuperSU] Bright09:
Having trouble with root due to binary is not updating on my i535 stock anyone can help?
[SuperSU] Methisfaction:
So, i got it working with the instructions some sites before...(but dont push remoteplay apk to system app)

The problem was Supersu with root.

I unrooted via Supersu's In app Settings...

but before that, (like said above) delete remote play Apk from System/apps/...and then unroot.

after that, open PS App and klick remoteplay, and download via Playstore. This worked for me..but controller support isnt there....

btw, change quality to high in remote play, so you got 720p resolution

So it works on Oneplus One!
[SuperSU] Cyrus_94:
I always install through CWM and clear cache everytime.
[SuperSU] simonbigwave:
jus wanna report installed SuperSuPro v2.16 on CM11 1027 Nightly on GT-I9505 all OK, no problems at all.
[SuperSU] Celestial Fury:
With SuperSU 2.16, com.anchorfree.service no longer shows or requests root. hotspotshield.android.vpn requests root and root permission sticks but toast keeps appearing after every reboot even after several reboots over several days. Also, another app that updated also has recurring toasts.

Time in SuperSU log is fixed though. :good:
[SuperSU] Viper_21:
Can someone please answer my earlier question about rooting from a fresh wipe and installation? Many thanks.
[SuperSU] SignetSphere:
You need to root it first via cf-autoroot on download mode. That update zip is just for well... you know "updates".
[SuperSU] avicohh:
Hi [MENTION=631273]Chainfire[/MENTION]

I'm trying to make a prerooted firmware for Samsung device (run on 4.4.2 android version, and armeabi-v7a cpu), which he doesn't have a root method yet. (I tried all the known methods)

I have able to repack the firmware using ext4_utils and your fix, and flash it via Odin.

What I need now is the proper SU binaries and their permissions.

e.x

system/app/superuser.apk, 644

system/xbin/su, 755

system/etc/ install-recovery.sh, 755

and etc.

I have tried the files from the SuperSU zip installer (the latest one 2.16), but with no success.

When i enter "su" command it just add "1" before my name.

for example:

u0_a103@hammerhead:/ $ su
[B]1[/B]u0_a103 @hammerhead:/ $

I'm very appreciate your help.

Have a nice day.
[SuperSU] Chainfire:
The ZIP describes in detail what needs to be installed where.

Make sure that when the device is booted up the file permissions are as they should be. Often this step goes wrong with prerooting /system. Especially /system/etc/install-recovery.sh often loses its executable bit.
[SuperSU] avicohh:
Thanks.

I will check it, and update here.

What about the ch_con? It's required?
[SuperSU] kewinhdorff:
random reboots

hey i just installed root on my samsung galaxy s4 i9505. with the firmware XXUGNF6. and i am having some problems. i am getting random reboots and if i am using touchwiz when i unlock my phone i can't scroll through the homescreen and i cant even open apps from and i can not enter app drawer. Sometimes it goes into safe mode. is there any way to fix it ? please thanks
[SuperSU] Strephon Alkhalikoi:
2.16 worked perfectly on my Galaxy S4 (GT-I9505) running EchoeROM 35.1.

I may break out my obsolete Gingerbread devices and try it on them to see if they work, and if I do, I'll let the world know. ;)
[SuperSU] grgsujan:
Idk if this has been asked previously or not, but How to fix the miscelleaneous battery drain? Build 16s .
[SuperSU] CamoGeko:
Yeah maybe my eyes are just swimming in XDA and everything is just blending into one.

How's you btw mate? See you've stuck with Samsung. :D

Sent from my N⁴ running Android L
[SuperSU] magik_zeppelin:
Help with finding SuperSU file

Hey guys, I have SuperSU 2.01 downloaded from playstore, and I'm trying to find the file location using ES file explorer, but it's nowhere to be found. I tried searching and looking the hard way and I can't seem to find it. I am trying to move it to my external sd card in order to flash Hyperdrive on my S4. Can anyone point me in the right direction ?
[SuperSU] egingell:
What are you looking for?

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] magik_zeppelin:
Where the SuperSU file is saved on my device.
[SuperSU] zadigre:
Why not just reinstall it from the play store or download it from chainfire website?

Envoyé de mon SM-N900W8 en utilisant Tapatalk
[SuperSU] magik_zeppelin:
I did reinstall it from the playstore. I will download from chainfire now, just found it curious I couldn't find it in the files.
[SuperSU] egingell:
The app of the binary? The app is just an app it's in applications where the rest of them are. The binary is in /system/xbin.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] magik_zeppelin:
But it's not in applications. When I try to search for it in ES file explorer, neither SuperSU nor eu.chainfire return any results. It's not in system/apps or system/data...
[SuperSU] dhatch93:
did you search from the root of your sd card? in Root Explorer i just browsed to /data/data and it is there... :confused:
[SuperSU] egingell:
If you installed it from the Play Store, it's in /data/app, but it *is* an application. If you're looking for the Play Store download for whatever reason, it's in /data/data/com.android.downloads/cache.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] magik_zeppelin:
Thanks, I found it after reinstalling. Do I need to make a copy of it on my internal or external SD card before flashing a ROM? The guide I'm following says to, but I can't understand why it would matter?
[SuperSU] egingell:
What are you flashing? You can't flash the Play Store download. And you install either from the Play Store (and update the binary) or flash it via recovery - you don't need to do both.

Edit: Sorry, I misunderstood. Put is anywhere that won't get deleted, but why are you bothering? If the ROM is already rooted, you can uninstall its SuperSU using a system app remover and install via the Play Store or flash the zip from the OP via recovery.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] magik_zeppelin:
I'm sorry if I'm not explaining correctly, I've rooted plenty of phones but never messed with ROMs until now and there is not a single "one size fits all" type guide on how to do it, so I'm just putting bits together from different places as I go. This is what I'm trying to do and the guy in the video makes a specific point of making sure SuperSU is located in a specific place.. When I tried to move it just now, SuperSU crashed and wouldn't open so I had to reinstall again. It works now, but I'm not sure where/how to move it like the guy in the video says to.
[SuperSU] egingell:
Removing any app's apk still cause that app to crash. Just copy it instead.

Like I said, somewhere it won't get deleted, but if the tutorial involves a pre-fab script, you will definitely need it to be in the correct location.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] magik_zeppelin:
Cool, thanks for your help mate.
[SuperSU] toyongbanatero:
Problem with latest

I have installed the latest 2.16 but it still forgets the granted apps when I reboot. any ideas? it's quite annoying to grant each time especially when i'm not holding my phone when i reboot, then afterwards, all of my root apps that run after boot are silently denied the time i pick up my phone.

any help will help (wait, what?)

thank you.
[SuperSU] lindsay_jude:
binary won't update

Is anyone else having problems getting the system to update? I have SuperSU Pro on my Droid Maxx

I've tried a few methods I saw online with no luck. Any help?
[SuperSU] asibmkhan:
well thanks and i upgraded to the lastest version a long time ago it works well! :D :D
[SuperSU] DarkAngel:
@Chainfire

Just wanted to let you know of an issue I keep having. The same happens on two Roms with my Note 2 being on NE2 KitKat ( Sprint ).Let me know if you need anything other than the Logcat...

Two Main logs I keep getting over and over:

I/SELinux ( ****): Function: selinux_android_load_priority [0], [B]There is no sepolicy file[/B].
I/SELinux ( ****):
I/SELinux ( ****): Function: selinux_android_load_priority [1], [B]There is no sepolicy version file[/B].

( While on v2.01 all is good.)

I have tried many ways, normal install, uninstall before updating and flashing via recovery. All end the same way until I reboot my phone. All works well when updated until I reboot, then the app just hangs on start up and I can not access any settings within.

Oh, I forgot to add that those two files are in place. Also SE for Android status is set to Enforcing.

Just trying to rule everything out but the version of busybox would not have an impact with my current problem correct? I have 1.22.1 installed.
[SuperSU] CyberpodS2:
I would like to suggest that people with issues use DarkAngel's post above me as a model when giving feedback or reporting problems. He lists the device, the environment, the specific behavior and a logcat to give the Dev a place to start... While I'm no programmer, I use process troubleshooting every day and can appreciate someone being prepared when they ask for help! :)
[SuperSU] Long Island NOOBIE:
Functions flawlessly on my devices. Thank you sir!
[SuperSU] magik_zeppelin:
Back again..

Ok guys, so I moved Safestrap to my external sdcard via the instructions for the ROM I am attempting to install. Now, when I click on the Safestrap app it asks for SuperSU permissions and immediately crashes. I think I know what I did wrong, I should have copied to my external sd card and not moved.. That being said, if I uninstall Safestrap completely and reinstall it will the backup I created still be usable?

Edit: I'm a noob, forgot to set permissive mode. All good now.
[SuperSU] inphamous36:
Kind of unique problem I'm having after upgrading to 2.16. I cannot grant any apps root access. It actually won't let me click on anything. If I press the home button while it's up it denys it, then I can go into the logs and choose to grant root, but it never actually let's it have root access. I'm using it on the new note 4. I've tried everything you could probably try but still no luck. If you want more details let me know. But for now I'm staying on 2.14. Just refreshed my rom and denied supersu to update. I'm not sure how I could get a logcat but I'll be happy to get one if you could show me exactly when to get it that would benefit you.
[SuperSU] mcnaught82:
No problems here...go into the app and do full unroot and flash it again
[SuperSU] egingell:
Your problem is not unique. Please check the last few pages.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] Chainfire:
Very interesting.

The same happens on two Roms with my Note 2 being on NE2 KitKat

That's a little unclear, you have tried multiple ROMs on this Note2 (if so, which ones), or is there a second device, or ...?

What do you mean "all works well when updated until I reboot" - do you mean after first update from 2.01 to 2.16 ? Or can you fix it every reboot ?

A full boot up logcat could be useful. A logcat from SuperSU being started up and hanging is also useful.

Also, please pull /sepolicy_version, as well as the entire /data/security folder from the device.

Does this affect root apps, or do they mostly just work regardless?

Additionally, the "I/SELinux(12345)" thing notes a process pid. Which process is responsible? "adb shell su -c ps | grep 12345" (where 12345 is replaced with the number in the log.

EDIT ----

I've been able to confirm something similar on my S5 Prime. I have those logcat messages regardless of SuperSU being installed or which version, every time an app is loaded. If you could confirm you still get these message in your logcat regardless of SuperSU version, that would be great.

This leads me to believe for now that the app hang is unrelated to these SELinux messages.
[SuperSU] DarkAngel:
Very interesting.

The same happens on two Roms with my Note 2 being on NE2 KitKat

That's a little unclear, you have tried multiple ROMs on this Note2 (if so, which ones), or is there a second device, or ...?

Yes I am sorry I was not clear. I have only one Note 2. I have tried two Roms that I go back and forth with, Rwilco12's Mostly Stock & Community Rom.

What do you mean "all works well when updated until I reboot" - do you mean after first update from 2.01 to 2.16 ? Or can you fix it every reboot ?

Yes, while on 2.01, I update to 2.16 and update the binaries normally with no reboot. Everything worked perfect, apps requesting root obtained root access and worked great, no problems what so ever. The problems begin once I reboot the phone.

A full boot up logcat could be useful. A logcat from SuperSU being started up and hanging is also useful.

Also, please pull /sepolicy_version, as well as the entire /data/security folder from the device.

Will do

Does this affect root apps, or do they mostly just work regardless?

Once rebooted I can, for example, access the busybox app but not Titanium Backup. If I click on the SuperSU app it will hang without opening. After clicking on SuperSU, I can not access say the busybox app.

Additionally, the "I/SELinux(12345)" thing notes a process pid. Which process is responsible? "adb shell su -c ps | grep 12345" (where 12345 is replaced with the number in the log.

I will look into which process.

EDIT ----

I've been able to confirm something similar on my S5 Prime. I have those logcat messages regardless of SuperSU being installed or which version, every time an app is loaded. If you could confirm you still get these message in your logcat regardless of SuperSU version, that would be great.

I will report back to you asap.

This leads me to believe for now that the app hang is unrelated to these SELinux messages.
[SuperSU] Scipizoa:
[STABLE][2014.10.25] SuperSU v2.16

Not to interupt can any recommend some logcat related apps?
[SuperSU] CyberpodS2:
https://play.google.com/store/apps/details?id=com.nolanlawson.logcat
[SuperSU] Scipizoa:
Thanks
[SuperSU] kmcphee:
Try clearing cache and dalvik cache through recovery. Please mzke sure you have a good backup. Also I am not responsible for anything that could happen yo your phone
[SuperSU] inphamous36:
Yes. I've tried everything I can think of.

---------- Post added at 12:06 PM ---------- Previous post was at 12:05 PM ----------

I hadn't looked that far back. I had been trying to fix that problem for about 3 hours when I posted that.
[SuperSU] Chainfire:
v2.17 beta is available, release notes
[SuperSU] atomomega:
On latest v2.16 I'm facing the same problem with SetCPU too. Even when toast notifications are disabled globally.
[SuperSU] DarkAngel:
@Chainfire

I PM'd you a link for a zip file with all requested and additional logs. Oh and to confirm on the logcat I still get the messages regardless. I restored my saved system partition from before the update ( while on v2.01 ) and all is working great of course.

If you would like for me to post the files/logs here, please let me know.
[SuperSU] samuelfai:
get some problem

when the screen prompt the deny or grant option, supersu is not response, either dent or grant.
[SuperSU] Darke5tShad0w:
Congratulations on not reading before posting, the answer is on the previous page that will tell you posts to read and prob every page for the last few weeks.
[SuperSU] Dr Goodvibes:
Toast notifications with SetCPU

Having SetCPU application toast notifications (even when notifications are turned off) pop up every now and then seems to happen on all the devices on which I'm using SetCPU.

Xperia S v4.1.2

Xperia M v4.3

Minix X7 TV box v4.2.2

With SuperSU v2.16 Chainfire has 'fixed' the actual permission request [Grant/Deny] issue on physical phone power-up we saw on v2.14

Hopefully Chainfire has a change to look at this during a 'quiet moment' and see if anything can be done.

Seems the 'issue' can be easily and quickly duplicated(fingers crossed) as I get a toast notification mostly within the first session of use in less than 5mins.

On all systems, I have at least one 'power' profile in SetCPU for when the screen is off, which uses powersave gov and low CPU freq.

Thank you Chainfire.

Update

Did try v2.17 Beta, but still getting SetCPU toast notifications.
[SuperSU] HarisA1:
Has anyone tried dirty flashing the nexus 6 version over the preview version? Just wondering if it would cause issues