Database Users

How to Install/Remove System Apps on Android [MUST HAVE ROOT]

########## IMPORTANT UPDATE ##########
There is an APP available that makes this much simpler
* No Console Commands Needed
* You still MUST HAVE ROOT
* It must be installed on internal memory to work correctly
* Be sure you know what a system app does before you remove it.
* If you remove a vital app you could mess up your system completely.
The APP is Called: "System APP Remover"
Here's a Link to Download it: http://www.megaupload.com/?d=ZFC2C1R7
Mirror Download Link: http://www.mediafire.com/?h3n3ftbwilshcvn
######################################
Here are the console commands for installing/removing system apps in android console emulator, very easy ; )
You must have ROOT and console emulator, I found this very helpful, so I hope it helps others as well...
_____________________________________________________________________________________
Install App to System:
Place APK file in the root folder on your sd card.
Open terminal and enter these commands:
# su
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
# cat /sdcard/filename.apk > /system/app/filename.apk
# mount -o remount,ro -t yaffs2 /dev/block/mtdblock3 /system
# reboot
_____________________________________________________________________________________
Remove App from System (Be careful what you remove):
# mount -o remount,rw /system
# rm /system/app/Filename.apk
[Optional, to make read-only again]
# mount -o remount,r /system
[When Finished]
# reboot
_____________________________________________________________________________________
****KEY****
"#" means root command will follow
[Notes are in these brackets and aren't commands]
- ENJOY
ALSO...
**** I'm new to Android APP creation, but if anyone can automate this script to make a simple One-Click GUI APP that would be awesome, all I ask is that you put my name in the co-dev/"Thanks to" list for the app, just so I can say I helped ;-) ****
- CuriousAndroid

I am trying to reinstall some files I uninstalled. I went to the following link on this site and found some apps that people said could be removed - http://forum.xda-developers.com/showthread.php?t=773142
however, my Act1 video player now quits whenever I receive an incoming text, so I need to reinstall some programs and see which one is causing the problem
I downloaded an app called Android Terminal Emulator by Jack Palevich. I tried a "reboot" command (without the #) but it said reboot operation not permitted. Is this the Emulator I need to reinstall files? Am I doing something wrong?
--------------
EDITED:
ok nevermind, i realized the "su" command gives superuser access needed for the reboot....going to try to install files now

yeah, to use any root commands "su" must be used first otherwise the shell will think your just some generic user with limited privileges and nothing will work.
It's very important to identify any apps you plan on removing before you attempt it to make sure it isn't needed by another process.
You got lucky, some apps once removed can cause the whole rom to fail, so be careful!
- CuriousAndroid

well i think i messed something up...is there a way to recover back to stock after using the sdx stock app remover? i removed the video player but tried reinstalling it...when i uninstalled it from sdx, i noticed my other video player (Act1) would quit whenever i'd get an incoming text
i have all the .apks backed up, but after attempting to reinstall the stock video player, it hangs in MyFiles...then i reset back to factory (no Act1), and it can't play my videos, i get the error "No applications can perform this action"
Is there a way to recovery back to stock with all applications installed and in tact? i have all the .apks, but this video player won't work, after following your instructions above
thanks

It will work. Check the following:
* All shell commands are CASE-sensitive, so if the app is called Vending.apk you can't type vending.apk
* for the command to work you must have the apk on the root of your SDcard, not in sub-directories.
* if you have a copy of the rom you installed you can unzip it on your PC and find the system app folder, which you can use to cross-refference with the system/app folder on your phone to see if your missing something else.
in terminal you can list system apps like this:
# su
# cd /system/app/
# ls | more
[that will allow you hit space bar to navigate through app list if it's longer than a page,press ESC when done to go back to prompt]
* If all else fails you can backup your settings to your sd card and re-install your rom (as a last resort)
-Good Luck

curiousandroid said:
Install App to System:
Place APK file in the root folder on your sd card.
Open terminal and enter these commands:
# su
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
# cat /sdcard/filename.apk > /system/app/filename.apk
# mount -o remount,ro -t yaffs2 /dev/block/mtdblock3 /system
# reboot
_____________________________________________________________________________________
Remove App from System (Be careful what you remove):
# mount -o remount,rw /system
# rm /system/app/Filename.apk
[Optional, to make read-only again]
# mount -o remount,r /system
[When Finished]
# reboot
_____________________________________________________________________________________
****KEY****
"#" means root command will follow
[Notes are in these brackets and aren't commands]
- ENJOY
ALSO...
**** I'm new to Android APP creation, but if anyone can automate this script to make a simple One-Click GUI APP that would be awesome, all I ask is that you put my name in the co-dev/"Thanks to" list for the app, just so I can say I helped ;-) ****
- CuriousAndroid
Click to expand...
Click to collapse
When I am doing the first part here of installing app to system I dont just simply do that first I can already have an app ready to go that I want to move to sd card right? I am just making sure I didnt have to do that simply first before I even start moving the apps. This site has be great and thanks for everybody help. Wish I would have known have this site way back when.

What is "yaffs2" standing for? I type "yaffs" instead of "yaffs2". What has this done to my system? Do I have to expect any "side-effects"?
When I call # ls | more to list the directories content, the apk is listed but it is not installed yet. Is there anything else i have to do?

yaffs is nand flash filesystem
yaffs2 is more elaborate updated version
yaff2 has greater support
so if your device isnt supported by yaffs1, it may not work.
it's best to follow the commands as they're written.
apps still appear as apks in system/apps folder after installation.

Haha thats funny!! I downloaded this app.. put it on my sdcard.. installed it and when i tried to open it it said " Shame on you for trying to pirate a 1.00 app "

If you have Applanet just go there and look for Systemapp Remover - it's a bit older version but seems to do the job.

By mistake my contacts.apk is removed. Above trick also not worked. my phone is LG GT540. Pl suggest any other way.

rajhan9412 said:
By mistake my contacts.apk is removed. Above trick also not worked. my phone is LG GT540. Pl suggest any other way.
Click to expand...
Click to collapse
Grab the contacts.apk from the rom you're running and push it back in. Btw titanium backup removes system/apps without terminal commands while allowing to to make a backup first in case u want. it back or for little hickups such as this.
Sent from transparent xda app by theimpaler747

I did everything right, and the apps that I removed disappeared from the app drawer. But, after I reboot my phone, they show up again.
What can I do?

In terminal type
ls system/app
Hit enter and see if said apps are in the list
Sent from my HTC Sensation 4G using XDA App

i got a better method.
app is called app quarantine
it need root and is totally free
it can quaratine every app including rom apps and system apps
really that thing awesome. no manuall backup needed anymore and as long you dont brick the os you can easy try and error - but of course still be carefull and login and activate com.brain.logic.provider lol

Hi there i use root explorer and that is the easiest way i think to remove system apps on android phones [root required] you can download root explorer from the market or get it from 4shared just search for root explorer.apk install it and navigate to /system/apps/ and the app you wish to delete long press the app and delete make sure you mount as read/write instead of read only.
Hope this helps 
@0mpranav

actually its not and actually you didnt read my post
i advertise this little peace of freeware because it really made my day (im not related in anyway to the developer)
the quarantine removes it but store it automatically in another directory
just multiselect and press one button DONE
no need to single delete something because you always should backup first
for example turns out on samsungs device EMAIl application is also related to exchange sync - huh i was happy to restore it
really take a look -
btw i hate the root explorer - for some taksts might be usefull but fileexpert is way better in that and its free as the quaratine app is too

bofh999 said:
actually its not and actually you didnt read my post
i advertise this little peace of freeware because it really made my day (im not related in anyway to the developer)
the quarantine removes it but store it automatically in another directory
just multiselect and press one button DONE
no need to single delete something because you always should backup first
for example turns out on samsungs device EMAIl application is also related to exchange sync - huh i was happy to restore it
really take a look -
btw i hate the root explorer - for some taksts might be usefull but fileexpert is way better in that and its free as the quaratine app is too
Click to expand...
Click to collapse
You were right mate got problems in upgrading my nexus one coz i deleted the .odex system apps directly without any backup but upgraded to 2.3.6 with some trial and error method but lost root access any help would be appriciated 
@0mpranav

Installing system app
Hi, i have the same problem. I tried Root Explorer, and the Shell Commands method (with Cat command), the files i copy are in there, with all the permissions and everything, but when i reboot, none of them are installed, and my "contacts" app is still broken. Can anyone help please?

Nevermind, found the problem. I needed the exact files for my Atrix 4G with the same android version.

Just rooted - unable to backup

Hi all,
Ive spent to weekend reading about rooting and ROMS/Kernels and decided to try it. I used a root kit found here from Mskip (great kit). Ive sucessfully rooted, and then sucessfully installed Smooth Rom 4.3 with the Motley kernel.
Ive downloaded Titanium Backup and Rom Manager. TB worked and I did a backup (which I now cant find) (i have ES File Explorer). I upgraded to Titanium Pro, and now when I open the app is states root was denied. I remember when I first opened TB SuperSu asked me to grant it access. After a reboot I opened SuperSu and stated a Binary update was necessary and performed it.
Now TB pro states root was denied, when I open SuperSu there is nothing there in the apps list, and I dont know how to manually grant TB root access.
Sorry if this is noobish, not sure what to do and I dont want to keep going without a backup.
Edit: When I try to backup in ROM Manager I hit backup, it brings up the notification to name the backup, I hit ok and nothing happens.

cam75 said:
After a reboot I opened SuperSu and stated a Binary update was necessary and performed it.
Now TB pro states root was denied, when I open SuperSu there is nothing there in the apps list, and I dont know how to manually grant TB root access.
Click to expand...
Click to collapse
That sort of sounds like the SuperSU "su" update might have failed. Can you get root with other apps? (e.g. go in to a terminal emulator and type "su")
Note there is a chicken-and-egg problem if (either) SuperSU/su or Superuser/su fail: they need root themselves to remount /system so that the "su" binary can be updated.
If no apps can get root, then you sort of have "lost root", and the fix is to manually insert the .apk and su binary into /system/app and /system/bin/su (or /system/xbin/su depending on flavor!) either with a flash package in recovery, or manually via the adb shell command line (with custom recovery running).
HTH
PS you should be able to just manually start the recovery and do a backup in the meantime, no? The fact that ROM manager isn't doing anything could either be a lack-of-root problem or something else (a busybox dependency?)

bftb0 said:
That sort of sounds like the SuperSU "su" update might have failed. Can you get root with other apps? (e.g. go in to a terminal emulator and type "su")
Note there is a chicken-and-egg problem if (either) SuperSU/su or Superuser/su fail: they need root themselves to remount /system so that the "su" binary can be updated.
If no apps can get root, then you sort of have "lost root", and the fix is to manually insert the .apk and su binary into /system/app and /system/bin/su (or /system/xbin/su depending on flavor!) either with a flash package in recovery, or manually via the adb shell command line (with custom recovery running).
HTH
PS you should be able to just manually start the recovery and do a backup in the meantime, no? The fact that ROM manager isn't doing anything could either be a lack-of-root problem or something else (a busybox dependency?)
Click to expand...
Click to collapse
thx for the quick response, however much of that is WAY over my head. I opened terminal emulator and typed su and this is what popped up. 1 [email protected]:/ $
When TB is opened it states error "sorry I could not acquire root privilegdes. this applidation will not work. please verify that your rom is rooted and try again. this attempt was made using the "/system/xbin/su" command.
I dont see busybox in my app drawer

cam75 said:
thx for the quick response, however much of that is WAY over my head. I opened terminal emulator and typed su and this is what popped up. 1 [email protected]droid:/ $
Click to expand...
Click to collapse
If the SuperSU app (and companion binary) were working correctly, you should have seen one of those "Accept / Deny" pop-up messages coming from the SuperSU app... assuming that you didn't previously grant root access to that terminal emulator app. You didn't mention that happening.... ?
Also, usually the command prompt usually changes from $ to # when you have root, but not always; the explicit way to check would be to (after you have tried the "su" command) to type in "id" and hit return at the prompt - that will tell you explicitly if you are root or not. (That's the letter "i" followed by the letter "d" followed by the return key).
From the way you describe this, it is sounding like you lost root.
I gotta go watch part of the game. In the meantime, perhaps you should at least create a backup manually.
As I said, the simplest fix-up would be to get Superuser.apk/su or SuperSU/su re-installed into /system/app and /system/{x}bin/su (it seems that chainsDD and chainfire use different locations).
There might be floating around someplace a flashable zip file with this stuff in it - to be used for "lightly rooting" a stock ROM after a custom recovery is in place. But things have been in flux recently with both the SuperSU (chainfire) and Superuser (chainsDD) kits because of the JellyBean multi-user support, so the version you might need is important. So you would have to do the research to figure out where.
gotta go - good luck.

bftb0 said:
If the SuperSU app (and companion binary) were working correctly, you should have seen one of those "Accept / Deny" pop-up messages coming from the SuperSU app... assuming that you didn't previously grant root access to that terminal emulator app. You didn't mention that happening.... ?
Also, usually the command prompt usually changes from $ to # when you have root, but not always; the explicit way to check would be to (after you have tried the "su" command) to type in "id" and hit return at the prompt - that will tell you explicitly if you are root or not. (That's the letter "i" followed by the letter "d" followed by the return key).
From the way you describe this, it is sounding like you lost root.
I gotta go watch part of the game. In the meantime, perhaps you should at least create a backup manually.
As I said, the simplest fix-up would be to get Superuser.apk/su or SuperSU/su re-installed into /system/app and /system/{x}bin/su (it seems that chainsDD and chainfire use different locations).
There might be floating around someplace a flashable zip file with this stuff in it - to be used for "lightly rooting" a stock ROM after a custom recovery is in place. But things have been in flux recently with both the SuperSU (chainfire) and Superuser (chainsDD) kits because of the JellyBean multi-user support, so the version you might need is important. So you would have to do the research to figure out where.
gotta go - good luck.
Click to expand...
Click to collapse
Thanks again.
Im watching Superbowl as well. I didnt grant Terminal access. I rebooted into recovery and restored to right after I rooted. SuperSu auto updated through the play store, and stated the binary need updated. I canceled that. TB and ROM manager are showing up in SuperSu. So now Im rebooting into recovery again to after I installed the Smooth Rom/Motley Kernal. I did make a backup of where SuperSu lost root. I now have three backups.
Question on installing the SuperSu apk file. I want to be sure I do it right, if needed. Download the file on my 7. it will go to my download folder. Move it to the system folder and open/run it? what do i do with the current SuperSu folder?
thanks again

I went to my restore point after root and reinstalled 4.3 Smooth ROM Mkernel. I did not take the SuperSu update, (ill wait for the next update) and everything is fine TB an ROM manager working fine, did a backup in both.
Thanks for your help on this.

cam75 said:
Question on installing the SuperSu apk file. I want to be sure I do it right, if needed. Download the file on my 7. it will go to my download folder. Move it to the system folder and open/run it? what do i do with the current SuperSu folder?
Click to expand...
Click to collapse
Dealing with .apk's is not that difficult - drop them into the correct place and reboot.
In Android, apps (.apk files) are stored in one of two places: /system/app or /data/app. It is even possible for two versions of an app to be on the phone - one in /system/app and one in /data/app; that is how upgrades of factory-installed apps happen: the pre-installed app is in /system/app... and never gets deleted (read-only filesystem), whereas update versions get dropped into /data/app. Generally you can just drop an .apk file into either of these locations, wipe the dalvik cache and reboot. During the android boot, these files are compiled into .dex objects in the dalvik-cache, and various version, consistency, rights and permissions are cross-checked.
Think of it this way: when you boot a new ROM for the first time, /data starts out completely empty. Everything needed to support each pre-installed app in /system/app gets created automatically during the android layer start-up.
The "su" native binary is a bit more complicated - it needs to be:
- owned by the user.group root.root
- be executable
- be setuid/setgid
Imagine that you had a copy of these two files on your "/sdcard". If you booted into the custom recovery, you could affect these changes like this:
C:\foo> adb shell
# mount # show what is already mounted
# mount /sdcard # if needed
# mount /system # if needed
# mv /system/app/SuperSU.apk /system/app/SuperSU.apk.old
# cp /sdcard/SuperSU.apk /system/app/SuperSU.apk
# mv /system/xbin/su /system/xbin/su.old
# cp /sdcard/su /system/xbin/su
# chown root.root /system/xbin/su
# chmod 6755 /system/xbin/su
# cd /
# umount /system
# exit
C:\foo>
*
As a practical matter, it is probably easier to just make sure to make a fresh backup if you are about to update the su binary - in case anything goes wrong. It might also be useful to use a root-aware file manager to remount the /system partition in rw mode prior to doing the "update su binary" procedure in the SuperSU app.
Good luck
* note that SuperSU and Superuser apps choose different locations for the su executable file - one uses /system/bin/su and the other /system/xbin/su. There might also be a symlink between these locations. Best policy is probably to examine a known-working installation to determine how to proceed.

lost all permissions after messing with platform.xml

Hello,
I have SM-N9005 variant and recently I updated to the latest android 4.4.2 leaked version with Odin, and then rooted with CF-Auto-Root.
After that, I lost the permission to write to external sdcard.
I searched and found this: http://forum.xda-developers.com/showthread.php?p=49603814
I backed up /system/etc/permissions/platform.xml and then I followed the instructions there.
After restart, a lot of app stopping messages showed and I had no access to file system or network anymore.
I used adb shell to restore the original platform.xml but it didn't helped in any way.
It seems that all mounts and networks are working, but none of the applications has permission to use any of them.
How do I resolve this, without wiping all my data?
Thank you!

You need to set the correct permissions on the .xml after you overwrite it back into the /system Off the top of my head I can't think what they are (just out of bed and got to work so still sleepy!)

radicalisto said:
You need to set the correct permissions on the .xml after you overwrite it back into the /system Off the top of my head I can't think what they are (just out of bed and got to work so still sleepy!)
Click to expand...
Click to collapse
I tried 644 and 777 but the problem persists.

rw-r-r which is 644 - read wrong
or chmod 666 -- forgive my lack of memory, it has been a long time since I have used chmod commands, few years since my glFTPD / site modding days.

radicalisto said:
rw-r-r which is 644 - read wrong
or chmod 666 -- forgive my lack of memory, it has been a long time since I have used chmod commands, few years since my glFTPD / site modding days.
Click to expand...
Click to collapse
The problem still persist

DxCK said:
The problem still persist
Click to expand...
Click to collapse
i dont know if it helps in your situation but did you try the "fix permissions" from a custom recovery like twrp?
there are also scripts you can execute in a terminal, the knoxout script linked in my sig for example has a permission fixer included.

A.N.Droid said:
i dont know if it helps in your situation but did you try the "fix permissions" from a custom recovery like twrp?
there are also scripts you can execute in a terminal, the knoxout script linked in my sig for example has a permission fixer included.
Click to expand...
Click to collapse
Thank you.
When i run this, no matter what are the parameters, for example: sh kn0x0ut.sh kn0x0ut
it says:
ERROR: Unknown parameter ""
Removing all temp folder /data/media/kn0x0ut_temp...

DxCK said:
Thank you.
When i run this, no matter what are the parameters, for example: sh kn0x0ut.sh kn0x0ut
it says:
ERROR: Unknown parameter ""
Removing all temp folder /data/media/kn0x0ut_temp...
Click to expand...
Click to collapse
just type sh kn0x0ut.sh to get all commands.
if you dont get this working, you can do it from twrp (i think cwm too)if you have it.
tap on "advanced" and then on "fix permissions".

[Q] build.prop edits for 803

I'm trying to edit the build.prop file on the G2 803 model. It's rooted and unlocked on a stock Bell Rom. The phone has the wi-fi forgetting problem. everytime I reboot it I have to reset the wifi password. I've tried editing the build.prop file to change the wifi.lge.patch line to=false but I can't seem to enter more than 4 characters after the = on that line. Am I missing something?

Use build prop editor free on playstore
_____________________________________Read more write less and be smart

siggey said:
Use build prop editor free on playstore
_____________________________________Read more write less and be smart
Click to expand...
Click to collapse
Thanks, I tried that but the changes don't appear to stick.

Fraggle_Shamy said:
Thanks, I tried that but the changes don't appear to stick.
Click to expand...
Click to collapse
Reason 1: Some build.prop values get their values from the ramdisk on each boot, so that's why some values wont stick.
Reason 2 (requires root): build.prop is located in /system. Your /system may be read-only, we want it to be read-write to make changes, so.. run the following command in a Terminal Emulator downloaded from the play store. Run the following commands,
Code:
su
mount -o rw,remount /system
Now make your build.prop changes. Once finished run the following command to get your system back to how it was,
Code:
mount -o ro,remount /system
If the app isnt helping you, download a file explorer such as ES and navigate to /system/build.prop, open the file and edit the values you want.
Note: It's nice to hit the "Thanks" button under our posts if you indeed are thankful. Saying thanks and not hitting the thanks button is a slap in the face .

Thanks for the suggestion, but the emulator didn't help. I'm guessing it's because it's locked to the boot rom (your first suggestion)? Any way around this? I have anohter 803 that doesn't have this issue. Can I copy the ROM from that phone to the problematic one?

Fraggle_Shamy said:
Thanks for the suggestion, but the emulator didn't help. I'm guessing it's because it's locked to the boot rom (your first suggestion)? Any way around this? I have anohter 803 that doesn't have this issue. Can I copy the ROM from that phone to the problematic one?
Click to expand...
Click to collapse
Try this. (Pretty much the same as a previous suggestion, doubt it will work)
Get a root capable browser. Jrummy has one that's free, I think it's called Root Browser.
Browse to /system there should be a button to mount it r/w, if not it may prompt you when you go to edit the file... Long click the file, and try to open for editing. (it may be some other combination, I don't have my phone handy right now). Make the a change or two, reboot and see if they stick.
Or the other thing you cna do is:
The other thing you can try is to do is check if they're being set on boot.
adb pull /*.rc
which will pull all of the ramdisk's initialization scripts into your current folder on your computer. Look through them and see if the values are indeed being set by the boot image. If they are, you'll need something like AIK (android image kitchen) to extract the ramdisk, either change or delete those lines, rebuild the boot.img and flash it (using flashify or manually using adb and dd). You have to rebuild them into the boot.img, any changes you make to them directly on the phone will never stay as they get re-created every boot. It's a pretty roundabout way to do it, but it's entirely possible to do.
A much easier, and less likely to cause you issues would simply be to create an init.d script that sets it. This will occur after whatever is setting it in your boot.img so there would be no need to recreate that.
create a file in /etc/init.d called something like... "Set_wifi_pass" set the permissions so that it can be executed and read by everyone.
Then enter the following:
Code:
[B][I]#!/system/bin/sh[/I][/B]
setprop wifi.lge.patch = WifiPassword
You can check that it worked by going through adb shell with
adb shell
getprop wifi.lge.patch
which should return that value you set. Same thing that build.prop is ultimately doing, just in a different way.
Hope that helps.

MAKING SYSTEM WRITABLE - [Z5] [Nougat] AFTER ROOT

after ROOTING Nougat 32.3.A.0.376 (E6833 E6853 E6883) (E6633 E6653 E6683 ), we will still face ERROR while removing system apps, because GOOGLE has changed file system properties in Android N to READ ONLY
in order to make system directory WRITABLE, install busybox, and terminal,
type these lines and enter one by one in #terminal
Code:
su
mount -o rw,remount /system
ORRR
Code:
su
busybox mount -o rw,remount,rw /system
-----------

What???

Why ??? I still can not write anything on the SYSTEM partition
I have full ROOT access and everything , no reboot or error issue !!
Please share if you find any solution to that

chinmoy32 said:
Why ??? I still can not write anything on the SYSTEM partition
I have full ROOT access and everything , no reboot or error issue !!
Please share if you find any solution to that
Click to expand...
Click to collapse
Mee too unable to write on system

download terminal on google play
open terminal
write "su" command and give root permission
then you will see "#"
after that, write this command:
Code:
echo 0 > /sys/kernel/security/sony_ric/enable
then you write this command:
Code:
mount -o rw,remount /system
if you see "#" again, it worked
but if you see "mount: Operation not permitted" it has not, sorry
Credits: https://forum.xda-developers.com/showpost.php?p=70677335&postcount=92

I did what @serajr described here:
https://forum.xda-developers.com/xp...-kernel-dm-t3301605/post70595975#post70595975
works like a charm, system always writable!

Can any of you share here your perfectly rooted working kernel for Z5 E6683 DSDS ????

chinmoy32 said:
Why ??? I still can not write anything on the SYSTEM partition
I have full ROOT access and everything , no reboot or error issue !!
Please share if you find any solution to that
Click to expand...
Click to collapse
i found a workaround and it goes
installing busybox
installing terminal
and writing following codes
Code:
su
'to give terminal root access
busybox mount -o rw,remount /system
later using ROOT APP REMOVER i manage to remove all bloatware!

toncheee said:
I did what @serajr described here:
https://forum.xda-developers.com/xp...-kernel-dm-t3301605/post70595975#post70595975
works like a charm, system always writable!
Click to expand...
Click to collapse
@serajr workaround was fo when rootkernel4.51 wasn't able to support Nougat kernel
however if you follow carefully, the lines mentioned
Code:
on post-fs
export LD_PRELOAD libNimsWrap.so:libdrmfix.so
and
Code:
write /sys/kernel/security/sony_ric/enable 0
will switchoff SONYRIC and will fix DRM
the issue is NOT sony RIC,
Google in general with or without any security/rootaccess changed the system folder properties from default Writable in <+ 6.01 Android version to READABLE ONLY from android 7.xx
so when i followed the both method of altering file via notepad++ in the ramdisk folder using N kernel and rootkernel version4.5, I ended up having fully root system with READLY ONLY ACCESS to /system partition and i could only switchoff the apps but can't remove!

YasuHamed said:
@serajr workaround was fo when rootkernel4.51 wasn't able to support Nougat kernel
however if you follow carefully, the lines mentioned
Code:
on post-fs
export LD_PRELOAD libNimsWrap.so:libdrmfix.so
and
Code:
write /sys/kernel/security/sony_ric/enable 0
will switchoff SONYRIC and will fix DRM
the issue is NOT sony RIC,
Google in general with or without any security/rootaccess changed the system folder properties from default Writable in <+ 6.01 Android version to READABLE ONLY from android 7.xx
so when i followed the both method of altering file via notepad++ in the ramdisk folder using N kernel and rootkernel version4.5, I ended up having fully root system with READLY ONLY ACCESS to /system partition and i could only switchoff the apps but can't remove!
Click to expand...
Click to collapse
I also think the issue is not the RIC but something to do with the Nougat filesystem itself.
I can delete all the files and folders with any file managers I like but like after 1 sec they all reappear as nothing ever happened to them !!!
How strange is that ??
It shows file sizes when I delete them and take times to delete the folders with , say for 500MB
but they still reappear after just 1 refresh or 1 sec.
I cant figure it out at all for the sake of my sanity --- why the hell this is happening ????

https://www.dropbox.com/sh/2kf8wg3g13pv869/AACB3l8iPJHJnBlpnGorRqrha?dl=0
@bungadudu @chinmoy32
I followed bungadudu-s steps and it worked i can change permissions and prove it with link i provided.
And chenges, yes they stick after reboot and i can rename files allso, but:
after reboot i have to repeat this steps if i want to change something elsewhere, old changes do stick aroind though
I deletet phone to 0 mb in twrp, flashed AU nougat .372 with flashtool, rebooted into twrp, flashed zip file provided in link, then flashed supersu in link and rebooted, no custom kernel used
Next i will try to copy modified thermal files now and see if they stick after reboot and if kernel aduitor uses them, see you later
Observations:
-i changed permissions from file /system/build.prop and changed lcd density to 320 and i have bootloop
working on how to boot it up...

YasuHamed said:
after ROOTING Nougat 32.3.A.0.372 (e6833 e6853 e6883) (E6633 E6653 E6683 ), we will still face ERROR because GOOGLE has changed file system properties in Android N to READ ONLY
in order to make system directory WRITABLE, install busybox, and terminal,
type these lines and enter one by one in terminal
Code:
su
busybox mount -o rw,remount /system
-----------
Click to expand...
Click to collapse
Please share the exact name / way to install busybox and terminal
i.e. which version of busybox I need to install from where ?? Which terminal app you used ?? if possible please share the links

https://www.dropbox.com/s/d9ie598b618feiz/recovery.log?dl=0
i managed to get somesort of log from twrp in link from previous post will this sufice?
i am reflashing my phone so i can not look at versions, for now i used:
when i reboot it i can look into busybox version
SR3-SuperSU-v2.79-SR3-20170114223742, on top of that i installed pro:
https://play.google.com/store/apps/details?id=eu.chainfire.supersu.pro
busyboxpro
https://play.google.com/store/apps/details?id=stericson.busybox.donate
terminal from romtoolbox pro:
https://play.google.com/store/apps/details?id=com.jrummy.liberty.toolboxpro
those are some apps i support so i dot know if it makes a diference from non paid
chinmoy32 said:
Please share the exact name / way to install busybox and terminal
i.e. which version of busybox I need to install from where ?? Which terminal app you used ?? if possible please share the links
Click to expand...
Click to collapse

chinmoy32 said:
Please share the exact name / way to install busybox and terminal
i.e. which version of busybox I need to install from where ?? Which terminal app you used ?? if possible please share the links
Click to expand...
Click to collapse
I install both of them via play.google.com
https://play.google.com/store/apps/details?id=stericson.busybox&hl=en
&
https://play.google.com/store/apps/details?id=jackpal.androidterm&hl=en
later i opened terminal and ran those commands
later i installed System App remover
https://play.google.com/store/apps/details?id=com.jumobile.manager.systemapp&hl=en
granted it SU rights and removed HANGOUTS and GOOGLE MOVIES etc

It seems to work to some extend but if you want to go tweak it up, kablaaam
i did not managed to boot it up after bootloop sadly, i need my phone so this is it for me this week

stipi69 said:
https://www.dropbox.com/s/d9ie598b618feiz/recovery.log?dl=0
i managed to get somesort of log from twrp in link from previous post will this sufice?
i am reflashing my phone so i can not look at versions, for now i used:
when i reboot it i can look into busybox version
SR3-SuperSU-v2.79-SR3-20170114223742, on top of that i installed pro:
https://play.google.com/store/apps/details?id=eu.chainfire.supersu.pro
busyboxpro
https://play.google.com/store/apps/details?id=stericson.busybox.donate
terminal from romtoolbox pro:
https://play.google.com/store/apps/details?id=com.jrummy.liberty.toolboxpro
those are some apps i support so i dot know if it makes a diference from non paid
Click to expand...
Click to collapse
I just clean install 372 and patched the kernel once again .................
tried the terminal commands ---- both commands were successful (without any errors )
but still the deleted apps and the edited files came back to normal as before

I did not manage to delete anny apps as my phone crashed before, i am glad you get commands to work.
oh, by the waj roomtoolbox is great as you can make shortcuts of the commands and then you klik it one after another and you get rid of the typing
example (first shortcut command depends of busybox install folder i think)
1.st shortcut "cd /su"
2.nd shortcut "su"
3.rd shortcut "echo 0 > /sys/kernel/security/sony_ric/enable"
4.th shortcut "mount -o rw,remount /system"
that way some people can do this quick and you dont need to remember commands, and you can experiment quicker.
sorry i dont know howto annything else for now
chinmoy32 said:
I just clean install 372 and patched the kernel once again .................
tried the terminal commands ---- both commands were successful (without any errors )
but still the deleted apps and the edited files came back to normal as before
Click to expand...
Click to collapse

stipi69 said:
I did not manage to delete anny apps as my phone crashed before, i am glad you get commands to work.
oh, by the waj roomtoolbox is great as you can make shortcuts of the commands and then you klik it one after another and you get rid of the typing
example (first shortcut command depends of busybox install folder i think)
1.st shortcut "md /su"
2.nd shortcut "su"
3.rd shortcut "echo 0 > /sys/kernel/security/sony_ric/enable"
4.th shortcut "mount -o rw,remount /system"
that way some people can do this quick and you dont need to remember commands, and you can experiment quicker.
sorry i dont know howto annything else for now
Click to expand...
Click to collapse
I just managed to restart my phone successfully after changing the LCD density to 320 [I also use this value since always ]
But then I carefully just deleted 1 single app and booom--- boot loop
PS. i used root explorer to just click mount as R/W and then do anything to system partition --

Great you magaged it, and yes 320 seems so right.
And i asume there is no way to break bootloop?...other than reflashing?
I had trouble afterwards on downgrading to.253, 3x times error on start, even after reseting " power & + " and couple of full wipes in twrp.
I had to flash lineage from twrp and boot it up and only then flashtool succeeded pushing. 253.
This nougat will be fun i see
If there is something to try tell me i will flash it once more tonight, otherways i can do it on weekends
Oh i did not tell, i managed to copy modified thermal files with no error and then changed lcd density so i can not 100% tell which caused bootlop, since i did not reboot in between...

chinmoy32 said:
I just clean install 372 and patched the kernel once again .................
tried the terminal commands ---- both commands were successful (without any errors )
but still the deleted apps and the edited files came back to normal as before
Click to expand...
Click to collapse
there is another way which i did not try because the busybox commands worked for me
its about flashsing updater script
delete_recursive(
"/system/app/GoogleAnalyticsProxy",
"/system/priv-app/GoogleBackupTransport",
"/system/priv-app/textinput-chn-xxhdpi",
);
https://forum.xda-developers.com/showpost.php?p=70920831&postcount=2015