yashsingh1/xdaforums huggingface dataset:
[SuperSU] Emmie0702:
Help! Desperate.

Hey guys. I'm in a bind. I connected my Galaxy S5 to WiFi & Supersu updated without me realizing it. I tried to update binary thru standard download & re started my phone as directed. Once booted none of my apps would work. Kept getting popups that yahoo, Google services, etc. Has stopped. Did a hard reset & now I can't get connected to the Internet thru WiFi or mobile. Help! 8 using a friend's phone to post this. I am out of town without a computer & now a working phone. What do I do?
[SuperSU] khairulez:
Wipe cache and dalvik-cache via recovery then reboot.
[SuperSU] JulianJenner:
Thank you [MENTION=631273]Chainfire[/MENTION]! v2.14 works fine on my LG Optimus L9 P760 with CM11 (Android 4.4.4) by artas18x
[SuperSU] Emmie0702:
I don't have recovery on my phone. It wasn't available when I rooted & i never got around to flashing one. Is there another way? Would re rooting help? I will be able to do that tonight when I get back home.
[SuperSU] egingell:
Every Android phone has a recovery from which you can wipe the dalvik cache. It comes with it... from the factory.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] quakeaz:
Eh, well.. I've never seen a stock recovery that can wipe dalvik, not saying they don't exist, but all I've seen just wipe standard cache partition.

Anyway, Emmie0702, if you still have root access, you can wipe dalvik cache by manually deleting the contents of /data/dalvik-cache. Don't know if this will solve your issue, but it's a way to try..

EDIT: If you did a factory reset, dalvik cache is cleared anyway, as the whole data partition gets formatted. This is unlikely to fix your network issues in my opinion.
[SuperSU] egingell:
The stock recoveries on both of my phones can wipe the dalvik cache. Maybe it's another Samsung thing, I don't know, but they do.

Edit: Kind of a moot point, though, since you can indeed just manually delete that folder.

Edit: I just checked. Turns out I was wrong. There are two lines with "cache". I'm guessing I misremembered one of them for dalvik cache.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] quakeaz:
I'm still waiting for Google Play to update. It's showing a release date of 10/15, but still version 2.01. Looking forward to trying 2.14 since I have been having issues getting the su binary to update on my SM-G730A with 4.4.2.
[SuperSU] ccgx:
I also have Problems updating the binary on my Xperia Z2 (D6503), Stock Firmware 4.4.2. Tried rebooting a number of times and even wont get it to update the binary after the 2.14 update.
[SuperSU] vadim-zh:
It doesn't, I installed downloaded zip for recovery.
[SuperSU] aaroncal:
Tried flashing in twrp and after reboot it still says 2.01
[SuperSU] Chainfire:
If you find the app that causes the reboot, let me know. You're not the only one this has happened to, so I'd be very happy to know what the cause is.
[SuperSU] Chainfire:
Due to the barrage of update failures and how hard it is to keep track of them and finding the issue, I've opened a new thread on the subject.

It can be found here: http://xdaforums.com/apps/supersu/support-update-failures-t2907365

If you're still having update failures, please report there. Please point others who are reporting update failures to this thread as well. Hopefully doing it this way will lead to better/faster solutions.
[SuperSU] appman1234:
I have flashed the SuperSU v2.14 to my Redmi 1 this morning. It works properly without any problems for about 8 hours.

Thanks!
[SuperSU] Murshad007:
I have flashed 2.13 some days before and working fine.

Today after it updating from Playstore . 2.14 my network not found..

I clear cache, dalvik cache. But no help..

I reflashef 2.13 and install it as system app..

Then reboot..

My network back again...

Sent from My LG Optimus G F180L Sling 2.2.2 stock 4.4.2 rooted
[SuperSU] AriStos13:
i am in the final stage of rooting me htc one mini but i have a problem.. when i go to recovery menu(TWRP) and hit the install button to install the superSU file i cant find it.. i made a folder named root and put it in there but the folder is empty when i try to install it.

what can i do?
[SuperSU] jesssiii:
You quoted his post telling you to post update issues in another thread, then proceeded to post your update issue. ?
[SuperSU] Emmie0702:
I don't see anything for it in recovery. I am unable to open any Google based apps, Gmail, maps, YouTube, etc. I get an error that says "Unfortunately, [app] has stopped.". Im also getting the "Unfortunately, the process com.google.process.gapps has stopped" error. What do I need to do? It seems as though it's not reading my SD card as well. It's showing I don't have pic or that one is even installed. I can make calls but that's about it. No Internet, no connections, no apps. Can even sign onto my gmail to be able to download any app. I have a titanium back up but can't download the application to try to restore everything.
[SuperSU] mir2ruso:
Recently I am having problems with the upgrade of the application SuperSU own.

