yashsingh1/xdaforums huggingface dataset:
[SuperSU] mbirth:
I'm in the same boat. Nexus 10. Previously 4.3.1 with SuperSU. Removed SuperSU for the upgrade. Did the OTA (without problems). Trying to install SuperSU 1.69 using TWRP resulted in a reboot at "Restoring files". Using CWMR, it completed fine. But no matter what I try (SuperSU 1.65, SuperSU 1.51, CWMR/TWRP flashed, CWMR/TWRP remote-booted, Zips sideloaded, directly from internal storage, etc.) - it just won't work. It doesn't show up in the drawer. Apps trying to get root just hang.

I tried to install the Superuser.apk as a user app, too. Now it shows up in the drawer, I can start it - but then it crashes.

DDMS shows this:

11-14 02:07:40.005: E/PackageManager(463): Adding duplicate user id: 10165 name=eu.chainfire.supersu
11-14 02:07:40.010: E/PackageManager(463): Failure adding uid 10165 while parsing settings at START_TAG <package name='eu.chainfire.supersu' codePath='/system/app/Superuser.apk' nativeLibraryPath='/data/app-lib/Superuser' flags='540293' ft='142540f5400' it='142540f5400' ut='142540f5400' version='169' userId='10165'>@2590:218 in java.io.InputStreamReader@41937298
11-14 02:07:41.445: E/PackageManager(463): Adding duplicate user id: 10165 name=eu.chainfire.supersu
11-14 02:07:42.065: I/PackageManager(463): Expecting better updatd system app for eu.chainfire.supersu; removing system app
11-14 02:07:58.565: W/PackageManager(463): Not granting permission android.permission.ACCESS_SUPERUSER to package eu.chainfire.stickmount because it was previously installed without
11-14 02:07:59.470: W/PackageSettings(463): Skipping PackageSetting{41abcbd8 eu.chainfire.supersu.pro/10336} due to missing metadata
[SuperSU] Chainfire:
Everyone should be aware that there's an issue with OTA survival mode and 4.4. It will prevent the OTA from finishing correctly at this time.

I think I actually found the issue, and the fix will be in the next update, but for now if you're manually applying the Nexus OTA, disable OTA survival first.
[SuperSU] eLCruz:
What about non 4.4 issues? Anything about 4.1.2? Why is it acting up?

sent from "Where Man has Never Gone Before" using Tapatalk Pro :confused:
[SuperSU] NTolerance:
Same issue here. I've got a 2013 Nexus 7 with the 4.4 OTA having been applied successfully. I go to flash SuperSU v1.69 via TWRP and it doesn't show up in the app drawer. The version of SuperSU from the Play Store just crashes.

I'll be happy to help test out any fixes or provide more information if needed.
[SuperSU] eLCruz:
Sgh-t989 4.1.2 stock debloated. Did full unroot option & worked. Flashed 1.69 zip w/ twrp. No supersu in drawer... :banghead: all options exhausted! Little help please... Is 1.69 bad or what? :what:

Edit: all root apps work, I just have NO control over them! Not good! Going back to 1.65...

sent from "Where Man has Never Gone Before" using Tapatalk Pro :confused:
[SuperSU] defim:
Works fine with 4.3.1

---------- Post added at 06:27 AM ---------- Previous post was at 06:13 AM ----------

And can you please fix the bright white screen on loading if I'm using the dark theme? M66B did it this way: https://github.com/fda77/XPrivacy/commit/4f4f22eacd342d6a671e1fc685d2228dee98d4da
[SuperSU] G.M.L:
The update works fine with custom rom Slim CM9 4.0.4 !!!!

Send from Greece (Slim CM9 RC4 - G.M.L. V4)!!!
[SuperSU] Josuhu:
I manually sideloaded 4.4 OTA to Nexus 7 Flo. Then adb booted in to latest TWRP and flashed latest SuperSu from twrp. Then restart and everything works.

