yashsingh1/xdaforums huggingface dataset:
[SuperSU] ruchern:
Does any one have Titanium Backup crashing after flashing this variant of SuperSU? Just want to narrow down the cause of it.
[SuperSU] andreoide:
I have taken a look in the logfile but it gives no answer. Posting it here is a no go it is like 3.4mb [emoji36]

Thank you very much so far [emoji106]

Peace [emoji111]
[SuperSU] vandyman:
I have a Nexus5x 5x 7.1.1 stock with Titanium Backup and there no flaws.

I do not have anything else installed like,

Su hide, xposed, magic crap or pogoman.

Sent from my Nexus 5X
[SuperSU] ruchern:
Thanks for confirming. It's probably just my build then.

I, same as you, do not have suhide, xposed nonsense, and pogo.
[SuperSU] grep_i:
You could zip the log file but that it is this big indicates more problems or did you flash more than 50 times before reboot to system.

Anyway your problem is fixed so it is up to you if you want more information or not.
[SuperSU] gothicVI:
Uff do you have any clue where and how to start searching? I actually never encountered a problem with /data and also until sr1 all versions of SuperSU worked without major issues for the past ~2 years. I'm actually quite helpless and clueless at the moment...

Gesendet von meinem Moto G 2014 LTE mit Tapatalk
[SuperSU] vercety974:
You can find the stock kernel in the Google factory image :)
[SuperSU] brb lol:
N4

Works like a charm on my stock N4 5.0 with stock kernel. No broken apps yet. I'll keep testing. Thanks CF!
[SuperSU] drawde40599:
2.27

Flashed with Twrp on stock N6 . no issues after half a day .
[SuperSU] dboechat:
Working fine on my i9505 with unofficial CM12. [emoji106]
[SuperSU] GiGiSSiMo:
Works like a charm on my GNEX4 with lollipop 5.0 and stock kernel flashed just today (previously i was on 2.23 with modified kernel).

Thank you very much CF!
[SuperSU] nightfishing:
Search android factory images and pick the one for your phone. Extract boot.img from the zip.
[SuperSU] raburs:
boot.img is stock kernel?
[SuperSU] Srandista:
Yes, that's correct.
[SuperSU] Nicknoxx:
Because Lux can dim the screen way below 0 and it can be controlled from tasker.
[SuperSU] An Droid:
SuperSU 2.27 worked for me on my nVidia Shield tablet.

Coming from a rooted KK. Bootloader remains locked with CWM recovery (installed via Flashify on rooted KK).

Thanks Chainfire!
[SuperSU] brb lol:
QuickBoot

Quickboot app by Sirius Applications is not working. Not sure if it's their problem but thought I'd mention it.

Nexus 4

All Stock

Stock Kernel

SuperSU 2.27
[SuperSU] shadyshadow:
I flashed the boot.IMG via fastboot lost root which I expected then flashed 2.27 zip with twrp and got error message about partitions. Had to reroot with cfar. Any suggestions?
[SuperSU] lynnux:
2.27 is working on my Nexus 10 after flashing it in TWRP. I originally fastbooted an AOSP version of 5.0, flashed CFAR, then TWRP, then earlier betas of SuperSu, all worked for me.

Thanks for doing this!
[SuperSU] shadyshadow:
Sorry nexus5
[SuperSU] ramjet73:
That's the app's problem.

It needs to be updated to pass the PIE check in Android 5.0 just like ES File Explorer and Flashify have been already.

You can use Power Menu or Power Toggles as an alternative for now since they both work with 5.0.

ramjet73
[SuperSU] mpgrimes:
Quick reboot (root) works fine with it. Devs name phongit I believe
[SuperSU] brees75:
I am having a hell of a time with nexus 10 lollipop and 2.27. It force closes the moment it boots up. I have tried 4 different builds and sequences. Flashed with rom, after rom is set up, with and without custom kernel, wiped cache and then not. CFAR then flash, it just won't work. Whats more aggravating is everything else is perfect. Loving lollipop i just can't do anything involving root. Lol I took root for granted until now. It always worked perfectly until now thanks to Chainfire.
[SuperSU] Mr.Jay:
I have a Nexus 5 with stock Lollipop and ElementalX 2.03 kernel, if I flash SuperSU 2.27 could I have any problems?

