Captivate Force close - Captivate Q&A, Help & Troubleshooting

After recieving my 2nd phone for the random shut down problems,i flashed 2.3v6 and every thing went well untill i re-installed sim card and now it force closes with message "com.android.phone".I flashed back to stock and re flashed cognition---still the same problem.It works well at stock.Just to the left of the serial # is "1006". This must be an old exchange phone i got.
I used lag fix and rom manager for flashing, I have tried every thing i know and cant get it right
Any ideas would be great

Did you unlock your phone, are you using a non at &t sim?
Are you restoring using titanium backup? If do what are you restoring?
Sent from my SAMSUNG-SGH-I897 using XDA App

I think had the same problem the first time I installed cognition. The phone kept vibrating and giving an fc error. There was a service that was restarted every time this happened and every time com.android.phone crashed i lost the signal. This happened arround 2/3 times per minute...
I wiped all user data from cwm as someone suggested and the problem was gone. You may want to give that a try. Remember it wipes your data, though probably u have everything backed up by now...

rastanthology said:
I think had the same problem the first time I installed cognition. The phone kept vibrating and giving an fc error. There was a service that was restarted every time this happened and every time com.android.phone crashed i lost the signal. This happened arround 2/3 times per minute...
I wiped all user data from cwm as someone suggested and the problem was gone. You may want to give that a try. Remember it wipes your data, though probably u have everything backed up by now...
Click to expand...
Click to collapse
You made my life real easy,wiping the data did the trick THANK YOU

Related

[Q] launcher crash after factory reset

Hello,
I have a SGS I9000 Gt from France I think.
Everything was running good. I installed a bunch of apps when I first got the phone, checking stuff out. After playing with it for a few months I now have a good idea of what apps I would like to keep.
I decided to do a factory reset so I could start fresh when froyo does come out.
I performed three button recovery and did factory reset and wipe cache partition.
Problem is when I reboot I constantly receive "The process "blank" has stopped unexpectedly. please try agian." message, and I hit force close and it just pops right back up. TwLauncher, Daily briefing, acore, and a google one.
I did notice that in the recovery mode menu I get some red text saying "multicsc : can not acces to /system/csc/XEF/system/" But when I go through the steps to reset and clear cache, it does it and gives me a message "wipe complete"
I removed battery and sim card No sd, and tried again with no luck, every time I boot now same thing, apps keep crashing.
I hope that makes sense I don't really know what to do.
So yea any help would be great!
Thank you so much for your time.
I almost have the same problem here.
I updated the firmware with Kies, using the default firware that was found by Kies.
I guess it has to be a custom made ROM made by/for my phone service provider (Bouygues, a French company).
Upon restarting, I get the same pop-up messages. Cannot close them fast enough to use anything. My phone is not usable, though not bricked.
Ps : formerly running off-the-factory custom Bouygues rom. Rooted and using OCLF or something lag fix.
I solved at least MY problem :
Do a factory reset and wipe cache AND user data. Simple as that
The answer was actually in the [Warning!!!] Do not flash... thread. I should slap myself for not looking into it first.
Hope it solves your problem too.
Thanks for the help, but how do you how did you wipe user data? Maybe I am blind but I don't see it?
I think I did that when I did the factory reset. When I do boot up however, my original unlock pattern is still set...so I don't know wtf is going on.
FIXED!!
I used Kies Registry Patcher v.1.6.0.0
then reset user data and cache WORKS GREAT AND I HAVE FROYO NOW!!

[Q] My phone reboots after I receive a txt msg

