Related
So I tried renaming my backups on pc, since rom manager would always mess up when trying that method. Both ways I get a "m5 sum incorrect " or something like that!
Any ideas, sometimes I have so many backups its hard to tell what's what
Sent from my PC36100 using XDA App
ROM Manager will let you name your backups. Only thing I can think of.
how do you use rom manager to rename them i renamed them all with ES File Explorer and now all my backups get that m5 sum incorrect thing
Already tried rom manager to rename, if I try and restore I get the "sum "error
Sent from my PC36100 using XDA App
I used to have this problem. What I currently do, is as follows, using Amon_RA 2.2.1 Located here:
http://forum.xda-developers.com/showthread.php?t=705026
I use the recovery nandroid backup. When I do this it creates a folder under /sdcard/nandroid/...... where ...... is the folder nandroid will create upon your first backup. From there all your future backups will go into that folder, it will be something goofy, the folder for me is Ht096Hl01177 (path looks like this: /sdcard/nandroid/HT096H101177/New Backup, rename this folder, not the HT one), within that folder will be your actual backup. Create the nandroid backup, I use ROOT EXPLORER (Paid but worth it since you can do mounted deletes), to rename the newley created backup, do not change the parent folder. Then when I want to restore to that one, I make sure I do a full wipe including Dalvick Cache. Using this process I don't hardly ever get the m5sum error. Hope that helps. I currently have 4 backups under the parent directory and I can restore them fine as long as I wipe first.
The easiest and cheapest way is by opening rom manager and scroll down to where it says backup/restore and on the backup you want to rename you hold it and then it will give you options like delete etc...chose rename and rename it example MikFroyo_1-24-2011 when you space make sure you _ for spaces and you should not get an error I segest you make a backup and use that to test it you can also rename it by clicking back up restore within rom manager and press back and rename it like showed in the example hopes this helps I have tested both with no problems what so ever
Sent from my PC36100 using XDA App
I always rename mine with no issues...so far. I just leave all the numbers then start at the end like this. 2010-11-20.07.24.51 then I add -MYN-01-HB-76. Dont know if this will work for everyone. I just didnt want to mess with the file name too much
Evo - Myn 2.2 RLS 3 - Clockwork - HBoot .76
The key thing to know about renaming nandroids is that you have to be sure to leave no spaces in the names...
You can name it CM6.Jan25 but not CM6 Jan 25
You do not need to save the given name of it, I assure you.
....this is true whether you rename with rom manager, root explorer or estrongs ..... that is all you need to be concerned with, as long as you do that you should be fine....
eeeeeeeeek said:
I used to have this problem. What I currently do, is as follows, using Amon_RA 2.2.1 Located here:
http://forum.xda-developers.com/showthread.php?t=705026
I use the recovery nandroid backup. When I do this it creates a folder under /sdcard/nandroid/...... where ...... is the folder nandroid will create upon your first backup. From there all your future backups will go into that folder, it will be something goofy, the folder for me is Ht096Hl01177 (path looks like this: /sdcard/nandroid/HT096H101177/New Backup, rename this folder, not the HT one), within that folder will be your actual backup. Create the nandroid backup, I use ROOT EXPLORER (Paid but worth it since you can do mounted deletes), to rename the newley created backup, do not change the parent folder. Then when I want to restore to that one, I make sure I do a full wipe including Dalvick Cache. Using this process I don't hardly ever get the m5sum error. Hope that helps. I currently have 4 backups under the parent directory and I can restore them fine as long as I wipe first.
Click to expand...
Click to collapse
right on. this is execly what i do to rename
Vandelay007 said:
The key thing to know about renaming nandroids is that you have to be sure to leave no spaces in the names...
You can name it CM6.Jan25 but not CM6 Jan 25
You do not need to save the given name of it, I assure you.
....this is true whether you rename with rom manager, root explorer or estrongs ..... that is all you need to be concerned with, as long as you do that you should be fine....
Click to expand...
Click to collapse
Yeah, I use Root Explorer, no spaces, works fine for me.
Hey guys,
asked this question in the wrong section so I'm asking it here.
Is it possible to extract an old nandroid backup to view memos I may have had?
I don't want to restore the backup, I know something in it is wrong as it would freeze on bootup after I tried a restore, that isn't important. What is important is there were memos stored on that backup that I need back.
I used unyaffs to extract system.img, but everytime I try and extract data.img (which is where I'm guessing the memos are stored) I get a popup in windows 7x64 that says unyaffs.exe has stopped working.
I copied data.img off my sdcard and am trying to extract through windows terminal.
Can someone tell me if I am correct in thinking the memos would be stored in the data.img and where they might be located and why I am unable to extract data.img?
Thanks in advance!
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.
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.
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.