yashsingh1/xdaforums huggingface dataset:
[SuperSU] markshu:
Help on Boot Loop

Need some help in here. Am on Xiaomi Mi3 device, install MIUI 6, afterwards install SuperSU from Google Play.

Upon install, open the app, it prompt for normal install / install with CWM in.

I accidentally clicked on the CWM option and once device restart, I see my usual splash screen with flicking screen (barely able to see on top saying SuperSU 2.0 ...)

I try to go to ADB mode / recovery mode with power + vol up / down but seems like am stuck in a boot loop.

Any help will be greatly appreciate
[SuperSU] JulianJenner:
XiaoMi3 with MIUIv6 is a pre-rooted phone. No need SuperSU, MIUI has got internal root system, namely: Permissions. Use this app.

LGE-P760 Optimus L9 / NamelessROM build 4.9.7 / Tapatalk Pro 4.6.2
[SuperSU] markshu:
Thanks mate! however my problem now is I cannot even boot into the rom. Am stuck @ the splash screen. Flicking screen afterwards ...
[SuperSU] JulianJenner:
You need to go Mi3 XDA thread. And yuor question will answering.

LGE-P760 Optimus L9 / NamelessROM build 4.9.7 / Tapatalk Pro 4.6.2
[SuperSU] markshu:
Thanks mate!
[SuperSU] JulianJenner:
Go there: http://en.miui.com/thread-34303-1-1.html here are your links...

LGE-P760 Optimus L9 / NamelessROM build 4.9.7 / Tapatalk Pro 4.6.2
[SuperSU] Chainfire:
v2.06 BETA is out!
[SuperSU] hgmichna:
According to my experience you could add the OnePlus One to your Android success list. SuperSU works fine on it, as long as the setting "Respect CM root settings" is disabled, so these invisible settings are ignored.
[SuperSU] asibmkhan:
Updating SuperSu

I have a rooted htc One X, running on CM11, i flashed a SuperSu of 0.87v when i first rooted and i have an integrated ''SuperUser'' in my phone's Settings from where i can access superuser and there is no app of super user in my phone rather than this integrated one.

So i wanted to know that if i install this latest version of super user, will it be integrated to my phones settings like before? and how i do i install it, flash through recovery? and will i lose my phones data???
[SuperSU] Ravenik:
I am experiencing a sort of a bug. I have just rooted my Samsung Galaxy S5 and installed SuperSu from Google Play. I also paid and installed Pro. Now when I need root privileges in Es File Explorer 3 (for example to delete folder inside /mnt/extSdCard/Media) then the SuperSu panel appears. I give privilege for 1 minute. Unfortunately ES File Explorer seems to run with root privileges for much more then given 1 minute - virtually until the mobile phone shutdown and start again. I don't like the idea of rebooting the phone to stop root privilege for one application. Why SuperSu's 1 minute time limit does not work? Is it a bug in SuperSu , ES File Explorer or sth else? I found "Root explorer" running without this bug.

Anyway if ES File Manager can act in this way then other apps also can and so giving time limit for root privilege in SuperSu just does not work.

I will appreciate clarification.

My phone is Samsung Galaxy S5 SM-G900F, Android 4.4.2, OS BUILD KOT49H.G900FXXU1ANG2, SuperSu Pro from GooglePlay, autoupdate.
[SuperSU] egingell:
Try to force stop ES (or whatever app holds root), wait a minute, and try again (after the initial grant). If SuperSU asks again, then ES is running in the background for whatever reason. That's my theory anyway.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] Ravenik:
I have already tried to kill Es File Manager using Advanced Task Killer and this does not improves described behaviour. ES file manager started again after 1 minute has root privileges without asking, despite 1 minute time limit that I forced in SuperSu's dialog window.

But even if killing ES File Manager helped, still the application should not have root privileges after given period, even without killing it. Thats my opinion. But anyway killing app does not solve the problem.
[SuperSU] hgmichna:
(deleted)
[SuperSU] Hoka-Hey:
won't even install

I can't even get it installed on my 2013 Nexus 7 running L-preview...

This is a pity because without it sticmount does not seen to work
[SuperSU] Chainfire:
ES File Manager uses a background process that keeps root. SuperSU doesn't kill *running* root processes after the time period expires - and it never will - it just doesn't grant access to *new* processes. In fact, what you want isn't even possible, for as soon as the app has been granted root, in theory it can do anything, including installing a second backdoor to root so it will never have to ask for root again.

