Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

ViMK3

macrumors newbie
Original poster
Jan 16, 2018
12
16
I am testing this iPhone and usually whenever a newer update is available than out of the box, I perform a dfu restore to have the cleanest system possible. With this iPhone I get an error (1669) during the start of recovery phase.
Has it happened to someone else? I would like to point out that I tried with two different m2 Macs, one with Ventura 13.6 and the other with Sonoma rc2, with USB-C USB-C and USB-C USB-A cable without success.
 
I am experiencing the same issue with my iPhone 15 Pro Max and have attempted to install iOS 17.0.2 without success. I am using a Mac Book M1 Pro with version 14.0 (23A344) installed. Has anyone found a solution to this problem yet?
 
  • Like
Reactions: chobo997
Registered just to say I'm in the same boat after extensive troubleshooting and testing with a 15 Pro. Have tested w/

  • Three different Macs I own (Intel & Apple Silicone) Ventura & Sonoma RC2
  • An Apple Genius' MacBook Pro 13" (Apple Silicone) on Ventura
  • A PC running W10 and the latest version of iTunes
  • iMazing v2 and v3 beta (DFU restore option)
  • Latest Xcode from developer site with manual MobileDevice.pkg install
All of this testing with the cable that shipped with the phone and a whole lot of others. Surprised there's not more chatter about this yet!
 
Last edited:
Registered just to say I'm in the same boat after extensive troubleshooting and testing with a 15 Pro. Have tested w/

  • Three different Macs I own (Intel & Apple Silicone, Ventura & Sonoma RC2)
  • An Apple Genius' MacBook Pro 13" (Apple Silicone) on Ventura
  • A PC running W10 and the latest version of iTunes
  • iMazing v2 and v3 beta (DFU restore option)
  • Latest Xcode from developer site with manual MobileDevice.pkg install
All of this testing with the cable that shipped with the phone and a whole lot of others. Surprised there's not more chatter about this yet!
Have you tried using the normal restore or recovery restore instead of DFU?
 
Same problem here for my iPhone 15 Pro Max~

