yashsingh1/xdaforums huggingface dataset:
[SuperSU] tumas04:
Since Android N is very close to be officially released (and the Android N Thread refers to the Beta Thread which shows the same version (2.76) as the stable version). Will it (with SuperSU 2.76) be possible to root the official Android N Release?
[SuperSU] a g bell:
Well unless someone's tried who knows l just want the new supersu team to show they mean business and push an update soon after n is released
[SuperSU] Sam Nakamura:
1st thing to do is to provide more info like the model number and not only the manufacturer...
[SuperSU] BlakeDC:
via me wiping my device...i'm going to try right now ;)
[SuperSU] bagarwa:
I'm also interested in knowing this. Does v2.76 root Android N and does it disable the force-encrypt flag of the stock boot.img. I don't want my device storage to get encrypted.
[SuperSU] Mepsipax:
Hey thanks for getting back to me. The issue seems to have resolved itself. Only thing I did differently now is I let it update itself via the OS instead of TWRP.
[SuperSU] kingracer:
I've installed latest supersu 2.76 via latest twrp with Android 7 support on my Nexus 5x and it still can't make changes in /system :( is it fixable?
[SuperSU] H4X0R46:
Does SuperSU 2.67 work with Android 7.0? Got a Nexus 6 here and waiting for the update! Excited! Does it currently work?
[SuperSU] TW1ST3D1NS4N3:
Cf autoroot
[SuperSU] H4X0R46:
Is auto root needed? Flashing the zip doesn't work?
[SuperSU] Portgas D. Ace:
From the OP:
[SuperSU] H4X0R46:
Well yea, I know that. But I'm talking about the TWRP flashable zip.
[SuperSU] TW1ST3D1NS4N3:
http://www.teamandroid.com/2016/07/19/root-nexus-5x-android-n-npd90g-developer-preview-5/2/
[SuperSU] egingell:
That's only if you install it like a normal app. Flashing from a custom recovery doesn't need root. I don't know how N works, but with M and lower, flashing works fine.

Sent from: SGS5 - MM 6.0.1 / SGS4 - LP 5.0.1
[SuperSU] Portgas D. Ace:
Ah, I see. It's early in the morning here, haven't had my coffee yet :silly:

Yes, flashing the .zip file from recovery will root your Nexus device and install SuperSU, whereas installing SuperSU from Play Store requires a rooted device.
[SuperSU] H4X0R46:
Ahh coffee, the only reason to wake up for most, myself included xD thanks guys! We'll see when Nougat reaches the Shamu! Cheers! :D
[SuperSU] ST Dog:
Anyone know of written out instructions to install to a system image mounted on Linux host.

The equivalent of installing with TWRP but w/o the script.

I've tried to make sense if the script but SH/BASH was never a strong point for me.
[SuperSU] grep_i:
My guess is you mean installing flashable zips without custom recovery.

You can install flashable zips with ADB sideload command just use the search function on this forum to find more information about it.

If this is not what you mean please clarify yourself and be very specific.
[SuperSU] frwerewolf:
Hello i have the latest supersu pro on my galaxy s7 edge. But clean master doesnt work for his autostart manager. Even if root is granted it says root access failed.

I have read in treads somewhere that if i flash v2. 49 it will work then.. But is there any danger to downgrade my supersu like this ?

Thanks for your help
[SuperSU] apogee82:
Me too! I have the same issue with /system not taking changes on my 6P. I tried setting the kernel to permissive but no dice. I think we need a modified boot.img? Not sure.

Otherwise root works normally if apps request privileges.
[SuperSU] kingracer:
Actually, i forgot to write that, but i think i found what is going on with root. Some apps are getting normal root privileges and some are not, i read that it's because of speceification of each app and for me now ES File Explorer, AdFree and Root Browser can write in /system when MiXplorer and AdAway can't.:confused:
[SuperSU] grep_i:
Most probably that is because those apps have the su path hardcoded in system, so they only work if you have a Supersu in systemmode the developers of these apps did not update their apps against [MENTION=631273]Chainfire[/MENTION]'s recommendation.

This has already been covered in the SuperSU threads for page after page.

Just search for Supersu compatibility mode and you will find a fix or workaround.

The best would be if the developer or anyone else with developer skills would update the app to [MENTION=631273]Chainfire[/MENTION]'s recommendation.
[SuperSU] bagarwa:
Want to keep storage unencrypted

I have Nexus 6P, Stock Android 6.0.1 August, SuperSu v2.76, franco kernel r27, Unencrypted storage.

I plan to do a factory reset from twrp before flashing the N image. After I do that, I don't want my storage to get encrypted.

So, I will flash twrp-3.0.2-1-angler.img and then SuperSu v2.76. Will that be enough to keep the storage unencrypted?
[SuperSU] kingracer:
But i thought that apps shouldn't work also on 6.0 because there is the same method to install supersu? Or i'm wrong?
[SuperSU] apogee82:
This isn't the case. Both AdAway and EmojiSwitcher worked fine on MM with Systemless Root. Something else is going on here. I tried setting running SuperSU in compatibility mode with no luck.
[SuperSU] grep_i:
I do not understand what you mean to say, can you be more clear or specific ?

Just now I see you are trying this on Android Nougat (7).

Sorry for my mistake I really can't help you there as I have no experience with using that version of Android yet.
[SuperSU] kingracer:
Sorry, my English is not good :( I mean that those apps should be updated to work without supersu in systemmode because either on 6.0 and on 7.0 supersu script working alls the same and on 6.0 those apps are working fine but on 7.0 they don't. I hope i wrote it understantable... :angel:
[SuperSU] H4X0R46:
I want to know this as well! Does the SuperSU zip turn off forced encryption? Or is a custom kernel needed?
[SuperSU] depressed_:
Damn I wanna have flashable zip for 6.0.1 already. Wanna restore DRM keys but without it no way.
[SuperSU] egingell:
What are you talking about? The flashable zip in the OP is for all Android versions.

Sent from: SGS5 - MM 6.0.1 / SGS4 - LP 5.0.1
[SuperSU] simmeone:
Hi, I read that Google make Android 7 harder to root. Is it necessary to root Android in the future? And what does it mean for future Android versions? In future no root? Will Google go the same way like Apple, an total close os, where customers can nothing decide.
[SuperSU] depressed_:
SU 2.76 Does not work on M4 Aqua 6.0.1
[SuperSU] egingell:
In the future, when you post problems and/or requests, include your device model. Also, check this thread in your device's forum.

Sent from: SGS5 - MM 6.0.1 / SGS4 - LP 5.0.1
[SuperSU] asc1977:
I have a question and sorry if already posted or asked.

If I flash my Rom the supers 2.76 it's included in flashing. So if I do again a dirty flash and again and again and again the supers app comes and goes in appdrawer. I didn't installed that app from playstore. Only with flashing supersu zip.

Anyone same problem or know why?
[SuperSU] floepie:
Maybe silly question: Previously, beta versions referred to systemless rooting whereas the stable versions wrote directly to system. It seems that the stable version beginning with this version now is systemless as well?
[SuperSU] :
If I'm not mistaken it will attempt to go systemless, if not then via system
[SuperSU] nunopenim:
It will detect compatibility. It is always preferable to write to system, but in MM, this would brick, so there was need for systemless. After detecting the device has MM or up, it will patch the boot image, for systemless compatibility.

Sent from my GT-I8730 running Slim6 ALPHA 0.10
[SuperSU] :
I see, thanks for the info
[SuperSU] ianmacd:
That's a matter of opinion. There are several significant advantages to not writing to system.
[SuperSU] nunopenim:
Yes, one of them probably is not having a modified system partition.

Sent from my GT-I8730 running Slim6 ALPHA 0.10
[SuperSU] egingell:
That's pretty much the only perk.

I don't get why people worry about it. OTAs aren't often and when they do pop, there are options other than just letting the phone do it automatically. Like Odin, Flashfire/Mobile Odin, and even TWRP (maybe--I've never tried).

Edit: Oh, and Android Pay and Samsung Pay won't work with a modded system even if root is removed.

Sent from: SGS5 - MM 6.0.1 / SGS4 - LP 5.0.1
[SuperSU] nunopenim:
I think even systemless root modifies the system...

Not the system partition, but system status would say Custom too, I believe.

Sent from my GT-I8730 running Slim6 ALPHA 0.10
[SuperSU] beren:
is 2.76 working on android 7 final release (NRD90M build)as with previous beta?

(nexus 6P)
[SuperSU] nellycruzz:
I'm running pure nexus can someone tell me if I boor info recovery and flash this, will it work or put me in a bootloop?
[SuperSU] Pkt_Lnt:
Choice A for thousands of us on Pure Nexus. You can do it system or systemless, your choice. Look at the Pure Nexus FAQ for more info.
[SuperSU] 0.0:
Fyi, installing systemless SuperSU breaks Android Pay on final (official) version of Android Nougat. I am on Nexus 5X
[SuperSU] osm0sis:
No, there was a server side change to Android Pay/SafetyNet several weeks ago so it now is able to detect systemless root again.
[SuperSU] player615:
Please can u think about Che2-l11 marshmellow?

He's still in bootloap
[SuperSU] egingell:
Can you find the right thread for support?

Sent from: SGS5 - MM 6.0.1 / SGS4 - LP 5.0.1
[SuperSU] paieneso:
Hi

Could anybody confirm how to downgrade to SuperSU 2.67? Can I just flash the Su 2.67 zip over and that is it? ( Do I have to wipe anything in the process?) Anything else to be done?

I have now SU 2.76 on an Onplus 3 running stock firmware Oxygen OS 3.2.2 Android 6.0.1 (as well as a bunch of Xposed modules), and I would like to get Viper4Android running. Unfortunately, the installation of the drivers does nothing. I have done some research and apparently it is caused by the system being set to enforcing instead of permissive.

So, in order to change that, it seems that I can use a selinux change app if I have SU 2.67 or lower. Hence my question.

I know I should not set my system to permissive, and I do not really want to. However, I do want to have V4A so if anybody knows any alternatives I am all ears (or eyes more accurately)

Thanks

---------- Post added at 09:16 PM ---------- Previous post was at 09:14 PM ----------

Hi [MENTION=631273]Chainfire[/MENTION] and everybody else,

Could anybody confirm how to downgrade to SuperSU 2.67? Can I just flash the Su 2.67 zip over and that is it? ( Do I have to wipe anything in the process?) Anything else to be done?

I have now SU 2.76 on an Onplus 3 running stock firmware Oxygen OS 3.2.2 Android 6.0.1 (as well as a bunch of Xposed modules), and I would like to get Viper4Android running. Unfortunately, the installation of the drivers does nothing. I have done some research and apparently it is caused by the system being set to enforcing instead of permissive.

So, in order to change that, it seems that I can use a selinux change app if I have SU 2.67 or lower. Hence my question.

I know I should not set my system to permissive, and I do not really want to. However, I do want to have V4A so if anybody knows any alternatives I am all ears (or eyes more accurately)

Thanks
[SuperSU] seanhanrei2000:
there is a problem with supersu when using it with gameguardian..
[SuperSU] egingell:
That's a GameGuardian problem.

Sent from: SGS5 - MM 6.0.1 / SGS4 - LP 5.0.1
[SuperSU] grep_i:
You could try and install Magisk framework and install viper4android in it maybe this resolves your issue.

I've read people successfully installed it that way search for the Magisk framework thread there are instructions on how to do it.
[SuperSU] paieneso:
Hi, thanks for your reply and the suggestion.

I've read somewhere abut this magisk framework and I believe there is even a magisk version of supersu that can be used and resolves the selinux issue. However, I could not find it. I'll do some more research.

In any case, can you or anybody else confirm how the downgrade to SuperSU 2.67 could be made (even if it is just for curiosity).

Thanks
[SuperSU] grep_i:
You could flash old version but just to be sure use unroot from within the SuperSU app and than flash SuperSU older version from custom recovery.

For Magisk you could start here

http://xdaforums.com/showthread.php?t=3388268
[SuperSU] ST Dog:
No, no running system at all.

So I have system.img loopback mounted on Linux. There I can modify anything in the file system I want.

So, what files/links need to be put where to mimic what the update script in the zip would do.

I get part of it, but my sh/bash comprehension isn't good enough to be sure.

I just want to do the steps of the update script manually, one at a time.

Think of it as creating a complete custom ROM on a Linux host that includes SuperSU.

I would then flash the changed system.img to the device.

This would be a system mode install, no the systemless version.
[SuperSU] dasacom:
Hello together,

I have a problem and need your help :)

You have to know that I am new to android: I was on IOS for more than 6 years. Here is my problem:

I was used to tap on the status bar with my iphone to scroll up the page. This is possible on android with the app: oneclickscroll root

This does not work with my one plus 3.

The developer of one click scroll root said that it is an issue with supersu

See attached email:

"Hi,

It sounds like superSU issue with selinux in your device. I dont have any good solution other than wait for newer superSU update. I think your superSU is the latest beta version and there is nothing newer than that. You could also try to update your rom to other custom build. That way, I am sure you can get a properly working superSU enviromnent. "

Someone here with an idea? Can I downgrade the SuperSU. I am running latest v2.76

I do not know what selinux is. Maybe someone can suggest an older version of superSU.

Thank you so much for your help.

Kind regards, dasacom
[SuperSU] hacknmtk:
Downgrading won't make any difference. It's not a SuperSU problem, it's a problem with SELinux and trying to find a work around that doesn't "break" the phone.

SELinux is Android's way of securing the phone from any outside attacks. It also makes modification on Lollipop and newer versions very difficult to work around.
[SuperSU] Chainfire:
Assuming SuperSU works at all on the One Plus 3 (I honestly don't know), if the app is not able to do something due to SELinux restrictions, SuperSU comes with the supolicy tool the developer can use to change SELinux rules as his apps needs them. That is the job for that app / developer. It is not the job of SuperSU to make sure that every app runs out-of-the-box with SELinux. That would be impossible to do without disabling SELinux completely.
[SuperSU] dasacom:
Hi, thank you for your reply. I will ask the app developer.

And yes, SuperSU works fine with OnePlus3 :)

Thank you for your great app and support

[MENTION=7601016]hacknmtk[/MENTION]

thanks for explaining. I got it.
[SuperSU] :
I find the Oneclick scroll app developer's response comical, particularly as he hasn't updated it since April 2015.
[SuperSU] hacknmtk:
It's not my app. [MENTION=631273]Chainfire[/MENTION] is the one that created it.

I just wanted to clear that up so I'm not getting undue credit.
[SuperSU] Riku Azhurlar:
so heres a fun one. currently im running on a oneplus 3 with AICP rom installed. keeping supersu as a user app it works great. when i try to install it into the system though thats where things get fun. it dissapears and closes like it should. i reboot my phone. still not there, following directions i go to reinstall from Gplay it says its installed. i try to open it. nothing happens. it says its installed. i ant uninstall or open it........ but when an app asks for root a prompt window still appears....... any ideas how to fix?
[SuperSU] pkelly517:
Custom ROMs will often put SuperSU access under Settings, removing it from the app drawer.

Maybe?

If that's not it, it sounds like an AICP specific question.
[SuperSU] Riku Azhurlar:
sure enough i look in the settings and in the weirdest and last category i would have ever expected it to hide under there it was wow im blind. Thanks!
[SuperSU] hacknmtk:
Check in the OP. There's a way to get back into the app using the dial pad, although it may not work for all phones.
[SuperSU] delro92:
So, after flashing TWRP keeping it read only, and installing SuperSu 2.76 on my XT1644 (Moto G4 Plus 64Gb) and not doing ANYTHING else, the phone is stuck booting at the "moto powered by android" logo. Any idea what might have happened and how to fix it?

EDIT: Waited it out for about 5 minutes and now the screen has gone black... I hate none nexus phone so freaking much.
[SuperSU] hacknmtk:
It sounds like you flashed the wrong TWRP for your phone. And what do you mean you installed it RO?
[SuperSU] delro92:
First, thanks for the quick reply, now onto the problem: I used the only .img for athene on twrp.me (this one: https://dl.twrp.me/athene/twrp-3.0.2-0-athene.img.html) and on the first run it asked if I wanted make it work in read only mode (which works perfectly on my Nexus 6P) which I accepted. With only twrp installed (not supersu) the phone booted normally but once I went back to twrp and flashed supersu 2.76 the phone stopped booting. At the moment I'm looking for the original factory image, which, compared to the Nexus 6P's one is proving quite hard to find for whatever stupid reason.
[SuperSU] hacknmtk:
You didn't make a backup first? That's the best way to make sure you have the stock recovery.img.

I would try to install it RW instead of RO and see if anything changes.
[SuperSU] davidzhaoooooo:
Hello to the dev. Will v2.77 work on note7 SM-N930FD?
[SuperSU] ipdev:
Might have better luck asking in the beta thread. :o

http://xdaforums.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133

https://plus.google.com/+Chainfire/posts/S4ucYdfqPhq

- Note :

I do have BETA-SuperSU-v2.77-20160827190633 running on all my devices. (4.x - 6.x)

-- Jagged up my nexus9 last night, so no official nougat to try on. (Dumb mistake ;) )
[SuperSU] vergilbt:
Hi [MENTION=631273]Chainfire[/MENTION], any news with issue when want using "SeLinux mode changer" app?
[SuperSU] quendo9:
Why should I want to change the state of SeLinux?? Are there apps that check the mode of it...?
[SuperSU] vergilbt:
Yes, viper4android for example...
[SuperSU] segv11:
Can we stay on topic?!?

This happens everytime Chainfire goes on vacation: this thread deteriorates into a complaint-fest and people whining about closed-source. And when he comes back he has to dig through all this **** to see if there is anything real to respond to.

Look, I like open source too: that's how I prefer to code. But if this were my app, I would not release source either.

Remember that SuperSU has a "survival mode" to backup the su binary. This backup needs to remain hidden because there are plenty of snoopy apps and carriers out there that like to screw with us rooters. SuperSU is effectively playing a game of cat and mouse with keeping the backup hidden, and releasing source would just announce to the world where the backup is hidden.

Sent from my Jelly Beaned Galaxy Nexus.
[SuperSU] G3-SCORPIO:
I uploaded the above screenshots. Especially for people like you! I do not like it when smart, not understanding what I mean!

The conversation is over!
[SuperSU] danieldmm:
Did you read Chainfire blog? Maybe it's the programs you talk that make a bad call to ROOT.

Cheers

Enviado pela minha bomba i9100 através doTapaTalk.
[SuperSU] G3-SCORPIO:
The program Superuser do not. The only problem SuperSU.

I have not read the blog. There is a list of programs that might be a mistake? If there is a special list, I would like to look the link.

Now began testing ES Explorer. And found that he too can not get ROOT. Put Superuser, and everything was as it should.

I do not use just two of the program. I only use one of the programs - "Superuser"

Now I see only one reason not to stable operation. Different firmware - different components of the toolbox. We must do more integration for different teams SuperSU. And it is quite possible, even to expand a set of commands for different devices.
[SuperSU] shaggyskunk:
Thought that the "conversation was over"?

In any event SuperSU works fine with esExporer, along with every single app that I have that requires root!

Sent from, The Eclectic Chair.
[SuperSU] G3-SCORPIO:
Are you familiar with the toolbox? You have it in the firmware is completely different. The fact that it works for you, I do not doubt it. But this is not a model. Not only do I have a problem.

I am very happy for you that you are running. When put 200 programs, then we can talk about something.
[SuperSU] shaggyskunk:
Ok sparky, let's just have you try to figure out why YOU can't get esExporer to get root, when everyone else can.... That's just one program! Who in blazes knows what you're other 199 are, maybe it's YOUR device that is the problem?!

Sent from, The Eclectic Chair.
[SuperSU] G3-SCORPIO:
Only this program is working and not getting ROOT. Other work well.

And the program bad work Multi Mount SD-Card

Let's check something. Here is our program. Place yourself on the phone. I want to check out as you have it will work.

Apply yourself tweaks. The program is stable at 100%
[SuperSU] shaggyskunk:
I'd rather not install this apk. I kinda like stability etc

Sent from, The Eclectic Chair.
[SuperSU] G3-SCORPIO:
Well, then, and do not have to argue with me. I am well versed in the components of the system. I understand how the program should work. You can imagine that different firmware SuperSU may behave differently.
[SuperSU] Pkt_Lnt:
Then use what works and stop whining. My gawd..............
[SuperSU] G3-SCORPIO:
shaggyskunk Version I gave above, works fine. Checked.

Pkt_Lnt Politely need to communicate. So keep in touch with their same age.
[SuperSU] jwds1978:
At last count, I had 30 root-dependant applications installed. Working great and good performance.

--

Sent via Tapatalk 2 from my TELUS HTC Amaze 4G on the Fido network.
[SuperSU] G3-SCORPIO:
And you are separate from the Superuser? Or use the two programs together?
[SuperSU] jwds1978:
On previous ROMs, I left the Superuser .APK installed, but replaced the Superuser SU binary with the SuperSU binary. The reason was that some applications, at the fault of that particular application's developer and not Chainfire's, checked for the existence of the Superuser .APK to determine if root access was available on-device rather actually attempting to gain root access and reporting failure/success of the attempt. With this ROM though, I've only ever used SuperSU, Superuser hasn't ever been installed on it; nor will it be.
[SuperSU] G3-SCORPIO:
I deleted the root user. I have in my system / app installed as SuperSU.

Could this be a problem, I do not know. Perhaps blame busybox.

Tell me what version of busybox you worth?
[SuperSU] jwds1978:
I have SuperSU as a system application. As for BusyBox, the version currently installed was 1.20.1-Stericson the last time I'd actually checked it; using BusyBox Pro by Stephen (Stericson) to keep it automatically updated.
[SuperSU] shaggyskunk:
Stephen Ericsson v8.9 pro

Sent from, The Eclectic Chair.
[SuperSU] G3-SCORPIO:
Found the problem!

In general I found the problem is in SuperSU. It now remains for someone to confirm this.

1) Go into the program SuperSU PRO, put a tick in the last: "Full content".

2) Go to the ES Explorer and check if there is a ROOT access.

I have, if "Full content", then changing the PATH variable and disappears the ROOT in "ES Explorer".

If I put - "Access only", and then I go to the ES Explorer, then all well and have a root.

Check for yourself and confirm please.

Write a response to me. Is there such at all, or not at all.

Everything is written in unison, there is no glitch. Why now all silent?
[SuperSU] jeliado:
superuser question

I accidentally installed superuser from the ROM manager app in top of my all ready existing superuser from the galaxy nexus toolkit. Will this cause any problems? Could I go back to the original superuser app from the toolkit?
[SuperSU] Chainfire:
supolicy --live "permissive *"
[SuperSU] :
Word up. SU gangstas.