yashsingh1/xdaforums huggingface dataset:
[SuperSU] slidesear:
I upgraded to the newest Wanam (the old one was disabling Knox at boot) and my Android System root prompt went away.
[SuperSU] sandroidnz01:
Damn.

I flashed CM10.2 recently.Was using it for 3 days then wanted to

try out the CM 11 KitKat today.Using Nandroid backup it prompted

to update the SuperSU ver 1.75 which I downloaded.Asked for root

right,granted.Reboot.

No more root!!!

WTF?

Samsung Galaxy Note2 N7100

CM 10.2
[SuperSU] Rinoceros:
Problems with reading this forum?

The answer is already above you or on the page before this one.

Please, do a comprehensive search before you post messages like this!
[SuperSU] nicods:
Uploaded the only one I could find on dropbox and sent the link to you via PM. I triedto get the other i mentioned, only available through Samsung App Shop, but i couldn't find anyone with a samsung device willing to help me.

Thank you again.
[SuperSU] Chiddy_:
I cannot find the temporary unroot menu in SuperSU,which used to be there previously. I really need this. I posted this on this thread some weeks ago,but got no reply. [MENTION=631273]Chainfire[/MENTION] Please help.
[SuperSU] sandroidnz01:
My sincere apologies mate.Was able to get back root after

uninstalling super su 1.75.

Redownloaded busybox ran it and sweet .
[SuperSU] meckipower:
....will not work for me, because im not able to deinstall SuperSu, System will not allow....must reinstall 1.69.....im also on the latest InsertCoin
[SuperSU] ogre_x:
I can't unzip 1.75 with 7-zip on windows. Anything strange in the zip - format?
[SuperSU] Chainfire:
Thanks. Is it perhaps possible we chat (type, not voice) live through hangouts (PM me your hangouts name/email address) or IRC ?

I want to figure and solve this issue asap.
[SuperSU] MiddleMan33:
v1.76 fix worked for me. Flashed using TWRP. Had updated to v1.75 from v1.69. I'm on InsertCoin v6.0-2. :good:
[SuperSU] Phil3759:
[MENTION=631273]Chainfire[/MENTION]

Just merged SuperSU into CWM in my new recovery mod versions. I just pushed the updates for i9300/i9505

It works ways better than open source superuser for TW ROMs

Hope you keep a big effort on maintaing the su binary size the lowest possible while taking your pleasure on the superuser.apk ;)

Big thanks for your tech support :good:

I will push commits to my github asap with full credits

Best regards
[SuperSU] Yenkazu:
Just deselect Enable Superuser from SuperSU setting
[SuperSU] Chiddy_:
Thanks a lot! It worked!!!
[SuperSU] SaddleTramp:
beta 1.76 fix worked

Beta 1.76 fixed my limited root issue on rooted moto RAZR HD x926. Unlocked bootloader stock 9.30 system.

Sorry it took so long for me to get a chance to try it out and report back.
[SuperSU] stfudude:
My setup :

Nexus 7 2013, stock KRT16S, rooted 1.76 beta (same issue on 1.75)

Error :

Shown in attachment.

Output :

printenv

mount
[SuperSU] aydc:
Full Unroot option doesn't work properly anymore. I used it to remove root after I've done using root to change some things. My work email uses an app called Good for Enterprise which bans me if I'm rooted.

Up until latest versions of SuperSU, full unroot always worked. But now, I guess it leaves some files behind, since my app keeps detecting root even after I've selected full unroot.
[SuperSU] Sleepy!:
[MENTION=631273]Chainfire[/MENTION]

The su daemon is one of my biggest wake locks on the Nexus 7 LTE running KRT16S, with SuperSu 1.75....

Should this happen, or is this a bug?

Sent from Tapatalk, using Tapatalk
[SuperSU] Chainfire:
It's not actually daemonsu, it's the app that is calling su - app id 110:

ps | grep u0_a110

^^^ I think running that from an adb shell will show you which app it really is.
[SuperSU] abdozoon:
Wrong thread. Sorry.
[SuperSU] defim:
[MENTION=631273]Chainfire[/MENTION]: thanks for fixing the white bacjground with black theme in the current version.

