This first happened on GSB 1.9, then I wiped and flashed the newest version and still got this same error. Wiped and flashed gingerTazz and it happened again.
The problem seems to be when rebooting the phone. After a fresh wipe/flash/formatted sd card this still happens
The process com.android.phone has stopped unexpectedly. Please try again.
Obviously I did some research and found a few different answers, but my real concern is why this is still happening after reflashes/wipes/switching roms, and it's always after a reboot. The phone shows no service and can't connect to service, but has had no problems 2 days prior until I had to turn it off.
I've also tried wiping dalvik cache before rebooting, wiping dalvik and fixing uid mismatches, and wiping data+dalvik. Still happens, anyone know what the deal is?
(this is all on gingerbread roms, so I guess I'll flash a froyo one in the meantime, but this just recently started happening, and i've been on 2.3 since the roms started rolling out.)
My fiance had the same problem and he wiped the dalvk and data a bunch of times one right after the other due to he didn't really know what he was doing and then flashed ginger tazz and its worked ever since. I know that doesn't help much but maybe some one else will answer.
Sent from my Ginger Tazz using Tapatalk
Might be a good idea to delete Android secure from the SD card. Then wipe and reflash the Rom.
Sent from my DINC using XDA Premium
Related
Hey guys,
little frustrated here as i am having some issues. I have the ERIS running Gin tazz CM7, and when the phone is on, it runs flawlessly, but as soon as i reboot or turn the phone off, and turn it back on, i get a force close error message stating "com.android.phone" has stopped working, and pretty much makes the phone useless. I then have to wipe and re-flash the ROM and everything is fine again, until I reboot/turn phone off and boot back up.
I experimented a little last night, and put the phone in airplane mode and shut the phone off, rebooted, and turned it off of airplane mode when it was done booting, and i did not get that message. I thought i had found the cure. Rebooted again and got the same error message! I'm pulling my hair out, not sure what else to do. Has anyone heard of this issue, and if so is there a quick fix? FYI i used another ROM and it did the same thing, so i do not think it is the software. It is almost as if on the reboot it can't load the necessary "codes" to get the radios up and running again. Any feedback appreciated!
p.s i attached a screenshot to let you guys see what the error message looked like!
do you do full wipes of data and dalvik for every flash? The same issue hit me one time when I had not done wipes of both. I went back and wiped both, dalvik I just went ahead and wiped three times. Idk that three times matters but I wanted to make sure I was good to go and I know I had seen workshed post before about 3x wipe of dalvik. When I went back and wiped everything like that and re-flashed everything went back to normal for me.
The wipe of Data & Dalvik is a critical step. Like the poster above me, I've heard the "3 times" suggestion and I'm not sure why 1 versus 3 would make a difference. However, just to be safe, I have started wiping Data & Dalvik 5x each, each time I flash. It's most likely just overkill & paranoia, but hey, I've had no issues.
Some roms, depending on what are are upgrading from, may also require you to delete a folder from your sd card. For example, as Workshed states in his GSB v3.7 thread,
"If you're coming from a cm6 or 2.1 ROM, make sure you delete .android_secure folder on your sdcard before flashing."
http://forum.xda-developers.com/showpost.php?p=11178912&postcount=1
Hope this helps!
Having similar problems. Only wiped once, I'll try it a few times and see how that goes.
I've tried the Liquid Thunderbred 2.2 and 2.3 and I can't get either if them to work. I get a constant android.phone force close. Using 627r and I do a full wipe procedure. Any ideas? I've heard good things about this rom and would like to try it out.
Did you try format system in recovery. Do after you wipe data and cache.Then load ROM.
Good luck it is nice ROM
Sent from my HTC ThunderBolt using XDA App
i am having this same issue regardless of what rom I use. It fc and then it acts like it has lost the 3g signal. I am going mad here with trying to figure out what is causing it to crash when I try calling. It isnt consistent either as some numbers arent crashing. any ideas?
I had issues with mine until I did a full wipe, loaded the radio first (MR2.5) followed by installing LTBv2.3. Make sure the back is on too. I kept wondering why I only had a x1.5 connection for a couple hours, thought I had screwed up installing the radio. Eventually I popped on the backing and it was fine.
A lot of what your experiencing is either a radio issue or a full wipe issue,,, I wipe data, cache, and dalvick cache at least twice and then load whatever radio that the rom suggests and when the rom loads up give it time to normalize, dont rush it. Be careful reformatting anything in cwm it will erase data on your SD card.
nrbowler said:
I've tried the Liquid Thunderbred 2.2 and 2.3 and I can't get either if them to work. I get a constant android.phone force close. Using 627r and I do a full wipe procedure. Any ideas? I've heard good things about this rom and would like to try it out.
Click to expand...
Click to collapse
i have a serious random reboot problem when my phone is in idle. here is what i did...
while on Alien v.3 i .sbf flashed the 1.97.00 radio and then flashed Kholk's kernel
then...
in romracer's CWM:
wiped dalvick cache
wiped cache
wiped data/factory reset
flashed Alien v.4
reboot
skipped blur setup
waited 10 minutes
went through set up (reset apn to default, added gmail account)
reboot into CWM
wiped dalvick cache
wiped cache
flashed Alien theme 4
reboot
restored apps
reboot into CWM
wiped dalvick cache
wiped cache
flashed Kholk's kernel
reboot
i started getting random reboots. i cant figure out what the problem is. i tried flashing a different theme, and still got reboots. tried flashing the stock kernel and still got reboots. i tried re-flashing Alien v.4 and not restoring any apps and still got reboots. argh... any ideas?
can the radio cause a reboot issue? i really dont think its a ROM/Theme thing since noone else seems to be reporting the same problem... am i noobing this whole mod process?
this happens to me too. Turn your wifi off when you aren't using it. Mine only reboots when its in standby with wifi on
fischwrap said:
i have a serious random reboot problem when my phone is in idle. here is what i did...
while on Alien v.3 i .sbf flashed the 1.97.00 radio and then flashed Kholk's kernel
then...
in romracer's CWM:
wiped dalvick cache
wiped cache
wiped data/factory reset
flashed Alien v.4
reboot
skipped blur setup
waited 10 minutes
went through set up (reset apn to default, added gmail account)
reboot into CWM
wiped dalvick cache
wiped cache
flashed Alien theme 4
reboot
restored apps
reboot into CWM
wiped dalvick cache
wiped cache
flashed Kholk's kernel
reboot
i started getting random reboots. i cant figure out what the problem is. i tried flashing a different theme, and still got reboots. tried flashing the stock kernel and still got reboots. i tried re-flashing Alien v.4 and not restoring any apps and still got reboots. argh... any ideas?
can the radio cause a reboot issue? i really dont think its a ROM/Theme thing since noone else seems to be reporting the same problem... am i noobing this whole mod process?
Click to expand...
Click to collapse
try version 4 of alien. It has less bugs, faster and better performance.
Voelker45 said:
try version 4 of alien. It has less bugs, faster and better performance.
Click to expand...
Click to collapse
i was using Alien v.4, but it turns out it wasnt an issue with alien...
i think i figured it out (for those of you who care!)
I hadnt correctly removed the old install-recovery.sh file, so i think that may have resulted in incorrect flashes/installs... so i removed it, then flashed romracer's CWM
also, i sbf flashed this 4.5.91 Radio: http://forum.xda-developers.com/showthread.php?t=1159505&highlight=radio
between those two things, i seem to finally be on a fully functional, seemingly bug-less Atrix running Alien v.4 + Theme on Kholk's kernel and the 4.5.91 radio!
thanks for sharing.
Since installing Alien 4 on the weekend, I've had two spontaneous reboots. Both times were while playing music with the screen off and wifi on. Could be the music app, but I didn't have any reboots in Alien 3 or the other GB roms I tried.
Sent from my MB860 using XDA App
whenever I flash a new ROM (whatever it is) I get a string of random reboots.
Then after a few days it settles down...... seems to be worse if
a.) playing music
b.) bad data reception <---- this has happened to me on stock when I have 5 bars but there is some kind of data issue with the carrier and I open too many data using apps that all time out and causes some kind of kernel panic BAM reboot
I think my phone maybe has an issue when it first runs apps after a fresh build if its deodexed (compiling the cache etc. or the JIT first run whatever I'm not a dev) as that would explain why it settles down after a day or two.
Well I may have spoken too soon... my phone has rebooted twice, with about 90 minutes between each one, since I took it off the charger.
Sent from my MB860 using XDA App
I have heard that if you restore apps with tibu it causes problems. Try a fresh start with apps and no restore
Sent from my MB860 using XDA Premium App
hate to necro an old thread, but since the kernel has been updated and this issue persists i figured it was relevant...
As others in this thread have discovered, it is an issue with WiFi while the phone is asleep. Particularly reboots the phone when moving in and out of known WiFi reception areas. While I'm now using WiFi much more conservatively and saving battery life, its still a troublesome issue. Has anyone else made any attempts to fix it? I will be trying a few things myself soon.
I've tried it all folks. New kernels, factory reset, different radios, different ROMs. Every-thing. The WiFi will turn on for a quick second and I will get an error message "Unable to scan for networks" and then the Wifi will just turn on and off on and off over and over again. I've even deleted the files in the data/dhcp and data/wifi folders. Rebooted, still same issue. I've deleted the files and flashed a kernel and rebooted, still same issue.
Of course I am still in contract and will have to purchase a new phone outright from Verizon if I can't get this issue resolved......
I don't know what else to do here.....
Did you try formatting data and system before installing a new rom from recovery? If that doesn't work i would say its a hardware issue. You're not restoring system data with any backup programs are you?
Sent from my ADR6400L using Tapatalk
I've wiped pretty much everything known to man on the phone. The ROM installs are all "fresh" I haven't tried to install any APPS on the phone. Just wipe everything, factory reset / Dalvik Cache, all of it... install fresh ROM. Try to turn on Wifi, phone boot loops. No matter what ROM I install, still same issue with Wifi / boot looping.
Well guess we can close this out. I went out and paid full boat for a Samsung Nexus since I couldn't fix this issue.
I'd like to reopen this topic. I had been running Bamf Forever 1.10, but last night I decided to try another ROM because it's been running really slow for some reason.
Did a wipe (factory reset, Dalvik cache) and installed Thunderstick. Now WiFi is broken -- the exact same problem as described in the original post. I tried flashing a new kernel and new radios, and cannot get WiFi to work.
Does anyone have any suggestions? Will flashing back to stock ROM/unrooting help?
Thanks!
@ajoesq I had the same problem when i installed thunderstick thru boot manager. My wifi stopped and I could get it going on my phone rom. So i booted back into thunderstick and wifi was working. Booted back to hte phone rom then into recovery and then i flashed my phone rom again without wiping or anything (Thunbershed V1.2) and it worked fine. wifi started agian.
ajoesq said:
I'd like to reopen this topic. I had been running Bamf Forever 1.10, but last night I decided to try another ROM because it's been running really slow for some reason.
Did a wipe (factory reset, Dalvik cache) and installed Thunderstick. Now WiFi is broken -- the exact same problem as described in the original post. I tried flashing a new kernel and new radios, and cannot get WiFi to work.
Does anyone have any suggestions? Will flashing back to stock ROM/unrooting help?
Thanks!
Click to expand...
Click to collapse
Run a logcat when you try to turn wifi on. Put the output on pastebin.com and post the link. This might tell us what the problem is.
I'd make sure that the radio(s) were at least at the minimum of what the ROM called for.
Sent from my HTC ThunderBolt using XDA Premium App
Hey, so about a month or so back, my Vibrant has started to restart seemingly randomly. I do nothing to trigger it, I will just have it sitting on my desk and then I see the boot animation. This has happened on various ROMs as I have tried fixing it by flashing different ones. Fishmanmod v4, Slim ICS, CM9 nightlies, all the same issues. Different kernels, same problem as well.
I have ODIN'd back to stock multiple times and reflashed all different ROMs to no avail. I always wipe cache, dalvik, format system, factory reset... all that stuff when I flash a new ROM. I have left things stock, not installing any apps, same issue.
So, does anyone know what could be the issue, how I can fix this? Any information anyone needs for me to post? I am not sure what to do, and it is a rather annoying problem.
Me and my sister have the same phone (Vibrant) and she had the same issue. Not exactly sure what caused it, but switching out the battery seemed to help. (It was probably something else, but it seemed to be working after we switched batteries. Worth a shot!)