1) I used DROID RAZR HD Utility 1.20 [Windows/Mac/Linux] to upgrade my phone to 4.1.2. The utility said i would lose my data and I did. No problem.
2) I flashed a ROM named XenonHD. I found that it would not fully boot until I wiped the data. I lost my data so fine I recover but this was a PITA.
3) I backup XenonHD using TWRP and when XenonHD decided to not allow a data connection any more I decided to go back to 4.1.2.
4) I use TWRP to restore the most recent 4.1.2 backup and I find that none of my data is present.
Question: Is there a way to serially flash multiple ROMs and keep my data through the process? I flashed my ROM with my HTC ThunderBolt and never had this issue.
Thanks.
jhimebau
Yup Titanium backup. I recommend the paid version for quicker restore.
There are a few other apps that do this also.
It's in the toolbox of every good crackflasher.
TiBu and "data"
When I say data in the above post I mean files like .pdb file for iSilo and midi files that I use to determine the tune for a hymn.
These are the "data" that I find being removed. I place these files in a folder under sdcard.
I can restore the .pdb files but they are all managed content and I have to put an access code for all 30 some .pdb files to re-enable their use with iSilo.
Thanks.
jhimebau
Hi,
recently purchased the titanium backup pro.
I have 2 android devices that are using it
samsung tab s and a S6.
I noticed that both devices upload to the dropbox in a single location - dropbox/TitaniumBackup.
Will it cause any issues of files being overwritten as there will definitely be some overlapping apps that i got for both devices.
Or will the file name be individualized so that will not be any problems when i restore back ups.
Another thing is, i usually do a manual restoration of my backup to the sdcard , now that both backups are in a single location, how can i "correctly" seperate them so i can transfer the correct one back to my device?
Or is there a feature within titaniumbackup that im not knowing, which can help to directly restore the backup from the dropbox location?
Btw, im upgrading my Samsung Tab S OS kitkat to lollipop.
will my data backup be still valid for usuage?
Hello everyone,
today i switched from the german XEG MM Firmware to the latest BTU Nougat one, all with CSC change factory reset and re partition to get the CSC into effect. Had to factory reset anyways, since i always do it after some months, so why not update and test Nougat, while at it.
While everything except VoLTE/WifiCall (which are to be expected not working) works perfectly, i do however have a small problem with 1 App only, namely WhatsApp.
I've done a Cloud and Local Backup before the Update and neither are restoring on the Nougat OS, tested with older / same and even a newer beta from the APK itself.
The backup is recognized in size and according to the SQL extract should not be corrupted, haven't seen through every chat though (Cloud Backup size 660MB, chat file 22MB <- too big maybe?).
So my question is, does anyone have the same problem as i do? Is it a Nougat Filesystem / WhatsApp Database Key change due to the upgrade?
If you had the problem aswell, did you solve it without a downgrade or am i alone with it? The MM Key works on local backup, though i haven't yet pulled a "new" key to verify yet.
Tried:
Install various APK's, older/newer and same version
Factory Reset w/ clearing cache via recovery mode after flashing
Give the app permissions before launching
Remove Google Account to restore from local backup
Since i now have to wait 13h to verify with their servers again due to my personal troubleshoot, i figured i could ask here
I'm grateful for any tips, otherwise i might downgrade to MM again and hope the problem fixes itself, though i'd like to have the features of Nougat now and not in 2-3months, given previous release schedules of my carrier.
edit:
- I've just had an idea, while you use your phone number to verify. Mine does not display under the phone settings -> Device information -> Own Number. This might be due to the CSC change, but should not be relevant, since the actual process is done via messaging right?
Some additions to above text.
Does someone have or can upload here a zip with all emui 5.0.1 stock apps?
I dont want to format or loss data in the process. Did some did it before?
Sent from my FRD-L04 using Tapatalk
Also I forgot to mention I have another honor 8 device with the same version that I can extract from there if possible.
If anyone can give me directions...
Sent from my FRD-L04 using Tapatalk
Back up your data with Backup app, make an FDR and then restore your data with Backup app.
Update: To do an FDR, go to Settings-->Advanced Settings-->Backup & Reset-->Factory Data Reset.
MT2-User said:
Back up your data with Backup app, make an FDR and then restore your data with Backup app.
Update: To do an FDR, go to Settings-->Advanced Settings-->Backup & Reset-->Factory Data Reset.
Click to expand...
Click to collapse
There is no other way?
I dont want to factory reset the device.
Sent from my FRD-L04 using Tapatalk
Solved it!
Root - needed.
EMUI 5.0.1
Android 7.0
FRD-L04
* I belive it should work for all 7.0 various but NOT tested
I've been able to restore all Huawei stock apps and features.
I've copied hw_init folder (copied from another fully working Honor 8 device) to his place and restarted the device (use an explorer that have root access, I've used Solid Explorer).
That's it!
Folder full path: root\data\hw_init
I'll do my best to upload the folder later this weekend.
Hi,
I've just upgraded from latest OnePlus stock ROM of Android 11 to LineageOS 19.1. I've made backups before formatting everything, a full NANDroid with TWRP, one using the Migrate app, one with Oandbackupx of all apps. Also Google's way, but that doesn't back this app up, which seems to be quiet bad...
After trying to restore from all the mentioned sources, Google Authenticator can't seem to be restored. It always ends up empty. Is there a a specific protection for that data? I've similar issue with Dropbox as an example, it asks me to login after a restore. Whereas other apps preserved their logins...
Would be great to restore it, as I had like 30+ MFA codes added. Any suggestions?
Thank you!
There is only one way to transfer codes to another phone in the case of Google Authenticator.
Perhaps there is an analogy with the Dropbox access application. You'll have to check it out for yourself.
Hi,
Ok, thanks for the info. This is just sad to hear.
Going back to the original system with restoring the NANDroid backup go get this code might not work either?
Thank you.
I can't seem to find a solution. So I'm switching to Authy and in the same time I'll add it to KeePassXC, which can also do it... This can't happen again, I have to reset 2FA on 30+ sites
antivirtel said:
I can't seem to find a solution. So I'm switching to Authy and in the same time I'll add it to KeePassXC, which can also do it... This can't happen again, I have to reset 2FA on 30+ sites
Click to expand...
Click to collapse
whats stopping you from flashing your nandroid backup back to regain access? Isn't the whole beauty of nandroid backups the fact that they're more like system snapshots?
We currently are running into the same problem (although different phone, different situation but same effective result. We already came from a custom rom but forgot to get the transfer QRs from the Auth app.)
Okay so let me update you on my findings. If you have a back-up of Authenticators data (made before the update Google pushed out earlier this month*) you could fish out the database file (called database, without any file extention, stored in the folder database (full path to the file in a TWRP backup would be /data/data/com.google.android.apps.authenticator2/database/database)) and just read out the table accounts using any sqlite3 tool. This table has a column called secrets which contains the keys. There even is a free (linux/cygwin) set of scripts that can generate QRs for you if you do not feel like punching in the keys manually.
Theoretically placing the database file into the database folder of the app (overwriting the empty one) or using something like Titanium Backup should work too if you have not updated the app on your old device/installation yet.
*With the last update Google started encrypting the secrets before writing them to the database and nobody has been able to find the key which they used for that (yet)
screen said:
whats stopping you from flashing your nandroid backup back to regain access? Isn't the whole beauty of nandroid backups the fact that they're more like system snapshots?
Click to expand...
Click to collapse
I'm now on Android 12, and since TWRP doesn't support the new encryption, I can't just take a NANDroid backup of the current one and flash the old one in (without losing much of the current one, which I don't want). Unless there's something new around this, that won't be too much of a help.
I can think of restoring the NANDroid backup to an Android emulator, but it doesn't seem to be possible:
https://www.reddit.com/r/Android/comments/k7v4c/_/c2i5l9g
(unless it has changed in the last 11 years).
screen said:
Okay so let me update you on my findings. If you have a back-up of Authenticators data (made before the update Google pushed out earlier this month*) you could fish out the database file (called database, without any file extention, stored in the folder database (full path to the file in a TWRP backup would be /data/data/com.google.android.apps.authenticator2/database/database)) and just read out the table accounts using any sqlite3 tool. This table has a column called secrets which contains the keys. There even is a free (linux/cygwin) set of scripts that can generate QRs for you if you do not feel like punching in the keys manually.
Theoretically placing the database file into the database folder of the app (overwriting the empty one) or using something like Titanium Backup should work too if you have not updated the app on your old device/installation yet.
*With the last update Google started encrypting the secrets before writing them to the database and nobody has been able to find the key which they used for that (yet)
Click to expand...
Click to collapse
Yeah, I already checked that file, it's encrypted in there, I was using the latest versions of the apps when I made the backup, didn't think that won't be enough. The weird thing is that restoring it won't restore the data. So it must use some device related key or it just detects that it's a different device... Annoying, backing it up doesn't actually do any good...
Do you have any other idea? Thank you!
antivirtel said:
I'm now on Android 12, and since TWRP doesn't support the new encryption, I can't just take a NANDroid backup of the current one and flash the old one in (without losing much of the current one, which I don't want). Unless there's something new around this, that won't be too much of a help.
I can think of restoring the NANDroid backup to an Android emulator, but it doesn't seem to be possible:
https://www.reddit.com/r/Android/comments/k7v4c/_/c2i5l9g
(unless it has changed in the last 11 years).
Yeah, I already checked that file, it's encrypted in there, I was using the latest versions of the apps when I made the backup, didn't think that won't be enough. The weird thing is that restoring it won't restore the data. So it must use some device related key or it just detects that it's a different device... Annoying, backing it up doesn't actually do any good...
Do you have any other idea? Thank you!
Click to expand...
Click to collapse
Well, if Authenticator doesn't pick up on databases from other installations that would sugest that Authenticator has a way to link a database to an Authenticator installation. Meaning, the only way you could possibly have a chance to retrieve the data is to restore your nandroid backup (and use the Authenticator in there to make your transfer QR codes), count your losses as far as your current installation goes and reinstall a 12 rom from scratch. (Or find a way to get the key used to encrypt the secrets, if you have the key you just decrypt them and punch them in manually (or use the earlier scripts for QR code gen))
screen said:
Well, if Authenticator doesn't pick up on databases from other installations that would sugest that Authenticator has a way to link a database to an Authenticator installation. Meaning, the only way you could possibly have a chance to retrieve the data is to restore your nandroid backup (and use the Authenticator in there to make your transfer QR codes), count your losses as far as your current installation goes and reinstall a 12 rom from scratch. (Or find a way to get the key used to encrypt the secrets, if you have the key you just decrypt them and punch them in manually (or use the earlier scripts for QR code gen))
Click to expand...
Click to collapse
It's sad that nobody seems to have the keys to decrypt the secrets.
Wish I had a nandroid backup or just an earlier backup of the app's data before they started to encrypt their db.
I'm losing many accounts here.
shokolatha said:
It's sad that nobody seems to have the keys to decrypt the secrets.
Wish I had a nandroid backup or just an earlier backup of the app's data before they started to encrypt their db.
I'm losing many accounts here.
Click to expand...
Click to collapse
To prevent exactly this from happening (again) I've switched to Authy like @antivirtel suggested earlier. Authy saves your secrets to your authy-account, and a big plus they actually have a desktop program too so I don't have to use my phone per se (I often just leave it home not needing my phone _untill_ I need 2FA somewhere lol). I'm sorry for your losses but at least take this as a learning oppertunity and switch to an 2FA/MFA application that does cloud
Exporting a QR code from google authenticator then taking a screenshot\pic of it and saving that for future phones has served me well so far..
I think if I read correctly, TWRP just released their new version with Android 12 decryption support, so I can go and extract it now from my nandroid backup. https://twrp.me/site/update/2022/10/10/3.7.0-released.html - did someone test this?
BTW, I also saved the 2FA codes to KeePassXC/DX, works brilliantly there too, has nice integration both on desktop and Android.
Hi,
I've finally found a way to save my current ROM and go back to my old backup of stock A11 (restore a NANDroid backup), and try to access G Auth, but it was empty straight away. Tried a restore with Neo Backup, no change. Unfortunately it seems like it's all gone. At least I have the DB file, it has a list of accounts, so I at least know where I had MFA...
Unless someone else has a clue how to restore it, someone?
Given it's finally getting cloud sync feature, Google should release a way to restore it. Google please do!
Thanks!