The second EFI partition isn't really relevant, but the Touch Bar runs full-blown iOS, and has its own permanent storage and firmware which gets upgraded separately in the form of an EEPROM.įor some reason Apple tries to hide the recovery partition when doing full hard drive wipes on the M1. The M1 does actually have an EFI partition, actually it has two, you can easily the main one using a Hackintosh tool such as OpenCore Configurator, it mostly contains pre-boot drivers (and pending firmware updates). With that said, you are able to boot Ubuntu live and then from the Ubuntu environment you are able to format the drive completely. Infact you can’t even erase the internal drive normally outside of a DFU restore. The drive will show up as uninitialised.īut this is not applicable to M1. In fact this even deletes the partition map. Now I can see where you’re coming from, in fact I wrote a medium article on how to property reset an INTEL mac where I told people to unmount all the partitions on the internal disk and then useįor 1 second to completely delete every partition on the drive. Not to mention M1 does not have an EFI and it’s recovery mode is vastly different from Intel chips. Sooo… “that won’t clean and restore the EFI and recovery partitions” is a load of BS. The whole machine is flashed.Īs far as I’m aware, the IPSWs for M1 are also signed meaning if even a single hash was out of place, the machine would reject it. It doesn’t matter if it’s done from Monterey or Big Sur. If you are on Big Sur you need to be on the latest (11.5) version with Xcode 13 beta installed and command line tools selected in locations.Īlso, do you know what you are talking about? Because a DFU is a DFU. If you’re on Monterey you need to disable private relay before interacting with recovery mode or DFU with iDevices, M1 and T2 devices. So I put the intel back into DFU and this time didn’t bother using an IPSW, instead I restored it from the button in configurator and it downloaded the ipsw itself and flashed the firmware. The mac restarted without informing Apple configurator and it hung on 2/2. This worked first try but Apple configurator was a bit buggy. After doing so I downloaded the latest stable BridgeOS IPSW for my mac model and then used that to flash the T2 with the stable version. After some poking around it turns out that an easy fix is to disable private relay. I then noticed my intel Mac’s T2 chip was still on a beta firmware so I put the intel mac into DFU and using my newly formatted M1 as the host this time I went to DFU restore the T2 // BridgeOS on the intel mac. I then installed Xcode 13 beta and Apple configurator was able to use the beta IPSW with no issues through a DFU. I ended up using internet recovery mode to do a clean install to 11.5. But it still failed to DFU restore the M1. I actually updated the host mac to the latest beta of Monterey. Originally my intel host mac was on big sur 11.2.3. But this hasn’t made a difference.įailed to copy auth install options in DFU mode. But the beta IPSW is not working.įor good measure I have also removed the beta seed profile from the laptop so it uses the public seed server. I have tried using a macOS 11.2.3 IPSW and it works. But it is still unable to flash the MacBook Air with the beta IPSW. I have since updated the bigsur laptop to Monterey beta 3. However, the big sur laptop would not DFU my m1 MacBook Air to Monterey beta 3. I was able to use a big sur laptop to DFU my iPhone. I am unable to do a restore to my iPhone or my M1 MacBook Air.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |