yashsingh1/xdaforums huggingface dataset:
[SuperSU] rush9935:
Hello,

Where can I find a Rom for the (galaxy s5 neo )convert like s7 Edge or other ????
[SuperSU] egingell:
You've wandered far away from where you should be looking.

Sent from: SGS5 - MM 6.0.1 / SGS4 - LP 5.0.1
[SuperSU] wollup:
Hello! I have a problem with the app solid explorer classic on my Note 4 with Emotion Rom 6.0.1. If i wont use a function that require root access there no pop up the window from SuperSU to confirm (like my other apps do by the way). In solid explorer comes a error message:

No root access available...
[SuperSU] ktmom:
This is an app problem, not a failure of SuperSu. You could point the developer to ChainFire's developer guidelines
[SuperSU] grep_i:
Open Supersu and look if access is granted to the app in the app list.

Also make sure you have busybox installed because it's needed for most root commands in solid explorer.

What's more possible is it won't work with systemless root you have to force systemmode root to make it work with Supersu.

This is an app for Android 2.3 and up you will have to update to solid explorer file manager which is the new version for Android 4.1 and up.

There will be an interface difference but it's the same app or you can choose to use another file explorer.
[SuperSU] hello00:
are you planning to support alcatel idol 4s?
[SuperSU] indiangamer007:
Having trouble downloading latest SuperSU from site. Any mirror links?
[SuperSU] grep_i:
Use Google or duckduckgo or even apkmirror.
[SuperSU] Duiesel:
Adding root into custom ROM

Hello, Guys! Thanks for the great work about rooting android devices!!!!

I've got problem with manual adding root into custom ROM.

I've been learned hoe to do it by update-binary.sh and by http://su.chainfire.eu/

But have no success for weeks.

I copied all needed files into system.img, gived all permissions and changed it's selinux context as describes in update-binary.sh, but already no success.

Only one thing that I can't do is: to run su --install

May be here someone can turn me into right way(docs, tutorials or other).

Anyway I'm happy for any help.

Thanks a lot!
[SuperSU] nicolap8:
[MENTION=631273]Chainfire[/MENTION]:

A suggestion.

A lot of people is havig problems with bootloop after systemless install.

A lot of devices can be booted with fastboot boot command.

If the installer would have a command to only "simulate" the install, creating the new boot image.

This boot image can be uploaded to pc and tested without modifying the phone.

If it works then can be flashed.

Else, in the appropriate thread, users can investigate and solve.
[SuperSU] Sam Nakamura:
Your questions is pointless as every device is supported if you find a appropriate custom recovery for your phone to flash the super su zip..

Or do I misunderstood anything?

---------- Post added at 08:14 PM ---------- Previous post was at 08:12 PM ----------

Just take a backup via twrp before modifying anything..
[SuperSU] nicolap8:
Maybe I not explained well...

If you install SuperSU in SystemLess mode (via twrp or other custom recovery) then your BOOT.IMG WILL BE modified! And this is the problem (if something go wrong).

What was unclear???
[SuperSU] mielletseed:
but before installing SuperSU you could backup your unmodified boot.img and restore it in case of a problem...
[SuperSU] nicolap8:
Of course you can...

You can also read all the docs before...

But a lot of people don't do this! And after come here requesting help.

I think that we must be proactive and do something before to help these users.
[SuperSU] mielletseed:
And you think people would "simulate" and copy the boot image to PC and test boot image via fastboot - the same people that would not make a backup? You really think, ya? I don't belive :D
[SuperSU] Sam Nakamura:
Yeah, so what's the point, boot can be restored via twrp and you still can enter your recovery even if boot is corrupted..

---------- Post added at 09:15 PM ---------- Previous post was at 09:14 PM ----------

Exactly, before you modify.. Thanks [emoji4] that's the very sense of backing up.. [MENTION=4159151]nicolap8[/MENTION]

---------- Post added at 09:20 PM ---------- Previous post was at 09:15 PM ----------

