d0n13
commented
3 months ago Maybe related to #867
Open d0n13 opened 3 months ago
dorssel
commented
3 months ago The usbmuxd error is logged here: https://github.com/libimobiledevice/usbmuxd/blob/1.1.1/src/device.c#L601
It looks like it is not usbmuxd's error. usbmuxd is just reporting/relaying the error from whatever underlying driver/library it is talking to. But I don't know what that is; I have no Apple knowledge.
The explanation in https://github.com/dorssel/usbipd-win/issues/867#issuecomment-1956410565 is still the best I can come up with. Try to find whatever usbmuxd is using to talk to the device and see if you can increase the buffer size there.
d0n13
commented
3 months ago The explanation in #867 (comment) is still the best I can come up with. Try to find whatever usbmuxd is using to talk to the device and see if you can increase the buffer size there.
I changed all buffer sizes I could find in idevicerestore which had hardcoded buffers of 65535 and 0xFFFF but the error was the same... Will have to dig deeper for this one I think.
Hi @dorssel
I am trying to run an idevicerestore in wsl to a connected iPhone. When the firmware starts to load onto the phone we get the following error in syslog as reported by usbmuxd on the WSL side.
The idevicerestore command logs are shown below for reference ...
Is it possible to fix this "message was too large (65536 bytes, max = 65535)"??
Many thanks Donie
Note: during the process of restoring the firmware the iPhone presents as different things on the usbipd side as shown. The apple devices persisted are all the same device. Just in case it's relevant. I have to manually bind and attach during the process before the code times out. I'm not worried about that as we can automate that later. Just need it to transfer the image to restore manually first.