yashsingh1/xdaforums huggingface dataset:
[SuperSU] nbi1:
how to downgrade?

When I first rooted my phone I wasn't aware of some of the gotchas.

A rather big gotcha is that v2.65 is incompatible with the LG G2 D801 Autorec app used to install TWRP. Supposedly a work around is to basically start over by totally unrooting the phone and installing an older (pre 2.6x) version of SuperSU.

For me that's a non-starter as rooting the LG G2 D801 30c was an extremely laborious and painful process. Not something I would wish on anyone.

So, given that I do NOT have a custom recovery and that I installed 2.65 from the playstore is there any way to downgrade/shoehorn in place an older version without unrooting the phone? Alternatively if you know of a way of installing TWRP that keeps 2.65 intact and doesn't resort to adb/fastboot please let me know. Please don't suggest Flashify as there are far too many bricking reports involving the LG G2.

Many thanks.

UPDATE: Downgrade not needed. Simply unchecked "Mount Namespace Separation" in SuperSU settings.
[SuperSU] Deltadroid:
Checksums are already built into signed zip files. Just turn on zip verification in your recovery.
[SuperSU] AtAM1:
Encryption on Rooted Devices

Hi everyone

I believe I may have found a workaround to why encryption fails on rooted devices on Android 6. Flashing SuperSu results in the boot image being modified which is causing the encryption process to freeze due to some pre-encryption initialization checks that fail.

The solution is simple (

works on an already rooted device

):

Important: please carry out a nandroid backup and copy the backup files to your pc/mac first as this was tested and verified on cm13/bacon

1. Flash the original boot image (boot.img) from the zip archive of the rom that is currently installed then reboot normally

2. Encrypt the device and verify encryption is working 100% by rebooting and entering your password/pin/pattern

3. Reboot into Recovery and 'adb sideload' or flash SuperSu zip (tested with recent Stable and Beta releases) then reboot normally

4. You will be presented with the encryption password prompt twice which is normal - don't worry, this is only for the rerooting process.

5. The device should now have booted to the lockscreen. Verify encryption and root are enabled ;)

Hope this helps those that have struggled to encrypt their rooted devices.
[SuperSU] jjakajonas:
That explains why i can't encrypt my device.

I have to try this guide later today and see if it works for me.
[SuperSU] Fif_:
Device encryption fails with SuperSU installed because /data cannot be unmounted when the device is about to perform the initial encryption pass.

Yes, uninstalling SuperSU, encrypting, and reinstalling it works.

This has been broken for ages for me.
[SuperSU] Surge1223:
These ideas of it being Chainfire's responsibility of making sure systemless survives a dirty flash are ridiculous imho.

I know CM is busy making a theme engine, but unless they plan to port audit2allow and libselinux.so with policy edits, I think supersu should be high on their priority list rather than relying on their users to figure it out.

Just tell your CM maintainer to edit the releasetools and other python files for updater script and add a simple check if systemless was previously install and if so to echo the commands needed (using the updater script to do this, or addon.d)

Then make sure that the order is changed so kernel is flashed before supersu.

That's roughly how I did it.
[SuperSU] permutations:
I updated v2.46 to v2.65 on a Nexus 10 through TWRP and it hosed my installation - no longer can boot.
[SuperSU] Savage01:
I have a Galaxy S5 SM-G900i running the india version of Marshmallow 6.0.1 and have flashed TWRP via ODIN and then flashed latest SUPERSU.zip via TWRP and now i have root access! Great work, keep it up.

I do believe i installed an earlier version ( System SU )before flashing the latest ( Systemless ) will this cause any issues?
[SuperSU] permutations:
I upgraded Android and when I reinstalled v2.65, it again hosed my Nexus 10. I'm backing off to v2.46, which has been working fine for me.

I did a search, and I saw several other reports from people with Nexus devices (all kinds, not just Nexus 10) about v2.65 causing hangs.
[SuperSU] J.P.:
boot loop

