Hi all!
Recently i rooted my S5 due to touchwiz being too slow to function properly. The first rom that I installed was the unofficial cyanogenmod 13. After my third reboot, the message com.android.phone has stopped appeared, and I my phone rebooted constantly. I had access to my phone for about 3 minutes before the message comes up again and It crashes. I then installed the mokee rom, and the same problem has occurred after a few reboots, with the same time interval for the message to pop up. I have tried solutions such as resetting the phone cache etc and even solutions offered by this thread, http://forum.xda-developers.com/show....php?t=2436229.
Could any one offer a solution that may help?
All responses are greatly appreciated!
Related
I have been using CM9 on my phone for around 8 months now. But it has started giving me problems recently.
The other day, I was using Google Maps and I suddenly started getting the error "Unfortunately android.process.media has stopped working". This started happening with every other application too.
I can now no longer use my camera.
I can now no longer upload anything from the gallery.
GMail doesn't work any more.
I literally get the error every 15 minutes or so. And usually when I am receiving a WhatsApp message.
I have tried fixing it by moving a lot of apps from the sdcard to /data/data using the Datafix. But it hasn't helped me at all.
I am away from home for another month due to work and I have very limited access to flash a new ROM again.
Is there a work around for this?
Please help.
Hey,
I don't think there's any other fix for this other than going back to stock 2.3.6 and then reflashing CM9 again...
EDIT: just read that you're away from home.
Okay, boot into recovery, wipe data+cache+dalvik, and try flash in CM9 again. See if that works, if not, well...
Sent from my GT-I9000
OK, so, I'm not to experienced with all of this but for the past few months my phone has had an error message pop up some times that says "unfortunately the process com.android.phone has stopped" when I am trying to send a text. I have no idea what could be causing it and I don't see any help for this topic any where. Some similar problems all you have to do it wipe the cache and the dalvik cache and it that fixes it. I tried this and it seems to work for a little under a week and then I have the problem again or it doesn't help at all. I was just wondering if you guys had any suggestions for this or any thing. I would even be open to switching roms as long as they have a dark thing like slimbean. Any help would be greatly appreciated.
First of all, hello all!
I'm a new member here.
So, what's the problem? Well, I recently rooted my Galaxy Tab 4 SM-T530 (WiFi only version) with Kingroot. Then I installed Cyanogenmod from the thread listed at the ROM section. All was working fine up until I decided to flash the GApps.
I chose the newest versions (both Zero and Mini for 6.0) but none of them worked.
Flashing went well. The problem was after booting.
After the first boot, I'd get caught in an endless loop of errors stating that "Unfortunately, Setup Wizard has stopped working". I couldn't do much other than rebooting. But then, I was greeted with yet another problem: it was stuck in a boot loop. Basically, after saying that it "Prepared Google App" and some others, the tab would repeat the process in an infinite loop. I left it for half an hour to do so, but the problem persisted.
Keep in mind the fact that I installed the newest version of Mini GApps package provided from that thread.
If any of you can help me out with this, I'd be very thankful, since this is the same time I install a custom ROM, and I really don't want to come back to the old Samsung ROM
http://forum.xda-developers.com/tab-4/development/rom-slimrom-5-0-1-alpha-0-7-t2963906
This is from where I installed all things needed.
Try again, this time flash both zips at the same time and not doing anything in the middle of both flashes. The usual cause of the same error in my other s3 is booting the ROM up, going back to recovery, then flashing GApps.
I never did anything else. Now I wiped data/dalvik/system/cache, reflashed the ROM and now just finished reflashing both zips in TWRP (first Mini then Zero, can't do them at the same time).
Now, I'm pretty much 'fingers crossed', as this is what an error told me. Pretty much tried to flash the zips without wiping anything/reflashing the ROM. That's why I went for a clean install.
EDIT: it didn't work at all. Still caught in the same "Preparing app x" boot loop. Now I'll let it run for 6 hours and see if not my own impatience is the problem.
EDIT 2: For some reason it took ages to boot up. Now, when I finished booting, I saw that the Play Store, Quick Search Bar and the Google Services weren't working at all. I tried to manually update them, but ended up in an agonizing loop of "Unfortunately, Google Services Framework has stopped" errors. Again, this leads me into thinking that the GApps from that thread aren't working.
Unlocked boot loader, installed DK S7 Edge/Note 5 INSTALL THREAD SMS/MMS Rom.
Rom is great but getting error When someone calls me or when the call is ended. I get the following error "unfortunately the process com.android.phone has stopped"
I've force stopped the phone app...all 3 of them, clear cache and data..and rebooted,, still the same.
Appears to be common right from verizon when the took the S7 and updgraded it to 6.0.1
http://forums.androidcentral.com/sa...ly-process-com-android-phone-has-stopped.html
http://thedroidguy.com/2016/05/fix-...ocess-com-android-phone-stopped-error-1059365
Didn't know if someone else had these concerns as well as a fix.
Hello XDA community,
I would never post on here unless it was a last resort. I tried everything with this phone to have it rooted. I rooted successfully in Android 10, 11 all of them worked, but all of them failed over the same issue after a few days which ill describe below. On TWRP + Stock Root Rom, the logs read something about "android telephony". This time around the logs (Adb logcat) is huge and I can't find what causes the bootloop. I am sure it could be fixed somehow.
I Installed Lineage OS 18.1 successfully. In all root roms (phone is dual sim) and even in normal rom, after 2-3 weeks the phone will crash and enter into bootloop. On LIneage OS 18.1 it started after 2-3 days.
Strangely this seems to be related to using express VPN (not sure why). Pressing reconnect on this software causes always the first bootloop. From there on phone repeats the bootloop every time it's rebooted, non stop. It restarts itself and bootloops again.
I have tried installing every rom there is available including root official rom. Nothing fixed this problem.
I am to where i will definitely provide financial compensation if anyone can really help me find out what this is and stop it. I cannot send the phone to OnePlus as they will not provide help over these matters.
I Need liberty of root user without all the harassment of the bootloop.
Now the phone is at LineageOS recovery and lineageOS 18.1 build. It WORKS in safemode, but it bootloops only in normal mode. There is nothing I know to do to stop it.
So I have access to every other function except the normal use of the phone.
Please advise.
It's one of the apps running in normal mode. Seek and destroy... obviously it runs at start up, that should help narrow it down.
Thanks for the help, but I have attempted this to no avail. I have removed all user apps but still the issue persists.
This has also happened on every rom I installed, after about a few days or weeks.
Could it be some remote command is used to terminate the handset? How can I diagnose what is happening?
What if you reflash without Google apps?
LR7875 said:
What if you reflash without Google apps?
Click to expand...
Click to collapse
I have tried, it was without Google Apps to begin with.
I am going to repeat same process and see if the next one bootloops too.
The strange bug occur when VPN connection was activated/deactivated. AFwall was also enabled, running as admin. Then this persist even when I uninstall all apps through safemode ADB.