Hi,
Finally I can enter recovery mode after messing up with build.prop on Xperia Tablet S
tablet is visible in ADB as
C:\Users\Amiga\Desktop\adb>adb devices
List of devices attached
0123456789ABCDEF recovery
but rest of the commands doesn't work
C:\Users\Amiga\Desktop\adb>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: closed
So I don't know how to pull out build.prop from Tablet
Amiga4ever123 said:
Hi,
Finally I can enter recovery mode after messing up with build.prop on Xperia Tablet S
tablet is visible in ADB as
C:\Users\Amiga\Desktop\adb>adb devices
List of devices attached
0123456789ABCDEF recovery
but rest of the commands doesn't work
C:\Users\Amiga\Desktop\adb>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: closed
So I don't know how to pull out build.prop from Tablet
Click to expand...
Click to collapse
The reason you are getting the "error: closed" message is because the version of System Recovery installed on your tablet inhibits ADB from accessing the tablet's file system. You are not going to be able to pull or push the build.prop file.
Ok I can't use ADb so how can I replace faulty build.prop file or make recovery? Any ZIP file that I can put on SD card?
Amiga4ever123 said:
Ok I can't use ADb so how can I replace faulty build.prop file or make recovery? Any ZIP file that I can put on SD card?
Click to expand...
Click to collapse
You can try copying an OTA update file to an SD card and using System Recovery to install it, but I do not believe doing that will work. I believe you have bricked your tablet to the point where you have to send your tablet to Sony for repair.
Cat McGowan said:
You can try copying an OTA update file to an SD card and using System Recovery to install it, but I do not believe doing that will work. I believe you have bricked your tablet to the point where you have to send your tablet to Sony for repair.
Click to expand...
Click to collapse
So its very easy to brick this amazing sony device
Cat McGowan said:
The reason you are getting the "error: closed" message is because the version of System Recovery installed on your tablet inhibits ADB from accessing the tablet's file system. You are not going to be able to pull or push the build.prop file.
Click to expand...
Click to collapse
Hi cat tried to PM you but can?t do it...
Can you teach me how to copy/restore (pull and or push) the original build.prop in my cell (now bricked) i had the original file (buil.prop) inside it... i am learning about adb commands. thanksss. The main problem I have: An issue with ADB VCOM drivers (in windows) (tried in a couple of PCS, the device manager "see" the vcom preloader only a little moment (when connect the cell with usb cable) and then dissapear... then with command adb devices: no devices found... can you help me?
federimau said:
Hi cat tried to PM you but can?t do it...
Can you teach me how to copy/restore (pull and or push) the original build.prop in my cell (now bricked) i had the original file (buil.prop) inside it... i am learning about adb commands. thanksss. The main problem I have: An issue with ADB VCOM drivers (in windows) (tried in a couple of PCS, the device manager "see" the vcom preloader only a little moment (when connect the cell with usb cable) and then dissapear... then with command adb devices: no devices found... can you help me?
Click to expand...
Click to collapse
The reason ADB is reporting no devices are found may be because (1) your device is bricked, which probably means you are not going to be able to pull/push files from/to your device, (2) you do not have ADB drivers for your device properly installed on your PC, and/or (3) you do not have USB debugging enabled in your tablet's Developer options settings.
It's good you are learning how to use ADB and there are plenty of ADB tutorials to be found via Google, etc.; e.g., HERE.
Here is what you specifically ask for.
Pulling the build.prop file from your tablet to your PC is easy, just use these commands.
Code:
adb wait-for-device
adb pull /system/build.prop
adb kill-server
Pushing the build.prop file from your PC to your tablet is more complicated.
(1) Your tablet must have root access. If it doesn't, attempts at pushing the file to your tablet's /system directory will fail.
(2) Along with having root access, you must have SuperSU or Superuser, and Busybox installed on the tablet.
(3) You have to temporarily set your tablet's /system directory's properties from RO to RW, which must be done quickly because your tablet's OS monitors the /system directory's properties and will reboot the tablet if it detects the directory's properties have been changed from RO.
(4) To issue the ADB commands as quickly as possible, the commands must be put into a DOS batch command script file. For example, create and run a batch file named doit.bat containing the following commands.
Code:
adb wait-for-device
adb push build.prop /build.prop
adb shell "su -c 'stop ric'"
adb shell "su -c 'busybox pkill -f /sbin/ric'"
adb shell "su -c 'mount -ro remount,rw /'"
adb shell "su -c 'chmod 0440 /sbin/ric'"
adb shell "su -c 'stop ric'"
adb shell "su -c 'busybox pkill -f /sbin/ric'"
adb shell "su -c 'mount -ro remount,rw /system'"
adb shell "su -c 'busybox cp -af /build.prop /system/build.prop'"
adb shell "su -c 'chmod 0744 /system/build.prop'"
adb shell "su -c 'rm /build.prop'"
adb shell "exit"
adb kill-server
Good luck.
Cat McGowan said:
The reason ADB is reporting no devices are found may be because (1) your device is bricked, which probably means you are not going to be able to pull/push files from/to your device, (2) you do not have ADB drivers for your device properly installed on your PC, and/or (3) you do not have USB debugging enabled in your tablet's Developer options settings.
It's good you are learning how to use ADB and there are plenty of ADB tutorials to be found via Google, etc.; e.g., HERE.
Here is what you specifically ask for.
Pulling the build.prop file from your tablet to your PC is easy, just use these commands.
Code:
adb wait-for-device
adb pull /system/build.prop
adb kill-server
Pushing the build.prop file from your PC to your tablet is more complicated.
(1) Your tablet must have root access. If it doesn't, attempts at pushing the file to your tablet's /system directory will fail.
(2) Along with having root access, you must have SuperSU or Superuser, and Busybox installed on the tablet.
(3) You have to temporarily set your tablet's /system directory's properties from RO to RW, which must be done quickly because your tablet's OS monitors the /system directory's properties and will reboot the tablet if it detects the directory's properties have been changed from RO.
(4) To issue the ADB commands as quickly as possible, the commands must be put into a DOS batch command script file. For example, create and run a batch file named doit.bat containing the following commands.
Code:
adb wait-for-device
adb push build.prop /build.prop
adb shell "su -c 'stop ric'"
adb shell "su -c 'busybox pkill -f /sbin/ric'"
adb shell "su -c 'mount -ro remount,rw /'"
adb shell "su -c 'chmod 0440 /sbin/ric'"
adb shell "su -c 'stop ric'"
adb shell "su -c 'busybox pkill -f /sbin/ric'"
adb shell "su -c 'mount -ro remount,rw /system'"
adb shell "su -c 'busybox cp -af /build.prop /system/build.prop'"
adb shell "su -c 'chmod 0744 /system/build.prop'"
adb shell "su -c 'rm /build.prop'"
adb shell "exit"
adb kill-server
Good luck.
Click to expand...
Click to collapse
Wowww Cat, you are the one!! Thanks in Advance
The main problem I have: An issue with device recognition in windows PC... driver ADB VCOM MTK 6592 (tried in different PCS windows Xp and 8) (the device manager "see" the vcom preloader but only a little moment (in the first instant when connect the cell (cell off) with usb cable) and then dissapear (disconnect) the vcom preloader... I think If I can reach the way to get this connection running ok I can progress with this... will fight hard...
When I type the command adb devices, result: no devices found...
Tried to upgrade the vcom drivers (when i can catch it in the active state in device manager)... nothing
Tried to "on" the phone... nothing
Tried to flash a new ROM from Recovery (MIUI or Feelingme 078)... ERROR installation aborted
I can see this effect (with usbview): the usb is recognized in the PC (but just for a little moment at the instant when plug it), then disconnect...
I need to recover the original build.prop.bak from coolpad memory, rename it to build.prop and send it to coolpad again...
I think i can flash (from recovery) an original build. prop (packed as update.zip) doing the wipes and apply update from sdcard)... anyone can assist me on this?
This new 9976A item comes to me with 048 version, custom buid version 265 and rooted from factory...
Anyone can please help me?
Cat McGowan said:
The reason ADB is reporting no devices are found may be because (1) your device is bricked, which probably means you are not going to be able to pull/push files from/to your device, (2) you do not have ADB drivers for your device properly installed on your PC, and/or (3) you do not have USB debugging enabled in your tablet's Developer options settings.
It's good you are learning how to use ADB and there are plenty of ADB tutorials to be found via Google, etc.; e.g., HERE.
Here is what you specifically ask for.
Pulling the build.prop file from your tablet to your PC is easy, just use these commands.
Code:
adb wait-for-device
adb pull /system/build.prop
adb kill-server
Pushing the build.prop file from your PC to your tablet is more complicated.
(1) Your tablet must have root access. If it doesn't, attempts at pushing the file to your tablet's /system directory will fail.
(2) Along with having root access, you must have SuperSU or Superuser, and Busybox installed on the tablet.
(3) You have to temporarily set your tablet's /system directory's properties from RO to RW, which must be done quickly because your tablet's OS monitors the /system directory's properties and will reboot the tablet if it detects the directory's properties have been changed from RO.
(4) To issue the ADB commands as quickly as possible, the commands must be put into a DOS batch command script file. For example, create and run a batch file named doit.bat containing the following commands.
Code:
adb wait-for-device
adb push build.prop /build.prop
adb shell "su -c 'stop ric'"
adb shell "su -c 'busybox pkill -f /sbin/ric'"
adb shell "su -c 'mount -ro remount,rw /'"
adb shell "su -c 'chmod 0440 /sbin/ric'"
adb shell "su -c 'stop ric'"
adb shell "su -c 'busybox pkill -f /sbin/ric'"
adb shell "su -c 'mount -ro remount,rw /system'"
adb shell "su -c 'busybox cp -af /build.prop /system/build.prop'"
adb shell "su -c 'chmod 0744 /system/build.prop'"
adb shell "su -c 'rm /build.prop'"
adb shell "exit"
adb kill-server
Good luck.
Click to expand...
Click to collapse
Cat i will need to pull the backup file... then the code i need is... (please monitor it for me)
adb wait-for-device
adb pull /system/build.prop.bak
adb kill-server
and... when you push the correct and original file
adb wait-for-device
adb push build.prop /build.prop
is it ok? or the path is this?
adb push build.prop /system/build.prop
(if there are a build.prop in the device this will overwrite it?
federimau said:
Cat i will need to pull the backup file... then the code i need is... (please monitor it for me)
adb wait-for-device
adb pull /system/build.prop.bak
adb kill-server
and... when you push the correct and original file
adb wait-for-device
adb push build.prop /build.prop
is it ok? or the path is this?
adb push build.prop /system/build.prop
(if there are a build.prop in the device this will overwrite it?
Click to expand...
Click to collapse
adb push build.prop /system/build.prop
Cat McGowan said:
adb push build.prop /system/build.prop
Click to expand...
Click to collapse
Thanks cat, as i say, the main problem in this case is: i have a short window of time when the windows PC see the driver in the device manager... then disconnects... do you have any idea what can i do to establish this connection betweeen the android device and the computer without interruption?
---------- Post added at 05:22 PM ---------- Previous post was at 05:12 PM ----------
Cat McGowan said:
adb push build.prop /system/build.prop
Click to expand...
Click to collapse
cat, i´m doing 2 bat files (edited with notepad, is this correct?)
one file: pull.bat
with code
adb wait-for-device
adb pull /system/build.prop.bak
adb kill-server
another file: push.bat
with code
adb wait-for-device
adb push build.prop /system/build.prop
adb shell "su -c 'stop ric'"
adb shell "su -c 'busybox pkill -f /sbin/ric'"
adb shell "su -c 'mount -ro remount,rw /'"
adb shell "su -c 'chmod 0440 /sbin/ric'"
adb shell "su -c 'stop ric'"
adb shell "su -c 'busybox pkill -f /sbin/ric'"
adb shell "su -c 'mount -ro remount,rw /system'"
adb shell "su -c 'busybox cp -af /build.prop /system/build.prop'"
adb shell "su -c 'chmod 0744 /system/build.prop'"
adb shell "su -c 'rm /build.prop'"
adb shell "exit"
adb kill-server
what do you think?
---------- Post added at 05:51 PM ---------- Previous post was at 05:22 PM ----------
federimau said:
Thanks cat, as i say, the main problem in this case is: i have a short window of time when the windows PC see the driver in the device manager... then disconnects... do you have any idea what can i do to establish this connection betweeen the android device and the computer without interruption?
---------- Post added at 05:22 PM ---------- Previous post was at 05:12 PM ----------
cat, i´m doing 2 bat files (edited with notepad, is this correct?)
one file: pull.bat
with code
adb wait-for-device
adb pull /system/build.prop.bak
adb kill-server
another file: push.bat
with code
adb wait-for-device
adb push build.prop /system/build.prop
adb shell "su -c 'stop ric'"
adb shell "su -c 'busybox pkill -f /sbin/ric'"
adb shell "su -c 'mount -ro remount,rw /'"
adb shell "su -c 'chmod 0440 /sbin/ric'"
adb shell "su -c 'stop ric'"
adb shell "su -c 'busybox pkill -f /sbin/ric'"
adb shell "su -c 'mount -ro remount,rw /system'"
adb shell "su -c 'busybox cp -af /build.prop /system/build.prop'"
adb shell "su -c 'chmod 0744 /system/build.prop'"
adb shell "su -c 'rm /build.prop'"
adb shell "exit"
adb kill-server
what do you think?
Click to expand...
Click to collapse
I think need to remove the first line?
adb wait-for-device
federimau said:
Thanks cat, as i say, the main problem in this case is: i have a short window of time when the windows PC see the driver in the device manager... then disconnects... do you have any idea what can i do to establish this connection betweeen the android device and the computer without interruption?
Click to expand...
Click to collapse
You need to solve that problem before you can do anything else. Find an xda-developers forum that deals with your device and look there for fixes for your device's drivers. I am confident I can help you with Sony tablet drivers, but not your device's drivers. I don't even know the model of your device.
Create and use the following CheckDriver.bat file to help you troubleshoot the drivers. The script simply opens a DOS command window, starts the adb server, then lists the devices the adb server finds. The DOS command window will stay open until you press any key. If the script hangs, press ctrl+c to abort the script and close the DOS command window, then open another DOS command window and issue the "adb kill-server" command to stop the adb server.
Code:
@echo off
echo Starting ADB server and waiting for device.
echo.
adb wait-for-device
adb devices
pause
adb kill-server
federimau said:
cat, i´m doing 2 bat files (edited with notepad, is this correct?)
one file: pull.bat
with code
adb wait-for-device
adb pull /system/build.prop.bak
adb kill-server
another file: push.bat
with code
adb wait-for-device
adb push build.prop /system/build.prop
adb shell "su -c 'stop ric'"
adb shell "su -c 'busybox pkill -f /sbin/ric'"
adb shell "su -c 'mount -ro remount,rw /'"
adb shell "su -c 'chmod 0440 /sbin/ric'"
adb shell "su -c 'stop ric'"
adb shell "su -c 'busybox pkill -f /sbin/ric'"
adb shell "su -c 'mount -ro remount,rw /system'"
adb shell "su -c 'busybox cp -af /build.prop /system/build.prop'"
adb shell "su -c 'chmod 0744 /system/build.prop'"
adb shell "su -c 'rm /build.prop'"
adb shell "exit"
adb kill-server
what do you think?
Click to expand...
Click to collapse
Looks okay. Just keep in mind that the scripts are based on what is required for Sony tablets. Your device may require something a little different.
federimau said:
I think need to remove the first line?
adb wait-for-device
Click to expand...
Click to collapse
No. The "adb wait-for-device" command is what starts the adb server and causes the script to wait until the adb server detects a device before the next command in the script is issued.
Similar to the CheckDevice.bat file, you can insert the "@echo off" command at the beginning of your .bat files and the "pause" command just before the "adb kill-server" to cause the DOS command window stay open so you can see what is going on and the DOS command window will stay open until you press any key. Again, if the script hangs, press ctrl+c to abort the script and close the DOS command window, then open another DOS command window and issue the "adb kill-server" command to stop the adb server.
Cat McGowan said:
You need to solve that problem before you can do anything else. Find an xda-developers forum that deals with your device and look there for fixes for your device's drivers. I am confident I can help you with Sony tablet drivers, but not your device's drivers. I don't even know the model of your device.
Create and use the following CheckDriver.bat file to help you troubleshoot the drivers. The script simply opens a DOS command window, starts the adb server, then lists the devices the adb server finds. The DOS command window will stay open until you press any key. If the script hangs, press ctrl+c to abort the script and close the DOS command window, then open another DOS command window and issue the "adb kill-server" command to stop the adb server.
Code:
@echo off
echo Starting ADB server and waiting for device.
echo.
adb wait-for-device
adb devices
pause
adb kill-server
Looks okay. Just keep in mind that the scripts are based on what is required for Sony tablets. Your device may require something a little different.
No. The "adb wait-for-device" command is what starts the adb server and causes the script to wait until the adb server detects a device before the next command in the script is issued.
Similar to the CheckDevice.bat file, you can insert the "@echo off" command at the beginning of your .bat files and the "pause" command just before the "adb kill-server" to cause the DOS command window stay open so you can see what is going on and the DOS command window will stay open until you press any key. Again, if the script hangs, press ctrl+c to abort the script and close the DOS command window, then open another DOS command window and issue the "adb kill-server" command to stop the adb server.
Click to expand...
Click to collapse
I am working with all of you advices... i owe you a drink (if you agree!!!) Thanks
Cat McGowan said:
You need to solve that problem before you can do anything else. Find an xda-developers forum that deals with your device and look there for fixes for your device's drivers. I am confident I can help you with Sony tablet drivers, but not your device's drivers. I don't even know the model of your device.
Create and use the following CheckDriver.bat file to help you troubleshoot the drivers. The script simply opens a DOS command window, starts the adb server, then lists the devices the adb server finds. The DOS command window will stay open until you press any key. If the script hangs, press ctrl+c to abort the script and close the DOS command window, then open another DOS command window and issue the "adb kill-server" command to stop the adb server.
Code:
@echo off
echo Starting ADB server and waiting for device.
echo.
adb wait-for-device
adb devices
pause
adb kill-server
Looks okay. Just keep in mind that the scripts are based on what is required for Sony tablets. Your device may require something a little different.
No. The "adb wait-for-device" command is what starts the adb server and causes the script to wait until the adb server detects a device before the next command in the script is issued.
Similar to the CheckDevice.bat file, you can insert the "@echo off" command at the beginning of your .bat files and the "pause" command just before the "adb kill-server" to cause the DOS command window stay open so you can see what is going on and the DOS command window will stay open until you press any key. Again, if the script hangs, press ctrl+c to abort the script and close the DOS command window, then open another DOS command window and issue the "adb kill-server" command to stop the adb server.
Click to expand...
Click to collapse
Cat, i can not establish a stable and in-time connection between cell and PC...
type
adb wait-for-device
and never "see" the cell
i have the drivers upgraded
with usbview software i see the PC "see" the cell a short amount of time, then disconnects...
any advice??
federimau said:
Cat, i can not establish a stable and in-time connection between cell and PC...
type
adb wait-for-device
and never "see" the cell
i have the drivers upgraded
with usbview software i see the PC "see" the cell a short amount of time, then disconnects...
any advice??
Click to expand...
Click to collapse
Sounds to me your device simply is not responding to the adb server's attempt to connect. Again, my advice is for you to find an xda-developers forum that deals specifically with your device and look there for fixes for your device.
@Cat McGowan
Thank you for the info,
but it's not working on Recovery mode!
I try to backup and restore the build.prop file on cmd in recovery & in bootloop case.
working:
adb wait-for-device
adb pull /system/build.prop.bak or adb pull /system/build.prop
adb kill-server
not working push to the system: (even the cmd showing the opposite)
adb wait-for-device
adb push build.prop /system/build.prop
adb kill-server
I'm tring to resotre from PC or SD card...
(after changing the permission to system folder (instead only build.prop file) to 00644 the device keep get to Recovery mode! (with root browser app)
only flashing again the rom fix it.)
I got an error too:
- exec '/system/bin/sh' failed: Permission denied (13) -
by the way what Should to be on?
SuperSU or Superuser (ADB shell allow ?)
Developer Mode (Enable ADB ) +USB Debugging on
i'm worng what else?
I want to add some info:
I know the best way to edit this file only by : Notepad++ or EditPlus editor to preserve UNIX encoding
or Turbo Editor ( File Editor ) app.
read here:
http://forum.xda-developers.com/showpost.php?p=54970011&postcount=171
http://forum.xda-developers.com/showpost.php?p=55094822&postcount=203
and great script from user.
http://forum.xda-developers.com/showpost.php?p=55113422&postcount=208
will this work too on recovery or bootloops mode?
backup:
adb shell
su
mount -o remount,rw /system
cp /system/build.prop /system/build.prop.bak
mount -o ro,remount /system/ /system
----
restore:
adb shell
su
mount -o remount,rw /system
cp system/build.prop system/build.prop.bootloop
cp system/build.prop.bak system/build.prop
chmod 00644 system/build.prop
reboot
I just rooted my LG K7 MS 330 recently. And I really am craving to uninstall all the manufacturers' applications. Please, can anyone tell me which ones can be uninstalled and which one MUSTN'T BE uninstalled? Thanks in advance.
Hello, notphongnguyen.
I'm currently running a: LG K7 MS330 as well (latest security patch updates and everything that was updated from stock).
I'm systematically running through eliminating programs / services (daemons) on: User / System level.
When I'm done (possibly by tomorrow): I'll post my findings in the format of APK (application package or "installer") names.
This will allow you to modify your system in various ways (modified ROM file or directly on the phone itself; Just to name 2).
I understand you only have 1 post. I am hoping you subscribed to your thread (e-mail).
This post is also being created to hopefully address future users who find this thread.
Thank you for your patience.
EDIT
Sorry for the delay (in the event you received an e-mail and were patiently waiting for an update)!
It took quite a while to run through all 158 packages that you can successfully disable without causing system-instability or an inoperable system.
I did not document 100% every aspect of every package, but I do believe I found and documented the majority of the alterations caused.
Listed as:
Package path
Package name
[QUOTE='Android Applications you CAN disable', 2017-22-12]/system/priv-app/FontServer/FontServer.apk
com.hy.system.fontserver
/system/priv-app/LGStartupwizard/LGStartupwizard.apk
com.android.LGSetupWizard
/system/app/RootPA/RootPA.apk
com.gd.mobicore.pa
/data/app/com.google.android.youtube-1/base.apk
com.google.android.youtube
/system/app/LGWeatherService/LGWeatherService.apk
com.lge.sizechangable.weather.platform
**** Required for system stability
/system/priv-app/LGTelephonyProvider/LGTelephonyProvider.apk
com.android.providers.telephony
/data/app/com.google.android.googlequicksearchbox-1/base.apk
com.google.android.googlequicksearchbox
/system/app/MyMetro/MyMetro.apk
com.nuance.nmc.sihome.metropcs
/system/priv-app/LGCalendarProvider/LGCalendarProvider.apk
com.android.providers.calendar
/system/priv-app/LGVoiceCommandService/LGVoiceCommandService.apk
com.lge.mtalk.voicecommand
**** Needed by "File Manager"
/system/priv-app/LGMediaProvider/LGMediaProvider.apk
com.android.providers.media
/system/app/EditorsDocs/EditorsDocs.apk
com.google.android.apps.docs.editors.docs
/system/priv-app/LGSystemServer/LGSystemServer.apk
com.lge.systemservice
/system/priv-app/GoogleOneTimeInitializer/GoogleOneTimeInitializer.apk
com.google.android.onetimeinitializer
/system/priv-app/WallpaperCropper/WallpaperCropper.apk
com.android.wallpapercropper
/system/priv-app/CNEService/CNEService.apk
com.quicinc.cne.CNEService
/system/priv-app/LGApplicationManager/LGApplicationManager.apk
com.lge.appbox.client
/system/app/ip-provider/ip-provider.apk
com.movial.ipprovider
/system/priv-app/MetroBlock-It/MetroBlock-It.apk
com.privacystar.android.metro
/system/app/DocumentsUI/DocumentsUI.apk
com.android.documentsui
**** Causes the file manager to behave odd (unable to delete files)
/system/priv-app/LGExternalStorageProvider/LGExternalStorageProvider.apk
com.android.externalstorage
/system/app/LGATCMDService/LGATCMDService.apk
com.lge.android.atservice
/system/app/HTMLViewer/HTMLViewer.apk
com.android.htmlviewer
/system/app/StaProxyService/StaProxyService.apk
com.qualcomm.sta
/system/framework/com.lge.app.floating.res/com.lge.app.floating.res.apk
com.lge.app.floating.res
/system/priv-app/MmsService/MmsService.apk
com.android.mms.service
/data/app/com.google.android.apps.docs.editors.sheets-1/base.apk
com.google.android.apps.docs.editors.sheets
/system/framework/com.lge.sui.widget/com.lge.sui.widget.apk
com.lge.sui.widget
/data/app/com.google.android.apps.docs.editors.slides-1/base.apk
com.google.android.apps.docs.editors.slides
**** Prevents Google Chrome from downloading files / Viewing files from the "Download" icon from the 'app drawer'
/system/priv-app/LGDownloadProvider/LGDownloadProvider.apk
com.android.providers.downloads
/system/priv-app/LGCameraApp/LGCameraApp.apk
com.lge.camera
/system/app/BrowserProviderProxy/BrowserProviderProxy.apk
com.android.browser.provider
/system/app/LGTouchControlAreas/LGTouchControlAreas.apk
com.lge.touchcontrol
/system/app/elt_test/elt_test.apk
com.lge.eltest
/system/priv-app/HomeSelector/HomeSelector.apk
com.lge.homeselector
/system/app/GnssTest/GnssTest.apk
com.lge.gnsstest
/system/app/ConfigUpdater/ConfigUpdater.apk
com.google.android.configupdater
/system/app/WifiCall/WifiCall.apk
com.movial.wificall
**** Used when installing an APK from the Play Store (disable results in a 100% download and error code 501)
/system/priv-app/DefaultContainerService/DefaultContainerService.apk
com.android.defcontainer
/system/priv-app/LGDownloadProviderUi/LGDownloadProviderUi.apk
com.android.providers.downloads.ui
**** Deletes the "Play Store" icon (access entirely?)
/system/priv-app/Phonesky/Phonesky.apk
com.android.vending
/system/app/PacProcessor/PacProcessor.apk
com.android.pacprocessor
/system/app/com.lge.shutdownmonitor/com.lge.shutdownmonitor.apk
com.lge.shutdownmonitor
/system/priv-app/MetroZone/MetroZone.apk
com.mobileposse.client
/system/app/CertInstaller/CertInstaller.apk
com.android.certinstaller
/data/app/com.google.android.marvin.talkback-1/base.apk
com.google.android.marvin.talkback
/system/app/LGHome_Theme_Optimus/LGHome_Theme_Optimus.apk
com.lge.launcher2.theme.optimus
**** Results in "Activity is not exist this device" message to appear when clicking on "Accessibility" button
/system/priv-app/LGSettingsAccessibility/LGSettingsAccessibility.apk
com.android.settingsaccessibility
/system/framework/framework-res.apk
android
/system/app/Upsell/Upsell.apk
com.lge.upsell
**** Removes the "Contacts" and "Phone" icons
/system/priv-app/LGContacts/LGContacts.apk
com.android.contacts
**** Disables "Lock screen" under "Settings" (Activity is not exist this device")
/system/app/LGLockScreenSettings_2/LGLockScreenSettings_2.apk
com.lge.lockscreensettings
/system/priv-app/InCalAgent/InCalAgent.apk
com.lge.ia.task.incalagent
**** Removed "Messaging" icon (no SMS/MMS text application)
/system/priv-app/LGMessage/LGMessage.apk
com.android.mms
/system/app/LGStk/LGStk.apk
com.android.stk
********
/system/priv-app/BackupRestoreConfirmation/BackupRestoreConfirmation.apk
com.android.backupconfirm
/system/priv-app/LGExchange/LGExchange.apk
com.lge.exchange
/system/priv-app/WapService/WapService.apk
com.lge.wapservice
/system/app/LGEasySettings/LGEasySettings.apk
com.lge.settings.easy
/data/app/com.google.android.gm-1/base.apk
com.google.android.gm
**** Disables the "Calender" icon in the 'app drawer'
/system/priv-app/LGCalendar/LGCalendar.apk
com.android.calendar
/system/priv-app/LGMapUI/LGMapUI.apk
com.lge.lgmapui
/system/priv-app/RCSProvider/RCSProvider.apk
com.lge.ims.rcsprovider
/system/priv-app/SetupWizard/SetupWizard.apk
com.google.android.setupwizard
/system/app/qcrilmsgtunnel/qcrilmsgtunnel.apk
com.qualcomm.qcrilmsgtunnel
**** System loops on bootanimation (ADB device remains active / responsive)
/system/priv-app/LGSettingsProvider/LGSettingsProvider.apk
com.android.providers.settings
/system/priv-app/SharedStorageBackup/SharedStorageBackup.apk
com.android.sharedstoragebackup
**** NOTE: "Music" app from the 'app drawer' still launches; Did not test playing an audio file
/system/app/Music2/Music2.apk
com.google.android.music
/system/app/PrintSpooler/PrintSpooler.apk
com.android.printspooler
/system/priv-app/LGInCallUI/LGInCallUI.apk
com.android.incallui
**** NOTE: Name sounds important; Unknown repercussions
/system/app/DriveActivator/DriveActivator.apk
com.lge.drive.activator
/system/app/GnssPosTest/GnssPosTest.apk
com.lge.gnsspostest
/system/priv-app/InputDevices/InputDevices.apk
com.android.inputdevices
/system/priv-app/AdaptClient/AdaptClient.apk
com.tmobile.pr.adapt
/system/app/GBAService/GBAService.apk
com.lge.gba.android
/system/app/UnifiedEULA/UnifiedEULA.apk
com.lge.eula
/system/app/GCUV/GCUV.apk
com.lge.gcuv
**** Causes Google account sync to display "Sync error"; Manually syncing displays "successful sync"
/system/priv-app/LGPCSuite/LGPCSuite.apk
com.lge.sync
/system/priv-app/LGTasksProvider/LGTasksProvider.apk
com.lge.task
/system/app/CloudPrint/CloudPrint.apk
com.google.android.apps.cloudprint
**** Removed 'Google drive' from the 'app drawer'
/system/app/Drive/Drive.apk
com.google.android.apps.docs
**** Removed 'Google maps' from the 'app drawer'
/data/app/com.google.android.apps.maps-1/base.apk
com.google.android.apps.maps
/data/app/com.google.android.webview-1/base.apk
com.google.android.webview
**** Removes the typical "HOME SCREEN" from the Android device ('Home screen theme?'); Displays "Home screen" from Settings/Home screen (can toggle without reboot)
/system/priv-app/LGHome/LGHome.apk
com.lge.launcher2
/system/priv-app/LGTelecom/LGTelecom.apk
com.android.server.telecom
/system/app/GoogleContactsSyncAdapter/GoogleContactsSyncAdapter.apk
com.google.android.syncadapters.contacts
/system/app/FaceLock/FaceLock.apk
com.android.facelock
/system/app/KeyChain/KeyChain.apk
com.android.keychain
**** Removes the 'Chrome browser' from the 'app drawer'
/data/app/com.android.chrome-1/base.apk
com.android.chrome
**** Removes the 'Gallery' from the 'app drawer'
/system/priv-app/LGGallery/LGGallery.apk
com.android.gallery3d
**** Removes the 'Voice command' (blue) from the 'app drawer'
/system/priv-app/LGVoiceCommand/LGVoiceCommand.apk
com.lge.voicecommand
**** Affects Google Play Hangouts ("Google Play Services notice: Update Hangouts") -- GMS = Google-Mail Server/Service(?)
/data/app/com.google.android.gms-1/base.apk
com.google.android.gms
/system/priv-app/GoogleServicesFramework/GoogleServicesFramework.apk
com.google.android.gsf
**** "Text-to-speech" option removed; Settings/Language & keyboard tree
/system/app/GoogleTTS/GoogleTTS.apk
com.google.android.tts
/system/app/GnssAirTest/GnssAirTest.apk
com.lge.gnss.airtest
**** Deactivates "Bluetooth" settings from: Settings/Bluetooth (you can still toggle it on/off)
/system/app/LGBluetoothSetting/LGBluetoothSetting.apk
com.lge.bluetoothsetting
**** Removed Google account from: Settings/Accounts & Sync?
/system/priv-app/GooglePartnerSetup/GooglePartnerSetup.apk
com.google.android.partnersetup
**** Does NOT prevent Play Store from downloading / installing APKs
/system/priv-app/PackageInstaller/PackageInstaller.apk
com.android.packageinstaller
**** Removes "Google Play Movies & TV" from the 'app drawer' (bloatware!)
/system/app/Videos/Videos.apk
com.google.android.videos
/system/priv-app/ProxyHandler/ProxyHandler.apk
com.android.proxyhandler
**** Will remove the customized "Update LG Apps" from: Settings/About Phone/Update Center menu tree
/system/priv-app/LGUpdateCenter/LGUpdateCenter.apk
com.lge.updatecenter
**** Removes the 'SIM Lock' icon from the 'app drawer'
/system/priv-app/MPCS_Simlock/MPCS_Simlock.apk
com.metro.simlock
/system/priv-app/GoogleFeedback/GoogleFeedback.apk
com.google.android.feedback
**** Removes the 'Google Photos' app from the 'app drawer'
/system/app/Photos/Photos.apk
com.google.android.apps.photos
/system/app/LGDivXDRM/LGDivXDRM.apk
com.lge.divx.permission
/system/app/GoogleCalendarSyncAdapter/GoogleCalendarSyncAdapter.apk
com.google.android.syncadapters.calendar
/system/priv-app/ManagedProvisioning/ManagedProvisioning.apk
com.android.managedprovisioning
**** Removed the (red) "Voice Recorder" from the 'app drawer'
/system/priv-app/LGVoiceRecorder/LGVoiceRecorder.apk
com.lge.voicerecorder
**** Removed the 'File Manager' from the 'app drawer'
/system/priv-app/LGFileManager/LGFileManager.apk
com.lge.filemanager
/system/framework/lge-res-permission/lge-res-permission.apk
com.lge.permissions
**** UNSURE -- I assume "bookmark" widgets for all(?) browsers (for "all users" ergo: /system/app)
/system/app/LGPartnerBookmarksProvider/LGPartnerBookmarksProvider.apk
com.android.providers.partnerbookmarks
/system/priv-app/GoogleLoginService/GoogleLoginService.apk
com.google.android.gsf.login
**** When selecting "Settings/Home Screen/Theme" it now crashes (error: "Home" has stopped)
/system/priv-app/LGLiveWallpapersPicker/LGLiveWallpapersPicker.apk
com.android.wallpaper.livepicker
/system/priv-app/LGEasyHome/LGEasyHome.apk
com.lge.easyhome
**** (https://forum.xda-developers.com/note-4-sprint/general/how-to-access-hidden-menu-adb-rooted-t3403289) am broadcast -a android.provider.Telephony.SECRET_CODE -d android_secret_code://IOTHIDDENMENU
/system/app/HiddenMenu/HiddenMenu.apk
com.lge.hiddenmenu
**** Unknown repercussions
/system/framework/lge-res/lge-res.apk
com.lge
/system/app/IPService/IPService.apk
com.movial.ipservice
**** Removes the "App store" from the 'app drawer' (bloatware)
/system/priv-app/AppStore/AppStore.apk
com.handmark.metro.launcher
**** Unknown repercussions
/system/priv-app/LGNetworkSettings/LGNetworkSettings.apk
com.lge.networksettings
**** Removes the "LG Backup" from the 'app drawer' (and modifies Settings/Backup & reset)
/system/app/LGBackupLauncher/LGBackupLauncher.apk
com.lge.bnr.launcher
/system/priv-app/GoogleBackupTransport/GoogleBackupTransport.apk
com.google.android.backuptransport
/system/priv-app/LGPrivacylock/LGPrivacylock.apk
com.lge.privacylock
**** Causes system instability (endless loop of error: "Unfortunately, Home has stopped")!!!!
/system/priv-app/LGSettings/LGSettings.apk
com.android.settings
/system/app/LGFOTA/LGFOTA.apk
com.lge.lgfota.permission
**** Disables internal usage of "Location" hardware? The interfaces (toggle switches) are unaffected (no crashing)
/system/priv-app/com.qualcomm.location/com.qualcomm.location.apk
com.qualcomm.location
**** Causes crashes when attempting to view: Settings/About phone/Legal info sub-menus
/system/app/LicenseProvider/LicenseProvider.apk
com.lge.eulaprovider
**** LG Backup package?
/data/app/com.lge.bnr-1/base.apk
com.lge.bnr
/data/app/com.lge.ime-1/base.apk
com.lge.ime
/system/priv-app/Ims4/Ims4.apk
com.lge.ims
/system/priv-app/VpnDialogs/VpnDialogs.apk
com.android.vpndialogs
/system/priv-app/LGVideo/LGVideo.apk
com.lge.videoplayer
/system/app/LGDrm/LGDrm.apk
com.lge.lgdrm.permission
**** Removes "Mobile Hotspot" in the 'app drawer' AND disables Settings/Wifi from opening (but the Wifi can still be enabled with this package DISABLED)
/system/priv-app/LGWifiSettings/LGWifiSettings.apk
com.lge.wifisettings
**** Removes the "Hangouts" from the 'app drawer' (bloatware)
/system/app/Hangouts/Hangouts.apk
com.google.android.talk
**** ROOTED DEVICE ****
/system/app/SuperSU/SuperSU.apk
eu.chainfire.supersu
/system/app/LGEIME_THEME_BLACK3/LGEIME_THEME_BLACK3.apk
com.lge.ime.theme.black
/system/priv-app/LGTeleService/LGTeleService.apk
com.android.phone
SOMETHING BELOW REMOVED THE HOTKEY "Home" BUTTON
**** NOTE: Does not affect "adb shell" or "adb shell su -C <command>"
/system/priv-app/Shell/Shell.apk
com.android.shell
/system/app/DrmService/DrmService.apk
com.lge.drmservice
**** Removes the "music" widget from the App Drawer/Widgets
/system/priv-app/LGMusicWidget/LGMusicWidget.apk
com.lge.sizechangable.musicwidget.widget
/system/app/LGStartupEula/LGStartupEula.apk
com.lge.lgsetupwizard.eula
/system/app/UserDictionaryProvider/UserDictionaryProvider.apk
com.android.providers.userdictionary
/system/priv-app/Lookout/Lookout.apk
com.lookout
/system/app/GnssLogCat/GnssLogCat.apk
com.lge.gnsslogcat
/system/priv-app/FusedLocation/FusedLocation.apk
com.android.location.fused
**** NOTE: REBOOT REQUIRED - Lower bottom buttons vanish; All top level (phone/time/charge/etc) items no longer display; Pull-down menu disabled
/system/priv-app/LGSystemUI/LGSystemUI.apk
com.android.systemui
**** NOTE: REBOOT REQUIRED - Phone appears to boot-up properly; NOTHING is displayed upon successful load!
/system/priv-app/LGSystemUI_Provider/LGSystemUI_Provider.apk
com.lge.provider.systemui
/system/app/LGLockScreenSettings_Provider/LGLockScreenSettings_Provider.apk
com.lge.provider.lockscreensettings
**** Removes the "Clock" app from the 'app drawer' (bloatware to me)
/system/priv-app/LGAlarmClock/LGAlarmClock.apk
com.lge.clock
**** Removes the "EMail" app from the 'app drawer' (bloatware to me! GMail for LIFE!)
/system/priv-app/LGEmail/LGEmail.apk
com.lge.email
**** Removes the "Music" app from the 'app drawer' (bloatware again)
/system/priv-app/LGMusic/LGMusic.apk
com.lge.music
**** Affects the kernel / CPU (Qualcomm)? UNKNOWN
/system/app/fastdormancy/fastdormancy.apk
com.qualcomm.fastdormancy
/data/app/com.lge.kpt.adaptxt.alladdons-1/base.apk
com.lge.kpt.adaptxt.alladdons
/system/priv-app/LGInstallService/LGInstallService.apk
com.lge.lginstallservies
**** DISABLES Bluetooth (hardware / software toggle switch)
/system/app/LGBluetooth4/LGBluetooth4.apk
com.android.bluetooth
**** Disables internal synchronization with world clock?
/system/app/TimeService/TimeService.apk
com.qualcomm.timeservice
/system/priv-app/AndroidForWork/AndroidForWork.apk
com.google.android.androidforwork
/system/app/atfwd/atfwd.apk
com.qualcomm.atfwd
/system/priv-app/LGContactsProvider/LGContactsProvider.apk
com.android.providers.contacts
/system/app/servicemenu/servicemenu.apk
com.lge.servicemenu
/system/app/CaptivePortalLogin/CaptivePortalLogin.apk
com.android.captiveportallogin
/system/app/VisualVoicemail/VisualVoicemail.apk
com.metropcs.service.vvm[/QUOTE]
For completeness: Here are the packages I left enabled on my device (minimally to play installed games on the internet (Wifi)!
package:com.android.providers.settings
package:com.lge.launcher2
package:com.android.settings
package:eu.chainfire.supersu
package:com.android.systemui
package:com.lge.provider.systemui
package:com.supercell.boombeach
Click to expand...
Click to collapse
Here is a batch file script to disable all unnecessary packages (root enabled):
Code:
adb shell su -C pm disable com.hy.system.fontserver
adb shell su -C pm disable com.android.LGSetupWizard
adb shell su -C pm disable com.gd.mobicore.pa
adb shell su -C pm disable com.google.android.youtube
adb shell su -C pm disable com.lge.sizechangable.weather.platform
adb shell su -C pm disable com.android.providers.telephony
adb shell su -C pm disable com.google.android.googlequicksearchbox
adb shell su -C pm disable com.nuance.nmc.sihome.metropcs
adb shell su -C pm disable com.android.providers.calendar
adb shell su -C pm disable com.lge.mtalk.voicecommand
adb shell su -C pm disable com.android.providers.media
adb shell su -C pm disable com.google.android.apps.docs.editors.docs
adb shell su -C pm disable com.lge.systemservice
adb shell su -C pm disable com.google.android.onetimeinitializer
adb shell su -C pm disable com.android.wallpapercropper
adb shell su -C pm disable com.quicinc.cne.CNEService
adb shell su -C pm disable com.lge.appbox.client
adb shell su -C pm disable com.movial.ipprovider
adb shell su -C pm disable com.privacystar.android.metro
adb shell su -C pm disable com.android.documentsui
adb shell su -C pm disable com.android.externalstorage
adb shell su -C pm disable com.lge.android.atservice
adb shell su -C pm disable com.android.htmlviewer
adb shell su -C pm disable com.qualcomm.sta
adb shell su -C pm disable com.lge.app.floating.res
adb shell su -C pm disable com.android.mms.service
adb shell su -C pm disable com.google.android.apps.docs.editors.sheets
adb shell su -C pm disable com.lge.sui.widget
adb shell su -C pm disable com.google.android.apps.docs.editors.slides
adb shell su -C pm disable com.android.providers.downloads
adb shell su -C pm disable com.lge.camera
adb shell su -C pm disable com.android.browser.provider
adb shell su -C pm disable com.lge.touchcontrol
adb shell su -C pm disable com.lge.eltest
adb shell su -C pm disable com.lge.homeselector
adb shell su -C pm disable com.lge.gnsstest
adb shell su -C pm disable com.google.android.configupdater
adb shell su -C pm disable com.movial.wificall
adb shell su -C pm disable com.android.defcontainer
adb shell su -C pm disable com.android.providers.downloads.ui
adb shell su -C pm disable com.android.vending
adb shell su -C pm disable com.android.pacprocessor
adb shell su -C pm disable com.lge.shutdownmonitor
adb shell su -C pm disable com.mobileposse.client
adb shell su -C pm disable com.android.certinstaller
adb shell su -C pm disable com.google.android.marvin.talkback
adb shell su -C pm disable com.lge.launcher2.theme.optimus
adb shell su -C pm disable com.android.settingsaccessibility
adb shell su -C pm disable android
adb shell su -C pm disable com.lge.upsell
adb shell su -C pm disable com.android.contacts
adb shell su -C pm disable com.lge.lockscreensettings
adb shell su -C pm disable com.lge.ia.task.incalagent
adb shell su -C pm disable com.android.mms
adb shell su -C pm disable com.android.stk
adb shell su -C pm disable com.android.backupconfirm
adb shell su -C pm disable com.lge.exchange
adb shell su -C pm disable com.lge.wapservice
adb shell su -C pm disable com.lge.settings.easy
adb shell su -C pm disable com.google.android.gm
adb shell su -C pm disable com.android.calendar
adb shell su -C pm disable com.google.android.instantapps.supervisor
adb shell su -C pm disable com.lge.lgmapui
adb shell su -C pm disable com.lge.ims.rcsprovider
adb shell su -C pm disable com.google.android.setupwizard
adb shell su -C pm disable com.qualcomm.qcrilmsgtunnel
adb shell su -C pm disable com.android.sharedstoragebackup
adb shell su -C pm disable com.google.android.music
adb shell su -C pm disable com.android.printspooler
adb shell su -C pm disable com.android.incallui
adb shell su -C pm disable com.lge.drive.activator
adb shell su -C pm disable com.lge.gnsspostest
adb shell su -C pm disable com.android.inputdevices
adb shell su -C pm disable com.tmobile.pr.adapt
adb shell su -C pm disable com.lge.gba.android
adb shell su -C pm disable com.lge.eula
adb shell su -C pm disable com.lge.gcuv
adb shell su -C pm disable com.lge.sync
adb shell su -C pm disable com.lge.task
adb shell su -C pm disable com.google.android.apps.cloudprint
adb shell su -C pm disable com.google.android.apps.docs
adb shell su -C pm disable com.google.android.apps.maps
adb shell su -C pm disable com.google.android.webview
adb shell su -C pm disable com.android.server.telecom
adb shell su -C pm disable com.google.android.syncadapters.contacts
adb shell su -C pm disable com.android.facelock
adb shell su -C pm disable com.android.keychain
adb shell su -C pm disable com.android.chrome
adb shell su -C pm disable com.android.gallery3d
adb shell su -C pm disable com.lge.voicecommand
adb shell su -C pm disable com.google.android.gms
adb shell su -C pm disable com.google.android.gsf
adb shell su -C pm disable com.google.android.tts
adb shell su -C pm disable com.lge.gnss.airtest
adb shell su -C pm disable com.lge.bluetoothsetting
adb shell su -C pm disable com.google.android.partnersetup
adb shell su -C pm disable com.android.packageinstaller
adb shell su -C pm disable com.google.android.videos
adb shell su -C pm disable com.android.proxyhandler
adb shell su -C pm disable com.lge.updatecenter
adb shell su -C pm disable com.metro.simlock
adb shell su -C pm disable com.google.android.feedback
adb shell su -C pm disable com.google.android.apps.photos
adb shell su -C pm disable com.lge.divx.permission
adb shell su -C pm disable com.google.android.syncadapters.calendar
adb shell su -C pm disable com.android.managedprovisioning
adb shell su -C pm disable com.lge.voicerecorder
adb shell su -C pm disable com.lge.filemanager
adb shell su -C pm disable com.lge.permissions
adb shell su -C pm disable com.android.providers.partnerbookmarks
adb shell su -C pm disable com.google.android.gsf.login
adb shell su -C pm disable com.android.wallpaper.livepicker
adb shell su -C pm disable com.lge.easyhome
adb shell su -C pm disable com.lge.hiddenmenu
adb shell su -C pm disable com.lge
adb shell su -C pm disable com.movial.ipservice
adb shell su -C pm disable com.handmark.metro.launcher
adb shell su -C pm disable com.lge.networksettings
adb shell su -C pm disable com.lge.bnr.launcher
adb shell su -C pm disable com.google.android.backuptransport
adb shell su -C pm disable com.lge.privacylock
adb shell su -C pm disable com.lge.lgfota.permission
adb shell su -C pm disable com.qualcomm.location
adb shell su -C pm disable com.lge.eulaprovider
adb shell su -C pm disable com.lge.bnr
adb shell su -C pm disable com.lge.ime
adb shell su -C pm disable com.lge.ims
adb shell su -C pm disable com.android.vpndialogs
adb shell su -C pm disable com.lge.videoplayer
adb shell su -C pm disable com.lge.lgdrm.permission
adb shell su -C pm disable com.lge.wifisettings
adb shell su -C pm disable com.google.android.talk
adb shell su -C pm disable com.lge.ime.theme.black
adb shell su -C pm disable com.android.phone
adb shell su -C pm disable com.android.shell
adb shell su -C pm disable com.lge.drmservice
adb shell su -C pm disable com.lge.sizechangable.musicwidget.widget
adb shell su -C pm disable com.lge.lgsetupwizard.eula
adb shell su -C pm disable com.android.providers.userdictionary
adb shell su -C pm disable com.lookout
adb shell su -C pm disable com.lge.gnsslogcat
adb shell su -C pm disable com.android.location.fused
adb shell su -C pm disable com.lge.provider.lockscreensettings
adb shell su -C pm disable com.lge.clock
adb shell su -C pm disable com.lge.email
adb shell su -C pm disable com.lge.music
adb shell su -C pm disable com.qualcomm.fastdormancy
adb shell su -C pm disable com.lge.kpt.adaptxt.alladdons
adb shell su -C pm disable com.google.android.play.games
adb shell su -C pm disable com.lge.lginstallservies
adb shell su -C pm disable com.android.bluetooth
adb shell su -C pm disable com.qualcomm.timeservice
adb shell su -C pm disable com.google.android.androidforwork
adb shell su -C pm disable com.qualcomm.atfwd
adb shell su -C pm disable com.android.providers.contacts
adb shell su -C pm disable com.lge.servicemenu
adb shell su -C pm disable com.android.captiveportallogin
adb shell su -C pm disable com.metropcs.service.vvm
Here's a batch file script to kill all active processes and background processes:
Code:
adb shell su -C am kill-all
adb shell su -C am force-stop com.hy.system.fontserver
<insert remaining disabled processes>
adb shell su -C am kill-all
Hopefully these findings will result in some helpful information or general tweaking of someone's ROM or phone! You can definitely cut out A LOT of these packages without altering the system very much! I am sure we can all agree that no one needs the "EMail" or "Music" or "Voice Recorder" or etc app with a legitimate 'stock firmware ROM,' as the person will likely remove them upon immediate installation (flashing) of the OS.
You're welcome.
EDIT: FINAL NOTE AND REMINDER
If you end up disabling the wrong package (EG: "system instability" or "system inoperable"): Do not worry! Even when you're stuck on the bootanimation ('screen is frozen'): You can still issue ADB commands to enable/disable packages.
Example: You disable com.android.settings or com.lge.provider.systemui
In either event: You can repair this with adb on the fly.
Code:
adb shell su -C pm enable com.lge.provider.systemui
Happy tweaking!