How to Fix iMessage

[jaymonkey]

Hello jaymonkey,

my motherboard is: Gigabyte X58A-OC, okay i will generate the new one. I got this serial number from one website and they said that it is good for hackintosh.

I have not contact apple yet, but i clicked on the button "Call Apple Support" is it problem? Thanks.

@Tomas2D,

I'll add that motherboard to the list, it should not be a problem having clicked on that button as long as you did not set a call up. As suggested follow methods in last msg then contact Apple using Step 8 in part 2.

You should be fine
Cheers
Jay

 

[Gerard71]

hello I think my hackintosh is correct serial number ect .....
I contacted apple canada, the person told me that it was an error code and that the problem came from the machine, he wanted to check the machine away and I said I had not with me right time
what I find strange is that on my real mac mini that is activated immediately without any problems, and my hackintosh it does not work,
if there was a blockage on my AppleID
no macintosh even a real mac mini should work with my apple id not?
Apple's going to probably find it strange that many people put a call to the same problem of a sudden

 

[Tomas2D]

@Tomas2D,

I'll add that motherboard to the list, it should not be a problem having clicked on that button as long as you did not set a call up. As suggested follow methods in last msg then contact Apple using Step 8 in part 2.

You should be fine
Cheers
Jay

I did all step, what you told me. My ROM and MLB are OK, so i also changed my serial number and added the SMsystemuuid.

Now i am waiting for tommorw and i will call apple support.

Thanks for the help!

 

[jaymonkey]

hello I think my hackintosh is correct serial number ect .....
I contacted apple canada, the person told me that it was an error code and that the problem came from the machine, he wanted to check the machine away and I said I had not with me right time
what I find strange is that on my real mac mini that is activated immediately without any problems, and my hackintosh it does not work,
if there was a blockage on my AppleID
no macintosh even a real mac mini should work with my apple id not?
Apple's going to probably find it strange that many people put a call to the same problem of a sudden

@Gerard71,

Sometimes that can happen, it just depends on the operator you get through ..... try and take control of the conversation and steer it back to the iMessage customer code issue and away from the OSX S/N ... be assertive ...in my case ... i've always been able to get them to think the issues is with their system ...

As to Apple catching on ... I don't think you need to worry ... The customer code Alert is a security system, it proves you are you on your machine, it can happen even if you own a lot of legitimate Apple Devices working on the same network. - Apple are supporting the software (OSX) and your AppleID. The only reason they push for a OSX S/N is to log the support call against, if you use the method detailed in Step 8 then you should avoid most S/N questions, tell them to log the call agist your AppleID - thats what i do.

Cheers
Jay

 

[jaymonkey]

I did all step, what you told me. My ROM and MLB are OK, so i also changed my serial number and added the SMsystemuuid.

Now i am waiting for tommorw and i will call apple support.

Thanks for the help!

@Tomas2D,

No problem, as long as all your ID's are now the correct syntax and persistent between boots then you'll be fine. Be sure to use the method in Part-2, Step-8 of the guide to contact Apple and they will call you ....

Cheers
Jay

 

[keypox]

So what is going one here? Do I need to call them with this customer code?

 

[fixjet]

Sorry to add more to this thread, but I have a quick question. I upgraded to 10.9.5 and all was well until i rebooted last night, then all of a sudden my iMessage stopped working. Unfortunately (and stupidly I suppose) after a couple days with no issues I upgraded my backup drive as well. Neither works with iMessage of course. I am getting the error during activation message.

The question is, going through the procedures when I look at my ROM using nvram -x -p in terminal it has the same initial alpha numeric code as the MLB, but then under data it just shows "A"s...is that normal (i think not the base64 comes up as just a repeating string of letters)? I have tried manually injecting with no luck. Everything else seems good, and nothing was changed (by me) during the upgrade. I've been reading and messing with this for hours now, maybe just need a break, just need to confirm this is an issue (I am assuming it is and I can't seem to resolve it no matter what I do)...

Update on this (since I cannot delete post), using iMessage debug discovered the AAA...'s etc equate to my ROM being all 00000's...tried several things with no luck... finally updated my fileNVRAM.dylib in my Extras folder to version 1.1.3 (hesitant on this since last time I tried 1.1.3 it BROKE everything), restarted and BINGO call Apple support message popped up with a code to use...so I'll call them tomorrow and we'll go from there.

