yashsingh1/xdaforums huggingface dataset:
[SuperSU] rowdyw:
I upgraded to v2.01 at the same time I upgraded to 4.4.4, so it is probably just some conflict with my ROM. No big deal, I'll just leave the icon as is. All other features seem to be working properly.
[SuperSU] justforreply:
But I want to include in my rom be default app, in a rom I'm doing.
[SuperSU] jwds1978:
[MENTION=631273]Chainfire[/MENTION]

Having updated to SuperSU Pro v2.01, via the Play Store when it was made available, it was working fine. However, just a few minutes ago, root was randomly lost; I'd not ever experienced this with previous versions.

Apps started reporting failed attempts to gain root access. Upon opening SuperSU itself, I was presented with an error that there was no binary and that SuperSU couldn't install it.

At that point, I'd restarted my device. Upon restarting, root Apps were working again and SuperSU was no longer giving the no binary error.

Sent via Tapatalk from my TELUS Samsung Galaxy Note 3 on the Bell network.
[SuperSU] AndroidDeveloperLB:
Just wanted to say thanks for this great app.

It's the best one amongst all others.
[SuperSU] rowdyw:
Tested this out on Purity, PA, and stock KK, all versions 4.4.4, and the same thing happened on all three. If the SuperSU app icon is changed, the icon will not stay on any homescreen after a reboot. It worked fine on 4.4.3, so something in the 4.4.4 update screwed it up.
[SuperSU] jesssiii:
After the play store updated the app, binaries wouldn't update, so I reflashed 2.01 and the app icon disappeared from everywhere. Showed in play as installed but no open button. I was really panicking until I found the SuperSU suddenly in my rom settings. This rom had no superuser in settings at all previously. Is this something new? I'm on Mahdi 4.4.4, using an LG G2 Verizon.
[SuperSU] AAPD11:
I Have note 3 n900 with official 4.4.2 ... I flashed Super SU 2.01 From recovery but now i faced this ERROR!

Please Help me
[SuperSU] bad67boy:
Problems on note 2 gt-n7105

Hallo,

i got a problem on my note 2 gt-n7105, supersu has stopped, this the message that continuously appear on screen.

Actually the firm is a stock 4.4.2. NEE stock base, with root as per yr. procedure.

I follow week all the step described in a different guide (including yours).

I imagine that supersu is the latest version, it's impossible to uninstall from the phone and consequently i can't to reinstall it.

please could you suggest me the right way to solve this problem. Thank you very much in advance.

Regards

marco
[SuperSU] mdiaz33685:
flash v2.00 that should work 4 u guys to fix the issue:D...
[SuperSU] osm0sis:
v2.01 only adds a symlink in /system/bin to /system/etc/install-recovery.sh there's no way it would cause those issues. ;)
[SuperSU] dyval:
AOSP rom has a built-in SuperSu on the settings menu. That can't be updated manually, is it okay to install this apart from the SuperSU in the Rom? Thanks
[SuperSU] bad67boy:
downloading v2.0

Mdiaz Thank you for suggestion, but where i can download the version 2.00, because chaifire's website it's only show the latest V2.01.

I believe that i must have an .tar.md5 extension type, and also must include the root.

Taking in account that actually my note have not the root, but during the V2,1 flash process a red robot appears, so i supposed that all was ok. After the check with root checker (i believe) the response was negative, not root applied in any case.

Other type of file manager have difficult to operate, after lanching, a response is stopped process.

By the way, probably I'll back to stock rom 4.4.2 NEE and waiting for something happen.
[SuperSU] remo0073:
Here it is

http://download.chainfire.eu/450/SuperSU/UPDATE-SuperSU-v2.00.zip

In case you need to try, v1.94 also

The previous stable version

http://download.chainfire.eu/396/SuperSU/
[SuperSU] bad67boy:
Thanks remo, this will be unzipped and the flashed by odin? or please suggest me the right way.
[SuperSU] Rinoceros:
Flash through recovery, don't unpack the zip.

Just copy the zip on the internal memory and restart your device into recovery.

Do an install in the recovery by pointing the install to the zip file and here you go.
[SuperSU] bad67boy:
Ok thakns to you rino.......i don't have a recovery...this is the problem and due to this i can't make something, i had downloaded a twrp, i imagine that this file must be falshed or installed on note before to install supersu (any version I believe) flashing via odin, it's right? thanks
[SuperSU] Rinoceros:
I don't know for which device you want to use it.

