Pangu 8.4

The jailbreak community, along with the stock iOS family, is swarming with fresh developments every now and then. Right from the time we received the iOS 8.3 jailbreak first, there have been a lot of releases and updates. The iOS 8.3 jailbreak itself received quite a few updates and then the iOS 8.4 came out with the Apple Music, the Cupertino company’s take on music streaming. Update Sep 11th 2015 : Pangu Team is working on iOS 8.4.1 Pangu . Read in more details here .

Image : Pangu Jailbreak 8.4 Progress Update

pangu 8.4

Just a few hours later, PP [jailbreak link] and TaiG [ jailbreak link] both released jailbreaks for the new OS and we rejoiced again. The TaiG jailbreak already has received quite a few updates and the same has happened to Cydia. TaiG and PP have also had their share of accusations when TaiG accused PP of stealing its jailbreak. There is so much happening. But amidst all this humdrum, we really missed the Pangu Team, who have just disappeared from the whole jailbreak scenario.

Where Are They ?

The last we heard of the Pangu team was quite a few weeks ago when the iOS 9 was just freshly unveiled by Apple at its 2015 WWDC. Team Pangu was seen at the MOSEC conference this year and then, it just disappeared. After Apple unveiled the iOS 9, Pangu team had revealed that it was working on the iOS 8.3, and they also showed a preview of the same at the MOSEC. They had, however, not stated a release date, for obvious reasons that Apple might patch iOS 8.4 for the vulnerabilities. We all were expecting a Pangu 8.4 Jailbreak for the long-unjailbroken iOS 8.3, but what came instead was a really surprise.

Image : The very last Pangu release


Surprisingly enough, TaiG came out with the iOS 8.3 untethered jailbreak in the form of its TaiG 2.0 jailbreak tool. Many users, in the excitement of jailbreaking their iOS 8.3 devices, forgot all about Pangu and started praising TaiG for its talents. But dedicated followers of the jailbreaking community were under a real shock- why wasn’t the iOS 8.3 jailbreak released by Pangu ? What were they waiting for ? And how come TaiG, without any speculation, released an iOS 8.3 jailbreak in such a surprising manner ? The questions were left unanswered. We expected Pangu to release the jailbreak soon after the TaiG tool came out, but all we received was updates for the TaiG jailbreak and a TaiG jailbreak clone by PP.

We have TaiG and PP with 8.4 Jailbreak :

taig pp 8.4

We then hoped that we would hear from the Pangu team after the iOS 8.4 release, and that they would be the first to bring in the iOS 8.4 jailbreak. But we did not know that another major shock awaited us. Just an hour after the release of the iOS 8.4, PP released their untethered jailbreak for the firmware, but the jailbreak community was expecting this move from TaiG. Just a few hours later, TaiG too came out with its updated jailbreak tool to support iOS 8.4. We then got to know, from the accusations of TaiG, that PP had copied their jailbreak. But again, amidst all this hullabaloo, Pangu was nowhere to be seen, especially keeping in mind the fact that they had, at MOSEC, expressed their interest in releasing an iOS 8.4 jailbreak. Also, up till now, none of the jailbreak tools support Mac, so the users have to stick with Windows for jailbreaking, which many users find inconvenient.

Keen Jailbreak Team working on iOS 9 :

keen team ios 9

We all know that iOS 9 would be coming this fall and Team K33n (Keen) is working on the iOS 9 jailbreak with assistance from Pangu. Pangu has literally disappeared from the jailbreak scenario, so we can only expect Team Pangu to show some activity after the release of iOS 9 and its jailbreak. But if we again don’t hear anything from Pangu in fall, then it will be better to believe that Pangu has retired forever from the jailbreak scenario and we might well move on with the TaiG team.

Comment Below for the Pangu Team to Come Back

Keep up with the Pangu news by subscribing to our Newsletter and follow us on Facebook and Twitter.




Leave a Reply

Your email address will not be published. Required fields are marked *