yashsingh1/xdaforums huggingface dataset:
[SuperSU] Wyneg:
Re-flash SuperSU 2.67 beta in recovery ;)
[SuperSU] Dr0idgroove:
Not much of a solution is it?

I already tried it and after re-flashing it, the behaviour is identical. As soon as I disable SuperSU via the app's settings menu any attempt to re-enable it results in an installation error.
[SuperSU] 089man:
Is this version working on cm13, aicp rom?

I9100 Tapatalk, AICP M
[SuperSU] Marília de Oliveira:
It works with lollipop?
[SuperSU] teddy0209:
Yes it does... Do backup just in case.?
[SuperSU] Marília de Oliveira:
Okay, thanks :o
[SuperSU] drewski_1:
not ideal, yes, but it is the current solution / workaround.
[SuperSU] 089man:
Have Flash the 2.67 in my I9100 with AICP cm13 rom. All was fine and no errors during flash. Reboot all fine.

But where I found the supersu app in my rom that I can used it?

I9100 Tapatalk, AICP M
[SuperSU] 1966er:
Install it from Playstore

Gesendet mit Tapatalk
[SuperSU] robertogl:
If he has my same problem, he can't. SuperSu apk is on the device but for some reason it doesn't show itself. Installing from play store give an error...

Inviato dal mio GT-I9505 utilizzando Tapatalk
[SuperSU] NZgeek:
The way I read it was that CM's root doesn't allow the SELinux policy to be modified, which means that it's not a full root. In other words, it gives you more rights than normal, but is still limited by the context it's running under.
[SuperSU] wartomato:
Yes.

---------- Post added at 10:26 AM ---------- Previous post was at 10:24 AM ----------

So just use selinuxmodechanger app from xda and tadaaa.
[SuperSU] 089man:
Thanks, flashing was ok boot was ok, but where I found the supersu app on my device?

The playstore apk is verry verry old 2.46 from 2014 and is not for cm13 I think?

Where I found a 2.67 apk that I can used supersu?

Thanks

I9100 Tapatalk, AICP M
[SuperSU] mielletseed:
For what? Setting SELinux to permissive? Than you didn't understand completely chainfire's approach. When you set SELinux to be permissive your device is more vulnerable. That's why SuperSU only modifies some of the policies that are needed to gain full root access but doesn't turn them off completely ...
[SuperSU] tcntad:
Using v2.67 Beta is working almost fine.

I just dont seem to be able to move some apps to /system/app & priv-app..
[SuperSU] Manuel15:
If you flashed in system-less mode, try this. Go in the system settings, apps and check if there is SuperSU app. If it's there uninstall it. Then go in the supersu.zip file, in the common folder. There should be SuperSU.apk, install it and see what happens
[SuperSU] robertogl:
Doesn't work for me. I've the apk in data/eu.chainfire, I've remove that but I get an error if I try to install the apk extracted from the zip.

Inviato dal mio GT-I9505 utilizzando Tapatalk
[SuperSU] egingell:
Copy it to where you found the old one and reboot.

Sent from: SGS5 - LP 5.1.1 / SGS4 - LP 5.0.1
[SuperSU] Gandalforce:
I always just factory reset after full unroot / backup data. Then reroot
[SuperSU] MarkAtHome:
Out of curiosity, do you have SuperSU set to something other than "prompt"? The reason I ask is that at some point in time, I believe that this happened to me.

If you have SuperSU set to "prompt", the act of updating the binary should prompt for permission, to which your response would be to grant. If not set to "prompt", you would not be asked for permission, and never know what happened.
[SuperSU] wartomato:
The apk is in the ZIP. In common folder. (Superuser.apk)

---------- Post added at 00:20 ---------- Previous post was at 00:17 ----------

Man, i understood bis approach, but you didn't Seen to understand my post.

Quick approach by me to solve a prob.

"Vulnerable"? A rooted device? Man, come to senses...
[SuperSU] 089man:
Hi, have found but install and than flash the zip from recovery again. Now supersu found in settings from the rom.

But now I need binary, where I found?

With normal it's not updated and over twrp I have not this file. Where can I download this binary?

