yashsingh1/xdaforums huggingface dataset:
[SuperSU] Bazilli:
Still breaks Moto E XT1524 camera after rooting. :(
[SuperSU] egingell:
Logs or it never happened.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] starbucks2010:
I confirm that everything got back to normal with SG Note Edge after flashing v2.49. I get the pop-up window asking for root access/deny and the Package Manager works again.

Thank you Chainfire.
[SuperSU] Frank Westlake:
2.49 OK through TWRP on:

- Note_ SGH-I717 4.0.3

- Note3 SM-N900V 4.3 single user Permissive

- Note3 SM-N900T 4.3 single user Enforcing TWRP 2.8.6.0

And OK through SuperSU normal update on:

- LGL34C 4.4 (TracFone, TowelRoot special code)

Frank
[SuperSU] motisu:
Just updated my Nexus 5 stock 5.1 using flashify. went smoothly and all is working.
[SuperSU] ktetreault14:
Tried on Tmobile S6 Edge 5.1.1 and got bootloop. All is well just wanted to let you know.
[SuperSU] NeoLogY:
Flashed through Twrp on SG Grand Duos i9082 running L5.0.2. No problem. I'm not sure if its placebo, but think got better response from device.

Sent from here to there
[SuperSU] sinisin:
I flashed 2.49 and my phone grew wings, caught fire, morphed in to a Phoenix and started killing iPhones. My dog also died and zombies ate my neighbors. I want a refund. With which I'll buy doughtnuts and become a traveling monk.

It's all your fault man.....
[SuperSU] USBhost:
WoW all that happened

in one day...
[SuperSU] papperlapapp:
Should people who want to upgrade to Lollipop update SuperSU 2.46 before installing Lollipop?
[SuperSU] purian23:
No it isn't necessary

Unless you're meaning pre 2.46 then yes. Not before, but after ROM/gapps the SU.
[SuperSU] simonbigwave:
Installed SuperSUPro 2.49 on [Android5.1.1] Cyanogen 12.1_0430 Nightly jfltexx, no problem all OK.
[SuperSU] CVAngelo:
SuperSU v2.49 BETA removing Kingo User

I believe the Chinese Kingo User (alias King User) su is connecting with the internet excessively. In other words, it appears to be a "trojan" of sorts since it is not simply install su binaries into the system folders. So my question is hopefully a simple one: when SuperSU v2.49 replaces the Kingo User binaries, is it also deleted all the other "stuff" that I think Kingo is putting into the system?

I'm just trying to get a sense for how much Chainfire has investigated what Kingo has installed and to what extent you've tried to clean up all their peripheral stuff?

Thanks in advance for any light you can shed on this. And I'm not looking for you to disparage the competitor. Just want to know what is meant by "replace".

Alcatel OT-7040D rooted, CWM

Vodafone V875 rooted, CWM

Nexus 7 (2013) rooted, TWRP
[SuperSU] Pkt_Lnt:
The install script in the zip will answer that for you.
[SuperSU] CVAngelo:
Of Course!

Yes, you're absolutely right! I feel s stupid..I should have just looked. :laugh:
[SuperSU] StratOS_HTC:
Why would a ku.su have encoded files then ? The answer is simple ...
[SuperSU] baanne:
even when i flash the v2.29 version i can't have my root access back

and when i try to flash the v2.26 i get bootloop and then flash the update file but still without root.

What should I do?? I'm using lollipop 5.1.1 on my Galaxy S3 i9300
[SuperSU] shaggyskunk:
Have you enabled Root Access in Developer Options - Apps and ADB?
[SuperSU] baanne:
No, it wasn't enabled. So now that I have enabled it I do all the process again? Flashing the update version?
[SuperSU] shaggyskunk:
Yeah just flash v2.49
[SuperSU] baanne:
enabled it, flashed the v2.29 and still no root access.
[SuperSU] shaggyskunk:
And if you open SuperSU - And look in Settings - Does it say that SuperSU is enabled? And you checked in Developer Options for Apps and ADB after flashing SuperSU?
[SuperSU] baanne:
Yes, I go on settings then SuperSU, its says it's enable. Go on Dev Options and everything is enable.

