yashsingh1/xdaforums huggingface dataset:
[SuperSU] shaggyskunk:
If you're running any app that uses an overlay - SuperSU Tapjacking protection will render the SuperSU pop-up un-clickable.

So - Go to SuperSU settings - Uncheck Tapjacking - Reboot and try again

"Bye bye Sweet Canadian Moonshine"

Sent from my SM-N910W8 Running RRO Layered SlimLP
[SuperSU] DjDiabolik:
Installed by Apk... I run it and no binary prompt.... The binary still remain the 2.45?
[SuperSU] gianton:
I'm using Lux and this was bugging me long time. Thanks for the heads up.
[SuperSU] shaggyskunk:
Flash the zip

http://download.chainfire.eu/734/SuperSU/BETA-SuperSU-v2.47.zip

"Bye bye Sweet Canadian Moonshine"

Sent from my SM-N910W8 Running RRO Layered SlimLP
[SuperSU] Sc4ryB3ar:
Where did you find 2.8.6.1?
[SuperSU] baltics:
The 2.8.6.1. is only for the i9300.

I was wrong to suggest all versions of 2.8.6.0 have been pulled.
[SuperSU] Chainfire:
I got confirmation from the TWRP guys that the 2.8.6.0 build for Nexus5 is botched, though. Probably be fixed in the next version.
[SuperSU] starbucks2010:
[MENTION=631273]Chainfire[/MENTION]

Can you tell me please how can I trace an issue with SuperSU not prompting me to grant or deny su access?

I'm on Samsung LP 5.0.1 (SuperSU v2.47) and other ROM have indicated also to have the same issue.

I don't use any app with screen overlay (Lux or something else) and I disabled also Tapjack feature within SU but still don't get the prompt.

Thank you in advance.
[SuperSU] Pkt_Lnt:
Get him a logcat during SuperSU pop up requesting permission.
[SuperSU] Captain_Throwback:
[MENTION=631273]Chainfire[/MENTION]

I'm hoping you can help with something. For the M9, TWRP has been setup with system in read-only mode, as HTC has moved to block-based OTAs. Mounting it this way allows the user to make a fully stock backup of system so they can unroot and take the OTA at a later date. It also has the unfortunate side effect of preventing the SuperSU zip from installing, though. ROM zips appear to work okay, since they specifically mount system as ext4 in order to write to it, but SuperSU has issues installing because it seems to be looking for files on /system and can't find them because it isn't mounted.

Would you mind taking a look at the logs in this post and see if there's anything you can do? The current Beta version of TWRP for the M9 detects whether system has been previously mounted and either mounts ro for an untouched system block and rw for one that's already been written to. This removes the issue for people that have already rooted. However for people that just want to root, until TeamWin comes up with an alternate solution, is there a way to update the SuperSU zip so it'll mount system properly for installation?

Any assistance you can offer is greatly appreciated.
[SuperSU] Chainfire:
Have you tried v2.47 ?
[SuperSU] Captain_Throwback:
Just tried it now, and same result.

SuperSU appears to be looking in /etc/fstab for writable block devices, but since system is in recovery.fstab as emmc (read-only), it doesn't appear there. These are the contents of /etc/fstab in recovery:

/dev/block/mmcblk0p65 /cache ext4 rw
/dev/block/mmcblk0p67 /data ext4 rw
/dev/block/mmcblk0p36 /devlog ext4 rw
/dev/block/mmcblk1p1 /external_sd exfat rw
/usb_otg vfat rw
/dev/block/mmcblk1p2 /sd-ext ext4 rw

Is there anything that can be done? Recovery.log from 2.47 flash is attached.
[SuperSU] shaggyskunk:
In Developer Options - You do have root access set to Apps and ADB?

In SuperSU you have these settings?

"Bye bye Sweet Canadian Moonshine"

Sent from my SM-N910W8 Running RRO Layered SlimLP
[SuperSU] Chainfire:
And the contents of recovery.fstab ?

TWRP has been a real pain lately.
[SuperSU] Captain_Throwback:
Well the problem is HTC changing stuff on us to make security tighter . . . what we're doing in TWRP is a bit of a workaround. A more permanent solution will be devised once TeamWin has time, I'm sure. With the move to a new site and build server, I think there have just been some "growing pains."

