This problem is common on phones but i did some popular soultion (fixes below) on the internet (it didnt work) except for flashing a rom. Whenever I hold my home button a message says "The process systemui has stopped".
The fixes i did:
1.Clearing cache
2.Clearing dalvik
3.Clearing app pref.
4.Restart
Im about to go flash ressurection remix rom because this is also one of the popular solution.
Related
Flashed from DamageR_DCG v4.6 Eris Port to CYANOGEN V8 THEMED.
I wish I would have read this post before proceeding further with f*ing up my phone.
I think the following fix would have worked if I hadnt started flashing other roms to try to fix the issue myself.
["-Second: if unresponsive and showing 3G signal bypass setup by touching all four corners of the screen starting with the top left and going clockwise. At the bottom touch the screen just above the language and emergency call buttons."]
After flashing CYANOGEN V8 THEMED, I waited for it to start up and load. Unexpectedly, there was an android icon presented in the middle of the screen, with a hand directing me to touch it. I touched the android icon, it turned white, but that was the end of it. As soon as I let go of the screen, the icon would turn into its normal green and black color scheme. So i touched everywhere, haha, and rotated the screen and continued to press every available space on my phone's screen. I gave up and thought the rom, itself, was "broken". So I tried flashing my previous rom, and the trouble began. I am now experiencing an error message with each rom I try to use. It says "Sorry! The process android.process.acore has stopped unexpectedly. Please try again. Force close button". The error message listed above pops up whenever the phone starts, neither HTC Sense nor Nexus Home loads. I could use some help.
I will try looking for a newer rom version to flash, but I dont think it will work. ;(
**Update - Problem Solved - I did a factory reset/wipe, Dalvik-cache wipe, and proceeded with flashing a new rom.
**Thanks, gnarlyc, it was the Dalvik-cache wipe that fixed the problem.
Go back into recovery and wipe data and dalvik-cache and flash another ROM.
gnarlyc said:
Go back into recovery and wipe data and dalvik-cache and flash another ROM.
Click to expand...
Click to collapse
Okay, I wiped, and am now flashing CELB Froyo2.2.
I will update this post when it is finished.
Cyanogen tazz needs the Google apps flashed right after you flash the rom.
Then you have to wait a minute or so for the 3g icon to appear. Then you can tap the android and proceed with setup.
Tazz v1.0 is super stable and fast. I would try this rom again but make surer you flashed the right Google apps package.
Sent from my Cyanogen Froyo using Tapatalk
Thanks, gnarlyc, it was the Dalvik-cache wipe that fixed the problem.
akaarnaz said:
Thanks, gnarlyc, it was the Dalvik-cache wipe that fixed the problem.
Click to expand...
Click to collapse
Anytime. Been there myself. Not too long ago either.
I have a problem where when I clear the Dalvik Cashe, it says E: Unknown volume SD_ext... People have said on other forums that this is not a problem, but I believe it is because it only happens with ICS roms, and when this started happening, the camera and gallery also stopped working. When I launch the camera or gallery, it says "media scanning" and it immediately closes the app. Anyone have any ideas about this. I'm worrying that I've broken something and I won't be able to use an ICS Rom. So far I've tried a few ICS roms and they all have this problem, but I didn't have this problem with ICS roms before. And Gingerbread roms are fine. None of the problems above.
Did you flash this way?
- Flash CF Repack via Mobile Odin
- Stay in recovery and do the following
- Fullwipe (factory reset)
- Flash ICS ROM
- Fullwipe (factory reset) again. This is important.
- Reboot device.
If you didnt full wipe before and after flash this may of had something to do with it.
Try reflash this way especially if camera is still working on GB.
I also get that same message but no problems with camera. On MIDNOTE ics but also tried TRR 1.5 ics
It isn't a problem. All ICS roms say this. Even on the Galaxy Nexus.
I used Redpill recovery...some say nonsense, but it worked like a charm. I flashed the Midnote ROM w/Chinese leak base (which has Chainfire's kernel in it), then I was able to flash any thing else over that...AOSP, MIUI, ect...
It worked for me.
Question:will someone help me?
I will begin by saying that I have no idea where the problem exists for my individual situation, and it would be great if I could get some help.
Background:
I used to run Dead Rage 1.2.
Now I have been back and fourth between Skrilax nightlies and Bytecode's cm10.1 with little to no hiccups.
Over time I began to notice a little lag(notification drawer, swiftkey, and basic ui elements).
Problem description:
Then I decided to try some other roms to fix my issues.
When I flash Carbon rom:
- It has no lock screen by default (and I have not been able to fix this in lockscreen settings)
- The home button does not work (neither in pie controls)
- the quick settings panel button in the notification drawer does not open the quick settings( nor can I access the quick settings any other way)
- the home screen apps are strangely and slightly above the software buttons
I saw someone with similar problems in the posts of carbon but it was resolved by a single reflash.
I also tried a relatively new rom called Revolt on droidrzr:
- I experienced similar issues with the home button
- I did not delve into the issues more because the issues were similar to carbon
Explained, further:
As explained above I have flashed without issue before.
I am under the impression that the way to flash is:
1. mount system
2. wipe system
3. repeat
4. reboot recovery
5. mount system
6. flash
I have tried every variation on this set of rules I think is possible for carbon. I initially had TWRP 2.3. I have flashed without rebooting recovery, without mounting system, with a factory reset on the previous rom, wiping cache and delvik as well. If I don't wipe the system I get weird crashes and the home button still doesn't work but it fixes other things like quick settings. Sometimes when I would wipe system, and not do a factory reset, and flash carbon all my apps from the Bytecode build persisted. This made me think it was a recovery problem.
Then I flashed TWRP 2.5. I have similarly tried everything with TWRP 2.5 and get the same results. I have tried 6/21, 6/23, 7/2, 7/4 carbon on both recoveries.
I have a backup of bytecode cm10.1 and I am running that currently.
If some one would help me troubleshoot or fix my problem, I would love to get carbon. And I would be very much appreciative.
If I am in the wrong place please point me.
I did not post in the carbon topic because I do not have more than 10 posts.
I know that people are not paid to help me so I respect when they do.
Also if you need screenshots, I can reflash carbon and take some shots too.
mrnathanman said:
Question:will someone help me?
I will begin by saying that I have no idea where the problem exists for my individual situation, and it would be great if I could get some help.
Background:
I used to run Dead Rage 1.2.
Now I have been back and fourth between Skrilax nightlies and Bytecode's cm10.1 with little to no hiccups.
Over time I began to notice a little lag(notification drawer, swiftkey, and basic ui elements).
Problem description:
Then I decided to try some other roms to fix my issues.
When I flash Carbon rom:
- It has no lock screen by default (and I have not been able to fix this in lockscreen settings)
- The home button does not work (neither in pie controls)
- the quick settings panel button in the notification drawer does not open the quick settings( nor can I access the quick settings any other way)
- the home screen apps are strangely and slightly above the software buttons
I saw someone with similar problems in the posts of carbon but it was resolved by a single reflash.
I also tried a relatively new rom called Revolt on droidrzr:
- I experienced similar issues with the home button
- I did not delve into the issues more because the issues were similar to carbon
Explained, further:
As explained above I have flashed without issue before.
I am under the impression that the way to flash is:
1. mount system
2. wipe system
3. repeat
4. reboot recovery
5. mount system
6. flash
I have tried every variation on this set of rules I think is possible for carbon. I initially had TWRP 2.3. I have flashed without rebooting recovery, without mounting system, with a factory reset on the previous rom, wiping cache and delvik as well. If I don't wipe the system I get weird crashes and the home button still doesn't work but it fixes other things like quick settings. Sometimes when I would wipe system, and not do a factory reset, and flash carbon all my apps from the Bytecode build persisted. This made me think it was a recovery problem.
Then I flashed TWRP 2.5. I have similarly tried everything with TWRP 2.5 and get the same results. I have tried 6/21, 6/23, 7/2, 7/4 carbon on both recoveries.
I have a backup of bytecode cm10.1 and I am running that currently.
If some one would help me troubleshoot or fix my problem, I would love to get carbon. And I would be very much appreciative.
If I am in the wrong place please point me.
I did not post in the carbon topic because I do not have more than 10 posts.
I know that people are not paid to help me so I respect when they do.
Also if you need screenshots, I can reflash carbon and take some shots too.
Click to expand...
Click to collapse
see post #7 here: http://forum.xda-developers.com/showthread.php?t=2355676
this should probably be in the Q&A/Help/Troubleshooting section....
Thank You So Much!!!!!!!!!!!!!!!!!
I know its soon and I am still crossing my fingers, but thank you!
A bit of a backstory, I've installed CM13 a while ago, then installed Gapps, everything was working perfectly.
Then a day ago I decided to install Viper4Android, but it was buggy so I decided to uninstall it, they said the best way to do that is to wipe /system, then flash CM13 again, and that's it.
I did that, the ROM still worked flawlessly, but then I realized I also needed to flash Gapps again, so I did, and I constantly got "Unfortunately XY has stopped" messages (it was 2 or 3 things that always stopped, but I can only remember that one of them was Setup Wizard).
I've tried installing Gapps immediately after installing the ROM too, but the results are the same.
Is it possible that it's because I've installed a different variant of Gapps than previously? I couldn't remember if at first I downloaded pico, nano, micro or mini.
Or what else could be the problem?
Deleted
SirOxyGems said:
Good day, This is my first time ever posting a thread on this site and new to custom ROMs on Android devices. I currently have Samsung Galaxy Note 4 (T-Mobile) and a friend suggest I flash it with some custom ROMs. I did, indeed, tried all the compatible ROMs for this phone and they all boot up find (despite the long hang time after finishing the boot setup), but I ran into some problems after doing everything, step-by-step, correctly. I've done light research on how to fix these issues but was afraid if my phone may brick again and do another Emergency Recovery using Samsung Smart Switch. To get to the point, the following issues that are occurring are these below,
- WiFi continuously says "Wifi turning on" and never stops
- Settings will sometimes crash when entering "Security" and then backing out of it
- Camera quality remains blur and can't find any settings to get the camera to focus properly
- LTE/Mobile Data does not apply on boot (when restarting or turning it on) and it requires to fully reboot again
- Uninstalling a application forces the phone to do a soft reboot
- Sometimes multiple background apps will pop-up a error message stating, "Unfortunately, (App) has stopped"
I currently have the Resurrection Remix v5.7.1 (which is the latest I've found) build on the phone, but at the moment using Stock Marshmallow as I'm witting this. If there is anyone on the forums that can help me resolve these issue so i can have a stable flashed ROM, I would greatly appreciated the help. Thanks for your time and have a bless day.
Click to expand...
Click to collapse
Did you have all of these issues on every ROM that you flashed or just a specific ROM?
Sent from my Nexus 6 using XDA-Developers mobile app
Deleted