yashsingh1/xdaforums huggingface dataset:
[SuperSU] Brds7t7:
Totally agree there mate. I'm always careful about what I install and i always read the permissions carefully first.

It's just a pity not everyone is as careful. My friend has learned a valuable (and expensive) lesson.

Anyway with regards to Avast and SuperSU, I'll keep an eye on it. If it does start throwing up warnings on my phone then I'll uninstall it until it's fixed.

I can live without Avast. SuperSU is essential though! ;)

Sent from My Calculator!
[SuperSU] Tungstwenty:
That's in theory, yes. You should look at the permissions and not install apps that use SEND_SMS, CALL_PHONE, etc.

But look at what Chainfire wrote:

Even on a non-rooted phone, there are several ways apps can run their own bundled code and exploit the kernel to gain temporary root access. From there they can either install SuperSU without your knowledge, or even run things as root without installing *su.

Scary, I know.
[SuperSU] Chainfire:
In theory, yes. In practise, malicious use of the exploits never install SuperSU or Superuser, they just abuse your phone.
[SuperSU] jesssiii:
So, Chainfire, what would you advise as far as security? I've never used any on my phones, nor had problems, but perhaps that's shortsighted?

Toro GNex
[SuperSU] Chainfire:
Don't open email attachments. Or the Android equivalent: watch the permissions of apps you install, don't install stuff that doesn't have a good reputation, don't sideload, don't use alternative app stores, don't do warez. Use head and such.
[SuperSU] billa:
free.avg.com is free and a really a good a/v with plenty of flexibility to make exceptions for files or folders, even entire drives.
[SuperSU] shnn2011:
Why can't Avast do somthing useful like flag and remove carrier IQ Spyware?

http://www.infamousdevelopers.com
[SuperSU] Chainfire:
And then there was root for 4.3 - the S4 Google Edition 4.3 leak: https://plus.google.com/113517319477420052449/posts/WqS2E9kkN1L
[SuperSU] polobunny:
I wish I had that kind of money to get a S4. Good job though. :)
[SuperSU] Chainfire:
Updated to v1.41. Brings various fixes for the 4.3, but also changes to logging. Some bugs in logging have been fixed, full content logging now works correctly with terminals (adb shell, android terminal emulator, etc), and I've changed the logs to use a monospace font (which reads much better).

4.3 users can wait for the Play store update which should just fix all issues automagically. A new download will be added to the G+ post as well.
[SuperSU] Kung-Fu-Tse:
hello Chain,

thx for the update.

When I install the update (S3 Android 4.2.2) the app is v1.40 ;) and not v1.41 :laugh:

maybe a mistake?
[SuperSU] Chainfire:
Installed from where? Play or first post?

If Play, it'll auto-update to v1.41 in a bit ... there was a wrong upload for 1.40 earlier.
[SuperSU] Kung-Fu-Tse:
from Play Store ;)

Screenshot:
[SuperSU] HannibaL_kk:
Hello. Updated from google play and there is a problem with option "install as system app'' . I reinstall the app but the problem is there.

ty.:confused:
[SuperSU] Pons:
Could you elaborate on what the problem is? What exactly do you do (I assume hit "install as system app") and what happens?
[SuperSU] HannibaL_kk:
I hit install as system app and the phone restarts. But the second time i hit install as system app the same think . The app dosnt closes to do the manualy restart. And the app does not installs as system app :confused:
[SuperSU] Rod_2007:
Samsung S4 4.3 root

Thank you sir! works great.....much appreciated. :laugh:
[SuperSU] Pons:
Hmm...it works for me, so I'm not sure what to tell you. If your phone is compatible, you could always try to flash the zip from recovery. The link is in the OP.
[SuperSU] HannibaL_kk:
I use omega rom v8 and perseus kernel. I didnt have any similar problem until today with the update :confused:
[SuperSU] 78Staff:
Worked here as well via play store and install to system option, but yeah the zip file is generally what I use and it works fine as well.
[SuperSU] SecUpwN:
ZIP file does not work for HTC EVO 3D anymore, cannot update binary. [MENTION=631273]Chainfire[/MENTION], please help me!
[SuperSU] :
I'm having the same problem on my Xperia. The flashable .zip is broken, even 7zip and WinRAR refuses to open it CWM says "can't open".
[SuperSU] :
Nice !! :)

But Why in JB CM10 is necessary to have Superuser insted of SuperSU? :/

I think SuperSU is better but it doesn't work on JB right? :/
[SuperSU] donshaffer:
Works fine for me and I have CM 10.1