Here are the contents of recovery.fstab:

# mount point fstype device	device2	flags
/misc	emmc	/dev/block/bootdevice/by-name/misc
/boot	emmc	/dev/block/bootdevice/by-name/boot
/cache	ext4	/dev/block/bootdevice/by-name/cache	flags=display="Cache"
/system	emmc	/dev/block/bootdevice/by-name/system	flags=display="System";backup=1
/data	ext4	/dev/block/bootdevice/by-name/userdata	length=-16384	flags=encryptable=/dev/block/bootdevice/by-name/extra
/devlog	ext4	/dev/block/bootdevice/by-name/devlog
/recovery	emmc	/dev/block/bootdevice/by-name/recovery	flags=display="Recovery"

# Removable storage
/external_sd	vfat	/dev/block/mmcblk1p1	/dev/block/mmcblk1	flags=display="Micro SDcard";storage;wipeingui;removable;andsec
/usb_otg	vfat	/dev/block/sda1	/dev/block/sda	flags=display="USB-OTG";storage;wipeingui;removable
/sd-ext	ext4	/dev/block/mmcblk1p2	flags=display="SD-Ext";wipeingui;removable
[SuperSU] Chainfire:
Let me know if this works, I'll make a 2.48 beta with this patch in the binary updater as well.
[SuperSU] starbucks2010:
[MENTION=631273]Chainfire[/MENTION]

Can you please have a look also on my logcat posted here?

Thank you.
[SuperSU] bombadier:
Still having that bootloop problem on my bacon, same zip works fine on my mako and grouper, any ideas ? I am running twrp 2.8.6.0 and CM11S, will stick to 2.46 but am out of ideas why the problem
[SuperSU] Captain_Throwback:
SUCCESS!!

Now it flashes successfully. Once you release the updated beta, I'll send all the M9 folks over here to use it. Thanks again for helping us workaround this annoying issue! :)
[SuperSU] Chainfire:
Have you tried an older version of TWRP ?
[SuperSU] Chainfire:
Posted.
[SuperSU] Frank Westlake:
2.47 OK through TWRP and

2.48 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

Frank
[SuperSU] DroidShift79:
Thanks Chainfire for new beta. Works with twrp on a m9
[SuperSU] bombadier:
2.48 flashed fine so just have to put that one down to a derp somehow
[SuperSU] DjDiabolik:
Also on 2.46 the binary still to 2.45...

Only [MENTION=631273]Chainfire[/MENTION] can confirm or not if on 2.48 it's present a updated binaries...

*edit*

Or if you are flashed this use a terminal emulator and post a result of command "su -v".

I have tryed and i obtain su binaries 2.45..
[SuperSU] Frank Westlake:
I have SuperSU 2.48 and su 2.45 also. I don't think you need to worry about them being different because it looks like SuperSU verifies 'su --version' on boot.

Frank
[SuperSU] DjDiabolik:
Yeah...I just only needed this confirmation ;) No worries :)
[SuperSU] Frank Westlake:
I shouldn't have said that, it was a weak guess. My assumption was that for SuperSU to know that binaries need to be updated it probably checks either on boot or on use, but I have never had the binary update problem so I don't really know what happens.

Frank
[SuperSU] DjDiabolik:
You are absolutely right :) I have update my supersu app from 2.46 to this latest 2.48 beta and, as fot the update from 2.45 to 2.46 of app, i not obtain the prompt for update the binaries. I thinks at this point the "su" binaries has not been updated and like 2.46 stable this two latest beta continue to use binaries of 2.45 :)

I have symply discovered this using "su -v" from "Terminal Emulator" and if you confirm you have my same result i thinks it's ok for all :)

P.S. i don't know if I have explained well.....
[SuperSU] rogconnect:
SuperSU 2.48 flashed with twrp-2.8.6.1_d855-bumped without issue on LG G3 D855

Sent from my LG G3 D855 CloudyG3 Lollipop
[SuperSU] Pure Drive GT:
For root on 5.1, is it recommend to flash the latest Beta, as it may have changes specifically for 5.1, or is it recommend to flash the stable version. In my case a Nexus 6 on stock rom.

Gesendet von meinem Nexus 9 mit Tapatalk
[SuperSU] IRONJIM4101:
2.48 working great on nexus 6

Войн Дух
[SuperSU] berniesteven:
Working well on att s5 active.

SM-G870A Peace
[SuperSU] CyberpodS2:
All good running 2.48 on Verizon s5 running ported Sprint 4.4.2 Alliance Rom.
[SuperSU] Ænimal:
When flashing 2.48 on secondary ROMs, SuperSU always installs on the primary. This happens on both of my devices (using multirom v32 + twrp 286)
[SuperSU] egingell:
There's probably no way to avoid that.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] Captain_Throwback:
[MENTION=3418703]Tasssadar[/MENTION] is aware of this already and is already working on a fix, I believe. But there's nothing [MENTION=631273]Chainfire[/MENTION] needs to do about it.
[SuperSU] Gustave17:
There is a new recovery for hammerhead in his thread. All is working well with SuperSU 2.48...

I think there will be a new release for everybody...
[SuperSU] marbulas:
Can't toggle of services and broadcast receivers with MyAndroidTools on Temasek's cm12.1 for hlte with SuperSU 2.48. but running init.d scripts works fine [emoji14]
[SuperSU] Jaglicic:
Zte Blade S6

How can we have root access on ZTE Blade S6 with locked bootloader and stock recovery, do we have to wait for someone to make custom recovery or there are some other methods?
[SuperSU] NZgeek:
The best place to check is in a thread or forum area dedicated to your device. This thread is here to help support the SuperSU app, not for general rooting advice.
[SuperSU] Prasad:
Thanks [MENTION=631273]Chainfire[/MENTION] ! Beta 2.48 works like a charm on the M9!
[SuperSU] Mikary31:
Here too!
[SuperSU] Cr33D OrB:
Thanks.
[SuperSU] mittorn:
[BUG] SuperSU breaks root after reboot on selinux android

Hello.

I have installed SuperSU on rooted tegra 3 device and updated su binary.

It worked until first reboot. After reboot suid flag on /system/xbin/su disappeared.

I have system with enabled SELinux in enforced mode, Android 4.2.2 and no sysfs support for selinux (no selinux in /sys/fs). There is no setenforce/getenforce binaries too.

How to reenable suid flag on su? I have no external access to filesystem!
[SuperSU] tbschommer:
Works great on my trusty old Xperia P :good:
[SuperSU] khanmein:
how to get the supersu icon? i flash via recovery or install .apk but the icon for supersu is not there. i can only find at setting > supersu
[SuperSU] Cr33D OrB:
For usually it comes and "fixes itself"

But however.. It u already have it integrated within Rom (and supersu not Working) then there should be no prob ? ;)
[SuperSU] khanmein:
i prefer my own supersu. integrated got material theme but after flashed my apk it become black. i missed the change theme setting at supersu.
[SuperSU] myabc:
please, i have installed supersu 2.48 integrated in a modded rom in galaxy s5 flashed with flashfire (knox 0x0) and for an app the developer sayd to me that with supersu 2.48 i don't need these command with terminal emulator:

supolicy --live "allow servicemanager init dir search" "allow servicemanager init file { open read getattr }" "allow servicemanager init process { getattr }"

BUT the developer, after some works, sayd me that even with 2.48 it needs even if chainfire told NOT need.

Are that command integrated in my version free or only in pro version or in none version yet?

please quote me in answer

thanks
[SuperSU] BR7fan:
I can not get it to uninstall on my ATT One M9. I need to get this off so I can get the latest update. Any ideas ?
[SuperSU] Lrs121:
If you read the thread for twrp carefully you'd know that the only way to take an update is to use fastboot to restore your system partition from a stock backup before anything was modified or else the update will always fail because of the new update method.
[SuperSU] BR7fan:
OK..I'm stupid :o

I'll look around and see if I can find a back up for my phone.

Thanks
[SuperSU] jerflash:
updated my nexus player to 5.1.1

had root on 5.1 but obviously lost it. tried the old way of gaining root but boot loop. ended up reflashing system.img then flashing new version of cm recovery and flashing the newest 2.48 beta. i have root back and all is working but i did not have the supersu actuall app installed which was strange. unpacked zip and installed from there and all is working as it should. Awesome work [MENTION=631273]Chainfire[/MENTION]
[SuperSU] d-pak:
Having an issue with "Unfortunately, Power has stopped"

The "History" under Settings --> Power shows a blank and clicking on History force closes power.

Setup is HTC M7 GSM, Stock ROM and Kernel at 5.0.2.

After Full Erase and Wipe using stock recovery, rooted with TWRP 2.8.6.0-m7

Zip installed SuperSU v2.46 via TWRP and also tried v2.48.

History is being collected but not displayed. Upon a reboot, history shows up including history prior to reboot. After going into SuperSU app and coming back out. Battery History is unavailable.

Unrooted using SuperSU app and restored stock recovery. Battery History works fine.

Maybe this is a coincidence with 5.0.2 as an issue, maybe not. Thought I would share.

The reason I rooted was to be able to use Titanium to freeze apps that cannot be disabled. Was getting great battery life, but now cannot see history, so the rooting purpose is defeated.
[SuperSU] zedlor:
I'm not sure if this is a known issue or not (haven't seen it mentioned anywhere) but I'm using this on my M9 with ARHD 5.0, and when the notification comes up to grant an apps permission, I'm unable to click anything on the popup - it's just dead. I'm not too sure what has triggered this to happen as when I first installed ARHD onto it it was fine, it just suddenly started doing it out of the blue.

Anyone know anything that could be causing it? I also have the ElementalX kernel installed if that makes any difference.
[SuperSU] USBhost:
Disable hijacking in supersu settings
[SuperSU] zedlor:
Oh, dammit. I probably should have seen that. I'll wait for another notification but that'll probably fix it, I would guess :P

Many thanks!
[SuperSU] shaggyskunk:
Yeah - You have to uncheck Tapjacking if you're running an app with Overlays - ie: Lux
[SuperSU] mirroalex:
Hi all,

This is first time I encounter a problem with supersu so sorry if my post is not in correct form.

Phone: i9505

Rom: phoenix 9.4 rom XXUGNF1 4.4.2

Kernel: ael kernel 6.3

PROBLEM: I am using wanam xposed's one of functions that let me kill current app by long pressing back key and after enabling it and long pressing back action "Android System [uid] 1000" request super user permission but i cant click any button like nothing works so permission denied, but this not happen in any other apps that request su permission just this one, I dont remember after which beta update but I guess it was after 2.06 or 2.08 that this issue arises, Is there any solution...?
[SuperSU] egingell:
You won't get any Xposed support in here.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] mirroalex:
It does not require su permission within xposed module it requires when for example I am in "chrome" and I want to kill that application by long pressing back key... so in this case again I dont have any option?

Ok lets forget about xposed I have application call X, it require android system uid 1000 su permission why I cant click any button grant or deny?

Dont be complicated...
[SuperSU] Blac Caesar:
I'm pretty sure you need to shoot this over to the Xposed thread. I use Wanam as well, not for what you do.. but I've had no issues. Maybe check with the devs for the Wanam module?

---------- Post added at 12:59 PM ---------- Previous post was at 12:53 PM ----------

@Chainfire.. v2.11 working perfectly here.

Nexus 5: Paranoid Android 4.6 Beta2, Elemental-X v1.09, Xposed Framework w/Wanam Module
[SuperSU] mirroalex:
Thanks bro I will try to ask there... thanks for help
[SuperSU] Frank Westlake:
This was probably not SuperSU. Humidity is high here now and the back button is sometimes being activated by close proximity.

Frank
[SuperSU] HorstiG:
Hello, I have Problems with Stormbird Backup Pro (root) after Update SuperSU 2.11. Stormbird crashes. With SuperSU 2.10 no problems.

Galaxy S3, Liquid Smooth KK - LS-KK-v3.2-2014-09-24-i9300, Boeffla kernel Omni NG 2.4 Beta 6

Problem solved: I have the app removed from the right and re-allocated.