In the end Im with Stock rooted 4.4 and with stock recovery.
[SuperSU] Chainfire:
Quite probably Gemini App Manager checks for the Superuser package name (weird) instead of if the su command is available.
[SuperSU] Chainfire:
Yeah it would be nice, but as long as I'm in an area where movies aren't available at all, it's unlikely to happen.

To be honest, Google should be punished for this behavior. They are treating you like a criminal just because you have root.
[SuperSU] drob311:
I rented inglorious basterd yesterday and the voodoo root keeper free on the market worked... Havent had the chance to try it again...

Sent from my PG06100
[SuperSU] sparksco:
Thanks for the tip drob I'll try that out
[SuperSU] tyler79durdan:
Awesome Work Man! Thank you for everything you have "allowed" me to do with your work! I appreciate it!!!
[SuperSU] Number R09:
thanks for developing this app. could someone point out the correct way to replace my current SU? i'm still classified as a noob, and i really don't want to accidentally screw up. so flash SuperSU, then uninstall the original SU? or the other way around?
[SuperSU] Kalavere:
So I installed it to see what it was all about, preferring SuperUser I've uninstalled SuperSU. However I can no longer gain root access using SuperUser, I've yet to try installing SuperSU again, was this to be expected?
[SuperSU] Chainfire:
First install SuperSU, then uninstall Superuser.

Yeah try reinstalling SuperSU. Then start Superuser, go to preferences, and let Superuser update it's binary. Then uninstall SuperSU.
[SuperSU] Kalavere:
The thought just hit me, thanks Chainfire. :)
[SuperSU] retnuh:
Did I do something wrong? This really scrwed up my AT&T SGS2.

Installed SuperSU from the Play Store. It is the current version. I am rooted and running stock GB on my AT&T SGS2. Now TB Pro is stuck on "Asking for root rights". Also, Root Checker stopped working. I uninstalled SuperSU and everything is still screwed up. Was this app not released for my phone and rom?
[SuperSU] Kalavere:
Look up a couple of posts, you need to reinstall SuperSU and update the binary's from your old SU app.
[SuperSU] sparksco:
Another thing you guys can try is wiping data for SuperSU under manage applications which will reset everything. You'll have to allow apps permissions again though.
[SuperSU] Chainfire:
I know a few people are having issues... trying to fix them but so far completely unable to reproduce... IRC, GTALK, logcats ?
[SuperSU] jsgraphicart:
Just installed it and tested all my root apps. Works good so far. The only problem I have had is the SuperSU app freezing up when I select the settings tab in the app itself.
[SuperSU] frogman74:
The zip

I had problems with the zip not wanting to flash. Error 0.

So I smooshed it into one of the zips I new worked.

Everything is running great now.

Those zips are like magnets, the work on magik.:eek:
[SuperSU] :
Chainfire i bought every app that you made so far so i can thank you enough for your work :D

Thanks for making our little gadgets more beautifull and useful
[SuperSU] Chainfire:
I originally had that with the ZIP I made, then changed it to the one uploaded, that one worked. Not quite sure what the problem is with that.
[SuperSU] sparksco:
Abd is you friend ;)

adb pull /cache/recovery/log; adb pull /cache/recovery/last_log;
[SuperSU] Chainfire:
You misread. I had the same issue: Error 0. What fixed the ZIP for me, apparently created the error for him.

The update-binary executable seems to be causing this ...
[SuperSU] sparksco:
Yes I understand, but if you want to see the error for why the zip failed this is how.
[SuperSU] kazzxtrismus:
Subscribing... I'm not rooted yet and I bought this!
[SuperSU] dark_knight35:
New version out! Didn't have any probs with the previous one, let's see how this one works.
[SuperSU] shaggyskunk:
Hope that this isn't a dumb question, but could someone explain why you should disable "survival mode" before doing a nandroid backup?

Thanks!

