Jump to content
Welcome to InsanelyMac Forum

Register now to gain access to all of our features. Once registered and logged in, you will be able to contribute to this site by submitting your own content or replying to existing content. You'll be able to customize your profile, receive reputation points as a reward for submitting content, while also communicating with other members via your own private inbox, plus much more! This message will be removed once you have signed in.

High Sierra MBR and Firmware Check Patch 10.13.3

1 Screenshot

About This File

Patched OSInstaller.framework to allow macOS 10.13 installation on MBR partition.


To use those patched files you must follow HowTo-10.13.x to create an USB installer. You can't just run the app downloaded from Mac App Store.


The patch is made base on 落下爱@pcbeta 10.10.x MBR patch method, and more patch for 10.13 Firmware check by crazybidy.


What is this patched OSInstaller doing?

1. Patch the MBR check, allow macOS 10.13 installation on MBR partition.

2. Patch the Firmware check, bypass the error of "An error occurred while verifying firmware".

3. This patched MBR OSInstaller method works with both MBR and GPT partition (GPT+recovery).

No longer need to set new SMbiosversion, FirmwareFeatures, and FirmwareFeaturesMask with this MBR-patch.


If you want to install to GPT, but still get the error of "An error occurred while verifying firmware".

All you need to do is, boot the Disk1mbrInstaller, and it will automatically load to install the "GPT-partition/macOS Install Data" which you installed with "Install macOS High Sierra.app" of createinstallmedia installer method at first stage.


How to make 10.13 installer for MBR?

Read HowTo-10.13.x.txt inside the zip file first, different with 10.12.

Read HowTo Q/A Q7. How to install in different computer with only one USB partition?

Read HowTo Q/A Q8. How to update 10.13.x combo-update to MBR without downloading the full installer app again?

Read HowTo Q/A Q9. How to update 10.13.x combo-update to MBR and GPT with installScript directly?


And, need a /Extra/SMBIOS.plist supported with /System/Library/CoreServices/PlatformSupport.plist.

Set a SMBIOS with Chameleon Wizard.


Work fine with Clover r4084+.


Work fine with Enoch r2885+.

and /Extra/kernel.plist with















If you want to patch MBR by yourself, just read the HowToPatch-10.13.txt inside the zip file.







What's New in Version 10.13.3   See changelog


No changelog available for this version.

User Feedback

Recommended Comments

With this, we can now install using base method?

Not the old basesystem method,

the new OSInstaller removed the manual partition selection and keep only automated installation.


It's new basesystem MBR method to load stage2 disk with /MBR-partition/macOS Install Data/ to install to the target /MBR-partition/ automatically.

Share this comment

Link to comment
Share on other sites

Pretty awesome!!I just wanna know how to solve the problem of mouse/keyboard freezing when booting into the install screen using Chameleon?And it seems that the USB kexts r not working any more!!

Share this comment

Link to comment
Share on other sites

Hi buddy great work. I have an issue tho I boot up and installer error log shows up I have 2 portions named as described added my uuid of installdata copied base system ect to install data to and put the patched osinstall in osinstall.framework/xxx/xx so on can you tell me what I may have done wrong

Share this comment

Link to comment
Share on other sites
that's fine.


Tried to pm you says you can't get any messages so il write it here


Right ok so I don't need 2 portions just one e.g. I have a 8gb USB and vmwere I format USB as guid restore base system then make a packages folder in the same place as the old method and copy osinstalker.mpkg. From here copy the installdata folder of yours on root of USB then copy all shared support files in to installdata folder and adding the USB uuid as described in read me then in privateframwork add osinstall to Osinstall.framework is that correct. Sorry for being a pain iv just been over the read me over and over but I boot the USB and at setup screen well what should be setup screen just a restart option and a error log

Share this comment

Link to comment
Share on other sites



