Jump to content
heryts

How to Solve Imessage Login Problem

168 posts in this topic

Recommended Posts

Advertisement

We can even use this under SMBIOS instead of RtVariables > MLB

<key>BoardSerialNumber</key>

<string>C02K7438DRVCN1S5A</string>

 

I dont know what is the equivalent of RtVariables > ROM under SMBIOS though.

Share this post


Link to post
Share on other sites

We can even use this under SMBIOS instead of RtVariables > MLB

<key>BoardSerialNumber</key>

<string>C02K7438DRVCN1S5A</string>

 

I dont know what is the equivalent of RtVariables > ROM under SMBIOS though.

yes you're right, thats why it called deprecated, just to make simple in this guide in one section rt variable :)

ROM value can be overriding by putting smuuid value, as you can see 12 digits last number from smuuid is my mac address and in rt variable it is converted to base 64

Share this post


Link to post
Share on other sites

We can even use this under SMBIOS instead of RtVariables > MLB

<key>BoardSerialNumber</key>

<string>C02K7438DRVCN1S5A</string>

I dont know what is the equivalent of RtVariables > ROM under SMBIOS though.

There's no equivalent for ROM, it's injected automatically by Clover instead.

Share this post


Link to post
Share on other sites

@heryts

One more inquiry... How were you able to convert UEZdNpmp to PF]6%99%a9? Tried converting it with the link you provided but gave me different result.

Share this post


Link to post
Share on other sites

heryts.... Many thanks for this info .. yes I was right, had only enter the top of the MAC address these colons ( : )

 
Now I have this ROM is inserted into the times Config.plist at Clover and let's see if iMessage is still going.
Yesterday it was already, in spite of the wrong ROM input. 
 
but one thing is still funny, I have taken Clever and with your instructions another system UUID as in chameleon and Mavericks. 
 
Although I have the same system UUID, as read by Mavericks with your tool 
imessage_debug have eigetragen in Cloverconfigurator, the system UUID in Yosemite is quite different. 
 
I want it so only under Yosemite use with Clever. 
 
In Mavericks I'm still working with Chameleon and folders in Modules is the Filenvram.dylib (version 1.1.3) 
 
Chameleon at Yosemite does not work when in folder Extra / modules this is filenvram.dylib it, then boot Chameleon not (even the latest version in 2391).

Share this post


Link to post
Share on other sites

Actually it doesnt matter with different system uuid, the most important is you have same mlb and rom read by imesage-debug, i add smuuid in case if we cant overide ROM value on clover, as i found on some hardware when it bios doesnt support write nvram without emuvariabel uefi driver, and by injecting smuuid will solve this problem on such hardware

To confirm if your value is working or not, you should sign out and sign in agan, and the last its true you cant use chameleon on yosemite, so the only option at the moment is using clover if we want to use this value on yosemite

Share this post


Link to post
Share on other sites

Heryts. Thank you for the wonderfull and experienced tipps.... You a absolut Experts.

Share this post


Link to post
Share on other sites

Hi heryts,

Thanks to ElNono_/flux84's iMessage debug tool, I was able to spoof my genuine Mac mini 2012 on my GA-P55aUD3/Intel i5-750/Radeon 5770 desktop and activate iMessages in Yosemite (no credit card required!) :).

I ran the attached tool in OSX terminal on my Mac mini and used the values from the mini in the config.plist of my hack:

  • IOPlatformSerialNumber---->Enter 12 digit SerialNumber key in SMBIOS section of config.plist
  • IOPlatformUUID ----> Enter SmUUID key in SMBIOS section (32 digits separated by dashes ie XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX)
  • ROM: <xxxxxxxx xxxx> ----> Enter 12 digit ROM key in RtVariables section of config.plist (12 digits without the space). Note - I did a direct copy, did not need to convert to Base64
  • MLB: XXXXXXXXXXXXXXXXX ----> Enter 17 digit MLB key in RtVariables section and also in BoardSerialNumber SMBIOS key

After rebooting my hackintosh, I ran the debug tool again and confirmed the MLB, ROM, IOPlatformUUID, IOPlatformSerialNumber were identical to the mini's. The hack even shows as a Mac mini (late 2012) in 'About this Mac' despite using an iMac 11.3 SMBIOS :hysterical: ....

 

post-846696-0-50137900-1405848326_thumb.

imessage_debug.zip

Share this post


Link to post
Share on other sites

that's because you have entered correct smuuid value on smbios section, so it will override the ROM value on RT variable, as you can see last 12 digits of SMuuid is mac-addres, you can try deleting ROM value in RT variable, it will still show your  ROM value of your genuine Mac Mini, but if you delete SMuuid value you will see wrong ROM value, because you haven't coverted it to base 64 yet, any way that's not my tool i just found it on google and congratulation

Share this post


Link to post
Share on other sites

that's because you have entered correct smuuid value on smbios section, so it will override the ROM value on RT variable, as you can see last 12 digits of SMuuid is mac-addres, you can try deleting ROM value in RT variable, it will still show your  ROM value of your genuine Mac Mini, but if you delete SMuuid value you will see wrong ROM value, because you haven't coverted it to base 64 yet, any way that's not my tool i just found it on google and congratulation

 

Hi heryts,

 

Just to clarify a few things...

 

The iMessage fix for Clover/Chameleon and the iMessage debug tool that you posted are based on the original research of @ElNono_,and @tflux - it would be nice to acknowledge them in your first post...

 

