yashsingh1/xdaforums huggingface dataset:
[SuperSU] Ch3vr0n:
Works just fine here on March updates

Sent from my Nexus 6P with Tapatalk.
[SuperSU] cowboy_ea:
Hi guys

I`ve Htc A9 device,after updating to android 7 Nougat 2.18.617.1 ver i bounded up to Interesting problem,i did install TWRP 3.0.3-8 and boot to recovery mode then i tried flash SuperSU 2.79 stable ver,everything did done very well then i boot my device in normally mode, i see SU app in my list but don`t working!!!!

For Example LINK2SD asq to grant permission to supersu and i accept but when i`m using this app to unistalling system apps LINK2SD show me Unistall completed but don`t work and i see those app in my list.i checked by root cheker and i see my device not rooted!!!!
[SuperSU] Rami04:
My S6 with Stock Nougat can't root with SU 2.79 SR3

It stops when Creating Image
[SuperSU] mielletseed:
Maybe the same issue and this one helps?

https://xdaforums.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133/post70985800#post70985800
[SuperSU] Kaito95:
Yes, it works perfectly after doing this step. Tested on my Galaxy S6 with stock Android 7.0 (G920FXXU5EQBG) :good:
[SuperSU] huismeester:
I did a full unroot on my s7 edge rooted stock rom but the phone will boot into twrp
[SuperSU] ulxerker:
you'll have to flash stock recovery, too.
[SuperSU] huismeester:
Hi Sir did you no a link for stock recovery Galaxy S7 edge
[SuperSU] peterlee928:
hi all apologies in advance for the noob q's :)

is this version of supersu compatible with the latest twrp version 3.1?

also, r there any specific steps that need to be taken when installing the appropriate twrp 3.1-compatible supersu (eg delete fstab.marlin file prior to installing supersu )?

much thx in advance :)
[SuperSU] ulxerker:
http://rootmygalaxy.net/download-install-stock-firmware-samsung-galaxy-s7-edge-sm-g935f/

for further questions please refer to the appropriate S7 edge subforum.
[SuperSU] ZRK_NanDRD:
Yes it's compatible TWRP 3.1-I've just flashed it as I've updated the rom RR N (120317) & there's no specific steps to be considered, just flash & reboot.
[SuperSU] kurtph1969:
Thank you. Following these instructions, worked perfectly Samsung Galaxy S6 stock 7.1
[SuperSU] kurtph1969:
No MTP connection to PC

I now have an issue. It would seem that my PC cannot recognise my phone after flashing the latest SU on nougat on my Samsung Galaxy S6. It was working before. MTP is enabled. Anyone help please?
[SuperSU] Alxoom33:
Try updating your drivers on the pc.
[SuperSU] kurtph1969:
No. It's not the pc. It worked before I flashed su
[SuperSU] jcmm11:
If you're PC can't recognize a hardware device that's connected to it then it is the PC, unless the hardware device has something physically wrong with it.

Do you have the newest drivers? If not what does it hurt to try that first.

If you remove su does the PC recognize it again?

If the device was recognized, but you couldn't connect, you might have more of a case (although even then it's highly unlikely). In any case see what happens with updated drivers. If that doesn't work see what happens if you remove su.
[SuperSU] Alxoom33:
SU does not make it so that the PC dosen't recognize your phone. It's your PC or its your cable. Otherwise, your phone is broken. But it's not Su.
[SuperSU] dahawthorne:
I agree that flashing SU is at best a coincidence. My Nexus 6 refuses to be recognised recently despite all efforts to install drivers, removing & reinstalling in Device Manager, every trick I can think of. Strangely it's seen in ADB/Fastboot, so it's not a cable or port problem.

