yashsingh1/xdaforums huggingface dataset:
[SuperSU] comat0se:
On a Pixel XL

I'm having trouble getting SR5-2.82 installed with TWRP 3.1.1-1. I had it previously working with TWRP 3.1.1-0. Once I tried to flash 3.1.1-1, initally I had the problem of it returning to recovery.

Now I've:

flashed stock boot.img to both slots

fastboot boot twrp 3.1.1-1

install twrp 3.1.1-1 zip

install ElementalX-P-2.02

then install SR5-2.82 SuperSU.

Everything seems to work normally, but when I look for the SuperSU app in the app drawer it's not there.

TWRP and Elemental are installed properly.

Suhide and Flashfire can't detect root, but other apps like Titanium and RootChecker show it present. Oddly, safetynet passes. Is suhide somehow installed still?

deleted /data/adb/su/suhide

Any ideas? I've even flashed the flash-all.sh script without the -w flag... can't seem to get full root anymore.
[SuperSU] JakeDHS07:
Sounds like you may have them hidden which was a feature of SUhide. Try hitting the volume up then volume down buttons three times in quick succession. That should add them back to the app tray.
[SuperSU] comat0se:
That was it... hours of my life wasted. I reinstalled suhide through twrp, then used the key combo. Thanks!
[SuperSU] JakeDHS07:
No problem. Yeah it was added because some apps can detect the SU application and then not work so this allows you to enable root for certain application then hide the actual SU apps while maintaining root for the already granted applications. But the implementation made it easy for those unaware to accidentally hide the apps imo. Glad I was able to help.
[SuperSU] mahefooz4u:
Built TWRP for Xiaomi Mi A1 - Android One phone with similar partition structure as Pixel.

1. If I boot twrp and flash Supersu, SuperSU working fine.

2. If I boot twrp, flash twrp installer, twrp is fine. But if I flash SuperSU, TWRP is gone, but SuperSU is working fine.

If I flash supersu, TWRP is not working.

TWRP and SuperSU are not coexisting. Any help?
[SuperSU] NLBeev:
You didn't mention what version of superSu you used.

My first suggestion is therefore use superSu 2.82 sr5.

Your issues has nothing to do with coexistence.

Your need a modded kernel that doesn't restore the stock recovery.

The recent versions of superSu patches the kernel, but a standard or gzip kernel is needed.

You tried already several sequences. Probably Xiaomi uses a different kernel type.
[SuperSU] mahefooz4u:
I'm using 2.82 SR5 is it is the latest one for pixel devices. Still I'm facing the same issue. Actually it is not restoring stock recovery as well. No recovery is coming up after flashing SuperSU.
[SuperSU] NLBeev:
That confirms my idea that the Xiaomi kernel is not standard Android.
[SuperSU] mahefooz4u:
I shouldn't mention here but Unofficial Magisk v13.4 specifically built for Pixel devices is working fine. The reason to mention this is to find out if there is any way to make SuperSU work.
[SuperSU] ravinder0003:
Yaah I also flashed the same...

I guess if SuperSU and Unofficial magisk, both zips are patching boot.img and one is breaking twrp, other not!

Then seems as if twrp-installer zip and SuperSU both zips are standing against each other...

Same issue is with magisk official beta zips...
[SuperSU] avijwr:
Or u can do one more thing...install twrp from playstore ...its an apk which can do same tasks as twrp does in recovery mode....its official app by twrp...i didn't use it but i think it will be solution for u
[SuperSU] DB126:
Flashify (also available via Play Store) is another option. Been around for awhile and is well regarded. Free and paid varients.
[SuperSU] ravinder0003:
We have temp solutions for Mi A1 like using that old unofficial magisk zip for root by [MENTION=2461994]goodwin_c[/MENTION]...

Looking for a solution to have SuperSU and twrp together...
[SuperSU] avijwr:
Yep...or install twrp recovery image or cwm from flashify.....
[SuperSU] osm0sis:
[MENTION=631273]Chainfire[/MENTION], I wanted to bring to your attention a couple of issues we've noted with your zipadjust signing method over in my Complete Shell Zip Documentation thread:

https://xdaforums.com/android/softw...shable-zip-t2934449/post74205160#post74205160
[SuperSU] ventil00:
Xperia Z1

I installed it on my Xperia Z1 and it works fine.