That is waaay to funny [emoji12]
[SuperSU] hello00:
The phone isn't supported as the phone just came out, hence why I asked
[SuperSU] -Duir-:
How is it not supported?

If you're having issues installing it you should post your logs. If it's that you can't unlock the bootloader and/or there's no TWRP available to use to install SuperSU, that has absolutely nothing to do with SuperSU.
[SuperSU] Sam Nakamura:
Exactly what I meant..
[SuperSU] Cyber Akuma:
Does this version fix the loss of wireless radio issue with the HTC 10 (something to do with encryption I think?), or should I still just use the modified version of 2.74 here: http://xdaforums.com/htc-10/development/root-supersu-2-71-forceencrypt-verity-t3373258
[SuperSU] lklun:
I have noticed that there is a folder called /supersu, i.e. a folder placed directly in the Android root directory. I seem to be unable to remove this folder when trying to fully unroot my Nexus 9. Anyone know how to remove it and all other SuperSU files?

/supersu contains 7 files:

* 99SuperSUDaemon

* install-recovery.sh

* install-supersu.sh

* libsupol.so

* su

* Superuser.apk

* supolicy

I have tried removing it with rm -rf in an ADB shell as well as removing it in the TWRP file manager. Doing this causes the folder to disappear but after rebooting, it reappears. Flashing the Nexus 9 factory image does not remove it either. Choosing the "fully unroot" option in the SuperSU app does not remove it.

Does anyone know what to do to remove it?
[SuperSU] ktmom:
Did you try the "fully unroot" after deleting files?

Look for a script in /system/addon.d
[SuperSU] lklun:
Thanks for your reply!

I tried choosing the "full unroot" option in the SuperSU app after deleting the folder in TWRP, but it reappears even though the SuperSU app itself is uninstalled.

/system/addon.d does not exist.

Do you know what is causing the folder to reappear?
[SuperSU] ktmom:
I'm sure it's the survive update script.

When you tried full unroot, did you uncheck "enable superuser" first?

Edit-----

How did you remove the app? Go through all of the steps you did, in the order you did it.
[SuperSU] egingell:
For clarification, how are you seeing that folder? In "working" (normal, everyday use) mode or recovery terminal? If recovery (specifically TWRP), it's created by recovery and isn't present in working mode. If working mode, the folder is created by boot. Not by any app or script. You have to restore the original boot image to get rid of that folder.

Sent from: SGS5 - MM 6.0.1 / SGS4 - LP 5.0.1
[SuperSU] interminable01:
Hi

I can't install this app on cm 13 Xperia sp

What should I do?

Does it need any other app or some instructions or not?
[SuperSU] osm0sis:
It's part of the TWRP ramdisk and has no relation to your root status. ;)
[SuperSU] lklun:
I tried unchecking "enable superuser" before fully unrooting after you mentioned it. Same result.

I have tried the following:

Choose "Full unroot" in SuperSU

Choose the option to try restoring the stock boot image

Choose the option to try restoring the stock recovery

Result: An uninstall dialog appears and after a few seconds the Nexus 9 reboots. When it finishes booting, SuperSU is gone and I can no longer use the su command in an ADB shell. The /supersu folder is still there when I boot into TWRP.

Choose "Full unroot" in SuperSU

Choose the option not to try restoring the stock boot image

Result: Same as before.

Boot to TWRP and remove /supersu with rm -rf.

Boot to Android and choose "Full unroot" in SuperSU

Choose the option to try restoring the stock boot image

Choose the option to try restoring the stock recovery

Result: Same as before.

Boot to TWRP and remove /supersu with the TWRP file manager.

Boot to Android and choose "Full unroot" in SuperSU

Choose the option to try restoring the stock boot image

Choose the option to try restoring the stock recovery

Result: Same as before.

Boot to TWRP and remove /supersu with rm -rf.

Reboot to fastboot and immediately flash the factory image.

Result: Same as before.

