yashsingh1/xdaforums huggingface dataset:
[SuperSU] WeT-Klb:
My wife and me both have the same N7105 on 4.4.2.

Two days before mine was offered the 2.46 - my wife´s phone still run 2.40 and still didn´t get any updates.

So the same phone - but one with 2.46 and one with 2.40-

C U

WeT-Klb
[SuperSU] MrKaon:
Stage roll out, you will get it soon.
[SuperSU] YK RAJ:
Yes,waiting for that bro.I don't know why someone received and someone waiting.This is the 1st time issue which m facing.
[SuperSU] remotehugger:
I'm waiting too - lol -

from my VM SGS3 - jdsingle76's rooted 4.4.2 NDC - stock kernel (for now ?) ?
[SuperSU] onlyfor.foren:
Yesterday i make a fresh install with CM12 on my Galaxy S2 and after this

i install SuperSu and Pro with playstore. My Version is 2.40.
[SuperSU] draskome:
I have frustrating issue with downloading superSU from the Playstore. Just started rooting my LGG2 and since SuperSu have in app purchase built in, I canot install it (not available in my country). Just searched all around XDA for direct APK download link, but haven't found it.

anyone have a solution for this? Direct download link or link to any other safe download site would be very helpful :)
[SuperSU] Ja_som:
http://xdaforums.com/showthread.php?p=58736039
[SuperSU] Mike B.:
Come on people, read the OP. At any time you can download the very latest SuperSU from:

http://download.chainfire.eu/supersu​

If necessary you can even extract Superuser.apk and the appropriate su binary from the ZIP.
[SuperSU] Fant0m3:
just curious

Is there any plans to add like an browser into the app that you can go through and control the super user access before it prompts u for it. Cause if anyone else is like me then you already know most the apps or all that use root and you clean wipe reinstall and mod phone a lot I just believe showing these apps in ui before they ask permission to have such rights u can grant it would be amazing. If not then it's cool just curious
[SuperSU] Frank Westlake:
I can't figure out what you are asking; maybe it would be better to use more accurate terms. Have you run the SuperSU application and seen the three tabs (Apps, Logs, Settings)?

Frank
[SuperSU] Fant0m3:
Okay so before an app has permissions from su it has to start on its own. I was wondering if you could add support to show all apps that ask for permission before starting each individual app so I can just grant them all at once when I set up SuperSU
[SuperSU] SyCoREAPER:
Mine tells me that my binary is out of date with no way to update it. On 2.46. Also, I don't have a custom recovery to flash
[SuperSU] Frank Westlake:
There isn't any way to know which applications have the ability to start a shell process and run 'su'. Some applications have a custom permission for superuser access but that permission is not required so it won't provide a complete list. If you have experience manipulating files with the shell then you can set your initial configuration by manipulating SuperSU's private directory.

Frank
[SuperSU] Mike B.:
Since presumably you have root access and the ability to modify /system, you could extract the appropriate "su" binary from the update ZIP and manually move it into place (typically in /system/xbin/) with proper permissions. Make sure to have a

good nandroid backup

and a way to restore before you attempt this in case something goes wrong. If a custom recovery is available for your system, consider installing it as it tends to make life much easier.
[SuperSU] iMakeTea:
I rooted on an HTC One M7 using TWRP and the zip file for SuperSU 2.46. Now I'm trying to unroot using the full unroot option and via root browser deleting the su and SuperSU.apk files in the system folder but nothing works.

The phone reroots itself on start up even if I use the full unroot option from within the SuperSU app. This doesn't seem normal at all, and googling this issue doesn't seem to give any results. I can't convert it into a user app from a system app. Link2SD asks to restart every time I try but it ends up as a system app anyways.
[SuperSU] egingell:
S-on - it's an HTC.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] SyCoREAPER:
Unfortunately there is no custom recovery which is why I'm stumped what to do. However the question remains of why supersu can't update it or is supersu 100%only an interface? I will try your method in the meantime
[SuperSU] IronTechmonkey:
I flash ROMS a few times a week and think this is an interesting idea although probably not workable. The way I deal with it is by incorporating an SU permissions step into my ROM installation and build-out process. After I restore apps from TiBU I run each app that requires permissions and grant those permissions. This is manual and somewhat inefficient but it is effective, and relative to the 90 minute installation/build-out process the time spent doing it is negligible. I would also add that the per-use pop up requesting permissions is more secure than mass approval.
[SuperSU] NeoLogY:
Agree with your way, so we could know exactly which app is using what kind of permission.

By the way, is there anyway to set shell sequence, which shell run first, i mean on boot, because i want to give proper app sequence during boot(if possible).

