yashsingh1/xdaforums huggingface dataset:
[SuperSU] SweetwaterBurns:
If I were you, I would find out what files SuperSu removes/changes during the unrooting process and make a CWM update script that does the same thing. That way you could flash it right after flashing your updated rom. The main problem with this method is if CM makes a major change to its root method, you'll have to update the script.
[SuperSU] jimzweb1:
Hi chainfire, I run SuperSU Pro. I have a Sprint Note 3 running Stock rooted NC5 4.4.2. A coupe of days ago I updated to 4.4.4 NK4, by clicking on SuperSU Pro v 2.40 it asked if I wanted to disable KNOX. After clicking OK it just froze at "disabling knox" . I wish I could supply more info but that's about it. No rush I know your very busy, please have look when you get a chance. Thank You !!!!
[SuperSU] ezio84:
Hi [MENTION=631273]Chainfire[/MENTION] !

I'm using on my rom the "launch SuperSU from Settings" commit, it works well but SuperSU loads the white theme and in its settings the theme entry is missing.

Is there a way to restore the theme setting in the app? Thanks.
[SuperSU] hellripper:
Hey guys i was facing a problem regarding supersu

I rooted my gts 5282 2days ago and now it asked for update

I updated my supersu. From then onwards when i open supersu it says to update binary. So i triedcto instal in normal mode. Installation failed it says. Anyone of u kindly please help.......
[SuperSU] baltics:
If you are using lollipop there should be a developer option 'root access', set it to 'apps only' and reboot.
[SuperSU] Miche1asso:
Just to let you know that after updating ROM Toolbox Pro SuperSU went nut. The phone was getting stuck. I checked with "top" via "adb shell" and SuperSU was spamming the OS with processes asking for the root authorization for that app. I know it is most likely a ROM Toolbox Pro fault but just in case...

Also, why is SuperSU so S L O W anytime it needs to make a new authorization? I am talking about a minute or two before to get the popup window. This on Xperia M2 with stock KitKat 4.4.4

PS: Now it shows the popup window in a couple of seconds. I tested a couple of apps changing the permission from allow to ask. I didn't really change anything. Never mind.
[SuperSU] Alexey71:
@Chainfire

Hi. Add SuperSU key.apk in 99-supersu.sh
[SuperSU] Frank Westlake:
I can't tell if those last two sentences are negating the P.S. or what comes before it, so it would help if you restate any problem that remains.

Frank
[SuperSU] Miche1asso:
The PS was about the slowness to get the auth window. I always remembered in this phone SuperSU to be quite slow. And so it was when the ROM Toolbox update trashed the phone. Until I tampered a bit with the SuperSU options. Just changing permission from ask to allow back to ask a couple of times plus some change of settings for the notifications it went from a minute or two to 2-3 secs.

The problem with ROM Toolbox instead I think is still there. I just managed to circumnavigate it. But I could reproduce it twice. The steps should be the following:

- Have ROM Toolbox Pro previous release installed and with actions running at boot time (like set DNS)

- Update the app

- Do not launch it

- Reboot the phone

After few minutes it spammed SuperSU requests ending up hanging the phone. It could be it was paired with the fact that the auth window was taking a couple of minutes to show up, making things worse. Still I'd expect an app to wait for an answer before to make new requests. But that's ROM Toolbox. Checking the log with the app running fine one can see just that application, with dozens of entries.
[SuperSU] TheWilkieWay:
Anyone know what this wakelock would be from? Been wondering what was keeping my phone 'awake' and I think this is it. Was on super su v2.40 and just updated to v2.44 to see if that fixes it. I can provide any more information if needed.
[SuperSU] NZgeek:
This is unlikely to be caused by SuperSU itself.

When an app wants to run some command as root, gay command isn't executed by the app itself, instead, SuperSU creates a special helper process that runs root commands on behalf of the app. If one of those commands good a bit crazy (e.g. holding onto a wakelock) then it looks like SuperSU is misbehaving, not the app that asked for those commands to be run.

