yashsingh1/xdaforums huggingface dataset:
[SuperSU] ithehappy:
I flashed this version from TWRP RC1, just the TWRP interface from ADB/fastboot, no TWRP zip was flashed to actually install TWRP if this has got to do anything with what I am asking, I am on stock recovery still, on the latest (January) security patch for the Pixel XL and after the first boot there was no WiFi connection. I rebooted the phone and everything was fine. Wonder what happened. Problem wasn't there when I flashed the SR1 in same method.
[SuperSU] norbusan:
Thanks, it turned out that I had to first cleanup by flashing magisk-uninstaller, cleanupsu, and suhide-rm, after that installation of 2.79-RC2 succeeded.

(besides that installation of suhide kickstarts the same boot animation hang, but I post this in a different threat)

Thanks a lot
[SuperSU] tag68:
[MENTION=631273]Chainfire[/MENTION]: As I have not enough time I asked another user to do a current test. Here is the result:

Hope that is enough.

That is strange. The issue occurred for sure on the Moto G2 XT1068 which I think you have, like on Moto X Play and AFAIK on all Moto E/G/X versions with Lollipop and Marshmallow. But to be sure I would need to repeat the test I did with some older 2.7x SuperSU. I'd do that if the above does not help fixing that Moto-system-problem, but I couldn't tell a time frame for that.
[SuperSU] knpk13:
This happened to me last I tried 2.78 SR5 on a Moto G 3rd gen stock ROM marshmallow. I too have had various people tell me it's an issue with all Moto stock ROMs.
[SuperSU] theoverseer:
Tried that, still can't get shell commands to work. They work in that format on 2.79, but not in the SR releases.

[MENTION=631273]Chainfire[/MENTION] can you shed any light on this?
[SuperSU] jackyaway:
Thank you. SR2 works fine on CM13 with f2fs data and cache partitions (oneplus 3), no more sepolicy error.

Inviato dal mio OnePlus 3 utilizzando Tapatalk
[SuperSU] :
Same issue. Normal SuperSU loses root after a while. System-mode superSU gets stuck at boot animation.

This issue is not on official oxygen os roms, only on CM based ones. I have F2FS data.
[SuperSU] mobile_sensei:
Still the best
[SuperSU] Ch3vr0n:
[MENTION=631273]Chainfire[/MENTION] I noticed something "off" when upgrading from SR1 to SR2 2.79. I opted NOT to restore stock boot image and recovery, as afaik that is not needed when doing a simple SU update. However the flashing text indicated stock backup WAS RESTORED anyway. Is this a bug or normal?
[SuperSU] grep_i:
It's normal this happened always, it's just the first time you noticed it.
[SuperSU] ive.heyah:
Please, address my enquiry, the issue in question is about no pop up windows popping up, so the SuperSU must work with the option "granted" unless an user manually writes down chosen apps root permission into the SuperSU configuration file (so did I)

You usually discuss here about higher operation systems than lollipop, however for my MediaPad-T1 there is just stock KittyKat available AFAIK (please give me a hint if you know anything new about it)

Huawei MediaPad T1, KittyKat (stock), EMUI, ROOT, Xposed
[SuperSU] hamstrman:
Flashed with TWRP. I did not just install the APK. I was following a method with a Root Switch patch.

Put custom_ramdisk_patch.sh in /data.

Put dot.supersu into /data/.supersu

Rename dot.supersu to .supersu.

chmod755 files.

Flash newest version of SuperSU v2.79 SR2.

Reboot, install Root Switch, etc, etc.

After reboot, SuperSU requires I update binary. Can't because of KNOX. And here I am. I'm back on stock now. Happy to try it again if there's something I can do differently! And I apologize if I'm doing something stupid.

Edit: Oh and I'm trying to HIDE my root, obviously. This method was suggested to me.
[SuperSU] Constrabus:
FYI: Working on the Xiaomi Mi Mix with xiaomi.eu ROM 6.12.29_v8-6.0 Marshmallow

But! adb sideload via TWRP will not work.

You must copy zip and flash.

