I have clockwork recovery on my phone and im trying to restore a backup I have and it keeps saying MD5 mismatch. I have searched but havent got any luck, could someone please help me with this problem.
it means the checksum that it does on the backed up info to verify the file is not corrupt, and hasnt been changed, doesnt match what was originally stored.
May have a corrupt backup. Do you Overclock your phone? if so, try undoing the overclock termporarily and see if it restores that way.. if so, you OC'd too much..
Otherwise, may be sol.
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.
When i try to do a nandroid backup, it says, "Oops...something went wrong. Check the Recovery Log."
I did not have a nandroid folder as usual. So i made one titled, "nandroid". Still didn't work. Or is it supposed to be, ".nandroid"? Idk. I'm going to try formatting my sdcard to see if that helps. Any ideas? Thanks
Just reflash your recovery. I've had that happen twice
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.
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.