In this guide, we show you how to save .shsh2 blobs for the Apple TV 4K. On the off-chance a futurerestore-type tool for the device is developed in future, having saved blobs will be essential to use it.
The clock is ticking on signing for iOS 11.1.1/11.1.2 and tvOS 11.0/11.1, so the pressure is on to save blobs for those firmwares, as well as to possibly restore to them. This doesn’t apply to everyone though, so check out our advice on the topic!
Update: tvOS 11.1 and iOS 11.1.2 are now unsigned. DO NOT ATTEMPT TO RESTORE TO THEM!
Now that tihmstar has updated his futurerestore tool with support for Odysseus 32-bit downgrade functionality, we’ve put together a guide for you to upgrade, downgrade, or restore your legacy devices at will, using your saved blobs.
iOS 10.3.1 signing is closing fast. With weak rumours of a possible iOS 10.3.1 jailbreak at some point in the future, we go through whether you should upgrade, downgrade, or save blobs before time runs out.
Given the recent news that a jailbreak for tvOS 10.1.1 may be coming after all, we recently advised all Apple TV 4 owners to downgrade from tvOS 10.2 to tvOS 10.1.1 immediately before signing closes.
Hand in hand with the possibility of a jailbreak comes the necessity of saving blobs for your device, which will allow you to upgrade, downgrade, or restore your device at a later date, without worrying about signing windows. This guide will walk you through how to save blobs for your Apple TV.
The signing window for iOS 10.2.1 could close any moment now, what with the upcoming release of iOS 10.3, so this is your last chance to save your blobs for iOS 10.2.1, or to downgrade to it from the iOS 10.3 betas.
iOS 10.2.1 is not currently jailbroken, so at the moment its blobs are not of use, nor is being on that firmware a guarantee of a jailbreak. However, you never know what’ll happen, so act now! Don’t be left out in the cold when signing ends.
Are you are stuck on iOS 10.2.1 or higher, having missed the iOS 10.2 signing window and therefore the Yalu jailbreak? If so, you may be in luck today, provided you have the correct setup. Early reports have come in that some devices are creating nonce collisions on iOS 10.3 b1, providing an indirect route back to iOS 10.2 through Prometheus.
For this clever workaround to come off, you must have a device which produces collisions, namely the iPhone 5s or (possibly, though not confirmed on iOS 10.3 b1), an iPad Air. If you do, you may be able to downgrade from iOS 10.2.1 to iOS 10.2 and jailbreak, by first downloading and installing iOS 10.3 beta 1, and then downgrading to iOS 10.2 using futurerestore.
We recently reported how some of the .shsh2 blobs saved with previous versions of tihmstar’s TSSChecker were faulty. One problem affected all iPhone 7 and iPhone 7 Plus blobs, rendering them useless. This issue has now been fixed going forward, though past blobs are invalid.
The other problem was more complex and affected only certain models of certain devices. It is also fixed for blobs saved from now on, but given these occurrences, it is important to be able to check whether the blobs you saved in the past are in fact valid and fit for use with Prometheus.
In this article, we’ll go through how to use another tool from tihmstar’s Prometheus suite, img4tool, to verify that your .shsh2 files are good. This method will clarify whether you are affected by the second problem mentioned above, but will also work in general, when checking the validity of your blobs in future.
It seems tihmstar has been busy putting right the flaws in his suite of tools; just one week after he revealed that a bug in his .shsh2 saving tool TSSChecker had led to all iPhone 7(+) blobs saved with it being invalid, a new update restores the ability to correctly save blobs on Apple’s most recent flagship device.