So my girlfriend has been running MIUI for two days now and as of this morning she keeps getting force closes of android.phone.
Any ideas how to fix? Thanks all!
Im no expert but I think you will need to odin back to stock w/ pit, then reflash miui.
Thanks for the reply... If nothing else works, I suppose we'll have to do that.
I've actually had this problem as well in the latest build of MIUI. Strangely enough, it stopped after a few battery pulls/days later, and now it's completely fine. Try giving it some time to settle.
wipe data after flashing miui. ALL data. User/system/cache/etc. That is all.
Related
on ed04 w/ newest MIUIwiz
pick up phone and its rebooting over and over...for no reason. Pull battery, it reboots to "safe" mode? Now it boots fully and its force close city, gapps force closes, launcher force closes, everything force closes then the phone reboots. Is there an obvious fix or reason for this? Reflashed rom and kernel, wiped caches and reinstalled, and its the same thing, force close city. Any reason why this would randomly happen out of the blue? All was well before.
mikey6p said:
on ed04 w/ newest MIUIwiz
pick up phone and its rebooting over and over...for no reason. Pull battery, it reboots to "safe" mode? Now it boots fully and its force close city, gapps force closes, launcher force closes, everything force closes then the phone reboots. Is there an obvious fix or reason for this? Reflashed rom and kernel, wiped caches and reinstalled, and its the same thing, force close city. Any reason why this would randomly happen out of the blue? All was well before.
Click to expand...
Click to collapse
Did you wipe data/factory reset? If so, and you still have problems, you could try fixing permissions in CWM (advanced menu). If that still doesn't work, I recommend flashing imnuts' Odin ED01 stock package here: http://www.multiupload.com/6ET46L1ATD (it should not replace your ED04 modem) and then downloading the MIUIWiz ROM again (in case the first download was corrupted).
Another Fascinating post by my XDA app...
i could tell u this much my wife phone is fully stock from day one (she would never let me flash anything to her phone but always liked my phone)and her phone was doing the same thing. so i dont think its just the rom.she called vz they told her to do a factory reset,and she did.2 days know and she ok. this happen a after updating to ed04.
If you've reflashed the ROM, then you've essentially wiped /system and started new there. Sounds like something in /data is corrupt. Wipe data (yeah, not having a recent backup will suck, but you'll get by) and everything should be fine.
I odin'd back, wiped data blah blah blah and fixed it all back up, but I am curious what happened in the first place.
Phone was working flawlessly for weeks, I go to take it out of my pocket and its on the boot animation, boots to something saying safe mode with force closes galore. Pull battery and reboot, and its the same thing, force close city, and backups through recovery do not work. I am curous why that happened
mikey6p said:
on ed04 w/ newest MIUIwiz
pick up phone and its rebooting over and over...for no reason. Pull battery, it reboots to "safe" mode? Now it boots fully and its force close city, gapps force closes, launcher force closes, everything force closes then the phone reboots. Is there an obvious fix or reason for this? Reflashed rom and kernel, wiped caches and reinstalled, and its the same thing, force close city. Any reason why this would randomly happen out of the blue? All was well before.
Click to expand...
Click to collapse
Personally, every so often, I'd recommend doing this http://forum.xda-developers.com/showthread.php?t=1090127&highlight=ext4+formatter. It wipes EVERYTHING.
Same thing happened to me for the second time last night. On com rom 2.1/otb kernel. Phone froze up randomly, held up and power to reboot. When it came back it was.force close city. Subsequent reboots would freeze on the lock screen or reboot right as the lock screen loaded.
Recovering a backup didn't work. Wiped data and reinstalled com rom and phone is fine again.
Is my phone possessed????
Sent from my SCH-I500 using XDA App
I can't take it anymore! Almost every week, I have a marathon of FCs and then when I try to reboot my phone I get a loop. The only way I can fix it is by wiping everything. I don't mind doing that every so often, but every week is just too often. It's so annoying! Does anyone know how to almost permanently fix this!?
I am using MIUI rom and I have a Samsung Galaxy Vibrant. I just updated to 1.11.25 through recovery, but still has a bootloop.
Thank you for your time!
(EDIT: Well I'm going to wipe everything again, because I want to use my phone, hahaha but still, I would love any feedback to help me rarely have to wipe my data again! Thank you!)
are you flashing manually?
lurker! said:
I can't take it anymore! Almost every week, I have a marathon of FCs and then when I try to reboot my phone I get a loop. The only way I can fix it is by wiping everything. I don't mind doing that every so often, but every week is just too often. It's so annoying! Does anyone know how to almost permanently fix this!?
I am using MIUI rom and I have a Samsung Galaxy Vibrant. I just updated to 1.11.25 through recovery, but still has a bootloop.
Thank you for your time!
(EDIT: Well I'm going to wipe everything again, because I want to use my phone, hahaha but still, I would love any feedback to help me rarely have to wipe my data again! Thank you!)
Click to expand...
Click to collapse
Hmmm... You've tried my guide right?
Manually flashing mentions "mounts and storage' its important, follow all op's but I believe Format storage may be your issue.
I am coming from a Galaxy Nexus. I have flashed many roms in the past, but when I flash roms on the Note the phone portion seems to stop working. Data works fine, its just when I try to make a call it just sits there for a long time and then the call terminates. Happens every time a flash a new rom. With my old Droid 1 on Verizon you could dial up a number to reactivate the phone, on the Nexus this seems to not be an issue at all. Is there some trick to getting AT&T to reinitialize the cell phone after a new rom flash? I tried pulling the battery for like 5 minutes figuring that would force it to resync or something...
Any one else running into this?
Never heard of this problem. Which roms are you loading, I would suggest asking the dev of the ROM, including all of the steps you use to install it.
Sent from my SAMSUNG-SGH-I717 using XDA
I completely agree with you and same thing is happening to my note as well...I thought i was in bad signal area....now i am running into problems with google market....cant load apps...always showing error 492....i installed saurom rom rc7 and also i dont see what kernel i have on my phone....i also installed the kernel fix and flashed it....still nothing...i am myself trying to get some help here
busybeebusy said:
I completely agree with you and same thing is happening to my note as well...I thought i was in bad signal area....now i am running into problems with google market....cant load apps...always showing error 492....i installed saurom rom rc7 and also i dont see what kernel i have on my phone....i also installed the kernel fix and flashed it....still nothing...i am myself trying to get some help here
Click to expand...
Click to collapse
To fix the market you need to reboot to clockworkmod and clear the cache. The issue with the kernel is normal, it is the HoloKernel, it just has bad information in the about screen, that's normal too.
To fix the phone issue I usually pull the battery for like 5 minutes and then toggle the network from auto to manual a couple of times and then it seems to finally pick it up. Just seems odd...
omniphil said:
I am coming from a Galaxy Nexus. I have flashed many roms in the past, but when I flash roms on the Note the phone portion seems to stop working. Data works fine, its just when I try to make a call it just sits there for a long time and then the call terminates. Happens every time a flash a new rom. With my old Droid 1 on Verizon you could dial up a number to reactivate the phone, on the Nexus this seems to not be an issue at all. Is there some trick to getting AT&T to reinitialize the cell phone after a new rom flash? I tried pulling the battery for like 5 minutes figuring that would force it to resync or something...
Any one else running into this?
Click to expand...
Click to collapse
Did you flash the ATT fix after flashing RC7? If not, download ATT fix, flash Saurom RC7, wipe cache and d cache, flash ATT fix and then reboot system...
Update.....yesterday i opened the cwm and just cleared the wipe cache and then rebooted the phone and everything came back to normal...error code 492 disappeared and i was able to download all my apps.. I hope it will help somebody. Running saurom rc7. Everything looks fine so far....only data speed needs to go up some more but it could be the area....
Sent from my SGH-I717R using XDA
omniphil said:
To fix the market you need to reboot to clockworkmod and clear the cache. The issue with the kernel is normal, it is the HoloKernel, it just has bad information in the about screen, that's normal too.
To fix the phone issue I usually pull the battery for like 5 minutes and then toggle the network from auto to manual a couple of times and then it seems to finally pick it up. Just seems odd...
Click to expand...
Click to collapse
What is the problem with the kernel that you need to flash the kernel fix? Is that only if you use holo kernel?
I had this problem before & Ive reflashed Virtuous twice but it keeps returning after a while. I get a notification saying theres a camera firmware upgrade, but it will not upgrade, and the camera wont open? Im under the understanding that updates are supposed to be disabled? Ive been looking through the root file browser, but Im not sure what exactly IM looking for, or what would relate to this. The reason Im on a custom Rom is to get as FAR AWAY from Asus Firmware as possible! I know that Virtuous is close to stock, but I had nothing but repeated problems before I rooted & flashed a new Rom. This camera update issue was even happening on stock for me... but I would usualy just let it upgrade & it would go away for a week or two. Now I cant even do that... Someone Please Help ME! Ive tried clearing dalvick & Cache, Ive also tried fixing permissions. Im tired of having to reinstall.
I have flashed over 10 roms each time I do a NUKE and wipe all caches and data. I have installed roms as per instructions. But for the life of me I can not find one that will go an hour without rebooting or freezing. I have tried many different kernels as well.
Does anyone else have this problem?
Do your phones reboot all the time?
Am I doing something wrong?
Is there something wrong with just my phone?
Is this normal?
Someone advise a stable version. I just don't get it......
Maybe a battery issue.
I really don't understand it. It reboots when I'm sending a text or searching internet or swiping screens. It doesn't matter what i am doing at the time.
The most stable one I have found to work the longest without reboot is Omega Milestones with 7.13 dormaix kernel. Thats it. But I still have problem.
Please help
It could be the battery dying on you.
If it's not the battery then we could be talking hardware.
Sent from the little guy
casualt said:
I have flashed over 10 roms each time I do a NUKE and wipe all caches and data. I have installed roms as per instructions. But for the life of me I can not find one that will go an hour without rebooting or freezing. I have tried many different kernels as well.
Does anyone else have this problem?
Do your phones reboot all the time?
Am I doing something wrong?
Is there something wrong with just my phone?
Is this normal?
Someone advise a stable version. I just don't get it......
Maybe a battery issue.
I really don't understand it. It reboots when I'm sending a text or searching internet or swiping screens. It doesn't matter what i am doing at the time.
The most stable one I have found to work the longest without reboot is Omega Milestones with 7.13 dormaix kernel. Thats it. But I still have problem.
Please help
Click to expand...
Click to collapse
Have you tried going back to an official stock firmware?
Sent from my SGS II