Database Users

Nandroid backup with Tenfars CWM

Ok so I understand the general idea of CWM and love that I can do updates (rom and OS) and backup my entire system with it. I do not however understand a few things. If I for example backup my entire system while I am on 1.57 and then flash back to 1.26 or upgrade to 1.83, will I be able to restore my backup? Or will it restore my backup and throw me back to 1.57?
I really like wiping the entire sd card and starting from scratch ever so often with a clean install. I had many problems on the iPhone when doing fresh installs then restoring settings. It seemed that along with the settings would come anything bad or not functioning correctly. I am just worried that if I keep updating and flashing and loading different roms all the time, that my main partition will start to get loaded with unwanted junk and my filesystem will become "unclean".
What I would like to do, and I don't know if its possible, is to do a nandroid backup right now on 1.57, update to 1.83 and wipe everything so I have a clean install of 1.83, then restore my nandroid backup of all my exact settings and apps as if nothing ever happened. I am thinking that its not possible and the only way to do what I want is to flash to 1.27, wipe everything, update to 1.57, update to 1.83, then manually install every app again and set all my settings. <------Long, tedious, and stupid.
I also do not want to use TB because of some complaints I have recently been reading.
Sent from my Atrix using XDA App

I don't think this will do what you want. I have never had to use one of my nandroid backups, but my understanding is that they don't just back up settings they back up the entire install. So if you do a nandroid on 1.5.7 then update, then recover using your nandroid backup you will literally be back on 1.5.7 where you started.

what complaints have you heard about TB? I swear by that app, and it has never caused me problems and is one hell of a lot simpler a process than what you're suggesting. also I don't think that's how nandroid backup works. it makes an image so if u restore, you will go right back to the firmware you had when you backed up.
TB will save both your apps and your user settings. try it before you write it off.

plasticglock said:
I don't think this will do what you want. I have never had to use one of my nandroid backups, but my understanding is that they don't just back up settings they back up the entire install. So if you do a nandroid on 1.5.7 then update, then recover using your nandroid backup you will literally be back on 1.5.7 where you started.
Click to expand...
Click to collapse
That's what I thought.
Sent from my Atrix using XDA App

I can vouch for TB being awesome. If all your concerned about is User apps, TB will back up all of that PLUS the settings for each app. You also get the choice to save the backup on your sd card, ext sd card, OR DropBox (recommend using it on WiFi). I currently have backups on all 3 hahaha

dLo GSR said:
what complaints have you heard about TB? I swear by that app, and it has never caused me problems and is one hell of a lot simpler a process than what you're suggesting. also I don't think that's how nandroid backup works. it makes an image so if u restore, you will go right back to the firmware you had when you backed up.
TB will save both your apps and your user settings. try it before you write it off.
Click to expand...
Click to collapse
Unfortunately I don't remember where I read the info but on one of these forums there was a whole thread where people were complaining of force closes on apps that were backed up and restored using titanium backup.
Sent from my Atrix using XDA App

seh6183 said:
Unfortunately I don't remember where I read the info but on one of these forums there was a whole thread where people were complaining of force closes on apps that were backed up and restored using titanium backup.
Sent from my Atrix using XDA App
Click to expand...
Click to collapse
interesting. well i don't know if that would be really TB related because TB doesn't modify the program files in any way. maybe it has to do with freezing certain processes to get rid of bloatware.
for what it's worth, i've done full batch backups and restores onto fresh SBF flashes, and i haven't ever run into any problems.

dLo GSR said:
interesting. well i don't know if that would be really TB related because TB doesn't modify the program files in any way. maybe it has to do with freezing certain processes to get rid of bloatware.
for what it's worth, i've done full batch backups and restores onto fresh SBF flashes, and i haven't ever run into any problems.
Click to expand...
Click to collapse
Ever?
If I do a full backup with TB what EXACTLY will it restore after I flash the stock sbf? All apps and settings for the apps? Will it save my game progress or system settings for the phone?
I was told that the market should restore all downloaded apps when you log into the phone for the first time. I've also been told that blur saves the system settings and restores them. I haven't found either of these to be for me.
Sent from my Atrix using XDA App

