Phone crashed: System UID inconsistent error - Galaxy S II Q&A, Help & Troubleshooting

I get "UIDs on the system are inconsistent, you need to wipe your data partition or your device will be unstable" error message consistently even after reboots. Running rooted, with stock ROM. I get multiple FC's which I have to acknowledge before using the phone. Not sure what's happening with my phone. Please help.

what was the last thing you installed before the problem started, it may have damaged the software that is on the phone.
Only thing you might try is doing a factory reset and see if that clears the problem.

sabesh said:
I get "UIDs on the system are inconsistent, you need to wipe your data partition or your device will be unstable" error message consistently even after reboots. Running rooted, with stock ROM. I get multiple FC's which I have to acknowledge before using the phone. Not sure what's happening with my phone. Please help.
Click to expand...
Click to collapse
I would flash another rom tbh ...
This will solve all your problems ..
Don't know why you would want to run stock anyway

Solved: I booted into recovery, then did a data wipe to fix. I then used Titanium Backup to restore everything. All good now. Thx guys!

Probably the cleanest solution HERE

Related

[Q] Alpha-X ROM ICS --- Keeps rebooting! HELP!

PLEASE HELP!!
I installed the Alpha-X ICS ROM for Evo 3D. The problem that I'm facing is that it keeps re-booting to "No Service" state.
I've already tried toggling the "Airplane" mode method - the moment I turn Airplane mode off, the status bar shows that I'm connected to Sprint but within a second starts rebooting (showing the ICS start up screen animation) and goes in a loop for 5-6 times and then ends up back with "No Service" state.
Please help as I really like this ROM. I am a newbie here, hence XDA doesn't allow me to post directly to the Alpha-X thread.
[email protected] said:
PLEASE HELP!!
I installed the Alpha-X ICS ROM for Evo 3D. The problem that I'm facing is that it keeps re-booting to "No Service" state.
I've already tried toggling the "Airplane" mode method - the moment I turn Airplane mode off, the status bar shows that I'm connected to Sprint but within a second starts rebooting (showing the ICS start up screen animation) and goes in a loop for 5-6 times and then ends up back with "No Service" state.
Please help as I really like this ROM. I am a newbie here, hence XDA doesn't allow me to post directly to the Alpha-X thread.
Click to expand...
Click to collapse
Hello,
How did you flash this ROM? Are you on HBoot 1.5?
If so, you will need to re-flash this ROM using Fastboot (PM Me if you cant find the instructions)
Yes, I'm on HBoot 1.5 and flashed it using Flash GUI.
I was earlier using ClearROM.
Update: I guess, i realized the problem - during the first time I had flashed this ROM, I had cleared all data & cache 9basically factory reset). It had worked fine.
Once in, I used Titanium backup to restore all my app data (including system data)... I guess that system data is causing this issue. I re-did the entire process (factory reset & flash) and now it's working fine.
I'll go ahead and try restoring only user app this time and update back.
This just proves my "Noob"ness, I guess
[email protected] said:
Update: I guess, i realized the problem - during the first time I had flashed this ROM, I had cleared all data & cache 9basically factory reset). It had worked fine.
Once in, I used Titanium backup to restore all my app data (including system data)... I guess that system data is causing this issue. I re-did the entire process (factory reset & flash) and now it's working fine.
I'll go ahead and try restoring only user app this time and update back.
This just proves my "Noob"ness, I guess
Click to expand...
Click to collapse
I just wrote a post about this lol. Yes, it is only the system spp/data that will cause the issues. You shouldn't have problems restoring all of your user apps and data. I am running ALPHA X with all of my apps and data restored through TB with zero problems.
Bamba1260 said:
I just wrote a post about this lol. Yes, it is only the system spp/data that will cause the issues. You shouldn't have problems restoring all of your user apps and data. I am running ALPHA X with all of my apps and data restored through TB with zero problems.
Click to expand...
Click to collapse
im going to try this to solve my problems i have been having with my phone... you will be getting lots of thanks if it works lol
[email protected] said:
Update: I guess, i realized the problem - during the first time I had flashed this ROM, I had cleared all data & cache 9basically factory reset). It had worked fine.
Once in, I used Titanium backup to restore all my app data (including system data)... I guess that system data is causing this issue. I re-did the entire process (factory reset & flash) and now it's working fine.
I'll go ahead and try restoring only user app this time and update back.
This just proves my "Noob"ness, I guess
Click to expand...
Click to collapse
LOL....restoring system data can cause all sorts of hell for you as Bamba1260's already pointed out and you've already figured out the hard way, and there's nothing wrong with being a "noob" either, but keep in mind if you're looking for a stable and fully functioning phone or prone to freaking out when something goes wrong.....this is after all an ALPHA (experimental / for testing and bug reporting purposes only) rom. Indeed it is a very good alpha state rom, but things are likely to and should be expected to go wrong with it periodically.
hockeyfamily737 said:
LOL....restoring system data can cause all sorts of hell for you as Bamba1260's already pointed out and you've already figured out the hard way, and there's nothing wrong with being a "noob" either, but keep in mind if you're looking for a stable and fully functioning phone or prone to freaking out when something goes wrong.....this is after all an ALPHA (experimental / for testing and bug reporting purposes only) rom. Indeed it is a very good alpha state rom, but things are likely to and should be expected to go wrong with it periodically.
Click to expand...
Click to collapse
Yeah.. that's one more thing I did realize.. but was so enamored by the ICS ROM that I wanted to "taste" it one way or other..
Anyway, since I'm not done with my first 10 posts, I will have to post this bug(?) here for everybody's FYI that the GPS doesn't seem to work with this ROM.
So, know before you jump...
P.S. I still love this ROM - one of the smoothest that I've tried.

