yashsingh1/xdaforums huggingface dataset:
[SuperSU] erfandl:
[MENTION=631273]Chainfire[/MENTION] 2.82 on xperia z ultra android 5.1.1 stuck on boot loop :| :| :| PLEASE FIX !!!!!!!!!!!!!!
[SuperSU] MegaTronics:
2.82 works for stock Nexus 5X 7.1.2 with Franco kernel and stock Nvidia Shield K1 7.0 :good:
[SuperSU] geko37:
Works fine here with Superman Rom on S7.

Gesendet von meinem SM-G930F mit Tapatalk
[SuperSU] Bronco77:
2.82 is working fine on S7 edge with Stock Rom. Thanks [MENTION=631273]Chainfire[/MENTION]
[SuperSU] P.Kosunen:
2.82 ok on Xiaomi Redmi Note 4 mido with xiaomi.eu 7.5.25 MIUI.

~ # twrp install /sdcard/UPDATE-SuperSU-v2.82-20170526223454.zip

Installing zip file '/sdcard/UPDATE-SuperSU-v2.82-20170526223454.zip'

Checking for MD5 file...

Skipping MD5 check: no MD5 file found

*****************

SuperSU installer

*****************

- Mounting /system, /data and rootfs

- Extracting files

- Detecting system compatibility

- System-less mode, boot image support required

- Creating image

- Mounting image

- Creating paths

- Removing old files

- Placing files

******************

Boot image patcher

******************

- Finding boot image

--- Boot image: /dev/block/mmcblk0p21

- Extracting ramdisk

- Decompressing ramdisk

- Checking patch status

- Creating backup

- Patching sepolicy

- Adding daemon launcher

- Adding init script

- Creating mount point

- Patching init.*.rc, fstabs, dm-verity

- Creating ramdisk backup

- Compressing ramdisk

- Creating boot image

- Applying hex patches

- Flashing boot image

*************************

IMPORTANT NOTICES

*************************

First reboot may take a

few minutes. It can also

loop a few times. Do not

interrupt the process!

*************************

- Unmounting /system

- Done !

Done processing script file

~ #
[SuperSU] Idebutterpiep:
UPDATE-SuperSU-v2.80-20170524085154.zip

Original v2.80 compiled by me instead of CCMT (fixes one of the major root loss issues)

SuperSU-v2.80-20170525215916-bindfix.zip

Test version that (maybe) fixes mount namespace separation / su.d / bind mounts at boot / AdAway

UPDATE-SuperSU-v2.82-20170526223454

Above bindfix version, but version code modified to v2.82 so it doesn't auto-update to v2.81 from Google Play

Does this work on SM-G935F( Samsung S7 Edge Exynos).

Please somebody can write the steps for me? Do I need TWRP or Odin to flash?

I am not rooted, but tripped void Knox and cannot use SHealth and my SamsungFit . My Phone tells me I am rooted.

I am afraid to flash.
[SuperSU] Ps24u:
Tried UPDATE-SuperSU-v2.82-20170526223454.zip on my Xperia Z1C / Android 5.1.1, and it bootloops.

I was coming from SuperSU 2.81 from Play store working correctly.

Now gonna reinstall TWRP backup.
[SuperSU] erfandl:
is 2.81 google play worked for you without bootloop ?
[SuperSU] Ps24u:
Yes. 2.81 from Play works OK.
[SuperSU] yuri76:
2.82 works on s8 +
[SuperSU] Jengo:
That’s strange. Version 2.81 from Play shouldn’t have worked as other Z1C users reported.

---------- Post added at 12:34 PM ---------- Previous post was at 12:27 PM ----------

My mistake. Version 2.81 was a “disguised” 2.79 since Play doesn’t allow developers to downgrade. So everything is consistent: Version (2.81 = 2.79) works on Xperias and 2.82 which is based on 2.80 doesn’t.
[SuperSU] kojak1989:
Do not make people mislead because version 2.81 does not work for everyone well because it loses root.
[SuperSU] Ps24u:
Of course I'm speaking for me, on Z1C.
[SuperSU] kojak1989:
In that case, please clarify your statement, because for some it may end badly.

---------- Post added at 13:05 ---------- Previous post was at 13:00 ----------

