Seasoned user here, def no noob. New to SGSII though. Anyway...here is my info.
I cannot no matter what I try get my phone to restore my Mms .db file, via recovery (I have tried, recovery, titanium, placing the files and setting the permissions manually).
If I delete the existing .db file and paste my Mms .db file there and it shows up in the data/data/com.android.providers.telephony/databases/mmssms.db
permissions
x x
x x
and then reboot
Go back and the old file is back there? Seriously WTF I want to smash this thing!
Someone assist me please?
Going to reply to my own thread with a solution in case anyone else has the same dramas? I kinda needed to do this because i got a chicks number the other day and she was hell cute and she had text me and I had saved her number but had not sync'ed my phone so the only way to get it back was from her SMS that was in the phone that someone had stolen. However I had the nandroid backup from the evening after i met this chick.
All previous hopes via recovery and titanium were fruitless
Anyway, I couldn't do a nandroid restore because it was saying that my device was not an MTD device....naturally its SGSII, and its not CM9 based firmware I have flashed either. So what I did was break the clockwork recovery backup down and pulled the data ext4 tar file out and re-hashed it (MD5sum)
I saw pulled an existing ICS nandroid backup form my SGSII fresh.
I exchanged the data tar and added the new hash value into the nandroid.md5 file and repackaged it.
It passed the check and installed the data but far out out it screwed my phone. android.process.android.acore was going nuts, I doubt there was even an app left that didn't force close.
I then did a titanium backup of the complete re-install with the Mms restored (although I wasn't certain because I couldn't open the messaging app at all! - nor could i get into settings to clear data cache without a bazillion force closes) I did this on total hope that it would work.
I then nandroid backuped my phone again just incase even though the data partition had a see of bugs in it. I then wiped the phone reflashed back to stock and then installed titanium and then restored just the SMS and couple of other things while i was at it! Bam perfect! All texts 100% restored including the drafts as if it was my old phone last I saw of it that is
I am still getting the odd few android.acore FCs but I know its a data cache related issue (I had this a while ago)....but no application FCs what so ever.
I hope this information helps someone out
James
Related
Hey there.
I had Lite'ning Rom 1.4 installed and decided to switch to VillainROM.
I did a full backup with Titanium Backup of all my user data and apps.
I did another backup in CMW, both successfully stored on the internal SD card.
I flashed VillainROM incl the tweaks, correct Kernel etc.
Now when I load Titanium Backup and want to restore my userdata like contacts, messages etc it does say it successfully restored the data but nothing is showing up, the contact list is still empty. So are the messages etc.
Since the Samsung stock apps are touched by VillainROM, is it possible the signatures are messed up or something?
I'm really a bit shocked I cannot seem to import the data, hopefully I'm just dumb and the data ain't lost
Please tell me that's the case...
Cheers for ANY advice on how to get my data back.
Okay, turns out I'm dumb.
A simply reboot did the trick, doh! It should say that somewhere...
Nevermind me, I will go into my corner and be ashamed of myself
Rooted SGS2 (with S2root) on Three network - kernel KI8, PDA KI2, CSC KI2
Backed up Talk 1.3 with titanium backup (not pro), uninstalled, cannot restore. titanium backup just sits on "restoring", even left it for 20 mins, cant even cancel it i have to close with task manager.
3 seemingly related titanium backup files:
com.google.android.talk-20111209-015957.properties
com.google.android.talk-fabd85cd35eb7dca08bec6aea0e6c41e.apk.gz (containing the apk)
com.google.android.talk-20111209-015957.tar.gz - (containing signinginactivity.xml)
com.google.android.talk.apk is still in the system\app folder, though nothing by that name on the titanium backup list, appears as "Talk 1.3" and uninstalled. if i delete the titanium backup files, the uninstalled app name changes to com.google.android.talk and talk 1.3 disappears.
Tried running a copy of talk.apk on the phone, didnt install, tried copying it to system\app and resarting: nothing. didnt show upanywhere as an installed app.
I thought it was something else and I want it back. Whatever changes i do, i still see the gtalk status next to people's names in my contacts/text message list, online/away etc. but no app in the app list. I can't work out what titanium backup did.
I think you should have booted to recovery and wiped cache partition and dalvik cache then rebooted and tried again.I dont think it was a good idea to have deleted the backup files cos the backup you made is most likely gone.You might have to reflash your firmware to get the stock app back you deleted.
hmm
I have a copy of the backup files on my desktop, what can I do with them? And is com.google.Android.talk.apk all there is to it? I have no talk.apk, no talkprovider.apk, no gservices like other people have mentioned.
boot into ClockworkMod recovery and flash
gapps-gb-20110828-newtalk-signed.zip
from
http://goo-inside.me/gapps
+1 thats the way to go
good call.that should do if your missing everything else.
I really don't think this was a good idea. Like I said before i still saw peoples talk statuses next to my normal contacts, some part of the stock app was still there. Now I get constantly disconnected in the new app and it seems to sign out when I back out of the program. What can I do with my titanium backup files instead? They are in .gz format but cwm flashes zips, I know I can convert just not sure if its the right thing to do.
I've also read that talk is part of the gmail app somewhere
P.s. Sorry for late reply, was getting my head round installing cwm, unrooted with s2 root then changed kernel to cfroot ki8
Or is there at least a way to reinstall the ki8 firmware that kies gave me...and would that even help
just incase
just incase anyone reading wants to know the real answer, it was to reinstall the official firmware from http://forum.xda-developers.com/showthread.php?t=1113928
then re-root with CF-Root from http://forum.xda-developers.com/showthread.php?t=1103399
all stock apps are back including talk, all my apps and settings were left untouched.
Hi everyone,
I recently dropped my Galaxy S3 and the Gorilla glas cracked. So I made a nandroid backup before sending it in to Samsung contractor to get it fixed. After I got it back (they couldn't replace the gorilla glas, they needed to replace the complete display) I tried to restore my nandroid backup. Everything seemed fine, reboot, then another reboot and I was back in recovery.
I then flashed back stock firmware (which caused some trouble so kies could update the phone but ended up fine). I then tried to use Titanium Backup Pro, Nandroid Explorer and AppExtractor 2.0 to get back my SMS and WhatsApp history but it failed.
Then I took a look at data.ext4.dup and it seemed to me as an index for what to restore from the blobs folder. So I searched for the mmssms.db file, found the entry and opened up the file in notepad++. It was an html file which seemed to me to be something from the Chrome cache. Next I used notepad++ to search over the whole blobs folder for some string from some SMS which I found in a file, that was supposed to be of the Chrome cache.
My conclusion is, that my data.ext4.dup file is mixed (messed) up. Was there a bug in CWM Touch Recovery and is there a way to fix this so I can restore my nandroid backup or at least get back my SMS and WhatsApp history? And is there a program to export / import / merge WhatsApp history?
Dash24x7 said:
Hi everyone,
I recently dropped my Galaxy S3 and the Gorilla glas cracked. So I made a nandroid backup before sending it in to Samsung contractor to get it fixed. After I got it back (they couldn't replace the gorilla glas, they needed to replace the complete display) I tried to restore my nandroid backup. Everything seemed fine, reboot, then another reboot and I was back in recovery.
I then flashed back stock firmware (which caused some trouble so kies could update the phone but ended up fine). I then tried to use Titanium Backup Pro, Nandroid Explorer and AppExtractor 2.0 to get back my SMS and WhatsApp history but it failed.
Then I took a look at data.ext4.dup and it seemed to me as an index for what to restore from the blobs folder. So I searched for the mmssms.db file, found the entry and opened up the file in notepad++. It was an html file which seemed to me to be something from the Chrome cache. Next I used notepad++ to search over the whole blobs folder for some string from some SMS which I found in a file, that was supposed to be of the Chrome cache.
My conclusion is, that my data.ext4.dup file is mixed (messed) up. Was there a bug in CWM Touch Recovery and is there a way to fix this so I can restore my nandroid backup or at least get back my SMS and WhatsApp history? And is there a program to export / import / merge WhatsApp history?
Click to expand...
Click to collapse
this is why i never use the new CWM, I hate the Blobs way... if i wanna save my backup to my pc forget it SO many files to transfer takes forever. I am a fan of cwm chainfire which is 6 files. and its a complete CLONEDroid and app extractor works perfect with it
Hello Friends and super expert Android devs and users,
I need some serious help with my SMS and MMS restores, moving from one ROM to another. The big reason for this? I currently have close to 47,000 messages in my SMS threads. Last time I restored these to a new ROM, via the XML insertion method using SMSBackup and Restore, for example it took me 48 hours to do so !!! All this being in Airplane mode to make sure nothing is corrupted or interrupted during the restore!
Titanium Backup is not an ideal solution for me either, because, it also takes a while, AND it will not work going from different UIs to UI, for example: Sense Backup to a CM10 restore of messages.
So I KNOW that the secret SHOULD lie in the msssms.db and the appstart folder, which seems to be the universal way Android stores its messages.
So far, the ONLY successful restore I have been able to pull off with the DBs has been this scenario:
1. Backup from a Sense ROM (Copy the providers.telephony folder into an SD)
2. Wipe and Install the SAME ROM
3. Copy the telephony folder using Root Explorer
4. Reboot into recovery, Fix Permissions, and Wipe Cache and Dalvik Cache
5. Reboot phone and then yes, the messages and MMS were there!
However, this process fails EPICALLY for going to other ROMs like:
Restoring this telephony folder OR JUST the mmssms.db and mmssms.journal files to a CM10 or a MIUI ROM, Rebooting in recovery, and then Fix Permissions, and Cache wipes. The outcome? Constant com.android.phone dying and the whole ROM being trashed ...
So... I need some education and desperate education here, guys. What exactly are the RULES and CORRECT (proven methods) of doing a mmssms.db restore? Can we move from OS version to OS? Like GB to JB? How about flavors of UI layers, like Sense to TouchWiz to MIUI and etc? If so, what is the REAL and the RIGHT way of pulling this off?
Other than that, if you experts thing of ANY OTHER way for me to restore 47K messages, while trying and using different ROMs on my phone, WITHOUT being in Airplane mode for 48 hours AND not, not restoring my whole 47K messages, then please feel free to share! I thank you in advance for your immense help!!!
*BUMP... one of you smart cats HAS TO know this ?
Hello all,
I just wiped and installed 4.13.651.4 rooted stock odex upgrade from captain throwback's release. Previously coming from 4.13.651.1. I used titanium backup to backup everything from previous installation, then restored everything from that release once upgraded. That screwed a bunch of stuff up because I restored all system and data as well as user apps and data. Wiped that out and reinstalled fresh, this time restoring all user apps and data, and only system data. For whatever reason, bluetooth will not operate. Everything else is fine. I cannot figure out how to reinstall only bluetooth files so that it works properly. So far the steps I've taken were to snag the following files from the 4.13.651.4 installation zip from the system/app folder in the zip:
Bluetooth.apk
Bluetooth.odex
HtcBluetoothLeProfiles.apk
HtcBluetoothLeProfiles.odex
HtcBtWidget.apk
HtcBtWidget.odex
Nfc.apk
Nfc.odex
I unzipped these with root explorer, then copied and pasted them into the ROOT/system/app folder after switching to "Mount R/W" in the system/app folder. Once the new files were in place, I changed permissions on all 6 files to be rw-r--r-- just like all the rest of the files. Rebooted phone, bluetooth still doesn't work. Are there any other files that I would've inadvertently have replaced or modified from the previous 4.13.651.1 files that controls bluetooth operation? I REALLY REALLY REALLY don't want to have to wipe and do over AGAIN!!!
Please help!!
Why are you replacing BT system files? Those aren't part of the TB backup, are they? Did BT work before you started restoring things from your previous install? I would suggest only restoring user apps and within that only the user data you really need to keep. Restore data for apps one-by-one, not all at once. Don't restore system data unless you know it's not going to interfere with what is already there. TB is almost too powerful for its own good when it comes to batch backup and restore. You gotta learn what to exclude and what you really want to migrate to a new install.
But mostly start fresh and make sure BT works before you start restoring anything.
SilverZero said:
Why are you replacing BT system files? Those aren't part of the TB backup, are they? Did BT work before you started restoring things from your previous install? I would suggest only restoring user apps and within that only the user data you really need to keep. Restore data for apps one-by-one, not all at once. Don't restore system data unless you know it's not going to interfere with what is already there. TB is almost too powerful for its own good when it comes to batch backup and restore. You gotta learn what to exclude and what you really want to migrate to a new install.
But mostly start fresh and make sure BT works before you start restoring anything.
Click to expand...
Click to collapse
It did work before I started messing with stuff. I'm restoring BT system files hoping it would work again. I don't really know what TB backs up when its set up backup everything. After first time I did restore items one by one and that's what screwed up BT in the first place. I figured putting original files back in system folder would fix it, but it didn't. I only restored system data one by one to try not to have to set up my phones settings again including BT pairings. Guess I've got egg on my face now. Any ideas?
whoshodade said:
It did work before I started messing with stuff. I'm restoring BT system files hoping it would work again. I don't really know what TB backs up when its set up backup everything. After first time I did restore items one by one and that's what screwed up BT in the first place. I figured putting original files back in system folder would fix it, but it didn't. I only restored system data one by one to try not to have to set up my phones settings again including BT pairings. Guess I've got egg on my face now. Any ideas?
Click to expand...
Click to collapse
If it was me, I'd do a factory reset or just reinstall the ROM (try dirty flash, if that doesn't work then wipe and start clean), then restore only user apps. In TB you can do a batch restore, but then uncheck apps you don't want to restore. I wouldn't reinstall any data from anything. If you open a user app and it turns out you don't have the data you want, then go in and restore data for just that app.
Restoring system apps and data is asking for trouble, IMHO.
SilverZero said:
If it was me, I'd do a factory reset or just reinstall the ROM (try dirty flash, if that doesn't work then wipe and start clean), then restore only user apps. In TB you can do a batch restore, but then uncheck apps you don't want to restore. I wouldn't reinstall any data from anything. If you open a user app and it turns out you don't have the data you want, then go in and restore data for just that app.
Restoring system apps and data is asking for trouble, IMHO.
Click to expand...
Click to collapse
Thats what I was trying to avoid.... if there was a way to break it, theres gotta be a way to fix it.
whoshodade said:
Thats what I was trying to avoid.... if there was a way to break it, theres gotta be a way to fix it.
Click to expand...
Click to collapse
Sure, replace the files you restored or copied over with the originals. My assumption is that the files that are "broken" are the ones that got overwritten when you restored and/or copied into /system from the previous install. They have to be replaced with the original files and data. That would involve extracting them from the original ROM and copying them back into place. I don't know how to go about that. I'd cut my losses and reinstall. If you have a TB backup already, you'll only be out the half-hour it takes to re-flash and restore things. Like I said, you can try a dirty flash, wipe caches only, try a factory reset, etc. I personally would wipe and re-flash clean, because I hate wondering if there are still any ghosts in the machine when I encounter problems like this.
SilverZero said:
Sure, replace the files you restored or copied over with the originals. My assumption is that the files that are "broken" are the ones that got overwritten when you restored and/or copied into /system from the previous install. They have to be replaced with the original files and data. That would involve extracting them from the original ROM and copying them back into place. I don't know how to go about that. I'd cut my losses and reinstall. If you have a TB backup already, you'll only be out the half-hour it takes to re-flash and restore things. Like I said, you can try a dirty flash, wipe caches only, try a factory reset, etc. I personally would wipe and re-flash clean, because I hate wondering if there are still any ghosts in the machine when I encounter problems like this.
Click to expand...
Click to collapse
I thought i did that... I dont know what other items affect BT
I am having issues on a clean install. Haven't connected to Bluetooth since I got the phone.
Sent from my EVO using Tapatalk