Unofficial archive. This is a read-only, community-run archive of the Apple Support Community. It is not affiliated with or endorsed by Apple Inc.
mc_bubbles
User level: Level 1 (4 points)

2019 MacBook Pro (T2) won’t format internal SSD + DFU Restore/Revive both fail with error 102

I’m trying to completely wipe and reinstall a 2019 Intel MacBook Pro 16" with T2 and a 500 GB internal SSD.

I do NOT care about any data recovery. The only goal is to get the Mac working again with a completely clean macOS installation.


Original problem

The Mac refused to update to Tahoe and after a complete wipe it somehow lost the Macintosh HD disk and I could no longer boot up properly.


Internet Recovery works with `Option + Command + R` and offers macOS Sonoma, but I cannot get the internal SSD formatted correctly.


What I have tried

Disk Utility could not erase/unmount them because they were reported as being used by:process 0 (kernel)

I then opened Terminal in Internet Recovery.

`diskutil apfs list` showed:

- Internal physical SSD: `disk0`

- APFS physical store: `disk0s2`

- APFS container: `disk2`

I successfully ran:

`diskutil unmountDisk force /dev/disk2`

It returned that all volumes were successfully unmounted.

I then ran:

`diskutil eraseDisk APFS "Macintosh HD" GPT /dev/disk0`

The GUID partition map was created successfully, but APFS formatting failed with:

`newfs_apfs: unable to format volume inside /dev/disk0s2: Input/output error`

and:

`Error: -69832: File system formatter failed`


After rebooting into Internet Recovery again

The old macOS Beta volumes were gone.

Disk Utility showed the ~500 GB internal partition as unknown/unformatted.

I tried erasing it as APFS again.

Disk Utility managed to:

- initialize the partition

- switch `disk0s2` to APFS

- create a new APFS container (`disk2`)

But it failed while:

`Creating APFS Volume`

with:

`An internal error has occurred. (-69624)`



Then I went on to DFU recovery. I tried a full T2 DFU recovery.

Host Mac:

- MacBook Pro M1

- macOS Tahoe 26.5.1

- ~872 GB free space

- Correct DFU USB-C port used on the 2019 MacBook Air (most right port when looking at the left side of the laptop, according to apple).

- Tried 3 different genuine Apple USB-C cables (confirmed with WhatCable)

The 2019 Pro successfully enters DFU mode and both Apple Configurator and Finder on the host Mac shows:

`Mac-DFU-tilstand`

So DFU mode itself is definitely working, however:


Revive Mac fails with:

`Unknown error (102)`


Restore Mac also fails with:

`Unknown error (102)`


Apple Diagnostics

I also ran Apple Diagnostics on the 2019 MacBook Pro.

Result:

`ADP000 – No issues found`



Current situation

So at this point:

- Internet Recovery works

- DFU mode works and is detected correctly

- Apple Diagnostics passes with ADP000

- The internal SSD can be repartitioned

- APFS container creation partly works

- Creating/formatting the actual APFS volume fails

- `newfs_apfs` has produced an explicit `Input/output error`

- Disk Utility has also failed with error `-69624`

- DFU Revive fails with error `102`

- DFU Restore fails with the same error `102`

- Multiple Apple USB-C cables have been tested


Has anyone seen this exact combination before?

Does this strongly suggest failing NAND/internal storage, T2/storage controller, or another logic-board issue despite Apple Diagnostics returning ADP000?

Or is there still a firmware/DFU/APFS procedure worth trying before assuming hardware failure?

Again, I do not care about recovering any data. I’m completely fine with wiping everything. I just want to get the internal SSD into a usable state so macOS can be installed again.

Posted on Oct 15, 2026 3:07 AM

3 replies

HWTech
User level: Level 9 (78,350 points)

Oct 15, 2026 7:33 AM in response to mc_bubbles

Just curious of the exact model of the host Mac used for the DFU Firmware Restore and version of macOS on it. You can get this information by clicking the Apple menu and selecting "About This Mac".


In my personal experience you will need a host Mac that is currently running macOS 15.7+ Sequoia, macOS 26.x Tahoe, or macOS 27.x Golden Gate. At least for Sequoia and possibly even Tahoe, the use of the Apple Configurator app v2.19+ is required. Unfortunately Apple's instructions are wrong on the OS requirements as well as other things and when using the wrong items things just won't work....sometimes with no error messages (this is the Apple today). Using the Apple Configurator app is usually best because it does provide just ever so slightly more information about the state of the "broken" Mac.


Disclaimer: I have not had the opportunity to use DFU Firmware Revive/Restore since the release of macOS 27 last month so I cannot be sure of the actual OS requirements for the host Mac, but I just checked and the Apple Configurator app appears to have been updated to v2.21, but still shows as being compatible with macOS 15.7+ Sequoia so what I wrote here is likely correct.


My organization doesn't have too many of the T2 MBAirs, but they do seem to have a lot of Logic Board failures.


You can always take it to Apple to have them attempt the DFU Firmware Restore on your behalf hoping that they have a bit more experience performing the procedure. I've performed the procedure a number of times and I can tell you that I still have problems and know very little about it. I despise it....always have even with iPods, iPhones, & iPads.


FYI, I do not recommend spending any money on repairs of any Intel USB-C Mac for multiple reasons....especially the T2 Airs as the money spent is much better put towards a new laptop.


Edit: I have successfully used a Thunderbolt rated cable (one with the lightning bolt on the connector) to perform a DFU Firmware Revive/Restore counter to Apple's own documentation (only tried it one time so far).

mc_bubbles Author
User level: Level 1 (4 points)

Oct 15, 2026 9:25 AM in response to HWTech

All the information regarding the host Mac is already in the post. I have a MacBook Pro 16" 2021 with an M1 Max chip and macOS Tahoe 26.5.1, so that should all be up to standard.


I've tried multiple cables including a thunderbolt rated cable with the lightning bolt on the connector to perform a DFU, but they all end up in the same 102 error code.


I was not planning on spending money on repairs due the age of the laptop, hence me trying everything I possibly can to get this fixed myself.

Originally posted at discussions.apple.com/thread/256376384