In one of my jumps correctly terminals me the OTA update the 2.13 and now 2.14.

The fact is that in another terminal to upgrade 2.02 always had been able to update OTA without any problem but now mysteriously can not update by google play at 2.14 and tells me I'm on the latest version when it is not so yaq ue with other mobile gets me is that the last 2.14.

Is that not coming from google play through the PC puts me there is a new update and tells me that the latest is 2.01.

Yesterday I had to upgrade my second cell from the recovery to 2.13 and has left me with no problems and binaries have been properly installed.

And today I updated it using the recovery to 2.14 without problems.

I do not understand what is happening.
[SuperSU] Chainfire:
Staged rollout. Play is only offering 2.14 to about 20% of devices at this time.
[SuperSU] Chainfire:
There is no difference between 2.13 and 2.14 aside from some installer code... I don't think this is actually a SuperSU issue.
[SuperSU] mir2ruso:
So if now I have updated to 2.14 through recovery I no longer jump anymore by Google Play?
[SuperSU] zadigre:
play store might not have the latest version because it's a progressive roll out... not everyone has access to the latest version... but after a few days, everyone should have it.

that being said, it you already upgraded to the latest version with the zip file, you don't have to worry with what is offered on the play store.
[SuperSU] mir2ruso:
I'm still right in Google Play 4.9 and have not skipped my 5.0

But my question is clear now that, if I upgraded to 2.14 via recovery SuperSU I want to know is if in the future I will be able to do with Google Play or whether on the contrary and only I can do through recovery.

Quizás quisiste decir: Muchísimas gracias por vuestra ayuda.

Thank you so much for your help.
[SuperSU] AriStos13:
come on guys no one can help?
[SuperSU] USBhost:
deleted
[SuperSU] dorimanx:
Really helping to solve it. Well done.

Provide more info for developer.

Sent from my LG-D802
[SuperSU] Pkt_Lnt:
Chainfire has posted many times what he needs. He has also said that no one has posted the results of what he asks. That is why there are 20 pages of useless posts.
[SuperSU] BriVG:
Chainfire asked for logcats to help debug the problems, that means you get him a logcat.
[SuperSU] USBhost:
Ok when i will
[SuperSU] netfortius:
Since upgrading to 2.14, after opening the SuperSU app the apps and logs tab just show the spinning wheel, for as long as I leave SuperSU running (many minutes). Only the settings tab works ok. The actual apps needing root access work just fine, as before the upgrade. Any idea where I could look into why this behavior?
[SuperSU] Chainfire:
So I guess I'm just going to post this link every 10 posts or so ...

To help fix issues, follows these instructions for making a report:

http://xdaforums.com/apps/supersu/readme-supersu-forums-t2868322
[SuperSU] dhatch93:
this really isn't an issue with SuperSU. if you can't find a file within TWRP you should ask in a TWRP thread. i really doubt saving SuperSU caused your recovery to stop seeing files.

have you saved other zips to the same folder to see if only supersu isn't showing up? if it's on an external SD, is it showing as mounted in TWRP? but again, really should be discussed in a TWRP thread, not here...

also you should allow more than three hours for a reply... time zone differences, nobody else having this issue, etc
[SuperSU] ayoubij:
Why isnt the new updates pushed to the playstore anymore?
[SuperSU] Dor-b:
update

hi,

quick question, i have the 2.01 version on my lg g pad 8.3 (no Twrp) .

what is the best way to update ? if i run the apk it will not cause any problems?

thanks!
[SuperSU] USBhost:
(bug v2.14) ( su / ) not working

Logcat http://pastebin.com/T3mZGXgU

of su /

last working v2.02
[SuperSU] dhatch93:
why don't people read the last few pages before asking questions? ;)

this was just answered in post #6847...

"Staged rollout. Play is only offering 2.14 to about 20% of devices at this time."
[SuperSU] AriStos13:
first of alla you are right for expecting answer in a little time.

i saved another zip file( a subtitle) and it didnt show up either.. because i am new to android and xda can you help e finding the right thread to ask?

thanx alot.
[SuperSU] dhatch93:
Sorry Chainfire - last non-SuperSU post on this

AriStos - get to know the forums for your phone - it should be in there (likely the android dev forum, but ask in the "q&a/help" forum there if you need more help)

http://xdaforums.com/htc-one-mini
[SuperSU] Cyrus_94:
v2.14 working great for my Lenovo A850+ (in before v2.13 not working)

