iOS 8.3 was released today, but if you’re looking to jailbreak your iPhone or iPad, you’ll have to wait, as details of an iOS 8.3 jailbreak are unknown at this point.
iOS 8.3 includes a handful of new features, including more emoji that are racially diverse and support for using CarPlay wirelessly, as well as the usual bug fixes and performance improvements.
The TaiG dev team, which is responsible for the latest jailbreak version, has not posted anything new on their website to reflect iOS 8.3. Currently, the latest developments from the team include details on an iOS 8.2 jailbreak. According to a message that the TaiG dev team has posted (translated to English), the development of an iOS 8.2 jailbreak tool is “constrained by many factors.” However, the team hopes to release its iOS 8.2 jailbreak “it as soon as we can.”
However, we’re likely to see an iOS 8.3 jailbreak at this point, with iOS 8.2 officially being an older version of iOS and iOS 8.3 possibly being the last major version of iOS 8.
Of course, TaiG’s message doesn’t give us a whole lot of information to work with and it doesn’t exactly give us a timeline as far as when to expect an iOS 8.2 jailbreak, but it at least proves that the TaiG team was working on an iOS 8.2 jailbreak.
Many users were hoping that an iOS 8.2 jailbreak would release last week in conjunction with the 2015 Mobile Security Summit, where the who’s who of the jailbreak community came and talked about their ideas on mobile security and jailbreaking. There were some big names, including P0sixninja, Comex, a member of the Evad3rs dev team, and a couple of members of the TaiG jailbreak team.
iOS 8.1.3 officially patched up the TaiG iOS 8 jailbreak and that has carried over to iOS 8.2. A support page on Apple’s website lists the TaiG Jailbreak Team as the source for a security vulnerability that Apple patched up in iOS 8.1.3, which means that iOS 8.1.3 is unjailbreakable, and as an extension, iOS 8.2 and iOS 8.3 are unjailbreakable as well.
Jailbreak developer MuscleNerd has warned all jailbreakers to stay away from the iOS 8.2 update, since it’s not jailbreakable just yet, and that also goes for today’s iOS 8.3 update .
However, an iOS 8.2 jailbreak was looking pretty optimistic just recently. The TaiG jailbreak team already has a jailbreak available for iOS 8.2 beta 1 and 2. However, there have been newer betas since then and Apple has closed access to the first and second betas for iOS 8.2, but the company hasn’t patched up those specific exploits, meaning that iOS 8.2 is technically still jailbreakable, and as an extension, iOS 8.3 is as well.
On the TaiG website, they have stated they’ve “already completed the untethered jailbreak support for iOS 8.2,” which could mean that the TaiG team already has newer exploits needed to crack iOS 8.2. Of course, TaiG won’t disclose these exploits until the jailbreak is released, but it gives us hope.
This is certainly good news, as Apple patched up the jailbreak exploits when it released iOS 8.1.3, and it was up in the air as far as when a new jailbreak would arrive, especially with iOS 8.2 and iOS 8.3 releasing.
While you wait for the iOS 8.3 jailbreak to release, it might be a good idea to prepare your iPhone or iPad for the jailbreak by backing up your device through iTunes, downloading the iOS 8.3 update (but not installing it, of course), and back up your jailbreak tweaks using PkgBackup, which is available through Cydia.
Whatever you do, you don’t want to update over-the-air. Instead, plug your device into your computer and do it through iTunes. The reason for this is because past jailbreaks haven’t worked all too well when installing on a device that was updated over-the-air. Because of this, it’s best to update through iTunes and you’ll likely come out of it without any problems.
In the end, when an iOS 8.3 jailbreak does release, be sure to set aside at least an hour to jailbreak your iPhone or iPad. M0st of that time will be dedicated to downloading iOS 8.3 alone, while the actual jailbreaking process shouldn’t take too long — maybe 10 minutes tops, depending on the method used by the dev team.