Questions/Help/Issues Thread

[assafdori]

Welcome!

Feel free to use this space to ask questions, post screenshots with issues, and so on. I'll try to help you out, or some other community member will.

[MasoudAlhelou]

Thanks, and it worked perfectly for me. I have a question: can I freely do updates, or do I have to create a temp user with every update?

[poporobright]

If I am not mistaken, someone recently updated their computer from 15.0 to 15.1.1 and brought MDM back, so it may break it.

[reabo]

miss information

[reabo]

I cant find a clear or honest answer anywhere. Id this bypass last year for Sonoma 14.5 and avoided updates incase id have to run the bypass again.

Any one in a similar position and updated via system settings? Did you mac run as normal or did you need to do thebypass again ti keep it MDM free?

[supigupi]

Does this work for more serious updates (macOS Sequoia 2024 -> macOS Tahoe 2025)?

[poporobright]

Does this work for more serious updates (macOS Sequoia 2024 -> macOS Tahoe 2025)?

Do not update. Wait some time to update it. You don’t always need the latest updates on your MacBook.

[supigupi]

Thank you for the response! I didn't mean to be rushing, I am asking out of curiosity. Will this bypass work when I eventually do the update to Tahoe?

[poporobright]

Thank you for the response! I didn't mean to be rushing, I am asking out of curiosity. Will this bypass work when I eventually do the update to Tahoe?

As all of the recent updates have gone well, I suspect Tahoe won’t overwrite the hosts data so I have high hopes.

[assafdori]

This is not yet tested on Tahoe so best to hold back until myself or someone else here confirms it.

[bloomerberg]

Hey Assaf,

Thanks for this tool. Just curious though, did you code this up by scratch yourself or was it modified from some other projects out there.

I'm not really technical so trying to understand how you came with this idea and were able to implement it successfully.

Thanks!

[assafdori]

Hey,

It's a combination of both. The methods have been known previously but I couldn't find a script that does it for you, so I compiled one.

Feel free to direct further questions to my inbox hi@assafdori.com

[bloomerberg]

Will do. Thanks, Assaf.

[poporobright]

Hi @assafdori,

Thank you for making this script. I am a bit of a noob on what I should be seeing once I ran the script. I got error messages such as directories or files not found after the step of creating the local account then the green text came up. Is this normal?

I hope you're doing well.

[assafdori]

Hey @poporobright feel free to attach screenshots and or logs and either myself or others will be able to assist

Assaf

[poporobright]

Hi, thanks for getting back so quickly! I think my problem was this:

I reset computer to factory settings > tried to wipe the hard drive but then it restarted on its own > tried to do the script and then updated to Sequoia 15.0 like you said in the title.

That’s when the computer asked me to set it up and connect to internet again cuz it belonged to a company. While trying to run the script again a second time, that’s when it worked.

hope that makes sense.

[user20033]

Thank you so much you saved my life, just still got only one problem that is i couldnt make my self admin and i dont know what is the real admin name or password i tried mine but it doesnt work even the Apple 1234 pleae help , and thank you again .

[poporobright]

This is odd, if you are able to sign into the computer after running the script and restarting, then you can technically create a new user (for yourself) and make it an admin as you are creating it, that's the way to do it. See the images below:

[yention]

Hey man, I know it works on some devices, probably I have "special" case.

1. I erised disks
2. ran script:
   
   and then reboot (restarted)
3. The very first thing I see is
   
   and in few mins later:
   

[poporobright]

Hey,

did you do the following?

1. Restarted into recovery
2. Wiped the hard drive
3. Install Mac OS from a Drive
4. Once Mac OS installed, restarted and went through setup until remote management came up
5. Went back into recovery and followed the steps to use Safari in Recovery to run the script in Terminal
6. Once script gave the good to go, you restarted
7. The login screen came up to login with Nam: Apple and the password in the documentation.

Is this what you went through? Also what is your laptop’s processor? Intel or Apple Silicon?

I want to help you.

[yention]

thank you for your quick response. yes, it was my way. Silicon (m2 or m3, cannot remember it for sure)

