yashsingh1/xdaforums huggingface dataset:
[SuperSU] Chainfire:
It's a problem with root checker. Apparently it has not been updated to correctly reflect the 4.3+ situation.

A good indication is always to just open the SuperSU user interface. If anything is wrong, it will complain (ask you to update binary, claim there isn't a binary, etc), if it doesn't tell you anything, all is well.

I don't support the more advanced stuff (anything reading/writing to /system, really) on HTC/S-ON, so anything you do inside SuperSU's user interface other than grant/deny apps access is a roll of the dice. It's interesting the full ZIP doesn't install for you but the "internal" ZIP (installed when you use the HTC recovery method) does, as they're generated the same way. Have you tried a more common recovery like CWM or TWRP ? Note that most recoveries make/create an internal log ( sometimes accessable through /cache/recovery/last_log after you boot back into Android ) that records the error and it's cause, if known.

It disables some system package that keeps popping up telling you KNOX has prevented access to the system, it stops a lot of (root) apps from working and is generally annoying. Letting SuperSU disable it does not trip KNOX 0x1 or anything like that, and it is certainly advised to use this option.
[SuperSU] Chainfire:
Are you sure there are no left-over Xposed files ?

The piece of information your quoting in no way indicates (nor was it meant to indicate) that SuperSU accesses some functions as "system" (uid 1000). I'm not sure how you read that piece of quote and came to that conclusion, but its certainly not the case.

I would usually turn on full content logging so you can look back which exact commands were executed, then grant access to the request. Then you can see what it was doing ... it'd take some adb work during the request to gather more details than that.

Nine out of ten times, it's caused by a root app. Occasionally it's actually a debugging/development leftover from the stock firmware. Haven't really seen any case of it being anything else than one of these, yet.

These specific cases appear to be due to Xposed as some had suggested, looking at the logcat. However, logcat is not usually the way to find this out.
[SuperSU] klau1:
I am sure it can't be x posed.

I also posted the adb output in this post.

http://xdaforums.com/showthread.php?p=48581943

Of course by the time this adb was made I had already installed a bunch of stuff. But it was happening even at blank state.
[SuperSU] Chainfire:
If you can reproduce the issue (again), try getting the output of "adb shell ps" at the very same time the popup is visible. From the post you linked, there's some indication the requesting process may be kiesexe, but I wouldn't place bets on it.
[SuperSU] klau1:
That file was captured during the popup
[SuperSU] Odysseus1962:
You may find it interesting, however, I find it worthy of concern. I've been using your app for quite some time and this has never been an issue. I use 4ext recovery because It's the only one that works properly on this device and is recommended by those who develop for it. I've never before had issues with it flashing anything except on two occasions where the d/l was corrupted. When I flashed good copies they succeeded.

I've used the recoveries you mentioned before, both on my old HD2 (with great success), and when I first got my amaze, but had nothing but problems. It was only afterward I learned of the Amaze devs recommending 4ext and I began its use.

Again I find it highly unusual that I've had no problems before, but they're manifest now. I'll go ahead and submit a bug report to the 4ext dev, but given that this is the only failed flash I've ever had with a properly downloaded file, I don't know what he can do about it.

I hope this is only a one off incident, as I like your work and wish you only success with it.
[SuperSU] Chainfire:
Then there's really nothing more I can say about it at this time ...
[SuperSU] Chainfire:
Well if it happens again - be sure to capture that log file. I can't do anything with your report as it is right now.

Note that I didn't mean to imply that this was a bug in 4ext or a bug report should be submitted to it's developer or that you should switch to a different recovery, but if you had tried the same flash with a different recovery and that also did (or didn't) work, either case may narrow down the root of the problem.
[SuperSU] Odysseus1962:
Something just dawned on me that perhaps bears relevance. Would enabling "survival" mode have an impact? I have this feature enabled now (after a previous update), but I dont recall enabling it before. As a precaution I'll specifically disable it prior to flashing the next update. Hopefully with better results.
[SuperSU] RHBH:
[MENTION=631273]Chainfire[/MENTION]

Please take a look:

Is this a su error or a rom error, could you give me a direction? :P

I'm using v1.86, installed through recovery.
[SuperSU] Chainfire:
Seems to me like you're working with a previously unrooted 4.3 Sony ROM. You might have actually told me that instead of keeping me in the dark.
[SuperSU] RHBH:
Sorry for that. It is the new 4.3 official firmware from Sony (14.2.A.0.290).
[SuperSU] klau1:
I don't suppose you have any idea what kiesexe is? We all know that Kies is a Windows program for syncing Samsung devices. But I've never heard of kiesexe.

---------- Post added at 11:01 PM ---------- Previous post was at 10:57 PM ----------

According to this post kiesexe is the counterpart to the desktop sync program:
[SuperSU] baldahin:
Same problem with SupersSU v1.86 and CWM v6.0.4.5 on Nexus 5. "Root access possibly lost" message appear even after backup.
[SuperSU] Cyclu:
Since the version 1.85 i see an error in the logcat:

Super SU E isLaunchedBySettings: No

This is important?
[SuperSU] Chainfire:
This is because CWM is stupid.

No.
[SuperSU] Dmtalon:
Morning everyone,

I've got a question, but first some back story.

I've got a Moto X DE (BL unlocked/rooted with supersu). And I've been fighting a weird "android os" issue keeping my phone awake/taking too much CPU time. I read somewhere that somebody fixed this by cleaning up the supersu install and reinstalling. I did this last night and it seems to have also cleared up my issue. my android os battery usage is much lower today, and no keep awake. The past few days its been 1.5h cpu time +.

I am home vs work today so I'm not 100% sure if its related. I'm on wifi both places, so It'll probably take a few days to be sure this was a/the fix.

My question is, what is the best / most approved way to update supersu? I'm assuming something went wonky during an update if this cleanup did fix my issue. I have been using the play store and doing the 'normal' method, not TWRP method.

Technical details

Moto X 4.4

paid version supersu

unchecked notifications

pin required in supersu

Those are the only changes from default settings.
[SuperSU] aavvaallooss:
How I update: Flashify + TWRP (Or only TWRP). Never had a problem
[SuperSU] atomomega:
I always flash the zip in CWM. Never had a problem.

Sent from my HTC Desire C
[SuperSU] nunein:
+1 (but with TWRP)

Flashing the Zip version is recommended for HTC devices because of the write-protection.
[SuperSU] Strephon Alkhalikoi:
I take the opposite tack and update through the Play Store. The only time I use the flashable zip is when I provide updates to my ROM, and then only to get the APK and su binary. In fact, one of the selling points of the ROM I offer (for the little known device I have) is that SuperSU is updated through the Play Store, so no matter what happens the end users have the latest version.
[SuperSU] almahix:
I cannot flash the 1.86.zip from twrp 2.6.3.3 nor from flashify on 4.4.2 rom. Tried repeatedly. Always fails.
[SuperSU] sudisk:
It works fine on my SG-Note I / 4.4.2 / TWRP 2.6.3.0
[SuperSU] jazzruby:
"Always fails" is not very helpful, how about posting the recovery log?

Flash in TWRP then > Advanced > Copy log to sdcard.

-JR-
[SuperSU] Lownita:
I can't get this solved. I flashed 1.86 on Cataclysm Rom using franco kernel r23 and ART. It just bootloops after flashing. Any suggestions?
[SuperSU] LuigiBull23:
Thank you so much for the update Mr. Chainfire. :good:
[SuperSU] almahix:
I did the log file but my browsers won't let me attach it for ridiculous various and sundry reasons..All I can say is as soon as the flash begins TWRO says "failed". The following few lines from the log may be meaningful to you...

UPDATE-SuperSU-v1.86.zip'...

Checking for MD5 file...

I:Cannot find file /data/media/0/Mods/Superuser/UPDATE-SuperSU-v1.86.zip.md5

Skipping MD5 check: no MD5 file found.

E:Zip file is corrupt!

E:Error installing zip file '/data/media/0/Mods/Superuser/UPDATE-SuperSU-v1.86.zip'

Done processing script file

I downloaded the file again and had the same results.
[SuperSU] Pons:
Check the md5. I got:

0b85474f0f139e1e6137f9eab40c3ecb UPDATE-SuperSU-v1.86.zip
[SuperSU] jazzruby:
E:Zip file is corrupt! ˂<<<< This line pretty much says it all.

Are you downloading on the device? If yes, make sure to use the default Android Download Mgr as some others may be downloading the 'interstitial' (html) page and not the actual download zip.

Check the size of the file (should be > 1MB)

and/or

Check the md5 hash against the one PonsAsinorem posted.

-JR-
[SuperSU] Maurice5813:
Hey [MENTION=631273]Chainfire[/MENTION]

Thanks for your awesomeness! And I got one irrelevant question, I thought if anyone would know, it'd be you. Its off topic a little, but, is there exactly a "limit" to how many lines can be added to a updater-script? I was asking because I making a mod, its extremely long updater script worries me, and I know through time and updates that it'll only become longer. Right now its about 150 lines according to notepad++, so exactly how many lines are supported? Is this based on recovery or what? Thanks if you can reply:D
[SuperSU] cmstlist:
Look at how long the scripts are for some stock OTA updates. They often involve verifying the checksum of every single file to be updated, one by one, and then applying each patch, one by one.
[SuperSU] almahix:
I downloaded the zip twice on the phone and had the same result. Later I downloaded it on my PC and moved it to the phone and it flashed fine. I used the same link all the times I downloaded.
[SuperSU] xdapowerapps:
Sorry for a late bump lol. Play movies don't play on any kernel except stock for me. I don't see a temporary unroot button like in OTA Rootkeeper and such but I see the option to permanently unroot or disable and hide. Neither option works. Play movies simply don't work. Just curious if you have any suggestions? :silly:
[SuperSU] aavvaallooss:
I can´t help you, sorry. Only tell you that Play Movies works for me with SuperSU and MX Player under Franco kernel without problem.
[SuperSU] dimebagdan65:
Google Play Movies has been root friendly for well over a year now... Sounds like a C2D interface error to me...

(For the lay person, that's chair to device interface... A fancy/polite way of saying it's human error)
[SuperSU] xdapowerapps:
Thanks for the useless response. Since you didn't originally read what I wrote, here is a snippet:

It's not a PEBKAC (For the lay person, that's Problem Exists Between Keyboard And Chair). It's a kernel issue. My question was about temporarily unrooting through SuperSu Pro, not whether Play Movies are root friendly or not.

So back to my question, is the "Disable and Hide" now the "temporary unroot" option?
[SuperSU] claytow:
Hi,

Im reasonably new to rooting, can I just ask what the pro's cons or reasons are for installing SuperSU into system? i.e is it necessary or should I just leave it as it is until something if anything requires it?

Ive tried to google it but can find nothing.

Thanks
[SuperSU] aavvaallooss:
And did you read that is not a custom kernel issue cause it works flawlessly with Franco's kernel?
[SuperSU] xdapowerapps:
I do have a N7 and franco is fine but there is no franco kernel for my Galaxy S4. It is a kernel specific issue on how it handles DRM movies.

My question once again for the third time... Is the "Disable and Hide" now the "temporary unroot" option? Don't worry about my kernel and play movies issue, I will cook up my own kernel to deal with it. But I need to know about SuperSu's temporary unroot option.
[SuperSU] aavvaallooss:
D'oh!

Now in SuperSU 1.86

Trying to integrate system apps with Titanium BackUp --> Everything OK in appearance; but when I reboot get a BOOTLOOP (Google logo)

Wiping Dalvik cache and Cache with TWRP doesn´t help. After Dalvik rebuilding have a "different" BOOTLOOP (Android is upgrading... Starting apps.)

Chainfire, any ideas before restoring nandroid backup???

Update: Fix permissions don´t help anyway

Update 2: Restore nandroid. Everything OK (My first soft brick successfully managed!!!)
[SuperSU] anoopva:
N7100XXUEMKD Root issues

Hi CF

Hi have issues with root and su on latest N7100XXUEMKD 4.3 stock rom (removed knox using ketan multitool) .

If i flash supersu v1.86 directly using philz recovery supersu fc. If i use ketan multitool v6 and inject old su and busy box then su will fc

but if i update su from playstore then su work and grant access to some apps but the only few apps like mobile odin works ..

many apps not working like root explorer, tb, etc.
[SuperSU] Chainfire:
It is absolutely no use to report FC's without the accompany logcat. There's no possible way for me to even guess what's going on.
[SuperSU] king_lud:
Got latest version (1.86) from Play Store. When I chose to install to system I got a bootloop. First time ever after using Supersu for 18 months.

I have a Galaxy S3 Mini running Maclaw's Slimrom 4.3
[SuperSU] nico1228:
what is the difference

Hello everyone, anyone here can tell me about the difference between superuser and superSU? I'm currently using a superuser which came from the rom that I'm currently using but I seen a lot of positive comments here in the xda and in the play store about superSU and I want to give it try but before I do that I want first to know the difference between the two, by the way my phone is t-mobile G1 which is running a aosp custom rom(Froyo) thanks in advance for those who can help.
[SuperSU] RHBH:
SuperSU is updated WAY more frequently as you have active dev (@Chainfire) support, just post your problem and he'll answer to you.

I bought his apps just to help, he's the kind of person that deserves it.
[SuperSU] rootlinux:
Amen brother.

Flashed with TWRP and not a single issue. :)