I've noticed this with 7.29-SR2 and 7.28-SR5
[SuperSU] jurassic512:
I'm using the Resurrection Remix 6.0.1 ROM for my Note 2 (t0lte), and I'm having problems I can't fix in regards to updating SuperSU binary, but I notice Android UI popups asking me to give root permission to my apps that require root when I open them. I found the approved apps in "Developer Options" under "Manage root Accesses".

Every time I tried to flash SuperSU (2.97 SR2, settled on 2.97 from Google Play) or SuperSU updates via recovery (TWRP v3.0.2.0), I get stuck on the Resurrection Remix boot logo and have to restore my RR backup without SuperSU installed. I'm don't want to risk bricking my phone using ADB or anything related to connecting my phone to my PC or using a CLI. Yes, I am that lazy. I just want root and my phone working as it has on past ROMs which was mainly stock 4.4.2- ew.

My questions are:

*Do I NEED to update binary, or have SuperSU installed at all to manage root access, since the ROM seems to be handling it?

*Will a future Google Play SuperSU update the binary?

Thanks, and I hope I posted this in the right thread since it does pertain to installing 2.97 SR2.
[SuperSU] bdwilk:
What you're seeing is the built in CM root manager. If all you want is root then you have it by default in RR ROM.
[SuperSU] jurassic512:
I am rooted. Always was, but you need a root access manager like SuperSU to be able to run apps that only run on rooted devices.

Why would the developer(s) program a spot for SuperSU in the settings after it's installed, rather just leave it in the app drawer with every other app, if the ROM itself can do it, based on the Android UI popups I've been seeing when running them? It's the option in Developers Options that is where you can see what apps the OS gave access to.

http://imgur.com/a/8BuBX
[SuperSU] bdwilk:
I'm a firm believer in SuperSU so I know the reasons behind using it. I also use it on my CM based ROMs. You said you just wanted root, that's why I said what I did in my last reply. Anyways privacy guard has nothing to do with SuperSU, that's CM's root manager.

I had your problem in the past. What I did was flash an older version of SuperSU (2.76) and then when I get the notification to update it from the playstore I would update. Then the binaries would ask to update and it always worked. Maybe try that.
[SuperSU] jurassic512:
Well I'd have to be rooted to flash a custom ROM right? :)

Doesn't CM root manager do the same thing SuperSU does? It acts and somewhat looks the same. That is what I need. A root manager. An app to give apps root access.

I tried flashing an older version of SuperSU, but everytime I do it and reboot, I get stuck on the RR boot animation. Factory reset wasn't fixing it either. I'll make a backup and try 2.76 specifically (i only went as far back as 2.78) and see if it works. If it does I'll be back to thank you again.

Thanks for trying to help me. XDA community is the best.
[SuperSU] egingell:
No. Just a recovery that's not stock.

Sent from: LG G4 MM 6.0 / SGS5 MM 6.0.1
[SuperSU] ulxerker:
and thus an opened bootloader.
[SuperSU] Ch3vr0n:
You don't even need that. You can adb BOOT into a custom recovery too.

Sent from my Nexus 7 (2013) with Tapatalk
[SuperSU] egingell:
I think that qualifies as not stock.

Sent from: LG G4 MM 6.0 / SGS5 MM 6.0.1
[SuperSU] yash92duster:
Sr2 works great on Galaxy s5 g900h in all custom and stock roms

No bootloops