…

On Sat, Dec 21, 2024 at 10:52 AM poporobright ***@***.***> wrote: Hey, did you do the following? 1. Restarted into recovery 2. Wiped the hard drive 3. Install Mac OS from a Drive 4. Once Mac OS installed, restarted and went through setup until remote management came up 5. Went back into recovery and followed the steps to use Safari in Recovery to run the script in Terminal 6. Once script gave the good to go, you restarted 7. The login screen came up to login with Nam: Apple and the password in the documentation. Is this what you went through? Also what is your laptop’s processor? Intel or Apple Silicon? I want to help you. — Reply to this email directly, view it on GitHub <#17 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AFIYC6PTYTRDSXH4ZEFCUMT2GWMFLAVCNFSM6AAAAABQD5UXQKVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCNRTHA2DKOA> . You are receiving this because you commented.Message ID: ***@***.***>

[poporobright]

Okay, do this:

insert the thumb drive in the computer port
Shut down MacBook
Wait 10 seconds, press and hold power button until you see options to pick your thumb drive with a version of MacOS, I prefer at least 15.0
Once in recovery, try to wipe hard drive, then if it reboots, try to install Mac OS again the same way,

once that all completes, make sure you then setup the MacBook til the enrollment screen comes up, force a shut down, go back into recovery, connect to WiFi, open safari, go to this site and then make sure to copy the bash command entirely.

close safari and open terminal, run command, once complete, restart, then check again

[yention]

It was a tambourine dance, but I did the same script several times and it worked!
Now the only thing left to sort out is security and possible future problems.
I found serial number still under enterprise coverage lol.
Thank you!

[madhat1]

Hi,
A few questions:

1. Is there a point on executing the script before reinstalling the OS? Does the OS installation restore MDM?
2. Why is it recommended to install the OS from USB? I'm having trouble creating a venture USB boot disc on Windows, if I install the OS via the regular way (through internet) the MDM bypass will not work?

Thanks

[poporobright]

Oh I see what you mean, not sure if the repo owner might have reasons behind it, if he does, then idk what they are, don’t think he mentioned the thumb drive for 0ero reasons. I say still give it a try by installing the OS via network and see how things go. I wouldn’t stress about it.

[madhat1]

It worked on Ventura 13.7.2! Yay!
So if I want to upgrade to latest macOS I guess I'll have to run the script again when MDM will show up after installation is finished?

[poporobright]

Awesome! However there are points you must understand.

Some updates COULD bring MDM back as updates patch certain aspects of the OS. However, when I did mine, I did it with 15.0 on a thumb drive, everything worked, turned off updates in settings when I got in. I was skeptical to update to 15.1.1 as someone said the update brought back MDM, I assume the data in the /etc/hosts file was set to default by the patches (I’m just guessing here) but then was brave enough to update to 15.2 and so far no issues with MDM being prompted.

Just keep that in mind. Worst case, you must reset hard disk again and then upgrade.

[madhat1]

Thanks for the tips.
Just to clarify, if I do upgrade to latest and then reset hard disk, it will suggest to reinstall the latest OS right?
If MDM returns in that case I should re-run the MDM bypass script or downgrade to lower version OS via USB?

[poporobright]

Not really.

This script will run with any version of Mac OS, specially since you’re still in Ventura, you can just upgrade to 15.2 from there and it shouldn’t bring MDM enrollment back, at least that’s how my machine has been working fine since updating from 15.0 to 15.2 no issues yet.

if it were to happen, then yes, wipe machine, reinstall OS (15.2 is fine too) and get to enrollment page when setting up, recovery to run script, then boom, login screen for default Apple account made by script.

if u don’t get my stuff up there let me know lol I will write it once more :]

[alexskapene]

bonjour tout le monde, j'ai juste une question

je veux savoir si le script peut résoudre le problème l’Activation Lock sur macbook M1 2020, cela est parvenu lorsque j'ai effacé le disque dur sans l'accord du bureau alors que je ne sais le mot de passe de l'iCloude activé sur le mac.

