yashsingh1/xdaforums huggingface dataset:
[SuperSU] djlech:
Sorry should be Chrome, Firefox, and build in browser. The only way I was able to fix it, it was flashing KK again and applying older version of supersu.
[SuperSU] IronTechmonkey:
Images and everything else fine in Firefox & Dolphin here. SuperSU 2.37 on Moto AHD/MB886, 2 different CM 11 recent nightlies, PA Gapps Nano.
[SuperSU] Nimueh:
Firefox, eBay app + stock browser all work just fine and also show images.

S4 with latest SuperSU (2.37).
[SuperSU] CyberpodS2:
Ditto for the S5.
[SuperSU] thematrix-cbw:
Works fine on my One M8 with ARHD 22.1 and ElementalX. Great work!

Gesendet von meinem HTC One_M8 mit Tapatalk
[SuperSU] ecrudragon:
Can anybody provide me with Root file for S5 Lolipop stock rom?
[SuperSU] harsh.ea:
Facing this for quite some time. Tried re-flashing SUzip.

On stock rom lollipop.

Kernel: HellsDoctor L13.

Please help
[SuperSU] TheImmortal1983:
I keep on getting the same error as [MENTION=4790604]harsh.ea[/MENTION] on Lollipop, reboot after reboot (sometimes it works, sometimes it doesnt...).
[SuperSU] harsh.ea:
Yeah same! Even flashed system.img again just to be sure
[SuperSU] 1ce8reaker:
I solved with a complete unroot and flashing the zip file of supersu in recovery.
[SuperSU] Jax Teller:
[MENTION=631273]Chainfire[/MENTION] does initial root of LRX21O factory image for Nexus 5 still require using CFAR or we can just flash SuperSU 2.37 from TWRP?

Thanks :)
[SuperSU] Chainfire:
TWRP ZIP is now enough.
[SuperSU] Jax Teller:
Great. It's so much easier to only have to flash a zip file.[emoji4]

Thanks again for all your hard work.
[SuperSU] dadoc04:
Are you running adaway?

Sent from my NEXUS 6
[SuperSU] djlech:
No but I'm running adfree. I will try tonight without adfree.
[SuperSU] Chainfire:
Just posted the v2.38 BETA in the BETA thread here: http://xdaforums.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133

Should work a lot better on the SGS5 Lollipop firmware. Interesting story, but too tired to type it up now. Let me know how it works.
[SuperSU] occtec:
[MENTION=631273]Chainfire[/MENTION] is there any point in testing this on nexus 5 if main changes are for the S5?
[SuperSU] egingell:
There's always a point in testing.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] xdamami:
After 5 reboot root V2.38 it continues work SGS5 thanks King!
[SuperSU] Droid2drummer:
[MENTION=631273]Chainfire[/MENTION]. Lmao as i caught the 2.37 (gingerbread) rofl. Good one. Nice and casual.

Sent from rotary technology Phone
[SuperSU] beton87:
I have an Oppo Find7a with LVM and lated 5.0.1 build from maxwen from this forum.

Supersu 2.37 flashed in recovery does not work, guys from Omni said to post here. Error popup says that phone is not rooted. Logcat:

http://d-h.st/PB3

Gonna try beta in a moment

Edit: same message on beta: There is no SU binary installed and SuperSU cannot install it. this is a problem.
[SuperSU] zelendel:
Works fine here on 5.0.1 HTC one
[SuperSU] Andriy U.:
Version mismatch?

Updated from 2.16 to 2.37 via apk, works fine on Galaxy N9005 (stock 4.4.2). Thanks!

$ su --version
2.35:SUPERSU
[SuperSU] Chainfire:
Omni issue confirmed, will be fixed next beta version (tomorrow?)
[SuperSU] miloytyn:
Versions 2.36 and 2.37 updated only SuperSU, but not su binary.
[SuperSU] commencal661:
Explaining that is useless. I tried once, and they didn't get it. It's sad :/
[SuperSU] JulianJenner:
SuperSU 2.38 works excellent on LGE-760 AOSP-Lollipop 5.0 by magician [MENTION=3519950]artas182x[/MENTION]
[SuperSU] grynnan:
Have anyone tested this version (2.37-2.38 beta) of Chainfire Supersu on Oppo Find 7?

