Jump to content
fantomas1

[pre-release] macOS High Sierra

3,845 posts in this topic

Recommended Posts

Kext Inject not working I need to boot -x with my Create Install media installer to the Sierra High drive

Booted installer key Ok with Clover 2079 and proceeded with installation on my Ivy Bridge Dell Latitude E6230. I get the same firmware checkup failure on reboot of 10.13 partition. Safe mode cannot be used and causes instant reboot.

 

I assume kext injection works because FakeSMC appears to load and so does my VoodooPS2Controller as I get TrackPad to work in the installer...

Share this post


Link to post
Share on other sites
Advertisement

First of all, if you tried to modify firmwarefeaturesmask inside clover, you should not forget about smbios Type 128 table, which also includes such information (firmwarefeatures / firmwarefeaturesmask).

I mean you should modify both DatahubCPU.c and smbios.c

 

I've modified both of those. It's working fine (FFM = 0xFFFFFFFF) and I can verify this in 10.11 and 10.12. The problem is PMheart's kext inject code isn't working here for 10.13. Only denskop's precompiled Clover build has worked so far.

Share this post


Link to post
Share on other sites

Booted installer key Ok with Clover 2079 and proceeded with installation on my Ivy Bridge Dell Latitude E6230. I get the same firmware checkup failure on reboot of 10.13 partition. Safe mode cannot be used and causes instant reboot.

 

I assume kext injection works because FakeSMC appears to load and so does my VoodooPS2Controller as I get TrackPad to work in the installer...

No for me on the Sierra 10.13 only Network and Wifi working -X

If I boot -v I have Couple line and Reboot  ^_^

I dont know why I try  to Install My FakeSMC on S/L/E but the issue is  the permission on Safe mode is disable ?

Share this post


Link to post
Share on other sites

290x is borked can anyone test out theres please thanks

Share this post


Link to post
Share on other sites

In a nutshell can anyone tell me how to bypass the 'OSInstall.mpkg' error? Just can't fathom it out.

Thanks!

Share this post


Link to post
Share on other sites

I've modified both of those. It's working fine (FFM = 0xFFFFFFFF) and I can verify this in 10.11 and 10.12. The problem is PMheart's kext inject code isn't working here for 10.13. Only denskop's precompiled Clover build has worked so far.

I tried with values from real macs but it doesn't change anything.

 

MacBook-Pro OSInstaller[558]: ROM Features returned nil!
MacBook-Pro OSInstaller[558]: ROM Features returned: 0
MacBook-Pro OSInstaller[558]: ROM does not support APFS

However, let's try your values. Post the FirmwareFeaturesMask and I'll compile clover with it.

Share this post


Link to post
Share on other sites

I tried with values from real macs but it doesn't change anything.

 

However, let's try your values. Post the FirmwareFeaturesMask and I'll compile clover with it.

 

I've just been using FFFFFFFF as suggested by savvamitrofanov earlier.

 

It looks like they have fixed Clover now so might as well wait for confirmation. I've already spent enough time today going in circles with broken code.

Share this post


Link to post
Share on other sites

Stay tuned , guys!

There binary with kernel_patcher and kext_inject hard coded for 10.13 with PMHeart, denskop patch.

You need to set FirmwareFeatures in config.plist to 

<key>FirmwareFeatures</key>
<string>0xe907f537</string>
Magic number for FirmwareFeaturesMask 0xff1fff3f

post-1248455-0-79014300-1496769576_thumb.jpg

post-1248455-0-73080900-1496769590_thumb.jpg

post-1248455-0-74601000-1496769691_thumb.jpg

BOOTX64.efi.zip

Share this post


Link to post
Share on other sites

Thanks I'll run with it now so I can get 10.13 installed once and for all.

 

I guess Clover needs more work to be able to detect 10.13 so until then hardcoding the kext injecting is the only way.

Share this post


Link to post
Share on other sites

"I guess Clover needs more work to be able to detect 10.13 so until then hardcoding the kext injecting is the only way."

Absolutely 

Share this post


Link to post
Share on other sites

Pretty cool, I've formatted a partition to APFS and added the driver to the clover folder and it works.

 

attachicon.gifdisk_utility_apfs.png

So you use a same EFI partition with Sierra and with any extra config to work with HighSierra ?

Share this post


Link to post
Share on other sites

can someone tell me how to get past the "OSInstall.mpkg appears to be missing or corrupted" error?

Share this post


Link to post
Share on other sites

So you use a same EFI partition with Sierra and with any extra config to work with HighSierra ?

