ipsw device-list

[CCICEngineering]

Is your feature request related to a problem? Please describe.

No it is not, the list is there

Describe the solution you'd like

I would like to see ipsw device-list with all Apple Devices, many devices are missing , for example iPhone 16e, no new iPads iPad15,8 (iPad (A16) Wi-Fi + Cellular) , iPad17,4 , iPad15,7 , iPhone17,5

Describe alternatives you've considered

this should be automatically updated

Search

• [x] I did search for other open and closed issues before opening this

Code of Conduct

• [x] I agree to follow this project's Code of Conduct

Additional context

No response

[blacktop]

have you tried the other cmd device-info:

❱ ipsw device-info --cpu "A18 Pro"

iPhone 16 Pro
  Prod: iPhone17,2
  Type: ios
  SDK:  iphoneos
  Memory Class: 8
  Boards:
    D94AP:
      CPU:           A18 Pro
      CPU ISA:
      Chip ID:       0x8140
      Platform:      t8140
      Platform Name:
      Arch:          arm64e
      Board ID:      0x0E
      Baseband Chip ID:
      Kernel Cache Type: iphone17


iPhone 16e
  Prod: iPhone17,5
  Type: ios
  SDK:  iphoneos
  Memory Class: 8
  Boards:
    V59AP:
      CPU:           A18 Pro
      CPU ISA:
      Chip ID:       0x8140
      Platform:      t8140
      Platform Name:
      Arch:          arm64e
      Board ID:      0x04
      Baseband Chip ID:
      Kernel Cache Type: v59


iPhone 16 Plus
  Prod: iPhone17,4
  Type: ios
  SDK:  iphoneos
  Memory Class: 8
  Boards:
    D48AP:
      CPU:           A18 Pro
      CPU ISA:
      Chip ID:       0x8140
      Platform:      t8140
      Platform Name:
      Arch:          arm64e
      Board ID:      0x0E
      Baseband Chip ID:
      Kernel Cache Type: iphone17


iPhone 16
  Prod: iPhone17,3
  Type: ios
  SDK:  iphoneos
  Memory Class: 8
  Boards:
    D47AP:
      CPU:           A18 Pro
      CPU ISA:
      Chip ID:       0x8140
      Platform:      t8140
      Platform Name:
      Arch:          arm64e
      Board ID:      0x0A
      Baseband Chip ID:  0x08
      Kernel Cache Type: iphone17


iPhone 16 Pro
  Prod: iPhone17,1
  Type: ios
  SDK:  iphoneos
  Memory Class: 8
  Boards:
    D93AP:
      CPU:           A18 Pro
      CPU ISA:
      Chip ID:       0x8140
      Platform:      t8140
      Platform Name:
      Arch:          arm64e
      Board ID:      0x0C
      Baseband Chip ID:
      Kernel Cache Type: iphone17

[blacktop]

NOTE: This database for the device-list cmd is sourced from Xcode's device_traits.db which includes simulator devices and may not accurately map to physical hardware devices. Some entries (e.g., iPad17,4-A, iPad17,4-B) represent simulator variants rather than distinct hardware models.

[blacktop]

the way the cmd is updated is by running: make update_devs periodically; I haven't ran it in a while. It's been updated so the next release will contain the devices you mentioned (along with others)

[CCICEngineering]

Hi, I understand. I’m just trying to point out that the newest devices are missing, but overall this product is fantastic. The way I use it is alongside cfgutil and shell scripting to generate asset tags — or even better, by using the Cambrionix API together with ipsw and cfgutil.

Cfgutil by itself can’t pull the public marketing name (for example, “iPhone 16 Pro”). It only reports identifiers like iPhone17,1. So I had to engineer a mapping workflow. Homebrew + ipsw made that possible. Yes, please keep this up to date.

Apple Configurator can correctly display “iPhone 16 Pro,” but command-line cfgutil cannot, which is why I rely heavily on ipsw.

I also want to ask if it’s possible to add Apple Part Numbers to ipsw — for example: • iPhone 16 Pro → MD0D4LL/A • iPad (A16) → MD7P4LL/A

Apple part numbers depend on model class, storage, color, and carrier. We can only retrieve these reliably from ABM if we have the proper access.

[blacktop]

if you know where to find these you can add them to the ipsw_db.json (which I need add better automation around updating) but for those fields that I won't be able to get to you'd have to add them manually.

Just take a peak in there and see where it makes sense to add a NEW field etc. NOTE I like to keep it minimized for efficiency but it will be easier to work with formatted/pretty-printed etc.