yashsingh1/xdaforums huggingface dataset:
[SuperSU] shaggyskunk:
If you're still having issues with SuperSU 2.46

Download and flash the beta zip 2.49 from here:

http://xdaforums.com/showthread.php?p=55256620
[SuperSU] NeoLogY:
I hope he didn't extract the zip.

Sent from here to there
[SuperSU] CarboN Juniors:
Yea that doesn't work either not I didn't extract the zip lol

Might have something to do with the phone its self
[SuperSU] NeoLogY:
I remember someone important in this thread said, if the SuperSU granted any apps asking for root privilege, without any problem when using the root app, then just ignore the update warning. So, I hope you're in this case.

Sent from here to there
[SuperSU] CarboN Juniors:
SuperSU doesn't do anything ATM it won't even install kinguser I'd doing all the work but its in Chinese and I don't particularly want kinguser as I feel I can count on supersu like I allways have...
[SuperSU] NeoLogY:
Try use this word in search, "replacing kinguser with SuperSU". I think someone did explained it well before, just not so sure when and who.

Edit:I'm not sure if this one can be trusted, but, just give it a look.

http://xdaforums.com/showthread.php?p=59282045

Sent from here to there
[SuperSU] CarboN Juniors:
I think that it is going to be phone specific. However I look as well I did find it on my phones about page I'll link you and I'll search for what you tyed thanks

???

http://xdaforums.com/showthread.php?p=60818978
[SuperSU] NeoLogY:
Glad you found it. And don't forget to help if someone else asking the same problem, better keep that link.:thumbup:

Sent from here to there
[SuperSU] albert_htc:
Hi

Nexus 5

I was running 5.1 stock and rooted with supersu.

I've manually flashed 5.1.1 and that seems to have gone well..the phone is up and working.

I downloaded SuperSU 2.46 and flashed it via TWRP, phone rebooted and I had a superSU icon.

When I click on it I got an error saying no binaries are installed.

So I booted to TWRP and flashed it again, then when exiting TWRP I was asked if I want to install SuperSU so I said yes.

Phone rebooted and now I have a superSU installer icon. I've run that and selected TWRP.

It downloaded a file, rebooted to recovery, flashed and restarted the phone.

The phone is backup but not rooted. I still have a superSU installer icon..

How do I root this phone ?

Thanks
[SuperSU] MrKaon:
Are you using latest TWRP?
[SuperSU] albert_htc:
I'm running twrp 2.8.6.0

Do I need to update it ?

Thanks
[SuperSU] a g bell:
Yes that was buggy
[SuperSU] Joker87:
Is there anyway to wipe supersu datas like a normal app? Wiping from settings doesn't work (option is greyed out), I tried wiping data from the app settings and didn't work either, I rebooted and ended with a bootloop. Fortunately removing the battery worked, after reboot it was everything like before

PS: I managed to do that manually, with es file explorer
[SuperSU] albert_htc:
Can you advise which version I should use.

Thanks
[SuperSU] aavvaallooss:
2.8.6.1

https://dl.twrp.me/hammerhead/
[SuperSU] ZANIUM:
Thanks OP :)
[SuperSU] mopartonyg:
LG VK810 Bootloop

[MENTION=631273]Chainfire[/MENTION], trying to flash 2.46 onto my Verizon LG gpad vk810 with the new LP update and bootloops evey time. Have tried 2.48 and 2.49 betas also with no luck. Flash the rom it boots up flash rom and supersu it loops. Any help would be greatly appreciated.Does not happen to everyone using it. Let me know if you need more info. Thanks
[SuperSU] schwem:
What exactly are you using to flash it? Do you already have custom recovery or are you flashing with flashify or rashr? You know you can't just flash supersu on LG devices in order to root right? If you did not know that there is a couple root exploits on xda for LG devices. One is called one click roit for LG devices. The ither is DP Root which is an easy gui style root that you use on a windows pc. I used DP Root on my G Pad V700 and ny G3 VS985 and it worked great. Both root methods utilize an exploit that LG did not account for in their built in download mode. There is more info on how this works on both threads I mentioned. If this is not the case and you were already once rooted and flashed a custom rom and this version of supersu is causing conflicts then try chainfires beta supersu 2.49 as thats what I had to do because the stable marked version 2.46 was causing issues on both my LG devices. My V700 and my VS985 after each received lollipop updates. Hope this helps.
[SuperSU] mopartonyg:
thanks for the reply, I have been trying every root exploit I can find. Both the ones you mentioned do not work. I am flashing through twrp with a LP Stock rom. I tried the updated dproot also. Can root 4.4 easily but can not root 5.02 LP. Thanks again
[SuperSU] sfs15:
Does it work with Android M, and with multirom?
[SuperSU] purian23:
Buddy you really have to read at least the last two pages..
[SuperSU] MrKaon:
Flashing Code Blue Kernel and latest SuperSU Beta will give you root on Android M Preview.
[SuperSU] kgptzac:
Two question/suggestions after trying to bypass root check to play certain games.