Thank you very much
[SuperSU] supermaus100:
Is the version synonymous for the sony xz premium?
[SuperSU] minhducsun2002:
Just curiosity, what's the syntax of Google's SU binary? I've only known its existence through How-To SU (if I remembered right). May I ask you this, [MENTION=631273]Chainfire[/MENTION]?
[SuperSU] iwearthebelt:
Suhide lite v1.09
[SuperSU] amir7777:
Is the latest version of superSU working with 8.1?
[SuperSU] Alxoom33:
Didn't know 8.1 is out in the wild.
[SuperSU] amir7777:
It was released just today, and to answer my question just tested it and it works.
[SuperSU] Alxoom33:
Where are you located? I checked my Pixel C and the current Google APIs for Android and I don't see it. How did you get the update?
[SuperSU] osm0sis:
http://www.androidpolice.com/2017/1...loper-preview-final-release-planned-december/

Also, check the main AP site for tons of features coverage. :good:
[SuperSU] TonikJDK:
How did you get SU in? Boot to TWRP seems flakey. People are reporting pin doesnt work.
[SuperSU] amir7777:
I installed the update with WugFresh toolkit without deleting my user data and then flashed TWRP with fastboot. After that it boots into the recovery and then I flashed the latest SuperSU.

I'm not sure what pin you're talking about, if it's the one that appears before booting into the OS, I had that disabled.
[SuperSU] TonikJDK:
That was what I needed, tyvm.
[SuperSU] Alxoom33:
I thought I was still enrolled in the Beta program. Updating my Dragon [emoji41]
[SuperSU] akaMETEOP:
Can i use it at tvBox?
[SuperSU] CamoGeko:
SuperSU v2.82 SR5 working fine for me on Onyx and Unofficial DU 11.7.1 (Android 7.1.2), thanks as always!
[SuperSU] Ibuprophen:
That all depends on what exactly you have.

If your TV Box is able to be Rooted, and SuperSU can be installed, then there should be some type of thread outlining this within some area of the Forum that's specific to your TV Box.

The following area of the forum is one example of this and does have threads pertaining to Rooting and installing SuperSU for certain TV Boxes.

https://xdaforums.com/android-stick--console-computers

I hope i had explained it okay via text... :)

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] Xdevillived666:
Anyone tried this on 8.1 Dev preview?

---------- Post added at 10:09 AM ---------- Previous post was at 10:08 AM ----------

Yeah but it's a *****
[SuperSU] DocteurN:
Yes see previous page, working for someone :laugh:
[SuperSU] kevtrysmoddin:
Yes it works but crashes sometimes but I've have no issue on 8.1
[SuperSU] panamera2011:
Hi guis, I upgrade Nexus 5X to 8.1 preview but when update SuperSU from Play Store I get bootloop. How can fix it? Thanks [emoji846]

Nexus H791 using Tapatalk
[SuperSU] jcmm11:
Try flashing the zip from the OP of this thread. It's newer than the Play Store version.
[SuperSU] panamera2011:
I flashing zip in the OP by Chainfire but when open SuperSU app ask me to upgrade. If you upgrade get bootloop :)

Nexus H791 using Tapatalk
[SuperSU] ffejy462:
2.82 sr5 is the most current. There isn't anything to update after that....
[SuperSU] panamera2011:
I know, but it's really strange when open the app ask me upgrade. Ok I try not upgrade to see if it works the same. Thanks

Nexus H791 using Tapatalk
[SuperSU] Ibuprophen:
I just checked the Play Store and it reflected v2.82... That is weird...

Maybe the next time you have to flash it, you could try downloading it again as a "just in case".

There shouldn't be any update notification if you use either the SR5:

http://download.chainfire.eu/1220/SuperSU/SR5-SuperSU-v2.82-SR5-20171001224502.zip

Or the use of the Stable:

https://download.chainfire.eu/1113/SuperSU/UPDATE-SuperSU-v2.82-20170528234214.zip

Though, the SR5 is a Service Release and not considered a Stable one.

This is just a personal opinion/suggestion.

It's funny that since [MENTION=631273]Chainfire[/MENTION] had, unfortunately, retired... I don't see [MENTION=7678190]SuperSU Release[/MENTION] (CCMT) making any contributions on any of the threads to support SuperSU at all. All that I've really seen is a thread post statement/announcement.

CCMT wants members to put their trust in them but, I haven't seen any contributions for building that trust.

Though another personal opinion but, am I wrong?

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

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

