I was installed CustoNexus rom with CWM. I instaled and always shown "unfortunately, the process com.android.phone has stopped"
I started CWM again and instaled 4.1.2 RD MIUI rom v 0.2 alpha by Dexter_nlb same message appear here.
Now I'm stuck with no cannection with pc to restore my phone and cant start CWM to restore prev rom.
What can I do? I saw posts no one had this problem.
Related
Hi everybody.
I just tried to install MoonROM 4.2 on my SGS+ (w/ stock ROM 2.3.5 PDA I9001XXKPI) and got stuck in bootloop.
Tried a second fresh installation but nothing changed... still bootloop
I did a factory reset before installing and a wipe data/cache/dalvik after each installation.
I had feamod recovery v 1.2 that has been updated to v 1.4 by the MoonROM setup (I guess...).
The setup process went fine (no error messages)...
Any idea / suggestion?
Thanks everybody.
I know there's lots of thread asking how to return to stock but please read on. I updated to CM10 a while ago but my phone kept freezing so I changed to the ULTIMATE jellbean rom but my phone still kept freezing. Today I decided to return to the original GB stock rom to try and fix the issue.
When I flashed the ROM in Odin it got stuck at FactoryFS :S, this resulted in a semi-brick and I had to rebuild the partitions with ADB. After unbricking I installed Rocketrom from my SD card but it cannot install apps and give me a german error message saying something about encryption and factory resets every time. Now if i try to flash aything through CWM it just hangs at installing and does nothing, please help
Hello, i have my Lg optimus 2x P990H for a year now. i was running CM 7.2 stable version last night and I decided to ParanoidAndroid CM10
link below
http://forum.xda-developers.com/showthread.php?t=2097807
I downloaded the last ParanoidAndroid CM10 ROM with the new boot-loader, i used Lite by KonstaT, the latest one. i used the latest kowalski kernel.
now the phone would start,load but i got a message saying "Unfortunately, the process com.google.process.gapps has stopped" message. i clicked okay and i got "Unfortunately, the process com.google.process.gapps has stopped". i cannot do nothing after that. i tried remove the battery, hold down power and volume down button but it seems recovery mode do not exist. i don't know what else to do. I can't understand those Nvflash instructions not those'how to flash stock rom" instructions. Im using Windows 7 64bit.
anyone knows how i can get my phone back to work
1st - why 2 same threads?
2nd - cm7.2 is on old bootloader so you better download & flash pa10 for old bl if you didn't change bootloaders prior flashing the new rom...
3rd - already mentioned "all-in-one tool" if everything above fails...
Yhe only prob is u flashed the wrong gapps
If ur flashin cm10 then install cm10 gapps and of ur flashong cm10.1 use cm 10.1 gapps
This will definately solve your prob
U can find the gapps easily in the forum but choose the correct 1 or else it will show the error again
Good luck
Sent from P990 the beast phone ^_^
Recently, I've installed [JB] Ultimate N7000 XXLT4 JellyBean 4.1.2 v6 ROM. Then, again flushed stock DDLSC and rooted with philz 5.03 stock kernel.
Problem is, whenever an app is not responding, My phone reboots and then stuck on "Samsung" load screen (startup boot screen).
I'm a android app developer. Whenever I compiled and run app on my phone, if there is an error/ANR, my phone firstly hanged, than few minutes later reboot and stuck on load screen.
I never have this problem on stock ICS ROM.
here are some several times logcat errors I copied.
url-> pastebin.com/ayYS0pLi
Hello,
Its not the first time that I get something like:
"Unfortunately, the process android.process.media has stopped"
This time it appears right after I flashed CM 4.2.2 rom, then I flashed Gaaps that related to this rom.
Then in first few seconds of using the device I got this error.
1. In general - What could cause this error to appear?
2. I tried again to flash both CM and Gaaps and again an error appeard while using the device.
Any idea?
Thanks
Android 4.2 is pretty new and the CM team hasn't developed stable version yet. So it's a bit buggy.