Remove KingRoot’s KingUser with SuperSU using Terminal [Requires Intermediate skills]
This method works for almost all the android devices and works the best, However, it requires some decent skills to follow the instructions and copy the commands listed below into the Terminal app.
The link of the script which is shared below works without a computer system/PC, Hence the steps I’m listing below won’t require a computer PC. So are you ready?
Downloads
This download section has the download links to the files or apps you will require to complete the below listed steps. Ready to shift from KingUser to SuperSU? What are you waiting for?
lets begin.
1.Download & Install Terminal Emulator App
2.Download SuperSu script from here http://www.mediafire.com/file/mxzbt42xypvn2ts/Replace_Kinguser_with_SuperSU-v2.4.zip and unzip it!
Steps to Replace KingUser with SuperSU?
Step 1: Extract the Replace_Kinguser_with_SuperSU ZIP File & Transfer the extracted version to Internal storage of device.
Install the Terminal app for Android and extract the Replace_Kinguser_with_SuperSU file and after extracting the Replace_Kinguser_with_supersu file transfer the “Extracted Folder – MRW” to outermost directory in the internal storage.
Step 2: Open Terminal Android App & Write the Following commands in the Android Terminal.
Open the terminal android app type the command “su” in the terminal, after writing the SU in terminal, you will be prompted with the message box asking you to deny/grant the functions. Granting permission will help you remove the kinguser on your smartphone.
After granting permissions you will have to type one single line of code, The other command will be: sh /sdcard/mrw/root.sh
After writing the above command, it might show some error, but ignore that error, it will automatically launch SuperSU, in case it doesn’t manually open SuperSU.
Once done, Restart your smartphone and you will see that SuperSU works flawlessly on your Smartphone. That’s all, you’ve successfully replaced KingRoot’s KingUser with Chainfire’s SuperSU.
Huge thanks to the Dev of the script
Source and Download link credits goes to Droidmen.com
Thread link of Droidmen: https://www.droidmen.com/remove-kingroot-kinguser-with-supersu/
I shared this guide from droidmen if you found this guide useful PLEASE HIT THANKS BUTTON!
RESERVED
Good
Sent from my Redmi Note 3 using Tapatalk
can anyone confirm it in above 4.4 ?
sohamsen said:
can anyone confirm it in above 4.4 ?
Click to expand...
Click to collapse
Well it works on 4.4.2 but you need you manually uninstall kinguser in system after.
Arkonite said:
Well it works on 4.4.2 but you need you manually uninstall kinguser in system after.
Click to expand...
Click to collapse
mine uninstalled automatically
Replace kingroot with supersu
Here you can get the most effective way to replace kingroot with supersu;
How to replace kingroot with supersu
King roots
This Guides are for People with Treble 8.1 ROM with SU from Treble Thread.
It's super simple and easy to Google out, but I'll write here for sum-up.
Magisk Root and Stock Camera is seperate GUIDE, you don't need to do both.
Magisk Root
1. download the patched_boot.zip I uploaded below and unzip, and jump to 3.
2. Fastboot flash ramdisk patched_boot.img
Q&A
Q. Why 'Patch Boot Image File' method?
A. Bcuz TWRP for Oreo is for 8.0 only or buggy for 8.1 at this point.
Q. What's the point of this guide?
A. Bcuz you may not know which file to patch, where to flash since huawei renamed BOOT to RAMDISK
TWRP for 8.1 GSI is there, you can use it with Magisk 16.7
For 9.0, There is no working TWRP so flash Magisk 16.7 from 8.0/8.1 before you go to 9.0 GSI.
if you having problems with certain apps at 9.0 GSI, It probably bcuz of which su, so use symbolic link.
open up adb, type
adb shell
su
mount -o bind /sbin/su /system/xbin/su
Q&A
Q. why mount -o? why not ln -s?
A. Bcuz ln -s did not worked, at least for me.
Q. will it last?
A. No. reboot will remove mount -o command so you need to do it again if you reboot.
stock Camera
1. Download the Stocam.zip file I uploaded below and unzip.
(source : https://forum.xda-developers.com/pr.../huawei-stock-camera-app-treble-roms-t3735169)
2. Install Zipsigner from Playstore and re-sign the apk file with auto-test
3. put .so files to vendor\lib64, re-signed .apk file to prive-app\HwCamera2, all permission 644 (rw-r-r)
Q&A
Q. What's the point of this guide?
A. Bcuz Honor 9 + 8.1 has quite a lot of things to do, and it's quite tough to read all the thread down to find out what to do.
Q. It's still not working.
A. Download OldDroid's files from the link below, copy-paste the files from system\lib64 and system\lib (not vendor\ !).
(https://mega.nz/#!7hQDhQAK!p2s7jQp9-nhp2-O1U2s2GrBB9UVBhgKDtFfHTq_CHvI)
for 9.0, there is no proper working stock camera port. you can try P20pro camera port mod.
it's Magisk module but not working, so you need to unzip and put HwCamera2 folder into /system/priv-app manually.
https://forum.xda-developers.com/honor-9/themes/app-port-p20-pro-camera-mod-root-t3777920
Modifying Android x86 rooted with Magisk
This thread is about android x86 from official website: https://www.android-x86.org/ and it's about rooting and modifying android x86.
Your warranty is now void.
I am not responsible for bricked devices, dead SD cards,
thermonuclear war, or you getting fired because the alarm app failed. Please
do some research if you have any concerns about features included in this ROM
before flashing it! YOU are choosing to make these modifications, and if
you point the finger at me for messing up your device, I will laugh at you.
Click to expand...
Click to collapse
Please continue this thread writting your ideas, guides, questions of modifying android x86.
Hello everyone!
Are you bored of stock su? Here you have instructions how to install magisk on android x86 pie (9)
In this post I'd like to share what I found on this website: https://asdasd.page/2018/02/18/Install-Magisk-on-Android-x86/ it's about installing magisk on android x86.
It's not my work, I just have rewritten it to XDA to be easier somebody to find information.
Also I checked is it working with newer version (for now 20.4) - yes
I have to admit, that on my android x86 modules aren't working.
Just superuser permissions management for other apps are ok. Don't know how to fix it and want community to help I'll share screenshots in close future and logs if someone can help me.
Prerequisite:
1. Linux environment
2. Partition r/w Android x86
3. Installed official Magisk Manager if I'm not wrong official project is here: https://github.com/topjohnwu/Magisk
Follow this steps to root your device with Magisk:
1. On Linux install android-tools-mkbootimg abootimg using command:
Code:
sudo apt install android-tools-mkbootimg abootimg
2. Open Android x86 folder with root permissions and copy the kernel and ramdisk.img file from the partition of the Android x86 to the created work folder on linux.
3. Open terminal as root in that folder
3. The following command will pack the boot.img of Android x86.
Code:
mkbootimg --kernel kernel --ramdisk ramdisk.img --output boot.img
4. Copy the extracted boot.img to the Android folder e.g downloads or documents
5. Reboot to android x86
6. In Magisk Manager choose Install ==> select patch to boot.img and click boot.img file.
7. After the operation, there should be a patched_boot.img or similarly named file in the same directory.
8. Reboot to linux
9. Open Android x86 folder with root permissions and copy patched_boot.img to another created folder on your linux. Open there terminal with root permissions.
10. Extract kernel and ramdisk from patched_boot.img file using the following command:
Code:
abootimg -x patched_boot.img
11. There should appear 3 new files in the folder after this operation.
12. Rename zImage to kernel and overwrite the one in the Android x86 partition. REMEMBER ABOUT the original permission
13. Rename initrd.img to ramdisk.img and overwrite the one in the Android x86 partition. REMEMBER ABOUT the original permission
14. Done! Reboot to Android and check if Magisk is installed in Magisk Manager app.
[Q]How to hide navigation bar in android x86 pie?
Hi everyone,
I tried to truly hide navigation bar in android x86 pie by editing build.prop located on system and vendor partitions adding line:
Code:
qemu.hw.mainkeys=1
The problem is it's not working.
Can you help me?
Important Update
I drop this subject as now I'm more interested in true Linux itself but I'll leave this thread open as closing needs messaging moderators and thre's no need to do the mess
@BigBrother84
I found a way to patch correctly, but I only tested it in VirtualBox.
https://github.com/shakalaca/MagiskOnEmulator
Thanks
HemanthJabalpuri said:
@BigBrother84
I found a way to patch correctly, but I only tested it in VirtualBox.
https://github.com/shakalaca/MagiskOnEmulator
Thanks
Click to expand...
Click to collapse
I tried before but failed
Where can I get the magisk.zip file for version 23.0 ?
NOTE: the used method I installed magisk.apk and then change the extension to .zip and I applied these codes but In the final result I got initrd.img (0kb) and ramdisk.img (1.82MB)
@HemanthJabalpuri please send me a guide on how to install magisk on android-x86_64-9.0-r2 in VirtualBox
to me too, please!!
If I installed android x86 with system writeable, there is no ramdisk.img and kernel file in the Android x86 partition.
So how where can I put these files to make the Magisk?
JuanLv said:
If I installed android x86 with system writeable, there is no ramdisk.img and kernel file in the Android x86 partition.
So how where can I put these files to make the Magisk?
Click to expand...
Click to collapse
Solved.
Mount the sda* (the partition you installed the Android x86), and the image file is there.
Ref: https://github.com/shakalaca/MagiskOnEmulator
BigBrother84 said:
Hello everyone!
Are you bored of stock su? Here you have instructions how to install magisk on android x86 pie (9)
In this post I'd like to share what I found on this website: https://asdasd.page/2018/02/18/Install-Magisk-on-Android-x86/ it's about installing magisk on android x86.
It's not my work, I just have rewritten it to XDA to be easier somebody to find information.
Also I checked is it working with newer version (for now 20.4) - yes
I have to admit, that on my android x86 modules aren't working.
Just superuser permissions management for other apps are ok. Don't know how to fix it and want community to help I'll share screenshots in close future and logs if someone can help me.
Prerequisite:
1. Linux environment
2. Partition r/w Android x86
3. Installed official Magisk Manager if I'm not wrong official project is here: https://github.com/topjohnwu/Magisk
Follow this steps to root your device with Magisk:
1. On Linux install android-tools-mkbootimg abootimg using command:
Code:
sudo apt install android-tools-mkbootimg abootimg
2. Open Android x86 folder with root permissions and copy the kernel and ramdisk.img file from the partition of the Android x86 to the created work folder on linux.
3. Open terminal as root in that folder
3. The following command will pack the boot.img of Android x86.
Code:
mkbootimg --kernel kernel --ramdisk ramdisk.img --output boot.img
4. Copy the extracted boot.img to the Android folder e.g downloads or documents
5. Reboot to android x86
6. In Magisk Manager choose Install ==> select patch to boot.img and click boot.img file.
7. After the operation, there should be a patched_boot.img or similarly named file in the same directory.
8. Reboot to linux
9. Open Android x86 folder with root permissions and copy patched_boot.img to another created folder on your linux. Open there terminal with root permissions.
10. Extract kernel and ramdisk from patched_boot.img file using the following command:
Code:
abootimg -x patched_boot.img
11. There should appear 3 new files in the folder after this operation.
12. Rename zImage to kernel and overwrite the one in the Android x86 partition. REMEMBER ABOUT the original permission
13. Rename initrd.img to ramdisk.img and overwrite the one in the Android x86 partition. REMEMBER ABOUT the original permission
14. Done! Reboot to Android and check if Magisk is installed in Magisk Manager app.
Click to expand...
Click to collapse
Just an FYI to all that this still works with Android-x86-9.0-r2. I did this on a Dell 3185 with Debian 11 installed. Thanks a million, OP!
Check out another simple and convenient way. If you got any error, please give feedback!
GitHub - HuskyDG/initrd-magisk: Integrate Magisk into Android-x86 project
Integrate Magisk into Android-x86 project. Contribute to HuskyDG/initrd-magisk development by creating an account on GitHub.
github.com
I have tried several methods to turn an app into a system app but even if in some case I managed to install the app inside /system/priv-app the app was not running as a system app as I could figure out by checking running the command "adb shell ps".
So please could someone tell me if I missed something or if there is some limitation link to Lineage or may be Magisk or TWRP to have an app runing as a system app ?
I have tried with Lineage 15.1 (Oreo) and magisk 21.2 the phone is a Samsung S5 using TWRP 3.5.0_9-0 as system Recovery
First method was to
1 making a copy of the app folder to the internal storage
2 renaming that copied Folder with a short name without dot (like renaming com.example.myapp folder to Myapp Folder)
3 renaming the apk from base.apk to Myapp.apk
4 uninstalling the app
5 under TWRP recovery mode mount the system partiton and copying the Myapp folder to system/priv-app directory
6 chmod 755 Myapp Folder
7 chmod 644 Myapp.apk
8 wipe Dalvilk Cache and rebooting
Steps 2 and 3 might be useless it was just because I noticed the Priv-app directory used these naming Scheme for apps inside this folder
I tried this method also under Lineage 17.1 and Magisk 21.4 but then the phone was not able to reboot until I delete the newly created folder inside Priv-app
I also tried another method using Magisk Systemize (Terminal) module but the result was the same (the app was running but not as a system app)
As I have never seen that it was mentionned in any posted method explaning how to turn an app into a system app, the installed app was not signed with the platform key and the manifest was not including android:sharedUserId="android.uid.system"
Thanks in advance to those that will try to help.
Have you tried copying it to /system/app ?
Droid_76 said:
Have you tried copying it to /system/app ?
Click to expand...
Click to collapse
Yes and unfortunately the result was exactly the same
If DM-Verity & AVB are enabled these locks must get disabled before trying to operate on /system partition
jwoegerbauer said:
If DM-Verity & AVB are enabled these locks must get disabled before trying to operate on /system partition
Click to expand...
Click to collapse
Thanks but I don't think I have these enabled as I can mount write on the system partition, how do you check whether they are enabled or not ?
Newer Android versions have these locks by default enabled - they are set within file vbmeta.img : If enabled then phone's bootloader always loads device's Stock ROM, not any modded ROM where it doesn't matter whether partitions temporarily got mounted - by you - as RW or not.
Long story short: You've to unlock phone's bootloader, if not done yet, then disable the locks
Example code:
Code:
adb devices
adb reboot fastboot
fastboot devices
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
I wonder what's the difference between a system app and a common app.
James_Watson said:
I wonder what's the difference between a system app and a common app.
Click to expand...
Click to collapse
Apps developed as system app / system privileged app can access System APIs whereas common user app cannot.
Simply installing a common user app as system app / system privleged app makes NO SENSE at all.
jwoegerbauer said:
Newer Android versions have these locks by default enabled - they are set within file vbmeta.img : If enabled then phone's bootloader always loads device's Stock ROM, not any modded ROM where it doesn't matter whether partitions temporarily got mounted - by you - as RW or not.
Long story short: You've to unlock phone's bootloader, if not done yet, then disable the locks
Example code:
Code:
adb devices
adb reboot fastboot
fastboot devices
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Click to expand...
Click to collapse
Thanks but correct me if I'm wrong I could not have installed LineageOS TWRP and Magisk if Dm-verify was active so I don't think it is the issue here. I'm still looking forward what is preventing the app to run as a system app when it is installed in system/priv-app. The app is then running but as a standard app.
Lisadev said:
I'm still looking forward what is preventing the app to run as a system app when it is installed in system/priv-app. The app is then running but as a standard app.
Click to expand...
Click to collapse
Must admit I don't understand your problem: an app either runs or runs not where it doesn't matter where it's located. That's also true if an app has root rights granted.
IMO only thing of interest is what Android app's permissions are granted. A permission SYSTEM / ALLOW_ALL what I think you expect to be there doesn't exist. See also here:
https://developer.android.com/reference/android/Manifest.permission#public-constructors_1
I ran into problems with a couple of methods as well. People said they would work, but they were no good. But do you know what has worked for me, reliably and consistently?
App Systemizer.
Just search for App Systemizer through Magisk. Download and install, then reboot. Now, open up a terminal with superuser privileges. Yeah, gotta use a terminal for this one. Open terminal and enter the command su (in case you didn't know how to get superuser privileges through a terminal). Once you've done that, enter the command systemize and then follow the prompts.
I had problems with other methods. This was the one that worked. Give it a try.
Start command prompt on your computer to navigate where the APK file is located. Enable USB debugging on your device and connect it to the computer via USB cable. Your phone will automatically rebooted and your app will now be saved as a system app.
jwoegerbauer said:
Must admit I don't understand your problem: an app either runs or runs not where it doesn't matter where it's located. That's also true if an app has root rights granted.
IMO only thing of interest is what Android app's permissions are granted. A permission SYSTEM / ALLOW_ALL what I think you expect to be there doesn't exist. See also here:
https://developer.android.com/reference/android/Manifest.permission#public-constructors_1
Click to expand...
Click to collapse
Fore instance there is some permissions like REBOOT that require a system app you will not be able to reboot through PowerManager otherwise even if I know you can rebbot by other means on a rooted phone using some su command.
FailSafeNow said:
I ran into problems with a couple of methods as well. People said they would work, but they were no good. But do you know what has worked for me, reliably and consistently?
App Systemizer.
Just search for App Systemizer through Magisk. Download and install, then reboot. Now, open up a terminal with superuser privileges. Yeah, gotta use a terminal for this one. Open terminal and enter the command su (in case you didn't know how to get superuser privileges through a terminal). Once you've done that, enter the command systemize and then follow the prompts.
I had problems with other methods. This was the one that worked. Give it a try.
Click to expand...
Click to collapse
Yes thanks but if you read my first post you will see that I have tried Systemizer and it works in the sense that the app in installed inside system/priv-app folder and is able to run but it does not run as a system app
nihitthakkar said:
Start command prompt on your computer to navigate where the APK file is located. Enable USB debugging on your device and connect it to the computer via USB cable. Your phone will automatically rebooted and your app will now be saved as a system app.
Click to expand...
Click to collapse
I don't get it, you probable forgot to post something in your message
Lisadev said:
Yes thanks but if you read my first post you will see that I have tried Systemizer and it works in the sense that the app in installed inside system/priv-app folder and is able to run but it does not run as a system app
Click to expand...
Click to collapse
It doesn't? How can you tell? Maybe I've been missing something all this time. Maybe I only think App Systemizer works.
Lisadev said:
Não entendi, provavelmente você se esqueceu de postar algo em sua mensagem
Click to expand...
Click to collapse
Hello Friend! This question is a mystery to me. A while ago I created a thread explaining how to turn the Cerberus app into a system app and still survive a factory reset. I can guarantee you that my method worked until about 4 months ago.
This is the thread:
[GUIDE] [CERBERUS] [MAGISK] How to install Cerberus as System app.
Hello friends, I bring good news. Yes! It is possible to install Cerberus as a system app. (Even if it's rooted with Magisk) Yes, Cerberus will survive a factory reset. And your device will be traceable after a factory reset. Obviously the...
forum.xda-developers.com
For some reason now I also can't make an apk stay in Priv-app after reboot.
Even after I successfully flash vbmeta.img as described in the link below, I can't get it to work.
How to disable dm-verity or Android Verified Boot (AVB)
This is a quick guide showing how to disable dm_verity or Android Verified Boot (AVB). Disabling dm-verity / AVB is only important if you intend to flash custom images such as patched boot, custom rec
forum.hovatek.com
The question that everybody wants to hear. Did any methods work for you?
At the time of posting this (9th oct, 2021), this method works in my Android 10 (dunno 11, but most prob.)
Used Magisk root
1) First step, make /system writable (google made it read-only) by applying instruction from this thread - https://forum.xda-developers.com/t/script-android-10-universal-mount-system-read-write-r-w.4247311/
This will make sure that folders moved into /system/app or /system/priv-app are permanent across reboots.
2) Install Lucky Patcher (search google to download)
3) Go to Magisk manager and install Lucky Patcher Module for moving apps to system.
4) Normally install the app you are aiming for. Grant it all necessary permissions by going to apps settings. (don't skip this particular step. Skipping it can make permissions not able to grant later on)
5) Go to Lucky Patcher and select the app, select tools option and then select move to /system/priv-app. Tick the use Magisk module checkbox
( No, not done yet. Remember, module only mounts the app, not truly move it to /system/priv-app )
6) Turn off the Lucky Patcher Module in Magisk and reboot. You will notice app has disappeared from system (expected behaviour)(don't skip this step)
7) Open a terminal app.
Type-
su
mount -o remount,rw /
After success (may need to reboot),
open a root file manager, go to folder /data/adb/modules/luckypatcher_apps/system
Here, you would find the real apk folder for /system/priv-app as well as the permission configuration for /system/etc/permissions
Copy both folders to respective /system directories.
(we use Lucky Patcher here since it generates correct files with the right permissions, but of course, App Systemizer may also be used, but the steps change and I don't use it, so continue)
8) Go to /data/data folder and delete the app data folder for the app that was moved to /system/priv-app (prevents bugs if any)
9) Reboot phone. Now the app you wanted is fully system privileged with it actually existing in /system/priv-app (can check with TWRP's file manager).
There is no modules like App Systemizer or Lucky Patcher module mounting it. Done.
10) As an aside, just delete the /data/adb/modules/luckypatcher_apps/system folder. Like this, no problem will arise even if you enable this module again for whatever reason.
That's it, all done. Survival across reboots is already a sure thing. Now try to Factory Reset if you want to test if it survives across resets.
*Note - Of course, just make a Nandroid and internal SD backup in case.
Who doesn't want a "Save Game" option in life?
System App is not easily uninstalled by user, so it is a type of must have app as a android OS for a specific vendor(HTC, MOTO, Samsung).
Now how we can make an app as a system App.
Have source code
Have .apk Only
Step 1 Create a folder inside packages/apps/
First create a folder for your app ( Let say MyTestApp) inside packages/apps/ of your android AOSP downloaded source code.
Then create a Android.mk file inside the folder(MyTestApp).
Step 2 open Android.mk file and add folowing code Snippet and save this mk file.
Step 3 put your app name in build/target/product/ folder
open core.mk file from build/target/product/ folder and add your app name(MyTestApp) in
PRODUCT_PACKAGES tag at the bottom MyTestApp.
Now step by step procedure for .apk file
Step 1 will be same like above
only change is that in place of src, res folder just put your .apk file.
step 2 open Android.mk file and add folowing code Snippet.
Step 3 will be same as above mention for Android source code (a)
This is all about how to make an android app as a system App.
Jeffrey A. Hancock said:
System App is not easily uninstalled by user, so it is a type of must have app as a android OS for a specific vendor(HTC, MOTO, Samsung).
Now how we can make an app as a system App.
Have source code
Have .apk Only
Step 1 Create a folder inside packages/apps/
First create a folder for your app ( Let say MyTestApp) inside packages/apps/ of your android AOSP downloaded source code.
Then create a Android.mk file inside the folder(MyTestApp).
Step 2 open Android.mk file and add folowing code Snippet and save this mk file.
Step 3 put your app name in build/target/product/ folder
open core.mk file from build/target/product/ folder and add your app name(MyTestApp) in
PRODUCT_PACKAGES tag at the bottom MyTestApp.
Now step by step procedure for .apk file
Step 1 will be same like above
only change is that in place of src, res folder just put your .apk file.
step 2 open Android.mk file and add folowing code Snippet.
Step 3 will be same as above mention for Android source code (a)
This is all about how to make an android app as a system App.
Click to expand...
Click to collapse
This means to compile the ROM yourself?