1. What is deamonsu and why is it not deleted when I "temporary unroot" from SuperSU app? FYI the game checks for both the su and deamonsu binary. It seems that temp unroot would delete su but not deamonsu. However deleting deamonsu makes SuperSU something's wrong with the installation. I think deamonsu should get the same treatment as su in temporary unroot.

2. SuperSU.apk file name is also a trigger. Does rename the file name have any impact on future app updates? If not, may I suggest an option within SuperSU that would randomize the apk file name?

I think nowadays being able to easily hide root access is almost as important as having root itself. I think (maybe even as a pro addition) SuperSU should provide more means to hide itself.
[SuperSU] _jis_:
Did you try cloakroot?

Tapatalk Pro 4.6.2
[SuperSU] sfs15:
But no way with stock kernel? Maybe Chainfire makes it possible in some days?
[SuperSU] MrKaon:
There is a patched stock kernel as well.

I'm sure Chainfire will fix it in future.
[SuperSU] Mikanoshi:
Is there a way to get root access status without showing request window? I just want to silently fail if root was not given before.
[SuperSU] ktmom:
In the settings, couldn't you just set it to deny all requests?
[SuperSU] PalmCentro:
Disable notifications in SuperSu settings...
[SuperSU] Mikanoshi:
I don't want to deny root. And I cannot be sure that root is granted or not.

I'm running a root command immediately after boot animation ends from system process using Xposed. If Android System is not granted root or "Trust system user" is not checked, then device freezes with a request window on screen. I just want to prevent this. It should silently check if root can be used without any requests.
[SuperSU] twobats1:
Enable Su during boot ?
[SuperSU] Mikanoshi:
It's not during boot, this option doesn't matter. You also don't understand, I cannot do anything with settings. User installs my Xposed module, enables mod, reboots and gets a freeze.

There is no way to request root for system process before the reboot, because Xposed module is not yet active.

I could add a red warning for users that will remind them to add Android System and allow root for it or enable that system user option, but it's only a reminder. I should be able to check somehow if user followed the instructions.
[SuperSU] egingell:
You'll probably have to settle for a warning.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] egingell:
Yes, yes. Settling is bad, but the bottom line is that if you want SuperSU to allow the call after a reboot, at some point prior to reboot, you have to make SuperSU ask (dummy call by Android System) and the user has to allow it. If the user blocks it, it's out of your hands.

Now, you said you're doing this with an Xposed module? Ideally, you shouldn't need su anyway.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] Mikanoshi:
Tell it to enforcing SELinux :) On permissive Xposed can do anything, even install its own su binary on boot and use it without any requests to the user.

On enforcing I can't even read SuperSU shared preferences xml from the process with root privileges! Damn security))
[SuperSU] egingell:
Yeah, that would need su.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] silvertrain78:
The patched stock kernel you mention... Where can I find it?

Thanks
[SuperSU] jreink01:
Does anyone know how i can get v2.49 ? I am currently on v2.46 and the issue i am having, was told to update and that would probably fix it. Looking on this thread the first page, when i download the zip, it says v2.46. Google Play also says v2.46
[SuperSU] Pkt_Lnt:
It's the second pinned thread in this same SuperSU forum.

http://xdaforums.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
[SuperSU] Rjrocks22:
ScreenOn Wakelock

Hi [MENTION=631273]Chainfire[/MENTION]

I'm getting a screenOn wakelock by SuperSU app. I'm on Andriod 5.0.2 CM12s ROM. I'm also attaching the screenshot for the same. Can you please help me how to fix this issue?
[SuperSU] DutchMan_1990:
enquiry

Is there any way to bypass CM12 built in super user with supersu?
[SuperSU] NZgeek:
When you install SuperSU, it takes over from the superuser that's built into CM. All requests for root are handled by SuperSU.

There is one SuperSU setting that you may need to look at, called Respect CM root settings. When this setting is turned on, SuperSU will check CM's setting about whether root should be enabled (Settings > Developer options > Root access). If you don't see the root permission dialog when you think you should, you can change either of these settings and checking if that helps.
[SuperSU] PIRATA!:
Hi to everybody.

After those asking about SuperSU and KingRoot, I'm back for telling my experience with rooting my Samsung S5 G906K.

