yashsingh1/xdaforums huggingface dataset:
[SuperSU] Surge1223:
[MENTION=631273]Chainfire[/MENTION] out of curiosity is there a reason the binaries and libs for su, supol, etc are dynamic and not static? Was there an issue with libc? I ask because I always figured that it would be beneficial not to rely on shared libs in recovery, or just that the differences between devices' libc.so, libdl.so etc would cause issues?

Also for supolicy and libsupol.so, did you write the code for patching sepolicy from scratch or? I figured you'd have used some part of setools for inspiration, I figured sediff + libpoldiff + libsepol etc would allow me to do this, but this only allows me to diff policies, I'm not quite sure what part of the setools would allow me to edit them.

And finally, is this the right place to ask you questions or is there a specific thread you'd prefer them in instead?
[SuperSU] jukiewalsh:
Previously I've just downloaded the zip from chainfire's site and it always flashed fine without any issues.

I'll investigate whether I need a device specific zip
[SuperSU] Alxoom33:
On what device and what N version did you have this problem? Which Super Su did you flash? Do you have logs?
[SuperSU] zalcsooo:
Okay. The only question here so far is that are there any user here who has enabled this new File encryption feature in the Developer settings with SuperSU (before or after, doesn't matter). If I see anyone using SuperSU on a file encrypted device, I will investigate my system and ofc give more details and ask for help.

---------- Post added at 08:45 PM ---------- Previous post was at 08:42 PM ----------

Nexus 5X, latest N (NRD90M and S), latest su (2.78) and, don't have logs yet, didn't want to investigate it until I get a confirmation about this new environment from someone else here. But if the dev(s) need(s) any logs or anything, I will provide and help gladly ofc. to make it more compatible.
[SuperSU] grep_i:
Don't know from experience but it should work because there are manuals how to root on Android 7.0 nougat and turn off the encryption afterwards.

This would of course not being possible if the device could not work with the encrypted files feature enabled.

They just seems to disable it so they can flash and use a more recent version than 2.8 of custom recovery TWRP.

To me it does not make sense to disable a security feature so you can have a recent version of custom recovery.

But that's my personal opinion on the matter.
[SuperSU] miloytyn:
File based encryption is totally different thing than full disk encryption. If I'm not remembering incorrectly, Chainfire wrote that it is not yet supported.
[SuperSU] DB126:
Yep - that's why KR and similar approaches are part of the solution space (satisfies needs not by addressed legit methods/tools). For some communities obtaining root opens the door to flashing a custom recovery and/or ROM. The latter obliterates KR detritus and permits use of SuperSU if desired/needed. There are other ways around root obsticles but the above is clean and effective for many.
[SuperSU] Ibuprophen:
I'm a little confused here...

Correct me if I'm wrong but, SuperSU doesn't have anything to do with the actual rooting of a device...

After a proper root has already been accomplished, all SuperSU does is to monitor and manage access to the devices rooted system files and folders.

I'm seeing SuperSU being referenced as a tool for obtaining root when that's not what the purpose of SuperSU is.

Am I wrong? And if I am then please elaborate so I will know.

Peace and Love!

Peace and Love!

~Ringo Starr~

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

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

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

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

********************************************
[SuperSU] vampirefo:
SuperSU is indeed used to root devices, it is limited due to not using exploits, it can root via custom recovery, or via download through playstore, the playstore version is a little more complex.
[SuperSU] manzoor ahamed:
anybody here???

i have a big problem...

i rooted my devices... and was using it for 1 week.. my devices brand is sony ..model xperia T3

after 1 week i had problems like device starts to crash i.e., unfotunately stopped errors... aftr tat i cleared cache , factroy reset and alll the things...

thn i flashed it with flashtool(official).. tis probem fr me persisiting fr months...

so i unrooted my devices..

the same problm occurs ..

bootloop fr every 1 week.. and i have to flash it with flashtool

can anyone please please please tell me a solution!!!!

thanks,
[SuperSU] DB126:
Exposing root might be a better descriptor but for all practical purposes the above is accurate from a user perspective.
[SuperSU] badohn:
Thanks for the information.
[SuperSU] culiacanazo:
If you were able to restore from a big fat brick or wasn't such a big fat brick after all, now, was it? Phew!

---------- Post added at 11:44 AM ---------- Previous post was at 11:39 AM ----------

Is this back in style? I mean, I'm just curious cause i thought I've read somewhere that it had become... Well, you know what i mean

---------- Post added at 11:48 AM ---------- Previous post was at 11:44 AM ----------

Emphasis mine.

How so? That's a new one for me
[SuperSU] brunopio:
Unsupported device: Moto G4 Plus ATHENE NPJ25.93-14 Android 7.0

Unsupported device: Moto G4 Plus ATHENE NPJ25.93-14 Android 7.0

Do not boot...

SuperSU-v2.79

instaling from twrp-3.0.3-n4-athene_shreps

(h t t ps://xdaforums.com/moto-g4-plus/development/recovery-twrp-3-0-2-r3-moto-g4-g4-plus-t3494337)

Logs and boot.img (google drive):

h t t ps://drive.google.com/drive/folders/0B0Fg4kGChrccbklpTlJyNkN0X2c?usp=sharing
[SuperSU] jdegreef:
[MENTION=8104781]brunopio[/MENTION]

X-posted !!!

I've replied to your other post !

---------- Post added at 17:56 ---------- Previous post was at 17:50 ----------

From the OP : !!! SuperSU requires a rooted device !!!

Rooted by flashing the .zip file through TWRP ;)
[SuperSU] chillo71:
:rolleyes:

Peace all!

I agreed on messing with my phone and its system by rooting, at first place.

Dunno though how much the guys around here had to move down to tell me I should flash system.img after the uninstall fault (of a systemless root)

All well after all, I suppose..
[SuperSU] bryantjopplin:
Are you taking the IMG from their device after it installs or directly from the update zip?

Sent from my Nexus 6 with Pixel XL build.prop
[SuperSU] Xak:
[MENTION=631273]Chainfire[/MENTION] can you update S7QC super su to latest stable version which would be like SuperSU-v2.79-S7QC if existed 2.79 su is latest stable i think. its troublesome to keep super su as skip updates and then having to click yes skip many times. if you dont feel like updating it could you tell me how? this is probably in issue with all root engroot for usa s7 models. since we will not get perm root ever. not trying to be nagging but figured i could ask since its a bother and sometimes we click yes at least i do and it ****s up s7 usa root and you have to do a complete re install and engroot boot root etc it gets annoying is all. id rather be able ot update the su version my self manually if possible via replacing files in your version with files from latest su apk etc. or something like that.

- Thanks
[SuperSU] nimastd:
i flash it , but my phone didnt turn on. :(
[SuperSU] ulxerker:
you really have to provide more details and be a lot more specific.

also, it might be worth it to try SuperSU v2.79 - SR3 instead.
[SuperSU] Why-Fi:
my vs985 is stuck in a bootloop after updating the binary through the app downloaded from the playstore. i cannot boot into recovery whatsoever. also, my computer doesn't recognize the device, and i have ensured the drivers are up to date. any direction as to how to proceed?
[SuperSU] Puff1911:
Hi,

I'm trying to install SuperSu on my Sprint HTC M9.

I've rooted the phone and installed TWRP 2.8.7.

The phone boots into the stock rom fine up to this point.

If I now go into the recovery and install the SuperSU 2.79 (stable) or the SuperSU 2.79 R3, the phone gets stuck in a boot loop at the very first HTC screen.

Any ideas?

The phone has been sitting here for over a year never been used. I am now trying to get it sim unlocked.

Any help would be grealy appreciated.

Thanks.
[SuperSU] Why-Fi:
add mr. bump to the zip que after supersu.
[SuperSU] KOLIOSIS:
SIM Unlocking & root/bootloader unlocking are unrelated,you don't need one for the other.

If your device is paid off in full,Sprint should be able to SIM Unlock it.

If they're not cooperative, there's SIM Unlocking sites that'll issue you a code for a fee, usually pretty low for a 2 year old device.

Also,if your rooted device is working fine otherwise,JMHO, I wouldn't worry about updating SuperSU.

You'd probably be better served checking the M9 & Sprint M9 sections for the latest version of SuperSU that is compatible with your particular device.
[SuperSU] Puff1911:
Thanks for your response.

Sprint is not providing the unlock code.

I'll try the Sprint M9 section again..
[SuperSU] jcmm11:
I suspect that the "never been used" part is why Sprint won't give you the unlock code.

https://www.sprint.com/legal/unlocking_policy.html

Your best bet is probably to go third party.
[SuperSU] Puff1911:
Third party won't work for the Sprint variant.

We're going off topic though.

Any idea why the SuperSu would cause the bootloop?
[SuperSU] jcmm11:
No idea, otherwise would have mentioned it. Last part of this off topic. Try http://www.htcsimunlock.com they claim to work for any network. Good luck.
[SuperSU] KOLIOSIS:
Going OT,real brief:

Sprint will SIM Unlock it,the requirements are listed here,guessing the active on network requirement wasn't met,or,the phone was blacklisted due to shenanigans from the previous owner.

https://www.sprint.com/legal/unlocking_policy.html

As for your bootlooping issues,this would be a good place to start,an RUU back to stock & start over:

https://xdaforums.com/sprint-one-m9/development/ruu-sprint-htc-one-m9-1-32-651-17-t3073355
[SuperSU] MJPByron:
Stupid question, but I'm running Echoe Rom on a Galaxy S7 and I have to update the SuperSU binary. It fails the normal method and crashes via the TWRP method.

Should I download and flash the zip in the OP via TWRP? Or is there some other method I need to use?
[SuperSU] niki101:
Relevant Info

:

Motorola G (falcon) - XT-1033, Root: Yes,

ROM: Lineage 14.1-20170315-nightly, TWRP 3.0.2-2

Root management right now: addonsu-arm-signed.zip (547kb, official LineageOS addon, flashed after flashing ROM)

I want SuperSu to be my root management app. How do I do that?

WHY?

Because, some apps that need root,

Not working - FlashFire, Viper4Android v7.9.3. :(

Working - Greenify, Airdroid, ROM Toolbox lite, etc. :)

I guess, 1st I will have to get rid of addonsu-arm and unroot. Then, I will have to install SuperSu.

I did this: Installed SuperSu while keeping addonsu-arm, but SuperSu says, that binary is not updated and I shall update it using recovery boot of twrp

EDIT: Resolved by fresh installing/(Flashing?): ROM, GApps, SuperSu v2.79
[SuperSU] DB126:
Did you flash the zip from the OP?
[SuperSU] Why-Fi:
? any help at all?
[SuperSU] DB126:
Some of these events seem unrelated. Installing the SuperSU app (APK) and subsequently updating the binary should not prevent your phone from booting into recovery. Not recognizing a tethered device is an expected outcome of a boot loop depending how far the ROM gets before looping. You should focus on getting into recovery by asking in your device's forum: https://xdaforums.com/verizon-lg-g3
[SuperSU] Why-Fi:
I have posted in my device's forum. I am posting here because the problem happened after updating the binary. the SUPERSU binary. SUPERSU binary update somehow screwed with my device in a way that has made it inaccessible. so I am asking for help on the SUPERSU thread. isn't that what this forum is for? learning and helping and all those other positive things? sharing information? what about your reply was any of that?
[SuperSU] vampirefo:
How could this thread possible help you? You have to get into recovery, so rather then waste time here try Google.
[SuperSU] DB126:
Actually, I was attempting to connect you with the best resource for addressing the immediate situation. Access to recovery is essential to salvage your device (unless the bootloader is unlocked which seems highly unlikely on Verizon). Appreciate your frustration but I neither own nor have experience with a LG G3.
[SuperSU] kojak1989:
Where can I find translations for superSU app?
[SuperSU] snowleopardmike:
noob question. i have twrp and slimkat custom rom. will flashing the zip file attached here root my device?
[SuperSU] jcmm11:
That's the theory.
[SuperSU] Whiskey103:
Thread cleaned a bit, please keep it nice and civil.

Whiskey

Forum Moderator
[SuperSU] DB126:
[MENTION=5559639]schneiderpatrick[/MENTION]

You quoted a post from another member without further context. Are you trying to ask a question?
[SuperSU] Why-Fi:
that is an odd one. either whiskey cleaned up something they wrote, or they have the same issue. that's my theory anyways. :)
[SuperSU] jcmm11:
Somebody is trying to get 10 posts. ? They'll find out that's not the way to do it. :eek:
[SuperSU] :
I Have been Using SuperSU for a Year Now i didn't knew anything about chainfire and a chinese firm buying it just read an article on it is there something to worry about ?
[SuperSU] Strephon Alkhalikoi:
[MENTION=7733127]parth_kalsi[/MENTION]: It's an issue of people not paying attention and becoming paranoid. Chainfire told everyone a year prior to the sale that he was selling. He didn't reveal the company he sold it to was Chinese, quite likely because he knew people on this and every other forum would freak out over the communist connection. Whether the concern is justified or not, it's up to you as to whether you want to trust SuperSU. Those of us still using it for the most part do, as one year plus from the sale it's been business as usual. If you trust SuperSU continue using it. Otherwise there are alternatives on XDA.
[SuperSU] :
Thanks for Explaining All this My Device's Maintainers Say Use Magisk but I am Still Using SuperSU i trust Chainfire :)
[SuperSU] Why-Fi:
omg that's hilarious :highfive:
[SuperSU] ioancr:
Hi all. I am currently on LG G2 D802, Android 7.1.1 (Resurrection Remix). Trying to replace the default su manager (Magisk) because of some compatibility issues, I lost root. I couldn't restore it with flashable SuperSu provided here, my phone would stuck at bootanimation, or (with SR3) would give "secure boot error" with problems getting to recovery. Neither restoring boot & system partition from a backup was effective, the phone stayed unrooted. Tried KingRoot to no avail. Finally, had an idea to extract "magisk.zip" from the ROM installation zip and flashed it in TWRP - it worked. Now I have root, but still can't use Terminal due to no "sudo" available. Is this normal - or I am still partially rooted? Hope my experience will help someone.

Thanks
[SuperSU] rajatgupta1998:
Isn't it

# su

?
[SuperSU] vampirefo:
Never heard of an android app asking for sudo, what app is that?
[SuperSU] ioancr:
:) my bad. Forgot it's not Linux. Now it works.
[SuperSU] FebryRamahdana:
can't update binary S7 edge Tmobile

pal, please help me or anybody..newbie here..

i have follow the instruction to root my and i made it

but when i open superSU, it says that i have to update the binary, i click the normal option but always failed.

what should i do?

i'm following at the page 1 instruction to root my s7 edge t mobile
[SuperSU] Why-Fi:
Don't update the binary. Whatever you do. Use a root checker app to see if you're rooted or not. If so, uninstall that app. If not, flash the SuperSU and Mr bump.zip. DO NOT UPDATE BINARY
[SuperSU] bryantjopplin:
Is that a locked down bootloader for the s7? Isn't the new one for systemless root require a boot IMG that is patched?

Sent from my Nexus 6 with Pixel XL build.prop
[SuperSU] FebryRamahdana:
Root checker app said my device wasn't rooted ?

I have follow the instruction to root my device in this forum.

And when i boot, i see padlock image that said unlocked.

So how?

I'm i fail ?
[SuperSU] Ibuprophen:
Did you look around the S7 Edge portion of the XDA Forum?

https://xdaforums.com/tmobile-s7-edge

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

***PLZ THANK ME WITH A THUMBS UP***
[SuperSU] Ibuprophen:
I apologize if I was insulting in any way.

I found a thread that just may help you out.

https://xdaforums.com/tmobile-s7-edge/how-to/heres-how-rooted-nougat-s7-edge-g935t-t3567502

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

***PLZ THANK ME WITH A THUMBS UP***
[SuperSU] FebryRamahdana:
Thanks man, this world need people like you ?

My device is S7 edge qualcomm series, my device can't instal custom recoveries.

So how to flash it?

Can you give me the tutor?

Sorry for that, i'm just a newbie ?

---------- Post added at 03:14 AM ---------- Previous post was at 03:12 AM ----------

I root my device basicly from that forum. But the problem still the same ?
[SuperSU] Why-Fi:
I got ya. I don't have working knowledge of that one in particular, but I can get you with someone that will help you. Send me a p.m. and in the mean time, do some research and ask some questions on the pertinent threads for your device. It's late, so I probably won't have comms with my buddy until morning. Just sit tight and keep asking questions. No questions is a dumb question.
[SuperSU] FebryRamahdana:
Omg!! I'm so frustrated ?

Still I can't root my device.

I have done the way from ibuprophen but still can't.
[SuperSU] peterlee928:
have u tried using supersu 2.79 sr3 (beta version)?

and ur using the latest twrp (assuming that is ur custom recovery)?
[SuperSU] FebryRamahdana:
My device S7 edge qualcomm can not instal custom recovery.
[SuperSU] peterlee928:
wut abt the beta supersu?
[SuperSU] ulxerker:
:confused:

he has to install twrp before supersu if he wants to flash it via twrp ...
[SuperSU] peterlee928:
he can install beta supersu via APK

point is

if stable supersu isnt working

perhaps give the beta version a try

just a thought :)
[SuperSU] TimSchumi:
He can only install the UI of SuperSU via APK. He still doesn't have the SU Binaries installed then. Because of that the UI would complain and he never gets root access.