Sent From my Two Tin Cans & String Device on The Wookie Network
[SuperSU] Crocodile1973:
fixed problem
[SuperSU] cbeckstein:
Problem with rsap (remote sim access protocol) App asking for root access whenever Bluetooth is switched on (although I grant root access each time with the option to not ask again) persists under supersu 0.85 with stock Rom XWLPQ...
[SuperSU] Волк:
0.85 seems to be the old version. Market shows I don't need to update and is listing 0.85 as the latest.

Maybe he updated the title but not the OP yet?

Edit: Never mind. Market is stupid. Phone has 0.83 not 0.85. Lol.
[SuperSU] Papun:
anyone can make for me v85 apk file? i cant install with cmw.
[SuperSU] DarkhShadow:
Download from market or extract it from the .zip

Sent from my ice cream powered Nexus S
[SuperSU] shaggyskunk:
He might not be able to get it from the market, because of his location?

Sent From my Two Tin Cans & String Device on The Wookie Network
[SuperSU] DarkhShadow:
Then he can extract the zip
[SuperSU] pesaroso:
Might be a stupid question, but.. If I have Superuser installed, how can I switch to SuperSU? If I try to replace the apk using i.e. Root Manager, it will need root access to overwrite, and.. then what? ^^ Any easy ways on making the switch? :)
[SuperSU] eoghan2t7:
Use the attached file in the open and flash from recovery ;)
[SuperSU] Волк:
There's something with the zip which some versions of CWM don't like. I get a status zero message. But all one has to do is install the app from their SD like they would another app.

Edit: for what ever it's worth I'm running Euroskank's 5.0.2.7 of CWM.
[SuperSU] Chainfire:
For both backup and restore... because OTA survival mode uses a filesystem flag that nandroid is to dumb to understand, so it will fail.
[SuperSU] yreham:
superSU

there is no su binay installed an d superSU cannot install it. this is a problem

?????

message from superSU 0.85 flashed as zip
[SuperSU] segv11:
I got that when I experimented with "Cleanup for reinstallation from Google Play". It looks like I managed to un-root myself by doing that: both the su binary and the backup were gone.

I had a secondary backup of the su binary, due to OTA-Rootkeeper, so I just went into adb and ran that (su treats adb shell as trusted). Then remounted /system r/w and copied the backup to /system/xbin/su. SuperSU can take care of cleaning up after that.

If you don't have an su backup, you could try restoring from a nandroid that has a working su, or manually pushing an su binary in fastboot.
[SuperSU] Chainfire:
This is stated in the first post ...

Problem found and fixed, thanks.
[SuperSU] moom999:
After installed it on Samsung galaxy note there is no update notification in google play I have to check for update for each apps manually
[SuperSU] rsap:
I'm the author of the rsap app and had the same behavior. To me it looks like SuperSU has problems with underscores in package names. The package name is "com.android_rsap.rsap". In the SuperSU list there is only a "com.android".
[SuperSU] Chainfire:
Thanks, will check this out.
[SuperSU] mbirth:
I just tried the procedure mentioned here - i.e. flashing stock 4.3 boot, recovery and system. Applying the OTA. Flashing TWRP (the new 2.6.3.1 from last night) and installing SuperSU-1.69. Everything went through fine without any hitch.

But still the same behavior. CatLog doesn't show anything. FX File Explorer hangs when trying to get root. SuperSU is missing from the drawer.
[SuperSU] gialakias:
Try installing the app from play store and repeat.
[SuperSU] mbirth:
No luck either. Android detects that the SuperSU APK from the Play Store is the same as that in /system/app and removes it from the user space.
[SuperSU] Xoib:
Am I the only one with the init process making root request ?
[SuperSU] cokeman2010:
Language reset

After upgrade to 1.69 phone resets system language after reboot. Does anyone have similar issue?
[SuperSU] MicheleJ:
Update worked great on my rooted vzw note 3 stock. I also had the ota update MJ7. Binaries updated fine rebooted with no problems and all my rooted apps retained the previous root access permissions. Thanks for the update!
[SuperSU] Rhian:
Nexus 7 (2012/grouper) with OTA from stock 4.3 to KitKat (4.4), I am getting "Unfortunately, SuperSU has stopped."

