iMessage issue. iCloud works

[albanyeye]

Hello I have successfully installed Catalina using your script. Thankyou. However iMessage seems to continue to give me problems. I took the serial number details from my 2015 iMac and placed them in the script.

DmiSystemUuid matches the Hardware UUID from the command system_profiler SPHardwareDataType, and the value of SYSTEM_UUID mathces value of system-id

system_profiler SPHardwareDataType ioreg -l | grep -m 1 board-id nvram 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:MLB nvram 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:ROM ioreg -l -p IODeviceTree | grep \"system-id

I get get only some of the output to match the output from the original mac, Sepcifically, the nvram 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:ROM command output is a bunch of 01 running several lines. Aslo, ioreg -l -p IODeviceTree | grep \"system-id command simply returns nothing.

Any suggestions?

[myspaghetti]

nvram 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:ROM command output is a bunch of 01 running several lines

ioreg -l -p IODeviceTree | grep "system-id command simply returns nothing.`

The script's NVRAM values are written to the virtual machine only when VirtualBox boots into the EFI Internal Shell and runs startup.nsh. To boot into the EFI interactive shell, power on the virtual machine from a completely halted state, press Esc as soon as the VirtualBox logo appears. This boots into the EFI Internal Shell or the boot menu. If the boot menu appears, select "Boot Manager" and then "EFI Internal Shell" and then allow the startup.nsh script to execute automatically, applying the NVRAM variables before booting macOS.

Since iMessage was already started before, starting it again will likely cause a "Call customer support" message. This can be fixed either by cleaning macOS of the previously detected values, or by making a clean install of macOS, which would probably take less time than cleaning the old values if you still have the installation media ready.

[albanyeye]

Thanks Jack. So placing the DmiSystemUuid and the SYSTEM_UUID values in the script before inital install is not sufficient? Do I still need to boot into EFI Internal shell and let startup.nsh execute?

I had initially placed the DmiSystemUuid and the SYSTEM_UUID in the startup script and ran it.

[albanyeye]

[removed image for privacy reasons - myspaghetti]

[albanyeye]

Holy cow… it worked. Thanks!!!!! This is cool I booted into EFI [removed for privacy reasons - myspaghetti]

[albanyeye]

Now I need to see about upgrading to Big Sur

thanks again