(Find 7, comess with busybox already installed on the phone, and there is always some issue with find 7, and chainfire supersu)

At the moment, only way to have a superuser on find 7 is to use a costum rec. like twrp, install chainfires supersu zip, and derectly after, without re-boot install clockworkmods superuser...

Chainfires doesn't work on the Find 7, and clockworkmod doesn't install as it should, but using them both in that order, works.. go figure..
[SuperSU] :
Work Fine In Blu Studio 5.0K :)

Best Regards
[SuperSU] Chainfire:
v2.39 beta out now, with more SGS5 and Omni5 fixes.
[SuperSU] iamnotkurtcobain:
Thanks buddy!
[SuperSU] Revontheus:
finally! supersu works for the alpha 5.0 for my z1c

thanks!
[SuperSU] melorib:
Thanks, where to download :confused:
[SuperSU] iamnotkurtcobain:
http://download.chainfire.eu/638/SuperSU/BETA-SuperSU-v2.39.zip
[SuperSU] melorib:
Thank you, I realized it has a different thread for each new version :o
[SuperSU] ymDroid:
Nexus 7 Survival Mode

My Nexus 7 2013 is rooted using towelroot, and Supersu 2.37....

Does anyone know if I take the OTA for Lollipop, will SuperSU's Survival Mode work?
[SuperSU] mindmajick:
It will not.
[SuperSU] ymDroid:
[/COLOR]

Ok.

I knew you couldn't OTA once you were on Lollipop, but I didn't know if going from 4.4.4 to 5.0.1 would be an issue.

So I either have to factory reset to take the OTA, or factory reset to unlock the bootloader.

Either way, I'm wiping., huh?
[SuperSU] vlt96:
Desktop OS protection:

Windows Vista or later: "the application wants to make changes to computer"(yes/no)

Ubuntu:"Sudo password for <user>"

So desktop OS have it build in... not for older than Windows Vista and I think Mac has no access whatsoever right?

Seek the signature below the line;)
[SuperSU] DarkhShadow:
Well if the "exploit" he found was the SU binary auto-grants root access if SuperSU is uninstalled then that's a feature Chainfire added

Sent from my ice cream powered Nexus S
[SuperSU] b3er:
No, exploit works when SSU is installed.

As i've sayed earlier, the SSU code is unsecure.
[SuperSU] Thenhz:
And that was clear from the original post. Shame for you this isn't a standard package in android because if it was Google would be writing you a big cheque right now.

Basically the exploit means that supersu doesn't protect you against rouge apps getting root which is it's entire point. After no one cares about ligit apps as you know what they are doing with it!
[SuperSU] dimebagdan65:
Seriously... For three days now...? Where are the mods at?
[SuperSU] b3er:
I'm working on programs security and development more than 10 years, so i'm sure that i'm writing here.

