yashsingh1/xdaforums huggingface dataset:
[SuperSU] borglogic:
Sorry, forgot to say I'm using a Pixel. TWRP with SuperSU was the first thing I tried and it's been working for months, so I kept using it.

I tried changing my Password to Swipe and also using a USB with USB C adapter and that didn't work either.

I'll try Magisk tomorrow after the coffee has kicked in.
[SuperSU] badhabit_wb:
Mine is an og pixel as well. I had to reboot before twrp would work after I changed it to swipe. I did a clean install after my ota didn't work out.
[SuperSU] borglogic:
I can confirm on my Pixel, flashing Magisk-v14.5(1456) with TRWP 3.2.1.0 works fine.

Just one day without Adaway and I thought I was going to lose it! LOL
[SuperSU] Sheetzie03:
Ain't that the truth! Haha
[SuperSU] Alxoom33:
If you plan on using Magisk, make sure that you remove SuperSu completely. Use most up to date Magisk Manager, I think v. 5.4.3 and Magisk 14.5.zip. I suggest you read up in your device forums before flashing.
[SuperSU] badhabit_wb:
That's what I used on my Pixel and it works great.
[SuperSU] akahroba:
Thanks a lot for this.
[SuperSU] ajack2001my:
Would like to report that I've updated to v2.40 on my Nexus 4 with Lollipop 5.0.1, all is good!
[SuperSU] Christendom...:
I've updated to v2.40 on my Oppo Find 7a with LVM as well, and root is maintained.

I was prompted to update su binaries, and did so with no problems.
[SuperSU] kmcphee:
Remember you have to update the binaries supersi is a user app but you go get the flash version and flashing through a recovery it becomes a system app and know what difference is

Yes is easier to just download and install however there is still an option in the supersu and you to convert to a system app after you install
[SuperSU] xdamami:
Thanks for all your hard work Chainire You are the best!
[SuperSU] turydios:
Thx for your job [MENTION=631273]Chainfire[/MENTION]

<< Turydios >>
[SuperSU] goran_oh:
2.41 works ok
[SuperSU] Chinaboy5216:
Galaxy Note 3 N9008V SuperSU 2.41 flash ok, no bootloop here
[SuperSU] Frank Westlake:
2.41 OK through TWRP on:

- Note_ SGH-I717 4.0.3

- Note3 SM-N900V 4.3 single user Permissive

- Note3 SM-N900T 4.3 single user Enforcing

Frank

EDIT:

I've been misidentifying my SGH-I717 as an SGJ-I717 (copy/paste error). Fixed.

Frank
[SuperSU] twobats1:
2.41 appears to be working fine on: SGS3

SGH-I747 ATT with LS-LP 4.0 w/NeoCore Kernel

Philz 6.48.4

Thank you [MENTION=631273]Chainfire[/MENTION]
[SuperSU] HorstiG:
Crash on Galaxy S5 (G900F) Stock KK 4.4 AllianceROM, BussyBox Pro, SuperSU 2.41 Pro.

No chance for a log file, the system stops completely.

after uninstall I have full root access without 1 problem.
[SuperSU] Chainfire:
Can you provide a link to both the exact firmware download and the exact busybox installer app you used ?
[SuperSU] HorstiG:
Hi,

This is my ROM: http://xdaforums.com/showthread.php?t=2716535

And that is Busybox.
[SuperSU] pbanj:
working fine on att note 2 running newest aokp 4.4.4 rom
[SuperSU] brandoncarlson33:
Working good on d2vzw running aicp lp nightlys
[SuperSU] eLPeReC:
Thank you Chainfire!

It works flawlessly on a Nexus 7 3g (2012) with [ROM][5.0][AOSP] Pixel Perfect Lollipops :good:
[SuperSU] Blümchen Blau:
Perfect

