| Age | Commit message (Collapse) | Author | Files | Lines | 
|---|
|  |  | 
|  |  | 
|  |  | 
|  |  | 
|  |  | 
|  |  | 
|  | This fixes hanging as the following payload message is not received
initially but after polling the second time. | 
|  |  | 
|  |  | 
|  |  | 
|  |  | 
|  |  | 
|  |  | 
|  |  | 
|  |  | 
|  |  | 
|  | This introduces passing around the "selected" build identity and
fixes code logic issues to make idevicerestore work again. | 
|  |  | 
|  |  | 
|  |  | 
|  |  | 
|  |  | 
|  |  | 
|  | Most of the time it means that there is no device attached as we
should be able to detect any mode of a device. | 
|  | We already handle the complex restore process, let's avoid the trouble
to add up the activation complexity additionally. | 
|  |  | 
|  | Since the iOS 4 IPSW contains a BuildManifest.plist even for devices
that do not require personal signing, the prior code logic would fail. | 
|  |  | 
|  |  | 
|  | duplicating them | 
|  |  | 
|  | not sure if it will run yet | 
|  |  | 
|  |  | 
|  |  | 
|  |  | 
|  |  | 
|  |  | 
|  |  | 
|  | the restore process to allow for easier porting | 
|  |  | 
|  | over the place | 
|  | state access | 
|  | declarations into the header file for easier maintainance | 
|  | starting to mature really well | 
|  | activate code to be cleaned up and added to process later | 
|  |  | 
|  |  | 
|  |  | 
|  |  |