Works again. But the game I have to repeat every time, after reboot my Phone
[SuperSU] Alex_rac:
Xperia Z2 Problem

Hi

I m a Xperia Z2 owner and i ve got some problem using supersu since version 2.08 beta

I ve installed every version between 2.08 and 2.11 but i m unable to get root permission for my apps.... ( root explorer , lucky patcher and ndrutils )

Xperia Z2 4.4.2 KK plese fix the issue :(
[SuperSU] Mr_JMM:
Working without issues on:

Nexus 4 (Mako) latest Purity, Slim, PA and Cyanogen with all running Art.

Nexus 7 2012 (Grouper) with latest CarbonRom and Purity tested both Dalvik and Art.

Many thanks.
[SuperSU] JaCh0o:
Hello Mr Chainfire,

Can I ask for help with my issue? I know Oppo is not common brand, but still we are you dedicated users. I got issue which I descirbed over here:

http://xdaforums.com/showpost.php?p=55411684&postcount=6534

But no one helped me. Moreover it's intresting that not "original" SuperSU is working instead of genuine Pro version.
[SuperSU] mpgrimes:
Works great on my n5, trinity, raskat . Can't test on tablet as no recovery.
[SuperSU] kevinco1:
I've been running 2.08, 2.09, 2.10 and 2.11 with no issues.

If you experience binary errors after installing the APK, just reboot to recovery and flash the included zip. This goes for Safestrap, CWM, Philz, etc.

Oh and [MENTION=631273]Chainfire[/MENTION] you should look into Safestrap. It's becoming a popular recovery for the huge number of U.S. Verizon and AT&T users who have limited options being on locked bootloaders.
[SuperSU] Mariner_1712:
I hate to be that guy, but what is the procedure for installing the SuperSU Beta over an existing one? I successfully flashed over to 2.11,but after the next reboot it goes back to 2.02!
[SuperSU] Megaflop666:
Just flash in recovery.
[SuperSU] BookCase:
This won't flash for me on KFHD 7 in recovery but, flashed fine on all other devices.
[SuperSU] Fivesack622:
So I decided to try something hoping it would help. Last night I tried every combination of disabling stuff and rebooting that I could think of to see if anything made a difference. Probably close to 30 reboots all together... Sometimes it would ask to update the binary and sometimes it wouldn't. There was no rhyme or reason that I could find.

So, today I decided to disable every module in xposed and then uninstalled xposed. I then use the option in SuperSU to completely unroot and rebooted. I then rerooted with Towelroot again and immediately installed beta 2.11. It asked to update the binary and succeeded! So from this point on, I kept rebooting go see if it asked for a binary update and copied the "SuperSU Installer" logcat each time. On the 4th reboot, it asked for a binary update, which failed. I am posting the logcats for the four reboots in case they can help you. There are a few other things mixed in the logcats I couldn't get filtered out so sorry about that. It's the best I could do and I hope this helps you. They should be attached in the order of the four reboots. As for me, I am about to help this phone with a sledgehammer....
[SuperSU] Fivesack622:
And just for the hell of it, here is the installer logcat from the failed binary update. I also want to add that I have no problems whatsoever with beta 2.11 on my Nexus 7 2013 running CM11, for what it's worth. With that though, I am flashing the zip from recovery, which I cannot do on my Samsung Galaxy S3 Mini because of the locked bootloader.
[SuperSU] Paschfire:
Nexus 5 rom Pa 4.6Beta2 Franco kernel r63 w/supersu v2.11 seems to be working fine. question: im coming from v2.02 and after installing v2.11 today I tried to change my boot animation via system/media instead of replacing the zip in data/local but noticed any boot animation zip I place in system/media(after changeing perm to 644) no longer plays at boot only data/local plays, is this anything to do with supersu v2.11 as it has been months since I've changed the animation but work fine before?
[SuperSU] mirroalex:
Hi,

After v2.09 beta in v2.10 and v2.11 i have following issue:

I can't press any button, Grant/Deny or any at all, just timer works and reach to zero when >>Android System [UID] 1000<< request su permission is there any workaround on this problem?:eek::eek:
[SuperSU] Pkt_Lnt:
Disabling an essential security feature implemented by Chainfire is not the best way to deal with this, find the real problem, usually a screen dimmer/control overlay.

---------- Post added at 11:11 AM ---------- Previous post was at 11:10 AM ----------

Or whitelist SuperSU in Lux, the best solution to keep the tapjacking security feature. :good:
[SuperSU] zedlor:
A-ha, so that's when it must have started, when I installed Lux!

I've added SuperSU to the Lux sleep option and now it's working fine with Tapjacking enabled - thanks both for the help :)
[SuperSU] CyberpodS2:
Something is using an overlay if I had to guess. momentarily turn off tapjacking protection under SuperSU settings and see if it fixes it. If so then you gotta find the offending app as you don't want to run like that normally.
[SuperSU] lolypop000:
Hello

