no boot after updating Ventura 13.6

At this point, there are enough users to clearly point to an issue with the 13.6 update. I doubt apple will release a fixed 13.7 since Sonoma is out, but we’ll see.

To get your machine back, follow these directions for restore (be sure to have Apple Configurator if your machine calls for it). You can format a usb drive as a boot drive (Mac OS Extended journaled) and download the Ventura 13.5.2 installer. Use recovery once restored to boot from that USB drive and install pre-bricked Ventura. Or simply go up to Sonoma if your software needs allow.

@synchronizer Look a few replies up. I laid it out, but apparently we can’t post links here. Search the apple support pages for “Revive or restore a Mac with Apple silicon using Apple Configurator

”.

If you need more specific directions. Ask again.

I'm watching the video for DFU mode and don't understand what key combination to press. It's too fast. I need to retain all my files. For simplicity, I can deal with updating to Sonoma, which I was going to delay, but oh well. May I have more specific instructions?

So far, I luckily have a MacBook Air M2 with 13.6, and a thunderbolt cable connected. What do I do next?

@Synchronizer

You may not have a choice but to erase.

If possible, don’t follow video instructions. You’ll need to follow the instructions for Reviving / Restoring Using Apple Configurator. Search Google or Apple Support for the exact phrase in bold from my last reply.

If you do not have a backup of your data, this may be a hard lesson learned.

I’m not a support tech, simply someone who has done this recently, and I’m short on time so:

Download Apple Configurator 2 from the App Store onto your working M2 Air.

Follow the directions in the Revive / Restore support article (like a cooking recipe, read ALL the directions BEFORE you begin), be sure to connect the computer using the proper ports (differs between machines), be sure to NOT use a Thunderbolt 3 cable; a simple USB-C cable (aka drive cable) should do the trick (so long as it can carry power as well as data).

Key combo for dead machine (plugged into power AND connected to working machine with Apple Configurator running) is:

Press and hold power button for 10 seconds to ensure shutdown then release.

Press and release power button and then IMMEDIATELY press and hold:

Power + Shift (right side) + Control (left side) + Option (left side)

for about 6-10 seconds (watch for MagSafe light to change and go out), then release all buttons EXCEPT power button; release power button 3 seconds later.

It can be tricky. Try until you get it.

If you successfully get it into DFU mode, use Configurator to “revive” first. If that doesn’t work, you’ll need to Restore which will wipe your drive.

Other’s may know of a way to use Configurator to save your data, but I don’t know the app well enough to say.

That’s all I’ve got for ya. Good luck!

I got it into DFU in the configurator, but it still says it's not booted and will only erase all content and settings... what do I do? Could it be that I have another issue on top of all of this that bricked the machine?

Not sure why a thunderbolt cable doesn't work, but okay.

I'm absolutely terrible at timing the keys.

My data are mostly in cloud storage, so I think I'm mostly lucky. This is mostly a time waster though. I didn't create a bootable image of any sort.

Here I am after updating my MacBook Pro M2 to, I think it was 13.6.1.

Blank screen after boot up logo and nothing happens anymore.

At the time of updating an external Screen (LG) was connected.

And possibly, it was still running after the update, just the screen was blank. Why? Because the Macbook still did some TimeMachine backups when I thought it was already 'gone'. I started the update before going to sleep, and in the morning it still did its hourly backups. Very strange.

Repairing in DFU mode did not work with the following error:

Failed to restore device in recovery mode, libusbrestore error:21
[com.apple.MobileDevice. MobileRestore - 0x15(21)]

Okay, the above error ("failed to restore...") happens, when the faulty MacBook is not actually in DFU mode. If it shows a computer icon in Configurator and NOT the dotted "DFU" icon, it is possible to select "revive" but it will produce the error. So you really need to be in DFU mode for it to work.

I was able to finish the revive process, but after a reboot the same issue with the blank screen reappears. Apple Service booked. Hopefully they have more options.

I was finally able to get into DFU mode. When I selected "revive" or "restore", or dropped the 13.6.1 ipsw file onto the DFU icon, I got a message that "a software update is needed" on this device. That sounded like I was going to loose my data on the target machine so I kept trying other routes. Finally after looking at the list of supported computers in Apple Configurator 2 I realized mine was not on the list (2021 16" M1Pro) so clicked OK when prompted about the software update and Apple Configurator downloaded the support files (device definitions?) for my computer. Then I was able to "revive" the machine. VERY unclear error message.

The target still would not boot into the failed OS, but I could boot into recovery and from the menu I could share the disk which allowed me to pull the data I wanted to preserve onto the host machine. Then I did a restore from Configurator and all is working normally. Of course I still need to re-install apps and put the data I copied off back in place, but working! This process needs MUCH better documentation.

Finally, I was apple to upgrade to Sonoma without loosing any data, as described here earlier (DFU mode with Configurator, start revive, reboot into options, install Sonoma from there).

It is really a mess by Apple, but finally I have my system back. Thanks to everybody in this thread who shared their knowledge.

Re- Causes This article throws some light on various bug issues and discusses causes. Thankfully found it just as I was about to upgrade to Ventura 13.6 -on 14 inch MBP 2021

https://www.theregister.com/2023/11/01/asahi_linux_mac_black_screen/

I had the similar problem with my company owned mac. After upgrade and restart for ventura 13.6.1, it got crashed after restart. System was not booting up and no display was coming. The IT support has to restore MAC using revive with DFU from other mac. The MacOS was restored with latest Sonoma version and works fine.

This is clearly an issue that is affecting multiple owners - and for those updates to be still be available is just outrageous.

I wish I had found this thread sooner - as I had the same issue yesterday and it has caused personal and financial chaos. In the middle of a high stress deadline I innocently allowed a Ventura and Safari update to run and then my M1 16 Inch would not start up afterwards. Tried safe mode, recovery and then a panic run to the local Apple Store where the employees in the genius bar had no idea about the issue and declared that the logic board was having issues and sent it off for repair.

The fact that this update is still available is just beyond me. And the fact that Apple neither care or can help out small business professionals when they make errors like this which have a real world effect on revenue is just outrageous. Under the UK Consumer Act that firmware could be argued to be defective and so these machines should be replaced. I am just disgusted.

Yes, I understand how you feel. It must be terrible if your own business suffers as a result of Apple's faults. They must have the data, they just don't act on it. I had a very knowledgeable support agent on phone, and she said that this is a very rare issue, but she has heard about it.

It is not the first issue with updates. As a safety precaution I only install x.1 oder even x.1.1 versions on my devices if they are already some days old (security update always, of course). But in this case it was 13.6.1 so this does not help in every case.

I had the same problem when upgrading to 13.6.1. The main screen is HDMI, the second screen is USB C connected. Tried all the suggested fixes. None worked. Could only get one screen to connect at a time.

The problem resolved when I disconnected a Cygnet port expander from the other USB C port. Once the second screen came to life I reconnected the port expander and all works as before the upgrade.

Unfortunately I don't know how long for.