How to Fix iMessage

[chill2x]

 

[esafeddie]

View attachment 176820View attachment 176821View attachment 176822

Ok I can see from your Clover Configurator pic that the Board S/N is now 17 characters, but at the same time in the pic I can see iMessage DeBugger value still showing 12 characters which as I said before is wrong. Ok now that you've changed the Board S/N to i7 digits, run iMsg DeBugger again and check the readout, it should be the same as it is injected in Clover Configurator - (stupid question, you did remember to save the new values in Clover Config before closing it).

 

[chill2x]

in imessage debugger it show 17 now.i put 5 random characters.
when i try to log in imessage & facetime it show this message..

 

[lazarus]

Ok - Error spotted, your Board S/N is not quite right, it should consist of your S/N plus 5 random digits added to the end making it 17 characters in total. Remember please log out of all Apples Services and go offline before making the changes - Good luck.

Easier to just use the guest account to ensure everything is working. Won't automatically log you in to any iCloud services, and deletes all preference files once you log out of it.

 

[lazarus]

in imessage debugger it show 17 now.i put 5 random characters.
when i try to log in imessage & facetime it show this message..
View attachment 176852

Yup. Welcome to our world. If you are getting this, and getting the same customer code every single time, you can call Apple. Read the last chapter of the guide in post 1 on how to go about that.

But that said, even though they have unblocked it for a lot of us, it still won't log in and gives the same customer code every time. For SOME accounts, and I can't figure which ones, you have to get your ROM/MLB combo whitelisted, and I THINK there is an additional check to make sure they are a valid combination. So for some accounts the random digits added to serial to make an MLB won't work. But no one at this time really knows what that MLB should be formatted as. The best discussion on that is probably this one at Insanelymac. My current best theory is for newer iCloud accounts, you need a valid MLB/ROM combo (ie properly formatted, so that it COULD be an authentic Apple MLB/ROM even though it doesn't yet exist in their system) that has been whitelisted by Apple. What it takes to make that valid combo is still unclear.

 

[chill2x]

thank you for your reply..i log in to my apple ID in the apple website under device i saw my mac book pro log in and my iphone.so it means they recognize it?btw, i apologize to our conversation before.

 

[lazarus]

thank you for your reply..i log in to my apple ID in the apple website under device i saw my mac book pro log in and my iphone.so it means they recognize it?btw, i apologize to our conversation before.

Yeah, no problem. I shouldn't have gotten so snarky.

The device showing up in your account doesn't mean much. iCloud stuff seems to work fine regardless (Back to My Mac, Contacts syncing, etc). But that doesn't seem to mean much when it comes to Messages working. Some people have had success removing that computer from the iCloud webpage, then logging in to just Messages, not logging in to iCloud in preference pane. But for my troublesome account, that hasn't helped. Maybe worth trying though.

 

[dimethyman]

@ dimethyman - My question is, when you activated iMsg did you receive a 5 pin 'Verification Code' from Apple for 'Text Forwarding' on your iPhone, Hack and other Apple products? iMsg won't or will only partially work without this. I suggest signing out of iCloud on your Hack then sign back in about 10 minutes or so after to give the service time to sync across all your devices.

When I log into iCloud/iMessages on my Hack I'll receive a notification that another device is now being used. On my iPhone when I click to turn on text forwarding, I never receive a pop up on my computer. I thought this was to set up continuity and is not needed for regular iMessage sending.

I looked into the IODevice Tree and the system id and the SMUUID from the config file do match. That's ok right? But the IOPlatformUUID from iMessage Debug does not match AND it changes after every boot. Is this the problem?

Otherwise my serial number is 12 digits and my board serial number is the same plus 5 extra digits.

 

[lebleu29]

I bought an old Macbook so that I could use its numbers to apply to my hack as iMessage doesn't seem to be working despite Customer Care having "fixed" the error code it was giving me.

Anyways, iMessage Debug wasn't working on Snow Leopard and so I tried upgrading to Lion but it still has the same problem.

I've been following this post, but I'm not sure I understand it fully. Here is what I'm thinking I need to do.

1. Serial Number
   • Enter this in the SMBIOS section of config.plist. No problem.
2. SmUUID
   • Enter ioreg -l -p IODeviceTree | grep "system-id in terminal, put resulting key in SMBIOS section of config.plist.
3. CustomUUID Key
   • These instructions I don't understand. It says to enter this key into the SystemParameters section and also to set the InjectSystemID to true.
   • Where / How do I get this CustomUUID key without iMessage Debug?
4. ROM
   • Enter 12 character ROM in Rt Variables section.
   • Where can I get this without iMessage Debug?
5. MLB
   • I've read in the guide that there is a strong suspicion that this is just the ethernet mac address of the computer. Is this confirmed?
   • Enter this in Rt variables sections and Board Serial Number section of SMBIOS.

So here is my plan once I figure out the CustomUUID key, ROM, and MLB values. I open Clover Configurator, go to the SMBIOS section, set it as iMac 14.2, then proceed to enter the values. Is it okay to set it as an iMac despite using the numbers from an old Macbook?

Also, I've seen in some posts that perhaps the ROM and MLB numbers are all I need. If this is the case, what do I do about the other numbers?

 

[grantfitz]

For the record, you don't need genuine numbers for iMessage right now. This guide I wrote should help. The current guide is a little messy for me so I wrote one I thought I could share.