Hello i have a galaxy s7 edge.

I have the orginal stock rom on it.

Now i try the option in SuperSu Full unroot but now my phone is in a loop .

It's go samsung galaxy text and off and then the samsung galaxy text and of.

I can come in download mode and in TWRP.
[SuperSU] HypoTurtle:
With system-less root is there any way of 'adding' a new file to a ro system.

i.e. mount -o bind .. works binding from one file to another; but is there a way introduce a new file/path into /system?
[SuperSU] egingell:
No.

Sent from: SGS5 - LP 5.1.1 / SGS4 - LP 5.0.1
[SuperSU] permutations:
BUG REPORT: SuperSU v2.65 causes boot hang

Bug Report

My previous bug report didn't contain full info - here's everything all together.

START: Nexus 10, Android 5.1.1 (mantaray-lmy49f), unlocked, rooted with SuperSU v2.46

Updated to SuperSU v2.65 through TWRP

On reboot, tablet hung at colored sparkles - no longer could boot.

Upgraded to April 2016 bug fix (Android 5.1.1, mantaray-lmy49j)

Flashed SuperSU v2.65 through TWRP

Could not reboot to system - would only boot into recovery

Reapplied April 2016 bug fix and allowed system to reboot before rooting

Tablet rebooted fine - and erased Recovery partition in the process, per usual (why?)

Reflashed TWRP, then flashed SuperSU v2.46 (previous stable version)

All is well.

SuperSU v2.46 works fine on my Nexus 10 running Android 5.1.1.

SuperSU v2.65 causes my Nexus 10 running Android 5.1.1 to hang - no longer can boot.
[SuperSU] ak117:
Hi everyone i want to know when i flash the super user on cm 13 my battery starts to drain quickly. But if i uninstall the app the battery consumption gets back to normal. I tested this twice my phone is still rooted but i uninstalled the super user app.

Can someone help me what would be the problem
[SuperSU] Rix70:
Please guys,

I have to reflash (dirty) my rom for solving audio issue.

Now I tried to update SU to 2.71 from 2.65 but the phone go in bootloop ..

That's strange because I make the same thing in the first/clean installation, same zip files but this time go into boot loop.

I'm on M9/viper rom..

Any solution or advice please?

Thanks in advance

Inviato dal mio HTC One M9 utilizzando Tapatalk
[SuperSU] teddy0209:
Just stay on 2.65
[SuperSU] Rix70:
But this version get twrp SU message after every flash, or I wrong?

Inviato dal mio HTC One M9 utilizzando Tapatalk
[SuperSU] Pkt_Lnt:
Upgrade your TWRP and you will not get that message. It is TWRP, not SuperSU.
[SuperSU] egingell:
I have TWRP 3.0.2-1 (the latest) on my S5 and I still get that message. I know it's not a SuperSU problem, but it's still not detecting systemless... at least not on my phone.

Sent from: SGS5 - LP 5.1.1 / SGS4 - LP 5.0.1
[SuperSU] Pkt_Lnt:
That was supposed to have been fixed in TWRP 3.0.0-0 at least in MM, maybe not in LP or the N preview. (?)

https://twrp.me/site/update/2016/02/05/twrp-3.0.0-0-released.html
[SuperSU] egingell:
I don't know, but it does offer to install "SuperSU" by name.

Sent from: SGS5 - LP 5.1.1 / SGS4 - LP 5.0.1
[SuperSU] RK_D2502:
Kingroot Services/KSysService

Hello Chainfire and fellow SUPERSU user. I have XZdual recovery and SuperSU 2.65 installed. While fiddling around with my phone, i came across Process Stats, Lo and behold, ran into com.kingroot.kinguser:services consuming 97% of system resources. How can I delete this?

