Age | Commit message (Collapse) | Author | Files | Lines | |
---|---|---|---|---|---|
2023-07-25 | Add SE,ChipID 0x2C | 1 | -1/+1 | ||
2023-07-25 | Display iBoot boot stage | 2 | -0/+29 | ||
This helps debugging cases where the iDevice does not go into stage 2 because of a missing firmware | |||||
2023-07-25 | Add support for incoherent iBoot parameters | 1 | -5/+7 | ||
Some firmwares to load during iBoot stage 1 can have both: - isLoadedByiBoot = false - isLoadedByiBootStage1 = true This allows to load it at stage 1 | |||||
2023-05-23 | Use DeviceGeneratedRequest plist for SE TSS requests | 2 | -8/+22 | ||
2023-04-30 | Make sure git-version-gen and .tarball-version are included in dist tarball | 1 | -1/+5 | ||
2023-04-30 | git-version-gen: Prevent multiple lines of output | 1 | -1/+2 | ||
2023-04-21 | Updated to use latest libplist API | 2 | -2/+2 | ||
2023-04-14 | docs: Updated man page | 1 | -32/+77 | ||
2023-04-14 | Allow setting custom TSS request URL through command line switch | 2 | -6/+34 | ||
2023-04-13 | img4: Remove unused debug code | 1 | -31/+0 | ||
2022-10-19 | restore: Fix compilation error due to wrong variable name | 1 | -2/+2 | ||
2022-10-19 | restore: Only print boot object v3/v4 plist in debug mode | 1 | -2/+8 | ||
2022-10-18 | Use limera1n_is_supported instead of compatibility check added with previous ↵ | 1 | -17/+1 | ||
commit | |||||
2022-10-12 | Check if device is limera1n-vulnerable for --pwn option | 1 | -8/+30 | ||
2022-10-11 | recovery: Also send "go" and "reset" commands with bRequest set to 1 | 1 | -2/+2 | ||
2022-10-08 | recovery: Send bootx with bRequest set to 1 for all platforms | 1 | -1/+1 | ||
2022-10-07 | [github-actions] Fix MinGW build | 1 | -1/+1 | ||
2022-10-05 | recovery: set bRequest to 1 when sending bootx command | 1 | -1/+1 | ||
In macOS 13 beta 8 or newer release, bootx seems to fail if bRequest is 0 in the control transfer setup. Then, the device fails to enter restore mode. Seems like something has changed in iBEC since beta 8 and Apple Configurator 2 has set it to 1, so do the same thing. While this could be applied for all *OS variants, it's limited to macOS for now just to be safe. Signed-off-by: Munehisa Kamata <kamatam@amazon.com> | |||||
2022-10-04 | img4: Add support for stitching with additional TBM data | 3 | -7/+191 | ||
2022-10-02 | Reduce memory usage for SourceBootObjectV4 images | 4 | -91/+201 | ||
2022-09-25 | tss: Add preliminary code to set UID_MODE | 1 | -0/+12 | ||
2022-09-25 | tss: Make sure vinyl tags include eUICC,Gold and eUICC,Main digests | 1 | -0/+19 | ||
... as well as eUICC,ApProductionMode which was missing before. | |||||
2022-09-21 | img4: Add some more component tags | 1 | -16/+28 | ||
2022-09-21 | tss: Add NeRDEpoch to TSS requests for newer devices (iPhone 13 and up) | 1 | -0/+2 | ||
2022-09-20 | ipsw: Add some NULL checks to ipsw_extract_to_file_with_progress() | 1 | -1/+12 | ||
2022-09-16 | tss: Don't add @BBTicket in tss_request_new() | 2 | -2/+1 | ||
2022-09-16 | Fix Cryptex1 and Cryptex1LocalPolicy TSS request handling | 3 | -15/+74 | ||
2022-08-29 | restore: Add support for Cryptex1LocalPolicy firmware updater | 1 | -10/+23 | ||
2022-08-29 | restore: use an appropriate ticket for Cryptex1 global manifest | 1 | -7/+24 | ||
macOS 13 introduced a new global manifest for Cryptex1 and it requires tickets found in Firmware/Manifests/restore/cryptex1/macOS Customer/ inside an IPSW, but we currently do not use the tickets and end up unexpected behavior on a Mac device after restoring, e.g. bputil fails to downgrade security mode due to "Cryptex1 manifest verification failed". This adds a proper handling to use the appropriate tickets. Signed-off-by: Munehisa Kamata <kamatam@amazon.com> | |||||
2022-08-23 | tss: Skip components with IsFTAB:true when adding AP tags to request | 1 | -0/+6 | ||
This should fix devices failing to enter restore mode due to an incorrect signature for the repective components. | |||||
2022-06-28 | restore: Don't print 'Attempting to continue after critical error' warning ↵ | 1 | -1/+1 | ||
when no error was detected This only occurred when using --ignore-errors command line option. | |||||
2022-06-28 | Make sure to exactly match the passed variant when using --variant | 3 | -9/+9 | ||
2022-06-27 | Add --variant command line switch to specify build identity to use | 2 | -4/+16 | ||
2022-06-27 | Ignore 'Research*' variant in build identity selection | 1 | -2/+2 | ||
2022-06-27 | ipsw: Add workaround for missing RestoreBehavior entries for ipsw info | 1 | -1/+9 | ||
2022-06-27 | Don't print an error message when RestoreBehavior is missing | 1 | -13/+6 | ||
2022-06-27 | ipsw: Improve error message when fwrite fails | 1 | -2/+2 | ||
2022-06-23 | Support iOS 16.0 Beta 2 (#506) | 1 | -0/+1 | ||
2022-06-20 | Remove more serial number checks, and get ECID early on in all modes | 8 | -135/+31 | ||
Some devices seem to not have a serial number, usually in restore mode, which will cause the restore operation to fail since we specifically check for it. An earlier commit already removed the actual comparison in favor of comparing the ECID, but some checks would still result in restore failures as it can't retrieve the serial number on said devices at all. This commit also makes sure to get the ECID in all modes as early as possible and removes all the helper functions for it since they are not needed anymore. | |||||
2022-06-20 | Add support for FirmwareUpdaterPreflight message | 1 | -0/+31 | ||
This message seems mandatory on the new versions of MacOS (12+), but it seems an empty response is what's expected. | |||||
2022-06-17 | Use more elegant way to match file name to component name | 1 | -37/+33 | ||
2022-06-17 | restore: Fix memory corruption in restore_get_timer_firmware_data | 1 | -1/+1 | ||
2022-06-17 | Add support for iOS 16 | 4 | -21/+157 | ||
2022-05-23 | ipsw: Update to reflect color macro name change in libimobiledevice-glue | 1 | -7/+7 | ||
2022-04-27 | Fix restore for devices that don't have eUICC | 1 | -1/+1 | ||
Because of a default value of (uint64_t)-1LL returned when _plist_dict_get_uint doesn't find the dictionary entry for the given key, a later comparison of that unsigned value against something like >= 5 will result in the condition being true even though it was not supposed to. _plist_dict_get_uint will now return a default value of 0 if the key is not found. Code paths that deal with actual values of 0 vs. non-existent values need to test the existence of the key deal with that; I am currently not aware of anything that would be affected. | |||||
2022-04-25 | Increase recovery mode disconnect and re-connect timeout from 10 to 60 seconds | 1 | -2/+2 | ||
2022-04-15 | configure: Only check for pthread if really required | 2 | -524/+6 | ||
2022-04-14 | configure: Make sure the plist_from_json works | 1 | -0/+1 | ||
2022-04-13 | Print version string upon execution | 1 | -0/+2 | ||
2022-04-13 | autoconf: Automatically derive version number from latest git tag | 2 | -19/+51 | ||
with a fallback to get the version string from a .tarball-version file |