[Q] XT1032 SystemUI Has Stopped. - Moto G Q&A, Help & Troubleshooting

Hey,
So over the past couple of days I've been trying to get Lollipop working on my XT1032 with no progress so far.
I've tried flashing various different ROMs from across the forums and keep getting an issue where on startup I am met with non-stop systemui has stopped errors. Seen as how this seems to be the same on all the various ROMs I've tried I can see it's my phone. What's wrong with it? I've tried flashing with the latest TWRP & PhilzTouch recoveries and it's the same story. Any thoughts?
Cheers.

Try a full wipe, data, cache, dalvik and reflash.
If still have problems, flash your stock ROM and reflash your custom ROM, that should work.

Thanks for the response.
Just tried that and hasn't made any difference, the SystemUI error is persistent in both custom roms and the stock rom.

TheSkateyBird said:
Thanks for the response.
Just tried that and hasn't made any difference, the SystemUI error is persistent in both custom roms and the stock rom.
Click to expand...
Click to collapse
What recovery are you using? Some are buggy and claim to have successfully wiped, but do not. Try Philz CWM Recovery: https://drive.google.com/drive/#fold...kJHb2dXNmo0N2M

Thanks for the responses, repeated the stock reflash process again and it seems to have sorted the issue.
I'll try using Philz recovery instead this time around.

Related

[Q] 4.3 not rebooting on Verizon Galaxy S 4

So I can't get 4.3 ROMs to reboot. I have tried several different Roms and always the same thing. Mainly Pac. It loads the first time fine, but when I reboot it just hangs on the Galaxy S4 screen. I have updated TWRP to 2.6 and tried wiping cache and dalvik between flashing the ROM and gaaps. And still nothing the only way I can get to do anything after that is to reformat and do a factory reset and the reflash the ROM. Any help would be greatly appreciated.
captainjibblet said:
So I can't get 4.3 ROMs to reboot. I have tried several different Roms and always the same thing. Mainly Pac. It loads the first time fine, but when I reboot it just hangs on the Galaxy S4 screen. I have updated TWRP to 2.6 and tried wiping cache and dalvik between flashing the ROM and gaaps. And still nothing the only way I can get to do anything after that is to reformat and do a factory reset and the reflash the ROM. Any help would be greatly appreciated.
Click to expand...
Click to collapse
So just in case anyone else runs into this problem, I figured it out myself. I am running the MDK build so the only thing you would change is th rooting process.
1. Reflash Stock using ODIN
2. Reroot http://forum.xda-developers.com/showthread.php?t=2381382
3. Install newest 2.6.3 TWRP
4. Back up Stock
5. Flash 4.3 ROM and 4.3 Gapps
I'm not sure if it was reflashing stock or the newest update to twrp but whichever. It worked.

Weird custom rom issue

Just got my n5 and decided to unlock and root it, everything went well until I wanted to flash a rom, no matter what rom I flashed I got all kinds of issues from all apps force closing to bootloops, soft keys not working ect. I've tried flashing stock img, factory reseting ect, nothing seems to work. I'm not sure what's going on here, any help?
I am probably already asking you questions you have already done but... Have you reformated the system, data, and cache partitions prior to flashing? Also are you checking the MD5 of the ROMs you are trying?
Yeah tried all of that, md5's are correct, thanks though
what recovery and version are you on?
what wipes exactly are you performing?
you've checked the md5?
Ok. just trying to narrow things down. When you flash the stock image from https://developers.google.com/android/nexus/images#hammerheadkrt16m are you running the flash-all script? And after that before even adding any apps or changing anything does it give you issues?
@xBeerdroiDx
I'm using cwm 6.0.4.4, wiping system data and cache, and yes I've checked md5's
@neomorphix
Stock works perfectly fine but custom roms gives me issues I listed above, not sure why
Xolith said:
@xBeerdroiDx
I'm using cwm 6.0.4.4, wiping system data and cache, and yes I've checked md5's
@neomorphix
Stock works perfectly fine but custom roms gives me issues I listed above, not sure why
Click to expand...
Click to collapse
are you flashing a gapps add-on package with your custom roms? the right gapps?
Do issues apear straight after flashing the custom ROM or once you start loading apps and changing settings? Also are you using another kernel with the ROMs or the one that comes with them?
simms22 said:
are you flashing a gapps add-on package with your custom roms? the right gapps?
Click to expand...
Click to collapse
Yeah, tried a few including banks, PA 0-day, psx gapps
neomorphix said:
Do issues apear straight after flashing the custom ROM or once you start loading apps and changing settings? Also are you using another kernel with the ROMs or the one that comes with them?
Click to expand...
Click to collapse
They appear right after I flash the rom, tried with both the included and with a custom one
Tried a few days later and it worked, weird haha. Thanks though

