yashsingh1/xdaforums huggingface dataset:
[SuperSU] avicohh:
Thanks [MENTION=631273]Chainfire[/MENTION]

Like you said the file /system/etc/install-recovery.sh loses its executable bit.

I did some research, and it turn out that some files loses their permissions because the file_contexts file. (attached file from my device boot.img)

When i used the ext4utils to recompile the system.img, he used the file_contexts to label the files, and for some reason it's also change the permissions on some files.

e.x.

/system/xbin/su change from rwx to rws

/system/etc/install-recovery.sh change from 755 to 644.

Is there any way to modify the file_contexts file, and make him ignore the root files?

Thanks a lot.
[SuperSU] aeppacher:
Can someone mirror the latest? My university has blocked chainfires website as malware so it is inaccessible to me
[SuperSU] avicohh:
Here.
[SuperSU] HassanM:
Friends,

SuperSU 2.17 is out as well....
[SuperSU] AriStos13:
hello guys..i have htc one mini and i flash twrp recovery 2.6.3.0.. i push UPDATE-SuperSU-v2.16.zip into my phone and then i install the zip file.. when the operation completes the twrp informs me that it was successful. but when i run root checker app it says that the phone isnt rooted.

i also tried with UPDATE-SuperSU-v2.14.zip, 2.01, 1.51.

is anything that i can do to root my phone? what is the wrong i made?
[SuperSU] okidokiss:
Read the OP. SuperSU requires a already rooted phone.
[SuperSU] franczg:
,

Thanks!
[SuperSU] egingell:
The SuperSU app itself requires root, but flashing SuperSU from recovery *should* successfully root the phone.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] radz_:
But before you can flash the zip, you must have a custom recovery. And you must be rooted before you can you have a custom recovery...lol

So.. root the phone 1st using PC tool for your phone or framaroot or towelroot
[SuperSU] kingvortex:
You can have a custom recovery without being rooted. I rooted my device originally by flashing a custom recovery, then the SuperSU zip. ;)

Sent from my C6603
[SuperSU] AriStos13:
exactly but why my phone isnt rooted after i flashing twrp and the the supersu?? :/
[SuperSU] bsoplinger:
Thanks for the explanation. So that backup I did last week without having turned off the protect option is no good. I'll redo it right away.

Sent from my PG41200 using Xparent Purple Tapatalk 2
[SuperSU] Chainfire:
Well it depends on CWM/Nandroid version. On the firmware I'm currently on, it'll fail restoring *any* backup as long as OTA protection is turned on. It'll restore backups of "OTA protected firmwares", but the OTA protection will not actually work, though everything will indicate that it is functional.
[SuperSU] Stupifier:
Ok OK OK.....I dumb (call me ignorant and retarded please). I did not know you had to be S-Off in order do this stuff....am I correct about that? I'm Rooted S-on (simple root). I am now going through process to get S-off and will report back later tomorrow. Sorry to hassle everyone here.....nothing in OP mentioned needing S-off so I figured I was alright.
[SuperSU] x0952060001:
To use than the previous easy to use many
[SuperSU] dimebagdan65:
No need for S-Off... All that does is enable you to flash radios, firmware, and splash screens...
[SuperSU] Stupifier:
Well....I tell you what. After a little exhaustive process (still new to this) I got S-Off. Once I got S-Off, I was able to properly install BusyBox AND Update Binaries in SU.

Also, from my research, I'll be bold and say you are wrong. This does require S-Off.

In order to properly write to your system folder, NAND must be Unlocked...at least that is what a bunch of my research told me. NAND Unlock = S-Off.

In any event, I got EVERYTHING I wanted (and More, I flashed a WAY updated Radio). SU is updated and properly working. I've yet to truly play around with my phone since all this but I have a feeling its smooth sailing from here on. Thanks!
[SuperSU] nexus.prime:
Hi Chainfire

Thanks for your great works :)

But, Samba Filesharing still got FC on SuperSU v0.88

http://play.google.com/store/apps/details?id=com.funkyfresh.samba

Edit:

and Plz look into this and post in this thread :)

http://rootzwiki.com/topic/14685-24-apr-glados-v130/page__st__970#entry649269

http://rootzwiki.com/topic/14685-24-apr-glados-v130/page__st__990#entry651956
[SuperSU] dimebagdan65:
lol you're funny dude... FYI, I am NOT new to this ~.o

