Database Users

[Q] Which ROM Do you suggest?

I'm looking to upgrade my phone to a custom ROM, but I'm not sure which one is the best for my needs. This is what I am looking for:
Fyro Update
Increased Phone Speed
Increased Battery Support
Adblock for browser and apps
Also, how do I flash my ROM? I have the drivers to connect my phone to my computer, and that's about as far as I got. Secondly, will I lose my apps and their data? I already have my contacts and SMS backed up.
Thanks guys
jt

As a shameless plug - I whole-heartedly recommend SyndicateROM. It'll fulfill three of your four features already (including ad blocking in apps and the browser), and when the OFFICIAL, FINAL (ACS prides itself on stability and feature-completeness) Froyo release is out, it will be updated right away!

That's actually the one I was looking at. Is there instructions on how to flash your ROM? Will I lose my apps and their data?

After rooting you'll need Clockwork Recovery mod(CWM). Look for a Dev who has created a root with a CWM install (http://forum.xda-developers.com/showthread.php?t=770388).
1. Follow steps to root and install CWM.
2. Download a ROM and put it on your SDcard (Start with ones that have been around for a while and have been tested quite a bit. Avoid Froyo ones till you feel comfortable with CWM and Odin {if you ever use it}).
3. Reboot into CWM, BACKUP everything (this is key for your data to come back), wipe x3 (including cache)
4. Install ROM from SDcard(reboot, may take a few minutes to load for the first time)
5. Reboot into CWM, and advance restore (DATA only). reboot
6. Enjoy with all your data.
Hope this helps

Epic Experience + Phoenix is the best battery life I've had on any ROM.
Performance feels like stock, which is to say, this phone is really fast just as is and I don't think its screaming for better performance out of the box. Its not like it feels sluggish like the Evo does.

All these devs do great work! You can't go wrong with any of these roms. This belongs in the General Discussions section!
Sent from my SPH-D700 using XDA App

Streamline8 said:
After rooting you'll need Clockwork Recovery mod(CWM). Look for a Dev who has created a root with a CWM install (http://forum.xda-developers.com/showthread.php?t=770388).
1. Follow steps to root and install CWM.
2. Download a ROM and put it on your SDcard (Start with ones that have been around for a while and have been tested quite a bit. Avoid Froyo ones till you feel comfortable with CWM and Odin {if you ever use it}).
3. Reboot into CWM, BACKUP everything (this is key for your data to come back), wipe x3 (including cache)
4. Install ROM from SDcard(reboot, may take a few minutes to load for the first time)
5. Reboot into CWM, and advance restore (DATA only). reboot
6. Enjoy with all your data.
Hope this helps
Click to expand...
Click to collapse
Hoping you can help me a little further;
1) Done successfully
2) Done
3) How do I boot into CWM? I installed Titanium back up, and ROM manager - not sure if that's needed or not
Thanks guys
PS, sorry for posting in the wrong section

tuttjs said:
Hoping you can help me a little further;
1) Done successfully
2) Done
3) How do I boot into CWM? I installed Titanium back up, and ROM manager - not sure if that's needed or not
Thanks guys
PS, sorry for posting in the wrong section
Click to expand...
Click to collapse
camera button, down volume and power on.

I suggest you try them all and figure out what you like or don't like. Also try out the ODIN program so when you accidentally bork your phone you will know how to fix it right away.

Got it. I assume this is backing up to my SD card. Do I not wipe my SD card?
Thanks, this should be the last question!

tuttjs said:
Got it. I assume this is backing up to my SD card. Do I not wipe my SD card?
Click to expand...
Click to collapse
The only way you will wipe your SD card is if you partition it for A2SD support. The factory reset wipes all your data and might be a good idea if you are going from one rom/kernel to another. CWM backs up to your SD card. I have about 6 backups and can restore several different roms if I want. If you try all the roms out and make backups of all them it will be easy to go back to what you want.
A program called ROM Manager will make it easy to rename your backups.

[GUIDE] Install CyanogenMod 7 on the SGS i9000 (and live to tell the tale)

