yashsingh1/xdaforums huggingface dataset:
[SuperSU] egingell:
He's taking about old versions.

No. There's no search function. Google is your best bet.

Sent from: LG G4 MM 6.0 / SGS5 MM 6.0.1
[SuperSU] Ibuprophen:
I have pretty much all of the older ones i was about to upload to my File Host Account.

I haven't yet but, if you tell me the version, i can do an upload and send the link to you.

I'm doing a good PC cleaning and have been working on a bunch of uploading for certain files.
[SuperSU] culiacanazo:
Guys lineage comes with a "suer" and "unsuer", although I haven't had that problem, it just may help you there, and make your switch from there as needed as far as super user management apps go

---------- Post added at 06:59 AM ---------- Previous post was at 06:54 AM ----------

Man every time i see your avatar i can't help but chuckle!

Ok, straight to business at hand: is your AFH name Rxly, also?

BTW tried to thank you but i ran out... Know what i mean?
[SuperSU] Y314K:
Thanks, v2.05 should be fine for current testing. Might try different versions to see if any newer versions GUI might work too after verifying that the v2.05 does.

Young Frankenstein is on my top 10 comedies of all time. Of course Blazing Saddles is #1.
[SuperSU] jdegreef:
Ok, I misunderstood you.

For me *the* version is always the latest one ;)
[SuperSU] Strephon Alkhalikoi:
I installed 2.79 SR2 on a Dell Streak still running Android 2.3.3 and had no issues with the GUI. That device's last "official" update was roughly 1.74 or 1.75, so you should have no issues installing the latest on your device. But perhaps I misunderstand your intent here.
[SuperSU] Y314K:
This is a known long running issue on Rooted Amazon Fire TV 1's. Might be something that is being actively partially blocked. I am thinking of trying the latest too.
[SuperSU] zaibansari20:
What does this XBIN mode mean?

Super su was installed in systemless mode from recovery then it asked me to update binary
[SuperSU] Ibuprophen:
Actually, i did still have the old link to Chainfire's 2.05 version. Here's Chainfire's link that I confirmed working and still downloads. I guess it may be time to do a little housekeeping on my bookmarks LOL!!!

http://download.chainfire.eu/461/SuperSU/BETA-SuperSU-v2.05.zip

I think that show is, indeed, one of the classics! LMAO!!!

"Dr. Frederick Frankenstein: You know, I'm a rather brilliant surgeon. Perhaps I can help you with that hump.

Igor: What hump?"
[SuperSU] Strephon Alkhalikoi:
[MENTION=7288133]zaibansari20[/MENTION]: It's reminding you that you installed SuperSU over the built-in superuser.
[SuperSU] MPeti1:
But it's faster to get into SuperSU with fingerprint, and SuperSU 's pinpad is a bit slow. I mean, i need to wait (very few time, a fraction of a second) after i press a number and before press an other number.

This not works for me :/ the setting is on the default 10 sec, and it seems SuperSU denies root access because it detects some other app opened instead of SuperSU. It's surely not timeout problem.
[SuperSU] jcmm11:
Try turning off tapjacking protection in SuperSU? (Just guessing)
[SuperSU] zaibansari20:
What does this XBIN mode mean?
[SuperSU] egingell:
Not satisfied with the answer you received, so you decided to ask again?

Sent from: LG G4 MM 6.0 / SGS5 MM 6.0.1
[SuperSU] Pkt_Lnt:
Same the reply to you the first time.

https://xdaforums.com/showpost.php?p=70788224&postcount=1103
[SuperSU] zaibansari20:
I installed addon-su.zip for LineageOS 14.1 from official site

So it mean that XBIN mode

It also asking me to update su-binary but the problem is when I update binary and reboot

My device stucks on boot
[SuperSU] culiacanazo:
*whispering*

hey dude... yes, you... I'mma drop you a hint, up to you, it won't hurt or affect me...

A little acknowledgements would come in handy right about now; also, a thanking phrase or clicking if you haven't...

