Jump to content

Hackintool v3.x.x


headkaze
1,057 posts in this topic

Recommended Posts

On 9/4/2018 at 12:39 PM, hack_vel said:

 

I was using 17G61, this is what the python script show me now 

 

#    ProductID    Version    Build  Title
 1    091-95774    10.13.6  17G2208  macOS High Sierra
 2    091-82771    10.13.5   17F66a  Install macOS High Sierra Beta
 3    091-94326    10.13.6    17G65  macOS High Sierra
 4    041-01261      10.14  18A377a  macOS Mojave Beta

 

I'm guessing 17G2208 is fine to use, will try with it and let you know. And follow the guide thanks.

 

I tried a lot for graphics acceleration but no success. I'm attaching all the debug info, clover kext files are at bootlog.txt end. 

I never succeed in generating /AppleIntelFramebuffer_GEN_KERNX_Y file in my EFI folder.

 

can someone help me:

build :
i5-8500, mobo:  Gigabyte B360N WIFI, UHD 630

debug_18225.zip

Link to comment
Share on other sites

6 minutes ago, hack_vel said:

I never succeed in generating /AppleIntelFramebuffer_GEN_KERNX_Y file in my EFI folder.

 

It gets generated to the root of your boot drive (as the guide states). You can also use the Framebuffer->macOS 10.13.6 (17G2112) menu option.

Link to comment
Share on other sites

On 9/1/2018 at 12:03 PM, tikizondo94 said:

Im currently using 59120000 to get acceleration which i know is not the correct one for my UHD620.

 

FYI A bug was recently fixed in WhateverGreen when CFL is spoofing KBL. Try the latest master.

Edited by headkaze
Link to comment
Share on other sites

 
FYI A bug was recently fixed in WhateverGreen when CFL is spoofing KBL. Try the latest master.
I'll give it a shot. Id given up since I could only get QE/CI running via external monitor. I'll grab the latest build. Leave devices/properties blank or do you think adding platform/device ID is needed?

Sent from my ONEPLUS A5010 using Tapatalk

Link to comment
Share on other sites

3 minutes ago, tikizondo94 said:

I'll give it a shot. Id given up since I could only get QE/CI running via external monitor. I'll grab the latest build. Leave devices/properties blank or do you think adding platform/device ID is needed?

Try injecting the KBL platform-id.

Link to comment
Share on other sites

On 8/21/2018 at 5:58 AM, Slice said:

Why this thread in DSDT section? May be move it into

https://www.insanelymac.com/forum/175-intel/

Or into Developement section?

As this tool is very useful, the newbies need to "see" it.

Another option is put it in: New Releases and Updates section

 

Or if this tool are a "Lilu" complement, you can move it to the Lilu and plugins section

Link to comment
Share on other sites

17 hours ago, Allan said:

As this tool is very useful, the newbies need to "see" it.

Another option is put it in: New Releases and Updates section

 

Or if this tool are a "Lilu" complement, you can move it to the Lilu and plugins section

 

Yeah I'm not entirely sure where it should go. It is in many ways a companion tool for WhateverGreen so perhaps the Lilu and plugins section would be best?

  • Like 1
Link to comment
Share on other sites

On 9/13/2018 at 12:25 PM, headkaze said:

Try injecting the KBL platform-id.

Still seem to be having the same issue. Tried the usual 0x59160000 and 0x591B0000. Using the lated 1.3.5 FBPatcher. Still locks at IOScreenLockState. :blink:

Link to comment
Share on other sites

1 hour ago, tikizondo94 said:

Does this look correct? I added the CNConnectorAlwaysConnected flag to "off". Plist attached

config.plist.zip

Yes that does look correct. Just a few other things to note:

 

- Don't rename GFX0 -> IGPU (WEG does this)

- Try setting Graphics/EDID/Inject=true / ProductID=0x9c7c

- Only set ProductName / BoardSerialNumber / SerialNumber / SmUUID in SMBIOS

- Remove RtVariables/MLB / ROM

- Remove KextsToPatch/minStolenSize patch

- Maybe try SMBIOS/ProductName/MacBookPro14,2 or others?

- If you're sure you've changed your DVMT pre-alloc to 64 MB or higher in BIOS don't use the "DVMT pre-alloc 32 MB" patch

- Make sure you don't have any custom kexts in /L/E and /S/L/E (sort files by date to make it easier to find any)

