yashsingh1/xdaforums huggingface dataset:
[SuperSU] awildsloth:
SuperSU v.2.65 - Purity ROM (CM13 and AOSP based)

Hey guys, everytime I try to update the SuperSU binary I get a bootloop. Does anyone know how to correctly update the binary? :confused:
[SuperSU] grep_i:
Can you first clarify how you update the binary ?
[SuperSU] awildsloth:
I believe I have the option to manually update (correct me if I'm wrong) or update through CWM/TWRP (I'm using TWRP 3.0.0-1). I chose through recovery, all went well, the phone auto reboots and then it bootloops.

Enviado do meu ONE E1003 através de Tapatalk
[SuperSU] grep_i:
Can you download the flashable zip and flash it through recovery yourself and report back what happens.

The flashable zip files you can find by following instructions on first thread
[SuperSU] nicolap8:
Hi,

I installed SuperSU.zip (2.65) using TWRP (2.7) but the app says that can't find su.

The su is present in the /system/xbin directory.

So what is searching the app? It's possible to know which check faulted?

Thanks
[SuperSU] awildsloth:
That's what I did to flash 2.65 and after some days it asked me to update the binaries. Did it through recovery and got a bootloop

Enviado do meu ONE E1003 através de Tapatalk
[SuperSU] c-prodigo:
thanks
[SuperSU] venkatsiddhartha:
I have rooted my Samsung galaxy s5 SM G900H with cf autoroot. . .I got super su version 2.68 with that. . .there is a problem with updating SuperSU binaries. . . can I degrade my super su to version 2.65 from 2.68. . assuper su version 2.65 is stable one. . . ????

---------- Post added at 10:25 AM ---------- Previous post was at 10:21 AM ----------

I have rooted my Samsung Galaxy s5 smg900h running on lollipop 5.0 with cf autoroot via Odin. . . I got super su version 2.68 with that. .I have a problem updaing the su binaries for that version. . .I have root access. . root checker shows positive root. . can I downgrade my super to version 2.65 which is stable one. . .????

---------- Post added at 10:26 AM ---------- Previous post was at 10:25 AM ----------

sorry for sending it twice. . .when I sent it 1st time. .it showed some error. . ????
[SuperSU] grep_i:
Yes that's possible

---------- Post added at 10:54 AM ---------- Previous post was at 10:52 AM ----------

Did you download the zip of the version it is trying to upgrade to and install that through recovery yourself.
[SuperSU] grep_i:
Can you clarify what you're trying to say here, maybe we're missing the clue.
[SuperSU] venkatsiddhartha:
hey man. . can you post or PM me the screen shots of settings in super su app. . I think I have messed up with them./ . . just the settings. so that I could know what should be checked and what else shouldn't be checked. . ..
[SuperSU] awildsloth:
Nah dude I gave up on it, my rom has a built-in superuser that works with everything I want it to work, no point in keeping it now :)

Enviado do meu ONE E1003 através de Tapatalk
[SuperSU] venkatsiddhartha:
any body there. . need little help please. . ..
[SuperSU] grep_i:
Supersu should just work out of the box.

There are no special settings that makes it work.
[SuperSU] egingell:
Please stop bumping threads mere minutes after you post.

Sent from: SGS5 - LP 5.1.1 / SGS4 - LP 5.0.1
[SuperSU] Chainfire:
Not at the moment, no.
[SuperSU] mystical80:
Thank You!!!
[SuperSU] snandlal:
Thanks for the reply. Really likin this better than Superuser. Keep it up.
[SuperSU] mystical80:
If I have to have to reset my phone, will I lose root, or will it stay and I just reinstall supersu from the playstore, because I needed to update .90 that came with the root. I updated supersu within the app which links me to the playstore for future updates.
[SuperSU] ironia.:
Anyone? Tnx a lot
[SuperSU] jahmeego:
@Chainfire, Hi.

i noticed that if u update superSu 0.92 to 0.93 or v1, screen not going off. So is problem with Supersu or with Rom...

