I've unlocked the bootloader, rooted my Moto G (xt1032) with superboot and installed CWM recovery on it. So I tried installing Cyanogenmod 11 (cm-11-20140405-SNAPSHOT-M5-falcon.zip at the moment) for my device and initially, everything works fine. It boots pretty smooth and downloads all the apps from the Google Play Store. But when I reboot the device I get the error "Unfortunately com.android.systemui has stopped" a few times. After clicking "okay" I get to enter my PIN for my SIM card, but then it just gets worse. The error pops up constantly and I have no possibility of selecting anything else. The apps on my wallpaper dissappear and appear again, the wallpaper switches to fullscreen, then normal again and so on. Wiping cache or dalvik cache does nothing, only a factory reset helps. Then it installs all the apps again, but when I reboot, the same problem persists.
Some threads suggested it may be an app and since it only happens when I reboot, could it be an app that launches on boot?
Others suggested trying an older version of Cyanogenmod (which is why I'm using M5 at the moment. M6 gave the exact same problem). Or has it something to do with the gapps file I'm using?
Any ideas on how to fix this? Thanks in advance.
Narcotle said:
I've unlocked the bootloader, rooted my Moto G (xt1032) with superboot and installed CWM recovery on it. So I tried installing Cyanogenmod 11 (cm-11-20140405-SNAPSHOT-M5-falcon.zip at the moment) for my device and initially, everything works fine. It boots pretty smooth and downloads all the apps from the Google Play Store. But when I reboot the device I get the error "Unfortunately com.android.systemui has stopped" a few times. After clicking "okay" I get to enter my PIN for my SIM card, but then it just gets worse. The error pops up constantly and I have no possibility of selecting anything else. The apps on my wallpaper dissappear and appear again, the wallpaper switches to fullscreen, then normal again and so on. Wiping cache or dalvik cache does nothing, only a factory reset helps. Then it installs all the apps again, but when I reboot, the same problem persists.
Some threads suggested it may be an app and since it only happens when I reboot, could it be an app that launches on boot?
Others suggested trying an older version of Cyanogenmod (which is why I'm using M5 at the moment. M6 gave the exact same problem). Or has it something to do with the gapps file I'm using?
Any ideas on how to fix this? Thanks in advance.
Click to expand...
Click to collapse
Mine did this once and what worked for me was fixing permissions.
DarkVanguard said:
Mine did this once and what worked for me was fixing permissions.
Click to expand...
Click to collapse
Tried fixing permissions before even installing any app. Rebooted, no luck. Still the same error without even a google account linked or app installed.
Narcotle said:
Do you remember which permissions exactly?
Click to expand...
Click to collapse
You need to do it from your recovery. In TWRP, there is a button that says "Fix Permissions." I'm sure it's available in CWM, as well.
DarkVanguard said:
You need to do it from your recovery. In TWRP, there is a button that says "Fix Permissions." I'm sure it's available in CWM, as well.
Click to expand...
Click to collapse
CWM recovery didn't have a fix permissions setting, so I flashed TWRP through fastboot. Fixed permissions, rebooted: same error.
Did another factory reset and cache, sideloaded CM11 snapshot M5 and GApps to TWRP, flashed again. CM11 booted fine, just like it always does the first time. Had to reboot into recovery in order to fix permissions (wasn't able to do that right after I flashed CM). Rebooted again and still the same error.
Narcotle said:
CWM recovery didn't have a fix permissions setting, so I flashed TWRP through fastboot. Fixed permissions, rebooted: same error.
Did another factory reset and cache, sideloaded CM11 snapshot M5 and GApps to TWRP, flashed again. CM11 booted fine, just like it always does the first time. Had to reboot into recovery in order to fix permissions (wasn't able to do that right after I flashed CM). Rebooted again and still the same error.
Click to expand...
Click to collapse
Try manually wiping system, data, cache, and dalvik. If that doesn't work, try a different gapps package. If it still gives the same error after that...then I don't know.
I had the same problem : I just flashed cm nighglies instead and waited for one enough stable...
Related
Hello,
I'm currently in some trouble with my phone.
Yesterday out of no thing I got the mentioned error "uids on the system are inconsistent you need to wipe your data partition"
My Moto G was only unlocked and rooted and basically Stock FW.
After I got this error I was like "well this sucks but ok" so I booted into the recovery (I pre-installed the recovery from the Cyanogen Mod thread) wiped it and booted again but nothing, the error still appeared.
So my next step was to try to flash a custom rom - I flashed CyanogenMod which ended in a boot loop. I flashed a stock firmware again aaaaand yes, the UIDs error was still persistent.
I also wiped the dalvik cache and the fix on the internet "use fix permissions in recovery" does not work as there is no such menu entry :/
So yeah, please help to resolve this this problem - I like my phone
Ireas said:
Hello,
I'm currently in some trouble with my phone.
Yesterday out of no thing I got the mentioned error "uids on the system are inconsistent you need to wipe your data partition"
My Moto G was only unlocked and rooted and basically Stock FW.
After I got this error I was like "well this sucks but ok" so I booted into the recovery (I pre-installed the recovery from the Cyanogen Mod thread) wiped it and booted again but nothing, the error still appeared.
So my next step was to try to flash a custom rom - I flashed CyanogenMod which ended in a boot loop. I flashed a stock firmware again aaaaand yes, the UIDs error was still persistent.
I also wiped the dalvik cache and the fix on the internet "use fix permissions in recovery" does not work as there is no such menu entry :/
So yeah, please help to resolve this this problem - I like my phone
Click to expand...
Click to collapse
I had this problem, and I was able to fix it through my TWRP Custom Recovery. You're using a CWM recovery, right? I searched, and found that there is an option to fix permissions in CWM. Advanced > Fix Permissions.
Probably the cleanest solution HERE
So I unlocked, rooted and installed Euphoria ROM on my Moto G today, and now I'm perplexed to find that when I select the "Reboot" option either in Android or TWRP, I immediately get shoved back into TWRP. Rebooting to Bootloader works as expected, rebooting to Recovery works as expected, but the normal reboot doesn't.
Also, when my phone is offline and I plug it in, it immediately lights up and boots directly into TWRP. I don't know why this is, but I'd like to fix it since it's hit and miss trying to boot into the ROM normally.
Can anyone help me pin point the problem? In all my years with Android I've never seen an issue with boot priority such as this.
Things I have done:
-I tried to decide on a recovery so I flashed PhilZ, CWM, and TWRP in that order from the fastboot commandline
-wiped system, data, cache, dalvik cache, and flashed Euphoria ROM
Thanks!
One thing I would suggest is to flash the stock recovery and try rebooting, even i had encountered this problem. Later you can flash twrp again and everything will work fine.
Are you getting any errors while wiping partitions
sjandroiddeveloper said:
Are you getting any errors while wiping partitions
Click to expand...
Click to collapse
I'm having the same problem here. Wiping works alright, no errors at all. Although the built-in TWRP file manager is unable to see any files in the system folder.
First of all: I made a thread about bricking my Moto G earlier, but since this is a new issue (and a new Android version) I thought it would be better to make a new thread
So as some of you might have noticed yesterday there was the first release of CM13 for the Moto G and if you had nightlies enabled (like me) you'd just get it as a normal update, except for having to install the new Gapps of course. The problem is I didn't notice that it was CM13 until it was too late... First thing that happened was of course that my Google Play Services we're not working anymore. I tired flashing Gapps for 5.1 but it said that I used the Gapps for the wrong Android version. So I looked in the settings and noticed that I had Android 6.0 . Now I tried flashing OpenGapps for Android 6.0, which worked, but as soon as I booted Android it told me something like "Setup Assistant stopped working" over and over again, so I tried reverting to my latest CM12.1 backup I had, which was a bad idea... My phone was stuck in a bootloop and everytime I tried wiping my phone (except for internal storage) it rebooted when wiping data. Reflashing TWRP didn't help, so I tried flashing stock Android with mfastboot and it got to the point where it was optimizing apps but after that it just did the same thing again (classic boot loop).
Here's my question: How can I get TWRP working again and install CM13 (again if possible without wiping my internal storage or at least being able to back some files up) ?
Can u access TWRP?
Andus1988 said:
Can u access TWRP?
Click to expand...
Click to collapse
Yes I can, flashing and wiping works, except when trying to wipe data
Then don't wipe data?! Wiping data isn't necessary every time!
Andus1988 said:
Then don't wipe data?! Wiping data isn't necessary every time!
Click to expand...
Click to collapse
I know but if I only wipe dalvik, cache and system it didn't work.
Now I tried booting into TWRP and it shows the "no command" screen :'(
I'll write u a PM
I have the same problem would be nice if someone have a solution.
Guys i have a similar problem here, i got the latest update downloaded (cm-13.0-20151207-NIGHTLY-peregrine.zip) and when i clicked on update, the phone went black and nothing work now, i cannot get into fastboot or anything else, it only show "qhsusb_bulk" when I plugged in to the computer, any help??? i would really appreciate it .
I had CM13 on my Oneplus 3, and saw that there was an update. Turns out it was for CM14 and it wiped out my recovery(after further googling, I found out that it's a known issue - http://forum.xda-developers.com/oneplus-3/help/boot-recovery-cm14-1-nightly-official-t3497425). So I flashed the custom TWRP recovery from that.
Then I proceeded to flash my last working update of CM13, and the ARM64 6.0 Nano GApps immediately after. I then wiped my dalvic cache and rebooted. It started booting up and the preparing apps screen started loading. But when it finished and I was at the phone setup screen(the screen you get when you first buy a phone and have to choose language, wifi etc), it shows me an error named - "unfortunately the process android.process.media has stopped one plus 3 boot"
I looked the error up online and all results are to go into settings and modify google sync settings, or delete gallery cache etc. But I never even get to reach that point to try it. I flashed CM14 and ARM64 7.1 Nano Gapps to see if maybe that would work, but got the same error. Then I downloaded the last snapshot from CM site with their recovery, but same error.
Can anyone please help me?
SOLVED: I wiped everything except Internal Storage from afvanced wipe of TWRP and reflashed CM13 along with Gapps. Now the phone booted up fine and I'll restore my apps using titanium backup.
Hello,
Glad you found your way.
Thread closed.
Regards
Vatsal,
Forum Moderator.
About two weeks ago just before CyanogenMod's announcement of its closure I updated my Moto G2015 (1GB) to the latest nightly, which was CM14.1 released on the 25th of December, with its corresponding GAPPS version also released on the 25th of December (ARM, android 7.1, Full)
Yesterday the 7th of January my Google Apps decided that they didn't want to open, at first I thought it was just updating and since my battery was low I plugged in my device, I later realised that my device randomly went to a boot loop and stayed there. I grew impatient so I restarted the phone and went to the Recovery Mode (To Re-Flash the ROM), but to my annoyance the recovery (TWRP) just stayed on the 'Teamwin' logo forever, it would randomly go black then return to that logo. infuriated I turned on my phone and went to backup/reset and clicked 'factory reset'. it annoyingly booted me into recovery to reset the device, which of course I couldn't do.
Now the simple answer would have been for me to go and wipe the cache and data from 'google play services' and or 'launcher3' but I did, either it always shows 'calculating' preventing me from clicking 'manage space' or clearing 'cache' or when it did finally show, after I did click the button for the cache and or data to be cleared it would say 'calculating', and a quick check would discover that nothing was actually cleared.
Kind Regards, and Thank You to any help recieved,
NotSoGreat
Boot TWRP or CWM Recovery (not sure if it's still called CWM Recovery now that LineageOS has replaced it) with the command 'fastboot boot recovery.img' but replace recovery.img with your actual recovery image filename. If TWRP won't boot wait, sometimes a theme or corruption in the TWRP directory on internal storage can pause the startup of TWRP by several minutes, if that still fails boot CWMR and remove the TWRP directory or wipe internal storage.
Once you can get TWRP to boot properly, backup everything (MPT works in TWRP) and wipe and reflash, should be good to go.
acejavelin said:
Boot TWRP or CWM Recovery (not sure if it's still called CWM Recovery now that LineageOS has replaced it) with the command 'fastboot boot recovery.img' but replace recovery.img with your actual recovery image filename. If TWRP won't boot wait, sometimes a theme or corruption in the TWRP directory on internal storage can pause the startup of TWRP by several minutes, if that still fails boot CWMR and remove the TWRP directory or wipe internal storage.
Once you can get TWRP to boot properly, backup everything (MPT works in TWRP) and wipe and reflash, should be good to go.
Click to expand...
Click to collapse
Thanks for the reply, what you're saying makes sense and would probably work, but I found a simpler work around. I'm actually annoyed I didn't do it earlier.
So simply put, I downloaded my stock recovery which worked and then I just factory reset my device from there, that reset the CM14.1 ROM and let my Google Apps work again. Now about the recovery, I'm a bit skeptical about Re Flashing it, but I think I'll try it next weekend and post the results.
NotSoGreat said:
Thanks for the reply, what you're saying makes sense and would probably work, but I found a simpler work around. I'm actually annoyed I didn't do it earlier.
So simply put, I downloaded my stock recovery which worked and then I just factory reset my device from there, that reset the CM14.1 ROM and let my Google Apps work again. Now about the recovery, I'm a bit skeptical about Re Flashing it, but I think I'll try it next weekend and post the results.
Click to expand...
Click to collapse
Have you tried it since you wiped? It might just work now that the reset wiped internal storage...
acejavelin said:
Have you tried it since you wiped? It might just work now that the reset wiped internal storage...
Click to expand...
Click to collapse
I'll try now.
acejavelin said:
Have you tried it since you wiped? It might just work now that the reset wiped internal storage...
Click to expand...
Click to collapse
Right, so I reinstalled and flashed the latest version TWRP, when I opened into it, it took about 1 minute before it opened up, it ran a quick operation that I just glimpsed, it looked like it was wiping cache and user data, my phone was rebooted and I was right, my phone had been reset for the second time today (I'm almost a pro at reinstalling all my apps). I rebooted into the recovery and Look and Behold, it was working.
Thanks slot for your help and time.