yashsingh1/xdaforums huggingface dataset:
[SuperSU] skulldreamz:
Hey, I was just thinking about how much I use adbd insecure and thought maybe you could implement giving root to adb in your SuperSU pro version for the people that have already purchased your adbd insecure app and then also give a prompt where if someone hasn't bought adbd insecure yet, in maybe a new part of your SuperSU settings you could add a area where people have the option to buy it or if already bought have a option to check it and will get automatic root to adb. Just a thought and could help save a little space on everyone's phone's and would be a pretty cool feature in SuperSU. Just a thought..
[SuperSU] Mezot:
Pro ver bought. Thanks for this awesome app :)
[SuperSU] justforkix:
Phone hanging on encryption

Hi. When I try to encrypt the phone using Android's standard encryption tool, the phone stays for hours on end with the boot logo animation running. After a full afternoon and night, I had to re-flash the ROM to get the phone to work again.

Any ideas of solutions?
[SuperSU] eaque:
Hi guys!

Quick question. I'm using CM12 and want to install Super su. What should I do between 2 nightlies update reguarding super su? Nothing, everything should work? Or there is something to do before or after flashing?

Thanks!
[SuperSU] remo0073:
In my experience, sometime I had to flash again supersu zip after nightly update

But not always...

Sent from my Moto G
[SuperSU] eaque:
OK, thanks. Nothing to do in the settings (super su or CM)?

Once, I tried and I couldn't open super su and root was lost. I guess I wasn't lucky! :D
[SuperSU] FernBch:
Don't know if this has been reported or not.

I'm using CWM 6.0.5.0 and am running the official CM12 for jfltevzw. The binary update does not survive new ROM flashes and must be updated after each new nightly. Not sure if it is a CWM, CM, or SuperSU issue.

I am using the latest SuperSU installed as a system app with the backup script enabled.
[SuperSU] w74132003:
I'm using m8 lollipop

everytime I flash the zip with recovery

I always stuck at the boot animation and can't get into system

but I do the same action with 4.4.4 , everything is fine:confused:

please help
[SuperSU] PAGZLY:
No update su binary code

It will not be updated in the 4.4.2 binary code
[SuperSU] PAGZLY:
No update su binary code

It will not be updated in the 4.4.2 binary code #2
[SuperSU] oae08:
when im using supersu on lollipop when i open titanium backup it tells me that mount namespace seperation setting in supersu might not work reliably. Is it recommended to turn it off guys? thanks
[SuperSU] Beat_Slayer:
Yes, otherwise TiBu doesn't work properly.
[SuperSU] Verrocio:
Ghostmode on GB

Does the "always run in ghost mode" feature work on gingerbread ?
[SuperSU] oae08:
but i kept it as it is, and didnt encounter any problem. Maybe luck? I dont know, but if it is known to cause problems, why it is ON by default by supersu ??
[SuperSU] Beat_Slayer:
Because it's safer. And you can disable and re-enable it when needed.
[SuperSU] Pkt_Lnt:
Titanium Backup is the only app that has trouble with namespace separation, The only problem is this "Display a warning if using SuperSU with the “mount namespace separation” setting enabled, which caused “Insufficient free storage space” errors for many users."

Leave it enable, run a TIBU and see if it works, if it does, keep it enabled. It runs fine for me on 4.4.4 with namespace separation enabled.

I'd google what the importance of namespace separation and why it is active rather than blindly disabling it in SuperSU over another app warning without understanding why.
[SuperSU] rogers11:
Same here.
[SuperSU] silvertrain78:
Unrooting Moto G XT1064 to receive OTA?

My GF's Moto G XT1064 just received a 5.0.2 OTA, and before installing I used the unroot feature in SuperSU 2.44, then flashed the stock recovery. Thought I would be good to go, but then several attempts at installing the update failed. Long story short, it was a PITA to get back to a state where I could apply the OTA update, and eventually everything worked out. I'd like to root her phone again, but want to know how to properly prepare for an OTA, so as not to have to repeat this experience.

Any ideas?

(Personally I have a N5, so this kind of thing is never an issue)
[SuperSU] :
Question is probably best suited in that device's forum
[SuperSU] dancapitan:
latest version is 2.40

hey chainfire why the latest version on play store is 2.40?? https://play.google.com/store/apps/details?id=eu.chainfire.supersu

