Database Info

[Guide]Remove system apps even from your unrooted device without any exploit

THIS IS BEST METHOD IF U WANT TO REMOVE UNWANTED SYSTEM APP AND YOUR DEVICE IS UNROOTED...
​REQUIREMENT
1. I am doing this in Ubuntu 13.04(64-bits)
2. Adb(If u dont have adb the download my adb attachment)
3. Assuming that u have placed the adb file in home directory...
PROCESS
1. Open the terminal by pressing "Ctrl+t+Alt" buttons together..
2. Now type the following commands--- ./adb root
3. Next Command --- ./adb shell
4. If u can see "[email protected]" Then u r going right...
5. Next Command--- cd system/app
6. This is the directory where all system apps r located..
7. Next Command--- ls
8. it Will list all the system apps.Make a close look at that particular apk that u want to remove.
9. Next Command--- mount -o remount,rw /system
10. Next Command-- rm x.apk
11. x.apk ,x is the name of apk file that u want to remove
12. Next Command - mount -o remount,r /system
13. Reboot your phone and done...
CAUTION !!!!!!!!! IF ANYTHING HAPPENS TO YOUR PHONE THAT IS UNEXPECTED THEN U R RESPONSIBLE FOR IT,,, DO IT ON YOUR RISK!!!!!!!!! IT WORKED ON MY PHONE!!!!!!!!!! ​
!!!!!!!!!!!!!IF NOT SURE OF THIS METHOD THEN YOU TRY IT ON AN EMULATOR THAT IS UNROOTED ALREADY AND GET SURE OF IT.....​
ENJOY OPEN SOURCENESS​

your title says
Remove system apps even from your unrooted device without any exploit
Click to expand...
Click to collapse
next you say
THIS IS BEST METHOD IF U WANT TO REMOVE UNWANTED SYSTEM APP AND YOUR DEVICE IS UNROOTED...
Click to expand...
Click to collapse
but now the important thing
THIS MEYHOD WILL WORK IF YOUR DEVICE IS ROOTED
Click to expand...
Click to collapse
means your thread title is misleading, you need a rooted phone to do that as
./adb root
Click to expand...
Click to collapse
will fail as well.
also you need to enable Debugging Mode on your phone first and you need to grant ADB root permissions on an rooted phone as well.
also you can do
./adb remount
Click to expand...
Click to collapse
instead of
mount -o remount,rw /system
Click to expand...
Click to collapse
oh, and you need to make your adb binary executeable with
chmod +x
Click to expand...
Click to collapse

You must be rooted for this method to work...

thxxx.. dude
Evisceration said:
your title says
next you say
but now the important thing
means your thread title is misleading, you need a rooted phone to do that as
will fail as well.
also you need to enable Debugging Mode on your phone first and you need to grant ADB root permissions on an rooted phone as well.
also you can do
instead of
oh, and you need to make your adb binary executeable with
Click to expand...
Click to collapse
now i got it dude

[Q] [HELP] /system read-only can't fix on adb no su response

i ported a LeWa OS ROM for my device and everything seemed to work perfectly, booted up without hassle, apps working, and everything was fine. not until i came to the point where i have to check the root capability. it seems like the /system partition was locked as read-only. i pre-rooted the rom with supersu and su binaries properly placed just like i do with other roms i ported. but this one is different. even on adb, the su isn't responding. although the request is showing on the phone and i click on grant, still there is no su response or whatsoever, that is why i cant remount it as rw.
so i was wondering if there is something i have to port from stock boot.img to port boot.img to permanently mount /system partition in RW capability.
i hope anyone can help me

How about making an insecure kernel so you can access root without requesting su?

xlSKYFiRElx said:
i ported a LeWa OS ROM for my device and everything seemed to work perfectly, booted up without hassle, apps working, and everything was fine. not until i came to the point where i have to check the root capability. it seems like the /system partition was locked as read-only. i pre-rooted the rom with supersu and su binaries properly placed just like i do with other roms i ported. but this one is different. even on adb, the su isn't responding. although the request is showing on the phone and i click on grant, still there is no su response or whatsoever, that is why i cant remount it as rw.
so i was wondering if there is something i have to port from stock boot.img to port boot.img to permanently mount /system partition in RW capability.
i hope anyone can help me
Click to expand...
Click to collapse
Download SuperSU and reinstall its binaries again.
Or you can try adbd Insecure app (not free)

