how to login apple id?

[tiyo]

success to run sequoia, but can't log in to apple id

[DrDonk]

Changed to a discussion as this is not a bug.

This is issue with most virtualised macOS guests. So transferred to discussions so someone can help out? I personably do not need this but there are answers on the web.

[DrDonk]

With the new 1.0.1 release there are 2 things you can try in the VM. You will need to open terminal to run the commands. Also will need to reboot the guest for the settings to change. See https://github.com/DrDonk/OC4VM/blob/main/tools.md

1. /Volumes/OPENCORE/tools/regen
2. /Volumes/OPENCORE/tools/vmhide on

I do not know if this will do what you want but it is worth a go.

[davewuk]

I did start another thread about this but for some reason it isn't showing. The regen script doesn't work either, it throws the following error message:

./regen:14: no such file or directory: /Volumes/OPENCORE/tools/macserial
OC4VM regen
-----------
Regenerating Mac identifiers...
Serial:  
MLB:     
ROM:     A143AA7F1FED
UUID:    EAC1BC88-4564-483C-A23F-5143E25B80E7

After running the script the VM's serial is blank.

[DrDonk]

My mistake I forgot to add th copy to the OC4V M disk image in the make script. I will fix it 1.0.3.

[davewuk]

My mistake I forgot to add th copy to the OC4V M disk image in the make script. I will fix it 1.0.3.

Thanks, I'll close the other discussion thread.

[DrDonk]

1.0.3 released

[davewuk]

The regen script seems to be working as intended now, I was able to generate a new set of identifiers for my VM. Many thanks!

[mikeyo]

This should help - https://youtu.be/gp0Vi5OJO-k?si=a795sAv6orVNDRRn

[DrDonk]

Ah OK so of course it's probably the spoofed values. Use the regen tool I have supplied on the OC disk.

/Volumes/OPENCORE/tools/regen

It will regenerate the serial, uuid, mlb and rom values. OC4VM spoofs a Macmini8,1 for best compatibility with macOS and VMs.

[DrDonk]

I've been doing this work since 2007 as Donk on InsanelyMac and DrDonk here, and sometimes these things slip my now 60+ memory!!

[tiyo]

https://youtu.be/gp0Vi5OJO-k?si=a795sAv6orVNDRRn

All IDs can log in normally, except for iMessage which automatically logs out. All machine codes pass the verification.

[DrDonk]

Sorry don't know where to go with this. Hopefully someone else has the answers.

[cosmokramerII]

I've observed that macOS Sonoma runs fully functional in VMware, including successful Apple ID login. However, once the system is upgraded to Sequoia, the login process begins to fail gradually—regardless of whether the VM's identifiers are properly spoofed. Eventually, Apple ID login fails entirely, showing an "unknown error."
Upon analyzing the OS's code, it appears Sequoia introduces a new verification mechanism. The OS attempts to access the host’s Secure Enclave to generate a unique identifier for Apple services. Since this cannot succeed in a virtual environment, the system treats the VM as untrusted, resulting in the Apple ID being blocked.
This suggests that Sequoia includes a new EFI- or bootloader-level integrity check or patch detection system.
To get around this, we probably need a low-level patch or some kind of emulation that either fakes a valid Secure Enclave response or skips the check altogether—just enough to make Apple ID work again inside a VM.

[DrDonk]

Thanks for that information. That would make sense and even more so for Tahoe as all the supported Intel Macs have a T2 chip.

[robross0606]

Confused by this thread. The latest release 1.1.1 doesn't seem to have a regen script at all. How is this done now?

[robross0606]

I tried using the latest regen script that's available in this repo which just seems to echo information out to the screen. I intuited that I should:

1. Launch the VM.
2. Run this tool inside the VM.
3. Copy the information echo'ed to the screen and save it someplace outside the VM.
4. Cleanly shut down the VM and VMWare.
5. Edit the macos.vmx file.
6. Paste the copied content in to the VMX file and save.
7. Restart VMWare and the VM.

This didn't cause any errors during the process, but I still get the same "Verification failure" as indicated above. The regen script doesn't appear to solve anything.

[BDisp]

I successfully bypassed the login a long time ago using a command mentioned in this discussion on a Sequoia installation in VMware. Now, with Tahoe, I can't log into the settings at all. Is it really not possible anymore?

[lhwynew]

Hello, can you please tell me how did you do to fix the Apple id login issue? I have been working on this problem for a week. It's really driving me crazy!

[BDisp]

Hello, can you please tell me how did you do to fix the Apple id login issue? I have been working on this problem for a week. It's really driving me crazy!

I didn't try yet with the new version, but probably I'll have the same problem. Probably they detect it's from VMware and block. I give up about login because I don't really need it.

[lhwynew]

Hello, can you please tell me how did you do to fix the Apple id login issue? I have been working on this problem for a week. It's really driving me crazy!

I didn't try yet with the new version, but probably I'll have the same problem. Probably they detect it's from VMware and block. I give up about login because I don't really need it.

Thank you for your reply, I haven't try Tahoe either, right now I am working on Sequoia 15.6. I have already installed Sequoia in VMware, and changed the SMBios by OpenCore Configurator, but still can't login apple id! Could you please help me?

[BDisp]

Thank you for your reply, I haven't try Tahoe either, right now I am working on Sequoia 15.6. I have already installed Sequoia in VMware, and changed the SMBios by OpenCore Configurator, but still can't login apple id! Could you please help me?

Sorry, I thought you were referring to Tahoe. With Sequoia, I managed to log in to my Apple ID a long time ago by running an existing Opencore.iso tool, but it seems it no longer exists. Try looking for it in version 1.0.3. Given this comment, it might not be possible even if that tool were running. I remember that after running that tool I had to restart the VM to apply the new configuration. You can try with tools from previous versions or wait for a solution that might result from the comment I mentioned above.

[DrDonk]

Please read this post and wiki page.

I see other patches being used but they do exactly the same things as changing the settings in the VMX file. I've workied on unlockers for nearly 20 years and the spoofing for about 15 so have quite a bit of background to this.

Just so you can see this is the case I captured the settings inside a VM.

hypervisor.cpuid.v0 = "TRUE"

hypervisor.cpuid.v0 = "FALSE"

As well as possibly now needing the SEP in the T2 chip, I also understand that Bluetooth may be needed. Not sure about that but it has been mentioned.

[user76-real]

AppleID Fix.txt

[DrDonk]

When you do what I described in “AppleID Fix.txt,” kern.hv_vmm_present becomes 0 without any problems, and I personally haven't encountered any issues.

I have had it fail with a kernel panic and not even get get xnu started. Same issue with VMHide.kext. I did a lot of testing on this and also in the unlocker days. I am happy it works for you and I"m trying to find a reliable solution for the issue. There is something going on inside xnu and certain CPUs that throws errors, and I have not pinned down the cause of it. Also I want option of having VMM present as my needs require it as I want the guest to present as a VM.

[user76-real]

When you do what I described in “AppleID Fix.txt,” kern.hv_vmm_present becomes 0 without any problems, and I personally haven't encountered any issues.

I have had it fail with a kernel panic and not even get get xnu started. Same issue with VMHide.kext. I did a lot of testing on this and also in the unlocker days. I am happy it works for you and I"m trying to find a reliable solution for the issue. There is something going on inside xnu and certain CPUs that throws errors, and I have not pinned down the cause of it. Also I want option of having VMM present as my needs require it as I want the guest to present as a VM.

config.plist
macos.vmx

[DrDonk]

OK added them to 2.0.2.

[bellum07]

When you do what I described in “AppleID Fix.txt,” kern.hv_vmm_present becomes 0 without any problems, and I personally haven't encountered any issues.

This seems pretty much the same what I've posted in #58 (comment) some days ago ...

And it works well with Sequoia 15.7.3 and Tahoe 26.0.1 without any kernel panics and successful Apple ID logins but I've noticed with 26.0.1 that Tahoe doesn't recognize the update to 26.2.

I've managed to workaround this by disabling the patch, update to 26.2 and reenable it still without any kernel panics ...

[BDisp]

With OC4VM version 2.0.2, after forcing a shutdown twice, on the third attempt I managed to start the VM and actually logged in to my Apple ID on Tahoe 26.2. Thank you @DrDonk and everyone who contributed to its resolution.