You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
idevicedebug + ideviceimagemounter broken with iOS 17 #1452
There seems to be a new structure or system for developer disk images and invoking debugserver. Debugging through Xcode in the "intended" way works the same.
Firstly, after iOS 16.4, there are no more disk images and signatures in the Xcode directory.
Second, when first plugging my iOS 17 iPhone into Xcode 15, I saw this message:
Also, I noticed there are certain specific device disk images at /Applications/Xcode-15-beta.app/Contents/Resources/CoreDeviceDDIs/iOS_DDI.dmg
this is not issue with libimobile, apple need to fix this, provide proper developer image for new OS version, then and only then, we can see how libimobile works with that.
it seems ios 16 also supports this image (i could get both the developer and the personalized image to mount simultaneously. one is at /Developer while the other is at /System/Developer)
i'm currently researching the protocol changes done to the developer protocol. it seems it doesn't even use lockdownd any longer, but the "RSD" (RemoteServiceDiscovery) instead.
NOTE: This new personalized image now requires an IM4M as the image signature from apple's ticket server just like during the update process
Reacted by k-inoway, Gianni Hong and Roman Gardukevich
i'm kind of consused, so it doesn't go anymore on top of their mux protocol, but instead over tcp on top of rndis adapter (or wifi)?
still kinda surprised it doesn't contact lockdown first to start mounter service, that would mean, that service is either running all time, or is started from xpc proxy on phone.
However, the DeveloperDiskImage interactions are purely over network afterwards. I'm currently working on a sniffer and parser for packets sent from the Interuments app and publish it once it is completed.
This will be the first step in writing my own client and allowing others easier research.
That makes sense, @doronz88 I was tying to use socat over usbmux and found no traffic on it when running Instruments, making me wonder if they are using another interface.
I'll want it to be supported on windows and Linux and since this is extracted from a DMG file it's not trivial to support other systems then macos. I'll eventually create a repo for the extracted files to remain platform independent. The you'll be able to simply connect the device and execute the mount without any additional parameters
Reacted by David Klopp, Matt, k-inoway, truonggiang0710, James Riley Wilburn and bbb651 🇮🇱
Also, has anyone tested if this fork is able to retrieve performance metrics like Memory, CPU Usage etc., @doronz88 great work btw!!! Just been looking at the changes you have made over the last few days
So what is the state of this? What extra steps will be required to get this working on iOS 17? From my small understanding, we will at least need a Mac with Xcode to generate our personalized dev disk image, and some changes will be needed to the code, but after the changes are implemented, is that all we would need to do? get the personalized dev disk image and it'll work?
For those encountering problems running on iOS 17 devices with Xcode 14.x, there's a workaround mentioned in this Stack Overflow discussion: How to run on iOS 17 device using Xcode 14.
...
File "/opt/homebrew/anaconda3/envs/myenv/lib/python3.10/site-packages/pymobiledevice3/service_connection.py", line 118, in sendall
self.socket.sendall(data)
OSError: [Errno 9] Bad file descriptor
`
Hi, why am I having this error message when mounting DDI?
no, libimobile has no support for this. there exists python implementation, if it works on other systems than os x, no idea, either test it, or ask author
Activity
joshrad-dev commentedon Jun 6, 2023
Result from trying to debug app using Xcode 14.3 after connecting to xcode 15 beta:
Details
mexmer commentedon Jun 6, 2023
this is not issue with libimobile, apple need to fix this, provide proper developer image for new OS version, then and only then, we can see how libimobile works with that.
Dantee296 commentedon Jun 7, 2023
seems with ios 17 we need to modify image mounter to support "personalized developer images"
doronz88 commentedon Jun 7, 2023
i'm also currently dealing with these changes. i managed to get the personalized image mounted:
https://github.com/doronz88/pymobiledevice3/pull/463/files
it seems ios 16 also supports this image (i could get both the developer and the personalized image to mount simultaneously. one is at
/Developerwhile the other is at/System/Developer)i'm currently researching the protocol changes done to the developer protocol. it seems it doesn't even use
lockdowndany longer, but the "RSD" (RemoteServiceDiscovery) instead.NOTE: This new personalized image now requires an
IM4Mas the image signature from apple's ticket server just like during the update processzhuowei commentedon Jun 7, 2023
@doronz88 Apple did mention they switched to a new framework for device communication (https://techhub.social/@JTostitos/110499792791802006).
Is the RemoteServiceDiscovery the same RemoteXPC framework used to talk with the Touch Bar / Studio Display (https://duo.com/labs/research/apple-t2-xpc)?
doronz88 commentedon Jun 8, 2023
@zhuowei it does bare some resemlence, at least the fact its over USB ethernet (ncm). I'm still trying to wrap my head arround it
doronz88 commentedon Jun 8, 2023
UPDATE: I'm getting the hang of it. It is RemoteXPC, but the existing tools will require some work before they can actually capture this
mexmer commentedon Jun 8, 2023
i'm kind of consused, so it doesn't go anymore on top of their mux protocol, but instead over tcp on top of rndis adapter (or wifi)?
still kinda surprised it doesn't contact lockdown first to start mounter service, that would mean, that service is either running all time, or is started from xpc proxy on phone.
doronz88 commentedon Jun 8, 2023
The mounter service is still on top of
lockdowndas you can see in my implementation over here:https://github.com/doronz88/pymobiledevice3/pull/463/files
However, the DeveloperDiskImage interactions are purely over network afterwards. I'm currently working on a sniffer and parser for packets sent from the Interuments app and publish it once it is completed.
This will be the first step in writing my own client and allowing others easier research.
karthikgbbristol commentedon Jun 8, 2023
That makes sense, @doronz88 I was tying to use socat over usbmux and found no traffic on it when running Instruments, making me wonder if they are using another interface.
doronz88 commentedon Jun 8, 2023
I'm currently sniffing it from my
en19network which is created when I connect the device over USBjoshrad-dev commentedon Jun 13, 2023
@doronz88 Which files are the trust cache and build manifest? Where do you find each?
doronz88 commentedon Jun 14, 2023
Inside the
IOS_DDI.dmgGeczy commentedon Jun 14, 2023
where do you find the signature, im4m?
doronz88 commentedon Jun 15, 2023
Look at the code. I request it just like any TSS request
3 remaining items
doronz88 commentedon Jun 15, 2023
I'll add a CLI method, but anyway you can trigger the
get_manifest_from_tss()and provide the correct build manifestGeczy commentedon Jun 15, 2023
ah got it, yeah i can get the correct build manifest. thanks ill try that for now
Geczy commentedon Jun 15, 2023
fwiw, this can all be extracted automatically
from
/Applications/Xcode-beta.app/Contents/Resources/CoreDeviceDDIs/iOS_DDI.dmgwhy the need to specify it one at a time?
doronz88 commentedon Jun 15, 2023
I'll want it to be supported on windows and Linux and since this is extracted from a DMG file it's not trivial to support other systems then macos. I'll eventually create a repo for the extracted files to remain platform independent. The you'll be able to simply connect the device and execute the mount without any additional parameters
doronz88 commentedon Jul 17, 2023
Just updating I already have a part of the Developer Services working.
For the image mounter you can look and use the same implementation for
libimobiledevice:https://github.com/doronz88/pymobiledevice3/blob/master/pymobiledevice3/services/mobile_image_mounter.py#L325
In general, I created this repository which stores all the DeveloperDiskImages together with the new Personalized format as splitted files so we'll be able to mount them cross-plartform.
https://github.com/doronz88/DeveloperDiskImage
mforys commentedon Aug 7, 2023
When do you expect to have these fixes already merged to the official release branch?
karthikgbbristol commentedon Aug 9, 2023
Also, has anyone tested if this fork is able to retrieve performance metrics like Memory, CPU Usage etc.,
@doronz88 great work btw!!! Just been looking at the changes you have made over the last few days
yodaluca23 commentedon Sep 18, 2023
So what is the state of this? What extra steps will be required to get this working on iOS 17? From my small understanding, we will at least need a Mac with Xcode to generate our personalized dev disk image, and some changes will be needed to the code, but after the changes are implemented, is that all we would need to do? get the personalized dev disk image and it'll work?
kj54321 commentedon Sep 22, 2023
Hi Folks, may we know the status? pymobiledevice3 only has work around on MacOS, but still no luck on Windows/Linux. Thanks
chirag05k commentedon Oct 30, 2023
For those encountering problems running on iOS 17 devices with Xcode 14.x, there's a workaround mentioned in this Stack Overflow discussion: How to run on iOS 17 device using Xcode 14.
jzhang1043 commentedon Nov 17, 2023
`(myenv) ➜ ~ python -m pymobiledevice3 mounter auto-mount --rsd fdad:84fd:1e10::1 59338
...
File "/opt/homebrew/anaconda3/envs/myenv/lib/python3.10/site-packages/pymobiledevice3/service_connection.py", line 118, in sendall
self.socket.sendall(data)
OSError: [Errno 9] Bad file descriptor
`
Hi, why am I having this error message when mounting DDI?
jzhang1043 commentedon Nov 18, 2023
nvm, I reinstalled python from 3.10 to 3.11 and the problem was resolved.
gotwig commentedon Dec 10, 2023
When I understand correctly there is a fix branch that just needs to be merged on main, or is that mac only?
Is that possible soon :)?
mexmer commentedon Dec 10, 2023
no, libimobile has no support for this. there exists python implementation, if it works on other systems than os x, no idea, either test it, or ask author
https://github.com/doronz88/pymobiledevice3
victorvianna commentedon Jul 8, 2025
Re this comment: I just tested and pymobiledevice3 does work with iOS 18.5