Hackintool v3.x.x

[miliuco]

1 hour ago, eSaF said:

Seems to be ok on mine.

Also it's running fine on my system.

[duffs]

warning when started from terminal.

2021-11-28 03:26:56.921 Hackintool[24907:2985710] Warning: Column selection is not supported in view-based table and outline views (<NSTableView: 0x7feeae03f600>).

[deeveedee]

I upgraded to Hackintool 3.7.4 on my rig running Big Sur 11.6.1 and found that Hackintool 3.7.4 does not display any of my installed Extensions.  If I revert to Hackintool 3.6.1, my extensions are displayed.

 

My rig is as described here with the EFI attached to Post #1 in that thread.  My system details are below:

 

• OpenCore 0.7.5
• OS: Big Sur 11.6.1
• Extensions (as viewed with Hackintool 3.6.1):
  Spoiler

  

  
   

EDIT: I ran Hackintool 3.7.4 from terminal:

Spoiler

 

Edited November 28, 2021 by tonyx86
Added note about running from terminal

[Matgen84]

On 11/25/2021 at 6:59 PM, headkaze said:

My guess is an exception is occurring on startup. Can you run it from Terminal and post the log here.

 

Hi @headkaze
 

Test: Ivybridge (Catalina, Clover )
Hackintool v 3.7.4 stucks at empty NSArray: Kexts windows is empty, some peripherals have disappeared... (Audio output, frame buffer, for example).

 

2021-11-28 08:38:10.230 Hackintool[1021:20186] Hackintool v3.7.4
2021-11-28 08:38:10.263 Hackintool[1021:20186] Initializing Bundle Data
2021-11-28 08:38:10.320 Hackintool[1021:20186] Initializing PCI
2021-11-28 08:38:10.474 Hackintool[1021:20186] Initializing Displays
2021-11-28 08:38:10.533 Hackintool[1021:20186] Initializing General
2021-11-28 08:38:10.534 Hackintool[1021:20186] macOS Version: Version 10.15.7 (assemblage 19H1519)
2021-11-28 08:38:10.534 Hackintool[1021:20186] Model Identifier: iMac13,2
2021-11-28 08:38:10.534 Hackintool[1021:20186] IntelGen: Ivy Bridge
2021-11-28 08:38:10.534 Hackintool[1021:20186] PlatformID: 0x01620007
2021-11-28 08:38:10.535 Hackintool[1021:20186] IGPU: Intel Graphics HD4000 (Desktop 7 Series) (0x01628086)
2021-11-28 08:38:10.662 Hackintool[1021:20186] Initializing Settings
2021-11-28 08:38:10.666 Hackintool[1021:20186] Initializing Menus
2021-11-28 08:38:10.666 Hackintool[1021:20186] Initializing Bootloader
2021-11-28 08:38:10.860 Hackintool[1021:20186] Initializing USB
2021-11-28 08:38:11.021 Hackintool[1021:20186] Found USB Controller: EH01 7 Series/C216 Chipset Family USB Enhanced Host Controller #1 (7/C210-series) Controller (0x1E268086)
2021-11-28 08:38:11.021 Hackintool[1021:20186] Found USB Controller: EH02 7 Series/C216 Chipset Family USB Enhanced Host Controller #2 (7/C210-series) Controller (0x1E2D8086)
2021-11-28 08:38:11.021 Hackintool[1021:20186] Found USB Controller: XHC 7 Series/C210 Series Chipset Family USB xHCI Host Controller (7/C210-series) Controller (0x1E318086)
2021-11-28 08:38:11.021 Hackintool[1021:20186] Initializing Disks
2021-11-28 08:38:11.024 Hackintool[1021:20186] Initializing Info
2021-11-28 08:38:11.382 Hackintool[1021:20186] *** -[__NSArray0 objectAtIndex:]: index 0 beyond bounds for empty NSArray

 

[headkaze]

Please try v3.7.5

[Matgen84]

30 minutes ago, headkaze said:

Please try v3.7.5

 

Thanks. Works fine.

 

Spoiler

 

 

Spoiler

 

[deeveedee]

@headkaze Thanks for the quick reply! v3.7.5 fixes the Extensions listing.

[whatnameisit]

Hi, @headkaze

Hackintool is downloading OpenCore Configuration.pdf instead of the Release package.

The Acidanthera team has changed their release format and that may be causing Hackintool to download the PDF only. Please take a look

 

 

Edit: I just noticed the release had errors in the docs and so they latter added the corrected ones.

Edited December 9, 2021 by whatnameisit

[headkaze]

Should be fixed in the latest release

[duffs]

Hi ! 

i still have problems with the app, have to force quit it.

 

[headkaze]

20 hours ago, duffs said:

i still have problems with the app, have to force quit it.

Any chance you can run it in Xcode to determine where it's hanging?

[miliuco]

@duffs @headkaze

Here 3.7.8 runs fine in Xcode and standalone.

[duffs]

in xcode i could build it and it loads, but it hangs. After forcequit i got sendtoapple error log if it helps. I'm not xcode expert and i dont know how to debug this. Console output in xcode looks the same as in terminal.

 

 

Edited December 16, 2021 by duffs

[miliuco]

@duffs

It doesn't nothing to do with this but I see you have -lilubetaall and -wegbeta in boot-args. Do you really need them? Current Lilu and WEG versions don't need this args.

[duffs]

im running Monterey 12.1 (21C52) beta.

[miliuco]

27 minutes ago, duffs said:

im running Monterey 12.1 (21C52) beta.

