Database Develop

Uninstall as system app

The method I used for rooting my LG G3 (v5.0.1) installs SuperSU (2.46) as a system app. I would much prefer to have it be a regular app (as it has always been on my Android devices prior to v5.0). When I use SuperSU to clean up in preparation for "another" SU app, it removes itself and leaves behind a few files (including the su binary) in /system/xbin.
All well and good. However, after now installing SuperSU from the Google Play Store, SuperSU gives the message that there is no su binary installed, and of course refuses to work. I even tried copying su to "sux" and giving the latter 4755 privileges (while still rooted), but that didn't help.
Is this a bug in SuperSU, or is it a necessity of Android 5.x ???
ps: The XDA forum software will not let me post this as a question. Where do I post questions about SuperSU?

DeanGibson said:
The method I used for rooting my LG G3 (v5.0.1) installs SuperSU (2.46) as a system app. I would much prefer to have it be a regular app (as it has always been on my Android devices prior to v5.0). When I use SuperSU to clean up in preparation for "another" SU app, it removes itself and leaves behind a few files (including the su binary) in /system/xbin.
All well and good. However, after now installing SuperSU from the Google Play Store, SuperSU gives the message that there is no su binary installed, and of course refuses to work. I even tried copying su to "sux" and giving the latter 4755 privileges (while still rooted), but that didn't help.
Is this a bug in SuperSU, or is it a necessity of Android 5.x ???
ps: The XDA forum software will not let me post this as a question. Where do I post questions about SuperSU?
Click to expand...
Click to collapse
Sorry as I don't have a solution for your problem....
But still as far as I know Super user 2.46 is not fully compatible with android 5 & above.
On other hand I would suggest you to give a try to super user 2.49 beta which is the latest but still under development.
Hope you find this useful.
ayushbpl10