Vos réponses me seront d'une grande importance. Merci

[poporobright]

Hi there,

I don’t think this would do that. You can however try to use a different MAC with Apple Configurator using DFU Mode and see if you have success. I believe there’s a video online about it.

good luck

[alexskapene]

bonjour, merci pour la réponse rapide, je voulais aussi si ce script ne peut pas résoudre mon problème ?
Et il ne peut pas il y a un autre solution à me proposer ?

[poporobright]

Nope, no other solution is given to you besides what's in this Git Repo. Sorry. You might have to keep looking online.

[alexskapene]

bonjour cher team, je vous espère tous dans bon état, je reviens encore une question, j'airmerai savoir si le script peut passer sur Macbook Air 2020 i7, je vais passer sur le mot de passer de véroullage. Merci pour votre suite

[merchantirani]

Bonjour,

Oui, le script devrait fonctionner sur un MacBook Air 2020 i7, tant que la version de macOS est compatible avec la méthode utilisée (par exemple macOS Sequoia, Ventura, ou une version antérieure selon la compatibilité du script).

Si votre objectif est de passer l’écran de mot de passe/verrouillage, veuillez noter :

Si le Mac est verrouillé iCloud (avec “Localiser mon Mac” activé), alors le script ne pourra pas contourner le verrouillage d’activation.

Si iCloud n’est pas activé et que vous souhaitez juste passer le mot de passe utilisateur, oui, c’est possible, avec un accès Terminal et le bon script.

Assurez-vous que :

FileVault est désactivé

Le Mac n’est pas en mode perdu

Vous avez un accès complet au disque (via le mode récupération ou un système bootable)

N’hésitez pas à me donner la version exacte de macOS installée sur le MacBook Air 2020 — je peux vous confirmer la compatibilité plus précisément.

[Rushh12]

When I finished the process, I tried to put in the default password but it wouldn't work

[poporobright]

Did you ensure you entered 1234 ?

The script sets the password to that above, so it should not be a problem if you do this correctly. I'd say, wipe the hard drive, do the process again and test it once more.

[Jerry12798]

How do some claim to remove MDM? They told me it's to do with the serial number. I would suspect this would be their method as my laptop now too says no activation lock in system settings nor has any profiles in settings. If I update or factory reset will I regain MDM?

[assafdori]

How do some claim to remove MDM? They told me it's to do with the serial number. I would suspect this would be their method as my laptop now too says no activation lock in system settings nor has any profiles in settings. If I update or factory reset will I regain MDM?

Yes, factory reset will bring back the MDM.

[7Orange7]

Hi Assaf

Are you able to advise if I follow the instructions without erasing the drive or installing OS from flash, will cause any traceable or irreversible problems with my protected M4 MacBook? OS is Sequoia 15.3.2. I have the option to sign in to Apple - not done it though. Any advice would be appreciated!

[7Orange7]

Hi again Assaf - so I followed the initial instructions and it gives me options, click that and I get a second of loading bar then black screen and cursor. Would a DFU option if I can get a second Mac help? Thank you!

[merchantirani]

If you follow the instructions without erasing the drive or reinstalling macOS from a flash drive, and your M4 MacBook is already running Sequoia 15.3.2 without showing "Enrolled via DEP" or any active MDM profiles, then you’re generally in a safe zone — as long as you don’t sign in to iCloud with “Find My Mac” enabled or allow a system reset.

Key things to keep in mind:

No Erase / No Reinstall = No Re-enroll:
As long as you avoid wiping the disk or using macOS Recovery (especially internet recovery), the device will not auto-re-enroll into MDM or get re-locked.

Don’t Sign in to iCloud Unless You're Sure:
If you log in with your Apple ID and accidentally enable “Find My Mac”, it can trigger activation lock, which is irreversible unless you have Apple’s blessing.

Stay on This OS Version (15.3.2):
Don’t update to a newer Sequoia version unless you’re sure the bypass or MDM block won't be broken. Apple could patch the loophole you’re relying on.

