yashsingh1/xdaforums huggingface dataset:
[SuperSU] kingvortex:
Can you open the zip by other means (on your PC or with a file manager on your device etc)?

The zip may be corrupted if not. Try redownloading and disable any download managers etc.

Edit - As for losing root when SuperSu is updated; if you know this is going to happen, then why don't you disable auto update of apps instead of complaining here about it? There is no "force update" and it's hardly Chainfire's fault that you're regularly away from internet access, is it?
[SuperSU] claytonjn:
It sounds to me like the reason the zip isn't working in TWRP is due to a bad download. Check the MD5, it should be 69c4ca16a05acf4daae4063971bc9d49.

Also, as kingvortex mentioned, SuperSU doesn't force an update. One the app has been updated, it forces a binary update, but at that point there's nothing more to be downloaded. As kingvortex also mentioned, Chainfire doesn't auto-update the app. He simply publishes it to the Play Store, and it's the setting that you have set that determine whether an app auto-updates.

-Sent from my Developer Edition Galaxy S4 using Tapatalk
[SuperSU] cucolino:
htc one zip update error

Actually, I dont blame anyone for me being away from internet. But its annoying to find out you have no root when you need it. And I did disable auto update for it, but still lose root. Is there any other way to disable it other than in playstore?

As for the zip, I can open it with file manager. Tried to download twice...

I'll try to copy it from PC to the storage and apply it afterwards, if that might help....
[SuperSU] kemoli:
Install SuperSU into /system

thanks [MENTION=631273]Chainfire[/MENTION] for the app, is the best!!

to anyone that knows, i have noob questions :confused: :

i have a htc butterfly s rooted and s-off, when i Install SuperSU into /system, is the best to have it like this or is better to have like an app? and how can I undone this to revert to work like just an app? how can i unroot when is a system app?

thanks for your response in advance!! :)
[SuperSU] asdfasdfvful:
I honestly don't see a difference. Removing from system can be done with titanium backup. To temporary unroot, just tap the first check box. There is also a button for full unroot, though I've never used it
[SuperSU] Pons:
Pretty sure Titanium hides SuperSU and Superuser from itself.
[SuperSU] asdfasdfvful:
Lol big derp moment for me...

The person can always tree cleanup for réinstallation, as that installs to app data
[SuperSU] hosgor45:
Please help,

I have searched it but could not find definite answer.

When I am on recovery and try to reboot it says fix root (/system/xbin/su).

Do any of you have any solution?

Thanks in advance.
[SuperSU] Pkt_Lnt:
You have CWM? It is being stupid with a false warning. Choose NO.
[SuperSU] Pons:
What the post below me said.

I'd also install an updated recovery (if available for your device) that doesn't give false warnings.
[SuperSU] Mittaa:
Doesn't matter if you answer Yes or No! CWM Touch have screwed up several Samsung Firmwares for me in past! After recovery of nandroid, something was broken and I had to factory reset and ROOT again.

Now I only use TWRP and it work fine, and I can shift between Samsung Firmware and CM11 :good:
[SuperSU] QuBeX:
It is not working on my intel device ( lenovo k900 ) with jellybean 4.3 . The binaries are there, but the app doesnt recognize them. It used To work well on 4.2.2 x86 and 4.2.1 x86

Is it a compatibility problem?

Thanks in advance :)
[SuperSU] Super_Dork_42:
Have you tried flashing the zip in recovery? For some reason, updating through the play store doesn't update the binaries for me, but flashing the new version in recovery does fine.
[SuperSU] QuBeX:
The problem is that we don't have a custom cwm yet. Wue have to include the binaries and the apk manually in the system image and then flash through fastboot
[SuperSU] H377:
Hi All,

Could someone please help me?

I have a HTC One DUAL SIM. TEMP-Root works on my device so I can get root access within one ADB session. Is there a way to install the SU Binaries and APK using this ADB shell? I tried to go through the install script located in the SuperSU.zip but some commands like ch_con doesn't exist. I was able to make the dirs and copy the files chmod them but still cannot get it to work.

Any idea?

Many thanks in advance!

Or I cannot do anything without unlocking the bootloader and installing a custom recovery? I would like to just get root access... :)
[SuperSU] Kdio:
Master [MENTION=631273]Chainfire[/MENTION]

Just dropping here all my gratitude for yours development skills :D

While trying to theme TouchWizard ambients, SuperSU has been unbeatable. No matter what I mess within framework, yours app always looks amazing. ;)

Thanks for creating the iconic app that I always point to when trying to show to my users how ALL apps should be developed.