janekmuric said:
Download SuperSU and reinstall its binaries again.
Or you can try adbd Insecure app (not free)
Click to expand...
Click to collapse
supersu or any of its binaries cannot help me. as every app that request root privileges hangs when grant permission is given. ill try adbd insecure app. gonna throw my money to this one

xlSKYFiRElx said:
supersu or any of its binaries cannot help me. as every app that request root privileges hangs when grant permission is given. ill try adbd insecure app. gonna throw my money to this one
Click to expand...
Click to collapse
I think the adb insecure app still requires su, you can upload the boot.img and i'll make it insecure (automatically root via adb, no su required)

Oooohh
xlSKYFiRElx said:
supersu or any of its binaries cannot help me. as every app that request root privileges hangs when grant permission is given. ill try adbd insecure app. gonna throw my money to this one
Click to expand...
Click to collapse
I didn't understand you correctly. Anyways from what I understand noe you can't give root to any app at all. Try using framaroot to re-root maybe it works. You have to find out the reason it hangs. I'm placing my bet on the corrupt or bad binary.

janekmuric said:
I didn't understand you correctly. Anyways from what I understand noe you can't give root to any app at all. Try using framaroot to re-root maybe it works. You have to find out the reason it hangs. I'm placing my bet on the corrupt or bad binary.
Click to expand...
Click to collapse
He's right, redownload the binaries again, if it still hangs, it might be the ROM.
Add this to build.prop if you want root via adb:
ro.secure=0

janekmuric said:
I didn't understand you correctly. Anyways from what I understand noe you can't give root to any app at all. Try using framaroot to re-root maybe it works. You have to find out the reason it hangs. I'm placing my bet on the corrupt or bad binary.
Click to expand...
Click to collapse
3DMapPlayer said:
He's right, redownload the binaries again, if it still hangs, it might be the ROM.
Add this to build.prop if you want root via adb:
ro.secure=0
Click to expand...
Click to collapse
sorry for the confusion but here is the case, i ported this (LEWA) ROM and i pre rooted with, placed the updated su binary to /system/xbin and the latest supersu.apk to /system/app. the phone boots properly and according to the rom. i installed root checker but when it checked for root it says the root is not installed properly but the supersu dialog box is appearing and i can press the grant button and a toast appears saying that it is granted superuser permissions. i tried to re-root using framaroots barahir exploit but it said "Half-Success" because the system partition is mounted read-only.
i tried using root explorer, when i try to mount system as r/w the supersu dialog appears and i can press the grant button again, also the toast appears saying that the app is granted superuser permission but then the application (root explorer) hangs, i tried other root explorer application still the same.
so what i want to achieve is to mount /system as read-write partition
i tried using ADB, but when i try to type su everything i type reappears
example: when i type 'su' the result is like this:
Code:
what i type: su
what show: su
what i type: busybox mount
what show: busybox mount
or simply, everything i type reappears and the command is not executed.
i tried to modify boot.img by editing build.prop and setting this values
#
# ADDITIONAL_DEFAULT_PROPERTIES
#
ro.secure=0
ro.allow.mock.location=1
persist.mtk.aee.aed=on
ro.debuggable=1
persist.sys.usb.config=mass_storage,mtp
persist.service.acm.enable=0
ro.mount.fs=EXT4
Click to expand...
Click to collapse
and also editing init.rc and setting this values
Code:
mount yaffs2 [email protected] /system rw remount
mount ubifs [email protected] /system rw remount
but still no luck. i hope you guys understand, sorry for my crappy english. not my language
i'll try to reflash the rom so that i can supply screenshots
also, here is a copy of my boot.img

