The iPhone Wiki - User contributions [en]

The iPhone Wiki:Community portal

2014-01-02T16:46:17Z

CompilingEntropy: /* "GSM" Replacement Proposals (cont.) */

{{Talk Archive}}
{{see also|Unsolved problems}}
==iPhone-Elite==
I think we should include all this old stuff before it gets lost: [http://code.google.com/p/iphone-elite/ code.google.com/p/iphone-elite/]. I mean the wiki articles there. Most infos should be already here, but I'm sure a lot of things are missing too.
--[[User:Http|http]] 15:02, 26 June 2012 (MDT)

==Boot-args cleanup==
We need to clean up the boot-args pages. First the technical part: What I understand is that iBoot loads the kernel. And when loading it, it can pass some parameters to select certain behavior. So this only works with an iBoot or bootrom exploit. I understand that in earlier firmware versions there was simply an iBoot variable, but that doesn't exist or work anymore, now passing theses args requires a different or patched iBoot. There are various parameters in different kernel versions. The description for these arguments is scattered over various places:
*[[Kernel#Boot-Args]] A section with the latest boot arguments list. This should be a short introduction and having a link "main article".
*[[Boot-args (iBoot variable)]] separate page for boot arguments, but mainly for the iBoot variable that doesn't exist any longer
*[{{FULLURL:Boot arguments|redirect=no}} Boot arguments] (redirect)
*[[:Talk:Restore_Mode]] describing the iBoot variable problem
*Various pages referencing boot-args, like [[Research: Re-allowing unsigned ramdisks and boot-args with the 2.* iBoot]] (here we should have a link on the second title)
*My earlier comment [[:Talk:Kernel#boot-args]]
*This comment here.
So what do we want to do about this mess? I suggest to move the current [[Kernel]] content to the redirect page [[Boot arguments]] (or to another new page, maybe [[boot-args]]). The current content of [[Boot-args (iBoot variable)]] and all other content should get merged into there. Then change all references to this new page and on the [[Kernel]] page write just something short with "main article there". What do you think? --[[User:Http|http]] ([[User talk:Http|talk]]) 21:31, 13 February 2013 (UTC)
:I like [[Boot Arguments]]. --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 02:01, 14 February 2013 (UTC)
::One addition: Maybe we should use [[boot-args]] as the main page, because all links are written like that. --[[User:Http|http]] ([[User talk:Http|talk]]) 07:37, 14 February 2013 (UTC)

==The iPhone Wiki re-design==
The design of the iPhone wiki is now quite old and I think it should be updated. I made a [http://oi42.tinypic.com/30ib9y8.jpg concept]. --[[User:Jaggions|Jaggions]] ([[User talk:Jaggions|talk]]) 10:30, 14 June 2013 (UTC)
:I disagree. If anything add an iPhone 5 to the logo but everything else is ok. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 11:05, 14 June 2013 (UTC)
:I wouldn't change the logo to an iPhone 5, especially with iOS 7 and a new iPhone (that will probably look the same as the 5, admittedly) around the corner. I contemplated updating the CSS for iOS 7's UI but decided not to because of the UI's supposed volatility (during the beta period) and I don't have a live version to toy around with. (I personally don't like its current state, but that's not a factor in why I'm not changing it yet.) --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 16:25, 14 June 2013 (UTC)
::Can we not do flat? --[[User:Haifisch|Haifisch]] ([[User talk:Haifisch|talk]]) 21:02, 14 June 2013 (UTC)
::This is what I was thinking. When iOS 7 finally comes out, we could change the CSS to look like that instead. --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 21:11, 14 June 2013 (UTC)
:::iOS 7 looks ugly. We do not want it like that. Maybe a bit more modern but nothing much. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 21:16, 14 June 2013 (UTC)
::::''You'' may not want it like that. That's your opinion. --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 01:55, 15 June 2013 (UTC)
:::::We could make a poll, and see if most users agree or disagree. --[[User:Jaggions|Jaggions]] ([[User talk:Jaggions|talk]]) 10:05, 15 June 2013 (UTC)
:The idea looks nice. But before we make any changes, let's wait until iOS7 comes out. And I'd prefer to just add another skin instead (if possible). I'm still using the classic MonoBook skin by the way. You shouldn't impose design changes to everyone. --[[User:Http|http]] ([[User talk:Http|talk]]) 14:38, 15 June 2013 (UTC)
::The problem with skins is that geohot needs to set them up... An idea I have is that we copy the Vector skin verbatim to a new skin (<code>iOS6</code>) and move the modifications (not general stuff) to [[Mediawiki:iOS6.css]]. Then we can do another verbatim copy to <code>iOS7</code> and modify [[Mediawiki:iOS7.css]]. We could then set the default skin to either <code>iOS6</code> or <code>iOS7</code> so you don't need to be logged in to see them like currently. Then if someone doesn't like them, like you, just change your settings to your preferred skin. The only way around needing geohot is if he opens up the credentials to FTP or whatever to someone. --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 21:17, 15 June 2013 (UTC)
:::I like [[User:5urd|5urd]]'s suggestion. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 22:29, 15 June 2013 (UTC)
What about just removing the text-shadow element for now? I think pages would be easier to read without it. Here's an example: [[:File:Noshadow.png]]. [[User:Britta|Britta]] ([[User talk:Britta|talk]]) 00:11, 29 August 2013 (UTC)
:Yeah removing the shadow will make everything seem more flat but like [[User:http|http]] I'm still using the classic [http://theiphonewiki.com/w/index.php?title=Main_Page&useskin=monobook MonoBook skin] --[[User:Jaggions|Jaggions]] ([[User talk:Jaggions|talk]]) 21:19, 31 August 2013 (UTC)

==Hacker page==
I would like to be added to the list of hackers for my work with the Private Dev Team and the [[Chronic Dev (team)|Chronic Dev Team]] in addition to my release of the Phoenix Semi-Untethered. --[[User:Ph0enix|Ph0enix]] ([[User talk:Ph0enix|talk]]) 18:36, 22 July 2013 (UTC)
:Did you find any exploits? --[[User:Haifisch|Haifisch]] ([[User talk:Haifisch|talk]]) 18:54, 22 July 2013 (UTC)
::No. [[User:phyrrus9|phyrrus9]], a team member found the vulnerability. I am the one who exploited it. --[[User:Ph0enix|Ph0enix]] ([[User talk:Ph0enix|talk]])
:::I can back up this "claim". I was a part of it. --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 20:52, 28 July 2013 (UTC)
::::Whatever happened to this? --[[User:Phyrrus9|phyrrus9]]

==Orphaned articles==
This is an interesting search: [[Special:LonelyPages]] - "The following pages are not linked from or transcluded into other pages in The iPhone Wiki." I'm not sure where all of those articles should be linked, but figuring that out could be a useful project for somebody. [[User:Britta|Britta]] ([[User talk:Britta|talk]]) 05:57, 28 August 2013 (UTC)

==Easy tasks for new editors==
* Finish converting the remaining error codes listed here [[MobileDevice_Library#Known_Error_Codes]] into the proper mach_return_t codes they should be displayed as. (convert the negative number listed into hex, strip any leading "FF" so it should be in the format "0xe80000" followed by two numbers) --[[User:Dirkg|Dirkg]] ([[User talk:Dirkg|talk]]) 22:40, 28 August 2013 (UTC)

== A1XXX model numbers vs. "GSM"/"CDMA"/"Global"/"Cellular"/etc. ==
I know that this topic was [[The iPhone Wiki:Community portal/2013#iPhone 5|already discussed earlier this year]], but it didn't seem to come to a consensus, and the introduction of the [[iPhone 5c]] and [[iPhone 5s]] brought a lot of model numbers. Some of them may "overlap" (think models A1429 and A1442 for the [[iPhone 5]]), but there's simply too many to give names to. There are at least two that can connect to CDMA networks, and all of them can connect to GSM. In addition, with the sheer amount of models, it doesn't seem likely for one model to be treated as a "global" model. Therefore, I changed the iPhone 5c to use model numbers. I would like to do the same to some of the devices that are already present on the wiki though— the same ones from when I first brought up this idea. The GSM/CDMA names work very well for the [[iPad 2]] and [[iPhone 4]]. Things are slightly murkier for the [[iPad 3|iPad (3rd gen.)]], [[iPad 4|iPad (4th gen.)]], [[iPad mini 1G]], and [[iPhone 5]] though; all of those devices' cellular models can connect to GSM networks, so it seems like nonsense to call some of them the "GSM model." The A1XXX model numbers are also how Apple tells the difference between the different models of these devices. Have any opinions changed? Or perhaps someone new might have something to say about this? --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 06:06, 13 September 2013 (UTC)

:I actually like the idea as it does get complicated now with the new devices coming like said and we would have to do this for all devices. Although, if we did this, we would have to move all the key pages that have keys on to support this. That would not be a big problem as we could limit the moves to say 20 per day. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 09:47, 13 September 2013 (UTC)

:I suggest we wait a bit until we see what models of the [[iPhone 5c]] and [[iPhone 5s]] will exist. But in general, I like the idea of using only the A1nnn numbers. The only issue I see right now is that Apple differentiates between A1532 GSM and A1532 CDMA. If there are real hardware differences between these two, then we're screwed again. That's why I suggest to wait until we know these exact model types. On the disambiguation page I added the GSM/CDMA model differentiation already (as Apple does). If they turn out to be the same, we can remove it again, but I wonder why Apple lists two models (with different bands supported) there now. Someone also added the "CDMA" mark to one of the others, but that's not how Apple marks them, so I suggest to remove that mark there again. If everything can be differentiated by these A-model-numbers, then yes, we should change the old pages too. Including all key pages. --[[User:Http|http]] ([[User talk:Http|talk]]) 14:44, 13 September 2013 (UTC)

::I do know there are 2 CDMA and 3-4 GSM for the [[iPhone 5c]] alone. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 16:04, 13 September 2013 (UTC)

:::Ahem… ''All'' of the iPhone 5c models can do GSM communications. Hence one of the reasons why I want to ditch the "GSM"/"Global"/etc. labels in favor of A1XXX model numbers. ;P --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 16:07, 13 September 2013 (UTC)

::::One thing is, what about iPod touch 5 as that has two model numbers that are the same device, same with iPhone5,2. How would we get around that? I suppose we could like both separated with a forward slash. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 18:19, 13 September 2013 (UTC)

:::::Yeah, we could just use something like "[[n42ap|iPhone 5 (Model A1429/A1442)]]." --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 22:45, 13 September 2013 (UTC)

::::::Yeah I thought that but what about the iPhone 4 GSM and GSM Rev A? They both seem to be A1432. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 23:10, 13 September 2013 (UTC)

:::::::This is why I'm against using the A1XXX model numbers instead of the current GSM/Global thing. --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 23:25, 13 September 2013 (UTC)

::::::::I had no plans to change the way we refer to the iPhone 4 or iPad 2 (Apple does use GSM/CDMA, and for those devices it works fine). If a new iPhone 5S revision comes along, Apple will probably refer to it as a "Rev A" thing, and so will we. --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 02:50, 14 September 2013 (UTC)

:Referencing Adam's reply above, if we had took that to the key pages, it'd be <code>[<nowiki/>[{BuildTrain} {Build} (A1432)]]</code> which would mess ''everything'' up. What could we do? Use <code>[<nowiki/>[{BuildTrain} {Build} (A1432 Rev A)]]</code>? No. That doesn't look good. The current way of referring to everything by their supported network type (GSM/CDMA/Global) helps in going to a different page.
:Let's say I'm on [[BrightonMaps 10B329 (iPhone 4 GSM)]] and I want to go the CDMA device. What do I do? Go to the URL and replace <code>GSM</code> with <code>CDMA</code>. With the model numbers, I'd have to navigate to [[Firmware]], then find the link, or find out what the model number of the CDMA variant is and replace the model number in the URL with that. 
:Ok, who navigates by the URL and search bar? ''I do''. And I'm sure there's '''many''' people out there that prefer to navigate with the search bar if they know the page name. If we go by model number, the AJAX search results just list pages with a model number in parenthesis. '''How does that help'''? I'd either have to ''know'' the model number of the device I want, or visit ''each one'' until I find the page I need.
:Sorry for the rant, but I am '''strongly''' against this. --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 23:25, 13 September 2013 (UTC)

::I do suppose we could just trash the buildtrain all together to shorten it down too. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 23:32, 13 September 2013 (UTC)

:::Dropping the Build Train would only ''increase'' the workload. Besides, what's the harm with it? We've been using the same page title structure since forever, and it's worked. "''If it ain't broke, don't fix it''". The current system works, so ''why'', other than the fact that Apple refers to them differently, should we change this? In addition, we don't refer to everything the way Apple does. The [[iPad mini 1G]] is referred to as the "iPad mini". The [[iPad 3]] is refered to as "The New iPad". The [[iPad 4]] is refered to as "iPad with Retina Display"[http://www.apple.com/ipad/compare/]. Are the key pages titled <code>BrightonMaps 10B329 (The New iPad, Wi-Fi+3G for AT&T and Verizon)</code>? No. --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 00:37, 14 September 2013 (UTC)

::::But the reason we want to not use the variants is because the new devices that are coming out are breaking he structure and also CDMA versions can use GSM in the 5c plus we have like 4 for GSM alone. I only meant drop buildtrain to shorten the urls down. For the iPhone 4 GSM Rev A we would have to list it as <code>iPhone 4 A1432 Rev</code> unless another idea is thought of. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 00:55, 14 September 2013 (UTC)

:::::No. Anything involving moving key pages to change their title I am ''completely'' against. As for the iPhone 5s and iPhone 5c, we ultimately have to wait. There may be different types, but if they all work with the same firmware, then what do we do then? Use <code>A1456/A1504</code>? I don't want to do that. It can get confusing in the future if that list were to be huge. With ''5'' different models for the iPhone 5c ''alone'', it's just not practical. For the fact that all support GSM, but not all support CDMA, we just do what we've ''been'' doing: "GSM" and "Global". --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 01:22, 14 September 2013 (UTC)

::::::There's nothing wrong with changing the titles of pages that don't even exist though. If *all* of the models use the same firmware, just go with "iPhone 5s." If they happen to be partitioned into two different firmwares again, that will certainly complicate things, but it wouldn't be worse than nonsense like "GSM," "GSM [<nowiki />Global]," "CDMA," "CDMA [<nowiki />Global]," or "GSM [<nowiki />Global Plus TD-LTE]." If it's just one oddball, we could just have "iPhone 5s" and "iPhone 5s A1XXX" (whatever the odd one is), and include a link on the former page to say "keys for model A1XXX are on this page." --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 02:50, 14 September 2013 (UTC)

::::I probably didn't phrase that well… I wasn't thinking of how Apple markets the product, but rather more along the lines of how they refer to it in, say, the tech specs page or support documents— the pages that shows the messier side to their simple sugar coating. --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 02:50, 14 September 2013 (UTC)

::You keep misinterpreting/misrepresenting what I'm proposing. I never said anything about dropping, say, "iPhone 5" so firmware page titles would look like [[Sundance 10A405 (A1428)]]. I want to change the GSM/Global part to the A1XXX number, so it would probably show like [[Sundance 10A405 (iPhone 5 A1428)]]. (If a hardware revision were made, it would probably look like [[Sundance 10A405 (iPhone 5 A1428 Rev A)]].) From time to time, I edit URLs to browse the wiki too. But the GSM/Global identifiers don't work that well; again, '''all iPhone 5 models can connect to GSM'''. That's not really helpful. --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 02:50, 14 September 2013 (UTC)

:::I suggest we drop the A and use Rev. As for the idea of changing to A1XXX, I see no issues and am for the idea. I admit it can cause chaos when we move the pages but we could limit the moving per day of course. Overall, I think it will be worth it. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 10:01, 14 September 2013 (UTC)

::::No. Don't drop the <code>A</code> from <code>Rev A</code>. Why would you even think to? You want to call them what Apple calls them, and the [[n90bap|revised iPhone 4 GSM]] is referred to with <code>Rev A</code>. In addition, there have been <code>Rev ''B''</code> things before, such as the [[S5L8947]] (A5 Rev B) used in the [[j33iap|revised Apple TV 3G]]. In addition, think of all the redirects we would need to keep for sites that link to key pages directly. I have even seen sites that still link with the URLs as <code>/wiki/index.php?title={Title}</code> instead of the year old change to <code>/wiki/{Title}</code>. The wiki handles that internally for us, but the redirects made in the moves would have to be kept. Currently, only the [[iPhone 5]] and [[iPad 4]] are the only devices referred to by their model numbers. --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 20:53, 14 September 2013 (UTC)

:::That's why I don't want to change it. It's worked for us, and we have no idea how the new firmwares will be handled. I am betting that there will only be two firmware types - one for the GSM, and one for the Global (GSM+CDMA) model. The only reason they are split, IIRC, is because AT&T uses different LTE bands than rest of the GSM world.
:::Ultimately, the GSM/CDMA/Global monikors haven't caused any ''naming conflicts''. Ok, you don't want to use the ''marketing'' title. What about the way they are referred to on [[Apple Developer Center|ADC]], because that seems to be what you want. I may be misreading what you're saying again, but if we're going to do that, let's use their ''full'' title. Something <code>(iPad [4th generation Model A1458])</code> (iPad 4 Wi-Fi) and <code>(iPad Wi-Fi + Cellular [model for Verizon])</code> (iPad 3 Global). Does the first one tell you if the device is Wi-Fi or a Wi-Fi+3G model? Does the second one tell you ''at all'' that it is an [[iPad 3]], or that it supports GSM? No.
:::Apple has a history of being inconsistent. For example, the iPad 3 Wi-Fi is referred to on ADC (and iTunes) as "iPad Wi-Fi (3rd generation)" while the iPad 3 GSM is referred to as "iPad Wi-Fi + Cellular [model for AT&T]". What happened to the "3rd generation"? --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 20:53, 14 September 2013 (UTC)

::::We could always list as <code>iPhone 4 (iPhone3,1)</code> etc instead if that would be better. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 21:13, 14 September 2013 (UTC)

::::Why is there a need to explicitly keep "Wi-Fi" in a key page's title? All you need is a way to distinguish what model it is from its other variants— the A1XXX model number does just that. It's not like we referred to the AppleTV3,2 as "Apple TV 3G (New Single-Core A5)" or something. And obviously, we can use common sense to address the 3rd generation iPad issue you brought up… Now you're just nitpicking. --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 05:28, 15 September 2013 (UTC)
:::::Actually, I think we should wait until we see the firmware for iPhone 5c/5s and then decide. TBH, as [[User:5urd|5urd]] said, it is ok as it is but of course if once the new firmware is out it is more confusing, then we can think again. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 14:12, 15 September 2013 (UTC)

:::::Come to think of it, we can use a mix of both; we can keep the "Global" moniker, but drop the "GSM" moniker in favor of the A1XXX model number. (The "GSM" moniker is the one that's been bothering me.) I think this works well for the iPad 3 (which is actually split into "CDMA" and "Global—" it probably doesn't need to be done for this), iPad 4, iPad mini 1G, and iPhone 5, but this leaves the question of what to do for the iPhone 5C/5S. --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 04:04, 19 September 2013 (UTC)

::::::That would look worse! If we are going to do it, we have to do it for '''''all'''''. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 09:40, 19 September 2013 (UTC)

:::::::What is the status on this now? --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 21:18, 9 November 2013 (UTC)

:::::This discussion has stagnated, but I'm firing it up again— I want to fix this before the end of the year, so this can probably be seen as an ultimatum. Now that Apple has pushed a 7.1 beta to developers, we now know how Apple's splitting the new iPhones up— and it's by A1XXX model numbers still. :\ That's probably the path the wiki will go down, but I do have another idea. The other idea I have in mind is using the A1XXX model number for the cellular devices launched last year. But for this year's iPhones, the FCC ID is actually different between the two, so we could actually use that. Before this gets nitpicked on, the last letter can get changed to an "X" to signify that it's a wildcard of sorts. It's not a pretty solution so I do expect it to get shot down (hence why I'm going with the A1XXX model numbers unless everyone says otherwise), but I'm still throwing it out there in case everyone actually likes that. Everyone is welcome to suggest alternatives, but I '''will''' eliminate that GSM label before the year ends. --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 18:31, 18 November 2013 (UTC)

::::::That is worse, nobody knows the FCC ID off the top of their head. I would suggest "iPhone 5 (iPhone5,1)" if anything. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 18:37, 18 November 2013 (UTC)

:::::::Using "iPhone5,1" or "iPhone6,2" is even ''less'' friendly… The FCC ID can be looked up in Settings or the back of a device. --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 19:06, 18 November 2013 (UTC)

::::::::Well that is not the point. I say either use the firmware name or leave it alone. See what others thing though. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 19:13, 18 November 2013 (UTC)

:::::::::I currently plan on using the A1XXX model numbers— the FCC ID proposal was just thrown out there in the off chance that someone might like it. I'm not really a fan of it myself, but the FCC ID is probably the simplest way to figure out if it's an iPhone6,1 or iPhone6,2 since both have multiple A1XXX model numbers. --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 19:19, 18 November 2013 (UTC)

::::::I agree to get rid of the "GSM" name, as almost all iPhones support GSM. The Axxxx numbers would be nice, but as some phones have several numbers, like A1457/A1518/A1528/A1530 (what is actually different between them?) we can't use it. For the FCC-ID, we can't use that either, because for example the iPhone 5 with FCC-ID BCG-E2599A stands for the GSM/A1428 and also for the GSM+CDMA/A1429 version. So I suggest to either use the identifier (like iPhone2,1) or better the internal name (like n88ap). That would have the advantage to separate them further, because the iPhone 4 A1332 has two internal versions: iPhone3,1/n90ap and the iPhone3,2/n90bap. The bigger question is where you want to use this. That determines mainly the name. On all the key pages? Then it must be a name that is different between models that use different firmwares. And regarding key pages, maybe we should delete all the key pages from this wiki and move them into some database instead and provide a nice user interface and API around it and integrate that into the wiki somehow. That way we can change all pages with one simple edit. For the name, I prefer the internal name. --[[User:Http|http]] ([[User talk:Http|talk]]) 23:43, 18 November 2013 (UTC)

:::::::We would have to edit key pages too. They should not be removed however. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 23:46, 18 November 2013 (UTC)

:::::::Well, I wasn't trying to say that we had to decide on one way to differentiate ''everything''; "GSM" does work fine for, say, the iPhone 4. The proposal I brought up today was using the FCC ID only for this year's (2013's) iPhones— last year's cellular devices would get the A1XXX model numbers (i.e. two different solutions for two different years). But as of right now, I like how using A1XXX model numbers sounds for all of the affected devices, mostly because that's the path Apple's going in their developer portal. Something like "iPhone 5s (Model A1457/A1518/A1528/A1530)" is admittedly a mouthful for this year's iPhones though. At the moment, I'm inquiring about how to label it on [[Firmware]] and such pages, but I'm sure the outcome can be adapted for key page titles as well. As for differences between the models, it seems to be the supported LTE bands. --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 03:49, 19 November 2013 (UTC)

:::::::::I still think that unless it is "iPhone 5 (iPhone5,1)" it will be complicated but on the other hand, I kind of like the idea that [[User:Http|http]] had, using the internal identifiers like this "iPhone 5 (n42ap)". The only problem is that it would cause quite a bit of a flood moving the key pages, although this can be done like 15 per day each or something. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 09:20, 19 November 2013 (UTC)

::::::::::I'm pretty sure the only key page that exists for an A5 (or newer) device is [[Telluride 9A406 (iPhone 4S)]]. --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 17:40, 21 November 2013 (UTC)

:::::::::::That was an example. I know there are no more A5 pages, only the one you said and two beta for iPhone 4S. I just meant that it would show the design. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 13:36, November 21, 2013 (UTC)

== "GSM" Replacement Proposals ==
Since this discussion has become extremely lengthy, here are the proposals (to my understanding) for changing the labels, each of which can be subject to changes (i.e. dropping the word "Model" from Proposal A). In an effort to conserve space (ironically, this still adds a significant amount of length), I only included a few models, which should give an idea of the proposal. Basically anything with an A5 or newer is involved. Feel free to edit this list if I missed or totally misinterpreted something. --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 03:25, 22 November 2013 (UTC)
# Proposal A (A1XXX numbers)
#* iPad 4 (Model A1458)
#* iPad 4 (Model A1459)
#* iPad 4 (Model A1460)
#* iPhone 5 (Model A1428)
#* iPhone 5 (Model A1429/A1442)
#* iPhone 5c (Model A1456/A1532)
#* iPhone 5c (Model A1507/A1516/A1526/A1529)
#* [[InnsbruckTaos 11B554a (iPad 4 A1458)]]
#* [[InnsbruckTaos 11B554a (iPhone 5 A1429/A1442)]]
#* [[InnsbruckTaos 11B554a (iPhone 5c Model A1507/A1516/A1526/A1529)]]
# Proposal B (A1XXX + FCC ID)
#* iPad 4 (Model A1458)
#* iPad 4 (Model A1459)
#* iPad 4 (Model A1460)
#* iPhone 5 (Model A1428)
#* iPhone 5 (Model A1429/A1442)
#* iPhone 5c (BCG‑E2644A)
#* iPhone 5c (BCG‑E2694X)
#* [[InnsbruckTaos 11B554a (iPad 4 A1458)]]
#* [[InnsbruckTaos 11B554a (iPhone 5 A1429/A1442)]]
#* [[InnsbruckTaos 11B554a (iPhone 5c BCG‑E2694X)]]
# Proposal C (-AP Identifier)
#* iPad 4 (p101ap)
#* iPad 4 (p102ap)
#* iPad 4 (p103ap)
#* iPhone 5 (n41ap)
#* iPhone 5 (n42ap)
#* iPhone 5c (n48ap)
#* iPhone 5c (n49ap)
#* [[InnsbruckTaos 11B554a (iPad 4 p101ap)]]
#* [[InnsbruckTaos 11B554a (iPhone 5c n42ap)]]
#* [[InnsbruckTaos 11B554a (iPhone 5c n49ap)]]
# Proposal D (iPhoneX,Y Identifier)
#* iPad 4 (iPad3,4)
#* iPad 4 (iPad3,5)
#* iPad 4 (iPad3,6)
#* iPhone 5 (iPhone5,1)
#* iPhone 5 (iPhone5,2)
#* iPhone 5c (iPhone5,3)
#* iPhone 5c (iPhone5,4)
#* [[InnsbruckTaos 11B554a (iPad3,4)]]
#* [[InnsbruckTaos 11B554a (iPhone5,2)]]
#* [[InnsbruckTaos 11B554a (iPhone5,4)]]

:I like this [[InnsbruckTaos 11B554a iPad 4 (3,4)]] or [[InnsbruckTaos 11B554a iPad 4 (iPad3,4)]]. I see there are 4 ways to approach this;
1. Change every single device. 
2. Change just devices with different variants, iPad 2+, iPad mini+, iPhone 4, iPhone 5+. 
3. Change A5+ only (which I hate the idea of). 
4. Change nothing at all. 
--[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 09:28, 22 November 2013 (UTC)
::My intention for this was to be a ''neutral'' (i.e. opinion-free) spot where all of the proposals were being mentioned, so people could easily see the proposed changes without any bias… v.v --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 20:54, 22 November 2013 (UTC)
:::TBH, I think it is better as it is, but I just stated my opinion that only A5+ would make in inconsistent. Though you could argue it is already, that is down to Apple and furthermore, just A5+ would still not eliminate iPhone 4 (GSM, GSM Rev A or CDMA). --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 17:07, November 22, 2013‎ (UTC)}}
:Do it like #4, and do them all. --[[User:CompilingEntropy|CompilingEntropy]] ([[User talk:CompilingEntropy|talk]]) 18:40, 23 November 2013 (UTC)
::::It will be a pain, but I like [[User:CompilingEntropy|CompilingEntropy]]'s idea as it would make it much much better in the end. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 16:25, 25 November 2013 (UTC)
:I would say A and B are impossible due to various numbers in the same model. I like C best. For variant C you could also leave away the "ap" at the end, because every model has that, so it would be even shorter. For D, that's simply longer names and these names are not used at many places, but I could live with that version as well. --[[User:Http|http]] ([[User talk:Http|talk]]) 23:30, 1 December 2013 (UTC)
Taking into account everyone's thoughts on this, I think we'll probably go with option C. The wiki already uses the "-ap" identifiers for the model pages, and an identifier like "iPad3,4" may confuse someone into thinking it's a model of the [[iPad 3]]. (I would still like to use the A1XXX numbers since Apple does that, but nobody else seems to agree now…) I'll give this a few more days for any last words before acting on it. --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 04:03, 26 December 2013 (UTC)
::It '''will''' get changed before the year ends. I don't know why your opinion keeps changing, but I have already explained the reason for changing it. You even agreed that it needs to be changed. I'm still open to suggestions on what to change it to though. Keep in mind that the change will affect not only key pages, but also how the devices will be referred to throughout the wiki. --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 19:34, 26 December 2013 (UTC)
:::I know it will. I said it is fine to change. I like bot #3 and #4. Only point I must make is that I feel we should change all devices with multiple variants, including iPad Air and iPhone 4. This way, it is consistent and also removes GSM etc altogether. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 19:48, 26 December 2013 (UTC)
::I agree with Adam, if you're going to change some of them then change all of them. This includes iPods. Whatever the outcome, be consistent. As for the outcome itself, I really think we should just use device identifiers (iPhone2,1). That's what we're actually differentiating by, so it only makes sense to refer to devices by them. I don't think there would be any confusion, especially considering we'll keep the name of the device next to it regardless. Barring that, the next best option is ***ap. The other options don't make any sense considering modern devices. --[[User:CompilingEntropy|CompilingEntropy]] ([[User talk:CompilingEntropy|talk]]) 10:54, 30 December 2013 (UTC)
:::I like [[User:CompilingEntropy|CompilingEntropy]]'s idea, though I do not mind if we do every device or just ones with multiple variants, as long as that included pre A5 (iPhone 4) too. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 18:34, 30 December 2013 (UTC)

== "GSM" Replacement Proposals (cont.) ==
So this entire discussion came up because we need to remove "GSM" from models, because there are many models nowadays where the non-GSM model or Global or whatever model, all support GSM. One suggestion was the FCC number, but I think we already agreed that this is out of discussion (only used within USA and nobody refers to this number). So we have to use either
*The Axxxx number (like A1332 for the iPhone 4). This is how Apple identifies their devices.
*The ap number (like n94ap or just short N94). This is the internal name and used in internal references, like in the [[iBEC]] or [[iBSS]] filenames within an [[IPSW]]. (This is also what iH8sn0w has on his stickers on the devices.)
*The 1,2 number (like iPad1,1 for the iPad 1G). This identifier is used in the [[IPSW]] filenames.
There are several issues with using one over the other:
*Some devices (iPad 1G, iPhone 3G, iPhone 3GS, iPhone 4S, iPhone 5, iPhone 5c, iPhone 5s to be exact) have multiple Axxxx numbers for the same ap number/1,2 number. For example the iPad 1G: A1219 (WiFi model) and A1337 (GSM model) both have k48ap / iPad1,1. So only the Axxxx number could be used to replace the "GSM" identifier.
*The iPhone 4 has for A1332 two ap numbers/1,2 numbers: A1332 stands for both n90ap/iPhone3,1 and also for n90bap/iPhone3,2.
*The iPod touch 5G has the same 1,2 number for two ap numbers/Axxxx numbers: iPod5,1 stands for both A1421/n78ap and also for A1509/n78aap.
I understand the point from [[User:IAdam1n|iAdam1n]] somehow that we should make it consistent and change it everywhere in the same manner. The question is where to change what. So where do we use these terms?
*The biggest affected change would be the key pages, so any change there should be carefully considered. Currently we use something like: "InnsbruckTaos 11B554a (iPhone 5c Global)". So the discussion here is just about the change in the brackets. For the devices where no different hardware versions exist, I think the current naming is ok. So let's just continue using that. Only where different (sub-)devices exist for the same main model (like for the iPhone 5c) and they require a different firmware file, then we need to specify it. So we need to add something after the "iPhone 5c" to specify the difference. For older devices, we should leave it as it is, because it works very well there. For example the iPad 1G WiFi and GSM require different firmware, but can be differentiated that way. And we can't use the ap number, because both versions use k48ap, respectively iPad1,1. So I think we should leave the old devices as they are. For newer devices, like the iPhone 5c, there are only two variations for the firmware, but six different Axxxx numbers and we don't want to list all of them in the firmware name. We also cannot use "GSM" for the reason mentioned at the introduction. I would prefer to use the ap number there, but that yields to problems. In case of the iPod touch 5G, we have two models (A1421/n78ap and also A1509/n78aap). Fortunately both use the same firmware, so we don't have to specify anything. But if Apple would release an additional model that would require a different firmware, we would have to specify the name even here and we can't add a name like "n78ap+n78aap". The name iPod5,1 there seems to be the obvious choice, as it is contained in the ipsw name already, so it is unlikely that Apple will change that. The only question is the format then. My choice would be to keep it short, something like "InnsbruckTaos 11B554a (iPhone 5c [5,4])" instead of the current "InnsbruckTaos 11B554a (iPhone 5c Global)". We shouldn't repeat the word "iPhone" there. And we shouldn't remove the "5c" of the original name.
*We also have some hardware lists, for example on the key pages titles where we list under iPad 2: Wi-Fi, GSM, CDMA, Wi-Fi (A). They link directly to our ap-pages, for example the "Wi-Fi (A)" name links to "k93aap". I think we don't need to change this. For the iPhone 5c, we have GSM and Global and they also link to the ap-pages. The link remains there, so we would only change the name. I suggest to use the same short name as in the key page extension, so something like my suggested "[5,4]" for example (instead of "GSM").
*On the [[Models]] page, we have the column "Variant", which also lists "GSM" and "Global" etc. That would also need to change. I suggest to leave it for older devices where "GSM" is a valid differentiation. For newer devices we might list the bands it supports or something else.
*On hardware pages, like [[iPhone]], we also have names and links in the title bar. For devices that have different sub-devices (like the iPhone 4 and iPhone 5/5c/5s) I suggest to rename the title names to the ap-names, as they link to the respective page. I would not change the title "iPhone 3G" to "N82ap" although it links there. So this change would only apply to sub-titles.
--[[User:Http|http]] ([[User talk:Http|talk]]) 00:26, 31 December 2013 (UTC)
:Include iPhone 4 in the change and use same format everywhere on the wiki. I agree that we do not need to change devices with only one variant such as iPhone 3GS. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 00:59, 31 December 2013 (UTC)
:: I agree on that. 3GS, 3G and the 1st iPhone are anyway devices where I do not see too many wiki-related changes in the future.--[[User:M2m|M2m]] ([[User talk:M2m|talk]]) 09:57, 31 December 2013 (UTC)
:I don't like how the abbreviated form of "iPad3,4" looks— I understand wanting to keep "iPad 4" in the name, but I can't come up with alternatives besides going with only the identifier. (Another issue is that MediaWiki's markup parser doesn't seem to like square brackets in links— I tried using <code><nowiki><nowiki /></nowiki></code>.) Having thought it over for a few days, I'm more receptive to changing all multi-variant devices (i.e. including the iPhone 4), but my concern about the Recent changes getting flooded with page moves still exists. The page moves should be done on "quiet" days, when the wiki doesn't see much activity. That being said, this is my understanding of the proposed changes. Does everyone agree with the following?
:* On pages like [[iPhone]], the variant labels will be replaced with the identifier, e.g. iPhone3,1/iPhone3,2/iPhone3,3. (An exception will probably need to be made for the iPad1,1. The "Internal Name" row should also be modified because there will be duplicated information.)
:* On [[Models]], the variant labels will be replaced with something else for the iPhone 5 and newer. (I feel like there are too many LTE bands to list in such a spot, but I don't have any better ideas.)
:* On pages such as [[Firmware]] and [[Jailbreak]], labels will be changed to things like "iPhone 4 (iPhone3,1)" and "iPad 4 (iPad3,4)." Single-variant devices like the Apple TV 2G will remain as-is.
:* The key pages will be moved to a different title, to resemble the following.
:** <del>[[InnsbruckTaos 11B554a (AppleTV3,1)]]</del> [[InnsbruckTaos 11B554a (Apple TV AppleTV3,1)]]
:** <del>[[InnsbruckTaos 11B554a (iPad2,4)]]</del> [[InnsbruckTaos 11B554a (iPad 2 iPad2,4)]]
:** <del>[[InnsbruckTaos 11B554a (iPhone3,1)]]</del> [[InnsbruckTaos 11B554a (iPhone 4 iPhone3,1)]]
:** [[InnsbruckTaos 11B554a (iPod touch 5G)]]
:Do let me know if I missed something. --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 23:57, 31 December 2013 (UTC)
::I agree with your idea [[User:Dialexio|Dialexio]], but make every page use iPhone 4 (iPhone3,1) etc. Of course if pages use iPhone 4 (GSM) now, change that to iPhone 4 (iPhone3,1) or iPhone 4 (3,1). I would suggest moving 10 pages per day for the iPhone 4 to avoid flooding. I do not want some pages to include the AP identifier and some others iPhone3,1 for example. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 00:08, 1 January 2014 (UTC)
:::Several comments:
*The square brackets were just an idea, nothing agreed on that yet. And yes, let's forget this idea if it has problems with MediaWiki.
*The beginning of the name should remain, otherwise we're getting inconsistent with other pages. I agree with [[User:IAdam1n|iAdam1n]] on this. To keep it short, my favorite would be something like "iPhone 4 (3,1)" then. But to make it more clear, "iPhone4 (iPhone3,1)" is also ok to me. If you wanted to leave the first part away and just use "iPhone3,1", then we would have to rename ALL pages (that's also an option).
*Regarding flooding, I prefer that we do all changes at once, at an agreed date/time, done by [[User:Dialexio|Dialexio]]. Maybe in two steps: first step to change the few hardware pages plus one page of each device of the key pages. In the second step the rest. This would ensure that any misunderstandings get catched in the first step, before all pages are renamed. I don't like to have 20 edits per day that I have to go through. Better all at once, but only after agreement of all.
*Yes, we can do iPhone 4 too, if that't the only missing one. It was a misunderstanding on my part for iPad GSM/WiFi, as this doesn't have different firmwares (only on hardware pages needed).
*Regarding the proposed listing of the bands on the [[Models]] page, Variant column, we could only list the bands that are different to make it short.

Can we list here what pages would be affected by the changes? Feel free to edit this list here within my comment. Here's what I have in mind:
*[[Models]]
*[[Apple TV]], [[iPad]], [[iPad mini]], [[iPhone]], [[iPod touch]]
*[[Firmware Keys]]
*[[Firmware]], [[Beta Firmware]]
*[[Jailbreak]]
*key pages: iPhone 4 GSM (like [[Telluride 9A334 (iPhone 4 GSM)]]), total 69 existing pages
*key pages: iPhone 4 GSM (A) (like [[InnsbruckVailPrime 11A4372q (iPhone 4 GSM Rev A)]]), total 21 existing pages
*key pages: iPhone 4 CDMA (like [[BrightonMaps 10B329 (iPhone 4 CDMA)]]), total 50 existing pages
*key pages: iPhone 5 GSM (nonexistent)
*key pages: iPhone 5 Global (nonexistent)
*key pages: iPhone 5c and 5s (nonexistent)
*key pages: iPad 2 Wi-Fi (like [[Durango 8G4 (iPad 2 Wi-Fi)]]), total 5 existing pages
*key pages: iPad 2 GSM (like [[Durango 8G4 (iPad 2 GSM)]]), total 5 existing pages
*key pages: iPad 2 CDMA (like [[Durango 8G4 (iPad 2 CDMA)]]), total 5 existing pages
*key pages: iPad 2 Wi-Fi Rev A (nonexistent)
*key pages: iPad 3 Wi-Fi (nonexistent)
*key pages: iPad 3 CDMA (nonexistent)
*key pages: iPad 3 Global (nonexistent)
*key pages: iPad 4 Wi-Fi (nonexistent)
*key pages: iPad 4 GSM (nonexistent)
*key pages: iPad 4 Global (nonexistent)
*key pages: iPad Air Wi-Fi (nonexistent)
*key pages: iPad Air Cellular (nonexistent)
*key pages: iPad mini Wi-Fi (nonexistent)
*key pages: iPad mini GSM (nonexistent)
*key pages: iPad mini Global (nonexistent)
*key pages: iPad mini 2G Wi-Fi (nonexistent)
*key pages: iPad mini 2G Cellular (nonexistent)
The key pages would get moved without redirect and all references updated. The references should also be in this list above. Add it to the list if I forgot anything.
--[[User:Http|http]] ([[User talk:Http|talk]]) 15:07, 1 January 2014 (UTC)
::::Yes that is fine. I said the 10 a day to avoid a big flood, but I do not mind either way. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 15:13, January 1, 2014‎ (UTC)
::::Looks good. I amended the list to include the iPads as well. --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 17:51, 1 January 2014 (UTC)
:::::So most of you seem to agree on the the generic change now. But what is missing is the exact naming. We have three variations still in discussion:
:::::#"iPhone 4 (3,1)"
:::::#"iPhone 4 (iPhone3,1)"
:::::#"iPhone 4 3,1"
:::::#"iPhone 4 iPhone3,1"
:::::I just noticed that we cannot use the round brackets, because this entire part is already enclosed in round brackets - otherwise we would have nested brackets and in grammar I think you have to use square brackets which are not allowed in MediaWiki. So this leaves us with #3 and #4. #3 looks silly without the brackets, so we probably have to use #4 as [[User:Dialexio|Dialexio]] suggested. --[[User:Http|http]] ([[User talk:Http|talk]]) 23:55, 1 January 2014 (UTC)
::::::I agree with #4, looks better as I feel that #3 needs some sort of brackets if we used that. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]])
::::::Wow, time really flies when you sleep all day. I've missed a ''lot''. Ok. I'm happy we decided to use the firmware moniker instead of something else. Personally, I don't like #1 because it just looks weird IMO. In addition, #1 and #2 would require the use of brackets (<code>(iPhone 4 [3,1])</code>) which would require the use of <code><nowiki/></code> all over the place, and that will get not only ugly, but annoying. I agree #3 looks weird. However, #4 just looks redundent. I personally would like just <code>iPhone3,1</code>, but if I would have to put my vote on one of those last two, it would be #4. --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 08:20, 2 January 2014 (UTC)
:::::::One last comment: We could also just use "iPhone3,1" (leaving the leading "iPhone 4" completely away). That would have two advantages and two disadvantages:
:::::::*+ shorter
:::::::*+ future-proof; if we ever decide to rename the rest as well, this is the way to name it
:::::::*- somehow inconsistent with non-ambiguous other key pages (although ambiguous and non-ambiguous pages are different now anyway)
:::::::*- less easy to understand from the name what device it is (but the iOS version is also not directly visible)
:::::::--[[User:Http|http]] ([[User talk:Http|talk]]) 11:10, 2 January 2014 (UTC)
::::::::To me, that makes it worse. Why can we not use the rounded "()" brackets? I mean, it will only be duplicated in the key page urls, in which if it must be, just do "iPhone 4 iPhone3,1". Does not seem too bad to me. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 11:18, 2 January 2014 (UTC)
::::::::::We ''don't want to'' use parenthesis because then we get double parenthesis (<code>Telluride 9A334 (iPhone 4 (3,1))</code>). We would have to use braces (<code>Telluride 9A334 (iPhone 4 [3,1])</code>), but MediaWiki chokes when there's braces in a link unless you use <code><nowiki/></code>; and that would mean ''everywhere'' there's a firmware link. --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 13:19, 2 January 2014 (UTC)
::::::::That ''is'' what I suggested in my reply... As for your first disadvantage, it only applies to the iPads where Apple has gotten confusing. Actually, now that I think of that, option #4 above does look nice. However, I still don't like the redundency of having <code>iPhone</code> in there twice. And as I said before, options #1 and #3 just look weird. So we're stuck at either redundency or looking weird. But then again, it wouldn't be redundent for the non-existent iPad key page links where Apple decided to be annoying with their firmware monikers. --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 13:19, 2 January 2014 (UTC)
:::::::::Could we not just use the parenthesis but just not in the key page URL's? I mean, "iPhone 4 (iPhone3,1)" but in the urls for key pages, <code>Telluride 9A334 (iPhone_4_iPhone3,1)</code>? That seems fine here. The underscores are currently there anyway. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 13:32, 2 January 2014 (UTC)
::::::::I think that "iPhone 4 (iPhone3,1)" does look the nicest, and I don't really feel like it's redundant. I also like the idea of just saying 'iPhone3,1'. If either of those options doesn't work, it might be good to do something like "iPhone 4; iPhone3,1" or "iPhone 4 | iPhone3,1".--[[User:CompilingEntropy|CompilingEntropy]] ([[User talk:CompilingEntropy|talk]]) 16:46, 2 January 2014 (UTC)

== Key page template ==
I actually like the idea of a database to an extent. I bet I could put together an extension that creates a [[Special:SpecialPages|special page]] that allows read access to everyone (and r/w access to users). Any edits to the key "pages" wouldn't cause a [[Special:RecentChanges|recent changes]] log. If we ever needed to update the layout, we would just need to update the extension. We could even have an API.
The only limitation is that updates to the extension would require either [[User:geohot|George]] or [[User:Dialexio|Alex]] needing to upload the fix. If we were to set up an external site, then all links to it would need to be wrapped with <code>...</code>.
Maybe a simple extension that takes links and redirects you to the external site? That could work. Like, we would have a link to, say, <code>[[<nowiki/>Special:Keys/iPad1,1/9A405]]</code> which would give an HTTP <code>301 Moved Permanently</code> header to, say, <code><nowiki>http://ioskeys.com/iPad1,1/9A405</nowiki></code>. Granted, someone would have to pay for the domain, but it would solve this problem. I may be able to pay for the domain if I make enough money by the time I finish writing everything. Any opposition? --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 16:48, 21 November 2013 (UTC)
:I do not like the idea. I like the idea of the database to a degree, but I think that the pages should remain on this wiki. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 17:03, 21 November 2013 (UTC)
::I don't see this solving any problem— the backlash against changing the key page template was because of (unnecessary?) changes to the arguments, and the frequency of how often such changes were being proposed/applied. How would a database prevent it? For instance, let's say the database columns are all decided on. Suddenly, it's decided that SHA-1 hashes should be added as well, or perhaps "VFDecryptKey" will be renamed to "FSKey." People submitting keys would still be bothered with having to adjust for those changes. --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 17:40, 21 November 2013 (UTC)
:::That with the database is something I'll implement anyway (if not someone else is faster, as I'm quite busy). I just threw that in here as it might solve the problem of the frequent template updates (which is/was wrong anyway). From there it would be easy to create the VFDecrypt page with an overview link or lists of missing keys and that stuff, so the wiki would not need any direct links. But it would mean that we either completely remove all keys here from the wiki and embrace that solution or have them still duplicate (which then doesn't solve the problem). Dialexio: renaming columns can be handled without interface changes, but that's another topic. So let's forget about this database thing for now and we can discuss again when I have something. We certainly don't want to add extensions for that. So back to the discussion about the renaming: If I understood this correctly, you only want to rename A5+ devices and therefore no key pages would be affected. Is my understanding correct? --[[User:Http|http]] ([[User talk:Http|talk]]) 22:08, 21 November 2013 (UTC)
::::As long as the pages stay on this wiki, I do not mind. Although, a database could be pointless as with only 50 more pages to edit for the new format, there is no planned new format/changes again. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 22:16, 21 November 2013 (UTC)
::::About the renaming, that is correct; I'm only interested in changing the cellular labels on A5/+ devices. (Well, the iPad 2 can remain as-is.) --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 00:02, 22 November 2013 (UTC)
:::::Oh, well that would just make things more complicated/inconsistent. We should do all or none. About the template idea, there is also no need as it is not likely we will change the format again. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 00:35, 22 November 2013 (UTC)
::::::Do we really need to CHANGE THE FORMAT 50 TIMES IN A ROW? The old one before everything was messed with worked fine enough. [[User:Winocm|Winocm]] ([[User talk:Winocm|talk]]) 18:22, 27 November 2013 (UTC)
:::::::It was actually one change, which was completed. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 18:32, 27 November 2013 (UTC)

==Login prompt revision suggestion==
I wrote a suggestion here: [[MediaWiki talk:Loginprompt]] (since I don't have permission to edit [[MediaWiki:Loginprompt]] directly) - I'd be interested in whether it sounds like a good idea to other people. [[User:Britta|Britta]] ([[User talk:Britta|talk]]) 01:00, 8 October 2013 (UTC)

==Homepage suggestions==
Under "Application Development", what about linking to [http://iphonedevwiki.net/index.php/Main_Page iPhoneDevWiki]? It's also a community-edited technical resource, and it links to this wiki. It could be helpful to add a little more detail to "Get [[up to speed]] in the community.", like this: "Get [[up to speed]] in the community - learn about how jailbreaks work." Under "Definitions", it could be helpful to list all the firmware tags in one line or sub-list, similar to how Jailbreak is organized next to Tethered jailbreak and Untethered jailbreak, both to save space and help readers understand the list. --[[User:Britta|Britta]] ([[User talk:Britta|talk]]) 23:01, 20 October 2013 (UTC)
:A link to the iPhoneDevWiki sounds good. I wonder if we should have an "External Links" or "Other Resources" section to include links to other sites (such as the [http://blog.iphone-dev.org/ iPhone Dev Team blog]) though. As for the "Up to Speed" page, I feel like the entire page could be reworked a bit— and perhaps even receive a new, clearer name ([[Introduction]]? [[Preface]]? Or something else?)— the current name makes it sound like it's for people that last paid attention to jailbreaking when the App Store didn't exist. And yeah, moving the IMG3 tags to a sub-list sounds like a really good idea. (Admittedly, I actually don't care for its inclusion in the first place, but that's just a personal preference.) --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 00:10, 21 October 2013 (UTC)
::There's already [[Useful Links]] with some links to other core community resources (which could be updated and rearranged) - I was just thinking that it'd be especially useful to link to iPhoneDevWiki prominently since it's likely for TheiPhoneWiki visitors to also be interested in relatively-organized technical information about development. Changing the name of "Up to Speed" sounds fine to me too - that page didn't get much attention since 2008 until I sort of commandeered it to serve as an "intro to jailbreaking" page. :) It could be renamed "getting started", as in "how to get started on learning about research into iOS devices, especially security research (such as jailbreaks)". [[User:Britta|Britta]] ([[User talk:Britta|talk]]) 00:31, 21 October 2013 (UTC)
Also I'd love to see a dedicated section for "Good tasks for new editors", where we could maintain a list of relatively easy/straightforward suggested edits that wouldn't require vast technical knowledge, like updating that links page. Where would that go? Add it as a sub-section of [[The iPhone Wiki:Current events]] and link that section from the homepage or something? Or make a new page? [[User:Britta|Britta]] ([[User talk:Britta|talk]]) 00:40, 21 October 2013 (UTC)

==What is 0x5265c384 in the boot process?==
Does anybody know where <code>0x5265c384</code> points to in the boot process? I haven't been able to find anything on it. --[[User:Ph0enix|Ph0enix]] ([[User talk:Ph0enix|talk]]) 20:14, 23 October 2013 (UTC)

==License for contributions==
This wiki has never had an official license for contributions. Now, IANAL, but IIRC, this means that you can't use ''anything'' posted here unless it qualifies as fair-use. What I propose is that we set a license and add a notice that states that any contributions after a set date are to be licensed under that license (that's kindof a mouthful). I think we should use the [http://creativecommons.org/licenses/by-sa/3.0/ CC-by-SA 3.0] as [[wikipedia:Wikipedia:Text of Creative Commons Attribution-ShareAlike 3.0 Unported License|Wikipedia uses it]], but that's just me. Any ideas? --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 19:53, 9 November 2013 (UTC)
:Well, the edit info already says all this:
Please note that all contributions to The iPhone Wiki may be edited, altered, or
removed by other contributors. If you do not want your writing to be edited mercilessly,
then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public
domain or similar free resource (see The [[:The iPhone Wiki:Copyrights|iPhone Wiki:Copyrights]] for details). '''Do not'''
'''submit copyrighted work without permission!'''
For me, that's enough. I don't need a 50 page license. But if you want to formalize this more, go ahead. --[[User:Http|http]] ([[User talk:Http|talk]]) 20:35, 9 November 2013 (UTC)
:Sounds good. It's good practice to have an official license, just in case any disputes happen someday, and to ensure that it's OK to copy text over to Wikipedia (for example). [[User:Britta|Britta]] ([[User talk:Britta|talk]]) 21:32, 9 November 2013 (UTC)

==Future plans==
Now that I have SSH access, I've begun working on making several, somewhat-overdue changes to the wiki. The Renameuser extension was reinstated, so admins can now rename accounts. If you have another account, that can also get merged into your current account. If you happen to get locked out from both your account and the email used is no longer active, I can run a script to reset your password. I've also begun implementing a very noticeable change— as users of the Vector skin have noticed, the iOS 6-based theming is gone. It's a semi-temporary move though; it's going into its own skin, because… you know, choice is cool. People who like the Vector skin may not have liked the iOS theming, especially since IE 9 and lower didn't display it completely accurately. Therefore, it's going into its own theme. Once that's done I also plan on making a separate iOS 7-based skin. If there are any further thoughts or suggestions on how to improve the wiki, do let me know! --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 22:18, 9 November 2013 (UTC)

==Banner Replacement?==
I kinda feel like the banner on the front page is getting a little stale, so I'm interested in seeing it replaced. I tossed a proposal [https://twitter.com/Draxelf/status/408295008794845184 on Twitter] a couple of days ago (which is admittedly plain, but Myriad Set…), but I haven't heard any opinions on replacing the banner. Are there any thoughts on this matter? --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 17:42, 6 December 2013 (UTC)
:Or, [http://imgur.com/wJFqPl1 this]. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 18:22, 6 December 2013 (UTC)
:Looks nice in Myriad! More professional. [[User:Britta|Britta]] ([[User talk:Britta|talk]]) 04:01, 7 December 2013 (UTC)

==Date Format==
I see that [[User:IAdam1n|iAdam1n]] started to unify the date formats in this wiki. While I like this to be consistent, actually we should've talked about what format to use before changing it. I like the d_mon_yyyy format though. I also saw that he removed the <code>&nbsp;</code> between the date parts on the [[iFaith]] page that I added once purposefully. The reason was that when making the browser window small (or on the iPhone) that the date wraps to two lines, which is almost always undesired. The question is if we should do that everywhere too? Additionally, as we now seem to have a "standard" here, we should document it, so that new users know what format to use. -- [[User:Http|http]] ([[User talk:Http|talk]]) 17:42, 30 December 2013 (UTC)
:I just made it consistent. If you want the <code>&nbsp;</code> back, feel free to add it. I removed it as it did nothing (previewing on OS X). We should use the format I used throughout the wiki and not Dec 23, 2013 etc. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 18:32, 30 December 2013 (UTC)

User:CompilingEntropy

2013-12-30T11:17:07Z

CompilingEntropy: /* About Me */

==About Me==
I'm a 19 year old dude who likes hacking and computers in general.
A few of my interests:
*Security (making and breaking)
*Wireless anything
*802.11 protocols
*Networking
*Zelda
*Rubik's Cubes
*Women

[http://github.com/compilingEntropy Github: compilingEntropy] 
[http://twitter.com/compiledEntropy Twitter: @compiledEntropy] 
[mailto:compilingEntropy@gmail.com compilingEntropy@gmail.com]

==Projects==
[[Keylimepie]]: A tool for mac that automates grabbing keys/ivs from IPSWs.

The iPhone Wiki:Community portal

2013-12-30T10:54:02Z

CompilingEntropy:

{{Talk Archive}}
{{see also|Unsolved problems}}
==iPhone-Elite==
I think we should include all this old stuff before it gets lost: [http://code.google.com/p/iphone-elite/ code.google.com/p/iphone-elite/]. I mean the wiki articles there. Most infos should be already here, but I'm sure a lot of things are missing too.
--[[User:Http|http]] 15:02, 26 June 2012 (MDT)

==Boot-args cleanup==
We need to clean up the boot-args pages. First the technical part: What I understand is that iBoot loads the kernel. And when loading it, it can pass some parameters to select certain behavior. So this only works with an iBoot or bootrom exploit. I understand that in earlier firmware versions there was simply an iBoot variable, but that doesn't exist or work anymore, now passing theses args requires a different or patched iBoot. There are various parameters in different kernel versions. The description for these arguments is scattered over various places:
*[[Kernel#Boot-Args]] A section with the latest boot arguments list. This should be a short introduction and having a link "main article".
*[[Boot-args (iBoot variable)]] separate page for boot arguments, but mainly for the iBoot variable that doesn't exist any longer
*[{{FULLURL:Boot arguments|redirect=no}} Boot arguments] (redirect)
*[[:Talk:Restore_Mode]] describing the iBoot variable problem
*Various pages referencing boot-args, like [[Research: Re-allowing unsigned ramdisks and boot-args with the 2.* iBoot]] (here we should have a link on the second title)
*My earlier comment [[:Talk:Kernel#boot-args]]
*This comment here.
So what do we want to do about this mess? I suggest to move the current [[Kernel]] content to the redirect page [[Boot arguments]] (or to another new page, maybe [[boot-args]]). The current content of [[Boot-args (iBoot variable)]] and all other content should get merged into there. Then change all references to this new page and on the [[Kernel]] page write just something short with "main article there". What do you think? --[[User:Http|http]] ([[User talk:Http|talk]]) 21:31, 13 February 2013 (UTC)
:I like [[Boot Arguments]]. --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 02:01, 14 February 2013 (UTC)
::One addition: Maybe we should use [[boot-args]] as the main page, because all links are written like that. --[[User:Http|http]] ([[User talk:Http|talk]]) 07:37, 14 February 2013 (UTC)

==The iPhone Wiki re-design==
The design of the iPhone wiki is now quite old and I think it should be updated. I made a [http://oi42.tinypic.com/30ib9y8.jpg concept]. --[[User:Jaggions|Jaggions]] ([[User talk:Jaggions|talk]]) 10:30, 14 June 2013 (UTC)
:I disagree. If anything add an iPhone 5 to the logo but everything else is ok. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 11:05, 14 June 2013 (UTC)
:I wouldn't change the logo to an iPhone 5, especially with iOS 7 and a new iPhone (that will probably look the same as the 5, admittedly) around the corner. I contemplated updating the CSS for iOS 7's UI but decided not to because of the UI's supposed volatility (during the beta period) and I don't have a live version to toy around with. (I personally don't like its current state, but that's not a factor in why I'm not changing it yet.) --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 16:25, 14 June 2013 (UTC)
::Can we not do flat? --[[User:Haifisch|Haifisch]] ([[User talk:Haifisch|talk]]) 21:02, 14 June 2013 (UTC)
::This is what I was thinking. When iOS 7 finally comes out, we could change the CSS to look like that instead. --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 21:11, 14 June 2013 (UTC)
:::iOS 7 looks ugly. We do not want it like that. Maybe a bit more modern but nothing much. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 21:16, 14 June 2013 (UTC)
::::''You'' may not want it like that. That's your opinion. --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 01:55, 15 June 2013 (UTC)
:::::We could make a poll, and see if most users agree or disagree. --[[User:Jaggions|Jaggions]] ([[User talk:Jaggions|talk]]) 10:05, 15 June 2013 (UTC)
:The idea looks nice. But before we make any changes, let's wait until iOS7 comes out. And I'd prefer to just add another skin instead (if possible). I'm still using the classic MonoBook skin by the way. You shouldn't impose design changes to everyone. --[[User:Http|http]] ([[User talk:Http|talk]]) 14:38, 15 June 2013 (UTC)
::The problem with skins is that geohot needs to set them up... An idea I have is that we copy the Vector skin verbatim to a new skin (<code>iOS6</code>) and move the modifications (not general stuff) to [[Mediawiki:iOS6.css]]. Then we can do another verbatim copy to <code>iOS7</code> and modify [[Mediawiki:iOS7.css]]. We could then set the default skin to either <code>iOS6</code> or <code>iOS7</code> so you don't need to be logged in to see them like currently. Then if someone doesn't like them, like you, just change your settings to your preferred skin. The only way around needing geohot is if he opens up the credentials to FTP or whatever to someone. --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 21:17, 15 June 2013 (UTC)
:::I like [[User:5urd|5urd]]'s suggestion. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 22:29, 15 June 2013 (UTC)
What about just removing the text-shadow element for now? I think pages would be easier to read without it. Here's an example: [[:File:Noshadow.png]]. [[User:Britta|Britta]] ([[User talk:Britta|talk]]) 00:11, 29 August 2013 (UTC)
:Yeah removing the shadow will make everything seem more flat but like [[User:http|http]] I'm still using the classic [http://theiphonewiki.com/w/index.php?title=Main_Page&useskin=monobook MonoBook skin] --[[User:Jaggions|Jaggions]] ([[User talk:Jaggions|talk]]) 21:19, 31 August 2013 (UTC)

==Hacker page==
I would like to be added to the list of hackers for my work with the Private Dev Team and the [[Chronic Dev (team)|Chronic Dev Team]] in addition to my release of the Phoenix Semi-Untethered. --[[User:Ph0enix|Ph0enix]] ([[User talk:Ph0enix|talk]]) 18:36, 22 July 2013 (UTC)
:Did you find any exploits? --[[User:Haifisch|Haifisch]] ([[User talk:Haifisch|talk]]) 18:54, 22 July 2013 (UTC)
::No. [[User:phyrrus9|phyrrus9]], a team member found the vulnerability. I am the one who exploited it. --[[User:Ph0enix|Ph0enix]] ([[User talk:Ph0enix|talk]])
:::I can back up this "claim". I was a part of it. --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 20:52, 28 July 2013 (UTC)
::::Whatever happened to this? --[[User:Phyrrus9|phyrrus9]]

==Orphaned articles==
This is an interesting search: [[Special:LonelyPages]] - "The following pages are not linked from or transcluded into other pages in The iPhone Wiki." I'm not sure where all of those articles should be linked, but figuring that out could be a useful project for somebody. [[User:Britta|Britta]] ([[User talk:Britta|talk]]) 05:57, 28 August 2013 (UTC)

==Easy tasks for new editors==
* Finish converting the remaining error codes listed here [[MobileDevice_Library#Known_Error_Codes]] into the proper mach_return_t codes they should be displayed as. (convert the negative number listed into hex, strip any leading "FF" so it should be in the format "0xe80000" followed by two numbers) --[[User:Dirkg|Dirkg]] ([[User talk:Dirkg|talk]]) 22:40, 28 August 2013 (UTC)

== A1XXX model numbers vs. "GSM"/"CDMA"/"Global"/"Cellular"/etc. ==
I know that this topic was [[The iPhone Wiki:Community portal/2013#iPhone 5|already discussed earlier this year]], but it didn't seem to come to a consensus, and the introduction of the [[iPhone 5c]] and [[iPhone 5s]] brought a lot of model numbers. Some of them may "overlap" (think models A1429 and A1442 for the [[iPhone 5]]), but there's simply too many to give names to. There are at least two that can connect to CDMA networks, and all of them can connect to GSM. In addition, with the sheer amount of models, it doesn't seem likely for one model to be treated as a "global" model. Therefore, I changed the iPhone 5c to use model numbers. I would like to do the same to some of the devices that are already present on the wiki though— the same ones from when I first brought up this idea. The GSM/CDMA names work very well for the [[iPad 2]] and [[iPhone 4]]. Things are slightly murkier for the [[iPad 3|iPad (3rd gen.)]], [[iPad 4|iPad (4th gen.)]], [[iPad mini 1G]], and [[iPhone 5]] though; all of those devices' cellular models can connect to GSM networks, so it seems like nonsense to call some of them the "GSM model." The A1XXX model numbers are also how Apple tells the difference between the different models of these devices. Have any opinions changed? Or perhaps someone new might have something to say about this? --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 06:06, 13 September 2013 (UTC)

:I actually like the idea as it does get complicated now with the new devices coming like said and we would have to do this for all devices. Although, if we did this, we would have to move all the key pages that have keys on to support this. That would not be a big problem as we could limit the moves to say 20 per day. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 09:47, 13 September 2013 (UTC)

:I suggest we wait a bit until we see what models of the [[iPhone 5c]] and [[iPhone 5s]] will exist. But in general, I like the idea of using only the A1nnn numbers. The only issue I see right now is that Apple differentiates between A1532 GSM and A1532 CDMA. If there are real hardware differences between these two, then we're screwed again. That's why I suggest to wait until we know these exact model types. On the disambiguation page I added the GSM/CDMA model differentiation already (as Apple does). If they turn out to be the same, we can remove it again, but I wonder why Apple lists two models (with different bands supported) there now. Someone also added the "CDMA" mark to one of the others, but that's not how Apple marks them, so I suggest to remove that mark there again. If everything can be differentiated by these A-model-numbers, then yes, we should change the old pages too. Including all key pages. --[[User:Http|http]] ([[User talk:Http|talk]]) 14:44, 13 September 2013 (UTC)

::I do know there are 2 CDMA and 3-4 GSM for the [[iPhone 5c]] alone. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 16:04, 13 September 2013 (UTC)

:::Ahem… ''All'' of the iPhone 5c models can do GSM communications. Hence one of the reasons why I want to ditch the "GSM"/"Global"/etc. labels in favor of A1XXX model numbers. ;P --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 16:07, 13 September 2013 (UTC)

::::One thing is, what about iPod touch 5 as that has two model numbers that are the same device, same with iPhone5,2. How would we get around that? I suppose we could like both separated with a forward slash. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 18:19, 13 September 2013 (UTC)

:::::Yeah, we could just use something like "[[n42ap|iPhone 5 (Model A1429/A1442)]]." --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 22:45, 13 September 2013 (UTC)

::::::Yeah I thought that but what about the iPhone 4 GSM and GSM Rev A? They both seem to be A1432. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 23:10, 13 September 2013 (UTC)

:::::::This is why I'm against using the A1XXX model numbers instead of the current GSM/Global thing. --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 23:25, 13 September 2013 (UTC)

::::::::I had no plans to change the way we refer to the iPhone 4 or iPad 2 (Apple does use GSM/CDMA, and for those devices it works fine). If a new iPhone 5S revision comes along, Apple will probably refer to it as a "Rev A" thing, and so will we. --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 02:50, 14 September 2013 (UTC)

:Referencing Adam's reply above, if we had took that to the key pages, it'd be <code>[<nowiki/>[{BuildTrain} {Build} (A1432)]]</code> which would mess ''everything'' up. What could we do? Use <code>[<nowiki/>[{BuildTrain} {Build} (A1432 Rev A)]]</code>? No. That doesn't look good. The current way of referring to everything by their supported network type (GSM/CDMA/Global) helps in going to a different page.
:Let's say I'm on [[BrightonMaps 10B329 (iPhone 4 GSM)]] and I want to go the CDMA device. What do I do? Go to the URL and replace <code>GSM</code> with <code>CDMA</code>. With the model numbers, I'd have to navigate to [[Firmware]], then find the link, or find out what the model number of the CDMA variant is and replace the model number in the URL with that. 
:Ok, who navigates by the URL and search bar? ''I do''. And I'm sure there's '''many''' people out there that prefer to navigate with the search bar if they know the page name. If we go by model number, the AJAX search results just list pages with a model number in parenthesis. '''How does that help'''? I'd either have to ''know'' the model number of the device I want, or visit ''each one'' until I find the page I need.
:Sorry for the rant, but I am '''strongly''' against this. --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 23:25, 13 September 2013 (UTC)

::I do suppose we could just trash the buildtrain all together to shorten it down too. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 23:32, 13 September 2013 (UTC)

:::Dropping the Build Train would only ''increase'' the workload. Besides, what's the harm with it? We've been using the same page title structure since forever, and it's worked. "''If it ain't broke, don't fix it''". The current system works, so ''why'', other than the fact that Apple refers to them differently, should we change this? In addition, we don't refer to everything the way Apple does. The [[iPad mini 1G]] is referred to as the "iPad mini". The [[iPad 3]] is refered to as "The New iPad". The [[iPad 4]] is refered to as "iPad with Retina Display"[http://www.apple.com/ipad/compare/]. Are the key pages titled <code>BrightonMaps 10B329 (The New iPad, Wi-Fi+3G for AT&T and Verizon)</code>? No. --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 00:37, 14 September 2013 (UTC)

::::But the reason we want to not use the variants is because the new devices that are coming out are breaking he structure and also CDMA versions can use GSM in the 5c plus we have like 4 for GSM alone. I only meant drop buildtrain to shorten the urls down. For the iPhone 4 GSM Rev A we would have to list it as <code>iPhone 4 A1432 Rev</code> unless another idea is thought of. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 00:55, 14 September 2013 (UTC)

:::::No. Anything involving moving key pages to change their title I am ''completely'' against. As for the iPhone 5s and iPhone 5c, we ultimately have to wait. There may be different types, but if they all work with the same firmware, then what do we do then? Use <code>A1456/A1504</code>? I don't want to do that. It can get confusing in the future if that list were to be huge. With ''5'' different models for the iPhone 5c ''alone'', it's just not practical. For the fact that all support GSM, but not all support CDMA, we just do what we've ''been'' doing: "GSM" and "Global". --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 01:22, 14 September 2013 (UTC)

::::::There's nothing wrong with changing the titles of pages that don't even exist though. If *all* of the models use the same firmware, just go with "iPhone 5s." If they happen to be partitioned into two different firmwares again, that will certainly complicate things, but it wouldn't be worse than nonsense like "GSM," "GSM [<nowiki />Global]," "CDMA," "CDMA [<nowiki />Global]," or "GSM [<nowiki />Global Plus TD-LTE]." If it's just one oddball, we could just have "iPhone 5s" and "iPhone 5s A1XXX" (whatever the odd one is), and include a link on the former page to say "keys for model A1XXX are on this page." --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 02:50, 14 September 2013 (UTC)

::::I probably didn't phrase that well… I wasn't thinking of how Apple markets the product, but rather more along the lines of how they refer to it in, say, the tech specs page or support documents— the pages that shows the messier side to their simple sugar coating. --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 02:50, 14 September 2013 (UTC)

::You keep misinterpreting/misrepresenting what I'm proposing. I never said anything about dropping, say, "iPhone 5" so firmware page titles would look like [[Sundance 10A405 (A1428)]]. I want to change the GSM/Global part to the A1XXX number, so it would probably show like [[Sundance 10A405 (iPhone 5 A1428)]]. (If a hardware revision were made, it would probably look like [[Sundance 10A405 (iPhone 5 A1428 Rev A)]].) From time to time, I edit URLs to browse the wiki too. But the GSM/Global identifiers don't work that well; again, '''all iPhone 5 models can connect to GSM'''. That's not really helpful. --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 02:50, 14 September 2013 (UTC)

:::I suggest we drop the A and use Rev. As for the idea of changing to A1XXX, I see no issues and am for the idea. I admit it can cause chaos when we move the pages but we could limit the moving per day of course. Overall, I think it will be worth it. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 10:01, 14 September 2013 (UTC)

::::No. Don't drop the <code>A</code> from <code>Rev A</code>. Why would you even think to? You want to call them what Apple calls them, and the [[n90bap|revised iPhone 4 GSM]] is referred to with <code>Rev A</code>. In addition, there have been <code>Rev ''B''</code> things before, such as the [[S5L8947]] (A5 Rev B) used in the [[j33iap|revised Apple TV 3G]]. In addition, think of all the redirects we would need to keep for sites that link to key pages directly. I have even seen sites that still link with the URLs as <code>/wiki/index.php?title={Title}</code> instead of the year old change to <code>/wiki/{Title}</code>. The wiki handles that internally for us, but the redirects made in the moves would have to be kept. Currently, only the [[iPhone 5]] and [[iPad 4]] are the only devices referred to by their model numbers. --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 20:53, 14 September 2013 (UTC)

:::That's why I don't want to change it. It's worked for us, and we have no idea how the new firmwares will be handled. I am betting that there will only be two firmware types - one for the GSM, and one for the Global (GSM+CDMA) model. The only reason they are split, IIRC, is because AT&T uses different LTE bands than rest of the GSM world.
:::Ultimately, the GSM/CDMA/Global monikors haven't caused any ''naming conflicts''. Ok, you don't want to use the ''marketing'' title. What about the way they are referred to on [[Apple Developer Center|ADC]], because that seems to be what you want. I may be misreading what you're saying again, but if we're going to do that, let's use their ''full'' title. Something <code>(iPad [4th generation Model A1458])</code> (iPad 4 Wi-Fi) and <code>(iPad Wi-Fi + Cellular [model for Verizon])</code> (iPad 3 Global). Does the first one tell you if the device is Wi-Fi or a Wi-Fi+3G model? Does the second one tell you ''at all'' that it is an [[iPad 3]], or that it supports GSM? No.
:::Apple has a history of being inconsistent. For example, the iPad 3 Wi-Fi is referred to on ADC (and iTunes) as "iPad Wi-Fi (3rd generation)" while the iPad 3 GSM is referred to as "iPad Wi-Fi + Cellular [model for AT&T]". What happened to the "3rd generation"? --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 20:53, 14 September 2013 (UTC)

::::We could always list as <code>iPhone 4 (iPhone3,1)</code> etc instead if that would be better. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 21:13, 14 September 2013 (UTC)

::::Why is there a need to explicitly keep "Wi-Fi" in a key page's title? All you need is a way to distinguish what model it is from its other variants— the A1XXX model number does just that. It's not like we referred to the AppleTV3,2 as "Apple TV 3G (New Single-Core A5)" or something. And obviously, we can use common sense to address the 3rd generation iPad issue you brought up… Now you're just nitpicking. --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 05:28, 15 September 2013 (UTC)
:::::Actually, I think we should wait until we see the firmware for iPhone 5c/5s and then decide. TBH, as [[User:5urd|5urd]] said, it is ok as it is but of course if once the new firmware is out it is more confusing, then we can think again. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 14:12, 15 September 2013 (UTC)

:::::Come to think of it, we can use a mix of both; we can keep the "Global" moniker, but drop the "GSM" moniker in favor of the A1XXX model number. (The "GSM" moniker is the one that's been bothering me.) I think this works well for the iPad 3 (which is actually split into "CDMA" and "Global—" it probably doesn't need to be done for this), iPad 4, iPad mini 1G, and iPhone 5, but this leaves the question of what to do for the iPhone 5C/5S. --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 04:04, 19 September 2013 (UTC)

::::::That would look worse! If we are going to do it, we have to do it for '''''all'''''. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 09:40, 19 September 2013 (UTC)

:::::::What is the status on this now? --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 21:18, 9 November 2013 (UTC)

:::::This discussion has stagnated, but I'm firing it up again— I want to fix this before the end of the year, so this can probably be seen as an ultimatum. Now that Apple has pushed a 7.1 beta to developers, we now know how Apple's splitting the new iPhones up— and it's by A1XXX model numbers still. :\ That's probably the path the wiki will go down, but I do have another idea. The other idea I have in mind is using the A1XXX model number for the cellular devices launched last year. But for this year's iPhones, the FCC ID is actually different between the two, so we could actually use that. Before this gets nitpicked on, the last letter can get changed to an "X" to signify that it's a wildcard of sorts. It's not a pretty solution so I do expect it to get shot down (hence why I'm going with the A1XXX model numbers unless everyone says otherwise), but I'm still throwing it out there in case everyone actually likes that. Everyone is welcome to suggest alternatives, but I '''will''' eliminate that GSM label before the year ends. --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 18:31, 18 November 2013 (UTC)

::::::That is worse, nobody knows the FCC ID off the top of their head. I would suggest "iPhone 5 (iPhone5,1)" if anything. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 18:37, 18 November 2013 (UTC)

:::::::Using "iPhone5,1" or "iPhone6,2" is even ''less'' friendly… The FCC ID can be looked up in Settings or the back of a device. --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 19:06, 18 November 2013 (UTC)

::::::::Well that is not the point. I say either use the firmware name or leave it alone. See what others thing though. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 19:13, 18 November 2013 (UTC)

:::::::::I currently plan on using the A1XXX model numbers— the FCC ID proposal was just thrown out there in the off chance that someone might like it. I'm not really a fan of it myself, but the FCC ID is probably the simplest way to figure out if it's an iPhone6,1 or iPhone6,2 since both have multiple A1XXX model numbers. --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 19:19, 18 November 2013 (UTC)

::::::I agree to get rid of the "GSM" name, as almost all iPhones support GSM. The Axxxx numbers would be nice, but as some phones have several numbers, like A1457/A1518/A1528/A1530 (what is actually different between them?) we can't use it. For the FCC-ID, we can't use that either, because for example the iPhone 5 with FCC-ID BCG-E2599A stands for the GSM/A1428 and also for the GSM+CDMA/A1429 version. So I suggest to either use the identifier (like iPhone2,1) or better the internal name (like n88ap). That would have the advantage to separate them further, because the iPhone 4 A1332 has two internal versions: iPhone3,1/n90ap and the iPhone3,2/n90bap. The bigger question is where you want to use this. That determines mainly the name. On all the key pages? Then it must be a name that is different between models that use different firmwares. And regarding key pages, maybe we should delete all the key pages from this wiki and move them into some database instead and provide a nice user interface and API around it and integrate that into the wiki somehow. That way we can change all pages with one simple edit. For the name, I prefer the internal name. --[[User:Http|http]] ([[User talk:Http|talk]]) 23:43, 18 November 2013 (UTC)

:::::::We would have to edit key pages too. They should not be removed however. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 23:46, 18 November 2013 (UTC)

:::::::Well, I wasn't trying to say that we had to decide on one way to differentiate ''everything''; "GSM" does work fine for, say, the iPhone 4. The proposal I brought up today was using the FCC ID only for this year's (2013's) iPhones— last year's cellular devices would get the A1XXX model numbers (i.e. two different solutions for two different years). But as of right now, I like how using A1XXX model numbers sounds for all of the affected devices, mostly because that's the path Apple's going in their developer portal. Something like "iPhone 5s (Model A1457/A1518/A1528/A1530)" is admittedly a mouthful for this year's iPhones though. At the moment, I'm inquiring about how to label it on [[Firmware]] and such pages, but I'm sure the outcome can be adapted for key page titles as well. As for differences between the models, it seems to be the supported LTE bands. --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 03:49, 19 November 2013 (UTC)

:::::::::I still think that unless it is "iPhone 5 (iPhone5,1)" it will be complicated but on the other hand, I kind of like the idea that [[User:Http|http]] had, using the internal identifiers like this "iPhone 5 (n42ap)". The only problem is that it would cause quite a bit of a flood moving the key pages, although this can be done like 15 per day each or something. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 09:20, 19 November 2013 (UTC)

::::::::::I'm pretty sure the only key page that exists for an A5 (or newer) device is [[Telluride 9A406 (iPhone 4S)]]. --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 17:40, 21 November 2013 (UTC)

:::::::::::That was an example. I know there are no more A5 pages, only the one you said and two beta for iPhone 4S. I just meant that it would show the design. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 13:36, November 21, 2013 (UTC)

== "GSM" Replacement Proposals ==
Since this discussion has become extremely lengthy, here are the proposals (to my understanding) for changing the labels, each of which can be subject to changes (i.e. dropping the word "Model" from Proposal A). In an effort to conserve space (ironically, this still adds a significant amount of length), I only included a few models, which should give an idea of the proposal. Basically anything with an A5 or newer is involved. Feel free to edit this list if I missed or totally misinterpreted something. --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 03:25, 22 November 2013 (UTC)
# Proposal A (A1XXX numbers)
#* iPad 4 (Model A1458)
#* iPad 4 (Model A1459)
#* iPad 4 (Model A1460)
#* iPhone 5 (Model A1428)
#* iPhone 5 (Model A1429/A1442)
#* iPhone 5c (Model A1456/A1532)
#* iPhone 5c (Model A1507/A1516/A1526/A1529)
#* [[InnsbruckTaos 11B554a (iPad 4 A1458)]]
#* [[InnsbruckTaos 11B554a (iPhone 5 A1429/A1442)]]
#* [[InnsbruckTaos 11B554a (iPhone 5c Model A1507/A1516/A1526/A1529)]]
# Proposal B (A1XXX + FCC ID)
#* iPad 4 (Model A1458)
#* iPad 4 (Model A1459)
#* iPad 4 (Model A1460)
#* iPhone 5 (Model A1428)
#* iPhone 5 (Model A1429/A1442)
#* iPhone 5c (BCG‑E2644A)
#* iPhone 5c (BCG‑E2694X)
#* [[InnsbruckTaos 11B554a (iPad 4 A1458)]]
#* [[InnsbruckTaos 11B554a (iPhone 5 A1429/A1442)]]
#* [[InnsbruckTaos 11B554a (iPhone 5c BCG‑E2694X)]]
# Proposal C (-AP Identifier)
#* iPad 4 (p101ap)
#* iPad 4 (p102ap)
#* iPad 4 (p103ap)
#* iPhone 5 (n41ap)
#* iPhone 5 (n42ap)
#* iPhone 5c (n48ap)
#* iPhone 5c (n49ap)
#* [[InnsbruckTaos 11B554a (iPad 4 p101ap)]]
#* [[InnsbruckTaos 11B554a (iPhone 5c n42ap)]]
#* [[InnsbruckTaos 11B554a (iPhone 5c n49ap)]]
# Proposal D (iPhoneX,Y Identifier)
#* iPad 4 (iPad3,4)
#* iPad 4 (iPad3,5)
#* iPad 4 (iPad3,6)
#* iPhone 5 (iPhone5,1)
#* iPhone 5 (iPhone5,2)
#* iPhone 5c (iPhone5,3)
#* iPhone 5c (iPhone5,4)
#* [[InnsbruckTaos 11B554a (iPad3,4)]]
#* [[InnsbruckTaos 11B554a (iPhone5,2)]]
#* [[InnsbruckTaos 11B554a (iPhone5,4)]]

:I like this [[InnsbruckTaos 11B554a iPad 4 (3,4)]] or [[InnsbruckTaos 11B554a iPad 4 (iPad3,4)]]. I see there are 4 ways to approach this;
1. Change every single device. 
2. Change just devices with different variants, iPad 2+, iPad mini+, iPhone 4, iPhone 5+. 
3. Change A5+ only (which I hate the idea of). 
4. Change nothing at all. 
--[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 09:28, 22 November 2013 (UTC)
::My intention for this was to be a ''neutral'' (i.e. opinion-free) spot where all of the proposals were being mentioned, so people could easily see the proposed changes without any bias… v.v --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 20:54, 22 November 2013 (UTC)
:::TBH, I think it is better as it is, but I just stated my opinion that only A5+ would make in inconsistent. Though you could argue it is already, that is down to Apple and furthermore, just A5+ would still not eliminate iPhone 4 (GSM, GSM Rev A or CDMA). --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 17:07, November 22, 2013‎ (UTC)}}
:Do it like #4, and do them all. --[[User:CompilingEntropy|CompilingEntropy]] ([[User talk:CompilingEntropy|talk]]) 18:40, 23 November 2013 (UTC)
::::It will be a pain, but I like [[User:CompilingEntropy|CompilingEntropy]]'s idea as it would make it much much better in the end. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 16:25, 25 November 2013 (UTC)
:I would say A and B are impossible due to various numbers in the same model. I like C best. For variant C you could also leave away the "ap" at the end, because every model has that, so it would be even shorter. For D, that's simply longer names and these names are not used at many places, but I could live with that version as well. --[[User:Http|http]] ([[User talk:Http|talk]]) 23:30, 1 December 2013 (UTC)
Taking into account everyone's thoughts on this, I think we'll probably go with option C. The wiki already uses the "-ap" identifiers for the model pages, and an identifier like "iPad3,4" may confuse someone into thinking it's a model of the [[iPad 3]]. (I would still like to use the A1XXX numbers since Apple does that, but nobody else seems to agree now…) I'll give this a few more days for any last words before acting on it. --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 04:03, 26 December 2013 (UTC)
::It '''will''' get changed before the year ends. I don't know why your opinion keeps changing, but I have already explained the reason for changing it. You even agreed that it needs to be changed. I'm still open to suggestions on what to change it to though. Keep in mind that the change will affect not only key pages, but also how the devices will be referred to throughout the wiki. --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 19:34, 26 December 2013 (UTC)
:::I know it will. I said it is fine to change. I like bot #3 and #4. Only point I must make is that I feel we should change all devices with multiple variants, including iPad Air and iPhone 4. This way, it is consistent and also removes GSM etc altogether. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 19:48, 26 December 2013 (UTC)
::I agree with Adam, if you're going to change some of them then change all of them. This includes iPods. Whatever the outcome, be consistent. As for the outcome itself, I really think we should just use device identifiers (iPhone2,1). That's what we're actually differentiating by, so it only makes sense to refer to devices by them. I don't think there would be any confusion, especially considering we'll keep the name of the device next to it regardless. Barring that, the next best option is ***ap. The other options don't make any sense considering modern devices. --[[User:CompilingEntropy|CompilingEntropy]] ([[User talk:CompilingEntropy|talk]]) 10:54, 30 December 2013 (UTC)

== Key page template ==
I actually like the idea of a database to an extent. I bet I could put together an extension that creates a [[Special:SpecialPages|special page]] that allows read access to everyone (and r/w access to users). Any edits to the key "pages" wouldn't cause a [[Special:RecentChanges|recent changes]] log. If we ever needed to update the layout, we would just need to update the extension. We could even have an API.
The only limitation is that updates to the extension would require either [[User:geohot|George]] or [[User:Dialexio|Alex]] needing to upload the fix. If we were to set up an external site, then all links to it would need to be wrapped with <code>...</code>.
Maybe a simple extension that takes links and redirects you to the external site? That could work. Like, we would have a link to, say, <code>[[<nowiki/>Special:Keys/iPad1,1/9A405]]</code> which would give an HTTP <code>301 Moved Permanently</code> header to, say, <code><nowiki>http://ioskeys.com/iPad1,1/9A405</nowiki></code>. Granted, someone would have to pay for the domain, but it would solve this problem. I may be able to pay for the domain if I make enough money by the time I finish writing everything. Any opposition? --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 16:48, 21 November 2013 (UTC)
:I do not like the idea. I like the idea of the database to a degree, but I think that the pages should remain on this wiki. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 17:03, 21 November 2013 (UTC)
::I don't see this solving any problem— the backlash against changing the key page template was because of (unnecessary?) changes to the arguments, and the frequency of how often such changes were being proposed/applied. How would a database prevent it? For instance, let's say the database columns are all decided on. Suddenly, it's decided that SHA-1 hashes should be added as well, or perhaps "VFDecryptKey" will be renamed to "FSKey." People submitting keys would still be bothered with having to adjust for those changes. --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 17:40, 21 November 2013 (UTC)
:::That with the database is something I'll implement anyway (if not someone else is faster, as I'm quite busy). I just threw that in here as it might solve the problem of the frequent template updates (which is/was wrong anyway). From there it would be easy to create the VFDecrypt page with an overview link or lists of missing keys and that stuff, so the wiki would not need any direct links. But it would mean that we either completely remove all keys here from the wiki and embrace that solution or have them still duplicate (which then doesn't solve the problem). Dialexio: renaming columns can be handled without interface changes, but that's another topic. So let's forget about this database thing for now and we can discuss again when I have something. We certainly don't want to add extensions for that. So back to the discussion about the renaming: If I understood this correctly, you only want to rename A5+ devices and therefore no key pages would be affected. Is my understanding correct? --[[User:Http|http]] ([[User talk:Http|talk]]) 22:08, 21 November 2013 (UTC)
::::As long as the pages stay on this wiki, I do not mind. Although, a database could be pointless as with only 50 more pages to edit for the new format, there is no planned new format/changes again. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 22:16, 21 November 2013 (UTC)
::::About the renaming, that is correct; I'm only interested in changing the cellular labels on A5/+ devices. (Well, the iPad 2 can remain as-is.) --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 00:02, 22 November 2013 (UTC)
:::::Oh, well that would just make things more complicated/inconsistent. We should do all or none. About the template idea, there is also no need as it is not likely we will change the format again. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 00:35, 22 November 2013 (UTC)
::::::Do we really need to CHANGE THE FORMAT 50 TIMES IN A ROW? The old one before everything was messed with worked fine enough. [[User:Winocm|Winocm]] ([[User talk:Winocm|talk]]) 18:22, 27 November 2013 (UTC)
:::::::It was actually one change, which was completed. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 18:32, 27 November 2013 (UTC)

==Login prompt revision suggestion==
I wrote a suggestion here: [[MediaWiki talk:Loginprompt]] (since I don't have permission to edit [[MediaWiki:Loginprompt]] directly) - I'd be interested in whether it sounds like a good idea to other people. [[User:Britta|Britta]] ([[User talk:Britta|talk]]) 01:00, 8 October 2013 (UTC)

==Homepage suggestions==
Under "Application Development", what about linking to [http://iphonedevwiki.net/index.php/Main_Page iPhoneDevWiki]? It's also a community-edited technical resource, and it links to this wiki. It could be helpful to add a little more detail to "Get [[up to speed]] in the community.", like this: "Get [[up to speed]] in the community - learn about how jailbreaks work." Under "Definitions", it could be helpful to list all the firmware tags in one line or sub-list, similar to how Jailbreak is organized next to Tethered jailbreak and Untethered jailbreak, both to save space and help readers understand the list. --[[User:Britta|Britta]] ([[User talk:Britta|talk]]) 23:01, 20 October 2013 (UTC)
:A link to the iPhoneDevWiki sounds good. I wonder if we should have an "External Links" or "Other Resources" section to include links to other sites (such as the [http://blog.iphone-dev.org/ iPhone Dev Team blog]) though. As for the "Up to Speed" page, I feel like the entire page could be reworked a bit— and perhaps even receive a new, clearer name ([[Introduction]]? [[Preface]]? Or something else?)— the current name makes it sound like it's for people that last paid attention to jailbreaking when the App Store didn't exist. And yeah, moving the IMG3 tags to a sub-list sounds like a really good idea. (Admittedly, I actually don't care for its inclusion in the first place, but that's just a personal preference.) --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 00:10, 21 October 2013 (UTC)
::There's already [[Useful Links]] with some links to other core community resources (which could be updated and rearranged) - I was just thinking that it'd be especially useful to link to iPhoneDevWiki prominently since it's likely for TheiPhoneWiki visitors to also be interested in relatively-organized technical information about development. Changing the name of "Up to Speed" sounds fine to me too - that page didn't get much attention since 2008 until I sort of commandeered it to serve as an "intro to jailbreaking" page. :) It could be renamed "getting started", as in "how to get started on learning about research into iOS devices, especially security research (such as jailbreaks)". [[User:Britta|Britta]] ([[User talk:Britta|talk]]) 00:31, 21 October 2013 (UTC)
Also I'd love to see a dedicated section for "Good tasks for new editors", where we could maintain a list of relatively easy/straightforward suggested edits that wouldn't require vast technical knowledge, like updating that links page. Where would that go? Add it as a sub-section of [[The iPhone Wiki:Current events]] and link that section from the homepage or something? Or make a new page? [[User:Britta|Britta]] ([[User talk:Britta|talk]]) 00:40, 21 October 2013 (UTC)

==What is 0x5265c384 in the boot process?==
Does anybody know where <code>0x5265c384</code> points to in the boot process? I haven't been able to find anything on it. --[[User:Ph0enix|Ph0enix]] ([[User talk:Ph0enix|talk]]) 20:14, 23 October 2013 (UTC)

==License for contributions==
This wiki has never had an official license for contributions. Now, IANAL, but IIRC, this means that you can't use ''anything'' posted here unless it qualifies as fair-use. What I propose is that we set a license and add a notice that states that any contributions after a set date are to be licensed under that license (that's kindof a mouthful). I think we should use the [http://creativecommons.org/licenses/by-sa/3.0/ CC-by-SA 3.0] as [[wikipedia:Wikipedia:Text of Creative Commons Attribution-ShareAlike 3.0 Unported License|Wikipedia uses it]], but that's just me. Any ideas? --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 19:53, 9 November 2013 (UTC)
:Well, the edit info already says all this:
Please note that all contributions to The iPhone Wiki may be edited, altered, or
removed by other contributors. If you do not want your writing to be edited mercilessly,
then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public
domain or similar free resource (see The [[:The iPhone Wiki:Copyrights|iPhone Wiki:Copyrights]] for details). '''Do not'''
'''submit copyrighted work without permission!'''
For me, that's enough. I don't need a 50 page license. But if you want to formalize this more, go ahead. --[[User:Http|http]] ([[User talk:Http|talk]]) 20:35, 9 November 2013 (UTC)

:Sounds good. It's good practice to have an official license, just in case any disputes happen someday, and to ensure that it's OK to copy text over to Wikipedia (for example). [[User:Britta|Britta]] ([[User talk:Britta|talk]]) 21:32, 9 November 2013 (UTC)

==Future plans==
Now that I have SSH access, I've begun working on making several, somewhat-overdue changes to the wiki. The Renameuser extension was reinstated, so admins can now rename accounts. If you have another account, that can also get merged into your current account. If you happen to get locked out from both your account and the email used is no longer active, I can run a script to reset your password. I've also begun implementing a very noticeable change— as users of the Vector skin have noticed, the iOS 6-based theming is gone. It's a semi-temporary move though; it's going into its own skin, because… you know, choice is cool. People who like the Vector skin may not have liked the iOS theming, especially since IE 9 and lower didn't display it completely accurately. Therefore, it's going into its own theme. Once that's done I also plan on making a separate iOS 7-based skin. If there are any further thoughts or suggestions on how to improve the wiki, do let me know! --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 22:18, 9 November 2013 (UTC)

== #we r of #WONDER ==
<nowiki/>#we r hav from of #QUESTIN holme ! #we r from of #WONDER #what is of #RESON in of #EDIT #wikeee ? #tanks and of RT #RT Smiley Smiley :) :) 
<nowiki/>#we r of #WONDER ! #is from also #of #WAKIKIKI #open src :) #is avalable under from of #FRE license ? --[[User:UnthreadedJB|UnthreadedJB]] ([[User talk:UnthreadedJB|talk]]) 21:11, 1 December 2013 (UTC)

:See [[#License for contributions]] above; no formal license for the content at the moment, and it'd be nice to get more opinions on this from other editors. [[User:Britta|Britta]] ([[User talk:Britta|talk]]) 22:47, 1 December 2013 (UTC)

==Banner Replacement?==
I kinda feel like the banner on the front page is getting a little stale, so I'm interested in seeing it replaced. I tossed a proposal [https://twitter.com/Draxelf/status/408295008794845184 on Twitter] a couple of days ago (which is admittedly plain, but Myriad Set…), but I haven't heard any opinions on replacing the banner. Are there any thoughts on this matter? --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 17:42, 6 December 2013 (UTC)
:Or, [http://imgur.com/wJFqPl1 this]. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 18:22, 6 December 2013 (UTC)

:Looks nice in Myriad! More professional. [[User:Britta|Britta]] ([[User talk:Britta|talk]]) 04:01, 7 December 2013 (UTC)

Scam Jailbreaks and Unlocks

2013-11-29T16:52:28Z

CompilingEntropy: move how-jailbreak-iphone.com as it appears to also scam with unlocks

This is an incomplete list of community-reported scam sites that pretend to distribute or sell jailbreaking and unlocking tools/services. (There are tons of other scam sites not listed here yet.)

If you see a site selling jailbreaking or unlocking software (or asking you to do a survey before downloading), it's a scam. Some legitimate forms of unlocking are not free - third-party IMEI unlocks and SIM interposer devices both cost money - but ultrasn0w is always free.

Please contribute to this list if you find a scam site. By listing them here, we can help people find good information when they search Google for more information about these sites. (If your site is listed here and you believe that's a mistake, you can register an account and remove it from the list.)

Make sure not to link to these pages, as all links will boost their Google ranking.

== Jailbreak fakes ==

{| class="wikitable"
|-
! Domain !! Notes
|-
| 7jailbreak.com || On-device survey scam
|-
| alphajailbreak.com || Survey scam
|-
| alpinejb.blogspot.com || Fake
|-
| celtikios7.com || Survey scam
|-
| downgradeiphone.com || Sells a false promise (universal iOS/baseband downgrade) for $29
|-
| equsi0n.com || Survey scam
|-
| evad3rsdevteam.com || Survey scam, copy of evasi0n.com
|-
| evad3rs-devteam.com || Copy of evasi0n.com
|-
| evad3rsteam.com || Survey scam
|-
| evasi0nblog.com || Repackaged evasi0n
|-
| evasi0ndevteam.com || Sells evasi0n for $15
|-
| evasi0njb.net || Copy of evasi0n.com
|-
| evasion-jailbreak.com || Survey scam
|-
| evasion-jailbreak7.com || Survey scam
|-
| evasi0n-jailbreak.net || Survey scam, copy of evasi0n.com
|-
| evasionjailbreak.net || Survey scam, copy of evasi0n.com
|-
| evasi0n-official.com || Survey scam, loosely copied from evasi0n.com
|-
| evasl0n.blogspot.com || Survey scam, copy of evasi0n.com
|-
| ex0dus-jailbreak.com || Unspecified tool, claims to be developed by @planetbeing and @pimskeks. Survey scam after being strung along downloading a fake tool which requires a patch, said patch download requiring survey completion.
|-
| factory-directme.com || Sells redsn0w for $14.95
|-
| firest0rm.net || Survey scam
|-
| freed0md00r.com || Survey scam
|-
| future7ios7.com || Survey scam
|-
| getthebest365.com || Sells unspecified tool for $27.00
|-
| icysn0w.com || Survey scam
|-
| ievad3rs.com || Survey scam
|-
| ijailbreak-iphone.com || Sells an unspecified tool for $19.95
|-
| ijailbreaktool.com || Sells an unspecified tool for $24.99
|-
| ineedjailbreak.com || Sells evasi0n / redsn0w for $24.95
|-
| inj3ct3d.klikkit.co.uk || asking for donations to publish a non-existent jailbreak
|-
| ios-6-1-4-jailbreak.com || Survey scam
|-
| ipadjailbreak3.com || Forwards to jailbreakunlock.org
|-
| iphone5break.com || Sells unspecified tool for $49.99
|-
| iphonejailbreakplus.com || Sells evasi0n / redsn0w for $29.95
|-
| iphonejailbreak-unlock.com || Sells unspecified tool for $27.00
|-
| jailbreak-absinthe.com || Survey scam
|-
| jailbreak-ios-7.com || Tells people to go to thejailbreakshop.com
|-
| jailbreak-my-ipad.org || Sells evasi0n / redsn0w for $29.95 '''per month'''
|-
| jailbreak-team.com || Sells an unspecified tool for $29.99
|-
| jailbreakandunlock1.pressdoc.com || Blog that is about jailbreak and unlock which uses fake tools.
|-
| jailbreakbj.com || Survey scam
|-
| jailbreakios7untethered.com || Survey scam, all set up in advance for iOS 7
|-
| jailbreakiphone5s.com || Tells people to go to thejailbreakshop.com
|-
| jailbreaknewiphone.com || Survey scam after being strung along downloading a fake tool
|-
| jailbreakunlock.info || Sells unspecified tools for $19.95, $29.95, and $39.95
|-
| jailbreakunlock.org || Sells evasi0n / redsn0w for $14.95
|-
| latestiphoneunlock.com || Sells an unspecified tool for $9.95 or $29.95
|-
| newios7jailbreak.com || Directs visitors to unlock-jailbreak.net
|-
| overcast7.com || Survey scam
|-
| pod2gblog.blogspot.com || Copy of pod2g's blog
|-
| purpletools.wordpress.com and all the other sites/people offering similar stuff || Scam - It sells [[PurpleRestore]] and other internal tools at high price promising they'll allow to downgrade any device/firmware and to install any firmware on any device (e.g. [[iOS]] 6.1.3 on [[iPhone 3G]]).
|-
| redpois0n.net || Survey scam
|-
| redsn0w-r9-new.blogspot.com || Survey scam, text is ripped from Dev-Team Blog
|-
| rocky-racoon.com || Survey scam, copy of Dev-Team Blog
|-
| safera1n.com || Sells an unspecified tool for $24.99
|-
| silv3rwind.com || Sells an unspecified tool for $20
|-
| synergyjailbreak.com || Survey scam
|-
| team7jailbreak.com || On-device survey scam (redirects to 7jailbreak.com)
|-
| theios7jailbreaker.com || Directs people to scam sites (ijailbreakpro.com, appleunlocker.com, ijailbreaktool.com)
|-
| thejailbreakshop.com || Sells an unspecified tool for $29.97 and $49.97
|-
| u7xjailbreak.com || Survey scam
|-
| unja1l.com || Survey scam
|-
|}

== Scam jailbreak and unlock sites ==

{| class="wikitable"
|-
! Domain !! Notes
|-
| appleunlocker.com || Sells unspecified jailbreaking + unlocking software for $19.95
|-
| cheapestiphoneunlock.com || Sells unspecified jailbreaking + unlocking software for $9.99
|-
| deblocage-iphone-fr.com || Sells unspecified unlocking software for €29.99
|-
| desbloquear-iphone-pro.com || Sells unspecified unlocking software for €29.99
|-
| e-imeiunlock.com || Survey scam
|-
| easyiphoneunlocking.com || Sells unspecified jailbreaking + unlocking software for $24.95
|-
| easyunlockiphone.net || Sells unspecified jailbreaking + unlocking software for $24.99
|-
| easyunlockingsolutions.com || Sells unspecified unlocking software for $19.99
|-
| how-jailbreak-iphone.com || Sells unspecified jailbreaking + unlocking software for $19.95
|-
| ijailbreakpro.com || Sells redsn0w for $29.90, $39.90, or $49.90
|-
| ios7jailbreaker.net || Survey scam
|-
| ios7jailbreak.fr || Survey scam
|-
| iphone5break.com || Sells unspecified jailbreaking + unlocking software for $49.99
|-
| iphone-instant-unlock.com || Sells unspecified unlocking software for $14.95
|-
| iphone-unlock-pro.com || Redirects to unlock4iphone.com, desbloquear-iphone-pro.com, and deblocage-iphone-fr.com
|-
| iphone-unlocker-pro.com || Sells unspecified jailbreaking + unlocking software for $24.95
|-
| iphone-unlock-me.com || Sells unspecified unlocking software for $14.95
|-
| iphone-unlockme.com || Sells unspecified unlocking software for $14.95
|-
| iphoneunlocker.org.uk || Sells unspecified jailbreaking + unlocking software for £14.99
|-
| iphoneunlockersoftware.com || Sells unspecified jailbreaking + unlocking software for $24.97
|-
| iphoneunlockplus.com || Sells unspecified unlocking software for $22.99
|-
| iphoneunlockwiz.com || Sells unspecified jailbreaking + unlocking software for $29.97
|-
| myappledownload.com || Sells undefined non-existing jailbreaks, unlocks, downgrades for $19.99
|-
| phoneunlockguy.com || Sells unspecified jailbreaking + unlocking software for $14.95
|-
| solutions-directme.com || Sells unspecified jailbreaking software for $14.95
|-
| superiorsim.com || Sells SIM interposers, reported to be a scam by various websites
|-
| superunlockiphone.com || Sells unspecified jailbreaking + unlocking software for £14.99
|-
| transx-solutions.com || Sells software for $14.95 which does not say what it is. Also requires a download
|-
| trusted-iphone-unlocker.com || Sells unspecified jailbreaking + unlocking software for $24.95
|-
| ultimateiphoneunlocker.com || Sells unspecified unlocking software for $19.95
|-
| unlock4iphone.com || Sells unspecified unlocking software for $29.99
|-
| unlock-apple-iphone.com || Sells unspecified jailbreaking + unlocking software for $29.99
|-
| unlockiphone.org || Sells unspecified unlocking software for $24.95
|-
| unlock-ijailbreak.net || Added a letter to the URL, otherwise it's the same site as unlock-jailbreak.net
|-
| unlock-jailbreak.net || Sells unspecified unlocking software for $24.99
|-
| unlock-jailbreak-iphone.com || Sells unspecified jailbreaking + unlocking software for $24.99
|-
| unlock-the-iphone.com || Sells unspecified jailbreaking + unlocking software for $29.95, $37.95, or $49
|-
| unlockimeiiphone.com || Sells unspecified jailbreaking + unlocking tool for $19.95
|-
| unlockiphone.net || Sells unspecified jailbreaking + unlocking tool
|-
| unlockiphoneios5.com || Sells unspecified jailbreaking + unlocking software for $14.95
|-
| unlockiphonenow.org || Sells unspecified jailbreaking + unlocking software for $24.99
|-
| unlockiphonepro.com || Sells unspecified jailbreaking + unlocking software for $24.99
|-
| ultrasn0wtool.com || Claims to unlock via a GUI app
|-
| ziphone.org || Directs visitors to easyiphoneunlocking.com
|}

Scam Jailbreaks and Unlocks

2013-11-29T16:50:38Z

CompilingEntropy: added how-jailbreak-iphone.com

This is an incomplete list of community-reported scam sites that pretend to distribute or sell jailbreaking and unlocking tools/services. (There are tons of other scam sites not listed here yet.)

If you see a site selling jailbreaking or unlocking software (or asking you to do a survey before downloading), it's a scam. Some legitimate forms of unlocking are not free - third-party IMEI unlocks and SIM interposer devices both cost money - but ultrasn0w is always free.

Please contribute to this list if you find a scam site. By listing them here, we can help people find good information when they search Google for more information about these sites. (If your site is listed here and you believe that's a mistake, you can register an account and remove it from the list.)

Make sure not to link to these pages, as all links will boost their Google ranking.

== Jailbreak fakes ==

{| class="wikitable"
|-
! Domain !! Notes
|-
| 7jailbreak.com || On-device survey scam
|-
| alphajailbreak.com || Survey scam
|-
| alpinejb.blogspot.com || Fake
|-
| celtikios7.com || Survey scam
|-
| downgradeiphone.com || Sells a false promise (universal iOS/baseband downgrade) for $29
|-
| equsi0n.com || Survey scam
|-
| evad3rsdevteam.com || Survey scam, copy of evasi0n.com
|-
| evad3rs-devteam.com || Copy of evasi0n.com
|-
| evad3rsteam.com || Survey scam
|-
| evasi0nblog.com || Repackaged evasi0n
|-
| evasi0ndevteam.com || Sells evasi0n for $15
|-
| evasi0njb.net || Copy of evasi0n.com
|-
| evasion-jailbreak.com || Survey scam
|-
| evasion-jailbreak7.com || Survey scam
|-
| evasi0n-jailbreak.net || Survey scam, copy of evasi0n.com
|-
| evasionjailbreak.net || Survey scam, copy of evasi0n.com
|-
| evasi0n-official.com || Survey scam, loosely copied from evasi0n.com
|-
| evasl0n.blogspot.com || Survey scam, copy of evasi0n.com
|-
| ex0dus-jailbreak.com || Unspecified tool, claims to be developed by @planetbeing and @pimskeks. Survey scam after being strung along downloading a fake tool which requires a patch, said patch download requiring survey completion.
|-
| factory-directme.com || Sells redsn0w for $14.95
|-
| firest0rm.net || Survey scam
|-
| freed0md00r.com || Survey scam
|-
| future7ios7.com || Survey scam
|-
| getthebest365.com || Sells unspecified tool for $27.00
|-
| how-jailbreak-iphone.com || Sells an unspecified tool for $19.95
|-
| icysn0w.com || Survey scam
|-
| ievad3rs.com || Survey scam
|-
| ijailbreak-iphone.com || Sells an unspecified tool for $19.95
|-
| ijailbreaktool.com || Sells an unspecified tool for $24.99
|-
| ineedjailbreak.com || Sells evasi0n / redsn0w for $24.95
|-
| inj3ct3d.klikkit.co.uk || asking for donations to publish a non-existent jailbreak
|-
| ios-6-1-4-jailbreak.com || Survey scam
|-
| ipadjailbreak3.com || Forwards to jailbreakunlock.org
|-
| iphone5break.com || Sells unspecified tool for $49.99
|-
| iphonejailbreakplus.com || Sells evasi0n / redsn0w for $29.95
|-
| iphonejailbreak-unlock.com || Sells unspecified tool for $27.00
|-
| jailbreak-absinthe.com || Survey scam
|-
| jailbreak-ios-7.com || Tells people to go to thejailbreakshop.com
|-
| jailbreak-my-ipad.org || Sells evasi0n / redsn0w for $29.95 '''per month'''
|-
| jailbreak-team.com || Sells an unspecified tool for $29.99
|-
| jailbreakandunlock1.pressdoc.com || Blog that is about jailbreak and unlock which uses fake tools.
|-
| jailbreakbj.com || Survey scam
|-
| jailbreakios7untethered.com || Survey scam, all set up in advance for iOS 7
|-
| jailbreakiphone5s.com || Tells people to go to thejailbreakshop.com
|-
| jailbreaknewiphone.com || Survey scam after being strung along downloading a fake tool
|-
| jailbreakunlock.info || Sells unspecified tools for $19.95, $29.95, and $39.95
|-
| jailbreakunlock.org || Sells evasi0n / redsn0w for $14.95
|-
| latestiphoneunlock.com || Sells an unspecified tool for $9.95 or $29.95
|-
| newios7jailbreak.com || Directs visitors to unlock-jailbreak.net
|-
| overcast7.com || Survey scam
|-
| pod2gblog.blogspot.com || Copy of pod2g's blog
|-
| purpletools.wordpress.com and all the other sites/people offering similar stuff || Scam - It sells [[PurpleRestore]] and other internal tools at high price promising they'll allow to downgrade any device/firmware and to install any firmware on any device (e.g. [[iOS]] 6.1.3 on [[iPhone 3G]]).
|-
| redpois0n.net || Survey scam
|-
| redsn0w-r9-new.blogspot.com || Survey scam, text is ripped from Dev-Team Blog
|-
| rocky-racoon.com || Survey scam, copy of Dev-Team Blog
|-
| safera1n.com || Sells an unspecified tool for $24.99
|-
| silv3rwind.com || Sells an unspecified tool for $20
|-
| synergyjailbreak.com || Survey scam
|-
| team7jailbreak.com || On-device survey scam (redirects to 7jailbreak.com)
|-
| theios7jailbreaker.com || Directs people to scam sites (ijailbreakpro.com, appleunlocker.com, ijailbreaktool.com)
|-
| thejailbreakshop.com || Sells an unspecified tool for $29.97 and $49.97
|-
| u7xjailbreak.com || Survey scam
|-
| unja1l.com || Survey scam
|-
|}

== Scam jailbreak and unlock sites ==

{| class="wikitable"
|-
! Domain !! Notes
|-
| appleunlocker.com || Sells unspecified jailbreaking + unlocking software for $19.95
|-
| cheapestiphoneunlock.com || Sells unspecified jailbreaking + unlocking software for $9.99
|-
| deblocage-iphone-fr.com || Sells unspecified unlocking software for €29.99
|-
| desbloquear-iphone-pro.com || Sells unspecified unlocking software for €29.99
|-
| e-imeiunlock.com || Survey scam
|-
| easyiphoneunlocking.com || Sells unspecified jailbreaking + unlocking software for $24.95
|-
| easyunlockiphone.net || Sells unspecified jailbreaking + unlocking software for $24.99
|-
| easyunlockingsolutions.com || Sells unspecified unlocking software for $19.99
|-
| ijailbreakpro.com || Sells redsn0w for $29.90, $39.90, or $49.90
|-
| ios7jailbreaker.net || Survey scam
|-
| ios7jailbreak.fr || Survey scam
|-
| iphone5break.com || Sells unspecified jailbreaking + unlocking software for $49.99
|-
| iphone-instant-unlock.com || Sells unspecified unlocking software for $14.95
|-
| iphone-unlock-pro.com || Redirects to unlock4iphone.com, desbloquear-iphone-pro.com, and deblocage-iphone-fr.com
|-
| iphone-unlocker-pro.com || Sells unspecified jailbreaking + unlocking software for $24.95
|-
| iphone-unlock-me.com || Sells unspecified unlocking software for $14.95
|-
| iphone-unlockme.com || Sells unspecified unlocking software for $14.95
|-
| iphoneunlocker.org.uk || Sells unspecified jailbreaking + unlocking software for £14.99
|-
| iphoneunlockersoftware.com || Sells unspecified jailbreaking + unlocking software for $24.97
|-
| iphoneunlockplus.com || Sells unspecified unlocking software for $22.99
|-
| iphoneunlockwiz.com || Sells unspecified jailbreaking + unlocking software for $29.97
|-
| myappledownload.com || Sells undefined non-existing jailbreaks, unlocks, downgrades for $19.99
|-
| phoneunlockguy.com || Sells unspecified jailbreaking + unlocking software for $14.95
|-
| solutions-directme.com || Sells unspecified jailbreaking software for $14.95
|-
| superiorsim.com || Sells SIM interposers, reported to be a scam by various websites
|-
| superunlockiphone.com || Sells unspecified jailbreaking + unlocking software for £14.99
|-
| transx-solutions.com || Sells software for $14.95 which does not say what it is. Also requires a download
|-
| trusted-iphone-unlocker.com || Sells unspecified jailbreaking + unlocking software for $24.95
|-
| ultimateiphoneunlocker.com || Sells unspecified unlocking software for $19.95
|-
| unlock4iphone.com || Sells unspecified unlocking software for $29.99
|-
| unlock-apple-iphone.com || Sells unspecified jailbreaking + unlocking software for $29.99
|-
| unlockiphone.org || Sells unspecified unlocking software for $24.95
|-
| unlock-ijailbreak.net || Added a letter to the URL, otherwise it's the same site as unlock-jailbreak.net
|-
| unlock-jailbreak.net || Sells unspecified unlocking software for $24.99
|-
| unlock-jailbreak-iphone.com || Sells unspecified jailbreaking + unlocking software for $24.99
|-
| unlock-the-iphone.com || Sells unspecified jailbreaking + unlocking software for $29.95, $37.95, or $49
|-
| unlockimeiiphone.com || Sells unspecified jailbreaking + unlocking tool for $19.95
|-
| unlockiphone.net || Sells unspecified jailbreaking + unlocking tool
|-
| unlockiphoneios5.com || Sells unspecified jailbreaking + unlocking software for $14.95
|-
| unlockiphonenow.org || Sells unspecified jailbreaking + unlocking software for $24.99
|-
| unlockiphonepro.com || Sells unspecified jailbreaking + unlocking software for $24.99
|-
| ultrasn0wtool.com || Claims to unlock via a GUI app
|-
| ziphone.org || Directs visitors to easyiphoneunlocking.com
|}

The iPhone Wiki:Community portal

2013-11-23T18:40:57Z

CompilingEntropy: /* "GSM" Replacement Proposals */

{{Talk Archive}}
{{see also|Unsolved problems}}
==iPhone-Elite==
I think we should include all this old stuff before it gets lost: [http://code.google.com/p/iphone-elite/ code.google.com/p/iphone-elite/]. I mean the wiki articles there. Most infos should be already here, but I'm sure a lot of things are missing too.
--[[User:Http|http]] 15:02, 26 June 2012 (MDT)

==Boot-args cleanup==
We need to clean up the boot-args pages. First the technical part: What I understand is that iBoot loads the kernel. And when loading it, it can pass some parameters to select certain behavior. So this only works with an iBoot or bootrom exploit. I understand that in earlier firmware versions there was simply an iBoot variable, but that doesn't exist or work anymore, now passing theses args requires a different or patched iBoot. There are various parameters in different kernel versions. The description for these arguments is scattered over various places:
*[[Kernel#Boot-Args]] A section with the latest boot arguments list. This should be a short introduction and having a link "main article".
*[[Boot-args (iBoot variable)]] separate page for boot arguments, but mainly for the iBoot variable that doesn't exist any longer
*[{{FULLURL:Boot arguments|redirect=no}} Boot arguments] (redirect)
*[[:Talk:Restore_Mode]] describing the iBoot variable problem
*Various pages referencing boot-args, like [[Research: Re-allowing unsigned ramdisks and boot-args with the 2.* iBoot]] (here we should have a link on the second title)
*My earlier comment [[:Talk:Kernel#boot-args]]
*This comment here.
So what do we want to do about this mess? I suggest to move the current [[Kernel]] content to the redirect page [[Boot arguments]] (or to another new page, maybe [[boot-args]]). The current content of [[Boot-args (iBoot variable)]] and all other content should get merged into there. Then change all references to this new page and on the [[Kernel]] page write just something short with "main article there". What do you think? --[[User:Http|http]] ([[User talk:Http|talk]]) 21:31, 13 February 2013 (UTC)
:I like [[Boot Arguments]]. --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 02:01, 14 February 2013 (UTC)
::One addition: Maybe we should use [[boot-args]] as the main page, because all links are written like that. --[[User:Http|http]] ([[User talk:Http|talk]]) 07:37, 14 February 2013 (UTC)

==The iPhone Wiki re-design==
The design of the iPhone wiki is now quite old and I think it should be updated. I made a [http://oi42.tinypic.com/30ib9y8.jpg concept]. --[[User:Jaggions|Jaggions]] ([[User talk:Jaggions|talk]]) 10:30, 14 June 2013 (UTC)
:I disagree. If anything add an iPhone 5 to the logo but everything else is ok. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 11:05, 14 June 2013 (UTC)
:I wouldn't change the logo to an iPhone 5, especially with iOS 7 and a new iPhone (that will probably look the same as the 5, admittedly) around the corner. I contemplated updating the CSS for iOS 7's UI but decided not to because of the UI's supposed volatility (during the beta period) and I don't have a live version to toy around with. (I personally don't like its current state, but that's not a factor in why I'm not changing it yet.) --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 16:25, 14 June 2013 (UTC)
::Can we not do flat? --[[User:Haifisch|Haifisch]] ([[User talk:Haifisch|talk]]) 21:02, 14 June 2013 (UTC)
::This is what I was thinking. When iOS 7 finally comes out, we could change the CSS to look like that instead. --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 21:11, 14 June 2013 (UTC)
:::iOS 7 looks ugly. We do not want it like that. Maybe a bit more modern but nothing much. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 21:16, 14 June 2013 (UTC)
::::''You'' may not want it like that. That's your opinion. --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 01:55, 15 June 2013 (UTC)
:::::We could make a poll, and see if most users agree or disagree. --[[User:Jaggions|Jaggions]] ([[User talk:Jaggions|talk]]) 10:05, 15 June 2013 (UTC)
:The idea looks nice. But before we make any changes, let's wait until iOS7 comes out. And I'd prefer to just add another skin instead (if possible). I'm still using the classic MonoBook skin by the way. You shouldn't impose design changes to everyone. --[[User:Http|http]] ([[User talk:Http|talk]]) 14:38, 15 June 2013 (UTC)
::The problem with skins is that geohot needs to set them up... An idea I have is that we copy the Vector skin verbatim to a new skin (<code>iOS6</code>) and move the modifications (not general stuff) to [[Mediawiki:iOS6.css]]. Then we can do another verbatim copy to <code>iOS7</code> and modify [[Mediawiki:iOS7.css]]. We could then set the default skin to either <code>iOS6</code> or <code>iOS7</code> so you don't need to be logged in to see them like currently. Then if someone doesn't like them, like you, just change your settings to your preferred skin. The only way around needing geohot is if he opens up the credentials to FTP or whatever to someone. --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 21:17, 15 June 2013 (UTC)
:::I like [[User:5urd|5urd]]'s suggestion. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 22:29, 15 June 2013 (UTC)
What about just removing the text-shadow element for now? I think pages would be easier to read without it. Here's an example: [[:File:Noshadow.png]]. [[User:Britta|Britta]] ([[User talk:Britta|talk]]) 00:11, 29 August 2013 (UTC)
:Yeah removing the shadow will make everything seem more flat but like [[User:http|http]] I'm still using the classic [http://theiphonewiki.com/w/index.php?title=Main_Page&useskin=monobook MonoBook skin] --[[User:Jaggions|Jaggions]] ([[User talk:Jaggions|talk]]) 21:19, 31 August 2013 (UTC)

==Hacker page==
I would like to be added to the list of hackers for my work with the Private Dev Team and the [[Chronic Dev (team)|Chronic Dev Team]] in addition to my release of the Phoenix Semi-Untethered. --[[User:Ph0enix|Ph0enix]] ([[User talk:Ph0enix|talk]]) 18:36, 22 July 2013 (UTC)
:Did you find any exploits? --[[User:Haifisch|Haifisch]] ([[User talk:Haifisch|talk]]) 18:54, 22 July 2013 (UTC)
::No. [[User:phyrrus9|phyrrus9]], a team member found the vulnerability. I am the one who exploited it. --[[User:Ph0enix|Ph0enix]] ([[User talk:Ph0enix|talk]])
:::I can back up this "claim". I was a part of it. --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 20:52, 28 July 2013 (UTC)
::::Whatever happened to this? --[[User:Phyrrus9|phyrrus9]]

==Orphaned articles==
This is an interesting search: [[Special:LonelyPages]] - "The following pages are not linked from or transcluded into other pages in The iPhone Wiki." I'm not sure where all of those articles should be linked, but figuring that out could be a useful project for somebody. [[User:Britta|Britta]] ([[User talk:Britta|talk]]) 05:57, 28 August 2013 (UTC)

==Easy tasks for new editors==
* Finish converting the remaining error codes listed here [[MobileDevice_Library#Known_Error_Codes]] into the proper mach_return_t codes they should be displayed as. (convert the negative number listed into hex, strip any leading "FF" so it should be in the format "0xe80000" followed by two numbers) --[[User:Dirkg|Dirkg]] ([[User talk:Dirkg|talk]]) 22:40, 28 August 2013 (UTC)

== A1XXX model numbers vs. "GSM"/"CDMA"/"Global"/"Cellular"/etc. ==
I know that this topic was [[The iPhone Wiki:Community portal/2013#iPhone 5|already discussed earlier this year]], but it didn't seem to come to a consensus, and the introduction of the [[iPhone 5c]] and [[iPhone 5s]] brought a lot of model numbers. Some of them may "overlap" (think models A1429 and A1442 for the [[iPhone 5]]), but there's simply too many to give names to. There are at least two that can connect to CDMA networks, and all of them can connect to GSM. In addition, with the sheer amount of models, it doesn't seem likely for one model to be treated as a "global" model. Therefore, I changed the iPhone 5c to use model numbers. I would like to do the same to some of the devices that are already present on the wiki though— the same ones from when I first brought up this idea. The GSM/CDMA names work very well for the [[iPad 2]] and [[iPhone 4]]. Things are slightly murkier for the [[iPad 3|iPad (3rd gen.)]], [[iPad 4|iPad (4th gen.)]], [[iPad mini 1G]], and [[iPhone 5]] though; all of those devices' cellular models can connect to GSM networks, so it seems like nonsense to call some of them the "GSM model." The A1XXX model numbers are also how Apple tells the difference between the different models of these devices. Have any opinions changed? Or perhaps someone new might have something to say about this? --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 06:06, 13 September 2013 (UTC)

:I actually like the idea as it does get complicated now with the new devices coming like said and we would have to do this for all devices. Although, if we did this, we would have to move all the key pages that have keys on to support this. That would not be a big problem as we could limit the moves to say 20 per day. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 09:47, 13 September 2013 (UTC)

:I suggest we wait a bit until we see what models of the [[iPhone 5c]] and [[iPhone 5s]] will exist. But in general, I like the idea of using only the A1nnn numbers. The only issue I see right now is that Apple differentiates between A1532 GSM and A1532 CDMA. If there are real hardware differences between these two, then we're screwed again. That's why I suggest to wait until we know these exact model types. On the disambiguation page I added the GSM/CDMA model differentiation already (as Apple does). If they turn out to be the same, we can remove it again, but I wonder why Apple lists two models (with different bands supported) there now. Someone also added the "CDMA" mark to one of the others, but that's not how Apple marks them, so I suggest to remove that mark there again. If everything can be differentiated by these A-model-numbers, then yes, we should change the old pages too. Including all key pages. --[[User:Http|http]] ([[User talk:Http|talk]]) 14:44, 13 September 2013 (UTC)

::I do know there are 2 CDMA and 3-4 GSM for the [[iPhone 5c]] alone. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 16:04, 13 September 2013 (UTC)

:::Ahem… ''All'' of the iPhone 5c models can do GSM communications. Hence one of the reasons why I want to ditch the "GSM"/"Global"/etc. labels in favor of A1XXX model numbers. ;P --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 16:07, 13 September 2013 (UTC)

::::One thing is, what about iPod touch 5 as that has two model numbers that are the same device, same with iPhone5,2. How would we get around that? I suppose we could like both separated with a forward slash. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 18:19, 13 September 2013 (UTC)

:::::Yeah, we could just use something like "[[n42ap|iPhone 5 (Model A1429/A1442)]]." --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 22:45, 13 September 2013 (UTC)

::::::Yeah I thought that but what about the iPhone 4 GSM and GSM Rev A? They both seem to be A1432. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 23:10, 13 September 2013 (UTC)

:::::::This is why I'm against using the A1XXX model numbers instead of the current GSM/Global thing. --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 23:25, 13 September 2013 (UTC)

::::::::I had no plans to change the way we refer to the iPhone 4 or iPad 2 (Apple does use GSM/CDMA, and for those devices it works fine). If a new iPhone 5S revision comes along, Apple will probably refer to it as a "Rev A" thing, and so will we. --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 02:50, 14 September 2013 (UTC)

:Referencing Adam's reply above, if we had took that to the key pages, it'd be <code>[<nowiki/>[{BuildTrain} {Build} (A1432)]]</code> which would mess ''everything'' up. What could we do? Use <code>[<nowiki/>[{BuildTrain} {Build} (A1432 Rev A)]]</code>? No. That doesn't look good. The current way of referring to everything by their supported network type (GSM/CDMA/Global) helps in going to a different page.
:Let's say I'm on [[BrightonMaps 10B329 (iPhone 4 GSM)]] and I want to go the CDMA device. What do I do? Go to the URL and replace <code>GSM</code> with <code>CDMA</code>. With the model numbers, I'd have to navigate to [[Firmware]], then find the link, or find out what the model number of the CDMA variant is and replace the model number in the URL with that. 
:Ok, who navigates by the URL and search bar? ''I do''. And I'm sure there's '''many''' people out there that prefer to navigate with the search bar if they know the page name. If we go by model number, the AJAX search results just list pages with a model number in parenthesis. '''How does that help'''? I'd either have to ''know'' the model number of the device I want, or visit ''each one'' until I find the page I need.
:Sorry for the rant, but I am '''strongly''' against this. --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 23:25, 13 September 2013 (UTC)

::I do suppose we could just trash the buildtrain all together to shorten it down too. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 23:32, 13 September 2013 (UTC)

:::Dropping the Build Train would only ''increase'' the workload. Besides, what's the harm with it? We've been using the same page title structure since forever, and it's worked. "''If it ain't broke, don't fix it''". The current system works, so ''why'', other than the fact that Apple refers to them differently, should we change this? In addition, we don't refer to everything the way Apple does. The [[iPad mini 1G]] is referred to as the "iPad mini". The [[iPad 3]] is refered to as "The New iPad". The [[iPad 4]] is refered to as "iPad with Retina Display"[http://www.apple.com/ipad/compare/]. Are the key pages titled <code>BrightonMaps 10B329 (The New iPad, Wi-Fi+3G for AT&T and Verizon)</code>? No. --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 00:37, 14 September 2013 (UTC)

::::But the reason we want to not use the variants is because the new devices that are coming out are breaking he structure and also CDMA versions can use GSM in the 5c plus we have like 4 for GSM alone. I only meant drop buildtrain to shorten the urls down. For the iPhone 4 GSM Rev A we would have to list it as <code>iPhone 4 A1432 Rev</code> unless another idea is thought of. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 00:55, 14 September 2013 (UTC)

:::::No. Anything involving moving key pages to change their title I am ''completely'' against. As for the iPhone 5s and iPhone 5c, we ultimately have to wait. There may be different types, but if they all work with the same firmware, then what do we do then? Use <code>A1456/A1504</code>? I don't want to do that. It can get confusing in the future if that list were to be huge. With ''5'' different models for the iPhone 5c ''alone'', it's just not practical. For the fact that all support GSM, but not all support CDMA, we just do what we've ''been'' doing: "GSM" and "Global". --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 01:22, 14 September 2013 (UTC)

::::::There's nothing wrong with changing the titles of pages that don't even exist though. If *all* of the models use the same firmware, just go with "iPhone 5s." If they happen to be partitioned into two different firmwares again, that will certainly complicate things, but it wouldn't be worse than nonsense like "GSM," "GSM [<nowiki />Global]," "CDMA," "CDMA [<nowiki />Global]," or "GSM [<nowiki />Global Plus TD-LTE]." If it's just one oddball, we could just have "iPhone 5s" and "iPhone 5s A1XXX" (whatever the odd one is), and include a link on the former page to say "keys for model A1XXX are on this page." --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 02:50, 14 September 2013 (UTC)

::::I probably didn't phrase that well… I wasn't thinking of how Apple markets the product, but rather more along the lines of how they refer to it in, say, the tech specs page or support documents— the pages that shows the messier side to their simple sugar coating. --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 02:50, 14 September 2013 (UTC)

::You keep misinterpreting/misrepresenting what I'm proposing. I never said anything about dropping, say, "iPhone 5" so firmware page titles would look like [[Sundance 10A405 (A1428)]]. I want to change the GSM/Global part to the A1XXX number, so it would probably show like [[Sundance 10A405 (iPhone 5 A1428)]]. (If a hardware revision were made, it would probably look like [[Sundance 10A405 (iPhone 5 A1428 Rev A)]].) From time to time, I edit URLs to browse the wiki too. But the GSM/Global identifiers don't work that well; again, '''all iPhone 5 models can connect to GSM'''. That's not really helpful. --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 02:50, 14 September 2013 (UTC)

:::I suggest we drop the A and use Rev. As for the idea of changing to A1XXX, I see no issues and am for the idea. I admit it can cause chaos when we move the pages but we could limit the moving per day of course. Overall, I think it will be worth it. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 10:01, 14 September 2013 (UTC)

::::No. Don't drop the <code>A</code> from <code>Rev A</code>. Why would you even think to? You want to call them what Apple calls them, and the [[n90bap|revised iPhone 4 GSM]] is referred to with <code>Rev A</code>. In addition, there have been <code>Rev ''B''</code> things before, such as the [[S5L8947]] (A5 Rev B) used in the [[j33iap|revised Apple TV 3G]]. In addition, think of all the redirects we would need to keep for sites that link to key pages directly. I have even seen sites that still link with the URLs as <code>/wiki/index.php?title={Title}</code> instead of the year old change to <code>/wiki/{Title}</code>. The wiki handles that internally for us, but the redirects made in the moves would have to be kept. Currently, only the [[iPhone 5]] and [[iPad 4]] are the only devices referred to by their model numbers. --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 20:53, 14 September 2013 (UTC)

:::That's why I don't want to change it. It's worked for us, and we have no idea how the new firmwares will be handled. I am betting that there will only be two firmware types - one for the GSM, and one for the Global (GSM+CDMA) model. The only reason they are split, IIRC, is because AT&T uses different LTE bands than rest of the GSM world.
:::Ultimately, the GSM/CDMA/Global monikors haven't caused any ''naming conflicts''. Ok, you don't want to use the ''marketing'' title. What about the way they are referred to on [[Apple Developer Center|ADC]], because that seems to be what you want. I may be misreading what you're saying again, but if we're going to do that, let's use their ''full'' title. Something <code>(iPad [4th generation Model A1458])</code> (iPad 4 Wi-Fi) and <code>(iPad Wi-Fi + Cellular [model for Verizon])</code> (iPad 3 Global). Does the first one tell you if the device is Wi-Fi or a Wi-Fi+3G model? Does the second one tell you ''at all'' that it is an [[iPad 3]], or that it supports GSM? No.
:::Apple has a history of being inconsistent. For example, the iPad 3 Wi-Fi is referred to on ADC (and iTunes) as "iPad Wi-Fi (3rd generation)" while the iPad 3 GSM is referred to as "iPad Wi-Fi + Cellular [model for AT&T]". What happened to the "3rd generation"? --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 20:53, 14 September 2013 (UTC)

::::We could always list as <code>iPhone 4 (iPhone3,1)</code> etc instead if that would be better. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 21:13, 14 September 2013 (UTC)

::::Why is there a need to explicitly keep "Wi-Fi" in a key page's title? All you need is a way to distinguish what model it is from its other variants— the A1XXX model number does just that. It's not like we referred to the AppleTV3,2 as "Apple TV 3G (New Single-Core A5)" or something. And obviously, we can use common sense to address the 3rd generation iPad issue you brought up… Now you're just nitpicking. --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 05:28, 15 September 2013 (UTC)
:::::Actually, I think we should wait until we see the firmware for iPhone 5c/5s and then decide. TBH, as [[User:5urd|5urd]] said, it is ok as it is but of course if once the new firmware is out it is more confusing, then we can think again. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 14:12, 15 September 2013 (UTC)

:::::Come to think of it, we can use a mix of both; we can keep the "Global" moniker, but drop the "GSM" moniker in favor of the A1XXX model number. (The "GSM" moniker is the one that's been bothering me.) I think this works well for the iPad 3 (which is actually split into "CDMA" and "Global—" it probably doesn't need to be done for this), iPad 4, iPad mini 1G, and iPhone 5, but this leaves the question of what to do for the iPhone 5C/5S. --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 04:04, 19 September 2013 (UTC)

::::::That would look worse! If we are going to do it, we have to do it for '''''all'''''. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 09:40, 19 September 2013 (UTC)

:::::::What is the status on this now? --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 21:18, 9 November 2013 (UTC)

:::::This discussion has stagnated, but I'm firing it up again— I want to fix this before the end of the year, so this can probably be seen as an ultimatum. Now that Apple has pushed a 7.1 beta to developers, we now know how Apple's splitting the new iPhones up— and it's by A1XXX model numbers still. :\ That's probably the path the wiki will go down, but I do have another idea. The other idea I have in mind is using the A1XXX model number for the cellular devices launched last year. But for this year's iPhones, the FCC ID is actually different between the two, so we could actually use that. Before this gets nitpicked on, the last letter can get changed to an "X" to signify that it's a wildcard of sorts. It's not a pretty solution so I do expect it to get shot down (hence why I'm going with the A1XXX model numbers unless everyone says otherwise), but I'm still throwing it out there in case everyone actually likes that. Everyone is welcome to suggest alternatives, but I '''will''' eliminate that GSM label before the year ends. --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 18:31, 18 November 2013 (UTC)

::::::That is worse, nobody knows the FCC ID off the top of their head. I would suggest "iPhone 5 (iPhone5,1)" if anything. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 18:37, 18 November 2013 (UTC)

:::::::Using "iPhone5,1" or "iPhone6,2" is even ''less'' friendly… The FCC ID can be looked up in Settings or the back of a device. --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 19:06, 18 November 2013 (UTC)

::::::::Well that is not the point. I say either use the firmware name or leave it alone. See what others thing though. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 19:13, 18 November 2013 (UTC)

:::::::::I currently plan on using the A1XXX model numbers— the FCC ID proposal was just thrown out there in the off chance that someone might like it. I'm not really a fan of it myself, but the FCC ID is probably the simplest way to figure out if it's an iPhone6,1 or iPhone6,2 since both have multiple A1XXX model numbers. --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 19:19, 18 November 2013 (UTC)

::::::I agree to get rid of the "GSM" name, as almost all iPhones support GSM. The Axxxx numbers would be nice, but as some phones have several numbers, like A1457/A1518/A1528/A1530 (what is actually different between them?) we can't use it. For the FCC-ID, we can't use that either, because for example the iPhone 5 with FCC-ID BCG-E2599A stands for the GSM/A1428 and also for the GSM+CDMA/A1429 version. So I suggest to either use the identifier (like iPhone2,1) or better the internal name (like n88ap). That would have the advantage to separate them further, because the iPhone 4 A1332 has two internal versions: iPhone3,1/n90ap and the iPhone3,2/n90bap. The bigger question is where you want to use this. That determines mainly the name. On all the key pages? Then it must be a name that is different between models that use different firmwares. And regarding key pages, maybe we should delete all the key pages from this wiki and move them into some database instead and provide a nice user interface and API around it and integrate that into the wiki somehow. That way we can change all pages with one simple edit. For the name, I prefer the internal name. --[[User:Http|http]] ([[User talk:Http|talk]]) 23:43, 18 November 2013 (UTC)

:::::::We would have to edit key pages too. They should not be removed however. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 23:46, 18 November 2013 (UTC)

:::::::Well, I wasn't trying to say that we had to decide on one way to differentiate ''everything''; "GSM" does work fine for, say, the iPhone 4. The proposal I brought up today was using the FCC ID only for this year's (2013's) iPhones— last year's cellular devices would get the A1XXX model numbers (i.e. two different solutions for two different years). But as of right now, I like how using A1XXX model numbers sounds for all of the affected devices, mostly because that's the path Apple's going in their developer portal. Something like "iPhone 5s (Model A1457/A1518/A1528/A1530)" is admittedly a mouthful for this year's iPhones though. At the moment, I'm inquiring about how to label it on [[Firmware]] and such pages, but I'm sure the outcome can be adapted for key page titles as well. As for differences between the models, it seems to be the supported LTE bands. --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 03:49, 19 November 2013 (UTC)

:::::::::I still think that unless it is "iPhone 5 (iPhone5,1)" it will be complicated but on the other hand, I kind of like the idea that [[User:Http|http]] had, using the internal identifiers like this "iPhone 5 (n42ap)". The only problem is that it would cause quite a bit of a flood moving the key pages, although this can be done like 15 per day each or something. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 09:20, 19 November 2013 (UTC)

::::::::::I'm pretty sure the only key page that exists for an A5 (or newer) device is [[Telluride 9A406 (iPhone 4S)]]. --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 17:40, 21 November 2013 (UTC)

:::::::::::That was an example. I know there are no more A5 pages, only the one you said and two beta for iPhone 4S. I just meant that it would show the design. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 13:36, November 21, 2013 (UTC)

== "GSM" Replacement Proposals ==
Since this discussion has become extremely lengthy, here are the proposals (to my understanding) for changing the labels, each of which can be subject to changes (i.e. dropping the word "Model" from Proposal A). In an effort to conserve space (ironically, this still adds a significant amount of length), I only included a few models, which should give an idea of the proposal. Basically anything with an A5 or newer is involved. Feel free to edit this list if I missed or totally misinterpreted something. --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 03:25, 22 November 2013 (UTC)
# Proposal A (A1XXX numbers)
#* iPad 4 (Model A1458)
#* iPad 4 (Model A1459)
#* iPad 4 (Model A1460)
#* iPhone 5 (Model A1428)
#* iPhone 5 (Model A1429/A1442)
#* iPhone 5c (Model A1456/A1532)
#* iPhone 5c (Model A1507/A1516/A1526/A1529)
#* [[InnsbruckTaos 11B554a (iPad 4 A1458)]]
#* [[InnsbruckTaos 11B554a (iPhone 5 A1429/A1442)]]
#* [[InnsbruckTaos 11B554a (iPhone 5c Model A1507/A1516/A1526/A1529)]]
# Proposal B (A1XXX + FCC ID)
#* iPad 4 (Model A1458)
#* iPad 4 (Model A1459)
#* iPad 4 (Model A1460)
#* iPhone 5 (Model A1428)
#* iPhone 5 (Model A1429/A1442)
#* iPhone 5c (BCG‑E2644A)
#* iPhone 5c (BCG‑E2694X)
#* [[InnsbruckTaos 11B554a (iPad 4 A1458)]]
#* [[InnsbruckTaos 11B554a (iPhone 5 A1429/A1442)]]
#* [[InnsbruckTaos 11B554a (iPhone 5c BCG‑E2694X)]]
# Proposal C (-AP Identifier)
#* iPad 4 (p101ap)
#* iPad 4 (p102ap)
#* iPad 4 (p103ap)
#* iPhone 5 (n41ap)
#* iPhone 5 (n42ap)
#* iPhone 5c (n48ap)
#* iPhone 5c (n49ap)
#* [[InnsbruckTaos 11B554a (iPad 4 p101ap)]]
#* [[InnsbruckTaos 11B554a (iPhone 5c n42ap)]]
#* [[InnsbruckTaos 11B554a (iPhone 5c n49ap)]]
# Proposal D (iPhoneX,Y Identifier)
#* iPad 4 (iPad3,4)
#* iPad 4 (iPad3,5)
#* iPad 4 (iPad3,6)
#* iPhone 5 (iPhone5,1)
#* iPhone 5 (iPhone5,2)
#* iPhone 5c (iPhone5,3)
#* iPhone 5c (iPhone5,4)
#* [[InnsbruckTaos 11B554a (iPad3,4)]]
#* [[InnsbruckTaos 11B554a (iPhone5,2)]]
#* [[InnsbruckTaos 11B554a (iPhone5,4)]]

:I like this [[InnsbruckTaos 11B554a iPad 4 (3,4)]] or [[InnsbruckTaos 11B554a iPad 4 (iPad3,4)]]. I see there are 4 ways to approach this;
1. Change every single device. 
2. Change just devices with different variants, iPad 2+, iPad mini+, iPhone 4, iPhone 5+. 
3. Change A5+ only (which I hate the idea of). 
4. Change nothing at all. 
--[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 09:28, 22 November 2013 (UTC)
::My intention for this was to be a ''neutral'' (i.e. opinion-free) spot where all of the proposals were being mentioned, so people could easily see the proposed changes without any bias… v.v --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 20:54, 22 November 2013 (UTC)
:::TBH, I think it is better as it is, but I just stated my opinion that only A5+ would make in inconsistent. Though you could argue it is already, that is down to Apple and furthermore, just A5+ would still not eliminate iPhone 4 (GSM, GSM Rev A or CDMA). --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 17:07, November 22, 2013‎ (UTC)}}
:Do it like #4, and do them all. --[[User:CompilingEntropy|CompilingEntropy]] ([[User talk:CompilingEntropy|talk]]) 18:40, 23 November 2013 (UTC)

== Key page template ==
I actually like the idea of a database to an extent. I bet I could put together an extension that creates a [[Special:SpecialPages|special page]] that allows read access to everyone (and r/w access to users). Any edits to the key "pages" wouldn't cause a [[Special:RecentChanges|recent changes]] log. If we ever needed to update the layout, we would just need to update the extension. We could even have an API.
The only limitation is that updates to the extension would require either [[User:geohot|George]] or [[User:Dialexio|Alex]] needing to upload the fix. If we were to set up an external site, then all links to it would need to be wrapped with <code>...</code>.
Maybe a simple extension that takes links and redirects you to the external site? That could work. Like, we would have a link to, say, <code>[[<nowiki/>Special:Keys/iPad1,1/9A405]]</code> which would give an HTTP <code>301 Moved Permanently</code> header to, say, <code><nowiki>http://ioskeys.com/iPad1,1/9A405</nowiki></code>. Granted, someone would have to pay for the domain, but it would solve this problem. I may be able to pay for the domain if I make enough money by the time I finish writing everything. Any opposition? --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 16:48, 21 November 2013 (UTC)
:I do not like the idea. I like the idea of the database to a degree, but I think that the pages should remain on this wiki. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 17:03, 21 November 2013 (UTC)
::I don't see this solving any problem— the backlash against changing the key page template was because of (unnecessary?) changes to the arguments, and the frequency of how often such changes were being proposed/applied. How would a database prevent it? For instance, let's say the database columns are all decided on. Suddenly, it's decided that SHA-1 hashes should be added as well, or perhaps "VFDecryptKey" will be renamed to "FSKey." People submitting keys would still be bothered with having to adjust for those changes. --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 17:40, 21 November 2013 (UTC)
:::That with the database is something I'll implement anyway (if not someone else is faster, as I'm quite busy). I just threw that in here as it might solve the problem of the frequent template updates (which is/was wrong anyway). From there it would be easy to create the VFDecrypt page with an overview link or lists of missing keys and that stuff, so the wiki would not need any direct links. But it would mean that we either completely remove all keys here from the wiki and embrace that solution or have them still duplicate (which then doesn't solve the problem). Dialexio: renaming columns can be handled without interface changes, but that's another topic. So let's forget about this database thing for now and we can discuss again when I have something. We certainly don't want to add extensions for that. So back to the discussion about the renaming: If I understood this correctly, you only want to rename A5+ devices and therefore no key pages would be affected. Is my understanding correct? --[[User:Http|http]] ([[User talk:Http|talk]]) 22:08, 21 November 2013 (UTC)
::::As long as the pages stay on this wiki, I do not mind. Although, a database could be pointless as with only 50 more pages to edit for the new format, there is no planned new format/changes again. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 22:16, 21 November 2013 (UTC)
::::About the renaming, that is correct; I'm only interested in changing the cellular labels on A5/+ devices. (Well, the iPad 2 can remain as-is.) --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 00:02, 22 November 2013 (UTC)
:::::Oh, well that would just make things more complicated/inconsistent. We should do all or none. About the template idea, there is also no need as it is not likely we will change the format again. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 00:35, 22 November 2013 (UTC)

==Login prompt revision suggestion==
I wrote a suggestion here: [[MediaWiki talk:Loginprompt]] (since I don't have permission to edit [[MediaWiki:Loginprompt]] directly) - I'd be interested in whether it sounds like a good idea to other people. [[User:Britta|Britta]] ([[User talk:Britta|talk]]) 01:00, 8 October 2013 (UTC)

==Homepage suggestions==
Under "Application Development", what about linking to [http://iphonedevwiki.net/index.php/Main_Page iPhoneDevWiki]? It's also a community-edited technical resource, and it links to this wiki. It could be helpful to add a little more detail to "Get [[up to speed]] in the community.", like this: "Get [[up to speed]] in the community - learn about how jailbreaks work." Under "Definitions", it could be helpful to list all the firmware tags in one line or sub-list, similar to how Jailbreak is organized next to Tethered jailbreak and Untethered jailbreak, both to save space and help readers understand the list. --[[User:Britta|Britta]] ([[User talk:Britta|talk]]) 23:01, 20 October 2013 (UTC)
:A link to the iPhoneDevWiki sounds good. I wonder if we should have an "External Links" or "Other Resources" section to include links to other sites (such as the [http://blog.iphone-dev.org/ iPhone Dev Team blog]) though. As for the "Up to Speed" page, I feel like the entire page could be reworked a bit— and perhaps even receive a new, clearer name ([[Introduction]]? [[Preface]]? Or something else?)— the current name makes it sound like it's for people that last paid attention to jailbreaking when the App Store didn't exist. And yeah, moving the IMG3 tags to a sub-list sounds like a really good idea. (Admittedly, I actually don't care for its inclusion in the first place, but that's just a personal preference.) --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 00:10, 21 October 2013 (UTC)
::There's already [[Useful Links]] with some links to other core community resources (which could be updated and rearranged) - I was just thinking that it'd be especially useful to link to iPhoneDevWiki prominently since it's likely for TheiPhoneWiki visitors to also be interested in relatively-organized technical information about development. Changing the name of "Up to Speed" sounds fine to me too - that page didn't get much attention since 2008 until I sort of commandeered it to serve as an "intro to jailbreaking" page. :) It could be renamed "getting started", as in "how to get started on learning about research into iOS devices, especially security research (such as jailbreaks)". [[User:Britta|Britta]] ([[User talk:Britta|talk]]) 00:31, 21 October 2013 (UTC)
Also I'd love to see a dedicated section for "Good tasks for new editors", where we could maintain a list of relatively easy/straightforward suggested edits that wouldn't require vast technical knowledge, like updating that links page. Where would that go? Add it as a sub-section of [[The iPhone Wiki:Current events]] and link that section from the homepage or something? Or make a new page? [[User:Britta|Britta]] ([[User talk:Britta|talk]]) 00:40, 21 October 2013 (UTC)

==What is 0x5265c384 in the boot process?==
Does anybody know where <code>0x5265c384</code> points to in the boot process? I haven't been able to find anything on it. --[[User:Ph0enix|Ph0enix]] ([[User talk:Ph0enix|talk]]) 20:14, 23 October 2013 (UTC)

==License for contributions==
This wiki has never had an official license for contributions. Now, IANAL, but IIRC, this means that you can't use ''anything'' posted here unless it qualifies as fair-use. What I propose is that we set a license and add a notice that states that any contributions after a set date are to be licensed under that license (that's kindof a mouthful). I think we should use the [http://creativecommons.org/licenses/by-sa/3.0/ CC-by-SA 3.0] as [[wikipedia:Wikipedia:Text of Creative Commons Attribution-ShareAlike 3.0 Unported License|Wikipedia uses it]], but that's just me. Any ideas? --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 19:53, 9 November 2013 (UTC)
:Well, the edit info already says all this:
Please note that all contributions to The iPhone Wiki may be edited, altered, or
removed by other contributors. If you do not want your writing to be edited mercilessly,
then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public
domain or similar free resource (see The [[:The iPhone Wiki:Copyrights|iPhone Wiki:Copyrights]] for details). '''Do not'''
'''submit copyrighted work without permission!'''
For me, that's enough. I don't need a 50 page license. But if you want to formalize this more, go ahead. --[[User:Http|http]] ([[User talk:Http|talk]]) 20:35, 9 November 2013 (UTC)

:Sounds good. It's good practice to have an official license, just in case any disputes happen someday, and to ensure that it's OK to copy text over to Wikipedia (for example). [[User:Britta|Britta]] ([[User talk:Britta|talk]]) 21:32, 9 November 2013 (UTC)

==Future plans==
Now that I have SSH access, I've begun working on making several, somewhat-overdue changes to the wiki. The Renameuser extension was reinstated, so admins can now rename accounts. If you have another account, that can also get merged into your current account. If you happen to get locked out from both your account and the email used is no longer active, I can run a script to reset your password. I've also begun implementing a very noticeable change— as users of the Vector skin have noticed, the iOS 6-based theming is gone. It's a semi-temporary move though; it's going into its own skin, because… you know, choice is cool. People who like the Vector skin may not have liked the iOS theming, especially since IE 9 and lower didn't display it completely accurately. Therefore, it's going into its own theme. Once that's done I also plan on making a separate iOS 7-based skin. If there are any further thoughts or suggestions on how to improve the wiki, do let me know! --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 22:18, 9 November 2013 (UTC)

==TOC==
I was wondering if it may look better if we made the TOC show horizontal because currently, like on [[Firmware]], you have to scroll down quite a way to get to the actual devices. I know that you can click "hide" but that is not the point as it is still ugly imo. What do you all think? Also, someone on IRC has said that they have seen three people get the wrong IPSW with the numbering before the variants, thinking that it is the device model number. Any way that it could be changed to drop that numbering as I also agree it is oddly numbered? --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 19:09, 10 November 2013 (UTC)

The iPhone Wiki:Community portal

2013-11-23T18:39:59Z

CompilingEntropy: /* Key page template */

{{Talk Archive}}
{{see also|Unsolved problems}}
==iPhone-Elite==
I think we should include all this old stuff before it gets lost: [http://code.google.com/p/iphone-elite/ code.google.com/p/iphone-elite/]. I mean the wiki articles there. Most infos should be already here, but I'm sure a lot of things are missing too.
--[[User:Http|http]] 15:02, 26 June 2012 (MDT)

==Boot-args cleanup==
We need to clean up the boot-args pages. First the technical part: What I understand is that iBoot loads the kernel. And when loading it, it can pass some parameters to select certain behavior. So this only works with an iBoot or bootrom exploit. I understand that in earlier firmware versions there was simply an iBoot variable, but that doesn't exist or work anymore, now passing theses args requires a different or patched iBoot. There are various parameters in different kernel versions. The description for these arguments is scattered over various places:
*[[Kernel#Boot-Args]] A section with the latest boot arguments list. This should be a short introduction and having a link "main article".
*[[Boot-args (iBoot variable)]] separate page for boot arguments, but mainly for the iBoot variable that doesn't exist any longer
*[{{FULLURL:Boot arguments|redirect=no}} Boot arguments] (redirect)
*[[:Talk:Restore_Mode]] describing the iBoot variable problem
*Various pages referencing boot-args, like [[Research: Re-allowing unsigned ramdisks and boot-args with the 2.* iBoot]] (here we should have a link on the second title)
*My earlier comment [[:Talk:Kernel#boot-args]]
*This comment here.
So what do we want to do about this mess? I suggest to move the current [[Kernel]] content to the redirect page [[Boot arguments]] (or to another new page, maybe [[boot-args]]). The current content of [[Boot-args (iBoot variable)]] and all other content should get merged into there. Then change all references to this new page and on the [[Kernel]] page write just something short with "main article there". What do you think? --[[User:Http|http]] ([[User talk:Http|talk]]) 21:31, 13 February 2013 (UTC)
:I like [[Boot Arguments]]. --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 02:01, 14 February 2013 (UTC)
::One addition: Maybe we should use [[boot-args]] as the main page, because all links are written like that. --[[User:Http|http]] ([[User talk:Http|talk]]) 07:37, 14 February 2013 (UTC)

==The iPhone Wiki re-design==
The design of the iPhone wiki is now quite old and I think it should be updated. I made a [http://oi42.tinypic.com/30ib9y8.jpg concept]. --[[User:Jaggions|Jaggions]] ([[User talk:Jaggions|talk]]) 10:30, 14 June 2013 (UTC)
:I disagree. If anything add an iPhone 5 to the logo but everything else is ok. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 11:05, 14 June 2013 (UTC)
:I wouldn't change the logo to an iPhone 5, especially with iOS 7 and a new iPhone (that will probably look the same as the 5, admittedly) around the corner. I contemplated updating the CSS for iOS 7's UI but decided not to because of the UI's supposed volatility (during the beta period) and I don't have a live version to toy around with. (I personally don't like its current state, but that's not a factor in why I'm not changing it yet.) --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 16:25, 14 June 2013 (UTC)
::Can we not do flat? --[[User:Haifisch|Haifisch]] ([[User talk:Haifisch|talk]]) 21:02, 14 June 2013 (UTC)
::This is what I was thinking. When iOS 7 finally comes out, we could change the CSS to look like that instead. --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 21:11, 14 June 2013 (UTC)
:::iOS 7 looks ugly. We do not want it like that. Maybe a bit more modern but nothing much. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 21:16, 14 June 2013 (UTC)
::::''You'' may not want it like that. That's your opinion. --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 01:55, 15 June 2013 (UTC)
:::::We could make a poll, and see if most users agree or disagree. --[[User:Jaggions|Jaggions]] ([[User talk:Jaggions|talk]]) 10:05, 15 June 2013 (UTC)
:The idea looks nice. But before we make any changes, let's wait until iOS7 comes out. And I'd prefer to just add another skin instead (if possible). I'm still using the classic MonoBook skin by the way. You shouldn't impose design changes to everyone. --[[User:Http|http]] ([[User talk:Http|talk]]) 14:38, 15 June 2013 (UTC)
::The problem with skins is that geohot needs to set them up... An idea I have is that we copy the Vector skin verbatim to a new skin (<code>iOS6</code>) and move the modifications (not general stuff) to [[Mediawiki:iOS6.css]]. Then we can do another verbatim copy to <code>iOS7</code> and modify [[Mediawiki:iOS7.css]]. We could then set the default skin to either <code>iOS6</code> or <code>iOS7</code> so you don't need to be logged in to see them like currently. Then if someone doesn't like them, like you, just change your settings to your preferred skin. The only way around needing geohot is if he opens up the credentials to FTP or whatever to someone. --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 21:17, 15 June 2013 (UTC)
:::I like [[User:5urd|5urd]]'s suggestion. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 22:29, 15 June 2013 (UTC)
What about just removing the text-shadow element for now? I think pages would be easier to read without it. Here's an example: [[:File:Noshadow.png]]. [[User:Britta|Britta]] ([[User talk:Britta|talk]]) 00:11, 29 August 2013 (UTC)
:Yeah removing the shadow will make everything seem more flat but like [[User:http|http]] I'm still using the classic [http://theiphonewiki.com/w/index.php?title=Main_Page&useskin=monobook MonoBook skin] --[[User:Jaggions|Jaggions]] ([[User talk:Jaggions|talk]]) 21:19, 31 August 2013 (UTC)

==Hacker page==
I would like to be added to the list of hackers for my work with the Private Dev Team and the [[Chronic Dev (team)|Chronic Dev Team]] in addition to my release of the Phoenix Semi-Untethered. --[[User:Ph0enix|Ph0enix]] ([[User talk:Ph0enix|talk]]) 18:36, 22 July 2013 (UTC)
:Did you find any exploits? --[[User:Haifisch|Haifisch]] ([[User talk:Haifisch|talk]]) 18:54, 22 July 2013 (UTC)
::No. [[User:phyrrus9|phyrrus9]], a team member found the vulnerability. I am the one who exploited it. --[[User:Ph0enix|Ph0enix]] ([[User talk:Ph0enix|talk]])
:::I can back up this "claim". I was a part of it. --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 20:52, 28 July 2013 (UTC)
::::Whatever happened to this? --[[User:Phyrrus9|phyrrus9]]

==Orphaned articles==
This is an interesting search: [[Special:LonelyPages]] - "The following pages are not linked from or transcluded into other pages in The iPhone Wiki." I'm not sure where all of those articles should be linked, but figuring that out could be a useful project for somebody. [[User:Britta|Britta]] ([[User talk:Britta|talk]]) 05:57, 28 August 2013 (UTC)

==Easy tasks for new editors==
* Finish converting the remaining error codes listed here [[MobileDevice_Library#Known_Error_Codes]] into the proper mach_return_t codes they should be displayed as. (convert the negative number listed into hex, strip any leading "FF" so it should be in the format "0xe80000" followed by two numbers) --[[User:Dirkg|Dirkg]] ([[User talk:Dirkg|talk]]) 22:40, 28 August 2013 (UTC)

== A1XXX model numbers vs. "GSM"/"CDMA"/"Global"/"Cellular"/etc. ==
I know that this topic was [[The iPhone Wiki:Community portal/2013#iPhone 5|already discussed earlier this year]], but it didn't seem to come to a consensus, and the introduction of the [[iPhone 5c]] and [[iPhone 5s]] brought a lot of model numbers. Some of them may "overlap" (think models A1429 and A1442 for the [[iPhone 5]]), but there's simply too many to give names to. There are at least two that can connect to CDMA networks, and all of them can connect to GSM. In addition, with the sheer amount of models, it doesn't seem likely for one model to be treated as a "global" model. Therefore, I changed the iPhone 5c to use model numbers. I would like to do the same to some of the devices that are already present on the wiki though— the same ones from when I first brought up this idea. The GSM/CDMA names work very well for the [[iPad 2]] and [[iPhone 4]]. Things are slightly murkier for the [[iPad 3|iPad (3rd gen.)]], [[iPad 4|iPad (4th gen.)]], [[iPad mini 1G]], and [[iPhone 5]] though; all of those devices' cellular models can connect to GSM networks, so it seems like nonsense to call some of them the "GSM model." The A1XXX model numbers are also how Apple tells the difference between the different models of these devices. Have any opinions changed? Or perhaps someone new might have something to say about this? --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 06:06, 13 September 2013 (UTC)

:I actually like the idea as it does get complicated now with the new devices coming like said and we would have to do this for all devices. Although, if we did this, we would have to move all the key pages that have keys on to support this. That would not be a big problem as we could limit the moves to say 20 per day. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 09:47, 13 September 2013 (UTC)

:I suggest we wait a bit until we see what models of the [[iPhone 5c]] and [[iPhone 5s]] will exist. But in general, I like the idea of using only the A1nnn numbers. The only issue I see right now is that Apple differentiates between A1532 GSM and A1532 CDMA. If there are real hardware differences between these two, then we're screwed again. That's why I suggest to wait until we know these exact model types. On the disambiguation page I added the GSM/CDMA model differentiation already (as Apple does). If they turn out to be the same, we can remove it again, but I wonder why Apple lists two models (with different bands supported) there now. Someone also added the "CDMA" mark to one of the others, but that's not how Apple marks them, so I suggest to remove that mark there again. If everything can be differentiated by these A-model-numbers, then yes, we should change the old pages too. Including all key pages. --[[User:Http|http]] ([[User talk:Http|talk]]) 14:44, 13 September 2013 (UTC)

::I do know there are 2 CDMA and 3-4 GSM for the [[iPhone 5c]] alone. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 16:04, 13 September 2013 (UTC)

:::Ahem… ''All'' of the iPhone 5c models can do GSM communications. Hence one of the reasons why I want to ditch the "GSM"/"Global"/etc. labels in favor of A1XXX model numbers. ;P --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 16:07, 13 September 2013 (UTC)

::::One thing is, what about iPod touch 5 as that has two model numbers that are the same device, same with iPhone5,2. How would we get around that? I suppose we could like both separated with a forward slash. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 18:19, 13 September 2013 (UTC)

:::::Yeah, we could just use something like "[[n42ap|iPhone 5 (Model A1429/A1442)]]." --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 22:45, 13 September 2013 (UTC)

::::::Yeah I thought that but what about the iPhone 4 GSM and GSM Rev A? They both seem to be A1432. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 23:10, 13 September 2013 (UTC)

:::::::This is why I'm against using the A1XXX model numbers instead of the current GSM/Global thing. --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 23:25, 13 September 2013 (UTC)

::::::::I had no plans to change the way we refer to the iPhone 4 or iPad 2 (Apple does use GSM/CDMA, and for those devices it works fine). If a new iPhone 5S revision comes along, Apple will probably refer to it as a "Rev A" thing, and so will we. --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 02:50, 14 September 2013 (UTC)

:Referencing Adam's reply above, if we had took that to the key pages, it'd be <code>[<nowiki/>[{BuildTrain} {Build} (A1432)]]</code> which would mess ''everything'' up. What could we do? Use <code>[<nowiki/>[{BuildTrain} {Build} (A1432 Rev A)]]</code>? No. That doesn't look good. The current way of referring to everything by their supported network type (GSM/CDMA/Global) helps in going to a different page.
:Let's say I'm on [[BrightonMaps 10B329 (iPhone 4 GSM)]] and I want to go the CDMA device. What do I do? Go to the URL and replace <code>GSM</code> with <code>CDMA</code>. With the model numbers, I'd have to navigate to [[Firmware]], then find the link, or find out what the model number of the CDMA variant is and replace the model number in the URL with that. 
:Ok, who navigates by the URL and search bar? ''I do''. And I'm sure there's '''many''' people out there that prefer to navigate with the search bar if they know the page name. If we go by model number, the AJAX search results just list pages with a model number in parenthesis. '''How does that help'''? I'd either have to ''know'' the model number of the device I want, or visit ''each one'' until I find the page I need.
:Sorry for the rant, but I am '''strongly''' against this. --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 23:25, 13 September 2013 (UTC)

::I do suppose we could just trash the buildtrain all together to shorten it down too. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 23:32, 13 September 2013 (UTC)

:::Dropping the Build Train would only ''increase'' the workload. Besides, what's the harm with it? We've been using the same page title structure since forever, and it's worked. "''If it ain't broke, don't fix it''". The current system works, so ''why'', other than the fact that Apple refers to them differently, should we change this? In addition, we don't refer to everything the way Apple does. The [[iPad mini 1G]] is referred to as the "iPad mini". The [[iPad 3]] is refered to as "The New iPad". The [[iPad 4]] is refered to as "iPad with Retina Display"[http://www.apple.com/ipad/compare/]. Are the key pages titled <code>BrightonMaps 10B329 (The New iPad, Wi-Fi+3G for AT&T and Verizon)</code>? No. --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 00:37, 14 September 2013 (UTC)

::::But the reason we want to not use the variants is because the new devices that are coming out are breaking he structure and also CDMA versions can use GSM in the 5c plus we have like 4 for GSM alone. I only meant drop buildtrain to shorten the urls down. For the iPhone 4 GSM Rev A we would have to list it as <code>iPhone 4 A1432 Rev</code> unless another idea is thought of. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 00:55, 14 September 2013 (UTC)

:::::No. Anything involving moving key pages to change their title I am ''completely'' against. As for the iPhone 5s and iPhone 5c, we ultimately have to wait. There may be different types, but if they all work with the same firmware, then what do we do then? Use <code>A1456/A1504</code>? I don't want to do that. It can get confusing in the future if that list were to be huge. With ''5'' different models for the iPhone 5c ''alone'', it's just not practical. For the fact that all support GSM, but not all support CDMA, we just do what we've ''been'' doing: "GSM" and "Global". --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 01:22, 14 September 2013 (UTC)

::::::There's nothing wrong with changing the titles of pages that don't even exist though. If *all* of the models use the same firmware, just go with "iPhone 5s." If they happen to be partitioned into two different firmwares again, that will certainly complicate things, but it wouldn't be worse than nonsense like "GSM," "GSM [<nowiki />Global]," "CDMA," "CDMA [<nowiki />Global]," or "GSM [<nowiki />Global Plus TD-LTE]." If it's just one oddball, we could just have "iPhone 5s" and "iPhone 5s A1XXX" (whatever the odd one is), and include a link on the former page to say "keys for model A1XXX are on this page." --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 02:50, 14 September 2013 (UTC)

::::I probably didn't phrase that well… I wasn't thinking of how Apple markets the product, but rather more along the lines of how they refer to it in, say, the tech specs page or support documents— the pages that shows the messier side to their simple sugar coating. --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 02:50, 14 September 2013 (UTC)

::You keep misinterpreting/misrepresenting what I'm proposing. I never said anything about dropping, say, "iPhone 5" so firmware page titles would look like [[Sundance 10A405 (A1428)]]. I want to change the GSM/Global part to the A1XXX number, so it would probably show like [[Sundance 10A405 (iPhone 5 A1428)]]. (If a hardware revision were made, it would probably look like [[Sundance 10A405 (iPhone 5 A1428 Rev A)]].) From time to time, I edit URLs to browse the wiki too. But the GSM/Global identifiers don't work that well; again, '''all iPhone 5 models can connect to GSM'''. That's not really helpful. --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 02:50, 14 September 2013 (UTC)

:::I suggest we drop the A and use Rev. As for the idea of changing to A1XXX, I see no issues and am for the idea. I admit it can cause chaos when we move the pages but we could limit the moving per day of course. Overall, I think it will be worth it. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 10:01, 14 September 2013 (UTC)

::::No. Don't drop the <code>A</code> from <code>Rev A</code>. Why would you even think to? You want to call them what Apple calls them, and the [[n90bap|revised iPhone 4 GSM]] is referred to with <code>Rev A</code>. In addition, there have been <code>Rev ''B''</code> things before, such as the [[S5L8947]] (A5 Rev B) used in the [[j33iap|revised Apple TV 3G]]. In addition, think of all the redirects we would need to keep for sites that link to key pages directly. I have even seen sites that still link with the URLs as <code>/wiki/index.php?title={Title}</code> instead of the year old change to <code>/wiki/{Title}</code>. The wiki handles that internally for us, but the redirects made in the moves would have to be kept. Currently, only the [[iPhone 5]] and [[iPad 4]] are the only devices referred to by their model numbers. --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 20:53, 14 September 2013 (UTC)

:::That's why I don't want to change it. It's worked for us, and we have no idea how the new firmwares will be handled. I am betting that there will only be two firmware types - one for the GSM, and one for the Global (GSM+CDMA) model. The only reason they are split, IIRC, is because AT&T uses different LTE bands than rest of the GSM world.
:::Ultimately, the GSM/CDMA/Global monikors haven't caused any ''naming conflicts''. Ok, you don't want to use the ''marketing'' title. What about the way they are referred to on [[Apple Developer Center|ADC]], because that seems to be what you want. I may be misreading what you're saying again, but if we're going to do that, let's use their ''full'' title. Something <code>(iPad [4th generation Model A1458])</code> (iPad 4 Wi-Fi) and <code>(iPad Wi-Fi + Cellular [model for Verizon])</code> (iPad 3 Global). Does the first one tell you if the device is Wi-Fi or a Wi-Fi+3G model? Does the second one tell you ''at all'' that it is an [[iPad 3]], or that it supports GSM? No.
:::Apple has a history of being inconsistent. For example, the iPad 3 Wi-Fi is referred to on ADC (and iTunes) as "iPad Wi-Fi (3rd generation)" while the iPad 3 GSM is referred to as "iPad Wi-Fi + Cellular [model for AT&T]". What happened to the "3rd generation"? --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 20:53, 14 September 2013 (UTC)

::::We could always list as <code>iPhone 4 (iPhone3,1)</code> etc instead if that would be better. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 21:13, 14 September 2013 (UTC)

::::Why is there a need to explicitly keep "Wi-Fi" in a key page's title? All you need is a way to distinguish what model it is from its other variants— the A1XXX model number does just that. It's not like we referred to the AppleTV3,2 as "Apple TV 3G (New Single-Core A5)" or something. And obviously, we can use common sense to address the 3rd generation iPad issue you brought up… Now you're just nitpicking. --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 05:28, 15 September 2013 (UTC)
:::::Actually, I think we should wait until we see the firmware for iPhone 5c/5s and then decide. TBH, as [[User:5urd|5urd]] said, it is ok as it is but of course if once the new firmware is out it is more confusing, then we can think again. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 14:12, 15 September 2013 (UTC)

:::::Come to think of it, we can use a mix of both; we can keep the "Global" moniker, but drop the "GSM" moniker in favor of the A1XXX model number. (The "GSM" moniker is the one that's been bothering me.) I think this works well for the iPad 3 (which is actually split into "CDMA" and "Global—" it probably doesn't need to be done for this), iPad 4, iPad mini 1G, and iPhone 5, but this leaves the question of what to do for the iPhone 5C/5S. --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 04:04, 19 September 2013 (UTC)

::::::That would look worse! If we are going to do it, we have to do it for '''''all'''''. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 09:40, 19 September 2013 (UTC)

:::::::What is the status on this now? --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 21:18, 9 November 2013 (UTC)

:::::This discussion has stagnated, but I'm firing it up again— I want to fix this before the end of the year, so this can probably be seen as an ultimatum. Now that Apple has pushed a 7.1 beta to developers, we now know how Apple's splitting the new iPhones up— and it's by A1XXX model numbers still. :\ That's probably the path the wiki will go down, but I do have another idea. The other idea I have in mind is using the A1XXX model number for the cellular devices launched last year. But for this year's iPhones, the FCC ID is actually different between the two, so we could actually use that. Before this gets nitpicked on, the last letter can get changed to an "X" to signify that it's a wildcard of sorts. It's not a pretty solution so I do expect it to get shot down (hence why I'm going with the A1XXX model numbers unless everyone says otherwise), but I'm still throwing it out there in case everyone actually likes that. Everyone is welcome to suggest alternatives, but I '''will''' eliminate that GSM label before the year ends. --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 18:31, 18 November 2013 (UTC)

::::::That is worse, nobody knows the FCC ID off the top of their head. I would suggest "iPhone 5 (iPhone5,1)" if anything. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 18:37, 18 November 2013 (UTC)

:::::::Using "iPhone5,1" or "iPhone6,2" is even ''less'' friendly… The FCC ID can be looked up in Settings or the back of a device. --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 19:06, 18 November 2013 (UTC)

::::::::Well that is not the point. I say either use the firmware name or leave it alone. See what others thing though. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 19:13, 18 November 2013 (UTC)

:::::::::I currently plan on using the A1XXX model numbers— the FCC ID proposal was just thrown out there in the off chance that someone might like it. I'm not really a fan of it myself, but the FCC ID is probably the simplest way to figure out if it's an iPhone6,1 or iPhone6,2 since both have multiple A1XXX model numbers. --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 19:19, 18 November 2013 (UTC)

::::::I agree to get rid of the "GSM" name, as almost all iPhones support GSM. The Axxxx numbers would be nice, but as some phones have several numbers, like A1457/A1518/A1528/A1530 (what is actually different between them?) we can't use it. For the FCC-ID, we can't use that either, because for example the iPhone 5 with FCC-ID BCG-E2599A stands for the GSM/A1428 and also for the GSM+CDMA/A1429 version. So I suggest to either use the identifier (like iPhone2,1) or better the internal name (like n88ap). That would have the advantage to separate them further, because the iPhone 4 A1332 has two internal versions: iPhone3,1/n90ap and the iPhone3,2/n90bap. The bigger question is where you want to use this. That determines mainly the name. On all the key pages? Then it must be a name that is different between models that use different firmwares. And regarding key pages, maybe we should delete all the key pages from this wiki and move them into some database instead and provide a nice user interface and API around it and integrate that into the wiki somehow. That way we can change all pages with one simple edit. For the name, I prefer the internal name. --[[User:Http|http]] ([[User talk:Http|talk]]) 23:43, 18 November 2013 (UTC)

:::::::We would have to edit key pages too. They should not be removed however. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 23:46, 18 November 2013 (UTC)

:::::::Well, I wasn't trying to say that we had to decide on one way to differentiate ''everything''; "GSM" does work fine for, say, the iPhone 4. The proposal I brought up today was using the FCC ID only for this year's (2013's) iPhones— last year's cellular devices would get the A1XXX model numbers (i.e. two different solutions for two different years). But as of right now, I like how using A1XXX model numbers sounds for all of the affected devices, mostly because that's the path Apple's going in their developer portal. Something like "iPhone 5s (Model A1457/A1518/A1528/A1530)" is admittedly a mouthful for this year's iPhones though. At the moment, I'm inquiring about how to label it on [[Firmware]] and such pages, but I'm sure the outcome can be adapted for key page titles as well. As for differences between the models, it seems to be the supported LTE bands. --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 03:49, 19 November 2013 (UTC)

:::::::::I still think that unless it is "iPhone 5 (iPhone5,1)" it will be complicated but on the other hand, I kind of like the idea that [[User:Http|http]] had, using the internal identifiers like this "iPhone 5 (n42ap)". The only problem is that it would cause quite a bit of a flood moving the key pages, although this can be done like 15 per day each or something. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 09:20, 19 November 2013 (UTC)

::::::::::I'm pretty sure the only key page that exists for an A5 (or newer) device is [[Telluride 9A406 (iPhone 4S)]]. --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 17:40, 21 November 2013 (UTC)

:::::::::::That was an example. I know there are no more A5 pages, only the one you said and two beta for iPhone 4S. I just meant that it would show the design. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 13:36, November 21, 2013 (UTC)

== "GSM" Replacement Proposals ==
Since this discussion has become extremely lengthy, here are the proposals (to my understanding) for changing the labels, each of which can be subject to changes (i.e. dropping the word "Model" from Proposal A). In an effort to conserve space (ironically, this still adds a significant amount of length), I only included a few models, which should give an idea of the proposal. Basically anything with an A5 or newer is involved. Feel free to edit this list if I missed or totally misinterpreted something. --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 03:25, 22 November 2013 (UTC)
# Proposal A (A1XXX numbers)
#* iPad 4 (Model A1458)
#* iPad 4 (Model A1459)
#* iPad 4 (Model A1460)
#* iPhone 5 (Model A1428)
#* iPhone 5 (Model A1429/A1442)
#* iPhone 5c (Model A1456/A1532)
#* iPhone 5c (Model A1507/A1516/A1526/A1529)
#* [[InnsbruckTaos 11B554a (iPad 4 A1458)]]
#* [[InnsbruckTaos 11B554a (iPhone 5 A1429/A1442)]]
#* [[InnsbruckTaos 11B554a (iPhone 5c Model A1507/A1516/A1526/A1529)]]
# Proposal B (A1XXX + FCC ID)
#* iPad 4 (Model A1458)
#* iPad 4 (Model A1459)
#* iPad 4 (Model A1460)
#* iPhone 5 (Model A1428)
#* iPhone 5 (Model A1429/A1442)
#* iPhone 5c (BCG‑E2644A)
#* iPhone 5c (BCG‑E2694X)
#* [[InnsbruckTaos 11B554a (iPad 4 A1458)]]
#* [[InnsbruckTaos 11B554a (iPhone 5 A1429/A1442)]]
#* [[InnsbruckTaos 11B554a (iPhone 5c BCG‑E2694X)]]
# Proposal C (-AP Identifier)
#* iPad 4 (p101ap)
#* iPad 4 (p102ap)
#* iPad 4 (p103ap)
#* iPhone 5 (n41ap)
#* iPhone 5 (n42ap)
#* iPhone 5c (n48ap)
#* iPhone 5c (n49ap)
#* [[InnsbruckTaos 11B554a (iPad 4 p101ap)]]
#* [[InnsbruckTaos 11B554a (iPhone 5c n42ap)]]
#* [[InnsbruckTaos 11B554a (iPhone 5c n49ap)]]
# Proposal D (iPhoneX,Y Identifier)
#* iPad 4 (iPad3,4)
#* iPad 4 (iPad3,5)
#* iPad 4 (iPad3,6)
#* iPhone 5 (iPhone5,1)
#* iPhone 5 (iPhone5,2)
#* iPhone 5c (iPhone5,3)
#* iPhone 5c (iPhone5,4)
#* [[InnsbruckTaos 11B554a (iPad3,4)]]
#* [[InnsbruckTaos 11B554a (iPhone5,2)]]
#* [[InnsbruckTaos 11B554a (iPhone5,4)]]

:I like this [[InnsbruckTaos 11B554a iPad 4 (3,4)]] or [[InnsbruckTaos 11B554a iPad 4 (iPad3,4)]]. I see there are 4 ways to approach this;
1. Change every single device. 
2. Change just devices with different variants, iPad 2+, iPad mini+, iPhone 4, iPhone 5+. 
3. Change A5+ only (which I hate the idea of). 
4. Change nothing at all. 
--[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 09:28, 22 November 2013 (UTC)
::My intention for this was to be a ''neutral'' (i.e. opinion-free) spot where all of the proposals were being mentioned, so people could easily see the proposed changes without any bias… v.v --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 20:54, 22 November 2013 (UTC)
:::TBH, I think it is better as it is, but I just stated my opinion that only A5+ would make in inconsistent. Though you could argue it is already, that is down to Apple and furthermore, just A5+ would still not eliminate iPhone 4 (GSM, GSM Rev A or CDMA). --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 17:07, November 22, 2013‎ (UTC)}}

== Key page template ==
I actually like the idea of a database to an extent. I bet I could put together an extension that creates a [[Special:SpecialPages|special page]] that allows read access to everyone (and r/w access to users). Any edits to the key "pages" wouldn't cause a [[Special:RecentChanges|recent changes]] log. If we ever needed to update the layout, we would just need to update the extension. We could even have an API.
The only limitation is that updates to the extension would require either [[User:geohot|George]] or [[User:Dialexio|Alex]] needing to upload the fix. If we were to set up an external site, then all links to it would need to be wrapped with <code>...</code>.
Maybe a simple extension that takes links and redirects you to the external site? That could work. Like, we would have a link to, say, <code>[[<nowiki/>Special:Keys/iPad1,1/9A405]]</code> which would give an HTTP <code>301 Moved Permanently</code> header to, say, <code><nowiki>http://ioskeys.com/iPad1,1/9A405</nowiki></code>. Granted, someone would have to pay for the domain, but it would solve this problem. I may be able to pay for the domain if I make enough money by the time I finish writing everything. Any opposition? --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 16:48, 21 November 2013 (UTC)
:I do not like the idea. I like the idea of the database to a degree, but I think that the pages should remain on this wiki. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 17:03, 21 November 2013 (UTC)
::I don't see this solving any problem— the backlash against changing the key page template was because of (unnecessary?) changes to the arguments, and the frequency of how often such changes were being proposed/applied. How would a database prevent it? For instance, let's say the database columns are all decided on. Suddenly, it's decided that SHA-1 hashes should be added as well, or perhaps "VFDecryptKey" will be renamed to "FSKey." People submitting keys would still be bothered with having to adjust for those changes. --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 17:40, 21 November 2013 (UTC)
:::That with the database is something I'll implement anyway (if not someone else is faster, as I'm quite busy). I just threw that in here as it might solve the problem of the frequent template updates (which is/was wrong anyway). From there it would be easy to create the VFDecrypt page with an overview link or lists of missing keys and that stuff, so the wiki would not need any direct links. But it would mean that we either completely remove all keys here from the wiki and embrace that solution or have them still duplicate (which then doesn't solve the problem). Dialexio: renaming columns can be handled without interface changes, but that's another topic. So let's forget about this database thing for now and we can discuss again when I have something. We certainly don't want to add extensions for that. So back to the discussion about the renaming: If I understood this correctly, you only want to rename A5+ devices and therefore no key pages would be affected. Is my understanding correct? --[[User:Http|http]] ([[User talk:Http|talk]]) 22:08, 21 November 2013 (UTC)
::::As long as the pages stay on this wiki, I do not mind. Although, a database could be pointless as with only 50 more pages to edit for the new format, there is no planned new format/changes again. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 22:16, 21 November 2013 (UTC)
::::About the renaming, that is correct; I'm only interested in changing the cellular labels on A5/+ devices. (Well, the iPad 2 can remain as-is.) --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 00:02, 22 November 2013 (UTC)
:::::Oh, well that would just make things more complicated/inconsistent. We should do all or none. About the template idea, there is also no need as it is not likely we will change the format again. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 00:35, 22 November 2013 (UTC)

==Login prompt revision suggestion==
I wrote a suggestion here: [[MediaWiki talk:Loginprompt]] (since I don't have permission to edit [[MediaWiki:Loginprompt]] directly) - I'd be interested in whether it sounds like a good idea to other people. [[User:Britta|Britta]] ([[User talk:Britta|talk]]) 01:00, 8 October 2013 (UTC)

==Homepage suggestions==
Under "Application Development", what about linking to [http://iphonedevwiki.net/index.php/Main_Page iPhoneDevWiki]? It's also a community-edited technical resource, and it links to this wiki. It could be helpful to add a little more detail to "Get [[up to speed]] in the community.", like this: "Get [[up to speed]] in the community - learn about how jailbreaks work." Under "Definitions", it could be helpful to list all the firmware tags in one line or sub-list, similar to how Jailbreak is organized next to Tethered jailbreak and Untethered jailbreak, both to save space and help readers understand the list. --[[User:Britta|Britta]] ([[User talk:Britta|talk]]) 23:01, 20 October 2013 (UTC)
:A link to the iPhoneDevWiki sounds good. I wonder if we should have an "External Links" or "Other Resources" section to include links to other sites (such as the [http://blog.iphone-dev.org/ iPhone Dev Team blog]) though. As for the "Up to Speed" page, I feel like the entire page could be reworked a bit— and perhaps even receive a new, clearer name ([[Introduction]]? [[Preface]]? Or something else?)— the current name makes it sound like it's for people that last paid attention to jailbreaking when the App Store didn't exist. And yeah, moving the IMG3 tags to a sub-list sounds like a really good idea. (Admittedly, I actually don't care for its inclusion in the first place, but that's just a personal preference.) --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 00:10, 21 October 2013 (UTC)
::There's already [[Useful Links]] with some links to other core community resources (which could be updated and rearranged) - I was just thinking that it'd be especially useful to link to iPhoneDevWiki prominently since it's likely for TheiPhoneWiki visitors to also be interested in relatively-organized technical information about development. Changing the name of "Up to Speed" sounds fine to me too - that page didn't get much attention since 2008 until I sort of commandeered it to serve as an "intro to jailbreaking" page. :) It could be renamed "getting started", as in "how to get started on learning about research into iOS devices, especially security research (such as jailbreaks)". [[User:Britta|Britta]] ([[User talk:Britta|talk]]) 00:31, 21 October 2013 (UTC)
Also I'd love to see a dedicated section for "Good tasks for new editors", where we could maintain a list of relatively easy/straightforward suggested edits that wouldn't require vast technical knowledge, like updating that links page. Where would that go? Add it as a sub-section of [[The iPhone Wiki:Current events]] and link that section from the homepage or something? Or make a new page? [[User:Britta|Britta]] ([[User talk:Britta|talk]]) 00:40, 21 October 2013 (UTC)

==What is 0x5265c384 in the boot process?==
Does anybody know where <code>0x5265c384</code> points to in the boot process? I haven't been able to find anything on it. --[[User:Ph0enix|Ph0enix]] ([[User talk:Ph0enix|talk]]) 20:14, 23 October 2013 (UTC)

==License for contributions==
This wiki has never had an official license for contributions. Now, IANAL, but IIRC, this means that you can't use ''anything'' posted here unless it qualifies as fair-use. What I propose is that we set a license and add a notice that states that any contributions after a set date are to be licensed under that license (that's kindof a mouthful). I think we should use the [http://creativecommons.org/licenses/by-sa/3.0/ CC-by-SA 3.0] as [[wikipedia:Wikipedia:Text of Creative Commons Attribution-ShareAlike 3.0 Unported License|Wikipedia uses it]], but that's just me. Any ideas? --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 19:53, 9 November 2013 (UTC)
:Well, the edit info already says all this:
Please note that all contributions to The iPhone Wiki may be edited, altered, or
removed by other contributors. If you do not want your writing to be edited mercilessly,
then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public
domain or similar free resource (see The [[:The iPhone Wiki:Copyrights|iPhone Wiki:Copyrights]] for details). '''Do not'''
'''submit copyrighted work without permission!'''
For me, that's enough. I don't need a 50 page license. But if you want to formalize this more, go ahead. --[[User:Http|http]] ([[User talk:Http|talk]]) 20:35, 9 November 2013 (UTC)

:Sounds good. It's good practice to have an official license, just in case any disputes happen someday, and to ensure that it's OK to copy text over to Wikipedia (for example). [[User:Britta|Britta]] ([[User talk:Britta|talk]]) 21:32, 9 November 2013 (UTC)

==Future plans==
Now that I have SSH access, I've begun working on making several, somewhat-overdue changes to the wiki. The Renameuser extension was reinstated, so admins can now rename accounts. If you have another account, that can also get merged into your current account. If you happen to get locked out from both your account and the email used is no longer active, I can run a script to reset your password. I've also begun implementing a very noticeable change— as users of the Vector skin have noticed, the iOS 6-based theming is gone. It's a semi-temporary move though; it's going into its own skin, because… you know, choice is cool. People who like the Vector skin may not have liked the iOS theming, especially since IE 9 and lower didn't display it completely accurately. Therefore, it's going into its own theme. Once that's done I also plan on making a separate iOS 7-based skin. If there are any further thoughts or suggestions on how to improve the wiki, do let me know! --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 22:18, 9 November 2013 (UTC)

==TOC==
I was wondering if it may look better if we made the TOC show horizontal because currently, like on [[Firmware]], you have to scroll down quite a way to get to the actual devices. I know that you can click "hide" but that is not the point as it is still ugly imo. What do you all think? Also, someone on IRC has said that they have seen three people get the wrong IPSW with the numbering before the variants, thinking that it is the device model number. Any way that it could be changed to drop that numbering as I also agree it is oddly numbered? --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 19:09, 10 November 2013 (UTC)

The iPhone Wiki:Community portal

2013-11-23T18:39:15Z

CompilingEntropy: /* Key page template */

{{Talk Archive}}
{{see also|Unsolved problems}}
==iPhone-Elite==
I think we should include all this old stuff before it gets lost: [http://code.google.com/p/iphone-elite/ code.google.com/p/iphone-elite/]. I mean the wiki articles there. Most infos should be already here, but I'm sure a lot of things are missing too.
--[[User:Http|http]] 15:02, 26 June 2012 (MDT)

==Boot-args cleanup==
We need to clean up the boot-args pages. First the technical part: What I understand is that iBoot loads the kernel. And when loading it, it can pass some parameters to select certain behavior. So this only works with an iBoot or bootrom exploit. I understand that in earlier firmware versions there was simply an iBoot variable, but that doesn't exist or work anymore, now passing theses args requires a different or patched iBoot. There are various parameters in different kernel versions. The description for these arguments is scattered over various places:
*[[Kernel#Boot-Args]] A section with the latest boot arguments list. This should be a short introduction and having a link "main article".
*[[Boot-args (iBoot variable)]] separate page for boot arguments, but mainly for the iBoot variable that doesn't exist any longer
*[{{FULLURL:Boot arguments|redirect=no}} Boot arguments] (redirect)
*[[:Talk:Restore_Mode]] describing the iBoot variable problem
*Various pages referencing boot-args, like [[Research: Re-allowing unsigned ramdisks and boot-args with the 2.* iBoot]] (here we should have a link on the second title)
*My earlier comment [[:Talk:Kernel#boot-args]]
*This comment here.
So what do we want to do about this mess? I suggest to move the current [[Kernel]] content to the redirect page [[Boot arguments]] (or to another new page, maybe [[boot-args]]). The current content of [[Boot-args (iBoot variable)]] and all other content should get merged into there. Then change all references to this new page and on the [[Kernel]] page write just something short with "main article there". What do you think? --[[User:Http|http]] ([[User talk:Http|talk]]) 21:31, 13 February 2013 (UTC)
:I like [[Boot Arguments]]. --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 02:01, 14 February 2013 (UTC)
::One addition: Maybe we should use [[boot-args]] as the main page, because all links are written like that. --[[User:Http|http]] ([[User talk:Http|talk]]) 07:37, 14 February 2013 (UTC)

==The iPhone Wiki re-design==
The design of the iPhone wiki is now quite old and I think it should be updated. I made a [http://oi42.tinypic.com/30ib9y8.jpg concept]. --[[User:Jaggions|Jaggions]] ([[User talk:Jaggions|talk]]) 10:30, 14 June 2013 (UTC)
:I disagree. If anything add an iPhone 5 to the logo but everything else is ok. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 11:05, 14 June 2013 (UTC)
:I wouldn't change the logo to an iPhone 5, especially with iOS 7 and a new iPhone (that will probably look the same as the 5, admittedly) around the corner. I contemplated updating the CSS for iOS 7's UI but decided not to because of the UI's supposed volatility (during the beta period) and I don't have a live version to toy around with. (I personally don't like its current state, but that's not a factor in why I'm not changing it yet.) --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 16:25, 14 June 2013 (UTC)
::Can we not do flat? --[[User:Haifisch|Haifisch]] ([[User talk:Haifisch|talk]]) 21:02, 14 June 2013 (UTC)
::This is what I was thinking. When iOS 7 finally comes out, we could change the CSS to look like that instead. --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 21:11, 14 June 2013 (UTC)
:::iOS 7 looks ugly. We do not want it like that. Maybe a bit more modern but nothing much. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 21:16, 14 June 2013 (UTC)
::::''You'' may not want it like that. That's your opinion. --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 01:55, 15 June 2013 (UTC)
:::::We could make a poll, and see if most users agree or disagree. --[[User:Jaggions|Jaggions]] ([[User talk:Jaggions|talk]]) 10:05, 15 June 2013 (UTC)
:The idea looks nice. But before we make any changes, let's wait until iOS7 comes out. And I'd prefer to just add another skin instead (if possible). I'm still using the classic MonoBook skin by the way. You shouldn't impose design changes to everyone. --[[User:Http|http]] ([[User talk:Http|talk]]) 14:38, 15 June 2013 (UTC)
::The problem with skins is that geohot needs to set them up... An idea I have is that we copy the Vector skin verbatim to a new skin (<code>iOS6</code>) and move the modifications (not general stuff) to [[Mediawiki:iOS6.css]]. Then we can do another verbatim copy to <code>iOS7</code> and modify [[Mediawiki:iOS7.css]]. We could then set the default skin to either <code>iOS6</code> or <code>iOS7</code> so you don't need to be logged in to see them like currently. Then if someone doesn't like them, like you, just change your settings to your preferred skin. The only way around needing geohot is if he opens up the credentials to FTP or whatever to someone. --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 21:17, 15 June 2013 (UTC)
:::I like [[User:5urd|5urd]]'s suggestion. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 22:29, 15 June 2013 (UTC)
What about just removing the text-shadow element for now? I think pages would be easier to read without it. Here's an example: [[:File:Noshadow.png]]. [[User:Britta|Britta]] ([[User talk:Britta|talk]]) 00:11, 29 August 2013 (UTC)
:Yeah removing the shadow will make everything seem more flat but like [[User:http|http]] I'm still using the classic [http://theiphonewiki.com/w/index.php?title=Main_Page&useskin=monobook MonoBook skin] --[[User:Jaggions|Jaggions]] ([[User talk:Jaggions|talk]]) 21:19, 31 August 2013 (UTC)

==Hacker page==
I would like to be added to the list of hackers for my work with the Private Dev Team and the [[Chronic Dev (team)|Chronic Dev Team]] in addition to my release of the Phoenix Semi-Untethered. --[[User:Ph0enix|Ph0enix]] ([[User talk:Ph0enix|talk]]) 18:36, 22 July 2013 (UTC)
:Did you find any exploits? --[[User:Haifisch|Haifisch]] ([[User talk:Haifisch|talk]]) 18:54, 22 July 2013 (UTC)
::No. [[User:phyrrus9|phyrrus9]], a team member found the vulnerability. I am the one who exploited it. --[[User:Ph0enix|Ph0enix]] ([[User talk:Ph0enix|talk]])
:::I can back up this "claim". I was a part of it. --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 20:52, 28 July 2013 (UTC)
::::Whatever happened to this? --[[User:Phyrrus9|phyrrus9]]

==Orphaned articles==
This is an interesting search: [[Special:LonelyPages]] - "The following pages are not linked from or transcluded into other pages in The iPhone Wiki." I'm not sure where all of those articles should be linked, but figuring that out could be a useful project for somebody. [[User:Britta|Britta]] ([[User talk:Britta|talk]]) 05:57, 28 August 2013 (UTC)

==Easy tasks for new editors==
* Finish converting the remaining error codes listed here [[MobileDevice_Library#Known_Error_Codes]] into the proper mach_return_t codes they should be displayed as. (convert the negative number listed into hex, strip any leading "FF" so it should be in the format "0xe80000" followed by two numbers) --[[User:Dirkg|Dirkg]] ([[User talk:Dirkg|talk]]) 22:40, 28 August 2013 (UTC)

== A1XXX model numbers vs. "GSM"/"CDMA"/"Global"/"Cellular"/etc. ==
I know that this topic was [[The iPhone Wiki:Community portal/2013#iPhone 5|already discussed earlier this year]], but it didn't seem to come to a consensus, and the introduction of the [[iPhone 5c]] and [[iPhone 5s]] brought a lot of model numbers. Some of them may "overlap" (think models A1429 and A1442 for the [[iPhone 5]]), but there's simply too many to give names to. There are at least two that can connect to CDMA networks, and all of them can connect to GSM. In addition, with the sheer amount of models, it doesn't seem likely for one model to be treated as a "global" model. Therefore, I changed the iPhone 5c to use model numbers. I would like to do the same to some of the devices that are already present on the wiki though— the same ones from when I first brought up this idea. The GSM/CDMA names work very well for the [[iPad 2]] and [[iPhone 4]]. Things are slightly murkier for the [[iPad 3|iPad (3rd gen.)]], [[iPad 4|iPad (4th gen.)]], [[iPad mini 1G]], and [[iPhone 5]] though; all of those devices' cellular models can connect to GSM networks, so it seems like nonsense to call some of them the "GSM model." The A1XXX model numbers are also how Apple tells the difference between the different models of these devices. Have any opinions changed? Or perhaps someone new might have something to say about this? --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 06:06, 13 September 2013 (UTC)

:I actually like the idea as it does get complicated now with the new devices coming like said and we would have to do this for all devices. Although, if we did this, we would have to move all the key pages that have keys on to support this. That would not be a big problem as we could limit the moves to say 20 per day. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 09:47, 13 September 2013 (UTC)

:I suggest we wait a bit until we see what models of the [[iPhone 5c]] and [[iPhone 5s]] will exist. But in general, I like the idea of using only the A1nnn numbers. The only issue I see right now is that Apple differentiates between A1532 GSM and A1532 CDMA. If there are real hardware differences between these two, then we're screwed again. That's why I suggest to wait until we know these exact model types. On the disambiguation page I added the GSM/CDMA model differentiation already (as Apple does). If they turn out to be the same, we can remove it again, but I wonder why Apple lists two models (with different bands supported) there now. Someone also added the "CDMA" mark to one of the others, but that's not how Apple marks them, so I suggest to remove that mark there again. If everything can be differentiated by these A-model-numbers, then yes, we should change the old pages too. Including all key pages. --[[User:Http|http]] ([[User talk:Http|talk]]) 14:44, 13 September 2013 (UTC)

::I do know there are 2 CDMA and 3-4 GSM for the [[iPhone 5c]] alone. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 16:04, 13 September 2013 (UTC)

:::Ahem… ''All'' of the iPhone 5c models can do GSM communications. Hence one of the reasons why I want to ditch the "GSM"/"Global"/etc. labels in favor of A1XXX model numbers. ;P --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 16:07, 13 September 2013 (UTC)

::::One thing is, what about iPod touch 5 as that has two model numbers that are the same device, same with iPhone5,2. How would we get around that? I suppose we could like both separated with a forward slash. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 18:19, 13 September 2013 (UTC)

:::::Yeah, we could just use something like "[[n42ap|iPhone 5 (Model A1429/A1442)]]." --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 22:45, 13 September 2013 (UTC)

::::::Yeah I thought that but what about the iPhone 4 GSM and GSM Rev A? They both seem to be A1432. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 23:10, 13 September 2013 (UTC)

:::::::This is why I'm against using the A1XXX model numbers instead of the current GSM/Global thing. --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 23:25, 13 September 2013 (UTC)

::::::::I had no plans to change the way we refer to the iPhone 4 or iPad 2 (Apple does use GSM/CDMA, and for those devices it works fine). If a new iPhone 5S revision comes along, Apple will probably refer to it as a "Rev A" thing, and so will we. --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 02:50, 14 September 2013 (UTC)

:Referencing Adam's reply above, if we had took that to the key pages, it'd be <code>[<nowiki/>[{BuildTrain} {Build} (A1432)]]</code> which would mess ''everything'' up. What could we do? Use <code>[<nowiki/>[{BuildTrain} {Build} (A1432 Rev A)]]</code>? No. That doesn't look good. The current way of referring to everything by their supported network type (GSM/CDMA/Global) helps in going to a different page.
:Let's say I'm on [[BrightonMaps 10B329 (iPhone 4 GSM)]] and I want to go the CDMA device. What do I do? Go to the URL and replace <code>GSM</code> with <code>CDMA</code>. With the model numbers, I'd have to navigate to [[Firmware]], then find the link, or find out what the model number of the CDMA variant is and replace the model number in the URL with that. 
:Ok, who navigates by the URL and search bar? ''I do''. And I'm sure there's '''many''' people out there that prefer to navigate with the search bar if they know the page name. If we go by model number, the AJAX search results just list pages with a model number in parenthesis. '''How does that help'''? I'd either have to ''know'' the model number of the device I want, or visit ''each one'' until I find the page I need.
:Sorry for the rant, but I am '''strongly''' against this. --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 23:25, 13 September 2013 (UTC)

::I do suppose we could just trash the buildtrain all together to shorten it down too. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 23:32, 13 September 2013 (UTC)

:::Dropping the Build Train would only ''increase'' the workload. Besides, what's the harm with it? We've been using the same page title structure since forever, and it's worked. "''If it ain't broke, don't fix it''". The current system works, so ''why'', other than the fact that Apple refers to them differently, should we change this? In addition, we don't refer to everything the way Apple does. The [[iPad mini 1G]] is referred to as the "iPad mini". The [[iPad 3]] is refered to as "The New iPad". The [[iPad 4]] is refered to as "iPad with Retina Display"[http://www.apple.com/ipad/compare/]. Are the key pages titled <code>BrightonMaps 10B329 (The New iPad, Wi-Fi+3G for AT&T and Verizon)</code>? No. --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 00:37, 14 September 2013 (UTC)

::::But the reason we want to not use the variants is because the new devices that are coming out are breaking he structure and also CDMA versions can use GSM in the 5c plus we have like 4 for GSM alone. I only meant drop buildtrain to shorten the urls down. For the iPhone 4 GSM Rev A we would have to list it as <code>iPhone 4 A1432 Rev</code> unless another idea is thought of. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 00:55, 14 September 2013 (UTC)

:::::No. Anything involving moving key pages to change their title I am ''completely'' against. As for the iPhone 5s and iPhone 5c, we ultimately have to wait. There may be different types, but if they all work with the same firmware, then what do we do then? Use <code>A1456/A1504</code>? I don't want to do that. It can get confusing in the future if that list were to be huge. With ''5'' different models for the iPhone 5c ''alone'', it's just not practical. For the fact that all support GSM, but not all support CDMA, we just do what we've ''been'' doing: "GSM" and "Global". --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 01:22, 14 September 2013 (UTC)

::::::There's nothing wrong with changing the titles of pages that don't even exist though. If *all* of the models use the same firmware, just go with "iPhone 5s." If they happen to be partitioned into two different firmwares again, that will certainly complicate things, but it wouldn't be worse than nonsense like "GSM," "GSM [<nowiki />Global]," "CDMA," "CDMA [<nowiki />Global]," or "GSM [<nowiki />Global Plus TD-LTE]." If it's just one oddball, we could just have "iPhone 5s" and "iPhone 5s A1XXX" (whatever the odd one is), and include a link on the former page to say "keys for model A1XXX are on this page." --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 02:50, 14 September 2013 (UTC)

::::I probably didn't phrase that well… I wasn't thinking of how Apple markets the product, but rather more along the lines of how they refer to it in, say, the tech specs page or support documents— the pages that shows the messier side to their simple sugar coating. --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 02:50, 14 September 2013 (UTC)

::You keep misinterpreting/misrepresenting what I'm proposing. I never said anything about dropping, say, "iPhone 5" so firmware page titles would look like [[Sundance 10A405 (A1428)]]. I want to change the GSM/Global part to the A1XXX number, so it would probably show like [[Sundance 10A405 (iPhone 5 A1428)]]. (If a hardware revision were made, it would probably look like [[Sundance 10A405 (iPhone 5 A1428 Rev A)]].) From time to time, I edit URLs to browse the wiki too. But the GSM/Global identifiers don't work that well; again, '''all iPhone 5 models can connect to GSM'''. That's not really helpful. --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 02:50, 14 September 2013 (UTC)

:::I suggest we drop the A and use Rev. As for the idea of changing to A1XXX, I see no issues and am for the idea. I admit it can cause chaos when we move the pages but we could limit the moving per day of course. Overall, I think it will be worth it. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 10:01, 14 September 2013 (UTC)

::::No. Don't drop the <code>A</code> from <code>Rev A</code>. Why would you even think to? You want to call them what Apple calls them, and the [[n90bap|revised iPhone 4 GSM]] is referred to with <code>Rev A</code>. In addition, there have been <code>Rev ''B''</code> things before, such as the [[S5L8947]] (A5 Rev B) used in the [[j33iap|revised Apple TV 3G]]. In addition, think of all the redirects we would need to keep for sites that link to key pages directly. I have even seen sites that still link with the URLs as <code>/wiki/index.php?title={Title}</code> instead of the year old change to <code>/wiki/{Title}</code>. The wiki handles that internally for us, but the redirects made in the moves would have to be kept. Currently, only the [[iPhone 5]] and [[iPad 4]] are the only devices referred to by their model numbers. --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 20:53, 14 September 2013 (UTC)

:::That's why I don't want to change it. It's worked for us, and we have no idea how the new firmwares will be handled. I am betting that there will only be two firmware types - one for the GSM, and one for the Global (GSM+CDMA) model. The only reason they are split, IIRC, is because AT&T uses different LTE bands than rest of the GSM world.
:::Ultimately, the GSM/CDMA/Global monikors haven't caused any ''naming conflicts''. Ok, you don't want to use the ''marketing'' title. What about the way they are referred to on [[Apple Developer Center|ADC]], because that seems to be what you want. I may be misreading what you're saying again, but if we're going to do that, let's use their ''full'' title. Something <code>(iPad [4th generation Model A1458])</code> (iPad 4 Wi-Fi) and <code>(iPad Wi-Fi + Cellular [model for Verizon])</code> (iPad 3 Global). Does the first one tell you if the device is Wi-Fi or a Wi-Fi+3G model? Does the second one tell you ''at all'' that it is an [[iPad 3]], or that it supports GSM? No.
:::Apple has a history of being inconsistent. For example, the iPad 3 Wi-Fi is referred to on ADC (and iTunes) as "iPad Wi-Fi (3rd generation)" while the iPad 3 GSM is referred to as "iPad Wi-Fi + Cellular [model for AT&T]". What happened to the "3rd generation"? --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 20:53, 14 September 2013 (UTC)

::::We could always list as <code>iPhone 4 (iPhone3,1)</code> etc instead if that would be better. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 21:13, 14 September 2013 (UTC)

::::Why is there a need to explicitly keep "Wi-Fi" in a key page's title? All you need is a way to distinguish what model it is from its other variants— the A1XXX model number does just that. It's not like we referred to the AppleTV3,2 as "Apple TV 3G (New Single-Core A5)" or something. And obviously, we can use common sense to address the 3rd generation iPad issue you brought up… Now you're just nitpicking. --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 05:28, 15 September 2013 (UTC)
:::::Actually, I think we should wait until we see the firmware for iPhone 5c/5s and then decide. TBH, as [[User:5urd|5urd]] said, it is ok as it is but of course if once the new firmware is out it is more confusing, then we can think again. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 14:12, 15 September 2013 (UTC)

:::::Come to think of it, we can use a mix of both; we can keep the "Global" moniker, but drop the "GSM" moniker in favor of the A1XXX model number. (The "GSM" moniker is the one that's been bothering me.) I think this works well for the iPad 3 (which is actually split into "CDMA" and "Global—" it probably doesn't need to be done for this), iPad 4, iPad mini 1G, and iPhone 5, but this leaves the question of what to do for the iPhone 5C/5S. --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 04:04, 19 September 2013 (UTC)

::::::That would look worse! If we are going to do it, we have to do it for '''''all'''''. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 09:40, 19 September 2013 (UTC)

:::::::What is the status on this now? --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 21:18, 9 November 2013 (UTC)

:::::This discussion has stagnated, but I'm firing it up again— I want to fix this before the end of the year, so this can probably be seen as an ultimatum. Now that Apple has pushed a 7.1 beta to developers, we now know how Apple's splitting the new iPhones up— and it's by A1XXX model numbers still. :\ That's probably the path the wiki will go down, but I do have another idea. The other idea I have in mind is using the A1XXX model number for the cellular devices launched last year. But for this year's iPhones, the FCC ID is actually different between the two, so we could actually use that. Before this gets nitpicked on, the last letter can get changed to an "X" to signify that it's a wildcard of sorts. It's not a pretty solution so I do expect it to get shot down (hence why I'm going with the A1XXX model numbers unless everyone says otherwise), but I'm still throwing it out there in case everyone actually likes that. Everyone is welcome to suggest alternatives, but I '''will''' eliminate that GSM label before the year ends. --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 18:31, 18 November 2013 (UTC)

::::::That is worse, nobody knows the FCC ID off the top of their head. I would suggest "iPhone 5 (iPhone5,1)" if anything. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 18:37, 18 November 2013 (UTC)

:::::::Using "iPhone5,1" or "iPhone6,2" is even ''less'' friendly… The FCC ID can be looked up in Settings or the back of a device. --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 19:06, 18 November 2013 (UTC)

::::::::Well that is not the point. I say either use the firmware name or leave it alone. See what others thing though. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 19:13, 18 November 2013 (UTC)

:::::::::I currently plan on using the A1XXX model numbers— the FCC ID proposal was just thrown out there in the off chance that someone might like it. I'm not really a fan of it myself, but the FCC ID is probably the simplest way to figure out if it's an iPhone6,1 or iPhone6,2 since both have multiple A1XXX model numbers. --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 19:19, 18 November 2013 (UTC)

::::::I agree to get rid of the "GSM" name, as almost all iPhones support GSM. The Axxxx numbers would be nice, but as some phones have several numbers, like A1457/A1518/A1528/A1530 (what is actually different between them?) we can't use it. For the FCC-ID, we can't use that either, because for example the iPhone 5 with FCC-ID BCG-E2599A stands for the GSM/A1428 and also for the GSM+CDMA/A1429 version. So I suggest to either use the identifier (like iPhone2,1) or better the internal name (like n88ap). That would have the advantage to separate them further, because the iPhone 4 A1332 has two internal versions: iPhone3,1/n90ap and the iPhone3,2/n90bap. The bigger question is where you want to use this. That determines mainly the name. On all the key pages? Then it must be a name that is different between models that use different firmwares. And regarding key pages, maybe we should delete all the key pages from this wiki and move them into some database instead and provide a nice user interface and API around it and integrate that into the wiki somehow. That way we can change all pages with one simple edit. For the name, I prefer the internal name. --[[User:Http|http]] ([[User talk:Http|talk]]) 23:43, 18 November 2013 (UTC)

:::::::We would have to edit key pages too. They should not be removed however. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 23:46, 18 November 2013 (UTC)

:::::::Well, I wasn't trying to say that we had to decide on one way to differentiate ''everything''; "GSM" does work fine for, say, the iPhone 4. The proposal I brought up today was using the FCC ID only for this year's (2013's) iPhones— last year's cellular devices would get the A1XXX model numbers (i.e. two different solutions for two different years). But as of right now, I like how using A1XXX model numbers sounds for all of the affected devices, mostly because that's the path Apple's going in their developer portal. Something like "iPhone 5s (Model A1457/A1518/A1528/A1530)" is admittedly a mouthful for this year's iPhones though. At the moment, I'm inquiring about how to label it on [[Firmware]] and such pages, but I'm sure the outcome can be adapted for key page titles as well. As for differences between the models, it seems to be the supported LTE bands. --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 03:49, 19 November 2013 (UTC)

:::::::::I still think that unless it is "iPhone 5 (iPhone5,1)" it will be complicated but on the other hand, I kind of like the idea that [[User:Http|http]] had, using the internal identifiers like this "iPhone 5 (n42ap)". The only problem is that it would cause quite a bit of a flood moving the key pages, although this can be done like 15 per day each or something. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 09:20, 19 November 2013 (UTC)

::::::::::I'm pretty sure the only key page that exists for an A5 (or newer) device is [[Telluride 9A406 (iPhone 4S)]]. --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 17:40, 21 November 2013 (UTC)

:::::::::::That was an example. I know there are no more A5 pages, only the one you said and two beta for iPhone 4S. I just meant that it would show the design. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 13:36, November 21, 2013 (UTC)

== "GSM" Replacement Proposals ==
Since this discussion has become extremely lengthy, here are the proposals (to my understanding) for changing the labels, each of which can be subject to changes (i.e. dropping the word "Model" from Proposal A). In an effort to conserve space (ironically, this still adds a significant amount of length), I only included a few models, which should give an idea of the proposal. Basically anything with an A5 or newer is involved. Feel free to edit this list if I missed or totally misinterpreted something. --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 03:25, 22 November 2013 (UTC)
# Proposal A (A1XXX numbers)
#* iPad 4 (Model A1458)
#* iPad 4 (Model A1459)
#* iPad 4 (Model A1460)
#* iPhone 5 (Model A1428)
#* iPhone 5 (Model A1429/A1442)
#* iPhone 5c (Model A1456/A1532)
#* iPhone 5c (Model A1507/A1516/A1526/A1529)
#* [[InnsbruckTaos 11B554a (iPad 4 A1458)]]
#* [[InnsbruckTaos 11B554a (iPhone 5 A1429/A1442)]]
#* [[InnsbruckTaos 11B554a (iPhone 5c Model A1507/A1516/A1526/A1529)]]
# Proposal B (A1XXX + FCC ID)
#* iPad 4 (Model A1458)
#* iPad 4 (Model A1459)
#* iPad 4 (Model A1460)
#* iPhone 5 (Model A1428)
#* iPhone 5 (Model A1429/A1442)
#* iPhone 5c (BCG‑E2644A)
#* iPhone 5c (BCG‑E2694X)
#* [[InnsbruckTaos 11B554a (iPad 4 A1458)]]
#* [[InnsbruckTaos 11B554a (iPhone 5 A1429/A1442)]]
#* [[InnsbruckTaos 11B554a (iPhone 5c BCG‑E2694X)]]
# Proposal C (-AP Identifier)
#* iPad 4 (p101ap)
#* iPad 4 (p102ap)
#* iPad 4 (p103ap)
#* iPhone 5 (n41ap)
#* iPhone 5 (n42ap)
#* iPhone 5c (n48ap)
#* iPhone 5c (n49ap)
#* [[InnsbruckTaos 11B554a (iPad 4 p101ap)]]
#* [[InnsbruckTaos 11B554a (iPhone 5c n42ap)]]
#* [[InnsbruckTaos 11B554a (iPhone 5c n49ap)]]
# Proposal D (iPhoneX,Y Identifier)
#* iPad 4 (iPad3,4)
#* iPad 4 (iPad3,5)
#* iPad 4 (iPad3,6)
#* iPhone 5 (iPhone5,1)
#* iPhone 5 (iPhone5,2)
#* iPhone 5c (iPhone5,3)
#* iPhone 5c (iPhone5,4)
#* [[InnsbruckTaos 11B554a (iPad3,4)]]
#* [[InnsbruckTaos 11B554a (iPhone5,2)]]
#* [[InnsbruckTaos 11B554a (iPhone5,4)]]

:I like this [[InnsbruckTaos 11B554a iPad 4 (3,4)]] or [[InnsbruckTaos 11B554a iPad 4 (iPad3,4)]]. I see there are 4 ways to approach this;
1. Change every single device. 
2. Change just devices with different variants, iPad 2+, iPad mini+, iPhone 4, iPhone 5+. 
3. Change A5+ only (which I hate the idea of). 
4. Change nothing at all. 
--[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 09:28, 22 November 2013 (UTC)
::My intention for this was to be a ''neutral'' (i.e. opinion-free) spot where all of the proposals were being mentioned, so people could easily see the proposed changes without any bias… v.v --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 20:54, 22 November 2013 (UTC)
:::TBH, I think it is better as it is, but I just stated my opinion that only A5+ would make in inconsistent. Though you could argue it is already, that is down to Apple and furthermore, just A5+ would still not eliminate iPhone 4 (GSM, GSM Rev A or CDMA). --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 17:07, November 22, 2013‎ (UTC)}}

== Key page template ==
I actually like the idea of a database to an extent. I bet I could put together an extension that creates a [[Special:SpecialPages|special page]] that allows read access to everyone (and r/w access to users). Any edits to the key "pages" wouldn't cause a [[Special:RecentChanges|recent changes]] log. If we ever needed to update the layout, we would just need to update the extension. We could even have an API.
The only limitation is that updates to the extension would require either [[User:geohot|George]] or [[User:Dialexio|Alex]] needing to upload the fix. If we were to set up an external site, then all links to it would need to be wrapped with <code>...</code>.
Maybe a simple extension that takes links and redirects you to the external site? That could work. Like, we would have a link to, say, <code>[[<nowiki/>Special:Keys/iPad1,1/9A405]]</code> which would give an HTTP <code>301 Moved Permanently</code> header to, say, <code><nowiki>http://ioskeys.com/iPad1,1/9A405</nowiki></code>. Granted, someone would have to pay for the domain, but it would solve this problem. I may be able to pay for the domain if I make enough money by the time I finish writing everything. Any opposition? --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 16:48, 21 November 2013 (UTC)
:I do not like the idea. I like the idea of the database to a degree, but I think that the pages should remain on this wiki. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 17:03, 21 November 2013 (UTC)
::I don't see this solving any problem— the backlash against changing the key page template was because of (unnecessary?) changes to the arguments, and the frequency of how often such changes were being proposed/applied. How would a database prevent it? For instance, let's say the database columns are all decided on. Suddenly, it's decided that SHA-1 hashes should be added as well, or perhaps "VFDecryptKey" will be renamed to "FSKey." People submitting keys would still be bothered with having to adjust for those changes. --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 17:40, 21 November 2013 (UTC)
:::That with the database is something I'll implement anyway (if not someone else is faster, as I'm quite busy). I just threw that in here as it might solve the problem of the frequent template updates (which is/was wrong anyway). From there it would be easy to create the VFDecrypt page with an overview link or lists of missing keys and that stuff, so the wiki would not need any direct links. But it would mean that we either completely remove all keys here from the wiki and embrace that solution or have them still duplicate (which then doesn't solve the problem). Dialexio: renaming columns can be handled without interface changes, but that's another topic. So let's forget about this database thing for now and we can discuss again when I have something. We certainly don't want to add extensions for that. So back to the discussion about the renaming: If I understood this correctly, you only want to rename A5+ devices and therefore no key pages would be affected. Is my understanding correct? --[[User:Http|http]] ([[User talk:Http|talk]]) 22:08, 21 November 2013 (UTC)
::::As long as the pages stay on this wiki, I do not mind. Although, a database could be pointless as with only 50 more pages to edit for the new format, there is no planned new format/changes again. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 22:16, 21 November 2013 (UTC)
::::About the renaming, that is correct; I'm only interested in changing the cellular labels on A5/+ devices. (Well, the iPad 2 can remain as-is.) --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 00:02, 22 November 2013 (UTC)
:::::Oh, well that would just make things more complicated/inconsistent. We should do all or none. About the template idea, there is also no need as it is not likely we will change the format again. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 00:35, 22 November 2013 (UTC)
:::::This ^; Do them all, and do them like #4. --[[User:CompilingEntropy|CompilingEntropy]] ([[User talk:CompilingEntropy|talk]]) 18:39, 23 November 2013 (UTC)

==Login prompt revision suggestion==
I wrote a suggestion here: [[MediaWiki talk:Loginprompt]] (since I don't have permission to edit [[MediaWiki:Loginprompt]] directly) - I'd be interested in whether it sounds like a good idea to other people. [[User:Britta|Britta]] ([[User talk:Britta|talk]]) 01:00, 8 October 2013 (UTC)

==Homepage suggestions==
Under "Application Development", what about linking to [http://iphonedevwiki.net/index.php/Main_Page iPhoneDevWiki]? It's also a community-edited technical resource, and it links to this wiki. It could be helpful to add a little more detail to "Get [[up to speed]] in the community.", like this: "Get [[up to speed]] in the community - learn about how jailbreaks work." Under "Definitions", it could be helpful to list all the firmware tags in one line or sub-list, similar to how Jailbreak is organized next to Tethered jailbreak and Untethered jailbreak, both to save space and help readers understand the list. --[[User:Britta|Britta]] ([[User talk:Britta|talk]]) 23:01, 20 October 2013 (UTC)
:A link to the iPhoneDevWiki sounds good. I wonder if we should have an "External Links" or "Other Resources" section to include links to other sites (such as the [http://blog.iphone-dev.org/ iPhone Dev Team blog]) though. As for the "Up to Speed" page, I feel like the entire page could be reworked a bit— and perhaps even receive a new, clearer name ([[Introduction]]? [[Preface]]? Or something else?)— the current name makes it sound like it's for people that last paid attention to jailbreaking when the App Store didn't exist. And yeah, moving the IMG3 tags to a sub-list sounds like a really good idea. (Admittedly, I actually don't care for its inclusion in the first place, but that's just a personal preference.) --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 00:10, 21 October 2013 (UTC)
::There's already [[Useful Links]] with some links to other core community resources (which could be updated and rearranged) - I was just thinking that it'd be especially useful to link to iPhoneDevWiki prominently since it's likely for TheiPhoneWiki visitors to also be interested in relatively-organized technical information about development. Changing the name of "Up to Speed" sounds fine to me too - that page didn't get much attention since 2008 until I sort of commandeered it to serve as an "intro to jailbreaking" page. :) It could be renamed "getting started", as in "how to get started on learning about research into iOS devices, especially security research (such as jailbreaks)". [[User:Britta|Britta]] ([[User talk:Britta|talk]]) 00:31, 21 October 2013 (UTC)
Also I'd love to see a dedicated section for "Good tasks for new editors", where we could maintain a list of relatively easy/straightforward suggested edits that wouldn't require vast technical knowledge, like updating that links page. Where would that go? Add it as a sub-section of [[The iPhone Wiki:Current events]] and link that section from the homepage or something? Or make a new page? [[User:Britta|Britta]] ([[User talk:Britta|talk]]) 00:40, 21 October 2013 (UTC)

==What is 0x5265c384 in the boot process?==
Does anybody know where <code>0x5265c384</code> points to in the boot process? I haven't been able to find anything on it. --[[User:Ph0enix|Ph0enix]] ([[User talk:Ph0enix|talk]]) 20:14, 23 October 2013 (UTC)

==License for contributions==
This wiki has never had an official license for contributions. Now, IANAL, but IIRC, this means that you can't use ''anything'' posted here unless it qualifies as fair-use. What I propose is that we set a license and add a notice that states that any contributions after a set date are to be licensed under that license (that's kindof a mouthful). I think we should use the [http://creativecommons.org/licenses/by-sa/3.0/ CC-by-SA 3.0] as [[wikipedia:Wikipedia:Text of Creative Commons Attribution-ShareAlike 3.0 Unported License|Wikipedia uses it]], but that's just me. Any ideas? --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 19:53, 9 November 2013 (UTC)
:Well, the edit info already says all this:
Please note that all contributions to The iPhone Wiki may be edited, altered, or
removed by other contributors. If you do not want your writing to be edited mercilessly,
then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public
domain or similar free resource (see The [[:The iPhone Wiki:Copyrights|iPhone Wiki:Copyrights]] for details). '''Do not'''
'''submit copyrighted work without permission!'''
For me, that's enough. I don't need a 50 page license. But if you want to formalize this more, go ahead. --[[User:Http|http]] ([[User talk:Http|talk]]) 20:35, 9 November 2013 (UTC)

:Sounds good. It's good practice to have an official license, just in case any disputes happen someday, and to ensure that it's OK to copy text over to Wikipedia (for example). [[User:Britta|Britta]] ([[User talk:Britta|talk]]) 21:32, 9 November 2013 (UTC)

==Future plans==
Now that I have SSH access, I've begun working on making several, somewhat-overdue changes to the wiki. The Renameuser extension was reinstated, so admins can now rename accounts. If you have another account, that can also get merged into your current account. If you happen to get locked out from both your account and the email used is no longer active, I can run a script to reset your password. I've also begun implementing a very noticeable change— as users of the Vector skin have noticed, the iOS 6-based theming is gone. It's a semi-temporary move though; it's going into its own skin, because… you know, choice is cool. People who like the Vector skin may not have liked the iOS theming, especially since IE 9 and lower didn't display it completely accurately. Therefore, it's going into its own theme. Once that's done I also plan on making a separate iOS 7-based skin. If there are any further thoughts or suggestions on how to improve the wiki, do let me know! --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 22:18, 9 November 2013 (UTC)

==TOC==
I was wondering if it may look better if we made the TOC show horizontal because currently, like on [[Firmware]], you have to scroll down quite a way to get to the actual devices. I know that you can click "hide" but that is not the point as it is still ugly imo. What do you all think? Also, someone on IRC has said that they have seen three people get the wrong IPSW with the numbering before the variants, thinking that it is the device model number. Any way that it could be changed to drop that numbering as I also agree it is oddly numbered? --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 19:09, 10 November 2013 (UTC)

Fuzzing

2013-10-27T05:59:57Z

CompilingEntropy: added line breaks

The idea behind fuzzing is that a sufficiently complex program (specifically, one designed to be able to accept an infinite amount of different inputs, such as packets or files) cannot possibly know how to parse and handle an infinite amount of different inputs, throwing errors when that input is invalid. Fuzzing is a technique that consists of repeatedly and intentionally providing a program with invalid (and in some cases, random) input in an attempt to cause the program to behave erratically. Erratic behaviors include, but are not limited to: crashing the program, halting it, leaking memory, failing error handling, bypassing input sanitation checks, etc. These behaviors are desired because they occasionally hint at deeper, underlying vulnerabilities can potentially be exploitable. The two most common targets of fuzzing are files and file formats, and network protocols; any input can be fuzzed, however.

For a detailed description on fuzzing, you should probably look elsewhere. This page deals with fuzzing in its relation to iOS. Fuzzing has been used in the jailbreak scene on several occasions to find bugs. Two notable occasions include SHAtter by the Chronic Dev Team, where DFU mode was fuzzed on non-standard pins using a special cable, and Saffron by Comex, where PDFs were fuzzed leading to the discovery of a vulnerability present in the handling of true-type fonts.

===Fuzzing MobileSafari===
Fuzzing iOS applications, MobileSafari specifically, was covered in chapter 6 of the iOS Hacker's Handbook. MobileSafari has specific interest as an injection vector because it handles so many different filetypes. It's easily the largest remote attack surface on the iOS platform. 
From p0sixninja: "MobileSafari is special, it's the only process that is allowed JIT permissions. It can execute dynamically generated bytecode." 
Given these facts on top of how many public exploits there are in webkit, the engine behind MobileSafari, it's surprising how few jailbreaks take advantage of exploits in MobileSafari. The "JailbreakMe" series of jailbreaks are the primary way MobileSafari has been historically exploited. This has a lot to do with the complicated exploit chain necessary to go from an exploit in MobileSafari to a kernel exploit. Still, MobileSafari exploits are more valuable and higher risk because they can be deployed remotely. For this reason, the fuzzing of MobileSafari has remained relevant despite the relative lack of public releases of end-to-end jailbreaks that utilize them. 
Tools have been developed to fuzz files directly on a jailbroken iOS device. The source for a python fuzzer is in chapter 6 of the iOS Hacker's Handbook. Zzuf was ported to iOS by Comex. Multiple solutions have been implemented for the automatic injection of fuzzed files into MobileSafari, most utilizing an instance of a local server on the device (such as lighttpd) and a tweak that causes MobileSafari to refresh, loading a new file, each time a darwin notification is received. Using these and other methods, MobileSafari has been fuzzed with some success.

===Fuzzing DFU Mode===
Someone who knows more about how this was done should complete this section. From what I understand, DFU mode was fuzzed on non-standard pins through almost every command that can be fed to DFU by p0sixninja & the Chronic Dev team. Crashes were found that led to the discovery of a vulnerability which was later exploited by pod2g and p0sixninja. Presumably, fuzzing is how several DFU bugs have been discovered.

Fuzzing

2013-10-27T05:57:49Z

CompilingEntropy: duplicate title

The idea behind fuzzing is that a sufficiently complex program (specifically, one designed to be able to accept an infinite amount of different inputs, such as packets or files) cannot possibly know how to parse and handle an infinite amount of different inputs, throwing errors when that input is invalid. Fuzzing is a technique that consists of repeatedly and intentionally providing a program with invalid (and in some cases, random) input in an attempt to cause the program to behave erratically. Erratic behaviors include, but are not limited to: crashing the program, halting it, leaking memory, failing error handling, bypassing input sanitation checks, etc. These behaviors are desired because they occasionally hint at deeper, underlying vulnerabilities can potentially be exploitable. The two most common targets of fuzzing are files and file formats, and network protocols; any input can be fuzzed, however.

For a detailed description on fuzzing, you should probably look elsewhere. This page deals with fuzzing in its relation to iOS. Fuzzing has been used in the jailbreak scene on several occasions to find bugs. Two notable occasions include SHAtter by the Chronic Dev Team, where DFU mode was fuzzed on non-standard pins using a special cable, and Saffron by Comex, where PDFs were fuzzed leading to the discovery of a vulnerability present in the handling of true-type fonts.

===Fuzzing MobileSafari===
Fuzzing iOS applications, MobileSafari specifically, was covered in chapter 6 of the iOS Hacker's Handbook. MobileSafari has specific interest as an injection vector because it handles so many different filetypes. It's easily the largest remote attack surface on the iOS platform.
From p0sixninja: "MobileSafari is special, it's the only process that is allowed JIT permissions. It can execute dynamically generated bytecode."
Given these facts on top of how many public exploits there are in webkit, the engine behind MobileSafari, it's surprising how few jailbreaks take advantage of exploits in MobileSafari. The "JailbreakMe" series of jailbreaks are the primary way MobileSafari has been historically exploited. This has a lot to do with the complicated exploit chain necessary to go from an exploit in MobileSafari to a kernel exploit. Still, MobileSafari exploits are more valuable and higher risk because they can be deployed remotely. For this reason, the fuzzing of MobileSafari has remained relevant despite the relative lack of public releases of end-to-end jailbreaks that utilize them.
Tools have been developed to fuzz files directly on a jailbroken iOS device. The source for a python fuzzer is in chapter 6 of the iOS Hacker's Handbook. Zzuf was ported to iOS by Comex. Multiple solutions have been implemented for the automatic injection of fuzzed files into MobileSafari, most utilizing an instance of a local server on the device (such as lighttpd) and a tweak that causes MobileSafari to refresh, loading a new file, each time a darwin notification is received. Using these and other methods, MobileSafari has been fuzzed with some success.

===Fuzzing DFU Mode===
Someone who knows more about how this was done should complete this section. From what I understand, DFU mode was fuzzed on non-standard pins through almost every command that can be fed to DFU by p0sixninja & the Chronic Dev team. Crashes were found that led to the discovery of a vulnerability which was later exploited by pod2g and p0sixninja. Presumably, fuzzing is how several DFU bugs have been discovered.

Fuzzing

2013-10-27T05:57:31Z

CompilingEntropy: Initial creation, please edit mercelessly

=Fuzzing=
The idea behind fuzzing is that a sufficiently complex program (specifically, one designed to be able to accept an infinite amount of different inputs, such as packets or files) cannot possibly know how to parse and handle an infinite amount of different inputs, throwing errors when that input is invalid. Fuzzing is a technique that consists of repeatedly and intentionally providing a program with invalid (and in some cases, random) input in an attempt to cause the program to behave erratically. Erratic behaviors include, but are not limited to: crashing the program, halting it, leaking memory, failing error handling, bypassing input sanitation checks, etc. These behaviors are desired because they occasionally hint at deeper, underlying vulnerabilities can potentially be exploitable. The two most common targets of fuzzing are files and file formats, and network protocols; any input can be fuzzed, however.

For a detailed description on fuzzing, you should probably look elsewhere. This page deals with fuzzing in its relation to iOS. Fuzzing has been used in the jailbreak scene on several occasions to find bugs. Two notable occasions include SHAtter by the Chronic Dev Team, where DFU mode was fuzzed on non-standard pins using a special cable, and Saffron by Comex, where PDFs were fuzzed leading to the discovery of a vulnerability present in the handling of true-type fonts.

===Fuzzing MobileSafari===
Fuzzing iOS applications, MobileSafari specifically, was covered in chapter 6 of the iOS Hacker's Handbook. MobileSafari has specific interest as an injection vector because it handles so many different filetypes. It's easily the largest remote attack surface on the iOS platform.
From p0sixninja: "MobileSafari is special, it's the only process that is allowed JIT permissions. It can execute dynamically generated bytecode."
Given these facts on top of how many public exploits there are in webkit, the engine behind MobileSafari, it's surprising how few jailbreaks take advantage of exploits in MobileSafari. The "JailbreakMe" series of jailbreaks are the primary way MobileSafari has been historically exploited. This has a lot to do with the complicated exploit chain necessary to go from an exploit in MobileSafari to a kernel exploit. Still, MobileSafari exploits are more valuable and higher risk because they can be deployed remotely. For this reason, the fuzzing of MobileSafari has remained relevant despite the relative lack of public releases of end-to-end jailbreaks that utilize them.
Tools have been developed to fuzz files directly on a jailbroken iOS device. The source for a python fuzzer is in chapter 6 of the iOS Hacker's Handbook. Zzuf was ported to iOS by Comex. Multiple solutions have been implemented for the automatic injection of fuzzed files into MobileSafari, most utilizing an instance of a local server on the device (such as lighttpd) and a tweak that causes MobileSafari to refresh, loading a new file, each time a darwin notification is received. Using these and other methods, MobileSafari has been fuzzed with some success.

===Fuzzing DFU Mode===
Someone who knows more about how this was done should complete this section. From what I understand, DFU mode was fuzzed on non-standard pins through almost every command that can be fed to DFU by p0sixninja & the Chronic Dev team. Crashes were found that led to the discovery of a vulnerability which was later exploited by pod2g and p0sixninja. Presumably, fuzzing is how several DFU bugs have been discovered.

Template talk:Keys

2013-10-08T20:15:30Z

CompilingEntropy:

== File Names ==
I know why we list the file names of the Root FS and ramdisks: to know which is which. Why don't we list the file names of the other ([[IMG3 File Format|IMG3]]) files? I have seen some [[n82ap|iPhone 3G]] (<code>iPhone1,2</code>/<code>n82ap</code>) firmwares that contain [[m68ap|iPhone 2G]] (<code>iPhone1,1</code>/<code>m68ap</code> IMG3 files also under <code>/Firmware/dfu</code> and <code>/Firmware/all_flash</code>. There have also been some firmwares that contain multiple [[Kernelcache]]s. To know which is which, you need to look up the [[Application Processor|application processor]]'s name. If you have the keys in front of you, it would make sense to have the file name also. Listing the file names of the Root FS and ramdisks makes it so you don't have to look in <code>BuildManifest.plist</code> to find out which is which. So why do we make you have to look up the applicatioin processor's name? Granted, this situation doesn't happen that often, but it would still make sense. As for how to acomplish this, we can just use the current method for IMG3 files, but modified a bit ([[Big Bear 5C1 (iPhone)|iPhone 2G 2.0.2 (5C1)]]):
| iBSS = iBSS.m68ap.RELEASE.dfu
| iBSSIV = TODO
| iBSSKey = TODO
Any ideas? --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 15:58, 3 October 2013 (UTC)
:Sounds like a great idea, but I would also add an option for the kernelcache (not the key) but the filename. --[[User:Phyrrus9|Phyrrus9]] ([[User talk:Phyrrus9|talk]]) 02:04, 5 October 2013 (UTC)
:I propose no such changes to key pages (we have many existing ones and updating them all is a pain - not to mention those of us who can ''actually grab keys'' keep having to change our templates.) --[[User:Cj|cj]] ([[User talk:Cj|talk]]) 16:57, 8 October 2013 (UTC)
:I'm with cj on this, it's frustrating to be updating things all the time just to keep up with the latest template. Additionally, I don't think the filenames are necessary; anyone who is going to be doing this type of thing will know how to find the file they're looking for without being told the exact filename. --[[User:CompilingEntropy|CompilingEntropy]] ([[User talk:CompilingEntropy|talk]]) 20:15, 8 October 2013 (UTC)

User:CompilingEntropy

2013-10-07T19:55:35Z

CompilingEntropy:

==About Me==
I'm a 19 year old dude who likes hacking and computers in general.
A few of my interests:
*Security (making and breaking)
*Wireless anything
*802.11 protocols
*Networking
*Zelda
*Rubik's Cubes
*Women

[http://github.com/compilingEntropy Github: compilingEntropy]<br\>
[http://twitter.com/compiledEntropy Twitter: @compiledEntropy]<br\>
[mailto:compilingEntropy@gmail.com compilingEntropy@gmail.com]

==Projects==
[[Keylimepie]]: A tool for mac that automates grabbing keys/ivs from IPSWs.

User:CompilingEntropy

2013-10-07T19:53:04Z

CompilingEntropy: Actual info and formatting, yo

==About Me==
I'm a 19 year old dude who likes hacking and computers in general.
A few of my interests:
*Security (making and breaking)
*Wireless anything
*802.11 protocols
*Networking
*Zelda
*Rubik's Cubes
*Women

[http://github.com/compilingEntropy Github]<br\>
[http://twitter.com/compiledEntropy Twitter]

==Projects==
[[Keylimepie]]: A tool for mac that automates grabbing keys/ivs from IPSWs.

Talk:Keylimepie

2013-10-07T05:35:27Z

CompilingEntropy:

== Timing ==

You should write something to autodetect device timing, I will look at it (already forked) but no guarantees. --[[User:Phyrrus9|Phyrrus9]] ([[User talk:Phyrrus9|talk]]) 21:06, 2 October 2013 (UTC)
:Thanks for the suggestion Phyrrus9, I'm planning on doing that. Eventually, the idea is for the whole process will be automated; I'm trying to move away from greenpois0n and recboot (instead using some syringe tools), and use iRecovery to detect what mode the device is in instead of relying on user feedback. --[[User:CompilingEntropy|CompilingEntropy]] ([[User talk:CompilingEntropy|talk]]) 22:13, 2 October 2013 (UTC)
::I would be willing to help out with that. --[[User:Phyrrus9|Phyrrus9]] ([[User talk:Phyrrus9|talk]]) 00:05, 3 October 2013 (UTC)
:::That would be great; what I need the most help with right now is getting a working version of injectpois0n. It always gives me <code>segmentation fault 11</code> when I compile it from source, and I haven't been able to fix it. --[[User:CompilingEntropy|CompilingEntropy]] ([[User talk:CompilingEntropy|talk]]) 12:51, 5 October 2013 (UTC)
::::If you can tell me where you got that code, and send me a zip of your current tree, I can find the fault. email is at [[User:Phyrrus9]] --[[User:Phyrrus9|Phyrrus9]] ([[User talk:Phyrrus9|talk]]) 00:37, 6 October 2013 (UTC)
:::::The source is available at https://github.com/Chronic-Dev/syringe, I'll be able to email you a precompiled zip on Tuesday. --[[User:CompilingEntropy|CompilingEntropy]] ([[User talk:CompilingEntropy|talk]]) 08:22, 6 October 2013 (UTC)
::::::I can compile syringe, I mean is the code on your github the most current? --[[User:Phyrrus9|Phyrrus9]] ([[User talk:Phyrrus9|talk]]) 19:31, 6 October 2013 (UTC)
:::::::Yep, the latest is on github. To be clear, injectpois0n segfaults when run on its own for me. If I could get past that, I could easily implement it in keylimepie. --[[User:CompilingEntropy|CompilingEntropy]] ([[User talk:CompilingEntropy|talk]]) 05:35, 7 October 2013 (UTC)

Talk:Keylimepie

2013-10-06T08:22:04Z

CompilingEntropy: /* Timing */

Talk:Keylimepie

2013-10-05T12:51:11Z

CompilingEntropy: /* Timing */

User talk:CompilingEntropy

2013-10-02T22:15:04Z

CompilingEntropy:

Contact me at [mailto:compilingEntropy@gmail.com compilingEntropy@gmail.com], or on twitter @compiledEntropy.

User talk:CompilingEntropy

2013-10-02T22:14:52Z

CompilingEntropy:

Contact me at [mailto:compilingEntropy@gmail.com], or on twitter @compiledEntropy.

User talk:CompilingEntropy

2013-10-02T22:14:01Z

CompilingEntropy: Created page with "Contact me at compilingEntropy@gmail.com, or on twitter @compiledEntropy."

Contact me at compilingEntropy@gmail.com, or on twitter @compiledEntropy.

Talk:Keylimepie

2013-10-02T22:13:20Z

CompilingEntropy: /* Timing */

Keylimepie

2013-10-02T20:08:50Z

CompilingEntropy:

{{lowercase}}
'''keylimepie''' is an automated script for OS X that grabs the IV's, Keys and the RootFS key for the key pages. This stores the [[KBAG]]'s into a file called KBAG.txt. Once it has the keys, two files are created: keys.txt which holds the keys and also wikikeys.txt which has the keys in the layout so that you can copy/paste the file content to the page on this wiki. It is written in bash. The syntax is <code>./keylimepie.sh ./path_to_IPSW [-t2]</code> - the <code>-t2</code> is optional, and should only be used if your timing is consistently off.

==Supported Devices==
* [[n88ap|iPhone 3GS]]
* [[n90ap|iPhone 4 GSM]]
* [[n72ap|iPod touch 2G]]
* [[n18ap|iPod touch 3G]]
* [[n81ap|iPod touch 4G]]

==External Links==
* [https://github.com/compilingEntropy/keylimepie GitHub]

[[Category:Decryption]]

Sugar Bowl 5F138 (iPod2,1)

2013-10-02T17:37:08Z

CompilingEntropy:

{{keys
| version = 2.1.1
| build = 5F138
| device = ipod21
| codename = Sugar Bowl
| downloadurl = http://appldnld.apple.com.edgesuite.net/content.info.apple.com/iPod/SBML/osx/bundles/061-5494.20080909.8i9o0/iPod2,1_2.1.1_5F138_Restore.ipsw

| rootfsdmg = 018-4160-1
| rootfskey = d1b957a0a5e56903adc523c5fa99f5d165c3963aea48274770b766b44ecdebab7b5a8f30

| updatedmg = 018-4177-1
| updateiv = 5447fa2ce0e2a6e39ffe8983be161e88
| updatekey = 87ecb5a20030a9350cf50de6a43413ac

| restoredmg = 018-4166-1
| restoreiv = 2f4481855ca39e67dfbf3d19b8ade60e
| restorekey = 6d4a00c0a08e90a3b024885f45bcb720

| AppleLogoIV = 64238fb03291422522b5dd283fc3895c
| AppleLogoKey = 859fd4d382b8385156fc581a7f1d9722

| BatteryLow0IV = cd40a18b7f454972a57f7bff2d994742
| BatteryLow0Key = 9fcbdce6092ad1ddfeea6224d403ad55

| BatteryLow1IV = ec0fb10072fda682ed5ffff80400f803
| BatteryLow1Key = 315aa2957e581cafb0ae3fc7f55cb9ac

| DeviceTreeIV = ccff634ee12735f01916c4a6b20ff145
| DeviceTreeKey = e17bcd568df1cddc8fecbf5487d5c3ce

| GlyphChargingIV = 4d131595de30c67fd277279c33ee1bca
| GlyphChargingKey = 7267785f56ba9a4a05e11658a5a3ec3d

| GlyphPluginIV = c42a87b7a92b24bcdea56edf1b74417a
| GlyphPluginKey = a7676d7767ca1d12a7dbf31270e2b6c9

| iBECIV = 9eff6fb9e4b9fd4ce0b9a10ed82c6bd0
| iBECKey = 83000205209203001e95d69d960065ee

| iBootIV = b3633afbe02e0e9ba4d7366c47abe5a8
| iBootKey = 2d916dabb6dfd4594dbe3635b4c71662

| iBSSIV = 9eff6fb9e4b9fd4ce0b9a10ed82c6bd0
| iBSSKey = 83000205209203001e95d69d960065ee

| KernelcacheIV = a191291290d487ff0731969c5fc8d918
| KernelcacheKey = 0e4d23fa675999d5959dd10c8dd73d20

| LLBIV = ce97a7c82ef864675ed3680597ec2aef
| LLBKey = 27732a6bbfb14a07250a2e4682bf3cba

| NeedServiceIV = TODO
| NeedServiceKey = TODO

| RecoveryModeIV = 47621cf22dc1b45ada5aaa4b0124dded
| RecoveryModeKey = c9de0834428ca28ecf5392ec9195ce79
}}

User:CompilingEntropy

2013-10-02T17:33:18Z

CompilingEntropy:

I'm a 19 year old dude who likes hacking iPhones. I'm writing keylimepie, a tool for mac that will grab keys/ivs for IPSWs.

http://github.com/compilingEntropy
http://twitter.com/compiledEntropy

User:CompilingEntropy

2013-10-02T17:32:23Z

CompilingEntropy: created page

I'm a 19 year old dude who likes hacking iPhones.

http://github.com/compilingEntropy
http://twitter.com/compiledEntropy

Sugar Bowl 5F138 (iPod2,1)

2013-10-02T17:09:28Z

CompilingEntropy:

{{keys
| version = 2.1.1
| build = 5F138
| device = ipod21
| codename = Sugar Bowl
| downloadurl = http://appldnld.apple.com.edgesuite.net/content.info.apple.com/iPod/SBML/osx/bundles/061-5494.20080909.8i9o0/iPod2,1_2.1.1_5F138_Restore.ipsw

| rootfsdmg = 018-4160-1
| rootfskey = d1b957a0a5e56903adc523c5fa99f5d165c3963aea48274770b766b44ecdebab7b5a8f30

| updatedmg = 018-4177-1
| updateiv = 5447fa2ce0e2a6e39ffe8983be161e88
| updatekey = 87ecb5a20030a9350cf50de6a43413ac

| restoredmg = 018-4166-1
| restoreiv = 2f4481855ca39e67dfbf3d19b8ade60e
| restorekey = 6d4a00c0a08e90a3b024885f45bcb720

| AppleLogoIV = 64238fb03291422522b5dd283fc3895c
| AppleLogoKey = 859fd4d382b8385156fc581a7f1d9722

| BatteryLow0IV = cd40a18b7f454972a57f7bff2d994742
| BatteryLow0Key = 9fcbdce6092ad1ddfeea6224d403ad55

| BatteryLow1IV = ec0fb10072fda682ed5ffff80400f803
| BatteryLow1Key = 315aa2957e581cafb0ae3fc7f55cb9ac

| DeviceTreeIV = ccff634ee12735f01916c4a6b20ff145
| DeviceTreeKey = e17bcd568df1cddc8fecbf5487d5c3ce

| GlyphChargingIV = 4d131595de30c67fd277279c33ee1bca
| GlyphChargingKey = 7267785f56ba9a4a05e11658a5a3ec3d

| GlyphPluginIV = c42a87b7a92b24bcdea56edf1b74417a
| GlyphPluginKey = a7676d7767ca1d12a7dbf31270e2b6c9

| iBECIV = 9eff6fb9e4b9fd4ce0b9a10ed82c6bd0
| iBECKey = 83000205209203001e95d69d960065ee

| iBootIV = b3633afbe02e0e9ba4d7366c47abe5a8
| iBootKey = 2d916dabb6dfd4594dbe3635b4c71662

| iBSSIV = 9eff6fb9e4b9fd4ce0b9a10ed82c6bd0
| iBSSKey = 83000205209203001e95d69d960065ee

| KernelcacheIV = a191291290d487ff0731969c5fc8d918
| KernelcacheKey = 0e4d23fa675999d5959dd10c8dd73d20

| LLBIV = ce97a7c82ef864675ed3680597ec2aef
| LLBKey = 27732a6bbfb14a07250a2e4682bf3cba

| NeedServiceIV = f8072ff468f7947daf0d5b5e4433a273
| NeedServiceKey = c8807d5e7240b3a963ff4c32a82d42a5

| RecoveryModeIV = 47621cf22dc1b45ada5aaa4b0124dded
| RecoveryModeKey = c9de0834428ca28ecf5392ec9195ce79
}}

SHSH

2013-02-20T03:02:28Z

CompilingEntropy: /* Timeline */

0x80 byte RSA signature of a firmware image.

This often also refers to the backup file with the signature ("SHSH blobs"). This signature is needed to restore a specific iOS version; it is generated by Apple based on hardware keys of the device and the hash of the firmware. Apple only issues signatures for the currently-available iOS version, which disallows installing older iOS versions. But if you have saved signatures for an older iOS version, you can use a [[wikipedia:replay attack|replay attack]] to restore that version. Therefore it is recommended to save the signature for your device as long as Apple issues it.

With the tools mentioned below it is possible to backup the signature. It is not necessary that the device is jailbroken to do the backup. Usually the SHSH signature file is stored on [[Cydia Server|Saurik's server]]. If it is stored there, then you can see in the top of [[Cydia Application|Cydia]] (on jailbroken devices) for which version a backup exists.

Users often misunderstand this system and think that the SHSH firmware version they back up depends on the firmware version they have installed on their device. This is the case for [[iFaith]], but not for TinyUmbrella. iFaith dumps the SHSHs from your device's storage (whatever's installed on your device, e.g. 4.3.3), while TinyUmbrella gets SHSHs from Apple's servers (whatever firmwares Apple is currently signing).

==Using SHSH==
Older devices allow installation of any correctly signed firmware, so no backup of the certificate is necessary. Devices that need Apple signatures are: [[N88ap|iPhone 3GS]], [[N90ap|iPhone 4]], [[N18ap|iPod touch 3G]], [[K48ap|iPad]], [[iPad 2]], [[n81ap|iPod touch 4G]], [[K66ap|Apple TV 2G]] and all newer devices. The [[N88ap|iPhone 3G]] and [[N72ap|iPod touch 2G]] bootroms do not require these SHSHs; however, newer versions of iOS require them (unless the chain of trust is broken and custom firmwares are installed). To restore to arbitrary versions of iOS 4.0, the SHSH is also needed for the [[N72ap|iPod touch 2G]] and [[N82ap|iPhone 3G]]. not only does [[DFU Mode]] require the [[iBSS]]/[[iBEC]] files to be signed with an SHSH that includes the device's [[ECID]], but the normal boot-chain requires the [[LLB]] to be fully signed with an [[ECID]]+SHSH, so a downgrade [[IPSW File Format|IPSW]] is not possible without a bootrom exploit of normal boot-chain (e.g. [[0x24000 Segment Overflow]]). See also the [http://blog.iphone-dev.org/post/833937433 Dev Team Blog post] about this.

To restore to iOS 3.x or 4.x, change your hosts file to map any request to an Apple server to point to [[Saurik]]'s server instead, if your device's signatures are hosted there. If you have the signature file on your computer, run [[TinyUmbrella]]'s TSS Server on your local machine.

Since the [[limera1n exploit]] is fixed in the [[bootrom]] since version [[Bootrom 838.3]] and because iOS since 5.0 includes a [[nonce]] in their SHSH hashes, downgrading newer devices ([[N94ap|iPhone 4S]], [[iPad 2]], [[iPad 3]], [[J33ap|Apple TV 3G]]) to earlier 5.x firmwares is not as simple. To restore to iOS 5.x on older devices, stitch iOS 5.x blobs into custom firmware (using redsn0w for example) and restore with that firmware. To restore to iOS 5.x on newer devices, use redsn0w's restore method. See the [http://www.jailbreakqa.com/questions/32462/frequently-asked-questions#94647 JailbreakQA guide to restoring to iOS 5.x using SHSH blobs] (for all devices that can run iOS 5.x except Apple TV 3G).

==Timeline==
{| class="wikitable" style="text-align: center; width: auto; table-layout: fixed; border-collapse: collapse;" border="1"
|-
! width="50" | iOS
! width="480" | for Device(s)
! width="130" | From
! width="130" | Until
! width="130" | Status
|-
| 3.0
| rowspan="3" | [[N88ap|iPhone 3GS]]
| 19 June 2009
| 9 September 2009
| {{no|Closed}}
|-
| 3.0.1
| 31 July 2009
| 9 September 2009
| {{no|Closed}}
|-
| 3.1
| 9 September 2009
| 8 October 2009
| {{no|Closed}}
|-
| 3.1.1
| [[N72ap|iPod touch 2G]]
| 9 September 2009
| 21 June 2010
| {{no|Closed}}
|-
| 3.1.1
| [[N18ap|iPod touch 3G]]
| 9 September 2009
| 8 October 2009
| {{no|Closed}}
|-
| 3.1.2
| [[N72ap|iPod touch 2G]]
| 8 October 2009
| 21 June 2010
| {{no|Closed}}
|-
| 3.1.2
| [[N88ap|iPhone 3GS]], [[N18ap|iPod touch 3G]]
| 8 October 2009
| 2 February 2010
| {{no|Closed}}
|-
| 3.1.3
| [[M68ap|iPhone]], [[N45ap|iPod touch 1G]]
| 2 February 2010
| -
| {{yes|Open}}
|-
| 3.1.3
| [[N72ap|iPod touch 2G]]
| 2 February 2010
| 21 June 2010
| {{no|Closed}}
|-
| 3.1.3
| [[N88ap|iPhone 3GS]], [[N18ap|iPod touch 3G]]
| 2 February 2010
| 21 June 2010
| {{no|Closed}}
|-
| 3.2
| rowspan="3" | [[K48ap|iPad]]
| 3 April 2010
| 15 July 2010
| {{no|Closed}}
|-
| 3.2.1
| 15 July 2010
| 19 August 2010
| {{no|Closed}}
|-
| 3.2.2
| 11 August 2010
| 2 December 2010 (?)
| {{no|Closed}}
|-
| 4.0
| [[N72ap|iPod touch 2G]]
| 21 June 2010
| 9 September 2010
| {{no|Closed}}
|-
| 4.0
| [[N18ap|iPod touch 3G]]
| 21 June 2010
| 19 August 2010
| {{no|Closed}}
|-
| 4.0
| [[N82ap|iPhone 3G]], [[N88ap|iPhone 3GS]]
| 21 June 2010
| 15 July 2010
| {{no|Closed}}
|-
| 4.0
| [[N90ap|iPhone 4 GSM]]
| 24 June 2010
| 15 July 2010
| {{no|Closed}}
|-
| 4.0.1
| [[N82ap|iPhone 3G]]
| 15 July 2010
| 9 September 2010
| {{no|Closed}}
|-
| 4.0.1
| [[N88ap|iPhone 3GS]], [[N90ap|iPhone 4 GSM]]
| 15 July 2010
| 19 August 2010
| {{no|Closed}}
|-
| 4.0.2
| [[N82ap|iPhone 3G]], [[N72ap|iPod touch 2G]]
| 11 August 2010
| 18 September 2010
| {{no|Closed}}
|-
| 4.0.2
| [[N88ap|iPhone 3GS]], [[N90ap|iPhone 4 GSM]], [[N18ap|iPod touch 3G]]
| 11 August 2010
| 9 September 2010
| {{no|Closed}}
|-
| 4.1
| [[N82ap|iPhone 3G]], [[N88ap|iPhone 3GS]], [[N72ap|iPod touch 2G]], [[N18ap|iPod touch 3G]]
| 8 September 2010
| -
| {{yes|Open}}
|-
| 4.1
| [[N90ap|iPhone 4 GSM]], [[N81ap|iPod touch 4G]]
| 8 September 2010
| 2 December 2010 (?)
| {{no|Closed}}
|-
| {{nowrap|4.1 (4.0)}}
| rowspan="2" | [[K66ap|Apple TV 2G]]
| 29 September 2010
| 2 December 2010 (?)
| {{no|Closed}}
|-
| {{nowrap|4.2 (4.1)}}
| 22 November 2010
| 14 December 2010
| {{no|Closed}}
|-
| 4.2.1
| [[K48ap|iPad]], [[N88ap|iPhone 3GS]], [[N90ap|iPhone 4 GSM]], [[N18ap|iPod touch 3G]], [[N81ap|iPod touch 4G]]
| 22 November 2010
| 11 March 2011
| {{no|Closed}}
|-
| 4.2.1
| [[N82ap|iPhone 3G]], [[N72ap|iPod touch 2G]]
| 22 November 2010
| -
| {{yes|Open}}
|-
| {{nowrap|4.2.1 (4.1.1)}}
| [[K66ap|Apple TV 2G]]
| 14 December 2010
| 28 May 2011 (?)
| {{no|Closed}}
|-
| 4.2.5
| rowspan="6" | [[N92ap|iPhone 4 CDMA]]
| 11 January 2011
| closed before product release
| {{no|Closed}}
|-
| 4.2.6
| 1 February 2011
| 19 April 2011 (?)
| {{no|Closed}}
|-
| 4.2.7
| 14 April 2011
| 6 May 2011
| {{no|Closed}}
|-
| 4.2.8
| 4 May 2011
| 18 July 2011
| {{no|Closed}}
|-
| 4.2.9
| 15 July 2011
| 27 July 2011
| {{no|Closed}}
|-
| 4.2.10
| 25 July 2011
| 18 October 2011
| {{no|Closed}}
|-
| 4.3
| [[K48ap|iPad]], [[iPad 2]], [[N88ap|iPhone 3GS]], [[N90ap|iPhone 4 GSM]], [[N18ap|iPod touch 3G]], [[N81ap|iPod touch 4G]]
| 9 March 2011
| 27 March 2011 (?)
| {{no|Closed}}
|-
| {{nowrap|4.3 (4.2)}}
| rowspan="4" | [[K66ap|Apple TV 2G]]
| 9 March 2011
| 22 March 2011 (?)
| {{no|Closed}}
|-
| {{nowrap|4.3 (4.2.1)}}
| 22 March 2011
| 28 May 2011 (?)
| {{no|Closed}}
|-
| {{nowrap|4.3 (4.2.2)}}
| 11 May 2011
| 18 October 2011 (?)
| {{no|Closed}}
|-
| {{nowrap|4.3 (4.3)}}
| 1 August 2011
| ?
| {{no|Closed}}
|-
| 4.3.1
| rowspan="5" | [[K48ap|iPad]], [[iPad 2]], [[N88ap|iPhone 3GS]], [[N90ap|iPhone 4 GSM]], [[N18ap|iPod touch 3G]], [[N81ap|iPod touch 4G]]
| 25 March 2011
| 19 April 2011 (?)
| {{no|Closed}}
|-
| 4.3.2
| 14 April 2011
| 6 May 2011
| {{no|Closed}}
|-
| 4.3.3
| 4 May 2011
| 18 July 2011
| {{no|Closed}}
|-
| 4.3.4
| 15 July 2011
| 27 July 2011
| {{no|Closed}}
|-
| 4.3.5
| 25 July 2011
| 18 October 2011
| {{no|Closed}}
|-
| 4.4
| rowspan="5" | [[k66ap|Apple TV 2G]]
| 4 October 2011
| ?
| {{no|Closed}}
|-
| 4.4.1
| 17 October 2011
| ?
| {{no|Closed}}
|-
| 4.4.2
| 24 October 2011
| 11 January 2012(?)
| {{no|Closed}}
|-
| 4.4.3
| 17 November 2011
| 11 January 2012(?)
| {{no|Closed}}
|-
| 4.4.4
| 15 December 2011
| 8 March 2012
| {{no|Closed}}
|-
| 5.0
| [[K48ap|iPad]], [[iPad 2]], [[N88ap|iPhone 3GS]], [[iPhone 4]], [[N18ap|iPod touch 3G]], [[N81ap|iPod touch 4G]]
| 4 October 2011
| 10 November 2011(?)
| {{no|Closed}}
|-
| 5.0
| [[N94ap|iPhone 4S]]
| 14 October 2011
| 10 November 2011(?)
| {{no|Closed}}
|-
| 5.0
| [[k66ap|Apple TV 2G]], [[j33ap|Apple TV 3G]]
| 7 March 2012
| 14 May 2012
| {{no|Closed}}
|-
| 5.0.1
| [[K48ap|iPad]], [[iPad 2]], [[N88ap|iPhone 3GS]], [[iPhone 4]], [[N94ap|iPhone 4S]], [[N18ap|iPod touch 3G]], [[N81ap|iPod touch 4G]]
| 9 November 2011
| 8 March 2012
| {{no|Closed}}
|-
| 5.1
| [[K48ap|iPad]], [[iPad 2]], [[iPad 3]], [[N88ap|iPhone 3GS]], [[iPhone 4]], [[N94ap|iPhone 4S]], [[N18ap|iPod touch 3G]], [[N81ap|iPod touch 4G]]
| 7 March 2012
| 14 May 2012
| {{no|Closed}}
|-
| 5.1.1
| [[iPad 2]], [[iPad 3]], [[N88ap|iPhone 3GS]], [[iPhone 4]], [[N94ap|iPhone 4S]], [[N81ap|iPod touch 4G]]
| 7 May 2012
| 21 Sep 2012
| {{no|Closed}}
|-
| 5.1.1
| [[K48ap|iPad]], [[N18ap|iPod touch 3G]]
| 7 May 2012
| -
| {{yes|Open}}
|-
| 5.0.1
| [[k66ap|Apple TV 2G]], [[j33ap|Apple TV 3G]]
| 10 May 2012
| ?? June 2012
| {{no|Closed}}
|-
| 5.0.2
| [[k66ap|Apple TV 2G]], [[j33ap|Apple TV 3G]]
| 5 June 2012
| -
| {{yes|Open}}
|-
| 6.0
| [[iPad 2]], [[iPad 3]], [[N88ap|iPhone 3GS]], [[iPhone 4]], [[N94ap|iPhone 4S]], [[iPhone 5]], [[N81ap|iPod touch 4G]], [[N78ap|iPod touch 5G]]
| 19 September 2012
| 1 November 2012
| {{no|Closed}}
|-
| 5.1
| [[k66ap|Apple TV 2G]], [[j33ap|Apple TV 3G]]
| 24 September 2012
| -
| {{yes|Open}}
|-
| 6.0
| [[p101ap|iPad 4 (Wi-Fi model)]], [[p105ap|iPad mini 1G (Wi-Fi model)]]
| 30 October 2012
| 1 November 2012
| {{no|Closed}}
|-
| 6.0.1
| [[iPad 2]], [[iPad 3]], [[p101ap|iPad 4 (Wi-Fi model)]], [[N88ap|iPhone 3GS]], [[iPhone 4]], [[N94ap|iPhone 4S]], [[N81ap|iPod touch 4G]]
| 1 November 2012
| 28 January 2013
| {{no|Closed}}
|-
| 6.0.1
| [[N78ap|iPod touch 5G]]
| 1 November 2012
| 29 January 2013
| {{no|Closed}}
|-
| 6.0.1
| [[p102ap|iPad 4 (GSM model)]], [[p103ap|iPad 4 (Global model)]]
| 9 November 2012
| 28 January 2013
| {{no|Closed}}
|-
| 6.0.1
| [[iPad mini 1G]], [[iPhone 5]]
| 1 November 2012
| 8 January 2013
| {{no|Closed}}
|-
| 5.1.1
| [[k66ap|Apple TV 2G]], [[j33ap|Apple TV 3G]]
| 26 November 2012
| -
| {{yes|Open}}
|-
| 6.0.2
| [[iPad mini 1G]], [[iPhone 5]]
| 18 December 2012
| 28 January 2013
| {{no|Closed}}
|-
| 6.1
| [[iPad 2]], [[iPad 3]], [[iPad 4]], [[P105ap|iPad mini 1G Wi-Fi]], [P106ap|[iPad mini 1G GSM]], [[N88ap|iPhone 3GS]], [[iPhone 4]], [[N94ap|iPhone 4S]], [[iPhone 5]], [[N78ap|iPod touch 5G]]
| 28 January 2013
| 19 February 2013
| {{no|Closed}}

|-
| 6.1
| [[P107ap|iPad mini 1G Global]], [[N81ap|iPod touch 4G]]
| 28 January 2013
| -
| {{yes|Open}}
|-
| 5.2
| [[k66ap|Apple TV 2G]], [[j33ap|Apple TV 3G]], [[j33iap|Apple TV 3G Rev A]]
| 28 January 2013
| -
| {{yes|Open}}
|-
| 6.1.1
| [[N94ap|iPhone 4S]]
| 11 February 2013
| 19 February 2013
| {{no|Closed}}
|-
| 6.1.2
| [[iPad 2]], [[iPad 3]], [[iPad 4]], [[iPad mini 1G]], [[N88ap|iPhone 3GS]], [[iPhone 4]], [[N94ap|iPhone 4S]], [[iPhone 5]], [[N81ap|iPod touch 4G]], [[N78ap|iPod touch 5G]]
| 19 February 2013
| -
| {{yes|Open}}
|}

== Protocol ==
To request a SHSH blob from Apple, a simple [[wikipedia:Hypertext Transfer Protocol|HTTP]] request can be made. For a full description, please see the separate article [[SHSH Protocol]] and [[Baseband SHSH Protocol]].

== Links and Tools ==
* [[Redsn0w]]
* [[TinyUmbrella]] (Java needed)
* [http://www.saurik.com/id/12 Detailed background info from Saurik]

== See Also ==
* [[APTicket]]
[[Category:Firmware Tags]]

SHSH

2013-02-20T03:01:54Z

CompilingEntropy: added the iphone and ipod touch 1g signing window for 3.1.3

0x80 byte RSA signature of a firmware image.

This often also refers to the backup file with the signature ("SHSH blobs"). This signature is needed to restore a specific iOS version; it is generated by Apple based on hardware keys of the device and the hash of the firmware. Apple only issues signatures for the currently-available iOS version, which disallows installing older iOS versions. But if you have saved signatures for an older iOS version, you can use a [[wikipedia:replay attack|replay attack]] to restore that version. Therefore it is recommended to save the signature for your device as long as Apple issues it.

With the tools mentioned below it is possible to backup the signature. It is not necessary that the device is jailbroken to do the backup. Usually the SHSH signature file is stored on [[Cydia Server|Saurik's server]]. If it is stored there, then you can see in the top of [[Cydia Application|Cydia]] (on jailbroken devices) for which version a backup exists.

Users often misunderstand this system and think that the SHSH firmware version they back up depends on the firmware version they have installed on their device. This is the case for [[iFaith]], but not for TinyUmbrella. iFaith dumps the SHSHs from your device's storage (whatever's installed on your device, e.g. 4.3.3), while TinyUmbrella gets SHSHs from Apple's servers (whatever firmwares Apple is currently signing).

==Using SHSH==
Older devices allow installation of any correctly signed firmware, so no backup of the certificate is necessary. Devices that need Apple signatures are: [[N88ap|iPhone 3GS]], [[N90ap|iPhone 4]], [[N18ap|iPod touch 3G]], [[K48ap|iPad]], [[iPad 2]], [[n81ap|iPod touch 4G]], [[K66ap|Apple TV 2G]] and all newer devices. The [[N88ap|iPhone 3G]] and [[N72ap|iPod touch 2G]] bootroms do not require these SHSHs; however, newer versions of iOS require them (unless the chain of trust is broken and custom firmwares are installed). To restore to arbitrary versions of iOS 4.0, the SHSH is also needed for the [[N72ap|iPod touch 2G]] and [[N82ap|iPhone 3G]]. not only does [[DFU Mode]] require the [[iBSS]]/[[iBEC]] files to be signed with an SHSH that includes the device's [[ECID]], but the normal boot-chain requires the [[LLB]] to be fully signed with an [[ECID]]+SHSH, so a downgrade [[IPSW File Format|IPSW]] is not possible without a bootrom exploit of normal boot-chain (e.g. [[0x24000 Segment Overflow]]). See also the [http://blog.iphone-dev.org/post/833937433 Dev Team Blog post] about this.

To restore to iOS 3.x or 4.x, change your hosts file to map any request to an Apple server to point to [[Saurik]]'s server instead, if your device's signatures are hosted there. If you have the signature file on your computer, run [[TinyUmbrella]]'s TSS Server on your local machine.

Since the [[limera1n exploit]] is fixed in the [[bootrom]] since version [[Bootrom 838.3]] and because iOS since 5.0 includes a [[nonce]] in their SHSH hashes, downgrading newer devices ([[N94ap|iPhone 4S]], [[iPad 2]], [[iPad 3]], [[J33ap|Apple TV 3G]]) to earlier 5.x firmwares is not as simple. To restore to iOS 5.x on older devices, stitch iOS 5.x blobs into custom firmware (using redsn0w for example) and restore with that firmware. To restore to iOS 5.x on newer devices, use redsn0w's restore method. See the [http://www.jailbreakqa.com/questions/32462/frequently-asked-questions#94647 JailbreakQA guide to restoring to iOS 5.x using SHSH blobs] (for all devices that can run iOS 5.x except Apple TV 3G).

==Timeline==
{| class="wikitable" style="text-align: center; width: auto; table-layout: fixed; border-collapse: collapse;" border="1"
|-
! width="50" | iOS
! width="480" | for Device(s)
! width="130" | From
! width="130" | Until
! width="130" | Status
|-
| 3.0
| rowspan="3" | [[N88ap|iPhone 3GS]]
| 19 June 2009
| 9 September 2009
| {{no|Closed}}
|-
| 3.0.1
| 31 July 2009
| 9 September 2009
| {{no|Closed}}
|-
| 3.1
| 9 September 2009
| 8 October 2009
| {{no|Closed}}
|-
| 3.1.1
| [[N72ap|iPod touch 2G]]
| 9 September 2009
| 21 June 2010
| {{no|Closed}}
|-
| 3.1.1
| [[N18ap|iPod touch 3G]]
| 9 September 2009
| 8 October 2009
| {{no|Closed}}
|-
| 3.1.2
| [[N72ap|iPod touch 2G]]
| 8 October 2009
| 21 June 2010
| {{no|Closed}}
|-
| 3.1.2
| [[N88ap|iPhone 3GS]], [[N18ap|iPod touch 3G]]
| 8 October 2009
| 2 February 2010
| {{no|Closed}}
|-
| 3.1.3
| [[M68ap|iPhone]], [[N45ap|iPod touch 1G]]
| 2 February 2010
| 21 June 2010
| {{yes|Open}}
|-
| 3.1.3
| [[N72ap|iPod touch 2G]]
| 2 February 2010
| 21 June 2010
| {{no|Closed}}
|-
| 3.1.3
| [[N88ap|iPhone 3GS]], [[N18ap|iPod touch 3G]]
| 2 February 2010
| 21 June 2010
| {{no|Closed}}
|-
| 3.2
| rowspan="3" | [[K48ap|iPad]]
| 3 April 2010
| 15 July 2010
| {{no|Closed}}
|-
| 3.2.1
| 15 July 2010
| 19 August 2010
| {{no|Closed}}
|-
| 3.2.2
| 11 August 2010
| 2 December 2010 (?)
| {{no|Closed}}
|-
| 4.0
| [[N72ap|iPod touch 2G]]
| 21 June 2010
| 9 September 2010
| {{no|Closed}}
|-
| 4.0
| [[N18ap|iPod touch 3G]]
| 21 June 2010
| 19 August 2010
| {{no|Closed}}
|-
| 4.0
| [[N82ap|iPhone 3G]], [[N88ap|iPhone 3GS]]
| 21 June 2010
| 15 July 2010
| {{no|Closed}}
|-
| 4.0
| [[N90ap|iPhone 4 GSM]]
| 24 June 2010
| 15 July 2010
| {{no|Closed}}
|-
| 4.0.1
| [[N82ap|iPhone 3G]]
| 15 July 2010
| 9 September 2010
| {{no|Closed}}
|-
| 4.0.1
| [[N88ap|iPhone 3GS]], [[N90ap|iPhone 4 GSM]]
| 15 July 2010
| 19 August 2010
| {{no|Closed}}
|-
| 4.0.2
| [[N82ap|iPhone 3G]], [[N72ap|iPod touch 2G]]
| 11 August 2010
| 18 September 2010
| {{no|Closed}}
|-
| 4.0.2
| [[N88ap|iPhone 3GS]], [[N90ap|iPhone 4 GSM]], [[N18ap|iPod touch 3G]]
| 11 August 2010
| 9 September 2010
| {{no|Closed}}
|-
| 4.1
| [[N82ap|iPhone 3G]], [[N88ap|iPhone 3GS]], [[N72ap|iPod touch 2G]], [[N18ap|iPod touch 3G]]
| 8 September 2010
| -
| {{yes|Open}}
|-
| 4.1
| [[N90ap|iPhone 4 GSM]], [[N81ap|iPod touch 4G]]
| 8 September 2010
| 2 December 2010 (?)
| {{no|Closed}}
|-
| {{nowrap|4.1 (4.0)}}
| rowspan="2" | [[K66ap|Apple TV 2G]]
| 29 September 2010
| 2 December 2010 (?)
| {{no|Closed}}
|-
| {{nowrap|4.2 (4.1)}}
| 22 November 2010
| 14 December 2010
| {{no|Closed}}
|-
| 4.2.1
| [[K48ap|iPad]], [[N88ap|iPhone 3GS]], [[N90ap|iPhone 4 GSM]], [[N18ap|iPod touch 3G]], [[N81ap|iPod touch 4G]]
| 22 November 2010
| 11 March 2011
| {{no|Closed}}
|-
| 4.2.1
| [[N82ap|iPhone 3G]], [[N72ap|iPod touch 2G]]
| 22 November 2010
| -
| {{yes|Open}}
|-
| {{nowrap|4.2.1 (4.1.1)}}
| [[K66ap|Apple TV 2G]]
| 14 December 2010
| 28 May 2011 (?)
| {{no|Closed}}
|-
| 4.2.5
| rowspan="6" | [[N92ap|iPhone 4 CDMA]]
| 11 January 2011
| closed before product release
| {{no|Closed}}
|-
| 4.2.6
| 1 February 2011
| 19 April 2011 (?)
| {{no|Closed}}
|-
| 4.2.7
| 14 April 2011
| 6 May 2011
| {{no|Closed}}
|-
| 4.2.8
| 4 May 2011
| 18 July 2011
| {{no|Closed}}
|-
| 4.2.9
| 15 July 2011
| 27 July 2011
| {{no|Closed}}
|-
| 4.2.10
| 25 July 2011
| 18 October 2011
| {{no|Closed}}
|-
| 4.3
| [[K48ap|iPad]], [[iPad 2]], [[N88ap|iPhone 3GS]], [[N90ap|iPhone 4 GSM]], [[N18ap|iPod touch 3G]], [[N81ap|iPod touch 4G]]
| 9 March 2011
| 27 March 2011 (?)
| {{no|Closed}}
|-
| {{nowrap|4.3 (4.2)}}
| rowspan="4" | [[K66ap|Apple TV 2G]]
| 9 March 2011
| 22 March 2011 (?)
| {{no|Closed}}
|-
| {{nowrap|4.3 (4.2.1)}}
| 22 March 2011
| 28 May 2011 (?)
| {{no|Closed}}
|-
| {{nowrap|4.3 (4.2.2)}}
| 11 May 2011
| 18 October 2011 (?)
| {{no|Closed}}
|-
| {{nowrap|4.3 (4.3)}}
| 1 August 2011
| ?
| {{no|Closed}}
|-
| 4.3.1
| rowspan="5" | [[K48ap|iPad]], [[iPad 2]], [[N88ap|iPhone 3GS]], [[N90ap|iPhone 4 GSM]], [[N18ap|iPod touch 3G]], [[N81ap|iPod touch 4G]]
| 25 March 2011
| 19 April 2011 (?)
| {{no|Closed}}
|-
| 4.3.2
| 14 April 2011
| 6 May 2011
| {{no|Closed}}
|-
| 4.3.3
| 4 May 2011
| 18 July 2011
| {{no|Closed}}
|-
| 4.3.4
| 15 July 2011
| 27 July 2011
| {{no|Closed}}
|-
| 4.3.5
| 25 July 2011
| 18 October 2011
| {{no|Closed}}
|-
| 4.4
| rowspan="5" | [[k66ap|Apple TV 2G]]
| 4 October 2011
| ?
| {{no|Closed}}
|-
| 4.4.1
| 17 October 2011
| ?
| {{no|Closed}}
|-
| 4.4.2
| 24 October 2011
| 11 January 2012(?)
| {{no|Closed}}
|-
| 4.4.3
| 17 November 2011
| 11 January 2012(?)
| {{no|Closed}}
|-
| 4.4.4
| 15 December 2011
| 8 March 2012
| {{no|Closed}}
|-
| 5.0
| [[K48ap|iPad]], [[iPad 2]], [[N88ap|iPhone 3GS]], [[iPhone 4]], [[N18ap|iPod touch 3G]], [[N81ap|iPod touch 4G]]
| 4 October 2011
| 10 November 2011(?)
| {{no|Closed}}
|-
| 5.0
| [[N94ap|iPhone 4S]]
| 14 October 2011
| 10 November 2011(?)
| {{no|Closed}}
|-
| 5.0
| [[k66ap|Apple TV 2G]], [[j33ap|Apple TV 3G]]
| 7 March 2012
| 14 May 2012
| {{no|Closed}}
|-
| 5.0.1
| [[K48ap|iPad]], [[iPad 2]], [[N88ap|iPhone 3GS]], [[iPhone 4]], [[N94ap|iPhone 4S]], [[N18ap|iPod touch 3G]], [[N81ap|iPod touch 4G]]
| 9 November 2011
| 8 March 2012
| {{no|Closed}}
|-
| 5.1
| [[K48ap|iPad]], [[iPad 2]], [[iPad 3]], [[N88ap|iPhone 3GS]], [[iPhone 4]], [[N94ap|iPhone 4S]], [[N18ap|iPod touch 3G]], [[N81ap|iPod touch 4G]]
| 7 March 2012
| 14 May 2012
| {{no|Closed}}
|-
| 5.1.1
| [[iPad 2]], [[iPad 3]], [[N88ap|iPhone 3GS]], [[iPhone 4]], [[N94ap|iPhone 4S]], [[N81ap|iPod touch 4G]]
| 7 May 2012
| 21 Sep 2012
| {{no|Closed}}
|-
| 5.1.1
| [[K48ap|iPad]], [[N18ap|iPod touch 3G]]
| 7 May 2012
| -
| {{yes|Open}}
|-
| 5.0.1
| [[k66ap|Apple TV 2G]], [[j33ap|Apple TV 3G]]
| 10 May 2012
| ?? June 2012
| {{no|Closed}}
|-
| 5.0.2
| [[k66ap|Apple TV 2G]], [[j33ap|Apple TV 3G]]
| 5 June 2012
| -
| {{yes|Open}}
|-
| 6.0
| [[iPad 2]], [[iPad 3]], [[N88ap|iPhone 3GS]], [[iPhone 4]], [[N94ap|iPhone 4S]], [[iPhone 5]], [[N81ap|iPod touch 4G]], [[N78ap|iPod touch 5G]]
| 19 September 2012
| 1 November 2012
| {{no|Closed}}
|-
| 5.1
| [[k66ap|Apple TV 2G]], [[j33ap|Apple TV 3G]]
| 24 September 2012
| -
| {{yes|Open}}
|-
| 6.0
| [[p101ap|iPad 4 (Wi-Fi model)]], [[p105ap|iPad mini 1G (Wi-Fi model)]]
| 30 October 2012
| 1 November 2012
| {{no|Closed}}
|-
| 6.0.1
| [[iPad 2]], [[iPad 3]], [[p101ap|iPad 4 (Wi-Fi model)]], [[N88ap|iPhone 3GS]], [[iPhone 4]], [[N94ap|iPhone 4S]], [[N81ap|iPod touch 4G]]
| 1 November 2012
| 28 January 2013
| {{no|Closed}}
|-
| 6.0.1
| [[N78ap|iPod touch 5G]]
| 1 November 2012
| 29 January 2013
| {{no|Closed}}
|-
| 6.0.1
| [[p102ap|iPad 4 (GSM model)]], [[p103ap|iPad 4 (Global model)]]
| 9 November 2012
| 28 January 2013
| {{no|Closed}}
|-
| 6.0.1
| [[iPad mini 1G]], [[iPhone 5]]
| 1 November 2012
| 8 January 2013
| {{no|Closed}}
|-
| 5.1.1
| [[k66ap|Apple TV 2G]], [[j33ap|Apple TV 3G]]
| 26 November 2012
| -
| {{yes|Open}}
|-
| 6.0.2
| [[iPad mini 1G]], [[iPhone 5]]
| 18 December 2012
| 28 January 2013
| {{no|Closed}}
|-
| 6.1
| [[iPad 2]], [[iPad 3]], [[iPad 4]], [[P105ap|iPad mini 1G Wi-Fi]], [P106ap|[iPad mini 1G GSM]], [[N88ap|iPhone 3GS]], [[iPhone 4]], [[N94ap|iPhone 4S]], [[iPhone 5]], [[N78ap|iPod touch 5G]]
| 28 January 2013
| 19 February 2013
| {{no|Closed}}

|-
| 6.1
| [[P107ap|iPad mini 1G Global]], [[N81ap|iPod touch 4G]]
| 28 January 2013
| -
| {{yes|Open}}
|-
| 5.2
| [[k66ap|Apple TV 2G]], [[j33ap|Apple TV 3G]], [[j33iap|Apple TV 3G Rev A]]
| 28 January 2013
| -
| {{yes|Open}}
|-
| 6.1.1
| [[N94ap|iPhone 4S]]
| 11 February 2013
| 19 February 2013
| {{no|Closed}}
|-
| 6.1.2
| [[iPad 2]], [[iPad 3]], [[iPad 4]], [[iPad mini 1G]], [[N88ap|iPhone 3GS]], [[iPhone 4]], [[N94ap|iPhone 4S]], [[iPhone 5]], [[N81ap|iPod touch 4G]], [[N78ap|iPod touch 5G]]
| 19 February 2013
| -
| {{yes|Open}}
|}

== Protocol ==
To request a SHSH blob from Apple, a simple [[wikipedia:Hypertext Transfer Protocol|HTTP]] request can be made. For a full description, please see the separate article [[SHSH Protocol]] and [[Baseband SHSH Protocol]].

== Links and Tools ==
* [[Redsn0w]]
* [[TinyUmbrella]] (Java needed)
* [http://www.saurik.com/id/12 Detailed background info from Saurik]

== See Also ==
* [[APTicket]]
[[Category:Firmware Tags]]

Bypassing Jailbreak Detection

2013-02-13T01:04:25Z

CompilingEntropy: /* How To Reverse An App */

Recently, a sizable handful of applications in Apple's own [[App Store]] have been implementing procedures to check the authenticity of the device on which the app itself is running, forbidding or inhibiting usage of certain features or even the app altogether. Obvious reasons are about the innate security risks of [[jailbreak|jailbreaking]] your device (e.g. banking companies don't want the blame for some rogue keylogger disguised as a tweak snagging your account info). However, most of the time, it seems as if companies are worried about the possibility of tweaks bypassing certain restrictions implemented into their apps. Video streaming apps are notorious for this; the companies don't want users bypassing restrictions on when and where you can stream their content, so instead of doing the responsible thing and obfuscating their restriction attempts, they instead block all jailbroken devices, regardless of malicious intent or lack thereof.

== How To Detect Jailbroken Devices ==
''For the sake of convenience within this article, a "rogue app" will refer to any app available in the App Store that actively implements jailbreak detection measures.''

For the most part, jailbreak detection procedures are a lot less sophisticated that one might imagine. While there are countless ways apps can implement checks for jailbroken devices, they typically boil down to the following:

* '''Existence of directories''' - Rogue apps love to check your file system for paths like [[Cydia.app|/Applications/Cydia.app/]] and [[/private/var/stash]], amongst a handful of others. Most often, these are checked using the -(BOOL)fileExistsAtPath:(NSString*)path method in NSFileManager, but more sneaky apps like to use lower-level C functions like fopen(), stat(), or access().
* '''Directory permissions''' - Similar to checking existence of directories, but checks the Unix file permissions of specific files and directories on the system using NSFileManager methods as well as C functions like statfs(). Far more directories have write access on a jailbroken device than on one still in jail.
* '''Process forking''' - sandboxd does not deny App Store applications the ability to use fork(), popen(), or any other C functions to create child processes on devices out of jail. sandboxd explicitly denies process forking on devices in jail. By checking the returned pid on fork(), a rogue app can tell if it has successfully forked or not, at which point it can determine a device's jailbreak status.
* '''SSH loopback connections''' - Only a very small number of applications implement this (as it is not nearly as effective as the others). Due to the very large portion of jailbroken devices that have [[OpenSSH]] installed, some rogue apps will attempt to make a connection to 127.0.0.1 on port 22. If the connection succeeds, it means OpenSSH is installed and running on the device, which obviously indicates that it is jailbroken.
* '''system()''' - Calling the system() function with no arguments on a device in jail will return 0; doing the same on a jailbroken device will return 1. Not sure why, but such is the case.
* '''dyld functions''' - By far the hardest to get around. Calling functions like _dyld_image_count() and _dyld_get_image_name() to see which dylibs are currently loaded. Very difficult to patch, as patches are themselves part of dylibs.

== How To Reverse Engineer An App ==
# In order to dump or disassemble an app from the App Store, it must first be decrypted (often referred to as "[[Copy Protection Overview|cracking]]"), even if it is a free application.
# Using [[class-dump-z]] on the application's decrypted binary will dump all of the header files. Occasionally, these contain "giveaway" method names, like "deviceIsJailbroken" or "checkDeviceSecurity." Typically, hooking these methods is enough to disable the jailbreak detection measures, but it nearly guarantees that the patch will not work on other apps.
# Tracing methods named like that in IDA using the Objective-C parsing feature can help pinpoint exactly which method is being used to detect the jailbreak.
# If the class-dumped headers don't give away anything, searching the binary for strings like "jail," "cydia," "apt," etc. often lead to the breaking point.

== xCon ==
See [[xCon]] on its separate page.

XCon

2013-02-13T00:55:13Z

CompilingEntropy: /* App Patching Status */

{{lowercase}}
xCon is a collaborative project by [http://twitter.com/unimp0rtanttech n00neimp0rtant] and [http://twitter.com/olunatiko Lunatik] that aims to be an all-in-one solution for hooking every known method and function responsible for informing an application of a jailbroken device. At first, the project aimed to patch applications on a per-app basis, but now it uses lower-level hooks to cover any apps that attempt to use the same procedure, even patching apps not explicitly reversed by the developers. Originally an open-source project, it remains closed-source now to discourage App Store developers from working around xCon's hooks.

xCon is available free of charge in Cydia. No configuration is needed; just install and go.

For general infos, see [[Bypassing Jailbreak Detection]].

== App Patching Status ==
''You can find an app's current release version in its iTunes listing page, linked below in the app names. If an app's current release version is newer than the "Last Confirmed Working Version," please help by testing it out yourself with the latest release of xCon and updating the table as necessary.''

'''ATTENTION: If you are going to edit this chart, do NOT just put a question mark for or leave blank the Bundle Identifier. You can find the bundle ID of any app by looking in its Info.plist file. This saves the devs both time and effort, and it also helps the devs filter patches on a per-app basis, making your phone or iPad run faster and more stable.'''

{| class="wikitable" style="text-align:center; width:100%;"
|-
! App Name
! Bundle Identifier
! Patched?
! Last Confirmed Working Version
! Notes
|-
| [http://itunes.apple.com/us/app/airwatch-mdm-agent/id338761996?mt=8 Airwatch MDM]
| com.air-watch.agent
| {{partial|BETA}}
| {{partial|3.0.8}}
| Currently in beta. Details at https://github.com/n00neimp0rtant/xCon-Issues/issues/30
|-
| [http://itunes.apple.com/us/app/amazon-instant-video/id545519333?mt=8 Amazon Instant Video]
| ?
| {{Yes}}
| 1.0
|
|-
| [https://itunes.apple.com/us/app/ankimobile-flashcards/id373493387?mt=8 Ankimobile]
| net.ichi2.anki
| {{no}}
| N/A
| detected on Ankimobile 2.0.1 on iphone 5 iOS 6.1
|-
| [http://itunes.apple.com/gb/app/barclays-mobile-banking/id536248734?mt=8 Barclays Mobile Banking]
| uk.co.barclays.bmbappstore
| {{no}}
| N/A
| App currently up to v1.0. Detects jailbreak with an RG22 error. Filed [https://github.com/n00neimp0rtant/xCon-Issues/issues/61 Issue 61] on the github page
|-
| [http://itunes.apple.com/gb/app/barclays-pingit/id496552142?mt=8 Barclays PingIt]
| uk.co.barclays.PingIt
| {{no}}
| 1.0.2
| 1.0.2 no-longer supported by Barclays
|-
| [http://itunes.apple.com/us/app/optimum/id387231038?mt=8 Cablevision Optimum]
| com.cablevision.rDVR
| {{yes}}
| 2.1.2
|
|-
| [http://itunes.apple.com/us/app/optimum-for-ipad/id424612367?mt=8 Cablevision Optimum (iPad)]
| com.cablevision.iOTV
| {{yes}}
| 2.1.1
|
|-
| [http://itunes.apple.com/gb/app/capital-one-uk/id481679012?mt=8 Capital One UK]
| com.ukcapitalone.capitalone
| {{yes}}
| 5.1
|
|-
| [http://itunes.apple.com/my/app/cimb-clicks/id328803038?mt=8 CIMB Clicks]
| com.cimb.CIMB
| {{no}}
| 04.00.00
| Filed [https://github.com/n00neimp0rtant/xCon-Issues/issues/67 Issue 67] on the github page
|-
| [http://itunes.apple.com/au/app/commbank-kaching/id475728226?mt=8 Commbank Kaching]
| au.com.commbank.kaching
| {{yes}}
| 1.1.0
|
|-
| [http://itunes.apple.com/us/app/cox-tv-connect-for-ipad/id474096909?mt=8 Cox TV Connect]
| com.cox.ios.ipad.tvconnect
| {{yes}}
| 1.0.1
|
|-
| [http://itunes.apple.com/us/app/directv-app-for-ipad/id421547368?mt=8 DirecTV for iPad]
| com.directv.mobile.ipad.navigator.production
| {{yes}}
| 1.3.4-1.5.0
|
|-
| [https://itunes.apple.com/app/id307386350 DIRECTV]
| com.directv.DTViPhone
| {{no}}
|
|
|-
| [http://itunes.apple.com/us/app/directv-nomad/id448679509?mt=8 DirecTV Nomad]
| com.directv.mobile.iphone.nomad.production
| {{yes}}
| 1.8.1
| 2.0.0 & 2.0.1 in beta - https://github.com/n00neimp0rtant/xCon-Issues/issues/34
|-
| [http://itunes.apple.com/za/app/dstv-mobile-decoder/id403946447?mt=8 DStv Mobile Decoder]
| com.multichoice.DStvMobileDVBH
| {{yes}}
| 1.01.07
|
|-
| [http://itunes.apple.com/us/app/entrust-identityguard-mobile/id384717687?mt=8 Entrust IdentityGuard Mobile]
| com.entrust.IdentityGuardSoftToken
| {{no}}
| N/A
| Filed [https://github.com/n00neimp0rtant/xCon-Issues/issues/43 request 43] on the github page
|-
| [http://itunes.apple.com/us/app/movies-by-flixster-rotten/id284235722?mt=8 Flixster/Movies/Ultraviolet]
| com.jeffreygrossman.moviesapp
| {{yes}}
| 5.22
|
|-
| [http://itunes.apple.com/us/app/golden-screen-cinemas/id413024972?mt=8 Golden Screen Cinemas]
| com.sinodynamic.gsc
| {{yes}}
| 1.4
|
|-
| [http://itunes.apple.com/us/app/good-for-enterprise/id333202351?l=es&mt=8 Good For Enterprise]
| com.good.gmmiphone
| {{yes}}
| 1.9.10
| App works but admin console still reports jailbreak
|-

| [http://itunes.apple.com/us/app/ibooks/id364709193?mt=8 iBooks]
| com.apple.iBooks
| {{no}}
| ?
| Patch(es) available in Cydia
|-
| [http://itunes.apple.com/us/app/kbseutabaengking/id373742138?mt=8 KB star]
| com.kbstar.kbbank
| {{yes}}
| 1.14.1
|
|-
| [http://itunes.apple.com/us/app/kb-starplus/id381065734?mt=8 KB starPlus]
| com.kbstar.starplus
| {{yes}}
| 1.2.0
|
|-
| [http://itunes.apple.com/gb/app/lovefilm-player-for-ipad/id454468674?mt=8 LOVEFiLM Player for iPad]
| com.lovefilm.watchnow.ipad
| {{No}}
| 1.0
| Working for ver 1.0 but not newer 1.0.1, it knows the iPad is jailbroken
|-
| [http://itunes.apple.com/us/app/maxis-movies/id369867024?mt=8 Maxis Movies]
| com.maxis.moviebooking
| {{yes}}
| 1.1.6
|
|-
| [http://itunes.apple.com/us/app/maxis-movies-for-ipad/id418096484?mt=8 Maxis Movies (iPad)]
| com.maxis.moviebookingipad
| {{yes}}
| 1.1.2
|
|-
| [http://itunes.apple.com/us/app/repudo/id416444260?mt=8 Repudo]
| com.repudo.iphone
| {{no}}
| 3.2.2
|
|-
| [http://itunes.apple.com/us/app/redbox-instant-by-verizon/id561226994?mt=8 Redbox Instant by Verizon]
| com.ctlabs.redboxinstant
| {{yes}}
| 1.0.2
| Requires invitation code
|-
| [http://itunes.apple.com/us/app/mcafee-enterprise-mobility/id322111072?mt=8 McAfee EMM]
| com.trustdigital.iTDClient
| {{yes}}
| 4.7.1
|
|-
| [http://itunes.apple.com/us/app/mobileiron-myphone-work-client/id320659794?mt=8 MobileIron MyPhone@Work]
| com.mobileiron.phoneatwork
| {{yes}}
| 4.5.12
|
|-
| [http://itunes.apple.com/us/app/skype/id304878510?mt=8 Skype]
| com.skype.skype
| {{yes}}
| 3.7
|
|-
| [http://itunes.apple.com/gb/app/sky-go/id446086440?mt=8 Sky Go]
| com.bskyb.skygo
| {{no}}
| 2.2
| After update app is now saying "Streaming is unavailable on jailbroken devices"
|-
| [http://itunes.apple.com/us/app/square/id335393788?mt=8 Square]
| com.squareup.square
| {{yes}}
| 2.2.5
|
|-
| [http://itunes.apple.com/ca/app/telus-optik-tv-hd/id467260646?mt=8 Telus Optik TV]
| com.telus.nscreen
| {{yes}}
| 1.1.2
|
|-
| [http://itunes.apple.com/us/app/tv-live-de-la-orange/id390896393?mt=8 TV live de la Orange]
| com.orange.TVOrange
| {{yes}}
| 1.0
|
|-
| [http://itunes.apple.com/us/app/twc-tv/id420455839?mt=8 TWC TV]
| com.timewarnercable.simulcast
| {{yes}}
| 2.6.1
|
|-
| [http://itunes.apple.com/us/app/verizon-media-manager/id460536890?mt=8 Verizon Media Manager]
| com.verizon.ams.flexview
| {{yes}}
| 2.0.29.26
|
|-
| [http://itunes.apple.com/no/app/voddler/id409806444?mt=8 Voddler]
| com.voddler.VoddlerHD
| {{yes}}
| 1.2.1
|
|-
| [http://itunes.apple.com/us/app/whatsapp-messenger/id310633997?mt=9 WhatsApp]
| net.whatsapp.WhatsApp
| {{yes}}
| 2.6.10
| [http://pic.twitter.com/xEaFciOP Support button blocked]
|-
| [http://itunes.apple.com/us/app/bamboo-wallet/id492663955?mt=8 Bamboo Wallet]
| ?
| {{no}}
| 7.5.4
| does not work
|}

== References ==
* [https://github.com/n00neimp0rtant/xCon-Issues Issue list]