yashsingh1/xdaforums huggingface dataset:
[SuperSU] H3llstorm:
It's not one app.

---------- Post added at 06:30 PM ---------- Previous post was at 06:23 PM ----------

I flashed through TWRP. Should I try uninstalling & re-installing through the Play Store?
[SuperSU] boyheadkick:
go ahead, there's an option to reinstall in the cleanup section in settings tab..of course i'd advise you to backup first ;)
[SuperSU] Solace50:
using chainsSU 1.86 after toggling off some options "notification" and granting permissions instead of prompting for access the app would not enforce these values until you disabled/re-enabled SU. i performed no reinstall i just disabled/re-enabled SU and it remedied the situation. i assume the options should be applied when toggled and not require to perform that step.

this was on goldeneye 18.2/kt latest kernel for a i337m.
[SuperSU] Chainfire:
I've tried my dev build (will be released today or tomorrow) on both the CMInstaller which installs CM 10.2 and the CM 11 nightlies and it seems to work fine for me in both cases, installing the APK and just letting it update the binaries ...

Let me know if the problem persists with the upcoming update (v1.90 or so)
[SuperSU] elxufas:
Great:good:
[SuperSU] H3llstorm:
Do you recommend installing through TWRP or the Google Play Store?

In the settings tab, do you think the "Install SuperSU into /system" or "Reinstall (cleanup for reinstallation from Google Play)" options will help?

Thanks.
[SuperSU] connex91:
Hi all

I have been searching for hours and trying several options to root 4.3 on my s3 with no luck.

My system: SGH-I747M Canada Fido, SuperSU Pro, Mobile Odin Pro

Upgraded from rooted 4.1.2 to 4.3 with stock firmware using Odin 3.07.

Rooted using CF Auto Root, Ended with success

Installed Root checker: device does not have proper root access

Try to open SuperSU (installed as system app): Unfortunately, SuperSU has stopped followed by Security notice: unauthorised access to a secured area has been blocked.

Downloaded the latest SuperSU apk, tried to install, error: App not installed with no further info.

I don't know what else to do to root... any help would be greatly appreciated.
[SuperSU] Frank Westlake:
Do you have some other way to check root access? A terminal, a file explorer? Verify with something else that Root Checker is not wrong. If it is not wrong then try rooting a few more times. I'm not an S3 user so I might be way off track.

Frank

SGH-I717(AoCP6.4), SM-N900V/MI9(dlV), XDA Premium
[SuperSU] detdett:
Are you sure it's rooted? Did you enable usb debugging?
[SuperSU] connex91:
Hey guys,

USB debugging was enabled

I have Titanium Backup Pro and Triangle Away that both require root access..

Triangle Away hangs at Loading...

Titanium Backup fails to open with the error: Sorry I could not acquire root privileges. Please verify that your ROM is rooted, and try again. This attempt was made using /system/xbin/su command.
[SuperSU] detdett:
Which model is your s3? Which link did you use for cf auto root
[SuperSU] Lord_Flaya:
Had this happen to me as well a few times. For me the problem was solved by clearing tb data, flashing latest su and poof problem solved.
[SuperSU] :
+1
[SuperSU] Frank Westlake:
Maybe start by clearing data and cache only on SuperSU using the application manager, reboot; if that fails flash SuperSU, boot; if that fails then do what the quote above says.

Hope you don't get a poof though.

Frank

SGH-I717(AoCP6.4), SM-N900V/MI9(dlV), XDA Premium
[SuperSU] Frank Westlake:
SuperSU

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

Samsung KNOX has been detected. This

might limit root capabilities and cause

annoying popups. Try to disable KNOX?

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

I get that dialog every time I launch SuperSU to check logs. There isn't any switch for it in 'settings' so I guess I either have to live with it or do what it asks. Is there a discussion somewhere about Knox so I can decide if it will benefit me to let SuperSU try to disable it?

Frank

