Chimera sends me in a loop

Hello:

I updated to 10.8.3 and ran Multibeast afterwards to re-enable audio. When I booted back into Mountain Lion I still didn't have audio, no output devices were showing up in the sound settings under System Preferences.

I decided to rerun Multibeast again and this time enabled a few other things as well that I normally pick for my system (3rd Party SATA, hnak's ethernet driver, nothing out of the ordinary.).

I tried rebooting and this time the resolution of my Chimera boot screen had changed. The icons were larger. I tried booting into Mountain Lion but it would not boot. The system would just restart and bring me back to the Chimera boot screen. Not even safe mode (-x) works.

Is there anyway to fix this? Or will I have to reinstall Mountain Lion? It seems to have rolled me back to an earlier version of Chimera (I updated to Chimera 2.0.1 last month).

If I have to reinstall ML is it safe to do so without harming the other OSes on the drive (Win7 and Ubuntu)? Can I just put the USB key in and tell it to install ML to the partition named "Mountain Lion", and install Chimera to the drive so I can pick an OS to boot?

After modifying the system definition I had a similar issue...
What I did (after panicking) was :
1) Used the unibeast install USB key as a boot loader (check the BIOS settings so the USB key is first in the list), then I could boot on my normal OS HD.
2) Used Multibeast again to reapply modification
3) Used Chimera 2.X (that I had used to activate iMessage)

Then I could boot normally. Hope you might have similar results

I have my Unibeast USB key, but when I plug it in and boot it doesn't give me the option to boot into ML. It looks as though it just gives me the option to reinstall the OS. Is there something I'm supposed to press to get it to boot me into my existing ML partition?

I tried booting into ML from my hard drive. I used the -x and -v options. I get as far as the screen below and then it freezes for a few seconds before going back out and into Chimera again and asking me to select an OS to load. It repeats this endlessly unless I tell Chimera to load Win7 or Ubuntu (both of which load normally).

What I did was :
1) Connect the USB key I used to install ML
2) When I start the computer I go to the BIOS settings and set the USB key as the first device in the boot order. Save & Exit BIOS
3) The computer reboot using the USB key.
IF you let it boot on its own it will go to the installer. If you know what are the incriminating files you can use the Terminal (utilities menu) to remove them.
BUT instead you can touch a keyboard key when the bootloader is present to avoid launching the installer and then select you normal system partition. In my case allowing me to boot on my normal OS partition and reapplying Multibeast & Chimera
4) This solved my problem

I can't seem to get ML to boot. And my problem sounds suspiciously like this guy's --> http://www.tonymacx86.com/general-h...fter-foolishly-updating-through-appstore.html (although I don't think updating from the App Store is the problem since my problem also happens when updating via the combo pack).

Anyways, I tried reinstalling ML three times last night. All three times Chimera does the same thing after I update to 10.8.3 and re-run Multibeast.

First I installed ML 10.8.2 from my USB key.
Then ran the latest MultiBeast and Chimera and rebooted.
Then updated to 10.8.3 via the App Store/Combo pack. Rebooted.
Then re-ran MultiBeast to get my audio working. Rebooted.
Then ML won't boot and I go back out into the BIOS. Back to the Chimera boot screen and I'm stuck in a loop without booting ML.

Something I've noticed. After I install 10.8.3 and re-run MultiBeast my version of Chimera reverts back to an older version (1.11.something). Does running MultiBeast also reinstall an older version of Chimera? Should I re-run Chimera every time I run MultiBeast?

Is there a way to break the loop and boot into ML? Using -x doesn't work. Trying to boot with -v gives me the screen that you see in my earlier post. Is it possible to use my ML USB key, open up a terminal, and modify some files so I can get ML to boot and update Chimera to the latest version?

Yes you have to reapply Chimera after (I guess like me you used the 2.xx version to get Messages working)

Another thing I really feel like you shouldn't have to reinstall OS X (I didn't have too), the issue is that you modified your system to use Chimera 2.xx that multibeast breaks.

I only used the USB install key in first position (thanks to BIOS settings) in order to avoid the boot loader on my main disk. Maybe I'm missing something.