[REF][GUIDE]CWM md5 mismatch problem solved

So, many of you probably faced the issue, when you tried to restore your CWM backup, that the recovery says MD5 mistmach, and will do nothing. The problem is now solved, and was solved, so I'm not the one, who made thing possible, I'm just porting this to the V.

So, the problem (in my iterations at least) are based on the /cache/ cannot be mounted error, which is common in the V. For why is that, I simply don't have a clue, but it is present. Because of this, the backup won't be full, and thus, the md5 image won't be made for the recovery, so cannot be recovered as is.

But happily you can make an md5 image from the backup yourself, and thus recover your backup.


There are three ways for you, to make an md5 sum of the img files, the good and the bad one and also the quoted one:

One (the good)

For this, you will need adb, root, and a working android. Yo don't have it? Here you go.

Go to the directory, were you have adb (or have extracted adb.exe, suggested c:\htc\), then plug in your phone (just for charge, no data connection), open terminal (syntax: cmd) then type in:

adb shell

this will get you to the phone's terminal
if you have # at the end of the line, you are good to go, if not, then type su

The syntaxes needed:

cd /sdcard/clockworkmod/backup/{recovery_timestamped_directory} <- this is from your backup, so you need to fill in appropirate data
md5sum *img > nandroid.md5

Click to expand...

Click to collapse

This will make an md5 image with the name that cwm acknowledges.

Two (the bad one)

So, you'we fired your ROM, cannot even boot, but cwm comes in. Than this is for you. There are programs (e.g. total commander) which can make md5 images. So if you have your backup folder, just go into it (sd card reader is preferred). You will see something like this in it:

.android_secure.vfat.tar
boot.img
data.ext4.tar
{nandroid.md5}
recovery.img
system.ext4.tar

Click to expand...

Click to collapse

sidenote:
If you have the nandroid.md5 and you cannot recover, don't try to recover from it!!!
The image itself is corrup, you have no luck, try RUU. (you can recover if you delete the md5 and create a new, but it is not really recommended)

1.
So, there are 2 .img files, highlight them in totalcommander. go to file->create checksum files

2.
tick in md5, then ok

3.
No, you're not done
open the md5 file in text editor, and remove the * 's from before the file names.

4.
Rename the file to nandroid.md5

5.
Now you're done, go to cwm, then recover.

Three (the quoted one)
Also on the 2nd page you will find an alternative solution for the problem which can help you if you have got busybox installed on your device.
The solution resembles the One type of fix, so with quotes here's the one (thanx for Meeshka for it).

Meeshka said:

For those who keep getting "md5sum not found" both in adb and in android terminql on device:
try instead
# busybox md5sum *img > nandroid.md5
worked for me

Click to expand...

Click to collapse

If I helped, don't hesitate to push the Thanks button.

md5 mismatch problem solved by a simple way

I kept getting the md5 mismatch problem no mater what I did, trying many different ways to create and verify the nandroid.md5 file.

In the end, I tumble across a Youtube video saying you only need to delete the old nandroid.md5 file create a blank one with the exact same name (using textedit or whatever method suit you) for it to work. The size of this new nandroid.md5 file should be zero since it's blank. This somehow works for me every time.

Running CWM 5.802 on Pantech Flex with CFIRv4.

Put this in the general android section as it works across most devices. ..

Sent from my One V

Beastben13 said:

in 3. it says to remove the * *'s, but i don't see any, so i was wondering should i leave that be or if im doing something wrong.

Click to expand...

Click to collapse

I have done the thing with a legacy tcmd, so there is a probability, that they have modified the md5sum algorithm, so if you don't se the stars don't panic. (also it should do the trick even with stars in the file, but wanted to be sure at the time I wrote the post)