View attachment 2095937

View attachment 2095938
[SuperSU] Pons:
SuperSU works on CM10. Currently I'm testing SuperSU on CM10, Android 4.2.2 with no issues. Not sure where you're getting that Superuser is necessary and SuperSU doesn't work.
[SuperSU] tiazek:
On Sony Xperia T LT30p, rooted, Android 4.1.2: The option to "Install SuperSU into /system" is not working for me with the last update. To update it, I did the following: 1) hit "Reinstall. Cleanup for reinstallation from Google Play", 2) Restarted, 3) Installed from Play Store... and everything is fine except that I cannot make it system app again (it was system app before). If I select "Install SuperSU into /system", the phone restarts itself, and after reboot, the app is still a regular app (not a system app). Selecting the option again produces the same result: automatic reboot and still the same. Any help please? is this a known bug? or any ideas on how to manually put the file into /system? Thank you.
[SuperSU] wcoaster:
Hi Chainfire

Just got the update and a little concerned about the dialogue asking me about using recovery. I'm on an extended vacation with limited PC accessibility. Using Galaxy Nexus with Codename Android 3.8 JB 4.1.2 What's my best course of action? Which option do I choose to update smoothly? I don't believe its installed as system app.

Thks from Thailand

PS..if this goes smoothly I'll buy the pro today..if not, I'll buy it later anyway. :)
[SuperSU] :
jaja Well Let's try it again :)

Thanks my friend (Y)
[SuperSU] 92drls:
I tested the play store version on the new 4.3 version on the S4 but said binaries needed updated. Tried flashing the ZIP and same outcome..
[SuperSU] SecUpwN:
[MENTION=631273]Chainfire[/MENTION], cannot even go back to the previous version with my HTC EVO - the binary cannot be updated. Right now it seems like I have to redo my whole system because of a failed SuperSU update. Would you PLEASE release a fixed version ASAP? Thank you!
[SuperSU] sintoo:
I can't flash with TWRP

I'm sorry if this was asked before,

What should I do to make the .zip file flashable with GingerBread 2.3.6 (Moto Atrix) ?

I tried both CWM and TWRP and both cannot flash.

I then flashed the superUser arm something .zip and success.

Thank you all.
[SuperSU] SecUpwN:
F*CK, I NEED SuperSu working! [MENTION=631273]Chainfire[/MENTION], where are you? :(
[SuperSU] polobunny:
What does it say?
[SuperSU] SecUpwN:
Installation failed. :(
[SuperSU] RomsWell:
I just downloaded it. The zip opens fine.
[SuperSU] Gaby4430:
Works great on the Galaxy Nexus . I prefer Superuser from Koushik Dutta (ClockWorkMod) , more open source and all content free

Edit : I discovered that SuperSu is available for free .
[SuperSU] polobunny:
Mod Edit: Meme Removed

---------- Post added at 11:24 AM ---------- Previous post was at 11:23 AM ----------

When you try to install from SuperSU app? Have you tried flashing the zip?
[SuperSU] rogio2:
Works for me htc dx .... thnx
[SuperSU] Super-Veloce:
I got S-OFF and unlocked bootloader by using revone on my HTC One.. when I install SuperSU from Play, and start the app, it says "Can't find SuperSU binaries" or something..

I want to intall it, whitout intalling custom recovery.. is this possible?
[SuperSU] SecUpwN:
Tried both. Doesn't work either way.
[SuperSU] polobunny:
Hmpf can't say I have nearly enough experience with HTC devices to be able to help you. :(
[SuperSU] POWerSUrgeSW3:
Yeah I had some issues with my HTC Evo4G. I found the ZIP to flash in recovery. Then whenever I launch SuperSU... Only could use the option to install binaries from recovery. The other option looked like it was doing something but never did.

~Max

Sent Via My WSv4.2 MD4 D2SPR
[SuperSU] htcflyerhc:
works on htc flyer
[SuperSU] russellvone:
Works on HTC OneV CDMA
[SuperSU] SecUpwN:
[MENTION=631273]Chainfire[/MENTION]: Problem with HTC EVO 3D solved, did a dirty flash of my ROM and flashed SuperSu 1.41 on top of it.

Works perfectly now. :)
[SuperSU] RomsWell:
Maybe via adb.
[SuperSU] Super-Veloce:
instead of fastboot flash trwp.img just fastboot boot trwp.img and you're using custom recovery once, to flash supersu.zip ;)

stock recovery and stock rom, with s-off, unlocked bootloader, root... whitout htvdev used :)
[SuperSU] kellwx:
Why does my Supersu different from the original?
[SuperSU] Will_Xda:
You can change the app's icon (a nice feature) to a few a different icons or no icon at all, it might be that what it is or maybe you were using "superuser" before, either way give it a try with the different icons :)
[SuperSU] kellwx:
I just rooted my GT-i9505 in less than 10mins, but the app icon is different from the original, and previously I rooted my GT-N7105, does it affect?
[SuperSU] Will_Xda:
Is there a flashable zip with the latest Binary files? As I can't update my Su binaries

Sent from my HTC Desire X

----

Nevermind
[SuperSU] polobunny:
It would be terrible for you to spend $2.50 of your hard earned money on an app you use likely daily on your $500 smartphone.

Chainfire puts a ridiculous amount of hours on all of his projects. Not only that, but he's liable for many great things that have made their way in the android world.

If you check SuperSU changelog, you'll see development has started more than a year and a half ago and still going strong, adding new features, fixing things that aren't even supposed to get fixed by your superuser application because other people cannot code properly.

In my honest opinion, that is worth more than $2.50.

The free version is by no means terribly crippled too...

Furthermore, correct me if I'm wrong, but I think the freeloader option is still present. You can unlock the pro features by ticking a box in the settings. You can use them for as long as you want, without any nagging, with the only incentive to make you buy SuperSU Pro being your own mind and stepping in that moral gray zone of activating Pro features for free... ;)
[SuperSU] justmpm:
Sorry for the interruption. I needed to do a little thread cleaning to remove some arguing and name calling posts. Please stop the arguing and the name calling...remember that this is a development thread and anything not directly related to the development of SuperSU doesn't belong here (even this post :)).
[SuperSU] Brixia:
[MENTION=631273]Chainfire[/MENTION]

thank you for your hard work.

I have one problem with the app. When I clear ram, if I open SuperSu, it give me "Force Close", but apps that require root can obtain SuperSu access. Could You help me? :)

I Have a Samsung Galaxy Y GT-S 5360, stock rom, custom kernel
[SuperSU] dbareis:
The author is ignoring my emails and I can't find any forum/FAQ for the product so I'll ask here..

How do I hide SuperSu/root from apps? I closed the apps, tried settings and unticking "Enable Superuser" but both apps I tried could still see it was rooted.

I bought the product because of the claimed "Temporary unroot".. If its is not done by unticking the option mentioned above, can someone please tell me how its done :)

Thanks for any pointers,

Dennis
[SuperSU] YMatrix:
If you are just trying to disable root rights from apps, all you need to do is open SuperSu, go to the applications tab, select the app you want and select disable / prevent....
[SuperSU] calisro:
It doesn't hide root from apps. It disable root access from apps. See the distinction?

EDIT: what are you trying to hide root from? Pm me what you are trying to do. I have a utility that may help depending on what you are trying to do. Let's not clog this thread with this though.
[SuperSU] Micoolef:
Can someone help me understand..

Why do you require root to download SuperSU from the playstore? I thought SuperSU is the root. When I take an unrooted phone and install SuperSU via .zip, it makes the phone rooted. Does this have to do with where the superuser.apk is installed, or does it have to do with the contents of the bin folder?

Does the "UPDATE" in front of the file name mean that I require older versions to install the UPDATE?

Even if the above is not the case, where can I find older versions of SuperSU? Is there an archive somewhere?

Can I just take the SuperSU v1.41 zip and flash it to any phone and it will root it?
[SuperSU] polobunny:
No, SuperSU is your root rights management software bundled with su binaries. It enables you to grant root access as well as control it. It does not permit you to "acquire" root per se. You must have a way of writing the files to a locked place in your system. Having a custom recovery installed, using an exploit or similar will enable you to write to these locked places.

No you don't need anything. Don't mind the UPDATE bit.

I don't believe it is suggested to try to run older versions of SuperSU. There's usually quite good reasons to the updates.
[SuperSU] Micoolef:
You rock.
[SuperSU] sparkplugDev:
Hey Chainfire, I love the app, of course. I'm actually running the Android 4.3 leak on my Nexus 4 and I was trying to change some files in the /System/apps folder and things got all confused. I think it has something to do with the Legacy memory issue. I tried to copy something from my downloads folder to the /system/app and I got this message "Error: Operation Failed: Message: cp: can't stat '/storage/emulated/Download/Mms.apk' No such file or directory." I can assure that my device is rooted using your experimental workaround and this was not a problem that I experienced before flashing the 4.3 ROM. I will do everything I can to help if you would like any assistance with this or any future issues. Thanks
[SuperSU] 008325:
Hi,