thanks chainfire :)
[SuperSU] quakeaz:
Version 2.14 fixed binary update issues for me as well on SM-G730A / 4.4.2. Thank you!
[SuperSU] sancho_panzer:
Not for you, you're lazy so you don't deserve it.
[SuperSU] jrbxx7:
2.14 works great on all my devices. To all having problems u need to provide the correct info for chainfire to do anything. And expecting an immediate answer is just poor etiquette. People have real lives and chainfires development is a bonus not an expectation.

NoTe III'd
[SuperSU] ayoubij:
Haha im not lazy i flashed the zip file to get the update but im just wondering why it wasnt updated in the playstore
[SuperSU] quakeaz:
As previously stated by Chainfire, it is a staged rollout.
[SuperSU] zadigre:
where in Lux can I find this whitelist? I've tried looking everywhere... and I did not find it.

I do not have any problem with Lux/SuperSU right now because I authorized all my apps before installing Lux.... but I just want to make sure I'm prepared in case I need this option.
[SuperSU] Taomyn:
Settings, Advanced, Sleep List
[SuperSU] zadigre:
ok thanks!

name in French (List de veille) wasn't very clear on that...

even in English, it's not clear what this feature is doing...
[SuperSU] Linuxx84:
Hi huys, I have a problem with SU binary. When I manually inject SuperSU and SU in my rom, after flash it ask always to update binary. Why? With SuperSU v2.01 there are no problems.
[SuperSU] zadigre:
you should go there for error regarding the update process :

http://xdaforums.com/apps/supersu/support-update-failures-t2907365
[SuperSU] Taomyn:
Just received an update for Lux - apparently with Android 5 "sleep" is currently broken, and awaiting a workaround. Oh joy.
[SuperSU] eng.stk:
Before anybody asks SuperSU 2.14 doesn't work with Android 5.0 preview.

Now, let the man work :fingers-crossed:
[SuperSU] mendozaram:
F5 F5 F5 F5 F5 F5 F5 F5 xD (Looks so great lollipop) :D
[SuperSU] Stanlehh:
Hey guys,

Any one knows why whenever an app requires superuser permission and the window pops up but I cannot select grant or dent at all, it's like it's not responding to my touch. Thereafter it says denied access.

However I can drag the notification bar down as per normal.

Hope anyone who has experienced this before could share what's the issue.

Thanks,.
[SuperSU] kingvortex:
If you have an app that uses a screen overlay like Lux, then the new tapjacking protection will stop you interacting with the popup.

This is mentioned several times in the thread already.
[SuperSU] Stanlehh:
Thanks man!

Disabled tapjacking and it's all working fine now.
[SuperSU] billyx1:
Same for me, doesn't work with updated preview.

I hate google for updating the security with every release!
[SuperSU] USBhost:
Can we turn it off?
[SuperSU] DragonHunt3r:
Interesting... http://www.xda-developers.com/android/supersu-2-13-android-l/
[SuperSU] madd0g:
That was for previous L preview.
[SuperSU] MrKaon:
Root achieved in new L preview:
[SuperSU] Chainfire:
I don't consider setting selinux to permissive a proper root.
[SuperSU] hlxanthus:
How could you, when it would bypass one of the new LP features . .
[SuperSU] Centurion13337:
Thanks for sharing, love supersu! :) Keep up the good work!
[SuperSU] Bexton:
Hey Chainfire, while checking why SuperSU v2.14 doesn't work with the latest LPX13 preview build on the Nexus 5, I noticed that the following part of the updater-binary could be the issue:

ui_print "- Extracting files"
cd /tmp
mkdir supersu
cd supersu
unzip -o "$ZIP"

BIN=/tmp/supersu/$ARCH
COM=/tmp/supersu/common

The problem seems for me, that /tmp does not exist (at this point). thus cannot cd into.

So, what it does is to create the supersu directory in root not in /tmp and in return the paths for BIN and COM are invalid.﻿

Hope it helps. Otherwise just ignore. ;)
[SuperSU] ramjet73:
My question is what comprises a "proper" root authorization mechanism in an enforced selinux environment? I'm very interested in the answer since one of the points of emphasis of Lollipop is supposed to be security, including the KNOX pieces.

I'm not a selinux guru and am trying to learn more about it, but my understanding is that each exception to the default policies (like root access) needs to be authorized with a formal policy, maintained in a specific format by a system administrator (reference). For a rooted phone or tablet the user has to be accepted as the "administrator" but will not be able/willing to code the detailed policies. Does that mean that a "proper" root utility will generate and commit the selinux policies required to allow access to resources used by an app requiring superuser permissions?

