Jump to content

Search the Community: Showing results for tags 'iMessage'.

More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • InsanelyMac Lounge
    • Front Page News and Rumors
    • Reader News and Reviews
    • Forum Information and Feedback
  • OSx86 Project
    • New Releases and Updates
    • New Users Lounge
    • Developers Corner
    • Tutorials (The Genius Bar)
    • Technical FAQ
    • OSx86 Installation
    • Post-Installation
    • DSDT and SSDT
    • Hardware Components and Drivers
    • Complete Desktops
    • Notebooks
    • Netbooks
    • Tablets
    • MacMod of the Month
    • Multi-booting and Virtualisation
  • International
    • Your Language
    • Deutsch
    • Español
    • Français
    • Italiano
    • Português
    • Русский
  • Apple World
    • Mac OS X
    • Apple Computers and Hardware
    • iOS Devices
    • Mac Applications
    • Mac Programming and Development
    • iOS Programming and Development
    • Mac Gaming
    • Mac Accessories
  • Discuss and Learn
    • Windows Discussion
    • *nix
    • Apple Opinions and Discussion
    • The Great Debates
    • Internet(s), Servers, and Networks
    • Buying Thoughts, Reviews, and Recommendations
    • Mods and Overclocking
    • The Big Issues [Real Life]
  • Everything Else
    • Creativity
    • Thunderdome (Random Stuff)
    • Laughs
    • The Marketplace


  • Kexts
    • Graphics Cards
    • Audio
    • LAN and Wireless
    • Other
  • Kernels
  • Bootloaders
  • DSDTs
    • Patches
  • Pandora
  • Apps
  • Miscellaneous
  • Customization

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start




Website URL







