yashsingh1/xdaforums huggingface dataset:
[SuperSU] jcmm11:
Just the boot image? You don't care about anything else? Simplest way is probably to extract the boot image from the PN install zip and then just apply that via TWRP.

If you want to completely unroot then I'd probably just flash the unsu script by Osmosis.
[SuperSU] jugoslavpetrovic:
I actually tried that. Root seemed to be gone but when tried to flash magisk latest 12.0 during flesh it detected SuperSU patched boot but even after flashing boot.img from rom the same thing. I dont how is it possible.
[SuperSU] Ibuprophen:
Here's a link to the "osm0sis' Odds and Ends" thread where you can find something called "unSU script" that is supposed to be able to remove SuperSU and, i believe, restore the boot.img.

https://xdaforums.com/showthread.php?t=2239421

I can't honestly endorse anything from osm0sis since I've never had the need to try anything developed by this member.

BUT, osm0sis does have a very good reputation for his developments.

If you have any questions regarding any of osm0sis developments, then post it in there and I'm sure someone should be able to assist you further.

I wish you the best of luck!

Sent on my Communicator [SCH-I535] from the Bridge of the U.S.S. Enterprise...
[SuperSU] traycold:
hi, I've exactly your same problem, i.e.: when SuperSU is set to grant always root access -> everything ok; but when set to "prompt" -> no prompt appears and therefore root access is never granted. Also, the tab apps/log is always empty.

Except for this, everything is ok.

I already executed the steps mentioned in your post but the problem is still present.

I tried also "usual" steps like: clean delvik / cache; reinstall SuperSU; check notification setting for App SuperSU.

Do you have any clue?

I'm on MM, with Yotaphone 2 stock rom (+twrp recovery +xposed last version).
[SuperSU] RootCheckM8:
Is there any way to root the Moto g3 running Lineage OS on android 7.1.1?
[SuperSU] Ja_som:
When you have LOS, why you do not flash su zip from LOS?
[SuperSU] RootCheckM8:
Since it's a different operating system, I thought that there would be a different process. I guess not.

Thanks.
[SuperSU] DB126:
Err...why not just enable native root (manager) under developer options? SuperSU is not needed with most LinOS builds.
[SuperSU] RootCheckM8:
On the build that am using, it's not natively supported. I actually just rooted my device hours ago. Problem solved. I went to the Lineage OS website and downloaded the supported SuperSU.zip file and its removal tool if I need it.
[SuperSU] ulxerker:
Deleted.
[SuperSU] Devilix:
Somebody use SuperSU in systemless mode passing safetynet test?

Is there anyone here?
[SuperSU] KaMyKaSii:
In addition to SuperSU systemless, you need Suhide. But it does not work on roms with November or higher security patch. And if you have installed Xposed (systemless or not), forget to pass safetynet check (at least with it active)
[SuperSU] momotothek:
Not working on Alcatel Pixi 4 8050D

I flashed the latest SuperSU (v2.79) with TWRP on my device. After reboot and opening SuperSU app, it says update to the latest version needed and no root. Pls help. Thanks.
[SuperSU] culiacanazo:
Thanks for all you've done!
[SuperSU] ulxerker:
did you try SuperSU v2.79 SR3, too?
[SuperSU] tomwuttke:
I had the same problem-- trying to install 2.79 release on to a 7.1.2 pixel xl using twrp would not root/install all the way.

Using 2.79-sr3 worked :good:
[SuperSU] momotothek:
Yes I've tried it with SR3 and tried to flash with both TWRP and CTR. Still not working :( It still says update to latest version after I open the SuperSU app. I'm on the Alcatel Pixi 4 8050D Device. Thanks for your help!
[SuperSU] Bakuryu42:
I I had this side loaded or installed during a flash can I still install it from the store swo it updates or is more up to date? It says its 2.79, so I don't know if it needs to update anything I just don't want to mess it up by installing the store one over it.
[SuperSU] utkarshpant:
Does it work on Moto E condor running 7.1.1?
[SuperSU] DB126:
Should be ok unless you flashed 2.79 SR3; in that case I would wait for stable update to hit Play Store (will likely be christened 2.80 if/when that happens).
[SuperSU] Ibuprophen:
To be honest, about 6 months ago, i had flashed the Stable 2.79 over the SR3 to confirm if it would work for other reasons, and it worked fine for me.