If you properly kill the explorer and all its components, it will no longer have root when you open it again.
[SuperSU] Ravenik:
Thanks for clarification!
[SuperSU] jazzruby:
ES File Explorer has always been this way; it appears to run a binary 'tool'/su_port on its own, which can hold/access root (su) privilege until shutdown/restart

Even after an ES upgrade (Play Store) it will not trigger a new access prompt; to spite having "Re-authentication" checked in SuperSU settings.

SuperSU log of ES File Explorer:

INTERACTIVE
echo successfully
successfully
chmod 777 "/data/data/com.estrongs.android.pop/files/libestool2.so"
echo
echo '$-----ESTOOL-END-----$'

$-----ESTOOL-END-----$
/data/data/com.estrongs.android.pop/files/libestool2.so 23486 /data/data/com.estrongs.android.pop/files/comm/su_port

The above log/command is the only log of ES in SuperSU

-JR-
[SuperSU] Ravenik:
I am new to using root features on Android but I find it disadvantage that I don't know which applications (even from GooglePlay) are "safe" in terms of root privilege access. So that I wouldn't install unsafe apps. Is there any list of root-safe or root-unsafe apps to be found on the Internet?
[SuperSU] egingell:
Point of order: Saying "even from GooglePlay" implies that all apps from the Play Store are safe. That's dangerous thinking. *Every* root app can cause irreparable damage to your phone if the dev were so inclined and your best bet for a NOC list of safe apps is reading the reviews and posts per app.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] Chainfire:
Some would say no root app is safe... In the end you're just going to have to *trust* the author to not screw you over. Some will rant about how you should only use open source root apps, but unless you actually personally review the code (and have the skills to do so properly) and personally build those apps from source, you're still going to have to *trust* someone else.

Having root is "dangerous" by nature. Even if you *trust* only those people who have good intentions, a bug in the root app (or god forbid, SuperSU) may still allow a malicious attacker to gain root access to your device.

Then again, any app may contain exploits to gain root access to your device. Most users *trust* most well known 3rd party app authors and Google's countermeasures enough to consider themselves relatively safe when using Play store apps.

Hacks and devs have shown time and again how full of holes OEM parts of the firmwares can be as well, and how these holes can be exploited to gain root access without something like SuperSU installed. Most users *trust* their firmwares, even though there are risks there as well. Same story with the base AOSP code and the kernel. Holes, holes everywhere.

All there is is trust and reputation - it always comes down to that. Safe? There's no such thing in practise.
[SuperSU] r4Rok:
Question, where to get latest SuperSU (including BETA) releases ?!? Because, Google Play store is always lists older versions!
[SuperSU] kingvortex:
The Play Store version is stable.

Anyway, test versions are posted in the SuperSU section, specifically in this thread.
[SuperSU] JulianJenner:
Only from this post, when Chainfire master share newest releases. Like yesterday's post: http://xdaforums.com/showthread.php?p=55325687
[SuperSU] r4Rok:
OK, it means you need to keep checking in to this thread for updates.
[SuperSU] r25txe:
The Play Store will always be updated to the latest stable version meaning the updates are simple.

Unless you're having issues with the stable versions there shouldn't be a need to use the BETA versions, so if you choose to test them you will need to check that thread two posts back. Setup an RSS to the thread or have the first page monitored by http://changedetection.com or http://followthatpage.com.
[SuperSU] Swamphound:
The tapjacking protection feature is very useful and very much appreciated! Ty.

Sent from my VS980 4G running Xdabbeb's Stock 25A/Dorimanx 7.4
[SuperSU] NZgeek:
Integration into your phone's settings is controlled by the ROM you're using. It typically uses the package name of the app, which I don't think Chainfire has ever changed. At worst, you'll get a SuperSU icon in your app drawer. Upgrading is highly recommended in any case, in order to fix bugs and security flaws.

Upgrading SuperSU shouldn't cause any loss of data. It's just an application, not a ROM, so is designed to be installed on systems that are already up and running.

Because you're upgrading from a very old version, you may have some problems installing the latest version from the Play Store. Give it a go, but if it fails then you're going to need the zip from the first post in this thread. That zip needs to be flashed from a CWM or TWRP recovery.
[SuperSU] elvisypi:
[MENTION=631273]Chainfire[/MENTION] First thanks for the hard work and the great support.

I have a HTC One M7 and as I updated to 4.4.3 I'm having some problems. I always set the settings to "always allow", logs turned off, no notifications. Since 4.4.3 it asks me if I want to allow root access, even though it was set to always allow and in the apps list show the allowed apps. In logs though there's no trace. I tried the latest version 2.02. Please have a look:D