Nice regards.

.
[SuperSU] ricardo85x:
Great update.

Now I can mount a NFS with the help of busybox with su --mount-master

I can mount and browse the files with RootBrowser

But I can't see the files using apps that does not have root.

What can I do?﻿
[SuperSU] igoivo:
Empty entry appears in the app list every few days. Any attempt to delete or modify it results in the force close.

The only solution is to re-install SuperSU from GooglePlay. But it works for few days and crashes again.

PS: 4.1.2 stock at GT-N7100 (SGN2)
[SuperSU] Pons:
If you haven't already, can you try and capture a logcat or report via Play Store? I'll start looking for this issue as well, but that's the first I've heard of this bug.
[SuperSU] igoivo:
I've sent few GooglePlay crash reports already. As to the logcat, then I can only capture the force close event, but not the empty entry appearance since it's random.
[SuperSU] Frank Westlake:
The crash might be related to the blank name causing a null pointer exception while trying to delete it. After a crash see if you can ADB shell to '/data/data/eu.chainfire.supersu/logs' and read any logs with the application name missing from the file name.

Frank

SGH-I717(AoCP6.4), SM-N900V/MI9(dlV), XDA Premium
[SuperSU] igoivo:
Sure, and the precaution must be implemented in the SuperSU code.
[SuperSU] saprowling:
How come supersu doesnt appear in my App Drawer after flashing it via TWRP? But it grants me root access.
[SuperSU] spankymo:
are you using omnirom? if so, you can find it in the settings app.
[SuperSU] aavvaallooss:
Install it from Play Store
[SuperSU] Pons:
[MENTION=631273]Chainfire[/MENTION] since your flashable zip takes out Superuser, would you mind taking out Team Venom's Superuser as well? It's just odd that when installing apps from the Play Store they still give Venom's superuser info. The path is as follows:

/system/priv-app/VenomSuperUser.apk

Let me know if you need the apk or any other info.
[SuperSU] jazzruby:
[MENTION=631273]Chainfire[/MENTION]

Is there any (dis)advantage:

SDK_VERSION=$(grep ro.build.version.sdk /system/build.prop)
SDK=${SDK_VERSION#*=}

if [ $SDK -lt 19 ]
then
cp $COM/Superuser.apk /system/app/Superuser.apk
set_perm 0 0 0644 /system/app/Superuser.apk
else
cp $COM/Superuser.apk /system/priv-app/Superuser.apk
set_perm 0 0 0644 /system/priv-app/Superuser.apk
fi

https://android.googlesource.com/platform/frameworks/base/+/ccbf84f

-JR-
[SuperSU] Chainfire:
What is the Java package name? What do "su -v" and "su -V" return? Can I get the APK somewhere?

I don't see why SuperSU would require priv-app (though maybe for rebooting on HTCs?). As it is, the app expects it be in /system/app and is not aware of the possibility of being in priv-app. I have not tested it, but I think there might be issues if you put it in priv-app.

Also all superuser implementations and scripts use /system/app/Superuser. Deviating from that (as it seems TeamVenom has done) should not be done unless there's a good reason to, for compatibility reasons.

For the moment, don't this. I will revisit the issue when I have time to properly investigate it after my vacation.
[SuperSU] Pons:
su -v
Venom SuperUser v14
su -V
14

Shows up in the drawer as "Venom Superuser" and its package name is "com.m0narx.su" Apk is attached (pulled it from the ROM on my phone), or you could download their ROM and do the same. I don't know of where it's hosted by itself, if at all.

I'm not asking that you deviate away from it, just to add as part of your updater-script to remove their su (again, located at /system/priv-app/VenomSuperUser.apk). SuperSU works fine as is at /system/app, I just have to go in and uninstall theirs (after flashing yours), and then reboot so your description and everything else takes precdence. Some root apps didn't want to work with theirs installed, and yours flashed over.

Edit: belatedly I realize that you were talking to someone else. That's what I get for forum hopping at midnight. Off to sleep.

Edit edit: added su binary. Just remove the .txt
[SuperSU] shoey63:
I thought SuperSU was proprietary.

There shouldn't be any re-naming to "Venom Super user" or anything else for that matter :confused:

Edit: its obviously not SuperSU - can't even install it:p
[SuperSU] alwi:
Till now no body answer me guys

Still my supersu no saving my option please guys help me what to do...

After I put setting on properties and restart the app retain again to previous one...

Also when grant some apps again after while ask me again to grant...(check in list its therr for while then sudden not there..)
[SuperSU] Pons:
If you really want to try this app without installing a Team Venom ROM, try pushing it either to /system/priv-app or /system/app, then push the su binary (remove the .txt) and push to /system/xbin. Not saying this will work, nor have I tried it, but it might. This app might also be too tightly integrated into Team Venom's ROM, and it won't work.

Also bear in mind the inherent risk of trying a su management app from someone (either myself or Team Venom) you don't know or trust. Highly ill-advised. And I didn't post this app with the intention of having a bunch of people try it, just giving Chainfire easier access to it if he didn't want to download the 1 gig ROM.
[SuperSU] Frank Westlake:
It might be better to ask this in a forum for your particular device.

Frank

SGH-I717(AoCP6.4), SM-N900V/MI9(dlV), XDA Premium
[SuperSU] soralz:
Hi all, recently I flashed my P780 with Custom Vibe ROM, I can root it using Vroot. But seems like replacing the China Superuser app with SuperSU is kinda impossible, I've tried many methods but no go. Whenever I allow SuperSU to install the binary it always says installation failed and I lost root, must root it via Vroot again. Any idea?
[SuperSU] Pons:
I'm not familiar with that phone, but can you flash the supersu update zip in the OP?
[SuperSU] soralz:
Oh, that worked very great, now I got SuperSU. Haha lucky me I have CWM on my phone. :good:
[SuperSU] bhiga:
The method described here worked for me, though on an entirely different device...

Make sure you're not accidentally denying SuperSU permission - "choose 允许(means allow). (Should be the right side option.)"

EDIT: Looks like you got it sorted. :)
[SuperSU] soralz:
Yup, I did tried that before but doesn't work, flash the SuperSU file via CWM solve my problem.
[SuperSU] drawde40599:
What exactly is 99supersudaemon? A search didn't really bring up answer , I'm just wondering because one of my N5's have the script and the other dose not , there both running 100% identical Roms ,kernel and apps .
[SuperSU] alwi:
Continue Reading ....

