Pinned Tweet
Dopamine 3.0 (by @opa334dev) has released, supporting all devices up to 17.3.1 and A13 and lower devices on 17.4-18.7.1/26.0.x.
Download: ellekit.space/dopamine
Guide (15.0-16.6.1/17.0): ios.cfw.guide/installing-dop…
Guide (16.7-16.7.16/17.0.1-18.7.1/26.0.x): ios.cfw.guide/installing-dop…
Download: ellekit.space/dopamine
Guide (15.0-16.6.1/17.0): ios.cfw.guide/installing-dop…
Guide (16.7-16.7.16/17.0.1-18.7.1/26.0.x): ios.cfw.guide/installing-dop…
89
180
966
106,743
Michael retweeted
I’m just going to put this out for future reference.
If something (for modern) is not posted here, there’s a few reasons why something might not be posted here:
1. I legitimately haven’t seen it (assume I have though)
2. It’s from an individual who has been provably incompetent before
3. It’s something that I do not have high confidence will have anything of value come from it
4. It’s just someone wanting attention/clout
5. It’s not something that is meaningfully relevant for anything
If something (for modern) is not posted here, there’s a few reasons why something might not be posted here:
1. I legitimately haven’t seen it (assume I have though)
2. It’s from an individual who has been provably incompetent before
3. It’s something that I do not have high confidence will have anything of value come from it
4. It’s just someone wanting attention/clout
5. It’s not something that is meaningfully relevant for anything
5
7
75
11,109
Here is a mega-post of everything about the latest updates from today (+ the iPad mini (A20 Pro))
First, as to iOS/iPadOS 27.2 and iOS/iPadOS 26.7.2: These versions are believed to have patched the bugs in the chain that Calif showed off, as well as the likely SPTM bug (which was patched in 27.2b3).
As a result:
- If you’re on 27.2/26.7.2 already: restore to 27.1 (Duo)/27.0.1 (non-EoL)/26.7.1 (EoL)
- If you have an iPhone Duo: stay on 27.1
- If you have an iPhone 18 Pro/18 Pro Max: restore to 27.0.1 if you‘re on 27.0, otherwise stay on 27.0.1
- If you’re currently on a 27.0 beta: restore to 27.0.1
- If you have any other device: stay on your current version and wait to see what happens (the aforementioned 90 day delayed ota timer starts today for those on 26.x and lower, so you have until then to decide to update or not)
Next, as to iOS/iPadOS 18.7.11: There are some CVE’s here, but nothing provably relevant to the above was patched (kernel version was also unchanged between 18.7.10/18.7.11).
Based on that, if you have a device that hit EoL on 18.x, I wouldn’t update to 18.7.11, but - compared to the other updates - this does not appear to be as significant.
Additionally, for checkm8 devices: palera1n works on iPadOS 18.7.11 (iPad 7th Generation) and tvOS 26.6.1 (Apple TV HD and Apple TV 4K 1st Generation).
Lastly, as to the iPad mini (A20 Pro): I’ll leave my thoughts on the iPad itself as a reply to this. However, there’s a slightly interesting thing about this that makes its inclusion in this main post relevant.
When the updates came out today, we also got a delta OTA to a 27.2 build for the new iPad mini.
Delta OTA’s - for reference - are smaller OTA’s that usually only include baseline stuff and the things that changed between a base version and the target version (this is how an OTA from 27.0 -> 27.0.1 is smaller than an OTA for 26.0 -> 27.0.1, as an example).
The interesting thing about this delta OTA? The delta is from 27.0 (24A7427).
The implication of this is - of course - the possibility that the preinstalled version for the new iPad mini will be vulnerable to all the relevant bugs patched in 27.2.
My recommendation? If you’re getting a new iPad mini and care about any of this: activate with a computer, don’t use a backup, and setup the device before connecting to any form of internet.
First, as to iOS/iPadOS 27.2 and iOS/iPadOS 26.7.2: These versions are believed to have patched the bugs in the chain that Calif showed off, as well as the likely SPTM bug (which was patched in 27.2b3).
As a result:
- If you’re on 27.2/26.7.2 already: restore to 27.1 (Duo)/27.0.1 (non-EoL)/26.7.1 (EoL)
- If you have an iPhone Duo: stay on 27.1
- If you have an iPhone 18 Pro/18 Pro Max: restore to 27.0.1 if you‘re on 27.0, otherwise stay on 27.0.1
- If you’re currently on a 27.0 beta: restore to 27.0.1
- If you have any other device: stay on your current version and wait to see what happens (the aforementioned 90 day delayed ota timer starts today for those on 26.x and lower, so you have until then to decide to update or not)
Next, as to iOS/iPadOS 18.7.11: There are some CVE’s here, but nothing provably relevant to the above was patched (kernel version was also unchanged between 18.7.10/18.7.11).
Based on that, if you have a device that hit EoL on 18.x, I wouldn’t update to 18.7.11, but - compared to the other updates - this does not appear to be as significant.
Additionally, for checkm8 devices: palera1n works on iPadOS 18.7.11 (iPad 7th Generation) and tvOS 26.6.1 (Apple TV HD and Apple TV 4K 1st Generation).
Lastly, as to the iPad mini (A20 Pro): I’ll leave my thoughts on the iPad itself as a reply to this. However, there’s a slightly interesting thing about this that makes its inclusion in this main post relevant.
When the updates came out today, we also got a delta OTA to a 27.2 build for the new iPad mini.
Delta OTA’s - for reference - are smaller OTA’s that usually only include baseline stuff and the things that changed between a base version and the target version (this is how an OTA from 27.0 -> 27.0.1 is smaller than an OTA for 26.0 -> 27.0.1, as an example).
The interesting thing about this delta OTA? The delta is from 27.0 (24A7427).
The implication of this is - of course - the possibility that the preinstalled version for the new iPad mini will be vulnerable to all the relevant bugs patched in 27.2.
My recommendation? If you’re getting a new iPad mini and care about any of this: activate with a computer, don’t use a backup, and setup the device before connecting to any form of internet.
10
20
189
41,950
As to my thoughts on the new iPad mini from a practical perspective: they’re simple:
- It’s not worth the $700 base price
- It’s good from a longevity perspective that it has an A20 Pro (probably also means it will be another 2-3 years before it gets updated)
- The iPad mini also makes the iPad Air look absolutely terrible right now (imo the next iPad Air should get an OLED display, but that also means it’ll probably be even more expensive which will just make the lineup even worse)
- The iPad lineup as a whole is a complete mess and I honestly think it’s not worth getting a brand new iPad at all right now (used/discount market could be interesting though)
- It’s not worth the $700 base price
- It’s good from a longevity perspective that it has an A20 Pro (probably also means it will be another 2-3 years before it gets updated)
- The iPad mini also makes the iPad Air look absolutely terrible right now (imo the next iPad Air should get an OLED display, but that also means it’ll probably be even more expensive which will just make the lineup even worse)
- The iPad lineup as a whole is a complete mess and I honestly think it’s not worth getting a brand new iPad at all right now (used/discount market could be interesting though)
0
0
12
4,160
Michael retweeted
You've definitely heard of #DarkSword. @imnotclarity is now walking us through the inner workings of some key elements of this exploit chain and re-implementation of the DarkSword kernel exploit supporting iOS 26.0.1. #TheSAS2026
1
7
44
5,282
Michael retweeted
Alfie CG (@alfiecg_dev) dissects the SPTM bypass used in Coruna (it also exploits AGX and uses more obscure hardware registers 👀) #TheSAS2026
0
20
173
9,619
Something else I've only thought about recently that I'll add to this: If you're considering getting an iPhone 18 Pro Max specifically (all other iPhones are fine), I would highly recommend getting one sooner rather than later.
Due to Apple/AT&T somehow managing to screw stuff up with 27.0 for the 18 Pro Max in the US (I have absolutely no idea how but they did), if you get a brand new 18 Pro Max *and it comes on 27.0* (27.0.1 is fine), you will likely get a forced update to whatever latest is when you try to activate it.
Right now, this is a non-issue because latest for the 18 Pro Max is 27.0.1. The problem is more if you get an 18 Pro Max on 27.0 in like a month from now when 27.0.1 is no longer latest.
Due to Apple/AT&T somehow managing to screw stuff up with 27.0 for the 18 Pro Max in the US (I have absolutely no idea how but they did), if you get a brand new 18 Pro Max *and it comes on 27.0* (27.0.1 is fine), you will likely get a forced update to whatever latest is when you try to activate it.
Right now, this is a non-issue because latest for the 18 Pro Max is 27.0.1. The problem is more if you get an 18 Pro Max on 27.0 in like a month from now when 27.0.1 is no longer latest.
If you’re on any iOS 27.x beta: please restore to 26.6.1 RC (heavily preferred since it has DelayOTA) or 27.0.1.
If you’re on an iPhone 18 Pro (Max): install 27.0.1, it patches some important issues for usability
If you’re on any other stable iOS release: *STAY WHERE YOU ARE!*
18
13
230
62,709
For those that aren't aware: 27.2 beta 3 did likely patch an SPTM Bypass.
The advice through everything has still been "stay and wait for stuff", and that hasn't changed in the slightest
However, as there's more "known" (for lack of a better term) about this (compared to the exact specifics of the Calif chain), I would say that - if you end up in a situation where you absolutely have to update - I would highly recommend avoiding anything past 27.0.1/27.2b2 (and probably 26.7.1 for AlternateSU)
The advice through everything has still been "stay and wait for stuff", and that hasn't changed in the slightest
However, as there's more "known" (for lack of a better term) about this (compared to the exact specifics of the Calif chain), I would say that - if you end up in a situation where you absolutely have to update - I would highly recommend avoiding anything past 27.0.1/27.2b2 (and probably 26.7.1 for AlternateSU)
16
35
203
22,178
For some more information, here's a post from opa on the elephant platform: infosec.exchange/@opa334/117456…
Additionally, it's worth noting that this bug type realistically probably doesn't matter for A12(X/Z) and A13 devices, as those devices now have momentarius.
Additionally, it's worth noting that this bug type realistically probably doesn't matter for A12(X/Z) and A13 devices, as those devices now have momentarius.
1
2
37
6,225
Michael retweeted
Finally got around to releasing Trigon for arm64e. Enjoy!
alfiecg.uk/2026/10/17/Tri…
alfiecg.uk/2026/10/17/Tri…
10
55
369
25,330
So this is indeed real - here’s a quick rundown on some simple things though:
- This does not involve that one TSS bug
- They’ve said something to the effect of “this will be released in due time” - I personally still think it’s many miles away, but I could ultimately be wrong on this
Now as to the question of “should I delay ota to 27.0.1?”, I would not for a multitude of reasons.
As I’ve mentioned before a couple of times, once you are on 27.x, delay ota’ing from that point on is effectively unviable (you need an MDM that supports a specific thing and most free ones don’t).
As a result, in the event the bugs are released or RE’d while vulnerable versions are still available in the delay ota window, you’ll still be able to delay ota to the optimal version one more time, provided you’re on 26.x or lower.
Some other smaller/related reasons to stay on older versions:
- There is no flat guarantee as to when the bugs will release or be RE’d (it could still be a very very long time ultimately) (technically there’s still the chance the bugs could never release or be RE’d in theory as well)
- It’s possible that a bug in this chain could have some issues/be unsupported for some devices (e.g. low reliability, only support newer SoC’s, etc.) - in this case, you’d still want to be on a lower version to have access to another bug (whether already existing or one that comes in the future).
- Tweak compatibility is probably better on lower versions (though tbf 26 is not exactly worse overall than 18 at the moment)
Overall, I’m interested to see where this leads, but I think even if this leads to something patience is the best move for now.
- This does not involve that one TSS bug
- They’ve said something to the effect of “this will be released in due time” - I personally still think it’s many miles away, but I could ultimately be wrong on this
Now as to the question of “should I delay ota to 27.0.1?”, I would not for a multitude of reasons.
As I’ve mentioned before a couple of times, once you are on 27.x, delay ota’ing from that point on is effectively unviable (you need an MDM that supports a specific thing and most free ones don’t).
As a result, in the event the bugs are released or RE’d while vulnerable versions are still available in the delay ota window, you’ll still be able to delay ota to the optimal version one more time, provided you’re on 26.x or lower.
Some other smaller/related reasons to stay on older versions:
- There is no flat guarantee as to when the bugs will release or be RE’d (it could still be a very very long time ultimately) (technically there’s still the chance the bugs could never release or be RE’d in theory as well)
- It’s possible that a bug in this chain could have some issues/be unsupported for some devices (e.g. low reliability, only support newer SoC’s, etc.) - in this case, you’d still want to be on a lower version to have access to another bug (whether already existing or one that comes in the future).
- Tweak compatibility is probably better on lower versions (though tbf 26 is not exactly worse overall than 18 at the moment)
Overall, I’m interested to see where this leads, but I think even if this leads to something patience is the best move for now.
16
27
327
27,653
Here’s some quick thoughts on the untether bug as well (couldn’t figure out how to fit it in the main part tbf).
It honestly seems to be a somewhat mid untether bug overall, as it seems to run quite late (still BFU but well after the device hits lockscreen), and - as this was a pre-recorded demo for the untether - I’m inclined to think that there may be reliability issues as well with this bug.
The first problem already makes me think it’d be best reserved for something akin to u0+Fugu14 (where a jailbreak app would be persistently available and you wouldn‘t need to worry about signing), and the second potential part might make that an unviable path in general (there’s also nuance in terms of what the untether bug is that could have issues, but that’s not known yet).
We actually already have an untether bug for 15.x/16.x (FSUntether), but the ultimate problem with that bug is that it’s so late and relies on either TrollStore or a paid developer account, which ultimately made it generally unviable to use in any practical sense.
It honestly seems to be a somewhat mid untether bug overall, as it seems to run quite late (still BFU but well after the device hits lockscreen), and - as this was a pre-recorded demo for the untether - I’m inclined to think that there may be reliability issues as well with this bug.
The first problem already makes me think it’d be best reserved for something akin to u0+Fugu14 (where a jailbreak app would be persistently available and you wouldn‘t need to worry about signing), and the second potential part might make that an unviable path in general (there’s also nuance in terms of what the untether bug is that could have issues, but that’s not known yet).
We actually already have an untether bug for 15.x/16.x (FSUntether), but the ultimate problem with that bug is that it’s so late and relies on either TrollStore or a paid developer account, which ultimately made it generally unviable to use in any practical sense.
1
1
21
3,470
Thoughts on new Apple announcements today:
- HomePod mini 2: what is the actual point (also HomePod mini is now 50% more expensive than before the original price increase)
- Apple TV 4K (4th Generation): can someone explain the value of Siri AI on a TV box thing ok thanks (price has more than doubled in the past year my god)
- HomeView: I will reserve my thoughts on this until it actually releases
- Apple Home Collection: It’s LG so it’s bad immediately
- HomePod mini 2: what is the actual point (also HomePod mini is now 50% more expensive than before the original price increase)
- Apple TV 4K (4th Generation): can someone explain the value of Siri AI on a TV box thing ok thanks (price has more than doubled in the past year my god)
- HomeView: I will reserve my thoughts on this until it actually releases
- Apple Home Collection: It’s LG so it’s bad immediately
5
5
110
31,000
At least iPhone Duo pre-orders are this week I guess? I’m not buying one because it’s $2000… but they’re this week at least.
0
0
4
3,078
Michael retweeted
#POC2026 ☄️☄️
Clarity(@imnotclarity) & Staturnz(@staturnzdev) - "Momentarius: A Momentary Solution to a Permanent Problem"
Clarity(@imnotclarity) & Staturnz(@staturnzdev) - "Momentarius: A Momentary Solution to a Permanent Problem"
0
4
13
2,516
There is an unc0ver update (8.1.0) that has just released - almost 5 years after 8.0.2 - with support for 12.5.6-12.5.8
While I personally recommend Amethyst(+TNSv2) over anything else for those, I still think this is a net positive overall.
Download: unc0ver.dev
While I personally recommend Amethyst(+TNSv2) over anything else for those, I still think this is a net positive overall.
Download: unc0ver.dev
15
34
259
40,470
For the first time in almost 11 years, there is now an end-user untethered jailbreak for a newer major iOS version (32-bit iOS 10.x). procyon untether is available through Socket 1.3.
Download: github.com/staturnzz/sock…
Guide: ios.cfw.guide/installing-soc…
Download: github.com/staturnzz/sock…
Guide: ios.cfw.guide/installing-soc…
procyon: untethered re-jailbreak for iOS 10.0-10.3.4 (32bit)
github.com/staturnzz/proc…
4
28
233
26,963
Notes:
- If you have an iPad 4th Generation on 10.3.2 to 10.3.4: There is an ~7% chance that the device will not successfully boot. If this happens, you will need to force reboot the device or use Legacy iOS Kit’s “Reboot Device” option.
- As a result of the above, the untether is not enabled by default for the iPad 4th Generation on 10.3.2 to 10.3.4 (It can be enabled in Socket's settings, however)
- On all other combinations, the untether is installed by default when jailbreaking with Socket 1.3
- Coolbooter Untetherer does not work (as such, it is conflicted with the procyon untether package, and will not install) (normal Coolbooter works fine)
- If you have an iPad 4th Generation on 10.3.2 to 10.3.4: There is an ~7% chance that the device will not successfully boot. If this happens, you will need to force reboot the device or use Legacy iOS Kit’s “Reboot Device” option.
- As a result of the above, the untether is not enabled by default for the iPad 4th Generation on 10.3.2 to 10.3.4 (It can be enabled in Socket's settings, however)
- On all other combinations, the untether is installed by default when jailbreaking with Socket 1.3
- Coolbooter Untetherer does not work (as such, it is conflicted with the procyon untether package, and will not install) (normal Coolbooter works fine)
0
1
14
3,099
This appears to be confirmed with the enterprise notes for iOS 27.
As a result: reasonable means of doing delayed OTA stuff (without jb) is dead with iOS/iPadOS 27. That being said, if you stay on 26 or lower, you’ll continue to have one last opportunity to utilize it normally.
As a result: reasonable means of doing delayed OTA stuff (without jb) is dead with iOS/iPadOS 27. That being said, if you stay on 26 or lower, you’ll continue to have one last opportunity to utilize it normally.
As we approach WWDC 2026 and iOS/iPadOS 27, it’s time to finally talk about something of future importance as we get to 27.x
Assuming nothing changes, Delayed OTA’s will no longer work as they currently exist, and will generally be impractical to actually utilize on 27 and later.
How do we know this? Apple’s own iOS/iPadOS 26 enterprise notes - available at support.apple.com/en-us/125073
Specifically, as follows (see the bottom 26.0 section):
”Software update management using mobile device management commands, restrictions, the com[dot]apple[dot]SoftwareUpdate payload, and queries is deprecated and will be removed next year. Going forward, software updates can be managed and enforced using only declarative software update management”.
(To clarify, the system that is actively used that people are familiar with is a restrictions profile with a certain number of days set as the restriction).
Now, for anyone wondering ”what is declarative software update management?”, it’s a newer thing that - on top of being very different (though obviously still supporting 90 day delays for businesses, obviously) is only available with an MDM, and not just traditional supervision.
To not go on a long long tangent, MDM’s are generally a paid thing, usually meant for stuff like schools/businesses and whatever else. While there are a very small handful of free options, they are - to put it mildly - extremely trash (and some of them may still not even support this new update system).
There is a potential lifeline here though (though we don’t know for certain yet, and we won’t know fully until 27.0.1 or whatever): this change probably only will apply once you’re actively on 27.x or later.
What this potentially means is that, as long as:
- You are still on 26.x (or lower)
- OTA’s to a major version are still supported from your current version (minimum to OTA to 16+ is iOS/iPadOS 13, for reference)
you’ll likely have one final opportunity to use delayed OTA’s in a reasonable manner once 27+ is the only available option.
3
17
120
32,023
