How to Fix iMessage

[esafeddie]

@kajaba - You just need to remove the problematic machine from your Apple account.
If your other devices are working with your Apple ID as expected, then there is no need to remove those.
As advised, you should re-generate completely new S/N, SmUUID, ROM, MLB and enter into config.plist.

After entering the new data, reboot, clean NvRAM, continue to Desktop but do not logon to any Apple Services (i.e App Store, iMessage, F/Time, iCloud etc) just yet, just give it a couple of hours or so and then try.
Good luck.

 

[esafeddie]

This exact problem is also with other apple ids on this machine (different accounts).

Ahhh - I just read this potion of your post again.
This possibly points to wrong format of entered data i.e SmUUID, ROM or S/N.
Looking through your previous posts, I would advise to not only change the S/N, SmUUID etc, but definitely change the ROM value to your actual Apple Address
which can be found in Systems Settings/Network.


(See my attached example)

 

[kajaba]

Thank again guys. But I dont get it:
I generated smbios with getSMBIOS. This tool will generate SN, SmUUID, MBL and ROM.
Every time when I was changing SN, I changed all these values - also ROM
Is this wrong? Should I use my real eth MAC address as ROM? In guide there is stated, that ROM can be any generated value (even real Apple MAC hw address).
And with wrong format: SN, SmUUID,MBL are simple strings. ROM is a data value from Mac address. I will try these values (from my config.plist):
<key>MLB</key>
<string>C029------LNV91M</string>
<key>ROM</key>
<data>tC6Zq7gJ</data>
<key>SystemProductName</key>
<string>iMac19,1</string>
<key>SystemSerialNumber</key>
<string>C02-----V3Q</string>
<key>SystemUUID</key>
<string>AD-----A-F35C-4C18-AD87-552------1EF</string>

And i forgot: I used iMacPro1,1 because I do not have iGPU in my CPU.
And also I notices that after signing in to icloud in settings a window pops up like this. But after that it normally signs in.

 

[esafeddie]

Is this wrong? Should I use my real eth MAC address as ROM?

I have always used my real MAC Address in all my Builds.
By your admission, it is not just your Apple ID that is not accepted in this machine but other Apple IDs as well.
Something is definitely off between your Machine and the inserted data.

The iMacPro1.1 model has nothing to do with the problem.
The fact you can logon to iCloud is irrelevant I think, it's the other Services you're not allowed to join.

It's been so long since I have delved into the 'Wherefores and Whatnots' of iMessage but if you can find iMessage Logs, somewhere you should see if a Security Token was granted or denied.
Of course I am going way, way back to the early introduced iMessage days when iMessage setup was more problematic. Things may have changed slightly with Monterey, Ventura and now Sonoma.

On all my Builds as soon as I put my Apple ID into the machine, all Apple Services are available automatically.
What you are experiencing, I really thought was a thing of the past.
I don't know if this is wise to suggest but if you own a real Mac and it is registered to you, copy the data to your Hack i.e S/N, SmUUID, ROM and MLB and see if the machine is accepted DO NOT HAVE BOTH LOGGED IN AT THE SAME TIME.

In essence, you would be cloning the machine (which is not a good idea) hence the reason I said to do this only if the genuine Mac is owned by you. It is not a long term fix, this is just to see if the Hack is prohibited on Apple Services with it's own generated credentials.

 

[kajaba]

I looked on logs in console and I will paste here some lines, that might be relevant to this:

BEGIN [436]: AuthenticateWithContext  AuthenticationType=__##__signpost.telemetry#____#number1#_##_#2##__##  ProxiedBundleID=__##__signpost.telemetry#____#string1#_##_###__##  enableTelemetry=YES

Context ID <private> has already been registered for authentication!

Error authenticating: Error Domain=AKAuthenticationError Code=-7086

Attempting to perform block in persona: (null)
No persona ID on account proceeding without setting context.

"No plugin provides credentials for account <private>. Falling back to legacy behavior."

[com.apple.MobileSMS:C522DE0F-B063-4D03-B90B-7D45F57DF2C7] Error when getting current app configuration for action identifier <private>, error='Error Domain=DNDErrorDomain Code=1007 "No current action is available. Supply the caller with the default." UserInfo={NSLocalizedDescription=No current action is available. Supply the caller with the default.}'

Couldn't read values in CFPrefsPlistSource<0x7f872941af60> (Domain: com.apple.CloudKit, User: kCFPreferencesCurrentUser, ByHost: No, Container: (null), Contents Need Refresh: Yes): accessing these preferences requires user-preference-read or file-read-data sandbox access

CoreData: Unable to create token NSXPCConnection.  NSXPCStoreServerEndpointFactory 0x7f8f6f32c230 -newEndpoint returned nil

Ok, I tried to use SN, SMUUID, ROM and MLB of my genuine macbook air (while using iMac19,1 as SystemProductName) but it does not work.
I think that there is some HW misconfiguration or something not related with SN/MLB/ROM because Iam quite sure I make the smbios setup correct.

Note: I am part of iCloud family sharing (not admin). Could be some problem here?

 

[esafeddie]

Note: I am part of iCloud family sharing (not admin). Could be some problem here?

Sorry man, I am completely stumped. Data format and entries all ok.
Ethernet=en0, Wi-Fi=en1 which is correct so I don't understand what is going on with your machine.

 

[kajaba]

you may also want to re generate SmUUID, ROM and MLB as mentioned above

Ofc I generated all SmUUID, MLB and ROM, but it does not work..Actually I dont know what to do more

 

[kajaba]

Will be anybody so kind and try to help me debug this? On my other macMini build is everythong ok (but there is ventura installed)

 

[kajaba]

Omg I figured it out.
I have intel cnvi wifi and used itlwm utility. But not itlwm.kext but Airport Itlwm.kext wit limited functionality.

 

[t80u]

Hi! Just to say thanks for this guide, I can confirm that the method described on Chapter 8 is still valid. I've installed High Sierra on a PC and got the "contact support" message, I did it and gave the customer code to the advisor and it solved the issue