I reported a few weeks back on an interesting new bug for 32-bit devices, which allowed you to restore them to any unsigned iOS 9.x firmware, provided you had blobs for the destination firmware.
At the time, it was thought that the bug would mainly be of use for people downgrading from iOS 9.3.5 to a lower firmware, to jailbreak with Home Depot or Pangu9. However, it turns out the bug is in fact more powerful and wide-ranging than previously thought, and may have much wider utility.
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.
As some of you may have seen from my tweet yesterday, there is some exciting news afoot for owners of 32-bit devices on iOS 9.
A group of developers including alitek12, ee_csw and Trevor Schmitt have stated that they are working on a downgrade solution which will allow users of legacy devices to escape from iOS 9.3.5 and return to a jailbreakable iOS 9 firmware.
With macOS Sierra, Apple dropped support for some of its hardware models for the first time in several years. Citing various incompatibilities and hardware deficiencies, they cut out a large swathe of machines from running Sierra. However, many Mac owners have questioned their motives, observing that some machines have made the cut whilst their more powerful contemporaries (such as the MacBook Pro) have mysteriously been left behind.
This led some to conclude that Apple is simply raising the bar to encourage hardware upgrades, and that there is often no incontrovertible hardware reason which dictates the unsupported machines. In many cases this turned out to be true, and with a few tweaks and amendments many of the "unsupported" machines have been brought back into the fold by a tool by dosdude1, called macOS Sierra Patcher. In this guide, we'll walk you through how to use the tool to install macOS 10.12 Sierra on older Mac hardware, which claims not to support it.
In the last few minutes Apple closed the signing window for iOS 10.2. That means that you can no longer upgrade, downgrade, or restore to that firmware, either over-the-air or through iTunes. You also can no longer save blobs for iOS 10.2 through any tool.
Is your Apple TV acting up and not working properly or do you want to give it a fresh start? In this tutorial, we will show you how to reset and erase your Apple TV to its default factory settings.
We recently covered the release of Luca Todesco's first build of yalu102. This tool will eventually allow all 64-bit devices to jailbreak iOS 10. iPhone 7 and iPhone 7 Plus will be able to use it on iOS 10.0-10.1.1, all other 64-bit devices will be able to use it on iOS 10.0-10.2.
As the signing window for iOS 10.2 could close at any time, the pressure is on to downgrade to iOS 10.2 if you are currently on a higher firmware. Some people on a lower firmware should also upgrade to iOS 10.2, but not everyone. In this guide, we'll talk you through how to upgrade/downgrade to iOS 10.2 from a lower/higher firmware, if you are one of the people who should be there.
What with the release of iOS 10.2.1 and the soon-to-be-closed signing window for iOS 10.2, many people are wondering what the best strategy is for their device. Should they stick with a jailbroken firmware or jump to iOS 10? If they're already without a jailbreak, which iOS version do they need to be on to make sure they get one? What do they need to do to be able to upgrade to iOS 10.2 later, and keep their jailbreak for now?
In this article, we'll quickly go through what we consider the smartest options for each device and iOS version, so that you can (hopefully) make an informed decision.
Extensively updated to reflect beta release of Yalu for 10.2.
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.
Update: tihmstar has stated that the tool is working perfectly, and that he has used it successfully multiple times today. However, some users have been encountering a TSS server error when using the tool nonetheless.
Hot on the heels of Prometheus' release at the 33c3 convention two days ago, tihmstar's tool for upgrading and downgrading to unsigned iOS firmwares seems already to have hit a snag. Following some changes to Apple's TSS servers today, the nature of which are yet to be investigated, the tool has been rendered non-functional at the present time.