SGH-I717(AoCP6.4), SM-N900V/MI9(dlV), XDA Premium
[SuperSU] engloa:
Here's one from the s4 thread

http://xdaforums.com/showthread.php?t=2470635
[SuperSU] Frank Westlake:
Thank you. It doesn't discuss the pros and cons of disabling Knox though. I'm guessing that with an unlocked bootloader Knox can cause difficulties for people installing some things, so I don't know if that is applicable to locked bootloader devices.

This is not the place to be discussing Knox so please consider this a request to make the dialog appear only on the first run of SuperSU.

Frank

SGH-I717(AoCP6.4), SM-N900V/MI9(dlV), XDA Premium
[SuperSU] ValenteL:
The same to me.

On Note3 N9005 KitKat I flash always 1.89. On another Knox devices I flash 1.80 and invalidate the update from SuperSU on Play Store (for now).

Forgot 1.86, I have issues also.

Sorry [MENTION=631273]Chainfire[/MENTION]. Please, include 1.89 on Play Store.

EDIT: Updated SuperSU to 1.91 today 20.01.2014
[SuperSU] connex91:
Here is my model ID and the versions of the tools I used for the root

S3 Model is SGH-I747M Canada Fido

CF Auto Root link: http://download.chainfire.eu/269/CF-Root/CF-Auto-Root/CF-Auto-Root-d2can-d2vl-sghi747m.zip

Odin version used: 3.07

SuperSU 1.89: http://download.chainfire.eu/supersu

Thanks for your suggestions guys.

Cleared data and cache in Application Manager for SuperSU, rebooted, no luck

Odin Rooted again using C-F Auto Root

Odin flashed TRWP

TRWP flashed SuperSU 1.89

Still no poof... :D

Everything seems to point to the C-F Auto Root not being done properly; FYI I have rooted the same S3 countless times on the same PC.

What did I do wrong?
[SuperSU] Chainfire:
Unless you disable KNOX popups using that dialog, its no use running SuperSU, as root calls may randomly fail. So no, I will not be removing it, and it will keep nagging you until you give it what it wants.
[SuperSU] Chainfire:
1.91 released

v1.91 has been uploaded to the Play Store - should start updating within a few hours. The ZIP has already been updated, link in the first post. Changelogs are also on the first page of the thread.
[SuperSU] Frank Westlake:
OK, thanks. I have not had any failures since I rooted the device and began using your application back in November; perhaps you are better than you thought.

If I permit SuperSU to do this how would I reverse it?
[SuperSU] Chainfire:
Whether or not it blocks things depends on the exact firmware version. Perhaps you should stop fighting SuperSU and let it do its thing.
[SuperSU] Bill Gamble:
[MENTION=631273]Chainfire[/MENTION] I see v1.91 is available...what's new (I didn't see any discussion about it on G+)?
[SuperSU] Chainfire:
Seriously?
[SuperSU] AlxMAX:
Read the third message of this thread.
[SuperSU] Bill Gamble:
Oops. Sorry. Thanks.
[SuperSU] Frank Westlake:
Thanks, but if I don't need to disable Knox, I won't.

Frank

