Page History
Bug Fixes:
- PHEN-12180 - Failed to erase M1 iMac with an error message - Device absent too long
- PHEN-12615 - BEAD Hangs during erasure
- PHEN-12414 - BEAD misidentifies M3 MacBooks, and Apple Configurator fails
- PHEN-12453 - Wrong Storage Size Reported
- PHEN-12595 - BEAD does not populate battery recharge cycles from BEAD Agent
- PHEN-12271 - M3/M3 pro DFU mode not recognized
- PHEN-12353 - Auto DFU switch issue noticed with Mac mini M1
Comments and Known Issues:
- New erasure standard "NIST 800-88 Clear" is now available for Macs. When the standard is used Macs should be kept connected to BEAD station during the whole erasure flow including re-setup and BEAD agent install phase.
- System sleep prevention is active while BEAD is in use.
- Auto DFU switch is disabled for Mac Mini M1.
- There's three "Osascript" trust queries seen at BEAD's first launch after installation and all of them should be trusted. In case those trust queries aren't validated instantly and those get expired the BEAD launch fails (MacOS default 120s). If that happens BEAD can be re-started and when trust queries are validated in time BEAD will launch successfully.
- Please note that sometimes when setting the Macs automatically to DFU mode using the DFU helper solution the UI tooltip might not update as expected and doesn't ask to switch to processing port to free the DFU cable. In that case once the mac is in DFU mode, cable can be swapped and erasure is expected to start. Except Macbook Pro M3 (A2918) model that need to be connected to DFU cable during the erasure also.
- It's possible some iPhones/iPads only setup partially e.g. for diagnostics flows and some manual steps might be needed to get setup finished.
Bug Fixes:
...