I successfully upgraded DB6 to DB7 with my original DB6 Disk1mbrInstaller.  Only needed to replace OSInstall.mpkg from DB6/17A344b with OSInstall.mpkg from DB7/17A352a in /Disk1mbrInstaller/System/Installation/Packages folder.


Steps to upgrade install:

1) Directly run DB7 "Install macOS High Sierra Beta.app", targeting the desired HFS+ or APFS installation partition --> automatically creates "macOS Install Data" folder on that volume

2) At first restart, boot to Disk1mbrInstaller ---> choose language ---> files from install packages written to disk

3) At second restart, boot to fully upgraded High Sierra partition :)

Share this comment

Link to comment
Share on other sites

Like mentioned above, I've now upgraded DB7 to DB8 with my original DB6 Disk1mbrInstaller. - only needed to replace OSInstall.mpkg in  /Disk1mbrInstaller/System/Installation/Packages to the new one from DB8/17A358a. 


Also when prepared with the full /S/L/E folder from "Core.pkg" (see post#3239 & 

How to create a macOS Installer which doesn't need bootloader kext injection (FakeSMC in pre-linked kernel), bypass High Sierra firmware and MBR check), I noticed my USB mouse is fully functional and I can access the installer menu items at the top (unlike when you boot to "macOS Install" in a mackintosh).


Update Sep 26 2017:  Upgraded to High Sierra 10.13.0 Release 17A365 with OSInstall.mpkg in /Disk1mbrInstaller/System/Installation/Packages

of DB9 Disk1mbrInstaller  :).

Share this comment

Link to comment
Share on other sites

Are you creating 2 partitions on the target Hard Drive, or on the USB pen drive??

Sorry, but the english directions are not clear.


1. Create a bootable USB installation drive.

2. On the target HDD create 2 partitions... OR on the bootable USB create 2 partitions?? 


Not clear... are you creating a USB drive that is then patched and modified so that you install it to the target HDD?


are you copying files from the USB drive to the target HDD which now has 2 partitions and then once modified boot from the target HDD???



Share this comment

Link to comment
Share on other sites

Let me get this correct

Where it says "you need 2 partitions - one for A.Disk1mbrInstaller,  size 2.5Gb... this is on the USB?

and then B.Disk2Install Data... 25 Gb minimum....


1. I already created a USB drive and have the OS installer.app on there....

SO then...

are the 2 partitions A and B for the target HDD?




should I wipe the USB and then put A on it and B on the target HDD????


IF A &B are on the target HDD then you just install your boot loader and run it??

Share this comment

Link to comment
Share on other sites

Can someone clarify in English:

OSInstaller replace to /Volumes/Disk1mbrInstaller/System/Library/Privateframeworks/OSInstaller.framework/Version/A/OSinstaller


Is this meaning - copy  System/Library/Privateframeworks etc from Basesystem.dmg to DISK1MBRINSTALLER????

Share this comment

Link to comment
Share on other sites

Ok Crazybirdy thank you.

I installed on usb drive, and on hdd creating per your instructions...

Using Enoch2902, and the Installer (first one from release day, not subsequent update installer) & Nvidia 720 vid card, i5 processor 2300 MHz (6 year old machine)... have used this since snow leopard, ok ... so has old bios etc.


followed steps and also A4 A5 to get it to boot.


The system boots up and starts to load ok, then hangs with a 

local host com apple xlc launchd messages ..then hangs with


IOConsoleUsers: gIOScreenLockState 3, hs 0, bs 0, nov 0, sm 0x0


 Video card nv_disable=1 does not help ... removing all video card kext does not help...

Any suggestions as to cause?

Share this comment

Link to comment
Share on other sites

System starts booting, but then 

complains can't find  /Library/LaunchAgents...


I have S/L/Launch agents copied over from .dmg as per instructions...


If I copy S/L/Launchagents to /Library   then it complains about duplicates..!


Can you post picture of what the file structure should look like??  

Share this comment

Link to comment
Share on other sites