yashsingh1/xdaforums huggingface dataset:
[SuperSU] Valdeck:
Hey all I am having a issue with SuperSU and am hoping you can help me out.

In the past SuperSU has worked like a champ on every phone I have ever had (including my current phone). However I thought I was going to need to return my phone so I put it back to stock but ended up not taking it back. Now for some reason I am having a strange issue with SuperSU.

It flashes fine and grants permissions like it should. But when I restart to apply changes the changes are never applied. If I do a softboot somethings like exposed will work but they stop working the next time I do a full reboot. I have tried uninstalling, flashing from TWRP, installing from the play store, pretty much everything I could think of but so far the issue wont go away.

Any ideas what I could do to fix this?
[SuperSU] Craniotomy:
i have the same problem with you guys, i already did a full wipe and clean install and same issue, i can't make some exposed modules work, i can't even install a theme thru twrp, even if i flash it several times, and I've updated binaries also still nothing, before super su was updated to v1.55 all Themes and exposed worked. Hope someone can help us with this issue.

POWERED by the MASTER!
[SuperSU] Kfler:
It is embedded into the setting menu, there is no option to switch superuser or uninstall.
[SuperSU] RedBullet:
flashing this on my nexus 10 which recently updated to 4.3 doesn't work...

SuperSU still says su binaries not installed
[SuperSU] Azarin:
Same issue here with my Nexus 4 running stock 4.3 + the recent OTA update. I tried updating the app via the play store, but every time it loads it displays a message about the SU binary being missing and quits.