I9100 Tapatalk, AICP M
[SuperSU] wartomato:
You need to flash the ZIP with every Rom update. The supersu APP will only be there in settings. That's normal.
[SuperSU] 089man:
Yes, I have do it, have Flash the zip, but I can't use supersu because he ned a new binary file. If i start this option than the dialog comes that not avaliable.

I need a binary file, where I found this?

I9100 Tapatalk, AICP M
[SuperSU] Manuel15:
Binary files are inside the zip file itself. So flashing it will flash SuperSU AND the binary files.
[SuperSU] 089man:
Have Flash again the zip. Than before reboot to system comes a info that su must flash, I do it and I think the binary was flashed, than reboot, but now I lost boot complete and if I start su app than error comes that not su can't start and can't repair by it self...

What version su is working with cm13, what beta before and where I found older zip?

I9100 Tapatalk, AICP M
[SuperSU] Manuel15:
You accepted the recovery request to flash SuperSU?? That is the problem! When you install SuperSU in system-less mode. The recovery will tell you the system is not rooted. Do NOT accept the recovery request to root the phone! Retry flashing SuperSU, then when the flash is finished reboot into the system, and if the recovery asks to install root, do NOT do it, deny and reboot.
[SuperSU] Ch3vr0n:
That flash question before boot is your problem. The instructions clearly state to NOT FLASH SU if twrp asks you if you're using twrp below 3.0.0. If you do (like u did) you break su and risk a boot loop. There are specific warnings to that end DURING the superSU flashing process that you (chose to) ignore.

Reflash your cm system image through fastboot and your boot image

Flash 2.67 beta in twrp.

If twrp asks you to flash su because it appears to be unrooted: DO NOT DO IT or you will break superSU.

Just reboot

Update your twrp to 3.0.0

Verstuurd vanaf mijn Nexus 7 met Tapatalk
[SuperSU] Thorge01:
DO NOT INSTALL ON MARSHMALLOW, even if you`re on S-off, latest RUU_HIMA_UL_M60_SENSE70_ATT_MR_NA_Gen_Unlock_3.35.617.12 and TWRP 3.0.0 --> SuperSU v2.67 is in Beta and even if you flash via TWRP 3.0.0 you`ll end up with boot loop. F***, i`m pissed - hope UPDATE-SuperSU-v2.65-20151226141550 will bring my device back to normal

btw, my device HTC one M9, Rom:ViperOneM9_4.2.1

Update:

If you also experienced a bootloop after flashing the SuperSU v2.67 beta do the following: Put SuperSU-v2.65 (stable) on your ext. sd, go into recovery and flash with TWRP 3.0.0. DO NOT INSTALL SU if TWRP ask`s you right after flashing SuperSU-v2.65 (stable) - ignore that request - and just reboot. Bootloop is history and system is on a stable state ;o)

Problem solved!
[SuperSU] 089man:
Have Flash my rom again and used the internal superuser at this time. Have removed from system all supersu files too.

I9100 Tapatalk, AICP M
[SuperSU] Ch3vr0n:
That's why the good lords of Android have created a wonderful technology called a 'nandroid backup' :P restore it with twrp and everything will be fine.

Verstuurd vanaf mijn Nexus 7 met Tapatalk
[SuperSU] 089man:
Trust me, that I have do before. But I have Flash the rom with dirty flash, it's was faster. For me was only important that the su is gone....

I9100 Tapatalk, AICP M
[SuperSU] wartomato:
Yep, all done right.

Remember (although it is off-topic) that AICP has the built-in Superuser from CM, the root option in settings and an option to turn on permissive kernel mode - if needed.

I did the same after SU in CM builds were stable.

AICP for your device is still under heavy development... So further posts should go in the AICP thread.
[SuperSU] doogfar:
I use the commands

su
setenforce 0

And then went to Secure Settings and it activated.
[SuperSU] USBhost:
[MENTION=631273]Chainfire[/MENTION]

i dont think this should be happing

did daemonsu go rogue

Nexus 9

2.19:SUPERSU

kernel FIRE-ICE

ROM Lollipopalooza LRX21T :: it also happened to stock too

root@flounder:/ # top

User 10%, System 41%, IOW 0%, IRQ 0%
User 63 + Nice 0 + Sys 254 + Idle 290 + IOW 0 + IRQ 0 + SIRQ 0 = 607