I've had 2.79R3 for weeks, and strangely the Nexus 6 appears fine in my old laptop, also on Windows 10. Definitely something on the laptop, not the device.
[SuperSU] spainter:
My Windows 10 desktop came up with a set of Le Mobile drivers the other day that played havoc on the google drivers for my Nexus phones and tablets. Had to uninstall all the drivers and force install the google drivers again to get the Nexus devices to be properly recognized.
[SuperSU] jayf99:
Unless its the wrong version of SU.
[SuperSU] NLBeev:
http://www.drivethelife.com/windows...remove-driver-on-windows-10-8-7-xp-vista.html

Useful info about drivers and Windows.
[SuperSU] kurtph1969:
I know it sounds bizarre. Let me explain in more detail:

I flashed stock nougat for SM-G920f (from Samsung Updates) in Odin. Booted phone -shows up fine on pc. Next, installed latest TWRP for nougat and then SuperSU-v2.79-201612051815 (following [MENTION=631273]Chainfire[/MENTION] 's instructions to make it boot correctly).

When I restarted phone and connected to pc I noticed I'm not getting the prompt either on the computer or phone. When I pull down the notification shade there's no connection status either (charging, MTP, etc.) On the computer in device manager the phone IS there but does not show up in file explorer for Windows 10. I also tried changing the USB settings in Developer options but that didn't help.

Just to check. I wiped the phone again and put stock nougat back on and hey ho, I can see the phone again in Windows file explorer! So I'm not saying it's directly rooting which is the issue, but the version of nougat I installed seemed to be affected by flashing superuser. Maybe someone else with a Samsung Galaxy S6 flat could test this?
[SuperSU] zameer_yus:
Custom Binary Blocked by FRP Lock

hello dear chainfire

today i root SM-G570F with this latest version (SuperSU-v2.79-SR3-20170114223742.zip) phone was rooted successful but when i add google account and then restart the phone

phone stuck on bootloop , its says Custom Binary Blocked by FRP Lock

please disable Frp lock in your next update
[SuperSU] Ch3vr0n:
Frp is Factory Reset Protection, doubt it has anything to do with superSU

Sent from my Nexus 7 (2013) with Tapatalk
[SuperSU] fefuzzo:
nobody can help me please?
[SuperSU] anabolic_guy:
Hi, I have a Huawei P9 Plus with nougat firmware version: VIE-L09C432B360.

I have also installed TWRP recovery version: twrp-3.1.0-0-vienna

When I try to install in recovery mode the file SuperSU v2.79 SR3, the system start the process but at the stage of creating system img, it doesn't complete and reeboots so fast that I can't read the error that cause this.

Someone knows how to solve this issue or the origin of it ?

Thanks for the attention.
[SuperSU] Captain_Throwback:
If SuperSU can't find your boot image, then your device is incompatible with a systemless installation. You'll need to manually patch your sepolicy and use a system install.
[SuperSU] fefuzzo:
and it's not possible to add my device to support systemless supersu? because i have android 6.0 so it's good to have systemless supersu..
[SuperSU] Captain_Throwback:
Guess you need to ask CCMT...
[SuperSU] fefuzzo:
what is CCMT?
[SuperSU] Captain_Throwback:
The company that owns this software.
[SuperSU] RandomPooka:
The things that you'd think should go without saying ...
[SuperSU] :
Yeah stop try flashing it because loop is broken. So it'll fail to mount the image.
[SuperSU] StevenTheDev:
Thanks for the help!

Thank you so much, I have been trying to get this to work for ages.
[SuperSU] ashyx:
Didn't your device already come prerooted, they pretty much always do and it will be installed to system?

All you need do is update via the supersu app.

I see no reason why you would require systemless root on your device.
[SuperSU] fefuzzo:
I would require systemless root because with system root i can't use "suhide" (magisk's module) to hide root on app like Sky Go, Tim Vision, Premium Play. So i can't use this app on my tv. :crying:
[SuperSU] RandomPooka:
For what it's worth, "suhide" is NOT Magisk related. It was for hiding SuperSU back when it actually worked. It doesn't anymore.

If you're considering installing Magisk to hide SuperSU (which you can't install systemless anyway), so you can pass SafetyNet checks, don't bother (the two are incompatible in that respect).