I have tried flashing the latest SU update zip from TWRP, along with clearing the cache, but without any luck.
[SuperSU] KillerElohim:
The same, but with nexus 10, already try with the last version (UPDATE-SuperSU-v1.55) with a clean stock rom. :(
[SuperSU] lion7718:
I have no problem on my Nexus 4 running stock 4.3. I had to uninstall SU to do the last OTA update but flashed SU 1.51 afterwards without any problem...updated to 1.55 through the play store & updated binary as normal.
[SuperSU] 78Staff:
No issues installing the zip on 4.2.2 Task AOKP, FWIW.
[SuperSU] RedBullet:
Yea, I think it is some new interaction with 4.3 that came with the recent update.

I was finally able to get it using the google nexus 10 toolkit which was recently updated. Still don't know what the issue is exactly.
[SuperSU] KillerElohim:
RedBullet, can you tell me the steps, you did to make it work?

Already try using toolkit, but every option to root , didnt work.

Thank you.
[SuperSU] nth0814:
could you add a shortcuts for enable/disable superuser,please?
[SuperSU] Sinergie:
When I go to CWM recovery (6.0.3.6) and choose reboot system now followed by the question:

ROM may flash stock recovery on boot. Fix?

THIS CAN NOT BE UNDONE

- No

- Yes - Disable recovery flash

When I choose "Yes" then I lose root, is this normal?
[SuperSU] My1xT:
just say no, and no problem

depending on device
[SuperSU] jbhtexas:
Problem with 1.55 and Android Wifi Tether on HTC phones

Hello!

I have an HTC EVO 4G LTE running stock ROM. I was running SuperSU 1.04 with no difficulties. However, I recently noticed that SuperSU was no longer working, displaying a message that the binaries needed to be updated. I downloaded the 1.55 zip file and flashed it through recovery. While other apps needing su access seem to work fine (such as titanium backup), android wifi tether (3.3-beta-2-06102013) stopped working. There are no indications of errors in the android wifi tether logs, and the app seems to run normally. Howerver, the app does not broadcast its SSID.

Upon checking bug reports for this issue on the android-wifi-tether wiki, I found a bug report from a user who has/had the same problem with an HTC One after upgrading from SuperSU 1.30 to 1.52. He solved the problem by downgrading back to 1.30. He also obtained some screenshots from the SuperSU full content log indicating what the problem might be between SuperSU and android wifi tether. I don't fully understand the errors, but perhaps they may help Chainfire. The bug report which includes the screenhots is below.

http://code.google.com/p/android-wifi-tether/issues/detail?id= 1879

How does one downgrade to an earlier verion of SuperSU? Can I still download 1.30? I still have the 1.04 update zip; can I just flash that from recovery to downgrade? Do I need to do a cleanup before from within SuperSU before downgrading. Sorry for the noob questions. I did some searching but didn't find clear answers. Is there a FAQ for this sort of thing?

Thanks!
[SuperSU] fernandezhjr:
[MENTION=939023]jbhtexas[/MENTION]. Make sure this from the op doesn't apply to you. There is link in there that gives you an older version.

"From v1.50 onward, ARMv5 devices are no longer supported. v1.45 (click to download) is the last ARMv5 compatible version."
[SuperSU] jbhtexas:
Thanks for the reply! The Evo 4g LTE is ARMv7, at least according to

http://en.wikipedia.org/wiki/Snapdragon_(system_on_chip)#Snapdragon_S4

I've found some older versions to try. Could someone just confirm the procedure for downgrading?

Thanks!
[SuperSU] polobunny:
I don't believe you'll be able to downgrade that easily, from the way SuperSU is made. Take that as a safety precaution.

My 2 cents.
[SuperSU] Oops...:
Yes, it's normal. You have to chose No, so that the script required for 4.3 persists. This is a "feature" not a bug.
[SuperSU] POWerSUrgeSW3:
Yeah but it pops up every time you exit out of recovery. At least it was in my situation. I ended up going to TWRP recovery just so I could automate things without having to select that before I could boot back into system

~Max

Sent Via My WSv4.2 MD4 D2SPR
[SuperSU] fernandezhjr:
There are cleanup options within the SuperSU app. Then flash the older version for a clean install.
[SuperSU] ThurstonX:
I successfully went from 1.51 to 1.45 by uninstalling the app, flashing 1.45, then installing the 1.45 APK. That allowed me to access the app without being told to update the binary. The update for 1.51 was listed when I checked for updates (for all apps) at the Play Store, but I just ignored it. I did this to keep CIFS working.

I should note that upgrading to 1.55 from 1.45 did NOT break CIFS, so :good: for that! :highfive:
[SuperSU] Sinergie:
If CWM asks me that then I would assume I go with "Yes" because I don't want the stock recovery but CWM. Choosing "No" would be illogical since then it seems you would opt for the chance stock recovery would return instead of CWM. Also I believe this shouldn't have an effect on having root or not, but I'm not sure if this is because of CWM or SuperSU.

Finally like POWerSUrgeSW3 pointed out the question returns everytime you reboot the system from CWM, so it would be an issue with the latest CWM after all?
[SuperSU] adrman:
Use a file browser with root access and create a file in system/etc called ".installed_su_daemon" and you won't be prompted again until you flash a new or updated rom.
[SuperSU] wozhere:
My Solution to Missing Binary SU Crashing of SuperSU:

- In recovery wipe Cache & Dalvik

- In recovery Install an old SuperSU 1.3x (I had 1.34), you need the update .zip version not .apk

- boot android but do not run SuperSU

- Install a SuperSU 1.4x (I had the 1.45), you need the .apk file

- Run SuperSU, if asked to uninstall other SU apps disagree & say cancel

- When asked to update Binary SU via normal android or via CWM/Recovery update, I chose CWM/Recovery method

Boots into recovery, installs binary update & reboots, you need not do anything, runs normal.

Once back to normal, I suggest disable update if any in Play Store/elsewhere & do not manually update till this ridiculous problem is fixed for good. I am not going to update for another year. Super User also gives similar problem. Whoever fixes it first will be my long term choice.

In settings I changed it from prompt to Grant so it does not keep popping up, half the time it is hidden behind the stalled app & useless anyway.

My initial 1.34 zip one was in a combo zip (TWRP+SU1.34+Busybox)

It is really sad this bug is wasting numerous hours of vast numbers with many given up and there is virtually no support. Also if firewall/privacy/anti-virus etc. apps are causing this in some cases, it is equally unbelievable.

Good luck.
[SuperSU] polobunny:
If both of the solutions give you the same problem yet it works for the majority of people, I would assume the problem would be on your side...
[SuperSU] wozhere:
You misunderstood what I wrote, no point describing it to you. Further, if you google various phrases regarding this bug, plenty have posted here alone & in other threads, you will see the minority you pit against the majority is actually a huge army posting in tens of forums elsewhere. Since you seem to have extra free time on your hands that is.
[SuperSU] polobunny:
You're the type of person that makes XDA a least enjoyable place. No point to go borderline insulting. I imagine civility isn't granted equally amongst all.

You know you can completely forego the app itself and simply use the su binary alone.

This will automatically grant su to anything that asks.

If you take one more instant of your time, you'll be able to open the update-script from within latest CWM/TWRP flashable SuperSU and see how simple the script is. These actions can all be done effortlessly one way or another once root is acquired. That's another solution if you would prefer to keep the whole SuperSU functionality. Attached with this post is the update-script, might you wanna glance over it.

Let's just say there's a thousand ways to make it work for someone willing to take the time. None of them that takes more than half an hour.
[SuperSU] wozhere:
Irrelevant & theoretical, as testified by many in XDA & tens of of forums: numerous normal solutions have been put forward & tested & except for a few in the large minority the normal remedies do not work which is why we have a silence on this affecting THOUSANDS OF PEOPLE. You flame then name-call not knowing what you are talking about.

If you were right, the OP would put that irrelevant false fix of yours in the OP in response to the many who have this problem GLOBALLY not to mention by many in this thread (gone ultimately unanswered BTW). But he, not being a busybody & actually productive & intelligent, knows better than you not to suggest that as the cure. Talk to him to promote "that ^" as his official fix if you are honest. You are in fact telling him to promote your irrelevant fix, not me.

QED.

Best wishes.
[SuperSU] polobunny:
My fix which will not be added to first post, neither would yours, for lack of usefulness outside the realm of a tiny parcel of users.

I assume you have tried it, probably wrongly, but I honestly don't have more time to waste for someone as closely minded as you. If you're unwilling to even attempt to solve your issue by following clearly enough outlined means, then I imagine your sole point is to bicker, complain and act like a pompous child all the while entertaining the thought anybody here should give you undue attention.

See, I can use cool words too! :)
[SuperSU] wozhere:
1- You continually deny there are thousands with this problem & most have tried numerous normal routes, as I did, which OP knows well.

