Contribute
Register
Joined
Jun 9, 2013
Messages
10,684
Motherboard
Gigabyte GA-H77N-WIFI
CPU
i7-3770
Graphics
HD 4000
Mac
  1. MacBook
  2. Mac mini
Mobile Phone
  1. Android
I see .. That actually makes a whole lot of sense, because the serial generator does repeat itself, to some degree. So your saying the mlb could be a possible dupe as well.

Yes. How i found that out was i kept the same values and just replaced the MLB with a genuine MLB from a broken logic board which sorted the iMessage problem out.
 
Joined
Apr 25, 2016
Messages
32
Motherboard
Dell 7347
CPU
Haswell I5 4th Gen
Graphics
Hd 4400 intel
Mac
  1. MacBook Pro
Mobile Phone
  1. iOS
Yes. How i found that out was i kept the same values and just replaced the MLB with a genuine MLB from a broken logic board which sorted the iMessage problem out.
Haha..while you were posting.. I was editing my post to include busted logic board. LOL Thinking alike..
 
Joined
Jun 9, 2013
Messages
10,684
Motherboard
Gigabyte GA-H77N-WIFI
CPU
i7-3770
Graphics
HD 4000
Mac
  1. MacBook
  2. Mac mini
Mobile Phone
  1. Android
Haha..while you were posting.. I was editing my post to include busted logic board. LOL Thinking alike..

Lmao. Just something i had to try. And it sorted my problem out.
 
Joined
Apr 25, 2016
Messages
32
Motherboard
Dell 7347
CPU
Haswell I5 4th Gen
Graphics
Hd 4400 intel
Mac
  1. MacBook Pro
Mobile Phone
  1. iOS
Lmao. Just something i had to try. And it sorted my problem out.
Cool.. That answers that question, i'm going to precede with it then. Thanks!!
 
Joined
Mar 9, 2012
Messages
2,605
Motherboard
Gigabyte Z590 AORUS MASTER
CPU
i7-11700k
Graphics
RX 580
Mac
  1. iMac
  2. Mac Pro
Mobile Phone
  1. iOS
Again no disrespect, since you've been at this a long time. I agree iMessage is a multi tier process. We are here to discuss our findings, and not disrespect? or ridicule? others for no apparent reason. Most of your response has nothing really to do with, what we are saying. You obviously didn't take the time to read anything we've actually said. I said nothing about iMessage fix, not working, or claiming Apple insider security( thanks i'm flattered) We stated, obvious speculation, not fud, nor anything about getting my ethernet card to en0 .. I actually can log into the App store. We ,meaning me, and 3 others who have posted this same message...

Apple's self solve site :

No longer shows the message

We're sorry, the number you have provided cannot be found in our records. Please verify the number and try again

Instead, it just shows:

This Serial Number is not valid

I know at-least two of us here have tried combined 600 times.

Never once.. Using Clover serials did it ever show..We're sorry, the number you have provided cannot be found in our records. Please verify the number and try again

If I may offer a little insight - If you have not done these steps already, one should always try and match the specs of their hack as close as possible to the specs of a real mac. At every change of values i.e. mac S/N, ROM, MLB or any injected values in all failed iMsg/F-Time attempt, before changing the values, you should log out the p/c from all Apple services, i.e. iCloud App Store etc etc this can also have an adverse effect on a successful setup. There is a useful web site (EveryMac.com) where you can put in your Mac s/n and it will return the Model your hack is closest to. Another idea, run DarwinDumper or iMessageDeBugger make a print out of the results, do at least three reboots and each time run run iMsg DeBugger and cross reference the results with the initial one - note there should be no discrepancies or any appendges added to the end of the MLB value such as + or - =.
 
Joined
Jan 20, 2016
Messages
8
Motherboard
Motherboard or System make and full model names > See Rules!
CPU
> Need full CPU model number > See Rules!
Graphics
> Need model name or number > See Rules!
I personally may or may not go through the process again sometime - though I followed the guide to the letter. But that doesn't always mean it's going to be right.

The only point that Piranha and i were trying to make is that it's entirely possible that things have changed. It is, after all, the beginning of a new month. Who knows, these policies could have changed the last day of april or first day of may.

I'm not trying to be lazy or say that I'm more experienced than people who have done this for years - but when it comes to things like these, changes can happen overnight without any warning at all. It might be worth it to wait several more days, but I don't think we should discredit the idea that something has changed. Remaining vigilant is in everyone's best interests.
 
Joined
Jun 9, 2013
Messages
10,684
Motherboard
Gigabyte GA-H77N-WIFI
CPU
i7-3770
Graphics
HD 4000
Mac
  1. MacBook
  2. Mac mini
Mobile Phone
  1. Android
If I may offer a little insight - If you have not done these steps already, one should always try and match the specs of their hack as close as possible to the specs of a real mac. At every change of values i.e. mac S/N, ROM, MLB or any injected values in all failed iMsg/F-Time attempt, before changing the values, you should log out the p/c from all Apple services, i.e. iCloud App Store etc etc this can also have an adverse effect on a successful setup. There is a useful web site (EveryMac.com) where you can put in your Mac s/n and it will return the Model your hack is closest to. Another idea, run DarwinDumper or iMessageDeBugger make a print out of the results, do at least three reboots and each time run run iMsg DeBugger and cross reference the results with the initial one - note there should be no discrepancies or any appendges added to the end of the MLB value such as + or - =.

Another thing id highly recommend is to use Apples Native NVRAM not EmuVaribles-64 only because at least you know that the NVRAM will stay the same on every reboot. Just a thought another thing id highly recommend is that you inject SystemID only because of something called SId Bug which can plague on some motherboards.
 
Joined
Apr 25, 2016
Messages
32
Motherboard
Dell 7347
CPU
Haswell I5 4th Gen
Graphics
Hd 4400 intel
Mac
  1. MacBook Pro
Mobile Phone
  1. iOS
Yes. How i found that out was i kept the same values and just replaced the MLB with a genuine MLB from a broken logic board which sorted the iMessage problem out.

Just for the record.. I got everything working!!!
No change in serial.. or any other parts. I Just reran uuidgen like 10 times/ copied the last one into my smuuid, and made the rom from last part of it.
Changed my MLB like we discussed earlier.. You were 100% correct in your MLB theory. Put it in.. Saved Plist in clover.. and then
edit: forgot to mention .. I also checked the inject system id box in Clover as well.

I deleted everything from.. (below) logged out of of iCloud .. Rebooted and, bada bing, bada bang!!, bob's your uncle.. everything works
      1. cd /Users/~username/Library/Caches/
      2. sudo rm -rf com.apple.iCloudHelper*
      3. sudo rm -rf com.apple.Messages*
      4. sudo rm -rf com.apple.imfoundation.IMRemoteURLConnectionAgent*
      5. cd /Users/~username/Library/Preferences/
      6. sudo rm -rf com.apple.iChat.*
      7. sudo rm -rf com.apple.icloud.*
      8. sudo rm -rf com.apple.imagent.*
      9. sudo rm -rf com.apple.imessage.*
      10. sudo rm -rf com.apple.imservice.*
      11. sudo rm -rf com.apple.ids.service*
      12. sudo rm -rf com.apple.identityserviced*
      13. sudo rm -rf com.apple.security.*
 
Last edited:
Joined
Mar 9, 2012
Messages
2,605
Motherboard
Gigabyte Z590 AORUS MASTER
CPU
i7-11700k
Graphics
RX 580
Mac
  1. iMac
  2. Mac Pro
Mobile Phone
  1. iOS
Once again correct formulation of SmUUID, ROM and MLB wins the day!!!!!
Guys please listen, it's imperative to get this part right, check check and then some before calling Apple.

Like I said if you're told by Apple tech all is well at their end, then the problem definitely lies with your injected values.
The 'Fix iMessage' guide is extensive because it tries to cover every possible scenario to getting it right.

If at first you hit a snag, don't start looking for the complicated, always start with the obvious - ROM, MLB and SmUUID values should be first port of call. These values can be easily checked by running iMessage DeBugger, these values must remain constant between reboots.
 
Joined
Jun 9, 2013
Messages
10,684
Motherboard
Gigabyte GA-H77N-WIFI
CPU
i7-3770
Graphics
HD 4000
Mac
  1. MacBook
  2. Mac mini
Mobile Phone
  1. Android
Just for the record.. I got everything working!!!
No change in serial.. or any other parts. I Just reran uuidgen like 10 times/ copied the last one into my smuuid, and made the rom from last part of it.
Changed my MLB like we discussed earlier.. You were 100% correct in your MLB theory. Put it in.. Saved Plist in clover.. and then

I deleted everything from.. (below) logged out of of iCloud .. Rebooted and, bada bing, bada bang!!, bob's your uncle.. everything works
      1. cd /Users/~username/Library/Caches/
      2. sudo rm -rf com.apple.iCloudHelper*
      3. sudo rm -rf com.apple.Messages*
      4. sudo rm -rf com.apple.imfoundation.IMRemoteURLConnectionAgent*
      5. cd /Users/~username/Library/Preferences/
      6. sudo rm -rf com.apple.iChat.*
      7. sudo rm -rf com.apple.icloud.*
      8. sudo rm -rf com.apple.imagent.*
      9. sudo rm -rf com.apple.imessage.*
      10. sudo rm -rf com.apple.imservice.*
      11. sudo rm -rf com.apple.ids.service*
      12. sudo rm -rf com.apple.identityserviced*
      13. sudo rm -rf com.apple.security.*

Yep. Having a valid MLB makes a a difference :thumbup:.
 
Top