Database Users

Why are my Clockworkmod backups unusable?

So, I just rooted my Mytouch 4G a few days ago using the 'Ultimate' guide on this forum. I had root access and I disabled and deleted some stock apps from my phone. I was using LauncherPro instead of the HTC Sense launcher. I made a backup in Clockworkmod recovery immediately after installing Clockworkmod, before I'd made any major changes.
So, I spent the past few days removing and tweaking things. I had my phone working extremely well. But then I realized that I actually wanted an .apk file (the stock visual voicemail app) that I'd already deleted from the phone. It should be in my original backup file, right? So I figured that I'd make a new backup, restore my old backup containing the .apk file, copy the .apk file off of the phone, then restore my recent backup. Well...this didn't work.
When I restored either the original backup or the more recent backup, the phone would boot up and I'd get a message that the System UIDs are inconsistent. The phone would let me make phone calls, but 95% of my apps were missing from the loader. Most of the icons on my home screens were grayed out and would tell me the applications were missing when I tried to click on them.
I tried Fix Permissions in Clockworkmod recovery, but it didn't help. My Android Market app and all of my file manager apps didn't work, so I couldn't reinstall any apps. When I'd wipe all the data on my phone, but only restore the System backup, the Android Market would work and the phone basically returns to stock. But as soon as I restore my Data backup, everything breaks.
At this point, I've already wiped the phone and started over from scratch, but I'm afraid to rely on Clockworkmod/Rom Manager for backups again. Any ideas what went wrong?

did you flash a different kernel? this may be the issue, as I know that for other devices CWM does not restore the kernel.

this happens when your backups/card gets corrupted... it could of been a number of things... changing the name of something to how much you scan the card... hard to say exactly what caused it... If your really worried about it I would suggest making a backup of your backup on your computer just to be safe...

Hmm. Mine does.
mr.tenuki said:
did you flash a different kernel? this may be the issue, as I know that for other devices CWM does not restore the kernel.
Click to expand...
Click to collapse
Sent from my stickie key HTC Glacier using XDA App

I did make a backup of my backup, but it's not like these backups sat on the memory card for months before they got used. I ran the restore within minutes of when I made the last backup. Besides, aren't the backups hashed with md5 and then retested before restoring? So, if the files did get corrupted, I would think Clockworkmod would have notified me, no?
I just wish that after making a backup, there was some way to test it out without taking the chance of trashing my phone.
Regarding using a different kernel, I did not. I did not flash any experimental/downloaded images, these were simple backups and restores of my existing phone data.

mr.tenuki said:
did you flash a different kernel? this may be the issue, as I know that for other devices CWM does not restore the kernel.
Click to expand...
Click to collapse
This is for phones that dont support Nand like the vibrant. HTC phones is a full backup including kernel.

sundayhustler said:
I did make a backup of my backup, but it's not like these backups sat on the memory card for months before they got used. I ran the restore within minutes of when I made the last backup. Besides, aren't the backups hashed with md5 and then retested before restoring? So, if the files did get corrupted, I would think Clockworkmod would have notified me, no?
I just wish that after making a backup, there was some way to test it out without taking the chance of trashing my phone.
Regarding using a different kernel, I did not. I did not flash any experimental/downloaded images, these were simple backups and restores of my existing phone data.
Click to expand...
Click to collapse
Your right, CWM does do a md5 check when restoring. I'm sorry, I don't know what could be wrong. I currently have like 5 backups of 4 ROMS and have to restored to just to play around. Did you do apps2sd? This can cause major issues when switching ROM's.

I am also having a problem restoring to my stock rom. how big does my backup file have to be?

I have had this problem before. I think in my case my issue was caused by and incompatible version of CWM. I found that to be safe, I usually make two back ups, one with recovery in 2.5.12 and one with 3.0.0.6.

It was the file. It was only 60mb, apparently I ran out of memory thanks though my other backups work fine and I found the stock rom on a thread.
Sent from my HTC Glacier using XDA App

oh haha i was about to post.

Nandroid Restore - Stuck on HTC screen

Hello all,
I tried to restore a nandroid backup via Clockwork recovery, at the end I got a E:Error in CACHE:recovery/log (No space left on device) message. After restart I am stuck at the htc screen (green letters on white screen). Any solutions please?
Thank you.

That's almost the exact same thing that happened to me after a nandroid restore, it just hung on that HTC screen forever. I'm not sure what the problem was in my case, but restoring an earlier backup worked for me so it's possible that the backup that I was trying to restore was somehow corrupted.. could be the same with yours.

try doing an advanced restore then restore everything EXCEPT sd-ext. had a similar problem too. checked my sd-ext after restore (full, not advanced). got nothing on it except folders with no files on each whatsoever. my phone still bootloops. maybe some of the great devs here could shed some light.
doing the advanced restore thingy though always works for me. HTH

I still get this and was wondering if there was a solution

This is a problem I've only heard of on backing up with different versions of CWM. Try checking into that.
Sent from my HTC Legend using XDA App

