last week after messing up my phone running a camcorder fix instead of the rom my phone would not boot and would not boot into recovery. my friend ended up having to run the ruu for the phone and after that i keep getting the com.android.htcdialer has stopped or com.android.phone has stopped. i had my friend re root my phone tried several different roms and had the same error. i have tried every fix i could find online if anyone has had this issue and fixed it please let me know
thanks
karl
http://forum.xda-developers.com/showthread.php?p=39311339
If you were using CWM, try that.
Sent from my Nexus 7 using XDA Premium HD app
Related
Hey everyone,
As you can see, I'm new here, and did my best to search (both here on the forum and elsewhere) and tried to put this in the right place. If I did something wrong, if you could politely let me know, I'll fix it.
As far as the problem goes, a couple of days ago, my phone just started having strange issues. All of a sudden it's been telling me all sorts of things are crashing, and force closing them. It's also been randomly telling me there's no sim card, and wont let me make phone calls. I'm also not receiving incoming text messages.
It's a Samsung Captivate, running Cyanogenmod 7, Mod Version: 7.0.0-RCO-Captivate-Kang
I'd try and grab screen shots, but Shoot Me can't get root privileges.
EX: "The application Email (processcom.android.email) has stopped unexpectedly. Please try again."
^I get a similar one for the messaging app, as well as facebook, but they flash too fast to read in their entirety.
Ex: Dolphin has Crashed
An unexpected error occured forcing the application to stop. Please help us fix this by sending your error data, all you have to do is hit report.
Here's what I tried to to:
I've tried restarting, pulling the battery, and a hard shut down and restart, but no dice. I figured I'd have to restore to the stock firmware, then tried to do this with the captivate toolbox, but no dice. I think it's because Cyanogenmod 7 makes everything think its a Nexus One. So what do I do? Should I try and update cyanogenmod? restore using Odin One Click?
This was my first flash, and it'd been working okay for a few months, but all of a sudden I got a ton of problems.
If you need more info, let me know.
Thanks Everyone.
Do a wipe data/factory reset in cwm. Do not restore anything and see if that helps.
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
You can always flash stock with Odin.
bulletproof1013 said:
Do a wipe data/factory reset in cwm. Do not restore anything and see if that helps.
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
Click to expand...
Click to collapse
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
Using CWM worked, or it seemed to anyways. Thanks for the help guys.
Does anyone have any idea why it was doing that?
Sometimes our data with Applications and other programs may have a conflict with one rom to another.it just does.now I have found on cm7 that sometimes it can be just about anything.I just like to start fresh on any rom.
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
Please look around the forum before starting new threads. There are stickies in the Q&A subforum for ROM-specific questions, which is where this should have gone. Always search before posting a new thread.
I am currently running Sky ICS and I am able to flash a new update just fine. After settling in and restoring all of my apps I will restart. After restarting my phone will just start freezing up. It seems the media scanning is delayed when restarted. I have already tried the Odin method. I even wiped EMMC. After starting completely fresh it is still having the issue. My phone is completely unusable (no texting because of media scanner not working correctly?, data doesn't work either). Anyone else having this issue?
eshewski said:
I am currently running Sky ICS and I am able to flash a new update just fine. After settling in and restoring all of my apps I will restart. After restarting my phone will just start freezing up. It seems the media scanning is delayed when restarted. I have already tried the Odin method. I even wiped EMMC. After starting completely fresh it is still having the issue. My phone is completely unusable (no texting because of media scanner not working correctly?, data doesn't work either). Anyone else having this issue?
Click to expand...
Click to collapse
I have seen a similar issue. Haven't found a solution yet unfortunately...
Sent from my SAMSUNG-SGH-I727 using xda premium
Sheolrock said:
I have seen a similar issue. Haven't found a solution yet unfortunately...
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
So I've been messing with it and decided not to restore all my pictures. Restarting seems to work just fine now. Had about 300 pictures.
maybe try thederekjay's wipe script?
orlandoxpolice said:
maybe try thederekjay's wipe script?
Click to expand...
Click to collapse
Already tried that. The only thing that seems to work is wiping EMMC and not restoring all my pictures. Basically just starting fresh.
I seem to have solved my problem though i'm not sure that it will help you. I restored back to a stock backup I have then installed sky ICS fresh and it has been stable for 3 days now.
Sent from my SAMSUNG-SGH-I727 using xda premium
I just installed the TEAM VIPER 1.1.0 ROM and the error comes up one first start.. " Unfortunately, the process com.android.phone has stopped " and its an infinite loop... .. very annoying.. cant use my phone.. please if anyone can help ????
Bad download maybe?
Download rom again, full wipe, flash. Let phone sit for a couple of minutes on first boot before you try and set it up
If new download don't work try flashing a different Rom, full wipe .. I had NUMEROUS problems with that new update myself. For some reason. It's a great Rom I just couldn't run it after the update my device kept freezing 5to10 times a day! Also weird stuff like half a screen would appear! I thought my device was breaking but after I flashed a new Rom, all the problems are gone! Many people run viper with out problems but for some of us I don't know why it gives issues. It's about 50/50 some have no problem At all. Before the update everything was wonderful! After the update it got so bad I had to get another Rom.....I'm not sure why I'm not over or under clocked, I have no rogue applications, I did clean installation, wiped even re downloaded, wiped again and still my device froze, my proximity sensor would stick , my screen would go half black, I would get vibrating while talking on calls it was very strange! Viper is a great Rom if you can run it without issues ..I guess I was one of the unlucky ones..I did nothing different from the first viper which ran beautifully. It's just after the update this started happening. My device is running perfectly now on a different Rom. Very strange.
Sent from my Sensation Z710e using Tapatalk 2
Wipe everything! And format all but sd
Sent from my HTC Sensation using xda app-developers app
Can't activate-get "Unfortunately, the process com.android.phone has stopped."
Bought an mx600 on swappa. It came rooted with cm10 on it. I wanted some aokp features so I flashed aokp milestone 6.
I just brought it in to Verizon to activate, they set it up for 4G, and when we went to settings, activate device, it gave the error : "Unfortunately, the process com.android.phone has stopped."
I tried it worth and without the sim card (always powering down to swap it in or out).
I thought it might be the rom so I flashed back to cm10 and now it is giving me that error on top of the lock screen right when it boots.
Anything anyone has heard of before? This is pretty frustrating, I am setting this up for my grandparents and am only here another two days.
Sent from my Nexus 4 using xda premium
telekinetic said:
Bought an mx600 on swappa. It came rooted with cm10 on it. I wanted some aokp features so I flashed aokp milestone 6.
I just brought it in to Verizon to activate, they set it up for 4G, and when we went to settings, activate device, it gave the error : "Unfortunately, the process com.android.phone has stopped."
I tried it worth and without the sim card (always powering down to swap it in or out).
I thought it might be the rom so I flashed back to cm10 and now it is giving me that error on top of the lock screen right when it boots.
Anything anyone has heard of before? This is pretty frustrating, I am setting this up for my grandparents and am only here another two days.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
I'd put it back to stock and activate that way considering it is for your grandparents and dought they are going to be flashing any ROMs.
Sent from my Xoom using xda app-developers app
serranom said:
I'd put it back to stock and activate that way considering it is for your grandparents and dought they are going to be flashing any ROMs.
Sent from my Xoom using xda app-developers app
Click to expand...
Click to collapse
Its rom related. Change it to oteher and check . On stock it will work if worked before...
"unfortunately, the process com.android.phone has stopped."
Everytime i start using the phone, that happens. The error occur and I lost my network and it reconnects.
I cannot receive calls. It can't be radio since I can still text.
CM10.1 Works fine for me. I don't know why but right now, all sense rom kills me...
I tried viperxl, senseless, cleanrom, and magiorom.
ALL OF THEM gives me the error.
PLEASE HELP ME. I would stick with cm10 or aosp but they give me HORRIBLE BATTERY LIFE
I need to go back to sense.
First thing to try is uninstall Google+
Then reinstall it. If that doesn't work you can try fix permission in recovery and then reboot the phone.
Sent from my HTC One XL using xda premium
Venomtester said:
First thing to try is uninstall Google+
Then reinstall it. If that doesn't work you can try fix permission in recovery and then reboot the phone.
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
nope fixing permission didn't work. and my senseless rom didn't came with google+
Fixed, flashed CWM recovery and flash the rom and it worked. I guess TWRP wasn't properly flashing the rom phone configuration.
No its a bug that happens when going from some version of cwm to twrp. You have to flash a non touch cwm then go to twrp.
Sent from my One X using xda app-developers app