Jump to content

iMessage and FaceTime - misbehaving again!

yosemite facetime imessage

Best Answer fusion71au, 06 August 2014 - 12:02 AM

@theconnactic,

 

Yes, you can use the serials from the MBP.

 

The crucial values, ROM & MLB, must be genuine and from the same Mac (I also use the same 12 Digit System Serial from my mac mini but I'm being careful).  The SmUUID for the hack can be unique and different from the Mac's.

 

Applying MLB & ROM to the "RT Variables" section in Clover (and MLB in Main Board Serial key in SMBIOS section of config.plist) ----> your hack will show the same model in the "About this Mac" screen as the "donor" Mac but since everything else in the SMBIOS section is correct, then Clover uses the appropriate SMBIOS for power management, sleep etc.

 

PS Why don't you create a Clover boot USB and boot into your Mavericks/chameleon install?  Just find the system-ID, ROM & MLB of the chameleon install like I explained in my procedure  and use them in the appropriate sections of Clover's config.plist on your USB.  Run the iMessage-debug tool to confirm that all the variables are the same when booting with Clover :).

Go to the full post


  • Please log in to reply
46 replies to this topic

#21
theconnactic

theconnactic

    Stubborn AMD user

  • Local Moderators
  • 2,907 posts
  • Gender:Male

P.S.: I have to type my iCloud password every boot. That's unusual behavior.



#22
fusion71au

fusion71au

    InsanelyMac Sage

  • Members
  • PipPipPipPipPipPip
  • 430 posts
  • Gender:Male

@theconnactic,

 

Please follow my procedure exactly and run the imessage_debug tool again on your ASUS netbook hack.  The values should be the same as the values you get when you run the tool on your MBP.

 

Your provided config.plist has all the serials hashed out (I assume you did this deliberately for security reasons? :))

Errors I noticed

  • MLB=6 characters instead of 17
  • ROM=6 characters instead of 12
  • SmUUID=22 characters instead of 32
  • Serial Number=13 characters instead of 12
  • No custom UUID specified in System Parameters (Custom UUID= 32 digit System ID)
  • Inject SystemID is set to false instead of true

The fact that "About this Mac" doesn't show the model of the "donor" Mac suggests that your config.plist isn't being saved correctly or being saved in the wrong location in the EFI.  See this post by @MilesTeg1 who had similar symptoms to you but later discovered that his config.plist wasn't being saved in the EFI!!!

 

PS

Can you upload the output of imessage_debug on your MBP and the output when you run it on your hack?  Of course you should hash some/all the characters in your serials...I want to compare the other outputs (IOPower variables). 



#23
theconnactic

theconnactic

    Stubborn AMD user

  • Local Moderators
  • 2,907 posts
  • Gender:Male
Sorry, fusion: all the strings have the correct number of digits, and I did hashed for security reasons, but I didn't care for the exactness "spelling" of it: I assumed you'd undestand I put the correct strings from the debug tool into place, verbatim, which I did. But you in fact perhaps uncovered a mistake: I'll set inject system ID to false: of your recommendations, is the only one I haven't already done.
P.s.: I'm worried my nvram isn't working properly, despite having a nvram plist at the root, because I'm prompted to input my iCloud password every time I start my computer.

P.p.s: will do. This time, I'll hash exactly. ;)
P.p.p.s.: oh, and my config is indeed in EFI.

#24
theconnactic

theconnactic

    Stubborn AMD user

  • Local Moderators
  • 2,907 posts
  • Gender:Male
Solved! Silliest mistake possible: so silly even you couldn't spot it on my config.plist. See:

<key>MLB</key>
<data>xxxxxxx</data> instead of <string>xxxxxxx</string>

The mistake was present in both MLB and ROM keys. Corrected it, now everything goes fine. But I must add this: thanks to I being very specific in the SMBIOS, it still displays as a MacBookAir in System Report.

I'll mark this as solved, for everyone to know your solution works even in cases like mine. Thank you very much for the advices and patience to help me out.

All the best!

#25
fusion71au

fusion71au

    InsanelyMac Sage

  • Members
  • PipPipPipPipPipPip
  • 430 posts
  • Gender:Male

@theconnactic,

 

Congratulations and my pleasure :thumbsup_anim:.

 

Thanks for confirming the method works (personally, I knew it would if everything from NVRAM to the use of genuine serials was done correctly and meticulously) :).

 

If you use Clover Configurator to input the MLB & ROM values, it correctly uses "string" instead of "data" specified (incorrectly) in the Clover wiki for the ROM entry.

 

I think your findings emphasize how good El Nono's original research was and that the exact same variables are still used in iMessage & Facetime authentication then as now.  The only difference is that Apple have become stricter in their checking for genuine serials....

 

Regards

Fusion



#26
TimeWalker75a

TimeWalker75a

    InsanelyMac Legend

  • Gurus
  • 1,056 posts
  • Gender:Male
If only he'd used what was provided as an installer package a topic like this would be needed. The serials are gashed because the placeholder plist I use is being populated with valid data only at postinstall. The MLB can be 17 characters since it's the same thing as board serial, but serial number for older Macs was 12 characters, newer use new structure and it's indeed 13. Injecting system Id is not a problem either. It works like this on all of my machines. And I have zero issues with FaceTime/Messages on this very same netbook running Yosemite DP5...

#27
theconnactic

theconnactic

    Stubborn AMD user

  • Local Moderators
  • 2,907 posts
  • Gender:Male
Fusion, This seems to confirm something I said back then, and was promptly dismissed as FUD, that the authentication protocol changes were a little jab at people accessing their servers from ilegimate hardware, that is, at us. Back then, the optimistic rebuttal was it was a simply change for a safer authentication protocol, conveniently forgetting that the steps taken to supposedly make it safer were not the kind of what would make an individual's Apple ID harder to crack (like stricter ID checks, passwords etc) but of what would make harder for an individual's use his/her legitimate Apple ID (previously created on an iDevice or even a Mac) to enjoy their iCloud services without buying a Mac. Indeed, a change for a safer protocol: safer for their servers, from us. QED.

If it was not enough, they just got the way the check was being circumvented and circunvented the circumvention, lol. I wouldn't doubt a black market of real Mac MLBs, ROMs and serials end up developing itself if this stricter check isn't, forgive me the lousy pun, put in check. Is not like Apple is cracking down on OSX86 - they're definitely not! - but be sure they don't want it to become easy enough to make a real Mac an eccentricity of high-income geeks. They will do the best they can short of a TPM. Remember, AppleMobileFileIntegrity.kext is on OS X now.

P.S.: as for Clover configuration, I don't use it because Clover developers recommend not to.



If only he'd used what was provided as an installer package a topic like this would be needed. The serials are gashed because the placeholder plist I use is being populated with valid data only at postinstall. The MLB can be 17 characters since it's the same thing as board serial, but serial number for older Macs was 12 characters, newer use new structure and it's indeed 13. Injecting system Id is not a problem either. It works like this on all of my machines. And I have zero issues with FaceTime/Messages on this very same netbook running Yosemite DP5...