You have three devices listed in your sig.

For each device it might be different to flash the recovery. Go to the thread of your device and look at the howto ot install the recovery for your device (i recommend TWRP).
[SuperSU] remo0073:
Theoretically, yes

BTW It' s better to ask this questions in Note section
[SuperSU] :
Yup, no probs...

Just flash the latest SuperSU zip from recovery and you're good to go...

If you've got SuperSU installed this will update the SuperSU binaries...

Else if you've got any other Superuser app in your ROM, SuperSU will take over by default... :good:

---------- Post added at 08:59 PM ---------- Previous post was at 08:55 PM ----------

Yup, flashing a custom recovery (CWM/TWRP/others) is the easiest way to obtain root...

You need to flash the custom recovery and then install the SuperSU zip from recovery...

I think you're talking about Note and AFAIK it has got a CWM build...

You can either flash the recovery through Odin/Heimdall and then you're good to go... :good:

Any more questions???

---------- Post added at 09:12 PM ---------- Previous post was at 08:59 PM ----------

[MENTION=929534]bad67boy[/MENTION] Well I've got the goodies for you...

Judging by your signature and posts, I think you're talking about the Samsung NOTE II LTE... Am I correct?

Well these are the latest official custom recoveries for your device....

CWM Touch> http://download2.clockworkmod.com/recoveries/recovery-clockwork-touch-6.0.4.1-t0lte.img

TWRP> http://goo.im/devs/OpenRecovery/t0lte/openrecovery-twrp-2.7.2.1-t0lteatt.img

I hope you're talking about the international LTE version?

Well that's a hell lot of a help there, now where's my cookie??? ;)

---------- Post added at 09:19 PM ---------- Previous post was at 09:12 PM ----------

Remove the Superuser app by deleting the apk from /system/apps, else, delete them from /data/app...

After that flash the SuperSU app in your build and you're good to go... :good:

SuperSU will be the default Superuser app anyway but this method will remove traces of the Superuser app...

Happy rom building dev... ;)

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

Seeing that all of you guys are using Sammy Note :D I think the best bet would be to flash the last SuperSU version which worked properly on your devices... in this case v2.00...

Hope this helps... :good:
[SuperSU] 78Staff:
Interesting, the rom i use has superuser baked in, but I flash SuperSU along with a different kernel before I even boot in to the rom. The settings menu does have SuperUser entry in Settings, would be cool if I could substitute SuperSU there as well similar to the screenshot a few posts back...
[SuperSU] 09eric09:
What is the best way to update?
[SuperSU] :
There's no best way...

Both are equally good...

You can either flash through recovery or update from Play Store...

It's your take... :good:
[SuperSU] 09eric09:
Thanks. One more thing, I updated from the store, but i still get the message about updating the binary when I open the app itself, why is that? Is it because AOSP has SuperSU built in?
[SuperSU] :
Pressing the Thanks button under my post instead of mentioning it would be highly appreciated... ;)

FYI the Thanks button is there to prevent thanks posts in thread... :good:
[SuperSU] 09eric09:
I wasn't done editing my post.
[SuperSU] :
Flash the SuperSU zip from recovery...

Some devices are facing issues with the v2.01 update...

Browse some pages back on this thread to be enlightened.... :angel:

Anyway here's v2.00 for you... http://download.chainfire.eu/450/SuperSU/

If that doesn't work, try v1.94.... http://download.chainfire.eu/396/SuperSU/

Don't forget to flash this zip file through your recovery...

Hope this helps... :good:

And press the Thanks button if I helped ya...
[SuperSU] 09eric09:
But is that necessary if my rom already has it built in?
[SuperSU] :
Since you are getting the binary update error, it is necessary...

This will revert your SuperSU to a working version... :good:
[SuperSU] Strephon Alkhalikoi:
My ancient Gingerbread device (Dell Streak) doesn't like anything later than 1.94. I've done some limited testing with 2.00/2.01, and my uneducated guess is that there's an issue with the apk itself. I've installed the binary through recovery and double checked to be sure it was the version for 2.00/2.01, then ran SuperSU. I get prompted to update the binary even though the binary IS updated. In fact, I can still approve or deny root requests, but cannot access any settings in the app itself because of the "binary update block". Unlike some of the users here who have this issue, I also cannot delete my data through SuperSU's options in Settings > Apps. This last thing is what convinced me that the apk was bugged, because the button for clearing data acts as if I had already pressed it, however I never pressed it and naturally the data hasn't cleared. Logcat reveals nothing out of the ordinary or I would have provided one by now, though if Chainfire needs it he'll naturally get it.

