Preforming a back up - Thunderbolt General

Just a quick note for all the people that back up app system data and user data. You may experience some f/c when restoring to a new rom. Every rom is slightly different, and when restoring both the system and user data to a new rom, the is a good chance their wil be bugs.
If you restore all this application system and user data from rom "A" to rom "B" and have f/c's or other bugs, you should do a fresh install and setup of your applications prior to posting problems you are having. There is no reason to post negative issues, if you have not tried to resolve the issue that is out of the dev's control.

Related

[Q] Titanium backup question

Searched and didn't find this specific question or anything close - so I'll post
I've been flashing roms a lot now that I've got the hang of it, but I think I was creating a problem for myself with titanium backup, which I think I've maybe now solved, but I'm not absolutely sure.
On the last couple of nighlies of CM that I've flashed I've been getting unfixable FC of the phone app (rom manager fix permissions didn't fix it and neither did wiping dalvik cache).
So I flashed ns-collab and I like it, but today I got the same FC problems and had to restore my nandroid to get the phone working (I was at work).
NS-collab is meant to be stable so I was starting to think that it's not the roms that are at fault but something I'm doing, and I had a feeling it was what I do with TB. So here is exactly what I do when I flash a new rom.
____________________________
I have TB set to "backup all user apps". That's it - no system data.
Before flashing the rom (even if it's just an update) I clear data, cache, and dalvik cache.
When I've got the new rom flashed I do not allow google backup to restore my stuff as I want it done with TB.
In TB restore I run "Restore all apps with data". When I do this I select the app+data checkbox in TB before clicking "Run the batch operation".
___________________________
So, I had a look at the apps that get restored when I run TB "Restore all apps with data", and I noticed there is quite a lot of android stuff in there like the dialler and lots of other services that are part of the android os and don't need restored with TB really.
I've just flashed the updated version of ns-collab and I removed all these android services from the TB restore before I ran it so I'll see if any problems crop up now.
But my question is, was I causing the phone to be unstable by allowing these android services to be restored by TB. Remember I did not select to restore system data, but I am wondering if system data was restored anyway because there were android apps in the list and I had the app+data option selected.
Hope the above isn't confusing and any advice will be appreciated.
Lot of information but I say you found your problem yourself.
I have not had issues in the past restoring: bookmarks, contacts/calls storage, SMS/MMS/APN Dialer storage, SMS/MMS PREFS etc.
I do think you are giving yourself a little extra work than needed. It is not necessary to do a data wipe before updating a ROM, wiping cache and dalvik cache should be sufficient and a lot of people don't even do that. Of course a good clean wipe every now and then is good and gives you that warm fuzzy feeling inside like after you change the oil in your car
In general, I do not recommend a full batch restore like restore all apps and data. I find when restoring with TB it is a good time to clean up and only restore the apps your really want back on your phone. I also do a batch restore, de-select all and just go down the list and pick out the stuff I HAVE to have.
irishrally said:
I have not had issues in the past restoring: bookmarks, contacts/calls storage, SMS/MMS/APN Dialer storage, SMS/MMS PREFS etc.
I do think you are giving yourself a little extra work than needed. It is not necessary to do a data wipe before updating a ROM, wiping cache and dalvik cache should be sufficient and a lot of people don't even do that. Of course a good clean wipe every now and then is good and gives you that warm fuzzy feeling inside like after you change the oil in your car
In general, I do not recommend a full batch restore like restore all apps and data. I find when restoring with TB it is a good time to clean up and only restore the apps your really want back on your phone. I also do a batch restore, de-select all and just go down the list and pick out the stuff I HAVE to have.
Click to expand...
Click to collapse
I think you are right about me giving myself work. Because I'm still a noob I'm still over cautious I think.
Maybe I'll try doing it your way. Sounds sensible.
Anybody know definitively whether me restoring everything via all apps and data would have contributed to the FCs I have been getting?
buachaille said:
I think you are right about me giving myself work. Because I'm still a noob I'm still over cautious I think.
Maybe I'll try doing it your way. Sounds sensible.
Anybody know definitively whether me restoring everything via all apps and data would have contributed to the FCs I have been getting?
Click to expand...
Click to collapse
Did you try fixing permissions? I only use the batch for Backup all user apps.
Backing up bookmarks.. I use BookmarkSB and SMS (i know theres a app for that) but i use GVoice so i dont need it
I've never had a problem restoring user apps with data. Instead of restoring all, choose restore missing user apps with data or something like that.
Although, I've had problems restoring SMS and certain data for system apps on the NS. Can't figure out why it doesn't work but whatever.
Sent from my Nexus S using XDA App
I would suggest you install app2sd & move your application to the sd-card. Each time you flash a new rom just wipe the /cache, dalvik-cache and battery stats. This is all you would ever require.
Thanks for all the replies. Quite a few suggestions there which I will try out.
Didn't have any FC problems at all at work today, so I'm hoping my more cautious restore last night might have done the trick.
buachaille said:
Thanks for all the replies. Quite a few suggestions there which I will try out.
Didn't have any FC problems at all at work today, so I'm hoping my more cautious restore last night might have done the trick.
Click to expand...
Click to collapse
Yeah FCs happen when you backup system apps / bookmarks etc. It could interfere

The problem with switching roms

So I'm pretty sure I figured out why a lot of us are having problems with teddys new rom. I'm guessing all of us have gone from rom to rom on this forum and I personally didn't have any problems untill I went from revolutions lightning rom to teddys touchmiuiwiz rom. I don't know why but I'm guessing something is incompatable with our backups between those two roms because teddys rom works perfectly fine untill I restore my apps and settings which are backed up currently with titanium backup from lightning rom. Once I do that my sd card starts acting weird and I get force closes loss of ringtones ect... so that's the only thing I can figure is going on :-/ I'm not sure what is causing the problem exactly but I'm pretty sure that's what the problem is.
Maybe someone can figure it out and fix it? This post might be pointless but I just figured I would share my thoughts and findings hence why I posted this in the general section.
Sent from my SGH-T839 using XDA App
i agree. TMW would be a 10/10 if my shiz didnt fux up. i even had to do my first ever odin because of it (although teds noob faq helped me through the odin (thanks ted))
Sent from my SGH-T839 using XDA App
The issue with nandroid restores is that they restore the full /data partition, rather than just the apps, it restores the data for each app, as well as the dalvik-cache. Wiping the dalvik-cache fixes most of the issues, but some apps are still older/different versions, or do not include the changes we have implemented in our rom, and therefore are incompatible.
The issue becomes that the restored apps are looking for something that isn't there in our rom, because they are from a different rom. You can always try wiping the data for the app that's FCing, but this is why we suggest using Titanium Backup, as it can backup just apps, rather than apps and data.

[Q] Question regarding restoring data contents from recovery...

Hey guys, just a quick question regarding restoring User Apps data from recovery.
I find myself flashing new roms more and more often these days, and it's becoming a tedious and repetitive task to install my apps and setup everything manually.
I use Titanium Backup PRO to restore my apps, and for my text messages I use GO SMS PRO to restore them.
The problem is, if you e.g. try to flash from CM7 to CM9, or flash from your current rom to an entirely different rom (which may also require a different kernel to be flashed), then as far as I know you can't simply use Titanium Backup to restore your apps data/settings. You can only use it to restore the apps (simply just installing the .apk files), but you would have to manually configure the settings all over again. I'm sure this has happened to many people with regards to using Titanium Backup when restoring user app data/settings, where they experienced corrupted data or battery drain issues etc.
As for restoring text messages with GO SMS PRO, it works but it lags and takes a long time. It would often popup the force close error box, and I would have to always choose "WAIT" to make it continue running. It may seem it's lagging or not working but in the end it restores all my messages fine.
Anyway, it's annoying to do all this setup manually, so I was wondering if it's possible to simply recover user apps data AND settings from the recovery? As far as I know, you simply recover /data from the recovery? Will that cause any problems if you were to update from CM7 to CM9?

[Q] [HELP] Android System UIDS inconsistent, cannot run Google Apps or backup files

I'm in a really tight spot here, and I really need someone's help.
My phone has multiple users on it and Titanium Backup only works for the main account.
However, when I updated my phone to the latest nightly the Play Store disappeared, and if I try flashing it again it doesn't work because of inconsistent UIDs.
Since installing a new rom would end up wiping all the data of the other user, and since they can't back up their apps because Google Services aren't working, I can't wipe and restore.
So either I need to get Google Services working so the second user can backup their app data, or I need to figure out how I can back up the second user's data and then restore when I install a new rom.
Probably the cleanest solution HERE

[GUIDE]: To transfer all app data + settings + all user configuration from old os to

TWRP METHOD ONLY
HOW TO TRANSFER ALL APP DATA + SETTINGS + ALL USER CONFIGURATION FROM PREVIOUS ANDROID OS TO NEW ANDROID CUSTOM ROM
Greetings, i have Great info for everyone for RESTORING User App + Data as it was before from TWRP. I used pixel experience 10 official rom for 2 days and after flashing it i restored my app data from titanium backup which after that took time to configure everything which is a bummer hectic to configure phone settings as per our likes and install & configure every app. Official Pixel 10 showed me little lags and slower performance compared to MIUI 11. Caution: TWRP DOES NOT BACKUP users Internal Storage data so make sure you backup your internal storage data like Photos, videos anything in internal flash storage backup somewhere else.
Now here's what i did, i rebooted to TWRP > Backup > Backed-up system image(incase anything goes wrong), boot and specially DATA (All user app + its data + settings stored in this). Make sure you backup data in external storage like memory card or OTG flash drive.
Then i installed EvolutionX Pixel 10 latest version released on 5th Dec after complete format, flashed DFE, Flashed Drunk Kernel, Flashed Magisk and wiped cache & dalvik cache. Then rebooted phone and configured the new os startup> rebooted to TWRP > Restore > selected only DATA and restored it > BOOTED SUCCESSFULLY WITH SAME APP DATA AND SETTINGS including same wallpaper and everything was same.
WARNING: After you boot your fresh backed up data & it asks for password after boot & gets stuck then reboot to TWRP and Install ResetScreenLock.zip (find it in XDA or CLICKHERE and boot successfully.
You can ONLY do this on SAME VERSION OF ANDROID OS. Like i had Pixel Experience 10 Official so it's data can only be transferred to any other Pixel Experience 10 custom Rom. I'm not sure about transferring Data from different versions of Android example android 9 Pie TO android 10 Q let me know if it's possible.
I didnt backup from titanium backup because usually restoring backup from titanium freezes & it cannot restore specific User App data to a new rom and it was a headache restoring apps manually after titanium backup didn't restore half of my apps & its data
You are welcome have blessed day. God Bless:laugh:
This is twrp 101. But mind that every problem and every force close you will encounter (and you most probably will) is going to be because of this.
Phone overheating, battery drain, apps crashing etc.
Developers suggest clean flashing for a reason, old ROM data interference with the new ones.
What you did is called dirty flashing and is the same as wiping system, davlik, cache and flashing ROM and gapps.
Your data backup is very useful when you want to try a new rom, clean flash it and then want to go back to your previous one.
sotosgolf said:
This is twrp 101. But mind that every problem and every force close you will encounter (and you most probably will) is going to be because of this.
Phone overheating, battery drain, apps crashing etc.
Developers suggest clean flashing for a reason, old ROM data interference with the new ones.
What you did is called dirty flashing and is the same as wiping system, davlik, cache and flashing ROM and gapps.
Your data backup is very useful when you want to try a new rom, clean flash it and then want to go back to your previous one.
Click to expand...
Click to collapse
Not a single problem till now, No phone heating, no abnormal battery drain, not a single app crashed. Phone is working perfectly smooth and not even a mili second lag. Basically Technically what actually i did is transfer my previous Pixel 10 data to New Pixel 10 data so there are no changes at all in Data.
You can test it if you follow my steps exactly you will successfully transfer Data to any New custom rom, i have tried. Just make sure the data you want to transfer is between same base roms like i transferred from Official Pixel 10 TO EvolutionX Pixel 10, similarly you can transfer to any Custom rom that is based on same base rom which you are using currently.
NOTE: Before you go & do TWRP backup, make sure you do complete system cleanup, app cleanup, corpse cleanup from SD Maid Pro and then do clean backup from TWRP
After you flash new custom rom make sure you boot it and go through its initial startup process then go back to TWRP and restore rom and flash ResetLockScreen.zip
Enjoy
eladamcain said:
Enjoy
Click to expand...
Click to collapse
I'm using custom ROMs since 2014, i have certainly enjoyed the issues i'm describing above.
Dirty flashing causes a lot of unwanted stuff.
Anyway, that's my two cents.
sotosgolf said:
I'm using custom ROMs since 2014, i have certainly enjoyed the issues i'm describing above.
Dirty flashing causes a lot of unwanted stuff.
Anyway, that's my two cents.
Click to expand...
Click to collapse
If you don't know what you are doing, you will face problem. This method works perfectly IF you are on Stock Rom and it is not bloated and you are transferring your data to custom rom who's made from the same base stock os. Example heavily bloated and transferring its settings to a different setting os is going to create instability its common sense. Backing up non bloated stock rom data to custom rom works
You saved my life... I tried a similiar method but it didn't work. But this... this saved my LIFE
(2FA Problems...)

Categories

Resources