The iPhone Wiki - User contributions [en]

Home Diagnostics

2019-06-21T18:18:44Z

ForestCorgi: Update latest known version (as per https://twitter.com/1nsane_dev/status/1142061454062960642)

{{internal software}}
{{Infobox software
| name = Home Diagnostics
| title = Home Diagnostics
| logo = [[File:Hdpkg.png|150px]]
| screenshot = [[File:Homediags.png|300px]]
| caption = HomeDiagnostics.pkg(14B70)
| collapsible =
| author = [[wikipedia:Apple_Inc.|Apple Inc.]]
| developer = [[wikipedia:Apple_Inc.|Apple Inc.]]
| released =
| discontinued =
| latest release version = 15A287b<br /><small>(latest ''known'' version)</small>
| latest release date =
| latest preview version =
| latest preview date =
| programming language =
| operating system = [[wikipedia:macOS|macOS]]
| platform =
| size =
| language = [[wikipedia:English language|English]]
| status =
| genre = Package
| license = [[wikipedia:Proprietary software|Closed source]]
| website =
}}
{{float toc|left}}
'''Home Diagnostics''' is an package which contains a few apps that are used by [[wikipedia:Foxconn|Foxconn]] or [[wikipedia:Apple_Inc.|Apple]]. It usually contains the following apps: [[PurpleRestore]], [[PurpleSNIFF]], [[PurpleFAT]], [[SkankPhone]], [[ScreenShotr]], [[DCSD]], [[PurpleBuildSanitizer]], iOS Menu, iPhone Menu, PurpleConsole, PowerWarriorX, PurplePod, SkankTunes, CarDisplaySim, a crash dumper, which automatically launches when an iDevice is connected and dumps the logs to the computer, and an additional panel for Xcode Organizer. It also installs a handful of useful command line utilities to /usr/local/bin. These applications aren't installed in /Applications like normal; They are instead installed to /AppleInternal/Applications.

{{stub|software}}

UID key

2018-08-26T22:30:44Z

ForestCorgi: Minor edits to wording and correction of the wrong version of "its"

The '''UID key''' (device's unique ID key) is an AES 256-bit hardware key, unique to each iPhone. It is fused into the application processor during manufacturing. It was previously used to encrypt things in the [[NOR]]. In later iOS versions, it is used to encrypt the entire file system, so that the flash chips cannot moved to another device and read out there again. On the [[S5L8960]] and later, the [[Secure Enclave|SEP]] has its own UID in its own AES engine, and that UID is the one used to encrypt the filesystem on iOS. On the [[S8000]] and [[S8003]] and later, the chip securely generates the UID for the device which is then used to encrypt the whole filesystem.

Apple says about this key:<br/>
''"The UID is unique to each device and is not recorded by Apple or any of its suppliers."''<br/>
and also<br/>
''"The UID is not related to any other identifier on the device."''

See also: [[GID Key]].

===References===
*[https://www.apple.com/br/privacy/docs/iOS_Security_Guide_Oct_2014.pdf iOS Security document by Apple]

[[Category:Decryption]]

NonUI builds

2018-05-09T03:34:05Z

ForestCorgi: Add debug identifiers to several basebands

{{internal software}}
{{see also|Beta Firmware|Internal OTA Updates}}
<div class="toclimit-3">{{float toc|left}}</div>
This is a documented list of known '''factory firmwares''', used by Apple workers in California to do engineering tests on prototype devices and also by factory workers on production ones during manufacturing. Factory firmwares are based on production iOS ones, but adapted for internal engineering tests, development and debugging. {{clear}}
[[File:newsblogo.png|thumb|125px|right|"Skankwerk" logo on 7.x and up]]
[[File:oldswblogo.png|thumb|125px|left|"Skankwerk" logo on 6.x and below]]
[[File:newswblogo.jpg|thumb|125px|right|Prototype showing Skankwerk logo during boot]]
[[File:oldswblogodevice.jpg|thumb|125px|left|Prototype showing Skankwerk logo during boot]]
They are also known as "NonUI (No User Interface)" builds, probably because most applications are command line ones. The SpringBoard replacement, named SwitchBoard, allow launching a GUI of some of those applications. Unlike production iOS firmwares, factory ones have the following differences:
* DEVELOPMENT Fused bootloaders in \Firmware\dfu\ and \Firmware\all_flash\all_flash.[board codename].factoryfa\.
* DEVELOPMENT Fused kernel cache with more symbols, and with individual kexts in /System/Library/Extensions
* Skankwerk (gear) logo image file in \Firmware\all_flash\all_flash.[board codename].factoryfa\.
* /AppleInternal folder, which the hierarchy inside get priority over hierarchy in /.
* No SpringBoard, requires the use of daemons to launch [[SwitchBoard.app]] as a multi-app launcher instead.
* /usr and subfolders contain many UNIX command line utilities.
* SSH daemon is pre-installed - as dropbear
* Boot loader passes arguments to kernel (unlike RELEASE boot loaders as of iOS 5.0) which makes it easy to disable AMFI
* It has some Private Frameworks in /System/Library/PrivateFrameworks for internal GUI apps and command line utilities.
* Most internal applications require the use of SkankKit to produce special layers such as text on the framebuffer.
Unlike regular iOS Firmwares, factory ones are distributed in both IPSWs and "restore bundles". Those are unzipped IPSW files which can be restored on devices using internal restore software such as [[PurpleRestore]]. Release and factory firmwares "restore bundles" have the same packaging structure (bootloaders, kernel, restore ramdisk, update ramdisk and root filesystem).
{{clear}}
= Some interesting facts about factory firmwares =
* '''Design:''' Apple seems to use the same GUI design from the production firmware to the factory one.
Production iOS 1.x to 6.x skeuomorphism design is also present on 1.x to 6.x factory firmwares, but seems really more excessive than production ones. For example, the "skankwerk" boot logo represents a real gear and many GUI icons are realistic or simply photos of real life things (especially in [[Operator]]). For newer versions, production iOS 7.x to 9.x flat design is mostly used in 7.x to 9.x factory firmwares. For example, the new "skankwerk" boot logo is a flat, simple white gear. Some newer internal applications like Earthbound also use a "flat" design.
* '''Other:''' The "skank" word is used to name multiple elements of factory firmwares. For example, there is "skankphone", "skankbattery" (the green battery shown in SwitchBoard), "skankwerk" logo, "skankkit" framework, "purpleskank" (used by BurnIn) and most likely others. The "skank" word seems to be a reference to "Skunkworks" projects, which are secrecy projects that are usually innovative. Read more about "Skunkworks" on [https://en.wikipedia.org/wiki/Skunkworks_project Wikipedia].

== [[M68AP|iPhone]] ==
{| class="wikitable"
|-
! Version
! Build
! Codename
! Baseband
! Comments
|-
| rowspan="2" | 1.0
| [[Alpine 1A420|1A420]]
| rowspan="3" | Alpine
| 03.06.01_G<sup>[http://web.archive.org/web/20110730023951/http://imageshack.us/photo/my-images/399/iphone2go0.jpg/]</sup>
| Originally available [http://forums.macrumors.com/showpost.php?p=7249071&postcount=85 here], but was soon taken down.
|-
| [[Alpine 4A57|4A57]]
| 04.02.13_G
| -
|-
| rowspan="1" | 1.1.2
| [[Alpine 3B48|3B48]]
| 04.02.13_G
| -
|-
| rowspan="2" | 1.1.3
| [[Alpine 4A102a|4A102a]]
| Alpine
| 04.04.05_G
| -
|-
|}

== [[N82AP|iPhone 3G]] ==
{| class="wikitable"
|-
! Version
! Build
! Codename
! Baseband
! Comments
|-
| rowspan="2" | 4.0
| [[ApexNanshan 8A2130h|8A2130h]]
| ApexNanshan
| ?
| -
|-
| [[ApexNanshan 8A2180g|8A2180g]]
| ApexNanshan
| 05.12.01
| -
|-
|}

== [[N88AP|iPhone 3GS]] ==
{| class="wikitable"
|-
! Version
! Build
! Codename
! Baseband
! Comments
|-
| rowspan="2" | 3.1b
| [[Sierra 7C108b|7C108b]]
| Sierra?
| ?
| -
|-
| [[Northstar 7C144|7C144]]
| Northstar?
| ?
| -
|-
| rowspan="2" | 4.0
| [[ApexNanshan 8A2130h|8A2130h]]
| ApexNanshan
| ?
| -
|-
| [[ApexNanshan 8A2180g|8A2180g]]
| ApexNanshan
| 05.12.01
| -
|-
| rowspan="3" | 5.1
| [[HoodooYabuli 9B3145a|9B3145a]]
| HoodooYabuli
| ?
| -
|-
| [[HoodooYabuli 9B3176b|9B3176b]]
| HoodooYabuli
| ?
| -
|-
| [[HoodooYabuli 9B3176n|9B3176n]]
| HoodooYabuli
| 05.16.05
| -
|-
| 6.0
| [[Sundance 10A316|10A316]]
| Sundance
| 05.16.06
| -
|}

== [[iPhone 4]] ==
{| class="wikitable"
|-
! Version
! Build
! Codename
! Baseband
! Comments
|-
| rowspan="4" | 4.0
| [[Apex 8A133|8A133]]
| Apex?
| 01.32.01
| -
|-
| [[Apex 8A2062a|8A2062a]]
| Apex?
| ?
| -
|-
| [[ApexNanshan 8A2130h|8A2130h]]
| ApexNanshan
| ?
| -
|-
| [[ApexNanshan 8A2180g|8A2180g]]
| ApexNanshan
| 01.42.01
| -
|-
| rowspan="3" | 5.1
| [[HoodooYabuli 9B3145a|9B3145a]]
| HoodooYabuli
| ?
| -
|-
| [[HoodooYabuli 9B3176b|9B3176b]]
| HoodooYabuli
| ?
| -
|-
| [[HoodooYabuli 9B3176n|9B3176n]]
| HoodooYabuli
| 04.12.01
| -
|-
| 6.0
| [[Sundance 10A316|10A316]]
| Sundance
| 04.12.02
| -
|-
|}

== [[N94AP|iPhone 4S]] ==
{| class="wikitable"
|-
! Version
! Build
! Codename
! Baseband
! Comments
|-
| rowspan="3" | 5.1
| [[HoodooYabuli 9B3145a|9B3145a]]
| HoodooYabuli
| ?
| -
|-
| [[HoodooYabuli 9B3176b|9B3176b]]
| HoodooYabuli
| ?
| -
|-
| [[HoodooYabuli 9B3176n|9B3176n]]
| HoodooYabuli
| 1.0.10
| -
|-
| 6.0
| [[SundanceNanshan 10A23941a|10A23941a]]
| SundanceNanshan
| 2.0.0.2
| -
|}

== [[iPhone 5]] ==
{| class="wikitable"
|-
! Version
! Build
! Codename
! Baseband
! Comments
|-
| rowspan="3" | 6.0
| [[Sundance 10A23110z|10A23110z]]
| Sundance?
| ?
| -
|-
| [[Sundance 10A23941s|10A23941s]]
| Sundance?
| ?
| -
|-
| [[Sundance 10A316|10A316]]
| Sundance
| 1.7.00
| -
|-
|}
== [[iPhone 5c]] ==
{| class="wikitable"
|-
! Version
! Build
! Codename
! Baseband
! Comments
|-
| 7.1
| [[Sochi 11D31620l|11D31620l]]
| Sochi?
| ?
| -
|}

== [[iPhone 5s]] ==
{| class="wikitable"
|-
! Version
! Build
! Codename
! Baseband
! Comments
|-
| rowspan="3" | 7.0
| [[InnsbruckNanshan 11A24580o|11A24580o]]
| InnsbruckNanshan
| 1.00.05
| -
|-
| [[InnsbruckNanshan 11A24581c|11A24581c]]
| InnsbruckNanshan
| ?
| -
|-
| [[Innsbruck 11A93840f|11A93840f]]
| Innsbruck?
| ?
| Originally found on a [https://forums.macrumors.com/threads/unusual-iphone-possible-engineering-sample-os.1885755/ Macrumors] post.
|-
|}

== [[N61AP|iPhone 6]] ==
{| class="wikitable"
|-
! Version
! Build
! Codename
! Baseband
! Comments
|-
| rowspan="5" | 8.0
| [[Okemo 12A22121a|12A22121a]]
| Okemo?
| ?
| -
|-
| [[Okemo 12A93311h|12A93311h]]
| Okemo?
| 1.00.01
| -
|-
| [[OkemoAni 12A93650o|12A93650o]]
| OkemoAni
| 1.00.05
| This build is pretty obscure, but it is in the wild.
|-
| [[OkemoAni 12A93651a|12A93651a]]
| OkemoAni
| 1.00.05
| -
|-
| [[OkemoAni 12A93651b|12A93651b]]
| OkemoAni
| 1.00.05
| -
|-
|}

== [[iPhone 6s]] ==
{| class="wikitable"
|-
! Version
! Build
! Codename
! Baseband
! Comments
|-
| rowspan="4" | 9.0
| [[Monarch 13A22120w|13A22120w]]
| Monarch?
| ?
| -
|-
| [[MonarchAni 13A93051l|13A93051l]]
| MonarchAni
| 0.37.08_DEBUG
| -
|-
| [[Monarch 13A93420d|13A93420d]]
| Monarch?
| ?
| -
|-
| [[Monarch 13A93420m|13A93420m]]
| Monarch?
| 1.00.05
| -
|-
|}

== [[D10AP|iPhone 7]] ==
{| class="wikitable"
|-
! Version
! Build
! Codename
! Baseband
! Comments
|-
| rowspan="5" | 10.0
| [[Whitetail 14A22580n|14A22580n]]
| Whitetail?
| ?
| -
|-
| [[Whitetail 14A22881a|14A22881a]]
| Whitetail?
| ?
| -
|-
| [[Whitetail 14A92340t|14A92340t]]
| Whitetail?
| ?
| -
|-
| [[WhitetailAni 14A93012r|14A93012r]]
| WhitetailAni
| ?
| -
|-
| [[WhitetailAni 14A93013a|14A93013a]]
| WhitetailAni
| ?
| -
|-
|}

== [[D20AP|iPhone 8]] ==
{| class="wikitable"
|-
! Version
! Build
! Codename
! Baseband
! Comments
|-
| 11.0
| [[TigrisAni 15A93261h|15A93261h]]
| TigrisAni
| 00.34.09-DEBUG
| -
|}

== [[D21AP|iPhone X]] ==
{| class="wikitable"
|-
| Version
| Build
| Codename
| Baseband
| Comments
|-
| 11.0
| [[TigrisAni 15A783601y|15A783601y]]
| TigrisAni?
| ?
| -
|}

== [[K48AP|iPad]] ==
{| class="wikitable"
|-
! Version
! Build
! Codename
! Baseband
! Comments
|-
| rowspan="2" | 3.2
| [[Wildcat 7B3341e|7B3341e]]
| Wildcat?
| ?
| -
|-
| [[Wildcat 7B5286a|7B5286a]]
| Wildcat?
| ?
| Found by SonnyDickson, documented on [https://9to5mac.com/2017/05/15/ipad-1-prototype/ 9to5mac]
|-
|}

== [[K93AP|iPad 2]] ==
{| class="wikitable"
|-
! Version
! Build
! Codename
! Baseband
! Comments
|-
| rowspan="2" | 4.3
| [[Durango 8F3178a|8F3178a]]
| Durango?
| ?
| -
|-
| [[Durango 8F3191d|8F3191d]]
| Durango?
| ?
| -
|-
|}

== [[P106AP|iPad mini]] ==
{| class="wikitable"
|-
! Version
! Build
! Codename
! Baseband
! Comments
|-
| rowspan="3" | 6.0
| [[SundanceTaosTianshan 10A63970m|10A63970m]]
| SundanceTaosTianshan
| ?
| -
|-
| [[SundanceTaosTianshan 10A63970v|10A63970v]]
| SundanceTaosTianshan
| ?
| -
|-
| [[SundanceTaosTianshan 10A63971b|10A63971b]]
| SundanceTaosTianshan
| ?
| -
|-
|}

== [[J86AP|iPad mini 2]] ==
{| class="wikitable"
|-
! Version
! Build
! Codename
! Baseband
! Comments
|-
| 7.0.3
| [[InnsbruckTaos 11B64940j|11B64940j]]
| InnsbruckTaos?
| ?
| -
|}

== [[J96AP|iPad mini 4]] ==
{| class="wikitable"
|-
! Version
! Build
! Codename
! Baseband
! Comments
|-
| 8.4
| [[Donner 12H60160o|12H60160o]]
| Donner?
| ?
| -
|-
| 9.0
| [[Monarch 13A62950o|13A62950o]]
| Monarch?
| ?
| -
|-
|}

== [[J71AP|iPad Air]] ==
{| class="wikitable"
|-
! Version
! Build
! Codename
! Baseband
! Comments
|-
| 7.0.1
| [[Innsbruck 11B34640l|11B34640l]]
| Innsbruck?
| ?
| -
|}

== [[N18AP|iPod touch (3rd generation)]] ==
{| class="wikitable"
|-
! Version
! Build
! Codename
! Baseband
! Comments
|-
| rowspan="3" | 3.1
| [[Inferno 7C1023e|7C1023e]]
| Inferno?
| ?
| -
|-
| [[Inferno 7C1095a|7C1095a]]
| Inferno?
| ?
| -
|-
| [[Northstar 7C144|7C144]]
| Northstar?
| ?
| -
|-
|}

== [[N81AP|iPod touch (4th generation)]] ==
{| class="wikitable"
|-
! Version
! Build
! Codename
! Baseband
! Comments
|-
| rowspan="3" | 5.1
| [[HoodooYabuli 9B3145a|9B3145a]]
| HoodooYabuli
| ?
| -
|-
| [[HoodooYabuli 9B3176b|9B3176b]]
| HoodooYabuli
| ?
| -
|-
| [[HoodooYabuli 9B3176n|9B3176n]]
| HoodooYabuli
| ?
| -
|}

[[Category:Firmware]]

TigrisAni 15A93261h

2018-05-09T00:22:03Z

ForestCorgi: List details of mach.kasan kernels

{{internal software|firmware}}
== Background ==
This firmware is an internal NonUI version of iOS 11.0. It has been seen on various iPhone 8 prototype units. Similarly to other recent builds, this one has a rather large filesize - a dump of its filesystem is around 9.1 GB.

Interestingly, this build contains kernels for Apple A7 to A11 processors, including differfent processor varieties. This has previously not been the case since iOS version 7.0. It also appears to support an unreleased processor type known as t8020. Based on previous NonUI firmwares having support for as of then unreleased processors, it's safe to assume that this processor is most likely the Apple A12 or A11X.
[[File:Iph8_15A93261h.jpg|thumb|right|iPhone 8 prototype running 15A93261h]]

== Notable Changes ==

This build is known to have various differences compared to previous builds, which will be listed here.

* '''[[T500AP]] and [[T501AP]]''' - Wi-Fi drivers for these unknown board identifiers can be found in <code>/AppleInternal/Diags/WifiFirmware/</code> alongside the iPhone 8 ([[D20AP]]) and iPhone 8 Plus ([[D21AP]]).

* '''mach.kasan''' - apart from the usual mach.development.{Processor Name / Identifier} kernels found within NonUI builds, this build contains kernels with the [https://www.kernel.org/doc/html/v4.12/dev-tools/kasan.html Kernel Address SANitizer], a tool used to detect bad memory accesses, enabled.

* '''Tailspin / Ariadne''' - A readme file located within /AppleInternal/tailspin references a previously unheard of application known as Ariadne, as well as "tailspin" files. The readme states that "tailspin holds onto 20-30 seconds of historical spindump and Ariadne data, from before the sysdiagnose invocation." The Ariadne application appears to be used for the visualization of these tailspin files.

* '''Firmware references''' - In the same readme - two iOS firmwares are referenced - Tigris 15A221 (an apparent version of iOS 11.0) and [[Lobo 17A202]]. Judging by the build number of the latter firmware compared to the standard build number scheme - it seems that this is a future version of iOS that has yet to be released, being newer than iOS 11.

* '''Test scripts''' - Located in AppleInternal/CoreOS/AppleSEP/unit_tests/hilo, these test scripts seem to communicate with the [[Secure Enclave]]. The scripts are written to only work on [[D22AP]], the [[iPhone X]], meaning that they may be used to test various sensors in the [[TrueDepth]] sensor housing. They contain multiple references to a display module with the codename '''[[Hilo]]'''.

== Applications ==
This firmware contains many applications launchable from [[SwitchBoard.app]], however roughly half of them are hidden by default:
* [[AltoMobile]]
* [[CoexBlender]] (hidden)
* [[ExtendedOQC]]
* [[FactoryStencil]]
* [[GrapeCal]]
* [[GrapeCal_Lite]]
* [[LCDMura]] (hidden)
* [[LcdUTest]] (hidden)
* [[MesaCal]]
* [[Ness]] (hidden)
* [[NonUIQRCode]] (hidden)
* [[NonUIConsoleViewer]]
* [[Operator]] (hidden)
* [[OrbCal]]
* [[Pippi]] (hidden)
* [[Reliability]]
* [[Reliability]] (again) (hidden)
* [[Sequencer]]
* [[Spelunx]]
* [[ThermalDOE]] (hidden)
* [[USBHost]]
* [[WiPASmini]]

TigrisAni 15A93261h

2018-05-09T00:18:49Z

ForestCorgi: Edit punctuation

{{internal software|firmware}}
== Background ==
This firmware is an internal NonUI version of iOS 11.0. It has been seen on various iPhone 8 prototype units. Similarly to other recent builds, this one has a rather large filesize - a dump of its filesystem is around 9.1 GB.

Interestingly, this build contains kernels for Apple A7 to A11 processors, including differfent processor varieties. This has previously not been the case since iOS version 7.0. It also appears to support an unreleased processor type known as t8020. Based on previous NonUI firmwares having support for as of then unreleased processors, it's safe to assume that this processor is most likely the Apple A12 or A11X.
[[File:Iph8_15A93261h.jpg|thumb|right|iPhone 8 prototype running 15A93261h]]

== Notable Changes ==

This build is known to have various differences compared to previous builds, which will be listed here.

* '''[[T500AP]] and [[T501AP]]''' - Wi-Fi drivers for these unknown board identifiers can be found in <code>/AppleInternal/Diags/WifiFirmware/</code> alongside the iPhone 8 ([[D20AP]]) and iPhone 8 Plus ([[D21AP]]).

* '''mach.kasan''' - apart from the usual mach.development.{Processor Name / Identifier} files found within NonUI builds - this build contains a new type of file - known as mach.kasan. It is currently unknown what the purpose of this new filetype is, since it has not been encountered in previous firmwares.

* '''Tailspin / Ariadne''' - A readme file located within /AppleInternal/tailspin references a previously unheard of application known as Ariadne, as well as "tailspin" files. The readme states that "tailspin holds onto 20-30 seconds of historical spindump and Ariadne data, from before the sysdiagnose invocation." The Ariadne application appears to be used for the visualization of these tailspin files.

* '''Firmware references''' - In the same readme - two iOS firmwares are referenced - Tigris 15A221 (an apparent version of iOS 11.0) and [[Lobo 17A202]]. Judging by the build number of the latter firmware compared to the standard build number scheme - it seems that this is a future version of iOS that has yet to be released, being newer than iOS 11.

* '''Test scripts''' - Located in AppleInternal/CoreOS/AppleSEP/unit_tests/hilo, these test scripts seem to communicate with the [[Secure Enclave]]. The scripts are written to only work on [[D22AP]], the [[iPhone X]], meaning that they may be used to test various sensors in the [[TrueDepth]] sensor housing. They contain multiple references to a display module with the codename '''[[Hilo]]'''.

== Applications ==
This firmware contains many applications launchable from [[SwitchBoard.app]], however roughly half of them are hidden by default:
* [[AltoMobile]]
* [[CoexBlender]] (hidden)
* [[ExtendedOQC]]
* [[FactoryStencil]]
* [[GrapeCal]]
* [[GrapeCal_Lite]]
* [[LCDMura]] (hidden)
* [[LcdUTest]] (hidden)
* [[MesaCal]]
* [[Ness]] (hidden)
* [[NonUIQRCode]] (hidden)
* [[NonUIConsoleViewer]]
* [[Operator]] (hidden)
* [[OrbCal]]
* [[Pippi]] (hidden)
* [[Reliability]]
* [[Reliability]] (again) (hidden)
* [[Sequencer]]
* [[Spelunx]]
* [[ThermalDOE]] (hidden)
* [[USBHost]]
* [[WiPASmini]]

Beta OTA Updates

2018-05-09T00:07:34Z

ForestCorgi: Change HTTP links to HTTPS

{{about|beta OTA updates|public OTA update|OTA Updates}}
In addition to seeding beta versions of iOS as [[Beta Firmware|beta firmwares]], Apple also distributes them as OTA updates. Installation of these required either a beta firmware to have been installed, or a configuration profile to change the location where the OS checks for updates. To use this software legally, you must enroll in either the [https://developer.apple.com/programs/enroll/ Apple Developer Program] or the [https://beta.apple.com/sp/betaprogram/ Apple Beta Software Program]. The download links provided on the following pages link directly to Apple's servers, but these do not provide a means of installation.

=== Apple TV ===
{{:Beta OTA Updates/Apple TV}}

=== Apple Watch ===
{{:Beta OTA Updates/Apple Watch}}

=== HomePod ===
{{:Beta OTA Updates/HomePod}}

=== iPad ===
{{:Beta OTA Updates/iPad}}

=== iPad mini ===
{{:Beta OTA Updates/iPad mini}}

=== iPhone ===
{{:Beta OTA Updates/iPhone}}

=== iPod touch ===
{{:Beta OTA Updates/iPod touch}}

[[Category:Beta OTA Updates]]

=== Software Update XMLs ===
==== Developer Beta Software Update XMLs ====
* iOS
** [https://mesu.apple.com/assets/iOSDeveloperSeed/com_apple_MobileAsset_SoftwareUpdate/com_apple_MobileAsset_SoftwareUpdate.xml iOS 10 Developer Beta] ([https://mesu.apple.com/assets/iOSDeveloperSeed/com_apple_MobileAsset_SoftwareUpdateDocumentation/com_apple_MobileAsset_SoftwareUpdateDocumentation.xml documentation])
** [https://mesu.apple.com/assets/iOS11DeveloperSeed/com_apple_MobileAsset_SoftwareUpdate/com_apple_MobileAsset_SoftwareUpdate.xml iOS 11 Developer Beta] ([https://mesu.apple.com/assets/iOS11DeveloperSeed/com_apple_MobileAsset_SoftwareUpdateDocumentation/com_apple_MobileAsset_SoftwareUpdateDocumentation.xml documentation])
* tvOS
** [https://mesu.apple.com/assets/tvOSDeveloperSeed/com_apple_MobileAsset_SoftwareUpdate/com_apple_MobileAsset_SoftwareUpdate.xml tvOS 10 Developer Beta]
** [https://mesu.apple.com/assets/tvOS11DeveloperSeed/com_apple_MobileAsset_SoftwareUpdate/com_apple_MobileAsset_SoftwareUpdate.xml tvOS 11 Developer Beta]
* watchOS
** [https://mesu.apple.com/assets/watchOSDeveloperSeed/com_apple_MobileAsset_SoftwareUpdate/com_apple_MobileAsset_SoftwareUpdate.xml watchOS ≤3 Developer Beta]
** [https://mesu.apple.com/assets/watchOS4DeveloperSeed/com_apple_MobileAsset_SoftwareUpdate/com_apple_MobileAsset_SoftwareUpdate.xml watchOS 4 Developer Beta] ([https://mesu.apple.com/assets/com_apple_MobileAsset_WatchSoftwareUpdateDocumentation/com_apple_MobileAsset_WatchSoftwareUpdateDocumentation.xml documentation])

==== Public Beta Software Update XMLs ====
* iOS
** [https://mesu.apple.com/assets/seed-R40.2112/com_apple_MobileAsset_SoftwareUpdate/com_apple_MobileAsset_SoftwareUpdate.xml iOS 8 Public Beta] ([https://mesu.apple.com/assets/seed-R40.2112/com_apple_MobileAsset_SoftwareUpdateDocumentation/com_apple_MobileAsset_SoftwareUpdateDocumentation.xml documentation])
** [https://mesu.apple.com/assets/seed-R40.Subdivide/com_apple_MobileAsset_SoftwareUpdate/com_apple_MobileAsset_SoftwareUpdate.xml iOS 9 Public Beta] ([https://mesu.apple.com/assets/seed-R40.Subdivide/com_apple_MobileAsset_SoftwareUpdateDocumentation/com_apple_MobileAsset_SoftwareUpdateDocumentation.xml documentation])
** [https://mesu.apple.com/assets/iOSPublicSeed/com_apple_MobileAsset_SoftwareUpdate/com_apple_MobileAsset_SoftwareUpdate.xml iOS 10 Public Beta] ([https://mesu.apple.com/assets/iOSPublicSeed/com_apple_MobileAsset_SoftwareUpdateDocumentation/com_apple_MobileAsset_SoftwareUpdateDocumentation.xml documentation])
** [https://mesu.apple.com/assets/iOS11PublicSeed/com_apple_MobileAsset_SoftwareUpdate/com_apple_MobileAsset_SoftwareUpdate.xml iOS 11 Public Beta] ([https://mesu.apple.com/assets/iOS11PublicSeed/com_apple_MobileAsset_SoftwareUpdateDocumentation/com_apple_MobileAsset_SoftwareUpdateDocumentation.xml documentation])
* tvOS
** [https://mesu.apple.com/assets/tvOS11PublicSeed/com_apple_MobileAsset_SoftwareUpdate/com_apple_MobileAsset_SoftwareUpdate.xml 11.x]
* watchOS
** [https://mesu.apple.com/assets/R30.11TT05-subdivisions/com_apple_MobileAsset_SoftwareUpdate/com_apple_MobileAsset_SoftwareUpdate.xml watchOS 2.0 Public Beta]

NonUI builds

2018-05-09T00:04:11Z

ForestCorgi: Found baseband version for TigrisAni 15A93261h

{{internal software}}
{{see also|Beta Firmware|Internal OTA Updates}}
<div class="toclimit-3">{{float toc|left}}</div>
This is a documented list of known '''factory firmwares''', used by Apple workers in California to do engineering tests on prototype devices and also by factory workers on production ones during manufacturing. Factory firmwares are based on production iOS ones, but adapted for internal engineering tests, development and debugging. {{clear}}
[[File:newsblogo.png|thumb|125px|right|"Skankwerk" logo on 7.x and up]]
[[File:oldswblogo.png|thumb|125px|left|"Skankwerk" logo on 6.x and below]]
[[File:newswblogo.jpg|thumb|125px|right|Prototype showing Skankwerk logo during boot]]
[[File:oldswblogodevice.jpg|thumb|125px|left|Prototype showing Skankwerk logo during boot]]
They are also known as "NonUI (No User Interface)" builds, probably because most applications are command line ones. The SpringBoard replacement, named SwitchBoard, allow launching a GUI of some of those applications. Unlike production iOS firmwares, factory ones have the following differences:
* DEVELOPMENT Fused bootloaders in \Firmware\dfu\ and \Firmware\all_flash\all_flash.[board codename].factoryfa\.
* DEVELOPMENT Fused kernel cache with more symbols, and with individual kexts in /System/Library/Extensions
* Skankwerk (gear) logo image file in \Firmware\all_flash\all_flash.[board codename].factoryfa\.
* /AppleInternal folder, which the hierarchy inside get priority over hierarchy in /.
* No SpringBoard, requires the use of daemons to launch [[SwitchBoard.app]] as a multi-app launcher instead.
* /usr and subfolders contain many UNIX command line utilities.
* SSH daemon is pre-installed - as dropbear
* Boot loader passes arguments to kernel (unlike RELEASE boot loaders as of iOS 5.0) which makes it easy to disable AMFI
* It has some Private Frameworks in /System/Library/PrivateFrameworks for internal GUI apps and command line utilities.
* Most internal applications require the use of SkankKit to produce special layers such as text on the framebuffer.
Unlike regular iOS Firmwares, factory ones are distributed in both IPSWs and "restore bundles". Those are unzipped IPSW files which can be restored on devices using internal restore software such as [[PurpleRestore]]. Release and factory firmwares "restore bundles" have the same packaging structure (bootloaders, kernel, restore ramdisk, update ramdisk and root filesystem).
{{clear}}
= Some interesting facts about factory firmwares =
* '''Design:''' Apple seems to use the same GUI design from the production firmware to the factory one.
Production iOS 1.x to 6.x skeuomorphism design is also present on 1.x to 6.x factory firmwares, but seems really more excessive than production ones. For example, the "skankwerk" boot logo represents a real gear and many GUI icons are realistic or simply photos of real life things (especially in [[Operator]]). For newer versions, production iOS 7.x to 9.x flat design is mostly used in 7.x to 9.x factory firmwares. For example, the new "skankwerk" boot logo is a flat, simple white gear. Some newer internal applications like Earthbound also use a "flat" design.
* '''Other:''' The "skank" word is used to name multiple elements of factory firmwares. For example, there is "skankphone", "skankbattery" (the green battery shown in SwitchBoard), "skankwerk" logo, "skankkit" framework, "purpleskank" (used by BurnIn) and most likely others. The "skank" word seems to be a reference to "Skunkworks" projects, which are secrecy projects that are usually innovative. Read more about "Skunkworks" on [https://en.wikipedia.org/wiki/Skunkworks_project Wikipedia].

== [[M68AP|iPhone]] ==
{| class="wikitable"
|-
! Version
! Build
! Codename
! Baseband
! Comments
|-
| rowspan="2" | 1.0
| [[Alpine 1A420|1A420]]
| rowspan="3" | Alpine
| 03.06.01_G<sup>[http://web.archive.org/web/20110730023951/http://imageshack.us/photo/my-images/399/iphone2go0.jpg/]</sup>
| Originally available [http://forums.macrumors.com/showpost.php?p=7249071&postcount=85 here], but was soon taken down.
|-
| [[Alpine 4A57|4A57]]
| 04.02.13_G
| -
|-
| rowspan="1" | 1.1.2
| [[Alpine 3B48|3B48]]
| 04.02.13_G
| -
|-
| rowspan="2" | 1.1.3
| [[Alpine 4A102a|4A102a]]
| Alpine
| 04.04.05_G
| -
|-
|}

== [[N82AP|iPhone 3G]] ==
{| class="wikitable"
|-
! Version
! Build
! Codename
! Baseband
! Comments
|-
| rowspan="2" | 4.0
| [[ApexNanshan 8A2130h|8A2130h]]
| ApexNanshan
| ?
| -
|-
| [[ApexNanshan 8A2180g|8A2180g]]
| ApexNanshan
| 05.12.01
| -
|-
|}

== [[N88AP|iPhone 3GS]] ==
{| class="wikitable"
|-
! Version
! Build
! Codename
! Baseband
! Comments
|-
| rowspan="2" | 3.1b
| [[Sierra 7C108b|7C108b]]
| Sierra?
| ?
| -
|-
| [[Northstar 7C144|7C144]]
| Northstar?
| ?
| -
|-
| rowspan="2" | 4.0
| [[ApexNanshan 8A2130h|8A2130h]]
| ApexNanshan
| ?
| -
|-
| [[ApexNanshan 8A2180g|8A2180g]]
| ApexNanshan
| 05.12.01
| -
|-
| rowspan="3" | 5.1
| [[HoodooYabuli 9B3145a|9B3145a]]
| HoodooYabuli
| ?
| -
|-
| [[HoodooYabuli 9B3176b|9B3176b]]
| HoodooYabuli
| ?
| -
|-
| [[HoodooYabuli 9B3176n|9B3176n]]
| HoodooYabuli
| 05.16.05
| -
|-
| 6.0
| [[Sundance 10A316|10A316]]
| Sundance
| 05.16.06
| -
|}

== [[iPhone 4]] ==
{| class="wikitable"
|-
! Version
! Build
! Codename
! Baseband
! Comments
|-
| rowspan="4" | 4.0
| [[Apex 8A133|8A133]]
| Apex?
| 01.32.01
| -
|-
| [[Apex 8A2062a|8A2062a]]
| Apex?
| ?
| -
|-
| [[ApexNanshan 8A2130h|8A2130h]]
| ApexNanshan
| ?
| -
|-
| [[ApexNanshan 8A2180g|8A2180g]]
| ApexNanshan
| 01.42.01
| -
|-
| rowspan="3" | 5.1
| [[HoodooYabuli 9B3145a|9B3145a]]
| HoodooYabuli
| ?
| -
|-
| [[HoodooYabuli 9B3176b|9B3176b]]
| HoodooYabuli
| ?
| -
|-
| [[HoodooYabuli 9B3176n|9B3176n]]
| HoodooYabuli
| 04.12.01
| -
|-
| 6.0
| [[Sundance 10A316|10A316]]
| Sundance
| 04.12.02
| -
|-
|}

== [[N94AP|iPhone 4S]] ==
{| class="wikitable"
|-
! Version
! Build
! Codename
! Baseband
! Comments
|-
| rowspan="3" | 5.1
| [[HoodooYabuli 9B3145a|9B3145a]]
| HoodooYabuli
| ?
| -
|-
| [[HoodooYabuli 9B3176b|9B3176b]]
| HoodooYabuli
| ?
| -
|-
| [[HoodooYabuli 9B3176n|9B3176n]]
| HoodooYabuli
| 1.0.10
| -
|-
| 6.0
| [[SundanceNanshan 10A23941a|10A23941a]]
| SundanceNanshan
| 2.0.0.2
| -
|}

== [[iPhone 5]] ==
{| class="wikitable"
|-
! Version
! Build
! Codename
! Baseband
! Comments
|-
| rowspan="3" | 6.0
| [[Sundance 10A23110z|10A23110z]]
| Sundance?
| ?
| -
|-
| [[Sundance 10A23941s|10A23941s]]
| Sundance?
| ?
| -
|-
| [[Sundance 10A316|10A316]]
| Sundance
| 1.7.00
| -
|-
|}
== [[iPhone 5c]] ==
{| class="wikitable"
|-
! Version
! Build
! Codename
! Baseband
! Comments
|-
| 7.1
| [[Sochi 11D31620l|11D31620l]]
| Sochi?
| ?
| -
|}

== [[iPhone 5s]] ==
{| class="wikitable"
|-
! Version
! Build
! Codename
! Baseband
! Comments
|-
| rowspan="3" | 7.0
| [[InnsbruckNanshan 11A24580o|11A24580o]]
| InnsbruckNanshan
| 1.00.05
| -
|-
| [[InnsbruckNanshan 11A24581c|11A24581c]]
| InnsbruckNanshan
| ?
| -
|-
| [[Innsbruck 11A93840f|11A93840f]]
| Innsbruck?
| ?
| Originally found on a [https://forums.macrumors.com/threads/unusual-iphone-possible-engineering-sample-os.1885755/ Macrumors] post.
|-
|}

== [[N61AP|iPhone 6]] ==
{| class="wikitable"
|-
! Version
! Build
! Codename
! Baseband
! Comments
|-
| rowspan="5" | 8.0
| [[Okemo 12A22121a|12A22121a]]
| Okemo?
| ?
| -
|-
| [[Okemo 12A93311h|12A93311h]]
| Okemo?
| 1.00.01
| -
|-
| [[OkemoAni 12A93650o|12A93650o]]
| OkemoAni
| 1.00.05
| This build is pretty obscure, but it is in the wild.
|-
| [[OkemoAni 12A93651a|12A93651a]]
| OkemoAni
| 1.00.05
| -
|-
| [[OkemoAni 12A93651b|12A93651b]]
| OkemoAni
| 1.00.05
| -
|-
|}

== [[iPhone 6s]] ==
{| class="wikitable"
|-
! Version
! Build
! Codename
! Baseband
! Comments
|-
| rowspan="4" | 9.0
| [[Monarch 13A22120w|13A22120w]]
| Monarch?
| ?
| -
|-
| [[MonarchAni 13A93051l|13A93051l]]
| MonarchAni
| 0.37.08
| -
|-
| [[Monarch 13A93420d|13A93420d]]
| Monarch?
| ?
| -
|-
| [[Monarch 13A93420m|13A93420m]]
| Monarch?
| 1.00.05
| -
|-
|}

== [[D10AP|iPhone 7]] ==
{| class="wikitable"
|-
! Version
! Build
! Codename
! Baseband
! Comments
|-
| rowspan="5" | 10.0
| [[Whitetail 14A22580n|14A22580n]]
| Whitetail?
| ?
| -
|-
| [[Whitetail 14A22881a|14A22881a]]
| Whitetail?
| ?
| -
|-
| [[Whitetail 14A92340t|14A92340t]]
| Whitetail?
| ?
| -
|-
| [[WhitetailAni 14A93012r|14A93012r]]
| WhitetailAni
| ?
| -
|-
| [[WhitetailAni 14A93013a|14A93013a]]
| WhitetailAni
| ?
| -
|-
|}

== [[D20AP|iPhone 8]] ==
{| class="wikitable"
|-
! Version
! Build
! Codename
! Baseband
! Comments
|-
| 11.0
| [[TigrisAni 15A93261h|15A93261h]]
| TigrisAni
| 00.34.09
| -
|}

== [[D21AP|iPhone X]] ==
{| class="wikitable"
|-
| Version
| Build
| Codename
| Baseband
| Comments
|-
| 11.0
| [[TigrisAni 15A783601y|15A783601y]]
| TigrisAni?
| ?
| -
|}

== [[K48AP|iPad]] ==
{| class="wikitable"
|-
! Version
! Build
! Codename
! Baseband
! Comments
|-
| rowspan="2" | 3.2
| [[Wildcat 7B3341e|7B3341e]]
| Wildcat?
| ?
| -
|-
| [[Wildcat 7B5286a|7B5286a]]
| Wildcat?
| ?
| Found by SonnyDickson, documented on [https://9to5mac.com/2017/05/15/ipad-1-prototype/ 9to5mac]
|-
|}

== [[K93AP|iPad 2]] ==
{| class="wikitable"
|-
! Version
! Build
! Codename
! Baseband
! Comments
|-
| rowspan="2" | 4.3
| [[Durango 8F3178a|8F3178a]]
| Durango?
| ?
| -
|-
| [[Durango 8F3191d|8F3191d]]
| Durango?
| ?
| -
|-
|}

== [[P106AP|iPad mini]] ==
{| class="wikitable"
|-
! Version
! Build
! Codename
! Baseband
! Comments
|-
| rowspan="3" | 6.0
| [[SundanceTaosTianshan 10A63970m|10A63970m]]
| SundanceTaosTianshan
| ?
| -
|-
| [[SundanceTaosTianshan 10A63970v|10A63970v]]
| SundanceTaosTianshan
| ?
| -
|-
| [[SundanceTaosTianshan 10A63971b|10A63971b]]
| SundanceTaosTianshan
| ?
| -
|-
|}

== [[J86AP|iPad mini 2]] ==
{| class="wikitable"
|-
! Version
! Build
! Codename
! Baseband
! Comments
|-
| 7.0.3
| [[InnsbruckTaos 11B64940j|11B64940j]]
| InnsbruckTaos?
| ?
| -
|}

== [[J96AP|iPad mini 4]] ==
{| class="wikitable"
|-
! Version
! Build
! Codename
! Baseband
! Comments
|-
| 8.4
| [[Donner 12H60160o|12H60160o]]
| Donner?
| ?
| -
|-
| 9.0
| [[Monarch 13A62950o|13A62950o]]
| Monarch?
| ?
| -
|-
|}

== [[J71AP|iPad Air]] ==
{| class="wikitable"
|-
! Version
! Build
! Codename
! Baseband
! Comments
|-
| 7.0.1
| [[Innsbruck 11B34640l|11B34640l]]
| Innsbruck?
| ?
| -
|}

== [[N18AP|iPod touch (3rd generation)]] ==
{| class="wikitable"
|-
! Version
! Build
! Codename
! Baseband
! Comments
|-
| rowspan="3" | 3.1
| [[Inferno 7C1023e|7C1023e]]
| Inferno?
| ?
| -
|-
| [[Inferno 7C1095a|7C1095a]]
| Inferno?
| ?
| -
|-
| [[Northstar 7C144|7C144]]
| Northstar?
| ?
| -
|-
|}

== [[N81AP|iPod touch (4th generation)]] ==
{| class="wikitable"
|-
! Version
! Build
! Codename
! Baseband
! Comments
|-
| rowspan="3" | 5.1
| [[HoodooYabuli 9B3145a|9B3145a]]
| HoodooYabuli
| ?
| -
|-
| [[HoodooYabuli 9B3176b|9B3176b]]
| HoodooYabuli
| ?
| -
|-
| [[HoodooYabuli 9B3176n|9B3176n]]
| HoodooYabuli
| ?
| -
|}

[[Category:Firmware]]

NonUI builds

2018-05-08T23:05:56Z

ForestCorgi: Fix build name for iPhone 6S 13A93051l

{{internal software}}
{{see also|Beta Firmware|Internal OTA Updates}}
<div class="toclimit-3">{{float toc|left}}</div>
This is a documented list of known '''factory firmwares''', used by Apple workers in California to do engineering tests on prototype devices and also by factory workers on production ones during manufacturing. Factory firmwares are based on production iOS ones, but adapted for internal engineering tests, development and debugging. {{clear}}
[[File:newsblogo.png|thumb|125px|right|"Skankwerk" logo on 7.x and up]]
[[File:oldswblogo.png|thumb|125px|left|"Skankwerk" logo on 6.x and below]]
[[File:newswblogo.jpg|thumb|125px|right|Prototype showing Skankwerk logo during boot]]
[[File:oldswblogodevice.jpg|thumb|125px|left|Prototype showing Skankwerk logo during boot]]
They are also known as "NonUI (No User Interface)" builds, probably because most applications are command line ones. The SpringBoard replacement, named SwitchBoard, allow launching a GUI of some of those applications. Unlike production iOS firmwares, factory ones have the following differences:
* DEVELOPMENT Fused bootloaders in \Firmware\dfu\ and \Firmware\all_flash\all_flash.[board codename].factoryfa\.
* DEVELOPMENT Fused kernel cache with more symbols, and with individual kexts in /System/Library/Extensions
* Skankwerk (gear) logo image file in \Firmware\all_flash\all_flash.[board codename].factoryfa\.
* /AppleInternal folder, which the hierarchy inside get priority over hierarchy in /.
* No SpringBoard, requires the use of daemons to launch [[SwitchBoard.app]] as a multi-app launcher instead.
* /usr and subfolders contain many UNIX command line utilities.
* SSH daemon is pre-installed - as dropbear
* Boot loader passes arguments to kernel (unlike RELEASE boot loaders as of iOS 5.0) which makes it easy to disable AMFI
* It has some Private Frameworks in /System/Library/PrivateFrameworks for internal GUI apps and command line utilities.
* Most internal applications require the use of SkankKit to produce special layers such as text on the framebuffer.
Unlike regular iOS Firmwares, factory ones are distributed in both IPSWs and "restore bundles". Those are unzipped IPSW files which can be restored on devices using internal restore software such as [[PurpleRestore]]. Release and factory firmwares "restore bundles" have the same packaging structure (bootloaders, kernel, restore ramdisk, update ramdisk and root filesystem).
{{clear}}
= Some interesting facts about factory firmwares =
* '''Design:''' Apple seems to use the same GUI design from the production firmware to the factory one.
Production iOS 1.x to 6.x skeuomorphism design is also present on 1.x to 6.x factory firmwares, but seems really more excessive than production ones. For example, the "skankwerk" boot logo represents a real gear and many GUI icons are realistic or simply photos of real life things (especially in [[Operator]]). For newer versions, production iOS 7.x to 9.x flat design is mostly used in 7.x to 9.x factory firmwares. For example, the new "skankwerk" boot logo is a flat, simple white gear. Some newer internal applications like Earthbound also use a "flat" design.
* '''Other:''' The "skank" word is used to name multiple elements of factory firmwares. For example, there is "skankphone", "skankbattery" (the green battery shown in SwitchBoard), "skankwerk" logo, "skankkit" framework, "purpleskank" (used by BurnIn) and most likely others. The "skank" word seems to be a reference to "Skunkworks" projects, which are secrecy projects that are usually innovative. Read more about "Skunkworks" on [https://en.wikipedia.org/wiki/Skunkworks_project Wikipedia].

== [[M68AP|iPhone]] ==
{| class="wikitable"
|-
! Version
! Build
! Codename
! Baseband
! Comments
|-
| rowspan="2" | 1.0
| [[Alpine 1A420|1A420]]
| rowspan="3" | Alpine
| 03.06.01_G<sup>[http://web.archive.org/web/20110730023951/http://imageshack.us/photo/my-images/399/iphone2go0.jpg/]</sup>
| Originally available [http://forums.macrumors.com/showpost.php?p=7249071&postcount=85 here], but was soon taken down.
|-
| [[Alpine 4A57|4A57]]
| 04.02.13_G
| -
|-
| rowspan="1" | 1.1.2
| [[Alpine 3B48|3B48]]
| 04.02.13_G
| -
|-
| rowspan="2" | 1.1.3
| [[Alpine 4A102a|4A102a]]
| Alpine
| 04.04.05_G
| -
|-
|}

== [[N82AP|iPhone 3G]] ==
{| class="wikitable"
|-
! Version
! Build
! Codename
! Baseband
! Comments
|-
| rowspan="2" | 4.0
| [[ApexNanshan 8A2130h|8A2130h]]
| ApexNanshan
| ?
| -
|-
| [[ApexNanshan 8A2180g|8A2180g]]
| ApexNanshan
| 05.12.01
| -
|-
|}

== [[N88AP|iPhone 3GS]] ==
{| class="wikitable"
|-
! Version
! Build
! Codename
! Baseband
! Comments
|-
| rowspan="2" | 3.1b
| [[Sierra 7C108b|7C108b]]
| Sierra?
| ?
| -
|-
| [[Northstar 7C144|7C144]]
| Northstar?
| ?
| -
|-
| rowspan="2" | 4.0
| [[ApexNanshan 8A2130h|8A2130h]]
| ApexNanshan
| ?
| -
|-
| [[ApexNanshan 8A2180g|8A2180g]]
| ApexNanshan
| 05.12.01
| -
|-
| rowspan="3" | 5.1
| [[HoodooYabuli 9B3145a|9B3145a]]
| HoodooYabuli
| ?
| -
|-
| [[HoodooYabuli 9B3176b|9B3176b]]
| HoodooYabuli
| ?
| -
|-
| [[HoodooYabuli 9B3176n|9B3176n]]
| HoodooYabuli
| 05.16.05
| -
|-
| 6.0
| [[Sundance 10A316|10A316]]
| Sundance
| 05.16.06
| -
|}

== [[iPhone 4]] ==
{| class="wikitable"
|-
! Version
! Build
! Codename
! Baseband
! Comments
|-
| rowspan="4" | 4.0
| [[Apex 8A133|8A133]]
| Apex?
| 01.32.01
| -
|-
| [[Apex 8A2062a|8A2062a]]
| Apex?
| ?
| -
|-
| [[ApexNanshan 8A2130h|8A2130h]]
| ApexNanshan
| ?
| -
|-
| [[ApexNanshan 8A2180g|8A2180g]]
| ApexNanshan
| 01.42.01
| -
|-
| rowspan="3" | 5.1
| [[HoodooYabuli 9B3145a|9B3145a]]
| HoodooYabuli
| ?
| -
|-
| [[HoodooYabuli 9B3176b|9B3176b]]
| HoodooYabuli
| ?
| -
|-
| [[HoodooYabuli 9B3176n|9B3176n]]
| HoodooYabuli
| 04.12.01
| -
|-
| 6.0
| [[Sundance 10A316|10A316]]
| Sundance
| 04.12.02
| -
|-
|}

== [[N94AP|iPhone 4S]] ==
{| class="wikitable"
|-
! Version
! Build
! Codename
! Baseband
! Comments
|-
| rowspan="3" | 5.1
| [[HoodooYabuli 9B3145a|9B3145a]]
| HoodooYabuli
| ?
| -
|-
| [[HoodooYabuli 9B3176b|9B3176b]]
| HoodooYabuli
| ?
| -
|-
| [[HoodooYabuli 9B3176n|9B3176n]]
| HoodooYabuli
| 1.0.10
| -
|-
| 6.0
| [[SundanceNanshan 10A23941a|10A23941a]]
| SundanceNanshan
| 2.0.0.2
| -
|}

== [[iPhone 5]] ==
{| class="wikitable"
|-
! Version
! Build
! Codename
! Baseband
! Comments
|-
| rowspan="3" | 6.0
| [[Sundance 10A23110z|10A23110z]]
| Sundance?
| ?
| -
|-
| [[Sundance 10A23941s|10A23941s]]
| Sundance?
| ?
| -
|-
| [[Sundance 10A316|10A316]]
| Sundance
| 1.7.00
| -
|-
|}
== [[iPhone 5c]] ==
{| class="wikitable"
|-
! Version
! Build
! Codename
! Baseband
! Comments
|-
| 7.1
| [[Sochi 11D31620l|11D31620l]]
| Sochi?
| ?
| -
|}

== [[iPhone 5s]] ==
{| class="wikitable"
|-
! Version
! Build
! Codename
! Baseband
! Comments
|-
| rowspan="3" | 7.0
| [[InnsbruckNanshan 11A24580o|11A24580o]]
| InnsbruckNanshan
| 1.00.05
| -
|-
| [[InnsbruckNanshan 11A24581c|11A24581c]]
| InnsbruckNanshan
| ?
| -
|-
| [[Innsbruck 11A93840f|11A93840f]]
| Innsbruck?
| ?
| Originally found on a [https://forums.macrumors.com/threads/unusual-iphone-possible-engineering-sample-os.1885755/ Macrumors] post.
|-
|}

== [[N61AP|iPhone 6]] ==
{| class="wikitable"
|-
! Version
! Build
! Codename
! Baseband
! Comments
|-
| rowspan="5" | 8.0
| [[Okemo 12A22121a|12A22121a]]
| Okemo?
| ?
| -
|-
| [[Okemo 12A93311h|12A93311h]]
| Okemo?
| 1.00.01
| -
|-
| [[OkemoAni 12A93650o|12A93650o]]
| OkemoAni
| 1.00.05
| This build is pretty obscure, but it is in the wild.
|-
| [[OkemoAni 12A93651a|12A93651a]]
| OkemoAni
| 1.00.05
| -
|-
| [[OkemoAni 12A93651b|12A93651b]]
| OkemoAni
| 1.00.05
| -
|-
|}

== [[iPhone 6s]] ==
{| class="wikitable"
|-
! Version
! Build
! Codename
! Baseband
! Comments
|-
| rowspan="4" | 9.0
| [[Monarch 13A22120w|13A22120w]]
| Monarch?
| ?
| -
|-
| [[MonarchAni 13A93051l|13A93051l]]
| MonarchAni
| 0.37.08
| -
|-
| [[Monarch 13A93420d|13A93420d]]
| Monarch?
| ?
| -
|-
| [[Monarch 13A93420m|13A93420m]]
| Monarch?
| 1.00.05
| -
|-
|}

== [[D10AP|iPhone 7]] ==
{| class="wikitable"
|-
! Version
! Build
! Codename
! Baseband
! Comments
|-
| rowspan="5" | 10.0
| [[Whitetail 14A22580n|14A22580n]]
| Whitetail?
| ?
| -
|-
| [[Whitetail 14A22881a|14A22881a]]
| Whitetail?
| ?
| -
|-
| [[Whitetail 14A92340t|14A92340t]]
| Whitetail?
| ?
| -
|-
| [[WhitetailAni 14A93012r|14A93012r]]
| WhitetailAni
| ?
| -
|-
| [[WhitetailAni 14A93013a|14A93013a]]
| WhitetailAni
| ?
| -
|-
|}

== [[D20AP|iPhone 8]] ==
{| class="wikitable"
|-
! Version
! Build
! Codename
! Baseband
! Comments
|-
| 11.0
| [[TigrisAni 15A93261h|15A93261h]]
| TigrisAni
| ?
| -
|}

== [[D21AP|iPhone X]] ==
{| class="wikitable"
|-
| Version
| Build
| Codename
| Baseband
| Comments
|-
| 11.0
| [[TigrisAni 15A783601y|15A783601y]]
| TigrisAni?
| ?
| -
|}

== [[K48AP|iPad]] ==
{| class="wikitable"
|-
! Version
! Build
! Codename
! Baseband
! Comments
|-
| rowspan="2" | 3.2
| [[Wildcat 7B3341e|7B3341e]]
| Wildcat?
| ?
| -
|-
| [[Wildcat 7B5286a|7B5286a]]
| Wildcat?
| ?
| Found by SonnyDickson, documented on [https://9to5mac.com/2017/05/15/ipad-1-prototype/ 9to5mac]
|-
|}

== [[K93AP|iPad 2]] ==
{| class="wikitable"
|-
! Version
! Build
! Codename
! Baseband
! Comments
|-
| rowspan="2" | 4.3
| [[Durango 8F3178a|8F3178a]]
| Durango?
| ?
| -
|-
| [[Durango 8F3191d|8F3191d]]
| Durango?
| ?
| -
|-
|}

== [[P106AP|iPad mini]] ==
{| class="wikitable"
|-
! Version
! Build
! Codename
! Baseband
! Comments
|-
| rowspan="3" | 6.0
| [[SundanceTaosTianshan 10A63970m|10A63970m]]
| SundanceTaosTianshan
| ?
| -
|-
| [[SundanceTaosTianshan 10A63970v|10A63970v]]
| SundanceTaosTianshan
| ?
| -
|-
| [[SundanceTaosTianshan 10A63971b|10A63971b]]
| SundanceTaosTianshan
| ?
| -
|-
|}

== [[J86AP|iPad mini 2]] ==
{| class="wikitable"
|-
! Version
! Build
! Codename
! Baseband
! Comments
|-
| 7.0.3
| [[InnsbruckTaos 11B64940j|11B64940j]]
| InnsbruckTaos?
| ?
| -
|}

== [[J96AP|iPad mini 4]] ==
{| class="wikitable"
|-
! Version
! Build
! Codename
! Baseband
! Comments
|-
| 8.4
| [[Donner 12H60160o|12H60160o]]
| Donner?
| ?
| -
|-
| 9.0
| [[Monarch 13A62950o|13A62950o]]
| Monarch?
| ?
| -
|-
|}

== [[J71AP|iPad Air]] ==
{| class="wikitable"
|-
! Version
! Build
! Codename
! Baseband
! Comments
|-
| 7.0.1
| [[Innsbruck 11B34640l|11B34640l]]
| Innsbruck?
| ?
| -
|}

== [[N18AP|iPod touch (3rd generation)]] ==
{| class="wikitable"
|-
! Version
! Build
! Codename
! Baseband
! Comments
|-
| rowspan="3" | 3.1
| [[Inferno 7C1023e|7C1023e]]
| Inferno?
| ?
| -
|-
| [[Inferno 7C1095a|7C1095a]]
| Inferno?
| ?
| -
|-
| [[Northstar 7C144|7C144]]
| Northstar?
| ?
| -
|-
|}

== [[N81AP|iPod touch (4th generation)]] ==
{| class="wikitable"
|-
! Version
! Build
! Codename
! Baseband
! Comments
|-
| rowspan="3" | 5.1
| [[HoodooYabuli 9B3145a|9B3145a]]
| HoodooYabuli
| ?
| -
|-
| [[HoodooYabuli 9B3176b|9B3176b]]
| HoodooYabuli
| ?
| -
|-
| [[HoodooYabuli 9B3176n|9B3176n]]
| HoodooYabuli
| ?
| -
|}

[[Category:Firmware]]

Monarch 13A93051l

2018-05-08T23:05:05Z

ForestCorgi: Forestcorgi moved page Monarch 13A93051l to MonarchAni 13A93051l: Build name has been found in the system logs of said build

#REDIRECT [[MonarchAni 13A93051l]]

MonarchAni 13A93051l

2018-05-08T23:05:05Z

ForestCorgi: Forestcorgi moved page Monarch 13A93051l to MonarchAni 13A93051l: Build name has been found in the system logs of said build

{{internal software|firmware}}
== Background ==
This NonUI build is slightly bigger than [[Monarch 13A93420m]], and is once again a build based off of an internal version of iOS 9.0.
== Applications ==
This firmware seems to have the exact same applications as [[Monarch 13A93420m]], therefore this build is mostly likely focused on bug fixes and minor GUI tweaks.
*[[AltoMobile]]
*[[DropTest]]
*[[dtxCaliente]]
*[[GrapeCal]]
*[[LCDMura]] (hidden)
*[[LcdUTest]] (hidden)
*[[MesaCal]]
*[[Ness]] (hidden)
*[[NonUIConsoleViewer]]
*[[Operator]] (hidden)
*[[QRCode]]
*[[Reliability]]
*[[Sequencer]]
*[[Spelunx]]
*[[USBHost]]
*[[WiPASmini]]
*[[ThermalDOE]] (hidden)

The iPhone Wiki:Community portal

2018-04-13T00:44:24Z

ForestCorgi: Make verb agree with subject.

{{see also|Unsolved problems}}
{{Talk Archive}}
==The iPhone Wiki's SSL==
As a security researcher, I have a bad habit of inspecting every SSL certificate I get in my hands, I couldn't ignore the fact that the SSL Certificate used on The iPhone Wiki is provided by CloudFlare (?). If it is, then you guys better buy (with help from some donations maybe?) a Comodo Positive Certificate. Those free certs provided by Cloudflare are shared, and I heard numerous stories about it being simply circumvented or replaced by man in the middle attacks as these certificates only protect a node kinda giving user the false security illusion, but the origin server remains unprotected unless you apply for the Full SSL feature of Cloudflare that requires you to also buy a certificate for the host (if applies).

As you can see, on the FREE certificates, the origin is still not encrypted thus rendering breaches in the system.

This is how Flexible SSL works: [https://scotthelme.co.uk/wp-content/uploads/2014/01/cloudflare-flxible-ssl.png]

This article worth reading: [https://info.ssl.com/the-real-cost-of-a-cloudflare-free-ssl-certificate/]
[[User:GeoSn0w|GeoSn0w]] ([[User talk:GeoSn0w|talk]]) 19:11, 4 August 2016 (UTC)

:You seem to have a misconception about what CloudFlare offers on their plans.
: * All "levels of SSL" ([https://www.cloudflare.com/a/static/images/ssl/ssl.png Off, Flexible, Full, Strict]) are available on all plans.
: * What is only available to Business and Enterprise plans however, is the option to use your own certificate. Free and Pro plans have no choice.
: That said, it should be easy enough to get a free valid SSL cert from [https://letsencrypt.org/ Let's Encrypt] to use between your server and CF so that you can switch to Strict SSL - even on a free plan.
:
: Also, I'm not sure if Saurik has reacted to this already, but I'm neither seeing a CF-issued SSL cert being used on the wiki, nor does theiphonewiki.com resolve to a [https://www.cloudflare.com/ips/ Cloudflare IP].
: I'm seeing a RapidSSL SHA256 cert that looks like it has been issued on the 3. September 2015, and contains only "theiphonewiki.com" and "www.theiphonewiki.com" as common/alternative name.
: — [[User:Siguza|Siguza]] ([[User_talk:Siguza|talk]]) 23:10, 4 August 2016 (UTC)
Strange, I am seeing a CF signed cert for "graham.ns.cloudflare.com". And is also verified and issued by "Avast! WebShield" (this is kinda misleading because it is generated by my Antivirus), but the CF has no sense to show up in my firefox if you say you use RapidSSL.
Actually, I know what CF do and how their shared SSL work, as I use CF myself, and trust me, you can't compare your own cert with the one they provide. Shared certs are not actually yours, they will still point to CF...
[[User:GeoSn0w|GeoSn0w]] ([[User talk:GeoSn0w|talk]])
:It sounds like that's your antivirus/security software intercepting your HTTPS traffic. This is generally done with products that contain parental controls to block certain websites from children, but is frowned upon for privacy/security reasons. (For the record, I see the same thing Siguza sees.) --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 06:29, 8 August 2016 (UTC)

Actually, I uninstalled the AV just to test, and it still shows the same cert even after browser cleanup.[[User:GeoSn0w|GeoSn0w]] ([[User talk:GeoSn0w|talk]])
:To what IP does theiphonewiki.com resolve for you? For the record, I get 54.147.18.44. If someone out there has another valid cert for theiphonewiki.com, then that is quite a problem. — [[User:Siguza|Siguza]] ([[User_talk:Siguza|talk]]) 13:16, 18 August 2016 (UTC)
::Can confirm the IP address is 54.147.18.44 and I also see the same RapidSSL SHA256 CA - G3 cert being used. [[User:Mwoolweaver|MWoolweaver]] ([[User talk:Mwoolweaver|talk]]) 23:18, 24 April 2017 (UTC)

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

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

== Email notifications? ==
Is it possible to get emailed when a watchlist page changes? I'd love that feature. [[wikipedia:mw:Manual:Configuration settings#Email notification (Enotif) settings|This looks relevant]]. --[[User:Beej|beej]] ([[User talk:Beej|talk]]) 08:02, 27 June 2014 (UTC)

== Mobile Stylesheet ==

I was thinking recently, if [[User:Geohot|geohot]] agrees to accept it, that I could make a mobile.css file in order to attempt to make a few changes to the site on mobile. This would make it so that it would not be so ugly and if possible, the text might be easier to read. What would everyone think about this? For one thing, I'd like to mobile the "Log out" off the black part of the screen and put it near the "Contributions" button or thereabout. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 10:37, 7 January 2015 (UTC)
:Instead of a mobile stylesheet to hack up the skin more (like the <code>ios6</code> and <code>ios7</code> skins do), I would create a whole new skin. I could write the PHP and JavaScript, and you can write the CSS. --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 17:04, 7 January 2015 (UTC)
::If you mean a skin just for mobile, that would be ok but not sure how you could make it selectable with a mobile device but not on desktop. If you could do this, it could work but personally I think a mobile.css would be easier since it has to be previewed in the iOS simulator (that's the way I do it). I couldn't say I'd edit a page without being an admin (unless it's made that I could). --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 17:35, 7 January 2015 (UTC)
::I was going to mention that MediaWiki includes a sorta-mobile theme called Chick, but it seems that's [https://gerrit.wikimedia.org/r/#/q/Ia6d73c2deb9428d2,n,z long gone]. MW's changed a lot since I used it, but the way it worked was it subclassed MonoBook (so there was no need to duplicate the HTML template) and swapped its CSS for its own ([https://upload.wikimedia.org/wikipedia/mediawiki/f/f6/Dantman-Skin-chick.png screenshot]).<br>Come to think of it, whoa, I even wrote my own skin called [https://github.com/kirb/iWiki iWiki]. Was never updated for MW 1.17, which made breaking changes to the skin API. I probably won't have the time to update it, but maybe someone else could? [[User:Thekirbylover|kirb]] ([[User talk:Thekirbylover|talk]]) 09:01, 8 January 2015 (UTC)
:I think this is a great idea, since this is actually a wiki about mobiles. No idea why it hasn't been done already. — '''[[User:Spydar007|<span style="color:black;">Spydar007</span>]] [[User talk:Spydar007|<span style="color:gray;">(Talk)</span>]]''' 15:17, 8 January 2015 (UTC)
::| There is a mobile pluggin for Media Wiki that will make it look very nice [[User:Mwoolweaver|MWoolweaver]] ([[User talk:Mwoolweaver|talk]]) 07:22, 1 February 2015 (UTC)
:::I completed this a while ago but forgot to comment about it. If anyone has any improvement requests, feel free to list them and I'll take a look. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 11:07, 24 April 2015 (UTC)

== Bite-sized editing tasks ==
It seems fun to make a list of relatively easy useful edits that new editors can do who are interested in helping, maybe at [[The iPhone Wiki:Bite-sized editing tasks]] or a similar page, and link it from the homepage here. I'd include the following as a start:

* Look at the list at [[Special:LonelyPages]] and figure out whether some of those pages should be linked within other pages on the wiki, and then go link them.
* Check the links at [[Useful Links]] and remove broken/outdated sites and add relevant new sites (but don't spam your own stuff).
* The iOS version table at [[SHSH]] should be listed in reverse-chronological order, with newest versions first instead of oldest versions first.
* If you run into a scam site, add it to the table at [[Scam Jailbreaks and Unlocks]].
* If you're reading an article and some part of it is confusing to you, post a message on the "talk" page (click the "Discussion" tab at the top of the article) explaining your question or what you found confusing, so that other editors can use this as a suggestion for improving the article.

Ideas? Opinions? [[User:Britta|Britta]] ([[User talk:Britta|talk]]) 09:31, 14 May 2015 (UTC)

== How to report problems ==
I saw people concerned on Twitter about the skin! Like iAdam1n said on Twitter, saurik just got a copy of the settings, images, and database from geohot and put them into a new site with an upgraded version of MediaWiki; he's asking geohot for a copy of the skin files. In general if you see problems or have requests for new extensions or other changes, it's totally fine to post them here and I'll see them and ask saurik to check it out. If something is more immediate and doesn't need discussion (like something missing, major errors, mysterious downtime, etc.), you can PM me or saurik on IRC (his IRC server is best, irc.saurik.com). Maybe good to post here too in those cases (if the site isn't down at the time) so other people know he's been alerted. [[User:Britta|Britta]] ([[User talk:Britta|talk]]) 18:44, 14 May 2015 (UTC)

More about how to report more immediate problems (or problems that require some level of privacy, such as a major security issue or "Britta has gone rogue") - if you don't use IRC, emailing me is also fine (britta@saurikit.com). Emailing saurik (saurik@saurik.com) won't be seen as quickly, but if you write a meaningful subject line (like "TheiPhoneWiki is giving error 403 upon login right now" or "Britta is putting glitter sparkle GIFs all over TheiPhoneWiki"), it'll likely be seen. Moving to a new server/admin can have some adjustment bumps but they can be fixed! [[User:Britta|Britta]] ([[User talk:Britta|talk]]) 03:03, 15 May 2015 (UTC)

== Apple internal content on the Wiki ==
I want to know what people think about having internal content on the Wiki. Some of the current content definitely needs some cleaning up and general editing. Should we publish information about internal firmwares? And is it okay to upload pictures of prototypes? Feel free to ask more questions. --[[User:Srb21103|Srb21103]] ([[User talk:Srb21103|talk]]) 05:08, 18 May 2015 (UTC)
:Looking through [[The iPhone Wiki:Ground rules]], it says "No posting of copyrighted material. Anything that could legally get us in trouble should not be posted, ever." I'm not sure what other precedent here has been. [[User:Britta|Britta]] ([[User talk:Britta|talk]]) 10:31, 18 May 2015 (UTC)

== JailbreakCon mini-talks ==
Hi wiki people! I'm working on gathering people to do mini-talks (5-10 minutes) for [[JailbreakCon]] in June in San Francisco, and it would be cool to have some more people speaking who contribute to the community in ways other than tweak development. Work other than development is important work too, such as documentation. If anyone who has put some effort into improving TheiPhoneWiki can attend and would like to give a mini talk about working on the wiki, let me know via [http://www.jailbreakcon.com/#contact the contact form on the site]. [[User:Britta|Britta]] ([[User talk:Britta|talk]]) 00:35, 26 May 2015 (UTC)

== [[File System Crypto]] ==
I just added Zdziarski's blog to the wiki (with his permission). I would recommend to take this apart and make multiple sub-articles, like an article for [[BAGI]], another one for [[Dkey]], etc. and on the page [[File System Crypto]] itself, just write the overview, similar to what we have on page 16 of the Sogeti document (wasn't there a newer graphic somewhere?) with some short description. --[[User:Http|http]] ([[User talk:Http|talk]]) 22:11, 9 June 2015 (UTC)

== Renaming [[Factory Firmware]]? ==
It's been brought to my attention that we don't really have anywhere on the wiki to document internal builds of iOS. Considering [[Factory Firmware]] consists of what are internal builds of iOS (with different software), I'd like to propose renaming it to [[Internal Firmware]], to broaden its scope a little more. Well, either that or create a brand new page for internal builds. What does everyone think about this? --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 06:43, 17 April 2016 (UTC)

== Amendments to Rule 3.7 ==
I would like to propose some amendments to Section 3.7, "Do not make numerous, consecutive edits." Recently, device renames and page cleanup have been taking place. As of now, I would classify page moves/deletions as edits. In addition to the 50 edits, I wanted to know— how would you feel about adding an additional 10 actions for page deletions? Considering page deletions are an admin-exclusive action, I don't want this amendment to be misconstrued as admin abuse of power. (Yes, us admins are meant to be subject to this rule as well.)

Another amendment I would like to make involves vandalism. Although it hasn't happened on here for quite a while, vandalism can occur on the wiki. As things currently stand, reverting vandalism would technically count as an edit. I don't think that should be the case, so I would like to add some language that does not count reverting vandalism against the edit limits. --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 20:03, 22 March 2017 (UTC)
:I was actually planning on making a topic on this after we had finished with the device names cleanup.
:I propose the removal of the rule entirely. This rule is stupid. I have not found any other wiki anywhere that imposes limits on the number of times a person can edit in a day or hour. It's absurd. Wikis are about collaborative editing. There should not be edit limits.
:Whilst I understand that making lots of edits can clog up RecentChanges, this is not a problem when you can change RecentChanges to show the last 2000 edits in the past 90 days. I could make 500 edits in the space of an hour, and this will not be a problem since RecentChanges can show a rather large amount of edits.
:The wiki is not ''incredibly'' active; it's the same few people editing. Vandalism is ridiculously unlikely, since everyone has to create an account to edit and that's a silly reason to prevent the number of edits a person can make. The majority of edits these days equate to Firmware and OTA Updates and details on Jailbreak page. These edits often take up more than 20 edits in an hour due to the growing number of devices. The edits to the device names that we are currently doing involve hundreds of edits. To have to watch how many edits we are making and to only be able to do a certain number is just silly. — '''[[User:Spydar007|<span style="color:black;">Spydar007</span>]] [[User talk:Spydar007|<span style="color:gray;">(Talk)</span>]]''' 20:42, 22 March 2017 (UTC)
::The rule was put into place is because the wiki has seen countless instances of "insignificant" edits (i.e. no major content, just adjustments like renaming "iPhone 4 GSM" to "iPhone3,1"), and there were a lot of complaints about this. We're not going down that road again. The main reason other wikis don't have a rule like this is probably because other wikis never deal with floods of edits just to rename one thing on such a frequent basis. On this wiki, a humongous change like this seems to happen every (other) year. (Why? This shouldn't be the case.) '''The rule stays''', but it's open for amendments— we can increase the limit count, for example. --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 21:16, 22 March 2017 (UTC)
:::I do think we should increase it. I'd propose either 75 or 100 daily edits and 30 major/minor (30 of each that is) per hour. Especially when we have a new firmware release, it is easy to go over 20 edits and if quick enough, could be done within an hour so I do think we should allow for more. I am with Spydar007 partly though as, although I can see why the rule was useful, we don't get enough editors to really cause an issue with this. If that changed, then we could review it. However, it isn't a make or break for me but I do think removing it would be a fairly good idea due to how few people edit this wiki now. I've also always thought that it would be better to fill Recent Changes on one day with big edits like that are currently taking place and then it be over, than do less edits that take a lot longer. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 10:22, 23 March 2017 (UTC)
::If that's the reason the rule was put in place, then it should ''definitely'' be removed. This rule does not prevent those edits from being made; it simply prevents the number of edits that can be made in a given time. With the same few editors, no one is going to be renaming "iPhone 4 GSM" to "iPhone3,1", or anything like that. And again, this rule doesn't prevent those edits from being made. I've never seen a large amount of these "insignificant" edits being made in any of the time I have had an account on this wiki. I'd say this is to do with the changing userbase of the wiki, and not anything else.
::If you ''absolutely'' insist that the rule is kept, then it should be changed to allow 50 edits per hour. No daily limits. This allows for plenty of cleanup to be made. Of course, if we start to see people making silly changes, then a nice message on the user's talk page usually suffices, and a general discussion about why the user feels that page or file should be changed or renamed, and not the creation of a rule to allow you to block the user. This rule was added (and from what I can see, with no discussion) on December 12, 2011‎. I can see no violations of this rule in silly page moves before this date. I simply do not see a need for this rule, and I feel like it hinders the amount of actually constructive edits to the wiki. — '''[[User:Spydar007|<span style="color:black;">Spydar007</span>]] [[User talk:Spydar007|<span style="color:gray;">(Talk)</span>]]''' 11:07, 23 March 2017 (UTC)
:::There absolutely was a [[The iPhone Wiki:Community portal/2011#New rule proposal|discussion]]. It's not meant to prevent these types of changes, as they can be necessary; it's meant to keep the list of changes accessible/readable, since an edit that's either questionable or notable (e.g. information about a new OTA package format) can easily be buried among 94 edits of merely renaming "iPod touch 4G" into "iPod touch (4th generation)." That said, taking the feedback into account, I think raising the limits to 50 major/50 minor edits per hour, with a daily limit of 150 edits would make a fair compromise. (Not having the daily limit would mean that you can actually make up all of the last 2,400 edits in one day. Uh… No.) --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 16:17, 23 March 2017 (UTC)
::::That limit would be awesome. I really like that idea of 50 major/50 minor edits per hour and 150 daily limit. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 16:35, 23 March 2017 (UTC)

----

Okay, I think Axi0mX's contributions highlighted something about this rule: if someone dumps a bunch useful information across numerous pages, it can very easily affect them. Contributions like these were not the intended target of the rule, and people shouldn't be punished for trying to share such information. However, we do need a system in place to limit insignificant changes— we do not, and should not, need to rename a key page every two years. I want to propose changing this to allow informative edits, such as the keys Axi0mX shared, while imposing a limit on inconsequential changes.

The following blurb reflects the changes I wish to make, and will be edited as suggestions are implemented. (Emphasis is added to highlight changes, and will not be part of the rule.)

<div style="background-color:#FFF; background-color:rgba(255,255,255,0.85); border:1px solid #AAA; padding:1em;">
<ins>From time to time, the format of pages on The iPhone Wiki may require changes. For example, we determined it was necessary to name device pages by their internal identifier (e.g. [[N72AP]]), and use the model identifier in firmware key pages (e.g. [[Sugar Bowl 5F138 (iPod2,1)]]). However,</ins> making <del>a lot of edits</del><ins>format changes like this</ins> causes the [[Special:RecentChanges|Recent changes]] to be filled up<ins>, as numerous pages must be edited or renamed to follow the new format</ins>. <del>In addition to annoying those that subscribe to the Recent changes feed (via Atom or Twitter), this hinders</del><ins>By filling the Recent changes feed with insignificant changes,</ins> everyone's ability to discover new information and track down any malicious <del>changes</del><ins>edits is unnecessarily hindered</ins>.

Therefore, for every hour (resetting at :00), you may only make <del>50 major edits and 50 minor edits. Do not abuse the ability to mark edits as minor to perform additional edits— if your non-minor edits look considerably similar to minor edits you made in the same hour (or vice-versa), this may be considered abuse</del><ins>up to 50 format changes</ins>. In addition, you may make no more than 150 edits <ins>pertaining to such format changes</ins> per day (resetting at midnight UTC). Any unused number of edits <ins>pertaining to format changes</ins> will ''not'' "roll over" to the next hour or day. <del>Avoid "clumping" your edits.</del><ins>Any such edits should not be "clumped" together.</ins> (e.g.- Do not make 45 edits <ins>for format changes</ins> at 01:58, and then another 45 at 02:01.) Temporary exemptions can be made at the discretion of administrators and/or the community. <ins>Enforcement of this rule is otherwise subject to the administrators' discretion.</ins>
</div>

This is a rough proposal, but I think this is going in the right direction. Are there any objections/suggestions? --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 02:11, 21 July 2017 (UTC)

:Sounds ok to me. I'd probably add firmware updates to the list of informative edits as they are pretty important. The only issue I can see with this is there will be a load of things not covered and could be confusing. I'm thinking maybe we could remove the rule altogether and if we get into an issue in future, add it back for certain things, such as key page template changes, although I hope we never do that again. If we must keep the rule, then I'd say keep it only for format changes. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 12:02, 21 July 2017 (UTC)

::Good point. Although I tried to provide examples of what should/should not be considered "informative," it can seem confusing. Considering that this rule was created pretty much solely because of the constant format changes, targeting those specifically should be fine. Unless someone has a second opinion, I'll revise the proposal tonight. (I don't have time right now to work on the text. I swear it's not because of Splatoon 2... Yet.) --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 16:13, 21 July 2017 (UTC)

== Wiki Logo Update 2017 ==
I think it's time we update the logo in the top left corner again. iPhone 4S and iOS 5 are so 2011. And that font definitely isn't San Francisco. I'll see if I can get something worked out. --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 05:48, 20 September 2017 (UTC)
:I believe Dialexio has already been working on this, see his Twitter for examples. — '''[[User:Spydar007|<span style="color:black;">Spydar007</span>]] [[User talk:Spydar007|<span style="color:gray;">(Talk)</span>]]''' 06:27, 20 September 2017 (UTC)
::Yup, I've been working on this for a few days now. As of now, [https://twitter.com/Dialexio/status/910260179463221249 this] is what I have so far. I was actually planning to make a topic about this today, but I guess I got beaten to the punch. :P --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 17:06, 20 September 2017 (UTC)
:::I was thinking something with iPhone X, too. But I think it should face the other way. Unless there's two phones back to back, having one face left looks weird IMHO. --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 21:41, 20 September 2017 (UTC)
::::I couldn't find any (clean) images from Apple that had the iPhone X facing right. I see no issue with the direction that the phone faces, though I suppose a right-facing one would've been a cleaner replacement for the current logo. --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 00:18, 21 September 2017 (UTC)
:::::On [https://apple.com/iphone/ apple.com/iphone], there's a big image of iPhone X: [https://images.apple.com/v/iphone/home/w/images/home/iphone_x_large.jpg iphone_x_large.jpg] (981x206). There's also [https://images.apple.com/media/us/iphone-x/2017/01df5b43-28e4-4848-bf20-490c34a926a7/overview/primary/design_corners/large.mp4 large.mp4] ([https://www.dropbox.com/s/v6ih5gf94m5f97y/080.bmp?dl=1 extracted image] - 1024x246). Would either of those work? --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 00:44, 21 September 2017 (UTC)
::::::Honestly, I think using a landscape iPhone would look even ''weirder'' than a portrait-oriented iPhone facing left. (There really isn't anything wrong with the latter.) Aside from taking or viewing photos/videos (...okay, games too, but those aren't exactly included from the get-go), iPhones aren't depicted in landscape. I did make an attempt to see what I can do with the first image, but when I tried resizing the first image to fit the logo's 150x150 size, I felt that it became somewhat difficult to identify as an iPhone. It almost looks like it's just a random bar of colors. Considering the dimensions for the second, I imagine that it would have a similar result. --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 03:28, 21 September 2017 (UTC)
:::::::Well you would rotate them 90° clockwise; I meant to specify that, but failed to do so. Anyways, considering the fact that iPhones have gotten bigger, there's not much we can do with only 150×150 pixels. In fact, [https://www.mediawiki.org/wiki/Manual:$wgLogo MediaWiki recommends no bigger than 135×135.] That documentation page does note, however, that we ''can'' use a bigger logo with some changes to the CSS. --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 00:51, 22 September 2017 (UTC)
::::::::Okay, I just tried rotating it, and I don't like the result at all— it seems off-center since the iPhone image is thinner. For both my version and the suggested swap, I made minor edits to the gradient color and switched to SF Text instead of SF Display. (I put together a comparison [https://imgur.com/a/fZXlU on imgur].) I'm sticking with the iPhone X image I originally used for my spin on a new logo. --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 03:56, 22 September 2017 (UTC)
:::::::::Well, the current logo has the iPhone at about the same angle as the second one. I think it only looks weird because it's too far to the left. I do prefer the angle of the first one (your original idea). However, I don't like the left facing direction; We do work in a left-to-right language. I do think, though, that a render of the lock screen is bad. Maybe I just prefer the current logo's use of the home screen because it adds color? I'm not particularly a fan of that wallpaper, but that's just me. I wonder if it would be possible to take all the 3D renders of iPhone X from Apple and build our own 3D model that could be positioned how we want it. I'll try that. In the meantime, I found this: [https://images.apple.com/v/iphone-x/b/images/overview/modal/design_expression_large.jpg design_expression_large.jpg] --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 23:15, 22 September 2017 (UTC)
::::::::::The left-to-right argument doesn't make sense to me; it's not like I wrote the words backwards or aligned it like it's a right-to-left language. Many Western brands do have an icon/glyph/whatever to the left of the text— Crunchyroll, Dropbox, Microsoft, Seagate, and YouTube all do that. (Of course, some brands like American Airlines and Chase have theirs on the right.) I don't think an image with the Lock screen is bad, but the wallpaper Apple chose for their iPhone X photos is rather... loud. The image I picked would probably look better if the colors weren't so bold. (Don't get me wrong though— I don't mind using a different iPhone X image or swapping the text and picture around, but I couldn't find any iPhone X images that look or fit better, except maybe a shot of the front without any perspective.) --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 03:21, 23 September 2017 (UTC)

== New rule proposal: Internal subjects ==
As we know, there are internal firmware builds that Apple uses to test their hardware. However, a wiki user reached out to me, concerned that there is incorrect information being added about these firmwares. I have no way to verify this information (and most probably don't either), so I would like to create a rule to require evidence in the form of an image or video for any substantial information about any such Apple internal subjects. This will help prevent false information being spread on the wiki.

<div style="background-color:#FFF; background-color:rgba(255,255,255,0.85); border:1px solid #AAA; padding:1em;">
Internal software and prototypes are rare to come across, and we welcome documentation about them. However, to maintain informational integrity, we do require evidence to be supplied with any substantial information that you have. For example, if you have a list of applications in an internal firmware, there should be an image or video showing them on the device. Any added information about internal subjects that does not comply with this is subject to removal, with account suspensions possible.
</div>

The above proposal will be edited as necessary during this discussion. --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 16:53, 22 October 2017 (UTC)

== Discussion of takedown for Cassandra Fuzzer ==
As you may know, the Cassandra Fuzzer, developed by [[Ih8ra1n|iH8Ra1n]] was taken down by [https://www.theiphonewiki.com/wiki/User:IAdam1n iAdam1n]. I ([[Ih8ra1n|iH8Ra1n]]) believe that Cassandra should not have been taken down for the following reasons:

* Information (If someone wants to help with it, for example. )

* Other vulnerabilities (Read on)

I think that I would be leaving people without some necessary information. Example, Cassandra discovers a vulnerability in MobileSafari. Now, I make a page about said vulnerability. I should probably mention Cassandra found it. Then, people wonder what it is. So, they look for a wiki page and find it was deleted. So, now they wonder what Cassandra is, and they don't know. This, I think, is a problem. Hence, why there should be a wiki page for it. {{unsigned|Ih8ra1n}}

With all due respect, the [[The_iPhone_Wiki:Ground_rules#Regarding_the_creation_of_pages_for_programs|ground rules]] specifically say that one should not create a page for a program that is upcoming. Moreover, it also states that the creator of a program should not be involved in its page's creation. I don't believe that Cassandra should be added to the wiki until it gains enough of a reputation independent of this place that someone else thinks to add it. [[User:Forestcorgi|Forestcorgi]] ([[User talk:Forestcorgi|talk]]) 00:41, 13 April 2018 (UTC)

The iPhone Wiki:Community portal

2018-04-13T00:42:24Z

ForestCorgi: Add reply to ih8rain's discussion of the takedown of Cassandra Fuzzer.

{{see also|Unsolved problems}}
{{Talk Archive}}
==The iPhone Wiki's SSL==
As a security researcher, I have a bad habit of inspecting every SSL certificate I get in my hands, I couldn't ignore the fact that the SSL Certificate used on The iPhone Wiki is provided by CloudFlare (?). If it is, then you guys better buy (with help from some donations maybe?) a Comodo Positive Certificate. Those free certs provided by Cloudflare are shared, and I heard numerous stories about it being simply circumvented or replaced by man in the middle attacks as these certificates only protect a node kinda giving user the false security illusion, but the origin server remains unprotected unless you apply for the Full SSL feature of Cloudflare that requires you to also buy a certificate for the host (if applies).

As you can see, on the FREE certificates, the origin is still not encrypted thus rendering breaches in the system.

This is how Flexible SSL works: [https://scotthelme.co.uk/wp-content/uploads/2014/01/cloudflare-flxible-ssl.png]

This article worth reading: [https://info.ssl.com/the-real-cost-of-a-cloudflare-free-ssl-certificate/]
[[User:GeoSn0w|GeoSn0w]] ([[User talk:GeoSn0w|talk]]) 19:11, 4 August 2016 (UTC)

:You seem to have a misconception about what CloudFlare offers on their plans.
: * All "levels of SSL" ([https://www.cloudflare.com/a/static/images/ssl/ssl.png Off, Flexible, Full, Strict]) are available on all plans.
: * What is only available to Business and Enterprise plans however, is the option to use your own certificate. Free and Pro plans have no choice.
: That said, it should be easy enough to get a free valid SSL cert from [https://letsencrypt.org/ Let's Encrypt] to use between your server and CF so that you can switch to Strict SSL - even on a free plan.
:
: Also, I'm not sure if Saurik has reacted to this already, but I'm neither seeing a CF-issued SSL cert being used on the wiki, nor does theiphonewiki.com resolve to a [https://www.cloudflare.com/ips/ Cloudflare IP].
: I'm seeing a RapidSSL SHA256 cert that looks like it has been issued on the 3. September 2015, and contains only "theiphonewiki.com" and "www.theiphonewiki.com" as common/alternative name.
: — [[User:Siguza|Siguza]] ([[User_talk:Siguza|talk]]) 23:10, 4 August 2016 (UTC)
Strange, I am seeing a CF signed cert for "graham.ns.cloudflare.com". And is also verified and issued by "Avast! WebShield" (this is kinda misleading because it is generated by my Antivirus), but the CF has no sense to show up in my firefox if you say you use RapidSSL.
Actually, I know what CF do and how their shared SSL work, as I use CF myself, and trust me, you can't compare your own cert with the one they provide. Shared certs are not actually yours, they will still point to CF...
[[User:GeoSn0w|GeoSn0w]] ([[User talk:GeoSn0w|talk]])
:It sounds like that's your antivirus/security software intercepting your HTTPS traffic. This is generally done with products that contain parental controls to block certain websites from children, but is frowned upon for privacy/security reasons. (For the record, I see the same thing Siguza sees.) --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 06:29, 8 August 2016 (UTC)

Actually, I uninstalled the AV just to test, and it still shows the same cert even after browser cleanup.[[User:GeoSn0w|GeoSn0w]] ([[User talk:GeoSn0w|talk]])
:To what IP does theiphonewiki.com resolve for you? For the record, I get 54.147.18.44. If someone out there has another valid cert for theiphonewiki.com, then that is quite a problem. — [[User:Siguza|Siguza]] ([[User_talk:Siguza|talk]]) 13:16, 18 August 2016 (UTC)
::Can confirm the IP address is 54.147.18.44 and I also see the same RapidSSL SHA256 CA - G3 cert being used. [[User:Mwoolweaver|MWoolweaver]] ([[User talk:Mwoolweaver|talk]]) 23:18, 24 April 2017 (UTC)

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

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

== Email notifications? ==
Is it possible to get emailed when a watchlist page changes? I'd love that feature. [[wikipedia:mw:Manual:Configuration settings#Email notification (Enotif) settings|This looks relevant]]. --[[User:Beej|beej]] ([[User talk:Beej|talk]]) 08:02, 27 June 2014 (UTC)

== Mobile Stylesheet ==

I was thinking recently, if [[User:Geohot|geohot]] agrees to accept it, that I could make a mobile.css file in order to attempt to make a few changes to the site on mobile. This would make it so that it would not be so ugly and if possible, the text might be easier to read. What would everyone think about this? For one thing, I'd like to mobile the "Log out" off the black part of the screen and put it near the "Contributions" button or thereabout. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 10:37, 7 January 2015 (UTC)
:Instead of a mobile stylesheet to hack up the skin more (like the <code>ios6</code> and <code>ios7</code> skins do), I would create a whole new skin. I could write the PHP and JavaScript, and you can write the CSS. --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 17:04, 7 January 2015 (UTC)
::If you mean a skin just for mobile, that would be ok but not sure how you could make it selectable with a mobile device but not on desktop. If you could do this, it could work but personally I think a mobile.css would be easier since it has to be previewed in the iOS simulator (that's the way I do it). I couldn't say I'd edit a page without being an admin (unless it's made that I could). --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 17:35, 7 January 2015 (UTC)
::I was going to mention that MediaWiki includes a sorta-mobile theme called Chick, but it seems that's [https://gerrit.wikimedia.org/r/#/q/Ia6d73c2deb9428d2,n,z long gone]. MW's changed a lot since I used it, but the way it worked was it subclassed MonoBook (so there was no need to duplicate the HTML template) and swapped its CSS for its own ([https://upload.wikimedia.org/wikipedia/mediawiki/f/f6/Dantman-Skin-chick.png screenshot]).<br>Come to think of it, whoa, I even wrote my own skin called [https://github.com/kirb/iWiki iWiki]. Was never updated for MW 1.17, which made breaking changes to the skin API. I probably won't have the time to update it, but maybe someone else could? [[User:Thekirbylover|kirb]] ([[User talk:Thekirbylover|talk]]) 09:01, 8 January 2015 (UTC)
:I think this is a great idea, since this is actually a wiki about mobiles. No idea why it hasn't been done already. — '''[[User:Spydar007|<span style="color:black;">Spydar007</span>]] [[User talk:Spydar007|<span style="color:gray;">(Talk)</span>]]''' 15:17, 8 January 2015 (UTC)
::| There is a mobile pluggin for Media Wiki that will make it look very nice [[User:Mwoolweaver|MWoolweaver]] ([[User talk:Mwoolweaver|talk]]) 07:22, 1 February 2015 (UTC)
:::I completed this a while ago but forgot to comment about it. If anyone has any improvement requests, feel free to list them and I'll take a look. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 11:07, 24 April 2015 (UTC)

== Bite-sized editing tasks ==
It seems fun to make a list of relatively easy useful edits that new editors can do who are interested in helping, maybe at [[The iPhone Wiki:Bite-sized editing tasks]] or a similar page, and link it from the homepage here. I'd include the following as a start:

* Look at the list at [[Special:LonelyPages]] and figure out whether some of those pages should be linked within other pages on the wiki, and then go link them.
* Check the links at [[Useful Links]] and remove broken/outdated sites and add relevant new sites (but don't spam your own stuff).
* The iOS version table at [[SHSH]] should be listed in reverse-chronological order, with newest versions first instead of oldest versions first.
* If you run into a scam site, add it to the table at [[Scam Jailbreaks and Unlocks]].
* If you're reading an article and some part of it is confusing to you, post a message on the "talk" page (click the "Discussion" tab at the top of the article) explaining your question or what you found confusing, so that other editors can use this as a suggestion for improving the article.

Ideas? Opinions? [[User:Britta|Britta]] ([[User talk:Britta|talk]]) 09:31, 14 May 2015 (UTC)

== How to report problems ==
I saw people concerned on Twitter about the skin! Like iAdam1n said on Twitter, saurik just got a copy of the settings, images, and database from geohot and put them into a new site with an upgraded version of MediaWiki; he's asking geohot for a copy of the skin files. In general if you see problems or have requests for new extensions or other changes, it's totally fine to post them here and I'll see them and ask saurik to check it out. If something is more immediate and doesn't need discussion (like something missing, major errors, mysterious downtime, etc.), you can PM me or saurik on IRC (his IRC server is best, irc.saurik.com). Maybe good to post here too in those cases (if the site isn't down at the time) so other people know he's been alerted. [[User:Britta|Britta]] ([[User talk:Britta|talk]]) 18:44, 14 May 2015 (UTC)

More about how to report more immediate problems (or problems that require some level of privacy, such as a major security issue or "Britta has gone rogue") - if you don't use IRC, emailing me is also fine (britta@saurikit.com). Emailing saurik (saurik@saurik.com) won't be seen as quickly, but if you write a meaningful subject line (like "TheiPhoneWiki is giving error 403 upon login right now" or "Britta is putting glitter sparkle GIFs all over TheiPhoneWiki"), it'll likely be seen. Moving to a new server/admin can have some adjustment bumps but they can be fixed! [[User:Britta|Britta]] ([[User talk:Britta|talk]]) 03:03, 15 May 2015 (UTC)

== Apple internal content on the Wiki ==
I want to know what people think about having internal content on the Wiki. Some of the current content definitely needs some cleaning up and general editing. Should we publish information about internal firmwares? And is it okay to upload pictures of prototypes? Feel free to ask more questions. --[[User:Srb21103|Srb21103]] ([[User talk:Srb21103|talk]]) 05:08, 18 May 2015 (UTC)
:Looking through [[The iPhone Wiki:Ground rules]], it says "No posting of copyrighted material. Anything that could legally get us in trouble should not be posted, ever." I'm not sure what other precedent here has been. [[User:Britta|Britta]] ([[User talk:Britta|talk]]) 10:31, 18 May 2015 (UTC)

== JailbreakCon mini-talks ==
Hi wiki people! I'm working on gathering people to do mini-talks (5-10 minutes) for [[JailbreakCon]] in June in San Francisco, and it would be cool to have some more people speaking who contribute to the community in ways other than tweak development. Work other than development is important work too, such as documentation. If anyone who has put some effort into improving TheiPhoneWiki can attend and would like to give a mini talk about working on the wiki, let me know via [http://www.jailbreakcon.com/#contact the contact form on the site]. [[User:Britta|Britta]] ([[User talk:Britta|talk]]) 00:35, 26 May 2015 (UTC)

== [[File System Crypto]] ==
I just added Zdziarski's blog to the wiki (with his permission). I would recommend to take this apart and make multiple sub-articles, like an article for [[BAGI]], another one for [[Dkey]], etc. and on the page [[File System Crypto]] itself, just write the overview, similar to what we have on page 16 of the Sogeti document (wasn't there a newer graphic somewhere?) with some short description. --[[User:Http|http]] ([[User talk:Http|talk]]) 22:11, 9 June 2015 (UTC)

== Renaming [[Factory Firmware]]? ==
It's been brought to my attention that we don't really have anywhere on the wiki to document internal builds of iOS. Considering [[Factory Firmware]] consists of what are internal builds of iOS (with different software), I'd like to propose renaming it to [[Internal Firmware]], to broaden its scope a little more. Well, either that or create a brand new page for internal builds. What does everyone think about this? --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 06:43, 17 April 2016 (UTC)

== Amendments to Rule 3.7 ==
I would like to propose some amendments to Section 3.7, "Do not make numerous, consecutive edits." Recently, device renames and page cleanup have been taking place. As of now, I would classify page moves/deletions as edits. In addition to the 50 edits, I wanted to know— how would you feel about adding an additional 10 actions for page deletions? Considering page deletions are an admin-exclusive action, I don't want this amendment to be misconstrued as admin abuse of power. (Yes, us admins are meant to be subject to this rule as well.)

Another amendment I would like to make involves vandalism. Although it hasn't happened on here for quite a while, vandalism can occur on the wiki. As things currently stand, reverting vandalism would technically count as an edit. I don't think that should be the case, so I would like to add some language that does not count reverting vandalism against the edit limits. --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 20:03, 22 March 2017 (UTC)
:I was actually planning on making a topic on this after we had finished with the device names cleanup.
:I propose the removal of the rule entirely. This rule is stupid. I have not found any other wiki anywhere that imposes limits on the number of times a person can edit in a day or hour. It's absurd. Wikis are about collaborative editing. There should not be edit limits.
:Whilst I understand that making lots of edits can clog up RecentChanges, this is not a problem when you can change RecentChanges to show the last 2000 edits in the past 90 days. I could make 500 edits in the space of an hour, and this will not be a problem since RecentChanges can show a rather large amount of edits.
:The wiki is not ''incredibly'' active; it's the same few people editing. Vandalism is ridiculously unlikely, since everyone has to create an account to edit and that's a silly reason to prevent the number of edits a person can make. The majority of edits these days equate to Firmware and OTA Updates and details on Jailbreak page. These edits often take up more than 20 edits in an hour due to the growing number of devices. The edits to the device names that we are currently doing involve hundreds of edits. To have to watch how many edits we are making and to only be able to do a certain number is just silly. — '''[[User:Spydar007|<span style="color:black;">Spydar007</span>]] [[User talk:Spydar007|<span style="color:gray;">(Talk)</span>]]''' 20:42, 22 March 2017 (UTC)
::The rule was put into place is because the wiki has seen countless instances of "insignificant" edits (i.e. no major content, just adjustments like renaming "iPhone 4 GSM" to "iPhone3,1"), and there were a lot of complaints about this. We're not going down that road again. The main reason other wikis don't have a rule like this is probably because other wikis never deal with floods of edits just to rename one thing on such a frequent basis. On this wiki, a humongous change like this seems to happen every (other) year. (Why? This shouldn't be the case.) '''The rule stays''', but it's open for amendments— we can increase the limit count, for example. --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 21:16, 22 March 2017 (UTC)
:::I do think we should increase it. I'd propose either 75 or 100 daily edits and 30 major/minor (30 of each that is) per hour. Especially when we have a new firmware release, it is easy to go over 20 edits and if quick enough, could be done within an hour so I do think we should allow for more. I am with Spydar007 partly though as, although I can see why the rule was useful, we don't get enough editors to really cause an issue with this. If that changed, then we could review it. However, it isn't a make or break for me but I do think removing it would be a fairly good idea due to how few people edit this wiki now. I've also always thought that it would be better to fill Recent Changes on one day with big edits like that are currently taking place and then it be over, than do less edits that take a lot longer. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 10:22, 23 March 2017 (UTC)
::If that's the reason the rule was put in place, then it should ''definitely'' be removed. This rule does not prevent those edits from being made; it simply prevents the number of edits that can be made in a given time. With the same few editors, no one is going to be renaming "iPhone 4 GSM" to "iPhone3,1", or anything like that. And again, this rule doesn't prevent those edits from being made. I've never seen a large amount of these "insignificant" edits being made in any of the time I have had an account on this wiki. I'd say this is to do with the changing userbase of the wiki, and not anything else.
::If you ''absolutely'' insist that the rule is kept, then it should be changed to allow 50 edits per hour. No daily limits. This allows for plenty of cleanup to be made. Of course, if we start to see people making silly changes, then a nice message on the user's talk page usually suffices, and a general discussion about why the user feels that page or file should be changed or renamed, and not the creation of a rule to allow you to block the user. This rule was added (and from what I can see, with no discussion) on December 12, 2011‎. I can see no violations of this rule in silly page moves before this date. I simply do not see a need for this rule, and I feel like it hinders the amount of actually constructive edits to the wiki. — '''[[User:Spydar007|<span style="color:black;">Spydar007</span>]] [[User talk:Spydar007|<span style="color:gray;">(Talk)</span>]]''' 11:07, 23 March 2017 (UTC)
:::There absolutely was a [[The iPhone Wiki:Community portal/2011#New rule proposal|discussion]]. It's not meant to prevent these types of changes, as they can be necessary; it's meant to keep the list of changes accessible/readable, since an edit that's either questionable or notable (e.g. information about a new OTA package format) can easily be buried among 94 edits of merely renaming "iPod touch 4G" into "iPod touch (4th generation)." That said, taking the feedback into account, I think raising the limits to 50 major/50 minor edits per hour, with a daily limit of 150 edits would make a fair compromise. (Not having the daily limit would mean that you can actually make up all of the last 2,400 edits in one day. Uh… No.) --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 16:17, 23 March 2017 (UTC)
::::That limit would be awesome. I really like that idea of 50 major/50 minor edits per hour and 150 daily limit. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 16:35, 23 March 2017 (UTC)

----

Okay, I think Axi0mX's contributions highlighted something about this rule: if someone dumps a bunch useful information across numerous pages, it can very easily affect them. Contributions like these were not the intended target of the rule, and people shouldn't be punished for trying to share such information. However, we do need a system in place to limit insignificant changes— we do not, and should not, need to rename a key page every two years. I want to propose changing this to allow informative edits, such as the keys Axi0mX shared, while imposing a limit on inconsequential changes.

The following blurb reflects the changes I wish to make, and will be edited as suggestions are implemented. (Emphasis is added to highlight changes, and will not be part of the rule.)

<div style="background-color:#FFF; background-color:rgba(255,255,255,0.85); border:1px solid #AAA; padding:1em;">
<ins>From time to time, the format of pages on The iPhone Wiki may require changes. For example, we determined it was necessary to name device pages by their internal identifier (e.g. [[N72AP]]), and use the model identifier in firmware key pages (e.g. [[Sugar Bowl 5F138 (iPod2,1)]]). However,</ins> making <del>a lot of edits</del><ins>format changes like this</ins> causes the [[Special:RecentChanges|Recent changes]] to be filled up<ins>, as numerous pages must be edited or renamed to follow the new format</ins>. <del>In addition to annoying those that subscribe to the Recent changes feed (via Atom or Twitter), this hinders</del><ins>By filling the Recent changes feed with insignificant changes,</ins> everyone's ability to discover new information and track down any malicious <del>changes</del><ins>edits is unnecessarily hindered</ins>.

Therefore, for every hour (resetting at :00), you may only make <del>50 major edits and 50 minor edits. Do not abuse the ability to mark edits as minor to perform additional edits— if your non-minor edits look considerably similar to minor edits you made in the same hour (or vice-versa), this may be considered abuse</del><ins>up to 50 format changes</ins>. In addition, you may make no more than 150 edits <ins>pertaining to such format changes</ins> per day (resetting at midnight UTC). Any unused number of edits <ins>pertaining to format changes</ins> will ''not'' "roll over" to the next hour or day. <del>Avoid "clumping" your edits.</del><ins>Any such edits should not be "clumped" together.</ins> (e.g.- Do not make 45 edits <ins>for format changes</ins> at 01:58, and then another 45 at 02:01.) Temporary exemptions can be made at the discretion of administrators and/or the community. <ins>Enforcement of this rule is otherwise subject to the administrators' discretion.</ins>
</div>

This is a rough proposal, but I think this is going in the right direction. Are there any objections/suggestions? --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 02:11, 21 July 2017 (UTC)

:Sounds ok to me. I'd probably add firmware updates to the list of informative edits as they are pretty important. The only issue I can see with this is there will be a load of things not covered and could be confusing. I'm thinking maybe we could remove the rule altogether and if we get into an issue in future, add it back for certain things, such as key page template changes, although I hope we never do that again. If we must keep the rule, then I'd say keep it only for format changes. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 12:02, 21 July 2017 (UTC)

::Good point. Although I tried to provide examples of what should/should not be considered "informative," it can seem confusing. Considering that this rule was created pretty much solely because of the constant format changes, targeting those specifically should be fine. Unless someone has a second opinion, I'll revise the proposal tonight. (I don't have time right now to work on the text. I swear it's not because of Splatoon 2... Yet.) --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 16:13, 21 July 2017 (UTC)

== Wiki Logo Update 2017 ==
I think it's time we update the logo in the top left corner again. iPhone 4S and iOS 5 are so 2011. And that font definitely isn't San Francisco. I'll see if I can get something worked out. --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 05:48, 20 September 2017 (UTC)
:I believe Dialexio has already been working on this, see his Twitter for examples. — '''[[User:Spydar007|<span style="color:black;">Spydar007</span>]] [[User talk:Spydar007|<span style="color:gray;">(Talk)</span>]]''' 06:27, 20 September 2017 (UTC)
::Yup, I've been working on this for a few days now. As of now, [https://twitter.com/Dialexio/status/910260179463221249 this] is what I have so far. I was actually planning to make a topic about this today, but I guess I got beaten to the punch. :P --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 17:06, 20 September 2017 (UTC)
:::I was thinking something with iPhone X, too. But I think it should face the other way. Unless there's two phones back to back, having one face left looks weird IMHO. --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 21:41, 20 September 2017 (UTC)
::::I couldn't find any (clean) images from Apple that had the iPhone X facing right. I see no issue with the direction that the phone faces, though I suppose a right-facing one would've been a cleaner replacement for the current logo. --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 00:18, 21 September 2017 (UTC)
:::::On [https://apple.com/iphone/ apple.com/iphone], there's a big image of iPhone X: [https://images.apple.com/v/iphone/home/w/images/home/iphone_x_large.jpg iphone_x_large.jpg] (981x206). There's also [https://images.apple.com/media/us/iphone-x/2017/01df5b43-28e4-4848-bf20-490c34a926a7/overview/primary/design_corners/large.mp4 large.mp4] ([https://www.dropbox.com/s/v6ih5gf94m5f97y/080.bmp?dl=1 extracted image] - 1024x246). Would either of those work? --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 00:44, 21 September 2017 (UTC)
::::::Honestly, I think using a landscape iPhone would look even ''weirder'' than a portrait-oriented iPhone facing left. (There really isn't anything wrong with the latter.) Aside from taking or viewing photos/videos (...okay, games too, but those aren't exactly included from the get-go), iPhones aren't depicted in landscape. I did make an attempt to see what I can do with the first image, but when I tried resizing the first image to fit the logo's 150x150 size, I felt that it became somewhat difficult to identify as an iPhone. It almost looks like it's just a random bar of colors. Considering the dimensions for the second, I imagine that it would have a similar result. --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 03:28, 21 September 2017 (UTC)
:::::::Well you would rotate them 90° clockwise; I meant to specify that, but failed to do so. Anyways, considering the fact that iPhones have gotten bigger, there's not much we can do with only 150×150 pixels. In fact, [https://www.mediawiki.org/wiki/Manual:$wgLogo MediaWiki recommends no bigger than 135×135.] That documentation page does note, however, that we ''can'' use a bigger logo with some changes to the CSS. --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 00:51, 22 September 2017 (UTC)
::::::::Okay, I just tried rotating it, and I don't like the result at all— it seems off-center since the iPhone image is thinner. For both my version and the suggested swap, I made minor edits to the gradient color and switched to SF Text instead of SF Display. (I put together a comparison [https://imgur.com/a/fZXlU on imgur].) I'm sticking with the iPhone X image I originally used for my spin on a new logo. --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 03:56, 22 September 2017 (UTC)
:::::::::Well, the current logo has the iPhone at about the same angle as the second one. I think it only looks weird because it's too far to the left. I do prefer the angle of the first one (your original idea). However, I don't like the left facing direction; We do work in a left-to-right language. I do think, though, that a render of the lock screen is bad. Maybe I just prefer the current logo's use of the home screen because it adds color? I'm not particularly a fan of that wallpaper, but that's just me. I wonder if it would be possible to take all the 3D renders of iPhone X from Apple and build our own 3D model that could be positioned how we want it. I'll try that. In the meantime, I found this: [https://images.apple.com/v/iphone-x/b/images/overview/modal/design_expression_large.jpg design_expression_large.jpg] --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 23:15, 22 September 2017 (UTC)
::::::::::The left-to-right argument doesn't make sense to me; it's not like I wrote the words backwards or aligned it like it's a right-to-left language. Many Western brands do have an icon/glyph/whatever to the left of the text— Crunchyroll, Dropbox, Microsoft, Seagate, and YouTube all do that. (Of course, some brands like American Airlines and Chase have theirs on the right.) I don't think an image with the Lock screen is bad, but the wallpaper Apple chose for their iPhone X photos is rather... loud. The image I picked would probably look better if the colors weren't so bold. (Don't get me wrong though— I don't mind using a different iPhone X image or swapping the text and picture around, but I couldn't find any iPhone X images that look or fit better, except maybe a shot of the front without any perspective.) --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 03:21, 23 September 2017 (UTC)

== New rule proposal: Internal subjects ==
As we know, there are internal firmware builds that Apple uses to test their hardware. However, a wiki user reached out to me, concerned that there is incorrect information being added about these firmwares. I have no way to verify this information (and most probably don't either), so I would like to create a rule to require evidence in the form of an image or video for any substantial information about any such Apple internal subjects. This will help prevent false information being spread on the wiki.

<div style="background-color:#FFF; background-color:rgba(255,255,255,0.85); border:1px solid #AAA; padding:1em;">
Internal software and prototypes are rare to come across, and we welcome documentation about them. However, to maintain informational integrity, we do require evidence to be supplied with any substantial information that you have. For example, if you have a list of applications in an internal firmware, there should be an image or video showing them on the device. Any added information about internal subjects that does not comply with this is subject to removal, with account suspensions possible.
</div>

The above proposal will be edited as necessary during this discussion. --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 16:53, 22 October 2017 (UTC)

== Discussion of takedown for Cassandra Fuzzer ==
As you may know, the Cassandra Fuzzer, developed by [[Ih8ra1n|iH8Ra1n]] was taken down by [https://www.theiphonewiki.com/wiki/User:IAdam1n iAdam1n]. I ([[Ih8ra1n|iH8Ra1n]]) believe that Cassandra should not have been taken down for the following reasons:

* Information (If someone wants to help with it, for example. )

* Other vulnerabilities (Read on)

I think that I would be leaving people without some necessary information. Example, Cassandra discovers a vulnerability in MobileSafari. Now, I make a page about said vulnerability. I should probably mention Cassandra found it. Then, people wonder what it is. So, they look for a wiki page and find it was deleted. So, now they wonder what Cassandra is, and they don't know. This, I think, is a problem. Hence, why there should be a wiki page for it. {{unsigned|Ih8ra1n}}

With all due respect, the [[The_iPhone_Wiki:Ground_rules#Regarding_the_creation_of_pages_for_programs|ground rules]] specifically says that one should not create a page for a program that is upcoming. Moreover, it also states that the creator of a program should not be involved in its page's creation. I don't believe that Cassandra should be added to the wiki until it gains enough of a reputation independent of this place that someone else thinks to add it. [[User:Forestcorgi|Forestcorgi]] ([[User talk:Forestcorgi|talk]]) 00:41, 13 April 2018 (UTC)

NonUIConsoleViewer

2018-04-12T01:30:13Z

ForestCorgi: Fix first build and rewrite some things.

{{internal software}}
[[File:NonUIConsoleViewer Icon.png|thumb|right|NonUIConsoleViewer's Icon]]
[[File:NonUIConsoleViewer.png|thumb|right|Inside NonUIConsoleViewer]]

'''NonUIConsoleViewer''', which is presented simply as "Console" on [[SwitchBoard.app]], is an app that is shipped in later builds of SwitchBoard. Its first known appearance is in [[Sochi 11D31620l]]. The app shows the contents of <code>/private/var/mobile/log.txt</code>, as shown below, but as of yet there has not been an instance in which anything shows up. One theory is that it is intended to show the output of console execs such as [[SwitchBoard:_/usr/local/bin]]. The latest known build is 1.21.

This application is typically located under <code>/AppleInternal/Applications/SwitchBoard/NonUIConsoleViewer.app</code>.

== Contents of the app ==
Info.plist _CodeSignature
NonUIConsoleViewer _internal_terminal.png
PkgInfo com.apple.reliability.NonUIConsoleViewer.plist
ResourceRules.plist
[[Category:Apple Internal Apps]]

NonUIConsoleViewer

2018-04-12T01:18:33Z

ForestCorgi: Add missing comma.

{{internal software}}
[[File:NonUIConsoleViewer Icon.png|thumb|right|NonUIConsoleViewer's Icon]]
[[File:NonUIConsoleViewer.png|thumb|right|Inside NonUIConsoleViewer]]

'''NonUIConsoleViewer''', which is presented simply as "Console" on [[SwitchBoard.app]], is an app that is shipped in later builds of SwitchBoard and first made a 'public' appearance in the iPhone 6's that run SwitchBoard. This app presumably shows the output of "/private/var/mobile/log.txt" Which is shown in the view below, but as of yet there has not been an instance in which anything shows up. This could potentially show the output of console execs such as [[SwitchBoard:_/usr/local/bin]]. The latest build "publicly" known is 1.21.

This application is typically located under <code>/AppleInternal/Applications/SwitchBoard/NonUIConsoleViewer.app</code>.

== Contents of the app ==
Info.plist _CodeSignature
NonUIConsoleViewer _internal_terminal.png
PkgInfo com.apple.reliability.NonUIConsoleViewer.plist
ResourceRules.plist
[[Category:Apple Internal Apps]]

NonUIConsoleViewer

2018-04-12T01:17:45Z

ForestCorgi: Fix duplicated word.

{{internal software}}
[[File:NonUIConsoleViewer Icon.png|thumb|right|NonUIConsoleViewer's Icon]]
[[File:NonUIConsoleViewer.png|thumb|right|Inside NonUIConsoleViewer]]

'''NonUIConsoleViewer''', which is presented simply as "Console" on [[SwitchBoard.app]] is an app that is shipped in later builds of SwitchBoard and first made a 'public' appearance in the iPhone 6's that run SwitchBoard. This app presumably shows the output of "/private/var/mobile/log.txt" Which is shown in the view below, but as of yet there has not been an instance in which anything shows up. This could potentially show the output of console execs such as [[SwitchBoard:_/usr/local/bin]]. The latest build "publicly" known is 1.21.

This application is typically located under <code>/AppleInternal/Applications/SwitchBoard/NonUIConsoleViewer.app</code>.

== Contents of the app ==
Info.plist _CodeSignature
NonUIConsoleViewer _internal_terminal.png
PkgInfo com.apple.reliability.NonUIConsoleViewer.plist
ResourceRules.plist
[[Category:Apple Internal Apps]]

/private/var/db

2017-12-22T20:01:24Z

ForestCorgi: Fix another misspelling of "database"

This folder appears to hold databases used by system components, such as the [[wikipedia:tz database|tz database]] (<code>tzdata</code>) among other things.

== Children ==
=== Folders ===
* {{ipfw|astris}}
* {{ipfw|com.apple.xpc.launchd}}
* {{ipfw|dhcpclient}}
* {{ipfw|FIPS}}
* {{ipfw|fud}}
* {{ipfw|launchd.db}} ([[launchd]])
* {{ipfw|lsd}} ;)
* {{ipfw|PanicReporter}} (crash logs)
* {{ipfw|stash}} (jailbroken devices only)
* {{ipfw|timezone}} (tz database)
* {{ipfw|UpdateMetrics}}

=== Files ===
(none)

== Parents ==
{{parent|private|var}}

[[Category:Filesystem]]

/private/var/db

2017-12-22T20:00:25Z

ForestCorgi: Make Wikipedia link to timezone database work

This folder appears to hold databases used by system components, such as the [[wikipedia:tz database|tz database]] (<code>tzdata</code>) among other things.

== Children ==
=== Folders ===
* {{ipfw|astris}}
* {{ipfw|com.apple.xpc.launchd}}
* {{ipfw|dhcpclient}}
* {{ipfw|FIPS}}
* {{ipfw|fud}}
* {{ipfw|launchd.db}} ([[launchd]])
* {{ipfw|lsd}} ;)
* {{ipfw|PanicReporter}} (crash logs)
* {{ipfw|stash}} (jailbroken devices only)
* {{ipfw|timezone}} (tz databse)
* {{ipfw|UpdateMetrics}}

=== Files ===
(none)

== Parents ==
{{parent|private|var}}

[[Category:Filesystem]]

IMG4 File Format

2017-11-23T17:37:05Z

ForestCorgi: Fix anchor link

The '''IMG4 file format''' is a replacement for the [[IMG3 File Format|IMG3 file format]] and is used on devices running a 64-bit processor (A7 or newer) and the [[List of Apple Watches| Apple Watch series]]. Just like the old IMG3 file format, it is used to contain files used by iOS' secure boot chain ([[#IMG4_Payload|'''im4p''' files]]), signatures of those files (<code>ApImg4Ticket</code>) and likely some info used in the [[Restore_Process|Restore Process]] ("<code>IM4R</code>" can be found in MobileDevice framework). The only known place in iOS filesystem where a complete IMG4 file can be found is [[/usr/standalone/firmware/sep-firmware.img4]]. Extracting a PersonalizedBundle from /tmp during a restore will also yield complete IMG4 files. The embeddedOS images in the macOS filesystem for the 2016 MacBook Pros also have complete IMG4 files.

== Structure ==
Contrary to the [[IMG3 File Format|IMG3 file format]] where a custom binary format was used, IMG4 files (and their payloads) are [[wikipedia:X.690#DER encoding|DER]] encoded [[wikipedia:Abstract Syntax Notation One|ASN.1]] objects. The reason for Apple's choice of ASN.1/DER encoding over their own [[PList File Format|Property List]] (PList) file format is currently unknown.

<pre>
sequence [
0: string "IMG4"
1: payload - IMG4 Payload, IM4P
2: [0] (constructed) [
manifest - IMG4 Manifest, IM4M
]
]
</pre>

==IMG4 Payload==
Payload contains the actual content of the file. IMG4 format allows to store payload in a separate file with '''im4p''' extension. '''im4p''' files are used more often than complete IMG4 files. Payload is structured as follows:
<pre>
sequence [
0: string "IM4P"
1: string type - ibot, rdsk, sepi, ...
2: string description - 'iBoot-1940.1.75'
3: octetstring - the encrypted/raw data
4: octetstring - containing DER encoded KBAG values (optional)
sequence [
sequence [
0: int: 01
1: octetstring: iv
2: octetstring: key
]
sequence [
0: int: 02
1: octetstring: iv
2: octetstring: key
]
]
]
</pre>

==IMG4 Manifest==
A.k.a. IM4M. Contains signature for one or multiple IMG4 payloads. Manifests are designed in a way that they can be stored separately from an IMG4 file or be a part of one. An example of an IMG4 manifest is ApImg4Ticket. Each IMG4 manifest is made of tags structured as follows (content = DER encoded object):
<pre>
[type] (private) [ - DER tag's class is the type of the tag (4 bytes) encoded as a big-endian integer
sequence [
string type - type of the tag, 4 bytes
content - content of the tag
]
]
</pre>
Manifest structure (tag <type> = tag of type 'type'):
<pre>
sequence [
0: string "IM4M"
1: integer version - currently 0
2: set [
tag MANB [ - manifest body
set [
tag MANP [ - manifest properties
set [
tag <manifest property> [
content
]
... - tags, describing other properties
]
]
tag <type> [ - ibot, illb, sepi, krnl, NvMR, bbcl...
set [
tag <tag property> [
content
]
...
]
]
... - tags for other images
]
]
]
3: octet string signature
4: sequence [ - containing certificate chain (arbitrary number of certificates)
certificates
]
</pre>

== External Links ==
* [https://twitter.com/i0n1c/status/501299082603020288 i0n1c's tweet]
* [https://www.itu.int/rec/T-REC-X.690/en X.690 - ASN.1 encoding rules: Specification of Basic Encoding Rules (BER), Canonical Encoding Rules (CER) and Distinguished Encoding Rules (DER)]

[[Category:File Formats]]