How to Fix t460s with OC 0.9.9 Sonoma or Ventura on macOS
Wi-Fi, Bluetooth, AWDL, Continuity and Location Services problems usually come from chipset support, kext pairing, privacy settings or network-location corruption. On Hackintosh systems, Location Services and Continuity depend on working Wi-Fi, Bluetooth, AWDL and correct AirportItlwm or itlwm/HeliPort behaviour.
Quick Checks
- Backup current state: Save a copy of your working EFI and run a full system backup before changing settings.
- Identify hardware components: Note down your exact CPU, GPU, Wi-Fi card, and motherboard/laptop model.
- Ensure utility alignment: Keep OpenCore, OCLP, and ProperTree updated.
Fix Steps
- Create a rollback point: Make a Time Machine backup and keep a copy of your last working EFI folder before editing OpenCore, kexts or root patches.
- Confirm the exact chipset: Identify the Wi-Fi, Bluetooth and Ethernet controller from System Information, Hackintool or Linux/Windows device manager.
- Use the correct network stack: Match AirportItlwm, itlwm, HeliPort, IntelBluetoothFirmware and BlueToolFixup to the exact macOS version.
- Reset macOS network state: Remove the current Wi-Fi service, reboot, add it again, then reconnect to a simple WPA2 network before testing advanced features.
- Check privacy permissions: Open System Settings and confirm Location Services, Maps, Weather and system services are enabled.
- Test Apple features separately: Verify normal internet first, then Bluetooth, then AirDrop/Continuity. Do not debug all three at the same time.
Do Not Continue If
- Do not continue if: you do not have a working EFI backup, a Time Machine backup, or another bootable macOS installer.
- Stop and capture evidence: if the machine stops booting, take a photo of the last verbose line before changing more settings.
Verify It Worked
- Maps can locate you without falling back to a stale location.
- Wi-Fi reconnects after reboot and sleep.
- Bluetooth remains available after a cold boot.
- Console no longer shows repeated wireless or location daemon errors.
Rollback
- Restore the previous EFI if Wi-Fi disappears completely.
- Switch from AirportItlwm to itlwm + HeliPort, or the reverse, if the issue is specific to one driver path.
- Use Ethernet or USB tethering while testing so you do not lose access to downloads.
Next Action
- Test now: reboot twice, reproduce the original problem, and confirm whether the same symptom returns.
- If it still fails: record the Mac model, macOS build, OpenCore or OCLP version, GPU, Wi-Fi/Bluetooth chipset, and the last visible error.
- Read next: use the related searches below for the nearest OpenCore or OCLP fix before making another change.
Related iATKOS Searches
- OpenCore · OCLP · EFI · kexts · config.plist · macOS troubleshooting
Original Question: "Help with t460s with OC 0.9.9 Sonoma or Ventura"
This is my first time attempting anything with building a hackintosh. I was following this github repo to use on one of my old t460s laptops. https://github.com/simprecicchiani/ThinkPad-T460s-macOS-OpenCore
The only difference with my t460s is I have a 1440 LCD and no touch. I can get into and past OC fine, but when the apple logo appears and the loading bar gets maybe 15% done, system reboots for Sonoma.
From Hardware Compatibility in the github Readme:
2. 1440p displays should change NVRAM -> Add -> 7C436110-AB2A-4BBB-A880-FE41995C9F82 -> UIScale:2 to get proper scaling while booting. However, I'm uncertain if this is correct? Opening the plist in OCAT I get a warning for another error. But I do not see UIScale where it is described. I tried adding, did not make a difference. Pic of OCAT: https://i.imgur.com/onrFfkL.png
OCAT also throws this error after loading the plist:
UEFI->Output->InitialMode is illegal (Can only be Auto, Text, or Graphics)! CheckUefi returns 1 error! Which I have also tried setting to 'Auto' with and without UIScale added and set to '2' under NVRAM 7C43.....C9F82 did not change anything either way, still rebooting when the loading bar on the apple logo gets maybe 15% or so.
Attempted to use Ventura, which boots into MacOS recovery without any issues. Since the wifi isn't working, I tried to apply the Ventura installer dmg image to my nvme, which applies without any issues. However I cannot boot at all. Acting like there's no EFI boot on the drive, doesn't attempt anything. Not sure if this is just some issue with the way I am installing or something else. Will mess with it more today.
I'm new to this, so I don't really know fully what I am doing. Just thought I would post this here if anything to relay some issues I have had and maybe someone down the line may find this information useful for reasons.
Running OC 0.9.9 tried with Sonoma and Ventura. Laptop is a t460s same specs as the readme, but non-touch and 1440p LCD. Have verified all bios settings match the settings described in the readme.
[link] [comments]
Post a Comment