Sent from my Nexus 5 ?
[SuperSU] scbash:
Upgraded my wife's Nexus 5 to Lollipop today, and 2.27 appears to be working fine. The first time I started SuperSU it crashed, but starting it again produced no errors. Titanium Backup requested and received super user permissions with no problem.

Thanks for the hard work!

Stephen
[SuperSU] occtec:
I guess this will only work initially with stock kernel, so if I was to flash Franco kernel afterwards I guess this would break root, right?
[SuperSU] grep_i:
You could try and mount /data manually and see what happens if it gives you an error message which you can solve or you could flash your rom again it is quite possible something went wrong the first time.

Reflashing rom helped someone else with a similar issue as yours but I can not guarantee anything.
[SuperSU] corkiejp:
SR1 Failing to flash on some Marshmallow devices!

SR1 Failing to flash on some Marshmallow devices!

[MENTION=631273]Chainfire[/MENTION]

As others have reported on this thread SR1 is failing to flash on Marshmallow Devices.

Mine is Redmi Note 3 running xiaomi.eu 6.12.29.

Here is the fault from recovery log: -

supolicy v2.79 (ndk:arm64-v8a) - Copyright (C) 2014-2016 - Chainfire

Patching policy [/sutmp/sepolicy] --> [/sutmp/sepolicy.patched] ...
(Android M policy compatibility mode)
Segmentation fault
--- Failure, aborting

.

And the full recovery log of trying to flash supersu here: - http://pastebin.com/nLg3MadP

If you flash Stable SU v2.79 first and then flash SR1, even though it fails at the same place. SR1 is successfully working!

Is this a fault with the zip or the version of TWRP?
[SuperSU] danilo_scala:
Xperia Z5 Premium Work Good, thanks for great work
[SuperSU] grep_i:
That's not possible as for than /data was not mounted and no files are installed or removed, most probable is that you are still on 2.79 stable
[SuperSU] corkiejp:
The app reports "SuperSU Pro v2.79-SR1" but is possibly using sepolicy from stable 2.79.
[SuperSU] grep_i:
Maybe it is device or ROM related as I have flashed it on my device today a couple of times without any problem, I'm on Nexus 5 with stock rom.
[SuperSU] mucha.k1994:
I flashed SR1 now on OP3 and have same issues with sepolicy. Stock, clean marshmallow.
[SuperSU] Legitsu:
confirmed issue with the moto x pure fails on sepolicy clean marshmellow stockrom with 2.79SR1

flashing dirty 2.79_stable worked and the device was successfully rooted

see attracted log

http://pastebin.com/KakngXM1
[SuperSU] chrcol:
this is failing to install via TWRP on my samsung s7 G930F

The ramdisk patching sepolicy stage fails.

cf-autoroot via odin works but I dont like using that method as its way less convenient and also requires reinstalling twrp afterwards.
[SuperSU] gothicVI:
I'm slowly coming to the conclusion that it actually might be a general marshmallow problem and not a problem with /data.

Gesendet von meinem Moto G 2014 LTE mit Tapatalk
[SuperSU] Nekromantik:
Hi

Anyone on else have issues with 2.79 SR1 and disabling root?

On SR5 2.78 I could disable root in the supersu app and use my banking application but on 2.79+ this seems to be broken as I still have root after disabling in the app.

Running DU 7.1.1 on Angler.
[SuperSU] marathonjon:
Perhaps you could update the link to the stable releases? https://xdaforums.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703
[SuperSU] corkiejp:
You provided the exact same link by mistake?

Should have pointed to here: -

https://xdaforums.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703

Or search chainfire's post for 2.79 provided by him.
[SuperSU] SoftWord:
Does work on kitkat 4.4.4? SuperSU app continue to tell me that su binary must be updated.......
[SuperSU] ruchern:
Just update it. I did that as well and it worked fine.
[SuperSU] SoftWord:
Non hai capito un cazzo cmq.... Lo aggiorno ma continua a dirmi che è da aggiornare.... Bah
[SuperSU] ruchern:
Sorry I do not understand you.
[SuperSU] drewski_1:
have you tried to flash the zip or just through the SuperSU app?
[SuperSU] theoverseer:
With SR1 I'm unable to run shell commands via Tasker. Had this confirmed with another user on Reddit.
[SuperSU] adrman:
Instead of using the "use root" checkbox in Tasker, make "su" the first line of your command. I forgot I had my shell commands in Tasker set up that way after experiencing something similar with phhusson's superuser. They're all working with 2.79SR1.
[SuperSU] pkelly517:
I think that's why XDA requires posts in English.

