Database Info

[Solution] MD5 mismatch error

Few days ago I faced MD5 mismatch error while restoring my backup after messed with my phone. But due to this error I couldn't restore backup. I asked many people but people said that I should now flash sock firmware which was really a headache for me.
Anyway I searched alot on xda & I found very easy solution.
It don't require pc or adb shell etc. It only requires rooted phone with Terminal Emulator app
STEP 1: Open Terminal Emulator
Step 2: Use the following commands. (DON'T FORGET TO REPLACE "2012-01-01.10.09.36" WITH YOUR OWN BACKUP FOLDER NAME WHICH WILL BE PRESENT IN folder /clockworkmod/backup/)
Code:
su
#mount -o remount rw /sdcard
#cd /sdcard/clockworkmod/backup/2012-01-01.10.09.36
#rm nandroid.md5
#md5sum *img > nandroid.md5
STEP 3: (This will create a new "nandroid.md5" file without ANY "md5 mismatch" errors )
Reboot your phone and enter Recovery mode & then restore.
I hope it will help you in future
ENJOY...
IMP NOTE :- Many times people change backup folder name which can create this error. So be sure that you have not changed your backup folder name & also be sure that there is no space in backup folder path.
Credit goes to UsmanJ member. I have just shared with you guys with more good explanation.
Original thread HERE
Click to expand...
Click to collapse

No need these at all you need "root toolbox". and ut works perfectly by the way thanks for sharung this way too
Tapatalk 2 ile GT-I9003 cihazımdan gönderildi

If you do this you can't be sure that your backup isn't broken. md5 needs exactly for checking this. Yes, you cheated the check system, but are you sure that your backup integrity is fine?

This problem is mainly due to folder name change. If you don't change folder name you shouldn't be having this problem.

silentvisitor said:
This problem is mainly due to folder name change. If you don't change folder name you shouldn't be having this problem.
Click to expand...
Click to collapse
Ya but sometimes we have to face this problem even if we dont change folder name like how it was happened in my case few days ago.

Well, I think this is no hint you should use. When creating a new backup md5 hashsums are calculated for each file. If you now want to restore it these hashsums are calculated again and compared to the previous ones. Only if the data is the same as before , in other words your backup hasn't been damaged, the checksums match. You may have had some luck that the error happened in a file that does not get used very often but in general you do not want to do that, just imagine your kernel backup is broken!
Sent from my GT-I9003 using XDA

Thanks, worked just fine for me.:good:

The error is not only because of changing the name of folder, as vishal says md5 mismatch can occur.
I even encountered the following problem with nandroid backup.
stock gb,xxkpu nandroid not compatible over cm9 or miui.
Or miui/CNET not compatible over stock rooted ROM.
I'm not sure of the reason why this error occurs while reporting the nandroid backup, but according to my limited knowledge of Android, I suppose either ext4 partition is not compatible over rfs of stock and vice versa or, out might be a kernel clash.
To be true, I didn't even try to search much about the issue as I'm mostly free and take the pain of customizing three new firmware as power my preference and reinstalling the app
Sent from my GT-I9003 using xda premium

If anyone is sure of the error and it's solution, the answer is most welcome.
P.s. while restoring out doesn't say md5 mismatch (I've also come across this though), the error I stated cannot restore the boot image atty the first place.
Sent from my GT-I9003 using xda premium

@ Iambalvindar
You are right bro. There can be number of reasons about this md5 mismatch error. Actually the solutuion which I have provided is just an option to correct error If error is due to other reason such corrupted backup then obviously the solution given in my thread will not be applicable.

