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.
Related
Hey all,
When I had my Windows mobile phone, I could use Sprite Backup to make a backup that basically acted as an image that I could store on the SD Card. I could then do anything possible to my phone, and then I could simply restore the image, and it went back to the EXACT state it was when i took the image - registry, ALL apps, messages, icons, etc..., just like a 100% hard drive image.
I have Sprite backup on my Samsung Epic now, and was wondering if it acted the same way?
That is, if I install a custom rom, I would like to be able to factory restore it, then apply the backup to take it back to the exact state it was.
Is this how it works?
Thanks,
Matt!
It's called a nand backup and one of the benefits of rooting
Sent from my SPH-D700 using XDA App
Great,
I'm rooted, so I'll. Check it out....
Thanks!
Get the one click root and recovery. Once you have clockwork mod you can do a full backup. Also you can do an "advanced restore" and just restore your /data.
I have found that sometimes a restore doesn't work correctly and I have to reflash the rom and just restore /data to put my apps and settings back.
A word of warning, sometimes when you flash an old /data to a new rom it causes issues with programs. Personally, I have had very few issues doing it, even when moving between 2.1 and 2.2.1, but ymmv.
Ok so I DLed ROM Manager to my epic and hit "back up ROM". I now have a backup with todays date under the Clockwork mod folder on my SD.
1. Am I all backed up? If wiped phone and re flashed I could get my angry bird levels back?
2. If I switch to a different ROM, can I still use this backup?
3. If I do restore, how do I do it? Thru CWM?
durrett syndrome said:
Ok so I DLed ROM Manager to my epic and hit "back up ROM". I now have a backup with todays date under the Clockwork mod folder on my SD.
1. Am I all backed up? If wiped phone and re flashed I could get my angry bird levels back?
2. If I switch to a different ROM, can I still use this backup?
3. If I do restore, how do I do it? Thru CWM?
Click to expand...
Click to collapse
In my experience with Rom Manager, it doesn't work with the epic.
Backup your apps with Titanium backup.
I suggest doing both rom manager and titanium backup
Just in case.
If you go to a differemt rom you could restore all apps in clockwork by going into advanced restore under cwm and choosing to restore only /data however with some roms that's not recommended and could cause issues. If you restore the whole backup through cwm then it would overwrite whatever rom you have loaded.
With titanium backup you can backup just individual applications and restore their data or data and the app itself so as someone else said above that's your best bet.
Sent from my DROID2 GLOBAL using XDA App
futureprospect said:
In my experience with Rom Manager, it doesn't work with the epic.
Click to expand...
Click to collapse
Backing up with rom manager is literally backing up with clockwork mod. ROM manager just reboots the phone into cwm and makes the backup there. Clockwork mod backups have always worked for me.
When I tried to use ROM Manager it wouldn't work properly. Someone a while ago complained that booting into cwm with the app causes errors. I wouldn't rely on the app at all if I were you.
Sent from my SPH-D700 using XDA App
Manually boot into cwm and backup, the app doesnt work properly. I tried backing up a rom and it said it was backed up after 10 seconds. The rom file was 3 mbs...the backup should be near 100, if not more.
Sent from my SPH-D700 using XDA Premium App
Gotta add my cold water here. ROM manager has been less than useless for me, screwing up things every time I've tried it.
Stick to backing up the entire system from CWM, and a full backup via Titanium to have access to individual apps as needed. This has always worked for me, and many others here.
Sent from my mind using telepathitalk
So if I ODIN my phone with a new modem and flash a completely different rom, I can still restore with a backup made with a different ROM? Thanks.
durrett syndrome said:
So if I ODIN my phone with a new modem and flash a completely different rom, I can still restore with a backup made with a different ROM? Thanks.
Click to expand...
Click to collapse
Technically, yes, but it is not recommended. Restoring data when moving between roms is usually when errors start happening. Also Rom manager does not work with the epic so there is probably no data in the file it created. You would have to boot into clockwork mod and backup from there.or use titanium backup and then restore just the apps when you switch roms.
Sent from my SPH-D700 using XDA App
Just my 2 cents...everyone here keeps saying to use Titanium, give Mybackup Root a try. Its free and has a good UI. Titanium seems to make it more complicated than it needs to be.
Other than that, the other posts here are correct, it doesnt matter what ROM you are running when you make or restore a backup, apps and their data will transfer and restore just fine, BUT like stated by others, system data does not always play well between ROMs and in my opinion you are better off not trying to restore that when you switch between ROMs...has given me more than one headache.
+1 on MyBackup Root. I find it to be more user friendly and just as effective as Titanium as well. I make a backup of everything (apks,data,photos,system settings, etc) at 4am everyday while I'm asleep. I plan on sticking with ACS so this is just a security net since they still do not use journaling. However if I want to try a different rom I can always choose to restore only the apks from the backup file.
The epic has not gotten rom manager support yet so it doesn't work and cwm can fail if you are switching between cm7 and acs cwm will give you a md5 mismatch so I had to re flash acs then restore data. So use titanium to restore apps.
Sent from my SPH-D700 using XDA App
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
I have a T-Mo G2 and want to keep my Froyo image to reinstall later if I cannot get theGingerbread to work right. I want to make an image file that will restore the phone to exactly how it is now. I have tried all kinds of stuff, but am not able to make the "img" file so that I ca do a restore when booting...
Can someone point me to what I need to install to do this, and if possible some directions on what/how to create the "img" or restore file ?
I would be most appreciative, as I had to reverse everything from the OTA of Gingerbread, since too many apps didn't work, ESPECIALLY the GPS!
My current Froyo is a temp-root system.
Thank you all!
Aloha. .
I would do full root via the wiki, and then install 4EXT (the full one that's like $2) - it will keep your old stuff straight
Ditto on previous reply
Root your G2
Backup all your apps with using Titanium backup
Get Clockwork mod ROM manger or 4ext ( I prefer 4ext) and backup your stock rom. You can download new ROM CM7 for first ROM.
If you don't like the ROM you can restore your stock ROM with CWM or 4ext at anytime.
I have a theory that Ti Backup or any backing up of apps is a bad plan. I know you can do it no problem, and that it is a great time saver, but I have a strong feeling that this ultimately results in an unstable phone with mysterious force closes etc.
Even though it's a real pain, I think you are always better off reinstalling your apps from scratch after changing to a new ROM and wiping caches.
WTF? said:
I have a theory that Ti Backup or any backing up of apps is a bad plan. I know you can do it no problem, and that it is a great time saver, but I have a strong feeling that this ultimately results in an unstable phone with mysterious force closes etc.
Even though it's a real pain, I think you are always better off reinstalling your apps from scratch after changing to a new ROM and wiping caches.
Click to expand...
Click to collapse
1. I have had zero problems with TB personally.
2. Without it your app data is gone.
3. Triple wipe, takes a few extra minutes and makes a world of a difference.
4. Do not restore system data!
5. Check md5 sums BEFORE doing anything!!!!
6. Make sure you have a recent nandroid backup and you'll be fine either way.
7. triple wipe before flashing anything including nandroids. Preferably with different wipes aka factory reset, superwipe+ ext4, then recovery wipe!
Just my 2 cents, it's saved my a$$ more then a few times...
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.