[Release] Hackintool v3.x.x

[XpertVolvox]

Here is my config.plist. Normally I use an RX580 and the HD 630 only for quick-sync, but if I get the HD 630 fully working, I sell the RX580.

Tried your patches for my hd 630 but same black bars and display is still glitchy. Is this the same config as your Mac mini screenshots that you shared. Thanks

Edit: this is for dual monitors for anyone else reading

 

[Shoy]

Tried your patches for my hd 630 but same black bars and display is still glitchy. Is this the same config as your Mac mini screenshots that you shared. Thanks

why am i the only one who not having any luck with any of the con figs ?

 

[lehmanhill]

What framebuffer data are you using in Hackintool? Obviously I'd like to fix any crashes in the latest release.

I just downloaded 1.7.4 and the same issue is happening for me. I am currently using 3E9B0007 for a Coffee Lake, UHD 630, Mojave 14.1 desktop and getting no patch when pressing the "generate patch" button. I have also tried it with all of the UHD 630 platform-id including mobile and id's with no model. None generate a patch for me. These screenshots show that default data using 3E9B0007.

Not really. There seems to be a lot of issues with Mojave. Hackintool is really just a tool to help people create configurations. It can't solve underlying issues and I don't really have the time to go through and check everyone's configs. For most people it should be a matter of setting ig-platform-id and letting Lilu + WhateverGreen take care of the rest. Obviously this is not the case for a lot of people and I really don't know why it's so problematic. All I can really suggest is to search the forums for hardware matching your own and try to find a known working config.

Thanks for clarifying that. Sometimes it feels like everyone else is doing fine and I'm just a dummy. I will take your advice and, if I can't get there this way, I will consider trying to get back to Mac OS13.x.

 

[lehmanhill]

I'm not sure why you're converting Base64. Hackintool can export this data directly to your config.plist. PS. The device-id value is mz4AAAA== which is 9b3e000000 in hex.

A little confusion here. I freely admit that I don't understand hex and 64 bit. Anyway, FB Patcher 1.7.1 gives mz4AAA== (no 4th A) in the patch text when told the platform-id is 3E9B0007.

Using the Clover Configurator/Devices/Properties method with the Properties Value for device-id set as 3E9B0007, then going to the Clover Configurator/Text Mode shows device-id to have a value of PpsABw== . See post #490, device-id picture to see what I am talking about.

I'm not clear if the == are showing that the value is truncated or if we are short of the needed input.

Also, the same input two ways is giving a different value, so I'm not sure which to use.

 

[XpertVolvox]

why am i the only one who not having any luck with any of the con figs ?

That configs for hd 630 kaby lake not for uhd 630.

 

[Shoy]

I just can't imagine a modern Coffee Lake PC having DVMT pre-alloc set to 32 MB by default. It's odd you need to set that. Are you using the Patch->Advanced->DVMT pre-alloc 32 MB option? It's not just framebuffer-stolenmem that needs to be set but framebuffer-fbmem also. This option will set them both for you. If your BIOS has it set above 32 MB you shouldn't have any issues.

hey my PIC bus is 0 do you think thats the reason why im not getting any output to my diskplay when i tgry to use 0x3E9B0007 or anything else for that matter ? if so is there a way to fix/change it

 

[Shoy]

That configs for hd 630 kaby lake not for uhd 630.

yeah i found that out already i open the config and took a look around

 

[headkaze]

I don not know how your tool reads the values, but without changing the pipe values, the tool will show me 18, 18, 18, while the 5912 ID settings are 9, 10, 10. See also the picture.

You must have the Patch->Advanced->Hotplug Reboot Fix option enabled. It sets the pipe values to 18.

 

[headkaze]

A little confusion here. I freely admit that I don't understand hex and 64 bit. Anyway, FB Patcher 1.7.1 gives mz4AAA== (no 4th A) in the patch text when told the platform-id is 3E9B0007.

Sorry my bad it is mz4AAA== / 0x9b3e0000. I accidentally added an extra byte. Either way FB Patcher is correct. It's just as easy to use a Base64 to hex converter online (not that you would need one if you used FB Patcher's export function).

Using the Clover Configurator/Devices/Properties method with the Properties Value for device-id set as 3E9B0007, then going to the Clover Configurator/Text Mode shows device-id to have a value of PpsABw== . See post #490, device-id picture to see what I am talking about.

I think you're getting confused between device-id and ig-platform-id. You don't need the "07" on the end of device-id. Check out [Guide] Intel Framebuffer patching using WhateverGreen.

Gen 8: Coffee Lake (Intel UHD Graphics 630)
- S/L/E/AppleIntelCFLGraphicsFramebuffer.kext
- Support started with macOS 10.13.6 (17G2112) / 10.14 beta 4 (18A336e)
- device-id: 0x3E9B 0x3EA5 0x3E92 0x3E91
- AAPL,ig-platform-id (desktop): 0x3EA50000 (default), 0x3E9B0007 (recommended)
- AAPL,ig-platform-id (laptop): 0x3EA50009 (default)

 

[wern]

Tried your patches for my hd 630 but same black bars and display is still glitchy. Is this the same config as your Mac mini screenshots that you shared. Thanks

Edit: this is for dual monitors for anyone else reading

It was not a MacMini, but an iMac18,1. I only use a few patches because the 5912 ID ports are very similar from my computer DP, HDMI, DP.
I usually use Lilu and WEG only for testing. Today I updated the kexts and got a black screen with Lilu 1.3.1 reverted to 1.2.8 and it works again. If you use 1.3.1 try 1.2.8 maybe it helps.