For the time being, I and the few users of my device have disabled automatic updates for SuperSU until Chainfire has the time or inclination to address the issue. Since I baked 1,94 into the ROM I use, it's easy enough to uninstall the updates if they don't work. The reality here, at least from what I've been seeing, is that it may be difficult, if not impossible to support Gingerbread while trying to implement the changes Google made to KitKat and the forthcoming Android L. Thus, if he is able to fix things, then that's great. But I am not expecting him to bend over backwards for me, not when the state of the art is KitKat and L.

P.S. Doing a factory reset didn't help the issue. The binary update block still appears.
[SuperSU] shdwmyst:
What am I missing?

I have rooted phones for years and never had a problem until now.

I rooted a Sprint S3 a few weeks ago, installed the latest SuperSU to disable Know and it worked perfect.

Now I am trying to root a brand new S3 - KOT49H.L710VPUDND8

I OTA it to the latest ND8 4.4.2

No matter what I do or try, it will not root.

Prepped:

- USB debugging enabled

- Correct drivers

- Cable that came with phone

Tried:

1. CF Auto-Root multiple times

It gets to the red android screen, finished very quickly,

reboots and I have SuperSU. It is not rooted so I try

the latest market version but I get this error when I open it:

"There is no SU binay installed and SuperSu can not install it..."

2. I tried Odin with Philz recovery - philz_touch_6.15.4-d2spr.tar.md5

by putting it in PDA. It still has the standard recovery installed.

3. Tried using the standard recovery to flash UPDATE-SuperSU-v2.00.zip (read 2.01 could have issues).

4. Tried SRS Root, said it was successful but SuperSU did not appear and still no root.

-------------------------

Have any of you had this kind of issue trying to root a phone?

If so, what did you do to fix it?

I am still working on it but would love some feedback.

Thanks
[SuperSU] rowdyw:
Have you tried rooting with Towel Root first, then downloading SuperSU after you have root?
[SuperSU] shdwmyst:
Towel Root worked, thanks!

I came across that one earlier but thought it was only for AT&T/Verizon.

Glad that fixed it.
[SuperSU] rowdyw:
No problem, just make sure you installed SuperSU after you did the Towel Root, otherwise any app can gain root access without asking permission first. :good:
[SuperSU] kishd:
I have an oppo find 7. For some hidden reason titanium backup does not work with SuperSu but works fine with superuser in the stable 4.3 firmware from oppo. Even root explorer does not read the external card consistently but superuser works fine. Not complaining but would like to understand why.
[SuperSU] :
That's the routine of software evolution.... New versions break compatibility with old versions...

If you see the changelogs, v1.97 onwards SuperSU had numerous workarounds for the new commits in AOSP...

Good to see that you've accepted the OP may not have the time to fix everything....

If everyone had this mindset, the XDA would have been a much better place....

Posts like this deserve RESPECT... :good:

---------- Post added at 10:11 AM ---------- Previous post was at 10:09 AM ----------

Working for me...

Which version of SuperSU are you using???

Install the latest version zip from your custom recovery...

Btw, root explorer not reading the external card has to do with the app itself rather than SuperSU...
[SuperSU] kishd:
[MENTION=5879883]g33kparineeti[/MENTION]

SuperSu works with oppo beta firmware but not with their stable releases. However koush's superuser works with both. The problem is that the phone is rooted but root apps don't seem to have full root access.
[SuperSU] Frank Westlake:
They can all be supported by one APK but it is a lot of work trying to keep it that way.

Maybe Chainfire will start publishing a list of which Android versions were last supported by which SuperSU versions. This list begins:

Gingerbread 1.94

The problem is that if a fix becomes necessary for Gingerbread then 1.94 would have to be redesignated somehow so that it would not be confused with the version for other Androids; something like 1.94-gb1, or GB1.00. There would be two sets of code to maintain but I think that would be easier than continueing to try to make everything work with one APK, because the other sets of code would only need emergency repairs.

ADDED

Redesignating the the APK will also help to keep people from installing versions they don't need and subsequently adding confusion to this forum.

Frank
[SuperSU] bad67boy:
Hi Rino....i'm using note 2 lte, with nordic european firm NEE, thank you for yr. support

---------- Post added at 11:52 AM ---------- Previous post was at 11:47 AM ----------

g33kparineeti you right, i'm using the note 2 LTE european, thanks
[SuperSU] Strephon Alkhalikoi:
As you may or may not know, the Play Store allows a developer to offer different versions of an app depending on the API version. This is how Google can push an updated copy of Maps to my ICS tablet while leaving the Gingerbread device untouched. I do believe Chainfire should focus on ICS and up for future versions of SuperSU, and NOT worry about Gingerbread and below. The changes Google are making are extensive enough that Gingerbread will suffer, and that's not a bad thing. The most Gingerbread users should see is an updated binary once in a while, if necessary.

No matter how it's done, people are still going to attempt to install a version that doesn't work for the device in question. They expect that the developer should cater to them and make the app work for their device regardless of its age, then come onto the thread and post their tales of woe. That's not realistic, but not unexpected, because I don't believe people who do stuff like this truly respect what the developer does.
[SuperSU] Chainfire:
Re: Gingerbread

Gingerbread is still officially supported by SuperSU even with 2.01. If you have some specific issues, let me know in as much detail as possible. Note that my GB test device is an ancient Galaxy S. I do not specifically test Gingerbread every update, so it may well be something broke somewhere.

Re: Oppo official firmwares

Without further information, I don't know what the problem could be. I do not have any Oppo devices, so I can't really test on them.

Re: Samsung 4.4.2 devices

On my list to do some further testing
[SuperSU] Frank Westlake:
I did not know because I have read Google's privacy statement and I choose not to accept it.

I tried to avoid that statement by saying "help to keep people from installing versions they don't need"; meaning that it would reduce the problem -- not eliminate it.

Frank
[SuperSU] Strephon Alkhalikoi:
I know it's still officially supported and I do appreciate the effort you put into supporting Gingerbread. I'm simply saying that if for some reason it can't be fixed then I'm ok with that. However, I do think that the things Google is adding to KitKat and L are what you should be focusing on, rather than Gingerbread. I guess all I'm trying to say is that compared to getting things working properly on ICS and above, I believe working on Gingerbread issues should have a relatively low priority.

My issues I had mentioned several posts back, but to recap, those issues are.

The app wants to update the binary. Pressing OK and trying to update through the normal method results in a failure to update the binary. Attempting to update the binary using the flashable zip works in that the binary overwrites the existing su binary, however after rebooting and running the app, it STILL requests to update the binary. Root functions work and it's possible to approve or deny new apps that require root access, which is what leads me to the conclusion that the app itself is somehow bugged on Gingerbread.

It's impossible to delete SuperSU's app data through Settings > Apps. The other three main buttons all appear to be normal, though I don't move apps to my MicroSD so I haven't tested that. The clear data button appears to be in a permanently disabled state.

On ICS, none of this occurs. My tablet updated to 2.01 without a problem. I had run a logcat the first time this occurred, but saw no warnings or errors related to SuperSU when I did it. I may not be remembering correctly however, so a little bit later I will update SuperSU and run a logcat, since you will likely need or want it.
[SuperSU] kishd:
[MENTION=631273]Chainfire[/MENTION] I have an Oppo. Is there anything I can do to help pinpoint the problem?
[SuperSU] :
Yup, post the logcats of your error.
[SuperSU] CynoMan:
[MENTION=631273]Chainfire[/MENTION] Can a notification tone or vibration be paired up with the superuser access Popup? Sometimes, while installing apps, I get distracted and don't notice the prompt, thereby miss authorizing permission (don't like setting that more than 10 sec).

Kindly, please consider[emoji4]
[SuperSU] Zen Arcade:
Speaking of Samsung 4.4.2 devices, I'm attempting to include SuperSU 2.00 in a stock firmware for the i317 (AT&T Note 2) - using the stock (SELinux enforcing) kernel. ATT doesn't release full firmwares for this device, so I've been turning OTAs into Odin and recovery CWM/TWRP packages. Rooting has proven to be a challenge with the UCUCNE5 4.4.2 release. At present, the only option has been to install the firmware, boot AOS, then boot recovery to install SuperSU manually after the fact.

My updater script is setting permissions and file contexts appropriately. I have noted that running "su --install" from updater-script produces a different result than from update-binary - closer to the final result it seems(See attached).

