yashsingh1/xdaforums huggingface dataset:
[SuperSU] Pkt_Lnt:
Talk to the CWM devs about fixing it and recognizing the file named .installed_su_daemon that SuperSU installs in /etc to stop that.
[SuperSU] tntnt:
Hi,

a friend just bought LG G Pad 8.3.

It's all stock, 4.4.2, stock recovery

I don't want custom roms, just root.

If I use Towelroot (I think it works on this device) and then install SuperSu from Playstore, i'll get root without any libraries problem (or other issues)?

And my second question is: the Supersu unroot is enough to be able to receive normally OTA updates without losing data?

I'm asking this because the tablet isn't mine and I don't want to take any risks. If it was mine, i would have tried already.
[SuperSU] LeftyGR:
http://xdaforums.com/showthread.php?t=2575783

This provides a how to root for this device and keep ota. This may be a good question to ask in there as well.
[SuperSU] tntnt:
That's not the same device and firmware. That one is just for the the V510 GPE and requires unlocked bootloader.

Thanks anyway.
[SuperSU] WorldOfJohnboy:
HTC One M8 Binary Updated

Running ViperOne M8 ROM on my Verizon HTC One M8. I have disabled their Superuser App and installed SuperSU from the Play Store. Whenever I open the SuperSU app, it says the binaries are out of date. I've tried the Normal version as well as the TWRP version (which I have TWRP installed) and Normal version fails, TWRP version reboots my phone and doesn't install the binaries and it continues to give me the "update binaries" message in SuperSU.

Is there a way to "manually" push the binaries or flash via Zip file? I did download the 2.01 Zip from ChainFire's site.

EDIT: I un-froze the ROM's custom Superuser app and gave SuperSU root access. After choosing the TWRP install, it did reboot into TWRP and ran the script. After I let it reboot, I went into SuperSU and no more message about binary updates! I can only guess that I needed to give SuperSU permissions before it could install properly...
[SuperSU] NZgeek:
What you're seeing is expected behaviour.

SuperSU needs to install its binaries into the /system partition. The only way it can do this is (a) if you're already rooted, or (b) if you install from recovery.

The bit about the initial TWRP install also doesn't completely surprise me. It's quite possible that SuperSU was unable to properly write its install script, and the reboot into TWRP did nothing.

As always, the best way to install is to follow the link in the first post, download the zip, and install that from recovery. It's much harder to get wrong :).
[SuperSU] PillowMetal:
Couldn't agree more... so many of the problems mentioned in the 100+ pages of this thread would go away if people would just flash the zip from recovery instead of using the Play Store or letting TWRP handle it for them. I have been using SuperSU for years (and have purchased it) and have never had a problem installing this way.
[SuperSU] egingell:
95%* of users don't even know what Recovery is let alone what Flashing ZIPs means.

*Guessed.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] PillowMetal:
Haha, probably true... but then they shouldn't even be here in this thread rooting IMHO.
[SuperSU] egingell:
No. They have every right to root their own phones. I only wish people would follow instructions. Most if not all devs usually post instructions that laymen can easily understand, but the user chooses not to follow them for whatever reason.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] sudhirkhanger:
I keep getting Root possibly lost everytime I reboot from CWM on Nexus 4 running SuperSU 2.01.
[SuperSU] nursoda:
I also get 'root possibly lost' on SGS i9000 SlimKat 6.x with SU 2.01. Answering Yes or No to CMWs question to 'repair' this seems to not change anything. Works fine anyway IIRC. (That phone is not with me ATM.)

Samsung Note N7000, Galaxy S I9000, Galaxy Ace S5830
[SuperSU] I Am The Frost:
Sounds like CWM needs to update the su it uses. Are you running a dated version of recovery? Just say no to it and all should be fine.
[SuperSU] nursoda:
Absolutely possible. SGS does no longer get big attention and latest releases ... while it has 4.4.4, Semaphore kernel / recovery is older. Thanks a lot, I'll just hit 'no'.
[SuperSU] aircooledbusses:
95% is conservative. I think it's a lot higher
[SuperSU] sjmiller:
Root is about a lot more than custom recovery and custom roms. Having root is extremely useful to me, but I have no interest in installing a custom ROM, and therefore I have no need for a custom recovery. Regardless, my boot loader is locked, so it doesn't matter. But, without custom recovery, you can't flash a zip. So play store installation is still important. At least an apk that can be installed. I'm grateful that SuperSU is available in this format.

