I succeded adding the -k and --user options to the pm command, e.g.:
pm uninstall -k --user 0 com.android.service
The command was issued as root, no need to remount /system as rw. Android on the phone is 6.0 and the package is a system app. Without the extra option I get the error:
From the man page for mount:
A mount namespace is the set of filesystem mounts that are visible to a process.
It makes it so that the superuser has separate mount points visible to it from the rest of the system/apps. I believe the intention is to prevent any issues when remounting partitions, such as remounting /system as read-write. With this option ...
If you are using stock Android 6 and newer you can only have systemless root because of security restriction. So if you root your phone running stock Android 6, you will have systemless root.
Because you are using a Samsung phone it might be a bit more tricky. It could be that your custom rom has it's own su installation in the system partition. Then it's ...
As of October 1, 2018, SuperSU has been removed from Google Play. However its pro key (US$3.99) is still available.
The latest version of SuperSU is 2.82 SR5, you can find it on this XDA thread. However, as Android evolves, SuperSU is no longer the best choice for rooting. Instead Magisk is recommended for Android 5.0 or newer. SuperSU is still good for ...
I have systemless root and a few ways
The superuser su binary will not be found in /system/xbin/, like in normal system-based root. See
On your terminal emulator enter which su , it should show the location of su binary other than /system/xbin/ ( in my case it shows in the /su/bin/su location ). You can leave a comment to show the result ...
When you use your phone, access applications and navigate it's file system, you do so as a user with a given set of permissions. This places certain restrictions on what you can and can't do or access.
Rooting your phone places an executable on your device called su (switch user), this executable switches the account credentials and permissions that you ...
Sometimes the need for a systemless installation of SuperSU is not detected by the installation script, to force this to occur follow the following steps.
Start TWRP 3.0 or higher on the device
Go to Advanced - Terminal
In the terminal, enter echo SYSTEMLESS=true>>/data/.supersu
Exit to the TWRP main menu
Flash the current SuperSU as per ...
From app's description in Play Store:
SuperSU is the Superuser access management tool....
SuperSU allows for advanced management of Superuser access rights for all the apps on your device that need root. SuperSU has been built from the ground up to counter a number of problems with other Superuser access management tools....
In more ...
Gather the steps in a gist.
How to flash and root OnePlus 3T on Linux
fix SuperSU with no-verity-opt-encrypt-5.0.zip and SR5-SuperSU-v2.78-SR5-20161130091551.zip² ;
Disclaimer: I've already done those kind of install on different phones and I'm familiar with the steps. So be sure to read the resources to get an ...
It is likely due to mount namespace separation being unchecked in SuperSU app settings
For an explanation of what it does and how it could possibly affect storage not being read see Mathew's answer here, also the link referred to therein
Aside, sometimes TiBu also asks you to do the same if SD is not recognised
You misunderstand the logic of su binary.
Android doesn't have an su command like other Linux distros do. The su binaries we use on Android are added to the /system (for pre-6.0 versions) and they are customized to work with the GUI application (such as SuperSU)
So when you run an application that wants to run as root, it sends out a call to su binary. ...
TL;DR - skip to the STEPS section
Kingroot and Kingoroot are two completely different apps, made by two completely different group of developers.
Kingroot, while it is probably the leading app for "1-Click-Root" solutions, also installs a ton of bloatware and annoying services that you may or may not know about.
Kingoroot I can't really speak too much ...
As you've already found out, LineageOS has its own, built-in, lightweight SU solution (addonsu), which is the only one supported officially (the team does not adore Magisk/SuperSU).
Note that officially LOS only provides 14.1 builds for your device. Assuming that's the version you're running, using the addonsu for 15.1 you will naturally bump into problems. ...
MI 5C is a fairly new phone and with Xiaomi's in-house SoC (harder to develop for than established ones like Snapdragon), therefore custom ROMs are expected to come out later and in fewer quantities.
Stock MIUI also employs a check on /system partition so as to prevent booting when it's modified, no matter how it's executed (modified before or after ...
Whether it is "Kingroot" or "Kingo Superuser" you are trying to swap to SuperSU, it will be best to use manual methods as most auto scripts out there doesn't work on all device. The simplest and most easiest way to do this does not even required any apps than a file manager. This can be done using ES File Explorer.
I've once faced an issue with kingoroot. ...
You did it wrong I guess. Despite all the tutorials you found online, I wonder how you missed the right one : There's a "safe" uninstall feature within Kingoroot app. This removes completely the app and the binaries from your device.
Open the app
Click three dots upper right, find settings menu.
Click "Remove Root".
Your device will be rebooted and root ...
Found out the way to fix it:
Download stock firmware (*.tar.md5)
Flash it with Odin (it removes TWRP and replaces it with a standard recovery)
Start Android - still "Unsuccessful encryption" error
Boot into recovery mode (now it's standard recovery instead of TWRP)
Run factory reset
Start Android - now it finally starts - problem solved
Flash again TWRP ...
Ports are not reserved by Android (or by any other OS) but are assigned by IANA for specific use. If a port is free i.e. no process is connected to or listening on that, you may use that with your program. But this may break the app's functionality for which the port is reserved. Otherwise you'll have to modify the source code and rebuild all the programs ...
It seems that you had Lineage (im on 14.1 right now & i love this rom), but you wanted, instead, the excitement, unreliability, the Wonder, of 3rd-party root management.
Yeah, I used to smoke a lotta that, too. JK. CM/LOS's su is way more stable, predictable, user-friendly, and PRIVATE than most other root-solutions. Seems you weren't aware of the add-...
I guess I was overthinking this. I just uninstalled Kingoroot's Superuser app through Apps, then downloaded and installed Super SU from the play store. Still have root. "All too easy" as a certain Sith Lord would say.
The last straw was when Kingoroot Superuser installed an unwanted app without asking. It had to die after that.
Rooting can be accomplished using Magisk (make sure not to use an old version, but that from the linked XDA thread: v14 at the time of this writing). Flashing Magisk will not modify the /system partition but rather create a modified boot image. So at boot time, Magisk gets initialized, creating an Overlay File System on top of the system structures. That way ...
With my experience I've learnt the side-load feature from TWRP is pretty finicky. I've only managed to get it working once and I had to do a lot of downgrading. I would load the file onto an SD card or USB and use an OTG cable (what I usually use) then flash it directly from the recovery. You can also flash things like CF-Auto-Root and load it while in ...
Certainly. In fact, ADB isn't at all necessary.
First of all, to save you a lot of worries, I will inform you about FlashFire. It's easily the best way to install ROMs and other such things if you do have root. Download it if you have root.
If you don't have root, here's the non-root TWRP method To boot into TWRP differs from phone to phone, so I won't go ...
You need to uninstall suhide. There is an uninstaller.
Check this post:
And scroll to the downloads section. Download the file with 'rm' in the name. Transfer it to your phone and flash it in TWRP. Make sure you have the latest version of TWRP. Reboot.
I would suggest buying a cheap phone and ...
Your device needs to be rooted first
You can only grant SU permissions when the application asks for it in a rooted environment. Forcing the app to ask for permissions is not trivial or likely to succeed . For details, see related question linked below
If you are not rooted, you can't bestow super user privileges to any app
Related How to add root ...
It seems like HTC Desire 500 has a "system write protection", so you may need to flash a custom (modified) kernel to prevent the system from protecting itself from modification.
Check this post on XDA forum.
Generally no, but it depends on your device. For example, if you have an older non-updated Amazon device, you can usually root it with as little as an app install. For devices that haven't been exploited yet, however, there's little hope besides asking the community on xda and such very very nicely. It's a good idea to look for "bootloader unlockable" ...
It is highly recommended not to do so. The TWRP is a touch-based recovery, meaning that it needs to initialize touch screen (actually every related hardware) before showing the main menu. If you insist on flashing a 'generic' TWRP to your specific, non-matching device, you will end up getting stuck and your recovery will never boot until you flash another ...