Walker, I made this topic after a DP update broke messages for me (not only on the 1201N) even though I have previously followed your procedure ipsis literis. Don't take offense, I'm not saying your guide is flawed or incomplete (otherwise I wouldn't cheer about it in all related topics), rather not infallible (like any thing under the sun, if you allow me petty philosophy). Since I used your support package, I haven't touched my EFI folder, until I lost the services. I could waste my time and your patience trying to find out why did it happen, but decided to solve it in a way it won't happen again, which seems to be the promise of this solution Fusion gave me, and try and understand Clover, instead of being spoonfed a pre-made fix. It's a win-win. No offense, I repeat: I do admire your work.

#28
theconnactic

theconnactic

    Stubborn AMD user

  • Local Moderators
  • 2,907 posts
  • Gender:Male

Hi again!

 

As an experiment, I backed up my config.plist from my 1201N, wiped the entire EFI folder from its EFI partition, deleted also the boot file, and reinstalled everything from scratch following (again) TimeWalker's guide, using his updated package installer, as per this post:             #7            

 

I immediately lost the ability of log in to both iMessage and FaceTime. Same symptoms I was experiencing when I created this topic. So I can safely say Walker's guide and tools, regardless how well designed both of them are, don't address iMessage and FaceTime issues, at least on Yosemite. He reports having both services working fine, and that's good, but it seems it was mostly luck, for the fact of old ways of enabling iMessage and FaceTime are still working for him. Unfortunately, that's not true for a growing number of people. For them, including me, Fusion/El Nono solution of including certain legitimate serials seems to be the only hope for now. As soon as I put back my backed up config.plist and restarted the computer, I recovered my ability to log in to both services.

 

All the best!



#29
TimeWalker75a

TimeWalker75a

    InsanelyMac Legend

  • Gurus
  • 1,056 posts
  • Gender:Male
Sure .. pure luck...

Your Apple ID (xxx) was used to sign in to FaceTime and iMessage on a MacBook Air 13" named “ION MacBook Air”.

Date and Time: August 6, 2014, 11:35 AM PDT

Operating System: Mac OS X,10.10,14A314h

If you recently signed in to this device, you can disregard this email.


Perhaps the issue lies in the post installation script, it may be generating improper serials, but how do you explain my serials being valid if they were generated by same script. But then again, I have pushed 4 iterations of my package for Vostro and Inspiron and nobody ever told me voodoo daemon is not being installed in the right place ... The script can be found in Resources/postflight in 1201 project on my git (account name Dolnor). See if you can locate the culprit...

#30
theconnactic

theconnactic

    Stubborn AMD user

  • Local Moderators
  • 2,907 posts
  • Gender:Male
Pure luck in the sense you can count on fingers the people which can actually log out and in to FaceTime or iMessage with the old method nowadays, that is, non-registered serials, ROM and MLB.

Apple changes the way it checks authentication, Walker: I'm not debating this, because it's a proven fact. It's not your tool's fault it doesn't work for me: it's Apple's. Cool it's still working for you, and I hope it keeps that way because I can tell I had a bad time until I realized what was going on and decided to ask for help.

All the best!

P.S.: I'll surely will take a look at the post installation script, but out of pure curiosity: as I told you, the culprit is already found. :)

#31
TimeWalker75a

TimeWalker75a

    InsanelyMac Legend

  • Gurus
  • 1,056 posts
  • Gender:Male
Highly doubt it is. I logged in to messages and FaceTime on that day for the first time (the day DP5 for released) on this netbook. Previously it has only been linked to iCloud.

I can log in and out on my DELL too, where same approach is used, only different serial length because it's a newer machine.

#32
fusion71au

fusion71au

    InsanelyMac Sage

  • Members
  • PipPipPipPipPipPip
  • 430 posts
  • Gender:Male

@theconnactic,

 

I think the bottom line is that Apple are trying to prevent "free loaders" from using their premium services like iMessage & Facetime.  The only proven ways to get iMessage working on a hack (once the basics such as ethernet is set to en0, NVRAM made functioning) are

 

1. Using working serials from a real Mac (Apple Support validated hackintosh also works)

2. Adding a credit card to your Apple ID

 

Both of these conditions mean that you have proven to Apple that you are a paying customer and are registered.

 

The advantage of the first method is that you don't need a credit card, you can apply the serials to any machine and you can still login and logout using any Apple ID - even one without an attached credit card.

 

As an experiment

1.  Create a new AppleID without attaching any credit card

2.  Logout of iMessages on your current account

3.  Login to iMessages using your new ID and see if it works :wink_anim:

 

PS I agree with you that Apple is not trying to totally prevent us from running our hacks (otherwise they could just block FakeSMC.kext instead of placing it in their kext exclude list)....they won't mind unless hacks can easily be made to function 100% like Macs by novices ie they don't mind technical experts like those on this forum to "try before buying" :).



#33
TimeWalker75a