PLEASE KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
[SuperSU] DEVILOPS 007:
For some reason, even after a clean flash and installing the apks manually there is no suhide or SuperSU app available in my app drawer but I still have root access. I'm on Oreo nitrogen ROM nexus 6p. Can someone help me please? Thank you!
[SuperSU] corkiejp:
[MENTION=7494055]DEVILOPS 007[/MENTION] If after flashing the supersu zip and there is no app present. You can find the apk in the common folder of the zip, just install the app.
[SuperSU] DEVILOPS 007:
Tried installing it like that and it doesn't work. I also checked play store and it said to install it. I installed it and it then said install again like it had never been installed. I have no clue what is going on. Thanks.
[SuperSU] DEVILOPS 007:
See here. See the from version bit at the top.
[SuperSU] TonikJDK:
Regrab the download, there were some issues and he rereleased s5, the version prior to the current posted one caused this. Bet you have an old copy.
[SuperSU] DEVILOPS 007:
Nah, didn't work unfortunately. The bad thing is that I can't grant any new apps root permission but can continue to use apps that I granted root permission in the past. It's like it's a system app that can't be used or accessed but just knows what apps I granted before it went. Any ideas? I don't want to have to switch to magisk.:crying:
[SuperSU] corkiejp:
Custom Nitrogen rom probably has it's own builtin root? Did you disable or remove that root before trying to install supersu?

Had a look at this thread and for that device it doesn't seam to have a builtin root. May try posting in that thread to see if anyone else has problem rooting?

Google it or [MENTION=4544860]osm0sis[/MENTION] has scripts that can remove builtin root from some roms,
[SuperSU] DEVILOPS 007:
Hi thanks. The root doesn't come with built in superuser or any root like some do. I tried one of osm0sis' scripts called unsu and have tried other methods like not flashing anything extra and clean and dirty flashing. I'll see what people in the nitrogen thread say. Thank you.
[SuperSU] KaMyKaSii:
Try this:

If SuperSU opens, try going into the customization settings, make the icon invisible and then undo this
[SuperSU] panamera2011:
I have tried twice with SuperSU without success. Maybe the partition 8.1 is different from 8.0. I solved with Magisk 14.3. Thanks [emoji6]

H791 using Tapatalk
[SuperSU] osm0sis:
Just updated unSU the other day actually with support for SBINBIND SuperSU, Magisk and LineageOS addonsu. :D

Full changelog (and lots more flashable goodness) in my Odds and Ends thread. :good:
[SuperSU] DEVILOPS 007:
Hi, had to go for a bit. Unfortunately your suggestion didn't work so I decided to try magisk to see what happened as soon as I booted with magisk root the SuperSU app showed in the app drawer. The hell's going on?! I know Oreo and some custom ROMs are working better with magisk so I might stick with this for now.
[SuperSU] harryohh:
I have the exact same issue.
[SuperSU] Alxoom33:
Yes, worked fine on the Pixel C.
[SuperSU] Alxoom33:
Anyone have any luck rooting the Pixel 2 XL?
[SuperSU] Badger50:
Not yet.....unfortunately! :crying:
[SuperSU] Itachisasuke:
Negatory. Patiently waiting for TWRP and root. Some good information has been collected about the partition structure and compiled over here.
[SuperSU] mymistake:
also had a bootloop on 8.1, after flashing v2.82 SR5 phone boots okay until you go to the supersu app and it asks you to update binaries, updating binaries results in bootloop

--- update: i installed the app found in the zip > common and everything's working fine now :) thank u!!
[SuperSU] grimmaniac:
After updating the binaries reboot into TWRP and reflash 2.82 SR5. This fixed the bootloop for me.
[SuperSU] anuraj1:
An alpha bootable TWRP was released today for Pixel 2 and 2 XL: https://plus.google.com/u/0/+DeesTroy/posts/dUd6Mf2VPEv
[SuperSU] bggold:
I was able to push SuperSU sr5 to /data with the Alpha build of twrp for pixel 2 xl and flash it successfully (no errors) But phone just boots back to bootloader. Flashed boot.img to a/b and phone boot back normally. Looks like SuperSU is going to need some work. Let's hope the group that took it over can figure something out soon. Maybe chainfire will take a last stab at it.

Running 8.0
[SuperSU] slothdabski:
I tried flashing SR5-SuperSU-v2.82-SYSTEMMODE.zip on pixel 2 XL via TWRP. It flashed and the phone booted, but root was not detected by SuperSU app
[SuperSU] tobitege:
[MENTION=5192674]itechengine[/MENTION]: in recovery you have to repeat re-flashing SuperSU and wipe cache and reboot; boot phone again normally, open SuperSU and it might ask to install an extra script and confirm that and reboot. Ideally this should only be needed once, but read from several users in the LG G3 forums that they had to do it multiple times (unless they did it wrong in the first place).

