hi everyone i installed king cobra v1.3 and i had issues with phone app and people getting force closed or giving an error "co.android.htcdialer has stopped".so i thought its a rom problem and cleared everything(factory reset,clear cahe,clear dalvik-cahe,format system) and installed a new rom(clean rom).to my surprise i got the same error.so i switched to stock rom(1.85) after relocking the bootloader and this time the god damn error pops out again.wtf.and btw this only happens in sense based roms because it did not happen to me when i installed cm and aokp roms.
anyone help me sort this issue.this has been asked in so many threads but no reply
Related
I posted this on the Desire forums, but since I got no solution there, I'm trying here.
Basically the problem is that every custom rom that I'm trying to install that is not the stock Sense Froyo, ends up popping endless force close messages ("the process com.android.phone has stopped unexpectedly. Please try again") and I get no signal. Thus far I've tried Cyanogen 6.1.1, Cyanogen 7 RC1, Oxygen 2.0 and Ginger Villain 1.2. All had the same problem. I am wiping all of the Data and Cache prior to flashing.
For a detailed explanation of the process I took, you can go here: http://forum.xda-developers.com/showthread.php?t=971150
Device is HTC Desire GSM, Clockwork 2.5 Recovery. Rooted using Revoked 3,
I would love some help on this as it drives me crazy. Thanks!
Any ideas guys? This is really frustrating.
Sent from my HTC Desire
Hmm... I've found that if I force the phone into Airplane mode, the FC messages stop. Of course, I still have no signal.
So, the reason for the FC messages is due to the failure to connect to my mobile network. Now, why would I be able to connect to my network fine on the official Desire ROM, but not on any other ROM?
installed new rom from rom manager and now i get a continual android.process.media. i had cyanogen mod 7.0.0 stable. installed the old rom to no avail. i have tried various roms and nothing. where is the error?
Firstly don't use rom manager, you are much better off booting in recovery and flashing manually. Rom manager has been known in some cases to cause issues
Secondly make sure you wipe system/data/cache when moving from one rom to another.
Thirdly if doing neither of the above helps, re download the rom. You may have got a bad download.
HEY NOOB, WATCH THIS
OHH, BOOBIES
I lost my backup of my original factory ROM, I tried the RC ICS ROM and it did not work. I had cyanogenmod 7.1 alpha running but now it is very unstable. I have a series problem where the phone options screen keeps randomly popping up, without me pressing the top power button. I would now like to revert back to the stock Sense 3.0 ROM that shipped with the Sensation. If anyone can help me I would so grateful as this is a super annoying problem to deal with.
I have Revolution, Clockmod Recovery and have tried multiple ROM's and find they all have some sort of bug
Another thing, the battery life has deteriorated to the point that I can not even get more than a half day of standby with a quarter of usage.
Please explain how I can get the factory ROM back on the phone with no bugs or issues. Thanks.
have you tried any other ICS ROM? majority of them are stock with minor tweaks,
insertcoin 4.3.1 is pretty stable
Click Me!
I know you'll probably do so already, but make sure you do a full wipe before flashing the stock ROM
I tried the RCmix ICS but when I installed it, all that happened was it kept popping up a dialog box non stop and was unable to use it so I reverted back to the Cyanogenmod 7.1
Can you please let me know where I can get this ROM, I will give it a shot.
RUU Roms can be found in thread
ttp://forum.xda-developers.com/showthread.php?t=1074559
I'm running miui 2.9.14 and i always lose my status bar and the ability to answer calls when i get the message "unfortunately system ui has stopped working" and once that happens i am forced to wipe and then reflash because thats the only fix i know which is so frustrating setting everything up again just because of the problem. is it because im flashing gapps, could that cause the problem, or is it a system problem? serached through so many forms and all they say is to wipe dalvik and cache and when i do that it happens again! Please someone help me
Have you tried posting on the miui site ? I'm not familiar with that Rom but it could be a sort of "bug". You can post on the Rom site and see if others are experiencing the same issue. If they are, perhaps they likely know of a fix for this issue.?? Wish I could be of more help but I don't know much about that particular Rom. On the miui site they sould be able to direct you towards a solution . Best of luck to you!
Sent from HTC sensation 4g, S-off, rooted with revolutionary, running Viper Rom, Sense 4.1, firmware 3.33, Kernel -xxxPachaxxx PYDX-stable 2, Mugen battery 3500mah, Please press thanks
EDIT- Now i get the same problem every time i my phone shuts off. So when i flash the rom its fine, then as soon as it shuts down and rebooted the message pops up and im forced to reflash all over again because thats the only way to fix the problem! Theres got to be a way to do it.
Brad4891 said:
EDIT- Now i get the same problem every time i my phone shuts off. So when i flash the rom its fine, then as soon as it shuts down and rebooted the message pops up and im forced to reflash all over again because thats the only way to fix the problem! Theres got to be a way to do it.
Click to expand...
Click to collapse
Hey brad, you ever find a fix for this? i have this same problem, and ive searched everywhere on the web and i cant find a solution other than to use the hyperMIUI rom. But id rather use the official MIUI
Has anyone found a solution to this problem yet?
Hello there,
i've tried to find an answer to my question in the forum and on the internet but, to the present day, I'm still wandering in the dark.
On my sensation i used to have a CM10 rom which worked quite well and, in october, i decided to switch to viperS 1.4.1.
Now i wanted to try again CM10 (doesn't matter which one, i've tried both bruce's and jellybam, the problem is the same) but right after flashing the AOSP keyboard keeps force closing making the phone useless. I'm not new to flashing roms so i've tried formatting all partitions (except sdcard) and flashing again but no progress was made. I've even flashed the latest 3.33 firmware just to be sure and tried clearing the keyboard data from "settings->applications": still no result.
If i restore the viperS backup, the phone works flawlessly (even tho i'm using switftkey there, so i don't know if the aosp kb works right under viper).
Any thoughts? Is there something else i could try?
Thank you very much in advance, regards.
A.