How to Fix iMessage

[Walril]

Is it really hard for you guys to read the instructions? or are guys just grabing stuff from here or there?

seriously, Id like to know.

Based on my reading AND understanding:

1) You DO NOT have to clone values to get iMessage and FaceTime working. Up until a few days ago, I never owned a Mac product yet I have iMessage working. Still dont clone.

2) 17 digit MLBs have not been understood yet, so that means you can't make them up in any capacity (10%, 20%, 99%, 1%)

3) 13 digit MLBs are the way to go

4) Your MLB/SN doesn't have to correlate to the System Definition


Please save yourself some time and frustration by reading the first page.

 

[wingc3]

Is it really hard for you guys to read the instructions? or are guys just grabing stuff from here or there?

seriously, Id like to know.

Based on my reading AND understanding:

1) You DO NOT have to clone values to get iMessage and FaceTime working. Up until a few days ago, I never owned a Mac product yet I have iMessage working. Still dont clone.

2) 17 digit MLBs have not been understood yet, so that means you can't make them up in any capacity (10%, 20%, 99%, 1%)

3) 13 digit MLBs are the way to go

4) Your MLB/SN doesn't have to correlate to the System Definition


Please save yourself some time and frustration by reading the first page.

So,

1. no one said you HAD to clone.
2. That's EXACTLY what I said.
3. The structure of these IS well understood, but the correlation that might be required to a generated ROM value is explained in contradictory ways all over the web. Perhaps you could enlighten us? Did you have to call apple to get your generated values to work? Did you use your en0 address or did you generate a ROM value using Apple's prefixes?
4. Also EXACTLY what I said, I'm using a macbook pro's IDs (my own), but an iMac 14,2 system definition and it works fine.


Though my system works, I would like to have my own unique values that work. So, if you could enlighten us with some DETAIL, as to how you generated your MLB/ROM values and whether that resulted in a call to Apple or not, that would be more helpful than somehow implying that the hundreds of people working on this are somehow morons....No one who is even in the position to be struggling with this on their home-built hackintosh is a moron. What we are dealing with is large amounts of contradictory information, and your help in sorting us out with what YOU did to be successful would be GRATEFULLY appreciated.

Thanks in advance...

 

[mld1]

I personally think the S/N + 5 random characters for MLB is a bad idea in the current environment. The reason is that the algorithms to represent the year and week of manufacture of the two components are entirely different. This makes it easy for a simple algorithm at Apple to discover that the two do not make a consistent match. If you have a S/N that passes SelfSolve, then I recommend making an effort to acquire MLBGen17V3.sh .

That script is certainly not perfect since there are two fields of the MLB of which nobody knows the meaning. But what it WILL do is generate two numbers that are consistent in the most obvious fields.

I do not know if it is available outside of the InsanelyMac forum, but I thought it was sufficiently important to join just to download the script. If it is not available otherwise and that situation persists, I can write a perl script that does the same thing with a day or so effort. (it has been a couple of years since I wrote perl so it will take me a day or so to get back in the "perl mode", but I used to use it for all my scripting work.) The user won't know the difference.

That is my 2 cents (insert your own currency).

 

[VioletDragon]

my iMessage and everything else just logged me in but i am using Chameleon in Mavericks 10.9.5 and it just logged me in with no issues

 

[bigorthy]

I'm using clover and followed this guide to get iMessage working on Yosemite 10.10.1. I'm not using any cloned IDs.

I used Clover Configurator in combination with iMessage Debug to verify my changes upon reboot. I'll post in detail when I get home, but I used - Part-1, Step-5d like the Feb 15th update suggested. My MLB value is 17 digits long since I'm using a 12 digit OSX S/N.

Also make sure you're following the parts further down in step-5d, especially these:

ROM: This will now be read from the last 6 bytes of the 'SmUUID' field. If you have nothing in the SmUUID field then Clover will try to use your BIOS's SystemId (see Part-2 of the guide) however, I personally think it's always best to override The BIOS (even if it does not suffer from the SId bug) and to use the terminal command 'uuidgen' to generate a new random value (See Part-2, Step 7, Path-C). Enter the generated UUID as the SmUUID value on the SMBIOS page. If this is a new OSX Install then you can leave it like that. If you want to keep you old ROM value then replace the last 6 bytes of SmUUID with the ROM value you were using before which is normally the MAC address of an ethernet port (usually en0).

Note: It is important to understand that configuring Clover like this will cause your existing Hardware (Platform) UUID to change ... whilst this in-it's-self is not a problem it will change the identity of your system from your previous install which in-turn may cause some user profile settings to be changed due to the Hardware (Platform) UUID being used as a key value for storing some OSX configuration data against.