Here are the current steps taken to obtain root (manual process):

Starting in recovery from a clean UCUCNE5 4.4.2 firmware install (after factory reset, /system formatted) - Neither option completes with root established (with either my updater-script option or installing UPDATE-SuperSU-v2.00.zip afterward). Same result after variable trials:

- First boot of AOS: SU binary not found

- After booting recovery, reflashing UPDATE-SuperSU-v2.00.zip, and a second boot of phone OS: SU binary is found

- (But Knox disable hangs).. After another reboot, Knox can be disabled and completes promptly

- After this root works as expected, but I have noted one app FCs at startup - WiFi Direct share - fwiw

Any suggestions on how to fix the install would be appreciated. If testing is needed I'm available.

As a side note, this issue goes away with a custom kernel that has SELinux set to permissive or disabled.
[SuperSU] Dryblow:
SuperSU is closed source?
[SuperSU] FlanjeUK:
Yup :)
[SuperSU] Taomyn:
I noticed a small issue with the alternate SuperSU launcher icons - if I choose anything but the default emblem icon, I still prefer the original # icon myself, then place it on my home screen (in or out of a folder), the icon is removed at next reboot of the phone.

Does anyone else have this issue? None of my other apps that are on the home screens behave like this.

This is on my Nexus 5 v4.4.4, stock but rooted and Xposed 2.6.1 installed.
[SuperSU] 78Staff:
When I change the icon it jumps to the primary app drawer, is all I have noticed. I just move it back to the drawer where i normally keep it, and it stays put. This is with Nova Launcher - other launchers my react differently, of course.
[SuperSU] Taomyn:
So it does sound like something is going on, and that the stock Google Launcher isn't liking it.
[SuperSU] 78Staff:
It's expected behavior, I would think - when the launcher sees the icon change, it treats it as a new app, thus dropping it back to the default app drawer - at least that's how Nova seems to be handling it - and had for some time. So yeah seems like Google Launcher is getting confused with the change...
[SuperSU] a g bell:
Hi,don't know if it would be possible but will there be a fix for this ,not working on android L port for nexus 4 ?Thanks☺

http://xdaforums.com/showthread.php?t=2807446

[L][5.0][PORT] Android L pv-79 Developer preview for Nexus 4 [BETA]
[SuperSU] Chainfire:
FYI, I just tested this, and it works without issue on the original Galaxy S running Gingerbread. Whatever the issue is, it is not specific to Gingerbread, but rather specific to the Gingerbread version running on your specific device.

Perhaps you can try the "full unroot" feature from settings first, then reinstall via ZIP ?
[SuperSU] Chainfire:
Tested the very latest Samsung firmwares on a couple of devices without issue.
[SuperSU] blaz1nr:
I ran into this problem rooting i537 ota's. The issue comes from binary being detected on boot. Installing su zip before first boot worked for us. I f you are still having issues, Let me know. There is a few more solutions I can give you via pm. altering the Ota updater to not check or update knox and then remove it all works great also.
[SuperSU] leomd333:
Past few times I've tried to convert SuperSu to a /system app it just tries to install forever. (On my LG G3). This time I have just left it as a /data app. Is there any downsides of leaving it in /data, apart from the obvious fact it can be easily uninstalled? Thanks!
[SuperSU] Strephon Alkhalikoi:
Logcats revealed nothing wrong, so no debug notices, warnings, or error messages. Thus why I haven't posted one.

I already tried the full unroot feature. I also did a test flash of my ROM (CyanogenMod 7.2 RC0. A final version was never made for the Dell Streak.) with SuperSU 2.00 and accompanying binary embedded in the flashable zip and the app still asks to update the binary. You may not recall, but my device had problems with 1.74, and you were able to solve them. The root cause I believe stems from the fact I have a 2GB MicroSD card that the user cannot replace within the casing, as well as the MicroSD card slot that is user accessible.

In other words, two MicroSD cards. And while you were able to fix things the last time around, this time around my device's odd configuration is a showstopper. Like I said, I'm ok with that, and I appreciate you taking a look at things. But, things like this happen when the device isn't terribly popular.

I do have one last question: is it possible to use the 1.94 app with the 2.01 binary, or do both have to match?
[SuperSU] Chainfire:
It needs to be in /system for multi-user capabilities as well, but I think that's it, really.

They both have to match.

Can you paste the output of "printenv" both from a normal adb shell, as well as su inside an adb shell ?