How to Fix iMessage

[foodfightr]

So I ran iMessage debug and everything from Model to BoardSerialNumber matches. Only 3 out of 5 of the strings on the bottom match though. Is this a problem?

 

[esafeddie]

esafeddie haha I'm back for good now how ever I'm using Mavericks 10.9.5 on the pretty much same hardware and i attempted with iMessage and the outcome of that it just logged me straight in ​

Glad to know we didn't lose you - just imagine, you wouldn't have had as much fun if you did get rid of your hardware and took the easy way out (lol). Thats what I like about the Hackintosh scene, over coming the 'It won't work challenges' and the ability to tinker with hardware upgrades when ever the I want to - Anyway jb nice to see you still around.

 

[dannymichel]

Haha, how'd you do that. I didn't think it was possible, which is why i bought this $3k Mac.

 

[Fly1ngSquid]

[...] To use iMessage Debug .... download the attachment from the Files section of the guide and extract, there is no install required, simply double click (or right-click -> Open) in Finder to execute the script. It should open a terminal windows and dump all of the critical iMessage values from the NVRAM Cache including MLB, ROM, Hardware (Platform) UUID, S/N .. etc in a readable form.
View attachment 127668Depending on the version of iMessage debug you use (or if you used the NVRAM command) then the MLB and ROM values may be prefixed by a UUID and will look something like this:-

4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:ROM <xxxxxx...>
4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:MLB xxxxxxx...

Note: Version 1.0 of iMessage Debug surrounds the The ROM value with '<' and '>' and will also insert a space between the 8th and 9th digit, this is a formatting issue and you should ignore these when referencing the ROM Value, just use the 12 Hex numbers.

If the values (xxx..) following these prefixes are incorrect, such as all zeros, null or blank then iMessage will have registration issues. Note that the UUID prefix should not and must not be the same as SM-UUID or Hardware (Platform) UUID - in most cases it will be the same UUID as above which is ok. [...]

Hello Jaymonkey.

I've followed your guide up to this point, and have updated Chameleon to the latest version using Chameleon Wizard, installed fileNVRAM in /Extra/modules (don't know if it is functioning correctly or not), and ran iMessage debug.

The debug returned this:

              Model: iMac14,1
           Board-id: Mac-031B6874CF7F642A
       SerialNumber: C02KV205F8J2
      Hardware UUID: 4E30379B-8832-5EE1-A4E2-D190AA2797B7


          System-ID: 7402D403-3504-1F05-6206-FD0700080009
                ROM: failed
  BoardSerialNumber: failed


         Gq3489ugfi: 4c13d3259bccad836c14b3a414494f7684
          Fyp98tpgj: d954b6584ce4c3cb45355f92a981bb613e
         kbjfrfpoJU: 0ce336f5a522abef136f82ccf0f3335144
       oycqAZloTNDm: 0000000000000000000000000000000000
       abKPld1EcMni: 0000000000000000000000000000000000

I also attempted to inject a ROM using this code:

[COLOR=#000000]sudo nvram [/COLOR]4E30379B-8832-5EE1-A4E2-D190AA2797B7[COLOR=#000000]:ROM=%[/COLOR]74%d4%35%1f%62%fd

It has been modified to match my system, the UUID being replaced by the one shown in the debug above, and using the MAC address from my ethernet.
However, the value does not seem to change whatsoever, as re-running debug returns the same results. Even upon reboot.

Attempting to sign into iMessage returns this:

​

Any help regarding this issue would be much appreciated. Thank you for your time.

 

[esafeddie]

Haha, how'd you do that. I didn't think it was possible, which is why i bought this $3k Mac.

If this was directed at me - I achieved it by using clover as my boot loader and following Jay's guide and by doing so saved my self a boatload ($3k) of money lol.

 

[pac-man]

Wow - that's amazing!

Thank you "jaymonkey" for the really great re-design and re-structured Guide!

 

[nimonster]

So does this mean I should just write random numbers for the MLB and ROM in the correct length if I shouldn't clone? What do you mean by using the serial number?

I have the most recent unibeast.

By the way very helpful and nicely laid out guide!

 

[slim.jim]

Hello Jaymonkey.

I've followed your guide up to this point, and have updated Chameleon to the latest version using Chameleon Wizard, installed fileNVRAM in /Extra/modules (don't know if it is functioning correctly or not), and ran iMessage debug.