The first two commands ('su' and 'mount') are not necessary because:
You don't need root permissions to edit stuff in /sdcard
/sdcard is always mounted as RW (that's what the second command does.)
EDIT:
I've just remembered that if you don't have busybox installed you don't have the 'md5sum' command avaible for the user.
However our CF-root kernels come with an inbuilt busybox, but it can't be used as normal user, because if I remember correctly all the symlinks are in /sbin, where the user has no access. So, probably, you need to do this as root (= type the 'su' command as in the OP).
Anyway, nandroid.md5 is the last thing made during a backup. That means if you don't have enough space for the backup and it stops, this file is not created. So, when you go to restore that backup, you have the mismatch error. In this case, if you create the nandroid.md5 as vishal wrote, you'll have a usable and damaged backup. So, before doing this, check if nandroid.md5 is there or, when you run "rm nandroid.md5", make sure the output is not "No such file or directory", because it means that most likely the backup is not complete.
All of these to say: be careful and do this if necessary (unless you know what you are doing of course).
A suggestion:
In this situation you can do an "advanced restore" and restore only /data and /datadata if you are using the same ROM you used for the backup (maybe a slightly different ROM is good too). The only things not restored are the mods you applied and system apps, but for the mods, simply reflash them, for the system apps, well, they are always the same. All the apps installed through the market are in /data.
Maybe this will cause bootloops, but in this case you can simply reboot in recovery and do a data wipe/factory reset. This will let you boot without the need of a reflash. You have of course to reinstal all your apps etc, but it's better than starting from scratch.
Or, even better, do a backup before the restore of /data and /datadata, so that in case of problems you can always restore everything.
EDIT 2:
I think you can do this even when you change ROM, as long as it's a stock ROM. That's because stock ROMs are intended to be flashed over another stock ROM and they are made in a way that you don't need to wipe your /data partition. When you use kies to upgrade, you don't loose anything. Restoring /data and /datadata should have the same effect (it's better to wipe the dalvik-cache after this).

@vishal: I'm not referring to corrupted backups. Sometimes later, even working backups fail to be restored after some ROM and kernel change.
Sent from my GT-I9003 using xda premium

iAmBalvinder said:
@vishal: I'm not referring to corrupted backups. Sometimes later, even working backups fail to be restored after some ROM and kernel change.
Sent from my GT-I9003 using xda premium
Click to expand...
Click to collapse
Ya its because different kernels have different cwm version & also different kernels creat different md5 code as per backup.

iAmBalvinder said:
@vishal: I'm not referring to corrupted backups. Sometimes later, even working backups fail to be restored after some ROM and kernel change.
Sent from my GT-I9003 using xda premium
Click to expand...
Click to collapse
I think you can do it, nandroid backups are the exact copy of the ROM you are running (the radio is not backed up).
The problem is that maybe you did a backup of Gingerbread using amit's CWM. His CWM is able to backup the kernel (normalboot.img), but he disabled this feature because he couldn't test it, so he thought it would be safer not to enable it. UC team however enabled it (that's what I can see from their recovery.fstab).
If you used amit's recovery to backup the ROM, when you restored it from CyanogenMod you didn't restore the kernel. So, when you turned the phone on, you tried to boot a stock ROM with a CM kernel.
Maybe if you flash a stock kernel after the restore with odin it will boot.
And if you tried to restore a CM backup (so with the kernel backed up) with amit's kernel, you didn't restore the kernel amit's recovery ignores it, so you tried to boot CM with a stock ROM kernel.
Maybe backups made from different CWM versions are not compatible, but I think Koush is trying to avoid this, but I'm not sure.
Another problem could be that CM is not yet finished and the continous changes in recovery cause new bugs that could affect the way backups are done (it recently happened).
Maybe I'm saying stupid things, but that's what I know. I'm not so interested in backups and restores, I rarely use them, so I've never tried to study well enough how they work etc. Correct me if I wrote something stupid.
Anyway, I'm sure that the md5sum error has nothing to do with the kernel you used to make the backup.
Every file has a unique md5 hash, it doesn't matter if you calculate it with your phone, with your computer or with your fridge (if you can ), the result is always the same. What CWM does before starting a restore is to re-calculate the md5 of each file inside /sdcard/clockwrockmod/backup/XXXXX/ and to compare them with the ones stored in /sdcard/clockwrockmod/backup/XXXXX/nandroid.md5 when you made the backup (open this file with a text editor and see). If they are all equal, it means the backup is not corrupted, so it's safe to start the restore.
I think you could even restore a backup of another phone (maybe there are some other check here and there to prevent this), but of course don't try it .

loSconosciuto said:
I think you can do it, nandroid backups are the exact copy of the ROM you are running (the radio is not backed up).
The problem is that maybe you did a backup of Gingerbread using amit's CWM. His CWM is able to backup the kernel (normalboot.img), but he disabled this feature because he couldn't test it, so he thought it would be safer not to enable it. UC team however enabled it (that's what I can see from their recovery.fstab).
If you used amit's recovery to backup the ROM, when you restored it from CyanogenMod you didn't restore the kernel. So, when you turned the phone on, you tried to boot a stock ROM with a CM kernel.
Maybe if you flash a stock kernel after the restore with odin it will boot.
And if you tried to restore from a CM backup (so with the kernel backed up) with amit's kernel, you didn't restore the kernel amit's recovery ignores it, so you tried to boot CM with a stock ROM kernel.
Maybe backups made from different CWM versions are not compatible, but I think Koush is trying to avoid this, but I'm not sure.
Another problem could be that CM is not yet finished and the continous changes in recovery cause new bugs that could affect the way backup are done (it recently happened).
Maybe I'm saying stupid things, but that's what I know. I'm not so interested in backups and restores, I rarely use them, so I've never tried to study well enough how they work etc. Correct me if I wrote something stupid.
Anyway, I'm sure that the md5sum error has nothing to do with the kernel you used to make the backup.
Every file has a unique md5 hash, it doesn't matter if you calculate it with your phone, with your computer or with your fridge (if you can ), the result is always the same. What CWM does before starting a restore is to re-calculate the md5 of each file inside /sdcard/clockwrockmod/backup/XXXXX/ and to compare them with the ones stored in /sdcard/clockwrockmod/backup/XXXXX/nandroid.md5 when you made the backup (open this file with a text editor and see). If they are all equal, it means the backup is not corrupted, so it's safe to start the restore.
I think you could even restore a backup of another phone (maybe there are some other check here and there to prevent this), but of course don't try it .
Click to expand...
Click to collapse
Cool, thx for the info. Nv knew the difference between the kernels
Sent from my GT-I9003 using xda app-developers app

loSconosciuto said:
I think you can do it, nandroid backups are the exact copy of the ROM you are running (the radio is not backed up).
The problem is that maybe you did a backup of Gingerbread using amit's CWM. His CWM is able to backup the kernel (normalboot.img), but he disabled this feature because he couldn't test it, so he thought it would be safer not to enable it. UC team however enabled it (that's what I can see from their recovery.fstab).
If you used amit's recovery to backup the ROM, when you restored it from CyanogenMod you didn't restore the kernel. So, when you turned the phone on, you tried to boot a stock ROM with a CM kernel.
Maybe if you flash a stock kernel after the restore with odin it will boot.
And if you tried to restore a CM backup (so with the kernel backed up) with amit's kernel, you didn't restore the kernel amit's recovery ignores it, so you tried to boot CM with a stock ROM kernel.
Maybe backups made from different CWM versions are not compatible, but I think Koush is trying to avoid this, but I'm not sure.
Another problem could be that CM is not yet finished and the continous changes in recovery cause new bugs that could affect the way backups are done (it recently happened).
Maybe I'm saying stupid things, but that's what I know. I'm not so interested in backups and restores, I rarely use them, so I've never tried to study well enough how they work etc. Correct me if I wrote something stupid.
Anyway, I'm sure that the md5sum error has nothing to do with the kernel you used to make the backup.
Every file has a unique md5 hash, it doesn't matter if you calculate it with your phone, with your computer or with your fridge (if you can ), the result is always the same. What CWM does before starting a restore is to re-calculate the md5 of each file inside /sdcard/clockwrockmod/backup/XXXXX/ and to compare them with the ones stored in /sdcard/clockwrockmod/backup/XXXXX/nandroid.md5 when you made the backup (open this file with a text editor and see). If they are all equal, it means the backup is not corrupted, so it's safe to start the restore.
I think you could even restore a backup of another phone (maybe there are some other check here and there to prevent this), but of course don't try it .
Click to expand...
Click to collapse
Yeah, most probably be that was the issue... Kernels needed to be changed.
Thanks
And I already saw that my backup was not corrupted with md5 check.
Moreover, I also don't use nandroid much, I always configure new ROM I try, from the scratch.
It's just that I needed to use USB storage urgently, which sadly doesn't work on any ics based ROM. So tried to restore the backup. Alas !
Had to flash again from scratch to get to stock gb, as I didn't have any gb.zip in sd card or computer.
Sent from my GT-I9003 using xda premium

i am not able to restore my backup due to mismatch md5
vishal24387 said:
Few days ago I faced MD5 mismatch error while restoring my backup after messed with my phone. But due to this error I couldn't restore backup. I asked many people but people said that I should now flash sock firmware which was really a headache for me.
Anyway I searched alot on xda & I found very easy solution.
It don't require pc or adb shell etc. It only requires rooted phone with Terminal Emulator app
STEP 1: Open Terminal Emulator
Step 2: Use the following commands. (DON'T FORGET TO REPLACE "2012-01-01.10.09.36" WITH YOUR OWN BACKUP FOLDER NAME WHICH WILL BE PRESENT IN folder /clockworkmod/backup/)
Code:
su
#mount -o remount rw /sdcard
#cd /sdcard/clockworkmod/backup/2012-01-01.10.09.36
#rm nandroid.md5
#md5sum *img > nandroid.md5
STEP 3: (This will create a new "nandroid.md5" file without ANY "md5 mismatch" errors )
Reboot your phone and enter Recovery mode & then restore.
I hope it will help you in future
ENJOY...
IMP NOTE :- Many times people change backup folder name which can create this error. So be sure that you have not changed your backup folder name & also be sure that there is no space in backup folder path.
Click to expand...
Click to collapse
i was using another bootloader and another cwm

Vishal, can you summarize every thing and update first post.
According to my understanding,
1. Do not change backup folder name.
2. Do not restore backup using different recovery than the one used, i.e. Use gb recovery to restore gb Rom, cm7 recovery to restore cm7 Rom and so on.
These are the main cause of md5 error, else better to assume the backup is corrupted.
Recalclating the md5 and restoring could have adverse effect on the system.
Sent from my LT28h using xda premium

ganeshbiyer said:
Vishal, can you summarize every thing and update first post.
According to my understanding,
1. Do not change backup folder name.
2. Do not restore backup using different recovery than the one used, i.e. Use gb recovery to restore gb Rom, cm7 recovery to restore cm7 Rom and so on.
These are the main cause of md5 error, else better to assume the backup is corrupted.
Recalclating the md5 and restoring could have adverse effect on the system.
Sent from my LT28h using xda premium
Click to expand...
Click to collapse
ok buddy I will update information in few minutes
I am still waiting for ur test kernel with modules inbulit in it.

I was on the same issue as all people with MD5 failure, then I rename my backup name with a short name with no space or blank and the it run like a charme !.
Hope it could help.

[Q] TWRP vs CWM

Im curious as to which recovery is working the best with the Galaxy Note 10.1. Im not asking which is the best, but I see darkman has come out with a touch version of cwm and I have the latest TWRP...Only issue i have is that it doesnt see my cwm backups....I havent had any issues with it yet though...Im just curious thats all

I always preferred cwm.. it is more stable.. use to love with twrp when I had asus tf101 but sometimes I couldnt see my internal sd card and sometimes I couldnt mount system.. but just use what works for you..
Sent from my GT-N8013 using XDA Premium HD app

txtmikhail said:
I always preferred cwm.. it is more stable.. use to love with twrp when I had asus tf101 but sometimes I couldnt see my internal sd card and sometimes I couldnt mount system.. but just use what works for you..
Sent from my GT-N8013 using XDA Premium HD app
Click to expand...
Click to collapse
Thanks for the input.... I do have to constantly tap the external sd option because it takes me back to the main screen. Im assuming its a sensitivity issue

txtmikhail said:
I always preferred cwm.. it is more stable.. use to love with twrp when I had asus tf101 but sometimes I couldnt see my internal sd card and sometimes I couldnt mount system.. but just use what works for you..
Sent from my GT-N8013 using XDA Premium HD app
Click to expand...
Click to collapse
Agreed. I've found CWM to be very stable. I loved to move to the touch version, though you have to be careful sometimes about accidentally touching an unwanted option. But since a confirmation menu comes up for each option that makes changes, you can easily correct it.

I have used CWM on all my devices and have worked without an itch so prefer CWM
Tried install TWRP on my device once it refused to install contacted the developers did not get the response so ditched it.

Twerp don't seem to get on with note .
But i would say their is very little difference between using TWRP or CWM for most users .
I use TWRP on SGS3 and CWM on Note .
jje

I moved to TWRP awhile ago for my phones and currently use it on my Note. As far as stability goes CWM is much more stable, though I have it tried the touch version(thinking of checking it out though.) TWRP is a little wonky sometimes,but I think that's a sensitivity issue.
As another poster already said, there's no real big difference between the two and they both get the job done.

My big problem with CWM is the backups. Maybe I didn't spend enough time with it or missed an option somewhere. But since they moved to the BLOB model for backups I found it impossible to delete an old backup. I like to do backups often, but I usually only want to keep 2 iterations due to the space they take up. With TWRP it's easy, each backup has it's own folder. Want to delete one, just delete the whole folder.
If someone can tell me how to manage backups properly in CWM I'd be glad to switch back.

midas69 said:
My big problem with CWM is the backups. Maybe I didn't spend enough time with it or missed an option somewhere. But since they moved to the BLOB model for backups I found it impossible to delete an old backup. I like to do backups often, but I usually only want to keep 2 iterations due to the space they take up. With TWRP it's easy, each backup has it's own folder. Want to delete one, just delete the whole folder.
If someone can tell me how to manage backups properly in CWM I'd be glad to switch back.
Click to expand...
Click to collapse
That's one of the reasons I stay with TWRP on my Note despite the super sensitive touch. In all it's wonkiness I've just become more of a fan due to the ease of the touch UI and the ability to just delete the backup folder.

insanecrane said:
That's one of the reasons I stay with TWRP on my Note despite the super sensitive touch. In all it's wonkiness I've just become more of a fan due to the ease of the touch UI and the ability to just delete the backup folder.
Click to expand...
Click to collapse
same thinking for me too..

midas69 said:
My big problem with CWM is the backups. Maybe I didn't spend enough time with it or missed an option somewhere. But since they moved to the BLOB model for backups I found it impossible to delete an old backup. I like to do backups often, but I usually only want to keep 2 iterations due to the space they take up. With TWRP it's easy, each backup has it's own folder. Want to delete one, just delete the whole folder.
If someone can tell me how to manage backups properly in CWM I'd be glad to switch back.
Click to expand...
Click to collapse
Easiest way I've found to manage backups with CWM is to use ROM Manager. It's integrated with CWM such that in the app you ask it to do a backup, you name the backup anything you want, then it automatically reboots into recovery and does it. ROM Manager also allows you to download your backups to you computer via WiFi, and has an easy option to delete backups. Further, CWM has the option to restore data only from a backup for easily getting settings back when doing a ROM upgrade. Geez I'm more sold on CWM than I thought. I almost sound likes a salesperson haha.

glopact said:
Geez I'm more sold on CWM than I thought. I almost sound likes a salesperson haha.
Click to expand...
Click to collapse
Don't apologize, you provided good information. On my HP Touchpad I used TWRP exclusively because it integrated with Goo Manager. But I really don't plan to use anything other than Mobile Odin to flash anything so not much reason to keep it. I may switch back to CWM and try the ROM Manager interface for the backups.
EDIT:
Well that didn't work well at all. Installed and tried to do a backup. Told me (obviously) that I needed CWM installed. Said there wasn't an official version for it so it then asked me if I already had one installed. I answered yes. It then asked if I had version 2 or version 3. But what I have installed has a version number of 6 something. Oh well, back to TWRP I guess.

I thought we could manager the CWM backup from a file manager I have been doing that on my optimus 2x never did it on note though

samir_a said:
I thought we could manager the CWM backup from a file manager I have been doing that on my optimus 2x never did it on note though
Click to expand...
Click to collapse
With older versions I was able to do that. But this newer version I have installed doesn't really work that way. It creates 2 folders for a backup. One has the backup name with just a small file inside. The other folder is called BLOBS. In that fold are multiple other folders that are alphabetical, I assume by file name. The problem is, when you create a 2nd backup, it used the same BLOBS folder. So there is no way to just delete one folder to delete a complete backup.

yes I remember that when I was trying to delete CWM backup files and did not find them. Thanks for the update
---------- Post added at 09:00 PM ---------- Previous post was at 08:59 PM ----------
A noob method try to sort by date/time should tell you which files were updated during your last backup and will give you an idea how the update works. Let me do some R&D on it

I just don't want to have to manually delete files from 20+ directories when, with TWRP, I can just delete one folder.

samir_a said:
I thought we could manage the CWM backup from a file manager ...?
Click to expand...
Click to collapse
midas69 said:
With older versions I was able to do that. But this newer version I have installed doesn't really work that way. It creates 2 folders for a backup. One has the backup name with just a small file inside. The other folder is called BLOBS ...
Click to expand...
Click to collapse
Change the backup format to "tar" and you'll get the old directory structure back.

[Q] Error while restoring nandroid of old GS3 to new replacement GS3

I got a replacement GS3 from Verizon because my current one had a charge port issue. I rooted and am using CWM 6.0.2.3 and get "error while restoring /system" when I try tp restore the nandroid of my old phone to the new one. How do I fix this?

Did you change the name of the nandroid at all? It's also possible that the backup you made contained individual phone information specific to your old phone...I seem to remember a thread before that mentioned it wasn't a good idea to move a nandroid to a new Samsung phone.
Edit: I found the thread shortly after hitting submit - http://forum.xda-developers.com/showthread.php?t=1795031

laurasaurisrex said:
Did you change the name of the nandroid at all? It's also possible that the backup you made contained individual phone information specific to your old phone...I seem to remember a thread before that mentioned it wasn't a good idea to move a nandroid to a new Samsung phone.
Click to expand...
Click to collapse
No I didnt't change anything. Anyway I can fix this?

laurasaurisrex said:
Did you change the name of the nandroid at all? It's also possible that the backup you made contained individual phone information specific to your old phone...I seem to remember a thread before that mentioned it wasn't a good idea to move a nandroid to a new Samsung phone.
Edit: I found the thread shortly after hitting submit - http://forum.xda-developers.com/showthread.php?t=1795031
Click to expand...
Click to collapse
If anyone has a way I can workaround that, please help! I don't want to setup my phone all over again!

droxide said:
If anyone has a way I can workaround that, please help! I don't want to setup my phone all over again!
Click to expand...
Click to collapse
there are a couple of apps where you can just extract the nandroid apps on the play store, but if you want the full restore, the file is probably corrupted.

dragon1357 said:
there are a couple of apps where you can just extract the nandroid apps on the play store, but if you want the full restore, the file is probably corrupted.
Click to expand...
Click to collapse
Yeah I used to use titanium backup but my phone is very customized, CM10, diff kernel, and a very highly customized home screen so I'd rather restore the nandroid if there is some kind of workaround. I also want all my data, texts, etc. without using titanium backup. When I used ti backup in the past, I had a bunch of different issues restoring apps and data, force closes, etc.

http://forum.xda-developers.com/showthread.php?t=1949020
I followed the directions in the last post of that thread.. I made a backup of the new phone, moved the old nandroid from old phone to the twrp back up folder in my new phone. I copied the new backup name and deleted the new backup. i pasted the name into the old back up, I tried to restore and i get an error "no partitions selected for restore. Is it because Im using twrp and I made the old backup with CWM?
Someone help!

droxide said:
http://forum.xda-developers.com/showthread.php?t=1949020
I followed the directions in the last post of that thread.. I made a backup of the new phone, moved the old nandroid from old phone to the twrp back up folder in my new phone. I copied the new backup name and deleted the new backup. i pasted the name into the old back up, I tried to restore and i get an error "no partitions selected for restore. Is it because Im using twrp and I made the old backup with CWM?
Someone help!
Click to expand...
Click to collapse
That could be it. They back up with different formats. Cwm uses the blob folder twrp does not.
Sent from my SCH-I605 (AKA NOTE 2)

kintwofan said:
That could be it. They back up with different formats. Cwm uses the blob folder twrp does not.
Sent from my SCH-I605 (AKA NOTE 2)
Click to expand...
Click to collapse
Ok so how can I switch from TWRP to CWM without resetting everything?

droxide said:
Ok so how can I switch from TWRP to CWM without resetting everything?
Click to expand...
Click to collapse
Ya, you should be able to flash it through odin no problem
Sent from my SCH-I535

droxide said:
Ok so how can I switch from TWRP to CWM without resetting everything?
Click to expand...
Click to collapse
You can just use ez recovery from the play store
Sent from my SCH-I605 (AKA NOTE 2)

[Q] Newer CWM, md5 mismatch won't allow recovery.

I don't know if it has to do with having installed a newer version of ClockworkMod Recovery (6.0.3.1), but when I go to restore a previous backup, I get "md5 mismatch!" and no recovery is done.
Things that my non-developer brain can think of that might be relevant:
I may have changed the name of the folder for the recovery (I didn't think this mattered)
I am trying to go from CyanogenMod M5 to a recovery of an M2 (don't think this should matter).
The recovery was made using a previous version of ClockworkMod Recovery (an earlier, but 2013, version)
The recovery folder was stored on my computer and I put it on my phone using USB on-the-go (I have tried this twice to make sure one wasn't corrupted or whatever).
Thanks for any pointers. Do have have to install an older version of ClockworkMod Recovery or is there something simpler I could do? Thanks! :good:

LudicrousPeed said:
I don't know if it has to do with having installed a newer version of ClockworkMod Recovery (6.0.3.1), but when I go to restore a previous backup, I get "md5 mismatch!" and no recovery is done.
Things that my non-developer brain can think of that might be relevant:
I may have changed the name of the folder for the recovery (I didn't think this mattered)
I am trying to go from CyanogenMod M5 to a recovery of an M2 (don't think this should matter).
The recovery was made using a previous version of ClockworkMod Recovery (an earlier, but 2013, version)
The recovery folder was stored on my computer and I put it on my phone using USB on-the-go (I have tried this twice to make sure one wasn't corrupted or whatever).
Thanks for any pointers. Do have have to install an older version of ClockworkMod Recovery or is there something simpler I could do? Thanks! :good:
Click to expand...
Click to collapse
Changing the name for CWM backups will cause md5 mismatches. If you did this, you should switch and use TWRP which allows native nandroid renaming. Delete your CWM backups and stick to TWRP. It could also be an issue between CWM backups over different CWM versions however if you renamed your backups and each of those renamed backups failed except the ones you left alone then you found your issue.

SlimSnoopOS said:
Changing the name for CWM backups will cause md5 mismatches. If you did this, you should switch and use TWRP which allows native nandroid renaming. Delete your CWM backups and stick to TWRP. It could also be an issue between CWM backups over different CWM versions however if you renamed your backups and each of those renamed backups failed except the ones you left alone then you found your issue.
Click to expand...
Click to collapse
Thanks for the insight. Seems like I should just be able to change the folder name back to what it was named by default, if I can make sure it is correct. Do you think that's worth trying or is it deeper than that? I'll use TWRP from now on since it seems to be more robust (CWM was just the recommended recovery from Cyanogenmod)

LudicrousPeed said:
Thanks for the insight. Seems like I should just be able to change the folder name back to what it was named by default, if I can make sure it is correct. Do you think that's worth trying or is it deeper than that? I'll use TWRP from now on since it seems to be more robust (CWM was just the recommended recovery from Cyanogenmod)
Click to expand...
Click to collapse
Depends on how much you value those nandroids. I only keep two on my phone so it's no thing for me to delete my backups entirely. You can rename them to their original names and your issue should go away.
Sent from my SCH-I535 using Tapatalk 4 Beta

Make sure the name of the backup folder doesn't have any spaces. When I renamed backups and had a space in the name I would get that same "md5 mismatch!" error.

Thanks! So renaming the backup to what it was originally allowed the backup to attempt to restore, but data could not be restored. Attempting to boot it resulted in nor getting past the boot animation. I wonder if it was because I didn't have enough space left on my phone or of it had to so with the newer firmware I installed. Or something else.
Slightly of topic at this point but not really. Any ideas why data could not be restored?
Sent from my SCH-I535 using Tapatalk 2

LudicrousPeed said:
Thanks! So renaming the backup to what it was originally allowed the backup to attempt to restore, but data could not be restored. Attempting to boot it resulted in nor getting past the boot animation. I wonder if it was because I didn't have enough space left on my phone or of it had to so with the newer firmware I installed. Or something else.
Slightly of topic at this point but not really. Any ideas why data could not be restored?
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I had a similar issue about a year ago. I resolved it by generating a new md5, but I don't recall what method I used. Do a search for that.

{help} making a flashable zip of my phone

Like the title says, I'm trying to figure out how to make a flashable zip of my phone with all my installed apps, app data and settings included.
I already have a nandroid backup and I already use titanium to back up my apps and app data, but I want to have a flashable zip as another backup incase all else fails.
I also want to be able to flash the zip on my wife's N5.
Can someone kindly walk me through the process or point me in the direction of a good walk through?
Thanks in advance.
Sent from my SM-N920T using XDA-Developers mobile app

re: zip file rom backups
tamelion1117 said:
Like the title says, I'm trying to figure out how to make a flashable zip of my phone with all my installed apps, app data and settings included.
I already have a nandroid backup and I already use titanium to back up my apps and app data, but I want to have a flashable zip as another backup incase all else fails.
I also want to be able to flash the zip on my wife's N5.
Can someone kindly walk me through the process or point me in the direction of a good walk through?
Thanks in advance.
Sent from my SM-N920T using XDA-Developers mobile app
Click to expand...
Click to collapse
Don't you think that if it was something feasible and worthwhile to do many of the developers would have
created something like that already after all these years?
The developers have already developed an excellent way of backing up and restoring android phones using
TWRP and CWM nandroid backup and restore functions in their custom recovery mode which everyone uses.
If you don't trust nandroid backups why not do a simple test and make some nandroid backups and restore each
of them one at a time to see if you can find any kind of issues, problems or difficulties with your phone after you
have restored each of the backups one at a time.
Have you ever created a nandroid backup which did not restore properly or know of anyone who did?
Also why not do a bit of research here in these xda forums and threads to see if you can find any posts here by
people who are having any problems, issues or difficulties using or restoring their nandroid backups.
Good luck,
Have a great day!

Misterjunky said:
Don't you think that if it was something feasible and worthwhile to do many of the developers would have
created something like that already after all these years?
The developers have already developed an excellent way of backing up and restoring android phones using
TWRP and CWM nandroid backup and restore functions in their custom recovery mode.
If you don't trust nandroid backups why not make two of them as a test and restore each of them one at a time
and see if you can find any kind of issues or problems with your phone after restoring each of the backups.
Have you ever created a nandroid backup which did not restore properly or know of anyone who did?
Also why not do a bit of reading here in these xda forums and threads to see if you can find any people here
who are having any problems or issues with their nandroid backups after they have restored them.
Good luck,
Have a great day!
Click to expand...
Click to collapse
I trust in my nandroid backups. The main reason I want to create a flashable zip with everything backed up in it is to have the ability to create a duplicate image of my phone and flash it on my wife's.
Sent from my Samsung Galaxy Note 5 running Darthstalker v8 and Xposed 85.1

tamelion1117 said:
Like the title says, I'm trying to figure out how to make a flashable zip of my phone with all my installed apps, app data and settings included.
I already have a nandroid backup and I already use titanium to back up my apps and app data, but I want to have a flashable zip as another backup incase all else fails.
I also want to be able to flash the zip on my wife's N5.
Can someone kindly walk me through the process or point me in the direction of a good walk through?
Thanks in advance.
Sent from my SM-N920T using XDA-Developers mobile app
Click to expand...
Click to collapse
well if you really want to learn
here's a simple example of how you can build yourself a rom
http://forum.xda-developers.com/honor-5x/development/custom-rom-starter-template-honor-5x-t3328809
keep in mind you can't use his updater-script and you need to adjust some of the commands to match the note 5
but for the most part all roms are the same
you need:
META-INF <Folder>
boot.img
system.apps.tar.gz
system.therest.tar.gz
and optionally > data.tar.gz
once you have these you essentially have a rom

There's also an app called "zip me" in the play store that will do exactly what I wanted.
https://play.google.com/store/apps/details?id=zip.me
Sent from my Samsung Galaxy Note 5 running Darthstalker v8 and Xposed 85.1

re: backups
tamelion1117 said:
I trust in my nandroid backups. The main reason I want to create a flashable zip with everything backed up in it is to have the ability to create a duplicate image of my phone and flash it on my wife's.
Sent from my Samsung Galaxy Note 5 running Darthstalker v8 and Xposed 85.1
Click to expand...
Click to collapse
If you want a duplicate image why not create two nandroids and copy one
to your pc then to your wife's phone since you say the phone is identical
which they would have to be in order to use the same backup.
Once the nandroid is on your pc you can simply copy it to your wife's
internal memory then restore using twrp.
I have about 5-6 nandroid backups of different roms for my phone.
Goodluck,

Misterjunky said:
If you want a duplicate image why not create two nandroids and copy one
to your pc then to your wife's phone since you say the phone is identical
which they would have to be in order to use the same backup.
Once the nandroid is on your pc you can simply copy it to your wife's
internal memory then restore using twrp.
I have about 5-6 nandroid backups of different roms for my phone.
Goodluck,
Click to expand...
Click to collapse
I don't think I was clear in the op. I know how to create nandroids, and yes, I could easily do it that way, but what I really want to do is compile my rom, settings apps and app settings into a flashable zip instead. To further my knowledge so to speak.
Sent from my Samsung Galaxy Note 5 running Darthstalker v8 and Xposed 85.1