Database Info

[TOOL][BIN]BusyBox Recovery Flashable Zips **ALL-ARCHS**

Update 14-Jul/18: Busybox v1.29.0 released (Complete changelog: here)
Hello XDA,
All the flashable zips include two builds.
SELinux Enabled and Normal
This post will give you a pretty good idea about the difference.
There are 401 applets included in the normal and 413 applets included in the selinux build.
Here's a list for the same.
NOTE: Installing busybox does not modify your device's selinux status.
Architectures supported: arm, arm64, x86, x86_64, mipsel, mips64el and mipseb.
The attached zips install busybox in one of /magisk/bbxyds, [/data/adb]/su/xbin, /system/xbin, [/system]/vendor/bin after cleaning older busybox binaries and their symlinks from the device (if any).
Universal busybox installer flashable zip detects the architecture and installs busybox accordingly.
Code for mounting the su.img and running in embedded mode is borrowed from the SuperSU project.​
SELinux status is automatically detected by the installers.
Behaviour of all the installers as well as the cleaner can be manipulated using a bbx.conf file which should be placed in one of /sdcard, /data or /cache. For more details refer to the second post.
TWRP recovery or Flashfire is recommended for flashing the attached installers, however the code is pretty generic and should work on other recoveries too.
Projects using my BusyBox builds are:
Open Gapps
Apps2SD
Project Skynet
StØck ROM Sense 5 by @denkem
Stock Debloated roms for nexus 5, 6, 5x and 6p by @tupac4u
Inlightning Org
Universal SafetyNet Fix by @Deic
If you would like to include my builds in your project, a link to this thread in the project thread would be expected.
Also, if you can, pm me about it so I can add the name to this list.
Credits:
@7175 for his thread
@bovirus @Chinaboy5216 @skulldreamz for testing and reporting
XDA for...do I need to say it
Disclaimer: Neither me nor anyone else at XDA is responsible for what happens to your device. Please use the tools/utilites attached at your own discretion.
Having said that, I'll try my best to help you with any bugs or exceptions you might face.​
Download: Click here
Mirror: Sourceforge​
Busybox-CLEANER.zip and all the installers clean BusyBox in /su/xbin /data/adb/su/xbin /system/xbin /system/vendor/bin /vendor/bin /data/adb/su/bin /system/bin /su/bin /magisk/phh/bin /su/xbin_bind /data/adb/su/xbin_bind and /magisk/bbxyds
The installers will automatically detect 32/64 bit arch and install the appropriate binary
NOTE: If FlashFire gets stuck on a black screen or errors out when flashing, please flash from recovery instead. (There seems to be a /system mounting issue on some devices in FlashFire)
File list:
Busybox-<VERSION>-YDS-UNIVERSAL.zip
Flashable zip compatible with all architectures.
Busybox-<VERSION>-YDS-<ARCHITECTURE>.zip
Architecture specific flashable zip files.
Busybox-<VERSION>-YDS-<ARCHITECTURE>.tgz
Consists of pre-compiled busybox binaries.
Not flashable
Busybox-installer-<ARCHITECTURE>.bin
Executable files for installing busybox without rebooting in recovery mode. See 2nd post for more details.
Not flashable
Source code (zip, tar.gz)
Source code files automatically generated via Github releases.
Not flashable
For older versions refer to my androidfilehost, drive, mediafire or sourceforge folders.
Toolchains used for building these binaries can be found here (host arch -> x86_64).
For official busybox source and changelog refer here.
Do report how these work out for you, as most of the testing has been done on emulators.
You can request any applet in this thread. If it does not affect the size of the whole binary or there are enough users backing it, I'll add it in the next release.
When reporting please attach the BusyBox-YDS-installer.log, it should be in either /sdcard, /data or /cache.
Source:
https://github.com/yashdsaraf/busybox
https://sourceforge.net/p/busybox-yds/code

Op
bbx.conf:
Allowed options in bbx.conf are,
installdir=<path>
Change the directory for installing busybox to <path>. If <path> is not a valid directory, then the installer will fall back to the default installation directory.
Note: Any older busybox installation in the supplied directory will be cleaned.
Warning: Please use this option only if you are absolutely sure about what you are doing.
e.g installdir=/data/local/xbin
​
selinux=[0|1]
Controls the selinux support in busybox.
E.g To disable SELinux support
Code:
selinux=0
To enable SELinux support
Code:
selinux=1
​
noclean
If supplied, the installers will skip cleaning any previous busybox installations.​Sample:
To install busybox in /data/local/xbin without cleaning previous busybox installations with SELinux support enabled, following would be a valid bbx.conf file
Code:
installdir=/data/local/xbin
noclean
selinux=1
Note: Busybox cleaner only reads the installdir option and cleans busybox in that directory
Self extracting executables:
All the .bin files in the download link in the above post are self extracting executables. They can install busybox directly from a terminal without rebooting in recovery.
Usage:
Install any terminal app.
Get root privileges,
Code:
su
E.g if you have the installer for ARM downloaded in sdcard, run this
in the terminal,
Code:
sh /sdcard/Busybox-installer-arm.bin
And watch the magic happen.
Options:
-h | --help
Show help message.​ -i | --interactive
Run script in interactive mode.​-nc | --noclean
Do not clean previous busybox installation(s) (IF ANY).​-oc | --onlyclean
Clean previous busybox installation(s) (IF ANY) and exit.​ If supplied, all other options are ignored except installdir.​--selinux=[es|o]
Enable or disable selinux support in busybox.​--installdir=<path>
Install busybox in <path>.​Tip: To clean busybox in a custom directory, run the installer in onlyclean mode and set installdir to the custom directory which needs to be cleaned.
e.g. to clean busybox in /data/local/xbin run the installer as
Code:
sh <script_name> -oc --installdir=/data/local/xbin

@YashdSaraf
Thanks for new thread
"[TOOL][BIN]busybox flashable for all architecture via recovery"
I will remove "Latest" and add info that is flashable via recovery.
I will change the thread title in

Nice work .
Keep it up !!!
Sent from my E2303 using XDA Free mobile app

bovirus said:
..Thanks for new thread....
Click to expand...
Click to collapse
is the issue mentioned here addressed? @YashdSaraf, hope you read my pm.

@YashdSaraf had a quick question. I have been using your busybox zips since you've staying building and i first want to say thank you. My question is when i use the busybox unistaller zip or busybox cleaner with your zip it says that it removes 0 symlinks and when i use stericson busybox zip it says that I'm removing 3xx plus symlinks. I was just wondering wondering why his and osmosis show that binaries were symlinked and yours showed that 0 were? I want to lastly say though that your zip worked and busybox was installed and worked correctly. I like some of the extra binaries yours offers do just a curious question thanks.
Sent from my Nexus 6P using Tapatalk

m0han said:
is the issue mentioned here addressed? @YashdSaraf, hope you read my pm.
Click to expand...
Click to collapse
I did, I'm sorry I was too busy switching to a new OS. Anyways, I've got a couple of ideas over what might've gone wrong. I'll pm you the updated installers as soon as I'm done for testing. :good:
skulldreamz said:
@YashdSaraf had a quick question. I have been using your busybox zips since you've staying building and i first want to say thank you. My question is when i use the busybox unistaller zip or busybox cleaner with your zip it says that it removes 0 symlinks and when i use stericson busybox zip it says that I'm removing 3xx plus symlinks. I was just wondering wondering why his and osmosis show that binaries were symlinked and yours showed that 0 were? I want to lastly say though that your zip worked and busybox was installed and worked correctly. I like some of the extra binaries yours offers do just a curious question thanks.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
I did not update the uninstaller after systemless root was introduced so it must be looking only in the /system partition for busybox. I'll upload the updated uninstaller today.
Thanks for your support.