http://www.dimedroidhq.com/2012/03/if-youre-rooted-you-need-this-app.html

Nand unlocked is the HTC Unlock, S-Off is your security flag which allows you to flash radios, firmwares and splash images

And yes, I'm Hboot 1.5 and S-on...

---------- Post added at 04:36 PM ---------- Previous post was at 04:14 PM ----------

I posted this I dunno how many pages back, but apparently it could do with another posting...

How To Switch From Superuser To SuperSU The Right Way

---------- Post added at 04:45 PM ---------- Previous post was at 04:36 PM ----------

My question is, what is this "Simple Root" you speak of? I'm thinking that was your problem. Only way to properly root the Evo 3D on Hboot 1.5 is HTC's Unlock Method, then flashing a custom recovery, then superuser. By the time I rooted mine (After having two rooted single core devices, when I got the 3D I decided to take stock for a spin for a while, then 1.5 happened XD lol), there were so many guides out that I didn't even bother writing one or I'd link ya to it so you could compare what you did with the proper method and do some troubleshooting. But all this is moot now since you successfully bricked and revived and got S-Off now. I'm just curious what the initial problem was in case I hear something like this again in the future so I can help
[SuperSU] Stupifier:
Oh ya, its clear you are no novice...a simple glance at how many posts you got here tells me that (good lord).

I followed this guide and stopped after Step 2. I stopped because of what the guide author had said at the end of step 2. When I read it, it sounded a person could stop here and kinda be "simple rooted" (just a phrase I made up). I followed that guide to the letter...big time.

http://xdaforums.com/showthread.php?t=1306400

after that, I found out I had a real old "Superuser Permissions" app (the one that had the ninja for its icon). Everywhere I read said that "Superuser Permissions" app version with the Ninja icon was old. Furthermore, I was not able to write to my /system folder which made all sorts of headaches regarding installing BusyBox and updating the binaries for your SuperSU app. I could not move the eu.chainfire.supersu.apk to /System/App because of this. And yes, I did mount /system as writable using ES File Explorer before attempting that stuff. Also, Rom Manager would complain about privileges when attempting to "Fix Permissions". With all of that, All apps still reported me as rooted....what gives lol.

After all the nonsense, I went back to that very same guide and continued on in its steps to get S-Off. Once I did that, everything cleared up.

After I sorted out all the above issues, I happily and EASILY updated to a new Radio, Kernel, and threw on a bunch of Mods. No issues. That is why I figured S-Off was a requirement. With S-on....I couldn't do much of anything as stated above. After S-off, all steps given by guide authors were butter. I dunno, maybe those steps did more then just S-Off. According to the author:

Now that I look back at it myself, the worst thing was to stop at the end of Step 2 of the above rooting guide. Dunno why the Author of that rooting guide even mentions the possibility of stopping there. I hope this can help you clear up issues that future noobs (like me) have. If you'd like, I can try to spit up more details if something is unclear where my mistake may have been. Most everything is still fresh in my mind......but fading in happy elation. Cheers
[SuperSU] dimebagdan65:
You're rockin' the D'Inc?! Man, wish I would've known that lol Here I was thinkin you were on an Evo 3D like me lol I haz too many forum windows open and it's getting hard to keep track hahaha
[SuperSU] sparksco:
I believe with "s-on unlocked" you can write to the system partition in recovery but while your booted it won't let you. CWM zip = win?
[SuperSU] dimebagdan65:
With HTC phones, being S-On means that you can't write to the boot partition. You can flash to the /system partition, mount it as r/w or r/o all day long, but the minute you try to flash a kernel, radio or splash image it doesn't work unless you fastboot into recovery. With the Evo 3D (Maybe more, not sure), I know you can use 4EXT recovery to get around that little snag (Or Flash Image GUI or HTC Dumlock from Team Win) but you still can't flash radios/firmwares/Splash Images. To flash a radio or firmware you have to relock the phone to accept any OTA or RUU update, the unlock again and reroot.
[SuperSU] Stupifier:
Well I was having serious issues Installing BusyBox and Updating Binaries of SuperSU with my Dinc S-On Unlocked. Even if I flash SuperSU via Zip in CWM recovery (which I did), I still couldn't do the Update Binaries since that is done when phone boots up normal and you open SuperSU up.

Again I say, once I was S-off....everything was smooth sailing. I believe I mentioned in an earlier post that I was using a Droid Incredible....but oh well. Glad its all fixed up now
[SuperSU] vua777:
request: to ask permission for app sending SMS