i personally checked it, after updating to 0.93 screen keeps on, when i uninstall update screen going of as rules.
[SuperSU] icedeocampo:
I have been using Super SU for all my Galaxy Note.

Recently though, I acquired a cheap Ainol - Paladin with a MIPS processor.

I can install SuperSU from Market, however it FCs once it gets to the updating binary message, and it fails to install.

I'd be happy to provide logs and other important stuff and would really happy if we can make it to run on this MIPS device.

Thanks
[SuperSU] hanzi54:
how did you removed it?
[SuperSU] shaggyskunk:
I'm not sure why there is such concern with removing superuser? On my phone, it just seems to sleep happily & doesn't get involved with anything, there's no logs of it doing anything either. So why is there any issue with just leaving it there?

Sent from, The Eclectic Chair.
[SuperSU] Fallen Spartan:
Was thinking this myself
[SuperSU] nkojic:
Supersu stop working after last update 0,93....still problems with this!!!
[SuperSU] CamoGeko:
Working fine here.

Sent from my HTC One X using Xparent Red Tapatalk 2
[SuperSU] nkojic:
Why i have this problem with supersu when i update it?
[SuperSU] bedtime_with_the_bear:
You have to be more specific. Saying "I have a problem" tells us nothing and will likely lead to your post going unanswered because it is impossible to answer.
[SuperSU] Savok:
I had to revert back to Superuser after having issues with GMail not letting me scroll emails and Netflix not getting to the log in screen.
[SuperSU] ty1993:
Running ICS, Galaxy S3 T-moble. Updated to latest SuperSU and binaries.

I cannot get any program, or the Terminal, to unfreeze packages. I have tried Titanium, Rom Toolbox, and using the pm commands in the Terminal Emulator.

Any suggestions?

Thank you.
[SuperSU] nkojic:
In the post before i wrote everything. If i update supersu to the latest everything is fine but if i use aplication that needs root then it says that supersu stop working?? I did everything even flashing clean rom and update supersu after that and again the same problem??
[SuperSU] georgek_gr:
Gentlemen I have an issue and could use your expertise. After unlocking the bootloader through htcdev.com, I tried to install superSU. It seemed to install OK but as soon as I opened the app it said that there are no binaries installed and superSU can't run. I uninstalled it and installed again but without success. Any idea what I'm doing wrong?

The error message reads "There is no SU binary installed and superSU cannot install it. This is a problem!" duh!

(forgot to mention, the device is an HTC ONE X)

Any help is much appreciated!

Thanks

G.
[SuperSU] bsoplinger:
You need a flashable version to start. You can't just install it from the market. SuperSU and the older superuser apps are just a wrapper, a buffer between apps that need root access and the program that does the root operation. You need to get that program (su) installed. Hence the need for a flashable zip.

The thread that you followed to HTC unlock most likely had instructions on how to flash a custom recovery which will allow you to flash updates and ROMs. You need to get that done before you can do anything else.

I know that the OP had a flashable version. If it doesn't work for you then you'll need to go the more tedious route of flashing the older superuser then upgrading to SuperSU. Try to flash the zip in the OP.

Sent from my PG86100 using Xparent Purple Tapatalk 2
[SuperSU] Gablinsangan:
I cant disable my knox but I dont have a knox icon in my phone. "Failed to disable knox." How can I fix this?
[SuperSU] ktmom:
SuperSU doesn't have anything to do with Knox. You're most likely to get help by searching/posting in your device thread.
[SuperSU] grep_i:
Knox can prevent Supersu from doing its job.

---------- Post added at 10:38 AM ---------- Previous post was at 10:33 AM ----------

In a terminal you can try the following commands:

su

pm disable com.sec.knox.seandroid

If su does not work in terminal on phone you can try and replace it with "adb shell" from PC with phone on USB cable.

Or use this script from XDA

