Has anyone had CWM totally screw up backup/restore process? - Epic 4G General

I backed up my Olympus ROM instance so I could test out the new Hurricane ROM, but now when I go to restore, it is a completely screwed up backup apparently. The background is totally wrong, and whenever I unlock the phone I get SetupWizard FCes, and a completely black and inoperable home screen. Looks like I totally lost my backup that I just made this morning before installing the new ROM.
Has this happened to anyone else?

algorhythm said:
I backed up my Olympus ROM instance so I could test out the new Hurricane ROM, but now when I go to restore, it is a completely screwed up backup apparently. The background is totally wrong, and whenever I unlock the phone I get SetupWizard FCes, and a completely black and inoperable home screen. Looks like I totally lost my backup that I just made this morning before installing the new ROM.
Has this happened to anyone else?
Click to expand...
Click to collapse
Wipe everything 3x and do the restore again. That should work, unless somehow the backup is corrupt although I have never seen that happen.

crawrj said:
Wipe everything 3x and do the restore again. That should work, unless somehow the backup is corrupt although I have never seen that happen.
Click to expand...
Click to collapse
Tried wiping cache, data and dalvik 3 times. Still same thing. Funny, I rebooted after getting the SetupWizard FC and I get the normal loading screen, but I can actually turn the screen off with the power button and see the CRT Off animation, but when I turn it back on I still just see the loading screen and it just sits there.
Guess it's corrupt Oh well.

algorhythm said:
Tried wiping cache, data and dalvik 3 times. Still same thing. Funny, I rebooted after getting the SetupWizard FC and I get the normal loading screen, but I can actually turn the screen off with the power button and see the CRT Off animation, but when I turn it back on I still just see the loading screen and it just sits there.
Guess it's corrupt Oh well.
Click to expand...
Click to collapse
Try wiping than flashing Olympus and than restore data only.
The data's part of the backup may not be corrupted.
Sent from my SPH-D700 using XDA App

Now that someone made this thread, I'll take the time and explain my issue, I have an MD5 mismatch for all 3 backups I made in the past. I know how it mismatched as well, I renamed the backups to something that actually made sense,like Eclair, EC05, & EG22, problem is, tried restoring any of them, I get mismatch, also, advanced restore also says MD5 mismatch.
P.S. To whoever made clockwork mod, you need to add the option to override the MD5 Mismatch, and also, why use MD5? Its an outdated form of Checking for the Integrity of files, there are newer methods.

I had some trouble with a backup once it turned out that my SD card was too full to create the full backup file.

counterfeit187 said:
I had some trouble with a backup once it turned out that my SD card was too full to create the full backup file.
Click to expand...
Click to collapse
Seems like that was it. Had 0 space once I booted to a new ROM.
Thanks

it would be nice if there was a way to pick the name of your backup instead of it auto generating by time/date..

Related

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.

Gingerbread Backups - Unreliable?