Flawless on Nexus 4 with Stock 5.0.1 and TWRP 2.8.2.0
[SuperSU] cesar74:
Working good on S5 4G
[SuperSU] ghenarys:
My LG G3 D855 is already on lollipop stock. Is it possible to root it ?
[SuperSU] DB126:
Yep - an update is needed. Unfortunately, no word (litteraly) from CCMT on future plans.
[SuperSU] tkacer:
Patiently waiting.....utilizing Magisk on the P2, but would much rather use SuperSu to root. I understand the advantages that Magisk has to offer, but you can't beat the history of stability that SuperSu has built!
[SuperSU] Badger50:
Not meaning to be a wet blanket, but the history and stability that was SU, has retired along with it's creator. Legends like Chainfire are far and few in between. On the positive side, magisk is pretty darn good too :good:
[SuperSU] xell75:
SuperSU still works for me even on 8.1. Magisk never worked stable for me, for me it's not good. Besides I don't need to pass Safetynet crap.
[SuperSU] shaggyskunk:
Yup SuperSU v2.82 SR5 is working great for me on 8.1 as well - Didn't even try Magisk on it ?

Sent from my SM-G955W ??
[SuperSU] DB126:
This has been my (limited) experience as well. Spontaneously lost root for no apparent reason on otherwise stable 6.01/7.1.2 configs. Grrr! Déja Vu SuperSU 2.79/2.80 on Android 5.1 based ROMs (y'all remember that nightmare?). That said, I am NOT condemning Magisk as it works for most, has unique capabilities and remains under active development. I applaud the developer for his/her selfless contributions along with an active XDA community that helps identify and squash bugs. Raises the bar for CCMT which to date has not responded. Well, we all need our sleep ...
[SuperSU] DodoGTA:
No logs = no fix
[SuperSU] Sh0X31:
In the Pixel with Android 8.1 SR5 don't work :(.
[SuperSU] DB126:
Why are you quoting me? Didn't ask for a "fix". I understand the drill and supply logs and other relevant detail when warranted. Choosing a different path does not preclude sharing experiences provided that does not include belly aching around the lack of a solution.

The SuperSU 2.79/2.80 fiasco produced plenty of feedback that ultimately led to a solution. The issues with Magisk are also being identified and squashed by the developer which what the point of my positive post. I personally opt to stay with SuperSU for now because it works and carries no disadvantages. In time that may change depending on what CCMT does with the product.
[SuperSU] Homeboy76:
Try Magisk:

I tested Magisk with Android 8.1 and it works on the Pixel/Pixel XL

a. Flashed Factory Image with Flash-all.bat (#5 in OP)

b. Fastboot twrp-3.2.1-0.img

c. Install twrp-3.2.1-0.zip

d. Reboot recovery

e. Install Magisk 14.5 (1456)

f. Reboot System
[SuperSU] Mzprx:
Yep... It crashes at sepolicy... Reading all posts it seems that this problem may be specific for Pixel.

However, this does not excuse CCMT for doing nothing... For example, TWRP fixed their software for couple of days (it had problem accepting the password) after the official 8.1 release. Not a zip (literally) from CCMT.

I agree with some of the other guys here that unfortunately SuperSU is about to become history. I don't really understand why CCMT spent money on something to abandon it... I would understand if they had competitive product and bought SuperSu just to kill the competition, but this does not seem to be the case...

So, I'll wait a bit longer, but probably will move to Magisk early or later, even that I'm not a fan of this app despite being big supporter of the open source software idea.
[SuperSU] Sh0X31:
Magisk drain my battery on Pixel. With SuperSU I get like 6-7h Screen on and with Magisk like 5h screen on what same settings and usage.
[SuperSU] Homeboy76:
Wow, Good information!
[SuperSU] martyfender:
CCMT does not even give any indication that they are even monitoring this thread, let alone provide any support or updates.

If ChainFire was still at it, he would have, by now, had at least a couple of SR releases.

And since CCMT never responds, it appears that they have either abandoned SuperSU, or at the very least, put it on hold for some reason.

The last time I checked their own thread, there had been no new activity.

Since Masgisk is getting more stable I may try it again in the future. For the present, the current version of SuperSU works great on my devices.
[SuperSU] osm0sis:
This is based on nothing, but it feels like CCMT ([MENTION=7678190]SuperSU Release[/MENTION]) has basically decided to all take a vacation at the same time as [MENTION=631273]Chainfire[/MENTION], as though they're waiting on him to make the transition to their public interactions, even though this is backwards and they should have introduced their new front-man as soon as CF announced he was entering the consultant phase of his contract.

Again, maybe just wishful thinking.. We'll see.
[SuperSU] badhabit_wb:
It's either that or they truly have abandoned supersu. If they plan to support it they're definitely getting a poor start.
[SuperSU] bsmitty83:
I kind of think chainfire saw this situation happening because if you look at the updater-script , it basically spells out verbatim how he makes the package . All the instructions are in the comments in the script . I never looked before but I don't think this is how it always was. I bet there is a way to update the zips supolicy without needing a new binary.

I'm not the most experienced person to look at it but I would guess someone could make an unofficial update work for at least 8.1.0
[SuperSU] Ibuprophen:
I believe in the statement "The loudest voice can be heard from many voices"

SuperSU on the Play Store reflects CodingCode (aka CCMT) as the developer and If enough members were to leave a 1 star ratings with verbiage that reflects the issues of abandonment by CCMT then this may have enough of an impact.

I had done this and also added that support elsewhere (which is where they will try and lead you to believe that you will be able to obtain support) has resulted by falling on a blind eye and a deaf ear.

Keep in mind that any negative feedback left will not be reflected upon Chainfire since he no longer is reflected as the developer for SuperSU on the Play Store.

Just a recommendation/suggestion... :)

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

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

PLEASE KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
[SuperSU] ashyx:
Nope, been like that for quite a while even before CCMT were on the scene.
[SuperSU] mrrocketdog:
...... pubic interactions. [emoji106] i loooove it!

fear a life un-lived ; not death
[SuperSU] osm0sis:
Bahaha, Google Keyboard, ladies and gentlemen.
[SuperSU] :
Magisk shouldn't impact on battery it's most likely something else

About supersu it looses root on the new installation method why I can't tell
[SuperSU] xell75:
I never lost root with SuperSU
[SuperSU] Homeboy76:
If you installed twrp 3.2.1-0 and your phone is a Pixel/Pixel XL. Please share the steps you used to install it.
[SuperSU] v12xke:
I used the instructions that are found on the TWRP download page.
[SuperSU] Homeboy76:
Ok, I wonder why so many, me included, lost root

with SuperSU v2.82 SR5 after flashing twrp 3.2.1-0. zip. Oh well, stuff happens.

Thanks for responding.
[SuperSU] v12xke:
Because on Pixel phones the Recovery now resides within the Boot partition. When you flash TWRP, it overwrites your root, so you have to reflash it after TWRP (SU or Magisk). Same thing applies if you run a custom kernel. It get's over-written as well, so the flashing order is TWRP, kernel, root. Hope this helps.
[SuperSU] fiverings:
I updated to 8.1 and removed the security code and fingerprint. Then fastbooted the previous twrp and previous twrp installer. Booted phone, Pixel XL, booted recovery, twrp, flashed SuperSU sr5 booted phone, checked for root, booted into twrp, flashed suhide 109 and everything is fine, I'm certified and pass saftey net. I'll use the new twrp when they fix it or fix super su.
[SuperSU] Homeboy76:
I agree, After flashing twrp 2.3.1-0 booted recovery to check if twrp 2.3.1- 0 was installed then flashed SuperSU and booted system. No root. :(

---------- Post added at 02:07 AM ---------- Previous post was at 01:58 AM ----------

You are using TWRP 2.3.0-0. img and zip with SuperSU v2.82 SR5 and suhide v1.09. :)
[SuperSU] Mzprx:
I think SuperSU is not open source... But if someone do that CCMT may wake up...:) I also do not have such skills.

---------- Post added at 07:41 AM ---------- Previous post was at 07:38 AM ----------

Well, they had 2 years to step in... And they didn't. Maybe they have it as New Year resolution :)
[SuperSU] arunwa:
Supersu and king root

Hi, what is the good Supersu or kingroot for root Huawei phone?
[SuperSU] okgnew:
SuperSu on Essential Phone

I can't install latest SuperSu on Essential Phone via TWRP.

It fails and aborts on sepolicy patching.

Full recovery.log attached.

I see the below messages in the log:

- Patching sepolicy
sukernel v2.82 (ndk:arm64-v8a) - Copyright (C) 2014-2017 - Chainfire & CCMT
Loading from [/sutmp/ramdisk] ...
Could not locate entry
sukernel v2.82 (ndk:arm64-v8a) - Copyright (C) 2014-2017 - Chainfire & CCMT
Loading from [/sutmp/ramdisk] ...
Could not locate entry
sukernel v2.82 (ndk:arm64-v8a) - Copyright (C) 2014-2017 - Chainfire & CCMT
Loading from [/sutmp/ramdisk] ...
Could not locate entry
--- Failure, aborting
umount: can't umount /su: Invalid argument
[SuperSU] v12xke:
No idea... maybe you should just start using Magisk?
[SuperSU] Josh:
I also got problem with Super SU latest version on my Nexus 5x after flashing in latest TWRP release. Then i install app from app store reboot (not in TWRP) after that has bootloop- turned off phone- reboot to recovery flash Super SU again and voila ,it works! In every 8.1 stock or custom ROM.
[SuperSU] :
Depends on how it's installed

