Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
|
|
libimobiledevice
|
|
|
|
interactive mode
|
|
|
|
|
|
|
|
NO COMMENT
|
|
|
|
|
|
|
|
was given
|
|
error: use of undeclared identifier 'STDIN_FILENO'
tcgetattr(STDIN_FILENO, &oldt);
|
|
msvcr100.dll
What a mess it is, all these msvcr*.dll - incompatible without limits
|
|
|
|
|
|
|
|
version when using --latest
|
|
... or we are dealing with a really old WTF device that doesn't ship the WTF
firmware in its .ipsw
|
|
|
|
|
|
|
|
systems lacking it
|
|
|
|
|
|
|
|
|
|
loop issue
|
|
|
|
|
|
|
|
|
|
|
|
identity
|
|
|
|
|
|
|
|
|
|
|
|
|
|
expecting it
This prevents a delay of about 10 seconds at the final stage of the restore process.
|
|
plist_dict_get_item()
|
|
This should be more accurate than guessing based on what is in the
build identity and avoid doing unexpected things for unknown hardware.
|
|
|
|
|
|
|
|
|
|
|
|
The check_hardware_model() function has a misleading name. It returns
a string with the hardware model but this is not used. Instead, this
function is only called for its side effect to initialise an irecv
device in the passed client struct which it creates from the hardware
model name returned by mode specific implementations. But these mode
specific implementations already create an irecv device to get the
hardware model name so instead of going through this unnecessary
complication just return the irecv device directly and rename the
function accordingly to make this clear. (This may also prevent
leaking an irecv device in the mode specific functions.)
|