yashsingh1/xdaforums huggingface dataset:
[SuperSU] Bexton:
Just trying to keep up. Is it correct that all you changed was to commented out one line - as seen below!? And if so, what does it exactley change (just a pointer to the right reference would be great too)? Thanks for your time!

c:\Android\unpackboot>diff ramdisk\ ramdisk-chainfire\
Common subdirectories: ramdisk\/data and ramdisk-chainfire\/data
Common subdirectories: ramdisk\/dev and ramdisk-chainfire\/dev
diff ramdisk\/init.rc ramdisk-chainfire\/init.rc
599c599
< seclabel u:r:install_recovery:s0
---
> #seclabel u:r:install_recovery:s0
Common subdirectories: ramdisk\/proc and ramdisk-chainfire\/proc
Common subdirectories: ramdisk\/res and ramdisk-chainfire\/res
Common subdirectories: ramdisk\/sbin and ramdisk-chainfire\/sbin
Common subdirectories: ramdisk\/sys and ramdisk-chainfire\/sys
Common subdirectories: ramdisk\/system and ramdisk-chainfire\/system

c:\Android\unpackboot>
[SuperSU] ferdinandpc:
Thanks, but if need reflash all system i have to wait until tomorrow night..
[SuperSU] Bexton:
You don't need top flash all again! Just flash the boot.img

# Download the Supersu zip 2.14 to your phone
# Download the modified kernel zip to your PC and unzip it, so you get the boot.img
# Open a command line tool and cd to where you have the boot.img. then, type:
adb reboot bootloader
fastboot flash boot boot.img
# use power buttons to select recovery and press power to confirm
# install Supersu zip from SD
# wipe cache/dalvik
# reboot system
[SuperSU] dudeman27:
If you already ran the flash-all file updating to Android 5.0 you can skip it and continue with flashing boot.img and supersu 2.14 in recovery.
[SuperSU] ramjet73:
Apps like ES File Explorer and the Play Store version of Titanium Backup do their own check for superuser being installed even after getting authorization via the API from SuperSU. Those apps are likely to fail in a selinux enforcing environment since even with SuperSU authorization they do not have the privileges required to perform those checks correctly.

There is a test version of Titanium Backup available that does not perform its own check and that was linked earlier in this thread. AFAIK there is not yet a version of ES File Explorer that works for the root explorer option. You may need to do your own research with the developers of other apps that appear to be authorized but are not working correctly.

ramjet73
[SuperSU] ferdinandpc:
Thanks but i did it 3 times with the same result...
[SuperSU] Bexton:
Then, you did something wrong before.
[SuperSU] ramjet73:
Well, if anyone can make it work it would be you. ;)

I have the Pro versions of SuperSu and StickMount and have used CF-AutoRoot and TriangleAway away on my Note 8.0. The fact that Samsung addressed the issues using CF-AutoRoot with a KNOX enabled bootloader tells me they respect your work as well and the significance of your contributions to the Android community.

If you need beta testers when the "supolicy" interface is ready to be tested with applications that implement it I would be happy to help.

ramjet73
[SuperSU] jaxbierley:
Most apps are not asking for root access. So far only TiBu has asked. Root explorer and greenify did not ask and do not have root access.
[SuperSU] ramjet73:
Something must be wrong with your installation of the preview ROM or SuperSU.

I have both those apps approved for superuser access (see attached screenshot).

Although ES File Explorer shows as authorized its Root Explorer function doesn't work because it fails the internal root verification.

ramjet73
[SuperSU] jaxbierley:
Damn. I'll try reflashing SuperSU. I have root access so it's weird that I can get it to ask.
[SuperSU] ferdinandpc:
Finaly i got it. I reinstall the apps and now it works!!! Thanks ?
[SuperSU] NPS_CA:
(Android 5.0-lpx13d) Have root with Chainfire modified kernel boot.img and TWRP recovery to flash his 2.14 version. Works fine with Root Explorer

Test version of Titanium backup is working to show superuser, however it seems data restores in that Titanium backup build are dumping in /data/data under the app folder name NOT a folder but a flat file on restore. Warning to those using it - Google Play store will get an error 506 on reinstall of any apps Titanium backup attempts to restore data on, go into /data/data and remove the flat file (using Root Explorer) and install/reinstall is OK
[SuperSU] ste71m:
I flashed boot.img and superSU 2.14 with TWRP but after rebooting i get a message there are no binary SU files
[SuperSU] NPS_CA:
I used TWRP - no other mods installed; just pushed the file to sdcard (internal storage) and did install from TWRP menus