OK, the CM7 ROM for the Samsung Galaxy S i9000 has now hit the CM7 Mainstream and has matured in leaps and bounds over the last few weeks. The installation method has therefore ALSO matured by leaps and bounds.
However, there has been a downside to all that advancement...namely that there are lots and lots of incorrect install procedures floating around out there and even more misunderstandings as to what/how/when/why you install CM7 on your SGS i9000.
Therefore, this is intended to be the definitive guide about how to install CyanogenMod 7 (or CyanogenMod 7.1 if you are a stickler for such things since that is the most recent stable version but for the purposes of this guide it is STILL CM7) on the i9000 right here, right NOW. As things change, the first post of this thread will be updated.
If you have any questions/comments about the CM7 install procedure, post them here.
If you have any questions/comments about CM7's features, capabilities, battery life or anything OTHER THAN installing it...look HERE or HERE.
Before we do anything....make sure of the following:
* Your phone is fully charged.
* You have confirmed you can get into download/recovery with the three button method.
* You have used Titanium Backup to backup your apps (yes, there may be some factory defaulting happening soon).
* You have taken a Nandroid backup via Clockwork Mod, just in case the early steps go south.
* You have used a third party program to back up your SMS messages (if so desired)
* You have made your peace with your loved ones and said all your goodbyes...maybe left a nice note or something.
Remember, this will be one of the most harrowing, horrific experiences of your life. Grown men have been known to gnaw off their own legs during this procedure, unable to face the deepening horror their feeble minds cannot hope to comprehend.
Are you SURE you want to install CM7?
Very, VERY SURE?
OK, its your funeral, I am just here for the open bar.
OK, here we go....
FIRST STEP!!!!! THE PRE-INSTALLATION TANGO!!!!
Boy are you lucky to be doing this now. Recently CM7 was improved so that it works just fine with either Froyo or Gingerbread Bootloaders. It used to be that when you installed CM7 with Gingerbread bootloaders, a puppy died in agony. Now, the cuddly little puppies are safe thanks to the hard work of the CM7 Devs.
However, if for some strange reason you have still have Eclair installed currently, smash your head repeatedly against a wall for being such a stinking Luddite. Once you wake up, update to Froyo or Gingerbread and then come back and start this again. Plenty of threads on XDA will help you do that. Go read one and flash froyo or gingerbread via ODIN, we'll wait right here with the car running.
Don't know how to use ODIN? Not sure about all those little checkboxes? Befuddled by those driver thingies? Unsure how to click on the links above while using a Commodore64? Well, we won't wait in the car THAT long. If this is the case then you absolutely shouldn't be flashing CM7 yet my poor lost child, educate yourself for awhile and then come back, or just buy a used iPhone.
OK, still with me? ONWARDS.
SECOND STEP!!!!! THE NITTY GRITTY DETAILS, AKA THE CALM BEFORE THE STORM!!!!!
Here is the point where you need to do all sorts of things that you may have already done.
If you have already done them, GOOD, you are very, very clever and ahead of the game. Give yourself a gold star.
If you don't know how to do any of these things, then you shouldn't be here yet. Go search for things you don't understand in the general and Q&A forums for the i9000 and when you feel you are better grounded in the arcane mysteries of flashing custom ROMS, come back and we will have a joyous reunion and try this again.
OK, so what do you do in STEP TWO?
* Doublecheck that you can indeed get into Download Mode using Vol Down+PWR+Home, and into Recovery with Vol Up+PWR+Home. If not, go away and search XDA for a way to fix that.
* Root your phone.
* Confirm you have Clockwork Mod recovery running. If not, use Odin to flash this Speedmod kernel if you are on Froyo. If you are on Gingerbread flash the TalonDev kernel using the v2.2 tar (yes I know the TalonDev kernel has lagfix automatically enabled, but as your file system will be grabbed and ripped out still beating and then replaced with a better one by the CM7 Installer, it really doesn't matter). There are two different versions of the v2.2 tar available but don't panic. Use TalonDEV-0.2.2R2-I9000-1200-JVP.tar first...if that doesn't work for you, try TalonDEV-0.2.2R2-I9000-JVP.tar. One of the two should work for you. (Thanks to chan1628 for testing them the hard way)
* Install ROM Manager (I STRONGLY suggest you buy the Premium version if possible to make flashing Nightlies easier. It is quite cheap with a lot of great features and is one of the core apps you will use on your phone from here on in...plus Koush deserves your support).
* Take another nandroid backup (even if you took one already) and confirm your Titanium Backup is up to date (and includes a backup of ROM Manager).
* Confirm that you are rooted.
* Backup your contacts to either Exchange, Gmail or your SIM card.
* Write down your correct APNs and your IMEI, just in case.
* Take a backup of your efs folder and save it somewhere.
* Post a note on your monitor reminding yourself to breathe.
* Say goodbye to your Samsung apps like Snap2Go and Daily Briefing, they won't work with CM7.
* Pour yourself a stiff drink
Confused? Not sure how to root your phone or worried about voiding your warranty? Really curious about what these APN things and where can you find them? Hoping to sync your phone with iTunes once CM7 is installed? Then go away, do some searching, get up to speed and I will see you later. I mean it...avaunt ye. Scram. Exeunt with all due alacrity. Happy reading.
Also, if you are getting errors concerning CWM, or cannot get into CWM3 Recovery, then search XDA (or the comments to this thread) for a solution. I cannot help you. I am not an expert on Clockwork Mod, I am just here to get CM7 running for you, or kill you and steal your girlfriend in the attempt. Clockwork Mod is YOUR lookout.
Still here? Did all that? CWM Recovery working properly? Crossed all your i's and dotted your t's? Forward then. Things get REALLY BAD from here on in. Whatever happens next, I am truly, truly sorry.
THIRD STEP!!!!!! THE COMPLEX, AGONIZING EXPERIENCE OF FLASHING THE ROM ITSELF!!!
Are you sure you are ready for this? Are you quite, QUITE sure?
It is not too late to turn back....and if you do no one will think less of you. I promise.
Positive you are where you want to be?
Brave, brave darling. Take my hand and lets do this then....there are two possible methods to use now that you are at the Third Step..Method the First uses the ROM Manager and is by far the simpler of the two. However if the ROM Manager doesn't work for you or if you have a sudden premonition of flaming disaster about it....don't cry. Man up and go to the manual method listed after Method the First, known quite coincidentally as Method the Second.
Method the First!
Open ROM Manager from your App Drawer.
Select Flash ClockworkMod Recovery.
When it asks you what phone you are using, scroll down until you find Galaxy S MTD and select it (Galaxy S is what CM7 calls the i9000 series...CM7 is weird that way).
When it asks what version to use, select CMW3.
By the way, if ROM Manager tries to argue with you during this process, or tells you your phone may not be supported, ignore it and click OK or Continue or whatever it takes. It just worries over what you may be about to do to yourself.
Confirm that under Flash ClockworkMod Recovery it now reads Current Recovery: ClockworkMod 3.x.x.x. This means that now you should be able to see CyanogenMod zips and nightlies (if you have ROM Manager Premium) in ROM Manager. Hoorah!
Now, the moment of truth arrives...select Download ROM.
Next close your little eyes tightly and select CyanogenMod or CyanogenMod Nightlies (if you see that one). Either one will do.
Down the road, you will use the CyanogenMod Nightlies files to update...assuming you survive the next 15 minutes. However when installing you can use the single file in the CyanogenMod folder (there for Free users) or the latest Nightly in the CyanogenMod Nightlies folder...same difference.
So click the file of your choice and stand back...well, not too far back because there is more stuff you have to do.
If/when you are asked if you wish to reinstall Google Apps, it is highly recommended that you do so, so check the little box. This saves many headaches and potential fc's down the line.
When you are asked what you wish to do to prepare for the new ROM, you can choose to do another Nandroid Backup, Clear Data and Cache (wiping the device) and/or Clear the Data Cache. No need for another Nandroid backup, but select the other two and hit OK.
Now let the ROM Manager make some magic. It will take a couple minutes but likely not nearly as long as you expect, so go out and make tea or paint the Sistine Chapel or something.
While you are gone your device will do all the wiping and installing, back up your efs folder and apply the new file system you will need. You will NOT need to apply any lagfix or mess about with tweaks or whatnot....CM7 does it all for you and no other options are possible....so don't ask.
Method the Second!
If for whatever reason you are having trouble working with ROM Manager in the previous method and are therefore stuck, you can do the following to flash CM7 manually.....but if you have a weak heart or tend to get squeamish...I implore you to look away.
Download this most recent version of CM7 from http://download.cyanogenmod.com/?type=nightly&device=galaxysmtd
Then download the most recent set of Google Apps from http://goo-inside.me/gapps
Place both on your SD card.
Go into Recovery using the handy-dandy Three Button Skidoo (NOT by using the command "Reboot to Recovery" found in ROM Manager...you have been warned).
Do a Factory Reset (wiping data so if you forgot to backup your apps before....whoops)
Wipe the Dalvik and Cache (just in case).
Select Install Zip from SD Card and flash first the CM7 zip, and then the gapps zip. No need to reboot in between. Finally fix permissions.
NOTE: If you are one of those people who have done some research and have also downloaded one of the CM7 custom kernels which you wish to flash as part of your install (if you haven't don't worry about it, I don't recommend using a custom kernel before you have spent some time with the stock kernel, but some people think they are 1337)...make certain you flash the Nightly BEFORE the custom kernel, otherwise you will totally confuse the installer and very bad things will happen which will require you to flash back to a Samsung ROM using ODIN and start all over again.
Once everything has completed, THEN reboot into CM7 (HOO-RAH) and continue to the Fourth Step. Hurry, hurry, scroll back up....
GO!!!
Oh, WAIT A MINUTE....When you have done all the stuff in the Fourth Step, do this too...go to ROM Manager, and select Flash ClockworkMod Recovery. ID your phone as Galaxy S MTD when it asks and select CWM3...it will tell you that your phone is not supported or some such but have it install it anyway. What the heck does it know. Doing so will ensure you can find your the Nightly updates using ROM Manager Premium in the future.
OK, now go on to the Fourth Step...really this time...
GO! GO!
FOURTH STEP!!!!! STEP OUT INTO THE LIGHT AND BREATHE THE FREE AIR
That's it, you are done. Throw back that drink now...or if you don't want it, I'll take it.
Your phone will show the CM7 SGS splash screen for a bit, then the CM7 boot animation for a while longer (spin, spin, spin)...and then you will be in CyanogenMod 7.
If you find that the boot animation never seems to end, or keeps restarting...DON'T PANIC. This happens to some people when flashing CM7 for the first time. Just go to recovery and flash the Nightly again, you should be fine. If you used ROM Manager the first time, the nightly will be in the ROM Manager folder on your SD card.
Where is all the pain, the agony, the brain bending complexity reducing scholars to madness that I warned you about?
OK, I lied...but I had to make sure you were serious.
Now restore your apps (remember that is best to do fresh from the Market, but if you use TB then be sure to reinstall just the APP, not APP + DATA, and NO SYSTEM APPS) and put all your contacts and email addresses back and so on.
Also, remember that your external SD card is now located in the /emmc directory. Why? Because that is how it is in CM7, so cope. It really is NOT that tough to get used to. However, if you want to have some kicks, go into the CM7 Dev thread and ask where your external_sd card has gone a few times to watch people go berzerk yelling at you. Fun, fun, fun.
From here on in, you can install nightly updates to stay on the bleeding edge of CyanogenMod, as well as to allow yourself to experience the terror of waiting for that boot animation to stop again and again and again. You can look at the Nightly Wiki for instructions on different flashing strategies.
You may also install custom kernels and alternate modems via Recovery if you wish, but be sure that they are CM7 compatible. The ones you used back on Samsung ROMs won't work for you any more.
Carry on, and enjoy your new ROM.
As always, if this procedure bricked anything or gave your dog syphilis, it isn't my fault. By God, I WARNED you. If you liked it, or it worked out well for you, feel free to click Thanks and heap praise in the comments.
Finally, all due honour and thanks to the incredible Devs and Maintainers of TeamHacksung and the SGSTEAM listed below. Find their profiles and donate to them, they have earned it.
* codeworkx - http://twitter.com/codeworkx
* atinm - http://twitter.com/atinm
* coolya - http://twitter.com/coolya

Great guide, just want to make a quick addition...
rschenck said:
OK, so what do you do in STEP TWO?
* Root your phone.
* Confirm you have Clockwork Mod recovery running. If not, flash the Speedmod kernel.
Click to expand...
Click to collapse
I couldn't complete this step during my exciting first install of CM7
If anyone has trouble getting Clockworkmod Recovery running, and you can't manage to flash a new kernel using Odin/heimdall please read:
[RECOVERY] 3e Recovery Modded w/ No Verification

I just skimmed through it but wouldn't this require you to buy rom manager premium?

runedrune said:
I just skimmed through it but wouldn't this require you to buy rom manager premium?
Click to expand...
Click to collapse
No. The premium version is only required to download nightlies directly through the app. Download them manually, then point rom manager at the zip on your sdcard & install.

Yay! First thanker! Nice guide too.

runedrune said:
I just skimmed through it but wouldn't this require you to buy rom manager premium?
Click to expand...
Click to collapse
Not the install, that is free as far as I know. Installing nightlies via ROM Manager needs Premium. Plus I suggested people buy Premium anyway.

sambwel said:
No. The premium version is only required to download nightlies directly through the app. Download them manually, then point rom manager at the zip on your sdcard & install.
Click to expand...
Click to collapse
Exactly. The instructions tell you to use rom manager to download CM7. Just thinking that http://download.cyanogenmod.com/?device=galaxysmtd should be included too for those that can't buy rom manager.
But anyway great guide rschenck. Hopefully it'll save us from unnecessary questions.

runedrune said:
I just skimmed through it but wouldn't this require you to buy rom manager premium?
Click to expand...
Click to collapse
Yepp true story!
IF you want to download roms and stuff from Rom manager you do have to have premium.

I have no plans to install yet (still waiting for the stable release) but really this guide has no boring part. Very informative and easy to follow. Just wanna say thanks for this guide. KUDOS!

Nice tutorial man. I want to instal cm7 and this tutorial is very helpfull. Hope this topic get sticky :d

upgrading to latest
just to clarify, I'm (thanks to you!) on v11 due to some people suggesting me that version over v14. After reading some I would like to flash the new experimental build (v15?) in order to do so I:
1) charge it up
2) do a nandroid backup /done
3) wipe data/factory reset + wipe cache in CMW /not sure about this, I've read some diferent post about what to wipe. Some said that when upgrading only cache + dalvik will do just fine. This is the main issue.
4) flash the v15 (update-cm-7-05282011-NIGHTLY-GalaxyS-signed.zip) through CMW
+ all that other stuff like preparing myself for long agonizing experience and stuff
thanks in advance!