I have an AT&T Nexus One. Got it since it was first released for AT&T never had any problems untill now.
I can do anything without problems except when I receive a text message my phone reboots. I tried factory reset no luck. I formatted my sd card wiped my phone and updated my rom from cm6 to the stable version of cm7 and it still reboots after I receive a text message. I searched google and found other people with the same problem with various android phones but I haven't found a fix yet.
I was hoping some of the genius here at xda dev could help me out with this.
My phone is out of warranty and it's unlocked/rooted.
Please help if you can.
Thanks,
Rick
*********************************************************
EDIT: Just found out that it restarts when I receive phone call aswell.
*********************************************************
This exact problem is happening with my Droid Incredible. I ran CM7 for quite a while and was just living with the problem... it doesn't happen every time I receive a text, but maybe half of the times it triggers my phone to reboot.
I have tried the following, but the phone continues to reboot on receiving texts:
- moved data off of SD card and formatted card.
- wiped data/did factory reset of CM7.
- installed MIUI rom
- wiped data/factory reset of MIUI
- deleted all backups
I'm currently running a completely wiped MIUI phone and it still reboots. I am at a loss as to what to try next. Did you ever solve your problem? Does anyone else have any suggestions?
You could try a new SIM...?

[Q] process com.android.mms stopped unexpectedly

Hi,
I have a problem,,, I have a rooted tab, I installed some apps... and recently I have been getting "process com.android.mms stopped unexpectedly"... after which, my WiFi doesn't work, Bluetooth doesnt work and some apps start to force close.
I tried to remove the apps that force close by themselves like PowerAmp but i am unable to unistall! when I try to unistall, Superuser also forcecloses.
I have wiped the device clean 3 times so far, re rooted, reinstalled the clockworkmod etc... it works for a couple of days then starts crashing again!
is there a way to find out what is causing this...
thanks.
Are you using a t-mobile tab? And if so are you using it as 2g + phone?
I use to have the same issue. It didn't stop happening for me until I started using a custom rom.
I am using a custom Rom. It was working fine.
I suspect it is an application I am using that is causing this. but I cannot figure out which one!
Guys, someone please help... After I reinstalled the RoM etc... I just got the same msg today!
Process com.android.mms crashed and followed by whatsapp and photobucket and wifi doesnt work etc etc..
Are you sure your flashing the rom correctly, it should fix these errors, or download the rom agan, maybe your download is corrupt
Yes... it has been working since my last Flash which was April 15 without any issues.
I downloaded some apps from Market yesterday and today I restarted the Tab and when I did I started getting the MMS error again.
When this happens, I am unable to Uninstall any apps, clear cache or data from Settings/applications, or do anything...
Even my previous Backup which was done in Recovery mode is not there :S
There must be some fix for this... Its really frustrating.
I deleted MMSSMS.DB file and still I get the same errors... Seems like an app that I installed received a msg or something and that msg is corrupt... If I didnt know any better, I would think its a virus!
try a factory reset , i hope your problem will go

[Q] Galaxy S i9000 won't factory reset and force closes frequently - now with logcat

