Talk:Jailbreak

Error
Actually, I believe redsn0w (normal version) still loads a 2.1.1 iBoot & uses the arm7_go exploit to bootstrap the ramdisk that flashes the NOR, including an LLB with the 24kpwn exploit. Can someone confirm this? --Cool name 01:33, 27 July 2009 (UTC)

limera1n/greenpois0n
We should really try to get a name for the exploit or find a way to add it to exploits used post 2.0 --JakeAnthraX 05:13, 30 October 2010 (UTC)
 * Apparenttly, limera1n uses SHAtter as it is unmatchable. Also google it --Balloonhead66 05:15, 30 October 2010 (UTC)
 * SHAtter was not used and was saved. This is the iPhone wiki, usually people come here before googling and after all it should be here. --JakeAnthraX 05:20, 30 October 2010 (UTC)
 * the exploit is used differently on both jailbreaks on limera1n it creates a command called geohot then reboots to recovery mode and boots a ramdisk however on greenpois0n it injects IBSS and then uses the exploit to inject a pwnd IBEC in the description of shatter it did say it rebooted --liamchat 11:31, 30 October 2010 (UTC)
 * [SHAtter] was saved, [greenpois0n] uses the same exploit as [limera1n]. Also can someone stem the flow of crap coming from liamchat? It's getting annoying now. --GreySyntax 11:45, 30 October 2010 (UTC)

"Exploits which are used in order to jailbreak 2.x?"
The exploits used for jailbreaking iOS 1.x are broken down by firmware version. I'd like to accomplish the same thing for the 2.0 and onward section, since it's formatted much differently. But then I thought to myself, "This is going to be a huge revision that may receive sharp criticism. Let me make a talk page entry for this." So that's what I did…
 * So, in other words, would it be fine if the "Exploits which are used in order to jailbreak 2.0+" section was changed to something similar to the "Exploits which are used in order to jailbreak 1.x" section? -- Dialexio 02:16, 11 July 2011 (UTC)
 * Sounds like a good idea to me. Wouldn't it be easier to also separate them by major revisions? Like have a 2.X section, a 3.X section, a 4.X section, and soon to be 5.X? --JakeAnthraX 02:27, 11 July 2011 (UTC)
 * Of course! I was planning to do that, too. :P -- Dialexio 02:31, 11 July 2011 (UTC)

4.3.5 / 4.2.10
I've changed references to 0.9.8b3 to 0.9.8b7 for 4.3.5 tethered jailbreaks (see latest iPhone Dev rs iOS5beta posting). Should the Main Page be changed to reflect that an official jailbreak is available? Or will this only be changed on release of an untethered exploit being made available? Also fixed an error in which a reference to 0.9.6rc18 was existent with a question mark. Now changed to the accurate version of rs beta that needs to be used for 4.3.4 on that device. I've left 0.9.8b3 for 4.3.4 simply because that was the first release supporting it. Hope this is okay. blackthund3r 04:57, 31 August 2011 (MDT)
 * Actually it should list the lowest and highest version number that supports the listed firmware version, not just the latest. That's why all other pre 4.3.3 versions for redsn0w have ranges. -- http 00:57, 1 September 2011 (MDT)

3GS separation
From a jailbreak point of view, the 3GS with old and new bootrom are totally different devices. Can we separate that into two tables? -- http 12:48, 14 December 2011 (MST)

5.x PwnageTool bundles
The list says there are PwnageTool custom bundles for 5.0 for iPad and iPhone 4 (GSM) available. Is that correct? -- http 05:06, 19 December 2011 (MST)
 * see pwnbundles.com --Zmaster 06:45, 19 December 2011 (MST)
 * That site doesn't list any bundle for iOS 5.0, while this page says iOS 5.0 can be jailbroken with PwnageTool and a custom bundle. Is this just meant theoretical or what? -- http 10:32, 19 December 2011 (MST)

Clutter
Some of the tables (notably the iPhone 3GS section) are beginning to appear crammed. I think we could break up the tables a little more, based on firmware versions, to alleviate this issue. Thoughts? -- Dialexio 18:51, 28 December 2011 (MST)
 * What about dropping the table all together:

