Hello.
I have had Remix Res. 3.1.3 as a 2nd ROM for a few weeks now. Recently it became unusable.
When it boots, the start-up animation stutters. When finally boots I right away receive "System UI has stopped" & "android.phone" has stopped".
No buttons are usable. It will just give me one of those errors until I physically remove the battery.
My main ROM is JellyBAM 4.0.0 and is working great.
Kernel on both ROMs is Siyha 5.0.1.
I tried completely removing the 2nd ROM, and re-installing it. I tired a complete wipe/clear and also fix permissions.
Nothing solved this.. What can be causing such problem???
RadicalxMind said:
Hello.
I have had Remix Res. 3.1.3 as a 2nd ROM for a few weeks now. Recently it became unusable.
When it boots, the start-up animation stutters. When finally boots I right away receive "System UI has stopped" & "android.phone" has stopped".
No buttons are usable. It will just give me one of those errors until I physically remove the battery.
My main ROM is JellyBAM 4.0.0 and is working great.
Kernel on both ROMs is Siyha 5.0.1.
I tried completely removing the 2nd ROM, and re-installing it. I tired a complete wipe/clear and also fix permissions.
Nothing solved this.. What can be causing such problem???
Click to expand...
Click to collapse
anyone?
RadicalxMind said:
anyone?
Click to expand...
Click to collapse
I experience the exact same thing. Managed to install RR_JB_V3.1.3_AOKP_4.2.1_I9100 as 2nd rom, tried both kernels, and when it loads up, the boot animation goes frame by frame, and as soon as its done, i get "System UI has stopped" & "android.phone has stopped" until i force a reboot.
wipedcache and delvik before installation, didnt help.
Any directions? could i give any more information that would be useful to identify the problem?
I've three options in mind:
Maybe the free space is to small to that the kernel save this for primary System.
Did u try to update ur kernel?
U both said u wipe and clear all, but did u even do a full wipe? (format data/system/cache)
Sorry no more ideas atm.
CHEERS
Sent from my GT-I9100 running with RootBox
Did you tried other 4.2.1 ROM then RR?
Maybe its a bug with 4.2.1 version at siyah 5 (when its become 2nd rom)
Oh I didn't recognized that it's 4.2.1
I think that's a problem, too, because this need an actual kernel but they don't support dual boot atm.
So I would say no (correct) dual boot in connection with 4.2.1
CHEERS
Sent from my GT-I9100 running with RootBox
Hannibal226 said:
Oh I didn't recognized that it's 4.2.1
I think that's a problem, too, because this need an actual kernel but they don't support dual boot atm.
So I would say no (correct) dual boot in connection with 4.2.1
CHEERS
Sent from my GT-I9100 running with RootBox
Click to expand...
Click to collapse
thanks for your reply, i didnt try any other rom, but what you say makes sense.
good day
Related
Hello,
So as title says, i own rooted HTC Wildfire S. I had CM7.2 and it was great, i had no problems with it at all. I decided to install CM9, which should be better, but it won't work... The problem is: The CM9 logo shines at the start, but when i try to Touch the Android to begin, the table appears with "Unfortunately, Setup Wizard has stopped.". What should i do? I tried to Wipe cache, wipe dalvik, Factory reset, nothing helped.
If someone know how to solve it, please tell me, thanks in advance.
Did u try to reflash the rom
did u added gaps
How to reflash rom?
Yes, i added gapps.
put the cm rom on youre sd card enter recovery whipe data/cash partition
than apply zip from sd card and reinstall it
if this doesnt work and u want to get back to a stock rom read this:
http://forum.xda-developers.com/showthread.php?t=1706918
Thank You very much, jiffer1991! You helped me a lot, but some issues still remain, like when i go to Settings -> Themes, then Settings has stopped, it seems to be only one problem (so far).
Manding said:
Thank You very much, jiffer1991! You helped me a lot, but some issues still remain, like when i go to Settings -> Themes, then Settings has stopped, it seems to be only one problem (so far).
Click to expand...
Click to collapse
do you mean the theme choser?
Well, i believe it's Theme chooser, i have one Theme as an app, i think it was developed by LeWa, and the other one is in the Settings as an default option. LeWa's Theme app is working fine.
Manding said:
Well, i believe it's Theme chooser, i have one Theme as an app, i think it was developed by LeWa, and the other one is in the Settings as an default option. LeWa's Theme app is working fine.
Click to expand...
Click to collapse
Hmm if it wont be fixed in the next release ask the developer for help
cm is still a custom rom and bugs are still a problem
for my device I9001 there are both cm7 and cm9 in none of them camera and wifi thethering works
Manding said:
Hello,
So as title says, i own rooted HTC Wildfire S. I had CM7.2 and it was great, i had no problems with it at all. I decided to install CM9, which should be better, but it won't work... The problem is: The CM9 logo shines at the start, but when i try to Touch the Android to begin, the table appears with "Unfortunately, Setup Wizard has stopped.". What should i do? I tried to Wipe cache, wipe dalvik, Factory reset, nothing helped.
If someone know how to solve it, please tell me, thanks in advance.
Click to expand...
Click to collapse
you have installed wrong version of gapp because of this you getting that error, as i was getting same error after updating with correct gapp everthing was working fine , search for universal gapp for ics 4.0.*
touch the corners of the screen from the bottum right in clockwise order
it will bypass the setup
I recently updated to the most recent version of paranoid android with a clean install (full wipe) and I'm experiencing multiple bugs. There's no lock screen when I turn the screen on and the home key doesn't work at all, apart from waking the phone up (can't exit apps with it or long press for recent apps). I'm receiving no notifications in my task bar and no incoming call alerts, although the notifications and calls are working in the background. Plus the stock browser won't start up.
The strangest thing is ...after returning to stock sammy rom all these bugs are gone but when I flash cm10 or aokp based rom back, all these same bugs come back regardless of what kernel I use (latest siyah or cm10 kernel).
All system settings are unchanged from default values so these bugs aren't setting related. I've done multiple full wipes with totally clean installs but, I'm still greeted with these bugs upon booting. Does anyone have the slightest idea why I'm plagued by these issues ...the phone is pretty unusable at the moment with these problems. No home key means so many extra taps on the screen and a lot of extra time wasted and I'm missing all my calls and texts because of no notifications. Please if anyone knows how to fix this ....it'll be much appreciated!!
Bumping cause I'm kinda desperate for some help.
Has no one experienced this kind of behaviour on their GSII? I'm really at a loss as to how to fix this. I've been flashing roms on my GSII for over a year now and never heard or seen anything like this before. I really can't face going back to sammy rom which seems to be the only thing to fix this.
please list all the steps you took when you flashed CM10/paranoid
Hi and thanks for the reply. All the relevent steps I took in CWM were
1 Wiped data/Factory Reset
2 Wiped Cache
3 Wiped Dalvik Cache
4 Ran a kernel cleaning script
5 Installed PA v2.17
6 Installed gaps
7 Fixed permissions
It's just really weird how these bugs are happening on both aokp (official) and PA, so it's obviously nothing to do with the roms. Just can't figure out what the problem is at all. I'm going to try the Super Nexus rom soon to see if that's any different.
Sebalon said:
Hi and thanks for the reply. All the relevent steps I took in CWM were
1 Wiped data/Factory Reset
2 Wiped Cache
3 Wiped Dalvik Cache
4 Ran a kernel cleaning script
5 Installed PA v2.17
6 Installed gaps
7 Fixed permissions
It's just really weird how these bugs are happening on both aokp (official) and PA, so it's obviously nothing to do with the roms. Just can't figure out what the problem is at all. I'm going to try the Super Nexus rom soon to see if that's any different.
Click to expand...
Click to collapse
Can you post your present ROM and kernel details?
Jokesy said:
Can you post your present ROM and kernel details?
Click to expand...
Click to collapse
At the moment I have official aokp build 4 rom installed with Siyah v4.1.5 kernel and the very same 4 bugs persist (no lock screen, broken home key, no notifications and stock browser unable to start up)
Sebalon said:
At the moment I have official aokp build 4 rom installed with Siyah v4.1.5 kernel and the very same 4 bugs persist (no lock screen, broken home key, no notifications and stock browser unable to start up)
Click to expand...
Click to collapse
Ok.
Try these steps:
In CWM recovery,
- wipe data / factory reset
- format /system (under mounts and storage)
- flash ROM
- flash Gapps
- reboot recovery (under Advanced)
- flash ROM
- flash Gapps
- fix permissions (under Advanced)
- reboot phone
Done
Jokesy said:
Ok.
Try these steps:
In CWM recovery,
- wipe data / factory reset
- format /system (under mounts and storage)
- flash ROM
- flash Gapps
- reboot recovery (under Advanced)
- flash ROM
- flash Gapps
- fix permissions (under Advanced)
- reboot phone
Done
Click to expand...
Click to collapse
OK ..I will try your method. I'll report back as soon as I've competed thanks
Hi ...I tried the procedure exactly as you instructed but the problem persist. However ...a couple of times during the procedure I saw that cwm was having problems mounting the sdcard. "fail mounting sdcard" I think. I'm not sure whether its referring to internal or external. I don't have an external inserted at the moment anyhow. If it refers to internal sd then maybe the answer to my problem can be found there?
Sebalon said:
Hi ...I tried the procedure exactly as you instructed but the problem persist. However ...a couple of times during the procedure I saw that cwm was having problems mounting the sdcard. "fail mounting sdcard" I think. I'm not sure whether its referring to internal or external. I don't have an external inserted at the moment anyhow. If it refers to internal sd then maybe the answer to my problem can be found there?
Click to expand...
Click to collapse
SDcard refers to your external SD.
Jokesy said:
SDcard refers to your external SD.
Click to expand...
Click to collapse
Oh well then I guess it's not a problem with internal memory then. Damn I thought I was onto something! Thanks for your efforts so far but do you have any other ideas where this problem may be coming from?
Sebalon said:
Oh well then I guess it's not a problem with internal memory then. Damn I thought I was onto something! Thanks for your efforts so far but do you have any other ideas where this problem may be coming from?
Click to expand...
Click to collapse
The stock Sammy ROM you talked about, were they custom ROMs or stock unmodified firmwares?
Jokesy said:
The stock Sammy ROM you talked about, were they custom ROMs or stock unmodified firmwares?
Click to expand...
Click to collapse
The stock Sammy ROM is unmodified XX OXA from about a year ago ...I keep it around in case of boot loops during an upgrade.
Sebalon said:
The stock Sammy ROM is unmodified XX OXA from about a year ago ...I keep it around in case of boot loops during an upgrade.
Click to expand...
Click to collapse
is the stock sammy firmware Gingerbread or ICS?
Jokesy said:
is the stock sammy firmware Gingerbread or ICS?
Click to expand...
Click to collapse
Hey Jokesy, thanks for getting back to me. Its gingerbread ...that was the last time I used stock unmodified sammy. So you think if I install stock sammy ICS it may fix the problem?
Sebalon said:
Hey Jokesy, thanks for getting back to me. Its gingerbread ...that was the last time I used stock unmodified sammy. So you think if I install stock sammy ICS it may fix the problem?
Click to expand...
Click to collapse
That was the cause of the problem.
you need to first flash either Custom Stock based ICS Rom via CWM recovery, or flash an unmodified Stock firmware via Odin before flashing an Aosp ICS or Jelly bean ROM.
So please flash stock ICS firmware now.
Problem solved.
Jokesy said:
That was the cause of the problem.
you need to first flash either Custom Stock based ICS Rom via CWM recovery, or flash an unmodified Stock firmware via Odin before flashing an Aosp ICS or Jelly bean ROM.
So please flash stock ICS firmware now.
Problem solved.
Click to expand...
Click to collapse
OK will download ICS Stock rom right away ....thanks alot for your help and patience. Guys like you really make the difference in this community, I really can't thank you enough. I'll report back as soon as I'm done.
No luck thus far ...I installed NeatRomLight on which the problems weren't present but as soon as I flashed back to PA the problems were back. I tried with the same instructions you gave in the earlier post with reboot of recovery and such. This really is a strange one. What confuses me most is the fact that everything works fine with stock sammy or modded sammy but, thats the last thing I want to go back to after using aosp/cm based roms for the last 6 months.
Maybe if I download stock unmodified rom eh? Well it can't hurt to try anyways.
Were you trying to install the latest version of PA on siyah? That doesn't work. Right now PA 2.17 and above will only run on the CM10 kernel..same goes for latest pure aokp builds I think.
If you want to stick to siyah and PA, download PA 2.16. It should work.
Sent from my GT-I9100 using xda app-developers app
"Process system isnt responding. Do you want to close it?
wait report ok
I get this message ALOT on all the JB roms out there now; it happens after a reboot/restart, and if I click ok, things seem to work normally after a few seconds...
Anyone else seeing this alot? Anyone figure out a way to stop it?
thanks!
Wipe data, cache and dalvik.
Sent from my SAMSUNG-SGH-I717 using xda premium
johnrippa said:
Wipe data, cache and dalvik.
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
wiping data will mean you have to reinstall your rom
I've wiped cache/dalvik numerous times, and it still happens
and, when I flash new rom, i factory reset, wipe data/cache/dalvik, and run darkstar system wipe, and it still happens
First try fixing permissions from within your recovery.
_____________________
Black Star VIII
ZPaul2Fresh8 said:
First try fixing permissions from within your recovery.
_____________________
Black Star VIII
Click to expand...
Click to collapse
did that many many times, and it doesnt help
wase4711 said:
did that many many times, and it doesnt help
Click to expand...
Click to collapse
Did you restore apps from titanium backup? If so that may be it.
_____________________
Black Star VIII
Me too
Hello,
this problem happens to me too for a few day now.
System not responding at every boot, but everything seems normal.
when i flash a new nightlie and it reboots, i do not get this message. But after i reboot again it reapears.
after a search i found this, there: http://www.modaco.com/topic/359832-devrom152-cyanogenmod-101-android-422/
its for zte blade
[DEV][ROM][15.2.] CyanogenMod 10.1 (Android 4.2.2)
"11.2.2013 changelog:
reverted commits (1,2) that caused 'Process system isn't responding' issue on every reboot"
(the comits have something to do with the new FM stuff in the rom)
Maybe someone want to have a look at it?
I can not post in the official CM10.1-galaxysmtd thread yet.
Greeting, Strainhunter
Problem gone (i hope)
strainhunter said:
Hello,
this problem happens to me too for a few day now.
System not responding at every boot, but everything seems normal.
when i flash a new nightlie and it reboots, i do not get this message. But after i reboot again it reapears.
after a search i found this, there: http://www.modaco.com/topic/359832-devrom152-cyanogenmod-101-android-422/
its for zte blade
[DEV][ROM][15.2.] CyanogenMod 10.1 (Android 4.2.2)
"11.2.2013 changelog:
reverted commits (1,2) that caused 'Process system isn't responding' issue on every reboot"
(the comits have something to do with the new FM stuff in the rom)
Maybe someone want to have a look at it?
I can not post in the official CM10.1-galaxysmtd thread yet.
Greeting, Strainhunter
Click to expand...
Click to collapse
Hello Again,
The problem is gone for me i found out that it has something to do either with the Theme i was using, or/and the Launcher. Because i first switched my Launcher (Nova Launcher) to the Stock one (Trebuchet) (merely just because i did not know how i should fix that problem) then at the after the first reboot with stock launcher the problem was gone, but came back after i rebooted again. So i changed my Theme (JellyBeanExtreme) and the problem did not appear again "knockin´3x on wood^^"
Maybe this can help someone who had or will have this problem.
Greetings,
Strainhunter
wase4711 said:
wiping data will mean you have to reinstall your rom
I've wiped cache/dalvik numerous times, and it still happens
and, when I flash new rom, i factory reset, wipe data/cache/dalvik, and run darkstar system wipe, and it still happens
Click to expand...
Click to collapse
Eh, nope. That would be if you wiped your system. Wiping data will take away all your apps and customizations, but will leave the ROM intact (remember: "ROM" = "Read-Only Memory").
IMO if you want to start anew as a first level troubleshoot, it's much easier to wipe cache/dalvik/SYSTEM, then reflash your ROM and GAPPS. This has solved my problems about 90% of the time, especially when I've installed a mod my phone doesn't like, or done something stupid while messing around in /system/.
CPA Poke said:
Eh, nope. That would be if you wiped your system. Wiping data will take away all your apps and customizations, but will leave the ROM intact (remember: "ROM" = "Read-Only Memory").
IMO if you want to start anew as a first level troubleshoot, it's much easier to wipe cache/dalvik/SYSTEM, then reflash your ROM and GAPPS. This has solved my problems about 90% of the time, especially when I've installed a mod my phone doesn't like, or done something stupid while messing around in /system/.
Click to expand...
Click to collapse
Does that leave your apps and data in place? Never thought of that
Sent from my SGH-I717 using XDA Premium HD app
did u install the walkman app for the note?
I had the same problem. I uninstalled Nova launcher but it was still giving me the same error.
I uninstalled Cobalt theme for CM 10 and that fixed it. Hopefully it gets updated to 10.1, I like the theme.
Sent from my SAMSUNG-SGH-I717 using xda premium
briand.mooreg said:
I had the same problem. I uninstalled Nova launcher but it was still giving me the same error.
I uninstalled Cobalt theme for CM 10 and that fixed it. Hopefully it gets updated to 10.1, I like the theme.
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
i was also getting this error using Jamies 10.1 rom.....found out it went away when i stoppped trying to use a theme. im using the TouchWiz launcher and no theme and no more error.
so if any one is using a theme and getting this error stop using a theme and see if that helps....
jrea77 said:
i was also getting this error using Jamies 10.1 rom.....found out it went away when i stoppped trying to use a theme. im using the TouchWiz launcher and no theme and no more error.
so if any one is using a theme and getting this error stop using a theme and see if that helps....
Click to expand...
Click to collapse
It is absolutely the themes that do this. However, from what I read up on it there is literally nothing actually going wrong with the device except for a teeny couple of extra seconds on boot up (which can supposedly be rectified by hitting "Wait" instead of "Stop" or whatever it says.
Actually, I even remember them saying that the mere fact that you're getting the error message means that it's installed correctly.. Something about the stock framework not liking being modified.
CPA Poke said:
It is absolutely the themes that do this. However, from what I read up on it there is literally nothing actually going wrong with the device except for a teeny couple of extra seconds on boot up (which can supposedly be rectified by hitting "Wait" instead of "Stop" or whatever it says.
Actually, I even remember them saying that the mere fact that you're getting the error message means that it's installed correctly.. Something about the stock framework not liking being modified.
Click to expand...
Click to collapse
ya...i noticed nothing was really wrong while getting the error, it just bug me that i was getting that little pop up window. i would hit "wait" or "cancel" and it didnt seem to make a difference, it would go away and that was it. once in a while it would pop back up when getting a text or call, before i could answer the call i had to click it to make it go away to be able to answer. so i decided not to use the theme and not worry about that error.....so would it be any theme or just some themes? maybe ill try other themes and see what happens.....
I have a GTab 10.1. I was using CM10 nightly build and it worked like a charm. Yesterday it started to crash. It boots, works OK and then crashes 30sec to 1 minute after that. It reboots and here we go again, and again.
I wiped user data, but it didn't help. I also restored one of the earlier backups. No success. I formated /system, /data, /cache and /preload from CWM and installed an older CM9 rom, which I have on my sd-card. Same behaviour as before.
I wanted to install latest CM10 nightly, but I am unable to upload it to the device as it crashes before it finishes.
It works fine (no crashes) in CWM recovery mode.
What else should I try? And ideas? Could be something wrong with the hardware?
Thanks in advance!
Try starting from first flash ics, bootloader then the latest build of cm10.....
Tapatalked from galaxy y
kishorsidu said:
Try starting from first flash ics, bootloader then the latest build of cm10.....
Tapatalked from galaxy y
Click to expand...
Click to collapse
Sorry... do not undestand. ics meaning stock firmware?
In the meanwhile I also noticed that tab sometimes just freezes and does not reboot. If I leave it like this for some time it becomes quite hot (as CPU would be under very high load - some infinite loop maybe?).
Are you overclocked? Maybe have an overclock set on boot
I have a same problem, but i manage to fix it.
First I flash my rom to ICS 4.0.4 P7500XXLQ8 using odin.
After flashing complete, wipe cache, factory reset than reboot.
And whallaaa........your tab is back to normal again. ^^
I hope this info can help you.
H. Ess said:
Are you overclocked? Maybe have an overclock set on boot
Click to expand...
Click to collapse
Hm... that might be an issue. I was playing with overclocking a while ago and totally forgot about it. Now I restored from an old backup (honeycomb), where I still had an old kernel. It has been working without freeze for some minutes now.
What should be the right procedure to upgrade back to 4.x? Can I just install CM10 over it?
Thank you all for your help!
[SOLVED] Crashes almost immediatley after boot
Installed CM10 and it works great. Thank you all for your help!
First of all: I have had my S II water damaged some months ago. It works fine that far (exept that the sensor keys are dead). Not sure if there is some other hardware malfunctioning...
Currently im running on MIUI and everything is fine, but recently I found out that no other ROM will work on my Phone:
- Samsung stock ROM runs extreme (!) laggy. Took me about 5 Minutes to go through the menus and enable USB debugging.
- CM9/ AOKP will reset immediately after system startup
- CM10 shows laggy boot animation for few secs, then bootloops
Only other ROM that works is "cMIUI". Which is a CM10 based ROM only with a MIUI userinterface...
What can I do to find out whats the problem with my phone??
Thats weird. Have you tried wiping data before flashing each of these ROMs? Next time, try formatting /system, /data, cache and dalvik cache. Also, have you tried using those kernel cleaning scripts, etc?
Sent from my GT-I9100 using Tapatalk 2
Spiralzz said:
Thats weird.
Click to expand...
Click to collapse
YES :laugh:
Spiralzz said:
Have you tried wiping data before flashing each of these ROMs? Next time, try formatting /system, /data, cache and dalvik cache.
Click to expand...
Click to collapse
Wiped and formatted like hell. I've hit every single wipe/ clean/ format option in the recovery. Also I have installed a dualboot kernel and installed CM as "second rom", where no ROM has gone before.....
Spiralzz said:
Also, have you tried using those kernel cleaning scripts, etc?
Click to expand...
Click to collapse
I Have tried different Kernels, all with the same effect. What kernel cleanig scripts specifically?
Rottnroll said:
YES :laugh:
Wiped and formatted like hell. I've hit every single wipe/ clean/ format option in the recovery. Also I have installed a dualboot kernel and installed CM as "second rom", where no ROM has gone before.....
I Have tried different Kernels, all with the same effect. What kernel cleanig scripts specifically?
Click to expand...
Click to collapse
Only one option I can think of is to go back to stock samsung rom then claim your warranty if you have it. Or, make a logcat and paste it here (upload to Dropbox or somewhere then past a link over here) and someone experienced might take a look.
Since you've already wiped everything, I'm more inclined to think that it's a hardware problem now. However, let's hope someone more experienced pops in and helps. Good luck
Sent from my GT-I9100 using Tapatalk 2
See two logs below, trying to boot cm9. One with default kernel, one with Siyah. Would be great if anybody could find out whats the issue.
https://www.dropbox.com/s/z7q3wbz1h9uhhvg/logcat_cm9_s2.txt
https://www.dropbox.com/s/r1l9umovmxx7jpo/logcat_cm9_s2_siyah.txt
In both logs the phone booted and showed the Pin dialog, then after few seconds rebooted.
As the Phone had been waterdamaged Im pretty shure warranty is absolutely void Also I think that the problems are due to some Hardware malfunctioning. Just want to know what and if theres some way to workaround.