The iPhone Wiki is no longer updated. Visit this article on The Apple Wiki for current information. |
Difference between revisions of "Talk:Jailbreak"
m (→TLC) |
m |
||
Line 320: | Line 320: | ||
:::::::::::I have now started to use this design on the page. However, I think we should now discuss the markup for the tables. Take a look at the 7.x table. Should we use rowspan to combine evasi0n7 into one? Should we do this for Geeksn0w? Should we use rowspan to combine the tool versions? Should we use rowspan to combine the 7.0.1, 2, 3 and 4 iOS versions? Should we combine Geeksn0w's 'No's? If for example, we combine the tools on the 7.x version, then this should be combined throughout this table and others. So, if we combine the evasi0n7 rows, we should also combine the Geeksn0w. Whatever we do on this table, we should do for other tables like 5.x and 6.x. It needs to be kept uniform and easy to read. — '''[[User:Spydar007|<span style="color:#ff5a00;">Spydar007</span>]] [[User talk:Spydar007|<span style="color:orange;">(Talk)</span>]]''' 15:12, 12 May 2014 (UTC) |
:::::::::::I have now started to use this design on the page. However, I think we should now discuss the markup for the tables. Take a look at the 7.x table. Should we use rowspan to combine evasi0n7 into one? Should we do this for Geeksn0w? Should we use rowspan to combine the tool versions? Should we use rowspan to combine the 7.0.1, 2, 3 and 4 iOS versions? Should we combine Geeksn0w's 'No's? If for example, we combine the tools on the 7.x version, then this should be combined throughout this table and others. So, if we combine the evasi0n7 rows, we should also combine the Geeksn0w. Whatever we do on this table, we should do for other tables like 5.x and 6.x. It needs to be kept uniform and easy to read. — '''[[User:Spydar007|<span style="color:#ff5a00;">Spydar007</span>]] [[User talk:Spydar007|<span style="color:orange;">(Talk)</span>]]''' 15:12, 12 May 2014 (UTC) |
||
::::::::::::Oh, and also take a look at the 1.x tables because that needs some ''serious'' improvements. For example, should we even include iOS 1.1? — '''[[User:Spydar007|<span style="color:#ff5a00;">Spydar007</span>]] [[User talk:Spydar007|<span style="color:orange;">(Talk)</span>]]''' 15:30, 12 May 2014 (UTC) |
::::::::::::Oh, and also take a look at the 1.x tables because that needs some ''serious'' improvements. For example, should we even include iOS 1.1? — '''[[User:Spydar007|<span style="color:#ff5a00;">Spydar007</span>]] [[User talk:Spydar007|<span style="color:orange;">(Talk)</span>]]''' 15:30, 12 May 2014 (UTC) |
||
− | :::::::::::::I don't mind if we do colspan only or none since we can't do both as it breaks on iLiberty+ iOS 1.1.4. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 16:00, 12 May 2014 (UTC) |
||
== iPhone 4 sections == |
== iPhone 4 sections == |
Revision as of 16:59, 12 May 2014
Archives | |
• 2009 • 2010 • 2011 • 2012 • 2013 • 2014 • |
TLC
Okay, we've seen a bunch of firmwares come and go now. The page has started getting pretty incomprehensible and unwieldy. For starters, I think we can move the exploits used to a different page (Jailbreak Exploits?). We'll probably have to rethink how the tables display the information to make it friendlier to use… Maybe forgo tables, and present the information in a list, like such:
iPod touch 4G
- Absinthe: iOS 5.0.1
- greenpois0n: iOS 4.1, 4.2.1
- p0sixspwn: iOS 6.1.5, 6.1.6 (Cydia package only)
- Saffron: iOS 4.3, 4.3.1, 4.3.2, 4.3.3
What do you guys think? --Dialexio (talk) 01:19, 23 March 2014 (UTC)
- I do like the idea of this, though I kind of prefer a table. I do agree though that something in the tables should change since they are getting too big. If no other table ideas are thought of, I would be fine with this proposed design. --iAdam1n (talk) 01:27, 23 March 2014 (UTC)
- We should definitely move the exploits to a seperate page. I'm not so sure about the list view since we wouldn't be able to show which version of which tool is capable of jailbreaking which firmware like we can in the tables at the moment. I think we should have a separate page for Jailbreak Tools and that this page should only be for the first few paragraphs. — Spydar007 (Talk) 09:25, 14 April 2014 (UTC)
- The only problem with the tables though, is that they do not fit on the page. If this can be made to fit, then I also like the idea of keeping tables. --iAdam1n (talk) 09:31, 14 April 2014 (UTC)
- I don't think it is a problem that they don't fit as you can just use the scrollbar at the bottom of your browser. There aren't many that don't fit, four or five. The only way I see we would be able to fix this, would be to make the text smaller. — Spydar007 (Talk) 09:40, 14 April 2014 (UTC)
- Maybe we could use the list view as Dialexio said but in brackets list the version used? We could have a sentence on the page saying what it means. For example;
- iPod touch 5G
- evasi0n7: iOS 7.0.4 (1.0)
- I don't think it is a problem that they don't fit as you can just use the scrollbar at the bottom of your browser. There aren't many that don't fit, four or five. The only way I see we would be able to fix this, would be to make the text smaller. — Spydar007 (Talk) 09:40, 14 April 2014 (UTC)
- The only problem with the tables though, is that they do not fit on the page. If this can be made to fit, then I also like the idea of keeping tables. --iAdam1n (talk) 09:31, 14 April 2014 (UTC)
- We should definitely move the exploits to a seperate page. I'm not so sure about the list view since we wouldn't be able to show which version of which tool is capable of jailbreaking which firmware like we can in the tables at the moment. I think we should have a separate page for Jailbreak Tools and that this page should only be for the first few paragraphs. — Spydar007 (Talk) 09:25, 14 April 2014 (UTC)
- That way we keep the version numbers but don't overflow the page. --iAdam1n (talk) 09:49, 14 April 2014 (UTC)
- We could do, but I still think the tables look cooler and nicer. — Spydar007 (Talk) 09:52, 14 April 2014 (UTC)
- We could also have a table for each jailbreak tool, listing tool versions, iOS versions and devices supported. I am not sure yet how it would be designed, but wanted to put the idea out there incase anyone has ideas. --iAdam1n (talk) 10:02, 14 April 2014 (UTC)
- So you mean instead of having a several tables for devices, wer have several tables for jailbreak tools. Nice idea! I like that and it will be a lot cleaner than it is currently. — Spydar007 (Talk) 10:06, 14 April 2014 (UTC)
- Yes, that is what I mean. I have a design that could be used, here. If anyone has a better idea, please share it. --iAdam1n (talk) 10:12, 14 April 2014 (UTC)
- That looks great! I was just coming up with another design, although I think that that makes it clear enough. — Spydar007 (Talk) 10:32, 14 April 2014 (UTC)
- Here is what I came up with for evasi0n7 (it's not finished, obviously). — Spydar007 (Talk) 10:37, 14 April 2014 (UTC)
- Looks great too. We could maybe avoid the (3,1) etc but lets see what others think. --iAdam1n (talk) 12:32, 14 April 2014 (UTC)
- I built on your proposal a little more and came up with this. (It's based off of Absinthe's compatibility information.) How does it look? --Dialexio (talk) 01:50, 16 April 2014 (UTC)
- Here is what I came up with for evasi0n7 (it's not finished, obviously). — Spydar007 (Talk) 10:37, 14 April 2014 (UTC)
- That looks great! I was just coming up with another design, although I think that that makes it clear enough. — Spydar007 (Talk) 10:32, 14 April 2014 (UTC)
- Yes, that is what I mean. I have a design that could be used, here. If anyone has a better idea, please share it. --iAdam1n (talk) 10:12, 14 April 2014 (UTC)
- So you mean instead of having a several tables for devices, wer have several tables for jailbreak tools. Nice idea! I like that and it will be a lot cleaner than it is currently. — Spydar007 (Talk) 10:06, 14 April 2014 (UTC)
- We could also have a table for each jailbreak tool, listing tool versions, iOS versions and devices supported. I am not sure yet how it would be designed, but wanted to put the idea out there incase anyone has ideas. --iAdam1n (talk) 10:02, 14 April 2014 (UTC)
- We could do, but I still think the tables look cooler and nicer. — Spydar007 (Talk) 09:52, 14 April 2014 (UTC)
- That way we keep the version numbers but don't overflow the page. --iAdam1n (talk) 09:49, 14 April 2014 (UTC)
iOS Version Device iPhone 4 (iPhone3,1) iPhone 4 (iPhone3,2) iPhone 4 (iPhone3,3) iPhone 4S 5.0 No 0.1 5.0.1 (9A405) 2.0 0.1 5.0.1 (9A406) N/A Yes 5.1 No 5.1.1 2.0
- That does look a bit like mine. You've just added in the colors and changed a few things around. :P I would be happy to go forward with this design as the final version. — Spydar007 (Talk) 12:36, 16 April 2014 (UTC)
- Also looks fine by me. If the table still did not fit, we could use iPhone 4 without variants also. --iAdam1n (talk) 12:50, 16 April 2014 (UTC)
- Do you guys think we should go ahead with this? — Spydar007 (Talk) 14:28, 19 April 2014 (UTC)
- Fine by me. --iAdam1n (talk) 16:08, 19 April 2014 (UTC)
- Are we agreed to move the exploits to Jailbreak Exploits and the tools to Jailbreak Tools? — Spydar007 (Talk) 14:27, 21 April 2014 (UTC)
- I agree with the exploits, but do not like the idea for a new page for tools. We can add a new section
==Jailbreak Tools==
instead which IMO will look better. --iAdam1n (talk) 16:22, 21 April 2014 (UTC) - I can go either way, but I don't see the need to move jailbreak compatibility to a new page. It seems fine over here. --Dialexio (talk) 17:08, 21 April 2014 (UTC)
- I agree with the exploits, but do not like the idea for a new page for tools. We can add a new section
- Are we agreed to move the exploits to Jailbreak Exploits and the tools to Jailbreak Tools? — Spydar007 (Talk) 14:27, 21 April 2014 (UTC)
- Fine by me. --iAdam1n (talk) 16:08, 19 April 2014 (UTC)
- Do you guys think we should go ahead with this? — Spydar007 (Talk) 14:28, 19 April 2014 (UTC)
- Also looks fine by me. If the table still did not fit, we could use iPhone 4 without variants also. --iAdam1n (talk) 12:50, 16 April 2014 (UTC)
- Hm… Now that I see the layout in action, the page certainly looks neater, but it does seem a bit difficult to find the device you're looking for. Any ideas on how to tackle this? Perhaps we can do away with "Device" in favor of more descriptive cells for device classes. (i.e. "Apple TV," "iPad," "iPad mini," "iPhone," and "iPod touch") Here's how it might look:
- That does look a bit like mine. You've just added in the colors and changed a few things around. :P I would be happy to go forward with this design as the final version. — Spydar007 (Talk) 12:36, 16 April 2014 (UTC)
iOS Version iPhone iPod touch iPhone 4 (iPhone3,1) iPhone 4 (iPhone3,2) iPhone 4 (iPhone3,3) iPhone 4S iPod touch 4G 5.1.1 2.0
- (I thought of squeezing that row in between "Device" and the different models, but I didn't care for how it looked.) Any other thoughts? --Dialexio (talk) 00:38, 25 April 2014 (UTC)
- To be honest guys, I think the original way is best. Think about it. Let's say someone from JailbreakQA wants to know which tool jailbreaks his iPod touch 2G on iOS 4.2.1. We can direct him to this page. With the original way, he can just scroll down to the iPod touch 2G section, look at 4.2.1 and see exactly which software jailbreaks 4.2.1. But with this new way, he has to scroll through every single tool looking for "iPod touch 2G" and "4.2.1" to be listed, which will take a very long time. I personally think the original way is best. — Spydar007 (Talk) 05:42, 25 April 2014 (UTC)
- (I thought of squeezing that row in between "Device" and the different models, but I didn't care for how it looked.) Any other thoughts? --Dialexio (talk) 00:38, 25 April 2014 (UTC)
- I don't think reverting is a good idea since it does not fit on the page. If we could make this fit, we could maybe have a table that lists the device, tool name, version and iOS version in a table but narrow it down to say 5.x, 6.x, 7.x then that could work, though I do not have an idea currently of a design for this. In any case, the current way is fine. People can cmd + f or ctrl +f to find out. --iAdam1n (talk) 08:41, 25 April 2014 (UTC)
- I don't see why it doesn't fit. It fits perfectly fine on both my monitors for both my computers. It must be your screen resolution. I think that whatever way we do it, it will not be as easy to find as it will be as it was with the original way. Even if people do Ctrl+F or CMD+F, they still have to scroll through and find the correct place for it. — Spydar007 (Talk) 14:50, 25 April 2014 (UTC)
- It does not fit on a 15" monitor. The page needs to be scrolled over to find the end of some of the tables, such as iPhone3,1 table. --iAdam1n (talk) 15:03, 25 April 2014 (UTC)
- The iPhone 3,1 has about 3-inch of space at the end of the table for me. What we could do, is to change the font size of certain tables.
- All tables start with this line:
{| class="wikitable" style="font-size: smaller; text-align: center;
- So, instead we just change it to say this:
{| class="wikitable" style="font-size: 7pt; text-align: center;
- Which will make the font asize smaller. — Spydar007 (Talk) 15:06, 25 April 2014 (UTC)
- Adam, scroll down and look at the iPhone 3,1 table now. Does it still overlap? — Spydar007 (Talk) 15:08, 25 April 2014 (UTC)
- No, still overlaps. See this image. --iAdam1n (talk) 15:39, 25 April 2014 (UTC)
- Since the new design can be confusing if you do not know which tool supports a certain firmware, I have had another design idea. See below.
- No, still overlaps. See this image. --iAdam1n (talk) 15:39, 25 April 2014 (UTC)
- Adam, scroll down and look at the iPhone 3,1 table now. Does it still overlap? — Spydar007 (Talk) 15:08, 25 April 2014 (UTC)
- It does not fit on a 15" monitor. The page needs to be scrolled over to find the end of some of the tables, such as iPhone3,1 table. --iAdam1n (talk) 15:03, 25 April 2014 (UTC)
- I don't see why it doesn't fit. It fits perfectly fine on both my monitors for both my computers. It must be your screen resolution. I think that whatever way we do it, it will not be as easy to find as it will be as it was with the original way. Even if people do Ctrl+F or CMD+F, they still have to scroll through and find the correct place for it. — Spydar007 (Talk) 14:50, 25 April 2014 (UTC)
6.x
iOS | Jailbreak Tool | Tool Version | Devices |
---|---|---|---|
6.0 | redsn0w | 0.9.15b11 | iPad 2, iPad 3, iPad mini 1G, iPhone 3GS, iPhone 4, iPhone 4S, iPhone 5, iPod touch 4G, iPod touch 5G |
evasi0n | 1.0-1.5.3 | ||
5.1 | redsn0w | 0.9.15b31 | Apple TV 2G |
6.0.1 | redsn0w | 0.9.15b31 | iPhone 3GS, iPhone 4, iPod touch 4G, iPod touch 5G |
evasi0n | 1.0-1.5.3 | iPad 2, iPad 3, iPad mini 1G, iPhone 3GS, iPhone 4, iPhone 4S, iPhone 5, iPod touch 4G, iPod touch 5G | |
5.1.1 | redsn0w | 0.9.15b31 | Apple TV 2G |
6.0.2 | redsn0w | 0.9.15b31 | iPad mini 1G, iPhone 5 |
evasi0n | 1.0-1.5.3 |
We would do this for each major iOS, 5.x, 6.x, 7.x etc. Let me know what you think. --iAdam1n (talk) 11:45, 6 May 2014 (UTC)
- I think this is a great idea! However, I think it could get confusing with having the iOS 5 firmwares for the Apple TV 2. I think that we a should either have these in the iOS 5 section, or label them as iOS 6. — Spydar007 (Talk) 14:41, 6 May 2014 (UTC)
- I think that would be more confusing since they are technically in the right place IMO. Since it lists which device it is, I see no issue but if anyone else wants it done like this, ok. --iAdam1n (talk) 14:48, 6 May 2014 (UTC)
- True, but I think we should move both of the iOS 5 ones to either the top or the bottom of the table. — Spydar007 (Talk) 14:53, 6 May 2014 (UTC)
- That would make it more confusing. Let's see what others think. --iAdam1n (talk) 16:15, 6 May 2014 (UTC)
- Maybe the Apple TV can get its own table under the same header. In the separate table, the Apple TV can list both the iOS version and the marketing version… Just throwing that out there. --Dialexio (talk) 05:53, 7 May 2014 (UTC)
- Yeah, that could work. --iAdam1n (talk) 07:49, 7 May 2014 (UTC)
- That would work. — Spydar007 (Talk) 14:19, 7 May 2014 (UTC)
- So, you propose that we have a table for the major versions like 5.x, 6.x, 7.x etc. and in those sections we have one table for all devices other than that of the Apple TV. Below that, we have a second table that has the Apple TV jailbreaks. Should we still use the {{yes}} and {{partial}} templates? — Spydar007 (Talk) 13:00, 10 May 2014 (UTC)
- Oh and also, should we include the betas (like evasi0n7 can jailbreak 7.1b1,2&3)? — Spydar007 (Talk) 13:02, 10 May 2014 (UTC)
- Yes, that is how it is proposed. We should not include betas as it promotes more piracy with people upgrading to use them and if we listed it for evasi0n7, we would have to for all jailbreaks that support betas. --iAdam1n (talk) 15:20, 10 May 2014 (UTC)
- Should we still use the {{yes}} and {{partial}} templates? — Spydar007 (Talk) 15:40, 10 May 2014 (UTC)
- I see no need to. --iAdam1n (talk) 16:45, 10 May 2014 (UTC)
- I was thinking that it would be better to include {{yes}} and whatnot too. I decided to sample it to see how it looks, and I think I really like it. It's just a rough draft, so the colspans and rowspans for the yes/partial/no cells can be changed as necessary. Now if you'll excuse me, my eyes are starting to burn from staring at this wiki markup. :P --Dialexio (talk) 20:36, 10 May 2014 (UTC)
- Should we still use the {{yes}} and {{partial}} templates? — Spydar007 (Talk) 15:40, 10 May 2014 (UTC)
- Yes, that is how it is proposed. We should not include betas as it promotes more piracy with people upgrading to use them and if we listed it for evasi0n7, we would have to for all jailbreaks that support betas. --iAdam1n (talk) 15:20, 10 May 2014 (UTC)
- Maybe the Apple TV can get its own table under the same header. In the separate table, the Apple TV can list both the iOS version and the marketing version… Just throwing that out there. --Dialexio (talk) 05:53, 7 May 2014 (UTC)
- That would make it more confusing. Let's see what others think. --iAdam1n (talk) 16:15, 6 May 2014 (UTC)
- True, but I think we should move both of the iOS 5 ones to either the top or the bottom of the table. — Spydar007 (Talk) 14:53, 6 May 2014 (UTC)
- I think that would be more confusing since they are technically in the right place IMO. Since it lists which device it is, I see no issue but if anyone else wants it done like this, ok. --iAdam1n (talk) 14:48, 6 May 2014 (UTC)
4.x
iOS | Jailbreak Tool | Tool Version | Devices | |||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
iPad | iPad 2 | iPhone 3G | iPhone 3GS | iPhone 4 (iPhone3,1) | iPhone 4 (iPhone3,3) | iPod touch 3G | iPod touch 4G | |||||
4.1 | redsn0w | 0.9.6b2 | N/A | N/A | Yes | Yes | Yes | N/A | Yes | Yes | ||
greenpois0n | RC4 | N/A | N/A | Yes | Yes | Yes | N/A | Yes | Yes | |||
4.2.6 | redsn0w | 0.9.6rc9 | N/A | N/A | N/A | N/A | N/A | Yes | N/A | N/A | ||
greenpois0n | RC5 b4 | N/A | N/A | N/A | N/A | N/A | Yes | N/A | N/A | |||
4.3.3 | redsn0w | 0.9.6rc16 | Yes | No | Yes | Yes | Yes | N/A | Yes | Yes | ||
Saffron | 1.0-1.5.3 | Yes | N/A | Yes |
Apple TV
Marketing Version | iOS Version | Jailbreak Tool | Tool Version | Devices |
---|---|---|---|---|
Apple TV 2G | ||||
4.0 | 4.1 | Seas0nPass | ? | Yes |
6.x
iOS | Jailbreak Tool | Tool Version | Devices | |||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
iPad 2 | iPad 3 | iPad 4 | iPad mini 1G | iPhone 3GS | iPhone 4 | iPhone 4S | iPhone 5 | iPod touch 4G | iPod touch 5G | |||
6.0 | redsn0w | 0.9.15b11 | No | No | No | No | Yes1 | Tethered | No | No | Tethered | No |
evasi0n | 1.0-1.5.3 | Yes |
1 Tethered jailbreak on devices not vulnerable to 0x24000 Segment Overflow.
Apple TV
Marketing Version | iOS Version | Jailbreak Tool | Tool Version | Devices | |
---|---|---|---|---|---|
Apple TV 2G | Apple TV 3G | ||||
5.1 | 6.0 | redsn0w | 0.9.15b1 | Tethered | No |
evasi0n | 1.0-1.5.3 | Yes | No |
- I like it. I would say use colspan and rowspan save duplicate yes/no but other than that, great design. --iAdam1n (talk) 20:55, 10 May 2014 (UTC)
- I to would be happy to go forward with this as the final design for the page. — Spydar007 (Talk) 06:57, 11 May 2014 (UTC)
- I have now started to use this design on the page. However, I think we should now discuss the markup for the tables. Take a look at the 7.x table. Should we use rowspan to combine evasi0n7 into one? Should we do this for Geeksn0w? Should we use rowspan to combine the tool versions? Should we use rowspan to combine the 7.0.1, 2, 3 and 4 iOS versions? Should we combine Geeksn0w's 'No's? If for example, we combine the tools on the 7.x version, then this should be combined throughout this table and others. So, if we combine the evasi0n7 rows, we should also combine the Geeksn0w. Whatever we do on this table, we should do for other tables like 5.x and 6.x. It needs to be kept uniform and easy to read. — Spydar007 (Talk) 15:12, 12 May 2014 (UTC)
iPhone 4 sections
Is it really necessary to have different sections for the variants of the iPhone 4? Surely, we could combine them into one. — Spydar007 (Talk) 16:26, 11 April 2014 (UTC)