I have an Evo (003 Hardware) and while switching ROMs, at least twice now, I've had trouble restoring some apps using Titanium Backup. The weird thing is, I'ts only some apps, that are having the restore problem, while others seem to be restored, but without their settings saved. (Google Listen is an example of the former, while AdwEX is of the later.
I've verified the backups themselves, and they come back without errors, I've also tried flashing different ROMs like Myn's new Warm Z, MIUI, and Koni's Elite II. Those have no trouble restoring. Seems the problem is confined to the nightlies, as I'd installed RC1 before without issues.
Anybody have an idea what's wrong?
When re-flashing the roms, try a clean install, and also flashing the latest gapps. Not flashing them has been seen lately to cause a few apps not restoring, or some just missing completely. Best to do it in 2 recovery sessions, backup, flash rom, reboot, flash gapps, reboot.
teh roxxorz said:
When re-flashing the roms, try a clean install, and also flashing the latest gapps. Not flashing them has been seen lately to cause a few apps not restoring, or some just missing completely. Best to do it in 2 recovery sessions, backup, flash rom, reboot, flash gapps, reboot.
Click to expand...
Click to collapse
I always do a fresh install. Wipe data, cache and Dalvik, plus flash Calkulin's Format All.
I haven't tried flashing ROM and gapps in different sessions, as that brought trouble pre-rc1, I'll try that now, though.
Well I practice the 2 recovery session as a standard, sometimes it works in 1 session, but when it doesn't the 2 session step bring me no problems; but let me know what happens.
turns out, that wasn't the problem. Two-session flashing didn't bring any issues, which I was glad to see (although it did switch the wallpaper, that's just weird). What did help was this post from the rc1 thread http://forum.xda-developers.com/showpost.php?p=11722822&postcount=1603, where this exact problem is described, but I happened to miss it while searching somehow. anyways, it finally restored the apps, but not their data. I guess that's better than nothing, but again, just plain annoying.
Ah I see. Well now backup the apps and data and you should be set now.
Related
I have a dinc running skyraider 3.3final and each time i reboot, i get the setup when i unlock
i tried skyraider, virtuous, and cyanogenmod and they all took me to setup after reboot and uninstalled all apps
~~~~please help~~~~
this happens even when you don't wipe?
I haven't tried not wiping
but everytime i do a full install and wipe everything, i still get the problem when i reboot. I've been going all day and everything has been working fine, i just don't want to reboot because i won't have anything
any suggestions
I had this happen to me also not too long ago, never tracked down what was causing it. No matter what ROM i flashed, or nandroid restored, I would end up with the setup screen and a multitude of FC's.
I ended up just returning to stock with the official RUU, and re-rooting. Haven't had an issue since. Make sure you back EVERYTHING up though.
I've rooted my phone for the first time the other day and started venturing into the custom ROM's realm, but so far all I got were dramas and failures.
I started by downloading Cyanogen 6.1.1 and 7 RC1. I thought I'll try each to see how they perform. So I copied them to the sd-card, along with the radio update that was recommended on the Cyanogen 7 RC1 thread, and rebooted to Clockswork recovery. I wiped my data and cache and went on with the ROM installation followed by the radio update (notice that I skipped the backup stage. stupid, I know).
Upon booting, I immediately noticed that I have no signal, and a force close message that says: "the process com.android.phone has stopped unexpectedly. Please try again" pops up every 2 seconds. Nothing happens when the message is dismissed, mind you, but it still comes up constantly every couple of seconds. This, along with the 'no signal' thing, rendered the phone unusable.
At this point I'm thinking that maybe my phone is just not reacting well to the non-final build of the Cyanogen 7, so I gave the stable Cyanogen 6.1.1 a go. Lo and behold, same thing happens with it also. Now panic kicks in when I realize that I have no backup, and no stock ROM to go back to.
Eventually, I downloaded the latest rooted Desire 2.2 ROM, got it into my sd-card and installed it. Thankfully, everything was working properly again. After some asking around in the Cyanogen forum, it got to my attention that the update to the radio might have caused all of this trouble, and that the installation of the stock ROM brought the previous radio version with it, which solved the problem. But when I tried to install Cyanogen again, without tinkering with the radio, same thing happened. I then tried Oxygen 2, thinking that maybe my device just doesn't like Cyanogen, but the exact same problem persisted.
Anyone have any idea what's the deal here?
Did you wipe dalvik cache after flashing the roms?
Sent from my HTC Desire using Tapatalk
I wiped the cache partition before I flashed. It didn't say 'dalvik' specificaly, just 'cache partition'. I never wiped any type of cache *after* the flashing process.
You should wipe the dalvik cache after (or just before) flashing roms.
You can find it under the advanced menu in clockworkmod recovery.
Sent from my HTC Desire using Tapatalk
Alright, tried wiping the Dalvik Cache after flashing, problem still persists.
You could try downloading another radio and trying it. Even if it's not the recommended one, an older radio works better for some people. There is no such thing as 'the best radio to use', since result may have large variations for different people (in different locations, using different phones and ROMs). Just browse the radios post and pick one
Btw, since the dalvik cache is stored at /data/dalvik-cache, wiping the /data partition implies deleting the dalvik cache
Well, since the radio that I have installed now works, and since it stays the same one after installing a different ROM, it seems to me that the radio is not the problem here. I really would like to stay away from tinkering with the radio stuff...
Bump.
This really bugs me that it wont work. I feel like I'm missing out on the biggest feature of having a rooted phone...
Hmm... I've found that if I force the phone into Airplane mode, the FC messages stop. Of course, I still have no signal.
So, the reason for the FC messages is due to the failure to connect to my mobile network. Now, why would I be able to connect to my network fine on the official Desire ROM, but not on any other ROM?
If all else fails you could always trying flashing the RUU for your phone then start from the beginning and root again if you've tried everything else.
Sent from my HTC Desire using XDA App
Ok, I'll try that.
Just a quick question. After I run the RUU and the device is unrooted, will I be able to recover my nandroid backup fully after I re-root?
So I decided to try one of the ICS roms earlier today. I nandroid backup'd my current config, flashed the ROM, played around, ran calkulin's format all, and proceeded to nandroid restore. Booted back into what was my original config only to find it's constantly locking up and random apps keep FCing. I did fix permissions, I wiped dalvik and cache multiple times. What the hell is the point of nandroid if it doesn't ****ing work right anyway?
I'm on RA 2.3 recovery. I backup the normal stuff including .android_secure and wimax.
Do you still have the rom handy?,if so,do your nandroid backup,then without wiping anything,install the rom over the top of the backup you just restored,it should help with the FC's,it worked for me,but if you installed a theme,it will convert back to stock as far as the framework goes.
Try manually wiping all options except sdcard and battery stats 3x or more and then restoring your nandroid then wipe cache and dalvik after the restore and before rebooting, sounds like you may have an errant piece of data that got left behind during the wipe
It seems that the 18 or so reboots I was forced to do have fixed something. No problems now. Strange for sure.
G+ was locking my phone up causing me to have to pull the battery, it was working fine then there was an update in the market but I was using an inverted version and didn't want to update the the bright white one and after a week of not updating it it started randomly freezing up when I would try to upload a pic or post a long message I updated and it stopped :-/ which was weird in itself maybe an app got updated and fixed your issue or maybe something uninstalled itself if your using dta2sd, sometimes when I have FCs, random reboots or have to do a battery pull some of my a2sd apps disappear when I reboot
After flashing deck's ICS alpha5 onto my Evo 4g (Sprint) everything works fine and as it should. However, whenever I install Titanium Backup and then restore my apps+data problems arise. Specifically after rebooting my phone it hangs on the ROM load screen and never gets passed that. Im forced to remove the battery and try again, but no luck. I can reflash the ROM and it works, it isn't until that initial reboot after TB restores my apps that I get this problem. Any suggestions?
Thanks in advance.
as far as i know its recommended restoring apps ONLY not apps + data. i have done it this way with all the roms i have flashed and never had any problems.
Lou8729 said:
as far as i know its recommended restoring apps ONLY not apps + data. i have done it this way with all the roms i have flashed and never had any problems.
Click to expand...
Click to collapse
Never even thought of that. I will try and give ya an update. Thanks
That seemed to do the trick, weird because I never had any problems before when going between other ROMS's. Thanks again.
Cm roms don't handle back ups of app data from other types of roms due to the OS code changes CM roms use
Whenever I flash Touchwiz ROMs I get force closes left and right when I first boot the phone up. I have no idea what's wrong. AOSP ROMs seem to work fine.
Sounds like you're not fully wiping, or you've got a bad download. Check md5s on any ROM you download, and ALWAYS do a factory reset in recovery (2 or 3 won't hurt either) and manually wipe System, Data, Dalvik, and Cache before flashing a new ROM. Don't try restoring any backed up system data either...
I have encountered the same problem, when flashing my latest DomPop builds. It just takes doing everything @Morningstar said, multiple times, and if you get force closes, reboot, try again. It may take a few times.
Also, the newest DomPop v0.5 will let you choose in your initial setup if you want a TouchWiz launcher or another one of like 10.. Nova Launcher, Google, etc. It is pretty dope ?