yashsingh1/xdaforums huggingface dataset:
[SuperSU] d8389:
.zip installed after kernel

Galaxy S7 International.

Android 6.0.1

Custom ROM based on G930FXXU1BPH6 (I'm developer)

No interfering apps.

--

shell@herolte:/ $ which su

which su

/su/bin/su

shell@herolte:/ $ ls -l `which su`

ls -l `which su`

-rwxr-xr-x root root 108480 2016-08-22 07:19 su

shell@herolte:/ $ which su

which su

/su/bin/su

shell@herolte:/ $ uname -a

uname -a

Linux localhost 3.18.14-prometheus-v1.5.3 #1 SMP PREEMPT Sat Aug 27 10:53:02 EEST 2016 aarch64

shell@herolte:/ $
[SuperSU] ulxerker:
try it vice versa, first supersu and then the kernel. also, you might want to ask for help in the S7 subforums.
[SuperSU] d8389:
same result

I can ask help from myself only...
[SuperSU] stoeggich:
instalation fail

sony m4 6.01 stock rom
[SuperSU] Heisenberg:
[Size=+1]Thread cleaned. Again.

As was previously pointed out by another moderator this thread is not the place to discuss the handover of SuperSU or how the company needs to prove itself. This thread is solely for the discussion of SuperSU itself. No more off topic please.[/sizE]
[SuperSU] HorstiG:
I have intsalled Susi from store without problems on your ROM.

View attachment 3862562
[SuperSU] Mainaharen:
SuperSU v2.78

I upgraded through TWRP flashable zip,Running smoothly in my Sony xperia E3 ,No su binaries update issues.
[SuperSU] ipdev:
Upgraded by playstore. Seems to be working fine.. ?

Question is why did some, not all of my settings change?

2.77 was installed into system and now 2.78 it is not.

(Install backup script for updates is not there now?)

Android 4.4.2 :(

Edit:

Took another (fourth reboot) and now all my settings are reset but, I am back to installed system app. (Still no backup script ?)
[SuperSU] str8str:
If you want to stay or be system less it's super su then kernel. Same if switching kernels

Straight from the one and only Straight Shooter. ?
[SuperSU] NYLimited:
A quick question...

In order to install suhide we need to flash both, suhide and Supersu in order to avoid boot loops.

Since 2.78 now updates from GP how do we accomplish the above?? I can't flash a GP download and I'll possibly have bootloops after installing suhide and before going to GP.

So, what do we do?

Inquiring minds want to know...
[SuperSU] osm0sis:
The latest zip is linked in the OP. I flashed it this afternoon with suhide and it's working perfectly. :)
[SuperSU] GrayJack:
Just upgraded from 2.76 to 2.78 through recovery (SuperSU in system partition) on both devices. Surprisingly I see two icons of the application, both start 2.78. The only app file is in /system/app.

No idea what is going on.
[SuperSU] santod040:
A very brief search brought me here: LINK

Good luck, XDA Search and Google are your friends... :good:
[SuperSU] terrorist96:
I looked around and didn't see anyone directly ask [MENTION=631273]Chainfire[/MENTION] if he will make changes in a future update so that we can use Magisk plus SuperSU plus xposed. Can you please make any comment? I would prefer to continue using SuperSU, but might have to switch to **the alternative** which allows for using Magisk with Xposed. Please let me know if I should stick around or if I have to switch. :)
[SuperSU] Bormental:
There is no solution in that thread. The method from the link works only in lolipop. I know about search and google and came here for the last chance :(
[SuperSU] dhampire:
Good afternoon.

My device is Zenfone2 (ZE551ML) x86 base.

with shakalaca's patched version,

http://xdaforums.com/zenfone2/general/root-using-tethered-twrp-to-root-t3458475

It works very well but no patched version will not suitable for ZE551ML(I did not tried) they said.

Do you think you can use his patch to official version?

Regards.
[SuperSU] tuiyaan:
both post asked by me:D

tried it but still same result

patching sepolicy

---failure aborting
[SuperSU] ianmacd:
Xposed will run on Magisk + SuperSU, as far as I'm aware, although Magisk's SuperSU support is rapidly dwindling and is now only nominal. I think it's only Magisk's dynamic root disablement feature that won't work with SuperSU.

I'm also interested in trying Magisk, but am not prepared to compromise on which root manager I use; nor am I prepared to run someone else's patched version of SuperSU.
[SuperSU] jalizi:
Hi

What is the meaning of SystemLess or SystemMode SuperSU?

What's the difference between theme and which one is better?

If I want to use SuperSU 2.78 for Samsung Galaxy J7 SM-700F , which type of SuperSU should I use and what Custom Kernel you recommend?

Please take a look at the picture and tell me what's the problem.

Regards
[SuperSU] DeathArrow:
No, I didn't install xposed before installing SuperSU.
[SuperSU] seschaum:
Failure on OnePlus3 with MoKee ROM

Hi all,

I just unlocked my OP3 to switch to MoKee (latest daily snapshot / 1209 NIGHLTY currently),

but I just can get SuperSU to install correctly.

I'm using the latest TWRP from twrp.me also

I always get:

******************
Boot image patcher
******************
- Finding boot image
--- Boot image: /dev/block/sde18 -> (which is the correct partition)
- Extracting ramdisk
- Decompressing ramdisk -> (RAMDisk is compressed with gzip fyi)
--- Failure, aborting

Anyone else a suggestion or idea?

Thanks already in advance!
[SuperSU] NLBeev:
Root checker could be obsolete.

Use a terminal emulator and type on the command line 'su'.

You will get a different prompt when superuser is installed.
[SuperSU] terrorist96:
I wasn't referring to the patched version of SuperSU by the Magisk dev. I was talking about the alternate SU app that I'm not allowed to mention by name, even though I already technically did.
[SuperSU] all_about_droid:
Ive rooted my note 5 and had root access at the time. Just redownloaded setcpu and superuser states that the su binary cannot be found. Do i need to re root my phone again? Or is there a way around it?
[SuperSU] egingell:
Do you mean SetCPU can't find the su binary?

Sent from: LG G4 MM 6.0 / SGS4 LP 5.0.1
[SuperSU] ianmacd:
I knew you were talking about a different app, but you said:

In response to that, I was making the point that you don't need an alternative root manager in order to use Magisk with Xposed. SuperSU will work, although support for it is nominal at this point.
[SuperSU] Bormental:
Anybody knows, is there any way to root android 6.0+ without modifying app_process binary?
[SuperSU] jesssiii:
Yet another great reason to root! ;)

Nexus 6P
[SuperSU] meleelord:
Okay guy's, so I'm on the Nexus 6P. My bootloader is unlocked, I'm on the factory released nougat, I have the newest TWRP, tried flashing SuperSu, and my phone keeps getting stuck on the Google boot animation when I flash the latest version of SuperSu.. Anyone possibly able to help please?
[SuperSU] janedoesmith:
I have the same exact setup. I had no issues. Define "getting stuck". The first boot after flashing SuperSU did take some time to complete.
[SuperSU] hoangphuc057:
Boot loop g3 android 7 aosp rom :(
[SuperSU] meleelord:
The boot animation just keeps going and going, no reboots occur. How long did you have to wait?
[SuperSU] Artieza:
I got issue:

mkdir*-p*/storage/emulated/0/2
exit
mkdir*failed*for*/storage/emulated/0/,*Read-only*file*system

It was fixed by activating name-separated space in SuperSU settings. But anyway, it's a bug, which can confuse many users.

Here is my build.prop: https://drive.google.com/file/d/0B2KH4VEXC-hjcDBUZnN5YUwtOEk/view?usp=sharing

P.S. Tried also SR3. Same.
[SuperSU] jcmm11:
Works fine here. This is SR3 in SBIN mode, Pure Nexus 7.1.2 (July)

bullhead:/ $ su
bullhead:/ # mkdir -p /storage/emulated/0/2
bullhead:/ # echo $?
0
bullhead:/ #
[SuperSU] Artieza:
That's fine, but we all know that all this is Android version / device specific issues. Some range of devices with disabled name-separated space is affected.
[SuperSU] Refax:
Hello, my Samsung Galaxy S3 Mini is not booting (shows only logo screen) i got a Resurrection Remix 7.1.2 installed and i tried SuperSu 2.82 SR3 and SuperSu 2.82 STABLE and phone is still not working, help.
[SuperSU] bearusa:
Restore from a nandroid backup, if that don't work just reflash the rom,
[SuperSU] SPOROOT01:
Ok
[SuperSU] skastream:
Is SuperSU-v2.82-SR3 working with android 6.01 too?
[SuperSU] Ibuprophen:
Yes.

It's working on my GS5 & GS3 both with Android 6.

~~~~~~~~~~~~~~~

I Am The Egg Man,

They Are The Egg Men.

I Am The Walrus!

Coo Coo Cachoo!

I DO NOT PROVIDE SUPPORT VIA PM UNLESS ASKED/REQUESTED BY MYSELF.

PLEASE KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
[SuperSU] KaMyKaSii:
We certainly have not been abandoned yet. At most there may be some incompatibility with your rom/device in particular, in that case report any problems with logs and detailed description
[SuperSU] Refax:
I just reflashed rom, and i didn't know that it has an built-in root in developers menu xD
[SuperSU] bearusa:
Personally I don't use the built in Root,, I always flash SuperSu, and have never had any problems,,
[SuperSU] f.a.tonmoy:
what about Nougat??
[SuperSU] Ch3vr0n:
what about it? works just fine
[SuperSU] Ashyford:
- Exact device model

AT&T Galaxy S4 i337

- Exact firmware version

MDL bootloader, OK2 baseband

Optimized Lineage 14.1, Stable 6

Alucard Kernel

- Exact Android version

Android 7.1.2

- Exact SuperSU version

2.52 and 2.82 sr3 systemless are currently working for Optimized Lineage 13.1 stable 5 but not for Optimized Lineage 14.1 stable 6. I also tried SuperSU 2.65, 2.71, 2.79, 2.79 sr3, 2.82 sr3 (systemless and forced system where possible).

- Interfering apps

None to my knowledge but a Clean install with BusyBox (symlinked or non-symlinked) is included in the ROM.

- Install methods tried

ZIP via TWRP.

- What kind of root are you left with?

Not able to install root.

- Logs from TWRP and ROM included

Anyone here successfully flash and root Optimized LineageOS 14.1 stable 6 on a Galaxy S4 i337 model on an MDL bootloader? Optimized LineageOS 13+ works fine for me but I lose root when flashing Optimized LineageOS 14.1. (Specifically, the SuoerSU install process aborts when ramdisk decompression fails on the boot image.) Subsequently, when I flash SuperSU 2.46, 2.52, 2.71, 2.79, 2.79 sr3, and 2.82 sr3, I'm stuck booting for 20 to 30 minutes before I give up. (SuperSU 2.52 works for Optimized LineageOS 13+.)

After clean installing the ROM, do I need to uninstall SuperSU completely (using un-SU zip), reboot, flash Loki, reboot, place the latest SuperSu 2.79 sr3 zip on the internal storage, force SuperSu system mode install, and then flash it? Or, do I need a patched boot image?

Thanks!
[SuperSU] CaptianXLAB:
In short, for Zenfone 2 ZE551ML running Android v5.0 LP (Stock), Using TWRP v2.8.7.2, all I have to do is put the TWRP Flashable zip in my phone's storage/MicroSD and flash it?

I just unlocked my Zenfone 2 ZE551ML's bootloader and successfully installed TWRP. At first, I thought TWRP will make changes to system files so I went for the read-only way for the backup of all partitions (using TWRP v3.0.0-0-Z00A). When I first installed TWRP on my other phone, Zenfone Max ZC550KL, it offered me an option to root first which was the easiest. To try and get that again, I reflashed, didn't offer. I flashed an older version (v2.8.7.2-Z00A.img) and it still didn't offer. That's when I came here.
[SuperSU] DB126:
Tip-of-the-hat for an outstanding problem description (full post here). While I can't answer your immediate question (prefer the integrated root manager with LineageOS based ROMs) I would be remiss in not acknowledging the fine investigative efforts put forward to date.

Long shot thought: A special LineageOS build is needed to accommodate SuperSU. Any chance the Optimized LineageOS 14.1 for this device has not been set up for switching over to SuperSU?
[SuperSU] Ashyford:
Thank you! I respect the time and patience invested in this project as well as assisting others with their challenges and try to do my part in upholding the values of the forum.

Good question regarding set up for switching. Optimized LineageOS 14.1 Stable 6 for the Galaxy S4 variants via Aroma install provides install choices of Privacy Guard, SuperSU, and Magisk. SuperSu and Magisk fail for the same reason resulting in post install SuperSU efforts. I can try the non-Aroma install but suspect the same issue will occur because of the locked bootloader. I'm stumped at the moment and open to suggestions after exhaustive flashing and bootloops for a week.
[SuperSU] jipis:
SuperSU flashed but not installed

I've been fighting this for a while at this point. I, at some point, must've accepted an OTA on my OnePlus 3 and lost root. (I didn't think that was possible, but :confused:) I've been rooting phones since the HTC Evo 4G, so 7 years? I've never had an issue like this before....

I flashed TWRP 3.0.4-1, no problem.

No matter how many times I try to install SuperSU, I fail. I mean, it *LOOKS* like it worked. But, when I boot back into OOS, no app installed.

I grabbed a log of the flash run. I see a bunch of failures in there, but I'm at a complete loss as to why. Specifically, see lines 670-685ish. Log at tinyw.in/Cp3r.

Anyone?

Thanks!
[SuperSU] Ch3vr0n:
just install it from the play store or grab the apk from within the zip
[SuperSU] DB126:
Agree with [MENTION=1754043]Ch3vr0n[/MENTION] if simply missing the app. If the problem persists after installing the apk give 2.82 SR3 a whirl which addresses several installation/stability issues.
[SuperSU] roelandjansen69:
S6 (ATO jul update and TWRP sideload fail

I have been searching high and low -- up till now no way I have managed to regain root.

I had my phone updateed to the jul security patch and reinstalled twrp.

I went into the recovery but could not locate the zip on the phone to flash so I decided to do a sideload.

(apply update from sd-card..??) -- checked zerofltexx/zeroflte

No matter which version I try, I get

adb sideload and E:footer is wrong E:Signature verification failed

installation aborted.

but the integrity of the file(s) are OK.

Now looking for other people who succesfully updated the stock ron, reflashed TWRP via odin and

supersu. Note that CF-autoroot, working on the previous version also does not work.

I do see some posts about DM-VERITY and I start to believe that I have missed a lot lately ..

Obviously nobody wants to brick the phone but I was hoping that someone could tell me what I mis-do here.

XDA itself does have so many posts that I haven't found any fixes there ...

Linux localhost 3.10.61-10958180 #1 SMP PREEMPT Tue Jul 4 19:45:39 KST 2017 aarch64

build NRD90M.G920FXXSSEQG1

twrp 3.1.1.0

suspersu 2.82 latest

Roeland
[SuperSU] jipis:
Thanks, [MENTION=5488402]Davey126[/MENTION] and [MENTION=1754043]Ch3vr0n[/MENTION]! I'm not sure why I didn't just try that first.... In fact, I expected that to completely fail and to report back as such.

But, nope!! I'm good to go. Woohoo for SuperSU actually being installed!!
[SuperSU] sclarckone:
Honor 5C running Android 7.0/EMUI 50.

Whenever I open the SuperSU app, it says that the SU binary needs to be updated then fails. I'm not sure which version I've originally flashed (could be v2.79 since it's the one present on my SD card) but my current version is 2.82.

I'm also a bit confused about this "binary update" since I'm pretty sure I have a "systemless root" and I thought it consisted in a modified initrd.

Any idea about what's happening here?
[SuperSU] Ch3vr0n:
If the app itself fails to update binaries, flash the SuperSU zip that updates them too. There's a real easy way to find out if you have systemless or not. Check the SuperSu app, if you can't select "move to system" then you've got systemless or something along those lines
[SuperSU] sclarckone:
That was the case for the "move to /system", plus typing "which su" in a shell didn't point to /system/xbin so I was pretty sure that it was a systemless root.

Anyway I flashed the latest stable and it worked, thanks! I think I got a bit confused since the Android app was showing v2.82 but it's probably not related to the binary/initrd version.
[SuperSU] Gsmmonju:
Give me
[SuperSU] Ch3vr0n:
Give you what? An asswhooping?

Sent from my Nexus 6P with Tapatalk
[SuperSU] Ibuprophen:
Hello Again Gentlemen! :D

I was hoping one or more of the fine experts here could take a quick look (if you haven't already) at a recent issue that a member, [MENTION=4699730]Vinnom[/MENTION], had posted on the "SuperSU SR" Thread.

I had responded to it but, I'm not sure if I've either read the issue correctly and/or outlined (what i had felt) the gaps/missing information provided by that member.

Any additional assistance would be well appreciated.

Thank you ALL very much for your time and understanding!

~~~~~~~~~~~~~~~

I Am The Egg Man,

They Are The Egg Men.

I Am The Walrus!

Coo Coo Cachoo!

I DO NOT PROVIDE SUPPORT VIA PM UNLESS ASKED/REQUESTED BY MYSELF.

PLEASE KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
[SuperSU] callihn:
I tried whatever the PlayStore is offering, I assume 2.82 SR 3.
[SuperSU] jcmm11:
No. Play Store only has stable releases. SR releases are testing (beta) releases. SR3 is now latest, back then it was SR1. Get SR3 here https://xdaforums.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133 then flash the zip via TWRP.
[SuperSU] nitzero:
I'm sorry if it has been addressed before but I've been trying to cook a rom with PRF Creator for my mom's Xperia Z3.

Seriously I was about to give up, tried many different ways and rom versions and the phone would end up in a boot loop.

Then I found a working Lolipop rom on the Internet and borrowed the SuperSU zip from it along with the updated recoveries.

It just worked. [emoji31]

So SuperSU binaries 2.82 asked to update. Why not? Bricked again [emoji37]

Flashed everything again and not gonna update it anytime soon.

Running Sony stock rom 6.0.1

Enviado do meu iPhone usando Tapatalk Pro
[SuperSU] grmpf72:
just want to add that my Nexus 10 / Android 5.1.1 (J) is also affected by the "optimize apps bug" at every reboot! after all I read here and in other forums, the combination seems to be always Android 5.1.1 and SUPERSU >2.79! Hoping for a quick solution...
[SuperSU] Cookie Ninja:
The "Optimising Apps" is not a bug. It occurs because your ROM runs a script at every shutdown which causes the dalvik cache to be wiped, leading to the optimising at every start and longer boot up time. Find the script and disable it....no more boot up delays!
[SuperSU] grmpf72:
That confuses me!

1) How can I find and disable this script?

2) The behaviour also occurs if the Nexus shuts down "hard" (i. e. Power off button long press or sudden reboot after an App-error i. e. seen in Chrome under specific circumstances). In this case a shutdown script would not run.
[SuperSU] LaGgY_42o:
Haven't had that problem, just the one, ya know, where every single time before u restart u have to / and mount it rw, open init.rc with a text editor, and manually add in the clearly missing / Infront of init.supersu.rc, after doing that a couple of boots later I actually had a clear log instead of a billion errors a second about missing permissions and files.... Also how the hell do I get the stupid systemless install out of my root? The Nexus 6 doesn't get OTA's it's EOL, and who runs stock???? I come back from trying Magisk while only having it completely cause Sprint's VoLTE w/ Google Voice intergration to go haywire and stop all towers from accepting any LTE request and now this :( gonna go try the Aroma installer I guess, nothing else better to do at 4:32am lol.

EDIT::. Yea, no, still with the Aroma Installer on Pure Nexus (latest) flashed from the latest official 7.1.1 Google img, unlocked bootloader (since 2014) 72.03 boot, no encryption, 2 days of trying every possible combo it always ends in flashing systemless sbin root, which is for 8.0+ right? lol. Guess I gotta just hook up RSDlite and do a complete refresh again, every time it leaves every single partition besides Data/Cache/System registered as empty and no apps can find any shared files anywhere :-/
[SuperSU] callihn:
Thanks, I'll give that a try as soon as I find 2.79 in case the crap hits the fan again.
[SuperSU] jcmm11:
2.79 SR3

https://download.chainfire.eu/1021/SuperSU/SR3-SuperSU-v2.79-SR3-20170114223742.zip

2.79

https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.79-201612051815.zip
[SuperSU] callihn:
Thanks!

Tested, 2.82 SR 3 has the same issue, will not go past the boot animation, had to restore from system update.
[SuperSU] shu006:
Using 2.82 on Moto G5s plus. I am getting error "Root undetected" after sometime. Please help
[SuperSU] :
Could you update SuperSU so it works like Magisk and I can pass SafetyNet test/use Android Pay?
[SuperSU] Ch3vr0n:
no, that's what suhide is for. SuperSU is a SU management app, no more no less. If you want something to work like magisk, use magisk. Simple as that.
[SuperSU] jcmm11:
SuperSU 2.82-SR3 in sbin mode + suhide
[SuperSU] :
How do I do this?
[SuperSU] jcmm11:
First you go to the correct SuperSU thread, download the zip, and, at a minimum, read the release notes. They contain pointers to the AROMA configurator thread and to the suhide thread.

At a further minimum you should carefully read and follow the OP in the suhide thread, and pay attention when it says to read the about tab once you've installed it.

Since you appear to be search deficient I'll give you the first thread.

https://xdaforums.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
[SuperSU] Jstame:
Will this project continue to move forward or has it stalled out completely?
[SuperSU] jcmm11:
And why would you think it stalled out? There's ongoing development.

This is the stable release thread, if you want to see current action check out the beta thread. I even linked to it in the post before yours.
[SuperSU] Jstame:
Thanks never saw the beta link. Sorry for the misunderstanding!
[SuperSU] omer7:
I'm also facing the same issue on my mako running stock google factory ROM Lollipop. I flashed TWRP and flashed SuperSU latest version 2.82. But after flashing latter, whenever, i reboot my device, it starts optimizing all apps (which happens when u clear cache from recovery). On uninstalling SuperSU 2.82, this issue went away and my phone would reboot straight to homescreen without any delay.

Now, I'm going to flash SuperSU 2.46 (I had that in my computer), hope it works fine.
[SuperSU] jcmm11:
Try 2.82-SR3 first.
[SuperSU] omer7:
Now, I've flashed 2.46, and it is working fine. No optimizing apps appear on rebooting phone.
[SuperSU] R8xx:
Can't extract boot.img

Hello... i have a vivo v5 device ( MTK6750 ) i tried to install supersu 2.82 throught twrp 3.1.1-0

but it failed to extract the ramdisk with this error.....

[IMG="Error"]https://s26.postimg.org/5qsniuzp5/Screenshot_1.png[/IMG]

Any solution please :D :)
[SuperSU] efrainmartinez:
I have flash the last SuperSU beta... It's fine, the only thing is a normal app that never ask me to give permission, now ask me to give permission.... It's the only thing.
[SuperSU] Berong:
[MENTION=631273]Chainfire[/MENTION] ... sir, whenever I will flash supersu SR. turn on my phone... it makes my lockscreen freeze for a couple of seconds. Unlike the supersu which has no SR everything works fine... but suhide needs SR version
[SuperSU] ktmom:
This is the stable thread. The SR releases are beta. You should look for help in the beta thread. But without logs, you'll probably be ignored. Try getting a logcat of the point where the lockscreen is an issue.

"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
[SuperSU] AnkitNawlakha:
In case you are having an issue with the installation of SuperSU, you can refer this guide here.

You might find it helpful.

Cheers.
[SuperSU] Ch3vr0n:
an external site really? There's only 1 guide i'd trust on the official site http://www.supersu.com/

http://www.supersu.com/gettingstarted#APK

http://www.supersu.com/gettingstarted#recovery