On a real mac,

  • the last 12 digits of the Hardware ID/IOPlatformUUID or "SMUUID" have no relation to ethernet mac address
  • The "ROM value" is the firewire mac address with two middle bytes removed if present, otherwise it is the ethernet mac address
  • The "MLB" is the Main Logic Board Serial Number/dmi type 2
  • The IOPlatformSerialNumber corresponds to the "System Serial" number

 

The confusion comes from the defaults used by Clover when the ROM and MLB are not specified in the RT Variables section of config.plist...See dmazar's post @ProjectOSX for Clover r978.

 

"By default, if not specified in config.plist:

- MLB will be set to SMBIOS/SerialNumber  <---later versions of Clover use Main Board Serial Number

- ROM will be set to last 6 bytes of SMBIOS UUID (or config.plist SMBIOS/SmUUID if specified); on some boards those last 6 bytes of UUID are ethernet MAC address - this is what we would like to insert"

 

Initially, Apple did not check whether MLB and ROM values were genuine or not, as long as they were the correct length (17 digits and 12 digits long), everything worked.  More recently, it seems Apple's servers are checking for genuine serials...

 

From my experimentation spoofing my genuine mac mini with my desktop hack to activate iMessage:

 

1. The SmUUID specified in Clover's config.plist can be any 32 digit number but Clover will use the last 12 digits and inject it as the ROM value if a ROM value is not specified in the RT Variables section.

2. The crucial values to set in Clover's config.plist are the ROM and MLB.  This is best done by extracting them from a real Mac with the iMessage_debug tool and putting them directly in the RT Variables section of Clover's config.plist.  NO conversion from Hex--->Base64 required.

3.  For safety's sake, I also use the genuine 12 digit System serial number from my mac mini in the config.plist.  Maybe the MLB and ROM that you posted before got banned because it was used with Fake System Serials &/or more than one person logged into iMessage at the same time with the same MLB/ROM combination....

 

PS The source code for the debug tool did come from ElNono_- read the bottom of the post I linked to.  Other people took the code and compiled it - see post by @pupin, another post by @flux84 ---> distributed without attribution of the original author on the internet.

 

The 32 digit SmUUID still needs to be specified for iMessage activation to work, but it can be any random 32 digit number (so I agree activation will fail if one is not specified).  The System-ID is related to SmUUID and is infact used to calculate SmUUID through some hashing process.  To find this value, just use terminal

ioreg -l -p IODeviceTree | grep \"system-id

as explained by dmazar/Slice (no need for DumpUefiCall).

 

The crucial things to specify are MLB, ROM & System Serial from a real Mac.

 

PPS Please don't get me wrong.  I appreciate all the work and testing you have done for the community so far :thumbsup_anim::) .  I just wanted to acknowledge the original authors/developers of the iMessage fix.  Their findings are still valid today but what has changed is that Apple is checking whether the serials used are genuine and if they aren't, you get the message to contact Apple Support....

Share this post


Link to post
Share on other sites

as now for new MLB and SMUUID I registered by contact apple support is

 

MLB 1111111111111111

SMUUID 11111111-1111-1111-1111-111111111111

 

and you can use it to activated iMessage from it, just to put those value on smbios section as on picture

 

or if on chameleon

 

sudo nvram 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:ROM=%11%11%11%11%11%11
sudo nvram 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:MLB=1111111111111111

post-1336554-0-77493200-1405495451_thumb.jpg

post-1336554-0-76384400-1405495473_thumb.jpg

Share this post


Link to post
Share on other sites

:yes:  this is working, thanks heryts !!!!!

 

Aug 24 12:35:54 System32.local login[507]: USER_PROCESS: 507 ttys000

Aug 24 12:35:54 System32.local imessage_debug[511]: Gq3489ugfi: <b2106dce 2d55f3c3 08b5b3e2 c8912224 74>

Aug 24 12:35:54 System32.local imessage_debug[511]: Fyp98tpgj: <1ec3bf76 437669a1 d9f99024 b2f92f2e a4>

Aug 24 12:35:54 System32.local imessage_debug[511]: kbjfrfpoJU: <6e3f4d38 e3a3f940 ff06a319 5d03f63c 2f>

Aug 24 12:35:54 System32.local imessage_debug[511]: IOPlatformSerialNumber: xxxxxxxxxxx  use  your valid serial number

Aug 24 12:35:54 System32.local imessage_debug[511]: IOPlatformUUID: 79C87F0E-9227-5AAD-AA91-25F794E1F52E

Aug 24 12:35:54 System32.local imessage_debug[511]: board-id: Mac-F2268DAE

Aug 24 12:35:54 System32.local imessage_debug[511]: product-name: iMac11,1

Aug 24 12:35:54 System32.local imessage_debug[511]: 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:ROM: <11111111 1111>

Aug 24 12:35:54 System32.local imessage_debug[511]: 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:MLB: 1111111111111111

Aug 24 12:35:54 System32.local imessage_debug[511]: oycqAZloTNDm: <5ac6462e 0ce8756b 25cb4a46 08fe17d5 52>

Aug 24 12:35:54 System32.local imessage_debug[511]: abKPld1EcMni: <49ca31ae 47f0b2bd 57ca66e2 91fbb1e0 ad>

Aug 24 12:35:54 System32.local login[507]: DEAD_PROCESS: 507 ttys000

 

 

post-333439-0-06810900-1408877890_thumb.png

Share this post


Link to post
Share on other sites

 fusion71au , 

 

Thanks!!!!  :D

 

a bit of war to put iMessage to work, but the fix from heryts work to me  :thumbsup_anim: , thanks!!!!

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

×