| Age | Commit message (Collapse) | Author | Files | Lines | 
|---|
|  |  | 
|  |  | 
|  |  | 
|  |  | 
|  |  | 
|  |  | 
|  |  | 
|  |  | 
|  |  | 
|  |  | 
|  |  | 
|  |  | 
|  |  | 
|  |  | 
|  | firmware | 
|  |  | 
|  |  | 
|  |  | 
|  |  | 
|  | ticket requests | 
|  | data/string/integer nodes | 
|  |  | 
|  |  | 
|  | without erasing user data)
Since it might result in a complete data loss, let's warn the user about it
and ask for confirmation. This check is not performed when -y command line
switch is used. | 
|  | data recovery' | 
|  |  | 
|  | ESEC:false instead of always assuming true | 
|  |  | 
|  |  | 
|  |  | 
|  |  | 
|  | 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 | 
|  |  |