Hello all,
please forgive me first of all because I've had very little sleep due to this issue. And its a long thread, but more detail is better generally I believe.
First, some background, and unfortunately, it starts with my wifes phone.
My wife has a Galaxy S GT-i9000 on Orange in the UK. She has had it, probably about a year maybe at most. She has a few apps that she has downloaded but nothing major and on first looks when I got it nothing I expect would cause this issue, just facebook etc.
My wife came home and said, my phone keeps coming up with a message saying force close. Ahh, I thought, some apps gone nuts, but alas, it appeared to be many apps including Maps, Google Upload (I assume this is a system process), Facebook Katana and many more, probably about 20 Force Close messages pop up one after the other and it lags whilst trying.
Odd, I thought, I also noticed the icon for one of the apps on her homescreen had changed to the default White and Green one with the android on it.
I suspected something had gone wrong (obviously), I asked if she had rebooted it and she said she had. So, I rebooted it again, just incase. Same problem.
I then thought it might need an update, it was running official Kies 2.3.3 (or was it 2.3.4, I forget) so I plugged it into my netbook and ran Kies, had to update that as it didn't have the latest application update. I then started the firmware update, after backing up the phone using Kies.
Halfway through the update, Kies popped up a message saying something went wrong and that I had to unplug the phone, take out the battery and reboot. Odd, I thought as the phone was telling me to not doing anything. I waited a minute, nothing further happened, so I did this. Then I got the Black Screen of Death with the phone, the dots and the computer screen.
Crap!!! I thought, I managed to get into Download mode, and reflash it using what I believe was an official ROM using Odin. I then rebooted, and found that it STILL had the data on it and it STILL was doing the force close. At least I had it back to "working" though so I was mildly happy.
I then did a factory reset using the menu system, erased the USB storage (there is no external SD card in her phone) and rebooted, still force closing but prompting me to setup again. Weird. I went through the setup slowly, as every second or so a force close would popup, then when I completed the setup (which still had the wifi settings, account settings etc in it) the System Setup crashed with Force Close. I then rebooted and got to the Home Screen, but still crashing.
I rebooted and used the recovery screen to clear the cache and factory reset, despite the warnings I will lose everything, nothing was wiped.
I tried to update using Kies again but it tells me that the firmware/device is not supported. I am now trying to see if I can use Odin to install a Kies supported firmware. So that I can then try an update using that again.
Anyone got any suggestions, at present, my thoughts are, I was going well within the realms of warranty up until I reflashed it using Odin to try and get back in as I'd only used Kies to update and the issue "just started happening" without my missus doing anything.
There are no signs of damage on the phone and she tells me it was just sat on her desk all day.
So, my question is, what now? I'm of the opinion based on the above that if I can't reflash a warranty supported Kies update, then maybe a custom ROM will be worth a shot to see if its a hardware failure or if its software. I just have never had an issue like this with my HTC Desire and I've ran many custom ROMs and standard ROMs on it.
I do have the .tmp file of the update Kies downloaded, and I also have a Binary folder which has some file inside a couple more folders but its not a .tar or a .zip because when I try renaming it (after a copy) it won't open.
So, suggestions on a postcard, thanks if you got this far through this nightmare. All help massively appreciated.
Edit: it appears to be the same issue as this: http://forum.xda-developers.com/showthread.php?t=822238
I'll try some of their suggestions. Today I also did the *2767*3855# today which I found after a bit more searching. Same problem after a reboot. Force close and data still there.
I've tried and tried again to do various solutions for this, I've even ran a logcat using adb to see if I can see the problem. I suspect its a Dalvik Cache issue in that its unable to write to it for some weird reason.
I've downgraded it to Froyo following this guide: http://forum.xda-developers.com/showthread.php?t=1100906
It now detects in Kies and offers me a firmware upgrade. I suspect it will die again though if I try due to this Dalvik problem.
Wiping cache does not wipe the cache. Everything still appears to be there on reboot as mentioned above.
Here is a copy of the LogCat with Java errors all over it: http://leenukes.co.uk/downloads/logcat1.txt (its quite long)
I guess nobody knows. Today I will speak to Orange to try and get it fixed or replaced.
Sent from my HTC Desire using Tapatalk
We've been told it is beyond repair. We will see what they say when we go back into the shop. Its still in warranty so I don't see why they won't replace it.
Sent from my Galaxy Nexus using Tapatalk
I have a friend with a Galaxy S from Orange Romania and suddenly the phone kept showing Force Close on every App. He had 2.2.1 if I remember right. He whent with the phone to an Orange Shop and they only do a factory reset but data was not wiped.
So what i have done for him:
- start the phone in Download Mode
- start Odin with repartition check and XXJVT (2.3.5) firmware with 3 files (code, phone and CSC) + pit file .512
- after reflashing the phone does have all tha data, so i resarted in Recovery Mode and done a Factory Reset and a Cache Wipe
- i flashed Speedmonde Kernel k16.10 and do again from Recovery Mode a Factory Reset, Cache Wipe and Davlick Wipe.
On reboot the phone was CLEAN. No force closes for a week now.
Sorry for my English hope it helps!
ZiDanRO said:
I have a friend with a Galaxy S from Orange Romania and suddenly the phone kept showing Force Close on every App. He had 2.2.1 if I remember right. He whent with the phone to an Orange Shop and they only do a factory reset but data was not wiped.
So what i have done for him:
- start the phone in Download Mode
- start Odin with repartition check and XXJVT (2.3.5) firmware with 3 files (code, phone and CSC) + pit file .512
- after reflashing the phone does have all tha data, so i resarted in Recovery Mode and done a Factory Reset and a Cache Wipe
- i flashed Speedmonde Kernel k16.10 and do again from Recovery Mode a Factory Reset, Cache Wipe and Davlick Wipe.
On reboot the phone was CLEAN. No force closes for a week now.
Sorry for my English hope it helps!
Click to expand...
Click to collapse
Sound advice there mate, other thing I would have done is in recovery mode before the ODIN flash I would have format sdcard, making sure you have removed BOTH the external sd and the sim card, as it can wipe them as well.Then flash through ODIN as per instructions above.
Using JVT I would flash either speedmod or semaphore 2.1.1 which I personally use.
Happy flashing!!
turns out it was water damage and some parts corroded.
Its going to be claimed for on insurance.
Sent from my Galaxy Nexus using Tapatalk
Hello all,
the phone came back from repair yesterday, yay!
the phone now however, doesn't appear to lock onto a mobile signal for very long. Boooo!!!
After sending off for repair using insurance, we got the phone back yesterday but it now appears to be broke in another way. It won't lock on to a mobile signal, wireless is fine but data network and sometimes just mobile signal is patchy and keeps dropping.
I've just reset it to factory defaults, same problem. What I did notice, which is odd is that since it came back from repair, its now unlocked and I can put another networks SIM card in it, same issue there too so I know its the phone now.
I'm going to scour the forums to see if anyone else had/has issues like this, it is running the latest firmware now and a full wipe really did fully wipe it this time, as opposed to last time with its issues due to water damage. One step forward, two steps back?
Its going back to the insurance company. Especially as Orange were suggesting that we pay £70 for a new handset.
Absolute fool I had on support today, yesterday I at least had someone sensible.
Sent from my Galaxy Nexus using Tapatalk
SGS force close problem
Hey guys i m facing a similar solution in my samsung galaxy s. After deleting all the contents and uninstalling the applications, I m getting them back after rebooting and all applications has to be force closed after rebooting.
Please help me to solve this problem
Signal issues
leenukes said:
Hello all,
the phone came back from repair yesterday, yay!
the phone now however, doesn't appear to lock onto a mobile signal for very long. Boooo!!!
After sending off for repair using insurance, we got the phone back yesterday but it now appears to be broke in another way. It won't lock on to a mobile signal, wireless is fine but data network and sometimes just mobile signal is patchy and keeps dropping.
I've just reset it to factory defaults, same problem. What I did notice, which is odd is that since it came back from repair, its now unlocked and I can put another networks SIM card in it, same issue there too so I know its the phone now.
I'm going to scour the forums to see if anyone else had/has issues like this, it is running the latest firmware now and a full wipe really did fully wipe it this time, as opposed to last time with its issues due to water damage. One step forward, two steps back?
Click to expand...
Click to collapse
Sounds like a modem issue, where the techs at Orange put in the wrong modem for your firmware. I did the same thing when I upgraded from Froyo to Gingerbread.
Alternately, it could be a broken external antenna connection as a result of the corrosion from the water damage. Google "no signal fix" and look for a site that ends in .uk
Just a thought for others who come across this problem.
I

[Q] Reorganizing internal process error

Hello,
I had my p970 for about two years with no problem, I switched between roms pretty often but about a month ago this error started to appear.
when I get a call and I try to answer the mobile wouldn't respond and it keeps ringing till it turns to a missed call, it doesn't matter if it was originally locked or unlocked, and when I try to make a call myself afterwards I get this error "reorganizing internal processes. please try again later" and only rebooting the device fixes it.
I tired everything I could think of, tried flashing a different version of the firmware, different baseband, different rom, going back to stock unrooted with gingerbread, and also tried updating to ICS...nothing worked...
I always had v20c as the firmware I flash when needed, this never happened before but now it's happening all the time...with almost 80% of the calls I get! and only recently it started to happen on its own and I'd only realize if I tried to make a call.
I'm currently on IZS 1.1 which is the rom I had when the problem first appeared. It started two weeks after using it though.
I'd really appreciate any help to fix this. It's frustrating...

Categories

Resources