Another way: if you can get any file browser to work with root (or in TWRP), try going to /system/bin/.ext and remove file ".su" and reboot and open SuperSU again to have it recreate it and reboot again before using Titanium.
[SuperSU] itechengine:
Hi, I have tried using both methods you have mentioned exactly the way they are written, TB asks for the root permissions when i try to launch but even after granting them, it says Root Access failed.
[SuperSU] tobitege:
Open SuperSU -> Settings and disable the option for "Mountspace separation", reboot and try again Titanium. If that and the previous does not work, than something else is wrong...
[SuperSU] tobitege:
No problem, glad you figured it out! :laugh:
[SuperSU] jmdearras:
N7 2013

Loaded 5.01 full image, TWRP, and then the 2.39 zip. Worked perfectly, no issues at all :D
[SuperSU] SamuriHL:
Confirming that 2.39 works great on the S4 GPE 5.0.0 build.
[SuperSU] kamilmirza:
v2.39 solved all root problems on lollipop ?
[SuperSU] AndiVienna91:
Hey Guys !!

First of all: THANK YOU so much for all your hard work !!

Im running the polish Lollipop on my Galaxy S5 and i have no problems with root since i have installed the 2.39 beta.

But...whatever i try...i cant run apps like "link2sd" or "foldermount" without an error. With link2sd i have no problems if i try to delete an system-app...but if i move an app on the sd card it crashes and after rebooting my galaxy the moved app is gone. Same thing about "foldermount" if i move some files from an app...the app crashes and i have to reinstall it.

Some people say that must be an error with the root...because link2sd is already updated for android 5.0.

Can somebody here tell me if you can run link2sd without an error...or gets everyone with an galaxy s5 and lollipop the same issue ??

What would you say...is the problem by the root or by link2sd or foldermount ?? (SDCard is multiple times formatet and partitioned...and on 4.4.2 i never had a problem like this)

THANKS !

(I´m so sorry for my bad english )
[SuperSU] beton87:
Again from OmniRom 5.0.1 on OPPO Find7a with LVM. Backup script does not work. After Rom update I have lost root. Supersu displayed error there is no binary file. After reflash it is working again, but in SuperSu settings it is shown that backup script is installed.
[SuperSU] Chainfire:
The backup script is not ready yet for 5.0. Still some issues to solve there.
[SuperSU] Marius D.:
Su Binnary

How can i copy the binary file in the xbin folder?i cant change permissions to that folder to get it copyed there....it says superSu cant find any binary file
[SuperSU] tobitege:
Why copy it manually? Just flash the ZIP from recovery... or do you need something special?
[SuperSU] JulianJenner:
Original link is working: download.chainfire.eu/638/SuperSU/BETA-SuperSU-v2.39.zip

Redmi Note 1W Enhanched / MIUI 37.0.0 Stable Multilanguage / Tapatalk Pro 4.6.2
[SuperSU] Carpe Noctem 11:
v2.40

No problems with v2.40 :good:
[SuperSU] Lightphaser:
I am too having this issue as well with SuperSU 2.40

Edit : I think disabling Tapjacking protection fixed it
[SuperSU] my2sense:
I normally have this issue when running an screen overlay program like Lux or twilight. You probably can't press install when installing app either. Just disable it, press deny/grant and re-enable it again.

If you're not running anything like that then ignore the above :)
[SuperSU] Lightphaser:
This must be it since i am also using Lux :) Thank you to have cleared this up, did several wipe trying to figure why, the thing was driving me crazy !

However i have no issue installing app from apk so disabling tapjacking protection in supersu sertings did the trick for me :good:
[SuperSU] TTA1326:
I'm a 20+ year Microsoft stack developer, and Android dumb lol. But, access to build.prop requires root to get pass 'ro' permissions right? I was just wondering if somebody can get write access to that file via temp TWRP and remove the provisioning setting. That would let us tether, unclinch and lot of people, and make it easier to wait on the rest to happen in due time. I guess I need to learn Android...
[SuperSU] bggold:
You should be able to pull the file with adb. Before you push it back change the permissions within twrp.

Have not tried
[SuperSU] martyfender:
A lot of that depends on if a twrp was ported to your device. You didn't mention which device and android version you have for some more knowledgeable member to help you with. If you can boot it into temp twrp, you can backup the boot.img and edit the build properties, fstab, init.rc, etc., in Android Image Kitchen, then repack it and flash it in twrp. you can also use twrp to flash supersu or magisk to root your device, most likely. Much of this will be dependant on your device and android version though. If there is an xda forum for your device, please consult it concerning rooting it and to enquire if twrp or other custom recovery has been ported to it.

Others may have additional thoughts or correct me if I have something wrong.