But another bug i also reported is still there: On pin input fiedl, the numbers don't change back their deign to "ontouched", see attached screenshot
[SuperSU] ChungHung.Chen:
I've encountered same problem after v1.69 in Win7 x64 + 7-zip.

Also failed to install using BMM in Moto XT910 (CWM recovery).

Both show extract fail messages.

But installation works in my Nexus 7(2012) w/ TWRP 2.6.3.1.

Is this normal after v1.69?
[SuperSU] Chiddy_:
You could uncheck the "Enable Superuser" checkbox instead of unrooting. This prevents apps from recognising that you have root.
[SuperSU] Chainfire:
There's really no way for me to know what is going on here. Nothing has changed in the unrooting procedure between these versions, though.

I can't replicate this. Exactly when is this? When you open a PIN protected app, when you open SuperSU, everytime it pops up? What is your exact device and resolution?

Nothing has changed in the ZIP format since v1.69 ... and WinRAR opens it just fine ?!
[SuperSU] aydc:
Somehow some root binaries were left over after the unrooting. I removed them manually and now the app that I mentioned cannot detect root again. Maybe it was a one time problem that somehow happened just once. I'll go through this again next time I flash a new ROM and if the problem persists, I'll report here with more detailed info.
[SuperSU] Chainfire:
It would be helpful if you actually listed *which* root binaries were left over ... :)
[SuperSU] aydc:
At that point I had already unrooted my ROM, so the only way that I knew was to go to TWRP and use the file manager in recovery. I saw a folder called 'superuser' at the top level. In the folder were some binaries like 'su' and some scripts and such. Unfortunately I forgot to take note. :) I just deleted everything.

If SuperSU doesn't open a folder called 'superuser' at the top level, it might be left over from another root like Koush's or some kernel that autoroots maybe. If it happens again, I'll report here with extremely detailed info. :)
[SuperSU] Chainfire:
Right - thanks.

That could well be, btw, if you've rooted with Superuser or CWM SU, SuperSU will not clean up those files it does not actually use itself. It only cleans up it's own files.
[SuperSU] Chainfire:
By the way if anyone has any more of these CPU run-away daemonsu processes, let me know. There's some stuff I want to test out with that.

I would expect the CPU use to be in "daemonsu:X:Y" process, not "daemonsu:X", so need to figure out what that's about. It's probably just normal, but there may always be a bug somewhere ... :)
[SuperSU] Liideri:
Same here after installing latest 4.3 build in Galaxy S3 (i9300, int. version). Installed it with Odin, did factory reset, rooted with latest CF-Root and it appeared that root privileges was gone. Even with Beta 1.76 it gives the "missing SU binary" announcement and closes app immediately.
[SuperSU] lolomolo:
Unfortunately same story here with nexus 7 2013. And lost my root privileges. And what ever I did it is not come back..

Twrp

Krt16s

