Related
C:\Repair\JFlash_MM>start.bat
C:\Repair\JFlash_MM>jflashmm pxa27x32 ebo_a.nb0 N 0 PAR
JFLASH Version 5.01.007
COPYRIGHT (C) 2000 - 2003 Intel Corporation
PLATFORM SELECTION:
Processor= PXA27x
Development System= Mainstone
Data Version= 1.00.001
PXA27x revision ??
Failed to read the Flash ID. Retrying 4 more times...
Failed to read the Flash ID. Retrying 3 more times...
Upper and Lower flash memory ID does not match.
You may have a damaged flash memory.
Upper half reads: 90
Lower half reads: F000
Failed to read the Flash ID. Retrying 2 more times...
Upper and Lower flash memory ID does not match.
You may have a damaged flash memory.
Upper half reads: 90
Lower half reads: F000
Failed to read the Flash ID. Retrying 1 more times...
Upper and Lower flash memory ID does not match.
You may have a damaged flash memory.
Upper half reads: 90
Lower half reads: F000
Failed to read the Flash ID. Retrying 0 more times...
Cannot open input file: Flash_f000_2_32.dat
This program supports flash devices defined by DAT files
contained in the same directory as the executable program.
If the file cannot be opened, there are four possibilities:
1 - The flash device installed is not supported.
2 - The flash device is a licensed product.
3 - The device ID could not be read, resulting in a poorly
constructed filename. The first numeric value in the
filename is the device ID. Verify this value with the
component specification.
4 - The memory bus is not functional. Check all CPLD and FPGA
devices. Make sure that you are using the correct
platform data file.
C:\Repair\JFlash_MM>jflashmm pxa27x32 ebo_a.nb0 N 3F40000 PAR
JFLASH Version 5.01.007
COPYRIGHT (C) 2000 - 2003 Intel Corporation
PLATFORM SELECTION:
Processor= PXA27x
Development System= Mainstone
Data Version= 1.00.001
PXA27x revision ??
Upper and Lower flash memory ID does not match.
You may have a damaged flash memory.
Upper half reads: 90
Lower half reads: F000
Failed to read the Flash ID. Retrying 4 more times...
Upper and Lower flash memory ID does not match.
You may have a damaged flash memory.
Upper half reads: 90
Lower half reads: F000
Failed to read the Flash ID. Retrying 3 more times...
Upper and Lower flash memory ID does not match.
You may have a damaged flash memory.
Upper half reads: 90
Lower half reads: F000
Failed to read the Flash ID. Retrying 2 more times...
Upper and Lower flash memory ID does not match.
You may have a damaged flash memory.
Upper half reads: 90
Lower half reads: F000
Failed to read the Flash ID. Retrying 1 more times...
Upper and Lower flash memory ID does not match.
You may have a damaged flash memory.
Upper half reads: 90
Lower half reads: F000
Failed to read the Flash ID. Retrying 0 more times...
Cannot open input file: Flash_f000_2_32.dat
This program supports flash devices defined by DAT files
contained in the same directory as the executable program.
If the file cannot be opened, there are four possibilities:
1 - The flash device installed is not supported.
2 - The flash device is a licensed product.
3 - The device ID could not be read, resulting in a poorly
constructed filename. The first numeric value in the
filename is the device ID. Verify this value with the
component specification.
4 - The memory bus is not functional. Check all CPLD and FPGA
devices. Make sure that you are using the correct
platform data file.
Where is the Problem ?????????????????????
Really this is Fcuk Forum
4 days Passed
Still no Help arrived
FCUK You ALL
jtag problem
HI
please see this link for helphttp://forum.xda-developers.com/showthread.php?t=336278
[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
Hi all,
I am using modpunks CM 12.1 on my G850F.
Working very nice. Now I get the following problem(s):
Random freezes, if I get freezings, very regular I cannot switch on the phone instantly. It's draining battery but I cannot boot it (no samsung logo...) nor I cannot boot into recovery. Only download mode works sometimes.
The SAME happens with stock ROM. Tried the "old" frenche XEF version, the "new" one from late november and the one the phone was initially delivered with.
To me it seems kind of if there is either a memory problem OR a CPU problem especially as I only get this problems when using the phone. so I can keep it in my pocket and it works.
Do you have other ideas howto narrow the problem down? Up to now there is no clear variant how to reproduce this behavior. but it happens now very often and EVEN when restoring CM from recovery once.
Best and thanks for your ideas and help,
Blubberor
I would suggest testing with some benchmark app. If it crashes take notice when it did. If not make a clean flash with odin with repertition ticked ON and see if it repeats the error.
Sent from my P6-U06
Same issue
Hi. I have the same issue with my Alpha. Official room, tried to reset several times with no result. It gets hot and then freezes. A friend of mine has same phone and OS version, no freezes encountered. Waiting for an update from Samsung.
Blubberor said:
Hi all,
I am using modpunks CM 12.1 on my G850F.
Working very nice. Now I get the following problem(s):
Random freezes, if I get freezings, very regular I cannot switch on the phone instantly. It's draining battery but I cannot boot it (no samsung logo...) nor I cannot boot into recovery. Only download mode works sometimes.
The SAME happens with stock ROM. Tried the "old" frenche XEF version, the "new" one from late november and the one the phone was initially delivered with.
To me it seems kind of if there is either a memory problem OR a CPU problem especially as I only get this problems when using the phone. so I can keep it in my pocket and it works.
Do you have other ideas howto narrow the problem down? Up to now there is no clear variant how to reproduce this behavior. but it happens now very often and EVEN when restoring CM from recovery once.
Best and thanks for your ideas and help,
Blubberor
Click to expand...
Click to collapse
flc555 said:
Hi. I have the same issue with my Alpha. Official room, tried to reset several times with no result. It gets hot and then freezes. A friend of mine has same phone and OS version, no freezes encountered. Waiting for an update from Samsung.
Click to expand...
Click to collapse
my wife as well.
although I have to admit, mine had to go 3 times to Samsung CSC, while hers is just working fine.
This is just a strange happening.
will do two things. soon.
Complete erase of all files.
Will open the phone to check if I see something strange...
In case I can get it back to work I will report back.
Best,
Blubberor
Why is it no matter what i post on XDA people just ignore it wut
now its official.
Odin was not able to repartition only regular flashing..., while completely opening in the end the display broke.
so I loved this phone, but as it made problems all over the time (even before testing and using CM (thx @modpunk ones again!!!)) won't stick to samsung.
now first use the good old nexus 4....
best and thanks to all from the samsung alpha area here on xda!!
was lucky...had the phone connected to adb and logcat was running when it crashed.
maybe someone can have a look. to me there is nothing strange on the system going on...
I have checked with E2FSCK memory and integrity of SYSTEM, DATA, EFS....partition without any strange error reports..
I was wondering if one can fully check the whole memory to exclude just bad blocks.
right now the phone was just charging when I unlocked screen and was starting logcat---
Code:
01-03 16:25:04.882 10126 10126 W GAv4 : AnalyticsReceiver is not registered or is disabled. Register the receiver for reliable dispatching on non-Google Play devices. See http://goo.gl/8Rd3yj for instructions.
01-03 16:25:04.886 10126 10126 W GAv4 : CampaignTrackingReceiver is not registered, not exported or is disabled. Installation campaign tracking is not possible. See http://goo.gl/8Rd3yj for instructions.
01-03 16:25:04.891 10126 10163 W GAv4 : AnalyticsService not registered in the app manifest. Hits might not be delivered reliably. See http://goo.gl/8Rd3yj for instructions.
01-03 16:25:04.990 2865 5470 I ActivityManager: Start proc 10164:com.estrongs.android.pop/u0a160 for broadcast com.estrongs.android.pop/.app.StartServiceReceiver
01-03 16:25:05.003 2865 3167 I ActivityManager: Killing 9510:com.android.deskclock/u0a39 (adj 15): empty #17
01-03 16:25:05.264 2457 2457 D gpsd : WakeLock(Acquire,GPSD)
01-03 16:25:05.264 2457 2457 D gpsd : WakeLock(Release,GPSD)
01-03 16:25:05.277 2865 3106 D WifiService: releaseWifiLockLocked: WifiLock{NlpWifiLock type=2 [email protected]}
01-03 16:25:05.361 3066 10110 I SecHAL : device_sleep: NFC can be going to sleep
01-03 16:25:05.405 4517 4630 I GCoreUlr: Successfully inserted 3 locations
01-03 16:25:05.409 4517 4630 I GCoreUlr: Starting service, intent=Intent { act=com.google.android.location.reporting.UPLOAD cmp=com.google.android.gms/com.google.android.location.reporting.service.DispatchingService }, extras=null
01-03 16:25:05.416 10164 10184 W ResourceType: No package identifier when getting value for resource number 0x00000000
01-03 16:25:05.421 2865 2979 D WifiService: New client listening to asynchronous messages
01-03 16:25:05.495 2865 3622 I ActivityManager: Killing 8291:com.cyanogenmod.lockclock/u0a53 (adj 15): empty #17
01-03 16:25:05.893 4517 10195 W BaseAppContext: Using Auth Proxy for data requests.
01-03 16:25:05.917 4517 4517 V GLSActivity: AuthDelegateWrapperCreated with selected intent: Intent { cmp=com.google.android.gms/.auth.DefaultAuthDelegateService }
01-03 16:25:05.925 4517 4517 V GLSActivity: AuthDelegateWrapperCreated with selected intent: Intent { cmp=com.google.android.gms/.auth.DefaultAuthDelegateService }
01-03 16:25:06.218 4517 4525 E DataBuffer: Internal data leak within a DataBuffer object detected! Be sure to explicitly call release() on all DataBuffer extending objects when you are done with them. (internal object: [email protected])
01-03 16:25:06.220 4517 4525 E DataBuffer: Internal data leak within a DataBuffer object detected! Be sure to explicitly call release() on all DataBuffer extending objects when you are done with them. (internal object: [email protected])
01-03 16:25:06.222 4517 4525 E DataBuffer: Internal data leak within a DataBuffer object detected! Be sure to explicitly call release() on all DataBuffer extending objects when you are done with them. (internal object: [email protected])
01-03 16:25:06.224 4517 4525 E DataBuffer: Internal data leak within a DataBuffer object detected! Be sure to explicitly call release() on all DataBuffer extending objects when you are done with them. (internal object: [email protected])
01-03 16:25:06.226 4517 4525 E DataBuffer: Internal data leak within a DataBuffer object detected! Be sure to explicitly call release() on all DataBuffer extending objects when you are done with them. (internal object: [email protected])
01-03 16:25:06.255 2865 5101 D NetlinkSocketObserver: NeighborEvent{elapsedMs=382899, fd00::9ec7:a6ff:fe12:55e6, [9CC7A61255E6], RTM_NEWNEIGH, NUD_REACHABLE}
01-03 16:25:06.705 2865 2980 D ConnectivityService: notifyType CAP_CHANGED for NetworkAgentInfo [WIFI () - 100]
01-03 16:25:06.730 4517 10195 I GCoreUlr: Batch Location Update succeeded for account account#-16#
01-03 16:25:06.767 4517 10195 I GCoreUlr: Upload task finished
01-03 16:25:06.770 2865 2876 W AppOps : Finishing op nesting under-run: uid 10012 pkg com.google.android.gms code 40 time=1451834705429 duration=97 nesting=0
01-03 16:25:06.819 2451 2899 V audio_hw_primary: do_out_standby: output standby: 0
01-03 16:25:06.877 3012 3012 D PhoneStatusBar: disable: < expand ICONS* alerts SYSTEM_INFO* back home recent clock search quick_settings >
01-03 16:25:08.695 2451 2899 V audio_hw_primary: out_set_parameters: key value pairs: routing=2
01-03 16:25:08.698 9786 9786 W System : ClassLoader referenced unknown path: /system/framework/tcmclient.jar
01-03 16:25:08.706 2451 2899 V audio_hw_primary: start_output_stream: starting stream
01-03 16:25:08.709 2451 2899 V audio_hw_primary: *** select_devices: Routing hasn't changed, leaving function.
01-03 16:25:08.709 2451 2899 V audio_hw_primary: start_output_stream: stream out device: 2, actual: 2
Blubberor said:
was lucky...had the phone connected to adb and logcat was running when it crashed.
maybe someone can have a look. to me there is nothing strange on the system going on...
I have checked with E2FSCK memory and integrity of SYSTEM, DATA, EFS....partition without any strange error reports..
I was wondering if one can fully check the whole memory to exclude just bad blocks.
right now the phone was just charging when I unlocked screen and was starting logcat---
Code:
01-03 16:25:04.882 10126 10126 W GAv4 : AnalyticsReceiver is not registerэ...
Click to expand...
Click to collapse
I'll help you. Turn the unlocking fingerprint.
What does this mean exactly?
Still have freezings. Kind of desperate how to brick the device..
Sent from my Nexus 4 using XDA Free mobile app
Turn off unlocking fingerprint.
Volks.com.ua said:
Turn off unlocking fingerprint.
Click to expand...
Click to collapse
would even be not supported in CM13 so there is no option I guess.
Thanks already - fingerprint was already exchanged and broken again bei CSP some months ago....
Best,
Blubberor
Hi! My cellphone has the same problem. Please, let me know if you could solve it.
Thanks,
Pablo
pablitolandia said:
Hi! My cellphone has the same problem. Please, let me know if you could solve it.
Thanks,
Pablo
Click to expand...
Click to collapse
Unfortunately could not solve it.
No errors in file checks, efs restored....Samsung refused warranaty due to Knox. Today a used alpha that I bought is going to arrive.
Good luck.
Blubberor
Sent from my Nexus 4 using XDA Free mobile app
Hi all, a quick fix that worked for me was to use another launcher.
nickps17 said:
Hi all, a quick fix that worked for me was to use another launcher.
Click to expand...
Click to collapse
To me happened with Stock as well as with cm.
Crossing the fingers for you.
Sent from my SM-G850F using XDA Free mobile app
I was trying to flash developer rom using mi flash in download mode. It was taking longer than usual and I pulled off the plug after more than 20 minutes. Now I'm stuck at bootloop. My device is restarting simutaneously. Can't enter download mode. I can enter fasboot mode though, but the bootloader is locked!! vol(+) + vol (-) + power button takes me to adb mode. tried adb commands to boot into edl, didn't work either... what can I do now?? Please Help!!!
In bootloader screen when you press download button it should go to edl mode, black screen.
yeah me too. mine was on boot loop or if use power with(+) it black and red light as edl but Com10 doesnt appear
And in Power (-) fastboot come but miflash appear strange name 16ca731 and cant flash. so sad,
saikatmitra71 said:
I was trying to flash developer rom using mi flash in download mode. It was taking longer than usual and I pulled off the plug after more than 20 minutes. Now I'm stuck at bootloop. My device is restarting simutaneously. Can't enter download mode. I can enter fasboot mode though, but the bootloader is locked!! vol(+) + vol (-) + power button takes me to adb mode. tried adb commands to boot into edl, didn't work either... what can I do now?? Please Help!!!
Click to expand...
Click to collapse
When you boot to stock recovery (abd mode) you can use Mi PC Suite and R-flash your device
saikatmitra71 said:
I was trying to flash developer rom using mi flash in download mode. It was taking longer than usual and I pulled off the plug after more than 20 minutes. Now I'm stuck at bootloop. My device is restarting simutaneously. Can't enter download mode. I can enter fasboot mode though, but the bootloader is locked!! vol(+) + vol (-) + power button takes me to adb mode. tried adb commands to boot into edl, didn't work either... what can I do now?? Please Help!!!
Click to expand...
Click to collapse
hello, i have the similar problem!
No EDL, No Fastboot, No boot logo and No charging Animaton.
Phone is not recognized as a device in Device manger.
Device manager is showing "Qualcomm Hs Usb Qdloader 9008".
when I try flashing in miflash 2016.04.01 with Fastboot rom, the error appears: "0x80070026: Receiving hello packet"
you managed to find a solution?
greetings
Goku5 said:
hello, i have the similar problem!
No EDL, No Fastboot, No boot logo and No charging Animaton.
Phone is not recognized as a device in Device manger.
Device manager is showing "Qualcomm Hs Usb Qdloader 9008".
when I try flashing in miflash 2016.04.01 with Fastboot rom, the error appears: "0x80070026: Receiving hello packet"
you managed to find a solution?
greetings
Click to expand...
Click to collapse
I solved this problem, but cant post link.. :/
but now I'm in another problem just like yours and found no solution till now...
saikatmitra71 said:
I solved this problem, but cant post link.. :/
Click to expand...
Click to collapse
Can you explain a little bit more about what you did for pass this state?
Valdem said:
Can you explain a little bit more about what you did for pass this state?
Click to expand...
Click to collapse
try this http://en.miui.com/forum.php?mod=redirect&goto=findpost&ptid=283484&pid=5299877
Based on my experiences (bootloop no Fastboot n EDL). This step need you to teardown some parts :
1. Remove your Sim
2. Pull (spudger/or your nail) remove the battery cover.
3. Screwdriver, removes the battery connector cover, pull your battery flex. In this state the phone was totally dead.
4. Put back all parts and the connector battery flex, BUT DO NOT TURN / Push the power button!!
5. Plug your usb to the phone (not the PC). While you keep hold the volume +/- togather, connect your usb cable to the pc while keep hold the volume+/- button.
4. Profit if youre lucky now youre on EDL (download mode)
5. Run miflash and wait till finoshed flash.
Hope youre lucky
SH1M4BD3 said:
Based on my experiences (bootloop no Fastboot n EDL). This step need you to teardown some parts :
1. Remove your Sim
...
5. Run miflash and wait till finoshed flash.
Hope youre lucky
Click to expand...
Click to collapse
Thanks for recomendation, but looks like I have little bit different situation.
1. As I explained I have no any visible activity.
2. But if I connect phone to the PC i see new device "Qualcomm HS-USB QDLoader 9008". It looks promissing.
3. But when I tried to flash it with miflash I got error "Reached the end of the file.(0x80070026 Receiving hello packet)".
No. Positive results. I can't flash it, and I don't know what to do.
Lets see how many rom(fastbotrom) youve try?and which miflash version yore use also make sure that youre on 64bit OS
SH1M4BD3 said:
Lets see how many rom(fastbotrom) youve try?and which miflash version yore use also make sure that youre on 64bit OS
Click to expand...
Click to collapse
Hi.
I tried to flash fastboot roms of next versions - 6.3.31 and 7.3.2.0. With "miFlash 2015.10.28.0" and "XiaoMiFlash(Beta)" (can't find version of this beta) and "QFil 1.0.0.2".
What I found during my investigation. That error happened so quick after start, it looks like software can't connect to device. I installed serial port sniffer to monitor activity of software on port, and I didn't see any traffic. Only few bytes during connecting device. I think that related to drivers. But I tried to do that on different PC with "Win7 x64" and "Win 8.1 x64" and tried with different drivers and of course disable signature checks during my attempts.
What I found in the log of miFlash:
Code:
[00000C60]COM20 0.13 Load programmer "C:\Temp\ido_7.3.2.0\images\prog_emmc_firehose_8936.mbn"
[00000C60]DownloadFlashProgrammerDMSS(625): An attempt was made to load a program with an incorrect format.(0x8007000b)
[00000C60]DownloadFlashProgrammer(930): An attempt was made to load a program with an incorrect format.(0x8007000b)
[00000C60]COM20 0.14 Open programmer "C:\Temp\ido_7.3.2.0\images\prog_emmc_firehose_8936.mbn"
[00000C60]COM20 0.14 Open serial port "\\.\COM20"
[00000C60]COM20 0.14 Receiving hello packet
[00000C60]COM20 0.14 Send hello response
[00000C60]COM20 0.14 EndTransferPacket id 0, status 9
[00000C60]DownloadFlashProgrammer(933): Unspecified error(0x80004005)
this I have when I start flashing first time after connection
and this after second attempt without reconnection:
Code:
[00000600]COM20 0.05 Load programmer "C:\Temp\ido_7.3.2.0\images\prog_emmc_firehose_8936.mbn"
[00000600]DownloadFlashProgrammerDMSS(625): An attempt was made to load a program with an incorrect format.(0x8007000b)
[00000600]DownloadFlashProgrammer(930): An attempt was made to load a program with an incorrect format.(0x8007000b)
[00000600]COM20 0.05 Open programmer "C:\Temp\ido_7.3.2.0\images\prog_emmc_firehose_8936.mbn"
[00000600]COM20 0.05 Open serial port "\\.\COM20"
[00000600]COM20 0.05 Receiving hello packet
[00000600]ReadRobust(202): Reached the end of the file.(0x80070026)
[00000600]ReadRobust(202): Reached the end of the file.(0x80070026)
[00000600]ReadRobust(202): Reached the end of the file.(0x80070026)
[00000600]ReadRobust(202): Reached the end of the file.(0x80070026)
[00000600]ReadRobust(202): Reached the end of the file.(0x80070026)
[00000600]ReadRobust(202): Reached the end of the file.(0x80070026)
[00000600]ReadRobust(202): Reached the end of the file.(0x80070026)
[00000600]ReadRobust(202): Reached the end of the file.(0x80070026)
[00000600]ReadRobust(202): Reached the end of the file.(0x80070026)
[00000600]ReadRobust(202): Reached the end of the file.(0x80070026)
[00000600]ReadRobust(209): Reached the end of the file.(0x80070026)
[00000600]DownloadFlashProgrammerSahara(781): Reached the end of the file.(0x80070026)
[00000600]COM20 2.23 Missed hello packet, try to recover
[00000600]COM20 2.23 Switch mode back
[00000600]COM20 2.23 Receiving hello packet
[00000600]ReadRobust(202): Reached the end of the file.(0x80070026)
[00000600]ReadRobust(202): Reached the end of the file.(0x80070026)
[00000600]ReadRobust(202): Reached the end of the file.(0x80070026)
[00000600]ReadRobust(202): Reached the end of the file.(0x80070026)
[00000600]ReadRobust(202): Reached the end of the file.(0x80070026)
[00000600]ReadRobust(202): Reached the end of the file.(0x80070026)
[00000600]ReadRobust(202): Reached the end of the file.(0x80070026)
[00000600]ReadRobust(202): Reached the end of the file.(0x80070026)
[00000600]ReadRobust(202): Reached the end of the file.(0x80070026)
[00000600]ReadRobust(202): Reached the end of the file.(0x80070026)
[00000600]ReadRobust(209): Reached the end of the file.(0x80070026)
[00000600]DownloadFlashProgrammerSahara(814): Reached the end of the file.(0x80070026)
Valdem said:
Hi.
I tried to flash fastboot roms of next versions - 6.3.31 and 7.3.2.0. With "miFlash 2015.10.28.0" and "XiaoMiFlash(Beta)" (can't find version of this beta) and "QFil 1.0.0.2".
What I found during my investigation. That error happened so quick after start, it looks like software can't connect to device. I installed serial port sniffer to monitor activity of software on port, and I didn't see any traffic. Only few bytes during connecting device. I think that related to drivers. But I tried to do that on different PC with "Win7 x64" and "Win 8.1 x64" and tried with different drivers and of course disable signature checks during my attempts.
What I found in the log of miFlash:
Code:
[00000C60]COM20 0.13 Load programmer "C:\Temp\ido_7.3.2.0\images\prog_emmc_firehose_8936.mbn"
[00000C60]DownloadFlashProgrammerDMSS(625): An attempt was made to load a program with an incorrect format.(0x8007000b)
[00000C60]DownloadFlashProgrammer(930): An attempt was made to load a program with an incorrect format.(0x8007000b)
[00000C60]COM20 0.14 Open programmer "C:\Temp\ido_7.3.2.0\images\prog_emmc_firehose_8936.mbn"
[00000C60]COM20 0.14 Open serial port "\\.\COM20"
[00000C60]COM20 0.14 Receiving hello packet
[00000C60]COM20 0.14 Send hello response
[00000C60]COM20 0.14 EndTransferPacket id 0, status 9
[00000C60]DownloadFlashProgrammer(933): Unspecified error(0x80004005)
this I have when I start flashing first time after connection
and this after second attempt without reconnection:
Code:
[00000600]COM20 0.05 Load programmer "C:\Temp\ido_7.3.2.0\images\prog_emmc_firehose_8936.mbn"
[00000600]DownloadFlashProgrammerDMSS(625): An attempt was made to load a program with an incorrect format.(0x8007000b)
[00000600]DownloadFlashProgrammer(930): An attempt was made to load a program with an incorrect format.(0x8007000b)
[00000600]COM20 0.05 Open programmer "C:\Temp\ido_7.3.2.0\images\prog_emmc_firehose_8936.mbn"
[00000600]COM20 0.05 Open serial port "\\.\COM20"
[00000600]COM20 0.05 Receiving hello packet
[00000600]ReadRobust(202): Reached the end of the file.(0x80070026)
[00000600]ReadRobust(202): Reached the end of the file.(0x80070026)
[00000600]ReadRobust(202): Reached the end of the file.(0x80070026)
[00000600]ReadRobust(202): Reached the end of the file.(0x80070026)
[00000600]ReadRobust(202): Reached the end of the file.(0x80070026)
[00000600]ReadRobust(202): Reached the end of the file.(0x80070026)
[00000600]ReadRobust(202): Reached the end of the file.(0x80070026)
[00000600]ReadRobust(202): Reached the end of the file.(0x80070026)
[00000600]ReadRobust(202): Reached the end of the file.(0x80070026)
[00000600]ReadRobust(202): Reached the end of the file.(0x80070026)
[00000600]ReadRobust(209): Reached the end of the file.(0x80070026)
[00000600]DownloadFlashProgrammerSahara(781): Reached the end of the file.(0x80070026)
[00000600]COM20 2.23 Missed hello packet, try to recover
[00000600]COM20 2.23 Switch mode back
[00000600]COM20 2.23 Receiving hello packet
[00000600]ReadRobust(202): Reached the end of the file.(0x80070026)
[00000600]ReadRobust(202): Reached the end of the file.(0x80070026)
[00000600]ReadRobust(202): Reached the end of the file.(0x80070026)
[00000600]ReadRobust(202): Reached the end of the file.(0x80070026)
[00000600]ReadRobust(202): Reached the end of the file.(0x80070026)
[00000600]ReadRobust(202): Reached the end of the file.(0x80070026)
[00000600]ReadRobust(202): Reached the end of the file.(0x80070026)
[00000600]ReadRobust(202): Reached the end of the file.(0x80070026)
[00000600]ReadRobust(202): Reached the end of the file.(0x80070026)
[00000600]ReadRobust(202): Reached the end of the file.(0x80070026)
[00000600]ReadRobust(209): Reached the end of the file.(0x80070026)
[00000600]DownloadFlashProgrammerSahara(814): Reached the end of the file.(0x80070026)
Click to expand...
Click to collapse
hello, I also have the same problem as you!
tries to use this latest version of qfil http://www.androidbrick.com/download/qpst-2-7-430-latest-qfil-qualcomm-flasher/ (I've tried but without success)
Hi,
I had the similar problem too with my Redmi 3. And I solved it.
My Redmi was unlocked but, I don't know why, it has a safety inside which lock it if you do wrong things.
I get to installed the original stable rom using MiFlash but only after I used MiUnlock software.
Before that I got same error code you've shown. The phone refused to flash system,data,recovery using fastboot . You can see if you get the same error code by trying to flash it using ADB and fastboot minimal:
http://forum.xda-developers.com/showthread.php?t=2317790
the error code was something like that: "system locked"
Hey try this miflash its beta https://docs.google.com/uc?export=download&confirm=HxZL&id=0BywPW6N-K7C2Nlo5WlNyRXVKblE credit to Manh_IT its allowed to flash in fastboot mode (lock/unlocked BL) no need EDL according to his statements
For redmi 3 : unbrick rom https://drive.google.com/file/d/0B40ItdHKfkyQbTg5SHZ2TWp3S1U/view?usp=sharing&pref=2&pli=1
Or this one : https://drive.google.com/file/d/0B40ItdHKfkyQVm9yS0JwN01lWlk/view?pref=2&pli=1
Sources : http://choimobile.vn
SH1M4BD3 said:
Hey try this miflash its beta https://docs.google.com/uc?export=download&confirm=HxZL&id=0BywPW6N-K7C2Nlo5WlNyRXVKblE credit to Manh_IT its allowed to flash in fastboot mode (lock/unlocked BL) no need EDL according to his statements
For redmi 3 : unbrick rom https://drive.google.com/file/d/0B40ItdHKfkyQbTg5SHZ2TWp3S1U/view?usp=sharing&pref=2&pli=1
Or this one : https://drive.google.com/file/d/0B40ItdHKfkyQVm9yS0JwN01lWlk/view?pref=2&pli=1
Sources : http://choimobile.vn
Click to expand...
Click to collapse
error this miflash: "can not read from port COM8"
Oke back and use stable miflash then
SH1M4BD3 said:
Oke back and use stable miflash then
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
continues with error
Did you guys try this :
http://en.miui.com/forum.php?mod=viewthread&tid=254606&extra=page=1&mobile=2
http://en.miui.com/thread-277276-1-1.html
[email protected]@[email protected] said:
Did you guys try this :
http://en.miui.com/forum.php?mod=viewthread&tid=254606&extra=page=1&mobile=2
http://en.miui.com/thread-277276-1-1.html
Click to expand...
Click to collapse
Yes, several times ...! but redmi 3 remains in a deep coma, with no activity
whatsapp chat backup got corrupted and chats were unable to restore. Thanks to whatsapp db key xtractor i pulled the crypt key decrypted the db to .db form. opened up whatsapp xtract and it auto repaired my db.
the following msg appears for this db alone.
H:\Whatsapp_Xtract_V2.2_2012-11-17>python "H:\Whatsapp_Xtract_V2.2_2012-11-17\whatsapp_xtract.py" H:\Whatsapp_Xtract_V2.2_2012-11-17\msgstore.db
Python Version 2.x
Android mode!
printing output to H:\Whatsapp_Xtract_V2.2_2012-11-17\msgstore.db.html ...
Traceback (most recent call last):
File "H:\Whatsapp_Xtract_V2.2_2012-11-17\whatsapp_xtract.py", line 2453, in <module>
main(sys.argv[1:])
File "H:\Whatsapp_Xtract_V2.2_2012-11-17\whatsapp_xtract.py", line 1921, in main
linkimage = findfile ("IMG", y.media_size, y.local_url, date, 2)
File "H:\Whatsapp_Xtract_V2.2_2012-11-17\whatsapp_xtract.py", line 1266, in findfile
timestamptoday = int(str(time.mktime(datetime.datetime.strptime(date, "%Y%m%d").timetuple()))[:-2])
File "C:\Python27\lib\_strptime.py", line 332, in _strptime
(data_string, format))
ValueError: time data 'N/A' does not match format '%Y%m%d'
Press any key to continue . . .
the db is readable in whatsapp viewer but db does not get restored in whatsapp gets stuck at 32%
this error does not happen for any other db file. i am not sure where the error is. kindly help