In no way am I trying to be argumentative but just want to get a better understanding of how "proper" root will work in an enforced selinux environment.

ramjet73
[SuperSU] mikereidis:
/tmp is there and works fine on my N7 w/ TWRP when in recovery. The bigger problem is that /system/etc/init.d/ doesn't exist, so 99SuperSUDaemon can't be copied to it.

Creating init.d myself didn't help, and I have no idea if init.d even works in Android 5 now.

I also created /system/app/Superuser/ and copied Superuser.apk to it and ran set_perm and ch_con on it. I don't know if that helps.

Then after reboot, the big error in logcat is "E/SuperSU ( 2076): SU BINARY IS NOT RUNNING AS "u:r:init:s0" - THIS WILL CAUSE ISSUES".

Anyway, I hope we'll have a nice working SuperSU v2.15 soon with "proper root". :)
[SuperSU] billyx1:
Getting rid of this stupid SELinux sounds very good. Perhaps there are other positive effects also like working ES File Explorer or working Secure Settings.
[SuperSU] USBhost:
Or just don't compile it with the kernel
[SuperSU] local_root:
Does the root issue fixed in android 5.0?
[SuperSU] sykopompos:
I agree with you that it isn't proper root but it is a temporary solution till proper root is achieved

Sent from my LG-D851
[SuperSU] jack197:
Update Super Su 2.01 to 2.14 in my LG G2 D802, no problem.
[SuperSU] GR0S:
Hope chainfire will figure out how to allow su calls
[SuperSU] Garner:
Out of interest what feature does it bypass?
[SuperSU] GR0S:
SeLinux for everything
[SuperSU] egingell:
Most posts I've read suggest that most people want to bypass/disable selinux.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] madd0g:
There's not much point in feeling secure with SElinux set to enforcing mode, while sporting a device with an unlocked bootloader and root at the tap of the button. I consider it a fair compromise.
[SuperSU] Giobio:
I like the place you live :) :good:

Sorry guys for the post....
[SuperSU] billyx1:
Done it and now root works, thank you.

The steps are just:

- Download boot.img from http://xdaforums.com/showpost.php?p=56100828&postcount=2934

- Flash it with fastboot flash boot boot.img

- Install SuperSU the usual way. (If already installed after updating Android L preview no need to do it again).

To make it clear: This disables SELinux, a new security feature of Lollipop. But hey, i haven't needed it for years and I DONT WANT IT.

Finally I'm able to set the density of to screen to a usable value (300).
[SuperSU] Floodle:
Thanks, but what is "Install SuperSU the usual way."?