2- You do not understand the basic fact a child would understand that having fixed the problem I am not interested in recreating the problem in order to try your irrelevant idea. If you do not fathom such basic things, I would be crazy to listen to you, which is not possible anyway as I fixed mine. Not to mention in response to the thousands who tried many suggested normal fixes without success & gave up.

Take it easy.
[SuperSU] :
Booyah!
[SuperSU] Oops...:
If you go with Yes you delete the script which is installed to make boot persistent. So indeed NO is the correct answer. It's basically a 4.3 change (security stuff) which requires the workaround with the script.

Sorry for not having more details on hand, but you can search in this thread. Should be explained here... If I remember correctly ;)
[SuperSU] Chainfire:
Please refrain from personal insults, thank you.
[SuperSU] polobunny:
My apologies Chainfire.
[SuperSU] shoey63:
[MENTION=631273]Chainfire[/MENTION] Is your su binary open source or proprietary?

---------- Post added at 09:27 PM ---------- Previous post was at 09:25 PM ----------

Try " my apologies" - there are no excuses;)
[SuperSU] polobunny:
Indeed, my French reared it's ugly head. ;)

His su binary is closed source.

Koush has an open source superuser though.
[SuperSU] ironia.:
proprietary
[SuperSU] jbhtexas:
I used the "Switch supersuer app" cleanup option and then installed the SuperSU 1.30 zip via recovery. I then reinstalled android wifi tether (per a suggestion in another forum), and android wifi tether worked fine.

For a test, I then upgraded to SuperSU 1.55, reinstalled android wifi tether, and android wifi tether worked fine !!

So, perhaps android wifi tether doesn't like something about the SuperSU upgrade, but it appears that a reinstall of the tether app will solve the problem !!
[SuperSU] yethz:
Mine when choosed yes it wont ask anymore when exiting recovery.

Using Nexus 4 PhilZ Touch Recovery by the way..
[SuperSU] Chainfire:
New CF-Auto-Root for those new SGS4 I9505 firmwares with Enforcing SELinux -https://plus.google.com/113517319477420052449/posts/5ggu7naWtaW

If it works out well, other SuperSU releases will be updated tomorrow or so.
[SuperSU] 089man:
Have a question, I have galaxy s2 with pacman 4.3 android. I have used su long time and have also buy the pay version. Now in 4.3 su not work. Can I used the zip file from op and than su works? Must I flash this zip and than the apk, or only the zip?

I9100 Tapatalk 4, Rom1 Pacman Android 4.3 / Rom2 Test only, Dori Kernel for. 4.3
[SuperSU] POWerSUrgeSW3:
Yeah the issue seems to be related to CWM only....

~Max

Sent Via My WSv4.2 MD4 D2SPR
[SuperSU] Chainfire:
v1.60 released

v1.60 has just been released. The ZIP file linked from the first post has been updated, Play update itself in a few hours, and the CF-Auto-Root's are updating as we speak (I suspect they'll be done some 30 minutes after this post).

