I recently got this',message when I was flashing a new ROM. It said UIDs of the syste,m are inconsistent, you need to wipe your data part ion and then my email app starts force closing repearedly
t only started recently and it happens no matter what ROm I flash. AOKP CM9 or a restore from an older working ROM. How do I fix this?
Related
Hey guys,
I have a serious problem.
I used to have CM6 stable until I noticed some heavy download traffic of about 4mb on any startup/reboot and someone told me it might be caused by some kind of OTA update, and that I should use the current nightly.
After flashing the nightly my phone crashes every time I want to install an app from the market. The download works fine and when it comes to "installation" is reboots.
I tried everything
flashing the CM6 stable
flashing the google apps
wiping partition cache
wiping davlink ache
deleting market data
full wipe/factory reset
nothing works, so basicly what I have now is an oversized state of the art nokia 3210... Can someone please help?
Hey, I've been running the stock build on my rooted O2X for a while now and tried the CM7 nightly's after having a bad experience with CM7 RC1 a month-ish ago.
I backed up with CWM(via rom manager), and CM7 works fine.
But i don't like how it remaps the external storage and for some other reasons is does not work for me.
So i'm trying to go back and its not working.
It says its restored successfully but boot stays on the LG screen with the progress bar underneath. only a battery pull gets me out, which i have probably done 20 times now.
-It was initially unable to unmount /system, but after i fixed permissions that error was gone but it did not fix the problem.
- I went into advanced restore and did each one separately, they all claim to have worked successfully. but no dice
-I used back2ext3 hoping that was the root of the problem, but no luck there.
i wipe data, cache as well as dalvik every time, but still nothing.
What is up with this? is it possible that my image is corrupted or something? but why is it saying restored successfully?
CM7 nightly installs fine, so im using it in the interim, but its not optimal.
thanks for any ideas.
I bet you have an older version of CWM.
Make sure you're on at least v4 then try restoring.
Nope, im running 4.0.0.9, which is current
Hello , i have a problem that started happening after I installed KD1 modem, i'm running Slim ICS 3.2 mnics-143 kernel ... I try to send SMS and always says sending failed... I tried installing stock modems like JVU , JVT but still same error happens ... Anyone with some experience that can help?
tyvm...
Have you tried clearing the data from the sms app? (This may delete your messages, use sms backup and restore to back them up)
You should have made a nandroid backup before flashing the modem, do this next time so you have a easy way to revert...
If the above does not work then you may have to reflash the rom...
First try clear cache and dalvik and see if that works if you haven't already. And if that doesn't then do the following,
Make a nandroid and back it up on your computer (just to be extra safe).
Flash with no wipe but this has caused further problems for me before where i started getting multiple apps force closing. At a slim possibility it may cause a boot loop. If any of this happens, then just do a wipe and flash, wipe cache and dalvik before flashing. (You may have to flash the rom twice (Not very likely).
I'we tried that reverted back to GB and still i cant send sms... anyone with any hint on why or what? i can receive sms no problem but fail to send em..
ahh i now see message centre not set think that is the issue ...
I'm currently running the latest CM9 on it with moboot... It seems like every time it boots up it pops up with that error message and literally won't go away and you have to reboot the device.. the only way I've found to temporarily fix it is to just wipe cache.... but it always comes back.
Is there any way to prevent this from popping up? It happened when I was on Classicnerd BUTTA too.
Wipe the system and caches, then reflash
I had this problem as well a while back. Wiping caches and reflashing the ROM worked for me.
And you guys didn't have the problem again, after that?
Help manually moving contacts and choosing a JB ROM.
If a pro could help me out I would appreciate it very much. I have been trying to move from a dangerous ICS build to JB and I am having this same problem.
My N7000 previously had this on it:
android 4.03
radio 19220zclp6
kernal version 3.0.15-i9220zclp1-cl131270 (bad ics kernal)
build number midnote 2.0 iml74k.zclp1
So I used ODIN to flash it to a GB rom but I got the com.android.process error and my phone would lock up.
So then I found this link http://forum.xda-developers.com/showthread.php?t=1424997 and flashed this ROM "N7000UBLR3 N7000UVOLR1 - Download - Argentina" from the bottom of the page. I wiped only the the cache (not the phone reset) and flashed it again but I still get the process error and phone locking up. I don't even know if this ROM is a safe ROM!!
Am I even on a safe kernal now? kernal n7000ublr3-cl890184 build imm76d.ublr3
What I need help doing is the following.
1. Before doing a full wipe, I need to either manually save my contacts to my PC or back them up. (no apps work but my pc can browse my phone) If I knew where my contacts were located, maybe I can manually copy them to my pc? So any help saving data from a partially unusable phone would help.
2. Flash to a safe GB rom, so I can then do the full wipes safely and then flash to a stable JB rom. (I have no clue which roms to choose here and need help).
Thanks for any help..
Hi guys,
so I sent my mobile phone in to samsung because of some problems including random reboots. They fixed every problem so I thought I can go ahead and install a custom rom again. I installed jelly bam but had random reboots so I thought it is because the rom is broken somehow so I installed cyanogen mod.. But I have the same problem there, too.
I wiped dalvik cache and formatted system, cache and data before installing the rom... i read somewhere that it could be a virus so i checked with avg but no results... what else could be the problem of the random reboots