The best on my One X.
[SuperSU] Pons:
That doesn't really pertain to su permissions. You could try a firewall app to block SMS from certain apps if you think an app is misusing them.
[SuperSU] dersh:
loosing root after flash

I was running a team EOS from. I installed supersu and all was working. I then disabled superuser in settings->apps. And all seemed fine.

The problem I ran into is that when I tried to update the from I lost root.

I think that what happened is that it updated the su back to the old version, but since I have superuser disabled it won't grant permissions so I can't update the binary for supersu.

I was able to go back to a backup I had, which is where I am now: supersu working and superuser disabled, but still present in /system/app.

Superuser doesn't seem to have a way to be reenabled in settings>apps.

If I can reenable it before the update then after I would just be able reinstall supersu. But I don't see how, so I am somewhat stuck right now.

Any suggestions?
[SuperSU] dersh:
The answer to getting superuser working again was actually just related to ICS, not really Superuser.

If you disable something in settings->apps they actually do still show up...but at the bottom of the list! They are no longer in their alphabetical place.

Once I figured that out I was able to re-enable superuser after the update, and can then re-activate superSU.
[SuperSU] lex25288:
SuperUser hasn't been updated since November 2011, so I figured I'd try this one and see how it goes.

My GN is on stock ROM, so I really liked the idea of the OTA Survival Mode.

I just bought the app from the Play Store, keep up the good work!
[SuperSU] McLongDong:
I can't gain access to my root explorer. I never saw the prompt to grant my access to it. Although if i change the settings of the superSU to grant instead of propmt, it works. Can you tell me why?
[SuperSU] ivAnash:
I've installed super-su from the market.. The free version.. Is the protect root option, that needs to be turned off during a backup available only in the Pro version.????
[SuperSU] shinra00:
Hi how are you?

I have two questions, I use cm11 unofficial since I have a sm-g3815 device and it isn't very popular, unfortunately.

I'm constantly flashing new builds and every time I do a clean installation, format system and all caches so it doesn't get messy.

Since I started to use CF supersu (because my cm11 has superuser pre-built), what I do is, flash the zip of cm11, then the Google Apps zip and then ChainFire's supersu zip.

When still on the recovery, when I pretend to leave it by doing a restart I always get a notification saying my root isn't correct and if I would like to correct it. I interpret this as, since I have a pre-built cm11 with a root base app and I installed on top CF one the device gets "confused". And I say, no don't correct the root. Am I interpretating this correctly?

Second one, I'm still on version 2.16 if I wish to update it, so I flash it on recovery or..? If I do a flash all the definitions of the will be lost and i have to grant access to all the apps again?

Thank you very much in advance
[SuperSU] jesssiii:
Look in your device specific threads for root info/options. Or google it.

LG G2 VS980
[SuperSU] Viper_21:
Problems with SuperSU

Device: Samsung Galaxy S3 | ROM: Stock JB 4.3 | Kernel: Boeffla 5.3b7 | Recovery: Philz Touch 6 | Mods: Xposed Framework

My woes started just over a week ago when I updated from SuperSu 2.01 to 2.16 (flashed update ZIP via recovery). When SuperSU app is installed, apps are no longer able to get root, and after about 2-3 minutes the phone either become totoally unresponsive (black screen) or reboots.

If I do a full uninstall of root (using the settings option in SuperSU), then boot into recovery and apply root (using the "Re-root system (SuperSU)" option in Philz), and then log on again, my phone works fine. All apps that were granted root beforehand, work well (I just can't grant root to any new apps). But the second I reinstall the SuperSU app either via Google play or flash via recovery, the same issues start up again.

I tried to restore my system partition when from v2.01 was installed, but that didn't fix anything.

Installing SuperSu 2.17-beta also doesn't fix anything.

For some reason I can't get adb to work on my PC (get an Error 5 and unable to start daemon message). I managed to get a short catlog and to save before my phone crashed (while SuperSu was installed). It's starts about a minute after phone reboots. I have attached the file.

I would be most grateful if someone could take a look at the log and let me know how to proceed. If you need a longer catlog then I can see if I can get a better log reading.

Thanks. :fingers-crossed:
[SuperSU] egingell:
If you live-flash a recovery (Mobile Odin), you need root, but not when using Download mode - if you did, every Android device would be stock with no possibility of rooting or using custom ROMs.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] Frank Westlake:
During a moment when you do have root run this in a terminal emulator and verify that the user and group ids are 50004:

