yashsingh1/xdaforums huggingface dataset:
[SuperSU] vashta:
I have xperia arc.

I've recently instal cusrom of 4.3 based rom.

How can I properly install the SuperSU in that rom?

This is what i got, after installing it. Never had this kinda issue when i was in ICS.

SuperSU
-------------------------------------
There is no SU binary installed, and SuperSU cannot install it.
This is a problem!

If you just upgraded to Android 4.3, you need to manually re-root - consult the relevant forums for your device

I've ask in the roms thread also, but haven't got reply.

So i ask here, maybe someone know the solution.
[SuperSU] jmjb:
SuperSU v1.65 does not update the binaries in normal mode and therefore I can not access the settings of the program, but the program works.

I have one note 3 (9005) and I can not try to update the binary for recovery without raising the knox to 0 * 1.

Sorry for my bad English
[SuperSU] Goddly:
having root issues on 4.3, mod pack erases init.d (to help with conflicting scripts etc.) which loses root. which file from the UPDATE- SuperSU.zip am i supposed to put back? any help would be much appreciated. Thanx.
[SuperSU] jazzruby:
In 4.3 we run su as a daemon, and the SuperSU zip has 2 files available to start the process:

/system/etc/init.d/99SuperSUDaemon - this if init.d available

or

/system/etc/install-recovery.sh

Both files contain the following code:

#!/system/bin/sh
/system/xbin/daemonsu --auto-daemon &

-JR-
[SuperSU] Goddly:
the recovery.sh adds init.d support to a non supported Kernels, the 99 su init.d script gets wiped via the updater script, after the init.d wipe, i push the init.d script back and set perms to 0755.. but some people still lose root? is it because the system is not "writable"

Sent from my ASUS Transformer Pad TF300T using Xparent Red Tapatalk 2
[SuperSU] volkmadi:
Hi,

a quick question.

I installed I9505XXUEMJ5 and rooted with CF-Auto-Root-jflte-jfltexx-gti9505.

All fine all good, I'm root, all works, just one small issue:

I can't find SuperSU in the apps drawer and when I open the store and search it it says in it's entry just uninstall, I miss the open button.

Any idea?!

Thx

Dirk

... found the reason already ... thx anyway!
[SuperSU] alanbr:
Cannot Update SU binary

I don't know if this has been asked before. I have a Galaxy Note 3 SM-N9005 with fully stock (Android 4.3) and have rooted via vroot. However, vroot installs its own version of Superuser, and parts of it are in Chinese. I have read that it is possible to replace it with SuperSU by installing SuperSU, then using Titanium Backup to freeze the Chinese Superuser. However, after installing SuperSU the first time I run it I get a message saying "The SU binary needs to be updated. Continue?". When I click "Continue", I get two options: Normal or TWRP/CWM. Because I have the stock Recovery, I choose Normal. And then after a few seconds, I get an "Installation failed!" message, telling me to reboot and try again. However, this happens after the reboot, endlessly. I have also tried this process after freezing the Chinese Superuser with Titanium Backup, but the results are the same. Is there anything that I can do to solve this problem?

Thanks for any help!

Alan
[SuperSU] SecUpwN:
Yes it has been. Use the search.
[SuperSU] sorg:
It seams i've found the bug.

if you are in non-root shell then following command will succeed:

su -c "mount -o remount,rw /"

But if you are already in root shell, then command above won't work.

Don't ask me why i have to use su in root shell. Sometimes, for unified scripts i have to do this.

With old version of SuperSU (without daemon) command works well in root shell.