Thanks a lot :):victory: chainfire
[SuperSU] jurassic512:
Does anyone know how to flash SuperSU (i'm using TWRP v3.0.2.0) without getting stuck on RR boot animation? If i install via apk, it won't update my binaries. Root Checker says I'm rooted.
[SuperSU] Ch3vr0n:
No it doest, you specifically stated he needed a custom recovery for non stock. Booting one keeps recovery at stock, the only non stock thing then before root access is unlocked bootloader.

Sent from my Nexus 6P with Tapatalk.
[SuperSU] bdwilk:
Did you try to flash 2.76?

https://download.chainfire.eu/969/SuperSU/
[SuperSU] egingell:
It's not installed to the phone, true, but it's still getting used. Are we really going to split hairs over verbiage?

Sent from: LG G4 MM 6.0 / SGS5 MM 6.0.1
[SuperSU] jurassic512:
Yes I did. I even let it sit at the boot animation for over 20mins before restoring my backup. I'm just going to use the root manager in RR until it finds an app it won't grant access. After that I don't know what I'm gonna do. I really like Marshmallow. I've flashed and reflashed with full wipes, dalvik cache wipes, formats and system wipes. I don't have the patience I did when I was flashing my previous devices.

Thanks for your help man. Appreciate it.
[SuperSU] bdwilk:
Sorry dude. I'm out then. That always worked for me. Time for you to move to Nougat. Haha.
[SuperSU] jurassic512:
I tried it, but had the wrong version (N7100). It installed, but would not detect my SIM card. I have the Canadian version and haven't been able to find another Nougat ROM for my phone, and CM 13 nightly causes callers to hear their own voice even with different modems. Either I don't know what I'm doing, or I have the worst luck!
[SuperSU] bdwilk:
Nope sorry. Keep looking. You're bound to find something. :svetius:
[SuperSU] Chainfire:
You should try SuperSU without RootSwitch. It's very possible something RootSwitch does is interfering.
[SuperSU] Vishal Vignesh:
Sir since I see you online I am asking

..

Supersu is fully compact able with lineage right...

It was always compact able for my device since it was running cm 11-12-13-14
[SuperSU] dratsablive:
I am going to guess that suhide is in there somewhere.
[SuperSU] Displax:
[MENTION=631273]Chainfire[/MENTION]

Hi,

SuperSU 2.79-SR2 (SR1 too) does not work on my Nexus 7 (2012) running stock Android 4.4.4.

I flash it in TWRP and it look like "ok", but after rebooting SuperSU say that I need update binary file and his update ("Normal & TWRP) failed.

Stable 2.79 work fine.

I attach logs.
[SuperSU] corkiejp:
Can't Flash SuperSU on xiaomi.eu 7.1.5 RN3 "Kenzo"

Can't Flash SuperSU on xiaomi.eu 7.1.5 RN3 "Kenzo"

Posting this here, although I don't believe supersu is to blame because i tried a few versions.

Getting the following error in recovery.

- Flashing boot image
dd: writing '/dev/block/mmcblk0p21': [B]No space left on device[/B]
16385+0 records in
16384+0 records out
67108864 bytes (64.0MB) copied, 0.281215 seconds, 227.6MB/s

.

Full log here: - http://pastebin.com/Encatgqm

Although it completes the flash, the device hangs on the boot animation.

Note: - Even though the log has suhide flashing, also tried with that removed.

I am attaching the boot image from the rom, if anyone can throw light on the problem
[SuperSU] Marnes:
Installing supersu via twrp on my moto g4 (europe) softbricked it on boot. Couldn't get past the logo at all.

Simply installing this the same way fixed it instantly with no sign of leftover damage. I didn't think fixing it would be as easy as just deleting the right files, but it is.

Thanks man, saved me
[SuperSU] andrew2432:
Did you remove your native root prior to flashing super su?? If so I suck and didn't go back a few pages
[SuperSU] Alxoom33:
SuSuperuser v. 279 SR2 bootlooping on Google's January 5 Nexus 6 update 7.1.1. it was working great on Android 7.0.
[SuperSU] jtwebfusion:
I'm not having any BL issues. Did you install the factory image? That's what I did and it's working great.
[SuperSU] Alxoom33:
I sideloaded the OTA. Having Bootloop issues with SR2 and with EX kernel.
[SuperSU] jtwebfusion:
I've had nothing but problems with OTA's in the past. That's why I installed the FI. Both SR2 and EX 4.16 are working great for me. Just bite the bullet and install the FI.
[SuperSU] Alxoom33:
I tried that first, System wouldn't install for some reason. I think WUG needs to be updated. So I sideloaded the OTA from the Google site, also using WUG. Used no-wipe option for both tries. Sideload worked great, but I am having the BL issues loading SuSu 279 SR2 and EX kernel 4.16. Not sure why?
[SuperSU] beast.in.black:
SuperSU Stable 2.79 as well as SR2-2.79 both cause hangs/bootloops on a Huawei Mediapad M2-802L running the stock Android 6.0 ROM mentioned in this thread.

EDIT: Adb logcat output attached - this was after installing SuperSU Stable 2.78.

Let me know how else I can help with this.
[SuperSU] bdwilk:
With all these negative posts I just want to confirm (2 devices) 2.79 SR2 runs great on OnePlus One running AICP 7.1.1 with Jan 5 security patch.
[SuperSU] :
Can confirm it runs very good on my Galaxy s7 flat with Superstock 2.3 (latest nougat beta) and on my Galaxy s4 with cm13
[SuperSU] ViTAMiNCHEG:
Latest SR2 working good on CM 13.1 TS 20161231 Xiaomi Mi 4s
[SuperSU] jtwebfusion:
In order to load the FI, you have to have the latest version of ADB and fastboot.
[SuperSU] danieldmm:
[MENTION=631273]Chainfire[/MENTION] , about the problem of loosing root, maybe this can help to fix the issue we are facing of losing binnaries.

Quoting [MENTION=4470081]topjohnwu[/MENTION]
[SuperSU] jdegreef:
Too fast, too slow, isn't that device dependent ?
[SuperSU] Spartan117H3:
[MENTION=631273]Chainfire[/MENTION], is there any easy way to switch between systemless and regular root? I want systemless root but Substratum theme engine doesn't play nicely with it, so I planned on switching to regular root only to update my themes, then go back to systemless. What would be the simplest process of switching between the two?

Edit: I also want to maintain suhide when systemless root is enabled, I assume I'd have to flash that after no matter what?
[SuperSU] grep_i:
Shall we get back on topic again in the suhide thread we are talking about suhide related issues and not Magisk, thanks please.
[SuperSU] danieldmm:
What are you saying ? Read and only then reply if you have more information to add to the problem itself. Betewen, if you want to talk of suhide you are not on the appropriated thread, this is SuperSU thread, there is a thread for that. Quoting other posts from other threads to try to fix a problem, its tottaly admissible, if you read my post you will notice that its discussing a issue about SuperSU and not Magisk, suhide.

Previous answer of [MENTION=631273]Chainfire[/MENTION] , he are aware but cannot reproduce/fix because he does not have a OP3/OP3T to test.

Talking of SuperSU loosing the binaries on OP3 / OP3T because of having data on F2FS by stock, if data its on ext4 this will not happen. When SuperSU looses the binnaries, a reboot temporary give back the SuperSU binnaries, but then it looses again. Since Magisk went to something a little similar to this behaviour, its why the quoted part of Magisk thread.

Peace
[SuperSU] tatsuyuki:
I have been experiencing bootloop on Chinese device 360 N4S after a firmware update. The kernel seems to be loaded, but something should be wrong with init (boot logo is shown, but not boot animation). Xposed worked fine anyway. Below is the kernel TWRP dump attached for reference.

http://cloud.tapatalk.com/s/5872454a063f5/boot.zip
[SuperSU] Chainfire:
Are you actually running Magisk? Because if you aren't, it's definitely not related, and if you are, I suggest testing without :)
[SuperSU] grep_i:
:o:confused::silly:

You are right I posted the word suhide instead of SuperSU my mistake.

Yes I have read and do not think it adds something to mention a problem with a completely different package.

You may think it is a little similar problem but lack to come up with proof.

You are just quoting a whole piece of text and say that it is a little similar problem but why post it then if it is only a little similar.

This kind of posting or thinking clutters the post with unsubstantiated claims.

Can you prove anything you said with log files that will work a lot better.

Peace back.
[SuperSU] Chahk:
Encrypted Nexus 6 upgraded from rooted 7.0 to 7.1.1 N6F26Q via fastboot (bootloader, radio, recovery, boot, cache, system) gets into a boot loop when I boot TWRP 3.0.3-0 and flash SuperSU v2.79 SR2.

I have "Require PIN on start-up" enabled. Could that be interfering with the rooting process? Does it matter if I flash TWRP or simply boot into it? What logs can I provide?
[SuperSU] Strephon Alkhalikoi:
Pin on startup definitely could have something to do with it as I don't use a pin and my Nexus 6 has no problems with SR2. No, it doesn't matter whether you install TWRP or run it.
[SuperSU] divineBliss:
If I have a rooted 6.0.1 Android in hand, what is the easiest reliable way to determine if the SuperSU installation is systemless or not? Could not find the answer googling or search ...... TIA :)

