Related
I heard about it on my incredible but never experienced it... I just tried to restore a back up and both my back ups say md5 mismatch...
cwm 3.0.2.4
I am just trying to not have to redo all my stuff but I guess I"ll start now... just looking to see if I can prevent it in the future
Thank god, no. It caused havoc on my Inc but not now.
Sent from my ADR6400L using XDA App
Has anyone else experienced this? I have tried making backups before flashing, but have this problem. It creates the backup and if I try to go back to it, the MD5 mismatch error comes up. This is frustrating. Any help?
happened to me one time...i copied the file onto my laptop and then back to my sd card and it worked! not sure if just a coincidence but worth a try
patdroid1 said:
happened to me one time...i copied the file onto my laptop and then back to my sd card and it worked! not sure if just a coincidence but worth a try
Click to expand...
Click to collapse
Thanks, I'll try that, but if I have to do that every time, it's gonna get old. There has to be something going on that I can fix, I hope. Anyone else?
certainly not a fix if happening often...like i said only happened once to me...let me know if it works.
No luck. Copying to PC, deleting, and replacing didn't change the outcome. Thanks for the idea though. Anyone else run into this?
did you guys rename the files? The names CANNOT have spaces
Of all the backups I ever made this did happen one time. I tried everything I could think of and nothing worked. Sometimes the file is just corrupt and there is nothing you can do about it.
the only time i ever got md5 mismatch was when I renamed the file. returning it to original name and it flashed.
This issue has become a pain in my butt!! everytime i rename a backup, even without spaces, i got an MD5 mismatch upon trying to restore. Is there a solution? Ive already wiped the phone, reflashed the stock RUU and still no luck. I even formatted my sd card and left it completely blank.
Any help is appreciated!
bmerrill63 said:
This issue has become a pain in my butt!! everytime i rename a backup, even without spaces, i got an MD5 mismatch upon trying to restore. Is there a solution? Ive already wiped the phone, reflashed the stock RUU and still no luck. I even formatted my sd card and left it completely blank.
Any help is appreciated!
Click to expand...
Click to collapse
What are you renaming it to? I always rename my backups, and have never had issues. I usually name them something along the lines of: "20110519_BAMF_Remix_1-6-3."
I've heard of people having issues with ROM Manager. Are you creating and restoring your backups from there, or are you booting into clockwork to do them?
TheStick13 said:
What are you renaming it to? I always rename my backups, and have never had issues. I usually name them something along the lines of: "20110519_BAMF_Remix_1-6-3."
I've heard of people having issues with ROM Manager. Are you creating and restoring your backups from there, or are you booting into clockwork to do them?
Click to expand...
Click to collapse
I rename to something similar to what you do.
Typically I never create or restore from RM cause I've heard of others having issues. I really only use RM to rename the backups. I prefer to do it manually through CWM.
However since I haven't successfully been able to rename a backup, I have been using RM to do backups.
Sent by the Tbolt
bmerrill63 said:
I rename to something similar to what you do.
Typically I never create or restore from RM cause I've heard of others having issues. I really only use RM to rename the backups. I prefer to do it manually through CWM.
However since I haven't successfully been able to rename a backup, I have been using RM to do backups.
Sent by the Tbolt
Click to expand...
Click to collapse
Stupid question, I'm sure, but you aren't changing the names of any files INSIDE the backup folder, are you? Only the folder name needs to be changed.
I don't mean that to be insulting your intelligence, at all. Just verifying.
TheStick13 said:
Stupid question, I'm sure, but you aren't changing the names of any files INSIDE the backup folder, are you? Only the folder name needs to be changed.
I don't mean that to be insulting your intelligence, at all. Just verifying.
Click to expand...
Click to collapse
No offense taken, no I am only renaming the folder name itself. I don't get it.
Sent by the Tbolt
I have never been able to restore any backups. Even when I dont rename them. The only one that always works is the original backup of the original rom. Really annoying. Any fix yet?
Turb0wned said:
I have never been able to restore any backups. Even when I dont rename them. The only one that always works is the original backup of the original rom. Really annoying. Any fix yet?
Click to expand...
Click to collapse
I don't think there is any "fix" because I've never heard of anyone else with that problem. Maybe you are renaming the backups with spaces in the file names or you just got a bad SD card.
dirtyfingers said:
I don't think there is any "fix" because I've never heard of anyone else with that problem. Maybe you are renaming the backups with spaces in the file names or you just got a bad SD card.
Click to expand...
Click to collapse
I've had a similar problem with renaming the files. I'll usually add something like: (BAMF_1.7_imo2.5.1) right on to the end of the file name -without spaces- and I also get an md5 mismatch. If I go back and delete the section I added it works fine. I actually ran into this problem when I was reverting from gingerbread back to froyo once all the brick warnings were coming out, and I foolishly cleared data/factory reset, and then tried restoring my backup, which I hadn't yet removed my (addition) at the end and got the md5 error. Luckily I had a copy of an older version of the ROM which I flashed, and then went in with EStrongs and renamed my backup to its original name.
Cmotion said:
I've had a similar problem with renaming the files. I'll usually add something like: (BAMF_1.7_imo2.5.1) right on to the end of the file name -without spaces- and I also get an md5 mismatch. If I go back and delete the section I added it works fine. I actually ran into this problem when I was reverting from gingerbread back to froyo once all the brick warnings were coming out, and I foolishly cleared data/factory reset, and then tried restoring my backup, which I hadn't yet removed my (addition) at the end and got the md5 error. Luckily I had a copy of an older version of the ROM which I flashed, and then went in with EStrongs and renamed my backup to its original name.
Click to expand...
Click to collapse
Thats the thing, I haven't been renaming them anymore and I still always get the same error. Only one that doesn't give me the error is my original rom backup.
Turb0wned said:
Thats the thing, I haven't been renaming them anymore and I still always get the same error. Only one that doesn't give me the error is my original rom backup.
Click to expand...
Click to collapse
I had a buddy have the same thing happen to him. The only backup that would work was the original one that I made for him when I helped root his phone. After that he bought a cheap class 10 SD card off eBay and no backups from that card would work, md5 mismatch every time. It ended up just being a bogus card from a shady seller and after he got a new SD card everything worked well again.
This is a general CWM question but I could not find any place better to post on XDA, so excuse this if incorrect location.
I have flashed all the Skyrocket ICS roms in the past few days to see which I liked best. Before I flashed a new one, I would make a CWM backup of the current one. Wanting to easily be able to identify the files, I appended the rom name to the end of the CWM filenames after deleting all the characters after the date, which appeared to be a GMT time stamp. Now, when I try to restore any of those files, I get an MD5 checksum error. I am only assuming that this is due to changing the filename and not some other problem. Anyone have any ideas on how to fix this? TIA.
phoneturf said:
This is a general CWM question but I could not find any place better to post on XDA, so excuse this if incorrect location.
I have flashed all the Skyrocket ICS roms in the past few days to see which I liked best. Before I flashed a new one, I would make a CWM backup of the current one. Wanting to easily be able to identify the files, I appended the rom name to the end of the CWM filenames after deleting all the characters after the date, which appeared to be a GMT time stamp. Now, when I try to restore any of those files, I get an MD5 checksum error. I am only assuming that this is due to changing the filename and not some other problem. Anyone have any ideas on how to fix this? TIA.
Click to expand...
Click to collapse
Are you talking about the folder name? Because that shouldnt affect it. Inside the folder that is created for each backup, there are backup files which dont have any dates/times in the filename itself.
I vaguely remember reading about this, but I can't recall how it was resolved. Try updating your can to 5.5.0.4 Touch or 5.8.1.3 (?? something along those lines) and seeing if that resolves it. Outside if that I must ask the obvious, did u Google "md5 checksum error cwm"?
Are you using the same CWM version as you did when you backed up? If you didnt, then thats one reason. You have to stay on the same CWM version, many of these CWM versions floating around have different fixes in there.
One way around this is to go to Advanced Restore and restore all the IMG files from there.
Dixit
ihtfp69 said:
I figured I would post this fix here in case anyone else ran into this problem. This is assuming you did not change the folder names and let Clockworkmod create them. I haven't had it happen until today, but it's not a nice message to see when you are trying to do a restore.
Code:
Checking MD5 sums...
MD5 mismatch!
Do this to fix:
To fix this problem use the code below. Substitute the final folder name for the backup you need to fix.
Code:
adb shell
# cd /sdcard/clockworkmod/backup/2010-06-29.20.22.53
# rm nandroid.md5
# md5sum *img > nandroid.md5
When that finishes, re-run the restore and everything should be fine.
NOTE: As rpearl stated, there could be something really wrong with your nandroid, so use this tutorial as a learning experience and not a fix-all. In my case, everything was fine after restoring. However, that may not always be the case. Do this with caution.
Click to expand...
Click to collapse
Use this method to potentially fix.
dixit said:
Are you using the same CWM version as you did when you backed up?
Dixit
Click to expand...
Click to collapse
That is correct on most of them. I updated to CWM Touch for the last one, but it did not restore either. To check this out, I just did a backup and without changing the name did a restore and it worked fine. The thing that was odd in the backups that would not restore was that it immediately bombed out of the checksum each time as if it was checking the name itself first.
That is brilliant. I did not realize you could generate the MD5 from ADB and stick it right into the folder. Thanks!
The few times this md5 mis-match has happened to me was because (a) the backup was actually messed up (check folder size) probably due to corruption or (b) my SD card was out of space. I've always renamed my backup set similar to yours (I append the ROM name) and it never affects the restore.
bdbx18 said:
The few times this md5 mis-match has happened to me was because (a) the backup was actually messed up (check folder size) probably due to corruption or (b) my SD card was out of space. I've always renamed my backup set similar to yours (I append the ROM name) and it never affects the restore.
Click to expand...
Click to collapse
Are you using touch or standard CWM? I wonder if this only happens in touch version. I will try this in the next few days.
I changed the name of one of the backups I created with CWM touch and it restored fine using touch. I suppose my earlier problem may have been trying to restore a backup created with old CWM using touch version.
well since you are on the subject cwm touch im making a nanadroid backup of my current ics rom right now as i speak. i started about an hour ago and its still on the backing up data part. when i used the older version to make backups i dont remember it taking this long. have any of you had cwm touch take well its been a little over an hour now? i do have more apps on my phone now than i did the last time i made a backup would that matter? should i just jerk the battery out and go back to the older version of cwm i was using? thanks ahead of time for any advice / help you may give i would appreciate it. im trying to backup this rom cause i want to flash a different modem cause the ics modem form the leak is crap and need a backup in case it dont work..
garydv2002 said:
well since you are on the subject cwm touch im making a nanadroid backup of my current ics rom right now as i speak. i started about an hour ago and its still on the backing up data part. when i used the older version to make backups i dont remember it taking this long. have any of you had cwm touch take well its been a little over an hour now? i do have more apps on my phone now than i did the last time i made a backup would that matter? should i just jerk the battery out and go back to the older version of cwm i was using? thanks ahead of time for any advice / help you may give i would appreciate it. im trying to backup this rom cause i want to flash a different modem cause the ics modem form the leak is crap and need a backup in case it dont work..
Click to expand...
Click to collapse
If you are using sk8erwitskil version of the CWM touch (ClockworkMod TOUCH 5.5.0.4 v3.5) then most likely you didnt follow one of the directions on the front page. This is a known issue. Here it is again. You need to create that file on the location you backing upto.
For CWM to recognize the .hidenandroidprogress file you need to boot into CWM and go to mounts and storage>>mount /sdcard then go back to backup & restore and make a restore and it should work everytime (as long as you do the steps in that order and you have the .hidenandroidprogress file in /sdcard/clockworkmod & /sdcard/external_sd/clockworkmod folders)
There is a known bug in ClockworkMod 5.5.0.4 that long file names can POSSIBLY cause backups to hang. There is a solution/workaround:
•boot into recovery
•try to make a backup (no matter if it passes or fails proceed to next step)
•either through terminal emulator or through adb run the following command EXACTLY:
Code:
touch /sdcard/clockworkmod/.hidenandroidprogress
•if you are backing up to external sdcard then run the following:
Code:
touch /sdcard/external_sd/clockworkmod/.hidenandroidprogress
im using 5.8.1.3 hercules that i got from the dev section. is this a known issue with it to?
garydv2002 said:
im using 5.8.1.3 hercules that i got from the dev section. is this a known issue with it to?
Click to expand...
Click to collapse
Not sure, I used that for awhile but then went back to the other touch and Ive had those two files still in my directories.
I would go ahead and create those two files (one for internal SD and one for external SD if you got one you are using that is) and try it again. Make sure you call that file exactly the way it is, or copy/paste the code identically if you do it through ADB.
Dixit
garydv2002 said:
im using 5.8.1.3 hercules that i got from the dev section. is this a known issue with it to?
Click to expand...
Click to collapse
I use that one, takes less than 5 minutes on my class 10 sd.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Well the crazy thing is after sitting there over an hour waiting I finally took out the battery and even though it never said complete all the files are there but I still don't trust that it made a good backup so I deleted those files tried putting in the code above and it still would not work so I flashed back to version 5.0.2.0 thats not touch and it made a perfect backup in under 2 minutes. Might be one of those it just ain't gonna work right on this specific phone thing or it could be the little green gremlins at it again lol... who knows.. I'll just wait for new version of touch to come along and try it. It won't be long till a newer greater version comes along as fast as technology is going today.. thanks for the help. I'm learning more and more each day from you guys on xda.....
Sent from my SAMSUNG-SGH-I727 using XDA
Not sure if this is the cause of the issue but for nandroid backups you can't make a folder name with spaces otherwise you will get an md5 sum error. Try renaming the folder with underscores instead of spaces
I currently have CWM 6 installed, but prefer the older version's backup method and file structure (don't like the Blob thing). Can I flash CWM 5 over 6? Thanks!
Youy could, but I dont recommend it. I dont have CWM installed so I cant tell you exactly how, but in the advanced options I am to understand there is an option to disabled the segmented backups, which would eliminate the blobs folder and each backup would then be in its own folder.
apacseven said:
Youy could, but I dont recommend it. I dont have CWM installed so I cant tell you exactly how, but in the advanced options I am to understand there is an option to disabled the segmented backups, which would eliminate the blobs folder and each backup would then be in its own folder.
Click to expand...
Click to collapse
Thanks for your response. I looked at the various menu options and couldn't find that option. Can you be more specific? Thanks!
STraver said:
Thanks for your response. I looked at the various menu options and couldn't find that option. Can you be more specific? Thanks!
Click to expand...
Click to collapse
The best I can do since I dont use CWM myself and dont really feel like installing it just to check (sorry) is quote the person that pointed out to me that it can be disabled. Hope this helps.
Legato Bluesummers said:
You guys realize you can stop making blob backups and go back to normal tar right? Under back up go to advanced settings or whatever its called and choose the other option. Now you won't make back ups in blobs,but now you do them the old way. One folder for the whole back up, about 1-2 GB in size. Blobs are just nice as the backup takes under 5 min. Doing it the old way takes a bit longer.
Click to expand...
Click to collapse
FWIW I use and prefer TWRP (team win recovery project). I switched to it because I was frustrated with the very problem you are having, and gave TWRP a shot and never looked back. I make backups quite frequently and I needed the option of deleting individual backups at will. You can install it with ez recovery. Give it a shot sometime.
apacseven said:
The best I can do since I dont use CWM myself and dont really feel like installing it just to check (sorry) is quote the person that pointed out to me that it can be disabled. Hope this helps.
FWIW I use and prefer TWRP (team win recovery project). I switched to it because I was frustrated with the very problem you are having, and gave TWRP a shot and never looked back. I make backups quite frequently and I needed the option of deleting individual backups at will. You can install it with ez recovery. Give it a shot sometime.
Click to expand...
Click to collapse
Okay thanks. I can't find the option they're talking about. Thanks for your help.
Iirc if you chose backup to external sd card wont it put each backup in its own dated dir inside the clockworkmod dir?
Sent from my CleanRom'd Galaxy SIII
x714x said:
Iirc if you chose backup to external sd card wont it put each backup in its own dated dir inside the clockworkmod dir?
Click to expand...
Click to collapse
Thats what it was doing when I stopped using it, but each folder was only 20mb. The rest of the data was going into the blobs folder.
Currently i have my IMEI backed up by having a nandroid of SYNERGY, which backs it up and creates a file.
my question is this: IS there an easier way that doesn't require keeping a 1gb nandroid on file? Not that i don't like the ROM, it's quite inovative andvery well built, but as i prefer AOSP / CM10.1 based roms, would rather have another way to keep it backed up.
No Flames, not meant to cause an AOSP / TW / CM flame war, but was just curious.
thanks
:cyclops:
Here's a thread with 3 different backup methods. One of them creates a flashable zip based on SynergyROM's backup, which for me ended up about 12.5 MB in size.
http://forum.xda-developers.com/showthread.php?t=1852255
SempaiMatt said:
Here's a thread with 3 different backup methods. One of them creates a flashable zip based on SynergyROM's backup, which for me ended up about 12.5 MB in size.
http://forum.xda-developers.com/showthread.php?t=1852255
Click to expand...
Click to collapse
Thanks! You know, i knew about that thread, however, have forgotten to go back and check it out.
:cyclops:
goldsmitht said:
Currently i have my IMEI backed up by having a nandroid of SYNERGY, which backs it up and creates a file.
my question is this: IS there an easier way that doesn't require keeping a 1gb nandroid on file? Not that i don't like the ROM, it's quite inovative andvery well built, but as i prefer AOSP / CM10.1 based roms, would rather have another way to keep it backed up.
No Flames, not meant to cause an AOSP / TW / CM flame war, but was just curious.
thanks
:cyclops:
Click to expand...
Click to collapse
I would recommend taking a look at the IMEI backup and restore tool http://forum.xda-developers.com/showthread.php?p=29461812#post29461812 it doesn't use the Synergy method. However, the Synergy method is considered easier to use.
Sent from my SCH-I535 using xda premium
Somewhere said to just navigate to the folder containing that, ems folder maybe? Or maybe ems or whatever is also in there. Anyways, there's a bunch of important stuff in that folder, including imei, but use root explorer or some other file manager with root privileges, and create a zip or tar or something of that folder. I have it backed up on my phone, computer, and external drive!
Have any heard of this back up way?
https://play.google.com/store/apps/details?id=com.j.y.daddy.customizer
Clean Rom/reinforced/Gunther/camblued/beastly phone!!!
su
Reboot nvbackup
I think this does it.
mandiw777 said:
su
Reboot nvbackup
I think this does it.
Click to expand...
Click to collapse
This method is the easiest and insures you never lose your IMEI in the first place. Before doing this I lost my IMEI 2 times. Since backing it up this way I have not lost it.
Hi, I currently have my nexus 5 in 4.4.4, and I'd like to try Android L, but I want to know if there's a way to create a full backup of my phone, like an image, so I can go back to 4.4.4 with everything as I left it, including apps, contacts, images, and all that, my phone is rooted, so I guess there's a a way, but, would it be possible to restore it if I'm already in Android L? thanks!
saman0suke1 said:
Hi, I currently have my nexus 5 in 4.4.4, and I'd like to try Android L, but I want to know if there's a way to create a full backup of my phone, like an image, so I can go back to 4.4.4 with everything as I left it, including apps, contacts, images, and all that, my phone is rooted, so I guess there's a a way, but, would it be possible to restore it if I'm already in Android L? thanks!
Click to expand...
Click to collapse
Take a nandroid backup then copy your sdcard to your computer
rootSU said:
Take a nandroid backup then copy your sdcard to your computer
Click to expand...
Click to collapse
Is this going to work if I want to use it from Android L to restore it? thanks!
saman0suke1 said:
Is this going to work if I want to use it from Android L to restore it? thanks!
Click to expand...
Click to collapse
Your best bet would be to take a nandroid backup (which will go to sdcard) then connect in recovery and adb pull the entire /sdcard (which is /data/media/0) to your pc. Then whne you want to go back, adb push it back.
Click the link in my signature. In there you'll find a thread about adb and fastboot if you're unsure about adb push and pull commands.
rootSU said:
Your best bet would be to take a nandroid backup (which will go to sdcard) then connect in recovery and adb pull the entire /sdcard (which is /data/media/0) to your pc. Then whne you want to go back, adb push it back.
Click the link in my signature. In there you'll find a thread about adb and fastboot if you're unsure about adb push and pull commands.
Click to expand...
Click to collapse
I'll take a look at it, I appreciate the help, thanks!
No probs.
The good thing about adb is you can push and pull files to your device, even if you cant get into Android.
rootSU said:
No probs.
The good thing about adb is you can push and pull files to your device, even if you cant get into Android.
Click to expand...
Click to collapse
That's great! and I have used adb before, mostly with rooting and development, but not a lot with backups and all that, I'll give it a try, thanks!:good:
U can use cwm too
kanhaiya
Kanhaiya1.kk said:
U can use cwm too
kanhaiya
Click to expand...
Click to collapse
That would be the "nandroid" part of the solution I suggested. This will not backup the sdcard though
Yes u ri8
Bt i suggested an easy way.. & with the help of some apps like titanium backup or my backup he can restore all things..
kanhaiya
Another way you can do is install Gdrivesync and sync your /sdcard partition to your Google Drive account. It won't replace the files on the phone but this will enable you to be able to recover lost downloads. You can set it up to have it automatically sync every x hours and it's nice too because if you accidently want to install the latest update but it wipes your whole phone including any backups, at least you can get your data again and just have to set up your apps.
If by "easy" you mean "incomplete ", you're right
Sent from my Nexus 5 using Tapatalk
rootSU said:
If by "easy" you mean "incomplete ", you're right
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Hey, I was doing some research, but all the tutorials that I find talks about GooManager, CWM or TWRP. I thought there was a way to create the nandroid backup manually, if not, which of these would you recommend? after that I would pull the entire sdcard I guess right? thanks!
saman0suke1 said:
Hey, I was doing some research, but all the tutorials that I find talks about GooManager, CWM or TWRP. I thought there was a way to create the nandroid backup manually, if not, which of these would you recommend? after that I would pull the entire sdcard I guess right? thanks!
Click to expand...
Click to collapse
You can investigate adb backup. Never used it myself so not sure what it includes
http://forum.xda-developers.com/galaxy-nexus/general/guide-phone-backup-unlock-root-t1420351
rootSU said:
If by "easy" you mean "incomplete ", you're right
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
rootSU said:
You can investigate adb backup. Never used it myself so not sure what it includes
http://forum.xda-developers.com/galaxy-nexus/general/guide-phone-backup-unlock-root-t1420351
Click to expand...
Click to collapse
I'll check on that one; just wondering, have you ever used any of those that I mentioned? if so, which one would you recommend? Thanks!
saman0suke1 said:
I'll check on that one; just wondering, have you ever used any of those that I mentioned? if so, which one would you recommend? Thanks!
Click to expand...
Click to collapse
The only thing that has worked consistently for me is to grab what you want off the /sdcard and copy it to a pc. Then a nandroid of the rest of the phone. I've had mixed results with adb backup and backup apps.
Sent from my Nexus 5 using XDA Free mobile app