James.q said:
just to clarify, I'm (thanks to you!) on v11 due to some people suggesting me that version over v14. After reading some I would like to flash the new experimental build (v15?) in order to do so I:
1) charge it up
2) do a nandroid backup /done
3) wipe data/factory reset + wipe cache in CMW /not sure about this, I've read some diferent post about what to wipe. Some said that when upgrading only cache + dalvik will do just fine. This is the main issue.
4) flash the v15 (update-cm-7-05282011-NIGHTLY-GalaxyS-signed.zip) through CMW
+ all that other stuff like preparing myself for long agonizing experience and stuff
thanks in advance!
Click to expand...
Click to collapse
You are quite correct...when upgrading all you need to do is wipe dalvik cache. You can also take a nandroid backup if you wish to be extra careful but there is no need to wipe data for an upgrade.
Sent from my GT-I9000 using XDA Premium App

rschenck said:
You are quite correct...when upgrading all you need to do is wipe dalvik cache. You can also take a nandroid backup if you wish to be extra careful but there is no need to wipe data for an upgrade.
Sent from my GT-I9000 using XDA Premium App
Click to expand...
Click to collapse
thanks! .. so is it just wipe cache or both wipe cache + wipe dalvik cache in advanced menu? I get confused with that

James.q said:
thanks! .. so is it just wipe cache or both wipe cache + wipe dalvik cache in advanced menu? I get confused with that
Click to expand...
Click to collapse
Wipe cache is in the main cwm menu, wipe dalvik is in advanced...and you can wipe them both.
Sent from my GT-I9000 using XDA Premium App