Scott
[SuperSU] Frank Westlake:
Some devices can make use of [MENTION=4243514]Hashcode[/MENTION]'s Safestrap system. Safestrap interrupts the boot process and runs a modified TWRP recovery from a RAM drive. Hashcode has made them for specific platforms (i.e. SM-N900V) but they also work on some other platforms (i.e. SM-N900V on SM-N900T). They are all here in XDA. Their primary function is to permit multiple customized system partitions but I use it only for the recovery.

Frank
[SuperSU] sjmiller:
Yes,I am familiar with Safestrap. I have no interest in it. To me, it's not worth the effort to install, that's just my opinion. I am satisfied with the stock experience, I just want to be able to do some things that Google seems to think are too dangerous. Like turning my GPS off and on, etc. You know, those really dangerous, security sensitive things.

Scott
[SuperSU] MikeRL100:
Anyone know how to delete the SuperSu backup script? The location would be of help, of course. I bring this up because I'm noticing some occasional odd behavior with 2.01. I don't know what version this started acting up in, but it must've been sometime recently. As in not more than a few versions back. Sometimes clearing logs freezes. Just sits there spinning forever. Same issue happened today on my Nexus 5 running the OmniROM Nightly built today. But this time, it was when installing the SuperSu backup script. SuperSu said it installed successfully, but I'd like to be certain. And I don't want to wipe data for SuperSu or completely reinstall it. Seems to be a UI issue, hopefully it's not something bigger. Only way to stop it is to kill SuperSu. I wish I grabbed a logcat, but I don't know how to reproduce it yet.
[SuperSU] Chainfire:
It's in /system/addon.d

Indeed, if you reproduce, grab a logcat. I have seen this issue once or twice (seems to be limited to source builds and L) but no way to reproduce, so far.
[SuperSU] dhampire:
Su binary update roop

Lenovo s930 was updated to Android 4.4.2 (ROW_S215_140714).

I did rooted by vroot and then install supersu (same as when Android 4.2.3).

I report "Su binary update roop" umm...

I re-installed SuperSU 1.94 which is the stable one I guess,

OK, No-problem was happened.
[SuperSU] bgcngm:
Judging by your post, I guess this issue plagues all Lenovo ROMs based on Android 4.4.2. I already reported the same issue here, which happens on Lenovo K910S and S860. If [MENTION=631273]Chainfire[/MENTION] wants further information I'm able to provide and be glad to help with further debugging.
[SuperSU] aapav01:
Hi, My Phone Su binary is not updating.... i used the flash able zip to root....... but su binary size is 123KB and where as earlier it was <=300KB

what to do???
[SuperSU] egingell:
Redownload it. It should be 1.9MB.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] aapav01:
Im not talking about zip file
[SuperSU] egingell:
In that case, it's correct... the size anyway.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] aapav01:
See IT.................. after it will fail
[SuperSU] gamer649:
[MENTION=631273]Chainfire[/MENTION]

Having problems with SuperSU v2.01. If I have the access set to prompt I get no prompt, meaning root access is denied to apps what require it. I have to set access to grant to allow apps root access. How do I get the prompt back?

Info on my device setup:

Device - Xperia M C1905

Android version - 4.3 ( been on it for about 3-4 months I think, no problems until the last month or so)

Build Number - 15.4.A.0.23

Kernel - Stock

Root - Full root (no remount reboot problem on my device (Sony device thing with the RIC))

Deodexed - Fully

SuperSU version - 2.01

su binary version - Unknown

Enable Superuser - Ticked

Re-Authentication - Unticked

Default access - Grant

