UnBloatMi - Xiaomi MIUI Bloatware Remover
I have been searching for a script to remove Bloatware from my Xiaomi Redni Pro, and found a couple of different ones that do part of the job.
None were exactly what I was looking for, so I wrote a script of my own.
Although I tested the script on Redmi pro and MI5s only, it should be very usable for any Xiaomi device running MIUI 7 or 8.
In UnBloatMi I have combined multiple lists of MIUI 7 and 8 apps that should be safe to remove.
It also contains a couple that are less safe to remove, but the script will ask for confirmation before removing those.
Which is a big difference from other scripts; you get to choose what to remove and what to restore!
Backup location:
If you edit the script, you can change the backup location to use (by default "/sdcard/UnBloatMi")
You can of course also add more apps to remove to the list in the script. (instructions are in the comments)
It's not needed to remove files from the list, as it will not process files that are not on your device, and you can choose not to remove any app.
To Customize the Script:
Unzip the zip and edit the file under: META-INF\com\google\android\update-binary
This script is written in shell language (sh), so editing is somewhat different from "normal" EDIFY scripts that use the "updater-script" file.
I used part of the excellent template by osm0sis to create UnBloatMi
Install Custom Apps/Files:
You can also have the script install Custom files to /system folder. (So you can add another HomeLauncher, for example)
To have the script install Custom files, just add them to the Zip in "/system/app/" folder:
/system/app/YourCustomApp1/YourCustomApp1.apk
/system/app/YourCustomApp2/YourCustomApp2.apk
The script will automatically install them for you.
To use the Script:
You need to have TWRP Recovery installed.
BACKUP YOUR DEVICE BEFORE RUNNING THIS SCRIPT!!! (I recommend using TWRP Backup)
(even though the script allows you to restore your changes, something can always go wrong - press wrong button for example)
- Move the ZIP file to your SDCard, and install using TWRP Recovery
Basically, you can just follow the instructions on the screen, by pressing Volume buttons.
- The first run, you'll be asked what apps to remove. Backups are automatically made.
You can confirm each app, or choose to only confirm the more risky apps.
- If you run the script again (after testing your installation), it will detect the backups from the previous run.
You can then choose to restore the backup files, or delete them from your device.
- You can now also create a default UnBloat list, that can be used to UnBloat after flashing a (new) ROM.
It is created by checking for installed apps. If an app is not found on the device, it's added to the list
{
"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"
}
Feel free to edit and change the script.
If you make any improvements, please let me know so I can add them to the script.
This includes reporting what apps caused problems when removed, or comments about apps.
You can find the script in: /META-INF/com/google/android/update-binary (or on GitHub by clicking the "Source Code" link below)
Instructions can be found in the comments of that file.
--UPDATE--
Added Step by Step Restore: You can now choose which apps to restore, so it is easier to troubleshoot your installation.
--UPDATE v0.2--
Added warning to SecurityCenter App (so it has to be confirmed). It caused bootloop on my device when removed.
--UPDATE v0.3--
Bugfixes, Added Apps, changed and added some app comments. Changed download link (GitHub download creates a folder too many)
--UPDATE v0.4--
Changed/Added menu's - Allows you to do more actions at once
Added apps and comments.
Added ability to save a default UnBloat list. This can be used to UnBloat after flashing a ROM.
Download
Source Code
Developer
Related
Parabola949 and the Android Creative Syndicate proudly present...
ACS Updater
{
"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"
}
UNINSTALL OLD VERSION FIRST:
adb uninstall com.acs.updater
Version 1.3
What is the ACS Updater?
ACS Updater is an app for android devices that allows you to download and install custom roms, kernels, themes, and modems from the internet on the fly. It's very simple to use: run the app, select what you want to install. You will get a screen asking if you want to wipe cache / backup first. Select options, and hit OK. The file will download from the net to /sdcard/ACSDownloads, and when complete, will reboot into recovery and install automatically.
Backup and Restore can also be done via the app, as well as Installing from SD Card, and even Install from URL - put in whatever URL you want, and it will download and install (if you put in a URL to something that isn't a flashable zip, and try to install it, that's your fault.)
In future releases, there will be more goodies, stay tuned!
Notes:
If you choose not to wipe cache, and the flash goes bad, that's on you. It's there as an option, but I'm not going to force it.
If you hit an area (such as Themes), and it says nothing available:
Developer's have not submitted anything for your device
Servers are temporarily down - try again in a couple minutes
Try using the "Reset Wifi Connection" Option
This App depends on a custom -R-E-C-O-V-E-R-Y- KERNEL which includes extendedcommands
It's always a good idea to backup before flashing a new ROM
Developers:
Want your work listed in the app? Simply submit your info to the following links (whichever applies), and I'll get it added to the database.
Submit Modem
Submit ROM
Submit Kernel
Submit Theme
Submit System Tweak
Submit (Flashable!) Custom App
ChangeLog:
v1.3
Added Custom apps section
Added Tweaks (Mods) section
Added Reboot Recovery Option
Added Reset Wifi Connection Option
Added the ability to publish to ALL devices!
v1.2: Bugfix
Backup Before install was not working properly - Fixed
v1.1: Initial release
Backup
Restore
Download / Install
Install from SD Card
Install from URL
Wipe Cache
Known Issues:
"Nothing Available at this time" - This appears to be a combination of server issues (the current host may have a limit on how many sql queries can be run at a time....) and possibly http host resolution issues within the app. I have added a bit of code to resolve this, and a "Reset Wifi Connection" option. Use this, wait a moment, then try again
Booting into a blue recovery and not flashing - this is caused by a stock kernel. This app relies on the recovery that is in the kernel, NOT that one you installed (i.e. amonra, clockwork, bonsai, etc)- your kernel MUST have a custom recovery. If you are coming from stock, please flash a kernel before using this app.
To get it, head over to:
http://www.forums.acsyndicate.net/showthread.php/1331-APP-ACS-Updater-download-and-install-ROMs-Kernels-Themes-and-Modems-on-the-fly
yeah thanks
This version/thread retired
new version - with source - can be found here: http://forum.xda-developers.com/showthread.php?p=36854150
This release composes of two parts:
The RTDPackager which creates an AIP file, and AIPInstaller which is the installer for these AIP files.
V1.1 of RTPackager release - now fully functional.
AIPInstaller Usage
Place the exe file and associated DLL in a folder somewhere sensible. I have not tested in ProgramFiles yet but the app elevates UAC so should be ok.
Double click on any AIP file (I include one as an example) and windows willl show this:
{
"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"
}
select 'more options' which will show this:
check the check box at the top and then click 'Look for another app on this pc'
A browse dialog will open - find and select AIPInstaller and you are done. You only need to do this the first time. I intend to add an auto install to this, so in future you can just double click the installer and it'll set itself up, but till then...
From now on, you can double click an AIP file and the installer will pop up. Usually just hitting 'install' will be all you need to do (there are some advanced functions like disabling the install batch if it exists, and changing the install path which isnt really recommended)
RTDPackager Usage
This utility is designed for creating AIP files. Its worth paying note that the AIP format is designed for repos more than it is the installer - so there are a lot of details here which the repo can use to make you app more visible.
V1.1 now has full open and save support.
Save will save a template XML, which can be loaded later with the Open button. Open will also open an existing AIP file and fill in the details.
Create Package no longer saves in the same place as the files being packaged - it opens a save dialog.
The browse button will now work and populate the run EXE field and the folder field.
some details:
AppName is the display name - and the install folder - so avoid \'s and such. If you change this in an update, it will get installed to a new folder.
Updates are detected based on the App GUID. Change this, it will appear as a new app - use the same GUID on more than one app and you will have conflicts. The generate button for GUID *DOES* work - you should only use it on the first release of your app - and for the time being, keep it safe for any updates.
Run EXE is the exe that will be launched by the store when the user asks to run it - and if a shortcut name exists, will be placed in the start menu.
Install/uninstall batch files are option batch files for installing/uninstalling registry settings and the like. There is currently no uninstaller, but the store app should have this built in - the uninstall batch is NOT for deleting files - the store will handle that.
App version number is a REAL number. ie. 1.03 is ok. 1.0.3 is not.
App category is for placing your app in a 'folder' - it is free form, with | splitting. Anyone can create a new category this way and its not up to the repo manager to manage this. Obviously it will work better if we have sensible categories such as 'Apps|Browsing' or 'Emulators|GameBoy' - while its totally possible to do 'djboo|prerelease|funthing' - i hope we dont do that.
DOWNLOADS
First Release of AIP installer: http://forum.xda-developers.com/attachment.php?attachmentid=1644222&stc=1&d=1358172785
V1.1 Release of RTD Packager: http://forum.xda-developers.com/attachment.php?attachmentid=1644631&stc=1&d=1358184708
Example AIP file (is in a zip as XDA wont allow the AIP extension): http://forum.xda-developers.com/attachment.php?attachmentid=1644224&stc=1&d=1358172785
reserved
Note: Once the RTD Packager is complete, code will be shared for both - that should be tonight.
Nice work so far, haven't tested all elements of it yet but it looks pretty good! Keep up the good dev work!
Hello everyone..
In my tutorial here, I want to show newbies how to create their own flashable zip file to flash by recovery mode (CWM)...
Now installing your mods become easier and faster
Needed tools for newbies:
1) Download your desired template:
Template - for auto-perm-fix kernel support.zip
Template - for non auto-perm-fix kernel.zip
more details is down there!!
2) WinRAR or 7-zip program installed in your computer.
3) Auto-ZIP-Signer patch in case your kernel needs it
4) Cup of hot tea!!!
Which template should I use?
It depends on kernel you are using whether it supports auto permission fix or not (most of custom kernels support this feature)..
To know if you are using kernel with auto permission fix or not, boot into recovery mode and check if you have fix permissions option or not (usually under advance). If your kernel has fix permissions option, then use Template - for auto-perm-fix kernel support.zip otherwise, use Template - for non auto-perm-fix kernel.zip.
What will happen if you use wrong template?
If your kernel supports auto permission fix feature and you used Template - for non auto-perm-fix kernel.zip, nothing will go wrong (so don't worry!!) but the flashing process will take unnecessary longer time for fixing permissions!!.
If your kernel doesn't support auto permission fix feature and you used Template - for auto-perm-fix kernel support.zip, then you might need to fix permissions of the flashed mod manually or to add extra permissions line in updater-script (not advised for newbies)
How is it working?
Open the template zip file by WinRAR or 7-zip (don't extract!! Just open)
{
"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"
}
Now what you need to do is just to drag & drop your modded file into its corresponding destination inside the zip file.
Copy your finished zip file to your external SD card.
Boot into recovery mode and flash your file... Now you can treat yourself the cup of tea.. you deserve it
Extra step:
If you are using stock kernel that needs varification key from flashable zip file, then you need to use Auto-ZIP-Signer to sign your finished zip file.
First copy your finished zip file from previous step and open ZIP Auto-Signer folder (download from above).
Now paste your zip file in "put-zip-to-sign-here" folder and run the script patch.
Now go to "Finished" folder and copy "Signed.zip" into your external SD card.
Boot into recovery mode and flash your signed file
Simple and noob proof tutorial, I hope it will help you all new xda members
I have installed and tested all the custom ROMs in this forum. Everything is unique in its own way.
I am from India ,and I found that my regional fonts(especially TAMIL) doesn't support with any of the custom ROM.
I tried copying fonts but doesn't work.
Then I recovered my stock firmware using recovery and tried to modify my stock ROM. I succeeded.
Its just a noob post but might help someone like me.
This is not only for S7562 but the links posted here is only for S7562.
STEP 1:
Rooting the device. Install superuser and clockworkmode recovery.
http://forum.xda-developers.com/showthread.php?t=2344909
STEP 2:
Create a nandroid backup using cwm recovery.
https://www.youtube.com/watch?v=7815OazAECQ
STEP 3: Removing system apps.
1.Download and Install ES file Explorer.
https://play.google.com/store/apps/details?id=com.estrongs.android.pop&hl=en
2. Open ES explorer.
3. Go to Settings.
4. Click on the Root Explorer
5. Allow superuser permissions.
6. A popup menu appears. Select "One Key Uninstall" feature. Go to system apps.
7. Click and Hold to select multiple apps. Select all the unwanted apps like Samsung apps,chat on,chrome,email,gmail,video player etc.
8. Uninstall all.
STEP 4: Decreasing RAM usage
1. Download and Install Exposed Framework and Greenify.
https://play.google.com/store/apps/details?id=com.oasisfeng.greenify
http://forum.xda-developers.com/showthread.php?t=2497957
2. Open Exposed Framework.
3. Go to Framework and select install\update to activate framework.
4. Go to Module Tick the box of greenify to activate module.
5. Then Reboot to make effect in changes.
6. Now open greenify and select apps you want to hibernate.
7. Select the apps that are running in background. example Facebook ,Twitter, messenger, uc browser etc.
8. Go to menu and click put into hibernation now.
9. This will hibernate all the apps and free the RAM.
STEP 5: Increasing Performance
1. Download and install no frills CPU control app.
https://play.google.com/store/apps/details?id=it.sineo.android.noFrillsCPU&hl=en
2. Open it and select the max and min freq.
3. Set the governor as performance.
4. Click on apply on boot.
5. Download Kernel from here and flash it through cwm.
http://forum.xda-developers.com/showthread.php?t=2431352
6. Now open the app again and set the max freq as 1.306Ghz.
STEP 6: Changing Appearance
1. Select and Download any theme from here. Flash it through cwm.
http://forum.xda-developers.com/showthread.php?t=2324451
2. Select and download any boot animation from here.
http://forum.xda-developers.com/showthread.php?t=2349033
3. Flash it or just copy bootsamsung.qmg,shutdown. qmg and bootsamsungloop.qmg to ext SD card.
4. Use root explorer or es file explorer to copy the qmg files into
/root/system/media/ and /root/system/media/video/shutdown/ to their respective locations
5. Flash files from here for lock screen animation effects.
http://forum.xda-developers.com/showthread.php?t=2331555
6. If you love any other effects in the custom ROM like PMP lite or ultra or L touch ROM(ROMs of s7562 ONLY), copy systemui.apk from /system/app and paste it in your root directory.
STEP 7: Installing a Launcher
1. I am using Nova launcher. It has some animation effects and also uses 20-36MB of RAM.
I suggest to restart the system on every steps. In case some kind of error occurred, just use recovery and skip that particular step or something.
{
"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"
}
Your system ui is awesome.can you provide me?
Hey everyone, in this guide I will show you how you can get 24bit audio processing on your beloved rosy.
Keep in mind that I WILL NOT provide a bunch of files for you to change within your root, because audio xml's changes a lot and its hard to keep track for me as to which files will work and which won't. So rather, I will provide a way for you to edit those files on your own.
Requirements:-
1. Rooted with Magisk
2. A File manager (ex. MiX) with root permission granted
3. Note Editor (You can use MiX note editor)
4. Terminal Emulator like Termux to test if the method worked or not
5. Some Common Sense
ROMs I tested this on:-
1. LOS by Pulkit
2.RevengeOS by Pratyakshm
3.PixelExperience
4.AOSP11 by Pulkit
This method should also work on:-
1. Any Android 10 based ROM
I cannot say about android 9 or the version's before that because i never tested them, however if someone is willing to do that, let me know in the post replies and make sure you follow the guide.
Before we start, MAKE SURE TO BACKUP YOUR OLD FILES IN CASE ANY PROBLEMS ARISES LIKE BOOTLOOP'S.
So the steps are as Follow:-
1. Open up MiX or any of the file manager that you have then head over to /vendor/etc .
2. In there, find "audio_policy_configuration.xml" .
3. Take backup of this file and then open "audio_policy_configuration.xml" .
4. Under <mixPort="primary output"> profile name would be written as "AUDIO_FORMAT_PCM_16_BIT" change this string to "AUDIO_FORMAT_PCM_24_BIT_PACKED" .
5. Follow the same process as given in Step 4 for <mixPort = "raw"> , <mixPort = "deepbuffer"> and <mixPort = "direct pcm"> .
6. Scroll down the section of <device_port> and replace the string shown above for <Wired_Headset>, <Wired_Headphones>,<BT_SCO>,<BT_SCO_Headset>,<Line>.
- - Refer to the Screenshot Attached below, That will be enough for you to understand it properly.
{
"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"
}
6.This step is only for people who also have the file audio_policy.conf in vendor/etc directory.
>> under primary > outputs , change format to "AUDIO_FORMAT_PCM_24_BIT_PACKED" for primary, raw & deep_buffer. [Screenshot attached below]
6. Save the file and put it back in /vendor/etc and give chmod 0644 [-rw-r--r--] .
7. Reboot your device.
- - At this point if your Phone doesn't boot, use TWRP to replace the new file [edited] with the Old one [unedited] file and message me on telegram @bancelhub so that I could look into the matter.
PROFIT!
How to check if it's working.
1. Open up termux with su.
2. Type "dumpsys media.audio_flinger"
3. AudioOut_D and AudioOut_1D should show "AUDIO_FORMAT_PCM_24_BIT_PACKED" as HAL Format. [Refer to Screenshots Attached]
Hope this guide was good enough, this was the first guide I wrote on xda. You might have noticed that I only explained how to do this on one device tree, Pulkit one's, since his dt is public I used it to show this experiment. You can try it on other ROM's based on other DT's but your procedure may vary, mildly. let me know your experience on telegram!
Happy Editing!
Awesome !!
Thanks for detailed guide :good:
Nice Guide ,Working