*whispering with only the wind in my voice now*

.... You're coming across as just a tad rude...
[SuperSU] Pkt_Lnt:
"I installed addon-su.zip for LineageOS 14.1 from

official site

."

So that is where you need to go for help since you did not install app from this thread.
[SuperSU] zaibansari20:
After that I installed SuperSU-v2.79-201612051815.zip

It means I installed an app from this thread
[SuperSU] TimSchumi:
Why are you installing LineageSU AND SuperSU?
[SuperSU] zaibansari20:
Just checking the addon by Lineage

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

Now I found the original cause of losing systemless root

When I use Dualboot Patcher, it patches boot.img to work whick conflicts with systemless root
[SuperSU] culiacanazo:
That means CTRL+Z, reverse, undo, go back, and then when you have a clean slate, only flash one or the other, whichever you wish, and i assume is the latter choice, namely "Welcome, come on in! How can we help you?"

---------- Post added at 07:54 AM ---------- Previous post was at 07:47 AM ----------

If you do exactly per the instructions, and nothing else, you should be able to boot no problem, don't forget double checking your boot.img after uninstalling so it's ready to receive the patching from SuperSU... Unless it installs as system, but that depends on quite a bit of other factors that are best left undisturbed right now since they may not even become a factor at all.
[SuperSU] Ja_som:
Why??? Just why you use two different root systems???

Official Lineage OS root is of course system root, because why not...

SuperSU is (probably also on your device) systemless root...

So, choose one Lineage root or SuperSU...
[SuperSU] zaibansari20:
To use Dualboot Patcher I need System mode

But whenever I tried to install SuperSU in system mode my phone didn't boot

Now I'm Lineage root
[SuperSU] Ja_som:
If you need system root, use Lineage (what you did), but why you also install SuperSU?
[SuperSU] zaibansari20:
Btw I was on Systemless mode

It was causing problems with Dualboot Patcher

Then I installed Lineage root to install SuperSU in system mode

But when I updated the su binary from SuperSU

My phone stuck on boot

Then I restore the boot.img and system which was rooted systemlessly by supersu zip

Then I flashed UPDATE-unSU-signed.zip to fully unroot my phone and flashed Stock lineage boot.img
[SuperSU] Ja_som:
Lineage root has nothing to do with SuperSU, it is different root. If you have SuperSU, you need to uninstall it to use Lineage root, and vice versa.
[SuperSU] zaibansari20:
Now I'm just running Lineageos root
[SuperSU] culiacanazo:
Now no problem for your application, then?
[SuperSU] zaibansari20:
No not at all

And not with root
[SuperSU] Filip013:
This is really off-topic, but I'm just curious. What issues did you experience with DualBootPatcher and systemless root? I use stock MIUI ROM and so I need SuperSU to get root access. I tried LineageOS as a data slot ROM and it worked without issues. I also flashed patched Magisk on data slot and it worked without issues. (I don't think I tried SuperSU, but I think it's compatible.) So I don't understand what issues you were facing.

Hm... Did you maybe patch your primary ROM? Because I didn't and I imagine that might cause some issues with systemless root.
[SuperSU] zaibansari20:
DualBootPatcher patches the primary boot.img for mbtool

This patching conflicts with my LineageOS 14.1 systemless root. I was facing the same problem earlier with DualBootPatcher

Everything was working fine before Dualboot
[SuperSU] Filip013:
Hm... Conflicts in what way? What are the issues you experienced? I have systemless SuperSU on my primary ROM and I have no issues with switching ROMs. I've only had issues app sharing, but I think that's ROM's fault.

P.S. Maybe you should try SuperSU beta.
[SuperSU] zaibansari20:
Do you have bootui support for your phone
[SuperSU] Filip013:
Ah! So that's the issue. No I don't have it. I'm not even sure what it is. I use the app or DualBootUtilities to switch ROMs. I take it that means that Boot UI is not compatible with systemless root.
[SuperSU] zaibansari20:
Check in the settings of DualBootPatcher