ls -l /data/data/eu.chainfire.supersu.pro-1

Some might be 0 and the lib will be something else but I think the only other number on your device for that directory should be 50004.

Frank

EDIT:

I've never used DRM so I've made an assumption I shouldn't have. Change that command to:

ls -l /data/data/eu.chainfire.supersu*

Frank
[SuperSU] Viper_21:
Hi Frank. Thanks for your willingness to assist. I ran the command (from your edited post). It's Greek to me. I have attached the result. Please let me know what you think and next steps.
[SuperSU] egingell:
I don't know where you pulled that UID/GID from, but I've only ever seen IDs on stuff in the /data/data folder in the 10000 range (e.g. user u0_a123 is ID 10123).

Edit: And they're not the same between devices (e.g. SuperSU on my SGS4 is UID 10181 and 10094 on my SGS2).

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] Frank Westlake:
I should have included the '-n' option -- my 'ls' defaults to numeric IDs so I didn't think of it. I think if you do this Greek instead, the a275 might turn into 10275:

ls -l -n /data/data/eu.chainfire.supersu*

As I said, I don't know how DRM works. I can't use the play store. It might be that group 50004 only appears in the DRM area or it might be that your SuperSU data directory has a user ID that does not match the SuperSU application. Some things work because they are being done by 'su' as root user, and other things are causing system failure because SuperSU.apk is trying to write to it's home where it is no longer allowed. Did you mix backups and restores and installs?

If the problem is as my guess above then you can fix it by doing a normal application uninstall of SuperSU followed by a normal install. The 'su' binaries should remain in place and the SuperSU data directory should be replaced, I don't think a reboot is necessary. Uninstall, install. But this is only a guess and I have never uninstalled SuperSU.

Another option is to wait until Chainfire has looked at your logcat.

Frank

---------- Post added at 12:13 PM ---------- Previous post was at 12:00 PM ----------

It's in the logcat but I could very likely be mis-guessing its purpose.

Frank
[SuperSU] egingell:
Even if that is a valid ID on your device, it won't be the same on someone else's. UIDs are assigned arbitrarily by the device.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] Frank Westlake:
I didn't get '50004' from my device, I got it from his logcat.

11-01 21:19:54.745 D/MountService(2523): :::: getSecureContainerPath :: id = eu.chainfire.supersu.pro-1

11-01 21:19:54.755 D/MountService(2523): :::: fixPermissionsSecureContainer :: id = eu.chainfire.supersu.pro-1, gid = 50004, filename = pkg.apk

Now it looks to me more like it is an ID for the secure container, but the reported symptoms seem to me to be a mis-matched data directory ID.

Frank
[SuperSU] egingell:
I don't know what that is even referring to ("MountService" suggests that the container is being created (boot/pro key installed)), but I don't know from what that GID is coming.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] Viper_21:
Here's a screenshot before uninstalling SuperSU:

View attachment 2996310

And here's one after uninstalling then reinstalling SuperSU:

Most likely. I've done much installing/uninstalls/restores over the last week.
[SuperSU] Frank Westlake:
After you have used it long enough to know, let us know if uninstall/install fixed the problem.

Frank
[SuperSU] inphamous36:
Does anyone, who was having problems with the popup menu not being responsive, downloaded and tried the 2.17 beta? Does it fix this problem? Right now I'm doing fine with 2.14, but I think having the latest version will be better in the long run.
[SuperSU] egingell:
The "problem" is not with SuperSU. Please read the last few pages in this thread.

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] Viper_21:
Everything was fine with SuperSU on my device -- used it for over an hour.... until I rebooted. After reboot things starting going crazy again. Then when I uninstalled SuperSU it's fine again. Grrrrrr.
[SuperSU] Frank Westlake:
I think that means the problem is not solved. Sorry I couldn't help.

Frank
[SuperSU] inphamous36:
I read back to page 712, I could not find any solution to this problem
[SuperSU] mendozaram:
Hi, how do i unroot/uninstall supersu from muy phone? Thx
[SuperSU] zadigre:
There's an option for that right in the Supersu app...

Envoyé de mon SM-P900 en utilisant Tapatalk
[SuperSU] mendozaram:
Thanx, i found it
[SuperSU] Bryce1488:
//