Okay, I'm about to SBF my phone, which is a major PITA. So I thought I should caution other members. I was on the Rooted/DeOdex'd Gingerbread release with the ALPHA1 theme and wanted to try out RubixBlurryBread. Rubix install went fine, and booted no problem. It didn't seem like an improvement over the original leak, and actually ran slower on my phone. I thought "No biggie, I made a backup before flashing Rubix"...... wrong. I restored my backup and everything went as it always does with a backup, until the bootup. It's a backup, a 1-to-1 match of how my phone was just 30 minutes earlier, this can't be happening, but I'm stuck in a boot loop. So, even though I hate the idea, I formatted the Data and Cache. Still boot looping. Grrr... Did factory reset from standard recovery, no help. Wiped Data/Cache and reinstalled the original DeOdex'd zip from TBH.. nothing is working, everything results in a boot loop.
Anyone have any insight on this? I really don't want to have to set everything up again. I'm going to SBF, but not going to set everything up again, until I know for sure that my backup is useless, for whatever reason.
raziel36 said:
Okay, I'm about to SBF my phone, which is a major PITA. So I thought I should caution other members. I was on the Rooted/DeOdex'd Gingerbread release with the ALPHA1 theme and wanted to try out RubixBlurryBread. Rubix install went fine, and booted no problem. It didn't seem like an improvement over the original leak, and actually ran slower on my phone. I thought "No biggie, I made a backup before flashing Rubix"...... wrong. I restored my backup and everything went as it always does with a backup, until the bootup. It's a backup, a 1-to-1 match of how my phone was just 30 minutes earlier, this can't be happening, but I'm stuck in a boot loop. So, even though I hate the idea, I formatted the Data and Cache. Still boot looping. Grrr... Did factory reset from standard recovery, no help. Wiped Data/Cache and reinstalled the original DeOdex'd zip from TBH.. nothing is working, everything results in a boot loop.
Anyone have any insight on this? I really don't want to have to set everything up again. I'm going to SBF, but not going to set everything up again, until I know for sure that my backup is useless, for whatever reason.
Click to expand...
Click to collapse
just SBF, reroot, and reflash the GB leak
boot into the GB leaked than boot into recovery again
than advance restore data only
if this doesnt work than your back to square 1 with your data
raziel36 said:
Okay, I'm about to SBF my phone, which is a major PITA. So I thought I should caution other members. I was on the Rooted/DeOdex'd Gingerbread release with the ALPHA1 theme and wanted to try out RubixBlurryBread. Rubix install went fine, and booted no problem. It didn't seem like an improvement over the original leak, and actually ran slower on my phone. I thought "No biggie, I made a backup before flashing Rubix"...... wrong. I restored my backup and everything went as it always does with a backup, until the bootup. It's a backup, a 1-to-1 match of how my phone was just 30 minutes earlier, this can't be happening, but I'm stuck in a boot loop. So, even though I hate the idea, I formatted the Data and Cache. Still boot looping. Grrr... Did factory reset from standard recovery, no help. Wiped Data/Cache and reinstalled the original DeOdex'd zip from TBH.. nothing is working, everything results in a boot loop.
Anyone have any insight on this? I really don't want to have to set everything up again. I'm going to SBF, but not going to set everything up again, until I know for sure that my backup is useless, for whatever reason.
Click to expand...
Click to collapse
You have to install the rooted version first then install the deodexed zip because I believe the deodexed zip only changes some system files, I did the same thing by mistake. So unfortunately you will have to SBF but when you get back up and running just remember to flash the root only zip first then boot into recovery and you can then flash the deodexed zip, hope this helps
luigi90210 said:
just SBF, reroot, and reflash the GB leak
boot into the GB leaked than boot into recovery again
than advance restore data only
if this doesnt work than your back to square 1 with your data
Click to expand...
Click to collapse
This is what I did last night, just before going to sleep. Thankfully, it worked, so only thing I had to really do was re-apply the theme and 180 LCD Density. Cool that we had the same idea but I'm still concerned about the backup not working, because I definitely don't want to make a habit of SBF'ing any time I don't like a new ROM, though I'm probably going to wait for LibertyGB before I flash another, and I'm fairly certain I will like that one
Thanks for taking the time to read and comment, really appreciate it.
I tried to go back to my stock bg backup also. It went ok and started up but I got force close on all my blur apps. I couldn't get the fc's to stop so I also had to sbf and reload everything.

Lots of FC's after restore using CWM