http://xdaforums.com/attachment.php?attachmentid=2352990&d=1382869026
[SuperSU] kamikaze702k:
Does the 2.71 work on lollipop? I just flashed the zip but it removed SuperSU completely from my device, had to install again from play store then flashed the 2.68 again... Thanks
[SuperSU] grep_i:
I have no clue flashed it on marshmallow and that seems to work
[SuperSU] jwds1978:
With exception of an empty Logs tab within the UI, it works fine for me.
[SuperSU] LoverBoy2415:
Yup its working only..no issues here..
[SuperSU] panjaby:
Are you using the latest TWRP, after installing the zip when rebooting twrp should ask to swipe to root your device. Swipe away and it should work fine.

I had a similar trouble as yours when i didn't allow twrp to root my device the first time.

Hope it helps
[SuperSU] egingell:
You're suggesting he let TWRP install root after numerous posts and the SuperSU install log explicitly stating that one should *not* do that?

Sent from: SGS5 - LP 5.1.1 / SGS4 - LP 5.0.1
[SuperSU] panjaby:
I was under the same impression and never tried it myself until last night when I tried updating to 2.71 and it worked for me. I had the same problem as described by [MENTION=4161949]Kamikaze.[/MENTION] So im speaking of personal experience. Im using note edge running lollipop.
[SuperSU] kamikaze702k:
I've never let twrp "root" me, because I'm already rooted using chainfire root. I've been rooted for over a decade lol, I found a version of the 2.71 zip that works

Thanks anyways
[SuperSU] panjaby:
Mind sharing the link, will come in handy next time.

Cheers
[SuperSU] egingell:
If you let TWRP root your phone, I guarantee you don't have Chainfire's SuperSU anymore. You have whatever TWRP installs and it's installed to the system.

Sent from: SGS5 - LP 5.1.1 / SGS4 - LP 5.0.1
[SuperSU] lmma97:
I have a problem regarding SuperSU.

I am using Galaxy Note 3 (N9005) Lollipop version 5.0 and I recently rooted it with this n9005-cwm-recovery-6.0.4.7-kk(0125) and using SuperSU updated from google play. I tried opening SuperSU as per instructions but it said

"There is no SU binary installed, and SuperSU cannot install it. This is a problem! If you just upgraded to Android 5.0, you need to manually re-root - consult the relevant forums for your device!"

Help me in the noob way please, thanks!
[SuperSU] LoverBoy2415:
Try Flashing the Stable Zip v2.65 in your Recovery ..
[SuperSU] Oneplus#:
Hi there is a SuperSU version that work on 6.0.1 traditional write on system because systemless root give me a lot of problems thanks
[SuperSU] MetalDroid01:
What's the good version for Android lollipop 5.1 Moto G Falcon stock rom ?
[SuperSU] bsw11:
When this app pops up its dialog to enable an app, the dialog is dead... No touches work at all. It's there a fix for this? I tried 71 with the same result.
[SuperSU] Ja_som:
Try to disable "Tapjacking protection" in SuperSU settings.
[SuperSU] Paulo SGarcia:
I must confess I didn't read all the 1041 pages from this thread, so probably the question I'm about to ask was already made and answered, but where it goes.

Does this version woks with AOSP 6.0.1?

I ask this because I tried to flash it through TWRP in my LG G Pad V500 and I got an error ("Secure Booting Error! Cause: boot certification verify") booting (soft brick). The solution was to flash the rom again.

Any help?
[SuperSU] Pkt_Lnt:
That's why they invented search engines - so you don't have to read the whole internet to find something. :laugh:

http://xdaforums.com/search
[SuperSU] grep_i:
You can find the download link at the first post
[SuperSU] doppelhelix:
Before flashing SuperSU run this in a root console (via adb or TWRP):

echo "SYSTEMLESS=false" > /data/.supersu
[SuperSU] bravonova:
Stable V2.65. :)
[SuperSU] Oneplus#:
thanks very much i will try after
[SuperSU] uraharajuku:
SuperSU installation failed