Edit: Just saw the beta releases. The 2.06 beta fixed it! Sorry for the disturb :silly:
[SuperSU] shoey63:
If you don't want notifications or logs - just delete the apk without uninstalling ;)

(not recommended obviously)
[SuperSU] jesssiii:
You saying deleting the SuperSU app will then auto allow all root permissions?

Verizon LG G2
[SuperSU] r25txe:
Yes, the apk is just the interface to use the binary.

Leave the binary with no interface will auto grant root privileges to ANY app without ANY notification to you.

A really bad idea, but it's your device ...
[SuperSU] Spacemonkie4207:
Should I remove the old SuperSU before flashing 2.02?
[SuperSU] khairulez:
No need..just flash it.Better do wipe cache and dalvik before flash.
[SuperSU] idcrisis:
Hi there,

Thanks so much for this great product.

Have you considered using sudo perhaps masquerading as su? That may negate the need for the intent calls to the Java subsystem.

App developers wanting to be better certified could probably use the feature to call specific binaries only ( perhaps a selfcheck.xml config file in the apk/remote authority/dynamically generated )?

This may perhaps even be used to signature check other apps/binaries and inodes/processes/boot sectors/system partitions/dex files etc.

Since your app is already so popular, it could probably become a certification authority or the like ;)

Thanks once again and do keep up the excellent work.

Cheers!
[SuperSU] mulbrich:
Interactive Shell notification

I have a "interactive shell" notification appearing, even disabling ALL notifications. There is no way to fix this ? I like supersu app. I don´t want to kill interface.
[SuperSU] hgmichna:
I guess some people here do not understand what you want the SuperSU app for, if you disable all notifications. Could you explain that?

It sounds a bit like, I want to have a car, but I will remove all wheels.
[SuperSU] mulbrich:
Sorry, I'll try to explain. I installed a app called mspy in my samsung S3. I´ll give this S3 to my children. I want to disable notifications only for this app. But how I explain before, setting the app (supersu) to no notifications, the notifications still appears.
[SuperSU] theartialmartist:
I've made a terrible mistake.

Unlocked the bootloader successfully then tried flashing superuser, then wiped all, then tried installing CM11

Apparently I never got root successfully and now the device has no ROM at all.

It won't write CM11 and I can't throw a stock rooter tmobile rom in the TWRP directory to try that.

"Error executing binary in zip"

did I just wreck the device?
[SuperSU] kv1dr:
You better ask this in your device section or your ROM thread
[SuperSU] Sebin35:
guys help......i dont know why my supersu keeps on crashing and asks for updating binary each time i reboot my device......
[SuperSU] hassaniq:
use SuperSU to disable Knox

i use SuperSU to disable Knox apps in my S4 I9505 4.4.2

i got Random reboots

how can i back disabled Knox to my phone and remove it manually by titanium backup?
[SuperSU] Chainfire:
Try:

pm enable com.sec.knox.seandroid

then use this command to find the name of the APK:

pm path com.sec.knox.seandroid

Note the filename, then:

mount -o rw,remount /system /system
rm -rf FILENAME
reboot

Maybe that'll work. Maybe it'll break your system and you need to reflash.
[SuperSU] Chainfire:
v2.08 beta - http://xdaforums.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
[SuperSU] Androidre:
Hi friends...

Hi at all, hi Chainfire,

I have a question, I state that I have downloaded and installed supersu for Android 4.1.2. (Galaxy s advance), using this link, before knowing this page. Please correct me if it was a mistake: d-h.st/ook. The first thing to say is that, I have not managed to get it to work, the app rootchecker tells me that the phone has not been rooted.

The second question concerns instead the opportunity to explore the system folders (hidden), by remote connection. I use web.airdroid.com with firefox.

When I've got root permissions, I'll have the opportunity to explore these folders in web.airdroid.com? Or, is there another method ?, ... not through a wi-fi, but only by means of a remote connection...

Thanks in advance for the answers

Best regards
[SuperSU] jcarroyo:
I have the same problem in GT-I9300I Android 4.4.4
[SuperSU] Pkt_Lnt:
As just posted by Chainfire, the beta is trying to solve that, try it here.

http://xdaforums.com/showpost.php?p=55400384&postcount=6525
[SuperSU] Chainfire:
If you are reporting a crash, you need to provide a logcat. There is nothing that can be done about crashes without logcats.
[SuperSU] jcarroyo:
I did not understand I install 2.08 or not in my GT-I9300I 4.4.4 To repair the Update the binary
[SuperSU] greyhd:
You still need to get a logcat, no matter what version you are running. The developer cannot solve your issue without a starting point.
[SuperSU] aamir.m.ali:
Hi Guys,