The only change from last week is updating to 10.9.5, had to reinstall sound using MB 6.1.0 and TRIM with MB 6.4.2...not sure why it broke...

 

[treblA311]

@Jaymonkey

Bought a PCIe lan card w/c is TP Link TG 3468 and my iCloud and Appstore works now...but iMessage and Facetime still not working followed all the instructions posted in part 1 and part 2...

here is my nvram = nvram.00000000-0000-0000-0000-50e54958d88f.plist

iMessage debug:

localhost:~ Cyber-0$ /Users/Cyber-0/Downloads/imessage_debug ; exit;
2014-09-22 12:42:13.682 imessage_debug[912:507] Gq3489ugfi: <e5a792d4 170591d1 e908365e 6d5a7d0b e2>
2014-09-22 12:42:13.684 imessage_debug[912:507] Fyp98tpgj: <11941d7a 237fceb9 fd4ff9d5 77479b3a 48>
2014-09-22 12:42:13.684 imessage_debug[912:507] kbjfrfpoJU: <e9476be2 7d2c2070 decddafd 545f3b15 c1>
2014-09-22 12:42:13.684 imessage_debug[912:507] IOPlatformSerialNumber: C02H5064DNCT
2014-09-22 12:42:13.684 imessage_debug[912:507] IOPlatformUUID: 8E2BD6E0-4DF0-5A5F-AD88-F5FAB0E80D00
2014-09-22 12:42:13.685 imessage_debug[912:507] board-id: Mac-00BE6ED71E35EB86
2014-09-22 12:42:13.685 imessage_debug[912:507] product-name: iMac13,1
2014-09-22 12:42:13.685 imessage_debug[912:507] 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:ROM: <e8de2706 ab91>
2014-09-22 12:42:13.685 imessage_debug[912:507] 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:MLB: C02H5064DNCT3M7J
2014-09-22 12:42:13.686 imessage_debug[912:507] oycqAZloTNDm: <6721b8d8 835d2f1a 5058c49d 5448d923 a9>
2014-09-22 12:42:13.686 imessage_debug[912:507] abKPld1EcMni: <b533969d 8255a2c7 8b9905a5 df8bf248 45>
logout

[Process completed]

can u pls tell me what else should i do?

when i run iMessage it sez...Your Apple ID "trebla@g?????.com.ph" can't be used to set up iMessage at this time.

 

[jaymonkey]

So what is going one here? Do I need to call them with this customer code?

@keypox,

If you have received the following alert message then yes


However before doing so you need to check ALL your ID's to ensure they are the correct syntax and are persistent on each boot. Many installs allow the ROM & MLB values to change on each bootor have a miss-matched System Type and/or S/N. If this happens then you will continue you get this message after some time. Suggest the following :-

• Read Part 2 of the guide Up to Step 7, check if you have the SId bug, if so fix it
• Check for persistent MLB & ROM values, see Part-1, Step 5d
• If you needed to change anything in steps 4 or 5 then Perform all of step 4 and 5e

Once you get the contact Apple alert with a customer code then follow the contact Apple method in step 8 in Part-2.

Cheers
Jay

 

[jaymonkey]

@Jaymonkey

Bought a PCIe lan card w/c is TP Link TG 3468 and my iCloud and Appstore works now...but iMessage and Facetime still not working followed all the instructions posted in part 1 and part 2...

here is my nvram = nvram.00000000-0000-0000-0000-50e54958d88f.plist

can u pls tell me what else should i do?.

@treblA311,

There are only two things that can cause that problem....

Your Bios could be suffering from the SId Bug (See Part-2 of the guide for information)

check your registry at location: IODeviceTree : efi / platform / system-id
(if your unfamiliar with getting values out of the registry see here)

---

If system-id is '00000000-0000-0000-0000-50e54958d88f' then your BIOS has the SId bug so use part-2, Step 7 of the guide to fix, then follow steps 4 and 5e in Part-1.

If system-id is a unique series of hexadecimal numbers (16 x 16 Bit word) then you do not have SId bug and the issue will be the boot-loader version your using. See the suggestions in Part-1, Step5d.

If you do have the SId bug please let me know your motherboard type if it's not already on the list in Part-2 of the guide and i'll add it.

Good Luck
Cheers
Jay