SGH-I717(AoCP6.4), SM-N900V/MI9(dlV), XDA Premium
[SuperSU] Chainfire:
That's fine by me, but then don't come here complaining about the popup (or stuff not working, in the future) :)
[SuperSU] TheCreat:
Small bugreport: I've just re-flashed my SGS2 with latest OmniRom Nightly and it seems to be new that SuperSU asks on first launch if it should install the backup script (which I appreciate). If you say 'Yes' the UI isn't updated though. In the 'Settings' tab I still saw the option to install the backup script. I didn't try to do so, but instead exited and restarted SuperSU (via the new and handy system settings integration), now the settings correctly said that the script is 'already installed'. So I guess the UI just isn't refreshed after hitting 'Yes' on the first-launch question about the script?
[SuperSU] MikeRL100:
Seriously, Chainfire. You've done big favors for the whole Android world again. You defeat Samsung's stupid enterprise security for a good cause and update your apps before I often even hear of a firmware release. Users should be grateful. You have also done developers a massive favor by giving everyone a head's up on that issue with that AOSP commit. Stuff is easy to overlook. I know root pays your bills but damn you do a lot of volunteering. Someone else on XDA pushed me a bit months back and I dumped CM for OmniROM. Glad you're leading it. I always thought you just developed a proprietary Superuser management application, but honestly you've done more for open source than I can imagine most others doing. Thanks for all your help. P.S. I donated to Omni a while back. Hoping that assists you guys with getting new devices. I donated $50. No, I didn't come here to be thanked. $50 ain't **** compared to all you've done for the community. I've had the pro version of SuperSu for ages. And I'm also helping report bugs with Omni. I'm going to get even more involved and try to track down some of my bugs and help test patches. I can get help getting started more so on IRC. Anyhow, you've done it again. I had no clue you'd hall ass past Samsung and Google and now CM. Serves them right for abusing the open nature of Android and the community. With my money and work put into Omni, hopefully others will follow. Omni currently is buggy, but we're just getting started. Still stabler than CM's stable builds. LOL. The future is bright.:D
[SuperSU] SveninFla:
As a Paid Member of your app SuperSu, I must take a moment to thank you. Never had a problem at all.
[SuperSU] mervluk:
Sorry if the question is unnecessary, but my Xperia Z rooted stock 4.3 rom has the necessary SuperSu fix for v1.86 to maintain root. Could the update to 1.91 adversely affect this? For the time being I have cancelled auto-update, just in case.
[SuperSU] kingvortex:
I'm running 4.3 stock on my C6603 and I'm unaware of any fix that is required for SuperSu. I've been on 1.86 downloaded directly from Chainfire's site for weeks with no issues and updated to 1.91 as soon as it was available and everything is working as it should be.
[SuperSU] david72262:
Disregard fixed it.

After updating thru play store today binaries won't install. On aocp7 kit kat based off of cm11.
[SuperSU] iXNyNe:
I am running omni 1-19 nightly for i777 and I had 1.89 installed and I updated to 1.91 via the play store and the supersu icon is no longer in my app drawer. I rebooted my phone, same issue. I downloaded the 1.91 flashable zip and installed it and still have the same issue. Using nova launcher I was able to create a shortcut to the main window activity, but still no icon in the drawer.
[SuperSU] david72262:
Go into settings and clean for new install from play store then reinstall from play store worked for me 10 min ago you may also need to change your icon you may have the hidden one selected
[SuperSU] iXNyNe:
No dice

I tried what you said and then I tried the full unroot and reflashed the zip and still have the issue. The icon and theme options are actually completely missing from the settings. I'll try the play store install one more time and then try switching back to 1.89
[SuperSU] Tunasty:
I had no problems in updating to 1.91 via play store. Binaries updated without any hiccups.

S4 is Poppin!
[SuperSU] Vlad Paul:
I received update from play store, v1.91. Working fine. I selected Normal when app asked me how to update binary. Its ok or i must select TWRP/CWM? I have twrp recovery on my nexus 4. Thank you!

Tapatalk via Nexus⁴
[SuperSU] iXNyNe:
yeah, i'm in some odd place here...

i tried reflashing 1.89 and i have the same issue that i started having in 1.91

I had never had this issue prior to 1.91 (today) - by this i mean i've never had issues with 1.89 or below

it seems like the icon is hidden, and the icon and theme options are missing from settings

i have done the full unroot and even tried completely wiping /system and reflashing my rom and gapps and supersu

so im guessing the issue must be something in /data but i cant clear data for the app from within system settings im going to try my file manager going through root and removing supersu data from /data/data/

