boot0 Error: The Official Guide

[keveye]

Article: boot0 Error: The Official Guide

Having the same issue, but kind of restricted to Method no.1 as I do not have a USB adapter.

Configuration:
Intel i5 4440 / Gigabyte H87M-HD3 / 240GB M500 Crucial SSD

(1) Installed Mavericks using UniBeast - required -x at boot to proceed to the installer
(2) Ran Multibeast DSDT Free
(3) Attempted to boot after Multibeast install from SSD, getting the boot0 error

(4)Tried to boot into the installer from the 32GB USB key using -x, now getting a Kernel Panic so cannot access disk utility to apply the fix for the boot0 problem?

any ideas as to what I can do?

thanks

 

[keveye]

Article: boot0 Error: The Official Guide

Resolved for anyone else with a similar issue:

To resolve the kernel panic I executed commands to remove Appletymcedriver.kext, which enabled me to boot into disk utility and perform step 1,

thank you for the guide,

Kev

Having the same issue, but kind of restricted to Method no.1 as I do not have a USB adapter.

Configuration:
Intel i5 4440 / Gigabyte H87M-HD3 / 240GB M500 Crucial SSD

(1) Installed Mavericks using UniBeast - required -x at boot to proceed to the installer
(2) Ran Multibeast DSDT Free
(3) Attempted to boot after Multibeast install from SSD, getting the boot0 error

(4)Tried to boot into the installer from the 32GB USB key using -x, now getting a Kernel Panic so cannot access disk utility to apply the fix for the boot0 problem?

any ideas as to what I can do?

thanks

 

[wstrohm]

I got a "Boot0" error after Mavericks 10.9.2 had been installed and working for several weeks. I used a variation of Solution 1 to recover, as follows:

1. Plug in Unibeast USB flash drive and press computer power button.
2. At the (Gigabyte) BIOS splash screen press F12.
3. Scroll selection down to boot on the Unibeast USB drive.
4. When the Mac OS X installer opens, select "Utilities" from its menu.
5. Open "Disk Utility." Select the problem disk and click "Unmount."
6. Quit "Disk Utility" and open "Terminal."
7. Type the following in Terminal after its opening string:
dd if=/usr/standalone/i386/boot1h of=/dev/disk0s2
8. Quit Terminal. Quit the Mac OS X installer, power down and remove the USB flash drive.
9. Reboot normally on the (previously faulty) disk.

I fear this "Boot0" issue may happen periodically, since there was no warning before it happened.

 

[grodid0]

Hello,

I found this boot1h fix very useful and very efficient.
I have a remark, however: it happened to me that I had to restore all my install of Mavericks on a Hackintosh NUC D54250WYK.
For this, I used a Time Machine backup, stored on a 4k block-sized HD drive. I also checked my SSD drive was 4k block-sized.
But, upon restore, the SSD was showing this "boot0: error" thing, and I had to re-apply the "dd if=..." fix once again.

Is this behavior expected ? Is there a workaround/fix for it ?

Thanks in advance for any hint, Best, G.

PS BTW, I believe the command must be "dd if=/usr/standalone/i386/boot1h of=/dev/disk0s2 bs=4096"

 

[nikko20040]

Article: boot0 Error: The Official Guide

I got a "Boot0" error after Mavericks 10.9.2 had been installed and working for several weeks. I used a variation of Solution 1 to recover, as follows:

1. Plug in Unibeast USB flash drive and press computer power button.
2. At the (Gigabyte) BIOS splash screen press F12.
3. Scroll selection down to boot on the Unibeast USB drive.
4. When the Mac OS X installer opens, select "Utilities" from its menu.
5. Open "Disk Utility." Select the problem disk and click "Unmount."
6. Quit "Disk Utility" and open "Terminal."
7. Type the following in Terminal after its opening string:
dd if=/usr/standalone/i386/boot1h of=/dev/disk0s2
8. Quit Terminal. Quit the Mac OS X installer, power down and remove the USB flash drive.
9. Reboot normally on the (previously faulty) disk.

I fear this "Boot0" issue may happen periodically, since there was no warning before it happened.

nikko20040
i5 - 3570, h77n-wifi, 16GM, 3TB hitachi HD
Hi wstrohm,
Is the name of your HD something other than "standalone" and do you still use the name standalone.
thanks

 

[septendre]

I should have tried the solution 2 in the first place!!! Put my crucial m500 ssd in an external enclosure linked via USB to a working OsX, and the chameleon wizard installed a functioning boot0 on it. Replaced the ssd drive in my netbook, and voilà! It wold have spared me the trouble of repartitioning and reinstalling all my Os from scratch!

Thanks a lot from Quebec city!

 

[wstrohm]

@nikko20040,

Is the name of your HD something other than "standalone" and do you still use the name standalone. thanks

Yes, my HD's name is "Mavericks," and yes, I used "standalone" as shown in the command. You have to be careful to put spaces where shown, and nowhere else!

 

[dkavraal]

I have done it as far as I can tell the same. It says
"2+0 records in
2+0 records out
1024 bytes transferred in ....
However still getting the same message (boot0: error) single line.

edit:---

I have fixed it. I have opened Ubuntu on live cd/usb and run "sudo gdisk /dev/sda" and obey the directions here: (http://falstaff.agner.ch/2012/11/20/convert-mbr-partition-table-to-gpt-ubuntu/)

After that I was having bios partition anymore. Yet I had to reboot into MacOs with help of another bootable mac USB (chimera i.e.) and installed the chimera installer.

Now everything is smooth.

fyi.

 

[RadMatty]

So, I just started using SuperDuper! to make a clone of my boot drive, which happens to be a WD 4k block drive. My backup/clone drive is not a 4k drive. It will not boot the cloned copy of my main drive. I suspect that this is because the copy contains the 4k boot instructions I installed to correct my boot drive to repair the boot0 problem. How do I reconfigure the clone drive to delete the 4k block instruction? It's probably not a big deal, but I am not a terminal wizard at all. Thanks.

 

[P1LGRIM]

Article: boot0 Error: The Official Guide

So, I just started using SuperDuper! to make a clone of my boot drive, which happens to be a WD 4k block drive. My backup/clone drive is not a 4k drive. It will not boot the cloned copy of my main drive. I suspect that this is because the copy contains the 4k boot instructions I installed to correct my boot drive to repair the boot0 problem. How do I reconfigure the clone drive to delete the 4k block instruction? It's probably not a big deal, but I am not a terminal wizard at all. Thanks.

SuperDuper doesn't copy the boot loader to your clone - Run Multibeast with your clone as the target and install just Chimera or alternatively, run the standalone Chimera installer.

Good Luck