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

iPhone 15 Pro Max iPhone 15 Pro Max DFU error

MegaBlue said:
Seems as though if you have any of the 15s on 17.1 beta 1, you CANNOT downgrade to 17.0.2, no matter the method.
Click to expand...
Yep, after spending hours looking into this - that's the current situation.

At least the beta doesn't seem to be all that bad so far. Doesn't seem to fix much either though.
 
  • Like
Reactions: Roman Sydorchuk
Thanks for the warning. I just got my iPhone 15 Pro Max in the mail and was going to do a DFU restore. Looks like I will be skipping that for now.
 
Hi folks,

Are there specific steps one can follow to get an iPhone 15 Pro up and running after attempting to restore the iOS 17.1 DB1 onto the phone (it had 17.0.2 on it but not setup - on the hello screen)? Getting error 4013 using Windows 10 and iTunes 12.12.10.1.

Swapping cables doesn't correct the situation and I have the latest version of iTunes.

UPDATE: Swapping a third usb c cable and it worked. Odd, never had issues with the first two usb c cables.

Thank you in advance,

Bry
 
Last edited:
  • Like
Reactions: Roman Sydorchuk
This is odd, I could not restore my phone from 17.1 to 17.0.2 and went to Apple store as I have AC+, after a couple attempts the guy just brought out a new phone and replaced it👀 at home I tried again to install 17.0.2 via DFU and the same 1669 error appears all the time….
 
Any1 have home thunderbolt 4 usb-c orginal cable? Must try with thi cable. TB4 cable is full pinout used. Must try . I read maybe this cable work for dfu restore
 
Roman Sydorchuk said:
Can you give more details please about the cable you used?
Click to expand...
It's the USB C cable that come with the Belkin BoostCharge Wireless Charging Pad

What I did notice is that while the other two cables have worked flawlessly (with my other USB C devices), iTunes intermittently discovered my iPhone 15 Pro when using them.

Also, Device Manager-> Portable Devices shows my iPhone 15 Pro with the third cable while the first two didn't.

The Belkin cable which worked for a flawless 17.1 DB1 restore via iTunes (Shift +Restore iPhone), never had issues in iTunes discovering my device. Perhaps you can test that assuming you're using Windows + iTunes.

Wonder if Apple is interrogating the cable when inserted and only allowing certain cables to function or only perform specific tasks?
 
Last edited:
LyxxSK said:
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
Click to expand...
Nope, it was same 1669 error, tested on i3 MBA 2020.
 
Continued macOS Sonoma testing over the weekend with various USB-C and Thunderbolt cables from Apple, Anker, Belkin, Generic, HP, LG, TekQ, et. al. No luck whatsoever. Traditional recovery mode restore works with most of these; DFU restore fails with all of them.
 
Last edited:
  • Like
Reactions: Roman Sydorchuk
ViMK3 said:
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.
Click to expand...
It is time to consult with Apple Support as they are the subject matter expert for proper resolution. Wish the best 😊
 
Glad I found this thread. Have been having the same problem, literally nothing has worked. Good to know it's not just me.

Imagine if iOS 17.1 was an unstable mess, and we were stuck on it. We're lucky it's usable. This isn't cool
 
  • Like
Reactions: Roman Sydorchuk
Yep, and as I have mentioned before it’s odd why Apple doesn’t have any solution for that now, they just simply replaced a new Phone for me…. And the new one has absolutely the same issue… hope this is software mater…
 
  • Like
Reactions: chobo997
ibookemo said:
Yep, after spending hours looking into this - that's the current situation.

At least the beta doesn't seem to be all that bad so far. Doesn't seem to fix much either though.
Click to expand...
So what can we do? My iPhone 15 Pro Max is stuck in DFU and I can do anything with it.
 
Confirming this continues to result in the same error for me with an iPhone 15 Pro and Sonoma 14.1b2 (with Xcode 15.1 beta) & iOS 17.1b2.
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back