Found 37 results

  1. Pattern of MLB (Main Logic Board) serial Alert: If you are seeking for some quick single click iMessage fix, this is not about that at all.. This research digs a much deeper, it's about an aspect of building computer, which is able to run properly OS X. This post is purely educational. Understanding of this subject also requires knowledge of some basics of ICT. This topic isn't for sure for Windows dumb user, who wants some sort of OS X single click installations. For single click solutions buy a genuine Mac. Since Apple has made several changes on services, hardware identification becomes more and more important. For proper activation is needed a valid stable device. Device serial numbers, various hardware id's etc are part of identification and authentication. Just for clarity. Abbreviation MLB is shortened form of phrase Main Logic Board, which is a hardware part (motherboard). Abbreviation MLB is used by custom comp builders community also as Serial ID of Main Logic Board, which is an identification code of single unique hardware part. In this post MLB can refer to both, serial id of main logic board or main logic board itself. So, pay attention to the context when your read this post. MLB as hardware part id (barcode), is used by various services on OS X based comp, especially on Yosemite. So, you don't need only a good serial number in your SMBIOS settings, but also a good MLB, which matches logically (not by letter) your serial number. It's obvious at this point, that proper serial number isn't enough anymore. You need a good combination of serial number, MLB, etc. Those values should remain persistent. If someone told you, that MLB and serial number aren't related, you couldn't relay on this information, as MLB and serial number are logically related with each another. Probably I don't have to remind you - system serial number reveals your system model. Probably you haven't heard that MLB reveals exact model of your system Main Logic Board (hardware part) too. The Genesis of Apple computer ID's You can think about Serial Number as an "external id" and MLB as an "internal id". Computers are built from inside out. For first main board, then other parts and finally gets boxed. Serial Number reveals entire product box (comp, device) sold to the customer, MLB reveals the main hardware part inside of this product. Serial Number and MLB are like two puzzle pieces from same unique puzzle. MLB tells even more about your hardware than a serial number. Mac device gets first the MLB id and later the Serial Number. So MLB is the primary identification for Mac hardware before it's assembled completely for selling!!!! Also Apple repair services have who forgot sometimes to burn Serial Number back to the new replacement logic board. Logic boards come from factory without Serial Number. Below is the genesis of genuine Mac comp ID's. Main Logic Board ID -> Serial Number So, your MLB ID is born before the Serial Number! Based on that I recommend to start from generating system and hardware id's in this order: MLB Serial ROM/MAC address System Serial If you have chosen too complicated option for your system serial, you might have a trouble when generating properly matching MLB. Before you read forward, keep in mind, I'm not a hardware engineer, so I'm not familiar with all specifics related to computer hardware. Pay attention - 2 different patterns! General pattern for system serials (barcode) is the same: Manufacturing location | Year | Week | Production number of given week | Model ID Apple uses 2 different main patterns for serials (product serial, hardware part serial etc) now. Before Apple used 11 char serials for product and 13 char for MLB. Later Apple started to use a new standard to fit needs of increased production. Product serial length is 12 chars (Barcode Code 128) and MLB 17chars. Old serials have a bit common pattern for both, products and hardware parts and new ones have also a common pattern. Below is the difference of 11 and 12 char system serials: 11 chrs serial: PPYWWSSSCCC 12 chrs serial: PPPYWSSSCCCC MLB's pattern/length was also upgraded when system serials become updated. Thats why there are 13 and 17 char MLB's available. For new pattern Apple has modified the "Y" component to include a letter code instead of a number, and the new system will reflect in that code not only the year of manufacture, but also whether it was manufactured in the first or second half of the year. The new week format utilizes one of 27 alphanumeric characters to denote the week of manufacture, beginning with 1-9 and moving on to letters, omitting 0, vowels A, E, I, O, and U, as well as B, S, and Z. Because the 27 possible characters can not account for all of the weeks in the year, the "W" component must be paired with the "Y" component to determine whether the machine was manufactured in the first or second half of the year, with the "W" codes recycling every six months. System serials and hardware ids are serving various logistical purposes (barcode). They should be easy to use by barcode reader and should be easy to decipher with simple regular expressions (regex). Its wise to use common general pattern everywhere. So, it's obvious that some pattern might occur for both, system serials and hardware part ids. About 13 char MLB Perhaps someone can complement my research about 13 char MLB. As you see below, there is a certain pattern hidden in MLB. I have found this pattern first after examination of approx. 50 MLB's and is conformed by additional research later. Based on this pattern MLB is easily reversible. Name your MLB and I'm able to tell to you to which Mac model it belongs, where and when made, and so on. It's not a random string. PPYWWSSSSCCCC ID - Manufacturing location? (Defined in Apple database,) Year of manufacturing: 2011 Week on manufacturing (01-52) Production number, within this week (base-36???) ID - Model of hardware part (Defined in Apple database) Please note, it's easy interpret wrongly this pattern, as it has similarities with 11char serial.. Some are guessing that they can use serial number parts for MLB. It's not true. Manufacturing location and model id's aren't shared between serial number and MLB. Definitions in serial number aren't valid for MLB. Do not try to use serial number location or model ids for MLB, those aren't valid. MLB uses its own definitions. If you have any additional or more adequate information about this pattern, please let me know! * * * About 17char MLB's 17 char MLB is a bit harder to decipher. I have found this pattern after examination of approx. 10 MLB's. I suspect that Apple is using a new system for year and week identification for 17 char MLB. I guess that YW pattern occurs in 17char MLBs, but location is shifted and there is only one char used for week. PPPYWXXXXXXCCCCCC I don't have enough data to decipher the 17char MLB pattern yet. You are welcome to help. * * * Apple collects data about you and your hardware Don't fool yourself! You need proper and matching hardware id's for your custom built comp. If you are trying to use any of Apple's online services, Apple collects some data about you and your hardware. You couldn't make a fake Apple ID as it goes trough credit card validation. So, banks are doing identifying of persons for Apple. Using someones credit card and personal data without a proper legal authorisation is criminal activity on most western countries. For second, Apple collects data about you hardware. For example all your devices a listed on iCloud or on another appropriate support pages. Below is screenshot of iCloud Settings page, where all devices, from which you have accessed the service. On certain cases Apple checks for System Serial, on some cases for ROM/MLB pair etc. Your hardware should match on MLB and Serial Number to avoid any too obvious suspicious behaviour. How to slice a MLB? 13 char MLB should be sliced as shown below. XX X XX XXXX XXXX The last part of 13 char MLB can be sliced additionally this way, where XXX is EEE code. XXX X . 17char (still a rough guess) XXX X X XXXXXX XXXXXX The last part of 17 char MLB can be sliced additionally this way, where XXXX is EEE code. XXXX XX You are welcome to support this research. Thank You! * * * How to setup MLB For first, pay attention: getting a good combination of serial, MLB and ROM etc is an exact science. Do not try to guess or randomly generate those values. Invalid values will cause a head-heck and if you are trying to use some Apple services, you get banned for those services soon or later, especially iMessage and FaceTime. Your system serial and MLB are sent to Apple! MLB and system serial should match logically. Do not contact Apple's support in any case, even if you have this kind alert. You are not eligible for Apple support with custom built computer. Please note also, you couldn't just convert Serial Number into MLB. You can bake a MLB, but you couldn't convert Serial Number directly into MLB. Do not try. Similarity is confusing, MLB and serial number are sharing only overall barcode pattern. Serial number is good point from where to start, thats obvious, as MLB and serial should have logical match, but not match by letter. You couldn't use MacPro logic board on MacBook, it's obvious and super easy to check by Apple. So, pieces of puzzle should fit with each another. I guess it's smart to use similar production time with system, just set MLB production time up to 6 months earlier of system production time. Production number is easy to calculate. Trickiest parts are the beginning and the end as there is no easily accessible public info avilable about these parts for MLB. The best option to inject proper values into your system, is to use Clover boot-loader, which injects all those values properly. An option to setup MLB is to open your Clover configuration file with text editor and add/edit appropriate values. Second option is to use some GUI for editing Clover configuration file. Read Clover Wiki for more details. Below is an screenshot how to setup MLB with Clover Configurator. Serial Number should be a good one to imitate Apple's hardware and also should be appropriate to your system. MLB should be either 13 chars or 17 chars and match the appropriate pattern. Also hardware model info in MLB should be logically adequate to your system defined in Serial Number. ROM part is defined in SmUUID and should be 12 chars and match the Apple's MAC address standard, otherwise illegal. Do not use any random UUID generator for this purpose, for example uuidgen on Mac OS X. Validate your ROM part of SMUUID before usage with Apple ROM validator. If motherboard manufacturer supports flashing comp MAC addresses, you can also try to rewrite original MAC addresses with valid Apple type MAC addresses. On this scenario value is taken directly from hardware. Flashing of MAC address is also the most bullet proof option to keep ROM value unchanged. Read about flashing on this post: Flashing Mac Address. Important note. For Clover use for all values UPPER CASE letters. I got a huge head heck with iMessage/FaceTime by using lowercase values. Note, If your serial is 11 chars, it's recommended to use 13 chars MLB. If you are using 12 chars Serial Number, you should use 17char MLB. It's not the 100% rule, but somewhere between 2007-2010 Apple started to use a new pattern for identification numbers (product serial, hardware serials etc). iCloud / iMessage / FaceTime errors Apple provides 44 different online services for his customers. Most of these require some sort of identification/authentication. Before signing into any Apple's services from custom built comp, think twice. And after that, think twice again! Are you Apple's customer at all? Do you have any genuine Apple device, which grants access to Apple's services? If yes, it's a bit up to you from where you access these services, from your custom built mac or from iDevice or from iCloud webpage etc. Whatever you do, do not attack Apple or anyone else! NB! Most of iMessage Fixing guides available on Internet are invalid today. Be very careful! If you got error shown below on your custom made comp, I do not recommend contact Apple support. This error isn't authentication related at all! It's related to hardware identification, usually related to an invalid ROM/MLB combination. Error shown above on custom made comp indicates usually that all of these ids or some of these are invalid: System Serial Number, Main Logic Board Serial (MLB), ROM. Apple is trying to protect users from spying/fraud etc. This error means that Apple suspects some sort of dangerous activity. So, they want to protect their customers privacy, etc. To check that your Apple ID is fine: login into your comp as Guest and try to log in into iMessages. If you see something like below, it's 100% hardware identification issue.Your Apple ID is fine, but Apple doesn't like your hardware. Any custom comp builder, who is trying to access Apples services with invalid serial, MLB or ROM, gonna have some sort of trouble. Most of services require a valid system serial. System serial should match appropriate pattern. The same applies to MLB, which should match the MLB pattern. Some services require both, the proper MLB and ROM. If you have a good serial and proper MLB, you still might have trouble, if your ROM is invalid and doesn't match MAC address standards. Also you need properly configured network card. All those values should be persistent. Do not use any randomly generated values if you want access Apple's services. Same values should be injected on each reboot / wake. Some users have tried to use genuine MLB/ROM values extracted from some another Mac. If you reuse these values, yo mightu put yourself into huge risk, which might end by terminating your Apples account. So be careful, do not steal those from someone. 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, you have an invalid value, which is unable to bypass Apples validation. You need a good combination of MLB/ROM/serial, which doesn't violate related standards! Do your science, don't relay on guesswork. Building a custom built comp, which runs an OS X, is a branch of computer science, not a some kind dumb-users Windows installation. Serial validation: genuine mac and self generated serial Conclusion and alert When you are building you own custom hardware based OS X comp, you have to generate a VALID COMBINATION of serial number, MLB, ROM etc. Hardware combination (system model and hardware part) should match in serial number and MLB. The best boot loader to get job done properly, to inject those values into OS X memory, is Clover. Forgot xBeast / Chimera installers. Do not use Chimera. Once again do not Chimera. TonyMac will sued soon by Apple too. Do not try to sign into any Apple's services before you have made a rock solid combination of serial number and hardware id's. MLB, ROM and Serial etc for your custom made comp should be globally unique values and match appropriate Apple's pattern. MLB and Serial should have logical match. Make sure that your system serial does not belong to anyone else! Those values should be used only in one single computer, nowhere else. Do not share your comp serial numbers, hardware ID's etc with anyone who you don't trust 100%. Do not post it any public forum, blog etc. Don't share it with your friends, colleagues etc. Some old news too Thx! I thank everybody who have helped me and still helping me on this research. Thank you for your contribution. Related tools Apple MAC Hack
  2. Is there any guide to make iMessage work? I tried reseting my apple's id password Changed my ethernet to en0 But nothing worked... Thanks
  3. FabioG

    iMessage OUT

    Buongiorno a tutti, da qualche giorno iMessage ha smesso di funzionare. Non ho mai avuto problemi, non ho installato nulla, ma all'improvviso non funziona più. Inserendo la psw mi dice: Il tuo ID Apple 'fabio.grammauta@libero.it' non può essere usato per impostare iMessage in questo momento. Questo è un nuovo ID Apple, non è necessario crearne un altro. Per usare questo ID Apple con iMessage, contatta l'Assistenza di iMessage e fornisci il codice qui sotto. Ho letto che vi sono dei "dix" che sistemano il problema, ma non so cosa siano. Potete per favore guidarmi? Grazie mille.
  4. need help, iMessage and Facetime is not working. updating clover to Clover_v2k_r2696 is not working either.
  5. So I'm running Yosemite on an HP Sandy Bridge laptop with MacBook 8,2 system definition, and I just picked up the same year(2011) Sandy Bridge MacBook Pro 8,2 that is ridiculously close to the end of it's life. I don't plan on using iMessage or FaceTime if I even use the MBP at all (it's screen is cracked, missing keys, aluminum falling apart, it's had a rough life). So I've taken the SMBIOS variables using iMessage_debug V2, but I'm not sure on what the best way to apply these is and I've seen a lot of conflicting information in the many forums I've checked out. I've seen people imply that MLB and ROM are the only really important variables here, and that if you're taking these values from a real mac that these ones are the only ones you should take while separately generating a serial number, smUUID etc from Clover Configurator or uuidgen. I've also seen people recommend to simply make sure the output of iMessage_debug exactly replicates your hack and real Mac (in the case where the system definition matches the Mac that you're getting the variables from). I've seen people say that you shouldn't take any variables, ever, at all, even from a retired Mac that you already own. A good chunk of the material I've found on this subject is over 5 years old, which is why I think I'm finding a lot of conflicting information. In addition to that most guides etc are written from the standpoint of someone that does not have another mac to take the variables from, and if they do mention scenarios like this it's so briefly touched that I'm still left unsure. Does anyone more experienced have any personal recommendations for someone specifically in my case, where I own a Mac that matches the system definition I'm using for my hack?
  6. I have my system completely setup with Clover 3259, Yosemite 10.10.5 and completed the entirety of the iMessage guide. My injected ROM values are correct and do not change. My hardware specs: • Asus Maximus VI Gene • Intel 4670K, not overclocked • Asus GTX 670 2GB • Apple BCM94360CD iCloud works no problem and all my data syncs to my iPhone 6. Perfect! iMessage allows me to sign in and it recognizes my phone number. However, I'm not able to send messages and all contacts appear in red. If I turn on Text Message Forwarding, it's still not perfect. Contacts only appear in green and any message people send to me do not receive on my computer, just my iPhone. Handoff works fine if I transfer from my iPhone to my computer, but not the other way around. For instance, if I start an email on my computer, the icons for Handoff don't even show up on my iPhone. I've verified that all my devices appear under my iCloud/AppleID account on the website. There are no duplicate devices listed anywhere. The WiFi/BT card appears to work perfectly, never dropping signal to the internet. Bluetooth connectivity works perfectly with my PlayStation 4 controller. Things I've already tried to fix this behaviour: • Removing the plist and cache files from my ~/Library folders • Completely signing out and back in to my iCloud and iMessage accounts on my iPhone and computer • Turning Handoff, Text Message Forwarding, and Bluetooth Sharing off and on again I'm beginning to think that this is an iMessage server authentication issue than anything else, strictly affecting my computer. But I'd rather not call Apple about it until I've exhausted my other options.
  7. Ciao a tutti, ho tra le mani un hackintosh praticamente perfetto (non sono riuscito ad attivare la regolazione della luminosità) e non vorrei combinare ulteriori casini visto che ora uso questo computer per tutto e sono molto soddisfatto! C'è una cosa che non riesco a sistemare ma che mi tornerebbe molto utile; l'utilizzo di iMessage! Su internet ho trovato delle guide ma ho troppa paura di pregiudicare il funzionamento del mio pc. iCloud e AppStore funzionano alla perfezione mentre iMessage mi dà questo errore quando vado ad inserire i dati per il login: Impossibile eseguire l'accesso a iMessage. Si è verificato un errore durante l'attivazione. Riprova. Ho utilizzato niresh Mavericks che è alla versione 10.9 (non ho fatto aggiornamenti per paura di combinare casini di cui sopra). Come boot loader uso chameleon. Mi riuscite a dare una mano? Grazie :-)
  8. Hello Everyone, Here's My Story. I am Using Hackintosh Sine Leopard It worked Flawless till Mavericks. I installed Yosemite Zone Niresh Distro Yesterday. Sine then I am trying to figure out iCloud Fix. Here is what I tried till. Reinstalled OS like 20 times. EFIstudio Method. (This method is to make Ethernet as en0 I already got en0 in System Config.) IMessage Fix V2 (Nireh Hack). Changed SMBIOS to everything. But non of them worked. Details :- Sys Config :- Model Name: iMac Model Identifier: iMac11,1 Processor Name: Intel Core 2 Duo Processor Speed: 1.2 GHz Number of Processors: 1 Total Number of Cores: 2 L2 Cache: 2 MB Memory: 2 GB Bus Speed: 800 MHz Boot ROM Version: Niresh12495.com SMC Version (system): 1.30f3 Serial Number (system): W8053TYI5RU Hardware UUID: D5194B8D-670A-583D-AE52-1874D81675E0 ALX Ethernet Driver: Name: Qualcomm Atheros AR8131 Gigabit Ethernet Type: Ethernet Controller Bus: PCI Vendor ID: 0x1969 Device ID: 0x1063 Subsystem Vendor ID: 0x1458 Subsystem ID: 0xe000 Revision ID: 0x00c0 Link Width: x1 BSD name: en0 Kext name: ALXEthernet.kext Location: /System/Library/Extensions/ALXEthernet.kext Version: 1.0.2 NetworkPreferences.plist <?xml version="1.0" encoding="UTF-8"?><!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>Interfaces</key> <array> <dict> <key>Active</key> <true/> <key>BSD Name</key> <string>en0</string> <key>IOBuiltin</key> <true/> <key>IOInterfaceNamePrefix</key> <string>en</string> <key>IOInterfaceType</key> <integer>6</integer> <key>IOInterfaceUnit</key> <integer>0</integer> <key>IOMACAddress</key> <data> HG9lkk7/ </data> <key>IOPathMatch</key> <string>IOService:/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/PEX1@1C,1/IOPP/ethernet@0/ALXEthernet/en0</string> <key>SCNetworkInterfaceInfo</key> <dict> <key>UserDefinedName</key> <string>Ethernet</string> </dict> <key>SCNetworkInterfaceType</key> <string>Ethernet</string> </dict> </array> <key>Model</key> <string>iMac11,1</string> </dict> </plist> org.chameleon.Boot <dict> <key>CSTUsingSystemIO</key> <string>y</string> <key>DropSSDT</key> <string>y</string> <key>EnableC2State</key> <string>y</string> <key>EnableC3State</key> <string>y</string> <key>EnableC4State</key> <string>y</string> <key>EthernetBuiltIn</key> <string>Yes</string> <key>GenerateCStates</key> <string>y</string> <key>GeneratePStates</key> <string>y</string> <key>Graphics Mode</key> <string>1024x768x32</string> <key>GraphicsEnabler</key> <string>y</string> <key>Kernel Flags</key> <string>debug=8 ahcidisk=1 dart=0</string> </dict> </plist> smbios.plist <dict> <key>SMbiosversion</key> <string>Niresh12495.com</string> <key>SMboardproduct</key> <string>Mac-F2268DAE</string> <key>SMfamily</key> <string>iMac</string> <key>SMproductname</key> <string>iMac11,1</string> <key>SMserial</key> <string>W8053TYI5RU</string> </dict> </plist> PLEASE HELP ME THANK YOU.
  9. What I had already tried Add Credit Card details Reinstall OS X Restarted New serial number Reset password etc. How to fix it? Contact Apple Support Start telling him/her about the problem as soon as he/she says hello. ESPECIALLY about the pop-up and the customer code. Give legit details. Even serial number. Keep telling him/her you are looking at the right place. He/She will say it's invalid. Confirm it again. Eventually, ask him/her to drop it/why does he/she needs it?I asked, and she said to know what Mac I was using. I gave her all the info she could want(Keep Champlist and everymac.com open) He/She'll ask you to repeat the Customer Code. Do it. He/She'll ask you your ID. Give him/her the correct one(The one that you're entering in the Messages app). He/She'll tell you that he/she needs to confirm that you're a real person, and will ask you to answer the security questions that you answered when you created the account(Like "Where did your parents meet?"/"What was your childhood name?"). You'll need to get at least one right(I think). He/She'll ask you to reboot. Do it. He/She'll tell you not to worry. Don't. Voila! You'll be able to login just fine. THANK HIM/HER. So, I think this issue was caused because I had changed so many Serial Numbers that Apple flagged me as a bot. Once I verified my identity, all was well! It worked fine for me, so just sharing. If you've got some problem, feel free to ask, although I've got exams the whole month so probably won't be able to help. Even so, I'll try to.
  10. Hey guys, This is my first topic on this forum, but I've been familiar with the mackintosh community for 3 years, and am not afraid to get my hands dirty. With that said, to the problem. I am having trouble signing into iMessage. And believe me I don't like posting stupid, duplicate topics without a reason to do so. I've read every damn topic on the net I could find, tried it, and all of those failed. It always tells me, "Your Apple ID "[My Mail ID]" can't be used to set up iMessage at this time". But, my father bought an iPhone 5s a couple of weeks ago, and I used it for a week. My iMessage was signed in on the phone. And around that time, I upgraded to Mavericks. I gave my father the iPhone back 3 days ago, and that's when it started giving me this stupid message. So, after browsing a bit, I heard about NVRam and Clover, and saw that my PC didn't have a UUID. So, I got the necessary tools and applied a UUID to my machine. Yet it didn't work. Also tried a full restore, booting from Chameleon, Chimera, and Clover. Nothing works. The only thing that works is signing into my father's iPhone. And again, logging out of that gives me the message. Yes, I've checked for nvram.[uuid].plist, and everything but the IOPower variables are valid. MLB and ROM are in place. Find MyMac works. I've also created a recovery partition. I would also have tried gdb-ing iMessage, but I'm terrible at that. I, currently, am on 10.9.1(It didn't work on 10.9 also). Also, I didn't use Messages when I used 10.8. Any suggestions would be warmly welcome.
  11. Hello, sorry for my english, I'm from Brazil... I have a hack a much longer, around 2, 3 years. I've used Lion, them a updated to 10.8.2 which always work 100%, and now I'm getting a problem: my iMessage does't work. It worked, but when I activated my account on my new iPhone (2 months ago), the iMessage just STOP... now I'm get that message (in image attached). PS: iCloud and Facetime works. If someone knows something about that, please, reply here. THANKS!
  12. I have been trying to get iMessage working on my otherwise perfect Hackontosh. The problem is i cannot switch to clover due to exception 64 error and it's due to my motherboard which is super old it is a Asrock-VGS3-FX and I use a Amd Athlon x2 Black Edition OverClocked to Quad Core with 750 ti Graphics, Now with my specs out for the way I have tried file NVRAM I placed the kext in my Extra Folder and put the modules folder in the Extra Folder but with the filenvram.dylb in the extra folder the system will not boot and also had issues with yosemite I had filenvram in my extra folder when I was running yosemite but than I update to el captain but on yosemite I had no idea how to use file nvram and how to get iMessage working,
  13. Dear Mac users, I'd like to talk about iMessage, El Capitan and Yosemite. I've been using Mac OS X on a Maximus V Gene motherboard with an i7-3770K processor for quite some time now. With the introduction of Yosemite I needed to figure out a way to make iMessage work as it included changes around the same time with validation of MLB and ROM values that were reported by the system and the NVRAM. Here's my basic setup: Chameleon boot loader (previously regular flavor, now ENOCH), drop the Chameleon.plist, insert SMBIOS.plist, FakeSMC, IntelE1000-Ethernet.kext and my systems is working. To enable iMessage I had to install the FileNVRAM.kext (1.1.4 package) and FileNVRAM.dylib (1.1.4 package) file onto the USB stick containing the chameleon boot loader. With this setup, I was able to boot Yosemite fine and get a working NVRAM. However, keep in mind that you have to create the /Extra folder on the hard drive of your OS X install and make it writable by anyone. Then the FileNVRAM.kext is able to create the nvram.1d34-12d4d1234-1d341234.plist ( ) which contains the data you have written. Whenever I needed to boot the system with -v -f or when doing software updates, I had to use a second Chameleon stick that did not include the FileNVRAM.kext and dylib files. (If booting with -v -f and FileNVRAM installed, the system would crash on caching the kexts) I would then boot the system, run kext utility or similar permissions-checking and kext-caching applications and reboot with the FileNVRAM-USB stick. This was my full working arrangement. Tedious, but worked excellent. Never had a problem with iMessage, FaceTime, iPhone Calls, AppStore, iTunes or iCloud. So far so good, but it was time to move to El Capitan. In El Capitan I encountered the problem that kexts cannot be passed through the Chameleon boot loader but have to be installed directly into /S/L/E and have to be cached by a running system (usually just boot the same SSD from a real Mac). This forced me into a predicament with the FileNVRAM.kext which had to be loaded through Chameleon as it wouldn't otherwise boot. So by trial and error I examined a problem with the FileNVRAM.kext on 10.11.3 which resulted in it not being loaded, no matter where you put it. Reason why? The Info.plist of the FileNVRAM.kext has the following code written in it: <key>OSBundleLibraries</key> <dict> <key>com.apple.iokit.IOStorageFamily</key> <string>1.0b1</string> <key>com.apple.kpi.bsd</key> <string>8.0b1</string> <key>com.apple.kpi.iokit</key> <string>7.0</string> <key>com.apple.kpi.libkern</key> <string>8.0d0</string> <key>com.apple.kpi.mach</key> <string>8.0d0</string> <key>com.apple.kpi.unsupported</key> <string>8.0b1</string> </dict> Not sure if you spotted the error yourself, but the IOStorageFamily version is too low for El Capitan. This OS X ships with 2.1 instead and the kext simply refuses to load. If you change this value in the Info.plist file, the kext is loadable. This is more of a dirty patch than a correct solution. So what happens next: I got my El Capitan working again with the same approach as above, but no FileNVRAM module or kext anywhere, neither Chameleon, nor OS X. When the system is booted up I would install the FileNVRAM.kext into /S/L/E, onto the /E/E on the Chameleon stick and in the /E/E folder on the hard drive. Same with the module, /E/E on both hard drive and chameleon stick. Now I would have to run kext utility again to precache the FileNVRAM.kext into the system and reboot. Sometimes it wouldn't boot up, sometimes it would "break" the system (fixable by dropping FileNVRAM from all instances and touching /S/L/E and running kextcache -u / from single-user mode or external system) - but most of the times it just works. NVRAM is capable of saving and creating the /Extra/nvram.xxxxxx.plist file and returning the required MLB/ROM values after being saved - even after reboot. Thus I have managed to get FileNVRAM.kext working by this trick in El Capitan. Despite this solution working for me and probably others, my hope is that there is someone capable of updating the FileNVRAM.kext file for El Capitan and its latest Xcode? The kext itself is still working, but the dependencies are off and thus causing the issues. Thank you and have fun! Florian P.S. Edit: Here's the files I used. (dylib and kext) http://uploaded.net/file/uc9c18wc(zip-file of the Extra folder)
  14. So if I use the command: sudo nvram joe=cool then nvram -p | grep joe it shows joe cool But after I reboot the machine nvram -p | grep joe shows nothing. Any ideas? This might explain issues with iMessage, might not. But it does seem to be a problem nonetheless.
  15. 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
  16. iMessage , Facetime work on Yosemite without any Data from ( serial and rom ,etc) Generic Mac All I have was Create App password and login. And Real apple Mini pci-e wifi + bluetooth BCM94360CD/BCM94331CD and PCI-e Adaptor Mini apple wifi+bluetooth - http://www.ebay.com/itm/Apple-Broadcom-BCM94360CD-802-11ac-mini-WLAN-Bluetooth-4-0-Wireless-card-/191029765954?pt=LH_DefaultDomain_0&hash=item2c7a42e742 Pci-e Adaptor - http://www.ebay.com/itm/BCM94360CD-BCM94331CD-to-PCI-e-1X-Adapter-for-hackintosh-and-PC-/231370068228?pt=LH_DefaultDomain_0&hash=item35debb1104
  17. Hi, Wondering if anyone is having the same problem I am having. I'm almost 100% certain its related to installing Yosemite and usingiMessage on it. I was using iMessage successfully on Yosemite Beta for a few hours. After which I switched back to my Mavericks system but when I tried to use iMessage it will not sign in. I have tried changing the password but still not working. Its working fine on my iPhone. If any one can point me in the right direction it would be great. Thanks in advance J
  18. Good morning everyone, I been trying to get my iCloud to work with little success. I tried all the fixes out there: EFI studio, Ethernet Built in, NVRAM module, etc. I also tried installing mountain lion but the same problem persists. When I do try to login to iCloud I get "Unable to sign in because of a problem communicating with iCloud" message. I am able to login into the APP STORE (I downloaded apps) and iTunes without any issues. When I do attempt to login into iMessage I input my credentials and it actually goes through, but two seconds after it logs me in iMessage goes "inactive" requiring me to input my password again. When I do input it again, it gives me trouble activating iMessage. I am currently running 10.9 with just Audio, R9 270 Kext, and RealtekRTL81xx.kext version 0.0.90. I made sure to update Chameleon and I can confirm my Ethernet is "en0" in system info I am using Chameleon pre made SMBIOS MacPro 3,1 and I randomized the Week of Manufacture and Unique Number Besides the fact iCloud/iMessage is not working I have a fully functional system. If I missed anything please do no hesitate to ask.
  19. burtsevmax96

    weird iMessage issue

    hey guys i faced a strange issue with iMessage on yosemite 10.10.3 it doesn't send or receive any messages including "green" ones i'm a complete noob in hackintosh and i'm not really sure what information should i give to you, so ask anything you need http://www.insanelymac.com/forum/topic/306330-imessage-wont-receivesend-imessages-but-receivessends-regular-texts/ - THIS DIDN"T HELP AT ALL
  20. Having a problem with my install of the mavericks gm. I'm able to log into, and use, FaceTime, iCloud, etc, without issue, but iMessage gives the error "An error occurred during activation. Try again." whenever I try to log in. I'm running the latest chameleon, and I've made sure the serial number in my smbios is 17 digits. I've made sure ethernet built in is in my boot plist, and then removed all my network interfaces, deleted the network preference file, restarted and re-added ethernet to make sure it is en0. At this point I'm kind of out of ideas/suggestions I've found on the forums here. Anything else I'm missing?
  21. I've installed Yosemite with [url=&quot;http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/&quot;]#####[/url], actually i'm using Chameleon. The problem is the next: I can't sign in with my iCloud account to sync my Notes, Messages, Calendar and things like that. I already tested a LOT of proceeds written on the internet, but no one worked. Note: I'm using a wireless adapter because here in my room do not have ethernet cable, and also hackintosh don't detect my ethernet card. I have FileNVRAM on the modules folder. org.chameleon.Boot <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>EthernetBuiltIn</key> <string>Yes</string> <key>IGPEnabler</key> <string>Yes</string> <key>Kernel Flags</key> <string>kext-dev-mode=1</string> <key>Legacy Logo</key> <string>Yes</string> <key>Timeout</key> <string>2</string> <key>UseKernelCache</key> <string>Yes</string> <key>GraphicsEnabler</key> <string>Yes</string> <key>DropSSDT</key> <string>Yes</string> <key>SMboardserial</key> <string>CK148614DB6F940D2</string> <key>SMsystemuuid</key> <string>a8dd17a0-cf10-4323-9841-29a9f08c1d49</string> <key>SMchassisserial</key> <string>CK129U13DB67</string> <key>SMserial</key> <string>CK129U13DB67</string> </dict> </plist> NetworkInterfaces <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>Interfaces</key> <array> <dict> <key>Active</key> <true/> <key>BSD Name</key> <string>en0</string> <key>IOBuiltin</key> <false/> <key>IOInterfaceNamePrefix</key> <string>en</string> <key>IOInterfaceType</key> <integer>6</integer> <key>IOInterfaceUnit</key> <integer>0</integer> <key>IOMACAddress</key> <data> 6E4GG+gE </data> <key>IOPathMatch</key> <string>IOService:/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/EUSB@1D,7/AppleUSBEHCI/802.11n WLAN Adapter@fd800000/IOUSBInterface@0/RTL8192CU/en0</string> <key>SCNetworkInterfaceInfo</key> <dict> <key>USB Product Name</key> <string>802.11n WLAN Adapter</string> <key>UserDefinedName</key> <string>802.11n WLAN Adapter</string> <key>idProduct</key> <integer>33142</integer> <key>idVendor</key> <integer>3034</integer> </dict> <key>SCNetworkInterfaceType</key> <string>Ethernet</string> </dict> <dict> <key>Active</key> <true/> <key>BSD Name</key> <string>en1</string> <key>IOBuiltin</key> <false/> <key>IOInterfaceNamePrefix</key> <string>en</string> <key>IOInterfaceType</key> <integer>6</integer> <key>IOInterfaceUnit</key> <integer>1</integer> <key>IOMACAddress</key> <data> ABWDB81d </data> <key>IOPathMatch</key> <string>IOService:/IOResources/IOUserEthernetResource/IOUserEthernetResourceUserClient/IOUserEthernetController/en1</string> <key>SCNetworkInterfaceInfo</key> <dict> <key>UserDefinedName</key> <string>Bluetooth PAN</string> </dict> <key>SCNetworkInterfaceType</key> <string>Ethernet</string> </dict> </array> <key>Model</key> <string>iMac14,2</string> </dict> </plist>
  22. marcoenancy

    Problemi vari

    Ciao a tutti, Ho seguito passo passo la guida per creare la chiavetta USB di installazione con Clover, ma una volta che seleziono "avvia macOS da Installer" si blocca l'avvio. Qualcuno può aiutarmi? Allego il mio EFI Configurazione in firma Grazie!! EFI.zip
  23. Hello everyone, I bring you today an easy installation of the latest El Capitan (10.11.5) with the CPU 5960X (16 cores) installed on ASUS X99 Deluxe U3.1 motherboard with a Nvidia GTX 908 Ti !! (Versão em Português aqui) Once installed, the following features are 100% operational: 1 x Ethernet adapter + Wlan @ 5Ghz adapter All USB3.0 ports available Nvidia 980ti working with 3 monitors and sound AppleHDA + functional HDMI CPU energy management operation from 1.2Ghz to 4.5GHz Bluetooth, AirDrop, Facetime, iMessage all workin and much faster than in 10.10.5 (Yosemite) !! Without NullCPUPowerManagement.kext the VoodooTSCSync.kext the IOPCIFamily.kext (modified) and without a modified kernel - The case of Yosemite in 5960X ... Requirements: "Install OS X El Capitan.app" downloaded and installed in the Applications folder Get the app "El Capitan HD.zip" here Access to a Mac/Hackintosh already with El Capitan installed and with SIP turned off, as described here An EMPTY SSD/hard disk on SATA/USB - If not empty, the "El Capitan HD" will format it completely !! Access to the Serial Number, ROM and MLB on a real mac Thanks: Brumbaer, stinga11, chris1111, the Clover team, onmybikedrunk, jamiethemorris, pokenguyen and many, many more ... Installation: 1 - Download the file "Comprimido.zip", which contains the Kexts, tools and EFI folder already pre-configured here and decompress on your downloads folder of your Mac/Hackintosh. Then configure the BIOS 3101 of the ASUS X99 Deluxe as per the screen snapshots stored here. 2 - Run the application "El Capitan HD.app" to install the basic configuration of El Capitan into an EMPTY SSD/hard disk: 2.1 - Enter your password at about 4% 2.2 - Wait for the end, such as: 3 - Use the "Clover Configurator.app" application to mount the EFI partition. 3.1 - "Mount EFI" 3.2 - "Check Partition" 3.3 - Search by type identifier "/dev/diskX" disk that contains the partition "Macintosh-HD" 3.4 - "Mount EFI partition/diskXs1" 4 - Install the latest CLOVER v2.3: 4.1 - Run CLOVER v2.3 application and install it on to the disk "Macintosh HD," with the following options: 4.2 - Use the "Finder" file manager to copy the files: 4.2.1 - <ZIP directory>/EFI/CLOVER/ACPI/*.* to the folder EFICLOVER/ACPI/ 4.2.2 - <ZIP directory>/EFI/CLOVER/config.plist to the folder EFI/CLOVER/ 4.2.3 - <ZIP directory>/EFI/CLOVER/kexts/10.11/FakeSMC.kext to the folder EFI/CLOVER/kexts/10.11/ 4.2.4 - <ZIP directory>/EFI/CLOVER/drivers64UEFI/OsxAptioFix2Drv-free2000.efi to the folder /EFI/CLOVER/drivers64UEFI/ 5 - Use the application "KCPM Pro.app Utility" to install the Kexts onto the "Macintosh HD" disk and then repair its file permissions and rebuild the kext Caches: AppleGraphicsControl.kext (changed already to SMBIOS 6.1) AppleIntelE1000e.kext BrcmFirmwareRepo.kext BrcmPatchRAM2.kext FakeSMC.kext X99_Injector.kext 6 - Start the PC with the new 10.11.5 installed, by selecting UEFI OS (P1:xxxxxx) 6.1 - In CLOVER boot menu, select "Boot Mac OS X from Macintost-HD" 6.2 - Setup the country and don't setup yet your AppleID 6.3 - Setup a new user 6.4 - Login and then run the application "Kext utility.app" and wait for the end of its operations: 6.5 Drag and drop the "LegacyUSBHub.kext" (for USB3.0) and "AppleHDA.kext" (changed to ALC1150) onto the window of "Kext utility" and wait for it to end its operations: 6.6 - Re-start the PC 9 - Install Nvidia Driver Web - http: //us.download.n...46.03.10f02.pkg 9.1 - Install the Nvidia CUDA - http: //www.nvidia.co....29-driver.html 9.2 - Re-start the PC 10 - To configure iMessage/FaceTime its necessary to extract various data from a real Mac: 10.1 - Check that the Ethernet network card is set to "en0" by running the "DPCIManager.app" application: 10.2 - Re-do step 3 again to mount the EFI partition 10.3 - Navigate to and follow the steps to extract (from a true Mac) the following data: Serial Number, SmUUID and Board Serial Number - used for "Clover Configurator.app" application in the "SMBIOS" section ROM & MLB identifier - used for "Clover Configurator.app" application in the "Rt Variables" section (Using the "iMessageDebug" in a terminal window) 10.4 - Re-start the PC Boa sorte, Paulo End results: Tests: Information sources: iCloud / iMessage / FaceTime - http: //www.insanelym...h/#entry2020598 http: //www.insanelym...ative-work-thru http: //www.insanelym...-capitan-10113/ http: //www.insanelym...-hotspot-patch/ http: //www.insanelym...hda-hdmi-audio/ http: //www.insanelym...da-audio/page-1 http: //www.insanelym...edstep-working/ https: //sourceforge..../Snow_or_Above/ https://nickwoodhams.com/x99-hackintosh-solving-osxaptiofixdrv-allocaterelocblock-can-not-allocate-relocation-block/
  24. http://imgur.com/CTorsta Credits go to redditors on the Hackintosh subreddit themacmeister, HackinDoge and badchromosome Essential kexts from Rehabman's guide And obviously Apple for making this amazing system in the first place Specs: Processor: Intel Core i7 4500U (Haswell) Graphics: Intel HD Graphics Family + Radeon HD 8670M RAM: 8 GB (two chips, 4 GB each - originally came with 4 GB, I added a chip ) WiFi: Broadcom BCM94322HM8L/Dell Wireless-N 1510 Mini Card ( Mini PCIe, half-size) (they're both the same card under two names) SMBIOS: MacBook Pro 11,1 - Retina, 13 inch Late 2013 (laptop's actually 14 inches though ) Hard Disk partitions: Microsoft Reserved (128 MB) Windows 10 Pro (350 GB) OS X El Capitan (127 GB) OS X Recovery Partition (got deleted later, no intention of getting it back) 1 GB HFS+ (purpose explained later) EFI System partition (205 MB) Windows OEM Recovery (21 GB) Hey everyone... so I managed to get my first Hackintosh build running without having to wipe everything completely! This could be useful for those of you who are trying to: Get OS X El Capitan on HP laptops. Don't want to ruin your existing Windows installations. Fix issues with Intel graphics cards. Don't want to dilute OS X with distro installations. I used Apple's createinstallmedia method for El Capitan and made it on an internal 24 GB drive in my laptop (this was installed alongside my 500 GB drive apparently for use as a cache disk, but it never worked so I thought I'd make use of it instead of buying another USB) using a VMware Mac (you can download the image on the TechReviews Youtube channel, the link is in a video description). After making my installer drive, I installed Clover from their SourceForge site and added: HFSPlus.efi to drivers64UEFI folder FakeSMC.kext to the "Other" kexts folder To the 10.10, 10.11, and Other kexts folders I added: Rehabman's VoodooPS2Controller (this was working with the installer, but didn't work in the system. Still looking for a fix.) HPRAIDInjector.kext (If you have a hard drive attached as SATA RAID, this may be necessary) RealtekRTL8100.kext for Ethernet (although I did notice WiFi was working out of the box) LegacyAppleAHCIPort.kext In Clover Configurator, I added these: (specific credits to themacmeister and R3habman) ig-platform-id = 0xa260006 (specific to Intel HD 4400) Injected IntelGFX device-id = config.plist/Devices/FakeID/IntelGFX=0x04128086 FakePCIID.kext and FakePCIID_Intel_HD_Graphics.kext to the 10.10/10.11/Other kext folders I was using cpus=1 to boot before I remembered to turn on KernelPM in Clover. That way, you use both CPU cores. Now, to prepare the drive for OS X. I shrunk my Windows partition by 1 GB, then 120 GB. In case you didn't notice above, right after my El Capitan drive, I have the recovery partition, then 1 GB HFS+, and THEN my EFI partition. The reason for this is that, when I booted into the installer and tried to install El Capitan, it failed showing a message "The installation failed because (something, I forgot what it was) would make your Windows installation unbootable". I learned from this that your OS X partition should NEVER be anywhere near your EFI boot partition, maybe because the installer shrinks the El Capitan partition to make the recovery partition, which probably might damage the nearby EFI System partition. So I shrunk the El Capitan by 1 GB again, just to make it as a barrier between the El Capitan partition and the EFI partition, and then the installer worked! For some of you who are having MediaKit errors when trying to format your El Capitan partition from exFAT or FAT32 or NTFS to Mac OS Extended (Journaled), do it in Windows. First format your partition as NTFS, then download Paragon NTFS-HFS Converter. This software is literally a goddamn blessing - it does exactly what it says, and converts your NTFS-formatted partition to HFS+ (or Mac OS Extended (Journaled), same thing) all on Windows itself without any stupid MediaKit errors :-) After installation, I used the same internal drive's Clover to boot into OS X, which worked like a charm. The system itself is very fast and responsive. My WiFi, PS/2 mouse and keyboard and external USB mouse work Rehabman's VoodooPS2Controller and I'm still working on these issues: Battery worked when I got Rehabman's battery kext and the DSDT patch from here. Used MaciASL to patch. Great thanks to this guide, iMessage and FaceTime work perfectly! Here's what I did to fix it, thanks to rehabman. Cheers!
  25. It gives me random error messages like "[AppleID or Phone Number] is not registered with iMessage." or "Your message could not be sent. - Click "Try Again" etc" I used the nvram workaround as-well as adding a valid serial for my "mac model", and added a new valid credit card. I am now signed into the mac app store, iCloud, and even signed into iMessage. But I cannot send or receive messages. Any ideas?