I like to ask something.

Is it possible to somehow in supersu.apk change name of system/xbin/su to something else like system/xbin/chain so that after install of supersu apk will be like this system/xbin/chain?

A lot of new app still search for system/xbin/su file but this new app have encrypted path so you can't disable root check.

If somehow is possible to change supersu apk ti create file in system/xbin/ with different name that su, we can run app that check if device is rooted.
[SuperSU] Pkt_Lnt:
Then all the root apps that call su will not work. You will have to get hundreds of devs to change their root apps. And android will have to be redone too..........
[SuperSU] lolypop000:
Try this:

- if full uninstall supersu, some app that check root still don't work

- if change su to something other this app start to work

- all app for hide root don't work still root detected from some app

Maybe if we can have option in supersu settings to rename su to something others and then change it back.

I read a lot thread but found out that nobody know what encryption use new apps to see if device is rooted or not.

In new app if you decrypt it you find /su, /su backup, busybox, but if you change this name to something others, still don't work, but in app from 2014 this trick work.

Don't know anymore how to disable root check ( for su ) in new app :(
[SuperSU] Chainfire:
v2.49 BETA posted. Fixes some SELinux stuff on newer 5.x firmwares.
[SuperSU] HorstiG:
Google Greetings :D

In half a year we are on the same level as an iPhone

Sorry, works great on Galaxy S5 G900F with CM12.1 Fusion ROM, Boeffla Kernel CM12.1, BussyBox Stericson 1.23.1
[SuperSU] alkanbw:
Best update ever !!!

Now on Samsung Galaxy S5 with latest ROMS BOD3 and BOC7 - all apks work ike charm.

There was problem with VmLite VNC Server - now all is solved.
[SuperSU] fadac:
Test. 1. 2.

jking...

Seems to be working fine on OnePlus One w/ Temasek's UNOFFICIAL 5.1/CM12.1
[SuperSU] misterpingle:
I can overwrite 2.49 over my 2.46 ?

MrPingle
[SuperSU] rogconnect:
Best ever update so far. It make my G3 like G4 xD

Sent from LG G3 D855 CloudyG3 Lollipop with L Speed v2.0
[SuperSU] koko115:
V2.49 not working with S6 Edge. Bootlop :(
[SuperSU] Christendom...:
v2.49 works perfectly on my Oppo Find 7a driving OmniROM 5.1 with TRWP 2.8.6.0

Thank you Chainfire ?%
[SuperSU] RandomPooka:
It turned my G3 into an Aston Martin...
[SuperSU] Cr33D OrB:
Yeah CF thanks for update is fine !! :)
[SuperSU] Rinoceros:
Beta 2.49 works on both HTC devices mentioned below.

Thanks :)
[SuperSU] Ahmed_eldewy:
sony zr (c5502)

I grante some program with super su but the programs failed to get root permission. my mobile sony zr(c5502)
[SuperSU] dr.ketan:
Perfectly fixed preroot issue (Unable to use default access Prompt) on Note4 Lollipop ROMs with Beta SuperSU 2.49. Now we can use prompt option without SELinux permissive kernel.

Thank you [MENTION=631273]Chainfire[/MENTION].
[SuperSU] Smoosh1:
v2.49 works perfectly on my Nexus 5 so far.

I'm currently running Lollipop 5.1 build LMY47D.

Question

: Is there a way to easily upgrade to LMY47i without losing root?