yashsingh1/xdaforums huggingface dataset:
[SuperSU] planb234:
It sounds like you are on a stock ROM. the manufacture will get rid of all binaries if you update. Or wait and it will do it by itself.

---------- Post added at 03:56 AM ---------- Previous post was at 03:52 AM ----------

When you flash super user on to a stock ROM it is a good idea make sure and open the super user app first so it has a chance to fight. But it sounds like you are using the wrong binary.

---------- Post added at 04:04 AM ---------- Previous post was at 03:56 AM ----------

That zip for titanium back up doesn't seem to work for me. Unless I'm using the same ROM but then what is the point? Even with titanium back up it is best that you are in control. The beautiful thing of super user is that it allows apps like titanium back up do what they want. It would mix mac binary if it could read it. One wrong restore and it is easier to reinstall than dig it out.
[SuperSU] occtec:
This YouTube video may be helpful... How to Update and Root Android 5.1 Manually on Nexus 4, 5, 6, 7, 9, and 10!: https://youtu.be/Ir-V1ONC6HI
[SuperSU] Fant0m3:
Oh for sure, to TB to work properly make sure your restore settings box is checked in preference section. I also had that problem at first but then I created a custom restore point on my internal SD card and only use that path once I start it I go and make sure the app goes to that path then go to manage android ID and hit restore previous ID. It has worked across three different ROMs I've installed just today.
[SuperSU] hitulg:
Super SU v2.46 doesn't require any particular cellphone or android version compatibility? Can I flash it as my SuperSU files aren't getting update manually inside the SuperSU app in Note 2 7100 running Ressurection Remix 5.3.2 ?? Please someone reply.
[SuperSU] jojo30:
Is it compatible with lollipop 5.1, or we need to wait for a new version?
[SuperSU] thecryof:
I'm using version 2.46 with stock lollipop 5.1 and haven't noticed any issues.
[SuperSU] jojo30:
I do see issues, on rr3 spots commercial did showed up, I'm on v.2.46 too
[SuperSU] MikeRL100:
There are issues with 5.1 and SuperSu. We both noticed issues with SELinux while I thought I found a bug in SD Maid. I'll upload the log. Chainfire, you may really want to look at it. Seems they changed up SELinux. You can notice occasional hiccups in performance, and some root apps have certain issues.

https://www.dropbox.com/s/dlly71pv73tulnn/Log_2015-03-12_12-15-46.txt?dl=0

It will kind of work, but if I were you guys I would wait. Hopefully that log proves to be of some use. Device is a Nexus 5 on 5.1 Omni with SuperSu 2.46.
[SuperSU] aikidoka9:
No "Survival Mode" checkbox in Settings

Big problem,besides my ignorance. Running: Nexus 5, Lollipop 5.0.1, TWRP, Xposed v3.0 alpha1,

From Google Play, loaded free SuperSU. No problem. days later loaded "SuperSU Pro from Play.

Rebooted, checked SuperSU, opened app, hit Settings where it says: "SuperSU Pro v2.46".

PROBLEM #1 There is no"Survival Mode" line/checkbox between Enable Superuser and Re-authentification

as shown in a youtube vid while I was doing homework on the app.

PROBLEM #2 I'm old (like Grandpa Simpson) and a noob. Patience and help will be appreciated since

I probably missed something,someplace.

Thanks.

aikidoka9
[SuperSU] Pkt_Lnt:
Lollipop change how OTA works so survival was removed for it. I'm on KitKat and it is still there in 2.46. You saw an old video probably about Kitkat.
[SuperSU] aikidoka9:
Much appreciated! Looks like I shot self in foot by loading 5.0.1. I lost Xprivacy aswell.

"Shoulda" stayed with KK. Be well.

Regards,