I've written pm to chainfire, describing this problem, but he don't reply. I wait a couple of weeks, if no one has interest to fix this vulnerability, the one way to change the situation is to publish here the exploit code.
[SuperSU] dimebagdan65:
Here's a thought, write your own root access control app... But talking about openly posting someone's private work...? You don't wanna be on XDA much longer do ya...? Go...back...under...your...BRIDGE! Haven't you been fed enough?
[SuperSU] b3er:
The exploit code is MY private work, so i can publish it anywhere in anytime, i just respect chaifire and what he did, and I want his applications are better and safer. It seems you are not completely competent in the subject.
[SuperSU] dimebagdan65:
Duh... If I was a coder I'd be coding right now. I'll be the first to admit I am completely INcompetent at coding (I can throw together a Hello world, but that's about it lol), I just know this type of crap is NEVER productive, and you wonder why CF hasn't PM'ed you back...? Find another project (by the way, what ever came of that universal global carrier code database you were trying to put together...?) Yes, I did some digging, do the same, you'll see, I'm here to help and educate. You seem to NEED for your point to be validated for some reason, I'm just trying to understand what it is exactly that you hope to achieve here...? So my pointed question to you is, what do you want CF to do...? You claim to have the skills, reverse engineer it, add in your fix, and release it. Or did you just stop at finding an "exploit" and not bother with trying to come up with a solution? Long story short, this entire fiasco should have never seen the cold light of day, it should have been confined to PM's between you and CF but apparently he didn't respond so you decided to seek attention elsewhere... Your bridge is calling...
[SuperSU] b3er:
Yep, i have a solution, but this solution needs to be implemented in chainfire's private source code. If this app has an open source, i've already posted the patch to eliminate vuln. I can't modify the sources bc i don't have it and i can't modify the other person private work. The man who's writing security management app must have a responsibility to the community using it.
[SuperSU] dimebagdan65:
And the community is fully behind you and is clamoring for justice... Oh wait, no, they're not... The community (for the most part) loves this app and trusts CF due to his track record and previous projects... Last thing I'm saying on this. I have a feeling the issue will be resolved one way or another very soon... For now, let's have a slow clap for the lone gunslinger sticking up for us poor, clueless users... *clap*... *clap*...*clap*... Come on, guys, give the hero a hand!
[SuperSU] Chainfire:
Some nice activity here :)

Let me just start with saying that I haven't replied to anything because I've been out of the country for the past few days, and stuck in airports due to (not mine!) planes crashing, etc.

I'm just reading about this now and have contacted b3er, to see what this is all about.

Please do note that open source vs closed source discussion is not welcome in my thread - nor are flaming and personal attacks.
[SuperSU] vlt96:
People should trust you, you are the most talented dev around, if they think you would brick phones or steal information, then they should use normal superuser...

Maybe you have some messy coding, can't be understood by others, I don't care, keep it closed source, people use iPhones, people use Windows, people use Mac, people install untrusted games (on windows), and they say you are evil, ha

Seek the signature below the line;)
[SuperSU] shaggyskunk:
With some 7 Billion people on this Planet, I'd imagine that any "Thinker" would welcome legitimate questions about their "process"... After all, Testing theories can only make the end result stronger.

I don't pretend to understand the guts of the mechanics, but I sure appreciate the results! :)

Sent from Down The Rabbit Hole, using Tapatalk 2.
[SuperSU] k2trill:
Guess it's just not meant to b with me an this app....
[SuperSU] Chainfire:
SuperSU has been updated to v0.89 !

Security issues brought to light by b3er have been fixed.
[SuperSU] shaggyskunk:
Kudos to Both Chainfire & b3er.... The "Thinkers" Rise to the Top! :):thumbup:

Sent from Down The Rabbit Hole, using Tapatalk 2.
[SuperSU] Note_E:
Thank you b3er

Edit: and of course you too Chainfire ;)
[SuperSU] Pkt_Lnt:
I want to directly apologize for the tin foil helmet image that I posted. You have contributed greatly, and in my limited knowledge, I did not understand. Sorry, and I removed it.

Thank you for the security contribution.
[SuperSU] shaggyskunk:
Now, That's Class! :thumbup:
[SuperSU] mindmajick:
Wrong place for this but... What I did was flash the boot.img and system.img from Google in fastboot. Kept all my data and everything is working fine. PM me if you have questions since this really isn't the place...
[SuperSU] Evo_Shift:
Flashing 2.37 in TWRP works for the 5.0.1 update on the Nexus 6. Nice and easy. Thanks
[SuperSU] CyberZeus1977:
Does 2.37 work on Nexus 4 and Lollipop 5.0.1?
[SuperSU] Ja_som:
There is no reason to not work...
[SuperSU] CyberZeus1977:
I know that when 5.0 was out, SuperSU didn't work. I was wondering if it happens also with 5.0.1.
[SuperSU] Ja_som:
But there are really small differences between 5.0 and 5.0.1, so when SuperSU works on 5.0 it should work also on 5.0.1, and I see in your signature, that SuperSU works on 5.0
[SuperSU] SanoJA:
Supersu 2.39 and knox