Thanks mate, you made my day! I haven't laughed so hard in a while ...

James.q said:
thanks! .. so is it just wipe cache or both wipe cache + wipe dalvik cache in advanced menu? I get confused with that
Click to expand...
Click to collapse
Yes, you should do both

A few small edits and clarifications added...

Good job on this guide.
You kids gave it easy. Back in my day, we had to flash our phones in Morse code.
Sent via XDA Premium app on my GT-I9000 running CM7 (GB 2.3.4)

bump...and if anyone who has used this guide has feedback or suggestions, please comment with them.

How come when i go to download rom i cannot see cyanogen mod there?
I did buy the rom manager

[Q] How to get rid of "System UIDs Inconsistent"?

I was on 4.2.1, rooted, and with TWRP as recovery.
I wanted to get the OTA to 4.2.2 so I did full Titanium backup and then used the WugFresh toolkit to flash stock 4.2.1.
After flashing, I was offered the OTA which I allowed to install.
When finished, I got root back with Rootkeeper and restored all Apps and Data (not System data) with Titanium.
Everything was working, but on every reboot I got the message :
"System UIDs Inconsistent. UIDs on the system are inconsistent, you need to wipe your data partition or your device will be unstable."
I also found that My Phone Explorer would no longer connect via USB so I decided to go back to 4.2.1.
I again flashed it with the toolkit and did another restore with Titanium. Again, everything seems to be working, but I still get this message on every boot.
I thought using Titanium Backup was a standard way of restoring apps and data.
How do I get rid of this message without wiping and reinstalling all my Apps individually, which means losing all my game scores, etc?

