Jump to content
fantomas1

[pre-release] macOS High Sierra

3,845 posts in this topic

Recommended Posts

Advertisement

I'm installing the new release on my skylake machine on a usb 3.0 hdd and no firmware or OSInstall.mpkg error

However after the first reboot system couldn't recognize any usb bootable device so I had to go to bios and after exiting the bios they apeared in the uefi boot menu

 

 

Sent from my iPhone using Tapatalk

Share this post


Link to post
Share on other sites

I'm installing the new release on my skylake machine on a usb 3.0 hdd and no firmware or OSInstall.mpkg error

However after the first reboot system couldn't recognize any usb bootable device so I had to go to bios and after exiting the bios they apeared in the uefi boot menu

 

 

Sent from my iPhone using Tapatalk

Strange. I didn't test your config.plist yet. Could it simply be that CC has added the word hack?

 

Sent from my SM-G930F using Tapatalk

Share this post


Link to post
Share on other sites

Strange. I didn't test your config.plist yet. Could it simply be that CC has added the word hack?

 

Sent from my SM-G930F using Tapatalk

I'm not entirely sure about the "Hacked" thingy that the new CC adds to the config.plist and to be honest I don't like it, neither the new version of cc it's so buggy.

I will post my EFI folder one the installation is done.

 

 

Sent from my iPhone using Tapatalk

Share this post


Link to post
Share on other sites

Hi there. Have any of you guys seen new support added for polaris12 (rx550) in latest DP? Its probably not / no.

From 2 months ago:

​> There is no 699F device ID in the kexts to allow Polaris 12 work in Mac OS.

​I just ask because the polaris12 has fewer CUs than rx460. So when we tried to spoof it today (on sierra 12.6) to be rx460, it just hard resets during boot time. Maybe its trying to address processing units which are not there, and then crashes.

 

Anyhow this is not a problem for me. Just thought to ask while still have the card in hands. In few days / couple of weeks I will return this card back to retailer anyhow due to fan noise issue / coil whine. And then revert back to passive gt1030 instead.

​What confused me was I bought this card (not checking carefuly!), just assuming it was already supported. Since a lot earlier on there was a news finding stuff like Polaris12 id in kexts:

https://forums.appleinsider.com/discussion/197513/trio-of-new-amd-gpu-references-for-possible-mac-refresh-found-in-latest-macos-sierra-beta

​Ah well. :lol:

Share this post


Link to post
Share on other sites

Update went without problems on my Optiplex 790  :) 
 

Image%202017-08-15%20at%201.17.05%20PM.p

@Sherlocks: Other than the usual handoff patch for the ASUS BT400 Bluetooth dongle I don't need a patch if using PCI ID 41e4,4331

The card will be recognized as third party but handoff, Hack-to-iPhone AirDrop, Instant Hotspot et cetera is working  ^_^

 

To make the card show up as AirPort Extreme, find: 6b100000 750d -> replace: 6b100000 9090 is still valid.
 

By the way:
 

BCM4352-fvco, (credit Sherlocks based on the-darkvoid original)
com.apple.driver.AirPort.BrcmNIC-MFG
81ff52aa 000074c4
81ff52aa 00006690

is not valid. Assuming it should be 81ff52aa 000074b4?

Schermafbeelding%202017-08-15%20om%2013.

Share this post


Link to post
Share on other sites

@ Sherlocks - Is there a new date for this firmware to put into SMBIOS?

 after all my usb boot ok with edit config.plist (post 2600 bios update) no necessari update clover (4152) and install 10.13.6 ok

Share this post


Link to post
Share on other sites

I'm not entirely sure about the "Hacked" thingy that the new CC adds to the config.plist and to be honest I don't like it neither the new version of cc it's so buggy.

I will post my EFI folder one the installation is done.

 

 

Sent from my iPhone using Tapatalk

Installing now on desktop. Kept changes from @xtddd but I also noticed I still had EmuVariableUefi on usb stick .

Laptop still needs looking at.

 

Sent from my SM-G930F using Tapatalk

Share this post


Link to post
Share on other sites

Installing now on desktop. Kept changes from @xtddd but I also noticed I still had EmuVariableUefi on usb stick .

Laptop still needs looking at.

Great :)

Share this post


Link to post
Share on other sites