:confused:
[SuperSU] SignetSphere:
http://xdaforums.com/showthread.php?p=58351765#post58351765
[SuperSU] Giobio:
Maybe your answer is on post #8185
[SuperSU] Scurzmann:
Take a little look-see on page 819 he mentioned about that matter.
[SuperSU] tcat007:
This has probably been answered, but too many posts to read through. Why does this sometimes end up in settings with no option to change theme to dark, and sometimes has a folder icon you can place anywhere with option to go dark? I know it's ROM dependent, but is there a way to always have the second option?
[SuperSU] shaggyskunk:
Probably try flashing the zip in the OP - That should give you the options that you're looking for
[SuperSU] cpnfantstk:
Flashed 2.45 zip via recovery .Reinstalled SU for from Google Play to get back icons. Version says 2.40. What happened? JB 4.12
[SuperSU] Pkt_Lnt:
http://xdaforums.com/showthread.php?p=58351765#post58351765
[SuperSU] cpnfantstk:
Thanks I saw that. I thought using the 2.45 zip would change the version # of the app to 2.45.. The app still says 2.40. Did I miss something?
[SuperSU] Pkt_Lnt:
You downgraded to 2.40 at the Play Store. Flash the zip and leave it alone to be on 2.45.
[SuperSU] cpnfantstk:
My intention was not to downgrade. It's just that after flashing the zip , my icons disappear. I don't know another easy of getting them back. BTW..thanks for helping me.
[SuperSU] Pkt_Lnt:
Understood. Just be patient until the 2.45 rolls out to you in the Play Store. It can take some time, but obviously, you are not up to 2.45 which is why the Play Store install was a downgrade.
[SuperSU] cpnfantstk:
So what am I left with. 2.45 zip gives me updated binaries but within the 2.40 version of the app. Huh? Sorry for the lack of knowledge. Can I zip without the icons disappearing so 2.45 means 2.45 within the app. ?
[SuperSU] doveman:
Deleted, sorry wrong thread.
[SuperSU] waleedezz:
rooting help

i wiped kisskat 4.4.2 kitkat to try to install omniROM, i wiped the system n formatted, but then flashing the rom failed, is it coz i lost root? if so how can i re-root it again, flashing superSU by twrp fail coz no system exist to complete installation, even installing a zip flash of this version of superSU didnt make difference when it came to installing the rom, did i do the rooting wrong, i mean did i miss something?
[SuperSU] shaggyskunk:
Sounds like you need to Odin back to stock - Then start over.
[SuperSU] NZgeek:
If you're familiar with Windows, here's a good way to think about root and recovery.

Unrooted Android is a bit like using Windows as a non-admin user. There are a bunch of things you can do, but there's also a lot of stuff that's off limits.

Rooted Android is like using a Windows account with admin rights. You can get at the stuff that's off limits to normal users. Depending on your settings, you may get asked to confirm that admin-level operation.

Recovery is like booting off a Windows install disc. You're not logged into Windows, so it doesn't care who you are or what rights you should have (i.e. rooted or unrooted). It's got full access to the entire storage drive and can make whatever change it wants.

[MENTION=6345905]waleedezz[/MENTION]: You're flashing a ROM from recovery, so root isn't even party of the equation. Your best chance of getting help is to ask in the OmniROM thread for your device. Remember to search the thread first, in case someone has already found the answer.
[SuperSU] badpanda:
Okay. 3rd user.. I have this rare issue where when I install stick mount after flashing supersu 2.45 I get a message saying my supersu is outdated... Also I noticed problem where stick mount will not unmount.. ever. even when rebooting it will mount by itself with out anything pluggd in...
[SuperSU] waleedezz:
thank you for your help, i will check with OmniROM
[SuperSU] simonbigwave:
just report SuperSuPro v2.45 installed on CM12 - 0130Nightly i9505 jfltexx all OK no problems.
[SuperSU] NovaSlim:
SuperSU v2.45 conflict with Elemental X kernel Aroma installer