Show Notifications - Ticked

Logging - Access only

Clear logs after - 3 days

Auto-refresh apps and logs tab - Ticked

Enable su during boot - Ticked

Enforce permission - Unticked

Enable multi-user - Unticked

Installed as system app - Yes

Trust system user - Unticked

Enable permission warning - Unticked

Could somebody help me to provide a logcat as I have no idea how to get one.
[SuperSU] keneth_c:
Try to clear data for SuperSU.

Apps / Application Manager and then select SuperSU. Clear Data.

Leave "Default Access" to prompt in SuperSU settings.

Untick / u check "Reauthentication" in settings as well.

For logcat, you can install "Catlog" from Play.
[SuperSU] gamer649:
I am unable to clear the data to the app as the button is greyed out and unpressable. I used the reinstall option in SuperSU to remove the app and the data and then I reinstalled it. This didn't help at all.

If I leave the default access to prompt I don't get the confirmation pop up and consequently can't give root access to apps, hence why I have set it to grant.

I am doing a logcat now, I have had to do it through ADB as catlog is a paid app and I don't have the money to pay for it currently. The logcat function has been running for approximately 1 1/2 hours, how long should it take?
[SuperSU] bgcngm:
Only the needed time to collect relevant data, in this case using apps that request root access and changing SuperSU settings for prompt / always grant access.
[SuperSU] gamer649:
Once I have replicated my problem should I just post the entire logcat or should I search for something? I get no errors or crashes, only messages from the apps saying they couldn't get root access.
[SuperSU] Strephon Alkhalikoi:
Catlog is an open source app, meaning anyone can build it from source. In fact, Catlog's license is a "Do What The F*** You Want To" license, so F-Droid has done just that and offers the app on their site.

Once you are able to, it might be good to support the developer by buying Catlog through the Play Store, but at least this way you can get the app.
[SuperSU] USBhost:
I don't know if this is a bug or not but

An app can get root with out an su prompt

If the user has adb over WiFi enabled

Adb root

Adb connect 192.168.1.129

Adb shell

And you will get # with no su prompt

Hmm I only get this on my nexus 7 why?

On my note 3 this doses not happen

I wonder the reason why it won't work with

My note is that when I type adb root, adb won't stay on root hmm
[SuperSU] Chainfire:
SuperSU v2.02 released

Update to v2.02 released: https://plus.google.com/113517319477420052449/posts/adzkJidyyt7
[SuperSU] olavopb:
I have a problem with 2.02 in N5 L

even if I have permission on the default access, the application requests permission!

Thanks!
[SuperSU] Olivier_V:
Does this update fix the problem of losing root after reboot (Galaxy i9305 android 4.3) wich needs to unsintall/resinstall/reboot SuperSU ?

Thanks
[SuperSU] VivaErBetis:
Tested new 2.02 update in a nexus 4 & nexus 10, both under Android 4.4.4 stock, without problems. Just for the records.
[SuperSU] nursoda:
I noticed a small typo in a german localisation of a notification that I think stems from SuperSU:

(the double "A")

Where should I report it? Here?

Samsung Note N7000, Galaxy S I9000, Galaxy Ace S5830
[SuperSU] Android-Andi:
[MENTION=4322342]nursoda[/MENTION] seems like a slimrom issue/typo. I'll fix it.

Gesendet von meinem GT-I8190 mit Tapatalk

Will be fixed in next SlimKat weekly:

https://gerrit.slimroms.net/#/c/12128/

THX for reporting!
[SuperSU] DarkhShadow:
:D

Sent from my ice cream powered Nexus S
[SuperSU] bsoplinger:
A page or two back I had an ah-ha moment, making the comment ”so that's why it seems like the preference to not prompt works then fails then works again” in reference to the fact that SuperSU will always prompt when a new version of a program is detected. So...

May I suggest that SuperSU say just that in the prompt, that is that a new version of app detected. I'd think other folks besides me were confused by this behavior. Note that I think it makes good sense from a security standpoint to do just as SuperSU does and make sure the new version is indeed something the user is aware of andreally does want it to get elevated privileges.