Downgrade from LFB, flashed back: Very weird ISSUES!!

I was disappointed with the LFB performance etc so today I tried flashing back to LF2.
Process I followed was this:
1) Directly from LFB, I fashed LF2 tar with Odin without wipe
Problem faced: "android.process.acore has stopped unexpectedly" and "contacts has stopped". Phone remained in a hung state with these messages popping up continuously and totally unusable.
2) Went back to CWM, wiped cache and dalvik cache, rebooted
Problem faced: Still same as above
3) Flashed back to LFB to make phone usable, took full Titanium backup. Then went back to CWM, wiped data (factory reset). Flashed LF2 again with Odin. Worked fine for a bit, then restored Titanium backup to get my apps and settings. Rebooted.
Problem faced: Still same as above.
4) Restored nandroid backup I had of LFB.
Problem faced: None, all working but I am still on LFB and back where I started.
Is there a way to go back to LF2 and keep my apps and data?
Any help will be appreciated and thanked.
Did you restore System apps? You can only use Titanium for non-system apps, since it will otherwise cause these issues.
d4fseeker said:
Did you restore System apps? You can only use Titanium for non-system apps, since it will otherwise cause these issues.
Click to expand...
Click to collapse
Restored only user apps + data.
Could you try installing the apps one at a time until you find the issue?
Titanium shows 294 items.
I don't think I have the patience to install them one by one.
There's another MAJOR problem I'm facing now after doing the nandroid restore.
When I'm on a call, THE OTHER PERSON CAN'T HEAR ME!!
I'll try flashing the ROM again through Odin and see if that solves this issue. If it doesn't, I have no clue how to proceed from there.
Sent from my GT-I9300 using Tapatalk 2
You probably have LFB modem with known problem .
Solutions mess for hours or wipe phone flash clean rom .
jje
Did you have Samsung or Google, or third party app restore settings?
The fact that LFB introduced new settings that it attempts to restore on an rom without these options may cause issues.
OK, this is getting weirder.
I wiped phone clean, then flashed LFB because of above problem. Restored user apps+data with Titanium.
Phone was working fine, until someone called just now. The screen went black and I could hear the ringtone but name wasn't shown. After sometime I got a pop-up message "com.android.phone stopped working". And I couldn't see who called as it wasn't logged either.
Now it gets weirder.
I tried to replicate this issue by calling from my landline and another mobile but it worked perfectly for the 5-10 times I tried. Then I tried another different mobile and the problem occurs again!!! And this is when I have flashed LFB after clean wipe (in CWM) and not restored system apps.......!
Please HELP!! I am getting desperate now!
Lennyuk said:
Did you have Samsung or Google, or third party app restore settings?
The fact that LFB introduced new settings that it attempts to restore on an rom without these options may cause issues.
Click to expand...
Click to collapse
Could this explain the above problem?? Where do I disable it? I haven't enabled anything that's not on by default.
JJEgan said:
You probably have LFB modem with known problem .
Solutions mess for hours or wipe phone flash clean rom .
jje
Click to expand...
Click to collapse
I did a clean wipe and I'm getting a different issue! Pls help!
g4rvd4 said:
OK, this is getting weirder.
I wiped phone clean, then flashed LFB because of above problem. Restored user apps+data with Titanium.
Phone was working fine, until someone called just now. The screen went black and I could hear the ringtone but name wasn't shown. After sometime I got a pop-up message "com.android.phone stopped working". And I couldn't see who called as it wasn't logged either.
Now it gets weirder.
I tried to replicate this issue by calling from my landline and another mobile but it worked perfectly for the 5-10 times I tried. Then I tried another different mobile and the problem occurs again!!! And this is when I have flashed LFB after clean wipe (in CWM) and not restored system apps.......!
Please HELP!! I am getting desperate now!
Try and flash lfb again could just be a bad flash something like this happened to me today
if i helped say thanks
Click to expand...
Click to collapse
g4rvd4 said:
I was disappointed with the LFB performance etc so today I tried flashing back to LF2.
Process I followed was this:
1) Directly from LFB, I fashed LF2 tar with Odin without wipe
Problem faced: "android.process.acore has stopped unexpectedly" and "contacts has stopped". Phone remained in a hung state with these messages popping up continuously and totally unusable.
2) Went back to CWM, wiped cache and dalvik cache, rebooted
Problem faced: Still same as above
3) Flashed back to LFB to make phone usable, took full Titanium backup. Then went back to CWM, wiped data (factory reset). Flashed LF2 again with Odin. Worked fine for a bit, then restored Titanium backup to get my apps and settings. Rebooted.
Problem faced: Still same as above.
4) Restored nandroid backup I had of LFB.
Problem faced: None, all working but I am still on LFB and back where I started.
Is there a way to go back to LF2 and keep my apps and data?
Any help will be appreciated and thanked.
Click to expand...
Click to collapse
Your answer is in number one "contacts has stopped". Don't restore your [CONTACTS/CALLS] in Titanium backup. I have had this same problem before. I hope that helped.

