yashsingh1/xdaforums huggingface dataset:
[SuperSU] blackj30:
Hi, I am on supersu pro and was running ok on my htc desire sv, until the last update from playstore today. After updating, i cant update binary as requested. It said binary update failed. Can you pls show me or where can i download binary update via cwm? Or how?

Thanks guys.
[SuperSU] bombadier:
Try flashing the update zip in recovery
[SuperSU] AlxMAX:
Have a look at the original message which started this topic! You'll find a link to a ZIP file, UPDATE-SuperSU-v1.30.zip, which contains your su binary.
[SuperSU] marbulas:
Flawless on my SGS4(SHV-E300S)! :D Thx a lot!
[SuperSU] JZ SmartMort:
Got a pretty significant problem --- for now I'm bricked but I can obviously restore using Odin and stock ROM --- but I want my old junk back :( and I'm only able to do this because I have the microUSB dongle for my GS2 (thank the lord for me doing something right for once!) that puts the GS2 into download mode (not recovery)

I updated to the new version and it said that I need to update my su binary to which I pressed the TWRP/CWM button hoping to see a quick CWM flash and another reboot. However, my GS2 is now stuck on the Galaxy S2 logo perpetually and I'm stuck.

Any ideas?

Thanks!

JZ

EDIT: actually holding power then holding volume down can get me over to Download mode. Still bricked at the moment though.
[SuperSU] calisro:
What does your problem have to do with supersu? post in your devices forum.
[SuperSU] JZ SmartMort:
This piece of my post should have been more obvious, sorry for not being too clear: I updated to the new version

After upgrading SuperSU when Play Store notified me of the update, it installed successfully and asked for the binary update after which I pressed TWRP/CWM which is how the new su binary would be installed.

---------- Post added at 05:07 PM ---------- Previous post was at 04:24 PM ----------

Quoting myself, sorry...

After putting my SGS2 into Download mode I then used Odin to write an old/good known kernel plus CWM. I used some Syah 3.3.2 tar file which gave me back CWM, after that I reflashed my Shostock3.0.2 ROM and I am looking much better now... successfully unbricked. It's good to be a nerd :) but I'm definitely gonna treat updates a bit more seriously especially something low level like SuperSU which may touch/run recovery pieces, etc.

That ability in SuperSU to apply the new su binary via recovery is pretty dangerous IMO and needs more warnings and confirmations considering what it did to me but I realize it doesn't do that to everyone.

Thanks!

JZ
[SuperSU] gpzbc:
Or just use a custom launcher like Apex or Nova.
[SuperSU] Pons:
Off the top of my head, that's how you enable the icon after it's been made invisible. And you can run it from adb shell from the terminal/command prompt on your pc.

To make it invisible, go into SuperUS > Settings > Launcher Icon, and choose Invisible.
[SuperSU] casonswag:
Delete
[SuperSU] bedtime_with_the_bear:
The installer only recommends recovery based installation for HTC devices, and Chainfire has gone so far as to state in this thread (I believe, if I'm wrong, it's my mistake, not Chainfire's) that you should normally never use the recovery based install on a non HTC device. There should be nothing preventing you from updating the binary normally on a Samsung, which wouldn't even require a reboot.
[SuperSU] JZ SmartMort:
I'm certain you're correct but keep in mind that quoting this thread is a moot point when the update was done via the Play store and I only came here after having the problem. The only point I'm making after an hour of cold sweat beads is to have more confirmation boxes on the piece that you're saying this thread warns about --- but not much warning exists in the software. That's my suggestion based on this little experiment, take it or leave it. Thanks!
[SuperSU] gamepois0n:
finally, a new update
[SuperSU] Mr_Gee:
Is there already a nice solution for the automatically unroot for specific applications?

At the moment I'm leaning towards Tasker + widget to get this done but if the is a better /nicer solution ..
[SuperSU] Magissia:
This is a dev tool and devs are supposed to know what they are doing.

Regards
[SuperSU] JZ SmartMort:
Just because the tool is for advanced users and backend Devs (both of which I am) it doesn't mean it can't have one more level of confirmation boxes --- don't forget that the tool is available for plain old users in the Market. I'm not sure why my point is being "defeated" with that argument. I'm just making a suggestion, period... not much more than that. If Chainfire doesn't want to do that, perfectly fine with me because I know how to unbrick my phone, less experienced users of his app may not.

I've never seen my phone brick in this particular manner where it was stuck at the logo... and considering that the tool popped the update of su binary prompt right after the update from the market I responded to quickly wanting to just finish the update (like I do with most other apps that UPDATE via the market). So to me adding one more "are you sure you want this typical HTC procedure" prompt is not totally wacky. It may save some heartache for others.

Thanks!
[SuperSU] bedtime_with_the_bear:
The point is that there is a "are you sure you want this typical HTC procedure", and you chose yes. You could probably make a case for a clearer prompt, or perhaps moving the recovery option to an "advanced" menu somewhere, but I'm not convinced there's a good use case for more prompting.

The problem with adding prompts is it's usually far easier to just click OK to get on with what you are doing than it is to read them, so adding yet another prompt is very often counterproductive, and in general interrupting the user is no longer considered a good idea.
[SuperSU] BonnyBedlamBoy:
What about throwing an eye to the OP (first post) of this thread?
[SuperSU] JZ SmartMort:
Your argument is definitely valid and I agree. I also can't argue that I made a bonehead move by choosing the HTC task of TWRP/CWM rather than the other (forgot the label). In my opinion the labels threw me off a bit because in my mind I'm thinking "well I have CWM so why not go for that button labeled CWM" even though the normal method would have probably worked (but I doubt it w/o a minor special provision because on my SGS2 using Shostock3 ROM I need to mount /system with r/w probably for that method to have worked correctly). Better labeling and confirmation is still something to think about.

It also seems that the new SU binary is kinda optional considering that when I rolled it all back and updated SuperSU I lost no functionality w/o updating to the new binary. I'd probably stick it under "advanced" as you suggested.

One question in that regard, and I obviously see the OP with the CWM version of the binary (but now afraid to update it :)) that prompt that came up to update the SU binary, how can I get back to that screen in order to attempt the "normal" method of applying the new binary? Surprising that the application prompted me after an upgrade but after downgrading then re-upgrading I can't get back to that SU binary update screen nor do I find it in Settings.

Thanks!
[SuperSU] bedtime_with_the_bear:
To be honest, part of the issue may be due to the way the SGS2 manages it's partitions - it's a little funky compared to most other devices. Anyway, it's good that you recovered and I don't want to beat a dead horse.

There are a few ways I guess you can push it to upgrade. If you're using Titanium Backup, restoring SuperSU's data to a point earlier than the upgrade would probably do it. Alternatively, you could try wiping it's data from TiBu or "Manage Apps".

For a more official method, the Play Store description hints at installing a different su management app, allowing it to install it's own version of su, and then go back to SuperSU, which will now ask to install su again.
[SuperSU] JZ SmartMort:
Very cool, thank you! I'll try one of the few methods but to be honest I tried to find SuperSU in Titanium Backup but it's almost as if it's filtered out by them in the same manner as they filter out their own software from the list. I like the suggestion of installing another SU installer and then downgrade/re-upgrade SuperSU for it to sense the incompatibility.

With my current ROM thought I'll probably need to use mount R/W utility otherwise /system is read-only. Thanks again for the feedback... and the recovery was simple in hind-sight and now could be done in 10 minutes if I screwed it up again :)
[SuperSU] daniello8:
Strange thing:

I have SuperSU 1.30 installed but the app "Multi Mount SD Card" shows me the following message now and then:

"SU 1.27: SUPERSU seems to be too slow to respond, try another version"

How come it doesn't show 1.30 ???

Is this an SU thing or rather an app thing .. and why is response too slow?
[SuperSU] Bright09:
Cant seem to launch from dailer after hidding icon need help thanks. on verizon gs3
[SuperSU] kingvortex:
This is not only the case with the rom you're using. /system is usually (always in my experience) mounted r/o by default.

I'm 100% certain Chainfire knows that /system needs to be mounted r/w to alter files in there and the updater does this. No need for your intervention with other apps :)
[SuperSU] Fireworkfan:
I have a problem, I am trying to unlock bootloader with ADB. I can find my devices 'adb device' and i can also reboot with 'adb reboot'. Also i am sure its rooted because when i typ 'adb root' it says its already rooted. but when i open shell, and typ 'su' NOTHING happens... SuperSU doesnt react.. and in my commandpropt i get 'su' in the first line, and then 'root@android:/ #' again
[SuperSU] My1xT:
the # means that you have root.
[SuperSU] Bakuron:
Lost root. Galaxy Ace. Tried to update binary through 'CWM' option instead of 'normal', now SuperSU doesn't recognise any binary installed. For some reason ES Explorer still has access to system partition and can see all the binaries installed in xbin, and original Superuser app shows v1.27:SUPERSU (0) binary is installed.