i'm trying to find a mirror that hosts supersu. i tried http://download.chainfire.eu/supersu and it keeps saying that the website is unavailable. anywhere else i can download it from?
[SuperSU] Pkt_Lnt:
Just downloaded it. You have something blocking you end, are you behind a firewall at work?
[SuperSU] JaCh0o:
Hello

I would like to report that versions of UPDATE-SuperSU2.01 an 2.02 aren't working on Oppo Find 7/7a. The just don't update the binaires - just install app. When I open app it ask me "Binaries have to be updated. Continue?: when press normal - "Installation failed. Reboot device and try again.", when pick TWRP/CWM - got same info. Only one working is this zipped update SuperSU: Find7_ROOT4.3_bbs.oppo.cn.zip also with your SuperSU 1.94 app.

On newest ColorOS (2.0.0i) it asks for update binaries -> Continue -> Normal -> Installation successful. When i let it update to newest version OR update to SuperSU Pro, it gives message "Binaries have to be updated. Continue?", but phone is rooted properly, every app is asking for root permissions and get granted. If press cancel still phone rooted, if continue (normal/TWRP/CWM) get installation failed. If i gonna uninstall update OR Pro version it stops asking and works properly. Please help. My knowledge is unsuffiecient to check where's the difference between Find7_ROOT4.3_bbs.oppo.cn.zip and UPDATE-SuperSU-v2.02.zip.

When I update by TWRP BETA-SuperSU-v2.08.zip, I got same message as 2.02 - "Binaries have to be updated. Continue?". Cancel - Phone not rooted, Continue Normal - "Installation failed. Reboot device and try again.", continue TWRP/CWM - reboots, then TWRP opens: done processing script file. After this phone reboots again and got info: SuperSU Binary files need to be updated. Same on BETA-SuperSU-v2.11.zip.

Phone info:

Oppo Find 7 (x9076)

ColorOS 2.0.0i (TWRP 2.7.1.3) (Rooted ??)
[SuperSU] Pkt_Lnt:
Did you try the beta that is working to solve this from the link Chainfire posted above?
[SuperSU] JaCh0o:
Yes. I've updated post #6534.
[SuperSU] jcarroyo:
Help

this is the logcat GT-I9300I android 4.4.4 (superSU 2.02) with errors do not know if this will help or I have to send View attachment log-error.txt problem binary update
[SuperSU] johndoe_71rus:
Hardware - Cubieboard 2

Software - cubieboard2_android_SDK_v1.09	http docs.cubieboard.org/tutorials/cb2/development/building_your_own_android_image

SuperSu latest from market

Install, please wait don't stop

logcat http paste.ubuntu.com/8332837/

Android runing SD card, this manual http shineworld.boxhost.me/doku/doku.php?id=cubieboard:bootandroidjbcb2sd

Thank you.
[SuperSU] volkmadi:
Store 2.01 - Stable 2.02?!

Hi,

I have a quick question.

The version here said to be the latest stable is 2.02. why does the version in the store still bring the 2.01?!

By the way, to split the thread in stable and beta was a good idea! :good:

Thx

Dirk
[SuperSU] txuki2005:
Miles thanks chainfire!

Testing it!

:good:
[SuperSU] jcarroyo:
after a day with 2,08 supersu again asked me to update binary. 4.4.4 GT-I9300I Android
[SuperSU] Pagozzi:
I got flashed my n5 with a CM11 nightlies with a built in superuser zip...I'd like to replace it with superSU...Do I got just downloading it from the play or I have to flash superSU zip via adb?
[SuperSU] johndoe_71rus:
Hardware - Cubieboard 2

Software - cubieboard2_android_SDK_v1.09 http docs.cubieboard.org/tutorials/cb2/development/building_your_own_android_image

Android runing SD card, this manual http shineworld.boxhost.me/doku/doku.php?id=cubieboard:bootandroidjbcb2sd

Don't work BETA-SuperSU-v2.08

logcat paste.ubuntu.com/8336679/
[SuperSU] AphotiC^:
You just download SuperSU from Play Store and launch it. It will ask you to update the su binaries by booting into recovery, just allow root access to it. After it is over, launch SuperSU app again and it will ass you to remove the older root access app. And you're done.
[SuperSU] zadigre:
I'm flashing the newest nightly on my device everyday. ..

The best option for me is to flash the nightly and the latest Supersu at the same time in the recovery... So no need to upgrade su binaries after the latest installation because it's already installed.

