How to Fix MacBook Pro 2013 literally dead acting weird after bad uninstalling open core 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: "MacBook Pro 2013 literally dead acting weird after bad uninstalling open core"
 | I don't know what to do. it's killing me that the only way to revive this messy situation is to format the ssd as an external drive. nothing works. the only key combination that work is internet recovery (opt cmd R or opt cmd shift R ). internet recovery get a white prohibited sign with no error code! nothing works. not even resetting the PRAM. I tested with a usb keyboard too but it's completely dead! nothing happens, just a black screen for ever. sometimes it resets itself too that imo, it's common and very normal! I know, I create a usb bootable with Open Core Legacy app on another MacBook but it's dead. keyboard acting weird and caps lock mode inverted! and numbers not working at all, only they symbol alternative like !@#$%%! it's true. help me please. what I do? it was 6 months ago when I get in a bios like environment I don't remover why but remember I delete everything and anything like OC DIR something like that. there was a screen with numbers that do specific jobs and edits to open core legacy in root access. id don't know, what I know is my MacBook Pro bricked. [link] [comments] |
Post a Comment