I've tried re-rooting via zip, it seems to have installed the old v2.3.1-ef (0) binary, but this hasn't returned root. Re-installed SuperSU and selected "normal" method of updating the binary, and in so doing it asks me to remove SuperUser which I agree to. I've waited a while now and nothings happened.

Edit: Really not sure what to do now. Will I have to backup/format my phone and start again?
[SuperSU] Bakuron:
I didn't get bricked doing what you did, my phone is basically fully operational, except I can't get root back. What exactly does the 'use CWM' option do to the phone? Why did you flash a different kernel?
[SuperSU] JZ SmartMort:
Because RECOVERY/CWM would not come up and spin forever. Once I applied any kernel, some old SiyahKernel which came with CWM in the ODIN image and that finally allowed me to restore a complete ROM with a functional CWM.

For you this will probably be too much/drastic if all you're missing is root. I would try the CWM ZIP file from the OP.

You can also re-apply whatever ROM you're using in CWM which will get the default root functions/executable of that ROM back for you.

Thanks!
[SuperSU] Bakuron:
OK, thankyou for the response. I'm getting the (Status 0) when attempting to install via that method, using CWM v5.0.2.6 - as explained in the OP of the thread. As such I really am at a loss here.

What exactly has happened to lose root when all files are apparently in their correct place?

---------- Post added at 02:58 PM ---------- Previous post was at 02:09 PM ----------

Oh just one other point. The SuperSU app does not specify that the TWRP/CWM is for HTC devices "only", it simply says "If you have a custom recovery (it) can be used to try to install the SU binary. This is recommended for HTC devices." But to be clear I have no issue with the developer here at all, not trolling, I accept full responsibility and only hope for help (don't expect it) rectifying my problem.

---------- Post added at 03:25 PM ---------- Previous post was at 02:58 PM ----------

I used adb shell to remove the superuser.apk, busybox, sh, su files etc and then tried re-rooting via flashing the gingeraceroot.zip app that put the old superuser app back on. This hasn't regained root. So I can only assume that something was changed somewhere else that is way beyond my understanding.
[SuperSU] wheelbot:
Crash

[MENTION=631273]Chainfire[/MENTION]

Keep getting an apps submenu in settings 'unfortunately has stopped' message after last update.

how can i revert back or fix this?

log attached.
[SuperSU] Magissia:
Hello, there's a bug where allowing an app to use SU for 15 mins doesn't work, and the app is allowed to use it only for one action instaed of 15 minutes.

Option to auto trust system apps doesn't work and supersu still askingme for a password.

Using latest google play's version.

Regards
[SuperSU] RamosDevil:
I'm in the same boat. I'm also on the HTC One; I installed TWRP and flashed supersu 1.25, and thought everything was going great, but now and then root will simply disappear. A reboot fixes the problem, but it's such a pain to launch a root app and realize I've got to restart my phone to get it to work (and even then, it will stop working after a period of time). Is there any solution to this? Rebooting into recovery from the SuperSU app just puts me at the default recovery screen... Help!
[SuperSU] rishabhbhatia36:
i fixed, my problem. shortly after my post i was stuck in a bootloop due to flashing a .zip for a power mod. i couldn't find a way to get into recovery so i used the all in one toolkit.

1) connect phone to pc via usb cable

2)click the open in recovery command in the toolkit

3)from the phone i restored a nandroid backup which had no root but was bootloader unlocked

4)too root it again, i used the "perm root" option on the toolkit

it still didn't seem to root so i flashed the SuperSU.zip

and was rooted, no problems since then
[SuperSU] RamosDevil:
Fixed as well - by installing Android Revolution HD 9.3.
[SuperSU] :
Every CM10.1 rom I use always gets SuperSU flashed right over it, right after gapps.

It is just simply better, Open Source or not.
[SuperSU] Samsung Fanboy:
I use agat kernal on my galaxy S2 on GB27 rom and I can't get my binary to update should I try the CWM method that htc uses?

Sent from a V6 Supercharged Galaxy S2
[SuperSU] DBGT_87:
SuperSU do not ask to give permission to applications that required root access like ROM toolbox, AdFree,

there are no application on the APPS list !!