First question: I notice that a fair % of the time when I try to do a restore from CWM, it tells me there's a MD5 mismatch. Is this just a symptom of a bad SD card -- that the backup did not save properly to the card?
Since it's no good to find out the backup is bad when I actually need it, I came up with a work-around, which was to try and immediately restore from the backup immediately after making it. If it gives me an MD5 error, then I make a new backup. Eventually I don't get an MD5 error and the restore works, and in theory it should be restoring the phone to the state it was in just a few minutes earlier -- i.e. nothing is changed.
However, after a successful restore and reboot, I tend to get a slew of FC's at startup from background apps. I'm wondering what I'm doing wrong -- is there some extra step I need to do after a restore using CWM?
Sounds like when you backd up you had some data issues that are being restored too your phone each time you restore. Bite the bullett reflash your rom don't restore. But before you do that try fixing permissions in cwm.
I would clear cache and dalvik before doing the backup...
Sent from my SPH-D700 using XDA App
If you're using SRF, just reflash srf 1.1.1 right over it. It will repair your framework but save your personal data.
MD5 bmismatch is a result of renaming backups incorrectly or using ROM manager or Quick Boot to get into recovery. ONLY use 3 finger method.
Did not know that. You get a thanks.
I tried clearing cache and davik cache before backup. When I restored, it gave me a FC on Google framework or whatever that's called. I rebooted and did another restore from the same backup, then cleared cache and dalvik cache before rebooting, and that time it booted with no FC's.
kennyglass123 said:
MD5 bmismatch is a result of renaming backups incorrectly or using ROM manager or Quick Boot to get into recovery. ONLY use 3 finger method.
Click to expand...
Click to collapse
Is "quick boot" when you don't power-down and then power-up with 3-fingers, but just do the 4-finger reboot? That would make sense that it would be causing the MD5 problem... good to know. Is that also what's causing the FC's when I restore?
Nerva said:
I tried clearing cache and davik cache before backup. When I restored, it gave me a FC on Google framework or whatever that's called. I rebooted and did another restore from the same backup, then cleared cache and dalvik cache before rebooting, and that time it booted with no FC's.
Is "quick boot" when you don't power-down and then power-up with 3-fingers, but just do the 4-finger reboot? That would make sense that it would be causing the MD5 problem... good to know. Is that also what's causing the FC's when I restore?
Click to expand...
Click to collapse
if you arent properly shutting down you will almost always get FCs on reboot if you have a no journal rom...
Wow, I had no idea that was an issue (I'm quite new to Android and was thinking of the phone as being more like a digital watch than a personal computer). Will pulling the battery cause the same problems?
How do I fix the FC problems when that happens?
ummmm
Nerva said:
Wow, I had no idea that was an issue (I'm quite new to Android and was thinking of the phone as being more like a digital watch than a personal computer). Will pulling the battery cause the same problems?
How do I fix the FC problems when that happens?
Click to expand...
Click to collapse
that would be not shutting down properly like pulling the power cable out of your comp and turn it back on not goood to do alot wil be ok in light doses
Corrupt data is 100% the cause. The only problem now is trying to determine where the problem came from. It can be from many things, but to be safe, i'd reformat the SD card (backup all ur data first on a computer). And recreate a backup from the rom previously. I use "my backup root" from the market and it works like a charm when switching from rom to rom.
Sent from my SPH-D700 using XDA Premium App
yep
i use the very same thing........... i read that somewhere lol
Nerva said:
I tried clearing cache and davik cache before backup. When I restored, it gave me a FC on Google framework or whatever that's called. I rebooted and did another restore from the same backup, then cleared cache and dalvik cache before rebooting, and that time it booted with no FC's.
Is "quick boot" when you don't power-down and then power-up with 3-fingers, but just do the 4-finger reboot? That would make sense that it would be causing the MD5 problem... good to know. Is that also what's causing the FC's when I restore?
Click to expand...
Click to collapse
The 4 finger will cause corruption on ROMs without journaling, so yes. There is also a Quick Boot app that boots into recovery, same thing can happen. So for backups and restores, always power down then 3 finger into CWM.

Backup restore problem

Hi all... tonight I decided to try the Samurai kernel. Unfortunately, it boot-looped on me. No big deal I figured, I did a full nandroid before in ACS's CWM, so I'll just restore. Unortunately, doing so isn't working: all of my apps, data and settings are gone! It basically looks stock (although, interestingly, all the Sprint bloat I had manually removed before still seems to be gone, so the restore worked to a degree)... I've restored backups before and never had a problem so I'm guessing the kernel is somehow the culprit, but I think that got restored from the backup too so I don't know what's going on. I'm stock EI22 by the way.
Can anyone help me? I'm pretty frustrated at the moment.
Thanks,
Frank
Try restoring an older backup. If that works you can attempt an advanced restore data only from your recent backup to see if it was something in your setup.
Sent from my SPH-D700 using XDA App
That was a thought I had too... I tried TWO older backups that I still had, same problem. I also tried a factory reset and then a restore (in theory it shouldn't make any difference to factory wipe first, and sure enough it didn't, but figured it was worth a shot).
My only other thought is maybe if I odin back to stock, root & install recovery and then try the restore again... kind of a shot in the dark, really shouldn't matter, but maybe.
Did you clear cache and dalvik before flashing the new kernel? I wonder if ACS is the issue and if trying CWM 5 might help.
DroidApprentice said:
Did you clear cache and dalvik before flashing the new kernel? I wonder if ACS is the issue and if trying CWM 5 might help.
Click to expand...
Click to collapse
I was thinking the same thing D. The only other thing I can think of is bad reads from the sd card.

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...

Categories

Resources