Thank for any idea.
[SuperSU] leetlover:
GT-I9505 Lollipop SuperSU doesn't work

Hi, I installed the I9505XXUHOA7 leaked build for the Galaxy S4 (GT-I9505) and (on top of losing all my data with the upgrade, did not backup before...) I have found that SuperSU 2.46 does not work on this build. I have flashed the firmware with Mobile Odin, upgraded the SuperSU apk in Mobile Odin's /data storage and everytime I try to use su, it just hangs. I suspect it's a SELinux issue, stracing the su binary reveals that it receives timeouts trying to use the /dev/ptmx socket. daemonsu is successfully started as root though and it's listed as a running process. I don't think the SELinux policies have been installed, as the only binary in /system/xbin is the su one. All the supolicy stuff is missing. Is there any way to fix this, as it is driving me insane? Can I somehow talk to daemonsu and disable SELinux temporarily or invoke commands?

Please note that I cannot flash the UPDATE zip, as I am Knox 0x0 and running the stock recovery.

Thank you in advance and sorry if this is meant to be in the Mobile Odin section. I know that ideally, Mobile Odin should use the latest SuperSU package and it would install everything properly.
[SuperSU] Mittaa:
How can you have Knox 0x0 and being rooted at the same time?

Just curious ;)
[SuperSU] fubo73:
Are you joking? There are plenty of threads explaining how to keep Knox 0x0 for a lot of phones.
[SuperSU] Mike B.:
As [MENTION=631273]Chainfire[/MENTION] mentioned

HERE

, the current Mobile Odin embeds an old SuperSU 1.94 and should NOT be used with KK or LP. Changing the internal SU version is not sufficient to make it magically functional. If you somehow insist on using the stock recovery you might not have many options at this time.
[SuperSU] iMakeTea:
Will look into it, thank you! I forgot to mention its a dev edition HTC One M7 with an unlocked boot loader if it makes a difference, but from the sounds of it S-Off should allow me to delete the SU file and SuperSU.apk or just full unroot from SuperSU.
[SuperSU] Zaynconfused:
Su Binary not updating

Actually I am using micromax canvas fire2 A104 and i have rooted it and install clockworkmod recovery img after this i have changed my kinguser app with supersu app. My Supersu app on opening shows su binary update i am updating the binary it shows two buttons "normal" and "cwm/trwm" i have chosen cwm/twrp but it shows my device will reboot automatically it nots rebooting and i have also tried normal button but it show update failed.........

Please please help me to update su binary
[SuperSU] Mike B.:
I know nothing about your device and I don't trust recent CWM recoveries but have you tried flashing the 2.46 ZIP from recovery (see OP)?
[SuperSU] Zaynconfused:
Sir i have flash it but cant do the su binary update for which my device is showing not rooted properly please help me
[SuperSU] IronTechmonkey:
Interesting question though I don't know how to set order of apps running at start-up.
[SuperSU] NeoLogY:
As I remember, if it doesn't reboot automatically, you need to reboot manually into recovery.

And.... I'm not sure what to do from here(when booted to recovery). I'm sorry, maybe someone will recall.:p
[SuperSU] leetlover:
Well, if you don't touch the kernel and the stock recovery, Knox will play nice. I was even able to downgrade 5.0 to a 4.4 build vulnerable to towelroot and Knox is still 0x0.

Sent from my GT-I9505

---------- Post added at 10:55 PM ---------- Previous post was at 10:46 PM ----------

I do need the stock recovery, as I want to keep Knox 0x0, I see no reason to trip it when I can work around it.

Will modifying the embedded install-recovery.sh script to do a su - - install first work? :) daemons is starting as root and I see it running. The question is, will SU install everything if I go this route? I know that Mobile Odin doesn't support Lollipop, but Chainfire has not given any info on when he will release the update and I need root asap.

Sent from my GT-I9505
[SuperSU] Frank Westlake:
I don't know how you have tried to use 'su' but a failure of one type of use does not necessarily mean other types will also fail. Try variations of

su -c cp newsu oldsu

Frank
[SuperSU] theronkinator:
I've got root but it's put on some crappy Chinese SU app, trying to get rid but SuperSU is failing on updating binary, but supersu hasn't requested root which is why I presume it's failing. Anyway I can trigger supersu to make a request so I can allow it, root definitely works as I can get root in terminal and ES.
[SuperSU] leetlover:
Frank, thank you for the tip, I have already tried su -c variations, even su -s with a blank file as the shell doesn't work. I also tried various SELinux contexts with the -cn flag. The su binary just hangs and gets killed eventually. It's KNOX or SELinux blocking it I think, all I can see using strace is that it keeps getting a timeout doing a select() call on a socket. I do see daemonsu started as root though, so if I could somehow get a root shell or execute setenforce 0, everything would work. I wonder if su --install would install everything needed, cause I could modify the install-recovery script embedded in the Mobile Odin installation to execute it first. Any ideas or suggestions are HIGHLY appreciated.

