yashsingh1/xdaforums huggingface dataset:
[SuperSU] Blac Caesar:
Latest SuperSU (v2.78) works perfectly on N6P, stock NRD90M; OTA'd from NPD56N. While I don't have a Nexus Player, but since all current 7.0 factory images out right now, have the same build number.. I think it's a safe bet that, obvi for SuperSU, it's compatible.
[SuperSU] drewski_1:
yeah, what egingell said . . . step 2: move mouse and click :p

my response was to the post saying it was faster to get to the terminal on Mac, but really it's pretty much the same clicks / effort on Windows
[SuperSU] tag68:
The easiest idea probably is to not flash custom recovery. Just use fastboot boot every time you need it. No need to flash it if you have access to your computer when doing things like Nandroid backup.
[SuperSU] jackdubl:
So then, just flash SuperSU after each OTA, via fastboot? And to do that, you temporarily boot custom recovery(without installing it) through fastboot and flash SuperSU, or is there a commamd to do it straight from fastboot?
[SuperSU] grep_i:
Yes that's basically how I do it every time I also flash custom kernel ElementalX and [MENTION=2476451]romracer[/MENTION] systemless Xposed in one run.

The same is possible by using flashfire I have done it twice already, but I'm so used to doing it with

fastboot boot "custom recovery.img"
[SuperSU] cba1986:
do anybody loose root randomly using cm13? i have to reboot to gain root access again. tried with version 2.76 and 2.78. anyhelp will be appreciated.

---------- Post added at 04:44 PM ---------- Previous post was at 04:31 PM ----------

little detail that i forgot to mention. i have all f2fs formatted.
[SuperSU] hammerhead2:
My question might be quite stupid for you, but it is not for me...

I have N910C, which was rooted using CF autoroot. Then I decided to switch to magisk, so I uninstalled root using SuperSU application, all went well, no conflicts.

Then reflashed stock rom.

And then I used Root Verifier app, which tells me I am not rooted, but I have SuperSU Pro 2.78 installed.

I have found Supersu folder in root directory using TWRP, removed it manually, but Root Verifier still detects SuperSU.

I tried unsu.zip by osmosis, no results.

I am a bit concerned, since I want to try systemless root with suhide, so I wanted to be as stock as possible before - what do?... ;)
[SuperSU] force70:
Start fresh by flashing your stock firmware with odin

Sent from my SM-N930FD
[SuperSU] hammerhead2:
That's what I did :)

Dirty flash though :(
[SuperSU] eboissier:
No problem here on CM13 (sytemless+xposed+suhide...)
[SuperSU] Nightshadow931:
Is it possible to install an app as system app with systemless root?

Cause the way I see it, systemless root doesn't touch /system partition, yet again I did change my build.prop, which is located in /system, and it worked fine.

So I don't really get that part, could someone explain it to me? :)
[SuperSU] egingell:
There is literally no functional difference. You can still do anything root can do.

Sent from: LG G4 MM 6.0 / SGS5 MM 6.0.1
[SuperSU] Nightshadow931:
But if I move an app to /system, I directly change /system partition, and the point of systemless root is not changing system partition, that's the part I don't get.

Also, if I do that, am I still going to be able to use FlashFire for OTA updates as I did before?
[SuperSU] egingell:
It doesn't block modifications. It's just how it's installed.

Sent from: LG G4 MM 6.0 / SGS5 MM 6.0.1
[SuperSU] ianmacd:
'Systemless' merely describes how your root is installed. It doesn't affect your ability to undo its advantages by modifying /system yourself.

And yes, one of those advantages is receiving OTAs. You will no longer receive them with a modified /system. Instead, you'll have to download the file yourself and flash it using, for example, FlashFire.
[SuperSU] tropicanapure:
Well from op3 and opo experience, custom recovery is the main hurdle in the way of installing OTAs. They will restore stock recovery on install.

To specifically answer your question, I use systemless root but am still required to reinstall root every time after I manually TWRP on the OTA.
[SuperSU] mielletseed:
Then uninstall SuperSU Pro app like you uninstall any other user app (from launcher, from settings) when you get headaches about it....

The /supersu folder in TWRP is part of TWRP and has nothing to do with your Android installation
[SuperSU] hammerhead2:
I admit I did not write this, but I did this already, as it's quite obvious; moreover I did not want to "mix roots" (magisk works better with phh's root).