I stand corrected, it is default properties one can edit with Android Image Kitchen, in the unpacked boot.img. I do believe though, as the above user stated , that you still need twrp or temp twrp for your device to do this and or root or adb root to be able to pull it. If you can get root, you can use a build property editor to do this.

adb shell
su
adb pull <path-of-the-file>

here is a few links I found on using these commands:

http://www.droidviews.com/push-pull-files-android-using-adb-commands/

https://www.androidauthority.com/android-customization-transfer-files-adb-push-adb-pull-601015/

http://adbshell.com/

Other, more knowledgeable members, may have better information on doing this.
[SuperSU] marc.ientilucci:
[MENTION=631273]Chainfire[/MENTION] I have a Pixel 2 and tried flashing this with the newly released TWRP alpha. It was unsuccessful and reboots into bootloader.

I've attached logs from TWRP

please let me know if I can assist with getting this working.
[SuperSU] cjkacz:
I believe [MENTION=631273]Chainfire[/MENTION] has retired. But I love that Avatar!! #billsmafia
[SuperSU] marc.ientilucci:
I forgot :(

do you (or anyone) know if CCMT has any means of open communication?

Much appreciated!
[SuperSU] osm0sis:
They have their own supersu.com forums which I think they'll probably be a little more active on, but that's a hunch; I haven't looked at them, and I don't think many will. Really, xda is SuperSU's birthplace and its livelihood, so they need to bite the bullet, choose a new front person, and get them on here, full time, yesterday. This is their first big challenge without Papa Chainfire to directly run the show and they need to get it right.

[MENTION=7678190]SuperSU Release[/MENTION]
[SuperSU] vandyman:
Well if there is no more support for Supersu, I guess it is done. (?)

[emoji23]
[SuperSU] xell75:
So, is it worth then to still use SuperSU when there is no active development more? And I not really trust some random chinese company that will defenitly not improve SuperSU more really. Without Chainfire SuperSU is going to die :(
[SuperSU] slothdabski:
I don't trust it. Shady AF
[SuperSU] gothicVI:
Magisk is a perfectly suitable alternative and it's open source - for all people who can't wait until there's eventually some note from the new owners of SuperSU.

Gesendet von meinem Moto G 2014 LTE mit Tapatalk
[SuperSU] xell75:
So long I'm still be able to modify the system partition, I should give it a try.
[SuperSU] slothdabski:
You can
[SuperSU] xell75:
Good, so I'm on a Galaxy S4 with Android 8, can I simply uninstall SuperSU, flash stock kernel again and then flash Magisk? And what do you recommend, a Beta Magisk or the Stable? :)
[SuperSU] slothdabski:
Regular should be fine. Beta only benefits new devices with A/B partitions
[SuperSU] xell75:
Thanks mate! I try!
[SuperSU] martyfender:
I tried the last 2, before the current final release of Magisk on my Nextbook Ares 8A, Android 6.0.1, x86, tablet and before a day was out, I lost root with it, several times, that was only solved by rebooting the device. So I reverted to back to Supersu latest SR release, in systemless mode, at the time. I have never lost root with Supersu.

I also have an older Nextbook Ares 8, Android 5.1.1, x86 (originally came with 5.0) tablet that has had every version of Supersu since about 2.46, betas and all and it has worked flawlessly in system mode on it also. Loosing root is not exceptable.

And , no, in case someone asks I did not save or provide logs to [MENTION=4470081]topjohnwu[/MENTION]

but I probably should have, but was busy at the time and just needed root to work, without question. Since I have 2 ares 8A tablets, I may eventually try the lastest release or the current beta. I have, from time to time been following both the release and beta threads of Magisk.

I believe the second time I tried Magisk, was after a clean install of my ROM also, from a nandroid backup which has userdata and cache, deleted by fastboot commands.

So the bottom line is, I will stay with Supersu until I see Magisk is more stable and works reliably on more devices. Yes, I have read [MENTION=4470081]topjohnwu[/MENTION] thread on troubleshooting Magisk and may have tried many of those things, such as flashing an original, virgin boot.img, to my device

If anyone has any thoughts on what I have said, please don't hesitate to respond.
[SuperSU] gothicVI:
That's a known issue that should be solved with the current beta if I remember correctly.

Gesendet von meinem Moto G 2014 LTE mit Tapatalk
[SuperSU] martyfender:
I may try it on one of my tablets, not sure yet. Also, in one of the threads, there is a link to a version that someone compiled from the source, with the lastest commits included with it.

https://xdaforums.com/apps/magisk/unofficial-magisk-v10-beta-built-t3521901

I know we are now getting off the topic of Supersu, but seems relevant if the current developers of Supersu don't live up to the task.