I did EXACTLY the following:

- Install 5.0 - USE their script/BAT - do NOT do selective keep of data; WIPE the phone

- Rebooted and let Google restore apps/login to Google, etc

- Enabled debug, rebooted with adb reboot bootloader in terminal/cmd

- In Fastboot did a: fastboot flash boot boot.img (this boot.img is the chainfire modified kernel NOT others that are posted)

- Did a TEMP boot of TWRP; I never replace stock recovery just boot as needed: fastboot boot openrecovery-twrp-2.8.0.1-hammerhead.img (this will temp go into recovery)

- When in TWRP my Mac had the file mounted with Android File Transfer so copied SuperSU version referenced here to root of internal accessible storage (e.g. /sdcard)

- Selected flash in TWRP and picked the SuperSU zip

- Rebooted in TWRP

Had root right away in Root Explorer
[SuperSU] ste71m:
Nearly did the same

installed 5.0 (i tried without wipe but was unstable and reinstalled)

installed TWRP 2.8.0.1

tried to install superSU

installed chainfire boot.img via fastboot

Installed superSu from TWRP

Edit: cleaning cache fixed. Unluckily titanium not working
[SuperSU] mikereidis:
Android 5 does not allow old style "non-PIE" executables to run. Many root apps, and even non-root apps, that provide their own executables will have to be updated for Android 5.

Root app users should also understand that there are many security related changes in Android 5 that will require root app updates. These are not issues with SuperSU and chainfire can't fix these problems in SuperSU (for the most part.)

As chainfire posted early this year "there may be much breakage for root apps": https://plus.google.com/+Chainfire/posts/Lyhjzu1z9s1 (and note that there are 2 followups to that post; see bottom for each).

The changes are extensive enough that I re-architected my own root apps to (hopefully) work around the announced possible changes, and other changes that may be coming, in this release, or the next, or the next...

My re-architecture puts most/all of the SU/root request stuff in a background "daemon" that is launched with SU, instead of scattered SU requests from various parts of the apps. It will take me some time to complete this re-architecture, and then I'll have to test (and fix) for many different devices and ROMs, stock and AOSP both.

So please be patient with, and support, the authors of your favorite root apps, especially BIG framework stuff like Xposed. And understand that some root apps will never work on Android 5+, unless SELinux is turned off completely and luck is good.
[SuperSU] pRo_lama:
I'm trying to flash your .zip file, but I get this error:

Installing '/sdcard/Download/nexus-razor.lpx13d-kernel.zip'...
Checking fr MD5 file...
Skipping MD5 check: no MD5 file found
Error flashing zip '/sdcard/Download/nexus7-razor.lpx13d-kernel.zip'
Updating partition details ....

Failed
[SuperSU] rawdealer:
Read just two or three pages back ;)
[SuperSU] ramjet73:
Thanks for the links. They definitely help clarify some of the issues involved in managing root access in the Android 5.0 environment. :good:

I'm disappointed that Google didn't provide a global SELinux policy administration app before implementing SELinux enforcing as the default mode. Superuser/root management would be a subset of that which may be one of the reason they didn't. Since the enterprise level security requirements of corporate and government customers seem to have increased in priority for Google they may not want to make it "too easy" to manage SELinux policies.

Or open the zip file and see what's included (and not included). :good:

ramjet73
[SuperSU] toyr99:
Can someone provide me link for that app which adds some tweaks to android l?

Inviato dal mio Nexus 4 utilizzando Tapatalk
[SuperSU] ramjet73:
This thread is specifically for SuperSU discussion and support. Please ask in one of the Android L (Lollipop) preview threads.

But since we've already used two posts in this thread, you can try this and it's documentation is here.

ramjet73
[SuperSU] CynoMan:
Just updated from v2.13 to v2.14, working fine on Samsung Galaxy S Duos 2 (GT-S7582, 4.2.2). Thanks a ton! [emoji2]
[SuperSU] jaxbierley:
[MENTION=275009]ramjet73[/MENTION]. Is greenify working for you? It tells me "failed to hibernate" on any app I have selected and never hibernates them?
[SuperSU] Giobio:
It heppens to me too but with runtastic app only. But it seems so me sometime it freezing whatsapp popup message even if i did not freeze it
[SuperSU] egingell:
I get that followed immediately by "successfully greenfied..." including the same app that failed and if I look in Greenify, the "failed" app is not listed. So it's greenifying them despite claiming it failed. Maybe a problem with Greenify.

