The New Beginner's Guide to USB Port Configuration

@Feartech I have still the same issue.

madman1234 said:

I did not change this. That was like this by default when I use HackinTool

Click to expand...

Remember too that the USBPorts.kext does NOT have an ExecutablePath entry in the config.plist. You have one in there and this is incorrect. Leave that field blank and just populate PlistPath.

Yes, you will see the up/down arrows to the right of the connector type, you must choose the right connector for each port chosen to keep, and I would even do the blocked ports. You should also name all ports in the device column.
USB 3.0 / 3.1.1 and 3.1.2 and C ports will not work properly with internal and or 255 as a connector type.
Only real internal ports for Bluetooth or lighting (HS11 OR HS12) should be internal or 255.
Hackintool does not use the USBMap numbering scheme in the Connector column for creation but the created port Kext does, and this is what the OS needs to decipher the proper interaction with each port.
#######################################################
# USB Types #
#######################################################

Type A: 0 This would be a USB 2.0-only port, not one with a companion 3.0 port.

USB 3 Type A: 3 ALL 2.0/3.0 COMPANION PORTS

Type C - USB 2 only: 8
Type C - with switch: 9
Type C - without switch: 10
Internal: 255

The difference between connector types 9 and 10 is if you reverse the plug and the devices are connected to the same ports as before, they have a switch (type 9).
If not, and they are connected to different ports, they do not have a switch (type 10).
you will see a copy of a portion of the Plist inside the USB Port Kext from you EFI you created in Hackintool:
all the connectors are 255 which is internal, which matches your Hackintool screenprint: SS ports are never internal.,

UtterDisbelief said:

Remember too that the USBPorts.kext does NOT have an ExecutablePath entry in the config.plist. You have one in there and this is incorrect. Leave that field blank and just populate PlistPath.

Click to expand...

Thank you very much, this was the issue. Now all USB Ports show up like I configured them before. Also USB-C works

Ventura macOS 13.0.1

@dasboot5

Great explanation! Very good to know, thank you!

One thing, what is a ITE Device?

madman1234 said:

One thing, what is a ITE Device?

Click to expand...

Usually lighting, (ie the Aorus rgb lighting in the board, lights supplied to your ram if RGB, The ARGB and RGB headers to any add-on lights) The power for these lights are supplied through the USB power circuit of port HS12 which is most likely a USB 2.0 internal port but the Mac OS needs to see this as 255 or internal, for the built-in lighting to work. If you block it, no lights will work, other than HD activity and Pled which is not on the USB circuit at all. Blocking this in the Mac OS only affects the Mac OS not Windows if Dual boot. (ie The lights will work in Windows, but not when booted from the Mac Os when blocked) Sometimes there is a USB 2.0 shared hub tied to this and blocking this kiils the hub as well. You can test if it allows another needed port to be free-ed up to make the magic 15. Asus boards and MSI show up as their brand lighting. Gigabyte shows up as ITE.

Feartech said:

yes

use the drop down option to change them

may need to re enable the quirk and reboot

hit the broom icon and then the refresh button

pop back in your usb2 and usb3 device in each port etc etc

next time, just upload your EFI as a zip

Click to expand...

This does not work in Hackintool for me (not understanding what "quirk" you are referring to). All of my USB connectors are listed as USB3. If I change them through the drop-down menu, they revert back after quitting/reopening Hackintool. Do I need to edit my USBMap.kext instead or use IORegistryExplorer?

Superbogey said:

This does not work in Hackintool for me (not understanding what "quirk" you are referring to). All of my USB connectors are listed as USB3. If I change them through the drop-down menu, they revert back after quitting/reopening Hackintool. Do I need to edit my USBMap.kext instead or use IORegistryExplorer?

Click to expand...

post 1 explains the quirk, also the guide does not use USBMap.kext

Feartech said:

post 1 explains the quirk, also the guide does not use USBMap.kext

Click to expand...

Ahhh. THAT quirk. I've previously done all the steps to create my USBMap.kext... err, USBPorts.kext (Thanks for that. Don't know why I had that named wrong (Older version of Hackintool maybe? <shrug>) even though it did the job, I renamed the kext (and the callout in my OC config.plist) for continuity sake to USBPorts.kext.