No Flash Drive or Fresh Install:
Avoid booting from external media or trying to reinstall the OS. That’s the most common way people accidentally trigger DEP/MDM re-enrollment.

[merchantirani]

Hi, first of all thank you for this amazing project. I successfully used the bypass on my:

MacBook Pro 14" (M2 Pro, 2023)
Current version: macOS Sonoma 14.5 (23F79)
Status:

Enrolled via DEP: No

MDM Enrollment: No

Activation Lock: Removed

Find My Mac: Disabled

I want to update via System Settings to macOS Sequoia 15.5 (shown as 8.75GB).
Can anyone confirm if this update is safe for already bypassed machines like mine, or if the MDM screen returns after update?

Thanks in advance!

[poporobright]

Hi there!

my MBP M3 Pro is up to date meaning it’s running 15.5 no issues on MDM coming back to the machine.

I’ve checked the /etc/host file every now and then but it’s never changed so we’re on the clear here.

[merchantirani]

Hey bro, thanks for confirming earlier — I followed your lead and successfully updated my:

MacBook Pro 14" (M2 Pro, 2023)
to macOS Sequoia 15.5 (Build 24F74)

✅ Status after update:

Enrolled via DEP: No

MDM Enrollment: No

/etc/hosts block entries still intact

Everything is working perfectly after the update — no MDM screen, no remote profiles, nothing.

So anyone who has already bypassed MDM on their Mac can now safely update to Sequoia 15.5 without issues.

Thanks again for giving the confidence ✌️

[merchantirani]

@assafdori @poporobright

Now, here’s my question for those with real-world experience:

🧠 After a clean MDM/DEP bypass, is it safe to turn Find My Mac back ON — or will it risk re-enabling Activation Lock and re-binding the device to Apple’s remote control again?

I understand that Find My writes a firmware-level flag that persists even after erase/reinstall.
But I want to hear from those who’ve tried it — especially on Apple Silicon Macs:

Have you turned it ON again after bypass?

If yes, did it re-enable Activation Lock after a reset or DFU?

If no, why are you keeping it off?

Any permanent consequences or recovery issues you faced?

Just trying to confirm best practices so I don’t unintentionally lose the freedom I’ve gained.

Thanks in advance to anyone who shares their experience 🙏

[poporobright]

I’ve turned Find My ON for my computer. No issues, no Apple locking my computer no anything so far.

[merchantirani]

@poporobright @assafdori

❓ Question:
I'm currently running macOS 15.5 (Sequoia) on my MacBook Pro M2, and it's already MDM bypassed.

I'm considering updating to the latest macOS 16 (Tahoe) public beta.

If I update to the beta directly, will the existing MDM profile come back?

Or will the bypass stay intact, and I can update without needing to bypass again?

Just want to confirm:

Will updating from 15.5 to the beta re-enable or restore the MDM lock?

Or is it safe to proceed with the beta update without triggering MDM again?

Any insight from people who’ve updated a bypassed device would be super helpful. Thanks!

[poporobright]

I’d avoid Beta testing. Why? I don’t know what will happen vs stable versions. I never do betas cuz I’m skeptical about those since are out in testing phases. Maybe wait til you’re in the safe zone.

[bluegrc-spec]

Hi community, I have a situation with my M4 Macbook Air. When I hold power button it does say "loading startup options" but as soon as it says so it gets the a screen saying "This Mac is Locked. The system PIN is required to use this Mac" I neve get to the screen where I can select options.

[bluegrc-spec]

[poporobright]

From what I understand you must have another Apple device capable of running Apple Configurator in order to perform a DFU Mode reset on the locked device to see if that lets you bypass it.

[bluegrc-spec]

does anyone know how to do that? I do have another Macbook Air M1

[geheim-s]

Heya,

I ran the script and it worked to put in the bypass and change the default username pass etc.

Only after that I got:
couldn’t create host file

And it shows it couldn’t find the Tahoe install folder
(That’s the Mac OS I installed most recently and that’s on the USB as boot).