PLEASE read up on both SuperSU and Magisk, as well as how they work together and things they can't do while working together. Continuing to ask about this will just further expose that you haven't done your research before trying to modify your device.

I don't know about you, but I don't have a couple of spare devices lying around. If I brick mine, I'm screwed. If you can just pop your SIM into another spare phone and don't mind that you're likely going to destroy something in an attempt to do things that you won't simply read the instructions on, go ahead. Nobody will help you fix it, but go ahead. Just research your plan. Research how to fix it if something goes wrong (something ALWAYS goes wrong when you don't research first). Download all the appropriate tools, learn how to use them, and have your PC ready to fix it before you start tinkering. Your PC should be like an EMS team, just waiting on the off chance that your phone has a near death experience.
[SuperSU] veez21:
Lol, you're going too far dude. The guy probably has an experience on doing things here in xda. He probably just had a misconception between the two. No need to post a speech about it. :laugh:
[SuperSU] 88darkghost88:
my phone reboots when i give root privelege to some apps. how can i stop this?
[SuperSU] RandomPooka:
Have you never been to XDA? Lol. That was entirely necessary, and will be summarily ignored by the one person it was intended for.

Judging by his previous posts regarding the systemless install, and the link to unSU directly before his last, I'm going to say that he did not at all RTFM
[SuperSU] veez21:
Well you're right about "RTFM". :laugh:. I would admit that he's going too far off with unSU being a magisk module. Some things we need to learn is to not become completely be a noob(ish) when posting/reporting a problem here in xda :).
[SuperSU] fefuzzo:
1) if YOU read, SUHIDE require SYSTEMLESS supersu.. not magisk, it's my mistake, but SYSTEMLESS SUPERSU yes!

And without this i can't use it..

2) this is a forum, so i can make any question for my problem, but you shouldn't make this POEM for a simple answer.

If you want respect, you have to give respect!

Bye!
[SuperSU] jcmm11:
What security patch level are you running?
[SuperSU] RandomPooka:
Last I checked, suhide was no longer functional and was causing boot loops on many devices. If that's changed, then I apologize. I *did* read, BTW. The post I quoted was written in a way that it sounded like you were trying to use magisk manager to hide systemless supersu. That's well documented as not possible anymore in the appropriate magisk thread.

Also, not a poem LOL. I guess maybe in the Iliad and Odyssey sense of being long winded, maybe?

I still don't think you're young to be able to hide root, even if you manage to manually modify your boot image for systemless SuperSU, because of suhide no longer being usable for that purpose. Again, if that has changed in the past 6 months or so, I apologize for not realizing it's been brought back into play.