Great job.
[SuperSU] GroteBozewolf:
Just wondering: is this a generic or ROM specific problem. I use TB a lot on my Nexus 4 rooted stock 4.4.2 and don't really feel like having boot loops after TB restores.
[SuperSU] king_lud:
It wasn't a problem with Titanium Backup, just with SuperSu's option to convert to system app. I later flashed the zip in recovery and that did not cause a bootloop, so it doesn't seem to be ROM specific.

I would always prefer to flash from the zip but sometimes Play gets in there first and updates it for me and then it becomes a user app.

I have never experienced a bootloop after a TB restore.
[SuperSU] GroteBozewolf:
Good to hear that. I misunderstood your post then. Because there were people reporting issues with app and data restore with SuperSu
[SuperSU] Zwulf:
Tried to install from Play Store, but it didn't work, because it asks for install in my recovery. When I click this nothing happens, so I flashed it. Now it works. Seems that installation from Play Store is not really the easiest way... ;)

Gesendet von meinem GT-I9300 mit Tapatalk
[SuperSU] zniper89:
if i use kingo app to root my note 3, can i just download the latest superSU from play store to update it to the newest or do i need to use Safestrap?
[SuperSU] jorceshaman:
Yeah, I don't even mess with the Play Store updates because it always wants me to update binaries in recovery afterwards anyways. Lol
[SuperSU] anoopva:
Sorry bro. I got a workaround for this issue .. from next time i will share the the logcat when i get issues.. thanks alot bro.
[SuperSU] atomantmk:
After flashing new firmware und ARHD 41.0 I have problem with root, after rebooting no root.

