Guides, Hackintosh, Technology, Tip

Fixing iMessage on Your macOS Sierra Hackintosh

iMessage icon

I wrote a lengthy post the other day about how to build a Hackintosh, and while everything worked pretty smoothly, the one thing I was missing was iMessage. I’d tried to follow a couple of guides, and while they worked at getting iMessage running, all of them without fail stopped my GPU from responding correctly. After a bit of tinkering, though, I finally managed to get everything up and running. Here’s what I did below (MASSIVE thanks to /u/cobo10201 for getting me 99% of the way there I wouldn’t have even known where to begin without that post).

  1. Mount your EFI using EFI Mounter v3
  2. Make a copy of your config.plist and name it config-bak.plist in case something goes wrong.
  3. Open terminal and enter the following command: uuidgen
  4. Open your config.plist in Clover Configurator.
  5. Go to the SMBIOS and paste the UUID you generated in step 2 into the smUUID field.
  6. In the Board Serial Number field, copy and paste your system serial number and then add 5 random numbers and letters.
  7. In Finder go to Go > Go to Folder… and enter the following path: /Users/[Username]/Library/Caches delete all files and folders that begin with the following:
    • com.apple.Messages
    • com.apple.imfoundation.IMRemoteURLConnectionAgent
  8. In Finder go to Go > Go to Folder… and enter the following path: /Users/[Username]/Library/Preferences delete all files and folders that begin with the following:
    • com.apple.iChat
    • com.apple.imagent
    • com.apple.imessage
    • com.apple.imservice
  9. In Finder go to Go > Go to Folder… and enter the following path: /Users/[Username]/Library. Delete the Messages folder.
  10. Open up Disk Utility and run First Aid on the hard drive with your macOS installation.
  11. Reboot the computer!

iMessage and FaceTime should now be up and running (without causing issues to your graphics card). One thing to note, this assumes you followed my previous guide and that everything else was up and running correctly. If you’re following a different guide or are in the middle of troubleshooting a variety of other issues, you may be better off following the original guide I linked to at the top of the post.

Leave a Reply

Your email address will not be published. Required fields are marked *