Develop Bugs

[Q] App Force Close Error In Custom ROM

OK so here's my problem.. I have backups in both nandroid and Titanium Backup. I flash a ROM wait for it to do its business. After everything boots up, I try to restore everything through titanium backup but I get a force close error. I also try to open Rom Manager to see if it works and I get the same error but for Rom Manager. So the error isn't in Titanium Backup, but I do not know where it is. Any ideas?? I enjoy having custom Roms, but not if I do not have all of my stuff on the Rom.
Well I was going to attach a picture but it will not allow me because I am " New".
The error message reads as this.
! Sorry!
The application Titanium Backup (process com.keramidas.TitaniumBackup) has stopped unexpectedly. Please try again.
(Force Close) <---- button
It also does it with other applications such as the Facebook Launcher.

Once you flash your ROM, run Fix Permissions preferably from recovery, else use the version(s) in either Rom Manager, or Titanium.
Once that completes, reboot device. When you restore things from Titanium, just restore apps, preferably one-by-one, and only the app, not the data.
Do not at all recommend restoring apps+data+system data from Titanium. Why?
The system data backup residing in Titanium was for the last ROM, or the last time the backup was completed. As such, if you flash a different ROM, you are overwriting the system data of the new ROM with the system data from the old ROM - that spells odd behavior, mass force closes. etc. etc.

Well I tried this solution smtom, and it was to no avail. Any other suggestions?

When flashing a ROM, are you clearing cache/dalvik and doing the factory reset on the device? What version of Rom Manager & CWM are you using?
The latest version of CWM is giving people issues.
Absent all that, try not restoring apps or data (anything really) from TB when you flash the new ROM, after having wiped data/caches/user data.

Yes I'm clearing cache and data. The CWM version is 3.0.0.5, which is the latest recovery.
What does clearing the dalvik do and how do I factory reset the device?

I figured it out, with tmtom's help of course! I had to do a factory reset and then flashed the rom and everything worked. Thanks for the advice!!

I have the same error so I'm going to try the solutions provided in this thread. I do have one question though. Kalebskalicky mentioned that he finally fixed it by doing factory reset and then flashing the rom.
Just to be clear; factory reset is the same as wiping data/factory reset? Or I need to do a factory reset from the phone settings?
Another thing. I have noticed that the FC issues have something to do with gapps, acore, and/or framework processes. When I get any of these force closes, all the other apps start to crash, but all the issues start with any of those 3 processes crashing.
However, there are 2 apps that force close from the start, even before any of these 3 processes crash. These 2 apps are voxer and waze.
Is there like a way to delete the folder where they are installed? maybe it's a problem of installation? I have no idea and haven't been able to fix it.
Any suggestions, would be inmensely appreciated.
Thank you very much.
UPDATE:
Just wanted to mention that I always wipe data/factory, wipe cache, and wipe dalvik cache, and then flash the new rom. Is this ok to do? Or am I deleting stuff I shouldn't?
Thanks again.

I also had this issue.
I had tried wiping the cache and the dalvik cache. Fixing permissions. didn't wont to format as everything was set-up how I wanted it and couldn't be bothered going through it again.
After some digging around I had to uninstall titanium backup first then delete the folder
/sdcard/external_sd/data/com.keramidas.TitaniumBackup
(there may also be /sdcard/data/com.keramidas.TitaniumBackup to Delete)
Reinstalling titanium backup after deleting this folder, worked like a charm.
Apparently its to do with a corrupt database upgrade???
I hope this helps any one.

Q: stuck in cyanogen boot animation - Flashed back to Cm6

So I got Cm7 running using rom manager, used titanium backup to restore apps + system data, then fixed permissions. For the last 10 minutes it's been stuck in the CM7 screen....
What should I do? Can I pull the battery without harm? Does it take that long to boot after fixing permissions?
Edit: pulled the batter and am trying to boot into recovery...going to wipe the dalvik/cache again.
Edit2: same thing for the last 6 minutes....dang. I guess I'll just nandroid in 5 minutes if it doesn't' get out of it.
Edit3: going to nandroid back. I might try it again later flashing from a Zip instead of using rom manager. I probably won't restore system data either next time. If anyone has any suggestions though please post them.
Edit4: not good...phone is bootlooping cyangen screen after nandroid.
Edit5: Cleared factordata, cache, and when I go to clear dalvik I'm getting
e unknown volume for path sd-ext
Any ideas here?
Edit6: I'm reflashing 6.1.2....okay...got through the boot and now I'm setting up the phone.

You may need to wipe everything now and reinstall fresh. Do a search for Calkulin's tools here and download the format all zip and put it on the root of your sdcard. Flash it just like you would a rom from recovery. It will wipe boot, data, cache and system. Then try flashing cm7 from recovery. Usually boot loops happen because of there not being enough space on one of your partitions like system or boot etc.

housry23 said:
You may need to wipe everything now and reinstall fresh. Do a search for Calkulin's tools here and download the format all zip and put it on the root of your sdcard. Flash it just like you would a rom from recovery. It will wipe boot, data, cache and system. Then try flashing cm7 from recovery. Usually boot loops happen because of there not being enough space on one of your partitions like system or boot etc.
Click to expand...
Click to collapse
Will do....I know I had been installing apps to the SD card using CM6 and when I first got CM7 up it said my phone memory was low. I thought it would say on the SD card.
I'll probably try tomorrow again if I get the courage and I most definitely will DL Calkun's tools.
Thanks!
I'm going to guess the nandroid didn't work either because of the phone memory low issue?