Gonna root my xxugnj8 4.4.2 with the cf autoroot but i read different things about knox disabling. Some say u press OK some CANCEL when supersu asks to disable knox. What should i do?
[SuperSU] Danygold:
No more ext sd

Please I need help

I have a Samsung GT-I9505 jfltexx with kit kat 4.4.2 rooted with towel root when it just came out

Worked fine for a long time but in my last update of supersu v2.37 from google playstore all ok working

Well binary using normal but something happens I lost the access of the ext sd card I tried to unmout but it said insert sd card tried with a 3 others card same problem went to Samsung service changed the card slot but same problem so they put it back in and tell me they can do more with the software because my mobile is from Switzerland and live in Nepal

Also at the same times titanium was updated so I have no idea where the problem came from

If you can help me I really don’t like to lose root what can you suggest

Thanks for the good work
[SuperSU] adrman:
Yes, no problems. I don't remember the timeline of 5.01 vs. 2.37, but 5.0 and SuperSU (the beta release) worked fine at the time as well, whatever version it was at.
[SuperSU] scottocs:
I have noticed this problem since I started using SuperSU months ago.

Is it just me or does the "Default access" set to 'Grant' not work?
[SuperSU] jesssiii:
Works fine. Need more info from you for anyone to help.

LG G2 VS980
[SuperSU] theprodigy85:
Does the Full Unroot option still work as described? I ask because because prior to doing the 5.0 -> 5.0.1 OTA update on my Nexus 4, I did the Full Unroot in SuperSU. But upon sideloading the 5.0.1 update, I receive the error "/system/bin/install-recovery.sh" has unexpected contents, Error (Status 7)".

Aside from rooting Android 5.0 with the initial 2.35 (and subsequently updated to 2.37), my phone is completely stock.

I've used the Full Unroot option prior to performing any update in the past (for KitKat updates) and it has worked fine.

Just wondering if this is a SuperSU issue involving the Full Unroot option not restoring everything completely to its defaults or is it something else on my end.
[SuperSU] Pkt_Lnt:
Lollipop changed how OTA is applied, not you or SuperSU. You have to flash system.img to take OTA.
[SuperSU] Android-Andi:
Rom/Kernel missing a policy or SuperSU ?

android-andi@buildbot:~/Downloads$ adb shell su -c dmesg | grep 'avc: '
<4>[ 4.811096] C1 [ init] avc: denied { set } for property=supolicy.loaded scontext=u:r:sysinit:s0 tcontext=u:object_r:default_prop:s0 tclass=property_service
[SuperSU] jcfunk:
search, could not find. Is there a way to make SuperSU use system mksh by default?
[SuperSU] egingell:
SuperSU only adds one executable file. The sh binary already exists on the system and is untouched... and is actually a symlink to mksh.

TL;DR: You're already using the system default mksh binary.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] Chainfire:
How can you be smart enough to know about ^^^, yet not post information about your device, firmware, build, etc.
[SuperSU] Android-Andi:
Think i fixed it late in the night:

https://gerrit.slimroms.net/#/c/16633/15/selinux/sysinit.te

Galaxy Tab 2, SlimLP alpha 0.8 on latest source.

Send from OnePlus One using Tapatalk
[SuperSU] peikojose:
It seems strange but SuperSu app doesn't show in the app drawer.. I don't get it.. Flashed 2.37 zip I got root but there is no app... Nexus 5 slimlp 0.8 elementalx 2.04
[SuperSU] aavvaallooss:
Download app from Play Store
[SuperSU] peikojose:
Says installed buy cannot open or uninstall it (as an traditional app)
[SuperSU] Chainfire:
I don't agree. Where does this sysinit context suddenly come from? It's not in AOSP.
[SuperSU] Android-Andi:
Let me dig around, i am new to all this SELinux stuff, maybe from slim.

