Have flashed my S2 a few times, and happy with XXKI4, and also rooted using the CF-Root method.
However, seem to be getting a few Force Close errors here and there.
Market sometimes force closes when im not even using it, And if i go to Settings-Location+Security-Find my mobile, both Sim change alert, and remote controls throw up a com.android.settings Force Close.
I have wiped cache, dalvik cache, and fixed permissions using CMW recovery.
Any ideas chaps?
Thanks.
Would a Hard reset maybe solve this?
mk2vr6 said:
Have flashed my S2 a few times, and happy with XXKI4, and also rooted using the CF-Root method.
However, seem to be getting a few Force Close errors here and there.
Market sometimes force closes when im not even using it, And if i go to Settings-Location+Security-Find my mobile, both Sim change alert, and remote controls throw up a com.android.settings Force Close.
I have wiped cache, dalvik cache, and fixed permissions using CMW recovery.
Any ideas chaps?
Thanks.
Click to expand...
Click to collapse
Would be my first impression too.
Just do a complete system / nandroid backup in recovery mode (or by using the CWM Manager app).
Then Boot into recovery mode and do a factory reset.
Then reboot into recovery again, wipe cache partition and Dalvik cache too.
Then reboot the phone.
If that does not help, then you may have to flash the ROM (and afterwards CF-Root kernel) again.
Please remember to backup before and wiping cache(s) after flashing.
That will prevent most common FCs.
Good luck !
I had the same problem on my galaxy note, happened when i disabled the samsungservice.apk under system/app (was trying to remove Samsung bloat)
Put back the samsungservice.apk there and no more forced closes for the find my phone settings
Related
I am sorry if this was answered before, but I have tried to search and couldnt find anything..
I have a Samsung Vibrant, of course, and had flashed Trigger 3.2. It was working great until applications started to fail such as the web browser. The applications will start but never actually run. So I tried to restore my nandroid backup, but after doing that, everytime I try to reboot my phone it stays stuck on the lock screen with "Searching" on the top right corner. Im assuming it is searching for the network, but it wont let me unlock the phone. I flashed Trigger again and it worked fine. I try restoring and Im stuck again. I also tried to factory reset and it still does the same thing.
has anyone else encountered this and know how to fix it?
Just odin back to stock with dl mode
Sent from my SGH-T959 using XDA Premium App
Factory reset from Recovery and re-flash Trigger again this time wiping cache, dalvik and fixing permissions after the flash. Now when restoring make sure to check APPS ONLY.
Abu-7abash said:
Factory reset from Recovery and re-flash Trigger again this time wiping cache, dalvik and fixing permissions after the flash. Now when restoring make sure to check APPS ONLY.
Click to expand...
Click to collapse
This is all correct. It is likely when restoring you are restoring old system data
thanks for the help! If I did this, would I still be able to flash back to stock or will I have to use Odin for that?
Abu-7abash said:
Factory reset from Recovery and re-flash Trigger again this time wiping cache, dalvik and fixing permissions after the flash. Now when restoring make sure to check APPS ONLY.
Click to expand...
Click to collapse
You have to remember when you Nandroid it doesnt flash the kernel back so you either need a flashable rom that has a stock kernel or odin back.
the above is correct make sure you do that!
Hello Everyone!
I just flash Galaxy task 7.0(new released ROM) on my tablet.
It almost works perfectly. However, I have one issue that I always get a pop-up message below when I reboot my device.
The application com.sec.android.app.worldclock has stopped unexpectedly.
What I can do is either to close it or send report to Google.
Any better solution on this issue? Where can I find the application and remove it from my tablet.
There is no problem with the rom. First try wipe data in app settings and if that doesn't work....Did you do a full wipe before installing? Whether you did or not do it agin. In cwm wipe cache, wipe dalvik and wipe data/factory reset. Do each one twice then you know it has worked, cos I heard that sometimes cwm can miss some files doing a wipe. Then install the full galaxy task 7 again. I am using it and have no problem with world clock or anything else.
I was flashing CM9 from CM7 on my Motorola Defy, botched it up intially due to a slip of my finger which led to me to Clear the cache first. But then I restarted the entire process by Clearing Data -> Installing -> Flashing Kernel and so on...
But when I tried to clear the Dalvik Cache, the phone didn't delete it. It didn't give me a message that it wiped the cache, but it didn't say otherwise either. This led me to believe that the cache just didn't exist anymore.
As a result, I'm unable to install apps - Says there is no memory and I need to make more. Also, everytime the phone comes on is treated as the first time. It takes me through the whole process of Setting up an account and everything. This has rendered my phone obsolete.
Please help me!
Thanks in advance.
~Bloo (newb) ^_^
EDIT: Solved, reflashed the stock SBF. But is this the only solution? :O
Have you tried doing a clean install?
Honestly, any time you get issues like this where the phone gets stuck (either in a boot loop or resetting your settings every boot, etc.) it's best to just wipe/factory reset and re-flash everything.
This is also why it's important to make backups so that if something does go wrong when flashing, you can just restore and be good to go.
If by a clean install you mean starting from wiping data, flashing the ROM on again and going on to clear cache and dalvik cache; Yes I did that. But I'm unable to clear the cache.
I ought to have created a backup, didn't.
So how can I go about fixing this issue?
bloomark said:
If by a clean install you mean starting from wiping data, flashing the ROM on again and going on to clear cache and dalvik cache; Yes I did that. But I'm unable to clear the cache.
I ought to have created a backup, didn't.
So how can I go about fixing this issue?
Click to expand...
Click to collapse
A clean install seems like the main thing to do (again). If you want, you could try going back to stock.
Installing again didn't do the job. Still can't wipe Dalvik Cache and the Setting still reset on every boot.
The chief problem I have with this is that I'm in India whereas the stock baseband is Europe. So to change it I've to reboot and can't do that because it resets every boot. @[email protected]
Is it a problem with the Kernel?
I'll go back to stock, but it seems a bit complex and I'm afraid I'll brick my phone. :'(
EDIT: Felt it was important to mention that the boot screen still shows CM7.1 and not CM9
I have a similiar problem.
Everytime I choose clear Dalvik men, it looks like he freezes for about a second or two. Then you see the 'menu' no - no - no - no - yes, clear dalvik memory - no - no - no (or something like that) pop up for half a second, and then it is gone. Is this a problem in CWM? Or is it in my phone?
I have a similar problem too! When I hit 'clear dalvik cache', the CWM screen just flashed once and nothing happened, and nothing says 'cleared dalvik cache' or similar...
Me too , how to solve it? Can anyone help? Mine is samsung gio
I have an issue similar to yours with my tablet (samsung galaxy tab 4 10.1 or SM-T430NU) in which it doesn't mount /data and it doesn't let me wipe to factory. Still haven't found how to fix this.
Hello..
I had a new Note I717 and rooted it. The new ICS would work fine initially but then gradually a program or 2 or 3 or 4 ... would start crashing/not open/Phone freezing. So I tried a new ICS and after initially working fine, the same thing would happen. After this happening with 3 different ICS ROMS that were supposedly stable, I decided to go back to my original saved ROM on CWM and Gingerbread and have a working phone.. then that started the same thing happening to where I cant even open settings as that crashes upon opening.
I am thinking it must be some underlying code that has been corrupted. I am conscious to wipe both cache including the davlik cache and previous version before installing anything yet this keeps happening.
Any suggestions?
Reflash your rom but before you flash it. Wipe data, wipe cache, wipe dalvik cache and also format system. It's under mount and storage in recovery. When you have done that flash your rom.
When you're booted if you use any app like titanium backup, just restore the app ONLY NO DATA.
This has worked for me maybe it will for you
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Hi,
I really don't understand what just happened with my Galaxy S2. It was on and well, then crashed for no reason and displayed two error messages in a loop: "Falcon Pro has stopped unexpectedly" (that's my Twitter client) and "android.process.media has stopped unexpectedly". I had not even the time to click on "OK" before the other message appeared and so on, so I forced the reboot by pressing the power button.
Now the phone is stuck on the "S2" logo when booting.
I tried wiping the parition cache, it did nothing.
I have Android 4.0.something, Samsung/Bouygues original rom with Siyah kernel.
What can I do (without losing all my data if possible)?
Thank you...
Zuddi said:
Hi,
I really don't understand what just happened with my Galaxy S2. It was on and well, then crashed for no reason and displayed two error messages in a loop: "Falcon Pro has stopped unexpectedly" (that's my Twitter client) and "android.process.media has stopped unexpectedly". I had not even the time to click on "OK" before the other message appeared and so on, so I forced the reboot by pressing the power button.
Now the phone is stuck on the "S2" logo when booting.
I tried wiping the parition cache, it did nothing.
I have Android 4.0.something, Samsung/Bouygues original rom with Siyah kernel.
What can I do (without losing all my data if possible)?
Thank you...
Click to expand...
Click to collapse
Do you still have the original rom zip on your sd card? If you do, you could try a dirty flash of it on top of your current setup. Wipe cache/dalvik cache and then flash the rom zip. Seeing as you're having FC's, you could also fix permissions in recovery, can't hurt.
Edit: Note, that's attempting to not wipe your data. If that doesn't work you'll likely have to factory reset from recovery.
Hopper8 said:
Do you still have the original rom zip on your sd card? If you do, you could try a dirty flash of it on top of your current setup. Wipe cache/dalvik cache and then flash the rom zip. Seeing as you're having FC's, you could also fix permissions in recovery, can't hurt.
Edit: Note, that's attempting to not wipe your data. If that doesn't work you'll likely have to factory reset from recovery.
Click to expand...
Click to collapse
No, I didn't have any rom on my card...
I tried to wipe dalvik, fix permission, wipe cache and reboot but the problem was not fixed.
So I said goodbye to my data, did a factory reset and that worked. Phew!
Thank you