YashdSaraf said:
.....I'll pm you the updated installers as soon as I'm done for testing.....
I did not update the uninstaller after systemless root was introduced....
. I'll upload the updated uninstaller today.......
Click to expand...
Click to collapse
got your pm. will test the updated installer and revert by pm.
is this 'the updated uninstaller'? can this be used in 'any setup'?

m0han said:
got your pm. will test the updated installer and revert by pm.
is this 'the updated uninstaller'? can this be used in 'any setup'?
Click to expand...
Click to collapse
Yes the one attached in the OP is the latest one. It will clean busybox in /system/bin, /system/xbin, /su/bin, /su/xbin.
So yeah it can be used in 'any setup'.:good:

@YashdSaraf
Are there any news about busybox for ARM and 64boit Android SO (like 5.1.)?

YashdSaraf said:
.....I'll pm you the updated installer......
Click to expand...
Click to collapse
...will test the updated installer and revert .....
your zip worked well, i think. thanks.

86_64 for zenfone 2 Z00A?

@YashdSaraf
Thanks for sharing mate. really appreciated. :good:
PM sent
Cheers,
UITA

@YashdSaraf
thanks for your busybox.
I had some problems to install it (I tried arm/arm64/all zip file withS elinux).
Every time the installation end with error "Wrong architecture".
My build propri content about cpu is
# ro.product.cpu.abi and ro.product.cpu.abi2 are obsolete,
# use ro.product.cpu.abilist instead.
ro.product.cpu.abi=arm64-v8a
ro.product.cpu.abilist=arm64-v8a,armeabi-v7a,armeabi
ro.product.cpu.abilist32=armeabi-v7a,armeabi
ro.product.cpu.abilist64=arm64-v8a
To install I had to use previous zip file (1.24.1) where you not have archictecture check and replace 1.24.1. busybox with busybox extracted by 1.24.2 zip.
Where can i get the error log of your script? It show just only /data...
Please check your script.
Thanks.

@YashdSaraf Could you update busybox to 1.24.2?

@exodius48
All busybox files in first post are version 1.24.2.
@YashdSaraf
Please add a note in first post about the vesrion of busybox.

bovirus said:
@exodius48
All busybox files in first post are version 1.24.2.
Click to expand...
Click to collapse
Sorry for asked it. I couldn't find busybox version on 1st post, also on the tittle.

@exodius48
In the first post there are various Download links with all busybox for all platforms.

OK... the BusyBox app on the play store had an update to 1.24.2.
When I install the update from 1.24.1 to 1.24.2, it states that it installed successfully, it doesn't reflect it.
It still shows that 1.24.1 is installed.
I tried wiping the dalvik cache before and after as well as reinstalling the app and it still reflects 1.24.1.
Also, it displays that 1.24.2 will be installed in the system xbin but, doesn't.
Thank you.

bovirus said:
@YashdSaraf
thanks for your busybox.
I had some problems to install it (I tried arm/arm64/all zip file withS elinux).
Every time the installation end with error "Wrong architecture".
My build propri content about cpu is
# ro.product.cpu.abi and ro.product.cpu.abi2 are obsolete,
# use ro.product.cpu.abilist instead.
ro.product.cpu.abi=arm64-v8a
ro.product.cpu.abilist=arm64-v8a,armeabi-v7a,armeabi
ro.product.cpu.abilist32=armeabi-v7a,armeabi
ro.product.cpu.abilist64=arm64-v8a
To install I had to use previous zip file (1.24.1) where you not have archictecture check and replace 1.24.1. busybox with busybox extracted by 1.24.2 zip.
Where can i get the error log of your script? It show just only /data...
Please check your script.
Thanks.
Click to expand...
Click to collapse
Hey,
I think the reason for failure was that the script could not detect the /data partition.
Please try these zips instead.
arm arm64
There should be a BusyBox-YDS-installer.log in either /sdcard, /data or /cache, whichever your device supports.
Do attach it when reporting back.:good:
Ibuprophen said:
OK... the BusyBox app on the play store had an update to 1.24.2.
When I install the update from 1.24.1 to 1.24.2, it states that it installed successfully, it doesn't reflect it.
It still shows that 1.24.1 is installed.
I tried wiping the dalvik cache before and after as well as reinstalling the app and it still reflects 1.24.1.
Also, it displays that 1.24.2 will be installed in the system xbin but, doesn't.
Thank you.
Click to expand...
Click to collapse
I'm not sure what are you talking about. I'm not related whatsoever to any play store busybox installer apps. Try one of the installers from the op to install 1.24.2 busybox.

[G925F/FD/W8/...][6.0+] SYSTEMLESS DevBase | Encryption support | Stock OTA updates

SYSTEMLESS DevBase has been developed and physically tested on S7 Edge (G935F), so main thread containing the most detailed description you can find here:
>> [SAMSUNG][6.0+] SYSTEMLESS DevBase | Encryption support | Stock OTA updates <<
However, it should work on ALL SAMSUNG DEVICES running Android 6.0+, so if you are Galaxy S6 Edge (G925xx) owner - please place your feedback & discussion here to let me know about device-specific issues or to let me know that everything works perfect
---------------------------------------------------------------------------
Are you tired with traditional custom ROMs?
Do you miss custom ROMs but you would like to have encrypted /data (for privacy/security reasons)?
You are in the right place! I present you SYSTEMLESS DevBase - an SYSTEMLESS equivalent of my previous work (for older devices)
Prerequisites:
- Samsung device running stock or stock-based Android 6.0+ (mandatory!)
- Rooted device - SuperSU v2.76+ installed in SYSTEMLESS mode (mandatory!) (*)
- Stock, untouched /system partition (not mandatory, but recommended for working OTA)
- Stock recovery (not mandatory, but recommended for working OTA)
(*) NOTE: The latest CF-Auto-Root image for G925F contains SuperSU v2.74 which does not support SYSTEMLESS solutions (su.d is not triggered early enough). It is NOT enough to update it via PlayStore to the newest version and update su binaries! You need to update it using TWRP / FlashFire installable ZIP from THIS STABLE or THIS BETA thread. Alternatively you can use "EverRoot" -> "Inject SuperSU" option in FlashFire even if you are rooted already by CF-Auto-Root (it will update SuperSU in the same way as flashing ZIP).
SYSTEMLESS DevBase:
1. Benefits / main features:
- Works with encypted /data partition
- Working official OTA updates! (see Tips & Tricks)
- Does NOT perform any phisical modifications in /system
- Does NOT perform any additional changes/patches to the kernel
- Removed KNOX warnings (systemlessly removed SecurityLogAgent)
- It contains SYSTEMLESS BusyBox (bionic, the most stable and respected release)
- It allows you to easily modify most of files & apps in your /system - SYSTEMLESSLY (see Tips & Tricks)
- It does not interfere with Magisk! You can use Magisk in paralell with SYSTEMLESS DevBase if you need it for your favorite module.
2. Systemless Safe De-Bloat (more info below):
What does it mean and why is it called "safe"?
- ONLY apps available in stores will be systemlessly removed from the ROM, so you can easily (re)install any of these app if you like
- ONLY pre-installed system apps are will be systemlessly removed, DevBase installer never touch any updated app nor app installed manually from store
Thus, the following conclusions can be drawn:
1. If you install my SYSTEMLESS DevBase directly over working stock ROM - in most cases almost all these apps will remain untouched, because almost all apps have been updated already (stored on /data). But then you will be able to remove any useless app using the "Application manager" -> [Name_Of_App_To_Remove] -> MORE -> Uninstall updates. NOTE: App will disappear arter reboot and will be visible even in Titanium Backup!
2. If you perform "Wipe data" directly before installing SuperSU and my SYSTEMLESS DevBase (before you let to install app's updates) - then all apps listed below will be removed. If you would like to use any of these apps - just install it manually from appropriate store. Installed manually app will not be removed during the next DevBase update or re-install.
Removed apps list (depends on the device, should cover all devices starting from Galaxy S5):
ChatON
Chrome
Drive
Dropbox
EditorsDocs
Evernote
Excel
Facebook
FB Messenger
FB Pages Manager
Flipboard
Google+ / Photos
Group Play
Hangouts
Instagram
OneDrive
OneNote
PEN.UP
Play Books
Play Games
Play Movies
Play Music
Play Newsstand
PowerPoint
Skype
Smart Remote
WhatsApp
Word
NEW! Safe De-Bloat feature automatically detects and systemlessly removes apps not listed above, but present in your CSC package
3. Systemless CscFeature MOD (enabled some built-in, hidden features):
- Added shutter sound menu in Camera app
- Sending/receiving MMS without data on
- Show SMS/MMS sending time instead of receiving
- Added "Exit Internet" option to stock browser
- Added call button in Phone Logs (**)
- Added "Call/Message block" option in Settings
- Added symbols as secondary keys in Samsung keyboard (**)
- Call Recording (manual control, added "Record" button)
(**) may not work starting from Android 7.0 Nougat
Installation:
1. FlashFire app (recommended ***):
- Open file using "Flash ZIP or OTA" option
- UNTICK "Mount /system read/write" [extremely important for working OTA!]
- Enable "EverRoot" -> "Inject SuperSU" option if necessary (see NOTE above (*))
- Tap "FLASH"
2. TWRP recovery:
- Tap "Keep Read Only" on the Welcome screen [extremely important for working OTA!]
- Open file using "Install" option (use extSdCard or OTG storage in case of encrypted /data)
- Confirm flash by swiping right
- Tap "Reboot System"
NOTE1: One additional auto-reboot may be performed at first boot. It is not a bug (may be required for systemless build.prop support - see Tips & Tricks for more explanations)
NOTE2: Do not worry about red "mount /data failed..." messages displayed in TWRP in case of encrypted /data (installer will do the work anyway!)
(***) As far as I know - FlashFire is the only flashing tool with full access to /data during flash in case of encrypted devices. It is also the only tool which allows you to perform full backup/restore of partitions, including encrypted /data. It does NOT require custom recovery to work!
Credits: @Chainfire for systemless SuperSU and a lot of inspiration
Hit Thanks button if you like my work. If you really appreciate my work - feel free to buy me a beer

Download
>> Recent SYSTEMLESS DevBase <<
Note:
Check MD5 sum BEFORE flash (useful TOOL), because flashing damaged or incomplete ZIP files can lead to issues! Correct MD5 sum is shown on the AndroidFileHost website while downloading.
Changelog
Please visit MAIN THREAD - post #3

Tips & Tricks
1. OTA updates:
- Basically, the only thing you need to take OTA update is to perform "Full unroot" in the SuperSU app. However, a better way is to use "unroot2ota" terminal command, because this will not remove DevBase boot script from /su/su.d and the only thing you will need to re-activate SYSTEMLESS DevBase (and all your systemless MODs) after performing OTA update is just re-root your device with CF-Auto-Root.
- If you flashed custom recovery like TWRP - it is mandatory to restore your stock recovery (otherwise OTA will not work). You can do it using FlashFire app (the easiest way) - just open recovery.img file (extracted from your original FW) using "Flash firmware package" option, disable "Preserve recovery" option and then tap "FLASH". EDIT: Starting from version v1.2 there is a new "unroot2ota" feature which allow you to restore stock recovery using /system/recovery-fromm-boot.p file. There is no guarantee to perform it successfully (even if there is no error message) but in most cases it works well (tested on Nougat beta). Please go to recovery before you try to get OTA to check if you have stock recovery already after performing "unroot2ota" (if not - you need to use PC Odin to flash recovery.img packed in tar file).
- It is recommended to temporarily disable "Auto-update apps" in Play Store settings before you unroot your device. It will prevent updating applications covered by Safe De-Bloat list, as there apps will temporarily appear until you re-root the phone after performing OTA update.
Note (devices which use dm-verity): You should never allow /system modifications in TWRP, never allow to remount /system r/w in any app (e.g. Root Explorer, FlashFire, etc.) and never flash a ZIP file which could modify your /system or remount it r/w. Failure to follow these recommendations will break dm-verity verification and will cause, that your device may not be able to boot with the stock kernel (you will need to re-flash your original FW using PC Odin to make your device bootable).
2. Making your own modifications:
- You can systemlessly replace any existing system app by modded one. Just put modified app to /data/devbase/system/app or /data/devbase/system/priv-app and then reboot your device
- You can systemlessly replace jar or apk in /system/framework. Just put modified one to /data/devbase/system/framework and then reboot your device (NOTE: framework support has been added for advanced users -> there is high risk of bootloop if you do something wrong!)
- You can systemlessly add or override any line in /system/build.prop. Just put (only new or changed) line to /data/devbase/system/build.prop and then reboot your device (NOTE: one additional auto-reboot will be performed if /data/devbase/system/build.prop file has been added, modified or removed. It is not a bug - it is required for the changes in /data/devbase/system/build.prop to take effect!)
- You can systemlessly replace any existing file in /system/csc and /system/etc (but NOT in subdirectories). Just put modified copy of a file to /data/devbase/system/csc or /data/devbase/system/etc and then reboot device
Limitations: original app or file MUST physically exist with the same name in /system, you can NOT add a new app or file this way!
Example 1 (Ad-Blocking): Download the latest Ad-Blocking ZIP installer from THIS thread. Extract "hosts" file (placed in /system/etc inside ZIP file), then copy it to /data/devbase/system/etc, set rw-r--r-- (644) permissions and then reboot device
Example 2 (modded SystemUI): Create "SystemUI" directory in /data/devbase/system/priv-app and then put modified "SystemUI.apk" file into it. Set rwxr-xr-x (755) permissions to "SystemUI" directory, rw-r--r-- (644) permissions to "SystemUI.apk" and then reboot device
Example 3 (De-Bloating a bit more): You can just create empty directories in /data/devbase/system/app (or priv-app) corresponding to applications in /system/app (or priv-app). Alternatively (more advanced method), you can add an app to modded enforceskippingpackages.txt file (you can find it in /data/devbase/system/etc or /data/devbase/system/csc_contents, depending on the original location in /system) and increase number in the 1st line. Second method should not be used by beginners (without a basic knowledge related to UNIX text format)
3. How to manually maintain the newest ROM version:
If you do not care about OTA - you can manually update your device to the newest ROM available @ Sammobile, keeping your original CSC (you need multi-file original FW, I mean separate files for BL/AP/CP/CSC). You need to download 2 ROMs: ROM with the newest changelist and the latest ROM containing your original CSC. Extract both and open in PC Odin BL/AP/CP files from the ROM with highest changelist but open CSC file from the ROM containing your CSC (I recommend to use HOME_CSC_* file to avoid auto-wipe-data). Flash such "mix", re-root and enjoy

Reserved

There is new version available
Changelog
v1.1:
- Added SYSTEMLESS support for /system/framework
- Added SYSTEMLESS support for /system/build.prop (overrides & additions)
- Added major Android update detection (auto-remove mods for older API to prevent bootloops & FCs)
- Added BusyBox bionic (the most stable and respected release)
- Added logging to /data/devbase/last_boot.log (API & errors)
- Added SuperSU boot patcher version checker (exits su.d boot script if < 2.76)
- Added "Please DO NOT wipe /cache" warning in case of encrypted devices and TWRP recovery
- Minor changes & optimizations in the shell code
- Added SYSTEMLESS DevBase uninstaller
Download link:
>> SYSTEMLESS_DevBase_v1.1.zip <<
Since new version has many more features -> there are more possibilities of bootloop (especially if you are playing with framework mods). I have created DevBase remover to let you get out from bootloop. Of course uninstaller does NOT "know" which mod caused the problem, so it will not remove any file from /data/devbase directory, it will remove only /su/su.d/0000000devbase boot script to make your device bootable (again) so you can manually delete problematic mod:
>> SYSTEMLESS_DevBase_remover.zip <<

Another update:
v1.3:
- Fixed CscFeature MOD (e.g. G920I case, now should work with all Samsung devices/variants)
v1.2:
- Added info in Settings/About device/Software info/Build number (can be overrided by editing /data/devbase/system/build.prop)
- unroot2ota: added ability to restore stock recovery using /system/recovery-from-boot.p file (no guarantee)
- unroot2ota: check /system partition for common modifications before unroot
- Minor changes & improvements in the shell code
>> SYSTEMLESS_DevBase_v1.3.zip <<

[SM-J120FN] Debloat/DeGApp/DeSApp/DeKNOX/Tweak - SuperSU - microG

First of all, thanks to @javad490, most of this is based on his thread: [Custom][ROM] For j1(2016) j120F Android 5.1.1.
I take no responsibility for any damage or data loss - proceed at your own risk.
Below you will find step-by-step instructions on how to do what's in the title of thread.
I've made backups at every step, which I can upload on request.
SM-J120FN CUSTOM SETUP (1.0-170620)
Probably also 100% compatible with SM-J120F.
0 - Initialize device
Install latest Smart Switch for desktop (2017-05-26 - 4.1.17054_16)
Initialize device & update (2017-03-14 - PDA:QC1 / CSCL1 / PHONE:QC1 (SEE))
1 - Flash TWRP Recovery
Install latest Odin3 (2017-05-06 - 3.12.7)
Flash compatible TWRP Recovery (2016-12-31 - 3.0.2-0)
⇒ Backup 1 (stock)
2 - Flash latest SuperSU (2017-05-27 - 2.82)
⇒ Backup 2 (sprsu)
3 - Flash Debloat & Tweak and configure (1.0-170619)
WARNING: This script removes 167 out of 202 packages and 286 files/directories, and installs a few essential apps (see details).
Please review the bloat list and/or the script so you don't remove anything you want to keep.
You can also have the script install apps of your choosing (just place them in the correct directory).
Before & After
Details:
⇒ Debloat & tweaks by javad490 (2017-05-27)
1 - Debloat (full list (.ods)) (2017-06-19)
Imporant sources:
Debloater and Deknox Patch (2017-03-08)
Remove GApps (2017-04-28)
2 - Tweaks (2017-06-16)
Custom boot animation and sound (2017-06-16)
Boot: SciFi Droid (2016-07-01)
Shutdown: Blue Cube Shutdown (2015-06-11)
more: here and here
Tweaks by javad490 (2017-05-27)
improve Camera quality (2016-12-26)
50 tweaks (2016-11-22)
SpeedUp Wifi-3G-Lte (2016-09-15)
3 - Install apps (1.0-170620)
BusyBox (2017-01-18 - 1.26.2)
This is only an installer app, install Busybox manually
F-Droid (2017-06-02 - 0.103.2)
IzzyOnDroid Repository: https://apt.izzysoft.de/fdroid/repo
Yalp Store (2017-06-14 - 0.17)
Ghost Commander (2017-06-18 - 1.54)
Requires Busybox for root functions
KISS Launcher (2017-05-12 - 2.30.2)
Tap the O in the search bar to get a list of all apps
AnySoftKeyboard (2017-06-16 - 1.8.844)
Manually run app and setup to enable
Disa (2017-05-24 - 0.9.9-317)
Manually run app and setup to enable SMS
Click to expand...
Click to collapse
⇒ Backup 3 (dbltw)
4 - Install Xposed
Flash compatible Xposed Framework (2016-07-09 - 0.86)
Install latest Xposed Installer (2016-10-31 - 3.11)
⇒ Backup 4 (xposd)
5 - Install microG Services
Install FakeGApps with Xposed Installer (2016-03-04 - 1.1)
Enable and reboot
Install microG with F-Droid
microG Services Core (2017-06-12 - 0.2.4-103-gd9e86d9)
microG Services Framework Proxy (2016-02-07 - 0.1.0)
FakeStore (2016-11-16 - 0.0.2) - be sure to install 0.0.2 from microG repo
microG DroidGuard Helper (2017-05-19 - 0.1.0-10-gf64bf69)
Nlp Backends:
NominatimNlpBackend (2017-05-22 - 1.2.2)
OpenBmapNlpBackend (2016-12-09 - 0.2.6)
LocalGsmNlpBackend (2016-12-01 - 1.4.9)
LocalWifiNlpBackend (2016-08-21 - 1.1.6)
MozillaNlpBackend (2016-04-08 - 1.3.2)
Configure and reboot
⇒ Backup 5 (mcrog)
6 - Flash App installer, configure apps and reboot (1.0-170620)
App path inside zip must be: /apps/data/app.package.name-1/base.apk or /apps/system/app.package.name/base.apk
WARNING: make sure to download the correct APK for your system. For J120FN this is armeabi-v7a.
This script cannot handle updates - only use it to install apps for the first time
⇒ Backup 6 (final)
Installed apps:
Apps installed with Debloat script (see 3)
DAVdroid (1.6.1-ose)
Nextcloud (1.4.3)
oandbackup (0.2.12.1)
K-9 Mail (5.206)
Open Camera (1.38.2)
Camera Roll (1.5.2 Beta)
Vanilla Music (1.0.53)
Document Viewer (2.7.9)
Document Viewer Font Pack (2.3)
LibreOffice Viewer (5.3.0.0.alpha1+/4136757)
AddressToGPS (1.32)
MAPS.ME (7.3.5-Google)
Clock+ (1.1.3)
Etar (1.0.12)
Nextcloud Notes (0.11.0)
OpenTasks (1.1.8.2)
Calculator (5.4)
Firefox (54.0)
HTTPS Everywhere
uBlock Origin
Wi‐Fi Privacy Police (2.2.4)

EzraZebra said:
3 - Flash Debloat & Tweak and configure (1.0-170619)
WARNING: This script removes 167 out of 202 packages and 286 files/directories, and installs a few essential apps (see details).
Please review the bloat list and/or the script so you don't remove anything you want to keep.
You can also have the script install apps of your choosing (just place them in the correct directory).
Before & After
Details:
⇒ Backup 3 (dbltw)
Click to expand...
Click to collapse
The link for "Debloat & Tweak" is down, could someone please provide me with a working link ?

[APP][ROOT][5.0+][1st Nov 2020] Migrate - custom ROM migration tool

Jumping from one custom ROM to another can be a challenging task. So I decided to make an app to simplify the process.
Introducing
Migrate!
Migrate-GPE (v4.0) is on Google Play
It was temporarily suspended. Read more here: https://forum.xda-developers.com/showpost.php?p=82230451&postcount=1273
Download from Google Play Store
Download from AndroidFileHost
Download from XDA labs (removed as XDA Labs has shutdown)
CODEBASE ON GITHUB
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
With Migrate, you can back up:
App apk
App data
App runtime permissions
Contacts (as vcf file)
SMS messages
Call logs
Current ROM screen DPI
Current default keyboard option
App installer (Migrate 3.0)
Adb state (Migrate 3.0)
Font scale (Migrate 3.0)
... everything in one app.
Ok. So its just another of those backup and restore apps, right?
Sort of... but with a twist.
Restoring everything requires flashing the backup via TWRP.
ALTERNATELY
You can use the Migrate Flasher app (if your phone does not have a compatible recovery, or your recovery is broken).
If you are flashing via TWRP, see the below screenshot.
All your apps and data are restored to a directory under /data/balti.migrate, /data/local/tmp/migrate_cache (from v2.0+) and a helper app is injected into the system.. Once you boot up your new ROM, the app will spring up, ask for root permission and do all the job while you can relax.
IF YOU ARE USING MIGRATE FLASHER
The process is similar. Only difference is Migrate Helper is not injected into system, but installed as a user app. There is no use of recovery environment.
Once Migrate Helper is installed, just press RESTORE APPS AND DATA and proceed as usual.
Please see the HOW TO FLASH section on Migrate Flasher for complete illustration.
IF you have already flashed using TWRP (with no errors) then the above sections about Migrate Flasher is not applicable.
Donations:
Well, the app already has ads, so you need not explicitly donate anything
But if you are feeling reaalllyyy grateful for the app, you can donate here: paypal.me/sayantanrc
Thanks.
Migrate Gemini (v4.0) release
Hello everyone.
Migrate 4.0 is now released.
There are 2 editions of Migrate.
Migrate NG: This is the Non-Google and Beta edition. It is not published on Google Play store. It will continue having in-app updates. Moreover new features will be tested on these builds first. People who did not like firebase analytics, this edition is for you as it does not have firebase SDK anymore. However, Google admob ads are still present.
Download link (NG): https://www.androidfilehost.com/?fid=10763459528675575696
Migrate GPE: This version is Google Play Edition. It is the stable version. It does not have in-app updates anymore as it violated Google Play policies.
Download on Google Play: https://play.google.com/store/apps/details?id=balti.migrate
Coming from alpha 3.1, if you update via the in-app updater, you will be switched to the Non-Google Edition.
Thank you.
Want to translate the app?
The strings.xml file is available here: https://github.com/SayantanRC/translations
Telegram group!
We now have a Telegram group for migrate:
http://t.me/migrateApp
This is not to rival XDA but only another form of communication between users and me
Thanks.

FAQ:
Click here for Troubleshooting options
If you are facing issues while flashing, refer to this video: https://youtu.be/0Cp6TNayXnM
Full manual extract guide: https://forum.xda-developers.com/showpost.php?p=82198185&postcount=1269
How is this app different from Titanium backup?
This app is a ROM migration tool. It not only backs up app and data, but also contacts, SMS, call logs etc. Moreover, the restoration process also involves flashing via TWRP. Titanium backup is an excellent app. Migrate just views the restoration process differently.
In recent times however, Migrate Flasher app can be used to flash a zip even if you dont have a compatible TWRP recovery. Everything is almost the same other than just the flashing part, which is done from the Flasher app.
Do I need to download the Migrate app to restore the apps?
No. Only your ROM needs to be rooted. The restoration process is handled by a helper app, which deletes itself after restoring everything.
Is it necessary to use Magisk?
The app works best with Magisk. Other options like Lineage OS su addon causes weird errors like incomplete file copy, etc.
All apps are restored from recovery?
No. That is not possible. Because Recovery is a completely different environment from Android. Think of it as installing a Windows game from a Linux distro. Instead from recovery, an app is injected into system which takes up the restore process when android boots up. Most things are automated, so you need not worry much.
A quick word on SD card support...
SD card support in v2.0 requires a Magisk module "ExSDCard Access Enabler", made by developer Romain. According to him, this module requires FUSE support on ROMs. FUSE is supported on some ROMs as a legacy feature as Android has moved away from FUSE to SDCARDFS. As such, the current implementation may or may not work based on your device and ROM.
If it does not work for you, please wait until either the module developer rewrites the module or I find a different implementation Thanks for your patience.
From version 5.0+ (Not yet released, available on GitHub)
Users will be able to natively store backups on SD Cards, especially on Android 11+.
For lower Android versions, Storage Access Framework is used (along with root access) to store backups on SD Cards as well as on USB-OTG.

Changelog
Version 4.0 [1st November 2020]
# Compatibility fixes for Android 11
# Add Message center to display important announcements.
# Migrate helper now allows to retry failed apk installs
# Add a "Migrate flasher only" backup option
# Save app icons as png files
# Show number of apps selected for backup in Extra backups screen
# Keep screen on when calculating backup size
# Save last state of selection in extras
# Don't remount /data partition in system test
# Many under the hood changes
Version 3.1.1 [25thApril 2020]
# Fix issue in v3.1 where restore would not be possible for apps with unsupported characters in the name.
Version 3.1 [24thApril 2020]
# Probable fix to data restore problems
# Probable fix to helper crashing during loading apps
# Record raw list of files in a backup
# Many other minor improvements
Use v3.1.1 above
Version 3.0.3 [18thApril 2020]
#. Slightly tweaked logo.
#. Probable fix to No metadata found after flashing.
Version 3.0.1 [9thApril 2020]
#. Bug fixes
#. Added translations
Version 3.0 [20th March 2020]
#. The app is rewritten in Kotlin
#. Many new preferences have been added.
#. Helper app is now available on Google Play.
#. Many fixes in recovery. Support for SAR and Android 10.
#. Added options for backup of app installer, font scale, adb state
#. Set max zip size in preferences.
#. Verification of zips after backup is complete.
#. Many more changes and improvements…
Version 2.1 [15th Jan]
# Minor errors are now suppressed, but recorded in log.
# Fix icon retention form previous backup
# Fix wrong backup duration display.
# Fixed a bug in error correction mechanism.
# Probable fix for some apps not being backed up.
# Fix for error 6 in TWRP for some locales.
# Fixed a long standing wrong /data space calculation in TWRP.
# Migrate helper no longer uninstalls app before installing.
# Added Telegram group link!
Version 2.0.1 [30th Dec] (christmas_beta)
# Fixed a probable crash in Migrate helper (needs a magisk module)
Version 2.0 [26th Dec] (christmas_beta)
# Experimental SD card support (needs a magisk module)
(please read the previous post)
# Support for split apks
# "Abort" option in Migrate helper
# "Temporary disable" in Migrate helper
# Apks are now unpacked under /data/local/tmp/migrate_cache
(probable fix to some devices unable to install apks)
# Each backup zip now has a busybox file as fallback
Version 1.2 [12th Nov] (beta)
# Completely avoid "dumpsys" to backup app permissions
# Now app data in tar.gz is unpacked in /data/data
(probable fix to "Operation not permitted" issues in Google Pixel and some other devices)
Version 1.1.1 [10th Nov] (beta)
v1.1 (skipping upload)
# [New] Backup verification before zipping
# Major code refactoring and under-the-hood changes
# CANCEL button now kills the backup process
# Fix to "set_progress()" in recovery
# Probable fix to "Failed to change locale for db"
# Probable fix to missing updater-script
# Probable fix to some "Operation not permitted" issues
# Remove illegal characters from backup name
# "Share scripts" option should now work properly.
v1.1.1
# Fix to a no-closing-quote issue in helper
Version 1.0.5 [7th Nov] (beta)
# Probable fix to "android.os.TransactionTooLargeException"
# Better in app protection to prevent zips from not being made
# App version is now written in logs
# App now targets Oreo instead of Pie to potentially avoid some crashes
# Fixed unexpected ( in restore process
Version 1.0.4 [5th Nov] (beta)
# Improvements to logging
# Ignore tar socket warnings
# New update-binary to prevent TWRP error 3
# Should fix a null String issue while reading backup data
Version 1.0.3 (beta)
# Fixed log sharing
# Share script file in log
# Blacklist Android system from system app backup list (prevents tar socket error)
Version 1.0 (beta)
# Initial release

Some plaguing bugs on some devices
"dumpsys not found"
(Severity: mild. Only permissions are not backed up)
Mainly in ASUS devices. Probable solution is to not use dumpsys at all.
Probably fixed in v1.2
"tar: can't execute 'gzip': Permission denied"
(Severity: severe. Do not restore this backup)
I still have no idea why this is happening. Probable solution is use something other than tar.gz
Data files cannot be moved during restore. "Operation not permitted"
(Severity: severe)
No idea yet. Prominent in Google Pixel devices and some Xiaomi devices
Probably partially or completely fixed in v1.2
Error 7 (or 6) in TWRP
(Severity: severe)
This issue which was supposedly fixed in v1.1.1 seems to occur again on few devices
Since I cannot reproduce the issue and the number of error reports are pretty small, please send the recovery.log from TWRP:
- Goto Advanced -> Terminal in TWRP
OR
open an adb shell inside TWRP
- Type the following and press enter: cp /tmp/recovery.log /sdcard/
- Reboot and upload the recovery.log file (from internal sd card) here.
Stuck at calculating size.
(Severity: severe)
This is being reported multiple times. I am still unable to reproduce the issue on my device.
That being said, I will be adding new controls to skip size checking of its stuck on any device, in the next release. Also, I will add more fine logging to see what is actually happening behind the scenes, which cannot be detected by a logcat.
Probably fixed in v2.0
Pocophone TWRP recovery has issues
(Severity: severe)
I need someone to do the following and then upload the file:/sdcard/test_log.log
- TWRP main menu -> Mount -> Data and System should be mounted
- TWRP main menu -> Advanced -> Terminal
OR
open an adb shell inside TWRP
- Type the following commands:
getprop > /sdcard/test_log.log
echo " " >> /sdcard/test_log.log
df /data >> /sdcard/test_log.log
echo " " >> /sdcard/test_log.log
df -k /data >> /sdcard/test_log.log
echo " " >> /sdcard/test_log.log
df -h /data >> /sdcard/test_log.log
echo " " >> /sdcard/test_log.log
df /system >> /sdcard/test_log.log
The following should work as an alternative:
SayantanRC said:
You have to manually do the following:
1. Open the backup zip file
2. Edit the "package-data.txt" file
3. Put the "data_required_size" as "0"
4. Save the file.
5. Repack the zip file.
Click to expand...
Click to collapse
"Segmentation fault"
(Severity: unknown)
Mainly in Xiaomi devices. I cannot reproduce it. Neither do I know how much this affects the backup. Please restore a backup and tell me if it works.

Useful

Quite promising
So what does the helper app really do? Move the apps and data from /data/balti.migrate to their respective directories? How does that work in a booted up ROM?

candiesdoodle said:
Quite promising
So what does the helper app really do? Move the apps and data from /data/balti.migrate to their respective directories? How does that work in a booted up ROM?
Click to expand...
Click to collapse
The helper app installs the apks using package manager and then unpacks the data of the respective apps in /data/data. Finally it restores all the apps runtime permissions.

I got this issue

Wifi?

ceelos218 said:
I got this issue
Click to expand...
Click to collapse
Please tell how to reproduce the issue.

m0d said:
Wifi?
Click to expand...
Click to collapse
Maybe added in future

bin.sayantan said:
Please tell how to reproduce the issue.
Click to expand...
Click to collapse
I just clicked next.. nothing else I selected all apps to backup then next page ticked boxes to back up.. click ready and I got that error and It didn't back up anything.

bin.sayantan said:
The helper app installs the apks using package manager and then unpacks the data of the respective apps in /data/data. Finally it restores all the apps runtime permissions.
Click to expand...
Click to collapse
Does it handle folder permissions when there are changes in app uid for data restore
when pm installs app, app uid can be different than before, so there might be folder permission discrepencies?
I.E.
Code:
#!/bin/sh
if [ "$1" != "" ];
then
#The folders in /data/data each have a different owner. The next line gets the owner and the strips the whitespace
appusername=$(stat -c "%U" /data/data/$1 | xargs)
#The next line constructs the chown command to repair the permissions for all the files in the target folder
fixperm="chown -R $appusername:$appusername /data/data/$1/*"
#Display the command to the user
echo "$fixperm"
#Uncomment the next line if you would like the script to fix the permission
eval $fixperm
else echo "Missing target folder parameter"
fi

m0d said:
Does it handle folder permissions when there are changes in app uid for data restore
when pm installs app, app uid can be different than before, so there might be folder permission discrepencies?
I.E.
Code:
#!/bin/sh
if [ "$1" != "" ];
then
#The folders in /data/data each have a different owner. The next line gets the owner and the strips the whitespace
appusername=$(stat -c "%U" /data/data/$1 | xargs)
#The next line constructs the chown command to repair the permissions for all the files in the target folder
fixperm="chown -R $appusername:$appusername /data/data/$1/*"
#Display the command to the user
echo "$fixperm"
#Uncomment the next line if you would like the script to fix the permission
eval $fixperm
else echo "Missing target folder parameter"
fi
Click to expand...
Click to collapse
It takes care of the new uid for the app. No problem with that.

ceelos218 said:
I just clicked next.. nothing else I selected all apps to backup then next page ticked boxes to back up.. click ready and I got that error and It didn't back up anything.
Click to expand...
Click to collapse
This is weird. Please open the green circle button on top left in the first screen of the app -> Contact by email and send the issue.

I'm getting this error

Sorry for inconvenience.
ceelos218 said:
I just clicked next.. nothing else I selected all apps to backup then next page ticked boxes to back up.. click ready and I got that error and It didn't back up anything.
Click to expand...
Click to collapse
Same here, nothing happen. But you check >sdcard/migrate and the files are there.
Regards.

Just tried this. Backup speed is super fast backed up 75 apps in 3 minutes. Interface is also very nice.
Please include a pro version or in app purchase to removed ads.

m0d said:
Does it handle folder permissions when there are changes in app uid for data restore
when pm installs app, app uid can be different than before, so there might be folder permission discrepencies?
Click to expand...
Click to collapse
Do you have an idea if Titanium Backup and/or Swift Backup take care of app uid changes during data restore to avoid folder permission discrepancies?

Can i use this to jump between like for example MIUI 10 China Stable(with root) to 9.0 Pie custom roms ? Using OrangeFox TWRP,Redmi Note 4x(mido)

[Magisk Debloat] [OOS A11] Eagle debloater V3.0

Hi all, This is my personal debloating module.
Debloats Oneplus analytics, Google apps, unnecesary apps
Personally i'm using Extreme debloat and disable analytics services
Requirements:
- OOS A11
- Supports All oneplus 7 series (i have tested only on op7p but it supports all)
- Magisk 20+
- Should be flashed only in Magisk
- Those who have india.img must flash Overlay Mount Fix magisk module v2.1 by Zackptg5 (inorder to debloat system/product apps).
If you don't know you have india.img or not, just flash the above overlay fix in magisk. If it flashed successfully no problem.
If it says "No overlay detected", also no problem you can now directly flash debloat zip
Debloating Options :
1- Extreme debloat
DEBLOATED APP LIST CAN BE FOUND HERE
Warning -
- Before flashing extreme debloat, Goto Settings - Security - Emergency rescue - Emergency call trigger - disable
If you don't disable emergency rescue, double tap power button -camera shortcut won't work.
- Oneplus software update app was removed so use oxygen updater from Playstore
- Removed Google apps can be installed from Playstore
Code:
/system/app/OPPush
/system/app/GooglePay
/system/app/EngineeringMode
/system/app/Backup
/system/app/BackupRestoreRemoteService
/system/app/GooglePrintRecommendationService
/system/app/EngSpecialTest
/system/app/LogKitSdService
/system/app/NFCTestMode
/system/app/oem_tcma
/system/app/OPYellowpage
/system/app/PhotosOnline
/system/app/OPBackup
/system/app/OEMLogKit
/system/app/NVBackupUI
/system/app/OPBreathMode
/system/app/OemAutoTestServer
/system/app/OPBugReportLite
/system/app/OPCommonLogTool
/system/app/BasicDreams
/system/app/OPFilemanager
/system/app/BookmarkProvider
/system/app/Traceur
/system/app/Stk
/system/app/Rftoolkit
/system/app/PartnerBookmarksProvider
/system/app/BuiltInPrintService
/system/app/BTtestmode
/system/app/WifiRfTestApk
/system/app/PlayAutoInstallConfig
/system/app/SensorTestTool
/system/app/CarrierDefaultApp
/system/app/OPAppUpgrader
/system/product/app/QtiSettings
/system/priv-app/RcsSDK
/system/app/WAPPushManager
/system/app/SmscPlugger
/system/priv-app/IFAAService
/system/priv-app/DynamicSystemInstallationService
/system/priv-app/ManagedProvisioning
/system/priv-app/OnePlusWizard
/system/priv-app/EmergencyInfo
/system/product/app/LatinImeGoogle
/system/priv-app/GoogleDocumentsUIPrebuilt
/system/product/priv-app/Turbo
/system/priv-app/BackupRestoreConfirmation
/system/priv-app/OPSimContacts
/system/priv-app/SharedStorageBackup
/system/priv-app/subsdm
/system/priv-app/TSDM
/system/priv-app/OPDeviceManager
/system/priv-app/OPCellBroadcastReceiver
/system/priv-app/OPDeviceManagerProvider
/system/product/app/CalendarGoogle
/system/product/app/Chrome
/system/product/app/TmoEngMode
/system/product/app/uimremoteclient
/system/product/app/Drive
/system/product/app/Gmail2
/system/product/app/GooglePay
/system/product/app/Videos
/system/product/app/talkback
/system/product/priv-app/GooglePartnerSetup
/system/product/app/Music2
/system/product/app/GoogleLocationHistory
/system/product/app/YouTube
/system/product/app/Duo
/system/product/priv-app/GooglePartnerSetup
/system/priv-app/HotwordEnrollmentOKGoogleWCD9340
/system/priv-app/HotwordEnrollmentXGoogleWCD9340
/system/product/app/Maps
/system/product/app/Photos
/system/product/app/GoogleTTS
/system/product/priv-app/Velvet
/system/product/priv-app/WallpaperCropper
/system/product/priv-app/SetupWizard
/system/product/priv-app/GoogleFeedback
/system/product/priv-app/GoogleOneTimeInitializer
/system/product/priv-app/GoogleRestore
/system/product/priv-app/AndroidAutoStub
/system/vendor/app/PowerOffAlarm
/system/reserve
/system/product/app/uceShimService
/system/product/app/com.qualcomm.qti.services.secureui
/system/vendor/app/pasrservice
/system/product/app/remotesimlockservice
/system/product/app/remoteSimLockAuthentication
/system/product/app/uimgbaservice
/system/product/app/uimlpaservice
/system/product/app/DeviceInfo
/system/app/Netflix_Activation
/system/app/Netflix_Stub
/system/app/OPGeoIpTime
/system/priv-app/CallLogBackup
/system/app/OPSesAuthentication
/system/app/WallpaperBackup
/system/app/WapiCertManage
/system/product/priv-app/Wellbeing
2 - Debloat Google apps except play service and playstore
Code:
/system/app/BackupRestoreRemoteService
/system/app/BasicDreams
/system/app/BookmarkProvider
/system/app/GooglePrintRecommendationService
/system/app/PartnerBookmarksProvider
/system/app/Traceur
/system/app/WallpaperBackup
/system/product/app/CalendarGoogle
/system/product/app/Chrome
/system/product/app/Drive
/system/product/app/Duo
/system/product/app/Gmail2
/system/product/app/GoogleContactsSyncAdapter
/system/product/app/GoogleLocationHistory
/system/product/app/GooglePay
/system/product/app/GoogleTTS
/system/product/app/Maps
/system/product/app/Music2
/system/product/app/Photos
/system/product/app/talkback
/system/product/app/Videos
/system/product/app/YouTube
/system/app/ARCore_stub
/system/product/priv-app/GoogleRestore
/system/product/priv-app/HotwordEnrollmentOKGoogleWCD9340
/system/product/priv-app/HotwordEnrollmentXGoogleWCD9340
/system/product/priv-app/Turbo
/system/system_ext/priv-app/GoogleFeedback
/system/system_ext/priv-app/GoogleOneTimeInitializer
/system/system_ext/priv-app/TagGoogle
/system/reserve
3- Debloat Oneplus Analytics only
Code:
/system/app/OPMinidumpOptimization
/system/priv-app/OnePlusWizard
/system/priv-app/SharedStorageBackup
/system/priv-app/DynamicSystemInstallationService
/system/priv-app/ManagedProvisioning
/system/priv-app/OPSimContacts
/system/priv-app/CellBroadcastLegacyApp
/system/system_ext/app/AntHalService-Soong
/system/system_ext/app/BTtestmode
/system/system_ext/app/EngineeringMode
/system/system_ext/app/EngSpecialTest
/system/system_ext/app/LogKitSdService
/system/system_ext/app/NFCTestMode
/system/system_ext/app/oem_tcma
/system/system_ext/app/OemAutoTestServer
/system/system_ext/app/OPBackup
/system/system_ext/app/OPBreathMode
/system/system_ext/app/OPBugReportLite
/system/system_ext/app/OPCommonLogTool
/system/system_ext/app/OPEngMode
/system/system_ext/app/OPPush
/system/system_ext/app/PhotosOnline
/system/system_ext/app/remoteSimLockAuthentication
/system/system_ext/app/remotesimlockservice
/system/system_ext/app/Rftoolkit
/system/system_ext/app/uimremoteclient
/system/system_ext/app/uimremoteserver
/system/system_ext/app/uceShimService
/system/system_ext/app/uimgbaservice
/system/system_ext/app/uimlpaservice
/system/system_ext/priv-app/OPDeviceManager
/system/system_ext/priv-app/OPDeviceManagerProvider
/system/vendor/app/SSGTelemetryService
/system/reserve
4- Remove unnecessary services like appmeasurement, gms analytics
Script by By foobar66
List of services disabled
Code:
com.braintreepayments.api.internal.AnalyticsIntentService
com.facebook.ads.internal.ipc.AdsMessengerService
com.facebook.ads.internal.ipc.AdsProcessPriorityService
com.facebook.internal.FacebookInitProvider
com.google.analytics.tracking.android.CampaignTrackingReceiver
com.google.analytics.tracking.android.CampaignTrackingService
com.google.android.gms.ads.MobileAdsInitProvider
com.google.android.gms.analytics.AnalyticsJobService
com.google.android.gms.analytics.AnalyticsReceiver
com.google.android.gms.analytics.AnalyticsService
com.google.android.gms.analytics.AnalyticsTaskService
com.google.android.gms.auth.api.signin.RevocationBoundService
com.google.android.gms.measurement.AppMeasurementInstallReferrerReceiver
com.google.android.gms.measurement.AppMeasurementJobService
com.google.android.gms.measurement.AppMeasurementReceiver com.google.android.gms.measurement.AppMeasurementService
com.google.firebase.perf.provider.FirebasePerfProvider
com.google.firebase.provider.FirebasePerfProvider
com.google.android.apps.xcn.libraries.clearcut.persistence.LogCommitService"
Credits
Tomatot for his original mod here
Analytics Script by foobar66 his original thread can be found here
Changelog
-v1 Initial Release
-V1.1 added google tag, qualcomm logging apps to Extreme debloat
Code:
/system/priv-app/TagGoogle
/system/product/app/DynamicDDSService
/system/product/app/uimremoteserver
/system/product/app/Account
/system/app/CtsShimPrebuilt
/system/app/AntHalService
/system/app/SoterService
/system/priv-app/CtsShimPrivPrebuilt
V1.2 Added more qualcomm apps to Extreme debloat
Code:
/system/product/app/uceShimService
/system/product/app/com.qualcomm.qti.services.secureui
/system/vendor/app/pasrservice
/system/product/app/remotesimlockservice
/system/product/app/remoteSimLockAuthentication
/system/product/app/uimgbaservice
/system/product/app/uimlpaservice
/system/product/app/DeviceInfo
V1.3
-Added some more qualcomm useless apps to extreme debloat
- Replaced system/etc/init/traceur.rc with empty file
Code:
/system/product/app/QtiSettings
/system/priv-app/RcsSDK
/system/product/priv-app/dpmserviceapp
/system/app/WAPPushManager
/system/app/SmscPlugger
/system/priv-app/IFAAService
-V1.4
- Reverted back the debloat of dpmserviceapp . As if i deleted this app, android system (onepluscore)having more wakelocks
V1.5
-Added to extreme debloat and google debloat
Code:
/system/product/priv-app/GooglePartnerSetup
-Added to extreme debloat
Code:
/system/app/Netflix_Activation
/system/app/Netflix_Stub
/system/app/OPGeoIpTime
V1.6
-Added following apps to extreme debloat
Code:
/system/app/OPScreenRecord
/system/app/EasterEgg_O2
-Added to both google and extreme debloat
Code:
/system/product/app/LatinImeGoogle
/system/priv-app/GoogleDocumentsUIPrebuilt
/system/product/priv-app/Turbo
V1.7
-Added separate option to debloat gboard
V1.8
-Added to extreme debloat
Code:
/system/priv-app/CallLogBackup
/system/app/OPSesAuthentication
/system/app/WallpaperBackup
/system/app/WapiCertManage
/system/product/priv-app/Wellbeing
- Added to oneplus analytics
Code:
/system/app/OPSesAuthentication
- Added Anysoft keyboard as alternative when gboard is debloated
V1.9
-Added to extreme
Code:
/system/product/priv-app/StorageManager
/system/app/OPIntelliService
Replaced system/etc/init/
bootstat.rc
bluetooth-events.rc
dumpstate.rc
engineermode.rc
recovery-refresh.rc
recovery-persist.rc
Click to expand...
Click to collapse
with empty file
V2.0
Removed
Code:
/system/app/OPIntelliService
/system/priv-app/GoogleDocumentsUIPrebuilt
Added to Extreme Debloat
Code:
/system/product/app/Nearme
/system/product/app/OPMemberShip
/system/product/priv-app/CloudService
/system/product/priv-app/IndiaOPRoamingServiceRelease
/system/product/priv-app/OPWorkLifeBalance
/system/product/app/heytap_mcs_in
/system/product/app/HeytapIdProvider
V3.0
Added support for Android 11 debloat
For Android 10 - Please use debloat v2.0
Download link
Android File host

Nice may can work on OP6T?

Mervingio said:
Nice may can work on OP6T?
Click to expand...
Click to collapse
Afaik, it will work if you're in OOS 10 Stock
You can try . If you got bootloop just flash the module again in twrp (to remove the module)

Does this keep PlayStore as a system app?

krishaun27 said:
Does this keep PlayStore as a system app?
Click to expand...
Click to collapse
yeah . Except playservices and playstore all Google apps removed which can be downloaded from playstore

Flashed this over 10.3.2 and ICE, got some apps back instead of debating and some apps stopped working, getting FCs...

twoxa said:
Flashed this over 10.3.2 and ICE, got some apps back instead of debating and some apps stopped working, getting FCs...
Click to expand...
Click to collapse
Did you flash Overlay mount fix or not

methuntt said:
Did you flash Overlay mount fix or not
Click to expand...
Click to collapse
Missed that, thanks. Supposed to be flashed right after the module?

twoxa said:
Missed that, thanks. Supposed to be flashed right after the module?
Click to expand...
Click to collapse
You can flash both at same time or in any manner first overlay then debloat or vice versa

Do both zips need to be flashed to both slots?
Sent from my GM1917 using Tapatalk

krishaun27 said:
Do both zips need to be flashed to both slots?
Click to expand...
Click to collapse
No . Only the slot your ROM running.

krishaun27 said:
Do both zips need to be flashed to both slots?
Click to expand...
Click to collapse
+1 yeah any chance of some instructions being listed in the first post? I tried flashing the overlay fix module in Magisk but it failed saying "no overlay mounts detected". So do I flash the zip first in Magisk? Or flash that in twrp? Or both in twrp?! Can the script be edited to exclude some apps from being debloated?
Many thanks in advance, looking forward to some debloating!

cd993 said:
+1 yeah any chance of some instructions being listed in the first post? I tried flashing the overlay fix module in Magisk but it failed saying "no overlay mounts detected". So do I flash the zip first in Magisk? Or flash that in twrp? Or both in twrp?! Can the script be edited to exclude some apps from being debloated?
Many thanks in advance, looking forward to some debloating!
Click to expand...
Click to collapse
Don't flash zips in twrp. It should be flashed in magisk only (updated instructions)
Script can be easily edited. just remove the line which contain the app you want from install.sh
Eg- Don't debloat Google app
Remove the line
/system/product/priv-app/velvet
No overlay detected --directly flash the debloater and say the result.

cd993 said:
+1 yeah any chance of some instructions being listed in the first post? I tried flashing the overlay fix module in Magisk but it failed saying "no overlay mounts detected". So do I flash the zip first in Magisk? Or flash that in twrp? Or both in twrp?! Can the script be edited to exclude some apps from being debloated?
Many thanks in advance, looking forward to some debloating!
Click to expand...
Click to collapse
Sorry... me again....
I successfully removed lines for the script and that flashed fine in Magisk. But neither v2.1 or v1.1 of the overlay fix install, even after a reboot after successful install of then debloat script, as again it just says "no overlay mounts detected"?

cd993 said:
Sorry... me again....
I successfully removed lines for the script and that flashed fine in Magisk. But neither v2.1 or v1.1 of the overlay fix install, even after a reboot after successful install of then debloat script, as again it just says "no overlay mounts detected"?
Click to expand...
Click to collapse
Without overlay fix, is apps are debloated successfuly ?
Sent from my 7 Pro using XDA Labs

methuntt said:
Without overlay fix, is apps are debloated successfuly ?
Click to expand...
Click to collapse
Yes, I can confirm the debloat script for me works fine without the overlay fix. I just added a custom line and it successfully removed it!

cd993 said:
Yes, I can confirm the debloat script for me works fine without the overlay fix. I just added a custom line and it successfully removed it!
Click to expand...
Click to collapse
Nice .
But for some people overlay fix needed. Those who have india.img.
Sent from my 7 Pro using XDA Labs

methuntt said:
Nice .
But for some people overlay fix needed. Those who have india.img.
Click to expand...
Click to collapse
Cool, that's good to know. I'm on EU.
Cheers!

New version
-V1.2 Added more qualcomm apps to Extreme debloat
Code:
/system/product/app/uceShimService
/system/product/app/com.qualcomm.qti.services.secureui
/system/vendor/app/pasrservice
/system/product/app/remotesimlockservice
/system/product/app/remoteSimLockAuthentication
/system/product/app/uimgbaservice
/system/product/app/uimlpaservice
/system/product/app/DeviceInfo

methuntt said:
New version
-V1.2 Added more qualcomm apps to Extreme debloat
Click to expand...
Click to collapse
Thanks for the update and listing the new added things that are being debloated, as I just add these to my custom edited version.
Cheers!