Ok. But 21C52 is already non beta. I think you can try without those args. They are not intended to use with macOS beta but to enable Lilu and all loaded plugins on unsupported os versions. Monterey is well supported by Lilu and WEG.

[duffs]

Removed beta args. Using it from when moterey was new and not supported by plugins. no change tho. What i found out is when i restart computer Hackintool app will work. Now im about 2h in and it stoped again. strange.

 

[duffs]

ok. So it looks like it's working, but it takes around 3 to 6 minutes to load.

[headkaze]

15 hours ago, duffs said:

ok. So it looks like it's working, but it takes around 3 to 6 minutes to load.

Yes unfortunately if I can't find a 3rd party Bluetooth device in IORegistry I'll call "system_profiler SPBluetoothDataType -xml" to see if there are any native Bluetooth devices.

 

I try to avoid calling shell commands as much as possible for this reason but I have yet to find a reliable way to get a list of native Bluetooth devices on a system.

 

In the Hackintool function getNativeBluetoothDeviceInfo() I need to find devices that Chipset is not determined to be a "THIRD_PARTY_DONGLE". The problem is macOS will open the USB device in exclusive mode so I cannot simply discover the chipsetID and determine it the way bluetoothd does.

 

Once we have the ChipsetID we know that bluetoothd simply checks against a list of hard-coded id's:

const char *getBluetoothChipset(int chipsetID)
{
    const char *result;

    if (chipsetID > 1999)
    {
        switch (chipsetID)
        {
            case 2000:
                return "APPLE_M1";
            case 2001:
                return "APPLE_M2";
            case 2002:
                return "APPLE_M2_5";
            default:
                return "Unknown Chipset";
        }
    }
    else
    {
        result = "THIRD_PARTY_DONGLE";
        switch (chipsetID)
        {
            case 0:
                return result;
            case 1:
                result = "BCM_4350C2";
                break;
            case 2:
                result = "BCM_20702A3";
                break;
            case 3:
                result = "BCM_20702B0";
                break;
            case 4:
                result = "BCM_4350";
                break;
            case 5:
                result = "BCM_4350A0";
                break;
            case 6:
                result = "BCM_4350C5";
                break;
            case 7:
                result = "BCM_20703A1";
                break;
            case 8:
                result = "BCM_20703A2";
                break;
            case 9:
                result = "BCM_43430";
                break;
            case 10:
                result = "BCM_43452";
                break;
            case 11:
                result = "BCM_4355B3";
                break;
            case 12:
                result = "BCM_4355C0";
                break;
            case 13:
                result = "BCM_4355C1";
                break;
            case 14:
                result = "BCM_4355";
                break;
            case 15:
                result = "BCM_4357";
                break;
            case 16:
                result = "BCM_4364";
                break;
            case 17:
                result = "BCM_4364B0";
                break;
            case 18:
                result = "BCM_4364B3";
                break;
            case 19:
                result = "BCM_4377";
                break;
            case 20:
                result = "BCM_4378";
                break;
            case 21:
                result = "BCM_4387";
                break;
            default:
                return "Unknown Chipset";
        }
    }
    return result;
}

 

Edited December 16, 2021 by headkaze

[duffs]

i see. I'm not using Bluetooth. i have [050d:065a] Belkin (20702) BCM20702A0 usb to test. BlueToolFixup.kext and bt works. app loads normaly but it did on fresh boot. will see in few hours. 

 

[kaoskinkae]

My question is because a tab of the loaded drivers is not added and the version of these in many cases some of their update errors come from not properly updating these .efi or having too obsolete or unused

[deeveedee]

@headkaze Happy New Year!

 

I was reading the Hackintool 3.8.4 context-sensitive help for patched framebuffer Indices (below) and am more confused about connector indices than before I read your help.  In your help, you give an example "Say, we have 2 active ports" where connectors 0-3 are listed with indices 1, 2, 3, -1.   Why is this list of 4 connectors with 1 dummy connector only considered to be 2 active ports and not 3 active ports and a dummy?

 

EDIT: Is it because LVDS connector type must always have Index 0 (connector with type LVDS but non-zero Index is ignored)?

 

Hackintool 3.8.4 Context-Sensitive Help for patched framebuffer Indices

Spoiler

 

Edited January 9, 2022 by tonyx86
Updated Hackintosh version to 3.8.4

[headkaze]

On 1/6/2022 at 1:03 PM, tonyx86 said:

@headkaze Happy New Year!

 

I was reading the Hackintool 3.8.4 context-sensitive help for patched framebuffer Indices (below) and am more confused about connector indices than before I read your help.  In your help, you give an example "Say, we have 2 active ports" where connectors 0-3 are listed with indices 1, 2, 3, -1.   Why is this list of 4 connectors with 1 dummy connector only considered to be 2 active ports and not 3 active ports and a dummy?

 

EDIT: Is it because LVDS connector type must always have Index 0 (connector with type LVDS but non-zero Index is ignored)?

 

Hackintool 3.8.4 Context-Sensitive Help for patched framebuffer Indices

Yes, LVDS must always be index 0.

 

The full document you should read is IntelFramebuffer.bt

[kaoskinkae]

Why the SSDT-EC-USBX.aml when creating it is called like that when it should be SSDT-USBX.aml since the EC is not included since the new versions?

[miliuco]

43 minutes ago, kaoskinkae said:

Why the SSDT-EC-USBX.aml when creating it is called like that when it should be SSDT-USBX.aml since the EC is not included since the new versions?

OpenCore package has SSDT-EC-USBX.aml and SSDT-EC.aml but not SSDT-USBX.aml. I haven't read anywhere what you are saying.