A lot of times try to flash SuperSu v1.86 but no success.

After dirty flashing of Rom root is back but only until first reboot.

Someone to help?
[SuperSU] KachowPow:
I'm sure it's mentioned somewhere, but if not on at least the Galaxy Note 3 (on Verizon) the dialer code is *#1234# to get SuperSU
[SuperSU] riza_hakam:
anyone face problem with greenify?

my device is nexus 4 currently on stock rom 4.2.2 with fk r199.. when i want to add more apps to be greenified, after that when i turn off the screen i can't turn on the screen..

what make worse is when i greenified more apps, the toast message from supersu won't dissapear and will make my device hang.. i must manually restart my device to make normal again..

but the auto hibernation work flawlessly.. i don't know which one the cause of this, either kitkat or newest supersu.. currently i am on my work outside of city, so i can't get the logcat
[SuperSU] coolkoushik07:
[MENTION=631273]Chainfire[/MENTION] there is a bug in supersu. I have selected the log to be clear after 1 day but the log is not automatically getting cleared. Please fix it.
[SuperSU] atomantmk:
I know now what was Problem with losing root after second reboot, after installing Rom with superuser now i dont't have a Problem with root, must be a bug in SuperSU!!!
[SuperSU] bovirus:
Where can I find in this thread or in other XDA thread the package to make a device rooted loading a zip package via recovery^?