Do I flash SuperSU somehow? Or do I install it from Google Play?
[SuperSU] t3chwizard:
In my personal experience, flashing a zip from a recovery causes too much trouble with SuperSU. Your best bet is to install the app from the Play Store and then install SuperSU that way.
[SuperSU] Floodle:
When I do that it pops up with a message saying that there is no SU binary installed :(
[SuperSU] ferdinandpc:
How do you change the density of screen?
[SuperSU] Grondinm:
disabling something to make it work is not a solution...i'll wait
[SuperSU] Rinoceros:
In the file build.prop :cowboy:

Tip: search and think about if you do want it or not :cool:
[SuperSU] Vanhoud:
Lollipop [MENTION=722057]380[/MENTION] DPI....bliss
[SuperSU] ferdinandpc:
Ok. I tried in the first preview and didn't run.

I flash the boot.IMG and now there isn't SuperSU error, but all applications say that I'm not root :(
[SuperSU] billyx1:
Are you talking about Google disabling the possibility to root to make SELinux/better security to work? ;)
[SuperSU] El-Lobo68:
Hello Guys

One question?

Today i flash the Android Preview Build LPX13D.

Recovery TWRP 2.8.0.1 works fine.

But i don´t know ,and that is my question,what must I do for Root sucess SuperSU.

After flashing Update SuperSU Zip 2.14 i have root.But the App doesn´t work correctly.

Sorry for my bad english.I am a german flashalholic....Nexus 5
[SuperSU] billyx1:
I like 300dpi more.
[SuperSU] billyx1:
The problem is not your english. The problem is that you didn't read the posts of the last pages.

Information for the others: Secure Settings 1.3.5 (the beta) is working for me now with root actions.

E.g. turning on and off flight mode with secure settings with root on the new preview works for me.
[SuperSU] Chainfire:
Well, I did speak in haste due to being at friends, "proper" is perhaps not the best choice of words.

Ideally, yes, a root would manipulate the exact policies it needs and nothing more. This is not what SuperSU does or will do however. For better compatibility, root using apps will run mostly unrestricted, some policies still apply, but most will not. For processes *not* running as root via su, all SELinux policy restrictions will still be in effect. That is the difference with a fully permissive system, there all processes run unrestricted.

While having root is undoubtedly a hole in the system making the entire thing less secure, there's no real reason to disable the security measures for processes not running as root, and thus I do not consider it a good thing to do so.

I'm not stopping anyone from doing that, but disabling securities without a good reason to is just not something that seems useful to me. From what I've heard and read, most people just think they have a good reason, but they mostly misunderstand some details ...

Unlocked bootloaders and rooting have no effect whatsoever on the exploitability of apps running on your device. Your argument makes no sense to me.

So yeah, if you have physical access, SELinux is not going to protect you. That's no surprise, it was never designed to.
[SuperSU] ramjet73:
If proper root access in an enforcing selinux environment means generating policies and letting the operating system handle root permissions that might be a while. I still haven't been able to find an answer, or even a discussion, of how superuser should be handled with selinux enforcing. Does anyone have a reference for a development document or discussion thread?

Edit: Sorry, I drafted this post while Chainfire was making his post above. I think we are in agreement on the requirement for true selinux enforcing support, which I agree is not practical for most phone and tablet users.

ramjet73
[SuperSU] Grondinm:
Google did not disable anything...rooting is not something google supports it is something the the community does and will have to figure out how to do with the changes google has made. Like chainfire said disabling SELinux is not the ideal solution but who knows in the end it might be the only one we just have to wait and see
[SuperSU] Chainfire:
Here are flashable kernels for the Nexus 5 and 7 that will allow you to flash SuperSU 2.14 via TWRP and it'll work, without switching the entire system to permissive. For ADT-1 first flash the kernel, then apply CF-Auto-Root.

Nexus5: nexus5-hammerhead-lpx13d-kernel.zip

Nexus7: nexus7-razor-lpx13d-kernel.zip

ADT-1: adt1-molly-lpx13d-kernel.zip

These are zipped fastboot images, not CWM/TWRP flashable ZIPs!
[SuperSU] Quacktop:
Nexus 5, works.

fastboot flash boot boot.img

reboot to recovery

flash SuperSU 2.14 zip

Confirmed TitaniumBackup (test5) and Root explorer working.
[SuperSU] nisby:
work without problems on nexus 5
[SuperSU] SketchyStunts:
[MENTION=631273]Chainfire[/MENTION] it failed in TWRP
[SuperSU] david279:
extract the file and flash in fastboot.
[SuperSU] gaurav2009:
I am still downloading at 4kbps on my 4g connection XD
[SuperSU] .MoHaMaD:
Thanks to his work on multi rom nexus 7

flash recovery META-INF a Kernel
[SuperSU] bigknowz:
N7 2013

Works on N7 2013 via fastboot. Having an issue with TiBu, SuperSU granted root, but inside the TiBu, error says could not acquire root privileges - this attempt was made using the "/system/xbin/su" command.
[SuperSU] nisby:
use this TiBu experimental version

http://www6.zippyshare.com/v/42457310/file.html
[SuperSU] dudeman27:
Nexus 5 works. Titanium Backup 6.2.0-test5, Root Explorer, all working perfectly.
[SuperSU] ramjet73:
Ideally, the developer of an app requiring root privileges would provide a template of the selinux policies needed for his/her app to run correctly, similar to the way the permissions required are identified today. Presumably those policy requirements could be translated by the superuser manager into the (current) policy format required by selinux and activated. The user would be responsible for reviewing the policie(s) before they are implemented and deciding whether or not to allow them for that app.

Of course we don't live in an ideal world so some compromises must be made unless/until a superuser authorization mechanism can be developed that meets enforcing selinux requirements and is acceptable to everyone involved.

ramjet73
[SuperSU] Chainfire:
This is actually more or less what is going to happen for root apps, as a number of them need to modify system-wide policies. The system for that is already in place, I just haven't made the API public yet. It's all done by the supolicy binary you can find in /system/xbin with the latest SuperSU's
[SuperSU] ferdinandpc:
I flash it again and have the same problem, i'm not root...
[SuperSU] Rinoceros:
Reflesh the SuperSU zip file through recovery.

Because you changed the density, some (or more) programs might start complaining about the resolution or even worse: not installing any more.
[SuperSU] dudeman27:
1. Reboot into bootloader and use the "flash-all.bat" (or other file if different OS)

2. Flash boot.img (from Chainfire's link) via adb

3. Reboot into recovery and flash SuperSu 2.14

4. Restart and check root privileges in apps