Take the 2-minute tour ×
Android Enthusiasts Stack Exchange is a question and answer site for enthusiasts and power users of the Android operating system. It's 100% free, no registration required.

I installed a CM7.1 over a custom 2.3.5 installation on my Samsung Galaxy S I9000. I did a full wipe through CWM as well as wiping the cache, as explained in the SGS installation instructions. The installation completed without any errors, but when the phone booted the process com.android.phone force-closed. When I dismissed the error, it force-closed again within less than a second, and continued doing so.

I rebooted into recovery and made sure to wipe everything, but nothing helped. I finally reverted to my previous ROM in disappointment.

What could be the causing these force-closes? How can I install CM7.1 successfully? Is there any specific kernel I should install? Any specific modem?

share|improve this question
    
FCs are often caused by an Java exception. Those exceptions get loged in the system log. It sure would be helpfull if you could show us that system log. –  Flow Nov 21 '11 at 19:21
    
I had more serious problems the first time I flashed CM7.1, and flashing it again after I had cleared the data worked. (Make sure you wipe data and not just cache.) That said, I had other problems with CM later and went back to my old ROM. –  Matthew Read Nov 21 '11 at 19:29
    
@Matthew: What serious problems did you have? Was this with the stable version? –  Nathan Fellman Nov 21 '11 at 19:40
    
Partition issues and resets. Then a few days after the successful install most of my apps started crashing :P and yes, it was the "stable" release. –  Matthew Read Nov 21 '11 at 19:56
    
@NathanFellman did you solve your problem? If so, could you add your solution as an answer (and accept it), so it may help others encountering the same issue? –  Izzy Aug 26 '12 at 17:32

1 Answer 1

up vote 0 down vote accepted

After researching this in local forums, it turned out to a SIM card issue. My carrier had a series of yellow SIM cards that for some reason caused this problem. I had my carrier replace it, and I've been on CM ever since (with a short break for AOKP).

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.