EDIT: I think the answer is if I have /su/bin/su , then it's systemless. Appreciate confirmation or other correct ways - thanks.
[SuperSU] ashyx:
How so? A device is either quick or slow and all processes will run relative to that.
[SuperSU] jcmm11:
That's the exact thing I was about to suggest. Yes you are correct.
[SuperSU] Pkt_Lnt:
Look in the app under "move to system". If it states "not possible in systemless mode", you are systemless.
[SuperSU] divineBliss:
systemless confirmation

Thanks! :highfive:

Doubly confirmed systemless! :)

I missed the SuperSU-Settings System section. It says under "Install SuperSU into /system" ......... "Not (currently) available in system-less mode" . (easiest way)

and 2nd way is /su/bin/su exists
[SuperSU] Alxoom33:
I had some issue. Bootlooped with Su and when flashing a custom kernel. If you were using Magisk, you may have some remnants that are causing issue for you. Solution is a clean flash. Or flash [MENTION=4830253]Danvdh[/MENTION]'s stock ROM.
[SuperSU] belek1979:
Does 2.79 sr2 patch boot to stay unencrypted?
[SuperSU] skooter32:
Hey chainfire a know u is a busy guy but my device is a moto g4 and we don't have root on 7.0 for some Variants the rkkt method used right now don't root my g4 a have tried pretty much everything and was just wondering if and when you have time could you please look into this issue thanks for taking the time to read this peace ?
[SuperSU] rcolitz:
I flashed the SuperSU v2.79 SR2 to both my phone and Tablet. My phone is a Samsung Galaxy On5 and it works great however my tablet is a Samsung Galaxy Tab 4 (SM-T230NU) and it is saying that binary needs to be updated and it has the # at the top of the screen. When I allow to try and update that it doesn't work and says that I should reboot, it also tried updating through TWRP and it was not successful. I can still grant super user permissions but I can't change anything in the app because of the binary update. I will be glad to try anything else that you can think of.
[SuperSU] wreid23:
Thanks for the Nougat Fixes came in clutch and now I get my Viper Audio great work man :good::good::good:
[SuperSU] tatsuyuki:
[MENTION=631273]Chainfire[/MENTION], here is a sepolicy which SuperSU gets into bootloop.

