Boot0 error when starting without USB

Hello!

I ran Unibeast and Multibeast to install Mountain Lion on my Hack Pro. Now if I try starting the PC without the Unibeast flash drive it gives me the following error:

boot0: GPT
boot0: test
boot0: test
boot0: GPt
boot0: test
boot0: test
boot0: error

Any ideas how to fix this issue so I can boot without the USB? Do I need to partition my 2 tb hard drive or is that just if you're installing Snow Leopard?

I followed all of the steps exactly from this tonymac guide.
http://www.tonymacx86.com/61-unibeast-install-os-x-mountain-lion-any-supported-intel-based-pc.html

Thanks!

Also, here's some of my specs:

Gigabyte motherboard z77x-ud5h Bios v.14
EVGA GeForce GTX670
32 GB Corsair Vengeance RAM
Intel i7 3770k quad core 3.5 ghz
2 tb Western Digital HDD Caviar Black
(basically followed top specs posted for Hack Pro)

Tried this option.

http://www.tonymacx86.com/25-boot0-error-official-guide.html

When entered in I received this message

dd:unknown operand HDD


any other ideas?

Seems like your getting the syntax wrong on the Sudo command. Are your sure your typing it correctly and using the correct name of your USB stick? Also you did unmount the hard drive?

Got rid of the boot0 error. Now I'm stuck on the grey apple loading screen with the dashed wheel. The loading bar on the boot screen also moves from right to left as if it is going backwards.

GraphcisEnabler=No only gets it to a grey screen with the cursor frozen on it. I know I checked to turn it off in Multibeast already.



This is what I did to get rid of boot0 error:

I entered:

dd if=/Volumes/USB/usr/standalone/i386/boot1h of=/dev/disk0s2

This was the response:

2+0 records in
2+0 records out
1024 bytes transferred in 0.001042 secs (982830 bytes/sec)

thestarman2112 said:

Got rid of the boot0 error. Now I'm stuck on the grey apple loading screen with the dashed wheel. The loading bar on the boot screen also moves from right to left as if it is going backwards.

Click to expand...

I'm in the same spot. Have you found a fix for this problem?