Cf 1.75
[SuperSU] Liideri:
Installed latest LiteGX custom kernel (v3.2.0), re-flashed Beta 1.76, wiped both cache and dalvik cache and now it seems to work again. At least SuperSU ain't complaining about missing SU binary and AdAway let's my phone update latest hosts file. Also terminal emulator gives hastag (#) after hitting su command so it seems that root privileges is fine again.
[SuperSU] ChungHung.Chen:
I've tested with WinRAR 5.0 x64 and works well.

7-zip can open zip file to view contents but error when extract/test them.

Messages shows "Unsupported format".

Same with CWM w/ BMM, looks like it can't extract at all.
[SuperSU] jazzruby:
>unzip -t UPDATE-SuperSU-v1.75.zip
Archive: UPDATE-SuperSU-v1.75.zip
signed by SignApk
file #1 (META-INF/MANIFEST.MF):
mismatch between local and central GPF bit 11 ("UTF-8"),
continuing with central flag (IsUTF8 = 1)
testing: META-INF/MANIFEST.MF OK
file #2 (META-INF/CERT.SF):
mismatch between local and central GPF bit 11 ("UTF-8"),
continuing with central flag (IsUTF8 = 1)
testing: META-INF/CERT.SF OK
file #3 (META-INF/CERT.RSA):
mismatch between local and central GPF bit 11 ("UTF-8"),
continuing with central flag (IsUTF8 = 1)
testing: META-INF/CERT.RSA OK
file #4 (META-INF/com/google/android/update-binary):
mismatch between local and central GPF bit 11 ("UTF-8"),
continuing with central flag (IsUTF8 = 1)
testing: META-INF/com/google/android/update-binary OK
file #5 (META-INF/com/google/android/updater-script):
mismatch between local and central GPF bit 11 ("UTF-8"),
continuing with central flag (IsUTF8 = 1)
testing: META-INF/com/google/android/updater-script OK
file #6 (arm/chattr):
mismatch between local and central GPF bit 11 ("UTF-8"),
continuing with central flag (IsUTF8 = 1)
testing: arm/chattr OK
file #7 (arm/su):
mismatch between local and central GPF bit 11 ("UTF-8"),
continuing with central flag (IsUTF8 = 1)
testing: arm/su OK
file #8 (common/99SuperSUDaemon):
mismatch between local and central GPF bit 11 ("UTF-8"),
continuing with central flag (IsUTF8 = 1)
testing: common/99SuperSUDaemon OK
file #9 (common/Superuser.apk):
mismatch between local and central GPF bit 11 ("UTF-8"),
continuing with central flag (IsUTF8 = 1)
testing: common/Superuser.apk OK
file #10 (common/install-recovery.sh):
mismatch between local and central GPF bit 11 ("UTF-8"),
continuing with central flag (IsUTF8 = 1)
testing: common/install-recovery.sh OK
file #11 (x86/chattr):
mismatch between local and central GPF bit 11 ("UTF-8"),
continuing with central flag (IsUTF8 = 1)
testing: x86/chattr OK
file #12 (x86/su):
mismatch between local and central GPF bit 11 ("UTF-8"),
continuing with central flag (IsUTF8 = 1)
testing: x86/su OK
At least one warning-error was detected in UPDATE-SuperSU-v1.75.zip.

-JR-
[SuperSU] osm0sis:
[MENTION=631273]Chainfire[/MENTION], I'm working on an "update-binary" shell script for a project of mine but I can't seem to get the signed zip to unzip in TWRP. The unsigned zip unpacks fine, but the signed one gives a "unzip: zip flags 1 and 8 are not supported" error. Your signed SuperSU zip, on the other hand, unpacks just fine..

Could you please share what signapk.jar are you using that works around this issue, or if there's some other trick? Thank you in advance. :)
[SuperSU] Chainfire:
Can you attach the binary you used for testing? Mine just outputs all is fine.
[SuperSU] ogre_x:
I tested myself with the unzip binary in cygwin on windows with the same errors. Can test it on os x and Ubuntu later tonight.

What are you creating the zip with? Android sdk? What platform?
[SuperSU] jazzruby:
Windows binary - UnZip 6.00 of 20 April 2009, by Info-ZIP

unzip.exe - md5: dfa534dd64d9783ab688e9febc76f1ae

unzip.zip - md5: 3092f656d587cab986e8ea3da851ec3d

-JR-
[SuperSU] jazzruby:
Just copied the UPDATE-SuperSU-v1.75.zip (unmodified) to my Nexus 7 and ran it through ZipSigner then copied the -signed.zip back to laptop:

unzip -t UPDATE-SuperSU-v1.75-signed.zip
Archive: UPDATE-SuperSU-v1.75-signed.zip
testing: META-INF/MANIFEST.MF OK
testing: META-INF/CERT.SF OK
testing: META-INF/CERT.RSA OK
testing: META-INF/com/google/android/update-binary OK
testing: META-INF/com/google/android/updater-script OK
testing: arm/chattr OK
testing: arm/su OK
testing: common/99SuperSUDaemon OK
testing: common/Superuser.apk OK
testing: common/install-recovery.sh OK
testing: x86/chattr OK
testing: x86/su OK
No errors detected in compressed data of UPDATE-SuperSU-v1.75-signed.zip.

Now unpacks in 7-Zip

[MENTION=4544860]osm0sis[/MENTION] - or if there's some other trick? - ZipSigner quick on-device zip signing.

https://play.google.com/store/apps/details?id=kellinwood.zipsigner2

-JR-
[SuperSU] Chainfire:
I could find a proper signing tool that work the way I needed it to work on my Windows setup, so I hacked together some code that modifies the relevant zip-headers, and then replaces the full-file signature with the correct one ... hackjob.

Please test attached ZIP and let me know if that fixes the issue
[SuperSU] ChungHung.Chen:
Hi,

It's worked with 7-zip now.

Should I test it with CWM ??
[SuperSU] Chainfire:
Yes please
[SuperSU] osm0sis:
Can I has? I really want to add zip signing to this project. :)
[SuperSU] radziop:
Hi everyone!

