yashsingh1/xdaforums huggingface dataset:
[SuperSU] FernBch:
Whatever it is I have concluded That I can't use SuperSU on any CM12 nightly after 2/12. It seems if I do root access is lost (SuperSU will report no root access). I can use SuperSU on CM12 - 2/12 or earlier. This issue is present when using 2.45 & 2.46, I have not attempted using earlier versions.
[SuperSU] h_onger:
Awesome update ! thx:good:
[SuperSU] Chainfire:
Can you get me a download link for the exact nightly you are running so I can test?
[SuperSU] Gandicela:
No issues here
[SuperSU] FernBch:
I am using the official CM12 for the Verizon GS4 (I-545), my recovery is CWM 6.0.5.0 and I get this using SuperSU 2.45 & 2.46. When I flashed the 2/15 nightly after it boots SuperSU and Root Checker report no root, RomManager will not reboot into recovery from it's menu command, and BBS root features no longer function. I am not the only one who has noticed this, there are a couple posts about it the the official CM12 for VZW thread.

CM12 link:

http://download.cyanogenmod.org/get/jenkins/100762/cm-12-20150215-NIGHTLY-jfltevzw.zip
[SuperSU] DjDiabolik:
I have installed the SUPERSU 2.46 from Superuser.apk inside common folder of zip file......... ok but from terminal emulator at "SU -V" the output it's again "2.45: SUPERSU"

Only the GUI it's been updated or i have some trouble whit my OPO ?
[SuperSU] NeoLogY:
I think it you suppose to see these in SuperSU 'About'.

i8190n SlimKat9.0(Android-Andi)

Fred'sKernel1.3(Fred6681) SuperSU2.46(ChainFire)
[SuperSU] DjDiabolik:
It's same me........ but try to open a Emulator Terminal and read the output of command "su -v" i obtain 2.45:SUPERSU and i have flashed the supersu 2.46 zip... very strange or it's normal ?
[SuperSU] marknoll:
Mine does the same

---------- Post added at 06:34 PM ---------- Previous post was at 06:33 PM ----------
[SuperSU] Pkt_Lnt:
That is the su binary, not the SuperSU apk. The binary does not always update, but the install scripts in the program do.
[SuperSU] DjDiabolik:
Great info......... at this point i thinks the ROOT it's ok on my OPO :)

Here come to back to Boeffla tweak thread because i have a little trouble whit config app and the ROOT ACCESS..... very strange.
[SuperSU] NeoLogY:
Thanks too. Love this community. More to learn n live in here. :D

I don't know if this will help, but I recognize there's Fix Permission func in TWRP recovery, can this do sumthin bout Root permission? Or I got it all wrong?:confused:
[SuperSU] DjDiabolik:
I don't know but i tryed to investigate on it.......
[SuperSU] Mendoka:
Men! I have an issue with my S5 g900m stock rom 5.0. When I try to update the SuperSu binary, it just keeps to load and nothing happens. I try to reboot the phone and it stays at the boot screen with no other action. I'm trying everything to make it works but nothing helped until now.

Is ther anybody with the same problem? :crying:
[SuperSU] marknoll:
Try posting in galaxy s5 thread. Better help there.
[SuperSU] Mendoka:
Oh, sorry!

I'll try. Thanks!
[SuperSU] ettore88:
Hi guys!!!My question to you.I would like to purchase the PRO version.I install the free version from recovery...What would be the procedure to install the PRO vs from recovery?THX in advance!!!:):good:
[SuperSU] fubo73:
No procedure. Pro is a separate APK, so it's not important if you install SuperSU from play store or from recovery.
[SuperSU] Steve Geemaggio:
Hello,

Apologies if this was asked already but I couldn't find anyone else with this issue after much searching.

I'm currently using SuperSU Pro (CM) V2.40 on my Galaxy S4 I9505 running current CM nightly (5.0.2)

Every time I update to the next nightly, via latest TWRP, as expected, I lose root. So I went into SuperSU to enable survival mode, but there is no option for survival mode.