I've decided to go for a deodexed rom, custom recovery and so KNOX 0x1.

I've flashed stock BOE1 (actual last version for my device) from firmware downloaded from Korean forum (as on Sammobile is broken).

Then flashed aeter97's BOE1 rom.

Flashed Philz unofficial recovery (no official for us).

Then for gaining root, I was told to try to simply flash original UPDATE SuperSU 2.46 by Chainfire...and I ended up having root!!

I didn't knew that that could be possible for my device.

I have to say that here someone told me that on some devices that could be possible...then another user from this community that has my same device told me that he was always routing like that from ages for any devices he had...and so I tried and I have root now!

Quite amazed...and happy about it.

I have then a question about root and KNOX:

I see to have installed the "KNOX" and "KNOX II" apps, that I assume are from Samsung.

I remember that on some threads here there were some advises on disabling/uninstalling those system apps with TB after having gained root and if on KNOX 0x1.

Do you people think is something should be done? Wouldn't it affect any root?

I hope my question it's not so OT.

I have another question related to root and apps that need root. Hope not to be too OT now:

I don't have BusyBox installed.

Is it better to install it? If so..which version?? From where?? Play Store or some free version here on Xda??

Tnx.
[SuperSU] Mike B.:
This is a thread about the stable version of SuperSU. Yes, you're OT and OT again. In the future, please

search

to at least find the appropriate thread in which to ask your many questions.

To save time and aggravation:

Knox is unrelated to SuperSU or root. If you've already tripped the Knox flag then the Knox components are effectively useless and can be deleted. Read up on the (un)importance of Knox if you need more details.

Busybox may need root but it's unrelated to SuperSU. If an application requires busybox, install whichever busybox is more convenient for you (usually simply from the Play Store). For further information, look up what busybox is and does.

If you need more,

SEARCH!
[SuperSU] sghens:
+1
[SuperSU] shew4s:
Nice

Ery good
[SuperSU] pupps96:
Very good
[SuperSU] Benrap:
The hebrew translation is finished... can the dev please update the app?! Thx
[SuperSU] PalmCentro:
[MENTION=631273]Chainfire[/MENTION]

We need some app or script to remove kinguser!

They block SuperSu and the block uninstalling Kinguser

---------- Post added at 03:12 PM ---------- Previous post was at 02:56 PM ----------

תודה רבה!

I guess in the next update...
[SuperSU] gorilla p:
You can try a root uninstall app, you can also try the method mentioned in the last post (#10) in link below

http://www.chinaphonearena.com/forum/Thread-Question-Substitute-kinguser-with-supersu
[SuperSU] PalmCentro:
I know these things... In the past they worked but lately Kinguser blocks the uninstalling it.
[SuperSU] shaggyskunk:
Depending on your device - Flash stock and root with Chainfire's Auto Root - or Flash TWRP img.tar and Flash a custom rom with Root built in

Sent From my SM-N910W8 Running SlimLP 5.1.1 RRO Layers
[SuperSU] PalmCentro:
Talking about devices that are not CF supported and they don't have any custom recoveries either...
[SuperSU] shaggyskunk:
That sux....

Sent From my SM-N910W8 Running SlimLP 5.1.1 RRO Layers
[SuperSU] NeoLogY:
The best way in my mind now is to learn to port TWRP to our device.

Sent from here to there
[SuperSU] PalmCentro:
Oh! that's what i keep telling myself..... I hope one day i will really learn it!
[SuperSU] Kateuka:
Great support [MENTION=631273]Chainfire[/MENTION], ;)
[SuperSU] starkly_raving:
[MENTION=631273]Chainfire[/MENTION] I'm sure this may have been brought to your attention but root breaks the camera on LTE Moto E 2015/Surnia. There's been talk of dm-verify, SELinux and other issues thank may be causing this. There's some dirty work arounds but they only last till next boot.(Like booting into safe mode then back to normal boot up)

Your attention/input regarding this would be greatly appreciated. Thanks in advance for your consideration.

Regards,

Chris
[SuperSU] Mike B.:
I believe that's a

kerne

l issue not directly related to SuperSU. Have you tried with a permissive kernel such as Squid Kernel?
[SuperSU] NZgeek:
It'll help a lot if you can capture a logcat of the issue. The log should include information about the problem and why it's happening.