aikidoka9 :(
[SuperSU] Pkt_Lnt:
Restore the nand you made before upgrade. Easy peasy.:good:
[SuperSU] 4r45h:
Stuck in installing binary in CWM recovery mode

I installed Kitkat build 4 custom ROM by Vaibhav on my GT-I8262 following the procedures he describes in his blog (using Odin3, CWM, installing device drivers).

the smart phone rebooted correctly in normal mode. I tried to open SuperSU (preinstalled by the ROM) and it closed because it couldn't find the binary. Then I installed Farmaroot and tried too root the device. By ending the rooting it said that binary should be installed and the recommended method is using CWM/TWRP. By selecting the CWM/TWRP option device rebooted to the CWM recovery mode.

* I don't know how to install the binary in this mode.

* The device is stuck in CWM recovery mode.

* PC (Odin) does not recognize the device.

* selecting "reboot to bootloader" boots the device in download mode.

I would appreciate if you could help me in this situation.
[SuperSU] MikeRL100:
I should mention that darken saw some SELinux related issues in the log as we were testing. Root appears to work fine for the most part on 5.1. However, I'm curious if these SELinux related entries in my log were related to SuperSu acting up on 5.1. It's worth glancing at, but if it's not, forget I said it. I PM'd Chainfire a link to the log. In case there's anything useful in it. If not, discard it and let me know. It could be OmniROM, an Android bug, or even SuperSu. Google has tweaked a few things under the hood in 5.1. It's way less buggy, but still it's a new non-minor release. SuperSu could not be fit for it 100% just yet, but most things behave good enough after a day of using it. Cannot say nothing new has been broken.

Don't expect darken to account for my own opinion above. I just helped him test SD Maid on 5.1 a bit (because the app kicks ass) and we noticed some odd log output. The bug wasn't in SuperSu after all. Guess I spoke too soon. But the log may help Chainfire if there's any SELinux changed on 5.1. Who knows?

A note to root developers - even though everyone thinks this is a boring release that is just 5.0 minus the bugs, things have changed under the hood a little. Enough that SD Maid's autostart toggling ability broke on 5.1 but worked fine on 5.0.2. I even let my guard down on noticing bugs this time around. I'm just a user myself, but sometimes we all get lazy.
[SuperSU] Luxferro:
I'm seeing some issues on 5.1.

It will grant apps root access, but seems to have issues with file permissions. Example; I created a new text file with root_explorer @ /sdcard. Then I edited it with a couple shell commands... then tried to change the permissions so it can be executed, and it wouldn't let me change the permissions. I also tried in an on-phone terminal; it granted su access, but wouldn't chmod 777 mytext.sh.
[SuperSU] Frank Westlake:
In Recovery you choose the option to install something and navigate to the SuperSU zip archive on your sdcard, then select and install it.

Frank
[SuperSU] 4r45h:
Thanks for your reply. Unfortunately this didn't help and the device did not come out of recovery/download mode booting loop.

I reinstalled PC drivers and Odin3 reorganized the device. so I installed the stock ROM.

I would try to install the custom ROM again :)
[SuperSU] Evie2883:
Broken Download Link

I'm trying to download the supersu binary zip file, and the link from the main post seems to be broken. I get taken to a seemingly blank page, then after about 5-10 mins, my browser says it cannot find the file.
[SuperSU] seahorsepip:
chainfire.eu seems down. Anyone able to post a mirror to the latest supersu zip(2.46) in the mean time?
[SuperSU] stynatu46:
UPDATE-SuperSU-v2.46.zip
[SuperSU] Chainfire:
Gave the server a kick, should be up again now.
[SuperSU] seahorsepip:
Thanks, Just did a clean install of android 5.1 and found out the site was down >.>

---------- Post added at 05:45 PM ---------- Previous post was at 05:42 PM ----------

Thanks!
[SuperSU] :
This is definately the best root app available. I am glad to have it come with my kernel.
[SuperSU] finalzero:
This version from Google Play works okay on a Note 3 with stock lollipop ROM but as soon as you allow it to update itself it bricks the phone
[SuperSU] DaBigFreak:
Nexus 10 running 5.1

I am getting no left space in /system so no additional data can be written by adblock or busybox.
[SuperSU] rogers11:
So you have to make some room in /system by deleting some apps. Or why did you post?
[SuperSU] DaBigFreak:
Nope, it's a root fault, because same thing happened in early 5.x SuperSU versions. It's a clean 5.1 original Rom, Google would never ever flash a ROM with filling /system up to 0mb left space. There are some hundred left.
[SuperSU] Frank Westlake:
It's more likely that you have a corrupt file system. Do you dirty flash? Restoring files from a backup of a corrupt system will corrupt a clean system.