Edit: I forgot to mention that it was doing it before I updated SuperSU.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] ramjet73:
It seems to be working for me (see attached screenshot).

I'm using the permissive boot.img from [MENTION=1050103]sykopompos[/MENTION] so that might make a difference.

ramjet73
[SuperSU] jaxbierley:
Ahh that could be difference. I'm using chainfires method.
[SuperSU] Wh1t3Rose:
I really do not recommend turning this on for everyday use. HUGE security risk.
[SuperSU] Mike B.:
Actually, it's not much of a risk as long as you select your apps wisely and keep a current backup. If your paranoia level allows it, you may be perfectly justified in granting su access to any process that wants it. If you run an app that requests root access but you don't want to grant it, maybe you shouldn't have that app? From a practical standpoint, the main "security risk" was rooting the device and once that's done your have to trust your apps (including SuperSU). Unless I'm testing a new ROM or apps, I always set my SuperSU to "grant" and I don't feel the least bit insecure or guilty about it! ;)
[SuperSU] shoey63:
In that case, you don't really need the app, so go to settings and select switch superuser app. This will remove the apk and leave the su binary in place, thus automatically giving full root access to any app that needs it. Your device - your choice....
[SuperSU] Celestial Fury:
Phone details in signature - previously rooted using towel root. SuperSU installed from Play Store. Tried updating from 2.03? to 2.14. Upon launching binary didn't update and message saying Super Su restored automatically. Problem was new app permission for grant and deny didn't stick upon a reboot.

Tried choosing clean up for reinstall option from within app and app didn't close. Upon reboot, started Super SU which was still there and app permission grant and deny previously seemed to stick.

Reporting this for info.
[SuperSU] Bexton:
fyi

Fyi: Some more SE and vold related changes have just been merged into AOSP master trees: https://android-review.googlesource.com/#/q/status:merged
[SuperSU] power2top:
[MENTION=631273]Chainfire[/MENTION], sorry if I sounded harsh. I love ur app and appreciate the efforts you put in. When I faced that binary issue and was unable to resolve, I did google and actually found various forums flooded with the same issue and that is what I mentioned but not to finger point at anything.

Coming to my setup and answering the questions/points you made in your post, here you go:

1. I am using CWM coz that is what I had when I bought my device and being a not-so-popular phone, this is the best I could have then. CWM works for me fine since then and why fix when it ain't broken and so did not check TWRP. Never needed to.

2. Your app updates have been always flawless and never needed to read anything. 'Fix permissions' of CWM works in all other cases so when faced with this issue the first time, this is what 'I' thought would be a solution.

3. Did not know this, never faced this problem as your app updates since .99 till before 2.13 have been flawless. I think the first post should have all of this documented for CWM, TWRP etc so that the user can re-try with what he shud select when faced with such prompts. The reason I selected disable flash recovery was that in some other app case, they had advise to disable else it will revert the recovery and all hell will break loose and did the same in SuperSu case. I came to this forum much later when googling.

Wish we can have all the steps to be followed incase of CWM and TWRP specifically documented so that during such issues, we can follow step by step and also help with fixing such issues instead of selecting wrong options unknowingly.

Once again, sorry if I hurt your sentiments unintentionally.
[SuperSU] nunein:
Updated from v2.01 to v2.14, working fine on Galaxy S4 Mini (GT-I9195, stock 4.4.2 NH5).

Thanks!
[SuperSU] Giobio:
How can I do to delete the original superuser app?

And more, can any kind soul tell me or explain if what are you talking to is to definitively fix permissions when restart the device from recovery? I think do not have problems with su but always that fixing to do when I back into android.

Only with nameless rom I have not fixing problem but always with CM11. I use Gustavo kernel and ART runtime.

Thanks
[SuperSU] Bhaskara Rao:
Delete
[SuperSU] Chainfire:
Here's some more info on the LPX13D root and SELinux on L. Devs should probably read.

https://plus.google.com/+Chainfire/posts/VxjfYJnZAXP
[SuperSU] tuncan:
Ok, I give up. As noob, I don't understand what I have to do, sorry for this post.

If I open SuperSU, I have v2.13 (on Nexus 5) - I installed it via Flashify last week.

