yashsingh1/xdaforums huggingface dataset:
[SuperSU] DullPeon:
Is there a way to get the v2.82/sr5 zip into a tar form to flash directly from odin?
[SuperSU] DB126:
Use FlashFire.
[SuperSU] ktmom:
Have you looked for a cf autoroot for your device? Once rooted at all, you could update with FlashFire.

"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
[SuperSU] Sr. Zé Alguém:
Above question is nice, if it could be flashed directly from Odin, installing TWRP would not be necessary. If this was possible, it would be a good thing for Samsung owners.

I would ask another question: what kind of scripts are needed to be included inside a tar package that can be flashed by Odin?
[SuperSU] ashyx:
The question was answered. CFAUTOROOT.
[SuperSU] Sr. Zé Alguém:
Definitely not answered. Maybe there is no easy answer, but flashing a modified firmware image is not the answer. Surely the answer won't be found on this thread.
[SuperSU] ashyx:
I'm afraid it is the answer and always has been. :rolleyes:
[SuperSU] ktmom:
In case it helps you, here is the modern CF-Auto-Root link. And for completeness, the original but depreciated page.

"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
[SuperSU] Sr. Zé Alguém:
The point is other: an way to just flash SuperSU using Odin (yes, Samsung phones), without needing to flash TWRP, firmware, rom or whatever.

As far I can see CF-Auto-Root firmwares are modded original firmwares where Chainfire injected SuperSU. Flashing them will lose current data etc. Not the answer for how to create a .tar.md5 of *only* SuperSU flashable by Odin. If you say 'Odin can't flash anything other than a firmware or TWRP', it would be an answer.
[SuperSU] ashyx:
Nope, it seems you have a misunderstanding of how CF-AUTOROOT works, it doesn't affect DATA at all. I think you need to do a little more research.

The ONLY thing CF-AUTOROOT will modify is the boot partition, exactly as it would if SuperSU was flashed by TWRP.

Also in any case, irrespective of the above, flashing stock firmware or otherwise should not affect DATA.
[SuperSU] mielletseed:
That's not really true too :)

CF-AUTOROOT replaces the recovery to run the scripts needed to root and then replaces the modified recovery with a stock version. It uses the stock version from the firmware mentioned. So you might have an old recovery after CF-AUTOROOT. But you are right, CF-AUTOROOT doesn't replace /system or deletes /data. You could achieve the same by flashing twrp, using "normal" SuperSU-ZIP and flashing stock recovery after that.
[SuperSU] AjOzzo:
how do unroot?

unroot failer
[SuperSU] DB126:
Might also be able to avoid mucking with recovery partition by booting TWRP vs flashing (overwriting). My preferred approach on several devices.
[SuperSU] ashyx:
Unfortunately not possible on Samsung devices.

---------- Post added at 02:30 PM ---------- Previous post was at 02:26 PM ----------

Correct, but I didn't want to confuse matters even more.
[SuperSU] Sr. Zé Alguém:
Both answers made it very clear, thank you 2 ;)
[SuperSU] Devilix:
Why i get a bootloop after the flash of this file??? :(
[SuperSU] jcmm11:
Hard to say with no additional information. Did you also restore stock boot image (as the instructions state to do)?
[SuperSU] Devilix:
So, i'm on THIS rom, and superSU is integrated, in system mode... i think...

And i would like to remove it to use magisk, or superSU but systemless :rolleyes:
[SuperSU] xdalass:
Thanks!

PS: Just saving this for later, dunno how to save just one post, sorry!
[SuperSU] jcmm11:
Not really sure, I don't do Samsung, but from what I know on Samsung you need 5.1 for default systemless supersu (non Samsung it's 6.0). I don't know if it'll work if you try to force systemless.

As far as Magisk I'm not sure what the minimum version for that is.

Since it's a custom ROM systemless won't really give you an advantage, even if you can force it.