Oops. I know that's why.

I got the 'Bah', though. That's universal!
[SuperSU] smitharro:
It's Italian. This is what he said:

understand a **** cmq .... The update but keeps telling me to upgrade .... Bah

Thanks to Google Translate (he should have used it himself!).

Send from my XT1642, with dualboot LineageOS, using Tapatalk
[SuperSU] ktmom:
Swearing, even in Italian, is not permitted.

As to the fact that the app keeps requiring an update, do what was previously suggested, flash the zip itself in recovery.

Giuramento, anche in italiano, non è consentito.

Quanto al fatto che l'applicazione continua a richiedere un aggiornamento, fare ciò che è stato suggerito in precedenza, il flash della stessa cerniera nel recupero.
[SuperSU] svnhvn:
Sexy indeed Italian language was.
[SuperSU] fmc000:
[OT] Guys, a small suggestion: don't ever use the Google translator with Italian as the target language. For example, "to swear" in Italian can be translated with both "giurare" or "imprecare" and the translator picked the wrong one here. Moreover "il flash della stessa cerniera nel recupero" just doesn't mean anything in Italian. That said, the use of a different language just to hide some unacceptable words is despicable. [/OT]
[SuperSU] Breathewave:
Is there any LineageOS version available or even planned?
[SuperSU] Legitsu:
why would there need to be a " LineageOS" version

supersu works on any android build period always has always will never mind that LineageOS is just cyanogen rebranded or that LineageOS doesn't even have builds rolling yet
[SuperSU] Breathewave:
I'm using this one here: https://xdaforums.com/showpost.php?p=70348722&postcount=121

Latest stable or beta version of SuperSU does not work on TWRP recovery (zip file).
[SuperSU] zelendel:
This is not the case. CM uses a completely different SU setup. For many years they even used a different app. Some Android distributions need a modified SU to work. This is due to coding differences. And how root permissions are handled.

This is just one of the choices they will have to make as they bring up their code. CM used to not use this SU due to it being closed sourced. They may stick with that and work on what is already there.
[SuperSU] Manok98:
Hey,

I have a problem with SR SuperSu: I want to install SuperSu in SYSTEMLESS-mode, but after I writed echo "SYSTEMLESS=true" >/data/.supersu , and I installed SR SuperSu, the installation of Boot image Patcher doesn't work. I will flash also suhide (v. 0.55), but when I reboot system, no root!!

See the screenshot for more info.

Thanks in advance
[SuperSU] jcmm11:
What device, what ROM, what kernel? I suspect you have a custom kernel installed, in which case reinstall the default kernel, apply SuperSU, then reapply custom kernel.