If I go to Google Play, it shows that latest version is 2.01.

Now, I see that something is wrong - what should I do now?
[SuperSU] zadigre:
which part you don't understand? it's a staged rollout... so that means that the latest version (2.14) is available to +/- 25% of users right now... the previous stable version available on the Play Store was 2.01... so what you are getting is perfectly fine.
[SuperSU] tuncan:
It looks strange for me: latest version is 2.01, but I have 2.14.

And now, I read about some problems (and quick root fix) on Nexus 5 and I don't now what to do.
[SuperSU] zadigre:
it looks strange? You manually installed SuperSU to get the latest version...

what you see in the Play Store is the latest version available in the Play Store... not necessarily the latest version available on Chainfire's server.

a staged rollout is use to "test" the new release on a relatively small number of users... there's nothing strange in this...

if you have the latest version available here (2.14), you don't have to worry about the play store.
[SuperSU] MrKaon:
Looks like you are in KitKat, so no need to fix root as yours is working perfectly come back here when you get lollipop ota. [emoji12]
[SuperSU] Technical:
Is there any way to set a sound when the SuperSu popup message appears?

Some apps just ask for root after a lot of time, executing all the non-rooted actions before... And then, I get the timeout...

Thanks.
[SuperSU] Bexton:
Btw, for those who flashed Chainsfire's modified Kernel for the LPX13D builds, thus run in enforcing mode, having root but still having issues with one's favorite root app (that hasn't been update yet). There's a simple toggle app for you to easily switch the system sepolicy mode betw enforcing and permissive here: http://xdaforums.com/showthread.php?t=2524485 . Switch to permissive, let the root app do its job and switch back to enforcing. This should help at least for certain broken root apps (TIBA still won't work for me, but popular apps like Flashify and the built-in Root-Explorer in the RomToolBox , for example, worked flawlessly). And this way it's still better than running in permissive mode all the time.

Note: updated to better reflect the fact that "this method" won't fix "most of" but only some of the broken root apps.
[SuperSU] ramjet73:
Have you actually used this app? Did "most broken root apps" that you tested work?

Even with the [MENTION=1050103]sykopompos[/MENTION] permissive boot.img some apps requiring root are broken because they try to access resources that used to be available in user mode that now require root. You should read the latest update from [MENTION=631273]Chainfire[/MENTION] here and then revise your comment "Should help for most broken root apps" appropriately. In reality, most of those apps are going to require changes by the developers.

ramjet73
[SuperSU] dimebagdan65:
Click on his avatar, view profile, find PayPal donate email, profit! (For Chainfire lol)
[SuperSU] BeatB:
I already flashed this zip yesterday in recovery. Same problem again.
[SuperSU] mehmet184:
yes the new version has been wonderful. will raise pro version.
[SuperSU] Stupifier:
I also have the same problem as BeatB.

To restate the problem. Everything is fine (root apps work etc) but SuperSU says "The SU binary needs to be updated. Continue ?" each time you open it. Pressing continue ends in "Installation failed !"
[SuperSU] shaggyskunk:
Has anyone just tried to uninstall, and then reinstall? Fixes lots of problems. (I mean supersu.. Reinstall it).

Sent from Down The Rabbit Hole, using Tapatalk 2
[SuperSU] Stupifier:
Forgive my noobness.....but if you uninstall Supersu....you would lose root all together, correct? That would make it very troublesome to re-install supersu.
[SuperSU] MarkAtHome:
I would like to see the sort order configurable, as I would prefer to see the most recent ones at the top. ;-)
[SuperSU] shaggyskunk:
Uhm, I'm not 100% sure about that.. Superuser needs you to have root first... But I'll defer to any other more knowledgeable folks.

Sent from Down The Rabbit Hole, using Tapatalk 2
[SuperSU] MarkAtHome:
Try doing that with notifications on and how to process set to prompt. I bet it doesn't have Superuser access! Completely exit/end SuperSU, and then re-launch it and see what happens. I have seen this before.
[SuperSU] Pons:
For that, you could look at the log.
[SuperSU] Stupifier:
SuperSU by default already had notifications on and how to process set to prompt. I did what you asked anyway.....still installation failed !

****

Update: Just for the hell of it...I also tried re-flashing SuperSU in CWM recovery. No change in final result....still installation failed !