I was thinking in flashing the SuperSU apk maybe... or there is no hope in this case?
[SuperSU] shaggyskunk:
What Rom are you running? - This really doesn't make sense...

You can't flash an apk - You can only install it - But I don't think that is the issue
[SuperSU] baanne:
Sorry I know I can't flash an apk lol I mixed the two process.

So, I'm using the 5.1.1 temasek's rom and seems like I'm the only one having this problem cause everyone did the exact same thing: flashed the Update-v2.26 of SuperSU and got the root back.

I update my TWRP to the newest version, flashed the update of SuperSU and still can't have the root access. Flashed the v2.29 of SuperSU still the same thing. DId what you said (enabled ADB on Dev Options) still the same.
[SuperSU] khairulez:
Now try this method..

Enter recovery,do wipe cache and dalvik-cache,flash SuperSu then reboot.
[SuperSU] shaggyskunk:
You're saying that you flashed SuperSU v2.46 - try flashing v2.49 it shouldn't really make a difference - but....
[SuperSU] baanne:
Tried... without success. Seriously, i don't what am i doing wrong anymore

---------- Post added at 02:49 AM ---------- Previous post was at 02:20 AM ----------

did this, still without root access

flashed SuperSU v2.29 and when I looked at the settings menu, the SuperSU has gone (??) flashed v2.26 update file and still missing
[SuperSU] priyam basak:
Yes missing because 2.26 will not work in android 5.1.

Seriously i flashed a flashable zip of 2.26 in my phone tunning 5.1

To my surprise root checker said i have root access but there is no superSU so i installed it from play store but supersu said it can't install binary hence it can't work..