Frank
[SuperSU] markusb68:
Had the same on my n10 with lp 5.02 and 5.1.

Did a dirty flash!

Then removed asian keyboards and had enough space for busybox.
[SuperSU] Pure Drive GT:
Compatibility in 5.1

Does the zip package for the installation via recovery work as it is supposed to on 5.1, or must we wait a bit till a few things have been sorted out?
[SuperSU] Primokorn:
A few posts above yours: http://xdaforums.com/showthread.php?p=59393957&postcount=8613
[SuperSU] purian23:
The last few pages back are nothing but 5.1 talk.. Yes it'll work. Some are experiencing some issues same are now. I am not on my Nexus 6. Seems okay.
[SuperSU] shaggyskunk:
I just flash the zip in the OP - Done ?

"Bye bye Sweet Canadian Moonshine"

Sent from my SM-N910W8
[SuperSU] smartymcfly:
Does anyone have a link to version 2.08 flashable zip, on amazon fire tv this is the most recent version of supersu that displays correctly. Anything that is newer than v2.08 and when you start supersu, nothing happens, as in you can not access the settings or see the logs or anything else.

Thank You

Edit:

If anyone wants the latest flashable zip of supersu v2.08 for use on the amazon fire tv in which supersu displays correctly here is the link from Chainfire's website, this is not a mirror, it is the original link

cwm-twrp_flashable_Beta_Supersu-update_v2.08.zip
[SuperSU] ettehcraeiram:
How can I have Super SU on KATA F1
[SuperSU] shaggyskunk:
Don't know what a KATA F1 is - But I'd imagine that if you have a custom recovery - just flash the zip in the OP

"Bye bye Sweet Canadian Moonshine"

Sent from my SM-N910W8
[SuperSU] Mike B.:
I'm not aware of any custom recovery (or custom ROM) for your device and I'm not even sure it can be rooted, especially if you're on 4.4.2 as opposed to an earlier (unpatched) 4.4. It looks like an interesting phone but because it seems to be relatively rare (as are all Kata products), chance are few developers have worked on it. Whatever you try, make sure to run a full Nandroid backup first since you'll have very few options to recover from a catastrophic failure.
[SuperSU] aamadorj:
The information at this site confirms [MENTION=1927554]Mike B[/MENTION] thoughts: http://forums.androidcentral.com/ask-question/481816-how-can-i-root-my-android-device-kata-f1.html
[SuperSU] jgcaap:
Because you deserve it. Thanks!
[SuperSU] Azlun:
Does lastest v2.46 support arm64 chattr? I found there is no chattr.pie in Update-SuperSU.zip
[SuperSU] Cheps01:
Hello,

I'm running: Galaxy Tab 2, OmniROM Lollipop 5.1 and TWRP Recovery v2.8.4.1.

I tried install SuperSU by two ways:

.- Flash the zip file (v 2.46) from recovery but when the tablet reboot, stays forever in the Lollilop logo screen.

.- Install from Google Play, free version, but when I run the program show the error message -> "Executable SU its not installed and SuperSU can not install......" and exit.

Any solution?.

Many thanks.

Regards.
[SuperSU] Vichenec:
Wanamlite ROM NOTE 4 (910c) latest lollipop build (BOC3) super su is not working properly, the root request is not prompt by any of the apps, tried to reinstall form market and reflash through twrp, no luck. I've been asked to post the problem here. Thanks
[SuperSU] Pkt_Lnt:
Without logs to show what is happening, there is no way anyone, even ChainFire can help.
[SuperSU] G.M.L:
delete it

G.M.L.
[SuperSU] bgmg:
[MENTION=5247964]G.M.L[/MENTION]

While the xda mobile app won't let you delete pics from your post, if you log into xda from a pc you can edit your post and delete pics. I did it yesterday.
[SuperSU] thahim:
[MENTION=631273]Chainfire[/MENTION] I have formated phone and flashed 5.0 again on TouchWiz note 3. There was a method to flash super user can you tell me that method or thread again.
[SuperSU] n1ck0:
Hi