I can only see /supersu when I'm in booted into TWRP. If I'm booted into TWRP, I can see the /supersu folder from an ADB shell as well as the TWRP file manager. If I boot into Android, I cannot see the folder in an ADB shell.

I have flashed the factory images provided by Google so the original boot image should have been restored.

Do you mean that it is TWRP creating this folder?
[SuperSU] osm0sis:
Yes, and it's not on your device's storage, it's part of TWRP's / filesystem. You don't have to worry about it.

All these attempts to remove /supersu are pointless; its existence does not mean you are rooted, nor does it mean you are not rooted. It is simply there so TWRP can root your device if you answer "yes" when it asks you, otherwise it doesn't do anything.
[SuperSU] lklun:
Thank you! This seems reasonable considering the fact that the folder is only visible from TWRP. I also copied the files from my Nexus 9 to my computer using ADB and compared the checksums to the corresponding files in the TWRP repo on Github and I think 3 of them agreed. 2 did not and 1 of the files on the device did not exist in the repo. Perhaps I looked in the wrong repo or the build does not correspond exactly to the source: https://github.com/TeamWin/Team-Win-Recovery-Project/tree/android-6.0/prebuilt. Some commits in this folder are a few years old...
[SuperSU] interminable01:
Hi

I flashed the zip file to Xperia sp cm 13 but it doesn't work and actually hasn't installed
[SuperSU] Sam Nakamura:
Did you use a custom recovery like twrp or cwm? It's not going to work with stock recovery..
[SuperSU] interminable01:
twrp and it was stable zip
[SuperSU] ZRK_NanDRD:
Give this one a try http://xdaforums.com/attachment.php?attachmentid=3807827&d=1468069141
[SuperSU] Sam Nakamura:
What was error message then?

Try to install the app from store separately.. See what happens
[SuperSU] xunholyx:
You need to already be rooted to install the app from the Play Store

---------- Post added at 12:36 PM ---------- Previous post was at 12:33 PM ----------

CM 13 is a pre-rooted ROM, I believe. You shouldn't need to flash SU seperately
[SuperSU] Sam Nakamura:
As cm13 is prerooted you only have to grant root access to application in your settings, developers options and install from play store, grand root permission when demands
[SuperSU] interminable01:
Hi

I haven't installed Google app none of them I hate them

And about error in recovery it was done successfully but in my app nothing is added

Besides I used to install this app to get rid of this sign at status bar #

I knew already that this rom is pre rooted

After all I don't know why the thank button doesn't work

Thank u
[SuperSU] Sam Nakamura:
Yeah ok, you can simply install elsewhere if you want to avoid Google, for example

http://www.apkmirror.com/apk/chainf...lease/supersu-2-49-beta-android-apk-download/

Edit: for your general information, screenshot of like button!
[SuperSU] egingell:
I don't understand this fascination with getting likes. At any rate, mine don't look like that. Mine's shaped like a heart (Tapatalk).

Sent from: SGS5 - MM 6.0.1 / SGS4 - LP 5.0.1
[SuperSU] Sam Nakamura:
As the guy stated he doesn't even know how it looks I think it is a good idea to help out, and for my opinion it's a useful way to mark working solutions and efforts of other to support each other..

But nothing should be so important to insist on it, one like more or less is actually irrelevant..

But when I see someone isn't even aware of the like system I am gonna tell..

I use xda app from play store as I don't fallow anything else but xda..

PS: sorry for being off topic..
[SuperSU] franktwoods:
I just installed resurrection remix ROM for my Samsung galaxy mega 5.8 duos (GT-i9152) then installed SuperSU, but SuperSU cannot be detected by root checkers, it says my phone is not rooted. Help please
[SuperSU] Sam Nakamura:
Go settings, developer options and allow root access to applications.. Then try again
[SuperSU] BartVCD:
I just wanted to inform that with the newest firmware (G930FXXU1BPH6) for Galaxy S7 (G930F) autoroot and custom-recovery is not working anymore! So we need a new way to get root!
[SuperSU] Duiesel:
Hello, can anybody help me?
[SuperSU] ecksdeeay:
[MENTION=2787645]Duiesel[/MENTION]