seh6183 said:
Unfortunately I don't remember where I read the info but on one of these forums there was a whole thread where people were complaining of force closes on apps that were backed up and restored using titanium backup.
Sent from my Atrix using XDA App
Click to expand...
Click to collapse
This is because people are doing what you've proposed. TB backs up programs and settings. But if you do a drastic change and then try to restore programs with settings for the old framework, it can cause really unexpected challenges which result in the Force Close error messages.
CWM takes a snapshot of EVERYTHING so you definitely wouldn't want to do a backup and try applying it to a different SBF flash. It wouldn't even boot most likely.
When backing things up in TB I just back up the app and NOT the settings. I'm also sure that when I do a batch restore of apps (and NOT their settings) that I don't introduce apps which aren't compatible with the new ROM I'm running.
We don't really have many options for the Atrix at the moment, so not lots of people should be encountering challenges like this. Both programs do exactly what they should. People just don't understand them. Hopefully this helps to clarify things because it can be a big frustration when you think you've backed things up but are really left either stranded without a backup, or you've applied a backup which completely obliterated your phone lol

bongd said:
This is because people are doing what you've proposed. TB backs up programs and settings. But if you do a drastic change and then try to restore programs with settings for the old framework, it can cause really unexpected challenges which result in the Force Close error messages.
CWM takes a snapshot of EVERYTHING so you definitely wouldn't want to do a backup and try applying it to a different SBF flash. It wouldn't even boot most likely.
When backing things up in TB I just back up the app and NOT the settings. I'm also sure that when I do a batch restore of apps (and NOT their settings) that I don't introduce apps which aren't compatible with the new ROM I'm running.
We don't really have many options for the Atrix at the moment, so not lots of people should be encountering challenges like this. Both programs do exactly what they should. People just don't understand them. Hopefully this helps to clarify things because it can be a big frustration when you think you've backed things up but are really left either stranded without a backup, or you've applied a backup which completely obliterated your phone lol
Click to expand...
Click to collapse
I love that last sentence and want it in my sig LOL
what's your explanation for just backing up the apps and not the settings?
Sent from my Atrix using XDA App

Just a word of caution: Be extra careful where you store your backups. With how the atrix names phone sdcard and actual sdcard-ext is confusing to apps not updated recognize this. I've lost everything twice now because full backups go missing. Use the cloud or another computer to store them to be safe.
Has anyone restored a nandroid backup...with what results...does that just do the firmware, or do you get apps/data too? I still would like something similar to spb backup for WM...it took EVERYTHING into 1 self extracting, self installing file...I never lost anything with my years on WM and spb backup.
-sent from Atrix-

seh6183 said:
Ever?
If I do a full backup with TB what EXACTLY will it restore after I flash the stock sbf? All apps and settings for the apps? Will it save my game progress or system settings for the phone?
I was told that the market should restore all downloaded apps when you log into the phone for the first time. I've also been told that blur saves the system settings and restores them. I haven't found either of these to be for me.
Sent from my Atrix using XDA App
Click to expand...
Click to collapse
yes, i haven't ever. which i should have just said "have never" had any problems.
have you used TiBu before? you have options. you can batch restore app only, app + data, or data only, and when you do each you can select which apps to exclude/include. so if you want your savegames, your settings, etc, then you can restore the app data.
you can also batch backup/restore system settings separately, which I do not recommend if you are going to a new firmware as it may mess up settings since they will be from different versions.
if you do a whole batch restore of EVERYTHING without paying attention to what might be incompatible in a few firmware, of course you will run into problems. but a nandroid backup will not solve that either because you will just be re-imaging your phone with exactly what you started with in the first place.

dLo GSR said:
a nandroid backup will not solve that either because you will just be re-imaging your phone with exactly what you started with in the first place.
Click to expand...
Click to collapse
Is that just an image of the firmware and nothing else...or do your settings and apps installed to internal phone memory get backed up along with it.

full backup
JVogler said:
Is that just an image of the firmware and nothing else...or do your settings and apps installed to internal phone memory get backed up along with it.
Click to expand...
Click to collapse
I THINK I am understanding that Nandroid will take a picture of the phone - apps and ROM - and backup and restore the entire phone - which is EXACTLY what i am looking for.
If I am correct i assume there are directions somewhere here on how and where to do a full backup and also how to restore just in case.....
thanks for any info

