- Joined
- May 7, 2011
- Messages
- 23
- Motherboard
- Dell optiplex 7020
- CPU
- i5 4590
- Graphics
- 4600
- Mac
- Mobile Phone
Fed up now followed the guide all the way through and still the same message what am I doing wrong?
Hi,
Thank's you for this topic.
Unfortunatelly I have try a lots of thing but iMessage still doesn't work.
Here is my config.plist (from Clover )
I'm now randomly getting the contact apple message now with iMessage. Doh!
For those of you that called Apple, did you go and find a genuine serial number or just used the one automatically generated in SMbios?
Thanks
Jay,
Thanks for the confirmation, however now I don't know why iMessage stopped working. I've done the following so far:
Step 1: I can login to apple and have verified my account
Step 2: Reverified that the AppleIntelE1000e starts with en0
Step 3: I'm using Chimera 3.0.1, other than that, I skipped this step since iMessage was working previously on this machine
Step 4: This is really the only change I think I should be making. I deleted all the files including the com.apple.security files and rebooted
Step 5: NVRAM, I set this up previously, and since all I've done is erase files in Step 4, I don't think I have anything to do here.
I've also repaired permissions repeatedly and run sudo nvram boot-args=""
At this point I keep getting the "Could not sign in to iMessage. An error occurred during activation. Try again."
What am I missing?
Jay,
Thanks for the confirmation, however now I don't know why iMessage stopped working.
At this point I keep getting the "Could not sign in to iMessage. An error occurred during activation. Try again."
@klemant,
Have you checked your ROM value ?, you don't have it specified in your clover config plist.
Whats is its current value .... ? use iMessage Debug or Darwin Dumper.
You could try injecting the MAC address of en0 for your ROM value via the RTVariables section.
Please read section Part-1, Step 5d again which was updated yesterday with clover specific info.
Good Luck
Cheers
Jay
Deprecated! Will automatically be read from SMBIOS.
I'm trying to work through the entire guide again. I'm gotten through most of the process and even written a very basic script to delete the files and directories in Step 4.
I could still use some direction on my questions above, and would like to clarify something from step 5 about the MLB and ROM values. To me it looks like the MLB is actual data, but not my UUID. What is this supposed to be? I believe it should be my Macs S/N + some random Alphanumeric characters to make it 17 characters long. Mine is the S/N (11 chars) + 5 chars giving me an MLB of 16 characters long. Is that OK? Is that also a boot related setup issue?
The ROM shows what I believe is a blank value. The data is AAAAAAAAAAAAAAAAAA== which equals blank right?
Since I'm using Chimera 3.0.1 I should be using FileNVRAM.dylib of 1.1.3. How do I tell which version I'm running?
Right now I'm thinking that I have a boot configuration problem with and should try and disable UEFI options in the bios?
To me it looks like the MLB is actual data, but not my UUID. What is this supposed to be? I believe it should be my Macs S/N + some random Alphanumeric characters to make it 17 characters long. Mine is the S/N (11 chars) + 5 chars giving me an MLB of 16 characters long. Is that OK? Is that also a boot related setup issue?
The ROM shows what I believe is a blank value. The data is AAAAAAAAAAAAAAAAAA== which equals blank right?
Since I'm using Chimera 3.0.1 I should be using FileNVRAM.dylib of 1.1.3. How do I tell which version I'm running?
Right now I'm thinking that I have a boot configuration problem with and should try and disable UEFI options in the bios?
@jborn,
All UUID's should be XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXX
MLB should be your OSX S/N + 5 extra alpha numeric characters
Your ROM value looks invalid - try injecting the MAC address of en0 for ROM value
If your not sure which version of FileNVRAM you have installed, simply delete the existing version in /Extra/modules and replace it with the correct version from the archive attached to Part-1 of the guide.
When using Chimera or Chameleon for your boot-loader i aways recommend disabling UEFI in the BIOS if you don't need it for Windows 8.1.
Cheers
Jay