- Remove all files from CLOVER/ACPI/patched

- Run "sudo kextcache -i /" from Terminal to rebuild your kext cache

 

Now if all that fails I think you need to experiment with your connectors. Try changing the Type of connector 0 first. Then maybe try different Index / Bus Id / Pipe / Type / Flags values. It's a lot trial and error and rebooting but you may find a setting that works for you. I would also search the forums for similar configs and see if anyone has a patch that worked for them.

 

I've also seen patches that change the order of connectors. There is a new patch method called "AllData" in the latest WEG that can make it easier to do a patch like this. It's also an option in the latest Intel FB-Patcher.

 

Eg. 

Key: framebuffer-con0-alldata
Value: <01050900 00080000 c7010000 02040a00 00040000 c7010000 03060a00 00040000 c7010000 00000800 02000000 98000000>

I personally don't have any experience changing the order of connectors but it's something some configs require.

Edited by headkaze
Link to comment
Share on other sites

@headkaze

Hello i found something to fix about iASL DSL output.

 

Now it shows

Device (IGPU)
"model", Buffer() { "Intel HD Graphics 530" },
"hda-gfx", Buffer() { "onboard-1" },
"enable-hdmi20", Buffer() { 01, 00, 00, 00 },
"device-id", Buffer() { 1B, 19, 00, 00 },
"AAPL,ig-platform-id", Buffer() { 00, 00, 1B, 19 },

But when it be aml it will be this 

Device (IGPU)
"model", Buffer() { "Intel HD Graphics 530" },
"hda-gfx", Buffer() { "onboard-1" },
"enable-hdmi20", Buffer() { 0x01, 0x00, 0x00, 0x00 },
"device-id", Buffer() { 0x01, 0x13, 0x00, 0x00 },
"AAPL,ig-platform-id", Buffer() { 0x00, 0x00, 0x01, 0x13 },

It was convert to hex code so it cant use now.

 

So i suggest to fix this.

Method 1:

Device (IGPU)
"model", Buffer() { "Intel HD Graphics 530" },
"hda-gfx", Buffer() { "onboard-1" },
"enable-hdmi20", Buffer() { 01, 00, 00, 00 },
"device-id", Buffer() { 27, 25, 00, 00 },
"AAPL,ig-platform-id", Buffer() { 00, 00, 27, 25 },

 

Method 2:(I prefered)

Device (IGPU)
"model", Buffer() { "Intel HD Graphics 530" },
"hda-gfx", Buffer() { "onboard-1" },
"enable-hdmi20", Buffer() { 0x01, 0x00, 0x00, 0x00 },
"device-id", Buffer() { 0x1B, 0x19, 0x00, 0x00 },
"AAPL,ig-platform-id", Buffer() { 0x00, 0x00, 0x1B, 0x19 },

Thanks for your nice work!

Edited by gujiangjiang
Link to comment
Share on other sites

Hi, the first (info screen) shows sandy bridge CPU generation, but should be ivy bridge i think. I tried older version ( 6-8 weeks agao) and i think there was shown correct cpu gen for my i5-3570K.  Platform-ID (by clover)is like shown in the upper right select box. But in system info 00000.

From where  / How get the app the System Info data? 

 

 

Bildschirmfoto 2018-09-21 um 07.21.42.jpg

  • Like 1
Link to comment
Share on other sites

26 minutes ago, mitch_de said:

Hi, the first (info screen) shows sandy bridge CPU generation, but should be ivy bridge i think. I tried older version ( 6-8 weeks agao) and i think there was shown correct cpu gen for my i5-3570K.  Platform-ID (by clover)is like shown in the upper right select box. But in system info 00000.

From where  / How get the app the System Info data? 

 

 

Bildschirmfoto 2018-09-21 um 07.21.42.jpg

 

Same here with latest and old version :cry:

Link to comment
Share on other sites

I am having trouble getting my Coffee Lake HD 630 3e92 (dual HDMI) working properly with frame buffers because I have transparency issues with tab menus and many apps in Mojave and High Sierra.  I am trying this utility and was wondering what the value of device-id is supposed to be.  When I use the generated value (923e0000) from the app the PC  reboots mid way through the boot.  When I take out device-id I get no video but the PC seems to work and it apparently will go to sleep mode.  When I swap the value to a normal id 3e920000 I get the transparency issue.

 

Martin

Link to comment
Share on other sites

×
×
  • Create New...