Boot0 boot1 error: Hack boots only from USB, help!

Hello you awesome people.

My spiffy Hackintosh has been misbehaving recently and after searching and trying all I could find, I still am unable to fix it.

I have had a perfectly running hack for several months ( i5 3570k, GA-Z77-DS3H, Nvidia GT 640, Samsung 128GB SSD, Corsair 16GB ram) but now all of a sudden it decided it won't boot, instead giving me this:


I have researched this issue and found out that it does boot from a USB, then working as usual, I tried re-installing everything including bootloader from most recent Multibeast, I also took out the SSD, plugged into other macbook and did all the disk repair, verify permissions, etc, but nada. It still won't boot on its own, without the USB.

Any help, or advice on where to go from there?
I suppose a fresh re-install could fix the problem, but first I would like to see if there is any other way to fix this.

Thanks a lot - you are an excellent community, I trust in you!

See boot0 Error: The Official Thread

I tried first the second method (unplugged HDD, plugged it into other Mac, ran multibeast) and didn't work.

Now I've tried the dd if=/Volumes/"Unibeast Volume Name"/usr/standalone/i386/boot1h of=/dev/disk0s2
method and it gave this message:
2+0 records in
2+0 records out
1024 bytes transferred in 0.001042 secs (982830 bytes/sec)

Then I quit terminal, restarted, and got the same boot1: error message once again. Any further ideas?

JackDavolio said:

I tried first the second method (unplugged HDD, plugged it into other Mac, ran multibeast) and didn't work.

Now I've tried the dd if=/Volumes/"Unibeast Volume Name"/usr/standalone/i386/boot1h of=/dev/disk0s2
method and it gave this message:
2+0 records in
2+0 records out
1024 bytes transferred in 0.001042 secs (982830 bytes/sec)

Then I quit terminal, restarted, and got the same boot1: error message once again. Any further ideas?

Click to expand...

You're getting a boot1 error, not boot0 error. Boot0 error is where boot0 (stage0 chimera boot loader) cannot find boot1 (stage1 chimera boot loader). Since you're getting a message from boot1, it is clear that boot0 is finding boot1. Boot1 looks is looking for /boot (stage3/final chimera) on (the first) HFS+ partition. So, does your main HFS+ partition have a file called /boot? (run 'ls -l /' in terminal to see).

Have you tried simply re-installing Chimera?

Have you tried Disk Utility 'repair' (by booting Unibeast into the Installer then going into Disk Utility). Because it is sounding like a file system corruption issue... (given that it just suddenly happened...)

Hey Rehabdude, thanks for your assistance.

I have indeed tried re-installing chimera and even all sorts of disk repair, now I have tried what you recommended and it seems that there is a /boot file indeed.

I get a list of folders in terminal, the one that specifies boot is as follows:

" -rw-r--r--@ 2 root wheel 272800 9 Aug 2012 boot "

I am now researching on the forum to see if anyone else has come up with a solution. If anybody knows of what else could I do for diagnosis please let me know, thanks!

Hi!

Simply switch to Clover, and all this annoyances will vanish. Clover is definitely not as straightforward as Chameleon/Chimera/Enoch, but since your bootloader is broken, that's a good opportunity for trying something new, and i guess the time you'll spend on it will give you both knowledge and a perfectly booting system (even more: a true UEFI boot if you dare so, perfect for Radeon 7xxx cards), while the time you're spending/have spent trying to fix your current bootloader is only giving you headaches.

Look for Clover on Insanelymac site > Developers Corner > Bootloaders > Clover and ask help there: the main developers of Clover answer all questions asked. Good luck and report here your results, if you do decide to do the switch.

All the best!

RehabMan said:

You're getting a boot1 error, not boot0 error. Boot0 error is where boot0 (stage0 chimera boot loader) cannot find boot1 (stage1 chimera boot loader). Since you're getting a message from boot1, it is clear that boot0 is finding boot1. Boot1 looks is looking for /boot (stage3/final chimera) on (the first) HFS+ partition. So, does your main HFS+ partition have a file called /boot? (run 'ls -l /' in terminal to see).

Have you tried simply re-installing Chimera?

Have you tried Disk Utility 'repair' (by booting Unibeast into the Installer then going into Disk Utility). Because it is sounding like a file system corruption issue... (given that it just suddenly happened...)

Click to expand...

hey rehabman, i have the same problem with boot1 error but i think i screwed it up a little! i hope there is a fix for this without formating the drive? i have a looot of things i need here and a lot of music projects and installed plugins and everything. so, i wanted to fix my hdmi to work and i installed clover but without testing it on a usb. i "nailed" it directly on HD without reading instructions and forums. now i got stucked. i boot with my usb i started hackintoshing my lap top so can u give me a little bit more detailed advise what to do? as i see it could be better to switch to clover but can i do it after i installed it on my HD? and how? thnx a lot !

batterylove said:

hey rehabman, i have the same problem with boot1 error but i think i screwed it up a little! i hope there is a fix for this without formating the drive? i have a looot of things i need here and a lot of music projects and installed plugins and everything. so, i wanted to fix my hdmi to work and i installed clover but without testing it on a usb. i "nailed" it directly on HD without reading instructions and forums. now i got stucked. i boot with my usb i started hackintoshing my lap top so can u give me a little bit more detailed advise what to do? as i see it could be better to switch to clover but can i do it after i installed it on my HD? and how? thnx a lot !

Click to expand...

You should be able to re-install Chimera, but the Chimera installer will probably not overwrite the Clover MBR code (I'm assuming you installed Clover in Legacy/BIOS mode, not UEFI). For some reason it will only overwrite an MBR that is empty, Windows, or Chimera itself. So, for that you'll need to run Chameleon Wizard and force a write of boot0md or boot0, depending on your situation (see descriptions in Chameleon wizard).

If you can't boot, hopefully you can use your Unibeast USB to get your system booted...

I have a similar setup only difference is a 480 Corsair SSD and 2 partitions, 1 mac journaled and 1 fat. Both are on a GUID style. Same exact problem.

Boot0 problem fixed via cmd line via the offical boot0 thread and then I get this. Tired booting back up off the unibeast drive, which works, and reinstalling chimera which gives me an old grub style boot loader that just hangs after selecting my hackintosh build.

No alternate bootloaders, followed the guides verbatim, by the book. Using an H87-D3H.

Solved my own problem. I didn't have the xhci and ehci settings correct in the bios. Someone in another thread stated the bios settings to be other than what I had used, but a little digging led me to the right combo.