Anyone know why? Is it something to do with Lollipop? I'm definitely running the Pro version, so the option should be there.

Thanks in advance for any help.

Keep up the great work. This app is amazing. Well worth the money!

Steve

*EDIT*

Hello again,

Just looked through the Change logs on this thread and saw that survival mode isn't currently supported for Lollipop. Silly me!

Steve

*EDIT*
[SuperSU] FernBch:
This message is mainly for Chainfire. I really like SuperSU. You're work is awesome and I hope to be able to come back in the future. I had to uninstall SuperSU 2.46 today from my I-545. I was running the official CM12 nightlies for the Verizon Galaxy S4 and was using CWM 6.0.5.0 for my recovery. I am fairly certain something changed in CM12 after 2/12 but have no idea what. I was unable to flash a newer nightly and retain root access. Also had the same issue with 2.45. Today I did the following and all has been fine with CM12 again:

*************

I have been doing some seriously thinking of late and I think I am going back to stock and start over to return to CM12. Today because of the issue I am having with root, SU, and CM12 I decided to do a factory reset and try to start over. Problem was when I rebooted I had SuperSU, TiBu, and Root Checker all report that root was lost (I believe it said not properly installed). This has been going on for almost a week and I am tired of it. If this doesn't work I will probably have to go all the way back to out of the box, re-root, etc, etc. I'm not exactly sure what happened but something went on when I upgraded either CM after 2/12 or SU to 2.46. I'm hopin that the clean uninstall method to switch SU app works and I don't have to go all the way back.

Edit:

It seems I have been able to make an improvement with my SU issue without starting over. I uninstalled SuperSU (clean up to switch su app) and rebooted. On reboot SU was lost. Rebooted into recovery, wiped cache and davlik, dirty flashed 2/12, and rebooted. SU access has returned. I have also successfully flashed a nightly after 2/12 AND maintained root access. Not sure why but it seems I can no longer use SuperSU........

************

Unfortunately I have no log files that could possibly help to figure this out. Thanks Again for awesome apps for our Androids.
[SuperSU] zelendel:
One of the issue is most likely the new root setup that cm is using. It has been causing issues all over the place with other root apps.
[SuperSU] FernBch:
Agreed. Psychol3oy told me that CM12 handled root differently than previous versions of CM but he did not elaborate.
[SuperSU] Chainfire:
I am looking at this.

Survival mode shouldn't be necessary for CM12 nightlies. Have you installed the backup script? It's in SuperSU settings somewhere.
[SuperSU] huismeester:
Hello after the OTA update on my HTC m8 stock rom supersu dont work anymore not rooted anymore????

How can i this fix please gif a tutorial

version of SuperSU v2.46
[SuperSU] Primokorn:
Flash SuperSU.zip. OTA updates automatically remove root access.
[SuperSU] huismeester:
I Flash supersu again in twrp but the same problem same error

Apps for control root say the device is rooted???
[SuperSU] Chainfire:
RE: CM12

I've just flashed CM12 to my SGS4 in multiple ways, full system wipe and reflash 2015/02/15 nightly between attempts. Latest SuperSU 2.46:

- Enabled root access in developer options, installed SuperSU via APK, updated binary successfully, used the install to /system feature, used the install backup script feature, updated to a newer nightly (2015/2/18) via TWRP, root remained.

- Flashed SuperSU via TWRP, confirmed root operational, used the install backup script feature, updated to a newer nightly (2015/2/18) via TWRP, root remained.

The only thing I haven't tried is using CWM or CM recoveries... so if you're having issues try switching to the latest TWRP.
[SuperSU] LinoX:
Problem with SuperSU and Mobile Odin Pro (both latest versions from play store)

Scenario:

Galaxy S5 (with version ANE rom).

Download towelroot.

Download SuperSU from playstore.

Download Mobile odin pro from playstore.

Execute towelroot. device reboots.

Open SuperSU. It says it must update su binary and disable knox.

It updates binary and disables knox successfully.

Reboot.

Check system works properly. It's ok.

Open Mobile Odin Pro.

Download flashkernel.

Set the rom to flash (boa3 version, lollipop)

