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
Related
My refurb Incredible has arrived, and while I continue to hope that I can RUU the old one to wipe the root, I have to think about how to get the new one up to speed.
My old incredible had a habit of starting to super heat (possibly reception issues, possibly something else) and when it got to 109, it would just reboot and reboot and reboot (4-13 times). It also had a spontaneous reboot issue (separate and apart from heat), and it was VERY difficult to get into recovery (it would go to HBOOT just fine, but if you scrolled to recovery, it would reboot twice, the second being a full normal reboot).
SO I wanted to see if anyone out there with knowledge thought if I should just un-titanium to reinstall apps, in case there was some deeper problem; or if I should just nandroid and be back 100% instantly. What I don't want is to bring back a problem to the new phone, which may have been software related on the old.
Any thoughts?
ruu the old, nandroid the new.
Sent from my Incredible using XDA App
Ummm
Will nandroid also overwrite the recovery? I suspect a bad recovery flash on my old may also be part of the problem ... I *really* don't want to reintroduce an old problem onto my new phone, despite how great it would be just to nandroid restore and be done with it.
jdmba said:
Will nandroid also overwrite the recovery? I suspect a bad recovery flash on my old may also be part of the problem ... I *really* don't want to reintroduce an old problem onto my new phone, despite how great it would be just to nandroid restore and be done with it.
Click to expand...
Click to collapse
i would nandroid, reboot, and flash unrevoked3 again. if it was a bad recovery, flashing unrevoked3 after nandroiding, than that should overwright the recovery
Sent from my Incredible using XDA App
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.
Hey guys so I have a weird problem.
I can't restore my new backups.
That means all backups I did 2 weeks ago are restorable but now, when I do a backup of my current cyanogenmod rom and try to restore it, I get stuck at the HTC boot screen.
I heard it's because I used rom manager and sometimes rom manager destroys the PC10IMG, is that true??
Same thing happened to me. I had to do everything all over again. It will be nice if there is some more information about the problem. Thank you.
whitis said:
Hey guys so I have a weird problem.
I can't restore my new backups.
That means all backups I did 2 weeks ago are restorable but now, when I do a backup of my current cyanogenmod rom and try to restore it, I get stuck at the HTC boot screen.
I heard it's because I used rom manager and sometimes rom manager destroys the PC10IMG, is that true??
Click to expand...
Click to collapse
don't trust rom manager to perform recovery operations through its gui with any consistency.
if you're going to perform a recovery operation, just do it through CWM and save the hassle.
Well I did it all /backups & recovery/ through CWM and just hang on the welcome screen. Not that it was important because I only wanted to back up something I forgot after intending of installing a new rom, but still the question remains and it will be helpful for future time
I've found that Nandroid backups are unreliable if I'm at all low on free space on the SD Card. Even if there are no errors during the backup. I make sure I've got at least room for two whole backups now. Seems to solve the problem.
I believe I've had this problem in the past with other android devices but I don't recall how I solved it.
Basically I unlocked, rooted, and flashed CWN using the nexus tool kit (I am very capable of using adb just felt like simplifying). I then made a nandroid backup using the CWM that the tool kit flashed. Later, i updated to CWM touch with Rom manager. I don't think the new CWM caused this but for some reason i am unable to delete that first nandroid i made. I've made other backups since and have had no problem deleting them, it's just this first one that i made that isn't deleting for some reason. Any ideas? It's pretty much just dead weight on my storage at this point.
randroid123 said:
I believe I've had this problem in the past with other android devices but I don't recall how I solved it.
Basically I unlocked, rooted, and flashed CWN using the nexus tool kit (I am very capable of using adb just felt like simplifying). I then made a nandroid backup using the CWM that the tool kit flashed. Later, i updated to CWM touch with Rom manager. I don't think the new CWM caused this but for some reason i am unable to delete that first nandroid i made. I've made other backups since and have had no problem deleting them, it's just this first one that i made that isn't deleting for some reason. Any ideas? It's pretty much just dead weight on my storage at this point.
Click to expand...
Click to collapse
im having the same issue and am working on it right now, will keep ya posted.
edit: i just flashed all the way back to stock and rerooted, started fresh basically. i wonder, can you just partition the "sdcard", effectively erasing the entire clockworkmod folder?
I had that problem and tried root explorer, astro, rom manager to delete the folders and nothing was working until I actually booted CWM and deleted the backup through CWM, it deleted just fine.
SoHaunted said:
I had that problem and tried root explorer, astro, rom manager to delete the folders and nothing was working until I actually booted CWM and deleted the backup through CWM, it deleted just fine.
Click to expand...
Click to collapse
that was my first thought but i wasnt able to locate the option to do so in the version of CWM i was using- honestly i dont recall which it was. now that im on a fresh system though, i think ill switch to TWRP. i use it on my one X and like it just fine.
Ok so after rooting and using Flashify to install Loki'd TWRP 2.3.6.2, I backed up my stock rooted. Then, I wiped and flashed PA 3.99. Other than this phone taking forever to do anything in TWRP, everything seemed fine. I booted into PA, installed my normal software setup, rebooted to recovery, and made a backup.
Now, if I try to restore (either stock rooted or PA, it fails. It says something about unchecking the MD5 verification option, which I have done in the general TWRP settings, as well as making sure it stays unchecked in the restore preferences. Have tried restoring to both stock rooted and PA from both a PA install, and a fresh stock rooted install. Both fail with the same error.
I'm backing up/restoring to/from the internal SD, not an OTG cable. my cable that worked fine for my Note 2 and HTC One does not work with my G2. I have also tried re-flashing TWRP in case it was a bad install or something.
Does anybody have any thoughts/suggestions on what I can do to be able to restore roms? I've never had any issues like this with any other device.
I'm interested in this as well. But honestly I haven't been able to restore a damn backup in quite some time using my Galaxy Nexus using TWRP and CWM. It just seems like it tries to, but fails toward the end.
I did a backup of my stock/unrooted but haven't tried to restore it yet. Have you thought or tried to use one of the GUI Apps from the Play Store that does Restore/Backups? I would also pull those backups off of your phone and onto a PC. You can always copy them back later but I've erased everything using TWRP a few too many times.
I would also suggest trying to use CWM to restore the backups. I've never tried to restore a Nandoid from one recovery using another, but it may work.
Sadly with restore not working, it is kind of scary to even attempt it. I would make sure I have some stock images laying around with the ability to adb push if need be. Keep this updated please with either findings or solutions. If I knew 100% that my Nandroid backup was able to be restored, I would attempt to try some of the custom roms out there.
player911 said:
I'm interested in this as well. But honestly I haven't been able to restore a damn backup in quite some time using my Galaxy Nexus using TWRP and CWM. It just seems like it tries to, but fails toward the end.
I did a backup of my stock/unrooted but haven't tried to restore it yet. Have you thought or tried to use one of the GUI Apps from the Play Store that does Restore/Backups? I would also pull those backups off of your phone and onto a PC. You can always copy them back later but I've erased everything using TWRP a few too many times.
I would also suggest trying to use CWM to restore the backups. I've never tried to restore a Nandoid from one recovery using another, but it may work.
Sadly with restore not working, it is kind of scary to even attempt it. I would make sure I have some stock images laying around with the ability to adb push if need be. Keep this updated please with either findings or solutions. If I knew 100% that my Nandroid backup was able to be restored, I would attempt to try some of the custom roms out there.
Click to expand...
Click to collapse
Thanks for the reply.
I have only tried directly through TWRP. I've been flashing phones and tablets for years, but only using TWRP and CWM. I've been using TWRP lately because it's gui is nicer and until now, I've never run into any problems with it.
And yes, restore not working scares me. I know I can adb stock if I screw things up, but I hope it doesn't come to that. I guess for now I'll keep running stock rooted (despite it's horribly ugly unlock animations) and just wait for official AOKP with 4.4...