yashsingh1/xdaforums huggingface dataset:
[SuperSU] BurlaMatto:
I set permissive mode, and re-enabled all knox app excluding "knox notification manager 2.0" and "knoxmigrationagent 4.0" for preventing notification about selinux disabled bla bla.

i'll see if the phone reboots again ;)

Thanks

PS phone reboots :\
[SuperSU] yankees45us:
Any news on ota root keeper working with latest nexus 5 4.4.3 update?
[SuperSU] NCguy:
That shouldn't be necessary with superSU pro should it? Is it even compatible?
[SuperSU] yankees45us:
Don't know what you mean by "shouldn't be necessary". Sorry. I think it's compatible. I have it installed now. I have 1.94 so I figure I need to update to .97 or wait for update in the market.
[SuperSU] NCguy:
The pro version has its own ota survival mode. I'm not sure if you can use rootkeepers survival code with superSU since it has its own code to do the same?
[SuperSU] ma678:
1.99r3 works fine on my Nexus 4 stock; however, no upgrade works on my Nexus 7 2013 after 1.94.
[SuperSU] volkmadi:
Hi,

for me that solved the reboots, but I left even the two knox apps enabled, I give a sh... to have a notification in the pull down from time to time.

Better the notification than a reboot! ;) Switch them on and monitor the behaviour of your phone!

I suppose that there is a hidden (at the moment at least to us) monitor in the back that checks the knox apps and if it finds one not running it tries to "bring it back to life" by rebooting the mobile. ;) (just my guess)

Anyway giving it a try won't make you too much trouble! ;)

Dirk
[SuperSU] varun.chitre15:
But what about late prompt?

I m planning to include this in my ROM but the app grants the superuser access late.

Burned from my laser torch using pencil cells
[SuperSU] Nucleotide:
So by me placing superuser.apk and su in the system folders, if I do a full wipe I won't loose root?

Sorry, just want to make sure I understand exactly what's going on.

Thanks.
[SuperSU] grayn0de:
You could always install SuperSU from Play Store and remove Superuser via a root explorer (under /system/app when cooked into most ROMs), but I think flashing the zip in the OP will overwrite the original Superuser.apk.

They mean that if you do a factory reset on a pre-rooted ROM, you won't lose root, you'll just revert back to the original (non-superSU) configuration. In otherwords, how ever your ROM was on first flash.

Sent from my Altered EVO 4G.
[SuperSU] Flappyraccoon:
If it was intended then disregard this error. I have notification popup unchecked in settings but from time to time it pops up stating superuser permission was granted. It usually happens after a fresh reboot or now and again in script manager.
[SuperSU] dimebagdan65:
Shameless Plug Time! lol

Just throwing it out again, my review of SuperSU (Hey, that rhymed!) and tutorial on how to install it as a system app as well as what to do if you encounter any wonkiness! App works FLAWLESSLY! Loving it, keep up the good work CF!
[SuperSU] varun.chitre15:
Wow!!that was a great review.

@chainfire

Are we allowed to include this in our ROMs?

@dimebagdan65

If chainfire says yes then can u tell me appropriate way to put it in my ROM?

Thanks!

Burned from my laser torch using pencil cells
[SuperSU] dimebagdan65:
Sure thing brotha, I'll do my best! CF can probably tell ya better though lol (If I was any good at that type of stuff I'd be developing instead of commentating. I wanna learn but tough finding time when you're an apartment manager lol started learning flash and then everything is going html5 fml... Lol)
[SuperSU] Pons:
From the OP:

Redistribution

