Hello, I was wondering if restoring my newly flashed to stock pixel 4 xl will affect its performance and battery life. I've read that restoring your phone with another can impact its performance.
Further information: I normally restore from Google drive, e.g. the backup option in your settings that's on the cloud. NOT using a cable.
Any more information will be appreciated
Related
Background info:
Updated Cyanogenmod 12.0 to 12.1 through a nightly update that the OS automatically recommended me do. Upon updating, the phone went into a boot loop. I did a data backup through TWRP and then I wiped the dalvik-cache and cache, but it still bootlooped, so I wiped the data. After wiping the data, the phone booted up just fine. At this point, I'd like to restore my data and I have tried doing so through TWRP, but then it just goes into a bootloop again.
Primary Questions:
Can I restore my data and not get the boot loop? If not, can I go back to Cyanogenmod 12.0 and then restore my data and not get the boot loop? If not, what are my options from here?
Secondary Questions:
What did I do wrong to get the boot loop and how can I prevent this from occurring in the future when updating to a new nightly?
thex2 said:
Background info:
Updated Cyanogenmod 12.0 to 12.1 through a nightly update that the OS automatically recommended me do. Upon updating, the phone went into a boot loop. I did a data backup through TWRP and then I wiped the dalvik-cache and cache, but it still bootlooped, so I wiped the data. After wiping the data, the phone booted up just fine. At this point, I'd like to restore my data and I have tried doing so through TWRP, but then it just goes into a bootloop again.
Primary Questions:
Can I restore my data and not get the boot loop? If not, can I go back to Cyanogenmod 12.0 and then restore my data and not get the boot loop? If not, what are my options from here?
Secondary Questions:
What did I do wrong to get the boot loop and how can I prevent this from occurring in the future when updating to a new nightly?
Click to expand...
Click to collapse
I'm going to answer your second question first, as the second answer shapes the first answer.
Sometimes a ROM needs a wipe before flashing..the reason for this is conflicting data.. Most commonly,.this will happen if going from one ROM to another from a different dev, but can also happen upgrading roms from the same dev.
The conflict will happen due to system settings.. All system settings go in /data/data along with your user app settings. Most settings will go in an sqlite database.
The boot loop problem occurs usually when there is an entry in one or more of these databases that correlates with a setting that no longer exists, or the entry doesn't match the options in a ROM. For example, if your ROM allows you to set screen sleep in 15, 30, 60 seconds only, but your database has your setting set at 45, android doesn't know what to do and boot loops.*
The fix is of course, wiping data.. This is why when restoring using titanium backup on a new ROM, we recommend only restring your user apps and data (using the filters and options) otherwise if you restore system apps and data you're restoring the problem.
The first question, you can restore app a from a nandroid backup using titanium. There is an option in preferences.
*please note, this is just a basic example for illustration purposes. Screen sleep may or may not cause a loop
Thank you for the detailed response. It was very helpful. I have a few more questions for you below.
rootSU said:
Sometimes a ROM needs a wipe before flashing..the reason for this is conflicting data.. Most commonly,.this will happen if going from one ROM to another from a different dev, but can also happen upgrading roms from the same dev.
Click to expand...
Click to collapse
Is there an easy way to predict whether this will occur prior to upgrading? And if so, how?
Can I downgrade back to my old nightly and restore my data to go back to the working setup that I previously had?
Is there a way to get my old OS customizations back from the nandroid backup that I created? For example, my desktop icon positions for my apps, etc..
Is it probable that a new version will come out that's compatible with the old versions settings? For example, you mentioned the screen sleep timer being 15, 30, 60 and then changing to 45 and the boot loop occurs. Do the developers ever recognize this issue occurred and then correct it in the next nightly to allow for 15, 30, 45 and 60 so I could restore my data without the boot loop occurring?
thex2 said:
Thank you for the detailed response. It was very helpful. I have a few more questions for you below.
Click to expand...
Click to collapse
Let's see what I can do
thex2 said:
Is there an easy way to predict whether this will occur prior to upgrading? And if so, how?
Click to expand...
Click to collapse
There are no hard and fast rules.. If you're going from Dev A ROM to Dev B ROM, you will almost certainly have to wipe. Also, between major version updates (5.0 to 5.1 for example) you too will most likely have to wipe
Usually for any upgrade on the same ROM that isn't a major version update (dev a 5.0 to dev a 5.0 base) you usually won't have to wipe, but you may well have to, depending on whether the dev changes things a lot. Always have a titanium and a nandroid backup before updating.
thex2 said:
Can I downgrade back to my old nightly and restore my data to go back to the working setup that I previously had?
Click to expand...
Click to collapse
Yes probably. Restore the full nandroid if you want.
thex2 said:
Is there a way to get my old OS customizations back from the nandroid backup that I created? For example, my desktop icon positions for my apps, etc..
Click to expand...
Click to collapse
It depends which launcher you're using.. If you install a launcher from play store, it is a user app.. So if you're restoring user also using titanium filters, it should restore it fully, including widgets etc. That said, sometimes it doesn't always work out. If the launcher has built in backup, it may be wise to use it.
If the launcher is built into the ROM, its classed as a system app, so even though user apps and system apps both keep their app data in /data/data, it will not be seen with titanium if you're using a filter to shoe only user apps and data.. Work around is backup system and user data without a filter in titanium then when restoring, apply the filter for user apps.. Then once user apps are restored, find the system apps you need to restore data for and restore individually as required. You need to restore as little as possible though to avoid the boot loop.
thex2 said:
Is it probable that a new version will come out that's compatible with the old versions settings? For example, you mentioned the screen sleep timer being 15, 30, 60 and then changing to 45 and the boot loop occurs. Do the developers ever recognize this issue occurred and then correct it in the next nightly to allow for 15, 30, 45 and 60 so I could restore my data without the boot loop occurring?
Click to expand...
Click to collapse
Usually not.. Generally ROM v2 changes from ROM v1.. ROM v3 is usually even further away from ROM v1. If a dev is changing such a setting they are probably doing so for a reason.. Sometimes if the setting is part of a function that the dev decides to remove again ROM v3, its possible. But its best to be prepared and accept that wiping and restoring is a common practice in custom ROM flashing
Hi,
Currently i'm running in 5.0.2.
Is there any way/possibilities to upgrade my firmware to 5.1.1 or the latest firmware without losing any of my apps + data (include messaging, etc). I only knew the way is to backup all my apps using titanium but i'm afraid when restore back it will cause some error due to the new 5.1.1 environment. Need some advice. Thank you.
if you can do what you have to do is if you do it by flashtool you should not tick the option, apps and user log data and if you do not do the same recovery from wipes just install the rom.
Thank you. Will try as your adviced.
Hi, I have got my N910F rooted phone with stock firmware build
MMB29M.N910FXXS1DPH1
and E-motion kernel.
These days I've installed L Speed to get a faster phone but I'm noticing many lags..unfortunately..
I notice the kswapd0 and Android system often suck my cpu.
I found on the web that if you want fox the kswapd0 issue you need to use Semaphore kernel but I installed E-motion kernel because I'm using a Zerolemon large battery and this kernel can read the battery in a correct way.
Therefore I'm thinking to change the Rom for example but I don't know them..
I thought about Emotion Revolution that you can match with the Zerolemon kernel.
In my phone I have installed about 650 apps (Titanium finds 660apps).
What do you think? Can I solve my lags issues?
Thanks!!
Sent from Note 4 device - Rome - Italy
umby75 said:
Hi, I have got my N910F rooted phone with stock firmware build
MMB29M.N910FXXS1DPH1
and E-motion kernel.
These days I've installed L Speed to get a faster phone but I'm noticing many lags..unfortunately..
I notice the kswapd0 and Android system often suck my cpu.
I found on the web that if you want fox the kswapd0 issue you need to use Semaphore kernel but I installed E-motion kernel because I'm using a Zerolemon large battery and this kernel can read the battery in a correct way.
Therefore I'm thinking to change the Rom for example but I don't know them..
I thought about Emotion Revolution that you can match with the Zerolemon kernel.
In my phone I have installed about 650 apps (Titanium finds 660apps).
What do you think? Can I solve my lags issues?
Thanks!!
Sent from Note 4 device - Rome - Italy
Click to expand...
Click to collapse
Sounds like you are suffering from the same symptoms I have. After over a years worth of usage and a couple "dirty" flashes to improve speed / stability my device was suffering from random reboots, slowdowns and lag spikes. In the end the only real solution is a factory reset
I've tried wiping cache, re flashing roms / kernels, trying different kernels (even though I need the zerolemon fix) all without any meaningful success
I'm unsure of the exact cause of the lag though. Even completely stock devices will experience lags / slowdowns after several years and the recommended fix from the manufactures themselves is a factory reset. This is only exasperated by flashing custom roms, kernels and patches which may introduce memory leaks, data leaks or other instability.
Personally I went back to a stock (debloated) Samsung based rom with Emotion's Zerolemon kernel, restored most of my apps and re-setup everything system related. It's now running like-new again.
Sadly there is no "quick fix" for this issue and, like me, your attempts to solve issues regarding speed / reliability by flashing various patches and fixes have come back to bite you.
So:
Backup userapps in Titanium (Do not backup / restore systemdata)
Perform a Nandroid Backup
Flash the rom of your choice (Do not flash the kernel yet)
Factory reset (Wipe system, Cache, Dalvik Cache in recovery)
Boot into android and perform the initial set-up
Flash the kernel in recovery (No need to wipe anything)
Boot back into android and begin restoring user apps and setting everything back up the way you like it.
I know "factory reset" probably isn't the answer you were hoping for but it's the only option I have found which fixes these issues for longer than a couple days..
hi. everyone
i have a oneplus 3 and i bought oneplus 3T can i restore a backup made by oneplus 3 TWRP in oneplus 3T , just to transfert everything or can i do thin in another way?
thank you
Definitely do not restore the boot and system partitions form the OP3 to the OP3T. That would likely cause issues as there are some differences between their ROMs and kernels.
You could maybe get away with restoring the System and Data partitions from the OP3 to the OP3T if they were both using the same unified ROM.
I would advise you to use something else like Titanium Backup to backup app data and transfer everything else you need manually. Much safer that way.
Im on Superior OS - Android 10.
I wanted to know how does TWRP DATA backup work, and where can I have problems?
I was thinking of giving a try to Pixel Experience 10.
If I backup just DATA usign TWRP, install pixel, gapps, magisk and after that I restore DATA, will the rom work perfectly and I will have all my configuration, settings, etc; or it just will work perfectly if I restore it to a clean installation of Superior OS.
Following that question.
May I go and try Havoc - Android 9, and restore DATA from Android 10? Will there be any problems?
And the last one.
If I go from Android 9 to 10, may I restore DATA?
Thanks!
When changing operating systems it's always best to re-install all apps.
I believe TWRP backup doesn't backup apps & data. Stuff like photos, music etc will not be backed up. You'll need to back those up separately. If you use Titanium, that would do more but reinstall your apps from their source and then restore data.
Sent from my Galaxy Tab S5e using XDA Labs
TWRP absolutely backups and restores data... But you only want to do this to the same OS version. You will likely get a bunch of force closes, and instability if you attempt to restore to different version.
A fresh install is always recommended, but you may want to check out the app called "Migrate" - YMMV.
jhedfors said:
TWRP absolutely backups and restores data... But you only want to do this to the same OS version. You will likely get a bunch of force closes, and instability if you attempt to restore to different version.
A fresh install is always recommended, but you may want to check out the app called "Migrate" - YMMV.
Click to expand...
Click to collapse
I would add, "same OS version" yes, but even custom 10 to another custom 10, I would strongly advise re-installing everything.
The problem is that you don't know what the environment is in an operating system and each app looks at its environment while it is installing and sets itself up appropriately.
So you have problems and you waste your own and others' time trying to shoot needless problems just in the hope of saving a few minutes.
You might think, "well, this custom 10 is like that custom 10" but unless you compare the full build trees and sources, you really don't have the faintest idea. They are different, because, well, they ARE different!