Restoring apps with TiBu after updating to a 4.3 rom?

For some reason it doesn't seem to work. When I look at the play store reviews, they say that Titanium Backup doesn't work well restoring apps with 4.3. For me it just hangs at 0%. 4.3 has been out for a while, what have people been using?
Sent from my Nexus 7 using XDA Premium 4 mobile app

andrewdroid said:
For some reason it doesn't seem to work. When I look at the play store reviews, they say that Titanium Backup doesn't work well restoring apps with 4.3. For me it just hangs at 0%. 4.3 has been out for a while, what have people been using?
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hi, andrewdroid...
Yes, I've just been looking at the reviews you mention, and I must admit, I'm puzzled.
I've been running Jellybean 4.3 (recently updated to build JWR66Y) since the beginning of August, and I've had no problems with restoring apps from Titanium.
I recall, during the first few days of JB 4.3, there where issues with Titanium, and the recommended advice was to change the backup path (where you're backups are stored) as follows...
Go to... Titanium>>Menu>>Backup folder location...
...and navigate (using the back button) to /storage/emulated/legacy/TitaniumBackup ...and select 'Use the current folder'.
And at the time, this worked for me. But subsequent updates to Titanium fixed the problem, and my backup path is now the more technically correct /storage/emulated/0/TitaniumBackup.
Titanium will offer to move the files to the new location, but in the event, nothing actually gets moved, because the locations are actually identical... just different ways of specifying the same location.
So, you could try modifying your backup path location in Titanium settings as outlined above, using either of the two 'paths' I've given. I've just tried both, and in both instances, my backups restored flawlessly.
I've no idea if this will work for you, but I do know there was an issue back in the early part of August, and the 'legacy' path fixed it for me... maybe it might for you.
Hope this helps... and good luck.
Rgrds,
Ged.

Just completed my first root and flashed my tablet to cyanogenmod. I'd like to thank this community for making it so simple. It seemed like a lot of reading but every instruction had a purpose and i understood it more as the process went along. I had no problem throughout the process due to the very detailed instructions here on this forum.
However, I seem to have made one mistake. I used TiBu to backup my apps and data. However, i failed to make the update.zip folder as i didn't think about losing the app when i flashed to the new rom. When i check my device, there is a huge titanium backup folder.
Is there a way i can restore my apps and data from the tibu folder, or did i lose it all by not creating the update.zip folder?
Im afraid to just reinstall TiBu in case it overwrites the old folder.
This is the only problem I had with the whole process and appreciate any help or suggestions.

giusti825 said:
Just completed my first root and flashed my tablet to cyanogenmod. I'd like to thank this community for making it so simple. It seemed like a lot of reading but every instruction had a purpose and i understood it more as the process went along. I had no problem throughout the process due to the very detailed instructions here on this forum.
However, I seem to have made one mistake. I used TiBu to backup my apps and data. However, i failed to make the update.zip folder as i didn't think about losing the app when i flashed to the new rom. When i check my device, there is a huge titanium backup folder.
Is there a way i can restore my apps and data from the tibu folder, or did i lose it all by not creating the update.zip folder?
Im afraid to just reinstall TiBu in case it overwrites the old folder.
This is the only problem I had with the whole process and appreciate any help or suggestions.
Click to expand...
Click to collapse
Rename the huge titanium backup folder, install TiBu, delete new folder and rename huge titanium backup folder back to original name.

fingerprint issue when restoring TWRP backup on new 6P - wanna transfer apps/settings

I have a Nexus 6P, and need to transfer everything on it (settings, apps, data, etc.) to a new replacement device (also a 6P). Both devices are rooted and have TWRP installed.
I have a TWRP nandroid backup from the original device, and I'm having issues restoring it onto the replacement. When I restore the cache, data, and system backup options, everything seems to work perfectly except for the screen lock and fingerprint security settings. (In addition to the nandroid backup, I also copied the Internal Storage partition of the old device to the new one.)
When I restore the backup and boot up the new device, it has all my settings except for the fingerprints I had saved in Nexus Imprint. I have tried to set up the fingerprints again, and get a "fingerprint not enrolled" error that prevents me from registering my fingerprints again.
I've experimented a little, and have made two backups on the original device -- one with my original screen lock and fingerprint settings, and a second with the finger prints deleted and no screen lock. I've also tried deleting the *.key files locksettings.db from /data/system with no luck. I can access the new device and set up the screen lock again, but can't figure out how to register my fingerprints to use the sensor again.
Please help me get this figured out. I still have the original device on hand, if there's anything I need to change or I need to make a new backup with different settings. (I also have Titanium Backup pro, or could try Helium if that would do it.) Ideally I'd like to find a way to transfer everything without having to set everything up manually on the new device -- user apps, settings, and data (as well as system settings like homescreen setup, widgets, etc.).
Thanks!

indiecognition said:
I have a Nexus 6P, and need to transfer everything on it (settings, apps, data, etc.) to a new replacement device (also a 6P). Both devices are rooted and have TWRP installed.
I have a TWRP nandroid backup from the original device, and I'm having issues restoring it onto the replacement. When I restore the cache, data, and system backup options, everything seems to work perfectly except for the screen lock and fingerprint security settings. (In addition to the nandroid backup, I also copied the Internal Storage partition of the old device to the new one.)
When I restore the backup and boot up the new device, it has all my settings except for the fingerprints I had saved in Nexus Imprint. I have tried to set up the fingerprints again, and get a "fingerprint not enrolled" error that prevents me from registering my fingerprints again.
I've experimented a little, and have made two backups on the original device -- one with my original screen lock and fingerprint settings, and a second with the finger prints deleted and no screen lock. I've also tried deleting the *.key files locksettings.db from /data/system with no luck. I can access the new device and set up the screen lock again, but can't figure out how to register my fingerprints to use the sensor again.
Please help me get this figured out. I still have the original device on hand, if there's anything I need to change or I need to make a new backup with different settings. (I also have Titanium Backup pro, or could try Helium if that would do it.) Ideally I'd like to find a way to transfer everything without having to set everything up manually on the new device -- user apps, settings, and data (as well as system settings like homescreen setup, widgets, etc.).
Thanks!
Click to expand...
Click to collapse
Use titanium backup for apps. And then just restore from last android backup during setup. You can choose to restore your 6P settings and which apps you use. It remembers where you put everything on MM. Even your folders and where they where. Then when it's done restore app data with TB.

Thanks, the built-in Android backup/copy from nearby device worked a lot better and more thoroughly than I'd assumed. Between Helium, TiB, and nandroid backups on hand just in case I need to get more restored for an app or two (which I can extract in Titanium Backup), I think I'm set.
I did realize that the fingerprint and/or screen lock information is saved somewhere in the data partition in TWRP backups. It'd be great if someone can find them and come up with a way to remove them before restoring. Since I was transferring between two of the same devices, using TWRP to restore a nandroid backup should've worked except for the lock features. I wouldn't have restored system (and especially not EFS and Vendor) onto the new device. But data is mostly stuff for user-setup, so it'd be good to be able to have the option to remove or replace the few device-specific contents so it can be used to restore after RMAs, etc. At least for Nexus devices, that'd be a nice way to do a one-shot backup and restore.

indiecognition said:
Thanks, the built-in Android backup/copy from nearby device worked a lot better and more thoroughly than I'd assumed. Between Helium, TiB, and nandroid backups on hand just in case I need to get more restored for an app or two (which I can extract in Titanium Backup), I think I'm set.
I did realize that the fingerprint and/or screen lock information is saved somewhere in the data partition in TWRP backups. It'd be great if someone can find them and come up with a way to remove them before restoring. Since I was transferring between two of the same devices, using TWRP to restore a nandroid backup should've worked except for the lock features. I wouldn't have restored system (and especially not EFS and Vendor) onto the new device. But data is mostly stuff for user-setup, so it'd be good to be able to have the option to remove or replace the few device-specific contents so it can be used to restore after RMAs, etc. At least for Nexus devices, that'd be a nice way to do a one-shot backup and restore.
Click to expand...
Click to collapse
If you were looking for just that its in
data/system/locksettings.db
If you erase that with twrp file manager after a restore you can log in and change your lock settings. There are more lock setting files in the same directory you can delete but the locksetting.db is what keeps you locked out even with the right pin/pattern/password. I have heard it doesn't play nice across devices though. So the route you took should be better IMO.

That only works when restoring a backup to same device. There is a hardware key for the fingerprint reader somewhere else in Data partition tied to device. So, like OP found, when restoring a nandriod to a new device the fingerprint reader won't register fingerprints or work at all bc the hardware is different.

Gizmoe said:
If you were looking for just that its in
data/system/locksettings.db
If you erase that with twrp file manager after a restore you can log in and change your lock settings. There are more lock setting files in the same directory you can delete but the locksetting.db is what keeps you locked out even with the right pin/pattern/password. I have heard it doesn't play nice across devices though. So the route you took should be better IMO.
Click to expand...
Click to collapse
I found that, and it works fine to access the device and setup the lockscreen. But the Nexus Imprint settings are separate from locksetting.db (and the *.key files in the same folder). I just wish there was a way to easily or automatically remove all of the security or lock settings from a TWRP backup and keep the other app and user settings and data. Maybe an option in TWRP or TiB for restoring a backup archive onto a new device that filters out anything that's unique to each device. Or prior to restoring the data parition, TWRP could merge any device-specific files/folders from the new device into an additional file to be kept with the original backup. Something like that.
Some things like call/SMS history, widgets, and a few app settings didn't transfer perfectly using the combo of google's Android backup and Titanium Backup that I went with. And a selective restore from TWRP files might not be hard to develop.

StephenMSmith said:
That only works when restoring a backup to same device. There is a hardware key for the fingerprint reader somewhere else in Data partition tied to device. So, like OP found, when restoring a nandriod to a new device the fingerprint reader won't register fingerprints or work at all bc the hardware is different.
Click to expand...
Click to collapse
I covered that. It's in the last part of what I wrote. But you were more elaborate.
---------- Post added at 11:18 AM ---------- Previous post was at 11:16 AM ----------
indiecognition said:
I found that, and it works fine to access the device and setup the lockscreen. But the Nexus Imprint settings are separate from locksetting.db (and the *.key files in the same folder). I just wish there was a way to easily or automatically remove all of the security or lock settings from a TWRP backup and keep the other app and user settings and data. Maybe an option in TWRP or TiB for restoring a backup archive onto a new device that filters out anything that's unique to each device. Or prior to restoring the data parition, TWRP could merge any device-specific files/folders from the new device into an additional file to be kept with the original backup. Something like that.
Some things like call/SMS history, widgets, and a few app settings didn't transfer perfectly using the combo of google's Android backup and Titanium Backup that I went with. And a selective restore from TWRP files might not be hard to develop.
Click to expand...
Click to collapse
Yeah security is good, but it's making the days of transferring data and modifying partitions much harder.

Gizmoe said:
I covered that. It's in the last part of what I wrote. But you were more elaborate.
---------- Post added at 11:18 AM ---------- Previous post was at 11:16 AM ----------
Yeah security is good, but it's making the days of transferring data and modifying partitions much harder.
Click to expand...
Click to collapse
I had these problems too. How exactly do I disable those security settings? In the my file manager, I can't seem to find what I need. Can someone please explain how I go about disabling these settings so I can make a nandroid? Thanks so much.

Not sure if this is the full list but works for me.
To clear fingerprint/Nexus Imprint data, delete/move to backup:
Code:
/data/fpc/ # this seems to be related to inability to add/remove imprints, perhaps the hardware ID, I haven't checked the contents of global.db
For each user (e.g. 0), delete/move to backup:
Code:
/data/system/users/0/fpdata/
/data/system/users/0/settings_fingerprint.xml # You can actually rename fingerprints without problems, this file seems to just reference the hardware storage

myshen said:
Not sure if this is the full list but works for me.
To clear fingerprint/Nexus Imprint data, delete/move to backup:
Code:
/data/fpc/ # this seems to be related to inability to add/remove imprints, perhaps the hardware ID, I haven't checked the contents of global.db
For each user (e.g. 0), delete/move to backup:
Code:
/data/system/users/0/fpdata/
/data/system/users/0/settings_fingerprint.xml # You can actually rename fingerprints without problems, this file seems to just reference the hardware storage
Click to expand...
Click to collapse
This works!!! Thank you!!!!

myshen said:
Not sure if this is the full list but works for me.
To clear fingerprint/Nexus Imprint data, delete/move to backup:
Code:
/data/fpc/ # this seems to be related to inability to add/remove imprints, perhaps the hardware ID, I haven't checked the contents of global.db
For each user (e.g. 0), delete/move to backup:
Code:
/data/system/users/0/fpdata/
/data/system/users/0/settings_fingerprint.xml # You can actually rename fingerprints without problems, this file seems to just reference the hardware storage
Click to expand...
Click to collapse
u are awesome
thanks

myshen said:
Not sure if this is the full list but works for me.
To clear fingerprint/Nexus Imprint data, delete/move to backup:
Code:
/data/fpc/ # this seems to be related to inability to add/remove imprints, perhaps the hardware ID, I haven't checked the contents of global.db
For each user (e.g. 0), delete/move to backup:
Code:
/data/system/users/0/fpdata/
/data/system/users/0/settings_fingerprint.xml # You can actually rename fingerprints without problems, this file seems to just reference the hardware storage
Click to expand...
Click to collapse
Just got an N6P RMA. Deactivated screen lock and fingerprints on the old device, then made a full nandroid backup in TWRP. Restored boot, system, data, and cache partitions onto the new device.
Initially the new phone couldn't register fingerprints after the restore. Deleted the folders that myshen suggested. Had to reboot, but was able to add my fingerprints with no problem after that. :good: Worked like a charm.
Thanks for the great tip!

myshen said:
Not sure if this is the full list but works for me.
To clear fingerprint/Nexus Imprint data, delete/move to backup:
Code:
/data/fpc/ # this seems to be related to inability to add/remove imprints, perhaps the hardware ID, I haven't checked the contents of global.db
For each user (e.g. 0), delete/move to backup:
Code:
/data/system/users/0/fpdata/
/data/system/users/0/settings_fingerprint.xml # You can actually rename fingerprints without problems, this file seems to just reference the hardware storage
Click to expand...
Click to collapse
I can't believe this isn't pinned. This is a major, major issue for anyone RMAing their phone or anything like that. Thank you so much for this solution, it was not easy to find!!!

kwest12 said:
I can't believe this isn't pinned. This is a major, major issue for anyone RMAing their phone or anything like that. Thank you so much for this solution, it was not easy to find!!!
Click to expand...
Click to collapse
It is pinned.
https://forum.xda-developers.com/nexus-6p/general/psa-twrp-backups-lockscreen-security-t3245070

after multiple attempts of using TB to restore phone, i did a twrp backup, and this worked. thank you

myshen said:
Not sure if this is the full list but works for me.
To clear fingerprint/Nexus Imprint data, delete/move to backup:
Code:
/data/fpc/ # this seems to be related to inability to add/remove imprints, perhaps the hardware ID, I haven't checked the contents of global.db
For each user (e.g. 0), delete/move to backup:
Code:
/data/system/users/0/fpdata/
/data/system/users/0/settings_fingerprint.xml # You can actually rename fingerprints without problems, this file seems to just reference the hardware storage
Click to expand...
Click to collapse
you got any idea where "fpc" went with android 9 on the pixel 3? i'm having the the same problem .. could only find "settings_fingerprint.xml" and deleted this, but problem persits .. thx in advance!

androidfreak11 said:
you got any idea where "fpc" went with android 9 on the pixel 3? i'm having the the same problem .. could only find "settings_fingerprint.xml" and deleted this, but problem persits .. thx in advance!
Click to expand...
Click to collapse
Amazing how we all run into issues which have been looked at by many people and solutions proposed over a period of time....
Anyhow, I faced the same issue. The trick as outlined above didn't seem to work at first.I did a 'find /data -name fpdata'. It turned its now living in a different folder: /data/vendor_de/0/fpdata. A quick 'mv /data/vendor_de/0/fpdata /data/vendor_de/0/fpdata.org' from root shell, followed by reboot fixed the issue.
There seems to be no 'fpc' folder anywhere in 9.

devsk said:
Amazing how we all run into issues which have been looked at by many people and solutions proposed over a period of time....
Anyhow, I faced the same issue. The trick as outlined above didn't seem to work at first.I did a 'find /data -name fpdata'. It turned its now living in a different folder: /data/vendor_de/0/fpdata. A quick 'mv /data/vendor_de/0/fpdata /data/vendor_de/0/fpdata.org' from root shell, followed by reboot fixed the issue.
There seems to be no 'fpc' folder anywhere in 9.
Click to expand...
Click to collapse
All I ever did is erase locksettings.db in /data/system and all was fine. Haven't used the 6p in a bit though.

Gizmoe said:
All I ever did is erase locksettings.db in /data/system and all was fine. Haven't used the 6p in a bit though.
Click to expand...
Click to collapse
I faced this issue on Pixel 3, where I restored from a /data backup from my earlier Pixel 3.

Titanium backup force closing and browser wiped data

Hi, I've got a weird problem. Titanium backup continues to force close over and over whenever I try to open it. This also happened on the same day that my browsers data was wiped and I lost my open tabs. I have a browser backup but can't restore with titanium backup. Any help would be greatly appreciated. Thanks you.

DEVILOPS 007 said:
Hi, I've got a weird problem. Titanium backup continues to force close over and over whenever I try to open it. This also happened on the same day that my browsers data was wiped and I lost my open tabs. I have a browser backup but can't restore with titanium backup. Any help would be greatly appreciated. Thanks you.
Click to expand...
Click to collapse
Have you cleared all app data for TiBu? Uninstalled/reinstalled? Wiped dalvik and cache partitions?

v12xke said:
Have you cleared all app data for TiBu? Uninstalled/reinstalled? Wiped dalvik and cache partitions?
Click to expand...
Click to collapse
Yes, done everything possible. I might try a different rom as the could be buggy. Thanks for the suggestion.

DEVILOPS 007 said:
Yes, done everything possible. I might try a different rom as the could be buggy. Thanks for the suggestion.
Click to expand...
Click to collapse
You may want to pull your TiBu folder off to a PC just in case. Use a file manager to zip the entire TiBu folder and then move that one zip file to your PC just in case. That way when the fit hits the shan you can always restore apps later.

v12xke said:
You may want to pull your TiBu folder off to a PC just in case. Use a file manager to zip the entire TiBu folder and then move that one zip file to your PC just in case. That way when the fit hits the shan you can always restore apps later.
Click to expand...
Click to collapse
I unfortunately didn't have a backup at the time but do have one from a couple of weeks ago. I'm probably going to switch from Chads pa builds to dirty unicorns. If you don't mind, what rom do you use? Thanks for the help, I'm definitely going to get this sorted tomorrow.?

They may not be super recent, but you can batch restore all your apps whenever you load the new ROM. I was just suggesting you safeguard your TiBu backup folder. You may also know you can schedule a backup to run on a schedule so you don't even have to think about it. I use a one week interval at 2:00am. I run stock 7.1.2 ROM, rooted with EX Kernel on my phone and LOS rooted and EX Kernel on my Nexus tablet.

Titanium Backup Crashes If You Try To Restore

So over the weekend, I chose to root my phone and get the newest 10u update (model h918) and everything seemed to work fine and everything works well.
However, that changed when I transferred my titanium backup files to my v20 from my note 3 and tried to restore a few games. The thing is that I can backup apps, but can't restore them at all. It crashes in response to it. I've checked google play store reviews and others are experiencing this on the model number, so I hope that there can be a fix to this.
Here's what I did:
Dragged and copied all the backup files from my note 3 to my computer
Created a com.kermidas.TitaniumBackup folder into my sd card.
Dragged and copied all the backup files from my computer to v20
Tried to restore from files, crashes every time.
Tested to see if backing up works, indeed it does.
Restarted my phone and tried again, fails.
Uninstalled and reinstalled
Same thing happens again.
If there's something wrong I hope I get to fix it, otherwise oh well, guess I have to get used to it.
Looking forward for a fix, so please give me some suggestions.
Thanks

ZenovajXD said:
So over the weekend, I chose to root my phone and get the newest 10u update (model h918) and everything seemed to work fine and everything works well.
However, that changed when I transferred my titanium backup files to my v20 from my note 3 and tried to restore a few games. The thing is that I can backup apps, but can't restore them at all. It crashes in response to it. I've checked google play store reviews and others are experiencing this on the model number, so I hope that there can be a fix to this.
Here's what I did:
Dragged and copied all the backup files from my note 3 to my computer
Created a com.kermidas.TitaniumBackup folder into my sd card.
Dragged and copied all the backup files from my computer to v20
Tried to restore from files, crashes every time.
Tested to see if backing up works, indeed it does.
Restarted my phone and tried again, fails.
Uninstalled and reinstalled
Same thing happens again.
If there's something wrong I hope I get to fix it, otherwise oh well, guess I have to get used to it.
Looking forward for a fix, so please give me some suggestions.
Thanks
Click to expand...
Click to collapse
what did you use to root the lg phone? which su mgr?
did you change the name space manager or whatever titanium backup errors on startup?

Alibaba0101 said:
what did you use to root the lg phone? which su mgr?
did you change the name space manager or whatever titanium backup errors on startup?
Click to expand...
Click to collapse
I used lafsploit with Magisk 17.1. I did get a "this su may not be compatible with titanium backup, if not, try using SuperSU" obviously we know what happened to that however...

ZenovajXD said:
I used lafsploit with Magisk 17.1. I did get a "this su may not be compatible with titanium backup, if not, try using SuperSU" obviously we know what happened to that however...
Click to expand...
Click to collapse
And you have magisk manager 5.9 or 6 installed? Does magisk have the same namespace settings as supersu? Did you try and install titanium backup from googleplaystore? You are trying non-system apps?

NVM this post I accidentally erased it while editing

Alibaba0101 said:
And you have magisk manager 5.9 or 6 installed? Does magisk have the same namespace settings as supersu? Did you try and install titanium backup from googleplaystore? You are trying non-system apps?
Click to expand...
Click to collapse
Magisk Manager version is 6.0.0, I did install Titanium Backup through play store and I'm only restoring non system apps. My namespace settings are Inherited Namespace, not sure what SuperSU has.

Seems a general issue which started since August security patch update.
Tried on two different devices (oneplus one and Mix 2S), both with Android P with August/September security patch and there is no way to avoid this FCs after the first one, at the best you can make it start on the first launch and restore only data, but if it crashes then for some reason it doesn't matter what you do, it will always crash after this.

mustang_ssc said:
Seems a general issue which started since August security patch update.
Tried on two different devices (oneplus one and Mix 2S), both with Android P with August/September security patch and there is no way to avoid this FCs after the first one, at the best you can make it start on the first launch and restore only data, but if it crashes then for some reason it doesn't matter what you do, it will always crash after this.
Click to expand...
Click to collapse
I have the May Security Patch, I have the system version 10u so I haven't updated to Oreo as of yet

I have the same problem on another device. I got a rom on which titanium worked before but now after a clean install not. I only changed the gapps pack. so I think and has something to do with different or newer packs.
Edit: fixes it by installing titanium 8.1.0 instead of newest build. But I needed to clean install rom because it kept crashing from the previous install

gohan456 said:
I have the same problem on another device. I got a rom on which titanium worked before but now after a clean install not. I only changed the gapps pack. so I think and has something to do with different or newer packs.
Edit: fixes it by installing titanium 8.1.0 instead of newest build. But I needed to clean install rom because it kept crashing from the previous install
Click to expand...
Click to collapse
I did a clean install of 10u when I unlocked my phone, but I found out that I can only restore data only, which I'm all good for, at least if anything it's livable, but still looking for fixes.

I had problems with some apps (usually system apps) but most of what i needed like google playstore apps restored fine. Apps that need accounts was always 50/50. I'm still on 10u too. There is a warning on titanium startup about if you have problems try turning off mount namespace separation. May be worth a try.
Also,
I'm running supersu on my v20.