I am still rooted with SuperSU. See attached file for reference. Disable Service apk could not detect or pick up com.kingroot.kinguser:services. Even titanium. I have no idea where this is coming from.
[SuperSU] egingell:
Clearly, you still have King Root installed. Go to any command prompt, switch to su, and execute the following:

pm path com.kingroot.kinguser

This should tell you where the apk is. Delete it and its parent folder if it's not "app" (e.g. If "package:/system/priv-app/Kingo/pkg.apk" is returned, then delete the folder /system/priv-app/Kingo". If "package:/system/priv-app/Kingo.apk" is returned, then just delete "/system/priv-app/Kingo.apk").

Then reboot.

Caveats:

* If "package:/data/anything" is returned, then repeat after rebooting.

* You don't need to do the pm command, you can, if you prefer, just scour the /system/app, /system/priv-app, and /data/app folders for files/folders with "king" in their names (note: Candy Crush Saga and Candy Crush Soda will also have "king" in their names - you can keep those. :p).

Sent from: SGS5 - LP 5.1.1 / SGS4 - LP 5.0.1
[SuperSU] RK_D2502:
pm path com.kingroot.kinguser

says path not found.
[SuperSU] egingell:
It shouldn't. If the app isn't installed, nothing is returned... literary nothing.

Try,

pm list packages -f com.kingroot.kinguser

Sent from: SGS5 - LP 5.1.1 / SGS4 - LP 5.0.1
[SuperSU] Conan179:
hello@all, i have the stock rom P605XXU1EOI5_P605VFGEOI2_P605XXU1EOI5_Home on my p605 and rootet sst with CF-Auto-Root-lt03lte-lt03ltexx-smp605.

because not all appps become root acces, the apps say "your device has not root" 2/3 apps become root acces.

i dont know what i can do, i flash the stock roms any time, the cf auto root any times, is the problem supersu?
[SuperSU] RK_D2502:
and yeah, i did the scouring, no luck. hehe Used ES File Explorer, Total Commander, Root Explorer, I can't seem to have search returns. Tried king, ku, kr,. No idea where this leech is hiding. Installed malware bytes, some av apk, com.kingroot.kinguser will stop. Then once I unistall those security programs, kingroot shows itself again. I don't understand some of it myself.

Is there any workaround if I can't search the said service via explorer and any command prompt?
[SuperSU] egingell:
Well, then I don't know. Maybe some app uses that as its service name for whatever weird reason.

Sent from: SGS5 - LP 5.1.1 / SGS4 - LP 5.0.1
[SuperSU] jlb1959.01:
Ok ,new to this so don't jump on me--- if kroot works as a temp root on MM vs985 can I use supersume and over ride kroot,i was told no,but I didn't want to explore and get stuck in bootloop..I'm sure you understand what I'm getting at,in other words there is no rooting vs985 on MM but if you can get temp root( until phone is rebooted), then why can't supersume over ride kroot and gain full root that way?? Just a thought..
[SuperSU] alessa:
hello ,its possible to have the 2.68 for my gs6 6.0.1?

ok ,find
[SuperSU] Exile1975:
I think kingroot, like SuperSU patches your kernel to start it's service. Try to flash a stock kernel and reroot using only SuperSU.
[SuperSU] Ningyou Higeki:
Hello all, I flashed a custom ROM for Sony Xperia Z2 based on stock 6.0.1, and I tried to update SuperSU in it by flashing the latest zip version, but I failed and lost root every time. What can I do to solve the problem? Thx in advance.
[SuperSU] shoey63:
Sony uses elf images for the kernel (except for Z3 concept firmware). Not compatible with systemless supersu. Consult your device forums for a workaround.
[SuperSU] Ubimo:
Some apps like ES file explorer don't work with systemless SuperSU. Is there any workaround on 6.0.1?

Edit:

That did the trick: http://xdaforums.com/showpost.php?p=66140836&postcount=5493
[SuperSU] spainter:
http://www.androidpolice.com/2016/0...dated-with-super-shady-speed-charging-adware/

