Jump to content

iMessage Problem getting bigger? Need help.. Customer Code not helping


mo92
 Share

8 posts in this topic

Recommended Posts

Hi, 

 

I've been trying to make my perfect Hackintosh for weeks now. It has been working very well for quite some time, but yesterday as I installed my original Apple WLAN and Bluetooth card (for continuity) I couldn't log back into iMessage/Facetime (had to sign out and back in to iCloud).

 

When I originally tried to get iMessage working, it was a struggle even though using Clover. I finally got it working using a real iMac serial number and calling Apple about the customer code. Now this time when it gave me the code, I read even more about it and found that I had to have a (generated) unique serial number.

 

I followed this guide for iMessage: http://www.tonymacx86.com/general-help/110471-how-fix-imessage.html#post795297

 

After changing this I just called Apple and the guy was asking me for my serial number which he couldn't identify. In the guide it said your serial needs to be unique, valid but unregistered, which on selfsolve.apple.com should give you the message "We're sorry, the number you have provided cannot be found in our records. Please verify the number and try again" which it shows for mine. Anyway, the Apple guy finally said he won't need the serial number just the customer code and after he told me to log in.. it still didn't work, iMessage would show me the same customer code to call Apple. He tried to solve the problem, asked more and more things and I finally told him I had to go, as I didn't want him to find out about my hackintosh.

 

But here's my problem, I want to get it working and I shouldn't change my serial once again, shouldn't contact Apple again without understanding what the problem is and fixing it. 

I wonder if it has something to do with my ROM value. When I run iMessage Debug the value looks like this, contains a space: ROM: <4246da1f bf56>

The values for ROM and MLB are injected by Clover, my MLB is the serial number followed by five random numbers so this should be fine. 

 

Any ideas? Any help is very appreciated :)
Thanks, Moritz

 

Link to comment
Share on other sites

The verification process is still the same, its just the values must be genuine due to Apple server side checks.

 

If you use the MLB and ROM from a real Mac, activation is still successful and you can still logout/login.  However, there are many user reports coming in that the "Call Apple Support with Error Code" method is no longer working to register fake generated serials on Apple's servers as of last week.

 

It appears that Apple are clamping down and checking on the validity of serials and only genuine MLB/ROMs from real Macs continue to work and activate iMessage/Facetime.

 

The guide on the "other" site spreads a lot of FUD about using MLB/ROM from a real Mac - it is OK as long as you don't publically share the values (better still, you actually own the Mac so its MLB/ROM is already registered to your AppleID).  The risk of Apple blacklisting your genuine MLB/ROM arises if you share the values so multiple different AppleIDs might login to Apple's servers at the same time, using the same MLB/ROM.

___________________________________________________________________________________________

 

PS

Have a look at this insightful post by ElNono_ about what the developers of VMWare Fusion 7 had to do to enable iMessage to work on OSX Yosemite Guests running on real Mac Hosts:

"Welp, it looks like it only copies ROM/MLB. Obviously the two matching kernel hashes, oycqAZloTNDm and abKPld1EcMni end up being the same too, which is expected. The rest of the values (IOPlatformSerialNumber, IOPlatformUUID, boot-uuid, board-id, product-name) are VM generated.

system-id seems not to be populated by the VM. I noticed there's a "system-id.enable" option for the vmx, but have not played with it, and it's apparently off by default. Since system-id is disabled, the IOPlatformUUID value follows the legacy convention: prefix "00000000-0000-1000-8000-" followed by the VM "primary" (en0) ethernet mac address.

I guess it makes sense, you want the VM to look like a different machine than the host, but at the same "pass" whatever server-side checks are there. AFAIK, VMWare has been in contact with Apple about this issue, per the previous thread link"


So the only values from the real Mac hosting the VM that are required to activate iMessage on the OSX Yosemite guests are its MLB and ROM combo - everything else like system-id and system serial are "generated"/"fake" values!

  • Like 2
Link to comment
Share on other sites

Thanks for your answers, I guess I have to wait to have my MacBook Pro from 2011 repaired to read the ROM/MLBs from it as it's one suffering the graphics problem and won't even boot anymore  :(

Link to comment
Share on other sites

It appears that Apple are clamping down and checking on the validity of serials and only genuine MLB/ROMs from real Macs continue to work and activate iMessage/Facetime.

 

Thats not true. Please read this post: Pattern of MLB (Main Logic Board)

 

The reason why some users (not all!!) have succeeded by using genuine MLB and ROM is very simple. Those values bypass regular expression validation on Apple services server. Thats the trick. A lot of users have followed misleading instructions by using random values. It's exact science how to generate those values. Several standards are involved into Serial Number, MLB and ROM generation. If you miss something here, you have an invalid value, which is unable to bypass Apples validation. 

 

Read linked post for more details.

  • Like 1
Link to comment
Share on other sites

 Share

×
×
  • Create New...