I'm not stating that it will for everyone's device but, wanted to just let you know that it worked for me.

When I had compared the 2 flash files, i had a feeling that it should but, I just wanted to confirm it for myself.

Sometimes even the best of Dev's tries something out to confirm, one way or another, whether or not something works that should/could. And many have taken their lumps too as I've done on more than one occasion LMAO!

Sent on my Communicator [SCH-I535] from the Bridge of the U.S.S. Enterprise...
[SuperSU] Bakuryu42:
Is there a way to tell if its 2.79 SR3? Would it say that instead of just 2.79?
[SuperSU] Ibuprophen:
When you open SuperSU, and go to the Settings tab, the version is located on the very top.

Sent on my Communicator [SCH-I535] from the Bridge of the U.S.S. Enterprise...
[SuperSU] Bakuryu42:
It just says 2.79
[SuperSU] Ibuprophen:
If you had SR3 installed, then it would state "2.79 SR3".

Sent on my Communicator [SCH-I535] from the Bridge of the U.S.S. Enterprise...
[SuperSU] khan alozai:
hi sir

I have Qmobile z12 pro. I tried to flash it but when i click on instal zip it say installation aborted. Any solution plz
[SuperSU] Bakuryu42:
What version does google play store have? just 2.79?
[SuperSU] Ibuprophen:
Yes. Chainfire only releases the stable versions on the Play Store.

Sent on my Communicator [SCH-I535] from the Bridge of the U.S.S. Enterprise...
[SuperSU] Strephon Alkhalikoi:
Chainfire no longer releases on the Play Store. CCMT has taken over.
[SuperSU] Ibuprophen:
My apologies!

I intended it to mean that whatever is on the Play Store is the Stable version.

Thank You for pointing this out.

***EDIT: I stand corrected again (what a day)... I referred to Chainfires notice again.

I should have referred to it in the first place and stated that the Play Store only has the Stable versions of SuperSU and the 2.79 that's currently there is the last one that will be released by Chainfire through the Play Store ONLY.

My apologies again!

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

---------- Post added at 06:03 PM ---------- Previous post was at 05:45 PM ----------

Wow...

You guys/gals here are a much nicer group than on the FlashFire thread!

I was getting pummeled in there with contradicting statements wrapped up in pretty little technical words.

Someone tried to state, as a fact, by telling me that if SuperSU is installed and the binaries are successfully installed then the SELinux State would change for FlashFire to work.

No matter how much I tried to make a point that this wasn't always the case when it comes to the SELinux State for FlashFire because even with a successful install of SuperSU and its binaries, not all devices with FlashFire will change the SELinux State. I also added the quote that Chainfire had made supporting this.

I really do believe that Chainfire had lost control of that thread. There's way too many things members trying to help other members all at once and just becomes a confusing mess.

Thanks for letting me air this out a moment... I need a drink but.. I DON'T DRINK! LMAO!!!

Sent on my Communicator [SCH-I535] from the Bridge of the U.S.S. Enterprise...
[SuperSU] culiacanazo:
What? Flashfire works?
[SuperSU] DB126:
Err...works for what on which device? Have no idea what you are asking (yes, I know what FlashFire is).
[SuperSU] Ibuprophen:
FlashFire does work as long as the device meets the prerequisites (outlined by Chainfire) and the device has the ability for the SELinux State to be changed temporarily to Permissive when FlashFire calls upon the device to do so.