The debug returned this:

              Model: iMac14,1
           Board-id: Mac-031B6874CF7F642A
       SerialNumber: C02KV205F8J2
      Hardware UUID: 4E30379B-8832-5EE1-A4E2-D190AA2797B7


          System-ID: 7402D403-3504-1F05-6206-FD0700080009
                ROM: failed
  BoardSerialNumber: failed


         Gq3489ugfi: 4c13d3259bccad836c14b3a414494f7684
          Fyp98tpgj: d954b6584ce4c3cb45355f92a981bb613e
         kbjfrfpoJU: 0ce336f5a522abef136f82ccf0f3335144
       oycqAZloTNDm: 0000000000000000000000000000000000
       abKPld1EcMni: 0000000000000000000000000000000000

I also attempted to inject a ROM using this code:

[COLOR=#000000]sudo nvram [/COLOR]4E30379B-8832-5EE1-A4E2-D190AA2797B7[COLOR=#000000]:ROM=%[/COLOR]74%d4%35%1f%62%fd

It has been modified to match my system, the UUID being replaced by the one shown in the debug above, and using the MAC address from my ethernet.
However, the value does not seem to change whatsoever, as re-running debug returns the same results. Even upon reboot.

Attempting to sign into iMessage returns this:

View attachment 127978​

Any help regarding this issue would be much appreciated. Thank you for your time.

Start using Clover.

 

[Fly1ngSquid]

Start using Clover.

Not quite the help I was looking for.

Changing to clover won't be easy for me, as I run a Windows 8.1 and Yosemite dual-boot on a single drive. If you'd like to give me some pointers, I'm open for them.

 

[zeuscba]

Hello Jaymonkey.

I've followed your guide up to this point, and have updated Chameleon to the latest version using Chameleon Wizard, installed fileNVRAM in /Extra/modules (don't know if it is functioning correctly or not), and ran iMessage debug.

The debug returned this:

              Model: iMac14,1
           Board-id: Mac-031B6874CF7F642A
       SerialNumber: C02KV205F8J2
      Hardware UUID: 4E30379B-8832-5EE1-A4E2-D190AA2797B7


          System-ID: 7402D403-3504-1F05-6206-FD0700080009
                ROM: failed
  BoardSerialNumber: failed


         Gq3489ugfi: 4c13d3259bccad836c14b3a414494f7684
          Fyp98tpgj: d954b6584ce4c3cb45355f92a981bb613e
         kbjfrfpoJU: 0ce336f5a522abef136f82ccf0f3335144
       oycqAZloTNDm: 0000000000000000000000000000000000
       abKPld1EcMni: 0000000000000000000000000000000000

I also attempted to inject a ROM using this code:

[COLOR=#000000]sudo nvram [/COLOR]4E30379B-8832-5EE1-A4E2-D190AA2797B7[COLOR=#000000]:ROM=%[/COLOR]74%d4%35%1f%62%fd

It has been modified to match my system, the UUID being replaced by the one shown in the debug above, and using the MAC address from my ethernet.
However, the value does not seem to change whatsoever, as re-running debug returns the same results. Even upon reboot.

Attempting to sign into iMessage returns this:

View attachment 127978​

Any help regarding this issue would be much appreciated. Thank you for your time.

I had the same problem with the "Failed" on BoardSerialNumber field and solve it following the steps of "Reset FileNVRAM Plist" of this guide, then use a MLB Generator again, restart and run iMessage dubug to verify that the valors reamain, log into iMessage, obtain a customer code and call apple..etc, etc..