Develop Bugs

[Q] Renaming nandroid backups

With trying new roms, daily now it seems, is it possible to rename nandroid backups to something that makes more sense then just a date/time stamp like the name of rom/kernel?

Usually it doesn't matter as long as there's no special characters but I've tried it before and always get an md5 sum mismatch I just write down the date and the name of the rom
Sent from my SPH-D700 using xda premium

You need to use ROM Manager for this, then it will work with or without ROM Manager in CWM 5.0.2.7.

I usually put the backups in folders with meaningful names. I have to move them back to the proper location before restoring.
Never tried rom manager to do this though.
sent from my secret underground bunker

I was able to rename my backups with es file explorer just renamed it something like CM7_33 and it restored just fine

K3VlN said:
I was able to rename my backups with es file explorer just renamed it something like CM7_33 and it restored just fine
Click to expand...
Click to collapse
Sometimes that will work for me also... most of the time I will get an md5 sum error when I rename them though... like biggoron said the easiest way is to write them down somewhere... or as (insert name here) said you can put them in a seperate folder with the name and then move them back before restoring them....
Sent from my SPH-D700 using Tapatalk

hmmm strange error to have happen but good to know guess id better make another back up and delete the changed one

I had the md5 mismatch too. It seems you can rename as long as you don't put any spaces. I have been renaming mine CM7N##beforeCM9blahblah and it still works. If I put spaces in, then md5 mismatch

kennyglass123 said:
You need to use ROM Manager for this, then it will work with or without ROM Manager in CWM 5.0.2.7.
Click to expand...
Click to collapse
Thanks, I renamed some of them using ROM manager and the one I tried worked.

I tried twice to do it manually, no spaces and always got the md5 error. My backups are too important so I only use ROM manager as it makes sure the MD5 is correct.

kennyglass123 said:
I tried twice to do it manually, no spaces and always got the md5 error. My backups are too important so I only use ROM manager as it makes sure the MD5 is correct.
Click to expand...
Click to collapse
Yup, this is the main reason I use rom manager, to name my backups to keep track of them easier. The nightlies for cm7 in rom manager don't hurt either..

I was actually trying to restore a backup which had an altered name and the recovery kept prompting error.
I had to rename the prefix back to BCDEARS in order for it to restore.
I think the prefix is important because it's a code to the kind of content that was actually backed up.

Md5 Mismatch on Nandroid Backups Caused by Name Change?

Some of my Nandroid backups have been getting md5 mismatched lately. I just realized that the reason may be because I change their names to something like "Blend ICS" or "Blazer", etc. Anyone know if this is the problem? And is there any way to rename them without causing a mismatch? Someone said to just add some like "blazer" without spaces right before the auto-named CWM folder (so basically the date). This won't cause problems will it?

iniz94 said:
Some of my Nandroid backups have been getting md5 mismatched lately. I just realized that the reason may be because I change their names to something like "Blend ICS" or "Blazer", etc. Anyone know if this is the problem? And is there any way to rename them without causing a mismatch? Someone said to just add some like "blazer" without spaces right before the auto-named CWM folder (so basically the date). This won't cause problems will it?
Click to expand...
Click to collapse
As long as you only add to the beginning without changing the rest if the name you should be ok.
Although I might recommend another option. When I need to categorize them I just create a new folder, name the new folder whatever i want and move them into it. If I need to restore a specific nandroid I just move it back into the original CWM backup folder and restore it.

iniz94 said:
Some of my Nandroid backups have been getting md5 mismatched lately. I just realized that the reason may be because I change their names to something like "Blend ICS" or "Blazer", etc. Anyone know if this is the problem? And is there any way to rename them without causing a mismatch? Someone said to just add some like "blazer" without spaces right before the auto-named CWM folder (so basically the date). This won't cause problems will it?
Click to expand...
Click to collapse
I've heard as long as you don't have any spaces, it should be fine. Such as "Blend.ICS" or something. I had the same issue long ago, I put the name of a ROM (with spaces) instead of the date then had the same issue. I simply fixed it by replacing the name back to a random date without spaces.

I never rename anything but I have heard you can change the beginning portion and I try to limit the amount of nandroids only three stock, daily driver, and one test build I update my daily every few days and delete the old one
Sent from my SPH-D710 using XDA

I always change the name because it only shows the timestamps. I modify the name with rom version and status good or final ....
I check the md5 checksum after the name change and it's always successful. Even I restored with name changed nandroid backup multiple times and never had any problem.
Only the problem with nandroid backup was I made it thru rom manager or rom toolbox. It's causing md5 mismatch on ics rom. So ifyou use rom toolbox or rom manager on ics, you need to extremely careful.
Sent from my SPH-D710 using xda premium