Got a potential issue here. There seem to be a conflict between SuperSU v 2.45 and ElementalX Kernel's Aroma installer. When using EX's Aroma installer on a device with 2.45 aboard the setting I(and a few other users http://xdaforums.com/search.php?searchid=337800136) set do not apply.

Attached a screenshot, I set readahead cache to 256 in aroma yet it shows 128 after boot.

I was only able to resolve this by flashing back to SuperSU v2.40

Take screenshot 3, reboot into recovery and flash EX 2.06(row/256)

Take screenshot 4, see that row/128 was shown in EX app

Reboot into recovery again, flash SuperSU v2.40 first then EX 2.06(row/256)

Take screenshot 5, confirm that 256 stuck as readahead setting, go into playstore and disable auto-update for SuperSU & SuperSU pro

Just for confirmation, I rebooted and reflashed EX2.06 again, this time changing readahead to 512, and this time it stuck too.(screenshot7)
[SuperSU] :
Flash the v2.45 zip from recovery and then don't update SuperSU from Play Store. Check Play Store after a few days to see whether the SuperSU version in Play Store says v2.45 and then update. :good:

v2.45 is being rolled out to Play Store in stages so some regions will receive it after few days.
[SuperSU] naik.aakash:
After successful root when i clicked on normal to update binary it keeps saying failed even i reboored device many times...what to do?
[SuperSU] shaggyskunk:
Did you Flash the zip from the OP?
[SuperSU] tcat007:
I get "need to update binary" about once a day. Click on the notification and it opens su, but nothing after that. I'm on 2.45, so wondering why I get that message. Installed 2.45 from zip in op.
[SuperSU] naik.aakash:
I flashed it when i was in recovery mode, i first moved zip file to ext sd card and then flashed it and was successful.

---------- Post added at 03:37 PM ---------- Previous post was at 03:32 PM ----------

http://xdaforums.com/showthread.php?p=57347794

This is the link where i got zip file and after flashing it i got supersu app and when i click on it keeps saying installation failed
[SuperSU] HdSht:
Hello guys :), I'm new here. Is it possible to flash SS over Paranoid Android since it's already rooted ? Ty in advance.
[SuperSU] gialakias:
Yes, no problem. You can even install it trough Google play. Or flash it after PA while still in recovery.

Sent from my Nexus 5
[SuperSU] HdSht:
Thanks a lot :). I asked that because some users reported problems after flashing SS on cyanogenmod and wanted to be sure that PA is safe.
[SuperSU] nick2503:
So I have installed CyanogenMod on my nexus 4 but the stick mount app won't work & hence OTG doesn't! It says to update the supersu version!

CM 12 already has supersu! How shall I update it?

Nexus 4

Franco(Sabermod) Kernel
[SuperSU] sparksco:
There is no USB otg on the nexus 4... The hardware isn't there to support it. Also who makes Franco SaberMod? I need to check that out for my nexus 5 :)
[SuperSU] TheDarkDefender:
http://xdaforums.com/nexus-4/develo...ernel-r211-t2858561/post55053022#post55053022

Nexus 4 supports externally powered otg only, and only if your kernel supports it. Stick mount explicitly mentions in the Playstore description that its not meant for n4.

What cm 12 has, is superuser and not super su.
[SuperSU] nick2503:
Stickmount does support nexus 4 as I have been using it on my stock Kitkat as well as lollipop since a very long time!
[SuperSU] TheDarkDefender:
Ok, I haven't tested it, but :

From Play:
[SuperSU] naik.aakash:
I've rooted my Samsung Galaxy Core 2 and after successful root i got supersu app. When i opened it, it said to update su binary, & i clicked to install in normal mode. But it keeps saying me su upgrade failed even i frequently rebooted device.

Plz check I've included device info as attachment

Sent from my SM-G355H
[SuperSU] baltics:
Flash the SuperSU 2.45 zip in recovery.
[SuperSU] danilo_scala:
thanks great work, i have one problem , I try to uninstall app system but not work, I do not know if it's my root (xperia z3) or app titanium or sd maid or super su
[SuperSU] juanpirulo:
If you are allready root try to mount rw in system partition, you can do it with es explorer or root explorer. Cheers
[SuperSU] danilo_scala:
thanks but how try mount, in root explorer and es file explorer mount rw but error ..
[SuperSU] doveman:
I have the same problem with my Lenovo A8-50 (A5500-HV) and 2.44. I posted a bug report in the thread here http://xdaforums.com/showpost.php?p=58539538&postcount=220

I tried flashing 2.45 but it still gives the same error when I open SuperSU.
[SuperSU] naik.aakash:
Sir i have flashed supersu 2.45 zip and problem still persists..plzzzzz help me...

It keeps saying installation failed, :(

Sent from my SM-G355H
[SuperSU] gorilla p:
If you're having issues even after flashing the latest zip, you may not REALLY have root.
[SuperSU] astuermer:
Not working on latest CM12 builds.
[SuperSU] jeozme:
Latest = 20150206?
[SuperSU] astuermer:
No last nights build.
[SuperSU] jeozme:
Ok. For me there is no problem. Lucky me :)
[SuperSU] sparksco:
I think it's been said before cm12 has a different version of superuser embedded in the ROM...
[SuperSU] i_mangesh94:
i used to update superuser everyday after rom update so i decided to flash superuser zip file so i directly uninstalled superuser which i installd from playstore and flashed superuser zip file n when i restarted phone the phone started to freeze so i tried to open su app i didnt opened n every app started to forced stopped.so i disabled it.and thn i found out that i have lost my root access from root checker app.plzzz help me how to get back root acess..anyone??
[SuperSU] naik.aakash:
Flash zip again , reboot and check...