[Q] help with reboot problem

Need help with a problem. I am not a noob, been flashing and rooting since the vogue and dzo, if you don't know what that means, well... am also not a Dev. I do use adb, etc.
See hboot and hardware ver in my Sig. Running either wftn 4.08 or 4.17 with this happening, but I do not think it is a ROM problem. Phone reboots after being on for a while after freezing for 10 seconds. It is a hard reboot, back to splash screen. It will boot into ROM, and at this point I can use it for no more than 10 seconds, before it repeats the process. It does not go to the setup screen. I tried wiping and restoring just data from a working backup, does the exact same thing. I also tried flashing ROM over it to see if writing the system would fix, exact same problem. yes, I did also try the reboot fix. Wiped everything, restored full working nandroid, ran for an hour and same thing happened. This was a nandroid that had previously run for >1wk with no issues. Also noted that some apps are missing from the restore. Tried reinstalling apps from TB, it hangs. Apps from market gives error 24 and won't install. Some App data is lost between reboots. Looked at my logs and see errors related to mtd partition - I've attached the log. I ran my SD card through windows disk check and error fix, it found zero errors and said it was fine.
I'm going to ruu restore, but based on the above I am uncertain whether this will fix the problem. Looking for other suggestions from people with more experience than me. Thanks in advance.
bump. where's ramjet when you need him? lol
I'm not Ramjet, but I like to think of myself as the poor man's Ramjet
Like you said, I would suggest the RUU and run stock for a little while to see if the problem is fixed. If not, it could be a hardware or heat issue.