Unfortunately, after migrating to Android 4.3, i cannot use non-daemone version anymore and this bug breaks all my scripts :(
[SuperSU] defim:
For me too, since I update from 4.1 to 4.3. Btw, can I get that twr package somewhere? So I could install it after flashing new image and without superuser trouble
[SuperSU] riahc3:
I just installed a 4.2.2 ROM and installed SuperSU and lost root.

This seems to be a major bug with SuperSU and its a shame as it was working great.
[SuperSU] shaggyskunk:
I just flashed 4.4 on my Nexus 7 & Flashed Chainfire's SuperSU 1.6 5 - And it works PERFECTLY.
[SuperSU] Pkt_Lnt:
Four different 4.2.2 ROMs on my S4 Active with SuperSU and no issues at all. You have a problem somewhere, not SuperSU.
[SuperSU] Chainfire:
Interestingly, I can't seem to replicate this issue. The command should be "mount -o remount,rw / /" (two slashes witha space in between) for compatibility reasons though.
[SuperSU] sorg:
actually, it's a part of windows batch file. Full command looks like this:

adb shell su -c "mount -o remount,rw /"

Second slash is not required. It worked correct with non-daemon su on android 4.1-4.2.2

With daemon su, it executes without error, but / (root dir) doesn't remount with rw flags. It looks like command mount -o remount,rw / just ignored.

adbd runs with root rights originally. Even in adb shell prompt manually invoked su -c "mount -o remount,rw /" does nothing.

But if i execute su system to switch to non-root user then original command works well.

So, it looks like new su ignores command if rights aren't elevated. May be it thinks elevation has failed and drop the command?
[SuperSU] 78Staff:
Agreed, I've run multiple 4.2.x roms with SuperSU with no issues - Touchwiz, AOKP, AOSP, etc
[SuperSU] xd4d3v:
having issues with supersu and running app ops on 4.3 it just crashed. Superuser doesn't do this. Any idea? How can I contact chain fire to let him know?
[SuperSU] Chainfire:
As I said, compatibility reasons. There are versions of mount out there that do not work with the single slash. Then again, you obviously know better, so tata.

What are you even checking? If you do su -c "..." and then check mount *without* su -c, then rootfs will not be remounted. If you su first, then it will.
[SuperSU] sorg:
why i use this command is beyond this topic. It's not important here. The most important is that daemon su produces different result than non-daemon su.

Yes, you are right, if i invoke su -c "mount" then i see root dir remounted as rw.

So, eventually it works, but differently. daemonsu executes root command in separate process, while old su executed in the same process.

I've heard some apps have compatibility problems with daemonsu. May be this kind behaviour causes this.

Is there a way to use old kind of su if i have my own compiled kernel with all security off and custom ROM?
[SuperSU] Chainfire:
Yes. In daemon mode, su commands are not executed in the same branch of the process tree as the calling executable (shell, apps, etc). Root apps that have not been updated for 4.3 may have issues with this, yes. The changes made in 4.3 required this change in how su works, it's been talked about a lot already, not opening that discussion again.

If you're making your own firmware, setting SELinux to permissive AND restore the capabilities bounding set to 0xFFFFFFFF will allow su to operate in traditional mode.
[SuperSU] hycian:
Thanks so much, you rock!!! I am using Galaxy Nexus on Android 4.3 stock ROM and since after the JWR66Y ota last time, I had lost root.

I had tried numerous methods before and none had worked until I saw your advice. My phone is now properly rooted and I am a happy guy. :good:
[SuperSU] pbaden:
I'm facing the exact same issue. Every time i go into recovery it asks me if i want to fix root.

Were you able to solve it? I can't find the fix.

Verizon GS3

Dirty Unicorns ROM

10/17 build (mislabeled as 10/13)

JB 4.3.1

Kernel: 3.4.62_CM 10/17

Baseband: I535VRBMF1

Recovery: CWM 6.0.2.3
[SuperSU] ptmax13:
I didn't have that exact issue. I was losing root with every reboot and had to reflash. Try to flash ssu, then fix permissions then reboot.
[SuperSU] Chainfire:
You're using an outdated CWM. CWM is stupid like that.
[SuperSU] pbaden:
Thank you!
[SuperSU] nfribeiro:
I am using last Philz recovery based on CWM 6.0.4.4 and still I have this fix issue...
[SuperSU] shoey63:
Philz next release will have an option to remove the"nag"
[SuperSU] Chainfire:
The permission checking is plain wrong. On 4.3+, /system/xbin/su and the likes (except /system/xbin/daemonsu) should not have suid bits. Not sure why upstream CWM hasn't fixed this yet, but [MENTION=4666971]Phil3759[/MENTION] should check /system/build.prop for ro.build.version.sdk >= 18 , and then /system/xbin/su only needs 755, not 06755. In fact, 06755 would *break* root on some devices on API >= 18, but daemonsu automatically detects and fixes that before an app actually has the chance to request root. Obviously that only works on writable /system devices, so HTCs with S-ON may lose root because of this (daemonsu cannot auto-correct).

I mentioned outdated CWM because I was confusing it with a similar issue, which has already be solved.
[SuperSU] Chainfire:
Invoking [MENTION=4666971]Phil3759[/MENTION] again because I'm not sure edited mentions send out notifications to the mentioned user :) Check the post above this one.
[SuperSU] CoolApps:
Seems like so unfortunately...

Same for quotes as well.
[SuperSU] Phil3759:
Sorry, I disabled the poke notification

Here's where cwm messes up things:

https://github.com/CyanogenMod/android_bootable_recovery/blob/cm-10.2/extendedcommands.c#L1705

Permissions detection on su binary:

if ((st.st_mode & (S_ISUID | S_ISGID)) != (S_ISUID | S_ISGID)) {
..... prompts to fix root and apply chmod 6755
}

Koush recently revised it, but kept it broken it seems

Thank you for the explanations

Meanwhile, I disabled the check and made it optional in config files 2 days ago

I do not like to hard modify these as I never had time to look at new daemonsu
[SuperSU] awyeahh1:
hi guys, got a nexus 10 yesterday, it has android 4.3

did all the regular stuff = fastboot oem unlock + fastboot flash recovery recovery-clockwork-touch-6.0.1.6-manta-Wfix-by-damien667.img

then I mistakenly used the old CWM-SuperSU-v0.98 .. it didn't work because no binaries error. then i went back to recovery and flashed UPDATE-SuperSU-v1.65 ... but the same problem with binaries persists and I have no root.. see image below.. what can I do you guys, any idea :confused:

http://tinypic.com/r/2ziocra/5
[SuperSU] Phil3759:
I committed this:

https://github.com/PhilZ-cwm6/philz_touch_cwm6/commit/699bee74b028a390a47105e4d3dfb89e909dfc06

Basically, if ro.build.version.sdk value >= 18, it skips any check for su permissions. It will only run CWM /sbin/install-su.sh to copy su binary if it doesn't exist (all credits given)

I would be grateful (I know you are short of time...) if you can comment on this simple workaround

Also, if I use your su binary instead of Koush su in cwm, will it be fine out of the box or do I need to include extra scripts from your installer?

I ask this because Koush su cannot root new Samsung ROMs while yours can, so felt it is a good idea I include your smaller su rather than Koush one, if it is ok for you.

Many thanks
[SuperSU] MikeRL100:
Chainfire, I don't know if this is normal behavior, but if it is, perhaps it should be modified? On my Nexus 5 with KitKat, if I enter in a PIN, I can tap the area to enter a PIN again but there is no option to either change the PIN or remove the PIN and go back to just a basic SuperSu prompt. Question number one - is this how it is supposed to be or am I missing something? Number two - If this is how it currently is implemented, could you change this behavior in a future update? Thanks. By the way, I can still delete the app from /system/app and reboot and install it via recovery, but it'd be a lot more convenient to have more options within the app.
[SuperSU] asusgarb:
Hi Chainfire. I'm on a Galaxy Note with a modded LTA stock rom. Usually i immediately open SuperSu and it asks me to update binaries. This time I forgot and now it does not ask. How can I update binaries?

Inviato dal mio GT-N7000 utilizzando Tapatalk
[SuperSU] jazzruby:
You can check the su binary version from terminal:

su -v

1.61:SUPERSU

The above result shows the su binary version and the current Superuser app (Chainfire)

-JR-
[SuperSU] asusgarb:
Sorry but even if i'm able to see that, how can I update them?

Inviato dal mio GT-N7000 utilizzando Tapatalk
[SuperSU] shoey63:
If you don't get a notification to update the binary, then it doesn't need to be updated;)
[SuperSU] asusgarb:
i've read with terminal emulator and says 1.61 (but the app is 1.65) so they're updated? but why only at first boot? i don't think it autoupdates the binaries.
[SuperSU] jazzruby:
Yes, you're all up to date.