Yes, you are allowed to embed the (free, non-Pro) SuperSU apk and su binaries in your own custom ROMs ! As is standard (and done by the attached ZIP), normal is to use /system/app/Superuser.apk for the apk and /system/xbin/su for the binary.
[SuperSU] Kurupt1:
Doesn't work with voodoodb louder on cm9 4.0.4
[SuperSU] dimebagdan65:
Happy Easter SuperSUsers!
[SuperSU] shaggyskunk:
Sent From Down the Rabbit Hole
[SuperSU] theone10:
I used 4ext and everytime I open the control app it asks for premission for su. It is not remembered. How can this be fixed
[SuperSU] dimebagdan65:
First things first I'd look in, ohhh, saaaaay... superuser settings...? That and read the su prompt CAREFULLY when it comes up and make sure you don't have the box checked to ask again next time... Other than that, that's a new one to me, mine works fine (with Superuser or SuperSU)
[SuperSU] PharmCAT:
To elaborate on this. In the SuperUS go to the first section ("Apps") and select the listing for 4EXT, you will be given options to edit the root access for the app, and make sure it says "Grant" under the Access. And as the above said, read.
[SuperSU] siseam:
So, in the end can I expect an update at some time where the prompt sticky will hold again? I do not wish to use the v0.83 forever and ignore other updates.
[SuperSU] sydbarrett55:
it would be nice that permissions remain when we update an application.

And also the possibilities to save the app that have root access. (as superuser)

If this is not resolved in future versions, I return to Superuser.

I'm sick autoprisation that do not remain
[SuperSU] theone10:
I get the same the same update app and it asks again
[SuperSU] davechcn:
Thanks, it's very good
[SuperSU] davechcn:
The Chinese Language Pack

This is the Chinese Language Pack for SuperSU.

Thanks!
[SuperSU] atilla88:
Hi guys,

Since i updated my galaxy s2 to xwlp7 and rooted it with the cf root kernel my supersu app keeps crashing sometimes.

For example if i install a new app.

Does someone know what to do?

Thanks
[SuperSU] dhampire:
1.99r3 : it can't use only NTPSync, popup no su binary. lenovo s930 jb4.2.2

Sent from Lenovo S930
[SuperSU] :
Some users are facing probs on v1.99... Wait for it to hit stable release...

Till then v1.97 is your best bet... Here you go http://download.chainfire.eu/416/SuperSU/UPDATE-SuperSU-v1.97.zip

Flash it from recovery...

hope this helps....:good:
[SuperSU] NghtWachman:
I'm going to try this method because I've been having issue with Chainfire SuperSU Pro v1.94 from play store which I purchase to support him, but it's becoming a freaking nightmare with superSU denying other apps even though I grant them access, apps such as SQLite Editor and clean master don't seem to work at all.

Would I have to remove SuperSU v1.94 then?
[SuperSU] :
Hey, I think it's got to do with your ROM rather than SuperSU... And I can assure you the money you gave to CF is the dollar best spent... trust me... He's the GOD OF ROOT and he knows what he does....

Nope, just flash v1.97 through recovery and reboot....

After that open SuperSU, it will ask you to update binaries... Press OK, and you're good to go...

But if you are facing problems with v1.94, you will face problems with v1.97 too...

Coz I believe the problem is with your ROM rather than SuperSU...

Btw, the recommended way to update SuperSU is through Play Store and I advise you that coz its the safest too...

Hope this helps...:good:
[SuperSU] NghtWachman:
Appreciate your reply and thanks for the info will have to look into my ROM so see what the heel is going on here, I find it unusual that SuperSU is blocking SQLite and Clean Master, oh by the way what ROM arte you using? Im running Xtresolite rom.
[SuperSU] :
No probs, buddy... Always there to help...