Sent on my Communicator [SCH-I535] from the Bridge of the U.S.S. Enterprise...
[SuperSU] culiacanazo:
The last part is the tricky part!

Once upon a time... Heck, I'll do some reading and searching (in the appropriate thread)!!
[SuperSU] JaR_B:
Working 100% on Samsung A500M with MM 6.0.1

Thanks :good:
[SuperSU] Bakuryu42:
So this is the second of Chainfire's apps that this is happening with and it doesn't happen with any other app. Installing these apps results in them being installed, but the Play store doesn't show that it is and thus probably won't update the app when they are updated. Like wise they both are acting very screwy. I just reinstalled this from the store, had the same issue. When it granted my apps root it started endlessly notifying me of each one over and over till I restarted. What is going on with this?
[SuperSU] shaggyskunk:
I personally always Flash the zip - as far as the notifications when you open an app that requires Root - You can go to SuperSU settings and uncheck notifications (I'm guessing that's what you are talking about?).
[SuperSU] Bakuryu42:
It wasn't a notification like you would see up top, it was those blue background toward the bottom notices that pop up when a app is granted root. Restarting seemed to fix it though so its not an issue anymore. I wanted it installed from the store so it just updates when it needs to. I just found out apparently another app is like this as well, BusyBox is also installed, but not showing installed in the Playstore and I swear it was installed from there as well. Even so know what I've seen so far if I try installing it from the store it probably won't change. I don't know why this is though. So far it seems to only be root apps.
[SuperSU] shaggyskunk:
Exactly - I'm not talking about the hashtag symbol on the Notification bar - I'm talking about the pop up

SuperSU Settings

View attachment 4112677
[SuperSU] j0nas_:
I've had root since the 7.0 update rolled out and it has sometimes crashed which led me to reflash it(restore stock boot>install elemental x1.04>install supersu>clear cache and dalvik). Yesterday I enabled freeform window mode through root essentials and about that time the phone crashed and will only boot if I flash stock boot with or without elemental x. What can I do to fix this?
[SuperSU] Bakuryu42:
Like I said this isn't the issue anymore. The issue is why this, Flashfire, and Busybox don't show as being installed in the Playstore.
[SuperSU] shaggyskunk:
When you open Titanium Backup - it checks for busybox - It's there for me - And I don't see it as being installed on the play store or in my app drawer.

I'm thinking that you are pretty new to Android and probably need to do a bunch of research and reading.
[SuperSU] Bakuryu42:
If you check my post history you would know that's not true. I've done tons of research and reading. BusyBox may have been installed while I was rooting back in the day, SuperSu definitely. But I switch to the playstore version for super su and flashfire was never side loaded on my phone. So why are both showing as not being installed on the play store even though they were installed through it?
[SuperSU] shaggyskunk:
Google search for the answers. And you've got a total of 65 posts - So it's not like you have much for another member of XDA to draw any conclusions about your expertise..
[SuperSU] Ibuprophen:
Have you looked at the following link?

https://xdaforums.com/showpost.php?p=31159763&postcount=7

"Live Long and Prosper..."

~Ambassador S'chn T'gai Spock

Sent via Communicator [D2VZW] from the Bridge of the U.S.S. Enterprise [NCC-1701]
[SuperSU] sebiciuca:
Problem with installing SuperSu

I've installed yesterday on my LG G2 https://xdaforums.com/lg-g2/orig-development/rom-cyanogenmod-14-1-t3490688 .

I've tried after to install SuperSU 2.79, but i can't.

What i did:

1. Download the Zip

2. Boot into recovery

3. Install the SuperSU ( with TWRP )

4. Restart the device.

Now here is where it gets tricky, after the LG Logo shows in the left upside corner there is a message "Boot verification fail" and screen goes black.

I've managed to go back into the TWRP ( Using volume down and power button ). I reflashed CM14.1 and GApps now it works. I've tried to install the SuperSU again the same problem. I''ve reflashed the CM14.1 again, but now I think i'll wait for an opinion from you guys. ( BTW I need the root access so I can write my APN settings, the mobile data is not working now on the phone)/
[SuperSU] DB126:
- check for native (privacy guard) manager under developer options; may not need SuperSU

