[Q] Different MD5 sums - Verizon Galaxy Note 3 Q&A, Help & Troubleshooting

Maybe I'm doing this wrong, but:
I just changed over to Verizon and rooted recently using Kingo with Safestrap as my recovery. All seems to go well when doing a b/u, but I'm a bit confused regarding the md5 files included in the backup. I'm trying to verify the files I copy to my pc from the phone.
In example:
system.ext4.win000 (on phone) matches system.ext4.win000 on pc
system.ext4.win000.md5 (on phone) matches system.ext4.win000.md5 on pc
but,
system.ext4.win000 does not match system.ext4.win000.md5 on either pc or phone.
The above holds true with 3 different b/u's.
So are the files with the md5 extension solitary md5 sums for easier and faster comparison, or should the md5 files match the win.000 files?
The backups verify on the phone itself using AFV. Simply long pressing on a folder created by SS to contain the backup files returns verified as good. This is why I assume that AFV is comparing the .md5 files to the .win000 files, yet they do not match each other when I manually check with HashTabs.
I hope this isn't too convoluted. Thanks for any input.

Related

MD5 mismatch on nandroid restore?!

Hey Guys, so I tested out a few roms and went to do a nandroid restore and it keeps giving me
Checking MD5 sums...
MD5 mismatch!
All I did was rename the folders from dates to something like "Stock 2.1" and now it won't restore.
Any help? I have all my .img files, why can't I just push them to the system?
EDIT:
I got it fixed guys =D
I right clicked the folder and saw when the folder was created and renamed the folder from
"Stock 2.1 06-24" to the original time and date format "2010-06-24-12-04-39" (or whatever time it was)
Went back into nandroid and checking the md5 sums completed
Click to expand...
Click to collapse
never rename a file that's been md5'd. Create folders name as wished then put the files as wished. The hash is created from the file as a whole including the name. obviously for future reference only.
I do not know how to resolve your current problem.
-------------------------------------
Sent via the XDA Tapatalk App
Had this issue back on the nexus. Just run another backup, delete the files in the new folder and move whichever backup you want into it and it should work
I'm not sure how to recover your files. I'd think finding another nand backup of stock phone would be your best bet?
Sent from my ADR6300 using XDA App
I got it fixed guys =D
I right clicked the folder and saw when the folder was created and renamed the folder from
"Stock 2.1 06-24" to the original time and date format "2010-06-24-12-04-39" (or whatever time it was)
Went back into nandroid and checking the md5 sums completed

Cant load cwm backups

There are no spaces in the file names but it gives me an md5 mismatch?
Sent from my albino HTC Vivid
try naming it something simple like backup. If it still doesn'twork it could be a corrupt file, I've had it happen once.

Rooted phone, backed up efs and then flashed CM9

Hello
I rooted my phone using hardcore's speedmod kernel as shown in the CyanogenMod webpage and then inmediately backed up the /efs folder doing a tar using an Android Terminal Emulator
However, the MD5 files information don't match the files themselves
For example
The MD5 string contained in .nv_data.bak.md5 doesn't match .nv_data.bak
The same for the other files as well.
Is my /efs corrupted? My phone has never been touched before, just stock roms applied thru Kies
I have noticed a new folder has popped up in the /efs folder called "lost+found". Why did it go there?
Do yu have another suggestion to backup the /efs as well? seems doing tarballs looses UNIX/Linux permissions
Thank you.
resotre only one file and reboot
albertocastillo2001 said:
Hello
I rooted my phone using hardcore's speedmod kernel as shown in the CyanogenMod webpage and then inmediately backed up the /efs folder doing a tar using an Android Terminal Emulator
However, the MD5 files information don't match the files themselves
For example
The MD5 string contained in .nv_data.bak.md5 doesn't match .nv_data.bak
The same for the other files as well.
Is my /efs corrupted? My phone has never been touched before, just stock roms applied thru Kies
I have noticed a new folder has popped up in the /efs folder called "lost+found". Why did it go there?
Do yu have another suggestion to backup the /efs as well? seems doing tarballs looses UNIX/Linux permissions
Thank you.
Click to expand...
Click to collapse
I had same problem when I install jelly bean first time on my I9000. After reading of some articles about efs folder I decided to restore only one file .nv_data.bak. And it works. I have done in following steps.
1) Backup full efs folder. (For safty purpose only)
2) Deleted both files nv_data.bin.md5 & nv_data.bin
3) Restored nv_data.bin only (No need to put back md5 file)
4) Restart the phone
Let me know if it works.
Hello
My phone works. It's just I have noticed the backup I made at the beginning just after I rooted my phone don't match. But the backup itself.
The backup files don't match their own .MD5 in the backup itself
Thanks!
Any ideas of why these files don't match?
albertocastillo2001 said:
Hello
My phone works. It's just I have noticed the backup I made at the beginning just after I rooted my phone don't match. But the backup itself.
The backup files don't match their own .MD5 in the backup itself
Thanks!
Click to expand...
Click to collapse
Hello
I've also checked that once in a while, some of the files inside /efs such as nv_data.bin and nv_data.bin.md5 change their modified date.
Any idea of why this happens and why the MD5 data doesn't match?
Thank you.

[HELP] Retrieving TWRP data [SOLVED]

Hello, I would like to know how I could extract backed up TWRP data on my computer? maybe because the data was large TWRP split it into two files : data.ext4.win000 and data.ext4.win001 (sizes 1.5 and 1.2 GB)
How I got there:
I've been using XenonHD rom for quite a while, and this rom uses koush's superuser app.
I noticed there was a newer version on the market so I installed it; however it appears the one used by the rom developer was modified and therefore had a different package name: I ended up with two superuser apps, one of them asking to update the binaries, which I did.
After that the phone got stuck and rebooted two or three times before being stuck indefinitely at 'updating app' message right after the bootanimation. I tried:
- to wipe dalvik cache but it was still stuck;
- I reflashed the rom + gapps but it was still stuck;
- then I went to the /data/app/ folder (via TWRP) and deleted the superuser app i installed from market, as well as the corresponding data in /data/data, wiped cache and dalvik again: still the same...
-the I decided to make a backup via TWRP : one of the whole system, and one of Data partition only;
- then I realised I couldn't transfer it to my computer in TWRP, so I finally made a factory reset, re-flashed the rom+gapps, and then (it worked) copied my backup to the computer
now; how can I retrieve the data of my apps only, as I guess it is the system data that is messed up?
Of course I tried to restore the Data backup in twrp and it got stuck again the same way....
any help greatly appreciated!
You could try appextractor on the play store
Sent from my Nexus 4 using xda app-developers app
forvrknight said:
You could try appextractor on the play store
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
It didn't work for me...
I finally got my data back by this tricky procedure (there might be an easier way but google+xda was not my friend on this one, I tried ext2explore and ext4explore, linux_reader, Andoird_ICS_JB_ext4_unpacker and maybe some more without success)
I renamed the two files:
data.ext4.win000 renamed as data.ext4.tar.001
data.ext4.win001 renamed as data.ext4.tar.002
Unzipping the first one with 7zip recreates a .tar archive named data.ext4.tar, which is not really a tar archive (extracting it will only give a very few files, for me it only included the image files of my custom bootanimation)
On this file I used AccessData FTK Imager, which would recognise the 'evidence' as a tar file and would allow you to export the data, however this is only the data contained originally in the first file (data.ext4.win000) (although the reconstructed archive was the right size, for me 2.7GB, the part extracted by this software was only 1.5GB)
To recover the second part, simply rename the second file (initially data.ext4.win001) into data.7z and then extract. (this does not work with the first file, all you would get is again a very few files, for me it looked like the content of a single apk file)
All you have to do now is to merge the two data folders and voilà
I could then retrieve my sms mms messages by retrieving the file smsmms.db (and eventually smsmms.db-journal) located in /data/data/com.android.providers.telephony/databases, and putting them on the phone in the same folder
I could also retrieve my phone call logs by retrieving the files contacts2.db (and eventually contacts2.db-journal) located in /data/data/com.android.providers.contacts/databases, and putting them on the phone in the same folder
Hope it helps someone someday
For some reason replacing the data folder of a particular app does not always work, I have to investigate a bit or maybe start fresh with a new rom and try again
asim0 said:
It didn't work for me...
I finally got my data back by this tricky procedure (there might be an easier way but google+xda was not my friend on this one, I tried ext2explore and ext4explore, linux_reader, Andoird_ICS_JB_ext4_unpacker and maybe some more without success)
I renamed the two files:
data.ext4.win000 renamed as data.ext4.tar.001
data.ext4.win001 renamed as data.ext4.tar.002
Unzipping the first one with 7zip recreates a .tar archive named data.ext4.tar, which is not really a tar archive (extracting it will only give a very few files, for me it only included the image files of my custom bootanimation)
On this file I used AccessData FTK Imager, which would recognise the 'evidence' as a tar file and would allow you to export the data, however this is only the data contained originally in the first file (data.ext4.win000) (although the reconstructed archive was the right size, for me 2.7GB, the part extracted by this software was only 1.5GB)
To recover the second part, simply rename the second file (initially data.ext4.win001) into data.7z and then extract. (this does not work with the first file, all you would get is again a very few files, for me it looked like the content of a single apk file)
All you have to do now is to merge the two data folders and voilà
I could then retrieve my sms mms messages by retrieving the file smsmms.db (and eventually smsmms.db-journal) located in /data/data/com.android.providers.telephony/databases, and putting them on the phone in the same folder
I could also retrieve my phone call logs by retrieving the files contacts2.db (and eventually contacts2.db-journal) located in /data/data/com.android.providers.contacts/databases, and putting them on the phone in the same folder
Hope it helps someone someday
For some reason replacing the data folder of a particular app does not always work, I have to investigate a bit or maybe start fresh with a new rom and try again
Click to expand...
Click to collapse
It actually helped me, thanks a lot!
Two Questions
asim0 said:
On this file I used AccessData FTK Imager,
Click to expand...
Click to collapse
This is a 4.6 Gigs professional software. If TWRP can read this type of file there must be a smaller tool available for this.
Can you please let me know of any other toll which would do the same?
asim0 said:
All you have to do now is to merge the two data folders and voilà
Click to expand...
Click to collapse
For the 2nd file do we need to follow the same procedure like 'evidence' and stuff?
Thanks, I am desperate to read some information from TWRP backup and cannot wait 6 days while the 4.6 Gigs of ISO will download.
pi_yush said:
This is a 4.6 Gigs professional software. If TWRP can read this type of file there must be a smaller tool available for this.
Can you please let me know of any other toll which would do the same?
For the 2nd file do we need to follow the same procedure like 'evidence' and stuff?
Thanks, I am desperate to read some information from TWRP backup and cannot wait 6 days while the 4.6 Gigs of ISO will download.
Click to expand...
Click to collapse
These files (at least the ones produced by TWRP2 on my phone) are just standard gzipped tar archives. The tar command has supported this format for at least 20 years. You can extract with a command like this:
Code:
tar xvfz data.ext4.win000
tar xvfz data.ext4.win001
number_thirty_two said:
These files (at least the ones produced by TWRP2 on my phone) are just standard gzipped tar archives. The tar command has supported this format for at least 20 years. You can extract with a command like this:
Code:
tar xvfz data.ext4.win000
tar xvfz data.ext4.win001
Click to expand...
Click to collapse
Thanks number_thirty_two, I copyed thes to a folder I named untar in my home folder of CYGWIN, and extracted my system files perfectly
C:\cygwin\home\carl\untar\
system.ext4.win000
system.ext4.win001
tar xvfz system.ext4.win000
tar xvfz system.ext4.win001
Apologies for resurrecting this, but does anyone know how to extract them if they were compressed as .comp files?
asim0 said:
It didn't work for me...
I finally got my data back by this tricky procedure (there might be an easier way but google+xda was not my friend on this one, I tried ext2explore and ext4explore, linux_reader, Andoird_ICS_JB_ext4_unpacker and maybe some more without success)
I renamed the two files:
data.ext4.win000 renamed as data.ext4.tar.001
data.ext4.win001 renamed as data.ext4.tar.002
Unzipping the first one with 7zip recreates a .tar archive named data.ext4.tar, which is not really a tar archive (extracting it will only give a very few files, for me it only included the image files of my custom bootanimation)
On this file I used AccessData FTK Imager, which would recognise the 'evidence' as a tar file and would allow you to export the data, however this is only the data contained originally in the first file (data.ext4.win000) (although the reconstructed archive was the right size, for me 2.7GB, the part extracted by this software was only 1.5GB)
To recover the second part, simply rename the second file (initially data.ext4.win001) into data.7z and then extract. (this does not work with the first file, all you would get is again a very few files, for me it looked like the content of a single apk file)
All you have to do now is to merge the two data folders and voil
Click to expand...
Click to collapse

[Q] Win7 app to open a ***.md5sum

Trying to verify a download with the associated .md5sum file. Tried various programs to verify the actual file download but can not get the associated .md5sum to agree. Used one app to open both files yet they do not match.
The file format in question is like the following: LS-KK-v3.0-2014-04-06-jflte.zip.md5sum
Help?
cyaclone said:
Trying to verify a download with the associated .md5sum file. Tried various programs to verify the actual file download but can not get the associated .md5sum to agree. Used one app to open both files yet they do not match.
The file format in question is like the following: LS-KK-v3.0-2014-04-06-jflte.zip.md5sum
Help?
Click to expand...
Click to collapse
Use this http://www.winmd5.com/ on the original zip file, the results should match the CONTENTS of the .md5sum file.
The .md5sum file is just a string of text, which is the result of running an md5 checksum against a particular file.
-Mike
mcapozzi said:
Use this http://www.winmd5.com/ on the original zip file, the results should match the CONTENTS of the .md5sum file.
The .md5sum file is just a string of text, which is the result of running an md5 checksum against a particular file.
-Mike
Click to expand...
Click to collapse
Thanks for the response but how do I get the string of text out of that md5 checksum file to use to verify what was generated by winmd5 on the ROM file?
cyaclone said:
Thanks for the response but how do I get the string of text out of that md5 checksum file to use to verify what was generated by winmd5 on the ROM file?
Click to expand...
Click to collapse
Open the file with notepad.
Mike
That is great! Thanks for the education and know I now. Tried it and it works. Thanks again, simple when you know how.
Sent from my SPH-L720 using Tapatalk

Categories

Resources