Tried a Windows PC first, and the iPhone didn't even pop up on iTunes.
Then I manually installed the drivers inside "C:\Program Files\Common Files\Apple", so the phone appeared, but got the 1669 error during start of recovery.
Rebooting, Reinstalling iTunes, changing different cables (the one came with the iPhone, Apple's Thunderbolt 4 cable, third-party ones), nothing worked.

So... I bought a brand new Mac Mini, only to find out the same error, this time in Finder not iTunes.

I dumped the following error logs from the macOS Console App:
Code:
2023-09-25 08:23:17.000 AMPDevicesAgent[1273:103]: restore library built Aug 21 2023 at 11:55:36
2023-09-25 08:23:17.000 AMPDevicesAgent[1273:103]: AMPDevicesAgent: 1.3.6.14
2023-09-25 08:23:17.000 AMPDevicesAgent[1273:103]: AMPDevicesAgent: Apple Mobile Device version: 1643.2.4
2023-09-25 08:23:17.000 AMPDevicesAgent[1273:103]: AMPDevicesAgent: Software payload version: 21A350
2023-09-25 08:23:17.000 AMPDevicesAgent[1273:103]: AMPDevicesAgent: Using MobileRestore state machine
[08:23:17.7423] Can't get board config with NULL device map
[08:23:17.7425] You can't copy the serial number from a Port DFU mode device
[08:23:17.7433] Failed to determine HubPortService for device at path IOService:/AppleARMPE/arm-io@10F00000/AppleT811xIO/usb-drd0@82280000/AppleT8112USBXHCI@00000000/usb-drd0-port-hs@00100000/Apple Device (Port DFU Mode)@00100000
[08:23:17.7433] _AMRSerialLogServiceIsHubPortService: service did not conform to "AppleUSB20HubPort"
[08:23:17.7433] Failed to determine HubPortService for device at path IOService:/AppleARMPE/arm-io@10F00000/AppleT811xIO/usb-drd0@82280000/AppleT8112USBXHCI@00000000/usb-drd0-port-hs@00100000/Apple Device (Port DFU Mode)@00100000
[08:23:17.7433] _AMRSerialLogServiceIsHubPortService: service did not conform to "AppleUSB20HubPort"
[08:23:17.7433] _AMRSerialLogCopySWDName Error: failed to get serial service for device
[08:23:17.7434] =====================================================
[08:23:17.7434] Device info:
[08:23:17.7434]   board configuration: (null)
[08:23:17.7434]   Board ID: 0x6
[08:23:17.7434]   Chip ID: 0x8130
[08:23:17.7434]   ECID: 0x3D[MASKED]
[08:23:17.7434]   Serial Number: (null)
[08:23:17.7434]   USB Location: 0x100000
[08:23:17.7434]   USB Name: (null)
[08:23:17.7434]   Starting State: Port DFU
[08:23:17.7434]   Production Fused: NO
[08:23:17.7434]
[08:23:17.7434] Build Info:
[08:23:17.7434]   Restore Bundle Path: /var/folders/0b/[MASKED]/T/iPhone Temporary Files.noindex
[08:23:17.7434] =====================================================
[08:23:17.7448] Successfully applied power assertion
[08:23:17.7450] requested restore behavior: Erase
[08:23:17.7538] Automatically set FormatForAPFS => True and FormatForLwVM => False.
[08:23:17.7539] Failed to create recovery OS variant , no recovery variant in options nor restore variant.
[08:23:17.7539] requested restore behavior: Erase
[08:23:17.7587] Couldn't find recovery OS variant in the restore variant based on the behavior based variant.
[08:23:17.7596] No recovery variant found in bundle, continue without recovery OS installation.
[08:23:17.7598] Not setting apfs boot-args because option is not set to true.
[08:23:17.7609] Changing state from '(null)' to 'Restoring'
[08:23:17.7689] AMPortDFUModeDeviceCopyAuthInstallPreflightOptions: Using signing server https://gs.apple.com:443
[08:23:18.9776] AMPortDFUModeDeviceCopyAuthInstallPreflightOptions: failed to personalize. TSSResonse was NULL: 3194
[08:23:18.9779] Finished Port DFU Restore Phase: Failed
[08:23:18.9782] State Machine Dump, status:ERROR - [state:Port DFU remaining-cycles:0] -> [state:DFU remaining-cycles:1 (current state)] -> [state:Recovery remaining-cycles:2] -> [state:RestoreOS remaining-cycles:1]
[08:23:18.9786] Changing state from 'Restoring' to 'Error'
[08:23:18.9786] State is now set to error: Can't restore Port DFU device with NULL prepared boot options
[08:23:18.9809] Restore completed, status: 0
[08:23:18.9809] Elapsed time (in seconds): 1
[08:23:18.9809]
[08:23:18.9809] =====================================================
[08:23:18.9809]  Successfully restored
[08:23:18.9809] =====================================================
[08:23:18.9809] Failure Description:
[08:23:18.9809] Depth:0 Code:0 Error:Can't restore Port DFU device with NULL prepared boot options
 
  • Like
Reactions: chobo997
Is there any advantage of DFU restore?
Well, no advantage whatsoever if everything's well. But if you just accidently bricked your phone, DFU is the most convenient way to get it back normal (after all reaching out for a Genius Bar is kinda troublesome).

For me, it's just some sort of way to quickly check my new iPhone hardware (DFU flashing will reveal some hardware issues as well as unauthorized modifications), plus getting a "relatively cleaner" system installed~
 
Tested this too, @Banglazed... DFU restore of earlier Lightning and USB-C devices completes without issue. Sure looks like a 15-specific issue at this point.
 
I would help troubleshoot but I have already set up my 15. Another suggestion, would you be able to try the latest Apple Configurator 2? It can detect DFU mode and restore it. Have you submitted the issue through Feedback app?

 
  • Like
Reactions: Roman Sydorchuk
Appreciated, @Banglazed. Failed to include this in my initial post above, but the latest version of Apple Configurator 2 attempts a DFU restore and ultimately returns this error:

Code:
iOS cannot be restored on this iPhone.
Can't restore Port DFU device with NULL prepared boot options
[com.apple.MobileDevice.MobileRestore - 0х0 (0)]

Feedback has been submitted to Apple. No updates as of posting.
 
I was able to DFU restore both my iPhone Pro 15 and my wife’s Pro 15 on a Mac Studio running Ventura 13.6.

When I first connected my 15 Pro using a basic Mophie USB-C cable plugged into the Studio Display, macOS prompted me to install a software update to connect to the phone. I’ve seen that message before, but usually when running an older OS.

After that, I backed up the phone, unmounted it in finder, and did the button press magic to enable DFU on the phone and initiated the process in Finder once the phone reconnected.

I don’t know if this will help anyone, but I just wanted to share my experience.
 
  • Like
Reactions: Roman Sydorchuk
I was able to DFU restore both my iPhone Pro 15 and my wife’s Pro 15 on a Mac Studio running Ventura 13.6.

When I first connected my 15 Pro using a basic Mophie USB-C cable plugged into the Studio Display, macOS prompted me to install a software update to connect to the phone. I’ve seen that message before, but usually when running an older OS.

After that, I backed up the phone, unmounted it in finder, and did the button press magic to enable DFU on the phone and initiated the process in Finder once the phone reconnected.

I don’t know if this will help anyone, but I just wanted to share my experience.
What IOS version your iPhones were during the installation? 17.0.1 or 17.0.2?
 
Appreciate the tip, @StudioMacs. Running the release version of Sonoma here. Will attempt again and report back ASAP.

UPDATE: Unfortunately, no change here. Anyone else able to test?
 

Attachments

  • 1669 error.png
    1669 error.png
    179.3 KB · Views: 227
Last edited:
All,

Just completed a fresh install of Ventura 13.6 (22G120) on a new partition, received the “A software update is required to connect to your phone.” message, installed the update and restarted, entered DFU mode, attempted a restore, and… same 1669 error as above. Anyone else have success?

Thx!
 
  • Like
Reactions: Roman Sydorchuk
hi, same . 17.0.2 DFU error 1669... a trying osx 13.6 and sonoma release v. macbook with m2 max. any1 try on intel cpu macbook, not silicone? i think problem maybe in USB drivers.. we need try dfu with iphone USB C to lighting connector. but in localy apple store not in stock
 
  • Like
Reactions: chobo997
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.