Related
When I look in the the "Downloads" section of the Market app, it shows 3 apps constantly installing even though they aren't and they are not on the top of the list. They are Titanium Backup, AutoKiller, and XDA Developers. I can use these apps without issue. When I try long pressing any of these items, only an the option "Details" pop up and going to the page is also useless. I tried uninstalling Titanium Backup to see if it would get rid of it but it doesn't and now I cannot reinstall Titanium Backup since I cannot cancel the false installation! Shutting off the phone and reflashing my Rom does not help. If I need to wipe may I have the Titanium apk so I can adb install it to my phone?
Edit: Never mind I fixed it.
Titanium Backup has been one of the most popular apps on the market for some time, and with good reason. It can be used to backup all your important app dada, system data, and even WiFi passwords on your handset.
Now, Android is a very stable operating system, and it’s pretty rare to run into a system or app killing bug. Even so, it’s better to be safe than sorry, you never know when a crippling update or malicious app might cause a problem. If you’re planning on removing apps using your newly found root permission or are planning to install custom versions of Android, then backing up your device is essential.
First things first, you’ll need a rooted handset before you can use Titanium Backup. Following that the app will need to be granted root permissions on your handset, but that’s simple enough. You’ll be prompted by Superuser once you run Titanium Backup, and can select to give it permanent access so you won’t be prompted again.
One word of caution before we proceed. If you’re using Titanium Backup to restore apps in between installing ROMs DO NOT attempt to restore system apps or their data across ROMs, as this will cause all sorts of crashes. Individual apps work fine, but system data will be incompatible.
Now that everything is setup we can begin.
Performing a mass backup
At first glance, Titanium Backup doesn’t appear to have the friendliest looking interface, the black and grey theme could certainly use a makeover. But don’t let that put you off, everything you need is actually very easy to find.
Frustratingly though, probably the most useful tool for performing a mass backup is actually hidden in another menu, rather than on the Backup/Restore tab where you’d think it would be. Instead, click the Menu button on your handset, and then select the “Batch actions” option under the “General” section, it should be the second option on the list.
Batch actions can be accessed from your devices menu button, or via the icon in the top left of Titanium’s home screen.
Batch actions can be accessed from your devices menu button, or via the icon in the top left of Titanium’s home screen.
The all-important backup section is located right here, giving you a wide variety of options regarding app and system data. System data includes Bookmarks, WiFi information, calendar events, etc. If you’re performing a backup for the first time then want to use the “Backup all user apps + system data” option, or at the very least the “all user apps” function. Clicking “Run” will present you with several more options to refine exactly what you’d like to backup. Once you’re satisfied with the selection, tap the green tick in the top right to begin the backup.
Patience is the key here as this can take a while, especially if you have lots of large apps installed.
If you’ve performed backups in the past and simply want to make a backup of newer apps you’ve installed recently, the “Backup new user apps” option on the “Batch actions” menu is the best choice. Alternatively, you can use the “Backup/Restore” tab on the Titanium homepage to select individual apps to backup.
Creating a recovery backup .zip file
Whilst the above backups will protect you from most bugs, they won’t be of much use if you experience a severe error that prevents your device from booting properly, such as corruption in a system file, or a bugged out launcher. This is where recovery compatible .zip files come in handy, as the backup can be restored without having to boot into Android. However, this is a donate version only option, but might be worthwhile if you’re changing ROMs a lot.
Head on over to the batch options again and scroll down until you see the “Recovery Mode” category. Here you can select the apps that you’d like to include in the backup .zip file, choose between apps or data only, and name the .zip file appropriately so that you can remember what it is.
If you ever need to recover your device using this boot file, enter ClockworkMod recovery and choose install zip from SDCard.
Scheduled backups
Generating a backup every time you install a new app is a bit of a pain, and it’s unlikely that anyone will remember to make a backup every week or month anyway. Fortunately, Titanium Backup now includes a scheduled backup option.
Over on the main menu tap the “Schedules” tab and you’ll be presented with two options. The first choice labelled “redo backups for modified data” will schedule backups only for app data which have been changed since the last backup. This could include games or changes make to specific app data.
The schedule has plenty of options to control automatic backups, so you don’t have to mess around with Titanium regularly.
The schedule has plenty of options to control automatic backups, so you don’t have to mess around with Titanium regularly.
The second option is probably the most important, as it will backup any new apps, system data, and updates since the previous update. Click “edit” to make changes to the schedule. There are all the necessary options to adjust the time and date of when backups are generated, but users can also set the charge state of the device required before making a backup, so as to prevent shutdowns mid backup, and there’s also a choice regarding filters and what to do once the backup has completed.
Restoring from backup
Alright, you’re protected in case your handset suffers a minor meltdown, but the next important step is being able to restore your apps and settings should anything go wrong.
In the batch actions, yet again, you’ll find a list of options for mass restoring your data. “Restore missing apps with data” will replace any content that is missing from your handset after a wipe. Alternatively restoring all apps with data will replace any existing apps with the backed up versions of them created earlier. There’s also a rather helpful option to only restore newer versions of user apps if you’re reinstalling your system.
However, the option that’ll you’ll most likely be interested is the “restore missing apps + all system data” option, which will put everything back to where it was when you created the backup. Although I can’t stress enough, that system data shouldn’t be restore if you’re switching ROMs.
Batch and individual restores can both be performed. There are also some additional commands when looking up the options for each app.
Batch and individual restores can both be performed. There are also some additional commands when looking up the options for each app.
If you discover that a specific app has developed a fault, say after a bugged update, and you want to restore it to a previously saved version, then this can be done by clicking on the backup/restore option on the main page. Here you can pick the specific app or piece of data from the list. Once tapped, a list of backups will appear along with a list of other functions to create backups, etc. Here you can manage your individual app backups, or can restore the app to a specific date by clicking on the corresponding restore button.
Managing bloatware
Whilst looking at the specific apps you’ll probably have noticed the Freeze function. Freezing apps is a handy tool that will allow you to completely stop apps from running without having to uninstall them. Usually this is used on factory installed apps that you don’t want to use. This option is a paid for only function, but it’s very helpful if you want to stop an irritating tasks from running or to see how your handset will react before uninstalling a piece of software.
Root permission also means that Titanium Backup can be used to uninstalled unwanted apps and bloat ware. A word of caution before doing this with any pre-installed software, uninstalled essential apps can cause force close errors and even render your handset virtually unusable if not done with care, so I thoroughly recommend backing up your apps and system first, preferably with a recovery zip file too.
Special features
That’s the really important stuff out of the way, but Titanium backup includes plenty of additional advanced features if you want to make the most out of your backups.
Firstly, backup data can be imported from by going to Titanium’s main menu and scrolling down to the import backup option. So you don’t even need to store all your backups on your handset, the files can easily be moved back and forth from your PC to your phone.
Slower compression will save on storage space, but be prepared to wait a little while while backups are performed.
Slower compression will save on storage space, but be prepared to wait a little while while backups are performed.
If you’re short of internal memory storage, there’s also the option to move apps to the SD card. However, this will cause certain apps to malfunction, so it’s only recommended to use on software which don’t integrate closely with any other part of Android, such as games.
Titanium Backup features many more options under the configurations menu, including tweaks to the type of compression used to create backups, the maximum number of backups to keep for each app, and whether or not to store market links for apps. In fact, apps can even be disconnected from the marketplace, so automatic updates can be left on for apps but then manually disconnected for certain apps, if you so desire.
Cloud backups
An extra feature for those who purchase the PRO edition is the ability to send backup data to various online services, including Dropbox and Google Drive. Although not essential, these options are very helpful if you need to wipe your SD card, or if your SD card ever develops a fault. To enable syncing to one of these services, tap your phone’s menu button and then go to “Preferences”, the options are under “cloud sync settings”.
And that concludes our guide on Titanium Backup. Hopefully that’s everything you need to protect your handset from unexpected faults.
LG Optimus G Pro (AT&T) lg version 4.4.2. Titanium Backup used to back up the files. Now an error msg. appears, "backup failed - insufficient storage space". The phone has many gb of storage space available. Over 10 gb on ext sd card where i want everything backed up. HELP
Apps include Titanium Backup Pro, Super Su, Root Browser, Root Checker, Rom Manager, Rom Installer, Nextapp SDFix, (haven't used yet because Storage/Emulated/Legacy/Titanium Backup won't backup to internal storage either ). Note: Just turned 69. Life is still fun after retirement as long as you learn something new each day. Thanks XDA for being here.
SOLVED: Titanium Backup Pro - Backup failed: insufficient-free-storage-space-error SOLVED by TitaniumTrack Support
If you are running Android 4.4 and above, there is another troubleshooting process that you can try. You need to have SuperSU v2.16 and above. Once you have that, go into SuperSU's settings and look for "mount namespace separation" and uncheck it. This has also worked for a vast number of users.
You can also use an application called SDFix to try as a troubleshooting method:*https://play.google.com/store/apps/details?id=nextapp.sdfix&hl=en
Also, when setting up the Backup Folder Location in Titanium Backup preferences, look for a section where you can change the "Storage Provider" and try SDCard or Document Provider to fix the problem.
If the problem STILL persists, here's an explanation. The insufficient storage occurs for two main reasons:
- Its due to the fat32 filesystem limitation. See, fat32 has a limit of how large files it can handle at once. Once this treshold is reached, it will run out of "placeholders" for the data and start throwing the insufficient storage error.*
- Another known cause of this error is because of your device running our of RAM. While making backups, the RAM gets utilized to its maximum which causes the superuser application to be killed. When superuser is killed, Titanium Backup could not acquire root permissions to proceed with its process, causing the application to halt.
Here are some suggestions you can try:
- reduce the number of backup history to 1
- try backing up to a different folder location if you have a non-fat32 location?
- try backing up without encryption?
- try using the system busybox instead of the one with Titanium Backup.
This is currently how i keep my Galaxy Active 2 working - connected and Samsung Pay working - across ROM flashes without having to reset it every time, because resetting sucks
Please note: At time of writing theres no known way to keep BP Monitor calibration data (ive tried backing up and restoring the relevant database), so you will lose that
Prerequisites:
Apps:
Android ID Changer: I use this (Free) https://play.google.com/store/apps/details?id=com.silverlab.app.deviceidchanger.free
Migrate (Free Backup App) -
Main app: https://play.google.com/store/apps/details?id=balti.migrate
Flasher Module: https://play.google.com/store/apps/details?id=balti.migrate.flasher
Helper Module: https://play.google.com/store/apps/details?id=balti.migrate.helper
MyAPK: https://play.google.com/store/apps/details?id=com.andatsoft.myapk.fwa
Steps:
Install all the above on the ROM you're currently on
Use MyAPK (set MyAPK to save somewhere easily navigable) to make a backup of the following apks:
Android ID Changer
Migrate Flasher Module
Migrate Helper Module
Store them safely (i always use PC, as well as sdcard) as you'll want to use these before restoring your apps, and later to restore your apps
Important: Open Magisk Manager and set MagiskHide for all Samsung Wearables packages (Gear/Samsung/Watch/Watch Plugins), you do not have to select all sub-items under the main packages, just select the main packages
To prepare for a new ROM:
This largely only has to be done once....and then reused on subsequent new ROM flashes. I do things to make life easier for myself as in a bad week i can be testing 3 ROMS...
Note: The only steps you might want to do again are make a new Migrate backup (for new apps), and backup /data/adb, if you MagiskHide further apps in future
Steps:
Run Android ID Changer, copy Android ID to a text file or email (i store mine in both)
With a root capable file manager, or in custom recovery, backup /data/adb/magisk.db to a safe place (i always use PC, as well as sdcard))
Important Note: This assumes as mentioned above you have already used Magisk Manager to MagiskHide all Samsung Wearables packages (Gear/Samsung/Watch/Watch Plugins)
Backup your apps and data with Migrate
Note: for most apps you want to tick all 3 boxes per app, but DO NOTbackup up App Data (middle column for both) of:
Samsung Health
Samsung Health Monitor
As we would have to wipe this anyway after ROM flash to get them working. Save yourself the drama and untick them in Migrate. Migrate is smart enough that it stores your selections between backups, so if you make a next Migrate backup it will automatically leave these de-selected in future backups.
Your Migrate backup will be in /sdcard/Migrate, i recommend backing this up to PC as well
On the New ROM:
After a new ROM and Magisk flash:
Setup ROM
Copy Android ID changer from wherever you backed it up, install and open it, copy and paste your original Android ID into the middle (Edit) field, then click Apply
Reboot the device
Enable MagiskHide (Don't hide Magisk Manager yet)
Test for SafetyNet, and if need be use whatever method is preferred for your ROM to achieve SafetyNet
Copy magisk.db from wherever you backed it up back to device
With a root enabled file manager (or from custom recovery), copy magisk.db to /data/adb
Reboot device (Do not skip this trying to be clever)
Open Magisk Manager, it should hopefully not complain that you've just dumped magisk.db back (Note: you will not see the list of MagiskHidden apps, as they are of course not installed yet, but MagiskHide now already knows to block root detection to them when you do install them - if Samsung Pay even gets a whiff of root, it wont work and you will have to reset some, if not all Gear/Watch Plugins, and reset your watch and start from scratch)
Hide Magisk App via Magisk Manager > Settings > Hide The Magisk App, name it anything but Magisk Manager, i call mine App
Copy the following apps from wherever you backed them up to device, and install them:
Migrate Flasher Module
Migrate Helper Module
Run Migrate Flasher
Descend into the backup folder (listed by date & time), and select all the zips inside it, and flash them (Of course if you moved Migrate folder off the device, restore it to /sdcard first)
At the end open Migrate Helper (which is already installed) and restore all the apps you wish - of course for our purposes, we want all the Samsung ones.... Note: Migrate will automatically select all backed up apps and data
At the finish of Migrate restore, leave the default options selected, which will remove the Migrate Helper, and reboot
On phone, open Gear App and press Connect
On watch, you may need to toggle BlueTooth off, and back on
You may need scan a few times and perhaps toggle bluetooth off and on, but it will give you the usual pairing prompt, both on the phone, and the watch, pair, and shortly you will have the watch reconnected, and Samsung Pay intactNext steps:
Open Samsung Health and sign in and restore
Open Samsung Health Monitor, and sign in
Set up ECG as normal
Re-Calibrate the Blood pressure monitor as normal
On any new ROM from now on, you can:
Make a new Migrate Backup, to include any new apps
Make a backup of /data/adb/magisk.db if you MagiskHide any new apps
Then refer to the On The New ROM steps above....
Please let me know if you find an error or issue folks
73sydney said:
This is currently how i keep my Galaxy Active 2 working - connected and Samsung Pay working - across ROM flashes without having to reset it every time, because resetting sucks
Please note: At time of writing theres no known way to keep BP Monitor calibration data (ive tried backing up and restoring the relevant database), so you will lose that
Prerequisites:
Apps:
Android ID Changer: I use this (Free) https://play.google.com/store/apps/details?id=com.silverlab.app.deviceidchanger.free
Migrate (Free Backup App) -
Main app: https://play.google.com/store/apps/details?id=balti.migrate
Flasher Module: https://play.google.com/store/apps/details?id=balti.migrate.flasher
Helper Module: https://play.google.com/store/apps/details?id=balti.migrate.helper
MyAPK: https://play.google.com/store/apps/details?id=com.andatsoft.myapk.fwa
Steps:
Install all the above on the ROM you're currently on
Use MyAPK (set MyAPK to save somewhere easily navigable) to make a backup of the following apks:
Android ID Changer
Migrate Flasher Module
Migrate Helper Module
Store them safely (i always use PC, as well as sdcard) as you'll want to use these before restoring your apps, and later to restore your apps
Important: Open Magisk Manager and set MagiskHide for all Samsung Wearables packages (Gear/Samsung/Watch/Watch Plugins), you do not have to select all sub-items under the main packages, just select the main packages
To prepare for a new ROM:
This largely only has to be done once....and then reused on subsequent new ROM flashes. I do things to make life easier for myself as in a bad week i can be testing 3 ROMS...
Note: The only steps you might want to do again are make a new Migrate backup (for new apps), and backup /data/adb, if you MagiskHide further apps in future
Steps:
Run Android ID Changer, copy Android ID to a text file or email (i store mine in both)
With a root capable file manager, or in custom recovery, backup /data/adb/magisk.db to a safe place (i always use PC, as well as sdcard))
Important Note: This assumes as mentioned above you have already used Magisk Manager to MagiskHide all Samsung Wearables packages (Gear/Samsung/Watch/Watch Plugins)
Backup your apps and data with Migrate
Note: for most apps you want to tick all 3 boxes per app, but DO NOTbackup up App Data (middle column for both) of:
Samsung Health
Samsung Health Monitor
As we would have to wipe this anyway after ROM flash to get them working. Save yourself the drama and untick them in Migrate. Migrate is smart enough that it stores your selections between backups, so if you make a next Migrate backup it will automatically leave these de-selected in future backups.
Your Migrate backup will be in /sdcard/Migrate, i recommend backing this up to PC as well
On the New ROM:
After a new ROM and Magisk flash:
Setup ROM
Copy Android ID changer from wherever you backed it up, install and open it, copy and paste your original Android ID into the middle (Edit) field, then click Apply
Reboot the device
Enable MagiskHide (Don't hide Magisk Manager yet)
Test for SafetyNet, and if need be use whatever method is preferred for your ROM to achieve SafetyNet
Copy magisk.db from wherever you backed it up back to device
With a root enabled file manager (or from custom recovery), copy magisk.db to /data/adb
Reboot device (Do not skip this trying to be clever)
Open Magisk Manager, it should hopefully not complain that you've just dumped magisk.db back (Note: you will not see the list of MagiskHidden apps, as they are of course not installed yet, but MagiskHide now already knows to block root detection to them when you do install them - if Samsung Pay even gets a whiff of root, it wont work and you will have to reset some, if not all Gear/Watch Plugins, and reset your watch and start from scratch)
Hide Magisk App via Magisk Manager > Settings > Hide The Magisk App, name it anything but Magisk Manager, i call mine App
Copy the following apps from wherever you backed them up to device, and install them:
Migrate Flasher Module
Migrate Helper Module
Run Migrate Flasher
Descend into the backup folder (listed by date & time), and select all the zips inside it, and flash them (Of course if you moved Migrate folder off the device, restore it to /sdcard first)
At the end open Migrate Helper (which is already installed) and restore all the apps you wish - of course for our purposes, we want all the Samsung ones.... Note: Migrate will automatically select all backed up apps and data
At the finish of Migrate restore, leave the default options selected, which will remove the Migrate Helper, and reboot
On phone, open Gear App and press Connect
On watch, you may need to toggle BlueTooth off, and back on
You may need scan a few times and perhaps toggle bluetooth off and on, but it will give you the usual pairing prompt, both on the phone, and the watch, pair, and shortly you will have the watch reconnected, and Samsung Pay intactNext steps:
Open Samsung Health and sign in and restore
Open Samsung Health Monitor, and sign in
Set up ECG as normal
Re-Calibrate the Blood pressure monitor as normal
On any new ROM from now on, you can:
Make a new Migrate Backup, to include any new apps
Make a backup of /data/adb/magisk.db if you MagiskHide any new apps
Then refer to the On The New ROM steps above....
Please let me know if you find an error or issue folks
Click to expand...
Click to collapse
My God! That's a lot of steps.
But you've written them down quite clearly.
This will certainly be helpful for those that like to flash ROMs frequently but don't want the hassle of setting up the watch again everytime you flash a new ROM on the phone. And of course, keeping Samsung Pay working successfully with root, while jumping across ROMs is quite impressive.
enigmaamit said:
My God! That's a lot of steps.
But you've written them down quite clearly.
This will certainly be helpful for those that like to flash ROMs frequently but don't want the hassle of setting up the watch again everytime you flash a new ROM on the phone. And of course, keeping Samsung Pay working successfully with root, while jumping across ROMs is quite impressive.
Click to expand...
Click to collapse
Once you have it set up the process is rather simple and i did have some help with the suggestion it might be tied to the Android ID....so i have to give @Dante63 some credit here (https://forum.xda-developers.com/t/galaxy-watch-features-ecg-bp.4051141/post-84652975)
Hehe If you want to see steps, and lots of words, visit the "My Magisk method for Google Pay SQLite Fix (Tested On P/Q/R)" link in my signature
Luckily at the moment that module isnt needed, but it had its fair share of downloads (23,000+) until recently when Google changed something on the backend again, and you can use Google Pay without it on a rooted device
Honest question: is SHealth so retarded that it doesn't save any backup in cloud, so that it could be restored afterwards?
w41ru5 said:
Honest question: is SHealth so retarded that it doesn't save any backup in cloud, so that it could be restored afterwards?
Click to expand...
Click to collapse
Samsung Health Does - All your steps etc are safe and can be restored after signing back in
Samsung Health Monitor (which calibrates and tests ECG/BP) does not.....
Hello,
since Titanium Backup which I used for years seems to not work anymore, I am now looking for any other possibilities to transfer my apps+app data and also some system settings like wifi passwords/APN data, BT connections and such.
With TB this was always well working for me.
What I have tried:
OAndBackupX -> I enabled "special backups" and tried to backup wifi, but sadly it just creates a new folder for the wifi backup (special.wifi.access.points) with a properties file. However the subfolder, where the backup should be present is empty.
So this solution doesn't seems to work, at least not on my phone with Android 8.
I also tried to do backups of some apps, however it looks a bit strange to backup an app that shows as 25mb and the base.apk which gets created for it is only 9mb (and no other file besides that, although everything was ticked for backup)
How is everyone here doing this when switching from one phone to another (especially for access point data and data of apps)?
Syncing wifi passwords to google cloud I somehow do not want (even if they're encrypted) and the issue with app+app data is still present then.
Annil said:
Hello,
since Titanium Backup which I used for years seems to not work anymore, I am now looking for any other possibilities to transfer my apps+app data and also some system settings like wifi passwords/APN data, BT connections and such.
With TB this was always well working for me.
What I have tried:
OAndBackupX -> I enabled "special backups" and tried to backup wifi, but sadly it just creates a new folder for the wifi backup (special.wifi.access.points) with a properties file. However the subfolder, where the backup should be present is empty.
So this solution doesn't seems to work, at least not on my phone with Android 8.
I also tried to do backups of some apps, however it looks a bit strange to backup an app that shows as 25mb and the base.apk which gets created for it is only 9mb (and no other file besides that, although everything was ticked for backup)
How is everyone here doing this when switching from one phone to another (especially for access point data and data of apps)?
Syncing wifi passwords to google cloud I somehow do not want (even if they're encrypted) and the issue with app+app data is still present then.
Click to expand...
Click to collapse
This was the biggest pain in the ass. I tried plugging my old phone into the new phone but my old phone died midway through so I basically just started fresh. it sucks I have been doing it all last night and this morning and haven't finished. I did use sms back up & restore to get my text messages other than that everything is fresh and annoying.
No one else facing issues with backup/transfer? How is everyone transferring nowadays their appdata and access points and such? Really curious....
Got two phones here (Pixel 6 + Pro) waiting for transfers and I am still not sure how to accomplish completely...
Glad about any inputs!
A lot of people are recommending Swift Backup which is supposed to be the successor to Titanium Backup. I haven't tried it myself though.
If I understand correctly, Swift Backup also requires root to restore app data, network settings etc.
The best backup/restore solution I found was Google One's built in. It just works (albeit not as well as, say, iOS, and definitely not up to the level of Swift/Titanium). Without root, sadly, you won't have many options as you're limited to the APIs Google provides, which themselves are limited. Swift works this around by "manually" backing up all the files/folders for every app.
I do have google one, but sadly most apps I would require, get only backed up for the APK but not the data
Is Titanium Backup now deprecated for latest Android? I have Android10 on a car head unit with a very customised oem Launcher. I managed to root it with universal root from here and Magisk (Thanks). Titanium shows me all the installed apps and bloat with sizes - great!. I want to make a backup of an App in the oem system folder before deleting it. I seem to be able to create a backup on mnt/sdcard, but I can't delete the oem app?
I have 2 system folders, System\ and system (root). They appear mirrors of each other and if I go to system(root) /oem/app/*My bloat app, I can delete it with FX root file browser. But not if I go to folders inside System\. Is this something to do with how Magisk roots and can restore to non root by creating a mirror folder? I used TB to make a backup of this bloat app and it worked. But after deleting the app successfully with a file browser the TB backup folder was empty - is this normal? With one pre-installed (Russian!) nav app I didn't need or trust, I recovered 4.5Gb of memory with more oem apps to look at.
For now I can use TB to locate bloat apps I want to remove with a file browser but I really wanted to back them up first and delete from within the app. Is TB trying to delete from system\ where access seems denied, rather than system(root) where I can delete files with a root explorer? Any help appreciated - Thanks
TB is pretty much dead...
i started using Swift.. and also https://forum.xda-developers.com/t/...mate-app-manager-debloat-tool-tweaks.4147837/
Thanks, I was guessing that from the age of posts in this thread. I started off thinking I wanted a full Nandroid backup but that requires a customised TWRP partition and AFIK this car head unit with its OE launcher doesn't seem to follow the partition structure I'm used to in phones. It has 3 external USBs and I can't get it to do anything with adb and a pc connected. The USBs are only active towards the end of boot. However, their factory image and unversal root seems to get picked up with the same 'Upgrade' screen messages from the folder Isec_updatesh. I don't know what I'd do if I bricked it, although I have found the OE Boot.img file packed in their update folders.
Thanks for the link to bloat removal. Nandroid backup creates a full rom image whereas most other backup apps seem to only backup apks and not system files. Android car head units are heavily customised with many added hardware based peripherals so a full backup is important to me. Adb might offer a solution, but as I said, even in developer mode I can't get the USBs to talk to a pc which I assume is because there isn't the usual recovery mode, unless it's on button press combos I haven't found yet? There is a recovery to factory reset, but it's an option in their launcher so I'm guessing it's not in the usual Android recovery partition?
OK I took a quick look at ADB AppControl. First I need to establish an ADB link from PC and I'm struggling with that. Second it does what some other non-root apps do which is to hide the bloatware and stop them running when my objective is to take the 16Gb+ memory they filled from 32Gb and recover memory by deleting bloatware and apps I don't need. There's a tendency now to sell these Chinese car head units with all the GAPPS and many more pre-installed. Unfortunely, most require a mobile network connection to function. I'm not interested in their Satnav, Google maps, Facebook or other social media apps they threw in. The one thing going for me now is I'm running AFwall+ which is the best reason for rooting a Chinese sourced device to stop data leaks to them or Google.
As I ran their factory 'update' I could see all these apps getting installed. If I was clever enough to understand how the Android 10 install 'Manifest' (my words) worked, I would prefer to edit out entries for OE apps in their installer, if it was possible?