Version 2.82 works fine on Nexus 5X with Pure Nexus rom.
[SuperSU] Ps24u:
It's perfectly clear already.
[SuperSU] 11sword11:
Version 2.82 works fine on Kyocera DuraForce (android 5.1.1) but in every reboot clean dalvik-cache ((

Go back to 2.79
[SuperSU] firebie:
Sony Z1C, 2.79 - works, 2.82 - boot loop.
[SuperSU] Chainfire:
v2.82 is currently in staged roll-out on Google Play

You can find the APK and ZIP files, and some more information, in the test releases post here:

https://xdaforums.com/showpost.php?p=72429329&postcount=9810

Testing and reports back are appreciated.

Xperia users should note that the boot-loop issue has

not

been resolved yet

Unfortunately the update cannot wait for this. I will need an Xperia user who is experiencing this issue to be available for live testing for several hours sometime in the coming days to be able to track and fix this issue.

Release posts, changelogs, and elaboration on what the hell exactly happened, etc, will come tomorrow or so. I need a break right now.
[SuperSU] papero68:
Xiaomi redmi note 4 sd, from zip, 2,82 ok

Inviato dal mio Redmi Note 4 utilizzando Tapatalk
[SuperSU] paiktaras:
Version 2.82 works fine on ONEPLUS 3T ( oxygen os 4.1.3 )
[SuperSU] koekoek91:
[MENTION=2514812]erfandl[/MENTION] on previous page posted he had issues on an Xperia.

Maybe he has some time to help tracking it down?

I would do it myself if I was experiencing the issues , but sadly Im not.
[SuperSU] shaggyskunk:
You (and other Xperia users) have been asked by [MENTION=631273]Chainfire[/MENTION] to help with the Xperia issue - Rather than provide [MENTION=631273]Chainfire[/MENTION] with some useful feedback.. "please fix" is of no help in any way.
[SuperSU] ad0dh67:
2.82 working as normal on my nexus 6p with android 7.12
[SuperSU] jcmm11:
On Nexus 5x Gsam working fine.
[SuperSU] laupuy:
Come on guy, grown a little!

Please post a useful message for once!
[SuperSU] tdunham:
All users please read - especially Xperia users!

SuperSU progress posted in official SuperSU thread by Chainfire:

https://xdaforums.com/showpost.php?p=72428986&postcount=1645
[SuperSU] Ibuprophen:
[MENTION=631273]Chainfire[/MENTION], just an FYI... All is well with v2.82 and my D2VZW S3.

Thank you very much for your time, support and understanding!

"Live Long and Prosper..."

~Ambassador S'chn T'gai Spock

Sent via Communicator [D2VZW] from the Bridge of the U.S.S. Enterprise
[SuperSU] Jengo:
In principle I could offer an Xperia Z1 (C6903) on stock 5.0.2 (14.5.A.0.270) (not the newest firmware) with a locked bootloader. But right now I have not enough space on my SD card to do a full backup and usually I am not the type of guy who likes to experiment with his phone if there is a good chance in bricking it. :angel:

Furthermore my phone is in a strange state: I flashed SuperSU-v2.79-201612051815.zip to get rid of the bootloop which worked. And now the su binary seems still to be there but the SuperSU app is missing. Also apps which require root just seem to be able to acquire root permissions without any prompt. So far I didn’t try to reinstall any SuperSU version because first I want to do a full backup.
[SuperSU] martyfender:
Thanks for your response. [MENTION=6726362]vickybonick[/MENTION], in the apps2sd thread asked, and I also posted your above reply to him after he posted:

"What exactly is the bind fix in SuperSu any description/details? If it affects su.d then it'll affect su.d mount method in Apps2SD. Is there any documentation provided by Chainfire on how to cope with it?"
[SuperSU] vickybonick:
In Apps2SD I use 'su -mm' because i remember i had issues with 'su --mount-master'. Does SuperSU support 'su -mm' ?
[SuperSU] rabbid10:
UPDATE-SuperSU-v2.82-20170526223454.zip

LG Nexus 5x running the latest PureNexus

I had lost root after updating via playstore. It had asked to update the su binary, said it did, but root was gone after reboot. After flashing the zip above, all seems to be working again. Thanks [MENTION=631273]Chainfire[/MENTION] for the update.
[SuperSU] Chainfire:
Yes, -mm is supported.

If there is still an issue, perhaps something we should investigate together. If you can produce a simple test case to demonstrate the problem I'd be happy to find and fix the issue. Be sure to use v2.82 for testing.
[SuperSU] Rebel2k:
As far as I can say, my father's phone is in the same state. The SuperSU app didn't come back with the 2.79 flashing in TWRP. If didn't notice that first but he confirmed that to me earlier today. Don't know if that's helpful but indeed worth giving the information.
[SuperSU] mpgrimes:
Works great so far on my n5. Just no menu labels when scrolling between screens
[SuperSU] Chainfire:
I don't understand
[SuperSU] Chainfire:
Please provide me with the output of:

adb shell su --self-test

and try flashing with TWRP, see if that fixes the problem.
[SuperSU] mpgrimes:
Sorry. Changed theme and it showed up.

The 'apps' 'logs' 'settings' labels.
[SuperSU] sndrdg:
Under version 2.06 - su--self-test command completes with larger quantity of output.

Under version 2.08

Output from su--self-test

after installing with TWRP, the

command does not complete/hangs:

version_code: 208

version_name: 2.08:SUPERSU

version_arch: ndk:armeabi-v7a

sdk: 18

daemon_sdk: 1

multiuser_sdk: 1

multiuser_userid: 0

multiuser_username: (null)

selinux_present: 1

selinux_enforcing: 1

context[base]: u:r:init:s0

context[u:r:shell:s0]: u:r:init:s0

context[u:r:shell:s0-->base]: u:r:init:s0

context[u:r:shell:s0-->u:r:system:s0]:

Thanks for your continued assistance!

Regards, Doug
[SuperSU] Chainfire:
Definitely something with sugote... can you

adb shell su -c ls -lZ /system/xbin/*su*
[SuperSU] sndrdg:
ls.txt

lrwxrwxrwx root root u:object_r:system_file:s0 cksum -> /system/xbin/busybox

-rwxr-xr-x root root u:object_r:system_file:s0 daemonsu

lrwxrwxrwx root root u:object_r:system_file:s0 lsusb -> /system/xbin/busybox

lrwxrwxrwx root root u:object_r:system_file:s0 md5sum -> /system/xbin/busybox

-rwxr-xr-x root root u:object_r:system_file:s0 otasurvival.sh

lrwxrwxrwx root root u:object_r:system_file:s0 sha1sum -> /system/xbin/busybox

lrwxrwxrwx root root u:object_r:system_file:s0 sha256sum -> /system/xbin/busybox

lrwxrwxrwx root root u:object_r:system_file:s0 sha3sum -> /system/xbin/busybox

lrwxrwxrwx root root u:object_r:system_file:s0 sha512sum -> /system/xbin/busybox

-rwxr-xr-x root root u:object_r:system_file:s0 su

-rwxr-xr-x root root u:object_r:zygote_exec:s0 sugote

-rwxr-xr-x root root u:object_r:system_file:s0 sugote-mksh

lrwxrwxrwx root root u:object_r:system_file:s0 sum -> /system/xbin/busybox

Thanks, Doug
[SuperSU] Chainfire:
Unfortunately, that all seems to be fine. Back to thinking what the issue may be.
[SuperSU] Chainfire:
Please let me know if v2.09 (see first post) fixes the issue for you
[SuperSU] Chainfire:
This is not properly document yet, but from v2.09, this works: https://github.com/Chainfire/libsup...infire/libsuperuser/HideOverlaysReceiver.java
[SuperSU] scoobyjenkins:
I flashed v2.09, rebooted then updated my rom and no more prompt to update binary!

Tapatalked that shiznit.
[SuperSU] Aaahh:
How about,

Intent intent = new Intent("my.service.action");
getApplicationContext().sendBroadcast(intent);

and then I could receiver it with:

@Override
public void setUp() throws Exception{
super.setUp();
bindToService()

IntentFilter filter = new IntentFilter("my.service.action");
getContext().registerReceiver(mMyReceiver, filter);
}

public BroadcastReceiver mMyReceiver = new BroadcastReceiver(){

@Override
public void onReceive(Context context, Intent intent) {
//Disable overlay here
}
};
[SuperSU] Chainfire:
I don't understand the question. The linked code shows you exactly which action and category you need to listen for, and what to do in the onReceive. What more could you possibly want?
[SuperSU] Aaahh:
Oh that makes much more sense... lol, i thought you were listening...

I'll test and edit this post
[SuperSU] matrixzone:
Thanks
[SuperSU] sndrdg:
Unfortunately 2.09 did not fix my "spinning circles". Guess I'm stuck on 2.06 for a while. I also tried a "Full Unroot" - thinking my data/logs were corrupt - but my wheels kept spinning (no pun intended). I'm here to help - should you think of anything else I might try. {and thanks for helping - what appears to be a problem - only I - am experiencing}

Regards, Doug
[SuperSU] JulianJenner:
New BETA version works without problems on LGE-P760 CM11. Thanks!

LGE-P760, Artas's cm11 build 4.9.13
[SuperSU] Chainfire:
That's too bad, last open issue for public release. Did you actually try 2.07 ? You stated 2.06 works and 2.08 didn't, but I haven't seen you say anything about 2.07. Here's the link: BETA-SuperSU-v2.07.zip. This narrows down exactly where the issue was introduced, though my money is still on 2.08.

However, generate an adb logcat of 2.09 first. You can filter (grep, find) for "[Installer]", or just post the whole thing if that's beyond your knowledge. Make sure you open and close SuperSU a couple of times. For extra points, manually kill eu.chainfire.supersu from an adb shell and then open SuperSU again and see if that changes things. Don't worry about it if you don't have the cmdline-fu for that, though.

If you are IRC savvy, doing some live debugging and testing would certainly be helpful.

I am certain others will experience the issue if you are. There are about 50 million users of SuperSU, if you were the only one with the issue you should consider playing the lotery ;) People actually willing to help find and fix issues are few and far between though, even for an app with as many users as SuperSU.
[SuperSU] sndrdg:
Will try all this weekend. Old VAX/VMS dude - been years since Solaris 2.3 - I will brush up - and get you what you need.

Regards, Doug
[SuperSU] cbeckstein:
Just tried supersu 2.09 beta:

flashed it from Philz recovery,

Upon reboot Philz said 'root possibly lost, fix it?', I said yes

Then first time I started supersu after the reboot it said that the su binary must be updated, allowed tthe normal update and now things seem to be fine
[SuperSU] VivaErBetis:
I just update a encrypted nexus 4 to SuperSU 2.35 without any problem.
[SuperSU] rskyline:
I've updated SuperSU to stable from the play store and now I've noticed that the option to make it a system app is available, should I make it system app or leave it that way?
[SuperSU] LittleConfucy:
Bootloop with 2.35

I'm using a N7 2013 with the lastest TWRP (2.8.2.2) and Stock Android Lollipop, and after flashing SuperSU through recovery it gets stuck in the boot animation. Tried reflashing it, wiping cache and dalvik; but nothing seems to work...

Update: tried formatting data and still doesn't boot to system (stuck on boot animation) but on TWRP's file manager it shows as though there is no system.
[SuperSU] ffejy462:
That option has been there for a long time.... I've never had an issue either way, but I'd still recommend installing it as a system app, or just flash the SuperSU zip in recovery (which installs it as a system app).

Kindle Fire Hd CM 11
[SuperSU] rskyline:
I know about that option and what it does. I'm asking because it changes after the play store update I think. I had beta 2.30 before and obviously flashed on recovery
[SuperSU] whchengcai:
how to OTA

Nexus 4 Android 5.0,I have flashed back the stock boot.img,and flash the supersu2.35,then how can I get OTA in the future? In the supersu`s setup,there is " cancel rooted",if I " cancel rooted" ,could I get the OTA and update sucessfully?
[SuperSU] Namikaze_Minato:
XModGames still not working with 2.35

Nexus 5 - updated from SuperSuv2.27 to SuperSuv2.35. XModGames still says device is not rooted.
[SuperSU] ankur1409:
good and able to root android lollipop

Good and able to re root android 5.0 Lollipop Nexus 4
[SuperSU] playahate:
Not related for the beta itself but an annoying thing since the old times. [MENTION=631273]Chainfire[/MENTION] can you please fix the russian translation in settings?

I think its Chech or Polish...

View attachment 3036109
[SuperSU] Srandista:
It's in Slovak ;)
[SuperSU] ciano865:
ok

NEXUS 4, L AOSP NX5 ROM

previus installed 2.23, today updated by Play Store 2.35, auto update binaries using TWRP. No problems at all with Hellscore kernel manager, busybox free and Xplorer file manager.

Thanks!!
[SuperSU] albert_htc:
Nexus 5 lollipop rooted with cfautoroot.

Play store is offering the upgrade to 2.35

Do I flash boot.img first ?

Do I need to flash system.img ?

Then flash 2.35 ?

Thanks
[SuperSU] Chainfire:
It's /system you need to reflash... you've reflashed everything but that, it seems :)

Stop reporting this for every version. XModGames needs to be updated, not SuperSU.

I don't know Russian. If you do, I suggest you fix the translation: http://www.getlocalization.com/supersu/
[SuperSU] Srandista:
Oh, and I forget to mention, it means: Tapjacking protection.
[SuperSU] playahate:
its been there for a long time.

The correct Number is 2, but in app its still number 3 in slovak.

View attachment 3036199
[SuperSU] Shad0w32:
XModGames support website says they are working in ART compatibility. Cgeck that, it is not su fault
[SuperSU] Frank Westlake:
2.35 OK through TWRP on:

- Note_ SGJ-I717 4.0.3

- Note3 SM-N900V 4.3 single user Permissive

- Note3 SM-N900T 4.3 single user Enforcing

Frank
[SuperSU] HorstiG:
SuperSU pro

No Problems on S3 and S5 KK 4.4.4 - LP 5.0

HGT - Galaxy S3 - S5 - Tesla TTL7 any AOSP ROM
[SuperSU] danetbra63:
bad zip file

Es file explorer says download is a bad zip file. Can someone link link a fresh one?
[SuperSU] LittleConfucy:
Pardon me for my ignorance, but what s do you mean by flashing /system? :confused:
[SuperSU] vickybonick:
Sure, I'll try that and let you know.
[SuperSU] SAGI1:
UPDATE-SuperSU-v2.82-20170526223454.ZIP worked at note 2

UPDATE-SuperSU-v2.82-20170526223454 worked as expected at N7100 samsung galaxy note 2

AICP ROM nougat 26/05/2017

Android 7.1.2

** Boot-loop encounter after one day in v2.8.0 bind fix, I hope that this is the final version

TNX Chinfire :good:
[SuperSU] bemagrp:
[MENTION=631273]Chainfire[/MENTION]

Pixel xl stock rooted 2.82 works perfect.
[SuperSU] The~Skater~187:
[MENTION=631273]Chainfire[/MENTION], SuperSu 2.82 is working great on kltespr resurrection remix 5.8.3. Thank you for the quick fix, keep up the awesome work.
[SuperSU] WiggleCat:
Note 7 on 6.0.1 here. 2.8.1 worked fine but I just updated to 2.8.2 and lost my root. Rolled SuperSU and SuperSU Pro back to 2.8.1 and rebooted and still no root, yet it boots up with the "custom" unlocked logo because the ROM itself is rooted and SuperSU just doesn't see it anymore.
[SuperSU] SAGI1:
sorry to destroyed the party

after two hours with 2.8.2 got boot loop the device not start

n7100 samsung galaxy note 2

7.1.2 AICP rom
[SuperSU] zoppa:
I was writing an extensive post on how it worked out for me, when a damn ad just killed my session. Wtf, is going on on XDA???

In short, 2.82 non-CCT and CCT zips work for me (no root loss like with 2.80 and 2.81) on Xiaomi Mi Mix, Lineage OS unofficial 14.1.

Fck ads.

Pissed.?
[SuperSU] WiggleCat:
My phone is indeed still rooted. Under status in system settings it says custom. I'm just unable to install SU binaries since the 2.82 update.
[SuperSU] zoppa:
Teh fckn mfn ad

See it!
[SuperSU] pittrich67:
All fine :good:
[SuperSU] DEVILOPS 007:
Thanks for me making me laugh at how bad that phone is! ? I don't understand that language, what are you trying to show?
[SuperSU] skyhirules:
Maybe this will help with the Xperia boot loops. On my Z1 Compact I've been reporting in this topic the boot loops I had with all the SR's after 2.79 stable. So, it's caused by some change in the app after 2.79.
[SuperSU] WiggleCat:
If anyone knows how I can fix this please let me know. Here's some screenshots from advanced root checker.
[SuperSU] zoppa:
You seem to be the most experienced user around, you tell me.

But maybe you are just a troll without any knowledge, who knows? :D :p
[SuperSU] peterlee928:
i suppose

thats one way

to get ppl

to not want to help u

:)
[SuperSU] miksontije:
N5X, PN rom, Ex kernel. i have supersu stop working, aplication must close. I done clean install and wipe data of su.

2.82 version
[SuperSU] Alxoom33:
The 2.82.update.zip file you provided works well on my Nexus 6 running 7.1.2 Stock, May update. The 281 Playstore.zip test file working, as well! The v. 281 Play Store version did not work for me.

I haven't tried it yet on my Pixel C running O DP 2 v.19. It froze in the boot animation with TWRP 3.1.1 and 2.79 SR4.
[SuperSU] ashyx:
Sukernel compression support

[MENTION=631273]Chainfire[/MENTION]

Totally unrelated question to any of the latest posts.

I know SuperSU only supports GZIP, but just wondered, does sukernel itself support LZMA compression, I.E can it recompress to LZMA?

Thanks.
[SuperSU] daitalos:
[MENTION=631273]Chainfire[/MENTION] Thanks for 2.82 fast update!...No problems
[SuperSU] udahy.manna:
Hi guys ,my pixel is bootlooping because of SuperSU.

What I did is,

Flashed Android 7.1.2 may version,

Booted into TWRP, flashed TWRP,signed using avb v7,

Flashed pure Nexus may version, flashed TWRP,signed it,

Booted into system, again booted into recovery, flashed TWRP,signed it,

Rebooted recovery, flashed super su 2.79 sr3 , signed it,

Phone booted into system without bootlooping,

But,After a restart,it's bootlooping.

Can someone please help me with this?

Thanks
[SuperSU] g3raldo:
UPDATE-SuperSU-v2.82-20170526223454 work for me on Latest Lineage 14.1

Enviado de meu Nexus 6 usando Tapatalk
[SuperSU] flroots:
Has anyone tried v2.82 on the Moto G4 Plus (xt1644)? I just lost root. Restored root by re-flashing v2.79 and verifying auto updates disabled. Now wondering if I should flash v2.82?
[SuperSU] DEVILOPS 007:
Well I do have knowledge and can tell you that phone is crap. Can you actually tell me what you meant by that picture? Did you have a question or something?
[SuperSU] ZRK_NanDRD:
2.82 zip Works on S3 I9300

RR 5.8.3 N 7.1.2

Boeffla Kernel

5 May Security Patch

Thanks Chainfire
[SuperSU] WiggleCat:
I am indeed still rooted as I'm able to run root commands via ADB. The problem lies within whatever SuperSU did with the binary updates. Does anyone know where I can get the 2.81 binaries so I can just delete the 2.82 ones and replace them via ADB?
[SuperSU] Ibuprophen:
The binaries are in the zip file...

"Live Long and Prosper..."

~Ambassador S'chn T'gai Spock

Sent via Communicator [D2VZW] from the Bridge of the U.S.S. Enterprise
[SuperSU] AJ:
does v2.82 works with android o dp2 ?
[SuperSU] droseofc:
Will system mode ever be available for nougat? Or ever period? Reason is that is the only way (it seems) that I am able to get an app to recognize and work with root. I've tried the options in settings, various ways, systemmode always seemed to be the easy fix. Or would it be possible to use titanium to install 2.82 systemless as system?
[SuperSU] Ch3vr0n:
then your app needs to be updated to not use hardcoded SU paths. Contact the app dev. or use the command line to force su in system mode
[SuperSU] jcmm11:
It's only a work-around, but I think you can get rid of those crashes by uninstall the SuperSU APK, rebooting, then re-installing it.

-------------------

The fix suggested by Chainfire worked. Haven't had a problem since. I extracted the apk from the zip file.
[SuperSU] droseofc:
Admittedly, the specific app is somewhat aged. Its the idoneapps gtupdate3.1.8 from awhile ago. I only use it because of the hidden system settings it enables to be accessed easily. I appreciate the reply though, so if I do a command force system mode it will be fine? Will it last?
[SuperSU] Ch3vr0n:
if you do it right, SU zip flash will detect the file and force system install. Note upon any ota you'll have to reflash the existing system image first before the ota can be applied
[SuperSU] ashyx:
I don't think you can it will boot loop.

[MENTION=7172205]droseofc[/MENTION] have you tried

echo "BINDSYSTEMXBIN=true" >> /data/.supersu

then reinstall the supersu zip.
[SuperSU] KaMyKaSii:
You made a typo
[SuperSU] ashyx:
I swear I didn't, it was xda labs that changed it. Corrected.
[SuperSU] Ch3vr0n:
Bootloop? Hardly that's exactly what i did when SU was still in system mode. Before every update, reflash the system.img that from the devices current build. Apply OTA, reroot, done. 0 bootloops
[SuperSU] Alxoom33:
Yes!

Was able to root my Pixel C running Android O DP2. Working well, but having issues with granting SU permission when prompted.