How would I get a different version of CWM then? Cuz I can't get pass the HTC splash screen.

Happened to me, too.
I don't know what else to do but load a different nandroid.
Now, I'm trying to load my first nandroid (because my sms messages are HORRIBLY late).
NO. GO.
Is it because of the lack of space on my microsd card? Possibly related? Also, what the heck is taking up all the damn space on an 8 gig card?! I deleted almost all my photos. Is it nandroid backups?
HERO CDMA

I have enough space on my SD card cuz I have 32gigs and only use about 10gigs. I was told that there were issues with 5.0.x.x versions of clockworkmod......

Help with CWM Restore!

Hi,
Sorry if this has been answered already but I did search the forum and couldn't find an answer.
So 2 days ago I got into flashing my Sam GS2, I followed the instructions completely, I made a NAND backup of my current ROM.
I used ROM manager to install Cyanogen nightly ROM build 75, which I liked a lot but the camera didn't work and realised after it was a test build, so decided to go back to my current ROM. I went into CWM recovery and restored, within 5 mins I was back to like nothing happened.
I then download VillanROM 3.0, again a few bugs so I decided install TK ROM 3.6 I never restored to backup this time as I thought that wasn't necessary, but when I now restore my backup through CWM I get my settings but not my data?
Why is this? The backup file is still there and the same size as before, have I done something wrong?
The reason why I restored was after finding that TK ROM was a stable ROM I forgot to back up my GO SMS settings and Smart keyboard pro settings so I wanted to back up to SD card, re-install the apps and then just restore the settings, now it looks like I won't be able too.
Any help would be appreciated.
Thanks in advance.

Well 64 views but no replies???
Someone must have an answer!!!

maverick1103 said:
Well 64 views but no replies???
Someone must have an answer!!!
Click to expand...
Click to collapse
Me for one fails to understand the problem .
jje

Well short version.
I did a NAND backup so I could go back to original ROM just incase things went pair shaped, I managed to restore to it after first flash, then on the 3rd time after realising that I forgot to back up certain app settings, I restored the NAND it does it reboots but only with settings and nothing else.
Can you help?

A failed nandroid restore looks to be a corrupt backup .
jje

Well I thought as much, thought I was doing something wrong.
Just have make sure I do 2 backups next time.
Thanks for the reply.

Corrupt Nandroid Backup

I ran a custom ROM today (10-13-2011) and wasn't completely satisfied, so I tried to flash back to my last working nandroid backup that I had created earlier this morning. Unfortunately, it got stuck while loading one particular file. After several battery pulls and several attempts at installation I ended up flashing a nandroid I had created 4 days ago (10-08-2011). This flash was successful which indicates to me that clockworkmod rom manager must have created a corrupt nandroid when I made one this morning. This is a bit disturbing to me bc I have OCD and now I'll be wondering if the nandroid backups I make from here on out are jacked up. Do you guys know why this may have happened? Or do you know a way to tell whether or not a nandroid is corrupt (before trying to flash it)? Should I be concerned with any of this at all?
Sent from my DROIDX using XDA App

Don't know why this happens, but it has happened a few times to me
Sent from my DROIDX using XDA App

It doesn't happen to you every time does it?

How long was it stick on a certain file? Mine sometimes seems to get hung up, but will continue after a minute or two...

It was hung up on that one file for like 5-10 minutes. When I flashed the older backup I didn't have that issue though.
Sent from my DROIDX using XDA App

Update: About a week ago I had this same issue again. I made another nandroid backup, tried to flash it, and discovered it was corrupted and had to (yet again) flash back to that backup I made on 10-08-2011. Today (10-31-2011) I tried to make a backup and it actually successfully flashed after install. I was happy to see that happen....however I'm still disturbed by the inconsistancy I'm now experiencing with Clockwork Mod ROM Manager. Do you guys have any explaination for why I may be having these inconsistent issues?
Sent from my DROIDX using XDA App

I'm just like you with the OCD about this...but I've luckily never had it happen to me.
I'm probably wrong on this, but it seems to me that these issues mostly started sprouting up on the 5.0.2.0(that's right, isn't it?) build.
What I've always done since hearing about this the first time is create a backup...and then restore the backup without even leaving cwm.
That way if MD5's don't match...(hopefully just that) I know it right away.
And if it fails on a single file...I can hope that it isn't a crucial file and my phone will still boot.
It gives me a little blanket of trust in my nandroid, at least.

I too must report many recent problems with nandroid backups (using CWM 5.0.2).
I take a full backup every week or so, as well as before doing something like changing a ROM. A couple of the backups are stored on my SD card, but the rest I push up to my NAS via FTP (to keep a longer history).
Yesterday I went to go back to a point in time only to find out that the backup didn't work (failed MD5 checksum). I managed to get a recent backup restored, but it had something broken in it, so I opted for a fully working backup. I ended up going through ALL of the nandroid backups that I've taken since getting my phone, and none of them work anymore!!! (even the broken one that did manage to restore once yesterday).
This is super weird, as I know that some of these backups were good as I have already restored them successfully!
I can't help but wonder if my file transfer method is playing a role here. First I was using FTP over WiFi, but then I switched to USB cable to PC as Flash drive -> NAS via wired Ethernet.
Whatever is going on here... it is really a serious problem. If you can't count on a full system backup like this, then there is really no point to it.
geva