Unfortunately, settings has stopped; even after clear data.

I know there are many forums addressing this problem but mines is a bit different, I know the common solution is App Info > Clear Data but this doesn't help. Neither does a force stop, reset or a clearing of settings cache.
I resolved to needing to do a data wipe, however I received this message, "failed to stat /data/date/com.android.defcontainer/cache" and nothing wiped. I started the phone to the exact same home screen and apps, but I had lost wifi settings and such, and can't open settings to set up wifi yet again.
I contemplated reflashing CM through the installer but wasn't sure if the failed to stat problem would interfere and potentially brick.
Any help would be much appreciated, cheers.
Flash the latest stock firmware for your country with Odin, factory reset in recovery before first boot.
boomboomer said:
Flash the latest stock firmware for your country with Odin, factory reset in recovery before first boot.
Click to expand...
Click to collapse
I read online that downgrading from 4.4 (CM) to Stock 4.3 would hard brick the device, is there any merit to this?
No, if you use the right firmware and do it properly there is no more risk than with a normal flash.
Problems with all roms SM-T210
Hi!
This problem is driving me crazy!
I have a similar problem!
I have Samsung Galaxy Tab SM-T210
For a long time I used RocketTab rom. I decided to try out new Android 4.4.2 Rom.
I started to get an error "Unfortunately settings has stopped" when I tried to open settings. I also got another application errors.
Now, it does not matter what rom I install, i get application has stopped error.
Even the RocketTab rom.
I flashed original stock rom via Odin, same problem.
I tried CWM and TWRP recovery.
I wiped dalvik cache, system, cache, Data, internal storage.
After flashing a new rom via odin or recovery, same problem.
I don't understand how it's possible that after deleting everything, I still get the same error.
Sometimes when I open settings, instead of getting an error, tablet restarts.
Tablet was 100% working before flashing Android 4.2.2
Any ideas?
Thanks guys
Why are you asking in the i9300 forum?
boomboomer said:
Why are you asking in the i9300 forum?
Click to expand...
Click to collapse
Because the problem seems to be very similar.
Point taken!

i9300 sleep of death issue

I'm helping a friend with her S3 i9300. It was running very sluggishly and starting in the last couple months she's been having a sleep of death issue.
It works fine (albeit slowly) while she's using it but when it sleeps for more than 10 minutes it doesn't turn back on without a lot of trouble or a holding down the power button and hard resetting. Every once in a while it only boots if I go indirectly through download mode.
I've confirmed with the play store app that she does NOT have the "insane chip" involved in the SDS issue. I've also factory resetted, rooted, tried flashing a custom kernel, a custom TW ROM (S5 sensation) and now an AOSP ROM (resurrection remix) and the problem persists.
Looking at other users' suggestions I took it apart and cleaned/played with the power button, even replacing it with the one from my old t999. Still the same.
I'm at a loss at this point. Has anyone run into this issue and found a fix I'm missing? Thanks for the help.
Have you already tried to format system partition (sdcard 0) via recovery?
After that you MUST flash a ROM, cause there is no system installed.
So, try to do this and let me know.
Else you can try to do a MEGA/SUPER wipe.
TENN3R said:
Have you already tried to format system partition (sdcard 0) via recovery?
After that you MUST flash a ROM, cause there is no system installed.
So, try to do this and let me know.
Else you can try to do a MEGA/SUPER wipe.
Click to expand...
Click to collapse
Thanks for the reply. Before flashing any ROMs I've always made sure to do a factory reset and then individually wipe System, Data, Cache, and Davlik Cache even though I know I'm duplicating some of the wiping. Unfortunately that did not work in this case.
I'll give the MEGA/SUPER wipe a try and report back.
Thanks again.
Looks like MEGA wipe didn't do the trick either. The phone is on NA8; is there a newer baseband I can try? Not sure what else to try.
At this point I'm thinking it might just be a hardware issue.
Flash the latest stock firmware from sammobile then factory reset, remove sd card and sim then test with a different battery.
If still the same then it is a hardware fault, motherboard/cpu.

Categories

Resources