Sent from my PG41200 using Xparent Purple Tapatalk 2
[SuperSU] Chainfire:
This behavior is configurable in the upcoming version.
[SuperSU] jollyb:
Also had this problem. Because i use Gemini for various stuff - it's awesome :)

I manly use SuperSu because it's great, but for Gemini to work it need Superuser to be installed, i confirm this :)

i did this:

Went to Market, installed SuperUser, run Gemini, on some app i click Config Autorun - and SuperSu was prompting for selection. i granted and Gemini is working. (Because i set in options previously for Superuser to allow and don't shows prompt)

Now is it good to have both SuperSu and Superuser installed at the same time?
[SuperSU] dimebagdan65:
You've pretty much got the same setup as me. SuperSU app and binary installed, Superuser app downloaded from the Play Store (but never ran!). A lot of apps check to verify if superuser.apk is "installed" before requesting access, at which point the SuperSU prompt appears
[SuperSU] Chainfire:
It's strange apps do that, because Superuser is not the only app that does this. Aside from SuperSU, MIUI also often uses it's own app, that would fail this detection. Not to mention the "su" that goes around that just always grants root access and does not have an accompanying UI.
[SuperSU] dimebagdan65:
Meh, minor wonkiness with a ridiculously simple workaround, non issue for me

:thumbup::D:beer:
[SuperSU] Chainfire:
SuperSU v0.88 released !

SuperSU has been updated to v0.88 on Android Market / Google Play.

Have not updated the CWM ZIP available in the first post yet, coming soon (dinner and such first). But if you have SuperSU already installed, just update it from Play!
[SuperSU] vlt96:
Lol are you serious? How can you update post, title and play store @the same time? How many tabs open?

Seek the signature below the line;)
[SuperSU] Chainfire:
You can't really... it takes a couple of hours for all of them to become "in sync".
[SuperSU] DarkhShadow:
Nothing wrong with update here, just downloaded it :)

Sent from my ice cream powered Nexus S
[SuperSU] sparksco:
Very odd mine still shows v0.87 as the latest version on the market :confused:
[SuperSU] dimebagdan65:
I just looked and it updated no problem, new binary and all
[SuperSU] DarkhShadow:
Its not ready for your area yet, although if you tap update all it WILL update wierdly

Sent from my ice cream powered Nexus S
[SuperSU] k2trill:
Android WiFi Tether....

.88 still doesn't work with WiFi Tether. Will u fix this please? I can deal with it not working with Root Explorer (yet) since there are 100,000,000 "root explorers" available, but WiFi Tether, I need.
[SuperSU] Fallen Spartan:
Root Explorer works fine for me

...........................

You can lead a fool to wisdom but you can't make him think! XDA, mobile wisdom, not a n00b feeding ground!!
[SuperSU] dimebagdan65:
What phone/Rom/kernel?
[SuperSU] Grevane:
I was one of the people helping Chainfire test the new version earlier today. I'd reported the root explorer problem to him and a few ways to replicate it.

I too have the problem with wifi tether but it does not look like a SuperSU problem on checking the logcat logs with aLogcat.

If you could install aLogcat and try to open wifi tether and after a few minutes then open aLogcat and save your logcat logs and pm the logs to me, I'll have a look and compare them to mine.

The were a lot if java class loader errors on my s2.

If you're getting the same, on face value, it doesn't look like SuperSU is to blame.
[SuperSU] Chainfire:
Thanks for letting me know. The "developer console", where I upload and manage apps on Google Play, was severely acting up and would not show me v0.88 after I uploaded it for quite some time. It's there now, so I guess it was just a glitch. But you never know the developer console - it has screwed up things many times before, requiring re-uploading :)