Sent from my SM-G355H
[SuperSU] m4f1050:
SU binary update fails normal way on a few of my devices
[SuperSU] Verrocio:
Ghost mode

How do we set a permanent new custom ghostmode configuration (code) and completely remove the 1234 and SUPERSU ones ? :confused:
[SuperSU] Peninaa:
Alsamixer

Is granted SuperUser but whenever I change a value it does nothing. Dunno if this is the SuperSu or the Rom I tried.
[SuperSU] kamikaze702k:
I have root, but this app stopped appearing in my app drawer, apps ask for root access etc, but I can't open the app interface, I can uninstall from play store but when installing again there is no open option, PLEASE help as I want to change my settings and prompt delay time, I've tried re flash and 1234/5 code from dial pad, but nothing...

Someone PLEASE help it's frustrating...
[SuperSU] david72262:
Did you check in your ROMs settings
[SuperSU] doveman:
I'm afraid I don't know the solution but I recall the same thing happened to me (i.e. icon disappearing from app drawer) when I used the option in SuperSU to convert it to a System app. Maybe that will help someone advise you.
[SuperSU] Scurzmann:
Open your terminal emulator

Type su

Then type this

am start -a android.intent.action.MAIN -n eu.chainfire.supersu/.MainActivity

It'll open up supersu from being hidden.
[SuperSU] mrrocketdog:
superSU opened , prompted for update scripts , i hit o.k. , x'd out of terminal but didnt show up in app drawer. maybe i typed wrong or did/didnt have a space. will try again. thank you for info though.:good:

"all i can really do , is stay out of my own way and let the will of heaven be done"
[SuperSU] kingy9000:
You may have to manually go into SuperSU Settings and into Launcher Icon and change it from hidden. Hope it works.
[SuperSU] Chainfire:
Tested with SuperSU v2.45 and ElementalX 2.05 on Nexus 5.

Tried various settings, they seemed to stick. At some point, indeed setting to 128 in Aroma stuck to 256 in the app.

After flashing, I confirmed the READAHEAD variable in /system/etc/elementalx.conf remains set to 256. The issue thus occurs in recovery, and not in Andoid under SuperSU operation.

Why SuperSU version is of influence at all in this I don't know. I doubt su is being called in recovery, that would be stupid.

Either way, as the problem is created in recovery during Aroma flash, I am ruling this 'not a SuperSU issue' until more evidence to the contrary turns up.
[SuperSU] Ugur Kiyici:
Hello everyone,

I have HTC One M8 (INT) with MaximusHD rom.

Clearly, I have rooted my phone. I want to turn it S-OFF via Sunshine.

I have the problem which is Sunshine trying to gain root access and it's denied somehow.

I have SuperSU and I allow to Sunshine to do some tests.

I checked other apps and I have root access there was no problem about it.

After Sunshine's denied, I opened SuperSU and it said the code is need to be updated. But I have the latest version of SuperSU which is 2.45.

I don't know the problem caused by Sunshine or SuperSU.

Please help me about it. Thanks.
[SuperSU] kamikaze702k:
Tried but I get this

COLUMNS=60;LINES=46;export COLUMNS LINES;

tent.action.MAIN -n eu.chainfire.supersu/.MainActivity <

Starting: Intent { act=android.intent.action.MAIN cmp=eu.chainfire.supersu/.MainActivity }

java.lang.SecurityException: Permission Denial: startActivity asks to run as user -2 but is calling from user 0; this requires android.permission.INTERACT_ACROSS_USERS_FULL

at android.os.Parcel.readException(Parcel.java:1465) at android.os.Parcel.readException(Parcel.java:1419) at android.app.ActivityManagerProxy.startActivityAsUser(ActivityManagerNative.java:2171)

at com.android.commands.am.Am.runStart(Am.java:680)

at com.android.commands.am.Am.onRun(Am.java:270)

at com.android.internal.os.BaseCommand.run(BaseCommand.java:47)

at com.android.commands.am.Am.main(Am.java:76)

at com.android.internal.os.RuntimeInit.nativeFinishInit(Native Method)

at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:243)

at dalvik.system.NativeStart.main(Native Method)

1|u0_a65@m3:/ $

Ps I'm using i9305 spirit Rom, I've checked the Rom settings everywhere, nothing
[SuperSU] NovaSlim:
Thanks alot for taking your time to look into this :good:

What was the SElinux setting during those tests? According to the results of a few people running the same Rom as me, aroma would work totally fine with SELinux permissive+2.45, but if it is always enforcing the readahead cache setting don't stick.
[SuperSU] Dark3n:
Not sure if the exact same issue, but:

On CM based ROMs (with superuser not SuperSU), I had problems remounting when doing it via an own busybox.

"-vv" showed a permission denied error.

When using the /system/xbin/mount that came with the ROM it worked flawless though. You should try to remount once through an extra busybox and once through the mount binary that got shipped with the ROM. See if one works and one doesn't, reboot inbetween.

Doing it once with the default mount binary also fixes the problem until reboot.

Don't know yet why this happens.
[SuperSU] danilo_scala:
was busybox not install on xperia z3 .96 firmware (with root). I do not think I can do what you said friend, i try other busybox .. i please make guide .. sorry. thanks for listening
[SuperSU] Scurzmann:
That's because you didn't type su first.

su first and allow root permission before invoking that script
[SuperSU] Verrocio:
Chainfire ,

Can you please address my question about removing existing ghostmode codes and adding a new one. Please :rolleyes:
[SuperSU] Chainfire:
SELinux was enforcing. But it doesn't matter. The config file for ElementalX contains the wrong value, so it's not a matter of the setting not being applied correctly, so SELinux, SuperSU, etc, is irrelevant. The config file isn't written correctly by the installer ZIP / Aroma. The only way SELinux matters there is if SELinux in the recovery is set to enforcing, which it usually isn't.

Now, as the above makes absolutely no sense at all in regards to SuperSU versions or SELinux state mattering, for the sake of argument, I am going to assume there is actually a second issue unrelated to the config file being wrong (you should still however double check what the config file says in your case).

What I have noticed is that the configuration script is in /system/etc/init.d/, and is run by the custom userinit service, which executes /system/xbin/busybox run-parts. Unless the kernel actually comes with a pre-modified sepolicy, SELinux will block various parts of that script's execution.

The SuperSU daemon modifies SELinux policies during the launch of it's daemon in early boot. This policy modification will also allow busybox run-parts to work. However, obviously if you are running an SELinux Enforcing system and that command is run before SuperSU has patched the SELinux policies (or you don't have SuperSU at all), the script will still (perhaps partially) fail.

As part of the fix for Motorola devices on Lollipop bootlooping, SELinux policy patching occurs slightly later in the boot process in 2.45 compared to 2.40. It might be the case that the script is thus executed before the policies are patched.

This is the entire reason for /system/su.d/ (as documented here: http://su.chainfire.eu/#selinux-policies-supolicy), which does the same thing as /system/etc/init.d/, but guarantees SELinux policies to be patched before the scripts are executed. With older versions of SuperSU, you were in fact just lucky SuperSU was faster in patching the policies than busybox was in executing the script.

tldr? init.d is obsolete, stop using it on SELinux Enforcing firmwares. This is a bug in ElementalX for which the workaround has already been documented in my How-To SU guide, and this is pretty much a waste of my sunday afternoon :)
[SuperSU] Chainfire:
Can you log the SELinux audits from logcat | dmesg | /data/misc/audit/audit.log files, if any?

Note that some busybox and/or toolbox binaries require different syntax - isn't that just dandy ?

toolbox mount -o rw,remount /system (android 4.x)
toolbox mount -o rw,remount /system /system (android 3.x+)
toolbox mount -o rw,remount /dev/block/whatever /system (android 2.x)
busybox mount -o rw,remount /system
busybox mount -o rw,remount /system /system
busybox mount -o rw,remount /dev/block/whatever /system

Covers most devices. The /dev/block/whatever may have to match as well. The silliest part of this? The actual mount system call eventually executed ignores that parameter altogether.

Different syntax between toolbox and busybox versions is the primary reason you should never install busybox in such a way that it replaces the system toolbox links, you just don't know what's going to break, and in my experience it has been the cause for many issues with many root apps (either being developed against a toolbox system and breaking with busybox, or not uncommonly the other way around).

ROMs that come with busybox prelinked instead of toolbox? Kill it with fire! Yes, of course apps should be built in such a way it doesn't matter, but the reality is that many apps aren't.
[SuperSU] Chainfire:
I don't even understand the question.
[SuperSU] sgtEN3RGY:
So.. I was wondering if someone actually tried to see if the "ota survival mode" actually works.. Anyone?
[SuperSU] Verrocio:
In the description here >>> https://play.google.com/store/apps/details?id=eu.chainfire.supersu&hl=en

It says : "Launch from dialer: *#*#1234#*#* or *#*#7873778#*#* (*#*#SUPERSU#*#*)"

How do we remove these codes (1234) (7873778) and use our own ?