I have really strange issue with SuperSU and Android 4.4.

On my N7/12 SuperSU is working without problems with 4.4

However on my HTC One I've lost root. I was trying to reflash SuperSU zip but without success. I was trying to uninstall update - no results (my phone is hanging on boot animation when I remove update). I was trying to use SuperSU 1.75 and 1.76 beta. Any ideas?

UPDATE

It works! After restart it started working ;) I don't know why - magic :D
[SuperSU] Trunkam:
hi all

i searched but was not able to find a solution..

i tried to install superSU to substitute superuser (in CM11) but once i install supersu root disappear and so i cannot freeze or delete superuser..

am i missing something? (that is possible obviously..)

thanks
[SuperSU] ChungHung.Chen:
I've encountered some problem in switch back from safestrap(TWRP) to BMM(CWM).

I'll test if I can switch back.
[SuperSU] DrTofu:
This one, Cubovision.
[SuperSU] kreindler:
where is the 1.75 zip

I cannot find the zip for 1.75.... could u pls help? just the apk, but i need the flashable zip pls
[SuperSU] Chainfire:
Well, you've at least missed mentioning which device you are using.
[SuperSU] Chainfire:
It's linked in the first post ...
[SuperSU] osm0sis:
In all seriousness, would I please be able to have your zip fixer? Hack or no hack it sounds like the easiest way to both sign zips and have them extract correctly from the recovery commandline when using a shell script as the updater-binary. I greatly appreciate your time and consideration. :fingers-crossed::good:
[SuperSU] kreindler:
me = blind

ok. now I know for sure! I need glasses! :)) thx
[SuperSU] defim:
I'm using a Motorola Defy+ with Android 4.3.1 (by Quarx@XDA). Resolution is unchanged, I think 240? The numbers have not long this wrong design. So I don't know if supersu updates caused it, or my update from Android 4.1.2. I noticed it as an app requested root permissions (screenshot taken with Xposed)
[SuperSU] Trunkam:
Sorry You are right!

hi all

i searched but was not able to find a solution..

i tried to install superSU to substitute superuser (in CM11) but once i install supersu root disappear and so i cannot freeze or delete superuser..

I got SGS 3 i9300 with cm11 unofficial temasek

thanks

tapatalked..
[SuperSU] Chainfire:
Maybe. Either way, need to hear back from [MENTION=3313632]ChungHung.Chen[/MENTION] to see if the latest adjustment works on his device.

Should be fixed next update (probably today)
[SuperSU] danivancouver:
Hi, I downloaded the zip version 1.75, to put it in my Rom, but the zip is corrupt, I have fallen several times, podesi check?

Best regards
[SuperSU] c-dric:
The new version of Zenprise (Worx) detects root even if we hide it....

The previous version (Connect) didn't detect it....

https://play.google.com/store/apps/details?id=com.zenprise&hl=fr
[SuperSU] ChungHung.Chen:
I've tried for few hours, BMM still can't install successfully.

I'll keep try but maybe someone with moto devices can help for test.

BTW, TWRP has no problem at all.
[SuperSU] zymphad:
Does anyone have a link to a guide on how to replace SuperUser with SuperSu? I'm building roms and would like to replace the superuser with supersu. Very new to building roms, and been just following guides to do it.
[SuperSU] danivancouver:
Thanks, I downloaded 1.8 file and all good.
[SuperSU] Chainfire:
SuperSU v1.80 release notes - https://plus.google.com/113517319477420052449/posts/QhrEdeJ3nqQ
[SuperSU] meangreenie:
Weird I just updated to 1.80 on nexus 4 kitkat via play store. On reboot half my apps rebuilt their dalvik.
[SuperSU] polobunny:
Thanks for the continual support and good move on the part of the plumbers. Are you looking at a lot of damage of your stuff? Sucks to be you and all the people under it. Got a similar situation in the past with my condo and it was absolutely awesome having to deal with insurance.
[SuperSU] Trunkam:
Problem still present with 1.80 version..

Once I install superSu and reboot root is no more present.

Is strange also because seems that happen only to me.

tapatalked..
[SuperSU] Chainfire:
I've flashed the ROM you said you were using on my device and installed it and it works for me... make sure that under Settings->Developer Options-> you have root enabled.
[SuperSU] sbiriguda:
Bug report (1.80)

Chiming in to report a particularly nasty bug with the PIN entry dialog.

I'm running 1.80 on a Nexus 7 2013 LTE with stock KRT16S and the PIN dialog is rather schizoid: it works once, maybe twice, then it starts flashing in and out of existance, both in-app and when granting access to 3rd party applications.

I managed to capture a log dump while the issue happens, and it seems it's mostly related to device orientation changes. The first WindowManager error happened right after I closed SuperSU, while the View leaks happened when I managed to break out of the "flashing UI" loop by pressing the back softkey at the right time (if you press it when the PIN entry dialog is not showing up it will be logged as an unhandled key press, go figures...).

The problem is that this bug allows users to bypass the pin entry dialog on the application entirely: just change the orientation, hit one of the tabs and you can perform any action, ranging from clearing the logs, changing application behaviour and wreak havoc in the Settings tab (to those concerned with the security implications of this report: I contacted Chainfire beforehand and he told me to log the bug here for reference).

There is another issue: sometimes (especially in applications which force the orientation to landscape) even the grant/deny dialog would flash in and out of existance until the system declares that SuperSU is experiencing an ANR and offer to kill it.

I disabled PIN protection for the time being, but this still doesn't solve the flashing "grant/deny" dialog issue.

--ADDENDUM--

If I kill SuperSU after the flashing "grant/deny" issue, the dialog will pop straight up and working. Weird.
[SuperSU] Vetala:
deleted
[SuperSU] Chainfire:
@everyone please try replicating the below issue, as I don't seem to be able to ...

Does the PIN dialog work properly after the kill as well ?
[SuperSU] sbiriguda:
Yes, but only once. As soon as the orientation changes or the app is closed and reopened everything goes south again.
[SuperSU] eradicator006:
I'm really wanting to switch to supersu from superuser and I cannot get it to work on my HTC One GPE 4.4. I even had this problem on 4.3. Supersu just won't work.

Before I install supersu I make sure to remove all traces of superuser. I then install supersu via twrp. No errors there. Once I reboot I do not see superuser in the application drawer.
[SuperSU] blaz1nr:
Go to system app find su app click on it to reinstall. I've been doing this all day.
[SuperSU] tweakradje:
Hi Chainfire, I posted a question here about su password protection.

In short, when su binary is called from the shell is it possible to protect it with a password?

Bedankt.
[SuperSU] eradicator006:
That didn't work. The app is visible now but now I get "super su has stopped responding". None of my root apps work either.

Thanks though.

EDIT: Did some further testing and found out that running su from android terminal emulator or adb shell causes the shell to hang. Doing a ps does in fact show daemonsu running so that's seems normal. I cannot open super su app without it quitting unexpectedly. I think I'm going to have to go back to superuser for the time being. This isn't making any sense to me.
[SuperSU] yaonos:
It may be the same issue many of us encountered after applying the 4.4 OTA. You may want to try the solution given here :
[SuperSU] Braxos:
Chainfire I don't know if this is from ROM or su but once I find it on supersu I post it here.

