This page is for those having iMessage and other iServices issues, this is a very basic guide so will not go as in-depth into the issues as some other guides. This specific guide is a translation and reinterpretation of the AppleLife Guide on fixing iService: Как завести сервисы Apple - iMessage, FaceTime, iCloud
Download GenSMBIOS and select option 1 to download MacSerial and next option 3 to generate some new serials. What we're looking for is a valid serial that currently has no registered purchase date.
iMacPro1,1 10 will print 10 serials, this will save you some time on generating
Now enter the serial into the Apple Check Coverage page, you will get 1 of 3 responses:
"We’re sorry, but this serial number isn’t valid. Please check your information and try again.":
Valid Purchase date:
Purchase Date not Validated:
This last one is what we're after, as we want something genuine but currently not in use by anyone. Now we can translate the rest of the values into our config.plist -> PlatformInfo -> Add:
Type = SystemProductName
Serial = SystemSerialNumber
Board Serial = MLB
SmUUID = SystemUUID
To start, grab Hackintool and head to Info -> Misc
Here under Network Interfaces, look for
En0 under BSD Names and check whether the device has a checkmark under Builtin. If there is a checkmark, skip to Fixing ROM section otherwise continue reading.
What if I don't have En0 at all?!?
Well, we'll want to reset macOS so it can build the interfaces fresh, open terminal and run the following:
sudo rm /Library/Preferences/SystemConfiguration/NetworkInterfaces.plistsudo rm /Library/Preferences/SystemConfiguration/preferences.plist
Once done reboot and check again.
If this doesn't work, add NullEthernet.kext and ssdt-rmne.aml to your EFI and config.plist under Kernel -> Add and ACPI -> Add respectively. The SSDT is precompiled so no extra work needed, reminder compiled files have a .aml extension and .dsl can be seen as source code.
Now head under the PCI tab of Hackintool and export your PCI DeviceProperties, this will create a pcidevices.plist on your desktop
Now search through the pcidevices.plist and find the PCIRoot of your ethernet controller. For us, this would be
Now with the PCIRoot, go into your config.plist -> DeviceProperties -> Add and apply the property of
built-in with type
Data and value
This is a section many may have forgotten about but this is found in your config.plist under PlatformInfo -> generic -> ROM
To find your actual MAC Address/ROM value, you can find in a couple places:
macOS: System Preferences -> Network -> Ethernet -> Advanced -> MAC Address
Windows: Settings -> Network & Internet -> Ethernet -> Ethernet -> Phyisical MAC Address
Some users have even gone as far as using real Apple MAC Address dumps for their config, for this guide we'll be using our real MAC Address but note that this is another option
When adding this to your config,
c0:7e:bf:c3:af:ff should be converted to
c07ebfc3afff as the
Data type cannot accept colons(
Something that many forget about iServices is that NVRAM is curtial to getting it working correcttly, the reason being is that iMessage keys and such are stored in NVRAM. Without NVRAM, iMessage can neither see nor store keys.
So we'll need to verify NVRAM works, regardless if "it should work" as some firmwares can be more of a pain than others.
Please refer to the Emulated NVRAM section of the OpenCore Guide for both testing if you have working NVRAM and emulating it if you dont.
This is important for those who've tried setting up iMessage but failed, to start make sure your NVRAM has been cleared. You can enable the option in the boot picker in your config under config.plist -> Misc -> Security -> AllowNvramReset.
Next open terminal and run the following:
sudo rm -rf ~/Library/Caches/com.apple.iCloudHelper* \~/Library/Caches/com.apple.Messages* \~/Library/Caches/com.apple.imfoundation.IMRemoteURLConnectionAgent* \~/Library/Preferences/com.apple.iChat* \~/Library/Preferences/com.apple.icloud* \~/Library/Preferences/com.apple.imagent* \~/Library/Preferences/com.apple.imessage* \~/Library/Preferences/com.apple.imservice* \~/Library/Preferences/com.apple.ids.service* \~/Library/Preferences/com.apple.madrid.plist* \~/Library/Preferences/com.apple.imessage.bag.plist* \~/Library/Preferences/com.apple.identityserviced* \~/Library/Preferences/com.apple.ids.service* \~/Library/Preferences/com.apple.security* \~/Library/Messages
Grab macserial and run the following:
This will provide us with a full rundown of our system, verify that what is presented matches up with your work.
Remove all devices from your AppleID: Manage your devices
Enable 2 Factor-Auth
Remove all iServices from Keychain, some examples:
ids: identity-rsa-key-pair-signature-v1ids: identity-rsa-private-keyids: identity-rsa-public-keyids: message-protection-keyids: message-protection-public-data-registeredids: personal-public-key-cacheiMessage Encryption KeyiMessage Signing Keycom.apple.facetime: registrationV1etc ...
And a final layer of precaution is to make a new AppleID to play with, this makes sure that if you do end up blacklisting your account that it's not your main.
An extra tip is adding a payment card to the account, some users found this also helped with iMessage activation.
Welp mate, you've done it. You blackmailed your AppleID. The fix is simple but not pretty, you MUST call Apple. Otherwise, there is no proceeding besides using a new account. Adding a payment card before calling can help legitimise the account so it doesn't seem as much like a bot.