New speculation suggests XinaA15 jailbreak may be discontinued as Fugu15 Max progress continues

The XinaA15 jailbreak by Zhu Xinlang (@xina520) for arm64e devices (A12+) running iOS & iPadOS 15.0-15.1.1 has been available as a beta to the public since the start of December 2022. It became public after an internal beta was leaked, prompting Xinlang to essentially throw both arms in the air and just begin seeding public betas instead of trying to keep it under wraps.

XinaA15 icon.

Since then, XinaA15 has received a bevy of updates improving the stability of the jailbreak and attempting to make it more compatible with popular packages. But as developer Lars Fröder (@opa334) continues to make astonishing progress on Fugu15 Max (the working name for a jailbreak based on Linus Henze’s Fugu15 jailbreak for arm64e devices running iOS & iPadOS 15.0-15.4.1), the need for a second jailbreak tool in the form of XinaA15 seems increasingly unnecessary, especially given all the caveats.

The above truth didn’t go unnoticed. In an announcement shared in the XinaA15 Discord server this Friday afternoon, there was talk about speculation that Xinlang may stop development of XinaA15 on the grounds that Fugu15 Max was progressing more quickly.

Discontinuation of XinaA15 announcement.

Loosely translated, the speculation came in the form of the quoted excerpt below:

After learning that the Fugu15 Max jailbreak has been widely spread, Zhu Xinlang, the developer of the XinaA15 jailbreak, notified in the internal test group that everyone should transfer to Fugu15! … I may not update it anymore. Fugu15 is progressing well, and I don’t think there is any need to get another one.

The quote allegedly comes from by way of the owner of @HUC_hbs, a Twitter account known for announcing previous XinaA15 jailbreak updates and sharing download links via Twitter. Not much is known about this account except that it’s followed by several high-profile members of the jailbreak community. The bio of this account reads, “Mysterious team, dedicated to prison break tools to provide effective signature installation.”

So what does all this mean? The announcement in the XinaA15 Discord channel is clear: since XinaA15 may not receive further updates, existing XinaA15 users are recommended to continue using it until Fugu15 Max is completed and officially out of public beta and upgraded to public release status. XinaA15 is currently more stable than the Fugu15 Max public beta, but Fugu15 Max is expected to become more stable in time.

Once this happens, users should consider making the jump to the public release of Fugu15 Max, which is likely to be named something different at the time of release.

Another perk of Fugu15 Max that’s worth mentioning is that it supports iOS & iPadOS 15.0-15.4.1 on arm6e devices, compared to only iOS & iPadOS 15.0-15.1.1 on arm64e devices as supported by XinaA15. This means that Fugu15 Max has the potential to reach and be useful to more people, which likely contributed to Xinlang’s tough decision to pull back after months’ worth of progress.

As for the XinaA15 Discord server, it’s not going anywhere currently. The admins have said that the server will remain active for users to use and discuss in for at least another month before the team decides if the server should be rebranded to something different. Since the situation is a developing one, more will be known in the coming weeks.

While absolutely none of this has been publicly confirmed by Xinlang themselves, that’s not too surprising given the fact that Xinlang tends to be publicly silent, even when releasing XinaA15 updates. In many cases, those updates had been released without change logs, leaving users with no way of knowing what was new until someone shared it.

It will be interesting to see what happens, especially amid this developing situation. Interested users can stay informed by joining the XinaA15 Discord server and following iDB as we monitor future updates to the status of XinaA15.

Are you planning to continue using XinaA15, or will you eventually transition over to Fugu15 Max for your iOS or iPadOS 15.0-15.4.1 arm64e (A12+) device? Let us know in the comments section down below.