Hey guys, I'm having a problem restoring my stock Touchwiz backup. Every time I try to restore it I get the md5 mismatch error. I'm using CWM recovery 6.0.4.5 from this thread. All my other backups work just fine. Now I did move my backup from my phone to my computer to save room on my SD card and moved it back when I wanted to restore it. I wonder if this could have changed the md5? Also the backup's name has no spaces, wish it was that simple to fix lol. I've seen a couple other threads to fix the md5 mismatch issue but wanted to see if someone who's experienced this could point me into the right direction. Thank you.
Related
Hello all, I have recently had problems restoring my nandroid backups.
I think it's because of Clockwork, but I'm not sure.
I get this message after checking for MD5 sums..
error while flashing boot image! /tmp/recovery.log was copied to /sdcard/cloclworkmod/recovery.log please open ROM manager to report the issue.
Any ideas on how I can use my nandroid back ups? I want to go back to FreshEvo for a while.
Were you using clockwork when you created the backups? I've had problems when I've made a backup under one recovery, then updated the recovery, then couldnt get my backups to work.
For some backups yes, but not the one I'm trying to go back to.
I tried restoring with nandroid and clockwork and both give me the same error.
I am using amon-ra so this might not help you.
I was not able to restore even after turning off the phone. After several tries I removed the battery and I was able to restore. Just turning it off did not do the trick. Really odd.
Sent from my PC36100 using XDA App
Hi guys, I want to run a nandroid restore with my leedroid backup, but I'm getting:
Error : run 'nandroid-mobile.sh' via adb!
I remember I had this problem before but I forgot how I fixed it.
Edit: the system.img md5 is corrupted, any way to fix it? Or the backup is done for?
Guess that backup is done for if it something to do with md5. Md5 is a pain if it messes up. It messes up for me so I don't bother really. You can try searching for md5 fixes but I seriously doubt it.
Did you have enough battery? Nandroids don't work if its below a certain percentage of battery.
I recall having that error as well, then I plugged my phone in for a few minutes before I was able to restore my nandroid.
hi
so i have installed cm9 alpha 7 and made a nandroid backup before through with the help of cwm recovery. when i tried to revert back through the same menu it gave md5 mismatch error, i have seen on other sections of this forums and they do have fixes for htc one and hd2... any fixes for wildfire s ??
let me know if it wasnt clear enough !!
thanks
just writing it here so that someone may get help from this post
well i have gone through some forums and the adb shell method written their didint worked out
i figured out i have renamed the folders from the cwm restore format to my own, so i reverted them back and the phone is restoring now
hit thanks if it helped you
Did you make a backup with a different CWM and try to restore it with a another version? Let's say you did a backup with version 3.X.X and then you tried to restore it with version 5.X.X, did you do that? If so revert back to your original CWM that you made a back up with. Also did you rename the backup file? That could cause a MD5 mismatch. Hope this helps
well as mentioned in second post, i have resolved the problem ... cwm recovery versions are same but i did "renamed" the folder. i reverted to original name and it restored well.
The problem is that cwm does not allow spaces in the name of the backup file....thus the following error arises.
Sent from my GT-S5570 using xda app-developers app
Hi guys
I'm having g some weird issues I have a gs3 from bell. I rooted it and been flashing all kinds of Roms and never having any issues going back to restoring stable Roms until I decided to try twrp recovery but I noticed that I couldn't restore anything backed up by cwm so I flashed cwm though Rom manager and since then whenever I try to backup a Rom it finishes then when I try to restore them they say md5 mismatch. So after a lot of research I managed to notice that cwm isn't making any nandroid md5 files.
So my question is have I flashed a bad version of cwm through Rom manager or may I have just screwed my phones files somehow I was thinking of uprooting my phone and rerooting it but I don't know if that will fix this. Please help
*deleted*
Good luck
Just so u know i've read through that 3 times already I don't have that issue ... I dOnt have a nandroid md5 like showing up in any of my backups so thanks for nothing if you would have read my post you would have understood That already
solved***** unrooted......rerooted..........backups and restors working fine..........my guess. rom manger`s update of cwm got messed up no more rom manager for me ;p
DLM2583 said:
solved***** unrooted......rerooted..........backups and restors working fine..........my guess. rom manger`s update of cwm got messed up no more rom manager for me ;p
Click to expand...
Click to collapse
Hi, I am still having the same problem as you, and I bought Cwm touch from rom manager and i created a backup and when i restore it it says md5 mistmatch.. So did you get a different older version of cwm? How did you end up using the backup that you couldn't open? Thanks for your help
Hi,
I am having problems with airplane mode being stuck so I´m trying to go back to stock as a last resort before laying the phone to rest in a drawer lol.
So I downloaded a Nandroid backup from here http://forum.xda-developers.com/showthread.php?t=1975140 because I think RUU is no longer an option? First question, does the file I downloaded have to be flashed as a zip in recovery or do I need to put it into a backup folder and flash it as a restore? I have tried both, the zip flash method gives an error and the restore method gives a md5 mismatch.
Also I should mention, I don't know which recovery was used to make these Nandroids so I tried TWRP and CWM both didn't work.
I was going to try this post http://forum.xda-developers.com/showthread.php?t=714114 but I thought I better ask before bricking the phone. Although after two weeks of frustration bricking the phone seems like a good option lol.
Any help would be much appreciated, Thanks.