== iPhone == * 1.0.0 ** iBrickr *** Untethered: 0.5-0.91
 * or

== iPhone == * 1.0.0 ** iBrickr (Untethered): 0.5-0.91
 * --Cole Johnson 19:00, 28 December 2011 (MST)
 * Sounds good to me. Unless somebody wants tables, I'll switch over to this proposed format sometime around the weekend. -- Dialexio 21:08, 28 December 2011 (MST)
 * There is one more that I would like better: the first option but list all versions:

== iPhone == * 1.0.0 ** iBrickr *** 0.5 (Untethered) *** 0.6 (Untethered) ...
 * Its a bigger job, but it is better IMO --Cole Johnson 22:42, 28 December 2011 (MST)
 * One more (the tools area is listed like list option three, but w/o the link. The link is on the second column. The "5.0.1" can be like ): File:JB Option.png --Cole Johnson 22:47, 28 December 2011 (MST)
 * I do like the tables and I don't see a big need to change anything (except updating). A list won't bring much advantage and just increase page size. But the last proposed version of Balloonhead, a table that lists all tools in their versions for each firmware (still per device) wouldn't be bad if you want to change something. Please see also my request above about separating devices for old/new bootrom. --http 02:59, 29 December 2011 (MST)
 * It will make it vertical instead of horizontal (which is better) and it would allow someone to link to the firmware version with the ToC if we make the version number a header (see above comment). I can do it later today. --Cole Johnson 12:01, 29 December 2011 (MST)
 * I would actually like to see the new table format on Firmware and Beta Firmware --Cole Johnson 16:08, 29 December 2011 (MST)

Absinthe
For all entries of Absinthe it is stated that Absinthe 2.0/2.0.1 jailbreaks iOS 5.0.1, however Absinthe 2.0.* jailbreaks only 5.1.1. In order to jailbreak 5.0.1, one must use Absinthe 0.4. The official website states this cleary and keeps both 0.4 and 2.0.* available. I'll refrain from making this edit myself because I am not that friendly of wiki-like tables and might break something else :D --Luxiel 06:16, 30 May 2012 (MDT)
 * You're absolutely right. To edit the tables, feel free to try. There's a preview button; that way you can't break anything. If nobody updates this soon, I'll edit it. Thanks for reporting. --http 13:45, 30 May 2012 (MDT)
 * My bad… I kinda went by what I saw inside Absinthe.app. I'll work on changing the tables accordingly. -- Dialexio 15:11, 30 May 2012 (MDT)
 * …OK, I just tried it out twice, and Absinthe 2.0.4 was able to successfully jailbreak my iPod touch 4G on iOS 5.0.1. It may be that Absinthe 0.4 is more recommended for jailbreaking iOS 5.0.1 (albeit only on the iPad 2 and iPhone 4S), but 2.0.4 seems to be perfectly capable of jailbreaking 5.0.1 and 5.1.1. -- Dialexio 16:18, 30 May 2012 (MDT)
 * I didn't actually try to jailbreak a 5.0.1 with the new versions, as Chronic Team states on the Absinthe.exe that it jailbreakes 5.1.1 and the website points us to use 0.4 for 5.0.1, but if it works, it works :D --Luxiel 13:30, 31 May 2012 (MDT)

Bootrom exploits
Should we really list/repeat the limera1n and other bootrom exploits for every iOS version here? --http 14:58, 25 October 2012 (MDT)

redsn0w versions
In the jailbreak charts, we are listing the redsn0w-versions that work with this device/iOS version. That's fine. But in order to avoid updating the charts for every minor redsn0w release, I suggest that we just leave the starting version, like "0.9.15b1-" to indicate that support was added then. Of course, if redsn0w no longer supports that iOS build on the affected device, we have to add the end version too, like it is now. And also if the tether-status changes. The main problem right now is not even a lot of updates here just for minor redsn0w changes, but also if we forget to update this. For example if we list it as compatible with versions "0.9.102-0.9.117" and not we're at version "0.9.135", then nobody knows if support stopped at version "0.9.117" or if just the list didn't get updated. --http 13:22, 4 November 2012 (MST)