I don't know what the manufacturer guys are doing, but this appeared after an update. I'm manually modifying the ramdisk to revert to the old sepolicy for the meanwhile.
[SuperSU] jdegreef:
That's exactly what I meant :D
[SuperSU] danieldmm:
No [MENTION=631273]Chainfire[/MENTION], not using and never used Magisk, only mentioned because the problem it's a little the same like SuperSU it's having, it loose binaries, reboot and all good again, then loose again, then even reboot finish to have no binaries at all, and flashing supersu again its the same result, it boots straight complaining missing binaries.

Enviado do meu ONEPLUS A3003 através de Tapatalk
[SuperSU] Nezorflame:
Hey guys, having a little but annoying problem here, maybe someone could help with it...

Using OP3 with latest LineageOS-based AICP ROM.

I've installed latest beta (reproduced this on Stable 2.79 too), and I'm unable to set the PIN code: after confirmation dialogue it just stays at [ No PIN code configured] even though I definitely entered it right.

This is not the case with the official and community ROMs of Oneplus, so it seems specific to LineageOS derivatives.

Maybe there's any info I could get to you which could help identify the problem?

Edit: also after some time root access is lost, reboot fixes it but only until the next try to set PIN code.
[SuperSU] nanodan:
Are you using F2FS?

SuperSU has issues with F2FS. Not sure when it'll get fixed.
[SuperSU] Nezorflame:
Thanks for the info!

