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
Apologies in advance for being such a n00b.
I'm currently running CM7 RC1.1 with the MR2 radio on my rooted TBolt.
Heard lots of good things about BAMF 3.0 and thought I'd give it a try.
Did a complete wipe. Installed. Immediately after boot, things started going wrong. Lots of crashes even before I could sign into my Google Acct, VZW appeared briefly and went away altogether, and I couldnt connect to any wifi network.
Tried a few reboots. Reflashed the MR2 radio. Did a complete reset. Still no success.
I'm back on CM7 now but very keen on trying BAMF. Any suggestions on what I might be doing wrong?
nulambhbk said:
Apologies in advance for being such a n00b.
I'm currently running CM7 RC1.1 with the MR2 radio on my rooted TBolt.
Heard lots of good things about BAMF 3.0 and thought I'd give it a try.
Did a complete wipe. Installed. Immediately after boot, things started going wrong. Lots of crashes even before I could sign into my Google Acct, VZW appeared briefly and went away altogether, and I couldnt connect to any wifi network.
Tried a few reboots. Reflashed the MR2 radio. Did a complete reset. Still no success.
I'm back on CM7 now but very keen on trying BAMF. Any suggestions on what I might be doing wrong?
Click to expand...
Click to collapse
Did you flash BAMF from ROM Manager or Recovery. Don't flash from ROM Manager. Flash it directly from the recovery. Also try wiping multiple times.
I did flash from recovery. Will try multiple wipes this time. Just to be clear, which selection in recovery is the proper one for a complete wipe?
Thanks for the idea!
nulambhbk said:
I did flash from recovery. Will try multiple wipes this time. Just to be clear, which selection in recovery is the proper one for a complete wipe?
Thanks for the idea!
Click to expand...
Click to collapse
Its Wipe Data/Factory Reset. There's also Wipe Cache Partition. And under advanced there's a Wipe Dalvik Cache. Make sure you Nandroid(Backup)!!!!
Btw if you don't know how to navigate in recovery menu, its volume button to scroll and the power button to select
Up and running. Thanks!
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
I have my phone rooted and installed the FTS V2.4 ROM onto my phone, followed the install instructions. On startup I get a force close error, The application Motorola services (process.com.motorola.service.) has stopped unexpectedly. Please try again. I then get the process com.motorola.home.other has stopped. Everything else works fine. I do get another error when trying to place an email and date & time widget. Is there a fix for this? It doesn't stop the phone from functioning just would like to fix it.
That is usually caused by a bad flash or incomplete wipe. Go back into the recovery wipe everything a couple of times reflash the rom and that should take care of it. I have had that happen on multiple phones with multiple roms.
arsmithsr said:
That is usually caused by a bad flash or incomplete wipe. Go back into the recovery wipe everything a couple of times reflash the rom and that should take care of it. I have had that happen on multiple phones with multiple roms.
Click to expand...
Click to collapse
So after booting into recovery I do wipe data/factory reset a couple times? Anything else I should wipe a couple times? And then do install zip from sdcard? Also, my friend said after it installs I should leave it for 10-20 minutes, is this true?
you can manually wipe the cache and dalvic cache 2 or 3 times each then factory reset a couple times then flash your rom again. What has happened is you have ssome files from the old rom and some files from the ne rom this causes the issues you are seeing. You could probably just factory reset a couple of times Cauculin? has made a special wipe becuase of these issues sometimes it doesn't format right that's why you need to do the multiple wipes to be sure it took.
Similar problem on virgin Razr
I get this each time I reboot " process com.motorola.home.other has stopped unexpectedly, Please try again. Force close. FC is my only option.
It has appeared a few other times but with no regularity. Like the OP I still have full function and use but I'm sure it is a sign of possibly other problems brewing.
From what I have read it looks as if a complete reset might be the only cure but I'm hoping to find another solution.
Q: Is "com.motorola.home.other" actually a file, or does it refer to a file that could possibly be copied back over from a backup if it is corrupt.
While writing this post this problem occurred again after closing an app, which has me even more concerned.
Many thanks
X/BillyD..
The gist of my problem: Earlier today I successfully installed the latest CM9 from Joker (.0.7.0.0). Unfortunately, all wireless services other than WIFI were down (including SMS and telephone), and on start the phone produced an error about the com.android.phone force closing (or some such). I figured I had screwed something up, so I reflashed the clean stock firmware.
Since then (roughly 12 hours ago), I've been getting the stuck on the boot screen whenever I try flashing CM9. Relevant details follow:
Logcat doesn't help -- it tosses an error about the shell directory or file not being found (the exact error message escapes me, but I can reproduce it if need be).
I've tried formatting cache, data, and system, followed by a wipe (or two) on several occasions.
I've also tried flashing various versions of CM9 -- specifically .0.7.0.0 and .3.1. Both give the same result. I've also tried whatever version is in the KitchenSink v2.11 installer. Same result.
My CMW version is the 5.0.2.8. I installed it through RomManager (as opposed to the command prompt on Windows, which I did the first time when it quasi-worked). I've read that using v2 fixes this issue, but I can't find a live copy anywhere, so I haven't been able to try it.
Rather than going for a completely new install every time I bork something, I made a backup just after I finished unlocking and rooting the phone. I just restore that backup after each attempt, and it goes back to working fine on the stock Android firmware (3.whatever).
Any ideas? I think I'll try starting completely from scratch again and not using RomManager tomorrow, but if anyone can point out my error before then and save me a lot of -- hopefully not wasted -- effort, it would be fantastic.
Cheers,
Vash
vash265 said:
The gist of my problem: Earlier today I successfully installed the latest CM9 from Joker (.0.7.0.0). Unfortunately, all wireless services other than WIFI were down (including SMS and telephone), and on start the phone produced an error about the com.android.phone force closing (or some such). I figured I had screwed something up, so I reflashed the clean stock firmware.
Since then (roughly 12 hours ago), I've been getting the stuck on the boot screen whenever I try flashing CM9. Relevant details follow:
Logcat doesn't help -- it tosses an error about the shell directory or file not being found (the exact error message escapes me, but I can reproduce it if need be).
I've tried formatting cache, data, and system, followed by a wipe (or two) on several occasions.
I've also tried flashing various versions of CM9 -- specifically .0.7.0.0 and .3.1. Both give the same result. I've also tried whatever version is in the KitchenSink v2.11 installer. Same result.
My CMW version is the 5.0.2.8. I installed it through RomManager (as opposed to the command prompt on Windows, which I did the first time when it quasi-worked). I've read that using v2 fixes this issue, but I can't find a live copy anywhere, so I haven't been able to try it.
Rather than going for a completely new install every time I bork something, I made a backup just after I finished unlocking and rooting the phone. I just restore that backup after each attempt, and it goes back to working fine on the stock Android firmware (3.whatever).
Any ideas? I think I'll try starting completely from scratch again and not using RomManager tomorrow, but if anyone can point out my error before then and save me a lot of -- hopefully not wasted -- effort, it would be fantastic.
Cheers,
Vash
Click to expand...
Click to collapse
Use this recovery. http://forum.xda-developers.com/showthread.php?t=1218417
Or jokers at http://forum.jokersax.com/discussion/25/joker-recovery-for-the-photon-v3
I use the first link. Works perfect. Once you install the recovery. Wipe everything. Install 0.3.1. Boot into the system. Go back and flash the newest 0.7.0 update with gapps.
Should fix all the issues.
Sent from my SGH-I777 using XDA
Well, I got .3.1 working. Then tried to install .7 and it crapped itself again. Should I have cleared all the data/caches/etc. between the two?
Edit - I tried it again but this time cleared all the data between installs. It booted, but I got the same 'android.phone failed to start' message.
Edit 2 - Alright, I think I got it. I didn't clear anything between the two installs, but I installed each firmware twice without exiting recovery mode either time. It seems to be working (phone works, at least), although I'm not sure my 3G is working...
na7q said:
Use this recovery. http://forum.xda-developers.com/showthread.php?t=1218417
Or jokers at http://forum.jokersax.com/discussion/25/joker-recovery-for-the-photon-v3
I use the first link. Works perfect. Once you install the recovery. Wipe everything. Install 0.3.1. Boot into the system. Go back and flash the newest 0.7.0 update with gapps.
Should fix all the issues.
Sent from my SGH-I777 using XDA
Click to expand...
Click to collapse
Joker's recovery is a zip file you can flash from 5.0.2.8 if you don't feel like hooking up to the computer and using fastboot. But 5.0.2.8 doesn't work right to flash roms.
Sent from my MB855 using xda app-developers app
Aside from not being able to connect to any 3G networks (which is a problem...), it looks like it's working. Any ideas why 3G doesn't work now?
Thanks for the help thus far =)
vash265 said:
Aside from not being able to connect to any 3G networks (which is a problem...), it looks like it's working. Any ideas why 3G doesn't work now?
Thanks for the help thus far =)
Click to expand...
Click to collapse
Install 3.1, boot, reboot to recovery, wipe cache and dalvik, install 7.0, install gapps, boot.
Sent from my MB855 using xda app-developers app
Acvice said:
Install 3.1, boot, reboot to recovery, wipe cache and dalvik, install 7.0, install gapps, boot.
Sent from my MB855 using xda app-developers app
Click to expand...
Click to collapse
Yep...already did that and got it to boot just fine. Now I'm struggling with poor reception. I've seen other users (different phones) mention radio upgrades, but I was extremely unfamiliar with the terminology. The phone seems to work okay, but I only get 1x reception for data.
Or were you actually suggesting to repeat the entire process?
Edit - Tried again, still no luck with 3G.
vash265 said:
Yep...already did that and got it to boot just fine. Now I'm struggling with poor reception. I've seen other users (different phones) mention radio upgrades, but I was extremely unfamiliar with the terminology. The phone seems to work okay, but I only get 1x reception for data.
Or were you actually suggesting to repeat the entire process?
Edit - Tried again, still no luck with 3G.
Click to expand...
Click to collapse
Before doing what i stated did you wipe everything (system, data, cache, dalvik)? Also, you still getting a forceclose upon boot or just crap signal? And are you on sprint or electrify?
Acvice said:
Before doing what i stated did you wipe everything (system, data, cache, dalvik)? Also, you still getting a forceclose upon boot or just crap signal? And are you on sprint or electrify?
Click to expand...
Click to collapse
I wiped everything. I can boot into the OS and my phone works fine, but my data rate is stuck on 1x (so crap signal). I'm on sprint.
vash265 said:
I wiped everything. I can boot into the OS and my phone works fine, but my data rate is stuck on 1x (so crap signal). I'm on sprint.
Click to expand...
Click to collapse
well did you have 3g on stock? there's no reason it would go to 1x unless 3g is unavailable. the rom shouldn't cause it to go into 1x.
na7q said:
well did you have 3g on stock? there's no reason it would go to 1x unless 3g is unavailable. the rom shouldn't cause it to go into 1x.
Click to expand...
Click to collapse
Yep. Despite popular belief, I'm not a moron =) I'm in the dead center of 3G availability for Sprint in my area, and with stock android I get perfect 3G reception. I've read reports of the same things happening to other people, but haven't found a solution yet. I restored to stock after making a backup to try updating the PRL. I'll update again when I find out if it worked or not.
Edit - Sprint just sucks, apparently. http://www.sprintusers.com/forum/showthread.php?t=225908
When I rebooted to stock I checked the radio status and sure enough, 1xRTT. Evidently I am a moron =p
There was something wrong with the phone afterall. To fix it, I did the following:
Dial *#*#4636#*#*
You'll be presented with a menu. Go to Phone Information.
About halfway down the page, there will be a menu with a dropdown. Mine was set to CDMA. To fix the issue, I changed it to CDMA auto (PRL). I'm now receiving excellent 3G reception.