everything else seems to be working, im prompted for root for new apps, existing apps can still use root, and but the icon does not appear in my drawer and once opening the app via an activity shortcut the theme options are missing.
[SuperSU] TheCreat:
Latest nightlies for Omni should integrate SuperSU into the settings. Scroll down in the system settings, the SuperSU config should be a little above the "About Phone" entry at the bottom. When it's integrated into system settings the icon in the app drawer is hidden.
[SuperSU] iXNyNe:
thank you!

i feel really dumb for not finding that....
[SuperSU] sgs505:
[MENTION=631273]Chainfire[/MENTION] thanks a lot +

Just wanted to report this issue

My gf n4 wasn't able to boot after her update on playstore 1,91

Mine was OK...

The only difference between both was that I set selinux to permissive on mine

I wasn't able to save her data had to reflash the whole stock...

Hope it could help you... Or some other couple :)
[SuperSU] zman519:
I always flash the zip idk it's just the way I like to do an update.

But any how I'm on AOCP 7 (4.4.2) Samsung s3 (710 / D2spr) with SuperSU 1.86. Any other users of aocp 7 having problems with updating to 1.91? Maybe I'll wait a day out two before I update, I could always do a nandroid.

@ Chainfire. Did i see you in a Nvidia promo/demo video about the Tegra K1? I remember watching an xda-tv report by azrienoch at a xda devcon a wile back and he was interviewing you (or you where doing a presentation idr witch) and you said you worked at Nvidia.

whoever came up with the crop circle thing is a genius that was so cool I saw that story on the Drudge report, and I was like I don't think this is really a ET its another fake one RoFL

BTW a BIG thanks for not only for your apps and code but I like reading your writings also. I'm going into I.S. I studied Electronics Engineering at one point also, but that's a whole another story for another time and place, take care:beer::):thumbup::beer:

OK sorry if I got way Off topic:eek:

Sent from a thing running on Electrons
[SuperSU] GravuTrad:
New version 1.91 impossible to install on the default emplacement on s4 gt-i9505 mga firmware
[SuperSU] Chainfire:
If you are having issues, please detail those issues.

I don't work at Nvidia, that's [MENTION=3869474]agrabren[/MENTION]

How is it impossible to install ? Does a person of the vertically challenged persuasion fall from the sky kicking the phone out of your hands every time you try ? Unless details are provided, there is nothing I can do.
[SuperSU] :
[MENTION=631273]Chainfire[/MENTION] I am trying to install newest update. Every time, a person of the vertically challenged persuasion falls from the sky, and kicks the phone out of my hands. Please help!

Sent from Nexus 5 on Slimkat
[SuperSU] zman519:
I'm not having any problems I didn't update yet, I saw that post about aocp and just wanted to see if any other users of that ROM had problems. Iam Just kinda busy to night to be nandroiding and troubleshooting.

Sent from a thing running on Electrons
[SuperSU] JulianJenner:
1.91 working without problems on LG L9 P760 with ported BeanStalk 4.4.215. Thank You so much!

Tapatalk-kal küldve az én LG-P760-el
[SuperSU] vicw:
I'm not sure if it has anything to do with SuperSU, but right after I updated to 1.9.1, and let it boot to Recovery, and it auto booted back to system, I had at least 4 apps disappear. The icons still showed, but the apps were gone. I was able to restore them with Titanium Backup. Very strange. I never have had that happen before.
[SuperSU] tclocki:
Hi guys, so my girlfriend has the latest omega rom on her s3 i9300. I just flashed it yesterday. She accidentally had cwm fix supersu without her asking me. I think she might have lost root? I havent looked at her phone yet but when she clicks on the supersu app she is saying that she's getting a message indicating that there are no su binaries installed.

What do I do? I need her to have root access cos of some of the apps we both use... Thanks in advance guys, and sorry for being noob on this
[SuperSU] Pons:
Flash the zip in the OP.
[SuperSU] makix13:
Updated PlayStore way without any issue!

