https://www.theiphonewiki.com/w/api.php?action=feedcontributions&feedformat=atom&user=Danzatt 2026-06-09T11:56:35Z User contributions MediaWiki 1.31.14 https://www.theiphonewiki.com/w/index.php?title=LwVM&diff=46007 2015-06-12T16:11:33Z

<p>Danzatt: Ugh</p> <hr /> <div>'''LwVM''' (Lightweight Volume Manager) - partition table, which is used by iOS since 5.0.<br /> <br /> '''com.apple.driver.LightweightVolumeManager''' kext wraps the block device (&lt;code&gt;/dev/disk0&lt;/code&gt;) where the actual LwVM partition table is stored and publishes &lt;code&gt;/dev/disk0s1&lt;/code&gt; with emulated [[Wikipedia:GUID Partition Table|GPT]] which can be edited from user-land using conventional [[Wikipedia:GUID Partition Table|GPT]] editing tools (e.g. [http://sourceforge.net/projects/gptfdisk/ gptfdisk]) [https://code.google.com/p/iphone-dataprotection/wiki/LightweightVolumeManager]. All edits are trapped by the kext and before shutting down (after the volumes are unmounted) it writes the corresponding changes to LwVM partition table on &lt;code&gt;/dev/disk0&lt;/code&gt; (implemented in &lt;code&gt;LightweightVolumeManager::_gptLazyRepartition()&lt;/code&gt; function from the LwVM kext). After next boot new devices (e.g. &lt;code&gt;/dev/rdisk0s1s3&lt;/code&gt;) are published by the kext. This mechanism is used during [[OTA Updates]] to create third partition where the update ramdisk is copied to and booted into by setting nvram &lt;code&gt;boot-command&lt;/code&gt; to &lt;code&gt;upgrade&lt;/code&gt; [https://twitter.com/iH8sn0w/status/580016602512539648] and probably also &lt;code&gt;boot-partition&lt;/code&gt; to &lt;code&gt;2&lt;/code&gt; (partitions are indexed from 0, so third partition). <br /> <br /> The update partition is set up by &lt;code&gt;com.apple.MobileSoftwareUpdate.CleanupPreparePathService&lt;/code&gt; (XPC service accompanying [[softwareupdated]]). It shrinks HFS of the second (data) partition using &lt;code&gt;fsctl&lt;/code&gt; as illustrated in [https://github.com/danzatt/hfs_resize hfs_resize]. It then edits [[Wikipedia:GUID Partition Table|GPT]] on &lt;code&gt;/dev/rdisk0s1&lt;/code&gt; to reflect the size of shrunk HFS and creates new entry for the update partition in the freed space and creates new HFS on it. To create file-system manually you can use e.g.: &lt;code&gt;newfs_hfs -s -b 8192 -J 8192k -v Data2 /dev/rdisk0s1s4&lt;/code&gt;.<br /> <br /> == Structure ==<br /> &lt;pre&gt;<br /> typedef struct _LwVMPartitionRecord {<br /> uint64_t type[2]; //Should be equal to LwVMPartitionTypeHFS (see below) on an unmodified device.<br /> uint64_t guid[2]; //Random.<br /> uint64_t begin; //Partitions begin in bytes.<br /> uint64_t end; //End.<br /> uint64_t attribute; // 0 == unencrypted; 0x1000000000000 == encrypted<br /> uint16_t partitionName[0x24]; // UTF-16 encoded<br /> } __attribute__ ((packed)) LwVMPartitionRecord;<br /> <br /> typedef struct _LwVM {<br /> uint64_t type[2]; //Should be LwVMType or LwVMType_noCRC.<br /> uint64_t guid[2]; //Random.<br /> uint64_t mediaSize; //Size in bytes.<br /> uint32_t numPartitions; //Number of partitions.<br /> uint32_t crc32;<br /> uint8_t unkn[464]; //Some unknown bytes, usually nulls.<br /> LwVMPartitionRecord partitions[12];<br /> uint16_t chunks[1024]; // chunks[0] should be 0xF000<br /> } __attribute__ ((packed)) LwVM;<br /> <br /> static const char LwVMType[] = { 0x6A, 0x90, 0x88, 0xCF, 0x8A, 0xFD, 0x63, 0x0A, 0xE3, 0x51, 0xE2, 0x48, 0x87, 0xE0, 0xB9, 0x8B };<br /> <br /> static const char LwVMType_noCRC[] = { 0xB1, 0x89, 0xA5, 0x19, 0x4F, 0x59, 0x4B, 0x1D, 0xAD, 0x44, 0x1E, 0x12, 0x7A, 0xAF, 0x45, 0x39 };<br /> <br /> static const char LwVMPartitionTypeHFS[] = { 0x48, 0x46, 0x53, 0x00, 0x00, 0x00, 0x11, 0xAA, 0xAA, 0x11, 0x00, 0x30, 0x65, 0x43, 0xEC, 0xAC };<br /> &lt;/pre&gt;<br /> <br /> == LightweightVolumeManager IOService ==<br /> Running 'ioreg | grep &quot;Lightweight&quot;' shows, that there's an IOService with such name. [[User:rzhikharevich|I]] tried fuzzing IOConnectCallStructMethod selectors (very bad idea). The first call which returned KERN_SUCCESS was done with selector 1. Next, I tried this code:<br /> &lt;pre&gt;<br /> &lt;...&gt;<br /> kern_ret = IOConnectCallStructMethod(lwvm_conn, 1, NULL, 0, &amp;info_sz, &amp;o_sz);<br /> if (kern_ret == KERN_SUCCESS)<br /> {<br /> printf(&quot;OK.\n&quot;);<br /> void *info = malloc(info_sz);<br /> IOConnectCallStructMethod(lwvm_conn, 1, NULL, 0, info, &amp;info_sz);<br /> &lt;...&gt;<br /> &lt;/pre&gt;<br /> All disk read operations started resulting with errors. Then my device rebooted and entered a boot loop. The code possibly messed the partition table up.<br /> <br /> == Tools ==<br /> [http://www.github.com/rzhikharevich/lwvmedit lwvmedit]<br /> <br /> == External links ==<br /> [https://code.google.com/p/iphone-dataprotection/wiki/LightweightVolumeManager iPhone dataprotection wiki]</div>

Danzatt https://www.theiphonewiki.com/w/index.php?title=LwVM&diff=46004 2015-06-12T13:42:09Z

<p>Danzatt: </p> <hr /> <div>'''LwVM''' (Lightweight Volume Manager) - partition table, which is used by iOS since 5.0.<br /> <br /> '''com.apple.driver.LightweightVolumeManager''' kext wraps the block device (&lt;code&gt;/dev/disk0&lt;/code&gt;) where the actual LwVM partition table is stored and publishes &lt;code&gt;/dev/disk0s1&lt;/code&gt; with emulated [[Wikipedia:GUID Partition Table|GTP]] which can be edited from user-land using conventional [[Wikipedia:GUID Partition Table|GTP]] editing tools (e.g. [http://sourceforge.net/projects/gptfdisk/ gptfdisk]) [https://code.google.com/p/iphone-dataprotection/wiki/LightweightVolumeManager]. All edits are trapped by the kext and before shutting down (after the volumes are unmounted) it writes the corresponding changes to LwVM partition table on &lt;code&gt;/dev/disk0&lt;/code&gt; (implemented in &lt;code&gt;LightweightVolumeManager::_gptLazyRepartition()&lt;/code&gt; function from the LwVM kext). After next boot new devices (e.g. &lt;code&gt;/dev/rdisk0s1s3&lt;/code&gt;) are published by the kext. This mechanism is used during [[OTA Updates]] to create third partition where the update ramdisk is copied to and booted into by setting nvram &lt;code&gt;boot-command&lt;/code&gt; to &lt;code&gt;upgrade&lt;/code&gt; [https://twitter.com/iH8sn0w/status/580016602512539648] and probably also &lt;code&gt;boot-partition&lt;/code&gt; to &lt;code&gt;2&lt;/code&gt; (partitions are indexed from 0, so third partition). <br /> <br /> The update partition is set up by &lt;code&gt;com.apple.MobileSoftwareUpdate.CleanupPreparePathService&lt;/code&gt; (XPC service accompanying [[softwareupdated]]). It shrinks HFS of the second (data) partition using &lt;code&gt;fsctl&lt;/code&gt; as illustrated in [https://github.com/danzatt/hfs_resize hfs_resize]. It then edits [[Wikipedia:GUID Partition Table|GTP]] on &lt;code&gt;/dev/rdisk0s1s3&lt;/code&gt; to reflect the size of shrunk HFS and creates new entry for the update partition in the freed space and creates new HFS on it. To create file-system manually you can use e.g.: &lt;code&gt;newfs_hfs -s -b 8192 -J 8192k -v Data2 /dev/rdisk0s1s4&lt;/code&gt;.<br /> <br /> == Structure ==<br /> &lt;pre&gt;<br /> typedef struct _LwVMPartitionRecord {<br /> uint64_t type[2]; //Should be equal to LwVMPartitionTypeHFS (see below) on an unmodified device.<br /> uint64_t guid[2]; //Random.<br /> uint64_t begin; //Partitions begin in bytes.<br /> uint64_t end; //End.<br /> uint64_t attribute; // 0 == unencrypted; 0x1000000000000 == encrypted<br /> uint16_t partitionName[0x24]; // UTF-16 encoded<br /> } __attribute__ ((packed)) LwVMPartitionRecord;<br /> <br /> typedef struct _LwVM {<br /> uint64_t type[2]; //Should be LwVMType or LwVMType_noCRC.<br /> uint64_t guid[2]; //Random.<br /> uint64_t mediaSize; //Size in bytes.<br /> uint32_t numPartitions; //Number of partitions.<br /> uint32_t crc32;<br /> uint8_t unkn[464]; //Some unknown bytes, usually nulls.<br /> LwVMPartitionRecord partitions[12];<br /> uint16_t chunks[1024]; // chunks[0] should be 0xF000<br /> } __attribute__ ((packed)) LwVM;<br /> <br /> static const char LwVMType[] = { 0x6A, 0x90, 0x88, 0xCF, 0x8A, 0xFD, 0x63, 0x0A, 0xE3, 0x51, 0xE2, 0x48, 0x87, 0xE0, 0xB9, 0x8B };<br /> <br /> static const char LwVMType_noCRC[] = { 0xB1, 0x89, 0xA5, 0x19, 0x4F, 0x59, 0x4B, 0x1D, 0xAD, 0x44, 0x1E, 0x12, 0x7A, 0xAF, 0x45, 0x39 };<br /> <br /> static const char LwVMPartitionTypeHFS[] = { 0x48, 0x46, 0x53, 0x00, 0x00, 0x00, 0x11, 0xAA, 0xAA, 0x11, 0x00, 0x30, 0x65, 0x43, 0xEC, 0xAC };<br /> &lt;/pre&gt;<br /> <br /> == LightweightVolumeManager IOService ==<br /> Running 'ioreg | grep &quot;Lightweight&quot;' shows, that there's an IOService with such name. [[User:rzhikharevich|I]] tried fuzzing IOConnectCallStructMethod selectors (very bad idea). The first call which returned KERN_SUCCESS was done with selector 1. Next, I tried this code:<br /> &lt;pre&gt;<br /> &lt;...&gt;<br /> kern_ret = IOConnectCallStructMethod(lwvm_conn, 1, NULL, 0, &amp;info_sz, &amp;o_sz);<br /> if (kern_ret == KERN_SUCCESS)<br /> {<br /> printf(&quot;OK.\n&quot;);<br /> void *info = malloc(info_sz);<br /> IOConnectCallStructMethod(lwvm_conn, 1, NULL, 0, info, &amp;info_sz);<br /> &lt;...&gt;<br /> &lt;/pre&gt;<br /> All disk read operations started resulting with errors. Then my device rebooted and entered a boot loop. The code possibly messed the partition table up.<br /> <br /> == Tools ==<br /> [http://www.github.com/rzhikharevich/lwvmedit lwvmedit]<br /> <br /> == External links ==<br /> [https://code.google.com/p/iphone-dataprotection/wiki/LightweightVolumeManager iPhone dataprotection wiki]</div>

Danzatt https://www.theiphonewiki.com/w/index.php?title=LwVM&diff=46003 2015-06-12T13:33:42Z

<p>Danzatt: addded info on repartitioning + update partiton</p> <hr /> <div>'''LwVM''' (Lightweight Volume Manager) - partition table, which is used by iOS since 5.0.<br /> <br /> '''com.apple.driver.LightweightVolumeManager''' kext wraps the block device (&lt;code&gt;/dev/disk0&lt;/code&gt;) where the actual LwVM partition table is stored and publishes &lt;code&gt;/dev/disk0s1&lt;/code&gt; with emulated [[Wikipedia:GUID Partition Table|GTP]] which can be edited from user-land using conventional [[Wikipedia:GUID Partition Table|GTP]] editing tools (e.g. [http://sourceforge.net/projects/gptfdisk/ gptfdisk]) [https://code.google.com/p/iphone-dataprotection/wiki/LightweightVolumeManager]. All edits are trapped by the kext and before shutting down (after the volumes are unmounted) it writes the corresponding changes to LwVM partition table on &lt;code&gt;/dev/disk0&lt;/code&gt; (implemented in &lt;code&gt;LightweightVolumeManager::_gptLazyRepartition()&lt;/code&gt; function from the LwVM kext). After next boot new devices (e.g. &lt;code&gt;/dev/rdisk0s1s3&lt;/code&gt;) are published by the kext. This mechanism is used during [[OTA Updates]] to create third partition where the update ramdisk is copied to and booted into by setting nvram &lt;code&gt;boot-command&lt;/code&gt; to &lt;code&gt;upgrade&lt;/code&gt; [https://twitter.com/iH8sn0w/status/580016602512539648] and probably also &lt;code&gt;boot-partition&lt;/code&gt; to &lt;code&gt;2&lt;/code&gt; (partitions are indexed from 0, so third partition). <br /> <br /> The update partition is set up by &lt;code&gt;com.apple.MobileSoftwareUpdate.CleanupPreparePathService&lt;/code&gt; (XPC service accompanying [[softwareupdated]]). It shrinks HFS of the second (data) partition using &lt;code&gt;fsctl&lt;/code&gt; as illustrated in [https://github.com/danzatt/hfs_resize hfs_resize]. It then edits [[Wikipedia:GUID Partition Table|GTP]] on &lt;code&gt;/dev/rdisk0s1s3&lt;/code&gt; to reflect the size of shrunk HFS and creates new entry for the update partition in the freed space and creates new HFS on it. To create file-system manually you can use e.g.: &lt;code&gt;newfs_hfs -s -b 8192 -J 8192k -v Data2 /dev/rdisk0s1s4&lt;/code&gt;.<br /> <br /> == Structure ==<br /> &lt;pre&gt;<br /> typedef struct _LwVMPartitionRecord {<br /> uint64_t type[2]; //Should be equal to LwVMPartitionTypeHFS (see below) on an unmodified device.<br /> uint64_t guid[2]; //Random.<br /> uint64_t begin; //Partitions begin in bytes.<br /> uint64_t end; //End.<br /> uint64_t attribute; // 0 == unencrypted; 0x1000000000000 == encrypted<br /> uint16_t partitionName[0x24]; // UTF-16 encoded<br /> } __attribute__ ((packed)) LwVMPartitionRecord;<br /> <br /> typedef struct _LwVM {<br /> uint64_t type[2]; //Should be LwVMType or LwVMType_noCRC.<br /> uint64_t guid[2]; //Random.<br /> uint64_t mediaSize; //Size in bytes.<br /> uint32_t numPartitions; //Number of partitions.<br /> uint32_t crc32;<br /> uint8_t unkn[464]; //Some unknown bytes, usually nulls.<br /> LwVMPartitionRecord partitions[12];<br /> uint16_t chunks[1024]; // chunks[0] should be 0xF000<br /> } __attribute__ ((packed)) LwVM;<br /> <br /> static const char LwVMType[] = { 0x6A, 0x90, 0x88, 0xCF, 0x8A, 0xFD, 0x63, 0x0A, 0xE3, 0x51, 0xE2, 0x48, 0x87, 0xE0, 0xB9, 0x8B };<br /> <br /> static const char LwVMType_noCRC[] = { 0xB1, 0x89, 0xA5, 0x19, 0x4F, 0x59, 0x4B, 0x1D, 0xAD, 0x44, 0x1E, 0x12, 0x7A, 0xAF, 0x45, 0x39 };<br /> <br /> static const char LwVMPartitionTypeHFS[] = { 0x48, 0x46, 0x53, 0x00, 0x00, 0x00, 0x11, 0xAA, 0xAA, 0x11, 0x00, 0x30, 0x65, 0x43, 0xEC, 0xAC };<br /> &lt;/pre&gt;<br /> <br /> == LightweightVolumeManager IOService ==<br /> Running 'ioreg | grep &quot;Lightweight&quot;' shows, that there's an IOService with such name. [[User:rzhikharevich|I]] tried fuzzing IOConnectCallStructMethod selectors (very bad idea). The first call which returned KERN_SUCCESS was done with selector 1. Next, I tried this code:<br /> &lt;pre&gt;<br /> &lt;...&gt;<br /> kern_ret = IOConnectCallStructMethod(lwvm_conn, 1, NULL, 0, &amp;info_sz, &amp;o_sz);<br /> if (kern_ret == KERN_SUCCESS)<br /> {<br /> printf(&quot;OK.\n&quot;);<br /> void *info = malloc(info_sz);<br /> IOConnectCallStructMethod(lwvm_conn, 1, NULL, 0, info, &amp;info_sz);<br /> &lt;...&gt;<br /> &lt;/pre&gt;<br /> All disk read operations started resulting with errors. Then my device rebooted and entered a boot loop. The code possibly messed the partition table up.<br /> <br /> TODO: reverse that IOService, attempt to modify the partition table, add the information here.<br /> <br /> == Tools ==<br /> [http://www.github.com/rzhikharevich/lwvmedit lwvmedit]<br /> <br /> == External links ==<br /> [https://code.google.com/p/iphone-dataprotection/wiki/LightweightVolumeManager iPhone dataprotection wiki]</div>

Danzatt https://www.theiphonewiki.com/w/index.php?title=I0n1c&diff=45905 2015-05-31T16:32:11Z

<p>Danzatt: chronological + more</p> <hr /> <div>{{lowercase}}<br /> '''i0n1c''', whose real name is Stefan Esser, is a German security researcher. He developed [[Antid0te]], an [[wikipedia:Address space layout randomization|ASLR]] for jailbroken [[iPhone]]s in fall 2010, but never released it, because [[iOS]] since 4.3 includes an implementation of ASLR. He developed an untethering exploit for iOS 4.3. He gave a version of the exploit that worked on iOS 4.3.1 to the [[iPhone Dev Team]] which updated [[redsn0w]] and [[PwnageTool]] to use it and released the new tools on 4 April 2011. [[sn0wbreeze]] was also updated to include his untether. As the vulnerability went unpatched in iOS 4.3.2 and 4.3.3, he updated his code later to support those firmwares. An iOS 4.3-compatible version was never released. His exploit was used in [[Pangu]] jailbreak.<br /> <br /> On Apr 19, 2015 he released a YouTube video of a iOS 8.4 beta 1 jailbreak, he has said he will not release it to the public.<br /> ===Presentations===<br /> *[http://www.slideshare.net/i0n1c/syscan-2015-esserios678securityastudyinfail iOS 678 Security - A Study in Fail]<br /> *[http://www.slideshare.net/i0n1c/ruxcon-2014-stefan-esser-ios8-containers-sandboxes-and-entitlements Ruxcon 2014 - iOS8 Containers, Sandboxes and Entitlements]<br /> *[https://reverse.put.as/wp-content/uploads/2011/06/SyScan2012_StefanEsser_iOS_Kernel_Heap_Armageddon.pdf SyScan Singapore 2012: iOS Kernel Heap Armageddon (PDF)]<br /> *[http://antid0te.com/CSW2012_StefanEsser_iOS5_An_Exploitation_Nightmare_FINAL.pdf CanSecWest 2012: iOS5, an Exploitation Nightmare (PDF)]<br /> *[https://media.blackhat.com/bh-us-11/Esser/BH_US_11_Esser_Exploiting_The_iOS_Kernel_Slides.pdf BlackHat US 2011: Exploiting the iOS Kernel (PDF)]<br /> *[http://conference.hitb.org/hitbsecconf2011kul/materials/D2T1%20-%20Stefan%20Esser%20-%20iPhone%20Exploitation%20-%20One%20ROPe%20to%20Bind%20Them%20All.pdf HITB 2011 Malaysia: iPhone Exploitation - One ROPe to bind them all?]<br /> ===Links===<br /> *[https://twitter.com/i0n1c i0n1c on Twitter]<br /> *[http://www.suspekt.org Homepage]<br /> *[https://github.com/stefanesser GitHub]<br /> [[Category:Hackers]]<br /> [[Category:Security Researcher]]</div>

Danzatt https://www.theiphonewiki.com/w/index.php?title=Talk:IEmu&diff=44815 2015-03-05T18:02:09Z

<p>Danzatt: </p> <hr /> <div>Awesomebeing1, are you sure this fork works? The last time it tried to compile, it didn't work. The problem seemed to be incomplete code. --[[User:Rzhikharevich|Rzhikharevich]] ([[User talk:Rzhikharevich|talk]]) 06:23, 5 March 2015 (UTC)<br /> :I accidentally forked it as well, you can try it [https://github.com/danzatt/QEMU-s5l89xx-port danzatt/QEMU-s5l89xx-port] --[[User:Danzatt|Danzatt]] ([[User talk:Danzatt|talk]]) 17:41, 5 March 2015 (UTC)<br /> ::How do you &quot;accidentally&quot; fork a repo? --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 17:48, 5 March 2015 (UTC)<br /> :::I have probably wanted to star it and clicked fork instead.--[[User:Danzatt|Danzatt]] ([[User talk:Danzatt|talk]]) 18:02, 5 March 2015 (UTC)<br /> :What error did you get? If it matters, cmwdotme's port was last committed to on 30 August 2012, and winocm's fork (or cmwdotme's port) was last committed to on 3 January 2013. --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 17:48, 5 March 2015 (UTC)</div>

Danzatt https://www.theiphonewiki.com/w/index.php?title=Talk:IEmu&diff=44811 2015-03-05T17:42:07Z

<p>Danzatt: Oh</p> <hr /> <div>Awesomebeing1, are you sure this fork works? The last time it tried to compile, it didn't work. The problem seemed to be incomplete code. --[[User:Rzhikharevich|Rzhikharevich]] ([[User talk:Rzhikharevich|talk]]) 06:23, 5 March 2015 (UTC)<br /> ::I accidentally forked it as well, you can try it [https://github.com/danzatt/QEMU-s5l89xx-port QEMU-s5l89xx-port]--[[User:Danzatt|Danzatt]] ([[User talk:Danzatt|talk]]) 17:41, 5 March 2015 (UTC)</div>

Danzatt https://www.theiphonewiki.com/w/index.php?title=Talk:IEmu&diff=44810 2015-03-05T17:41:22Z

<p>Danzatt: </p> <hr /> <div>Awesomebeing1, are you sure this fork works? The last time it tried to compile, it didn't work. The problem seemed to be incomplete code. --[[User:Rzhikharevich|Rzhikharevich]] ([[User talk:Rzhikharevich|talk]]) 06:23, 5 March 2015 (UTC)<br /> ::I accidentaly forked it as well, you can try it [https://github.com/danzatt/QEMU-s5l89xx-port QEMU-s5l89xx-port]--[[User:Danzatt|Danzatt]] ([[User talk:Danzatt|talk]]) 17:41, 5 March 2015 (UTC)</div>

Danzatt https://www.theiphonewiki.com/w/index.php?title=Talk:Brick&diff=44569 2015-02-21T08:19:38Z

<p>Danzatt: </p> <hr /> <div>====Difficulty of bricking an iOS device====<br /> : &quot;(unless very specifically designed to do so by a malicious person, which has not been seen &quot;in the wild&quot;)&quot; --- Wasn't this seen here recently with the nvram hack that was discovered [http://www.reddit.com/r/jailbreak/comments/2w2pzz/a_proof_of_concept_that_tweaks_can_permanently/ here]?? Given it hasn't been used in an actual tweak or a package yet... [[User:Mwoolweaver|MWoolweaver]] ([[User talk:Mwoolweaver|talk]]) 16:28, 19 February 2015 (UTC)<br /> <br /> ::What I meant by this sentence is that nobody has deployed this method maliciously/intentionally in a package on any repository that I've heard of - they have all so far been clearly marked as dangerous &quot;proof of concept&quot; packages/instructions, not meant to trick you. In other words, it's not &quot;in the wild&quot; as a malicious tweak that people might randomly run into right now. I'd welcome revising this sentence with alternate phrasing that makes this more clear. [[User:Britta|Britta]] ([[User talk:Britta|talk]]) 05:07, 20 February 2015 (UTC)<br /> <br /> Maybe we could advise people to delete/rename nvram binary (e.g. mv /usr/sbin/nvram /usr/sbin/nvram.disabled) so that potentially malicious tweaks can't use it (it's easy to bypass by supplying another copy of nvram with the tweak though).--[[User:Danzatt|Danzatt]] ([[User talk:Danzatt|talk]]) 08:19, 21 February 2015 (UTC)</div>

Danzatt https://www.theiphonewiki.com/w/index.php?title=Jailbreak_Exploits&diff=44517 2015-02-10T14:24:50Z

<p>Danzatt: /* TaiG and PPJailbreak (8.0 / 8.0.1 / 8.0.2 / 8.1 / 8.1.1 / 8.1.2) */</p> <hr /> <div>This page lists the '''exploits''' used in [[jailbreak]]s.<br /> <br /> == Common exploits which are used in order to jailbreak different versions of iOS ==<br /> * [[Pwnage]] + [[Pwnage 2.0]] (together to jailbreak the [[n82ap|iPhone 3G]])<br /> * [[ARM7 Go]] (from iOS 2.1.1) (for [[tethered jailbreak]] on [[n72ap|iPod touch 2G]])<br /> * [[0x24000 Segment Overflow]] (for [[untethered jailbreak]] on [[n88ap|iPhone 3GS]] with [[Bootrom 359.3|old bootrom]] and [[n72ap|iPod touch 2G]] with [[Bootrom 240.4|old bootrom]]; another exploit as the [[limera1n Exploit]] is required)<br /> * [[limera1n Exploit]] (for [[tethered jailbreak]] on [[n88ap|iPhone 3GS]], [[n18ap|iPod touch 3G]], [[k48ap|iPad]], [[iPhone 4]], [[n81ap|iPod touch 4G]] and [[k66ap|Apple TV 2G]])<br /> * [[usb_control_msg(0xA1, 1) Exploit]] (also known as &quot;steaks4uce&quot;) (for [[tethered jailbreak]] on [[n72ap|iPod touch 2G]])<br /> <br /> == Programs which are used in order to jailbreak different versions of iOS ==<br /> === [[PwnageTool]] (2.0 - 5.1.1) ===<br /> * uses different common exploits<br /> * uses the exploits listed below to untether up to iOS 5.1.1<br /> <br /> === [[redsn0w]] (3.0 - 6.0) ===<br /> * uses different common exploits<br /> * uses the same exploits as [[Absinthe|Absinthe]] and [[Absinthe|Absinthe 2.0]] to jailbreak iOS 5.0/5.0.1 and 5.1.1<br /> * uses the exploits listed below to untether up to iOS 5.1.1<br /> <br /> === [[sn0wbreeze]] (3.1.3 - 6.1.3) ===<br /> * uses different common exploits<br /> * uses the exploits listed below to untether up to iOS 6.1.2<br /> <br /> == Programs which are used in order to jailbreak 1.x ==<br /> === [[AppTapp Installer]] (1.0 / 1.0.1 / 1.0.2) ===<br /> * iBoot &lt;code&gt;cp&lt;/code&gt;-command exploit<br /> <br /> === [[iBrickr]] (1.0 / 1.0.1 / 1.0.2) ===<br /> * iBoot &lt;code&gt;cp&lt;/code&gt;-command exploit<br /> <br /> === [[AppSnapp]]/[[JailbreakMe|JailbreakMe 1.0]] (1.0 / 1.0.1 / 1.0.2 / 1.1.1) ===<br /> * [[LibTiff|libtiff exploit]] (Adapted from the PSP scene, used by [[JailbreakMe]]) ({{cve|2006-3459}})<br /> <br /> === [[mknod|OktoPrep]] (1.1.2) ===<br /> &quot;Upgrade&quot; to 1.1.2 from a jailborken 1.1.1<br /> * [[mknod]]<br /> <br /> === [[Soft Upgrade]] (1.1.3) ===<br /> &quot;Upgrade&quot; to 1.1.3 from a running jailbroken 1.1.2<br /> <br /> === [[ZiPhone]] (1.1.3 / 1.1.4 /1.1.5) ===<br /> * [[Ramdisk Hack]]<br /> <br /> === [[iLiberty+|iLiberty / iLiberty+]] (1.1.3 / 1.1.4 /1.1.5) ===<br /> <br /> == Programs which are used in order to jailbreak 2.x ==<br /> === [[QuickPwn]] (2.0 - 2.2.1) ===<br /> * uses [[Pwnage]] and [[Pwnage 2.0]]<br /> <br /> === [[Redsn0w Lite]] (2.1.1) ===<br /> * [[ARM7 Go]] (for [[n72ap|iPod touch 2G]] only)<br /> <br /> == Programs which are used in order to jailbreak 3.x ==<br /> === [[purplera1n]] (3.0) ===<br /> * [[iBoot Environment Variable Overflow]] ({{cve|2009-2795}})<br /> * uses [[0x24000 Segment Overflow]]<br /> <br /> === [[blackra1n]] (3.1.2) ===<br /> * [[usb_control_msg(0x21, 2) Exploit]] ({{cve|2010-0038}})<br /> * uses [[0x24000 Segment Overflow]]<br /> <br /> === [[Spirit]] (3.1.2 / 3.1.3 / 3.2) ===<br /> * [[MobileBackup Copy Exploit]]<br /> * [[Incomplete Codesign Exploit]]<br /> * [[BPF_STX Kernel Write Exploit]]<br /> <br /> === [[Star|JailbreakMe 2.0 / Star]] (3.1.2 / 3.1.3 / 3.2 / 3.2.1) ===<br /> * [[Malformed CFF Vulnerability]] ({{cve|2010-1797}})<br /> * [[Incomplete Codesign Exploit]]<br /> * [[IOSurface Kernel Exploit]] ({{cve|2010-2973}})<br /> <br /> === [[limera1n]] / [[greenpois0n (jailbreak)|greenpois0n]] (3.2.2) ===<br /> * uses different common exploits<br /> * [[Packet Filter Kernel Exploit]]<br /> <br /> == Programs which are used in order to jailbreak 4.x ==<br /> === [[Star|JailbreakMe 2.0 / Star]] (4.0 / 4.0.1) ===<br /> * [[Malformed CFF Vulnerability]] ({{cve|2010-1797}})<br /> * [[Incomplete Codesign Exploit]]<br /> * [[IOSurface Kernel Exploit]] ({{cve|2010-2973}})<br /> <br /> === [[limera1n]] / (4.0 / 4.0.1 / 4.0.2 / 4.1) ===<br /> * uses different common exploits<br /> * [[Packet Filter Kernel Exploit]]<br /> <br /> === [[greenpois0n (jailbreak)|greenpois0n]] (4.1) ===<br /> * uses different common exploits<br /> * [[Packet Filter Kernel Exploit]]<br /> <br /> === [[greenpois0n (jailbreak)|greenpois0n]] (4.2.1) ===<br /> * uses different common exploits<br /> * [[HFS Legacy Volume Name Stack Buffer Overflow]]<br /> <br /> === [[Saffron|JailbreakMe 3.0 / Saffron]] (4.2.6 / 4.2.7 / 4.2.8) ===<br /> * [[T1 Font Integer Overflow]] ({{cve|2011-0226}})<br /> * [[HFS Legacy Volume Name Stack Buffer Overflow]]<br /> <br /> === [[Saffron|JailbreakMe 3.0 / Saffron]] (4.3 / 4.3.1 / 4.3.2 / 4.3.3) ===<br /> Except for the [[n18ap|iPod touch 3G]] on iOS 4.3.1.<br /> * [[T1 Font Integer Overflow]] ({{cve|2011-0226}})<br /> * [[IOMobileFrameBuffer Privilege Escalation Exploit]] ({{cve|2011-0227}})<br /> <br /> === i0nic's Untether (4.3.1 / 4.3.2 / 4.3.3) ===<br /> used in [[redsn0w]] to untether iOS 4.3.1 / 4.3.2 / 4.3.3<br /> * [[ndrv_setspec() Integer Overflow]]<br /> <br /> == Programs which are used in order to jailbreak 5.x ==<br /> === [[unthredera1n]] (5.0 / 5.0.1 / 5.1 / 5.1.1) ===<br /> Except for the [[iPad 3]]<br /> * MobileBackup2 Copy Exploit<br /> * a new Packet Filter Kernel Exploit ({{cve|2012-3728}})<br /> * [[AMFID code signing evasion]] ({{cve|2013-0977}})<br /> * [[launchd.conf untether]]<br /> * [[Timezone Vulnerability]]<br /> <br /> === [[Absinthe]] (5.0 on [[n94ap|iPhone 4S]] only / 5.0.1 on [[iPad 2]] and [[iPhone 4S]]) ===<br /> * [[Racoon String Format Overflow Exploit]] ({{cve|2012-0646}}) (used both for payload injection and untether)<br /> * [[HFS Heap Overflow]] ({{cve|2012-0642}})<br /> * unknown exploit ({{cve|2012-0643}})<br /> <br /> === [[Corona|Corona Untether]] (5.0.1) ===<br /> * [[Racoon String Format Overflow Exploit]] ({{cve|2012-0646}})<br /> * [[HFS Heap Overflow]] ({{cve|2012-0642}})<br /> * unknown exploit ({{cve|2012-0643}})<br /> <br /> === [[Absinthe|Absinthe 2.0]] and [[Rocky Racoon|Rocky Racoon Untether]] (5.1.1) ===<br /> * a new Packet Filter Kernel Exploit ({{cve|2012-3728}})<br /> * Racoon DNS4/WINS4 table buffer overflow ({{cve|2012-3727}})<br /> * MobileBackup2 Copy Exploit<br /> <br /> == Programs which are used in order to jailbreak 6.x ==<br /> === [[evasi0n]] (6.0 / 6.0.1 / 6.0.2 / 6.1 / 6.1.1 / 6.1.2) ===<br /> * [[Symbolic Link Vulnerability]] ({{cve|2013-0979}})<br /> * [[Timezone Vulnerability]]<br /> * [[Shebang Trick]] ({{cve|2013-5154}})<br /> * [[AMFID code signing evasion]]<br /> * [[launchd.conf untether]]<br /> * [[IOUSBDeviceFamily Vulnerability]] ({{cve|2013-0981}})<br /> * [[ARM Exception Vector Info Leak]] ({{cve|2013-0978}})<br /> * [[dynamic memmove() locating]]<br /> * [[vm_map_copy_t corruption for arbitrary memory disclosure]]<br /> * [[kernel memory write via ROP gadget]]<br /> * [[Overlapping Segment Attack]] ({{cve|2013-0977}})<br /> <br /> === [[p0sixspwn]] (6.1.3 / 6.1.4 / 6.1.5 / 6.1.6) ===<br /> * [[posix_spawn kernel information leak]] ({{cve|2013-3954}}) (by [[i0n1c]])<br /> * [[posix_spawn kernel exploit]] ({{cve|2013-3954}}) (by [[i0n1c]])<br /> * [[mach_msg_ool_descriptor_ts for heap shaping]] ({{cve|2013-3953}})<br /> * [[AMFID_code_signing_evasi0n7]] ({{cve|2014-1273}})<br /> * [[DeveloperDiskImage race condition]] (by [[comex]])<br /> * [[launchd.conf untether]]<br /> <br /> == Programs which are used in order to jailbreak 7.x ==<br /> === [[evasi0n7]] (7.0 / 7.0.1 / 7.0.2 / 7.0.3 / 7.0.4 / 7.0.5 / 7.0.6) ===<br /> {{Section Stub}}<br /> * [[Symbolic Link Vulnerability]] ({{cve|2013-5133}})<br /> * [[AMFID_code_signing_evasi0n7]] ({{cve|2014-1273}})<br /> * CrashHouseKeeping chmod vulnarability ({{cve|2014-1272}})<br /> * ptmx_get_ioctl ioctl crafted call ({{cve|2014-1278}})<br /> <br /> === [[Geeksn0w]] (7.1 / 7.1.1 / 7.1.2) ===<br /> * [[limera1n]]'s bootrom exploit ([[Tethered jailbreak]]) on [[iPhone 4]]<br /> <br /> === [[Pangu]] (7.1 / 7.1.1 / 7.1.2) ===<br /> * [[i0n1c]]'s Infoleak vulnerability (Pangu v1.0.0)<br /> * break_early_random (by [[i0n1c]] and Tarjei Mandt of Azimuth) (Pangu v1.1.0)<br /> * LightSensor / ProxALSSensor kernel exploit (Pangu 1.0.0) ({{cve|2014-4388}})<br /> * TempSensor kernel exploit (Pangu 1.1.0) ({{cve|2014-4388}})<br /> * &quot;syslogd chown&quot; vulnerability<br /> * enterprise certificate (no real exploit, used for initial &quot;unsigned&quot; code execution)<br /> * &quot;foo_extracted&quot; symlink vulnerability (used to write to /var) ({{cve|2014-4386}})<br /> * /tmp/bigfile (a big file for improvement of the reliability of a race condition)<br /> * VoIP backgrounding trick (used to auto restart the app)<br /> * hidden segment attack<br /> * IOKit crafted call maker utility ({{cve|2014-4407}})<br /> <br /> == Programs which are used in order to jailbreak 8.x ==<br /> === [[Pangu8]] (8.0 / 8.0.1 / 8.0.2 / 8.1) ===<br /> * an exploit for a bug in /usr/libexec/neagent (source @iH8sn0w)<br /> * enterprise certificate (inside the IPA)<br /> * a kind of dylib injection into a system process (see IPA)<br /> * a dmg mount command (looks like the Developer DMG) (syslog while jailbreaking)<br /> * a sandboxing problem in debugserver ({{cve|2014-4457}})<br /> * the same/a similar kernel exploit as used in [[Pangu|the first Pangu]] ({{cve|2014-4461}}) (source @iH8sn0w)<br /> * enable-dylibs-to-override-cache<br /> * a new ovelapping segment attack ({{cve|2014-4455}})<br /> * i0n1c's Kernel info leak ({{cve|2014-4491}})<br /> <br /> === [[TaiG]] and [[PPJailbreak]] (8.0 / 8.0.1 / 8.0.2 / 8.1 / 8.1.1 / 8.1.2) ===<br /> (See also details at [http://newosxbook.com/articles/TaiG.html newosxbook.com])<br /> * LightSensor / ProxALSSensor kernel exploit (Also used in Pangu 1.0.0)<br /> * [[DeveloperDiskImage race condition]] (by [[comex]]) (source: https://twitter.com/iH8sn0w/status/538602532088860672; also used in p0sixspwn)<br /> * enable-dylibs-to-override-cache (Also used in Pangu8)<br /> * a kind of dylib injection into a system process (see IPA) (Also used in Pangu8 but tweaked slightly)<br /> * a new ovelapping segment attack [in a modified version] ({{cve|2014-4455}})<br /> * a new afc symlink attack ({{cve|2014-4480}})<br /> * mach_ports info leak kernel exploit ({{cve|2014-4496}})<br /> * IOHIDFamily Kernel exploit ({{cve|2014-4487}})</div>

Danzatt https://www.theiphonewiki.com/w/index.php?title=Jailbreak_Exploits&diff=44516 2015-02-10T14:24:22Z

<p>Danzatt: /* TaiG and PPJailbreak (8.0 / 8.0.1 / 8.0.2 / 8.1 / 8.1.1 / 8.1.2) */</p> <hr /> <div>This page lists the '''exploits''' used in [[jailbreak]]s.<br /> <br /> == Common exploits which are used in order to jailbreak different versions of iOS ==<br /> * [[Pwnage]] + [[Pwnage 2.0]] (together to jailbreak the [[n82ap|iPhone 3G]])<br /> * [[ARM7 Go]] (from iOS 2.1.1) (for [[tethered jailbreak]] on [[n72ap|iPod touch 2G]])<br /> * [[0x24000 Segment Overflow]] (for [[untethered jailbreak]] on [[n88ap|iPhone 3GS]] with [[Bootrom 359.3|old bootrom]] and [[n72ap|iPod touch 2G]] with [[Bootrom 240.4|old bootrom]]; another exploit as the [[limera1n Exploit]] is required)<br /> * [[limera1n Exploit]] (for [[tethered jailbreak]] on [[n88ap|iPhone 3GS]], [[n18ap|iPod touch 3G]], [[k48ap|iPad]], [[iPhone 4]], [[n81ap|iPod touch 4G]] and [[k66ap|Apple TV 2G]])<br /> * [[usb_control_msg(0xA1, 1) Exploit]] (also known as &quot;steaks4uce&quot;) (for [[tethered jailbreak]] on [[n72ap|iPod touch 2G]])<br /> <br /> == Programs which are used in order to jailbreak different versions of iOS ==<br /> === [[PwnageTool]] (2.0 - 5.1.1) ===<br /> * uses different common exploits<br /> * uses the exploits listed below to untether up to iOS 5.1.1<br /> <br /> === [[redsn0w]] (3.0 - 6.0) ===<br /> * uses different common exploits<br /> * uses the same exploits as [[Absinthe|Absinthe]] and [[Absinthe|Absinthe 2.0]] to jailbreak iOS 5.0/5.0.1 and 5.1.1<br /> * uses the exploits listed below to untether up to iOS 5.1.1<br /> <br /> === [[sn0wbreeze]] (3.1.3 - 6.1.3) ===<br /> * uses different common exploits<br /> * uses the exploits listed below to untether up to iOS 6.1.2<br /> <br /> == Programs which are used in order to jailbreak 1.x ==<br /> === [[AppTapp Installer]] (1.0 / 1.0.1 / 1.0.2) ===<br /> * iBoot &lt;code&gt;cp&lt;/code&gt;-command exploit<br /> <br /> === [[iBrickr]] (1.0 / 1.0.1 / 1.0.2) ===<br /> * iBoot &lt;code&gt;cp&lt;/code&gt;-command exploit<br /> <br /> === [[AppSnapp]]/[[JailbreakMe|JailbreakMe 1.0]] (1.0 / 1.0.1 / 1.0.2 / 1.1.1) ===<br /> * [[LibTiff|libtiff exploit]] (Adapted from the PSP scene, used by [[JailbreakMe]]) ({{cve|2006-3459}})<br /> <br /> === [[mknod|OktoPrep]] (1.1.2) ===<br /> &quot;Upgrade&quot; to 1.1.2 from a jailborken 1.1.1<br /> * [[mknod]]<br /> <br /> === [[Soft Upgrade]] (1.1.3) ===<br /> &quot;Upgrade&quot; to 1.1.3 from a running jailbroken 1.1.2<br /> <br /> === [[ZiPhone]] (1.1.3 / 1.1.4 /1.1.5) ===<br /> * [[Ramdisk Hack]]<br /> <br /> === [[iLiberty+|iLiberty / iLiberty+]] (1.1.3 / 1.1.4 /1.1.5) ===<br /> <br /> == Programs which are used in order to jailbreak 2.x ==<br /> === [[QuickPwn]] (2.0 - 2.2.1) ===<br /> * uses [[Pwnage]] and [[Pwnage 2.0]]<br /> <br /> === [[Redsn0w Lite]] (2.1.1) ===<br /> * [[ARM7 Go]] (for [[n72ap|iPod touch 2G]] only)<br /> <br /> == Programs which are used in order to jailbreak 3.x ==<br /> === [[purplera1n]] (3.0) ===<br /> * [[iBoot Environment Variable Overflow]] ({{cve|2009-2795}})<br /> * uses [[0x24000 Segment Overflow]]<br /> <br /> === [[blackra1n]] (3.1.2) ===<br /> * [[usb_control_msg(0x21, 2) Exploit]] ({{cve|2010-0038}})<br /> * uses [[0x24000 Segment Overflow]]<br /> <br /> === [[Spirit]] (3.1.2 / 3.1.3 / 3.2) ===<br /> * [[MobileBackup Copy Exploit]]<br /> * [[Incomplete Codesign Exploit]]<br /> * [[BPF_STX Kernel Write Exploit]]<br /> <br /> === [[Star|JailbreakMe 2.0 / Star]] (3.1.2 / 3.1.3 / 3.2 / 3.2.1) ===<br /> * [[Malformed CFF Vulnerability]] ({{cve|2010-1797}})<br /> * [[Incomplete Codesign Exploit]]<br /> * [[IOSurface Kernel Exploit]] ({{cve|2010-2973}})<br /> <br /> === [[limera1n]] / [[greenpois0n (jailbreak)|greenpois0n]] (3.2.2) ===<br /> * uses different common exploits<br /> * [[Packet Filter Kernel Exploit]]<br /> <br /> == Programs which are used in order to jailbreak 4.x ==<br /> === [[Star|JailbreakMe 2.0 / Star]] (4.0 / 4.0.1) ===<br /> * [[Malformed CFF Vulnerability]] ({{cve|2010-1797}})<br /> * [[Incomplete Codesign Exploit]]<br /> * [[IOSurface Kernel Exploit]] ({{cve|2010-2973}})<br /> <br /> === [[limera1n]] / (4.0 / 4.0.1 / 4.0.2 / 4.1) ===<br /> * uses different common exploits<br /> * [[Packet Filter Kernel Exploit]]<br /> <br /> === [[greenpois0n (jailbreak)|greenpois0n]] (4.1) ===<br /> * uses different common exploits<br /> * [[Packet Filter Kernel Exploit]]<br /> <br /> === [[greenpois0n (jailbreak)|greenpois0n]] (4.2.1) ===<br /> * uses different common exploits<br /> * [[HFS Legacy Volume Name Stack Buffer Overflow]]<br /> <br /> === [[Saffron|JailbreakMe 3.0 / Saffron]] (4.2.6 / 4.2.7 / 4.2.8) ===<br /> * [[T1 Font Integer Overflow]] ({{cve|2011-0226}})<br /> * [[HFS Legacy Volume Name Stack Buffer Overflow]]<br /> <br /> === [[Saffron|JailbreakMe 3.0 / Saffron]] (4.3 / 4.3.1 / 4.3.2 / 4.3.3) ===<br /> Except for the [[n18ap|iPod touch 3G]] on iOS 4.3.1.<br /> * [[T1 Font Integer Overflow]] ({{cve|2011-0226}})<br /> * [[IOMobileFrameBuffer Privilege Escalation Exploit]] ({{cve|2011-0227}})<br /> <br /> === i0nic's Untether (4.3.1 / 4.3.2 / 4.3.3) ===<br /> used in [[redsn0w]] to untether iOS 4.3.1 / 4.3.2 / 4.3.3<br /> * [[ndrv_setspec() Integer Overflow]]<br /> <br /> == Programs which are used in order to jailbreak 5.x ==<br /> === [[unthredera1n]] (5.0 / 5.0.1 / 5.1 / 5.1.1) ===<br /> Except for the [[iPad 3]]<br /> * MobileBackup2 Copy Exploit<br /> * a new Packet Filter Kernel Exploit ({{cve|2012-3728}})<br /> * [[AMFID code signing evasion]] ({{cve|2013-0977}})<br /> * [[launchd.conf untether]]<br /> * [[Timezone Vulnerability]]<br /> <br /> === [[Absinthe]] (5.0 on [[n94ap|iPhone 4S]] only / 5.0.1 on [[iPad 2]] and [[iPhone 4S]]) ===<br /> * [[Racoon String Format Overflow Exploit]] ({{cve|2012-0646}}) (used both for payload injection and untether)<br /> * [[HFS Heap Overflow]] ({{cve|2012-0642}})<br /> * unknown exploit ({{cve|2012-0643}})<br /> <br /> === [[Corona|Corona Untether]] (5.0.1) ===<br /> * [[Racoon String Format Overflow Exploit]] ({{cve|2012-0646}})<br /> * [[HFS Heap Overflow]] ({{cve|2012-0642}})<br /> * unknown exploit ({{cve|2012-0643}})<br /> <br /> === [[Absinthe|Absinthe 2.0]] and [[Rocky Racoon|Rocky Racoon Untether]] (5.1.1) ===<br /> * a new Packet Filter Kernel Exploit ({{cve|2012-3728}})<br /> * Racoon DNS4/WINS4 table buffer overflow ({{cve|2012-3727}})<br /> * MobileBackup2 Copy Exploit<br /> <br /> == Programs which are used in order to jailbreak 6.x ==<br /> === [[evasi0n]] (6.0 / 6.0.1 / 6.0.2 / 6.1 / 6.1.1 / 6.1.2) ===<br /> * [[Symbolic Link Vulnerability]] ({{cve|2013-0979}})<br /> * [[Timezone Vulnerability]]<br /> * [[Shebang Trick]] ({{cve|2013-5154}})<br /> * [[AMFID code signing evasion]]<br /> * [[launchd.conf untether]]<br /> * [[IOUSBDeviceFamily Vulnerability]] ({{cve|2013-0981}})<br /> * [[ARM Exception Vector Info Leak]] ({{cve|2013-0978}})<br /> * [[dynamic memmove() locating]]<br /> * [[vm_map_copy_t corruption for arbitrary memory disclosure]]<br /> * [[kernel memory write via ROP gadget]]<br /> * [[Overlapping Segment Attack]] ({{cve|2013-0977}})<br /> <br /> === [[p0sixspwn]] (6.1.3 / 6.1.4 / 6.1.5 / 6.1.6) ===<br /> * [[posix_spawn kernel information leak]] ({{cve|2013-3954}}) (by [[i0n1c]])<br /> * [[posix_spawn kernel exploit]] ({{cve|2013-3954}}) (by [[i0n1c]])<br /> * [[mach_msg_ool_descriptor_ts for heap shaping]] ({{cve|2013-3953}})<br /> * [[AMFID_code_signing_evasi0n7]] ({{cve|2014-1273}})<br /> * [[DeveloperDiskImage race condition]] (by [[comex]])<br /> * [[launchd.conf untether]]<br /> <br /> == Programs which are used in order to jailbreak 7.x ==<br /> === [[evasi0n7]] (7.0 / 7.0.1 / 7.0.2 / 7.0.3 / 7.0.4 / 7.0.5 / 7.0.6) ===<br /> {{Section Stub}}<br /> * [[Symbolic Link Vulnerability]] ({{cve|2013-5133}})<br /> * [[AMFID_code_signing_evasi0n7]] ({{cve|2014-1273}})<br /> * CrashHouseKeeping chmod vulnarability ({{cve|2014-1272}})<br /> * ptmx_get_ioctl ioctl crafted call ({{cve|2014-1278}})<br /> <br /> === [[Geeksn0w]] (7.1 / 7.1.1 / 7.1.2) ===<br /> * [[limera1n]]'s bootrom exploit ([[Tethered jailbreak]]) on [[iPhone 4]]<br /> <br /> === [[Pangu]] (7.1 / 7.1.1 / 7.1.2) ===<br /> * [[i0n1c]]'s Infoleak vulnerability (Pangu v1.0.0)<br /> * break_early_random (by [[i0n1c]] and Tarjei Mandt of Azimuth) (Pangu v1.1.0)<br /> * LightSensor / ProxALSSensor kernel exploit (Pangu 1.0.0) ({{cve|2014-4388}})<br /> * TempSensor kernel exploit (Pangu 1.1.0) ({{cve|2014-4388}})<br /> * &quot;syslogd chown&quot; vulnerability<br /> * enterprise certificate (no real exploit, used for initial &quot;unsigned&quot; code execution)<br /> * &quot;foo_extracted&quot; symlink vulnerability (used to write to /var) ({{cve|2014-4386}})<br /> * /tmp/bigfile (a big file for improvement of the reliability of a race condition)<br /> * VoIP backgrounding trick (used to auto restart the app)<br /> * hidden segment attack<br /> * IOKit crafted call maker utility ({{cve|2014-4407}})<br /> <br /> == Programs which are used in order to jailbreak 8.x ==<br /> === [[Pangu8]] (8.0 / 8.0.1 / 8.0.2 / 8.1) ===<br /> * an exploit for a bug in /usr/libexec/neagent (source @iH8sn0w)<br /> * enterprise certificate (inside the IPA)<br /> * a kind of dylib injection into a system process (see IPA)<br /> * a dmg mount command (looks like the Developer DMG) (syslog while jailbreaking)<br /> * a sandboxing problem in debugserver ({{cve|2014-4457}})<br /> * the same/a similar kernel exploit as used in [[Pangu|the first Pangu]] ({{cve|2014-4461}}) (source @iH8sn0w)<br /> * enable-dylibs-to-override-cache<br /> * a new ovelapping segment attack ({{cve|2014-4455}})<br /> * i0n1c's Kernel info leak ({{cve|2014-4491}})<br /> <br /> === [[TaiG]] and [[PPJailbreak]] (8.0 / 8.0.1 / 8.0.2 / 8.1 / 8.1.1 / 8.1.2) ===<br /> (See also details at [http://newosxbook.com/articles/TaiG.html newosxbook.com])<br /> * LightSensor / ProxALSSensor kernel exploit (Also used in Pangu 1.0.0)<br /> * [[DeveloperDiskImage race condition]] (by [[comex]]) (source: https://twitter.com/iH8sn0w/status/538602532088860672; also used in p0sixspwn)<br /> * enable-dylibs-to-override-cache (Also used in Pangu8)<br /> * a kind of dylib injection into a system process (see IPA) (Also used in Pangu8 but tweaked slightly)<br /> * a new ovelapping segment attack [in a modified version] ({{cve|2014-4455}})<br /> * a new afc symlink attack ({{cve|2014-4480}})<br /> * mach_ports info leak kernel exploit ({{cve|2014-4496}})<br /> * IOHIDFamily Kernel exploit ({{cve|2014-4487}})</div>

Danzatt https://www.theiphonewiki.com/w/index.php?title=Jailbreak_Exploits&diff=44515 2015-02-10T14:23:57Z

<p>Danzatt: /* TaiG and PPJailbreak (8.0 / 8.0.1 / 8.0.2 / 8.1 / 8.1.1 / 8.1.2) */</p> <hr /> <div>This page lists the '''exploits''' used in [[jailbreak]]s.<br /> <br /> == Common exploits which are used in order to jailbreak different versions of iOS ==<br /> * [[Pwnage]] + [[Pwnage 2.0]] (together to jailbreak the [[n82ap|iPhone 3G]])<br /> * [[ARM7 Go]] (from iOS 2.1.1) (for [[tethered jailbreak]] on [[n72ap|iPod touch 2G]])<br /> * [[0x24000 Segment Overflow]] (for [[untethered jailbreak]] on [[n88ap|iPhone 3GS]] with [[Bootrom 359.3|old bootrom]] and [[n72ap|iPod touch 2G]] with [[Bootrom 240.4|old bootrom]]; another exploit as the [[limera1n Exploit]] is required)<br /> * [[limera1n Exploit]] (for [[tethered jailbreak]] on [[n88ap|iPhone 3GS]], [[n18ap|iPod touch 3G]], [[k48ap|iPad]], [[iPhone 4]], [[n81ap|iPod touch 4G]] and [[k66ap|Apple TV 2G]])<br /> * [[usb_control_msg(0xA1, 1) Exploit]] (also known as &quot;steaks4uce&quot;) (for [[tethered jailbreak]] on [[n72ap|iPod touch 2G]])<br /> <br /> == Programs which are used in order to jailbreak different versions of iOS ==<br /> === [[PwnageTool]] (2.0 - 5.1.1) ===<br /> * uses different common exploits<br /> * uses the exploits listed below to untether up to iOS 5.1.1<br /> <br /> === [[redsn0w]] (3.0 - 6.0) ===<br /> * uses different common exploits<br /> * uses the same exploits as [[Absinthe|Absinthe]] and [[Absinthe|Absinthe 2.0]] to jailbreak iOS 5.0/5.0.1 and 5.1.1<br /> * uses the exploits listed below to untether up to iOS 5.1.1<br /> <br /> === [[sn0wbreeze]] (3.1.3 - 6.1.3) ===<br /> * uses different common exploits<br /> * uses the exploits listed below to untether up to iOS 6.1.2<br /> <br /> == Programs which are used in order to jailbreak 1.x ==<br /> === [[AppTapp Installer]] (1.0 / 1.0.1 / 1.0.2) ===<br /> * iBoot &lt;code&gt;cp&lt;/code&gt;-command exploit<br /> <br /> === [[iBrickr]] (1.0 / 1.0.1 / 1.0.2) ===<br /> * iBoot &lt;code&gt;cp&lt;/code&gt;-command exploit<br /> <br /> === [[AppSnapp]]/[[JailbreakMe|JailbreakMe 1.0]] (1.0 / 1.0.1 / 1.0.2 / 1.1.1) ===<br /> * [[LibTiff|libtiff exploit]] (Adapted from the PSP scene, used by [[JailbreakMe]]) ({{cve|2006-3459}})<br /> <br /> === [[mknod|OktoPrep]] (1.1.2) ===<br /> &quot;Upgrade&quot; to 1.1.2 from a jailborken 1.1.1<br /> * [[mknod]]<br /> <br /> === [[Soft Upgrade]] (1.1.3) ===<br /> &quot;Upgrade&quot; to 1.1.3 from a running jailbroken 1.1.2<br /> <br /> === [[ZiPhone]] (1.1.3 / 1.1.4 /1.1.5) ===<br /> * [[Ramdisk Hack]]<br /> <br /> === [[iLiberty+|iLiberty / iLiberty+]] (1.1.3 / 1.1.4 /1.1.5) ===<br /> <br /> == Programs which are used in order to jailbreak 2.x ==<br /> === [[QuickPwn]] (2.0 - 2.2.1) ===<br /> * uses [[Pwnage]] and [[Pwnage 2.0]]<br /> <br /> === [[Redsn0w Lite]] (2.1.1) ===<br /> * [[ARM7 Go]] (for [[n72ap|iPod touch 2G]] only)<br /> <br /> == Programs which are used in order to jailbreak 3.x ==<br /> === [[purplera1n]] (3.0) ===<br /> * [[iBoot Environment Variable Overflow]] ({{cve|2009-2795}})<br /> * uses [[0x24000 Segment Overflow]]<br /> <br /> === [[blackra1n]] (3.1.2) ===<br /> * [[usb_control_msg(0x21, 2) Exploit]] ({{cve|2010-0038}})<br /> * uses [[0x24000 Segment Overflow]]<br /> <br /> === [[Spirit]] (3.1.2 / 3.1.3 / 3.2) ===<br /> * [[MobileBackup Copy Exploit]]<br /> * [[Incomplete Codesign Exploit]]<br /> * [[BPF_STX Kernel Write Exploit]]<br /> <br /> === [[Star|JailbreakMe 2.0 / Star]] (3.1.2 / 3.1.3 / 3.2 / 3.2.1) ===<br /> * [[Malformed CFF Vulnerability]] ({{cve|2010-1797}})<br /> * [[Incomplete Codesign Exploit]]<br /> * [[IOSurface Kernel Exploit]] ({{cve|2010-2973}})<br /> <br /> === [[limera1n]] / [[greenpois0n (jailbreak)|greenpois0n]] (3.2.2) ===<br /> * uses different common exploits<br /> * [[Packet Filter Kernel Exploit]]<br /> <br /> == Programs which are used in order to jailbreak 4.x ==<br /> === [[Star|JailbreakMe 2.0 / Star]] (4.0 / 4.0.1) ===<br /> * [[Malformed CFF Vulnerability]] ({{cve|2010-1797}})<br /> * [[Incomplete Codesign Exploit]]<br /> * [[IOSurface Kernel Exploit]] ({{cve|2010-2973}})<br /> <br /> === [[limera1n]] / (4.0 / 4.0.1 / 4.0.2 / 4.1) ===<br /> * uses different common exploits<br /> * [[Packet Filter Kernel Exploit]]<br /> <br /> === [[greenpois0n (jailbreak)|greenpois0n]] (4.1) ===<br /> * uses different common exploits<br /> * [[Packet Filter Kernel Exploit]]<br /> <br /> === [[greenpois0n (jailbreak)|greenpois0n]] (4.2.1) ===<br /> * uses different common exploits<br /> * [[HFS Legacy Volume Name Stack Buffer Overflow]]<br /> <br /> === [[Saffron|JailbreakMe 3.0 / Saffron]] (4.2.6 / 4.2.7 / 4.2.8) ===<br /> * [[T1 Font Integer Overflow]] ({{cve|2011-0226}})<br /> * [[HFS Legacy Volume Name Stack Buffer Overflow]]<br /> <br /> === [[Saffron|JailbreakMe 3.0 / Saffron]] (4.3 / 4.3.1 / 4.3.2 / 4.3.3) ===<br /> Except for the [[n18ap|iPod touch 3G]] on iOS 4.3.1.<br /> * [[T1 Font Integer Overflow]] ({{cve|2011-0226}})<br /> * [[IOMobileFrameBuffer Privilege Escalation Exploit]] ({{cve|2011-0227}})<br /> <br /> === i0nic's Untether (4.3.1 / 4.3.2 / 4.3.3) ===<br /> used in [[redsn0w]] to untether iOS 4.3.1 / 4.3.2 / 4.3.3<br /> * [[ndrv_setspec() Integer Overflow]]<br /> <br /> == Programs which are used in order to jailbreak 5.x ==<br /> === [[unthredera1n]] (5.0 / 5.0.1 / 5.1 / 5.1.1) ===<br /> Except for the [[iPad 3]]<br /> * MobileBackup2 Copy Exploit<br /> * a new Packet Filter Kernel Exploit ({{cve|2012-3728}})<br /> * [[AMFID code signing evasion]] ({{cve|2013-0977}})<br /> * [[launchd.conf untether]]<br /> * [[Timezone Vulnerability]]<br /> <br /> === [[Absinthe]] (5.0 on [[n94ap|iPhone 4S]] only / 5.0.1 on [[iPad 2]] and [[iPhone 4S]]) ===<br /> * [[Racoon String Format Overflow Exploit]] ({{cve|2012-0646}}) (used both for payload injection and untether)<br /> * [[HFS Heap Overflow]] ({{cve|2012-0642}})<br /> * unknown exploit ({{cve|2012-0643}})<br /> <br /> === [[Corona|Corona Untether]] (5.0.1) ===<br /> * [[Racoon String Format Overflow Exploit]] ({{cve|2012-0646}})<br /> * [[HFS Heap Overflow]] ({{cve|2012-0642}})<br /> * unknown exploit ({{cve|2012-0643}})<br /> <br /> === [[Absinthe|Absinthe 2.0]] and [[Rocky Racoon|Rocky Racoon Untether]] (5.1.1) ===<br /> * a new Packet Filter Kernel Exploit ({{cve|2012-3728}})<br /> * Racoon DNS4/WINS4 table buffer overflow ({{cve|2012-3727}})<br /> * MobileBackup2 Copy Exploit<br /> <br /> == Programs which are used in order to jailbreak 6.x ==<br /> === [[evasi0n]] (6.0 / 6.0.1 / 6.0.2 / 6.1 / 6.1.1 / 6.1.2) ===<br /> * [[Symbolic Link Vulnerability]] ({{cve|2013-0979}})<br /> * [[Timezone Vulnerability]]<br /> * [[Shebang Trick]] ({{cve|2013-5154}})<br /> * [[AMFID code signing evasion]]<br /> * [[launchd.conf untether]]<br /> * [[IOUSBDeviceFamily Vulnerability]] ({{cve|2013-0981}})<br /> * [[ARM Exception Vector Info Leak]] ({{cve|2013-0978}})<br /> * [[dynamic memmove() locating]]<br /> * [[vm_map_copy_t corruption for arbitrary memory disclosure]]<br /> * [[kernel memory write via ROP gadget]]<br /> * [[Overlapping Segment Attack]] ({{cve|2013-0977}})<br /> <br /> === [[p0sixspwn]] (6.1.3 / 6.1.4 / 6.1.5 / 6.1.6) ===<br /> * [[posix_spawn kernel information leak]] ({{cve|2013-3954}}) (by [[i0n1c]])<br /> * [[posix_spawn kernel exploit]] ({{cve|2013-3954}}) (by [[i0n1c]])<br /> * [[mach_msg_ool_descriptor_ts for heap shaping]] ({{cve|2013-3953}})<br /> * [[AMFID_code_signing_evasi0n7]] ({{cve|2014-1273}})<br /> * [[DeveloperDiskImage race condition]] (by [[comex]])<br /> * [[launchd.conf untether]]<br /> <br /> == Programs which are used in order to jailbreak 7.x ==<br /> === [[evasi0n7]] (7.0 / 7.0.1 / 7.0.2 / 7.0.3 / 7.0.4 / 7.0.5 / 7.0.6) ===<br /> {{Section Stub}}<br /> * [[Symbolic Link Vulnerability]] ({{cve|2013-5133}})<br /> * [[AMFID_code_signing_evasi0n7]] ({{cve|2014-1273}})<br /> * CrashHouseKeeping chmod vulnarability ({{cve|2014-1272}})<br /> * ptmx_get_ioctl ioctl crafted call ({{cve|2014-1278}})<br /> <br /> === [[Geeksn0w]] (7.1 / 7.1.1 / 7.1.2) ===<br /> * [[limera1n]]'s bootrom exploit ([[Tethered jailbreak]]) on [[iPhone 4]]<br /> <br /> === [[Pangu]] (7.1 / 7.1.1 / 7.1.2) ===<br /> * [[i0n1c]]'s Infoleak vulnerability (Pangu v1.0.0)<br /> * break_early_random (by [[i0n1c]] and Tarjei Mandt of Azimuth) (Pangu v1.1.0)<br /> * LightSensor / ProxALSSensor kernel exploit (Pangu 1.0.0) ({{cve|2014-4388}})<br /> * TempSensor kernel exploit (Pangu 1.1.0) ({{cve|2014-4388}})<br /> * &quot;syslogd chown&quot; vulnerability<br /> * enterprise certificate (no real exploit, used for initial &quot;unsigned&quot; code execution)<br /> * &quot;foo_extracted&quot; symlink vulnerability (used to write to /var) ({{cve|2014-4386}})<br /> * /tmp/bigfile (a big file for improvement of the reliability of a race condition)<br /> * VoIP backgrounding trick (used to auto restart the app)<br /> * hidden segment attack<br /> * IOKit crafted call maker utility ({{cve|2014-4407}})<br /> <br /> == Programs which are used in order to jailbreak 8.x ==<br /> === [[Pangu8]] (8.0 / 8.0.1 / 8.0.2 / 8.1) ===<br /> * an exploit for a bug in /usr/libexec/neagent (source @iH8sn0w)<br /> * enterprise certificate (inside the IPA)<br /> * a kind of dylib injection into a system process (see IPA)<br /> * a dmg mount command (looks like the Developer DMG) (syslog while jailbreaking)<br /> * a sandboxing problem in debugserver ({{cve|2014-4457}})<br /> * the same/a similar kernel exploit as used in [[Pangu|the first Pangu]] ({{cve|2014-4461}}) (source @iH8sn0w)<br /> * enable-dylibs-to-override-cache<br /> * a new ovelapping segment attack ({{cve|2014-4455}})<br /> * i0n1c's Kernel info leak ({{cve|2014-4491}})<br /> <br /> === [[TaiG]] and [[PPJailbreak]] (8.0 / 8.0.1 / 8.0.2 / 8.1 / 8.1.1 / 8.1.2) ===<br /> * LightSensor / ProxALSSensor kernel exploit (Also used in Pangu 1.0.0)<br /> * [[DeveloperDiskImage race condition]] (by [[comex]]) (source: https://twitter.com/iH8sn0w/status/538602532088860672; also used in p0sixspwn)<br /> * enable-dylibs-to-override-cache (Also used in Pangu8)<br /> * a kind of dylib injection into a system process (see IPA) (Also used in Pangu8 but tweaked slightly)<br /> * a new ovelapping segment attack [in a modified version] ({{cve|2014-4455}})<br /> * a new afc symlink attack ({{cve|2014-4480}})<br /> * mach_ports info leak kernel exploit ({{cve|2014-4496}})<br /> * IOHIDFamily Kernel exploit ({{cve|2014-4487}})<br /> (See also details at [http://newosxbook.com/articles/TaiG.html newosxbook.com])</div>

Danzatt https://www.theiphonewiki.com/w/index.php?title=Jailbreak_Exploits&diff=44514 2015-02-10T14:23:32Z

<p>Danzatt: </p> <hr /> <div>This page lists the '''exploits''' used in [[jailbreak]]s.<br /> <br /> == Common exploits which are used in order to jailbreak different versions of iOS ==<br /> * [[Pwnage]] + [[Pwnage 2.0]] (together to jailbreak the [[n82ap|iPhone 3G]])<br /> * [[ARM7 Go]] (from iOS 2.1.1) (for [[tethered jailbreak]] on [[n72ap|iPod touch 2G]])<br /> * [[0x24000 Segment Overflow]] (for [[untethered jailbreak]] on [[n88ap|iPhone 3GS]] with [[Bootrom 359.3|old bootrom]] and [[n72ap|iPod touch 2G]] with [[Bootrom 240.4|old bootrom]]; another exploit as the [[limera1n Exploit]] is required)<br /> * [[limera1n Exploit]] (for [[tethered jailbreak]] on [[n88ap|iPhone 3GS]], [[n18ap|iPod touch 3G]], [[k48ap|iPad]], [[iPhone 4]], [[n81ap|iPod touch 4G]] and [[k66ap|Apple TV 2G]])<br /> * [[usb_control_msg(0xA1, 1) Exploit]] (also known as &quot;steaks4uce&quot;) (for [[tethered jailbreak]] on [[n72ap|iPod touch 2G]])<br /> <br /> == Programs which are used in order to jailbreak different versions of iOS ==<br /> === [[PwnageTool]] (2.0 - 5.1.1) ===<br /> * uses different common exploits<br /> * uses the exploits listed below to untether up to iOS 5.1.1<br /> <br /> === [[redsn0w]] (3.0 - 6.0) ===<br /> * uses different common exploits<br /> * uses the same exploits as [[Absinthe|Absinthe]] and [[Absinthe|Absinthe 2.0]] to jailbreak iOS 5.0/5.0.1 and 5.1.1<br /> * uses the exploits listed below to untether up to iOS 5.1.1<br /> <br /> === [[sn0wbreeze]] (3.1.3 - 6.1.3) ===<br /> * uses different common exploits<br /> * uses the exploits listed below to untether up to iOS 6.1.2<br /> <br /> == Programs which are used in order to jailbreak 1.x ==<br /> === [[AppTapp Installer]] (1.0 / 1.0.1 / 1.0.2) ===<br /> * iBoot &lt;code&gt;cp&lt;/code&gt;-command exploit<br /> <br /> === [[iBrickr]] (1.0 / 1.0.1 / 1.0.2) ===<br /> * iBoot &lt;code&gt;cp&lt;/code&gt;-command exploit<br /> <br /> === [[AppSnapp]]/[[JailbreakMe|JailbreakMe 1.0]] (1.0 / 1.0.1 / 1.0.2 / 1.1.1) ===<br /> * [[LibTiff|libtiff exploit]] (Adapted from the PSP scene, used by [[JailbreakMe]]) ({{cve|2006-3459}})<br /> <br /> === [[mknod|OktoPrep]] (1.1.2) ===<br /> &quot;Upgrade&quot; to 1.1.2 from a jailborken 1.1.1<br /> * [[mknod]]<br /> <br /> === [[Soft Upgrade]] (1.1.3) ===<br /> &quot;Upgrade&quot; to 1.1.3 from a running jailbroken 1.1.2<br /> <br /> === [[ZiPhone]] (1.1.3 / 1.1.4 /1.1.5) ===<br /> * [[Ramdisk Hack]]<br /> <br /> === [[iLiberty+|iLiberty / iLiberty+]] (1.1.3 / 1.1.4 /1.1.5) ===<br /> <br /> == Programs which are used in order to jailbreak 2.x ==<br /> === [[QuickPwn]] (2.0 - 2.2.1) ===<br /> * uses [[Pwnage]] and [[Pwnage 2.0]]<br /> <br /> === [[Redsn0w Lite]] (2.1.1) ===<br /> * [[ARM7 Go]] (for [[n72ap|iPod touch 2G]] only)<br /> <br /> == Programs which are used in order to jailbreak 3.x ==<br /> === [[purplera1n]] (3.0) ===<br /> * [[iBoot Environment Variable Overflow]] ({{cve|2009-2795}})<br /> * uses [[0x24000 Segment Overflow]]<br /> <br /> === [[blackra1n]] (3.1.2) ===<br /> * [[usb_control_msg(0x21, 2) Exploit]] ({{cve|2010-0038}})<br /> * uses [[0x24000 Segment Overflow]]<br /> <br /> === [[Spirit]] (3.1.2 / 3.1.3 / 3.2) ===<br /> * [[MobileBackup Copy Exploit]]<br /> * [[Incomplete Codesign Exploit]]<br /> * [[BPF_STX Kernel Write Exploit]]<br /> <br /> === [[Star|JailbreakMe 2.0 / Star]] (3.1.2 / 3.1.3 / 3.2 / 3.2.1) ===<br /> * [[Malformed CFF Vulnerability]] ({{cve|2010-1797}})<br /> * [[Incomplete Codesign Exploit]]<br /> * [[IOSurface Kernel Exploit]] ({{cve|2010-2973}})<br /> <br /> === [[limera1n]] / [[greenpois0n (jailbreak)|greenpois0n]] (3.2.2) ===<br /> * uses different common exploits<br /> * [[Packet Filter Kernel Exploit]]<br /> <br /> == Programs which are used in order to jailbreak 4.x ==<br /> === [[Star|JailbreakMe 2.0 / Star]] (4.0 / 4.0.1) ===<br /> * [[Malformed CFF Vulnerability]] ({{cve|2010-1797}})<br /> * [[Incomplete Codesign Exploit]]<br /> * [[IOSurface Kernel Exploit]] ({{cve|2010-2973}})<br /> <br /> === [[limera1n]] / (4.0 / 4.0.1 / 4.0.2 / 4.1) ===<br /> * uses different common exploits<br /> * [[Packet Filter Kernel Exploit]]<br /> <br /> === [[greenpois0n (jailbreak)|greenpois0n]] (4.1) ===<br /> * uses different common exploits<br /> * [[Packet Filter Kernel Exploit]]<br /> <br /> === [[greenpois0n (jailbreak)|greenpois0n]] (4.2.1) ===<br /> * uses different common exploits<br /> * [[HFS Legacy Volume Name Stack Buffer Overflow]]<br /> <br /> === [[Saffron|JailbreakMe 3.0 / Saffron]] (4.2.6 / 4.2.7 / 4.2.8) ===<br /> * [[T1 Font Integer Overflow]] ({{cve|2011-0226}})<br /> * [[HFS Legacy Volume Name Stack Buffer Overflow]]<br /> <br /> === [[Saffron|JailbreakMe 3.0 / Saffron]] (4.3 / 4.3.1 / 4.3.2 / 4.3.3) ===<br /> Except for the [[n18ap|iPod touch 3G]] on iOS 4.3.1.<br /> * [[T1 Font Integer Overflow]] ({{cve|2011-0226}})<br /> * [[IOMobileFrameBuffer Privilege Escalation Exploit]] ({{cve|2011-0227}})<br /> <br /> === i0nic's Untether (4.3.1 / 4.3.2 / 4.3.3) ===<br /> used in [[redsn0w]] to untether iOS 4.3.1 / 4.3.2 / 4.3.3<br /> * [[ndrv_setspec() Integer Overflow]]<br /> <br /> == Programs which are used in order to jailbreak 5.x ==<br /> === [[unthredera1n]] (5.0 / 5.0.1 / 5.1 / 5.1.1) ===<br /> Except for the [[iPad 3]]<br /> * MobileBackup2 Copy Exploit<br /> * a new Packet Filter Kernel Exploit ({{cve|2012-3728}})<br /> * [[AMFID code signing evasion]] ({{cve|2013-0977}})<br /> * [[launchd.conf untether]]<br /> * [[Timezone Vulnerability]]<br /> <br /> === [[Absinthe]] (5.0 on [[n94ap|iPhone 4S]] only / 5.0.1 on [[iPad 2]] and [[iPhone 4S]]) ===<br /> * [[Racoon String Format Overflow Exploit]] ({{cve|2012-0646}}) (used both for payload injection and untether)<br /> * [[HFS Heap Overflow]] ({{cve|2012-0642}})<br /> * unknown exploit ({{cve|2012-0643}})<br /> <br /> === [[Corona|Corona Untether]] (5.0.1) ===<br /> * [[Racoon String Format Overflow Exploit]] ({{cve|2012-0646}})<br /> * [[HFS Heap Overflow]] ({{cve|2012-0642}})<br /> * unknown exploit ({{cve|2012-0643}})<br /> <br /> === [[Absinthe|Absinthe 2.0]] and [[Rocky Racoon|Rocky Racoon Untether]] (5.1.1) ===<br /> * a new Packet Filter Kernel Exploit ({{cve|2012-3728}})<br /> * Racoon DNS4/WINS4 table buffer overflow ({{cve|2012-3727}})<br /> * MobileBackup2 Copy Exploit<br /> <br /> == Programs which are used in order to jailbreak 6.x ==<br /> === [[evasi0n]] (6.0 / 6.0.1 / 6.0.2 / 6.1 / 6.1.1 / 6.1.2) ===<br /> * [[Symbolic Link Vulnerability]] ({{cve|2013-0979}})<br /> * [[Timezone Vulnerability]]<br /> * [[Shebang Trick]] ({{cve|2013-5154}})<br /> * [[AMFID code signing evasion]]<br /> * [[launchd.conf untether]]<br /> * [[IOUSBDeviceFamily Vulnerability]] ({{cve|2013-0981}})<br /> * [[ARM Exception Vector Info Leak]] ({{cve|2013-0978}})<br /> * [[dynamic memmove() locating]]<br /> * [[vm_map_copy_t corruption for arbitrary memory disclosure]]<br /> * [[kernel memory write via ROP gadget]]<br /> * [[Overlapping Segment Attack]] ({{cve|2013-0977}})<br /> <br /> === [[p0sixspwn]] (6.1.3 / 6.1.4 / 6.1.5 / 6.1.6) ===<br /> * [[posix_spawn kernel information leak]] ({{cve|2013-3954}}) (by [[i0n1c]])<br /> * [[posix_spawn kernel exploit]] ({{cve|2013-3954}}) (by [[i0n1c]])<br /> * [[mach_msg_ool_descriptor_ts for heap shaping]] ({{cve|2013-3953}})<br /> * [[AMFID_code_signing_evasi0n7]] ({{cve|2014-1273}})<br /> * [[DeveloperDiskImage race condition]] (by [[comex]])<br /> * [[launchd.conf untether]]<br /> <br /> == Programs which are used in order to jailbreak 7.x ==<br /> === [[evasi0n7]] (7.0 / 7.0.1 / 7.0.2 / 7.0.3 / 7.0.4 / 7.0.5 / 7.0.6) ===<br /> {{Section Stub}}<br /> * [[Symbolic Link Vulnerability]] ({{cve|2013-5133}})<br /> * [[AMFID_code_signing_evasi0n7]] ({{cve|2014-1273}})<br /> * CrashHouseKeeping chmod vulnarability ({{cve|2014-1272}})<br /> * ptmx_get_ioctl ioctl crafted call ({{cve|2014-1278}})<br /> <br /> === [[Geeksn0w]] (7.1 / 7.1.1 / 7.1.2) ===<br /> * [[limera1n]]'s bootrom exploit ([[Tethered jailbreak]]) on [[iPhone 4]]<br /> <br /> === [[Pangu]] (7.1 / 7.1.1 / 7.1.2) ===<br /> * [[i0n1c]]'s Infoleak vulnerability (Pangu v1.0.0)<br /> * break_early_random (by [[i0n1c]] and Tarjei Mandt of Azimuth) (Pangu v1.1.0)<br /> * LightSensor / ProxALSSensor kernel exploit (Pangu 1.0.0) ({{cve|2014-4388}})<br /> * TempSensor kernel exploit (Pangu 1.1.0) ({{cve|2014-4388}})<br /> * &quot;syslogd chown&quot; vulnerability<br /> * enterprise certificate (no real exploit, used for initial &quot;unsigned&quot; code execution)<br /> * &quot;foo_extracted&quot; symlink vulnerability (used to write to /var) ({{cve|2014-4386}})<br /> * /tmp/bigfile (a big file for improvement of the reliability of a race condition)<br /> * VoIP backgrounding trick (used to auto restart the app)<br /> * hidden segment attack<br /> * IOKit crafted call maker utility ({{cve|2014-4407}})<br /> <br /> == Programs which are used in order to jailbreak 8.x ==<br /> === [[Pangu8]] (8.0 / 8.0.1 / 8.0.2 / 8.1) ===<br /> * an exploit for a bug in /usr/libexec/neagent (source @iH8sn0w)<br /> * enterprise certificate (inside the IPA)<br /> * a kind of dylib injection into a system process (see IPA)<br /> * a dmg mount command (looks like the Developer DMG) (syslog while jailbreaking)<br /> * a sandboxing problem in debugserver ({{cve|2014-4457}})<br /> * the same/a similar kernel exploit as used in [[Pangu|the first Pangu]] ({{cve|2014-4461}}) (source @iH8sn0w)<br /> * enable-dylibs-to-override-cache<br /> * a new ovelapping segment attack ({{cve|2014-4455}})<br /> * i0n1c's Kernel info leak ({{cve|2014-4491}})<br /> <br /> === [[TaiG]] and [[PPJailbreak]] (8.0 / 8.0.1 / 8.0.2 / 8.1 / 8.1.1 / 8.1.2) ===<br /> * LightSensor / ProxALSSensor kernel exploit (Also used in Pangu 1.0.0)<br /> * [[DeveloperDiskImage race condition]] (by [[comex]]) (source: https://twitter.com/iH8sn0w/status/538602532088860672; also used in p0sixspwn)<br /> * enable-dylibs-to-override-cache (Also used in Pangu8)<br /> * a kind of dylib injection into a system process (see IPA) (Also used in Pangu8 but tweaked slightly)<br /> * a new ovelapping segment attack [in a modified version] ({{cve|2014-4455}})<br /> * a new afc symlink attack ({{cve|2014-4480}})<br /> * mach_ports info leak kernel exploit ({{cve|2014-4496}})<br /> * IOHIDFamily Kernel exploit ({{cve|2014-4487}})<br /> (See also details at [http://newosxbook.com/articles/TaiG.html newosxbook.com])</div>

Danzatt https://www.theiphonewiki.com/w/index.php?title=I0n1c&diff=43810 2014-11-29T12:21:20Z

<p>Danzatt: adding newly released slide deck (exploit used in taig jb)</p> <hr /> <div>{{lowercase}}<br /> '''i0n1c''', whose real name is Stefan Esser, is a German security researcher. He developed [[Antid0te]], an [[wikipedia:Address space layout randomization|ASLR]] for jailbroken [[iPhone]]s in fall 2010, but never released it, because [[iOS]] since 4.3 includes an implementation of ASLR. He developed an untethering exploit for iOS 4.3. He gave a version of the exploit that worked on iOS 4.3.1 to the [[iPhone Dev Team]] which updated [[redsn0w]] and [[PwnageTool]] to use it and released the new tools on 4 April 2011. [[sn0wbreeze]] was also updated to include his untether. As the vulnerability went unpatched in iOS 4.3.2 and 4.3.3, he updated his code later to support those firmwares. An iOS 4.3-compatible version was never released. His exploit was used in [[Pangu]] jailbreak.<br /> <br /> ===Presentations===<br /> *[http://www.slideshare.net/i0n1c/ruxcon-2014-stefan-esser-ios8-containers-sandboxes-and-entitlements Ruxcon 2014 - iOS8 Containers, Sandboxes and Entitlements]<br /> *[http://conference.hitb.org/hitbsecconf2011kul/materials/D2T1%20-%20Stefan%20Esser%20-%20iPhone%20Exploitation%20-%20One%20ROPe%20to%20Bind%20Them%20All.pdf HITB 2011 Malaysia: iPhone Exploitation - One ROPe to bind them all?]<br /> *[http://antid0te.com/CSW2012_StefanEsser_iOS5_An_Exploitation_Nightmare_FINAL.pdf CanSecWest 2012: iOS5, an Exploitation Nightmare (PDF)]<br /> *[https://media.blackhat.com/bh-us-11/Esser/BH_US_11_Esser_Exploiting_The_iOS_Kernel_Slides.pdf BlackHat US 2011: Exploiting the iOS Kernel (PDF)]<br /> <br /> ===Links===<br /> *[https://twitter.com/i0n1c i0n1c on Twitter]<br /> *[http://www.suspekt.org Homepage]<br /> *[https://github.com/stefanesser GitHub]<br /> [[Category:Hackers]]<br /> [[Category:Security Researcher]]</div>

Danzatt https://www.theiphonewiki.com/w/index.php?title=SHSH&diff=43095 2014-10-28T19:56:53Z

<p>Danzatt: Oh Britta</p> <hr /> <div>As the [[wikipedia:SHSH blob | '''SHSH''' blob article on Wikipedia]] summarizes it: &quot;SHSH blob is a jargon term for a small piece of data that is part of Apple's digital signature protocol for iOS restores and updates, designed to control the iOS versions that users can install on their iOS devices (iPhones, iPads, iPod touches, and Apple TVs), generally only allowing the newest iOS version to be installable. &quot;<br /> <br /> Technically, the SHSH of a firmware image is a 1024-bit (&lt;code&gt;0x80&lt;/code&gt; bytes) [[wikipedia:RSA (cryptosystem)|RSA]] signature. This often also refers to backup files with the signature (&quot;SHSH blobs&quot;). This signature is needed to restore a specific iOS version; it is generated by Apple based on hardware keys of the device and the hash of the firmware. Apple only issues signatures for the currently-available iOS version, which disallows installing older iOS versions. But if you have saved signatures for an older iOS version, you may be able to use a [[wikipedia:replay attack|replay attack]] to restore that version. Therefore it is recommended to save the signature for your device as long as Apple issues it.<br /> <br /> With the tools mentioned below it is possible to backup the signature. It is not necessary that the device is jailbroken to do the backup. Usually the SHSH signature file is stored on [[Cydia Server|Saurik's server]]. If it is stored there, then you can see in the top of [[Cydia Application|Cydia]] (on jailbroken devices) for which version a backup exists. This moved to [[TSS Center]] which can be located on the main page and then they are shown at the top of that. <br /> <br /> Users often misunderstand this system and think that the SHSH firmware version they back up depends on the firmware version they have installed on their device. This is the case for [[iFaith]], but not for TinyUmbrella. iFaith dumps the SHSHs from your device's storage (whatever's installed on your device, e.g. 4.3.3), while TinyUmbrella gets SHSHs from Apple's servers (whatever firmwares Apple is currently signing).<br /> <br /> ==Using SHSH==<br /> Older devices allow installation of any correctly signed firmware, so no backup of the certificate is necessary. Devices that need Apple signatures are: [[n88ap|iPhone 3GS]] (new Bootrom), [[N90ap|iPhone 4]], [[N18ap|iPod touch 3G]], [[K48ap|iPad]], [[iPad 2]], [[n81ap|iPod touch 4G]], [[K66ap|Apple TV 2G]] and all newer devices. The [[N82ap|iPhone 3G]], [[N88ap|iPhone 3GS Old Bootrom]] and [[N72ap|iPod touch 2G]] bootroms do not require these SHSHs; however, newer versions of iOS require them (unless the chain of trust is broken and custom firmwares are installed). To restore to arbitrary versions of iOS 4.0, the SHSH is also needed for the [[N72ap|iPod touch 2G]] and [[N82ap|iPhone 3G]]. not only does [[DFU Mode]] require the [[iBSS]]/[[iBEC]] files to be signed with an SHSH that includes the device's [[ECID]], but the normal boot-chain requires the [[LLB]] to be fully signed with an [[ECID]]+SHSH, so a downgrade [[IPSW File Format|IPSW]] is not possible without a bootrom exploit of normal boot-chain (e.g. [[0x24000 Segment Overflow]]). See also the [http://blog.iphone-dev.org/post/833937433 Dev Team Blog post] about this.<br /> <br /> To restore to iOS 3.x or 4.x, change your hosts file to map any request to an Apple server to point to [[Saurik]]'s server instead, if your device's signatures are hosted there. If you have the signature file on your computer, run [[TinyUmbrella]]'s TSS Server on your local machine.<br /> <br /> Since the [[limera1n Exploit]] is fixed in the [[bootrom]] since version [[Bootrom 838.3]] and because iOS since 5.0 includes a [[nonce]] in their SHSH hashes, downgrading newer devices ([[N94ap|iPhone 4S]], [[iPad 2]], [[iPad 3]], [[J33ap|Apple TV 3G]]) to earlier 5.x firmwares is not as simple. To restore to iOS 5.x on older devices, stitch iOS 5.x blobs into custom firmware (using redsn0w for example) and restore with that firmware. To restore to iOS 5.x on newer devices, use redsn0w's restore method. See the [http://www.jailbreakqa.com/questions/32462/frequently-asked-questions#94647 JailbreakQA guide to restoring to iOS 5.x using SHSH blobs] (for all devices that can run iOS 5.x except Apple TV 3G).<br /> <br /> ==Timeline==<br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! iOS<br /> ! For Device(s)<br /> ! From<br /> ! Until<br /> ! Status<br /> |-<br /> | 3.0<br /> | rowspan=&quot;3&quot; | [[n88ap|iPhone 3GS]]<br /> | 19 June 2009<br /> | 09 September 2009<br /> | {{no|Closed}}<br /> |-<br /> | 3.0.1<br /> | 31 July 2009<br /> | 09 September 2009<br /> | {{no|Closed}}<br /> |-<br /> | 3.1<br /> | 09 September 2009<br /> | 08 October 2009<br /> | {{no|Closed}}<br /> |-<br /> | rowspan=&quot;2&quot; | 3.1.1<br /> | [[n72ap|iPod touch 2G]]<br /> | 09 September 2009<br /> | 21 June 2010<br /> | {{no|Closed}}<br /> |-<br /> | [[n18ap|iPod touch 3G]]<br /> | 09 September 2009<br /> | 08 October 2009<br /> | {{no|Closed}}<br /> |-<br /> | rowspan=&quot;2&quot; | 3.1.2<br /> | [[n72ap|iPod touch 2G]]<br /> | 08 October 2009<br /> | 21 June 2010<br /> | {{no|Closed}}<br /> |-<br /> | [[n88ap|iPhone 3GS]], [[n18ap|iPod touch 3G]]<br /> | 08 October 2009<br /> | 02 February 2010<br /> | {{no|Closed}}<br /> |-<br /> | 3.1.3<br /> | [[n88ap|iPhone 3GS]], [[n72ap|iPod touch 2G]], [[n18ap|iPod touch 3G]] <br /> | 02 February 2010<br /> | 21 June 2010<br /> | {{no|Closed}}<br /> |-<br /> | 3.2<br /> | rowspan=&quot;3&quot; | [[k48ap|iPad]]<br /> | 03 April 2010<br /> | 15 July 2010<br /> | {{no|Closed}}<br /> |-<br /> | 3.2.1<br /> | 15 July 2010<br /> | 19 August 2010<br /> | {{no|Closed}}<br /> |-<br /> | 3.2.2<br /> | 11 August 2010<br /> | 02 December 2010 (?)<br /> | {{no|Closed}}<br /> |-<br /> | rowspan=&quot;4&quot; | 4.0<br /> | [[n72ap|iPod touch 2G]]<br /> | 21 June 2010<br /> | 09 September 2010<br /> | {{no|Closed}}<br /> |-<br /> | [[n18ap|iPod touch 3G]]<br /> | 21 June 2010<br /> | 19 August 2010<br /> | {{no|Closed}}<br /> |-<br /> | [[n82ap|iPhone 3G]], [[n88ap|iPhone 3GS]]<br /> | 21 June 2010<br /> | 15 July 2010<br /> | {{no|Closed}}<br /> |-<br /> | [[n90ap|iPhone 4 (iPhone3,1)]]<br /> | 24 June 2010<br /> | 15 July 2010<br /> | {{no|Closed}}<br /> |-<br /> | rowspan=&quot;2&quot; | 4.0.1<br /> | [[n82ap|iPhone 3G]]<br /> | 15 July 2010<br /> | 09 September 2010<br /> | {{no|Closed}}<br /> |-<br /> | [[n88ap|iPhone 3GS]], [[n90ap|iPhone 4 (iPhone3,1)]]<br /> | 15 July 2010<br /> | 19 August 2010<br /> | {{no|Closed}}<br /> |-<br /> | rowspan=&quot;2&quot; | 4.0.2<br /> | [[n82ap|iPhone 3G]], [[n72ap|iPod touch 2G]]<br /> | 11 August 2010<br /> | 18 September 2010&lt;!--Apple may have ceased signing earlier.--&gt;<br /> | {{no|Closed}}<br /> |-<br /> | [[n88ap|iPhone 3GS]], [[n90ap|iPhone 4 (iPhone3,1)]], [[n18ap|iPod touch 3G]]<br /> | 11 August 2010<br /> | 09 September 2010<br /> | {{no|Closed}}<br /> |-<br /> | rowspan=&quot;2&quot; | 4.1<br /> | [[n82ap|iPhone 3G]], [[n88ap|iPhone 3GS]], [[n72ap|iPod touch 2G]], [[n18ap|iPod touch 3G]]<br /> | 08 September 2010<br /> | -<br /> | {{yes|Open}}<br /> |-<br /> | [[n90ap|iPhone3,1]], [[n81ap|iPod touch 4G]]<br /> | 08 September 2010<br /> | 02 December 2010 (?)<br /> | {{no|Closed}}<br /> |-<br /> | {{nowrap|4.1 (4.0)}}<br /> | rowspan=&quot;2&quot; | [[k66ap|Apple TV 2G]]<br /> | 29 September 2010<br /> | 02 December 2010 (?)<br /> | {{no|Closed}}<br /> |-<br /> | {{nowrap|4.2 (4.1)}}<br /> | 22 November 2010<br /> | 14 December 2010<br /> | {{no|Closed}}<br /> |-<br /> | rowspan=&quot;2&quot; | 4.2.1<br /> | [[k48ap|iPad]], [[n88ap|iPhone 3GS]], [[n90ap|iPhone 4 (iPhone3,1)]], [[n18ap|iPod touch 3G]], [[n81ap|iPod touch 4G]]<br /> | 22 November 2010<br /> | 11 March 2011<br /> | {{no|Closed}}<br /> |-<br /> | [[n82ap|iPhone 3G]], [[n72ap|iPod touch 2G]]<br /> | 22 November 2010<br /> | -<br /> | {{yes|Open}}<br /> |-<br /> | {{nowrap|4.2.1 (4.1.1)}}<br /> | [[k66ap|Apple TV 2G]]<br /> | 14 December 2010<br /> | 28 May 2011 (?)<br /> | {{no|Closed}}<br /> |-<br /> | 4.2.5<br /> | rowspan=&quot;6&quot; | [[n92ap|iPhone 4 (iPhone3,3)]]<br /> | 11 January 2011<br /> | closed before product release<br /> | {{no|Closed}}<br /> |-<br /> | 4.2.6<br /> | 01 February 2011<br /> | 19 April 2011 (?)<br /> | {{no|Closed}}<br /> |-<br /> | 4.2.7<br /> | 14 April 2011<br /> | 6 May 2011<br /> | {{no|Closed}}<br /> |-<br /> | 4.2.8<br /> | 4 May 2011<br /> | 18 July 2011<br /> | {{no|Closed}}<br /> |-<br /> | 4.2.9<br /> | 15 July 2011<br /> | 27 July 2011<br /> | {{no|Closed}}<br /> |-<br /> | 4.2.10<br /> | 25 July 2011<br /> | 18 October 2011<br /> | {{no|Closed}}<br /> |-<br /> | 4.3<br /> | [[k48ap|iPad]], [[iPad 2]], [[n88ap|iPhone 3GS]], [[n90ap|iPhone 4 (iPhone3,1)]], [[n18ap|iPod touch 3G]], [[n81ap|iPod touch 4G]]<br /> | 09 March 2011<br /> | 27 March 2011 (?)<br /> | {{no|Closed}}<br /> |-<br /> | {{nowrap|4.3 (4.2)}}<br /> | rowspan=&quot;4&quot; | [[k66ap|Apple TV 2G]]<br /> | 09 March 2011<br /> | 22 March 2011 (?)<br /> | {{no|Closed}}<br /> |-<br /> | {{nowrap|4.3 (4.2.1)}}<br /> | 22 March 2011<br /> | 28 May 2011 (?)<br /> | {{no|Closed}}<br /> |-<br /> | {{nowrap|4.3 (4.2.2)}}<br /> | 11 May 2011<br /> | 18 October 2011 (?)<br /> | {{no|Closed}}<br /> |-<br /> | 4.3<br /> | 01 August 2011<br /> | ?<br /> | {{no|Closed}}<br /> |-<br /> | 4.3.1<br /> | rowspan=&quot;5&quot; | [[k48ap|iPad]], [[iPad 2]], [[n88ap|iPhone 3GS]], [[n90ap|iPhone3,1]], [[n18ap|iPod touch 3G]], [[n81ap|iPod touch 4G]]<br /> | 25 March 2011<br /> | 19 April 2011 (?)<br /> | {{no|Closed}}<br /> |-<br /> | 4.3.2<br /> | 14 April 2011<br /> | 06 May 2011<br /> | {{no|Closed}}<br /> |-<br /> | 4.3.3<br /> | 04 May 2011<br /> | 18 July 2011<br /> | {{no|Closed}}<br /> |-<br /> | 4.3.4<br /> | 15 July 2011<br /> | 27 July 2011<br /> | {{no|Closed}}<br /> |-<br /> | 4.3.5<br /> | 25 July 2011<br /> | 18 October 2011<br /> | {{no|Closed}}<br /> |-<br /> | 4.4<br /> | rowspan=&quot;5&quot; | [[k66ap|Apple TV 2G]]<br /> | 04 October 2011<br /> | ?<br /> | {{no|Closed}}<br /> |-<br /> | 4.4.1<br /> | 17 October 2011<br /> | ?<br /> | {{no|Closed}}<br /> |-<br /> | 4.4.2<br /> | 24 October 2011<br /> | 11 January 2012(?)<br /> | {{no|Closed}}<br /> |-<br /> | 4.4.3<br /> | 17 November 2011<br /> | 11 January 2012(?)<br /> | {{no|Closed}}<br /> |-<br /> | 4.4.4<br /> | 15 December 2011<br /> | 08 March 2012<br /> | {{no|Closed}}<br /> |-<br /> | rowspan=&quot;2&quot; | 5.0<br /> | [[k48ap|iPad]], [[iPad 2]], [[n88ap|iPhone 3GS]], [[iPhone 4]], [[n18ap|iPod touch 3G]], [[n81ap|iPod touch 4G]]<br /> | 04 October 2011<br /> | 10 November 2011(?)<br /> | {{no|Closed}}<br /> |-<br /> | [[n94ap|iPhone 4S]]<br /> | 14 October 2011<br /> | 10 November 2011(?)<br /> | {{no|Closed}}<br /> |-<br /> | 5.0<br /> | [[k66ap|Apple TV 2G]], [[j33ap|Apple TV 3G (AppleTV3,1)]]<br /> | 07 March 2012<br /> | 14 May 2012<br /> | {{no|Closed}}<br /> |-<br /> | 5.0.1<br /> | [[k48ap|iPad]], [[iPad 2]], [[n88ap|iPhone 3GS]], [[iPhone 4]], [[n94ap|iPhone 4S]], [[n18ap|iPod touch 3G]], [[n81ap|iPod touch 4G]]<br /> | 09 November 2011<br /> | 08 March 2012<br /> | {{no|Closed}}<br /> |-<br /> | 5.1<br /> | [[k48ap|iPad]], [[iPad 2]], [[iPad 3]], [[n88ap|iPhone 3GS]], [[iPhone 4]], [[n94ap|iPhone 4S]], [[n18ap|iPod touch 3G]], [[n81ap|iPod touch 4G]]<br /> | 07 March 2012<br /> | 14 May 2012<br /> | {{no|Closed}}<br /> |-<br /> | rowspan=&quot;2&quot; | 5.1.1<br /> | [[iPad 2]], [[iPad 3]], [[n88ap|iPhone 3GS]], [[iPhone 4]], [[n94ap|iPhone 4S]], [[n81ap|iPod touch 4G]]<br /> | 07 May 2012<br /> | 21 September 2012<br /> | {{no|Closed}}<br /> |-<br /> | [[k48ap|iPad]], [[n18ap|iPod touch 3G]]<br /> | 07 May 2012<br /> | -<br /> | {{yes|Open}}<br /> |-<br /> | 5.0.1<br /> | rowspan=&quot;2&quot; | [[k66ap|Apple TV 2G]], [[j33ap|Apple TV 3G (AppleTV3,1)]]<br /> | 10 May 2012<br /> | ?? June 2012<br /> | {{no|Closed}}<br /> |-<br /> | 5.0.2<br /> | 05 June 2012<br /> | 20 March 2013<br /> | {{no|Closed}}<br /> |-<br /> | rowspan=&quot;2&quot; | 6.0<br /> | [[iPad 2]], [[iPad 3]], [[n88ap|iPhone 3GS]], [[iPhone 4]], [[n94ap|iPhone 4S]], [[iPhone 5]], [[n81ap|iPod touch 4G]], [[iPod touch 5G]]<br /> | 19 September 2012<br /> | 01 November 2012<br /> | {{no|Closed}}<br /> |-<br /> | [[iPad 2]], [[iPad 3]], [[p105ap|iPad mini 1G (iPad2,5)]], [[n88ap|iPhone 3GS]], [[iPhone 4]], [[n94ap|iPhone 4S]], [[iPhone 5]], [[n81ap|iPod touch 4G]], [[iPod touch 5G]]<br /> | 26 July 2013<br /> | 26 July 2013<br /> | {{no|Closed}}<br /> |-<br /> | 5.1<br /> | [[k66ap|Apple TV 2G]], [[j33ap|Apple TV 3G (AppleTV3,1)]]<br /> | 24 September 2012<br /> | 20 March 2013<br /> | {{no|Closed}}<br /> |-<br /> | 6.0<br /> | [[iPad 4]], [[iPad mini 1G]]<br /> | 30 October 2012<br /> | 01 November 2012<br /> | {{no|Closed}}<br /> |-<br /> | rowspan=&quot;4&quot; | 6.0.1<br /> | [[iPad 2]], [[iPad 3]], [[iPad 4]], [[iPad mini 1G]], [[n88ap|iPhone 3GS]], [[iPhone 4]], [[n94ap|iPhone 4S]], [[iPhone 5]], [[n81ap|iPod touch 4G]], [[iPod touch 5G]]<br /> | 01 November 2012<br /> | 28 January 2013<br /> | {{no|Closed}}<br /> |-<br /> | [[iPad 4]], [[iPad mini 1G]]<br /> | 09 November 2012<br /> | 28 January 2013<br /> | {{no|Closed}}<br /> |-<br /> | [[iPad mini 1G]]<br /> | 01 November 2012<br /> | 08 January 2013<br /> | {{no|Closed}}<br /> |-<br /> | [[iPad 2]], [[iPad 3]], [[p101ap|iPad 4 (iPad3,4)]], [[p105ap|iPad mini 1G (iPad2,5)]], [[n88ap|iPhone 3GS]], [[iPhone 4]], [[n94ap|iPhone 4S]], [[iPhone 5]], [[n81ap|iPod touch 4G]], [[iPod touch 5G]]<br /> | 26 July 2013<br /> | 26 July 2013<br /> | {{no|Closed}}<br /> |-<br /> | 5.1.1<br /> | [[k66ap|Apple TV 2G]], [[j33ap|Apple TV 3G (AppleTV3,1)]]<br /> | 26 November 2012<br /> | 20 March 2013<br /> | {{no|Closed}}<br /> |-<br /> | rowspan=&quot;2&quot; | 6.0.2<br /> | [[iPad mini 1G]], [[iPhone 5]]<br /> | 18 December 2012<br /> | 28 January 2013<br /> | {{no|Closed}}<br /> |-<br /> | [[p105ap|iPad mini 1G (iPad2,5)]], [[iPhone 5]]<br /> | 26 July 2013<br /> | 26 July 2013<br /> | {{no|Closed}}<br /> |-<br /> | rowspan=&quot;2&quot; | 6.1<br /> | [[iPad 2]], [[iPad 3]], [[iPad 4]], [[iPad mini 1G]], [[n88ap|iPhone 3GS]], [[iPhone 4]], [[n94ap|iPhone 4S]], [[iPhone 5]], [[n78ap|iPod touch 5G]]<br /> | 28 January 2013<br /> | 19 February 2013<br /> | {{no|Closed}}<br /> |-<br /> | [[p106ap|iPad mini 1G (iPad2,6)]], [[n81ap|iPod touch 4G]]<br /> | 28 January 2013<br /> | 20 March 2013<br /> | {{no|Closed}}<br /> |-<br /> | {{nowrap|5.2 (6.1)}}<br /> | [[k66ap|Apple TV 2G]], [[Apple TV 3G]]<br /> | 28 January 2013<br /> | 20 March 2013<br /> | {{no|Closed}}<br /> |-<br /> | 6.1.1<br /> | [[n94ap|iPhone 4S]]<br /> | 11 February 2013<br /> | 19 February 2013<br /> | {{no|Closed}}<br /> |-<br /> | rowspan=&quot;2&quot; | 6.1.2<br /> | [[iPad 2]], [[iPad 3]], [[iPad 4]], [[iPad mini 1G]] [[n88ap|iPhone 3GS]], [[iPhone 4]], [[n94ap|iPhone 4S]], [[iPhone 5]], [[n81ap|iPod touch 4G]]<br /> | 19 February 2013<br /> | 19 March 2013<br /> | {{no|Closed}}<br /> |-<br /> | [[n78ap|iPod touch 5G]]<br /> | 19 February 2013<br /> | 20 March 2013<br /> | {{no|Closed}}<br /> |-<br /> | rowspan=&quot;3&quot; | 6.1.3<br /> | [[iPad 2]], [[iPad 3]], [[iPad 4]], [[p105ap|iPad mini 1G (iPad2,5)]], [[p107ap|iPad mini 1G (iPad2,7)]], [[iPhone 4]], [[n94ap|iPhone 4S]], [[iPod touch 5G]]<br /> | 19 March 2013<br /> | 20 September 2013<br /> | {{no|Closed}}<br /> |-<br /> | [[n88ap|iPhone 3GS]]<br /> | 19 March 2013<br /> | 21 February 2014<br /> | {{no|Closed}}<br /> |-<br /> | [[p106ap|iPad mini 1G (iPad2,6)]]<br /> | 19 March 2013<br /> | 25 September 2013<br /> | {{no|Closed}}<br /> |-<br /> | {{nowrap|5.2.1 (6.1.3)}}<br /> | [[k66ap|Apple TV 2G]], [[Apple TV 3G]]<br /> | 19 March 2013<br /> | 20 June 2013<br /> | {{no|Closed}}<br /> |-<br /> | rowspan=&quot;2&quot; | 6.1.3<br /> | [[iPhone 5]]<br /> | 19 March 2013<br /> | 02 May 2013<br /> | {{no|Closed}}<br /> |-<br /> | [[n81ap|iPod touch 4G]]<br /> | 19 March 2013<br /> | 14 November 2013<br /> | {{no|Closed}}<br /> |-<br /> | 6.1.4<br /> | [[iPhone 5]]<br /> | 02 May 2013<br /> | 20 September 2013<br /> | {{no|Closed}}<br /> |-<br /> | rowspan=&quot;2&quot; | {{nowrap|5.3 (6.1.4)}}<br /> | [[k66ap|Apple TV 2G]], [[j33ap|Apple TV 3G (AppleTV3,1)]]<br /> | 19 June 2013<br /> | -<br /> | {{yes|Open}}<br /> |-<br /> | [[j33iap|Apple TV 3G (AppleTV3,2)]]<br /> | 19 June 2013<br /> | 21 September 2013<br /> | {{no|Closed}}<br /> |-<br /> | 6.1.5<br /> | [[n88ap|iPod touch 4]]<br /> | 24 November 2013<br /> | 21 February 2014<br /> | {{no|Closed}}<br /> |-<br /> | 6.1.6<br /> | [[n88ap|iPhone 3GS]], [[n88ap|iPod touch 4]]<br /> | 24 November 2013<br /> | -<br /> | {{yes|Open}}<br /> |-<br /> | 7.0<br /> | [[iPad 2]], [[iPad 3]], [[iPad 4]], [[iPad mini 1G]], [[iPhone 4]], [[n94ap|iPhone 4S]], [[iPhone 5]], [[iPod touch 5G]]<br /> | 18 September 2013<br /> | 07 October 2013<br /> | {{no|Closed}}<br /> |-<br /> | 7.0.1<br /> | [[iPhone 5c]], [[iPhone 5s]]<br /> | 18 September 2013<br /> | 07 October 2013<br /> | {{no|Closed}}<br /> |-<br /> | {{nowrap|6.0 (7.0.1)}}<br /> | rowspan=&quot;2&quot; | [[k66ap|Apple TV 2G]], [[Apple TV 3G]]<br /> | 20 September 2013<br /> | 24 September 2013<br /> | {{no|Closed}}<br /> |-<br /> | {{nowrap|6.0 (7.0.2)}}<br /> | 24 September 2013<br /> | 29 October 2013<br /> | {{no|Closed}}<br /> |-<br /> | rowspan=&quot;2&quot; | 7.0.2<br /> | [[iPad 2]], [[iPad 3]], [[iPad 4]], [[p106ap|iPad mini 1G (iPad2,6)]], [[p107ap|iPad mini 1G (iPad2,7)]], [[iPhone 4]], [[n94ap|iPhone 4S]], [[iPhone 5]], [[iPhone 5c]], [[iPhone 5s]], [[iPod touch 5G]]<br /> | 26 September 2013<br /> | 29 October 2013<br /> | {{no|Closed}}<br /> |-<br /> | [[p105ap|iPad mini 1G (iPad2,5)]]<br /> | 26 September 2013<br /> | 21 February 2014<br /> | {{no|Closed}}<br /> |-<br /> | 7.0.3<br /> | [[iPad 2]], [[iPad 3]], [[iPad 4]], [[iPad Air]], [[iPad mini 1G]], [[iPad mini 2]], [[iPhone 4]], [[n94ap|iPhone 4S]], [[iPhone 5]], [[iPhone 5c]], [[iPhone 5s]], [[iPod touch 5G]]<br /> | 22 October 2013<br /> | 14 November 2013<br /> | {{no|Closed}}<br /> |-<br /> | {{nowrap|6.0.1 (7.0.3)}}<br /> | [[k66ap|Apple TV 2G]], [[Apple TV 3G]]<br /> | 24 October 2013<br /> | 14 November 2013<br /> | {{no|Closed}}<br /> |-<br /> | 7.0.4<br /> | [[iPad 2]], [[iPad 3]], [[iPad 4]], [[iPad Air]], [[iPad mini 1G]], [[iPad mini 2]], [[iPhone 4]], [[n94ap|iPhone 4S]], [[iPhone 5]], [[iPhone 5c]], [[iPhone 5s]], [[iPod touch 5G]]<br /> | 14 November 2013<br /> | 21 February 2014<br /> | {{no|Closed}}<br /> |-<br /> | {{nowrap|6.0.2 (7.0.4)}}<br /> | [[k66ap|Apple TV 2G]], [[Apple TV 3G]]<br /> | 14 November 2013<br /> | 21 February 2014 <br /> | {{no|Closed}}<br /> |-<br /> | 7.0.5<br /> | [[n49ap|iPhone 5c (iPhone5,4)]], [[n53ap|iPhone 5s (iPhone6,2)]]<br /> | 29 January 2014<br /> | 21 February 2014<br /> | {{no|Closed}}<br /> |-<br /> | 6.0.2 (7.0.6)<br /> | [[k66ap|Apple TV 2G]], [[Apple TV 3G]]<br /> | 21 February 2014<br /> | 10 March 2014<br /> | {{no|Closed}}<br /> |-<br /> | 7.0.6<br /> | [[iPad 2]], [[iPad 3]], [[iPad 4]], [[iPad Air]], [[iPad mini 1G]], [[iPad mini 2]], [[iPhone 4]], [[n94ap|iPhone 4S]], [[iPhone 5]], [[iPhone 5c]], [[iPhone 5s]], [[iPod touch 5G]]<br /> | 21 February 2014<br /> | 10 March 2014<br /> | {{no|Closed}}<br /> |-<br /> | 6.1 (7.1)<br /> | [[k66ap|Apple TV 2G]], [[Apple TV 3G]]<br /> | 10 March 2014<br /> | 30 April 2014<br /> | {{no|Closed}}<br /> |-<br /> | 7.1<br /> | [[iPad 2]], [[iPad 3]], [[iPad 4]], [[iPad Air]], [[iPad mini 1G]], [[iPad mini 2]], [[iPhone 4]], [[n94ap|iPhone 4S]], [[iPhone 5]], [[iPhone 5c]], [[iPhone 5s]], [[iPod touch 5G]]<br /> | 10 March 2014<br /> | 30 April 2014<br /> | {{no|Closed}}<br /> |-<br /> | 6.1.1 (7.1.1)<br /> | [[k66ap|Apple TV 2G]], [[Apple TV 3G]]<br /> | 22 April 2014<br /> | 11 July 2014<br /> | {{no|Closed}}<br /> |-<br /> | 7.1.1<br /> | [[iPad 2]], [[iPad 3]], [[iPad 4]], [[iPad Air]], [[iPad mini 1G]], [[iPad mini 2]], [[iPhone 4]], [[n94ap|iPhone 4S]], [[iPhone 5]], [[iPhone 5c]], [[iPhone 5s]], [[iPod touch 5G]]<br /> | 22 April 2014<br /> | 12 August 2014<br /> | {{no|Closed}}<br /> |-<br /> | 6.2 (7.1.2)<br /> | [[k66ap|Apple TV 2G]], [[Apple TV 3G]]<br /> | 30 June 2014<br /> | 26 September 2014<br /> | {{no|Closed}}<br /> |-<br /> | rowspan=&quot;2&quot; | 7.1.2<br /> | [[iPhone 4]]<br /> | 30 June 2014<br /> | -<br /> | {{yes|Open}}<br /> |-<br /> | [[iPad 2]], [[iPad 3]], [[iPad 4]], [[iPad Air]], [[iPad mini 1G]], [[iPad mini 2]], [[n94ap|iPhone 4S]], [[iPhone 5]], [[iPhone 5c]], [[iPhone 5s]], [[iPod touch 5G]]<br /> | 30 June 2014<br /> | 26 September 2014<br /> | {{no|Closed}}<br /> |-<br /> | 6.2.1 (7.1.2)<br /> | [[k66ap|Apple TV 2G]]<br /> | 17 September 2014<br /> | -<br /> | {{yes|Open}}<br /> |-<br /> | 7.0 (8.0)<br /> | [[Apple TV 3G]]<br /> | 17 September 2014<br /> | -<br /> | {{yes|Open}}<br /> |-<br /> | 8.0<br /> | rowspan=&quot;3&quot; | [[iPad 2]], [[iPad 3]], [[iPad 4]], [[iPad Air]], [[iPad mini 1G]], [[iPad mini 2]], [[n94ap|iPhone 4S]], [[iPhone 5]], [[iPhone 5c]], [[iPhone 5s]], [[n61ap|iPhone 6]], [[n56ap|iPhone 6 Plus]], [[iPod touch 5G]]<br /> | 17 September 2014<br /> | 22 October 2014<br /> | {{no|Closed}}<br /> |-<br /> | 8.0.1<br /> | 24 September 2014<br /> | 24 September 2014<br /> | {{no|Closed}}<br /> |-<br /> | 8.0.2<br /> | 25 September 2014<br /> | 27 October 2014<br /> | {{no|Closed}}<br /> |-<br /> | 8.1<br /> | [[iPad 2]], [[iPad 3]], [[iPad 4]], [[iPad Air]], [[iPad Air 2]], [[iPad mini 1G]], [[iPad mini 2]], [[iPad mini 3]], [[n94ap|iPhone 4S]], [[iPhone 5]], [[iPhone 5c]], [[iPhone 5s]], [[n61ap|iPhone 6]], [[n56ap|iPhone 6 Plus]], [[iPod touch 5G]]<br /> | 20 October 2014<br /> | -<br /> | {{yes|Open}}<br /> |}<br /> <br /> Note: The original [[m68ap|iPhone]] and [[n45ap|iPod touch]] don't use SHSH Blobs<br /> <br /> == Protocol ==<br /> To request a SHSH blob from Apple, a simple [[wikipedia:Hypertext Transfer Protocol|HTTP]] request can be made. For a full description, please see the separate article [[SHSH Protocol]] and [[Baseband SHSH Protocol]].<br /> <br /> == Links and Tools ==<br /> * [[Redsn0w]]<br /> * [[TinyUmbrella]] (Java needed)<br /> * [http://www.saurik.com/id/12 Detailed background info from Saurik]<br /> <br /> == See Also ==<br /> * [[APTicket]]<br /> [[Category:Firmware Tags]]</div>

Danzatt https://www.theiphonewiki.com/w/index.php?title=User:Rzhikharevich&diff=42454 2014-09-23T17:17:31Z

<p>Danzatt: Fixed this for you</p> <hr /> <div>Just an iPhone user and programmer, a [http://uncyclopedia.wikia.com/wiki/Grammar_Nazi grammar nazi] (with russian language). 13 years old, started being interested in computer science at the age of 11.<br /> PS. Not a native english-speaker.<br /> <br /> == Projects ==<br /> Here's the list of my iOS-related projects:<br /> *[https://github.com/rzhikharevich/lwvmedit lwvmedit] - first useful (?) tool for iOS, it can read and edit LwVM tables.<br /> Other projects:<br /> *[http://github.com/rzhikharevich/NyanOS NyanOS] &amp; [http://github.com/rzhikharevich/XNC XNC programming language].<br /> <br /> == Knowledge ==<br /> I know a lot about the iOS (at least relatively). I am also an experienced Unix/Linux user. <br /> <br /> Programming languages:<br /> *C/C++<br /> *Python<br /> *x86 assembly.<br /> Web design skills:<br /> *HTML5<br /> *CSS3<br /> *Javascript.<br /> <br /> == Links ==<br /> *[http://rzhikharevich.github.io My blog], under construction.<br /> *[http://github.com/rzhikharevich Github account]<br /> *[http://twitter.com/rzhikharevich Twitter]<br /> <br /> == iDevices ==<br /> *White iPad 3, 64GB, iOS 7.1.2, jailbroken.<br /> *iPhone 4, 16GB, iOS 7.1.2, jailbroken.<br /> *The original iPhone (2G), it lies somewhere deep in my room, it probably has OpeniBoot and iDroid on it.<br /> <br /> I also have limited access to an iPhone 5.<br /> <br /> == Operating systems ==<br /> In current use:<br /> *OS X Mavericks.<br /> *iOS.<br /> Used:<br /> *Windows XP/7/8<br /> *Different Linux distributions (Gentoo is my favorite)</div>

Danzatt https://www.theiphonewiki.com/w/index.php?title=/private/etc/rc.d&diff=42346 2014-09-19T11:57:45Z

<p>Danzatt: </p> <hr /> <div>All scripts and executables here seem to be executed at boot time.<br /> == Parents ==<br /> * [[/private/etc|etc]]<br /> == Children ==<br /> * [[/private/etc/substrate|substrate]]<br /> == External Links ==<br /> [https://www.freebsd.org/doc/en/articles/rc-scripting/ FreeBSD rc.d tutorial]</div>

Danzatt https://www.theiphonewiki.com/w/index.php?title=SEP&diff=42192 2014-09-16T20:12:54Z

<p>Danzatt: Redirected page to Secure Enclave</p> <hr /> <div>#REDIRECT [[ Secure Enclave ]]</div>

Danzatt https://www.theiphonewiki.com/w/index.php?title=Talk:LwVM&diff=42183 2014-09-15T18:24:33Z

<p>Danzatt: Err...</p> <hr /> <div>== Volume manager ==<br /> Volumes can be managed using LightweightVolumeManager kext. You can interface with it using IOKit (which is well documented by Apple, example usage can be seen at [https://github.com/comex/attach-and-detach comex's attach-and-detach] utility). The deal is to reverse engineer the right interface, selector codes, ... Probably restore ramdisk might contain some useful binaries which make us of this kext (or disassemble the kext itself). --[[User:Danzatt|Danzatt]] ([[User talk:Danzatt|talk]]) 18:23, 15 September 2014 (UTC)</div>

Danzatt https://www.theiphonewiki.com/w/index.php?title=Talk:LwVM&diff=42182 2014-09-15T18:23:41Z

<p>Danzatt: Created page with &quot;== Volume manager == Volumes can be managed by using LightweightVolumeManager kext. You can interface with it using IOKit (which is well documented by Apple, example usage can...&quot;</p> <hr /> <div>== Volume manager ==<br /> Volumes can be managed by using LightweightVolumeManager kext. You can interface with it using IOKit (which is well documented by Apple, example usage can be seen at [https://github.com/comex/attach-and-detach comex's attach-and-detach] utility). The deal is to reverse engineer the right interface, selector codes, ... Probably restore ramdisk might contain some useful binaries which make us of this kext (or disassemble the kext itself). --[[User:Danzatt|Danzatt]] ([[User talk:Danzatt|talk]]) 18:23, 15 September 2014 (UTC)</div>

Danzatt https://www.theiphonewiki.com/w/index.php?title=LwVM&diff=42181 2014-09-15T18:14:59Z

<p>Danzatt: </p> <hr /> <div>'''LwVM''' (Lightweight Volume Manager) - partition table, which is used by iOS since 5.0.<br /> <br /> <br /> == Structure ==<br /> &lt;pre&gt;<br /> typedef struct _LwVMPartitionRecord {<br /> uint64_t type[2]; //Should be equal to LwVMPartitionTypeHFS (see below) on an unmodified device.<br /> uint64_t guid[2]; //Random.<br /> uint64_t begin; //Partitions begin in bytes.<br /> uint64_t end; //End.<br /> uint64_t attribute; // 0 == unencrypted; 0x1000000000000 == encrypted<br /> char partitionName[0x48]; //For an unknown reason every char is separated by null.<br /> } __attribute__ ((packed)) LwVMPartitionRecord;<br /> <br /> typedef struct _LwVM {<br /> uint64_t type[2]; //Should be LwVMType or LwVMType_noCRC.<br /> uint64_t guid[2]; //Random.<br /> uint64_t mediaSize; //Size in bytes.<br /> uint32_t numPartitions; //Number of partitions.<br /> uint32_t crc32;<br /> uint8_t unkn[464]; //Some unknown bytes, usually nulls.<br /> LwVMPartitionRecord partitions[12];<br /> uint16_t chunks[1024]; // chunks[0] should be 0xF000<br /> } __attribute__ ((packed)) LwVM;<br /> <br /> static const char LwVMType[] = { 0x6A, 0x90, 0x88, 0xCF, 0x8A, 0xFD, 0x63, 0x0A, 0xE3, 0x51, 0xE2, 0x48, 0x87, 0xE0, 0xB9, 0x8B };<br /> <br /> static const char LwVMType_noCRC[] = { 0xB1, 0x89, 0xA5, 0x19, 0x4F, 0x59, 0x4B, 0x1D, 0xAD, 0x44, 0x1E, 0x12, 0x7A, 0xAF, 0x45, 0x39 };<br /> <br /> static const char LwVMPartitionTypeHFS[] = { 0x48, 0x46, 0x53, 0x00, 0x00, 0x00, 0x11, 0xAA, 0xAA, 0x11, 0x00, 0x30, 0x65, 0x43, 0xEC, 0xAC };<br /> &lt;/pre&gt;<br /> <br /> == Tools ==<br /> [http://www.github.com/rzhikharevich/lwvmedit lwvmedit]<br /> <br /> == External links ==<br /> [https://code.google.com/p/iphone-dataprotection/wiki/LightweightVolumeManager iPhone dataprotection wiki]</div>

Danzatt https://www.theiphonewiki.com/w/index.php?title=LwVM&diff=42180 2014-09-15T18:14:05Z

<p>Danzatt: </p> <hr /> <div>'''LwVM''' (Lightweight Volume Manager) - partition table, which is used by iOS since 5.0.<br /> <br /> <br /> == Structure ==<br /> &lt;pre&gt;<br /> typedef struct _LwVMPartitionRecord {<br /> uint64_t type[2]; //Should be equal to LwVMPartitionTypeHFS (see below) on an unmodified device.<br /> uint64_t guid[2]; //Random.<br /> uint64_t begin; //Partitions begin in bytes.<br /> uint64_t end; //End.<br /> uint64_t attribute; // 0 == unencrypted; 0x1000000000000 == encrypted<br /> char partitionName[0x48]; //For an unknown reason every char is separated by null.<br /> } __attribute__ ((packed)) LwVMPartitionRecord;<br /> <br /> typedef struct _LwVM {<br /> uint64_t type[2]; //Should be LwVMType or LwVMType_noCRC.<br /> uint64_t guid[2]; //Random.<br /> uint64_t mediaSize; //Size in bytes.<br /> uint32_t numPartitions; //Number of partitions.<br /> uint32_t crc32;<br /> uint8_t unkn[464]; //Some unknown bytes, usually nulls.<br /> LwVMPartitionRecord partitions[12];<br /> uint16_t chunks[1024]; // chunks[0] should be 0xF000<br /> } __attribute__ ((packed)) LwVM;<br /> <br /> static const char LwVMType[] = { 0x6A, 0x90, 0x88, 0xCF, 0x8A, 0xFD, 0x63, 0x0A, 0xE3, 0x51, 0xE2, 0x48, 0x87, 0xE0, 0xB9, 0x8B };<br /> <br /> static const char LwVMType_noCRC[] = { 0xB1, 0x89, 0xA5, 0x19, 0x4F, 0x59, 0x4B, 0x1D, 0xAD, 0x44, 0x1E, 0x12, 0x7A, 0xAF, 0x45, 0x39 };<br /> <br /> static const char LwVMPartitionTypeHFS[] = { 0x48, 0x46, 0x53, 0x00, 0x00, 0x00, 0x11, 0xAA, 0xAA, 0x11, 0x00, 0x30, 0x65, 0x43, 0xEC, 0xAC };<br /> &lt;/pre&gt;<br /> <br /> == Tools ==<br /> [http://www.github.com/rzhikharevich/lwvmedit lwvmedit]<br /> <br /> == External links ==<br /> [https://code.google.com/p/iphone-dataprotection/wiki/LightweightVolumeManager description of LwVM on iPhone dataprotection wiki]</div>

Danzatt https://www.theiphonewiki.com/w/index.php?title=The_iPhone_Wiki:Community_portal&diff=42171 2014-09-15T09:58:35Z

<p>Danzatt: </p> <hr /> <div>{{Talk Archive}}<br /> {{see also|Unsolved problems}}<br /> ==iPhone serial cable==<br /> Could somebody document how to use uart cable (i.e. setup, bitrate, ...) ? Some intructions are available at [http://www.instructables.com/id/Apple-iOS-SerialUSB-Cable-for-Kernel-Debugging/ instructables]. Can two iPhones' serial inputs be connected to each other (i.e. TX of 1st iPhone to RX of 2nd and RX of first to TX of second) and minicom used on one of them to connect to /dev/uart.iap such that no USB to 3.3V TTL (FT232RL in the link) would be needed provided that you already have multiple iDevices with dock connector<br /> ==iPhone-Elite==<br /> 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.<br /> --[[User:Http|http]] 15:02, 26 June 2012 (MDT)<br /> <br /> ==Boot-args cleanup==<br /> 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:<br /> *[[Kernel#Boot-Args]] A section with the latest boot arguments list. This should be a short introduction and having a link &quot;main article&quot;.<br /> *[[Boot-args (iBoot variable)]] separate page for boot arguments, but mainly for the iBoot variable that doesn't exist any longer<br /> *[{{FULLURL:Boot arguments|redirect=no}} Boot arguments] (redirect)<br /> *[[:Talk:Restore_Mode]] describing the iBoot variable problem<br /> *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)<br /> *My earlier comment [[:Talk:Kernel#boot-args]]<br /> *This comment here.<br /> 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 &quot;main article there&quot;. What do you think? --[[User:Http|http]] ([[User talk:Http|talk]]) 21:31, 13 February 2013 (UTC)<br /> :I like [[Boot Arguments]]. --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 02:01, 14 February 2013 (UTC)<br /> ::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)<br /> <br /> ==The iPhone Wiki re-design==<br /> The design of the iPhone wiki is now quite old and I think it should be updated. I made a [http://oi42.tinypic.com/30ib9y8.jpg concept]. --[[User:Jaggions|Jaggions]] ([[User talk:Jaggions|talk]]) 10:30, 14 June 2013 (UTC)<br /> :I disagree. If anything add an iPhone 5 to the logo but everything else is ok. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 11:05, 14 June 2013 (UTC)<br /> :I wouldn't change the logo to an iPhone 5, especially with iOS 7 and a new iPhone (that will probably look the same as the 5, admittedly) around the corner. I contemplated updating the CSS for iOS 7's UI but decided not to because of the UI's supposed volatility (during the beta period) and I don't have a live version to toy around with. (I personally don't like its current state, but that's not a factor in why I'm not changing it yet.) --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 16:25, 14 June 2013 (UTC)<br /> ::Can we not do flat? --[[User:Haifisch|Haifisch]] ([[User talk:Haifisch|talk]]) 21:02, 14 June 2013 (UTC)<br /> ::This is what I was thinking. When iOS 7 finally comes out, we could change the CSS to look like that instead. --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 21:11, 14 June 2013 (UTC)<br /> :::iOS 7 looks ugly. We do not want it like that. Maybe a bit more modern but nothing much. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 21:16, 14 June 2013 (UTC)<br /> ::::''You'' may not want it like that. That's your opinion. --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 01:55, 15 June 2013 (UTC)<br /> :::::We could make a poll, and see if most users agree or disagree. --[[User:Jaggions|Jaggions]] ([[User talk:Jaggions|talk]]) 10:05, 15 June 2013 (UTC)<br /> :The idea looks nice. But before we make any changes, let's wait until iOS7 comes out. And I'd prefer to just add another skin instead (if possible). I'm still using the classic MonoBook skin by the way. You shouldn't impose design changes to everyone. --[[User:Http|http]] ([[User talk:Http|talk]]) 14:38, 15 June 2013 (UTC)<br /> ::The problem with skins is that geohot needs to set them up... An idea I have is that we copy the Vector skin verbatim to a new skin (&lt;code&gt;iOS6&lt;/code&gt;) and move the modifications (not general stuff) to [[Mediawiki:iOS6.css]]. Then we can do another verbatim copy to &lt;code&gt;iOS7&lt;/code&gt; and modify [[Mediawiki:iOS7.css]]. We could then set the default skin to either &lt;code&gt;iOS6&lt;/code&gt; or &lt;code&gt;iOS7&lt;/code&gt; so you don't need to be logged in to see them like currently. Then if someone doesn't like them, like you, just change your settings to your preferred skin. The only way around needing geohot is if he opens up the credentials to FTP or whatever to someone. --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 21:17, 15 June 2013 (UTC)<br /> :::I like [[User:5urd|5urd]]'s suggestion. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 22:29, 15 June 2013 (UTC)<br /> What about just removing the text-shadow element for now? I think pages would be easier to read without it. Here's an example: [[:File:Noshadow.png]]. [[User:Britta|Britta]] ([[User talk:Britta|talk]]) 00:11, 29 August 2013 (UTC)<br /> :Yeah removing the shadow will make everything seem more flat but like [[User:http|http]] I'm still using the classic [http://theiphonewiki.com/w/index.php?title=Main_Page&amp;useskin=monobook MonoBook skin] --[[User:Jaggions|Jaggions]] ([[User talk:Jaggions|talk]]) 21:19, 31 August 2013 (UTC)<br /> <br /> ==Hacker page==<br /> I would like to be added to the list of hackers for my work with the Private Dev Team and the [[Chronic Dev (team)|Chronic Dev Team]] in addition to my release of the Phoenix Semi-Untethered. --[[User:Ph0enix|Ph0enix]] ([[User talk:Ph0enix|talk]]) 18:36, 22 July 2013 (UTC)<br /> :Did you find any exploits? --[[User:Haifisch|Haifisch]] ([[User talk:Haifisch|talk]]) 18:54, 22 July 2013 (UTC)<br /> ::No. [[User:phyrrus9|phyrrus9]], a team member found the vulnerability. I am the one who exploited it. --[[User:Ph0enix|Ph0enix]] ([[User talk:Ph0enix|talk]])<br /> :::I can back up this &quot;claim&quot;. I was a part of it. --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 20:52, 28 July 2013 (UTC)<br /> ::::Whatever happened to this? --[[User:Phyrrus9|phyrrus9]]<br /> :::::So this went cold and i am going to again request that this change be made. --[[User:Ph0enix|Ph0enix]] ([[User talk:Ph0enix|talk]]) 18:28, 13 January 2014 (UTC)<br /> ::::::I'm gonna say no. I don't see any notable accomplishments to merit this. --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 21:53, 13 January 2014 (UTC)<br /> ::::::'''No'''. The first step would be to get to the category [[:Category:Hackers|hackers]]. You can get there by finding a vulnerability that is used with an exploit in a jailbreak - or by writing a new exploit. Remember that it's not allowed to add yourself to that category. Instead of finding a vulnerability you could also be member of either The [[iPhone Dev Team]] or [[Chronic Dev]] or [[evad3rs]]. After being in that category, the next step would be that you're famous enough from all those hackers there to get to the main page. The people chosen are discussed here. --[[User:Http|http]] ([[User talk:Http|talk]]) 23:42, 13 January 2014 (UTC)<br /> <br /> ==Orphaned articles==<br /> This is an interesting search: [[Special:LonelyPages]] - &quot;The following pages are not linked from or transcluded into other pages in The iPhone Wiki.&quot; I'm not sure where all of those articles should be linked, but figuring that out could be a useful project for somebody. [[User:Britta|Britta]] ([[User talk:Britta|talk]]) 05:57, 28 August 2013 (UTC)<br /> <br /> ==Easy tasks for new editors==<br /> * 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 &quot;FF&quot; so it should be in the format &quot;0xe80000&quot; followed by two numbers) --[[User:Dirkg|Dirkg]] ([[User talk:Dirkg|talk]]) 22:40, 28 August 2013 (UTC)<br /> <br /> == A1XXX model numbers vs. &quot;GSM&quot;/&quot;CDMA&quot;/&quot;Global&quot;/&quot;Cellular&quot;/etc. ==<br /> I know that this topic was [[The iPhone Wiki:Community portal/2013#iPhone 5|already discussed earlier this year]], but it didn't seem to come to a consensus, and the introduction of the [[iPhone 5c]] and [[iPhone 5s]] brought a lot of model numbers. Some of them may &quot;overlap&quot; (think models A1429 and A1442 for the [[iPhone 5]]), but there's simply too many to give names to. There are at least two that can connect to CDMA networks, and all of them can connect to GSM. In addition, with the sheer amount of models, it doesn't seem likely for one model to be treated as a &quot;global&quot; model. Therefore, I changed the iPhone 5c to use model numbers. I would like to do the same to some of the devices that are already present on the wiki though— the same ones from when I first brought up this idea. The GSM/CDMA names work very well for the [[iPad 2]] and [[iPhone 4]]. Things are slightly murkier for the [[iPad 3|iPad (3rd gen.)]], [[iPad 4|iPad (4th gen.)]], [[iPad mini 1G]], and [[iPhone 5]] though; all of those devices' cellular models can connect to GSM networks, so it seems like nonsense to call some of them the &quot;GSM model.&quot; The A1XXX model numbers are also how Apple tells the difference between the different models of these devices. Have any opinions changed? Or perhaps someone new might have something to say about this? --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 06:06, 13 September 2013 (UTC)<br /> <br /> :I actually like the idea as it does get complicated now with the new devices coming like said and we would have to do this for all devices. Although, if we did this, we would have to move all the key pages that have keys on to support this. That would not be a big problem as we could limit the moves to say 20 per day. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 09:47, 13 September 2013 (UTC)<br /> <br /> :I suggest we wait a bit until we see what models of the [[iPhone 5c]] and [[iPhone 5s]] will exist. But in general, I like the idea of using only the A1nnn numbers. The only issue I see right now is that Apple differentiates between A1532 GSM and A1532 CDMA. If there are real hardware differences between these two, then we're screwed again. That's why I suggest to wait until we know these exact model types. On the disambiguation page I added the GSM/CDMA model differentiation already (as Apple does). If they turn out to be the same, we can remove it again, but I wonder why Apple lists two models (with different bands supported) there now. Someone also added the &quot;CDMA&quot; mark to one of the others, but that's not how Apple marks them, so I suggest to remove that mark there again. If everything can be differentiated by these A-model-numbers, then yes, we should change the old pages too. Including all key pages. --[[User:Http|http]] ([[User talk:Http|talk]]) 14:44, 13 September 2013 (UTC)<br /> <br /> ::I do know there are 2 CDMA and 3-4 GSM for the [[iPhone 5c]] alone. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 16:04, 13 September 2013 (UTC)<br /> <br /> :::Ahem… ''All'' of the iPhone 5c models can do GSM communications. Hence one of the reasons why I want to ditch the &quot;GSM&quot;/&quot;Global&quot;/etc. labels in favor of A1XXX model numbers. ;P --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 16:07, 13 September 2013 (UTC)<br /> <br /> ::::One thing is, what about iPod touch 5 as that has two model numbers that are the same device, same with iPhone5,2. How would we get around that? I suppose we could like both separated with a forward slash. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 18:19, 13 September 2013 (UTC)<br /> <br /> :::::Yeah, we could just use something like &quot;[[n42ap|iPhone 5 (Model A1429/A1442)]].&quot; --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 22:45, 13 September 2013 (UTC)<br /> <br /> ::::::Yeah I thought that but what about the iPhone 4 GSM and GSM Rev A? They both seem to be A1432. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 23:10, 13 September 2013 (UTC)<br /> <br /> :::::::This is why I'm against using the A1XXX model numbers instead of the current GSM/Global thing. --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 23:25, 13 September 2013 (UTC)<br /> <br /> ::::::::I had no plans to change the way we refer to the iPhone 4 or iPad 2 (Apple does use GSM/CDMA, and for those devices it works fine). If a new iPhone 5S revision comes along, Apple will probably refer to it as a &quot;Rev A&quot; thing, and so will we. --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 02:50, 14 September 2013 (UTC)<br /> <br /> :Referencing Adam's reply above, if we had took that to the key pages, it'd be &lt;code&gt;[&lt;nowiki/&gt;[{BuildTrain} {Build} (A1432)]]&lt;/code&gt; which would mess ''everything'' up. What could we do? Use &lt;code&gt;[&lt;nowiki/&gt;[{BuildTrain} {Build} (A1432 Rev A)]]&lt;/code&gt;? No. That doesn't look good. The current way of referring to everything by their supported network type (GSM/CDMA/Global) helps in going to a different page.<br /> :Let's say I'm on [[BrightonMaps 10B329 (iPhone 4 GSM)]] and I want to go the CDMA device. What do I do? Go to the URL and replace &lt;code&gt;GSM&lt;/code&gt; with &lt;code&gt;CDMA&lt;/code&gt;. With the model numbers, I'd have to navigate to [[Firmware]], then find the link, or find out what the model number of the CDMA variant is and replace the model number in the URL with that.&lt;br /&gt;<br /> :Ok, who navigates by the URL and search bar? ''I do''. And I'm sure there's '''many''' people out there that prefer to navigate with the search bar if they know the page name. If we go by model number, the AJAX search results just list pages with a model number in parenthesis. '''How does that help'''? I'd either have to ''know'' the model number of the device I want, or visit ''each one'' until I find the page I need.<br /> :Sorry for the rant, but I am '''strongly''' against this. --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 23:25, 13 September 2013 (UTC)<br /> <br /> ::I do suppose we could just trash the buildtrain all together to shorten it down too. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 23:32, 13 September 2013 (UTC)<br /> <br /> :::Dropping the Build Train would only ''increase'' the workload. Besides, what's the harm with it? We've been using the same page title structure since forever, and it's worked. &quot;''If it ain't broke, don't fix it''&quot;. The current system works, so ''why'', other than the fact that Apple refers to them differently, should we change this? In addition, we don't refer to everything the way Apple does. The [[iPad mini 1G]] is referred to as the &quot;iPad mini&quot;. The [[iPad 3]] is refered to as &quot;The New iPad&quot;. The [[iPad 4]] is refered to as &quot;iPad with Retina Display&quot;&lt;sup class=&quot;plainlinks&quot;&gt;[http://www.apple.com/ipad/compare/]&lt;/sup&gt;. Are the key pages titled &lt;code&gt;BrightonMaps 10B329 (The New iPad, Wi-Fi+3G for AT&amp;T and Verizon)&lt;/code&gt;? No. --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 00:37, 14 September 2013 (UTC)<br /> <br /> ::::But the reason we want to not use the variants is because the new devices that are coming out are breaking he structure and also CDMA versions can use GSM in the 5c plus we have like 4 for GSM alone. I only meant drop buildtrain to shorten the urls down. For the iPhone 4 GSM Rev A we would have to list it as &lt;code&gt;iPhone 4 A1432 Rev&lt;/code&gt; unless another idea is thought of. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 00:55, 14 September 2013 (UTC)<br /> <br /> :::::No. Anything involving moving key pages to change their title I am ''completely'' against. As for the iPhone 5s and iPhone 5c, we ultimately have to wait. There may be different types, but if they all work with the same firmware, then what do we do then? Use &lt;code&gt;A1456/A1504&lt;/code&gt;? I don't want to do that. It can get confusing in the future if that list were to be huge. With ''5'' different models for the iPhone 5c ''alone'', it's just not practical. For the fact that all support GSM, but not all support CDMA, we just do what we've ''been'' doing: &quot;GSM&quot; and &quot;Global&quot;. --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 01:22, 14 September 2013 (UTC)<br /> <br /> ::::::There's nothing wrong with changing the titles of pages that don't even exist though. If *all* of the models use the same firmware, just go with &quot;iPhone 5s.&quot; If they happen to be partitioned into two different firmwares again, that will certainly complicate things, but it wouldn't be worse than nonsense like &quot;GSM,&quot; &quot;GSM [&lt;nowiki /&gt;Global],&quot; &quot;CDMA,&quot; &quot;CDMA [&lt;nowiki /&gt;Global],&quot; or &quot;GSM [&lt;nowiki /&gt;Global Plus TD-LTE].&quot; If it's just one oddball, we could just have &quot;iPhone 5s&quot; and &quot;iPhone 5s A1XXX&quot; (whatever the odd one is), and include a link on the former page to say &quot;keys for model A1XXX are on this page.&quot; --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 02:50, 14 September 2013 (UTC)<br /> <br /> ::::I probably didn't phrase that well… I wasn't thinking of how Apple markets the product, but rather more along the lines of how they refer to it in, say, the tech specs page or support documents— the pages that shows the messier side to their simple sugar coating. --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 02:50, 14 September 2013 (UTC)<br /> <br /> ::You keep misinterpreting/misrepresenting what I'm proposing. I never said anything about dropping, say, &quot;iPhone 5&quot; so firmware page titles would look like [[Sundance 10A405 (A1428)]]. I want to change the GSM/Global part to the A1XXX number, so it would probably show like [[Sundance 10A405 (iPhone 5 A1428)]]. (If a hardware revision were made, it would probably look like [[Sundance 10A405 (iPhone 5 A1428 Rev A)]].) From time to time, I edit URLs to browse the wiki too. But the GSM/Global identifiers don't work that well; again, '''all iPhone 5 models can connect to GSM'''. That's not really helpful. --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 02:50, 14 September 2013 (UTC)<br /> <br /> :::I suggest we drop the A and use Rev. As for the idea of changing to A1XXX, I see no issues and am for the idea. I admit it can cause chaos when we move the pages but we could limit the moving per day of course. Overall, I think it will be worth it. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 10:01, 14 September 2013 (UTC)<br /> <br /> ::::No. Don't drop the &lt;code&gt;A&lt;/code&gt; from &lt;code&gt;Rev A&lt;/code&gt;. Why would you even think to? You want to call them what Apple calls them, and the [[n90bap|revised iPhone 4 GSM]] is referred to with &lt;code&gt;Rev A&lt;/code&gt;. In addition, there have been &lt;code&gt;Rev ''B''&lt;/code&gt; things before, such as the [[S5L8947]] (A5 Rev B) used in the [[j33iap|revised Apple TV 3G]]. In addition, think of all the redirects we would need to keep for sites that link to key pages directly. I have even seen sites that still link with the URLs as &lt;code&gt;/wiki/index.php?title={Title}&lt;/code&gt; instead of the year old change to &lt;code&gt;/wiki/{Title}&lt;/code&gt;. The wiki handles that internally for us, but the redirects made in the moves would have to be kept. Currently, only the [[iPhone 5]] and [[iPad 4]] are the only devices referred to by their model numbers. --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 20:53, 14 September 2013 (UTC)<br /> <br /> :::That's why I don't want to change it. It's worked for us, and we have no idea how the new firmwares will be handled. I am betting that there will only be two firmware types - one for the GSM, and one for the Global (GSM+CDMA) model. The only reason they are split, IIRC, is because AT&amp;T uses different LTE bands than rest of the GSM world.<br /> :::Ultimately, the GSM/CDMA/Global monikors haven't caused any ''naming conflicts''. Ok, you don't want to use the ''marketing'' title. What about the way they are referred to on [[Apple Developer Center|ADC]], because that seems to be what you want. I may be misreading what you're saying again, but if we're going to do that, let's use their ''full'' title. Something &lt;code&gt;(iPad [4th generation Model A1458])&lt;/code&gt; (iPad 4 Wi-Fi) and &lt;code&gt;(iPad Wi-Fi + Cellular [model for Verizon])&lt;/code&gt; (iPad 3 Global). Does the first one tell you if the device is Wi-Fi or a Wi-Fi+3G model? Does the second one tell you ''at all'' that it is an [[iPad 3]], or that it supports GSM? No.<br /> :::Apple has a history of being inconsistent. For example, the iPad 3 Wi-Fi is referred to on ADC (and iTunes) as &quot;iPad Wi-Fi (3rd generation)&quot; while the iPad 3 GSM is referred to as &quot;iPad Wi-Fi + Cellular [model for AT&amp;T]&quot;. What happened to the &quot;3rd generation&quot;? --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 20:53, 14 September 2013 (UTC)<br /> <br /> ::::We could always list as &lt;code&gt;iPhone 4 (iPhone3,1)&lt;/code&gt; etc instead if that would be better. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 21:13, 14 September 2013 (UTC)<br /> <br /> ::::Why is there a need to explicitly keep &quot;Wi-Fi&quot; in a key page's title? All you need is a way to distinguish what model it is from its other variants— the A1XXX model number does just that. It's not like we referred to the AppleTV3,2 as &quot;Apple TV 3G (New Single-Core A5)&quot; or something. And obviously, we can use common sense to address the 3rd generation iPad issue you brought up… Now you're just nitpicking. --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 05:28, 15 September 2013 (UTC)<br /> :::::Actually, I think we should wait until we see the firmware for iPhone 5c/5s and then decide. TBH, as [[User:5urd|5urd]] said, it is ok as it is but of course if once the new firmware is out it is more confusing, then we can think again. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 14:12, 15 September 2013 (UTC)<br /> <br /> :::::Come to think of it, we can use a mix of both; we can keep the &quot;Global&quot; moniker, but drop the &quot;GSM&quot; moniker in favor of the A1XXX model number. (The &quot;GSM&quot; moniker is the one that's been bothering me.) I think this works well for the iPad 3 (which is actually split into &quot;CDMA&quot; and &quot;Global—&quot; it probably doesn't need to be done for this), iPad 4, iPad mini 1G, and iPhone 5, but this leaves the question of what to do for the iPhone 5C/5S. --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 04:04, 19 September 2013 (UTC)<br /> <br /> ::::::That would look worse! If we are going to do it, we have to do it for '''''all'''''. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 09:40, 19 September 2013 (UTC)<br /> <br /> :::::::What is the status on this now? --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 21:18, 9 November 2013 (UTC)<br /> <br /> :::::This discussion has stagnated, but I'm firing it up again— I want to fix this before the end of the year, so this can probably be seen as an ultimatum. Now that Apple has pushed a 7.1 beta to developers, we now know how Apple's splitting the new iPhones up— and it's by A1XXX model numbers still. :\ That's probably the path the wiki will go down, but I do have another idea. The other idea I have in mind is using the A1XXX model number for the cellular devices launched last year. But for this year's iPhones, the FCC ID is actually different between the two, so we could actually use that. Before this gets nitpicked on, the last letter can get changed to an &quot;X&quot; to signify that it's a wildcard of sorts. It's not a pretty solution so I do expect it to get shot down (hence why I'm going with the A1XXX model numbers unless everyone says otherwise), but I'm still throwing it out there in case everyone actually likes that. Everyone is welcome to suggest alternatives, but I '''will''' eliminate that GSM label before the year ends. --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 18:31, 18 November 2013 (UTC)<br /> <br /> ::::::That is worse, nobody knows the FCC ID off the top of their head. I would suggest &quot;iPhone 5 (iPhone5,1)&quot; if anything. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 18:37, 18 November 2013 (UTC)<br /> <br /> :::::::Using &quot;iPhone5,1&quot; or &quot;iPhone6,2&quot; is even ''less'' friendly… The FCC ID can be looked up in Settings or the back of a device. --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 19:06, 18 November 2013 (UTC)<br /> <br /> ::::::::Well that is not the point. I say either use the firmware name or leave it alone. See what others thing though. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 19:13, 18 November 2013 (UTC)<br /> <br /> :::::::::I currently plan on using the A1XXX model numbers— the FCC ID proposal was just thrown out there in the off chance that someone might like it. I'm not really a fan of it myself, but the FCC ID is probably the simplest way to figure out if it's an iPhone6,1 or iPhone6,2 since both have multiple A1XXX model numbers. --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 19:19, 18 November 2013 (UTC)<br /> <br /> ::::::I agree to get rid of the &quot;GSM&quot; name, as almost all iPhones support GSM. The Axxxx numbers would be nice, but as some phones have several numbers, like A1457/A1518/A1528/A1530 (what is actually different between them?) we can't use it. For the FCC-ID, we can't use that either, because for example the iPhone 5 with FCC-ID BCG-E2599A stands for the GSM/A1428 and also for the GSM+CDMA/A1429 version. So I suggest to either use the identifier (like iPhone2,1) or better the internal name (like n88ap). That would have the advantage to separate them further, because the iPhone 4 A1332 has two internal versions: iPhone3,1/n90ap and the iPhone3,2/n90bap. The bigger question is where you want to use this. That determines mainly the name. On all the key pages? Then it must be a name that is different between models that use different firmwares. And regarding key pages, maybe we should delete all the key pages from this wiki and move them into some database instead and provide a nice user interface and API around it and integrate that into the wiki somehow. That way we can change all pages with one simple edit. For the name, I prefer the internal name. --[[User:Http|http]] ([[User talk:Http|talk]]) 23:43, 18 November 2013 (UTC)<br /> <br /> :::::::We would have to edit key pages too. They should not be removed however. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 23:46, 18 November 2013 (UTC)<br /> <br /> :::::::Well, I wasn't trying to say that we had to decide on one way to differentiate ''everything''; &quot;GSM&quot; does work fine for, say, the iPhone 4. The proposal I brought up today was using the FCC ID only for this year's (2013's) iPhones— last year's cellular devices would get the A1XXX model numbers (i.e. two different solutions for two different years). But as of right now, I like how using A1XXX model numbers sounds for all of the affected devices, mostly because that's the path Apple's going in their developer portal. Something like &quot;iPhone 5s (Model A1457/A1518/A1528/A1530)&quot; is admittedly a mouthful for this year's iPhones though. At the moment, I'm inquiring about how to label it on [[Firmware]] and such pages, but I'm sure the outcome can be adapted for key page titles as well. As for differences between the models, it seems to be the supported LTE bands. --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 03:49, 19 November 2013 (UTC)<br /> <br /> :::::::::I still think that unless it is &quot;iPhone 5 (iPhone5,1)&quot; it will be complicated but on the other hand, I kind of like the idea that [[User:Http|http]] had, using the internal identifiers like this &quot;iPhone 5 (n42ap)&quot;. The only problem is that it would cause quite a bit of a flood moving the key pages, although this can be done like 15 per day each or something. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 09:20, 19 November 2013 (UTC)<br /> <br /> ::::::::::I'm pretty sure the only key page that exists for an A5 (or newer) device is [[Telluride 9A406 (iPhone 4S)]]. --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 17:40, 21 November 2013 (UTC)<br /> <br /> :::::::::::That was an example. I know there are no more A5 pages, only the one you said and two beta for iPhone 4S. I just meant that it would show the design. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 13:36, November 21, 2013 (UTC)<br /> <br /> == &quot;GSM&quot; Replacement Proposals ==<br /> Since this discussion has become extremely lengthy, here are the proposals (to my understanding) for changing the labels, each of which can be subject to changes (i.e. dropping the word &quot;Model&quot; from Proposal A). In an effort to conserve space (ironically, this still adds a significant amount of length), I only included a few models, which should give an idea of the proposal. Basically anything with an A5 or newer is involved. Feel free to edit this list if I missed or totally misinterpreted something. --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 03:25, 22 November 2013 (UTC)<br /> # Proposal A (A1XXX numbers)<br /> #* iPad 4 (Model A1458)<br /> #* iPad 4 (Model A1459)<br /> #* iPad 4 (Model A1460)<br /> #* iPhone 5 (Model A1428)<br /> #* iPhone 5 (Model A1429/A1442)<br /> #* iPhone 5c (Model A1456/A1532)<br /> #* iPhone 5c (Model A1507/A1516/A1526/A1529)<br /> #* [[InnsbruckTaos 11B554a (iPad 4 A1458)]]<br /> #* [[InnsbruckTaos 11B554a (iPhone 5 A1429/A1442)]]<br /> #* [[InnsbruckTaos 11B554a (iPhone 5c Model A1507/A1516/A1526/A1529)]]<br /> # Proposal B (A1XXX + FCC ID)<br /> #* iPad 4 (Model A1458)<br /> #* iPad 4 (Model A1459)<br /> #* iPad 4 (Model A1460)<br /> #* iPhone 5 (Model A1428)<br /> #* iPhone 5 (Model A1429/A1442)<br /> #* iPhone 5c (BCG‑E2644A)<br /> #* iPhone 5c (BCG‑E2694X)<br /> #* [[InnsbruckTaos 11B554a (iPad 4 A1458)]]<br /> #* [[InnsbruckTaos 11B554a (iPhone 5 A1429/A1442)]]<br /> #* [[InnsbruckTaos 11B554a (iPhone 5c BCG‑E2694X)]]<br /> # Proposal C (-AP Identifier)<br /> #* iPad 4 (p101ap)<br /> #* iPad 4 (p102ap)<br /> #* iPad 4 (p103ap)<br /> #* iPhone 5 (n41ap)<br /> #* iPhone 5 (n42ap)<br /> #* iPhone 5c (n48ap)<br /> #* iPhone 5c (n49ap)<br /> #* [[InnsbruckTaos 11B554a (iPad 4 p101ap)]]<br /> #* [[InnsbruckTaos 11B554a (iPhone 5c n42ap)]]<br /> #* [[InnsbruckTaos 11B554a (iPhone 5c n49ap)]]<br /> # Proposal D (iPhoneX,Y Identifier)<br /> #* iPad 4 (iPad3,4)<br /> #* iPad 4 (iPad3,5)<br /> #* iPad 4 (iPad3,6)<br /> #* iPhone 5 (iPhone5,1)<br /> #* iPhone 5 (iPhone5,2)<br /> #* iPhone 5c (iPhone5,3)<br /> #* iPhone 5c (iPhone5,4)<br /> #* [[InnsbruckTaos 11B554a (iPad3,4)]]<br /> #* [[InnsbruckTaos 11B554a (iPhone5,2)]]<br /> #* [[InnsbruckTaos 11B554a (iPhone5,4)]]<br /> <br /> <br /> :I like this [[InnsbruckTaos 11B554a iPad 4 (3,4)]] or [[InnsbruckTaos 11B554a iPad 4 (iPad3,4)]]. I see there are 4 ways to approach this;<br /> 1. Change every single device.&lt;br /&gt;<br /> 2. Change just devices with different variants, iPad 2+, iPad mini+, iPhone 4, iPhone 5+.&lt;br /&gt;<br /> 3. Change A5+ only (which I hate the idea of).&lt;br /&gt;<br /> 4. Change nothing at all.&lt;br /&gt;<br /> --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 09:28, 22 November 2013 (UTC)<br /> ::My intention for this was to be a ''neutral'' (i.e. opinion-free) spot where all of the proposals were being mentioned, so people could easily see the proposed changes without any bias… v.v --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 20:54, 22 November 2013 (UTC)<br /> :::TBH, I think it is better as it is, but I just stated my opinion that only A5+ would make in inconsistent. Though you could argue it is already, that is down to Apple and furthermore, just A5+ would still not eliminate iPhone 4 (GSM, GSM Rev A or CDMA). --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 17:07, November 22, 2013‎ (UTC)}}<br /> :Do it like #4, and do them all. --[[User:CompilingEntropy|CompilingEntropy]] ([[User talk:CompilingEntropy|talk]]) 18:40, 23 November 2013 (UTC)<br /> ::::It will be a pain, but I like [[User:CompilingEntropy|CompilingEntropy]]'s idea as it would make it much much better in the end. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 16:25, 25 November 2013 (UTC)<br /> :I would say A and B are impossible due to various numbers in the same model. I like C best. For variant C you could also leave away the &quot;ap&quot; at the end, because every model has that, so it would be even shorter. For D, that's simply longer names and these names are not used at many places, but I could live with that version as well. --[[User:Http|http]] ([[User talk:Http|talk]]) 23:30, 1 December 2013 (UTC)<br /> Taking into account everyone's thoughts on this, I think we'll probably go with option C. The wiki already uses the &quot;-ap&quot; identifiers for the model pages, and an identifier like &quot;iPad3,4&quot; may confuse someone into thinking it's a model of the [[iPad 3]]. (I would still like to use the A1XXX numbers since Apple does that, but nobody else seems to agree now…) I'll give this a few more days for any last words before acting on it. --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 04:03, 26 December 2013 (UTC)<br /> ::It '''will''' get changed before the year ends. I don't know why your opinion keeps changing, but I have already explained the reason for changing it. You even agreed that it needs to be changed. I'm still open to suggestions on what to change it to though. Keep in mind that the change will affect not only key pages, but also how the devices will be referred to throughout the wiki. --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 19:34, 26 December 2013 (UTC)<br /> :::I know it will. I said it is fine to change. I like bot #3 and #4. Only point I must make is that I feel we should change all devices with multiple variants, including iPad Air and iPhone 4. This way, it is consistent and also removes GSM etc altogether. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 19:48, 26 December 2013 (UTC)<br /> ::I agree with Adam, if you're going to change some of them then change all of them. This includes iPods. Whatever the outcome, be consistent. As for the outcome itself, I really think we should just use device identifiers (iPhone2,1). That's what we're actually differentiating by, so it only makes sense to refer to devices by them. I don't think there would be any confusion, especially considering we'll keep the name of the device next to it regardless. Barring that, the next best option is ***ap. The other options don't make any sense considering modern devices. --[[User:CompilingEntropy|CompilingEntropy]] ([[User talk:CompilingEntropy|talk]]) 10:54, 30 December 2013 (UTC)<br /> :::I like [[User:CompilingEntropy|CompilingEntropy]]'s idea, though I do not mind if we do every device or just ones with multiple variants, as long as that included pre A5 (iPhone 4) too. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 18:34, 30 December 2013 (UTC)<br /> <br /> == &quot;GSM&quot; Replacement Proposals (cont.) ==<br /> So this entire discussion came up because we need to remove &quot;GSM&quot; from models, because there are many models nowadays where the non-GSM model or Global or whatever model, all support GSM. One suggestion was the FCC number, but I think we already agreed that this is out of discussion (only used within USA and nobody refers to this number). So we have to use either<br /> *The Axxxx number (like A1332 for the iPhone 4). This is how Apple identifies their devices.<br /> *The ap number (like n94ap or just short N94). This is the internal name and used in internal references, like in the [[iBEC]] or [[iBSS]] filenames within an [[IPSW]]. (This is also what iH8sn0w has on his stickers on the devices.)<br /> *The 1,2 number (like iPad1,1 for the iPad 1G). This identifier is used in the [[IPSW]] filenames.<br /> There are several issues with using one over the other:<br /> *Some devices (iPad 1G, iPhone 3G, iPhone 3GS, iPhone 4S, iPhone 5, iPhone 5c, iPhone 5s to be exact) have multiple Axxxx numbers for the same ap number/1,2 number. For example the iPad 1G: A1219 (WiFi model) and A1337 (GSM model) both have k48ap / iPad1,1. So only the Axxxx number could be used to replace the &quot;GSM&quot; identifier.<br /> *The iPhone 4 has for A1332 two ap numbers/1,2 numbers: A1332 stands for both n90ap/iPhone3,1 and also for n90bap/iPhone3,2.<br /> *The iPod touch 5G has the same 1,2 number for two ap numbers/Axxxx numbers: iPod5,1 stands for both A1421/n78ap and also for A1509/n78aap.<br /> I understand the point from [[User:IAdam1n|iAdam1n]] somehow that we should make it consistent and change it everywhere in the same manner. The question is where to change what. So where do we use these terms?<br /> *The biggest affected change would be the key pages, so any change there should be carefully considered. Currently we use something like: &quot;InnsbruckTaos 11B554a (iPhone 5c Global)&quot;. So the discussion here is just about the change in the brackets. For the devices where no different hardware versions exist, I think the current naming is ok. So let's just continue using that. Only where different (sub-)devices exist for the same main model (like for the iPhone 5c) and they require a different firmware file, then we need to specify it. So we need to add something after the &quot;iPhone 5c&quot; to specify the difference. For older devices, we should leave it as it is, because it works very well there. For example the iPad 1G WiFi and GSM require different firmware, but can be differentiated that way. And we can't use the ap number, because both versions use k48ap, respectively iPad1,1. So I think we should leave the old devices as they are. For newer devices, like the iPhone 5c, there are only two variations for the firmware, but six different Axxxx numbers and we don't want to list all of them in the firmware name. We also cannot use &quot;GSM&quot; for the reason mentioned at the introduction. I would prefer to use the ap number there, but that yields to problems. In case of the iPod touch 5G, we have two models (A1421/n78ap and also A1509/n78aap). Fortunately both use the same firmware, so we don't have to specify anything. But if Apple would release an additional model that would require a different firmware, we would have to specify the name even here and we can't add a name like &quot;n78ap+n78aap&quot;. The name iPod5,1 there seems to be the obvious choice, as it is contained in the ipsw name already, so it is unlikely that Apple will change that. The only question is the format then. My choice would be to keep it short, something like &quot;InnsbruckTaos 11B554a (iPhone 5c [5,4])&quot; instead of the current &quot;InnsbruckTaos 11B554a (iPhone 5c Global)&quot;. We shouldn't repeat the word &quot;iPhone&quot; there. And we shouldn't remove the &quot;5c&quot; of the original name.<br /> *We also have some hardware lists, for example on the key pages titles where we list under iPad 2: Wi-Fi, GSM, CDMA, Wi-Fi (A). They link directly to our ap-pages, for example the &quot;Wi-Fi (A)&quot; name links to &quot;k93aap&quot;. I think we don't need to change this. For the iPhone 5c, we have GSM and Global and they also link to the ap-pages. The link remains there, so we would only change the name. I suggest to use the same short name as in the key page extension, so something like my suggested &quot;[5,4]&quot; for example (instead of &quot;GSM&quot;).<br /> *On the [[Models]] page, we have the column &quot;Variant&quot;, which also lists &quot;GSM&quot; and &quot;Global&quot; etc. That would also need to change. I suggest to leave it for older devices where &quot;GSM&quot; is a valid differentiation. For newer devices we might list the bands it supports or something else.<br /> *On hardware pages, like [[iPhone]], we also have names and links in the title bar. For devices that have different sub-devices (like the iPhone 4 and iPhone 5/5c/5s) I suggest to rename the title names to the ap-names, as they link to the respective page. I would not change the title &quot;iPhone 3G&quot; to &quot;N82ap&quot; although it links there. So this change would only apply to sub-titles.<br /> --[[User:Http|http]] ([[User talk:Http|talk]]) 00:26, 31 December 2013 (UTC)<br /> :Include iPhone 4 in the change and use same format everywhere on the wiki. I agree that we do not need to change devices with only one variant such as iPhone 3GS. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 00:59, 31 December 2013 (UTC)<br /> :: I agree on that. 3GS, 3G and the 1st iPhone are anyway devices where I do not see too many wiki-related changes in the future.--[[User:M2m|M2m]] ([[User talk:M2m|talk]]) 09:57, 31 December 2013 (UTC)<br /> :I don't like how the abbreviated form of &quot;iPad3,4&quot; looks— I understand wanting to keep &quot;iPad 4&quot; in the name, but I can't come up with alternatives besides going with only the identifier. (Another issue is that MediaWiki's markup parser doesn't seem to like square brackets in links— I tried using &lt;code&gt;&lt;nowiki&gt;&lt;nowiki /&gt;&lt;/nowiki&gt;&lt;/code&gt;.) Having thought it over for a few days, I'm more receptive to changing all multi-variant devices (i.e. including the iPhone 4), but my concern about the Recent changes getting flooded with page moves still exists. The page moves should be done on &quot;quiet&quot; days, when the wiki doesn't see much activity. That being said, this is my understanding of the proposed changes. Does everyone agree with the following?<br /> :* On pages like [[iPhone]], the variant labels will be replaced with the identifier, e.g. iPhone3,1/iPhone3,2/iPhone3,3. (An exception will probably need to be made for the iPad1,1. The &quot;Internal Name&quot; row should also be modified because there will be duplicated information.)<br /> :* On [[Models]], the variant labels will be replaced with something else for the iPhone 5 and newer. (I feel like there are too many LTE bands to list in such a spot, but I don't have any better ideas.)<br /> :* On pages such as [[Firmware]] and [[Jailbreak]], labels will be changed to things like &quot;iPhone 4 (iPhone3,1)&quot; and &quot;iPad 4 (iPad3,4).&quot; Single-variant devices like the Apple TV 2G will remain as-is.<br /> :* The key pages will be moved to a different title, to resemble the following.<br /> :** &lt;del&gt;[[InnsbruckTaos 11B554a (AppleTV3,1)]]&lt;/del&gt; [[InnsbruckTaos 11B554a (Apple TV AppleTV3,1)]]<br /> :** &lt;del&gt;[[InnsbruckTaos 11B554a (iPad2,4)]]&lt;/del&gt; [[InnsbruckTaos 11B554a (iPad 2 iPad2,4)]]<br /> :** &lt;del&gt;[[InnsbruckTaos 11B554a (iPhone3,1)]]&lt;/del&gt; [[InnsbruckTaos 11B554a (iPhone 4 iPhone3,1)]]<br /> :** [[InnsbruckTaos 11B554a (iPod touch 5G)]]<br /> :Do let me know if I missed something. --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 23:57, 31 December 2013 (UTC)<br /> ::I agree with your idea [[User:Dialexio|Dialexio]], but make every page use iPhone 4 (iPhone3,1) etc. Of course if pages use iPhone 4 (GSM) now, change that to iPhone 4 (iPhone3,1) or iPhone 4 (3,1). I would suggest moving 10 pages per day for the iPhone 4 to avoid flooding. I do not want some pages to include the AP identifier and some others iPhone3,1 for example. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 00:08, 1 January 2014 (UTC)<br /> :::Several comments:<br /> *The square brackets were just an idea, nothing agreed on that yet. And yes, let's forget this idea if it has problems with MediaWiki.<br /> *The beginning of the name should remain, otherwise we're getting inconsistent with other pages. I agree with [[User:IAdam1n|iAdam1n]] on this. To keep it short, my favorite would be something like &quot;iPhone 4 (3,1)&quot; then. But to make it more clear, &quot;iPhone4 (iPhone3,1)&quot; is also ok to me. If you wanted to leave the first part away and just use &quot;iPhone3,1&quot;, then we would have to rename ALL pages (that's also an option).<br /> *Regarding flooding, I prefer that we do all changes at once, at an agreed date/time, done by [[User:Dialexio|Dialexio]]. Maybe in two steps: first step to change the few hardware pages plus one page of each device of the key pages. In the second step the rest. This would ensure that any misunderstandings get catched in the first step, before all pages are renamed. I don't like to have 20 edits per day that I have to go through. Better all at once, but only after agreement of all.<br /> *Yes, we can do iPhone 4 too, if that't the only missing one. It was a misunderstanding on my part for iPad GSM/WiFi, as this doesn't have different firmwares (only on hardware pages needed).<br /> *Regarding the proposed listing of the bands on the [[Models]] page, Variant column, we could only list the bands that are different to make it short.<br /> <br /> Can we list here what pages would be affected by the changes? Feel free to edit this list here within my comment. Here's what I have in mind:<br /> *[[Models]]<br /> *[[Apple TV]], [[iPad]], [[iPad mini]], [[iPhone]], [[iPod touch]]<br /> *[[Firmware Keys]]<br /> *[[Firmware]], [[Beta Firmware]]<br /> *[[Jailbreak]]<br /> *[[Application Processor]]<br /> *[[Main Page]] - for Application Processors and Baseband Devices.<br /> *[[:Category:Baseband]] - some pages state models and also the baseband devices, such as [[MDM6600]].<br /> *[[Template:Keys]]<br /> *[[P0sixspwn]]<br /> *[[:Timeline]]<br /> *[[SHSH]]<br /> *key pages: iPhone 4 GSM (like [[Telluride 9A334 (iPhone 4 GSM)]]), total 69 existing pages<br /> *key pages: iPhone 4 GSM (A) (like [[InnsbruckVailPrime 11A4372q (iPhone 4 GSM Rev A)]]), total 21 existing pages<br /> *key pages: iPhone 4 CDMA (like [[BrightonMaps 10B329 (iPhone 4 CDMA)]]), total 50 existing pages<br /> *key pages: iPhone 5 GSM (nonexistent)<br /> *key pages: iPhone 5 Global (nonexistent)<br /> *key pages: iPhone 5c and 5s (nonexistent)<br /> *key pages: iPad 2 Wi-Fi (like [[Durango 8G4 (iPad 2 Wi-Fi)]]), total 5 existing pages<br /> *key pages: iPad 2 GSM (like [[Durango 8G4 (iPad 2 GSM)]]), total 5 existing pages<br /> *key pages: iPad 2 CDMA (like [[Durango 8G4 (iPad 2 CDMA)]]), total 5 existing pages<br /> *key pages: iPad 2 Wi-Fi Rev A (nonexistent)<br /> *key pages: iPad 3 Wi-Fi (nonexistent)<br /> *key pages: iPad 3 CDMA (nonexistent)<br /> *key pages: iPad 3 Global (nonexistent)<br /> *key pages: iPad 4 Wi-Fi (nonexistent)<br /> *key pages: iPad 4 GSM (nonexistent)<br /> *key pages: iPad 4 Global (nonexistent)<br /> *key pages: iPad Air Wi-Fi (nonexistent)<br /> *key pages: iPad Air Cellular (nonexistent)<br /> *key pages: iPad mini Wi-Fi (nonexistent)<br /> *key pages: iPad mini GSM (nonexistent)<br /> *key pages: iPad mini Global (nonexistent)<br /> *key pages: iPad mini 2G Wi-Fi (nonexistent)<br /> *key pages: iPad mini 2G Cellular (nonexistent)<br /> The key pages would get moved without redirect and all references updated. The references should also be in this list above. Add it to the list if I forgot anything.<br /> --[[User:Http|http]] ([[User talk:Http|talk]]) 15:07, 1 January 2014 (UTC)<br /> ::::Yes that is fine. I said the 10 a day to avoid a big flood, but I do not mind either way. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 15:13, January 1, 2014‎ (UTC)<br /> ::::Looks good. I amended the list to include the iPads as well. --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 17:51, 1 January 2014 (UTC)<br /> :::::So most of you seem to agree on the the generic change now. But what is missing is the exact naming. We have three variations still in discussion:<br /> :::::#&quot;iPhone 4 (3,1)&quot;<br /> :::::#&quot;iPhone 4 (iPhone3,1)&quot;<br /> :::::#&quot;iPhone 4 3,1&quot;<br /> :::::#&quot;iPhone 4 iPhone3,1&quot;<br /> :::::I just noticed that we cannot use the round brackets, because this entire part is already enclosed in round brackets - otherwise we would have nested brackets and in grammar I think you have to use square brackets which are not allowed in MediaWiki. So this leaves us with #3 and #4. #3 looks silly without the brackets, so we probably have to use #4 as [[User:Dialexio|Dialexio]] suggested. --[[User:Http|http]] ([[User talk:Http|talk]]) 23:55, 1 January 2014 (UTC)<br /> ::::::I agree with #4, looks better as I feel that #3 needs some sort of brackets if we used that. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]])<br /> ::::::Wow, time really flies when you sleep all day. I've missed a ''lot''. Ok. I'm happy we decided to use the firmware moniker instead of something else. Personally, I don't like #1 because it just looks weird IMO. In addition, #1 and #2 would require the use of brackets (&lt;code&gt;(iPhone 4 [3,1])&lt;/code&gt;) which would require the use of &lt;code&gt;&amp;lt;nowiki/&amp;gt;&lt;/code&gt; all over the place, and that will get not only ugly, but annoying. I agree #3 looks weird. However, #4 just looks redundent. I personally would like just &lt;code&gt;iPhone3,1&lt;/code&gt;, but if I would have to put my vote on one of those last two, it would be #4. --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 08:20, 2 January 2014 (UTC)<br /> :::::::One last comment: We could also just use &quot;iPhone3,1&quot; (leaving the leading &quot;iPhone 4&quot; completely away). That would have two advantages and two disadvantages:<br /> :::::::*+ shorter<br /> :::::::*+ future-proof; if we ever decide to rename the rest as well, this is the way to name it<br /> :::::::*- somehow inconsistent with non-ambiguous other key pages (although ambiguous and non-ambiguous pages are different now anyway)<br /> :::::::*- less easy to understand from the name what device it is (but the iOS version is also not directly visible)<br /> :::::::--[[User:Http|http]] ([[User talk:Http|talk]]) 11:10, 2 January 2014 (UTC)<br /> ::::::::To me, that makes it worse. Why can we not use the rounded &quot;()&quot; brackets? I mean, it will only be duplicated in the key page urls, in which if it must be, just do &quot;iPhone 4 iPhone3,1&quot;. Does not seem too bad to me. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 11:18, 2 January 2014 (UTC)<br /> ::::::::::We ''don't want to'' use parenthesis because then we get double parenthesis (&lt;code&gt;Telluride 9A334 (iPhone 4 (3,1))&lt;/code&gt;). We would have to use braces (&lt;code&gt;Telluride 9A334 (iPhone 4 [3,1])&lt;/code&gt;), but MediaWiki chokes when there's braces in a link unless you use &lt;code&gt;&amp;lt;nowiki/&amp;gt;&lt;/code&gt;; and that would mean ''everywhere'' there's a firmware link. --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 13:19, 2 January 2014 (UTC)<br /> ::::::::That ''is'' what I suggested in my reply... As for your first disadvantage, it only applies to the iPads where Apple has gotten confusing. Actually, now that I think of that, option #4 above does look nice. However, I still don't like the redundency of having &lt;code&gt;iPhone&lt;/code&gt; in there twice. And as I said before, options #1 and #3 just look weird. So we're stuck at either redundency or looking weird. But then again, it wouldn't be redundent for the non-existent iPad key page links where Apple decided to be annoying with their firmware monikers. --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 13:19, 2 January 2014 (UTC)<br /> :::::::::Could we not just use the parenthesis but just not in the key page URL's? I mean, &quot;iPhone 4 (iPhone3,1)&quot; but in the urls for key pages, &lt;code&gt;Telluride 9A334 (iPhone_4_iPhone3,1)&lt;/code&gt;? That seems fine here. The underscores are currently there anyway. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 13:32, 2 January 2014 (UTC)<br /> ::::::::::This seems fine to me… Well, aside from the underscores. Other than that, we're actually already doing the same thing until the changes are implemented. (Key pages say &quot;(iPhone 4 GSM)&quot; while other parts of the wiki say &quot;iPhone 4 (GSM model).&quot;) --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 18:05, 2 January 2014 (UTC)<br /> ::::::::I think that &quot;iPhone 4 (iPhone3,1)&quot; does look the nicest, and I don't really feel like it's redundant. I also like the idea of just saying 'iPhone3,1'. If either of those options doesn't work, it might be good to do something like &quot;iPhone 4; iPhone3,1&quot; or &quot;iPhone 4 | iPhone3,1&quot;.--[[User:CompilingEntropy|CompilingEntropy]] ([[User talk:CompilingEntropy|talk]]) 16:46, 2 January 2014 (UTC)<br /> :::::::::The underscores were stated due to the key page URL's use that. I did not mean use that throughout. Was just to give an example, [[User:Dialexio|Dialexio]]. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 13:16, January 2, 2014‎ (UTC)<br /> ::::::::::So we have to decide between<br /> ::::::::::#&quot;Telluride 9A334 (iPhone 4 iPhone3,1)&quot; (name on link could be &quot;Telluride 9A334 (iPhone 4 [iPhone3,1])&quot; or whatever fits best in the context)<br /> ::::::::::#&quot;Telluride 9A334 (iPhone3,1)&quot;<br /> ::::::::::I would prefer #2 (for advantages/disadvantages see list above), but could also live with the other one. Votes? --[[User:Http|http]] ([[User talk:Http|talk]]) 22:06, 2 January 2014 (UTC)<br /> :::::::::::I would prefer #1 because it would be more consistent. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 22:14, 2 January 2014 (UTC)<br /> :::::::::::Count my vote for #2. I could go either way, but option #2 looks nicer. But just to double-check (yet again), we ''are'' using &quot;iPhone 4 (iPhone3,1)&quot; in places like [[Firmware]]'s headings, right? --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 18:19, 7 January 2014 (UTC)<br /> ::::::::::::Headings/titles/links: we didn't decide on that, but I think we can put whatever fits best in the context of a page. So that's a 'yes'. --[[User:Http|http]] ([[User talk:Http|talk]]) 23:53, 9 January 2014 (UTC)<br /> :::::::::::::This has been completed. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 10:12, 15 March 2014 (UTC)<br /> <br /> == Key page template ==<br /> I actually like the idea of a database to an extent. I bet I could put together an extension that creates a [[Special:SpecialPages|special page]] that allows read access to everyone (and r/w access to users). Any edits to the key &quot;pages&quot; wouldn't cause a [[Special:RecentChanges|recent changes]] log. If we ever needed to update the layout, we would just need to update the extension. We could even have an API.<br /> The only limitation is that updates to the extension would require either [[User:geohot|George]] or [[User:Dialexio|Alex]] needing to upload the fix. If we were to set up an external site, then all links to it would need to be wrapped with &lt;code&gt;&amp;lt;span class=&quot;plainlinks&quot;&amp;gt;...&amp;lt;/span&amp;gt;&lt;/code&gt;.<br /> Maybe a simple extension that takes links and redirects you to the external site? That could work. Like, we would have a link to, say, &lt;code&gt;[[&lt;nowiki/&gt;Special:Keys/iPad1,1/9A405]]&lt;/code&gt; which would give an HTTP &lt;code&gt;301 Moved Permanently&lt;/code&gt; header to, say, &lt;code&gt;&lt;nowiki&gt;http://ioskeys.com/iPad1,1/9A405&lt;/nowiki&gt;&lt;/code&gt;. Granted, someone would have to pay for the domain, but it would solve this problem. I may be able to pay for the domain if I make enough money by the time I finish writing everything. Any opposition? --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 16:48, 21 November 2013 (UTC)<br /> :I do not like the idea. I like the idea of the database to a degree, but I think that the pages should remain on this wiki. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 17:03, 21 November 2013 (UTC)<br /> ::I don't see this solving any problem— the backlash against changing the key page template was because of (unnecessary?) changes to the arguments, and the frequency of how often such changes were being proposed/applied. How would a database prevent it? For instance, let's say the database columns are all decided on. Suddenly, it's decided that SHA-1 hashes should be added as well, or perhaps &quot;VFDecryptKey&quot; will be renamed to &quot;FSKey.&quot; People submitting keys would still be bothered with having to adjust for those changes. --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 17:40, 21 November 2013 (UTC)<br /> :::That with the database is something I'll implement anyway (if not someone else is faster, as I'm quite busy). I just threw that in here as it might solve the problem of the frequent template updates (which is/was wrong anyway). From there it would be easy to create the VFDecrypt page with an overview link or lists of missing keys and that stuff, so the wiki would not need any direct links. But it would mean that we either completely remove all keys here from the wiki and embrace that solution or have them still duplicate (which then doesn't solve the problem). Dialexio: renaming columns can be handled without interface changes, but that's another topic. So let's forget about this database thing for now and we can discuss again when I have something. We certainly don't want to add extensions for that. So back to the discussion about the renaming: If I understood this correctly, you only want to rename A5+ devices and therefore no key pages would be affected. Is my understanding correct? --[[User:Http|http]] ([[User talk:Http|talk]]) 22:08, 21 November 2013 (UTC)<br /> ::::As long as the pages stay on this wiki, I do not mind. Although, a database could be pointless as with only 50 more pages to edit for the new format, there is no planned new format/changes again. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 22:16, 21 November 2013 (UTC)<br /> ::::About the renaming, that is correct; I'm only interested in changing the cellular labels on A5/+ devices. (Well, the iPad 2 can remain as-is.) --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 00:02, 22 November 2013 (UTC)<br /> :::::Oh, well that would just make things more complicated/inconsistent. We should do all or none. About the template idea, there is also no need as it is not likely we will change the format again. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 00:35, 22 November 2013 (UTC)<br /> ::::::Do we really need to CHANGE THE FORMAT 50 TIMES IN A ROW? The old one before everything was messed with worked fine enough. [[User:Winocm|Winocm]] ([[User talk:Winocm|talk]]) 18:22, 27 November 2013 (UTC)<br /> :::::::It was actually one change, which was completed. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 18:32, 27 November 2013 (UTC)<br /> <br /> ==Login prompt revision suggestion==<br /> I wrote a suggestion here: [[MediaWiki talk:Loginprompt]] (since I don't have permission to edit [[MediaWiki:Loginprompt]] directly) - I'd be interested in whether it sounds like a good idea to other people. [[User:Britta|Britta]] ([[User talk:Britta|talk]]) 01:00, 8 October 2013 (UTC)<br /> <br /> ==Homepage suggestions==<br /> Under &quot;Application Development&quot;, what about linking to [http://iphonedevwiki.net/index.php/Main_Page iPhoneDevWiki]? It's also a community-edited technical resource, and it links to this wiki. It could be helpful to add a little more detail to &quot;Get [[up to speed]] in the community.&quot;, like this: &quot;Get [[up to speed]] in the community - learn about how jailbreaks work.&quot; Under &quot;Definitions&quot;, it could be helpful to list all the firmware tags in one line or sub-list, similar to how Jailbreak is organized next to Tethered jailbreak and Untethered jailbreak, both to save space and help readers understand the list. --[[User:Britta|Britta]] ([[User talk:Britta|talk]]) 23:01, 20 October 2013 (UTC)<br /> :A link to the iPhoneDevWiki sounds good. I wonder if we should have an &quot;External Links&quot; or &quot;Other Resources&quot; section to include links to other sites (such as the [http://blog.iphone-dev.org/ iPhone Dev Team blog]) though. As for the &quot;Up to Speed&quot; page, I feel like the entire page could be reworked a bit— and perhaps even receive a new, clearer name ([[Introduction]]? [[Preface]]? Or something else?)— the current name makes it sound like it's for people that last paid attention to jailbreaking when the App Store didn't exist. And yeah, moving the IMG3 tags to a sub-list sounds like a really good idea. (Admittedly, I actually don't care for its inclusion in the first place, but that's just a personal preference.) --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 00:10, 21 October 2013 (UTC)<br /> ::There's already [[Useful Links]] with some links to other core community resources (which could be updated and rearranged) - I was just thinking that it'd be especially useful to link to iPhoneDevWiki prominently since it's likely for TheiPhoneWiki visitors to also be interested in relatively-organized technical information about development. Changing the name of &quot;Up to Speed&quot; sounds fine to me too - that page didn't get much attention since 2008 until I sort of commandeered it to serve as an &quot;intro to jailbreaking&quot; page. :) It could be renamed &quot;getting started&quot;, as in &quot;how to get started on learning about research into iOS devices, especially security research (such as jailbreaks)&quot;. [[User:Britta|Britta]] ([[User talk:Britta|talk]]) 00:31, 21 October 2013 (UTC)<br /> Also I'd love to see a dedicated section for &quot;Good tasks for new editors&quot;, where we could maintain a list of relatively easy/straightforward suggested edits that wouldn't require vast technical knowledge, like updating that links page. Where would that go? Add it as a sub-section of [[The iPhone Wiki:Current events]] and link that section from the homepage or something? Or make a new page? [[User:Britta|Britta]] ([[User talk:Britta|talk]]) 00:40, 21 October 2013 (UTC)<br /> <br /> ==What is 0x5265c384 in the boot process?==<br /> Does anybody know where &lt;code&gt;0x5265c384&lt;/code&gt; points to in the boot process? I haven't been able to find anything on it. --[[User:Ph0enix|Ph0enix]] ([[User talk:Ph0enix|talk]]) 20:14, 23 October 2013 (UTC)<br /> <br /> ==License for contributions==<br /> This wiki has never had an official license for contributions. Now, IANAL, but IIRC, this means that you can't use ''anything'' posted here unless it qualifies as fair-use. What I propose is that we set a license and add a notice that states that any contributions after a set date are to be licensed under that license (that's kindof a mouthful). I think we should use the [http://creativecommons.org/licenses/by-sa/3.0/ CC-by-SA 3.0] as [[wikipedia:Wikipedia:Text of Creative Commons Attribution-ShareAlike 3.0 Unported License|Wikipedia uses it]], but that's just me. Any ideas? --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 19:53, 9 November 2013 (UTC)<br /> :Well, the edit info already says all this:<br /> Please note that all contributions to The iPhone Wiki may be edited, altered, or<br /> removed by other contributors. If you do not want your writing to be edited mercilessly,<br /> then do not submit it here.<br /> You are also promising us that you wrote this yourself, or copied it from a public<br /> domain or similar free resource (see The [[:The iPhone Wiki:Copyrights|iPhone Wiki:Copyrights]] for details). '''Do not'''<br /> '''submit copyrighted work without permission!'''<br /> For me, that's enough. I don't need a 50 page license. But if you want to formalize this more, go ahead. --[[User:Http|http]] ([[User talk:Http|talk]]) 20:35, 9 November 2013 (UTC)<br /> :Sounds good. It's good practice to have an official license, just in case any disputes happen someday, and to ensure that it's OK to copy text over to Wikipedia (for example). [[User:Britta|Britta]] ([[User talk:Britta|talk]]) 21:32, 9 November 2013 (UTC)<br /> <br /> ==Banner Replacement?==<br /> I kinda feel like the banner on the front page is getting a little stale, so I'm interested in seeing it replaced. I tossed a proposal [https://twitter.com/Draxelf/status/408295008794845184 on Twitter] a couple of days ago (which is admittedly plain, but Myriad Set…), but I haven't heard any opinions on replacing the banner. Are there any thoughts on this matter? --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 17:42, 6 December 2013 (UTC)<br /> :Or, [http://imgur.com/wJFqPl1 this]. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 18:22, 6 December 2013 (UTC)<br /> :Looks nice in Myriad! More professional. [[User:Britta|Britta]] ([[User talk:Britta|talk]]) 04:01, 7 December 2013 (UTC)<br /> <br /> ==Date Format==<br /> I see that [[User:IAdam1n|iAdam1n]] started to unify the date formats in this wiki. While I like this to be consistent, actually we should've talked about what format to use before changing it. I like the d_mon_yyyy format though. I also saw that he removed the &lt;code&gt;&amp;amp;nbsp;&lt;/code&gt; between the date parts on the [[iFaith]] page that I added once purposefully. The reason was that when making the browser window small (or on the iPhone) that the date wraps to two lines, which is almost always undesired. The question is if we should do that everywhere too? Additionally, as we now seem to have a &quot;standard&quot; here, we should document it, so that new users know what format to use. -- [[User:Http|http]] ([[User talk:Http|talk]]) 17:42, 30 December 2013 (UTC)<br /> :I just made it consistent. If you want the &lt;code&gt;&amp;amp;nbsp;&lt;/code&gt; back, feel free to add it. I removed it as it did nothing (previewing on OS X). We should use the format I used throughout the wiki and not Dec 23, 2013 etc. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 18:32, 30 December 2013 (UTC)<br /> ::&lt;code&gt;&amp;amp;nbsp;&lt;/code&gt; stands for &quot;'''n'''on-'''b'''reaking '''sp'''ace&quot;. It is essentially a space, but with a property that prevents word wrap from occurring between the two words it's between. Look at [[Firmware Keys]] on a small enough screen (1024 across should do it). Your browser should preserve the space between the date &quot;words&quot;. Now, go into the edit page and remove the &lt;code&gt;&amp;amp;nbsp;&lt;/code&gt; from everything in one table. Your browser will now word wrap the date &quot;words&quot;. --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 00:04, 5 January 2014 (UTC)<br /> :What I actually want to do is use &lt;code&gt;{{[[Template:Start date|start date]]}}&lt;/code&gt; instead of plain dates in areas where dates are used as a statistic; for example, [[Firmware]], [[Firmware Keys]], [[SHSH]], [[Timeline]], etc. Places where dates are used to record when something happened, for example on [[evasi0n7]], &quot;On 28 December 2013...&quot;, should use the date flat out in the source. --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 00:04, 5 January 2014 (UTC)<br /> <br /> == Template documentation ==<br /> Whenever using templates that are copied here from Wikipedia, I almost always forget the parameters of the template. I then have to open Wikipedia and search for the template. What I want to do it copy the template documentation from Wikipedia here. To work around the licensing issue, we can create our own template that you would include at the bottom of the copied documentation that says the documentation comes from Wikipedia (because Wikipedia uses [[wikipedia:Wikipedia:Text of Creative Commons Attribution-ShareAlike 3.0 Unported License|CC-BY-SA 3.0]] which says our copied text must be under CC-BY-SA 3.0 ''and'' attribute Wikipedia and her editors. I can write the text for license template. Any ideas? Any opposition? If not, I'll begin in a few days. --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 00:04, 5 January 2014 (UTC)<br /> :I don't see why not. That's what I've seen done on other wikis. — '''[[User:Spydar007|&lt;span style=&quot;color:#ff5a00;&quot;&gt;Spydar007&lt;/span&gt;]] [[User talk:Spydar007|&lt;span style=&quot;color:orange;&quot;&gt;(Talk)&lt;/span&gt;]]''' 16:56, 18 January 2014 (UTC)<br /> <br /> == Mainpage &quot;iPhone Hackers&quot; List ==<br /> <br /> I think the &quot;iPhone Hackers&quot; List of the mainpage needs to be updated. Here are some people that need adding:<br /> <br /> *[[Pimskeks]]<br /> *[[User:iH8sn0w|iH8sn0w]]<br /> *[[User:winocm|winocm]]<br /> *SquiffyPwn<br /> *[[i0n1c]]<br /> <br /> Are there any others you can think of? — '''[[User:Spydar007|&lt;span style=&quot;color:#ff5a00;&quot;&gt;Spydar007&lt;/span&gt;]] [[User talk:Spydar007|&lt;span style=&quot;color:orange;&quot;&gt;(Talk)&lt;/span&gt;]]''' 16:55, 18 January 2014 (UTC)<br /> :I agree with the list except I do not think that SquiffyPwn has done anything huge, except help with [[p0sixspwn]] and i0n1c shouldn't be added. Just my opinions. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 20:53, 5 February 2014 (UTC)<br /> :: [[User:ph0enix|Me]], [[User:5urd|5urd]] and [[User:phyrrus9|phyrrus9]] have definitely earned our keep refer to http://theprivatedevteam.blogspot.com/2012/04/ios-51-semi-untethered-jailbreak.html --[[User:Ph0enix|Ph0enix]] ([[User talk:Ph0enix|talk]]) 02:17, 8 February 2014 (UTC)<br /> :::I disagree, you are not that well know, like pimskeks etc. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 09:25, 8 February 2014 (UTC)<br /> ::::I agree with iAdam1n. You are not known enough. — '''[[User:Spydar007|&lt;span style=&quot;color:#ff5a00;&quot;&gt;Spydar007&lt;/span&gt;]] [[User talk:Spydar007|&lt;span style=&quot;color:orange;&quot;&gt;(Talk)&lt;/span&gt;]]''' 14:52, 8 February 2014 (UTC)<br /> :::::Are you kidding me?? we have worked with many &quot;well known&quot; hackers and are in constant communication with people like p0sixninja! this is a joke we dont have to be &quot;well known&quot; to be influential hackers who not to mention have been running support and hacking in the community for 4 almost 5 years! --[[User:Ph0enix|Ph0enix]] ([[User talk:Ph0enix|talk]]) 18:08, 15 February 2014 (UTC)<br /> ::::::Support does not count. I am sticking with my original decision. AFAIK, you released no jailbreaks or found any new exploits, not as well know as the main hackers. Feel free to share what you have found/made if you want and also you can see what others say. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 19:24, 15 February 2014 (UTC)<br /> :::::::are you kidding me!! http://theprivatedevteam.blogspot.com/2012/04/ios-51-semi-untethered-jailbreak.html that is the reason i have high quality followers like posixninja and nitotv just because you guys are too young in the community to know about our major help to the community doesnt mean we are it is a closed sourced exploit but very functional and based off of redsn0w that implements our exploit now if you wanna get your thumb out of your buts and pay attention it would be great --[[User:Ph0enix|Ph0enix]] ([[User talk:Ph0enix|talk]]) 22:17, 15 February 2014 (UTC)<br /> ::::::::Why is this being brought up again? The answer was no before, and it's going to remain no for the reasons http stated before. I should add that who follows who on Twitter doesn't really mean anything— I have nitoTV, chronic, iH8sn0w, and winocm as followers, but that doesn't mean [https://twitter.com/Dialexio/status/376801384752222208 this] was a legitimate jailbreak by any means. --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 23:05, 15 February 2014 (UTC)<br /> ::::::::: Jeez idk maybe because we RELEASED A WORKING TOOL AND KEEP BEING BLOWN OFF BY INFERIOR ASS HOLES WHO REFUSE TO ADMIT IT! when you create a tool then challenge it till then we should be put on the list for discovering and implementing a previously unknown userland exploit and building a tool to ease the process... --[[User:Ph0enix|Ph0enix]] ([[User talk:Ph0enix|talk]]) 23:22, 15 February 2014 (UTC)<br /> ::::::::::Your insults aren't helping your credibility. Just saying. --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 23:35, 15 February 2014 (UTC)<br /> ::::::::::: well if i wouldn't have to have been asking for so long then i wouldn't be so upset my credibility is there whether you choose to ignore it or not is up to you. our tool is a working tool and we discovered and implemented a exploit that should be grounds for our names to be on the list,and the followers point is that we may not be well known but the people who follow us are legit people. quality over quantity. --[[User:Ph0enix|Ph0enix]] ([[User talk:Ph0enix|talk]]) 23:49, 15 February 2014 (UTC)<br /> ::::::::::::And now, your arguing with the administration. The answer is no. End of. — '''[[User:Spydar007|&lt;span style=&quot;color:#ff5a00;&quot;&gt;Spydar007&lt;/span&gt;]] [[User talk:Spydar007|&lt;span style=&quot;color:orange;&quot;&gt;(Talk)&lt;/span&gt;]]''' 09:13, 16 February 2014 (UTC)<br /> :Coming back to this old discussion, the decision at that time was to not even include iH8sn0w there, so I don't see a reason to include much lesser known people. For the overview list, we already have the [[:Category:Hackers]]. The main page is just for the 5-10 currently most important people. Regarding names, there should be a wide consensus of the people listed. If you ask me today, I'd comment like this:<br /> :*i0n1c is not working on public jailbreaks, so don't include<br /> :*geohot has retired from the scene, he could get removed, but as founder of this wiki and best contributor to the scene of all time, better leave him there<br /> :*winocm new shooting star, could get added<br /> :*iH8sn0w could get added with all the tools created<br /> :*all others I would not add or only added to category mentioned above<br /> :Remember that the list should be really short, so adding anyone would most probably mean to remove someone less important. Also, number of followers on Twitter doesn't mean anything; all these people follow me too and I wouldn't claim to be that important. This shouldn't discourage anybody not on this main page to continue his/her work. If this is causing these feelings, I think we should remove the list there entirely. --[[User:Http|http]] ([[User talk:Http|talk]]) 14:28, 16 February 2014 (UTC)<br /> :: Thanks [[User:Http|http]] I feel like in that case their should be a new category made for the people who have worked very hard but by those standards do not fit in that category, something like security researchers for the people who are doing a lot of behind the scenes work and certainly deserve some recognition somewhere on here. Just a thought though. --[[User:Ph0enix|Ph0enix]] ([[User talk:Ph0enix|talk]]) 22:29, 18 February 2014 (UTC)<br /> == Category Security Researchers==<br /> Hi all! i've created the category Security Researchers in order to cut down on the pages categorized as hackers as it apparently needs to be more exclusive. i've been adding the less known or inactive hackers from the hacker page but have not removed them from the hackers page. I feel that it should be a vote on who gets removed from the hackers page so my first suggestion is [[User:Fallensn0w‎]] as he has been inactive for a very long time and didn't do a lot in the first place. --[[User:Ph0enix|Ph0enix]] ([[User talk:Ph0enix|talk]]) 15:57, 22 February 2014 (UTC)<br /> <br /> == Replacing old/broken download links ==<br /> <br /> I have noticed on pages like [[evasi0n]] and [[p0sixspwn]] that some of the dwonlaod links no longer work because the developers have taken the revision of the software down. Rather than leave them there, I suggest we replace the links with ones that can be accessed (such as with ones in my MEGA). For example, version 1.0 of [[evasi0n]] was taken down from MEGA and no longer exists. However, I have version 1.0 saved in my MEGA Drive so I could replace the broken links with ones to downloads in my MEGA Drive. What do you guys think of this? — '''[[User:Spydar007|&lt;span style=&quot;color:#ff5a00;&quot;&gt;Spydar007&lt;/span&gt;]] [[User talk:Spydar007|&lt;span style=&quot;color:orange;&quot;&gt;(Talk)&lt;/span&gt;]]''' 10:07, 30 March 2014 (UTC)<br /> :I do not like this idea as it breaks copyright. We normally just put a line through with &lt;code&gt;style=&quot;text-decoration: line-through;&quot;&lt;/code&gt;. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 10:18, 30 March 2014 (UTC)<br /> ::I know but I think that people should still be able to download the old versions. — '''[[User:Spydar007|&lt;span style=&quot;color:#ff5a00;&quot;&gt;Spydar007&lt;/span&gt;]] [[User talk:Spydar007|&lt;span style=&quot;color:orange;&quot;&gt;(Talk)&lt;/span&gt;]]''' 11:23, 30 March 2014 (UTC)<br /> :::I disagree. Except for [[evasi0n7]], latest versions work best and with evasi0n7, all links work. We do not want unofficial links because of copyright. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 17:35, 30 March 2014 (UTC)<br /> ::::This contradicts your actions a bit— I've never seen official MEGA links for newer releases of evasi0n7, yet you filled it in for some of them. But I digress… In all honesty, I wouldn't mind, as long as no copyrights are violated. There should be some sort of distinction that it's not an official link though. --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 23:28, 30 March 2014 (UTC)<br /> :::::The MEGA links that I have added myself have been from evasi0n.com with &quot;view source&quot; in a browser. The earlier releases, [[User:5urd|5urd]] added them so I don't know about those. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 07:23, 31 March 2014 (UTC)<br /> ::::::To be honest, it is only violating copyright if the jailbreak tools cost money. Since they are free, it is not violating copyright. — '''[[User:Spydar007|&lt;span style=&quot;color:#ff5a00;&quot;&gt;Spydar007&lt;/span&gt;]] [[User talk:Spydar007|&lt;span style=&quot;color:orange;&quot;&gt;(Talk)&lt;/span&gt;]]''' 15:11, 31 March 2014 (UTC)<br /> :::::::Copyright laws are '''always''' in place, regardless of how much something costs, unless the creator waives their copyrights. --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 05:25, 1 April 2014 (UTC)<br /> :::::So, should I go ahead a do it? I could put a warning triangle symbol before it so that it is shown to be an unofficial link. — '''[[User:Spydar007|&lt;span style=&quot;color:#ff5a00;&quot;&gt;Spydar007&lt;/span&gt;]] [[User talk:Spydar007|&lt;span style=&quot;color:orange;&quot;&gt;(Talk)&lt;/span&gt;]]''' 14:42, 31 March 2014 (UTC)<br /> ::::::I say no. On JailbreakQA, one moderator was told by MuscleNerd to remove a hosted version that included the edit for 7.0.6 before evasi0n7 1.0.7 was released. There is no need for older versions since the latest works, with the exception of evasi0n7 1.0.8 but 1.0.7 links are still valid. I strongly disagree to add this. Also it should have at least a week on discussion. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 15:59, 31 March 2014 (UTC)<br /> :::::::That sounds more like MuscleNerd not wanting tampered copies of evasi0n7 to float around. That being said, I don't know whether he or the rest of the evad3rs would be fine with rehosting untouched copies of their files though. --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 05:25, 1 April 2014 (UTC)<br /> <br /> == geeksn0w ==<br /> <br /> I think we should make a page for geeksn0w. It is a jailbreak tool used by a significant amount of users who have iPhone 4's. I don't see why there isn't a page already. What do you guys think? — '''[[User:Spydar007|&lt;span style=&quot;color:#ff5a00;&quot;&gt;Spydar007&lt;/span&gt;]] [[User talk:Spydar007|&lt;span style=&quot;color:orange;&quot;&gt;(Talk)&lt;/span&gt;]]''' 15:07, 10 April 2014 (UTC)<br /> :I personally like the idea. I would at least like to see it added to [[iPhone 4]] on [[Jailbreak|the jailbreak page]]. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 15:32, 10 April 2014 (UTC)<br /> ::Exactly, we should add it to the [[Jailbreak]] page and create a page on it. What do you think of creating a page for the developer/hacker, BlackGeekTutorial? He is just about to start working on [[iFaith]] for iOS 7.<br /> :::Personally, we don't need a page on him I don't think until he has made a lot. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 15:52, 10 April 2014 (UTC)<br /> ::::On the page, I am thinking of having download links to previous versions (in my MEGA drive) since BlackGeek doesn't give out other links. What do you think? — '''[[User:Spydar007|&lt;span style=&quot;color:#ff5a00;&quot;&gt;Spydar007&lt;/span&gt;]] [[User talk:Spydar007|&lt;span style=&quot;color:orange;&quot;&gt;(Talk)&lt;/span&gt;]]''' 16:10, 10 April 2014 (UTC)<br /> :::::I think we should only use official links but thats just me. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 22:56, 25 April 2014 (UTC)<br /> ::::::I know we should use official links, but BlackGeek doesn't keep the links active. Also, he doesn't use MEGA. He just hosts it in the portfolio for his website. But he uses Adfly links to host them too. Do we really want Adfly links here? — '''[[User:Spydar007|&lt;span style=&quot;color:#ff5a00;&quot;&gt;Spydar007&lt;/span&gt;]] [[User talk:Spydar007|&lt;span style=&quot;color:orange;&quot;&gt;(Talk)&lt;/span&gt;]]''' 12:10, 26 April 2014 (UTC)<br /> :::::::If that is the official link, I would say yes. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 14:11, 26 April 2014 (UTC)<br /> <br /> == Cyberelevat0r ==<br /> I think we should make a page for Cyberelevat0r (i0n1c's 7.1.x Untethered Jailbreak). There is multiple proof that he might release it and we can fill it with information about all other hackers that have 7.1.x untethered jailbreaks as well. What do you think? — '''[[User:Spydar007|&lt;span style=&quot;color:black;&quot;&gt;Spydar007&lt;/span&gt;]] [[User talk:Spydar007|&lt;span style=&quot;color:gray;&quot;&gt;(Talk)&lt;/span&gt;]]''' 05:40, 22 May 2014 (UTC)<br /> :No. If (and it's a massive if) it gets released, then ok. Not until. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 08:01, 22 May 2014 (UTC)<br /> <br /> == Email notifications? ==<br /> 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)<br /> <br /> == Ambiguous names ==<br /> I feel like the names for [[Symlinks]] and [[Symbolic Link Vulnerability]] is a bit too ambiguous. Now, I don't anticipate there being much confusion, particularly since nobody really cares about 1.x anymore, but I would like to make the distinction clearer. I think both articles should be renamed, but I have no idea on what to rename them to (or even if you guys approve). I thought of using the CVE ID, but Apple doesn't provide one for [[Symlinks]] (or even any indication that they fixed it). ([[Symbolic Link Vulnerability]] was assigned CVE-2013-5133.) --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 17:51, 2 July 2014 (UTC)<br /> :They are referred to as the Symbolic Link by people like MuscleNerd and iH8sn0w so, in my opinion, they should be kept as their current names. — '''[[User:Spydar007|&lt;span style=&quot;color:black;&quot;&gt;Spydar007&lt;/span&gt;]] [[User talk:Spydar007|&lt;span style=&quot;color:gray;&quot;&gt;(Talk)&lt;/span&gt;]]''' 18:06, 2 July 2014 (UTC)<br /> ::I don't mind if one of them keeps their current name, but there should be something to make the distinction clearer. --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 01:13, 3 July 2014 (UTC)<br /> <br /> == IRC Channel on Freenode ==<br /> Howdy iphonewiki folks, I have #theiphonewiki registered on freenode, and am ready to have people come in (it's been ages since this idea has been brought up). Shall we open it? I'd like to get some ops in there to help out. --[[User:Haifisch|Haifisch]] ([[User talk:Haifisch|talk]]) 05:48, 6 July 2014 (UTC)<br /> &lt;br /&gt;<br /> I think we should make an IRC channel for this wiki. It can be either #theiphonewiki or #iphonewiki on freenode. The channel would be used for discussions, such as the TLC of the Jailbreak page for example. It would make getting things sorted a lot easier, since we could just ping each other different ideas. I know this idea was made before, but the channel never really got anywhere. What do you guys think of this idea? We would need to decide who has founder, op and voice etc. on the channel here. — '''[[User:Spydar007|&lt;span style=&quot;color:black;&quot;&gt;Spydar007&lt;/span&gt;]] [[User talk:Spydar007|&lt;span style=&quot;color:gray;&quot;&gt;(Talk)&lt;/span&gt;]]''' 06:58, 6 July 2014 (UTC)<br /> : This is idiotic. You just want to do it yourself cause you want power. We won't help you feed your ego. --[[User:Goeo|goeo_]] ([[User talk:Goeo|talk]]) 19:43, 6 July 2014 (UTC)<br /> :: You have never edited on this wiki in your life before so STFU. — '''[[User:Spydar007|&lt;span style=&quot;color:black;&quot;&gt;Spydar007&lt;/span&gt;]] [[User talk:Spydar007|&lt;span style=&quot;color:gray;&quot;&gt;(Talk)&lt;/span&gt;]]''' 05:48, 7 July 2014 (UTC)<br /> : Being that I own #theiphonewiki, the original channel in which the wiki's channel was going to be on, I have control over who's moderating the channel. One op will be me, I have 3+ years of IRC moderation experience (To be honest, Is this even CV worthy? :P) we can choose the other operators when the channel becomes somewhat popular. ps. Why make two topics for this? --[[User:Haifisch|Haifisch]] ([[User talk:Haifisch|talk]]) 08:03, 6 July 2014 (UTC)<br /> :: That most definitely is CV worthy. I've seen Spydar007 moderate a channel, it crashed in a week or so. Not to mention the channel wasn't even his, and he kinda took it over anyway. --[[User:Goeo|goeo_]] ([[User talk:Goeo|talk]]) 19:43, 6 July 2014 (UTC)<br /> ::No, no, no. The community decides. Juts because Farahtwiggy asked you to register it before, doesn't mean you get to be an op there now. This was my idea (Dialexio can vouch). You have no control over who are ops there. {{unsigned|Spydar007|04:11, July 6, 2014 (UTC)}}<br /> ::: One &quot;no&quot; is enough. Farah, really, doesn't have much (if anything) to do with this, the channel was registered a year ago. Your childish response above does not show me that you can handle owning the channel, nor do the rumors of you abusing channel control in your personal channel. It's really not your idea, it may have just now come to your mind, but adaminsull and I have gone through this whole deal before (one year ago). Join me on #theiphonewiki if you'd like to chat this out. --[[User:Haifisch|Haifisch]] ([[User talk:Haifisch|talk]]) 08:22, 6 July 2014 (UTC)<br /> ::::I don't know what's happening off of the wiki so I might only have part of the picture. I definitely don't see Haifisch as trying to steal credit for this idea, which actually was brought up about ages ago. I'm not much of an IRC guy, so my opinion might not have that much weight for a lot of this discussion, but I feel that the channel would be better in Haifisch's hands given his experience. Ownership/management/whatever for the IRC channel should certainly be open for discussion though. I really don't care too much about whoever gets to run it, as long as the person is someone that the community knows, respects, and trusts. (Same goes for the channel ops.) --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 17:42, 6 July 2014 (UTC)<br /> :It does not sound like a good idea to have an IRC channel for this wiki. It is useful for discussion of this wiki's articles to continue to be be done publicly on the wiki (on the appropriate talk pages), so that everyone interested in the wiki can easily contribute to the discussion, and so that there is a well-organized public record of discussions that we can all easily refer to. IRC channels are also very fertile breeding grounds for social conflicts and unhappiness (as we've seen already), which is helpful to skip. In any case, this should be discussed at [[The iPhone Wiki:Community portal]] instead of here - this page is for discussing modifications to the Main Page, and that one is for general discussions about TheiPhoneWiki. [[User:Britta|Britta]] ([[User talk:Britta|talk]]) 09:46, 7 July 2014 (UTC)<br /> <br /> == Moving to Canada ==<br /> I'm moving this server in the next few days to a quality server in Canada. It'll be running inside a VM, so I'll also look into giving admins more access. Hopefully the periodic outages will stop. Maybe I'll add some SSL certs. --[[User:Geohot|geohot]] ([[User talk:Geohot|talk]])<br /> :Nice, thanks! HTTPS would be great. --[[User:Britta|Britta]] ([[User talk:Britta|talk]]) 21:08, 14 August 2014 (UTC)<br /> ::So we're not in canada yet?--[[User:Awesomebing1|Awesomebing1]] ([[User talk:Awesomebing1|talk]]) 20:32, 30 August 2014 (UTC)<br /> You should all be in Canada now, with 8&amp;nbsp;GiB of Canadian RAM. We also have [https://theiphonewiki.com/wiki/Main_Page HTTPS], but it avoids the [[wikipedia:Squid (software)|Squid proxy]]. It's fine for people making edits but I don't plan on changing the default anytime soon. --[[User:Geohot|geohot]] ([[User talk:Geohot|talk]]) 04:43, 2 September 2014 (UTC)<br /> :Yay! Thanks as always George! Any plans on adding back SSH? There's a few things I'd love to have done. --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 21:40, 2 September 2014 (UTC)<br /> ::Thanks [[User:Geohot|geohot]]! Hopefully now there will be less downtime ;p --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 07:41, 3 September 2014 (UTC)<br /> :Sweeeeeeeet. :D --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 15:16, 3 September 2014 (UTC)</div>

Danzatt https://www.theiphonewiki.com/w/index.php?title=The_iPhone_Wiki:Community_portal&diff=42170 2014-09-15T09:57:54Z

<p>Danzatt: </p> <hr /> <div>{{Talk Archive}}<br /> {{see also|Unsolved problems}}<br /> ==iPhone serial cable==<br /> Could somebody document how to use uart cable (i.e. setup, bitrate, ...) ? Some intructions are available at [http://www.instructables.com/id/Apple-iOS-SerialUSB-Cable-for-Kernel-Debugging/ instructables]. Can two iPhones' serial inputs be connected to each other (i.e. TX of 1st iPhone to RX of 2nd and RX of first to TX of second) and minicom used on jailbroken device to connect to /dev/uart.iap such that no USB to 3.3V TTL (FT232RL in the link) would be needed provided that you already have multiple iDevices with dock connector<br /> ==iPhone-Elite==<br /> 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.<br /> --[[User:Http|http]] 15:02, 26 June 2012 (MDT)<br /> <br /> ==Boot-args cleanup==<br /> 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:<br /> *[[Kernel#Boot-Args]] A section with the latest boot arguments list. This should be a short introduction and having a link &quot;main article&quot;.<br /> *[[Boot-args (iBoot variable)]] separate page for boot arguments, but mainly for the iBoot variable that doesn't exist any longer<br /> *[{{FULLURL:Boot arguments|redirect=no}} Boot arguments] (redirect)<br /> *[[:Talk:Restore_Mode]] describing the iBoot variable problem<br /> *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)<br /> *My earlier comment [[:Talk:Kernel#boot-args]]<br /> *This comment here.<br /> 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 &quot;main article there&quot;. What do you think? --[[User:Http|http]] ([[User talk:Http|talk]]) 21:31, 13 February 2013 (UTC)<br /> :I like [[Boot Arguments]]. --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 02:01, 14 February 2013 (UTC)<br /> ::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)<br /> <br /> ==The iPhone Wiki re-design==<br /> The design of the iPhone wiki is now quite old and I think it should be updated. I made a [http://oi42.tinypic.com/30ib9y8.jpg concept]. --[[User:Jaggions|Jaggions]] ([[User talk:Jaggions|talk]]) 10:30, 14 June 2013 (UTC)<br /> :I disagree. If anything add an iPhone 5 to the logo but everything else is ok. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 11:05, 14 June 2013 (UTC)<br /> :I wouldn't change the logo to an iPhone 5, especially with iOS 7 and a new iPhone (that will probably look the same as the 5, admittedly) around the corner. I contemplated updating the CSS for iOS 7's UI but decided not to because of the UI's supposed volatility (during the beta period) and I don't have a live version to toy around with. (I personally don't like its current state, but that's not a factor in why I'm not changing it yet.) --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 16:25, 14 June 2013 (UTC)<br /> ::Can we not do flat? --[[User:Haifisch|Haifisch]] ([[User talk:Haifisch|talk]]) 21:02, 14 June 2013 (UTC)<br /> ::This is what I was thinking. When iOS 7 finally comes out, we could change the CSS to look like that instead. --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 21:11, 14 June 2013 (UTC)<br /> :::iOS 7 looks ugly. We do not want it like that. Maybe a bit more modern but nothing much. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 21:16, 14 June 2013 (UTC)<br /> ::::''You'' may not want it like that. That's your opinion. --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 01:55, 15 June 2013 (UTC)<br /> :::::We could make a poll, and see if most users agree or disagree. --[[User:Jaggions|Jaggions]] ([[User talk:Jaggions|talk]]) 10:05, 15 June 2013 (UTC)<br /> :The idea looks nice. But before we make any changes, let's wait until iOS7 comes out. And I'd prefer to just add another skin instead (if possible). I'm still using the classic MonoBook skin by the way. You shouldn't impose design changes to everyone. --[[User:Http|http]] ([[User talk:Http|talk]]) 14:38, 15 June 2013 (UTC)<br /> ::The problem with skins is that geohot needs to set them up... An idea I have is that we copy the Vector skin verbatim to a new skin (&lt;code&gt;iOS6&lt;/code&gt;) and move the modifications (not general stuff) to [[Mediawiki:iOS6.css]]. Then we can do another verbatim copy to &lt;code&gt;iOS7&lt;/code&gt; and modify [[Mediawiki:iOS7.css]]. We could then set the default skin to either &lt;code&gt;iOS6&lt;/code&gt; or &lt;code&gt;iOS7&lt;/code&gt; so you don't need to be logged in to see them like currently. Then if someone doesn't like them, like you, just change your settings to your preferred skin. The only way around needing geohot is if he opens up the credentials to FTP or whatever to someone. --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 21:17, 15 June 2013 (UTC)<br /> :::I like [[User:5urd|5urd]]'s suggestion. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 22:29, 15 June 2013 (UTC)<br /> What about just removing the text-shadow element for now? I think pages would be easier to read without it. Here's an example: [[:File:Noshadow.png]]. [[User:Britta|Britta]] ([[User talk:Britta|talk]]) 00:11, 29 August 2013 (UTC)<br /> :Yeah removing the shadow will make everything seem more flat but like [[User:http|http]] I'm still using the classic [http://theiphonewiki.com/w/index.php?title=Main_Page&amp;useskin=monobook MonoBook skin] --[[User:Jaggions|Jaggions]] ([[User talk:Jaggions|talk]]) 21:19, 31 August 2013 (UTC)<br /> <br /> ==Hacker page==<br /> I would like to be added to the list of hackers for my work with the Private Dev Team and the [[Chronic Dev (team)|Chronic Dev Team]] in addition to my release of the Phoenix Semi-Untethered. --[[User:Ph0enix|Ph0enix]] ([[User talk:Ph0enix|talk]]) 18:36, 22 July 2013 (UTC)<br /> :Did you find any exploits? --[[User:Haifisch|Haifisch]] ([[User talk:Haifisch|talk]]) 18:54, 22 July 2013 (UTC)<br /> ::No. [[User:phyrrus9|phyrrus9]], a team member found the vulnerability. I am the one who exploited it. --[[User:Ph0enix|Ph0enix]] ([[User talk:Ph0enix|talk]])<br /> :::I can back up this &quot;claim&quot;. I was a part of it. --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 20:52, 28 July 2013 (UTC)<br /> ::::Whatever happened to this? --[[User:Phyrrus9|phyrrus9]]<br /> :::::So this went cold and i am going to again request that this change be made. --[[User:Ph0enix|Ph0enix]] ([[User talk:Ph0enix|talk]]) 18:28, 13 January 2014 (UTC)<br /> ::::::I'm gonna say no. I don't see any notable accomplishments to merit this. --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 21:53, 13 January 2014 (UTC)<br /> ::::::'''No'''. The first step would be to get to the category [[:Category:Hackers|hackers]]. You can get there by finding a vulnerability that is used with an exploit in a jailbreak - or by writing a new exploit. Remember that it's not allowed to add yourself to that category. Instead of finding a vulnerability you could also be member of either The [[iPhone Dev Team]] or [[Chronic Dev]] or [[evad3rs]]. After being in that category, the next step would be that you're famous enough from all those hackers there to get to the main page. The people chosen are discussed here. --[[User:Http|http]] ([[User talk:Http|talk]]) 23:42, 13 January 2014 (UTC)<br /> <br /> ==Orphaned articles==<br /> This is an interesting search: [[Special:LonelyPages]] - &quot;The following pages are not linked from or transcluded into other pages in The iPhone Wiki.&quot; I'm not sure where all of those articles should be linked, but figuring that out could be a useful project for somebody. [[User:Britta|Britta]] ([[User talk:Britta|talk]]) 05:57, 28 August 2013 (UTC)<br /> <br /> ==Easy tasks for new editors==<br /> * 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 &quot;FF&quot; so it should be in the format &quot;0xe80000&quot; followed by two numbers) --[[User:Dirkg|Dirkg]] ([[User talk:Dirkg|talk]]) 22:40, 28 August 2013 (UTC)<br /> <br /> == A1XXX model numbers vs. &quot;GSM&quot;/&quot;CDMA&quot;/&quot;Global&quot;/&quot;Cellular&quot;/etc. ==<br /> I know that this topic was [[The iPhone Wiki:Community portal/2013#iPhone 5|already discussed earlier this year]], but it didn't seem to come to a consensus, and the introduction of the [[iPhone 5c]] and [[iPhone 5s]] brought a lot of model numbers. Some of them may &quot;overlap&quot; (think models A1429 and A1442 for the [[iPhone 5]]), but there's simply too many to give names to. There are at least two that can connect to CDMA networks, and all of them can connect to GSM. In addition, with the sheer amount of models, it doesn't seem likely for one model to be treated as a &quot;global&quot; model. Therefore, I changed the iPhone 5c to use model numbers. I would like to do the same to some of the devices that are already present on the wiki though— the same ones from when I first brought up this idea. The GSM/CDMA names work very well for the [[iPad 2]] and [[iPhone 4]]. Things are slightly murkier for the [[iPad 3|iPad (3rd gen.)]], [[iPad 4|iPad (4th gen.)]], [[iPad mini 1G]], and [[iPhone 5]] though; all of those devices' cellular models can connect to GSM networks, so it seems like nonsense to call some of them the &quot;GSM model.&quot; The A1XXX model numbers are also how Apple tells the difference between the different models of these devices. Have any opinions changed? Or perhaps someone new might have something to say about this? --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 06:06, 13 September 2013 (UTC)<br /> <br /> :I actually like the idea as it does get complicated now with the new devices coming like said and we would have to do this for all devices. Although, if we did this, we would have to move all the key pages that have keys on to support this. That would not be a big problem as we could limit the moves to say 20 per day. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 09:47, 13 September 2013 (UTC)<br /> <br /> :I suggest we wait a bit until we see what models of the [[iPhone 5c]] and [[iPhone 5s]] will exist. But in general, I like the idea of using only the A1nnn numbers. The only issue I see right now is that Apple differentiates between A1532 GSM and A1532 CDMA. If there are real hardware differences between these two, then we're screwed again. That's why I suggest to wait until we know these exact model types. On the disambiguation page I added the GSM/CDMA model differentiation already (as Apple does). If they turn out to be the same, we can remove it again, but I wonder why Apple lists two models (with different bands supported) there now. Someone also added the &quot;CDMA&quot; mark to one of the others, but that's not how Apple marks them, so I suggest to remove that mark there again. If everything can be differentiated by these A-model-numbers, then yes, we should change the old pages too. Including all key pages. --[[User:Http|http]] ([[User talk:Http|talk]]) 14:44, 13 September 2013 (UTC)<br /> <br /> ::I do know there are 2 CDMA and 3-4 GSM for the [[iPhone 5c]] alone. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 16:04, 13 September 2013 (UTC)<br /> <br /> :::Ahem… ''All'' of the iPhone 5c models can do GSM communications. Hence one of the reasons why I want to ditch the &quot;GSM&quot;/&quot;Global&quot;/etc. labels in favor of A1XXX model numbers. ;P --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 16:07, 13 September 2013 (UTC)<br /> <br /> ::::One thing is, what about iPod touch 5 as that has two model numbers that are the same device, same with iPhone5,2. How would we get around that? I suppose we could like both separated with a forward slash. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 18:19, 13 September 2013 (UTC)<br /> <br /> :::::Yeah, we could just use something like &quot;[[n42ap|iPhone 5 (Model A1429/A1442)]].&quot; --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 22:45, 13 September 2013 (UTC)<br /> <br /> ::::::Yeah I thought that but what about the iPhone 4 GSM and GSM Rev A? They both seem to be A1432. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 23:10, 13 September 2013 (UTC)<br /> <br /> :::::::This is why I'm against using the A1XXX model numbers instead of the current GSM/Global thing. --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 23:25, 13 September 2013 (UTC)<br /> <br /> ::::::::I had no plans to change the way we refer to the iPhone 4 or iPad 2 (Apple does use GSM/CDMA, and for those devices it works fine). If a new iPhone 5S revision comes along, Apple will probably refer to it as a &quot;Rev A&quot; thing, and so will we. --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 02:50, 14 September 2013 (UTC)<br /> <br /> :Referencing Adam's reply above, if we had took that to the key pages, it'd be &lt;code&gt;[&lt;nowiki/&gt;[{BuildTrain} {Build} (A1432)]]&lt;/code&gt; which would mess ''everything'' up. What could we do? Use &lt;code&gt;[&lt;nowiki/&gt;[{BuildTrain} {Build} (A1432 Rev A)]]&lt;/code&gt;? No. That doesn't look good. The current way of referring to everything by their supported network type (GSM/CDMA/Global) helps in going to a different page.<br /> :Let's say I'm on [[BrightonMaps 10B329 (iPhone 4 GSM)]] and I want to go the CDMA device. What do I do? Go to the URL and replace &lt;code&gt;GSM&lt;/code&gt; with &lt;code&gt;CDMA&lt;/code&gt;. With the model numbers, I'd have to navigate to [[Firmware]], then find the link, or find out what the model number of the CDMA variant is and replace the model number in the URL with that.&lt;br /&gt;<br /> :Ok, who navigates by the URL and search bar? ''I do''. And I'm sure there's '''many''' people out there that prefer to navigate with the search bar if they know the page name. If we go by model number, the AJAX search results just list pages with a model number in parenthesis. '''How does that help'''? I'd either have to ''know'' the model number of the device I want, or visit ''each one'' until I find the page I need.<br /> :Sorry for the rant, but I am '''strongly''' against this. --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 23:25, 13 September 2013 (UTC)<br /> <br /> ::I do suppose we could just trash the buildtrain all together to shorten it down too. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 23:32, 13 September 2013 (UTC)<br /> <br /> :::Dropping the Build Train would only ''increase'' the workload. Besides, what's the harm with it? We've been using the same page title structure since forever, and it's worked. &quot;''If it ain't broke, don't fix it''&quot;. The current system works, so ''why'', other than the fact that Apple refers to them differently, should we change this? In addition, we don't refer to everything the way Apple does. The [[iPad mini 1G]] is referred to as the &quot;iPad mini&quot;. The [[iPad 3]] is refered to as &quot;The New iPad&quot;. The [[iPad 4]] is refered to as &quot;iPad with Retina Display&quot;&lt;sup class=&quot;plainlinks&quot;&gt;[http://www.apple.com/ipad/compare/]&lt;/sup&gt;. Are the key pages titled &lt;code&gt;BrightonMaps 10B329 (The New iPad, Wi-Fi+3G for AT&amp;T and Verizon)&lt;/code&gt;? No. --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 00:37, 14 September 2013 (UTC)<br /> <br /> ::::But the reason we want to not use the variants is because the new devices that are coming out are breaking he structure and also CDMA versions can use GSM in the 5c plus we have like 4 for GSM alone. I only meant drop buildtrain to shorten the urls down. For the iPhone 4 GSM Rev A we would have to list it as &lt;code&gt;iPhone 4 A1432 Rev&lt;/code&gt; unless another idea is thought of. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 00:55, 14 September 2013 (UTC)<br /> <br /> :::::No. Anything involving moving key pages to change their title I am ''completely'' against. As for the iPhone 5s and iPhone 5c, we ultimately have to wait. There may be different types, but if they all work with the same firmware, then what do we do then? Use &lt;code&gt;A1456/A1504&lt;/code&gt;? I don't want to do that. It can get confusing in the future if that list were to be huge. With ''5'' different models for the iPhone 5c ''alone'', it's just not practical. For the fact that all support GSM, but not all support CDMA, we just do what we've ''been'' doing: &quot;GSM&quot; and &quot;Global&quot;. --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 01:22, 14 September 2013 (UTC)<br /> <br /> ::::::There's nothing wrong with changing the titles of pages that don't even exist though. If *all* of the models use the same firmware, just go with &quot;iPhone 5s.&quot; If they happen to be partitioned into two different firmwares again, that will certainly complicate things, but it wouldn't be worse than nonsense like &quot;GSM,&quot; &quot;GSM [&lt;nowiki /&gt;Global],&quot; &quot;CDMA,&quot; &quot;CDMA [&lt;nowiki /&gt;Global],&quot; or &quot;GSM [&lt;nowiki /&gt;Global Plus TD-LTE].&quot; If it's just one oddball, we could just have &quot;iPhone 5s&quot; and &quot;iPhone 5s A1XXX&quot; (whatever the odd one is), and include a link on the former page to say &quot;keys for model A1XXX are on this page.&quot; --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 02:50, 14 September 2013 (UTC)<br /> <br /> ::::I probably didn't phrase that well… I wasn't thinking of how Apple markets the product, but rather more along the lines of how they refer to it in, say, the tech specs page or support documents— the pages that shows the messier side to their simple sugar coating. --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 02:50, 14 September 2013 (UTC)<br /> <br /> ::You keep misinterpreting/misrepresenting what I'm proposing. I never said anything about dropping, say, &quot;iPhone 5&quot; so firmware page titles would look like [[Sundance 10A405 (A1428)]]. I want to change the GSM/Global part to the A1XXX number, so it would probably show like [[Sundance 10A405 (iPhone 5 A1428)]]. (If a hardware revision were made, it would probably look like [[Sundance 10A405 (iPhone 5 A1428 Rev A)]].) From time to time, I edit URLs to browse the wiki too. But the GSM/Global identifiers don't work that well; again, '''all iPhone 5 models can connect to GSM'''. That's not really helpful. --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 02:50, 14 September 2013 (UTC)<br /> <br /> :::I suggest we drop the A and use Rev. As for the idea of changing to A1XXX, I see no issues and am for the idea. I admit it can cause chaos when we move the pages but we could limit the moving per day of course. Overall, I think it will be worth it. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 10:01, 14 September 2013 (UTC)<br /> <br /> ::::No. Don't drop the &lt;code&gt;A&lt;/code&gt; from &lt;code&gt;Rev A&lt;/code&gt;. Why would you even think to? You want to call them what Apple calls them, and the [[n90bap|revised iPhone 4 GSM]] is referred to with &lt;code&gt;Rev A&lt;/code&gt;. In addition, there have been &lt;code&gt;Rev ''B''&lt;/code&gt; things before, such as the [[S5L8947]] (A5 Rev B) used in the [[j33iap|revised Apple TV 3G]]. In addition, think of all the redirects we would need to keep for sites that link to key pages directly. I have even seen sites that still link with the URLs as &lt;code&gt;/wiki/index.php?title={Title}&lt;/code&gt; instead of the year old change to &lt;code&gt;/wiki/{Title}&lt;/code&gt;. The wiki handles that internally for us, but the redirects made in the moves would have to be kept. Currently, only the [[iPhone 5]] and [[iPad 4]] are the only devices referred to by their model numbers. --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 20:53, 14 September 2013 (UTC)<br /> <br /> :::That's why I don't want to change it. It's worked for us, and we have no idea how the new firmwares will be handled. I am betting that there will only be two firmware types - one for the GSM, and one for the Global (GSM+CDMA) model. The only reason they are split, IIRC, is because AT&amp;T uses different LTE bands than rest of the GSM world.<br /> :::Ultimately, the GSM/CDMA/Global monikors haven't caused any ''naming conflicts''. Ok, you don't want to use the ''marketing'' title. What about the way they are referred to on [[Apple Developer Center|ADC]], because that seems to be what you want. I may be misreading what you're saying again, but if we're going to do that, let's use their ''full'' title. Something &lt;code&gt;(iPad [4th generation Model A1458])&lt;/code&gt; (iPad 4 Wi-Fi) and &lt;code&gt;(iPad Wi-Fi + Cellular [model for Verizon])&lt;/code&gt; (iPad 3 Global). Does the first one tell you if the device is Wi-Fi or a Wi-Fi+3G model? Does the second one tell you ''at all'' that it is an [[iPad 3]], or that it supports GSM? No.<br /> :::Apple has a history of being inconsistent. For example, the iPad 3 Wi-Fi is referred to on ADC (and iTunes) as &quot;iPad Wi-Fi (3rd generation)&quot; while the iPad 3 GSM is referred to as &quot;iPad Wi-Fi + Cellular [model for AT&amp;T]&quot;. What happened to the &quot;3rd generation&quot;? --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 20:53, 14 September 2013 (UTC)<br /> <br /> ::::We could always list as &lt;code&gt;iPhone 4 (iPhone3,1)&lt;/code&gt; etc instead if that would be better. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 21:13, 14 September 2013 (UTC)<br /> <br /> ::::Why is there a need to explicitly keep &quot;Wi-Fi&quot; in a key page's title? All you need is a way to distinguish what model it is from its other variants— the A1XXX model number does just that. It's not like we referred to the AppleTV3,2 as &quot;Apple TV 3G (New Single-Core A5)&quot; or something. And obviously, we can use common sense to address the 3rd generation iPad issue you brought up… Now you're just nitpicking. --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 05:28, 15 September 2013 (UTC)<br /> :::::Actually, I think we should wait until we see the firmware for iPhone 5c/5s and then decide. TBH, as [[User:5urd|5urd]] said, it is ok as it is but of course if once the new firmware is out it is more confusing, then we can think again. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 14:12, 15 September 2013 (UTC)<br /> <br /> :::::Come to think of it, we can use a mix of both; we can keep the &quot;Global&quot; moniker, but drop the &quot;GSM&quot; moniker in favor of the A1XXX model number. (The &quot;GSM&quot; moniker is the one that's been bothering me.) I think this works well for the iPad 3 (which is actually split into &quot;CDMA&quot; and &quot;Global—&quot; it probably doesn't need to be done for this), iPad 4, iPad mini 1G, and iPhone 5, but this leaves the question of what to do for the iPhone 5C/5S. --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 04:04, 19 September 2013 (UTC)<br /> <br /> ::::::That would look worse! If we are going to do it, we have to do it for '''''all'''''. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 09:40, 19 September 2013 (UTC)<br /> <br /> :::::::What is the status on this now? --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 21:18, 9 November 2013 (UTC)<br /> <br /> :::::This discussion has stagnated, but I'm firing it up again— I want to fix this before the end of the year, so this can probably be seen as an ultimatum. Now that Apple has pushed a 7.1 beta to developers, we now know how Apple's splitting the new iPhones up— and it's by A1XXX model numbers still. :\ That's probably the path the wiki will go down, but I do have another idea. The other idea I have in mind is using the A1XXX model number for the cellular devices launched last year. But for this year's iPhones, the FCC ID is actually different between the two, so we could actually use that. Before this gets nitpicked on, the last letter can get changed to an &quot;X&quot; to signify that it's a wildcard of sorts. It's not a pretty solution so I do expect it to get shot down (hence why I'm going with the A1XXX model numbers unless everyone says otherwise), but I'm still throwing it out there in case everyone actually likes that. Everyone is welcome to suggest alternatives, but I '''will''' eliminate that GSM label before the year ends. --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 18:31, 18 November 2013 (UTC)<br /> <br /> ::::::That is worse, nobody knows the FCC ID off the top of their head. I would suggest &quot;iPhone 5 (iPhone5,1)&quot; if anything. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 18:37, 18 November 2013 (UTC)<br /> <br /> :::::::Using &quot;iPhone5,1&quot; or &quot;iPhone6,2&quot; is even ''less'' friendly… The FCC ID can be looked up in Settings or the back of a device. --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 19:06, 18 November 2013 (UTC)<br /> <br /> ::::::::Well that is not the point. I say either use the firmware name or leave it alone. See what others thing though. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 19:13, 18 November 2013 (UTC)<br /> <br /> :::::::::I currently plan on using the A1XXX model numbers— the FCC ID proposal was just thrown out there in the off chance that someone might like it. I'm not really a fan of it myself, but the FCC ID is probably the simplest way to figure out if it's an iPhone6,1 or iPhone6,2 since both have multiple A1XXX model numbers. --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 19:19, 18 November 2013 (UTC)<br /> <br /> ::::::I agree to get rid of the &quot;GSM&quot; name, as almost all iPhones support GSM. The Axxxx numbers would be nice, but as some phones have several numbers, like A1457/A1518/A1528/A1530 (what is actually different between them?) we can't use it. For the FCC-ID, we can't use that either, because for example the iPhone 5 with FCC-ID BCG-E2599A stands for the GSM/A1428 and also for the GSM+CDMA/A1429 version. So I suggest to either use the identifier (like iPhone2,1) or better the internal name (like n88ap). That would have the advantage to separate them further, because the iPhone 4 A1332 has two internal versions: iPhone3,1/n90ap and the iPhone3,2/n90bap. The bigger question is where you want to use this. That determines mainly the name. On all the key pages? Then it must be a name that is different between models that use different firmwares. And regarding key pages, maybe we should delete all the key pages from this wiki and move them into some database instead and provide a nice user interface and API around it and integrate that into the wiki somehow. That way we can change all pages with one simple edit. For the name, I prefer the internal name. --[[User:Http|http]] ([[User talk:Http|talk]]) 23:43, 18 November 2013 (UTC)<br /> <br /> :::::::We would have to edit key pages too. They should not be removed however. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 23:46, 18 November 2013 (UTC)<br /> <br /> :::::::Well, I wasn't trying to say that we had to decide on one way to differentiate ''everything''; &quot;GSM&quot; does work fine for, say, the iPhone 4. The proposal I brought up today was using the FCC ID only for this year's (2013's) iPhones— last year's cellular devices would get the A1XXX model numbers (i.e. two different solutions for two different years). But as of right now, I like how using A1XXX model numbers sounds for all of the affected devices, mostly because that's the path Apple's going in their developer portal. Something like &quot;iPhone 5s (Model A1457/A1518/A1528/A1530)&quot; is admittedly a mouthful for this year's iPhones though. At the moment, I'm inquiring about how to label it on [[Firmware]] and such pages, but I'm sure the outcome can be adapted for key page titles as well. As for differences between the models, it seems to be the supported LTE bands. --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 03:49, 19 November 2013 (UTC)<br /> <br /> :::::::::I still think that unless it is &quot;iPhone 5 (iPhone5,1)&quot; it will be complicated but on the other hand, I kind of like the idea that [[User:Http|http]] had, using the internal identifiers like this &quot;iPhone 5 (n42ap)&quot;. The only problem is that it would cause quite a bit of a flood moving the key pages, although this can be done like 15 per day each or something. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 09:20, 19 November 2013 (UTC)<br /> <br /> ::::::::::I'm pretty sure the only key page that exists for an A5 (or newer) device is [[Telluride 9A406 (iPhone 4S)]]. --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 17:40, 21 November 2013 (UTC)<br /> <br /> :::::::::::That was an example. I know there are no more A5 pages, only the one you said and two beta for iPhone 4S. I just meant that it would show the design. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 13:36, November 21, 2013 (UTC)<br /> <br /> == &quot;GSM&quot; Replacement Proposals ==<br /> Since this discussion has become extremely lengthy, here are the proposals (to my understanding) for changing the labels, each of which can be subject to changes (i.e. dropping the word &quot;Model&quot; from Proposal A). In an effort to conserve space (ironically, this still adds a significant amount of length), I only included a few models, which should give an idea of the proposal. Basically anything with an A5 or newer is involved. Feel free to edit this list if I missed or totally misinterpreted something. --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 03:25, 22 November 2013 (UTC)<br /> # Proposal A (A1XXX numbers)<br /> #* iPad 4 (Model A1458)<br /> #* iPad 4 (Model A1459)<br /> #* iPad 4 (Model A1460)<br /> #* iPhone 5 (Model A1428)<br /> #* iPhone 5 (Model A1429/A1442)<br /> #* iPhone 5c (Model A1456/A1532)<br /> #* iPhone 5c (Model A1507/A1516/A1526/A1529)<br /> #* [[InnsbruckTaos 11B554a (iPad 4 A1458)]]<br /> #* [[InnsbruckTaos 11B554a (iPhone 5 A1429/A1442)]]<br /> #* [[InnsbruckTaos 11B554a (iPhone 5c Model A1507/A1516/A1526/A1529)]]<br /> # Proposal B (A1XXX + FCC ID)<br /> #* iPad 4 (Model A1458)<br /> #* iPad 4 (Model A1459)<br /> #* iPad 4 (Model A1460)<br /> #* iPhone 5 (Model A1428)<br /> #* iPhone 5 (Model A1429/A1442)<br /> #* iPhone 5c (BCG‑E2644A)<br /> #* iPhone 5c (BCG‑E2694X)<br /> #* [[InnsbruckTaos 11B554a (iPad 4 A1458)]]<br /> #* [[InnsbruckTaos 11B554a (iPhone 5 A1429/A1442)]]<br /> #* [[InnsbruckTaos 11B554a (iPhone 5c BCG‑E2694X)]]<br /> # Proposal C (-AP Identifier)<br /> #* iPad 4 (p101ap)<br /> #* iPad 4 (p102ap)<br /> #* iPad 4 (p103ap)<br /> #* iPhone 5 (n41ap)<br /> #* iPhone 5 (n42ap)<br /> #* iPhone 5c (n48ap)<br /> #* iPhone 5c (n49ap)<br /> #* [[InnsbruckTaos 11B554a (iPad 4 p101ap)]]<br /> #* [[InnsbruckTaos 11B554a (iPhone 5c n42ap)]]<br /> #* [[InnsbruckTaos 11B554a (iPhone 5c n49ap)]]<br /> # Proposal D (iPhoneX,Y Identifier)<br /> #* iPad 4 (iPad3,4)<br /> #* iPad 4 (iPad3,5)<br /> #* iPad 4 (iPad3,6)<br /> #* iPhone 5 (iPhone5,1)<br /> #* iPhone 5 (iPhone5,2)<br /> #* iPhone 5c (iPhone5,3)<br /> #* iPhone 5c (iPhone5,4)<br /> #* [[InnsbruckTaos 11B554a (iPad3,4)]]<br /> #* [[InnsbruckTaos 11B554a (iPhone5,2)]]<br /> #* [[InnsbruckTaos 11B554a (iPhone5,4)]]<br /> <br /> <br /> :I like this [[InnsbruckTaos 11B554a iPad 4 (3,4)]] or [[InnsbruckTaos 11B554a iPad 4 (iPad3,4)]]. I see there are 4 ways to approach this;<br /> 1. Change every single device.&lt;br /&gt;<br /> 2. Change just devices with different variants, iPad 2+, iPad mini+, iPhone 4, iPhone 5+.&lt;br /&gt;<br /> 3. Change A5+ only (which I hate the idea of).&lt;br /&gt;<br /> 4. Change nothing at all.&lt;br /&gt;<br /> --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 09:28, 22 November 2013 (UTC)<br /> ::My intention for this was to be a ''neutral'' (i.e. opinion-free) spot where all of the proposals were being mentioned, so people could easily see the proposed changes without any bias… v.v --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 20:54, 22 November 2013 (UTC)<br /> :::TBH, I think it is better as it is, but I just stated my opinion that only A5+ would make in inconsistent. Though you could argue it is already, that is down to Apple and furthermore, just A5+ would still not eliminate iPhone 4 (GSM, GSM Rev A or CDMA). --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 17:07, November 22, 2013‎ (UTC)}}<br /> :Do it like #4, and do them all. --[[User:CompilingEntropy|CompilingEntropy]] ([[User talk:CompilingEntropy|talk]]) 18:40, 23 November 2013 (UTC)<br /> ::::It will be a pain, but I like [[User:CompilingEntropy|CompilingEntropy]]'s idea as it would make it much much better in the end. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 16:25, 25 November 2013 (UTC)<br /> :I would say A and B are impossible due to various numbers in the same model. I like C best. For variant C you could also leave away the &quot;ap&quot; at the end, because every model has that, so it would be even shorter. For D, that's simply longer names and these names are not used at many places, but I could live with that version as well. --[[User:Http|http]] ([[User talk:Http|talk]]) 23:30, 1 December 2013 (UTC)<br /> Taking into account everyone's thoughts on this, I think we'll probably go with option C. The wiki already uses the &quot;-ap&quot; identifiers for the model pages, and an identifier like &quot;iPad3,4&quot; may confuse someone into thinking it's a model of the [[iPad 3]]. (I would still like to use the A1XXX numbers since Apple does that, but nobody else seems to agree now…) I'll give this a few more days for any last words before acting on it. --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 04:03, 26 December 2013 (UTC)<br /> ::It '''will''' get changed before the year ends. I don't know why your opinion keeps changing, but I have already explained the reason for changing it. You even agreed that it needs to be changed. I'm still open to suggestions on what to change it to though. Keep in mind that the change will affect not only key pages, but also how the devices will be referred to throughout the wiki. --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 19:34, 26 December 2013 (UTC)<br /> :::I know it will. I said it is fine to change. I like bot #3 and #4. Only point I must make is that I feel we should change all devices with multiple variants, including iPad Air and iPhone 4. This way, it is consistent and also removes GSM etc altogether. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 19:48, 26 December 2013 (UTC)<br /> ::I agree with Adam, if you're going to change some of them then change all of them. This includes iPods. Whatever the outcome, be consistent. As for the outcome itself, I really think we should just use device identifiers (iPhone2,1). That's what we're actually differentiating by, so it only makes sense to refer to devices by them. I don't think there would be any confusion, especially considering we'll keep the name of the device next to it regardless. Barring that, the next best option is ***ap. The other options don't make any sense considering modern devices. --[[User:CompilingEntropy|CompilingEntropy]] ([[User talk:CompilingEntropy|talk]]) 10:54, 30 December 2013 (UTC)<br /> :::I like [[User:CompilingEntropy|CompilingEntropy]]'s idea, though I do not mind if we do every device or just ones with multiple variants, as long as that included pre A5 (iPhone 4) too. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 18:34, 30 December 2013 (UTC)<br /> <br /> == &quot;GSM&quot; Replacement Proposals (cont.) ==<br /> So this entire discussion came up because we need to remove &quot;GSM&quot; from models, because there are many models nowadays where the non-GSM model or Global or whatever model, all support GSM. One suggestion was the FCC number, but I think we already agreed that this is out of discussion (only used within USA and nobody refers to this number). So we have to use either<br /> *The Axxxx number (like A1332 for the iPhone 4). This is how Apple identifies their devices.<br /> *The ap number (like n94ap or just short N94). This is the internal name and used in internal references, like in the [[iBEC]] or [[iBSS]] filenames within an [[IPSW]]. (This is also what iH8sn0w has on his stickers on the devices.)<br /> *The 1,2 number (like iPad1,1 for the iPad 1G). This identifier is used in the [[IPSW]] filenames.<br /> There are several issues with using one over the other:<br /> *Some devices (iPad 1G, iPhone 3G, iPhone 3GS, iPhone 4S, iPhone 5, iPhone 5c, iPhone 5s to be exact) have multiple Axxxx numbers for the same ap number/1,2 number. For example the iPad 1G: A1219 (WiFi model) and A1337 (GSM model) both have k48ap / iPad1,1. So only the Axxxx number could be used to replace the &quot;GSM&quot; identifier.<br /> *The iPhone 4 has for A1332 two ap numbers/1,2 numbers: A1332 stands for both n90ap/iPhone3,1 and also for n90bap/iPhone3,2.<br /> *The iPod touch 5G has the same 1,2 number for two ap numbers/Axxxx numbers: iPod5,1 stands for both A1421/n78ap and also for A1509/n78aap.<br /> I understand the point from [[User:IAdam1n|iAdam1n]] somehow that we should make it consistent and change it everywhere in the same manner. The question is where to change what. So where do we use these terms?<br /> *The biggest affected change would be the key pages, so any change there should be carefully considered. Currently we use something like: &quot;InnsbruckTaos 11B554a (iPhone 5c Global)&quot;. So the discussion here is just about the change in the brackets. For the devices where no different hardware versions exist, I think the current naming is ok. So let's just continue using that. Only where different (sub-)devices exist for the same main model (like for the iPhone 5c) and they require a different firmware file, then we need to specify it. So we need to add something after the &quot;iPhone 5c&quot; to specify the difference. For older devices, we should leave it as it is, because it works very well there. For example the iPad 1G WiFi and GSM require different firmware, but can be differentiated that way. And we can't use the ap number, because both versions use k48ap, respectively iPad1,1. So I think we should leave the old devices as they are. For newer devices, like the iPhone 5c, there are only two variations for the firmware, but six different Axxxx numbers and we don't want to list all of them in the firmware name. We also cannot use &quot;GSM&quot; for the reason mentioned at the introduction. I would prefer to use the ap number there, but that yields to problems. In case of the iPod touch 5G, we have two models (A1421/n78ap and also A1509/n78aap). Fortunately both use the same firmware, so we don't have to specify anything. But if Apple would release an additional model that would require a different firmware, we would have to specify the name even here and we can't add a name like &quot;n78ap+n78aap&quot;. The name iPod5,1 there seems to be the obvious choice, as it is contained in the ipsw name already, so it is unlikely that Apple will change that. The only question is the format then. My choice would be to keep it short, something like &quot;InnsbruckTaos 11B554a (iPhone 5c [5,4])&quot; instead of the current &quot;InnsbruckTaos 11B554a (iPhone 5c Global)&quot;. We shouldn't repeat the word &quot;iPhone&quot; there. And we shouldn't remove the &quot;5c&quot; of the original name.<br /> *We also have some hardware lists, for example on the key pages titles where we list under iPad 2: Wi-Fi, GSM, CDMA, Wi-Fi (A). They link directly to our ap-pages, for example the &quot;Wi-Fi (A)&quot; name links to &quot;k93aap&quot;. I think we don't need to change this. For the iPhone 5c, we have GSM and Global and they also link to the ap-pages. The link remains there, so we would only change the name. I suggest to use the same short name as in the key page extension, so something like my suggested &quot;[5,4]&quot; for example (instead of &quot;GSM&quot;).<br /> *On the [[Models]] page, we have the column &quot;Variant&quot;, which also lists &quot;GSM&quot; and &quot;Global&quot; etc. That would also need to change. I suggest to leave it for older devices where &quot;GSM&quot; is a valid differentiation. For newer devices we might list the bands it supports or something else.<br /> *On hardware pages, like [[iPhone]], we also have names and links in the title bar. For devices that have different sub-devices (like the iPhone 4 and iPhone 5/5c/5s) I suggest to rename the title names to the ap-names, as they link to the respective page. I would not change the title &quot;iPhone 3G&quot; to &quot;N82ap&quot; although it links there. So this change would only apply to sub-titles.<br /> --[[User:Http|http]] ([[User talk:Http|talk]]) 00:26, 31 December 2013 (UTC)<br /> :Include iPhone 4 in the change and use same format everywhere on the wiki. I agree that we do not need to change devices with only one variant such as iPhone 3GS. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 00:59, 31 December 2013 (UTC)<br /> :: I agree on that. 3GS, 3G and the 1st iPhone are anyway devices where I do not see too many wiki-related changes in the future.--[[User:M2m|M2m]] ([[User talk:M2m|talk]]) 09:57, 31 December 2013 (UTC)<br /> :I don't like how the abbreviated form of &quot;iPad3,4&quot; looks— I understand wanting to keep &quot;iPad 4&quot; in the name, but I can't come up with alternatives besides going with only the identifier. (Another issue is that MediaWiki's markup parser doesn't seem to like square brackets in links— I tried using &lt;code&gt;&lt;nowiki&gt;&lt;nowiki /&gt;&lt;/nowiki&gt;&lt;/code&gt;.) Having thought it over for a few days, I'm more receptive to changing all multi-variant devices (i.e. including the iPhone 4), but my concern about the Recent changes getting flooded with page moves still exists. The page moves should be done on &quot;quiet&quot; days, when the wiki doesn't see much activity. That being said, this is my understanding of the proposed changes. Does everyone agree with the following?<br /> :* On pages like [[iPhone]], the variant labels will be replaced with the identifier, e.g. iPhone3,1/iPhone3,2/iPhone3,3. (An exception will probably need to be made for the iPad1,1. The &quot;Internal Name&quot; row should also be modified because there will be duplicated information.)<br /> :* On [[Models]], the variant labels will be replaced with something else for the iPhone 5 and newer. (I feel like there are too many LTE bands to list in such a spot, but I don't have any better ideas.)<br /> :* On pages such as [[Firmware]] and [[Jailbreak]], labels will be changed to things like &quot;iPhone 4 (iPhone3,1)&quot; and &quot;iPad 4 (iPad3,4).&quot; Single-variant devices like the Apple TV 2G will remain as-is.<br /> :* The key pages will be moved to a different title, to resemble the following.<br /> :** &lt;del&gt;[[InnsbruckTaos 11B554a (AppleTV3,1)]]&lt;/del&gt; [[InnsbruckTaos 11B554a (Apple TV AppleTV3,1)]]<br /> :** &lt;del&gt;[[InnsbruckTaos 11B554a (iPad2,4)]]&lt;/del&gt; [[InnsbruckTaos 11B554a (iPad 2 iPad2,4)]]<br /> :** &lt;del&gt;[[InnsbruckTaos 11B554a (iPhone3,1)]]&lt;/del&gt; [[InnsbruckTaos 11B554a (iPhone 4 iPhone3,1)]]<br /> :** [[InnsbruckTaos 11B554a (iPod touch 5G)]]<br /> :Do let me know if I missed something. --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 23:57, 31 December 2013 (UTC)<br /> ::I agree with your idea [[User:Dialexio|Dialexio]], but make every page use iPhone 4 (iPhone3,1) etc. Of course if pages use iPhone 4 (GSM) now, change that to iPhone 4 (iPhone3,1) or iPhone 4 (3,1). I would suggest moving 10 pages per day for the iPhone 4 to avoid flooding. I do not want some pages to include the AP identifier and some others iPhone3,1 for example. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 00:08, 1 January 2014 (UTC)<br /> :::Several comments:<br /> *The square brackets were just an idea, nothing agreed on that yet. And yes, let's forget this idea if it has problems with MediaWiki.<br /> *The beginning of the name should remain, otherwise we're getting inconsistent with other pages. I agree with [[User:IAdam1n|iAdam1n]] on this. To keep it short, my favorite would be something like &quot;iPhone 4 (3,1)&quot; then. But to make it more clear, &quot;iPhone4 (iPhone3,1)&quot; is also ok to me. If you wanted to leave the first part away and just use &quot;iPhone3,1&quot;, then we would have to rename ALL pages (that's also an option).<br /> *Regarding flooding, I prefer that we do all changes at once, at an agreed date/time, done by [[User:Dialexio|Dialexio]]. Maybe in two steps: first step to change the few hardware pages plus one page of each device of the key pages. In the second step the rest. This would ensure that any misunderstandings get catched in the first step, before all pages are renamed. I don't like to have 20 edits per day that I have to go through. Better all at once, but only after agreement of all.<br /> *Yes, we can do iPhone 4 too, if that't the only missing one. It was a misunderstanding on my part for iPad GSM/WiFi, as this doesn't have different firmwares (only on hardware pages needed).<br /> *Regarding the proposed listing of the bands on the [[Models]] page, Variant column, we could only list the bands that are different to make it short.<br /> <br /> Can we list here what pages would be affected by the changes? Feel free to edit this list here within my comment. Here's what I have in mind:<br /> *[[Models]]<br /> *[[Apple TV]], [[iPad]], [[iPad mini]], [[iPhone]], [[iPod touch]]<br /> *[[Firmware Keys]]<br /> *[[Firmware]], [[Beta Firmware]]<br /> *[[Jailbreak]]<br /> *[[Application Processor]]<br /> *[[Main Page]] - for Application Processors and Baseband Devices.<br /> *[[:Category:Baseband]] - some pages state models and also the baseband devices, such as [[MDM6600]].<br /> *[[Template:Keys]]<br /> *[[P0sixspwn]]<br /> *[[:Timeline]]<br /> *[[SHSH]]<br /> *key pages: iPhone 4 GSM (like [[Telluride 9A334 (iPhone 4 GSM)]]), total 69 existing pages<br /> *key pages: iPhone 4 GSM (A) (like [[InnsbruckVailPrime 11A4372q (iPhone 4 GSM Rev A)]]), total 21 existing pages<br /> *key pages: iPhone 4 CDMA (like [[BrightonMaps 10B329 (iPhone 4 CDMA)]]), total 50 existing pages<br /> *key pages: iPhone 5 GSM (nonexistent)<br /> *key pages: iPhone 5 Global (nonexistent)<br /> *key pages: iPhone 5c and 5s (nonexistent)<br /> *key pages: iPad 2 Wi-Fi (like [[Durango 8G4 (iPad 2 Wi-Fi)]]), total 5 existing pages<br /> *key pages: iPad 2 GSM (like [[Durango 8G4 (iPad 2 GSM)]]), total 5 existing pages<br /> *key pages: iPad 2 CDMA (like [[Durango 8G4 (iPad 2 CDMA)]]), total 5 existing pages<br /> *key pages: iPad 2 Wi-Fi Rev A (nonexistent)<br /> *key pages: iPad 3 Wi-Fi (nonexistent)<br /> *key pages: iPad 3 CDMA (nonexistent)<br /> *key pages: iPad 3 Global (nonexistent)<br /> *key pages: iPad 4 Wi-Fi (nonexistent)<br /> *key pages: iPad 4 GSM (nonexistent)<br /> *key pages: iPad 4 Global (nonexistent)<br /> *key pages: iPad Air Wi-Fi (nonexistent)<br /> *key pages: iPad Air Cellular (nonexistent)<br /> *key pages: iPad mini Wi-Fi (nonexistent)<br /> *key pages: iPad mini GSM (nonexistent)<br /> *key pages: iPad mini Global (nonexistent)<br /> *key pages: iPad mini 2G Wi-Fi (nonexistent)<br /> *key pages: iPad mini 2G Cellular (nonexistent)<br /> The key pages would get moved without redirect and all references updated. The references should also be in this list above. Add it to the list if I forgot anything.<br /> --[[User:Http|http]] ([[User talk:Http|talk]]) 15:07, 1 January 2014 (UTC)<br /> ::::Yes that is fine. I said the 10 a day to avoid a big flood, but I do not mind either way. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 15:13, January 1, 2014‎ (UTC)<br /> ::::Looks good. I amended the list to include the iPads as well. --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 17:51, 1 January 2014 (UTC)<br /> :::::So most of you seem to agree on the the generic change now. But what is missing is the exact naming. We have three variations still in discussion:<br /> :::::#&quot;iPhone 4 (3,1)&quot;<br /> :::::#&quot;iPhone 4 (iPhone3,1)&quot;<br /> :::::#&quot;iPhone 4 3,1&quot;<br /> :::::#&quot;iPhone 4 iPhone3,1&quot;<br /> :::::I just noticed that we cannot use the round brackets, because this entire part is already enclosed in round brackets - otherwise we would have nested brackets and in grammar I think you have to use square brackets which are not allowed in MediaWiki. So this leaves us with #3 and #4. #3 looks silly without the brackets, so we probably have to use #4 as [[User:Dialexio|Dialexio]] suggested. --[[User:Http|http]] ([[User talk:Http|talk]]) 23:55, 1 January 2014 (UTC)<br /> ::::::I agree with #4, looks better as I feel that #3 needs some sort of brackets if we used that. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]])<br /> ::::::Wow, time really flies when you sleep all day. I've missed a ''lot''. Ok. I'm happy we decided to use the firmware moniker instead of something else. Personally, I don't like #1 because it just looks weird IMO. In addition, #1 and #2 would require the use of brackets (&lt;code&gt;(iPhone 4 [3,1])&lt;/code&gt;) which would require the use of &lt;code&gt;&amp;lt;nowiki/&amp;gt;&lt;/code&gt; all over the place, and that will get not only ugly, but annoying. I agree #3 looks weird. However, #4 just looks redundent. I personally would like just &lt;code&gt;iPhone3,1&lt;/code&gt;, but if I would have to put my vote on one of those last two, it would be #4. --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 08:20, 2 January 2014 (UTC)<br /> :::::::One last comment: We could also just use &quot;iPhone3,1&quot; (leaving the leading &quot;iPhone 4&quot; completely away). That would have two advantages and two disadvantages:<br /> :::::::*+ shorter<br /> :::::::*+ future-proof; if we ever decide to rename the rest as well, this is the way to name it<br /> :::::::*- somehow inconsistent with non-ambiguous other key pages (although ambiguous and non-ambiguous pages are different now anyway)<br /> :::::::*- less easy to understand from the name what device it is (but the iOS version is also not directly visible)<br /> :::::::--[[User:Http|http]] ([[User talk:Http|talk]]) 11:10, 2 January 2014 (UTC)<br /> ::::::::To me, that makes it worse. Why can we not use the rounded &quot;()&quot; brackets? I mean, it will only be duplicated in the key page urls, in which if it must be, just do &quot;iPhone 4 iPhone3,1&quot;. Does not seem too bad to me. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 11:18, 2 January 2014 (UTC)<br /> ::::::::::We ''don't want to'' use parenthesis because then we get double parenthesis (&lt;code&gt;Telluride 9A334 (iPhone 4 (3,1))&lt;/code&gt;). We would have to use braces (&lt;code&gt;Telluride 9A334 (iPhone 4 [3,1])&lt;/code&gt;), but MediaWiki chokes when there's braces in a link unless you use &lt;code&gt;&amp;lt;nowiki/&amp;gt;&lt;/code&gt;; and that would mean ''everywhere'' there's a firmware link. --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 13:19, 2 January 2014 (UTC)<br /> ::::::::That ''is'' what I suggested in my reply... As for your first disadvantage, it only applies to the iPads where Apple has gotten confusing. Actually, now that I think of that, option #4 above does look nice. However, I still don't like the redundency of having &lt;code&gt;iPhone&lt;/code&gt; in there twice. And as I said before, options #1 and #3 just look weird. So we're stuck at either redundency or looking weird. But then again, it wouldn't be redundent for the non-existent iPad key page links where Apple decided to be annoying with their firmware monikers. --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 13:19, 2 January 2014 (UTC)<br /> :::::::::Could we not just use the parenthesis but just not in the key page URL's? I mean, &quot;iPhone 4 (iPhone3,1)&quot; but in the urls for key pages, &lt;code&gt;Telluride 9A334 (iPhone_4_iPhone3,1)&lt;/code&gt;? That seems fine here. The underscores are currently there anyway. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 13:32, 2 January 2014 (UTC)<br /> ::::::::::This seems fine to me… Well, aside from the underscores. Other than that, we're actually already doing the same thing until the changes are implemented. (Key pages say &quot;(iPhone 4 GSM)&quot; while other parts of the wiki say &quot;iPhone 4 (GSM model).&quot;) --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 18:05, 2 January 2014 (UTC)<br /> ::::::::I think that &quot;iPhone 4 (iPhone3,1)&quot; does look the nicest, and I don't really feel like it's redundant. I also like the idea of just saying 'iPhone3,1'. If either of those options doesn't work, it might be good to do something like &quot;iPhone 4; iPhone3,1&quot; or &quot;iPhone 4 | iPhone3,1&quot;.--[[User:CompilingEntropy|CompilingEntropy]] ([[User talk:CompilingEntropy|talk]]) 16:46, 2 January 2014 (UTC)<br /> :::::::::The underscores were stated due to the key page URL's use that. I did not mean use that throughout. Was just to give an example, [[User:Dialexio|Dialexio]]. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 13:16, January 2, 2014‎ (UTC)<br /> ::::::::::So we have to decide between<br /> ::::::::::#&quot;Telluride 9A334 (iPhone 4 iPhone3,1)&quot; (name on link could be &quot;Telluride 9A334 (iPhone 4 [iPhone3,1])&quot; or whatever fits best in the context)<br /> ::::::::::#&quot;Telluride 9A334 (iPhone3,1)&quot;<br /> ::::::::::I would prefer #2 (for advantages/disadvantages see list above), but could also live with the other one. Votes? --[[User:Http|http]] ([[User talk:Http|talk]]) 22:06, 2 January 2014 (UTC)<br /> :::::::::::I would prefer #1 because it would be more consistent. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 22:14, 2 January 2014 (UTC)<br /> :::::::::::Count my vote for #2. I could go either way, but option #2 looks nicer. But just to double-check (yet again), we ''are'' using &quot;iPhone 4 (iPhone3,1)&quot; in places like [[Firmware]]'s headings, right? --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 18:19, 7 January 2014 (UTC)<br /> ::::::::::::Headings/titles/links: we didn't decide on that, but I think we can put whatever fits best in the context of a page. So that's a 'yes'. --[[User:Http|http]] ([[User talk:Http|talk]]) 23:53, 9 January 2014 (UTC)<br /> :::::::::::::This has been completed. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 10:12, 15 March 2014 (UTC)<br /> <br /> == Key page template ==<br /> I actually like the idea of a database to an extent. I bet I could put together an extension that creates a [[Special:SpecialPages|special page]] that allows read access to everyone (and r/w access to users). Any edits to the key &quot;pages&quot; wouldn't cause a [[Special:RecentChanges|recent changes]] log. If we ever needed to update the layout, we would just need to update the extension. We could even have an API.<br /> The only limitation is that updates to the extension would require either [[User:geohot|George]] or [[User:Dialexio|Alex]] needing to upload the fix. If we were to set up an external site, then all links to it would need to be wrapped with &lt;code&gt;&amp;lt;span class=&quot;plainlinks&quot;&amp;gt;...&amp;lt;/span&amp;gt;&lt;/code&gt;.<br /> Maybe a simple extension that takes links and redirects you to the external site? That could work. Like, we would have a link to, say, &lt;code&gt;[[&lt;nowiki/&gt;Special:Keys/iPad1,1/9A405]]&lt;/code&gt; which would give an HTTP &lt;code&gt;301 Moved Permanently&lt;/code&gt; header to, say, &lt;code&gt;&lt;nowiki&gt;http://ioskeys.com/iPad1,1/9A405&lt;/nowiki&gt;&lt;/code&gt;. Granted, someone would have to pay for the domain, but it would solve this problem. I may be able to pay for the domain if I make enough money by the time I finish writing everything. Any opposition? --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 16:48, 21 November 2013 (UTC)<br /> :I do not like the idea. I like the idea of the database to a degree, but I think that the pages should remain on this wiki. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 17:03, 21 November 2013 (UTC)<br /> ::I don't see this solving any problem— the backlash against changing the key page template was because of (unnecessary?) changes to the arguments, and the frequency of how often such changes were being proposed/applied. How would a database prevent it? For instance, let's say the database columns are all decided on. Suddenly, it's decided that SHA-1 hashes should be added as well, or perhaps &quot;VFDecryptKey&quot; will be renamed to &quot;FSKey.&quot; People submitting keys would still be bothered with having to adjust for those changes. --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 17:40, 21 November 2013 (UTC)<br /> :::That with the database is something I'll implement anyway (if not someone else is faster, as I'm quite busy). I just threw that in here as it might solve the problem of the frequent template updates (which is/was wrong anyway). From there it would be easy to create the VFDecrypt page with an overview link or lists of missing keys and that stuff, so the wiki would not need any direct links. But it would mean that we either completely remove all keys here from the wiki and embrace that solution or have them still duplicate (which then doesn't solve the problem). Dialexio: renaming columns can be handled without interface changes, but that's another topic. So let's forget about this database thing for now and we can discuss again when I have something. We certainly don't want to add extensions for that. So back to the discussion about the renaming: If I understood this correctly, you only want to rename A5+ devices and therefore no key pages would be affected. Is my understanding correct? --[[User:Http|http]] ([[User talk:Http|talk]]) 22:08, 21 November 2013 (UTC)<br /> ::::As long as the pages stay on this wiki, I do not mind. Although, a database could be pointless as with only 50 more pages to edit for the new format, there is no planned new format/changes again. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 22:16, 21 November 2013 (UTC)<br /> ::::About the renaming, that is correct; I'm only interested in changing the cellular labels on A5/+ devices. (Well, the iPad 2 can remain as-is.) --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 00:02, 22 November 2013 (UTC)<br /> :::::Oh, well that would just make things more complicated/inconsistent. We should do all or none. About the template idea, there is also no need as it is not likely we will change the format again. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 00:35, 22 November 2013 (UTC)<br /> ::::::Do we really need to CHANGE THE FORMAT 50 TIMES IN A ROW? The old one before everything was messed with worked fine enough. [[User:Winocm|Winocm]] ([[User talk:Winocm|talk]]) 18:22, 27 November 2013 (UTC)<br /> :::::::It was actually one change, which was completed. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 18:32, 27 November 2013 (UTC)<br /> <br /> ==Login prompt revision suggestion==<br /> I wrote a suggestion here: [[MediaWiki talk:Loginprompt]] (since I don't have permission to edit [[MediaWiki:Loginprompt]] directly) - I'd be interested in whether it sounds like a good idea to other people. [[User:Britta|Britta]] ([[User talk:Britta|talk]]) 01:00, 8 October 2013 (UTC)<br /> <br /> ==Homepage suggestions==<br /> Under &quot;Application Development&quot;, what about linking to [http://iphonedevwiki.net/index.php/Main_Page iPhoneDevWiki]? It's also a community-edited technical resource, and it links to this wiki. It could be helpful to add a little more detail to &quot;Get [[up to speed]] in the community.&quot;, like this: &quot;Get [[up to speed]] in the community - learn about how jailbreaks work.&quot; Under &quot;Definitions&quot;, it could be helpful to list all the firmware tags in one line or sub-list, similar to how Jailbreak is organized next to Tethered jailbreak and Untethered jailbreak, both to save space and help readers understand the list. --[[User:Britta|Britta]] ([[User talk:Britta|talk]]) 23:01, 20 October 2013 (UTC)<br /> :A link to the iPhoneDevWiki sounds good. I wonder if we should have an &quot;External Links&quot; or &quot;Other Resources&quot; section to include links to other sites (such as the [http://blog.iphone-dev.org/ iPhone Dev Team blog]) though. As for the &quot;Up to Speed&quot; page, I feel like the entire page could be reworked a bit— and perhaps even receive a new, clearer name ([[Introduction]]? [[Preface]]? Or something else?)— the current name makes it sound like it's for people that last paid attention to jailbreaking when the App Store didn't exist. And yeah, moving the IMG3 tags to a sub-list sounds like a really good idea. (Admittedly, I actually don't care for its inclusion in the first place, but that's just a personal preference.) --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 00:10, 21 October 2013 (UTC)<br /> ::There's already [[Useful Links]] with some links to other core community resources (which could be updated and rearranged) - I was just thinking that it'd be especially useful to link to iPhoneDevWiki prominently since it's likely for TheiPhoneWiki visitors to also be interested in relatively-organized technical information about development. Changing the name of &quot;Up to Speed&quot; sounds fine to me too - that page didn't get much attention since 2008 until I sort of commandeered it to serve as an &quot;intro to jailbreaking&quot; page. :) It could be renamed &quot;getting started&quot;, as in &quot;how to get started on learning about research into iOS devices, especially security research (such as jailbreaks)&quot;. [[User:Britta|Britta]] ([[User talk:Britta|talk]]) 00:31, 21 October 2013 (UTC)<br /> Also I'd love to see a dedicated section for &quot;Good tasks for new editors&quot;, where we could maintain a list of relatively easy/straightforward suggested edits that wouldn't require vast technical knowledge, like updating that links page. Where would that go? Add it as a sub-section of [[The iPhone Wiki:Current events]] and link that section from the homepage or something? Or make a new page? [[User:Britta|Britta]] ([[User talk:Britta|talk]]) 00:40, 21 October 2013 (UTC)<br /> <br /> ==What is 0x5265c384 in the boot process?==<br /> Does anybody know where &lt;code&gt;0x5265c384&lt;/code&gt; points to in the boot process? I haven't been able to find anything on it. --[[User:Ph0enix|Ph0enix]] ([[User talk:Ph0enix|talk]]) 20:14, 23 October 2013 (UTC)<br /> <br /> ==License for contributions==<br /> This wiki has never had an official license for contributions. Now, IANAL, but IIRC, this means that you can't use ''anything'' posted here unless it qualifies as fair-use. What I propose is that we set a license and add a notice that states that any contributions after a set date are to be licensed under that license (that's kindof a mouthful). I think we should use the [http://creativecommons.org/licenses/by-sa/3.0/ CC-by-SA 3.0] as [[wikipedia:Wikipedia:Text of Creative Commons Attribution-ShareAlike 3.0 Unported License|Wikipedia uses it]], but that's just me. Any ideas? --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 19:53, 9 November 2013 (UTC)<br /> :Well, the edit info already says all this:<br /> Please note that all contributions to The iPhone Wiki may be edited, altered, or<br /> removed by other contributors. If you do not want your writing to be edited mercilessly,<br /> then do not submit it here.<br /> You are also promising us that you wrote this yourself, or copied it from a public<br /> domain or similar free resource (see The [[:The iPhone Wiki:Copyrights|iPhone Wiki:Copyrights]] for details). '''Do not'''<br /> '''submit copyrighted work without permission!'''<br /> For me, that's enough. I don't need a 50 page license. But if you want to formalize this more, go ahead. --[[User:Http|http]] ([[User talk:Http|talk]]) 20:35, 9 November 2013 (UTC)<br /> :Sounds good. It's good practice to have an official license, just in case any disputes happen someday, and to ensure that it's OK to copy text over to Wikipedia (for example). [[User:Britta|Britta]] ([[User talk:Britta|talk]]) 21:32, 9 November 2013 (UTC)<br /> <br /> ==Banner Replacement?==<br /> I kinda feel like the banner on the front page is getting a little stale, so I'm interested in seeing it replaced. I tossed a proposal [https://twitter.com/Draxelf/status/408295008794845184 on Twitter] a couple of days ago (which is admittedly plain, but Myriad Set…), but I haven't heard any opinions on replacing the banner. Are there any thoughts on this matter? --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 17:42, 6 December 2013 (UTC)<br /> :Or, [http://imgur.com/wJFqPl1 this]. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 18:22, 6 December 2013 (UTC)<br /> :Looks nice in Myriad! More professional. [[User:Britta|Britta]] ([[User talk:Britta|talk]]) 04:01, 7 December 2013 (UTC)<br /> <br /> ==Date Format==<br /> I see that [[User:IAdam1n|iAdam1n]] started to unify the date formats in this wiki. While I like this to be consistent, actually we should've talked about what format to use before changing it. I like the d_mon_yyyy format though. I also saw that he removed the &lt;code&gt;&amp;amp;nbsp;&lt;/code&gt; between the date parts on the [[iFaith]] page that I added once purposefully. The reason was that when making the browser window small (or on the iPhone) that the date wraps to two lines, which is almost always undesired. The question is if we should do that everywhere too? Additionally, as we now seem to have a &quot;standard&quot; here, we should document it, so that new users know what format to use. -- [[User:Http|http]] ([[User talk:Http|talk]]) 17:42, 30 December 2013 (UTC)<br /> :I just made it consistent. If you want the &lt;code&gt;&amp;amp;nbsp;&lt;/code&gt; back, feel free to add it. I removed it as it did nothing (previewing on OS X). We should use the format I used throughout the wiki and not Dec 23, 2013 etc. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 18:32, 30 December 2013 (UTC)<br /> ::&lt;code&gt;&amp;amp;nbsp;&lt;/code&gt; stands for &quot;'''n'''on-'''b'''reaking '''sp'''ace&quot;. It is essentially a space, but with a property that prevents word wrap from occurring between the two words it's between. Look at [[Firmware Keys]] on a small enough screen (1024 across should do it). Your browser should preserve the space between the date &quot;words&quot;. Now, go into the edit page and remove the &lt;code&gt;&amp;amp;nbsp;&lt;/code&gt; from everything in one table. Your browser will now word wrap the date &quot;words&quot;. --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 00:04, 5 January 2014 (UTC)<br /> :What I actually want to do is use &lt;code&gt;{{[[Template:Start date|start date]]}}&lt;/code&gt; instead of plain dates in areas where dates are used as a statistic; for example, [[Firmware]], [[Firmware Keys]], [[SHSH]], [[Timeline]], etc. Places where dates are used to record when something happened, for example on [[evasi0n7]], &quot;On 28 December 2013...&quot;, should use the date flat out in the source. --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 00:04, 5 January 2014 (UTC)<br /> <br /> == Template documentation ==<br /> Whenever using templates that are copied here from Wikipedia, I almost always forget the parameters of the template. I then have to open Wikipedia and search for the template. What I want to do it copy the template documentation from Wikipedia here. To work around the licensing issue, we can create our own template that you would include at the bottom of the copied documentation that says the documentation comes from Wikipedia (because Wikipedia uses [[wikipedia:Wikipedia:Text of Creative Commons Attribution-ShareAlike 3.0 Unported License|CC-BY-SA 3.0]] which says our copied text must be under CC-BY-SA 3.0 ''and'' attribute Wikipedia and her editors. I can write the text for license template. Any ideas? Any opposition? If not, I'll begin in a few days. --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 00:04, 5 January 2014 (UTC)<br /> :I don't see why not. That's what I've seen done on other wikis. — '''[[User:Spydar007|&lt;span style=&quot;color:#ff5a00;&quot;&gt;Spydar007&lt;/span&gt;]] [[User talk:Spydar007|&lt;span style=&quot;color:orange;&quot;&gt;(Talk)&lt;/span&gt;]]''' 16:56, 18 January 2014 (UTC)<br /> <br /> == Mainpage &quot;iPhone Hackers&quot; List ==<br /> <br /> I think the &quot;iPhone Hackers&quot; List of the mainpage needs to be updated. Here are some people that need adding:<br /> <br /> *[[Pimskeks]]<br /> *[[User:iH8sn0w|iH8sn0w]]<br /> *[[User:winocm|winocm]]<br /> *SquiffyPwn<br /> *[[i0n1c]]<br /> <br /> Are there any others you can think of? — '''[[User:Spydar007|&lt;span style=&quot;color:#ff5a00;&quot;&gt;Spydar007&lt;/span&gt;]] [[User talk:Spydar007|&lt;span style=&quot;color:orange;&quot;&gt;(Talk)&lt;/span&gt;]]''' 16:55, 18 January 2014 (UTC)<br /> :I agree with the list except I do not think that SquiffyPwn has done anything huge, except help with [[p0sixspwn]] and i0n1c shouldn't be added. Just my opinions. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 20:53, 5 February 2014 (UTC)<br /> :: [[User:ph0enix|Me]], [[User:5urd|5urd]] and [[User:phyrrus9|phyrrus9]] have definitely earned our keep refer to http://theprivatedevteam.blogspot.com/2012/04/ios-51-semi-untethered-jailbreak.html --[[User:Ph0enix|Ph0enix]] ([[User talk:Ph0enix|talk]]) 02:17, 8 February 2014 (UTC)<br /> :::I disagree, you are not that well know, like pimskeks etc. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 09:25, 8 February 2014 (UTC)<br /> ::::I agree with iAdam1n. You are not known enough. — '''[[User:Spydar007|&lt;span style=&quot;color:#ff5a00;&quot;&gt;Spydar007&lt;/span&gt;]] [[User talk:Spydar007|&lt;span style=&quot;color:orange;&quot;&gt;(Talk)&lt;/span&gt;]]''' 14:52, 8 February 2014 (UTC)<br /> :::::Are you kidding me?? we have worked with many &quot;well known&quot; hackers and are in constant communication with people like p0sixninja! this is a joke we dont have to be &quot;well known&quot; to be influential hackers who not to mention have been running support and hacking in the community for 4 almost 5 years! --[[User:Ph0enix|Ph0enix]] ([[User talk:Ph0enix|talk]]) 18:08, 15 February 2014 (UTC)<br /> ::::::Support does not count. I am sticking with my original decision. AFAIK, you released no jailbreaks or found any new exploits, not as well know as the main hackers. Feel free to share what you have found/made if you want and also you can see what others say. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 19:24, 15 February 2014 (UTC)<br /> :::::::are you kidding me!! http://theprivatedevteam.blogspot.com/2012/04/ios-51-semi-untethered-jailbreak.html that is the reason i have high quality followers like posixninja and nitotv just because you guys are too young in the community to know about our major help to the community doesnt mean we are it is a closed sourced exploit but very functional and based off of redsn0w that implements our exploit now if you wanna get your thumb out of your buts and pay attention it would be great --[[User:Ph0enix|Ph0enix]] ([[User talk:Ph0enix|talk]]) 22:17, 15 February 2014 (UTC)<br /> ::::::::Why is this being brought up again? The answer was no before, and it's going to remain no for the reasons http stated before. I should add that who follows who on Twitter doesn't really mean anything— I have nitoTV, chronic, iH8sn0w, and winocm as followers, but that doesn't mean [https://twitter.com/Dialexio/status/376801384752222208 this] was a legitimate jailbreak by any means. --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 23:05, 15 February 2014 (UTC)<br /> ::::::::: Jeez idk maybe because we RELEASED A WORKING TOOL AND KEEP BEING BLOWN OFF BY INFERIOR ASS HOLES WHO REFUSE TO ADMIT IT! when you create a tool then challenge it till then we should be put on the list for discovering and implementing a previously unknown userland exploit and building a tool to ease the process... --[[User:Ph0enix|Ph0enix]] ([[User talk:Ph0enix|talk]]) 23:22, 15 February 2014 (UTC)<br /> ::::::::::Your insults aren't helping your credibility. Just saying. --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 23:35, 15 February 2014 (UTC)<br /> ::::::::::: well if i wouldn't have to have been asking for so long then i wouldn't be so upset my credibility is there whether you choose to ignore it or not is up to you. our tool is a working tool and we discovered and implemented a exploit that should be grounds for our names to be on the list,and the followers point is that we may not be well known but the people who follow us are legit people. quality over quantity. --[[User:Ph0enix|Ph0enix]] ([[User talk:Ph0enix|talk]]) 23:49, 15 February 2014 (UTC)<br /> ::::::::::::And now, your arguing with the administration. The answer is no. End of. — '''[[User:Spydar007|&lt;span style=&quot;color:#ff5a00;&quot;&gt;Spydar007&lt;/span&gt;]] [[User talk:Spydar007|&lt;span style=&quot;color:orange;&quot;&gt;(Talk)&lt;/span&gt;]]''' 09:13, 16 February 2014 (UTC)<br /> :Coming back to this old discussion, the decision at that time was to not even include iH8sn0w there, so I don't see a reason to include much lesser known people. For the overview list, we already have the [[:Category:Hackers]]. The main page is just for the 5-10 currently most important people. Regarding names, there should be a wide consensus of the people listed. If you ask me today, I'd comment like this:<br /> :*i0n1c is not working on public jailbreaks, so don't include<br /> :*geohot has retired from the scene, he could get removed, but as founder of this wiki and best contributor to the scene of all time, better leave him there<br /> :*winocm new shooting star, could get added<br /> :*iH8sn0w could get added with all the tools created<br /> :*all others I would not add or only added to category mentioned above<br /> :Remember that the list should be really short, so adding anyone would most probably mean to remove someone less important. Also, number of followers on Twitter doesn't mean anything; all these people follow me too and I wouldn't claim to be that important. This shouldn't discourage anybody not on this main page to continue his/her work. If this is causing these feelings, I think we should remove the list there entirely. --[[User:Http|http]] ([[User talk:Http|talk]]) 14:28, 16 February 2014 (UTC)<br /> :: Thanks [[User:Http|http]] I feel like in that case their should be a new category made for the people who have worked very hard but by those standards do not fit in that category, something like security researchers for the people who are doing a lot of behind the scenes work and certainly deserve some recognition somewhere on here. Just a thought though. --[[User:Ph0enix|Ph0enix]] ([[User talk:Ph0enix|talk]]) 22:29, 18 February 2014 (UTC)<br /> == Category Security Researchers==<br /> Hi all! i've created the category Security Researchers in order to cut down on the pages categorized as hackers as it apparently needs to be more exclusive. i've been adding the less known or inactive hackers from the hacker page but have not removed them from the hackers page. I feel that it should be a vote on who gets removed from the hackers page so my first suggestion is [[User:Fallensn0w‎]] as he has been inactive for a very long time and didn't do a lot in the first place. --[[User:Ph0enix|Ph0enix]] ([[User talk:Ph0enix|talk]]) 15:57, 22 February 2014 (UTC)<br /> <br /> == Replacing old/broken download links ==<br /> <br /> I have noticed on pages like [[evasi0n]] and [[p0sixspwn]] that some of the dwonlaod links no longer work because the developers have taken the revision of the software down. Rather than leave them there, I suggest we replace the links with ones that can be accessed (such as with ones in my MEGA). For example, version 1.0 of [[evasi0n]] was taken down from MEGA and no longer exists. However, I have version 1.0 saved in my MEGA Drive so I could replace the broken links with ones to downloads in my MEGA Drive. What do you guys think of this? — '''[[User:Spydar007|&lt;span style=&quot;color:#ff5a00;&quot;&gt;Spydar007&lt;/span&gt;]] [[User talk:Spydar007|&lt;span style=&quot;color:orange;&quot;&gt;(Talk)&lt;/span&gt;]]''' 10:07, 30 March 2014 (UTC)<br /> :I do not like this idea as it breaks copyright. We normally just put a line through with &lt;code&gt;style=&quot;text-decoration: line-through;&quot;&lt;/code&gt;. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 10:18, 30 March 2014 (UTC)<br /> ::I know but I think that people should still be able to download the old versions. — '''[[User:Spydar007|&lt;span style=&quot;color:#ff5a00;&quot;&gt;Spydar007&lt;/span&gt;]] [[User talk:Spydar007|&lt;span style=&quot;color:orange;&quot;&gt;(Talk)&lt;/span&gt;]]''' 11:23, 30 March 2014 (UTC)<br /> :::I disagree. Except for [[evasi0n7]], latest versions work best and with evasi0n7, all links work. We do not want unofficial links because of copyright. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 17:35, 30 March 2014 (UTC)<br /> ::::This contradicts your actions a bit— I've never seen official MEGA links for newer releases of evasi0n7, yet you filled it in for some of them. But I digress… In all honesty, I wouldn't mind, as long as no copyrights are violated. There should be some sort of distinction that it's not an official link though. --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 23:28, 30 March 2014 (UTC)<br /> :::::The MEGA links that I have added myself have been from evasi0n.com with &quot;view source&quot; in a browser. The earlier releases, [[User:5urd|5urd]] added them so I don't know about those. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 07:23, 31 March 2014 (UTC)<br /> ::::::To be honest, it is only violating copyright if the jailbreak tools cost money. Since they are free, it is not violating copyright. — '''[[User:Spydar007|&lt;span style=&quot;color:#ff5a00;&quot;&gt;Spydar007&lt;/span&gt;]] [[User talk:Spydar007|&lt;span style=&quot;color:orange;&quot;&gt;(Talk)&lt;/span&gt;]]''' 15:11, 31 March 2014 (UTC)<br /> :::::::Copyright laws are '''always''' in place, regardless of how much something costs, unless the creator waives their copyrights. --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 05:25, 1 April 2014 (UTC)<br /> :::::So, should I go ahead a do it? I could put a warning triangle symbol before it so that it is shown to be an unofficial link. — '''[[User:Spydar007|&lt;span style=&quot;color:#ff5a00;&quot;&gt;Spydar007&lt;/span&gt;]] [[User talk:Spydar007|&lt;span style=&quot;color:orange;&quot;&gt;(Talk)&lt;/span&gt;]]''' 14:42, 31 March 2014 (UTC)<br /> ::::::I say no. On JailbreakQA, one moderator was told by MuscleNerd to remove a hosted version that included the edit for 7.0.6 before evasi0n7 1.0.7 was released. There is no need for older versions since the latest works, with the exception of evasi0n7 1.0.8 but 1.0.7 links are still valid. I strongly disagree to add this. Also it should have at least a week on discussion. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 15:59, 31 March 2014 (UTC)<br /> :::::::That sounds more like MuscleNerd not wanting tampered copies of evasi0n7 to float around. That being said, I don't know whether he or the rest of the evad3rs would be fine with rehosting untouched copies of their files though. --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 05:25, 1 April 2014 (UTC)<br /> <br /> == geeksn0w ==<br /> <br /> I think we should make a page for geeksn0w. It is a jailbreak tool used by a significant amount of users who have iPhone 4's. I don't see why there isn't a page already. What do you guys think? — '''[[User:Spydar007|&lt;span style=&quot;color:#ff5a00;&quot;&gt;Spydar007&lt;/span&gt;]] [[User talk:Spydar007|&lt;span style=&quot;color:orange;&quot;&gt;(Talk)&lt;/span&gt;]]''' 15:07, 10 April 2014 (UTC)<br /> :I personally like the idea. I would at least like to see it added to [[iPhone 4]] on [[Jailbreak|the jailbreak page]]. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 15:32, 10 April 2014 (UTC)<br /> ::Exactly, we should add it to the [[Jailbreak]] page and create a page on it. What do you think of creating a page for the developer/hacker, BlackGeekTutorial? He is just about to start working on [[iFaith]] for iOS 7.<br /> :::Personally, we don't need a page on him I don't think until he has made a lot. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 15:52, 10 April 2014 (UTC)<br /> ::::On the page, I am thinking of having download links to previous versions (in my MEGA drive) since BlackGeek doesn't give out other links. What do you think? — '''[[User:Spydar007|&lt;span style=&quot;color:#ff5a00;&quot;&gt;Spydar007&lt;/span&gt;]] [[User talk:Spydar007|&lt;span style=&quot;color:orange;&quot;&gt;(Talk)&lt;/span&gt;]]''' 16:10, 10 April 2014 (UTC)<br /> :::::I think we should only use official links but thats just me. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 22:56, 25 April 2014 (UTC)<br /> ::::::I know we should use official links, but BlackGeek doesn't keep the links active. Also, he doesn't use MEGA. He just hosts it in the portfolio for his website. But he uses Adfly links to host them too. Do we really want Adfly links here? — '''[[User:Spydar007|&lt;span style=&quot;color:#ff5a00;&quot;&gt;Spydar007&lt;/span&gt;]] [[User talk:Spydar007|&lt;span style=&quot;color:orange;&quot;&gt;(Talk)&lt;/span&gt;]]''' 12:10, 26 April 2014 (UTC)<br /> :::::::If that is the official link, I would say yes. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 14:11, 26 April 2014 (UTC)<br /> <br /> == Cyberelevat0r ==<br /> I think we should make a page for Cyberelevat0r (i0n1c's 7.1.x Untethered Jailbreak). There is multiple proof that he might release it and we can fill it with information about all other hackers that have 7.1.x untethered jailbreaks as well. What do you think? — '''[[User:Spydar007|&lt;span style=&quot;color:black;&quot;&gt;Spydar007&lt;/span&gt;]] [[User talk:Spydar007|&lt;span style=&quot;color:gray;&quot;&gt;(Talk)&lt;/span&gt;]]''' 05:40, 22 May 2014 (UTC)<br /> :No. If (and it's a massive if) it gets released, then ok. Not until. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 08:01, 22 May 2014 (UTC)<br /> <br /> == Email notifications? ==<br /> 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)<br /> <br /> == Ambiguous names ==<br /> I feel like the names for [[Symlinks]] and [[Symbolic Link Vulnerability]] is a bit too ambiguous. Now, I don't anticipate there being much confusion, particularly since nobody really cares about 1.x anymore, but I would like to make the distinction clearer. I think both articles should be renamed, but I have no idea on what to rename them to (or even if you guys approve). I thought of using the CVE ID, but Apple doesn't provide one for [[Symlinks]] (or even any indication that they fixed it). ([[Symbolic Link Vulnerability]] was assigned CVE-2013-5133.) --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 17:51, 2 July 2014 (UTC)<br /> :They are referred to as the Symbolic Link by people like MuscleNerd and iH8sn0w so, in my opinion, they should be kept as their current names. — '''[[User:Spydar007|&lt;span style=&quot;color:black;&quot;&gt;Spydar007&lt;/span&gt;]] [[User talk:Spydar007|&lt;span style=&quot;color:gray;&quot;&gt;(Talk)&lt;/span&gt;]]''' 18:06, 2 July 2014 (UTC)<br /> ::I don't mind if one of them keeps their current name, but there should be something to make the distinction clearer. --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 01:13, 3 July 2014 (UTC)<br /> <br /> == IRC Channel on Freenode ==<br /> Howdy iphonewiki folks, I have #theiphonewiki registered on freenode, and am ready to have people come in (it's been ages since this idea has been brought up). Shall we open it? I'd like to get some ops in there to help out. --[[User:Haifisch|Haifisch]] ([[User talk:Haifisch|talk]]) 05:48, 6 July 2014 (UTC)<br /> &lt;br /&gt;<br /> I think we should make an IRC channel for this wiki. It can be either #theiphonewiki or #iphonewiki on freenode. The channel would be used for discussions, such as the TLC of the Jailbreak page for example. It would make getting things sorted a lot easier, since we could just ping each other different ideas. I know this idea was made before, but the channel never really got anywhere. What do you guys think of this idea? We would need to decide who has founder, op and voice etc. on the channel here. — '''[[User:Spydar007|&lt;span style=&quot;color:black;&quot;&gt;Spydar007&lt;/span&gt;]] [[User talk:Spydar007|&lt;span style=&quot;color:gray;&quot;&gt;(Talk)&lt;/span&gt;]]''' 06:58, 6 July 2014 (UTC)<br /> : This is idiotic. You just want to do it yourself cause you want power. We won't help you feed your ego. --[[User:Goeo|goeo_]] ([[User talk:Goeo|talk]]) 19:43, 6 July 2014 (UTC)<br /> :: You have never edited on this wiki in your life before so STFU. — '''[[User:Spydar007|&lt;span style=&quot;color:black;&quot;&gt;Spydar007&lt;/span&gt;]] [[User talk:Spydar007|&lt;span style=&quot;color:gray;&quot;&gt;(Talk)&lt;/span&gt;]]''' 05:48, 7 July 2014 (UTC)<br /> : Being that I own #theiphonewiki, the original channel in which the wiki's channel was going to be on, I have control over who's moderating the channel. One op will be me, I have 3+ years of IRC moderation experience (To be honest, Is this even CV worthy? :P) we can choose the other operators when the channel becomes somewhat popular. ps. Why make two topics for this? --[[User:Haifisch|Haifisch]] ([[User talk:Haifisch|talk]]) 08:03, 6 July 2014 (UTC)<br /> :: That most definitely is CV worthy. I've seen Spydar007 moderate a channel, it crashed in a week or so. Not to mention the channel wasn't even his, and he kinda took it over anyway. --[[User:Goeo|goeo_]] ([[User talk:Goeo|talk]]) 19:43, 6 July 2014 (UTC)<br /> ::No, no, no. The community decides. Juts because Farahtwiggy asked you to register it before, doesn't mean you get to be an op there now. This was my idea (Dialexio can vouch). You have no control over who are ops there. {{unsigned|Spydar007|04:11, July 6, 2014 (UTC)}}<br /> ::: One &quot;no&quot; is enough. Farah, really, doesn't have much (if anything) to do with this, the channel was registered a year ago. Your childish response above does not show me that you can handle owning the channel, nor do the rumors of you abusing channel control in your personal channel. It's really not your idea, it may have just now come to your mind, but adaminsull and I have gone through this whole deal before (one year ago). Join me on #theiphonewiki if you'd like to chat this out. --[[User:Haifisch|Haifisch]] ([[User talk:Haifisch|talk]]) 08:22, 6 July 2014 (UTC)<br /> ::::I don't know what's happening off of the wiki so I might only have part of the picture. I definitely don't see Haifisch as trying to steal credit for this idea, which actually was brought up about ages ago. I'm not much of an IRC guy, so my opinion might not have that much weight for a lot of this discussion, but I feel that the channel would be better in Haifisch's hands given his experience. Ownership/management/whatever for the IRC channel should certainly be open for discussion though. I really don't care too much about whoever gets to run it, as long as the person is someone that the community knows, respects, and trusts. (Same goes for the channel ops.) --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 17:42, 6 July 2014 (UTC)<br /> :It does not sound like a good idea to have an IRC channel for this wiki. It is useful for discussion of this wiki's articles to continue to be be done publicly on the wiki (on the appropriate talk pages), so that everyone interested in the wiki can easily contribute to the discussion, and so that there is a well-organized public record of discussions that we can all easily refer to. IRC channels are also very fertile breeding grounds for social conflicts and unhappiness (as we've seen already), which is helpful to skip. In any case, this should be discussed at [[The iPhone Wiki:Community portal]] instead of here - this page is for discussing modifications to the Main Page, and that one is for general discussions about TheiPhoneWiki. [[User:Britta|Britta]] ([[User talk:Britta|talk]]) 09:46, 7 July 2014 (UTC)<br /> <br /> == Moving to Canada ==<br /> I'm moving this server in the next few days to a quality server in Canada. It'll be running inside a VM, so I'll also look into giving admins more access. Hopefully the periodic outages will stop. Maybe I'll add some SSL certs. --[[User:Geohot|geohot]] ([[User talk:Geohot|talk]])<br /> :Nice, thanks! HTTPS would be great. --[[User:Britta|Britta]] ([[User talk:Britta|talk]]) 21:08, 14 August 2014 (UTC)<br /> ::So we're not in canada yet?--[[User:Awesomebing1|Awesomebing1]] ([[User talk:Awesomebing1|talk]]) 20:32, 30 August 2014 (UTC)<br /> You should all be in Canada now, with 8&amp;nbsp;GiB of Canadian RAM. We also have [https://theiphonewiki.com/wiki/Main_Page HTTPS], but it avoids the [[wikipedia:Squid (software)|Squid proxy]]. It's fine for people making edits but I don't plan on changing the default anytime soon. --[[User:Geohot|geohot]] ([[User talk:Geohot|talk]]) 04:43, 2 September 2014 (UTC)<br /> :Yay! Thanks as always George! Any plans on adding back SSH? There's a few things I'd love to have done. --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 21:40, 2 September 2014 (UTC)<br /> ::Thanks [[User:Geohot|geohot]]! Hopefully now there will be less downtime ;p --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 07:41, 3 September 2014 (UTC)<br /> :Sweeeeeeeet. :D --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 15:16, 3 September 2014 (UTC)</div>

Danzatt https://www.theiphonewiki.com/w/index.php?title=IM4P_File_Format&diff=42169 2014-09-15T09:47:35Z

<p>Danzatt: </p> <hr /> <div>The '''IM4P''' file format is a replacement of the [[IMG3 File Format]] used on older devices. It was introduced with [[iOS]] 7.0.1 and appears to be exclusive to the [[iPhone 5c]] and newer, [[iPad Air]] and [[iPad mini 2G]].<br /> <br /> The file is encoded as an DER encoded asn.1 object, structured like this:<br /> <br /> &lt;pre&gt;<br /> sequence [<br /> 0: string &quot;IM4P&quot;<br /> 1: string type - ibot, rdsk, sepi, ...<br /> 2: string description - 'iBoot-1940.1.75'<br /> 3: octetstring - the encrypted data<br /> 4: octetstring - containing asn1 encoded KBAG values<br /> sequence [<br /> sequence [<br /> 0: int: 01<br /> 1: octetstring: iv<br /> 2: octetstring: key<br /> ]<br /> sequence [<br /> 0: int: 02<br /> 1: octetstring: iv<br /> 2: octetstring: key<br /> ]<br /> ]<br /> ]<br /> &lt;/pre&gt;<br /> <br /> each .im4p file is accompanied with a .plist file containing the sha1 of the .im4p file.<br /> <br /> == External Links ==<br /> * [https://twitter.com/i0n1c/status/501299082603020288]<br /> <br /> {{stub}}<br /> <br /> [[Category:File Formats]]</div>

Danzatt https://www.theiphonewiki.com/w/index.php?title=User:Danzatt&diff=42168 2014-09-15T09:25:26Z

<p>Danzatt: Created page with &quot;== Contact == :[https://twitter.com/danzatt Twitter]&quot;</p> <hr /> <div>== Contact ==<br /> <br /> :[https://twitter.com/danzatt Twitter]</div>

Danzatt https://www.theiphonewiki.com/w/index.php?title=Talk:Pangu&diff=42167 2014-09-15T09:20:39Z

<p>Danzatt: Created page with &quot;==Reverse engineering/payload extraction== Has anyone reverse engineered Pangu executable or extracted the payloads (as in case of evasi0n7) ? If so, can you update the pa...&quot;</p> <hr /> <div>==Reverse engineering/payload extraction==<br /> Has anyone reverse engineered Pangu executable or extracted the payloads (as in case of [[evasi0n7]]) ? If so, can you update the page accordingly ? --[[User:Danzatt|Danzatt]] ([[User talk:Danzatt|talk]]) 09:20, 15 September 2014 (UTC)</div>

Danzatt https://www.theiphonewiki.com/w/index.php?title=Talk:AES_Keys&diff=42159 2014-09-14T11:14:13Z

<p>Danzatt: </p> <hr /> <div>==Use kloader to bootstrap patched iBSS/iBEC on A4+ devices==<br /> Has anyone tried loading patched iBSS/iBEC on A4+ device ? That way we would be able to load unsigned ramdisk (which could be used to decrypt kbag even on non-limerain devices). {{unsigned|‎Danzatt|15:58, 12 September, 2014}}<br /> :It won't work as the AES engine gets disabled when the kernel is booting up. Jumping back into iBoot won't reenable it. --[[User:Aker|Aker]] 21:56, 12 September 2014 (GMT+1)<br /> ::Does it make a &quot;call&quot; to coprocessor so that it is disabled on hardware level ? (Are there any details available on how this is done ?). --[[User:Danzatt|Danzatt]] ([[User talk:Danzatt|talk]]) 21:32, 12 September 2014 (UTC)<br /> :::The IOAESAccelerator chip gets a request to restrict the access to the GID key and disables it until the iPhone/iPad/iPod touch is rebooted. -- [[User:Aker|Aker]] 08:54, 13 September 2014 (GMT+1)<br /> ::::Yes, I know that. But I thought bootloader just hides it from the kernel. Is there any source that confirms it is disabled per-reboot ? (Also... How was it possible that XPwn's kernel patcher could patch kernel to grant access to GID key ?) --[[User:Danzatt|Danzatt]] ([[User talk:Danzatt|talk]]) 10:59, 14 September 2014 (UTC)<br /> ::::Well, you're right [https://mobile.twitter.com/coolstarorg/status/450711034743889920] [https://mobile.twitter.com/iH8sn0w/status/450717200568320000] --[[User:Danzatt|Danzatt]] ([[User talk:Danzatt|talk]]) 11:14, 14 September 2014 (UTC)<br /> <br /> ==Greenpois0n Method==<br /> After GP does its magic and the device boots into the patched iBSS, I cannot get the command to decrypt the KBAG to work. In iRecovery, 'go aes dec [long KBAG string]' gives no output. Commands like bgcolor, reboot, etc. work, but I cannot get any feedback from the device to give me the decrypted KBAG. Has anyone gotten this to work? --[[User:Cool name|Cool name]] 16:01, 11 November 2010 (UTC)<br /> :you need a [[payload]] or run -s flag on [[IBSS]] --[[User:Liamchat|liamchat]] 16:29, 11 November 2010 (UTC)<br /> ::I'm pretty sure the payload is already initialized by running GP, because when opening the iRecovery console with 'sudo ./irecovery -s' it spits out stuff about Greenpois0n initializing, aes_crypto_cmd being patched, etc, and it is an iBSS. My trouble is getting the device to respond to the go aes dec command, I think it may be a problem with iRecovery but not sure --[[User:Cool name|Cool name]] 17:03, 11 November 2010 (UTC)<br /> :::well what copy of [[IRecovery]] do you have i know that the one from [[User:GreySyntax]] works also try an [[IRecovery]] script like --[[User:Liamchat|liamchat]] 17:43, 11 November 2010 (UTC)<br /> go aes dec AACACFB9258D7DFBF7D46F21BD9BF27C7E67C673594B7DEE4FF8FE1F08040B1F<br /> go aes dec FF47F3DA0949016984CDED28E286C45CB14B1962B328F82589608C5A5D0A4050<br /> go aes dec 73FFC67694FC821AB9C21CB3CC9A64792D14320F917F469B4935110284990778<br /> go aes dec 3DD9554AB61398A3B6323FA71730A4243837777651DFB8AD212B81ECF194C653<br /> go aes dec 3D2B301E5A7069D52DA258C4B0A2209FA9BA4CEDB120688FC51D3BF1EDEDE5BC<br /> go aes dec E996535613828554253DC21B4875C4BB371FF21699C2D2AF8C02E1137EB1951F<br /> go aes dec 3D538743E45B5B6B6C190B2BBACA705372A3147CC9A60C6856EE2B9B1E60FD85<br /> go aes dec 5FCF5DA27AC995B0B10D76C42ADD5F0BB9268FA88A045EDCCDBC946A73A7CFDC<br /> go aes dec 68D3DE8EA8CC1707D08C983E745EA6A25E40FD532A5BD3BF7760BD540BE257DC<br /> go aes dec 1AE9223C4B8AEBD5F0A30C910212EC8171E3BFC2EF7BF802A39C9C5F45939B2C<br /> go aes dec 87CE52FFEB8E4FB685BA7FA37CBAC0004C9C0B0274FB8A7C1E06D85796063DF0<br /> go aes dec BDB129D92704104423940EC40913FABD30E676CD800E523273DA4E38065B0E13<br /> go aes dec 55D6DE657EB16C5563551C4DA26EE12197783C7100A92695D2B74802F10155C1<br /> go aes dec BA6A3959FBC43D3BCF2708640D5E7B4E5C2306C7ED8A34F7ABC3F49EE6D0BDD4<br /> go aes dec B6689C5BA40B644470C51C35257B984F97F9BE8A3E620086A5A726D7A2C1B7B1<br /> go aes dec 874AD4B93947DAA4D14DDACD3F948F2EFAA207BF6E6FDE3C9D6248E72186894B<br /> go aes dec 9C51D82560C30D976F374F5CB7CC2A7E286FF0067169EA393A8285AC74129D05<br /> /exit note: these are the [[KBAG]]'s of [[Northstar 7D11 (iPod touch 2G)]]<br /> ::::--[[User:Liamchat|liamchat]] 18:25, 11 November 2010 (UTC)<br /> :::::Thank you, GreySyntax's version of iRecovery did the trick :) --[[User:Cool name|Cool name]] 19:32, 11 November 2010 (UTC)<br /> <br /> == Project ==<br /> So I'm working on a project for the AES Engine, May I add the info somewhere in this page? [https://github.com/Absinthed-Dev/AESPayload AESPayload Syringe] --[[User:Haifisch|Haifisch]] 22:38, 13 November 2012 (MST)<br /> :No. Finish your project and ask again. If it's really useful and used by more than 1000 users, we might add it. --[[User:Http|http]] 05:22, 14 November 2012 (MST)<br /> ::Finished --[[User:Haifisch|Haifisch]] 00:03, 17 November 2012 (MST)<br /> :::Mind explaining exactly how one would use it? --[[User:5urd|5urd]] 14:39, 17 November 2012 (MST)<br /> ::::New people to the hacking community (iOS hackers) may want to help by finding the keys to such things as kernelcaches and root fs dmgs. Using this tool they can, this may be the easiest way to find it, It does most of the work for you. All one would need to do is get the KBAG key and run the aes decrypt command with the included irecovery tool (Not of my work). I suggest this as a starting point for the new guys jumping into hardware hacking. --[[User:Haifisch|Haifisch]] 16:39, 17 November 2012 (MST)<br /> <br /> == Finding AES keys. ==<br /> How can I find the AES keys? I have Haifisch's version but I cant find out to compile. Also I dont get irecovery to work. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 18:07, 14 November 2012 GMT}}<br /> :Not being rude, but if you can't compile a simple Makefile project, you need to learn a bit more before delving into things like hacking the device's hardware and software. --[[User:5urd|5urd]] 16:34, 14 November 2012 (MST)<br /> ::I made my version as easy as possible (without just handing him a compiled executable). I want him to learn at least to compile a simple project. --[[User:Haifisch|Haifisch]] 19:14, 14 November 2012 (MST)<br /> :::Did you make it for Mac? Also I cannot get the irecovery -s to work. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 23:20, 15 November 2012 (GMT)<br /> ::::What happens if you run &lt;code&gt;file irecovery&lt;/code&gt;? Is it a Mac Intel executable? If not, that's why. Any yes, it is for Mac. You need &lt;code&gt;GNU Compiler Collection&lt;/code&gt; and &lt;code&gt;gnumake&lt;/code&gt; though. --[[User:5urd|5urd]] 17:45, 15 November 2012 (MST)<br /> :How do I use the pwnstrap for iOS 6.x? cant use pwnagetool to cook. haifisch what about instructions for your tool? --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 18:13 2 December 2012 (MST)<br /> ::You make me sad... pwnstap is just (really) uploading the custom iBSS file; You cannot simply compile my tool yourself so why not learn how to like we all did? --[[User:Haifisch|Haifisch]] 00:34, 2 December 2012 (MST)<br /> :::I can but half of the commands don't work. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 5:46, 2 December 2012 (MST)<br /> ::::Because you need to set them up and know how to use them --[[User:Haifisch|Haifisch]] 15:46, 2 December 2012 (MST)<br /> :::::http://www.hackint0sh.org/tools-128/tutorial-get-iv-keys-using-idevice-385143.htm --[[User:Markcoker|Blue Skies]] ([[User talk:Markcoker|talk]]) 11:32, 4 April 2014 (UTC)</div>

Danzatt https://www.theiphonewiki.com/w/index.php?title=Talk:AES_Keys&diff=42158 2014-09-14T10:59:00Z

<p>Danzatt: </p> <hr /> <div>==Use kloader to bootstrap patched iBSS/iBEC on A4+ devices==<br /> Has anyone tried loading patched iBSS/iBEC on A4+ device ? That way we would be able to load unsigned ramdisk (which could be used to decrypt kbag even on non-limerain devices). {{unsigned|‎Danzatt|15:58, 12 September, 2014}}<br /> :It won't work as the AES engine gets disabled when the kernel is booting up. Jumping back into iBoot won't reenable it. --[[User:Aker|Aker]] 21:56, 12 September 2014 (GMT+1)<br /> ::Does it make a &quot;call&quot; to coprocessor so that it is disabled on hardware level ? (Are there any details available on how this is done ?). --[[User:Danzatt|Danzatt]] ([[User talk:Danzatt|talk]]) 21:32, 12 September 2014 (UTC)<br /> :::The IOAESAccelerator chip gets a request to restrict the access to the GID key and disables it until the iPhone/iPad/iPod touch is rebooted. -- [[User:Aker|Aker]] 08:54, 13 September 2014 (GMT+1)<br /> ::::Yes, I know that. But I thought bootloader just hides it from the kernel. Is there any source that confirms it is disabled per-reboot ? (Also... How was it possible that XPwn's kernel patcher could patch kernel to grant access to GID key ?) --[[User:Danzatt|Danzatt]] ([[User talk:Danzatt|talk]]) 10:59, 14 September 2014 (UTC)<br /> ==Greenpois0n Method==<br /> After GP does its magic and the device boots into the patched iBSS, I cannot get the command to decrypt the KBAG to work. In iRecovery, 'go aes dec [long KBAG string]' gives no output. Commands like bgcolor, reboot, etc. work, but I cannot get any feedback from the device to give me the decrypted KBAG. Has anyone gotten this to work? --[[User:Cool name|Cool name]] 16:01, 11 November 2010 (UTC)<br /> :you need a [[payload]] or run -s flag on [[IBSS]] --[[User:Liamchat|liamchat]] 16:29, 11 November 2010 (UTC)<br /> ::I'm pretty sure the payload is already initialized by running GP, because when opening the iRecovery console with 'sudo ./irecovery -s' it spits out stuff about Greenpois0n initializing, aes_crypto_cmd being patched, etc, and it is an iBSS. My trouble is getting the device to respond to the go aes dec command, I think it may be a problem with iRecovery but not sure --[[User:Cool name|Cool name]] 17:03, 11 November 2010 (UTC)<br /> :::well what copy of [[IRecovery]] do you have i know that the one from [[User:GreySyntax]] works also try an [[IRecovery]] script like --[[User:Liamchat|liamchat]] 17:43, 11 November 2010 (UTC)<br /> go aes dec AACACFB9258D7DFBF7D46F21BD9BF27C7E67C673594B7DEE4FF8FE1F08040B1F<br /> go aes dec FF47F3DA0949016984CDED28E286C45CB14B1962B328F82589608C5A5D0A4050<br /> go aes dec 73FFC67694FC821AB9C21CB3CC9A64792D14320F917F469B4935110284990778<br /> go aes dec 3DD9554AB61398A3B6323FA71730A4243837777651DFB8AD212B81ECF194C653<br /> go aes dec 3D2B301E5A7069D52DA258C4B0A2209FA9BA4CEDB120688FC51D3BF1EDEDE5BC<br /> go aes dec E996535613828554253DC21B4875C4BB371FF21699C2D2AF8C02E1137EB1951F<br /> go aes dec 3D538743E45B5B6B6C190B2BBACA705372A3147CC9A60C6856EE2B9B1E60FD85<br /> go aes dec 5FCF5DA27AC995B0B10D76C42ADD5F0BB9268FA88A045EDCCDBC946A73A7CFDC<br /> go aes dec 68D3DE8EA8CC1707D08C983E745EA6A25E40FD532A5BD3BF7760BD540BE257DC<br /> go aes dec 1AE9223C4B8AEBD5F0A30C910212EC8171E3BFC2EF7BF802A39C9C5F45939B2C<br /> go aes dec 87CE52FFEB8E4FB685BA7FA37CBAC0004C9C0B0274FB8A7C1E06D85796063DF0<br /> go aes dec BDB129D92704104423940EC40913FABD30E676CD800E523273DA4E38065B0E13<br /> go aes dec 55D6DE657EB16C5563551C4DA26EE12197783C7100A92695D2B74802F10155C1<br /> go aes dec BA6A3959FBC43D3BCF2708640D5E7B4E5C2306C7ED8A34F7ABC3F49EE6D0BDD4<br /> go aes dec B6689C5BA40B644470C51C35257B984F97F9BE8A3E620086A5A726D7A2C1B7B1<br /> go aes dec 874AD4B93947DAA4D14DDACD3F948F2EFAA207BF6E6FDE3C9D6248E72186894B<br /> go aes dec 9C51D82560C30D976F374F5CB7CC2A7E286FF0067169EA393A8285AC74129D05<br /> /exit note: these are the [[KBAG]]'s of [[Northstar 7D11 (iPod touch 2G)]]<br /> ::::--[[User:Liamchat|liamchat]] 18:25, 11 November 2010 (UTC)<br /> :::::Thank you, GreySyntax's version of iRecovery did the trick :) --[[User:Cool name|Cool name]] 19:32, 11 November 2010 (UTC)<br /> <br /> == Project ==<br /> So I'm working on a project for the AES Engine, May I add the info somewhere in this page? [https://github.com/Absinthed-Dev/AESPayload AESPayload Syringe] --[[User:Haifisch|Haifisch]] 22:38, 13 November 2012 (MST)<br /> :No. Finish your project and ask again. If it's really useful and used by more than 1000 users, we might add it. --[[User:Http|http]] 05:22, 14 November 2012 (MST)<br /> ::Finished --[[User:Haifisch|Haifisch]] 00:03, 17 November 2012 (MST)<br /> :::Mind explaining exactly how one would use it? --[[User:5urd|5urd]] 14:39, 17 November 2012 (MST)<br /> ::::New people to the hacking community (iOS hackers) may want to help by finding the keys to such things as kernelcaches and root fs dmgs. Using this tool they can, this may be the easiest way to find it, It does most of the work for you. All one would need to do is get the KBAG key and run the aes decrypt command with the included irecovery tool (Not of my work). I suggest this as a starting point for the new guys jumping into hardware hacking. --[[User:Haifisch|Haifisch]] 16:39, 17 November 2012 (MST)<br /> <br /> == Finding AES keys. ==<br /> How can I find the AES keys? I have Haifisch's version but I cant find out to compile. Also I dont get irecovery to work. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 18:07, 14 November 2012 GMT}}<br /> :Not being rude, but if you can't compile a simple Makefile project, you need to learn a bit more before delving into things like hacking the device's hardware and software. --[[User:5urd|5urd]] 16:34, 14 November 2012 (MST)<br /> ::I made my version as easy as possible (without just handing him a compiled executable). I want him to learn at least to compile a simple project. --[[User:Haifisch|Haifisch]] 19:14, 14 November 2012 (MST)<br /> :::Did you make it for Mac? Also I cannot get the irecovery -s to work. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 23:20, 15 November 2012 (GMT)<br /> ::::What happens if you run &lt;code&gt;file irecovery&lt;/code&gt;? Is it a Mac Intel executable? If not, that's why. Any yes, it is for Mac. You need &lt;code&gt;GNU Compiler Collection&lt;/code&gt; and &lt;code&gt;gnumake&lt;/code&gt; though. --[[User:5urd|5urd]] 17:45, 15 November 2012 (MST)<br /> :How do I use the pwnstrap for iOS 6.x? cant use pwnagetool to cook. haifisch what about instructions for your tool? --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 18:13 2 December 2012 (MST)<br /> ::You make me sad... pwnstap is just (really) uploading the custom iBSS file; You cannot simply compile my tool yourself so why not learn how to like we all did? --[[User:Haifisch|Haifisch]] 00:34, 2 December 2012 (MST)<br /> :::I can but half of the commands don't work. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 5:46, 2 December 2012 (MST)<br /> ::::Because you need to set them up and know how to use them --[[User:Haifisch|Haifisch]] 15:46, 2 December 2012 (MST)<br /> :::::http://www.hackint0sh.org/tools-128/tutorial-get-iv-keys-using-idevice-385143.htm --[[User:Markcoker|Blue Skies]] ([[User talk:Markcoker|talk]]) 11:32, 4 April 2014 (UTC)</div>

Danzatt https://www.theiphonewiki.com/w/index.php?title=Talk:AES_Keys&diff=42121 2014-09-12T21:34:57Z

<p>Danzatt: </p> <hr /> <div>==Use kloader to bootstrap patched iBSS/iBEC on A4+ devices==<br /> Has anyone tried loading patched iBSS/iBEC on A4+ device ? That way we would be able to load unsigned ramdisk (which could be used to decrypt kbag even on non-limerain devices). {{unsigned|‎Danzatt|15:58, 12 September, 2014}}<br /> :It won't work as the AES engine gets disabled when the kernel is booting up. Jumping back into iBoot won't reenable it. --[[User:Aker|Aker]] 21:56, 12 September 2014 (GMT+1)<br /> ::Does it make a &quot;call&quot; to coprocessor so that it is disabled on hardware level ? (Are there any details available on how this is done ?). --[[User:Danzatt|Danzatt]] ([[User talk:Danzatt|talk]]) 21:32, 12 September 2014 (UTC)<br /> ==Greenpois0n Method==<br /> After GP does its magic and the device boots into the patched iBSS, I cannot get the command to decrypt the KBAG to work. In iRecovery, 'go aes dec [long KBAG string]' gives no output. Commands like bgcolor, reboot, etc. work, but I cannot get any feedback from the device to give me the decrypted KBAG. Has anyone gotten this to work? --[[User:Cool name|Cool name]] 16:01, 11 November 2010 (UTC)<br /> :you need a [[payload]] or run -s flag on [[IBSS]] --[[User:Liamchat|liamchat]] 16:29, 11 November 2010 (UTC)<br /> ::I'm pretty sure the payload is already initialized by running GP, because when opening the iRecovery console with 'sudo ./irecovery -s' it spits out stuff about Greenpois0n initializing, aes_crypto_cmd being patched, etc, and it is an iBSS. My trouble is getting the device to respond to the go aes dec command, I think it may be a problem with iRecovery but not sure --[[User:Cool name|Cool name]] 17:03, 11 November 2010 (UTC)<br /> :::well what copy of [[IRecovery]] do you have i know that the one from [[User:GreySyntax]] works also try an [[IRecovery]] script like --[[User:Liamchat|liamchat]] 17:43, 11 November 2010 (UTC)<br /> go aes dec AACACFB9258D7DFBF7D46F21BD9BF27C7E67C673594B7DEE4FF8FE1F08040B1F<br /> go aes dec FF47F3DA0949016984CDED28E286C45CB14B1962B328F82589608C5A5D0A4050<br /> go aes dec 73FFC67694FC821AB9C21CB3CC9A64792D14320F917F469B4935110284990778<br /> go aes dec 3DD9554AB61398A3B6323FA71730A4243837777651DFB8AD212B81ECF194C653<br /> go aes dec 3D2B301E5A7069D52DA258C4B0A2209FA9BA4CEDB120688FC51D3BF1EDEDE5BC<br /> go aes dec E996535613828554253DC21B4875C4BB371FF21699C2D2AF8C02E1137EB1951F<br /> go aes dec 3D538743E45B5B6B6C190B2BBACA705372A3147CC9A60C6856EE2B9B1E60FD85<br /> go aes dec 5FCF5DA27AC995B0B10D76C42ADD5F0BB9268FA88A045EDCCDBC946A73A7CFDC<br /> go aes dec 68D3DE8EA8CC1707D08C983E745EA6A25E40FD532A5BD3BF7760BD540BE257DC<br /> go aes dec 1AE9223C4B8AEBD5F0A30C910212EC8171E3BFC2EF7BF802A39C9C5F45939B2C<br /> go aes dec 87CE52FFEB8E4FB685BA7FA37CBAC0004C9C0B0274FB8A7C1E06D85796063DF0<br /> go aes dec BDB129D92704104423940EC40913FABD30E676CD800E523273DA4E38065B0E13<br /> go aes dec 55D6DE657EB16C5563551C4DA26EE12197783C7100A92695D2B74802F10155C1<br /> go aes dec BA6A3959FBC43D3BCF2708640D5E7B4E5C2306C7ED8A34F7ABC3F49EE6D0BDD4<br /> go aes dec B6689C5BA40B644470C51C35257B984F97F9BE8A3E620086A5A726D7A2C1B7B1<br /> go aes dec 874AD4B93947DAA4D14DDACD3F948F2EFAA207BF6E6FDE3C9D6248E72186894B<br /> go aes dec 9C51D82560C30D976F374F5CB7CC2A7E286FF0067169EA393A8285AC74129D05<br /> /exit note: these are the [[KBAG]]'s of [[Northstar 7D11 (iPod touch 2G)]]<br /> ::::--[[User:Liamchat|liamchat]] 18:25, 11 November 2010 (UTC)<br /> :::::Thank you, GreySyntax's version of iRecovery did the trick :) --[[User:Cool name|Cool name]] 19:32, 11 November 2010 (UTC)<br /> <br /> == Project ==<br /> So I'm working on a project for the AES Engine, May I add the info somewhere in this page? [https://github.com/Absinthed-Dev/AESPayload AESPayload Syringe] --[[User:Haifisch|Haifisch]] 22:38, 13 November 2012 (MST)<br /> :No. Finish your project and ask again. If it's really useful and used by more than 1000 users, we might add it. --[[User:Http|http]] 05:22, 14 November 2012 (MST)<br /> ::Finished --[[User:Haifisch|Haifisch]] 00:03, 17 November 2012 (MST)<br /> :::Mind explaining exactly how one would use it? --[[User:5urd|5urd]] 14:39, 17 November 2012 (MST)<br /> ::::New people to the hacking community (iOS hackers) may want to help by finding the keys to such things as kernelcaches and root fs dmgs. Using this tool they can, this may be the easiest way to find it, It does most of the work for you. All one would need to do is get the KBAG key and run the aes decrypt command with the included irecovery tool (Not of my work). I suggest this as a starting point for the new guys jumping into hardware hacking. --[[User:Haifisch|Haifisch]] 16:39, 17 November 2012 (MST)<br /> <br /> == Finding AES keys. ==<br /> How can I find the AES keys? I have Haifisch's version but I cant find out to compile. Also I dont get irecovery to work. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 18:07, 14 November 2012 GMT}}<br /> :Not being rude, but if you can't compile a simple Makefile project, you need to learn a bit more before delving into things like hacking the device's hardware and software. --[[User:5urd|5urd]] 16:34, 14 November 2012 (MST)<br /> ::I made my version as easy as possible (without just handing him a compiled executable). I want him to learn at least to compile a simple project. --[[User:Haifisch|Haifisch]] 19:14, 14 November 2012 (MST)<br /> :::Did you make it for Mac? Also I cannot get the irecovery -s to work. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 23:20, 15 November 2012 (GMT)<br /> ::::What happens if you run &lt;code&gt;file irecovery&lt;/code&gt;? Is it a Mac Intel executable? If not, that's why. Any yes, it is for Mac. You need &lt;code&gt;GNU Compiler Collection&lt;/code&gt; and &lt;code&gt;gnumake&lt;/code&gt; though. --[[User:5urd|5urd]] 17:45, 15 November 2012 (MST)<br /> :How do I use the pwnstrap for iOS 6.x? cant use pwnagetool to cook. haifisch what about instructions for your tool? --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 18:13 2 December 2012 (MST)<br /> ::You make me sad... pwnstap is just (really) uploading the custom iBSS file; You cannot simply compile my tool yourself so why not learn how to like we all did? --[[User:Haifisch|Haifisch]] 00:34, 2 December 2012 (MST)<br /> :::I can but half of the commands don't work. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 5:46, 2 December 2012 (MST)<br /> ::::Because you need to set them up and know how to use them --[[User:Haifisch|Haifisch]] 15:46, 2 December 2012 (MST)<br /> :::::http://www.hackint0sh.org/tools-128/tutorial-get-iv-keys-using-idevice-385143.htm --[[User:Markcoker|Blue Skies]] ([[User talk:Markcoker|talk]]) 11:32, 4 April 2014 (UTC)</div>

Danzatt https://www.theiphonewiki.com/w/index.php?title=Talk:AES_Keys&diff=42120 2014-09-12T21:33:08Z

<p>Danzatt: </p> <hr /> <div>==Use kloader to bootstrap patched iBSS/iBEC on A4+ devices==<br /> Has anyone tried loading patched iBSS/iBEC on A4+ device ? That way we would be able to load unsigned ramdisk (which could be used to decrypt kbag even on non-limerain devices). {{unsigned|‎Danzatt|15:58, 12 September, 2014}}<br /> :It won't work as the AES engine gets disabled when the kernel is booting up. Jumping back into iBoot won't reenable it. --[[User:Aker|Aker]] 21:56, 12 September 2014 (GMT+1)<br /> ::Does it make a &quot;call&quot; to coprocessor so that it is disabled on hardware level ? (Are there any details available on how it is blocked?). --[[User:Danzatt|Danzatt]] ([[User talk:Danzatt|talk]]) 21:32, 12 September 2014 (UTC)<br /> ==Greenpois0n Method==<br /> After GP does its magic and the device boots into the patched iBSS, I cannot get the command to decrypt the KBAG to work. In iRecovery, 'go aes dec [long KBAG string]' gives no output. Commands like bgcolor, reboot, etc. work, but I cannot get any feedback from the device to give me the decrypted KBAG. Has anyone gotten this to work? --[[User:Cool name|Cool name]] 16:01, 11 November 2010 (UTC)<br /> :you need a [[payload]] or run -s flag on [[IBSS]] --[[User:Liamchat|liamchat]] 16:29, 11 November 2010 (UTC)<br /> ::I'm pretty sure the payload is already initialized by running GP, because when opening the iRecovery console with 'sudo ./irecovery -s' it spits out stuff about Greenpois0n initializing, aes_crypto_cmd being patched, etc, and it is an iBSS. My trouble is getting the device to respond to the go aes dec command, I think it may be a problem with iRecovery but not sure --[[User:Cool name|Cool name]] 17:03, 11 November 2010 (UTC)<br /> :::well what copy of [[IRecovery]] do you have i know that the one from [[User:GreySyntax]] works also try an [[IRecovery]] script like --[[User:Liamchat|liamchat]] 17:43, 11 November 2010 (UTC)<br /> go aes dec AACACFB9258D7DFBF7D46F21BD9BF27C7E67C673594B7DEE4FF8FE1F08040B1F<br /> go aes dec FF47F3DA0949016984CDED28E286C45CB14B1962B328F82589608C5A5D0A4050<br /> go aes dec 73FFC67694FC821AB9C21CB3CC9A64792D14320F917F469B4935110284990778<br /> go aes dec 3DD9554AB61398A3B6323FA71730A4243837777651DFB8AD212B81ECF194C653<br /> go aes dec 3D2B301E5A7069D52DA258C4B0A2209FA9BA4CEDB120688FC51D3BF1EDEDE5BC<br /> go aes dec E996535613828554253DC21B4875C4BB371FF21699C2D2AF8C02E1137EB1951F<br /> go aes dec 3D538743E45B5B6B6C190B2BBACA705372A3147CC9A60C6856EE2B9B1E60FD85<br /> go aes dec 5FCF5DA27AC995B0B10D76C42ADD5F0BB9268FA88A045EDCCDBC946A73A7CFDC<br /> go aes dec 68D3DE8EA8CC1707D08C983E745EA6A25E40FD532A5BD3BF7760BD540BE257DC<br /> go aes dec 1AE9223C4B8AEBD5F0A30C910212EC8171E3BFC2EF7BF802A39C9C5F45939B2C<br /> go aes dec 87CE52FFEB8E4FB685BA7FA37CBAC0004C9C0B0274FB8A7C1E06D85796063DF0<br /> go aes dec BDB129D92704104423940EC40913FABD30E676CD800E523273DA4E38065B0E13<br /> go aes dec 55D6DE657EB16C5563551C4DA26EE12197783C7100A92695D2B74802F10155C1<br /> go aes dec BA6A3959FBC43D3BCF2708640D5E7B4E5C2306C7ED8A34F7ABC3F49EE6D0BDD4<br /> go aes dec B6689C5BA40B644470C51C35257B984F97F9BE8A3E620086A5A726D7A2C1B7B1<br /> go aes dec 874AD4B93947DAA4D14DDACD3F948F2EFAA207BF6E6FDE3C9D6248E72186894B<br /> go aes dec 9C51D82560C30D976F374F5CB7CC2A7E286FF0067169EA393A8285AC74129D05<br /> /exit note: these are the [[KBAG]]'s of [[Northstar 7D11 (iPod touch 2G)]]<br /> ::::--[[User:Liamchat|liamchat]] 18:25, 11 November 2010 (UTC)<br /> :::::Thank you, GreySyntax's version of iRecovery did the trick :) --[[User:Cool name|Cool name]] 19:32, 11 November 2010 (UTC)<br /> <br /> == Project ==<br /> So I'm working on a project for the AES Engine, May I add the info somewhere in this page? [https://github.com/Absinthed-Dev/AESPayload AESPayload Syringe] --[[User:Haifisch|Haifisch]] 22:38, 13 November 2012 (MST)<br /> :No. Finish your project and ask again. If it's really useful and used by more than 1000 users, we might add it. --[[User:Http|http]] 05:22, 14 November 2012 (MST)<br /> ::Finished --[[User:Haifisch|Haifisch]] 00:03, 17 November 2012 (MST)<br /> :::Mind explaining exactly how one would use it? --[[User:5urd|5urd]] 14:39, 17 November 2012 (MST)<br /> ::::New people to the hacking community (iOS hackers) may want to help by finding the keys to such things as kernelcaches and root fs dmgs. Using this tool they can, this may be the easiest way to find it, It does most of the work for you. All one would need to do is get the KBAG key and run the aes decrypt command with the included irecovery tool (Not of my work). I suggest this as a starting point for the new guys jumping into hardware hacking. --[[User:Haifisch|Haifisch]] 16:39, 17 November 2012 (MST)<br /> <br /> == Finding AES keys. ==<br /> How can I find the AES keys? I have Haifisch's version but I cant find out to compile. Also I dont get irecovery to work. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 18:07, 14 November 2012 GMT}}<br /> :Not being rude, but if you can't compile a simple Makefile project, you need to learn a bit more before delving into things like hacking the device's hardware and software. --[[User:5urd|5urd]] 16:34, 14 November 2012 (MST)<br /> ::I made my version as easy as possible (without just handing him a compiled executable). I want him to learn at least to compile a simple project. --[[User:Haifisch|Haifisch]] 19:14, 14 November 2012 (MST)<br /> :::Did you make it for Mac? Also I cannot get the irecovery -s to work. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 23:20, 15 November 2012 (GMT)<br /> ::::What happens if you run &lt;code&gt;file irecovery&lt;/code&gt;? Is it a Mac Intel executable? If not, that's why. Any yes, it is for Mac. You need &lt;code&gt;GNU Compiler Collection&lt;/code&gt; and &lt;code&gt;gnumake&lt;/code&gt; though. --[[User:5urd|5urd]] 17:45, 15 November 2012 (MST)<br /> :How do I use the pwnstrap for iOS 6.x? cant use pwnagetool to cook. haifisch what about instructions for your tool? --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 18:13 2 December 2012 (MST)<br /> ::You make me sad... pwnstap is just (really) uploading the custom iBSS file; You cannot simply compile my tool yourself so why not learn how to like we all did? --[[User:Haifisch|Haifisch]] 00:34, 2 December 2012 (MST)<br /> :::I can but half of the commands don't work. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 5:46, 2 December 2012 (MST)<br /> ::::Because you need to set them up and know how to use them --[[User:Haifisch|Haifisch]] 15:46, 2 December 2012 (MST)<br /> :::::http://www.hackint0sh.org/tools-128/tutorial-get-iv-keys-using-idevice-385143.htm --[[User:Markcoker|Blue Skies]] ([[User talk:Markcoker|talk]]) 11:32, 4 April 2014 (UTC)</div>

Danzatt https://www.theiphonewiki.com/w/index.php?title=Talk:AES_Keys&diff=42119 2014-09-12T21:32:24Z

<p>Danzatt: </p> <hr /> <div>==Use kloader to bootstrap patched iBSS/iBEC on A4+ devices==<br /> Has anyone tried loading patched iBSS/iBEC on A4+ device ? That way we would be able to load unsigned ramdisk (which could be used to decrypt kbag even on non-limerain devices). {{unsigned|‎Danzatt|15:58, 12 September, 2014}}<br /> :It won't work as the AES engine gets disabled when the kernel is booting up. Jumping back into iBoot won't reenable it. --[[User:Aker|Aker]] 21:56, 12 September 2014 (GMT+1)<br /> :Does it make a &quot;call&quot; to coprocessor so that it is disabled on hardware level ? (Are there any details available on how it is blocked?). --[[User:Danzatt|Danzatt]] ([[User talk:Danzatt|talk]]) 21:32, 12 September 2014 (UTC)<br /> ==Greenpois0n Method==<br /> After GP does its magic and the device boots into the patched iBSS, I cannot get the command to decrypt the KBAG to work. In iRecovery, 'go aes dec [long KBAG string]' gives no output. Commands like bgcolor, reboot, etc. work, but I cannot get any feedback from the device to give me the decrypted KBAG. Has anyone gotten this to work? --[[User:Cool name|Cool name]] 16:01, 11 November 2010 (UTC)<br /> :you need a [[payload]] or run -s flag on [[IBSS]] --[[User:Liamchat|liamchat]] 16:29, 11 November 2010 (UTC)<br /> ::I'm pretty sure the payload is already initialized by running GP, because when opening the iRecovery console with 'sudo ./irecovery -s' it spits out stuff about Greenpois0n initializing, aes_crypto_cmd being patched, etc, and it is an iBSS. My trouble is getting the device to respond to the go aes dec command, I think it may be a problem with iRecovery but not sure --[[User:Cool name|Cool name]] 17:03, 11 November 2010 (UTC)<br /> :::well what copy of [[IRecovery]] do you have i know that the one from [[User:GreySyntax]] works also try an [[IRecovery]] script like --[[User:Liamchat|liamchat]] 17:43, 11 November 2010 (UTC)<br /> go aes dec AACACFB9258D7DFBF7D46F21BD9BF27C7E67C673594B7DEE4FF8FE1F08040B1F<br /> go aes dec FF47F3DA0949016984CDED28E286C45CB14B1962B328F82589608C5A5D0A4050<br /> go aes dec 73FFC67694FC821AB9C21CB3CC9A64792D14320F917F469B4935110284990778<br /> go aes dec 3DD9554AB61398A3B6323FA71730A4243837777651DFB8AD212B81ECF194C653<br /> go aes dec 3D2B301E5A7069D52DA258C4B0A2209FA9BA4CEDB120688FC51D3BF1EDEDE5BC<br /> go aes dec E996535613828554253DC21B4875C4BB371FF21699C2D2AF8C02E1137EB1951F<br /> go aes dec 3D538743E45B5B6B6C190B2BBACA705372A3147CC9A60C6856EE2B9B1E60FD85<br /> go aes dec 5FCF5DA27AC995B0B10D76C42ADD5F0BB9268FA88A045EDCCDBC946A73A7CFDC<br /> go aes dec 68D3DE8EA8CC1707D08C983E745EA6A25E40FD532A5BD3BF7760BD540BE257DC<br /> go aes dec 1AE9223C4B8AEBD5F0A30C910212EC8171E3BFC2EF7BF802A39C9C5F45939B2C<br /> go aes dec 87CE52FFEB8E4FB685BA7FA37CBAC0004C9C0B0274FB8A7C1E06D85796063DF0<br /> go aes dec BDB129D92704104423940EC40913FABD30E676CD800E523273DA4E38065B0E13<br /> go aes dec 55D6DE657EB16C5563551C4DA26EE12197783C7100A92695D2B74802F10155C1<br /> go aes dec BA6A3959FBC43D3BCF2708640D5E7B4E5C2306C7ED8A34F7ABC3F49EE6D0BDD4<br /> go aes dec B6689C5BA40B644470C51C35257B984F97F9BE8A3E620086A5A726D7A2C1B7B1<br /> go aes dec 874AD4B93947DAA4D14DDACD3F948F2EFAA207BF6E6FDE3C9D6248E72186894B<br /> go aes dec 9C51D82560C30D976F374F5CB7CC2A7E286FF0067169EA393A8285AC74129D05<br /> /exit note: these are the [[KBAG]]'s of [[Northstar 7D11 (iPod touch 2G)]]<br /> ::::--[[User:Liamchat|liamchat]] 18:25, 11 November 2010 (UTC)<br /> :::::Thank you, GreySyntax's version of iRecovery did the trick :) --[[User:Cool name|Cool name]] 19:32, 11 November 2010 (UTC)<br /> <br /> == Project ==<br /> So I'm working on a project for the AES Engine, May I add the info somewhere in this page? [https://github.com/Absinthed-Dev/AESPayload AESPayload Syringe] --[[User:Haifisch|Haifisch]] 22:38, 13 November 2012 (MST)<br /> :No. Finish your project and ask again. If it's really useful and used by more than 1000 users, we might add it. --[[User:Http|http]] 05:22, 14 November 2012 (MST)<br /> ::Finished --[[User:Haifisch|Haifisch]] 00:03, 17 November 2012 (MST)<br /> :::Mind explaining exactly how one would use it? --[[User:5urd|5urd]] 14:39, 17 November 2012 (MST)<br /> ::::New people to the hacking community (iOS hackers) may want to help by finding the keys to such things as kernelcaches and root fs dmgs. Using this tool they can, this may be the easiest way to find it, It does most of the work for you. All one would need to do is get the KBAG key and run the aes decrypt command with the included irecovery tool (Not of my work). I suggest this as a starting point for the new guys jumping into hardware hacking. --[[User:Haifisch|Haifisch]] 16:39, 17 November 2012 (MST)<br /> <br /> == Finding AES keys. ==<br /> How can I find the AES keys? I have Haifisch's version but I cant find out to compile. Also I dont get irecovery to work. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 18:07, 14 November 2012 GMT}}<br /> :Not being rude, but if you can't compile a simple Makefile project, you need to learn a bit more before delving into things like hacking the device's hardware and software. --[[User:5urd|5urd]] 16:34, 14 November 2012 (MST)<br /> ::I made my version as easy as possible (without just handing him a compiled executable). I want him to learn at least to compile a simple project. --[[User:Haifisch|Haifisch]] 19:14, 14 November 2012 (MST)<br /> :::Did you make it for Mac? Also I cannot get the irecovery -s to work. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 23:20, 15 November 2012 (GMT)<br /> ::::What happens if you run &lt;code&gt;file irecovery&lt;/code&gt;? Is it a Mac Intel executable? If not, that's why. Any yes, it is for Mac. You need &lt;code&gt;GNU Compiler Collection&lt;/code&gt; and &lt;code&gt;gnumake&lt;/code&gt; though. --[[User:5urd|5urd]] 17:45, 15 November 2012 (MST)<br /> :How do I use the pwnstrap for iOS 6.x? cant use pwnagetool to cook. haifisch what about instructions for your tool? --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 18:13 2 December 2012 (MST)<br /> ::You make me sad... pwnstap is just (really) uploading the custom iBSS file; You cannot simply compile my tool yourself so why not learn how to like we all did? --[[User:Haifisch|Haifisch]] 00:34, 2 December 2012 (MST)<br /> :::I can but half of the commands don't work. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 5:46, 2 December 2012 (MST)<br /> ::::Because you need to set them up and know how to use them --[[User:Haifisch|Haifisch]] 15:46, 2 December 2012 (MST)<br /> :::::http://www.hackint0sh.org/tools-128/tutorial-get-iv-keys-using-idevice-385143.htm --[[User:Markcoker|Blue Skies]] ([[User talk:Markcoker|talk]]) 11:32, 4 April 2014 (UTC)</div>

Danzatt https://www.theiphonewiki.com/w/index.php?title=Talk:AES_Keys&diff=42107 2014-09-12T14:58:19Z

<p>Danzatt: </p> <hr /> <div>==Use kloader to bootstrap patched iBSS/iBEC on A4+ devices==<br /> Has anyone tried loading patched iBSS/iBEC on A4+ device ? That way we would be able to load unsigned ramdisk (which could be used to decrypt kbag even on non-limerain devices).<br /> <br /> ==Greenpois0n Method==<br /> After GP does its magic and the device boots into the patched iBSS, I cannot get the command to decrypt the KBAG to work. In iRecovery, 'go aes dec [long KBAG string]' gives no output. Commands like bgcolor, reboot, etc. work, but I cannot get any feedback from the device to give me the decrypted KBAG. Has anyone gotten this to work? --[[User:Cool name|Cool name]] 16:01, 11 November 2010 (UTC)<br /> :you need a [[payload]] or run -s flag on [[IBSS]] --[[User:Liamchat|liamchat]] 16:29, 11 November 2010 (UTC)<br /> ::I'm pretty sure the payload is already initialized by running GP, because when opening the iRecovery console with 'sudo ./irecovery -s' it spits out stuff about Greenpois0n initializing, aes_crypto_cmd being patched, etc, and it is an iBSS. My trouble is getting the device to respond to the go aes dec command, I think it may be a problem with iRecovery but not sure --[[User:Cool name|Cool name]] 17:03, 11 November 2010 (UTC)<br /> :::well what copy of [[IRecovery]] do you have i know that the one from [[User:GreySyntax]] works also try an [[IRecovery]] script like --[[User:Liamchat|liamchat]] 17:43, 11 November 2010 (UTC)<br /> go aes dec AACACFB9258D7DFBF7D46F21BD9BF27C7E67C673594B7DEE4FF8FE1F08040B1F<br /> go aes dec FF47F3DA0949016984CDED28E286C45CB14B1962B328F82589608C5A5D0A4050<br /> go aes dec 73FFC67694FC821AB9C21CB3CC9A64792D14320F917F469B4935110284990778<br /> go aes dec 3DD9554AB61398A3B6323FA71730A4243837777651DFB8AD212B81ECF194C653<br /> go aes dec 3D2B301E5A7069D52DA258C4B0A2209FA9BA4CEDB120688FC51D3BF1EDEDE5BC<br /> go aes dec E996535613828554253DC21B4875C4BB371FF21699C2D2AF8C02E1137EB1951F<br /> go aes dec 3D538743E45B5B6B6C190B2BBACA705372A3147CC9A60C6856EE2B9B1E60FD85<br /> go aes dec 5FCF5DA27AC995B0B10D76C42ADD5F0BB9268FA88A045EDCCDBC946A73A7CFDC<br /> go aes dec 68D3DE8EA8CC1707D08C983E745EA6A25E40FD532A5BD3BF7760BD540BE257DC<br /> go aes dec 1AE9223C4B8AEBD5F0A30C910212EC8171E3BFC2EF7BF802A39C9C5F45939B2C<br /> go aes dec 87CE52FFEB8E4FB685BA7FA37CBAC0004C9C0B0274FB8A7C1E06D85796063DF0<br /> go aes dec BDB129D92704104423940EC40913FABD30E676CD800E523273DA4E38065B0E13<br /> go aes dec 55D6DE657EB16C5563551C4DA26EE12197783C7100A92695D2B74802F10155C1<br /> go aes dec BA6A3959FBC43D3BCF2708640D5E7B4E5C2306C7ED8A34F7ABC3F49EE6D0BDD4<br /> go aes dec B6689C5BA40B644470C51C35257B984F97F9BE8A3E620086A5A726D7A2C1B7B1<br /> go aes dec 874AD4B93947DAA4D14DDACD3F948F2EFAA207BF6E6FDE3C9D6248E72186894B<br /> go aes dec 9C51D82560C30D976F374F5CB7CC2A7E286FF0067169EA393A8285AC74129D05<br /> /exit note: these are the [[KBAG]]'s of [[Northstar 7D11 (iPod touch 2G)]]<br /> ::::--[[User:Liamchat|liamchat]] 18:25, 11 November 2010 (UTC)<br /> :::::Thank you, GreySyntax's version of iRecovery did the trick :) --[[User:Cool name|Cool name]] 19:32, 11 November 2010 (UTC)<br /> <br /> == Project ==<br /> So I'm working on a project for the AES Engine, May I add the info somewhere in this page? [https://github.com/Absinthed-Dev/AESPayload AESPayload Syringe] --[[User:Haifisch|Haifisch]] 22:38, 13 November 2012 (MST)<br /> :No. Finish your project and ask again. If it's really useful and used by more than 1000 users, we might add it. --[[User:Http|http]] 05:22, 14 November 2012 (MST)<br /> ::Finished --[[User:Haifisch|Haifisch]] 00:03, 17 November 2012 (MST)<br /> :::Mind explaining exactly how one would use it? --[[User:5urd|5urd]] 14:39, 17 November 2012 (MST)<br /> ::::New people to the hacking community (iOS hackers) may want to help by finding the keys to such things as kernelcaches and root fs dmgs. Using this tool they can, this may be the easiest way to find it, It does most of the work for you. All one would need to do is get the KBAG key and run the aes decrypt command with the included irecovery tool (Not of my work). I suggest this as a starting point for the new guys jumping into hardware hacking. --[[User:Haifisch|Haifisch]] 16:39, 17 November 2012 (MST)<br /> <br /> == Finding AES keys. ==<br /> How can I find the AES keys? I have Haifisch's version but I cant find out to compile. Also I dont get irecovery to work. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 18:07, 14 November 2012 GMT}}<br /> :Not being rude, but if you can't compile a simple Makefile project, you need to learn a bit more before delving into things like hacking the device's hardware and software. --[[User:5urd|5urd]] 16:34, 14 November 2012 (MST)<br /> ::I made my version as easy as possible (without just handing him a compiled executable). I want him to learn at least to compile a simple project. --[[User:Haifisch|Haifisch]] 19:14, 14 November 2012 (MST)<br /> :::Did you make it for Mac? Also I cannot get the irecovery -s to work. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 23:20, 15 November 2012 (GMT)<br /> ::::What happens if you run &lt;code&gt;file irecovery&lt;/code&gt;? Is it a Mac Intel executable? If not, that's why. Any yes, it is for Mac. You need &lt;code&gt;GNU Compiler Collection&lt;/code&gt; and &lt;code&gt;gnumake&lt;/code&gt; though. --[[User:5urd|5urd]] 17:45, 15 November 2012 (MST)<br /> :How do I use the pwnstrap for iOS 6.x? cant use pwnagetool to cook. haifisch what about instructions for your tool? --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 18:13 2 December 2012 (MST)<br /> ::You make me sad... pwnstap is just (really) uploading the custom iBSS file; You cannot simply compile my tool yourself so why not learn how to like we all did? --[[User:Haifisch|Haifisch]] 00:34, 2 December 2012 (MST)<br /> :::I can but half of the commands don't work. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 5:46, 2 December 2012 (MST)<br /> ::::Because you need to set them up and know how to use them --[[User:Haifisch|Haifisch]] 15:46, 2 December 2012 (MST)<br /> :::::http://www.hackint0sh.org/tools-128/tutorial-get-iv-keys-using-idevice-385143.htm --[[User:Markcoker|Blue Skies]] ([[User talk:Markcoker|talk]]) 11:32, 4 April 2014 (UTC)</div>

Danzatt