Jump to content

fusion71au

Gurus
  • Content Count

    959
  • Joined

  • Last visited

  • Days Won

    13

Everything posted by fusion71au

  1. fusion71au

    [pre-release] macOS Mojave 10.14.4

    Just tested booting into 10.14.4 beta/18E174f macOS Base System on my legacy machines (waiting to download full installer with 10.14.4 official release). On my legacy Dell laptop (Geforce 8600M GT/tesla) using MBP7,1 SMBIOS and -no_compat_check boot flag, had same error as @macq - hang on message ioconsoleUsers: gIOScreenLockState 3, hs 0, bs 0, now 0, sm 0x0 after DSMOS arrives. Note I have full install of 10.14.3 on this system working OK with High Sierra tesla graphics kexts. Changing to 10.14.3 prelinked kernel in /System/Library/PrelinkedKernels ---> same system hang message ie swapping to PLK with 10.14.3 graphics kexts doesn't help in my case Changing to MacPro5,1 SMBIOS and inject NVidia to no in config.plist ---> boots OK to Recovery/Installer environment with VESA graphics Maybe with this latest beta, more stringent checking of systems with deprecated SMBIOS + non metal graphics? MacPro5,1 SMBIOS also works booting 10.14.4 beta/18E174f macOS Base System on my legacy desktop (Desktop 2 in signature with ATI HD5770) with VESA graphics.
  2. Making a High Sierra USB Installer Entirely From Scratch in Windows This is a proof of concept tutorial, to show it's possible to create a vanilla High Sierra installer, entirely from scratch, in Windows (even without App Store downloaded "Install macOS High Sierra.app" from a real Mac ). @PikeRAlpha's link to Apple's Software Catalog provides us with all the URLs necessary to download the needed files directly from Apple instead of some dubious source from the internet... Pre-Requisites 8GB or larger USB drive Boot Disk Utility v2.1.2017rev021b from @CVAD TransMac (free 15 day trial) Paragon Hard Disk Manager Free Download Installer Files Directly from Apple 1) Browse Apple's Regular Software Catalog and find the URLs to download the following 6 installer files... BaseSystem.dmg BaseSystem.chunklist InstallInfo.plist InstallESDDmg.pkg AppleDiagnostics.dmg AppleDiagnostics.chunklist (Hint - search page for "InstallESD" to find its URL and others nearby) to a folder named "SharedSupport" on your Windows NTFS drive. A browser download manager (eg Chrono for Chrome, dTA for FireFox) is handy since InstallESD is >4GB ---> allows you to pause/resume interrupted download... 2) Rename InstallESDDmg.pkg to InstallESD.dmg 3) Edit InstallInfo.plist with WordPad/text editor to remove the chunklistURL and chunklistid keys for InstallESD, and renaming it from InstallESDDmg.pkg to InstallESD.dmg (example of edited file attached to this post)... Note: You can verify the SHA1 checksum of your InstallESD.dmg and BaseSystem.dmg with the correct ones at this website. Boot Disk Utility to format the Installer USB and Restore OS X Base System HFS partition 1. Format USB with BDU & latest Clover ---> creates boot files in CLOVER partition + second FAT partition 2. Extract 4.hfs from \SharedSupport\BaseSystem.dmg with BDU --> save to it's local folder 3. Restore 4.hfs to USB second partition with BDU ---> 2nd partition becomes bootable "OS X Base System" Paragon Hard Disk Manager to extend HFS Partition to its Full Extent Open Paragon Partition Manager Free and resize the second partition of the USB drive to the full size allowed. Don't forget to apply the changes at the end... Transmac to Copy "SharedSupport" folder to OS X Base System 1. Open the TransMac program and navigate to the HFS+ Volume/Install macOS High Sierra.app/Contents folder. Right click anywhere in the empty space on the RHS pane and select "Copy Here"... 2. In the next stage, select the "SharedSupport" folder we created above as the "Files and Folders to be copied to the Mac Volume"... Clover Settings Clover configuration is required now. The default config.plist (in the Clover FAT32 partition of the USB) maybe sufficient to boot your machine if you’re lucky. If not, look at the Clover Wiki, Clover Instructions and Clover Configuration Thread for pointers and edit /EFI/Clover/config.plist accordingly with Wordpad or Notepad. The location of the important configuration files for Clover are summarized below config.plist--->EFI/CLOVER folder DSDT.aml with or without SSDT.aml--->EFI/CLOVER/ACPI/patched (don't need one if your DSDT is auto patched by Clover in config.plist) Kexts eg FakeSMC, NullCPUPowerManagement --->EFI/CLOVER/kexts/<osx version> or /Other. NB BootDiskUtility by default already has FakeSMC.kext installed here. You may need to add VoodooPS2Controller for your laptop keyboard/trackpad to work. If UEFI booting, you will most likely need one of the OsxAptioFixDrv-64 drivers copied from /EFI/CLOVER/drivers-off/drivers64UEFI to /EFI/CLOVER/drivers64UEFI. If you want to use the installer to run High Sierra in Windows on VMware, you can follow my guide to set up the Virtual Machine and replace Clover's default config with EFI_Clover for VMware (which is compatible to run in VMware). In the screenshots below, I have attached the USB Installer (in this case PhysicalDrive7) to my macOS Virtual Machine. Reboot the system to the USB installer to install High Sierra ... What happens if we don't have access to TransMac or Paragon Hard Disk Manager? Not a problem, as long as we get "OS X Base System" bootable, we can launch terminal from the Utilities Menu to copy the SharedSupport folder over to the Installer app. In essence, we will build the full installer app = 5GB+ on the target HD eg "Macintosh HD", by copying both the "small" installer app = 15MB (on "OS X Base System") and the SharedSupport folder from the NTFS volume (mounted in this example on /Volumes/DATA)... -bash-3.2# cd / -bash-3.2# cp -R Install\ macOS\ High\ Sierra.app /Volumes/Macintosh\ HD/ -bash-3.2# cp -R /Volumes/DATA/SharedSupport /Volumes/Macintosh\ HD/Install\ macOS\ High\ Sierra.app/Contents/ ...then start installation with the startosinstall utility... -bash-3.2# /Volumes/Macintosh\ HD/Install\ macOS\ High\ Sierra.app/Contents/Resources/startosinstall --volume /Volumes/Macintosh\ HD --converttoapfs NO --applicationpath /Volumes/Macintosh\ HD/Install\ macOS\ High\ Sierra.app The above steps can be automated with the attached "startosinstall.command" script, which will assemble "Install macOS High Sierra.app" on "Macintosh HD" and launch the startosinstall utility targeting the "Macintosh HD" volume. Copy/download to "Macintosh HD", then run in terminal (after attaching DATA USB with /Shared Support folder)... cd "/Volumes/Macintosh HD" chmod +x startosinstall.command ./startosinstall.command Updated Download Links for macOS Mojave 10.14.3_18D42 Browse Apple's Regular Software Catalog and find the URLs to download the following 6 installer files... BaseSystem.dmg BaseSystem.chunklist InstallInfo.plist InstallESDDmg.pkg AppleDiagnostics.dmg AppleDiagnostics.chunklist Note: In Mojave, Apple has removed the --converttoapfs NO and --applicationpath arguments from the startosinstall utility.... eg to use startosinstall for the above section "What happens if we don't have access to TransMac or Paragon Hard Disk Manager?", the syntax is now -bash-3.2# /Volumes/Macintosh\ HD/Install\ macOS\ Mojave.app/Contents/Resources/startosinstall --volume /Volumes/Macintosh\ HD This basically means that for Mojave, the default installation will always convert the target volume to the apfs file system. startosinstall.command.zip InstallInfo.plist_edited_10.13.6.zip InstallInfo.plist_edited_10.14.2.zip InstallInfo.plist_edited_10.14.3.zip
  3. fusion71au

    AppleAHCIPort.kext

    Version v328

    3,051 downloads

    AppleAHCIPort.kext v328 from High Sierra PB1_17A291m. Info.plist has been edited so Bundle version is 999.1.1 ---> give higher priority loading in kernel cache/pre-linked kernel than v329 from later betas/GM. Need to disable SIP (since editing info.plist invalidates Apple's kext signature). Install in /Library/Extensions (so doesn't get over-written during updates) repair permissions, rebuild caches eg sudo chown -R 0:0 /Library/Extensions/AppleAHCIPort.kext && sudo chmod -R 755 /Library/Extensions/AppleAHCIPort.kext sudo touch /System/Library/Extensions && sudo kextcache -u / Test kext is loadable... sudo kextutil -tn /Library/Extensions/AppleAHCIPort.kext Confirm kext is loaded after rebooting the system... kextstat | grep AHCIPort To use with a USB installer, the kext needs to be included in the prelinkedkernel. Use PLK.tool attached to post#13 to create a new prelinkedkernel with AppleAHCIPort.kext v328, then replace original prelinkedkernel in the installer - post#16.
  4. Create Custom Entries to Hide Preboot and Recovery APFS Volumes with Clover Configurator With the release of High Sierra and the APFS file system, Clover users now have "extra" entries appearing in their Main Menu - Preboot and Recovery APFS volumes. While they are harmless and actually useful in certain circumstances (eg need Preboot to boot if using File Vault encryption, need Recovery to fix some file system problems), most users will likely want to hide them in day to day use. Note: This guide is tailored to those users who want to understand how to create custom APFS entries and the "nuts and bolts" of how Clover parses the file system looking for efi loader entries. If all you want to do is hide entries, the easiest way is through the GUI/Hide section of the config.plist. This won't allow you to rename custom entries, nor unhide them with the <F3> key (at least not till Clover r4247). Pre-requisites macOS High Sierra installed on APFS SSD or HDD Clover r4097+ with apfs.efi installed in /EFI/CLOVER/drivers64UEFI or /EFI/CLOVER/drivers64 Clover Configurator v 4.49.0.0 or later Procedure 1. Record output of "diskutil list" and "diskutil apfs list" to determine the layout of the actual physical disk(s) and the synthesized APFS container. In my example, the High Sierra Volume is named macOS_HS and is installed in physical disk partition disk3s4. fusion71aus-iMac:~ fusion71au$ diskutil list /dev/disk3 (internal, physical): #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme *1.0 TB disk3 1: EFI EFI 209.7 MB disk3s1 2: Microsoft Basic Data DATA 935.6 GB disk3s2 3: Microsoft Reserved 134.2 MB disk3s3 4: Apple_APFS Container disk4 63.6 GB disk3s4 5: Apple_KernelCoreDump 655.4 MB disk3s5 /dev/disk4 (synthesized): #: TYPE NAME SIZE IDENTIFIER 0: APFS Container Scheme - +63.6 GB disk4 Physical Store disk3s4 1: APFS Volume macOS_HS 34.3 GB disk4s1 2: APFS Volume Preboot 20.9 MB disk4s2 3: APFS Volume Recovery 519.6 MB disk4s3 4: APFS Volume VM 20.5 KB disk4s4 2. Generate Clover Boot Log with terminal bdmesg > ~/Documents/bootlog.txt Note: for easier analysis of boot log, please remove all Custom/Hidden Entries from config.plist/GUI first (leaving only Clover auto scanning) before generating it. 3. Open bootlog.txt with a text editor and under the [ ScanLoader ] section, note the volume numbers corresponding to the Preboot, High Sierra and Recovery APFS volumes... Preboot Volume ---> 24 High Sierra Volume ---> 25 Recovery Volume ---> 26 4. Under [ ScanVolumes ] section, record the UUIDs of the above 3 Volumes In this example Vol 24 = Preboot: E38C70C3-C1C1-4096-B2DE-2EE2660FCE41,0x6CF46800,0x7687D88)\VenMedia(BE74FCF7-0B7C-49F3-9147-01F4042E6842,050BA2A72D1D0E4D8ABDE9B99632868E Partition UUID = E38C70C3-C1C1-4096-B2DE-2EE2660FCE41 Vol UUID = 050BA2A72D1D0E4D8ABDE9B99632868E (little endian format) Vol 25 = macOS_HS: E38C70C3-C1C1-4096-B2DE-2EE2660FCE41,0x6CF46800,0x7687D88)\VenMedia(BE74FCF7-0B7C-49F3-9147-01F4042E6842,67B6FC62811C594E819DACAE2F90240D Partition UUID = E38C70C3-C1C1-4096-B2DE-2EE2660FCE41 Vol UUID = 67B6FC62-811C-594E-819D-ACAE2F90240D (little endian format), 62FCB667-1C81-4E59-819D-ACAE2F90240D (big endian format) Vol 26 = Recovery: E38C70C3-C1C1-4096-B2DE-2EE2660FCE41,0x6CF46800,0x7687D88)\VenMedia(BE74FCF7-0B7C-49F3-9147-01F4042E6842,F3D73FFF25C8334DAF3C183BC35433DF Partition UUID = E38C70C3-C1C1-4096-B2DE-2EE2660FCE41 Vol UUID = F3D73FFF25C8334DAF3C183BC35433DF (little endian format) Note the partition UUIDs for all the APFS volumes are the same because they are all formed from the same physical disk partition disk3s4 = E38C70C3-C1C1-4096-B2DE-2EE2660FCE41 5. Mount the APFS Volumes to determine the "path" to boot.efi for the Preboot and Recovery Volumes. In terminal: fusion71aus-iMac:~ fusion71au$ diskutil mount disk4s2 Volume Preboot on disk4s2 mounted fusion71aus-iMac:~ fusion71au$ diskutil mount disk4s3 Volume Recovery on disk4s3 mounted fusion71aus-iMac:~ fusion71au$ open /Volumes In Finder, the hidden folder /Volumes will open (or use "ShowAllFiles.app" attached)... Record the "path to boot.efi" by expanding the directory tree of Preboot and Recovery (hint: drag the icon of boot.efi to a terminal window for full path): So for Preboot Volume, path = /Volumes/Preboot/62FCB667-1C81-4E59-819D-ACAE2F90240D/System/Library/CoreServices/boot.efi --> record as \62FCB667-1C81-4E59-819D-ACAE2F90240D\System\Library\CoreServices\boot.efi and for Recovery Volume, path = /Volumes/Recovery/62FCB667-1C81-4E59-819D-ACAE2F90240D/boot.efi ---> record as \62FCB667-1C81-4E59-819D-ACAE2F90240D\boot.efi Notes Need backslashes in the path, including the leading \ The UUID in the paths to boot.efi, for both the Preboot and Recovery APFS volumes, is the same = Vol UUID of the High Sierra Volume in big endian format... 6. Open Clover Configurator, mount EFI System Partition to edit /Volumes/EFI/EFI/CLOVER/config.plist 7. Click GUI section on LHS and the + sign under Custom Entries to create New Custom Entry 8. Create Preboot High Sierra Custom Entry In Volume, copy and paste Vol UUID of Preboot Volume from step 4 In Path, copy and paste path to boot.efi from step 5, including the leading \ Click Title/FullTitle and enter the display name you want eg "Preboot High Sierra" Set Injectkexts and Hidden attributes to Yes Set Entry type to OSX Leave VolumeType blank 9. Create APFS Recovery Custom Entry In Volume, copy and paste Vol UUID of Recovery APFS Volume from step 4 In Path, copy and paste path to boot.efi from step 5, including the leading \ Click Title/FullTitle and enter the display name you want eg "APFS Recovery" Set Injectkexts and Hidden attributes to Yes Set Entry type to OSXRecovery Leave VolumeType blank 10. Save config.plist and reboot the system. At the main Clover Menu, you should see something like this ... To unhide the custom APFS entries, press the F3 key Update: New "macOS Install Prebooter" Entry with Clover r4225+ Clover r4225+ has added new code to detect OS X installer data on the Preboot Volume ---> causes an extra entry at the Clover Main Menu: "Boot macOS Install Prebooter from Preboot"... If you mount your Preboot volume, you will see ... Method for hiding the new entry would be similar to hiding the Preboot Entry discussed above: In Volume, copy and paste Vol UUID of Preboot Volume from step 4 In Path, copy and paste path to boot.efi from step 5, including the leading \ (eg \UUID\com.apple.installer\boot.efi ) Click Title/FullTitle and enter the display name you want eg "High Sierra Install Prebooter" Set Injectkexts and Hidden attributes to Yes Set Entry type to OSXInstaller Leave VolumeType blank Custom Entry for Fusion Drive Installation of Sierra or High Sierra - post#22. sample_config.plist.zip apfs.efi.zip ShowAllFiles.app.zip Clover_v2.4k_r4220.zip
  5. fusion71au

    Disk Utility (patched_v2)

    Version 10.10.5

    15,403 downloads

    Disk Utility from Yosemite 10.10.5 (ver 13 (606)) patched to run on El Capitan. Note: After you have downloaded and unzipped the file, you need to let root:wheel take ownership of the app before the app will run... sudo chown -R 0:0 ~/Downloads/Disk\ Utility.app v1 Patching procedure from Restore old Disk Utility in OS X El Capitan, credit @Justus Beyer v2 Patched with patch pattern from diskUtilityPatch, credit @dimosgmx Debug menu can be enabled with defaults write com.apple.DiskUtility DUDebugMenuEnabled 1 Advanced image verification options unlocked with defaults write com.apple.DiskUtility advanced-image-options 1 To turn off the above options, use the same commands in terminal but type 0 instead of 1.
  6. fusion71au

    macOS Mojave on Legacy PC ? Yes we can

    I successfully updated from 10.14.1 to 10.14.2 on my Mojave HFS partition by creating a full installer USB ---> in place upgrade installation. This avoided the missing frameworks/app opening problems associated with the updater script discussed above... * Can use either @dosdude1's macOS Mojave patcher tool or @crazybirdy's MBR-EasyInstallerMaker script to make USB installer from full 10.14.2 app * Boot system to USB installer and target the 10.14.1 partition to perform upgrade install * After upgrade completes, boot system to Mojave in single user mode to patch/replace com.apple.telemetry.plugin (eg with mojave2core script). Can also replace legacy kexts from High Sierra if overwritten by update eg in single user mode, type the following commands followed by <Enter> after each line ... fsck -fy mount -uw / /usr/bin/mojave2core cp -R /Volumes/USB/Kexts/* /System/Library/Extensions //Assuming you put legacy NVidia/other needed kexts in "Kexts" folder on your USB touch /System/Library/Extensions && kextcache -u / reboot
  7. fusion71au

    EFI_Clover for VMware

    Version r4799

    1,317 downloads

    Clover r4799 ISO compiled with GCC and minimal config.plist compatible for use in VMWare Workstation. Tested with unlocked Workstation 15 running OSX 10.9 -->10.14 guest in Windows X64 host. Installation 1. Download and unzip "EFI_Clover_r4799 for VMware.zip". Mount Clover-v2.4k-4799-X64 by double clicking on it. 2. Mount your VM's EFI System Partition eg in terminal sudo diskutil mount disk0s1 3. Copy EFI folder from step 1 into the EFI partition 4. Shutdown the VM, add bios.bootDelay = "3000" to your VM's vmx file 5. Reboot your VM, press <F2> to access the VMware Boot Manager and add CLOVERX64.efi to the boot menu. Substitute your own unique and valid MLB and ROM variables in the /EFI/CLOVER/config.plist (Rt Variables section) to activate iMessage/Facetime on your VM.
  8. fusion71au

    Clover General discussion

    Attached Clover r4784 compiled with XCODE 8.2.1 in 10.11.6: Clover_v2.4k_r4784.zip Alternatively, you can use GCC instead of XCODE to build Clover eg if you use the Build_Clover.command script, edit the BuildCloverConfig.txt file like below... GNU=GCC53 Build_Tool=GNU Unfortunately, this expertise is beyond my pay grade...calling @Zenith432 for help? Disabled optimization during compilation with -O0 flag in tools_def.txt still results in bad boot6,7 using XCODE 10.1. Looks like new rules for XCODE10 will be required...
  9. fusion71au

    Clover General discussion

    I believe compilation with XCODE 10.1 is the problem. From your debug log, you are compiling Clover with XCODE 10.1 (with toolchain set to XCODE8) on your system... Build with: [Args: -mc --no-usb -D NO_GRUB_DRIVERS_EMBEDDED -t XCODE8 | -D DISABLE_USB_SUPPORT -D NO_GRUB_DRIVERS_EMBEDDED --conf=/Users/pkovacs/src/edk2/Conf -D USE_BIOS_BLOCKIO -D USE_LOW_EBDA -a X64 -b RELEASE -t XCODE8 -n 9 | OS: 10.13.6 | XCODE: 10.1] I already mentioned in this post that other XCODE versions eg 8.2.1, 8.3.3, 9.2, or GCC5.3, generate working boot6 and boot7 for my legacy desktop (system 2 in signature) but not XCODE 10.1 ---> boot hanging on stuck underscore "_" symbol. Also interesting to note that the officially released Clover r4741 was compiled with XCODE 8.3.3 but r4769 (which also fails for your system) with XCODE 10.1. No, still bad boot6,7 if Clover r4760 compiled with XCODE 10.1 (toolchain set to XCODE8, edk2 r27956). I think the problem/bug is intrinsic to XCODE 10.1.
  10. Yes, you are correct. Apple removed the URLs for 10.14_18A391 from the software catalog and replaced them with URLs for 10.14.1_18B75. I just hadn't gotten around to updating the links for 10.14.1 in the first post . Yes, you need the partition number of the hfs BaseSystem image for the next step... sudo dmg2img -v -i BaseSystem.dmg -p 4 -o /dev/sdb3
  11. fusion71au

    Clover General discussion

    @Slice, Notice that commit r4761 includes a change to Variable.c in /Patches_for_UDK2018/MdeModulePkg/Universal/Variable/RuntimeDxe/ ... Also noticed that official Clover r4769 was compiled with XCODE 10.1 (with tool chain set to XCODE8) but r4741 was compiled with XCODE 8.3.3 ---> successful boot... 6:891 0:000 Starting Clover revision: 4741 on CLOVER EFI 6:891 0:000 Build with: [Args: -D NO_GRUB_DRIVERS_EMBEDDED -t XCODE8 | -D NO_GRUB_DRIVERS_EMBEDDED -D USE_LOW_EBDA -a X64 -b RELEASE -t XCODE8 -n 5 | OS: 10.12.6 | XCODE: 8.3.3] Edit Further to XCODE 10.1 being the problem, my legacy desktop boots fine with Clover r4772 compiled with XCODE 8.2.1 or XCODE 9.2 (both with tool chain set to XCODE8).... 6:897 0:000 Starting Clover revision: 4772 on CLOVER EFI 6:897 0:000 Build with: [Args: -mc --no-usb -D NO_GRUB_DRIVERS_EMBEDDED -t XCODE8 | -D DISABLE_USB_SUPPORT -D NO_GRUB_DRIVERS_EMBEDDED --conf=/Users/fusion71au/src/edk2/Conf -D USE_BIOS_BLOCKIO -D USE_LOW_EBDA -a X64 -b RELEASE -t XCODE8 -n 3 | OS: 10.11.6 | XCODE: 8.2.1] 6:911 0:000 Starting Clover revision: 4772 on CLOVER EFI 6:911 0:000 Build with: [Args: -mc --no-usb -D NO_GRUB_DRIVERS_EMBEDDED -D USE_APPLE_HFSPLUS_DRIVER -t XCODE8 | -D DISABLE_USB_SUPPORT -D NO_GRUB_DRIVERS_EMBEDDED --conf=/Users/fusion71au/src/edk2/Conf -D USE_BIOS_BLOCKIO -D USE_LOW_EBDA -a X64 -b RELEASE -t XCODE8 -n 5 | OS: 10.13.6 | XCODE: 9.2] If I swap out the boot6 "boot" file with one compiled with XCODE 10.1, the boot hangs ---> after seeing "6" on the screen, it stops at an underscore symbol "_" and no GUI appears.
  12. fusion71au

    Clover General discussion

    Try replacing just the "boot" file with the one attached, compiled with GCC53. I have also attached Clover_v2.4k_r4772 package installer compiled with GCC53... I noticed that for the latest officially released Clover r4769 from Sourceforge, the boot process would hang on my legacy desktop after seeing "6" on the screen. It seems that CloverEFI (the boot6/boot7 "boot" file) compiled with XCODE 10.1 fails to chainload CLOVERX64.efi but CloverEFI compiled with GCC53 works OK. Bug possibly due to latest edk2 28338 sync with commit r4761? Clover_v2.4k_r4772.pkg.zip boot.zip
  13. For those wanting to try Windows 10, I thought I would create a short guide on how to create a Clover/UEFI Windows 10 installer with Rufus and clean install. This guide is tailored for legacy BIOS machines but should also work in systems with native UEFI firmware. Prerequisites 1. Access to OSX and Windows to run Rufus and install Clover 2. Install Rufus: Download from here 3. Download the Windows 10 insider preview ISO (build 10074) from here. Edit 29/7/15 RTM build 10240 available!: Download MediaCreationTool. Making the UEFI Windows Installer 1. In Windows, Insert a 4GB or larger USB and start Rufus with the following settings Partition scheme and target system device = MBR for UEFI computer File System FAT32 2. Click the “Create a bootable disk using ISO image” checkbox and the CDROM icon to browse/choose your downloaded ISO 3. Click Start & OK to burn the image to the USB. Notice the USB takes on the name of the original ISO. 4. After the image has been burned to the USB, copy bootx64.efi from the /efi/boot folder of the Windows ISO/DVD into /efi/microsoft/boot. Rename the file to "bootmgfw.efi" and also rename cdboot.efi to cdboot.bak. For Windows 7, you need to extract bootmgfw.efi from "install.wim" eg using 7-Zip, open the iso and navigate to \sources\install.wim\1\Windows\Boot\EFI\bootmgfw.efi and copy to efi\microsoft\boot on the USB. Installing Legacy Clover (for legacy BIOS machines to boot the installer in UEFI mode) 1. Install Clover onto the USB drive (in OSX) with the “use alternative booting PBR” option ticked as shown below. Note - you can also install legacy Clover onto the USB in Windows using the Bootice program - see post#23 2. Copy the config.plist, DSDT/SSDT.aml file(s) which are specific to your system into the Clover folder - Put config.plist in /EFI/CLOVER directory
 - Put DSDT.aml in /EFI/CLOVER/ACPI/patched - Put FakeSMC.kext and other kexts required in EFI/CLOVER/kexts/10.x (where x is your version of OSX) Installation of Windows 10 1. Create free space on the target hard drive for Windows 10. This can be done in OSX using Disk Utility or in Windows with Disk Management/Diskpart.exe. 2. It is recommended to temporarily disconnect all hard drives except the target hard drive when installing or updating Windows 10. 3. Boot the computer with the Installer USB, pressing <F12> (or whatever your system’s BIOS boot selection key is) to choose the USB and then pressing the number <6> key when you see Clover’s flashing underscore 4. At the Clover Main Menu, choose “Boot Microsoft EFI boot menu from your_USB_name” ---> start the Windows 10 installer GUI 5. Follow the rest of the steps in this guide - http://www.tenforums.com/tutorials/1950-windows-10-clean-install.html Notes Choose the “Custom: Install Windows only (advanced)” option and just select the Unallocated Space for the installation —> the correct partitions will be automatically set up At the first reboot, boot to the USB again but at the Clover Main Menu, select “Boot Microsoft EFI boot menu from EFI” As the final step, don’t forget to install Clover on the hard drive . Major version upgrades through Windows Update (as opposed to a clean install) may overwrite the bootsector so legacy Clover might need to be re-installed. I recommend clean installing instead of letting Windows update perform an upgrade. If you run Windows 10 or 8 with Windows 7, you should turn off "Windows Hybrid Boot" to avoid chkdsk running every time you change from booting Windows 8/10 to Windows 7. Chameleon/Clover Emergency Boot Disk As an added bonus, by adding the attached Chameleon boot file to the root of the USB, you can use the installer as an emergency boot disk for Clover or Chameleon: Set your BIOS to boot first from USB ---> when you see the flashing underscore, press <1> to boot with Chameleon or <6> to boot with Clover . Chameleon v2737_boot1.zip Chameleon v2795_boot1.zip
  14. Yes, after installing High Sierra graphics kexts and patched GeForceTesla.kext as described before in this post... Process of install and post install patching can be automated with @dosdude's macOS Mojave Patcher.
  15. Run Vanilla OS X El Capitan, Sierra, High Sierra or Mojave in VirtualBox 5.x.x on a Windows Host Following on from my previous guide on how to create a VMware virtual machine running Vanilla OS X El Capitan in Windows, I’ve decided to write a similar guide for creating a VirtualBox El Capitan VM. The virtual machine should be useful for testing El Capitan and also for creating installers for use on a real machine/hackintosh. There are other tutorials and videos on the net about running OS X on Windows machines using pre-made VMDK disk images but you can never guarantee what else is in there…. I’ve gathered info for this guide from several threads in the Multibooting and Virtualisation section of this forum and also the wider internet eg @colt2 HOW TO: Create a bootable El Capitan ISO for VMware @dsmccombs comment on faking Ivybridge Processor @E:V:A http://forum.xda-developers.com/showpost.php?p=55572430&postcount=6 @Tech Reviews video tutorial https://www.youtube.com/watch?v=t7X07U63lwg. VirtualBox Forum: Status of OSX on OSX Requirements Intel PC with four or more CPU cores running Windows 7 X64 or later OS (2 or more cores needed for OS X) 4GB or more RAM (2GB or more will be needed for OS X) Hard Disk with at least 40GB free for Virtual Machine Oracle VM VirtualBox v 5.0.34 Install OS X El Capitan app and Mac or Hack to prepare installation iso <-- Now, no longer necessary to have previous access to a Mac or Hack by building the Installer.app from scratch - see post#75 16GB or larger exFAT formatted USB stick to transfer El Capitan iso from Mac/Hack to Host PC Prepare Installation ISO on your Mac or Hack 1. On your Mac or Hack, download "Install OS X El Capitan.app" from the App Store into your Applications folder. 2. Download and unzip the CECI.tool (attached to this post) into your ~/Downloads folder. The commands in this executable script are shown below for informational purposes. Note: you will need approx 16GB of free space on your hard disk for the script to complete. 3. Open OS X terminal, then run the following commands to execute the script: cd downloads chmod +x CECI.tool ./CECI.tool 4. At the end of the process, you will have an El Capitan iso on your desktop - copy this onto an exFAT formatted USB for use on the PC Host later. Create an El Capitan Virtual Machine in VirtualBox 1. Open the VirtualBox program and click the "New" button to create a new VM. 2. Select Mac OS X and Mac OS X 10.11 El Capitan (64 -bit) for Operating System type and version. I named my Virtual Machine "El_Capitan", then clicked next... 3. Leave the Memory size at the recommended 2048 MB, then click next. 4. Choose to "Create a virtual hard disk now", then click the create button. 5. For the hard disk file type, the default is VDI (VirtualBox Disk Image) but I have selected VMDK for inter-operability with VMWare. Click next... 6. For Storage on physical hard disk, I have chosen the default Dynamically allocated (grows larger to a set limit as you need more disk space). 7. On the File location and size screen, you can set the location of the new virtual hard disk and its size - I recommend changing disk size to 40GB or larger. When you click the create button, you will now see your new VM in the VirtualBox main GUI. 8. Click the settings button on the Main Menu to tweak a few settings.... a. On the System/Motherboard tab in Boot Order, you can uncheck the Floppy Drive (who has these now?) b. On the System/Processor tab, you can increase the allocated CPU cores to 2 c. On the Display tab, you can increase the allocated Video Memory to 128MB d. On the Storage tab, click on the icon of the Optical Drive and select "Choose Virtual Optical Disk File". Navigate and select the El Capitan ISO we created earlier... e. Click the OK button to finalise the VM settings. Patch El Capitan vbox configuration file with DMI Settings from a Mac 1. From the start menu, type cmd and click run as administrator to open an administrative command prompt. 2. Choose a Mac Model similar to your host system, then type the following lines, followed by <enter> after each line. Make sure you first close all VirtualBox Windows and the VirtualBox program, otherwise any changes you make won't stick... Eg iMac11,3 cd "C:\Program Files\Oracle\VirtualBox\" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemProduct" "iMac11,3" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemVersion" "1.0" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiBoardProduct" "Mac-F2238BAE" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/smc/0/Config/DeviceKey" "ourhardworkbythesewordsguardedpleasedontsteal(c)AppleComputerInc" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/smc/0/Config/GetKeyFromRealSMC" 1 MacBookPro11,3 cd "C:\Program Files\Oracle\VirtualBox\" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemProduct" "MacBookPro11,3" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemVersion" "1.0" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiBoardProduct" "Mac-2BD1B31983FE1663" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/smc/0/Config/DeviceKey" "ourhardworkbythesewordsguardedpleasedontsteal(c)AppleComputerInc" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/smc/0/Config/GetKeyFromRealSMC" 1 Macmini6,2 cd "C:\Program Files\Oracle\VirtualBox\" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemProduct" "Macmini6,2" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemVersion" "1.0" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiBoardProduct" "Mac-F65AE981FFA204ED" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/smc/0/Config/DeviceKey" "ourhardworkbythesewordsguardedpleasedontsteal(c)AppleComputerInc" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/smc/0/Config/GetKeyFromRealSMC" 1 3. Optional- For some host systems eg those with Haswell and newer CPUs, you might have to spoof an older CPU to avoid VirtualBox errors. You can try from one of the following if this happens: To spoof Lynnfield i5 750 CPU VBoxManage.exe modifyvm "El_Capitan" --cpuidset 00000001 000106e5 06100800 0098e3fd bfebfbff To spoof IvyBridge CPU VBoxManage.exe modifyvm "El_Capitan" --cpuidset 00000001 000306a9 04100800 7fbae3ff bfebfbff or VBoxManage.exe modifyvm "El_Capitan" --cpuidset 00000001 000306a9 00020800 80000201 178bfbff 4. Close the command prompt window. Installation of El Capitan We are now ready to start the El_Capitan Virtual Machine.... Installation should be relatively straight forward, just following the prompts of the OS X installer: 1. Select language, agree to legal terms 2. Use Disk Utility from the Utilities Menu to erase and format the virtual hard drive as a single partition GUID Mac OS X Extended. I named my drive "Macintosh HD" but you can enter whatever you like eg El_Capitan. 3. Quit DU and choose Macintosh HD to install El Capitan on. 4. After 20-30 min (depending on how fast your system is), the installation will complete. At this point, unmount the El Capitan ISO by clicking the Devices menu from the VM window, click Optical Drives, then choose Remove disk from virtual drive. The VM is now ready to reboot into OS X from the virtual hard drive. 5. At the welcome screen, choose your country and keyboard layout. You can skip transfer information, location services and logging in with your Apple ID if you wish… 6. Create a User Account and select your Time Zone. You can skip sending diagnostics and usage data to Apple…. 7. Finally, you will arrive at the El Capitan Desktop. 8. Network/internet and audio should work OOB but on my system, the sounds were distorted. Unfortunately, there is no QE/CI and the VM resolution will be fixed without the ability to dynamically resize the VM window (no VirtualBox additions for OS X guests atm). Customization with VBoxManage 1. You can change the default resolution of 1024*768 (after shutting down the VM) with the VBoxManage command from the Windows Administrative Command Prompt: cd "C:\Program Files\Oracle\VirtualBox\" VBoxManage setextradata "El_Capitan" VBoxInternal2/EfiGopMode N (Where N can be one of 0,1,2,3,4,5) referring to the 640x480, 800x600, 1024x768, 1280x1024, 1440x900, 1920x1200 screen resolution respectively. Update: For VirtualBox 5.2.x, the command for changing screen resolution has changed... VBoxManage setextradata "<MyVM>" VBoxInternal2/EfiGraphicsResolution XxY (where X=Horizontal screen resolution, Y=Vertical screen resolution) eg VBoxManage setextradata "<MyVM>" VBoxInternal2/EfiGraphicsResolution 1280x1024 2. Adding serials and other SMBIOS details for the System Information Screen VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemSerial" "W8#######B6" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiBoardSerial" "W8#########1A" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemVendor" "Apple Inc." VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemFamily" "iMac" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiBIOSVersion" "IM112.0057.03B" A listing of known issues with Mac OS X guests can be found in the VirtualBox Manual - link https://www.virtualbox.org/manual/ch14.html. Vanilla Mavericks and Yosemite, Snow Leopard from Retail DVD The same VM settings for El Capitan will also boot and run vanilla installations of OS X Mavericks and Yosemite . Attached to this post are installer scripts to create bootable Mavericks (CMI.tool) and Yosemite (CYI.tool) ISOs for VirtualBox and VMware. With the respective OS X installer apps in the Applications folder, download and run the installer tools using terminal ie To create a Mavericks ISO on your desktop cd downloads chmod +x CMI.tool ./CMI.tool To create a Yosemite ISO on your desktop cd downloads chmod +x CYI.tool ./CYI.tool Here is a screenshot of the VM running Mavericks 10.9.5... Finally, those without a Mac/Hack to prepare the install media can purchase a retail Snow Leopard DVD directly from Apple and install OSX 10.6.3 on their virtual machines (Snow Leopard, Lion and Mountain Lion run quite happily in VirtualBox with 1 CPU, 1-2 GB of RAM and the rest of the settings unchanged from above). Once you update by combo update to SL 10.6.8, you can directly download El Capitan from the App Store for free . UPDATE macOS Sierra 10.12 to 10.12.6: For macOS Sierra, use CSI.tool in post#51. UPDATE macOS High Sierra 17A365: For macOS High Sierra, use CHSI.tool in post#73. UPDATE macOS Mojave 18A391: For macOS Mojave or High Sierra, use macOS_iso_creator.tool on page 4 of thread. Good luck and enjoy CECI.tool.zip CYI.tool.zip CMI.tool.zip
  16. Run Vanilla OS X El Capitan, Sierra, High Sierra or Mojave in VMware Workstation on a Windows Host I wanted to make a simple guide on how to create a vanilla OS X El Capitan virtual machine running on a Windows host. The virtual machine should be useful for testing El Capitan and also for creating installers for use on a real machine/hackintosh. There are many guides and videos on the net about running OS X on Windows machines using pre-made VMWare disk images but you can never guarantee what else is in there…. I’ve gathered info for this guide from various threads in the Multibooting and Virtualisation section of this forum eg Workstation 11/12, Player 7/12, Fusion 7/8 and ESXi 6 Mac OS X Unlocker 2 by @Donk How to Install OS X 10.x from Snow Leopard to El Capitan in VMware Workstation 10/12, Player 6/8 or ESXi 5/6 by @MSOK HOW TO: Create a bootable El Capitan ISO for VMware Credit and thanks to @Donk, @Albert Nietsnie and @MSOK for all their hard work in creating and testing the VMware Unlocker program. Requirements Intel PC with four or more CPU cores running Windows 7 X64 or later OS (2 or more cores needed for OS X) 4GB or more RAM (2GB or more will be needed for OS X) Hard Disk with at least 40GB free for Virtual Machine VMware Workstation 12 or later VMware Unlocker 2.0.7 or later Install OS X El Capitan app and Mac or Hack to prepare installation iso <-- Now, no longer necessary to have previous access to a Mac or Hack by building the Installer.app from scratch - see post#41 16GB or larger exFAT formatted USB stick to transfer El Capitan iso from Mac/Hack to Host PC Prepare Installation ISO on your Mac or Hack 1. On your Mac or Hack, download "Install OS X El Capitan.app" from the App Store into your Applications folder. 2. Unmount any attached install image/InstallESD.dmg (if currently mounted) by rebooting the system or running the hdiutil unmount command in terminal eg 3. Download and unzip the CECI.tool (attached to this post) into your ~/Downloads folder. The commands in this executable script are shown below for informational purposes…. 4. Open OS X terminal, then run the following commands to execute the script: cd downloads chmod +x CECI.tool ./CECI.tool 5. At the end of the process, you will have an El Capitan iso on your desktop - copy this onto an exFAT formatted USB for use on the PC Host later. Updates: @shela has created an ISO generating script compatible with OS X 10.6-10.12: create_osx_iso post #362. See post#30 for macOS_iso_cim.tool script to create ISO for macOS 10.13+ using Apple's createinstallmedia utility. Install and Patch VMware Workstation 12 on your PC 1. Download and install VMWare Workstation Player 12 or later 2. Download and extract Unlocker 2.0.7 or later to your USB stick… 3. Run the win-install.cmd as administrator by right clicking the file in Windows explorer or run it from an Administrative Command Prompt. Create an El Capitan Virtual Machine 1. Double click on the VMware Workstation 12 Player icon on your desktop and click “Create a New Virtual Machine”. Choose “I will install the operating system later” at the How will you install screen…. 2. Select Apple Mac OS X as the Guest operating system and OS X 10.11 as the version. By default, an OS X 10.11 folder will be created in your Documents\Virtual Machines folder. 3. Under Specify Disk Capacity, you can leave the default 40GB or set a larger value. I personally store the virtual disk as a single file. Click Finish and you will see OS X 10.11 on the Main Screen of Workstation 12. 4. Next, we need to edit the virtual machine settings to map the virtual SATA CD/DVD drive to the El Capitan installation iso we created earlier. 5. To prevent the virtual machine from crashing in Windows, the virtualHW.version set in the vmx configuration file needs to be changed from 12 to 10 (alternatively, the line smc.version = "0" can be added to the file). The OS X 10.11.vmx file can be edited with the WordPad program (navigate to the OS X 10.11 virtual machine folder with Windows Explorer and right click on the file to open in WordPad). 6. For HW10, set USB compatibility to USB 2.0, otherwise your mouse and keyboard might not work in the virtual machine. 7. Finally click “Play virtual machine” Installation of El Capitan Installation should be relatively straight forward, just following the prompts of the OS X installer: 1. Select language, agree to legal terms 2. Use Disk Utility from the Utilities Menu to erase and format the virtual hard drive as a single partition GUID Mac OS X Extended. I’ve named the drive Macintosh HD but you can enter whatever you like eg El_Capitan. 3. Quit DU and choose Macintosh HD to install El Capitan on. 4. After 20-30 min (depending on how fast your system is), the installation will complete and the VM will automatically reboot… 5. At the welcome screen, choose your country and keyboard layout. You can skip transfer information, location services and logging in with your Apple ID if you wish… 6. Create a User Account and select your Time Zone. You can skip sending diagnostics and usage data to Apple…. 7. Finally, you will arrive at the El Capitan Desktop. You should eject the Installation iso now by right clicking and selecting “Eject OS X Base System”. This will allow you to install VMware Tools…. 8. After rebooting, the VM can now be resized or run at full screen resolution. Audio and network/internet should also work OOB. SMBIOS Customization and iMessage Vars To make the Virtual Machine more "Mac like", you can edit the vmx file to add unique identifiers from a real Mac's SMBIOS - eg for an iMac 11,3 SMBIOS, you can enter the following lines.... smbios.reflectHost = "FALSE" board-id.reflectHost = "FALSE" board-id = "Mac-F2238BAE" hw.model.reflectHost = "FALSE" hw.model = "iMac11,3" serialNumber.reflectHost = "FALSE" serialNumber = "W80#######6" Refer How to spoof real Mac in VMware - Multi-booting and Virtualisation. The critical variables for iMessage/Facetime activation are MLB & ROM. By default, VMware "reflects" the host's MLB and ROM since it assumes you are running the OSX guest on a real Mac host - see post#42 by @Donk. If the host is a Windows PC, the following lines need to be added to the vmx file (requires virtualHW.version 12 and smc.version = "0").... efi.nvram.var.ROM.reflectHost = "FALSE" efi.nvram.var.MLB.reflectHost = "FALSE" system-id.enable = "TRUE" and the MLB, ROM and optionally system-id entered manually eg efi.nvram.var.MLB = "W80######BA1A" (MLB can be 13 or 17 characters long, alphanumeric string) efi.nvram.var.ROM = "<=>?@A" (ROM is entered here as a 6 character ASCII string) uuid.bios = "## ## ## ## ## ## ## ##-## ## ## ## ## ## ## ##" <---Optional (if you want to inject a given system-id hexadecimal value) Note the output for ROM from imessage_debug is a 12 character hexadecimal that needs to be entered here as a 6 character ASCII string eg using an Hex to ASCII converter we find that "3c3d3e3f4041" hex is equivalent to "<=>?@A". Vanilla Mavericks and Yosemite The same VM settings for El Capitan will also boot and run vanilla installations of OS X Mavericks and Yosemite . Attached to this post are installer scripts to create bootable Mavericks (CMI.tool) and Yosemite (CYI.tool) ISOs for VirtualBox and VMware. With the respective OS X installer apps in the Applications folder, download and run the installer tools using terminal ie To create a Mavericks ISO on your desktop cd downloads chmod +x CMI.tool ./CMI.tool To create a Yosemite ISO on your desktop cd downloads chmod +x CYI.tool ./CYI.tool Here is a screenshot of the VM running Mavericks 10.9.5... Enjoy Update for macOS 10.12 Sierra The above settings still work for macOS Sierra after upgrading to VMware Workstation 12.5 and unlocker 2.0.8 - see post #13. Update for macOS 10.13 High Sierra and 10.14 Mojave See post#30 for macOS_iso_cim.tool script to create ISO for macOS using Apple's createinstallmedia utility. Post#41 describes how to build "Install macOS ******.app" on the fly from installer files downloaded beforehand in /SharedSupport folder. CECI.zip CYI.tool.zip CMI.tool.zip
  17. fusion71au

    Vector Themes

    My legacy desktop (system 2 in signature with ATI HD5770) reboots immediately after scanning volumes but before reaching Main GUI when using Clovy theme or switching to Clovy theme after commit r4750. Debug boot log attached. System boots fine when using other themes eg BGM. My other systems have no issues booting with Clovy theme, but I noticed a stray semi colon ";" just below the text "Boot macOS from macOS" in the screenshot of the initial GUI screen below... debug_r4750.log
  18. This is a brief guide on how to create a vanilla El Capitan (also same process for Sierra) OS X Installer USB with an updated prelinked kernel containing FakeSMC. It is tailored for those users who want to understand the “nuts and bolts” of how to create an installer and also to help brush up on their terminal skills (rather than have one made for them with the numerous automated “tools” available or even Apple’s createinstallmedia) : Specifically, it is also a “Proof of Concept” which shows that installation is possible without even having to rely on boot loader kext injection. Prerequisites Existing Yosemite installation (or Mavericks - see post#4 for steps 7,8) “Install OS X El Capitan.app" downloaded to the Applications folder Pacifist FakeSMC.kext - Slice or Kozlek branch Bootloader - Clover or Chameleon 8GB or larger USB drive (16GB recommended), formatted HFS+ (MBR or GUID) named “Installer” Procedure 1. Boot into Yosemite with the kext-dev-mode=1 boot flag 2. Open OS X terminal and type the following lines, followed by <Enter> after each line. The image restore and file copying may take a while to complete, and at the end of the process, the Installer volume is renamed to “OS X Base System".... sudo -s hdiutil attach /Applications/Install\ OS\ X\ El\ Capitan.app/Contents/SharedSupport/InstallESD.dmg asr restore -source /Volumes/OS\ X\ Install\ ESD/BaseSystem.dmg -target /Volumes/Installer -erase -format HFS+ -noprompt -noverify rm /Volumes/OS\ X\ Base\ System/System/Installation/Packages cp -av /Volumes/OS\ X\ Install\ ESD/Packages /Volumes/OS\ X\ Base\ System/System/Installation cp -av /Volumes/OS\ X\ Install\ ESD/BaseSystem.dmg /Volumes/OS\ X\ Install\ ESD/BaseSystem.chunklist /Volumes/OS\ X\ Base\ System diskutil unmount /Volumes/OS\ X\ Install\ ESD exit 3. Right click on the “OS X Base System” Volume and click “Get Info” 4. Click on the lock icon and untick “Ignore ownership on this volume” 5. Extract/Copy the El Capitan Kernels folder into /System/Library/ of the USB with Pacifist. NB It is found in the "Essentials.pkg" in /System/Installation/Packages 6. Delete or Rename the original /System/Library/PrelinkedKernels/prelinkedkernel —> OG.prelinkedkernel 7. Copy FakeSMC.kext and other necessary kexts (e.g. VoodooPS2Controller.kext for laptops) into the /Library/Extensions folder of the installer USB using Finder. 8. Back in terminal, type the following lines, followed by <Enter> after each line to rebuild the prelinkedkernel….. sudo -s chmod -R 755 /Volumes/OS\ X\ Base\ System/Library/Extensions chown -R 0:0 /Volumes/OS\ X\ Base\ System/Library/Extensions touch /Volumes/OS\ X\ Base\ System/System/Library/Extensions kextcache -u /Volumes/OS\ X\ Base\ System exit Any errors should be noted but the output below is normal e.g. 9. Install your Bootloader targeting the OS X Base System volume 10. Boot your system with the USB without injected kexts into the OS X Installer GUI.... Post Install The original prelinked kernel in a fresh install of El Capitan will also lack FakeSMC ie it will only be linked to Apple signed kexts. In order to boot into El Capitan the first time around without boot loader kext injection, the PLK needs to be rebuilt for the El Capitan volume like we did for the installer: 1. Boot into Yosemite with the kext-dev-mode=1 boot flag 2. Delete or Rename the original /System/Library/PrelinkedKernels/prelinkedkernel for the El Capitan volume —> OG.prelinkedkernel 3. Copy FakeSMC.kext and other necessary kexts (e.g. VoodooPS2Controller.kext for laptops) into the /Library/Extensions folder of El Capitan using Finder 4. Back in terminal, type the following lines, followed by <Enter> after each line to rebuild the prelinkedkernel. In this example, the El Capitan volume is named "El_Capitan" - change if you have named it something else... sudo -s chmod -R 755 /Volumes/El_Capitan/Library/Extensions chown -R 0:0 /Volumes/El_Capitan/Library/Extensions touch /Volumes/El_Capitan/System/Library/Extensions kextcache -u /Volumes/El_Capitan exit 5. Install your Bootloader targeting the El Capitan volume. This step is only necessary if you are installing El Capitan on a new drive without existing boot loader (not required if installing on a disk with existing boot loader beside Yosemite). 6. Reboot your system without injected kexts into El Capitan! Other links The All-In-One Guide to Vanilla OS X for beginners Updates for Sierra and High Sierra Custom Prelinkedkernel Generator Tool I have made a custom prelinkedkernel generator "PLK.tool" for Sierra + El Capitan. Instructions: 1. Download and extract the attached BaseSystem_PLK.tool.zip into your ~/Downloads folder. 2. Copy any extra kexts necessary for booting your hack to ~/Downloads/BaseSystem/ExtraKexts (e.g. FakeSMC, VoodooPS2Controller), making sure SIP is disabled. 3. Copy BaseSystem.dmg to ~/Downloads/BaseSystem 4. Open terminal and run the following commands... cd ~/Downloads/BaseSystem chmod +x PLK.tool ./PLK.tool ---> supply your admin password ---> will place your new custom prelinkedkernel on the desktop. macOS High Sierra bypass Firmware and MBR checks in post#13. BaseSystem_PLK.tool_ElCap.zip BaseSystem_PLK.tool_Sierra.zip BaseSystem_PLK.tool_Mojave.zip (need to run in Mojave to avoid dependency errors)
  19. The prelinkedkernel used by the installer is not the read only file inside BaseSystem.dmg. It is in a hidden folder (unhide with ShowAllFiles.app), full path is /Volumes/Install\ macOS\ Mojave/System/Library/PrelinkedKernels/prelinkedkernel... The terminal app for the installer can be opened by clicking on the Utilities Menu at the top. However, easier for noob to continue installation on the hard drive (click "My computer does not connect to the internet") ---> set up the new user, then install AirPortAtheros40.kext through terminal or kext utility ---> reboot and wifi can now be set up.
  20. For questions 1-3, these are unfortunately unresolved issues/bugs with VirtualBox itself. Native audio in Mojave doesn't work at present (never tried with VoodooHDA inside VM), VirtualBox BIOS does not remember previously "saved" settings and NVRAM is also non functional (these maybe related). Ofc, AptioMemoryFix driver would be useless since the BIOS is not Aptio ... If you want a "smoother" experience with native sound and working NVRAM, better to try running Mojave in VMware patched with @Donk's unlocker program. Installing VMware tools also improves graphics performance and allows dynamic resizing of the VM window (unlike VirtualBox which doesn't provide macOS guest tools at all). Sorry, don't know about Ozmosis inside VM.
  21. No need to copy both IO80211Family.kext and AirPortAtheros40.kext, just IO80211Family.kext IO80211Family.kext from High Sierra already contains AirPortAtheros40.kext inside its /IO80211Family.kext/Contents/PlugIns folder. Yes. On first boot to the newly installed Mojave on your hard dive, AirPortAtheros40.kext will be absent in /System/Library/Extensions. Copy the kext into /S/L/E and rebuild kext caches/prelinkedkernel eg In terminal... sudo cp -R AirPortAtheros40.kext /System/Library/Extensions sudo chown -R 0:0 /System/Library/Extensions/AirPortAtheros40.kext && sudo chmod -R 755 /System/Library/Extensions/AirPortAtheros40.kext sudo touch /System/Library/Extensions && sudo kextcache -u / then reboot your system. Your Atheros wifi should now work. Confirm the kext has loaded by typing kextstat | grep Atheros. I get the result Mac-Pro:~ fusion71au$ kextstat | grep Atheros 67 0 0xffffff7f81df4000 0x148000 0x148000 com.apple.driver.AirPort.Atheros40 (700.74.5) 9753F22E-5C85-3E95-B543-0870CF03838A <66 15 12 7 5 4 3 1>
  22. fusion71au

    Mojave and AirPortAtheros40.kext

    Click title bar of the Mojave installer window on top RHS to enable wifi and enter wifi password...
  23. Unfortunately to generate a working prelinked kernel for Mojave, the PLK tool needs to be run in Mojave (with Mojave's kextcache binary), otherwise you see the errors about the missing dependencies. Try the prelinked Mojave kernel that I have already posted here Mojave and AirPortAtheros40.kext.
  24. Troubleshooting 1) Check SHA1 hashes of your downloaded files with eg HashMyFiles utility. Compare with verified hashes from this website and the screenshot below for files from 10.13.6_ 17G65 ... 2) Maybe due to incorrectly edited InstallInfo.plist in \SharedSupport folder. Replace with InstallInfo.plist.zip from 10.13.6 attached to this post. InstallInfo.plist.zip Update for How to install High Sierra or Mojave on a VirtualBox Guest from scratch (without access to Mac or App Store Installer.app) I've simplified steps 1-8 with BaseSystem_vmdk_generator and added apfs support with Clover r4699 in macOS_apfs.vmdk. 1) Download & extract the contents of BaseSystem_vmdk_generator.zip to your USB. For my system, the drive letter was D: 2) Convert \SharedSupport\BaseSystem.dmg to vmdk by double clicking BaseSystem_vmdk_generator.bat. The file BaseSystem.vmdk is automatically created in the root directory \ of the USB. Deleting any existing image files and vmdk files... Could Not Find D:\*.vmdk Could Not Find D:\qemu-img-win-x64-2_3_0\*.img Converting BaseSystem.dmg to BaseSystem.img with dmg2img... dmg2img v1.6.7 (c) vu1tur (to@vu1tur.eu.org) \SharedSupport\BaseSystem.dmg --> \qemu-img-win-x64-2_3_0\BaseSystem.img decompressing: opening partition 0 ... 100.00% ok opening partition 1 ... 100.00% ok opening partition 2 ... 100.00% ok opening partition 3 ... 100.00% ok opening partition 4 ... 100.00% ok opening partition 5 ... 100.00% ok opening partition 6 ... 100.00% ok opening partition 7 ... 100.00% ok Archive successfully decompressed as \qemu-img-win-x64-2_3_0\BaseSystem.img Converting BaseSystem.img to BaseSystem.vmdk... BaseSystem.vmdk created in root directory of USB drive! Press any key to continue . . . 3) Copy BaseSystem.vmdk from your USB into the VirtualBox macOS guest folder 4) Attach BaseSystem.vmdk and macOS_apfs.vmdk to your macOS guest as extra hard drives 5) Boot your VM to the macOS Utilities screen. Attach the usb (named "USB" and containing the \SharedSupport folder) to the VM and open Disk Utility, show all devices ---> will see blank 50GB drive for installation, 2GB "OS X Base System" and the USB volume "USB" 6) Erase blank drive, format it to apfs named "macOS"  7) Close DU and start Terminal... -bash-3.2# cd /Volumes/USB -bash-3.2# ./startosinstall.command The startosinstall.command script builds the full "Install macOS ******.app" and chain loads the startosinstall utility on the "macOS" target volume. It combines both the "small" installer app (approx 15MB in size on "OS X Base System") and the SharedSupport folder from the NTFS volume (mounted on /Volumes/USB). Note the full installer app is >5GB in size 8) After a few minutes, Apple's Software License agreement will appear ---> type "A" to agree to the License Agreement etc InstallInfo.plist.zip BaseSystem_vmdk_generator.zip macOS_apfs.vmdk.zip
  25. fusion71au

    VirtualSMC — SMC Emulator

    Try copying the attached nasm, mtoc and mtoc.NEW files into /usr/local/bin. I compiled VirtualSMC 1.0.1 release version with XCODE 9.2 in 10.13.6... bin.zip Virtual SMC v1.0.1 package.zip
×