1.61 - su

1.65 - SuperSU

Sent from my Galaxy Nexus
[SuperSU] Chainfire:
It'll tell you when it needs to be updated. If it doesn't tell you, it doesn't need to be updated. It's that simple.
[SuperSU] asusgarb:
sorry Chainfire. I was worried because i flashed the rom i'm using three times in 2 days, and i read an user's reply where it said it had problem when he didn't updated binaries immediately after boot. now that i know everything's fine i say

thanks alot and see you later
[SuperSU] boyheadkick:
1.61 is the SU binary version

1.65 is the SuperSU app version

far as i understand the binary and the app doesnt have to have the same version..course, i could be wrong :laugh:
[SuperSU] chachi:
Dare we apply this to cm11?
[SuperSU] Chainfire:
There's no UI installed by CWM ?

The permission check skip looks good to me, if you've tested it and it works, great.

As for using my su binary, if I look at https://github.com/PhilZ-cwm6/philz_touch_cwm6/blob/cm-10.2/su/install-su.sh, the following are the minimum changes (following my full script would be even better, but this is the bare minimum):

copy the su binary to these locations and chmod 06755 (this is the same binary file, you need to have it twice):

/system/xbin/su

/system/xbin/daemonsu

Do *not* ln it to /system/bin . Do not check for /system/etc/.has_su_daemon , just copy over the install-recovery.sh file from my ZIP.