(I don't want respect. I want clearly written and researched requests for help)
[SuperSU] Strephon Alkhalikoi:
[MENTION=3053466]RandomPooka[/MENTION]: Not to mention respect is earned, not granted.
[SuperSU] yauser:
Ramdisk extraction Failure

Hi,

I am trying to get SuperSU onto my Moto G5 with TWRP 3.1.0.

I get the extracting ramdisk failure.

Recovery log: pastebin at /d5qC1Bze (I am not allowed to post outside links yet..)

There are a couple of failed SuperSU installs in there (I tried SR1,2,3).

I'd appreciate any help in getting this work! Thanks
[SuperSU] andrew2432:
Manually patch your .lib files and you can run suhide on newer ROM!!

Isn't the [un]intended bug/feature of suhide that it hides xposed 86.2? Rootswitch is involved in that method and just turns root off.
[SuperSU] yauser:
I realised that paste is too long to look at nicely, so I made a new one with only one try.

pastebin: /dJHWS86y

The first line of failure is actually not the ramdisk, but a read-only file system under Creating paths.

mkdir: can't create directory '/su/bin': Read-only file system
chown: /su/bin: No such file or directory
chown: /su/bin: No such file or directory
chmod: /su/bin: No such file or directory
mkdir: can't create directory '/su/xbin': Read-only file system
chown: /su/xbin: No such file or directory
chown: /su/xbin: No such file or directory
chmod: /su/xbin: No such file or directory
mkdir: can't create directory '/su/lib': Read-only file system
chown: /su/lib: No such file or directory
chown: /su/lib: No such file or directory
chmod: /su/lib: No such file or directory
mkdir: can't create directory '/su/etc': Read-only file system
chown: /su/etc: No such file or directory
chown: /su/etc: No such file or directory
chmod: /su/etc: No such file or directory
mkdir: can't create directory '/su/su.d': Read-only file system
chown: /su/su.d: No such file or directory
chown: /su/su.d: No such file or directory
chmod: /su/su.d: No such file or directory
[SuperSU] AvisAile:
It's work on android O ? thanks
[SuperSU] Ja_som:
You can try it and tell us
[SuperSU] gothicVI:
From the log part you posted here I'm tempted to suggest mounting /system manually in twrp.

Gesendet von meinem Moto+G+2014+LTE mit Tapatalk
[SuperSU] skiely666:
I flashed O with flashfire 0.53, O flashed no problems but everoot failed. I know 0.53 has an older version of SuperSU but I'd say we need O boot patched..
[SuperSU] exSD:
SuperSU currently not working with Android O.

It will boot to the lockscreen, but pin/pass do not take and you get a blank screen.
[SuperSU] osm0sis:
It's not /system that's failing for him, it's the /su filesystem. Either su.img isn't getting mounted at all (so it's trying to create things in the / root filesystem which is often read only), or for some reason su.img is getting mounted read-only on his device.
[SuperSU] LazerL0rd:
Failed.

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

Try again. Give it a minute and it'll load. But THEN.. root binaries exist but "permissions" don't. Same error with Magisk.
[SuperSU] fefuzzo:
I have KM8 PRO tvbox with android 6.0.1

I don't know how to see security patch level because in "settings info" is not written.
[SuperSU] pkelly517:
Don't give root privileges to those apps.

Sheesh!
[SuperSU] Alxoom33:
Had same issue with the Pixel C and Android O preview. I was using FF v. 0.55 to flash Android O preview. Will SuperSU 279 SR3 be able to provide root?
[SuperSU] skiely666:
Thanks for the clarification sir..
[SuperSU] Chainfire:
I've used FlashFire to flash O on several devices and that part worked fined. The rooting part did not. Needs a SuperSU update I guess.

Will be looking at 6P/Angler in detail tomorrow. Flashing the SR3 ZIP through TWRP fails for me on 6P as well. Does it succeed for anyone on any device (regardless of if root actually works) ?
[SuperSU] Alxoom33:
I'll try it tonight on the Pixel C and report back.
[SuperSU] ziggynlp:
On Nexus 5x with TWRP 3.1.0-0 failure after Patching sepolicy
[SuperSU] nohair:
Flashes and boots fine on Nexus 5X(O) here /(but doesn't work, obviously)
[SuperSU] crisis_trustee:
Wait new SuperSU for Android O DP1.
[SuperSU] yauser:
I did try manually mounting /system, but yeah, no change as it's /su.

Any idea on what can be done to fix this? For ease, the log was here: pastebin /dJHWS86y

The TWRP comes from here: https://xdaforums.com/g5/development/unofficial-twrp-3-1-0-0-moto-g5-t3574450

Perhaps the force encryption messes around here beyond /data?
[SuperSU] cjkacz:
Lol I can't even get TWRP on my pixel with O
[SuperSU] tag68:
A look in the log shows data is formatted f2fs. This is the known problem regarding loopback device on f2fs.

For Moto Z Play a kernel exists where f2fs is fixed, then you can root systemless using SuperSU. Don't know for G5.
[SuperSU] Chainfire:
I have basic root running on ODP1/Angler, but there's still some issues to work out.
[SuperSU] w0rdie:
I realize it's gauche to ask for eta/estimate but here I am typing it anyway. ツ
[SuperSU] exSD:
Check back next year. :good:
[SuperSU] ashyx:
Probably somewhere between now and then. ;)
[SuperSU] prakharkmr27:
Tried installing the latest 2.79 via TWRP, but got this error "Already patched, attempting to find stock backup

restore failed, aborting"

Moreover, lost the built-in SuperUser management app/settings in the custom ROM (Nitrogen OS - Android 7.1.1)
[SuperSU] sahem:
Please help me my phone is stuck on creating image while flashing su 2.79
[SuperSU] RandomPooka:
Push the second button from the left two times, then shake the device.
[SuperSU] sahem:
dear i'm unable to abort the operation
[SuperSU] RandomPooka:
Sarcasm is truly wasted on the stupid. Note to self: no more sarcasm for at LEAST 4 hours.
[SuperSU] sahem:
i didn't "Push the second button from the left two times, then shake the device" as you said, but i'm ignoring your sarcasm now and looking for a solution to my case
[SuperSU] dahawthorne:
Guy, we should be helping people rather than trying to show that we're cleverer. Yes, the poster doesn't appear to have a clue and didn't provide any sensible information to allow for help, but still, no point in going out of your way to make him look foolish. (And don't say "He's already done that" - far too easy... :))

P.S. I've seen the help and advice you've given, and your thanks score shows that you generally are. Maybe having a bad day...? :)
[SuperSU] LazerL0rd:
Thanks allot. Flashing works on Nexus 5X but rot doesn't obviously. I think there's some universal thing blocking root recognition...
[SuperSU] Chainfire:
Update

Just an update on O:

Both the 5X and 6P seem to be suffering from a kernel panic if SuperSU launches at boot. I can work around it by delaying the startup, but this is 'unclean' and I'd rather find the cause of the issue. Other than that, it seems to work fine (after some of my patches).

On the Pixel (and Pixel XL) the trick I used before to get root working seems broken. I have not had the opportunity yet to find out why as I was working mostly on the 6P.

I have not looked at any other devices at all yet.

Naptime!
[SuperSU] Maxr1998:
[MENTION=631273]Chainfire[/MENTION] just want to share an interesting observation, I yesterday flashed Android O on my 6P, but I used the sukernel tool in before to modify the fstab of the boot.img, to disable force encrypt and verify. After setting everything up, I rebooted, and had the (known) issue that I couldn't input my PIN. Interestingly enough, it actually worked again this morning.

So, is the PIN issue only related to verify?
[SuperSU] rul3z:
Its a known issue on note 5/ S7 on nougat update mentioned here https://xdaforums.com/showthread.php?p=70985800#post70985800

You have to wait for [MENTION=631273]Chainfire[/MENTION] to update SuperSU, or try the solution mentioned in the post
[SuperSU] yauser:
Thanks for telling, that's what was wrong. I formatted to ext4 and the install run, but the phone won't boot without data as f2fs.

Someone in the G5 forum suggested trying phh-superuser. It worked!

https://xdaforums.com/android/software-hacking/wip-selinux-capable-superuser-t3216394

So, anyone encountering issues on a Moto G5, try the phh superuser.
[SuperSU] attaullahsahito:
Root for Android O Developer Preview 1

Is there any ongoing work on root for Android O Developer Preview 1..?
[SuperSU] Ch3vr0n:
Ignorance is bliss i suppose. It does help to read a few pages back.

https://xdaforums.com/showpost.php?p=71541864&postcount=9326
[SuperSU] ainaz:
Why SuperSU.zip not installed as default on system apps??

Cause if I wiped the phone, superSu.apk is lost. So I tried to install zip again.. and i convert SuperSU app as system app, but not give me permission again to grant for root access

Sorry for my English.

I'm on lineageOS 7.1.1
[SuperSU] Chainfire:
Preliminary root for ODP1 on 5X and 6P

This is still very much a work in progress. I am releasing it now because I will be away from my development PC for about a week, and I don't think I'll be able to fix any more issues before I leave.