Not to do with recovery here it just temp losses root a reboot fixes it
[SuperSU] Alxoom33:
See my post in the TWRP for the Pixel 2 XL thread.
[SuperSU] srqrob:
deleted
[SuperSU] The Analog Kid:
A few days back SuperSU v2.82 SR2 started either crashing or stopping when trying to get logs from the app AND when scrolling up/down SuperSU settings. Updated to SR5, but it didn't fix the issue. I have this logs from "Apps2SD" and have a full collection from "Cracker" as well Any hint?
[SuperSU] The Analog Kid:
These are from Cracker:
[SuperSU] Alxoom33:
It will be difficult to help you within knowing more details about your phone and setup.
[SuperSU] KaMyKaSii:
You may have activated full content logging in SuperSU and this is one of the apps that "spam" multiple commands. You can get the SuperSU data and see if the size is above normal. If so, it happened to me once. In this case you can disable logging for the particular app

https://xdaforums.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133/post70737690
[SuperSU] The Analog Kid:
Well it's Moto G4 Plus on stock 6.0.1 OS... You mean SuperSU setup?
[SuperSU] The Analog Kid:
No, actually I haven't set "full content" or per app logging...
[SuperSU] Alxoom33:
Use SU uninstaller from [MENTION=1143630]osmosis[/MENTION]. Then reinstall SU Superuser v. 2.82 SR 5 in TWRP.
[SuperSU] The Analog Kid:
Already did so using SuperSu app. Didn't work. Right now I'm looking for [MENTION=1143630]osmosis[/MENTION] uninstaller. Haven't found it yet...
[SuperSU] Alxoom33:
He has an XDA thread.
[SuperSU] Locura18:
https://xdaforums.com/showthread.php?t=2239421&page=159

There's the thread
[SuperSU] martyfender:
https://xdaforums.com/showpost.php?p=63615067
[SuperSU] miksontije:
Im flashed 8.1 abc on n5x with twrp 3.2.10 and i lost superuser aplication from phone. It looks phone is rooted bcouse i can run tb or i can go into system,but there is no superu aplication nowhere on phone. Does anyone have same error?

Merry Christmas!
[SuperSU] elotan:
Can you please provide a link to that post?
[SuperSU] jcmm11:
Extract the superuser.apk from the superuser install zip and side load it. It's in the "common" sub-directory.
[SuperSU] Alxoom33:
https://xdaforums.com/showthread.php?p=74932513

