I have done a quick search on this but didn't come up with anything that refers to my specific problem.
I did two backups tonight.. one before I went back to stock w/root and one about ten minutes ago once I got back to almost where I was before going back to stock.
Neither one of them are showing up in the menu on CWM recovery?!? I did a Titanium Backup as well as the nandroid bu so I was at least able to get my data back but I really wanted to restore the first backup I made this evening before I had issues and had to restore an older backup... what I'm wondering is where are the backups? I looked in the clockworkmod/backup folder on the sd card and nothing from tonight shows up.. just my previous bu I made before flashing a ROM. Any help?
No ideas huh?
I just did two Nandroids in Rouges custom recovery based on CWM. It's CWM based so I assume this is going to be the same.
OK! Now I would assume they would/should end up the clockworkmod folder but my phone keeps putting them in /emmc/emmc/bmmc/*
I went into that folder, found the two I just did and moved them over to clockworkmod/backup/* and my recovery instantly saw them and I was able to restore to them.
Not sure why this is the way it is, maybe someone else can shed some light?
Like the previous poster mentioned, sometimes different versions/builds of CWM store their backups in different directories. When backups don't show up, usually the backups are all there, just CWM isn't looking for them there.
You may have gotten different versions of CWM inadvertently by installing a ROM that included a kernel with a different version/build of CWM.
If you manually move the backup directory to the place where your current CWM is expecting them, they'll be seen again.
Related
EDIT: I found the answer! It is true! When I was finally able to get into the system and load clockwork, it worked - I found my Nandroid backup.
So I was using Clockword and I nandroided... subsequently changed to Amon and then messed around with some kernel changes... it didn't work.
So, I tried to Nandroid back *but cannot find the backup I made today* I can only find one that is a couple of days old...
I was wondering, are the Nandroid files stored differently based on the recovery? I am hoping that is the case although it seems unlikely, because I want the one I just saved tonight... Help!
Thanks!
Apologies for what is probably an often asked question, but the search seems to be down at the moment. I'm currently running Ras 2.3 and when I make a nandroid backup of my MIUI, it always runs into an error when trying to restore? I don't even know where to begin looking for solutions to the issue, is this a common thing? Should I just re-flash Ras or something?
Seems the backup was corrupted, reflash your recovery, then make a new one.
Yeah every backup I do seems to get corrupted. I'll try reflashing AmonRa.
thegregbradley said:
Yeah every backup I do seems to get corrupted. I'll try reflashing AmonRa.
Click to expand...
Click to collapse
Let me know how it goes. Also make sure to have at least ~500mb available for a backup.
So I finally re-flashed AmonRa 2.3, and my nandroids STILL show an error! It gets like one dot into resotring and says "oops! an error occurred, check the logs" or something like that. What is happening
first thing would be to check your memory card to see if you have enough space like the post above says. if that doesn't work move the recovery.log via your recovery screen to the sd card and post it here. that should get some questions answered.
edit: also i had this happen to me a couple times when trying to restore it only happened when i changed big things like the radio or the hboot or switching from aosp to sense. that kinda stuff. you might just need to start over and flash a new rom. good thing you used titanium...right? p.s. just relized you were trying to restore not backup so the memory card issue shouldn't apply sry.
I have my MIUI backup so it's not so much of a big deal since that works, but I'd like to have a 100% working nandroid backup in the event that I wanna try out a new rom. Where to I find the recovery log so that I may post it up on here? Thanks for the help guys, I'd be lost without xda
So I just tried moving my recovery log to the SD card and I got the same message, "Oops... something went wrong! Please check the recovery log!"
WTF is going on here?
Potential causes and solutions:
Corrupt SD card. You're screwed, reformat SD card and flash the rom over again.
Corrupt Nandroid file. You're screwed, delete from SD card and flash the rom over again.
Corrupt Recover. Download Rom Manager and re-flash recovery (if you use clockwork, flash alternate then back to clockwork or vice versa if you use amon ra). If this doesn't work, it's likely one of the two above.
However, this is usually the problem when they mess up.
Is there a space in the name of the Nandroid backup? Nandroid backups can NOT EVER have a space in the title. Go into your favorite file manager and remove the space if it has one and it should work just fine.
For example:
MikFroyo 4.61 is NOT an acceptable name. There's a space between the o and the 4.
KonisEliteSeriesIII IS an acceptable name. Notice, there's no spaces.
Hit the thanks button if I helped. Toodles!
Don't use ROM Manager to reflash Amon Ra. Just use the PC36IMG
Trust me on this.
Is it possible that your original nandroids were with clockwork and now that you have updated to amon that they will not work?
Okay so I've re-flashed Amon Ra and reformatted my SD card and I STILL can't get the nandroids to work or my recovery log to move over to the SD card! I've only used Amon Ra for as long as I've been rooted, and nandroids previously worked. Also, these are nandroids that I made within the last 2 weeks or so, they're not old and I have not renamed them. Should I maybe try an older version of AmonRa or something?
OMG I figured it out! Here's the story:
So I bought a new SD card a few weeks back and put it in with just a straight copy of my old SD card in there. This included my nandroid folder. I had been making backups and deleting old backups, but the folder under sdcard/nandroid/HT089HL02240 simply needed to be deleted. I kept sdcard/nandroid, deleted HT089HL02240, then made a new nandroid so that the recovery could simply make this folder itself. Somehow this worked, I don't know why, but it seemed like it might help being that you can't restore nandroids between phones. Perhaps the recovery thought I was attempting to do this, given the SD card switch. Well it works now!
Hi all,
So I've been on paranoid android for the past few months, and I had to revert back to stock for work reasons tonight; it's been a while since I've done my routine backups.
Having made my standard nandroid backup and restored to stock via ODIN, I was horrified to discover that none of my stored nandroid backups would work, running into system/data restore errors every time. I've just read that clockworkmod uses a new process that keeps each individual backups small but requires the presence of a .blob file of sorts, which must have gotten erased when I flashed stock. I checked the size of my nandroid backups and sure enough, they were only around 20 megs; it looks like my internal memory was wiped clean.
My questions are: is everything pretty much gone? And if so, WTF is the point of nandroids if they're no longer self-contained backups? If the devs indeed made changes that led to this, it reeks of inconsiderateness, if not just plain ineptitude.
I apologize in advance if I'm venting or missed something obvious, but I've been at this for a while now and exhaustion is just turning into frustration.
Thanks for your feedback/help.
Blob backups are incremental. Tar backups are full.
When CWM 6 was released, the devs made blob the default backup format. Later versions changed it back to tar.
You can manually change this setting through the CWM options.
As far as your backups being hosed, its tough to say without having the device in front of me. Are you attempting to restore with the same version that created the backup?
For what it's worth, I mirror your opinion about incremental backups being a terrible idea.
Aerowinder said:
Blob backups are incremental. Tar backups are full.
When CWM 6 was released, the devs made blob the default backup format. Later versions changed it back to tar.
You can manually change this setting through the CWM options.
As far as your backups being hosed, its tough to say without having the device in front of me. Are you attempting to restore with the same version that created the backup?
For what it's worth, I mirror your opinion about incremental backups being a terrible idea.
Click to expand...
Click to collapse
Thanks; I did try multiple recovery versions including older ones, but the internal memory was wiped since I formatted system so I'm pretty sure everything's gone. Clockwork has been such a useful tool but I really have to wonder what they were thinking when they did this, ugh.
C'est la vie
Basically, TWRP is not seeing all my nandroid backups. I'm not sure what's going on really. I'm on TWRP 2.4.1. Basically, I'm trying to restore to previous state. I forgot to do a Titanium backup of a few items, mainly games, and I need to get back to the phone state so I can TB the games and saves, so I don't have to redo all the work.
This morning, I did a backup of my GN2 (LJC). Was planning on going to 5MA rom and firmware. Before flashing 5MA, I realized I didnt' TB those apps. Went to reboot back into the system, and got an error there was no OS. I didn't try rebooting into recovery; I didn't think of it at the time. So I flashed the 5MA. I figured I could just restore it later. Installed 5MA no problems. Did a nandroid for the 5MA to a working state before I start adding more mods and tweaks.
Before going that, I figure I would do a restore to the LJC. Went to restore, and only listed the 5MA backup. Check on the PC using file explorer and can see the backup for LJC. I did see the LJC only has seven files and the 5MA one has nine. I went into TB and asked it pull from a nandroid, and did list the LJC. It's analysis found no apps. This wouldn't have solved my problem in the end though.
I tried to search to see if anyone had a similar issue, but no luck. I did remind about the TB nandroid thing though. I think TWRP didn't do a correct backup of the LJC, and that's why it's not being listed.
lovekeiiy said:
Basically, TWRP is not seeing all my nandroid backups. I'm not sure what's going on really. I'm on TWRP 2.4.1. Basically, I'm trying to restore to previous state. I forgot to do a Titanium backup of a few items, mainly games, and I need to get back to the phone state so I can TB the games and saves, so I don't have to redo all the work.
This morning, I did a backup of my GN2 (LJC). Was planning on going to 5MA rom and firmware. Before flashing 5MA, I realized I didnt' TB those apps. Went to reboot back into the system, and got an error there was no OS. I didn't try rebooting into recovery; I didn't think of it at the time. So I flashed the 5MA. I figured I could just restore it later. Installed 5MA no problems. Did a nandroid for the 5MA to a working state before I start adding more mods and tweaks.
Before going that, I figure I would do a restore to the LJC. Went to restore, and only listed the 5MA backup. Check on the PC using file explorer and can see the backup for LJC. I did see the LJC only has seven files and the 5MA one has nine. I went into TB and asked it pull from a nandroid, and did list the LJC. It's analysis found no apps. This wouldn't have solved my problem in the end though.
I tried to search to see if anyone had a similar issue, but no luck. I did remind about the TB nandroid thing though. I think TWRP didn't do a correct backup of the LJC, and that's why it's not being listed.
Click to expand...
Click to collapse
Were you on a prior version of twrp before backing up? If so, mine did the same thing. And a bunch of other people too. Their trying to figure it out now but have a work around for now...
Make a new backup. Then copy your old one into the new folder. It should show up now.
Sent from my SPH-L900 using Tapatalk 2
nope, it was the same version of TWRP
Same thing here, it backs it up but does not list it in the backup section. But root explorer shows it.
I've gone from stock to rooted MA5 and then to stock rooted MA7. I'm on TWRP 2.4.1 (or whatever the newest one is) and I can see my backups fine. I haven't tried to restore one though.
HTC One V [CDMA], Virgin Mobile US, original (pre-OTA) radio version, TWRP recovery
Has anyone else experienced flakiness with Nandroid backups on this phone? All of them that I've done with major OS changes—even after factory reset—have failed to produce a working restore even though they were taken from a working state.
I'm also unable to get back my previously-working CM 10.1 ROM even though I followed the exact same procedures (with the same files) that I used to get it working before.
This has been happening since my first failed Nandroid restore trying to go back from CM 10.1 to the HTC Sense Nandroid backup I made before attempting CM 10.1 in the first place. I thought this was due to the Sense Nandroid having been made under the OTA-upgraded radio version (I had to use the stock rom.zip from the RUU to get CM 10.1 working at all), but now I'm not so sure. I get the HTC logo and angry red legal text indefinitely now with those setups.
I can't even get back to the Nandroid I made of the stock HTC Sense ROM right after I restored from the RUU's rom.zip.
Anyone have any idea what I'm doing wrong? Or is this model really just that much of a pain?
Are you flashing the correct kernel in fastboot after completing the restore? The recovery is not able to flash a kernel, that still needs to be done through fastboot, even with a nandroid restore.
riggerman0421 said:
Are you flashing the correct kernel in fastboot after completing the restore? The recovery is not able to flash a kernel, that still needs to be done through fastboot, even with a nandroid restore.
Click to expand...
Click to collapse
That's the boot.img, right? I did try flashing that after the restore didn't work the first time. No joy.
EDIT: Actually, that explains why some of my restores have failed, but not all of them.
EDIT 2: Mystery solved. I think. The Nandroid backup I took yesterday evening must be broken somehow. I noticed a few minutes ago that TWRP wasn't actually telling me that it finished restoring the backup—it was just taking me back to the home screen. I switched to CWM Recovery to grab a backup I took yesterday Morning, and that one worked.
So now I'm just left extremely disconcerted that I can't be certain my backups are reliable.
mynewshiny said:
That's the boot.img, right? I did try flashing that after the restore didn't work the first time. No joy.
EDIT: Actually, that explains why some of my restores have failed, but not all of them.
EDIT 2: Mystery solved. I think. The Nandroid backup I took yesterday evening must be broken somehow. I noticed a few minutes ago that TWRP wasn't actually telling me that it finished restoring the backup—it was just taking me back to the home screen. I switched to CWM Recovery to grab a backup I took yesterday Morning, and that one worked.
So now I'm just left extremely disconcerted that I can't be certain my backups are reliable.
Click to expand...
Click to collapse
I originally thought this was just an isolated incident, but it seems to be recurring. Several of the Nandroid backups I've made more recently, both within TWRP Recovery and via the Online Nandroid Backup app, seem to produce this result. (Fortunately, I have a known good backup that I've been able to use reliably.)
Is there a way to validate a Nandroid backup other than trying to restore from it? I don't mean comparing a hash (which is what I find using Google), but rather making sure that the original, uncorrupted file is valid for use as a backup.
As a side note, every backup I've done with CWM Recovery has been reliable, so my fallback plan is to switch to CWM. I just find TWRP easier to navigate.
mynewshiny said:
I originally thought this was just an isolated incident, but it seems to be recurring. Several of the Nandroid backups I've made more recently, both within TWRP Recovery and via the Online Nandroid Backup app, seem to produce this result. (Fortunately, I have a known good backup that I've been able to use reliably.)
Is there a way to validate a Nandroid backup other than trying to restore from it? I don't mean comparing a hash (which is what I find using Google), but rather making sure that the original, uncorrupted file is valid for use as a backup.
As a side note, every backup I've done with CWM Recovery has been reliable, so my fallback plan is to switch to CWM. I just find TWRP easier to navigate.
Click to expand...
Click to collapse
I've played with recovery files before (se my signature) when cwm wasn't working well.
Basicly if you want to know that the backup is correct, you can only compare the hash codes (nandroid.md5) which is practically useless, because hases are made only for the .img files, so the OS itself is not protected like this, which is somehow ok, because the files are compressed to a .tar file, which also means it has it's own validation algorithms itself. So you can validate it if you can decompress the file (don't ask that how it could be done under windows) without errors, it should be allright.
I personnaly can say only this: use CWM 6. i-don't-know-which version (which is online now). There is a possibility for cache not mounting, and of course a backup to not be full, but as you can see from my signature, it can be "bypassed" so the OS will be backed up, and because we don't have S-OFF, it doesn't really matters. All of my backups from CWM is working (have at least 10 gigs at the time, from stock to EV).
I always use android file verifier by scary Allen (free market download). It has saved me many times!
Sent from my HTC One V using xda app-developers app
so as a conclusion, nandroid backup won't restore boot image? and the option in cwm advance restore>restore boot is useless? Me also always got stuck using nandroid restore
Ken-Shi_Kun said:
I've played with recovery files before (se my signature) when cwm wasn't working well.
Basicly if you want to know that the backup is correct, you can only compare the hash codes (nandroid.md5) which is practically useless, because hases are made only for the .img files, so the OS itself is not protected like this, which is somehow ok, because the files are compressed to a .tar file, which also means it has it's own validation algorithms itself. So you can validate it if you can decompress the file (don't ask that how it could be done under windows) without errors, it should be allright.
I personnaly can say only this: use CWM 6. i-don't-know-which version (which is online now). There is a possibility for cache not mounting, and of course a backup to not be full, but as you can see from my signature, it can be "bypassed" so the OS will be backed up, and because we don't have S-OFF, it doesn't really matters. All of my backups from CWM is working (have at least 10 gigs at the time, from stock to EV).
Click to expand...
Click to collapse
sellersj27 said:
I always use android file verifier by scary Allen (free market download). It has saved me many times!
Sent from my HTC One V using xda app-developers app
Click to expand...
Click to collapse
Confirmed that comparing file hashes isn't helpful for this purpose—I just downloaded scaryalienware's AFV as suggested and ran it against several of my Nandroid backups. It said all of them succeeded, including at least one of which I know will not restore successfully. However, of interest is the fact that it took about half as much time to scan the known "bad" one, and further analysis shows that it's about half the size of the others. I'll have to make some more backups via the various mechanisms to confirm that the size is an indicator; it may be simply that I had fewer apps installed when making those backups.
Too bad there isn't some kind of Nandroid Restore Simulator. But even if there was, this phone probably wouldn't have enough memory to use it. Checking Nandroid backups in a VM would be awesome though!