Install Hackintool

[Maria]

Current Framebuffer" is your currently booted framebuffer information. The "Selected Framebuffer" is based on your selection from the "Intel Generation" and "Platform ID" dropdown lists. In other words the "Selected Framebuffer" is for when you're trying to patch to something else.

Re the frame buffer and selection, I did not actually select I just opened hackintool and those screens came up, so no selection on my part just an observation, that in one snapshot it clearly shows a "mobile" in another snapshot taken directly from Hackintool it shows that its not Mobile, I have not touched anything, same with the video memory in different sections of hackintool it gives conflicting information, it is just an observation, and wish to thank you for responding, your hard work is very much appriciated.

can anyone point me towards how to change from a Mobile Graphics processor to a desktop I have cycled through the different device ids trying to find UHD 630 coffee lake that would give me connectors for hdmi and display port, I am not sure if hdmi con is 40.0000 and display con is 80.0000 ?

1. Was any button or anything supposed to exist on the Lilu panel? While I do see a "reload" icon on both Boot and System panels, there is nothing on Lilu. And no logs either inside the content panel (see #2 below, might be linked).

2. Even with the DEBUG kexts compiled and running, and with all the -kextdbg boot-args (-liludbg -vsmcdbg -wegdbg -younameitdbg lol), I cannot get any output from Lilu and friends kexts on any of the Logs panels. I have Boot logs, I have kernel and Hackintool logs, though. Are you aware of any changes on Big Sur's logging?

The icon in the Boot and System tabs of the Logs panel is called "Refresh" (mouse over to see the name). System also has an "Erase Log" icon. You're right about the Lilu tab - no icons exist and the log is empty.

Using "--predicate" is faster than "grep". Using "contains" is faster than "matches". I think using senderImagePath works only for messages from the kext (the kext has successfully loaded). Using "message contains" is slow (like grep) but use it if there's no messages from the kexts.

Thank you both @headkaze and @joevt. The "log show" command, which used to work on Catalina to display Lilu and friends kexts, seems not to work with Big Sur anymore for these kexts. I was able to get the debug output via liludump boot-arg (including it now displayed on the Lilu tab of Hackintool). Too bad I'll need to set a high enough timeout to be able to collect all the debug I'm looking for.

I use "log show" successfully in Big Sur. I had to compile Lilu and WhateverGreen to make them work (the code is newer than the releases). I use "kmutil load -p" to load them in Big Sur on my Mac Mini 2018 (not using Clover or Open Core).

When you do a fresh install does the install reach all the way to the Desktop? If it does then all you need to do is mount the EFI Partition of the main Drive and copy the EFI Folder from the installer to the EFI Partition of your main drive and reboot that should solve the problem if I interpreted your query correctly.

Hackintool collects the kext off the desktop and installs it to the opencore kext folder on the EFI. When you look at installed kext in hackintool the kext that you installed by hackintool itself do not appear in that list.

Kexts will show up under the Extensions tab if you install them correctly. Since Mojave you no longer install kexts to /L/E so there's really is no need to use Hackintool for this purpose. Just mount your EFI and copy the kexts you need into EFI/OC/Kexts then reboot and they should show.

It made sense to use a tool when we needed to install kexts to /L/E because it would require a permission and cache update. Now you can copy them to EFI/OC/Kexts using Finder without issue so there is no need for a tool anymore.

Could someone help me with this issue?

Would I have to do the procedure of applying the AppleIntulAzulFramebffer patch or would Hackintool help me on this point?

As the photo below, when connected to the Dell UltraSharp 24 "U2419H it boots and enters normally.

Hi everyone, I hope you are all well and safe. As this thread and tool have been a little quiet these last weeks, I wanted to ask if @headkaze is well and around? I detected an issue for the kext as the version is not detected correctly (not sure if it's Hackintool or the kext) and posted a request here so not sure if I am the only one having this issue? @headkaze if you see this and have time, a quick feedback is appreciated so I can raise it to the developers of itlwm. Thank you!

I have been having trouble updating kexts in Hackintool. While Hackintool identifies updates that require compiling with Xcode, they do not compile properly. Just compiling Lilu.kext, I get 8 errors and build failure. I'm not sure if the problem is with Hackintool or if it has to do with the way Github stores some files needed to compile kexts properly. The fact that most kexts have a lot of errors compiling suggests that it's not a problem caused by the developers of the kexts. Anyone else having this issue?

On my iMac my Firestudio Mobile (as its the same series I think it applies here as well) it still worked after some "tinkering" I can't recall exactly, but on my my macbook it did not. The FS did not initialize and the driver Version in UC was 0.0.0.0. All "easy routes" did not seem to fix the problem.

I'm pretty sure the reason why the old UC 1.7.6 won't install on Catalina (and later MacOSses to come) is, that the installer wants to put some files into MacOS /System/Library folder - which is considered "not best practice" since long before Mojave and the latest UC updates. And exactly this is not possible anymore since Catalina's implementation of new measures to ensure System Integrity.

Unfortunately it's not so easy to work around that, simply moving the kext file into the "new" directory with finder did not work for me. However with a method a little more complex I managed to get my FS mobile up and running on my Desktop Mac and my older MacBook pro - both running Catalina:

The initial situation:

- iMac/MacBook Pro with Mojave installed

- Studio One and UC already installed

-> FS works, initializes perfectly in S1

- Upgrade to MacOS Catalina (FS not plugged in)

- Afterwards Universal Control shows Driver Version 0.0.0.0, FS does not initialize

After some experimenting, what I did to make it work again:

- Boot into recovery mode (CMD+R before apple symbol), start terminal from utilities menu, enter "csrutil disable" and enter to disable the System Integration Protection

- Reboot (by issuing "reboot" in terminal)

- Extract the PaeFireStudio.kext file from the Presonus Universal Control.pkg by using for a tool like "Pacifist" for example

- After that I followed the instructions found on the hackintosh portal for installing 3rd party kexts below "The Hackintool Method": -installing-3rd-party-kexts-el-capitan-sierra-high-sierra-mojave-catalina.268964/

- Download the Hackintool from the Link provided below the sceenshots

- Unzip and start the tool with Right Click -> Hold Alt + Open

- You do not need to update "Clover" if asked

- Goto Tools and follow the procedure as mentioned in the thread

- disable gatekeeper/mount disk as rw

- install kext

- rebuild plugin cache and permissions (was started automatically for me after installing the kext)

- Reboot

- After that, Universal Control shows driver version 4.2.1.46437 and the interface initializes normally like before

- Reboot and again boot into recovery mode (CMD+R before apple symbol), start terminal from utilities menu, enter "csrutil enable" and enter to enable the System Integration Protection

- Reboot (by issuing "reboot" in terminal)

3a8082e126