Where does Nandroid back up your current rom to? - EVO 4G Q&A, Help & Troubleshooting

Topic.
I have used it a couple of times and wanted to delete some of the older backups to save space. Thanks for your help!

Should be under your SD card in a folder named nandroid. Inside will be one folder beginning in HT05 (at least it is in mine) and within that folder are more folders with different nand backups. I can't tell if there is any importance to their naming but I know you can view them by the date created so you should have some idea of whats what. Hope this helped.

Faust* said:
Should be under your SD card in a folder named nandroid. Inside will be one folder beginning in HT05 (at least it is in mine) and within that folder are more folders with different nand backups. I can't tell if there is any importance to their naming but I know you can view them by the date created so you should have some idea of whats what. Hope this helped.
Click to expand...
Click to collapse
Quick correction - if you have ClockworkMod, it has a folder in the root of the SD card called clockworkmod. I guess it does things a bit differently. This caused me some panic when it could not see my previous nandroid backups (from a different custom recovery).

Related

clearing my old backups

Quick ? since i been playing around with different roms i've also done a lot of backing up but now since im sticking to a rom how do i delete the old backups saved in recovery i mean the ones i dont want anymore?
You can delete via rom manager, manage backups and restore, select, and then delete.
Or mount your sd card on your comp, navigate to the backup folder, and delete.
thanks for the tip.
No problem man. They can eat up space if you have a lot.
teh roxxorz said:
No problem man. They can eat up space if you have a lot.
Click to expand...
Click to collapse
Especially if you make a backup before you install the latest CM7 Nightly like I do. I just deleted about six backups last night before creating one for build 28 and then installing build 30.
Astro, root explorer or most of the file explorers can delete them. They should be in /sdcard/nandroid/(device identifier). Just delete the older dates you don't want.
Sent from my PC36100 using XDA App
The question i've always had is can you rename this files and if so, will nandroid be able to restore from whatever custom name you create? Does it look at some other identifier number or something to know which is the last back up that was created?
I think I had read a while back that you can because it's hard to loose track of which out of the many in that folder is your last back up or what is on that back up. Wasn't there an app that let you rename them and or put a description of the ROM's contents as well?
QuiQNeZZ said:
The question i've always had is can you rename this files and if so, will nandroid be able to restore from whatever custom name you create? Does it look at some other identifier number or something to know which is the last back up that was created?
I think I had read a while back that you can because it's hard to loose track of which out of the many in that folder is your last back up or what is on that back up. Wasn't there an app that let you rename them and or put a description of the ROM's contents as well?
Click to expand...
Click to collapse
You can rename them. No spaces tho! (Use - instead) cant rename the folder tho.
Sent from my PC36100 using XDA App
aimbdd said:
You can rename them. No spaces tho! (Use - instead) cant rename the folder tho.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Ok so as the other poster said, there is a "Phone Identifier" numbered folder. I know I can't rename that. Then inside that are the different backups I have in folders and the files within them. So are you saying I can't rename THOSE folders too?
You can rename the individual backup folders, just not the phone identifier folder. My paths look like this. /sdcard/nandroid/HT0A****/ (then I have my cm backup folder named CM7, My fresh folder named Fresh and a couple others). The *'s are just place holders, I can't remember the exact name.
You can change any folder names after the HT0A folder. Just no spaces, - or _ work fine though.
Sent from my PC36100 using XDA App

Rename backup files - CWM

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.

[Q] Problem with nand bakcup

Hello
My problem is that I downloaded the nand stock rom from the thread and extracted it and tried to put it in the clockworkmod\backups folder and I think it was ok (not sure) but by mistake I deleted all of backups (the stock and the one i created) and I tried to copy it again and create another one but I noticed that there never 2 backups.
The one that I created I can see only from the restore option in recovery and not in the folder ( I used to see it in the folder ..) and the stock one I can see in the folders but not in the restore option.
Should it be like this ? Am I doing something wrong ?
How can I restore that stock backup if I cant see it ?
I'm on ordroid 9 with TWRP recovery.
And the stock one gets in ZIP but i extracted it and copied as folder.
Thanks in advance , I'm afraid to flash new version.
That's because you didn't put it into clockworkmod>backup folder in the sd card and btw you don't extract anything .....every nandroid backup must have 5 zip files in it (don't extract it) and should be named as the date and time it was created
The folder should be like this
Clockworkmod\backup\date & time folder\backup files
donhashem.dh said:
That's because you didn't put it into clockworkmod>backup folder in the sd card and btw you don't extract anything .....every nandroid backup must have 5 zip files in it (don't extract it) and should be named as the date and time it was created
Click to expand...
Click to collapse
I know :\
I extracted the stock backup folder from the zip . not the content in backup.
Forgot the part about renaming, that actually might be the case.
Thanks both of you, I'll try it.

Internal SD File Structure has embedded"0" folders (2)

So I flashed a new rom with all the wipes and I ended up with a couple issues and the typical 4.2 file structure under the "0".
I tried another ROM again today (with the wipes) and now I have two "0" folders, one embedded under another and a lot of my backups are in different locations.
So it's SDCard/0/0.
Is there a good way to fix this?
cwepruk said:
So I flashed a new rom with all the wipes and I ended up with a couple issues and the typical 4.2 file structure under the "0".
I tried another ROM again today (with the wipes) and now I have two "0" folders, one embedded under another and a lot of my backups are in different locations.
So it's SDCard/0/0.
Is there a good way to fix this?
Click to expand...
Click to collapse
I know the CAUSE is from using an out-of-date recovery. TWRP hasn't had that issue for a while, but i think CWM only fixed it just recently. It didn't start until i believe 4.2.1 ROMS were flashed. I'm still not sure if it's a good thing or not to delete those "0" folders or not. I'm sure someone will chime in on that.
the 0 folders have your sd card files in them (pictures, music, etc). if you move all your stuff back to the root of your internal sd card you can delete the 0 folders.
sent from my i747 with xda-premium
I tried moving the folders on my windows PC (old pos) and it didn't work. Android file transfer doesn't work with my GS3 and my Mac.
Frustrating.
Anyways to reflash something in CWM or is moving the files the only way?
Edit: Astro works alright...so where should Ibe putting most of these files? Under SDCard or under SDCard/0?
Now i moved some folders up, the gallery shows everything as a picture (icons) and titanium can't find any apps.
Nw sure what to do.
After I went back to stock, re-rooted, and reflashed 4.2, I tried moving everything from /sdcard/0 to /sdcard. It seemed to work, but then all of a sudden, on the next boot, it was all gone. My internal storage was wiped.
Luckily most of the important stuff is on my external SD card, but that was still really frustrating.
Just a word of warning if you try to move these files. Make a backup.
Please read forum rules before posting
Questions and help issues go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
No file moving should be done, it will most likely cause data loss when the issue is finally gone... If CWM has fixed it switch to the newest one or use TWRP and Fully Wipe the phone including format /system...
Here is a link to a script you can flash to move files from 0 folders back to sdcard, you can thank the OP of the script there:
http://forum.xda-developers.com/showpost.php?p=35653109&postcount=8124
Manual solution via Windows
I had the same problem. Solved via the following steps: Using Windows, navigate to deepest level "0" folder. Select all, copy. Navigate to the next higher level "0" folder (or the root "Phone" folder if you're only one step down). Paste. Windows will perform a merge, versus replace.
Next, delete the "0" folder from the directory you're currently in, the one you just copied all the files from. I should note, I actually moved the folder to my desktop just in case I needed to bring it back later. So far I haven't, but better safe than sorry.
Once that's done, select all in the same folder, copy. Navigate to the next higher "0" level folder or the root (or the root "Phone" folder if you're only one step down). Paste. Repeat same process, move up a level, repeat, move up a level. You'll need to do this for every "0" folder you have (I had two, I've seen reports of more & less).
Eventually, you'll have all the same files and directory structure merged up to the root Phone folder. My device, a Samsung S3 running 4.3, recognized and responded to the changes with no problems.

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.

Categories

Resources