Also you shouldn't need to force systemless mode, that should be default. If it's not then your device may not support systemless.
[SuperSU] Manok98:
I have a Galaxy S2 (I9100), running Cm13 with Lanchon IsoRec custom Kernel (I've installed this Kernel for the TwRp recovery).
[SuperSU] fubo73:
SuperSU does not work on s2 cm13. Use embedded superuser instead.
[SuperSU] Manok98:
OK thanks!:good:
[SuperSU] Chainfire:
For future Google search results:

"E/ActivityManager(xxxxx): Sending non-protected broadcast eu.chainfire.supersu.NativeAccess from system uid 0 pkg null"

Notes:

- This is incorrectly marked as an E/Error instead of a W/Warning. This is logged only, code is not being aborted.

- This is caused by the su binary's communication with the GUI.

- The logged error implies this communication is not protected, but it it is.

- AOSP code has been updated in 7.1 to detect the specific protection used by SuperSU, and this message is no longer logged.

Conclusion:

- No fix is required in SuperSU: code flow is not affected, and new Android versions will no longer log this message.
[SuperSU] Chainfire:
v2.79 SR2

v2.79 SR2 is out - https://plus.google.com/+Chainfire/posts/fHE1BFEaEKS
[SuperSU] corkiejp:
Thanks chainfire for latest release and hopefully fixed flashing on Marshmallow.

Just used SR1 to root my Nexus 9 on January Image, there doesn't seem to be much changes in the update to require reflashing with SR2. Might do it anyway.

Will also test SR2 on my RN3 (Kenzo) Xiaomie.eu 6.12.29.

Edit: - Successfully flashed on both devices without problems. Marshmallow bug fixed!
[SuperSU] Cares:
Just flashed Jan security patch on Pixel without issue. I know SR2 did not change the Pixel but thought I would report in.
[SuperSU] danieldmm:
Any fix for SuperSU binnaries keeping disapearing on F2FS data partitions ? ( case of OP3T )

Are you aware [MENTION=631273]Chainfire[/MENTION] ?
[SuperSU] thomasswan5547:
stupid question but do you have to still have to echo the "systemless command" within twrp to flash these zips systemless-ly? or are they installed systemless by default? Thanks
[SuperSU] andreoide:
SM-G901F Samsung S5 plus kccat6

Flashed with TWRP from v279 SR1 to SR2 without any problems & working.

Cheers for Chainfire [emoji106]
[SuperSU] andrew2432:
Hey team where is the pass safety net since November security patch being discussed? I don't need directions on what to do, just a push to the correct forums!!
[SuperSU] hamstrman:
Ugh please help.

"The SU binary needs to be updated. Continue?" "Continue"...

"Samsung KNOX has been detected. This might limit root capabilities and cause annoying popups. Try to disable KNOX?" "OK"

Instant: "Failed to disable KNOX."

This hasn't been an issue for me since KNOX first existed. I have SM-G920P with Android 6.0.1 October security patch level What am I doing wrong? Ready to tear my hair out.
[SuperSU] Mesmurized:
Flashed SR2 over SR1, Nexus 5X; 7.1.1 PN. Perfect! :good:
[SuperSU] MgouravR:
OnePlus 2 in OxygenOS 3.5.6

Please tell me, can I use latest version in my OnePlus 2 which is working on oxygenos 3.5.6?

Is it working?

Thanks!
[SuperSU] eris23:
Problem continues as with https://xdaforums.com/showpost.php?p=70219469&postcount=8503 on TugaPower N 12.1 on OnePlus One with SR2-SuperSU-v2.79-SR2-20170103215521.zip
[SuperSU] tag68:
The default depends on device/OS/other things. It is not always the same.

There exist devices eg Motorola Marshmallow where the current default is system, default is not working, and you need this line to enforce systemless. On others it is fine. Usually SuperSU tries to do best guess which root method is appropriate. If you want to enforce systemless, you need this line. My question if the default for Motorola Marshmallow can get changed never got an answer:
[SuperSU] norbusan:
boot loop on angler/7.1.1 with 2..79-SR2

Hi,

I just tried it two times, both with the same outcome:

flash original firmware (system, boot, vendor, ...)

install twrp (3.0.3)

flash supersu 2.79-SR2

go into boot loop

This is on a Nexus 6p, 2017/1 security update 7.1.1

Thanks for any suggestion
[SuperSU] 123SIT:
SR2 no longer boot loops on 6.0.1 emotion as previously reported with SR1, well done sir.
[SuperSU] skyhirules:
Still boot loop on my Z1 Compact with stock Android 5.1.1. The worst thing is that after flashing 2.79, I have to wait for the dalvik to be rebuilt again.:p
[SuperSU] kimikim0:
just use the stable supersu v2.79
[SuperSU] Harrison Le:
Great, work well on custom rom Lineages OS 7.1.1
[SuperSU] ViTAMiNCHEG:
Works great on CM13 with December security patch
[SuperSU] Chainfire:
/tmp/recovery.log from twrp ?
[SuperSU] Chainfire:
I've seen it mentioned, yes, but I have no OP3T to test and my test devices running F2FS do not seem to be affected.

/tmp/recovery.log from TWRP directly after flash, logcat and dmesg from Android boot may help.

Does the OP3T come with F2FS by default?
[SuperSU] Chainfire:
Did you flash through TWRP or FlashFire, or did you just install the APK ?
[SuperSU] Chainfire:
Is RootSwitch freezing the only issue, or does root not work? RootSwitch may need an update to handle the new SELinux rules. Either way I can't test as I don't have an OPO.

Which Android version is that?
[SuperSU] Chainfire:
I need the (original, stock) boot image from one of these affected devices so I can fix it.

(The problem does not occur on any of the Motorola devices/firmwares I have here)
[SuperSU] :
[MENTION=631273]Chainfire[/MENTION] if u got questions about Huawei devices running nougat there's no need to investigate that issue. There's no loop support on the beta version and doesn't seem to be on stable version either (reports from Huawei mate 9 pro user) so there's nothing to be done except use phh with your su binaries or modify the boot image itself. Either way we can't mount su.img so that issue is no need to look at.

Regards
[SuperSU] danieldmm:
Some times after flash it boots fine and you have root, after few seconds supersu app complain binaries missing, some times, even after re-flash supersu zip, it boots straight without binaries missing. Will try to catch the recovery.log and attach here. And yes, OP3T it's shipped with data in f2fs by stock, only data is. System and cache its ext4.

It's me also that build that rom, it's based on LineageOS ( CM14.1), android 7.1.1, deactivating root on root switch it freezes all the system, sometimes it will soft reboot.

Enviado do meu ONEPLUS A3003 atrav�s de Tapatalk
[SuperSU] skyhirules:
Unfortunately there's no log file there. Maybe it has to do with the xzdualrecovery I'm using.
[SuperSU] buttie:
[MENTION=631273]Chainfire[/MENTION], just fyi: this bug is still present in SR2:
[SuperSU] vasileios26:
Hey my friends and thank you very much for that answer. flashed on my mobile to version 2.79 SR2. my phone doesn't bootloop, is okay. root also works perfectly (for example Adaway, link2sd etc). I have lenovo z90-7 at version 6.0.1, with unlock bootloader (i have flashed twrp), and stock bootloader (for its unlock). my problem, is that they have upgraded the su binary said: "installation failed! Please reboot and try again, the su binary needs to be updated" . I can't! unfortunately I do not have time to read 866 pages because I am a student and writing tests. Please help me.
[SuperSU] Portgas D. Ace:
Try flashing the latest SuperSU.zip file through recovery, this should update SuperSU and also the binaries.
[SuperSU] mielletseed:
I suppose that was no beg for help but just a report of the boot loop as requested by chainfire ...
[SuperSU] vasileios26:
Thank you very much for your answer my friend. I have flash the version 2.79 SR2 via TWRP. When you said "via recovery", you mean the same with me? (TWRP)? Correct?

The latest version, is the 2.79 SR2 , correct? Thank you very much again.
[SuperSU] Portgas D. Ace:
Yes for both :good:
[SuperSU] danieldmm:
Your problem it's not SuperSU mate, it's because you have November security patch, it have that behaviour over suhide, if you are running custom rom ask your developer to give support to Suhide

Enviado do meu ONEPLUS A3003 através de Tapatalk
[SuperSU] skyhirules:
Sorry, my mistake. Here's the log. I'm not sure if you can get something out of it. I hope so.
[SuperSU] andreoide:
Huh... Is it just me or do more pple expirience faster boot up time since SR2 ?

I mean every boot when having flashed SR2 and all is working okay. The normal everyday boot.

I think here it's like 10 sec faster wich does not seem a lot but it's noticeable.
[SuperSU] warriorvibhu:
you joking .. ?? 10 sec is probably 30-50% improvement .. All my phone takes is 30 second to boot .. so a 10 second improvement would mean boot time improvement of 33.33% that is huge... I dont see any such improvements..
[SuperSU] Chainfire:
I've followed the exact same procedure (including wipe) with the same firmware and the same device and it works fine for me.
[SuperSU] andreoide:
No joke. Im as suprised as you r.

BUT maybe I have other phone like yours, did you think of that?

I have SM-G901F Samsung s5 plus kccat6, stock, xposed, bloatware&knox frozen with titanium backup and last but not least (!!) Rooted with Chainfire's (?) SR2 now.

With SR1 booted like 1 min and 10-15 sec

With SR2 it boots in 1 minute

View attachment 3990371

Picture taken from stopwatch other phone [emoji6]

Peace [emoji111]
[SuperSU] Chainfire:
This is useless. You need to grab /tmp/recovery.log immediately after flashing the SuperSU ZIP, without rebooting. And you need to paste it to pastebin.com or whatever.
[SuperSU] Hecke92:
Got a bootloop too, previous Version working fine (op3):

http://pastebin.com/FnSJ8Kws
[SuperSU] andrew2432:
Hey where is the thread to update that to work manually?!?! I can't find it yet but I've heard there are fixes out to suhide post November patch
[SuperSU] Chainfire:
Seems to be installing in system mode.

Try forcing systemless using:

echo "SYSTEMLESS=true">/data/.supersu
[SuperSU] yung40oz84:
any chance this version will work on f2fs, or is that just not happening, I am not a huge PHH superuser fan as I have used superSU for ages, but I want to run f2fs as well.
[SuperSU] ZRK_NanDRD:
Flashed SR2 on S3 & S5 running Resurrection Remix 7.1.1 (5.8.0) all went fine.

Thanks as always for your great work Chainfire
[SuperSU] Chainfire:
I can't fix this as long as I can't reproduce the issue, and I don't have an OP3(T)

I have absolutely no idea why it's not working at this point. F2FS has worked on devices in the past with SuperSU, not sure what makes the difference this time.

Try rebooting into recovery during the 3rd or 4th loop, then pulling /proc/last_msg and/or /sys/fs/pstore/console-ramoops, those may provide some clues.
[SuperSU] Hecke92:
Sorry to sound stupid, but where and when do i have to enter this?

But I got it to work now by installing the previous version first and installing this new one after that. Are there any disadvantages by doing so?

Thank you so much :)
[SuperSU] gothicVI:
In TWRP go to advanced, then terminal and type it there.

Flash after doing so.

Gesendet von meinem Moto G 2014 LTE mit Tapatalk
[SuperSU] Hecke92:
Thank you, it worked!
[SuperSU] skyhirules:
OK. That's easy. There you are:

http://pastebin.com/0ZwWpe7i :)
[SuperSU] yung40oz84:
it does not boot loop, it boots fine, but root just disappears or stops working or reboot or a little after boot. Should I still grab those same logs, I will get em.
[SuperSU] Chainfire:
Also installing in system mode for some reason. See https://xdaforums.com/showpost.php?p=70391652&postcount=8680

Please post stock/original boot.img .

Ah yes, I am confusing reports. I'm not really sure what can even cause this.

In this case I guess logcat and dmesg logs are appropriate.
[SuperSU] Hecke92:
Mine is attached
[SuperSU] jt1998:
Flashed SR2 2.79 over last release with no issues. On Nexus 6p with Pure Nexus ROM and elementalX kernel.
[SuperSU] Elanza_48:
On SR1 It is not able to uninstall and restore the stock boot image will, saying "uninstall failed !!" But will it effect it the stock image is not restored and the SR2 is flashed ?

Running on cm 14.1
[SuperSU] yung40oz84:
OK, so approx. a minute or two after granting some root privileges and messing around after boot, I went back into superSU app and said no superSU binary, root lost all sudden. Here is two logs. thanks a bunch!

https://drive.google.com/file/d/0Bw-ARc6DtAVJM3JZRC1CeDBzUEU/view?usp=sharing
[SuperSU] littleshiro:
Flashed SR2 2.79 over nightly CM 14.1 20161225 with no issues. On Moto G 2015.
[SuperSU] skyhirules:
But isn't it supposed to install in system mode? All previous versions up to 2.79 were doing so with no issues. I'm using Android 5.1.1 and I actually don't want systemless root.
[SuperSU] Chainfire:
Right you are. I'm not sure where my head is at today.
[SuperSU] skyhirules:
That's normal mate. Being bombed with all those posts, logs etc. I'd have gone nuts! :silly:

I hope you can resolve the issues. Take care. ;)
[SuperSU] Dor71:
Works with no issues, Nexus 6p, stock 7.1.1, january update, elemental kernel.Thank you :)