I closed the terminal script and ran the USB install from recovery. Thru which I now was able to be admin. I could create a new user admin after install also, only the prompt of the MDM keeps coming back which I had no choice to agree to, tried deleting the account and change it to a different admin. And once started it came back again.

so I guess I do have to install it again directly thru the script,
Any tips how to get it to create the host file and let it ran the install straight w the bypass?

what could be the culprit in this case?

[admin294]

Anyone updated to macOS Tahoe 26.3.1?

MacBook Air
M2, 2022

[KazminM]

I upgraded my macbook m1 pro to macOS 26.3.1 and then to 26.3.1(a) without any problems or limitations.

[kylexcore]

have you guys tried updating to 26.5 ?
kinda wondering since im in 26.3 now and worried if i update the MDM will kick in again lol

[Alexi254]

When I ran the script, I'm getting this message:

0Warning: Failed to create the file bypass-mdm.sh: Read-only file system
curl: (23) Failed writing body (0 !=1371)

on a Macbook A1707 with Sierra OS

Can someone help me with this?

Thanks

[Alexi254]

Issue solved.

When formatting hard drive, renamed to Macintosh HD and use the legacy script. That solved my my problem.

[Vossilisco]

Hi @Alexi254

I have a MacBook Pro 16" EMC 3347 with the same error:
Warning: Failed to create the file bypass-mdm.sh: Read-only file system

I tried both scripts and got the same error.

Could you please provide more detail about the rename you performed? I see already "Macintosh HD" and "Macintosh HD - Data" volumes

[Vossilisco]

Ok I made it using:
cd /var/tmp/
and then the legacy script

[qwertyuiop97]

@Vossilisco That solved my read-only issue. Thank you!

Edit: Actually nevermind, it still says read only, except now it actually opens the prompt for the script and says it after I select 1 to bypass MDM.

[mrkasee]

Hi,

Im recieving this error on A2254
What i did : dfu reset, erase hdd, sequioa reinstall in recovery, sip off, mounted hdd to be sure .
After reboot it says cant connect mdm server .
Any advice? thanks,

[brilliantartist888]

Hi
I tried to remove jamfcloud on enterprise macbook. It didn't work and now I'm locked out. Am I done for?

[poporobright]

Kind of a late reply but, yes you are. This is to bypass the MDM enrollment, not remove remote lock. You can try putting the computer on DFU Mode, and restore it using another Mac, but that's the only thing I can suggest you to try.

Please do not reply to this since remote lock isn't part of this github repo.

[brokejaw5]

Anyone updated to 26.5 yet?

[kylexcore]

thats what im waiting for lol anyone please let us know if it works

[poporobright]

Yes, I'm on 25.6 now and no issues. feel free to update.

[hjson-lang]

Hi please help when i copy thr code into terminul it says failure??

[hjson-lang]

Yes pls, that way we can check if the command is missing syntax/content.

[hjson-lang]

There you go!

[poporobright]

Okay, looks like it's not treating part of the process like it's supposed to.

Did you try the commands found in the troubleshooting section of the repo?

https://github.com/assafdori/bypass-mdm#-troubleshooting

You'd have to look at the section of:

Make sure it's executable

chmod +x bypass-mdm.sh

Run it again

./bypass-mdm.sh

See if this helps you

[poporobright]

@hjson-lang any updates on this?

[juanesppinosa-bot]

Is it necessary to reinstall macOS?

[kylexcore]

Can anyone confirm if its safe to update on Tahoe 26.5 ?
I'm currently on Tahoe 26.3 Macbook Air M2 and used this thread to bypass mdm and it worked like a charm. big thanks to assaf!

Now im just a little curious if its safe to update to the latest version as i heard that certain updates will have the MDM security kick in again. and if it is possible for this thread to work again if it ever locked me out. lol

kinda wishing to update as codeweavers updated crossover and they say that there are major fixes and over all performance gain if you are on Tahoe 26.5.

Thanks in advance!

[poporobright]

My main device is on 26.5.1, you should be good.

[basement5k]

My main device is on 26.5.1, you should be good.

I ran this on my mac a few months ago but im still on Sequoia - if I upgrade to Tahoe do i need to still completely wipe my HD and go through the process again? or if I update will the script still work without me needing to go through it again?

[poporobright]

Nope, you'll be fine. MacOS upgrades aren't affecting the MDM bypass because an update isn't meant to overwrite manual the configurations within etc/hosts file. You're okay to proceed.

[kylexcore]

thanks i updated mine now to the latest update.
does that mean that we are safe for future updates?

[poporobright]

Yes, I honestly don't think Apple should in any way affect user created bash lines in the etc/hosts file, apart from their work as the file itself has lines set by them. That'd be a nightmare for all users since there are people out there who do edit the hosts file tailored to their needs.

[iglobalpro]

can someone help me with raw patch for A4-12+ security bypass and other if available let the person drop message on my +23230524087 ibootrom, Ramdisk patch files or jailbreak patch files

[poporobright]

Do not comment/request anything that is not related to this GitHub Repo. @assafdori can we remove this comment from the discussion section? thx.

[juanesppinosa-bot]

Can you help me? I've tried both options and followed the instructions at the bottom, but this is the result I'm getting. Could you please help me?

[juanesppinosa-bot]

If it's properly connected to Wi-Fi, I haven't installed a new macOS; my Mac was working and I accidentally clicked on the MDM notification, then I restarted to perform these steps.

[juanesppinosa-bot]

Is it necessary to reinstall macOS?

[poporobright]

Yes, this script is for machines that have been wiped to factory settings. Just like it shows on the README. You can't do this if you're already using it and clicked on the MDM.

[juanesppinosa-bot]

I’ve installed macOS Ventura on my iMac using OpenCore, and after the installation finished, an MDM notification appeared. At this point, I need to restart and run the command—is that correct?

[poporobright]

Yes, as long as the hard drive was wiped and reloaded you can restart and run the command.

[jexoxoxxxooo]

Has anyone updated to 26.5.2? I want to know if it's safe before I update

[poporobright]

You should be fine.

[jexoxoxxxooo]

Thanks. I was able to update without problem

[merchantirani]

Hello, @assafdori @poporobright

I noticed that you've released Version 2 of the bypass.

About 10 months ago, I used your MDM bypass method, and it's been working perfectly ever since. I can sign in with my Apple ID, iCloud works, Find My Mac works, and everything I normally use is functioning flawlessly.

Thank you for making my laptop usable again!

I just have one question. Does Version 2 offer any significant advantages or additional features over the previous version? Is there any benefit to redoing the bypass, or should I simply keep using my current setup since it's working without any issues?

Thanks in advance!

[8sz8djksh9-dev]

Bro please save me

[8sz8djksh9-dev]

Bro please save me

[Supaleo]

Hello

I browsed the FAQ and was wondering if there is any latest updates about wether the bypass would still work when updating to mac os 27 soon? or when resetting a macbook pro to resell?

thank you

[poporobright]

Reselling this MacBook comes with a risk for the buyer because MDM could activate at any time if for some reason Apple finds a way to disable the bypass with an update — so transparency is non-negotiable if you sell it.

The bypass stays active as long as you don't factory reset the MacBook. It works by modifying the etc/hosts file to block the MDM enrollment server (you can read the script). That change persists through normal use. But the moment you wipe the machine, the bypass is gone and you'd have to redo the whole process before handing it off — just like you had to create your own admin account to get in initially.

macOS major updates shouldn't break it — in theory. Since the bypass lives in the etc/hosts file (which stores user-defined settings), Apple's update process isn't designed to touch or overwrite that file. It would actually be counterintuitive for Apple to delete user-configured data during an update. So upgrading from say Ventura to Sonoma to Sequoia should be fine, but it's never 100% guaranteed, same goes for macOS 27.

Bottom line:

• Don't factory reset unless you redo the bypass first
• Be upfront with any buyer about the MDM situation
• Major updates are likely safe, but always verify the bypass is still working after any significant update.