S2 JB 4.1.2 Stock ROM ES I9100XWLSD - ROOT SuperSU
[SuperSU] sebadamus:
Updatin to 1.91 then cant install binaries

Hello,

I used to have 1.86 installed and working on my XT1058 moto x, 4.2.2... but after updating 1.91 now seems not possible to update binaries.

Strange thing for me is that I have installed 1.91 supersu, with binaries outdated and still being able to run apps with root priviledges.

Might it be some su wrong permision set? I can try to change them by terminal if have some directions :)

Thanks
[SuperSU] Lord_Flaya:
+1

Since installing 1.91 I got message about binaries update. Tried and failed and the message never show again. Reinstalled and same thing happen. Is there a way to manually trigger update, let's say terminal command or in-app?
[SuperSU] simonsalo:
Are you working on version for galaxy s4 i9506 snapdragon 800 that roots without tripping the Knox flag to 1? I imagine the new S5 will have the same issue?
[SuperSU] johnqjx:
SuperSU always needing to update binary

Hi I'd like to ask if there is an easy method to update the binary automatically? It seems that everytime there is a new binary, SuperSU doesn't work and it asks me to update the binary.

It then goes to offer me Normal or Via TWRP/CWM. Normal doesn't work and Via TWRP/CWM just boots up recovery mode. Thanks!
[SuperSU] kingvortex:
Download the update zip from the link in the first post and flash it via recovery.
[SuperSU] connex91:
Upgraded to PlayStore version 1.91 of SuperSu and everything is back in order. Thanks guys!
[SuperSU] Cookie Ninja:
Haha!

Thanks! You, sir, have made my day!

Dead Cookies leave no trails...
[SuperSU] GravuTrad:
Sorry but i don't know what to give more than i've given...what do you need?....
[SuperSU] sebadamus:
Is there any other way without flash recovery? because I havent unlocked my boot yet (motorola has some issues to get my code, unless I try some kind of hack to unlock it then) so I would need a way to update the binaries using the terminal... is it possible?

Thanks!
[SuperSU] kingvortex:
I have no idea, as I originally flashed SuperSU via recovery and just update via the Play store. Never had a problem updating binaries on any of the devices I've used it on.

What do you expect anyone to say? If you updated via normal mode, the binary update succeeded and you have root access, why would you need to do anything differently?
[SuperSU] Frank Westlake:
But your device is rooted!?

Extract the zip archive. Read the script at 'META-INF/com/google/android/update-binary' and do all that it says. I haven't looked at 1.91 yet but essentially you'll copy all the other files from the archive to their identical locations on your device, unless the script alters that for some reason. Then you'll need to set all the file permissions as the script says, which is normally the same as other files at the destination directory. The script might do other things so read it carefully.

Then reboot.

Frank

SGH-I717(AoCP6.4), SM-N900V/MI9(dlV), XDA Premium
[SuperSU] Vlad Paul:
[MENTION=2452820]kingvortex[/MENTION]

What do you expect anyone to say? If you updated via normal mode, the binary update succeeded and you have root access, why would you need to do anything differently?

Thank you!

Tapatalk via Nexus⁴
[SuperSU] GravuTrad:
I see in looking the software that he stayed on 1.86 version, why all this? no update possible cause it doesn't want to take the default emplacement....

---------- Post added at 11:32 PM ---------- Previous post was at 11:29 PM ----------