PID PR CPU% S #THR VSS RSS PCY UID Name
4566 1 50% S 4 14272K 788K root daemonsu:sugote:10080:4557
8295 0 0% R 1 4100K 1356K root top
8028 0 0% S 22 2126964K 92408K bg u0_a88 flar2.elementalxkernel
483 0 0% S 81 2227316K 133836K fg system system_server
154 0 0% S 13 83220K 30104K fg system /system/bin/surfaceflinger
92 0 0% S 1 0K 0K root kworker/0:3
9 0 0% S 1 0K 0K root rcu_bh
10 0 0% S 1 0K 0K root rcu_sched
11 0 0% S 1 0K 0K root watchdog/0
12 1 0% S 1 0K 0K root watchdog/1
13 1 0% S 1 0K 0K root migration/1
14 1 0% S 1 0K 0K root ksoftirqd/1
16 1 0% S 1 0K 0K root kworker/1:0H
17 1 0% S 1 0K 0K root khelper
[SuperSU] clamitas:
I did

$ su
# setenforce 0
# pm grant com.intangibleobject.securesettings.plugin android.permission.WRITE_SECURE_SETTINGS
# pm grant com.intangibleobject.securesettings.plugin android.permission.CHANGE_CONFIGURATION
# setenforce 1

Maybe I didn't need this extra lines, but it worked anyway ☺
[SuperSU] varazir:
Thanks, it worked I should change back setenforce to 1 after I have have granted secure settings access?
[SuperSU] doogfar:
I didn't as i rebooted, I'm sure that resets it. Although i wonder what command i need to issue to see if its enforced?
[SuperSU] Chainfire:
When this is happening, please also provide the output of "ps", so we can trace what caused it. There's probably a bug in sugote somewhere, but I need to be able to reproduce in order to fix.

Don't use setenforce ...

su --context u:r:system_app:s0 -c pm grant ...

... is the correct command
[SuperSU] varazir:
su --context u:r:system_app:s0 -c pm

After that I tried to disable and enable secure settings and it failed.

Nvm pm gives me a error.
[SuperSU] Kung-Fu-Tse:
Android-System [UID] not work :(

Hello [MENTION=631273]Chainfire[/MENTION] :highfive:

Big thx for your great app

I have a problem with your app.

I can not give access to this:

I can NOT touch... :( (only for this access -see pic-, for apps will work), only what will work is I goes into "settings" - "Standard access" from "input" to "allow" :(

An ideas what I can do?

I need the access to kill some app (sometimes I need this).

I use:

App: SuperSU PRO

Phone: Samsung Galaxy Note 3

OS: Android v4.4.2, Stock Samsung

kernel: stock or leankernel

Sorry for my bad english
[SuperSU] relevant_placeholder:
Lux?
[SuperSU] Kung-Fu-Tse:
WHAT?
[SuperSU] relevant_placeholder:
[MENTION=631273]Chainfire[/MENTION], please consider donate IAP in pro so people like me can give something extra. Google Play codes are the thing now and people who don't want to link credit card to store use it. Thank You for all of your hard work!
[SuperSU] Frank Westlake:
You need to replace the "..." in Chainfire's message with the remainder of the command line as you specified earlier.

Frank
[SuperSU] varazir:
Ahh it wasn't my command. I see it now
[SuperSU] relevant_placeholder:
:) as much as I could figure out from what you wrote is that you're not able to click on allow/deny buttons so I asked if you're using lux.

Anyway, if you're experiencing problems clicking on buttons on SuperSU prompts then consider disabling click jacking protection in SuperSU as long as you know what app is the problematic one.
[SuperSU] Danzic59:
Working great on mine running 1111 nightly
[SuperSU] Kung-Fu-Tse:
thx, but I dont know again what is "lux" ;) is this a app on Play Store or what? I use my dicionary and can not find lux.

What I find is "Lux" is also "lux" into germany for the light :D

I have installed SuperSU completly new and fresh but also the same problem (v2.16 from Play Store).
[SuperSU] User_99:
Try to disable tapjacking in SuperSU
[SuperSU] JulGer01:
Same effect with any screenfilter app. To dimm lights or change lightcolor.

Gesendet von meinem GT-N7000 mit Tapatalk
[SuperSU] ryanjf:
SM-G900T, installed via apk, updated using normal process, no issues to report so far.
[SuperSU] fmc000:
Confused...

I run an Omni-based ROM (6.0.1) on my device with SuperSU Pro 2.67 systemless without issues. This morning I installed a new kernel without reflashing the 2.67 zip and as soon as I rebooted I knew I was in trouble.

But I was wrong: everything worked without issues even if the zipfile didn't do its magic on the newly installed boot image. Why? Maybe because the ROM I use runs SeLinux in permissive mode?

Thanks in advance.
[SuperSU] bunklung:
I am having the same issue with 2.67 on 29Q/N6/TWRP3.0.0-0. This does not happen on 2.66. I did a full unroot and reflashed 2.67 to test this.

What I observed is that when you attempt to re-enable SU via supersu.apk the daemonsu gets copied (I have no idea where from) to 2.66, but su never appears. I can tell that it's the older binary due to the file size (153kb 2.66 vs 75kb 2.67) and the fact I can execute -v switch and daemonsu reports a regressed version (2.66:SUPERSU).

I tried to be a smart ass and manually copy a good copy of su AND daemonsu back into /su/bin and supersu.apk still reports the binary needs and update. I can regain root by this manual method.

Any reason why there appears to be a regression into 2.66? Is 2.67 pointing to the old 2.66 binary for some reason?

Thanks.

*update* It does seem like SU will be re-enabled and functional in some cases, but it still gives a update message. In addition to SU/daemonsu, supolicy_wrapped and sukernel seem to get modified/replaced.
[SuperSU] savvy1968:
maybe v2.66+ is for mm?
[SuperSU] tinko975:
Back to older version [emoji4]
[SuperSU] DreadN:
Have a stock Nexus 5 with 6.01 MMB29Q,

encrypted

and with TWRP 3.0.0.0, tried flashing modified boot + SuperSU 2.67 but no luck. SuperSu when phone is rebooted goes in loop with "can't update executable" error.

Followed this last post in this thread, donwloaded superSU 2.65

- Flashed stock /boot

- Flashed stock /system

- Flashed modded boot.img

Ran TWRP 3.0, installed 2.65 via ZIP.

Q: How can I understand if I am in systemless root if in EU and do not have android pay?
[SuperSU] Ch3vr0n:
- 3 is your problem. It's been several beta's now you do NOT flash a modified boot. The su beta modifies the STOCK one during su installation.

About Android pay, wrong topic.

Verstuurd vanaf mijn Nexus 7 met Tapatalk
[SuperSU] Manuel15:
You can check if you're in system-less root checking the "install SuperSU in /system" option. If you're in system-less mode it will say "not available for system-less root"
[SuperSU] DreadN:
No, sorry, /system was tainted, thanks manuel for the suggestion.

So i did clean procedure.

Redid:

- Flashed stock /boot (6.01 last)

- Flashed stock /system (6.01 last)

- Flashed modded boot.img

Flashed BETA-SuperSU-v2.65-20151226141550.zip via TWRP 3.0.0.0

(put encryption password, mounted dm-0)

Install from ZIP seems all ok, but complaints that cannot restore stock boot.img...

Reboot system: no SuperSu icon present.

Installed SuperSu via .APK, all ok.

Verified "install SuperSU in /system" and says no (currently) available for system-less root mode.

Seems ok.
[SuperSU] Manuel15:
OK, but afaik there wasn't need for the modded boot.img . SuperSU v2.65 should mod the stock boot.img
[SuperSU] Ch3vr0n:
I'll repeat. Do NOT flash a modified boot. The zip installer modifies the STOCK boot and a modified or isn't needed and has been known to break things (in Android) if the wrong boot image is used.

Verstuurd vanaf mijn Nexus 7 met Tapatalk
[SuperSU] :
I'm having motorola motoG 2014 running official marshmallow. I was trying to flash stable version of supersu 2.65.zip over stock boot.img but my device went to bootloop. Root got successful only when I flashed supersu over moded boot.img.

Seems lots of ambiguity here for some supersu works with stock boot, for some it only works with moded boot.img.
[SuperSU] Ch3vr0n:
Nothing ambiguous about it, he's using a nexus line device you're not.

Verstuurd vanaf mijn Nexus 7 met Tapatalk
[SuperSU] :
I have seen root tutorials of many others Moto devices like motox pure, style, play etc...all uses supersu without moded boot.img.
[SuperSU] Chillerhippie:
Just a little feedback for your latest beta...

Phone model:

SAMSUNG NOTE 4

N910F

OS: v5.1.1

Status before install: clean / stock (unmodified system)

After Install:

At boot, I get a yellow error message: Set bit warranty: kernel

Google play services have also report an unknown error and I can't sync to my Gmail although all other services work.

Some apps report that additional files (busybox) need to be installed even though they have been installed, the phone now says its status is "custom" and android pay no longer works.
[SuperSU] fmc000:
Anyone?
[SuperSU] folusmile:
help

Help pls I flash su 2.67 on note4 lollipop 5.1 everything went okay ..but titanium can not backup apps saying "insufficient storage" pls any help will b appreciated.

What I did was I flashed su 2.67 over 2.56. Did I do the right thing?

Thanks
[SuperSU] egingell:
Except for the Gmail sync, all of those things are expected.

Remove and readd Google account(s).

Some old apps have a hard time finding systemless busybox because of how it's looked for (hard-coded path).

Google has decided that they need to take our security into their own hands and disable Android Pay when it detects root. It's none of their business, but I digress.

The phone is no longer factory stock, so your warrantee is void.

And of course it's custom. What did you expect?

Sent from: SGS5 - LP 5.1.1 / SGS4 - LP 5.0.1
[SuperSU] Ch3vr0n:
No you didn't, instructions clearly state that if you're coming from 2.56 you must flash stock system first. As far as the storage issue, that's a TB issue not a superSU one

Verstuurd vanaf mijn Nexus 5 met Tapatalk
[SuperSU] alex00006:
Hi guys

I have note5 with android 5.1.1 ..

I'm use su2.7 for root

My phone root successful

Tnx chinfire

But

After root no deep asleep

Never deep aleep

Plz guide for fix problem

Tnx
[SuperSU] OMJ:
I know this has been posted but I have not seen any logs posted...

flashing BETA-SuperSU-v2.67-20160121175247.zip on HTC M9 causes bootloop...v2.65 works fine..

[MENTION=631273]Chainfire[/MENTION] here is a log, pls let me know if u need anything else, I also have a backup of the boot after flashing v2.67...

https://www.dropbox.com/s/fqq701y3tfx571y/HTC_M9_v2.67_last_log.zip?dl=0
[SuperSU] Snowby123:
If you have root but do not have deep sleep install the app betterbatterystats to address the issue. It is likely not a problem with supersu but rather an issue with one of the root apps you are using.
[SuperSU] DreadN:
...that's why TWRP shell said that cannot patch boot!

So i've followed an old thread... thanks for the 2nd time...
[SuperSU] alex00006:
I'm for test issue deep sleep after root i

Use application cpu spy and no seen deep sleep

and

I did not sleep after root with su 2.67
[SuperSU] dimebolt:
Hi all,

I try to flash stable 2.65 supersu over my 2.49 on my international N920I note 5 (5.1.1) through twrp 3.0.0. After flashing my supersu icon is gone and root check said my phone is not rooted. Can anyone advice me what i did wrong?
[SuperSU] ackzsel:
logcat not working for super user

Hi guys,

I flashed SuperSU v2.67 on my i9300 running CM13 and all seems to work except: logcat will exit immediately without any output when executed as super user. It works fine as normal user.

Do you guys have any information about this issue? I tried to search this thread about it but couldn't find anything.

Thanks!
[SuperSU] :
Can't root LG Watch Urbane (with Marshmallow).

Issue: Can't mount /system in recovery after the OS update.

Result: Flash all ZIP files fails.
[SuperSU] mpgrimes:
By chance, are you running latest fastboot/adb version from Google development kit?
[SuperSU] jbfountain:
Are you on LP or MM?

Using XDA to unleash the power of Android on my S6 Edge Plus & HTC One M9
[SuperSU] OMJ:
Marshmallow
[SuperSU] NPOA556:
Because 2.49 was traditional root and 2.65 is systemless, you need to flash stock system and boot images before flashing SuperSU.

http://xdaforums.com/showpost.php?p=64161125&postcount=3
[SuperSU] Alxoom33:
Is it possible to Systemlessly Root a smatwatch? How?
[SuperSU] :
Finally I've rooted.

The main problem was TWRP doesn't support aquafs

But finally a friend had compiled a upgrade.

Of course, superuser.apk doesn't work and needs to be

Deleted, but su command works fine
[SuperSU] 3lMghraby:
can I modify my system after installing systemless root on galaxy note5 marshmallow ?

as stock kernel doesn't allow system modifications ?
[SuperSU] namfat:
Dear [MENTION=631273]Chainfire[/MENTION],

Please release next version to support android M on N920C.

We tried to root N920C using your SuperSU V2.67 but it says none of permission.

[IMG="http://uploads.tapatalk-cdn.com/20160219/6add59922d03bee906619e7fd0620e14.jpg"]http://uploads.tapatalk-cdn.com/20160219/6add59922d03bee906619e7fd0620e14.jpg[/IMG]

Thanks master,
[SuperSU] prototovsky:
Then have you barely flashed main supersu beta zip with a modified twrp image?

Where can we found this image? It would be amazing if you can share this method :)
[SuperSU] :
http://xdaforums.com/showpost.php?p=65381634&postcount=12
[SuperSU] tet-bundy:
U need rooted device for SuperSU to work. The app just manages superuser access

