[International / GSM] "unfortunately, the process com.android.phone has stopped"

Last Updated:

  1. dlukas

    dlukas New Member

    I posted this also at droidforums.net... I apologize in advance if this is a violation of etiquette, but I checked the forum rules and didn't see anything about double-posting. If I'm inadvertently being a total jackass, please tell me but I haven't gotten a solution at droidforums so I wanted to broaden my approach... If I get a solution in either forum I will cross-link to the other. SO:

    Ok this is NOT good. I rooted my new Galaxy Nexus and everything was fine. I then installed Titanium Backup and ran a batch restore from my old phone (a Droid X). After the restore was complete, I verified that the restored apps were in fact in my app drawer, then rebooted my phone. It boots up normally, but as soon as gets to the home screen, I get a dialog box that says "Unfortunately, the process com.android.phone has stopped." It has two buttons--"Report" and "Ok"--but the instant I hit either one of them, the same dialog box reappears, and I can't tap on anything else. I have rebooted multiple times and the same thing occurs every time. If anyone has ANY idea what is happening, I would be much obliged...

    Also: when I boot into recovery, it goes to the Android guy on his back with his chest cover opened up and a red triangle with an exclamation point. Then after a minute it goes to my home screen and I get the error message loop again.

  2. Yeahha

    Yeahha Usually off topic VIP Member

    Hey and welcome back to AF :D (I assume anyways)

    You are fine with the link IMO at least.

    I am guessing you backed up system data and tried to take it from the DX to the Gnex. If you did that could cause issues like you are having for force closes.

    As for getting the dead android for your recovery it sounds like CWM was overwritten by the stock recovery. You can plug the phone into your CPU and boot into the bootloader manually. Then use fastboot to either flash CWM or softboot CWM. If you do a factory reset in recovery it should fix your force close issues (or if you restore a backup that should do the same)

    When you get back up and running I would suggest not restoring anything other than user data using TiBU.

    There are instructions on how to use fastboot to flash or softboot CWM in the how to root sticky I am having some internet issues right now and can't link them (it should be the first post :D)
    dlukas likes this.
  3. dlukas

    dlukas New Member

    Thanks yeahha... I will let you know what happens. The primary reason I even used TiBU was to back up apps and settings... can you recommend another method for doing that that would work in going from GB to ICS?
  4. dlukas

    dlukas New Member

    FIXED! I used the instructions here and successfully restored the phone to stock. Very simple
  5. Yeahha

    Yeahha Usually off topic VIP Member

    User app and user app data restores should work fine the issue would be caused by restoring system app data. Each phone/rom will have slight differences in the system app data so when trying to restore it you can easily cause something to not work, in your cause the com.android.phone system app. If you want to have the phone rooted that in itself shouldn't cause any issues like you saw.

    Glad your phone is working again :D
  6. alcalay

    alcalay Member

    I bought a new galaxy nexus. it works ok without the sim . as soon as i insert the sim i get the same message:unfortunately the process android.process.phone has stopped. it is a loop . only when I take out the sim it works. how I can resolve the problem
  7. RiChDAiLLesT1

    RiChDAiLLesT1 Active Member

    I found the solution to this. if your using titanium backup app to restore apps and data you need to uncheck [contacts/calls] back up obviously you will loose your text messages and call log. At least everything else is restored.

Share This Page