Restoring CWM backup leads to splash loop

I'm using: NexusHD2-ICS-4.0.4-CM9-HWA V2.4
Something went wrong on my phone so I decided to restore a backup. I had one from 2 weeks ago. After the restore completed, I rebooted my phone. It was stuck on the ROM splash screen and never got past that. I left it running for 20 minutes. I tried clearing /cache and dalvik-cache, with no luck. If I format /data then it works, but then of course all my data is gone.
Luckily I had a previous backup which did work.
I'm nervous about nandroid backup/restore. Can I trust it? It only happened for this particular backup, but why would it happen at all? There were no MD5 sum errors at all.
Any advice would be useful.

frostinide said:
I'm using: NexusHD2-ICS-4.0.4-CM9-HWA V2.4
Something went wrong on my phone so I decided to restore a backup. I had one from 2 weeks ago. After the restore completed, I rebooted my phone. It was stuck on the ROM splash screen and never got past that. I left it running for 20 minutes. I tried clearing /cache and dalvik-cache, with no luck. If I format /data then it works, but then of course all my data is gone.
Luckily I had a previous backup which did work.
I'm nervous about nandroid backup/restore. Can I trust it? It only happened for this particular backup, but why would it happen at all? There were no MD5 sum errors at all.
Any advice would be useful.
Click to expand...
Click to collapse
I've had an issue only once with CWM backup where my data from the ROM was lost but the ROM itself flashed fine. I suspect though that I actually had to reboot a few times more before giving up so quickly, because somehow the wallpaper was still kept and I've found on occasion that my data from a ROM restore/update slowly comes back after a few reboots. Anyway, as for your issue, did you change partition sizes between the time you made a backup and when you tried to restore it? I'm using NexusHD2 and I know that the required partition sizes have changed quite a lot between the ROMs.

Nigeldg said:
I've had an issue only once with CWM backup where my data from the ROM was lost but the ROM itself flashed fine. I suspect though that I actually had to reboot a few times more before giving up so quickly, because somehow the wallpaper was still kept and I've found on occasion that my data from a ROM restore/update slowly comes back after a few reboots. Anyway, as for your issue, did you change partition sizes between the time you made a backup and when you tried to restore it? I'm using NexusHD2 and I know that the required partition sizes have changed quite a lot between the ROMs.
Click to expand...
Click to collapse
I did not change the partition size at all. The backup before this one worked fine, so it can't be that. I also just did a new backup of today, and restored it. It worked at the first boot and didn't take extra time. I then tried restoring the broken backup again but ONLY data, and again I got a splash screen loop. I doubt multiple reboots will help, but I did try that.
I have an urge to mount the data backup and slowly take out folders until I find out the cause. If not for anything else, just out of my own curiosity.

Nigeldg said:
I've had an issue only once with CWM backup where my data from the ROM was lost but the ROM itself flashed fine. I suspect though that I actually had to reboot a few times more before giving up so quickly, because somehow the wallpaper was still kept and I've found on occasion that my data from a ROM restore/update slowly comes back after a few reboots. Anyway, as for your issue, did you change partition sizes between the time you made a backup and when you tried to restore it? I'm using NexusHD2 and I know that the required partition sizes have changed quite a lot between the ROMs.
Click to expand...
Click to collapse
I am facing exactly the same problems...
In same cases i got bootloops when restoring a Backup, in other cases i can boot after restoring but then my data is gone and i am asked to configurate my phone again with the wizard...
I never tried to boot several times if the data comes after some tries...
Btw I also didn't change the partitions...is it possible that it has something 2 do with link2sd?

In that case (@OP) I'm guessing its just a broken backup. This is why I always use Titanium as well. It takes up less space and you can restore it on almost any ROM.
Sent from my NexusHD2

Are you using an A2SD script? or do you have an ext partition?
You may have resized it, you can also try formatting it.

Nigeldg said:
I've had an issue only once with CWM backup where my data from the ROM was lost but the ROM itself flashed fine. I suspect though that I actually had to reboot a few times more before giving up so quickly, because somehow the wallpaper was still kept and I've found on occasion that my data from a ROM restore/update slowly comes back after a few reboots. Anyway, as for your issue, did you change partition sizes between the time you made a backup and when you tried to restore it? I'm using NexusHD2 and I know that the required partition sizes have changed quite a lot between the ROMs.
Click to expand...
Click to collapse
Marvlesz said:
Are you using an A2SD script? or do you have an ext partition?
You may have resized it, you can also try formatting it.
Click to expand...
Click to collapse
I use Link2SD, i have ext4....i didn't change anything in the SD Card Layout since first install of the Rom and updated several times without any problem...