Can you please tell me the device model
[SuperSU] culiacanazo:
Should i grab pop corn now?

Lol I'm getting a kick!

Now, seriously, this is not only off topic, this is a lost in the woods topic
[SuperSU] surbiks:
where can download su binary source code?
[SuperSU] egingell:
You don't. SuperSU is closed.

Sent from: LG G4 MM 6.0 / SGS5 MM 6.0.1
[SuperSU] surbiks:
why ?
[SuperSU] shaggyskunk:
Developer's prerogative
[SuperSU] MPeti1:
It's the same :/
[SuperSU] Alxoom33:
It might be your OS. I have Android 7.1.1 Stock/debloated on the Nexus 6 and Pixel C and never lost root. You may want to go to your device threads and check with the developer.
[SuperSU] maxher66:
I can use this installable ZIP or needed SR3 flashable zip on mm6 rom ? ty
[SuperSU] ALIGATOR26:
For Marshmallow use the stable version v2.79

Trimis de pe al meu SM-G930F folosind Tapatalk
[SuperSU] Ch3vr0n:
Bollocks, SR3 works just as well
[SuperSU] Shrooblord:
Hi.

I'm having trouble installing SuperSU. When it finishes, either through TWRP or by installing while the phone is booted to system, then restarts, I end up in an infinite boot loop.

I've waited for 25+ minutes for the phone to boot, after which I decided it must have gotten stuck, because it takes 0.5-1 minute per normal boot and 3-5 minutes if it's performing a lot of tasks while booting. 25+ mins is definitely abnormal.

I am using a custom ROM called Resurrection Remix to run on my Samsung Galaxy Note II (n7100), where I also mentioned I'm running into issues with SuperSU.

The link to that post is here:

https://xdaforums.com/showpost.php?p=70844470&postcount=452

PS

The phone is already rooted. I can give apps root permission and Rootchecker apps confirm correct root status.
[SuperSU] ZeeJcG:
After succesfully flashing and installing the binary script and then rebooting the device, it is stuck at logo only, not booting up. My devicd is Zenfone 5 and im using LineageOS 7.1.1 custom rom. I flashed 2.79. please any help?
[SuperSU] jdegreef:
https://xdaforums.com/apps/supersu/support-update-failures-t2907365/
[SuperSU] ulxerker:
Try to flash SuperSU v2.79 SR3.
[SuperSU] arvati:
Thanks for the great work...
[SuperSU] Shrooblord:
Reply on the problem:

OK - problem is that I can't use SuperSU alongside this ROM. (But fortunately I don't need to, since I already have root access.)
[SuperSU] Frédéric.Stol:
Asus ZenFone Max Z010D

Hello,

I can have root with this version nor the 2.78 version.

The current version I use is 2.46, it work well on my ZenFone Max Z010D ?.

The method I use for is TWRP with zip install.

Have a good day, I hope this will help your improvement.

Thanks for your work
[SuperSU] quasarswastik:
Same problem with Resurrection Remix based on Android Nougat on Zenfone 5. I think its some OEM(Asus) only problem.
[SuperSU] vygavedha:
Can u try systemless mode of rooting with 2.79 version ? Because it worked for me for all noughat roms including RR too...
[SuperSU] DarkLanternX:
I am using a RR 5.8.0 android 7.1 ROM , I use to use magisk to hide root on RR 5.7.3 android mm, after updating to N ..magisk stopped working , so I just thought of suhide. Has anyone managed to run it successful on RR 5.8.0 7.1 or any 7.1 based custom ROM?
[SuperSU] DB126:
Magisk 11.x reportedly works with Android 7.1 (specifically LinOS 14.1).
[SuperSU] DarkLanternX:
I am having a problem with it, cuz in Android N the safetynet keeps loading and loading both in v10.2 and 11.0 so i was thinking of suhide
[SuperSU] Ch3vr0n:
Well you're in the wrong thread for suhide and it doesn't work with any ROM with Nov '16 and higher security patches.