Try solid Explorer or Root Explorer they don't cost much and they are not turning their apps into crap.
[SuperSU] Pkt_Lnt:
Read this about compatibility and old poorly coded apps.

https://plus.google.com/+Chainfire/posts/N6EARb8LF3d
[SuperSU] NYLimited:
Chainfire is right when he leaves the compatibility switch off. The sad part is that many are using software which should have been updated or deprecated long ago (like Secure Settings, which was last updated about a year and a half ago) and I'm not aware of alternatives to them. It is a tough choice sometimes.
[SuperSU] Pkt_Lnt:
Agreed. I am using Secure Settings on 6.0.1 with SuperSU 2.68 as /system root on a custom rom, and 95% of things still work. There are some plugins recently and some shell scripts that keep it functional. It is too bad it has not been updated, but the dev warned that "real life" was getting in the way. Since I run a custom rom, no worry about updates or OTA failures for me. Systemless is the future it seems, but for now System root is still functional for its own reasons.
[SuperSU] NYLimited:
I was under the impression that SU pretty much had to be systemless on 6.x.

Real life is fine and well but the change to accommodate systemless is a one line change (according to Chainfire, not me). Of real life truly prevented me from publishing a one line change I'd publish the source and be done with it. Anyway..
[SuperSU] Chainfire:
He's running a custom ROM, which can come with a custom kernel, which in turn may allow SU to run from /system.

It's only stock/manufacturer 6.0 firmwares that require this. With custom, it depends on the author.
[SuperSU] belek1979:
Solid Explorer from NeatBytes and Root Explorer from Speed Software?

Which one do you recommend?
[SuperSU] rickbosch:
root explorer might not be the prettiest, but it's never let me down.
[SuperSU] LeftHandedWave:
I'm a fan of Solid Explorer.
[SuperSU] spainter:
I like and have purchased both. I do use Root Explorer the most just because I have used it for a long time, and works great on all my devices. I use Solid Explorer too, and it works well to. Its like having the old favorite coffee cup that you just find you reach for it out of habit instead of the shiny new one that you just got:D
[SuperSU] grep_i:
Although it's fine to know which file explorer you all like, mine are "total commander" and "root browser".

This is a little bit off topic, please let us go back on topic.
[SuperSU] Ja_som:
DELETED :)
[SuperSU] jwds1978:
I've always preferred Root Explorer myself.
[SuperSU] sayedhamidfatimi:
I'm using solid explorer right now, recently moved from root browser and es file explorer, it's a very good replacement, nice clean design, no pop ups, options for customisation and does the job, have you given it a go?
[SuperSU] ioy:
I've the same problem on tablet Huawei MediaTab T1

It looks like Huawei puts into its devices some sort of GUI overlay which strictly controls what applications can do on the screen: have you seen any other application's pop-up window... except of KingRoot? ;)
[SuperSU] spainter:
Try turning tapjacking protection off in the SU app.
[SuperSU] ioy:
[MENTION=3137037]spainter[/MENTION], I've already tried, what [MENTION=7318693]tolux1[/MENTION] did and many more, after this rebooted device and so on... Have you any other suggestions maybe, please?

Or there's some special way how it needs be done...
[SuperSU] spainter:
Other than rebooting after the change no special way
[SuperSU] ioy:
As you can see there is something else what causes the issue...

Besides, tapjack protection works in the way it prevents receive some taps, while doesn't influence popping up prompt windows themselves.

And the issue in question consist of not appearing prompt windows at all,

and apparently any popup windows, e.g. so called toasts.

It seems, something from Huawei prevents popping up windows of non-Chinese apps ;) it's my guess, as for instance KingRoot works correctly... What about other rooting applications e.g. superuser?

The issue in question is pretty important issue. The situation every app whichever wants root gets it is unacceptable, isn't it?

