Related
Hi,
4.2 of Jelly Bean update could be imminent for my Nexus 7, and I'm wondering about what and how to backup before the update. The question I think is a general android one though... which is why I'm posting it here.
This was going to be a question about factory reset... but reading other posts I think I now understand that factory reset just deletes data/cache, so I think any time you do that it's just gonna return the device to a clean ROM state without changing the ROM. (whatever flavour/version ROM is)
When a ROM update is applied (either official or manually flashed), I guess it wipes everything, is it like a disk format or something like that? I have installed CWM recovery and rooted my device, I think the update will unroot it, but will the CWM recovery still be loaded?
And then, what backup should I take before the update... I think a Titanium Backup is a must, I understand how that works. But a Nandroid backup too? Or is that more like taking a disk image, would that be useless to restore after the ROM has been updated? And if so, does that mean any old Nandroid backups should be discarded?
Once the new update to 4.2 is installed, is it advisable to take a Nandroid backup immediately, or better to download the stock 4.2 image and keeping it as a starting point? (does this amount to the same thing?) I guess this is where a factory reset would return it to stock (providing I haven't moved anything to the system apps)?
Or is it possible/better to use a Nandroid backup as a point in time image of everything that's been installed on the device after adding back all the apps etc? I guess that leads me to wonder if the Nandroid backup is needed at all if I'm going with the Titanium Backups...
Thanks a lot and sorry for the lengthy question, I've seen many posts touching on this
stillchimp said:
Hi,
4.2 of Jelly Bean update could be imminent for my Nexus 7, and I'm wondering about what and how to backup before the update. The question I think is a general android one though... which is why I'm posting it here.
This was going to be a question about factory reset... but reading other posts I think I now understand that factory reset just deletes data/cache, so I think any time you do that it's just gonna return the device to a clean ROM state without changing the ROM. (whatever flavour/version ROM is)
When a ROM update is applied (either official or manually flashed), I guess it wipes everything, is it like a disk format or something like that? I have installed CWM recovery and rooted my device, I think the update will unroot it, but will the CWM recovery still be loaded?
And then, what backup should I take before the update... I think a Titanium Backup is a must, I understand how that works. But a Nandroid backup too? Or is that more like taking a disk image, would that be useless to restore after the ROM has been updated? And if so, does that mean any old Nandroid backups should be discarded?
Once the new update to 4.2 is installed, is it advisable to take a Nandroid backup immediately, or better to download the stock 4.2 image and keeping it as a starting point? (does this amount to the same thing?) I guess this is where a factory reset would return it to stock (providing I haven't moved anything to the system apps)?
Or is it possible/better to use a Nandroid backup as a point in time image of everything that's been installed on the device after adding back all the apps etc? I guess that leads me to wonder if the Nandroid backup is needed at all if I'm going with the Titanium Backups...
Thanks a lot and sorry for the lengthy question, I've seen many posts touching on this
Click to expand...
Click to collapse
1. OTA updates should let you retain your apps.
2. Clockworkmod will still be installed following the update.
3. Nandroid backups are like a system image it makes a backup of everything on your phone (Minus sd card external) at the exact point in time when you make the backup. If you restore the backup it will restore your phone to the exact state it was in when you made the backup. You only need to keep a couple of your recent nandroid backups on your phone.
4. After the 4.2 update you can either make a backup or use a factory restore image it will make no difference. Factory reset would return it to stock.
5. You can use nandroid to make a backup after you install your apps in fact I would recommend this that way you have a convient restore point. You can also backup your apps with titanium backup.
Hope this answers some of your questions .
Sent from my SCH-I535 using xda premium
shimp208 said:
1. OTA updates should let you retain your apps.
2. Clockworkmod will still be installed following the update.
3. Nandroid backups are like a system image it makes a backup of everything on your phone (Minus sd card external) at the exact point in time when you make the backup. If you restore the backup it will restore your phone to the exact state it was in when you made the backup. You only need to keep a couple of your recent nandroid backups on your phone.
4. After the 4.2 update you can either make a backup or use a factory restore image it will make no difference. Factory reset would return it to stock.
5. You can use nandroid to make a backup after you install your apps in fact I would recommend this that way you have a convient restore point. You can also backup your apps with titanium backup.
Hope this answers some of your questions .
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Excellent, thanks for the fast reply, you did answer my questions!
I was misunderstanding then about the 4.2 update, thinking it was equivalent to flashing a new ROM... you clarified it for me, seems it's less severe than that.
I think I'll go with your point 5 to use a Nandroid image for a convenient restore point after the OTA happens
Can someone help me understand when I should use one or the other. Also when is a good time to do it?, before a flash of a custom rom?
I recently performed the bootloader unlock procedure from Adam and after it completed I ran the twrp backup to my sd card. Does that mean I could restore to that backup should verizon send ota and revert the unlock?
Thanks!!!
JRunner01 said:
Can someone help me understand when I should use one or the other. Also when is a good time to do it?, before a flash of a custom rom?
I recently performed the bootloader unlock procedure from Adam and after it completed I ran the twrp backup to my sd card. Does that mean I could restore to that backup should verizon send ota and revert the unlock?
Thanks!!!
Click to expand...
Click to collapse
Titanium would be used when you want to backup all of your apps+data, Twrp would be used when you want to back up EVERYTHING apps, messages, pics(on internal sd), basically everything lol. As for verizon sending a ota, I think it's highly unlikely that they can push a ota to our phones now I think the bootloader unlocking and rooting broke all of that. Especially if you run a custom Rom.
Sent from my rooted, and unlocked Vzw note 2 running beans Rom! U mad?
JRunner01 said:
Can someone help me understand when I should use one or the other. Also when is a good time to do it?, before a flash of a custom rom?
I recently performed the bootloader unlock procedure from Adam and after it completed I ran the twrp backup to my sd card. Does that mean I could restore to that backup should verizon send ota and revert the unlock?
Thanks!!!
Click to expand...
Click to collapse
Titanium is backing up apps. So lets say you use CleanROM and you want to flash to a newer version cleanly. Use titanium to back up the apps and you will be able to restore them easily on the new rom.
Backing up via TWRP basically means you are backing up EVERYTHING in the rom. So lets use the previous example, uograding from one rom to another. You do a twrp back up and begin to flash the new rom. If anything screws up, you could just restore the twrp back up and everything would go back to normal, back exactly to how your phone was when you made the backup.
Edit: basically a back up in recovery is creating a safe point to come back to if anything goes wrong EVER with your device. There are things that this typenof back up cannot undo however.
Titanium is for apps and that's it. It helps free up space as well as making backups for apps incase on of your apps screws up.
EDIT 2: next time post this type of thing in Q&A and not in general
Sent from my SCH-I605 using xda premium
Titanium Backup - Used to back up all of your apps and their data
TWRP - Used to back up the ENTIRE system. Meaning, if anything goes wrong, you can restore a past "save" of your system before the problem.
You can think of it as Titanium Backup would be like copying a MS Word document onto a flash drive and TWRP would be like taking a copy of your entire hard drive.
JRunner01 said:
Can someone help me understand when I should use one or the other. Also when is a good time to do it?, before a flash of a custom rom?
I recently performed the bootloader unlock procedure from Adam and after it completed I ran the twrp backup to my sd card. Does that mean I could restore to that backup should verizon send ota and revert the unlock?
Thanks!!!
Click to expand...
Click to collapse
Titanium backup: for backing up apks and their datas, mms and calling history, bookmarks, alarm and wifi settings....i think that's about it. Because your apks keep updating every few days, you should make this backup right before you flash a new rom. Once you retrieve, you don't have to keep this too long.
TWRP backup(aka nandroid): this is just like a saved point when you play a video game. sometimes when you download something, it can alternate other settings and create a mess.....which then may cause your rom to malfunction. At this time, you can flash your nandroid.....it dumps every saved datas, cache, etc etc so that you can go back to your saved point.
Titanium back up- is a app that backs up applications and their data...also has the ability to freeze system apps and create back up .zips of the devices applications.
TWRP back up- is a custom recovery that allows the user to create a back up image... that image will restore the boot image, rom, kernel, data, and cache back to the point of when the back up was created.
It used to be that restoring titanium data from one rom to another was bad. Is this still a recommended no no?
Sent from my SCH-I605 using Tapatalk 2
Pretty much.
Please read forum rules before posting
Questions go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
First thanks to everyone for the replies!!!
Sorry for posting in wrong section.
So I cant use titanium to backup my apps, then to be restored on a custom rom, since I am on what appears to be a stock / rooted rom from Adams unlock procedure? I would have to reinstall them from google / my apps.
My twrp backup would be useful if the custom rom I soon load goes bad any I need to get back to a good state, right?
Also as on reply said, no worries from ota since we are rooted and unlocked? You all agree?
JRunner01 said:
First thanks to everyone for the replies!!!
Sorry for posting in wrong section.
So I cant use titanium to backup my apps, then to be restored on a custom rom, since I am on what appears to be a stock / rooted rom from Adams unlock procedure? I would have to reinstall them from google / my apps.
My twrp backup would be useful if the custom rom I soon load goes bad any I need to get back to a good state, right?
Also as on reply said, no worries from ota since we are rooted and unlocked? You all agree?
Click to expand...
Click to collapse
yes you can use titanium to back up your apps and restore them on a custom rom...just restore the apps without data. you have the rest correct.
I always restore my user apps with data, I just don't do system apps.
pool_shark said:
I always restore my user apps with data, I just don't do system apps.
Click to expand...
Click to collapse
great...but when switching between aosp and touchwiz this can cause apps to force close. the op said "custom rom" so i provided a blanket statement covering all bases.
droidstyle said:
great...but when switching between aosp and touchwiz this can cause apps to force close. the op said "custom rom" so i provided a blanket statement covering all bases.
Click to expand...
Click to collapse
I restored all of my apps user that I used on JBSourcery from my Nexus to my Note II.
I think the main problem some people have with restoring their apps is that they're restoring system apps not just user apps. Sometimes what was a user app on one ROM is a system app on another.
pool_shark said:
I restored all of my apps user that I used on JBSourcery from my Nexus to my Note II.
I think the main problem some people have with restoring their apps is that they're restoring system apps not just user apps. Sometimes what was a user app on one ROM is a system app on another.
Click to expand...
Click to collapse
I agree that folks get into trouble because of what you posted in your last sentence. This is exactly why I do not recommend it because a new user 99% of the time wont know that. So I simply do not suggest it...now somebody more experienced like yourself is a different story.
pool_shark said:
I restored all of my apps user that I used on JBSourcery from my Nexus to my Note II.
I think the main problem some people have with restoring their apps is that they're restoring system apps not just user apps. Sometimes what was a user app on one ROM is a system app on another.
Click to expand...
Click to collapse
Disagree.
It won't always happen, but problems can and will happen restoring user data. I have seen it a million times and logcat shows it too. When there is a database conflict (the logcat shows this), the app force closes, and the only fix is to clear data for that app, which undoes what you restored. Might as well forgo the irritation and not restore it the first time.
adrynalyne said:
Disagree.
It won't always happen, but problems can and will happen restoring user data. I have seen it a million times and logcat shows it too. When there is a database conflict (the logcat shows this), the app force closes, and the only fix is to clear data for that app, which undoes what you restored. Might as well forgo the irritation and not restore it the first time.
Click to expand...
Click to collapse
It has yet to happen to me.
The only time it came close was with better terminal emulator pro. I restored using titanium and it refused to work. Downloaded it from the play store, it worked fine. Then restored over that using titanium and it worked fine.
Anyone have any advice on creating the .zip? Is it even a possibility in TWRP? I used CWR for the longest and am a n00b with TWP. There are only 2 options when creating the update.zip: Edify (Android 1.6+, ClockworkMod 3+) and Amend (Android 1.5, ClockworkMod 2). So which is needed to flash in TWRP?
I'm not interested in creating a .zip of all my apps, just a .zip I can flash in recovery after clean wipe/flashing a new ROM. TIA guys
So I get the fundumental difference between utilizing the 2 methods of backing up but what I don't understand is that if TWRP backup is like taking a snapshot or image of EVERYTHING, why is my backup folder created from a TWRP backup such a small size (2.4GB) when everything on my phone equals way more than that? Is it compressed? I don't remember selecting that option.
airbus318 said:
So I get the fundumental difference between utilizing the 2 methods of backing up but what I don't understand is that if TWRP backup is like taking a snapshot or image of EVERYTHING, why is my backup folder created from a TWRP backup such a small size (2.4GB) when everything on my phone equals way more than that? Is it compressed? I don't remember selecting that option.
Click to expand...
Click to collapse
It only gets /system, /data, and kernel if you don't change the options. It's not getting everything on SD card or internal storage unless you specify that option.
One reason why I chose to buy this device (aside from official Google support) is the overwhelmingly large amount of developer enthusiasm for it. And with that enthusiasm comes a lot of custom ROMs.
I haven't had time to test all of them, but I will - and here's a guide I made that'll hopefully make testing different ROMs easier.
Prerequisites
Before continuing with this guide, make sure that you have:
a LOT of free time, depending on how many ROMs you want to test;
unlocked and rooted your device;
downloaded all the ROMs you want to test;
have installed a good recovery - I would recommend the latest version of TWRP;
common sense.
(OPTIONAL) a spare microSD card of at least 8GB. This'll make everything easier, as you won't have to delete stuff in order to fit all your ZIPs and backups.
Things to remember
Make sure you know how exactly to restore your device to how it was before following this guide.
You should know what you're doing. One small mistake can lead to your device being completely unusable!
You should know what features you're looking for in a ROM. It's never nice to have gone all the way to flash a different ROM, only to discover that feature X doesn't work. Ask questions in the ROM thread, if you like.
You can always ask help from others, should you have any trouble with your device.
When using custom ROMs (or any customization, for that matter), do NOT ask for ETAs. Our developers are doing their work at their own leisure and during their own time, and they don't get their pay from you.
Ready? Let's get going!
Getting started
A good Android user always backs up before doing anything radical to their phone, and that's precisely what we're going to do. There are three ways to go about this:
The easy way
The easy way is through making a Nandroid backup. This is particularly easy to do in TWRP, as all you need to do is reboot into recovery, press Backup, select the partitions you want to back up and whether to compress them, and start backing up. Simple as that.
Pros: Easy to restore your data once you're finished testing ROMs.
Cons: It's somewhat hard to restore individual pieces of data (such as messages and apps) instead of the whole thing.
The (slightly) more complicated way
This way deals with TitaniumBackup, an absolute must-have app for every Android user out there.
With TitaniumBackup, you can choose to back up individual apps (and even update their individual backups). TB isn't limited to backing up/restoring data, though; it can do so much more - remove bloatware, freeze apps you don't use, make a flashable ZIP out of your backups... the list goes on.
Pros: Finer control over what data gets backed up. Very powerful tool in migrating ROMs.
Cons: Somewhat outdated and intimidating interface; and features are reduced without buying the PRO version.
The Google way
This one is the simplest way of all three, though it only works if you have a) GApps and have signed in to your Google account, b) if you've agreed to let Google back your data up when you first set up your device, and c) if you have Settings > Backup & reset > Back up my data enabled.
Google automatically backs up almost all of your data to its servers, ready to be restored when you do a factory reset/switch to a new phone. A list of all data that are backed up can be seen by going to Settings > Accounts > Google > (your email address).
Notable exceptions to the data backed up are messages, which you have to back up yourself - I recommend SMS Backup & Restore for that.
Now that you have your data backed up, let's get flashing.
Flashing
Put your ROMs/kernels/GApps on your SD card, then reboot to recovery.
1. Wiping / factory resetting
This is why we back up your data in the first place. Different ROMs need different data, and data left over from one ROM can cause another ROM to get stuck in a bootloop.
Tip: If you're using TWRP, try enabling Use rm -rf instead of formatting in Advanced settings. Formatting doesn't really have any perceivable advantages over simply removing the contents of your data partition (unless you somehow corrupted it), and it actually causes higher wear on your storage chip. (Storage doesn't last forever - I've had my old Samsung bricked because I reformatted too much.)
Click to expand...
Click to collapse
In CWM, it's called wipe data/factory reset; in TWRP, it's simply called Wipe. Wipe your data, dalvik-cache, and cache partitions.
2. Flashing the ROM and other addons
In CWM, it's called install zip (from sdcard); in TWRP, it's simply called Install. Browse to your ROM zip and install.
Tip: If you're using TWRP, you can add ZIPs to the ZIP queue in this order: ROM > GApps (if any) > Kernel (if any) > Addons/Patches (if any).
Users of CWM must manually flash each ZIP, in the same order.
Click to expand...
Click to collapse
3. Finishing up
Now all that's left to do is pray for the best and reboot.
Testing
If you flashed GApps, do NOT let Google restore data yet. We'll do that later.
Click to expand...
Click to collapse
After initial setup completes and your newly-installed ROM settles down, it's time to get testing. It would be helpful if you listed down all the features you need and check/cross them out one by one if they work or not. For example, I need working screen cast and usable video recording, both of which do not work in all the CM-based ROMs I've tested.
Some ROMs, especially sprout4 ROMs, require patches when installing on sprout8 devices in order to provide the most optimal experience. Try flashing those to see if the ROM gets any better for you.
Rinse & repeat?
So, have you decided that this ROM is for you?
Yes, this ROM is awesome! I love it!
If you backed up earlier using Google, do another factory reset and this time, let Google restore your data.
If you used Titanium for backup, you can safely restore your data now.
If you made a Nandroid backup, you technically can restore your backup as-is since most of the ROMs available for sprout are CM-based; but I wouldn't recommend this as this can cause bootloops. Otherwise, you can manually restore your data one-by-one - but this is a time-consuming process.
I'm not quite sure I like this ROM yet.
Well that's okay, just repeat this guide from the start.
Finishing up
Now that you've decided on what ROM to use, you can safely delete your backups and ZIPs - though it would be better to keep them as they might come in handy if your device starts having problems.
Notes
If you're flashing a Marshmallow ROM, don't flash Xposed right after you flash your ROM as this may cause a bootloop.
Never ask for ETAs on ROM threads. That's rude.
That's it for this guide! Happy flashing! :fingers-crossed:
Reserved 1
Reserved 2
Reserved 3
Awesome post. Enjoyed it!?
aureljared said:
Reserved 3
Click to expand...
Click to collapse
Sry for digging up this old thread. I was wondering if there is a tutorial for Titanium Backup specifically targeting a switch between custom roms, having different versions of android.
I'm in the midth of moving from cm 13 to lineageos 15 and just tried to backup apps+data in Titanium Backup and restore them and the new system is now somewhat buggy..I'm not sure if the restored backup is the reason for this or not....Maybe there are specific settings to be set..... I mean it's common sense for me not to backup and restore system data but maybe I am missing other important things to be set prior to a backup in Titanium Backup.
trohn_javolta said:
Sry for digging up this old thread. I was wondering if there is a tutorial for Titanium Backup specifically targeting a switch between custom roms, having different versions of android.
I'm in the midth of moving from cm 13 to lineageos 15 and just tried to backup apps+data in Titanium Backup and restore them and the new system is now somewhat buggy..I'm not sure if the restored backup is the reason for this or not....Maybe there are specific settings to be set..... I mean it's common sense for me not to backup and restore system data but maybe I am missing other important things to be set prior to a backup in Titanium Backup.
Click to expand...
Click to collapse
It's hard to say, some apps might work improperly or refuse to terminate in the background due to a mismatch in the restored data. I only backup/restore game data nowadays, as Google Backup takes care of my contacts, SMS, settings, and customization. No problems encountered so far.
The only setting I change in TiBkp is the compression method, as the default (gzip, I think) produces somewhat large backups. I use bzip2.
If you really need to restore everything, it might help for you to wipe /data and restore apps in TiBkp one by one until you find the culprit.
aureljared said:
It's hard to say, some apps might work improperly or refuse to terminate in the background due to a mismatch in the restored data. I only backup/restore game data nowadays, as Google Backup takes care of my contacts, SMS, settings, and customization. No problems encountered so far.
The only setting I change in TiBkp is the compression method, as the default (gzip, I think) produces somewhat large backups. I use bzip2.
If you really need to restore everything, it might help for you to wipe /data and restore apps in TiBkp one by one until you find the culprit.
Click to expand...
Click to collapse
Trying the Google Way was also my thought, unfortunately it does not work for me. I posted this today in the rom I used until now:
https://forum.xda-developers.com/showthread.php?p=76022005#post76022005
The initial setup was quite some time ago and now I cannot recall what I may have done to insult the google sync service
Thanks for this.
Can I ask something?
If I'm on stock rom and have magisk and modules installed. To switch rom, do I need to uninstall those first?
or when using nandroid backup... is its okey to backup with magisk+module on it?
watatara.102 said:
Can I ask something?
If I'm on stock rom and have magisk and modules installed. To switch rom, do I need to uninstall those first?
or when using nandroid backup... is its okey to backup with magisk+module on it?
Click to expand...
Click to collapse
You might want to uninstall your modules first to be safe, but if you're sure they're compatible with the ROM you're switching to, then you might be fine keeping them. As always, backup before trying anything dangerous. :good:
Nandroids are whole-device backups, so if you backup while Magisk is installed, Magisk and your modules will still be there when you restore the backup. If that's what you're aiming for, then go ahead and backup. Just make sure to backup the boot image too, since that's where Magisk is installed.
Sent from my starlte using XDA Labs
Can I install a nandroid backup of a totally different ROM to replace the current ROM I'm using with TWRP?
Over the course of the last two years I have flashed the *expletive deleted* out of my Nine and gone through the set up countless times, because I wanted to, and mostly with childlike enthusiasm. Sometimes, like today, it's because I have to. I seem to fail more often than not restoring from TWRP, and recently sometimes with flashfire free version. I never seem to have a problem "testing" the backups after creation, without any major changes they restore without issue. My problems seem to arise after flashing a new rom or preview and then trying to revert back to my previous restores. More often than not these fail on me and I find myself , like today, looking at the set up screen.
What ways (free) work best to save/restore roms, and what the hell am I doing wrong with my back ups? I have a basic grasp of ADB/fastboot. But it appears I have just enough info to be dangerous.
I blame the Vendor partition...
I've not had any problems with TWRP and restoring. I will add, however, that I don't backup the vendor partition. I have had problems with that before. I don't seen any real need to back up the vendor partition, though, so I just exclude that. I keep copies of the vendor image for the ROM that I flash. If I need to restore a backup, I restore it and then flash the original vendor image for that ROM version again.
I don't back up at all any more now that Google is able to reinstall all your apps when performing a fresh install. Just install the rom, choose the restore and let Google do its thing whilst I crack on with other things.
I've had several issues with TWRP backups on 6.x and 7.x, so now I use FF over ADB to make a "NORMAL" backup to my PC. I also use TiBu for apps and store a zip file of the complete TiBu folder on my PC.
Hi! So, I have a newer Android 10 device with no TWRP support. I think my question is not model specific, so I'm posting generally, but if it matters, it's a OnePlus 7T Pro, bootloader unlocked of course.
Anyway, since there's no good custom recoveries for Android Q (none that I know of that can decrypt /data), I was trying to be safe and using a hacked (adb enabled) stock recovery to make backups from the command line. I have a nice tarball created in recovery mode with "tar cvf - /data/". It looks like it was made properly, I can unpack the files on back onto the device in recovery mode, and it's not corrupt or anything.
The problem is that naively trying to restore it back to my /data partition (e.g. tar xvf) after a wipe causes two problems:
1) after rebooting to recovery, the /data partition just looks encrypted again. If it was working properly, stock recovery can decrypt /data
2) normal system boot just bootloops.
If anyone has tried manually saving and restoring /data from a tarball, I'd appreciate any tips on getting it to work.
My best guess is that the ext4 encryption keys are the culprit - since after a factory reset the device creates new encryption keys, I think I need to figure out how to restore 99% of my backup without overwriting the fresh encryption keys that were created after wiping. I think I need to combine the new encryption keys with the other files in my tarball backup. If I can get past that, I might have to worry about things like SELinux xattrs as well, but one thing at a time.
If any experienced Android hackers know how filesystem encryption works in Android 10, I would appreciate a map of which files should not be overwritten. For example, I'm thinking I should probably avoid restoring some of these files:
Code:
/data/unencrypted/key
/data/unencrypted/key/encrypted_key
/data/unencrypted/key/keymaster_key_blob
/data/misc/vold/user_keys
/data/misc/vold/user_keys/de/0/keymaster_key_blob
/data/misc/vold/user_keys/de/0/encrypted_key
/data/misc/vold/user_keys/ce/0/current/keymaster_key_blob
/data/misc/vold/user_keys/ce/0/current/encrypted_key
/data/misc/systemkeys
/data/misc/keystore
/data/misc/keychain
/data/system/recoverablekeystore.db
[edit] spoke too soon
I ended up doing something janky and wrote a little shell script to repack the files from /data/data and /data/app into files that Titanium Backup could understand. I also figured out how to restore my SMS messages from /data/user_de. That was enough to recover the things I cared most about.
Still begs the question of what's the best method of doing backup and restores of /data on Android 10 when you don't have custom recovery but you do have Magisk, root, and stock recovery with adb. I want to keep hacking and playing with this phone so gotta figure something out.
I like Titanium Backup, have used it for many years, but the maintainance hasn't really kept up with Android development, theres a lot of gotchas like it hangs trying to restore multi APK packages. I still want to figure out something more seamless like a nandroid backup solution even if its from the command line. At least until TWRP eventually supports Android 10.
try backing up data partition in a external storage live usb or sd card
DrWowe said:
I ended up doing something janky and wrote a little shell script to repack the files from /data/data and /data/app into files that Titanium Backup could understand. I also figured out how to restore my SMS messages from /data/user_de. That was enough to recover the things I cared most about.
Still begs the question of what's the best method of doing backup and restores of /data on Android 10 when you don't have custom recovery but you do have Magisk, root, and stock recovery with adb. I want to keep hacking and playing with this phone so gotta figure something out.
I like Titanium Backup, have used it for many years, but the maintainance hasn't really kept up with Android development, theres a lot of gotchas like it hangs trying to restore multi APK packages. I still want to figure out something more seamless like a nandroid backup solution even if its from the command line. At least until TWRP eventually supports Android 10.
Click to expand...
Click to collapse
try backing up data partition in a external storage live usb or sd card, first you for encryption, then restore from external source after formatting phone storage