I also see that in Bootloader there is a line
"Signing - not defined yet".
I do not know if that was there before flashing back to stock.

same problem
system UIDs inconsistent, it keeps showing up after every boot.
i have nexus 7 GSM 32 gb rooted using nexus 7 toolkit with clockworkmod recovery, android version 4.2.1 build number JOP40D
i tried Rom manager fix permission the same problem, i don't like resetting it any suggestion
thank you

windwhisper said:
system UIDs inconsistent, it keeps showing up after every boot.
i have nexus 7 GSM 32 gb rooted using nexus 7 toolkit with clockworkmod recovery, android version 4.2.1 build number JOP40D
i tried Rom manager fix permission the same problem, i don't like resetting it any suggestion
thank you
Click to expand...
Click to collapse
I found the answer in another thread. I used TWRP (Advanced - Fix Permissions). It was instantly fixed.
I took a full backup before trying this, but didn't need it.

devra1 said:
I found the answer in another thread. I used TWRP (Advanced - Fix Permissions). It was instantly fixed.
I took a full backup before trying this, but didn't need it.
Click to expand...
Click to collapse
it took me time and I did it using clockwork mod recovery
advanced then fix permissions
but nothing happen , still the same.
should I try flashing TWRP recovery then..
if yes. could u help me with a simple guide
much appreciated
thank you
Sent from my Nexus 7

windwhisper said:
it took me time and I did it using clockwork mod recovery
advanced then fix permissions
but nothing happen , still the same.
should I try flashing TWRP recovery then..
if yes. could u help me with a simple guide
much appreciated
thank you
Sent from my Nexus 7
Click to expand...
Click to collapse
You can boot any recovery you want without hard-flashing it to the device (so long as the boot loader is unlocked).
With the device in bootloader/fastboot mode,
Code:
fastboot boot name-of-recovery-image-file.img
So download TWRP and give it a roll.

Hello,
I got the same "System UIDs Inconsistent" problem. I like to solve my problems myself but I've got no way out this time, so I'm asking for your kind help.
I'm on the SGS III, i9300, I rooted it then went to Omega ROM, and then to Paranoid Android. Everything went well until I got a battery problem (when charging the phone, it was not sufficient to bear with it functionning, so it powered out while charging). After that, the phone restarted and the UID problem appeared. Maybe it's just a coincidence.
So far, I : fixed permissions, did at least 10 factory resets with TWRP, changed ROM (went to CM and came back to PA as nothing changed).
I read the 6 first post about this in xda forum, and other forums too, but nothing came out as an evidence.
Last thing I did was upgrade my PA ROM : the phone couldn't even go beyond the booting process, failed to initiate the phone "first settings" app.
So I came back to the previous version of PA, and was able to use my phone again, but apps like Gmail, Color Note, won't work.
I want to get rid of that, and I wish someone told me, step by step, the things I could do to eradicate the problem. I will do what's necessary to achieve that, I only need someone who knows what to do, and how to do it. I saw some tricks that maybe could do the job but I don't have the knowledge to choose one.
That's my first message here so I hope I didn't break the rules of the forum ^^ If you want any informations about my device to help me, just ask
Thanks a lot, and I hope my english is not too bad ! Have a good day.

Thanks
I got this message too without having any other problem with this TWRP version or Hairy Bean 2.2
The message appeared after flashing the new 4.2.1 (?) modded bootloader for Hairy Bean and the ROM itself.
I'm not sure whether the ROM or bootloader are causing it but mine got fixed by fixing the permissions via TWRP.
Thanks for the tip! :good:

In my case only re-partitioning helped.

for me uninstalling quadrant did the trick

That did it
devra1 said:
I found the answer in another thread. I used TWRP (Advanced - Fix Permissions). It was instantly fixed.
I took a full backup before trying this, but didn't need it.
Click to expand...
Click to collapse
Quick and easy. Worked for me. Thanks