Send from OnePlus One using Tapatalk
[SuperSU] AkiraProject:
I have downloaded UPDATE-SuperSU zip from chainfire website then flashed it through TWRP now it's working fine again. I won't update supersu from google play store again because if I do that supersu becomes an user app :)
[SuperSU] jayplusone:
You can install as system app through settings..

Sent from my Nexus 5
[SuperSU] furboom1240:
No R/W Access to Rooted Filesystem

hello, [MENTION=631273]Chainfire[/MENTION]

I have an HTC One M8 GPE that is rooted, S-Off, and running CyanogenMod 11 M12 stable. I'd like to know despite all of this, why I cannot edit the filesystem despite mounting all seven partitions to R/W via ES File Explorer's root explorer function (granted superuser access, too!). By the way, I purchased SuperSU Pro on 2/28/2014 from the Play Store for $2.49 with the same email associated with this XDA Account.

I'd really like to edit my hostapd.conf file because its settings for 802.11n functionality and SSID Broadcast can't be changed in a GUI. I was able to do so on my previous device (SGH-T699) with no issue. I discovered, through Root Checker Pro [joeykrim] that there is a line of code that says despite me having root access, I have been denied filesystem access, which explains why any changes I make to hostapd.conf are reverted if I toggle the hotspot.

I certainly hope anyone here besides Chainfire can point me in the right direction, as I understand staying ahead of new security implementations is Chainfire's specialty, and it's not fair to tie him up, to say the least.
[SuperSU] shinra00:
do you have to always install as system app after each update? Or once done it sticks? thaks
[SuperSU] jayplusone:
After every update from google play [emoji4]

Sent from my Nexus 5
[SuperSU] gothicasshole:
Ok i wasnt able to root my nexus 6 with cf autoroot i found a nother tool kit i was having driver issues i finally got it unlocked and pushed twrp 2.8 to my nexus but after that the tool kit no longer recognised the phone (those pesky driver issues) my question is if i flash the su update 2.37.zip through twrp i should have root rite?
[SuperSU] SamuriHL:
Yes. The NX6 is very touchy with sideload drivers. No idea why, but, I've had problems too. But anyway, boot up twrp and flash the supersu zip in that and you'll regain root. I went through this earlier this week.
[SuperSU] Strephon Alkhalikoi:
I was a bit bored. After restoring my lost SIM unlock on my Galaxy S4, I decided to look once again into the binary update issue I had been having with my Dell Streak running Gingerbread. I can now confirm that the binary update issue only occurs on the ROM I released for the Dell Streak based on Cyanogenmod 7. I switched the Dell Streak over to the ROM I released that was based on the last stock ROM, and had no problems whatsoever with updating the binary. Therefore, either the changes to SuperSU have rendered it incompatible with the CM7-based ROM, or more likely is that the changes I made to the ROM broke something.

In the end, even though I did get SuperSU to work on Gingerbread, I'm still going to advocate dropping support for Gingerbread soon.
[SuperSU] rogersb11:
On htc m8 you need to be running a kernel that hacks the htc system control or all attempts will be futile
[SuperSU] furboom1240:
NOT helpful at all

Oops, I gave the right response to the wrong thread. Sorry about that. I have asked this question in more than one thread, and I though this response was the one when i mentioned "redpoint73". Shucks.
[SuperSU] rogersb11:
I was gonna say lol. Not helpful?! I told you what you needed to do haha. I know elemental has it from flar2 but that's the only m8 kernel I've ever actually looked at since I have a Note 2
[SuperSU] schwem:
I have an issue as of today! I have been using the newest playstore release of supersu since its release without issue but today anytime my apps request supersu access the prompt will appear but I cannot click on the prompt at all. This has never been an issue for me in the past. If I go to supersu setting and choose grant as default action when root is requested then it grants supersu access no problem but if I leave the default request as prompt I cannot grant access as I cannot click on the prompt. Please help as I am not to keen on allowing evering as default. I like the control over apps I have with prompt window. I am running cloudy G3 on lg g2 vs980 with dorimanx kernel and have been for 5 months without any previous issues with supersu. I tried uninstalling and reinstalling update without success as I still cannot click prompt window. Thanks for the help in advance

