|
The iPhone Wiki is no longer updated. Visit this article on The Apple Wiki for current information. |
Difference between revisions of "Failbreak"
m (Changed to references.) |
m |
||
| (5 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
{{lowercase}} |
{{lowercase}} |
||
| − | The term "'''failbreak'''" |
+ | The term "'''failbreak'''" is used to mean one or both of two things: an incomplete or otherwise flawed jailbreak that cannot run [[Cydia Substrate]] properly, or a jailbreak that cannot be released to the public for some reason (whether or not that jailbreak is complete). Some "failbreaks" are both incomplete and cannot be released to the public. Sometimes people also call [[Scam Sites|fake jailbreaks]] "failbreaks". Since this word has multiple possible meanings, it's confusing to try to use it in conversation, so it's best to avoid it. |
saurik has said that "the term was actually first used years ago by chpwn on a released jailbreak as there was something wrong with it that caused Substrate to only work in some processes; I was then later using it with regards to jailbreaks where the kernel patches didn't support the various memory protection changes required by C Substrate. I provide a tool called 'vmcheck' that people developing jailbreaks use to 'unit test' their patches, and when it fails... well, that's a 'failbreak'."<ref>http://www.reddit.com/r/jailbreak/comments/12kx0q/chpwn_and_phoenixdev_already_have_a_failbreak_for/c6w4zk7</ref> |
saurik has said that "the term was actually first used years ago by chpwn on a released jailbreak as there was something wrong with it that caused Substrate to only work in some processes; I was then later using it with regards to jailbreaks where the kernel patches didn't support the various memory protection changes required by C Substrate. I provide a tool called 'vmcheck' that people developing jailbreaks use to 'unit test' their patches, and when it fails... well, that's a 'failbreak'."<ref>http://www.reddit.com/r/jailbreak/comments/12kx0q/chpwn_and_phoenixdev_already_have_a_failbreak_for/c6w4zk7</ref> |
||
| − | [[User:chpwn|chpwn]] showed a screenshot of his new [[iPhone 5]] running [[Cydia.app|Cydia]] shortly after its launch on [[Timeline| |
+ | This term came up again when [[User:chpwn|chpwn]] showed a screenshot of his new [[iPhone 5]] running [[Cydia.app|Cydia]] shortly after its launch on [[Timeline#September_10|{{date|2012|09|19}}]]<ref>https://twitter.com/chpwn/status/249249128926806016</ref>. He [https://twitter.com/chpwn/status/252166757643583489 explained this] as "the “failbreak” is for jailbreak developers (e.g. @iphone_dev, @chronicdevteam, etc)." On {{date|2012|10|19}}, [[User:Planetbeing|planetbeing]] tweeted that he upgraded the "failbreak" with a [[exploit|kernel exploit]] so that tweaks actually work on the [[iPhone 5]], to make it "almost a full tethered jailbreak."<ref>https://twitter.com/planetbeing/status/259059248795881472</ref> |
| + | |||
| + | In {{date|2015|03}}, [https://twitter.com/chpwn/status/577801639169560576 chpwn said] "I open sourced the code for the old ‘failbreak’ from around iOS 6.0. (The exploits involved are all fixed now.) http://github.com/grp/amfi_interpose" |
||
== Failbreaks == |
== Failbreaks == |
||
* iOS 4.2.1 ([[Jailbreak Monte]]) |
* iOS 4.2.1 ([[Jailbreak Monte]]) |
||
| − | ** Access to iOS 4. |
+ | ** Access to iOS 4.2 beta 3 for device |
* iOS 6.x on [[S5L8940|A5]], [[S5L8942|A5 Rev A]] [[S5L8942|A5X]], [[S5L8950|A6]] and [[S5L8955|A6X]] |
* iOS 6.x on [[S5L8940|A5]], [[S5L8942|A5 Rev A]] [[S5L8942|A5X]], [[S5L8950|A6]] and [[S5L8955|A6X]] |
||
** [[Apple Developer]] account required |
** [[Apple Developer]] account required |
||
| Line 15: | Line 17: | ||
== References == |
== References == |
||
<references/> |
<references/> |
||
| + | |||
| + | [[Category:Jailbreaking]] |
||
Latest revision as of 12:47, 17 September 2021
The term "failbreak" is used to mean one or both of two things: an incomplete or otherwise flawed jailbreak that cannot run Cydia Substrate properly, or a jailbreak that cannot be released to the public for some reason (whether or not that jailbreak is complete). Some "failbreaks" are both incomplete and cannot be released to the public. Sometimes people also call fake jailbreaks "failbreaks". Since this word has multiple possible meanings, it's confusing to try to use it in conversation, so it's best to avoid it.
saurik has said that "the term was actually first used years ago by chpwn on a released jailbreak as there was something wrong with it that caused Substrate to only work in some processes; I was then later using it with regards to jailbreaks where the kernel patches didn't support the various memory protection changes required by C Substrate. I provide a tool called 'vmcheck' that people developing jailbreaks use to 'unit test' their patches, and when it fails... well, that's a 'failbreak'."[1]
This term came up again when chpwn showed a screenshot of his new iPhone 5 running Cydia shortly after its launch on 19 September 2012[2]. He explained this as "the “failbreak” is for jailbreak developers (e.g. @iphone_dev, @chronicdevteam, etc)." On 19 October 2012, planetbeing tweeted that he upgraded the "failbreak" with a kernel exploit so that tweaks actually work on the iPhone 5, to make it "almost a full tethered jailbreak."[3]
In March 2015, chpwn said "I open sourced the code for the old ‘failbreak’ from around iOS 6.0. (The exploits involved are all fixed now.) http://github.com/grp/amfi_interpose"
Failbreaks
- iOS 4.2.1 (Jailbreak Monte)
- Access to iOS 4.2 beta 3 for device
- iOS 6.x on A5, A5 Rev A A5X, A6 and A6X
- Apple Developer account required
- Developers under NDA
