Skip to content

M5 MacBook Air not detected by restorekit after entering DFU / Debug USB (0x1881) #51

Closed

Description

@rs1278

Summary

When using restorekit (via the GUI Enter DFU mode button or sudo restorekit restore) to put a 13" or 15" M5 MacBook Air into DFU mode, the DFU trigger succeeds—Apple Configurator immediately recognizes the target Mac in DFU—but restorekit fails to detect the device and reports:

VDM error: no target detected on the DFU port (check the cable and port)

Steps to Reproduce

  1. Connect a 13" or 15" M5 MacBook Air to the host Mac's DFU port with a direct passive USB-C cable.
  2. Click Enter DFU mode in the restorekit desktop app or run sudo restorekit restore.
  3. The target Mac enters DFU / Console USB mode (verified in Apple Configurator), but restorekit does not recognize it as a connected DFU target.

Environment

  • Host Mac: 14" MacBook Pro (M3 Max, J514mAP) running macOS Tahoe (26.x)
  • Target Devices: 13" and 15" M5 MacBook Air
  • Connection: Apple USB-C cable (included with a Mac) into the target's designated DFU port

Observed USB Enumeration (ioreg)

After restorekit triggers DFU, ioreg -p IOService -c IOUSBHostDevice -l shows the target enumerating with PID 0x1881 ("Debug USB") and no USB Serial Number attribute:

"idVendor" = 1452        (0x05ac)
"idProduct" = 6273       (0x1881)
"USB Product Name" = "Debug USB"
"bcdDevice" = 1024       (0x0400)
"bDeviceClass" = 255     (0xff)
"bDeviceSubClass" = 255  (0xff)
"bDeviceProtocol" = 255  (0xff)
"USB Serial Number" = <absent>

(Note: On some attempts, the target enters Port DFU / Console USB mode instead, and is still not recognized by restorekit.)

Additional Context

  • Apple Configurator detects the target M5 MacBook Air in DFU mode immediately over the same cable and port.
  • Happy to run additional ioreg / verbose diagnostic commands or test builds on this hardware if needed.

(Note: This bug was identified with the assistance of AI, but the details have been tested and confirmed by a human)

Activity

  1. fcjr commented on Nov 14, 2026

    @fcjr
    Owner

    Hey @rs1278 thanks for the issue, this is a new DFU mode that the app currently doesn't support. I unfortunately don't have a a new enough mac to test this this weekend (i have a buddy who hopefully will be able to get me one this week).

    In the meantime, I have a proposed fix that adds support for KIS mode but the full flow is still untested. If you happen to be able to test this PR on the machine you mentioned it would be greatly appreciated: #53

    (I was only able to test the DFU flow not the full restore as i only have an A series iphone that supports KIS not an m5 machine yet)

    lmk if you are able to test, otherwise i will test this as soon as i am able to get my hands on some newer hardware

  2. freddy-fazbear-real commented on Nov 14, 2026

    @freddy-fazbear-real

    Hey @fcjr - I am having the same issue on an M4 MacBook Pro. I'll try testing.

  3. fcjr commented on Nov 17, 2026

    @fcjr
    Owner

    This should be fixed in v0.6.2: https://github.com/fcjr/restorekit/releases/tag/v0.6.2 thanks to @freddy-fazbear-real and their help. (also shout out to @gregsadetsky for helping me get a test bench to confirm)

    @rs1278 lmk if you have any more issues!

  4. rs1278 commented on Nov 19, 2026

    @rs1278
    Author

    Looks to be fixed! Thank you for the quick turnaround. Just had an opportunity to test the latest release today, but noticed another bug with two laptops connected. will open a new PI for it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions