Ventura docs for M2 Macs in this comment: https://gist.github.com/henrik242/65d26a7deca30bdb9828e183809690bd?permalink_comment_id=4555340#gistcomment-4555340
Old Monterey docs in this old revision: https://gist.github.com/henrik242/65d26a7deca30bdb9828e183809690bd/32c410e3a1de73539c76fa13ea5486569c4e0c5d
Solution for Sonoma: https://gist.github.com/sghiassy/a3927405cf4ffe81242f4ecb01c382ac
Not sure if it helps but I found this website which might do it for you: https://skipmdm.com
You can verify the contents with curl https://raw.githubusercontent.com/skipmdm-phoenixbot/skipmdm.com/main/Autobypass-mdm.sh | cat
To save everyone time, the script provided on skipmdm is just what was discussed here previously put together in a nice script.
The current version linked is safe, but as it goes always check before you run something you got off the internet as the script can always be changed.
For anyone curious, here is the direct link to the script:
AutoBypass-mdm.sh
I need an agent to help me sell my bypass service, use my technology or we can study new technologies together. At present, my research result is that I can bypass the MDM without didn't disabling SIP. The command line I need to use is only 20 characters, which contains multiple options, such as cleaning up WiFi information, waking up MDM, bypassing MDM, cleaning up MDM agent, creating users，and more。My authorization method is to bind the serial number, and a machine can be used for life. The price is $14. Friends in need can ask friends in China to pay me. My personal homepage has my email address.
I have been writing this program for a year. At first it was a script, but someone stole my script to make money, and later it was changed to an encrypted program. At the beginning, I collected MDM Agent information and deleted plist file and agent App together.Later, this situation was less, so we just need to bypass and disable MDM.
At first, I used some simple command lines to bypass the MDM，But some people can't access google and github, so I provide $1 technical service.(Video guidance)
What I do is not simple copying and pasting, because ordinary users can't use the command line, and it's easy to input case errors and even spaces. I don't have this much energy.I arranged all the necessary steps into options for users to choose, and even provided videos, notes and communication groups.
Later, I found all kinds of MDM-Agent, I knew that I needed to constantly optimize them, so the price rose to $7.
Later, some seniors criticized me and my peers slandered me. I once thought about giving up.But I still have dozens of customers, and I can't leave them alone, and these users pay enough money for me to buy some fruit. Even without me, there will be another one. The main reason why I spend so much time studying is that these are too expensive. (check8 or other)
My main client is from China, so most of the documents are in Chinese. Please forgive me, you can use Google Translation.
** I'm here now because I think the brother above has the same experience as me, and I'm afraid he will replace me. @skipmdm-phoenixbot. His growth may pose an indirect threat to me **
video: https://b23.tv/shTJigT
options:
Is there anyone who has tried installing MacOS Sonoma on bypassed MB M1?
Since only 2 days are left for Sonama's final release. This is my question, will we have any problems after upgrading to Sonoma? I now work easily on ventura without bypass. Will I have the same experience with the upgrade? Or it is an issue that should be considered
Thank you all
I am running Sonoma, just upgrade manually and make sure to have blocked in the hosts file and in the router's settings the domains listed in this thread. After upgrading, check your hosts file and make sure that the services are still disabled. Additionally, you could block access to the internet of the services using a firewall like Little Snitch to make sure that even if Apple has added an additional domain or whatever type of check, all the traffic to and from the services is blocked.
Has anyone used the site skipmdm.com? it helps to bypass the blocking and everything works well, but are there any risks associated with this?
Has anyone used the site skipmdm.com? it helps to bypass the blocking and everything works well, but are there any risks associated with this?
You can always see exactly what their script is doing here: https://raw.githubusercontent.com/skipmdm-phoenixbot/skipmdm.com/main/Autobypass-mdm.sh
Not to mention their script is housed here: https://github.com/skipmdm-phoenixbot/skipmdm.com
See for yourself....
Has anyone used the site skipmdm.com? it helps to bypass the blocking and everything works well, but are there any risks associated with this?
You can always see exactly what their script is doing here: https://raw.githubusercontent.com/skipmdm-phoenixbot/skipmdm.com/main/Autobypass-mdm.sh
Not to mention their script is housed here: https://github.com/skipmdm-phoenixbot/skipmdm.com
See for yourself....
I’m not the programmer to be honest. And I don’t understand what does it mean :( I just want to use my MacBook and not to lose my files and data…
If you can explain - I would be very grateful!
Has anyone used the site skipmdm.com? it helps to bypass the blocking and everything works well, but are there any risks associated with this?
You can always see exactly what their script is doing here: https://raw.githubusercontent.com/skipmdm-phoenixbot/skipmdm.com/main/Autobypass-mdm.sh
Not to mention their script is housed here: https://github.com/skipmdm-phoenixbot/skipmdm.com
See for yourself....I’m not the programmer to be honest. And I don’t understand what does it mean :( I just want to use my MacBook and not to lose my files and data… If you can explain - I would be very grateful!
this script essentially runs all the command that have been recommended in this long thread. It appears that it would work. I would do this on a clean reinstall. Following their instructions should result in success, and nothing nefarious being installed or done to your machine.
Has anyone used the site skipmdm.com? it helps to bypass the blocking and everything works well, but are there any risks associated with this?
You can always see exactly what their script is doing here: https://raw.githubusercontent.com/skipmdm-phoenixbot/skipmdm.com/main/Autobypass-mdm.sh
Not to mention their script is housed here: https://github.com/skipmdm-phoenixbot/skipmdm.com
See for yourself....I’m not the programmer to be honest. And I don’t understand what does it mean :( I just want to use my MacBook and not to lose my files and data… If you can explain - I would be very grateful!
this script essentially runs all the command that have been recommended in this long thread. It appears that it would work. I would do this on a clean reinstall. Following their instructions should result in success, and nothing nefarious being installed or done to your machine.
Thank you so much, hope all will be great! Have a nice day :)
Sonoma is here. Let's keep experiences/observations coming.
**** WORKING!!! ******. HI EVERYONE! I have a simplified way I figured out today to bypass DEP today with Ventura against a M2 Macbook Air
Need 3 things
- A separate M1/M2 Mac (could be anytjhing, macbook, studio, etc). this machine must not have DEP/Business Manager enabled
- Create a USB Boot installer flash drive with Ventura - you can google the instructions on how to create a boot usb drive.
- An external SSD that you can install a fresh OS on. I just use a sandish extreme USB 3.1 256GB drive.
Steps I did On the non-DEP M1/M2 Mac
- USB BOOT installer and install Ventura on the External SSD --- using the non-DEP Mac
- Once installed, go thru the account creation so you have an account
- Boot from USB SSD drive just to make sure it is working.
Now you have a bootable external disk.
On the DEP enabled M1/M2 Mac
- Boot to recovery mode
- Disk Utility
- Erase the internal physical disk
- Click on internal disk and use the RESTORE option, FROM the external SSD
- Let it run - will take a while.
Now you jsut copied the clean ventura to the internal drive.
Once the restore is finished. Remove the External SSD Boot from the internal disk
You WILL get an error that it cannot find the OS or some other stupid errors like no owner, or some other silly error... don't worry.
Now you boot again using the USB BOOT Ventura disk. REINSTALL Ventura again on the internal disk - DO NOT DO ANY DISK FORMATTING this time.
Once USB Installer is done, reboot - you will get to the login prompt of the user you created on the initial fresh install. you will have a working Ventura M1/M2 that just bypassed DEP/Business Manager.
Why this works? Because you first lay down the image on internal disk but due to some apple security, it will never boot unless you "fresh install" it. But the good things about fresh installs, Apple doesn't really wipe the system, it just lays whatever that is necessary for the OS. This means it will fix the ownership of the disks, do whatever it does but won't overwrite local accounts etc. so you will not get prompted for DEP enrollment. I don't know the actual internal details but I just know this works.
Enjoy. took me a while to figure this out after trying many things.
I do not need to do any /etc/hosts hacks, csrutil, etc. nothing. It's pretty simple to do but it does require a double install but it's easier than editing files.
You could in theory transfer a fully working Mac to another Mac now but I don't need to do that so I did the clean Ventura Install.
Now I can use this method to clean/wipe any DEP enabled machine and have myself a "pre-built" machine with certain things like chrome etc already installed. I can just boot from the external SSD periodically to get new updates of OS and software and continue to use it on any new Macs I wipe.Does anyone know if I've used this method to enroll in MDM? Can I update without issues to macOS Sonoma?
Unfortunately, no. After the update, a fullscreen Device Enrollment popup started appearing. Does anyone know of a solution?
**** WORKING!!! ******. HI EVERYONE! I have a simplified way I figured out today to bypass DEP today with Ventura against a M2 Macbook Air
Need 3 things
- A separate M1/M2 Mac (could be anytjhing, macbook, studio, etc). this machine must not have DEP/Business Manager enabled
- Create a USB Boot installer flash drive with Ventura - you can google the instructions on how to create a boot usb drive.
- An external SSD that you can install a fresh OS on. I just use a sandish extreme USB 3.1 256GB drive.
Steps I did On the non-DEP M1/M2 Mac
- USB BOOT installer and install Ventura on the External SSD --- using the non-DEP Mac
- Once installed, go thru the account creation so you have an account
- Boot from USB SSD drive just to make sure it is working.
Now you have a bootable external disk.
On the DEP enabled M1/M2 Mac
- Boot to recovery mode
- Disk Utility
- Erase the internal physical disk
- Click on internal disk and use the RESTORE option, FROM the external SSD
- Let it run - will take a while.
Now you jsut copied the clean ventura to the internal drive.
Once the restore is finished. Remove the External SSD Boot from the internal disk
You WILL get an error that it cannot find the OS or some other stupid errors like no owner, or some other silly error... don't worry.
Now you boot again using the USB BOOT Ventura disk. REINSTALL Ventura again on the internal disk - DO NOT DO ANY DISK FORMATTING this time.
Once USB Installer is done, reboot - you will get to the login prompt of the user you created on the initial fresh install. you will have a working Ventura M1/M2 that just bypassed DEP/Business Manager.
Why this works? Because you first lay down the image on internal disk but due to some apple security, it will never boot unless you "fresh install" it. But the good things about fresh installs, Apple doesn't really wipe the system, it just lays whatever that is necessary for the OS. This means it will fix the ownership of the disks, do whatever it does but won't overwrite local accounts etc. so you will not get prompted for DEP enrollment. I don't know the actual internal details but I just know this works.
Enjoy. took me a while to figure this out after trying many things.
I do not need to do any /etc/hosts hacks, csrutil, etc. nothing. It's pretty simple to do but it does require a double install but it's easier than editing files.
You could in theory transfer a fully working Mac to another Mac now but I don't need to do that so I did the clean Ventura Install.
Now I can use this method to clean/wipe any DEP enabled machine and have myself a "pre-built" machine with certain things like chrome etc already installed. I can just boot from the external SSD periodically to get new updates of OS and software and continue to use it on any new Macs I wipe.Does anyone know if I've used this method to enroll in MDM? Can I update without issues to macOS Sonoma?
Unfortunately, no. After the update, a fullscreen Device Enrollment popup started appearing. Does anyone know of a solution?
Someone mentioned that after downloading the update and reboot, you should unplug the router to disconnect from the network .During the restart after the installed, your mac may communicate with the MDM server. Considering that your SN exists on the MDM server, if there is successful communication, a pop-up might appear.
is there any other way to run "sudo rm /var/db/ConfigurationProfiles/Settings/.cloudConfigHasActivationRecord sudo rm /var/db/ConfigurationProfiles/Settings/.cloudConfigRecordFound sudo touch " without closing SIP? every time I turn on sip, these two files will reappear again.
Try this in Recovery
rm -rf /Volumes/Macintosh\ HD/var/db/ConfigurationProfiles/Settings/.cloudConfigHasActivationRecord
rm -rf /Volumes/Macintosh\ HD/var/db/ConfigurationProfiles/Settings/.cloudConfigRecordFound
touch /Volumes/Macintosh\ HD/var/db/ConfigurationProfiles/Settings/.cloudConfigProfileInstalled
touch /Volumes/Macintosh\ HD/var/db/ConfigurationProfiles/Settings/.cloudConfigRecordNotFound
Not sure if these can be used with SIP enabled
Try this in Recovery rm -rf /Volumes/Macintosh\ HD/var/db/ConfigurationProfiles/Settings/.cloudConfigHasActivationRecord rm -rf /Volumes/Macintosh\ HD/var/db/ConfigurationProfiles/Settings/.cloudConfigRecordFound touch /Volumes/Macintosh\ HD/var/db/ConfigurationProfiles/Settings/.cloudConfigProfileInstalled touch /Volumes/Macintosh\ HD/var/db/ConfigurationProfiles/Settings/.cloudConfigRecordNotFound
Not sure if these can be used with SIP enabled
It doesn't work, at first I tried to use these scripts in recovery but I couldn't do it. The code has to be in a terminal on macos to work
successful upgrade to Sonoma, here are some experiences that I learn from these process. I hope it was helpful.
There are two main steps to do.
step 1: shield the host
1.open terminal and enable the root user and give it password.
2.enter the command below and press enter
"
sudo -i
echo "0.0.0.0 iprofiles.apple.com" >> /etc/hosts
echo "0.0.0.0 mdmenrollment.apple.com" >> /etc/hosts
echo "0.0.0.0 deviceenrollment.apple.com" >> /etc/hosts
echo "0.0.0.0 gdmf.apple.com" >> /etc/hosts
echo "0.0.0.0 acmdm.apple.com" >> /etc/hosts
echo "0.0.0.0 albert.apple.com" >> /etc/hosts
"
3.now you have successfully shield the host. if you do not wan to upgrade to Sonoma, then enjoy your macOS without annoying notifications. and if you want Sonoma, please follow the second step.
step 2: delete two files and built two files
1.shut down your Mac and enter Recovery.
2.in terminal on Recovery, enter "csrutil disable" to disable SIP.
3.reboot your Mac. in terminal on macOS.enter the command below and press enter.
"
sudo rm /var/db/ConfigurationProfiles/Settings/.cloudConfigHasActivationRecord
sudo rm /var/db/ConfigurationProfiles/Settings/.cloudConfigRecordFound
sudo touch /var/db/ConfigurationProfiles/Settings/.cloudConfigProfileInstalled
sudo touch /var/db/ConfigurationProfiles/Settings/.cloudConfigRecordNotFound
sudo launchctl disable system/com.apple.ManagedClient.enroll
"
finish! now you can enjoy the boring Sonoma.
successful upgrade to Sonoma, here are some experiences that I learn from these process. I hope it was helpful.
There are two main steps to do.
step 1: shield the host
1.open terminal and enable the root user and give it password.
2.enter the command below and press enter " sudo -i echo "0.0.0.0 iprofiles.apple.com" >> /etc/hosts echo "0.0.0.0 mdmenrollment.apple.com" >> /etc/hosts echo "0.0.0.0 deviceenrollment.apple.com" >> /etc/hosts echo "0.0.0.0 gdmf.apple.com" >> /etc/hosts echo "0.0.0.0 acmdm.apple.com" >> /etc/hosts echo "0.0.0.0 albert.apple.com" >> /etc/hosts " 3.now you have successfully shield the host. if you do not wan to upgrade to Sonoma, then enjoy your macOS without annoying notifications. and if you want Sonoma, please follow the second step.
step 2: delete two files and built two files
1.shut down your Mac and enter Recovery.
2.in terminal on Recovery, enter "csrutil disable" to disable SIP.
3.reboot your Mac. in terminal on macOS.enter the command below and press enter. " sudo rm /var/db/ConfigurationProfiles/Settings/.cloudConfigHasActivationRecord sudo rm /var/db/ConfigurationProfiles/Settings/.cloudConfigRecordFound sudo touch /var/db/ConfigurationProfiles/Settings/.cloudConfigProfileInstalled sudo touch /var/db/ConfigurationProfiles/Settings/.cloudConfigRecordNotFound sudo launchctl disable system/com.apple.ManagedClient.enroll "
finish! now you can enjoy the boring Sonoma.
Should the step 2 be done before update to Sanoma or after? Thanks.
successful upgrade to Sonoma, here are some experiences that I learn from these process. I hope it was helpful.
There are two main steps to do.
step 1: shield the host
1.open terminal and enable the root user and give it password.
2.enter the command below and press enter " sudo -i echo "0.0.0.0 iprofiles.apple.com" >> /etc/hosts echo "0.0.0.0 mdmenrollment.apple.com" >> /etc/hosts echo "0.0.0.0 deviceenrollment.apple.com" >> /etc/hosts echo "0.0.0.0 gdmf.apple.com" >> /etc/hosts echo "0.0.0.0 acmdm.apple.com" >> /etc/hosts echo "0.0.0.0 albert.apple.com" >> /etc/hosts " 3.now you have successfully shield the host. if you do not wan to upgrade to Sonoma, then enjoy your macOS without annoying notifications. and if you want Sonoma, please follow the second step.
step 2: delete two files and built two files
1.shut down your Mac and enter Recovery.
2.in terminal on Recovery, enter "csrutil disable" to disable SIP.
3.reboot your Mac. in terminal on macOS.enter the command below and press enter. " sudo rm /var/db/ConfigurationProfiles/Settings/.cloudConfigHasActivationRecord sudo rm /var/db/ConfigurationProfiles/Settings/.cloudConfigRecordFound sudo touch /var/db/ConfigurationProfiles/Settings/.cloudConfigProfileInstalled sudo touch /var/db/ConfigurationProfiles/Settings/.cloudConfigRecordNotFound sudo launchctl disable system/com.apple.ManagedClient.enroll "
finish! now you can enjoy the boring Sonoma.Should the step 2 be done before update to Sanoma or after? Thanks.
all of these two steps should be done if you want Sonoma
successful upgrade to Sonoma, here are some experiences that I learn from these process. I hope it was helpful.
There are two main steps to do.
step 1: shield the host
1.open terminal and enable the root user and give it password.
2.enter the command below and press enter " sudo -i echo "0.0.0.0 iprofiles.apple.com" >> /etc/hosts echo "0.0.0.0 mdmenrollment.apple.com" >> /etc/hosts echo "0.0.0.0 deviceenrollment.apple.com" >> /etc/hosts echo "0.0.0.0 gdmf.apple.com" >> /etc/hosts echo "0.0.0.0 acmdm.apple.com" >> /etc/hosts echo "0.0.0.0 albert.apple.com" >> /etc/hosts " 3.now you have successfully shield the host. if you do not wan to upgrade to Sonoma, then enjoy your macOS without annoying notifications. and if you want Sonoma, please follow the second step.
step 2: delete two files and built two files
1.shut down your Mac and enter Recovery.
2.in terminal on Recovery, enter "csrutil disable" to disable SIP.
3.reboot your Mac. in terminal on macOS.enter the command below and press enter. " sudo rm /var/db/ConfigurationProfiles/Settings/.cloudConfigHasActivationRecord sudo rm /var/db/ConfigurationProfiles/Settings/.cloudConfigRecordFound sudo touch /var/db/ConfigurationProfiles/Settings/.cloudConfigProfileInstalled sudo touch /var/db/ConfigurationProfiles/Settings/.cloudConfigRecordNotFound sudo launchctl disable system/com.apple.ManagedClient.enroll "
finish! now you can enjoy the boring Sonoma.
I did the above steps on a previously MDM bypassed working Ventura then updated to Sonoma and it worked.
On another machine I did a clean install of Ventura then blocked/patched/bypassed MDM. Then updated it to Sonoma.
I want to run migration assistant on a Time Machine backup to restore files and apps. If I only migrate over apps and files and no network settings will the bypass stick?
What's up! What do I do if I have already updated to Sonoma and the notification appears? I did the steps mentioned but since it was already updated I guess that's why it doesn't work. I didn't realize it and it was updated...
I've been on Sonoma since beta 1, however I have had to manually install each update and now 14.1 isn't appearing. Anyone else have this issue too in software update?
What's up! What do I do if I have already updated to Sonoma and the notification appears? I did the steps mentioned but since it was already updated I guess that's why it doesn't work. I didn't realize it and it was updated...
You could boot to recovery and try the bypass site listed in the video. I have another machine in the same state as yours and I’m going to try it when I get home.
¡Qué pasa! ¿Qué hago si ya actualicé a Sonoma y aparece la notificación? Hice los pasos mencionados pero como ya estaba actualizado supongo que por eso no funciona. No me di cuenta y se actualizó...
Puede iniciar la recuperación y probar el sitio de derivación que aparece en el video. Tengo otra máquina en el mismo estado que la tuya y la voy a probar cuando llegue a casa.
Ok I'll do it right now, I'll comment on the result...
Well, the video didn't work for me, I also did the other videos that are practically the same but nothing works, I still get the notification in system settings. From what I have read, the only way to solve it is to reinstall the system and do a clean bypass. I hope someone with great knowledge of it can help. Thank you.
¡Qué pasa! ¿Qué hago si ya actualicé a Sonoma y aparece la notificación? Hice los pasos mencionados pero como ya estaba actualizado supongo que por eso no funciona. No me di cuenta y se actualizó...
Puede iniciar la recuperación y probar el sitio de derivación que aparece en el vídeo. Tengo otra máquina en el mismo estado que la tuya y la voy a probar cuando llegue a casa.
https://gist.github.com/sghiassy/a3927405cf4ffe81242f4ecb01c382ac?permalink_comment_id=4690041#gistcomment-4690041Ok lo haré ahora mismo, comentaré el resultado...
Well, the video didn't work for me, I also did the other videos that are practically the same but nothing works, I still get the notification in system settings. From what I have read, the only way to solve it is to reinstall the system and do a clean bypass. I hope someone with great knowledge of it can help. Thank you.