On my old Magic, I was running CM6 and I thought CWM - but I don't remember now, I'm thinking possibly it was another recovery, because I had the ability then to name my backup files before starting the backup, so I could give them more meaningful names than just the date.
Can I rename my backup files on my SD card? Just use Astro for this, or what?
Or will this cause CWM to no longer see the files as valid backup files?
Additionally, I had been rooted prior on GB - now that I'm on ICS, I'm not sure I want those on my SD card in the (hopefully) unlikely event that I accidentally pick one of those nandroids to restore when I meant to restore back to a prior ICS version. Seems like there could be risk of bricking my phone, so can I copy and delete these off my phone?
Is it as simple as knowing where to look on the SD card and using Astro to rename them, or Kies (or Windows) to move them/delete them?
I dont think you can do that because then it will give you an MD5 mismatch. I think in the new version of TWRP recovery coming out, you can name and rename backups though.
slick_rick said:
I dont think you can do that because then it will give you an MD5 mismatch. I think in the new version of TWRP recovery coming out, you can name and rename backups though.
Click to expand...
Click to collapse
You can rename them as long as you don't put any spaces when you rename it. For example - blazer 4.1 gb- would not work you would have to us blazer.4.1.gb and it would work fine.
albertouresti said:
You can rename them as long as you don't put any spaces when you rename it. For example - blazer 4.1 gb- would not work you would have to us blazer.4.1.gb and it would work fine.
Click to expand...
Click to collapse
There's your answer then.
Related
Does anyone have the default SMS notification sound? I flashed a new rom and it doesn't have it. Thanks!
I have it somewhere on the sd card but honestly, I forgot what it sounded like and the name of it. Was it "notice me"? I can't help you at this moment because the phone won't let me upload. The only other thing I could think of if nobody else comes through for you is to do a COMPLETE nandroid backup in recovery, reinstall the previous rom, find the sounds and copy them to your card. Then go back into recovery and restore the full nandroid backup.
Or another way is to extract the rom zip file on the sd card or computer and then look in system/media/audio of the extracted zip and that's where they are at. Put them in (make these directories if you don't already have them) /sdcard/media/audio/notifications. After a reboot, they "should" show up in the place to change notifications. If that doesn't work the program called "aring" should set things up for you. I think you still might need a reboot. Sorry I couldn't be more help, I'm at work now.
herbthehammer said:
I have it somewhere on the sd card but honestly, I forgot what it sounded like and the name of it. Was it "notice me"? I can't help you at this moment because the phone won't let me upload. The only other thing I could think of if nobody else comes through for you is to do a COMPLETE nandroid backup in recovery, reinstall the previous rom, find the sounds and copy them to your card. Then go back into recovery and restore the full nandroid backup.
Or another way is to extract the rom zip file on the sd card or computer and then look in system/media/audio of the extracted zip and that's where they are at. Put them in (make these directories if you don't already have them) /sdcard/media/audio/notifications. After a reboot, they "should" show up in the place to change notifications. If that doesn't work the program called "aring" should set things up for you. I think you still might need a reboot. Sorry I couldn't be more help, I'm at work now.
Click to expand...
Click to collapse
That's fine. That's help enough. Thanks again.
extract not flash
Like I said, make new folders on the sdcard media/audio/notifications
unzip file(s)
put files into the directory above
reboot
phone should see them now
I think the sound you wanted was little, here's all the original notification sounds anyways
And if you act right now, we'll throw in a bonus gift!
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.
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.
I have a backup file on my sd card from my old evo. The phones broken so i can't restore the backup. I wanted to pull some files out but I don't know how to go about doing it. I started making an emulated version of the phone but I'm not sure I'll be able to restore the backup in the emulated version. Any help would be great.
Put the file in your new phone and use a program like Nandroid Manager to extract what you need.
Captain_Throwback said:
Put the file in your new phone and use a program like Nandroid Manager to extract what you need.
Click to expand...
Click to collapse
Great. Thank you.
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.