- be sure to use the latest SuperSU build (2.79 SR3 as of this post)

- beyond that is likely ROM dependent; might have better luck in your device forum
[SuperSU] Bakuryu42:
If Google searching got me my answer I wouldn't be posting on here. I tried all the usual clear the Google Play/Google Play Service cache, data, reinstall updates. None of it worked. And the fact that it was these specific apps make me feel like it has something to do with root.

I am not sure what this has to do with my problem? It did make me wonder about how I had busy box installed and it is in xbin, but Titanium Backup is working fine as far as I know, it detects Busy Box so I don't think this is the problem.
[SuperSU] Ibuprophen:
I've recently clarified the following for a couple of members elsewhere and wasn't sure if you were aware of this as well.

There's 2 different "xbin" directories that the BusyBox app has to choose from to install the BusyBox Binaries into.

1) /su/xbin

2) /system/xbin

The second one is what's more widely used for apps and such that requires one or more of the BusyBox Binaries AND though there's nothing wrong with using the first one to install the BusyBox Binaries, many of the apps and such are developed to look in a specific location for them and the first one is usually the most commonly used as the default location.

Just wanted to mention this...

Thanks!

"Live Long and Prosper..."

~Ambassador S'chn T'gai Spock

Sent via Communicator [D2VZW] from the Bridge of the U.S.S. Enterprise [NCC-1701].
[SuperSU] sebiciuca:
Yeah just saw the Root option in developer option, thank you!
[SuperSU] Bakuryu42:
You say the second is more widely used only to say the first one is commonly used as the default for apps. Mine is installed into the second directory.
[SuperSU] jcmm11:
Custom ROMs that pre-install BusyBox place it in/system/xbin

/su/xbin is only available with a systemless install of SuperSU. Osmosis's BusyBox installer will use/su/xbin of it's available, else will stick it in /system/xbin. Someplace else for Magisk.

Stericson let's you set where you want it, defaults to /su/xbin. Not sure about others, but /su/xbin should be the preferred location, if it's available, in order to keep from modifying /system (especially on stock systems). Not sure where Magisk prefers it's systemless installs.

An app that uses BusyBox will often include it's own copy of the specific modules it needs. Any app that uses a version of BusyBox that's installed systemwide should not be looking for it in a specific location, otherwise the app is poorly coded.
[SuperSU] Bakuryu42:
Honestly I have no idea where this discussion is going. I am trying to figure out why Google Play Store doesn't recognized the app it just installed, mainly this one and FlashFire.
[SuperSU] vampirefo:
That is interesting, I just checked my SuperSU is listed as installed in playstore, I haven't installed flashfire, have no need for it so can't confirm if it's displayed in playstore or not.

OK just the hell of it I installed flashfire, playstore shows it's installed and up to date, no sure what is happening on your device, not happening on mine, can't reproduce your problem.
[SuperSU] DB126:
Nor can I. Have both named packages (plus several that utilize root) installed on several devices from different vendors with varying ROMs. Have yet to observe this behavior. Feels like a borked Google Play Services, Store and/or Framework install.
[SuperSU] vampirefo:
Yes, something besides just these apps, or we would also have the same problem he does, seeing we don't that rules out it being the apps.
[SuperSU] Morrpheus:
Hi, my phone was rooted with TWRP and SuperSU 2.79. I unrooted in SuperSU so I could use/login Snapchat.

When I flash SU 2.79 again in TWRP it hangs in supersu installer when creating an image.

Anybody an idea how to solve?

Thanks!

