Database Info

tcsh port to Android

Hi,
I searched the web for a tcsh port to Android, but came up empty. So I ported it
myself today. I've sent the required patches (not many, actually) upstream a couple of
minutes ago. You can also find them attached as file tcsh-android.diff.
There's one problem. Since $HOME isn't set by default, tcsh can't load the user
profiles (.login/.cshrc). My patch tweaks tcsh so that it sets the home directory to
/sdcard on Android if $HOME doesn't exist in the environment.
Does that make sense? On my Samsung i5800, there's an environment variable
EXTERNAL_STORAGE, which is set to /scard. Does this environment variable
exist on all Android platforms or is that a Samsung invention? If it's generically
available it would probably make sense to default the home dir to the content of
EXTERNAL_STORAGE. Is there another, better alternative?
I also made an arm binary available (see attached file tcsh.zip). Sha1sum of the
unzipped binary is 5b19a3de76c0caf20b3d7f5d1ae1e9b9427d7ef4. Tested on
Samsung i5800 w/ 2.1 via `adb shell' and local ConnectBot sessions.
It has been build like this:
configure --host=arm-linux-androideabi --prefix=/system
make
Have fun,
Corinna

cvxda said:
It has been build like this:
configure --host=arm-linux-androideabi --prefix=/system
make
Click to expand...
Click to collapse
I forgot to mention that you have to run `autoreconf' first. The patch file
doesn't include a new configure, only configure.in.
Corinna

Thanks for this! Just got it working on my Samsung Galaxy S. Good to have a decent shell.

How do you installl the shell and run it on the device?

Installing tcsh
sillyfunnypedro said:
How do you installl the shell and run it on the device?
Click to expand...
Click to collapse
I used root file explorer but you can do it with sh/busybox
Steps I under took
Unzip
Mount /system/ read write
copy to /system/xbin/
Change permissions to rwx-rx-rx
Mount /system read only again
The reason I put it in /system/xbin is the sdcards are mounted -noexec this prevents any linux executables from running from anywhere but the write protected system partitions.
To be totally correct I feel I should have used a bin directory in a new read only yafs partition mounted on /opt/

BusyBox Aliases
Attached is a complete list of aliases to busybox suitable for tcsh
add/append to your .cshrc
Or type source shell.aliases.txt just to load them.
Traditional method with busybox is to use links as in
ln -s /system/bin/busybox /somepath/more
I want to modify /system/ as little as possible and am yet to create a separate partition for /opt/. So I am using Aliases.

Hi,
for some reason this breaks resolv.conf. any ideas?
# busybox nslookup google.com
busybox nslookup google.com
Server: 192.168.2.1
Address 1: 192.168.2.1 router
Name: google.com
Address 1: 74.125.73.147 tul01m01-in-f147.1e100.net
Address 2: 74.125.73.99 tul01m01-in-f99.1e100.net
Address 3: 74.125.73.103 tul01m01-in-f103.1e100.net
Address 4: 74.125.73.104 tul01m01-in-f104.1e100.net
Address 5: 74.125.73.105 tul01m01-in-f105.1e100.net
Address 6: 74.125.73.106 tul01m01-in-f106.1e100.net
# tcsh
tcsh
localhost/# busybox nslookup google.com
busybox nslookup google.com
Server: 0.0.0.0
Address 1: 0.0.0.0
nslookup: can't resolve 'google.com'

cvxda said:
Hi,
I searched the web for a tcsh port to Android, but came up empty. So I ported it
myself today... [etc.]
Click to expand...
Click to collapse
At long last I updated the Android port in the upstream tcsh repository to support latest Android. The patches are backward incompatible with Android versions prior to 4.1.
The tcsh repo can be accessed via Github, the patchset is in commits c09b305 and 47ac106.
I attached a new arm version of tcsh to this thread for convenience. It's a zip file which can be installed from recovery mode. It installs tcsh into /system/xbin and default .cshrc and .login files to /sdcard.
Have fun,
Corinna

[Guide] How to enable init.d script support on stock ROM