The only way to tell for sure is if you can get the process id of the SuperSU process holding the wakelock. There's info somewhere in this thread on how to trace that back to the process SuperSU is doing work for. You'll need to do that to find the real culprit.
[SuperSU] Avasta:
Life saver!!!

Installed a new ROM and was having Root Issues, Chainfire is DA SH!T
[SuperSU] Daved+:
Deleted
[SuperSU] egingell:
What does that have to do with SuperSU?

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] bjorntje123:
Hey guys i was facing a problem regarding supersu

I rooted my sm-g386f today and now it asked for update.

I updated my supersu. From then onwards when i open supersu it says to update binary. So i triedcto instal in normal mode. Installation failed it says. Anyone of u kindly please help ......
[SuperSU] shaggyskunk:
Did you flash the zip - or get it from the store?

If you got it from the store - I'd flash the zip - You shouldn't have any problems after that.

Sent from my SM-N910W8

Running SlimLP
[SuperSU] bjorntje123:
From the store
[SuperSU] shaggyskunk:
Flash the zip in the OP ?

Sent from my SM-N910W8

Running SlimLP
[SuperSU] JustinSB:
Upgrade boot loops Lollipop

I got a pop-up this morning telling me that my SuperSu binary needed upgrading on my Nexus 7 grouper/nakasi tablet with TWRP recovery version 2.8.4.0 & Lollipop 5.0.2, so I did what I always do & told it to upgrade the binary using TWRP. It did, & semed to work OK, but then dropped into a boot loop on the rotating balls. The only way that I could get it to boot back up was to use:

fastboot boot CF-Auto-Root-grouper-nakasi-nexus7.img

with the version of Auto-Root that I had already downloaded yesterday. Has anyone else seen this?

Justin
[SuperSU] gurr4m:
Sorry for a n00b question, but difference between SuperSU and the superuser app which comes bundled with my CM12 ROM, do they do anything different? Which one should I use? Thanks.
[SuperSU] simonbigwave:
for me, if you use Titanium back up on CM12, most users use SuperSU with better results and no problems in backup.
[SuperSU] Scurzmann:
Same superuser, but supersu seems to have better binaries and has some distinct features not available on cm or other superuser tool. See post #1 for complete list.:)
[SuperSU] arman68:
How to disable notifications (without gui access)?

Since version 2.16, on Amazon Fire TV, the SuperSU GUI does not load anymore (I have tried it on multiple Fire TV). Is there a way to disable the notifications toasts from a shell or adb prompt?
[SuperSU] bringonblink:
Thank you for the best super user app

Sent from my Nexus 4
[SuperSU] balramkukreja:
binary update problem

