Shattered Screen? Turn Your Broken Device into a Complete Media Center!

A cracked screen usually means you’ll have to spend a hefty … more

Gmail 5.0: Material Design and Multiple Account Support

Google started to materialize many of its applications right after announcing the … more

Some of Our Favorite Features in Android 5.0 Lollipop

Android 5.0 Lollipop is the latest major revision to Google’s mobile operating … more

Sony SmartEyeglass SDK Developer Preview Released

A little over a month ago in Tokyo, Japan, Sony unveiled its new SmartEyeglasstechnology. … more
Post Reply

"Unfortunately the process com.android.phone has stopped" error message on boot

OP Dimitri Stephan

19th January 2014, 02:49 AM   |  #1  
OP Member
Thanks Meter: 2
 
45 posts
Join Date:Joined: Jul 2009
Hey guys,

After flashing the 4.4.2 firmware to my Note 3, I get the following error message once the device turns on: "Unfortunately the process com.android.phone has stopped". I can just click ok and the message goes away but it shouldn't be appearing in the first place so does anyone know how to make it go away?

Thanks!
19th January 2014, 08:52 AM   |  #2  
Member
Thanks Meter: 11
 
86 posts
Join Date:Joined: Feb 2011
Quote:
Originally Posted by Dimitri Stephan

Hey guys,

After flashing the 4.4.2 firmware to my Note 3, I get the following error message once the device turns on: "Unfortunately the process com.android.phone has stopped". I can just click ok and the message goes away but it shouldn't be appearing in the first place so does anyone know how to make it go away?

Thanks!

Only known solution I have on these issues is a factory reset. I don't think there's another way of fixing it. It is always recommended to do a factory reset before flashing a new ROM.

Hope this helps
19th January 2014, 01:25 PM   |  #3  
OP Member
Thanks Meter: 2
 
45 posts
Join Date:Joined: Jul 2009
Quote:
Originally Posted by Sinotek

Only known solution I have on these issues is a factory reset. I don't think there's another way of fixing it. It is always recommended to do a factory reset before flashing a new ROM.

Hope this helps

I will give it a try see if it works.
19th January 2014, 02:00 PM   |  #4  
OP Member
Thanks Meter: 2
 
45 posts
Join Date:Joined: Jul 2009
I've tried resetting the phone but the message still appears. I've also tried tr-flashing the rom and that hasn't worked either. What else could it be?
19th January 2014, 02:06 PM   |  #5  
Junior Member
Thanks Meter: 0
 
13 posts
Join Date:Joined: Jul 2012
I had this error message the first and the second time I booted my phone when I got it. I haven't seen it since then!

I have Hangouts, messages and S Voice disabled. Not sure if it has something to do with those apps...
19th January 2014, 04:57 PM   |  #6  
Senior Member
Thanks Meter: 14
 
118 posts
Join Date:Joined: Apr 2009
Same issue...I have tried all full wipe, full reset, stock 4.4.2, leak, but still have that problem
19th January 2014, 06:43 PM   |  #7  
my-galaxy's Avatar
Member
Thanks Meter: 6
 
69 posts
Join Date:Joined: Oct 2013
I had the same issue. I did go to recovery and format everything in internal memory. Then, installed Kitkat from PC Odin...

Sent from my SM-N9005 using xda app-developers app
20th January 2014, 06:09 AM   |  #8  
EnterLordVader's Avatar
Senior Member
Thanks Meter: 21
 
107 posts
Join Date:Joined: Jan 2013
Had the exactly same issue, I did a factory reset and it worked.
20th January 2014, 01:40 PM   |  #9  
Junior Member
Thanks Meter: 1
 
19 posts
Join Date:Joined: Apr 2007
More
On similar problems with upgrades on both the S4 and S3 this have helped:
Go to phone settings-->More, then select Date and Time. Change the date format to something else then change it back to the format you wanted. Save and go back.

I have no idea if this will help on this problem but it might be a thing to try instead of a factoryreset

Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes


Top Threads in Galaxy Note 3 Q&A, Help & Troubleshooting by ThreadRank