Tick everroot, wipe data, wipe cache.

Chose to reboot in download mode (to flash bootloader)

Flash.

Device reboots.

Roots rom, reboots in download mode.

Open odin (untick auto-reboot).

Flash bootloader only.

Reboot in recovery. CSC applies and auto-reboots.

"upgrading applications xxx of yyy"

system starts.

download from play store SuperSU again.

SuperSU warns SU binary needs to be updated.

Click on "update" (to update the binary)...

Installation failed.

Reboot.

Device doesn't boot anymore. Stuck at boot-loop.

Tried three times.

Any hint/fix?

It seems that mobile odin pro doesn't include latest SU binary and supersu has problems installing it....
[SuperSU] Steve Geemaggio:
Hi [MENTION=631273]Chainfire[/MENTION],

Thanks very much for your help. I installed the backup script and it works like a charm.

Steve
[SuperSU] fubo73:
Some notes:

- at "Flash bootloader only." phase, you should flash also modem.

- after "system starts", mop should not be there anymore (you selected wipe /data, ROM should delete /system and previous SU), it's a matter of which SU the ROM is using. But if you are installing SU from Play Store, is the ROM provided with any SuperSU?

- SuperSU from play store is 2.40. What is the version provided in ROM?
[SuperSU] LinoX:
I'm flashing the standard samsung lollipop rom. (G900FXXU1BOA3_G900FITV1BOA1_G900FXXU1BOA3_HOME.tar.md5)

I didn't flash modem because it's already flashed by mobile odin pro.

I had to flash the BL because MOP explictly says it doesn't flash it.

The flashed rom is fine. it works as a charm except for root.

The apps are the latest versions available on play store as of now (supersu 2.46)
[SuperSU] Mike B.:
Only [MENTION=631273]Chainfire[/MENTION] could tell us for sure, but the main issue might be your use of Mobile Odin. From the Play Store description of v4.20 (May1, 2014):

AFAIK there hasn't been any update since then. I know I have never been able to successfully use Mobile Odin since pre 4.4.2 days which is a problem since Odin/Heimdall is broken for Macs and not everyone has/wants a W*ndows machine. If you can Odin (not Mobile), try that but flashing the ZIP from recovery seems to be the preferred approach where applicable.
[SuperSU] LinoX:
Thanks mike, I've read the warning on play store listing but I used MOP to flash over an OLD 4.4 firmware (and I'm not using it to flash on 5, I know it doesn't work on 5).

I'm just posting it here because the app (supersu) on update failure says I should report the problem on here.

Moreover, I can't flash using a custom recovery because I want to keep KNOX 0x0.
[SuperSU] NeoLogY:
I'm sorry to jump in, but isnt root will gone if we flash any standard android ROM or custom ROM without root? And we need to reroot it? Correct me if im wrong.
[SuperSU] Mike B.:
Mobile Odin also fails on some "old" 4.4 versions (I forgot when exactly it started having trouble). It's clearly a matter of personal preference but keeping a virgin KNOX might be a greatly overrated goal and causes significant limitations without any obvious benefits unless your device needs to be inspected by a misguided employer confused about "security" matters. The KNOX flag got tripped on all my Samsung devices (and KNOX apps deleted) within hours of unpacking... ;)
[SuperSU] Chainfire:
I am working hard on the Mobile ODIN successor (spending most of my dev time on it, actually). It will hopefully be out shortly. Existing Mobile ODIN version carries an older SuperSU version that is not compatible with the latest firmwares. There's nothing to do about that right now.
[SuperSU] LinoX:
That's why I'm using MOP: to inject root during the flash of lollipop

---------- Post added at 04:40 PM ---------- Previous post was at 04:37 PM ----------

Thanks for the reply, Chainfire...but is there a way to manually update su? (since supersu fails to do it) I mean... now I have a working android 5 with a su binary installed that doesn't work and I can't update automatically...
[SuperSU] fubo73:
You answered yourself! The procedure to maintain root does not work with official ROMs, as Knox and other stuff are re enabled and prevent towelroot job effectiveness! You must flash some custom stock-based ones, like _alexndr or ambasadii ones. And, you must start from a towelroot'able KK ROM.
[SuperSU] NeoLogY:
Thanks for clear it out. Not so familiar with MOP.