Got it!
xlSKYFiRElx said:
sorry for the confusion but here is the case, i ported this (LEWA) ROM and i pre rooted with, placed the updated su binary to /system/xbin and the latest supersu.apk to /system/app. the phone boots properly and according to the rom. i installed root checker but when it checked for root it says the root is not installed properly but the supersu dialog box is appearing and i can press the grant button and a toast appears saying that it is granted superuser permissions. i tried to re-root using framaroots barahir exploit but it said "Half-Success" because the system partition is mounted read-only.
i tried using root explorer, when i try to mount system as r/w the supersu dialog appears and i can press the grant button again, also the toast appears saying that the app is granted superuser permission but then the application (root explorer) hangs, i tried other root explorer application still the same.
so what i want to achieve is to mount /system as read-write partition
i tried using ADB, but when i try to type su everything i type reappears
example: when i type 'su' the result is like this:
Code:
what i type: su
what show: su
what i type: busybox mount
what show: busybox mount
or simply, everything i type reappears and the command is not executed.
i tried to modify boot.img by editing build.prop and setting this values
and also editing init.rc and setting this values
Code:
mount yaffs2 [email protected] /system rw remount
mount ubifs [email protected] /system rw remount
but still no luck. i hope you guys understand, sorry for my crappy english. not my language
i'll try to reflash the rom so that i can supply screenshots
also, here is a copy of my boot.img
Click to expand...
Click to collapse
Flash the attached ZIP. It will reinstall SuperSU and all needed files.

Root user cannot 'remount'

Hi,
after a lots of hassle I finally accessed the root access into my Sony z2 tablet. But the Root Checker Basic app says
Sorry! Root access is not properly installed on this device.
Click to expand...
Click to collapse
I can still run
Code:
adb root
without error. And the
Code:
adb shell whoami
returns "root".
Still when I run
Code:
adb remount
it says
remount of /system failed; couldn't make block device /dev/block/platform/msm_sdcc.1/by-name/system writable: Permission denied
remount failed
Click to expand...
Click to collapse
I need to remount the device because I want to move an APK to the "/system/priv-apps" folder.

Did you try remounting directly from an adb shell ?
mount -o remount,rw /system

ddscentral said:
Did you try remounting directly from an adb shell ?
mount -o remount,rw /system
Click to expand...
Click to collapse
Yes I tried. it says
mount: Operation not permitted
Click to expand...
Click to collapse