Yeah I have an ICS ROM and I tend to avoid using apps like ROM Manager and just do it myself in Recovery. But thanks everyone for the responses. I think I'm just gonna create a folder for them like rwilco said or just edit the beginning.

One of the good habit is verifying the md5 checksum using the tool something like afv. I'm always check the md5 checksum against the nandroid backup. This tools is free and very useful...

MD5 Checksum
How do you do the md5 check? Is there a special command you need to type at a command prompt?

bronski813 said:
How do you do the md5 check? Is there a special command you need to type at a command prompt?
Click to expand...
Click to collapse
There are many ways but I use afv.
For example - (serious of screenshots)
1. You can change the directory name of nandroid backup (it's not related to md5 checksum at all. But don't change the individual file's name inside of the directory. If you do that, then you have to change the md5 checksum file and checksum data also.
2. Open afv and select file
3. move to the directory and long click on nandroid.md5 file
4. select verify nondroid backup
5. check the result.
If you want to check the individual backup's md5 checksum, select the file and do the 'calc md-5 checksum' and compare the result with nandroid.md5 file.
Lots of fun (lof)!

kobridge said:
There are many ways but I use afv.
For example - (serious of screenshots)
1. You can change the directory name of nandroid backup (it's not related to md5 checksum at all. But don't change the individual file's name inside of the directory. If you do that, then you have to change the md5 checksum file and checksum data also.
2. Open afv and select file
3. move to the directory and long click on nandroid.md5 file
4. select verify nondroid backup
5. check the result.
If you want to check the individual backup's md5 checksum, select the file and do the 'calc md-5 checksum' and compare the result with nandroid.md5 file.
Lots of fun (lof)!
Click to expand...
Click to collapse
How do you correct the md5? im not sure what i did but every nandroid i make refuses to restore saying that "md5 mismatch"...
Can afv match the md5?

samsmalls said:
How do you correct the md5? im not sure what i did but every nandroid i make refuses to restore saying that "md5 mismatch"...
Can afv match the md5?
Click to expand...
Click to collapse
If nandroid backup md5 file mismatch, then calculate individual files md5 checksum and compare with nandroid.md5 data. Modify the checksum data from nandroid.md5 file. It does not automatically match the md5. AFV only provides verification and calculation.
To fix the md5 mismatch automatically, you can use another tool something like 'Root Toobox'. This tool fixs the md5 error but does not show the fixing result. So, this tool is not recommended to fix the md5. There are many other tools in the market, please try to search.
Update - do not use root toolbox. It breaks the md5 file.

samsmalls said:
How do you correct the md5? im not sure what i did but every nandroid i make refuses to restore saying that "md5 mismatch"...
Can afv match the md5?
Click to expand...
Click to collapse
If you have a mismatch with md5 - see my signature. You can type the command from terminal on your phone. Then everything is right again.
Oops, forgot I deleted it from my signature. Here it is:
http://forum.xda-developers.com/showthread.php?t=714114

iniz94 said:
Some of my Nandroid backups have been getting md5 mismatched lately. I just realized that the reason may be because I change their names to something like "Blend ICS" or "Blazer", etc. Anyone know if this is the problem? And is there any way to rename them without causing a mismatch? Someone said to just add some like "blazer" without spaces right before the auto-named CWM folder (so basically the date). This won't cause problems will it?
Click to expand...
Click to collapse
If you have this problem, use rom manager or romtoolbox to rename the backups , and itll work

This thread is 4 months old...
Sent from my SPH-D710 using xda app-developers app

Indeed it is
Sent from my SPH-D710 using xda app-developers app

krishneelg3 said:
If you have this problem, use rom manager or romtoolbox to rename the backups , and itll work
Click to expand...
Click to collapse
So one person says Rom Manager / Rom Toolbox will not work for renaming nandroids, you say it does. Which is it?
I recently had some backups that didn't work because I renamed them completely. I got md5 mismatches. I dont use CWM though. Strictly 4EXT. I dont believe Rom Manger will do much for you if your recovery is not CWM. Still, renaming seems to be problematic but you have to do something to keep them organized/separate. Dates dont mean much a few weeks later.

It doesn't matter what you name the backup. Just don't add spaces instead if where the space is put dots "." And it'll work.

Can't restore?! Please help

I rooted my phone today and did a CWM backup - I then flashed CM10 and then tried to do a restore but when I try it I get the following error "Couldn't open directory, No files found"
Yet when I browse my files I can see the back up I made in the CWM folder - why won't it restore this?
Any thoughts?
Thanks in advance!

jackryan57 said:
I rooted my phone today and did a CWM backup - I then flashed CM10 and then tried to do a restore but when I try it I get the following error "Couldn't open directory, No files found"
Yet when I browse my files I can see the back up I made in the CWM folder - why won't it restore this?
Any thoughts?
Thanks in advance!
Click to expand...
Click to collapse
Hmm...not sure if it's related, but the only time my CWM backup didn't restore was some MD5 mismatch error. I renamed the backup to "backup.tar" (if you're using *.tar and not /blobs) after I read that worked on a thread, and wala, it worked! Unsure if that's what your issue is, though.

ikjadoon said:
Hmm...not sure if it's related, but the only time my CWM backup didn't restore was some MD5 mismatch error. I renamed the backup to "backup.tar" (if you're using *.tar and not /blobs) after I read that worked on a thread, and wala, it worked! Unsure if that's what your issue is, though.
Click to expand...
Click to collapse
I just tried what you said and it still doesn't work - I did notice that my backup is a file folder not just a file - so I don't think renaming the folder to a .tar will actually do anything to it?

Is there any other way to restore from a back up I have on my phone but that CWM doesn't seem to see??

You could try moving the file with a file manager or make sure permissions are good.
Sent from my SAMSUNG-SGH-I747 using xda premium

Push it with Odin? Or just grab the stock rooted file from the stickies and push that with Odin.
Sent from my SGH-I747 using xda app-developers app

What would I be looking for as far as permissions go?

jackryan57 said:
I just tried what you said and it still doesn't work - I did notice that my backup is a file folder not just a file - so I don't think renaming the folder to a .tar will actually do anything to it?
Click to expand...
Click to collapse
Hmm..it's been a while since CWM--do you have any folder called blobs? If so, then my tip to rename to "backup.tar" won't work. Basically, you're right. If you don't have a *.tar backup, then I got nothing. CWM used to be *.tar only, then defaulted to /blobs, and now is defaulting back to *.tar with the option of /blobs.

join the club...
http://forum.xda-developers.com/showthread.php?t=2101424
No idea what's going on with this crap. I've lost every backup now for two weeks, the worst of which was my stock backup.

i may have ended up finding a solution to the problem here, if yours is similar enough to mine.
http://forum.xda-developers.com/showthread.php?t=2101424

[Q] How do I fix MD5 Mismatch problem with 4.2?

I would like to go back to backup that I did earlier today, but when I try to restore the nandroid backup, I get the MD5 mismatch problem. I googled and found reference to creating a blank nandroid.md5 file, but I can't seem to find where Clockwork Mod 6.0.3.1 has stored the files.
I realize that the issue is that my new ROM (CM 10.1) s different than the old ROM (Stock 4.2.1).

kendoori said:
I would like to go back to backup that I did earlier today, but when I try to restore the nandroid backup, I get the MD5 mismatch problem. I googled and found reference to creating a blank nandroid.md5 file, but I can't seem to find where Clockwork Mod 6.0.3.1 has stored the files.
I realize that the issue is that my new ROM (CM 10.1) s different than the old ROM (Stock 4.2.1).
Click to expand...
Click to collapse
Your backup is in data/media/clockworkmod
with es explorer navigate to backup>name of backup, open nandroid.md5 file, select Text, and then select ES Note Editor. Highlight everything in the file and delete it. Tap the Back key, and confirm saving with Yes. By deleting the content in the file, you force clockworkmod to skip matching md5sum.
this method requires that you have a non corrupted backup.
sent from my Galaxy

samersh72 said:
Your backup is in data/media/clockworkmod
with es explorer navigate to backup>name of backup, open nandroid.md5 file, select Text, and then select ES Note Editor. Highlight everything in the file and delete it. Tap the Back key, and confirm saving with Yes. By deleting the content in the file, you force clockworkmod to skip matching md5sum.
this method requires that you have a non corrupted backup.
sent from my Galaxy
Click to expand...
Click to collapse
Thanks for this. It turned out to be in a different location: /mnt/shell/emulated/clockworkmod
Also by default ES File Explorer is not in root mode so that this is not accessible until you change that.

TWRP can't recognize backup folder name

My phone is GT-N7105 (Samsung Note 2)
=============SHORT STORY=============
TWRP can't recognize my backup folder name which I am trying to restore
=====================================
=============LONG STORY=============
I had a nandroid backup before, then I copied the backup to PC, still have it. Then I flashed lineage 13. I deleted the nandroid backup on the phone storage. Now I want to restore the backup so I copied the backup files from the PC.
Now when I go to TWRP Restore mode, no backups are found.
I already searched through the internet and found the renaming method but there's a problem:
this is my original backup:
TWRP/backups/42f7491d7b409fc7/2017-03-01--05-28-34_JZO54K.N7105XXDMB
I tried to make a new backup of my current lineage (just to see if the folder name changed based on the new folder the backup process will create), here is what the resulting folder was:
TWRP/backups/42f7491d7b409fc7/2017-07-05--09-27-29_lineage_tOlte-userdebug_6.0.1_MOB31K_ab972c
As you can see, only the innermost folder name changed. So from what I found through searching, it said to rename the old backup folder to the new backup folder's name, meaning :
I changed
2017-03-01--05-28-34_JZO54K.N7105XXDMB
to
2017-07-05--09-27-29_lineage_tOlte-userdebug_6.0.1_MOB31K_ab972c
TWRP still can't see the original backup.
So what should I rename the original backup folder for TWRP to recognize it and make it appear?
EDIT:
I already updated my TWRP but problem still exists.

Create a new backup with your current rom, then remove it and add the old one instead.

futchy4u said:
Create a new backup with your current rom, then remove it and add the old one instead.
Click to expand...
Click to collapse
Sorry not really a developer type of guy and I regret tinkering with these stuff on my phone.
What you meant was to make a backup with current rom just to get the folder name that TWRP will recognize and then swap the old stock backup into the folder?
If I just rename the stock backup folder name to 2017-07-05--09-27-29_lineage_tOlte-userdebug_6.0.1_MOB31K_ab972c it's the same as what you said right?
and it should still run smoothly (stock rom should be restored without errors)?
Sorry just asking out of caution.

It's ok, we're all helping each others here. And we all had lots of mistakes and we still do.
Anyways, yes renaming it could do the trick but you don't need to rename the backup name directly. Instead, you need to rename the folder containing the backup.
TWRP path is going to be similar to that
/TWRP/BACKUPS/4d00475b004150de/2017-07-05--09-27-29_lineage_tOlte-userdebug_6.0.1_MOB31K_ab972c
Click to expand...
Click to collapse
All you need to get is that folder name "4d00475b004150de" because it's auto generated by twrp, that's why I asked you to create another backup even if you just backed up your boot file to generate the folder.
Once you did the backup you can then move your old backup to that folder or rename that old similar folder to the newly created one (not the rom backup folder itself).
sgn15 said:
Sorry not really a developer type of guy and I regret tinkering with these stuff on my phone.
What you meant was to make a backup with current rom just to get the folder name that TWRP will recognize and then swap the old stock backup into the folder?
If I just rename the stock backup folder name to 2017-07-05--09-27-29_lineage_tOlte-userdebug_6.0.1_MOB31K_ab972c it's the same as what you said right?
and it should still run smoothly (stock rom should be restored without errors)?
Sorry just asking out of caution.
Click to expand...
Click to collapse

futchy4u said:
It's ok, we're all helping each others here. And we all had lots of mistakes and we still do.
Anyways, yes renaming it could do the trick but you don't need to rename the backup name directly. Instead, you need to rename the folder containing the backup.
TWRP path is going to be similar to that
All you need to get is that folder name "4d00475b004150de" because it's auto generated by twrp, that's why I asked you to create another backup even if you just backed up your boot file to generate the folder.
Once you did the backup you can then move your old backup to that folder or rename that old similar folder to the newly created one (not the rom backup folder itself).
Click to expand...
Click to collapse
Oh, the folder name code you're referring to was 42f7491d7b409fc7 for me. Thanks. I tried it and everything worked (done restoring and it looks like everything is working so far). Thanks a lot again!
To moderators, this topic's problem is solved. Not sure if the topic needs to be locked after being solved, but yeah just a heads up. Not very active here.
Cheers.

sgn15 said:
Oh, the folder name code you're referring to was 42f7491d7b409fc7 for me. Thanks. I tried it and everything worked (done restoring and it looks like everything is working so far). Thanks a lot again!
To moderators, this topic's problem is solved. Not sure if the topic needs to be locked after being solved, but yeah just a heads up. Not very active here.
Cheers.
Click to expand...
Click to collapse
You're welcome. I think it's ok to be left here so that it could help others.