Now what i did is just flashed 2.46 final zip and i have root access without any problem but my android version is 5.1 not 5.1.1 and am using stock rom pure vanilla.
[SuperSU] Pietchaki:
Try enabling multi-user root acess, I was having same issue and resolved after that. Maybe the default user isn't the Primary user?
[SuperSU] baanne:
That's what I did all the time: flashed the 2.46 final zip (the one I flashed was the update file) and I still can't have the root access. Everyone with this rom I'm using got their root access back, except for me.
[SuperSU] inincognito:
is there currently a way of rooting your phone without flashing anything?
[SuperSU] Lakino:
No
[SuperSU] miggsr:
Did you really just ask that question? Have you considered flashing a rom that's already rooted ?
[SuperSU] egingell:
To be fair, there used to be a way to root without flashing anything. Z4root (I think that's what it was called) did it.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] miggsr:
And to be fair times have changed android has changed...
[SuperSU] egingell:
Indeed it has, but that doesn't invalidate the question.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] NZgeek:
SuperSU doesn't support what you want. If you're not already rooted, you'll need to install via custom recovery. You may also be able to use CF-AutoRoot with some devices, but this needs to be flashed.

While there are other tools out there that might be able to do the job, they're not related to SuperSU, so this isn't the right place to ask.

TL;DR - question is valid, just asked in wrong thread.
[SuperSU] egingell:
It wasn't my question.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] jesssiii:
Depends on the phone. I rooted my VZW LG G2 using adb. But you should ask in your devices threads.

VZW LG G2
[SuperSU] kindofabuzz:
You will still need SuperSu (or equivalent) to grant sudo to the apps that need root.
[SuperSU] HTC55555:
This may have already been answered but can I flash using flash fire on my Samsung s4 active i537?
[SuperSU] Cr33D OrB:
It should..

Or easily flash in recovery xd
[SuperSU] HTC55555:
Wow that fixed a few issues I was having. Glad I found this thread. Thanks!!!
[SuperSU] Cr33D OrB:
Yeah supersu is great/BEST xd
[SuperSU] jerryfan2000:
I am developer of an app that requires some level of Selinux workaround. I know that new superSU can workaround Selinux restriction in some cases. But I still hav small number of users who complaint they have problem to use my app even with latest superSU(2.46). Wondering what could be the cause?
[SuperSU] Cr33D OrB:
SELinux

Since when supersu 'bypasses' supersu??

So if set to enforcing,its settibg to permissive (without showing) vor DISABLING IT ?

Sry,heard it to first xd

EDIT: So its bypassing automatically?
[SuperSU] jerryfan2000:
Sorry for choosing the wrong word. It should be workaround some SELinux restrictions.
[SuperSU] Pkt_Lnt:
As a developer you should know that logcats are the only way to see that.
[SuperSU] Gyrxiur:
Hi, I've rooted my Fonepad 7 FE170CG with latest firmware (Android 5.0, ROM build 12.8.1.26) by flashing latest 2.49 supersu, Rootchecker says that I am rooted, but I can't modify any data on system partition. (I've mounted it as read/write of course) Because of this, Adaway or any root app which modifies system partition doesn't work. How to fix it?

edit: somehow it started to work and I don't even know what I did, I've used sdfix and flashed busybox from zip and deleted some system apps to get some free space in system partition
[SuperSU] RandomPooka:
I didn't think SuperSU could get around selinux. It's kernel level, and if an app isn't in the right groups, it won't matter of its got root or not
[SuperSU] xuhaib:
Binary error

V2.46 is giving binary update while beta v2.49 is working perfectly
[SuperSU] garyfunk:
2.46 uses the 2.45 binaries. 2.49 updates the binaries to 2.49.

I am hoping for a 2.50 binary update to fix the am call.
[SuperSU] xuhaib:
Is it good to install beta version?
[SuperSU] garyfunk:
Yes. I've been using it from the day it was released.
[SuperSU] xuhaib:
+1
[SuperSU] Cr33D OrB:
BETA is fine.

Always stay at beta ;)
[SuperSU] lorenzitto:
Could I root a S4 i9515 with lollipop 5.0 without downgrading to KitKat 4.4.3 ?
[SuperSU] RandomPooka:
That's so not even a question for this forum.
[SuperSU] NZgeek:
SuperSU can be used to root most devices. The current beta (see OP in this thread) works with Lollipop, so no downgrade should be needed.

In order to root, you will need a custom recovery like CWM, PhilZ or TWRP. The OP has a zip file that you can download, and installing that via recovery should root your phone.

If you need instructions on how to flash the zip, ask in the forum thread for the recovery you're using. If you don't have a custom recovery, or want to root without using a custom recovery, ask in the I9515 section of the forum.
[SuperSU] iall5tar:
Hiho guys dunno if i this is already related to kernel or app or rom... i just throw it up here if somebody know how to fix it...

The case is that i already flash SuperSu v2.49 and each boot i always get "#need Su binaries get update" but when i press it nothing happens...

btw all my apps that need root works...

LG G2 D802

Stock v30B EUR
[SuperSU] shaggyskunk:
Did you initially install SuperSU from the store?

In any event - This should fix the issue - Method:

a) Wipe System and Caches - Flash Rom and Gapps AND the SuperSU zip - If that doesn't fix it:

b) Factory Reset - Wipe System and Caches - Flash Rom and Gapps AND the SuperSU zip

Sent From my SM-N910W8 Running SlimLP 5.1.1 RRO Layers
[SuperSU] iall5tar:
Hi thanks for your fast answer,

i installed super su from Market then flash v.249...

i also installed supersuPro.

apparently apps that need root works great.

btw with v2.46 works great didnt get any notification about to update su binaries...
[SuperSU] lorenzitto:
No chance to root without using recovery menu?

Or simply install .apk file for superuser? :confused:
[SuperSU] mielletseed:
No. Some times there are bugs in ROMs that could be used for rooting. But these are getting fixed soon. For example there was towelroot to root some 4.4 firmwares ...
[SuperSU] NZgeek:
In order for your phone to get root, a small number of files need to be written to the /system partition. The OS prevents this partition from being written to by normal apps, including the app installer. This prevents you from simply installing an apk to root your phone.

There are 3 ways to write these /system files:

(1) Using existing root access.

(2) Exploiting a security bug to get write access to /system, e.g. towelroot. These bugs get fixed, which is why these tools only work on certain Android versions.