Yeah, I use it on every partition. Should I move only /system back to ext4 or /cache and /data too?
[SuperSU] nanodan:
Unfortunately you need to have everything as EXT4 for SuperSU to work correctly. I too would love to use F2FS but having a functioning SuperSU is more important imo.

I do believe the built in root works with F2FS but I'm unsure. Not that that helps you at all haha

Also I didn't even know system as F2FS was supported yet. That's pretty nice.
[SuperSU] chipiko:
Root Htc Desire 610

Hi guys, I have a Htc Desire 610, have unlocked bootloader, I installed TWRP and automatically installed and SuperSu. The phone is not root, update the SuperSu I did, I wanted to uninstall the application. Help me!
[SuperSU] yung40oz84:
OK, so I am back on f2fs and running a custom ROM, Dirty Unicorns on my OP3. Now, we have already came to the conclusion that superSU does not keep root on f2fs running a custom ROM, but does on stock I guess. SO, when I get some time I am going to be willing to provide anything the developer needs in order to get this issue ironed out. Would [MENTION=631273]Chainfire[/MENTION] please let me know exactly what u need in order to investigate. I did already provide two logs on post 8693 for you to investigate. if you need anything more or another round please let me know. I would really love to see superSU working on f2fs for custom ROMs as it is my go to rooting method for years back and years to come. Thanks!
[SuperSU] chipiko:
My English is not very good in terms of what you wrote (f2fs, OP3) being? You will not mind, but trying to learn Android. What more details? A link or tutorial? Thank you!
[SuperSU] -Deco-:
Either search for ADB uninstall commands or do a data wipe.
[SuperSU] BlackHoleSlam:
Chainfire the website is down. I can't access the new superuser.
[SuperSU] fiffan86:
I'm glad im not the only one with that issue
[SuperSU] paranull:
here is a mirror :

http://ul.to/gpxltpse
[SuperSU] The_Virus:
I'm on stock OOS 4.0 with F2FS /data partion and working root (2.79 SR1).

So what problems does SuperSU have with F2FS? Because for me it's working fine, didn't notice any problems.
[SuperSU] nanodan:
Seems to be an issue on CM14/LAOS14 based ROMs. Root won't stick. You'll have root for like 10 minutes after flashing but lose it eventually, in my experience. I've heard similar issues from other people.
[SuperSU] Chainfire:
Re: F2FS/CM/LAOS

It's not just an F2FS issue, or just a CM/LAOS issue. I've been running SuperSU on my LAOS+F2FS GalaxyS5 for hours now and it's still working fine...
[SuperSU] Chainfire:
I just flashed N6F26Q on my own Nexus6 with Pin-on-boot protection, it's working fine for me. If you're still having this problem, try deleting /data/su.img in TWRP and reflashing SuperSU.
[SuperSU] scanno:
I have simular issues with omnirom on the oneplus 3t. Perhaps there is something I can test?

Verstuurd vanaf mijn ONEPLUS A3003 met Tapatalk
[SuperSU] Chainfire:
I really wouldn't know what. Disappearing root is very difficult to debug without a live device in my hand.
[SuperSU] yung40oz84:
A good developer would help [MENTION=631273]Chainfire[/MENTION] debug and fix, just my thoughts.
[SuperSU] scanno:
It has nothing to do with f2fs. Clark also has a data partition (stock) that is formatted as f2fs and has not problems. Also running omnirom.

Verstuurd vanaf mijn ONEPLUS A3003 met Tapatalk

---------- Post added at 07:47 PM ---------- Previous post was at 07:43 PM ----------

It is not really a disappearing root. If I am in a terminal session and want root (typing su) I see errors. Do not know what errors because a working supersu was not really on my to-do list.