EFIPayloads:

 

 - IM101.88Z.00CF.B00.1708080133

 - IM111.88Z.0037.B00.1708080241

 - IM112.88Z.005B.B00.1708080439

 - IM121.88Z.004D.B00.1708080012

 - IM131.88Z.010F.B00.1708080805

 - IM141.88Z.0122.B00.1708080806

 - IM142.88Z.0122.B00.1708080739

 - IM143.88Z.0122.B00.1708080732

 - IM144.88Z.0183.B00.1708080656

 - IM151.88Z.0211.B00.1708080656

 - MB61.88Z.00CB.B00.1708080203

 - MB71.88Z.003D.B00.1708080317

 - MBA31.88Z.0067.B00.1708080355

 - MBA41.88Z.007B.B00.1708072159

 - MBA51.88Z.00F4.B00.1708080803

 - MBA61.88Z.0103.B00.1708080653

 - MBP101.88Z.00F2.B00.1708080809

 - MBP102.88Z.010B.B00.1708080805

 - MBP111.88Z.0142.B00.1708080655

 - MBP112.88Z.0142.B00.1708080655

 - MBP61.88Z.005A.B00.1708072217

 - MBP71.88Z.003D.B00.1708080058

 - MBP81.88Z.004D.B00.1708080655

 - MBP91.88Z.00D7.B00.1708080744

 - MM41.88Z.0045.B00.1708072325

 - MM51.88Z.007B.B00.1708080744

 - MM61.88Z.010B.B00.1708080649

 - MM71.88Z.0224.B00.1708080033

 - MP61.88Z.0120.B00.1708080652

 - IM161.88Z.0212.B00.1708080033

 - IM162.88Z.0212.B00.1708080033

 - IM171.88Z.0110.B00.1708080012

 - IM181.88Z.0151.B00.1708080034

 - IM183.88Z.0151.B00.1708080034

 - MB101.88Z.0154.B00.1708080122

 - MB81.88Z.0168.B00.1708080033

 - MB91.88Z.0159.B00.1708080011

 - MBA71.88Z.0171.B00.1708072210

 - MBP114.88Z.0177.B00.1708080033

 - MBP121.88Z.0171.B00.1708080033

 - MBP131.88Z.0212.B00.1708080127

 - MBP132.88Z.0233.B00.1708080034

 - MBP133.88Z.0233.B00.1708080034

 - MBP141.88Z.0167.B00.1708080034

 - MBP142.88Z.0167.B00.1708080034

 - MBP143.88Z.0167.B00.1708080129

 

 

SMCJSONs:

 

 - Mac-031B6874CF7F642A: 2.14f24

 - Mac-189A3D4F975D5FFC: 2.16f68

 - Mac-27ADBB7B4CEE8E61: 2.15f7

 - Mac-2BD1B31983FE1663: 2.19f12

 - Mac-35C1E88140C3E6CF: 2.12f143

 - Mac-35C5E08120C7EEAF: 2.24f32

 - Mac-3CBD00234E554E41: 2.18f15

 - Mac-42FD25EABCABB274: 2.22f16

 - Mac-473D31EABEB93F9B: 2.36f97

 - Mac-65CE76090165799A: 2.33f10

 - Mac-66E35819EE2D0D05: 2.37f20

 - Mac-77EB7D7DAF985301: 2.17f7

 - Mac-7DF21CB3ED6977E5: 2.13f15

 - Mac-81E3E92DD6088272: 2.21f92

 - Mac-937CB26E2E02BB01: 2.27f2

 - Mac-9AE82516C7C6B903: 2.35f105

 - Mac-9F18E312C5C2BF0B: 2.26f2

 - Mac-A369DDC4E67F1C45: 2.31f36

 - Mac-A5C67F76ED83108C: 2.38f7

 - Mac-B809C3757DA9BB8D: 2.34f2

 - Mac-BE0E8AC46FE800CC: 2.25f87

 - Mac-DB15BD556843C820: 2.33f10

 - Mac-E43C1C25D4880AD6: 2.28f7

 - Mac-F60DEB81FF30ACF6: 2.20f18

 - Mac-FA842E06C61E91C5: 2.23f11

 - Mac-FFE5EF870D7BA81A: 2.32f20

 

 

FirmwareFeatures(Mask):

 

 - IM131.88Z.010F.B00.1708080805: FirmwareFeaturesMask=0xff1fff3f | FirmwareFeatures=0xe00de137

 - IM141.88Z.0122.B00.1708080806: FirmwareFeaturesMask=0xff1fff3f | FirmwareFeatures=0xe00fe137

 - IM142.88Z.0122.B00.1708080739: FirmwareFeaturesMask=0xff1fff3f | FirmwareFeatures=0xe00fe137

 - IM143.88Z.0122.B00.1708080732: FirmwareFeaturesMask=0xff1fff3f | FirmwareFeatures=0xe00fe137

 - IM144.88Z.0183.B00.1708080656: FirmwareFeaturesMask=0xff1fff3f | FirmwareFeatures=0xf00fe137

 - IM151.88Z.0211.B00.1708080656: FirmwareFeaturesMask=0xff1fff3f | FirmwareFeatures=0xf80fe137

 - MBA41.88Z.007B.B00.1708072159: FirmwareFeaturesMask=0xff1fff3f | FirmwareFeatures=0xd00de137

 - MBA51.88Z.00F4.B00.1708080803: FirmwareFeaturesMask=0xff1fff3f | FirmwareFeatures=0xe00de137

 - MBA61.88Z.0103.B00.1708080653: FirmwareFeaturesMask=0xff1fff3f | FirmwareFeatures=0xe00fe137

 - MBP101.88Z.00F2.B00.1708080809: FirmwareFeaturesMask=0xff1fff3f | FirmwareFeatures=0xe00de137

 - MBP102.88Z.010B.B00.1708080805: FirmwareFeaturesMask=0xff1fff3f | FirmwareFeatures=0xe00de137

 - MBP111.88Z.0142.B00.1708080655: FirmwareFeaturesMask=0xff1fff3f | FirmwareFeatures=0xe80fe137

 - MBP112.88Z.0142.B00.1708080655: FirmwareFeaturesMask=0xff1fff3f | FirmwareFeatures=0xe80fe137

 - MBP91.88Z.00D7.B00.1708080744: FirmwareFeaturesMask=0xff1fff3f | FirmwareFeatures=0xc00de137

 - MM51.88Z.007B.B00.1708080744: FirmwareFeaturesMask=0xff1fff3f | FirmwareFeatures=0xd00de137

 - MM61.88Z.010B.B00.1708080649: FirmwareFeaturesMask=0xff1fff3f | FirmwareFeatures=0xe00de137

 - MP61.88Z.0120.B00.1708080652: FirmwareFeaturesMask=0xff1fff3f | FirmwareFeatures=0xe80fe136

 - IM171.88Z.0110.B00.1708080012: FirmwareFeaturesMask=0xff1fff3f | FirmwareFeatures=0xfc0fe136

 - IM181.88Z.0151.B00.1708080034: FirmwareFeaturesMask=0xff1fff3f | FirmwareFeatures=0xfc0fe136

 - IM183.88Z.0151.B00.1708080034: FirmwareFeaturesMask=0xff1fff3f | FirmwareFeatures=0xfc0fe136

 - MB101.88Z.0154.B00.1708080122: FirmwareFeaturesMask=0xff1fff3f | FirmwareFeatures=0xfc0fe13e

 - MB91.88Z.0159.B00.1708080011: FirmwareFeaturesMask=0xff1fff3f | FirmwareFeatures=0xfc0fe13e

 - MBP131.88Z.0212.B00.1708080127: FirmwareFeaturesMask=0xff1fff3f | FirmwareFeatures=0xfc0fe136

 - MBP132.88Z.0233.B00.1708080034: FirmwareFeaturesMask=0xff1fff3f | FirmwareFeatures=0xfc0fe136

 - MBP133.88Z.0233.B00.1708080034: FirmwareFeaturesMask=0xff1fff3f | FirmwareFeatures=0xfc0fe13e

 - MBP141.88Z.0167.B00.1708080034: FirmwareFeaturesMask=0xff1fff3f | FirmwareFeatures=0xfc0fe136

 - MBP142.88Z.0167.B00.1708080034: FirmwareFeaturesMask=0xff1fff3f | FirmwareFeatures=0xfc0fe136

 - MBP143.88Z.0167.B00.1708080129: FirmwareFeaturesMask=0xff1fff3f | FirmwareFeatures=0xfc0fe13e

I have use to my PC config iMac 10,1 and new EFIPayloads - IM101.88Z.00CF.B00.1708080133 , what set value for FirmwareFeaturesMask and FirmwareFeatures, because not is on that list info? Very thanks for help.

Share this post


Link to post
Share on other sites

Well done  :) ( after some hesitation ) :

- Always   Clover_v2.4k_r4104

- no change in my apf.efi driver ( driver from june)

- no change in smbios or firmewarefeatures

post-1879825-0-61595000-1502797793_thumb.png

Share this post


Link to post
Share on other sites

Hi there. Have any of you guys seen new support added for polaris12 (rx550) in latest DP? Its probably not / no.

From 2 months ago:

​> There is no 699F device ID in the kexts to allow Polaris 12 work in Mac OS.

