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.
Related
What the title says really. It has been working fine since I installed ACA march 8th but 2 days ago, for no reason i can see, it stopped acquiring root access. It appears that SU is suddenly automatically denying the permissions but i have never told it to do such a thing for TB. All the other programs i have that require root (Root Explorer and Rom manager to name 2) are working fine.
I have tried, fixing permissions both in Rom manager and CWM more times than i can count, I've done reboots, power offs, soft resets, cleared the caches for both Superuser and TB, reinstalled both, upgraded and downgraded SU and obviously searched my ass off and i just can't get the damn thing to work again.
It's a little important that i get a good backup because the one i have is 2 days old and in the morning I'm going to be picking up my new Endeavour (One X for the uninitiated) and I'll need to transfer everything over.
I know there are a bunch of these threads about but i wouldn't start a new one unless it was really needed. So has anyone got any ideas?
M3PH said:
What the title says really. It has been working fine since I installed ACA march 8th but 2 days ago, for no reason i can see, it stopped acquiring root access. It appears that SU is suddenly automatically denying the permissions but i have never told it to do such a thing for TB. All the other programs i have that require root (Root Explorer and Rom manager to name 2) are working fine.
I have tried, fixing permissions both in Rom manager and CWM more times than i can count, I've done reboots, power offs, soft resets, cleared the caches for both Superuser and TB, reinstalled both, upgraded and downgraded SU and obviously searched my ass off and i just can't get the damn thing to work again.
It's a little important that i get a good backup because the one i have is 2 days old and in the morning I'm going to be picking up my new Endeavour (One X for the uninitiated) and I'll need to transfer everything over.
I know there are a bunch of these threads about but i wouldn't start a new one unless it was really needed. So has anyone got any ideas?
Click to expand...
Click to collapse
Oh no, two days old?! whatever will you do? JK I've never come across an issue like this before, have you tried clearing all of the data for both apps and trying again? I'm very stumped as to how something like this would come about, especially if nothing actually solves it
Nigeldg said:
Oh no, two days old?! whatever will you do? JK I've never come across an issue like this before, have you tried clearing all of the data for both apps and trying again? I'm very stumped as to how something like this would come about, especially if nothing actually solves it
Click to expand...
Click to collapse
Yeah i tried that. I even rebooted the phone once i had. SU just doesn't want to give the correct permissions.
I have my One X charging on my desk and my brother has agreed to pay me for my Leo so i need to get this sorted pretty quick coz i can't give him the HD2 if it still has my data on it. I will be honest though and say that i'm starting to think the best solution will be to restore the good backup i have from [now] 3 days ago and then work on the leo. If i have to lose the sms messages etc i have for the last few of days then so be it but i am going to blame the rom for the fault if i do.
M3PH said:
Yeah i tried that. I even rebooted the phone once i had. SU just doesn't want to give the correct permissions.
I have my One X charging on my desk and my brother has agreed to pay me for my Leo so i need to get this sorted pretty quick coz i can't give him the HD2 if it still has my data on it. I will be honest though and say that i'm starting to think the best solution will be to restore the good backup i have from [now] 3 days ago and then work on the leo. If i have to lose the sms messages etc i have for the last few of days then so be it but i am going to blame the rom for the fault if i do.
Click to expand...
Click to collapse
Maybe it's something to do with ACA? Try this:
1. Backup everything in CWM
2. Flash a new ROM (not ACA)
3. Restore the data partition in CWM (through something like advanced restore, cba to boot into cwm to check it)
4. Load Titanium Backup and see if it works
5. (Assuming it works) backup your apps and enjoy.
Hopefully that might work. Also you don't need to worry about using a ROM with the same partition sizes as ACA, it won't matter (from what I've read, never actually tried it before).
Nigeldg said:
Maybe it's something to do with ACA? Try this:
1. Backup everything in CWM
2. Flash a new ROM (not ACA)
3. Restore the data partition in CWM (through something like advanced restore, cba to boot into cwm to check it)
4. Load Titanium Backup and see if it works
5. (Assuming it works) backup your apps and enjoy.
Hopefully that might work. Also you don't need to worry about using a ROM with the same partition sizes as ACA, it won't matter (from what I've read, never actually tried it before).
Click to expand...
Click to collapse
Ok i will try it and report back. i'm in the middle of installing HTC sync for the One X, unlocking its bootloader and flashing a custom rom to it.
To be frank, i wouldn't have kept ACA on it to give anyway for the very simple reason it seems to be far buggier than most of the other CM7 roms out there for the Leo
Thanks to an odd series of events last night (i managed to lock myself out of my flat/apartment) i didn't get to looking into this further but the scheduled TB backup ran at 2AM as normal and it succeeded. Although when i open TB it still says unable to gain root access. So this gets wierder but atleast i have a current, good backup to put on my Endeavour and now i can flash the Leo with a new rom.
I won't say problem solved but i will say crisis averted.
M3PH said:
Thanks to an odd series of events last night (i managed to lock myself out of my flat/apartment) i didn't get to looking into this further but the scheduled TB backup ran at 2AM as normal and it succeeded. Although when i open TB it still says unable to gain root access. So this gets wierder but atleast i have a current, good backup to put on my Endeavour and now i can flash the Leo with a new rom.
I won't say problem solved but i will say crisis averted.
Click to expand...
Click to collapse
Good to know, hopefully all the backups are good rather than corrupted. I don't know if it overwrites the old ones when it does a new backup, but if I were you I would have copied the old ones to my PC before the scheduled backup. That way, you have a fail-safe, but now if something went wrong you've effectively lost all of your app data.
Nigeldg said:
Good to know, hopefully all the backups are good rather than corrupted. I don't know if it overwrites the old ones when it does a new backup, but if I were you I would have copied the old ones to my PC before the scheduled backup. That way, you have a fail-safe, but now if something went wrong you've effectively lost all of your app data.
Click to expand...
Click to collapse
Titainum backup overwrites or deletes older backups as per user preference. I personally only ever kept one. The backup itself is ok but it turns out the contacts and sms databases in GB are not compatible with ICS so i had to move most stuff the long way round anyway.
It's a good job i keep like 5 backups of my contacts in 5 different places. That would have been a pain otherwise.
Using Skyrocket here but I found this thread because my TiBu failed to get root access after flashing a new ROM.
Solution:
-Go to Settings, then Applications
-Find "Superuser"
-Press "Clear Data"
-Go back to Applications
-Find "Titanium Backup"
-Press "Clear Data"
Close all apps and windows and go to your home screen. Open Titanium Backup. It should then request root access. Allow it.
Worked for me!
Datron said:
Using Skyrocket here but I found this thread because my TiBu failed to get root access after flashing a new ROM.
Solution:
-Go to Settings, then Applications
-Find "Superuser"
-Press "Clear Data"
-Go back to Applications
-Find "Titanium Backup"
-Press "Clear Data"
Close all apps and windows and go to your home screen. Open Titanium Backup. It should then request root access. Allow it.
Worked for me!
Click to expand...
Click to collapse
Thanks!
Had the same problem and this worked for me too.
I have this problem every time I restore my phone. All I do is uninstall it and reinstall it and it works just fine.
Sent from my HD2 using xda premium
Datron said:
Using Skyrocket here but I found this thread because my TiBu failed to get root access after flashing a new ROM.
Solution:
-Go to Settings, then Applications
-Find "Superuser"
-Press "Clear Data"
-Go back to Applications
-Find "Titanium Backup"
-Press "Clear Data"
Close all apps and windows and go to your home screen. Open Titanium Backup. It should then request root access. Allow it.
Worked for me!
Click to expand...
Click to collapse
This worked like a charm!!! I was about to wipe everything and redo my ROM, thank god i didn't have to!
Datron said:
Using Skyrocket here but I found this thread because my TiBu failed to get root access after flashing a new ROM.
Solution:
-Go to Settings, then Applications
-Find "Superuser"
-Press "Clear Data"
-Go back to Applications
-Find "Titanium Backup"
-Press "Clear Data"
Close all apps and windows and go to your home screen. Open Titanium Backup. It should then request root access. Allow it.
Worked for me!
Click to expand...
Click to collapse
Heh, I know this is an old thread, and even not my phones thread, but I just needed to say that this solution worked for me after the latest update for TB (8-21-12)....a quick google search pulled this up. Thanks!:highfive:
Datron said:
Using Skyrocket here but I found this thread because my TiBu failed to get root access after flashing a new ROM.
Solution:
-Go to Settings, then Applications
-Find "Superuser"
-Press "Clear Data"
-Go back to Applications
-Find "Titanium Backup"
-Press "Clear Data"
Close all apps and windows and go to your home screen. Open Titanium Backup. It should then request root access. Allow it.
Worked for me!
Click to expand...
Click to collapse
Got the same problem after 4.1.2 OTA with Galaxy Nexus. Can't resolve following the steps.
I just RESET and rooted my Infuse, added Titanium Backup, and it fails to gain access. Everyone who has this issue seems to have done some ROM install or some other thing. I can't find any report of someone just installing fresh and having this problem. Also seeing mention of hitting the problem button and getting something...I get nothing but a troubleshooting page that tells me to go read a wiki... Then I see people talking about accidentally disallowing titanium in Superuser, What does that mean? There is no Titanium in Superuser.
I just tried the above quoted solution, that did nothing as well.
Nothing on this thread makes Titanium work for me.
robs80 said:
Thanks!
Had the same problem and this worked for me too.
Click to expand...
Click to collapse
Guys, you're wonderful. It just worked for me too, just a minute before I decided to kill myself. Thnx:good:
Took me a long time to try everything specified here. Nothing's worked for me. It happened after I have installed Lollipop ROM on my rooted TMO S5. Finally I have uninstalled the TB Pro 6.1 I had before, and installed a non-Pro version from the Play. Now all works!
So probably the Pro has "incompatibility" with the Lollipop.
The thread is a bit old, but I just wanted to give one more tip if somebody else has similar issues. I encountered after one of the recent TB updates the same issue. I open TB and it does ask for root privileges, but for some reason never obtains them. Tried every possible proposal out there and in the end the only thing that actualy worked for me (although this is a bit of an unsecure setting) is to change the "Default access" setting in SuperSU to "Grant" instead of "Prompt". This is actualy telling the SU to grant acess to every app requesting it w/o prompting the user.
I was having the exact same issue on Titanium Backup 7.2.4 with SuperSu on the Samsung Galaxy SIII (AT&T SGH-I747). I looked at the access logs and discovered that Titanium Backup was getting an error when attempting to load busybox (not su), in spite of what the error says. I installed busybox, and the problem was resolved.
Edit:
1) My signature is really out of date.
2) Problem probably could have also been resolved in the TB preferences -> Troubleshooting by turning off "Force use System Busybox"
chriv said:
2) Problem probably could have also been resolved in the TB preferences -> Troubleshooting by turning off "Force use System Busybox"
Click to expand...
Click to collapse
That IS THE solution
Confirmed
Despite there's a lot posts with the same error, however I've readed all of them, followed all the possible solutions and nothing, that's why I'm writing this.
I have the latest version of Titanium Backup Pro (installed 1 hour before this post) with Busybox and SQLite in perfect condition, also I'm rooted (obvious).
I've tried with the 3 options in Preferences / App Procesing Mode (AUTO Direct, AUTO Indirect, INTERACTIVE) and nothing. Also I've tried uncheking Market Link in Preferences since someone advices it in other post. I've tried to scan the entire phone for the backups folder (wich is dumb cuz TB show me how many backups I have... however I did it). I tried to erase cache, force stop, re-install both the app and the entire ROM (cyanogenmod 10.2)... and nothing.
Titanium Backup Pro just halt on 0% when I try to do a backup.
Please guys, give me some ninja answers to fix this.
Thanks in advance.
Best regards.
PD: I also tried with an older version of Titanium Backup Pro... and got the same issue.
Make sure you have the latest SU binary.
Try SuperSU
https://play.google.com/store/apps/details?id=eu.chainfire.supersu&hl=en
From another thread:
Johmama said:
Go into Titanium Backup and change the backup folder location to /storage/emulated/legacy/TitaniumBackup, as opposed to /storage/emulated/0/TitaniumBackup.
That worked for me when the 4.3 leak came out, and when official 4.3 came out. I'm assuming it's the same issue.
Click to expand...
Click to collapse
baseballfanz said:
Make sure you have the latest SU binary.
Try SuperSU
https://play.google.com/store/apps/details?id=eu.chainfire.supersu&hl=en
Click to expand...
Click to collapse
I have the SU binary in the last version (checked right now).
alainalemany said:
I have the SU binary in the last version (checked right now).
Click to expand...
Click to collapse
Does your splash screen look like this, boxes are ticked, enough storage on the device?
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.
Hi,
I can't perform a Whatsapp backup since January this year, regardless if Google Drive Backup is checked, if the Whatsapp app is stored in the local or on sd card memory, automatic backups are being cancelled, too.
After I hit "Backup", the Dialogue "Messages are being backed up" shows up, which closes after 10 sec without any error message.
I tried to contact the WA Support, but they insist that my S4 is rooted (which it isn't, maybe because of the custom ROM I use).
I have flashed my Samsung I9505 in January this year from CM 12.1 to CM 13. At the beginning, the phone ran smoothless except BT. After a while, WiFi stopped working as well. I tried to flash the CM 12.1 backup and radios without any success, just a new mainboard helped. I installed my CM 12.1 backup from January via TWRP from my old mainboard, which ran without any errors on it (after a fullwipe on the new one).
The phone works great, except the WA backup.
WA gets always updated to the current version, I have ~1,2 GB free internal memory, I tried to update to the latest CM 12.1 5.1.1 version from 12/26/2015, perform a backup via 4G, 3G, Wifi, with an without Google Backup checked, cleared the cache and wiped Dalvic Cache, there is no app deactivated.
I use Baseband I9505XXUHOD7 and Kernel: 3.4.107-cyanogenmod-gab9afd6clyde.
Running a custom ROM means you are rooted.
Now, I don't know why whatsapp wouldn't work on a rooted ROM, but if you want to backup you can use titanium backup.
GDReaper said:
Running a custom ROM means you are rooted.
Now, I don't know why whatsapp wouldn't work on a rooted ROM, but if you want to backup you can use titanium backup.
Click to expand...
Click to collapse
There is no root, please check the screenshot below.
Since there is no root, I can't use Titanium Backup, however, it wouldn't be the most practicable way to backup your Whatsapp history every time with Titanium Backup.
Besides that, I don't think this would work if I would like to transfer my history to a new phone on which WA Backup should work as intended as I won't flash the ROM/install root and void the warranty.
WA backup worked perfect with the old logicboard before flashing CM 13.
m_pa said:
There is no root, please check the screenshot below.
Since there is no root, I can't use Titanium Backup, however, it wouldn't be the most practicable way to backup your Whatsapp history every time with Titanium Backup.
Besides that, I don't think this would work if I would like to transfer my history to a new phone on which WA Backup should work as intended as I won't flash the ROM/install root and void the warranty.
WA backup worked perfect with the old logicboard before flashing CM 13.
Click to expand...
Click to collapse
Root has to be activated from developer options.
That is definitely a whatsapp problem if it worked before.
GDReaper said:
Root has to be activated from developer options.
That is definitely a whatsapp problem if it worked before.
Click to expand...
Click to collapse
Well, I haven't even unlocked the developer options until now..
Any idea how to convince WA doing it's job? Anybody with this problem before?
if you really want a backup it makes more sense that you either activate root or flash superSU yourself rather than wait on whatsapp to change their code just for you. they've already told you effectively that they aren't going to do anything for you and don't have to.
backing up the app and data with TiBu and copying the whatsapp folder achieves everything you want and has worked flawlessly for me many many times.
Well guys, got a new phone but the problem persists when trying to restore my history on the new phone and really need your help.
Got root on the old phone and saved the com.whatsapp folder of it with the key file and databases. How can I encrypt the msgstore.db to msgstore.db.crypt8?
I have tried the app Whatcrypt, which creates a msgstore.db.crypt file, as large as msgstore.db, but Whatsapp on the new phone does not recognize it as a backup file.
When using whatcrypt.com and uploading the key and msgstore.db, it tells me "Encryption failed / Incorrect account?"
Also tried Omni-Crypt app. It creates msgstore.crypt, which Whatsapp ignores as well ("searching for Backups" with waiting triangle for hours)
I don't know any other way and I'm literally stuck now
when i mentioned copying the apps folder i was thinking of the one on the root of your internal storage, not the one in Android/data/...
you can paste that onto a new phone and restore the app and data with titanium.
3mel said:
when i mentioned copying the apps folder i was thinking of the one on the root of your internal storage, not the one in Android/data/...
you can paste that onto a new phone and restore the app and data with titanium.
Click to expand...
Click to collapse
Of course I can copy the Whatsapp folder on the root of the storage but this folder only contains the wa media files of my old phone since there are no msgstore.db.cryptX files created by Whatsapp.
For TiBa I would need to root the new phone which is a S7 Edge and I would like to avoid this until the warranty has expired. It is not as easy to do repairs by yourself as the S4..
fair enough, have you tried copying both folders over and installing from playstore ? or rather, install the app but don't open it, copy over both folders and then try and see what happens...
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.