---------- Post added at 11:32 AM ---------- Previous post was at 11:31 AM ----------

You may try one of those One-Click Root Applications (vRoot, etc.)

But for those Applications this thread isn't the correct one (I think)
[SuperSU] bryantjopplin:
Questions

Was your device rooted before?

If you did, what was the highest SuperSU installed?

Also if previously rooted how did you root?

Have you ever rooted via a tool (app or adb)?

Does your phone boot with the unlocked symbol?

If you have never been rooted previously, just installing the app from the play store will not work on your device, well at least I'm pretty sure you can't.

Sent from my Nexus 6 with Pixel XL build.prop
[SuperSU] DB126:
You were not and did not deserve the response provided. Action taken.
[SuperSU] sguy156:
which version of SU works with 7.0 and doesn't cause boot loop
[SuperSU] Ibuprophen:
I didn't think so either but, I've learned that some battles are worth fighting and some are not.

I also realized that due to that members off the wall response just reflected to me that no matter how i responded to it would have resulted in another, even deeper, off the wall response.

But, thank you VERY much for going to bat for me!

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

***PLZ THANK ME WITH A THUMBS UP***
[SuperSU] peterlee928:
ibuprophen is a good dude

helped me out on more than 1 occasion

cut the man a break :)
[SuperSU] DB126:
The responder (post since removed) has a history of nasty comments. And yes, [MENTION=4828250]Ibuprophen[/MENTION] is a good dude with solid intentions.
[SuperSU] Ibuprophen:
Thank You!!!

