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
Related
Hi:
I am quite worried, because my Xoom is unable to boot normally. I have EOS Nightly 99 installed, and after many weeks of perfect bahaviour, it was giving some messages like "gapps has closed", so I restarted the tablet. To my surprise, I saw the Moto lgo, the Tam EOS animation, and the "wheel" that appears before booting completely... and that´s it. Stuck.
I tried wiping dalvik-cache and cache and restart. Same result.
I tried restoring a nandroid backup. And here's the strange thing, because it can't restore data. The error message reads:
Error removing /data/data/com.android.browser/databases/webview.db-wal!Error formatting /data!
I tried wiping userdata, same error message
I tried with another recovery, in case it mattered (cwm and rogue). Same error
EDIT (Update):
I tried accessing the Xoom through ADB, and try to delete manually the pesky file. I was succesful. When I tried another "wipe data" from the recovery, I got a similar error:
Error removing /data/data/com.android.browser/databases/autofill.db (another file)
When I tried to delete it, I got the following error message (through adb) [why did it work the first time and not now???]
rm: can't remove 'autofill.db': Read-only file system
Any help, please? I'm at a loss here...
I post some photos of the errors
iruiz2 said:
Hi:
I am quite worried, because my Xoom is unable to boot normally. I have EOS Nightly 99 installed, and after many weeks of perfect bahaviour, it was giving some messages like "gapps has closed", so I restarted the tablet. To my surprise, I saw the Moto lgo, the Tam EOS animation, and the "wheel" that appears before booting completely... and that´s it. Stuck.
I tried wiping dalvik-cache and cache and restart. Same result.
I tried restoring a nandroid backup. And here's the strange thing, because it can't restore data. The error message reads:
Error removing /data/data/com.android.browser/databases/webview.db-wal!Error formatting /data!
I tried wiping userdata, same error message
I tried with another recovery, in case it mattered (cwm and rogue). Same error
Any help, please? I'm at a loss here...
I post some photos of the errors
Click to expand...
Click to collapse
have you tried re-flashing the rom completely?
daley stephenson said:
have you tried re-flashing the rom completely?
Click to expand...
Click to collapse
Yes, I did try that as well. It flashes without problem (rom + gapps), but does not restart (same original problem). I flashed it after a cache and dalvik-cache wipe.
iruiz2 said:
Yes, I did try that as well. It flashes without problem (rom + gapps), but does not restart (same original problem). I flashed it after a cache and dalvik-cache wipe.
Click to expand...
Click to collapse
ok backup your recovery to your desktop just so it is safe
try this
wipe cache - wipe dalvik cache - wipe/reset factory data - flash rom only then reboot - if it bootloops again enter recovery and go to advanced settings and run fix permissions and reboot
daley stephenson said:
ok backup your recovery to your desktop just so it is safe
try this
wipe cache - wipe dalvik cache - wipe/reset factory data - flash rom only then reboot - if it bootloops again enter recovery and go to advanced settings and run fix permissions and reboot
Click to expand...
Click to collapse
Thanks for your reply.
The problem, in case I wasn't clear, is that I can not make a WIPE DATA (that's when I get the error). It doesn't help wiping cache and dalvik beforehand. So I am in the same bootloop situation. tried fixing permissions, but I continue in the same situation.
iruiz2 said:
Thanks for your reply.
The problem, in case I wasn't clear, is that I can not make a WIPE DATA (that's when I get the error). It doesn't help wiping cache and dalvik beforehand. So I am in the same bootloop situation. tried fixing permissions, but I continue in the same situation.
Click to expand...
Click to collapse
sorry i must of mis-read your op - all i can suggest then is returning to stock using adb guide here http://goo.gl/G09vP then flashing your rom again - just make sure you get the right image for your device
daley stephenson said:
sorry i must of mis-read your op - all i can suggest then is returning to stock using adb guide here http://goo.gl/G09vP then flashing your rom again - just make sure you get the right image for your device
Click to expand...
Click to collapse
I will try this, as a last resort. Now I am making a backup of my internal sd card, because this process will delete everything in it. In case somebody wonders how to do this (I didn't know it myself), I used adb. The exact command I used was:
adb pull /data/media .
It's taking ages to backup my internal sd files (at a rate of 7Gb/hour aprox).
Meanwhile, anybody knows what possibly is happening to my Xoom?
After wating several hours to back up my internal sd card, I have been able to wipe (format) /data from fastboot. In case somebody needs to do something similar:
Once in recovery, type in your computer:
adb reboot bootloader (wait for the xoom to reboot into fastboot)
fastboot erase userdata
I then rebooted into recovery, and restored a nandroid backup. This time, no problems.
Now I am in the (again) long process of copying the /data/media files back to my Xoom, but I was VERY relieved to see that it was booting normally after this...
glad you got it fixed dude
hello there, i have a serious problem:
i had my a510 with unlocked bootloader and had the CM11 rom installed...so far, so good: all of a sudden when reading a PDF, it shut down, rebooted, went into a bootloop showing the acer logo.
i had also CWM installed, tried EVERYTHING there to erease cache and stuff like that..nothing worked it started flashing a different rom...no success...
i´ve already installed TWPR 2.7.0.0....worked until the point where i wanted to install a new rom...installing works, saying "successful" but in the lower left corner it says:
E: error opening ' /data/tf '
E: error: I/O error
Click to expand...
Click to collapse
can anybody help me please?! this is driving me insane!!
EDIT1:
i tried formatting DATA....after 5 minutes still no luck....it keeps "formatting data". could this be the reason for everything?!
EDIT2:
adb shell
recovery --wipe_data
did the trick!!!! i went back to TWRP, wiped DATA, no errors in /data/tf this time...clean installed CM11...and now it works again
Try to flash back CWM, format every partition (via the advanced menu)
and then flash a ROM like CM11
Shreps said:
Try to flash back CWM, format every partition (via the advanced menu)
and then flash a ROM like CM11
Click to expand...
Click to collapse
i have tried that...it didn´t work....it was stuck formatting...same went with TWRP....
only moving to ADB and sending the --wipe data helped me.
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...
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.
Hello fellas,
I had few problems with my Moto G. I was on official Moto lolipop.
I've unlocked bootloader, flashed TWRP, flashed SlimRom from dev thread, but it was hard to boot (bootlooping after phone restart, I was forced to turn down, and then turn on the phone, and sometimes it was booting) and I wanted to flash other rom, without ,,hard boot" problem.
And there is how I bricked my phone.
When I tried to wipe data in TWRP (factory/cache wipe) my phone reboots suddenly. It didn't wipe anything. It just reboot my system. I tried many times - always ending with reboot.
So, I tried to flash AICP rom without wiping anything. I installed it, and I had ,,android.acore has stopped working" error. Phone was rebooting often.
I tried to wipe my data again, without succeed. It was rebooting, and I've seen all my apps I had installed before.
I though it was TWRP fault, so I flashed CM recovery. Same thing occured. Next, I flashed CWM recovery. Same situation (reboot after choosing wipe).
So, I deleted my userdata and cache from fastboot, and tried this to solve my problems :
http://forum.xda-developers.com/moto-g/general/how-to-to-stock-5-0-2-motorola-lollipop-t3077806
Unfortunetly, it didn't helped me. Now I have one big bootloop.
What to do? Help me, please.
Thank you for your time!
////EDIT
I think I know whats happening. I have deleted my partition accidentally... I have Internal storage 0MB free, and mount errors... Is there a way to fix that, or I am screwed?
radogost said:
Hello fellas,
I had few problems with my Moto G. I was on official Moto lolipop.
I've unlocked bootloader, flashed TWRP, flashed SlimRom from dev thread, but it was hard to boot (bootlooping after phone restart, I was forced to turn down, and then turn on the phone, and sometimes it was booting) and I wanted to flash other rom, without ,,hard boot" problem.
And there is how I bricked my phone.
When I tried to wipe data in TWRP (factory/cache wipe) my phone reboots suddenly. It didn't wipe anything. It just reboot my system. I tried many times - always ending with reboot.
So, I tried to flash AICP rom without wiping anything. I installed it, and I had ,,android.acore has stopped working" error. Phone was rebooting often.
I tried to wipe my data again, without succeed. It was rebooting, and I've seen all my apps I had installed before.
I though it was TWRP fault, so I flashed CM recovery. Same thing occured. Next, I flashed CWM recovery. Same situation (reboot after choosing wipe).
So, I deleted my userdata and cache from fastboot, and tried this to solve my problems :
http://forum.xda-developers.com/moto-g/general/how-to-to-stock-5-0-2-motorola-lollipop-t3077806
Unfortunetly, it didn't helped me. Now I have one big bootloop.
What to do? Help me, please.
Thank you for your time!
Click to expand...
Click to collapse
Easiest thing to do . Reflash stock via fastboot
I tried, my friend. Bootloop. Always bootloop.
I think I have deleted my partition accidentally... I have Internal storage 0MB free, and mount errors...
Thread closed per OPs request.
Regards,
XDA-Staff