Thanks
[SuperSU] Vinnom:
When I need it to work, I have to use quotes, but I think you may have tried it already.
[SuperSU] leetlover:
ioctl(0, SNDCTL_TMR_TIMEBASE or SNDRV_TIMER_IOCTL_NEXT_DEVICE or TCGETS, {B38400 opost isig icanon echo ...}) = 0
open("/dev/ptmx", O_RDWR|O_LARGEFILE) = 4
fcntl64(4, F_SETFD, FD_CLOEXEC) = 0
ioctl(4, TIOCSPTLCK, [0]) = 0
ioctl(4, TIOCGPTN, [1]) = 0
ioctl(0, SNDCTL_TMR_TIMEBASE or SNDRV_TIMER_IOCTL_NEXT_DEVICE or TCGETS, {B38400 opost isig icanon echo ...}) = 0
ioctl(0, SNDCTL_TMR_STOP or SNDRV_TIMER_IOCTL_GINFO or TCSETSW, {B38400 -opost -isig -icanon -echo ...}) = 0
ioctl(0, TIOCGWINSZ, {ws_row=0, ws_col=0, ws_xpixel=0, ws_ypixel=0}) = 0
ioctl(4, SNDRV_TIMER_IOCTL_STATUS or TIOCSWINSZ, {ws_row=0, ws_col=0, ws_xpixel=0, ws_ypixel=0}) = 0
write(3, "\n\0\0\0", 4) = 4
write(3, "/dev/pts/1", 10) = 10
select(5, [0 3 4], NULL, [3 4], {0, 250000}) = 0 (Timeout)
ioctl(0, TIOCGWINSZ, {ws_row=0, ws_col=0, ws_xpixel=0, ws_ypixel=0}) = 0
poll([{fd=0, events=POLLERR}], 1, 1) = 0 (Timeout)
nanosleep({0, 16000000}, 0xbefad350) = 0
select(5, [0 3 4], NULL, [3 4], {0, 250000}) = 0 (Timeout)
ioctl(0, TIOCGWINSZ, {ws_row=0, ws_col=0, ws_xpixel=0, ws_ypixel=0}) = 0
poll([{fd=0, events=POLLERR}], 1, 1) = 0 (Timeout)
nanosleep({0, 16000000}, 0xbefad350) = 0

This is the strace log by the way. Yes, I have tried quoting the commands as well. It's just something in SELinux blocking access to that /dev socket.
[SuperSU] egingell:
S-on simply means everything you do to the system partition must be done via recovery.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] Frank Westlake:
It seems unlikely but I wonder if it could be related to the application you are using to run 'su'. You might have some success by installing SafeStrap (http://xdaforums.com/showthread.php?t=2611107). SafeStrap uses 'su' to install some boot-intercept code into '/system/etc', which would probably fail on your device, but maybe not. If it does install then use that application to reboot into its own custom recovery, which is installed into a ramdisk and does not harm your stock recovery partition. Knox stays at 0.

If all that works then use that Recovery (a modified TWRP) to update SuperSU. Then reboot into the system and use SafeStrap to uninstall all that boot-intercept code, then uninstall SafeStrap.

Frank
[SuperSU] duongtm:
Can you make an option that after bought Pro version from GP store, the line Upgrade to Pro version in Setting will be disappeared
[SuperSU] _jis_:
It works automatically. Did you restart?

Tapatalk Pro 4.6.2
[SuperSU] leetlover:
Once again, thanks for the advice, Frank.

After going through the Safestrap documentation, I've seen that it uses a kernel exploit called bypassLKM which allows custom kernel modules to be loaded. This has been fixed in the new Samsung kernels. Interesting development though, I disabled and re-enabled superuser through the app and the phone is now in a bootloop, as I was expecting. However, I have adb access and I can get access to su -c commands as root. Invoking su normally gives me the shell but typing any command faces the same issue where it just hangs. The problem is that even if I can execute root commands with su -c, I can't do much as SELinux is blocking pretty much anything. I tried writing to /system/lib for example and it won't let me. I tried setenforce 0 and it won't let me. I tried to remove the SELinux policy from / and it gives me permission denied as well.

Do you have any ideas that I could try from this stage, with partially restricted su commands?

Thank you.

EDIT: I was able to get a successful root shell with su -s /system/xbin/sugote-mksh.

Apparently, the system shells were dropping context. I can now write to /system/lib, but still can't disable SELinux.

Going to try and fix SuperSU, but still don't know how to deal with the bootloop or what's causing it, probably app_process?

EDIT2: I HAVE SUCCESSFULLY FIXED IT, I NOW HAVE A FULLY WORKING SUPERSU INSTALL, KNOX 0X0 AND LOLLIPOP.

After getting a full SELinux init context, I was able to move libsupol.so in the /system/lib folder. Once I did that, I just ran supolicy --permissive.

Some magic happened when I did that (I suspect it removed the SELinux policies from init), I also ran su --install (which was still failing with an error about not being able to chcon ddexe).

All I did afterwards was reboot the phone and updated the su binaries through the SuperSU app. :)

Ahhh, the sweet taste of success!
[SuperSU] Frank Westlake:
Good work!

I use the Android application to read this forum so old messages are hard to find making it easy to lose continuity in a discussion, but I assume that the problem was an old 'su' that did not completely handle contexts. If that's true, do you think it would have helped, if it could be done at that access level, to 'adb push' the current 'su' to an executable location of '/data/local' and then use that 'su'? I rarely use ADB so I don't recall if /data is mounted or if it can be mounted at the given access level.

Frank
[SuperSU] NeoLogY:
Man... I'm totally out the league on this. :confused: I read about setting Selinux to permissive stick even after hard reboot, using commands. But not sure is it script or dd command, but it stay as permissive after reboot(not softboot but normal system reboot, as this being issues for Xposed user).

Just one question, is it the same issue here? ( SuperSU and Xposed)

BTW, really like the way [MENTION=218722]frank[/MENTION] explain. You make it much easier to understand.:thumbup::thumbup::thumbup:
[SuperSU] Sam7777777:
[MENTION=631273]Chainfire[/MENTION]

Sir could you please guide me on the issue i have

Sir i am using latest cwm flashable supersu.zip (v2.46) to root my device, which roots the device fine but after every boot, root is lost

I had this issue months back with my another device too (Note 10.1)

Now i am operating on mediatek 6592 device (Karbonn Titanium octane) running kitkat 4.4.2

I tried v2.02 which on which root is not lost but Titanium Backup doesn't work (Not restoring any app)

I am runnung cwm recovery v5 which is automade (since this model doesn't have official recovery i think)

Also i tried to use kingroot apk which roots the device but is in chinese + installs it's own super user app + T.Backup also complains of using this app (complains regarding binary)

I have no idea on what to do

Plz help

Thank you

Good day : )
[SuperSU] papatzis:
Hi

A little help please bacause I cannot understand what is going on here....