Gesendet von meinem SM-G800F mit Tapatalk
[SuperSU] TonySuperPony:
The supersu zip is the thing that roots your phone...
[SuperSU] Shark5060:
no. That would be either the root implemented in your custom rom or cf.autoroot for example. NOT supersu
[SuperSU] TonySuperPony:
Then why does the zip place su binaries on your phone...
[SuperSU] mielletseed:
You are wrong. The zip file roots your device. Period. You don't need to be rooted before.
[SuperSU] fmc000:
As other have said before me, you're absolutely wrong. Moreover, even if you clearly don't have the slightest idea what you're talking about you waste other people's time answering.

Just to be clear, the zipfile is what you have to flash in recovery mode to gain root access on your phone. Period.
[SuperSU] Wyneg:
I used cf root after flash recovery and supersu 2.67... What a mess! Well, I know what to do in future ;)
[SuperSU] tet-bundy:
Cause the app needs those to work. But to place these, you need root access.

More precisely, there is a user named root which is the "superuser"/admin of a linux system. On stock android, this account is present but usually locked , so u are not able to su (substitute user identity) to this user. To root a device means to give access to this account.

When you "su to this account" you gain all privileges/rights of root and are allowed to write to directories other than the normal useres home directory, often named/linked to "/storage/emulated/0".