​I just ask because the polaris12 has fewer CUs than rx460. So when we tried to spoof it today (on sierra 12.6) to be rx460, it just hard resets during boot time. Maybe its trying to address processing units which are not there, and then crashes.

 

Anyhow this is not a problem for me. Just thought to ask while still have the card in hands. In few days / couple of weeks I will return this card back to retailer anyhow due to fan noise issue / coil whine. And then revert back to passive gt1030 instead.

​What confused me was I bought this card (not checking carefuly!), just assuming it was already supported. Since a lot earlier on there was a news finding stuff like Polaris12 id in kexts:

https://forums.appleinsider.com/discussion/197513/trio-of-new-amd-gpu-references-for-possible-mac-refresh-found-in-latest-macos-sierra-beta

​Ah well. :lol:

If I'm not mistaking the device ID for RX550 is 1002699F and I can't find it any of the AMDFramebuffer kext files. So no, it's not added to the latest version.

Share this post


Link to post
Share on other sites

I have use to my PC config iMac 10,1 and new EFIPayloads - IM101.88Z.00CF.B00.1708080133 , what set value for FirmwareFeaturesMask and FirmwareFeatures, because not is on that list info? Very thanks for help.

Try install without FF FFM. Then tell me result.

 

Some smbios model are not clean. We need to clean

 

나의 LG-F800S 의 Tapatalk에서 보냄

Share this post


Link to post
Share on other sites

@ricoc90

The new patch looks healthy. But why not use AirportBrcmFixup instead? (You also need Lilu v1.1.6 of course)

Within Sierra, the only way I can make my Archer T6E work is by using find: 81f952aa 00007529  -> replace: 81f952aa 00006690

Otherwise my wireless won't work (No hardware found). Something about Brcm4360 start failed. I just tried AirportBrcmFixup. The kext is loaded but it gives me the same problem: Brcm4360 start failed -> No hardware found

 

Within High Sierra I don't need that patch, since Wifi works OOB. Only Handoff doesn't.

Handoff works when I either replace AirPortBrcm4360.kext with the one from Sierra and use the same patch, OR if I add my device ID to high Sierra's AirPortBrcm4360.kext's info.plist, OR, when I use Fake PCI ID 41e4,4331. 

Actually, it uses BrcmNIC-MFG per default and I could not find a way to make Handoff work on it. It only works if I force macOS to load AirPortBrcm4360.kext

Share this post


Link to post
Share on other sites
Guest
This topic is now closed to further replies.

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By fantomas1
      This update:
      • Makes downloaded issues available in the My Magazines section of Apple News+, both online and offline
      • Adds all publications in Apple News+, including newspapers, to the catalog at the top of the News+ feed
      • Adds the ability to clear downloaded magazine issues in Apple News+ by selecting History > Clear > Clear All
      • Addresses an issue which prevents creation of a new Boot Camp partition on iMac and Mac mini with Fusion Drive
      • Resolves an issue that may cause a hang during a restart
      • Resolves a graphics issue that may occur when waking from sleep
      • Fixes an issue that may cause fullscreen video to appear black on Mac mini
      • Improves file sharing reliability over SMB
       
      macOS Mojave 10.14.6 (18G84)
       
      Update
      Combo

      View full article
    • By fantomas1
      This update:
      • Makes downloaded issues available in the My Magazines section of Apple News+, both online and offline
      • Adds all publications in Apple News+, including newspapers, to the catalog at the top of the News+ feed
      • Adds the ability to clear downloaded magazine issues in Apple News+ by selecting History > Clear > Clear All
      • Addresses an issue which prevents creation of a new Boot Camp partition on iMac and Mac mini with Fusion Drive
      • Resolves an issue that may cause a hang during a restart
      • Resolves a graphics issue that may occur when waking from sleep
      • Fixes an issue that may cause fullscreen video to appear black on Mac mini
      • Improves file sharing reliability over SMB
       
      macOS Mojave 10.14.6 (18G84)
       
      Update
      Combo
    • By fantomas1
      macOS Mojave 10.14.6 (18G84)
       
      Update
      Combo
    • By fusion71au
      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, the hackintosh-vanilla-desktop-guide has some good explanations on the various settings available and also offers sample configuration files based on CPU type.  Also, 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.5_18F132
      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.5.zip
       
       
    • By Pentothal.Z
      Hello all,
      I have a working hackintosh....ok.....but it takes a lot to boot and according to the boot.log there are a few problems.
      One of them is a black screen that stays on for a long time.
      I would like to ask anyone in this community some help to fine tune my machine.
      Boot.log and config.plist attached


      Any help would be appreciated.
      bootlog.txt
      config.plist
×