As far as bootloop issues after running UnSU a log of the uninstall would probably be helpful. [MENTION=4544860]osm0sis[/MENTION] may know more.
[SuperSU] hopecore777:
Can i use this with my aex custom rom, android 7.1.2?
[SuperSU] shaggyskunk:
Yeah why not? You have TWRP installed? ?

Sent from my SM-G955W ?? ?
[SuperSU] hopecore777:
Yes i have. Where i can find the apk & the zip file sir? Sorry for my noob question. I've been experienced a boot loop many times. So i already ask to this thread for help.
[SuperSU] shaggyskunk:
The OP is a good place to start ??

And Flash the zip not the apk.
[SuperSU] hopecore777:
I see. Thanks! :)
[SuperSU] shaggyskunk:
Also - Make sure you have a recent Nandroid backup ??
[SuperSU] Cyberuben:
I seem to get a softbrick when attempting to install this on my OnePlus 5T. I have OxygenOS 5.0.4 and use TWRP twrp-3.2.1-0-universal-codeworkx-cheeseburger.img

Anyone know what might be wrong?
[SuperSU] osm0sis:
5T=dumpling, 5=cheeseburger, for one.

Try it with twrp-3.2.1-0-universal-codeworkx-dumpling.img perhaps. It's also quite possible SuperSU has fallen into disrepair.
[SuperSU] hopecore777:
Why? :(
[SuperSU] jcmm11:
Device?
[SuperSU] hopecore777:
Lenovo a5000, I'm using a custom rom, AEX 4.6, android 7.1.2
[SuperSU] shaggyskunk:
Well... Try to find any information on Coding Code....Even their Play Store address doesn't bring up any results beyond 2016 - Personally I wouldn't Flash any version that they came out with - Still happily using Chainfire's SR5 v2.82.

Seems to be a pretty sketchy outfit using what appears to be a "legal services llc" address.... that's been referred to as a "shell company".

Thanks - But NOT interested..

Sent from my SM-G955W ?? ?
[SuperSU] jcmm11:
From what I found that's a MediaTek CPU. I don't think SuperSU does MediaTek. You can try Magisk. (I don't know if that will work either)
[SuperSU] xell75:
I have an Mediatek too, but for me SuperSU works without any problems.
[SuperSU] DB126:
Not a CPU/SOC issue; SuperSU works fine on MediaTek devices when that's the only variable.
[SuperSU] AJ:
any news on supporting Android P ?
[SuperSU] laupuy:
no -> https://plus.google.com/+Chainfire/posts/6Sp6t9LxtQZ
[SuperSU] p1r473:
On my Pixel XL 8.1:

Just booted to twrp-3.2.1-2-marlin, flashed twrp-pixel-installer-marlin-3.2.1-2, and when I try to flash SuperSU-v2.82-201705271822 from within TWRP, SuperSu is not found when I boot to system
[SuperSU] sharkie405:
SuperSU does not work on 8.1, so far as I'm aware. Nor is it likely to ever get updated to work. I think you'll have to stick with magisk.
[SuperSU] Ibuprophen:
Just to clarify...

Are you referring only to the Pixel devices under Oreo?

I, personally, know that there's SuperSU issues with many/most of the Pixel Devices depending on which specific Pixel Model and/or Android Version loaded on those devices.

I would just hate to see a member be misquoted because your post looks like a "Blanket" type of statement that may be looked at as SuperSU doesn't work for any Oreo Device.

I'm not stating that you don't know what you're talking about nor am I trying to argue against your post...

I just wanted to see if you can clarify this Opinion/Fact a bit more.

Thanks a bunch! :)

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

I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
[SuperSU] sharkie405:
I thought it didn't work on 8.1 on any device, but I certainly could be wrong. Apologies. It for sure doesn't work on Pixel 2s.
[SuperSU] Ch3vr0n:
You are wrong. Works just fine on my Nexus 6p on 8.1 and has done so since the first 8.1 release

Sent from my Nexus 7 with Tapatalk
[SuperSU] jcsww:
I haven't had any issues with it on my 6P either.
[SuperSU] j1gga84:
Is there a working script that keeps SuperSU installed after a dirty flash of the ROM?

I am currently running Resurrection Remix 5.8.5 (Android 7.1.2)

regards
[SuperSU] ashyx:
You shouldn't lose root unless you replace the boot image or the data partition gets wiped.

If you don't replace the boot image then you can use the FRP flag to maintain root even after a factory reset.
[SuperSU] GopalKaul:
How about using flashfire?

It will automatically maintain root
[SuperSU] jcmm11:
Just backup the boot image, dirty flash the ROM, restore the boot image. You should be good to go.
[SuperSU] Ibuprophen:
I'm not sure about Resurrection Remix since I only have a "working knowledge" of it but, have never personally used it on any of my devices (though I had always planned to try it out on one of them).

I can only state what I, personally, need to do when it comes to the LineageOS I've got installed on 2 of my devices.

Though, I only dirty flash if needed functionally or periodically...

For myself, when I dirty flash a LineageOS update (in TWRP), i have to go with the following flash order:

1) LineageOS