[Q] How to I restore my boost mobile moto g?

So the only rom I have on my boost mobile moto g is not working. I flash it and when it boots up i get the phone force closing non stop. Its crazy because i flashed this exact rom zip a few times before and it worked fine. For whatever reason though, it won't now and I'm not sure what to do. As stupid as it is, its the only rom zip i have on my phone....
So how would I go about restoring my moto g... Please help!
Ok....so I got that issue fixed...now the new issue is...whenever i install any rom, besides the stock boost one, i get constant android.process.phone and android.process.acore has stopped errors, non stop! I have tried many different roms, gapps, and both twrp and cwm recovery. roms were working just fine before...i am out of ideas!
itslels said:
So the only rom I have on my boost mobile moto g is not working. I flash it and when it boots up i get the phone force closing non stop. Its crazy because i flashed this exact rom zip a few times before and it worked fine. For whatever reason though, it won't now and I'm not sure what to do. As stupid as it is, its the only rom zip i have on my phone....
So how would I go about restoring my moto g... Please help!
Ok....so I got that issue fixed...now the new issue is...whenever i install any rom, besides the stock boost one, i get constant android.process.phone and android.process.acore has stopped errors, non stop! I have tried many different roms, gapps, and both twrp and cwm recovery. roms were working just fine before...i am out of ideas!
Click to expand...
Click to collapse
Just try a clean installation bro format data , cache, davic cache and under mount and storage delete system ,data, cache bro just try this once
And flash a correct gapps pack for the ROM sure it will work
moha07 said:
Just try a clean installation bro format data , cache, davic cache and under mount and storage delete system ,data, cache bro just try this once
And flash a correct gapps pack for the ROM sure it will work
Click to expand...
Click to collapse
I did that many times and flashed many different roms and gapps packages and kept having same issue. I finally fixed it though. I had to restore it back to stock by flashing the stock firmware with fastboot. Roms work now. :good:

[Q] Got stuck in Bootloop

Hello xda community. I have a problem. I've been using Nexus experience rom(MM) and i've decided to go back to LP. I tried so many LP roms and after a short use(1 hour to 1 day, depends on rom) it gives me a bootloop. I tried 4-5 roms. One of them was my daily driver one month ago. Now I am using stock 5.1 with root and no problem at all. But why a custom rom gives me bootloop All answers appreciated.
Edit: Now i got bootloop on stock 5.1 too!! Please help!
Have you installed xposed framework?
No. The problem encountered after CM. I formatted system, data (not internal storage) but i got bootloops since then.
Have you tried flashing stock vía fastboot?
Nope, but is there any difference between flashing via fastboot or recovery?
well if you flash stock via fastboot, it will also reset some partitions and system files like radio/modem or gps
flashing via recovery just changes the OS and kernel
Than you. And is this procedure needs full wipe?

Help. Unable to revert back to stock/stock based rom, only CM works. (N910C)

