Localhost: vmware$./system.sh VMware7,1 VMWVk21tM5F4+1Uty1UOSqjAQ 440BX Desktop Reference Platform Let's swap these out for some genuine looking Apple settings. Firstly, you need to have a running OS X guest and a copy of Chameleon Wizard to generate the relevant IDs.
I also suggest you take a snapshot first just in case you make a mistake. Step 1 - Create unique identifiers Fire up your OS X guest and run the downloaded copy of Chameleon Wizard in the guest.
We are not going to be using the Chameleon boot loader just using the wizard's capability to generate various identifiers such as serial number and board-id. Click on the SMBIOS button Select Edit Select a model and other parameters to generate a spoof ID. In this example I have created a MacBook Pro 6.1 with a re-manufactured serial number. Please do not re-use these but generate your own to make sure everything you do is unique. The 3 pieces of information you need to copy to the host are:.
Product Name. Board Product. Serial Now close down the guest ready for the next step. Edit the VMX file Open the VMX file for your guest in a text editor and add the following lines. Board-id.reflectHost = 'FALSE' board-id = 'MAC-F22589C8' hw.model.reflectHost = 'FALSE' hw.model = 'MacBookPro6,2' serialNumber.reflectHost = 'FALSE' serialNumber = 'RM129481AGW' smbios.reflectHost = 'FALSE' Make sure you do not have any duplicate lines or VMware will not load the guest and give you a dictionary error message. The 'board-id.reflectHost ' is normally added from the new VM wizard and set to trye so make sure you set it to false.
El Capitan on VirtualBox. How to Install Mac OS X El Capitan on VirtualBox on PC. Video memory 128 mb, ram 1.5gb, mac os, set to mac 10.11 El capitan. March 30, 2017. Mukhtar Jafari. Before adding the code to the cmd exit virtual machine. I find that I can’t long into the Apple Store to install any apps. Seems as if the serial number.
Save the VMX file start the guest. Step 3 Check the system You should now be able to use the 'System Information' application to see that the guest is using the product and serial number you specified. Hardware Overview: Model Name: MacBook Pro Model Identifier: MacBookPro6,2 Processor Speed: 2.53 GHz Number of Processors: 2 Total Number of Cores: 2 L2 Cache (per Processor): 256 KB L3 Cache (per Processor): 12 MB Memory: 4 GB Boot ROM Version: VMW71.00V.0.B723 SMC Version (system): 1.16f8 Serial Number (system): RM129481AGW Hardware UUID: 000-1000-8000-000C292AA301 Attached is a small script file which can be run from Terminal to get all 3 parameters. To use copy to the guest rename to system.sh and make executable with chmod. Here is the output from the script showing the specified IDs. I think if we can manually patch the VM Ethernet IDs network values to spoof a Mac's 'Ethernet' device to apple, such as ZackehSoul method: Along with this vmx patching by Donk we can achieve iMessage use in VMware while still preserving the stock VMware EFI and no longer breaking any of the machines features and stability. EDIT: If anyone has any knowledge of kext writing, there could be some sort of Ethernet 'injector' written that resolves the Ethernet information to apple permitted hardware.
![Kumpulan serial number idm Kumpulan serial number idm](/uploads/1/2/5/3/125349907/507644266.jpg)
Actually it looks like the Platform-UUID not mac addresses. I have tested a ML guest on Fusion 6 on a real Macbook Pro and it doesn't work there either, and also people with same problem on VMware forums. I think we need to find a way to update the UUID in NVRAM.
I know the VMX file has 2 lines that set the UUID, they are: uuid.bios and uuid.location. They are both hex values and there is an algorithm VMware uses to generate the machine UUID from these. They both seem to contribute to how the UUID of the machine is derived, I know when you move a machine it asks whether you want it to keep the same UUID or generate a new one. We might be able to play with these lines and see if this changes the UUID in NVRAM, I will check when I get home, but you are talking about the UUID in system profiler right?
I think if you set uuid.location = ' (it might use the actual machines UUID), would you be able to verify this on your Mac Book Pro? EDIT: Maybe this can be fixed with a patch to the PlatformUUID.kext, to inject the correct UUID from the machine. Anyone have any knowledge with Kexts in order to write this?
There used to be some for snow leopard but I doubt they inject the values in mountain lion, I think superhai wrote those. So added SMBIOS.use12CharSerialNumber = 'TRUE' Removed line serialNumber = 'RM129481AGW' I see it generated a serial number. Tried iMessage but still not signing in Now what? Yes, you' re right. I thought it would work because the results of osx-system.sh within the Guest were the same as on my Real Mac but I hadn' t verified iMessage. I used the identification of my Real MBP (along with the Serial Number, the hardware type, etc.) and it' s still not signing in.
(although it seems to take longer to verify that information). Kind regards. Only just had time to do this, but clean Mavericks install on Fusion 6 Pro, on a real Macbook Pro allows iMessage to work. So now need to take that VM to a Workstation machine and see if I can find what is different. Will probably use DarwinDumper to get a complete snapshot of all hardware information, and compare between the 2 platforms.
Hi Donk, where you able to verify the same machine on Workstation? I wonder if it is something to do with the vmware injected hardware values from the local machine. Is there any way to use this to basically trick a program that wont run in an OSX virtual machine to actually run in it. Basically i have this software that somehow detects that im running osx in vmware. From the log i have it seems to check the ROMBootVersion, SCM version and the rombootversion shows up as VMF.xxxxx which is the VMware software version.
I also have not installed the parallels tools yet so i know its not seeing that. I think it is checking the hardware profile and since it doesnt know the processor type, memory, ect it fails. Is there any way i can monitor the startup of the app to see what it called for in the system for checks. Is there a way i can spoof my entire real rMBP Thanks! Only just had time to do this, but clean Mavericks install on Fusion 6 Pro, on a real Macbook Pro allows iMessage to work. So now need to take that VM to a Workstation machine and see if I can find what is different.
Will probably use DarwinDumper to get a complete snapshot of all hardware information, and compare between the 2 platforms. Donk, could you please specify on which condition (virtual hw ver, vmx option,) I am currently running on Mac with Fusion but I was unable to get iMessage working Thnx. This is the current version of VMware Tools for OS X / macOS from the VMware CDS repository for Fusion 11.0.2 Please note: In the latest VMwareGfx.kext from Fusion 8.5.5 onwards VMware have discontinued the 2D-Acceleration code, and graphics performance is better now, thanks to Zenith432 for the update. To check for the latest version visit The various VMware Tools downloads are located under the packages folder for each version. Instructions for extracting darwin.iso - Download the file above - Extract com.vmware.fusion.tools.darwin.zip.tar - darwin.iso is located in the 'payload' folder com.vmware.fusion.tools.darwinPre15.zip.tar com.vmware.fusion.tools.darwin.zip.tar. Here is a new utility to patch the EFI firmware in VMware Workstation and Fusion to allow the non-server versions of Mac OS X 10.5 (Leopard) and 10.6 (Snow Leopard) to run. Yoiu will need macOS unlocker 3 if you are using Workstation on non-Apple hardware.
I still have to find a way to do this on ESXi as the UEFIPatch utility will not run in the ESXi console. This currently supports: Workstation 11/12/14/15 on Windows and Linux Workstation Player 7/12/14/15 on Windows and Linux Fusion 10/11 on macOS Please read the readme.txt file for details. Readme.txt.
MacOS Unlocker V3.0 for VMware Workstation +-+ IMPORTANT: Always uninstall the previous version of the Unlocker before using a new version. Failure to do this could render VMware unusable.
+-+ 1. Introduction - Unlocker 3 is designed for VMware Workstation 11-15 and Player 7-15. If you are using an earlier product please continue using Unlocker 1. Version 3 has been tested against:. Workstation 11/12/14/15 on Windows and Linux. Workstation Player 7/12/14/15 on Windows and Linux The patch code carries out the following modifications dependent on the product being patched:.
Fix vmware-vmx and derivatives to allow macOS to boot. Fix vmwarebase.dll or.so to allow Apple to be selected during VM creation. Download a copy of the latest VMware Tools for macOS Note that not all products recognise the darwin.iso via install tools menu item. You will have to manually mount the darwin.iso for example on Workstation 11 and Player 7. In all cases make sure VMware is not running, and any background guests have been shutdown. The code is written in Python.
Prerequisites - The code requires Python 2.7 to work. Most Linux distros ship with a compatible Python interpreter and should work without requiring any additional software.
Windows Unlocker has a packaged version of the Python script using PyInstaller, and so does not require Python to be installed. Limitations - If you are using VMware Player or Workstation on Windows you may get a core dump.
Latest Linux products are OK and do not show this problem. +-+ IMPORTANT: If you create a new VM VMware may stop and create a core dump. There are two options to work around this issue: 1.
Change the VM to be HW 10 - this does not affect performance. 2.
Edit the VMX file and add: smc.version = '0' +-+ 4. Windows - On Windows you will need to either run cmd.exe as Administrator or using Explorer right click on the command file and select 'Run as administrator'. Win-install.cmd - patches VMware win-uninstall.cmd - restores VMware win-update-tools.cmd - retrieves latest macOS guest tools 5. Linux - On Linux you will need to be either root or use sudo to run the scripts.
You may need to ensure the Linux scripts have execute permissions by running chmod +x against the 2 files. Lnx-install.sh - patches VMware lnx-uninstall.sh - restores VMware lnx-update-tools.cmd - retrieves latest macOS guest tools 6. Thanks - Thanks to Zenith432 for originally building the C unlocker and Mac Son of Knife (MSoK) for all the testing and support. Thanks also to Sam B for finding the solution for ESXi 6 and helping me with debugging expertise. Sam also wrote the code for patching ESXi ELF files and modified the unlocker code to run on Python 3 in the ESXi 6.5 environment.
History - 27/09/18 3.0.0 - First release 02/10/18 3.0.1 - Fixed gettools.py to work with Python 3 and correctly download darwinPre15.iso 10/10/18 3.0.2 - Fixed false positives from anti-virus software with Windows executables - Allow Python 2 and 3 to run the Python code from Bash scripts (c) 2011-2018 Dave Parsons. MacOS Unlocker V3.0 for VMware ESXi 1.
Introduction - Unlocker 3 for ESXi is designed for VMware ESXi 6.5 and 6.7. The patch code carries out the following modifications dependent on the product being patched:. Fix vmware-vmx to allow macOS to boot. Fix libvmkctl to allow vSphere to control the guest The code is written in Python as it makes the Unlocker easier to run and maintain on ESXi. +-+ IMPORTANT: Always uninstall the previous version of the Unlocker before using a new version. Failure to do this could render VMware unusable. +-+ 2.
Installation - Copy the distribution file to the ESXi host datastore using scp or some other data transfer system. Decompress the file from the ESXi console or via SSH: tar xzvf esxi-unlocker-xxx.tgz (xxx - will be the version number, for example, 300) Run the command from the terminal:./esxi-install.sh Finally reboot the server. Uninstallation - Open the ESXi console or login via SSH and chnage to the folder where the files were extracted.
Run the command from the terminal:./esxi-uninstall.sh Finally reboot the server. Notes - A. There is a command added called esxi-smctest.sh which can show if the patch is successful. It must be run from a terminal or SSH session. The output should be: /bin/vmx smcPresent = true custom.vgz false 38725560 B B. The unlocker can be temporarily disabled during boot by editing the boot options and adding 'nounlocker'. Thanks - Thanks to Zenith432 for originally building the C unlocker and Mac Son of Knife (MSoK) for all the testing and support.
Thanks also to Sam B for finding the solution for ESXi 6 and helping me with debugging expertise. Sam also wrote the code for patching ESXi ELF files and modified the unlocker code to run on Python 3 in the ESXi 6.5 environment. The code is available at History - 26/09/18 3.0.0 - First release (c) 2011-2018 Dave Parsons. How to spoof real Mac in VMware.
If you have problems with iCloud and iMessage and but nothing has changed maybe the problem can be your current serial number. In fact to enable iCloud and iMessage a Mac Real or Hackintosh needs to connect to the official Apple servers which will obviously check what type of computer it is and that is done using the unique serial number. If the serial is valid all services will be enabled, if not the access will be denied and that’s were all problems starts. If you installed OS X using MultiBeast your Hackintosh already have a serial number since it will generate one for you during the installation of the Chimera bootloader using an algorithm, and at 70% it will be correctly recognized by Apple servers but those serial numbers are fake and not completely “safe”, in fact if you try to check warranty on using one of those serials it will 100% end like this: So, how can we solve this issue and find a real serial number? There are a few ways you can try but the first thing I suggest you is the easiest, easy as a Google search, do you think I am crazy? How can you find a real Mac serial on Google?
Well it turns out there are a tons of website and single users who have posted they’re Mac serial number online and you can find them using Google Image Search like in case: You can easily read the serial which is: C02JT1EGDNMP and since its a real serial number Apple will recognize it too off course as you can see here: cool, uh? All you need to do is search for your model number, for example “iMac 14,2” or “iMac Late 2012”, and look for serial numbers in the pictures.
Another thing you can try is to go to an Apple Store, an Apple Premium Reseller or any other places where they sell Macs, use a Mac which can be used freely by customers and go to the “About this Mac” menu and copy his serial. The last thing you can try is to generate it by yourself using Chameleon Wizard by going to the SMBIOS tab and generate it there. You can find Chameleon Wizard latest version. Just select the correct device model according to your hardware and click on “Random”, remember to check the serial on the and keep generating until you find the working one. You can’t use a serial number of a different model even if it’s recognized by Apple, for example an iMac serial number on a Mac Pro Hackintosh, it won’t work. If this post was useful to you feel free to ?! Thank you really much.
![Virtualbox mac os x Virtualbox mac os x](http://reference.albertlua.com/wp-content/uploads/2016/04/cmdsearch.png)
I don’t mean to state the obvious but doesn’t this stray into the “definitely illegal” territory? I don’t mind using a hackintosh but if stealing somebody’s legitimate serial number compromises their access to entitled support, I’d feel like an asshole.
The worst thing I’d imagine could be that they (the legal owner) get an email saying “Your device was just registered ” and then they could somehow gain access to the machine or information about its location. No idea if that’s possible but it definitely sounds plausible.