See changelog on the first page (post #3).

I'll post it on Twitter / G+ when all have been updated, but as the ZIP is already available, you can get it already if you want.
[SuperSU] Phhoenyxx:
I just went to the Play Store and updated it. Rebooted, re-installed it as a system app, rebooted again, everything is good. Great job as always! Thanks!
[SuperSU] HorstiG:
Great Work, thank you for 1.6
[SuperSU] SecUpwN:
[MENTION=631273]Chainfire[/MENTION]: YOU ROCK. Never give up!
[SuperSU] theprodigy85:
not sure if it's related, but my Greenify app's app analyzer just hangs now after the update.

Not sure if it's just a coincidence. Anyone with that app have the same issue?
[SuperSU] aamadorj:
After installing SuperSU v1.60 (with the recovery ZIP), Handcent just FC when trying to run the app. I went back to Supersu V1.55 and Handcent started to work again. My Galaxy Nexus is using ParanoidAndroid 3.99 (02-SEP) with Fancy kernel r40 BIGMEM Linaro (other details at the signature).

UPDATE: I found that updating SuperSU from version 1.55 to version 1.60 from Google Play didn't produce the misbehavior of Handcent.
[SuperSU] friedrich420:
I can confirm working FLAWLESSLY on MH8 Base Sir!! Thanks for sticking it to Samsung once again!! ;) :good:
[SuperSU] polobunny:
Upgraded to v1.60 just now, works fine for me. Greenify Free (Not donate version)

---------- Post added at 11:01 AM ---------- Previous post was at 10:49 AM ----------

Leave it to you to bring back the idea of a root user to SELinux. :p

While I understand the whole concept of SELinux, I don't have a freaking clue what the hell its doing on our phones. Why do we even need this crap? Is there enough people getting fished/hacked/exploited on their phone to the point it makes sense having enforced access policies?

Either way, I feel like I'm missing a part of the puzzle, or this is all marketing scare tactics bull$hit.
[SuperSU] Azarin:
Still not having any luck avoiding the missing binary error when starting the app after trying 1.60.

Haven't been able to get it working since the security update Google issued for 4.3 on the Nexus 4. As suggested by some others on the post, I have attempted flashing older versions via TWRP back to the first SU version which supported 4.3 with no luck.

Wiped cache etc each time. It seems I'm not the only one with the issue looking around a bit - is there any more info I can provide which may be helpful in troubleshooting?
[SuperSU] lorolouis:
Agree ...

Whoever needs a "security" shouldn't they stay unrooted and factory locked at all?

---------- Post added at 11:53 AM ---------- Previous post was at 11:40 AM ----------

BTW, IS THE BINARY actually ver. 1.56?

After all this new s....t about SELinux .... how now we can be sure that our SuperSU is installed properly at all say on PA 4.3 based ROM ?

Any reliable verification ?

What does it mean "you may need to re-root" and "app update may not be sufficient"?

How to check if su is fully installed to support the SElinux on my 4.3 rom?

is having that line on ps command listed a sufficient prove?

(some Terminal app -> type ps)

...

root 2558 195 ..................... daemonsu: 10099

Thank you guys ... it is getting very unpleasant this 4.3 SElinux "feature" that everybody talks about now.
[SuperSU] VivaErBetis:
I think that it's to make android more NSA compliant :sly:
[SuperSU] Chainfire:
At the moment, I wouldn't really know where to begin finding the source for this problem. Replicating the issue on any of the phones I actually have would go a long way ...

It reduces exploit attack vectors.

While being rooted is definitely more insecure than not, just because you can be had by a root app you mistakenly trust, doesn't mean you shouldn't protect yourself from malicious apps trying to gain access in other ways.

Yes
[SuperSU] lorolouis:
Hey [MENTION=631273]Chainfire[/MENTION]

Nice to see your direct responses here.

We all understand that no way, we have to follow these new things.

Just we need some good way to know if all is working properly and fully as expected.

This particular thing looks like we may have situations that all seems to be "working fine" with no issues but still - the new features not properly setup at recovery, su or ROM side as they all are cross involved to it.

So .. for the SuperSU 1.60 (1.56) is it enough to say all is OK if I see daemonsu running ?

Best Regards.

Good work, really!
[SuperSU] Phhoenyxx:
I have a quick question for all you knowledgeable folks...

I'm not a root expert by any means. I just installed the SuperSU 1.55 zip a few days ago via CWM Recovery (via fastboot boot, so I'm back to stock recovery). I then performed a clean-up to reinstall it from the Play Store. I then installed it as a system app. All was good, I had root access.