(3) From a custom recovery, which has full access to the file system and can modify anything it wants.

SuperSU will never use an exploit to install itself (although third party rooting apps may choose to install SuperSU). This means that in order to install SuperSU, you need to be already rooted or have a custom recovery.
[SuperSU] nubia11:
What is the am call?
[SuperSU] NeoLogY:
+1

Sent from here to there
[SuperSU] shaggyskunk:
The am call is "Wake Up" - lol

But seriously - I think that was a typo and he probably meant to say: su call - ie when to get SuperSU to call for permission

Sent From my SM-N910W8 Running SlimLP 5.1.1 RRO Layers
[SuperSU] garyfunk:
am is Android Activity Manager

Read this post from idone

http://xdaforums.com/showthread.php?p=60633669
[SuperSU] shaggyskunk:
K - I was looking at this:

http://su.chainfire.eu/

Sent From my SM-N910W8 Running SlimLP 5.1.1 RRO Layers
[SuperSU] coukou:
Hello

I have a Galaxy Note4 N910C with Stock Rom (Samsung original) XEH-N910CXXU1BOC3 Lollipop 5.01.

3 months ago, I had installed SuperSU 2.46 with Default access set to Prompt and Quick Boot (Reboot) and LBE security master were granted superuser permissions. Also, in SuperSu/Apps I got these 2 apps configured granted .

For some reason that I can't explain, SuperSu no longer granted access. I uninstalled it properly and reinstalled it... same problem

In fact, the problem is the following: If SuperSu/Settings/Default access is set to Prompt, I get Superuser Request, I press Grant then I get Appsxxx has been denied superuser permissions.

On the other hand, if SuperSu/Settings/Default access is set to Grant, all apps has supersu permissions granted.

Moreover, in SuperSu/Apps NO apps configured granted.

So, today I updated to SuperSu 2.49 beta via TWRP recovery... same problem: If Default access is set to Prompt all apps denied superuser permissions (see bellow image). I may set the Default access to Grant to get superuser permissions.

What is weird is that SuperSu (2.46) had worked well since 3 months until yesterday :rolleyes::confused:

Is any how to configure apps granted?

Any suggestion be welcome

Regards
[SuperSU] Pkt_Lnt:
What did you install or change yesterday? Post a logcat of this happening.
[SuperSU] garyfunk:
Go into SuperSu and uncheck Tap jacking then see if you can Grant access.
[SuperSU] coukou:
Well done:svetius: It works :D

Regarding SuperSU settings, do I've to check "Enable su during boot"?

what other settings to check/uncheck?

Regards
[SuperSU] tonii58:
KNOX

samsung have an limite root because of knox on lollipop and supersu never ask to disable knox notification

i have root but not fully :)and thx 4 ur great work
[SuperSU] rgrever2:
Working fine on otterx with AICP. Thanks!
[SuperSU] egingell:
SuperSU disables (freezes) all "knox" apps. You can try manually disabling them or uninstall them.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] Adizzzle:
Deleted
[SuperSU] harrymason37:
Xperia v jb 4.3 stock, noticeable bug: "binaries not found, the app will revert back to previous version " but it is actually installed after reboot
[SuperSU] shaggyskunk:
I'm guessing that you flashed the zip?

Sent From my SM-N910W8 Running SlimLP 5.1.1 RRO Layers
[SuperSU] pitsgraft:
Hi [MENTION=631273]Chainfire[/MENTION],

I installed your latest SuperSU 2.49, everything's work superbly on my D802 30b, all root access and permission work flawlessly.

But everytime i restart/ turn on my device after the startup process is finished i get a notification to update the superSU binary? And everytime i clicked just went to your app. No further instructions.

As attached

Cheers,
[SuperSU] boyheadkick:
go ahead and update it..i used normal mode..we're running the same rom
[SuperSU] egingell:
Except there are "no further instructions".

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] Pkt_Lnt:
Look at the second part of this reply from ChainFire in the [Stable] SuperSU thread.