2) SuperSU

3) XPosed Framework (optional)

Then begin the dirty flash, wipe Dalvik when done and then reboot.

For me, if I don't flash those together, I typically ended up with a 50% +/- chance of resulting in an issue with SuperSU.

When it comes to XPosed, it rarely resulted in an issue if I had left it out but, (knock on wood) I've never, till this day, had an XPosed issue when I did add it to the dirty flash.

I'm not stating that what works for me will definitely work for all but, I was told a while ago that, when the firmware is dirty flashed, SuperSU needs to follow right afterwards because the Firmware sometimes/most of the time can/may undo something regarding SuperSU.

I'm just providing my thoughts/opinions to, hopefully, help others.

Good Luck!

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

I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
[SuperSU] flipmode_11:
[MENTION=8912262]hopecore777[/MENTION];75794179 "Boot Image Not Found"??? I think you have a different issue than Mediatek problem/issue. Have you tried flashing an already rooted ROM? Same issue? Have you tried flashing ROM and using Slot 2 for SuperSU - so you flash it together? Sequence of items makes a big difference. Check if a SuperUser is not already on your ROM or su is just corrupt?

Trying Magisk is very realistic. They've just released another update with further device support and additional OS support. The other benefit of Magisk is that it does not modify your /System partition which means upgrading custom ROM's, troubleshooting issues or reverting to stock is much easier. Check the Magisk topic and download the Magisk flashable ZIP, Magisk Uninstaller flashable ZIP, and Magisk Manager.

I'd be interested to see if you get the same error...
[SuperSU] cnkzlyr:
Guys can anyone help me to make a patch to install supersu as systemless sbin on android marshmallow without aroma. Want to make it on one zip
[SuperSU] ashyx:
Just use the system mode zip or use the system mode flag. No need for patches.

https://xdaforums.com/apps/supersu/v2-64-2-66-supersu-mode-t3286120
[SuperSU] jcmm11:
Just modify the update-binary file in the SuperSU install zip to include the echo command up at the start of the script

echo "BINDSBIN=true" >/data/.supersu

That should do the trick.
[SuperSU] sibali:
Thank you for the links……
[SuperSU] minhajul6322:
how to unroot from supersu
[SuperSU] Badger50:
Search for the un SU flashable zip :good:
[SuperSU] furboom1240:
Try SuperSU's built in option to do that

You can do so from the app's settings. Or you can simply wipe your ROM and skip the root option.

Be sure to make a nandroid backup of your current ROM if you change your mind.
[SuperSU] ranasrule:
which version of SuperSU are you guys using with 8.1 ? Can you provide a link ?
[SuperSU] Badger50:
What device are you using SU hasn't been updated in a very long time. So, compatibility will likely be an issue for 8.1.
[SuperSU] shaggyskunk:
I've been using SuperSU SR5 v2.82 on AOSP 8.1 without any issues on a Samsung S7 ?