Verstuurd vanaf mijn SM-G955F met Tapatalk
[SuperSU] ulxerker:
Try SuperSU v2.79 SR3.
[SuperSU] jcmm11:
Dirty flash your ROM then reapply SuperSU. (I'm guessing you're talking about boot image).
[SuperSU] devdjena:
binary is not updated... pls help me.... I have a Lenovo tab2 A7 ...
[SuperSU] shaggyskunk:
Just Flash the SuperSU zip in Recovery.
[SuperSU] nadim365:
in case i want to unroot what do i have to do ?
[SuperSU] delca85:
I have just flashed supersu 2.79 on my Huawei P9 lite with Nougat installed but supersu App keep on telling me I have not rooted. Is this version not working with Nougat and my phone?

Thanks!
[SuperSU] DB126:
Try 2.79 SR3 beta release as it contains many fixes (search thread for link).
[SuperSU] delca85:
Thanks for your reply. I have tried now with SR3 beta but it does not work neither.

Inviato dal mio HUAWEI VNS-L31 con Tapatalk 2
[SuperSU] DB126:
Don't have an immediate response. Hopefully someone who owns that device can chime in.

BTW - how are you "flashing" if device is not rooted? Bootloader unlocked?
[SuperSU] delca85:
I was on a marshmallow kernel, I have unlocked bootloader and rooted that kernel. Now I have updated to Nougat, I have installed twrp and I would like to root it too.

Inviato dal mio HUAWEI VNS-L31 con Tapatalk 2
[SuperSU] jcmm11:
Stock or custom ROM? Kernel? TWRP log from trying to root?
[SuperSU] RoxAbout:
Not sure if this helps but..

It would appear that some dev's have decided to use superuser for root instead of SuperSu.

Yes it is a royal PITA for users who have paid for SuperSu and have things "broken / not working properly" with the new superuser.

check your devices thread for conflicts of the above.

I wont say my rom's dev but it's the same issue for my device/rom, and with the posted work around for it works but because of who and how and about the changes to SuperSu some dev's have made it difficult by switching out one for the other.

Personally I prefer SuperSu, and wish the dev and the new owners the best.

Your mileage may vary.

Good luck
[SuperSU] culiacanazo:
Tap "UNROOT".

You know, inside the app.

---------- Post added at 05:37 AM ---------- Previous post was at 05:33 AM ----------

Haha your avatar's cool AF! :highfive:
[SuperSU] delca85:
Stock rom. Twrp stop printing any message after few line when I try to install SuperSu zip and reboot my device.

Inviato dal mio HUAWEI VNS-L31 con Tapatalk 2

---------- Post added at 08:34 AM ---------- Previous post was at 08:32 AM ----------

Do you think this can be my situation even if I am on the stock rom?

Inviato dal mio HUAWEI VNS-L31 con Tapatalk 2
[SuperSU] EinderJam:
I just rooted my P9 Lite using TWRP and supersu from this topic:

https://xdaforums.com/huawei-p9lite/development/twrp-t3588356/page7

Check it out !
[SuperSU] crazydr0id:
Is this why I can't install SuperSU as system app with recovery script? I have to flash SuperSU zip every update anyway otherwise get errors about not having root. Would changing from systemless mode to system app prevent having to reflash every rom update?

Along the same lines, should root be enabled in developer options and which setting should be used, apps only or include adb?

If this is the reason SuperSU can't be installed as system app, can busybox be moved to su/xbin and if so what's the best method to do this?

Thanks! ?
[SuperSU] delca85:
Thanks for your suggestion but now I am in an ugly situation: I had to rollback to MM because of bluetooth was not working in nougat and now I have bricked because with Revolution Recovery no update.zip can be flashed. Now I am without os and I am trying to solve this with dload/UPDATE.APP method.
[SuperSU] delca85:
I have rooted with the zip you linked me, but now I am not able to restore with Titanium Backup. The su binary is updated, SuperSu app does not tell anything to me. Have you used Titanium too?
[SuperSU] EinderJam:
No,i used hisuite to restore my apps, contacts and photos
[SuperSU] RTNDO128:
Anyone having issues with this on the new May security update for the Pixel? Right after flashing, I got stuck in some EXT4 Ramdump bootloop.
[SuperSU] Ibuprophen:
Here's some information that just may reflect this situation and some suggestions as to a possible fix.

