Database Users

Ttianium backup misbehaving

OK I just remembered why I don't change roms often, cos its a total pain in the A%%%%
I did a backup of apps and data in Titanuim, tried a few roms and have decided to settle on CM 10.2. But now Titanium is stubbernly refusing to see my backup. I can see the files in File Manager in /sdcard/TitaniumBackup. And in Titanium, when I go to preferences - backup folder location, I can see everything listed in there too (all the apks are there from my previous rom). But in the batch actions screen, I have a zero next to all the restore options.
Whats going on? Has anyone seen this problem before?

You need to change the backup directory to legacy
Like : storage/emulated/legacy/titanium.......
Sent from my Nexus 4 using xda app-developers app

Thanks for the suggestion, that is one thing I hadn't tried. Unfortunately it did not make any difference.

st0kes said:
Thanks for the suggestion, that is one thing I hadn't tried. Unfortunately it did not make any difference.
Click to expand...
Click to collapse
Go to Terminal Emulator doing the following:
su
busybox chown -R 1023.1023 /data/media/*
Wala now its fix and I can make a thread which should hopefully stop people from being negative to Titanium Backup.
Sent from my Nexus 4 using Tapatalk 4

Again thanks for the suggestion, but that didn't fix it either. I suspect you are on the right lines though, and this is some kind of permissions issue introduced with the new security features in android 4.3.
I think I'll go back to cm 10.1 and see if I can restore on there.
I was not being negative to titanium back up btw, my original post was very neutral. I've always liked TB and paid for pro a long time ago.

ok back on cm 10.1 and the problem still exists!

I am using /storage/sdcard0/TitaniumBackup. TB asked to move my files to this location and after accepting it, I have had no problems since. TB also alerted me that my Android id had changed and asked to change it back, which I also accepted. You could try going into the TB settings and under Manage Android ID, see if you have a previous id available thru Restore Android id from a backup.
Sent from my Nexus 4 using Tapatalk 4

So I know the actual location of our emulated sdcard is /data/media/0/
But then there are so many symlink locations like /sdcard, /mnt/sdcard/, /storage/sdcard0/, /storage/emulated/legacy/
So from now on 4.3+ what is the Google devs "best" or preferred location to use when saving to our virtual sdcard.. /sdcard, /mnt/sdcard/, /storage/sdcard0/, /storage/emulated/legacy/ any ideas?

[Help] Titanium backup and PA 3.98/Android 4.3

Hi,
Can someone tell me if there is problem with titanium backup 6.1 with PA 3.98 because when I try to restore an app with just hangs at processing. Installing app and then restoring data doesn't work too. I tried restoring apps with nandroid manager bt it just installed apps without app data even though I selected app data. Thanks

Change the path in Titanium backup from /storage/emulated/0/TitaniumBackup to /storage/emulated/legacy/TitaniumBackup. Titanium will ask if you want to move the files. Say No, since they are really the same folder. It's a 4.3 thing, not a PA problem.
That should do it.
Hit thanks if it works for you.
desiresiscool said:
Hi,
Can someone tell me if there is problem with titanium backup 6.1 with PA 3.98 because when I try to restore an app with just hangs at processing. Installing app and then restoring data doesn't work too. I tried restoring apps with nandroid manager bt it just installed apps without app data even though I selected app data. Thanks
Click to expand...
Click to collapse

Been thoroughly covered. You have two options to get it to work with 4.3- install supersu or point TiBu to storage/emulated/legacy.
Sent from my Nexus 7 using Tapatalk 4

desiresiscool said:
Hi,
Can someone tell me if there is problem with titanium backup 6.1 with PA 3.98 because when I try to restore an app with just hangs at processing. Installing app and then restoring data doesn't work too. I tried restoring apps with nandroid manager bt it just installed apps without app data even though I selected app data. Thanks
Click to expand...
Click to collapse
you have to flash the SuperSU 1.51

szabadgy said:
you have to flash the SuperSU 1.51
Click to expand...
Click to collapse
Installing SuperSU is not necessary and it will work if one just points TiBu to the appropriate directory. Installing SuperSU is an optional workaround. Whichever one a user opts for is a matter of personal preference.

Thanks for all the replies I will try when I get time
Sent from my GT-I9100 using Tapatalk 4

Is there a workaround for user accounts? I changed /storage/emulated/10/TitaniumBackup to /storage/emulated/legacy/TitaniumBackup but it is still hanging. would the SuperSU workaround work?

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.

Nexus Imprint doesn't work after TWRP restore

I have a 64GB Nexus 6P and am upgrading to 128GB. I backed up and restored via TWRP. I removed security before the backup. However, when I restore, I can't add a Nexus Imprint - it keeps saying enrollment was unsuccessful before it even lets me try to read my fingerprint. However, if I do a clean wipe & install, the fingerprint reader works fine.
Any suggestions?

seems to me something i borked in your backup. probably just going to have to start fresh. unless... of course... your backup contains a probram or xposed module that could be causing the problem. then it would just be a process of elimination to determine which one.

byproxy said:
seems to me something i borked in your backup. probably just going to have to start fresh. unless... of course... your backup contains a probram or xposed module that could be causing the problem. then it would just be a process of elimination to determine which one.
Click to expand...
Click to collapse
I've tried it twice (full cycle, backup, wipe, restore) with the same issue. I haven't installed Xposed yet.
I don't think this can be a program issue, I think Google added something at the OS level.
I hate starting fresh. Even with Titanium Backup, it takes forever.

That happened to me as well. Only way that worked was a complete clean flash for me.
Sent from my Nexus 6P using Tapatalk

roopesh said:
I've tried it twice (full cycle, backup, wipe, restore) with the same issue. I haven't installed Xposed yet.
I don't think this can be a program issue, I think Google added something at the OS level.
I hate starting fresh. Even with Titanium Backup, it takes forever.
Click to expand...
Click to collapse
I don't know if it's just my experience, but TiBu takes for-EVAR to restore APKs (not data, thats fast). Just forget it for any sizable app like Chrome or Facebook. So, I started using another app called AppWererabbit strictly for purposes of backing up/restoring APKs. With root privileges, it'll batch install over 100 apps fast. Then for a subset of apps that are non-trivial to set back up, i'll use TiBu to restore the data. Unfortunately AppWererabbit seems broken on Marshmallow for me. Also, Pro key is needed to do anything worthwhile.
I've looked into using TiBu's feature for creating flashable zip's to skip all that but it has yet to work for me a single time. I have, however, had promising results with some modest testing of this app called ZipMe that is in beta (also, tested on a Nook HD+ not Nexus6P)
Also, am I to understand you are trying to restore a nandroid for one device onto another?

cabbieBot said:
Also, am I to understand you are trying to restore a nandroid for one device onto another?
Click to expand...
Click to collapse
Yes. This should work since they're both Nexus 6P devices.

cabbieBot said:
I've looked into using TiBu's feature for creating flashable zip's to skip all that but it has yet to work for me a single time. I have, however, had promising results with some modest testing of this app called ZipMe that is in beta (also, tested on a Nook HD+ not Nexus6P
Click to expand...
Click to collapse
Thanks for the app recommendations. I tried ZipMe, it didn't work. Or at least I couldn't tell that it worked... It processed for hours but there wasn't an output zip.
Yeah, not impressed with Titanium Backup right now, either. Pretty frustrating experience overall.

roopesh said:
Thanks for the app recommendations. I tried ZipMe, it didn't work. Or at least I couldn't tell that it worked... It processed for hours but there wasn't an output zip.
Yeah, not impressed with Titanium Backup right now, either. Pretty frustrating experience overall.
Click to expand...
Click to collapse
I did some testing on app2zip https://play.google.com/store/apps/details?id=scd.app2zip
Made 5 zips of the same simple (nonsystem) calculator app. Got 5 different md5s. LOLNOPE...running, not walking, away from that app because I dislike bootloops and misery.

I have same problem. Did you find a solution or did you started fresh?

fikide said:
I have same problem. Did you find a solution or did you started fresh?
Click to expand...
Click to collapse
It's a bug with TWRP and the 6p, after restore in TWRP, use the TWRP file manager navigate to /data/system and delete locksettings.db file. Reboot and the secured lockscreen will be gone, just set up a pattern lock again and the secured lockscreen will work as normal with your saved fingerprints.

djkinetic said:
It's a bug with TWRP and the 6p, after restore in TWRP, use the TWRP file manager navigate to /data/system and delete locksettings.db file. Reboot and the secured lockscreen will be gone, just set up a pattern lock again and the secured lockscreen will work as normal with your saved fingerprints.
Click to expand...
Click to collapse
For this problem deleting locksettings.db is not working. This is different problem than you talked about.

It's been discovered in other threads that there is a hardware key associated with the fingerprint scanner. Which means you can't restore a TWRP data backup from one device to another. That sucks bc this is my main motivation for keep a TWRP backup. Hopefully, a solution will be found.

fikide said:
For this problem deleting locksettings.db is not working. This is different problem than you talked about.
Click to expand...
Click to collapse
StephenMSmith said:
It's been discovered in other threads that there is a hardware key associated with the fingerprint scanner. Which means you can't restore a TWRP data backup from one device to another. That sucks bc this is my main motivation for keep a TWRP backup. Hopefully, a solution will be found.
Click to expand...
Click to collapse
I don't know about transferring devices but restoring a backup and then using the twrp built in file manager to delete locksettings.db is what I do with my backups. And it works every time.

Right, that works for restoring TWRP backup to same device. But if you get another 6p for any reason, and then restore this same backup to it, the fingerprint scanner will not work.

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.