link is in the OP

Sent from my SM-G955W ?? ?
[SuperSU] Badger50:
It's Levon! ??
[SuperSU] shaggyskunk:
lmao ??
[SuperSU] GopalKaul:
I didn't get the meaning?
[SuperSU] Wolfcity:
Long story... [MENTION=4351374]shaggyskunk[/MENTION] made a reference to that Elton John song in another thread and he's not to old ?.
[SuperSU] Wolfcity:
inadvertently double post.
[SuperSU] twistedominoes:
When I try to flash this on my Samsung sm-G950U it gives me secure system check fail: boot. Does this need a unlocked bootloader to flash?
[SuperSU] SpasilliumNexus:
Yes it needs to be done with an unlocked bootloader. No, Snapdragon variants of the S8/S8+ don't have a way to unlock it.

You want root? Look for SamFAIL in the respective subforum.
[SuperSU] nademandy:
Thanks
[SuperSU] dhampire:
My devices is ASUS Zenfone2 (ZE551ML) Z00A , X86 based.

Supersu 2.82 => OK

Supersu 2.82 SR2-SR5 => after install it, boot to recovery only.

I want to use suhide but can't install after SR2 version.

Does anyone have supersu after SR2 version which can use for Z00A?
[SuperSU] We7dy:
Hello,

I'm on Android Oreo 8.0, on the latest version of OxygenOS and when I try to flash SuperSu with the latest version of TWRP, when I restart, I get stuck on the OnePlus logo. Is SuperSu compatible with Oreo?
[SuperSU] Ch3vr0n:
Works fine on my N6p running 8.1 so yes, it's most likely something with the way the oxygen ROM acts

Sent from my Nexus 6P with Tapatalk
[SuperSU] shake_me:
Cool
[SuperSU] Dr_Mask:
please help

my phone (Note 3 Neo duos)rooted with cf root and i have TWRP recovery ,

when i opened super user app it says (The Superuser binary (su) must be updated)

i clicked yes , it requested to reeboot and asked if i am TWRP or CWM or normal ,i choose TRWP ,then it rebooted in TWRP and update occurs

but phone keeps open in TWRP even when i press on power button only .

how to solve please ??

thanks
[SuperSU] ashyx:
Reflash TWRP. Next time choose Normal only and do not use any utilities to reboot your device to recovery.
[SuperSU] ktmom:
[MENTION=625504]Dr_Mask[/MENTION], it sounds like you have an older version of TWRP recovery that it's attempting to help this along. If your TWRP hasn't been updated since MM came out, it may be adding to your troubles.

If you flash SuperSu 2.82 SR5 in TWRP it should update the binary. Make sure to deny any pop-up from TWRP offering to do root updates/installs.

"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
[SuperSU] vponomarev:
I have Galaxy S9+ (G965F) with latest TWRP 3.2.1.1. Flashed patched stock kernel that disables dm-verity, then flashed SuperSU 2.82 SR5.

At first it worked, but then, perhaps, after reboot when I start the app it just gets stuck on black screen.

If I clear app's data/cache, I see the initial green screen, but same back screen after pressing "Start" button.

Occasionally, once in a blue moon, I can open the app, but that's only until the next reboot.

I tried to see if there is anything obvious I can see in logcat (just ran "adb logcat"), but didn't notice anything interesting.

I then tried 'adb logcat "eu.chainfire.supersu:V" "*:S"', but didn't get anything.

Sorry for very little info, but not sure where else to look. Any suggestions? Thanks!
[SuperSU] ashyx:
Maybe the kernel isn't compatible with your current firmware or you are hitting encryption issues.

You'd be better off flashing the stock firmware then flashing the dm-verity/encryption patch to patch the stock boot image.