Guys please help me. I flash supersu in latest twrp (TWRP 3.0.0) nothing wrong all smooth. then when i open SuperSU it ask me to update su binary. but when i update it say failed. i try to reflashed it but same result. i also try another version of supersu (supersu 2.46/2.65/beta 2.71) but all got same result. check with root checker and root is fail due to su dialog not promt. please help me guys. what im done wrong?:(
[SuperSU] Spartacus500:
Hello, on my Galaxy S4 I9505 4.4.2 the most current version 2.66 Beta, from 2.67 to 2.71 I had a problem with the update binary files is there a solution to this problem ?
[SuperSU] rouyal:
What does this mean? I thought SuperSU is what enables root on a device.
[SuperSU] LoverBoy2415:
Nope SuperSU is a Root Management App ..it's not an Root Enabling App.. It Roots your Device Unless You Are Using Marshmallow+ in that You Can Get Root Access & Management via SuperSU ..but Below Marshmallow(<Lollipop) you will need other methods like Apps and etc to Gain Root Access.. In this SuperSU Doesn't Root ,it Gives Only Root Management... :)
[SuperSU] Mesmurized:
Interesting. So in the case of stock with SuperSU, what roots the device?
[SuperSU] doppelhelix:
The unlocked bootloader. Unlocked device > custom recovery > SuperSU.
[SuperSU] grep_i:
Correct me if I'm wrong are we talking about the Supersu apk or flashable zip files ?

My understanding was always that the flashable zip files or binaries are the rooting part and the Supersu apk the management side.
[SuperSU] doppelhelix:
Sure. But to flash the zip you need an unlocked device & custom recovery.

Technically you have root access if you are unlocked but SuperSU will give you the whole infrastructure to use it outside recovery or adb.
[SuperSU] grep_i:
I always thought that unlocking the bootloader was just to be sure that the provider/carrier could not undo your rooting actions and you basically are freeing your device from the provider/carrier restrictions after which you could get permanent root. Thanks man learned a lesson here once again.
[SuperSU] Dafta:
Flashing with fastboot update supersu.zip. Yay or nay?
[SuperSU] spainter:
Flash with custom recovery ie TWRP
[SuperSU] Dafta:
That's not really possible for me right now. I've got a Gsmart Classic Pro, and installations of custom recovery failed so far.
[SuperSU] daniu:
Hi chainfire,

There had been discussions about supersu for s2 - cm13 and iirc you said that you are working on it.

Are you still working at it? Any progress?

Regards

Sent from my x-phone using brain 2.0
[SuperSU] drezz2:
having android 4.4.2, worth upgrading to 2.65 SuperSU? or nothing changes for this version of android?
[SuperSU] Pkt_Lnt:
Changelogs in posts # 3 & 4 will let you decide if it is worth it for you.
[SuperSU] spainter:
I upgraded my old xt926's via the playstore just to keep up with what was current. It is installed in system mode and works well. Not really any changes for the older phones on 4.4.2.
[SuperSU] jjakajonas:
What's the deference between system and system-less install of superSU?

I have a system-less install on my CM13 device at the moment and need to know if I need a system install and how to do it if so.
[SuperSU] egingell:
1. Where and how it's installed.

2. Apps which look for "/system/bin/su" or "/system/xbin/su" instead of just "su", will have to be fixed.

Sent from: SGS5 - LP 5.1.1 / SGS4 - LP 5.0.1
[SuperSU] jjakajonas:
Okay.. So in shot. Nothing else than the placement of the install...
[SuperSU] doppelhelix:
Systemless installation won't break (stock) OTA's. That's the main advantage. OTA won't work if system is modified.
[SuperSU] jjakajonas:
Okay. I will mess a bit more around with it and see what will happened.
[SuperSU] grep_i:
Systemless works with Android pay where system mode won't work with Android pay. So if you need root and need Android pay you have to use systemless otherwise you can stick to system mode. Most people I know that stays with system mode, do it because than root will survive dirty flashing newer updated roms and factory reset.
[SuperSU] jjakajonas:
That's one of the reasons why I want the system one.

I don't use android pay anyway. I don't think there's support for it here in Denmark.
[SuperSU] grep_i:
Than you will have to search for modified version with system mode enabled because is systemless is default for quite some time now
[SuperSU] jjakajonas:
Okay. Tanks.
[SuperSU] Fif_:
I don't think any modified version is needed.