It's all about Respect...
[SuperSU] ulxerker:
SuperSU v2.79 SR3
[SuperSU] nimnull:
Is there any option to install via TWRP only "su" binaries, but not Superuser.apk?

I am going to use "su" only with adb, and I do not want it to be always loaded, as long as it uses "RECEIVE_BOOT_COMPLETED".

If not, can it be removed later?

Thank you in advance.
[SuperSU] Strephon Alkhalikoi:
You asked this on the beta thread and [MENTION=1162986]Captain_Throwback[/MENTION] answered you there. If you want just the su binary you'll have to extract it from the zip, replace the existing su binary with it, and set permissions on the binary. Don't be surprised however if your device bootloops as a result.
[SuperSU] vampirefo:
Your post doesn't make sense to me, let me explain none of my devices are rooted, yet all are adb root.

I use insecure boot.img, which means my adb is always # never $ I don't use any su binary file as it's only needed for non adb work.

adb remount mounts system as rw, I can do anything to phone via adb without ever using a su binary file, su is really only needed to run apps.
[SuperSU] culiacanazo:
I missed it but i agree with the latter opinion since the times we've crossed paths, he's been pleasant to interact with.
[SuperSU] oggerz:
complete noob here

Rooted my first device yesterday using this guide https://xdaforums.com/moto-g4-plus/how-to/guide-how-root-nougat-moto-g4-plus-t3484672/page20#post71655231 Using a Moto G4 XT-1622(UK) - Nougat 7.0 Stock ROM/ElementalXkernel/TWRP. Was rooted using Phh's superuser file however forgot to change some text in the config, which has led me to believe my phone isn't correctly rooted. Can I change this by simply connecting my phone and changing the text on my PC, or is there a more thorough approach that needs to be done, or better yet, how can i replace phh's superuser file with SuperSu.