After your tirade and accusations last page, it's not exactly a priority. That being said, logcats I have seen so far on the issue have not shown SuperSU as the reason it failed ... So I need a better/different way of replicating the problem, at the very least.
[SuperSU] dimebagdan65:
I'm just gonna shut up lol I feel bad reading about all these problems... My setup works flawlessly... Since the get go, only ever had one issue that I was able to resolve by emailing the developer of the app (it was Tasker). I've used SSU as a system app, user app, with superuser.apk and without, never any issues...
[SuperSU] Darian71:
No issues to report running 4.4.2 NE4 Based TMS3KK TouchWiz v2.0. Root Explorer, Titanium Backup etc working perfectly. Thanks for the continued dedication!
[SuperSU] simonbigwave:
confirm installed SuperSUv2.02Pro, no problem on CM11 718 nightly w/ART on 9505 all OK.
[SuperSU] remo0073:
:good:

No problem with SuperSU 2.02 on Moto G GPE Edition running Android 4.4.4
[SuperSU] stev1456:
Same problem here on N9005
[SuperSU] boyheadkick:
Here too -i9300 running unofficial CM11 Temasek

-aL

tapatalked from my super duper palm top computer
[SuperSU] Blac Caesar:
[MENTION=631273]Chainfire[/MENTION], running v2.02 on latest Paranoid Android 4.5-ALPHA2.. works perfectly

sent from my PARANOID four.Four.Four Nexus 5
[SuperSU] brunodu91:
This release is not useful for slimkat 4.4.4??

Envoyé de mon S4, via tapatalk 4 .

Slimsaberkat 4.4.4 released, alucard Kernel , buzz launcher , modem ET bootloader NC4.

---------- Post added at 04:41 PM ---------- Previous post was at 04:41 PM ----------

[MENTION=631273]Chainfire[/MENTION]

Envoyé de mon S4, via tapatalk 4 .

Slimsaberkat 4.4.4 released, alucard Kernel , buzz launcher , modem ET bootloader NC4.
[SuperSU] Gandicela:
Very useful, I just finished install of SlimKat's latest weekly.
[SuperSU] brunodu91:
It's flashed! Thx

Envoyé de mon S4, via tapatalk 4 .

Slimsaberkat 4.4.4 released, alucard Kernel , buzz launcher , modem ET bootloader NC4.
[SuperSU] WorldOfJohnboy:
Perhaps the OP should be updated then? I only followed the instructions on Post #1 in order, (complicated by the fact that the TWRP Zip install didn't work as it should have).
[SuperSU] zard:
Hi Chainfire,

I'm not sure if this is in your plans or not, or even someone had asked for it and you might have rejected the request or as mentioned, plan in progress. My apologies if any of that applies.

Anyway, the rooting method on Xiaomi's Mi Pad at the moment is using Vroot (http://en.miui.com/thread-27976-1-1.html). I had just downloaded Supersu v2.01 and Supersu Pro from Playstore, rebooted and ran Supersu, which requested to be updated. Update was successful and I rebooted. I launched ES File Explorer File Manager and Titanium Pro, Supersu didn't prompt until maybe half a minute, after which I accepted them. This is good news for Mi Pad users, I'm sure.

At this moment, there isn't any cwmr or twrp recovery for Mi Pad, I can't flash the latest version of SuperSU v2.02 using the zip. Tested with the stock recovery "Mi Recovery v2.01" but it error out after 98%. If you have any idea how to make this work in Mi Recovery, please let me know. You can PM me if you need some help on testing or any other information.
[SuperSU] nguyenquoctrong:
Me too, N7100 4.4.2 & Nexus 7 3G 2012 4.4.4
[SuperSU] Braxos:
Same here as above. Apps requesting access even su is on grant.

N7000 with omni ROM Nightly 4.4.4 from 27/28-07-14, BBS and file explorer.
[SuperSU] Chainfire:
And yet I have flashed this exact ROM to the exact same device and installed the same version of SuperSU, and this does not happen.

I need a proper reproducable case.

Did you by any chance use the "fix permissions" script or anything odd like that?
[SuperSU] sancho_panzer:
v2.02 working fine on:

- Nexus 7 (grouper)/CM11-20140727-nightly/default kernel

- GT-I9505/CM11-20140708-SNAPSHOT-M8-jflte/Alucard v2.6.9 AOSP kernel

Both SuperSU v2.02 flashed with TWRP and not respecting CM root definitions.

Edit: didn't change anything on default definitions besides theme color to dark. Didn't fix permissions or anything else.
[SuperSU] KBanause:
I can't see the current version (2.0.2) in the Play Store.
[SuperSU] jesssiii:
https://plus.google.com/app/basic/stream/z13egjdw3ozui53id04cjl1aoor5ezninhc

Sent from my LG-VS980
[SuperSU] Braxos:
Nop i haven't done anything like this I guess I will try a clean flash of the system as i haven't done a clean flash since 4.4.4 can out.
[SuperSU] YoungDaddy:
I'm still having this bug even after clean flashing a ROM both on my g2 and nexus 7
[SuperSU] boyheadkick:
I have a log, hope it helps..i have the same thing too
[SuperSU] MATRIKS:
+1 on htc one m8 sense version did not try on gpe version
[SuperSU] mindmajick:
fine for me on 4.4.2 and 4.4.3 sense versions.. on the HTC m8.
[SuperSU] Braxos:
Flashed everything clean but at start the same issue. Dunno why
[SuperSU] gijokmr:
Is it possible to overwrite cm superuser app with supersu? I flashed supersu via recovery but superuser is present in setting menu.it's not changed to supersu
[SuperSU] steviemch:
The settings menu will still show superuser, but SuperSU will be the default app.

---------- Post added at 10:51 AM ---------- Previous post was at 10:49 AM ----------

I've flashed 2.02 on my N7 2012 running the latest PA alpha, and N4 running L port with no problems whatsoever.

Sent by Borg neural subspace transceiver node.
[SuperSU] Gustave17:
Just a feedback: I have a little bug with 2.02 on L preview, ES explorer say me my device isn't rooted...

But Root Browser work without any issue...

Envoyé depuis mon Nexus 5

AOKPK & Faux123
[SuperSU] jarcuri:
I want to buy pro version to push to my Amazon fire tv. I went to do it and back up the apk but it wouldn't let me. Is there a way to do this? The play store I have loaded can't find the app for some reason
[SuperSU] Primokorn:
Actually it can be changed by rom developers

https://github.com/TheKang/packages_apps_Settings/commit/dec5df7ff41cc8db2d1781836025d293f9aaa283

https://github.com/TheKang/packages_apps_Settings/commit/5503af9e13e1d241c64c63613bc34fa21a25b483

https://github.com/TheKang/packages_apps_Settings/commit/e194685eab43a78475e769dff6c4491516c618f3
[SuperSU] greogory:
Would logcat or dmesg output help you? I'm not sure how to provide a case that you can definitely reproduce, but I can send any data that might help to you.

I can reproduce the symptom simply by installing 2.0.2. In fact, I can't use 2.0.2 without it requiring re-approval for my apps that were previously approved in 2.0.1, and are still listed as approved by 2.0.2. The symptom goes away as soon as I select reinstall from within SuperSU 2.0.2's settings and install 2.0.1 from either the Playstore, or by flashing the zip.

The re-approve symptom occurs whether my default is grant or prompt. I have a Sprint Galaxy S5, G900P, and have tested 2.0.2 and verified the same behavior with both stock NE5 and MOAR v1.1 NE5.

I haven't tried fixing perms.
[SuperSU] Chainfire:
If you let SuperSU "forget" these apps, then let them re-request access, and grant it, does the problem still come back?

I'll see if there's an NE5 version for my G900F and flash that, and check if I can reproduce the issue.
[SuperSU] boyheadkick:
it does on my i9300
[SuperSU] Braxos:
[MENTION=631273]Chainfire[/MENTION] could you give a link to 2.01 please. Since a clean install with format the internal memory didn't resolved the issue.

Thanks
[SuperSU] remo0073:
Here it is

http://download.chainfire.eu/451/SuperSU/UPDATE-SuperSU-v2.01.zip