I keep getting error message upon boot up on phone saying Process com.android.phone stopped unexpectantly?? Anyone know what this is related too?
Related
Hey Guys,
I have a G1 running the Cyanogen 6.0. It was working fine last nigh before i went to bed. Got up this morning and went to make a call and i got this error message:
the process com.android.phone has stopped unexpectedly. please try again
So i rebooted figuring i hadn't done it in a while and that would do the trick. Phone reboots and still had the error and it wouldnt go away. So i decided id just reflash, went to reboot into recovery and now its just stuck on the Tmobile G1 screen. Cant get into recovery no matter what i try, and now i cant even get back in period.
Any thoughts here? Is it finally bricked?
Specifics please.
RC1 or RC2? What recovery, etc.? Can you fastboot? Can you boot into safe mode? etc...
RC2, Amon Ra. I can fastboot but its not loading the Dream.img.
and no i cannot reboot into safe mode.
Think i got it figured out.
If your file is named "Dream.img" then that is a HUGE problem... Should be "Dreaimg.nbh"
Ok, so I was updating to KitKat last night, and at about 60% through the installation, an error message appeared and now my phone will not make it past the moto boot logo on startup. If i try to initiate recovery in fastboot, I get the message "Failed to hab check for recovery: 0x56 Boot up failed". Anybody have any idea on what I can do to fix this? Thanks in advance.
jonnydb9 said:
Ok, so I was updating to KitKat last night, and at about 60% through the installation, an error message appeared and now my phone will not make it past the moto boot logo on startup. If i try to initiate recovery in fastboot, I get the message "Failed to hab check for recovery: 0x56 Boot up failed". Anybody have any idea on what I can do to fix this? Thanks in advance.
Click to expand...
Click to collapse
download the fxz for att and install it through fastboot/rsdlite. your choice. you will lose your data. if you want to keep all of your data, you will need to know how to do some other things that will take longer to explain or test. Since idk what part failed during install it will be trying various things until something works.
Trying to upgrade Cyanogenmod something fails in clockworkmod but the phone restarts so quickly that I cannot read the error message.
¿Is there any log? ¿How could I diagnose de problem?
Thanks
So I recently unbricked with OC4 Stock Modem and Kernel. Everything was working perfectly until I click software update. The update downloaded and started to install, but after that it goes into recovery mode and ended up failed to update. The phone then reboots to the at&t logo screen, then to a black screen with error messages such as "Unfortunately, System UI has stopped", "Unfortunately, Media Storage has stopped" and "Unfortunately, setting has stopped".... I pressed the power button to see if I can go to emergency mode, but it will give me another one of those error message "Unfortunately, Emergency recovery manger has stopped" or something like that. What can I do to fix this?
i have problems with my rog 2 the bootloader is unclocked but im stuck in a bootloop
I can access recovery mode and i did a factory reset but every it tries to boot up from the recovery mode it just keeps bootlooping
I also tried to flash the stock rom but it did nothing, everytime after a flash the phone tries to boot up but always ended up in a bootloop
Sometimes in the middle of a bootloop it will show "your device is corrupted, it cannot be trusted and will not boot, pls visit bababa" or sometimes the bootloop stops and the phone just power off by itself after it shows "AVB VERIFY FAIL!!! Error verifying image, or low battery voltage. Your device will shutdown in 30s." And after 30s it shuts down and when i boot it back up the same bootloop just repeats
I really dont know what to do Pls help me? i would really appreciate it THANK YOU SO MUCH )
Ligthin said:
i have problems with my rog 2 the bootloader is unclocked but im stuck in a bootloop
I can access recovery mode and i did a factory reset but every it tries to boot up from the recovery mode it just keeps bootlooping
I also tried to flash the stock rom but it did nothing, everytime after a flash the phone tries to boot up but always ended up in a bootloop
Sometimes in the middle of a bootloop it will show "your device is corrupted, it cannot be trusted and will not boot, pls visit bababa" or sometimes the bootloop stops and the phone just power off by itself after it shows "AVB VERIFY FAIL!!! Error verifying image, or low battery voltage. Your device will shutdown in 30s." And after 30s it shuts down and when i boot it back up the same bootloop just repeats
I really dont know what to do Pls help me? i would really appreciate it THANK YOU SO MUCH )
Click to expand...
Click to collapse
did your phone have fix?
i am facing same problem of my rog 2