I'm actually not an it expert or sth so correct me someone if I'm wrong.

Gesendet von meinem SM-G800F mit Tapatalk
[SuperSU] fmc000:
You're neither completely correct nor completely wrong. Let's try:

Flashing the zipfile in recovery mode enables root on your phone;

the "su" binary is placed under /system or, in the systemless installations, under /su;

any root-enabled app then tries to execute this "su" binary;

the superuser apk manages if, when and how the requesting apps can get the root privileges (and many other things).

The root privileges in an Android system are usually needed to write under /system, to access the /data partition using a file manager, to tweak the kernel, to freeze some system apps, to backup the apps data and so on.

BTW, "su" means "switch user" and it's a standard Unix command used to assume the privileges of any other non-locked user (not necessarily root), provided you know the password.
[SuperSU] RandomPooka:
Correct. You can su to any user account from any other, if you have their credentials and the account is set to allow it. In the case of Android, there aren't usually any other accounts you'd need to switch to apart from the root account.
[SuperSU] Ozgurce:
I have tried that too. I flashed old sboot and after that flash the twrp. Booted twrp installed 2.67 zip go bavk to bootloader and flash the new sboot and rebooted.

Phone booted and few seconds later atartong boot rebooted. And booted again fine. But binaries not installed . Not /su nor /xbin.

I think samsung changed something in the partition.

I dont have logs right now but i will be upload the recovery logs after trying again.