I have a no name 4.4.2, 10,1 tablet the only working root method is Rootgenius, but it installs a su app Kinguser ( I don't trust ) , I had tried many times to replace this with superSU but no luck.

The most strange thing is that when I try manual to install via recovery supersu.zip or manually via adb shell, I manage to install su binary, superuser.apk but when I try a app that needs root the su app doen't come up to ask if I want to give root access to this app. So I have no root ( SU access it is not given to apps by Supersu.apk )

If I try to unstall Kinguser.apk, root is gone, but strange I have root shell access via adb ( # prompt )

I had already installed stericson busybox

SuperSu says to update binaries but it fails. As I had said using Recovery Supersu is installed as system app but it is not working. If I had already kinguser installed and try to run Supersu the kinguser is not opens to tell me if I want to give Supersu root permitions. I had read in some forums that they replaced kinguser after they gave through kinguser root permitions to supersu but I have not that option

I am confused

I don't know what is going on,

Thanks in advance
[SuperSU] duongtm:
Not sure it works, I bought almost 6 months
[SuperSU] draplater:
I imagine a function that provide different selinux context to different app to restrict them.
[SuperSU] egingell:
I have no Upgrade button... and please quote the posts you reply to - don't expect people to read your mind or dig for your posts.

Did you download and install the Pro app? It's a separate app that activates the Pro features of the primary app and both must remain installed.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] huuho:
User rootexplore go to system app, delete king... app, go to playstore install su. Reboot.

Have fun.
[SuperSU] papatzis:
Had you done this by youself ? When I delete kinguser.app root is lost and supersu cannot update binaries not normal not even through recovery it says it is not rooted. I Don't know what is going on with kinguser….. Is anyone that managed to do this somehow?
[SuperSU] Mairo:
Su update failed with lenovo tab a3300h. Whitout custom recovery. Any solution? Su version is right now 2.40.
[SuperSU] Pkt_Lnt:
With no catlog or logs or screenshots, no.
[SuperSU] truelies1:
Htc one gets 'supersu binary needs to be updated'. Confused
[SuperSU] huuho:
Tried root via king.., normally, download su.apk lasters updat and install it, reboot, and confirm for king.. ask, update binaries, reboot.

User rootexplore go to system app delete king... app, reboot.

And

U can disable king... on settings/app/all app
[SuperSU] inlinez1:
I don't know why I've try every link, but I think I'm not flowing the steps in a row

:eek:
[SuperSU] papatzis:
This is the problem when I first run supersu, kinguser doesn't take over to give root permissions to supersu I had read it somewhere it has to do with the last versions of rootgenuis

Is there a way to force kinguser to give root priveliges to supersu?
[SuperSU] shrikanth191997:
supersu binary not getting updated

i am running rr 5.3.7 in my gti9152 i am unable to update supersu. It is constantly showing su binary us not up to date give me a solution i am unable to use any root app
[SuperSU] Fant0m3:
Now i understand there is no way of knowing which apps reqire a permission to be givilen this however can be worked around if your lets say for those who have the donate pro version can be linked to an android ID thus u can then save those of your apps that require said permissions and the settinga you added for those apps would automatically apply. Just an idea of course it would save some time but if your looking to add something new this could be a way to go. :good::good:
[SuperSU] AvgPhoneUser:
Hello. I rooted my phone with an old SuperSU version. I updated it to 2.40 through the Play Store. Weirdly, version 2.46 still isn't in the store for me. I updated it with an Apk. And in Google Play it is still 2.40. Can you help me?

Sent from my M512 that I like a lot!
[SuperSU] IronTechmonkey:
Playstore version, which is behind version being tested in this thread, is still at 2.40, at least for my phone and in a PC browser.
[SuperSU] AvgPhoneUser:
Ok thanks. So it will appear later in Play Store.

Sent from my M512 that I like a lot!
[SuperSU] dragoncon:
I have payed for the pro version but OTA survival doesn't show up in my menu's at all, (Sprint, Nexus 5 5.0.1 lollipop)
[SuperSU] jesssiii:
There is no survival in lollipop.

VZW LG G2
[SuperSU] Frank Westlake:
That's ominous.

Frank
[SuperSU] dragoncon:
Thanks I wasn't aware.
[SuperSU] egingell:
It was hidden in 2.22 (see changelog). When you're beta testing (which you are always doing when installing beta versions), it's generally wise to read the changelog.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] dragoncon:
I do read changelogs i just installed superSU after this version and just bought pro (mainly to support chainfire) and was wondering why the option was absent from my device, my net has been on/off today so i didn't have the time to spend reading older changelogs.
[SuperSU] egingell:
It was quite a long time ago. I merely stated it for the record.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] Pkt_Lnt:
A couple things you should review about XDA, with your 3 posts.

http://xdaforums.com/announcement.php?a=81

https://www.youtube.com/watch?v=JmvCpR45LKA&feature=youtu.be
[SuperSU] dragoncon:
I did do a search of the forums before posting thank you very much, found someone else asking similar question with no-one answering him adequately im sorry if i didn't literally scour the whole internet on an intermittent connection at the time but i wasn't sure when my connection was going to drop.

This isn't my first forum buddy, thanks for the attempt at helping anyway ;).
[SuperSU] aaaku:
Unable to access sd card as su

Thanks nice app. Will seriously consider upgrading to pro if this problem is fixed :)

I see a strange bug. Using terminal emulator, I am able to access /storage/sdcard0 and /storage/sdcard1 . ls on these directories work fine.

I do su (with supersu installed), ls on /storage/sdcard0 works but ls on /storage/sdcard1 shows nothing! I am not sure how a normal user has access to the SD card, but a super user cannot see anything. There is no permission error. The directory is just empty.

As soon as you exit the su shell, /storage/sdcard1 works fine again!

I tried a couple of previous supersu releases, in 2.02 neither sdcard1 nor sdcard0 work! 2.01 behaves the same as latest. Strange enough, the supersu reports the app version is 1.86.
[SuperSU] SyCoREAPER:
Not too happy. Paid for Pro and don't even get a response for support via email.
[SuperSU] egingell:
You don't pay for support - you pay for the extra features.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] Pkt_Lnt:
He has been at the MWC2015 in Barcelona, patience. These forums are good support, "what is the problem you are having so that we may be able to try to assist"..
[SuperSU] SamuriHL:
I think you mean to ask "what is the problem you are having so that we may be able to try to assist"... The way it's worded COULD be construed differently. LOL ;)