Here you go.
[SuperSU] 93fuelslut:
How do you extract the boot img from your rom zip via rom toolbox? I don't see the img file
[SuperSU] Alxoom33:
Use Root Explorer, it file explorer in Toolbox, use extract all and go to the extracted folder. It's in there!
[SuperSU] elotan:
Thanks, I will have a look.
[SuperSU] Angry_ATC:
Somebody did.

It doesn`t help too. Disk digger pro detected only a pieces of some damaged mp4`s but nothing connected with lost videos, which was mistakenly deleted just only about 3 months ago. So sadly :(
[SuperSU] jcmm11:
If they were deleted 3 months ago just kiss them goodbye. They're gone.
[SuperSU] ashyx:
You need the pro version on a rooted device to have any hope of recovering anything.

It is pretty good at recovering data. If it isn't able to recover much then it's probably gone.

The other option is to create an image of the partition then use a windows recovery program that can do a deeper search.
[SuperSU] jekyll530:
Has anybody tried to use 2.82-SR5 on OnePlus 5 official Oreo? I tried and successfully flashed SuperSU but stuck au splash screen (not boot animation). Anybody succeeded? Thanks.
[SuperSU] Angry_ATC:
It`s completely done - pro on rooted samsung.
[SuperSU] sansanc:
Ah yes should have paid more attention. What's wrong with your post quotes? Anyway, i installed magisk, works now...
[SuperSU] a g bell:
So what is the update situation now with SuperSU ?is just going to slip away or will we see some update soon?
[SuperSU] Bobbaloo:
I'm afraid it's probably the first choice
[SuperSU] a g bell:
Yeah l feared that ☹️
[SuperSU] Bobbaloo:
Hey, I'm not sure but I'm thinking of making the switch soon
[SuperSU] a g bell:
Yeah but those modules for everything ?
[SuperSU] Bobbaloo:
Well, ain't nobody gonna accuse me of being too old to learn new tricks

°/___\°
[SuperSU] Alxoom33:
Coming over to the Dark side, you are?

https://photos.app.goo.gl/31WjmRj7i6wlTUss2
[SuperSU] a g bell:
Strange l see no link to this here

http://forum.supersu.com/

Do they want to hide it from us for some reason ?
[SuperSU] Alxoom33:
What are you looking for?
[SuperSU] Ch3vr0n:
Actually that site is legit. It was created after the takeover. Though I don't see much going on there either, even the forum is filled with trash. Take a look at the 'help me now' section. It's full of 'diploma spam' by Asian type spammers.

Sent from my Nexus 6P with Tapatalk
[SuperSU] Mzprx:
Yeah... To tatooine (or I hope more hospitable place) I think the last jedi retired:) . Hmmmmmm
[SuperSU] Alxoom33:
Unfortunately, I agree. Already have my phone, Pixel 2 XL on Magisk, and I will move on from SuSuperu on my Pixel C when I receive the January update. [emoji26]
[SuperSU] peterlee928:
unfortunately im prob in the same boat. quick question on magisk - can i use tibu and busybox with magisk? if so, then bye bye supersu :(
[SuperSU] gothicVI:
Clear yes on busybox. Never used tibu, thus no comment on that.

Gesendet von meinem Moto G 2014 LTE mit Tapatalk
[SuperSU] hokiealumnus:
TiBu works fine with Magisk. I use it all the time. There is a busybox Magisk module readily available to download via the Magisk app.
[SuperSU] casouzaj:
I have both of them installed in my Sony Xperia Z3 Compact running CarbonROM (BusyBox as a Magisk module, though) and they work great under Magisk v15.1.
[SuperSU] peterlee928:
awesome! i had read somewhere that magisk and tibu are not compatible. glad to hear that that is incorrect. :)

EDIT

so here is what i read elsewhere... is this incorrect?

"However, Magisk's built-in root management system will not allow you to modify files on the Pixel or Pixel XL's system partition. This means that certain apps, like Titanium Backup, will not work properly with this root method."
[SuperSU] hokiealumnus:
I'm not sure where that come from, but my app restore from yesterday's ROM install on my Pixel XL (and all of the ones since Magisk has been released for the Pixels back in February/March'ish of last year) beg to differ with the assertion. I build ROMs, so I am constantly having to wipe & perform clean installs. I'd go insane without TiBu.

I can also access and modify/add/delete/change permissions on system files using FX file explorer without issue. Some file explorers do have issues with Magisk & Pixels, that's a known problem, but I've always used FX and it has always worked.

Edit - Added screenshot, works fine on Pixel XL, 8.1, Magisk.
[SuperSU] peterlee928:
so i use tibu to restore/back up app data, other data (texts/phone logs/wifi connections), and freeze system apps. all that is doable via magisk?
[SuperSU] hokiealumnus:
Yep. I added a screenshot go my post above of a happy TiBu just taken a minutes ago. It has full functionality. EDIT - It has full functionality *as far as I can tell*. I have never backed up anything besides apps & app data. I have frozen system apps without issue though.

As a side note, I want to be clear that I would NOT be having this conversation if chainfire were still developing SuperSU. The only reason I am responding in what would otherwise be a rude intrusion into this thread is because (it appears) the company that bought it isn't interested in supporting it at this time. Mods please feel free to move or delete my posts if they aren't kosher.
[SuperSU] Ibuprophen:
Thank you very much [MENTION=4936949]hokiealumnus[/MENTION] :)

It appears that CCMT (aka [MENTION=7678190]SuperSU Release[/MENTION] on the forum) won't support anything on the xda-developers forum at all.

Please correct me if I'm wrong [MENTION=631273]Chainfire[/MENTION] but, based on what I've seen, I really don't believe that CCMT realizes that the xda-developers forum is where SuperSU had gotten its start and had grown to where it is now.

CCMT also should take under consideration how strong of a community that the xda-developers is and can potentially impact the SuperSU in a negative way if they continue to ignore the primary fan base here.

I can also understand where Chainfire is coming from too. I've got a feeling that he's tried (possibly on multiple occasions) to let CCMT know this. As always, Chainfire still has my support since he's always provided excellent support to the end and its CCMT that has lost my support.

I, personally, will continue to use SuperSU as long as it still works for me but, like a bad habit, I'll stop as soon as it no longer works for me.

I just feel bad for those members here that are having issues with it on their devices.

Anyways... Have a Happy New Year Everyone!!!

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

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

PLEASE KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
[SuperSU] vandyman:
I agree completely, but it is a shame for the people that paid for the pro su app like myself. I paid for the app for the support.
[SuperSU] mobileman88:
I use tibu with Magisk for the past year just fine. There is busybox module within Magisk you can simply download and use

---------- Post added at 05:16 AM ---------- Previous post was at 05:14 AM ----------

I restored my nexus 6p tibu backup on a pixel just fine nothing to worry about
[SuperSU] Boriar:
Well, Chainfire never let alone people who only have the free app. I also bought the pro version but only like a way to say thanks for all his support here.

I will use it until stop working because it's the most stable option at the moment.
[SuperSU] peterlee928:
likewise - i shouldnt be having a magisk discussion in a supersu thread. only because of the current lack of support for supersu from the new owners. and other (semi?)noobs like myself can at least know other options and compatibility :)
[SuperSU] badhabit_wb:
Time passes and things change. I paid for the premium but feel like it was a bargain over the years. We have an alternate that works fine, magisk, and I for one am thankful for that. Chainfire did a great job time will tell if CCMT continues to support supersu or it fades into the past.
[SuperSU] vandyman:
I have done the same as you to say thanks. But I was making a point. Do not buy the paid version at this time, you will get what?

What do you get for the Pro version as of right now..??

Honestly, all the apps that I use from Chain fire are paid apps. Example ; Flashfire.

All the apps that I use on system are paid apps, supported the developer..

Examples ; Titanium Pro, Busy box pro, Root explorer pro,..........
[SuperSU] Mzprx:
Interestingly CCMT has link to XDA at the bottom of the SUperSU official website pages, but apparently they have no intent (so far) to participate or even read the discussion.