Root md5 mismatch

[androidninja]

I was wondering what this meant as when i make a nandroid back up and try to restore it says this and wont let me restore my most recent nandroid. Just wondering if im doing something wrong and how to fix it.

 

[Rastaman-FB]

I was wondering what this meant as when i make a nandroid back up and try to restore it says this and wont let me restore my most recent nandroid. Just wondering if im doing something wrong and how to fix it.

its either because youve changed the name or the card is starting to fail and corrupting the backups

 

[androidninja]

its either because youve changed the name or the card is starting to fail and corrupting the backups

What do you mean changed the name??

 

[Paul8944]

Renamed the file...it causes issues with the md5 check and therefore stops it loading

 

[Tyseyh]

if you have renamed it with a space, take the space out and try again.

 

[androidninja]

Im not trying to be a pain guys but i never renamed anything. I have literally no idea how to rename a file. The backups are labeled by dates like 10-9-2011 and so on. I just make backups with my current rom and factory reset/wipe cache and install a different rom. Then when im tired or dont like a certain rom i got back to ntelos stock rom 2.2 and it says md5 mismatch.

 

[Tyseyh]

Im not trying to be a pain guys but i never renamed anything. I have literally no idea how to rename a file. The backups are labeled by dates like 10-9-2011 and so on. I just make backups with my current rom and factory reset/wipe cache and install a different rom. Then when im tired or dont like a certain rom i got back to ntelos stock rom 2.2 and it says md5 mismatch.

oh right, i get ya.
reason we mentioned the renaming is because that is the main reason for MD5 errors.

Here is what SUroot told me to do to remove the current MD5 and make a new one. ( I haven't tried this, but SUroot tried it, said it works, and lets face it, he is a smart man )

Download and open Terminal Emulator from the Market.

"Type:
cd /sdcard/clockworkmod/backup/backupname

And press enter (where backupname is what you renamed the backup to) this takes you to that directory

Type:
rm nandroid.md5

And press enter. This removes the current unworking Md5 file

Type:
md5sum *img > nandroid.md5

And press enter. This generates new Md5

Easy""


if this helps, please go to this link here and thank SUroot. ( Post 13 )
This one here.

 

[SUroot]

It's likely that the backups have corrupted since creation which is what Md5 is designed to detect. That will create new Md5s but that doesn't mean it will restore properly so do so at your own risk

 

[Rastaman-FB]

Im not trying to be a pain guys but i never renamed anything. I have literally no idea how to rename a file. The backups are labeled by dates like 10-9-2011 and so on. I just make backups with my current rom and factory reset/wipe cache and install a different rom. Then when im tired or dont like a certain rom i got back to ntelos stock rom 2.2 and it says md5 mismatch.

i did also say it could be a corrupt sdcard. the files are becoming corrupted

 

[Hadron]

It's likely that the backups have corrupted since creation which is what Md5 is designed to detect. That will create new Md5s but that doesn't mean it will restore properly so do so at your own risk

If he's not already deleted the nandroid.md5 file he could try checking which file is mismatched. Use something like Android File Verifier to check the md5s of the images in the nandroid folder and compare with the codes in nandroid.md5.

Won't help if system.img is mismatched, but if it's just something like recovery.img (what is the purpose of that?) you could use the advanced restore option to selectively restore system, data etc. If data.img is bad you could try restoring the ROM (system.img) without restoring data (wipe first!), then restore apps and data from Ti etc like you would for a new ROM install.

Might work, but take a nandroid first in case! Then verify it (using AFV) and back it up to a computer if it's possible the card us playing up (in fact back all your nandroids up). Only start messing with stuff like the above when you are sure you have a way back if it fails.