I m getting problem in updating the su binary in my new canvas nitro a 311 plzz help....:(
[SuperSU] GroteBozewolf:
You need to be me specific. What problem do you have with updating?
[SuperSU] shaggyskunk:
Did you try flashing the zip in the OP - Solves most problems ?
[SuperSU] bocke85:
i have problems with cm 12 and titanium backup on my xperia z1 compact "amami" i knew it from my old i9300 that i could flash this zip... but is it compatible with the sony and will it work on it?

many thx
[SuperSU] blisside:
I cannot seem to find recovery mode

I have pains for the full version and cannot find the ota survival mode on my phone I have a oneplus one and I am running custom cm12

Any tips would be greatly appreciated
[SuperSU] sparksco:
Download the pro license as a separate app. This app goes on data so ota survival can work. Works great for me. Also maybe restart your phone so the su app can reload and see the license.

https://play.google.com/store/apps/details?id=eu.chainfire.supersu.pro
[SuperSU] gqukyo:
Should be under the custom rom section in settings. Says something along the lines of installing a backup script to survive flashes.
[SuperSU] balramkukreja:
Its just loading...........for a long time but not updating
[SuperSU] Chainfire:
v2.45 released. Release candidate, ZIP available via latest stable zip permalink. Will be updated to Play sometime in the next few days if no show-stopper issues are found.
[SuperSU] Giobio:
As usual it works on my S2. No issues with system or apps need/work supersu.

Thanks again
[SuperSU] dkonect:
Work fine on s3 GT-I9300 (on kitkat and lollipop)
[SuperSU] Ja_som:
No issue with 2.45 on my Nexus 7 WiFi Android 5.0.2 and on Moto G GPe Android 5.0.1

installed apk and binary updated with normal method inside app...

Thanks...
[SuperSU] GTI-9300:
Works fine on S4 GT-I9506
[SuperSU] sancho_panzer:
Working fine here.

Device:

Samsung Galaxy S4 (GT-I9505)

ROM:

CyanogenMod 11/M12 (KK 4.4.4)

Kernel:

Alucard-V1.4qs

Recovery:

TWRP 2.8.4.0

Modem:

I9505XXUGNE8

Device:

Nexus 7 (Grouper)

ROM:

CyanogenMod 11/M9 (KK 4.4.4)

Kernel:

Default CM11/M9 3.1.10

Recovery:

TWRP 2.7.1.0
[SuperSU] Lonnie Reeder:
2.4.5 zip file install

So far so good. I am running a Asus TF300t, running KatKiss Lollipop 5.0.2 release 15.

Thanks for such an awesome app.

Lonnie
[SuperSU] mrrocketdog:
v2.45 , all good. :good:

att htc one m8 - unlocked - superCID - s-off - CM11 latest nigjtly.
[SuperSU] damca:
Thanks all works good on lollipop on note 3 9005
[SuperSU] CyberpodS2:
All good on both S5 running 4.4.2 and Nexus 7 (2013) running 5.0.2
[SuperSU] scrin378:
Works well on note 2 4.4.2
[SuperSU] daniello8:
Flashed 2.45 with Mobile Odin on Galaxy S5 .. which is now hanging on "booting recovery" .. so no TV this evening :(
[SuperSU] Frank Westlake:
2.45 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

Frank
[SuperSU] king.larry:
I tried SU 2.45 on my Samsung Note 10.1 (N8000) with Android 4.4.2. Freezes after reboot, no chance. Back to Vers. 2.40 and everything is O.K.
[SuperSU] c3k:
full unroot seems to delete both /system/bin/install-recovery.sh and /system/bin/install-recovery_original.sh

:eek::eek::eek:

i'm on 2.40
[SuperSU] osm0sis:
Yes, hopefully [MENTION=631273]Chainfire[/MENTION] can add an OTA option to the Clean up list. :good:
[SuperSU] paynedave315:
Chainfire works for Google now have you gorgot

sent from my beast note 3
[SuperSU] qwerty22:
The Pro version additionally offers: "Per-app user override". What does this mean?
[SuperSU] egingell:
Tap the app on the Apps tab and change its settings to override SuperSU's settings.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] RafaelWP:
You did a great job with the Moto G 2014 at 2:45 SuperSU update! Thank U! Boot is fast as factory!
[SuperSU] Duiesel:
Mod edit: Do not quote the entire first post.

Hello guys!

Can anybody help me with link or tutorial how to add root into my custom rom?

I copied files and gave permissions like described in comments into update-binary.

It isn't properly working :(

I'm trying to repack stock android 4.4.2 Rom for Lenovo Yoga tab.

Some suggestions?

Thanks
[SuperSU] atamig:
Works well on Sony Tablet Z2
[SuperSU] cpvm:
Anyone get android is upgrading message every boot, it occurs since v2.45?
[SuperSU] G.M.L:
Yes and me get this message in every boot after installed v2.45

G.M.L.
[SuperSU] white7561:
Already try wiping dalvik cache?
[SuperSU] b@r1:
!

Thank you man
[SuperSU] Niro96:
Wakelock Detector doesn't work on a OnePlus One with SuperSU. TitaniumBackup works.

Edit:

I have found it. In SuperSU Settings -> CM -Root note Settings -> Enable.
[SuperSU] raz_il_dio:
superSu problem

Hey everybody....so supersu worked fine for me but yesterday has stopped working....i get this error every time i open supersu ( i have the paid version) i think is about the su binary ...i tried to update it via recovery mode,...ecc but still nothing. ...I'm always getting this error ( sry if it's in italian) xD how can i fix it? Thanks
[SuperSU] gorilla p:
Have you tried Settings>Cleanup to switch superuser app, uninstall, then reflash?

Visit the NeXuS⁴ file repository at bit.ly/makostuff
[SuperSU] raz_il_dio:
I can't open supersu lol after that message he push me to the home screen :/
[SuperSU] dancapitan:
this is why this version 2.45 is not yet in play store because is not final, still buggy so wait until is released officially thru play store.
[SuperSU] Taomyn:
I'll just leave this here:

*runs away*
[SuperSU] dancapitan:
i'll wait for play store version as always did :good:
[SuperSU] Chainfire:
2.45 is an RC, as in, it'll probably go to the Play store as it is right now. Probably.

There have been nearly a hundred thousand installs of this version of SuperSU over the past few days, and as far as I've seen only two users have reported an issue.

I will start a staged rollout.
[SuperSU] nightcr4wler:
Hi,

I've update to the latest version from play and when I open the app it says that binary needs to update.

Installation fails on either normal or TWRP.

What shall I do?

Thanks.
[SuperSU] purian23:
To hear those install numbers is just phenomenal to put your work into perspective! Thank you Chainfire.
[SuperSU] sancho_panzer:
I never understood why people prefer Play Store over flashing it on recovery...

Device:

Samsung Galaxy S4 (GT-I9505)

ROM:

CyanogenMod 11/M12 (KK 4.4.4)

Kernel:

Googy-Max3 CM-Kernel 1.2.5

Recovery:

TWRP 2.8.4.0

Modem:

I9505XXUGNE8

Device:

Nexus 7 (Grouper)

ROM:

CyanogenMod 11/M9 (KK 4.4.4)

Kernel:

Default CM11/M9 3.1.10

Recovery:

TWRP 2.7.1.0
[SuperSU] nightcr4wler:
Did that first. It didn't work.

Then I tried the play version, also to no avail.
[SuperSU] egingell:
Because it's not at all necessary and end-users don't like doing things themselves.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] jesssiii:
Some people want to root but not install custom recovery.

LG G2 VS980
[SuperSU] NZgeek:
Ummm... Installing SuperSU from the Play Store will not give you root. You need to be rooted already for SuperSU to install its own version of the su binary. Installing SuperSU just gives you a better root :)

If you're installing from a custom recovery, this limitation doesn't apply. The recovery has root-level access to the file system and can put the right files in the right places
[SuperSU] sancho_panzer:
Nice debate, very valid points. But I doubt that users at Xda are "end-users don't like doing things themselves". Having root without a custom recovery is another thing that puzzles me because all the possibilities you'll be losing (ok, don't bother to explain me again the warranty stuff and bla, bla, bla).

But hey, Vive la différence. Nice debate though. :thumbup:

Device:

Samsung Galaxy S4 (GT-I9505)

ROM:

CyanogenMod 11/M12 (KK 4.4.4)

Kernel:

Googy-Max3 CM-Kernel 1.2.5

Recovery:

TWRP 2.8.4.0

Modem:

I9505XXUGNE8

Device:

Nexus 7 (Grouper)

ROM:

CyanogenMod 11/M9 (KK 4.4.4)

Kernel:

Default CM11/M9 3.1.10

Recovery:

TWRP 2.7.1.0
[SuperSU] ViNNNtalik:
No problem. Just send (when it will be ready) me updated values
[SuperSU] joselopez23:
I have a problem with SuperSU. SetCPU and other apps that has an option to "Set on Boot" does not work. I have to open the app for it to run. Please advise.
[SuperSU] PMGRANDS:
Do you have any Boot Startup apps Installed that may be preventing the Startup?
[SuperSU] joselopez23:
Nope none. Set on Boot works on Superuser though but not on SuperSU.
[SuperSU] jwds1978:
They (i.e. Root Call Blocker, SetCPU, etc.) are working just fine for me.

--

Sent via Tapatalk 2 from my TELUS HTC Amaze 4G on the Fido network.
[SuperSU] shinobisoft:
Did you go into SuperSU settings and tick the update binary option?
[SuperSU] freifahrt:
>>>Very good work, thanks Bro.<<<

Me and my countrymen could look forward to a German translation!

If necessary, I would also provide the string. ...
[SuperSU] Reviewers:
This helped me root my ROM.

Thanks!
[SuperSU] xz124:
Hey chainfire,

First, thanks for all your work on android. This is a great app. Secondly, do you think we might see a pro feature where a pin is asked for every time an app requests root for the first time again in say 10 minutes or so? (I.e. if an app asks for root, get pin authorization from the user and don't ask for a pin again for 10 minutes unless a different app is asking). That would really help us paranoid people :) (especially when someone asks to borrow my device).

Thanks!
[SuperSU] shaggyskunk:
You're kidding right?

If you are in fact one of those "paranoid" people, don't lend your phone.

Sent from Down The Rabbit Hole, using Tapatalk 2.
[SuperSU] segv11:
Before lending your phone, go into SuperSU, set survival mode, and disable root. When you get the device back, go back into SuperSU (pin required) and enable root.
[SuperSU] Pons:
One thing about the survival mode/pin. It does not ask for a confirmation pin, so you enter it once and hope you typed it in right. Does adding a confirmation pin sound like a good request?
[SuperSU] huyrich:
I'm trying to uninstall SuperSU and unroot my Galaxy Tab GT-P6210 (root by the method from this thread: http://xdaforums.com/showthread.php?t=1367249). Whatever I tried (Reinstall, Cleanup, or Fully Unroot), it never completed successfully. I lost root but SuperSU is still there and there's no way I can remove it. Opening the app I got:

"There is no SU binary installed and SuperSU cannot install it"

and an OK button which just closes the app upon clicking it.

I also tried removing supersu.apk and busybox in xbin but something doesn't let me do it (maybe supersu itself?)

So how do I remove SuperSU now?

TIA
[SuperSU] shinobisoft:
Have you tried using adb uninstall?

"The way is known to all, but not all know it."
[SuperSU] huyrich:
After poking around for a bit, I had to get Root Explorer pro to get the job done. So I just removed supersu.apk in xbin. Hopefully that's a "clean" uninstall".
[SuperSU] mviana:
Is the above method the way that I need to go to use this app with HTC One S? I'm rooted and trying to watch movies from Play store along with movies purchased from HTC Watch app.

Do I just use root explorer and delete as well to be able to watch movies on my rooted device?

Marc
[SuperSU] bsoplinger:
SuperSU has built in a way to temporary unroot for just your sort of need. Use that and you shouldn't need to fall back on using a file explorer.

Sent from my PG41200 using Xparent Purple Tapatalk 2
[SuperSU] mviana:
unchecked Enable Superuser and still does not allow me to play movies from HTC Watch app. It's a little frustrating when you have purchased movies and can't watch them. grrr

Any direction pointing would be very much appreciated.

Thanks

Marc
[SuperSU] dimebagdan65:
Search Ttorrent on the play store... Screw Watch lol
[SuperSU] Pons:
Did you reboot after you unchecked it? If not, try that.
[SuperSU] fubo73:
Samsung knox 0x0 users, like me, don't have custom recovery, and rely on play store version ☺

Sent by my NeatROM'd SM-G900F, aka Galaxy S5
[SuperSU] sancho_panzer:
Yes, I know, it was rhetoric. Read above. ;)

... and my knox have been tripped long time ago. :)

Device:

Samsung Galaxy S4 (GT-I9505)

ROM:

CyanogenMod 11/M12 (KK 4.4.4)

Kernel:

Googy-Max3 CM-Kernel 1.2.5

Recovery:

TWRP 2.8.4.0

Modem:

I9505XXUGNE8

Device:

Nexus 7 (Grouper)

ROM:

CyanogenMod 11/M9 (KK 4.4.4)

Kernel:

Default CM11/M9 3.1.10

Recovery:

TWRP 2.7.1.0
[SuperSU] Deltadroid:
patch for backup script

[MENTION=631273]Chainfire[/MENTION]

I've been testing SuperSu 2.45's backup script and have found two issues (one is a lollipop only issue).

1) bin/log is a softlink to toolbox and should not be included in the list of files to be backed up. This causes the toolbox binary to be copied to bin/log after an update is applied.

2) When a directory is restored after an update and that directory is not part of the original ROM structure, the directory is given full read/write/execute permissions upon recreation. A post-script rule is necessary to set the proper permissions (755). This behavior is the same for CyanogenMod 11 and 12. For Example, /system/app/SuperSU is not a directory that is part of the original ROM, so when that "SuperSU" directory gets restored after an upgrade, it will be full read/write/execute. It is noticeable in lollipop because of the new file structure in /system/app/.

In the mean time, I've made a file to flash in the recovery that installs a patched backup script in addon.d:

supersu-v2.45-backup-script-signed.zip

Patch:

--- 99-supersu.sh.orig	2015-01-22 23:12:43.014098798 +0100
+++ 99-supersu.sh	2015-01-22 23:03:40.477860000 +0100
@@ -19,7 +19,6 @@
xbin/otasurvival.sh
lib/libsupol.so
lib64/libsupol.so
-bin/log
bin/.ext/.su
etc/init.d/99SuperSUDaemon
etc/install-recovery.sh
@@ -136,5 +135,6 @@
fi
fi
fi
+ chmod 755 /system/app/SuperSU
;;
-esac
+esac
\ No newline at end of file

Regards.
[SuperSU] egingell:
In the I forget how many years I've had an Android device, I've not once felt like I needed a custom recovery. Everything I need to do can be done with ADB and/or Root Explorer. If something goes terribly wrong, I have Odin one-clicks and Download Mode. If something goes catastrophically wrong, no custom recovery in the world is going to help fix it.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] Mike B.:
Correct, there is no absolute

NEED

for a custom recovery but it sure makes life much easier, especially for those of us who don't always have access to a suitable computer for ADB or something that runs Odin (not an option for Mac users). Obviously Root Explore require the ability to boot into a usable Android and won't help in many cases. A custom recovery, preferably one with builtin file manager, can help you recover from many catastrophes, even if only by reflashing crucial components . Stock recoveries vary in capabilities but are usually much more limited in flexibility.

I never quite understood why keeping Knox at 0x0 is so important for some people since I've never heard of anyone having actual trouble after tripping that bit. Let's face it, if your device is rooted, it has already lost its virginity and pretending that it's true stock by keeping the custom recovery doesn't seem to bring any obvious benefits. If something goes catastrophically wrong, a custom recovery has at least a better chance of fixing it. No guarantees, but since it doesn't hurt, going custom is probably the wise way to go, just in case... ;)
[SuperSU] efrant:
Let's keep this thread on-topic please. This is not the place to discuss the benefits of using a custom recovery.
[SuperSU] Chainfire:
Your adjustments break OTA survival mode on 4.x.

bin/log backup should be prevented by this line, in case bin/log is not overwritten by the OTA suvival script:

[ ! -L $S/"$FILE" ] && backup_file $S/"$FILE"

I'll implement your chmod's.
[SuperSU] rockknee:
Is anyone else prompted to reinstall SU binary after CM updates or is it just me? I have backupscript enabled from settings and I'm using the latest SuperSU V2.45.
[SuperSU] wimsop:
Hi! Do the CF-Auto-Root packages (specifically the one for titan_retaildsds) already include version 2.45? Or how can I find out (before installing, of course)?
[SuperSU] amirmalas:
when I want to install " S Note " it prompts "Not Installed." message.

Do you have same problem ?!

what should I use instead of it ?!
[SuperSU] zelendel:
Please post in the proper thread. This has nothing to do with SU.

As for your question make sure to be using a touch wiz rom. Other then that ask your rom developers.
[SuperSU] crz210:
SuperSu chain fire

I'm new at rooting on my phone if any body can help out I would really appreciated thanks::
[SuperSU] sjsharksfan420:
What do you need help with?