Not entirely sure if my phone is rooted correctly as some things haven't worked - despite root checker saying root access is properly installed. Can I remedy this by installing the SR3 v2.79 file on my phone.

apologies for the stupid questions but phone modding is only noob friendly until something goes wrong.
[SuperSU] jcmm11:
To replace with SuperSU first of all you have to completely remove phh. Get the unsu script from Osmosis

That should remove all traces of any su you may have installed. After that you should be able to just flash SuperSU
[SuperSU] oggerz:
Awesome thanks very much!
[SuperSU] Koniorek:
Hello,

Im having same problem over and over again. When I'm trying to install SuperSU ( TWRP ) to root my phone ( S6, android 7.0) every time I stuck on "Creating image" ( when installing v2.79 ) and on "Creating paths" when installing version 2.78. I dont really know what can I do to fix it ? Please help. Thank you

Tried SuperSU v2.79 SR3 aswell - same as with 2.79
[SuperSU] Chainfire:
On newer Android versions (6.0+ top of my head) the SuperSU APK is installed in /data by default. Do the following from an adb shell:

su
pm uninstall eu.chainfire.supersu
rm -rf /data/app/eu.chainfire.supersu*
rm -rf /data/data/eu.chainfire.supersu*

Just uninstalling the APK may leave a leftover configuration file (by design) that will prevent APK-less su from gaining root.

You can also just take the SuperSU ZIP installer, and delete common/Superuser.apk from it. Depending on your TWRP version, that might still install fine.
[SuperSU] jugoslavpetrovic:
Hey guys, anyone knows how to fully unroot and unpatch the boot image?
[SuperSU] Devilix:
Hi, somebody has issue with bypass safetynet protection with supersu and root switch? Thanks

I'm gettin a bad blue screen with root disable by root switch :(
[SuperSU] drewski_1:
Full unroot option in Super SU app?
[SuperSU] Ibuprophen:
Just to, respectfully, elaborate on this...

Towards the bottom of the SuperSU Settings, you'll see a "Cleanup" category and, just under that, you'll notice the words "Full Unroot".

I wish you the best of luck!

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