Be aware you will need to Format the data partition.
[SuperSU] pedro1977:
Anyone aware of a trwp flashable version that will work on LOS 15.1 (LG G5 H830)? It reaches setup, freezes and then loops.
[SuperSU] ktmom:
Answered in the stable thread where you also posted.

"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
[SuperSU] zongojim:
Dears,

I try to use SuperSU v2.82 SR5 on a Pixel (sailfish) with Android P Preview factory image.

Unfortunatly I have the message:

- Patching sepolicy

--- Failure, aborting

In attachment the recovery.log file.

Thanks i nadvance for your help !
[SuperSU] Ibuprophen:
I don't have this device but, I did a quick search within your device dedicated area on the forum and I had located the following thread post that reflects the same issue that your having with a solution that member had found which may be helpful for you as well.

https://xdaforums.com/showthread.php?p=74751877

If you have any issues, questions or concerns regarding that, try posting the question to that member within that thread. He, or someone else, may be able to provide some additional member guidance to help you out.

Good Luck!

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

I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
[SuperSU] TonikJDK:
SU will not work, and it is no longer being developed. You need to use Magisk for root.
[SuperSU] xell75:
R.I.P SuperSU on Android 9.0+.. That sucks :(
[SuperSU] Alxoom33:
Use Magisk! SuperSU doesn't work on Pixel 2 and 2XL.
[SuperSU] xell75:
Glad that I not have a flagship device.
[SuperSU] Ch3vr0n:
Well I do, in a way. The N6p WAS the flagship model at the time ;)

Sent from my Nexus 6P with Tapatalk
[SuperSU] jcsww:
SuperSU works perfectly fine with the latest factory image of the Nexus 6P.
[SuperSU] Ch3vr0n:
I never said it didn't ;) I know it does

Sent from my Nexus 6P with Tapatalk
[SuperSU] scrubjay55:
Wait.. How do you know that? From where you got this info that it's not and will be not developed anymore?
[SuperSU] TonikJDK:
Chainfire announced in October that he was officially out of development for SU. Since then, and even before that, the new owners have done nothing. It's dead.
[SuperSU] scrubjay55:
Soo you saying that there wont be any updates by cctm either? RIP then.
[SuperSU] jcmm11:
They've been completely unresponsive, no updates, no status reports, no communication of any kind. Draw your own conclusions.
[SuperSU] Alxoom33:
Unfortunately, I agree, RIP SperSU.

I miss [MENTION=631273]Chainfire[/MENTION].
[SuperSU] Tylog:
Yes, and I do not understand the sense of it, the people take SU and then none of them works on it Since they took over, I think that's a pity and extremely pointless
[SuperSU] jcmm11:
How do you know that they haven't worked on it? I suspect that they have (and are) working on it but for their own purposes. Just because they haven't released updates doesn't mean they haven't made any. There's no reason for them to release anything to us. Supporting us, in their view, is probably just considered a waste of resources.
[SuperSU] DB126:
Businesses routinely make acquisitions for the underlying technology, people and/or resources with no intention if continuing the consumer facing product. Google does it all the time. Perhaps there was never an interest in continuing SuperSU in its present form. Maybe the business climate changed direction. Our selfish interests (dude - I want to rule my gizmo!) really are of no concern to the new owners.
[SuperSU] andrew2432:
I did exactly this for GE for an internship, identify issues to their continuity and eliminate through purchase
[SuperSU] Tylog:
yes, that's right and a pity at the same time. If you use something for so many years and then suddenly it's gone, albeit with an announcement, you quickly fall into nostalgia. But yes. the passage of time, whatever the meaning behind it. Whatever, life goes on :)
[SuperSU] Tomleungyuethei:
I am new with Supersu root. Maybe I ask, is it possible to use Supersu to root SM-G9650 (Galaxy S9+ HK version) now?
[SuperSU] zelendel:
Many saw this coming. It was mostly a money grab by the company. (it is known who they are and xda has a hand in it) this will most likely end up like miui. It will go from being an open source project. To being bought by a company and then released on Chinese phones.
[SuperSU] corkiejp:
Chainfire's SuperSU was never open sourced!

