How to Fix iMessage

[sentur]

The output of iMessageDebugV2 is not what I'm expecting and looks like it's gone back to default generic values.

I have an old saved version of iMessageDebugV2 values that I kept from when I last had iMessage working correctly. The System-ID, ROM, BoardSerial S/N are quite different from my last saved version. Ie my ROM is now ROM: 888888888788 and BoardSerial: 00020003-0004-0005-0006-000700080009.

Would it be better to try and revert back to all my old System-ID, ROM, MLB etc or attempt to generate new ones?

I think when I updated my OS to 10.11.4 a couple of weeks back the iMessage details changed and I didn't notice. I noticed messages wouldn't send at first, but a login and log out rectified the issue until now.

 

[esafeddie]

The output of iMessageDebugV2 is not what I'm expecting and looks like it's gone back to default generic values.

I have an old saved version of iMessageDebugV2 values that I kept from when I last had iMessage working correctly. The System-ID, ROM, BoardSerial S/N are quite different from my last saved version. Ie my ROM is now ROM: 888888888788 and BoardSerial: 00020003-0004-0005-0006-000700080009.

Would it be better to try and revert back to all my old System-ID, ROM, MLB etc or attempt to generate new ones?

I think when I updated my OS to 10.11.4 a couple of weeks back the iMessage details changed and I didn't notice. I noticed messages wouldn't send at first, but a login and log out rectified the issue until now.

Go off line - either remove ethernet cable or disable wifi until you complete these steps - Follow the instructions in Chapter 3.3 (Reset iMessage Configuration files) and delete the files in the folders as instructed and reboot the pc, still off line, inject the values from your old saved iMessage values that you kept i.e ROM, MLB, Board S/N etc. Reboot p/c after all necessary values are injected, still off line, run iMessage DeBugger to insure values are static, if ok reconnect internet and attempt a logon to the iMsg services. Good luck

 

[esafeddie]

If that is the result you got after checking your s/n with Apple then I am afraid you cannot and must not use it as it belongs to a real Mac out there. You stand to have that Mac as well as your p/c blacklisted and possibly your ID, try generating another which should give the result 'Not Valid' or words to that effect.

 

[EddyMac]

Quick question: I'm getting a brand new Gigabyte Z170X board and Skylake processor tomorrow. Will iMessage work out of the box after installing with Unibeast and doing the Multibeast post install, or is there more tinkering required after that? This thread seems to be dedicated to "fixing" problems; it seems to be the official TonyMac guide for all things iMessage...yet I'm not seeing where it addresses brand new installs with new hardware. Thanks, and sorry if I'm missing something.

 

[P1LGRIM]

Will iMessage work out of the box after installing with Unibeast and doing the Multibeast post install, or is there more tinkering required after that?

No, it won't work OOB and yes you will have to tinker.

For a walkthrough of how I set up my last build for iMessage see the Qx-2000 link in my sig.
Obviously you would have to make adjustments for your relevant System Definition.

 

[EddyMac]

Thanks, P1LGRIM!

 

[sentur]

Go off line - either remove ethernet cable or disable wifi until you complete these steps - Follow the instructions in Chapter 3.3 (Reset iMessage Configuration files) and delete the files in the folders as instructed and reboot the pc, still off line, inject the values from your old saved iMessage values that you kept i.e ROM, MLB, Board S/N etc. Reboot p/c after all necessary values are injected, still off line, run iMessage DeBugger to insure values are static, if ok reconnect internet and attempt a logon to the iMsg services. Good luck

Thank you for your help. That appears to have fixed things. The elements after BoardSerialNumbers (what loo to be randomish hex) have changed from what I had saved. Should I be concered about these? The Board-id, S/N, ROM, MLB etc are all persistent across reboots and I'm able to login to iMessage. Just waiting for my history to sync back.

Thanks again!

 

[esafeddie]

Thank you for your help. That appears to have fixed things. The elements after BoardSerialNumbers (what loo to be randomish hex) have changed from what I had saved. Should I be concered about these? The Board-id, S/N, ROM, MLB etc are all persistent across reboots and I'm able to login to iMessage. Just waiting for my history to sync back.

Thanks again!

Don't worry about the other info displayed - they are not meant to be constant - the Board-ID, S/N, ROM and MLB are the vital ones that should remain static at all times. Just be patient with your history to sync, the servers can be a bit slow at times. Glad you were able to get it sorted

 

[sentur]

Don't worry about the other info displayed - they are not meant to be constant - the Board-ID, S/N, ROM and MLB are the vital ones that should remain static at all times. Just be patient with your history to sync, the servers can be a bit slow at times. Glad you were able to get it sorted

I just updated to the new released 10.11.5 update. In doing so, my SN and System-ID both reset. Looks like I'm going to have to check the output of iMessageDebugV2 after every update and make sure I'm offline before completing the update.

 

[esafeddie]

I just updated to the new released 10.11.5 update. In doing so, my SN and System-ID both reset. Looks like I'm going to have to check the output of iMessageDebugV2 after every update and make sure I'm offline before completing the update.

Updates shouldn't really break iMsg/F-Time - are you running a Chimera or a Clover install? I haven't run OS X under Chimera since Mavericks so I can't really comment truthfully on the reason why, I don't have any problems regardless of updates. Just remember the golden rule of going off line and re-enter the values and you should be good to go. Good luck.