To force SuperSU into system mode, I believe all you have to do is to run the following as root:

echo SYSTEMLESS=false >> /data/.supersu

After that step, you (re-)install SuperSU.
[SuperSU] mrrocketdog:
also maybe something here :what:

http://xdaforums.com/showthread.php?t=3286120

"err on the side of kindness"
[SuperSU] android08:
I installed SuperSU on my M9 running Marshmallow and all worked fine.

After that, because I just needed the root to get S-Off, I unrooted SuperSu via the App.

In the following few days I realized that there is a folder named "supersu" under / which you can see in TWRP-Recovery but not for example in the ES Manager.

I tried to flash different versions of SuperSU to unroot them again what didn't work.

When I try to delete the folder he just regenerates.

Now I flashed a RUU via fastboot which I thought would be a safe method to delete everything but this folder doesnt want to go away.

I really have no idea what to do, maybe it is a generell folder in Marshmallow or the fastboot-method doesnt work and I have to do it again with a sdcard...?

Would be great if you guys could help me and explain me the phenomenon, I'm really frustrated :crying:
[SuperSU] spainter:
Try this page osm0sis unSU script: http://xdaforums.com/showpost.php?p=63615067
[SuperSU] android08:
The thing that I can't understand is that even a RUU didn't delete the folder...

How can that be?
[SuperSU] spainter:
RUU was built for a one size fits all and before systemless root came out. If you look on that page osmOsis says that the best way to remove systemless root is to flash the boot image file for the device and version of android you are running. Also osmOsis wrote this for SuperSU. Just follow his instructions on the link I gave you.
[SuperSU] android08:
As far as I know the Boot.img is included in the RUU.

If I'm wrong correct me but I can cleary see the Installation of the boot.img in the course...
[SuperSU] spainter:
Well it sounds to me you have it figured out.
[SuperSU] android08:
I'm on CM at the moment but flashed the RUU before.

Should I just run the unsu.zip now or what else should I do?
[SuperSU] avicohh:
Hi [MENTION=631273]Chainfire[/MENTION]

I'm trying to make a pre-rooted firmware for Galaxy J1 Mini (J105H), by repacking the system.img with the SuperSU binaries.

I used the last stable version (2.65), and I followed the comments in the update-binary file.

The device running android 5.1.1 version, and he has armv7 cpu.

Here is what I did.

Unpack and mount the system.img under linux.

Copy the files from the folders common and armv7 to the right places.

Run this script I made to set the permissions and the SELinux context to the new files, change the app_process, and create the symlinks. (I run it from inside the system folder)

#!/sbin/sh
rm bin/app_process
mv bin/app_process32 bin/app_process32_original
cp bin/app_process32_original bin/app_process_init
ln -s /system/xbin/daemonsu bin/app_process
ln -s /system/xbin/daemonsu bin/app_process32
ln -s /system/etc/install-recovery.sh bin/install-recovery.sh

chmod 755 app/SuperSU
chmod 644 app/SuperSU/SuperSU.apk
chmod 755 bin/.ext
chmod 755 bin/.ext/.su
chmod 755 bin/app_process32_original
chmod 755 bin/app_process_init
chown 0.2000 bin/app_process32_original
chown 0:2000 bin/app_process32_original
chown 0.2000 bin/app_process_init
chown 0:2000 bin/app_process_init
chmod 755 etc/install-recovery.sh
chmod 644 lib/libsupol.so
chmod 755 xbin/daemonsu
chmod 755 xbin/su
chmod 755 xbin/supolicy

chcon u:object_r:system_file:s0 app/SuperSU
chcon u:object_r:system_file:s0 app/SuperSU/SuperSU.apk
chcon u:object_r:system_file:s0 bin/.ext
chcon u:object_r:system_file:s0 bin/.ext/.su
chcon -h u:object_r:system_file:s0 bin/app_process
chcon -h u:object_r:system_file:s0 bin/app_process32
chcon -h u:object_r:system_file:s0 bin/install-recovery.sh
chcon u:object_r:zygote_exec:s0 bin/app_process32_original
chcon u:object_r:system_file:s0 bin/app_process_init
chcon u:object_r:system_file:s0 etc/install-recovery.sh
chcon u:object_r:system_file:s0 lib/libsupol.so
chcon u:object_r:system_file:s0 xbin/daemonsu
chcon u:object_r:system_file:s0 xbin/su
chcon u:object_r:system_file:s0 xbin/supolicy

