Related
Quick and to the point:
1. Is a clockwork backup a full image of the system, such that if I restore from it no matter what kernel, rom, mod, etc. I've installed, I get exactly the completely system and state that I had when I made the backup? I.e., it is a true failsafe against messing up the phone, so long as CWR will boot and the SD card is intact?
2. A complete backup with Titanium, backing up all apps and system data, is a migration path for trying a new ROM? IOW, I can simply do a complete backup with Titanium, wipe wipe wipe, install the target ROM, then restore "missing apps and data" from Titanium and -- voila! I'm on the new ROM, but with all my apps, configuration, etc. I had before?
I'm getting ready to try out the Syndicate ROM...
dwallersv said:
Quick and to the point:
1. Is a clockwork backup a full image of the system, such that if I restore from it no matter what kernel, rom, mod, etc. I've installed, I get exactly the completely system and state that I had when I made the backup? I.e., it is a true failsafe against messing up the phone, so long as CWR will boot and the SD card is intact?
2. A complete backup with Titanium, backing up all apps and system data, is a migration path for trying a new ROM? IOW, I can simply do a complete backup with Titanium, wipe wipe wipe, install the target ROM, then restore "missing apps and data" from Titanium and -- voila! I'm on the new ROM, but with all my apps, configuration, etc. I had before?
I'm getting ready to try out the Syndicate ROM...
Click to expand...
Click to collapse
Ha! I am searching now for the exact same question! I am looking to try the Epic Experience. I will follow this thread to see what the answer is.
Thanks.
First off might I comment that Syndicate Rom is a great choice. Not just saying that cause any of them are my buddies either, cause IDK Any of them... so far though Running Syndicate Rom/Kernel with SetCPU at 200-1200 has been the smoothest Rom experience I have had up to date.
1. Is a clockwork backup a full image of the system, such that if I restore from it no matter what kernel, rom, mod, etc. I've installed, I get exactly the completely system and state that I had when I made the backup? I.e., it is a true failsafe against messing up the phone, so long as CWR will boot and the SD card is intact?
Click to expand...
Click to collapse
Yes in theory it is a backup of everything, data, apps installed, boot, system, literally the entire phone is backed up. Is it a failsafe though? I would rather say not. On some phones we can restore a clockwork recovery and have no issues, but since I've had my epic and switched around with different Roms, I've noticed that restore dosen't work quite as it should, probably because Roms are so much different, and you run into FC's, boot loops, and other issues... Restoring peices in advanced restore works well but a complete restore almost always has bugs.
True statement though that even if you screw up and get a boot loop, or constant force closes/phone restarts, as long as you can get back into clockwork your phone is not screwed. You were right on that one. So no worries if you wanna test and play.
2. A complete backup with Titanium, backing up all apps and system data, is a migration path for trying a new ROM? IOW, I can simply do a complete backup with Titanium, wipe wipe wipe, install the target ROM, then restore "missing apps and data" from Titanium and -- voila! I'm on the new ROM, but with all my apps, configuration, etc. I had before?
Click to expand...
Click to collapse
You have the idea right. You really don't even need to back all your apps up with titanium anymore these days, though, it too is plagued with FC's and problems. If you are using clockwork recovery, and you have made a backup already... all you have to do when installing a NEW rom is first wipe-fest, then let it boot once, then restart, go to clockwork, go to Advanced Restore, and ONLY restore the DATA part. (Reason for this is if you restore Boot, System, etc it will try to restore the Rom you just installed... Data is where all your apps/settings are at) This will do exactly the same thing as titanium backup will do, only with less bugs and alot easier.
Cool... thanks for the great response.
It's too bad there isn't an iron-clad, 100% reliable means to take a snapshot of the phone that can be restored reliably.
On WM it was simply a matter of using one of the various backup utilities (I used SPB Backup 2) to make an image of the system. No matter what I did to the phone, I could always wipe it back to factory clean, then restore from backup and have my phone back exactly as it was, with no issues.
I'm trying a CW backup, factory reset, restore cycle right now to see what happens. I'll report back on my experience.
EDIT: Okay, one deviation from the WM experience: The factory reset did NOT reset the kernel -- MixUp is still showing as the running kernel. Is Odin the only way to get the factory kernel back?No matter what, I'm on my way after that to the Syndicate ROM!
EDIT: Okay, the CW restore seems to have restored everything back to the way it was, without problems after some brief playing around. No FCs (so far). On to wiping again, installing Syndicate Standard, then restoring data from CW as recommended here.
OperationMove said:
You have the idea right. You really don't even need to back all your apps up with titanium anymore these days, though, it too is plagued with FC's and problems. If you are using clockwork recovery, and you have made a backup already... all you have to do when installing a NEW rom is first wipe-fest, then let it boot once, then restart, go to clockwork, go to Advanced Restore, and ONLY restore the DATA part. (Reason for this is if you restore Boot, System, etc it will try to restore the Rom you just installed... Data is where all your apps/settings are at) This will do exactly the same thing as titanium backup will do, only with less bugs and alot easier.
Click to expand...
Click to collapse
Alright I took the plunge and it seemed to work well. Some things that I noticed was that on first boot (before I did the restore), all of the preinstalled apps showed up (for instance, wireless tether, wired tether, launcher pro, etc...). Since I did a restore of the data, all of MY apps are there, but some of the apps that were preinstalled disappeared. Not all of them, though. For example, Launcher Pro and Wired and wireless tether disappeared, but Car Home is still there.
Another thing to note is that my widgets on the home screen don't seem to function correctly at first. I had to remove them and readd them to the home screen for them to work.
Other than that, everything is as it should be.
hotwired34 said:
Alright I took the plunge and it seemed to work well. Some things that I noticed was that on first boot (before I did the restore), all of the preinstalled apps showed up (for instance, wireless tether, wired tether, launcher pro, etc...). Since I did a restore of the data, all of MY apps are there, but some of the apps that were preinstalled disappeared. Not all of them, though. For example, Launcher Pro and Wired and wireless tether disappeared, but Car Home is still there.
Another thing to note is that my widgets on the home screen don't seem to function correctly at first. I had to remove them and readd them to the home screen for them to work.
Other than that, everything is as it should be.
Click to expand...
Click to collapse
Hmmm... okay. So just to provide a different datapoint, I'll go the Titanium route to get my own apps and settings back, and report. I'm guessing CW wiped the DATA partition before the restore, wiping out the pre-installed stuff from the ROM.
dwallersv said:
Hmmm... okay. So just to provide a different datapoint, I'll go the Titanium route to get my own apps and settings back, and report. I'm guessing CW wiped the DATA partition before the restore, wiping out the pre-installed stuff from the ROM.
Click to expand...
Click to collapse
Ok, since yesterday, I tried both ways. I did a wipe back to the default Syndicate Rom and installed Titanium Backup. While restoring, I noticed that not all apps would restore (seemed to be ones that were in the stock ROM so it's understandable). I did a restore of apps + data. Now, I had most of my apps back, however, I noticed that some of the data was missing. For me, most importantly was the SMS Messages. I also wanted to note that doing an application by application restore of the backup was very time consuming! I had to basically reinstall every app (and then Titanium restored the data)
Nandroid doesnt seem to touch the kernel on our phones ether I noticed. I had a problem yesterday after I flashed a new rom and when I went to do a restore through nandroid I got a bootloop. Once I reflashed the kernel it fixed the bootlooping problem. I have noticed this in other instances to with kernels not being backed up since I did one after I rooted my phone so I would have a stock image.
Thanks guys on your experience and feedback on the backup thing that I'm wondering what to do after stock root.
dito33
Sent from my SPH-D700 using XDA App
pyroswithoutfire said:
Nandroid doesnt seem to touch the kernel on our phones ether I noticed. I had a problem yesterday after I flashed a new rom and when I went to do a restore through nandroid I got a bootloop. Once I reflashed the kernel it fixed the bootlooping problem. I have noticed this in other instances to with kernels not being backed up since I did one after I rooted my phone so I would have a stock image.
Click to expand...
Click to collapse
This is what I have been told in the past- a nandroid restore does not replace the kernel
I'm running the latest version of ACS, and I keep getting a force close loop for "com.sec.android.provider.logsprovider", when I boot. Meaning I tap force close, and it comes right back, giving me no access to my phone. This is after two crashes (using the phone then it turns off). Does anyone have a suggestion? My father's Evo did this too, and he had to scream at Sprint before they'd swap the phone, but it's working fine now. I have the insurance thing on my plan, should I try that? If so, would I have to use Odin first?
Did you try to restore a backup with titanium backup??? I would boot to clockwork recovery and try to fix permissions by going to advanced in the menu.
Already done. I wiped user settings or whatever too. I'm now trying to reflash ACS and it says can't open /sdcard/foo/bar/syndicatefro110-standard-signed.zip (bad) could it be my sdcard? Does Sprint cover those under my hardware thing? I'm using ext4 afaik.
Im not sure if the cover the sd card I want to say no unless it is under a month old. However I wouldnt bring the phone in like that I would odin to a stock unrooted rom. Try to recopy the acs rom to the root of your sd card and then wipe data/factory reset 3 times in clockwork and then try to reinstall the rom.
I've been having issues on all my roms, so I'm thinking it could be my sd card. I'll bring it in as a last resort. Don't want to Odin if I can avoid it. Thanks for the help.
the logs provider has to do with mms and call logs and the sd card shouldn't affect it since it is a system app data/data/com.sec.android.provider.logsprovider. Did you try to clear the dalvik in advanced within clockwork???
That's crazy, I'm having the same exact problem. I was running the latest ACS fine for weeks and then I just rebooted it and BAM, 'Force closes' like crazy!
I reformatted, cleared all cache and factory reset to no avail. I still kept getting the same things pop up. I finally installed it through the zip file the 3rd time and somehow iit's working fine. I lost all my apps and evidently they didn't back up to my google account.
I'm too scared to reboot myphone now since that's what seems to trigger the problem.
Anybody know the source of the problem?
Curious if your getting any oneDram errors in dmesg? Seems like you guys are starting to have those odd errors were seeing in the Bonsai 4.1.0 beta.
Sent from Bonsai 7.0.3
I don't think i saw a oneDram error message, I remember seeing force closes for most of the services or processes that usually run in the background like phone and DRM service.
The persistent force close message that kept popping up was the logs.provider one.
This problem is currently happening to me now
I'm to lazy to fix it now though by the end of the week I'll do something
This happened to me while I had very bad/varying signal
(0-2 bars on a six bar scale)
And low battery
(40%ish)
I clicked on my email app and while it was loading I locked my phone and walked toward a window for better signal
When I looked back at my phone it rebooted by it self and everything is force closing like email and messaging.
Sent from my SPH-D700 using XDA Premium App
Yeah that's very similar to how out started with me too. Actually it might be exactly how it started.
Please let us know what you find out, because I've actually had this problem once before with an ACS rom.
I had my phone do this the other day with the logs provider. Reinstalled the rom (ACS Latest) and the issue went away...
Brother has been having the same issue for weeks on his epic too. He was running Bonsai 4.0.1 getting the same force closes, only his started first when he tried to open his mms app... He installed the latest ACS to see if it was Bonsai, about an hour later got the force closes again until he had an endless loop again.
We checked our memory blocks just for giggles and noticed he has 3 bad blocks while i have 11... cant be the issue...
He would get those force closes on EB13 and DK28 too.
We always do the 3x 3x 3x dance in clockwork before installing a rom too...
Dont know if this info helps or not. He thought about going stock and hitting up a Sprint store today and taking out an insurance claim....
Sorry I missed this thread.
Here's what I want you guys to do.
Back up your sdcard to your pc. ( just the files you wanna save.
Format your sd card with your phone
put the rom zip on your sdcard
Back up everything with your favorite back up program. titanium or mybackup root.
Reboot into cwm make sure it's 3.0.0.6
Wipe data, cache, dalvik 3x's ( don't cheat )
Flash your rom.
Boot your phone.
Restore your back up from your backup program. ( apps only no data )
Reboot into cwm again.
This time only wipe cache and dalvik 3x's ( no cheating )
Reboot and you should be good to go
Sent from my SPH-D700 using Tapatalk
^ This is a guaranteed solution to any unexpected FC problems.
k0nane said:
^ This is a guaranteed solution to any unexpected FC problems.
Click to expand...
Click to collapse
I wish it was, but it isn't a guaranteed solution. It might work 99% of the time.
Sent from Bonsai 7.0.3
Top Nurse said:
I wish it was, but it isn't a guaranteed solution. It might work 99% of the time.
Sent from Bonsai 7.0.3
Click to expand...
Click to collapse
I said for FCs, not bricks.
I'm having the exact same problem with the same ROM. The other day it froze after I took a picture and wouldn't respond. Had to do a battery pull after which I was stuck in an endless boot loop.
Tried just reflashing the ROM from SD and no dice, then cleared all caches 3 times and reflashed and I had a working phone again.
Then about 10 minutes ago I was using the phone and it shut down out of nowhere, after that booted back up with a tone of force closes and now the log provider force close won't go away. I'm just going to switch ROMs cause this is ridiculous.
No need to do that. The solution for freezing is excrutiatingly simple - and if it only freezes when you're in the camera, you need only format your SD card.
Do that, wipe data, and reflash, and everything will work 100% perfectly.
i had this issue more than once. and any kind of restoration of a backup made after the fc started resulted in continued fc's. i had to start fresh no backup and restore.
darksideauto said:
i had this issue more than once. and any kind of restoration of a backup made after the fc started resulted in continued fc's. i had to start fresh no backup and restore.
Click to expand...
Click to collapse
As expected - Nandroid bad data, and your bad data will remain. Use MyBackup Root for that.
Just take a Nandroid backup and restore it when you're running properly - or use the zip in the development section to turn journaling on. No problem.
Anyone else go into the app screen on manage applications and see all the data flashing and the buttons too. I have to exit and go back in several times to get a stable screen to be able to the clear data or cache
Any particular app, or all of them? Are you using Titanium, or running a custom ROM?
I've never seen this until last week. I flashed the Virtuous Unity ROM, then tried to restore ChompSMS via Titanium Backup. Chomp SMS kept giving me force closes. Going to that app in Manage Applications gave me flashing, non-responsive buttons like you described. Hitting the Back button, and selecting the app again, made the buttons behave normally. Restoring Chomp using Titanium kept giving me the same result, whether I restored with app data or not. Just uninstalling the app, and installing the original APK fixed the problem. Not sure if the Titanium backup data was somehow corrupted, or what. But it seems fine now, and I haven't noticed this issue with any other apps (including ones restored from Titanium).
If the app is not one where you need to keep the data, just uninstall the program and re-install, and see if that helps.
EDIT: I see from your other posts, that you are also on Unity. So perhaps its some bug or incompatibility in the ROM? It would help if you mentioned things like running a custom ROM, when asking about an issue.
redpoint73 said:
EDIT: I see from your other posts, that you are also on Unity. So perhaps its some bug or incompatibility in the ROM? It would help if you mentioned things like running a custom ROM, when asking about an issue.
Click to expand...
Click to collapse
Its a known issue with unity. I believe the sensation has exactly the same problem with the stock rom
Hey guys. I've had it with MIUI. and i'm ready to switch to a new rom. i figured now was as good a time as any to try out CM7. So i downloaded the latest stable version, backed up my existing install and flashed. The phone got stuck at the bootscreen. I assumed it was because i neglected to wipe data and cache, so i went back, wiped everything, reflashed and booted into CM7(after an extensive wait)
Everything was running great and i just finished restoring my apps with MyBackup. I was getting FCs on a few apps, but i chocked it up to CM7 not having all the components that some of those apps require. I was about to start removing the offenders when the phone crashed and went back to the bootscreen. It sat there for 2 hours before i pulled the battery and restored back to MIUI.
In short, i really want to try out CM7, but if it's going to be this unstable, obviously it won't cut it. Am i doing something wrong??
Some apps just do not play nicely when being restored from a backup. Can you restore apps 1 at a time so that you only get the apps that you know work? Then re-download the apps that are causing problems.
Possibly. That seems like an unnecessary step though. Would a rom really crash because of app incompatibility? I thought they would just FC every time i tried to run them, not blow up the whole ROM.
If you are using ROM MANAGER you can try to use the utility for "Fix Permissions". I'm sure there is a way to do it in the recovery them selves, but the process escapes me.
This is not an uncommon requirement when restoring from one complex ROM to another.
I had some quirkiness restoring a few apps with Titanium backup. I ended up just reinstalling them from Market and haven't had issues since. Also, after restoring my contacts with Mobile Backup II, I could not edit them from the phone. Force closes. Had to delete them and re-sync with Gmail and exchange server. No problems after that.
I have flashed Synergy, Swagged Out Stock, SavagedZen, and a few others and always wandered back to CM7. In my experience, whenever you switch ROMs like that, there are always quirks, so I have taken to getting apps one at a time from MyBackup Root when I do switch. And yeah, I have had App conflicts cause forced bootloops before, it is not completely unheard of. I second the notion of installing one at a time, and Market DLing any that force loops. And as always, I reccomend a cache/dalvik/data whipe when switching full roms.
I've noticed two problems that crop up when I use Titanium Backup to restore my apps/data
1) If I try to restore the missing apps + data, sometimes everything gets restored, and sometimes it gives me "X elements failed", where some apps will not be installed. This happens whether I restore on the same ROM that I backed up on (backup on Cloudy G2, restore on Cloudy G2) , or if I use a different ROM (backup on NDM 5.5, restore on Cloudy G2). I thought I found a work around, where I just install the app from the Play Store first, and THEN I would restore the app data. That worked a few times until....
2) When I tried restoring my app data last night after a fresh KDZ wipe, the apps that I restored data on all couldn't start (Snapchat, Amazon, Wechat, SwiftKey). I would tap them, they would try to open for half a second, then they would close. I tried restarting my phone, but with that, I got "UIDs on your system are inconsistent, you need to wipe your data partition or your device will be unstable". I was stupid, and decided to wipe my data partition so I had to restore all my apps from scratch, but that at least hasn't lead to any problems yet.
Does anyone know what I did wrong, or what I can do to fix this? I know for number 1, some threads mentioned that your Android I.D. changes when you flash a new ROM (that MIGHT explain number 2?), but not a lot of people mention this, and it seems like the majority of people don't have this problem. For number 2, I found this thread, but it was too late already.
If possible, I'd like to find a backup app that avoids ALL of these and just lets me back things up and restore easily. Is there one out there?
tdk0117 said:
I've noticed two problems that crop up when I use Titanium Backup to restore my apps/data
1) If I try to restore the missing apps + data, sometimes everything gets restored, and sometimes it gives me "X elements failed", where some apps will not be installed. This happens whether I restore on the same ROM that I backed up on (backup on Cloudy G2, restore on Cloudy G2) , or if I use a different ROM (backup on NDM 5.5, restore on Cloudy G2). I thought I found a work around, where I just install the app from the Play Store first, and THEN I would restore the app data. That worked a few times until....
2) When I tried restoring my app data last night after a fresh KDZ wipe, the apps that I restored data on all couldn't start (Snapchat, Amazon, Wechat, SwiftKey). I would tap them, they would try to open for half a second, then they would close. I tried restarting my phone, but with that, I got "UIDs on your system are inconsistent, you need to wipe your data partition or your device will be unstable". I was stupid, and decided to wipe my data partition so I had to restore all my apps from scratch, but that at least hasn't lead to any problems yet.
Does anyone know what I did wrong, or what I can do to fix this? I know for number 1, some threads mentioned that your Android I.D. changes when you flash a new ROM (that MIGHT explain number 2?), but not a lot of people mention this, and it seems like the majority of people don't have this problem. For number 2, I found this thread, but it was too late already.
If possible, I'd like to find a backup app that avoids ALL of these and just lets me back things up and restore easily. Is there one out there?
Click to expand...
Click to collapse
is a supersu issue, open supersu than go to is setting and not select "name space mount separation" that is selected by default.
Now titanium can work as intended
Romagnolo1973 said:
is a supersu issue, open supersu than go to is setting and not select "name space mount separation" that is selected by default.
Now titanium can work as intended
Click to expand...
Click to collapse
That will fix both problems that I have?
Try, I was unable to use it untill I change the SuperSu setting and now Titanium is working perfectly, so probably your problem is the same.
Oh I mean, I can use it just fine. It can perform backups. But restoring is a when I get those errors. I'll keep this in mind in case I need to restore to a new ROM, thanks!