Envoyé de mon SM-N900W8 en utilisant Tapatalk
[SuperSU] Pagozzi:
Excuse me I'm not an expert in modding...So if I want a root acces using superSU on nightlies, all I got to do is to flash(via adb using sideload command?) the .zip of superSU after the flashing of the CM n...is that correct?
[SuperSU] zadigre:
What I do is download the latest nightly though cyandelta, I to into recovery and I install the latest nightly that I just downloaded and the latest supersu zip file

Envoyé de mon SM-N900W8 en utilisant Tapatalk
[SuperSU] Platinum1986:
Hi everyone,

I just updated my nexus 7 2012 from 4.3 JWR66Y to 4.4 KRT16O, i also installed the UPDATE-SuperSU-v2.02.zip with CWM. Now when i try to open Super SU i got this error:

What can i do to retrieve the root and get Super SU to work again?

I would be very grateful for your help, thank you.
[SuperSU] egingell:
Looks like you're not rooted. Did you consult the relevant forum for your device for how to root it?

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] zard:
[MENTION=631273]Chainfire[/MENTION] I tried using SuperSU in zip format downloaded from OP link with Xiaomi Mi Pad, using their Mi Recovery. I had renamed the file as update.zip and copied to root of internal storage, as required by Mi Recovery, but flashing failed. Tried on 2.02 stable zip and 2.08 beta zip. Is it because the current zip format is not compatible to MIUI Mi Recovery? Any possibilities of making it compatible?
[SuperSU] Dan1234567890:
Can you show the cwm screnn/log, after flashing SuperSU zip? Did it report some errors? Did you do a clean install?
[SuperSU] Platinum1986:
Thanks a lot for your help.

My Nexus 7 was rooted before i updated it to 4.4. Should i root it again with the nexus root tool kit?

In fact I got some errors with the 4.4 update flashable zip, i used this file.

Here is the log :

-- Installing: /sdcard/0/Download/grouper_krt16o.zip
Finding update package...
Opening update package...
Installing update...
arning: No files_contextsStock Android 4.4 installer
Extracting scripts...
Extractingarchive to tmp...
Extracting data to /system partition...
Extracing boot.img
Settings xattrs...
set_metadata: some changed failed
E: Error in /sdcard/0/Download/grouper_krt16o.zip
(Status 7)
Installation aborted.

I thought my tablet still was in 4.3 after this error but after the reboot it was in 4.4 :confused:

I didn't get any errors with the UPDATE-SuperSU-v2.02.zip, everything was OK if i remember well but i can't i find the log of this installation. There is no recovery.log in /sdcard/clockworkmod/.
[SuperSU] Dan1234567890:
Try clean rom flash again, and if you have some problems ask in respected rom thread if the flashing doesn't go as it should... [emoji106]
[SuperSU] Vagelis1608:
Hey [MENTION=631273]Chainfire[/MENTION] ,

Is it possible to add an option to preserve install-recovery.sh (with the line that points to install-recovery-2.sh) during "Full Unroot"?

I am asking because I have a mod at install-recovery-2.sh which can run while unrooted.

Sent from my D620R [Stock 4.4.2]
[SuperSU] birdie:
SuperSU 2.0.1 (the latest version installed from Google Play) silently grants SuperUser privileges to ES File Explorer.

What's even more worrying is that there's nothing in the logs! And no prompt at all.

Can you please look into that?

I have a Nexus 5 with stock Android 4.4.4 (rooted via TowelRoot).

Edit: There are people who experience the same problem.
[SuperSU] jazzruby:
This was already discussed just a few days ago.

A search in this thread for "ES File Explorer" results in:

http://xdaforums.com/showthread.php?p=55338769&highlight=es+file+explorer#post55338769

and 2 posts below it

http://xdaforums.com/showthread.php?p=55339167&highlight=es+file+explorer#post55339167

-JR-
[SuperSU] NZgeek:
Expected. Carry on.

Flash, as in from CWM/TWRP recovery? That should get you root access on its own.

Wiped all? Including /system? If you're switching from one ROM to another, it's often required that you wipe /system. This also removes SuperSU.

CM contains its own Superuser, which would overwrite all of the key SuperSU files. That's assuming there was anything there to overwrite.

Boot back into recovery, wipe /system and /data, then install (1) CM11, (2) GApps, then (3) SuperSU. Works perfectly for me, every time.
[SuperSU] hgmichna:
It wouldn't hurt to mention that step (3) is not needed to acquire root rights and should be done only if the user has a good reason for wanting it.
[SuperSU] egingell:
SuperSU is better. What more reason do you need?

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9