---------- Post added at 05:54 PM ---------- Previous post was at 05:43 PM ----------

Nevermind turns out for some reason the tapjacking option was selected not allowing me to click prompt window if any other app was open including the one that was requesting access! Although I'm pretty positive this option was always checked and this was never an issue in the past. Kind of strange but with the tapjacking option unchecked I am now able to click on prompt window when access is requested. Any ideas on why this is all of a sudden an issue?
[SuperSU] Pkt_Lnt:
Screen brightness / dimming apps are the most likely cause, especially Lux.
[SuperSU] schwem:
Really? I use lux as the built in auto brightness is terrible! Is it ok to use supersu with tapjacking off? It works with this disabled
[SuperSU] Pkt_Lnt:
Yes, this lux issue has been discussed at least 50 times sin the thread. Tapjacking is a security feature, disable it if you wish, or add SuperSU to the sleep list in Lux to keep tapjacking.
[SuperSU] Mike B.:
This has been discussed ad nauseum in this and other threads. The tapjacking protection feature introduced in recent SuperSU versions is intended to protect users from apps that create an overlay over the screen and can potentially "hijack" sceen taps. It can be disabled but then the potential risk remains. It's a NICE feature and the various "SuperSU prompts doesn't respond" reports merely confirm that it's working exactly as intended. It also confirms that users seldom search threads or read instructions! ;)

Some brightness control apps, including Lux, use such a screen overlay to alter the hue and transparency of the display. SuperSU has no way of distinguishing between legitimate overlays and "evil" ones. Lux happens to have a white list to which you can add SuperSU so that the overlay is not displayed over the SuperSU prompts. Other apps may or may mot have a similar option.

Unless you're absolutely positive you need the screen overlay, you may want to consider using brightness apps that only adjust brightness without any additional wizardry. I suspect that it's more than sufficient for many users and happens to be much less conflict-prone and resource-intensive.
[SuperSU] schwem:
Thanks
[SuperSU] Android-Andi:
Unable to find it atm, any proper way to find out?

Send from OnePlus One using Tapatalk
[SuperSU] Giowi:
Hello,I installed duos android emulator on windows 8.1 but i have trouble updating binaries files. The emulator is rooted. Every time i reboot the emulator , SupeSu asks me to update the binaries. I installed Supersu via playstore because the emulator has no reovery.could anyone help me?
[SuperSU] mindwalkr:
Just flashed the update zip (2.37) from Chainfire's website. Used Clockwork 6.0.4.5 to do it. Before flashing the zip I cleared the Cache., then

- Flashed the ZIP

- Chose to reboot

- A warning came up that the su binary permissions could have been lost and that I could chose to restore them, which I did.

After doing the above, my phone restarted but got stuck forever in Android Upgrading "Starting Apps".

Pressed the power button long enough to restart and it is now working again... which is good news :)

But I can't help but wonder why did it get stuck in the boot ? Any ideas ?
[SuperSU] kingvortex:
"Fixing" the su permissions is probably what caused your problems. It actually breaks root in most cases and causes problems. If you ever see that message again, select "No".

Sent from my C6603
[SuperSU] CyberpodS2:
Seeing something odd, that I don't know how to search for an answer. I'm running this rom:

http://xdaforums.com/showthread.php?t=2971430

If I flash the 2.39 beta and reboot, it shows correctly until I reboot. Then it's showing 2.16 and let's me upgrade to 2.37. When I reboot after the upgrade, it shows 2.39 pro again till the next reboot then I'm back on 2.16 again. If this is a rom issue, please let me know and I'll take it there. I figured maybe someone recognizes the behaviour.