That being said, I did all obvious steps, including reflashing stock, I was quite surprised that remains of supersu survived it, and that's the reason I am here bothering you.

Edit: You were right, at least to some extent. Supers was installed as system app and at the first glance not visible in app manager. It was listed when "show system apps" option was chosen and I removed it with no problem then. Sorry for messing around.
[SuperSU] Nightshadow931:
That's perfect, thank you very much.
[SuperSU] yelupic:
A couple of weeks ago, I had the same question and found this dirty hack for me on a systemless rooted Moto E2 with Marshmallow stock ROM, keeping the system partition absolutely untouched:

How to move a userspace app to a system app (systemless rooted device)

You have rooted your stock-rom device systemless (existing /data/su.img which gets mounted to /su/)

Now install an app to be converted into a system app the "normal" way as a user app (into /data/app/)

With a root file explorer of your choice open /su/

Create the folder /su/app/ (root:root -rwxr-xr-x 0755)

Copy your desired user app - the whole folder from /data/app/<your app folder to move> to /su/app/<your app folder to move>

Rename (or delete) the original folder of your app (/data/app/<your app folder to move>) to keep the app's /data/data/ folder (if there is no need to keep it, just deinstall the app)

Change into folder /su/su.d/ and edit (for the first time create) an init.d-script (i. e. 01-my-sys-apps-bind-mounts) with permissions root:root -rwx------ 0700

Open this file and add a line like this to it:

mount -o bind /su/app/<your app folder to move> /system/app/<already existing and not needed app folder>

One simple example:

Firstly install Lightning browser form F-Droid app store (or Google Play Store)

Then copy its whole folder acr.browser.lightning-1 from /data/app/ to /su/app/

You may rename the new folder (i. e. LightningBrowser or something else)

Then create or edit /su/su.d/01-my-sys-apps-bind-mounts adding the following line:

mount -o bind /su/app/LightningBrowser /system/app/Chrome

where "LightningBrowser" is the browser Lightning from F-Droid app store and "Chrome" is the already installed Chrome browser by Google (one of the stock's system apps which we don't want to use/need)

Save the file

Reboot

Now the Lightning browser will behave like a system app and the Chrome browser has gone - like in "is uninstalled" (it is still there in the untouched system partition but overlayed by Lightning browser)

So the trick here is really simple:

Choose an already installed system app which you don't need and abuse its /system/app/ folder for your desired (system) app by using a bind mount (script) under /su/su.d/

Another advantage is, that all your (faked system) apps sit in the small su.img and can easily be backed up, restored, even moved to another device (same model/Stock-ROM, after having rooted systemless).

Note: I didn't face any side effects, but there could be some. - Also I only chose folders of unimportant system apps (Chrome, YouTube, Drive, GMail etc.) which I don't use/need to be abused by my apps, no "real" core system apps.
[SuperSU] Nightshadow931:
I've already moved my app to /system/app, and that worked just fine.

What's the advantage of doing things your way?

I guess the ability to use android pay, since /system stays untouched?

Will it survive factory reset that way?

Cause I need it to.
[SuperSU] yelupic:
If you move apps (directly/physically) to your system partition, it is no more untouched.

I described a way to circumvent changes to the original system partition when it comes to alien (system) apps.

And no, it won't survive a factory reset, because your data partition (containing your /data/su.img) gets also vaporized.

But there is always hope:

just save /data/su.img somewhere on an external SD card / USB-OTG stick / computer before the factory reset

perform your factory reset (data and so root will have gone afterwards)

(you need the original boot.img in place before)

boot up until the first homescreen (here you are unrooted and have none of your own (system) apps)

reboot into twrp recovery

root your device systemless

boot up until the first homescreen

reboot into twrp recovery

copy your saved su.img over the newly created /data/su.img

reboot your device

your faked system apps (and other tweaks), sitting in su.img are back again without further work, the system partition has been left original

(that was my point in my pre-posting)
[SuperSU] Nightshadow931:
That's good workaround, but the app I'm converting is an app for remote controlling my phone, in case it gets lost or stolen. So if thief does a factory reset, I'd still be able to remote access my phone and determine its location. :)
[SuperSU] yelupic:
Ok, then I'm off for now. - This is a very special use case of yours, you didn't mention before.

(BTW: Unlocked bootloader > boot into bootloader > fastboot flash "full stock firmware" > your tracking app has gone > thief happy ...)
[SuperSU] OsniNO:
It's not working with CM 14 - Moto G 2014
[SuperSU] Nightshadow931:
Of course, but how many people would know to do that? :)

He could just go to file explorer and delete the app like I installed it. But most of the people would just do factory reset :)
[SuperSU] grep_i:
Almost everyone in here I guess
[SuperSU] StormCell:
I an now unable to install in system after switching to PureNexus N. Am I missing something?
[SuperSU] pkelly517:
PN doesn't have the selinux code to run system mode.
[SuperSU] kojak1989:
How to make systemless root to work ?
[SuperSU] Ch3vr0n:
By reading/searching the last few pages yet again for 'systemless mode'. That question is like asked a dozen times ever few pages.
[SuperSU] i42o:
If you're not gonna say anything productive, why even waste your time? i dislike people that act this way. Edit. _end rant
[SuperSU] Ch3vr0n:
That is productive. There's no point in constantly repeating the same thing every few pages. And it's the same thing other people constantly have to say as well. That's what the forum search was invented for. And it's ok, I don't dislike you. I'll leave it at that. Have a nice day.
[SuperSU] grep_i:
Now this is not productive too telling someone you dislike people like him without knowing the person.

You could have said you dislike how he acts.

In his defence he is right that we do not have to repeat the same answers every 10 posts that is so unproductive.

Study the rules and learn to use the search function and than we can discuss new issues without discussing the same things over and over again because people do not want to read up or search first for an answer.

And yes he is one of the person's who answers the same questions over and over.

Please don't be offended by this but see it as a tip or advice to keep this forum sane.
[SuperSU] Ch3vr0n:
Not a superSU problem. There's multiple ways to replace kinguser with superSU. Most of them can be found through forum search, Google search or both.
[SuperSU] Cyan-Bird:
Method?*1:?*Download?*SuperSUme?*to?*replace?*it?*.Method?*2:?*replace?*system/ Xbin?*with?*SU?*file,?*Steps?*:?*Step?*1:?*Install?*Root.Explorer?*APK.Step?*2:?*Rename Su to .SU?*Step?*3:?*Copy .SU to system/xbinStep?*4:?*Authorize?*Su?*(chmod?*0777?*.su)Step?*5:?*delete?*the?*other?*SU?*files,?*such?*as?*ksu,?*etc.Step?*6:?*Rename.SU?*to?*SU?*Step?*7:?*Go?*back?*to?*the?*desktop?*to?*delete?*the?*other?*authorization?*apps
[SuperSU] egingell:
What the crap? We're supposed to be helping people here, not confusing the hell out of them.

Sent from: LG G4 MM 6.0 / SGS5 MM 6.0.1
[SuperSU] thogz11:
Working great!

Nexus 5 7.0 Nougat AOSP.

Thank you!
[SuperSU] aggie113:
Galaxy s4 AOSP 7.0 issues

Installed after loading AOSP 7.0-20160909-jftle-gsm rom on my S4 and it is not rooted. Also attempted Beta SuperSU 2.77-20160827190633 with same results.
[SuperSU] dark_boy99:
where are i can translate app for persian?
[SuperSU] AmanoTooko:
The post content is old and has been re-edited.
[SuperSU] paktepu:
zip file corrupt

Download many times but always got corrupt zip file. Anyone has a mirror please? Thanks.
[SuperSU] Einwod:
It is not corrupt. There is no need to "test" the file, simply flash it in TWRP. It works.
[SuperSU] paktepu:
Thanks for your response..

Usually i always check every zip file with rar.apk to check. But thanks for your confirmation. Its work great.
[SuperSU] GustavoWiesner:
In my Moto Android Stock 6.0.1, it stays in the logo :(
[SuperSU] egel1:
Hi my SuperSU Not updated Flashed v2.78 and binaries will not update. Any suggestions?Now I have TWRP Recovery without root,I have tried everything

But nothing,I am using note 4 Stock Marshmallow 6.0.1.thanks
[SuperSU] Chaud227:
Any chance for LZO compression support in the future?
[SuperSU] pra27:
forcing systemless mode

can anybody help me by giving information on "forcing systemless mode every time i flash supersu zip". ?
[SuperSU] hammerhead2:
I might be out of the loop a bit, but I just wanted to report that on n9005 I flashed with flashfire last avaliable firmware over cm13. Root was preserved, safety net was red. Then I installed root switch and SN is green now.

Phone had bootloader factory unlocked.
[SuperSU] Chaud227:
What ROM specifically and kernal are you using? And did you flash SuperSU 2.7.8 and suhide as well to get it working?
[SuperSU] hammerhead2:
No suhide.

The rom is N9005XXUGBOK6_N9005XEOGBOJ1_XEO from sammobile I guess. Stock kernel.

Edit: Sorry, it is stock.

Su version is 2.78-SR1. It is NOT systemless.

One more thing: twrp is also there.
[SuperSU] hammerhead2:
Follow up.

It no longer works...
[SuperSU] Ch3vr0n:
2.78 is systemless just fine. Your rom needs to support systemless.
[SuperSU] str8str:
It is systemless you need to install it in correct order been using it for months

Sect From Me, Is That You?

---------- Post added at 20:25 ---------- Previous post was at 20:23 ----------

Install from play store is easiest

Sect From Me, Is That You?
[SuperSU] USBhost:
Flounder/Nexus 9 BUG report...

sukernel v2.77 (ndk:arm64-v8a) - Copyright (C) 2014-2016 - Chainfire

Loading from [/sutmp/ramdisk.original] ...

Loading from [/sutmp/ramdisk] ...

Creating [.subackup] ...

Append@0000 [* file_contexts.bin 0000_file_contexts.bin]
Creating [.subackup/0000_file_contexts.bin] ...

Append@0001 [* fstab.flounder 0001_fstab.flounder]
Creating [.subackup/0001_fstab.flounder] ...

Append@0002 [* fstab.flounder64 0002_fstab.flounder64]
Creating [.subackup/0002_fstab.flounder64] ...

Append@0003 [* init.environ.rc 0003_init.environ.rc]
Creating [.subackup/0003_init.environ.rc] ...

Append@0004 [* init.rc 0004_init.rc]
Creating [.subackup/0004_init.rc] ...

Append@0005 [* sepolicy 0005_sepolicy]
Creating [.subackup/0005_sepolicy] ...

Segmentation fault

This causes the whole installation to stop on NONE STOCK boot images.

On the stock boot.img it flashes just fine no problems but if its not stock, like AOSP, CM, DU etc it will fail.

This happens on marshmallow(sometimes if the boot.img was modded) and nougat(always)

check_zero_def "- Creating ramdisk backup" "LD_LIBRARY_PATH=$SYSTEMLIB /su/bin/sukernel --cpio-backup /sutmp/ramdisk.original /sutmp/ramdisk /sutmp/ramdisk"

Removing that line allows it to install just fine.
[SuperSU] fhem:
I am seeing the same thing on my N9. Hope you get an answer. Thanks for posting here. :good::good::good:
[SuperSU] grep_i:
Answer on what the guy literally posted the answer on how to complete flashing.

Just remove lines of creating backup of ramdisk, probably the compression method used in the custom boot.img is not supported, SuperSU only supports gzip and raw Android formats.
[SuperSU] fhem:
:o:o:o My 71 year old brain gotta learn to understand what I am reading better -- Thanks :good::good::good:
[SuperSU] Timster292:
I'm sorry if this question is stupid but where do I have to remove the lines? So where do I find them.
[SuperSU] USBhost:
It's gzip.... So it should have worked.

If it was not gzip it would have failed to decompress the ramdisk.

Backing up the ramdisk is where it failed.

Haha np!

Remove it from /META-INF/com/google/android/update-binary

But before doing that try the latest beta

It seems to have fixed the problem.
[SuperSU] Nekromantik:
Got weird issue. Running aosip rom on n6p and it comes with supersu 2.78 and states installing in system less mode however there is su binary in /system/xbin and if you temp disable root and re enable some apps like titanium backup can't detect root any longer.
[SuperSU] a**hole:
YuYureka!!!

Motherbuddy plz tell me how the puck will i root my YU Yureka 7.1 unofficial with this ? will it work ??? Or will the older version of SuperSU work ???? Tell me plz Brooooollol.
[SuperSU] Chainfire:
Can you post a boot.img on which installing SuperSU would fail ?
[SuperSU] USBhost:
Will do man!

When i get home.

Also note this http://xdaforums.com/showpost.php?p=69416083&postcount=7751

Edit: make that in the morning!
[SuperSU] The Pope of Dope:
I'm pretty sure they don't speak retard here.
[SuperSU] Happy_Alien:
Honor6

My Honor6 got B860 (A6/MIUI4) update tonight and root is gone :D ReRoot with multitool done without errors (SuperSU 2.78 aborted, lower versions without errors), app still installed, but problem with su binary and I am unable to get it works again... TWRP and ZIPs/Multitool/Kingo and nothing. Anyone who solved this?
[SuperSU] grep_i:
Can you post your recovery log maybe someone can find your error in there.
[SuperSU] Happy_Alien:
H60

Here it is (Multitool + SuperSU 2.70):

https://goo.gl/dbP2EZ
[SuperSU] grep_i:
Your boot partition is too small it's only 14MB.

During flashing of boot.img it runs out of space.

It's printed in the recovery log you posted.

Mine is 16MB and has no problem, I do not know if that would be enough for your case and how you can change your partition easily and safely.

Guess for that you have to search forum or Google.
[SuperSU] Happy_Alien:
Damn. :) I overlooked that in the log. Thank you... Ill do a backup and try to find a solution.
[SuperSU] fhem:
FYI: I tried with beta SR2 no go. I also tired removing that line from the update-binary on both SR1 and SR2 still no go. I am simply replacing my ROM boot image w/ the stock boot image. That is all that works for me.
[SuperSU] USBhost:
https://drive.google.com/open?id=0B1cOHQ70J9vlZ3pJcXE5bGxWa00
[SuperSU] Chainfire:
This should be fixed in v2.78 SR3 (out soon)
[SuperSU] Artieza:
[MENTION=631273]Chainfire[/MENTION], could you explain why SuperSU 2.65 works well with Link2SD (http://xdaforums.com/showthread.php?t=919326&page=544), but all newest versions forbid apps which was moved on external SD?

/data/sdext2 is mounted, I can check this partition via file explorer, all aps here, but system doesn't see it.
[SuperSU] ldeveraux:
It doesn't do that on lollipop s5.
[SuperSU] Artieza:
I know that not all users of Link2SD faced with this problem. But I know that I'm not only one. I'm on Android 5.0.2 too. Maybe, it is kernel/system specific...
[SuperSU] Chaud227:
Can this still happen please? And if not, is there another easy solution, for example, changing the compression on Arter Kernal for the Note 3 to gzip or the other compression format that systemless SuperSU works with? Not sure if its possible or how one would do that, information is scarce on the issue besides a tutorial that temporarily changes the compression while in adb and changes back with a risk of brick if you reboot before finishing. I'm uncomfortable with that particular tutorial.

*reposted from beta thread for visibility*
[SuperSU] bovirus:
[MENTION=7678190]SuperSU Release[/MENTION]

In the first post is reported SuperSU zIp file for TWRP as v. 2.78 (01.09.2016).

But the latest is 2.78 SR1 (15.09.2016). Is it beta?

Why is not reported this?
[SuperSU] Ja_som:
Latest is 2.78 SR3, but this is stable thread and "SR" are "beta"
[SuperSU] bovirus:
@ Ja_som

For me SR means Service Release that has a different meaning than beta.

Service release is an official patch.
[SuperSU] grep_i:
Good for you but you can find them in the SuperSU beta thread
[SuperSU] hotland:
may i know how do i uninstall supersu? i tried using the full unroot option but it says uninstall failed
[SuperSU] Einwod:
Dirty flash your current ROM as long as it is not rooted.
[SuperSU] grep_i:
I have a flashable zip for that.

Try it out
[SuperSU] magicreal:
hello guys i have a problem, i reinstall my MM rom(clean install, same rom) and i select the titanium folder on my SD card(like always i format) but strange things happen, titanium see my backup "112 backup"but in the section "restore" 0 backup, maybe is there a problem with last supersu? i cant understand cos is same rom versions, same titanium version and always work, thank you for help
[SuperSU] Federacion:
Anybody knows how to stop Xposed installer constantly asking to update?
[SuperSU] KOLIOSIS:
I havent used Xposed in a long time,but,can you turn off the notifications for that app/.apk,under SETTINGS > APPLICATIONS > XPOSED INSTALLER & turn off notifications?

Again,not sure if it's an option,but,just throwin' it out there.........................
[SuperSU] tanzan:
SuperSU 2.78 (1.09.16) doesn't install binary on alcatel pixi 3 4.5 4g (5017a)

Hi there.

My phone crashed last week and the only way to recover it was to use the system update (from windows pc) on the phone, which it did. This wiped everything (was okay with it), however when I try and install superSU either the .zip or the .apk (and i've tried even both at once), the furtherest I can get is 'we need to install the supersu binary' i've tried it while running, and i've tried installing it from the .zip. She just doesn't want to install.

I should point out that it doesn't reboot onitself into crwp, I have to manually restart it. Is there a way to manually install the binary in crwp? or is that what the supersu.zip is about?

Any advice would be great,

thanks guys, keep up the good work!
[SuperSU] Federacion:
Not working unfortunately but thanks for the reply
[SuperSU] andrew2432:
Bro you got 2.78 working on your s5? Systemless? Which android os version??
[SuperSU] ldeveraux:
As I said, lollipop (5.0) and no, it's not systemless.
[SuperSU] andrew2432:
Ok, are you trying to hide root or not then??
[SuperSU] Lw00d:
Nexus 6P

i had rooted andriod 6.1.1 systemless expose. i updated to 7.0 nov security .. i updated with ADB. update went smooth.. had all my apps still installed . no setting lost.. but i notice i lost root.. so i installed twrp 3.0.2-3 . thats the twrp compatible with 7.0. i flash superSU v2.78 stable. wipe cashe/delvik , reboot system. . but phone never boots up. stays in boot screen..

the only way to start phone is to flash boot.img and system.img.

i try three different factory images.. superSU will never let phone boot up.. i even try superSU SR3.. same thing phone will not boot up..

i also try uninstalling busy box., flashfire, then flash superSU still phone will not start.

what should i do??
[SuperSU] mobileman88:
I think the November 7.0 update has some compatibility issues. In the October update NRD90X I was able to root with all versions of SuperSU 2.78 , 2.78SR1, SR2, SR3 and phh r259 r266 . However I have been stuck in the boot screen of the Novemer update nbd91k . Thanks.
[SuperSU] Lw00d:
i try two other factory images. the same happens
[SuperSU] ajay vadaparthi:
In custom roms, even after enabling root access in developer options. supersu shows that binary is to be updated. upon updating, it shows the phone is not rooted. should i have to root my phone or i have to flash the supersu zip?

i flashed supersu zip file and wiped cache & dalvik cache but when booted into system, bootloop occured. please help me