Boot0: Error 4k Hard Drive Fix for OSx86 Hackint0sh drives
The default block size on newer SSDs has changed from 512 bytes to 4,096 bytes, this has caused an explained issue in which the bootloader can not be written to a drive that’s active. There are many tutorials that help explain the issue but none advise anyone to flag the drive which is the reason I am writing this tutorial.
- Install as you would and acquire a bootloader.
- You need the boot1h from your specific bootloader, I can upload mine but you might use a specific revision of Chimera, Chameleon, or Enoch depending on your model, this can be found in the i386 folder if you extract the contents of the pkg file. (Hint: if you have a bootloader installed and aren’t sure what revision it is, you can find it’s boot1h file in %DRIVEROOT%/usr/standalone/i386/boot1h) You will also notice a boot0, boot1x, boot1hp, etc., for more information, read below, The other boot files.
Put the boot1h file on an accessible drive whether it be the OS X installer disk or another bootable Mac partition, or if you have a real Mac and can plug in your un-bootable drive to it, doesn’t really matter, installation disk is easiest so I’ll continue with that.
- Boot the installer, click next and then click Utilities and open Terminal.
run “diskutil list”, find the disk identifier for your un-bootable partition (in my case it’s /dev/disk0s2 and will continue with it), then run:
sudo dd if=/whereever/you/put/this/file/boot1h of=/dev/disk0s2
- If you get Resource Busy, this failed so open Disk Utility and unmount the broken-boot drive (this is why you can’t have the boot1h file on that drive)
- run command 6 again, it should complete successfully and show the bytes written, if it did not, please contact me with the error.
- This only writes the bootloader properly, we now need to flag the drive, run:
- sudo fdisk440 -e /dev/rdisk0 (referring to my disk again, yours might be different) then run these 1-letter commands:
- p (list partitions)
- f 2 (this will flag the 2nd partition, e.g. disk0s2 from above but you might have a different partition number)
- w (write)
- y (…yes)
- This should have properly written and flagged the bootloader, please read below especially about the Metro bootloader and let me know if this did not bring you success.
The other boot files:
Honestly I haven’t looked too much into this so I won’t start spewing out stuff I don’t know but from using Chameleon Wizard, we know that these boot files are used for:
boot0md – Used when 2 or more disk with Windows on the other disk than OS X
boot0 – One disk with OS X and Windows, or only OS X.
boot0hfs – One disk with OS X and Windows or just OS X.
boot1h – possibly alternate bootloader or backup?
boot1hp – ?
boot1x – ?
The various bootloader fix tutorials always recommend using boot1h and I remember reading many years ago that it was another bootfile alongside boot0 but don’t quote me on it. I have always used boot0 for step 6 for my Dell XPS L702x but the recommendation is to use boot1h, if you still weren’t able to boot with either, you can’t do too much damage from trying the other boot files, I can vogue for that as I’ve tried every one of those boot files and had different results, so consider that when you are facing an unbootable hackint0sh.
The Metro Bootloader in my experience has caused a lot of headaches, I usually install EasyBCD 2.2 and install the Windows 7 bootloader then rewrite the Windows boot options, in my dual-HDD & triple-boot scenario, this breaks my Windows boot until I install the chameleon (personally use enoch) bootloader which I know sounds scary but if Metro seems to take precedence over your flagged OS X partition, then this would be the best thing for you to try.