Am running Moto E stock rom 4.4.2....
[SuperSU] dimebagdan65:
Probably a bit early to ask but, does 1.97 play nice with 4.4.3? Anybody updated and tried it yet?
[SuperSU] Pkt_Lnt:
Yes, 1.99r3 on Nexus 7.2013
[SuperSU] VivaErBetis:
Tested 1.99r3 in nexus 4 and nexus 10 with the new Android 4.4.3 and no problems at all.
[SuperSU] dimebagdan65:
Thanks guys, so 1.99r3 is a go, that's good to know. Guess I'll test with 1.97 stable tonight and post back unless someone beats me to it lol
[SuperSU] Taomyn:
I'm on stock recovery for my N5, so is 1.94 ok for when I get 4.4.3 or do I need to go to 1.97?
[SuperSU] dimebagdan65:
From what I've read 1.94 will work with 4.4.3. Some folks here on XDA have included it with a flashable zip of 4.4.3 so [emoji106]
[SuperSU] mdprfsr:
1.99r3 working great on 4.4.3 nexus 5
[SuperSU] 78Staff:
Not sure if you want any more reports from non-official TWRP's still, but I experience the same still on all post-1.94 versions through 1.99r3 - updating binary fails. Reverting to 1.94 is successful each time however. Using the last 2 or 3 versions of Task's AOKP on the S4.

Same as bobbarker and a few others I believe, using F2FS-enabled TWRP, although I wouldn't expect it to make any difference as it only allows F2FS formatting along with ext4.
[SuperSU] dhampire:
1.97 : su binary update loop. back to 1.94, everything no problem. waiting stable release sir.

Sent from Lenovo S930
[SuperSU] osm0sis:
Yup! I can confirm no issues so far on my N7 '13 with SuperSU v1.94; I think a lot of the v1.97+ stuff is for the AOSP master branch changes that have yet to make it into a tagged Google build. Chainfire said they have made it into some Samsung devices already, but otherwise things should be good. :good:

http://www.androidpolice.com/2014/0...not-cripple-writing-to-system-for-root-users/
[SuperSU] gotluck:
1.99r3 seems all good on gs4 ge i9505g 4.4.3
[SuperSU] Android-Andi:
[MENTION=631273]Chainfire[/MENTION] any statement about this commit?

https://android-review.googlesource.com/#/c/96284/

<3 the NSA :D

Gesendet von meinem GT-I8190 mit Tapatalk
[SuperSU] pigr8:
1.99r3 tested on HTC One M7 Google Edition 4.4.3, perfectly working so far
[SuperSU] yankees45us:
1.94 will work. Used it last night and I was able to keep root after I flashed ota zip.
[SuperSU] Taomyn:
Yes confirmed - I sideloaded the OTA for my Nexus 5 this morning and root was and is fine (contrary to some sites reporting that root is lost for all updated devices - what do they know).
[SuperSU] lion7718:
1.99r3 worked on my Nexus 4 without any problems.
[SuperSU] meduza:
1.99r3 works perfectly on both devices :)

m.
[SuperSU] Klaus N.:
1.99r3 also works on my Xperia Z1 (C6903) without any problem.
[SuperSU] gorilla p:
SuperSu Virus

I know some people have said that Google has not actively tried to make rooting more difficult, but it is only a byproduct of trying to make it more secure. Could someone explain this then? (See attached picture)

Google Drive is now warning that SuperSU flashable zip is a virus.
[SuperSU] osm0sis:
Some of the stuff su does now probably triggers heuristics. Honest mistake, I'd assume. :)

Edit: Where are you downloading that from? That's not the correct filename.. :confused:
[SuperSU] Frank Westlake:
Then maybe it does have a virus. But the SuperSU archives I've examined have a certificate appended as a zip comment, and since appending data to binaries is a means of transporting harmful data, that virus scanner may be providing good advice.

Frank
[SuperSU] zard:
1.99r3 is all good on Nexus 7 GSM Tilapia before and after updating to 4.4.3.
[SuperSU] gorilla p:
Yes it is. Latest version downloaded from chainfire.eu website (different download page). Put on my google drive site and went to download it install on my gbox today and got that message.
[SuperSU] osm0sis:
Ah okay, you renamed it then. :good:

OT: Which GBox do you have? :D

http://xdaforums.com/showthread.php?t=2492843
[SuperSU] kabini:
SuperSu + 4.4.3 + ART

Has anyone checked if SuperSU Root + Android 4.4.3 + ART work together?

Chainfire has been acting like the prophet of doom lately on his G+:crying: - Apparently this combo will cause ART to crash and force it to rebuild.