and my phone seems to not seen my sdcard anymore...:(
[SuperSU] Frank Westlake:
It seems that there is a language difference here. By "he" you mean the device?

You started with 1.86, you booted into Recovery, you selected the UPDATE of 1.91, the update installed, the device rebooted, and now you still have the old 1.86?

Also your sdcard did not mount? Is it still not mounted after rebooting again? The removable sdcard or the internal sdcard?

If the update failed try again and watch the text output. It probably goes too fast so maybe it writes to a log file -- does anyone know? Maybe the second time will work.

Frank

SGH-I717(AoCP6.4), SM-N900V/MI9(dlV), XDA Premium
[SuperSU] GldRush98:
Hey Chainfire,

I flashed 1.91 yesterday and at some point today daemonsu locked up and drained my battery.
[SuperSU] Frank Westlake:
Which device is this, it appears that you have several.

Frank

SGH-I717(AoCP6.4), SM-N900V/MI9(dlV), XDA Premium
[SuperSU] Pons:
It's not actually daemonsu, but the root app that calls it. I'd try looking up the app id.

(obviously change the app id to match yours)

P.S. Those are some ridiculously huge pictures.
[SuperSU] GldRush98:
Yeah, sorry about that. They're straight off the phone, Nexus 5, so they're 1920x1080 in portrait mode. I'll resize these by 50%

As far as I can tell the pid that called this daemonsu doesn't exist any more.

I've got my phone recharged now and I haven't rebooted yet, so it is still chugging away on there. I'm willing to help if I can. I've got to give my daughter a bath and get her to bed here, but I'll be around in and out if anyone wants me to try anything that could help track it down if this looks like a su bug.

edit: Got adb over wifi working:

root@hammerhead:/ # ps | grep daemonsu
ps | grep daemonsu
root 199 1 6584 80 ffffffff 0000863c S daemonsu:master
root 2622 199 2488 160 c083cbcc 0000863c S daemonsu:10076
root 3420 199 3512 104 c083cbcc 0000863c S daemonsu:10115
root 3564 199 4536 212 c083cbcc 0000863c S daemonsu:10181
root 11396 199 6588 216 ffffffff 0000863c S daemonsu:10176
root 12894 199 6588 116 c083cbcc 0000863c S daemonsu:10212
root 13771 199 8636 168 ffffffff 0000863c S daemonsu:0
root 13773 13771 8636 356 c02763ac 000083a4 S daemonsu:0:13768
root 13868 13773 0 0 c01973ac 00000000 Z daemonsu
root@hammerhead:/ # ps | grep 10176
ps | grep 10176
root 11396 199 6588 216 ffffffff 0000863c S daemonsu:10176
root@hammerhead:/ # ps | grep 11396
ps | grep 11396
root 11396 199 6588 216 ffffffff 0000863c S daemonsu:10176
root 11580 11396 920 320 c026cddc b6ed33a0 S tmp-mksh
[SuperSU] zeppelinrox:
Use busybox ps to get full paths.

busybox ps -w | grep <string>

or if it doesn't have the -w option just plain:

busybox ps | grep <string>

Some builds of busybox have the -w (wide) switch which gives more detail.

However, if it doesn't have the -w switch, you get the extra detail by default.
[SuperSU] GldRush98:
I think it is being caused by AdAway 2.8.

I rebooted and tried updating the hosts file and saw the daemonsu jump up and stay up again. It did it twice in a row (2 reboots) to me so I have a good feeling that this is it. AdAway has been finicky ever since 4.4 came out anyway. I have disabled AdAway's automatic updating for now.
[SuperSU] sebadamus:
Yes my device is rooted with cydia impactor and PwnMyMoto, this puts a "su" file inside /system/xbin/su and /system/bin/.ext/.su (dont really know what is the .ext and .su... but the su file works)

Then I installed supersu 1.86 (last month I think), the the 1.91 update came and I installed it too... and there appeared the problem that it cant update binaries (anyway, SupuerSu exits right after telling me it cant update the binaries... the supersu application 1.86 is still working)

For example... I remove SuperSu from my PlayStore, no other su app installed by PlayStore... supersu 1.86 still works!

Maybe I shoud have not updated to 1.91 just like that... should I have to uninstall from SuperSu options first?

Too much questions :D sorry.

Thanks FrankI will try that about METAINF and following the script trying to install the update... if it works I will post here!

it would be good that SuperSu gives you some detailed log about the error... not just "cant install the binaries" and exit, maybe having a debug log can help...