Sent from my Nexus 7 (2013) with Tapatalk
[SuperSU] kevinblackwell:
Super su 2.79 doesn't work on Z play with 7.0 nougat stock

HELP
[SuperSU] Surge1223:
That's because the boot.img everyone uses is wrong, dt is the wrong size and wrong address, also it has userdata defined to use f2fs so fs_mgr is not thrilled. dtb header is offset by 2072 bytes. This was from a quick glance.

you're better off using the custom zimage with stock ramdisk and patching verity, encryption and mount flags.

This is assuming you're using the boot images I've seen on xda and for Z play

I'm assuming supersu either cant dump to stock ramdisk to /data since it's defined as f2fs in fstab or that the ramdisk is not compressed correctly leading to this error.
[SuperSU] kevinblackwell:
Thank you for the fast answer, I send you a private message.

Regards
[SuperSU] lectricas:
Unable to get root on my tmo h811 LG g4.

After flashing supersu v2.79 zip via TWRP, I don't get any SuperSU apk or root on my device.

Also it says something like

boot image patcher failure aborting

but other than that rooting seems to be successful.
[SuperSU] Ch3vr0n:
If the boot image patcher fails then rooting is NOT successful. That's what needs to be done in order to get root. Unless you try the system method. You need to provide the logs and boot image so chainfire can take a look

Sent from my Nexus 6P with Tapatalk.
[SuperSU] Alpha1BA:
is there anybody that has a stable v that would be compatible with my Tab S2 T813???

Thank you
[SuperSU] vygavedha:
I had flashed AOSP ROM in titan.This ROM comes with inbuilt super Su..But it could not give root access to secure settings plugin of Tasker.I read somewhere in this forum because of SuperSU installed in some other location.in order to fix, we had to flash SuperSU after typing something like below

echo SYSTEMXBIN= true >>/data/.supersu

Can anyone know what is the exact issue and how to resolve ?
[SuperSU] swallowingled:
You can read more about it here on Chainfire's Google + page.

https://plus.google.com/+Chainfire/posts/N6EARb8LF3d
[SuperSU] vygavedha:
Thanks dude. .. .I have to bookmark this...Whenever I flash AOSP ROM,I face this problem...
[SuperSU] chivisimo:
Excellent...

Work like a charm in my htc desire 626s
[SuperSU] barry123:
Decided to post here to the main SU forum as well. Sorry for the double post:

I hope I'm using the right forum as this was not an issue before I used SR3-SuperSU-v2.79-SR3-20170114223742. I've decided to root my Nexus 6P again. Using Lineage OS build NMF26B [7.1.1]. So the problem is, in developer options, I've enabled Android debugging/notify. Root access page only gives me option to ADB or disabled ONLY. ADB & Apps is NOT in the list since using the 2.79 file. Security: unknown sources is ticked off as well. I don't have a notification at all on my status bar about android debugging nor notification on connection options i.e. USB charging/MTP....etc. It was working before tho'. Anyone can help out on this problem? I am rooted, SuperSu app is enabled, etc. Double/triple checked everything, re-booted in case I did make any changes to be certain. I installed Lineage OS/GApps/SuperSU 2.79,etc from a flash drive, cleaning up my phone completely. It's only the problem with developers options problem. Thanks!
[SuperSU] DB126:
See 3rd bullet: http://lineageos.org/Update-and-Build-Prep/
[SuperSU] jdegreef:
Cross-posted ! I've replied to you in the Supersu dev thread !
[SuperSU] gbdrbob:
Hi, I'm trying to get systemless root on my stock galaxy note 3 with android lollipop 5.0. I just want to temporarily root to enable call recording then unroot, keeping safetynet pass for banking apps and android pay features.

I've installed twrp via odin and found these instructions on how to force a systemless root install. I've backed up my boot partition to restore it and unroot my device after enabling call recording.

Is that all I need to do? I'd prefer to get it right and not mess up my system - it's a while since I did anything with root.