I just want to clarify if any fellow XDAs have tried this out.

---------- Post added 5th June 2014 at 12:05 AM ---------- Previous post was 4th June 2014 at 11:58 PM ----------

Were you running ART or Dalvik?
[SuperSU] Chainfire:
It seems to be working fine so far on my Nexus5+ART

SuperSU (or anything containing the name "chainfire", really) has been being marked as virus, exploit, etc by many scanners. I wouldn't worry about it.

(There have been so many false positives, typical 'scanner who cried wolf' issue)
[SuperSU] Nemado:
Since rooting requires an exploit, it's no surprise supersu is tagged as a virus by some companies.

I updated my nexus 10 (stock rooted) through ota with supersu 1.94 in survival mode. Everything went fine and I still have root (adaway works).
[SuperSU] kabini:
Thanks for the clarification

Merci

Thanks for the clarification - makes me feel a lot better.

I guess those warnings regarding SELinux and ART only apply to AOSP as of now:D
[SuperSU] Natakranta:
Grouper fastboot flashed with 4.4.3 factory images and latest official CWM 6.0.4.3

SuperSU 1.99r3 is working fine as expected. Titanium restored user apps backups.

Thank you!
[SuperSU] Alkemix:
[MENTION=631273]Chainfire[/MENTION]

I've flashed Your last SuperSU (1.99r3 release) into:

- Galaxy Nexus (Maguro)

- FML 4.4.3 ROM

- [MENTION=2915683]BaNkS[/MENTION] gapps 4.4.3 minimal

I've found issues... Suspersu app disappears from app list and root is lost...

Rom problems or SuperSu need of another update ?
[SuperSU] Chainfire:
v1.99r4

Another test release, this time v1.99r4. Hopefully solves the remaining issues, detailed below in response to reporters of various issues.

This specific release is available through this link: http://download.chainfire.eu/447/SuperSU/UPDATE-SuperSU-v1.99r4.zip. The standard SuperSU download link (http://download.chainfire.eu/supersu) also currently points to this release, but who knows for how long :)

This update needs to be flashed through recovery if you are running any other v1.99 release, or the su binaries will not be properly updated.

I suspect the language issue is now fixed. I was not able to reproduce the issue, but I do think I have found the cause. Please test and report back!

I suspect these issues had to do with a symlinked busybox that does not support SELinux (doh - symlinking busybox is a terrible practise, and not including a SELinux capable variant on an SELinux ROM is even worse), this update will hopefully fix your issue. Let me know!

This issue should be fixed now as well.

Not sure about these specific issues, let me know if the problems persists with the 1.99r4 update.

I have made some adjustments. I'm not sure if they solve every case you mention.

You mention missing logs - I did find an issue where logs would not display, while they would actually exist. Rebooting or manually refreshing the display would bring them into view. Maybe this is related - maybe not. Please test and let me know.

Additionally, after unlocking the device, SuperSU will now display a notification of apps that were silently denied while the screen was off - if any.

Not sure what is going on exactly with your 4th case. It smells like an infinite su request loop is going on here, so when you turn the screen on, logically there still is a popup prompt, because as soon as one times out, a new one appears, due to the request loop.
[SuperSU] Alkemix:
Thanks for update but...

I've done full wipe (system also) and flashed 1,99r4 ...issue remain... supersu app doesn't appear into apps list and I can't open It.