I?m talking about

Roou_Supersu_x.yy.zip (where x.yy is the version number).

The latest that I found is Root:_SuperSU1.02.

I tried to load the package Update-v1.86 downlaoded by Chainfire website but the recovert reporetd a problem in the signature.

Thanks.
[SuperSU] iXNyNe:
Is the recovery flashable zip supposed to allow me to enable pro features without buying pro? I'm on omni for i777 BTW.
[SuperSU] Pons:
No, it is not.
[SuperSU] Pons:
[MENTION=3386399]iXNyNe[/MENTION] I thought he added it to the Play store version. Maybe he didn't. I've been on Pro since almost day one, and I'm too lazy right now to uninstall it, then reinstall it from Play Store to see if it's there or not.
[SuperSU] nico1228:
hello everyone, I just want to ask how can I change from superuser to superSU? my superuser which I currently use was from the rom I'm using. I heard that changing from superuser to superSU was a bit complicated since it can unroot my device if I did something wrong, and I want to avoid that, thanks in advance for those who can help me
[SuperSU] kl1k:
Trying to root a Nexus 10 - I've followed all the instructions to root it. Can get into clockwork recovery and installed SuperSU 1.86

When I reboot now and run SuperSU I get

There is no SU binary installed, and super SU cannot install it.

Any ideas? I've tried installing old versions, new version, nothing seems to help.
[SuperSU] Pons:
AS long as you can get into recovery (are are generally S-OFF), you should have no fear of losing root. The quickest way to switch would be to flash the SuperSU zip linked in the OP.

You'd probably get more help in your device forum, but I'll give it a whirl:

Does that mean you tried flashing the zip in the OP? If not, I'd try that.
[SuperSU] kl1k:
Thanks - not 100% sure what I did. Went through the factory reset/reinstall route again and this time it worked fine SU installed and working.
[SuperSU] DjeRoid:
Hi,