https://support.google.com/pixelphone/forum/AAAAb4-OgUsesjkO_p9LjE

http://phandroid.com/2017/01/03/nexus-6p-bootloop-bug/

https://support.google.com/pixelphone/answer/4582729

http://www.androidpolice.com/2017/04/14/google-may-sued-nexus-6p-early-shutdown-bootloop-issues/

"Live Long and Prosper..."

~Ambassador S'chn T'gai Spock

Sent via Communicator [D2VZW] from the Bridge of the U.S.S. Enterprise [NCC-1701].
[SuperSU] chwiejak:
Please help me with this, I need working supersu for another app.

Thanks
[SuperSU] culiacanazo:
The silence probably stems from a mixture of lack of info on your part and the fact that, because your problem is very common, it's been answered before. Kindly search, because it would be a long write. :good:
[SuperSU] chwiejak:
Thank you for reply, and yes, you are right it looks like common issue and there is lots of treats but most of them are without even single reply.

What other info you need to detect my problem?

Thanks
[SuperSU] jjakajonas:
Is there a way to hide that supersu is installed and the phone is rooted?
[SuperSU] jhs39:
There used to be but I don't think the app used for that is updated anymore. If you want to hide root you probably need to root with Magisk rather than SuperSu.
[SuperSU] jjakajonas:
Okay.

Thanks.
[SuperSU] :
There is a Xposed Module (Root Cloak)

But Who Uses MM These Days With Android O On The Verge

#RIPXposed :(
[SuperSU] jjakajonas:
Personally I use N on my device.
[SuperSU] DB126:
While Android 7.x rocks a pretty face I see no functional advantage of N over MM with a small, carefully selected suite of Xposed modules. Early read on O suggests a similar conclusion. Not wed to MM by any means but have a hard time stepping away from control provided via Xposed.
[SuperSU] #ApolloLiteProblems:
I keep flashing the zip but it won't register. It says that there is no SU binary installed yet I have installed it 3 times, all of which failed. My phone was rooted but Magisk wasn't working. Running Vented Apollo Lite on RR 7.1.1
[SuperSU] Shtiff1:
How can I make this a systemless install?

XT1254, 6.0.1, stock rom, unlocked bl, Xposed, busybox, changed unlocked bl warning. TY
[SuperSU] cgibbons51:
Magisk is one of the main ways to do it.:mad:
[SuperSU] Shtiff1:
Ya, I've been following that thread. I don't want to deal with all those issues. I thought there might have been an easier way to do supersu. Which I'm already running.
[SuperSU] cgibbons51:
Oh not 100% sure but I got Android pay working with magisk :laugh: but yah I'm only using cause it came with ROM
[SuperSU] vygavedha:
Boot recovey a go to terminal.type the following

echo SYSTMLESS =true >>/data/.supesu

then flash su zip as normal in twrp..

Su will be installed SYSTMLESS mode.
[SuperSU] Chainfire:
It is systemless already on this firmware.
[SuperSU] vygavedha:
No need to type systemless =true in terminal before flashing..Is'nt it?
[SuperSU] jcmm11:
Correct. Systemless is the default install method.
[SuperSU] Shtiff1:
Thank you, this just seemed a little confusing.
[SuperSU] Mesmurized:
Me too. IMHO stating what is installed is much clearer than what isn't available.
[SuperSU] Didgeridoohan:
It's not stating how SuperSU is installed, just informing you that the option to move SuperSU to /system isn't available on a systemless install (indirectly telling you that you have a systemless install :p).
[SuperSU] Mesmurized:
I get what you're saying, but I interpret the sentence as a negative .vs. positive. Always need to re-read it 2 or 3 times. Could be my old-school logic in play.