It might be better to ask this in a forum for your particular device.

Frank

SGH-I717(AoCP6.4), SM-N900V/MI9(dlV), XDA Premium

But I think its software problem not from my mobile!!!

My mobile is galaxy note 3 4g ...

Ok then...

How to unistall the supersu!!!

When I try it give error message. ..

I want to remove it completely and install it again...(better unistalled manually)

Thanks
[SuperSU] Pons:
After reading and looking around, I'm fairly certain SuperSU can remain as a /system/app and doesn't need to be a priv-app. After all, SuperSU just manages and grants su permissions, but doesn't change any system level settings (or any settings) really. It just manages su permissions.

http://stackoverflow.com/questions/19868138/aosp-privileged-vs-system-app

Edit: I'm all about the Principle of least privilege. If an app (even a su management app) doesn't need something/a privilege to do its job, then it shouldn't have it.
[SuperSU] ayoubij:
anyone knows why when I flash aosp roms that have built in superuser, the superuser doesn't work with most root apps, whereas if I flash this superSU it works like a charm ?

For example with superuser that comes with aosp roms, titanium says that binaries wont make it work properly, and also for example if I want to uninstall a system app, it shows as if it got successful removed but it is still there.

So why is this can you explain please?

Thank you.
[SuperSU] nemofbaby2010:
Because supersu is just better
[SuperSU] Pkt_Lnt:
They are different apps from different developers; one is more actively developed for all ROMs where the other is just for CyanogenMod ROM.
[SuperSU] furtom:
Supersu icon gone

I can see this has been discussed, but none of the solutions I've found have worked in my case. I'm wondering if I'm missing something fundamental...

I installed OmniROM on my Nexus FLO 2013 today and flashed SuperSU 1.93. I then proceeded to use TB to restore a bunch of things including my SuperSU Pro licence.

All was well. Supersu was working fine as it always does, but then at some point during the day, the ICON (and only the icon) has been removed from the app drawer. I, therefore, cannot access the settings.

I say only the icon, because the tablet is still rooted and Supersu is still installed and working fine. If a new app requests root permissions, the usual Supersu dialog box pops up and works as always. I took a peek in /system and the apk is still there. I tried installing again from suspersu.apk in /system. It installs fine, but then the "open" button is grayed out. Only the "done" button is functional.

The first thing I tried was to reflash Supersu 1.93. This has no effect.

Of course, since I flashed it, it cannot be uninstalled via TB, Google Play or any of the other usual means, rooted or not.

I'm out of ideas. Most of the search results I've found involve reinstalling/reflashing the app. This seems to have worked for some people, but it hasn't here. I'm wondering if I should flash a downgrade or something like that?

