I have a rooted custom device (Android 8.0), I can use adb and run su and do whatever I want in the shell. But SuperSU or any other app cannot find root. I have made a symlink from /system/xbin/su to /system/bin/su but it still does not work.

I am working on a pre-rooted Android head unit. I can do "adb root" or "adb shell su" using wifi adb. So there is root access and Su binary on the device. But I can't use root applications because there is no app to grant root access. I have tried installing supersu or superuser on /system/app. I made it install the apps but they say "device not rooted" when I try to run them. So how can I make supersu see my su binary?

I recently installed [LightningFastRom 17.1](https://forum.xda-developers.com/t/lightningfastrom-17-1-q-10-for-gtelwifiue-gtesqltespr.4231493/ "LightningFastRom XDAForums"), a ROM based off LineageOS 17.1, for my Galaxy Tab E 9.6 (SM-T560NU-gtelwifiue). For GApps, I used OpenGApps (arm, 10.0, micro). I modified the .zip file using this [video](https://www.youtube.com/watch?v=KxW72-Nzb3A&ab_channel=EncryptedGuy "This package is for {device}. This device is ."). When I first booted it, it worked perfectly, then I flashed [SuperSU](https://supersuroot.org/ "supersuroot.org"). I waited an entire day and it still didn't boot. Does anyone know how to get back to recovery while on the boot screen, I decided to flash a new ROM.

Whenever I follow a root guide, I see a link to SuperSU and TWRP files. Are these SuperSU and TWRP files the same file for all phones, or is there a different SuperSU for each phone? Also, if it exists for each phone, is it ROM-specific? Do I need a separate SuperSU file for CM13 and stock ROM on the same phone?

I unlocked bootloader on Huawei MediaPad T5 (AGS2-L09). Then I put TWRP on it and everything was fine until I installed UPDATE-SuperSU-v2.46.zip using TWRP. After that the tablet stuck at Huawei welcome screen. Then I found UPDATE-unSU.zip on xda-developers forum. Its author promised that it will revert changes of UPDATE-SuperSU. Now the tablet goes scrictly into TWRP and doesn't want to do anything else. How to recover it? P.S. Before to install SuperSU-v2.46.zip for the first time I noticed that many folder names in the tablet internal storage were encrypted.

I'm using cm13 on my OnePlus 3, along with systemless SuperSu and suhide. When I update cm (often), I need to flash both SuperSu and suhide. The problem is that cm comes with root access and when updating, makes a su directory in /system/bin/su that suhide detects so that it won't install. I need to delete that directory in between of the flashes, and I would like to make a script that does that for me when i flash it so that I can flash all files together on update using CyanDelta. I know that this is possible because I have seen other zips that execute command scripts as i flash them.

After I root my Samsung Galaxy Mega 6.3 (GT-i9205), I downloaded SuperSU from [XDA Forums](http://forum.xda-developers.com/showthread.php?t=1538053) . After I open SuperSU, it asks me to update my su binary. > The SU binary needs to be updated. Continue? But after a long time, it got stuck on > Installing, please wait. If you see this message for more than five minutes please restart and try again. Then I tried to check whether my phone is rooted or not by using a root checker. At last, the answer is *does not have proper root*. Please help!

I tried to replace Kingroot with SuperSU since in the newer versions of Kingroot you can't block all of its connections. I had some problems, SuperSU always failed to install the newer binaries, Kingroot didn't fully uninstall and sometimes I lost root. After being unable to install SuperSU, since it always failed to install the binaries not even as a system app, I gave up and decided to keep using an old version of Kingroot (4.85). But since then, I can't write on /system. I tried to remount /system as rw but it always get Mount: Read only file system. I tried mount -o rw,remount /system, adb remount and also through Root Explorer, Total Commander, and with mount system RO/RW, but none of them worked. I think it is because SELinux mode somehow changed to enforcing while I was trying to install SuperSU. I tried with SELinuxModeChanger to change it back to permissive, but I still cant remount. I can't even uninstall Kingroot either. What can I do? I'm using a rooted 4.4.4 Huawei phone with Kingroot, it has root but it can't write to /system.

I have a Huawei AT&T Fusion 3 (Y536A1) with Android 4.4.3 which I attempted to root with KingoRoot but it ended up giving me a half-root after testing it with the Freedom app. I tried uninstalling it using the KingoRoot Superuser, but it just deletes the Superuser app and restarts but doesn't delete the root itself. I tried manually deleting the su files (with Root Explorer and ES File Explorer), but I don't have the right permissions to do so. I also tried using SuperSU but the binaries always failed to update and when I tried full unroot it still didn't unroot. I also tried to install KingRoot over KingoRoot but it said that it couldn't root (even though the device is compatible). How do I remove this half root so I can fully root?

I have Cyanogenmod 14.1 installed on my Samsung SM-G900f. After installing SuperSu from Phillz recovery, Wifi try to start, but no success. I found the same post here https://android.stackexchange.com/questions/161353/wifi-doesnt-work-when-supersu-2-72-binaries-are-installed-on-android-7?newreg=a413e9de1352448cb64d9d4b2b60aa3c The last comment sugest to "Better you uninstall SuperSu app and binaries and use CM's Default Root Access (from Developer Settings) till the issue is fixed" I've tried to uninstall SuperSu the normal way and from the app settings: SuperSu > Settings > Switch superuser app, but when SuperSu is uninstalled and in the CM settings the root access is set to disabled, it is ignored and every app that granted root permission from SuperSu before, seems it has it now and use it without asking. Root access from CM settings is ignored. That being said, how can I uninstall SuperSu app and binaries and use CM's Default Root Access? Or even better, is there a fix to a non working Wifi?

I installed TWRP successfully. On my phone i downloaded the SuperSu Zip. When i click install on TWRP it doesnt show up. Can Anyone tell me what to do to make it show up. Info: -Phone = J7 (2016) j700T -NETWORK T-Mobile

I recently got a root request that came up as "Greenify [UID]". This looked suspicious to me as I usually get greenify requests as just "Greenify". I have tried to contact the developer of Greenify and I have yet to get a reply. Could someone clarify what "[UID]" means?

I managed to root my Verizon Samsung Galaxy Note 10.1 tablet with Kingroot, but I'd like to remove it and switch to using SuperSU (because of KingRoot's aggressive practices and somewhat shady reputation). Even after uninstalling it and deleting everything labelled kingroot or superuser in /system, I still get Binary Occupied from the SuperSU app. I believe there is a hidden process somewhere monitoring attempts to delete it and replacing the binary. For example, in system/usr there is a directory called iku (kinguser?) which replaces itself immediately after being deleted. Similarly, in system/xbin there is ku.sud and start_kusud.sh, which I can delete but instantly reappear. This may be a quirk of the Samsung system, or some kind of hidden or inaccessible process. I've followed numerous online tutorials, and tried to run the Replace_Kingroot_With_SuperSU.zip method, but to no avail. Anybody know of a workaround? Edit: here is part of the stdout form a script I ran. Note where it says **operation not permitted**: rm failed for /system/xbin/ku.sud, Operation not permitted rm failed for /data/data/com.kingroot.RushRoot, No such file or directory rm failed for /data/data-lib/com.kingroot.RushRoot, No such file or directory rm failed for /data/data/com.kingroot.kinguser, Directory not empty rm failed for /data/data/com.kingroot.master, No such file or directory rm failed for /system/bin/.usr/.ku, Operation not permitted rm failed for /system/bin/rt.sh, No such file or directory rm failed for /system/bin/ddexe, Operation not permitted

Question : what are effects of factory reset while in rooted condition of mobile In my lyf water 7 mobile device having 16gb internal memory and 2 gb ram and 64gb external sd card I had first factory rest my mobile with and formatted my external sd card with no user apps or data installed then I decided to root it and before that want to take a backup I had loaded twrp recovery (fastboot boot twrprecovery.img) in bootloader mode and took NANDROID backup of system boot cache userdata through twrp backup menu and through adb pull tool all partitions backup of mmcblk0 and system boot recovery userdata and all in other partitions in devices. Then In twrp menu install menu I installed superuser .apk after installing succesfully I rebooted to android 5.1.1 rooted version Through root checker i checked the rooting status ita good Then I download link2sd plus modified parched .apk file which installed successfully and to open it asked to grant root permission for 15 minutes and disappeared and I tried to locate its icon in main menu or front wall but no success. I thought to uninstall but there is no mark in any settings>apps installed or running list I tried to find in root folders but it's hidden or disappears name there to I m wooried it's not any virus malware or spyware apk file which asked executed or hidden .. I thought to factory reset to erase that hidden apk file of link2sd My queries:- 1. How to find and erase that hidden apk file aftermarks or settings 2. Should I format or factory reset the mobile as su was installed or I should first unroot or clear su before factory reset will it erase that malware hidden aftermarks 3. If I don't not remove or unroot SU and factory reset the mobile then will after factory reset I have to re root or install SU again or it will be rooted or unrooted automatically after factory reset format withing rooting

**Question Which root method is safe and can be unrooted easily safely without aftermarks** I want to root my mobile lyf water 7 and change modify settings of PM set install location and if it works then I will like to unroot and install https://android.stackexchange.com/questions/106028/moving-installation-location-on-non-rooted-android-5-lollipop-device I googled founded three methods 1. Twrp installing and installing super user 2. Installing magisk which writes on Bot partition and don't touches the system partition 3. Installing kingoroot or one root 4. Xda rooting batch file https://forum.xda-developers.com/t/lyf-water-7-ly5504.3524381/ Which of the above rooting methods are safe to install what are pros nd cins of each methods and which and can be unistalled easily and don't leave any after marks after unrooting How to unroot with all four methods 1. Superuser 2. Magisk 3. Kingoroot or one touch root 4. Xda batch dile

Have to mention this to avoid possible confusion, this question is *not* duplicate. This question is specific to **using adb to uninstall a package**. There are several similar questions but are all different from this one, as they're focused on removing an application by any means. *Please do not provide answers using "rm" command to delete the package files. Also, answers related to malformed package names, or trailing carriage returns. I think they're pretty much all covered in all the other questions.* I had pm uninstall functionality but after ROM upgrade. Some things won't uninstall anymore. For example the following two system apps (which I removed under previous ROM, significantly improving overall performance):
/system/priv-app/SecurityCenter/SecurityCenter.apk=com.miui.securitycenter
/system/app/Updater/Updater.apk=com.android.updater Now I get an error trying to pm uninstall them: **Failure [DELETE_FAILED_INTERNAL_ERROR]** But other **system** apps (which won't uninstall through regular android interface) do uninstall via pm uninstall command. Example:
/system/priv-app/Browser/Browser.apk=com.android.browser So both are system apps, what could be the difference between them? For reference, I upgraded from MIUI 8.1.6.0 to 8.5.3.0, and re-installed TWRP and SuperSU. This question is not specific to my ROM, as I see other people are in the same situation. But I seem to have an advantage being able to be able to uninstall some system apps. And am willing to contribute, to find a solution for everyone, to uninstall any app. I tried: mount -o rw,remount /system but that didn't solve it. Please help out with any ideas along the way. Thanks! --- *Update 1* - Confirming steps to avoid intermittent issues
* Wiped all partitions in TWRP
* Installed Latest ROM (MIUI 8.5.3.0)
* Went back to TWRP, wiped only /Data
* Restored /Data from backed up version of the ROM that came with device (MIUI 8.1.6.0)
* Now after I boot into OS, ROM shows as latest (MIUI 8.5.3.0) in settings Now I am able to pm uninstall every app I've tried. Even the most resilient: Google APP, Updater, Security. This Frankenstein.. err I mean hybrid ROM works fine so far, and I've already removed many system packages, making the phone (Redmi 3S+) visibly faster. But I would still like to pinpoint what was causing this to make it into _Generic Solution_. So, if it ain't broke I'm willing break it, so next time it breaks we will know what's causing it and how to fix it. *Update 2* -
* Wiped all partitions and restored all partitions from Original ROM.
* Restored to factory settings (using TWRP)
* and after booting into ROM, went back to TWRP and made another backup
* Using same scenario as in Update 1 above, with only exception of using /Data from here. pm uninstall does *not* work. Any thoughts on the differences between the two /Data partitions I should be focusing on?

I am having trouble installing SuperSU from Twrp Recovery. The steps I used are as follows: 1. Boot into bootloader: adb reboot bootloader 2. Flash recovery to twrp image file: `fastboot flash recovery twrp-3.5.2_9-0-ali.img` 3. Open recovery mode, opens twrp 4. Twrp asks for decryption password, I don't know what to do so I press cancel 5. Twrp asks if I want to keep system read only 6. I swipe to allow modifications 7. I click install 8. I find /external_sd 9. I click UPDATE-SuperSU-v1.80.zip 10. I swipe to confirm flash 11. It says successful, but also says unable to mount storage `unable to mount /data/media/TWRP/.twrps` 12. I click wipe cache/dalvik 13. I swipe to wipe 14. I click reboot system 15. I input my password to start device 16. I look for the SuperSU app, I don't find it. So something messed up and SuperSU didn't install. Any ideas?

I had rooted my device, I have Titanium Backup, Superuser, and ES File Explorer. I changed the android version, phone model and sdk version in the build.prop file. Now I can't open any app other than Titanium Backup, which tells me it wasn't granted superuser permissions, and that I should check if my ROM is rooted. When I access the files through my computer with Android Studio, I can see the root files. Is my phone not rooted anymore or is Superuser just not working properly due to the build.prop change?

I am trying to root my android 6.0.1 phone using the following method: I first booted into a TWRP image using fastboot boot, then using the TWRP terminal I copied the su binary from the SuperSU kit to /system/xbin/ and ran chmod 6755 ./su, chown root:root ./su and chcon u:object_r:system_file:s0 ./su. Now I booted into Android and opened a terminal emulator and goto /system/xbin/ and see that the SUID bit is set for su. But when I run su, nothing happens and the binary exits with a 0 value. Running strace su shows that the setresuid() and setuid() calls are failing. I suspect this is because of SELinux contexts. What should the SELinux contexts be for the binary?

KingRoot's Superuser, while effective at its main purpose, is throwing up adware lockscreens. I'd like to replace it with SuperSU but have had difficulty finding instructions detailed enough for my low level of knowledge. I tried just installing SuperSU from the play store but that failed. When googling, I see results for kingroot, kingoroot, and I don't even know if they are the same or not. The Superuser package on my device is com.kingouser.com version 2.1.6.8 (2168). The device is an Azpen A746, the world's 2nd cheapest tablet. Detailed information on replacing this SuperUser with SuperSu would be greatly appreciated.