Talk:Jailbreak/2012

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)

Order of jailbreak tools.
I was looking at this today and thought that on different devices that it gets confusing that the order of tools is different. Would it be better if the tools were sorted in alphabetical order? --iAdam1n (talk) 11:07, 4 December 2012 (MST)
 * I don't care. If it bothers you so much, feel free to sort them. --http 13:09, 14 December 2012 (MST)
 * Okay. Will do. --iAdam1n (talk) 13:12, 14 December 2012 (MST)

Version number of tool.
Would it not be better to just say yes or no? I mean most people will use the latest version to jailbreak even old firmwares. --iAdam1n (talk) 11:24, 4 December 2012 (MST)
 * Because sometimes the latest one doesn't work. Take sn0wbreeze: before 2.9, you would need a specific version as the latest didn't include the bundles for old firmwares. --5urd 11:32, 4 December 2012 (MST)
 * Ok. Was hoping to change it to yes, no or tethered but that is a good point. --iAdam1n (talk) 11:34, 4 December 2012 (MST)
 * That's exactly the problem. Not all tools in their latest version work with old firmwares, so you have to take an older version in order to use it. But for tools that do work in their latest version we might want to remove the latest version and just list since which version it is supported, for example firmware x is supported with "redsn0w 0.99.1023-" meaning since that version of redsn0w. That way we don't have to update everything if a new redsn0w version comes out. And when (for any reason) firmware x is no longer supported with the newest redsn0w, we could replace it with "redsn0w 0.99.1023-0.99.2039" (when redsn0w 0.99.2040 is the version no longer supporting it). -- http 17:59, 4 December 2012 (MST)
 * I see. Please see my question above this one. --iAdam1n (talk) 04:29, 5 December 2012 (MST)

Tethered Jailbreak breaks camera
Has anybody noticed that the 6.0.1 tethered jailbreak breaks the camera? --Haifisch (talk) 20:25, 24 December 2012 (UTC)
 * What device? Have you tried a fresh restore + jailbreak (restore, set up as new, jailbreak) as it could be your system having a corrupted binary. If that didn't/doesn't work, did/can you contact p0sixninja? --5urd (talk) 20:52, 24 December 2012 (UTC)
 * Works ok here. --iAdam1n (talk) 21:02, 24 December 2012 (UTC)
 * Hmm seems to be my iPhone 4 (6.0.1) then... Let me see if the binary is OK --Haifisch (talk) 00:19, 25 December 2012 (UTC)
 * Errm… This has nothing to do with the front page. I'll let it slide though. (For the record, my iPhone 4 CDMA's cameras function properly.) -- Dialexio ( talk ) 02:14, 25 December 2012 (UTC)
 * I wasn't sure where to put it (I meant to put it on the community portal actually, made a mistake) What have you installed? --Haifisch (talk) 03:17, 25 December 2012 (UTC)
 * Well, you could have asked something like "Should it be noted that the 6.0.1 jailbreak messes with camera functionality?" on the Jailbreak talk page. ;P But I digress. I have AntiTint, BlurriedNCBackground, f.lux, iCleaner, MultiStorey, My3G, PrivaCy, Protect My Privacy, ScrollingBoard, and TetherMe installed. -- Dialexio ( talk ) 03:22, 25 December 2012 (UTC)
 * is there somewhere were i can note this? --Haifisch (talk) 21:38, 25 December 2012 (UTC)