just to point out that provided download link does direct to a blank page :

http://download.chainfire.eu/supersu

I'd need 1.86 apk to root my nexus 7. Thanks.
[SuperSU] Notn4:
yeah its just a blank page, I would love to get the latest flashable ZIP as I'm in the middle of rooting my new Nexus 5 :)
[SuperSU] Prufta:
DELETED
[SuperSU] Chainfire:
Please don't do that. Especially since the link was back up before you mirrored it again.
[SuperSU] Prufta:
Sorry, :( just was trying to gave a little help.
[SuperSU] nico1228:
hello guys, my current SPL is S-ON SHIP, can I flash a .zip for superSU even if I still have superuser installed? will it change from superuser to superSU? will I loose my root access? pls help, thanks
[SuperSU] king_lud:
It should be OK - SuperSu replaces Superuser during the flashing process. You won't lose root.
[SuperSU] hariraj96:
QUERY

hi,

i had a custom recovery flashed on my samsung galaxy S but stock GB 2.3.3 os is not rooted...can i just flash the supersu zip in OP over my stock rom...nand is not protected..

http://download.chainfire.eu/372/SuperSU/UPDATE-SuperSU-v1.86.zip
[SuperSU] jster:
Bug in v1.86

Chainfire,

First of, thank you for your many contributions to the community; they are certainly appreciated.

I have what appears to be a small bug to report in SuperSu v1.86. If the program is run with a write protected system partition, it complains that the SU binary needs to be updated even if it is up-to-date. If you hit cancel, the app closes. If you hit continue > normal, an installation failed dialog pops up and there is no way to continue without closing the app. SuperSu loads fine and does not complain about the binary if the phone is booted with write protect off.

Thanks!
[SuperSU] pltctytc:
verizon note 3 and ok'd supersu to deactivate knox after update and works fine using that root that rhymes with bingo
[SuperSU] kornelius1982:
Maybe a wrong thread, but I can`t grant superuser access to new versions/apps. It stuck on checking root access and don`t prompt for an action.

Using SGS3 i9300 sammy 4.3 rom.
[SuperSU] Tunasty:
Superuser or SuperSU? :eek: :confused:
[SuperSU] atomomega:
Did you install SuperSU thru Play Store? If so, uninstall it and flash the SuperSU zip.

Sent from my HTC Desire C
[SuperSU] jowilk:
Hi, I have a Galaxy S3 running BamRom v2 Kitkat with ktoonz kernel. I updated the rom and kernel and reinstalled Supersu. While converting to system app, I lost root. How do I reroot? Do I use Odin 3 and Cf-auto? I just don't want to brick my phone. Thanks.
[SuperSU] LittleConfucy:
SuperSU version

How can I check my SuperSU version?
[SuperSU] Pons:
Manage Apps, or the far right tab of SuperSU.
[SuperSU] matejdro:
Could you add option to NOT deny superuser when I click outside SuperSU popup? It is very easy to accidentally cancel it, especially if you wanted to click something and SuperSU just popped up out of nowhere.
[SuperSU] JulianJenner:
Thank you Chainfire! Happy New Year for You!

Sent by my imprisoned LG Optimus L9 (P760) with Tapatalk 4.3 from deadly & suffering Hungary
[SuperSU] xawen:
If you're still fighting with this, it's probably not a SuperSU problem. The Google Play upgrade from Market most likely broke it. Go into Application settings and clear data for the Play Store application. You'll lose any preferences for auto app updates, but it should fix TiBu. I had the same problem.
[SuperSU] netban:
Sure, no worries mate ;)
[SuperSU] Iceberger:
This is not an answer. The question is about Root Explorer.
[SuperSU] ndnesh:
Thank you Mate :)
[SuperSU] nicholaaaas:
no problem here... what is the log saying when you open root explorer?
[SuperSU] Pons:
Very good question. Mine works, too. For a full log report with all the information you probably need, though, you'll have to buy SuperSU Pro (a worthy investment, imo).
[SuperSU] nicholaaaas:
A log cat or root logger will probably tell him what he need both are free. But everyone should spring for the pro version
[SuperSU] awesomedoscious:
Thank you

This Superuser Permissions app is much better than the standard one. This should be the new standard. Also, thanks for providing the .zip file.
[SuperSU] sparksco:
Yup alogcat app is the one I use and love ;)
[SuperSU] dimebagdan65:
It is an answer, as ES will do anything Root Explorer will do (and then some that RE hasn't even touched) AND it's SuperSU friendly, my question to you is why are you using root explorer? What feature of that app must you have that's not in ES...? Or do you just have money to burn? ;')