Skip to content

Commit

Permalink
Update Documentation and Submodules
Browse files Browse the repository at this point in the history
* Update README.md
* Remove error message that prevents building on other platforms.
* Update Jssy (submodule)
  • Loading branch information
DanTheMann15 committed Jan 28, 2021
1 parent af69f55 commit 3c1c625
Show file tree
Hide file tree
Showing 3 changed files with 22 additions and 19 deletions.
36 changes: 21 additions & 15 deletions README.md
Original file line number Diff line number Diff line change
@@ -1,53 +1,59 @@
# tsschecker
tsschecker is a powerful tool to check TSS signing status on combinations of<br/>various devices and iOS/iPadOS/tvOS/watchOS/macOS firmware versions.
tsschecker is a powerful tool to check TSS signing status on combinations of various apple devices and firmware versions.

## Features
* Allows you to get lists of all devices as well as all Firmwares and OTA versions for a specific device.
* Can check signing status for any firmware version (by specifying a `BuildManifest.plist`).
* Supports Apple TV, Apple Watch, HomePod, iBridge, iPadOS, iOS and MacOS (Apple Silicon)
* Allows you to get lists of supported apple devices as well as Firmwares and OTA versions for any specified apple device.
* Can check signing status for any firmware version by specifying either a firmware version or a BuildManifest.
* Works without specifying any device relevant values to check signing status, but can be used to save blobs when given an ECID and the option --print-tss-response (although there are better tools to do this).

tsschecker is not only meant to be used to check firmware signing status, but also to explore Apple's TSS servers.
tsschecker is not only meant to be used to check firmware signing status, but also to explore Apple's TSS servers.<br/>
By using all of its customization possibilities, you might discover a combination of devices and firmware versions that is getting signed but wasn't getting signed before.

# About nonces:
## recommended generators for saving tickets:
* `0xbd34a880be0b53f3` // used on Electra & Chimera jailbreaks
* `0x1111111111111111` // used on unc0ver jailbreak
* `0xbd34a880be0b53f3` // default on the Electra, Chimera and Odyssey jailbreak apps.
* `0x1111111111111111` // default on the unc0ver jailbreak app.

## Nonce Entangling (Apple A12/S4 and newer)
Newer devices, like the iPhone XR or the Apple Watch Series 4 have nonce-entangling enabled.
Newer devices, such as the iPhone XR or the Apple Watch Series 4 (and any device newer) have nonce-entangling.

this means the boot nonces generated by your device are now also UID derived, and consequently device-specific.<br/>to save usable tickets for a newer device, you need to get the boot nonce that your device actually generates from your generator.
this means any boot nonce generated by your device is now also UID derived, and consequently device-specific.<br/>to save usable tickets for a newer device, you need to get the boot nonce that your device actually generates from your generator.

for information on how to get your actual boot nonce, [see this post on r/jailbreak](https://www.reddit.com/r/jailbreak/comments/cssh8f/tutorial_easiest_way_to_save_blobs_on_a12/).

## Nonce Collisions:

the Nonce Collision method only works on a few firmwares and devices, and isn't reliable.<br/>it's better to save a ticket with a generator and use the [checkm8](https://github.com/axi0mx/ipwndfu) bootrom exploit.
the Nonce Collision method only works on a few firmwares and devices, and is not reliable and not recommended.<br/>it's a lot better to save a ticket with a generator and use the [checkm8](https://github.com/axi0mx/ipwndfu) bootrom exploit or a nonce setter.

Recovery Nonce Collisions only occur on a few iOS versions, like iOS 9.3.3 and iOS 10.1-10.2 on the iPhone 5s<br/>and is not reliable as once you update, your device will either generate different nonce or not collide nonces anymore.
Recovery Nonce Collisions only occur on a few iOS versions, like iOS 9.3.3 and iOS 10.1-10.2 on the iPhone 5s<br/>and is not reliable as once you update, your device will almost-certainly not collide nonces anymore.

DFU Nonce Collisions commonly occur on any device using A7 and A8 chipsets, regardless of iOS version.<br>and is much more reliable than using recovery collisions.
DFU Nonce Collisions on the other hand, very commonly occur on any device using A7 and A8 chipsets, regardless of iOS version<br/>and is MUCH more reliable than using recovery collisions.

# Build
Install dependencies
Install or Compile dependencies

* Buildsystem:
* autoconf
* autoconf-archive
* autogen
* automake
* libtool
* m4
* make
* pkg-config

* Tihmstar's tools:
* Tihmstar's libs:
* [libgeneral](https://github.com/tihmstar/libgeneral)
* [libfragmentzip](https://github.com/tihmstar/libfragmentzip)

* External:
* External libs:
* [libcurl](https://curl.haxx.se/libcurl/)
* [libirecovery](https://github.com/libimobiledevice/libirecovery)
* [libplist](https://github.com/libimobiledevice/libplist)
* [openssl](https://www.openssl.org/) or commonCrypto on macOS/OS X
* [libzip](https://libzip.org/)
* [openssl](https://www.openssl.org/) (or you can use CommonCrypto on macOS/OS X)
* [zlib](https://zlib.net/)

* Submodules:
* [jssy](https://github.com/tihmstar/jssy)
Expand Down
3 changes: 0 additions & 3 deletions configure.ac
Original file line number Diff line number Diff line change
Expand Up @@ -24,9 +24,6 @@ case "${host_os}" in
darwin*)
build_mac=yes
;;
*)
AC_MSG_ERROR(["OS $host_os is not supported"])
;;
esac

# Pass the conditionals to automake
Expand Down
2 changes: 1 addition & 1 deletion external/jssy

0 comments on commit 3c1c625

Please sign in to comment.