Is it possible to use standard android 5 ROM and root it via odin/recovery like normal root method (using root.zip file) and flash supersu.zip file straight away after rooting, (while still in recovery, not yet boot into system)?

Thinking about flashing everything in 1 shot.:D
[SuperSU] fubo73:
If you like to trigger Knox to 0x1, yes, there are custom kernels that can be used. But if you want to keep Knox to 0x0, no way.
[SuperSU] conectarenet:
error

after update need update binary su. But error Install. Lg e455
[SuperSU] LinoX:
I didn't want to mantain root or re-root using towelroot (that doesn't work on newer kernels with the exploit fixed)

I wanted to root it again during flash, that's why I use MOP: To inject SU....but the "injected version" is old and can't be upgraded to a working one...that's why I asked if there was a "manual" update procedure to update the SU binary...
[SuperSU] fubo73:
You can't and will never be able to do that, I think, also after master Chainfire will release newer MOP. I suppose the problem is in these pre-rooting actions:

As all those options in stock ROMs will be enabled at first start (mainly the first I believe), I think MOP will not be able to maintain root. Custom ROMs coming from stock have all those options disabled.

But [MENTION=631273]Chainfire[/MENTION] can better answer about my thoughts...
[SuperSU] CyberpodS2:
Brother that is why you freaking rock!
[SuperSU] Goddly:
Hey [MENTION=4565594]CyberpodS2[/MENTION] what's been up? Been a long time. Lol need a white out theme? [emoji12]
[SuperSU] CyberpodS2:
Hey man, glad to see some old names around. Running a Verizon s5 with a Sprint ported Alliance Rom and a Nexus 7 (2013) running Screwed aosp 5.0.2 Not sure what you can do with those but I'm always looking for your look from WOR Rom! For the sake of this thread I also wanted to post that both these devices are running 2.46 with no issues and the nexus also running the lollipop alpha xposed. I'll drop you a note on one of your threads man.
[SuperSU] Ahmedivx:
Great Job, last version 2.46 runs flawlessly :)
[SuperSU] huismeester:
I have the latest version but keep getting the message

Update supersu binary

where and how do I do that.

Iam using Xposed framework for lollipop.
[SuperSU] baltics:
Have you set root options to apps or apps & adb in developers settings?
[SuperSU] KinoTheMystic:
So I want to use SuperSU but I have superuser installed in system/apps. Do I just install SuperSU from the play store or do I have to delete the superuser apk from that folder and then install superSU?
[SuperSU] It_ler:
No need to remove the superuser files or uninstall it.

Just install SuperSU app, and on first start, confirm to install its binaries.

Or flash the SuperSU zip file (from first post) in your custom recovery.

That's it.
[SuperSU] LogKill:
I installed SuperSU Pro would like to know how can I enable it in settings instead of launcher?

What do SuperSU configuration mean in 'you will not be able to open SuperSU configuration' when I choose launcher icon to be invisible?

Thanks
[SuperSU] Scurzmann:
ROM specific?

When you set launcher icon to hidden, SuperSU will disappear in your app drawer and thus you can no longer access SuperSU app and its configs. That's what it means.

But there are some ways you can open SuperSU's interface and set launcher icon back by either launching it from dialer or terminal.
[SuperSU] LogKill:
Thanks for reply. From what I know it can be done on CM12. Just that I dont know how to do it.
[SuperSU] karlbu:
Supersu 2.45 Pro freezes when an app asks for root access permission. Neither the 'grant' nor the 'deny' buttons respond, although the countdown timer continues to run. Root Checker app confirms the phone is rooted. T-mobile Galaxy Note 4 rooted for SM-N910T Android 4.4.4 using CF-AUTOROOT. Received 'pass' notification after root. Was working previously, but no longer. Any ideas?
[SuperSU] janedoesmith:
Do you have some sort of a screen overlay app like Lux or similar? I've read those apps may produce symptoms like yours.
[SuperSU] karlbu:
Thanks. I have Apex launcher installed. Will remove and report back.