Device?
[SuperSU] Duiesel:
Lenovo Yoga Tab 3 x50m android 5.1.1
[SuperSU] Tone527:
Hi, could some please help me out here. I read a ton of information and my head is spinning. I would like to root my device tonight asap once it’s confirm.

I would like to know which of the two SuperSU to flash to retain radio using TWRP 3.0.2-6 recovery

Do I use the latest SuperSU v2.76 or the BETA-SuperSU-v2.74-2 force encrypt?

And is there a guide on flashing the SuperSU?
[SuperSU] grep_i:
You forgot to tell which device you have or is it in your signature ?

I would go for the latest version myself.

But in your case I don't know if your device is even supported.

Flashing Supersu is not difficult it is straight forward.

In the OP or first post is enough information to successfully flash SuperSU.
[SuperSU] ashyx:
When you post something like this, you need to be more specific. Like device, firmware build, actual issue etc.

Nobody is going to attempt to read your mind here.
[SuperSU] Tone527:
Sorry about that. This is for the HTC 10 sprint version.
[SuperSU] neovision777:
My Mini M8 II S905x is not rooted how do i install SuperSU

My MIni M8 II S905X is not rooted there have been replies on how to install SuperSU and install its binary do i need to be rooted first and after you install SuperSu how do you update binary this is the message i see

[attached pic]
[SuperSU] grep_i:
Have you searched this forum already to see if there's a specialized thread about your phone something like:

http://xdaforums.com/htc-10/help/how-to-root-sprint-t3381844

Please do not quote such a large portion of the first post just refer to it.

Yes you have to first root before using SuperSU it is although a root management tool.

The binaries can be updated through the management app or through custom recovery.
[SuperSU] BrunoJeric:
ramdisc faliure

Hi!

When i try to flash zip file via twrp i get :

-Extracting ramdisk

-Decompressing ramdisk --- Failure, aborting

Anyone knows what should I do?

Xperia m4 Aqua running on stock 6.0.1
[SuperSU] grep_i:
Are you experienced enough to provide a recovery log or logcat, it might be possible someone will take a look for you in the log and answer your question
[SuperSU] BrunoJeric:
[/QUOTE]

Here is my log. I hop someone will find answer :)

Edit: Here is txt file
[SuperSU] grep_i:
Here is my log. I hop someone will find answer :)

Edit: Here is txt file[/QUOTE]

Can you tell if your bootloader is unlocked also are you aware that it is trying to install systemmode or is this what you wanted instead of systemless
[SuperSU] BrunoJeric:
My bootloader is deffinetly unlocked. And that is part where i got lost while researching...i read that superSu.zip will automaticaly decide is it going for system or systemless root depending on android version...since i am on Marshmellow it should have been systemless
[SuperSU] tag68:
Some devices need manually be configured. For instance for many Motorola devices you need to manually activate systemless. May be that changed for Motorola with SuperSU 2.76 (probably not), but at least the version before needed that echo line in TWRP to configure systemless, otherwise you end in a bootloop.
[SuperSU] BrunoJeric:
I didn't end up in bootloop....my phone normally reboots as if nothing happened....how to activate that systemless withe that echo line if you know?
[SuperSU] grep_i:
Type this in a terminal before flashing SuperSU.

echo SYSTEMLESS=true>>/data/.supersu

Don't know which rom you have maybe your rom is forcing into systemmode.
[SuperSU] BrunoJeric:
Hi i tried this and unfortunatly didn't work....I'am on stock sony firmwere, latest marshmellow update for xperia m4 qua
[SuperSU] Orochi77:
Systemless Root TWRP and Device Status Custom

Hello Everyone.

Maybe someone can help me here.

I installed systemless root in order to get OTA updates. However my device status is custom.

Here is what I did.