Permissive SELinux is a workaround, not a fix. You're turning off a huge chunk of system security in order to avoid some localized problems. It's like leaving your entire house unlocked because a newly cut key doesn't work in the front door.
[SuperSU] Mike B.:
I won't comment on SELinux and "system security" concerns but you are correct, permissive mode is merely a way around a limitation of that camera app and it probably would be nice if Motorola were to fix it but then they don't exactly encourage rooting so it's unlikely to be a major priority for them. To use your analogy, there's nothing obviously wrong with the key (root) but the lock (camera) seems to malfunction! ;)

That said, since this issue isn't specifically related to SuperSU in general or the stable version in particular, this thread might not be the best place to discuss such matters.
[SuperSU] starkly_raving:
Logs....

https://drive.google.com/file/d/0B46DbOH2IgChc053NmZBai1vek0/edit?usp=docslist_api
[SuperSU] A San:
I am on rooted Verizon Galaxy S5 Lollipop. I've just noticed that some new application that need root didn't work. But old application like Titanium, Xbooster etc still work. I've checked the setting of the supersu. And I just wonder if this is happened when I changed the supersu to /system. Is there a way to uninstall it from system?

Thx.
[SuperSU] priyam basak:
If you uninstall supersu you will lose root.
[SuperSU] starkly_raving:
All 3rd party cameras including Google camera face the same issue. So I wouldn't say it solely a Motorola Camera issue. As far as root friendly, I'm not sure what your talking about...Moto made the Nexus6 and the entire Moto series has a huge development following, OEM unlock included. Back in the OG locked down Droid X days maybe but not now. [emoji6]
[SuperSU] MrKaon:
Sorry it was my mistake there is no patched stock M kernel, what we have is few custom kernels with disabled SELinux security in order to have ROOT access.

My guess is Chainfire already have a solution but better not public it till final built of Android M.
[SuperSU] frogt9:
Can you please add option to hide root? Many games & apps doesn't work because of it, so this would be really helpful.
[SuperSU] milojoseph:
This would be a great feature or app

Sent from my SM-G900T powered by Alliance Rom and ktoonsez kernel
[SuperSU] PalmCentro:
[MENTION=5049505]frogt9[/MENTION]

Some xposed modules can do that...
[SuperSU] milojoseph:
people would like the option to do certain stuff without xposed as it's not stable
[SuperSU] Fox1Lead:
Hello, as i wrote in

http://xdaforums.com/general/xda-assist/root-samsung-xcover3-sm-g388f-t3135553#post61360838

i but the 2.46 zip file to the sd root

and startet the upgrade process now after almost one hour

i only see the android logo

Downloading ...

Do not disconnect USB Cable During the software update!

how long should this usually take

and what should i do now?

remove the akku or wait until it is empty it was around 95% loading when i startet the process

thank you, please advice :) phone is junst 4 days old

thanks ahead
[SuperSU] Masterchief87:
It sounds like you are trying to flash the supersu recovery zip through Odin in download mode which would be your problem. It needs to be flashed through a custom recovery like CWM, TWRP, or Philz. Do you have one of those installed?
[SuperSU] Fox1Lead:
yes you are right after removing the power soure the phone is working again but

i cannot Access the recovery menu anymore ....

if i try it always try to start the Flash

i already removed the zipfile from the sdcard, but this doesn´t help

phone is working but no Access to recovery mode anymore,

i hope this can be sovled?

and also no root activated (wich is clear :) )

ok iam a bit stupid :)

power + home + vol up = recovery menu

power + home + vol down = flashing from external source?

so no Problem right now but no root :(
[SuperSU] Mike B.:
If, after a full battery-off reboot, when you use the proper "boot to recovery" sequence for your device, (VolumeUP + Home + Power?), you don't actually get into recovery, there's a chance you might have inadvertently wiped your recovery partition or loaded something you shouldn't have in it. It might be wise to reload the custom recovery using whatever approach you originally used. It might also be a good idea to immediately run a full nandroid backup on your SD card just in case you clobber something again in futures attempts.
[SuperSU] Fox1Lead:
thank you very much :) for right now everything is back normal

can you please give me an advice how to get root right to this phone?

ich just Need it for installing Bluetooth rsap because the Samsung stock sap Profile Fails to work

thank you very much
[SuperSU] Mike B.:
Someone in the areas where your phone is supported should be able to advise you, but once you have a proper custom recovery (TWRP?) you can certainly try to flash (through recovery,!) a SuperSU ZIP, either the stable 2.46 or if necessary the 2.49 beta (in the beta thread). As long as you have a good full nandroid backup you can experiment in relative safety... ;)
[SuperSU] Fox1Lead:
iam sorry but i cant follow your instructions

i think i Need something on my Computer what is streamed via usb

but i must say the stock Rom is ok for me i just Need the root right for installing the rsap application, i guess there is no easy way?

iam very familiar with pc and Network and also Windows mobile 4,5 & 6 but android is completly new to me :)

so thanks for any advice
[SuperSU] garyfunk:
You get root from a custom recovery and SuperSU.
[SuperSU] Mike B.:
First install a custom recovery such as TWRP then flash the SuperSU ZIP from that recovery. You seem to be a W*ndows user and I have no clue on how to use that but I'm sure there is a Redmond-approved version of adb (Android Debug Bridge), fastboot, etc to quickly install a recovery. You'll get root but that won't change anything else on your ROM. The process is often very painless when done right and you might not even need a PC except maybe for the initial install of the recovery.

That said, since you seem a bit hesitant about the whole process, you might want to make sure you absolutely need root at this time as there might be other ways to talk to your car. This is best discussed wherever rsap and VW meet... wherever that is... ;)
[SuperSU] Fox1Lead:
Thank you very much ich will Google your hints tomorrow ....

i only bought Samsung because of the integrated sap Profile but if the car connects

the phone tells me i have removed the simcard

otherwise i can use handsfree Profile but for me traveling alot this is no Option because of the very bad Network Connection :(

so andriod-rsap app will be my only hope :(

i had a htc touch pro 2 wich worked perfekt with the car but now the phone is total down so i cant Switch back.

i Need to find a solution :)
[SuperSU] Mike B.:
Don't forget to check with VW also. Often it's the car firmware that needs updating. Happy sleuthing! ;)
[SuperSU] Fox1Lead:
this part i know alot better

ist easy buy a new Bluetooth unit :(

not my favorite solution
[SuperSU] nex86:
Hello!

I flased Supersu v2.46 on my Nexus 4 using TWRP, then I upgraded to PRO on play store.

But it still says SuperSU FREE in the app. How come?

I rebootet my device but that didn't help.

I'm running stock 5.1.1 just saying.
[SuperSU] marknoll:
Reboot to recovery and wipe cache and dalvik cache...reboot
[SuperSU] nex86:
Tried that, and it didn't work.

Probably a compatiblity issue with 5.1.1.
[SuperSU] Mike B.:
I suggest you check the

beta thread

. Even the latest 2.49 beta there isn't quite ready for this new 5.1.1 from what I understand, and it's best to discuss that there as opposed to here. ;)
[SuperSU] Crapping_Bricks:
Dialler codes

Hi guys I just rooted my S2 with SuperSU installed and the view firmware code *#1234# opens up SuperSU rather than the interface with my device info. I am aware of the two codes that open SuperSU (*#*#1234#*#* or *#*#7873778#*#* (*#*#SUPERSU#*#*) Mine opens with *#1234# I understand that chainfire states that there can be variations but he states that they differ by excluding one or two (*#) so I was wondering if there was a way to stop SuperSU recognising the *#1234# code so I can see my firmware information once again. I am running a GT-I9100T with NeatROM extra lite.

Thanks guys!
[SuperSU] Mike B.:
I don't have a SG2 handy right now, but even though you might first get to the SuperSU screen when dialing #1234#, exiting that screen (the "back" key?) should get you to the version screen (AP, CP, CSC). Note that you can also get that info from various apps, such as the thorough "Phone INFO" one from the Play Store.
[SuperSU] Crapping_Bricks:
Thanks! The app works but pressing back on the supersu window does not.
[SuperSU] It_ler:
I think it's related to missing system apps in you ExtraLite version.

Please ask in Neatrom thread, or just install Neatrom Lite.

I had Lite version on my S2 and and the system menu was visible after closing SuperSu app.

Signature:

Device:

SGS5 (SM-G900F)

ROM:

AllianceROM v8

Kernel:

Stock XXU1BOC7 kernel

Recovery:

TWRP recovery by Ktoonsez

Modem:

XXU1BOC7
[SuperSU] cavaliere336@gmail.com:
Binary update

Motorola xt530

Android 2.3.5

SU 2.46

The SU binary needs to be update when I press continue,

choose normal, but installations failed , why?
[SuperSU] garyfunk:
What ROM are you on?
[SuperSU] lolle.santoso:
The SU binary needs to be updated. Continue ? Press Normal Installation failed !
[SuperSU] Mike B.:
I see you're new here, but you should consider reading the OP before posting. If you had, you would have seen:

That said, the most common solution is to flash the current UPDATE ZIP (see link in the OP). There is also a thread about BETA versions of SuperSU but I'll let you search for that one on your own... ;)
[SuperSU] tkjeeper:
Repeating the same thing won't help. We don't spoon feed here.
[SuperSU] lolle.santoso:
Updating the binary failed