The main thing worrying me is the changelog for 2.79 which says systemless on 5.0 "requires 3rd party patches" - can anyone explain what that means? Which patches, are they included or do I need to install something else to get systemless root working on 5.0? - I've been hunting through the thread and google but not found an answer.

Thanks in advance for any help.

EDIT: Nevermind. I tried a standard root with SuperSU, installed the call recording patch then did full unroot and I still pass safetynet checks, so didn't need systemless after all.
[SuperSU] Destr1k0h9092:
:svetius:
[SuperSU] sguy156:
I used SU v2.79 for One Plus 3T with Android 7.0 and that caused phone to bootloop. Which version of SU works with 7.0 and doesn't cause bootloop.
[SuperSU] ulxerker:
SU v2.79-SR3
[SuperSU] jjakajonas:
Is there a way to make a temp unroot thing?

I will try a SMART-ID app we have in Denmark there is recurring a unrooted device.
[SuperSU] chillo71:
Hello, I did Full Unroot, when app asked I restored boot.img but not recovery and went on a big fat brick. I restored from a backup and now I 'm back on scratch. I have to go all the way from the beginning, maybe try a more productive path..

What should I try to completely remove Su?

My thinking was to flash stock recovery first and then full unroot from within supersu app, will this work?

*I'm on a MTK6750 device

**of course the point is not to lose any of my data
[SuperSU] jcmm11:
Just get unsu script from osmosis. Flash it via recovery.

https://xdaforums.com/showthread.php?t=2239421
[SuperSU] chillo71:
Thanks for the hand! I had unsu in mind but I thought it would be more complex and it is. Same stuck in bot logo

See, I was never able to mount /system rw, I have tried anything that I could.

maybe that was because I installed TWRP recovery without allowing any system modification.. ?

SuperSu was installed and working, so was BusyBox.

I first uninstalled BusyBox and everything seemed right and clear. Maybe the mistake was in SuperSu 's boot backup, it might have been overwritten by double installation, not sure.

Now I'm on a clean install. I have a full nandroid backup on PC .

Is there a way to recover from that my apps and settings and sd after installing TWRP? Like restoring /system, /data.ext* /external.sd* and such? Any recommendations what I should check ?
[SuperSU] extrahelper88:
Kingroot does the job but, there's a price (not monetary...) as it installs other bloatware type of applications:o and will stop working if you uninstall those.
[SuperSU] Ch3vr0n:
It also locks the binaries and is just lousy compared to SuperSU and irrelevant to this thread. Nobody asked for alternative rooting options.

Sent from my Nexus 6P with Tapatalk.
[SuperSU] chillo71:
meanwhile I managed to remove SuperSu on my backup with flashing system, recovery and boot images, along with secro.img and... logo.bin this time.

I 'm not sure if the guy who told me to flash thos was joking with logo.bin, but that worked ..!

I m now a happy droid user :D
[SuperSU] DB126:
I'm no fan of KingRoot (borderline malware) and actively discourage use when other options exists. That said, KR has its place as SuperSU can not root every device/ROM. The previous posters comments were relevant for those seeking an alternative to SuperSU when it doesn't work or isn't applicable.
[SuperSU] vampirefo:
boot.img, recovery.img, system.img was enough, flashing the rest wasn't needed, but didn't hurt your phone either.
[SuperSU] chillo71:
I guess the whole mess was caused when i quit coffee and enabled system mount in TWRP, but I'm now too drunk to remember :xD

I mean I must have restored system.img a dozen times through twrp... but I couldn't get any hands on it with it running... or smt like that

Tyvm guyz, use the force for good cause and money :xD
[SuperSU] Ch3vr0n:
SuperSU can't root every device, for the simple reason that it doesn't rely on abusing exploits like KR.

Sent from my Nexus 6P with Tapatalk.
[SuperSU] habylab:
Do people find the stable or beta release works better on 7.1?
[SuperSU] Ibuprophen:
I'd recommend to try the Stable one and, if necessary, update it to the Service Release.

