How to Fix iMessage

[photom]

I didn't claim that it would fix anything, I just pointed out the values that your blank fields should be populated with.

The usual cause of "An error occurred during activation" is a lack of native NVRAM support or an emulation of same.

I have removed OsxAptioFix*.efi from my EFI and replaced it with AptioMemoryFix.efi which has solved the issue. Thank you so much P1LGRIM for pointing me to the right direction.

 

[photom]

I have removed OsxAptioFix*.efi from my EFI and replaced it with AptioMemoryFix.efi which has solved the issue. Thank you so much P1LGRIM for pointing me to the right direction.

This unfortunately created a new problem - after swapping both of these - I get a panic error on shutdown. Any reason why this is happening?

 

[P1LGRIM]

This unfortunately created a new problem - after swapping both of these - I get a panic error on shutdown. Any reason why this is happening?

Off topic in this thread.
Of course there is a reason or it wouldn't happen.
You may need to install EmuVariableUefi-64.efi.

 

[jaymonkey]

UPDATE: I went ahead and changed my system definitions after iMessage was already set up. Luckily the system still booted just fine but it did immediately kick me out of iMessage, iCloud, Adobe, and any other service that are tied to the serial number. Hopefully I’ll just be able to redo the “idiots guide” and get back to where I was.

@Thrashavich & All ....

When ever your going to experiment with different System Definitions (SMBIOS) you should always first logout of all of Apples online services, iCloud, iMessage, iTunes .... etc. Then isolate the system from the internet, then make the changes to the SMBIOS, always generate new id for SerialNo, MLB, ROM ..etc, and check that the new serial number passes the online checks using @P1LGRIM's guide ... once your happy that the changes are ok and that SystemID's/Keys are the same on each boot (use iMessage Debug or Hackintool for this) you can then re-connect to the internet and log back into Apples online services. Failure to follow this procedure may result in activation problems.

Cheers
Jay

 

[PREngineer]

Hello everybody!

I recently upgraded my machine from Sierra to Mojave and I thought that everything was OK because I am able to use Facetime, log into iCloud and log into iMessage (even got the notification "Your Apple ID and phone number are now being used for iMessage on a new Mac."), and sent a text to my own iphone.

But yesterday, while trying to message my cousin (android user) and a friend (iphone user), my texts got stuck and I got the Not Delivered message.

I have read the guide carefully and followed all steps several times but I can't get iMessage to send texts.

-----------------------------------------------------------------------------------------------------------------------------------
I checked and my MOBO does have NVRAM working and all the settings seem correct.

I think that I erased some rc files that I shouldn't have when I realized that I didn't have to have the NVRAM faked.

After that I can't boot with -x -v because I get an "ERROR!!! Load prelinked kernel with status 0x800000000000000e. Error loading kernel cache (0xe)" but I can boot normally.
-----------------------------------------------------------------------------------------------------------------------------------

I would appreciate any help.

 

[jaymonkey]

After that I can't boot with -x -v because I get an "ERROR!!! Load prelinked kernel with status 0x800000000000000e. Error loading kernel cache (0xe)" but I can boot normally.

@PREngineer,


Since MacOS 10.12.13 Sierra you can no longer boot with the -x flag (ignore caches) which is most likely why your getting the error and is why Clover no longer offers it as a boot option when you press the space bar key.

If your motherboard has natively supported NVRAM then there is no need for the Clover shutdown RC scripts, they are only required if your using emulated NVRAM and are responsible for writing the NVRAM cache to the nvram.plsit file which is used by EmuVariableUefi-64.efi to populate the NVRAM cache on boot.

Make sure your SystemID;s and Key's are persistant between boots using iMessage Debug or Hackintool, if they are not then it is indicative of a NVRAM issue.

Cheers
Jay

 

[PREngineer]

Thank you Jay,

I wasn't aware of the -x flag thing. So, I guess my machine is OK when it comes to that.

I have checked and my NVRAM is rock solid.

Before Shut Down:

**********************iMessage Debug**********************
Credits: ElNono, mdmwii,flux84, sugarface, pokenguyen

Model: iMacPro1,1
Board-id: Mac-7BA5B2D9E42DDD94
SerialNumber: C02V32ZLHX87
Hardware UUID: D43DFD49-1DDA-5813-A0E7-D51C4586A040

System-ID: 7565FDD1-6233-41B6-8B50-414B6D2BB12B
ROM: 902b34df3eca
BoardSerialNumber: C02V32ZLHX87A12BC

