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..
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 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
Im unable to make voice calls through the Phone app. It will connect, then make no noise (ie no ringing). Same if i receive a call, i hit accept and i hear nothing, nor can the person calling me hear anything. I can use the voice search/navigation, and i can use other voice apps (ie voxer) just fine. SMS works, as does 3g, and im not getting any error messages.
Phone is GT-I9100, Kernel is Siyah 3.1rc6, running D4rom (ICS). I've tried 3 seperate roms (Omega v11, D4, and Slim (all ICS)) all having the same issues. Im assuming this is an issues with ICS (or more likely something i didnt update prior to switching) but ive spent about 6 hours now trying to find out what is causing it.
I realize downgrading would solve this, but i'd rather find out what my issue is and fix it. any ideas?
Flash again, but this time full wipe, it happened to me once on d4 rom, this should do it
Edit: have you tried wanamlite with siyahkernel? If you follow the below, you shouldn't have a problem.
A. Ensure FULL wipe;
1. System
2. Cache
3. Data
4. Dalvik cache
B. Immediately Flash ROM
C. Let boot and initial setup
D. Check if phone dialer and choice calls are ok?
E. If ok, Restore only user apps and data. NO System crap. Recheck
F. Reboot and setup accounts. Recheck
Sent from my GT-I9100 using xda premium
Still no luck. Flashed 3 times, once with D4 again, twice with wanalite. did factory reset, manually wiped /data, /system, /cache, and Dalvik cache. after doing initial run (i didn't set up my gmail account, since i need wifi for that (data cap is annoying)) i tried to make a call, and it still wont ring. At first it would end the call after 15's or so. after restarting it it would go longer, usually until i end it. SMS still works, as does 3g data.
I got an error this time setting up the clock, but it was only visible for about 2s. It was something to do with setting the time, if i can get it again ill try to write it down.
Also, when wiping the Dalvik cache i get this :
E:unknown voluem for path [/sd-ext]
Dalvik cache wiped
any other advice?
I finally downgraded to GB rom (unnamed). Phone worked fine, as well as everything else. Ty for your help though, It was greatly appreciated.
Also, i noticed prior to updating it that the search and back buttons didnt do anything. IDK if this is normal or not, i dont use those buttons much.
Very strange after fresh full wipe and flash, and test without setup of the different ROMs
Edit: Have you tried flashing some of the alternative ICS modems found in the modem thread? Maybe yours doesn't like the modem packaged with the ROM.
If that doesn't work, what if you flash one of Intratech official or Frankenstein firmware. You'll need to re-root after and flash cwm again.
That error with the Dalvik is ok. Forget why, answer will be found with some searching though. If you look carefully, it would have said "Dalvik cache wiped"
Sent from my GT-I9100 using xda premium
My pocket felt hot, so I pulled out my phone and saw that it kept rebooting itself. It just shows the initial Samsung splash for maybe a second or two, then loops again. I can get into Recovery and Download modes fine. I tried wiping the cache, factory reset, restoring a cwm backup. No luck so far. I've been using the CM9 rom for months. I haven't flashed or changed anything in months, I haven't even installed new apps in a while. Before this happened, it said I had no signal, so I had to restore my EFS(which I've had to do several times since I got the phone, mostly when I was switching back and forth from CM9 and stock to see which I prefer). After going into and out of airplane mode to reset the antenna, the signal and all worked fine. I let the phone cool down to make sure it wasn't just rebooting due to heat, but that didn't change anything. I've been searching here and google for anyone else with an identical issue, but I've failed so far. Everyone else seems to get to the home screen or just having random reboots during use.
Just to clarify, my question is: How can I fix my phone? Is there any other information I can give that would help?
I have the international i9300. I also tried removing the SD card and SIM card, since one thread concerning a different kind of rebooting issue reported success with that. Nope.
Try to reflash a stock rom on Odin
Is that different from restoring the original rom with CWM? I did that already. I don't have or know how to use Odin, but I'll download it and figure it out if that's the next step.
Solution?
Ok, I never didn't have to figure out Odin. I fixed it by wiping dalvik, factory resetting, restoring the stock rom, wiping it all again, rebooting into stock(it worked), then restoring back to the backup I made after the crash. Some of these steps might not be crucial, but at worst you waste a few minutes to make sure it works right again. Hopefully it'll help others with similar problems.
I'm helping a friend with her S3 i9300. It was running very sluggishly and starting in the last couple months she's been having a sleep of death issue.
It works fine (albeit slowly) while she's using it but when it sleeps for more than 10 minutes it doesn't turn back on without a lot of trouble or a holding down the power button and hard resetting. Every once in a while it only boots if I go indirectly through download mode.
I've confirmed with the play store app that she does NOT have the "insane chip" involved in the SDS issue. I've also factory resetted, rooted, tried flashing a custom kernel, a custom TW ROM (S5 sensation) and now an AOSP ROM (resurrection remix) and the problem persists.
Looking at other users' suggestions I took it apart and cleaned/played with the power button, even replacing it with the one from my old t999. Still the same.
I'm at a loss at this point. Has anyone run into this issue and found a fix I'm missing? Thanks for the help.
Have you already tried to format system partition (sdcard 0) via recovery?
After that you MUST flash a ROM, cause there is no system installed.
So, try to do this and let me know.
Else you can try to do a MEGA/SUPER wipe.
TENN3R said:
Have you already tried to format system partition (sdcard 0) via recovery?
After that you MUST flash a ROM, cause there is no system installed.
So, try to do this and let me know.
Else you can try to do a MEGA/SUPER wipe.
Click to expand...
Click to collapse
Thanks for the reply. Before flashing any ROMs I've always made sure to do a factory reset and then individually wipe System, Data, Cache, and Davlik Cache even though I know I'm duplicating some of the wiping. Unfortunately that did not work in this case.
I'll give the MEGA/SUPER wipe a try and report back.
Thanks again.
Looks like MEGA wipe didn't do the trick either. The phone is on NA8; is there a newer baseband I can try? Not sure what else to try.
At this point I'm thinking it might just be a hardware issue.
Flash the latest stock firmware from sammobile then factory reset, remove sd card and sim then test with a different battery.
If still the same then it is a hardware fault, motherboard/cpu.