Android Enthusiasts Stack Exchange is a question and answer site for enthusiasts and power users of the Android operating system. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I've just installed the new MildWild (oxygen) rom, to replace my very old LeeDroid rom.

It's seemed to have installed fine, but when the phone boots, I get the 'mildwild' logo on screen, just animating for ages, nothing seems to happen.

Is this a problem with the install? I cleared all my partitions, cache, dalvik, etc, and ClockWork didn't report any errors.

Anyone have any ideas? Or shall I just try a different rom? I'm working with a UK HTC Desire (bravo)

share|improve this question
How long did you wait? It must be rebuilding dalvik cache. – roxan Jan 23 '12 at 12:56
I gave it about 10 minutes. Should I wait longer? – David Yell Jan 23 '12 at 12:58
up vote 1 down vote accepted

This actually can happen with any ROM you install.

If you are not installing a "new" version of the same ROM, you can get in to a boot loop. You have to do a factory reset and clear the data and cache when installing a new ROM for the first time.

If you are installing an upgraded version of the ROM, you don't have to do the wipe (unless the instructions tell you that you should). But you should always clear the cache.

When the device boots up for the first time, after clearing the cache, it needs to rebuild the cache for the applications you have installed. The more applications that you have installed, the longer it will take to boot the first time.

Keep an eye on the "boot up", if it looks like it is "starting over" and not just replaying the boot animation, you are in a boot loop. If you have adb installed, you can plug the device in and look at the logcat that is going on during the boot process. This can also help you determine if you are in a loop or not.

share|improve this answer
Marked as accepted, as you put it better than I did, and gave more in-depth response :) – David Yell Jan 24 '12 at 9:55

I had not done a factory reset. Once I had done this, it took about 2 minutes to boot up!

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.