When I flash supersu 1.69 1.75 1.80 and I grant always root rights to applications the timer is gray when now I download the pro from Google play store then the always grant stays but now I can change the timer to grant root rights. Not a big issue since it doesn't do anything but you never know.

ROM omni 4.4 experimental n7000 on version from (22-23-24-25-26) .11.13
[SuperSU] tovarish:
I have a really strange problem. I have the latest (1.80) version that I installed via google play as well as cwm in a galaxy s4 active stock. The problem is that some apps get root access or the prompt but many are silently denied. The setting Enforce Permission is off. Nothing is shown in the logs. I can even get root using "su -" in adb shell.

How can I debug this problem? One of the apps that is silently denied root access is your own adbd-insecure.
[SuperSU] Braxos:
OK I tried but no flashing at all. The only I could find is on file explorer when I try to give root rights to it and I press back key , on first attempt it doesn't give it but on next one after back key is pressed it says root access granted be careful and the rights are given this can be done even you have pressed grant and you are on the pin window and you press there the back key

Oh and I can't give root rights on apps for limited time they have root right till reboot even I gave them a 1 minute or one time root rights.

I tried even forget on supersu but still the apps have full root access. BTW the file manager had deny as root access but still could with using back key to give it access.
[SuperSU] ykumar00:
OHMYGOD same problem here. i was flashing 4.3 factory image in order to flash 4.4 OTA. Had the same problem you had.

Flashed The Factory image files again, flashed latest TWRP with fastboot flash recovery recovery.img

Flashed SuperSu 1.51

Working Fine!
[SuperSU] ChungHung.Chen:
Finally I've got my BMM recovery installed.

Both test zip and 1.80 zip are not work.

I've found that update-binary and updater-script were changed since v1.60.

Perhaps this is the root cause?

EDIT 1 : CWM is 6.0.x.x version

EDIT 2 : Both test-utf8.zip & 1.80 zip is ok in Win7 + 7-zip now.
[SuperSU] eradicator006:
That didn't really help. When I chose uninstall updates supersu disappears completely. I'm just going to stick with superuser. I've wasted 4 hours trying to get this to work. I've never been able to get supersu working on my htc one gpe so I don't think it's anything with the 4.4 OTA. On 4.3 I got the same behaviour.

I do appreciate the help I did receive. Thanks again.
[SuperSU] Daniol71:
How to remove PIN

Hi, I have SuperSU Pro and have PIN protection enabled, but I can't seem to find a way to remove it, does anybody know how to do it?
[SuperSU] Braxos:
Enter supersu then go to settings on PIN press it leave blank press OK. Done
[SuperSU] azeem40:
I am having issues installing the SU binaries for my device (S2 SGH-i777). Whenever I click TWRP/CWM when prompted to update binaries, it just closes the app and nothing happens. My phone doesn't reboot as it should. I heard of a suggestion that said to reboot into recovery manually if this happens, but nothing happens. I have OmniROM installed (I think you are part of the development team for it). Any help is appreciated.
[SuperSU] TrenchKato:
Try the normal method
[SuperSU] adrman:
All 4 of my devices, 1 hammerhead, 1 mako and 2 grouper updated perfectly via Play Store/normal method. Damn that makes me hungry. Time to order some sushi. :D
[SuperSU] azeem40:
My problem was that I didn't use the zip file.
[SuperSU] vinsbelmar:
[2013.11.26] SuperSU v1.80

SuperSU on my s3 its working fine since v.1.80. [MENTION=631273]Chainfire[/MENTION] Thanks for your work!

Enviado desde mi iPad con Tapatalk
[SuperSU] c-dric:
Same with the 1.80 version.

Do you know how this software detects root ?
[SuperSU] YHWHF:
I wonder, have you spotted 'bug' as in version 1.69 for the language issue or is everything right?