Gq3489ugfi: 1a31417783a881eb37760896e977eff87d
Fyp98tpgj: 08e1273c247bb8befc8051f70a43e70ce7
kbjfrfpoJU: d12988416a28b14dca6d2248c45d56cf94
oycqAZloTNDm: 7f240ce5f186064903cff60715d45517c0
abKPld1EcMni: 66cbb39a85a25feb05b3130e10592ec41b


After Shut Down:

**********************iMessage Debug**********************
Credits: ElNono, mdmwii,flux84, sugarface, pokenguyen

Model: iMacPro1,1
Board-id: Mac-7BA5B2D9E42DDD94
SerialNumber: C02V32ZLHX87
Hardware UUID: D43DFD49-1DDA-5813-A0E7-D51C4586A040

System-ID: 7565FDD1-6233-41B6-8B50-414B6D2BB12B
ROM: 902b34df3eca
BoardSerialNumber: C02V32ZLHX87A12BC

Gq3489ugfi: 1a31417783a881eb37760896e977eff87d
Fyp98tpgj: 08e1273c247bb8befc8051f70a43e70ce7
kbjfrfpoJU: d12988416a28b14dca6d2248c45d56cf94
oycqAZloTNDm: 7f240ce5f186064903cff60715d45517c0
abKPld1EcMni: 66cbb39a85a25feb05b3130e10592ec41b


After Restart:

**********************iMessage Debug**********************
Credits: ElNono, mdmwii,flux84, sugarface, pokenguyen

Model: iMacPro1,1
Board-id: Mac-7BA5B2D9E42DDD94
SerialNumber: C02V32ZLHX87
Hardware UUID: D43DFD49-1DDA-5813-A0E7-D51C4586A040

System-ID: 7565FDD1-6233-41B6-8B50-414B6D2BB12B
ROM: 902b34df3eca
BoardSerialNumber: C02V32ZLHX87A12BC

Gq3489ugfi: 1a31417783a881eb37760896e977eff87d
Fyp98tpgj: 08e1273c247bb8befc8051f70a43e70ce7
kbjfrfpoJU: d12988416a28b14dca6d2248c45d56cf94
oycqAZloTNDm: 7f240ce5f186064903cff60715d45517c0
abKPld1EcMni: 66cbb39a85a25feb05b3130e10592ec41b


As you can see, it didn't change.

I honestly can't understand why it doesn't work.

 

[jaymonkey]

I wasn't aware of the -x flag thing. So, I guess my machine is OK when it comes to that......I have checked and my NVRAM is rock solid.....I honestly can't understand why it doesn't work.

@PREngineer,

All looks good as far as your NVRAM goes, if your sure your Serial No, MLB & ROM .. etc are all ok (I assume they are if it has already been working) then i would try the following.

1. Logout of all of Apples on line systems iCloud, iMessage, iTunes ... etc.
2. Wait 24 Hours then log back in.

Sometimes an account can get flagged in-correctly ... logging out and waiting 24 hours can sometimes clear this.

If it doesn't work after 24 then logout out of everything again, disconnect from the internet and generate a new set of critical SystemID's including Serial No, ROM, MLB, SMUUID .. etc, don't forget to check that the serial number is valid, use @P1LGRIM's quick guide as a reference. Once your sure that the new SystemID's have taken and are persistant ... reconnect the system to the internet and log back into Apples on-line services.

Hopefully that should fix the issue.

Cheers
Jay

 

[PREngineer]

@PREngineer,

All looks good as far as your NVRAM goes, if your sure your Serial No, MLB & ROM .. etc are all ok (I assume they are if it has already been working) then i would try the following.

Logout of all of Apples on line systems iCloud, iMessage, iTunes ... etc.

Wait 24 Hours then log back in.

Sometimes an account can get flagged in-correctly ... logging out and waiting 24 hours can sometimes clear this.

If it doesn't work after 24 then logout out of everything again, disconnect from the internet and generate a new set of critical SystemID's including Serial No, ROM, MLB, SMUUID .. etc, don't forget to check that the serial number is valid, use @P1LGRIM's quick guide as a reference. Once your sure that the new SystemID's have taken and are persistant ... reconnect the system to the internet and log back into Apples on-line services.

Hopefully that should fix the issue.

Cheers
Jay

I feel like a total idiot... and I really want to punch myself in the face.

Turns out that the problem was that I needed to go into my iPhone and enable the "new" iMac Pro to send and receive messages using my iMessage.

Thanks for being so patient.

I hope this helps anyone having the same stupid problem.

I believe that this should be added as an important note to the guides.

 

[esafeddie]

I feel like a total idiot... and I really want to punch myself in the face.

Don't be too hard on your self mate we all make mistakes even though the answer is in front of us - Glad you got it sorted, enjoy