I'm using htc sensation xe (CM10.1)
[SuperSU] Chainfire:
Not in this thread ...
[SuperSU] noomarsil:
I can't flash SuperSU on my HTC Desire X. I have v1.30 but it's still doesn't work and need to be updated. I'm using TWRP Recovery. What am I doing wrong?
[SuperSU] 78Staff:
Same here for Task's AOKP, when dirty flashing SuperSU Pro apk is already installed and I flash SuperSU zip after gapps, along with a few other things like kernel boot screen change, modified phase beam wp, ONB part detect fix, etc...
[SuperSU] :
download the SuperSu.Zip from the OP of this thread.

Reboot to recovery.

Flash it.

Go to Settings -> apps

clear supersu data

try again
[SuperSU] DBGT_87:
the problem from 1st june pyramid cm10.1, not supersu

end
[SuperSU] noomarsil:
When I'm trying to update SuperSU via Google Play it doesn't work (SU binary is not updated). When I flash zip with an update, I still have v.1.25. What's the problem?
[SuperSU] NCtwin:
I can't get an app to show up on supersu, and I'm sure it asked for permission before...
[SuperSU] polobunny:
Usually triggers when that app calls for su. Do whichever action needed to make that pop? What is the app?
[SuperSU] NCtwin:
It's not one that we talk about here, so maybe I'm just asking for it...
[SuperSU] hinxnz:
Black Mart prompts you when you install an app from it :)

Sent from my HTC Sensation
[SuperSU] NCtwin:
Makes sense, but the app now just gives me a connection error and I can't connect to it.

I've tried the update and everything.

Feel free to PM me if you want. I don't want to get anyone(including myself) in trouble.
[SuperSU] ddloco:
I can't turn off the fifteen minutes check box by default I always gotta unchecked it before granting su rights

Sent from my Nexus 4 using Xparent BlueTapatalk 2
[SuperSU] dhampire:
can't move to system

hi. I have pro (paid at google play) because it's cool.

I have a problem.

I update from 1.25 to 1.30, did move to system as apps

tell, but it was back to 1.25..... I tried that many times,

every time are same.

Would you please teach me how.
[SuperSU] dhampire:
Great ! 1.32 have no problem !! Thanks a lot !!
[SuperSU] netban:
Working wonders. Business as usual then :)
[SuperSU] gamepois0n:
Wouldbuy the pro if .99
[SuperSU] kingvortex:
Yeah, and I'd buy a Ferrari if they were £100. :rolleyes:

Why post here to let us know you're cheap? The pro app hardly costs the earth!

Edit: I just checked and I paid £1.77 for it. I couldn't even buy half a pint of beer for that, so extremely cheap to support a great dev :D
[SuperSU] netban:
Just remembered I have pro too haha
[SuperSU] noomarsil:
Still doesn't work on my HTC Desire X. When I tried update this via Google Play I had notification that I should update SU binary, when I tried update via recovery I still have 1.25 version. What the hell is wrong with this app?!
[SuperSU] gamepois0n:
yea, but I don't like to pay more than a dollar for an app
[SuperSU] jgcaap:
In Portugal you can buy a beer for 30 euro cents =p

Sent from my GT-I9100
[SuperSU] kingvortex:
Then you don't get to buy SuperSU pro. No need to post in here telling us you're cheap. I noticed you also did the same in the Greenify thread (more than once as well). Seriously, nobody cares if you don't think an app is worth more than a dollar. Just keep it to yourself and move on.

Damn you! :D A beer is around £3.50 here in a pub (around 4 Euro) :beer::thumbdown:
[SuperSU] :
First off, most quality apps are more than $1. Furthermore, I have purchased nearly all of Chaninfire's apps because they are quality apps.

Do you even have a clue how much time CF puts into it? And your initial root exploit methodology was probably conceived of by him
[SuperSU] dhampire:
Can't be 1.32 again

Hi.

Once success supersu 1.32 was in system. After reboot device, it back to 1.25 again....
[SuperSU] ddloco:
I guess no one other then me wants to have su unchecked the box for 15 minutes by default I asked twice and have been ignored twice

Sent from my Nexus 4 using Xparent BlueTapatalk 2
[SuperSU] :
I would like this feature too...

Its really annoying to have top untick it

Why in the world would I want it timed by default
[SuperSU] kingvortex:
1. It is not checked for me and never has been as far as I can remember.

2. Even if it is checked for you, how often do you install/update a root app for the 1 second it takes to uncheck it to be an issue?
[SuperSU] Chainfire:
Your ROM probably reinstalls root at every boot, it's not uncommon ...