TimeWalker75a

    InsanelyMac Legend

  • Gurus
  • 1,056 posts
  • Gender:Male

In case of MLB I don't think your suggestion about it being 6 characters long instead of 17 would result in *valid* data.

AnV just posted his MBP8,1 dump, which has the following board number: C021482021**TMYAJ (I've covered 2 chars just in case). 

I don't think Apple would go stripping down serial numbers down to 6 chars when putting vars from SMBIOS to NVRAM.. 

Same goes for ROM - since it's a MAC address variable, why would it be 6 chars? Besides, Clover automatically parses it from Ethernet adapter and puts it as a var into NVRAM.

 

Edit: 

Sorry, disregard that .. I'm still sleepy :D it was ERROR NOTICED, not suggested structure.



#34
TimeWalker75a

TimeWalker75a

    InsanelyMac Legend

  • Gurus
  • 1,056 posts
  • Gender:Male

Edit 2:

 

Just tried the script which is responsible for number generation .. it properly produces 11 character number for Air2,1 and MLB/Board numbers that are 17 chars long. The data type can be either string or data - it doesn't matter, Clover can parse both. BUT! I've found that it had a flaw .. it was generating week number using chars, while older 11 character formats used 2 numbers to indicate week number the machine was produced.... Correcting the issue and going to selfsolve page now results in "We're sorry, the number you have provided cannot be found in our records." when checking a generated number. Message simply meaning that a machine with such a number was never registered in Apple Care. I will push an update to the package when I find a way to elegantly limit it to 52 week range ;D



#35
theconnactic

theconnactic

    Stubborn AMD user

  • Local Moderators
  • 2,907 posts
  • Gender:Male
Walker, Fusion did not suggest a 6 character MLB: he thought I was using a six character MLB, because I posted 6 "*" instead of my own MLB to illustrate my config.plist structure.

Okay, your script did have a flaw, but I was having the same issue with my Desktop, for which I had used both Champlist and Chameleon Wizard to generate the serials. Once I put my MBP's, problem solved! :)

Fusion, I do have a valid credit card registered with my Apple ID, yet I cannot log in to iMessage or FaceTime with any automatically generated serial anymore. I'm one of the unlucky ones that need real Mac serials since Apple tightened the grip. So it's safe to say method 1 is better than 2.

All the best!
P.S.: Walker, just noticed your disregard notice: disregard that part of my post.

#36
TimeWalker75a

TimeWalker75a

    InsanelyMac Legend

  • Gurus
  • 1,056 posts
  • Gender:Male

Still, give package v1.2 a try, it should resolve the issue for you.

Cham plist was coded by a single person from inmac.org, it doesn't mean it's 100% accurate in terms of producing valid data for every Mac model.. 



#37
theconnactic

theconnactic

    Stubborn AMD user

  • Local Moderators
  • 2,907 posts
  • Gender:Male
I'll test and report back here (or there in the 1201n).

All the best!

#38
asapreta

asapreta

    InsanelyMac Legend

  • Members
  • PipPipPipPipPipPipPip
  • 755 posts

I'll give a try using my mac mini info but I also would like to know about this " package v1.2 " you're talking about. What is it?



#39
TimeWalker75a

TimeWalker75a

    InsanelyMac Legend

  • Gurus
  • 1,056 posts
  • Gender:Male
It's only meant for eee pc 1201N post installation. I doubt it will be of any for anyone else.

#40
asapreta

asapreta

    InsanelyMac Legend

  • Members
  • PipPipPipPipPipPipPip
  • 755 posts

Oh, okay. Thanks for the answer.

 

I'll try the solution mentioned here regarding MLB and ROM and other stuff.

 

EDIT: Using MLB and ROM like described before, iMessage worked.







Also tagged with one or more of these keywords: yosemite, facetime, imessage


0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

© 2014 InsanelyMac  |   News  |   Forum  |   Downloads  |   OSx86 Wiki  |   Mac Netbook  |   PHP hosting by CatN  |   Designed by Ed Gain  |   Logo by irfan  |   Privacy Policy