I used My Backup Root to back up my apps/data when I switched from stock to SHOstock and it worked great. Yesterday I decided I wanted to try out XWLI1 with JKay because I've heard great things about the combo, so I backed up all my apps/data with My Backup Root and then I flashed CleanRom. I then went into My Backup Root and told it to restore my apps and data, it said it worked and I rebooted my phone. But when I rebooted, none of my apps had their data... I tried it a couple times, and it never seemed to work. I ended up just nandroiding back to SHOstock, but I was thinking of trying it again today...
Is there something fundamentally different about the 2 ROMs that would keep me from restoring app data? Or is there something else I might be overlooking? Any help would be great...
Related
I've always used MyBackup Root to backup and restore my apps when going from ROM to ROM and never had a problem. Recently I backed up my apps (NOTE: I NEVER backup system apps, just user/third-party apps and the only system data I back up is calendar data) in a 2.2 ROM (Trigger) in order to flash a 2.2.1 one (Bi-Winning) without issues. I flashed the new ROM and proceeded to restore the apps using MyBackup, again with virtually no problems, everything went smoothly and the market apps had their links restored, etc.
However when I started using my apps, most of them had weird problems. Some were force closing, others had missing data or no data at all, and some were simply broken. I instantly lost track of what worked and what didn't. I assumed this was caused by a bad flash so I re-downloaded the ROM and flashed it again making sure I followed all the instructions to the letter. Then I restored everything again and all of my apps were behaving the same way. This isn't the case if I delete then reinstall an app using Market or another source that is not MyBackup.
After freaking out/****ting bricks/etc, I started looking for ways to deal with the problem. This is what I've done so far:
- Used a 1-week old MyBackup folder that had worked before when I went from Bionix to Trigger. (Failed: Similar, if not the same, results)
- Flashed Trigger again and both folders failed.
- Flashed a different ROM (phiremod) and tried both folders. Fail again.
I'm about to delete my folders, start from scratch with no app data, and use Titanium Backup from now on. Has anyone had similar problems?
Just thought I'd give an update since this has gotten over 90 views.
I started from scratch ever since and have been using Titanium Backup Pro. I've switched to many 2.2.1 and 2.2 ROMs so far without issues and all of the restores have been flawless.
So last night, I felt a bit adventurous and flashed CM7. I had my Titanium backups done so I restored my apps back but none of the backups would restore its user settings, like how it did for TW-based roms. For example, my LancherPro does not have the paid status, my XDA app needs my ID/PW put in again, Whatsapp needs to reconnect with my contacts, etc etc. I went back to EC01 rom and restored everything back without any issues. Is there an explanation as to why the user/password/key settings aren't getting restored in AOSP/CM roms? I'd really appreciate it. Thank you.
I guess this goes beyond the Defy forums...
I have a Motorola Defy with CyanogenMod-7.1.0-11-Defy on and since about 3 days ago I noticed that it doesn't send SMS'es. At first I didn't care, but today I looked more into it.
The message center is the right one. Wiped the Messaging data, restored it from an earlier backup with Titanium Backup. Wiped the cache partition. Nothing! I even freezed some apps that I recently installed (nothing that might have to do with SMS'es).
Strangely, Handcent SMS sends the messages.
I've had a similar problem some time ago (before using CM7), but that time it was because of the CloclworkMod recovery. After I uninstalled that (not the market app) everything went back to normal. This time the recovery is included in CM7....
Any ideas what should I try?
I have the exact same problem. still haven't figured out a fix short of wiping your data and re-flashing your rom.
In the end I've made a back-up with Titanium Backup, wiped, installed ROM (newer version of CM7) and restored the backup.
Everything seems to work now.
Alright, first of all, yes, I'm a noob here, however I am not a noob to forums. I did search for similar problems but to no avail. Moving on..
I just recently put CM 7.2 on my dad's Droid X2, I had it working flawlessly and everything was fine. Created a nandroid backup and all was good.
Today he wanted to restore his phone back to that original nandroid in order to get his recipes and notes from some app that didn't transfer over (I was unaware, or i would have saved them) when he did so he restored it and everything was going fine until the phone locked up with "dynamic config335.data" on his screen. Apparently, it locks at this and needs a battery pull to fix, and the restore never occurred.
We ended up doing this a second time and the same process occurred again. As I never had to deal with this with my DX2, i'm not quite sure what to do.
Any help would be great!
Thanks
You could try to sbf and then restore the nandroid.
DD you do not ID the restoration agent is it TB? Or what?
Ok so the error occurred after the suspected nandroid?
Here is where I get confused
"(I was unaware, or i would have saved them) when he did so he restored it and everything was going fine until the phone locked up with "
Restored it w/ cwr?
DD you do not ID the restoration agent is it TB? Or what?
Click to expand...
Click to collapse
'
You'll have to slow it down with the acronyms until I know them all haha
After I rooted his phone, and before I flashed CM7, I created a Nandroid. After he's been tinkering with it for the last few days he realized he wanted some files that did not get transferred over.
He decided to restore to that nandroid and while it was restoring it got stuck with that appearing on his screen. It never finished the restore.
Luckily I had him make another nandroid before messing with it so I was able to get CM7 back unharmed however he still wants these files...
Do you guys recognize this error? It just happens mid restore
Never seen the error. You could just have a random error. Maggard.
...may have the best advice.
If you have Titanium Backup you could try using it to restore just the data that he needs. TB has the ability to restore files and data from nandroids. You may have to have the paid version though, I'm don't remember for sure.
Alrighty, i'll try and mess with it. Thanks guys!
hey guys, I just bought OPX 2 days ago and rooted and unlocked the bootloader yesterday. I also removed few apps like slides, doc etc and everything was working fine. Today when I saw storage was almost full (because of those google apps updates) I tried to integrate them into ROM using Titanium backup. 2 of 18 apps were successfully integrated (don't know which) but then it stuck for a lot of time. So i forced stop tit and tried integrating each app individually, but still same problem and it had f**ked system a little so fortunately I had restored the backup which I took before integration. During backup, I selected all the partitions (or whatever it is) and started restoring. Everything went well until the 'persist' was getting restored. Wiping of Persist was successful but it was stuck to restoring for a really long time so aborted the restoring, wiped everything and restored everything except persist. So my question is What is Persist and will it affect my phone 'cause I didn't restored it? and why are apps not getting integrated into ROM? any solutions will be helpful
(and extremely sorry for super-long post )