Does anyone think the "Reinstall - Cleanup for resinstallation from Google Play" option would help??? This option was found under settings of SuperSU app. I'm gonna be away from my computer for a few hours. I'll check back in then in hopes of a solid solution to this problem. It really sucks.

Just a thought though....say I roll back to a backup I made that has the old "Superuser Permissions" app on it. Could I try the Google Play Market install way to get SuperSU App? If so, from what I read here, you install it via the Google Market, then remove the old "Superuser Permissions" app, correct? If I do this, wouldn't the SuperSU app I installed from Google Market NOT have all the proper permissions it needs?
[SuperSU] voryzen:
I haven't had an issue, guys. Super su has worked for me with every app that has required root.
[SuperSU] dimebagdan65:
Same, dude... Feel bad for folks with issues :'(
[SuperSU] vlt96:
Me2:)

Seek the signature below the line;)
[SuperSU] Stupifier:
Well, I know I'm not alone with my issues here...so I figure would get some kind of support/help. Until then, I'm just sitting on my real old "super permissions" app. Wish I could get supersu
[SuperSU] dimebagdan65:
Tried updating BusyBox...?
[SuperSU] bsoplinger:
I just noticed the comment about turning off the protect root preference before doing a nandroid backup. Out of curiosity, why? It seems to me that I'd want to backup things just like I normally have them vs. doing something special to change things a bit before a backup.

Sent from my PG41200 using Xparent Purple Tapatalk 2
[SuperSU] Stupifier:
Prior to flashing SuperSU, I made sure I had the most current/updated BusyBox standalone installed.
[SuperSU] dimebagdan65:
Dang, that worked for me whenever I couldn't update a binary from SU or SSU, sorry bud :'(
[SuperSU] Chainfire:
Nandroid is a bit of a dumbass, and it cannot cope with the mechanism used to protect the root binary. It wail fail during restore.
[SuperSU] Bexton:
Wow. I'd say you should rather revise your attitude. That's the 2nd time I see you playing the sheriff now; and a very supercilious*one on top. A) I'm not sure why you think I didn't but I've read his post about 3 minutes after he posted it. B) Of course, I wouldn't have said "most of" just because I assume it may be like this but actually have no clue, am some foolish noob and just want to gain some recognition in online forums because I've time to waste. Ehm, no.

Specifically, for 3 out of 5 apps that I personally tried - I consider this "most of", btw - setting permissive mode fixed the apps' issues. I was just happy when I saw it working for me and thought it might be helpful to others too. Also, while you were typing your rant, I already updated "most of" to "many", because I thought this might sound too generalized.

Anyway, if it is not true for "most of" but just for "some of" the broken root apps, I'm a) obviously very lucky having "the right" apps installed and b) sorry for generalizing my personal experience. However, you could have addressed this is a much more friendly way; not behaving like a teacher speaking to people who won't listen for reason.

Anyway, I need to thank you for the friendly hint. I'll update my comment above and hope it better reflects the situation now.
[SuperSU] ramjet73:
I have a hard time going for style points when I see misleading information being posted on XDA in what appears to be a very authoritative manner. Yes, I could have been more tactful in questioning your conclusion but you could have been less certain about it's effectiveness in your presentation.

Just to clarify, are you suggesting that for the apps that require superuser privileges and currently don't run correctly with the [MENTION=631273]Chainfire[/MENTION] relaxed boot.img, that 60% of those will run successfully just by setting permissive mode on? That certainly hasn't been my experience and turning permissive mode on and off would do nothing to help applications like Greenify that need access to additional resources, beyond what the [MENTION=631273]Chainfire[/MENTION] boot.img supports, on an ongoing basis.

I'm happy to let other XDA users be the "jury" for this one, but I'd be willing to bet that most who try that app either use it to turn permissive mode on and leave it on, or get tired of manually switching it and stop using the apps that require it.

Hopefully the developers whose apps have problems with the [MENTION=631273]Chainfire[/MENTION] relaxed approach, which is the subset this app might address, will be the first to step up to the plate and make the changes required. And ultimately all applications that require elevated privileges will need to conform to the SELinux policies that Google implements in Android. Luckily, for them and for the Android community at large, [MENTION=631273]Chainfire[/MENTION] is taking the lead for something that Google will not support and would be very difficult for each developer to address on their own.

In the meantime, there are no magic bullets, and we all need to be careful about how "workaround" solutions are presented.

ramjet73
[SuperSU] tuncan:
Thank you, you are right. I'm (still) on KitKat.