Related
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.
Ok I'm new to flashing roms and slightly confused about nandroid backup and my reasons are this I read that nandroid backup backs up everything apps included but can't reinstall them so for example say I have a fresh clean installed rom I then sync all my apps from play store and have it set up how I like it ,
Next I create a nandroid backup and with all the apps I have installed that backup is now 14 gb in size ,
Now if I ever need to restore my phone I have a huge 14 gab nandroid backup that can't even install the apps so wasting all that space ,
So to get apps installed I need to do a titanium backup of apps again a fair bit of space used but at least I can reinstall them so call me stupid or whatever but would it not be better to just have a copy of your rom image,gaps and vendor on your phone or usb otg together with your titanium apps update zip?
Am I total missing something ?
I
garny68 said:
Ok I'm new to flashing roms and slightly confused about nandroid backup and my reasons are this I read that nandroid backup backs up everything apps included but can't reinstall them so for example say I have a fresh clean installed rom I then sync all my apps from play store and have it set up how I like it ,
Next I create a nandroid backup and with all the apps I have installed that backup is now 14 gb in size ,
Now if I ever need to restore my phone I have a huge 14 gab nandroid backup that can't even install the apps so wasting all that space ,
So to get apps installed I need to do a titanium backup of apps again a fair bit of space used but at least I can reinstall them so call me stupid or whatever but would it not be better to just have a copy of your rom image,gaps and vendor on your phone or usb otg together with your titanium apps update zip?
Am I total missing something ?
I
Click to expand...
Click to collapse
You're definitely totally missing something. The first mistake I think you're making is selecting too many of the checkboxes when creating a nandroid backup, it isn't fathomable for a backup to be 14GB in size when selecting the right options. You only need to select system, data, boot, and vendor. Make sure you leave all other boxes unchecked. The second mistake you're making is the belief that your apps aren't reinstalled when you restore a backup. When you create a backup (by selecting the four boxes I mention above) you create a snapshot of your operating system exactly the way it is when you make the backup. This means all of your apps, all of your settings, every single detail is preserved in this snapshot, so when you restore this backup at a later time it will boot up and be in the exact state that it was in when you created the backup, all of your apps will be installed just like they were previously. So there's no need to keep a Titanium backup of your apps for this specific purpose, but you should definitely have a Titanium backup of your apps for if/when you want to try a different ROM. I hope this all makes sense, if not please ask whatever questions you need to. Also check out my guide here:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
It contains a lot of information you might find useful, including a section on nandroid backups (section 4).
Ok thanks very much for that , I've just cleaned cache out and uninstalled some apps no longer needed , in that huge backup file was the titanium apps backup folder I forgot to delete like a divy ?
I've just done a backup again and now a backup by twrp is 8921mb according to twrp does that sound about right ? I have loads of apps installed and tomtom go which is about 1gb with uk map installed ?
garny68 said:
Ok thanks very much for that , I've just cleaned cache out and uninstalled some apps no longer needed , in that huge backup file was the titanium apps backup folder I forgot to delete like a divy ?
I've just done a backup again and now a backup by twrp is 8921mb according to twrp does that sound about right ? I have loads of apps installed and tomtom go which is about 1gb with uk map installed ?
Click to expand...
Click to collapse
No that's still too high. It looks like you're backing up userdata too which is unnecessary. Do what I said and only back up system, data, boot, and vendor.
That's all I have backed up what you said system boot data and vendor ? Maybe I should just do a clean install of pure nexus then install my apps from titanium then create a nandroid and see what size it comes up with ?
garny68 said:
That's all I have backed up what you said system boot data and vendor ? Maybe I should just do a clean install of pure nexus then install my apps from titanium then create a nandroid and see what size it comes up with ?
Click to expand...
Click to collapse
Perhaps you don't have compression enabled for your TWRP backups?
Heisenberg said:
Perhaps you don't have compression enabled for your TWRP backups?
Click to expand...
Click to collapse
That's right. ive just been into twrp and can see there is an option for compression but ive never checked that box, im guessing compression zips up the backup? if so do i need to decompress if i ever need restore?
garny68 said:
That's right. ive just been into twrp and can see there is an option for compression but ive never checked that box, im guessing compression zips up the backup? if so do i need to decompress if i ever need restore?
Click to expand...
Click to collapse
Yeah enable contain and it'll reduce the size, you don't need to decompress, TWRP does it automatically.
Heisenberg said:
Yeah enable contain and it'll reduce the size, you don't need to decompress, TWRP does it automatically.
Click to expand...
Click to collapse
thanks a bunch for your time been very helpful
Compression enabled me to get it to 4.99gb
garny68 said:
thanks a bunch for your time been very helpful
Compression enabled me to get it to 4.99gb
Click to expand...
Click to collapse
No worries, glad to help.
For those who can't restore apps from TB on the latest Oreo ROMs, please see my discovered workaround below.
TB > Menu > Preferences > App processing mode > Interactive
You should now be able to restore app and data, however, it will require your interaction for every app.
Remaining problem: can't freeze apps.
I decided to go back to Android 7.0
Oreo no root
This method worked for me, but it is very tedious as I have restored more than 125 apps.
ZainBilq said:
This method worked for me, but it is very tedious as I have restored more than 125 apps.
Click to expand...
Click to collapse
After first restored app, Titanium shows up on a "install unknown apps" list And no further process
I started having this problem restoring from Titanium. I'm using a Hauwei Mediapad M3 tablet on Android 7. I tried all of the fixes I've been able to find:
1. Turn off verify apps
2. Turn off verify apps over USB
3. Turn off wifi and data
4. Change Titanium preferences to Processing>Interactive
None of these approaches have worked for me. Does anybody have any other ideas to fix this?
xgneilx said:
For those who can't restore apps from TB on the latest Oreo ROMs, please see my discovered workaround below.
TB > Menu > Preferences > App processing mode > Interactive
You should now be able to restore app and data, however, it will require your interaction for every app.
Remaining problem: can't freeze apps.
Click to expand...
Click to collapse
Worked like a charm, thanks!
was getting furious over restoring my apps on Oreo!!!
:good:
xgneilx said:
For those who can't restore apps from TB on the latest Oreo ROMs, please see my discovered workaround below.
TB > Menu > Preferences > App processing mode > Interactive
You should now be able to restore app and data, however, it will require your interaction for every app.
Remaining problem: can't freeze apps.
Click to expand...
Click to collapse
Is this method for ppl want to restore their apps backup on say nougat or earlier version to oreo? Wud there be any issues if restoring apps from nougat or earlier to oreo?
mkruo said:
Is this method for ppl want to restore their apps backup on say nougat or earlier version to oreo? Wud there be any issues if restoring apps from nougat or earlier to oreo?
Click to expand...
Click to collapse
I did restore my apps from Nougat to Oreo, and haven't encountered any problem with the restored apps.
Great it worked on Samsung
Hello,
i have used titanium backup many times to restore my whatsapp backup from One phone to Another and it used to work without me having to get verification code from whatsapp.
But since i have installed Lineage OS 15.1 (Oreo), i am not able to restore the backup. Even after successful restoration of backup when i open Whatsapp it take me to Number Verification.
Does anyone here have any work around for it? i am looking to restore my Whatsapp and Other Apps along with DATA from my OLD Phone to my New Phone
Old Phone is : Google Nexus 6 (Running Lineage OS 15.1 Oreo) - Lineage OS Inbuilt Root Access
New Phone is: Nokia 7 Plus (Running Oreo OS 8.1.0) - Magisk Root Access
Please help if anyone has a work around for it..
Note: I cant get verification of whatsapp as my sim is lost and cannot get new one.
Will I be able to use Titanium Backup to restore apps in Oreo that were backed up in lollipop?
I want to upgrade the OS but keep some apps and their data, some transport apps and whatsapp in particular.
Hi
i´m facing a problem whith Titanium Backup.
I backuped my apps under Nougat LOS14.1 , which i wanted to take with to any Oreo Rom.
after flashing of several Oreo Roms , i didn´t get any App to restore under Oreo.
Titanium Restore still stand 0% and did not anything.
Is this a known Problem, that Apps from Nougat can not restored under Oreo?
Not a known problem that I know of. Well, used to be. When going from Marshmallow to Nougat.
I use TiBu on all Oreo ROMs. Originally anything restored was from Nougat backups.
I take it you're only trying to restore some user apps. No system apps which is a bad idea. Also, not sure if Oreo's change in the naming of items in /data/app/ have any bearing. Maybe not. TiBu would just dump the restored apks there instead of in subdirectories.
If possible, I would suggest installing the apps normally (Play Store, apk, etc.) then restore the data with TiBu. Some apps can be easily reconfigured so it's best to be selective.
Another issue you might come across is device ID. Has Titanium Backup shown a dialog about the backups being from a different device ID? If so, normally you can choose the previous and be good, otherwise data might not restore.
Oreo has changed how it deals with Device ID. TiBu can't make the change. Existing device ID changing tools don't work either.
This one does, on a per app basis...
https://forum.xda-developers.com/android/general/app-device-id-changer-oreo-13-aprv0-9-2-t3777299
If you get everything squared away and data restored onto Oreo, create a different Oreo-only backup destination.
Moto G5S Plus XT1806, AOSiP 8.1 ROM, microG (NoGapps), MultiROM, Tapatalk 4.9.5
no dialog about different Device ID
i tried only User Apps to restore, no System Apps
the way with only App Data is a good advice , i will give it a try
Hille2001 said:
no dialog about different Device ID
i tried only User Apps to restore, no System Apps
the way with only App Data is a good advice , i will give it a try
Click to expand...
Click to collapse
The auto install mode on titanium. Backup doesn't work on Oreo, U need to change that to Interactive ( Preferences> App processing mode) change from auto to Interactive, But this will ask install permission per app which can be a lengthy process especially if u have large no. Apps to restore but something is better than nothing
I've had no trouble whatsoever restoring apps and their data with TiBu. But I only restored user apps. Could have something to do with your root solution, probably Magisk. Or SELinux interfering. I use SuperSU on Oreo and all root apps work as expected.
I have TB example in latest AEX. Installed new version of google play services, and it was FCing. I tried to restore previous version from TB, and it did it, at least I thought so. TB didn't give any error message. When I looked in settings>apps and the version of GPServices was not the one from TB, but the one that was giving me problems. Eventually I manually installed the proper version of GPServices. I suspect it could be Magisk 16.0, which is what I am using for root. Non system apps get restored correctly.
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.