If you've ever wanted to downgrade your legacy devices but didn't have the tools for the job, then this one may be for you. Tihmstar has released an addition to his well-known futurerestore tool (sometimes called Prometheus), entitled libipatcher. What does libipatcher do? In a nutshell, it will allow you to downgrade any jailbroken 32-bit device to any firmware for which you have blobs.
The signing window for iOS 10.3.1 could close any moment now, with iOS 10.3.2 released and iOS 10.3.3 in beta already, so this is your last chance to save your blobs for iOS 10.3.1, to upgrade to it from a lower firmware, or to downgrade to it from iOS 10.3.2+.
iOS 10.3.1 isn't currently jailbroken, and being on that firmware is in no way a guarantee of a jailbreak. However, you never know what'll happen, and there have been some stirrings, so act now! Take necessary precautions before signing ends.
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.
It's been a busy period for tihmstar's suite of tools since the release of Prometheus during the 33c3 convention. Both TSSChecker and Prometheus have seen some problems, as well as updates in the intervening period, and this article will bring you up to date with their current statuses.