Hi.
Im a noob on XDA but have enjoyed the freedom of custom roms for some time now on my note 4 (N910C). So far it has only been stock based touchwiz roms. A few days ago i decided to give CM13 a go and since then i have been unable to revert back. Every touchwiz rom (stock and custom) i have tried just ends in a bootloop but when i flash CM13 again it boots up just fine.
I have tried flashing numerous android 6.0.1 stock roms through odin, even from different regions but still for the same version. Its always stuck in a bootloop.
Tried flashing stock and then immediately flashing custom stock based rom (both clean install after wiping and trying to dirty flash over stock rom)
I have done all the suggestions of factory resetting, wiping caches and you name it after clean flashes and even tried them with dirty flashes. Whatever i do i cannot get any stock or stock based rom to boot up.
A few months ago i tried out cm12.1 and had no problem going back to a stock based rom, but after CM13 my phone absolutely refuses to boot anything stock or stock based.
I would appreciate any advice and suggestions. Please ask if theres any more info needed of my device or roms i already tried.
JackalJC said:
Hi.
Im a noob on XDA but have enjoyed the freedom of custom roms for some time now on my note 4 (N910C). So far it has only been stock based touchwiz roms. A few days ago i decided to give CM13 a go and since then i have been unable to revert back. Every touchwiz rom (stock and custom) i have tried just ends in a bootloop but when i flash CM13 again it boots up just fine.
I have tried flashing numerous android 6.0.1 stock roms through odin, even from different regions but still for the same version. Its always stuck in a bootloop.
Tried flashing stock and then immediately flashing custom stock based rom (both clean install after wiping and trying to dirty flash over stock rom)
I have done all the suggestions of factory resetting, wiping caches and you name it after clean flashes and even tried them with dirty flashes. Whatever i do i cannot get any stock or stock based rom to boot up.
A few months ago i tried out cm12.1 and had no problem going back to a stock based rom, but after CM13 my phone absolutely refuses to boot anything stock or stock based.
I would appreciate any advice and suggestions. Please ask if theres any more info needed of my device or roms i already tried.
Click to expand...
Click to collapse
You might be having kernel issues. If the stock you're flashing is a flashable zip then it might not include the stock kernel, if it doesn't include the stock kernel then its leaving the custom kernel from CM13. If that's the case it won't work because stock won't work with a CM kernel.
You said you did the wipes when you flashed, did you mean that you did factory reset, wipe cache and wipe dalvik cache? Or did you mean that you did the advanced wipe options to wipe system partition and data partition before flashing?
If you didn't do the advanced wipe before flashing then it might help if you did them before flashing. Wipe system and wipe data then factory reset then flash ROM then wipe cache and dalvik after flashing then reboot.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
Droidriven said:
You might be having kernel issues. If the stock you're flashing is a flashable zip then it might not include the stock kernel, if it doesn't include the stock kernel then its leaving the custom kernel from CM13. If that's the case it won't work because stock won't work with a CM kernel.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
Click to expand...
Click to collapse
I flash stock roms through Odin with the .tar.md5 file.
JackalJC said:
Hi.
Im a noob on XDA but have enjoyed the freedom of custom roms for some time now on my note 4 (N910C). So far it has only been stock based touchwiz roms. A few days ago i decided to give CM13 a go and since then i have been unable to revert back. Every touchwiz rom (stock and custom) i have tried just ends in a bootloop but when i flash CM13 again it boots up just fine.
I have tried flashing numerous android 6.0.1 stock roms through odin, even from different regions but still for the same version. Its always stuck in a bootloop.
Tried flashing stock and then immediately flashing custom stock based rom (both clean install after wiping and trying to dirty flash over stock rom)
I have done all the suggestions of factory resetting, wiping caches and you name it after clean flashes and even tried them with dirty flashes. Whatever i do i cannot get any stock or stock based rom to boot up.
A few months ago i tried out cm12.1 and had no problem going back to a stock based rom, but after CM13 my phone absolutely refuses to boot anything stock or stock based.
I would appreciate any advice and suggestions. Please ask if theres any more info needed of my device or roms i already tried.
Click to expand...
Click to collapse
Usually if it bootloops after flashing with Odin, you boot to stock recovery and factory reset/wipe cache and it should boot after that.
The times that you tried stock and then went back to CM13, are you rooting and reflashing TWRP again so you can flash back to CM13? Or is it leaving custom recovery on the device even after flashing with Odin? If its leaving TWRP on the device then Odin isn't flashing correctly.
Are you flashing the full stock firmware in Odin? Or are you flashing a modified stock .tar?
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
Droidriven said:
Usually if it bootloops after flashing with Odin, you boot to stock recovery and factory reset/wipe cache and it should boot after that.
The times that you tried stock and then went back to CM13, are you rooting and reflashing TWRP again so you can flash back to CM13? Or is it leaving custom recovery on the device even after flashing with Odin? If its leaving TWRP on the device then Odin isn't flashing correctly.
Are you flashing the full stock firmware in Odin? Or are you flashing a modified stock .tar?
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
Click to expand...
Click to collapse
I have tried all the factory reset/wipe cache suggested on other threads and websites i have found regarding bootloops.
When going back to CM13 after trying methods to get stock back i flash TWRP again as flashing stock through Odin replaces TWRP with stock recovery again and then do a restore of CM13 through TWRP with all my necessary apps on, much easier than installing everything again after each try (a fresh install of CM13 also works fine with no problems). I also tried various versions of Odin just in case it was a problem with the version i used but every time i get the same same results.
I am flashing full pure stock from sammobile.

Categories

Resources