Finally, I repack the the partition to a new system.img, make a tar and flash it by Odin.

For some reason after I flash the new system.img the device stuck in boot loop.

I double checked the new img by unpack it again, and all the permissions and SELinux context are exactlly as they should be.

After some testing It turned out that the problem is in the app_process, I did it all without touching the app_process and the device work's fine but with no root of course.

I tried also the last version (1.71), with the same result.

Anyone know what cause the problem?

What I'm missing here?

I would very appreciate the help.

Thanks.
[SuperSU] avicohh:
Well..

After a very long night I finally found this Thread.

http://xdaforums.com/apps/supersu/wip-android-6-0-marshmellow-t3219344

I didn't actually believed taht it has nothing to do to with this, but I gave it a chance and it turned out that this was exactly what was needed to solve the problem.

I patched the sepolicy file and repacked the boot.img, and now the device and up and rooted.

Thank you very much [MENTION=631273]Chainfire[/MENTION] :)
[SuperSU] xxfwmxx:
Stupid question time. What is the later systemless version of supersu?
[SuperSU] jjakajonas:
What terminal app wuld be the best to use for this type of commands?
[SuperSU] doppelhelix:
Since you have to have root access to write to /data, there are two possible ways. Either via adb or with the terminal provided by TWRP.
[SuperSU] jjakajonas:
Thanks. I think I will give Twrp a try.
[SuperSU] uraharajuku:
nvm i find the solution with the oldest trick. for anyone with the same problem here the solution https://www.youtube.com/watch?v=HNi1j_OzMrk&nohtml5=False. thanks btw and u r welcome

---------- Post added at 09:59 PM ---------- Previous post was at 09:56 PM ----------

https://www.youtube.com/watch?v=HNi1j_OzMrk&nohtml5=False. u r welcome
[SuperSU] Spartacus500:
Link youtube not work
[SuperSU] Pkt_Lnt:
This is your YouTube link.
[SuperSU] [NUT]:
Sony Smart Watch 3, running MM 6.0.1 with 2.71 installed. It's unfortunately not working...

The accompanying logcat is attached. I hope you are able to fix it easily.
[SuperSU] kostassfirakis:
is it possible to update supersu via downloading the latest version zip and flash it with terminal app and which are the commands? I am asking because a tablet I have doesnt let twrp to be installed
[SuperSU] zzenyoo:
FlashFire from Play Store
[SuperSU] uraharajuku:
there i fix it

---------- Post added at 05:58 PM ---------- Previous post was at 05:57 PM ----------

ops sorry.. there i fix it
[SuperSU] uciha753:
I have a problem, my supersu doesn't prompt root acces after prompt 3 app. So i just can gain root access for 3 app only.

My device : Samsung J500g

Supersu v2.71
[SuperSU] Nur_Alom:
"BETA-SuperSU-v2.71-20160331103524"

??

in This version all app get root permission bt ES File Explorer don't get root permission
[SuperSU] Pkt_Lnt:
That has been reported and solved in the BETA thread.
[SuperSU] LoverBoy2415:
Well..i don't know what's the issue with ES File Explorer & v2.71 as some users Stated .. But for me its Getting Root Permissions properly like other apps .. No issues Here With Root Functions on ES_FE v4.0.4.9 ...

..

Sent from my Nitro
[SuperSU] kh34d:
If you on marshmallow, you must allow root access for "ES File Explorer" [emoji4]
[SuperSU] Noe83:
Hello, I got a lollipop 5.1 China phone (UMI iron pro) who come pre-rooted with SuperSU installed, all it's fine. Now I see an update on play store, can I just install it or have I to do a particular procedure?