This is why if no solution is found for Huawei phones/tablets it's necessary to find other root provider. Which one please? KingRoot, Kingo, superuser, supersu or maybe any else? There are several alternatives on PlayStore. However please provide some hints how to switch neatly from SuperSU to another app?
[SuperSU] Yudh:
Are there any issues with the latest version of flashable zip

10.05.2016 - v2.72 - BETA

I am on marshmallow resurrection remix rom v5.6.8 based on Cm 13 r30

✌
[SuperSU] drs22:
Nope
[SuperSU] grep_i:
Are you aware you are asking about beta in the stable thread, better ask your question in the beta thread[emoji4]
[SuperSU] MarcusBremen:
ok, need sum help... running cm13 with 6.0.1 on my moto g 2014,

installed supersu 2.65 and i'm not able to get "adaway" run properly...

it says "su binary has to be updated or if i'm rooted"...

i have root and already did the workaround from the net (installed the busybox by meefik and rebooted) and still, no change... reflashed the zip, same result...

i would be grateful for any hint and tip...
[SuperSU] Pkt_Lnt:
From post #1

http://xdaforums.com/apps/supersu/support-update-failures-t2907365
[SuperSU] ioy:
Please respond to
[SuperSU] georgek_gr:
Installing the .zip from CW did the trick! Much appreciated buddy :)
[SuperSU] shaggyskunk:
I'm pretty sure that I had read that another member, had suggested that you could make supsrSU a system app using Titanium. I tried searching for the guys name, so that I could link his post. But for me at least the search feature on Tapatalk & xda premium seems to not really working?

Sent from, The Eclectic Chair.
[SuperSU] dr.ketan:
Install supersu.from market

Then open titanium, find supersu on list, long press n select convert to sys application
[SuperSU] Pons:
I think the newer versions of Titanium hide SuperSU from itself for security reasons, the same reason they've always hid Superuser.
[SuperSU] bsoplinger:
I use link2SD for additional storage. However it has app2sd and freeze and user <-> system conversion operations also. Perhaps you could use that to do what you need ignoring its link2SD functionality.

Sent from my Sprint Evo View 4G (PG41200) using Xparent Purple Tapatalk 2
[SuperSU] shaggyskunk:
I've got the 17 June update of Titanium, and both superuser elite & superSu are there. I'm not sure if those are just the keys though? But the option to convert to a system app is still there.

And that member that I mentioned in my previous post, was none other than Dr Katen.

Once & for all, is there any reason why you shouldn't both superuser apps residing on your phone... I'm not sure if a definitive answer has ever been given, or explained?

Sent from, The Eclectic Chair.
[SuperSU] neokv:
i use v0.93

after install i hv su icon(from none)

i cant up date binary(installation failed)

but its still grant app

this mean i didnt get full root yet right?

what should i do to get full root.

thanks you
[SuperSU] Pkt_Lnt:
Having both on the phone will be fine in my experience. I am testing a couple ROMS, so frequent new flashes and they come with superuser. Once I install SuperSU (and Pro), I use root explorer to delete superuser from /system/app. After deleting, clearing cache and dalvik in recovery, and reboot, my phone seems quicker in response. I have toast notifications off in SuperSU, and it might be a placebo effect, but I like it.
[SuperSU] ArmanUV:
Doesn't the cwm version in OP delete superuser.apk? I always flash the OP version after rom flashes, then update binaries with supersu pro after boot.
[SuperSU] Pkt_Lnt:
It does not work on all devices stated in OP, mine is one it does not work on, so I do it manually.

Sent from my LS670
[SuperSU] rovo89:
I'm afraid there is an incompatibility between SuperSU and a Xposed. The latter is a framework developed by me and Tungstwenty. It uses a modified app_process binary to inject additional Java coding and special native methods which allow to replace any Java function in the Android framework and any app (and some other things in the same direction).