*****************************************************************************************************************************************************
Credit for discovering this method goes to Sr. Staff gurus @_that (bet you could have guessed) and @becomingx for parsing GNU code to figure out file naming limitations (no dots!) to make this work.
******************************************************************************************************************************************************
This short Guide accompanies the need to run my B2R startup script (or any script) as root at boot. If you are rooted and have busybox installed on a stock ROM or any ROM that does not have init.d support thru init.rc, here's how you can add it. This is an alternative method to either using Script Manager (SManager) or hijacking the install-recovery.sh file directly to run a startup script. Enabling this support allows you to be able to run all executable scripts located in init.d as root at boot.
IMPORTANT: Your init script name can NEITHER have any dots in the filename NOR use an extension. Name it something like autostart or start-up or init_script. Also when you write a script, NEVER forget to start it with the hash-bang-path to shell (#!/system/bin/sh) and NEVER forget to press ENTER after the last character of the last line of code. You can't just use any simple text editor to create the file - you must pay close attention to "line ends". I use ES Note Editor on device and Notepad++ configured for UNIX/OSX line ends on PC. Always save the file AS PLAIN TEXT. Read "Additional Information" below on line ends.
[NOTE: /system/etc = /etc (symlink)]
1. Mount your /system rw
Code:
mount -o remount,rw /system
2. Make directory /system/etc/init.d
Code:
mkdir /system/etc/init.d
3. Create a shell script (using a text editor with UNIX line ends [LF only] ) named "/system/etc/install-recovery.sh" with the following contents:
Code:
#!/system/bin/sh
/system/bin/logwrapper /system/xbin/busybox run-parts /system/etc/init.d
4. Put your init script in init.d and remember to make both /system/etc/install-recovery.sh and your script in /system/etc/init.d executable.
Code:
cd /system/etc
chmod 755 install-recovery.sh
cd /system/etc/init.d
chmod 755 name_of_your_init_script
5. Immediately reboot or if not, mount your /system ro
Code:
mount -o remount,ro /system
If you have busybox installed in /system/xbin this enables support for running init.d scripts from ROMs that do not offer native support thru init.rc.
Additional Information:
Every file has what are know as line ends or more technically end of line (EOL) conversions. These are HIDDEN characters that you normally don't see (if the line end are in the native OS format) at the end of lines in a text editor when editing files. This is the character that tells the OS where one line stops and the next starts in any file. In order to see the line ends you must enable "show all characters".
Your text editor must support UNIX line ends (LF only, not CR + LF = CRLF). Do NOT use Windows Notepad as it only creates Windows line ends (CRLF).
Always use UNIX line ends - a Windows editor like Notepad will create CRLF line ends, while your shell script MUST use LF line ends or it will fail to execute. Otherwise your first line will look like this to Linux:
Code:
#!/system/bin/sh^M
The ^M above is the common convention to display the control character Ctrl+M, which is CR (carriage return) before the LF (line feed) or (CRLF). The consequence is that the system can't find your shell under the name "sh^M" (or any subsequent command "some_command^M") and your script will fail.
This is VERY important to understand and also how to configure any cross-platform text editor. Using notepad++ in Windows without changing the default settings still results in CRLF at the end of lines because it knows its running in Windows and thinks you want Windows line ends. In order to change this behavior, Under the Edit menu find EOL conversion, and select Unix/OSX format. Also toggle the paragraph symbol on the top bar (backwards P with double verticles; show all characters) and now its clear as day what line ends you have, where they are, and if you have one after the end of the last line or not. Now its WYSIWYG. Once these setting are toggled, saving the file in Windows results in Unix/OSX line ends (LF) and when you open notepad++ the next time the settings are retained. See screenshot before attachment at the end of this post.
Example for changing default EOL conversion to Unix LF for an older version of notepad++:
http://techtips-it.blogspot.com/2011/04/can-i-convert-file-format-in-notepad.html
If done correctly, the output you will see if VIEWED (not edited) using Windows notepad will show a small hollow rectangle representing each LF. You will see one for each line end, and two together at the end of the last line itself - the first is the EOL LF for that line, and the subsequent is the LF you entered after the last line. If notepad just shows what you would normally see in the XDA code block with no extra special characters as described, you have Windows line ends and your script will fail to execute.
If you have multiple scripts to run at boot, the real purpose of init.d, you should name your init scripts prepended with two digits between 00 and 99. (Fairly) Evenly divide the range into 3 groups like 2# (20-29), 5# (50-59), and 8# (80-89). Scripts in the 20 series will be run first, followed by 50 series scripts, ending with 80 series scripts. They will be executed from lowest number to highest number, in that order. This allows you to define the load order for a group of init scripts. We didn't use 00-19 or 90-99 in case we need to put a future script before the first or after the last one without having to rename the rest of the scripts to do so.
Example init script names: 20firststart, 50mid_start, 80end-boot
******************************************************************************************************************************************************
Download the attachment and remove the txt extension and copy it into /system/etc and make sure it is executable. Make directory /system/etc/init.d, put your executable boot scripts in there, and reboot to run your executable init.d scripts as root.
This method replaces the depreciated method of directly hijacking install-recovery.sh with a single boot script run as root. Why have only one when you can have many?
Linkback to dev thread
http://forum.xda-developers.com/showthread.php?t=2191777

Reserved
Sent from my LG-LS970 using xda app-developers app

elfaure said:
@_that, please review and bless.
Click to expand...
Click to collapse
elfaure said:
IMPORTANT: Your init script name can NEITHER have any dots in the filename NOR use an extension. Name it something like autostart or start-up or init_script.
Click to expand...
Click to collapse
I still recommend using the common Unix convention of 2 digits + lowercase name for init.d scripts, e.g. 50something, 60dothislater, 90somethingtodolast. The numbers allow for clearly defining the order in which multiple startup scripts are executed.
elfaure said:
Also when you write a script, NEVER forget to start it with the hash-bang-path to shell (#!/system/bin/sh) and NEVER forget to press ENTER after the last character of the last line of code. You can use any simple text editor to create the file. I use ES Note Editor on device and Notepad++ on PC. Always save the file AS PLAIN TEXT.
Click to expand...
Click to collapse
And always use UNIX line ends - a Windows editor like Notepad will create CRLF line ends, while your shell script MUST use LF line ends. Otherwise your first line will look like this to Linux:
Code:
#!/system/bin/sh^M
The ^M above is the common convention to display the control character Ctrl+M, which is CR (carriage return) before the LF (line feed). The consequence is that the system can't find your shell under the name "sh^M" and your script will fail.
elfaure said:
4. Remember to make it executable and to create the /system/etc/init.d directory.
Click to expand...
Click to collapse
You already created init.d in step 1.
Looks like it could work like this. If you want to be sure, remove your existing scripts and rmdir your init.d directory, then follow your own guide and see if everything is OK. Then you can bless it yourself. In software development, peer review is always good, but testing is even more important.

_that said:
I still recommend using the common Unix convention of 2 digits + lowercase name for init.d scripts, e.g. 50something, 60dothislater, 90somethingtodolast. The numbers allow for clearly defining the order in which multiple startup scripts are executed.
And always use UNIX line ends - a Windows editor like Notepad will create CRLF line ends, while your shell script MUST use LF line ends. Otherwise your first line will look like this to Linux:
Code:
#!/system/bin/sh^M
The ^M above is the common convention to display the control character Ctrl+M, which is CR (carriage return) before the LF (line feed). The consequence is that the system can't find your shell under the name "sh^M" and your script will fail.
You already created init.d in step 1.
Looks like it could work like this. If you want to be sure, remove your existing scripts and rmdir your init.d directory, then follow your own guide and see if everything is OK. Then you can bless it yourself. In software development, peer review is always good, but testing is even more important.
Click to expand...
Click to collapse
Thanks for the review! I will make some edits, test drive the guide, and bless it myself. I was already going to add the two digit numerical discussion. I'm not trying to get you to do any extra or my work here, God knows you are a very busy multi-tasking hundreds of tasks , I just thought I was on newb patrol after posting a non-working script and then mandated to your must review list.

Is this method works on other phone too?
I really do want the init.d support on stock rom
Sorry for my bad English...
Sent from my HTC Desire 200 using XDA Premium 4 Mobile app

dicks93277 said:
Is this method works on other phone too?
I really do want the init.d support on stock rom
Click to expand...
Click to collapse
The method is reasonably generic that it is worth trying on your device.

so sad that i can't make this work on my phone
but still thanks for your reply @_that

Awesome it works on my Panasonic T41 running MIUI 5 beta
Could you tell how to do the same thing from init.rc ???
and also one script is not working
Code:
#!/system/bin/sh
su
mount -o rw,remount /
mkdir -p /rex
mount -o bind /data/data/com.spartacusrex.spartacuside/files/system /rex
mount -o rw,remount /system
mkdir -p /system/vendor/bin
mount -o /rex/bin /system/vendor/bin
Is there any thing wrong with it ?? I used unix terminators and also set the permissions to 755

uttarayan21 said:
Awesome it works on my Panasonic T41 running MIUI 5 beta
Could you tell how to do the same thing from init.rc ???
and also one script is not working
Code:
#!/system/bin/sh
su
mount -o rw,remount /
mkdir -p /rex
mount -o bind /data/data/com.spartacusrex.spartacuside/files/system /rex
mount -o rw,remount /system
mkdir -p /system/vendor/bin
mount -o /rex/bin /system/vendor/bin
Is there any thing wrong with it ?? I used unix terminators and also set the permissions to 755
Click to expand...
Click to collapse
The 'su' command with no arguments starts an interactive shell, everything after 'su' waits for the user to exit that shell, which you can't do. Init.rc and subsequent scripts are run as root anyway, including init.d scripts, so just delete the 'su' line and it should work.
Sent from my LGL41C using Tapatalk

Kor1134 said:
The 'su' command with no arguments starts an interactive shell, everything after 'su' waits for the user to exit that shell, which you can't do. Init.rc and subsequent scripts are run as root anyway, including init.d scripts, so just delete the 'su' line and it should work.
Sent from my LGL41C using Tapatalk
Click to expand...
Click to collapse
Thanks !!! It worked !!!!

uttarayan21 said:
Thanks !!! It worked !!!!
Click to expand...
Click to collapse
You're welcome [emoji6]
Sent from my LGL41C using Tapatalk

Why don't use service from init.rc ??
elfaure said:
*************************************,
3. Create a shell script (using a text editor with UNIX line ends [LF only] ) named "/system/etc/install-recovery.sh" with the following contents:
Code:
#!/system/bin/sh
/system/bin/logwrapper /system/xbin/busybox run-parts /system/etc/init.d
Click to expand...
Click to collapse
But it is better to add a service to init.rc and launch sysinit from there for init.d support !!!
Maybe you should update your guide with that !!!
:laugh: :good:

uttarayan21 said:
But it is better to add a service to init.rc and launch sysinit from there for init.d support !!!
Maybe you should update your guide with that !!!
:laugh: :good:
Click to expand...
Click to collapse
Changing init.rc requires repacking the boot image.

_that said:
Changing init.rc requires repacking the boot image.
Click to expand...
Click to collapse
Yeah it does but if you install SuperSU then the install-recovery.sh file will be modified and init.d will be lost !!!

What bloatware is safe to uninstall?

Hi,
I couldn't find a thread already on this with a quick search so I was wondering if anyone knows what bloatware apps, User or System, would be safe to uninstall with a rooted phone?
By safe I mean either:
Has no impact on any other functions and if you don't want the features that the app provides you can uninstall it/freeze it/disable it
Can be uninstalled/disabled/frozen with no major impact on device functionality but with some exceptions that if a user is ok with these exceptions not to work then it is otherwise safe to uninstall/freeze/disable (for example say uninstalling a certain system app breaks NFC but you don't care about NFC anyway)
I basically would like to see if this helps with speeding up the phone as, although there is 3GB of RAM, when clearing all recent apps, 2GB is still used up by, I can only assume, system apps and the OS and perhaps some of these are RAM hoggers that I don't need/want anyway.
Thanks for any help/advice

I personally go by what apps can be found in the app drawer
(Aside the obvious e.g settings app)
Sent from my D6503 using XDA-Developers mobile app

apks of MM .185 on Z5 Compact
I've been doing a lot of debloating some weeks ago, mainly to try to decrease idle battery drain on my Z5 Compact (without much success...)
So I may share my understanding and sorting of system apks by topic and importance.
These are from MM .185 on Z5 Compact (hope all Z5 models have the same apps).
I'm going to post the content of some input file to a script I execute in TWRP, which moves the apk listed in the non-commented lines (lines not starting with a #) in /system/__REMOVED/.
The current state of removed (lines starting with /) vs kept (lines starting with #) is what I consider safe and sane for now. But lots of # app can be removed without any side effects (see comments). It boots and works ok if you remove all the apks listed, except the ones in the latest 2 sections.
(Full content, sorry if it hurts, but it will allow people to find this post if they search XDA for one of the listed apk - like I had been doing for days).
Most have obvious names, so we get what they do. Some others are less obvious, and I give in the comment line before them what i found out (or just guess) they do.
# Started with elements from from XPower 1.0
# http://forum.xda-developers.com/z5-compact/development/rom-xpower-v1-0-aroma-debloat-custom-t3371100
# Also see for a full detailed list of Lollipop apps
# https://docs.google.com/spreadsheets/d/1geFByRKDTOOZSIBOixO2boG1_78NUjqzkB6iozzJ4-k/htmlview#
# 20160520 : tested a few days with some extreme debloat, but no effect on battery usage
# So, we go easier, and we let some app that otherwise would cause warnings in logcat
#########################################
### The obvious bloat
# Other than /system/app/priv-app :
/system/recovery-from-boot.p
# Lots of bloat in etc/product
/system/etc/product
# Not much in these dirs, and these looks like low-level stuff (nativeaudiolatency, servicemenu...), better keep them :
# /system/vendor/overlay
# /system/vendor/app
# Google apps
/system/app/Chrome
/system/app/Drive
/system/app/Gmail2
/system/app/Photos
/system/app/Hangouts
/system/app/Music2
/system/app/Videos
/system/app/YouTube
/system/app/Maps
/system/app/talkback
/system/priv-app/Velvet
# We keep google TTS, we get logcat warnings if no tts available
# /system/app/GoogleTTS
# Sony themes/wallpapers
/system/app/BasicDreams
/system/app/Galaxy4
/system/app/HoloSpiralWallpaper
/system/app/LiveWallpapers
/system/app/LiveWallpapersPicker
/system/app/NoiseField
/system/app/PhaseBeam
/system/app/photoslideshow-release
/system/app/PhotoTable
/system/app/experienceflow2livewallpaper-release
/system/vendor/overlay/overlay-semcexperienceflow2-300-release.apk
# Themes stuff (work without, but we may need to keep it to get black lockscreen wallpaper)
# No, Album should be enough to allow us to pick wallpapers
/system/app/skin-core-release
/system/app/skin-picker-release
/system/app/theme-manager-release
# We keep themes 000 (rainbow) and 006 007 008 (grey, black & white)
# No, we keep only 007 black, just in case
/system/app/Theme000-sw360dp-xhdpi-release
/system/app/Theme001-sw360dp-xhdpi-release
/system/app/Theme002-sw360dp-xhdpi-release
/system/app/Theme003-sw360dp-xhdpi-release
/system/app/Theme004-sw360dp-xhdpi-release
/system/app/Theme005-sw360dp-xhdpi-release
/system/app/Theme006-sw360dp-xhdpi-release
# /system/app/Theme007-sw360dp-xhdpi-release
/system/app/Theme008-sw360dp-xhdpi-release
# Sony updates/accounts/services
/system/app/com.sonyericsson.xhs
/system/app/com.sonymobile.xperialounge.services
/system/app/Lifelog-googlePreloadLive-release-2.9.P.3.8-5377032
/system/priv-app/GetMore-stub-release
/system/priv-app/somc-get-to-know-it-release
/system/priv-app/MyXperia
/system/priv-app/RecommendationEngineExtension-release
/system/priv-app/UpdateCenter-release
# Sonyentrance = Whats new
/system/priv-app/sonyentrance2-release
/system/app/SyncHub-release
/system/app/SemcWarrantyTime
/system/app/sneiaccountmanager-live
/system/app/support
/system/app/DemoAppChecker
/system/priv-app/retaildemo
# Sony & parners apps
/system/app/PhotoWidget-release
/system/app/WikipediaPlugin
/system/app/YouTubeKaraokePlugin
/system/app/YouTubePlugin
/system/app/WorldClockWidget-release
/system/app/WeatherWidget-release
/system/app/facebook-appmanager-xhdpi
/system/priv-app/facebook-installer
/system/priv-app/com.mobisystems.fileman
# We keep clock widgets
# /system/app/ClockWidgets-release
#########################################
### The less obvious bloat
# For Xperia companion (?) that we don't use anymore (we use Flashtool)
/system/priv-app/usb-mtp-backup-transport
/system/priv-app/usb-mtp-factoryreset-wrapper
/system/priv-app/usb-mtp-fotaupdate-wrapper
/system/priv-app/usb-mtp-update-wrapper
/system/priv-app/usb-mtp-vendor-extension-service
# Sony apps/features we don't really care about
/system/app/TouchBlock
/system/app/gmail-reader-service
/system/app/GoogleLyricsPlugin
/system/app/HTMLViewer
/system/app/TopContactsWidget-release
/system/app/weather-release
/system/app/XperiaTransferMobile-release
/system/app/cover-widget
/system/priv-app/CoverApp
/system/priv-app/ActiveClipper
# We only keep SmallAppManagerService : avoid warnings in logcat (but yet no small app)
# /system/priv-app/SmallAppManagerService-release
/system/priv-app/SmallApp-Calculator-release
/system/priv-app/SmallAppsFramework-release
/system/priv-app/SmallAppsLauncher-release
/system/priv-app/SmallApp-Timer-release
/system/priv-app/SmallAppWidget-release
# We keep Sony Tasks, Agenda has some dependancies on it (otherwise logcat warnings)
# /system/app/Tasks
# We will reinstall updated Album from Store
/system/priv-app/album-albumLive-release
# To edit pictures in case we need to
# /system/priv-app/SemcPhotoEditor
# Other apps we don't care about
/system/priv-app/SomcPhotoAnalyzer
/system/app/SomcMovieCreatorRmm-release
/system/priv-app/SomcMovieCreator-release
/system/priv-app/SemcVideo
/system/priv-app/SemcMusic
/system/priv-app/SomcPodcast
/system/priv-app/SemcEmail
# Sony Video store
/system/priv-app/SnpVUStore
# Music Metadata
/system/app/SemcMetadataCleanup
# Camera gadget addons
/system/priv-app/ArtFilterCamera-xhdpi-release
/system/app/ar-effect
/system/priv-app/SemcCamera3D-xhdpi-release
/system/priv-app/StylePortrait
/system/app/StyleBlue-release
/system/app/StyleBubble-release
/system/app/StyleDaily-release
/system/app/StylePaint-release
/system/app/StyleRed-release
/system/app/StyleStar-release
/system/app/StyleSunshine-release
/system/app/StyleSuntan-release
/system/priv-app/DualCamera-xhdpi-release
/system/priv-app/FaceFusionCamera-xhdpi-release
/system/priv-app/OnlineRemoteCamera-xhdpi-release
/system/priv-app/SoundPhotoCamera-xhdpi-release
/system/priv-app/CameraWearableBridgeHandheldServer
# Tv & wireless sharing
/system/app/dlna-somc-xhdpi-release
/system/priv-app/SemcTvOut
/system/priv-app/SomcMirrorLinkManualSwitch
/system/priv-app/SomcMirrorLinkServer
/system/priv-app/SomcMirrorLinkSystem
/system/priv-app/SomcPlayAnywhere
# We let everything "wifi display", not really clear what is sony/qualcomm/atfWD
# and what makes Chromecast or Miracast in settings...
# (ATFWD may mean AT command forward, which would be completely something else)
# Could be added to build.prop : persist.radio.atfwd.start=false
# /system/priv-app/SomcWifiDisplay
# Qualcomm Wifi display
# /system/app/WfdService
# Gamepad, smartwatch, heartbeat & co
/system/app/AntHalService
/system/priv-app/livewaremanager
/system/app/DualShockManager
/system/app/RemoteControlService
# Asian keyboards
/system/app/ExternalKeyboardJP
/system/app/SomcPOBox
/system/priv-app/textinput-chn-xhdpi
# Intelligent stuff
/system/app/Iengine
/system/app/IntelligentBacklight
/system/app/IntelligentObserver
/system/priv-app/IntelligentGesture
/system/app/FaceLock
# OverTheAir stuff
/system/app/OmaDownload
/system/app/OmaV1AgentDownloadServices
/system/app/fota-service
/system/priv-app/OMAClientProvisioning-release
# This app deletes some becknmark apps and block access to android forums (launched in
# some very specific context ?!)
/system/app/pip
# Sony background services, crash & usage reporting
/system/app/AnonymousData
/system/app/CrashMonitor
/system/app/CrashMonitorSystem
/system/app/IddAgent
/system/app/RcaHandler
/system/app/phone-usage
/system/app/device-monitor
/system/app/GoogleAnalyticsProxy
# Setting "Storage/Move stuff to Sd Card" will Force-Close without this
# but it checks disk usage every 10 minutes ! :
/system/priv-app/SemcStorageChecker
# Xperia configurator/Enterprise/Cloud backup...
/system/app/DeviceConfigTool
# Exchange & Enterprise stuff
/system/app/Exchange3Google
/system/priv-app/Exchange2
/system/app/SomcEnterpriseInstallationService
/system/priv-app/EnterpriseService
/system/app/OneTimePassLockScreenApp
/system/priv-app/RemoteUnlockService
# DRM stuff : we keep them, may be needed for Sony own drm stuff
# /system/app/DrmDialogs
# /system/app/SecureClockService
# /system/priv-app/DtcpCtrl-release
# /system/app/KerberosService
# Works fine without all that :
# These creates some bookmarks sqlite dbs
# /system/app/BookmarkProvider
# /system/app/PartnerBookmarksProvider
# /system/priv-app/BackupRestoreConfirmation
# /system/priv-app/EmergencySms
# Backup on SD card
# /system/priv-app/SharedStorageBackup
# We keep this one to avoir warnings in logcat
# /system/app/PrintSpooler
# These two do not prevent the SIM card and phone from working :
# "Sim service" app : if kept, our carrier icon is recreated in Home launcher at each boot
/system/app/Stk
/system/app/SmartcardService
# /system/app/TetherEntitlementCheck
# May help start SIM card pin earlier (?)
# /system/app/StartupFlagV2
# Rich content services ? We can keep them, may be used by SMS/MMS
# /system/app/rcs-startup
# /system/priv-app/RcsVideoShare
# /system/priv-app/rcs-core
# /system/priv-app/rcs-settings
# Low level GSM/network stuff
# Works without these, but do not change battery usage, so let's keep them
# /system/priv-app/CNEService
# /system/priv-app/QtiTetherService
# /system/priv-app/fast-dormancy-wakeup
# /system/priv-app/qcrilmsgtunnel
###############################################
# 20150517 : boots and works OK without the following ones,
# but some features are obviously lost
# Bluetooth & NFC
# /system/app/Bluetooth
# /system/app/NfcNci
# /system/app/BluetoothMidiService
# /system/app/AptxNotifier
# Camera
# /system/app/CameraAddonPermission-release
# /system/app/CameraCommonPermission-release
# /system/app/CameraExtensionPermission-release
# /system/priv-app/CameraCommon
# /system/priv-app/SemcCameraUI-generic-xhdpi-release
# /system/priv-app/SuperVideoCamera-xhdpi-release
# Wifi (CaptivePortal = free wifi access points with intermediate web page ?)
# /system/app/CaptivePortalLogin
# /system/app/HotspotAdvancedSetting
# /system/priv-app/SomcWifiService
# Used to raise power when acting as a hotspot, and decrease it when power is low :
# /system/app/TransmitPower
# Fingerprint (works ok without this Sony one), but :
# java.lang.Exception: The FPC extension service could not be loaded
# /system/priv-app/SomcFingerprint
# /system/app/FingerprintServiceExtension
# Fingerprint "FIDO" stuff, fingerprint unlock works without these two apk
# /system/app/FingerprintASM
# Other FIDO stuff (not in CM13)
# /system/app/FidoClient
# /system/priv-app/FidoCryptoService
# Other Sony stuff we can remove
# /system/app/HeadphoneSelection
# /system/app/UnsupportedHeadsetNotifier
# /system/app/SemcAutoPowerOff
# /system/app/SemcPowerSaveModule
# Cnap = Calling Name Provider
# /system/app/SemcCnapProvider
# Restart if SIM inserted/removed popup
# /system/app/SemcSimDetection
# /system/app/TouchFilterPackageSwitchService
# This one installs packages (?)
# /system/app/package-courier-release
# Sound
# /system/app/SoundEnhancement
# /system/priv-app/MusicFX
# /system/priv-app/SoundRecorder
# Sony images enhancement
# Let's keep it to validate drmrestore
# /system/app/ImageEnhancer
# /system/app/ImageProcessorPermission-release
# Standard stuff (also in CM13)
# /system/app/PacProcessor
# /system/app/Radio3
# /system/app/WAPPushManager
# WapPush is Sony only
# /system/priv-app/WapPush
# /system/app/white-balance
# /system/priv-app/ApnUpdater-release
# /system/priv-app/CallLogBackup
# /system/priv-app/CredentialManagerService
# /system/priv-app/CustomizationSelector-xhdpi-release
# /system/priv-app/CustomizedSettings-release
# Low level security (IMEI, SIM, S1 cert...) :
# /system/priv-app/DeviceSecurityService
# /system/priv-app/ExtendedBootLockService
# /system/priv-app/ScreenRecording
# /system/priv-app/SimlockUnlockApp
# /system/priv-app/SmartSearch
# /system/priv-app/TopContactsProvider
# /system/priv-app/VpnDialogs
# Lots of location services in this Qualcomm app
# /system/priv-app/com.qualcomm.location
# USB stuff, mainly for japanese carrier ? (not many translations in ressources)
# /system/priv-app/enhancedusbux
###############################################
# Google core stuff
# Apps included in Open Gapps PICO :
# ConfigUpdater
# GoogleBackupTransport
# GoogleContactsSyncAdapter
# GoogleFeedback
# GoogleLoginService
# GoogleOneTimeInitializer
# GooglePartnerSetup
# GoogleServicesFramework
# Phonesky
# PrebuiltGmsCore
# SetupWizard
# Stock Google stuff, that we can remove if we want to install Gapps pico instead
# /system/app/GoogleCalendarSyncAdapter
# /system/app/GoogleContactsSyncAdapter
# /system/priv-app/ConfigUpdater
# /system/priv-app/GoogleBackupTransport
# /system/priv-app/GoogleFeedback
# /system/priv-app/GoogleLoginService
# /system/priv-app/GoogleOneTimeInitializer
# /system/priv-app/GooglePackageInstaller
# /system/priv-app/GooglePartnerSetup
# /system/priv-app/GoogleServicesFramework
# /system/priv-app/Phonesky
# /system/priv-app/GmsCore
# /system/priv-app/SetupWizard
# We can remove some of them, but some others of them are needed : otherwise, bootloop.
###############################################
# 20150517 : apk we still keep (probably all essentials)
# /system/app/CertInstaller
# /system/app/ClockWidgets-release
# /system/app/CoreSettings
# /system/app/DocumentsUI
# /system/app/DownloadProviderUi
# /system/app/ExactCalculator
# /system/app/ExternalKeyboardsInternational
# /system/app/KeyChain
# /system/app/LockscreenSettings-release
# /system/app/SemcSettings
# /system/app/ServiceMenu
# /system/app/TimeService
# /system/app/UserDictionaryProvider
# /system/app/WebViewGoogle
# /system/app/app-textInputLive-release
# /system/app/bootinfo
# /system/app/duidgenerator
# /system/app/home-release
# /system/app/telresources
# /system/app/wallpaperpicker-release
# /system/app/xperia-keyboard-dictionaries
# /system/priv-app/CalendarProvider
# /system/priv-app/CarrierConfig
# /system/priv-app/Conversations
# /system/priv-app/DefaultContainerService
# /system/priv-app/DownloadProvider
# /system/priv-app/ExternalStorageProvider
# /system/priv-app/FusedLocation
# /system/priv-app/InCallUI
# /system/priv-app/InputDevices
# /system/priv-app/LocalContacts
# /system/priv-app/ManagedProvisioning
# /system/priv-app/MediaProvider
# /system/priv-app/MmsService
# /system/priv-app/Phonebook
# /system/priv-app/ProxyHandler
# /system/priv-app/SEMCSetupWizard
# /system/priv-app/SemcCalendar
# /system/priv-app/SemcClock
# /system/priv-app/SemcContactsProvider
# /system/priv-app/SemcTelephonyProvider
# /system/priv-app/Settings
# /system/priv-app/SettingsProvider
# /system/priv-app/Shell
# SimCotacts = services with "sdn" in names
# /system/priv-app/SimContacts
# /system/priv-app/StatementService
# /system/priv-app/SystemUI
# /system/priv-app/Tag
# /system/priv-app/TeleService
# /system/priv-app/Telecom
# /system/priv-app/WallpaperCropper
# /system/priv-app/sound-picker-release
# The end.

Thank you very much for the extensive guide and tests! Great job and good help for anyone interested in Sony's bloat
I personally focused myself on the running processes and services, searched for information about them and decompiled the strange ones, and then just hid the useless apks.
For anyone interested: freezing/disabling system apps will not prevent them from being launched and run, you need to uninstall them or hide them (which makes them unavailable to the Android system without deleting them, ready to be restored)

LolaPalocz said:
I've been doing a lot of debloating some weeks ago, mainly to try to decrease idle battery drain on my Z5 Compact (without much success...)
So I may share my understanding and sorting of system apks by topic and importance.
Click to expand...
Click to collapse
Did you encounter any problem with com.qualcomm.qti.tetherservice?
Sometimes, on reboot, i get cyclic crashing of this app, and Logcat shows that the problem lays on some uninstalled system apps (like crashmonitor or enterprise service) :
Bad call: specified package com.appname under uid 1000 but it is really -1
and then com.qualcomm.qti.tetherservice crashes because of:
SecurityException: com.appname was not granted this permission: android.permission.WRITE_SETTINGS
com.appname could be enterprise service or crashmonitor or other system apps uninstalled. They strangely seem to make qti tether app crash. Restoring one of them just makes the error trigger with another system app.

ninestarkoko said:
Did you encounter any problem with com.qualcomm.qti.tetherservice?.
Click to expand...
Click to collapse
No, it was may be among the packages I removed early, with the other Entreprise stuff.
I dont do any tethering, and I didnt encouter what you did, sorry.
Have you tried removing it ? Tethering may still work with the pure android stuff (like fingerprint still worked when I removed 2 or may be the 3 apk with fingerprint in their names).
I also checked in my archive of numerous logcats, and did not find any occurence of the string "com.appname" ...

LolaPalocz said:
I'm going to post the content of some input file to a script I execute in TWRP, which moves the apk listed in the non-commented lines (lines not starting with a #) in /system/__REMOVED/.
The current state of removed (lines starting with /) vs kept (lines starting with #) is what I consider safe and sane for now. But lots of # app can be removed without any side effects (see comments). It boots and works ok if you remove all the apks listed, except the ones in the latest 2 sections.
Click to expand...
Click to collapse
As some people requested it, here are the script and the files list.
Probably best to use it just after flashtool and fastboot flash boot+twrp, before first boot, but can be run anytime, even multiple times if you want to debloat progressively by uncommenting some lines.
In TWRP : Advanced > Terminal, then cd /externalsd/, and execute :
sh debloat.sh debloat.sane dry to see what the script would do
sh debloat.sh debloat.sane to actually move the apks into /system/__Removed/.
Forgot to say in my first post that it also removes the whole content of /oem/deletable-app/ and /oem/priv-app/ .

LolaPalocz said:
I also checked in my archive of numerous logcats, and did not find any occurence of the string "com.appname" ...
Click to expand...
Click to collapse
com.appname was a generic name for one of the system apps removed... however i'll try to remove Qti tether and see. thanks

LolaPalocz said:
As some people requested it, here are the script and the files list.
Probably best to use it just after flashtool and fastboot flash boot+twrp, before first boot, but can be run anytime, even multiple times if you want to debloat progressively by uncommenting some lines.
In TWRP : Advanced > Terminal, then cd /externalsd/, and execute :
sh debloat.sh debloat.sane dry to see what the script would do
sh debloat.sh debloat.sane to actually move the apks into /system/__Removed/.
Forgot to say in my first post that it also removes the whole content of /oem/deletable-app/ and /oem/priv-app/ .
Click to expand...
Click to collapse
Thanks for the scripts.
If I want to restore an apk I just move the apk back to its original place and reboot?
For some reason cant get it to work. Open Terminal but unable to cd to /externalsd/.
If not too much trouble could I ask you to upload it as a flashable script.zip?

Norup58 said:
Thanks for the scripts.
If I want to restore an apk I just move the apk back to its original place and reboot?
For some reason cant get it to work. Open Terminal but unable to cd to /externalsd/.
If not too much trouble could I ask you to upload it as a flashable script.zip?
Click to expand...
Click to collapse
Sorry, I dont know how to make flashable zips. And as TWRP is so nice and provides a shell (you can get it with 'adb shell' too, which is more confortable than the tiny keyboard and screen), you get more flexibility.
And it's ' cd /external_sd/ ' (with a _), where you'll find your external SD card.
And yes, to restore, you just move it back from /system/__Removed/ to its original place, and reboot.
You first have to mount /system (with twrp menu) read-write.
Also, an apk is actually in its own directory (with other stuff, libs, odex...), so we (the script, and you when you restore) are moving directories. So, if you vant to restore, you move the directory back.
Good luck.

LolaPalocz said:
Sorry, I dont know how to make flashable zips. And as TWRP is so nice and provides a shell (you can get it with 'adb shell' too, which is more confortable than the tiny keyboard and screen), you get more flexibility.
And it's ' cd /external_sd/ ' (with a _), where you'll find your external SD card.
And yes, to restore, you just move it back from /system/__Removed/ to its original place, and reboot.
You first have to mount /system (with twrp menu) read-write.
Also, an apk is actually in its own directory (with other stuff, libs, odex...), so we (the script, and you when you restore) are moving directories. So, if you vant to restore, you move the directory back.
Good luck.
Click to expand...
Click to collapse
Thanks again, got it to work....sort of....
In my case it was 'cd /sdcard/' and running the script via Minimal ADB gives a better overview :good:
Only 'issue' was the apks werent removed. Oh, they were 'backup' ok as your script said/does but had to manually deleted then afterwards. So guess to get best result one should run the script straight after 'SuperSU' has been flashed/installed (before any apks starts updating)- like you mentioned earlier

system/app/AnonymousData
system/app/ar-effect
system/app/BasicDreams
system/app/Chrome
system/app/com.sonyericsson.xhs
system/app/com.sonymobile.xperialounge.services
system/app/cover-widget
system/app/CrashMonitor
system/app/CrashMonitorSystem
system/app/DemoAppChecker
system/app/Drive
system/app/DualShockManager
system/app/ExactCalculator
system/app/experienceflow2livewallpaper-release
system/app/Exchange3Google
system/app/facebook-appmanager-xhdpi
system/app/Galaxy4
system/app/GetMoreClient-release
system/app/Gmail2
system/app/gmail-reader-service
system/app/GoogleLyricsPlugin
system/app/GoogleTTS
system/app/Hangouts
system/app/HTMLViewer
system/app/IddAgent
system/app/HoloSpiralWallpaper
system/app/Lifelog-googlePreloadLive-release-2.9.P.3.8-5377032
system/app/LiveWallpapers
system/app/LiveWallpapersPicker
system/app/Maps
system/app/Music2
system/app/NoiseField
system/app/PhaseBeam
system/app/phone-usage
system/app/Photos
system/app/photoslideshow-release
system/app/PhotoTable
system/app/PhotoWidget-release
system/app/RcaHandler
system/app/SemcWarrantyTime
system/app/sneiaccountmanager-live
system/app/support
system/app/SomcPOBox
system/app/StyleBlue-release
system/app/StyleBubble-release
system/app/StyleDaily-release
system/app/StylePaint-release
system/app/StyleRed-release
system/app/StyleStar-release
system/app/StyleSunshine-release
system/app/StyleSuntan-release
system/app/talkback
system/app/TopContactsWidget-release
system/app/TouchBlock
system/app/Videos
system/app/weather-release
system/app/WeatherWidget-release
system/app/WikipediaPlugin
system/app/WorldClockWidget-release
system/app/XperiaTransferMobile-release
system/app/YouTube
system/app/YouTubeKaraokePlugin
system/app/YouTubePlugin
system/etc/product
system/priv-app/ActiveClipper
system/priv-app/album-albumLive-release
system/priv-app/ArtFilterCamera-xhdpi-release
system/priv-app/com.mobisystems.fileman
system/priv-app/CoverApp
system/priv-app/DualCamera-xhdpi-release
system/priv-app/facebook-installer
system/priv-app/FaceFusionCamera-xhdpi-release
system/priv-app/GetMore-release
system/priv-app/livewaremanager
system/priv-app/MyXperia
system/priv-app/OnlineRemoteCamera-xhdpi-release
system/priv-app/RecommendationEngineExtension-release
system/priv-app/retaildemo
system/priv-app/SemcCamera3D-xhdpi-release
system/priv-app/SmallApp-Calculator-release
system/priv-app/SmallAppManagerService-release
system/priv-app/SmallAppsFramework-release
system/priv-app/SmallAppsLauncher-release
system/priv-app/SmallApp-Timer-release
system/priv-app/SmallAppWidget-release
system/priv-app/SnpVUStore
system/priv-app/somc-get-to-know-it-release
system/priv-app/SomcPhotoAnalyzer
system/priv-app/sonyentrance2-release
system/priv-app/SoundPhotoCamera-xhdpi-release
system/priv-app/StylePortrait
system/priv-app/textinput-chn-xhdpi
system/priv-app/UpdateCenter-release
system/priv-app/usb-mtp-backup-transport
system/priv-app/usb-mtp-factoryreset-wrapper
system/priv-app/usb-mtp-fotaupdate-wrapper
system/priv-app/usb-mtp-update-wrapper
system/priv-app/usb-mtp-vendor-extension-service
system/priv-app/Velvet

LolaPalocz said:
As some people requested it, here are the script and the files list.
Probably best to use it just after flashtool and fastboot flash boot+twrp, before first boot, but can be run anytime, even multiple times if you want to debloat progressively by uncommenting some lines.
In TWRP : Advanced > Terminal, then cd /externalsd/, and execute :
sh debloat.sh debloat.sane dry to see what the script would do
sh debloat.sh debloat.sane to actually move the apks into /system/__Removed/.
Forgot to say in my first post that it also removes the whole content of /oem/deletable-app/ and /oem/priv-app/ .
Click to expand...
Click to collapse
Greetings,
the script works perfect!
Is it possible to make a script for the new firmware .224 ?
Thanks in advance.

greg.chalk said:
Is it possible to make a script for the new firmware .224 ?
Click to expand...
Click to collapse
Here it is (changes from .185 to .224 described at the beginning of the list file).

LolaPalocz said:
Here it is (changes from .185 to .224 described at the beginning of the list file).
Click to expand...
Click to collapse
That works nice on Z3+/Z4 with 224 FW

LolaPalocz said:
Here it is (changes from .185 to .224 described at the beginning of the list file).
Click to expand...
Click to collapse
Thank you very much for your effort

LolaPalocz said:
Here it is (changes from .185 to .224 described at the beginning of the list file).
Click to expand...
Click to collapse
After testing the script, everything works perfectly.
Just one last question: is it possible to disable or delete with the script "suggested apps"?
Also, maybe it's a good idea to make a new specific thread for this script so even more people be able to find it.

greg.chalk said:
Just one last question: is it possible to disable or delete with the script "suggested apps"?
Click to expand...
Click to collapse
If you mean the list of recent opened apps on the side of the drawer, it's part of the launcher (/system/app/home-release), and you don't want to remove the launcher : ) , so no.
(It would need hacking this package - there are other threads about modded sony home to install and replace this one - dunno if there is one with this removed).
greg.chalk said:
Also, maybe it's a good idea to make a new specific thread for this script so even more people be able to find it.
Click to expand...
Click to collapse
Well, I like it here : ) The real added value is the list of packages, sorted by importance and categories, with comments. So people can go edit it by hands and decide for themselves what they need. The script is just a side effect : )

Is it possible to make a script for the new firmware .253?

toncheee said:
Is it possible to make a script for the new firmware .253?
Click to expand...
Click to collapse
I wont have the time to check .253 soon.
But the script and the file list for .224 will most probably work with .253.
There was a few changes between .185 (Android 6.0) and .224 (Android 6.0.1), but as .253 is still Android 6.0.1, Sony may not have changed many .apk filenames, possibly none.
You may execute the script with the option "dry" to see what would be removed. If you see any line starting with "?" instead of "dry", the apk was not found and Sony may have renamed (or just removed) it. Please tell us.

[SCRIPT][TOOL] ADitor - Easily edit your Hosts file

ADitor
We all know what AdBlock is, how its done and how it works.
The purpose of this script is to let you easily edit your /system/etc/hosts file that contains host sites or whatever they're called, either you can add one or remove one.
What we need:
Terminal Emulator or adb shell or anything that has a shell
Busybox
Root
How to use:
Copy the file to /system/bin or /system/xbin
Set permissions to 'rwxr-xr-x'
Go to Terminal Emulator
Then su
Then this one:
Code:
usage: aditor [-r] <host>
aditor [-r] <host> <hosts file dir>
-r Unblock site
Example:
To block a site:
Code:
aditor adfl.ly
To unblock:
Code:
aditor -r adfl.ly
DOWNLOAD IN AFH

reserved

Nice one.
Since I access XDA too much (sometimes), I may use it along with Tasker to block the forum lol.

#Henkate said:
Nice one.
Since I access XDA too much (sometimes), I may use it along with Tasker to block the forum lol.
Click to expand...
Click to collapse
Lol. Actually, I've accidentally done that when I made this :laugh:

Nice script, I'll use it when I'm study with Tasker

How To Guide Editing HOST file

DISCLAIMER: I WAS NEVER, HAVE NEVER BEEN, AND WILL NEVER BE RESPONSIBLE OF ANY DAMAGES AGAINST YOUR DEVICES BY YOUR OWN MIS-OPERATIONS​
Code:
# knox_bit_warranty:0x1
#
# Your warranty is now void
#
# You have been warned.
#
# I will laught at you if you point the finger at me.
Hello everyone, in this guide I will be showing you how to edit android HOST file. There will be more methods in this guide, make sure you have allready unlocked the OEM and have installed root_privlages
Unlocking the bootloader and rooting
DISCLAIMER: I WAS NEVER, HAVE NEVER BEEN, AND WILL NEVER BE RESPONSIBLE OF ANY DAMAGES AGAINST YOUR DEVICES BY YOUR OWN MIS-OPERATIONS # knox_bit_warranty:0x1 # # Your warranty is now void # # You have been warned. # # I will laught at you if you...
forum.xda-developers.com
I will be updateing this guide regulary so make sure to chek it.
FIRST METHOD​
First method is by useing Android Debugging Bridge (ADB). Make sure you SDK platform tools ready on your pc.
1. Open a terminal window in the install folder of platform tools.
2. Pull the hosts file out of the phone to your PC
Code:
adb pull /system/etc/hosts C:\platform-tools
Ofcourse you can change the location of where you want the fille to be pulled to.
3. Once you have pulled the hosts file to the desired location you can edit it. I will share my hosts file I use on my PC, you can take stuff frome there and integrated it in to yours. But don't put #, " and usles text, It will not like it.
4. After you have edited the host file to your needs, you need to send it back to your phone.
Code:
adb shell
su
mount -o rw,remount /system
adb push C:\platform-tools\hosts /system/etc/
After you type SU a prompt for root_privlages will apear on your phone, allow the shell to have root_privlages. mount -o rw,remount /system will disable SYSTEM on READ_ONLY
5. After pushing the HOSTS file to your phone put SYSTEM back to READ_ONLY
Code:
mount -o ro,remount /system
6. Enoy.
SECONED METHOD​
Doesn't require root but requires TWRP to be installed.
1. You will need SDK platform tools
2. Open a terminal windows in the install folder of platform tools.
3. Pull the HOST file from the phone
Code:
adb pull /system/etc/hosts C:\platform-tools
Ofcourse you can change the location of where you want the fille to be pulled to.
4. Once you have pulled the hosts file to the desired location you can edit it. I will share my hosts file I use on my PC, you can take stuff frome there and integrated it in to yours. But don't put #, " and usles text, It will not like it.
5. Transfer your version of the HOSTS file to your sd_card, either by file explorer or ADB
Code:
adb push C:\platform-tools\hosts /sdcard
6. Boot in to TWRP and tap on mount, uncheck the option SYSTEM PARTITIONS ON READ_ONLY
7. Once READ_ONLY is disabled on SYSTEM partition go in to advanced then in to file manager. Copy your hosts file from external_sd card to system\etc\
8. Reboot and enoy.
THIRD METHOD​
Requires SDK platform tools and root_privlages
1. Open terminal window in install folder
2. Run shell with super user
Code:
adb shell
su
You will get a pop up on your phone for shell asking root_premisions you want to click allow.
3. Remount system and get in to folder of host file
Code:
remount system
cd system
cd etc
4. Display the host file in terminal window
Code:
cat hosts
5. Manualy edit host file, this is with a example ip
Code:
echo "127.0.0.1 google.com" >> hosts
6. You should see this now after running cat hosts
Code:
127.0.0.1 localhost
::1 ip6-localhost
127.0.0.1 google.com
7. Exit shell by typing exit
FOURTH METHOD​
Useing a app on your phone which is the easiest way. Requires root_privlages.
Wount be writeing that, I will link a video that will show you how to do it.
Credits goes to him for that video.
FIFTH METHOD​
You can use a terminal emulator app on your phone and manualy do everything, same as THIRD METHOD.
Requires root_privlages
LINKS:
Unlocking the bootloader and rooting
DISCLAIMER: I WAS NEVER, HAVE NEVER BEEN, AND WILL NEVER BE RESPONSIBLE OF ANY DAMAGES AGAINST YOUR DEVICES BY YOUR OWN MIS-OPERATIONS # knox_bit_warranty:0x1 # # Your warranty is now void # # You have been warned. # # I will laught at you if you...
forum.xda-developers.com
Installing TWRP and LInageOS
DISCLAIMER: I WAS NEVER, HAVE NEVER BEEN, AND WILL NEVER BE RESPONSIBLE OF ANY DAMAGES AGAINST YOUR DEVICES BY YOUR OWN MIS-OPERATIONS # knox_bit_warranty:0x1 # # Your warranty is now void # # You have been warned. # # I will laught at you if you...
forum.xda-developers.com
SDK Platform Tools release notes | Android Studio | Android Developers
Android SDK Platform-Tools is a component for the Android SDK.
developer.android.com

what are bloat ips and how do i add?
also how much of the host file is necessary

Seems the solution is not working for me,
I'm on Android 11 and it seems I cannot remount because I need to disable dm-verity first.
But when I run adb disable-verity, I got following error:
Code:
verity cannot be disabled/enabled - USER build
Any idea how to make it work?

LAST_krypton said:
DISCLAIMER: I WAS NEVER, HAVE NEVER BEEN, AND WILL NEVER BE RESPONSIBLE OF ANY DAMAGES AGAINST YOUR DEVICES BY YOUR OWN MIS-OPERATIONS​
Code:
# knox_bit_warranty:0x1
#
# Your warranty is now void
#
# You have been warned.
#
# I will laught at you if you point the finger at me.
Hello everyone, in this guide I will be showing you how to edit android HOST file. There will be more methods in this guide, make sure you have allready unlocked the OEM and have installed root_privlages
Unlocking the bootloader and rooting
DISCLAIMER: I WAS NEVER, HAVE NEVER BEEN, AND WILL NEVER BE RESPONSIBLE OF ANY DAMAGES AGAINST YOUR DEVICES BY YOUR OWN MIS-OPERATIONS # knox_bit_warranty:0x1 # # Your warranty is now void # # You have been warned. # # I will laught at you if you...
forum.xda-developers.com
I will be updateing this guide regulary so make sure to chek it.
FIRST METHOD​
First method is by useing Android Debugging Bridge (ADB). Make sure you SDK platform tools ready on your pc.
1. Open a terminal window in the install folder of platform tools.
2. Pull the hosts file out of the phone to your PC
Code:
adb pull /system/etc/hosts C:\platform-tools
Ofcourse you can change the location of where you want the fille to be pulled to.
3. Once you have pulled the hosts file to the desired location you can edit it. I will share my hosts file I use on my PC, you can take stuff frome there and integrated it in to yours. But don't put #, " and usles text, It will not like it.
4. After you have edited the host file to your needs, you need to send it back to your phone.
Code:
adb shell
su
mount -o rw,remount /system
adb push C:\platform-tools\hosts /system/etc/
After you type SU a prompt for root_privlages will apear on your phone, allow the shell to have root_privlages. mount -o rw,remount /system will disable SYSTEM on READ_ONLY
5. After pushing the HOSTS file to your phone put SYSTEM back to READ_ONLY
Code:
mount -o ro,remount /system
6. Enoy.
SECONED METHOD​
Doesn't require root but requires TWRP to be installed.
1. You will need SDK platform tools
2. Open a terminal windows in the install folder of platform tools.
3. Pull the HOST file from the phone
Code:
adb pull /system/etc/hosts C:\platform-tools
Ofcourse you can change the location of where you want the fille to be pulled to.
4. Once you have pulled the hosts file to the desired location you can edit it. I will share my hosts file I use on my PC, you can take stuff frome there and integrated it in to yours. But don't put #, " and usles text, It will not like it.
5. Transfer your version of the HOSTS file to your sd_card, either by file explorer or ADB
Code:
adb push C:\platform-tools\hosts /sdcard
6. Boot in to TWRP and tap on mount, uncheck the option SYSTEM PARTITIONS ON READ_ONLY
7. Once READ_ONLY is disabled on SYSTEM partition go in to advanced then in to file manager. Copy your hosts file from external_sd card to system\etc\
8. Reboot and enoy.
THIRD METHOD​
Requires SDK platform tools and root_privlages
1. Open terminal window in install folder
2. Run shell with super user
Code:
adb shell
su
You will get a pop up on your phone for shell asking root_premisions you want to click allow.
3. Remount system and get in to folder of host file
Code:
remount system
cd system
cd etc
4. Display the host file in terminal window
Code:
cat hosts
5. Manualy edit host file, this is with a example ip
Code:
echo "127.0.0.1 google.com" >> hosts
6. You should see this now after running cat hosts
Code:
127.0.0.1 localhost
::1 ip6-localhost
127.0.0.1 google.com
7. Exit shell by typing exit
FOURTH METHOD​
Useing a app on your phone which is the easiest way. Requires root_privlages.
Wount be writeing that, I will link a video that will show you how to do it.
Credits goes to him for that video.
FIFTH METHOD​
You can use a terminal emulator app on your phone and manualy do everything, same as THIRD METHOD.
Requires root_privlages
LINKS:
Unlocking the bootloader and rooting
DISCLAIMER: I WAS NEVER, HAVE NEVER BEEN, AND WILL NEVER BE RESPONSIBLE OF ANY DAMAGES AGAINST YOUR DEVICES BY YOUR OWN MIS-OPERATIONS # knox_bit_warranty:0x1 # # Your warranty is now void # # You have been warned. # # I will laught at you if you...
forum.xda-developers.com
Installing TWRP and LInageOS
DISCLAIMER: I WAS NEVER, HAVE NEVER BEEN, AND WILL NEVER BE RESPONSIBLE OF ANY DAMAGES AGAINST YOUR DEVICES BY YOUR OWN MIS-OPERATIONS # knox_bit_warranty:0x1 # # Your warranty is now void # # You have been warned. # # I will laught at you if you...
forum.xda-developers.com
SDK Platform Tools release notes | Android Studio | Android Developers
Android SDK Platform-Tools is a component for the Android SDK.
developer.android.com
Click to expand...
Click to collapse
Thanks, I will be thankfully glad that I seccseed, Fir 1st Method via twrp recovery>file terminal,mount system>file maneger>cd /system/host/etc, but Ihave lost the host of the host refer to gms [email protected]#$# auto update, someone has made that in past and now a days the battery work by the rulz of android 9 eco system

great write up, third method worked for me on Android 12 with root.

tealtadpole said:
Seems the solution is not working for me,
I'm on Android 11 and it seems I cannot remount because I need to disable dm-verity first.
But when I run adb disable-verity, I got following error:
Code:
verity cannot be disabled/enabled - USER build
Any idea how to make it work?
Click to expand...
Click to collapse
the easiest way is to get and use a vndklite image.
you can google: "vndklite vs vndk" to learn more about it.
here it is from Google for a head start: https://source.android.com/docs/core/architecture/vndk

I cannot solve my one issue and very dipressed, I highly for you to see the given link and plz replay me for my Issue.