Well the problem is your flashing between basix, which is rooted in the kernel, verses Exodus, which is currently rooted the scripted way. I had this problem switching between the two, and until my next release of 1.0, it won't be so easy to go back and forth. Typically to have a fresh install of either ROM esp basix because it uses a custom kernel, you have to odin wipe it. Plus if your restoring any of your apps, that can also mess up either rom. Myback up root is good, but if you backup the superuser, or some of the system it can mess with either, and more specifically Exodus.
This is why I worked long and hard with alot of help from k0 to root the phone just like the script, verse his which is the typical standard way of rooting (this was prior to the release of his rom, and I wanted him to get full credit for the custom kernel he worked hard on). Yes if your saying you get that glitch at start up, that's because your switching between the two. You can try just a factory reset in the CWM, and flash one or the other. But no matter what, you kernel will be basix if you go between them, because basix uses custom kernel. If I'm not making sense to you, back up your contacts/important stuff, then you need to use this:
http://androidforums.com/indulge-all-things-root/335191-910-how-flash-using-odin-return-stock.html
Then don't root, just boot up and put it in debugging mode and use this after your back to stock:
http://androidforums.com/indulge-al...ne-root-clockworkmod-win-intel-mac-linux.html
Then when the phone reboots, go into CWM, aka from off hold PWR+R, then flash the rom you want. Another problem is, you DONT NEED TO ROOT YOUR PHONE prior to either installing Exodus or Basix. Because both roms are already rooted, I believe that is the source of your problems.