If a remove supesu by reflashing all (full wipe again) by rom root inside all work perfect :(

Have You changed Supersudaemon script ?
[SuperSU] Chainfire:
FML appears to be based on Omni, which has the SuperSU link in Settings, not in the app drawer. It also has a CM heritage, so perhaps in settings you need to still enable root or whatnot.
[SuperSU] Alkemix:
Into Metalspring omnimetal rom yes (it is into settings).. but into FML It doesn't apperar into settings... never seen It into settings .. maybe ROM issues (ROM "doesn't like" supersu :( )
[SuperSU] Chainfire:
So they probably took it out of settings, but didn't remove the resource that lets SuperSU detect if settings supports SuperSU - they only removed half.

Does this command from shell show SuperSU ?

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

If not, then I don't know what's going on ...
[SuperSU] 78Staff:
Success here :good: - Flashed in recovery over 1.94 on S4 with Task's latest AOKP, and no more prompt for upgrading binary. :)
[SuperSU] joni2012:
Great
[SuperSU] Alkemix:
Full wipe (system perfetc clean) and supersu last test release into FML 4.3.3 for Nexus (maguro):

after..

am start -a android.intent.action.MAIN -n eu.chainfire.supersu/.MainActivity
[SuperSU] bobbarker2:
Hooray, fixed here. Thanks for your work Chainfire!
[SuperSU] derpotato:
I'm really sorry for asking questions here, but is there any other way to open supersu after I hide it in my tablet? (which does NOT have dialer so I can't dial the supersu)

I accidentally deleted the data of supersu after I hid it ... and then every single app does not have root access anymore...

I tried to open supersu with terminal emulator , I tried to delete supersu in system app, but without the ability to grant root access , everything failed.

I have searched everywhere how to fix this, but since my case is irregular, there's no help available.

I thought the developers themselves would be more experienced than most people, and probably know the solution, so I asked here.

Can anybody help me? Thank you.
[SuperSU] Pons:
Try the post two above yours, and should also be in posts 1-4. It's a command that must be typed in terminal. I'm mobile right now, so I can't easily copy/paste it for you.
[SuperSU] derpotato:
Yes I typed that, and I already said that I cannot grant root or superuser access to terminal emulator or any other application. The result is the same as two post above me.
[SuperSU] osm0sis:
You need to run as root..;)

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

Also [MENTION=4701553]Alkemix[/MENTION], I think FML has those root settings under Developer options. Tap the Build number in About phone 8 times or so.
[SuperSU] derpotato:
I copied and pasted your code or command, but it does not give me any response in terminal emulator. However, just typing su -c, that actually worked (it does not open the app though) . But after that, no matter what combination of code I tried, the supersu still won't open at all. Is there any other code or way I could try?
[SuperSU] Alkemix:
Right! I've forgotten!

Ok.. after line command SuperSu runs and now I've root access... but only by this command I can see "supersu" and I can use It.

ROM issue ? How Can I solve ? Thanks

I'm not so noob :silly: ;) but thanks ... Nope .. into dev options is all ok like "Root access"

You must not include "-c" parameter
[SuperSU] derpotato:
You mean like this ? :

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

I tried that and that doesn't work either.. I also tried to type 'su' first then press enter then 'am start -a android.intent.action.MAIN -n eu.chainfire.supersu/.MainActivity' , but that does not work either.. Or am I doing something wrong?
[SuperSU] sub1287:
Just for the hell of it I tested this out on my old wildfire s and 1.99r4 works I tried 1.99 and it worked as far as root access goes however it always said binaries needed updated and it no longer is doing that.

accelerated [mako]
[SuperSU] iamnotkurtcobain:
1.99r4 works now on cm11 S4 9505.

Thanks chainfire!! Great work!

Gesendet von meinem GT-I9505 mit Tapatalk
[SuperSU] Frank Westlake:
It should look something like this, though the prompts may have text before the '$' and '#':

$ su

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

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

#

You type the 'su' and 'am ...' parts, the "Starting..." part is the output.

Frank
[SuperSU] sub1287:
But it does force close on every boot up though.

Lol no ones using this type of phone anymore anyways... its my oh **** my nice phone broke, phone.

accelerated [mako]
[SuperSU] NZgeek:
You say you hid the app... how did you do this? If there's a way to hide an icon, there must also be some way to unhide one.
[SuperSU] Frank Westlake:
1.99r4 OK on:

SGH-I717/AoCP6.4 Android4.31

SM-N900V/MI9 Android4.3

SM-N900T/MI7 Android4.3

The SGH-I717 (Note) booted partially to the "Android is upgrading\nStarting apps..." dialog until I reset it 20 minutes later. Second boot appeared normal.