Today, I updated directly from the Play Store. It says I have version 1.60. After some basic maintenance operations, I got it back as a system app.

What I want to know is if the update from the Play Store also updates the SU binary to 1.56, and if so, how would I know if mine was updated? Is there a way to determine the version of the SU binary? Keep in mind that other than having SuperSU 1.60 and both binaries (SU and DaemonSU in /system/xbin), I'm running a completely stock GNEX (Maguro) with Android 4.3 (JWR66Y).

Thanks in advance!
[SuperSU] volkmadi:
Hi all,

I read here all the time with the 1.6 all works good, but I'm really scared.

I updated this morning to the DBT I9505XXUDMH5 and re-rooted with the CF-Auto-Root-jflte-jfltexx-gti9505.zip

which has the 1.6 included. Ok, I'm root, but 50% of my apps are not running/die all the time.

I disabled the selinux like told in one post around here with "pm disable ...." but has not changed something.

I did even a full wipe (what I hate) and then brought back my apps with titanium, but it does not help.

Even my whatsapp is dieing. I don't know wht to do, in the state like that I have no smat phone, I steped back

to an old mobile. :) or better :(

I have no idea what to do.

Need help!

I know, that triangle away and odin mobile do not work at the moment, but does that mean I need to uninstall them?!

As I said, I have no idea how to get my phone/the apps back working and need real help!!

Thx in advance!!

Dirk
[SuperSU] polobunny:
Definitely, but so does not owning a smartphone. :p I just find this ridiculous overall. Let's pad the whole world with styrofoam, no more dangers ever haha
[SuperSU] abatt:
I update to 1.60 and tried to install as system app. My phone wont boot after HTC logo black screen. Any advice ??? HTC Desire X with custom rom myONEdx RC3.0.
[SuperSU] MVJ1225:
Not sure what's going on...My SuperSU just updated through GooglePlay and when I went to open SuperSU it says binary needs to be updated..I press continue..Says If you have a custom recovery like TWRP or CWM that can be used to (try to) install the SU binary..This is recommended for HTC devices...so I press TWRP/CWM..It loads into TWRP...but then nothing...what steps am I supposed to take from that point?

I have an EVO 4G LTE
[SuperSU] KreNtal:
Hi guys. I flashed supersu by chainfire and then installed cm 10.2 but the built-in superuser option doesn't work. Can someone explain how can I make it works?
[SuperSU] polobunny:
Uh, that's not really the place to ask this question. This thread is for SuperSU by Chainfire, so you need to flash it AFTER your rom, not before.
[SuperSU] DeanGibson:
SuperSU fails installation of the su binary

I have ten Android devices (all rooted); six with Google Play and SuperSU installed. Until about a month ago, whenever I updated SuperSU and it needed to update the "su" binary, that worked fine.

However, starting about a month ago, whenever I update SuperSU, the update succeeds, but on two of the devices (an original Motorola Droid and a Nook Color), the update of the "su" binary fails. I still have root access and and the SuperSU hook to catch rooted application updates still works. Everything is fine except that when SuperSU fails the update, it exits (leaving the old "su" binary around), so I no longer have admin control over rooting permissions, etc.

The Droid is running Android v2.2.3, and the Nook is running v2.2.1 (the other devices are running v4.x). Both show the following line in /system/build.prop:

ro.product.cpu.abi=armeabi-v7a

Note I manually root each device and I DO NOT modify /system/build.prop (except to change the number of wifi channels on the Nook).

If I take the working SuperSU "su" binary from one of my other Android tablets, and put on one of the Nook and run it, it seg-faults.

After noticing that there was no immediate fix forthcoming, I came to this thread. I note that you no longer support Arm-v5. The above /system/build.prop line seems to suggest that both of my failing devices are running an Arm-v7.

So, assuming that this is not a bug that you will fix, should the older SuperSU.apk fix this (my guess is yes), if so, will I have to manually prevent Google Play updates???

ps: I have the "Pro" version.
[SuperSU] My1xT:
usually you can prevent play update per app with menu-> Auto App updates (or whatever it is called in english)
[SuperSU] Chainfire:
Are you using CWM or TWRP ? If not TWRP, please see if TWRP is available for your device and flash that, then try the update again. Now when you select to update through CWM/TWRP, you'll reboot into TWRP, and because of the error, probably you'll just get the main TWRP screen.

At that point ADB into your device and, get recovery.log ( "adb pull /tmp/recovery.log" should put it in your current folder on your computer ) and pastebin.com that.

That might help me figure out the problem, and will take about 10 minutes of your time.