I would reccomend re-doing what you did originally, except when restoring with titanium, do NOT restore system settings, only apps and data. That's probably the cause.

teh roxxorz said:
I would reccomend re-doing what you did originally, except when restoring with titanium, do NOT restore system settings, only apps and data. That's probably the cause.
Click to expand...
Click to collapse
Wiped manually, installed from zip, and didn't restore system data. CM7 has been running for about an hour now.
Thanks everyone!

Glad that you got it working man.

Is ANY system data safe to restore from Titanium?
Had the exact same problem myself... I'm restoring my Myn nandroid as we speak, and I'll mess with it more tomorrow.
Does anyone know what (if any) system data is safe to restore from Titanium? I just want my contacts and text messages basically... I don't know exactly what caused the problem from Titanium since I made sure not to check any of the Sense-related items.
For about 20 min after I pulled the battery I couldn't get the phone to do anything except vibrate three times when I tried to get into recovery. Eventually coaxed it into the bootloader where I selected to boot into recovery to nandroid back. Almost had a heart attack!

phsteve said:
Had the exact same problem myself... I'm restoring my Myn nandroid as we speak, and I'll mess with it more tomorrow.
Does anyone know what (if any) system data is safe to restore from Titanium? I just want my contacts and text messages basically... I don't know exactly what caused the problem from Titanium since I made sure not to check any of the Sense-related items.
For about 20 min after I pulled the battery I couldn't get the phone to do anything except vibrate three times when I tried to get into recovery. Eventually coaxed it into the bootloader where I selected to boot into recovery to nandroid back. Almost had a heart attack!
Click to expand...
Click to collapse
You should never restore system settings.
For contacts, open accounts and sync, tap your google account, then sync contacts, and that'll be done.
For texts, people highly recommend sms backup or my backup. Then backup apps and data, then restore only apps and data, and you'll be set.

Process Media stopped working

I've flashed my phone with the latest Cyanogen mod (http://forum.xda-developers.com/showthread.php?t=957344)
I flashed the radio, then the ROM and in the end the latest Gapps... But now several things don't work. Facebook can't start and when I try to set a new ringtone, it gives me the 'process media stopped working'. Any idea how to fix this?

Ow. It also happens when I try to visit Facebook and when I try to create a ringtone via Zedge.

Nobody with tips or hints what I did wrong?

Did you wipe everything before flashing it? Data, cache, system, battery stats...
Did you restore any system data e.g. via Titanium Backup?
Have you got a nandroid backup of where you were before?

1. Yes I wiped everything.
2. I did both. First I restored with Titanium Backup. Then I tried without a restore. STill the same problem.
3. before this I used a MIUI ROM but I didn't like it.

Nandroid Backup Failure

Allow me to preface this by stating my credentials. I've been rooted and have flashed most every ROM created since day one. I'm no stranger to the processes involved.
Just recently, this started happening. If I create a nandroid backup, then try to restore it, the boot animation just goes forever. It doesn't boot loop, it just keeps going.
This has happened with both CWM3 and CWM5, when trying to restore ICS backups. I've tried flashing the VR Superwipe with no luck either. I've also tried Fixing Permissions.
Has anyone had similar situations that could offer a solution?

Only ICS backups? Did you install a different hboot?

Well I've only tried it with ICS cause I've been running them since January.
I'm using Hboot .92

I personally haven't run into issues with restoring ICS backups using CWM 3.0.0.8. I've done the same process for GB and ICS restore, which is:
1) boot into recovery
2) backup rom
3) flash a new rom then realize I need to restore for some reason
4) boot into recovery then wipe data, format boot, & format system
5) restore and enjoy
I've done this on ICS roms AOKP and CM9 with no issues. I'm not sure how to find a fix if you have used CWM 3 and CWM 5 unsuccessfully.

If you've used the same hboot the whole time that can't be the problem. Try reflashing recovery with ROM Manager and use the "erase recovery before flashing" option.

[Q] Backup not working with new custom ROM

Hello
last night I tried installing the carbon rom for my Note 2 N7100. (v1.8 Release stable build)
Everything wen't fine but I used titanium backup to backup my files and I also have a backup with CWM. I cleared all data/factory reset and wipe cache plus I installed the 4.2.2 gapps. The OS worked completely fine but when I used titanium backup to restore all apps and system data, It asks to restart which I did and when I restarted my phone the startup time took 25 minutes+ so I knew something wen't wrong. I rebooted into recovery and wiped cache and data reset again but I'm still having issues. I forgot to mention I tried using titanium backup and just restoring system data and not the apps.
I decided to do a restore completely using the CWM backup then I flashed 4.3 gapps to get it back up to date. However, when I tried to startup my phone, gapps isn't working properly and keeps popping up com.process.gapps or something like that has stopped. Usually this means the wrong version of gapps is installed but I've tried reflashing it incase I had a bad flash but that didn't work either.
I'm now using carbon rom without any of my previous system data or apps.
What can I do?
Thanks