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.

Apps Force Closing after root?

I just installed the RED ANGRY ALIEN theme running on CWM3 and for some reason, swype and google apps keep force closing and giving me errors. I cleared the cachs and stuff but nothing helps. any ideas?

cheech92007 said:
I just installed the RED ANGRY ALIEN theme running on CWM3 and for some reason, swype and google apps keep force closing and giving me errors. I cleared the cachs and stuff but nothing helps. any ideas?
Click to expand...
Click to collapse
Boot into CWM and clear cache partition/dalvik cache 3x
Reboot.
If that doesn't work you could always try booting back into CWM and select Advanced>Fix Permissions. Then reboot. I think the first suggestion should work.

[Q] Unrooted or problem with ROM?

I have been using MIUI lately, yes it has it quirks but its sufficient as a daily driver...until now at least.
The latest release has issues with SU force closing, but there was a fix. Flashed the fix and everything was working fine.
SU started acting up again, so I reflashed fix...no dice.
Not only is SU FC'ing, Terminal, titanium backup, root explorer and set cpu don't think I have root access.
S-off is displayed in the bootloader, i can get to recovery still...
Is the ROM jacked? Is it safe to do a fresh wipe and try another ROM?

You can either:
-Reboot
-Run fix permissions [rom manager or recovery]
-Reflash the rom
-Do a full wipe [backing up what you need], flash another rom
All should solve the problem

teh roxxorz said:
You can either:
-Reboot
-Run fix permissions [rom manager or recovery]
-Reflash the rom
-Do a full wipe [backing up what you need], flash another rom
All should solve the problem
Click to expand...
Click to collapse
I have rebooted several times including wiping cache and dalvik cache (if that even helps in this case).
I have run fix permissions in rom manager but obtain 'error occured while attempting to run privileged commands'.
If terminal says 'permission denied' and subsequently SU force closes, is the ROM just messed up?
As long as S-off is displayed in bootloader, I still have root and can flash a ROM without any problems?

jdefran said:
I have rebooted several times including wiping cache and dalvik cache (if that even helps in this case).
I have run fix permissions in rom manager but obtain 'error occured while attempting to run privileged commands'.
If terminal says 'permission denied' and subsequently SU force closes, is the ROM just messed up?
As long as S-off is displayed in bootloader, I still have root and can flash a ROM without any problems?
Click to expand...
Click to collapse
May just be the rom, but yes, while s-off, you can [re] flash, it or another rom from recovery.

[Q] In need of some assistance.

So i have flashed for awhile and never have encountered this problem. i was on lbj7 i went back to stock. did Ota upgrade to 4.1.2, rerooted flashed another rom and now all it does is forceclose. How do i clean the system completly so i can reflash a fresh clean install. I normally wipe Delvik+cache+ factory what else can i include to insure i have a 100% clean flash?. Any and all help is appreciated thanks!

Wipe internal storage will erase anything on the internal just as it states. What ROM are you trying to flash? Also what recovery do you have and is it up to date. If you want the ultimate clean install I do this, make sure the and if you need gasps or any other file is on the external card
Wipe data, cache, dalvick, system this removes the ROM, internal and maybe even format data. Flash ROM wipe cache and dalvick and if you need to gasps the wipe cache and dalvick the boot. But make sure your recovery is up to date, I use twrp which is on 2.4.4 right now. And you have the correct gasps if needed. Good luck.
Sent from my SPH-L710 using Tapatalk 2

Hey Thanks Giantay.. I am trying to reflash Goodness 9.0.4. Its forceclosing Touchwiz and Apex and all the other.. I seem to have a Wakelock aswell Media is stuck at 40% Battery Useage. I use Cwm. Maybe i should switch to Twrp..

thaset said:
Hey Thanks Giantay.. I am trying to reflash Goodness 9.0.4. Its forceclosing Touchwiz and Apex and all the other.. I seem to have a Wakelock aswell Media is stuck at 40% Battery Useage. I use Cwm. Maybe i should switch to Twrp..
Click to expand...
Click to collapse
To install TWRP the easiest way just download Goomanager from the Play Store here https://play.google.com/store/apps/...anager&feature=nav_result#?t=W251bGwsMSwyLDNd open it go to settings and select Install OpenRecoveryScript, This will download and install TWRP's newest recovery. You could also check the md5sum to see if it's a good download. Sometimes the files that you download are corrupted but I have never had it happen, and I have flashed endless amounts of ROMs on different phones, but it happens people say. I am unfamiliar with that specific ROM but try searching in the thread for it to see if anyone else has had similar experiences and have a way to fix it. Searching is your friend, search and read a lot will ussually solve your problem, and if you don't turn up anything don't be afraid to ask a question instead of doing something that might be unsafe or worries you.

I did as u suggested and just tried re flashing using Twrp. Awaiting Results as first boot aproaches. Thanks again for the helping hand.

Just a heads up. Try and hit the thanks button on these forums if people help you in any way. I don't really care about it but it helps some people especially devs and what not.

Kernel error message

Hello fellow M8 users, I would get a error message "unfortunately android system has stopped" every time I flash a custom kernel either on faux or elementalx. This is usually rom related but I am on rooted stock sense, s-off. I have a good backup copy of the rom before any changes but I would really like to get the benefits of a custom kernel without this message. Anyone got any ideas for what I can do to get rid this message on startup?

Did you overclock or undervolt at all? Make a backup of your current rom then try wiping cache and dalvik then try and see if you still get the error? If not then you can restore the backup, backup apps and data with titanium backup and Wipe cache and dalvik then install kernel again and restore apps and data and see if you still get it.

exad said:
Did you overclock or undervolt at all? Make a backup of your current rom then try wiping cache and dalvik then try and see if you still get the error? If not then you can restore the backup, backup apps and data with titanium backup and Wipe cache and dalvik then install kernel again and restore apps and data and see if you still get it.
Click to expand...
Click to collapse
Same error. I am not running any overclock or undervolt. I think this is because I am running the ATT version of this phone but there are users who are running custom kernels with no issue.
The only other thing I can think of is that I edited platform.xml to modify the WRITE_EXTERNAL_STORAGE permission so I can write to the ext sd card.

Post a logcat. That would show this issue. Otherwise its just a guessing game.

task650 said:
Post a logcat. That would show this issue. Otherwise its just a guessing game.
Click to expand...
Click to collapse
Hi Task, here is my logcat from boot using: adb -d logcat -v long
I appreciate your help in this matter. I would also like to thank you since I thoroughly enjoyed using your GS3 rom :good: