my phone suddenly restarted while i was launching skype, and when i came back on it showed a "unfortunately system ui has stopped" message. if i tap ok or report it just gives more of the same popup. tried wiping and reflashing but it happened again after 2 hours of usage.
i am using rootbox 3.6
Terens said:
my phone suddenly restarted while i was launching skype, and when i came back on it showed a "unfortunately system ui has stopped" message. if i tap ok or report it just gives more of the same popup. tried wiping and reflashing but it happened again after 2 hours of usage.
i am using rootbox 3.6
Click to expand...
Click to collapse
Oh boy.....read the topic and I thought "reflash".
So....as you have already done the reflash thing, my advice is go stock for a day.
And then go back to rootbox.
And maybe run these scripts that theatheist is promoting. Those are cleaning scripts, could help removing all the previous ROM's waste.
Sent from the little guy
gastonw said:
Oh boy.....read the topic and I thought "reflash".
So....as you have already done the reflash thing, my advice is go stock for a day.
And then go back to rootbox.
And maybe run these scripts that theatheist is promoting. Those are cleaning scripts, could help removing all the previous ROM's waste.
Sent from the little guy
Click to expand...
Click to collapse
^^this
Got the same problem with different rom. It first started t do that with RR 3.1.3 and I thought I'd try the revolt 3.2. Flashed and everything was fine. I really started to love this new rom and then boom "unfortunately system ui has stopped"... I did everything like the instructions said but didn't run any cleaning scripts. Always these things happen to me... How can I get rid of this? Please help, my phone is useless because the warning just keep popping back! How does one run cleaning scripts?
Nuke script.
Sent from the little guy
Thanks for fast reply! I decided to try reflashing first. This time I chose CM10.1 kernel instead of dorimanx 7.46. Everything seems to be ok again but I'm afraid that the warning pops up very soon. I downloaded that nuke script but I hope reflashing helped. So what exactly that script will erase? Can I lose something important?
Is this a known issue? I couldn't find many similar cases and I'm fairly new to using custom roms above android 2.3... I'm just trying to figure out what caused this whole thing. I was installing new apps on the fresh rom and suddenly it popped up. It did this on the last minutes when I was using RR 3.1.3 rom and I have been using that rom for about 2 weeks without that kind of problems.
edit. Holy s***! I figured out what's causing this for me! Atleast I got rid of it for a while now. So I reflashed and did everything as the instructions say; wipe data, cache, dalvik, format /system & flash followed with wiping cache & dalvik. I chose CM10.1 kernel to test if that has anything to do with it. Everything started ok and again I started to customize settings and launcher. I was enabling toggles from the ROM Control menu and when I ticked on the "Profiles" toggle the warning came right away and came back again and again after tapping ok. There's about 0.5 second delay after you tap ok and when the message pops up again. During that delay I was able to go back to toggle settings and untick the "Profiles" toggle. Tapped ok to the warning and suddenly it was gone without coming back! I have always been good at finding bugs and stuff but this must be the first time when I find a solution for it on my own! Feels so good that I'm gonna reward myself with a beer! Hopefully that isn't too early reward... Just an excuse to get a beer =)
Read that script thread, it'll remove all previous ROMs left overs.
The thing about custom ROMs & kernels is that they are not that stable at the time, simply because stock JB is showing some bugs and all.
Siyah v6 final is out know, try that.
Sent from the little guy
Related
I saw that there was a similar thread in the Epic 4G forum, but I wanted to make sure before I start trying something that might mess up the phone even further. My wife's vibrant will start having everything force close on her after a few weeks. This has happened on 2 or three different ROMs, and I'm not sure what's causing it. I saw the similar thread where it might be related to "journaling", but we don't change her battery out at all or even reboot the phone that often, so I'm not sure if its the same issue. I've done a reset of her phone a few times, but I'm on a GB ROM so it doesn't go completely back to factory. Should I try to ODIN to stock? Any ideas why this happens? Thanks in advance.
Try fixing permissions in CWM first and see if that helps.
Sent from my SGH-T959 using xda premium
Fix permissions worked for a while, but not anymore. Everything's force closing again. Will the journaling fix help?
Anybody have any ideas? Gonna wipe then install a newer ROM, but I want to make sure this doesn't happen again.
Only titanium the "necessary" apps that you wanna keep your data from. Then uninstall it - often I find that this helps for some odd reason.
Sent from my SGH-T959 using xda premium
chairhome said:
I saw that there was a similar thread in the Epic 4G forum, but I wanted to make sure before I start trying something that might mess up the phone even further. My wife's vibrant will start having everything force close on her after a few weeks. This has happened on 2 or three different ROMs, and I'm not sure what's causing it. I saw the similar thread where it might be related to "journaling", but we don't change her battery out at all or even reboot the phone that often, so I'm not sure if its the same issue. I've done a reset of her phone a few times, but I'm on a GB ROM so it doesn't go completely back to factory. Should I try to ODIN to stock? Any ideas why this happens? Thanks in advance.
Click to expand...
Click to collapse
Get into recovery:
wipe dalvik
wipe cache
fix permissions
reboot
wait 10 mins reboot into recovery again
fix permissions
reboot
open rom manager [worth its weight in gold!]
fix permissions
reboot
Thats what I did with my cm7.1.0.1 but I also installed eugenes streamline 110411 ver and [knock on wood] havnt had any more issues with fc's.
And yes even if you follow the installs to a "T" some of us still have the FC issue!
Good luck!
3 weeks later and I'm back to square one. I'll try the above, if it doesn't work, i'll have to wipe and reinstall. thanks. What's eugene's streamline?
Id flash to stock, flashing different roms wont help if theres a ghost in the machine, what launcher are you running...touchwiz sucks on my wimpy replacement phone.
Sugartibbs said:
Id flash to stock, flashing different roms wont help if theres a ghost in the machine, what launcher are you running...touchwiz sucks on my wimpy replacement phone.
Click to expand...
Click to collapse
MIUI's launcher. I'll probably try flashing to stock soon. :-(
No go. I'll have to look into Eugene's streamlined 110411
ok just for future sake, 3 rule's of flashing,
it's better to reinstall your applications manually then to trust titanium when bouncing between roms with different frameworks, versions, partitions, etc.
always flash from stock unless your updating a weekly rom ie cm7/miui
after flashing power off screen and have a cup of coffee/beer/shower. give the OS time to do all it's background configurations and setup.
now if you follow those 3 rules you "should" have no real issues.
I have to post here because I'm a massive lurker and haven't got the post count for the development forum!
Firstly, excellent to see Task back in action for ICS! I was considering going back to stock for the OTA following today's ICS release but figured seeing as I was already rooted I might as well stick with custom roms.
I installed Infamous 2 (1st Aug) no problem at all, smooth as silk for a day 1 release! I used it for a bit before seeing Task was back with his first ICS so thought I'd stick with what I know best and completed the process again for his rom.
Install went fine, factory reset/wipe everything, install from .zip and booted first time no problems. I didn't go through the Google setup, or wifi, in order to let the rom settle, then I rebooted after 10 mins and the problem started. I got the following error on screen every 10 seconds:
android the process com.android.phone has stopped working
It would hang every time (unsurprisingly) and I couldn't access files via PC either, despite MTP connection showing. I've now restored back to Task14 from recovery backup and I'll wait for some more mods to be done before trying again, but thought I'd share my experience here in the hope it might help others/Task sort things out if it happens to them.
/refreshes the forum over and over again impatiently waiting for the real goodies to start flowing
mooter said:
I have to post here because I'm a massive lurker and haven't got the post count for the development forum!
Firstly, excellent to see Task back in action for ICS! I was considering going back to stock for the OTA following today's ICS release but figured seeing as I was already rooted I might as well stick with custom roms.
I installed Infamous 2 (1st Aug) no problem at all, smooth as silk for a day 1 release! I used it for a bit before seeing Task was back with his first ICS so thought I'd stick with what I know best and completed the process again for his rom.
Install went fine, factory reset/wipe everything, install from .zip and booted first time no problems. I didn't go through the Google setup, or wifi, in order to let the rom settle, then I rebooted after 10 mins and the problem started. I got the following error on screen every 10 seconds:
android the process com.android.phone has stopped working
It would hang every time (unsurprisingly) and I couldn't access files via PC either, despite MTP connection showing. I've now restored back to Task14 from recovery backup and I'll wait for some more mods to be done before trying again, but thought I'd share my experience here in the hope it might help others/Task sort things out if it happens to them.
/refreshes the forum over and over again impatiently waiting for the real goodies to start flowing
Click to expand...
Click to collapse
logcat or it didnt happen.
task650 said:
logcat or it didnt happen.
Click to expand...
Click to collapse
I see some logs in the root folder, is that what you're referring to? I'll happily help you investigate if I can but it'll help if you point me in the right direction. Actually, maybe I'll try again and see how I get on? Restoring from backup was pain-free so not much to lose but 20 mins
Regardless, I very much look forward to seeing your work progress on this one over time! I know you're busy but superstars have obligations dude haha ;D
edit - trying again now with logcat reader installed - I'll report back!
do you have Ti backup installed? I would first try to see if there is some kind of phone apk in there. If there is try to clear the phone apk data and cache. If that doesnt work maybe try freezing it. Its strange that you have this error since tasks rom is a stock galaxy tab 10.1 ics build. Maybe try to wipe everything again and follow tasks instructions one more time step by step. sometimes weird things happen and a reflash might fix that. And just a stupid question but you have the wifi p7510 tab right
i have Slim's latest on my I777. i am having constant shutdowns & SOD's, like every few minutes. the twist is that i have had the same release of Slim on the phone before, several times in fact, and i had the occasional SOD, but not constantly like now. i have installed Slim a number of times because i like to try new ROMs, and i keep coming back to Slim cus i like JB.
this must be diagnosed, because i believe now that something was messed up a bit along the way of flashing ROMs, mods, and kernels, but our awesome ROM supporters in their threads have their limits they have told me, and i should ask here since this is a general question about the phone & system. i am seeking help here relating to the rest of the phone and system that may become damaged somehow, and i want to clean up my system to end this problem. logcat & last_kmssg linked below.
to be clear: i am rooted correctly, am running the right software for the I777, always check my MD5's from the phone before flashing, clear my caches when needed, wipe dalvik before flashing kernels, etc etc.
interestingly, i fully wiped/factory reset, formatted system, dalvik, wiped batt stats, and fixed permissions, then reinstalled stock Slim last night because i thought maybe my settings were trouble, so i decided to run an out-of-the-box Slim, changing only the dpi and launcher. no change.
i've tried Siyah's latest after running Jkay's kernel cleaner as well. no change. something is making my phone shutdown/SOD constantly, and it may not be the ROM. others don't seem to be having this issue. i have little running on the phone. just accuweather, Date in Tray Pro, and Apex Pro. no overclocking/voltage changes... nothing fancy at all. so i'm just perplexed.
here's the latest logcat: http://davidb.net/logcat_and_device_info(1).zip
here's the latest last_kmssg: http://davidb.net/last_kmsg
if any of you guys can help with this, then thank you in advance.
VR32 said:
i have Slim's latest on my I777. i am having constant shutdowns & SOD's, like every few minutes. the twist is that i have had the same release of Slim on the phone before, several times in fact, and i had the occasional SOD, but not constantly like now. i have installed Slim a number of times because i like to try new ROMs, and i keep coming back to Slim cus i like JB.
this must be diagnosed, because i believe now that something was messed up a bit along the way of flashing ROMs, mods, and kernels, but our awesome ROM supporters in their threads have their limits they have told me, and i should ask here since this is a general question about the phone & system. i am seeking help here relating to the rest of the phone and system that may become damaged somehow, and i want to clean up my system to end this problem. logcat & last_kmssg linked below.
to be clear: i am rooted correctly, am running the right software for the I777, always check my MD5's from the phone before flashing, clear my caches when needed, wipe dalvik before flashing kernels, etc etc.
interestingly, i fully wiped/factory reset, formatted system, dalvik, wiped batt stats, and fixed permissions, then reinstalled stock Slim last night because i thought maybe my settings were trouble, so i decided to run an out-of-the-box Slim, changing only the dpi and launcher. no change.
i've tried Siyah's latest after running Jkay's kernel cleaner as well. no change. something is making my phone shutdown/SOD constantly, and it may not be the ROM. others don't seem to be having this issue. i have little running on the phone. just accuweather, Date in Tray Pro, and Apex Pro. no overclocking/voltage changes... nothing fancy at all. so i'm just perplexed.
here's the latest logcat: http://davidb.net/logcat_and_device_info(1).zip
here's the latest last_kmssg: http://davidb.net/last_kmsg
if any of you guys can help with this, then thank you in advance.
Click to expand...
Click to collapse
Nothing jumps out at me but you need to backup your data and SDCARD to a PC, flash back to stock..... when stock boots up perform a factory reset and test with the stock firmware... if it work fine.... root and install the ROM fresh and clean and test without installing anything else. If it again is fine then install every app from the Market. if you want to restore your recent data afterwards that is up to you but There are so many variables that could be causing your issue and you need to step back and try to find the cause one step at a time.
shoman94 said:
Nothing jumps out at me but you need to backup your data and SDCARD to a PC, flash back to stock..... when stock boots up perform a factory reset and test with the stock firmware... if it work fine.... root and install the ROM fresh and clean and test without installing anything else. If it again is fine then install every app from the Market. if you want to restore your recent data afterwards that is up to you but There are so many variables that could be causing your issue and you need to step back and try to find the cause one step at a time.
Click to expand...
Click to collapse
thanks shoman. much appreciated for the tips.
You wouldn't happen to be using an aftermarket phone charger would you? I was working on a phone behaving like that and it was the charger. If you lifted up on the plug a little while plugged in, it would wake the phone from sleep and constantly restart it. It also did something to the ROM or possibly the Kernel cause it started restarting while not plugged in and the power button quit working. I used a known good Samsung charger and installed AOKP JB with the kernel that came with and it fixed everything. I replicated this problem with two different chargers. It is possible that the USB port on the phone was worn. However, no matter how I moved the cable with a Samsung charger, nothing bad would happen.
beaverslayer said:
You wouldn't happen to be using an aftermarket phone charger would you? I was working on a phone behaving like that and it was the charger. If you lifted up on the plug a little while plugged in, it would wake the phone from sleep and constantly restart it. It also did something to the ROM or possibly the Kernel cause it started restarting while not plugged in and the power button quit working. I used a known good Samsung charger and installed AOKP JB with the kernel that came with and it fixed everything. I replicated this problem with two different chargers. It is possible that the USB port on the phone was worn. However, no matter how I moved the cable with a Samsung charger, nothing bad would happen.
Click to expand...
Click to collapse
no I've never used one.
but it appears this was all caused by the app Screen Off And Lock by Katecca. I had the donate version. its always worked for me on every ROM up through ICS, but it seems to wonk out JB. I changed to Lock Screen App by Kenneth Cheng and have had zero problems in days now, which is a first.
Sent from my SGH-I777 using xda premium
Hi,
Whenever i turn my phone off and back on again it fails to recognise my baseband or IMEI. I have seen other threads on this forum relating to this but not specifically after a reboot.
If the phone stays on there seems to be no problem and when I rebooted in my flat last night (where I have strongish signal) it doesn't seem to be a problem (though i would need to check this again).
So far my fixes is, and this works everytime:
- Reboot recovery,
- Flash rom/kernel (cmexperimental)
- wipe dalvik
- wipe cache
- reboot.
This is not really feasible long term as it is a battery drain and not how a phone should be! I do have a EFS backup apparently though i did not do this back up intentionally. It is dated the 18th September of this year, i've heard Siyah back ups efs automatically so worse case i should have that there but i know that it's not ideal to mess around with EFS.
Can anybody help me? I can supply further information.
This problem started earlier this week after i flashed PA 2.54 and then restored a nandroid back up of the changmin rom.
I would really appreciate any help. if i've missed anything out i apologise.
Thanks
I have a similar problem and Apparantly you need to restore a backed up efs to fix it there is this app it hasnt worked for me though.
https://play.google.com/store/apps/details?id=com.helroz.GSII_Repair
1Chef said:
I have a similar problem and Apparantly you need to restore a backed up efs to fix it there is this app it hasnt worked for me though.
Click to expand...
Click to collapse
can i ask what you did to cause the issue in the first place? any idea?
Im using neat rom (http://forum.xda-developers.com/showthread.php?t=1569686) and I flashed an aroma mod to add more options to it, I then rebooted and I had no signal, imei no anything and this message kept appearing (see pic)
The way I fixed it was to just reflash the rom and it removed the aroma mods, I decided today to just keep the standard rom with no mods and its looking good as ive rebooted 4 times so far and nothings happen except on one reboot i lost 62% wtf. The dev of the rom (salesale) pm'd me and explained how to fix it by editing your efs backup and then placing it back and using command lines to replace the old one, this didnt work for me though.
1Chef said:
Im using neat rom (http://forum.xda-developers.com/showthread.php?t=1569686) and I flashed an aroma mod to add more options to it, I then rebooted and I had no signal, imei no anything and this message kept appearing (see pic)
The way I fixed it was to just reflash the rom and it removed the aroma mods, I decided today to just keep the standard rom with no mods and its looking good as ive rebooted 4 times so far and nothings happen except on one reboot i lost 62% wtf
Click to expand...
Click to collapse
yeh i'm going to try factory reset and a fresh rom install to see if that fixes the problem. nice to hear there is hope and all the time it is working it's not so bad! just have to cut down on the amount of flashing i do!!
Is that neat rom ICS or JB? i really don't want to go back from JB to ICS!
Jelly bean of course its nice and stable, and you can't hide it, if your a flashaholic your gonna flash wow wtf your post was apparantly sent from 01/01/1970
Ok I've done a clean install of neat rom and installed the aroma mods. This has once again deleted all of the IMEI and other data like that, after lots of googling and using the repy from neat roms developer (salesale) I managed to do the steps he posted I also found this forum which outlines the steps of what to do, you will need to do the command lines in recovery, to unmount the efs so youll need this ( I think you should have this anyway as its great) I unfortunately couldn't do this as I get stuck on the last command line with: tar: invalid tar magic I have retreated back to just standard neat rom which for some reason unknown to me will not delete my IMEI but will do so upon the next reboot with aroma mods flashed WTF .
So I finally got around to installing the last of Task's 4.2.2 JB roms (6/24/2013 release) after using Task's 4.1.2 release for a long time (if it ain't broke don't fix it?). I did a full wipe, flashed the ROM, gapps, and put back the data for the apps I installed from the play store (not the system app data). I verified the MD5 sum of the ROM when I downloaded to my computer and again after I moved it to my phone, so I'm reasonably sure I got a good copy of the ROM.
One issue I have is that when I got to "Kernel Settings" in the settings menu, the settings app force closes with the message "Unfortunately Settings has stopped". Not sure what to do here - is the thing that manages the kernel settings something separate that I could clear the app data for?
Another thing is that I used to be able to have the wireless network name the phone is on in the pull-down status shade. I looked for it in ROM Control -> General UI where it was before but I can't find it there or anywhere else.
Battery life isn't as good as it was on 4.1.2 either. A couple of times I've looked at the phone and it had 40-50% battery left, and when I looked again a few hours later, it was dead. The battery was completely drained. I suppose it could be the battery, but this started happening after I installed 4.2.2 so I doubt it. The battery is about 9 months old. No apps were running at the time the battery was drained - I had closed anything that was running earlier.
I poked around in the (closed) ROM thread but couldn't find anything about the kernel settings issue or the wireless name setting (other than when Task put it in the ROM).
Anyone got any ideas?
Just curious as to why you would flash such an old ROM. There are sevral newer roms in active development here. Many 4.2.2 and 4.3 that are quite stable.
Sometimes in order to get a true battery indication you need to let the rom settle through several battery cycles (charge and drain the battery several times).
If you are having problems with stability like you describe you can boot into recovery, wipe cache, in advanced wipe dalvik cache, then reboot. If this doesn't fix you problems you can always try a new kernel ie STI, or AJ's.
Let me recommend you try one of the newer roms. Task has a 4.2.2 that is quite nice. Many are running Carbon that is now up to 4.3.1. If you really like 4.1.2 try out Cook's rom, or Sho's. Both of those have been recently updated.
Butchr said:
Let me recommend you try one of the newer roms. Task has a 4.2.2 that is quite nice. Many are running Carbon that is now up to 4.3.1. If you really like 4.1.2 try out Cook's rom, or Sho's. Both of those have been recently updated.
Click to expand...
Click to collapse
I'm using Tasks 4.2.2 ROM, and that's the one I'm having the problems with. I realize that wasn't exactly clear in my original posting.
So clearing the cache didn't fix your issue?
Flashing a different kernel didn't fix it either?
At that point it is time to factory reset.
Regardless the ROM troubleshooting is basically the same.
Sent from my SGH-I777 using xda app-developers app
Butchr said:
So clearing the cache didn't fix your issue?
Flashing a different kernel didn't fix it either?
At that point it is time to factory reset.
Regardless the ROM troubleshooting is basically the same.
Sent from my SGH-I777 using xda app-developers app
Click to expand...
Click to collapse
Clearing the cache didn't fix it, but I didn't expect it to since that was done when I did the factory reset before flashing the ROM.
I'm probably going to find a different ROM to use.
Look for a ROM that seems to be in active development. I haven't seen an update on tasks four a while it seems. He may have moved on. The collective has a recent update. I see a lot of people using carbon. Cook updated his pretty regularly. Happy flashing.
Sent from my SGH-I777 using xda app-developers app
Did you specifically clear the Dalvik cache?
I have the same issue and it happens when Trickster MOD is updated, at some point. I get the same message you do. The app would run from the app menu, just not from System -> Kernel Settings.
A full wipe and reset brings everything back. I only recently considered that possibly deleting the dalvik and regular cache may correct the issue after a Trickster update. I have to set aside a little time to backup and test this.
How do/did others handle updating the Trickster app?
The Dalvik cache and regular cache were cleared when I flashed the ROM and I did it again a few days ago, but it still fails going to System->Kernel Settings. I wasn't aware this ran Trickster MOD, and that runs fine from the app menu.
If I have to go thru the full wipe/reset/etc again, I'm going to look at some other ROMs when I do that since Task is no longer updating his ROM for this phone.