I tried both the Update-zip and the Google Play method, the result is the same, not working.
[SuperSU] marvellyukon:
SuperSU v1.69

Not work in the upper scrollbar.

Android 2.3.6

Display Size 480x854
[SuperSU] Chainfire:
Seems a number of people are having issues with KitKat and SuperSU and force closing. I need a logcat of the crash, or there's nothing I can do.
[SuperSU] CoolApps:
SELinux is set to "Enforcing" on KitKat, maybe that's the issue?

Since you have Nexus devices maybe you can install KitKat and find the issues?
[SuperSU] CoolApps:
Maybe .NativeAccessReceiver contains some unsupported code or something is disallowing it (SELinux).
[SuperSU] Viggen66:
I have a problem with SuperUser 1.69, I have installed a custom rom on a ICS, but the SuperUser that come with the rom asked for permittion to grant or deny root access, after the automatic update, no popups appear on apps that requires root access, making the apps useless, and the log says it denied permission, but it doesn't ask anything? And it is not possible based on the logs to change the settings, this is really annoying
[SuperSU] Zytrel:
I can confirm this issue on a Galaxy S2 I9100 on stock XWLSD 4.1.2 firmware.

Language resets to rom default after each reboot. It only seems to affect reboots btw, when doing a shutdown everything is still fine.

UPDATE: Reverting to v1.65 fixed the issue.
[SuperSU] Viggen66:
I have removed Supersu, and now apps are working, what is the point of this app, if it blocks root access, is it security related?
[SuperSU] cschmitt:
Without supersu app any process that asks for root gets it.
[SuperSU] sub1287:
You have two root apps, sounds like superuser took over superSU. You need to reinstall superSU and grant it root then make sure you have superuser disabled.

Installing the zip should make superSU the default root app.

Pure Speed X? ~ ViPER4Android ? [n⁴]
[SuperSU] Viggen66:
where can I get the zip?
[SuperSU] Pons:
In the OP (original/first post).
[SuperSU] 78Staff:
Come on man, at least make an effort to read the OP...
[SuperSU] Dovidhalevi:
Adventures in superSU land.

Running on cm-10.2 on an LG P500.

Today (first time in a while), I tried to get to the main UI pane of the app. It said it must be updated. Not doing so exits.

So, tried to do so from within the app. Not successful.

Tried to do so through CWM, from the app's dialog box. Ended up with a soft-bricked phone, stuck on Cyanogen's logo. No adb.

I took out the battery, put back in, connected usb and go the charging bootloader. From there, I was able to adb reboot recovery and get my phone back restoring most recent backup.

So ... downloaded the new UPDATER zip.

Rebooted into recovery, made a new backup and then installed the zip. Ended up with a soft-bricked phone ...

Phone has been rooted for a long while, naturally. Do not know what is meant by or how to re-root it as was suggested somewhere. The thing should update from Play if that is where it is posted (lists version as 13.10.2013), yesterday!

What to do (other than going to a tamer superuser app?
[SuperSU] Viggen66:
I think the problem on the update was not making the SuperSU Binary Update, I have done through Recovery, never thought this was necessary, probably it's the reason why no pop up appears

---------- Post added at 09:03 PM ---------- Previous post was at 08:52 PM ----------

There's really a bug on Supersu 1,69 popups stop to work
[SuperSU] Dark_Avenger:
Same for me on gingerbread 2.3.5.
[SuperSU] Viggen66:
There's really a bug on Supersu 1,69 popups stop to work
[SuperSU] SecUpwN:
[MENTION=631273]Chainfire[/MENTION], please have a look into this thread in the security discussions. Do these vulnerbilities really exist and are you able to fix them soon?
[SuperSU] k1mu:
That post says to update to SuperSU greater than or equal to 1.69. Look at the version in the first post of this thread.

Fixed in current release. :)
[SuperSU] Chainfire:
That's very strange. Doesn't make any sense. Can you reboot your device, wait approx one minute, then do a complete logcat and attach that? It appears something is wrong with the APK parsing