ATM i have El Capitan @HPFS and High Sierra @APFS on one drive with two partitions, and the EFI partition for both OSes

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 glasgood
      CLOVER DUAL BOOT MOJAVE & WINDOWS 10 GUIDE 
       

       
       
      INCLUDES  MBR / LEGACY BIOS  TO  GPT / EFI CONVERSION
      USING MBR2GPT TOOL
       
       
      PREREQUISITE: Two physical discs ( SSD’s or HDD’s )
       
       
       
       
       
      STEP 1 - Clover dual boot configuration 
       
      Open config.plist with Clover Configurator
       
      Boot
       Legacy = PBR Timeout = True ( will remove the Timeout countdown, from Clover boot menu)  

       
      GUI 
      Scan / Custom
       Entries = True  Tool = True  Legacy = False ( removes extra Windows 10 entries )  
      Hide Volume
      - Preboot ( macOS Preboot )
      - Recovery ( macOS Recovery )
       

       
      So at boot you will have two options: boot macOS Mojave or Windows 10 
       
       
       
       
       
       
       
      ————————————————————
       
       
      STEP 2 - Using a drive without Windows 10 installed
       
      Disconnect system drive that contains your macOS Mojave install from computer ( This is so that Windows does not overwrite existing macOS Mojave boot loader )
       
      Proceed with a Windows 10 UEFI install.  
      After installation reconnect macOS Mojave Drive, the Windows installation should now be detected and usable in Clover. 
      If Windows 10 is not detected or able to boot,  then verify you installed Windows 10 as UEFI and not MBR ---->  ( Read step 2 - For a drive with Windows 10 installed )
       
       
      OR
       
       
       
      STEP 2 - Using a drive with Windows 10 already installed
       
      Verify your Windows install is  GPT / UEFI or MBR / Legacy BIOS.   
      If Windows install is GPT UEFI then Windows 10 install is ready to use at Clover boot menu, you should be able to boot into Windows directly from Clover boot screen. 
       

       
       
      But if  Windows drive is detected at Clover boot screen, but when booting Windows you get a black screen with a cursor on the top left,
      then this is most likely because Windows drive is MBR ( Legacy BIOS ).  You can easily convert MBR to GPT using  Windows MBR2GPT tool ( this saves hours work having to reinstall Windows 10 and setting up all your applications again  ) 
       
      If Windows 10 install is MBR / Legacy BIOS  then simply convert to GPT / UEFI  following instructions below ( read video summary and view video )
       
       
      ** To use Windows 10  MBR2GPT tool  you must have Windows 10 version 1703 ( creators update  ) or later and less than 3 partitions on 
      the Windows 10 drive **
       
      Video summary:
       
      Confirm Windows 10 drive is MBR Legacy BIOS ( in Windows Disk Management ) Reboot into Windows PE ( Advanced Startup ) Convert from MBR Legacy BIOS to GPT UEFI ( using commands below ) mbr2gpt /validate mbr2gpt /convert Restart Verify Windows 10 drive has changed to GPT UEFI ( in Windows Disk Management )  
       
       
       
      After conversion Windows 10 is ready to use at the Clover boot menu 
       
       
    • By Slice
      I successfully installed macOS 10.11.6 and Windows 7 Pro SP1 in UEFI mode on the laptop.
      I know, there are detailed guides here and on osxlatitude.com but I was not agree with them and carefully check and test every step to tune my Mac.
       
      Hardware
      Intel® Core� i5-3320M CPU @ 2.60GHz, speedstep works with Clover default settings
      Chipset Intel 7 series, no patches needed
      Video: IntelHD4000 or NVS5200M switchable in BIOS, work in both cases
      LAN; Intel 82579LM, works with IntelMausiEthernet.kext v2.2.1
      Audio: IDT 92HD93BXX, works with VoodooHDA 2.9.0.
      SDHC reader O2Micro; works with native AppleSDHC.kext with Clover Arbitrary properties.
      USB3.0 works natively if not disabled in DSDT
      PS2 keyboard and touchpad works with VoodooPS2.
      WiFi: Dell Intel WiFi was replaced by Dell DW1520, Broadcom BCM943224HMS. DeviceID=4353
      LCD Screen 1366x768
      BIOS A12. Initially was A02. Then I flashed A23 and found it is quite bad. The screen is full of artefacts. Flash A12 and all is OK. Not tested other versions.
      For some reason BIOS can switched from Intel to Nvidia by itself so I have to do my solution working independent on this state.
       
      WiFi
      It is not working OOB although it has DeviceID known to Apple. The reason is WhiteList in the driver.
      I set MacModel as MacBookPro10,1 while the WiFi will work on MacBookAir. I make a patch in Clover.
      As well a patch for channels.
      I deleted a kext Brcm4331 because it has the same DeviceID. Let kext Brcm4360 to work alone.
       
      VideoCards
      In Bios we can set Optimus = Enable/Disable
      If Enable then we have two videocards Intel first and Nvidia second. In this case additional SSDT-3.aml will switch off Nvidia.
      If Disable then we have only Nvidia card. It will work if Board-ID taken from iMac13,2.
      But here there is contradiction with WiFi with required Board-ID from MacBookAir.
      So I take MacModel as MacBookPro10,1 which is most close by CPU IvyBridge.
      Set BoardID like iMac13,2 to make Nvidia working.
      Patch BoardID in Brcm4360 to make WiFi working.
      Now I have
      Inject->
      ->Intel=YES
      ->Nvidia=YES
      and SSDT-3.aml in ACPI\patched folder. This SSDT will switch off Nvidia if Intel card ON.
      For Intel graphics there is a patch against 8 apples at start.
       
      Brightness
      No special kexts.
      The brightness controlled by keys F1,F2 and slider in Control Panel in both case Intel or Nvidia. Details here  #72 
       
      DSDT and SSDT
      This is very long story and finally I have working sleep in both cases Intel or Nvidia.
       
      Sensors
      I use my HWSensors3 with FakeSMC 3.5.0.
      I got monitoring:
      CPU temperature
      GPU temperature
      GPU main frequency
      GPU shader frequency
      Battery state % full, time to charged or time to empty.
      Battery voltage dinamically.
      Battery amperage dynamically. I can see it changes on heavy games.
      HDD temperature.

       
      Audio
      I like VoodooHDA and have no problems with it.
      The sound is clear, loud, and switchable between internal speaker and headphone.
      Mic is working.
       
      Bluetooth
      Just tested with BTFirmwareUpdate.kext and it works in 10.11.6. I not needed it so switched off by wireless switch at right side.
      For 10.13.6 there is other kext BRCMInjector.
       
      Keyboard, Touchpad and Touchstick
      Post #14
       
      My config, ACPI files and kexts are in attachment.
      05.12.2017
      EFI.7z
       
      EDITED:
      Better DSDT in the post #6.
      Sleep working even when AC inserted.
       
      EDITED 06.12.2018
      Now I have HighSierra and this is my EFI folder
       

       
       
      Welcome to discussion!
      EFI-E6430.7z
      BRCMInjector.kext.zip
    • By h2onions
      Hey all,
       
      First Hackintosh that I think I have completed! I've been working on it on and off for a month, but just grinded it this past weekend. I just have a small QOL issue. I have posted in the r/Hackintosh reddit, but have not gotten a reply to this specific issue, but did for other issues I was having. I also posted at tonymacx86 and was getting replies for other issues I was having, but got banned because I said, "used VM, but didn't work" in my OP I think ...
       
      I followed a PC vanilla guide from r/Hackintosh that I found as I did not have an Apple system. One monitor connected to a GTX 1080, CPU: i7-8700, Coffee Lake. Motherboard is Alienware specific 0VDT73, with chipset Z370.
       
      The issue is every time High Sierra boots up and gets to the login screen, my keyboard and mouse do not work. I only have to reseat both and then they work the whole time until I restart. They are both plugged into USB2.0 ports. I do have Lilu, WhateverGreen, USBInjectAll, and VoodooPS2 installed in my /Library/Extensions folder using #####. Mouse and Keyboard work fine each time I boot to Clover (USB). Any ideas?
       
      Thank you!
      Working: NVIDIA using (One) DisplayPort, USB3.0 (rear), USB-C (rear), USB2.0 (rear), Audio, Ethernet
       
      EDIT: Did some more testing, and it looks like my Keyboard works fine after each reboot, the only issue is that my mouse has to continuously be reseated. Any ideas? Could it just be the mouse?It's an old Inland USB mouse: 337451
    • By Badruzeus
      "The all-new 2019 version of the graphic design software suite is compatible with not only Windows but also Mac, complete with support for Dark Mode on macOS Mojave and the Touch Bar on the latest MacBook Pro models, providing quick access to layout settings, text controls, and more." ~ macrumors
       
      More details: https://www.coreldraw.com/en/product/coreldraw/mac/
    • By Utku
      Hi guys, I have a big problem for VT -x. I tried any things for example: dark=0 or already bios option is virtualization is enable. I don't understand this problem.
       
      Thanks guys!! And yes I have intel Q8400 quad core cpu, motherboard is Asus asus p5g41c-m lx.
       


×