That should be enough. Then the user will have root (without UI). They can manually install SuperSU from the Play Store, or until they do, all apps will be given root if they ask for it.
[SuperSU] Chainfire:
If you're talking about per-app PIN, set access to "accept" or something different than PIN to remove the PIN. If you're talking about the global SuperSU PIN (in settings), tap it to open the PIN dialog, then press the bottom-left Clear button, and your PIN is gone.

I'm not sure what is not working here ?
[SuperSU] MikeRL100:
Yeah I had to hold down the clear button. I'm not normally that clueless. Sorry for not specifying I meant the global PIN. A lot of apps (but not yours!) have been acting up on KitKat, and I've reported so many bugs and tested so many betas I guess my brain fried out. Your app works flawlessly on KitKat, and sir I and the community thank your rootly hackerness for rooting the Nexus 5. I don't normally title people, but I figure you of all people have earned it! I normally use Koush's Superuser, but I used yours for ages and am using it now, and I loved it enough I bought the Pro version. It's the least anyone can do for such quality work. Thanks again for the help, and the service you've done for the community, me included.
[SuperSU] Phil3759:
I appreciate the time you took :good:

I can use either your script or the minimalistic one from Koush. I will go with yours

superuser.apk is too big to fit in many recoveries. I have added a menu for manual rooting that asks user to install app from market later

Going to implement your su binary since Koush one doesn't support new TW stock ROMs. Also, from yours, people can migrate to what ever they like

Thank you again
[SuperSU] MikeRL100:
Call me the gestapo, but you're of the minority on here or any forum that knows what the "Thanks" button is. I hate it when people say thanks and don't hit that button. I like to watch the thanks meter grow, especially when it's mine.
[SuperSU] bpark32:
Sorry for noob question. I just upgraded to KitKat on my GNex. Downloaded SuperSU from Play Store, n it tells me to update binaries. Tried both ways, and it doesn't work for me. Could anybody give me some insight as to what I need to do, or am doing wrong? Thanks in advance.