i'm trying to root an android stick (MK809IV with RK3188). I have used the TPSparkyroot way, but the superSU is the v1.5 and when i lunch superSU it says that i have to download binaries... i tried without getting to work... I installed the last version of SuperSU but i can't get the binaries, installation failled!

can someone help me updating this supersu to get the lastest binaries?

thanks
[SuperSU] Dor-b:
High wake lock

Hello,

I'm getting a very high wake lock from superSU(ss attached) , any one experienced the same thing? And maybe have a solution..

Thanks in advance.
[SuperSU] Dor-b:
High wake lock

Please delete
[SuperSU] 10basetom:
My oh my, 866 pages of many people having issues updating the binary. After having to reflash my CFW three times and still not able to fix this binary update issue, I have finally arrived at a solution that has worked out for me and saved me from pulling out all my hair: I simply stuck with the version that came with my CFW (v1.94) and unchecked the auto-update option in Google Play. That's right, the solution is to never update the binary if it is working reliably for you. Sometimes newer is not always better.
[SuperSU] MultiKoopa:
So these problems with 5.1 and SuperSU 2.46... are they minor and ignorable completely?
[SuperSU] egingell:
There are far more users without problems than with problems. And a lot of those who have problems have problems that are completely unrelated to SuperSU.

Your "solution" is like burying your head in the sand - ignoring the problem is not solving the problem.

Posting your "solution" helps no one - especially not the dev. This is a development thread, after all, and if you really want to help people, help Chainfire by posting your logs, ROM version, and device details.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] Lonnie Reeder:
Not everyone seems to be hampered with v2.46 and 5.1. I am currently running a custom ROM on my ASUS TF300t (KatKiss v21 v5.1.0) and I flashed v2.46 and have had no wake-lock issues nor any other issues that have been reported. So I am not having the issues. But if you experience any issues, I would recommend you send as much information as can to assist the forum in helping.
[SuperSU] 10basetom:
That's the thing -- I'm not having any problems with v1.94. I stand by my solution: if it ain't broke, don't try to update the binary because it can break the app and you'll end up spending too much time trying to troubleshoot.

The thread for posting logs related to binary update failures is http://xdaforums.com/apps/supersu/support-update-failures-t2907365, as stated in post #1.
[SuperSU] y0000:
sorry for my silly question guys i dont know if it is the true thread here for my question but.. I look the wakelocks today and im confused Is normal supersu stay awake for 10:30 hours? i dont remember to previous versions stay awake for so long time. thnx and sorry if it is wrong thread and for noob question.
[SuperSU] NeoLogY:
Could it be something(other app) is using SuperSu's wakelock and make it stay awake? Like triggering sudaemon to keep it awake?

Sorry if im misleading it, curiousity is to blame.:D

Sent from my GT-I9082
[SuperSU] Pkt_Lnt:
Super SU has never shown in my BetterBatteryStats or Wakelock Detector.
[SuperSU] y0000:
me too thats why im confused if i press to open supersu stay awake all the day and i show it to wakelocks for many hours and dont go to deepsleep or desapiar just run and run. if dont prees to open it its ok dont open and dont show it to wakelocks. i try to remove some apps maybe is stuck
[SuperSU] Pkt_Lnt:
In Settings, change logs to Full Content and see if anything odd shows up.
[SuperSU] y0000:
you are right i check it some times adaway run for long time i dont know why but i thing this is the problem thnx a lot
[SuperSU] Cheps01:
Any help???
[SuperSU] khairulez:
After install SuperSu via recovery,do wipe cache & dalvik-cache then reboot system.
[SuperSU] Pkt_Lnt:
I see it was Adaway auto update and not SuperSU.
[SuperSU] JsChiSurf:
Anybody have any idea what is the source / cause of these repeated logcat entries? They occur non-stop about every 5 seconds or so, and I can't decipher based on documentation the root cause.

I'm suffering rapid battery loss (LP 5.0.1, Nexus 5), and in trying to track down, I'm wondering if this is the root cause. SELinux is running in permissive mode as verified via getenforce.

I/supolicy(12429): --- SELinux policy patch start ---
I/supolicy(12429): allow sdcardd unlabeled dir { append create execute write relabelfrom link unlink ioctl getattr setattr read rename lock mounton quotaon swapon rmdir audit_access remove_name add_name reparent execmod search open }
I/supolicy(12429): allow sdcardd unlabeled file { append create write relabelfrom link unlink ioctl getattr setattr read rename lock mounton quotaon swapon audit_access open }
I/supolicy(12429): allow unlabeled unlabeled filesystem associate
I/supolicy(12429): --- SELinux policy patch end ---
W/supolicy(12429): type=1400 audit(0.0:23228): avc: denied { write } for name="load" dev="selinuxfs" ino=3 scontext=u:r:debuggerd:s0 tcontext=u:object_r:selinuxfs:s0 tclass=file
W/supolicy(12429): type=1400 audit(0.0:23229): avc: denied { load_policy } for scontext=u:r:debuggerd:s0 tcontext=u:object_r:kernel:s0 tclass=securityI/auditd ( 295): type=1403 audit(0.0:23230): policy loaded auid=4294967295 ses=4294967295
W/debuggerd(12430): type=1400 audit(0.0:23231): avc: denied { execute_no_trans }for path="/system/bin/toolbox" dev="mmcblk0p25" ino=24742 scontext=u:r:debuggerd:s0 tcontext=u:object_r:system_file:s0 tclass=fileW/toolbox (12430): type=1400 audit(0.0:23232): avc: denied { remount } for scontext=u:r:debuggerd:s0 tcontext=u:object_r:rootfs:s0 tclass=filesystem
W/debuggerd(12427): type=1400 audit(0.0:23233): avc: denied { write } for name="ready" dev="mmcblk0p28" ino=163789 scontext=u:r:debuggerd:s0 tcontext=u:object_r:app_data_file:s0 tclass=file
W/debuggerd(12427): type=1400 audit(0.0:23234): avc: denied { open } for name="ready" dev="mmcblk0p28" ino=163789 scontext=u:r:debuggerd:s0 tcontext=u:object_r:app_data_file:s0 tclass=file
[SuperSU] Cheps01:
Many thanks khairulez,

I'll tried it.

Regards.
[SuperSU] schrodinger56:
When I download certain apps that require the granting of 'Superuser Request' the Grant button doesn't work, I tap Grant but nothing happens. Am I doing something wrong or is there an error with the set-up of my rooted Nexus 7? For interest my N7 is running on CM12.

Thanks
[SuperSU] arlenwoot:
Tabbing to a different app then back or disabling tapjacking protection worked for me.
[SuperSU] schrodinger56:
That's sorted it. :)

many thanks.
[SuperSU] PeQuEsan:
I can't seem to root my Nexus 5 after flashing last fresh (today) factory image (5.1.0_r3)... I always flash it using .zip in recovery and it works. But this time, no error message when flashing, but after rebooting there's no "su" binary...

Anyone?

PD: Forget it... It's TWRP 2.8.6.0 that it's not flashing correctly. Sorry.
[SuperSU] Pure Drive GT:
Android 5.1

I've been searching around, but I don't seem to find anything about chainfire stating the current situation with regard to compatibility with 5.1. Is this really the case or am I just unable to find his post?
[SuperSU] Pkt_Lnt:
I have seen no Chainfire posts on 5.1. Some report success, some report issues in the beta thread.
[SuperSU] Ja_som:
And what do you need?

SuperSU works on 5.1
[SuperSU] MultiKoopa:
I thought people were having some issues.
[SuperSU] oaliaso:
I'm getting blank pages and "Database error" from chainfire.eu

Sql borked?

Do they/he have any official mirrors?
[SuperSU] J00sef:
I'm having the same problem.
[SuperSU] Pkt_Lnt:
Play Store
[SuperSU] egingell:
Play Store doesn't have the fancy flash-in-recovery version.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] mrrocketdog:
http://xdaforums.com/showthread.php?t=1538053

post #8628.

