Hi everyone!
Like many others I ran into the problem that my bootcamp-partition would no longer boot after installing Mojave DB2, instead always firing up MacOS. Now the same happened for me with Beta 3. If one or more of these conditions apply to your problem here’s how to get it going again:
Solution:
Boot into internet recovery (cmd+alt+r at boot), klick the apple on the top left and select startup disk. Select bootcamp and reboot. Windows should boot by default and you can select the OS in bootloader again
Using the Internet recovery is crucial as it will detect the bootcamp partition as bootable unlike point 2 higher above. My guess is it is still based on 10.13. I have yet to determine wether normal recovery works too and if you can set macOS as default OS to boot again via recovery. In DB2 that was not possible for me, I’ll update this thread.
Hope this helps some lost souls that think their firmware is damaged or something.
Like many others I ran into the problem that my bootcamp-partition would no longer boot after installing Mojave DB2, instead always firing up MacOS. Now the same happened for me with Beta 3. If one or more of these conditions apply to your problem here’s how to get it going again:
- bootcamp does no longer boot when selected in bootloader
- bootcamp partition does not show up in startup-disk in system preferences
- first aid in disk utility not helping
- „bless“-command not working
Solution:
Boot into internet recovery (cmd+alt+r at boot), klick the apple on the top left and select startup disk. Select bootcamp and reboot. Windows should boot by default and you can select the OS in bootloader again
Using the Internet recovery is crucial as it will detect the bootcamp partition as bootable unlike point 2 higher above. My guess is it is still based on 10.13. I have yet to determine wether normal recovery works too and if you can set macOS as default OS to boot again via recovery. In DB2 that was not possible for me, I’ll update this thread.
Hope this helps some lost souls that think their firmware is damaged or something.