Thanks.

Frank
[SuperSU] rs tony:
Phone: Samsung galaxy s2 plus (gt-i9105p)

Rom: Resurrection Remix 4.4.2(aokp based)

I got already SuperSu v1.94 installed. When I flash v1.99r4 from twrp and reboot, I got still SuperSu 1.94 apk in my phone. So nothing happens when I flash SuperSu v1.99r4.
[SuperSU] Frank Westlake:
And mine still says 1.99r3 in Settings. Maybe it was just an update of the root files.

Frank
[SuperSU] sub1287:
accelerated [mako]
[SuperSU] Claghorn:
Just reporting oddity for reference: I got 4.4.3 on my Nexus 7 (flo) today, and when I re-rooted and set SuperSU to reinstall from google play, it couldn't update the binary using the "normal" method. I never had a problem with the normal method before 4.4.3, but I was able to update it with TWRP, so I'm good to go now.
[SuperSU] sub1287:
Chainfires post says to update with recovery a couple pages ago...

accelerated [mako]
[SuperSU] dhampire:
report. 1.99r4 : still su bynary update loop. lenovo s930 jb 4.2.2

Sent from Lenovo S930
[SuperSU] AlmostIdiot:
For anyone who hs the binary update problem, try wipe dalvik cache & cache, I had the same problem the first time, I even wiped cache & dalvik, but I wiped them again, and now everything works OK.
[SuperSU] derpotato:
Yes I typed that but it doesn't give me anything , the '#' that usually shows after typing 'su' is not in here too because I couldn't grant root access

I hid the icon by changing the icon to nothing in the supersu app. And then the supersu app is actively hiding itself , and I am trying to find a way to unhide it. So far, everything have been unsuccessful. I guess there is no other way than calling supersu from dialer (which tablets do not have , and I tried using exdialer from playstore but it still won't work) and opening them with terminal emulator (which is impossible without superuser access).

Can I request to the developer here to make other ways of getting to the hidden supersu without needing to grant superuser access and without using dialer? Thanks for all of you trying to help though.
[SuperSU] gorilla p:
Using NeXuS⁴ Not running 4.4.3 yet, but flashed latest 1.99r4 using ART on C-Rom with Hells Doctor Kernel. It took a bit to boot, but its working fine.
[SuperSU] NZgeek:
Doh! Kinda hard to come back from that.

If you've got a CWM/TWRP recovery, you could try uninstalling SuperSU and reinstalling it via zip. This effectively a fresh install, and you should get your icon back.
[SuperSU] derpotato:
I do know how to reinstall supersu via zip, but what I can't do is uninstall the supersu. I couldn't uninstall the supersu directly (the only thing I can do is uninstall the updates), and I couldn't delete the apk on system/app because I can't grant superuser access to root browser, and I do not know any other way to uninstall it.

I also did this : cwm backup, then wipe all the data and system, then reflash stock android zip which does not have supersu, and then do an advanced restore for just the data , so that the supersu won't be restored. After that, I booted the system, and the supersu apk in system is gone. After that , I installed the supersu zip, and supersu is back on the system/app reinstalled, but the icon still does not show , I think it's because android still remembered to hide the supersu...

Is there any other way to uninstall supersu? Thank you in advance.
[SuperSU] bhiga:
Do you have Tasker?

I hid the SuperSU icon but can still launch the config via a Tasker task.

Launch App

Tap the All button on the bottom right

Hold on SuperSU and choose MainActivity from the pop up

Go back to the task and hit the Play button.

-= this post enhanced with bonus mobile typos =-
[SuperSU] derpotato:
I don't have tasker.. I haven't even used it once. Does that app needs root access to launch supersu? If it needs root, it won't work because I can't grant root access.
[SuperSU] jazzruby:
Backup your data with Titanium Backup, reflash your ROM and SuperSU.

Boot into system, download/install Titanium Backup, restore your data and call it a day.

-JR-