MLB: This is now read from the 'Board Serial Number' field on the SMBIOS page, on a clean Clover install this is defaulted to Clovers own pre-set static value which is of-course black-listed on Apples systems. You therefore must replace this with your existing MLB value (on an existing install) or use your OSX S/N + Random Alpha / Numeric digits to make it up to 17 digits.

I was having issues with my iMessage not working until I made sure my MLB value was also copied into my SMBIOS in the "Board Serial Number" box (not to be confused with "Serial Number"). To generate my MLB value, I just used my serial number and added a few random characters to get to 17 (since the serial number itself is only 12).

This was a fresh install on a new hackintosh. I did not use any cloned IDs and I didn't have iMessage working since I built this machine in December until just two nights ago when I followed this guide with the Feb 15th update.

 

[LaFemme69]

wondering if anyone can please help me.

I have not been able to use iMessage on my Hackintosh since the changes in Oct/Nov. 2014. I tried to follow this thread to fix but NO LUCK.

SYSTEM:
Mavericks 10.9.5
Chameleon bootloader
OS X SN - 9 digit, CKxxxxxxx (created by Chameleon wizard, under Mac Pro 3,1 preset which is closest to my system specs)

This is what I did:

(1) My appledID is 'verified' through on-line Account Manager (https://appleid.apple.com/cgi-bin/WebObjects/MyAppleId.woa/), although DO NOT have a credit card # on the account

(2) Verified that my network interface is en0

(3) I checked my SN at https://selfsolve.apple.com/ and to my surprise to find out that the S/N is already registered and assigned to another machine. Not sure how and when. I do have an iPod touch with iMessage logged into the same AppleID and working FINE, but don't think that's the case.......Anyways........

(4) Followed "Updating the SMBIOS & OSX S/N - Chimera or Chameleon method" to get another SN, verified with https://selfsolve.apple.com/ and I get the message "We're sorry, the number you have provided cannot be found in our records. Please verify the number and try again".....I assume good so far?

(5) tried to log onto iMessage, NO GO. Even tried with a different AppleID but still did not work.

(6) Followed Step-4 to reset iMessage configurations. Tried to log into iMessage again, NO GO. Still getting the message "Could not sign in to iMessage. Please check your network connecting and try again"

(7) After running iMessage Debug v2, noticed my ROM is all ZEROs so I created new MLB and ROM values following Step-5d and manually injecting the values via Terminal:

sudo nvram <my Hardware UUID pulled from iMessage debug>:MLB=<my new OS SN + 2 extra numbers to make 13 digits>
sudo nvram <my Hardware UUID pulled from iMessage debug>:ROM=<my network Mac address separated by %>

(8) Rebooted, run iMessage debug again and STILL all ZEROs for the ROM.

(9) decided to follow all the steps in Step-5e to reset my FileNVRAM plist. Following step 6, NEVER saw a new nvram.uuid.plist file created after rebooted. Only saw a nvram document file (nvram.xxxxxxxx-xxxx-ee0DriversPackage-xxxxxxx). anyways......

(10) ran iMessage debug v2 again, STILL ROM 0000000000000.......

......so here I am, still NO iMessage.

Where and what did I do wrong?

anyone?

sorry for a long post, tried to be as detailed as I can.

thank you.

kd

P.S. side notes: (1) I have never gotten a message to contact Apple for any code
(2) I created a Clover bootable USB to boot Mavericks with so I can tried Clover method, didn't work
(3) i did a fresh install of Yosemite (with Chameleon boot loader) on ANOTHER DRIVE and boot with Clover USB and tried Clover method, didn't work
(4) I have a system of total 5 Drives: 1 SSD with the main Mavericks, a partition of another HDD with a backup of FRESH INSTALL of Mavericks, another partition of a different drive with a backup of current-state Mavericks, another partition with Yosemite so I can test.........Do you think this may be the problem because when OS boots up, it also mount other drives and perhaps the data may 'cross over'? I noticed that certain files are associated with apps I didn't even install but it was from the previous install on another HDD......hope you understand what I mean. (5) plan to do a fresh install of either Mavericks or Yosemite with Clover boot loader on a test HDD to see what happens.

 

[MarcelBidon]

wondering if anyone can please help me.


SYSTEM:
Mavericks 10.9.5
Chameleon bootloader
OS X SN - 9 digit, CKxxxxxxx (created by Chameleon wizard, under Mac Pro 3,1 preset which is closest to my system specs)

kd

P.S. side notes: (1) I have never gotten a message to contact Apple for any code
(2) I created a Clover bootable USB to boot Mavericks with so I can tried Clover method, didn't work
(3) i did a fresh install of Yosemite (with Chameleon boot loader) on ANOTHER DRIVE and boot with Clover USB and tried Clover method, didn't work
(4) I have a system of total 5 Drives: 1 SSD with the main Mavericks, a partition of another HDD with a backup of FRESH INSTALL of Mavericks, another partition of a different drive with a backup of current-state Mavericks, another partition with Yosemite so I can test.........Do you think this may be the problem because when OS boots up, it also mount other drives and perhaps the data may 'cross over'? I noticed that certain files are associated with apps I didn't even install but it was from the previous install on another HDD......hope you understand what I mean. (5) plan to do a fresh install of either Mavericks or Yosemite with Clover boot loader on a test HDD to see what happens.

Not absolutely sure with the new successes, it seems that Clover is needed to make working an installation that was not already working before Apple changes in November.

In my desktop, I have 4 HDD (Data) and 2 SDD (Osx and Win 8.1) and iMessage is working.

No need to reinstall to switch from Chameleon to Clover.
First make an USB boot with Clover and try to start your regular install from it (disable network when you are trying to avoid to send multiple configuration to Apple). When it is working, you can make a duplicate (or a backup) and modify your installation on SSD.
They are many tutorials to explain how to switch from Chameleon to Clover (format of startup file is different, there is a special place for kext, and it is more powerful with the possibility to patch kext on the fly). Not so easy, and need time to understand how to take advantage of the patch on the fly (it is possible to have installs updating without problem as a true Mac).

 

[Walril]

So,

1. no one said you HAD to clone.
2. That's EXACTLY what I said.
3. The structure of these IS well understood, but the correlation that might be required to a generated ROM value is explained in contradictory ways all over the web. Perhaps you could enlighten us? Did you have to call apple to get your generated values to work? Did you use your en0 address or did you generate a ROM value using Apple's prefixes?
4. Also EXACTLY what I said, I'm using a macbook pro's IDs (my own), but an iMac 14,2 system definition and it works fine.


Though my system works, I would like to have my own unique values that work. So, if you could enlighten us with some DETAIL, as to how you generated your MLB/ROM values and whether that resulted in a call to Apple or not, that would be more helpful than somehow implying that the hundreds of people working on this are somehow morons....No one who is even in the position to be struggling with this on their home-built hackintosh is a moron. What we are dealing with is large amounts of contradictory information, and your help in sorting us out with what YOU did to be successful would be GRATEFULLY appreciated.

Thanks in advance...

No, but people seem to clone like its in style because they are too lazy to RTFM

I used the information from this site and the insanelymac site to make the MLB/ROM so that they would more likely validate each other.
Yes, I did get the call apple, but before apple was letting anyone in, you always had to call them to whitelist them.

I wont call the people working on this morons. They are the ones that deciphered the MLB/ROM. To the countless people that ask the same questions after its been answered every other page, I wont call them morons. I will call them lazy though, because the answer to their questions have been posted again and again and again. In fact, I followed the guide(s) to a T and got it working on try #1.

I say lazy because when a user tells me they glanced over the guide instead of reading it then thats laziness. When someone asks a question that was just answered a page or two ago that means they didn't read...thats laziness. In the beginning when this method didn't work on chimera and it was said it didn't work on chimera and people asked "How does it work, im on chimera"..thats them not reading = laziness.

If YOU want DETAIL on how to make this work using your own values, then read the guide. Follow the thread on insanelymac too to see how a MLB/ROM are formatted. I really don't have the time or patience to explain what's already been explained in DETAIL from those two sources. If you can't follow them (or refuse to), then me explaining it won't help either.

 

[esafeddie]

No, but people seem to clone like its in style because they are too lazy to RTFM

I used the information from this site and the insanelymac site to make the MLB/ROM so that they would more likely validate each other.
Yes, I did get the call apple, but before apple was letting anyone in, you always had to call them to whitelist them.

I wont call the people working on this morons. They are the ones that deciphered the MLB/ROM. To the countless people that ask the same questions after its been answered every other page, I wont call them morons. I will call them lazy though, because the answer to their questions have been posted again and again and again. In fact, I followed the guide(s) to a T and got it working on try #1.

I say lazy because when a user tells me they glanced over the guide instead of reading it then thats laziness. When someone asks a question that was just answered a page or two ago that means they didn't read...thats laziness. In the beginning when this method didn't work on chimera and it was said it didn't work on chimera and people asked "How does it work, im on chimera"..thats them not reading = laziness.

If YOU want DETAIL on how to make this work using your own values, then read the guide. Follow the thread on insanelymac too to see how a MLB/ROM are formatted. I really don't have the time or patience to explain what's already been explained in DETAIL from those two sources. If you can't follow them (or refuse to), then me explaining it won't help either.

Totally agree!!!!

 

[esafeddie]

@ jbamford - Glad to see you back on the Scene and up and running, the last time we heard from you, you was that Hacked off with the iMessage fiasco, (no pun intended) you was about to offload all your Hacks and buy an iMac - Glad we didn't lose you to the dark side lol.