~[{¤}]<Federal
[SuperSU] aeppacher:
Just a heads up [MENTION=631273]Chainfire[/MENTION] this is why you might start getting blocked from different people. My university has already blocked your site unfortunately despite my repeated emails pointing out you arent hostint malware. Apparently plenty of companies and school use this service to identify who to block.

https://www.virustotal.com/en/domain/download.chainfire.eu/information/
[SuperSU] Scipizoa:
Seems like another overzelous site not designed proper so it'll pick up harmess websites
[SuperSU] beany>:
The site is picking up from anti virus softwares and they usually detect something that changes fundmentals like root as malware. I can't see how it can be changed as it seems to be the nature of the beast.
[SuperSU] CyberpodS2:
From a corporate perspective, root by its very nature is seen as a bypassing of security.
[SuperSU] Jaybatch:
Temporary Unroot

How do you use the Temporary Unroot feature? I have a Samsung update that's trying to install and I keep getting an error message during the installation. I updated my version of SuperSU in the Google Play store today to v2.01 but I don't see an option for Temporary Unrooting.
[SuperSU] IT_Architect:
Where can we download 2.16? The play store only has 2.01.
[SuperSU] Ritvars:
Read the OP.
[SuperSU] IT_Architect:
That is where I started. Basically, the only way I see to get the latest stable is through the zip. The latest Amazon has is 2.1.2
[SuperSU] Ritvars:
Then zip it is. Good luck.
[SuperSU] 65vdub:
Click on the link that says CWM/TWRP/MOBILE ODIN flashable zip, open in any root browser to look inside the zip, then click on the common folder and then click the super su apk to install
[SuperSU] IT_Architect:
Thank you! That is useful information. I have many years on other phone operating systems, but this is my first Android and I'm rooting to get a decent my Bluetooth call recording back and a decent backup.

Thanks!
[SuperSU] 65vdub:
You're welcome, glad I could be of assistance [emoji5]

Edit: forgot to mention that once you click on the link it will take you to chainfire's website. Click on the supersu zip in the website to download it, then follow the steps of my previous post.
[SuperSU] IT_Architect:
Yes, I have it already. So from what I understand, all I need to do is unzip it on my SD card, then go to the common directory, and run the .apk and it will install?

Thanks tons!
[SuperSU] claytonjn:
Correct. You should then open the app to have it prompt you to update the binaries.
[SuperSU] 65vdub:
Yes that would be it. If the install is blocked go to settings, security, and make sure unknown sources are checked and that verify apps is unchecked then proceed to retry installing super su.
[SuperSU] aeppacher:
Since when is gaining control of your device malware? Like windows ships with administration mode, linux with su. How is it malware for android? I persisted and the site is now whitelisted at my school.
[SuperSU] IT_Architect:
I've done some more reading about KNOX and how it works.

- Verizon says the boot loader looks for the KNOX files, thus it's best not to remove or move them if you root.

- Earlier versions have an app where you can turn off KNOX, but KitKat 4.4.2 does not.

- If you unroot the phone, do a factory reset, and if KNOX is still not active, you haven't fooled Verizon even if the KNOX counter is at 0x0, and you are at their mercy for support and warranty purposes. Moreover, you could never sell the phone to someone who needs the KNOX.

My question is: When SuperSU disables it, does it also enable it when you unroot?
[SuperSU] smknutson:
How would they know about the third statement?
[SuperSU] egingell:
I'm sure they have they're ways; however, it's unlikely that they would check more than the KNOX bit.

My phone is covered by Best Buy's Geek Squad - no questions asked (aside from curiosity).

Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
[SuperSU] IT_Architect:
That's a great idea.

---------- Post added at 05:59 PM ---------- Previous post was at 05:33 PM ----------

That's easy, it wouldn't be running, which is easily discoverable in Application Manager.
[SuperSU] inphamous36:
I've read back about 20 pages and I don't see any solution. If you could please direct me that would be great. I do apologize for missing it. I just did not see it.
[SuperSU] zadigre:
I will make it easy for you...

You probably have two options... First is to find the probable app that might interfere with Supersu (ex Lux). One of your app might add an overlay that will trigger the tapjacking protection. Those apps usually have a white list to disable the overlay for apps like Supersu.

If you cannot find which app, disable the tapjacking protection in Supersu and see if it's working after that.

Envoyé de mon SM-N900W8 en utilisant Tapatalk
[SuperSU] beany>:
I didn't say it was malware, I actually agree with you. But unfortunately that's how things get pigeon-holed. Because it may be used maliciously.