1. Flashed latest TWRP for my phone (g900t1)

2. Did not enable system read only. (not sure why) later went to change it after boot but that didn't help.

3. Flashed latest beta supersu.

I am rooted and my device status is custom and I cannot get OTA updates.

My first question:

1. Is there a way to correct this without going back to stock firmware?

2. What did I do wrong? Is this because of the system read only in TWRP?

3. I figured the point of systemless root is not to touch system partition at all. But then there are many root apps that reply on modifying system partition. So how will this work then?

Thank you for your help.
[SuperSU] grep_i:
Try to find a solution at the following thread.

http://xdaforums.com/m4-aqua/general/guide-t3130092
[SuperSU] sagar846:
[Off Topic] So I was watching a show...

And I found this.

OK I dont know whether you can see the image or not. link : http://imgur.com/a/g7tWw

Mr .Robot Season 1 Episode 3.
[SuperSU] egingell:
That's funny because that package name doesn't exist and System Update wouldn't be asking for root access. It's like TV shows using invalid IP addresses and 555 phone numbers.

Sent from: SGS5 - MM 6.0.1 / SGS4 - LP 5.0.1
[SuperSU] BrunoJeric:
I read that tread.. But nothing seems to solve my problem....
[SuperSU] grep_i:
Sorry mate your problem seems to be device specific, you need to get help in device thread.
[SuperSU] BrunoJeric:
Well it's ok....ty for your time :)
[SuperSU] culiacanazo:
[MENTION=631273]Chainfire[/MENTION], would purchasing the pro at this point b benefit you or go to the company taking over supersu in the near future? Thank you so much greetings from Mexico
[SuperSU] grep_i:
Please don't quote first post, it's so uncool and unnecessary.

People with mobile must scroll endlessly to see the real message.
[SuperSU] culiacanazo:
My bad, thanks for pointing it out
[SuperSU] egingell:
He wasn't just informing you. He was also hinting. He and the rest of us would like you to edit it out of your post.

Sent from: SGS5 - MM 6.0.1 / SGS4 - LP 5.0.1
[SuperSU] grep_i:
You are absolutely right that really was my intention.

So [MENTION=7182553]culiacanazo[/MENTION] will you please do as we asked ?
[SuperSU] Orochi77:
Wondering, if anyone can answer my questions on the previous page.

Thanks.
[SuperSU] egingell:
1. No.

2. Nothing and most likely.

3. Don't use apps that modify the system.

Sent from: SGS5 - MM 6.0.1 / SGS4 - LP 5.0.1
[SuperSU] jimbomodder:
1) delete twrp from internal storage then reboot to recovery and it'll be like you just installed, then swipe to ALLOW modifications

Sent from my GT-I9505
[SuperSU] egingell:
Allowing modifications is what broke OTA. He said first he didn't allow modifications, then he allowed modifications later. At least that's what I read.

Sent from: SGS5 - MM 6.0.1 / SGS4 - LP 5.0.1
[SuperSU] culiacanazo:
Just gonna ask this very questions to my two, very active, rather helpful buddies here
[SuperSU] Orochi77:
I see. Well I ended up installing xposed and a module that fakes system status.

My system status in now official and at least I can check for OTA updates.

Not sure if they will actually be installed properly or at all when times comes.

To clear the TWRP confusion from earlier. I installed TWRP and disabled system read only. Later I came back and enabled it. But by that time it might have been late.

Almost every useful root program modifies system in some way.

Adaway, titanium backup and so on...

It's like saying you are administrator of your pc but cannot write to registry.

Thanks to those who replied.
[SuperSU] egingell:
You cannot apply OTA as far as I know.

There's a version of AdAway that doesn't modify the system. Not sure where it is.

Titanium Backup doesn't modify the system unless you tell it to (convert to user/system app, uninstall system apps). The point is that it isn't required for TiB to function.

