Failed to Verify Your Identity. Try Again Apple Id Changed Password

# Fixing iMessage and other services with OpenCore

This page is for those having iMessage and other iServices bug, this is a very basic guide so will not get as in-depth into the issues as some other guides. This specific guide is a translation and reinterpretation of the AppleLife Guide on fixing iServices: Как завести сервисы Apple tree - iMessage, FaceTime, iCloud (opens new window) .

Your Apple ID is the unmarried nigh influential cistron in using iServices.

If you have existing Apple tree products in your account, such as an iPhone, you should have no issues whatsoever using a generated series gear up. Nonetheless, if you lot recently created an account, that does non have any existing Apple tree hardware or App Store purchases, yous may exist required to call Apple in one case yous have attemped logging in.

The post-obit items will be created below and are required to use iServices:

• MLB
• ROM*
• SystemProductName
• SystemSerialNumber
• SystemUUID

*for ROM, we use the MAC Address of the network interface, lowercase, and without :.

Note: You and y'all alone are responsible for your AppleID, read the guide carefully and take full responsibility if you screw up. Dortania and other guides are not held accountable for what you lot do.

# Using GenSMBIOS

Download GenSMBIOS (opens new window) and select choice 1 to download MacSerial and next pick 3 to generate some new serials. What we're looking for is a valid serial that currently has no registered purchase date.

Tip: iMacPro1,1 ten will print 10 serials, this will save you some time on generating

# Using macserial

This is for Linux users and an alternative to using GenSMBIOS.

Generate a new Serial and Board Series (MLB) for your model.

To generate this you lot volition demand macserial.

You tin download the latest release of OpenCorePkg from hither. (opens new window)

Or compile the development macserial (opens new window) from source.

Notice your SystemProductName in your config.plist file. That is your model number.

Supercede "iMacPro1,1" below with SystemProductName in your config.plist.

Example output:

The value on the left is your Serial number. The value on the right is your Lath Serial (MLB).

# Choose a MAC Address

Select a MAC Address with an Organizationally Unique Identifier (OUI) that corresponds to a real Apple, Inc. interface.

See the following list:

https://gitlab.com/wireshark/wireshark/-/raw/master/manuf (opens new window)

For example:

Make upwards the concluding 3 octets.

For example:

# Derive the respective ROM Value

ROM is calculated from your MAC Address.

Lowercase your MAC Address, and remove each colon : betwixt the octets.

For example:

MAC: 00:16:CB:00:11:22

ROM: 0016cb001122

# Generate an UUID

Type uuidgen in Terminal

So merely supercede those values in your config.plist:

Key	Data
MLB	C02733401J9JG36A8
Mac Address	00:xvi:CB:00:11:22
ROM	0016cb001122
SystemProductName	iMacPro1,i
SystemSerialNumber	C02V7UYGHX87
SystemUUID	976AA603-75FC-456B-BC6D-9011BFB4968E

It should expect something like this:

Notation: If you have trouble using the App Store, you may need to fix En0, depending on your hardware setup.

Brand new Apple ID's volition nearly certainly not work. Having other existent devices in your account nigh always works.

If yous see a support warning, see beneath.

# Serial Number Validity

At present enter the serial into the Apple Check Coverage page (opens new window) , you will go 1 of 3 responses:

We're sorry, but this serial number isn't valid	Valid Purchase date	Purchase Date not Validated

This last ane is what nosotros're afterward, as we want something genuine but currently not in apply by anyone. Now we can interpret the residual of the values into our config.plist -> PlatformInfo -> Generic:

• Type = SystemProductName
• Serial = SystemSerialNumber
• Board Serial = MLB
• SmUUID = SystemUUID

Note: "We're deplorable, just this serial number isn't valid. Delight check your data and effort again." works for many users equally well, do note though if you've had a bad rails record with Apple tree/iServices you many need one that's "Purchase Date non Validated". Otherwise there may be suspicion

Notation ii: Using a "Buy Engagement not Validated:" tin can cause issues down the line if another automobile of the aforementioned series ever gets activated, for initial setup it tin can assistance convalesce issues with your account but in the long run an invalid serial can be a safer choice.

Annotation 3: Checking also many serials may result in you existence ratelimited. To bypass this limitation you tin try immigration your cookies or changing your IP.

# Fixing En0

