• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

2.1 ROM glitching

I've downloaded a couple different ROMs last couple weeks and everyone of them is causing force close issues. Mainly getting htc sense force closes. like I said I've downloaded Alouyosis fresh and damageless and keep getting the same issues. I even RUU back to 1.5 and rerooted. still getting same issues. If anyone has a clue please help. Thanks in advance.
 
That is quite a vague description of what your problem is. Which ROM did you start with? Did you make sure to wipe both data and dalvik before you flashed a new ROM? What exactly is causing FC?

Keep in mind, the more info you provide, the more we can help you out.

Help us to help you :)
 
Upvote 0
Could someone please explain, or even link me to, how to perform a wipe dalvik? I have no problem wiping data/factory reset, but when I try to either wipe dalvik or even wipe SD, I continuously get an error message telling me that i must run 'wipe dalvik" via adb.

I'm confused
Check the amount of free space on your SD card. It may be that you are short on space. If so, try moving one or more of your Nandroid backups to your computer for safe keeping. I had this issue, and this worked.
 
Upvote 0
Could someone please explain, or even link me to, how to perform a wipe dalvik? I have no problem wiping data/factory reset, but when I try to either wipe dalvik or even wipe SD, I continuously get an error message telling me that i must run 'wipe dalvik" via adb.

I'm confused

Check the amount of free space on your SD card. It may be that you are short on space. If so, try moving one or more of your Nandroid backups to your computer for safe keeping. I had this issue, and this worked.

This typically happens as a result of running the 1.5.2 Recovery Image. It is a known bug. Technically it still wipes dalvik even though it gives you that error. If you were to upgrade to 1.6.2 Recovery Image, you would no longer get that error.
 
Upvote 0
This typically happens as a result of running the 1.5.2 Recovery Image. It is a known bug. Technically it still wipes dalvik even though it gives you that error. If you were to upgrade to 1.6.2 Recovery Image, you would no longer get that error.
Oh yeah! Good call! I totaly forgot about that bug. I'm using 1.6.2. Been a long couple of days!
 
Upvote 0

BEST TECH IN 2023

We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.

Smartphones