yashsingh1/xdaforums huggingface dataset:
[SuperSU] ts1506:
Noticed a weird UX thing on 2.35 on LRX21O on Nexus 5.

When you open SuperSu, then go to recents, and then swipe away SuperSu, or simply swipe up / down the carousel, a blank SuperSu bar is left behind. Happens every time. Also the list of apps reloads everytime you return from recents.

However, if you go directly to home instead of recent from SuperSU, it doesnt appear in recents, so the issue is not there. I believe the activity is getting killed when the UI is not in foreground.

I have attached a video for easy understanding.

Other than that, it works fine, love the new icon :)

Link to Video - Here
[SuperSU] raven1090:
Not work on Motorola Moto G 2014 on android lollipop
[SuperSU] ceabbott2:
v2.35 Failed

Just updated to v2.35 and it could never gain SU. None of the other root access apps work either. Samsung Galaxy Note II. Everything worked on previous build. Running custom rom 4.4.2
[SuperSU] fer456:
Just updated on my LG L5 II and now I can't update to the newer binaries using the normal mode. Always I updated worked for me. Why not in this version?
[SuperSU] juliatan:
After Play Store update a su binary had to be updated by SuperSu Pro. Choose normal (on my fully stock N7-13 KK 444). Waited 10 minutes but it would not finish update. So rebooted. Root seems to be working and I don't get 'su binary update' message. Does that mean update was finished correctly?

Verstuurd vanaf mijn Nexus 7 (2013), iPad Mini 2 of Moto G Lte
[SuperSU] imperia777:
latest update killed my phone with bootloop

I am using NeatROM with my GalaxyS2 and this update killed my phone with bootloop. Reinstalled NeatROM again. Same thing.

Bad update!
[SuperSU] Takamoto:
[quote name="Takamoto" post=57058060]what a pity, I was hoping for help..[/QUOTE]<br />

<br />

In your first Greenify screenshot, there is a reference to 'keyguard is unlocked' (keyguard = lockscreen, I think that part of greenify was badly translated in your language) ... probably it is inherent to the Pin protection offered as pro feature in SuperSU but I'm not entirely sure.<br />

<br />

Now I think we should ask to @<a href="http://xdaforums.com/member.php?u=631273" target="_blank">Chainfire</a> if this lockscreen permission may be stopped in free version without issues. :)<br/>

Can I solve the problem with the last supersu update? now i'm on supersu v 2.16
[SuperSU] Giobio:
On CM11 Nightly it goes wonderful....Good update here....
[SuperSU] albert_htc:
Updated on Nexus 7 (2013) 4.4.4

Works fine.
[SuperSU] fmc000:
Perfect update on OnePlus One running CM11S (44S).
[SuperSU] xlollomanx:
V2.35 works flawlessy on my opo with cm11s and AK kernel
[SuperSU] gevans35:
My rooted Galaxy S3 updated to latest version of Supersu today on Play. After making a CWM backup, device is now showing "custom" in device status and will not reset to "original" via Triangle Away. Is this a coincidence or related to the Supersu update?
[SuperSU] Chainfire:
I can't possible say why the update fails. If using TWRP works, use that...

That's odd, but strangely you're not the first saying this.

Logcat of the crash?

Where have you read translators get Pro? There's a button in the app to switch to Pro mode, what more do you need? Sure, I can send you the Pro APK if you really need... I'm not sure what the benefit for you would be, though :P

The activity is supposed to be killed when it leaves the foreground. I'm not sure what the issue is with that bar, I have noticed it as well. Apps don't actively do anything on that screen though, it's a glitch (or feature?) on Lollipop itself.

http://xdaforums.com/apps/supersu/support-update-failures-t2907365

Can't know.

If SuperSU doesn't complain when you open it, all is well.

Unknown
[SuperSU] Celestial Fury:
Hehe I clicked that button a long time ago. I just read you saying not too long ago that one option made you awesome and the other one didn't. So I've decided to go the awesome way. :D
[SuperSU] david72262:
Running slimkat 4.4.4 on galaxy s2 and all is flawless
[SuperSU] alexlost:
Same here.

Nexus 5, latest lollipop. Updated SuperSU binary. Bootloop.
[SuperSU] fubo73:
Updated from 2.16 on S2 with Slimsaber 4.4.4 20141116 + PA GApps through TWRP 2.8.1.0. Everything perfect.
[SuperSU] imperia777:
bootloop s2/neatrom

What is correct method for installing SuperSU on GalaxyS2 with NeatRom?

This is what I do:

1. Full wipe

2. Install NeatROM from CWM

The only option that I change from default settings is that I pick Apolo kernel instead of Phil. Everything else I leave to default.

3. After installation is complete I reboot the device and update SuperSU from GoogleStore.

Bootloop again with TWRP/CWM

I select TWRP/CWM installation method because NeatRom/Apolo has CWM.

IS that correct or I have to choose Normal method?????
[SuperSU] Sepsis12:
Tip with Google Play Balance

Hello,

is there a way to use my google play balance (acquired with google surveys) to tip chainfire?

I could not find a donation app or a paid app (as with Greenify e.g.).

So is there a way to use this balance or do I simply have to use the in-app-purchase?
[SuperSU] DЯΦiDi@П:
Nexus 5, stock lollipop with autoroot: everything works as expected. Thank you very much.
[SuperSU] relevant_placeholder:
Latest version has IAP in Additional donations section.

edit: paid version would be Pro.
[SuperSU] marc112:
v2.35 not working on Gingerbread 2.3.5

Updated to 2.35 from Google Play. Since then SuperSU force closes 9 out of 10 times.

Similar problem as maddoc1007 reported in #7512, however I was able to update binaries after several reboots.

HTC Desire S on Gingerbread 2.3.5, stock ROM, SuperSU Pro.

logcat of crash attached
[SuperSU] mindfkr:
Updated LG G3 on normal mode ended up in bootloop using CM12, reinstalled CM12 updated SuperSU on TWRP as the app asks all is good, thanks.
[SuperSU] Chainfire:
Let me know if the attached version fixes the issue.
[SuperSU] PeQuEsan:
Nexus 5 with fresh stock lollipop, initially rooted flashing appropiate cf-auto-root (so boot patched) some weeks ago, updated binaries after play store update supersu to 2.35 with no further issues using normal mode here.

bye!

PD: I've fastboot flashed stock boot.img back after that... not sure if updated cf-auto-root is doing that. Sure it's said somewhere in update notes. :silly:
[SuperSU] Celestial Fury:
[MENTION=631273]Chainfire[/MENTION], I sent you a PM concerning this as after the update, SuperSU now says PseudoPro.
[SuperSU] marc112:
Works like a charm again with this version.

Thanks for your quick action, Chainfire!
[SuperSU] audinswfc:
Can anyone tell me how I change to the green theme and new icon please? I've just updated mine from the Play Store (I was on v2.01 prior to this) and I can't figure out how to change it...

Apologies if this has been asked a million times already! :eek:
[SuperSU] creesch:
On my sony xperia Z2 (D6503) with android 4.4.4 (build number 23.0.1.A.0.167) updating of the binary is failing. I originally rooted it with this method after which it survived several OTA updates (which now that I think of it might be related since I did not have OTA survival enabled and only recently bought the pro version).

It seems it is still rooted since rooted apps continue to work and I get prompted to give them access by SU. I just can't seem to install the new binary and since I don't have a custom recovery installed I can't try the other method.

I am currently not at work so can't provide the proper logs, do you still want those posted to the thread you created a while ago?

edit:

It seems I don't have complete root (no system access), I guess that can cause the issue with updating the binary?
[SuperSU] HassanM:
Friends & [MENTION=631273]Chainfire[/MENTION]

I just updated my s4 i9500 to v2.35 but as soon as i updated the binary and rebooted the phone, my phone dead right after Samsung logo.. The screen goes blank and nothing happens...

Already tried pulling out the battery, reflashing the Rom (Omega v26) w/full wipe but no luck....

The only thing its letting do is going into custom recovery and I hope the download mode (which i havent tried so far)....

Plz advise me....

Your help will be really appreciated.... Thanks in advance....
[SuperSU] FedUpChoosing:
not got lux but have twilight, disabled that and all's good with the world again :)

Cheers
[SuperSU] gumbyx84:
After updating SuperSU via the Play Store, my system will continually reboot. The system stopped rebooting after SuperSU was uninstalled so I can only assume that is the cause of the app. I ended up flashing (the now current version of) SuperSU via TWRP. The issue now is that it contiunually asking to update the SU Binary on every reboot no matter what update method I use. I ended up restoring from a Nandroid backup to try and get back to a stable install. Has anyone run into a similar issue? I really don;t feel comfortable trying the update again until I get some feedback.
[SuperSU] Celestial Fury:
In SuperSU: Settings - Launcher Icon.
[SuperSU] TheInVisibleGoD:
I believe that's just because you haven't bought the Pro version... So only indicates that you have enabled Pro features w/o actually buying the Pro version!

Chainfire or someone else, correct me if wrong!
[SuperSU] Celestial Fury:
That is correct :) but read here too: #7516 #7530
[SuperSU] SignetSphere:
That shouldn't be the case. I've used the pro features by ticking it within the app and the app didn't change the name difference is... that was ver 2.16. I'm not entirely sure on ver 2.35 since I just bought the pro version (again... had some billing issues on my carrier don't ask lol).
[SuperSU] audinswfc:
Not showing for me.

Screenshots of all options available to me in these links...

https://www.dropbox.com/s/a8gapu2sz2ai7fp/Screenshot_2014-11-27-13-06-42.png?dl=0

https://www.dropbox.com/s/kxtyipq00snseug/Screenshot_2014-11-27-13-06-51.png?dl=0

https://www.dropbox.com/s/ta973kb4eva91gb/Screenshot_2014-11-27-13-06-59.png?dl=0

https://www.dropbox.com/s/9xpfjjyytpbm1ga/Screenshot_2014-11-27-13-07-07.png?dl=0

https://www.dropbox.com/s/7ct9alf8q36ksyj/Screenshot_2014-11-27-13-07-14.png?dl=0
[SuperSU] 17viper17:
I was having the same FC issues like marc112 on GB. I installed the one Chainfire gave him, rebooted and all is good no more FC's. Thank you Sir for your hardwork.
[SuperSU] Celestial Fury:
Here:

https://www.dropbox.com/s/ta973kb4eva91gb/Screenshot_2014-11-27-13-06-59.png?dl=0

Right below customization.
[SuperSU] Chainfire:
I am dealing with people bootlooping right now, this will have to wait.

As others have stated, in Settings, Launcher Icon and Theme options. However, you do need to be running on Android 5.0 for the option to be available.

Without the logs, it could literally be a million things.

http://xdaforums.com/apps/supersu/support-update-failures-t2907365

Correct.
[SuperSU] audinswfc:
All that gives me is a language option...
[SuperSU] fer456:
How I can help you to solve the error? How to get logs?

Thanks!
[SuperSU] Celestial Fury:
If you don't see it here then I've no idea.

* Chainfire, no problem.
[SuperSU] kryzeK:
Please get me a question: If I do root on my Nexus 4 with Android 5.0 official and unlocked bootloader, not receive OTA right?

But I can not even install "OTA captured" manually by TWRP or adb?

Thanks!

I like root, but do not want to reset my device completely only by an update 5.0.1 or 5.1.0 :(
[SuperSU] abym:
Update to v2.35 Working good on my device running Alliance Rom ...thanks. .???

G900F __ abym
[SuperSU] Srandista:
Yes, when you root device, you are gonna be unable to install official OTA updates. This apply to all methods of OTA installation, for TWRP and adb sideload too.

You have Nexus 4 though, so you don't need to worry, you can update your system by installing factory image without wiping user data.
[SuperSU] kryzeK:
Will we one day an update of SuperSU can back be like before? Or is it really impossible in Lollipop?
[SuperSU] gevans35:
I had a similar problem, but I think mine was caused by Triangle Away in conjunction with the Supersu update. My S3 got into a boot loop and the only thing I could get into was download mode so I flashed a recovery Tar I found, using Odin, which didn't install, but got me out of the boot loop so I was able to get into the phone in normal mode. Re-flashing PhilZ recovery through Mobile Odin cleared it out of recovery, where it kept trying to install when I went into recovery mode. All is back to normal except that phone still reports "custom" in device status, but I think I'll live with that for now.
[SuperSU] Srandista:
With current method, how SuperSU is installed it seems, that we will have install factory images, when phone will be updated. As for the future, its more question for Chainfire.
[SuperSU] bbernardini:
Absolutely no problems updating the app or binaries on a S5 running OptimalROM.
[SuperSU] dante2p:
Updated vía play store, SuperSU 2.35 work fine in CM 12, Taoshan (XPERIA L)

10xx, Chainfire ?
[SuperSU] jesssiii:
Try this: http://xdaforums.com/showthread.php?p=56421010

Or use Syslog from the play store, it's simple and free.
[SuperSU] MaxNXS:
Working great on my N5 with stock kernel. However I don't see the OTA survival option anymore (yes I have purchased the Pro version). Is that feature gone?
[SuperSU] 3DSammy:
I'm still on Lollipop with the SuperSU v2.20 boot.img that I installed using fastboot. Now I want to upgrade to SuperSU v2.35 so are these the best install steps:

- boot into the bootloader

- fastboot the stock lollipop boot.img then reboot

- From the playstore install SuperSU v2.35

OR

- Use the SuperSU v2.35 flash file and apply using TWRP

I'm open to an easier method but am comfortable using fastboot and/or flashing.

I read dam near every post in this thread and re-read the OP for this corner case but do not see a clear post about how someone that is using the SuperSU altered boot.img should upgrade to the latest version of SuperSU. I do not want to leave junk around due to the root method changing.

Thanks
[SuperSU] Bobboman:
anyone getting boot loops, tried flashing 2.35 on a moto G 2014 XT1064 running stock android 5.0, and its bootlooping

pity i was hoping this would allow me to get root access
[SuperSU] jesssiii:
I still have it on my LG G2 vs980. I'm on kitkat. Perhaps if you're on Lollipop it was removed in that?
[SuperSU] CyberpodS2:
I won't assume I can speak for Chainfire, so I'll speak for myself. Since he has already stated he is busy getting people's phones out of boot loops can we please stop asking about an icon color or some feature that is missing for maybe a day or two? This thread will be much more productive and it won't be getting bumped with topics not related to getting these issues squared away.
[SuperSU] IaKnightHawke:
I would agree with this too. Also, if you are NOT having issues with the program, it would be helpful to the developer and those who are to not have to wade thru multiple posts of those who report everything is fine on their devices, to find posts reporting a problem. Everyone here appreciates the work that goes into putting out a program like this. Be patient ....please. . Gary
[SuperSU] gumbyx84:
Right there with you. I had about a minute before phone would reboot so I was able to uninstall SuperSU abd stop the bootloop.
[SuperSU] FletchF:
As per the release notes (you read them, right?), OTA Survival mode was removed for L. It is unclear if or when it will return.
[SuperSU] hwlester:
Nexus 7 (2012) on KitKat 4.4.4 and rooted with WugFresh. Just updated to SuperSU 2.35. It kept asking me to update the su binary. I tried normal since I don't have a custom recovery and failed, so rebooted and tried again, but still failed. Clicked the option in settings to convert to system app (since I was reasonably sure this was done on the initial root). After rebooting, I'm no longer getting the prompt to update. I assume I'm good now? :)
[SuperSU] Cyrus_94:
I'm getting error message for the latest version of SuperSU v2.35, installed using .zip file via CWM and cache cleared.

"There is no SU binary installed, and SuperSU cannot install it. This is a problem!"

Phone

Brand: Lenovo

Model: A850+

CPU: MTK6592

Android 4.2.2 official rom

for those who are looking for previous stable version of .zip file

v2.16 http://download.chainfire.eu/589

v2.14 http://download.chainfire.eu/578

v2.13 http://download.chainfire.eu/567

v2.02 http://download.chainfire.eu/452 so far this the latest stable version that is working for my phone...

v2.01 http://download.chainfire.eu/451

v2.00 http://download.chainfire.eu/450

for more older version, please search by yourself, I lazy search edi.
[SuperSU] egingell:
[Reposted elsewhere]

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] sancho_panzer:
[MENTION=631273]Chainfire[/MENTION] just reporting all working fine with v2.35 on my both devices. Flashed with TWRP 2.7.1.0

Device:

Samsung Galaxy S4 (GT-I9505)

ROM:

CyanogenMod 11/M12 (KK 4.4.4)

Kernel:

Default CM11/M12 3.4.104

Recovery:

TWRP 2.7.1.0

Modem:

I9505XXUGNE8

Device:

Nexus 7 (Grouper)

ROM:

CyanogenMod 11/M9 (KK 4.4.4)

Kernel:

Default CM11/M9 3.1.10

Recovery:

TWRP 2.7.1.0
[SuperSU] Takamoto:
[quote name="Takamoto" post=57058060]what a pity, I was hoping for help..[/QUOTE]<br /><br />

<br /><br />

In your first Greenify screenshot, there is a reference to 'keyguard is unlocked' (keyguard = lockscreen, I think that part of greenify was badly translated in your language) ... probably it is inherent to the Pin protection offered as pro feature in SuperSU but I'm not entirely sure.<br /><br />

<br /><br />

Now I think we should ask to @<a href="http://xdaforums.com/member.php?u=631273" target="_blank">Chainfire</a> if this lockscreen permission may be stopped in free version without issues. :)<br/><br />

<br />

Can I solve the problem with the last supersu update? now i'm on supersu v 2.16<br/>

I've update the last version supersu..same situation.. :(
[SuperSU] DingoDingo:
Are you on NX 5.0 rom? I am and also don't have that option, maybe because SuperSu settings are integrated in System settings of the NX rom. There is no icon in app drawer, I can only access SuperSU through System settings menu.

EDIT
[SuperSU] CatThief:
Everything is perfect on my Nexus 5 LP. I'm loving that Power Toggles (airplane, mobile data, gps) works now with v2.35. Chainfire, you da man!
[SuperSU] jignesh2594:
binary!

after applying update on play store.

showing error while updating binary files!
[SuperSU] whitedavidp:
Binary Refuses to Update With New Release

Sorry, but on my Samsung Note N7000 running Android 4.1.2 (CWM and Philz kernel, otherwise stock firmware), the binary refuses to update. I have tried both normal and CWM modes. Normal mode just fails and after CWM reboot and install, SU still says the binary needs updating. I went back to my previous night's Nandroid backup. Cheers (and thanks)!
[SuperSU] [Lemmy]:
same here... Nexus 10 with today's update of Super SU, tells me the su binary needs updating but the update fails to apply.
[SuperSU] b3er:
So, if it doesn't matter for you if an any app can grant super user without your permission to do this, it's only your opinion. I don't think those who haves ROMs with preinstalled SuperSU, or those who downloaded it from market also believe like you.
[SuperSU] Pkt_Lnt:
removed graphic
[SuperSU] shaggyskunk:
:thumbup::)

Sent from Down The Rabbit Hole, using Tapatalk 2
[SuperSU] crachel:
Android does not completely allow end users to install apps with impunity, particularly when root access is obtained. That's not an opinion. So,

if

everything you say about SuperSU is true, it would just be 1 more way out of COUNTLESS a malicious app could wreck havoc. The end user has NO NEW consideration but whether they trust the app they are installing or not.
[SuperSU] dimebagdan65:
That's why we call ourselves superusers, not power users lol
[SuperSU] shaggyskunk:
Yeah, and Don't mess with Texas :)

Sent from Down The Rabbit Hole, using Tapatalk 2
[SuperSU] k2trill:
WiFi Tether....

anyone got this working with the latest WiFi Tether (v 3.1-beta14)??????????
[SuperSU] dimebagdan65:
There were issues? Works fine for me
[SuperSU] k2trill:
and u r using the latest version??
[SuperSU] dimebagdan65:
Of tether and SSU, yes
[SuperSU] sparksco:
Same here it works fine for me on the latest beta tether.
[SuperSU] k2trill:
The only way this works for me is to select the option "Grant" instead of Prompt in the settings. Also, WiFi Tether does not even show up under "APPS" where the list of root apps that are maintained are so, this is not hardly working the way it was intended to be. WiFi Tether only shows up in the logs....
[SuperSU] dimebagdan65:
No problem whatsoever here...
[SuperSU] k2trill:
What do u suppose is the problem then? I have tried installing WiFi tether and SuperSU every way imaginable as this is the ONLY root app giving me problems. I've tried wiping data and cache and all of that.
[SuperSU] dimebagdan65:
As you're on a Rezound, I'm afraid all I can do is speculate, as I'm on Evo 3D. Just wanted to show that it does play nice, I still have the superuser.apk in /system/app, but the binary isn't installed, just the SSU binary
[SuperSU] k2trill:
Same here with the superuser.apk and binaries......
[SuperSU] dimebagdan65:
Dang, we both have HTC hardware, this should be a no brainer lol. I also have SSU on the sd-ext2 partition (ext4 fs) via link2sd app if that helps?
[SuperSU] Basjoo:
Problem solved

Okay, i had the same problem as you guys. SU binaries would not update.

1. So I went to the market

2. Uninstalled SuperSU

3. Searched for Superuser in the market and installed the one with the android icon with eye patch

4. Then opened Superuser and closed it

5. Opened SuperSU (which was still present in my app drawer) and succesfully installed the SuperSU update :D

6. Voila, i have root acces!!

7. After that I re-installed SuperSU and deleted Superuser and it all works LOL haha
[SuperSU] Benzoman:
I'd really like to see an app that is "safe at 100%"

If you run any app whatsoever, or even turn your device on running stock from store, you cannot say you're 100% safe.

Give me a break. lol

Sent using XDA Premium HD app
[SuperSU] Thenhz:
You are having a go at a guy whom has gone to the effort to decompile a closed source su app and found a major exploit?

If an app like this can be bypassed then what the point of using it? These type apps exist only to protect you against rouge apps, if they can't do that then they have no point.

If this exploit was in a desktop OS it would be front page news! And yes I know supersu isn't in android prime, but it is intended for use in ROMs.
[SuperSU] alexlost:
"if it works, dont fix it". In other words... Since alot of people experience problems with this install I would wait with an uppgrade.
[SuperSU] tom1807:
Installed on my N4, N5 and N9 without problems by PlayStore, binaries got updated regular.

My N7 (2012) had problems in updating the binaries so I flashed by TWRP; problem solved.

Maybe my imagination, but with SuperSU v2.35 the devices feel faster again, especially the N5 which needed previously long time to boot.

Also my N7 feels now faster again

But as I said, maybe just my imagination
[SuperSU] hwlester:
I had the same issue with my N7 (2012) updating regularly. I don't have a custom recovery, so I tried the reboot and it still failed. I finally installed to system apps and the notification went away. Any idea how to tell if it actually updated?
[SuperSU] tom1807:
I guess when SuperSU doesn't complain about missing binaries, then you are good to go
[SuperSU] hwlester:
Pretty much what I was assuming as well. :)
[SuperSU] Phhoenyxx:
Galaxy Nexus (Maguro) - Stock 4.3

Update from the Play Store went smoothly. Everything works as expected. The only "issue" I can see is that the icon doesn't change in the Running Services section. I can set any icon and it will change in the launcher, but the old icon still shows in Running Services. FWIW, I did install SuperSu into /system before changing the icon. Could that be the reason?

Thanks,
[SuperSU] Cile90:
updated through ps ...

before had the issue of binary not installed ..now works perfect

Thank you