devra1 said:
I found the answer in another thread. I used TWRP (Advanced - Fix Permissions). It was instantly fixed.
I took a full backup before trying this, but didn't need it.
Click to expand...
Click to collapse
This worked for me, too. Thank you.
My situation was a little bit different:
- Flashed Paranoid Android 3.99
- everything was fine (for a few reboots) until I made a nandroid back up with CWM 6.0.3.6 ( which was surprisingly slow, almost 1,5h)
- rebooted
- UID consistency problem
- tried to boot temporary into TWRP - NOT POSSIBLE!
- flashed TWRP 2.6.0.0 permanently
- TWRP: advanced - fix permissions: SUCCESSFUL!
Maybe I'll keep TWRP, but I'm used to CWM for years now.
CWM has removed "fix permissions" since 6.0.3.5 (http://review.cyanogenmod.org/#/c/45945/ )

Fix Permissions
For me worked fixing permissions through TWRP on CM 10.2 latest nightly (10082013).

edbertin said:
For me worked fixing permissions through TWRP on CM 10.2 latest nightly (10082013).
Click to expand...
Click to collapse
Me too! TWRP on SlimRom 4.3
Thanks

I am also having this issue after I flashed SlimBean Beta 4 Weekly-409 on my i9300 (wipe data/cache/dalvik and clean install with gapps) and tried restoring a couple of apps like Any do and Temple Run 2 with Titanium Backup.
Is the TWRP being referred here mean the TWRP manager? I installed it from play store but I don't find 'fix permissions' option anywhere in it.
I remember of seeing it in SuperSU but I am unable to install that as well as it says the binary needs to updated.
Could someone please help me here?
Thanks!
--IH

Confirmed. Get into the TWRP n do a fix cache wipe/dalvik wipe/fix permission

Thank you for clarifying this fix
polarfrz said:
Quick and easy. Worked for me. Thanks
Click to expand...
Click to collapse
I just updated my S4 to 10.1 Hyperdrive and experienced this very same issue. Rebooting into safestrap and fixing permissions cleared up this very annoying issue on my phone.

I flashed gummy V4.4 yesterday works great. I went into rom toolbox and changed LCD density to 361 and rebooted, got the UID inconsistent message.
found this thread, fix permissions in TWRP, all fixed. bing bang boom.

thanks all, I also fixed with TWRP latest version, and try to roll back to CWM

I installed a new ROM and I got the System UIDs inconsistent error, then my S Planner FC. I went to find the txt file and it stated that the problem is related to Calendar Storage. I deleted the apk and placed a new one back in. Problem persists, I scratched my head for so long and then I found this thread.
THANK YOU, fixing permission for the Calendar Storage did the trick! Thank God I found this thread!

[Help Needed] Apps won't restore or install after flashing rom [SOLVED!]

Well, my first venture into rom flashing hasn't been the most successful one as it's caused a really strange issue that a couple people on another thread have tried to help me solve, but I figure I had hijacked that thread long enough so this issue deserved it's own thread.
I rooted, unlocked bootloader, and installed TWRP v2.4.0.0 on Stock Android 4.1.1. Everything worked great. Until I flashed a rom. Now, I have been through wiping Cache, Dalvik Cache, Factory Reset, Flashing the rom (I've tried 4 with the same exact issue), flashing Gapps... All seems to go well and it says "success" when I flash, and I reboot into system. Run the setup of Google. Everything seems great and working fine. Here's where the problem is. When Google Play Store starts downloading for restore, and I'm on a solid wifi connection, nothing downloads. I have also tried stopping the downloads and installing apps individually. When I do that, I receive the same error message over and over for any app:
Unknown error code during application install: "-24"
I've rebooted, wiped cache, dalvik cache. Nothing installs. Same error. I did somehow, some way, get Titanium backup to install after numerous tries... when I try to restore any of that backup it just hangs on the first app. It does not restore anything. No batch apps. No single apps. No app data.
The odd thing is, the first time I flashed a rom, it seemed to load up fine. Stupidly, when I was running Titanium Backup for a restore I was not paying attention to what I was restoring. I was restoring all apps and app data... It caused an issue and a bunch of force closes, as you can probably imagine. So I rebooted into recovery and wiped and reinstalled rom and gapps. And virtually nothing has installed since. I have wiped and reinstalled AOKP, PACman, Carbon, and CM to no avail. Nothing seems to solve my issue. I'd love to at the very least be able to regularly install apps from the Play Store. At this point I'm not even concerned with restoring app data if that's too much to ask. I just want to be able to use my phone normally again as this is my "daily driver". If I have to go back to 4.1.1, that would be fine with me. I just want to get back to normal. And I'll do whatever it takes to get there. Any help at all would be appreciated.
Here is the original thread that some people have been giving me great advice on as to what to do, but none of it has fixed the issue yet unfortunately:
http://forum.xda-developers.com/showthread.php?t=2341470

Jersey846 said:
Well, my first venture into rom flashing hasn't been the most successful one as it's caused a really strange issue that a couple people on another thread have tried to help me solve, but I figure I had hijacked that thread long enough so this issue deserved it's own thread.
I rooted, unlocked bootloader, and installed TWRP v2.4.0.0 on Stock Android 4.1.1. Everything worked great. Until I flashed a rom. Now, I have been through wiping Cache, Dalvik Cache, Factory Reset, Flashing the rom (I've tried 4 with the same exact issue), flashing Gapps... All seems to go well and it says "success" when I flash, and I reboot into system. Run the setup of Google. Everything seems great and working fine. Here's where the problem is. When Google Play Store starts downloading for restore, and I'm on a solid wifi connection, nothing downloads. I have also tried stopping the downloads and installing apps individually. When I do that, I receive the same error message over and over for any app:
Unknown error code during application install: "-24"
I've rebooted, wiped cache, dalvik cache. Nothing installs. Same error. I did somehow, some way, get Titanium backup to install after numerous tries... when I try to restore any of that backup it just hangs on the first app. It does not restore anything. No batch apps. No single apps. No app data.
The odd thing is, the first time I flashed a rom, it seemed to load up fine. Stupidly, when I was running Titanium Backup for a restore I was not paying attention to what I was restoring. I was restoring all apps and app data... It caused an issue and a bunch of force closes, as you can probably imagine. So I rebooted into recovery and wiped and reinstalled rom and gapps. And virtually nothing has installed since. I have wiped and reinstalled AOKP, PACman, Carbon, and CM to no avail. Nothing seems to solve my issue. I'd love to at the very least be able to regularly install apps from the Play Store. At this point I'm not even concerned with restoring app data if that's too much to ask. I just want to be able to use my phone normally again as this is my "daily driver". If I have to go back to 4.1.1, that would be fine with me. I just want to get back to normal. And I'll do whatever it takes to get there. Any help at all would be appreciated.
Here is the original thread that some people have been giving me great advice on as to what to do, but none of it has fixed the issue yet unfortunately:
http://forum.xda-developers.com/showthread.php?t=2341470
Click to expand...
Click to collapse
2 suggestions:
1) i think others have reported having issues with TWRP 2.4, so try 2.5 or 2.3.2.3
2) I think the error could be a lack of internal storage, so certainly try the "wipe internal storage" in TWRP (after making sure that your ROM/GApp files, backups (including Tibu) are saved to your external folder

jco23 said:
2 suggestions:
1) i think others have reported having issues with TWRP 2.4, so try 2.5 or 2.3.2.3
2) I think the error could be a lack of internal storage, so certainly try the "wipe internal storage" in TWRP (after making sure that your ROM/GApp files, backups (including Tibu) are saved to your external folder
Click to expand...
Click to collapse
Ok giving this a shot. I did notice that you had mentioned a different version of TWRP than I had. I will try the wiping internal storage before I install a different TWRP then if that doesn't work, TWRP. Gotta find the external folder. Unless you just mean anything that is on the actual SD card.

Jersey846 said:
Ok giving this a shot. I did notice that you had mentioned a different version of TWRP than I had. I will try the wiping internal storage before I install a different TWRP then if that doesn't work, TWRP. Gotta find the external folder. Unless you just mean anything that is on the actual SD card.
Click to expand...
Click to collapse
i would actually recommend installing TWRP 2.5 first.
never wipe external SD card.
if you have an app called Root Explorer, that works best.

jco23 said:
i would actually recommend installing TWRP 2.5 first.
never wipe external SD card.
if you have an app called Root Explorer, that works best.
Click to expand...
Click to collapse
Ok I'll try 2.5 then. And I wasn't gonna wipe the card, just was wondering if when you said external folder you were talking about the SD card. Root explorer works great.. if i could install it.
EDIT: Since I am away from my computer, I tried the multiple wipe method. Didn't change anything. So I will be changing TWRP versions later and will post an update.

Jersey846 said:
Ok I'll try 2.5 then. And I wasn't gonna wipe the card, just was wondering if when you said external folder you were talking about the SD card. Root explorer works great.. if i could install it.
EDIT: Since I am away from my computer, I tried the multiple wipe method. Didn't change anything. So I will be changing TWRP versions later and will post an update.
Click to expand...
Click to collapse
You never mentioned using TWRP 2.4. DEFINITELY replace that. Also, just a thought. If you haven't already done so, try using the option to fix permissions. I'm fairly sure its an option in TWRP.
Sent from my XT907 using xda premium

Back in business! Wow thank you all so much! What a pain it's been but without the help I'd have never guessed how to get this running as perfectly as it is now. Here's what worked for me:
Installed TWRP 2.5 (Instead of what I had, 2.4)
Then followed jco23's precise directions:
jco23 said:
- I use TWRP 2.3.2.3 (SS has been uninstalled via it's own app, not Tibu or the system awhile ago) - but TWRP 2.5 works just fine for others
- after downloading the ROM and GApps (or any file that I intended to flash for that matter), I always place the file on the mnt/external1 directory. I
m not sure if this will make a difference, but I recall it being an issue back on my Droid Charge days
- after flashing the files, does TWRP say successful?
- perhaps you do need to a double wipe of everything prior to flashing:
1) mount everything
2) wipe cache
3) wipe dalvik cache
4) wipe system
5) factory reset/wipe data
6) wipe internal storage (if you do this, make sure to change your TiBu backup folder to your external1 directory, or this will be gone too!!!!! also make sure that the system backup you made is on the external1 directory as well
7) reboot recovery
8) install ROM
9) install GApps
Click to expand...
Click to collapse
And it's working flawlessly. Able to download or restore anything from Gapps. Was able to restore some specific app data from Titanium Backup (did not want to ruin the phone again and do that full restore so I selected specific apps that I really wanted the data on).
Thanks to everyone who took the time to assist me and a special thanks to jco23 and netizenmt who were with me through this whole debacle, leading me through every possible fix they could think of. As for those of you that may be wondering which ROM I settled on... AOKP.

