I've got 3 CWM backups on the internal memory of my Samsung SG2.
I tried to restore one and it failed on md5 mismatch/error (or something to that effect...) - tried the others - all returned the same error, yet when I'd actually backed them up, they all completed successfully.
The one thing I did to them all, was give them a more recognisable name, rather than just the date & time so I knew which ROM they were...so out of interest, I backed up my existing (new) Cognito ROM while still in CWM, then when it had finished the back up, immediately tried to restore the newly backed up ROM....and it worked! Is it failing on the others because I've renamed the CWM backup folder?? I'm sure I've done this in the past on my old HTC Desire, and had no problems
Also, is there a way to rescue the backups I've done by generating a new md5 checksum for the renamed backups...or are they toast now??
Thanks for any help...
Willie_Heckerslyke said:
Also, is there a way to rescue the backups I've done by generating a new md5 checksum for the renamed backups...or are they toast now??
Thanks for any help...
Click to expand...
Click to collapse
Google and you will find:
# cd /sdcard/clockworkmod/backup/2010-06-29.20.22.53 (Which is your clockwork mod backup folder)
# rm nandroid.md5
# md5sum *img > nandroid.md5
Do this from a terminal emulator or from adb...
Thanks karendar...but I'm afraid I'm a bit crap at adb and that kinda stuff
I've downloaded an emulator off the market and when I fire it up, I got a $ prompt; found out how to get # prompt but when I put all that in, it gives the following error:-
"md5sum: can't open '*Img': No such file or directory"
When I looked inside the backup folder, there are a series of img files so is the wildcard * is to be put for each file in the back up folder? (I tried one of them - the boot.img file in there, this time there was no error brought up....but I also never got any 'success' confirmation or anything
Help
(BTW....whenever I type the letter 'i' - it changes into a capital 'I' all the time... What's that all about??)
**Bump** anyone??
Rename your backups and make sure there are no spaces in the names. Or keep them to a maximum of one space.
That way there will be no problem with md5 mismatch.
Considering your issue with md5sum: turn off autocorrection in your keyboard settings, and then make sure the command you are typing is
Code:
md5sum *.img
Note that as Android is Linux, capitalisation matters, and *Img will return no results at all.
Thanks dude, i had the same problem on my P500, and your tip helped a lot!
Especially since my phone was stuck in a bootloop and my recoverys wouldnt work... You learn something every day!
Gasai Yuno said:
Rename your backups and make sure there are no spaces in the names. Or keep them to a maximum of one space.
That way there will be no problem with md5 mismatch.
Considering your issue with md5sum: turn off autocorrection in your keyboard settings, and then make sure the command you are typing is
Code:
md5sum *.img
Note that as Android is Linux, capitalisation matters, and *Img will return no results at all.
Click to expand...
Click to collapse
..
Related
When I try to restore certain backups in CWR it says MD5 mismatch. Wat causes thus? It seems to be the name.
Note: I'm not altering the number sequence. Just adding to the end.
Is it cuz I use numbers or wat?
Sent from my ADR6400L using XDA App
I had a few instances of this happening before and when I opened the .md5 file located in the nandroid backup folder and actually ran the md5sum myself I got a mismatch. I don't recommend changing the .md5 file to the correct md5sum.
To check it yourself, use terminal:
Code:
cd /sdcard/clockworkmod/backup/<path to nandroid>/
cat nandroid.md5
md5sum *.img
There you can see if there are discrepancies.
Awesome. This forum's become soooo essential to me. Tundra 4the help.
Sent from my ADR6400L using XDA App
Im having the same issue. If i rename a backup in RM and then try to reflash it, I always get MD5 mismatch. So whats the solution?
yo, i found a solution that worked for me:
just rename the the folder to its original tittle fx. "2011-06-30.15.21.11"
and then try restore again !
MD5 checks the integrity of the entire file.....you change something (even the name of the folder) and the MD5 checksum will fail.....I never rename my nandroids, nor any .zips I flash....I've never downloaded anything from here that was named in such a way that I wouldn't know what it was....
xNitebreedx said:
MD5 checks the integrity of the entire file.....you change something (even the name of the folder) and the MD5 checksum will fail.....I never rename my nandroids, nor any .zips I flash....I've never downloaded anything from here that was named in such a way that I wouldn't know what it was....
Click to expand...
Click to collapse
I'm calling foul on this one. I have renamed my folders for over a year without issue. Only had one problem recently with updating to CM7 on DroidX (using new 2nd init recovery). As long as there are no spaces in the folder name it works fine.
Read somewhere before that not enough space on your sd card may cause MD5 errors. I always thought recovery might have to 'unpack' the files somewhere to restore and if there's not enough space then it would produce an error. I have not tested this out myself.
md5's are stored for each .img not for the entire folder. As someone else said, I've been renaming backups for about 18 months on devices. As long as you don't include spaces (if renamed with RM it should warn you of this) you're fine. Chars like "- . _" are fine just no spaces.
I recently tried a new ROM and made a Rom Manager recovery restore file prior to changing. Things didn't work out as well as I had hoped and when attempting to restore, it fails at the checking MD5 sum process.
Any way to work around this? I really would like to restore to the previous ROM without starting over.
Anybody? I am not quite sure how the restore file can be created on this phone and then not pass verification?
Any ideas or am I stuck starting over?
sandiegopaneraiguy said:
Anybody? I am not quite sure how the restore file can be created on this phone and then not pass verification?
Any ideas or am I stuck starting over?
Click to expand...
Click to collapse
depending on the type of file format used to backup, the restoring could be done manually but a changed md5sum generally means the files are not the same as the original. this could result in corruption and generally it isnt recommended to restore corrupted files as you run the risk of nothing working.
if you're still wanting to proceeding with attempting to restore files which are different than the original and could be corrupted, off the top of my head, you can probably dd the .img files back and untar the .tar files back.
i would suggest starting over and perhaps copying the backup files over to your desktop instead of only leaving on the sdard. this should help ensure at least one of the copies maintains their integrity.
hope that helps!
You can boot into recovery, and run nandroid via adb shell command line, no md5 checksum file needed. Now if the image is bad, you of course get bad results, but if the checksum is just hosed for some reason, it will work fine.
Put the .win files for the partitions you want to restore in /sdacrd
then issue the command "tar xvpf /sdcard/data.win" or "tar xvpf /sdcard/system.win" from the adb shell while in /data or /system respectively. .win files are what TWRP creates for backups.
I had this happen with TWRP 1.01 or 1.02 once on a good backup that passed the checksum tests when I backed it up.
I was testing the reliability of the TWRP package's nandroid and first one failed.
Once I moved to the newer version, I've not had that issue.
Went to install a backup made with CWM today. This is the first time I've done a restore on this phone. Went to restore and am getting an MD5 mismatch on all 3 of my backups!
I have not moved the files or changed their names. They are right where CWM put them.
I've had trouble with the newer versions of CWM in the past that use the TAR files instead of an image file.
I deleted the MD5 file and through terminal did a md5sum *.* > nandroid.md5 to create a new MD5 file but it doesn't work. Is the *.* a proper way to wildcard all files in the directory under linux? Is this the correct way to do it or is it just one of the files I should be doing the MD5 for?
Thanks for the help!
Mike
Can't believe no one has an answer for this.
I did answer my question about the proper syntax for the MD5, it's: md5sum * > nandroid.md5 in case anyone wants to know.
I did finally get my phone to restore. I removed the RAZR bootstrap and reinstalled it and bang, it installed just fine.
Mike
Can you say exactly how you did it? Would be quite interested to know.
Hi friends i would like to share the problem that i faced and solved with other's help.
This thread is only for the people who have the md5 mismatch error while restoring nandroid backups. I created this thread since there were no similar questioned thread.
This error comes usually due to renaming the nandroid backup folders.
Try any one of the following fixes to solve this,
1. Use a program editor like notepad++ to open the nandroid.md5 file and remove all lines except the first line which would have some hex values follwed by boot.img.
2. run the following commands in terminal emulator of ur android:
#cd /sdcard/clockworkmod/backup/(name of backup)
#rm nandroid.md5
#md5sum *img > nandroid.md5
Hit the thanks button if u think the post to be helpful!
I've tried, but didn't generate a new checksum?!?
Tedo said:
I've tried, but didn't generate a new checksum?!?
Click to expand...
Click to collapse
Are you sure u typed the commands correctly. The command surely creates a nandroid.md5 file in the nandroid backup folder with the checksum values.
parkourkarthik said:
Are you sure u typed the commands correctly. The command surely creates a nandroid.md5 file in the nandroid backup folder with the checksum values.
Click to expand...
Click to collapse
all good and well...why step one though? if you're just rm'ing it...seems a little unnecessary....? sorry i just performed step one then looked at step 2 and thought..wtf! lol unless theres something im clearly missing....?
sinner99 said:
all good and well...why step one though? if you're just rm'ing it...seems a little unnecessary....? sorry i just performed step one then looked at step 2 and thought..wtf! lol unless theres something im clearly missing....?
Click to expand...
Click to collapse
I am sorry did i miss saying that u can use any one of the fixes!! That means it's not a step by step it's either this or that, u can use whatever u wish that would be easy for u aong the two methods..
Sent from my GT-S6102 using XDA
Files not found
where to find these nandroid backup files
rjawan said:
where to find these nandroid backup files
Click to expand...
Click to collapse
Hi,
Look on your sd card/clockworkmod/backup.
Missing backup files
Have an AT&T Samsung Galaxy S4 (SGH-i337) Have made a couple of backups with CM and they show up in the Backup and Restore when in CM app. The path shows /mnt/shell/emulated/clockworkmod/backup but when I use ES File Explorer or Explorer they are not to be found. I can open /mnt/shell but the shell folder says 'Empty Folder'.
The reason I want to open the backups is to fix the MD5 checksum errors I always get when trying to restore.
It must be something simple but I can't figure it out.
parkourkarthik said:
Hi friends i would like to share the problem that i faced and solved with other's help.
This thread is only for the people who have the md5 mismatch error while restoring nandroid backups. I created this thread since there were no similar questioned thread.
This error comes usually due to renaming the nandroid backup folders.
Try any one of the following fixes to solve this,
1. Use a program editor like notepad++ to open the nandroid.md5 file and remove all lines except the first line which would have some hex values follwed by boot.img.
2. run the following commands in terminal emulator of ur android:
#cd /sdcard/clockworkmod/backup/(name of backup)
#rm nandroid.md5
#md5sum *img > nandroid.md5
Hit the thanks button if u think the post to be helpful!
Click to expand...
Click to collapse
ems_pilot said:
Have an AT&T Samsung Galaxy S4 (SGH-i337) Have made a couple of backups with CM and they show up in the Backup and Restore when in CM app. The path shows /mnt/shell/emulated/clockworkmod/backup but when I use ES File Explorer or Explorer they are not to be found. I can open /mnt/shell but the shell folder says 'Empty Folder'.
The reason I want to open the backups is to fix the MD5 checksum errors I always get when trying to restore.
It must be something simple but I can't figure it out.
Click to expand...
Click to collapse
Have you granted ES File Explorer Root permission ? Have you looked on both the Internal, and External SD ?
Have looked everywhere but don't know about granting ES File Explorer root permission....... Thanks for the quick reply.
prboy1969 said:
Have you granted ES File Explorer Root permission ? Have you looked on both the Internal, and External SD ?
Click to expand...
Click to collapse
---------- Post added at 11:02 PM ---------- Previous post was at 10:30 PM ----------
Granted Su to ES File Explorer, was able to see my nandroid.md5 files, edited and now restoring backup... Thank you very much for your expert help.
Now I have to figure out how to move my apps to my SD card. Thanks again!
ems_pilot said:
Granted Su to ES File Explorer, was able to see my nandroid.md5 files, edited and now restoring backup... Thank you very much for your expert help.
Now I have to figure out how to move my apps to my SD card. Thanks again!
Click to expand...
Click to collapse
You can move them with Titanium Backup.
TEAM MiK
MikROMs Since 3/13/11
cant access MD5
i installed CWM & made a rom backup, it said "Backup completed" & wiped data & &dalvik cache. now when tried to install custom rom, in recovery mode it doesnt opens ext sd card(where my custom rom is) & also when i try to restore backed up rom it says MD5 mismatch. As a result i am stucked up in recovery mode. now how to access that rom backup? my phone doesnt starts so i cant get it through ES explorer. also backup is in internal sd card so cant open it in computer also
parkourkarthik said:
Hi friends i would like to share the problem that i faced and solved with other's help.
This thread is only for the people who have the md5 mismatch error while restoring nandroid backups. I created this thread since there were no similar questioned thread.
This error comes usually due to renaming the nandroid backup folders.
Try any one of the following fixes to solve this,
1. Use a program editor like notepad++ to open the nandroid.md5 file and remove all lines except the first line which would have some hex values follwed by boot.img.
2. run the following commands in terminal emulator of ur android:
#cd /sdcard/clockworkmod/backup/(name of backup)
#rm nandroid.md5
#md5sum *img > nandroid.md5
Hit the thanks button if u think the post to be helpful!
Click to expand...
Click to collapse
atulbuddy said:
i installed CWM & made a rom backup, it said "Backup completed" & wiped data & &dalvik cache. now when tried to install custom rom, in recovery mode it doesnt opens ext sd card(where my custom rom is) & also when i try to restore backed up rom it says MD5 mismatch. As a result i am stucked up in recovery mode. now how to access that rom backup? my phone doesnt starts so i cant get it through ES explorer. also backup is in internal sd card so cant open it in computer also
Click to expand...
Click to collapse
You can find any other ways to Mount the SD card in recovery, with the help of adb shell or any other methods to access the backup file.
Else with the help of externel sdcard flash any stable ROMs and then try the restore thing.
Else try flashing the stock firmware available for your model.
Hit thanks rather than typing it
Thanks for the info!! Still working in android 4.4. Just saved me, thank you.
hi guys. i tried all your steps but no success. when i try with android emulator i get /system/bin/sh:cd/sdcard..... not found
and i try to edit the file and i install notepad but i get just some symbols inside the file so i have no ideea where the first line ends
I dont have PC or ADB. any other way to fix the problem?
Hi friends i would like to share the problem that i faced and solved with other's help.
This thread is only for the people who have the md5 mismatch error while restoring nandroid backups. I created this thread since there were no similar questioned thread.
This error comes usually due to renaming the nandroid backup folders.
Try any one of the following fixes to solve this,
1. Use a program editor like notepad++ to open the nandroid.md5 file and remove all lines except the first line which would have some hex values follwed by boot.img.
2. run the following commands in terminal emulator of ur android:
#cd /sdcard/clockworkmod/backup/(name of backup)
#rm nandroid.md5
#md5sum *img > nandroid.md5
Hit the thanks button if u think the post to be helpful![/QUOTE]
I dont have PC or ADB. any other way to fix the problem?
Hello Everybody,
I'm new to this forum and I hope posted this in the right section.
I have a Coolpad F1 TD-SCDMA. Today I flashed a custom ROM but I want my original ROM back.
So I wanted to restore the backup I earlier made today. When I am in CWM and choose restore it gives me: MD5 Mismatch!
I went to check for it in the directory but i didn't see any .md5 file.
Here is a guide for a similair problem, but since I am new to this and as he said in the topic: he ported it for One V. I am not sure if it will work.
I hope someone can help me with this.
Thanks in advantage!
HarlemOrange said:
Hello Everybody,
I'm new to this forum and I hope posted this in the right section.
I have a Coolpad F1 TD-SCDMA. Today I flashed a custom ROM but I want my original ROM back.
So I wanted to restore the backup I earlier made today. When I am in CWM and choose restore it gives me: MD5 Mismatch!
I went to check for it in the directory but i didn't see any .md5 file.
Here is a guide for a similair problem, but since I am new to this and as he said in the topic: he ported it for One V. I am not sure if it will work.
I hope someone can help me with this.
Thanks in advantage!
Click to expand...
Click to collapse
Yea, that SHOULD work.
Just tried it when typing in: 'adb shell' in cmd I get: 'error: device not found'.
Drivers are installed I think, I can see the files on my phone of my SD and emulated SD card.
Any suggestions?
Edit: It WILL find my device when turing on Mass Storage (MTP) instead of charging only.
I tried this using MTP.
Code:
# cd /sdcard/clockworkmod/backup/2014-10-08.08.47.17/
# rm nandroid.md5
# md5sum *img > nandroid.md5
Then I went back to CWM to restore the backup but still the MD5 mismatch.
Edit:
I wonder how this MD5 mismatch error even started.
HarlemOrange said:
I tried this using MTP.
Code:
# cd /sdcard/clockworkmod/backup/2014-10-08.08.47.17/
# rm nandroid.md5
# md5sum *img > nandroid.md5
Then I went back to CWM to restore the backup but still the MD5 mismatch.
Edit:
I wonder how this MD5 mismatch error even started.
Click to expand...
Click to collapse
Did you start with adb shell while connected in MTP? Did you look with a file manager to see if it is creating the md5 file? Did you try Method 3 with busybox? As far as what causes it, it's explained in the first post of that thread.
es0tericcha0s said:
Did you start with adb shell while connected in MTP? Did you look with a file manager to see if it is creating the md5 file? Did you try Method 3 with busybox? As far as what causes it, it's explained in the first post of that thread.
Click to expand...
Click to collapse
Thanks for the response. First I started try with charge only. When that didn't work I start with adb shell whil connected in MTP.
Yes, but unfortunatly it isn't. No, did not try method 3 yet.
But I did try this. It is the same method but without adb. But as you can see in the other topic:
HarlemOrange said:
When I try the following command:
Code:
#cd /sdcard/clockworkmod/backup/2014-10-08.08.47.17
I get this:
Code:
No such file or directory
Did it like 3/4 times now and I'm pretty sure I did not make mistakes when typing.
Click to expand...
Click to collapse
Looks like this (third paragraph) is the problem: Not enough space to finish the backup. I will install the sotck rom shortly and try to restore the data.