Yes I know that there is open sourced alternatives.
[SuperSU] andrew2432:
Haha yeah I remember tjw using some SuperSU code without consent...

Sell your stock at its peak. Maybe if that donation button was hit as much as thanks or complaints on the threads we would be signing a different song. This is a serious shockwave, there are only a few trusted root methods out there. Download page still up? Still works on nougat right? Take wins where we can!!!
[SuperSU] Ibuprophen:
It's funny (in a bad way)...

CCMT refers users (via Play Store and other locations) to post their Questions, Concerns, Issues, etc... on their SuperSU forum website.

When you go to their website, they rarely respond to any of the posts and a majority of those they had responded to are the same Robo-Response worded slightly different.

Their "Supposedly" support forum is completely filled with all kinds of Warez, Spoofing, Hack-Traps, etc...

I know that [MENTION=631273]Chainfire[/MENTION] can't take on anything regarding this development without permission but, I truly do hope that he releases something different that does the same as SuperSU and legally severed from it.

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

I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
[SuperSU] madbat99:
Maybe used by nefarious folks in power to backdoor their citizens' devices. Seems many tech companies have ties to military/government over there.

Too far? Yeah I realized as soon as I posted. Oh well. :cool:
[SuperSU] pkelly517:
The downloads linked in this thread are compiled by CF himself.

Nothing nefarious there.
[SuperSU] andrew2432:
Files still hosted on his website!! Will he host that final version forever? Obviously its not updated for o or p one or both, don't rightly remember.
[SuperSU] Wolfcity:
I don't think so. Download a copy and you're good to go ,there won't be any updates. And as far as I remember the last version was pre-oreo.
[SuperSU] jcsww:
It works fine on the Nexus 6P running stock O on April 2018's factory image.
[SuperSU] madbat99:
I don't mean the people who download. I mean what CCMT can do with it. They can let manufacturers pre load it on devices, or any other means. It was just speculation. Nothing more.
[SuperSU] ktmom:
Uhhhh... Nothing ever stopped manufactures from "pre-loading" root or any other hack on any device. It's got nothing to do with the decline of support after CCMT took over. I suspect it's nothing more or less than they are in over their heads.

Amazing how the conspiracy theories come out when people don't get what they want [emoji854]

"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
[SuperSU] Wolfcity:
I'm aware that it works on several Oreo devices.

But it wasn't build for them.
[SuperSU] madbat99:
I don't want it. I don't even use SuperSU. Not a conspiracy theory either. Just heard some things.
[SuperSU] andrew2432:
I don't think its wild speculation. Actually with all the strange spyware news lately....

And can ccmt make changes to the files hosted on chain fires site? I was/am inclined to trust chain fire but I didn't even think if he would be still in control of hosting
[SuperSU] jcmm11:
No - Chainfire's site is under his sole control.
[SuperSU] DB126:
Seriously? Not which is worse: screaming click-bait media headlines (beware of the "dark web") or social media where facts and opinion are synonymous.
[SuperSU] andrew2432:
I'm confused, I was just agreeing that ccmt may have purchased super su with their own interests in mind? Whatever those may be?

And has wannacry not been used by every idiot recently? Have android apps been collecting data and sharing with third parties? Have security vulnerabilities not sent people to prison for life for nonsense?

What's a dark web
[SuperSU] GopalKaul:
Dark web is the part of the web using .onion sites which has a lot of **** in it . You can find anything in the world there! Be careful while venturing into it
[SuperSU] osm0sis:
This thread is becoming unreadable.
[SuperSU] GuardianUSMC:
Agreed, people are going way off topic and just discussing anything and everything like it's a chat service.
[SuperSU] GopalKaul:
Sorry if it was directed to me but I needed to keep him safe from the dark world