Good for you bro! That stinking TWRP 2.4.0 is such a menace! Wish there was a way to have it yanked from circulation. Glad you're up and running!
Sent from my Droid Razr M using xda premium

Jersey846 said:
Back in business! Wow thank you all so much! What a pain it's been but without the help I'd have never guessed how to get this running as perfectly as it is now. Here's what worked for me:
Installed TWRP 2.5 (Instead of what I had, 2.4)
Then followed jco23's precise directions:
And it's working flawlessly. Able to download or restore anything from Gapps. Was able to restore some specific app data from Titanium Backup (did not want to ruin the phone again and do that full restore so I selected specific apps that I really wanted the data on).
Thanks to everyone who took the time to assist me and a special thanks to jco23 and netizenmt who were with me through this whole debacle, leading me through every possible fix they could think of. As for those of you that may be wondering which ROM I settled on... AOKP.
Click to expand...
Click to collapse
glad you finally got it working - this is just the first step in becoming a crack-flasher....

jco23 said:
glad you finally got it working - this is just the first step in becoming a crack-flasher....
Click to expand...
Click to collapse
Yeah, I've got it bad. I have had CM 10.1, Slimbean, Carbon AND AOKP on my phone all in the last 2 days. Carbon is on it right now. No telling what will be on it by tonight.
Sent from my XT907 using xda premium