Anyway, that's all the info I can think of. Sorry if I'm repeating old material. Any input would be appreciated.
[SuperSU] jazzruby:
SuperSU has Settings > Customization > Launcher icon where you can change the icon; one of them is to hide from the app drawer.

Run this from a root(su) terminal to bring up the UI:

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

-JR-
[SuperSU] Pons:
That, or try dialing one of these from the phone app:

*#*#1234#*#*

*#*#SUPERSU#*#*
[SuperSU] egingell:
Or just: am start eu.chainfire.supersu

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] Pkt_Lnt:
Like CyanogenMod, Omni places the controls in Settings and hides the icon, you can get to it there.
[SuperSU] furtom:
Thanks for your answers guys.

Well, I have a tablet, not a phone, but I hope someone else can use this.

Thanks. I did JR's code above and it worked. But then I realized...

Yes. As I thought. I was missing something fundamental. Supersu was there all along in System settings, right below Developer Options! DOH!

I could have sworn the icon was there earlier today, but apparently not. The mind plays tricks, it does.

Thanks for all the replies! I appreciate your time.
[SuperSU] ayoubij:
Yes true but shouldnt the one that comes with CM work with CM :p

I dont like the idea of having two superusers. I have bought superSU Pro but is there any way to delete the rom superuser?
[SuperSU] kien_vip:
i am using solid explorer to browse file and allowed by supersu. then i change into "deny" but i still can use solid explorer to access root. get same problem with other app. seem supersu not take effect immediately. then i must reboot or wait for few hours to take effect. i am using 2.3.6 GB. How to make SUpersu take effect as soon as i change permisson. sorry for my bad english
[SuperSU] Pkt_Lnt:
It is not a question of superuser working with the rom, but it must work with the apps correctly. Reports of problems with the CM superuser are frequent. I do not use CM, and my only experience is with the old superuser by ChainsDD and this SuperSU.

If you flash the SuperSU zip linked in the first post from recovery, it should remove the CM superuser and install SuperSU as a system app.
[SuperSU] goodoane:
Hi Chainfire,

Galaxy Note II just get a leak of 4.4.2 and the supersu.apk failed to work on this leak build. I will try to explain what is happened when I try to access the supersu from app drawer is force close. When an application request supersu access the toast show up and I can grant su access with no problem.

So this is very strange. here a short logcat about this problem. I hope that you can fix this. Thank you.

Link for the leak rom: http://xdaforums.com/showthread.php?t=2669492
[SuperSU] mindmajick:
Where is this note 2 leak?!

I can't find it anywhere

-》Sent from my mind to your screen.
[SuperSU] guycan:
Where's that leak i also would like to know cause I dont see it anywhere. .. google search and nothing

SGNote2
[SuperSU] goodoane:
Please stop the off topic (

do not hijack

) this thread about note 2 4.4.2 leak I updated my original post.
[SuperSU] Frank Westlake:
If you are a programmer it might help if you know the values in 'android.os.Build'.

Frank
[SuperSU] goodoane:
No i'm not a programmer any help it will be useful. I believe is about a null point that is in suspersu apk but how come that it didn't happen in other builds of samsung 4.4.2KK?...
[SuperSU] Frank Westlake:
Then my guess was probably a bad guess.

Frank
[SuperSU] zolaisugly:
Can anybody offer any help..... I seem to have lost root, I have a working recovery yet when I flash the su update zip,I still get no binaries not installed.

I am running 4.3, Sony sp.
[SuperSU] egingell:
If you lost root, you may need to reroot. Installing or flashing this will not do that.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] kingvortex:
...

Flashing the zip from recovery should root the device. That's exactly how I rooted my phone.

What do you think most rooting methods do, apart from place the su binary in the correct place? You know, like flashing the zip does. :)

Something else must be wrong with his phone.
[SuperSU] mcgi5sr2:
building into rom source build

Hi sorry for what seemed to me like a rookie question, until I couldn't find the answer.

Is there a way of adding this to my local_manifest and building it with the rest of android? I have found how to do it with Koush' open source supersu but Chainfires is a favorite among the users....

I checked the github to no avail :'(
[SuperSU] Pons:
You can't compile it, but you can download the zip, extract it, and place the appropriate files in the appropriate locations. It's a little more involved, but look at what CM does with Terminal Emulator.
[SuperSU] mcgi5sr2:
Thanks for this, saved me a whole evening of failed discovery!
[SuperSU] Pegajoso:
I have the same problem.