http://xdaforums.com/showpost.php?p=60933992&postcount=9156
[SuperSU] harrymason37:
I extracted the apk from the zip file
[SuperSU] shaggyskunk:
Why didn't you just Flash the zip? Works every time.

Sent From my SM-N910W8 Running SlimLP 5.1.1 RRO Layers
[SuperSU] mxxxw:
Hello!

I'm using SuperSU on my Pingpongrooted S6 and after I updated to 2.49 any new app I grant root access is not added to the "Apps" list in SuperSU. The actions are logged, but the app is not showing up in the "Apps" list. Look at attached screenshots

Also, "All in one gestures" sometimes looses root access and I have to open the app and enable it again.
[SuperSU] a g bell:
wont work on android m dev preview anybody intrested hanging at boot ani
[SuperSU] USBhost:
working awesome on the nexus player on android M

but I had to disable selinux to get it to boot.
[SuperSU] h4z3d:
Generally, how did you disable SELinux? I'd love to be rooted on M x).
[SuperSU] Megaflop666:
So, 2.49 is working on m of you disable selinux?
[SuperSU] a g bell:
how did you disable selinux you have a kernel?
[SuperSU] USBhost:
by adding androidboot.selinux=permissive to the kernel command line

but for me I like having it disabled androidboot.selinux=disabled

but if you add androidboot.selinux=disabled it may not boot

I had to replace the init file in the ramdisk to allow it to boot.

thanks to CM for there init file.

---------- Post added at 02:56 PM ---------- Previous post was at 02:54 PM ----------

yes
[SuperSU] Chainfire:
I will look at M when I can.
[SuperSU] chitownCL:
classic757, Would you tell us the method you used to root the Verizon Moto G please? I've searched for hours and couldn't find anything to get permroot. I registered just to ask you so I would really appreciate it. TIA
[SuperSU] M Diddy:
Chainfire,

Just an FYI, tried flashing the 2.46 build on a cleanly installed N6. Zip seemed to install just fine, but, when the phone rebooted, it comes up saying the phone failed verification and will boot up in 5 seconds. 5 seconds go by and nothing. All I get is a black screen.

The phone is on, just not doing anything. Hope this helps a bit.
[SuperSU] Lawn Gnome:
Since I don't want to unpack and repack the ramdisk, I've been poking around on my Nexus 5 running Android M. I can get past the boot loop by setting the SELinux context on /system/xbin/daemonsu to u:object_r:zygote_exec:s0 to match /system/bin/app_process32_original, but attempting to run /system/xbin/su just results in exit code 1. (I'm guessing it too needs a different context, but I don't know what it requires.)
[SuperSU] jerflash:
Hey can you post your nexus player edited boot image with SElinux disabled? Thanks!!
[SuperSU] USBhost:
enjoy

note: the kernel is built with

-O3 and updated to 3.10.79

if you only want the stock kernel

just tell me
[SuperSU] jerflash:
thanks dude! ya post the stock also if you can. why not do a thread on the nexus player forum also?
[SuperSU] USBhost:
all stock

with selinux disabled
[SuperSU] SamuriHL:
You're a saint, brother. :) You'll have an army ready to test whenever. I just clean installed it to my NX6.
[SuperSU] CarboN Juniors:
I am having a problems installing SuperSU on my ZTE Blade S6. I cannot install the binary. I believe my phone is supposed to be done on 'Normal' but I have also tried it on the secondary option.

I have roots my Blade S6 with kingroot as this is the only option at this time any would like to move to SuperSU...
[SuperSU] SacredDeviL666:
you don't by any chance could upload a modified image for hammerhead with selinux disabled? if so it would be really helpful
[SuperSU] Creative9170:
[MENTION=5501864]USBhost[/MENTION] please make it for hammerhead too if you can , thanks bro :)
[SuperSU] skhjpz:
Can I also ask for shamu?
[SuperSU] Koragg618:
If you guys can wait, I'll try to make one for the hammerhead when I get home (6 hours), maybe someone might make one before?
[SuperSU] pavik62:
Yes! We are waiting for you
[SuperSU] USBhost:
edit: someone told me it still did not work

so i removed it

i will most likely get the nexus 9 one working

but for the nexus 5/6 sorry
[SuperSU] skhjpz:
Could you post shamu as well?
[SuperSU] fooznugget:
Thanks, but my Nexus 5 won't boot with this img. Boot fails then it loads recovery instead.
[SuperSU] USBhost:
hmm can you try the other one

i may have accidentally mislabeled them lol
[SuperSU] fooznugget:
Actually the other file is named recovery.img and is 18.5 MB. Judging by the size, I don't believe that one is the correct one for the Nexus 5.
[SuperSU] USBhost:
dont tell me lol

i was too sleepy last night

i will get the new on up soon

sorry guys
[SuperSU] mikaole:
same here, but thx anyway for the try. :)

lets wait for the master :)
[SuperSU] fooznugget:
haha no problem. I'm not complaining when you're the one doing all the work.
[SuperSU] a g bell:
No news from cf yet

?

---------- Post added at 06:13 PM ---------- Previous post was at 06:12 PM ----------

For me:)?

Sent from mey Nexus 5 using XDA Free mobile app
[SuperSU] datajosh:
Not surprising since he said he had early appointments today.
[SuperSU] mikaole:
If you fix it I will call you master all the time:)
[SuperSU] Koragg618:
Did you replace only the init? I was able to get the phone to boot with init from CM and androidboot.selinux=disabled, but when I flashed SuperSU, it refused to boot. Am I supposed to copy all the init files (init.rc, etc)?

Thanks in advance!
[SuperSU] a g bell:
Sorry difference in time zones maybe?
[SuperSU] datajosh:
Yeah, the time zones throw us all off :)
[SuperSU] mikaole:
Think I'll flash back velo for now. Hope su is coming soon
[SuperSU] a g bell:
Yeah let's hope so?
[SuperSU] Fluidification:
I have been trying to set selinux to at permissive, but despite adding androidboot.selinux=permissive to the commandline, (i unpacked and repacked the boot.img) when I run adb shell getenforce it's still set to enforcing. (hammerhead)
[SuperSU] x10man:
I've had the same problem. If I use fastboot to boot the stock image with androidboot.selinux=permissive the device just sits at the boot loader screen(or google screen), and never actually starts android.

For reference, the command I was using was "fastboot boot stock boot.img -c androidboot.selinux=permissive"
[SuperSU] garyfunk:
Generally we wait at least 48 hours before asking.
[SuperSU] lcallahan70:
Have you tried disabling SELinux completely?
[SuperSU] x10man:
When using that command, disabling SELinux produces the same results. I haven't however tried completely disabling via ramdisk changes yet, although I am not entirely sure where to look to make such a change, but I will probably give it a shot tomorrow.

Thanks,

X10man
[SuperSU] a g bell:
Depending on your time zone
[SuperSU] lcallahan70:
I don't know if it's been posted or not yet, but I tried to mess around with the ramdisk a little bit. The resulting img file flashed okay, but when I went to boot up, it got to the Google logo, shut down, then booted into recovery. Not sure if this helps at all, but I figured I might as well try.
[SuperSU] garyfunk:
Seriously?

48 hours is not time zone dependent.
[SuperSU] CSX321:
But is it 48 Metric or Imperial hours?

(No, it wasn't seriously. I'm sure it was a joke.)
[SuperSU] USBhost:
i guess I can try getting it booting

i will test on the nexus 9

and reportback

getting root on the nexus player was easy lol
[SuperSU] Isus <3:
Chainfire has life, asking for it continuously won't change things, it's just gonna make it worse. Patience is the key.
[SuperSU] shaggyskunk:
There used to be an app on the store for changing the SELinux setting to Permissive - Don't think that SuperSU has anything to do with it - It's the Kernel - Nothing to do with Root

A link to the app has been posted here and there - Search Viper4A threads ?

Sent From my SM-N910W8 Running SlimLP 5.1.1 RRO Layers
[SuperSU] crazyeats:
Seriously? You do know root is needed to use that app right!?