DeanGibson said:
The method I used for rooting my LG G3 (v5.0.1) installs SuperSU (2.46) as a system app. I would much prefer to have it be a regular app (as it has always been on my Android devices prior to v5.0). When I use SuperSU to clean up in preparation for "another" SU app, it removes itself and leaves behind a few files (including the su binary) in /system/xbin.
All well and good. However, after now installing SuperSU from the Google Play Store, SuperSU gives the message that there is no su binary installed, and of course refuses to work. I even tried copying su to "sux" and giving the latter 4755 privileges (while still rooted), but that didn't help.
Is this a bug in SuperSU, or is it a necessity of Android 5.x ???
ps: The XDA forum software will not let me post this as a question. Where do I post questions about SuperSU?
Click to expand...
Click to collapse
If you want to make SuperSU a user app:
If SuperSU was "updated" by the Play Store (ie there's an eu.chainfire.supersu-*.apk in /data/app), then delete /system/app/SuperSU.apk and reboot. If it's flashed *and* the afore mentioned apk is *not* in /data/app, then move /system/app/SuperSU.apk to /data/app and reboot.
Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9

Sent from my Aqua i5 mini using xda-developers.com, powered by appyet.com

DeanGibson said:
The method I used for rooting my LG G3 (v5.0.1) installs SuperSU (2.46) as a system app. I would much prefer to have it be a regular app (as it has always been on my Android devices prior to v5.0). When I use SuperSU to clean up in preparation for "another" SU app, it removes itself and leaves behind a few files (including the su binary) in /system/xbin.
All well and good. However, after now installing SuperSU from the Google Play Store, SuperSU gives the message that there is no su binary installed, and of course refuses to work. I even tried copying su to "sux" and giving the latter 4755 privileges (while still rooted), but that didn't help.
Is this a bug in SuperSU, or is it a necessity of Android 5.x ???
ps: The XDA forum software will not let me post this as a question. Where do I post questions about SuperSU?
Click to expand...
Click to collapse
If all you wanted to do was make it a user app, reroot, open supersu, go to cleanup and choose for reinstallation. After choosing that, if it says to reboot then press it again, do so, else reboot and install supersu from play. Done, supersu as a user app

mmonaghan34 said:
If all you wanted to do was make it a user app, reroot, open supersu, go to cleanup and choose for reinstallation. After choosing that, if it says to reboot then press it again, do so, else reboot and install supersu from play. Done, supersu as a user app
Click to expand...
Click to collapse
That doesn't work (v2.46 on LG G3 running v5.0.1). It loops trying to uninstall. After a couple minutes, I forced a reboot. SuperSU was still there, and as a system app.
Edit: The same thing happens when I tell SuperSU to completely unroot the LG G3. Since I needed to unroot in order to apply an LG/Verizon OTA update, I used LG's Flash Tool to replace the system partition (THAT removed SuperSU!), and then the OTA update was successful.
Since LG now supplies an on-phone backup/restore tool for the G3 as part of the Settings menu, I no longer need to run Titanium Backup, which means I no longer need root. Given the nuisance issues with rooting/unrooting/system updating/etc, I've decided to remain unrooted on the LG G3 for the time being. Quite a change for me, since this is the first Android device in well over a dozen for which I've made this decision.

The second Wind (Parallel SU)

Hello, new user here.
Since I stuggled with root on my Phone and somehow managed to maintain it, I thought, I 'd share you the stuff I did with you.
I put the TL;DR between hide, if you want to read the story behind my struggle anyway, you are welcome.
I am better with explaining stories then explaining things.
Spoiler
I am using a Samsung S4 mini, Stock ROM and just don't want to flash a cROM.
But I wanted more functions to do - a swiss knife like my old GT-S3650, which was able to boot a PC from.
Most of the things I want to use need root, so why not rooting this sleep S4 mini baby?
And I managed to root it using Kingroot. And all of the things I want to use worked.
After a few days, I noticed network traffic, even with the most network apps and Sync disabled.
Weird? Yes. So I installed "Shark" on my Phone and "Wireshark" on my PC, and started logging.
I noticed an increase of Jabber (the protocol) and a lot of request on domains from China.
Some requests even included my IMEI, how I am connected to the Internet, etc... pretty private Stuff.
I found most of the sources, the IMEI sending App was Shark itself.
Used Lucky Patcher to get rid of it and /etc/hosts blocked the DNS with Hosts Editor.
Did the same with some Kingroot DNS.
But then I asked myself: "Can Kingroot still root my phone, even when cut of the web?".
So I UNROOTED my Phone from Kingroot. Bad idea. Really bad one.
After I ran Kingroot again, it told me, it didn't have a network connection.
I have no idea how I was able to edit the hosts file without SU.
Rerooted the Phone, even if it left a bitter taste of having unwanted network traffic.
This is which made me want to switch to SuperSU.
I tried to mount system as RW prior and installing SuperSU over Kingroot SU. And it failed.
I even tried to make my own uninstall script to uninstall KR by unpacking the Kingroot APK and look what it does.
Not working, the script failed (I am not used to Linux), so I stayed at Kingroot.
While I was working on Kingroot, I was thinking about the idea of having 2 SU Apps, which everyone said it won't work.
But I wanted it to make work - and this is actually the focus on this topic.
During tests, it didn't work as intended, so I stopped working on it and forgot it overtime, resting within my /system.
Days passed, Weeks and Months and I lived with Kingroot, forgot all the trouble and access to/from China.
Recently, I started SuperSU - it was still on my phone. This "cannot install su binary" nagged me and thought:
Oh, why not use this instead.
And then there was SuperSuME... which I didn't want to use, since I was able to brick BlueStacks with it.
But I really wanted to get rid of Kingroot and use SuperSU. This was yesterday.
My phone still has warranty and I think I have Odin here (just in case), but not the 100% exact ROM file.
So I did SuperSuME anyway -I always could return the phone and claim it "broken after OTA update", lol.
Well, SuperSuME did it's Job better then expected and no bricks. Nice Job.
While playing around with SuperSU, I did another mistake.
And here we are... at the main topic.
TD;TR for those who didn't want to read the story:
I rooted my phone 2 times with Kingroot and finally wanted to switch to SuperSU.
After I accidentally broke Kingroot the first time, blocked it's Internet access and unrooted afterwards, I got stuck with a unrooted phone and Kingroot failed to root it.
I was lucky to fix that problem and rooted again with Kingroot.
After months, I used SuperSUME to change that. After SuperSU was installed, i made the mistake of unticking "Enable Superuser". Bad idea.
Tapping "Enable" again, it failed to update the su-binary. oh god. I unrooted again.
While traversing through my directories to start Kingroot again to root, I found my "shadow copy" of SU.
Wut? Shadow copy? Let me explain:
After my first unroot, I wanted to have a SU backup anyway at all costs, just in case I accidentally messup root again.
Now after hours I think I know why it doesn't work.. the normal way, of course.
I installed SuperSU, went into /data/data (or where ever SuperSU has its files) and took a look at them.
Unpacked the SuperSU APK on the PC and gathered all "needed" (I think were needed) files.
I hexedited the most SU binaries from SU to ZU and changed all other referenced binaries as well.
I am sorry about that, Chainfire. I was just testing things.
SU => ZU
SUpolicy => ZUpolicy
setup_su => setup_zu
99SuperSUDaemon => 99SuperZUDaemon
daemonsu => daemonzu
zygote => zugote
I had no idea what sukernel was for, so I left that out.
Why call it ZU? "Sun Tzu" thats why. Known as "Sunzi", he wrote Book about "the Art of War".
After I made sure everything is properly renamed and edited, I moved them onto my phone in the right directories required and chmod them.
I don't know much about that, I just copied the chmod numbers from Kingroot SU and some weird script I found on the web.
Tried to run it using JuiceSSH local terminal, and BAM!! the SuperSU box popped up.
But pressing "Allow" accepted it and nothing else happened.
It became stuck after ZU... it did nothing, but the daemon was running as daemonzu and daemonsu at the same time..
JuiceSSH popped up in SuperSU (while it told me the SU bin was outdated), though.
So I was on the right track, but a piece of the puzzle was missing, so I stopped delving deeper into it.
And forgot about it until about yesterday - where I disabled "Superuser" in SuperSU.
Midwhile the su binary changed from Kingroot SU to SuperSU SU.
Note: It should really ask "Do you want to disable Superuser? SuperSU will delete su binary" Yes/NO.
As I found those files, I started JuiceSSH and typed "zu".
This time, ZU somehow worked like it should.
It spawned a root shell. OMG...
I guess it somehow requires something else needed, which wasn't working while Kingroot was active.
I tried "Root Checker" and it failed. I had no "official" root. But still root available in JuiceSSH.
Somehow I managed to restore SuperSU to normal status. Guess this thing can latch onto an active root user or so.. no idea.
I even screenshotted this, cause I couldn't believe it. If you want, I can post those.
I have now a working second su on my phone, which is hidden from most apps.
But I think it is not perfect, it relies on something SuperSU does or installs during installation.
I apologize again to Chainfire for editing his stuff.
So, now my questions:
1. How can I make it perfect to run standalone, only using SuperSU as a GUI for (Allow/Deny)?
1b. Can we make it part of SuperSU? As a special function: "Install Stealth SU"?
2. Can we use that for something else? -> Probably for this? http://forum.xda-developers.com/apps/supersu/suhide-t3450396
3. Why must the binary be called SU? I know it's for the most apps to do their job and somehow Linux standard.

Need Help with Z3 Compact

***UPDATE***
I removed Kingroot through their app and unrooted my phone. I tried another one click root, Kingoroot (I know, quite similar names.) The SU which this one installs, isn't restricting me and I successfully set read/write to /system.
I still would prefer to be using superSU but I get a binary occupied message, and the kingouser app doesn't have an option to switch SU app.
For anyone else struggling with kingroot not letting apps work properly, try kingo, who knows.
-----------------------------------------------------------------------------
I have the Z3 Compact, and I HAVE NO ACCESS to a PC, and thus have rooted my phone with King root (which was a terrible idea but any root is better than no root)
I have this issue, where King root in some way shape or form is not allowing anything that requires write permission to /storage access to it.
This is not allowing me to install/use things like busybox, lucky patcher, freedom, and is also, stopping me from using terminal emulator to do things such as mount -o rw,remount,/system or anything else. I tried to use a system I found on XDA to replace Kingroots superuser to SuperSU to get around this, however, the replace_kinguser method, fails with no write permission, and also, fails to remove kinguser from /system/apps/kinguser because that doesn't exist as a directory and I think Kingroot may have made changes to their superuser handler.
I really, really need help getting Kingroot out, and superSU in. Without the use of a PC. Considering I do, have root, there must be something I can do.
I also can't set system to write with ES file explorer or pretty much any other method on the first ten pages of Google.
Any time I try to set /system to r/w I get permission denied.
I'm running, android 5.0.2
Also, BOOTLOADER UNLOCK ALLOWED? NO
So I don't think I can flash a custom recovery of any kind.

Rooting LN14????

Could someone please point me at instructions on how to root LN14.
I've searched the HD/HD+ forums for 'root LN14' and 'rooting LN14' and got no results (which by itself is suspicious).

have you enabled Developer Options?

I, for one, had no luck with either SuperSu or addon su. The first would put the HD+ into a permanent boot loop necessitating a re-install from scratch,and the latter would install but the unit still indicated it was not rooted. Doing the Dev Op made no difference. A real mystery!

harryzee said:
I, for one, had no luck with either SuperSu or addon su. The first would put the HD+ into a permanent boot loop necessitating a re-install from scratch,and the latter would install but the unit still indicated it was not rooted. Doing the Dev Op made no difference. A real mystery!
Click to expand...
Click to collapse
The file addonsu-14.1-arm.zip in the main folder is the one to use. As I seem to recall, you might have to enable, disable, then re-enable, in order for root access to take effect.

digixmax said:
The file addonsu-14.1-arm.zip in the main folder is the one to use. As I seem to recall, you might have to enable, disable, then re-enable, in order for root access to take effect.
Click to expand...
Click to collapse
That is the one I flashed using 3.0.1.0 TWRP. Not clear on your second sentence: "...enable, disable,, then re-enable...". Forgive me for being lost as to what you physically/specifically mean. Please explain.
Thanks.

harryzee said:
That is the one I flashed using 3.0.1.0 TWRP. Not clear on your second sentence: "...enable, disable,, then re-enable...". Forgive me for being lost as to what you physically/specifically mean. Please explain.
Thanks.
Click to expand...
Click to collapse
I meant "enable, disable,, then re-enable" the root access option in "Developer Options".

Aha! Will give it a go. Thanks.
5/2/2018:
Okay: I d/l three android root checkers and titanium backup. The first root checker (Clivin Inc. with small green android robot graphic) told me I was not rooted both before following your above instructions and after. The other two (d/l after following the above) both say I am rooted. However, I was not and am still not able to get "TB" to run. It says "failed" and that I am not rooted.
Since the HD+ is running really well now in its stripped down mode, I can "leave well enough alone" or try to get "TB" working so I can remove anything not needed for my chosen minimal functionality (ereader, viewing videos, photo review/minor editing) that would further reduce unnecessary battery drain.
Thanks again for the above clarification and any additional thoughts.

I am having this same problem
- Root options *do* appear in my Developer settings, but no amount of toggling on/off/on seems to enable root
- I have flashed the Lineage SU addon, log shows successful in TWRP but no change after boot
- SuperSU from Play Store says "SU Binary occupied"
- Adaway says "Rooted Android required- Either the su binary could not be found or you did not allow root permission for Adaway" ie I believe I am indeed *not* rooted.
- SuperSU flashable zip is a broken link on their website.... http://www.supersu.com/download
Out of ideas here, anyone got anything else I can try?
Edit: I was able to obtain Root properly by flashing Magisk & installing the Magisk Manager APK from here: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445

You got it. Use Magisk. Works wonders and way better than SuperSU or any other root permission tool I've came across. It's even akin to, and even has within it, xposed and other magical rooted modules for you to try out for a day or two and then decide you don't need it.
pchc_lx said:
I am having this same problem
- Root options *do* appear in my Developer settings, but no amount of toggling on/off/on seems to enable root
- I have flashed the Lineage SU addon, log shows successful in TWRP but no change after boot
- SuperSU from Play Store says "SU Binary occupied"
- Adaway says "Rooted Android required- Either the su binary could not be found or you did not allow root permission for Adaway" ie I believe I am indeed *not* rooted.
- SuperSU flashable zip is a broken link on their website.... http://www.supersu.com/download
Out of ideas here, anyone got anything else I can try?
Edit: I was able to obtain Root properly by flashing Magisk & installing the Magisk Manager APK from here: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Click to expand...
Click to collapse

Magisk Manager with built-in su

Hi all!
I might be asking a stupid question, so forgive me if I do.
The situation is the following... I have a TVBOX Q96 HOME 4K (cheap Chinese one based on RK3229) that is pre-rooted. All applications using root work fine. However, there is no "superuser" manager installed on it in order to disallow certain apps to gain root access. In the past I already had a similar situation with some other box and when I installed SuperSU apk the device hasn't boot anymore. I that case I got a stock firmware and could unbrick it, but now I can't find any ROM for this device in order to play with it.
So, the question is... is it possible to install Magisk Manager in order to manage access to the built-in su? Older version I tried correctly identify the device as rooted (with SuperSU 2.76), but do not offer me a Superuser menu where I could manage access to the su of the apps. Neither I get a prompt when an app is requesting access to su.
Any solution to my problem?

No, you will not be able to use the Magisk Manager to manage superuser access for SuperSU.

Any idea what might cause the device to not boot anymore after installing SuperSU.apk?
I compared the installed su binary with the one from chainfire's UPDATE-SuperSU-v2.76-20160630161323.zip (arm7), and they are identical. What does installing an apk alone to the system beside managing the access for the apps?
I have to admit I don't know exactly what happens "behind the scene".

I have absolutely no idea why installing the SuperSU apk would cause your device not to boot... Sorry.
Edit: Wait... You write "installing an apk alone to the system". You're not installing it as a regular app, but to the /system partition? If so, that's what might be causing issues.

Sorry to mislead you... I wrongly expressed myself.
I'm not installing it as a system app - I have installed it (on previous box) as an ordinary user app and as I said the system couldn't boot anymore afterwards (I had to reflash the ROM to unbrick it).
BTW... this is a known issue with these Chinese TVBOXes. There are couple of posts also here in XDA about it and nobody knows AFAIK what is the root cause.