Jump to content
InsanelyMac Forum

fusion71au

Gurus
  • Content count

    888
  • Joined

  • Last visited

  • Days Won

    12

fusion71au last won the day on October 26 2017

fusion71au had the most liked content!

About fusion71au

  • Rank
    InsanelyMac Legend

Profile Information

  • Gender
    Male

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. fusion71au

    macOS High Sierra 10.13.4 (17E202) is out

    You can directly download 6 files from Apple's software catalog and assemble the Installer app yourself, bypassing the App Store altogether... Essentially, adding the "SharedSupport" files to the small 17.1MB "Install macOS High Sierra.app" (found in BaseSystem.dmg) creates the full Installer.app of 5.22GB (ver 13.4.09). Can confirm the shasum of BaseSystem.dmg and InstallESD.dmg of the 10.13.4 Installer (in "SharedSupport" folder) are as follows... fusion71aus-MacBook-Pro:~ fusion71au$ shasum /Applications/Install\ macOS\ High\ Sierra.app/Contents/SharedSupport/InstallESD.dmg 2c72b22a45ea8f5a80bee91db8aba96dae8310ea /Applications/Install macOS High Sierra.app/Contents/SharedSupport/InstallESD.dmg fusion71aus-MacBook-Pro:~ fusion71au$ shasum /Applications/Install\ macOS\ High\ Sierra.app/Contents/SharedSupport/BaseSystem.dmg 06fb280713ada5595a45eb221af0091b3c24f314 /Applications/Install macOS High Sierra.app/Contents/SharedSupport/BaseSystem.dmg
  2. fusion71au

    AppleHDA Patcher

  3. fusion71au

    macOS HighSierra 10.13.3 released

    SHA1 checksums of Apple's full installer apps can be found here. For 10.13.3 (17D47), fusion71aus-iMac:~ fusion71au$ shasum /Applications/Install\ macOS\ High\ Sierra.app/Contents/SharedSupport/InstallESD.dmg 726c7516fdbe33ae3f2384ba1ce7efcda4335776 /Applications/Install macOS High Sierra.app/Contents/SharedSupport/InstallESD.dmg fusion71aus-iMac:~ fusion71au$ shasum /Applications/Install\ macOS\ High\ Sierra.app/Contents/SharedSupport/BaseSystem.dmg d64fd8e6ca5287b80fd785a3a1a151da92b8369d /Applications/Install macOS High Sierra.app/Contents/SharedSupport/BaseSystem.dmg
  4. The latest commits for AptioFixPkg (jan 17 2018) seem to only build with nasm v2.13.02 in /usr/local/bin. If I use export NASM_PREFIX="~/src/opt/local/bin/", I now get a nasm build error during the build phase. The following steps worked for me to fix the build... 1) Delete the old ~/src/edk2/AptioFixPkg folder and reboot the computer. Clean the edk2 build environment by running Build_Clover.command option 3 (Update Clover + force edk2 update), then exit with option 11. 2) Install the attached nasm v2.13.02 in /usr/local/bin sudo cp ~/Downloads/nasm /usr/local/bin/ 3) Then run the following commands to build AptioMemoryFix.efi again... cd ~/src/edk2 git clone https://github.com/vit9696/AptioFixPkg.git git clone https://github.com/CupertinoNet/CupertinoModulePkg git clone https://github.com/CupertinoNet/EfiMiscPkg git clone https://github.com/CupertinoNet/EfiPkg source edksetup.sh make -C BaseTools touch edk2.ready build -a X64 -b RELEASE -t XCODE5 -p AptioFixPkg/AptioFixPkg.dsc ---> output binary files in ~/src/edk2/Build/AptioFixPkg/RELEASE_XCODE5/X64 4) Replace OsxAptioFix3Drv-64.efi in ~/src/edk2/Clover/CloverPackage/CloverV2/drivers-Off/drivers64UEFI with AptioMemoryFix.efi. Slightly modified @vit9696's build script (attached Build_AptioFixPkg.sh) so it uses existing ~/src/edk2 ---> output to ~/src/edk2/Clover/CloverPackage/CloverV2/drivers-Off/drivers64UEFI. Edit: Build_Clover.command v4.6.4 now automatically compiles AptioMemoryFix.efi when using XCODE5 toolchain. Thanks @Micky1979 and @Vit9696 . nasm.zip Compiled AptioFixPkg.zip Build_AptioFixPkg.sh.zip
  5. Just a request for Build_Clover.command to include an option to build AptioMemoryFix and include AptioMemoryFix.efi in /drivers64UEFI. At present, I manually build from terminal... cd ~/src/edk2 git clone https://github.com/vit9696/AptioFixPkg.git git clone https://github.com/CupertinoNet/CupertinoModulePkg git clone https://github.com/CupertinoNet/EfiMiscPkg git clone https://github.com/CupertinoNet/EfiPkg export NASM_PREFIX="~/src/opt/local/bin/" source edksetup.sh make -C BaseTools touch edk2.ready build -a X64 -b RELEASE -t XCODE5 -p AptioFixPkg/AptioFixPkg.dsc ---> outputs binary files in ~/src/edk2/Build/AptioFixPkg/RELEASE_XCODE5/X64. Thanks to all the devs involved
  6. fusion71au

    EFI_Clover for VMware

    Tested with unlocked Workstation 12.5 running OSX 10.9 -->10.13 guest in Windows X64 host. Need Donk's unlocker on non Mac hosts to allow creation of macOS guests.
  7. First, verify the SHA1 checksum of your InstallESD.dmg and BaseSystem.dmg with the correct ones at this website. Eg for "Install macOS High Sierra.app" 10.13.2_17C88, SHA1 in Terminal... fusion71aus-iMac:~ fusion71au$ shasum /Applications/Install\ macOS\ High\ Sierra.app/Contents/SharedSupport/InstallESD.dmg 49e336085247331ea6033ebd3598a827caa6596e /Applications/Install macOS High Sierra.app/Contents/SharedSupport/InstallESD.dmg fusion71aus-iMac:~ fusion71au$ shasum /Applications/Install\ macOS\ High\ Sierra.app/Contents/SharedSupport/BaseSystem.dmg 209d6a382026115a30c79f0825aec1b7a4cdb2dd /Applications/Install macOS High Sierra.app/Contents/SharedSupport/BaseSystem.dmg The OSInstall.mpkg error can sometimes be due to "stale data" in /macOS Install Data (time stamp/IAEndDate in OSInstallAttr.plist too old). Easiest to erase target drive and start again... If using VirtualBox, follow instructions exactly as per post#75. If using VMware, follow instructions as per post#41.
×