But I'm using a S3 LTE (I747M) 4.3 Stock, CWM installed.

I try the method to re-root + flash the new zip and sometimes root works, sometimes fail to work.

And as you can see in the pic, I have root stuff working... But now my root is broken, btw KNOX is disabled..
[SuperSU] brolee93:
Please chainfire can you help us?
[SuperSU] Pons:
From his Pry-Fi thread:
[SuperSU] Thomas_BA:
It seams you have root but no write access to /system/..

Restart you phone into recovery mode, install Buysbox and update the binaries of SU. Restart your phone in normal mode.

I had this problem in 4.2.2 (recovery mode allows write access in this case, it is not a real recovery mode), and solved it this way. Perhaps it works in 4.3.

4.4 is different regarding rooting.
[SuperSU] dbzgod:
Sounds like since its been pre rooted that SuperSU is running as a system app.

I had a similar problem when my Note 2 updated to 4.3, the root binary was working but the SuperSU app would repeated crash over and over constantly in a loop. I didn't figure out what exactly caused it, figured it was something programmed into the firmware however I did fix it.

I had previous installed SuperSU as a system app and this is what caused the constant crashing, I removed SuperSU as a system app and then reinstalled it as a normal one and everything worked properly, I did this via ES File Explorer, mounted the system directory as writable and deleted SuperSU, then rebooted and reinstalled from the playstore as a normal app.

EDIT: Since deleting supersu from the system directory is not a proper way of uninstalling an app, you might run into the problem of when you go to install it from the play store it might already show it as "installed" and does not let you redo it, if this happens, then use the SuperSU zip and install via custom recovery.
[SuperSU] egingell:
As long as you reboot, there are no ill effects other than lingering data in its /data directory.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] caspboy:
[MENTION=631273]Chainfire[/MENTION]

Sorry to blaze you thread, but I got a problem. See I just compiled cm11, which is working fine. But I wanted to add some tweaks to it before I release it. Unfortunately, the updater-script turns out to be in "set_metadata" instead of "set_perm", which I know nothing about. I need to set some permissions for the extra files and folders I've added, and the permissions are:

And some more like that. But I don't want to mess up the updater-script. Can I just add these perms in between or does the updater-script only read "set_metadata" lines?
[SuperSU] Pkt_Lnt:
Read post #4960 above.
[SuperSU] dannyella:
How can I disable supersuser toast?
[SuperSU] Pkt_Lnt:
Superuser settings, uncheck notifications if you mean SuperSU.
[SuperSU] Heisenberg:
SuperSU/Settings/Notifications

Sent from my Evita
[SuperSU] goodoane:
SuperSU is in data not in system and is not loop FC just FC when I try to access the application, if I don't touch SuperSU no problem. I think it also a new form of protection in kernel.
[SuperSU] bhiga:
I had this symptom when I did a clean upgrade to 4.2.2 on my GS3. I had to install an older version of SuperSU and let Google Play update it. All was fine after that.

-= this post enhanced with bonus mobile typos =-
[SuperSU] Pons:
Have you tried flashing the update zip in the OP?
[SuperSU] goodoane:
Yes I did try all version old and new and market. This build is strange. I also checked the kernel ramdisk and it may have implemented a new security feature who knows.
[SuperSU] zygzoo:
pls fix the issue on leaked N7100XXUFNB4 (android 4.4.2) for samsung galaxy note2.

thanks
[SuperSU] kingvortex:
1. Read/search the thread before posting. This has been reported multiple times already.

2. Just to reiterate. Read/search the thread before posting. If you did, you would know that Chainfire is on vacation and therefore won't be fixing anything.

3. Bug reports should be accompanied by logs at all times or there's no point reporting them.
[SuperSU] muniz_ri:
The latest 4.4 OTA for I337 deletes and reinstalls the stock install-recovery.sh unrooting the device. Is there an alternative process that can be modified to launch daemonsu at startup at keep root when taking the OTA? Thank you.
[SuperSU] doclorenzo:
Same here, note 2 with stock 4.3 knox removed, bootloader mj5, rom mj9.

Root randomly lost on reboot, rerooting with recovery, but only stays rooted for a couple of reboots, then gone again. Supersu is not removed.

How do we find out what removes root?

Is there a log to do this?
[SuperSU] Prasad:
I flashed "UPDATE-SuperSU-v1.93.zip" on my T-Mobile HTC One from CWM Recovery using ADB Sideload and it says "There is no SU binary installed" upon launching SuperSU. Please advise.
[SuperSU] Pons:
Try just flashing the zip via recovery, instead of sideloading it.