Fourteen days after Calif rebooted an iPhone 18 Pro on a stage in Paris and watched the jailbreak come back on its own, the most common question in the jailbreak community is also the most misleading one. Why has Calif not published anything yet? The silence looks like a stall. It is not. It is the normal, deliberate gap between a private disclosure to Apple and a public writeup, and the clock that controls that gap is not Calif’s calendar. It is Apple’s signing server.
As of this morning, October 30, there is still no Calif writeup, no proof of concept code for the Paris chain, and no public tool for any iOS 27 version. That is the honest status, and it has not changed since the October 16 Hexacon demo. What has changed around it is everything that makes publication safer: Apple shipped the patch, researchers have had days to study it, and the downgrade window is now on borrowed time.
The October 30 check: still signed, still silent
The ONE Jailbreak signing status page, crawled on October 30 at 07:17 UTC (12:47 IST) with a dated update of October 29, still lists iOS 27.0.1 among the versions Apple is signing, alongside iOS 27.2, iOS 27.1 for the iPhone Duo, and iOS 26.7.2. That makes today day four after iOS 27.2 shipped on October 26. The same check found no new Calif post, no writeup, and no fresh demonstration on iOS 27.2 in the last 48 hours.
The usual cautions apply, and they matter more with each passing day. Signing is per device, not global, so a version listed as signed in general must still be signed for your exact model. A signing page is also a snapshot, not a promise. Apple has closed windows in the middle of a day before, with no announcement, and this page will simply flip from signed to unsigned when that happens.
Coordinated disclosure, in plain language
Coordinated disclosure is the deal researchers and vendors have worked out over years of painful experience. The researcher tells the vendor about the bugs privately, the vendor ships a fix, and only then does the researcher publish the details. The order matters. Publish the chain before the patch, and you hand a working exploit to everyone at once, including the scammers who are already selling fake iOS 27 jailbreak downloads.
Calif researcher Stefan Esser told German outlet Heise that the bugs behind the Paris demo had already been reported to Apple over the last few months, or were about to be reported, and that most were already fixed in the iOS 27.2 beta. Apple then shipped iOS 27.2 on October 26, and its security notes credit Calif on six fixes, with a total of 163 CVE fixes for iPhone and iPad. That is the first half of the disclosure deal, completed in public. The second half, Calif’s own writeup, is what everyone is waiting for.
Esser has also set expectations clearly, and they are worth repeating because they keep getting lost in social media retellings. Calif has said it has no plans for an end-user jailbreak tool. A proof of concept may come later. A writeup and research code are not a consumer app, and treating them as one is how readers end up installing malware.
Why the signing window is the real trigger
Here is the part of the story that gets the least attention. As long as Apple keeps signing iOS 27.0.1, any compatible iPhone can still be restored or downgraded to the version Calif jailbroke. Publishing the full exploit chain while that door is open would let anyone, including attackers, move a phone onto the vulnerable version and then use the chain. Once Apple stops signing 27.0.1, that downgrade path closes for everyone who has not saved SHSH2 blobs, and the risk of publishing drops sharply.
That logic is why ONE Jailbreak, in its report on the iOS 27.2 fixes, expressed hope that Calif will release a writeup once iOS 27.1 stops being signed. That is an outside outlet’s hope, not a promise from Calif, and Calif has given no date. But the reasoning behind it is sound, and it fits the timeline researchers are watching.
The tracker’s own FAQ puts the typical signing window at 7 to 14 days after a new release. Day four, where we are today, is neither early nor late. It means the window could close any day now, or it could run for several more days. Either way, the signing flip is the event most likely to precede, or at least accompany, any Calif publication, because it removes the easiest way back to the vulnerable version.
What a Calif writeup would contain, and what it would not
A writeup, when it arrives, would most likely name the vulnerabilities, explain how they link together into a chain, and possibly include proof of concept code for a research device. That would let independent researchers verify Calif’s work, confirm which of the iOS 27.2 fixes belong to the Paris chain, and settle whether any part of the chain survives on 27.2.
What it would not be, by Calif’s own account, is a tool you download, tap, and use. Turning research code into a reliable jailbreak for many models takes additional work: testing across devices, building a package manager environment, handling the boot process safely, and supporting users when things go wrong. That is community work, and it takes time even when the starting code is good.
The recent CryptSn0w release is a useful warning here. Researcher @0xjohnny open-sourced that earlier iOS 27 jailbreak project on October 22, and it was real code. It was also deliberately incomplete, and Apple had already killed the server-side bug it depended on, on October 9. Real code, published openly, that cannot jailbreak a new phone today. A Calif proof of concept could be far more complete, but CryptSn0w shows why code on a repository is not the same thing as a working jailbreak.
What to watch next, in order
First, the signing flip. When iOS 27.0.1, and iOS 27.1 for the Duo, move from signed to unsigned, the downgrade era for this chain ends for anyone without saved blobs. We will report that day when it happens, as we reported day three on October 29, when India’s CERT-In also rated the iOS 27.2 flaws high severity.
Second, a Calif post. The team’s own blog and social accounts are the only authoritative source for a writeup. Secondhand claims, reposted videos, and download sites are not, and any site offering an iOS 27 jailbreak download today is selling something that does not exist.
Third, independent patch analysis. Researchers compare the shipping iOS 27.2 build against iOS 27.0.1 to see exactly which code changed. No standalone patch-diff finding on the Calif chain had been published as of this morning’s check.
For most readers, the advice has not changed. Install iOS 27.2 and keep Automatic Updates on. For the narrow group still holding on 27.0.1 or 27.1 for a possible jailbreak, the trade is now clearer than it was on day one. You are waiting for a writeup Calif has promised only in the vague phrase “in due time,” for a tool Calif has said it will not build, on a version with publicly documented flaws now rated high severity by a national CERT. Saving SHSH2 blobs while the window holds costs nothing and keeps one option alive. Waiting without them, past the day Apple stops signing, closes that option for good.