---------- Post added at 03:41 AM ---------- Previous post was at 03:32 AM ----------

Wow. You are good. I had a screen overlay app called Twilight. Turned it off and, it worked. I would have never guessed that was the source of interference. Thank you.
[SuperSU] zelendel:
HAd you followed the rules you would have known.
[SuperSU] karlbu:
What rules?
[SuperSU] zelendel:
The one that states you are to search before posting. The issues was explained in length many times already. Might want to go over the rules again to make sure you understand what this site is about.
[SuperSU] karlbu:
I did, but didn't find anything. Case closed.
[SuperSU] zelendel:
Then you didnt search enough. This is a developers site. This have been covered dozens of times in this thread alone.

Your right case closed.
[SuperSU] ilnessuno4691:
Guys but why i can't flash su 2.45 or 46 on cm 11 :confused: instead the 2.40 yes, sometimes i've downloaded su from play store and i've seen that there's wrote in the version "2.40 (cyanogenmod)" or something of similar not remember well, why :confused:
[SuperSU] NZgeek:
There should be no problem running 2.45 or 2.46 on CM11. If the correct version isn't showing up in the Play Store, just download the zip file in the first post and install it via recovery.
[SuperSU] ilnessuno4691:
I installed cm 11, gapps, then su 2.46 failed, 2.45 failed, 2.40 successful
[SuperSU] Chainfire:
Link to your exact CM version and information on your device?
[SuperSU] ilnessuno4691:
Cm 11 M 12, pa gapps 4.4.x modular mini and S3 I9300 or what information of device you mean? anyway i am on cm 12 uo by justarchi right now and i don't never had problems to flash every version of supersu on all cm 12 roms (ex temasek, RR, slimpop, cm 12 uo) so, the problem is cm 11 i think.....or no? for this reason i wonder why on cm 11 no?
[SuperSU] fBx:
Hi Guys,

I flashed the 2.46 on my Stock M8 Lollipop today (with TWRP 2.8.5.0) and everything worked fine.

Strange thing is, everything I do and install in terms of root is not permanent. When I install AdAway and reboot the phone, the changes in the host are gone. When I delete a system app and reboot, it's back and so on. While I could live with activating AdAway once every reboot (which isn't that often), I do not think it is supposed to be that way. Any explanation maybe why everything gets reset? Is there some kind of new "automatic system recovery" in Lollipop that just undos changes in the system? Thanks.
[SuperSU] baltics:
I installed SuperSU 2.46 on a friend's phone running KK RR, last week.

No issues.
[SuperSU] ilnessuno4691:
in fact i told that the problem maybe is cm 11, but now that i think also on pa 4.45 i had the same problem........bho i don't care more, now i am on cm 12 and i have not problems to install new versions of supersu, i wanted just know if there's a reason
[SuperSU] Verrocio:
Grrrr

This one has got us kinda stumped here.

We installed SuperSU on a fresh device, it prompted us to update the binary which we did and worked fine. Then we used its option in settings to remove all other superuser apps. Then moved SuperSU to /system. Now its prompting us to update the binary again :eek: :confused: ?

So we went through the process again and it prompted us to reboot. We do and it goes to recovery and nothing happens. :-/ So now we are like wth ? :confused:

Edit I am attaching the recovery log but from the best i can tell there isn't anything worth noting from it.

Edit2: I should probably also mention everything was working fine with 2.40 with fresh devices.. this device included.

Edit3: I will try and recreate the issue on this device and a few more then post in the support thread.

EDIT4: Issue fixed. Will update soon.
[SuperSU] Software Guru:
Thanks for this
[SuperSU] andu86:
i cant install supersu 2.46 over 2.40 as normal apk on stock rom, it says that an existing package by the same name with a conflicting signature is already installed
[SuperSU] baltics:
Flash the zip for 2.46 in recovery.