- This version works pretty well for me on the 5X and 6P flashed with TWRP.

- It does not work on the Pixel or Pixel XL.

- PIxel C and Nexus Player have not been tested - please let us all know your results.

- I would advise against using this release on any device not mentioned in this post.

SuperSU-v2.79-SR4-20170323220017-ODP1-5X-6P.zip

When linking, please link to this post, not to the download directly.

Technical notes

Service mode

Both the 5X and 6P suffer from a kernel panic (of yet unknown origin) if SuperSU's daemon loads at early boot. Due to this, on ODP1 exec mode is skipped, and even the service launch is delayed. As a result, su.d scripts are executed too late in the boot process to hijack system services before they launch. While most of you are probably not going to run into that, some might, and it is thus worth noting. (Most seem to think you need some sort of framework rather than a few lines of script for that sort of mod...)

This kernel panic may be a kernel issue only Google can solve, or it may be possible to work-around on our end, it is too soon to say.

If the boot animation freezes for a second and it reboots, you are most likely hitting the same kernel panic I was during development. If this keeps being an issue, increasing the startup delay may help as a work-around. Click here for a test version with an extra 15-second delay. I already spent quite a lot of hours trying to trace this kernel panic without result, I don't think I will invest more time in finding the cause unless the problem still exists on ODP2.

Pixel and Pixel XL

These devices have the new A/B partition layout, and something is going wrong with the code that handles this. This is most likely something I can solve with some more time and effort. This part of the code is just very tricky and time-consuming to debug, as logging isn't operational yet at this stage of booting.

Apps

Just because an app can gain root access doesn't mean it'll work. While O still seems very similar to Nougat, some things have changed. The syntax of some commands has changed (try 'ps -A' now instead of 'ps' for example). As expected, SELinux rules have been tightened some more, and this always has the chance of breaking some root apps. The point is - just because an app doesn't work doesn't necessarily mean something in SuperSU is broken (it could be, though).
[SuperSU] :
Is SR4 only for Nexus devices?
[SuperSU] :
The new build will work on nexus 4?
[SuperSU] MatiasLopezxD:
Wont work for me, Nexus 6p Android O dp
[SuperSU] bmg1001:
We're you getting a bootloop issue (where the boot animation would freeze right after the last vibration)? If so, try reflashing the entire alpha image. I know it's tedious, but only after this the phone booted up for me.
[SuperSU] eduardozeassesme:
do you have root?
[SuperSU] MatiasLopezxD:
ohh! thx bro I will try
[SuperSU] bmg1001:
Yes.
[SuperSU] eduardozeassesme:
what flash? only system?
[SuperSU] bmg1001:
Also, if it still doesn't work, you might have to wipe userdata and cache too when flashing (essentially factory resetting) via fastboot format cache and fastboot format userdata.

---------- Post added at 04:30 PM ---------- Previous post was at 04:28 PM ----------

I flashed boot, system, and vendor, and also wiped userdata and cache. I know it may be tough to have to essentially start from scratch, but that's what happens when you install beta mods on alpha software lol :)
[SuperSU] eduardozeassesme:
sorry double post
[SuperSU] Lord*Andre:
my phone went to a bootloop. I have reflashed SR4 and now it is working. so far i have tried root explorer to edit build.prop.
[SuperSU] eduardozeassesme:
but how do you obtain roo?
[SuperSU] bmg1001:
By flashing the SuperSU Beta for Android O from the last page......it automatically installs the app too so it should all work right away.
[SuperSU] eduardozeassesme:
ok bro, because I make wipe and boot but don´t have SuperSU app

I have root thanks
[SuperSU] hbbxmjbb:
If i could try it on my xiaomi mi4lte?
[SuperSU] xdarkstar:
I guess people don't like to read before asking
[SuperSU] hbbxmjbb:
I'll try and I've read that.
[SuperSU] xdarkstar:
Good luck and take a backup before it as chainfire himself advised against using for other devices and it's meant for odp1