Sent from my AOSP on Toro using Xparent Skyblue Tapatalk 2
[SuperSU] dadoc04:
Uninstall the playstore version and use the flashable zip in the OP

Sent via Galaxy s4
[SuperSU] gbswales:
also got update SuperSU issues

Same problem here. I installed SuperSU a year ago when I rooted my galaxy S3 but since installation I get prompted to update SU binary but when I try using either of the offered methods it simply fails. I cant uninstall it to start over and when I read the uninstall instructions it says to open the original app and update that first! I didnt have any superuser app before this one so do not know how I can do this.

It hasnt been a problem to date as it has simply given permission to all apps that need it but it wont give permission to the screen recorder app - maybe I pressed no without realising but I cant get past the update screen to get into settings to see if I can change the setting.

Has anyone worked out how to uninstall super SU or update it

t am running 4.1.2 on a GT-19300 using the stock ROM
[SuperSU] Pkt_Lnt:
Have you flashed the zip file from post #1 in recovery?
[SuperSU] MrWareWolf:
clustermug... 8(

This app used to be so awesome. What happened?

I update my tablet to 4.3 and all these problems come up.

Installs from recovery are fine but that just made my situation worse. Now titanium says it can't get root.

Android 4.3-thors rom, a500 Acer, want a logcat or something?
[SuperSU] chachi:
WareWolf - flash the zipfile
[SuperSU] wmarcin:
1. Flash SU zip file from recovery.

2. Install busybox.

3. If using CMW, always say 'no' when asked whether you want to fix root. Not sure about other recoveries.
[SuperSU] gbswales:
further question

I wondered about doing this, thanks, my concerns are that I am not able to remove the current version as there is no uninstall option - or would flashing replace it? Also I paid for pro so wouldnt that get lost?

It s quite possible that I loaded it this way in the first place but its so long ago now I have forgotten - I am running TRWP recovery
[SuperSU] gpzbc:
Survival Mode

Would someone mind telling me why "Survival Mode" needs to be disabled before doing a nandroid backup? I'm just curious.

Thanks!
[SuperSU] jesssiii:
Curious here as well.

LG G2 VS980 (VZW)
[SuperSU] MrWareWolf:
My fix was accomplished by an unordinary means. I put in superuser app from another company which failed but it caused SuperSU to kick in and start working. Apps now ask for and get permission for su requests.

Luving this new 4.3 rom.
[SuperSU] Pkt_Lnt:
Flashing from recovery will totally replace the standard app, but not the pro version.
[SuperSU] Chainfire:
v1.69 released

v1.69 has just been released. See the ZIP in the first post and the changelog on the third post. Google Play will start updating shortly.

This update includes fixes for two exploits that have been found and may allow an attacker to gain root access without prompting. Disclosure of these will take place next Monday, so I advise everyone to update before then.
[SuperSU] Schrotty35:
Dont see a zip file in the first post but xda have problem now.
[SuperSU] User_99:
Already there. Here the link :silly:
[SuperSU] Dark_Avenger:
[MENTION=631273]Chainfire[/MENTION],

after the update to 1.69 I can't switch application pages by clicking on the tab - click on "Log" and "Settings" does not work. It's on Gingerbread 2.3.5. Page slide left/right works fine, but does not update the tab (mark as selected).

No such problems with 1.65.
[SuperSU] osm0sis:
[MENTION=631273]Chainfire[/MENTION], please remove this line from your install script:

echo 1 > /system/etc/.has_su_daemon

As discussed previously, it breaks things for the other guys and Koush reached out to you on this. :good:
[SuperSU] Chainfire:
So? Just because someone reached out doesn't make it my top priority. It's on the to-do list as are a plethora of other things (and it's certainly not the only place this needs to be adjusted)

CVE's however require immediate attention, fix, and release - and that's what happened here, a security related update with absolutely no regard to anything else on the to-do list. The other changes just happened to be implemented already.
[SuperSU] tarund:
Reboot loops by v1.69

After upgrading from the Play Store, I'm prompted to update the binary. Which I've tried to do both normally and via custom recovery but the phone just goes into a boot loop after booting into the OS.

After uninstalling v1.69 and reverting to v1.65, all is well.

I also tried to install the v1.69 by using the the zip file in CW Touch Recovery and before completing the install, the phone reboots; install does not finish successfully. I believe there could be an issue with this version of SuperSU.
[SuperSU] djjstew:
Just completed zip install and worked gr8 for me
[SuperSU] tarund:
Did you remove the previous version?
[SuperSU] osm0sis:
Gotcha. Thanks sir. :)
[SuperSU] Chainfire:
This post is useless without information about exactly what Android device running what firmwre you are using.
[SuperSU] tarund:
Phone is HTC One running ROM ARHD 31.0 (3.62.401.1), Firmware is AT&T v3.17.502.3. Recovery is CWMR Touch 6.0.4.3
[SuperSU] HorstiG:
Works without problems on S3 with Carbon ROM. I flash the zip File and install the Key from Store.

Thank you for Update.

Horst
[SuperSU] polobunny:
Just as I was thinking of skipping this version out of lazyness. Thanks for the heads up and fix as usual.
[SuperSU] djjstew:
nope just installed on my phone and tab using the zip file in recovery
[SuperSU] thejordan:
Flashed this immediately after flashing the 4.4 update zip on my N7 (2013). Worked perfectly. Thanks CF for all your hard work!
[SuperSU] Technical:
Chainfire, can you update the flashable zip?

http://download.chainfire.eu/351/SuperSU/UPDATE-SuperSU-v1.65.zip

Thanks.

Sorry, realized it is here http://download.chainfire.eu/365/SuperSU/UPDATE-SuperSU-v1.69.zip
[SuperSU] Pkt_Lnt:
He did, look at the link in the OP!

http://download.chainfire.eu/supersu
[SuperSU] RovG:
Hi [MENTION=631273]Chainfire[/MENTION],

The updater-binary in the zip, backs up Map, GMS_Maps & Youtube and then deletes them to make space in /system. After the install of SuperSU, etc it restores them to /system/app. Unfortunately this does not take into account the fact that these apps on the Galaxy S2 with stock JB are symlinked to preload. Consequently the restore to /system/app may result in either running out of space or unnecessarily consuming space on /system.
[SuperSU] tarund:
That didn't work for me at all. Every time it says 'Installing update...' in recovery, the phone reboots. I tried to completely remove the SU binary and app using "Full unroot" but that doesn't do anything either. I'm not sure where the issue is.
[SuperSU] marc112:
Same here! HTC Desire S running Gingerbread 2.3.5. Version 1.65 worked fine..
[SuperSU] Chainfire:
That's a very interesting bug re: those tabs... must be in the actionbar library I'm using. Just loaded SuperSU on my trusty old Galaxy S (running 2.x) and the same issue ... under investigation :)
[SuperSU] marvellyukon:
SuperSU v1.69 => Not work in the upper scrollbar on the screen resolution 480x854
[SuperSU] Xoib:
Hey [MENTION=631273]Chainfire[/MENTION],

Thanx for your work.

But why (running 4.3 stock since the beginning) today was the first time the process init asked for root permission, I grant it but there has been no reason why it triggered it. Just why today ? I did not installed any new apps for weeks, not even did some new stuffs with it.
[SuperSU] eLCruz:
SGH-T989 Stock 4.1.2 (was rooted on 1.65) used zip binary failed to update both ways. Restored using twrp... Used play store disappeared after install to system option (with double reboot). What's up with 1.69? Never had trouble before... :banghead:

sent from "Where Man has Never Gone Before" using Tapatalk Pro :confused:
[SuperSU] Gitah.:
I'm on 4.4 and I just flashed supersu but it doesn't show up on the drawer, what happened?