Toriq100 said:
Yes I tried. it says
Click to expand...
Click to collapse
Are you trying to mount as root ? (your shell prompt should start with # and not $). If not, use "su" command to get root and then try mounting again.
If remount fails even from a root shell, check your SELinux status with "getenforce" command.

ddscentral said:
Are you trying to mount as root ? (your shell prompt should start with # and not $). If not, use "su" command to get root and then try mounting again.
If remount fails even from a root shell, check your SELinux status with "getenforce" command.
Click to expand...
Click to collapse
Yes, I am trying to mount as root so that I can move an APK to "system/priv-apps". My shell prompt does start with #. I cannot use "su", it says "[-] Daemon is stop".
I checked SELinux status. It says "Enforcing", then I tried "adb shell setenforce 0" it says "setenforce: Couldn't set enforcing status to '0': Permission denied". :'(

Likely SELinux is preventing remount.
Are you still using the original software or a custom ROM ?

ddscentral said:
Likely SELinux is preventing remount.
Are you still using the original software or a custom ROM ?
Click to expand...
Click to collapse
Original software (I gained the root access using KingRoot, tried everything else, didn't work)

I would either flash SuperSU with a custom recovery (assuming you can unlock the bootloader) or flash a third party ROM.

ddscentral said:
I would either flash SuperSU with a custom recovery (assuming you can unlock the bootloader) or flash a third party ROM.
Click to expand...
Click to collapse
I tried recovering with custom ROM but failed. Here I asked a question for reference, but didn't find working solution.

Make system as rw on android 10?

So apparently klaxosaur custom rom doesn't have rw enabled as it is ro locked, is there any way to make it rw permanently? and yes, i have tried @lebigmac 's method on making system rw. on orangefox all it says is "error code 255 please install unzip and try again"

Hi @Fgacko did you try to manually install and run my script as per instructions?
Hopefully I can fix that annoying automatic installation error 255 in next version Not sure why it happens in some recoveries and others not.
Do you have recovery log from /tmp/recovery.txt by any chance?

lebigmac said:
Hi @Fgacko did you try to manually install and run my script as per instructions?
Hopefully I can fix that annoying installation error 255 in next version Not sure why it happens in some recoveries and others not.
Do you have recovery log from /tmp/recovery.txt by any chance?
Click to expand...
Click to collapse
I don't have the recovery log, i didn't try the manual install yet. How do you do it? *I don't understand the instructions for manual installation you said in your thread*

Fgacko said:
I don't have the recovery log, i didn't try the manual install yet. How do you do it? *I don't understand the instructions for manual installation you said in your thread*
Click to expand...
Click to collapse
Alright i've done it, now what?

Fgacko said:
Alright i've done it, now what?
Click to expand...
Click to collapse
Universal init.d enabler still says this

Please send me your log files from this folder:
/data/local/tmp/systemrw_1.32/log/
Thanks.

lebigmac said:
Please send me your log files from this folder:
/data/local/tmp/systemrw_1.32/log/
Thanks.
Click to expand...
Click to collapse
no log file appear there

lebigmac said:
Please send me your log files from this folder:
/data/local/tmp/systemrw_1.32/log/
Thanks.
Click to expand...
Click to collapse
ah i needed to run the script, here
systemrw: Initiating procedure...
systemrw: Device is in Android mode. Ignoring
systemrw: Current device: samsung
systemrw: Current Android version: 10
systemrw: Current SELinux status: Permissive
systemrw: Unable to locate super partition on device. Ignoring
systemrw: /system is already R/W capable. Ignoring
systemrw: /product is already R/W capable. Ignoring
systemrw: /vendor is already R/W capable. Ignoring
systemrw: Adjusting permissions...
systemrw: Attempting to disable dm-verity and verification...
systemrw: There was a problem removing read-only restriction(s) of your device. Abort

lebigmac said:
Please send me your log files from this folder:
/data/local/tmp/systemrw_1.32/log/
Thanks.
Click to expand...
Click to collapse
also, every restart or boot, my tmp folder gets wiped

@Fgacko type this and send me result please:
Bash:
adb shell
su
tune2fs -l /dev/block/by-name/system | grep "features"

lebigmac said:
@Fgacko type this and send me result please:
Bash:
adb shell
su
tune2fs -l /dev/block/by-name/system | grep "features"
Click to expand...
Click to collapse
hmm ok, by any chance you know how to revert build.prop? like the default.prop and prop.default, its cause i accidentally changed a line and its stuck in bootloop

Fgacko said:
hmm ok, by any chance you know how to revert build.prop? like the default.prop and prop.default, its cause i accidentally changed a line and its stuck in bootloop
Click to expand...
Click to collapse
nvm, ill just reflash the rom

Fgacko said:
hmm ok, by any chance you know how to revert build.prop? like the default.prop and prop.default, its cause i accidentally changed a line and its stuck in bootloop
Click to expand...
Click to collapse
That's easy. Simply:
boot into custom recovery
login with your password to decrypt /data
mount /system (/system_root) in the mount options
remount /system (/system_root) as r/w by running mount -o remount,rw /system_root
replace faulty default.prop with your original backup from computer
done

lebigmac said:
That's easy. Simply:
boot into custom recovery
login with your password to decrypt /data
mount /system (/system_root) in the mount options
remount /system (/system_root) as r/w by running mount -o remount,rw /system_root
replace faulty default.prop with your original backup from computer
done
Click to expand...
Click to collapse
problem is, every time i reboot to system it replaces it with the faulty one

Fgacko said:
problem is, every time i reboot to system it replaces it with the faulty one
Click to expand...
Click to collapse
ill just reflash the rom and send you the log file thingy later since its 1:32 am here

lebigmac said:
@Fgacko type this and send me result please:
Bash:
adb shell
su
tune2fs -l /dev/block/by-name/system | grep "features"
Click to expand...
Click to collapse
do i need to run this in adb?

Fgacko said:
do i need to run this in adb?
Click to expand...
Click to collapse
also, when i went to /dev/block/by-name/ i dont see a file or folder called "system", instead it was "SYSTEM" with 0 B

Fgacko said:
also, when i went to /dev/block/by-name/ i dont see a file or folder called "system", instead it was "SYSTEM" with 0 B
Click to expand...
Click to collapse
ok it worked

Thanks for the screenshot. I can't believe you actually got that command to work
It looks like your device doesn't have shared_blocks read-only feature so my script will not be able to remove the read-only lock of your device
If you want you can also check your other partitions such as product or vendor with the same tune2fs -l command but it should be the same result.
You must first try to figure out which Android feature is responsible for the read-only lock of your device.
Please let me know if you figure it out. Thanks.
systemrw: /system is already R/W capable. Ignoring
systemrw: /product is already R/W capable. Ignoring
systemrw: /vendor is already R/W capable. Ignoring
Click to expand...
Click to collapse
According to your script log you can already mount your partitions as R/W. Did you try mounting your partitions as r/w yet (see picture below)?
Are you using custom ROM? Some custom ROM's can do this by default. Sadly not all of them.
Good luck!

lebigmac said:
Thanks for the screenshot. I can't believe you actually got that command to work
It looks like your device doesn't have shared_blocks read-only feature so my script will not be able to remove the read-only lock of your device
If you want you can also check your other partitions such as product or vendor with the same tune2fs -l command but it should be the same result.
You must first try to figure out which Android feature is responsible for the read-only lock of your device.
Please let me know if you figure it out. Thanks.
According to your script log you can already mount your partitions as R/W. Did you try mounting your partitions as r/w yet (see picture below)?
Are you using custom ROM? Some custom ROM's can do this by default. Sadly not all of them.
Good luck!
Click to expand...
Click to collapse
yeah im using klaxosaur custom rom, i tried the command "mount -o remount,rw /" but on every boot it becomes ro again and the command only works for whatever i mounted it. ex if i mounted it in terminal, other apps like mt manager still is ro locked. how do you know which read only lock is on my device?

Question How to pull Build.Prop...

Here's where I'm at. I've got the system to give me the Mount /System option in recovery, now i just need assistance getting the build.prop pulled to my PC. What's the procedure for pulling the build.prop from the Android to PC via ADB while the system is mounted in recovery? Why am I getting one of these two ADB errors?
Error 1: Connect failed: closed.
error 2: Failed to get feature set: no devices or emulators
OR, am I approaching it wrong?
Thanks in advance,
K0mraid3

you dont need to be in recovery to do it via adb....
adb pull /system/build.prop
that will pull it to where evr you run the adb command
which would be
C;\adb more than likely
or you can choose a destination with
adb pull /system/build.prop c:\buildprop
if you create a folder called "buildprop" in the root directory of c:\
at least thats how i remember doing it many years ago, ive been away for a while at her majesties pleasure, so i cant try it currently as im not rooted

gav83collins said:
you dont need to be in recovery to do it via adb....
adb pull /system/build.prop
that will pull it to where evr you run the adb command
which would be
C;\adb more than likely
or you can choose a destination with
adb pull /system/build.prop c:\buildprop
if you create a folder called "buildprop" in the root directory of c:\
at least thats how i remember doing it many years ago, ive been away for a while at her majesties pleasure, so i cant try it currently as im not rooted
Click to expand...
Click to collapse
Thanks, so far, its still for some reason denying me permission when OS is booted. So i just cant quite figure out where im supposed to execute these commands, is my issue. I can boot directly to BL from recovery menu, but i can also mount system. i think maybe i need sto send command for r/w.. will try that now.

Another question, when i mount /system in recovery, does that carry over on boot?

no you can re mount system via adb though
Code:
$ adb shell
$ su
# mount -o rw,remount /system

gav83collins said:
no you can re mount system via adb though
Code:
$ adb shell
$ su
# mount -o rw,remount /system
Click to expand...
Click to collapse
1.Needs root for this command. If he have rooted device then why so much trouble needed. Simply use root explorer to copy
2.Since long Samsung have removed system from proc/mounts still magisk system_root can be used
3.Even with system in mounts you can't do system rw on S22 because of Samsung have implemented extra layer of protection. Even not with magisk system_root too
Indeed as of now there is no method available to make stock system/vendor/product/odm rw on S22 even with root access.
4.To copy file from system rw mount not needed, ro is fine

dr.ketan said:
1.Needs root for this command. If he have rooted device then why so much trouble needed. Simply use root explorer to copy
2.Since long Samsung have removed system from proc/mounts still magisk system_root can be used
3.Even with system in mounts you can't do system rw on S22 because of Samsung have implemented extra layer of protection. Even not with magisk system_root too
Indeed as of now there is no method available to make stock system/vendor/product/odm rw on S22 even with root access.
4.To copy file from system rw mount not needed, ro is fine
Click to expand...
Click to collapse
im yet to root my device so i cant test but what about
Code:
adb root
adb disable-verity
adb reboot
Then
Code:
adb root
adb remount

gav83collins said:
im yet to root my device so i cant test but what about
Code:
adb root
adb disable-verity
adb reboot
Then
Code:
adb root
adb remount
Click to expand...
Click to collapse
Do you got what I meant?
leave it.

dr.ketan said:
WTF
Do you got what I meant?
leave it.
Click to expand...
Click to collapse
look, there is no need for condescension and bad language, a simple "no" would have sufficed

Lol not meant to hurt you! but on which planet WTF is bad language
Here search WTF on xda

dr.ketan said:
1.Needs root for this command. If he have rooted device then why so much trouble needed. Simply use root explorer to copy
2.Since long Samsung have removed system from proc/mounts still magisk system_root can be used
3.Even with system in mounts you can't do system rw on S22 because of Samsung have implemented extra layer of protection. Even not with magisk system_root too
Indeed as of now there is no method available to make stock system/vendor/product/odm rw on S22 even with root access.
4.To copy file from system rw mount not needed, ro is fine
Click to expand...
Click to collapse
So my device is strange. It doesn't have root, but it indeed shows options in recovery to apply updates from ADB, SD Card aswell as boot directly to BL and to Mount /System, but when I'm booted, the OS is denying me permission to "Su" . I have verified that USB debugging is activated. So I'm trying to see if there's a way to pull the build.prop from Recovery since the Mount /System option is available, but my computer refuses to recognize the device in while in recovery, but easily finds it in Download, BL mode. No FRP lock. No accounts on device. But also no option to unlock bootloader. This device in particular is/was a development sample so I have no clue what the current state of the bootloader etc is in terms of being unlocked prior to me working on it.

It'd also worth noting that this device was loaded with Android 11 when I received it. I'm not kidding. So idk what's going on with this FrankenGalaxy

K0mraid3 said:
It'd also worth noting that this device was loaded with Android 11 when I received it. I'm not kidding. So idk what's going on with this FrankenGalaxy
Click to expand...
Click to collapse
K0mraid3 said:
So my device is strange. It doesn't have root, but it indeed shows options in recovery to apply updates from ADB, SD Card aswell as boot directly to BL and to Mount /System, but when I'm booted, the OS is denying me permission to "Su" . I have verified that USB debugging is activated. So I'm trying to see if there's a way to pull the build.prop from Recovery since the Mount /System option is available, but my computer refuses to recognize the device in while in recovery, but easily finds it in Download, BL mode. No FRP lock. No accounts on device. But also no option to unlock bootloader. This device in particular is/was a development sample so I have no clue what the current state of the bootloader etc is in terms of being unlocked prior to me working on it.
Click to expand...
Click to collapse
These options are normal in stock recovery and can be used only for flashing official zip (OTA), To have root access on your recovery, you needs custom one (TWRP) which is in development stage on S22
Without twrp, You needs to root device (must have oem unlock option in development option) to access system files while you are booted to android.
Android 11 on S22? Can you show me screenshot of settings - about phone - software info?

dr.ketan said:
These options are normal in stock recovery and can be used only for flashing official zip (OTA), To have root access on your recovery, you needs custom one (TWRP) which is in development stage on S22
Without twrp, You needs to root device (must have oem unlock option in development option) to access system files while you are booted to android.
Android 11 on S22? Can you show me screenshot of settings - about phone - software info?
Click to expand...
Click to collapse
Thanks for the clear answer, that's kind of what I'm working on is trying to gain root access, but like you said, I need oem unlocking, which isn't on this device. So I'm trying to find a backdoor/vulnerability that will take me even one step closer to atleast finding a way to set ro.secure. prop. Something VERY interesting I did find, is that if you put the device to Debug medium or high via device keystring activity, and play with the key combos, you can get booted into a mode called RDX, if you plug it into your dev system with the right drivers, it's treats the phone as if it were a Disk and shows a bunch of VZW upgrade software ment for PCs. I've installed it but haven't got it working quite yett.

No idea what you have shown in screenshot, I'd asked something else.

dr.ketan said:
No idea what you have shown in screenshot, I'd asked something else.
Click to expand...
Click to collapse
Maybe Heindall will give me better results. I just refuse to believe the manufacturers have outsmarted us all on this.