may i know the methodology of the "Disable Super User"? i notice that it not just simple copy the bin ./ext/su to /xbin/ ,

i would like to know what it have done in detail.

it it because there has a game call puzzle and dragon which check the device has been rooted or not, i tried to

to delete the su binary on xbin to simulate SuperSU but i got fail , i am really really want to know what is additional work for this option.

Thanks

Gordon
[SuperSU] sparkplugDev:
Gordon, Try downloading the OTA rootkeeper app by supercurio (http://goo.gl/EJvmm). First backup the su binary and then you can temporarily disable root. You may need to reboot but after that your app should work properly. This isn't really the place to be asking those type of questions though.
[SuperSU] THE.W!ZARD:
Deleted
[SuperSU] kaneelias:
Hey guys,

Looking for some assistance with SuperSu. I have been using it for a while and recently I came across the new app from my cable subscription provider here in Australia that now has an android app for watching on the go. Unfortunately this app does not work with rooted devices. If I disable root it works fine however I lose the SuperSu app from my app draw when I do so. The only way I have found to get it back is to go to the playstore and download it again. Am I doing something wrong when disabling and enabling SuperSu? I have tried the same process on my tablet and the icon remains in the app draw when ever I toggle disable and disable on my Xoom.

I am using a rooted Galaxy S3 running Android Revolution HD 26

Cheers.
[SuperSU] GroteBozewolf:
Look three posts up and try the OTA Rootkeeper
[SuperSU] kaneelias:
Thanks for the reply but I don't really see how this app will help me. Supersu already allows me to disable and enable root so I can use the app I need it for. Just when I disable root I lose supersu app
[SuperSU] bsoplinger:
I'm having trouble trying to flash the newest zip when I updated my ROM. Its somewhat of a non issue since I've learned that the ROM developer included the latest version of SuperSU. I just blindly flash ROM, kernel, gapps then SuperSU. Can the flash issue be because I'm flashing the same version? I always figured it'd be redundant but harmless.

Sent from my Nexus 7 using Xparent Purple Tapatalk 2
[SuperSU] polobunny:
What is the error?
[SuperSU] bsoplinger:
I don't know how or even if its possible to get a screenshot in recovery and I generally don't have a pen around so I don't have the exact wording hence my extremely vague "problem" description. From what I remember the process failed because it could not mount some partition who's name I didn't recognize. It wasn't cache, system, data nor any variation of temp.

Sent from my Nexus 7 using Xparent Purple Tapatalk 2
[SuperSU] jed.paolo:
What happens if i convert it into /system app?

sorry im new to this..thanks
[SuperSU] bsoplinger:
If you convert SuperSU to a system app you're making your system more secure. There's a remote possibility when its just a user app that a malicious app can take over that's removed when SuperSU is a system app. Search the thread, Chainfire explained exactly what protection it offers.

Re: My flashing issue. The error read: "E: cannot mount /staging" whatever that means.

Sent from my Nexus 7 using Xparent Purple Tapatalk 2
[SuperSU] Magissia:
I still have trouble to use the temp authorization, if i set it to a hour it will reask for pasword at next call and not next hour.

Maybe the app and not supersu is the cause, i've seen this problem with SD maid and will send a message to the dev too.

Regards
[SuperSU] tjackbjorn:
Any chance to root a Nexus 7 on 4.3? :D
[SuperSU] ygvuhb:
hi Chainfire

the super su v1.41 do not work on nexus 4 android 4.3 anymore

:crying:

may be something changed in android 4.3
[SuperSU] bombadier:
Get the version that works from his G+ post

It works on my Nexus 4
[SuperSU] Blindi1985:
This Works on my Nexus 4, Nexus 7 and Nexus 10 - all with Android 4.3

EDIT: please read the post - no direct linking to the download (because the post will be updated with new links maybe)
[SuperSU] bombadier:
I know its not a SuperSU issue (or is it?) but I cannot get Titanium Backup to restore any of my backed up apps it just hangs

Need to learn to read,only fools rush in!
[SuperSU] osm0sis:
Chainfire just stated on G+ that he'll be updating CF-Root and SuperSU in the next few days to support the new protections in 4.3.

Current issue some are seeing (on the N4 at least) are that you can somehow eventually lose root, and the daemonsu process starts eating up ~70%+ of your CPU until you reboot.

---------- Post added at 03:51 PM ---------- Previous post was at 03:50 PM ----------

It's not SuperSU per se, it's the new root daemon method required for 4.3. See here: https://plus.google.com/+Chainfire/posts/WqS2E9kkN1L.

Changing the sdcard location to the legacy symlink in /storage/emulated should fix it.
[SuperSU] DJxSpeedy:
important :
[SuperSU] osm0sis:
Yup. It uses a hack by replacing install-recovery.sh to create the daemon on boot. Hopefully Chainfire can come up with a better way since that's kind of dirty.
[SuperSU] VivaErBetis:
I think it's unnecessary, but I confirm, like others, that the “normal“ zip doesn't work in JWR66V on nexus4 and nexus10, but the “daemon version“ zip works perfectly well in both devices. Thank you chainfire!!!
[SuperSU] polobunny:
That's the way we like it no? :p
[SuperSU] osm0sis:
Just experienced the lost root + CPU load problem on my GN with daemonsu on 4.3. Happens fairly frequently, pretty much unusable. :(

P.S. I wonder what excuse Google has for breaking root, the way we root and all the root apps in existence..
[SuperSU] gamepois0n:
I have cyanogenmod installed, how can I change superuser into supersu?

Signup and get 15 Gb free plus an extra 5 Gb each using this link: https://copy.com/?r=vOeT9D
[SuperSU] Chainfire:
I'd happily investigate what causes that problem, but I need to replicate it first. I'll happily restore your backup having issues on any device I own to investigate the issue. But I don't have a Nexus 4.

Maybe it'll hijack something else, but it will have to hijack something. Daemon-based su is here to stay it seems - and install-recovery.sh is an easy and compatible way to start at boot.

Because the new security features they implemented are needed to guard against exploits.
[SuperSU] segv11:
Here's to hoping that our favorite custom ROM developers will provide the option to disable those features so we can have root without the hacks...

Sent from my stock 4.2.2 manta.
[SuperSU] osm0sis:
Indeed, this might be the thing that finally drives me away from stock ROM before Google officially pulls the plug. :(
[SuperSU] segv11:
Well I'm already running a custom ROM in my toro (cause, you know, Verizon delays).

My manta and mako are rooted stock. I've been willing to give up my favorite tweaks, like the extended quick settings, in order to get the stability of the stock ROM. But I'm not giving up root, and CF is having to do ugly hacks to make it work (that other developers of root apps will need to emulate...)

Sent from my stock 4.2.2 manta.
[SuperSU] backslashV:
Flashed the zip file on Android 4.3

After trying to open the app it says: There is no SU binary installed ...

Anyone?
[SuperSU] onbeskarakterli:
Same.
[SuperSU] Chainfire:
I really don't see what you have against it - it doesn't make much difference. Sure, there's probably some kinks that still have to be worked out, but other than that...
[SuperSU] rcs408:
Ditto, not working on my Nexus 7 with 4.3. Help?
[SuperSU] challl88:
[MENTION=313859]Phone[/MENTION]

EDIT: FFS stop spreading that link, it will be updated soon. Point people to posts containing the link, not the link itself.
[SuperSU] rcs408:
That one is also not working as expected -- lots of root apps are acting screwy.
[SuperSU] onbeskarakterli:
I needed root for TB and the workaround on the G+ account of Chainfire worked. I will try other root apps.
[SuperSU] 3c:
Hello Chainfire, just a few words on 4.3 "small" issues, hopefully that can help. (sorry for the G+ post, I was not sure where to discuss this as this thread is linking to G+)...

I noticed 2 main issues on the N4, probably related.

1- SD path is missing for root user, /storage/emulated/legacy is available but the default API-provided /storage/emulated/0 is missing.

2- Mounting /system RW with root users, other users continue to see /system RO. I know in 4.2 this was not the way it was.

That said, it seems to only apply to a fuse filesystem, and the SGS4 is probably not affected by issue #1 at least. When using vfat SD card (or sdcardfs on the SGS4) mount points (like -bind) are valid for every users.﻿

Is there a way to mount the SD card default path under root, using a script maybe, until this is fixed within the SU binary?

---------- Post added at 09:34 PM ---------- Previous post was at 09:25 PM ----------

I don't think Google will bother, it's just part of a much needed increased security and the new user model.

I rather hope for a fix on the real issues breaking most root apps than anything else.
[SuperSU] osm0sis:
Agreed. The sdcard thing and the cpu spike are the only things that really matter. For me right now it's about minimizing the impact while I wait to see if something better for those symlinked paths can be worked out. My File Explorer has a "native mode" toggle and turning that off allows the normal symlinked paths to work again even though the app remains root enabled.