Sent from: SGS5 - MM 6.0.1 / SGS4 - LP 5.0.1
[SuperSU] Schrotty35:
The latest supersu dont work with f2fs.
[SuperSU] nunopenim:
I use F2FS and I have no problem

Sent from my GT-I8730 running Slim6 ALPHA 0.9
[SuperSU] Sam Nakamura:
Can't have something to do with f2fs, I run that combination since quite some months with NO problems at all!
[SuperSU] grep_i:
Probably user error or incompatible rom
[SuperSU] interminable01:
Hi

I can't install this app neither normally nor by zip on Xperia sp cm 13

Is there any way to do so?
[SuperSU] Orochi77:
Thank you for your reply.

I might have to redo the whole process.

Is there a way to know for sure which root app modifies system?

Supersu will either grant or deny permission but there is no way to know whether the root app will modify system partition or not.

I am assuming that keeping system read only in TWRP will at least protect root apps from modifying system.
[SuperSU] egingell:
There's really no way to tell for sure.

TWRP doesn't protect anything. That setting only applies when you're in TWRP recovery.

Sent from: SGS5 - MM 6.0.1 / SGS4 - LP 5.0.1
[SuperSU] mjjcb:
Okay. I have a real problem here. I have an LG G3 ls990, and I've been rooted for years with this and other devices without ever having this problem. I do have xposed installed on Xenon HD 6.01. Several builds back, I noticed I was unable to start Titanium Backup. It said it was searching for root.

I flashed the Uninstall SuperSU zip and installed SuperSU 2.74 and SuperSU Pro from the Play Store. Now, when I open SuperSU, it says I have no binaries and my G3 says I don't have root. I'm on the latest TWRP and can access recovery fine. My only backup is several weeks old, and it's from a time when I couldn't open TB but seemed to have all my other root privileges. It's before I flashed the uninstall zip.

I'd like to avoid having to flash a rom and lose everything since my last TB backup. If it comes to that, I'm hoping it will include SU and full root access. No one else in G3 Xenon thread seems to have this problem.

Based on all of this, can anyone say if I can do something to get binaries back so I can at least back up with TB?

---------- Post added at 04:46 PM ---------- Previous post was at 04:20 PM ----------

Geez. Never mind. You'd think I didn't research thus at all, but that's all I've been doing for the last few days. I downloaded the latest zip file for supersu and flashed it. Everything is as it should be. Sorry for wasting the last minute of your lives.
[SuperSU] nunopenim:
It's okay buddy. We all make mistakes.

Sent from my GT-I8730 running Slim6 ALPHA 0.10
[SuperSU] pkelly517:
Not to worry.

If I had a dollar for every problem I solved within 10 minutes of posting a question online, I'd have a lot of dollars.

All my questions look pretty dumb, too, when I know the answer. I promise they weren't dumb when i wrote them.
[SuperSU] mjjcb:
Thanks to both of you. That's it exactly. Search, read, search, read, search, read... post, simple answer occurs to me, regret posting. I knew it had to be something stupid, since I've gone through different devices and countless roms and never run into this before.
[SuperSU] nunopenim:
Sometimes I post my issue and the answer is in it. No worries. Also, if you add the simple thing that fixes your problem, you could help users in the same situation that didn't had the "flick of the switch" you had :D

Sent from my GT-I8730 running Slim6 ALPHA 0.10
[SuperSU] smfilip:
HTC One M9 indefinite reboot loop when I try to install 2.76 via TWRP :(

had to do with 2.65
[SuperSU] teddy0209:
Restore and Start fresh... Or you could try just wiping data then flash...
[SuperSU] smfilip:
tnx for re... I've tried multiple times everything, only older ver works :(

but better that than nothing :)
[SuperSU] teddy0209:
Well, I am an M9 user... And 2.76 was a dependency for previous version of xposed, so I had to find a way to make it work... ?

Edit: I mean systemless xposed
[SuperSU] Mepsipax:
New Version gives me boot loop on OPO with cm13. Flashed an older version again. Any tips what I should do?