Having installed it check settings so that it sticks if you update your ROM.
[SuperSU] andu86:
never mind, i had received the update via play store hours after posting in this thread :)
[SuperSU] MrKaon:
Got the Play Store update to 2.46 this morning.

Everything went smooth and binary flash with Normal method.

Thanks
[SuperSU] awha:
canr update my binary

I cant update my binary in my supersu and i cant completed my root on galaxy prime beloved . Would you help me ?
[SuperSU] qwerty22:
Why 5 digits instead of 4? 06755 instead 6755?
[SuperSU] ArtDC:
After upgrading to 2.46 the boot/startup time is almost doubled. Android 4.3, XTL. Any idea?
[SuperSU] jos90:
How much time does complete unroot take? Seems to be not working on my Moto G (4.4.4)
[SuperSU] bovirus:
Read carefully first post.

Supersu is not a root program. It's a program to handle admin program permission.

To root your device you have to use specific root program (Framaroot/iRoot/Kingoo root, etc)-.
[SuperSU] hanschke:
can I flash it on my lg watch too or do I have to wait for extra wear support?
[SuperSU] qwerty22:
chmod 06755

Why in the rooting script permissions on the files specified as 5-digit number (0 before 4-digit number)?

set_perm (0, 0, 06755, "/system/bin/.ext/.su");

6 - understood, 755 - understood, but what is 0?
[SuperSU] efrant:
A leading zero is standard notation signifying that the string is an representation of octal numbers.
[SuperSU] qwerty22:
Thanks for the answer! Will be different the result of the following commands?

1.

#chmod 6755 /system/bin/.ext/.su
#chmod 06755 /system/bin/.ext/.su

2.

#!/system/bin/sh
chmod 6755 /system/bin/.ext/.su
chmod 06755 /system/bin/.ext/.su

3.

#!/system/bin/sh
set_perm() { chmod $1 $2 }
set_perm 6755 /system/bin/.ext/.su
set_perm 06755 /system/bin/.ext/.su

4.

#!/system/bin/sh
set_perm() { chmod $1 $2 }
SUMOD=6755
set_perm $SUMOD /system/bin/.ext/.su
SUMOD=06755
set_perm $SUMOD /system/bin/.ext/.su
[SuperSU] Frank Westlake:
'chmod' expects an octal value and does not require the zero prefix. Any value that cannot be read as octal (i.e. 0x08) is a "bad mode". Chainfire's installation script tries to support all devices with that one script so he or she might be including the prefix for some other variation of 'chmod' that we aren't aware of.

Frank
[SuperSU] qwerty22:
Maybe Chainfire uses a modified chmod, in which the 0 (5th symbol) is important?.. Ubuntu ignores that symbol if symbol is equal to 0 (or 00). My script for testing variants:

#!/bin/bash
echo 1> test_file
echo Set perm 0644
chmod 0644 test_file
ls -l test_file
set_perm() {
chmod $1 $2
}
VAR1=06755
echo Set perm "$VAR1"
set_perm $VAR1 test_file
ls -l test_file
VAR2=6755
echo Set perm "$VAR2"
set_perm $VAR2 test_file
ls -l test_file
rm test_file
[SuperSU] Garv35:
Supersu not working
[SuperSU] fubo73:
Did you join XDA to be banned? :confused::confused::confused:
[SuperSU] Mezot:
Guess alot of people here beg the difference. It's working as intended.
[SuperSU] YK RAJ:
Where is update for su v2.40 to 2.46? Because yet showing 2.40 on ps.
[SuperSU] fubo73:
Same here. Are you on KK or LP? I am thinking PS updates only for LP.
[SuperSU] egingell:
My phones both have 2.46 from the Play Store. Android 4.1 and 4.2 respectively.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] fubo73:
My S5 has 2.40 and PS does not report any update. Perhaps CF disabled update for S5...
[SuperSU] YK RAJ:
I think exactly this is the reason.But [MENTION=4587767]egingell[/MENTION] saying he has 2.46.

I'm on note2/note4 (4.4.4) but not getting any update v2.40+ from ps(@Chainfire).