I have absolutely no clue what is going on here. SuperSU isn't involved in changing language, nor does it contain any feature to.

SuperSU can deal with Enforcing SELinux, that's not it. And that's just it - I have SuperSU running on multiple Nexus devices on KitKat without any issue.

You're not the first one to report this on CM-10.2 since the v1.69 update, but I have no answer yet. For me of course it works fine on the one device I have running CM-10.2 ...

These are already fixed in v1.69.
[SuperSU] CoolApps:
Oh ok, are you using the official KitKat 4.4 from the Nexus Factory Image page on those devices?
[SuperSU] Chainfire:
For the Nexus 7 2012 I used the OTA update, for the others full images from that page, yes.
[SuperSU] eLCruz:
Why won't 1.69 show in the app drawer on jb 4.1.2? It installs (play store & zip) but no icon in apps. Root is there but no way to control or notify! Any help please...

sent from "Where Man has Never Gone Before" using Tapatalk Pro :confused:
[SuperSU] CoolApps:
Probably the users experiencing issues are using 4.4 KitKat which was ported over from the Nexus 5.
[SuperSU] gee one:
i'm on a stock rooted nexus 5 and have no problems. i rooted with 1.65 via cwm, and then updated to 1.69 from the play store. maybe ports have issues?

thanks

sent while running with scissors
[SuperSU] CoolApps:
People who are experiencing issues on KitKat, where did you get the KitKat rom from and which device?
[SuperSU] adrman:
Here as well. I initially used CF-Autoroot, then updated to 1.69 via the playstore/normal method without issue. Since then, I've installed cwm and Franco kernel r10, and reflashed the 1.69 zip from cwm after. All is still good.
[SuperSU] Gitah.:
Nexus 7 2012, downloaded the OTA from google's servers from a link on android police. Supersu doesn't show up in the drawer after I flash it.
[SuperSU] CoolApps:
So after reflashing SuperSU it will not appear within the app draw?, try checking if you can open it via Google Play.
[SuperSU] sgs2.5:
Lost root after 11/13/2013 playstore upd. Hours later root is back !

Something werd happened after installing the SuperSU update from the gp-store.

SuperSU would not replace the su binary, so I tried the auto recovery install from SuperSU.

After rebooting I lost root !

Now hours later as I was about to flash (eventually didn't) I tried some root apps, and ROOT WAS BACK, or at least started to work again afterall.

The only change I made was setting SuperSu to disabled (setting disable superuser), started and exited Titanuim Backup once, and enabling it (in SuperSU setting enable superuser) again.

Somehow root magically came back.

So before flashing/bricking/doing heart surgery on your phone, you might want to mess with the settings a bit...

I'm on Galaxy S4 (intl) / PACman rom (4.3.1)

Thanks ChainFire !
[SuperSU] Gitah.:
I can download it from Google Play and it shows up but it constantly crashes if something requests root access.
[SuperSU] CoolApps:
Same issue has the other user...

Try uninstalling that one and use CF-Autoroot.
[SuperSU] Zytrel:
I just did some digging into the language reverting to default on system reboot issue. It seems this is caused by BetterBatteryStats with root features enabled.

Upon uninstalling said app the issue has not resurfaced again so far.

Note that it worked perfectly before with SuperSU v1.65. I will let the BBS dev know about this issue as well, as I have no clue which one of the apps is to blame.

Sorry, disregard the above, it resurfaced after a few reboots. I will keep trying to find a cause.

So far the only thing I can tell you is that it seems to happen every time any app is granted/denied root access.
[SuperSU] inbetweenaisles:
I'm on CM11 beta for Sprint Galaxy S3 and wanted to use ART on it so I disabled the superuser built into the rom, then flashed the 1.69 file in the OP using CWM, and now I lost root access. Can someone help me out?
[SuperSU] fajarep:
after updating, it seems, the prompt for root access not working, disabling prompt for grant automatically not a problem. i don't what problem with 1.69
[SuperSU] mbirth:
I just sent you a PN.
[SuperSU] hyperspacey:
Funnily enough I was getting the same issues; I wound up getting it working, somehow, by going into Settings->Apps, where it was appearing as a system app version 1.60 but not in my app drawer. I uninstalled all updates from there, then it started working, but appeared as v1.60 still. Then I did a Play Store update which brought it up to 1.69. It works now but **** if I know why.
[SuperSU] mbirth:
Holy cow! I think you found the fix! Now it started working for me.
[SuperSU] hyperspacey:
Damned if I know how it works (I'm guessing there's some kind of permissions bug or something going on somewhere) but I just mashed my face against the screen until it started working and it does the job.
[SuperSU] RaphaDroid:
I dont't know if it was already tested... Just like expected (at least by me), SuperSU v1.69 does work on the official 4.4 KitKat build for mako.

[MENTION=631273]Chainfire[/MENTION], you're simply the best! Thank you!
[SuperSU] mbirth:
This is how I did it on my N4:

Install SuperSU from Play Store

Reboot

Settings → Apps → SuperSU → Uninstall updates

Reboot

Settings → Apps → SuperSU → Uninstall updates (again)

Reboot

And then it worked.
[SuperSU] Ezekial:
I can vouch this worked perfect for me.

I am on a Nexus 7, stock ROM, OTA update, flashed the 1.69 SU, and the installed the SuperSU apps (with pro ;) ) from the Play store. I was getting force closures of SuperSU after a few seconds of opening the app and was never receiving the SU prompts when apps requested root.

