Jump to content
fantomas

[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 Rohan20
      Opencore is running really really slow on Catalina 10.15.4. So It was running perfectly before I put the ssdt-pnlf for enabling Brightness control. it is running really slow and I verified my config with the sanity checker and its all correct. can someone please help. I am attaching my oc folder.

       
      https://www.dropbox.com/s/drkek0eaz19ina5/OC.zip?dl=0
       
    • By RyzenDude
      Hi everyone,
      Today I finished my High Sierra install with OpenCore. I got everything up and running but I can't seem te get rid of this text on te boot screen while booting up. Does anyone have a solution to this?
      Thanks in advance!
      Hardware:
      CPU: Ryzen 5 1600
      GPU: GTX 980
      RAM: 16 GB DDR4 2666 MHz
      Motherboard: ASUS EX-A320M-GAMING
      Audio Codec: AppleALC
      Ethernet Card: Realtek RTL8111
      Bootloader: OpenCore 0.5.5

    • By Sagnik Ganguly
      Hello I'm Sagnik Ganguly, I'm trying to dual boot macOS 10.14 and Windows 10 (already installed) on a PC with Legacy BIOS. I've two hard drives one in where the windows is installed and another which is converted to GPT to install macOS Mojave 10.14 with a partion of Mac OS Extended (Journal) or APFS but when I went to the Install Disk Selection page, I'm selecting the partition but it says "This version of macOS 10.14 cannot be installed on this computer." can you help me please? 
      P. S. My motherboard doesn't support UEFI. 
      I'm attaching some pictures of the screens.


    • By y010204025
      Disclaimer: All files of this article are from itpwd.com and rehabman ’s github.com

       
      After Testing:
       
      Graphics card: NVIDIA K1000M / K2000M / K2100M / K3000M / K3100M / K4000M / M1000M (ordinary TN1600x900 or 1920x1080), AMD W5170M / W7170M (DC2 or 4K), Intel HD4000 (ordinary TN1600x900 or 1920x1080) can be driven normally, but NVIDIA graphics card Brightness adjustment is disabled. AMD W5170m and w7170m are the best choices on 8570W and 8770W. The brightness can be adjusted normally and the graphics performance is very good. For WX7100m and WX4170m, the graphics card fans cannot be controlled, and other methods are required to control the fans. CPU: 3rd generation Intel Core i3, i5 and i7 (Ivy Bridge architecture, including all dual-core and quad-core. Celeron and Pentium are not supported), frequency conversion is normal. In general: If you have 8570W, 8770W, and hope you can get the best Hackintosh experience, it is recommended to replace the CPU with i7-3840QM / i7-3940XM, 8570W is recommended to choose W5170M, 8770W, and it is recommended to choose W7170M. In addition: If you want to have a 4K experience or perfect HIDPI, W5170m / W7170M supports 4K output, you can choose a suitable 4K screen to replace, but because 4K screens are mostly edp interface, and 8570W / 8770W motherboard is lvds interface, This requires a custom screen cable, which seems to be a difficult choice, but you can choose to do it yourself or buy it separately. In China, taobao.com is almighty and may be more suitable for you than eBay.
       
      EFI features:
      out of the box, the relevant hardware can be driven after the OS is installed, and it is easy to use without code operation.
      Supported models: HP EliteBook 8470p, 8570p, 8570w, 8770w (click the model for official specifications)
      Wireless network card: Recommended: BCM94360cd (requires ipex4 to ipex1,3 antenna 1300mbps), BCM94352HMB / DW1550 (2 antennas, 867mbps)
      Wireless characteristics: no white list, wireless network card with Bluetooth does not support the Bluetooth function of the wireless network card (also does not need to shield the pins), but the wireless normal use, you need the Bluetooth function to use this machine comes with Bluetooth:
      Clover version: 5103, keyboard mapping has been added Command key = Alt key, Option key = Win key
      Supported systems: macOS Mojave 10.14.6 (18G103)-macOS Catalina 10.15.x,
       
      Notes on known issues:
      1. The touchpad and the left and right keys under the touchpad are normal, the pointing stick and the left and right keys above the touchpad are temporarily unavailable (recommended to use the second generation of Apple Magic Trackpad)
      2. Indicator display problem (can be ignored, function is normal): Caps light is sometimes not switched in time, mute / wireless key may be yellow
      3.AMD graphics card / Intel nuclear display has supported sleep and 15 levels of brightness adjustment, NVIDIA has no
      4. If the AMD graphics card enters Huaping, refer to editing the Clover startup parameters, and add the Boot parameter radpg = 15 (the EFI file that has been configured with this parameter has been uploaded, refer to the following EFI-guided download link)
      5. Using the above NVIDIA graphics card with a normal TN screen 1600x900 or 1920x1080 can not enter the installation interface, please check whether the VBiOS of the graphics card is exclusively for HP, thank you for your test face K1000M
      6. Due to product design defects, the MSata positions of 8570w and 8770w cannot be used as boot disks, so EFI boot can only be placed on the main hard disk (turn the machine over and open the hard disk in the lower left corner of the cover, which is the main hard disk). Put on msata plate
      +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
      Hardware requirements:
      Model: 8470p, 8570p, 8570W, 8770W 1 or more, it is recommended to use another notebook for emergency Hard disk: It is recommended to choose an SSD hard disk of 240g or more. Samsung or Intel SATA hard disk is a good choice. Wireless card: BCM94352HMB, DW1550, BCM94360CD, miniPCIe slot U disk: 1 for 16g and above, another winPE emergency USB disk is recommended If you use a rescue USB flash drive, it means that you read this post carefully
       
      Make and install a USB flash drive:
      Get the mirror: please do it your way Making and installing a USB flash drive: macOS command line production is recommended, whether it is a real macOS model or a virtual machine (although this is not allowed to be discussed in many forums)Or you can choose to use TransMac or ether under Windows. This is not recommended, but it is simple enough for those new to Hackintosh. Make boot U disk: If you know how to put the boot into the installation U disk, unzip the EFI file and put it in the EFI partition, or you can choose a fat32 format U disk to store the EFI file separately Note: EFI is an unzipped folder, not a zip or ISO suffix file.
       
      BIOS settings From RehabMan
      To start, set BIOS to defaults.
      Then insure:
      UEFI boot is enabled (hybrid/with CSM for best result) secure boot is disabled disable fast boot IGPU graphics memory set to 64mb, if available disable the serial port via BIOS option, if available disable "LAN/WLAN switching", if available disable "Extended Idle Power States" if you find it under "Power Management Options" disable "Wake on LAN" and "Wake on USB" disable Firewire/IEEE 1394, if your laptop has it for Skylake and KabyLake laptop, enable "Launch Hotkeys without Fn keypress" Note: If you have a laptop with switchable graphics, leave it enabled. You can still use it on Windows, although the discrete card will be disabled when running OS X by the ACPI patches provided here. If you want to also disable it in Windows (via BIOS option), make sure you read about the DGPU option in your model specific SSDT (source is in SSDT-HACK.dsl), as in the scenario where the DGPU is disabled by BIOS, DGPU should be set to zero.
       
      Install:
      Please modify according to the above BIOS settings: Press F9 after booting, select the boot efi to file option, which is generally the last item. Enter your boot USB disk to find the location of cloverx64.efi, select cloverx64.efi, press Enter, and enter the clover boot interface. Select the location of the install entry and press Enter. Enter the macOS interface, use the disk tool to format the partition you need to install to hfs + or apfs format, do not choose the encryption option, this will make your efforts in vain. Note: The disk must be in gpt format, and the remaining EFI space is greater than 200M, 300mb + is recommended. If it is not, please try to modify it in WindowsPE environment. This may cause you to lose the Windows system boot and disk data. Please prepare for backup.
      After formatting the partition successfully, close the disk tool and select install, you will find the partition you installed, and follow the interface prompts. When the installation reaches a certain progress, it will restart. When restarting, select F9, enter from the boot U disk, select the disk partition where you installed macOS (no longer the U disk installation), the installation will continue, and it may restart 2 ~ 3 times Every time, you need F9 to select the boot. After entering the installation interface, except for the first installation, select the U disk, and then select the disk installation partition. Eventually you will enter the settings interface. After following the interface prompts, you will enter the macOS system interface. Remember the system password and turn off the Find my mac option.  
      Post install:
       
      After the installation is complete, you need to hang the EFI partition of the disk, copy the EFI file of the U disk to the EFI partition of the disk, so that you can directly use the disk to boot, otherwise you need to select the U disk to boot each time. The mount tool can choose cloverconfigurator. If after copying the EFI file to the disk, the computer cannot recognize your clover boot, you can use the custom boot option of bios: set the custom boot path to \efi\clover\cloverx64.efi, and set it as the first boot, Use bootice or easyUEFI to increase the clover boot option under Windows and set it as the first boot. If you do not have a wireless network card available temporarily, you can use the USB binding function of your Android phone to share the network. This may require the HoRndis driver. It is not recommended to use a US wireless network card. If you need Windows or Linux, you can install it normally. Be careful not to let Windows overwrite your boot files.  
      For other uses of macOS and brew, please pay attention to forums and other communities. Hackintosh is just the beginning.
       
      Finally, I would like to thank rehabman, vit9696 and others who contributed to Hackintosh. I also thank Cwen for his efforts to modify files and hardware tests. I hope that Hackintosh will be eternal.
       
      Please comply with the laws and regulations of your country or region. My description may not be clear or professional, but I think it is necessary. I think the existence of Hackintosh is everyone's technical hobby and experience macOS, not as a substitute for macOS cheap hardware.

      EFI_8x70_5103_W7170m_20200116 .zip
×