If the Service Release doesn't work out, then, what I've found, reflashing the Stable release won't hurt the device.

Just a suggestion but, what works for me, may not work for you.

Peace and Love!

Peace and Love!

~Ringo Starr~

Sent on my Communicator [SCH-I535] from the Bridge of the U.S.S. Enterprise...

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

**IF I WAS HELPFUL IN ANY WAY THEN**

**PLZ THANK ME WITH A THUMBS UP!**

********************************************
[SuperSU] habylab:
I've tried that, thanks.
[SuperSU] grep_i:
Can you be more specific will what work ?
[SuperSU] str8str:
If super su is installed via play store does it install as system less? Still shows option to install to system app in settings
[SuperSU] egingell:
It only replaces the su binary. Everything else stays as it was.

Sent from: LG G4 MM 6.0 / SGS4 LP 5.0.1
[SuperSU] Federacion:
I mean that maybe I don't have to reinstall the whole Rom but only the custom kernel to make Xposed to work. Will that work?
[SuperSU] mitchdickson:
1. Make a backup

2. Try it

3. If it didn't work, restore your backup
[SuperSU] grep_i:
What did you miss from my answer.

After updating Supersu just reflash Xposed and custom kernel that's all.
[SuperSU] thwalker3:
Supersu > 2.65 broken on HTC M9 with August security patches

Not sure if chainfire or the new developers read this thread, but they should be aware of the following thread over on the HTC M9 forum:

http://xdaforums.com/one-m9/help/attempting-to-root-unlocked-stock-rom-3-t3448785

Essentially, the HTC M9 just got 3.35.617.16 and trying to flash the ZIP for any supersu newer than 2.65 results in bootloops. Using 2.65 ZIP and then updating to the latest (2.78) via play store and binary update works but is hardly ideal. If the next ROM version that the device receives includes new security features that prevent 2.65 from working, users of this device will be SOL. Looks like something in the ROM's new sepolicy is the culprit, but I don't have enough experience fiddling with sepolicy to nail down exactly what the problem is.

I'm attaching a diff of the (working) sepolicy generated by flashing the 2.65 ZIP vs the looping one flashing 2.66 ZIP. Hopefully someone can make some sense of it. This is the *only* difference between the ramdisks (of course, the su.img differs, because the binaries were updated between the two versions). Flashing the 2.65 generated ramdisk over a b0rked 2.66 update seems to work, so I'm pretty sure it is just sepolicy changes that broke it.

Please let me know if I can collect any more diagnostics for you.
[SuperSU] banciii:
No. If you flash su first, the convert option disappears from dev options. If you flash it after the convertion, you get bootloop. So it is not compatible yet.
[SuperSU] jukiewalsh:
Doesn't boot when installing on Oneplus 3, clean flash of stock rom and no other mods besides twrp.
[SuperSU] Alxoom33:
That is so out of context, nobody, including me, knows what you are talking about.[emoji4]
[SuperSU] ktmom:
Don't you have to force systemless on a OP3? I thought folks were posting modified zips to make that easy.
[SuperSU] Sam Nakamura:
For my OnePlus 2 I need a modified version of super su, maybe check at oneplus forums..
[SuperSU] banciii:
Wow, how did you ask all of these people this fast, about what I am talkin about? :D But you can understand what I am saying if you search for Android Nougat's new Direct Boot feature, which has a developer setting requirement, called File (based) encryption. This option disapperas if you flash SuperSU and you can't turn this new encryption on. Or if you enable it before you flash SuperSU, you will get bootloop after the flashing. :( Or at least I got it.
[SuperSU] grep_i:
Maybe he did read a little, like stated in the forum rules.

Next time it is better to be clear and specific so anyone can understand what you are talking about.

That way your comments can be helpful for anybody on this forum.

And you will get better answers from other forum users.

Question remains why you have this problem and like I said before be very clear and specific.

Tell us about your device model and type and all used software versions.

Maybe we can help you find out what's going wrong.