I only had to do one session of "uninstall updates" and reboot though.

Thanks!
[SuperSU] GuileC:
Worked for me also on Nexus4, uninstalled update and let the app self updated with the play store :D
[SuperSU] eLCruz:
[MENTION=631273]Chainfire[/MENTION]

Is this only for 4.3+ cause it ain't installing anyway, anyhow, on 4.1.2 JB! No icon in app drawer no matter how you install. Some thing isn't right with this for 4.1.2. I know its not the latest and greatest but what's happening? Any help, thanks...

sent from "Where Man has Never Gone Before" using Tapatalk Pro :confused:
[SuperSU] SUNUN:
Hi after upgrare to this version in every boot phone langusge resets from english into Russian
[SuperSU] Viggen66:
Supersu 1.69 has a bug, which it won't show any popup requesting granting or deny of root access, it's very annoying, I hope the developer will fix this soon.
[SuperSU] Chainfire:
Have you actually tried uninstalling (updates or app) through Settings -> Apps / Application Manager / whatever its called on your ROM, rebooting between each attempt, then doing that again a few times, then reinstalling?
[SuperSU] Chainfire:
The issue with the language changing has been found and solved. That was a tricky one to locate ... :)
[SuperSU] cokeman2010:
How to solve it?
[SuperSU] SUNUN:
How to solve it?
[SuperSU] phillibl:
I am on a DROID Incredible 2 running Evervolv 4.3 and whenever I have Super I flash the binary I go into a boot loop (stuck on splash screen). I have to pull the battery and flash my room in order to boot again. Also, the other non-reboot method just fails and says to reboot and try again.

Any help is appreciated.
[SuperSU] Chainfire:
You'll have to wait for the next SuperSU update
[SuperSU] Chainfire:
Some news on SuperSU issues: https://plus.google.com/113517319477420052449/posts/P2Aqd3jBrgb
[SuperSU] SUNUN:
Ok thx, and when new realease willl be avialable?
[SuperSU] Dark_Avenger:
Did you address the missing pop-up/app hang for new applications requested root in android 2.3.x? Is it related to tabs click problem?
[SuperSU] SignetSphere:
One golden rule on what not say to a dev...

"DO NOT ASK FOR AN ETA!"

No. Seriously don't.
[SuperSU] NTolerance:
This resolved the issue on my 2013 N7 after upgrading to 4.4. Thanks!
[SuperSU] polobunny:
lol @ the tab swiping. Oh the pain. :p