[SOLVED, see 2011/11/14 update]
Anyone has experience in restore history successfully in Whatsapp?
I have a backup file named "msgstore.db.crypt" in the Whatsapp folder in SD card.
After I reset the phone and install back the WhatsApp, it will prompt me whether I want to restore History.
After I clicked "Yes", there is a loading bar form 0% to 100%. However, nothing was restored except the group name...
I traced back and send the log to my own gmail.
I found the following things...
msgstore/restore/backupfiles msgstore.db.crypt (597008)
msgstore/restore/copy msgstore.db.crypt 597008
msgstore/restore/ioerror java.io.IOException: File.renameTo failed
After discussed with WhatsApp CS, they also have no idea how to solve this.
Their reply is "it's not letting the app write into the internal storage properly."
and the target internal storage location should be "/data/data/com.whatsapp/databases/"
Anyone have same situation ??
Updates: 2011/11/13
Finally figured out one possible reason with the help from Titanium Backup Team, currently /data/data/com.whatsapp/database/ is linked to /firstboot/sqlite/com.whatsapp/.
I try a simple copy of the folder "/data/data/com.whatsapp/" to SDcard , the database folder is not copied, possibly some permission issue..
So even titanium backup also failed to backup the database folder.
But i tried manually copy those db files to SDcard, it succeeds. Strange....
Updates: 2011/11/14
Dxmn i did it!!After two months of contacting WhatsApp support and Titanium Backup Team, and study the ROM structure of Android.
Finally can restore the backup file successfully problems-free!!!!
OK! Time to consolidate what i found in this two months....
Problem:
1. Failed to restore whatsapp history file "msgstore.db.crypt", only in Dell Streak, but succeed in other device (i tried Atrix, IDEOS and Galaxy Tab, they all succeed in restoring this file)
Symptoms:
1.
For a normal procedure:
i. Install whatsapp from market
ii. register my phone no.
iii. receive sms from whatsapp
iv. my number is activated
v. If there is msgstore.db.crypt or msgstore-yyyy-mm-dd.x.db[within 7 days] in \sdcard\WhatsApp\Databases\ , Whatsapp will ask if you want to restore history.
vi. After you say yes, the app will restore all your history.
HOWEVER, in my case, step vi will still prompt but it loads up to 10-15% , it will suddenly become 100%, and... you will see NOTHING in your whatsapp except your joined group name (which store in server).....
2.
In whatsapp, after failed to restore history, "Menu" > "Settings" > "More" > "Report a problem", enter something and click "Next" > select your email app > change to "To:" to your own email.
In the log file inside, you should see a line "msgstore/restore/ioerror java.io.IOException: File.renameTo failed"
3.
By using Root Explorer, look for the \data\data\com.whatsapp, there should be a folder "databases", select the property of this folder. It is linked to \firstboot\sqlite\com.whatsapp\.
Solutions:
If you match the above symptoms, i guess the following steps may help you!~
Suppose you are now using a phone, where whatsapp is not installed.
1. Make sure you have msgstore.db.crypt or msgstore-yyyy-mm-dd.x.db[within 7 days] in \sdcard\WhatsApp\Databases\ and DO A BACKUP OF IT
2. Install Whatsapp from market
3. Just after finished installation, open RootExplorer, go to \data\data\com.whatsapp, you should see "databases" is linked to "\firstboot\sqlite\com.whatsapp\" if you check its property
4. Check the owner of the folder "databases" by select "Owner" of this folder in RootExplorer.It should be something like "App-xx"(xx is app id)
5. rename the "databases" folder to "databases-firstboot"
6. create a folder using Root Explorer named "databases", and set its owner to the previous App-xx
7. Just open whatsapp and follow the normal procedure, the db files will be stored in \data\data\com.whatsapp\databases\
8. [i didnt do this step, but to ensure everything back to original] Finally revert the previous procedure, copy all the files from \data\data\com.whatsapp\databases to \data\data\com.whatsapp\databases-firstboot, and rename databases to databases-old, then rename databases-firstboot to databases.
9. Force Stop Whatsapp and restart it.
Hope this help everyone who have the same problem as me in Dell Streak or other devices.
Good luck
Please use the Q&A Forum for questions Thanks
Moving to Q&A
Same problem with an HTC Desire Z. I don't how to restore msgstore.db.crypt (
I've solved: with Root Manager go in data/data/com.whatsapp/databases and leave only wa.db file deleting msgstore.db file...now go in your mnt/sdcard/whatsapp/databases...here put only the backup file, the msgstorexxxxxx.db.crypt and after this, with app manager close forcing whatsapp if it has activities in background: when you will reopen the program it will say that the file of conversations is broken and if you want restore from the backup. So it's solved
Inviato dal mio HTC Vision usando Tapatalk
Hi,Confucio1986 , thanks for your suggestion.
I have tried what you did, but seems my history still not restored...
The following is the log from WhatsApp, "android.database.sqlite.SQLiteDatabaseCorruptException" is caused by removing the msgstore.db after root. But still have "java.io.IOException: File.renameTo failed" error.
Sigh....
2011-10-13 15:30:57.538 msgstore/checkhealth
2011-10-13 15:30:57.550 msgstore/checkhealth/journal/delete false
2011-10-13 15:30:57.563 msgstore/checkhealth/back/delete false
2011-10-13 15:30:57.574 msgstore/checkdb
2011-10-13 15:30:57.585 msgstore/checkdb/list msgstore.db 2602000
2011-10-13 15:30:57.610 ### begin stack trace 2.6.7814
android.database.sqlite.SQLiteDatabaseCorruptException: error code 11: database disk image is malformed
at android.database.sqlite.SQLiteStatement.native_1x1_long(Native Method)
at android.database.sqlite.SQLiteStatement.simpleQueryForLong(SQLiteStatement.java:107)
at android.database.sqlite.SQLiteDatabase.getVersion(SQLiteDatabase.java:926)
at com.whatsapp.wl.b(wl.java:962)
at com.whatsapp.wl.d(wl.java:816)
at com.whatsapp.t2.onClick(t2.java:15)
at android.view.View.performClick(View.java:2408)
at android.view.View$PerformClick.run(View.java:8816)
at android.os.Handler.handleCallback(Handler.java:587)
at android.os.Handler.dispatchMessage(Handler.java:92)
at android.os.Looper.loop(Looper.java:123)
at android.app.ActivityThread.main(ActivityThread.java:4627)
at java.lang.reflect.Method.invokeNative(Native Method)
at java.lang.reflect.Method.invoke(Method.java:521)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:858)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:616)
at dalvik.system.NativeStart.main(Native Method)
### end stack trace
2011-10-13 15:30:57.626 registername/clicked/sdcardstate mounted
2011-10-13 15:30:57.643 verifymsgstore/usehistoryifexists/backupfilesfound 1
2011-10-13 15:30:57.654 verifymsgstore/dialog/restore
2011-10-13 15:31:00.542 verifymsgstore/dialog/setup
2011-10-13 15:31:00.600 msgstore/initialize
2011-10-13 15:31:00.666 msgstore/restore/backupfiles msgstore.db.crypt (2602000)
2011-10-13 15:31:00.712 msgstore/restore/copy msgstore.db.crypt 2602000
2011-10-13 15:31:05.566 msgstore/restore/ioerror java.io.IOException: File.renameTo failed
2011-10-13 15:31:05.866 msgstore/setup
2011-10-13 15:31:05.887 msgstore/checkdb
2011-10-13 15:31:06.014 msgstore/checkdb/nodb
2011-10-13 15:31:06.024 msgstore/getwritabledb doesn't exist
2011-10-13 15:31:06.040 msgstore/create
2011-10-13 15:31:06.067 msgstore/getwritabledb/done/list msgstore.db 8192
2011-10-13 15:31:06.078 msgstore/preparestatements
2011-10-13 15:31:06.092 msgstore/backup
2011-10-13 15:31:06.504 msgstore/backup/size 8192
2011-10-13 15:31:06.522 msgstore/backup/to msgstore.db.crypt
2011-10-13 15:31:07.445 msgstore/backup | time spent: 1336
2011-10-13 15:31:07.633 msgstore/finish
2011-10-13 15:31:07.644 msgstore/initialize/lastmsgs
2011-10-13 15:31:07.656 msgstore/initialize/lastmsgs 0
2011-10-13 15:31:07.667 msgstore/getAllGroupActionMessages
2011-10-13 15:31:07.680 msgstore/asyncthread/started
2011-10-13 15:31:07.691 verifymsgstore/success
But I found one interesting thing recently, if the backup is too old, you also can't restore history.
I tried in my Atrix before, what i did to resolve this is to change the file creation date and file modified date to be a recent date.
Then the history can be stored.
However, this is not the solution for my Dell Streak...
Updated on 2011/11/13
Emailing chat / thread to ourselves
Good thing I read this thread. Was hoping that the backup work.
I tried emailing the chat to myself but that function only email those part of the thread history that is loaded. I have a chat thread going back half a year and each time I load up a few months, my phone slows and freezes until watsapp finally FCs.
Is there a function that allows me to let watsapp retrieve all the chat history from a single thread and post everything to me without me manually loading them?
Hi akita, i guess your case is not same as mine.
But what i know is the database file "msgstore.db", which store all of your history, is located in \data\data\com.whatsapp\databases\
If you know some SQL commands and have root access to your phone,
Copy the file to your desktop, and use some sqlite editor to open the msgstore.db in PC, and export your conversation as CSV for archive purpose...
Hope this help!~
akita16384 said:
Good thing I read this thread. Was hoping that the backup work.
I tried emailing the chat to myself but that function only email those part of the thread history that is loaded. I have a chat thread going back half a year and each time I load up a few months, my phone slows and freezes until watsapp finally FCs.
Is there a function that allows me to let watsapp retrieve all the chat history from a single thread and post everything to me without me manually loading them?
Click to expand...
Click to collapse
Thanks for the tip, that works!
In addition to this, does your "Email Conversation" function work properly? Does it email the *whole* conversation? Or only those presently loaded?
eg,
If you open up any conversation, some recent ones are loaded while older ones are hidden. Clicking "Load Earlier Messages" loads up a block of them. When you choose "Email Conversation", whatsapp seem to email only those presently loaded and not everything in the conversation.
How do we make it email *all* the messages in the conversation, including those earlier ones that is not loaded yet?
Since my original db doesnt hv much chat, i tried restore my 2.7mb db file and send back the chat log to myself.
The txt inside hv all my half year chat include those not loaded.
Maybe you can try my previous method to send back the log to yourself to see if anything strange during Whatsapp prepare the txt file, or whatsapp stuck in one of your messages.
akita16384 said:
Thanks for the tip, that works!
In addition to this, does your "Email Conversation" function work properly? Does it email the *whole* conversation? Or only those presently loaded?
eg,
If you open up any conversation, some recent ones are loaded while older ones are hidden. Clicking "Load Earlier Messages" loads up a block of them. When you choose "Email Conversation", whatsapp seem to email only those presently loaded and not everything in the conversation.
How do we make it email *all* the messages in the conversation, including those earlier ones that is not loaded yet?
Click to expand...
Click to collapse
Sent from my Dell Streak using XDA App
CharlesCCO said:
[SOLVED, see 2011/11/14 update]
Hope this help everyone who have the same problem as me in Dell Streak or other devices.
Good luck
Click to expand...
Click to collapse
you sir, are my hero!
i had the same issue and managed to get the backup restored thanks to your post.
Workaround
I also faced similar problems after rooting my neo v.
I removed all the msgstore-*.db.crypt and msgstore.db files from /Whatsapp/Databases folder in sd card.
But retained only 1 msgstore-*.db.crypt file which I wanted to restore (ie the latest backup)
Renamed it to msgstore.db.crypt. So now i have only 1 file in the databases folder.
Stopped the whatsapp service.
When I restarted whatsapp, it asked for restore again.
Pressed yes and it got restored with the latest chats history.
Hope it helps...
How to retrieve all whatsapp messages to PC / email
akita16384 said:
Good thing I read this thread. Was hoping that the backup work.
I tried emailing the chat to myself but that function only email those part of the thread history that is loaded. I have a chat thread going back half a year and each time I load up a few months, my phone slows and freezes until watsapp finally FCs.
Is there a function that allows me to let watsapp retrieve all the chat history from a single thread and post everything to me without me manually loading them?
Click to expand...
Click to collapse
This might help you:
[TOOL] Whatsapp Database Analyzer / Messages Extractor / Chat-Backup
http://forum.xda-developers.com/showthread.php?p=24603294
You can copy the whatsapp database to your PC and use the tool to display the chats on your pc as they are displayed by whatsapp.
Then you can delete all messages and have a faster whatsapp again
I tried all the steps in this Thread on my Atrix 4G but nothing works.
My whatsapp starts and creates a new database. I upgraded to ICS.
Before I just installed the App and when I started it, it restores the backup from the SDcard automatically.
Is my backup corrupt or is it an ICS issue?
Hi guys,
I haven't followed this thread in detail but here's something you might want to try when there are symbolic links within the apps' data:
In Titanium Backup, hit MENU -> Preferences -> Troubleshooting -> Enable the "Follow all symbolic links" option.
Then the following backups should properly include the apps' database data.
I got the same problem but only on a certain ROM. When I try to restore my whats app chats only the empty chat groups names are restored. I tried all suggestions on this thread but still no solution.
Please help me to find one.
Sent from my HTC Desire using xda app-developers app
What can you say about this log file?
Code:
[1895] msgstore/initialize
2014-03-21 01:15:11.849 LL_I [1895] msgstore/restore/backupfiles msgstore.db.crypt5 (5492752)
2014-03-21 01:15:11.850 LL_I [1895] msgstore/restore/copy msgstore.db.crypt5 5492752
2014-03-21 01:15:11.884 LL_I [1895] msgstore/restore/key CRYPT5
2014-03-21 01:15:16.817 LL_W [1895] msgstore/restore/error
### begin stack trace 2.11.186
[B][COLOR="Red"]java.io.IOException: Error while finalizing cipher[/COLOR][/B]
at javax.crypto.CipherInputStream.read(CipherInputStream.java:107)
at javax.crypto.CipherInputStream.read(CipherInputStream.java:143)
at java.io.InputStream.read(InputStream.java:162)
at com.whatsapp.util.wc.a(wc.java:82)
at com.whatsapp.ldb.a(ldb.java:2203)
at com.whatsapp.ldb.a(ldb.java:1121)
at com.whatsapp.ldb.a(ldb.java:2242)
at com.whatsapp.rl.a(rl.java:23)
at com.whatsapp.rl.doInBackground(rl.java:14)
at android.os.AsyncTask$2.call(AsyncTask.java:288)
at java.util.concurrent.FutureTask.run(FutureTask.java:237)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1112)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:587)
at java.lang.Thread.run(Thread.java:841)
Caused by: javax.crypto.BadPaddingException: error:06065064:digital envelope routines:EVP_DecryptFinal_ex:bad decrypt
at com.android.org.conscrypt.NativeCrypto.EVP_CipherFinal_ex(Native Method)
at com.android.org.conscrypt.OpenSSLCipher.doFinalInternal(OpenSSLCipher.java:420)
at com.android.org.conscrypt.OpenSSLCipher.engineDoFinal(OpenSSLCipher.java:480)
at javax.crypto.Cipher.doFinal(Cipher.java:1178)
at javax.crypto.CipherInputStream.read(CipherInputStream.java:105)
... 13 more
### end stack trace
2014-03-21 01:15:16.818 LL_I [1895] msgstore/restore/nothing-restored
2014-03-21 01:15:16.824 LL_I [1895]
Its restoring until 50% and then its aborting and nothing is restored. Any solutions for that?
HI Tylonhh, did you renamed your backup ?
The new whatsapp using a new key "crypt5" to decrypt, i am not sure if you are restoring from a very old backup (i.e. msgstore.db.crypt") and hence throw error while decrypting the database.
Tylonhh said:
What can you say about this log file?
Code:
[1895] msgstore/initialize
2014-03-21 01:15:11.849 LL_I [1895] msgstore/restore/backupfiles msgstore.db.crypt5 (5492752)
2014-03-21 01:15:11.850 LL_I [1895] msgstore/restore/copy msgstore.db.crypt5 5492752
2014-03-21 01:15:11.884 LL_I [1895] msgstore/restore/key CRYPT5
2014-03-21 01:15:16.817 LL_W [1895] msgstore/restore/error
### begin stack trace 2.11.186
[B][COLOR="Red"]java.io.IOException: Error while finalizing cipher[/COLOR][/B]
at javax.crypto.CipherInputStream.read(CipherInputStream.java:107)
at javax.crypto.CipherInputStream.read(CipherInputStream.java:143)
at java.io.InputStream.read(InputStream.java:162)
at com.whatsapp.util.wc.a(wc.java:82)
at com.whatsapp.ldb.a(ldb.java:2203)
at com.whatsapp.ldb.a(ldb.java:1121)
at com.whatsapp.ldb.a(ldb.java:2242)
at com.whatsapp.rl.a(rl.java:23)
at com.whatsapp.rl.doInBackground(rl.java:14)
at android.os.AsyncTask$2.call(AsyncTask.java:288)
at java.util.concurrent.FutureTask.run(FutureTask.java:237)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1112)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:587)
at java.lang.Thread.run(Thread.java:841)
Caused by: javax.crypto.BadPaddingException: error:06065064:digital envelope routines:EVP_DecryptFinal_ex:bad decrypt
at com.android.org.conscrypt.NativeCrypto.EVP_CipherFinal_ex(Native Method)
at com.android.org.conscrypt.OpenSSLCipher.doFinalInternal(OpenSSLCipher.java:420)
at com.android.org.conscrypt.OpenSSLCipher.engineDoFinal(OpenSSLCipher.java:480)
at javax.crypto.Cipher.doFinal(Cipher.java:1178)
at javax.crypto.CipherInputStream.read(CipherInputStream.java:105)
... 13 more
### end stack trace
2014-03-21 01:15:16.818 LL_I [1895] msgstore/restore/nothing-restored
2014-03-21 01:15:16.824 LL_I [1895]
Its restoring until 50% and then its aborting and nothing is restored. Any solutions for that?
Click to expand...
Click to collapse
I tried renaming, but that makes no sense because of the decrypting.
I have an back from the 19th this month. So it's just two days old and also from the same WhatsApp version which I use now.
I just got a new phone with a higher Android version. From galaxy S2 to Motorola G (4.4.2).
So normally there should be no errors. Does the log show you something? Does it mean WhatsApp can't decrypt it?
---------------
gesendet vom Barhocker
Hello all,
I installed [ROM] NexusHD2-JellyBean-4.1.2-CM10 V1.2 from tytung.
It is fine. I find it great.
But I have an issue to configure with my corporate exchange account.
My error log emaillog.txt is as following:
[11:17:53] AbstractSyncService| Testing EAS: my.server.adress, my_domain\my_user, ssl = 1
[11:17:53] ExchangeService| !!! EAS ExchangeService, onStartCommand, startingUp = false, running = false
[11:17:53] ExchangeService| Reconciling accounts...
[11:17:53] ExchangeService| !!! EAS ExchangeService, stopping self
[11:17:53] AbstractSyncService| Validation (OPTIONS) response: 500
[11:17:53] AbstractSyncService| Internal server error
[11:17:53] ExchangeService| !!! EAS ExchangeService, onDestroy
Click to expand...
Click to collapse
I can't get rid of the error:
[11:17:53] AbstractSyncService| Validation (OPTIONS) response: 500
[11:17:53] AbstractSyncService| Internal server error
Does someone know how to solve it? What is it meaning?
I searched hours on the xda forums and found lots of posts with issues concerning Email.apk and Exchange Server.
I tried different proposed solutions, but they didn't solved my case.
Here what I tried:
- Delete all accounts (even the google account), recreate the exchange account 1st ...
- Check my permissions in Active directory (The famous checkbox inherit permissions), which are correct.
- Reinstalled the rom.
- I tried to replace my apk with various Email.apk and Exchange2.apk without exchange security, it never worked.
- I tried with a pin lock screen, a password lockscreen or a pattern lock screen
- I found post speaking about issues concerning the exchange server SSL Certificate.
I tried the workaround with WIFI connection and shut down the connection, to finish the account configuration, but it didn't worked.
Instead of skipping the SSL certificate check and completing the account configuration, it cancelled/interrupted the account configuration.
- I tried to add the SSL certificate in the trusted certificates
- With my Email.apk V4.1 and Exchange2.apk v5.0 I never got the message to add the email application to the device administrator...
- I checked my settings with Moxier trial and Touchdown trial, and it worked. So my settings (account, domain, server) are correct. The only problem is the Email.apk on JB 4.1.2 !!!
I noticed that if i install a previous version of Email.apk (v2.3), I can configure my exchange account and sync mails, but the application is not stable on JB 4.1.2 and constantly crashes.
What could I do to solve that issue?
Do someone have a tip or hint?
Thanks in advance
Regards
A. Meladius
Hello together,
I recently made an update of LineageOS for my LG G5 (LineageOS 14.1) as well as my Samsung Galaxy S5 (LineageOS 15.1). They both seem to have serious issues afterwards and I don't know what happened. I assume something has changed within the last month or so and my problem appears with both devices.
It appears as if the permissions for all GApps have changed (or the uids perhaps). All other apps work perfectly fine so far. I also downloaded the latest GApps and installed them via TWRP but that doesn't seem to solve any problem. However I'm not sure that overwrites the old applications or only installs currently not installed ones.
So when ever I use one of these apps (Gmail, Playstore, Maps, some of the system processes), it always crashes and I see the log messages looking like this:
Code:
com.google.android.gms.persistent, PID: 13071
java.lang.RuntimeException: Unable to create application
com.google.android.gms.common.app.GmsApplication:
java.lang.SecurityException: addOnPermissionsChangeListener:
Neither user 10039 nor current process has android.permission.OBSERVE_GRANT_REVOKE_PERMISSIONS.
at android.app.ActivityThread.handleBindApplication(ActivityThread.java:5451)
at android.app.ActivityThread.-wrap2(ActivityThread.java)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1564)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:154)
at android.app.ActivityThread.main(ActivityThread.java:6186)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:889)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:779)
or
Code:
java.lang.SecurityException: Permission Denial: opening provider
com.google.android.gsf.gservices.GservicesProvider from
ProcessRecord{22a7d3b 23968:com.google.android.youtube/u0a108}
(pid=23968, uid=10108) requires com.google.android.providers.gsf.permission.READ_GSERVICES or com.google.android.providers.gsf.permission.WRITE_GSERVICES
at android.os.Parcel.readException(Parcel.java:1684)
at android.os.Parcel.readException(Parcel.java:1637)
at android.app.ActivityManagerProxy.getContentProvider(ActivityManagerNative.java:4199)
or
Code:
java.lang.SecurityException: tname=Sensors - Permission Denial: opening provider com.google.android.gsf.gservices.GservicesProvider from ProcessRecord{3745b29 6048:com.google.android.apps.maps/u0a179} (pid=6048, uid=10179) requires com.google.android.providers.gsf.permission.READ_GSERVICES or com.google.android.providers.gsf.permission.WRITE_GSERVICES
They all have in common that they tell me that "Neither user [???] nor current process has android.permission.[???] "
It seems to work uninstalling the specific app and reinstalling it. However this is a lot of work and isn't really easy for some apps that are closer to the system.
So what can I do? What exactly is the problem here? Did the UIDs change? Any suggestions please!