To first, grab Hackintool (opens new window) (Github link (opens new window) ) and head to System -> Peripherals (Info -> Misc on older versions of Hackintool)

Here under Network Interfaces (network menu icon), look for en0 under BSD and check whether the device has a bank check mark under Builtin. If there is a check mark, skip to Fixing ROM department otherwise go on reading.

• Annotation: en0 can be either Wifi, ethernet or even Thunderbolt.

What if I don't take En0 at all?!?

Well, we'll want to reset macOS so it can build the interfaces fresh, open terminal and run the following:

Once washed reboot and cheque again.

If this doesn't work, add NullEthernet.kext (opens new window) and ssdt-rmne.aml (opens new window) to your EFI and config.plist under Kernel -> Add together and ACPI -> Add together respectively. The SSDT is precompiled then no extra work needed, reminder compiled files take a .aml extension and .dsl tin can exist seen equally source code.

Now head nether the PCI tab of Hackintool and export your PCI DeviceProperties, this volition create a pcidevices.plist on your desktop

Now search through the pcidevices.plist and find the PciRoot of your ethernet controller. For united states, this would be PciRoot(0x0)/Pci(0x1f,0x6)

Now with the PciRoot, go into your config.plist -> DeviceProperties -> Add and use the property of built-in with type Data and value 01

# Fixing ROM

This is a section many may accept forgotten nearly but this is institute in your config.plist under PlatformInfo -> generic -> ROM

To find your actual MAC Address/ROM value, you tin find in a couple places:

• BIOS

• macOS: Arrangement Preferences -> Network -> Ethernet -> Advanced -> Hardware -> MAC Accost

• Windows: Settings -> Network & Internet -> Ethernet -> Ethernet -> Physical MAC Address

• Note: en0 can be either Wifi, ethernet or even Thunderbolt, accommodate the to a higher place example to your situation.

Some users have fifty-fifty gone every bit far every bit using real Apple MAC Address dumps for their config, for this guide we'll be using our real MAC Address just note that this is some other option.

When calculation this to your config, c0:7e:bf:c3:af:ff should exist converted to c07ebfc3afff equally the Information type cannot take colons(:).

# Verifying NVRAM

Something that many forget about iServices is that NVRAM is crucial to getting it working correctly, the reason beingness is that iMessage keys and such are stored in NVRAM. Without NVRAM, iMessage can neither come across nor store keys.

So we'll need to verify NVRAM works, regardless if "it should piece of work" as some firmwares can exist more of a pain than others.

Delight refer to the Emulated NVRAM section of the OpenCore Guide for both testing if you take working NVRAM and emulating information technology if you don't.

# Clean out erstwhile attempts

This is of import for those who've tried setting up iMessage but failed, to outset make sure your NVRAM has been cleared. You tin can enable the option in the boot picker in your config under config.plist -> Misc -> Security -> AllowNvramReset.

Adjacent open terminal and run the post-obit:

# Verifying your piece of work i last time

Grab macserial from the latest OpenCore release (opens new window) and run the following:

This volition provide us with a full rundown of our system, verify that what is presented matches up with your work.

# Cleaning up your AppleID

• Remove all devices from your AppleID: Manage your devices (opens new window)
• Enable 2 Factor-Auth
• Remove all iServices from Keychain, some examples:

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.

Tip: Adding a payment carte du jour to the business relationship and having a decent corporeality of purchases can also help. While not concrete, you can retrieve of an AppleID as a credit score where the better an Apple customer you are the more likely they won't accept activation issues or get an easier pass with AppleSupport

# Client Code error

Well mate, you've done it. You lot blacklisted your AppleID. The fix is simple but not pretty, you MUST call Apple (opens new window) . Otherwise, at that place is no proceeding besides using a new account. Adding a payment card before calling tin can assistance legitimize the account and then it doesn't seem as much like a bot.

• For Apple tree contacting, there are 2 methods
  • Apple calls y'all: Apple Support (opens new window) . You must click on Apple tree ID and then select the iCloud, Facetime & Messages. At present, you lot should click on Talk to Apple Back up Now and type your telephone number
  • You can contact Apple for support and service as well, wait for your land in the list so make a telephone call: Apple Support Phone Numbers (opens new window)

marrowhird1974.blogspot.com

Source: https://dortania.github.io/OpenCore-Post-Install/universal/iservices.html

Share this post