Why is it that when I rename one of my backups (rom manager) when I try to restore it later on it gives me an error message?
I haven't had issues with this. What is the version of CWR/rom manager you are running? have you tried restoring in recovery?
lx1907 said:
I haven't had issues with this. What is the version of CWR/rom manager you are running? have you tried restoring in recovery?
Click to expand...
Click to collapse
Running the latest, yes i've tried that also.
I do this all the time (10+ times a week) without problem. This isn't a known or widespread issue.
Sent from my ADR6400L using XDA App
*Ahem* Do you have any spaces in the names for the backup?
Yeah, that'll do it.
I was about to say the same thing. Post an exact example of what you are trying to rename the backup. Probably either spaces or unallowed characters being used.
This is pretty much the ONLY thing I use RM for. I do a nandroid manually and then rename it with RM. I've never had it happen but doesn't it reject your rename if it is unacceptable?
I've never had a renamed backup give an error at restore.
Like a couple people have said, it's more than likely not happy with what you're renaming it as.
I typically do mine like this, "20110531_BAMF_Remix_1-7"
Related
So i restored back to stock blur rom cuz i was feeling all nostalgic and to get a few TB backups. Well when i attempted to restore back to CM9 i kept getting "MD5 Mismatch!" errors. Well it turns out I had left spaces in that and a few other renamed backup folders which apparently is a no-no. Luckily i was able to restore back to another backup, rename the folders without spaces via USB and was able to restore CM9 backups. Just thought this may help others. You might want to check your backup file folder names and get rid of the spaces.
Well I've never thought of renaming then but either way this is good to know for future reference
Sent from my MB855 using xda premium
Thats why I use _ in place of spaces when dealing with CWM backups, makes it easy to read and usable
w0lf215 said:
Thats why I use _ in place of spaces when dealing with CWM backups, makes it easy to read and usable
Click to expand...
Click to collapse
exactly how i renamed the backups
jbb2388 said:
exactly how i renamed the backups
Click to expand...
Click to collapse
Hm that's weird.. I kept name same and just added at end _cm9 or whatever ROM for most but a few I completely changed file name using underscores with no issues and trust me my nandroids get used more than they should lol
Sent from my MB855 using XDA
Given that the same date is used when making Nandroid Backups, how does a person know which is the latest?
I do see different times, but have no idea how to tell for sure which is the latest. Looking at properties via a file explorer doesn't help either.
For me, I rename it it right after so that I know which is the newest. I think this might be your best bet. On mine as well, the dates do change as I do nandroids. They are all from 1970 (lol) but it will start off as 1970/01/01 and then 1970/01/15 and so on.
blue265 said:
For me, I rename it it right after so that I know which is the newest. I think this might be your best bet. On mine as well, the dates do change as I do nandroids. They are all from 1970 (lol) but it will start off as 1970/01/01 and then 1970/01/15 and so on.
Click to expand...
Click to collapse
Thanks, Yeah, that is what I decided, but wondered if there was a way to determine. Which means the 3 I had now really need to be deleted. In fact I have already run another and renamed it.
Interesting note: if you look at the properties of the file, instead of 1970, it shows as being created in 1979, but the name shows 1970.
I have had my Rogers S3 for 1 week not and have had the same problem. Already switched out my sim card and now the same thing. I reboot and it works fine. Any one?
ewingr said:
Thanks, Yeah, that is what I decided, but wondered if there was a way to determine. Which means the 3 I had now really need to be deleted. In fact I have already run another and renamed it.
Interesting note: if you look at the properties of the file, instead of 1970, it shows as being created in 1979, but the name shows 1970.
Click to expand...
Click to collapse
[email protected] said:
I have had my Rogers S3 for 1 week not and have had the same problem. Already switched out my sim card and now the same thing. I reboot and it works fine. Any one?
Click to expand...
Click to collapse
Not sure we are talking about same thing. You talking about Nandroid Files haveing a 1970 date? If so, that is a known bug in the CWMs' creation of the Nandroid files...however from what I hear the files work fine. You just need to be able to keep track of which one is which should you need to restore and have more than 1.
ewingr said:
Given that the same date is used when making Nandroid Backups, how does a person know which is the latest?
I do see different times, but have no idea how to tell for sure which is the latest. Looking at properties via a file explorer doesn't help either.
Click to expand...
Click to collapse
This is not a problem with the "official" version of CWM from clockworkmod.com using ROM Manager...
Sent from my A500 using Tapatalk 2
BakaNeko59 said:
This is not a problem with the "official" version of CWM from clockworkmod.com using ROM Manager...
Sent from my A500 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for that.
JFYI, I read so often that we shouldn't use Rom Manager. Seen a number of posts about it causing problems. Maybe it depends on which CWM use have installed, I don't know. But given the issues I've read about that, and not just on this phone, but my previouis Captivate, I have decided to avoid RM, even though I do own it and used it successfully in the past.
For me the problem is that the phone date is at 1970 while in recovery mode. I tried changing the date from automatic network to manual but that didn't help. I guess I'll be renaming my nandroid backups for a while.
ewingr said:
Thanks for that.
JFYI, I read so often that we shouldn't use Rom Manager. Seen a number of posts about it causing problems. Maybe it depends on which CWM use have installed, I don't know. But given the issues I've read about that, and not just on this phone, but my previouis Captivate, I have decided to avoid RM, even though I do own it and used it successfully in the past.
Click to expand...
Click to collapse
CWM and rom manager are now working fine, date stamp and all.... In sprint anyhow....
Sent from my SPH-L710 using xda premium
Naddict said:
CWM and rom manager are now working fine, date stamp and all.... In sprint anyhow....
Click to expand...
Click to collapse
I can second that for Sprint. I use ROM Manager for my backups, and that lets you edit the name of them prior to starting the backup. I always make sure to append the ROM name after the timestamp of the backup name.
I wonder what version of CWM works for AT&T, and that we know does not blow away IMEI (of course we aren't sure CWM has anything to do with that)
ewingr said:
Given that the same date is used when making Nandroid Backups, how does a person know which is the latest?
I do see different times, but have no idea how to tell for sure which is the latest. Looking at properties via a file explorer doesn't help either.
Click to expand...
Click to collapse
Because since we know the issue with the date on nandroids, us smart one's go in an rename the nandroid right away so we know. For example, 7.22.12StockRD, would be what I would name my nandroid if I made one today....the date for obvious reasons, Stock indicates it's the stock rom, RD indicates rooted and deodexed.
Gadgetz said:
Because since we know the issue with the date on nandroids, us smart one's go in an rename the nandroid right away so we know. For example, 7.22.12StockRD, would be what I would name my nandroid if I made one today....the date for obvious reasons, Stock indicates it's the stock rom, RD indicates rooted and deodexed.
Click to expand...
Click to collapse
Yeah, the smart ones who knew about it before hand. I'm so proud of you. :good:
I recently just tried to restore one of my backups of a different rom and got an MD5 mismatch error. I understand that that can come from errors during a download of a rom but why would I get that error now? Could it be because I renamed the file after it was backed up? Thanks in advance....
Sent from my SAMSUNG-SGH-I717 using xda premium
If your file name has spaces in it, it may cause the MD5 mismatch error.
Or the backup was moved to a pc then moved back to the phone. Windows adds a few bytes to a file so the sum is a little different.
rangercaptain said:
Or the backup was moved to a pc then moved back to the phone. Windows adds a few bytes to a file so the sum is a little different.
Click to expand...
Click to collapse
I hate windows....it bites! I mean ":cyclops:bytes"
I did it all on my phone using a file manager. So if I change the name to something without spaces it should be fine?
Sent from my SAMSUNG-SGH-I717 using xda premium
I had the same problem the other day - a known good backup wouldn't install. After much searching and asking I ended up considering the backup scrapped and moved on. Then the next day I tried again and it worked fine.
Do you have another backup?
Did you change the name of the backup?
rangercaptain said:
Or the backup was moved to a pc then moved back to the phone. Windows adds a few bytes to a file so the sum is a little different.
Click to expand...
Click to collapse
I have had this issue since I like to store my older nandroids on my Win 7 PC. Do you know of any way to identify or remove the extra bytes? It would have to be after the file is transferred back to the Note I imagine.
Your should try renaming your file.
tmb993 said:
I recently just tried to restore one of my backups of a different rom and got an MD5 mismatch error. I understand that that can come from errors during a download of a rom but why would I get that error now? Could it be because I renamed the file after it was backed up? Thanks in advance....
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
Hi
if you did your backup using CWM and you renamed it after doing the backup I suggest you use "." instead of spaces; example if you rename it "CM9 ROM" try "CM9.ROM" or if you backup your stock rom and rename it "stock android rom" tried "stock.android.rom"
Cheers from DFW
Ok well I did that and I thought it would fix the problem but now I keep getting this error message in my recovery. Got it when I tried to reflash the recovery that I properly named and then again when I tried to flash on PA's 4.1 CM10. What in the heck does this mean??
Sent from my SAMSUNG-SGH-I717 using xda premium
I think that means that your version of CWM is not compatible with the zip you're trying to flash.
lactardjosh said:
I think that means that your version of CWM is not compatible with the zip you're trying to flash.
Click to expand...
Click to collapse
Aw man. Well I just had the newest version but reverted back to 5.5.0.4 because it game me a lot of issues. Strange but I also got the same error when I tried to restore from that one backup.
Sent from my SAMSUNG-SGH-I717 using xda premium
I could be wrong, I don't know for sure.
But, you could see what recovery other people are using in the ROM thread.
I copy my backups from SD to computer and back and have run into this issue. I followed the instructions in this link, http://forum.xda-developers.com/showthread.php?t=714114 and it fixed the MD5 mismatch issue. I guess these commands "clean" the backup of whatever windows does to it when copied. Worked like a charm! Also, I always change my backup names and am sure not to leave spaces. This works even if the name is not what CWR generated.
Bigjoe, can you please add this to your Super Everything page -- probably in the CWM section? Thank you.
http://forum.xda-developers.com/showthread.php?t=714114
is there a way to rename a nandroid back up?
if you are using CWM u can do with a file explorer, navigate to clockworkmod/backup/name folder of what u want, no spaces, u can use . though. or with TWRP u can do it before you do the backup on the right where it says rename backup.
robwscott83 said:
is there a way to rename a nandroid back up?
Click to expand...
Click to collapse
I have ended up with MD5 mismatch far too many times renaming CWM backups, I tend these days to place the backup itself into another folder and title that, tends to save the risk of a very irritating error.
TWRP is pretty badass in that it allows you to title your own backups before you even start the backup process. Much more organized of a way to do it if ya ask me.
When naming a backup avoid special characters, period's etc. -_ are OK. Absolutely no spaces. Follow those rules and your fine. To answer op, grab your favorite file explorer (I prefer Root explorer) and rename it under clockwork/backup.
Synergy-I535
thanks for all of the replies guys... I got it... should have known this I guess... just wasn't something I ever really needed to do but now with all the great roms out there for the note... its hard to settle on one.. so organizing my Nbackups is important... thanks guys really appreciate it and love this community! cheers
celkin said:
I have ended up with MD5 mismatch far too many times renaming CWM backups, I tend these days to place the backup itself into another folder and title that, tends to save the risk of a very irritating error.
TWRP is pretty badass in that it allows you to title your own backups before you even start the backup process. Much more organized of a way to do it if ya ask me.
Click to expand...
Click to collapse
this is the correct method...IMHO.:good:
I've renamed mine countless times with no spaces... no problems at all.
you could just make a folder with the name you like, and move the backup to that folder, avoiding the chance of a mismatched checksum.
Twrp is really easy to use
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Anyone know why I can't do a nandroid backup? Every time I try it gives me an error creating MD5 checksum. Currently I'm on AOKP M1 with the built-in kernel which includes CWM 6.0.1.5, but I don't think I've ever gotten it to work with any JellyBean ROM. I'm still using my stock class 2 card and I still have 9gb free space.
Any help would be appreciated.
Sent from my SCH-I500 using xda app-developers app
Are you trying to restore a older nandroid from before the recent partition change? If so, then it won't work. If not then I believe I remember seeing a thread about correcting an md5 error with a nandroid, but I don't have a link for you, sorry. Try to do a search.
I personally don't use nandroids because it backs up system data which in a way defeats the purpose of doing a complete data wipe (which I do often before installing new roms). I simply use TiBu to restore all my apps and just spend 5-10 minutes or so fixing the system settings, then I'm good to go.
I'm not restoring a previous nandroid backup; I'm actually trying to use it to back up my current setup. I'll try to search the issue, unless someone knows where to find it.
I may have to give TiBu another try. It's just nicer to do the nandroid because I wouldn't have to reactivate the phone or resync my accounts afterwards. Basically if I want to try a different ROM and I don't like it I could easily go back to the previous ROM with all my settings and layout.
Sent from my SCH-I500 using xda app-developers app
scarfman4 said:
I'm not restoring a previous nandroid backup; I'm actually trying to use it to back up my current setup. I'll try to search the issue, unless someone knows where to find it.
I may have to give TiBu another try. It's just nicer to do the nandroid because I wouldn't have to reactivate the phone or resync my accounts afterwards. Basically if I want to try a different ROM and I don't like it I could easily go back to the previous ROM with all my settings and layout.
Sent from my SCH-I500 using xda app-developers app
Click to expand...
Click to collapse
You have to reactivate the phone when you flash a rom? Yeah I guess I can see how that would be annoying. I've never had to do that before, however I do have to sign into google every time (doesn't really bother me)
I always make it a habit to reactivate after flashing a new ROM if I also do a data wipe. Otherwise I can't receive calls or texts.
I wonder if the failing backup is because of the larger system partition?
Sent from my SCH-I500 using xda app-developers app
Try a older version of cwm...perhaps 6.0.1. Back when ics was first dropped cwm 5 had similar issues. There is a way to fix it, ill see if i can dig it up for ya.
edit* found it!!
Fix CWM 5.x Nandroid Backup
Let's just say you did what I did today, and did a backup, flashed another ROM, then tried to restore back to the nandroid you just made. Didn't work did it. Come to find out, I wasn't watching the backup, and it fails to generate an MD5 sum. I did a little searching to find out what to do, and I found the following steps (not my work...thanks goes to "desmail" for sharing this).
To fix this is assuming you did not change the folder names and let Clockworkmod create them.*
Code:Checking MD5 sums...
MD5 mismatch!
- Plug your phone to the computer
- Open a Terminal and type:
Code:adb devices
adb shell
# cd /sdcard/clockworkmod/backup/2011-06-29.20.22.53
# rm nandroid.md5 (Probably will fail - for me, the file was never there to begin with...this is fine)
# md5sum *img > nandroid.md5
# exit
****Make sure you change "2011-06-29.20.22.53" to the name of your backup folder*****
- Re-run the restore and everything should be fine.
You will most likely need the Nexus S ADB drivers to accomplish this.