The problem occurs during the installation if the replacement binary. The installer currently copies the existing app_process to app_process.orig (in case it doesn't exist) and then overwrites the binary with the new one. This generally works fine, after a restart the new binary becomes active and can do the magic.

However, if su access is requested again before a reboot, the prompt doesn't detect the app name but displays "/system/bin/app_process (deleted)". No matter what the choice is, the app freezes and eventually Zygote restarts. I have executed "strings" for your su binary and found references to /proc/%d/exe and /system/bin/app_process. That leads me to the assumption that you check the link behind /proc/(parent pid)/exe and if it is app_process, you do something special. But when overwriting the binary, the link points to what is mentioned in the prompt. I also tried moving the old binary away. Then the link is updated to the new location, but it still crashes.

What I also tried was to change the string to app_proces2 in the su binary. In this case, the normal su requests fail as well because they are not detected anymore. On the other hand, if I rename to old binary to app_proces2, the whole process is working fine. So not the removal of the old binary is the problem but the different name.

Do you have any idea how this could be avoided? Could you maybe ignore a "(deleted)" suffix, either by strictly checking for it or comparing only the first 23 characters of the link? I would prefer not to force an automatic restart after the installation, so users can still change some settings which also require a restart to apply. Any help would be appreciated!
[SuperSU] pr0x:
Can i convert suopersu, and google play to user apps, so then i update them to have only 1 apk. Is is going to compromise system stability, are the going to work. And if there is a problem can i return them as system apps without problems with titanium backup. Thanks?
[SuperSU] bsoplinger:
You have the right idea but wrong direction. You want to convert the user app updates into the system apps. A number of programs do this and I'll list which I know that do. Warning some may require a pay/pro version to do this magic. You can also do it yourself by just copying the updated apk from data to system.

Titanium Backup, link2SD, ES File Explorer.

Sent from my Sprint Evo View 4G (PG41200) using Xparent Purple Tapatalk 2
[SuperSU] GldRush98:
FYI: Something is wrong with the CWM flashable zip download. It is only giving me a 6kb file, where it should be closer to 650kb. Might want to check that and see what is up.
[SuperSU] pr0x:
No the direction is right. See in original roms almost everything is system. In my rom almost everything is user, even maps. Only play store, videos and super su are apps that get update and are system, i converted play videos to user allready, but i am not confident to do that with the rest 2. That is why i am asking what will happen if i do that. I know already that i can copy user apps in system, but why should i do it can theu just be user?!
[SuperSU] bsoplinger:
Ok I understand now. That is an odd ROM. I would be very leery of moving SuperSU to user space. I do know that apps in system get treated differently than user apps by the Android system. And I know that the temp unroot feature moves files around on system as does the save root over a ROM upgrade feature as well. But that's my guess which means I can't help you. You'll need to wait on the dev for a definitive answer.

Sent from my HTC Evo V 4G (PG86100) using Xparent Purple Tapatalk 2
[SuperSU] phone_user:
Samba Filesharing : http://play.google.com/store/apps/details?id=com.funkyfresh.samba

works well with SuperSU v0.93 :)
[SuperSU] Chainfire:
Interesting stuff. Please PM me your email address :)
[SuperSU] sjhotwings:
i just reflashed everything rom etc..and redownload supersu from market. somehow i cannot update the binary ,.. help ? anyone ?
[SuperSU] bsoplinger:
In doing your reflashing did you loose root?

Sent from my Sprint Evo View 4G (PG41200) using Xparent Purple Tapatalk 2
[SuperSU] drs22:
You can try each su alternative by using 'switch superuser app'within su settings
[SuperSU] ioy:
And which su alternative would you recommend the most to begin with?

Why people prefer SuperSU over KingRoot, especially when KingRoot does the job of gaining the root at the first place breaking through the system protection,

and only afterwards by using the app Super-Sume people CAN and prefer to switch to SuperSU?

Is SuperSU better than KingRoot as everyday su application and why?