Contribute
Register
Hi,

From my real MacBook Pro 15'' Mid 2010 (6.2):

Number of Bytes making up the MLB: 13
Number of Characters in the string: 13
Your System Type: MacBookPro6,2
Last four digits of OSX S/N: PAGZ

First five hex values of MLB: 57 38 30 32 38
First five string values of MLB: W8028
Last three hex values of MLB: 55 50 41
Last three string values of MLB: UPA
 
I finally plucked up the courage to change to clover after my iMessage stopped working when I went over to a RAID 0 setup.

I have managed to get everything working (I think) as I have the customer code which does not change on restarts.

I gave apple a call, gave them an OS X/SN from my real macbook pro. The lovely man on the other end of the phone put the customer code in I gave him, but no luck. He attempted this at least 4 times. He then told me he had another customer earlier that day with the same problem and had to pass it onto the "Mac team" as he was a part of the "iCloud" team. Unfortunately I was busy and couldn't continue with the call, which was logged and I have been given a reference number to call back at a more convenient time for myself.

I have had this code once before, and when I called it was entered into apples system and it activated immediately. I am now worried that, as this is the second time of me calling with another customer code, they might be a little more thorough with their investigations. Has this happened to anyone else?
 
from an iMac

:MLB
------------------------------------------------------------------------------
000000: 43 30 32 33 30 XX XX XX XX XX XX XX XX 35 33 41 |C0230XXXXXXXX53A|
000010: 54 |T|


system type: iMac13,2
last 4 of SN: DNMN

if it matters the ROM value matches en0
 
last 4 SN: DV35
system type: MacBookPro9,1
MLB:

000000: 43 30 32 32 33 XX XX XX XX XX XX XX XX 32 35 41 |C0223XXXXXXXX25A|
000010: 56 |V|

ROM consists of the first 3 bytes and last 3 bytes of fw0
 
Probably too small a sample size for now but I do notice almost (if not all) 17 char MLBs have a '1' or 'A' as the 2nd last char
 
Here's another one, but this is from imessage debug, not darwin dumper, hope its ok

OSX SN last 4: F8J5
product-name: iMac14,2
MLB: C0232xxxxxxxx3FAE
 
And another

OSX SN last 4: HDAS
Model IDentifier: iMac11,2
MLB

000000: 43 30 32 31 31 XX XX XX XX XX XX XX XX 4a 4e 31 |C0211XXXXXXXXJN1|
000010: 36 |6|
 
Interesting finding. But why does changing the MLB and ROM from a real mac work? I used MLB and ROM from an air, and it worked on my imac system definition (everything but the mlb and rom remained generated by clover configurator). Shouldn't that have not worked if the MLB needs to be a certain length depending on the system definition?
 
Cloning real macintosh values undermines the apple security system, and risks messing up hackintosh progress in every way. Also worth realising apple almost certainly pays people to keep an eye on this (and other hack) forums.
imessege and icloud security is a big issue. Why should the hackintosh community threaten it? We must stick to using unique system values before something bad happens.

:banghead:
 
Cloning real macintosh values undermines the apple security system, and risks messing up hackintosh progress in every way. Also worth realising apple almost certainly pays people to keep an eye on this (and other hack) forums.
imessege and icloud security is a big issue. Why should the hackintosh community threaten it? We must stick to using unique system values before something bad happens.

:banghead:

I am very concerned this will affect iCloud eventually. I can live without iMessage and FaceTime, but iCloud integrates so many things I use daily that losing it would mean I would have to switch back to Windows (I refuse to buy an iMac as it doesn't suit my needs).

I realize people want to get this to work, but I'm so afraid people will not be patient enough to do this, "by the book" and create issues that will be unsolvable, or worse screw up features like ICloud, App Store, Xcode, etc.

I really encourage everyone to take a step back, not contact Apple, and allow the experts here to determine the issue. Calling Apple, creating tech support tickets, escalating issues and the like, might undermine all the work being done here, and make a solution impossible.
 
Back
Top