"all i can really do , is stay out of my own way and let the will of heaven be done"
[SuperSU] egingell:
Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] mrrocketdog:
edit

---------- Post added at 01:41 AM ---------- Previous post was at 01:38 AM ----------

post #8628

"all i can really do , is stay out of my own way and let the will of heaven be done"
[SuperSU] magnethart:
Link on this post doesn't appear to be working. Takes you to the wrong file.
[SuperSU] mrrocketdog:
:banghead:

"all i can really do , is stay out of my own way and let the will of heaven be done"
[SuperSU] agentexeider:
seriously, can someone just drop their copy onto a site somewhere, at least until chainfire gets his site unborked, I don't think he would care, especially if it's temporary.
[SuperSU] egingell:
I concur with his :banghead:. He gave you a post number in this thread which contains a link to a mirror. If you have the default settings (10 posts per page), it's on page 863.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] garyfunk:
It's post 8628.
[SuperSU] peejaybee:
Maybe I'm takin' crazy pills here, but the link in post 8628 takes me to wikisend.com/download/405620/UPDATE-SuperSU-v2.46.zip which appears to be a download page for Hide.me-Setup-1.0.6.rar. It doesn't look like the right file, and anyway, clicking the "download" button gives a 404.
[SuperSU] garyfunk:
Yes. There is something very wrong.
[SuperSU] egingell:
Yeah, it is indeed broken. I guess you'll just have to wait.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] peejaybee:
I found what purports to be a copy of it. Can someone share the MD5 of the original, or would that be too helpful?
[SuperSU] xOddFuture:
someone needs to just stop being lazy and put it out here for us...
[SuperSU] peejaybee:
As soon as I can verify that I won't be unleashing malware on everybody, I will put a copy up. I just need the MD5 of the original.
[SuperSU] maaljen:
Here is a temp link for the UPDATE-SuperSU-v2.46.zip - however, I cannot find the .md5 and compare.

So use it with CAUTION!

UPDATE-SuperSU-v2.46.zip (mega)
[SuperSU] mrrocketdog:
i know you didnt just post this ^^

well , i'm out.

"all i can really do , is stay out of my own way and let the will of heaven be done"
[SuperSU] arlenwoot:
332de336aee7337954202475eeaea453 UPDATE-SuperSU-v2.46.zip is what I have from my copy downloaded awhile back straight from Chainfire's site.
[SuperSU] xOddFuture:
new solution....MANY again MANY old versions of SuperSU download one...flash it to your phone. then update it. thats what i just did lol mostly because i didnt want to wait
[SuperSU] peejaybee:
That matches the one I have. I also verified the file at the MEGA link to have the same MD5. Since I am not a real boy yet, I can't post links, so just use the MEGA link.

$ md5sum UPDATE-SuperSU-v2.46.zip

332de336aee7337954202475eeaea453 *UPDATE-SuperSU-v2.46.zip
[SuperSU] donnabelmartie:
Can anybody confirm if this is working with the latest 5.1_r3?
[SuperSU] Pkt_Lnt:
http://xdaforums.com/showpost.php?p=59701012&postcount=8679
[SuperSU] donnabelmartie:
I have the v2.46 from flashing wugs. Hope it'll work. Thinking of flashing 5.1_r3 stock tonight.
[SuperSU] aavvaallooss:
It's works for me on Nexus 5
[SuperSU] triplepwnu:
Found UPDATE-SuperSU-v2.46.zip in my computer's downloads folder from when I downloaded it a while ago. I'll share it until the official site goes up. :) https://drive.google.com/file/d/0B1c-HD-GmBH4dDNLaUdPUXJhZ0U/view?usp=sharing

Click the download arrow on the top when clicking the link. No promises that It'll work without problems. I'll try flashing it now.
[SuperSU] donnabelmartie:
You're making me wanna go hooooome. Still at work :(
[SuperSU] Lybross:
today update binaries not working at all. i do everything well not first time. binary update not working temporary unavaible on server i mean.
[SuperSU] shaggyskunk:
Just flash the zip in the OP - done

"Bye bye Sweet Canadian Moonshine"

Sent from my SM-N910W8 Running SlimLP