The thing is: replication.

As others have commented, they don't have this problem. Neither do I. I don't know why this is happening for you, and until I do know how this is happening, I can't fix it.

So please explain to me exactly what and when this is happening.

1) Are you using Pro or not ?

2) Does this happen for every app that's *new* to SuperSU, the first time you get the prompt ?

3) Does this happen only for apps you've set to *ask again* / *prompt* ?

4) Any other details that may be relevant. If you want to have this issue fixed, more info is always better

Please pull from your device and attach:

/data/data/eu.chainfire.supersu/files/supersu.cfg

/data/data/eu.chainfire.supersu/shared_prefs/eu.chainfire.supersu_preferences.xml
[SuperSU] polobunny:
Maybe related to the fix permissions script? Cause it borks everything.
[SuperSU] sirxdroid:
I'm wondering the same thing, playing with various ROMs, on some the checkbox is checked by default, on others it is not. Even with the same ROM on two different devices (N4 and GNex) one has it checked, the other does not. What's going on? How can we set a default for the checkbox or at least could someone please clarify what the intended default is supposed to be?
[SuperSU] Bandaid_nyc:
Rooting is so easy YEY!

Just got rooted (breeze) and got my SuperSU. Thank you!:D
[SuperSU] Seelenteufel666:
Hello

Sorry, an error comes in contact with ES File Explorer and SuperSu.

The error comes only since update GT-I9505 on MEA and SuperSu 1.32.

The Error:

SuperSu says "ES File Explorer has been granted SuperSu permissions" and after 1 second : " Sorry test failed. This feature cannot run on your phone''
[SuperSU] My1xT:
you need to be fast then if you have ticked timed grant, this may come because the su request gets timed out when you accept it and ES is rather strict in the point of the su check.

go out of the settings go back and retick (and stay in the time if you set one)
[SuperSU] Seelenteufel666:
Permission is already given. I think it is the consent dadran the query takes too long. Therefore denied ES File Explorer it
[SuperSU] miloytyn:
Do you have full logging enabled? That might cause the test to fail.
[SuperSU] daibaron:
I'm having the same issue posted before, Es File Explorer can't get Root Explorer to work.

I just tried Adam Kernel which solved the problem and now ES File Explorer is able to gain Root access and shows few more options...

It has been confirmed Cf-Root for GS4 is perfectly working with ES File Explorer.

Personally I prefer to use Cf-Root vs Adam's Kernel (That's is a great work !!!) which has a Knox notification issue

any ideas ?
[SuperSU] My1xT:
maybe trying to turn log for ES to access Only/none. ES has some REAL Problems with logging...
[SuperSU] daibaron:
Hi, Ty for helping.

Since Adam's Kernel did the trick with Super SU 1.32, I really doubt this could be SU issue.

just did what you said with no luck... I also tried (for fun) to change language settings, multi-user, Install into system, etc...
[SuperSU] My1xT:
oh, well I had previously problems with ES and sSU and it was the log setting, but I use pro and want to know whats going on...
[SuperSU] stalonn:
İ unlocked my bootlader of htc m7 and then rooted it and supersu ınstalled, i did these all to uninstall system apps lıke trashy facebook and apps etc., how i m gonna uninstall forevere these system apps lıke facebook then?
[SuperSU] bsoplinger:
I'm seeing the same issue as others have reported where the ask again in 15 minutes checkbox is/stays enabled. The only additional information I can provide is that I also get notifications (or perhaps I should say toasts) that the app has been granted superuser status even though I have them turned off. I do not see them for other apps that previously (as in from a previous boot) were granted superuser approval just any newly approved apps.

Sent from my Nexus 7 using Xparent Purple Tapatalk 2
[SuperSU] Chainfire:
The notification thing is often a result of using the "fix permissions" script ... it actually breaks permissions. Did you happen to run that ?
[SuperSU] bsoplinger:
From the way you say "fix permissions" script I tend to think that there's some specific script you have in mind. The only thing that is close is that I flashed a new kernel about a week and a half ago and did a fix permissions while in recovery.

Assuming that permissions have been broken, can they be repaired?

Sent from my Nexus 7 using Xparent Purple Tapatalk 2
[SuperSU] polobunny:
It's exactly that script, which is embedded in recovery and that everyone tells you to run for no reason ever.

Nobody has really found a way to fix it since this script changes a lot of things. It's just easier to titanium backup your apps, wipe everything, reflash your rom and then restore your backup.