netizenmt said:
Yeah, I've got it bad. I have had CM 10.1, Slimbean, Carbon AND AOKP on my phone all in the last 2 days. Carbon is on it right now. No telling what will be on it by tonight.
Sent from my XT907 using xda premium
Click to expand...
Click to collapse
funny, and the goal is to find a ROM that you're happy with and don't need to flash.
but I've been on Carbon since 7/5, and very happy.

[Q] Different backups, superusers, and flashing kernels

Hi all,
I have learned a lot about Android customization in the last week since my Nexus 4 finally arrived at my door, and I have become reasonably comfortable with the processes of flashing ROMs/kernels, and backing up my phone to make sure I have something stable to return to if something happens to go wrong. However, I am still dealing with a few points of confusion that I was hoping someone could clarify for me:
1. I have CWM installed on my phone and I can use it to backup/restore images of my phone for safety. However, I have heard about other methods like Nandroid, Carbon/Helium, and Titanium Backup while browsing the forums, and have tried them only to become confused as to how they are different from using CWM backup. Could someone please explain this to me and clarify which is the best for keeping a backup of my phone stored on my computer?
2. I have noticed that when I "wipe date/factory reset" in CWM, not everything on my phone is wiped. There are still plenty of files left over from previous ROM installs when I browse my phone with Android File Transfer, and obviously the .zip files you need to flash new ROM's/kernels are left too. What exactly is deleted when do a CWM factory reset?
3. Is it necessary to wipe everything when installing a custom kernel? I have CyanogenMod 10.2 installed because it is quick and relatively bloat-free, but allows for enough customization that I can make the my phone feel the way I want it to. I want to give Matr1x/Hells-core a try, but I am tired of factory reseting everything when install a new kernel. Can I get away with just wiping Cache/Dalvik and flashing the new kernels? If not, what is the best way to avoid losing app data between ROM and kernel flashes?
4. What is the difference between the default Android superuser, CWM superuser, and SuperSU? They all seem like the same thing and it makes me nervous installing different ones.
Any information you guys can offer would be great. Thank you so much for your time !

Downloaded7 said:
Hi all,
I have learned a lot about Android customization in the last week since my Nexus 4 finally arrived at my door, and I have become reasonably comfortable with the processes of flashing ROMs/kernels, and backing up my phone to make sure I have something stable to return to if something happens to go wrong. However, I am still dealing with a few points of confusion that I was hoping someone could clarify for me:
1. I have CWM installed on my phone and I can use it to backup/restore images of my phone for safety. However, I have heard about other methods like Nandroid, Carbon/Helium, and Titanium Backup while browsing the forums, and have tried them only to become confused as to how they are different from using CWM backup. Could someone please explain this to me and clarify which is the best for keeping a backup of my phone stored on my computer?
A backup in CWM is the same as a nandroid backup. It basically take a "snapshot" of your ROM and restore it exactly as it was when backing up.
Titanium Backup is an app that backup your apps and app's data. It's recommend you only restore user's apps and data. Let Google restore any system app's data.
2. I have noticed that when I "wipe date/factory reset" in CWM, not everything on my phone is wiped. There are still plenty of files left over from previous ROM installs when I browse my phone with Android File Transfer, and obviously the .zip files you need to flash new ROM's/kernels are left too. What exactly is deleted when do a CWM factory reset?
Wiping data/factory reset only wipe the data. Wiping system will wipe your ROM (system partition) Of course you don't want to wipe all the files such as the ROM you're going to flash.
There's an option to format internal sd, that will wipe EVERYTHING so unless you know how to ADB push files or sideload a ROM, DO NOT touch that.
3. Is it necessary to wipe everything when installing a custom kernel? I have CyanogenMod 10.2 installed because it is quick and relatively bloat-free, but allows for enough customization that I can make the my phone feel the way I want it to. I want to give Matr1x/Hells-core a try, but I am tired of factory reseting everything when install a new kernel. Can I get away with just wiping Cache/Dalvik and flashing the new kernels? If not, what is the best way to avoid losing app data between ROM and kernel flashes?
No, just flash kernel. Some recommend wipe cache and dalvik cache after kernel flash before reboot.
4. What is the difference between the default Android superuser, CWM superuser, and SuperSU? They all seem like the same thing and it makes me nervous installing different ones.
Different app that does the same thing. Usually go with what is recommend by the ROM's dev. I ususally just leave what's included with the ROM.
Any information you guys can offer would be great. Thank you so much for your time !
Click to expand...
Click to collapse
Hope that answer some of your questions. I'm sure I left out some stuffs so hopefully someone else can add to it.:good: