Hi all, wondered if anyone can help.
I have a rooted note 2 running jedi x16 rom and all is fine.
I have been testing out some 4.2 roms but when ever I reboot the phone it starts fine and then after a bit I get an error message saying com.android.phone has stopped working, then my signal goes then wait a couple of seconds and it comes back and then all is fine with the phone.
This only happens after i reboot the phone.
Any help would be great.
Related
Help i went back to stock so i could fix my phone because i would keep losing my signal while calling and now im on the latest stock for the att sgs3 and i keep getting process com.android.phone has stopped , process android.process.acore has stopped android.process.media has stopped . Is there anyway to stop this from happening?
Never mind i've fixed my problem please delete this thread.
Tyler.Boston1 said:
Never mind i've fixed my problem please delete this thread.
Click to expand...
Click to collapse
I know it's been 6 months but what did you do to fix the problem?
I just flashed a stock rom via odin to try and start fresh and now I keep getting the same things basically making my phone unusable.
Hi all,
Not sure if anyone can help.
I have seen loads of posts about the com.android.phone has stopped working problem but none are like what happens to my phone.
I have a rooted note 2 and running jedi x17 rom (4.1.2 based on the standard touchwiz) all works fine no problems.
I want to go to a 4.3 rom like cm/pacman/pa etc but whenever I flash the rom and reboot after 2 min the com.android.phone has stopped comes up, but only once after I reboot, everything works fine and I can get on the Internet and make calls etc, it's just annoying.
I have even gone back to unrooted stock and started again but the problem still happens, any help would be great.
I'm on the EE network in the UK, I was wondering if Apn settings could be a problem.
try after flashing to wipe cache and do a factory reset, see if that works.
OK so i rooted my phone along time ago and it been running smoothly. I've used different roms that worked fine no issue well i recently tried a new rom it ran smoothly for about 2 weeks, then i tried rebooting it and it got stuck on the Samsung galaxy s III. i reloaded the rom it worked until i rebooted then it got stuck on the same screen again. Well 8 reloads and 3 roms later its still doing the same smh any suggestions if so it will be greatly appreciated.thanks
Do you have your phone under volted? Or have apps set to not boot at start up
I'd just Odin back to stock MD4, if you didn't take the 4.3 OTA, MK3 if you did. then start from square 1.
sounds like perhaps something has become corrupted.
I have been trying to get my phone to work for the past two days and still no success.
I flashed T-Mobile Stock De-Bloated ROM. After that I did the OTA thing and messed up my phone.
I did a bit research on xda and found out the terminal command solution and did that. But now I think messed up big time. My phone will turn on on the same tmobile rom but as soon as it starts it keeps on giving messages like com.android.process has stopped working and many more and i cant get past those messages after boot. My phone basically just starts up and thats it, i just keep on getting those messages. I lost root too and i cant goto download mode wither because it keeps on starting up even when i turn it off.
Any help would be appreciated.
GPE Lollipop 5.01 RUU.
Phone just stops working when someone calls me. it shows the call but phone error message comes up straight away.
It's been working great for weeks,just started this morning. I haven't installed anything new. Tried clear cache data of app and cache of phone with reboot. Problem reappears immediately.
I can dial out with no problems.
Anyone know what's going on? Or how to fix?