The iPhone Wiki - User contributions [en]

Talk:Bootrom Dumper Utility

2016-07-11T14:54:34Z

Markcoker: Add precompiled option

If anyone gets it working for [[n72ap|iPod touch 2G]], let me know. I am trying to work on it, but not much spare time --[[User:JacobVengeance|JacobVengeance (JakeAnthraX)]] 07:27, 23 December 2010 (UTC)
:[https://github.com/liamchat/Bootrom-Dumper/tree/master/stake4uce my fork] should work --[[User:Liamchat|liamchat]] 16:27, 24 December 2010 (UTC)
:You can also use the current [[n72ap|iPod touch 2G]] [[OpeniBoot]] [https://github.com/kleemajo/openiBoot link]. The bootrom is at 0x20000000 on the 2g touch --[[User:Kleemajo|Kleemajo]] 01:02, 26 December 2010 (UTC)
::I ended up making my own very crappy [[steaks4uce]] version to dump it. I didn't realize you made a version liam, nice job. Also where did you guys get your ARM toolchain? The one I use keeps breaking and giving me errors lately.--[[User:JacobVengeance|JacobVengeance (JakeAnthraX)]] 03:38, 29 December 2010 (UTC)
:::i use ''sudo port install arm-elf-binutils and sudo port instal arm-elf-gcc'' --[[User:Liamchat|liamchat]] 10:56, 29 December 2010 (UTC)
::::Using that I just get errors when compiling everything. I had it working on my last setup when I wrote my crappy syeaks4uce method, but now it isn't working. I will figure it out sooner or later. Thanks anyways. --[[User:JacobVengeance|JacobVengeance (JakeAnthraX)]] 22:45, 29 December 2010 (UTC)
::hey liam when I try running this on linux i get 84 00 00 00 05 00 00 00 80 00 00 00 80 62 02 22 FF FF FF FF 00 00 00 00 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 15 00 00 00 02 00 00 00 01 38 02 22 90 D7 02 22 and then the rest of it gets filled with nulls until the next 0x800 bytes start :( [[User:Revolution|Revolution]] 19:02, 19 February 2011 (UTC)
:::use toolchain.txt from openiboot, it works perfect --[[User:Posixninja|posixninja]] 23:41, 29 December 2010 (UTC)
::::using OpeniBoot-toolchain results in the following error - Failed to build GCC part 1 (stage: gcc_build), but precompiled works fine. (See below)
:::::cd /tmp
:::::curl -O -C - http://www.mikrocontroller.net/download/arm-toolchain-macosx-intel-2.tar.bz2
:::::tar xjvf arm-toolchain-macosx-2.tar.bz2
:::::sudo mv arm /usr/local/
:::::echo 'export PATH=/usr/local/arm/bin:$PATH' >> ~/.profile
:::::--[[User:Markcoker|Blue Skies]] ([[User talk:Markcoker|talk]]) 14:54, 11 July 2016 (UTC)
:::run:
::::''<code>sudo apt-get install libusb-1.0-0 libusb-1.0-0-dev libreadline6-dev readline-common libreadline6 libreadline-dev texinfo cmake git-core build-essential texinfo libreadline-dev libssl-dev libusb-1.0-0-dev libpng12-dev libusb-dev autoconf automake libnewlib-dev</code>'' [[Image:Return.png|15px]] Return
::::''<code>sudo build-toolchain.sh</code>'' [[Image:Return.png|15px]] Return
:::for linux
:::--[[User:Liamchat|liamchat]] 01:35, 20 February 2011 (UTC)
::::um liam I did that... on line 145 you need to make that specified for macosx only, well at least that's what the pod2g's version did... try building it on linux. [[User:Revolution|Revolution]] 16:51, 20 February 2011 (UTC)
::::i fixed the error there does not need to be any specific platform support for [[usb control msg(0xA1, 1) Exploit|stake]] or [[pwnage2]] i think there is better way using [http://www.beyondlogic.org/usbnutshell/usb5.shtml|USB Descriptors] --[[User:Liamchat|liamchat]] 00:02, 21 February 2011 (UTC)
::::: I just tried your new version. It still doesn't work. i managed to dump the bootrom with openiboot but yeah. here is the dump your ipod produces. it contains no copy writed code so i'll paste it here. [http://www.mediafire.com/?um4gz4ga00v067a] [[User:Revolution|Revolution]] 21:11, 24 February 2011 (UTC)
:::::: None of his things will work, I can promise you that. He doensn't know what he is doing. --[[User:JacobVengeance|JacobVengeance (JakeAnthraX)]] 00:22, 25 February 2011 (UTC)
:::::::i have edited it again however i cant the usb wait for image call offset i origany thought it was the [https://github.com/Chronic-Dev/syringe/blob/master/syringe/exploits/steaks4uce/steaks4uce.S#L30 usb wait for image offset] from syringe. --[[User:Liamchat|liamchat]] 20:41, 7 March 2011 (UTC)
:::::::: I am getting an arm-elf-as: No such file or directory error on OSX Lion. Do I need to get the full toolchain compiled or can I get this working with Xcode (for iOS) somehow with less hassle ?--[[User:M2m|M2m]] 04:22, 3 January 2012 (MST)
::::::::I believe you will need the arm toolkit. --[[User:Markcoker|Blue Skies]] ([[User talk:Markcoker|talk]]) 14:27, 11 July 2016 (UTC)
== VMware + Windows ==
anyone tried this on vmware + windows? can't make it work. tried on [[n90ap|iPhone 4]] & [[n18ap|iPod touch 3G]] -- [[User:Paul0|paulzero]] 10:38, 13 February 2011 (UTC)
:it's the [[limera1n]] exploit. it does not work throughout a vm --[[User:Liamchat|liamchat]] 14:45, 13 February 2011 (UTC)

== A5 devices ==
Can we use this tool to dump A5 devices? --[[User:XiiiX|XiiiX]] 12:28, 2 January 2012 (MST)
:Not until there is a jailbreak for A5 devices.--[[User:M2m|M2m]] 12:51, 2 January 2012 (MST)
:No. Limera1n doesn't work on A5 devices. --[[User:Http|http]] 13:04, 2 January 2012 (MST)
::It's kind of non-sense this tool so. To dump already hacked bootroms? --[[User:XiiiX|XiiiX]] 14:21, 2 January 2012 (MST)
:::No. Not really. You may find an exploit outside the bootrom which leads to a jailbreak which you can use to dump the bootrom which can help you to find exploits in the bootrom for later jailbreaks. Jailbreaks based on bootrom exploits can only be fixed with new hardware.--[[User:M2m|M2m]] 15:28, 2 January 2012 (MST)
:::There is no such thing as an "hacked BootROM". We cannot change the contents of the BootROM. Note "ROM" - Read Only Memory. -SquiffyPwn 17:10, 2 January 2012 (CST)
::::That's a better explanation. So we don't need a bootrom jailbreak to use this, just a user-land could work? Why is the necessity of a jailbreak to dump te bootrom? We need the offsets? --[[User:XiiiX|XiiiX]] 16:09, 2 January 2012 (MST)
Do you know what is dump? dump is a copy, to use this tool you MUST have a BootROM Exploit, look the source code, it send the exploit to allow acess to the read-only BootROM memory. Userland exploit here? what offsets?~zmaster

== Compatibility with older devices ==
I looked as payload.s, apparently, everything is in place for older devices (e.g., 0x8b7 for basically every old device). I can't check the actual BDU application, but I'd think it was updated with code needed for older devices as well. Can anyone confirm this? --[[User:Rdqronos|rdqronos]] 14:33, 3 January 2012 (MST)
:Can't get it working with an iPhone 3G with the following values:
EXPLOIT_LR 0x22000000 LOADADDR_SIZE 0x24000 RET_ADDR 0x8b7
:Output looks OK:
sudo ./bdu
______ Bootrom Dumper Utility (BDU) 1.0 ______

(c) pod2g october 2010

[.] Now executing arbitrary code using geohot's limera1n...
sent data to copy: 800
padded to 0x84023000
sent shellcode: 800 has real length 48
never freed: 800
sent exploit to heap overflow: FFFFFFF9
[.] Dump payload started.
[.] Now dumping bootrom to file bootrom.bin...
:But I get a zero sized (empty) bootrom.bin. --[[User:M2m|M2m]] 02:17, 4 January 2012 (MST)
::So it can read the BootROM, but not dump it. Okay. --[[User:Rdqronos|rdqronos]] 13:04, 4 January 2012 (MST)
:::Not sure if it can be read correctly or not. --[[User:M2m|M2m]] 17:16, 4 January 2012 (MST)

== Working on OSX? ==

Did anybody get this working on OSX? I could compile the payload.bin and tried with both the included binary and also with the recompiled one on a MacMini OSX 10.6.8 with an iPhone 4 (with iOS 5.0.1), libusb 1.0.8 is installed. I also tried with a 3GS and the forked code (just uses the different offsets). In all cases I always get "device stalled" and the bdu terminates. I know it worked on Linux for others, but anybody had success on OSX yet? I'm not sure where to start debugging, as I'm not a Mac user. -- [[User:Http|http]] 16:36, 11 January 2012 (MST)
: I compiled it under OSX Lion and can also run it but I only get a zero sized dump. May or may not be a problem of the program & Lion or that I only have iPhone2G & 3G to test.--[[User:M2m|M2m]] 04:15, 12 January 2012 (MST)

== Dumping 3GS bootrom from OSX 10.7.2 ==

sudo ./bdu
______ Bootrom Dumper Utility (BDU) 1.0 ______

(c) pod2g october 2010

[.] Now executing arbitrary code using geohot's limera1n...
sent data to copy: 800
padded to 0x84023000
sent shellcode: 800 has real length 48
never freed: 800
sent exploit to heap overflow: FFFFFFF9
[.] Dump payload started.
[.] Now dumping bootrom to file bootrom.bin...
Segmentation fault: 11

Any ideas? I've changed all the offsets to the ones in the wiki and yet still no success.
:Try the unchanged version on a compatible device first. Also try the included precompiled executable. If it still doesn't work, try on Linux first. Post an update on how that went. -- [[User:Http|http]] 05:06, 20 January 2012 (MST)

Talk:Bootrom Dumper Utility

2016-07-11T14:27:31Z

Markcoker:

If anyone gets it working for [[n72ap|iPod touch 2G]], let me know. I am trying to work on it, but not much spare time --[[User:JacobVengeance|JacobVengeance (JakeAnthraX)]] 07:27, 23 December 2010 (UTC)
:[https://github.com/liamchat/Bootrom-Dumper/tree/master/stake4uce my fork] should work --[[User:Liamchat|liamchat]] 16:27, 24 December 2010 (UTC)
:You can also use the current [[n72ap|iPod touch 2G]] [[OpeniBoot]] [https://github.com/kleemajo/openiBoot link]. The bootrom is at 0x20000000 on the 2g touch --[[User:Kleemajo|Kleemajo]] 01:02, 26 December 2010 (UTC)
::I ended up making my own very crappy [[steaks4uce]] version to dump it. I didn't realize you made a version liam, nice job. Also where did you guys get your ARM toolchain? The one I use keeps breaking and giving me errors lately.--[[User:JacobVengeance|JacobVengeance (JakeAnthraX)]] 03:38, 29 December 2010 (UTC)
:::i use ''sudo port install arm-elf-binutils and sudo port instal arm-elf-gcc'' --[[User:Liamchat|liamchat]] 10:56, 29 December 2010 (UTC)
::::Using that I just get errors when compiling everything. I had it working on my last setup when I wrote my crappy syeaks4uce method, but now it isn't working. I will figure it out sooner or later. Thanks anyways. --[[User:JacobVengeance|JacobVengeance (JakeAnthraX)]] 22:45, 29 December 2010 (UTC)
::hey liam when I try running this on linux i get 84 00 00 00 05 00 00 00 80 00 00 00 80 62 02 22 FF FF FF FF 00 00 00 00 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 15 00 00 00 02 00 00 00 01 38 02 22 90 D7 02 22 and then the rest of it gets filled with nulls until the next 0x800 bytes start :( [[User:Revolution|Revolution]] 19:02, 19 February 2011 (UTC)
:::use toolchain.txt from openiboot, it works perfect --[[User:Posixninja|posixninja]] 23:41, 29 December 2010 (UTC)
::::using OpeniBoot-toolchain results in the following error - Failed to build GCC part 1 (stage: gcc_build).
::::../../gcc-4.1.1/gcc/toplev.c:524:1: error: redefinition of a 'extern inline'
::::function 'floor_log2' is not supported in C99 mode
::::floor_log2 (unsigned HOST_WIDE_INT x)
::::../../gcc-4.1.1/gcc/toplev.c:559:1: error: redefinition of a 'extern inline'
::::function 'exact_log2' is not supported in C99 mode
::::exact_log2 (unsigned HOST_WIDE_INT x)
:::run:
::::''<code>sudo apt-get install libusb-1.0-0 libusb-1.0-0-dev libreadline6-dev readline-common libreadline6 libreadline-dev texinfo cmake git-core build-essential texinfo libreadline-dev libssl-dev libusb-1.0-0-dev libpng12-dev libusb-dev autoconf automake libnewlib-dev</code>'' [[Image:Return.png|15px]] Return
::::''<code>sudo build-toolchain.sh</code>'' [[Image:Return.png|15px]] Return
:::for linux
:::--[[User:Liamchat|liamchat]] 01:35, 20 February 2011 (UTC)
::::um liam I did that... on line 145 you need to make that specified for macosx only, well at least that's what the pod2g's version did... try building it on linux. [[User:Revolution|Revolution]] 16:51, 20 February 2011 (UTC)
::::i fixed the error there does not need to be any specific platform support for [[usb control msg(0xA1, 1) Exploit|stake]] or [[pwnage2]] i think there is better way using [http://www.beyondlogic.org/usbnutshell/usb5.shtml|USB Descriptors] --[[User:Liamchat|liamchat]] 00:02, 21 February 2011 (UTC)
::::: I just tried your new version. It still doesn't work. i managed to dump the bootrom with openiboot but yeah. here is the dump your ipod produces. it contains no copy writed code so i'll paste it here. [http://www.mediafire.com/?um4gz4ga00v067a] [[User:Revolution|Revolution]] 21:11, 24 February 2011 (UTC)
:::::: None of his things will work, I can promise you that. He doensn't know what he is doing. --[[User:JacobVengeance|JacobVengeance (JakeAnthraX)]] 00:22, 25 February 2011 (UTC)
:::::::i have edited it again however i cant the usb wait for image call offset i origany thought it was the [https://github.com/Chronic-Dev/syringe/blob/master/syringe/exploits/steaks4uce/steaks4uce.S#L30 usb wait for image offset] from syringe. --[[User:Liamchat|liamchat]] 20:41, 7 March 2011 (UTC)
:::::::: I am getting an arm-elf-as: No such file or directory error on OSX Lion. Do I need to get the full toolchain compiled or can I get this working with Xcode (for iOS) somehow with less hassle ?--[[User:M2m|M2m]] 04:22, 3 January 2012 (MST)
::::::::I believe you will need the arm toolkit. --[[User:Markcoker|Blue Skies]] ([[User talk:Markcoker|talk]]) 14:27, 11 July 2016 (UTC)
== VMware + Windows ==
anyone tried this on vmware + windows? can't make it work. tried on [[n90ap|iPhone 4]] & [[n18ap|iPod touch 3G]] -- [[User:Paul0|paulzero]] 10:38, 13 February 2011 (UTC)
:it's the [[limera1n]] exploit. it does not work throughout a vm --[[User:Liamchat|liamchat]] 14:45, 13 February 2011 (UTC)

== A5 devices ==
Can we use this tool to dump A5 devices? --[[User:XiiiX|XiiiX]] 12:28, 2 January 2012 (MST)
:Not until there is a jailbreak for A5 devices.--[[User:M2m|M2m]] 12:51, 2 January 2012 (MST)
:No. Limera1n doesn't work on A5 devices. --[[User:Http|http]] 13:04, 2 January 2012 (MST)
::It's kind of non-sense this tool so. To dump already hacked bootroms? --[[User:XiiiX|XiiiX]] 14:21, 2 January 2012 (MST)
:::No. Not really. You may find an exploit outside the bootrom which leads to a jailbreak which you can use to dump the bootrom which can help you to find exploits in the bootrom for later jailbreaks. Jailbreaks based on bootrom exploits can only be fixed with new hardware.--[[User:M2m|M2m]] 15:28, 2 January 2012 (MST)
:::There is no such thing as an "hacked BootROM". We cannot change the contents of the BootROM. Note "ROM" - Read Only Memory. -SquiffyPwn 17:10, 2 January 2012 (CST)
::::That's a better explanation. So we don't need a bootrom jailbreak to use this, just a user-land could work? Why is the necessity of a jailbreak to dump te bootrom? We need the offsets? --[[User:XiiiX|XiiiX]] 16:09, 2 January 2012 (MST)
Do you know what is dump? dump is a copy, to use this tool you MUST have a BootROM Exploit, look the source code, it send the exploit to allow acess to the read-only BootROM memory. Userland exploit here? what offsets?~zmaster

== Compatibility with older devices ==
I looked as payload.s, apparently, everything is in place for older devices (e.g., 0x8b7 for basically every old device). I can't check the actual BDU application, but I'd think it was updated with code needed for older devices as well. Can anyone confirm this? --[[User:Rdqronos|rdqronos]] 14:33, 3 January 2012 (MST)
:Can't get it working with an iPhone 3G with the following values:
EXPLOIT_LR 0x22000000 LOADADDR_SIZE 0x24000 RET_ADDR 0x8b7
:Output looks OK:
sudo ./bdu
______ Bootrom Dumper Utility (BDU) 1.0 ______

(c) pod2g october 2010

[.] Now executing arbitrary code using geohot's limera1n...
sent data to copy: 800
padded to 0x84023000
sent shellcode: 800 has real length 48
never freed: 800
sent exploit to heap overflow: FFFFFFF9
[.] Dump payload started.
[.] Now dumping bootrom to file bootrom.bin...
:But I get a zero sized (empty) bootrom.bin. --[[User:M2m|M2m]] 02:17, 4 January 2012 (MST)
::So it can read the BootROM, but not dump it. Okay. --[[User:Rdqronos|rdqronos]] 13:04, 4 January 2012 (MST)
:::Not sure if it can be read correctly or not. --[[User:M2m|M2m]] 17:16, 4 January 2012 (MST)

== Working on OSX? ==

Did anybody get this working on OSX? I could compile the payload.bin and tried with both the included binary and also with the recompiled one on a MacMini OSX 10.6.8 with an iPhone 4 (with iOS 5.0.1), libusb 1.0.8 is installed. I also tried with a 3GS and the forked code (just uses the different offsets). In all cases I always get "device stalled" and the bdu terminates. I know it worked on Linux for others, but anybody had success on OSX yet? I'm not sure where to start debugging, as I'm not a Mac user. -- [[User:Http|http]] 16:36, 11 January 2012 (MST)
: I compiled it under OSX Lion and can also run it but I only get a zero sized dump. May or may not be a problem of the program & Lion or that I only have iPhone2G & 3G to test.--[[User:M2m|M2m]] 04:15, 12 January 2012 (MST)

== Dumping 3GS bootrom from OSX 10.7.2 ==

sudo ./bdu
______ Bootrom Dumper Utility (BDU) 1.0 ______

(c) pod2g october 2010

[.] Now executing arbitrary code using geohot's limera1n...
sent data to copy: 800
padded to 0x84023000
sent shellcode: 800 has real length 48
never freed: 800
sent exploit to heap overflow: FFFFFFF9
[.] Dump payload started.
[.] Now dumping bootrom to file bootrom.bin...
Segmentation fault: 11

Any ideas? I've changed all the offsets to the ones in the wiki and yet still no success.
:Try the unchanged version on a compatible device first. Also try the included precompiled executable. If it still doesn't work, try on Linux first. Post an update on how that went. -- [[User:Http|http]] 05:06, 20 January 2012 (MST)

Pangu8

2014-11-04T15:44:41Z

Markcoker: Making consistent

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

'''Pangu8''' is an [[untethered jailbreak]] for all devices on iOS 8.0 through 8.1, except the [[Apple TV]]. It was initially released on 22 October 2014 as a SSH version only, because [[Cydia|Cydia.app]] and [[Cydia Substrate]] hadn't been updated for iOS 8. [[Cydia|Cydia.app]] was updated later that day for iOS 8 support. [[Cydia Substrate]] has since been updated. On 31 October 2014, version 1.1.0 was released to fix the remaining bugs and include Cydia by default. version 1.2.0 was released on November 4, 2014, to further address bug fixes. Pangu8 was patched in iOS 8.1.1.

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

== Download ==
{| class="wikitable"
! Version
! OS
! SHA-1 Hash
! colspan="2" | Download
! Changes
|-
| 1.0.0
| [[wikipedia:Microsoft Windows|Windows]]
| <code>83e1452fc354eeb2356f0da1a88efd760d94abcb</code>
| style="text-decoration: line-through;" | [http://dl.pangu.25pp.com/jb/Pangu8_v1.0.0.exe 25PP]
| rowspan="2" {{n/a}}
|
* First version of Pangu8 which supports all devices with iOS 8/8.1.
|-
| 1.0.1
| [[wikipedia:Microsoft Windows|Windows]]
| <code>a18013b2a55656af4126e00e34bc22a4011b1bab</code>
| [http://dl.pangu.25pp.com/jb/Pangu8_v1.0.1.exe 25PP]
|
* Fix an issue may cause lost of photos.
|-
| 1.1.0
| [[wikipedia:Microsoft Windows|Windows]]
| <code>6c2dbe785f32deaa12bc18f3680e1ecc045c0e08</code>
| [http://dl.pangu.25pp.com/jb/Pangu8_v1.1.0.exe 25PP]
| [https://mega.co.nz/#!PE1iWDbC!I5AuPbmRJE9gHFtrhcEkF61W0Ibz7ucwNbtJvCpEYjE MEGA]
|
* Bundle latest Cydia for iOS8.
* Optimize jailbreak process.
* Fix an issue that may cause MobileSafari to crash on 64bit devices.
* Fix an issue that causes iMessage/SMS to fail to send images.
* Respring is not required anymore to make Substrate working.
* Pangu APP now with some useful functions.
* Add English support
|-
| 1.2.0
| [[wikipedia:Microsoft Windows|Windows]]
| <code>35b8ebe4c08d0947136ee7c7c19766dc55c4f955</code>
| [http://dl.pangu.25pp.com/jb/Pangu8_v1.2.0.exe 25PP]
| [https://mega.co.nz/#!CM9UDSCQ!DvTM3y3HtoMwehNJWBoLLfCXOtgLkuQwdKYJ4_t_P_E MEGA]
|
* Fix the issue that launchd may drain cpu on 32bit devices.
* Fix Safari reloading bug and occasionally crash problem.
* Optimize jailbreak process.
* Restore function now support iPad Air2/iPad Mini3.
|}

== Name ==

"Pangu" is the name of the [https://en.wikipedia.org/wiki/Pangu "the first living being and the creator of all in some versions of Chinese mythology"].

The 8.0-8.1 untether is nicknamed "Xuan-Yuan Sword", which refers to a powerful weapon in a series of video games based on Chinese mythology (see [https://en.wikipedia.org/wiki/Xuan-Yuan_Sword Xuan-Yuan Sword on Wikipedia]).

This follows in the theme of the nickname of [[Pangu|Pangu's 7.1-7.1.2 untether]], which was "Pangu Axe", the powerful weapon used by the mythological Pangu to separate the earth and the sky.

[[Category:Jailbreaks]]

Talk:Lightning Connector

2014-04-09T13:02:32Z

Markcoker: /* Breakout Board for Serial Debugging */

== Content ==
Oh, totally missed it that we already had such a page. Sorry for that. But what is missing here is still the main content instead of sales blabla: Pinouts, hardware protocol and other tech infos. --[[User:Http|http]] 00:28, 7 November 2012 (MST)
:'''Lightning Connector''' is better than '''Lightning''' ''IMHO''. Anyways, there is a pinout. But it's a weak one as the pins are dynamic. --[[User:5urd|5urd]] 17:01, 7 November 2012 (MST)

== Breakout Board for Serial Debugging ==
So it terms of connecting to iPhone via serial using the lighting connector is there publicly available breakout boards or iPhone to serial cables even? is there information about how they work with the new cable? {{unsigned|Markcoker|0:16, 30 January 2013 (UTC)}}
:No known way to do that yet. --[[User:Http|http]] ([[User talk:Http|talk]]) 23:57, 30 January 2013 (UTC)
::Most likely a stupid question lighting > 30 pin > serial breakout ? --[[User:Markcoker|Blue Skies]] ([[User talk:Markcoker|talk]]) 13:02, 9 April 2014 (UTC)

== Haywire ==

I suggest to move the entire Adapter part to the new page [[Haywire]]. Maybe we leave the Lightning to 30-pin Connector here, as it is not related to this Haywire thing? Opinions? --[[User:Http|http]] ([[User talk:Http|talk]]) 23:20, 17 March 2013 (UTC)
: I don't really mind, but I rather think that 'haywire' is the internal name for the whole lightning port.--[[User:M2m|M2m]] ([[User talk:M2m|talk]]) 23:25, 17 March 2013 (UTC)

Talk:Lightning Connector

2014-04-09T13:00:32Z

Markcoker: /* Breakout Board for Serial Debugging */

== Content ==
Oh, totally missed it that we already had such a page. Sorry for that. But what is missing here is still the main content instead of sales blabla: Pinouts, hardware protocol and other tech infos. --[[User:Http|http]] 00:28, 7 November 2012 (MST)
:'''Lightning Connector''' is better than '''Lightning''' ''IMHO''. Anyways, there is a pinout. But it's a weak one as the pins are dynamic. --[[User:5urd|5urd]] 17:01, 7 November 2012 (MST)

== Breakout Board for Serial Debugging ==
So it terms of connecting to iPhone via serial using the lighting connector is there publicly available breakout boards or iPhone to serial cables even? is there information about how they work with the new cable? {{unsigned|Markcoker|0:16, 30 January 2013 (UTC)}}
:No known way to do that yet. --[[User:Http|http]] ([[User talk:Http|talk]]) 23:57, 30 January 2013 (UTC)
::Most likely a stupid question lighting > 30 pin > serial breakout ?

== Haywire ==

I suggest to move the entire Adapter part to the new page [[Haywire]]. Maybe we leave the Lightning to 30-pin Connector here, as it is not related to this Haywire thing? Opinions? --[[User:Http|http]] ([[User talk:Http|talk]]) 23:20, 17 March 2013 (UTC)
: I don't really mind, but I rather think that 'haywire' is the internal name for the whole lightning port.--[[User:M2m|M2m]] ([[User talk:M2m|talk]]) 23:25, 17 March 2013 (UTC)

Talk:AES Keys

2014-04-04T11:32:40Z

Markcoker: /* Finding AES keys. */

==Greenpois0n Method==
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)
:you need a [[payload]] or run -s flag on [[IBSS]] --[[User:Liamchat|liamchat]] 16:29, 11 November 2010 (UTC)
::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)
:::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)
go aes dec AACACFB9258D7DFBF7D46F21BD9BF27C7E67C673594B7DEE4FF8FE1F08040B1F
go aes dec FF47F3DA0949016984CDED28E286C45CB14B1962B328F82589608C5A5D0A4050
go aes dec 73FFC67694FC821AB9C21CB3CC9A64792D14320F917F469B4935110284990778
go aes dec 3DD9554AB61398A3B6323FA71730A4243837777651DFB8AD212B81ECF194C653
go aes dec 3D2B301E5A7069D52DA258C4B0A2209FA9BA4CEDB120688FC51D3BF1EDEDE5BC
go aes dec E996535613828554253DC21B4875C4BB371FF21699C2D2AF8C02E1137EB1951F
go aes dec 3D538743E45B5B6B6C190B2BBACA705372A3147CC9A60C6856EE2B9B1E60FD85
go aes dec 5FCF5DA27AC995B0B10D76C42ADD5F0BB9268FA88A045EDCCDBC946A73A7CFDC
go aes dec 68D3DE8EA8CC1707D08C983E745EA6A25E40FD532A5BD3BF7760BD540BE257DC
go aes dec 1AE9223C4B8AEBD5F0A30C910212EC8171E3BFC2EF7BF802A39C9C5F45939B2C
go aes dec 87CE52FFEB8E4FB685BA7FA37CBAC0004C9C0B0274FB8A7C1E06D85796063DF0
go aes dec BDB129D92704104423940EC40913FABD30E676CD800E523273DA4E38065B0E13
go aes dec 55D6DE657EB16C5563551C4DA26EE12197783C7100A92695D2B74802F10155C1
go aes dec BA6A3959FBC43D3BCF2708640D5E7B4E5C2306C7ED8A34F7ABC3F49EE6D0BDD4
go aes dec B6689C5BA40B644470C51C35257B984F97F9BE8A3E620086A5A726D7A2C1B7B1
go aes dec 874AD4B93947DAA4D14DDACD3F948F2EFAA207BF6E6FDE3C9D6248E72186894B
go aes dec 9C51D82560C30D976F374F5CB7CC2A7E286FF0067169EA393A8285AC74129D05
/exit note: these are the [[KBAG]]'s of [[Northstar 7D11 (iPod touch 2G)]]
::::--[[User:Liamchat|liamchat]] 18:25, 11 November 2010 (UTC)
:::::Thank you, GreySyntax's version of iRecovery did the trick :) --[[User:Cool name|Cool name]] 19:32, 11 November 2010 (UTC)

== Project ==
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)
: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)
::Finished --[[User:Haifisch|Haifisch]] 00:03, 17 November 2012 (MST)
:::Mind explaining exactly how one would use it? --[[User:5urd|5urd]] 14:39, 17 November 2012 (MST)
::::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)

== Finding AES keys. ==
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}}
: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)
::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)
:::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)
::::What happens if you run <code>file irecovery</code>? Is it a Mac Intel executable? If not, that's why. Any yes, it is for Mac. You need <code>GNU Compiler Collection</code> and <code>gnumake</code> though. --[[User:5urd|5urd]] 17:45, 15 November 2012 (MST)
: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)
::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)
:::I can but half of the commands don't work. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 5:46, 2 December 2012 (MST)
::::Because you need to set them up and know how to use them --[[User:Haifisch|Haifisch]] 15:46, 2 December 2012 (MST)
:::::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)

Talk:BCM4334

2014-01-09T16:17:35Z

Markcoker: /* Monitor Mode */

== Monitor Mode ==
BCM4329 is being used in the iPod touch 3G, iPad, iPhone 4, iPod touch 4G, Apple TV 2G, and iPad 2. BCM4334 used in Apple TV 3G Rev A, iPad 4, iPad mini 1G, iPhone 5, iPhone 5c and iPod touch 5G.
Which prompted the thought why isn't the iphone being used for airdump and aireplay attacks. My understanding is using B43 driver (http://wireless.kernel.org/en/users/Drivers/b43) both are supported (with some limitations - http://www.aircrack-ng.org/doku.php?id=compatibility_drivers#compatibility).
I understand it would most likely require porting tools, but having a working airdump on your iphone = awesomeness. You can then even offload the cracking to an online service or your desktop or using the current aircrack port.
i clearly dont have the full understanding of what is required to get drivers (are drivers required to be signed?) working to allow monitor mode. I assume porting airodump to the iphone be a reasonably easy task?
Anyone have thoughts or insights into this? It is possible for android phones, are iPhones that much different? i would love to see it happen or even just a bit more information on this topic of drivers etc.

--[[User:Markcoker|Blue Skies]] ([[User talk:Markcoker|talk]]) 16:17, 9 January 2014 (UTC)

Talk:BCM4334

2014-01-09T16:17:24Z

Markcoker: Created page with "== Monitor Mode == BCM4329 is being used in the iPod touch 3G, iPad, iPhone 4, iPod touch 4G, Apple TV 2G, and iPad 2. BCM4334 used in Apple TV 3G Rev A, iPad 4, iPad mini 1G..."

Talk:BCM4329

2014-01-09T15:56:20Z

Markcoker: /* Monitor Mode */

== 802.11n on iPod touch 3G ==
Has there been any progress on enabling "N" wifi for the iPod touch 3g?
Makes me wish I wasn't so no0by and I could actually help :/ [[User:Shengis14|Shengis14]] 16:41, 11 October 2010 (UTC)

the wifi firmware on the iPod touch 3g does not alow N but if you open iPod touch 4g firmware you can copy the wifi firmware over ( not tested but should work same os and same chip ) --[[User:Liamchat|liamchat]] 18:10, 11 October 2010 (UTC)

yes it is possible go to /usr/share/firmware/wifi and copy the 3 folders ( all have a .plist file to enable radio ) to your iPod touch 3g and reboot the device --[[User:Liamchat|liamchat]] 18:40, 11 October 2010 (UTC)

== FM Radio ==

Has anyone done any work on enabling the FM radio receiver?--[[User:Dra1nerdrake|dra1nerdrake]] 19:39, 11 October 2010 (UTC)
: Not that I've heard of, but if there is an antenna soldered to the chip then we should be able to do something with it over at iDroid project, once we have OpeniBoot figured out for a device with one of the BCM4329/BCM4325 chips that is. Same goes for 802.11n I suppose. -[[User:Rekoil|Rekoil]] 21:17, 11 October 2010 (UTC)

== Bluetooth HFP ==

Now that the iPod Touch can be jailbroken, has anyone looked into enabling Hands-Free Profile (to connect Bluetooth headsets)? -[[User:TouchFaith|TouchFaith]] 11 October 2010

== Monitor Mode ==

BCM4329 is being used in the iPod touch 3G, iPad, iPhone 4, iPod touch 4G, Apple TV 2G, and iPad 2.
Which prompted the thought why isn't the iphone being used for airdump and aireplay attacks. My understanding is using B43 driver (http://wireless.kernel.org/en/users/Drivers/b43) both are supported (with some limitations - http://www.aircrack-ng.org/doku.php?id=compatibility_drivers#compatibility).

I understand it would most likely require porting tools, but having a working airdump on your iphone = awesomeness. You can then even offload the cracking to an online service or your desktop or using the current aircrack port.

i clearly dont have the full understanding of what is required to get drivers (are drivers required to be signed?) working to allow monitor mode. I assume porting airodump to the iphone be a reasonably easy task?

Anyone have thoughts or insights into this? i would love to see it happen.

--[[User:Markcoker|Blue Skies]] ([[User talk:Markcoker|talk]]) 15:56, 9 January 2014 (UTC)

Talk:BCM4329

2014-01-09T15:56:09Z

Markcoker: /* Monitor Mode */

Talk:BCM4329

2014-01-07T06:20:27Z

Markcoker: added discussion about

IRecovery

2013-09-09T17:02:10Z

Markcoker: /* Updates */ removed dead links, included openjailbreak.org irecovery

{{DISPLAYTITLE:iRecovery}}
iRecovery is a libusb-based CLI utility for Mac OS X, Linux, and Windows. It is able to talk to [[iBoot (Bootloader)|iBoot]] and [[iBSS]] via USB. It's completely open source; the source code is released under the terms of the GNU GPL v3. The full license text can be found in the LICENSE file on github.

It currently connects to:
* [[DFU 0x1227|0x1227]] ([[DFU Mode]]/[[WTF]] Mode 2.0)
* [[Recovery Mode (Protocols)#Recovery_Mode_2.x_.28DevID.3D0x1281.29|Recovery Mode 0x1281]] (Recovery Mode/iBSS)

==Credits==
westbaer

==Thanks==
[[User:Pod2g|pod2g]], [[tom3q]], [[User:Planetbeing|planetbeing]], [[User:Geohot|geohot]] and [[User:posixninja|posixninja]].

==Features==

===DFU 2.0 (0x1227)===
It can upload a file, such as an [[iBSS]], so that you can unplug and spawn a shell with 0x1281.

===Recovery 2.0 (0x1281)===
====File Uploading====
You can upload a file to 0x9000000 with the following syntax:
./iRecovery -f file
In newer builds that use libusb-1.0 this is now
./iRecovery -u file

====Two-Way Shell====
You can spawn a shell to do all sorts of neat things with the syntax:
./iRecovery -s
Once it has spawned, you can type 'help' and iBoot will respond with its built-in command list.

====Single Command====
./iRecovery -c "command"
Sends a single command to the device *without* spawning a shell.

====usb_control_msg(0x21, 2) Exploit Command====
./iRecovery -k
Sends Chronic Dev's + Geohot's latest usb exploit. Implemented into blackra1n.
This was updated near October 17, 2009. [http://github.com/posixninja/irecovery posixninja's fork]
In newer builds this is now -e

====Auto Boot====
You can now enable auto-boot by running:
./iRecovery -a
or by sending /auto-boot in a shell.

====USB Reset====
Reset USB
./iRecovery -r

====Batch Scripting====
iRecovery now supports batch scripting, this allows you to send commands to iBoot from a pre written list of commands, this also suports scripting such as /auto-boot and /upload <file>
./iRecovery -b <file>
or in a shell:
/batch <file>

====Raw Commands====
You can now send raw commands via the -x21 -x40 or -xA1 flags

==Example Output==

iRecovery -s
======================================
::
:: iBSS for n82ap, Copyright 2009, Apple Inc.
::
:: BUILD_TAG: iBoot-596.24
::
:: BUILD_STYLE: RELEASE
::
:: USB_SERIAL_NUMBER: CPID:8900 CPRV:30 CPFM:03 SCEP:05 BDID:04 ECID:000003293C113D76 IBFL:00
::
=======================================

Entering recovery mode, starting command prompt
] printenv
build-style = "RELEASE"
build-version = "iBoot-596.24"
config_board = "n82ap"
loadaddr = "0x9000000"
boot-command = "fsboot"
bootdelay = "0"
auto-boot = "true"
idle-off = "true"
boot-device = "nand0"
boot-partition = "0"
boot-path = "/System/Library/Caches/com.apple.kernelcaches/kernelcache.s5l8900x"
display-color-space = "RGB888"
display-timing = "optC"
framebuffer = "0xfd00000"
secure-boot = "0x1"

== Supported Raw Commands ==

Currently Supported by All Firmware: 
Reboot - Reboots Iphone

More IBoot Commands Information: 
http://code.google.com/p/chronicdev/wiki/iBootCommands

NOTE: 'bgcolor' appears to be no longer supported -- requires confirmation.

==Forks==
[http://github.com/iH8sn0w/irecovery iH8sn0w/irecovery]

[http://github.com/GreySyntax/irecovery GreySyntax/irecovery]

==Updates==
* A C++ port is also in the works dubbed iRecovery++ (by [[User:GreySyntax|GreySyntax]]) can be found at [http://github.com/NSPwn/iRecoveryplusplus GitHub/NSPwn/iRecoveryplusplus]]
* [https://www.openjailbreak.org/projects/libirecovery-2-0/repository libiRecovery 2.0 in development by OpenJailBreak.org]

==Download==
*[https://github.com/Chronic-Dev/libirecovery Chronic-Dev - libiRecovery (Mac OS X | Linux | Windows)]
*[https://github.com/GreySyntax/iRecoveryplusplus GreySyntax - iRecovery++ (Mac OS X| Linux | Windows (Possibly))]

Note: Source only.

[[Category:Hacking Software]]

IRecovery

2013-09-09T16:57:05Z

Markcoker: /* Updates */

{{DISPLAYTITLE:iRecovery}}
iRecovery is a libusb-based CLI utility for Mac OS X, Linux, and Windows. It is able to talk to [[iBoot (Bootloader)|iBoot]] and [[iBSS]] via USB. It's completely open source; the source code is released under the terms of the GNU GPL v3. The full license text can be found in the LICENSE file on github.

It currently connects to:
* [[DFU 0x1227|0x1227]] ([[DFU Mode]]/[[WTF]] Mode 2.0)
* [[Recovery Mode (Protocols)#Recovery_Mode_2.x_.28DevID.3D0x1281.29|Recovery Mode 0x1281]] (Recovery Mode/iBSS)

==Credits==
westbaer

==Thanks==
[[User:Pod2g|pod2g]], [[tom3q]], [[User:Planetbeing|planetbeing]], [[User:Geohot|geohot]] and [[User:posixninja|posixninja]].

==Features==

===DFU 2.0 (0x1227)===
It can upload a file, such as an [[iBSS]], so that you can unplug and spawn a shell with 0x1281.

===Recovery 2.0 (0x1281)===
====File Uploading====
You can upload a file to 0x9000000 with the following syntax:
./iRecovery -f file
In newer builds that use libusb-1.0 this is now
./iRecovery -u file

====Two-Way Shell====
You can spawn a shell to do all sorts of neat things with the syntax:
./iRecovery -s
Once it has spawned, you can type 'help' and iBoot will respond with its built-in command list.

====Single Command====
./iRecovery -c "command"
Sends a single command to the device *without* spawning a shell.

====usb_control_msg(0x21, 2) Exploit Command====
./iRecovery -k
Sends Chronic Dev's + Geohot's latest usb exploit. Implemented into blackra1n.
This was updated near October 17, 2009. [http://github.com/posixninja/irecovery posixninja's fork]
In newer builds this is now -e

====Auto Boot====
You can now enable auto-boot by running:
./iRecovery -a
or by sending /auto-boot in a shell.

====USB Reset====
Reset USB
./iRecovery -r

====Batch Scripting====
iRecovery now supports batch scripting, this allows you to send commands to iBoot from a pre written list of commands, this also suports scripting such as /auto-boot and /upload <file>
./iRecovery -b <file>
or in a shell:
/batch <file>

====Raw Commands====
You can now send raw commands via the -x21 -x40 or -xA1 flags

==Example Output==

iRecovery -s
======================================
::
:: iBSS for n82ap, Copyright 2009, Apple Inc.
::
:: BUILD_TAG: iBoot-596.24
::
:: BUILD_STYLE: RELEASE
::
:: USB_SERIAL_NUMBER: CPID:8900 CPRV:30 CPFM:03 SCEP:05 BDID:04 ECID:000003293C113D76 IBFL:00
::
=======================================

Entering recovery mode, starting command prompt
] printenv
build-style = "RELEASE"
build-version = "iBoot-596.24"
config_board = "n82ap"
loadaddr = "0x9000000"
boot-command = "fsboot"
bootdelay = "0"
auto-boot = "true"
idle-off = "true"
boot-device = "nand0"
boot-partition = "0"
boot-path = "/System/Library/Caches/com.apple.kernelcaches/kernelcache.s5l8900x"
display-color-space = "RGB888"
display-timing = "optC"
framebuffer = "0xfd00000"
secure-boot = "0x1"

== Supported Raw Commands ==

Currently Supported by All Firmware: 
Reboot - Reboots Iphone

More IBoot Commands Information: 
http://code.google.com/p/chronicdev/wiki/iBootCommands

NOTE: 'bgcolor' appears to be no longer supported -- requires confirmation.

==Forks==
[http://github.com/iH8sn0w/irecovery iH8sn0w/irecovery]

[http://github.com/GreySyntax/irecovery GreySyntax/irecovery]

==Updates==
* A C++ port is also in the works dubbed iRecovery++ (by [[User:GreySyntax|GreySyntax]]) can be found at [http://github.com/NSPwn/iRecoveryplusplus GitHub/NSPwn/iRecoveryplusplus]]

==Download==
*[https://github.com/Chronic-Dev/libirecovery Chronic-Dev - libiRecovery (Mac OS X | Linux | Windows)]
*[https://github.com/GreySyntax/iRecoveryplusplus GreySyntax - iRecovery++ (Mac OS X| Linux | Windows (Possibly))]

Note: Source only.

[[Category:Hacking Software]]

IRecovery

2013-09-09T16:55:20Z

Markcoker: /* Download */ -- Removed dead links, added updated links

{{DISPLAYTITLE:iRecovery}}
iRecovery is a libusb-based CLI utility for Mac OS X, Linux, and Windows. It is able to talk to [[iBoot (Bootloader)|iBoot]] and [[iBSS]] via USB. It's completely open source; the source code is released under the terms of the GNU GPL v3. The full license text can be found in the LICENSE file on github.

It currently connects to:
* [[DFU 0x1227|0x1227]] ([[DFU Mode]]/[[WTF]] Mode 2.0)
* [[Recovery Mode (Protocols)#Recovery_Mode_2.x_.28DevID.3D0x1281.29|Recovery Mode 0x1281]] (Recovery Mode/iBSS)

==Credits==
westbaer

==Thanks==
[[User:Pod2g|pod2g]], [[tom3q]], [[User:Planetbeing|planetbeing]], [[User:Geohot|geohot]] and [[User:posixninja|posixninja]].

==Features==

===DFU 2.0 (0x1227)===
It can upload a file, such as an [[iBSS]], so that you can unplug and spawn a shell with 0x1281.

===Recovery 2.0 (0x1281)===
====File Uploading====
You can upload a file to 0x9000000 with the following syntax:
./iRecovery -f file
In newer builds that use libusb-1.0 this is now
./iRecovery -u file

====Two-Way Shell====
You can spawn a shell to do all sorts of neat things with the syntax:
./iRecovery -s
Once it has spawned, you can type 'help' and iBoot will respond with its built-in command list.

====Single Command====
./iRecovery -c "command"
Sends a single command to the device *without* spawning a shell.

====usb_control_msg(0x21, 2) Exploit Command====
./iRecovery -k
Sends Chronic Dev's + Geohot's latest usb exploit. Implemented into blackra1n.
This was updated near October 17, 2009. [http://github.com/posixninja/irecovery posixninja's fork]
In newer builds this is now -e

====Auto Boot====
You can now enable auto-boot by running:
./iRecovery -a
or by sending /auto-boot in a shell.

====USB Reset====
Reset USB
./iRecovery -r

====Batch Scripting====
iRecovery now supports batch scripting, this allows you to send commands to iBoot from a pre written list of commands, this also suports scripting such as /auto-boot and /upload <file>
./iRecovery -b <file>
or in a shell:
/batch <file>

====Raw Commands====
You can now send raw commands via the -x21 -x40 or -xA1 flags

==Example Output==

iRecovery -s
======================================
::
:: iBSS for n82ap, Copyright 2009, Apple Inc.
::
:: BUILD_TAG: iBoot-596.24
::
:: BUILD_STYLE: RELEASE
::
:: USB_SERIAL_NUMBER: CPID:8900 CPRV:30 CPFM:03 SCEP:05 BDID:04 ECID:000003293C113D76 IBFL:00
::
=======================================

Entering recovery mode, starting command prompt
] printenv
build-style = "RELEASE"
build-version = "iBoot-596.24"
config_board = "n82ap"
loadaddr = "0x9000000"
boot-command = "fsboot"
bootdelay = "0"
auto-boot = "true"
idle-off = "true"
boot-device = "nand0"
boot-partition = "0"
boot-path = "/System/Library/Caches/com.apple.kernelcaches/kernelcache.s5l8900x"
display-color-space = "RGB888"
display-timing = "optC"
framebuffer = "0xfd00000"
secure-boot = "0x1"

== Supported Raw Commands ==

Currently Supported by All Firmware: 
Reboot - Reboots Iphone

More IBoot Commands Information: 
http://code.google.com/p/chronicdev/wiki/iBootCommands

NOTE: 'bgcolor' appears to be no longer supported -- requires confirmation.

==Forks==
[http://github.com/iH8sn0w/irecovery iH8sn0w/irecovery]

[http://github.com/GreySyntax/irecovery GreySyntax/irecovery]

==Updates==
* A C++ port is also in the works dubbed iRecovery++ (by [[User:GreySyntax|GreySyntax]]) can be found at [http://github.com/NSPwn/iRecoveryplusplus GitHub/NSPwn/iRecoveryplusplus]]
* A VB.NET port (by [[User:Fallensn0w|Fallensn0w]]) can be found at [http://github.com/fallensn0w/vbiRecovery GitHub/fallensn0w/vbiRecovery]
* A GUI (Graphical User Interface) has been made for Windows under the name [[GiRecovery|Zeratul]] and it's developed by [[User:Fallensn0w|Fallensn0w]] and available at [http://github.com/fallensn0w/Zeratul @github]
(or compiled binary files [http://fallensn0w.host22.com here].)
* A new iRecovery port to 4.0x (by [[User:Xx TechGeek xX|Xx TechGeek xX]]) can be downloaded at [http://hotfile.com/dl/128302927/404f4fe/iRecovery.zip.html HotFile]

==Download==
*[https://github.com/Chronic-Dev/libirecovery Chronic-Dev - libiRecovery (Mac OS X | Linux | Windows)]
*[https://github.com/GreySyntax/iRecoveryplusplus GreySyntax - iRecovery++ (Mac OS X| Linux | Windows (Possibly))]

Note: Source only.

[[Category:Hacking Software]]

ITunes Errors/16xx

2013-02-21T13:26:01Z

Markcoker: /* Error 1600 */

=== Error 1600 ===
* Custom firmware can't be restored on a device with [[DFU Mode]]. The software of the device isn't patched. Using a jailbreak tool, enter a pwned [[DFU Mode]]. During that process the software gets patched and the custom firmware should run without any problems.
* [[APTicket]] problems if you try to restore to iOS 5.x in the [[DFU Mode]].
* If trully stuck (even with an regular iTunes Restore), edit the hosts file and comment out the "guzzoni.apple.com" line
* GetDeviceID: failed for iBoot (experienced on Windows 8)

=== Error 1601 ===
See [http://support.apple.com/kb/TA38633 KB TA38633].

=== Error 1602 ===
* Restart computer; change computer; reinstall system.
* If this error occured during an [[Apple TV]] restore, then unplug the [[Apple TV]] from the power cable, after you entered the [[Recovery Mode|recovery]] or [[DFU Mode|DFU]] mode, and then try it again.

=== Error 1603 ===
False [[kernelcache]] patch. Known on damaged bundles from unofficial [[PwnageTool]] distributions or bundles. See also Apple's [http://support.apple.com/kb/TA38603 KB TA38604]

=== Error 1604 ===
Device was not pwned (signature checks were not blocked). Custom firmware can't be restored. Can also happen when there's a problem with the [[IPSW File Format|IPSW]].

=== Error 1611 ===
[[iTunes]] tried to enter the [[Restore Mode]], but the device turned back to the [[Recovery Mode]].
This can happen when updating an [[iPad 2]] jailbroken with [[Saffron]] gets updated to [[iOS]] 5. In this case simply retry, as it is in [[Recovery Mode]] then anyway.

=== Error 1618 ===
Missing system files or corrupt data in iTunes installation. Try to uninstall iTunes, restart computer, install again.
This error also occurs for iTunes in [[wikipedia:Windows 8|Windows 8]] for reasons currently unknown.

=== Error 1619 ===
[[iTunes]] is too old and couldn't read the iPhone in Recovery or DFU Mode. Please update [[iTunes]] and try it again.

=== Error 1644 ===
[[IPSW File Format|IPSW]] was moved during prepare with [[iTunes]]. Try it again and don't move the IPSW.

=== Error 1646 ===
iTunes expected the device to be in a different state (Example: booted into [[iOS]] rather than jumping to [[iBEC]]).

Talk:Baseband Commands

2013-02-08T04:07:35Z

Markcoker: /* Working on the iPhone 5 */

i bought an iphone from 2weeks with baseband 02.30.03 and bootlooder 6.2 and i need to unlock it to work with vodafone sim card need you'r help plz find me a sulution to unlock or downgrade my baseband so i can use yellowsn0w {{unsigned|Na7la|15:57, April 16, 2009 (UTC)}}

I am having trouble figuring out how to run these commands on my iPhone 4. I mean minicom does not work. I saved and all but it wont let me see what command im typing and it says "offline" in the bottom. {{unsigned|Grisolp|22:25, April 5, 2011 (UTC)}}
:You have to remember, minicom hasn't been updated in a while. It's probably not going to work very well with iOS 4+, and pretty much any device after the iPhone 3G... also, sign your talk page comments :) --[[User:Rdqronos|rdqronos]] 06:22, 23 July 2011 (MDT)

== Working on the iPhone 4? ==

Well, I tried tty.debug, dlci.baseband.blablabla... amd it didn't seem to work very well. Are there new releases of minicom? Or the source of it? --[[User:XiiiX|XiiiX]] 17:09, 14 August 2011 (MDT)
:Minicom is an open source project: [http://alioth.debian.org/projects/minicom/] --pjakuszew 12:45, 15 August 2011 (MDT)
::The days of <code>tty.baseband</code> are gone (1.x?). <code>tty.debug</code> does not require CommCenter to be shut down, but you have to spam AT[enter] until you get a reply and then issue your command hoping the connection doesn't fail as CommCenter is using the BB pretty much all the time making you unable to connect. Also, the OFFLINE message is normal. --[[User:Ryccardo|Ryccardo]] 05:37, 16 August 2011 (MDT)
:Would shutting down CommCenter help though? Like honestly, if it's that much of an issue, I'll run the command to kill it... Also, if I did kill CC, would I have to spam AT or would one typing of AT do it? --[[User:Rdqronos|rdqronos]] 17:00, 16 August 2011 (MDT)
::According to my experience in 3.x, shutting down CommCenter ''barely'' helps yet it's pretty much a requirement. Remember that shutting it down remover Wi-Fi until a reboot, so you have to permanently disable it (<code>launchctl unload -w /System…</code>), reboot until you can't get signal as per the status bar + get the non-visual voicemail indicator (empty badge over Phone icon), try your luck then enable CCenter with <code>launchctl load -w /System…</code>. --[[User:Ryccardo|Ryccardo]] 16:50, 18 August 2011 (MDT)

One way around this is to install signal iphone app found in cydia:

"...Signal was designed for iOS 4, and contacts /dev/tty.debug in a iOS 4 compatible way, it does this to receive baseband information, one of them being, the exact measurement in dBm. This opens the port to /dev/tty.debug..." (http://applehack23.blogspot.com/2010/09/smscl-on-iphone-4-and-ios-4.html#comments)

I can confirm this works.--[[User:JackR1|JackR1]] 07:44, 23 September 2011 (MDT)

== Working on the iPhone 5 ==

Well...

Minicom set to connect to tty.debug connects* (if i turn off commcenter using "launchctl unload /System/Library/LaunchDaemons/com.apple.CommCenter.plist").
It doesn't display anything. I've tried spamming AT with no success.

i tested tty.wlan-debug to see if anything gets displayed, and it does.

Dump of /dev
{| class="wikitable"

|aes_0 ||klog ||random ||ttyp9
|-
|bpf0 ||null ||rdisk0 ||ttypa
|-
|bpf1 ||pf ||rdisk0s1 ||ttypb
|-
|bpf2 ||pfm ||rdisk0s1s1 ||ttypc
|-
|bpf3 ||ptmx ||rdisk0s1s2 ||ttypd
|-
|btpoweroff ||ptyp0 ||tty ||ttype
|-
|btwake ||ptyp1 ||tty.bluetooth ||ttypf
|-
|console ||ptyp2 ||tty.debug ||ttys000
|-
|cu.bluetooth ||ptyp3 ||tty.debug-console ||uart.bluetooth
|-
|cu.debug ||ptyp4 ||tty.gas-gauge ||uart.debug
|-
|cu.debug-console ||ptyp5 ||tty.iap ||uart.debug-console
|-
|cu.gas-gauge ||ptyp6 ||tty.wlan-debug ||uart.gas-gauge
|-
|cu.iap ||ptyp7 ||ttyp0 ||uart.iap
|-
|cu.wlan-debug ||ptyp8 ||ttyp1 ||uart.wlan-debug
|-
|disk0 ||ptyp9 ||ttyp2 ||urandom
|-
|disk0s1 ||ptypa ||ttyp3 ||vn0
|-
|disk0s1s1 ||ptypb ||ttyp4 ||vn1
|-
|disk0s1s2 ||ptypc ||ttyp5 ||zero
|-
|fsevents ||ptypd ||ttyp6
|-
|io8log ||ptype ||ttyp7
|-
|io8logmt ||ptypf ||ttyp8
|}

Ideas?!? im dont know what else to really try?

--[[User:Markcoker|Blue Skies]] ([[User talk:Markcoker|talk]]) 04:07, 8 February 2013 (UTC)

Talk:Baseband Commands

2013-02-08T00:38:36Z

Markcoker: iPhone5 Baseband Connection

Talk:Lightning Connector

2013-01-30T00:16:15Z

Markcoker: /* Content */

Talk:Lightning Connector

2013-01-30T00:15:38Z

Markcoker: serial

The iPhone Wiki:Community portal

2013-01-28T09:43:17Z

Markcoker: /* THIS IS THE NEW MIRROR */

{{Talk Archive|2010|2011|2012}}
{{float toc|right}}
{{see also|Unsolved problems}}
This is the place to post ideas to help the wiki and for proposed changes that admins must make.

== Site Related Requests ==
=== More Esser Info ===
i0nic's slides from his CanSecWest [http://antid0te.com/CSW2012_StefanEsser_iOS5_An_Exploitation_Nightmare_FINAL.pdf presentation have been released]. Where should we link to them from? --[[User:Beej|beej]] 17:38, 17 March 2012 (MDT)

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

=== Theme ===
Several people are compaining about the theming/style change [http://twitter.com/#!/DarkMalloc/status/174555059777052672 1] [http://twitter.com/#!/Gojohnnyboi/status/178253989232648192 2]. I wasn't involved in this change (except the new image), but I think there was no discussion about changing the default style. Can't we switch the default style back to how it was and for those that like a fancy new theme can still have the new one? -- [[User:Http|http]] 16:37, 9 March 2012 (MST)
:The way to add new themes would be to have access to the server. Thats why we did this. What we can do is get geohot to copy Vector.php, Vector.deps.php, and Vector/ to iPhone.php, iPhone.deps.php, and iPhone/ and modify some variables. I can do that. Then just move [[Mediawiki:Vector.css]] to [[Mediawiki:iPhone.css]]. --[[User:5urd|5urd]] 17:05, 9 March 2012 (MST)
::Second this. In fact, seeing as it'll have the same base html/css/js as vector, geohot can copy Vector.deps.php→iPhone.deps.php, [http://pastie.org/3583443 save this to iPhone.php], put <tt>$wgDefaultSkin="iphone";</tt> in LocalSettings.php and then [http://theiphonewiki.com/wiki/index.php?title=special:movepage&wpOldTitle=mediawiki:vector.css&wpNewTitle=mediawiki:iPhone.css&wpReason=moving+iphone+style+to+separate+skin&wpMovetalk=1 move the css] [[User:thekirbylover|the]][[User talk:thekirbylover|kirby]][[Special:Contributions/thekirbylover|lover]] 02:01, 13 March 2012 (MDT)
:As I've tweeted about since last night, I decided to give the current iOS-like theme a bit of a makeover. [http://img.ly/fa7T Here's] how it looks in Chromium. The theme also works in Firefox for Windows, except the left navigation tabs aren't shifted closer to the center. I haven't gotten around to testing it in other browsers just yet, unfortunately. Thoughts on this? --[[User:Dialexio|Dialexio]] 18:32, 12 March 2012 (MDT)
::Looks great, though as I mentioned on twitter, the heading should be put somewhere in the title bar area so it looks more realistic. Maybe something similar to the "other network" window under Wi-Fi settings. [[User:thekirbylover|the]][[User talk:thekirbylover|kirby]][[Special:Contributions/thekirbylover|lover]] 02:01, 13 March 2012 (MDT)
:::That'd be nice, but I don't want the page heading to overlap the tabs. --[[User:Dialexio|Dialexio]] 13:46, 13 March 2012 (MDT)
I added my modifications to the theme. It works as desired in all (desktop) browsers except IE… I'll make an attempt at improving the theme in IE 7/+. --[[User:Dialexio|Dialexio]] 21:05, 8 April 2012 (MDT)
:Looking great :) I tested in IE8 and 9, doesn't look too bad, barring the unselected tabs due to the solid background; you can use the longer <tt>filter</tt>/<tt>-ms-filter</tt> syntax [http://msdn.microsoft.com/en-us/library/ms532997(v=vs.85).aspx like so] for IE gradients [[User:thekirbylover|the]][[User talk:thekirbylover|kirby]][[Special:Contributions/thekirbylover|lover]] 09:06, 15 April 2012 (MDT)
----
I created more modifications that I'd like feedback on before the possibly get implemented. Both of these are meant to further help emulate the iOS look. I was thinking of giving the sidebar and header bar fixed positioning, so they stick around regardless of where you scroll. ([http://img.ly/nded Screenshot]) I also created some CSS that makes some headers (particularly those on the [[Main Page]] and [[Special:SpecialPages|Special pages]] page) look like iOS… sections? (I don't recall the correct term for it.) [http://img.ly/ndee Here's] a screenshot since I suck at describing what I'm trying to say. :P Thoughts on these changes? --[[User:Dialexio|Dialexio]] 19:39, 11 September 2012 (MDT)
:They're section headers :) and they look great, but maybe some negative margins (like <code>margin: 0 -8px</code>) could be used to make them extend to the edge of the page area and look more iOS-y. The top bar could go well with some fixed positioning, but I don't think the sidebar should. [[User:thekirbylover|the]][[User talk:thekirbylover|kirby]][[Special:Contributions/thekirbylover|lover]] 19:51, 11 September 2012 (MDT)
::I didn't really want the sidebar to be fixed either. However, the title bar actually stretches across the complete width of the page, and scrolling down on long pages can reveal that.[http://img.ly/nk8O] Currently, that section of the title bar is hidden by applying the linen background to the logo, hence why I currently have the sidebar fixed. Any ideas on how deal with the title bar? --[[User:Dialexio|Dialexio]] 13:04, 14 September 2012 (MDT)
:::One small issue I noticed with making the title bar fixed is that, when you click on an anchor link, the title bar will cover up the header for the section you're looking at (and some content as well). You can always scroll a little up to see what was being blocked though. To combat this problem, I entertained the idea of making just the area where page content is displayed the part that scrolls.[http://img.ly/nqrY] I don't think that a lot of people (especially those with small screens) would like this change, so I'm expecting heavy criticism. I plan on using the previously-mentioned method for the fixed title bar instead of this newer method, unless everybody actually prefers the newer method. :P (Note that the scrolling area is not for the whole page, just the content area.) --[[User:Dialexio|Dialexio]] 20:13, 16 September 2012 (MDT)
----
I'm interested in changing the banner alert for when someone edits your talk page (or a page you're watching?). [http://cl.ly/image/3T1U3b2m0i09 Here's] how it currently looks, and [http://cl.ly/image/1G1p3w3Az0D1R here's][http://cl.ly/image/1G1p3w3A0D1R here's] my proposal. The newer styling is based on iOS once again (the notification banners) and seems more pleasing to the eye, but I'm not sure if it catches the user's attention as well as the older version. (I think it does, but I'm biased. :P) Thoughts? --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 20:03, 24 December 2012 (UTC)
:Ummmm... Your proposal can't be found :P --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 20:14, 24 December 2012 (UTC)
::Fixed the link. Not sure how that "z" slipped into the URL. --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 21:34, 24 December 2012 (UTC)
:::I love it! Maybe move it up a bit and stretch across the entire screen like a notification center banner? I might be able to through together some CSS ([[Mediawiki:vector.js|vector.js]]) for a fold down like the iOS banners. --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 21:51, 24 December 2012 (UTC)

=== [[Firmware]] page ===
I know I just created the iPad mini and iPad (4th generation) entries on the [[Firmware]] page, but I was thinking… Instead of keeping the firmware tables unique to each model, could we keep the firmware tables divided by ''generation'' instead? (i.e. Instead of editing three pages for the iPad mini to add a new firmware, there would be just one page that holds the three firmware tables.) It'd certainly help keep the amount of changes made with each new firmware to a minimum. --[[User:Dialexio|Dialexio]] 19:50, 30 October 2012 (MDT)
:That would certainly reduce the amount of edits. They were separated as the source was getting ridiculously long. I'm for it. --[[User:5urd|5urd]] 20:00, 30 October 2012 (MDT)
:As long as no information gets lost, feel free to change it. But I wonder how you want to put all this into a horizontal design. I think it won't fit or you'd have to remove infos. Can you explain further? --[[User:Http|http]] 00:31, 31 October 2012 (MDT)
::I think you might be misunderstanding a bit; I'm planning on, as one example, copying all of the iPad 2 firmware tables into one embedded page, instead of having four different pages that require editing. Everything's still going to look the same. :P --[[User:Dialexio|Dialexio]] 01:21, 31 October 2012 (MDT)
:::Yes, I misunderstood you. I thought you wanted to regroup the lists by iOS version. Yes, just grouping more devices together seems like a simple change and seems to be useful. --[[User:Http|http]] 04:06, 31 October 2012 (MDT)
:Maybe we could do it like [[Beta Firmware]] where all current devices are on the page while deprecated devices are separated off. --[[User:5urd|5urd]] 18:45, 31 October 2012 (MDT)
:: This would make the code very long, horrible and hard to detect. Maybe someone can make a template like "Latest Public Release" on device pages? --[[User:Adaminsull|adaminsull]] ([[User talk:Adaminsull|talk]]) 18:41, 27 December 2012 (UTC)
:::What? I made [[Beta Firmware]] like that so that instead of editing 15 pages ''per beta'', you would only need to edit one. --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 20:46, 27 December 2012 (UTC)
:::: Sorry I was thinking you meant all devices on one page. Would you like me to attempt to do it? Obviously I will preview it first to make sure its ok. I feel that this would be a good idea. --[[User:Adaminsull|adaminsull]] ([[User talk:Adaminsull|talk]]) 19:00, 14 January 2013 (UTC)
:::::That's fine, but I would move the "deprecated" devices off of it to their own like [[Beta Firmware]] is to reduce clutter a bit. --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 19:31, 14 January 2013 (UTC)
::::: Ok sure. Or what about making a new page for them like [[Unsupported Devices]] ? This would make more sense I would think. I could also do this on [[Beta Firmware]] too. --[[User:Adaminsull|adaminsull]] ([[User talk:Adaminsull|talk]]) 19:34, 14 January 2013 (UTC)
:::::: I have made a depreciated devices template for each device type and have added them to that. Sorry for lots of edits but this was required to make the wiki in shape. Enjoy. --[[User:Adaminsull|adaminsull]] ([[User talk:Adaminsull|talk]]) 20:29, 14 January 2013 (UTC)
::::::: This now also applies to [[Beta Firmware]]. I did this because it uses less templates, looks neater and is easier to add devices to if/when needed. --[[User:Adaminsull|adaminsull]] ([[User talk:Adaminsull|talk]]) 22:07, 14 January 2013 (UTC)

=== iPad mini ===
Me and Alex were chatting on Twitter and the topic of what to do with the iPad mini and two solutions came up:
* New section on [[iPad]]
* New page: [[iPad mini]]
The problem I see with the new page is there are three different models and when we have multiple models for a device, we make the page with that name a disambiguation page. Maybe we could have [[iPad mini]] have a note at the top to a disambiguation page ([[iPad mini (disambiguation)]] or [[iPad mini (first generation)]])? I don't want [[iPad mini 1G]] as we don't list the key pages with the 1G in the title ([[Wildcat 7B500 (iPad)|Wildcat 7B500 ('''iPad''')]]). Any thoughts? --[[User:5urd|5urd]] 09:51, 25 October 2012 (MDT)
:So let's see what we have right now for all the other categories:
:* [[iPhone]] -> [[m68ap]] for 1st gen, [[n82ap]] for 2nd gen, [[n88ap]] 3rd gen, [[iPhone 4]] with different models [[n90ap]], [[n90bap]], [[n92ap]], etc.
:* [[iPod touch]] -> [[n45ap]] for 1st gen, [[n72ap]] for 2nd gen, etc.
:* [[iPad]] -> [[k48ap]] for 1st gen (both Wi-Fi and 3G), [[iPad 2]] for 2nd gen with [[k93ap]], [[k94ap]], [[k95ap]], [[k93aap]], etc.
:* [[Apple TV]] -> [[k66ap]] for 2nd gen
:* [[iPad mini]] -> ? for 1st gen with kap123 etc. for the different models
:So previously we didn't have the problem, because:
:* 1st gen iPhone was only available in one model, [[m68ap]]
:* same for iPod touch, only one model, [[n45ap]]
:* for iPad, both models (Wi-Fi and 3G) had the same model number, later devices have different numbers.
:* for Apple TV, the first iOS version was 2nd gen, so the name without a version number can be used for the device category
:For me it's clear that [[iPad mini]] is for the category of device and must be a separate page. As long as we have only one model, we can add all infos to there and don't create another page between the category and the individual models.
:So the question comes up what to use later when there are more generations, what to use as disambiguation page between the category page [[iPad mini]] and the individual models, something that describes the first generation. We can't use [[iPad mini]], because that's for the category. Why not use [[iPad mini 1]] or [[iPad mini 1G]]? I mean the only problem is that it doesn't match the key pages. So either we start the key pages to include the generation as well, or we simply ignore this difference. I mean why is this a problem if this single page to describe the specifics of the first generation iPad mini has a generation number in the page title? Everybody knows that leaving this 1G away gets you to the device category page [[iPad mini]]. So I don't see a problem here. And as long as there is no 2nd generation, we don't even need such a page. Ok, so I suggest:
:* create [[iPad mini]] for the device category
:* while no 2nd generation exists, put all links onto that same page [[iPad mini]]
:* when 2nd gen iPad mini comes out, create a page [[iPad mini 1]] and [[iPad mini 2]] (or with the "G" if you wish)
:* the key pages can be with our without the "1G", I don't care
--[[User:Http|http]] 14:46, 25 October 2012 (MDT)
::I went ahead and moved the stuff to [[iPad mini]] with a possible link to [[iPad mini 1G]]. I kept the G because everything else has it. I also put a note up on [[iPad]] for the link. The key pages should be determined on how they are with other devices:
::* One model type (like iPad 1G)
::** <code>(iPad mini)</code>
::* Multiple (all else)
::** <code>(iPad mini Wi-Fi)</code>
::** <code>(iPad mini GSM)</code>
::** <code>(iPad mini Global)</code>
::I don't think we should put the <code>1G</code> on the key pages as we don't use <code>(iPhone 2G)</code>, <code>(iPod touch 1G)</code>, or <code>(iPad 1G)</code>. --[[User:5urd|5urd]] 21:38, 25 October 2012 (MDT)
:: I will make them all [[iPad mini]]. When/if we get a 2G iPad mini, add iPad mini 2G. --[[User:Adaminsull|adaminsull]] ([[User talk:Adaminsull|talk]]) 15:44, 15 January 2013 (UTC)

=== Baseband Chip Pages ===
This has been discused before, but why do we use the marketing name for the earliest three baseband chip pages? Because we list the processors under their internal name (not marketing) and the device pages are their internal, not marketing ([[n82ap]] instead of "iPhone 3G"; [[n72ap]] instead of "iPod touch 3G" or "iPod touch (third generation)"). We even have the key pages by code name and build number, not version! Those three pages are the only ones that are listed under their marketing name, not internal. --[[User:5urd|5urd]] 10:24, 25 October 2012 (MDT)

=== Key Pages for [[n90ap|iPhone 4 GSM]] ===
Currently, we list the GSM varient's key pages with <code>(iPhone 4)</code> with the Rev A ones at <code>(iPhone 4 GSM Rev A)</code>, but if Apple decides to release another version of the [[n92ap|CDMA varient]], then we would have:
* iPhone 4
* iPhone 4 GSM Rev A
* iPhone 4 CDMA
* iPhone 4 CDMA Rev A
I think we should move the original GSM ones to <code>iPhone 4 GSM</code> like we do for other pages such as [[Firmware]] ([[Firmware/iPhone 4 GSM|GSM]]/[[Firmware/iPhone 4 GSM Rev A|GSM Rev A]]/[[Firmware/iPhone 4 CDMA|CDMA]]) and [[Beta Firmware]] ([[Beta Firmware/iPhone 4 GSM|GSM]]/[[Beta Firmware/iPhone 4 CDMA|CDMA]]). This was proposed back about a month after the CDMA version came out, but we left it. 
Maybe just four or five pages a day? It will take a few weeks, but it could be done. --[[User:5urd|5urd]] 16:02, 31 October 2012 (MDT)
:Being the person that initially proposed this change, it sounds good to me (as I said on Twitter). Since there are quite a lot of key pages, it would definitely be best to spread out the change over several days (or weeks). --[[User:Dialexio|Dialexio]] 23:01, 31 October 2012 (MDT)
:The extension <code>(iPhone 4)</code> was fine when there was only one iPhone 4. But now, with the CDMA, Rev. A, etc. we need the differentiation. So yes, I agree with the change. But I would rather change all pages at once (if everybody agrees to the change itself). Preferably during a quiet time, when there were no other edits for a week or so. And by the way, for the iPhone 5, Apple refers to the two models as A1428 and A1429, not Global and GSM: [http://www.apple.com/iphone/LTE/] --[[User:Http|http]] 01:33, 2 November 2012 (MDT)

=== Mediawiki upgraded ===
Now version 1.20.2 And switched to PHP 5.4, hopefully it'll be faster. --[[User:Geohot|geohot]] ([[User talk:Geohot|talk]]) 00:49, 22 December 2012 (MST)
: Thanks --[[User:Haifisch|Haifisch]] ([[User talk:Haifisch|talk]]) 00:52, 22 December 2012 (MST)
:: We have realish caching now too, there's no reason this site perf should be bad. If it's still slow at all tomorrow, let me know and I'll move to rackspace --[[User:Geohot|geohot]] ([[User talk:Geohot|talk]]) 04:19, 22 December 2012 (MST)
:Definitely seems faster. The update caused a few CSS problems though - the background image URL needs to be updated to [http://theiphonewiki.com/w/images/1/1a/ScrollView_Texture.png this] and the borders on the top buttons need to be removed. [[User:thekirbylover|the]][[User talk:thekirbylover|kirby]][[Special:Contributions/thekirbylover|lover]] 04:24, 22 December 2012 (MST)
::I'll be working on the CSS fixes. It should be done by tonight. --[[User:Dialexio|Dialexio]] 11:39, 22 December 2012 (MST)
::: Great. Seems much faster now. Thanks [[User:Geohot|geohot]]. --[[User:Adaminsull|Adaminsull]] ([[User talk:Adaminsull|talk]]) 11:40, 22 December 2012 (MST)
:::Great! But we now have a problem. The <code>www</code> mirror is not a duplicate, but a whole nother instance. If you compare the Recent Changes of them both, they are different. George, can you edit the <code>.htaccess</code> or whatever to **REDIRECT** all traffic over? --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 04:50, 23 December 2012 (UTC)
::::So after clicking Save, I was put onto <code>166.78.23.129</code>. Its the same site, but I'm no longer logged in. The edit was saved as you can see, but it could be annoying and ip addresses can be scary to paranoid people. Is there something that tells the server to send you to that IP address when you save? If there is, can you change that also? --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 04:53, 23 December 2012 (UTC)
:::::Err yea, it isn't exactly "mirroring". Everything is switched to 166.78.23.129, and I configured it so it no longer shows up as an ip address. A redirect is tricky, because where do I redirect it to, the ip? Where do links from that site go? The traffic to the old site has been going down every hour, and will fully switch once everyones DNS cache is flushed. --[[User:Geohot|geohot]] ([[User talk:Geohot|talk]]) 16:48, 23 December 2012 (UTC)
::::::Yes! Thanks! --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 00:50, 24 December 2012 (UTC)

=== Title icon ===
[[File:I5.png|thumb|right|150px|adaminsull proposal]]
The top left icon is showing an iPhone 4S. I have made one similar for the iPhone 5. Please consider using it. [[:File:I5.png|I5.png]] --[[User:Adaminsull|Adaminsull]] ([[User talk:Adaminsull|talk]]) 16:08, 23 December 2012 (UTC)
:The image has some artifacts around it. --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 00:50, 24 December 2012 (UTC)
:: What do you mean? --[[User:Adaminsull|Adaminsull]] ([[User talk:Adaminsull|talk]]) 01:00, 24 December 2012 (UTC)
::: Clean up the image --[[User:Haifisch|Haifisch]] ([[User talk:Haifisch|talk]]) 20:19, 24 December 2012 (UTC)
::: I added it over on the right. Look on the left side of the phone. It looks slightly blocky. The cob isn't complete. I'll see if i can fix up the iPhone one. Maybe we could get iSurenix to fix it up? I like the blue text, but I don't know if it will fit with the highly gray/black stuff. I guess it could make it look like a link, but IDK. --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 20:24, 24 December 2012 (UTC)
:::: Give me a while and I will try to fix it closer. --[[User:Adaminsull|adaminsull]] ([[User talk:Adaminsull|talk]]) 20:59, 24 December 2012 (UTC)
::::: Check http://theiphonewiki.com/wiki/File:I5.png now. --[[User:Adaminsull|adaminsull]] ([[User talk:Adaminsull|talk]]) 21:10, 24 December 2012 (UTC)
::::: Also I did this one http://theiphonewiki.com/wiki/File:I5image.png --[[User:Adaminsull|adaminsull]] ([[User talk:Adaminsull|talk]]) 21:25, 24 December 2012 (UTC)
:::::: What do you think? --[[User:Adaminsull|adaminsull]] ([[User talk:Adaminsull|talk]]) 20:50, 27 December 2012 (UTC)

=== THIS IS THE NEW MIRROR ===
Isn't migration fun? --[[User:Geohot|geohot]] ([[User talk:Geohot|talk]]) 22:35, 22 December 2012 (UTC)
:So much --[[User:Haifisch|Haifisch]] ([[User talk:Haifisch|talk]]) 23:21, 22 December 2012 (UTC)
The migration is complete and the old site has been taken offline. Costs me about $50 per month to run, but for now am still avoiding donations or ads. The old one was unacceptably slow, this site gets about 100,000 page loads per day and it was time to move to server that could handle it. It's using a Squid proxy and barely loaded now, so it is capable of handling much more traffic. And it's much more of a pleasure to visit. I'm hoping the increase in speed will encourage more content creation, and if there's anything else I can do to encourage that, let me know, I'm happy to do it. --[[User:Geohot|geohot]] ([[User talk:Geohot|talk]]) 20:09, 23 December 2012 (UTC)
:Thanks for the migration geohot. This helps a lot. See the comments on your talk page since when we have this problem, I think since February or so.
:I'd also like to have an emergency contact where we could reach you (just for wiki related issues, maybe only for admins, so that you don't get bothered with nonsense) - you have our emails to contact us for this if you think it's a good idea.
:If the hosting fee gets a problem, just let us know. Just open a targeted donation and you'll have the money for the next ten years hosting or so. I'm happy to sponsor a month per year or so. --[[User:Http|http]] ([[User talk:Http|talk]]) 22:16, 23 December 2012 (UTC)
:: Im willing to contribute to the costs, if needed. --[[User:Haifisch|Haifisch]] ([[User talk:Haifisch|talk]]) 01:10, 24 December 2012 (UTC)
::Ditto --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 22:30, 24 December 2012 (UTC)

: It would be nice to see an option for donations, even if not for current running cost for future upgrades or running cost. (Possibly to support related research projects) Just wondering if theres any problem with that?

:Geo, this is a great site, resource its great to see you working behind the scences. I know you could probably afford it and is easier to pay your self but if we can share the cost why not :) --[[User:Markcoker|Blue Skies]] ([[User talk:Markcoker|talk]]) 09:32, 28 January 2013 (UTC)

=== iOS 6.1 on revised iPhone 4 (n90bap) ===
[[User:iNeil11|Neil]] claims that the [{{FULLURL:Beta Firmware|diff=28657&oldid=28648}} revised iPhone 4 didn't get iOS 6.1 betas 1-], but Apple [appears to have] released [{{FULLURL:OTA Updates#iPhone 4 (GSM) [Rev A]}} OTA Updates] for the device. [http://www.9to5mac.com 9to5mac]'s report on [http://9to5mac.com/2012/11/01/apple-releases-ios-6-1-beta-for-ipad-iphone-ipod-touch-xcode-4-6-beta-to-developers/ 6.1b1] and [http://9to5mac.com/2012/11/12/apple-releases-ios-6-1-beta-2-to-developers/ 6.1b2] contains a dev center screenshot that shows no link for the revised device. After inspecting [http://mesu.apple.com/assets/com_apple_MobileAsset_SoftwareUpdate/com_apple_MobileAsset_SoftwareUpdate.xml com_apple_MobileAsset_SoftwareUpdate.xml], there are, in fact, payloads for 6.1b2-6.1b3 and 6.1b3-6.1b4. If there was one for 6.1b1-6.1b2, it has been removed. Any ideas? --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 22:30, 24 December 2012 (UTC)
: There must have been due to OTA updates. That is enough evidence. --[[User:Adaminsull|adaminsull]] ([[User talk:Adaminsull|talk]]) 18:43, 27 December 2012 (UTC)
::OTA updates '''aren't''' enought evidence. Apple's automatic packaging system could have compiled the deltas even though there wasn't an IPSW for the device. Unless you can give proof of an IPSW, there are no betas. --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 20:45, 27 December 2012 (UTC)

=== Stub ===
Can we rename "Stub|firmware to stub|Page so its stub page as it sounds silly as firmware? --[[User:Adaminsull|adaminsull]] ([[User talk:Adaminsull|talk]]) 23:32, 25 December 2012 (UTC)
:Firmware is software for the hardware. i.e. baseband. software is user mode stuff. Plus, I set it up that way because that is how Wikipedia does it. It was a simple copy-paste with some modifications so it would work here. --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 00:05, 26 December 2012 (UTC)

=== Editing help ===
I noticed on the edit page there is a link to [[Help:Editing]]. This is actually an empty page. Should we remove this from the page or add some info to it? I am not sure what to add to it even so I haven't touched it. I was wondering what you all thought. --[[User:Adaminsull|adaminsull]] ([[User talk:Adaminsull|talk]]) 20:54, 16 January 2013 (UTC)
:To remove it requires knowing the page it is set on (in the <code>Mediawiki:</code> NS). If you can find that, I'll be fine with changing it. --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 00:26, 17 January 2013 (UTC)
::It's at [[MediaWiki:Edithelppage]]. ([[Special:AllMessages]] is helpful.) --[[User:thekirbylover|the]][[User talk:thekirbylover|kirby]][[Special:Contributions/thekirbylover|lover]] 11:23, 17 January 2013 (UTC)
:Fixed. I changed it to link to [[wikipedia:Help:Editing|Wikipedia's page]]. --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 00:50, 18 January 2013 (UTC)

=== Page Deletion ===
I was wondering how long we have to wait for a page to be deleted? I noticed two that should be. [[iDevice Info]] and [[Sort this]]. {{unsigned|adaminsull}}
:It varies. Some are within a day. Some take a month. Pages with more content generally take longer. As for [[Sort this]], it contains some useful content, albeit unsorted. --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 22:44, 23 January 2013 (UTC)

=== evad3rs page ===
I made this page but [[User:5urd|5urd]] deleted this. I was wondering why? Also what are everybody's thoughts on this? --[[User:Adaminsull|adaminsull]] ([[User talk:Adaminsull|talk]]) 11:43, 26 January 2013 (UTC)
:We had this discussion in the past already on some similar pages. But I think when several of these respected hackers bring this term up several times, then we can also have a page for it. But [[User:Adaminsull|Adaminsull]], don't just create the page again, wait for this discussion to finish. --[[User:Http|http]] ([[User talk:Http|talk]]) 11:59, 26 January 2013 (UTC)
:: I had already made it before seeing this. In future I will just wait. I did put a note to [[User:5urd|5urd]] saying that he left no reason for deletion. --[[User:Adaminsull|adaminsull]] ([[User talk:Adaminsull|talk]]) 12:02, 26 January 2013 (UTC) There is also a twitter account and it has been mentioned that its them by [[user:Pod2g|pod2g]].
:: I also think when a page is deleted the user should give a reason for it. Otherwise no one knows why. --[[User:Adaminsull|adaminsull]] ([[User talk:Adaminsull|talk]]) 12:11, 26 January 2013 (UTC)
::: It is correct that deletions should be discussed first. [[User:5urd|5urd]], can you give a reason why you acted so fast, with no discussion at all? --[[User:Http|http]] ([[User talk:Http|talk]]) 12:21, 26 January 2013 (UTC)
:My apologies. I deleted it as we had an edit war about 2 1/2 years ago on unpopular dev "teams" which resulted in the 3 year block of the [[Main Page|main page]]. There were numerous pages made and a flood of edits to the main page. A simple mention my pod2g does not validate a "team"'s "worthiness" unless it was stated that he is working with them. On a side note, just because you see a "team" that claims to have a jailbreak for 6.0 does not mean they are legitimate. I now looked the team up and it is legitimate, so again, my apologies. --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 01:08, 27 January 2013 (UTC)

User:Markcoker

2013-01-28T09:38:42Z

Markcoker:

Blue Skies (Mark Coker)

Interests in iDevices, security and other technologies.

The iPhone Wiki:Community portal

2013-01-28T09:34:19Z

Markcoker: /* THIS IS THE NEW MIRROR */

{{Talk Archive|2010|2011|2012}}
{{float toc|right}}
{{see also|Unsolved problems}}
This is the place to post ideas to help the wiki and for proposed changes that admins must make.

== Site Related Requests ==
=== More Esser Info ===
i0nic's slides from his CanSecWest [http://antid0te.com/CSW2012_StefanEsser_iOS5_An_Exploitation_Nightmare_FINAL.pdf presentation have been released]. Where should we link to them from? --[[User:Beej|beej]] 17:38, 17 March 2012 (MDT)

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

=== Theme ===
Several people are compaining about the theming/style change [http://twitter.com/#!/DarkMalloc/status/174555059777052672 1] [http://twitter.com/#!/Gojohnnyboi/status/178253989232648192 2]. I wasn't involved in this change (except the new image), but I think there was no discussion about changing the default style. Can't we switch the default style back to how it was and for those that like a fancy new theme can still have the new one? -- [[User:Http|http]] 16:37, 9 March 2012 (MST)
:The way to add new themes would be to have access to the server. Thats why we did this. What we can do is get geohot to copy Vector.php, Vector.deps.php, and Vector/ to iPhone.php, iPhone.deps.php, and iPhone/ and modify some variables. I can do that. Then just move [[Mediawiki:Vector.css]] to [[Mediawiki:iPhone.css]]. --[[User:5urd|5urd]] 17:05, 9 March 2012 (MST)
::Second this. In fact, seeing as it'll have the same base html/css/js as vector, geohot can copy Vector.deps.php→iPhone.deps.php, [http://pastie.org/3583443 save this to iPhone.php], put <tt>$wgDefaultSkin="iphone";</tt> in LocalSettings.php and then [http://theiphonewiki.com/wiki/index.php?title=special:movepage&wpOldTitle=mediawiki:vector.css&wpNewTitle=mediawiki:iPhone.css&wpReason=moving+iphone+style+to+separate+skin&wpMovetalk=1 move the css] [[User:thekirbylover|the]][[User talk:thekirbylover|kirby]][[Special:Contributions/thekirbylover|lover]] 02:01, 13 March 2012 (MDT)
:As I've tweeted about since last night, I decided to give the current iOS-like theme a bit of a makeover. [http://img.ly/fa7T Here's] how it looks in Chromium. The theme also works in Firefox for Windows, except the left navigation tabs aren't shifted closer to the center. I haven't gotten around to testing it in other browsers just yet, unfortunately. Thoughts on this? --[[User:Dialexio|Dialexio]] 18:32, 12 March 2012 (MDT)
::Looks great, though as I mentioned on twitter, the heading should be put somewhere in the title bar area so it looks more realistic. Maybe something similar to the "other network" window under Wi-Fi settings. [[User:thekirbylover|the]][[User talk:thekirbylover|kirby]][[Special:Contributions/thekirbylover|lover]] 02:01, 13 March 2012 (MDT)
:::That'd be nice, but I don't want the page heading to overlap the tabs. --[[User:Dialexio|Dialexio]] 13:46, 13 March 2012 (MDT)
I added my modifications to the theme. It works as desired in all (desktop) browsers except IE… I'll make an attempt at improving the theme in IE 7/+. --[[User:Dialexio|Dialexio]] 21:05, 8 April 2012 (MDT)
:Looking great :) I tested in IE8 and 9, doesn't look too bad, barring the unselected tabs due to the solid background; you can use the longer <tt>filter</tt>/<tt>-ms-filter</tt> syntax [http://msdn.microsoft.com/en-us/library/ms532997(v=vs.85).aspx like so] for IE gradients [[User:thekirbylover|the]][[User talk:thekirbylover|kirby]][[Special:Contributions/thekirbylover|lover]] 09:06, 15 April 2012 (MDT)
----
I created more modifications that I'd like feedback on before the possibly get implemented. Both of these are meant to further help emulate the iOS look. I was thinking of giving the sidebar and header bar fixed positioning, so they stick around regardless of where you scroll. ([http://img.ly/nded Screenshot]) I also created some CSS that makes some headers (particularly those on the [[Main Page]] and [[Special:SpecialPages|Special pages]] page) look like iOS… sections? (I don't recall the correct term for it.) [http://img.ly/ndee Here's] a screenshot since I suck at describing what I'm trying to say. :P Thoughts on these changes? --[[User:Dialexio|Dialexio]] 19:39, 11 September 2012 (MDT)
:They're section headers :) and they look great, but maybe some negative margins (like <code>margin: 0 -8px</code>) could be used to make them extend to the edge of the page area and look more iOS-y. The top bar could go well with some fixed positioning, but I don't think the sidebar should. [[User:thekirbylover|the]][[User talk:thekirbylover|kirby]][[Special:Contributions/thekirbylover|lover]] 19:51, 11 September 2012 (MDT)
::I didn't really want the sidebar to be fixed either. However, the title bar actually stretches across the complete width of the page, and scrolling down on long pages can reveal that.[http://img.ly/nk8O] Currently, that section of the title bar is hidden by applying the linen background to the logo, hence why I currently have the sidebar fixed. Any ideas on how deal with the title bar? --[[User:Dialexio|Dialexio]] 13:04, 14 September 2012 (MDT)
:::One small issue I noticed with making the title bar fixed is that, when you click on an anchor link, the title bar will cover up the header for the section you're looking at (and some content as well). You can always scroll a little up to see what was being blocked though. To combat this problem, I entertained the idea of making just the area where page content is displayed the part that scrolls.[http://img.ly/nqrY] I don't think that a lot of people (especially those with small screens) would like this change, so I'm expecting heavy criticism. I plan on using the previously-mentioned method for the fixed title bar instead of this newer method, unless everybody actually prefers the newer method. :P (Note that the scrolling area is not for the whole page, just the content area.) --[[User:Dialexio|Dialexio]] 20:13, 16 September 2012 (MDT)
----
I'm interested in changing the banner alert for when someone edits your talk page (or a page you're watching?). [http://cl.ly/image/3T1U3b2m0i09 Here's] how it currently looks, and [http://cl.ly/image/1G1p3w3Az0D1R here's][http://cl.ly/image/1G1p3w3A0D1R here's] my proposal. The newer styling is based on iOS once again (the notification banners) and seems more pleasing to the eye, but I'm not sure if it catches the user's attention as well as the older version. (I think it does, but I'm biased. :P) Thoughts? --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 20:03, 24 December 2012 (UTC)
:Ummmm... Your proposal can't be found :P --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 20:14, 24 December 2012 (UTC)
::Fixed the link. Not sure how that "z" slipped into the URL. --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 21:34, 24 December 2012 (UTC)
:::I love it! Maybe move it up a bit and stretch across the entire screen like a notification center banner? I might be able to through together some CSS ([[Mediawiki:vector.js|vector.js]]) for a fold down like the iOS banners. --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 21:51, 24 December 2012 (UTC)

=== [[Firmware]] page ===
I know I just created the iPad mini and iPad (4th generation) entries on the [[Firmware]] page, but I was thinking… Instead of keeping the firmware tables unique to each model, could we keep the firmware tables divided by ''generation'' instead? (i.e. Instead of editing three pages for the iPad mini to add a new firmware, there would be just one page that holds the three firmware tables.) It'd certainly help keep the amount of changes made with each new firmware to a minimum. --[[User:Dialexio|Dialexio]] 19:50, 30 October 2012 (MDT)
:That would certainly reduce the amount of edits. They were separated as the source was getting ridiculously long. I'm for it. --[[User:5urd|5urd]] 20:00, 30 October 2012 (MDT)
:As long as no information gets lost, feel free to change it. But I wonder how you want to put all this into a horizontal design. I think it won't fit or you'd have to remove infos. Can you explain further? --[[User:Http|http]] 00:31, 31 October 2012 (MDT)
::I think you might be misunderstanding a bit; I'm planning on, as one example, copying all of the iPad 2 firmware tables into one embedded page, instead of having four different pages that require editing. Everything's still going to look the same. :P --[[User:Dialexio|Dialexio]] 01:21, 31 October 2012 (MDT)
:::Yes, I misunderstood you. I thought you wanted to regroup the lists by iOS version. Yes, just grouping more devices together seems like a simple change and seems to be useful. --[[User:Http|http]] 04:06, 31 October 2012 (MDT)
:Maybe we could do it like [[Beta Firmware]] where all current devices are on the page while deprecated devices are separated off. --[[User:5urd|5urd]] 18:45, 31 October 2012 (MDT)
:: This would make the code very long, horrible and hard to detect. Maybe someone can make a template like "Latest Public Release" on device pages? --[[User:Adaminsull|adaminsull]] ([[User talk:Adaminsull|talk]]) 18:41, 27 December 2012 (UTC)
:::What? I made [[Beta Firmware]] like that so that instead of editing 15 pages ''per beta'', you would only need to edit one. --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 20:46, 27 December 2012 (UTC)
:::: Sorry I was thinking you meant all devices on one page. Would you like me to attempt to do it? Obviously I will preview it first to make sure its ok. I feel that this would be a good idea. --[[User:Adaminsull|adaminsull]] ([[User talk:Adaminsull|talk]]) 19:00, 14 January 2013 (UTC)
:::::That's fine, but I would move the "deprecated" devices off of it to their own like [[Beta Firmware]] is to reduce clutter a bit. --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 19:31, 14 January 2013 (UTC)
::::: Ok sure. Or what about making a new page for them like [[Unsupported Devices]] ? This would make more sense I would think. I could also do this on [[Beta Firmware]] too. --[[User:Adaminsull|adaminsull]] ([[User talk:Adaminsull|talk]]) 19:34, 14 January 2013 (UTC)
:::::: I have made a depreciated devices template for each device type and have added them to that. Sorry for lots of edits but this was required to make the wiki in shape. Enjoy. --[[User:Adaminsull|adaminsull]] ([[User talk:Adaminsull|talk]]) 20:29, 14 January 2013 (UTC)
::::::: This now also applies to [[Beta Firmware]]. I did this because it uses less templates, looks neater and is easier to add devices to if/when needed. --[[User:Adaminsull|adaminsull]] ([[User talk:Adaminsull|talk]]) 22:07, 14 January 2013 (UTC)

=== iPad mini ===
Me and Alex were chatting on Twitter and the topic of what to do with the iPad mini and two solutions came up:
* New section on [[iPad]]
* New page: [[iPad mini]]
The problem I see with the new page is there are three different models and when we have multiple models for a device, we make the page with that name a disambiguation page. Maybe we could have [[iPad mini]] have a note at the top to a disambiguation page ([[iPad mini (disambiguation)]] or [[iPad mini (first generation)]])? I don't want [[iPad mini 1G]] as we don't list the key pages with the 1G in the title ([[Wildcat 7B500 (iPad)|Wildcat 7B500 ('''iPad''')]]). Any thoughts? --[[User:5urd|5urd]] 09:51, 25 October 2012 (MDT)
:So let's see what we have right now for all the other categories:
:* [[iPhone]] -> [[m68ap]] for 1st gen, [[n82ap]] for 2nd gen, [[n88ap]] 3rd gen, [[iPhone 4]] with different models [[n90ap]], [[n90bap]], [[n92ap]], etc.
:* [[iPod touch]] -> [[n45ap]] for 1st gen, [[n72ap]] for 2nd gen, etc.
:* [[iPad]] -> [[k48ap]] for 1st gen (both Wi-Fi and 3G), [[iPad 2]] for 2nd gen with [[k93ap]], [[k94ap]], [[k95ap]], [[k93aap]], etc.
:* [[Apple TV]] -> [[k66ap]] for 2nd gen
:* [[iPad mini]] -> ? for 1st gen with kap123 etc. for the different models
:So previously we didn't have the problem, because:
:* 1st gen iPhone was only available in one model, [[m68ap]]
:* same for iPod touch, only one model, [[n45ap]]
:* for iPad, both models (Wi-Fi and 3G) had the same model number, later devices have different numbers.
:* for Apple TV, the first iOS version was 2nd gen, so the name without a version number can be used for the device category
:For me it's clear that [[iPad mini]] is for the category of device and must be a separate page. As long as we have only one model, we can add all infos to there and don't create another page between the category and the individual models.
:So the question comes up what to use later when there are more generations, what to use as disambiguation page between the category page [[iPad mini]] and the individual models, something that describes the first generation. We can't use [[iPad mini]], because that's for the category. Why not use [[iPad mini 1]] or [[iPad mini 1G]]? I mean the only problem is that it doesn't match the key pages. So either we start the key pages to include the generation as well, or we simply ignore this difference. I mean why is this a problem if this single page to describe the specifics of the first generation iPad mini has a generation number in the page title? Everybody knows that leaving this 1G away gets you to the device category page [[iPad mini]]. So I don't see a problem here. And as long as there is no 2nd generation, we don't even need such a page. Ok, so I suggest:
:* create [[iPad mini]] for the device category
:* while no 2nd generation exists, put all links onto that same page [[iPad mini]]
:* when 2nd gen iPad mini comes out, create a page [[iPad mini 1]] and [[iPad mini 2]] (or with the "G" if you wish)
:* the key pages can be with our without the "1G", I don't care
--[[User:Http|http]] 14:46, 25 October 2012 (MDT)
::I went ahead and moved the stuff to [[iPad mini]] with a possible link to [[iPad mini 1G]]. I kept the G because everything else has it. I also put a note up on [[iPad]] for the link. The key pages should be determined on how they are with other devices:
::* One model type (like iPad 1G)
::** <code>(iPad mini)</code>
::* Multiple (all else)
::** <code>(iPad mini Wi-Fi)</code>
::** <code>(iPad mini GSM)</code>
::** <code>(iPad mini Global)</code>
::I don't think we should put the <code>1G</code> on the key pages as we don't use <code>(iPhone 2G)</code>, <code>(iPod touch 1G)</code>, or <code>(iPad 1G)</code>. --[[User:5urd|5urd]] 21:38, 25 October 2012 (MDT)
:: I will make them all [[iPad mini]]. When/if we get a 2G iPad mini, add iPad mini 2G. --[[User:Adaminsull|adaminsull]] ([[User talk:Adaminsull|talk]]) 15:44, 15 January 2013 (UTC)

=== Baseband Chip Pages ===
This has been discused before, but why do we use the marketing name for the earliest three baseband chip pages? Because we list the processors under their internal name (not marketing) and the device pages are their internal, not marketing ([[n82ap]] instead of "iPhone 3G"; [[n72ap]] instead of "iPod touch 3G" or "iPod touch (third generation)"). We even have the key pages by code name and build number, not version! Those three pages are the only ones that are listed under their marketing name, not internal. --[[User:5urd|5urd]] 10:24, 25 October 2012 (MDT)

=== Key Pages for [[n90ap|iPhone 4 GSM]] ===
Currently, we list the GSM varient's key pages with <code>(iPhone 4)</code> with the Rev A ones at <code>(iPhone 4 GSM Rev A)</code>, but if Apple decides to release another version of the [[n92ap|CDMA varient]], then we would have:
* iPhone 4
* iPhone 4 GSM Rev A
* iPhone 4 CDMA
* iPhone 4 CDMA Rev A
I think we should move the original GSM ones to <code>iPhone 4 GSM</code> like we do for other pages such as [[Firmware]] ([[Firmware/iPhone 4 GSM|GSM]]/[[Firmware/iPhone 4 GSM Rev A|GSM Rev A]]/[[Firmware/iPhone 4 CDMA|CDMA]]) and [[Beta Firmware]] ([[Beta Firmware/iPhone 4 GSM|GSM]]/[[Beta Firmware/iPhone 4 CDMA|CDMA]]). This was proposed back about a month after the CDMA version came out, but we left it. 
Maybe just four or five pages a day? It will take a few weeks, but it could be done. --[[User:5urd|5urd]] 16:02, 31 October 2012 (MDT)
:Being the person that initially proposed this change, it sounds good to me (as I said on Twitter). Since there are quite a lot of key pages, it would definitely be best to spread out the change over several days (or weeks). --[[User:Dialexio|Dialexio]] 23:01, 31 October 2012 (MDT)
:The extension <code>(iPhone 4)</code> was fine when there was only one iPhone 4. But now, with the CDMA, Rev. A, etc. we need the differentiation. So yes, I agree with the change. But I would rather change all pages at once (if everybody agrees to the change itself). Preferably during a quiet time, when there were no other edits for a week or so. And by the way, for the iPhone 5, Apple refers to the two models as A1428 and A1429, not Global and GSM: [http://www.apple.com/iphone/LTE/] --[[User:Http|http]] 01:33, 2 November 2012 (MDT)

=== Mediawiki upgraded ===
Now version 1.20.2 And switched to PHP 5.4, hopefully it'll be faster. --[[User:Geohot|geohot]] ([[User talk:Geohot|talk]]) 00:49, 22 December 2012 (MST)
: Thanks --[[User:Haifisch|Haifisch]] ([[User talk:Haifisch|talk]]) 00:52, 22 December 2012 (MST)
:: We have realish caching now too, there's no reason this site perf should be bad. If it's still slow at all tomorrow, let me know and I'll move to rackspace --[[User:Geohot|geohot]] ([[User talk:Geohot|talk]]) 04:19, 22 December 2012 (MST)
:Definitely seems faster. The update caused a few CSS problems though - the background image URL needs to be updated to [http://theiphonewiki.com/w/images/1/1a/ScrollView_Texture.png this] and the borders on the top buttons need to be removed. [[User:thekirbylover|the]][[User talk:thekirbylover|kirby]][[Special:Contributions/thekirbylover|lover]] 04:24, 22 December 2012 (MST)
::I'll be working on the CSS fixes. It should be done by tonight. --[[User:Dialexio|Dialexio]] 11:39, 22 December 2012 (MST)
::: Great. Seems much faster now. Thanks [[User:Geohot|geohot]]. --[[User:Adaminsull|Adaminsull]] ([[User talk:Adaminsull|talk]]) 11:40, 22 December 2012 (MST)
:::Great! But we now have a problem. The <code>www</code> mirror is not a duplicate, but a whole nother instance. If you compare the Recent Changes of them both, they are different. George, can you edit the <code>.htaccess</code> or whatever to **REDIRECT** all traffic over? --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 04:50, 23 December 2012 (UTC)
::::So after clicking Save, I was put onto <code>166.78.23.129</code>. Its the same site, but I'm no longer logged in. The edit was saved as you can see, but it could be annoying and ip addresses can be scary to paranoid people. Is there something that tells the server to send you to that IP address when you save? If there is, can you change that also? --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 04:53, 23 December 2012 (UTC)
:::::Err yea, it isn't exactly "mirroring". Everything is switched to 166.78.23.129, and I configured it so it no longer shows up as an ip address. A redirect is tricky, because where do I redirect it to, the ip? Where do links from that site go? The traffic to the old site has been going down every hour, and will fully switch once everyones DNS cache is flushed. --[[User:Geohot|geohot]] ([[User talk:Geohot|talk]]) 16:48, 23 December 2012 (UTC)
::::::Yes! Thanks! --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 00:50, 24 December 2012 (UTC)

=== Title icon ===
[[File:I5.png|thumb|right|150px|adaminsull proposal]]
The top left icon is showing an iPhone 4S. I have made one similar for the iPhone 5. Please consider using it. [[:File:I5.png|I5.png]] --[[User:Adaminsull|Adaminsull]] ([[User talk:Adaminsull|talk]]) 16:08, 23 December 2012 (UTC)
:The image has some artifacts around it. --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 00:50, 24 December 2012 (UTC)
:: What do you mean? --[[User:Adaminsull|Adaminsull]] ([[User talk:Adaminsull|talk]]) 01:00, 24 December 2012 (UTC)
::: Clean up the image --[[User:Haifisch|Haifisch]] ([[User talk:Haifisch|talk]]) 20:19, 24 December 2012 (UTC)
::: I added it over on the right. Look on the left side of the phone. It looks slightly blocky. The cob isn't complete. I'll see if i can fix up the iPhone one. Maybe we could get iSurenix to fix it up? I like the blue text, but I don't know if it will fit with the highly gray/black stuff. I guess it could make it look like a link, but IDK. --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 20:24, 24 December 2012 (UTC)
:::: Give me a while and I will try to fix it closer. --[[User:Adaminsull|adaminsull]] ([[User talk:Adaminsull|talk]]) 20:59, 24 December 2012 (UTC)
::::: Check http://theiphonewiki.com/wiki/File:I5.png now. --[[User:Adaminsull|adaminsull]] ([[User talk:Adaminsull|talk]]) 21:10, 24 December 2012 (UTC)
::::: Also I did this one http://theiphonewiki.com/wiki/File:I5image.png --[[User:Adaminsull|adaminsull]] ([[User talk:Adaminsull|talk]]) 21:25, 24 December 2012 (UTC)
:::::: What do you think? --[[User:Adaminsull|adaminsull]] ([[User talk:Adaminsull|talk]]) 20:50, 27 December 2012 (UTC)

=== THIS IS THE NEW MIRROR ===
Isn't migration fun? --[[User:Geohot|geohot]] ([[User talk:Geohot|talk]]) 22:35, 22 December 2012 (UTC)
:So much --[[User:Haifisch|Haifisch]] ([[User talk:Haifisch|talk]]) 23:21, 22 December 2012 (UTC)
The migration is complete and the old site has been taken offline. Costs me about $50 per month to run, but for now am still avoiding donations or ads. The old one was unacceptably slow, this site gets about 100,000 page loads per day and it was time to move to server that could handle it. It's using a Squid proxy and barely loaded now, so it is capable of handling much more traffic. And it's much more of a pleasure to visit. I'm hoping the increase in speed will encourage more content creation, and if there's anything else I can do to encourage that, let me know, I'm happy to do it. --[[User:Geohot|geohot]] ([[User talk:Geohot|talk]]) 20:09, 23 December 2012 (UTC)
:Thanks for the migration geohot. This helps a lot. See the comments on your talk page since when we have this problem, I think since February or so.
:I'd also like to have an emergency contact where we could reach you (just for wiki related issues, maybe only for admins, so that you don't get bothered with nonsense) - you have our emails to contact us for this if you think it's a good idea.
:If the hosting fee gets a problem, just let us know. Just open a targeted donation and you'll have the money for the next ten years hosting or so. I'm happy to sponsor a month per year or so. --[[User:Http|http]] ([[User talk:Http|talk]]) 22:16, 23 December 2012 (UTC)
:: Im willing to contribute to the costs, if needed. --[[User:Haifisch|Haifisch]] ([[User talk:Haifisch|talk]]) 01:10, 24 December 2012 (UTC)
::Ditto --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 22:30, 24 December 2012 (UTC)

: It would be nice to see an option for donations, even if not for current running cost for future upgrades or running cost. (Possibly to support related research projects) Just wondering if theres any problem with that?

:Geo, this is a great site, resource its great to see you working behind the scences. I know you could probably afford it and is easier to pay your self but if we can share the cost why not :)

--[[User:Markcoker|Blue Skies]] ([[User talk:Markcoker|talk]]) 09:32, 28 January 2013 (UTC)

=== iOS 6.1 on revised iPhone 4 (n90bap) ===
[[User:iNeil11|Neil]] claims that the [{{FULLURL:Beta Firmware|diff=28657&oldid=28648}} revised iPhone 4 didn't get iOS 6.1 betas 1-], but Apple [appears to have] released [{{FULLURL:OTA Updates#iPhone 4 (GSM) [Rev A]}} OTA Updates] for the device. [http://www.9to5mac.com 9to5mac]'s report on [http://9to5mac.com/2012/11/01/apple-releases-ios-6-1-beta-for-ipad-iphone-ipod-touch-xcode-4-6-beta-to-developers/ 6.1b1] and [http://9to5mac.com/2012/11/12/apple-releases-ios-6-1-beta-2-to-developers/ 6.1b2] contains a dev center screenshot that shows no link for the revised device. After inspecting [http://mesu.apple.com/assets/com_apple_MobileAsset_SoftwareUpdate/com_apple_MobileAsset_SoftwareUpdate.xml com_apple_MobileAsset_SoftwareUpdate.xml], there are, in fact, payloads for 6.1b2-6.1b3 and 6.1b3-6.1b4. If there was one for 6.1b1-6.1b2, it has been removed. Any ideas? --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 22:30, 24 December 2012 (UTC)
: There must have been due to OTA updates. That is enough evidence. --[[User:Adaminsull|adaminsull]] ([[User talk:Adaminsull|talk]]) 18:43, 27 December 2012 (UTC)
::OTA updates '''aren't''' enought evidence. Apple's automatic packaging system could have compiled the deltas even though there wasn't an IPSW for the device. Unless you can give proof of an IPSW, there are no betas. --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 20:45, 27 December 2012 (UTC)

=== Stub ===
Can we rename "Stub|firmware to stub|Page so its stub page as it sounds silly as firmware? --[[User:Adaminsull|adaminsull]] ([[User talk:Adaminsull|talk]]) 23:32, 25 December 2012 (UTC)
:Firmware is software for the hardware. i.e. baseband. software is user mode stuff. Plus, I set it up that way because that is how Wikipedia does it. It was a simple copy-paste with some modifications so it would work here. --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 00:05, 26 December 2012 (UTC)

=== Editing help ===
I noticed on the edit page there is a link to [[Help:Editing]]. This is actually an empty page. Should we remove this from the page or add some info to it? I am not sure what to add to it even so I haven't touched it. I was wondering what you all thought. --[[User:Adaminsull|adaminsull]] ([[User talk:Adaminsull|talk]]) 20:54, 16 January 2013 (UTC)
:To remove it requires knowing the page it is set on (in the <code>Mediawiki:</code> NS). If you can find that, I'll be fine with changing it. --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 00:26, 17 January 2013 (UTC)
::It's at [[MediaWiki:Edithelppage]]. ([[Special:AllMessages]] is helpful.) --[[User:thekirbylover|the]][[User talk:thekirbylover|kirby]][[Special:Contributions/thekirbylover|lover]] 11:23, 17 January 2013 (UTC)
:Fixed. I changed it to link to [[wikipedia:Help:Editing|Wikipedia's page]]. --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 00:50, 18 January 2013 (UTC)

=== Page Deletion ===
I was wondering how long we have to wait for a page to be deleted? I noticed two that should be. [[iDevice Info]] and [[Sort this]]. {{unsigned|adaminsull}}
:It varies. Some are within a day. Some take a month. Pages with more content generally take longer. As for [[Sort this]], it contains some useful content, albeit unsorted. --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 22:44, 23 January 2013 (UTC)

=== evad3rs page ===
I made this page but [[User:5urd|5urd]] deleted this. I was wondering why? Also what are everybody's thoughts on this? --[[User:Adaminsull|adaminsull]] ([[User talk:Adaminsull|talk]]) 11:43, 26 January 2013 (UTC)
:We had this discussion in the past already on some similar pages. But I think when several of these respected hackers bring this term up several times, then we can also have a page for it. But [[User:Adaminsull|Adaminsull]], don't just create the page again, wait for this discussion to finish. --[[User:Http|http]] ([[User talk:Http|talk]]) 11:59, 26 January 2013 (UTC)
:: I had already made it before seeing this. In future I will just wait. I did put a note to [[User:5urd|5urd]] saying that he left no reason for deletion. --[[User:Adaminsull|adaminsull]] ([[User talk:Adaminsull|talk]]) 12:02, 26 January 2013 (UTC) There is also a twitter account and it has been mentioned that its them by [[user:Pod2g|pod2g]].
:: I also think when a page is deleted the user should give a reason for it. Otherwise no one knows why. --[[User:Adaminsull|adaminsull]] ([[User talk:Adaminsull|talk]]) 12:11, 26 January 2013 (UTC)
::: It is correct that deletions should be discussed first. [[User:5urd|5urd]], can you give a reason why you acted so fast, with no discussion at all? --[[User:Http|http]] ([[User talk:Http|talk]]) 12:21, 26 January 2013 (UTC)
:My apologies. I deleted it as we had an edit war about 2 1/2 years ago on unpopular dev "teams" which resulted in the 3 year block of the [[Main Page|main page]]. There were numerous pages made and a flood of edits to the main page. A simple mention my pod2g does not validate a "team"'s "worthiness" unless it was stated that he is working with them. On a side note, just because you see a "team" that claims to have a jailbreak for 6.0 does not mean they are legitimate. I now looked the team up and it is legitimate, so again, my apologies. --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 01:08, 27 January 2013 (UTC)

The iPhone Wiki:Community portal

2013-01-28T09:32:53Z

Markcoker:

{{Talk Archive|2010|2011|2012}}
{{float toc|right}}
{{see also|Unsolved problems}}
This is the place to post ideas to help the wiki and for proposed changes that admins must make.

== Site Related Requests ==
=== More Esser Info ===
i0nic's slides from his CanSecWest [http://antid0te.com/CSW2012_StefanEsser_iOS5_An_Exploitation_Nightmare_FINAL.pdf presentation have been released]. Where should we link to them from? --[[User:Beej|beej]] 17:38, 17 March 2012 (MDT)

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

=== Theme ===
Several people are compaining about the theming/style change [http://twitter.com/#!/DarkMalloc/status/174555059777052672 1] [http://twitter.com/#!/Gojohnnyboi/status/178253989232648192 2]. I wasn't involved in this change (except the new image), but I think there was no discussion about changing the default style. Can't we switch the default style back to how it was and for those that like a fancy new theme can still have the new one? -- [[User:Http|http]] 16:37, 9 March 2012 (MST)
:The way to add new themes would be to have access to the server. Thats why we did this. What we can do is get geohot to copy Vector.php, Vector.deps.php, and Vector/ to iPhone.php, iPhone.deps.php, and iPhone/ and modify some variables. I can do that. Then just move [[Mediawiki:Vector.css]] to [[Mediawiki:iPhone.css]]. --[[User:5urd|5urd]] 17:05, 9 March 2012 (MST)
::Second this. In fact, seeing as it'll have the same base html/css/js as vector, geohot can copy Vector.deps.php→iPhone.deps.php, [http://pastie.org/3583443 save this to iPhone.php], put <tt>$wgDefaultSkin="iphone";</tt> in LocalSettings.php and then [http://theiphonewiki.com/wiki/index.php?title=special:movepage&wpOldTitle=mediawiki:vector.css&wpNewTitle=mediawiki:iPhone.css&wpReason=moving+iphone+style+to+separate+skin&wpMovetalk=1 move the css] [[User:thekirbylover|the]][[User talk:thekirbylover|kirby]][[Special:Contributions/thekirbylover|lover]] 02:01, 13 March 2012 (MDT)
:As I've tweeted about since last night, I decided to give the current iOS-like theme a bit of a makeover. [http://img.ly/fa7T Here's] how it looks in Chromium. The theme also works in Firefox for Windows, except the left navigation tabs aren't shifted closer to the center. I haven't gotten around to testing it in other browsers just yet, unfortunately. Thoughts on this? --[[User:Dialexio|Dialexio]] 18:32, 12 March 2012 (MDT)
::Looks great, though as I mentioned on twitter, the heading should be put somewhere in the title bar area so it looks more realistic. Maybe something similar to the "other network" window under Wi-Fi settings. [[User:thekirbylover|the]][[User talk:thekirbylover|kirby]][[Special:Contributions/thekirbylover|lover]] 02:01, 13 March 2012 (MDT)
:::That'd be nice, but I don't want the page heading to overlap the tabs. --[[User:Dialexio|Dialexio]] 13:46, 13 March 2012 (MDT)
I added my modifications to the theme. It works as desired in all (desktop) browsers except IE… I'll make an attempt at improving the theme in IE 7/+. --[[User:Dialexio|Dialexio]] 21:05, 8 April 2012 (MDT)
:Looking great :) I tested in IE8 and 9, doesn't look too bad, barring the unselected tabs due to the solid background; you can use the longer <tt>filter</tt>/<tt>-ms-filter</tt> syntax [http://msdn.microsoft.com/en-us/library/ms532997(v=vs.85).aspx like so] for IE gradients [[User:thekirbylover|the]][[User talk:thekirbylover|kirby]][[Special:Contributions/thekirbylover|lover]] 09:06, 15 April 2012 (MDT)
----
I created more modifications that I'd like feedback on before the possibly get implemented. Both of these are meant to further help emulate the iOS look. I was thinking of giving the sidebar and header bar fixed positioning, so they stick around regardless of where you scroll. ([http://img.ly/nded Screenshot]) I also created some CSS that makes some headers (particularly those on the [[Main Page]] and [[Special:SpecialPages|Special pages]] page) look like iOS… sections? (I don't recall the correct term for it.) [http://img.ly/ndee Here's] a screenshot since I suck at describing what I'm trying to say. :P Thoughts on these changes? --[[User:Dialexio|Dialexio]] 19:39, 11 September 2012 (MDT)
:They're section headers :) and they look great, but maybe some negative margins (like <code>margin: 0 -8px</code>) could be used to make them extend to the edge of the page area and look more iOS-y. The top bar could go well with some fixed positioning, but I don't think the sidebar should. [[User:thekirbylover|the]][[User talk:thekirbylover|kirby]][[Special:Contributions/thekirbylover|lover]] 19:51, 11 September 2012 (MDT)
::I didn't really want the sidebar to be fixed either. However, the title bar actually stretches across the complete width of the page, and scrolling down on long pages can reveal that.[http://img.ly/nk8O] Currently, that section of the title bar is hidden by applying the linen background to the logo, hence why I currently have the sidebar fixed. Any ideas on how deal with the title bar? --[[User:Dialexio|Dialexio]] 13:04, 14 September 2012 (MDT)
:::One small issue I noticed with making the title bar fixed is that, when you click on an anchor link, the title bar will cover up the header for the section you're looking at (and some content as well). You can always scroll a little up to see what was being blocked though. To combat this problem, I entertained the idea of making just the area where page content is displayed the part that scrolls.[http://img.ly/nqrY] I don't think that a lot of people (especially those with small screens) would like this change, so I'm expecting heavy criticism. I plan on using the previously-mentioned method for the fixed title bar instead of this newer method, unless everybody actually prefers the newer method. :P (Note that the scrolling area is not for the whole page, just the content area.) --[[User:Dialexio|Dialexio]] 20:13, 16 September 2012 (MDT)
----
I'm interested in changing the banner alert for when someone edits your talk page (or a page you're watching?). [http://cl.ly/image/3T1U3b2m0i09 Here's] how it currently looks, and [http://cl.ly/image/1G1p3w3Az0D1R here's][http://cl.ly/image/1G1p3w3A0D1R here's] my proposal. The newer styling is based on iOS once again (the notification banners) and seems more pleasing to the eye, but I'm not sure if it catches the user's attention as well as the older version. (I think it does, but I'm biased. :P) Thoughts? --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 20:03, 24 December 2012 (UTC)
:Ummmm... Your proposal can't be found :P --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 20:14, 24 December 2012 (UTC)
::Fixed the link. Not sure how that "z" slipped into the URL. --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 21:34, 24 December 2012 (UTC)
:::I love it! Maybe move it up a bit and stretch across the entire screen like a notification center banner? I might be able to through together some CSS ([[Mediawiki:vector.js|vector.js]]) for a fold down like the iOS banners. --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 21:51, 24 December 2012 (UTC)

=== [[Firmware]] page ===
I know I just created the iPad mini and iPad (4th generation) entries on the [[Firmware]] page, but I was thinking… Instead of keeping the firmware tables unique to each model, could we keep the firmware tables divided by ''generation'' instead? (i.e. Instead of editing three pages for the iPad mini to add a new firmware, there would be just one page that holds the three firmware tables.) It'd certainly help keep the amount of changes made with each new firmware to a minimum. --[[User:Dialexio|Dialexio]] 19:50, 30 October 2012 (MDT)
:That would certainly reduce the amount of edits. They were separated as the source was getting ridiculously long. I'm for it. --[[User:5urd|5urd]] 20:00, 30 October 2012 (MDT)
:As long as no information gets lost, feel free to change it. But I wonder how you want to put all this into a horizontal design. I think it won't fit or you'd have to remove infos. Can you explain further? --[[User:Http|http]] 00:31, 31 October 2012 (MDT)
::I think you might be misunderstanding a bit; I'm planning on, as one example, copying all of the iPad 2 firmware tables into one embedded page, instead of having four different pages that require editing. Everything's still going to look the same. :P --[[User:Dialexio|Dialexio]] 01:21, 31 October 2012 (MDT)
:::Yes, I misunderstood you. I thought you wanted to regroup the lists by iOS version. Yes, just grouping more devices together seems like a simple change and seems to be useful. --[[User:Http|http]] 04:06, 31 October 2012 (MDT)
:Maybe we could do it like [[Beta Firmware]] where all current devices are on the page while deprecated devices are separated off. --[[User:5urd|5urd]] 18:45, 31 October 2012 (MDT)
:: This would make the code very long, horrible and hard to detect. Maybe someone can make a template like "Latest Public Release" on device pages? --[[User:Adaminsull|adaminsull]] ([[User talk:Adaminsull|talk]]) 18:41, 27 December 2012 (UTC)
:::What? I made [[Beta Firmware]] like that so that instead of editing 15 pages ''per beta'', you would only need to edit one. --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 20:46, 27 December 2012 (UTC)
:::: Sorry I was thinking you meant all devices on one page. Would you like me to attempt to do it? Obviously I will preview it first to make sure its ok. I feel that this would be a good idea. --[[User:Adaminsull|adaminsull]] ([[User talk:Adaminsull|talk]]) 19:00, 14 January 2013 (UTC)
:::::That's fine, but I would move the "deprecated" devices off of it to their own like [[Beta Firmware]] is to reduce clutter a bit. --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 19:31, 14 January 2013 (UTC)
::::: Ok sure. Or what about making a new page for them like [[Unsupported Devices]] ? This would make more sense I would think. I could also do this on [[Beta Firmware]] too. --[[User:Adaminsull|adaminsull]] ([[User talk:Adaminsull|talk]]) 19:34, 14 January 2013 (UTC)
:::::: I have made a depreciated devices template for each device type and have added them to that. Sorry for lots of edits but this was required to make the wiki in shape. Enjoy. --[[User:Adaminsull|adaminsull]] ([[User talk:Adaminsull|talk]]) 20:29, 14 January 2013 (UTC)
::::::: This now also applies to [[Beta Firmware]]. I did this because it uses less templates, looks neater and is easier to add devices to if/when needed. --[[User:Adaminsull|adaminsull]] ([[User talk:Adaminsull|talk]]) 22:07, 14 January 2013 (UTC)

=== iPad mini ===
Me and Alex were chatting on Twitter and the topic of what to do with the iPad mini and two solutions came up:
* New section on [[iPad]]
* New page: [[iPad mini]]
The problem I see with the new page is there are three different models and when we have multiple models for a device, we make the page with that name a disambiguation page. Maybe we could have [[iPad mini]] have a note at the top to a disambiguation page ([[iPad mini (disambiguation)]] or [[iPad mini (first generation)]])? I don't want [[iPad mini 1G]] as we don't list the key pages with the 1G in the title ([[Wildcat 7B500 (iPad)|Wildcat 7B500 ('''iPad''')]]). Any thoughts? --[[User:5urd|5urd]] 09:51, 25 October 2012 (MDT)
:So let's see what we have right now for all the other categories:
:* [[iPhone]] -> [[m68ap]] for 1st gen, [[n82ap]] for 2nd gen, [[n88ap]] 3rd gen, [[iPhone 4]] with different models [[n90ap]], [[n90bap]], [[n92ap]], etc.
:* [[iPod touch]] -> [[n45ap]] for 1st gen, [[n72ap]] for 2nd gen, etc.
:* [[iPad]] -> [[k48ap]] for 1st gen (both Wi-Fi and 3G), [[iPad 2]] for 2nd gen with [[k93ap]], [[k94ap]], [[k95ap]], [[k93aap]], etc.
:* [[Apple TV]] -> [[k66ap]] for 2nd gen
:* [[iPad mini]] -> ? for 1st gen with kap123 etc. for the different models
:So previously we didn't have the problem, because:
:* 1st gen iPhone was only available in one model, [[m68ap]]
:* same for iPod touch, only one model, [[n45ap]]
:* for iPad, both models (Wi-Fi and 3G) had the same model number, later devices have different numbers.
:* for Apple TV, the first iOS version was 2nd gen, so the name without a version number can be used for the device category
:For me it's clear that [[iPad mini]] is for the category of device and must be a separate page. As long as we have only one model, we can add all infos to there and don't create another page between the category and the individual models.
:So the question comes up what to use later when there are more generations, what to use as disambiguation page between the category page [[iPad mini]] and the individual models, something that describes the first generation. We can't use [[iPad mini]], because that's for the category. Why not use [[iPad mini 1]] or [[iPad mini 1G]]? I mean the only problem is that it doesn't match the key pages. So either we start the key pages to include the generation as well, or we simply ignore this difference. I mean why is this a problem if this single page to describe the specifics of the first generation iPad mini has a generation number in the page title? Everybody knows that leaving this 1G away gets you to the device category page [[iPad mini]]. So I don't see a problem here. And as long as there is no 2nd generation, we don't even need such a page. Ok, so I suggest:
:* create [[iPad mini]] for the device category
:* while no 2nd generation exists, put all links onto that same page [[iPad mini]]
:* when 2nd gen iPad mini comes out, create a page [[iPad mini 1]] and [[iPad mini 2]] (or with the "G" if you wish)
:* the key pages can be with our without the "1G", I don't care
--[[User:Http|http]] 14:46, 25 October 2012 (MDT)
::I went ahead and moved the stuff to [[iPad mini]] with a possible link to [[iPad mini 1G]]. I kept the G because everything else has it. I also put a note up on [[iPad]] for the link. The key pages should be determined on how they are with other devices:
::* One model type (like iPad 1G)
::** <code>(iPad mini)</code>
::* Multiple (all else)
::** <code>(iPad mini Wi-Fi)</code>
::** <code>(iPad mini GSM)</code>
::** <code>(iPad mini Global)</code>
::I don't think we should put the <code>1G</code> on the key pages as we don't use <code>(iPhone 2G)</code>, <code>(iPod touch 1G)</code>, or <code>(iPad 1G)</code>. --[[User:5urd|5urd]] 21:38, 25 October 2012 (MDT)
:: I will make them all [[iPad mini]]. When/if we get a 2G iPad mini, add iPad mini 2G. --[[User:Adaminsull|adaminsull]] ([[User talk:Adaminsull|talk]]) 15:44, 15 January 2013 (UTC)

=== Baseband Chip Pages ===
This has been discused before, but why do we use the marketing name for the earliest three baseband chip pages? Because we list the processors under their internal name (not marketing) and the device pages are their internal, not marketing ([[n82ap]] instead of "iPhone 3G"; [[n72ap]] instead of "iPod touch 3G" or "iPod touch (third generation)"). We even have the key pages by code name and build number, not version! Those three pages are the only ones that are listed under their marketing name, not internal. --[[User:5urd|5urd]] 10:24, 25 October 2012 (MDT)

=== Key Pages for [[n90ap|iPhone 4 GSM]] ===
Currently, we list the GSM varient's key pages with <code>(iPhone 4)</code> with the Rev A ones at <code>(iPhone 4 GSM Rev A)</code>, but if Apple decides to release another version of the [[n92ap|CDMA varient]], then we would have:
* iPhone 4
* iPhone 4 GSM Rev A
* iPhone 4 CDMA
* iPhone 4 CDMA Rev A
I think we should move the original GSM ones to <code>iPhone 4 GSM</code> like we do for other pages such as [[Firmware]] ([[Firmware/iPhone 4 GSM|GSM]]/[[Firmware/iPhone 4 GSM Rev A|GSM Rev A]]/[[Firmware/iPhone 4 CDMA|CDMA]]) and [[Beta Firmware]] ([[Beta Firmware/iPhone 4 GSM|GSM]]/[[Beta Firmware/iPhone 4 CDMA|CDMA]]). This was proposed back about a month after the CDMA version came out, but we left it. 
Maybe just four or five pages a day? It will take a few weeks, but it could be done. --[[User:5urd|5urd]] 16:02, 31 October 2012 (MDT)
:Being the person that initially proposed this change, it sounds good to me (as I said on Twitter). Since there are quite a lot of key pages, it would definitely be best to spread out the change over several days (or weeks). --[[User:Dialexio|Dialexio]] 23:01, 31 October 2012 (MDT)
:The extension <code>(iPhone 4)</code> was fine when there was only one iPhone 4. But now, with the CDMA, Rev. A, etc. we need the differentiation. So yes, I agree with the change. But I would rather change all pages at once (if everybody agrees to the change itself). Preferably during a quiet time, when there were no other edits for a week or so. And by the way, for the iPhone 5, Apple refers to the two models as A1428 and A1429, not Global and GSM: [http://www.apple.com/iphone/LTE/] --[[User:Http|http]] 01:33, 2 November 2012 (MDT)

=== Mediawiki upgraded ===
Now version 1.20.2 And switched to PHP 5.4, hopefully it'll be faster. --[[User:Geohot|geohot]] ([[User talk:Geohot|talk]]) 00:49, 22 December 2012 (MST)
: Thanks --[[User:Haifisch|Haifisch]] ([[User talk:Haifisch|talk]]) 00:52, 22 December 2012 (MST)
:: We have realish caching now too, there's no reason this site perf should be bad. If it's still slow at all tomorrow, let me know and I'll move to rackspace --[[User:Geohot|geohot]] ([[User talk:Geohot|talk]]) 04:19, 22 December 2012 (MST)
:Definitely seems faster. The update caused a few CSS problems though - the background image URL needs to be updated to [http://theiphonewiki.com/w/images/1/1a/ScrollView_Texture.png this] and the borders on the top buttons need to be removed. [[User:thekirbylover|the]][[User talk:thekirbylover|kirby]][[Special:Contributions/thekirbylover|lover]] 04:24, 22 December 2012 (MST)
::I'll be working on the CSS fixes. It should be done by tonight. --[[User:Dialexio|Dialexio]] 11:39, 22 December 2012 (MST)
::: Great. Seems much faster now. Thanks [[User:Geohot|geohot]]. --[[User:Adaminsull|Adaminsull]] ([[User talk:Adaminsull|talk]]) 11:40, 22 December 2012 (MST)
:::Great! But we now have a problem. The <code>www</code> mirror is not a duplicate, but a whole nother instance. If you compare the Recent Changes of them both, they are different. George, can you edit the <code>.htaccess</code> or whatever to **REDIRECT** all traffic over? --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 04:50, 23 December 2012 (UTC)
::::So after clicking Save, I was put onto <code>166.78.23.129</code>. Its the same site, but I'm no longer logged in. The edit was saved as you can see, but it could be annoying and ip addresses can be scary to paranoid people. Is there something that tells the server to send you to that IP address when you save? If there is, can you change that also? --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 04:53, 23 December 2012 (UTC)
:::::Err yea, it isn't exactly "mirroring". Everything is switched to 166.78.23.129, and I configured it so it no longer shows up as an ip address. A redirect is tricky, because where do I redirect it to, the ip? Where do links from that site go? The traffic to the old site has been going down every hour, and will fully switch once everyones DNS cache is flushed. --[[User:Geohot|geohot]] ([[User talk:Geohot|talk]]) 16:48, 23 December 2012 (UTC)
::::::Yes! Thanks! --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 00:50, 24 December 2012 (UTC)

=== Title icon ===
[[File:I5.png|thumb|right|150px|adaminsull proposal]]
The top left icon is showing an iPhone 4S. I have made one similar for the iPhone 5. Please consider using it. [[:File:I5.png|I5.png]] --[[User:Adaminsull|Adaminsull]] ([[User talk:Adaminsull|talk]]) 16:08, 23 December 2012 (UTC)
:The image has some artifacts around it. --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 00:50, 24 December 2012 (UTC)
:: What do you mean? --[[User:Adaminsull|Adaminsull]] ([[User talk:Adaminsull|talk]]) 01:00, 24 December 2012 (UTC)
::: Clean up the image --[[User:Haifisch|Haifisch]] ([[User talk:Haifisch|talk]]) 20:19, 24 December 2012 (UTC)
::: I added it over on the right. Look on the left side of the phone. It looks slightly blocky. The cob isn't complete. I'll see if i can fix up the iPhone one. Maybe we could get iSurenix to fix it up? I like the blue text, but I don't know if it will fit with the highly gray/black stuff. I guess it could make it look like a link, but IDK. --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 20:24, 24 December 2012 (UTC)
:::: Give me a while and I will try to fix it closer. --[[User:Adaminsull|adaminsull]] ([[User talk:Adaminsull|talk]]) 20:59, 24 December 2012 (UTC)
::::: Check http://theiphonewiki.com/wiki/File:I5.png now. --[[User:Adaminsull|adaminsull]] ([[User talk:Adaminsull|talk]]) 21:10, 24 December 2012 (UTC)
::::: Also I did this one http://theiphonewiki.com/wiki/File:I5image.png --[[User:Adaminsull|adaminsull]] ([[User talk:Adaminsull|talk]]) 21:25, 24 December 2012 (UTC)
:::::: What do you think? --[[User:Adaminsull|adaminsull]] ([[User talk:Adaminsull|talk]]) 20:50, 27 December 2012 (UTC)

=== THIS IS THE NEW MIRROR ===
Isn't migration fun? --[[User:Geohot|geohot]] ([[User talk:Geohot|talk]]) 22:35, 22 December 2012 (UTC)
:So much --[[User:Haifisch|Haifisch]] ([[User talk:Haifisch|talk]]) 23:21, 22 December 2012 (UTC)
The migration is complete and the old site has been taken offline. Costs me about $50 per month to run, but for now am still avoiding donations or ads. The old one was unacceptably slow, this site gets about 100,000 page loads per day and it was time to move to server that could handle it. It's using a Squid proxy and barely loaded now, so it is capable of handling much more traffic. And it's much more of a pleasure to visit. I'm hoping the increase in speed will encourage more content creation, and if there's anything else I can do to encourage that, let me know, I'm happy to do it. --[[User:Geohot|geohot]] ([[User talk:Geohot|talk]]) 20:09, 23 December 2012 (UTC)
:Thanks for the migration geohot. This helps a lot. See the comments on your talk page since when we have this problem, I think since February or so.
:I'd also like to have an emergency contact where we could reach you (just for wiki related issues, maybe only for admins, so that you don't get bothered with nonsense) - you have our emails to contact us for this if you think it's a good idea.
:If the hosting fee gets a problem, just let us know. Just open a targeted donation and you'll have the money for the next ten years hosting or so. I'm happy to sponsor a month per year or so. --[[User:Http|http]] ([[User talk:Http|talk]]) 22:16, 23 December 2012 (UTC)
:: Im willing to contribute to the costs, if needed. --[[User:Haifisch|Haifisch]] ([[User talk:Haifisch|talk]]) 01:10, 24 December 2012 (UTC)
::Ditto --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 22:30, 24 December 2012 (UTC)
:: It would be nice to see an option for donations, even if not for current running cost for future upgrades or running cost. (Possibly to support research even) Just wondering if theres any problem with that?

Geo, this is a great site, resource its great to see you working behind the scences. I know you could probably afford it and is easier to pay your self but if we can share the cost why not :)

--[[User:Markcoker|Blue Skies]] ([[User talk:Markcoker|talk]]) 09:32, 28 January 2013 (UTC)

=== iOS 6.1 on revised iPhone 4 (n90bap) ===
[[User:iNeil11|Neil]] claims that the [{{FULLURL:Beta Firmware|diff=28657&oldid=28648}} revised iPhone 4 didn't get iOS 6.1 betas 1-], but Apple [appears to have] released [{{FULLURL:OTA Updates#iPhone 4 (GSM) [Rev A]}} OTA Updates] for the device. [http://www.9to5mac.com 9to5mac]'s report on [http://9to5mac.com/2012/11/01/apple-releases-ios-6-1-beta-for-ipad-iphone-ipod-touch-xcode-4-6-beta-to-developers/ 6.1b1] and [http://9to5mac.com/2012/11/12/apple-releases-ios-6-1-beta-2-to-developers/ 6.1b2] contains a dev center screenshot that shows no link for the revised device. After inspecting [http://mesu.apple.com/assets/com_apple_MobileAsset_SoftwareUpdate/com_apple_MobileAsset_SoftwareUpdate.xml com_apple_MobileAsset_SoftwareUpdate.xml], there are, in fact, payloads for 6.1b2-6.1b3 and 6.1b3-6.1b4. If there was one for 6.1b1-6.1b2, it has been removed. Any ideas? --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 22:30, 24 December 2012 (UTC)
: There must have been due to OTA updates. That is enough evidence. --[[User:Adaminsull|adaminsull]] ([[User talk:Adaminsull|talk]]) 18:43, 27 December 2012 (UTC)
::OTA updates '''aren't''' enought evidence. Apple's automatic packaging system could have compiled the deltas even though there wasn't an IPSW for the device. Unless you can give proof of an IPSW, there are no betas. --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 20:45, 27 December 2012 (UTC)

=== Stub ===
Can we rename "Stub|firmware to stub|Page so its stub page as it sounds silly as firmware? --[[User:Adaminsull|adaminsull]] ([[User talk:Adaminsull|talk]]) 23:32, 25 December 2012 (UTC)
:Firmware is software for the hardware. i.e. baseband. software is user mode stuff. Plus, I set it up that way because that is how Wikipedia does it. It was a simple copy-paste with some modifications so it would work here. --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 00:05, 26 December 2012 (UTC)

=== Editing help ===
I noticed on the edit page there is a link to [[Help:Editing]]. This is actually an empty page. Should we remove this from the page or add some info to it? I am not sure what to add to it even so I haven't touched it. I was wondering what you all thought. --[[User:Adaminsull|adaminsull]] ([[User talk:Adaminsull|talk]]) 20:54, 16 January 2013 (UTC)
:To remove it requires knowing the page it is set on (in the <code>Mediawiki:</code> NS). If you can find that, I'll be fine with changing it. --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 00:26, 17 January 2013 (UTC)
::It's at [[MediaWiki:Edithelppage]]. ([[Special:AllMessages]] is helpful.) --[[User:thekirbylover|the]][[User talk:thekirbylover|kirby]][[Special:Contributions/thekirbylover|lover]] 11:23, 17 January 2013 (UTC)
:Fixed. I changed it to link to [[wikipedia:Help:Editing|Wikipedia's page]]. --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 00:50, 18 January 2013 (UTC)

=== Page Deletion ===
I was wondering how long we have to wait for a page to be deleted? I noticed two that should be. [[iDevice Info]] and [[Sort this]]. {{unsigned|adaminsull}}
:It varies. Some are within a day. Some take a month. Pages with more content generally take longer. As for [[Sort this]], it contains some useful content, albeit unsorted. --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 22:44, 23 January 2013 (UTC)

=== evad3rs page ===
I made this page but [[User:5urd|5urd]] deleted this. I was wondering why? Also what are everybody's thoughts on this? --[[User:Adaminsull|adaminsull]] ([[User talk:Adaminsull|talk]]) 11:43, 26 January 2013 (UTC)
:We had this discussion in the past already on some similar pages. But I think when several of these respected hackers bring this term up several times, then we can also have a page for it. But [[User:Adaminsull|Adaminsull]], don't just create the page again, wait for this discussion to finish. --[[User:Http|http]] ([[User talk:Http|talk]]) 11:59, 26 January 2013 (UTC)
:: I had already made it before seeing this. In future I will just wait. I did put a note to [[User:5urd|5urd]] saying that he left no reason for deletion. --[[User:Adaminsull|adaminsull]] ([[User talk:Adaminsull|talk]]) 12:02, 26 January 2013 (UTC) There is also a twitter account and it has been mentioned that its them by [[user:Pod2g|pod2g]].
:: I also think when a page is deleted the user should give a reason for it. Otherwise no one knows why. --[[User:Adaminsull|adaminsull]] ([[User talk:Adaminsull|talk]]) 12:11, 26 January 2013 (UTC)
::: It is correct that deletions should be discussed first. [[User:5urd|5urd]], can you give a reason why you acted so fast, with no discussion at all? --[[User:Http|http]] ([[User talk:Http|talk]]) 12:21, 26 January 2013 (UTC)
:My apologies. I deleted it as we had an edit war about 2 1/2 years ago on unpopular dev "teams" which resulted in the 3 year block of the [[Main Page|main page]]. There were numerous pages made and a flood of edits to the main page. A simple mention my pod2g does not validate a "team"'s "worthiness" unless it was stated that he is working with them. On a side note, just because you see a "team" that claims to have a jailbreak for 6.0 does not mean they are legitimate. I now looked the team up and it is legitimate, so again, my apologies. --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 01:08, 27 January 2013 (UTC)

Baseband Device

2013-01-01T08:09:11Z

Markcoker:

This is the device in the iPhone that manages all the functions which require an antenna. The baseband processor has its own RAM and firmware in NOR flash, separate from the [[ARM]] core resources. The baseband is a resource to the OS. The Wi-Fi and Bluetooth are managed by the main CPU, although the baseband stores their MAC addresses in its NVRAM.

The [[M68ap|iPhone]]'s baseband processor is the [[S-Gold 2]]. The [[N82ap|iPhone 3G]], the [[N88ap|iPhone 3GS]] and the [[K48ap|iPad]] make use of the [[X-Gold 608]] chip for this purpose. The [[N90ap|iPhone 4 (GSM)]] and [[K94ap|iPad 2 (GSM)]] use the [[XMM 6180]], while the [[N92ap|iPhone 4 (CDMA)]] uses the [[MDM6600]] and the [[N94ap|iPhone 4S]] uses the [[MDM6610]]

You can check some [[Baseband Commands]].

==[[Seczone]]==
This is the area in the baseband where the lock state is stored.

===Layout===
0x400--NCK token
0xA00--IMEI signature
0xB00--IMEI
0xC00--Locks table

===Encryption===
Many of the sections are encrypted using [[Baseband TEA Keys|TEA]] based off the [[CHIPID]] and [[NORID]]. See [[NCK Brute Force]] for more info.

==Exploits==
* [[SIM hacks]]

===[[S-Gold 2]]===
* [[Fakeblank]]
* [[IPSF]]
* [[Minus 0x400]]
* [[Minus 0x20000 with Back Extend Erase]]

===[[X-Gold 608]]===
* [[JerrySIM]]
* [[AT+stkprof]]
* [[AT+XLOG Vulnerability]]
* [[AT+XEMN Heap Overflow]]
* [[AT+XAPP Vulnerability]]

===[[XMM 6180]]===
* [[AT+XAPP Vulnerability]]

===[[MDM6600]]===
* none right now

===[[MDM6610]]===
* none right now

===[[MDM9615]]===
* none right now

==Theoretical Attacks==
* [[NCK Brute Force]]
* [[Baseband JTAG]]

==Boot Chain==
[[Baseband Bootrom|bootrom]]->[[Baseband Bootloader|bootloader]]->[[Baseband Firmware|firmware]]

[[Category:Baseband]]

Talk:Fuzzyband Downgrader

2011-09-27T13:53:11Z

Markcoker: Created page with "What is the current process when iphone upgrades its baseband with an iphone update? What is the security envoled in stopping a downgrade. What is required to be able to downgrad..."

What is the current process when iphone upgrades its baseband with an iphone update?
What is the security envoled in stopping a downgrade. What is required to be able to downgrade a baseband. (and an another noob question i guess, what would be required to load a custom baseband, is it possible/has it been done).

Fuzzyband Downgrader

2011-09-27T13:48:54Z

Markcoker: Added for information

3G Fuzzyband Downgrader detects your bootloader and baseband and downgrade it with a simple click. Fuzzyband will downgrade any baseband from 2.30 to 4.26.08 (beta 5). This GUI Baseband Downgrader was created by w1kedZ (coding) & DHowett (GUI). It is based on the exploit in the 5.08 bootloader found by geohotz.

Talk:DFU Mode

2011-09-27T08:31:14Z

Markcoker:

failsafe thing was made up by zibri, his point was you can always downgrade to 1.1.4, but it is really officially known as Device Firmware Upgrade by '''the people actually invented it :P'''

== drg ==
Contradiction... can or cannot exit DFU without restore??
:Can exit no problem ~geohot
::Method one and method two are the same. ~geohot
:::Thought so. Cleaned. -drg
Hi all, please can someone make a utility to take iPhone into DFU. Or do someone know howto take iPhone into DFU without using Sleep button? ~ makovice
:Please read the original article, It is not possible --[[User:JacobVengeance|JakeAnthraX]] 10:01, 17 November 2010 (UTC)
:It is possible but your iDevice will go into a DFU Loop. --[[User:Whiteshinyapple|Whiteshinyapple]] 18:10, 19 November 2010 (GMT +8)
:Thanks for your interactions. I'll suggest repair the button ;) (DFU Loop I tried, but without success - iTunes refused modified firmware) -- makovice
:iTunes will error out and if your iphone is in a black screen then it is in dfu mode. -- Whiteshinyapple
:Yeh I know, but it doesn't even start restore (iPhone didn't make anything), so did anyone try it with 4.1 iOS and iTunes 10.1?? -- Makovice
::well the way i did it was used [[PwnageTool]] or [[redsn0w]] to enter pwn [[DFU Mode]] (tested this on 4.0 because i don't have SHSH for it) then without unzipping the .ipsw (this is important because it will not be recognised by itunes if unzipped) removed the build manifest then restore and it will give you error 10 and every reboot it will be in dfu mode however if you are wanting to save the data in your device it is impossible because the bootchain is flashed at the end of a restore --[[User:Liamchat|liamchat]] 16:00, 22 November 2010 (UTC)
::ok, only one thing ... how can I change conent without unzipping? :) -- Makovice
:::i used http://www.stuffit.com/mac-home.html --[[User:Liamchat|liamchat]] 16:52, 22 November 2010 (UTC)
:::any zip program. Winzip winrar peazip anything just view the file on the program and delete the file like in explorer or finder... --[[User:Balloonhead66|Balloonhead66]] 17:36, 22 November 2010 (UTC)
:Ill be creating a video on how to create a DFU Loop IPSW.[http://www.youtube.com/sn0wra1n My Youtube] --[[User:sn0wra1n|sn0wra1n]]
::on an intresting note it may be posible to make a dongle to boot the device ( like [http://wikee.iphwn.org/howto:ipt2g_dongle_prep]) but when [[redns0w]] boot's tethered it inject's big file's and the ipod 4g has a void in it so the dongle will not be visible --[[User:Liamchat|liamchat]] 18:11, 25 November 2010 (UTC)

== Reverse engineer ==
Okay, so, we know that [[iTunes]] puts the iDevice into DFU mode when the device is upgrading/downgrading/restoring. How does [[iTunes]] do this? It certainly doesn't require us to press and hold the home/sleep buttons. How do we reverse iTunes' mechanism to put devices into DFU mode WITHOUT creating a DFU loop? --[[User:Rdqronos|rdqronos]] 12:26, July 1, 2011 (UTC)
:No one but Apple has the source code. I guess you could attach a debuger to the USB port (if there is one that does that) and monitor the data sent out of it. --[[User:Balloonhead66|Balloonhead66]] 15:09, 1 July 2011 (UTC)
:OMG iPhone knowledge is slipping fast. Updates are done in recovery mode, not DFU mode. blackra1n will happily enter recovery mode for you. There's no (easy) way in qsoftware to get into DFU, although a half baked flash to brick could probably do it. --[[User:Geohot|geohot]] 00:16, 2 July 2011 (UTC)
:I did not know that... You're right, iPhone knowledge IS slipping fast. That's why I come here. Also, there is evidently an easy way in software, we just haven't found it yet. Balloonhead did have the good idea, using a USB debugger of some sort to monitor all traffic sent to/from the iPhone. Sorry if I sound like a douche :P --[[User:Rdqronos|rdqronos]] 02:50, 2 July 2011 (UTC)
:stop bullshitting about dfu and stuff, much love, qwertyoruiop. you can't via software. also lulz at usb debugger. it's called sniffing and it's kinda funny. --[[User:Qwertyoruiop|Qwertyoruiop]] 23:50, 2 July 2011 (UTC)
:As Geohot said, DFU mode can be entered when iPhone is "bricked". That state can be achieved by, for example, inserting random crap into NOR (DO NOT DO THIS! I tested that on iPhone1,1 in 2009, I don't know how other devices behave in such situations, but it's probably the same). --pjakuszew 14:38, 3 July 2011 (UTC)
:Hmm... So basically, screw around with a 4.3 ipsw for a bit? --[[User:Rdqronos|rdqronos]] 15:57, 3 July 2011 (UTC)
::You can try. I was doing everything from OpeniBoot. If you just mess with LLB file, iTunes will probably spit out an error before flashing a modified file. --pjakuszew 21:10, 3 July 2011 (UTC)
::Dontcha love messing with stuff? Also, can i install openiboot on my i4? thanks man. --[[User:Rdqronos|rdqronos]] 22:18, 3 July 2011 (UTC)
:::I'd just press those buttons, damn it's 20 seconds it's not like your whole life. But yea, screw up the LLB to enjoy (semi)software based DFU. --[[User:Qwertyoruiop|Qwertyoruiop]] 01:08, 5 July 2011 (UTC)

== Disabling DFU ==

As a general question, would it be possible for Apple to disable DFU mode completely with a software update? I know it would be possible to do it with refreshed hardware.
--[[User:Rdqronos|rdqronos]] 15:05, 26 September 2011 (MDT)
:No. This is in the bootrom to reinstall firmware even without any software installed. Without DFU Mode: How would Apple install the firmware the first time? And what would users do that have disconnected their phone in the middle of an update? I don't see any reason to remove this mode even in new hardware. -- [[User:Http|http]] 15:18, 26 September 2011 (MDT)
Updates are done in recovery mode.
"I know it would be possible to do it with refreshed hardware." well if you know it to be possible without hardware being refresh doesn't that mean.. the only other options is via software update?.
"I don't see any reason to remove this mode even in new hardware." i agree, its highly unlikely in my mind they will remove it, for at least in the next few years imho.
--[[User:Markcoker|Blue Skies]] 02:31, 27 September 2011 (MDT)

ITunes Errors/Below 100

2011-09-20T07:00:22Z

Markcoker: /* Error 20 */

=== Error 1 ===

* You are attempting to downgrade an iPhone from iOS 5 to iOS 4.x. To resolve, use either custom firmware created by [[PwnageTool]]/[[sn0wbreeze]] or use [[User:semaphore|notcom]]'s [[FixRecovery]] utility available on [http://thefirmwareumbrella.blogspot.com his site].
* On an [[iPhone 4]] downgrading from iOS 5, use the option in [[TinyUmbrella]] to allow a baseband "upgrade" to bypass the error and go back to basband [[4.10.1]].
* Unable to downgrade. Try changing the USB port (the back one of chassis is better) and restart computer.
* The installed version of [[iTunes]] may also be too old. Update iTunes.

=== Error 2 ===
* ASR does not exist on ramdisk or is corrupt/not signed.
* [[sn0wbreeze]] 1.6 Custom Firmware has a [[ASR]] patch problem. Use [[sn0wbreeze]] 1.7+ or [[PwnageTool]]. Device isn't bootable.

=== Error 6 ===
Not enter the downgrading mode, change USB port (the back one of chassis is better) and restart computer.

=== Error 9 ===
* Due to asr being patched, the SHA signature is automatically changed and after being resigned the kernel will refuse to use it. Therefore proper kernel patches are required. If necessary kernel patches are not applied, it will fail to load asr and error 9 would occur during restore.
* Rebooting your Mac or PC may resolve this issue.

=== Error 10 ===
[[LLB]] is missing from the [[IPSW File Format|IPSW]]. The device cannot be booted up. The trick to skip the baseband update no longer works.

=== Error 11 ===
* Removed [[Baseband|BB]]<nowiki />FW file in the firmware folder of an unzipped [[IPSW File Format|IPSW]]. Can also be used to prevent a baseband update. The device is bootable, if you set the auto-boot to true or use TinyUmbrella and use "Kick Device out of Recovery".
* You are trying to update to a custom firmware from [[PwnageTool]] 4.1+. You always have to go into DFU mode and restore from there.

=== Error 13 ===
* Occurs when you want to install a beta firmware with [[iTunes]] for Windows (actively blocked by Apple; beta users are developers and therefore must have a Mac).
* USB problem. Check the USB connection and try other direct ports or maybe the USB cable is an older one. Device isn't bootable.
* The installed version of [[iTunes]] may also be too old. For firmwares 4.0 and higher you need iTunes 9.2 or higher. Update iTunes.

=== Error 14 ===
* Custom firmware update fail ([[PwnageTool]] until 4.0.1). You have to restore the device with a custom firmware. Update to a custom firmware isn't working. Device isn't bootable. 2
* USB Problem. Check the USB connection and try other direct ports or maybe the USB cable is an older one. Device isn't bootable.
* You're trying to 'update' to a [[Beta Firmware|beta firmware]] instead of performing a restore. Device is still bootable if you kick it out of recovery mode.
* Rebooting your Mac or PC may resolve this issue.

=== Error 17 ===
* Device failed to display the applelogo img3 which results in this error.
* One or more of the nand0/nor0 flash images were missing from the IPSW.

=== Error 18 ===
This occurs when the media library on the device is corrupt and cannot be modified or updated.

Updating to the latest version of iTunes and then restoring should resolve this issue

=== Error 20 ===
Error when downgrading 2.0 to 1.1.1.
I've also received this error ios5 -> 4.33 (3gs oldBB using cydia)

=== Error 21 ===
Custom firmware restore fail ([[PwnageTool]] since 4.1). You have to put your device into the DFU mode and not into recovery mode. Device won't boot correctly an stuck at the Apple logo after the error. Press and hold power and home button until it reboots.

=== Error 23 ===
Cannot restore or update due to hardware problems.
* In software you have to set default web browser.
* In hardware, it's a communication problem. Check all connections, also try to change battery.
* Faulty [[baseband]] flash or processor
* Happens frequently after water damage. Remove and clean motherboard.

=== Error 26 ===
* Values or variables in the options property list within the ramdisk are incorrect.
* False version of the [[NOR]] flash firmware. Use the correct [[sn0wbreeze]] version.

=== Error 28 ===
* Hardware error. Return your device to Apple if possible. The problem is a bad dock connector on the iPhone. Must change the connector.
* If you have tried almost everything, reset the logic board (leave uncharged for five days or remove battery for half an hour), then pwn and restore. If this doesn't work, the {{wp|flash memory}}/{{wp|hard drive}} of your device is damaged.

=== Error 29 ===
See [http://discussions.apple.com/ Apple's discussion thread] number [http://discussions.apple.com/thread.jspa?threadID=2329795 2329795] about this problem. You might need to change the battery.

=== Error 31 ===
{{main|DFU Loop}}

=== Error 34 ===
Hard disk is run out of space when trying to download. Clear space and then continue downloading.

=== Error 37 ===
* [[N72ap|iPod touch 2G]] [[LLB]] patched with the [[0x24000 Segment Overflow]] was used on an [[N88ap|iPhone 3GS]] custom firmware. Known on damaged bundles from unofficial [[PwnageTool]] distributions or bundles.
* [[sn0wbreeze]] 2.0.1 bug, which was fixed in 2.0.2.
* Recent [[sn0wbreeze]] can cause this issue. Deselect all custom boot logos, recreate [[IPSW File Format|IPSW]]. If received on an [[N88ap|iPhone 3GS]], select "new boot-rom" and deselect all custom bootlogos, then recreate the [[IPSW File Format|IPSW]].

=== Error 40 ===
Hacktivation bug in [[Sn0wbreeze]] 2.0.1, which was fixed in [[Sn0wbreeze]] 2.0.2.

=== Error 46 ===
?

Talk:IRecovery

2011-08-22T13:20:24Z

Markcoker:

== Including forks of iRecovery? ==
Wouldn't it be an idea to include the various forks of iRecovery? p0sixninja have made one and so has GreySyntax (Jordan). Jordan is even doing an iRecovery++. Westbaer's version haven't been updated since July 2009 whereas the others have been updated just a day or two ago. [[User:Josso|Josso]] 09:22, 10 May 2010 (UTC)

== Supported Raw Commands ==

A list of raw commands supported by each firmware and short description i think would be great. Most likely in table format if big enough, maybe a page for them if there is too many for this page.
--[[User:Markcoker|Blue Skies]] 15:31, 18 August 2011 (MDT)
:This kind of list belongs to iBoot page IMO. iRecovery is just an interface that sends everything you type to the device and doesn't contain any commands by itself. Also, Apple doesn't include any useful commands besides reboot, setenv and some others in RELEASE-type iBoots from 4.x onwards, so it could only serve historic purpose, I guess --pjakuszew 16:32, 18 August 2011 (MDT)
::Ok great can we add this to iboot page then, with a discription then. I agree it doesn't belong here (Not that it hurts maybe should still have a link to this info though) some examples ive found(below). are they all still working.. what are they used for, are there more (im sure there is) i think alot of people want to know about this information.--[[User:Markcoker|Blue Skies]] 05:14, 19 August 2011 (MDT)

setenv boot-device nand0
setenv boot-partition 0
setenv boot-path /System/Library/Caches/com.apple.kernelcaches/kernelcache.s5l8900xrb
setenv boot-file nand0:0,/System/Library/Caches/com.apple.kernelcaches/kernelcache.s5l8900xrb
setenv boot-command fsboot
setenv display-color-space RGB888
setenv display-timing opt
setenv config_board m68ap
setenv boot delay
setenv auto-boot true
saveenv

:These are actually environment variables, not commands by itself. They are stored in NVRAM, think of it as a very simplified version of Windows registry. <code>boot-device</code>, <code>boot-partition</code> and <code>boot-path</code> are used for locating the kernel cache file. <code>boot-command</code> is the default command to execute if boot countdown is not interrupted. <code>boot-delay</code> is the delay for executing the boot-command. <code>auto-boot</code> is the variable that can be used to enable and disable automatic booting. If you set it to false, your device won't boot into iOS, but instead go into recovery mode. --pjakuszew 05:50, 19 August 2011 (MDT) 

::Thanks for formatting :D, great information. Is there a way to display environment variables, or is there information on the defaults used and other parameters you can set. --[[User:Markcoker|Blue Skies]] 07:19, 22 August 2011 (MDT)

Talk:IRecovery

2011-08-22T13:19:45Z

Markcoker:

== Including forks of iRecovery? ==
Wouldn't it be an idea to include the various forks of iRecovery? p0sixninja have made one and so has GreySyntax (Jordan). Jordan is even doing an iRecovery++. Westbaer's version haven't been updated since July 2009 whereas the others have been updated just a day or two ago. [[User:Josso|Josso]] 09:22, 10 May 2010 (UTC)

== Supported Raw Commands ==

A list of raw commands supported by each firmware and short description i think would be great. Most likely in table format if big enough, maybe a page for them if there is too many for this page.
--[[User:Markcoker|Blue Skies]] 15:31, 18 August 2011 (MDT)
:This kind of list belongs to iBoot page IMO. iRecovery is just an interface that sends everything you type to the device and doesn't contain any commands by itself. Also, Apple doesn't include any useful commands besides reboot, setenv and some others in RELEASE-type iBoots from 4.x onwards, so it could only serve historic purpose, I guess --pjakuszew 16:32, 18 August 2011 (MDT)
::Ok great can we add this to iboot page then, with a discription then. I agree it doesn't belong here (Not that it hurts maybe should still have a link to this info though) some examples ive found(below). are they all still working.. what are they used for, are there more (im sure there is) i think alot of people want to know about this information.

setenv boot-device nand0
setenv boot-partition 0
setenv boot-path /System/Library/Caches/com.apple.kernelcaches/kernelcache.s5l8900xrb
setenv boot-file nand0:0,/System/Library/Caches/com.apple.kernelcaches/kernelcache.s5l8900xrb
setenv boot-command fsboot
setenv display-color-space RGB888
setenv display-timing opt
setenv config_board m68ap
setenv boot delay
setenv auto-boot true
saveenv
--[[User:Markcoker|Blue Skies]] 05:14, 19 August 2011 (MDT)
:These are actually environment variables, not commands by itself. They are stored in NVRAM, think of it as a very simplified version of Windows registry. <code>boot-device</code>, <code>boot-partition</code> and <code>boot-path</code> are used for locating the kernel cache file. <code>boot-command</code> is the default command to execute if boot countdown is not interrupted. <code>boot-delay</code> is the delay for executing the boot-command. <code>auto-boot</code> is the variable that can be used to enable and disable automatic booting. If you set it to false, your device won't boot into iOS, but instead go into recovery mode. --pjakuszew 05:50, 19 August 2011 (MDT) 
::Thanks for formatting :D, great information. Is there a way to display environment variables, or is there information on the defaults used and other parameters you can set.
--[[User:Markcoker|Blue Skies]] 07:19, 22 August 2011 (MDT)

Talk:IRecovery

2011-08-22T13:19:10Z

Markcoker:

== Including forks of iRecovery? ==
Wouldn't it be an idea to include the various forks of iRecovery? p0sixninja have made one and so has GreySyntax (Jordan). Jordan is even doing an iRecovery++. Westbaer's version haven't been updated since July 2009 whereas the others have been updated just a day or two ago. [[User:Josso|Josso]] 09:22, 10 May 2010 (UTC)

== Supported Raw Commands ==

A list of raw commands supported by each firmware and short description i think would be great. Most likely in table format if big enough, maybe a page for them if there is too many for this page.
--[[User:Markcoker|Blue Skies]] 15:31, 18 August 2011 (MDT)
:This kind of list belongs to iBoot page IMO. iRecovery is just an interface that sends everything you type to the device and doesn't contain any commands by itself. Also, Apple doesn't include any useful commands besides reboot, setenv and some others in RELEASE-type iBoots from 4.x onwards, so it could only serve historic purpose, I guess --pjakuszew 16:32, 18 August 2011 (MDT)
::Ok great can we add this to iboot page then, with a discription then. I agree it doesn't belong here (Not that it hurts maybe should still have a link to this info though) some examples ive found(below). are they all still working.. what are they used for, are there more (im sure there is) i think alot of people want to know about this information.

setenv boot-device nand0
setenv boot-partition 0
setenv boot-path /System/Library/Caches/com.apple.kernelcaches/kernelcache.s5l8900xrb
setenv boot-file nand0:0,/System/Library/Caches/com.apple.kernelcaches/kernelcache.s5l8900xrb
setenv boot-command fsboot
setenv display-color-space RGB888
setenv display-timing opt
setenv config_board m68ap
setenv boot delay
setenv auto-boot true
saveenv
--[[User:Markcoker|Blue Skies]] 05:14, 19 August 2011 (MDT)
:These are actually environment variables, not commands by itself. They are stored in NVRAM, think of it as a very simplified version of Windows registry. <code>boot-device</code>, <code>boot-partition</code> and <code>boot-path</code> are used for locating the kernel cache file. <code>boot-command</code> is the default command to execute if boot countdown is not interrupted. <code>boot-delay</code> is the delay for executing the boot-command. <code>auto-boot</code> is the variable that can be used to enable and disable automatic booting. If you set it to false, your device won't boot into iOS, but instead go into recovery mode. --pjakuszew 05:50, 19 August 2011 (MDT)
::Thanks for formatting :D, great information. Is there a way to display environment variables, or is there information on the defaults used and other parameters you can set.

IRecovery

2011-08-20T07:34:24Z

Markcoker: /* Supported Raw Commands */

{{DISPLAYTITLE:iRecovery}}
iRecovery is a libusb-based CLI utility for Mac OS X, Linux, and Windows. It is able to talk to [[iBoot (Bootloader)|iBoot]] and [[iBSS]] via USB. It's completely open source; the source code is released under the terms of the GNU GPL v3. The full license text can be found in the LICENSE file on github.

It currently connects to:
* [[DFU 0x1227|0x1227]] ([[DFU Mode]]/[[WTF]] Mode 2.0)
* [[Recovery Mode (Protocols)#Recovery_Mode_2.x_.28DevID.3D0x1281.29|Recovery Mode 0x1281]] (Recovery Mode/iBSS)

==Credits==
westbaer

==Thanks==
[[User:Pod2g|pod2g]], [[tom3q]], [[User:Planetbeing|planetbeing]], [[User:Geohot|geohot]] and [[User:posixninja|posixninja]].

==Features==

===DFU 2.0 (0x1227)===
It can upload a file, such as an [[iBSS]], so that you can unplug and spawn a shell with 0x1281.

===Recovery 2.0 (0x1281)===
====File Uploading====
You can upload a file to 0x9000000 with the following syntax:
./iRecovery -f file
In newer builds that use libusb-1.0 this is now
./iRecovery -u file

====Two-Way Shell====
You can spawn a shell to do all sorts of neat things with the syntax:
./iRecovery -s
Once it has spawned, you can type 'help' and iBoot will respond with its built-in command list.

====Single Command====
./iRecovery -c "command"
Sends a single command to the device *without* spawning a shell.

====usb_control_msg(0x21, 2) Exploit Command====
./iRecovery -k
Sends Chronic Dev's + Geohot's latest usb exploit. Implemented into blackra1n.
This was updated near October 17, 2009. [http://github.com/posixninja/irecovery posixninja's fork]
In newer builds this is now -e

====Auto Boot====
You can now enable auto-boot by running:
./iRecovery -a
or by sending /auto-boot in a shell.

====USB Reset====
Reset USB
./iRecovery -r

====Batch Scripting====
iRecovery now supports batch scripting, this allows you to send commands to iBoot from a pre written list of commands, this also suports scripting such as /auto-boot and /upload <file>
./iRecovery -b <file>
or in a shell:
/batch <file>

====Raw Commands====
You can now send raw commands via the -x21 -x40 or -xA1 flags

==Example Output==

iRecovery -s
======================================
::
:: iBSS for n82ap, Copyright 2009, Apple Inc.
::
:: BUILD_TAG: iBoot-596.24
::
:: BUILD_STYLE: RELEASE
::
:: USB_SERIAL_NUMBER: CPID:8900 CPRV:30 CPFM:03 SCEP:05 BDID:04 ECID:000003293C113D76 IBFL:00
::
=======================================

Entering recovery mode, starting command prompt
] printenv
build-style = "RELEASE"
build-version = "iBoot-596.24"
config_board = "n82ap"
loadaddr = "0x9000000"
boot-command = "fsboot"
bootdelay = "0"
auto-boot = "true"
idle-off = "true"
boot-device = "nand0"
boot-partition = "0"
boot-path = "/System/Library/Caches/com.apple.kernelcaches/kernelcache.s5l8900x"
display-color-space = "RGB888"
display-timing = "optC"
framebuffer = "0xfd00000"
secure-boot = "0x1"

== Supported Raw Commands ==

Currently Supported by All Firmware: 
Reboot - Reboots Iphone

More IBoot Commands Information: 
http://code.google.com/p/chronicdev/wiki/iBootCommands

==Forks==
[http://github.com/iH8sn0w/irecovery iH8sn0w/irecovery]

[http://github.com/GreySyntax/irecovery GreySyntax/irecovery]

==Updates==
A C++ port is also in the works dubbed iRecovery++ (by [[User:GreySyntax|GreySyntax]]). [http://github.com/NSPwn/iRecoveryplusplus]]

A VB.NET port (by [[User:Fallensn0w|Fallensn0w]] )can be found at [http://github.com/fallensn0w/vbiRecovery vbiRecovery]

A GUI (Graphical User Interface) has been made for Windows under the name [[GiRecovery|Zeratul]] and it's developed by [[User:Fallensn0w|Fallensn0w]] and available at [http://github.com/fallensn0w/Zeratul @github]
(or compiled binary files [http://fallensn0w.host22.com here].)

==Download==
[http://github.com/chronicdev/libirecovery Offical Repository (Maintained) / Download here]
[http://www.mediafire.com/?nmn25bnjzy3 Win32 binary]

[[Category:Hacking Software]]

IRecovery

2011-08-20T07:34:03Z

Markcoker: /* Supported Raw Commands */

{{DISPLAYTITLE:iRecovery}}
iRecovery is a libusb-based CLI utility for Mac OS X, Linux, and Windows. It is able to talk to [[iBoot (Bootloader)|iBoot]] and [[iBSS]] via USB. It's completely open source; the source code is released under the terms of the GNU GPL v3. The full license text can be found in the LICENSE file on github.

It currently connects to:
* [[DFU 0x1227|0x1227]] ([[DFU Mode]]/[[WTF]] Mode 2.0)
* [[Recovery Mode (Protocols)#Recovery_Mode_2.x_.28DevID.3D0x1281.29|Recovery Mode 0x1281]] (Recovery Mode/iBSS)

==Credits==
westbaer

==Thanks==
[[User:Pod2g|pod2g]], [[tom3q]], [[User:Planetbeing|planetbeing]], [[User:Geohot|geohot]] and [[User:posixninja|posixninja]].

==Features==

===DFU 2.0 (0x1227)===
It can upload a file, such as an [[iBSS]], so that you can unplug and spawn a shell with 0x1281.

===Recovery 2.0 (0x1281)===
====File Uploading====
You can upload a file to 0x9000000 with the following syntax:
./iRecovery -f file
In newer builds that use libusb-1.0 this is now
./iRecovery -u file

====Two-Way Shell====
You can spawn a shell to do all sorts of neat things with the syntax:
./iRecovery -s
Once it has spawned, you can type 'help' and iBoot will respond with its built-in command list.

====Single Command====
./iRecovery -c "command"
Sends a single command to the device *without* spawning a shell.

====usb_control_msg(0x21, 2) Exploit Command====
./iRecovery -k
Sends Chronic Dev's + Geohot's latest usb exploit. Implemented into blackra1n.
This was updated near October 17, 2009. [http://github.com/posixninja/irecovery posixninja's fork]
In newer builds this is now -e

====Auto Boot====
You can now enable auto-boot by running:
./iRecovery -a
or by sending /auto-boot in a shell.

====USB Reset====
Reset USB
./iRecovery -r

====Batch Scripting====
iRecovery now supports batch scripting, this allows you to send commands to iBoot from a pre written list of commands, this also suports scripting such as /auto-boot and /upload <file>
./iRecovery -b <file>
or in a shell:
/batch <file>

====Raw Commands====
You can now send raw commands via the -x21 -x40 or -xA1 flags

==Example Output==

iRecovery -s
======================================
::
:: iBSS for n82ap, Copyright 2009, Apple Inc.
::
:: BUILD_TAG: iBoot-596.24
::
:: BUILD_STYLE: RELEASE
::
:: USB_SERIAL_NUMBER: CPID:8900 CPRV:30 CPFM:03 SCEP:05 BDID:04 ECID:000003293C113D76 IBFL:00
::
=======================================

Entering recovery mode, starting command prompt
] printenv
build-style = "RELEASE"
build-version = "iBoot-596.24"
config_board = "n82ap"
loadaddr = "0x9000000"
boot-command = "fsboot"
bootdelay = "0"
auto-boot = "true"
idle-off = "true"
boot-device = "nand0"
boot-partition = "0"
boot-path = "/System/Library/Caches/com.apple.kernelcaches/kernelcache.s5l8900x"
display-color-space = "RGB888"
display-timing = "optC"
framebuffer = "0xfd00000"
secure-boot = "0x1"

== Supported Raw Commands ==

Currently Supported by All Firmware: 
Reboot - Reboots Iphone

More Iboot Commands Information: 
http://code.google.com/p/chronicdev/wiki/iBootCommands

==Forks==
[http://github.com/iH8sn0w/irecovery iH8sn0w/irecovery]

[http://github.com/GreySyntax/irecovery GreySyntax/irecovery]

==Updates==
A C++ port is also in the works dubbed iRecovery++ (by [[User:GreySyntax|GreySyntax]]). [http://github.com/NSPwn/iRecoveryplusplus]]

A VB.NET port (by [[User:Fallensn0w|Fallensn0w]] )can be found at [http://github.com/fallensn0w/vbiRecovery vbiRecovery]

A GUI (Graphical User Interface) has been made for Windows under the name [[GiRecovery|Zeratul]] and it's developed by [[User:Fallensn0w|Fallensn0w]] and available at [http://github.com/fallensn0w/Zeratul @github]
(or compiled binary files [http://fallensn0w.host22.com here].)

==Download==
[http://github.com/chronicdev/libirecovery Offical Repository (Maintained) / Download here]
[http://www.mediafire.com/?nmn25bnjzy3 Win32 binary]

[[Category:Hacking Software]]

IRecovery

2011-08-20T07:33:38Z

Markcoker: /* Supported Raw Commands */

{{DISPLAYTITLE:iRecovery}}
iRecovery is a libusb-based CLI utility for Mac OS X, Linux, and Windows. It is able to talk to [[iBoot (Bootloader)|iBoot]] and [[iBSS]] via USB. It's completely open source; the source code is released under the terms of the GNU GPL v3. The full license text can be found in the LICENSE file on github.

It currently connects to:
* [[DFU 0x1227|0x1227]] ([[DFU Mode]]/[[WTF]] Mode 2.0)
* [[Recovery Mode (Protocols)#Recovery_Mode_2.x_.28DevID.3D0x1281.29|Recovery Mode 0x1281]] (Recovery Mode/iBSS)

==Credits==
westbaer

==Thanks==
[[User:Pod2g|pod2g]], [[tom3q]], [[User:Planetbeing|planetbeing]], [[User:Geohot|geohot]] and [[User:posixninja|posixninja]].

==Features==

===DFU 2.0 (0x1227)===
It can upload a file, such as an [[iBSS]], so that you can unplug and spawn a shell with 0x1281.

===Recovery 2.0 (0x1281)===
====File Uploading====
You can upload a file to 0x9000000 with the following syntax:
./iRecovery -f file
In newer builds that use libusb-1.0 this is now
./iRecovery -u file

====Two-Way Shell====
You can spawn a shell to do all sorts of neat things with the syntax:
./iRecovery -s
Once it has spawned, you can type 'help' and iBoot will respond with its built-in command list.

====Single Command====
./iRecovery -c "command"
Sends a single command to the device *without* spawning a shell.

====usb_control_msg(0x21, 2) Exploit Command====
./iRecovery -k
Sends Chronic Dev's + Geohot's latest usb exploit. Implemented into blackra1n.
This was updated near October 17, 2009. [http://github.com/posixninja/irecovery posixninja's fork]
In newer builds this is now -e

====Auto Boot====
You can now enable auto-boot by running:
./iRecovery -a
or by sending /auto-boot in a shell.

====USB Reset====
Reset USB
./iRecovery -r

====Batch Scripting====
iRecovery now supports batch scripting, this allows you to send commands to iBoot from a pre written list of commands, this also suports scripting such as /auto-boot and /upload <file>
./iRecovery -b <file>
or in a shell:
/batch <file>

====Raw Commands====
You can now send raw commands via the -x21 -x40 or -xA1 flags

==Example Output==

iRecovery -s
======================================
::
:: iBSS for n82ap, Copyright 2009, Apple Inc.
::
:: BUILD_TAG: iBoot-596.24
::
:: BUILD_STYLE: RELEASE
::
:: USB_SERIAL_NUMBER: CPID:8900 CPRV:30 CPFM:03 SCEP:05 BDID:04 ECID:000003293C113D76 IBFL:00
::
=======================================

Entering recovery mode, starting command prompt
] printenv
build-style = "RELEASE"
build-version = "iBoot-596.24"
config_board = "n82ap"
loadaddr = "0x9000000"
boot-command = "fsboot"
bootdelay = "0"
auto-boot = "true"
idle-off = "true"
boot-device = "nand0"
boot-partition = "0"
boot-path = "/System/Library/Caches/com.apple.kernelcaches/kernelcache.s5l8900x"
display-color-space = "RGB888"
display-timing = "optC"
framebuffer = "0xfd00000"
secure-boot = "0x1"

== Supported Raw Commands ==

Currently Supported by All Firmware: 
Reboot - Reboots Iphone

More Iboot Commands: 
http://code.google.com/p/chronicdev/wiki/iBootCommands

==Forks==
[http://github.com/iH8sn0w/irecovery iH8sn0w/irecovery]

[http://github.com/GreySyntax/irecovery GreySyntax/irecovery]

==Updates==
A C++ port is also in the works dubbed iRecovery++ (by [[User:GreySyntax|GreySyntax]]). [http://github.com/NSPwn/iRecoveryplusplus]]

A VB.NET port (by [[User:Fallensn0w|Fallensn0w]] )can be found at [http://github.com/fallensn0w/vbiRecovery vbiRecovery]

A GUI (Graphical User Interface) has been made for Windows under the name [[GiRecovery|Zeratul]] and it's developed by [[User:Fallensn0w|Fallensn0w]] and available at [http://github.com/fallensn0w/Zeratul @github]
(or compiled binary files [http://fallensn0w.host22.com here].)

==Download==
[http://github.com/chronicdev/libirecovery Offical Repository (Maintained) / Download here]
[http://www.mediafire.com/?nmn25bnjzy3 Win32 binary]

[[Category:Hacking Software]]

Talk:IRecovery

2011-08-19T11:21:59Z

Markcoker: --~~~~

Talk:IRecovery

2011-08-19T11:15:09Z

Markcoker: /* Supported Raw Commands */

Talk:IRecovery

2011-08-19T11:14:47Z

Markcoker: /* Supported Raw Commands */

Talk:IRecovery

2011-08-19T11:14:29Z

Markcoker: /* Supported Raw Commands */

Talk:IRecovery

2011-08-18T21:31:51Z

Markcoker: /* Supported Raw Commands */ --BlueSkies

Talk:IRecovery

2011-08-18T21:29:39Z

Markcoker: /* Supported Raw Commands */ new section

IRecovery

2011-08-18T08:35:08Z

Markcoker: Raw Commands --BlueSkies

{{DISPLAYTITLE:iRecovery}}
iRecovery is a libusb-based CLI utility for Mac OS X, Linux, and Windows. It is able to talk to [[iBoot (Bootloader)|iBoot]] and [[iBSS]] via USB. It's completely open source; the source code is released under the terms of the GNU GPL v3. The full license text can be found in the LICENSE file on github.

It currently connects to:
* [[DFU 0x1227|0x1227]] ([[DFU Mode]]/[[WTF]] Mode 2.0)
* [[Recovery Mode (Protocols)#Recovery_Mode_2.x_.28DevID.3D0x1281.29|Recovery Mode 0x1281]] (Recovery Mode/iBSS)

==Credits==
westbaer

==Thanks==
[[User:Pod2g|pod2g]], [[tom3q]], [[User:Planetbeing|planetbeing]], [[User:Geohot|geohot]] and [[User:posixninja|posixninja]].

==Features==

===DFU 2.0 (0x1227)===
It can upload a file, such as an [[iBSS]], so that you can unplug and spawn a shell with 0x1281.

===Recovery 2.0 (0x1281)===
====File Uploading====
You can upload a file to 0x9000000 with the following syntax:
./iRecovery -f file
In newer builds that use libusb-1.0 this is now
./iRecovery -u file

====Two-Way Shell====
You can spawn a shell to do all sorts of neat things with the syntax:
./iRecovery -s
Once it has spawned, you can type 'help' and iBoot will respond with its built-in command list.

====Single Command====
./iRecovery -c "command"
Sends a single command to the device *without* spawning a shell.

====usb_control_msg(0x21, 2) Exploit Command====
./iRecovery -k
Sends Chronic Dev's + Geohot's latest usb exploit. Implemented into blackra1n.
This was updated near October 17, 2009. [http://github.com/posixninja/irecovery posixninja's fork]
In newer builds this is now -e

====Auto Boot====
You can now enable auto-boot by running:
./iRecovery -a
or by sending /auto-boot in a shell.

====USB Reset====
Reset USB
./iRecovery -r

====Batch Scripting====
iRecovery now supports batch scripting, this allows you to send commands to iBoot from a pre written list of commands, this also suports scripting such as /auto-boot and /upload <file>
./iRecovery -b <file>
or in a shell:
/batch <file>

====Raw Commands====
You can now send raw commands via the -x21 -x40 or -xA1 flags

==Example Output==

iRecovery -s
======================================
::
:: iBSS for n82ap, Copyright 2009, Apple Inc.
::
:: BUILD_TAG: iBoot-596.24
::
:: BUILD_STYLE: RELEASE
::
:: USB_SERIAL_NUMBER: CPID:8900 CPRV:30 CPFM:03 SCEP:05 BDID:04 ECID:000003293C113D76 IBFL:00
::
=======================================

Entering recovery mode, starting command prompt
] printenv
build-style = "RELEASE"
build-version = "iBoot-596.24"
config_board = "n82ap"
loadaddr = "0x9000000"
boot-command = "fsboot"
bootdelay = "0"
auto-boot = "true"
idle-off = "true"
boot-device = "nand0"
boot-partition = "0"
boot-path = "/System/Library/Caches/com.apple.kernelcaches/kernelcache.s5l8900x"
display-color-space = "RGB888"
display-timing = "optC"
framebuffer = "0xfd00000"
secure-boot = "0x1"

==Supported Raw Commands==
I would like to see a list supported raw commands. "GreySyntax Jordan apple removed most cosmos during the 4.x cycle" So its a hard for new users to know if they are going crazy. Ill get the ball rolling.(correct me if im wrong)

Currently Supported by All Firmware:
Reboot - Reboots Iphone

==Forks==
[http://github.com/iH8sn0w/irecovery iH8sn0w/irecovery]

[http://github.com/GreySyntax/irecovery GreySyntax/irecovery]

==Updates==
A C++ port is also in the works dubbed iRecovery++ (by [[User:GreySyntax|GreySyntax]]). [http://github.com/NSPwn/iRecoveryplusplus]]

A VB.NET port (by [[User:Fallensn0w|Fallensn0w]] )can be found at [http://github.com/fallensn0w/vbiRecovery vbiRecovery]

A GUI (Graphical User Interface) has been made for Windows under the name [[GiRecovery|Zeratul]] and it's developed by [[User:Fallensn0w|Fallensn0w]] and available at [http://github.com/fallensn0w/Zeratul @github]
(or compiled binary files [http://fallensn0w.host22.com here].)

==Download==
[http://github.com/chronicdev/libirecovery Offical Repository (Maintained) / Download here]
[http://www.mediafire.com/?nmn25bnjzy3 Win32 binary]

[[Category:Hacking Software]]

User:Geohot

2011-05-29T18:24:39Z

Markcoker: /* Links */ No longer accepting donations, battle with Sony in court is for now over.

{{lowercase|ns=User:}}
The founder of this wiki.

==Achievements==
* Published the [http://iphonejtag.blogspot.com/2007/08/its-release-time.html first iPhone hardware unlock].
* Published the [http://iphonejtag.blogspot.com/2008/01/112-otb-unlocked.html first iPhone hardware unlock for bootloader 4.6]
* Software unlocked BL 4.6 via [[Minus 0x20000 with Back Extend Erase]].
* Found the [[AT+stkprof]] vulnerability in baseband [[2.28.00]].
* Independently found the [http://iphonejtag.blogspot.com/2009/04/58-exploit.html BL 5.8 exploit].
* Found the [[iBoot Environment Variable Overflow]] exploit.
** Released [[purplera1n]], which used said exploit.
* Released [[purplesn0w]], an [[X-Gold 608]] unlock for [[4.26.08]].
* Independently found the [[usb_control_msg(0x21, 2) Exploit]].
** Released [[blackra1n]], which used said exploit.
* Discovered how to exploit [[AT+XEMN Heap Overflow|AT+XEMN]] (but did not discover the crash) for a software-based [[X-Gold 608]] unlock.
** Released [[blacksn0w]], which used said exploit to unlock [[X-Gold 608]] firmware [[5.11.07]].
* Released [[limera1n]].

==Links==
* [http://iphonejtag.blogspot.com/ Blog (currently private)]
* http://www.geohot.com/ his homepage
* [http://geohotgotsued.blogspot.com/ New Blog, related to his PS3 battle]

NOTE: He does not have any active Twitter accounts. Any Twitter account you see posing as geohot is fake.

[[Category:Hackers]]

User:Geohot

2011-05-29T18:17:13Z

Markcoker: No Longer Accepting Donations

User:Markcoker

2011-05-29T17:44:36Z

Markcoker: New page: Blue Skies (Mark Coker) Interests in IDevice, Security and other technology.

Blue Skies (Mark Coker)

Interests in IDevice, Security and other technology.

IPad 2

2011-05-29T17:02:24Z

Markcoker: timeline for exploit

[[Image:Ipad2.png|right|thumb|iPad 2]]
{{lowercase}}
The iPad 2 was announced on March 2, 2011. It was initially released on March 11 in the United States, and March 25 elsewhere. There are three variants of the iPad 2.

As of May 30, 2011, the iPad 2 does not have any (publicly released) exploits to run unsigned code. (there is impression there is exploit to be release within about 3 weeks.)

* [[K93ap|Wi-Fi only]]
* [[K94ap|GSM model]]
* [[K95ap|CDMA model]]

== Application processor ==
It makes use of the dual-core 1 GHz[http://www.apple.com/ipad/specs/] [[S5L8940]] CPU (A5 chip).

== Baseband (3G versions) ==
The [[K94ap|GSM model]] uses the [[X-Gold 618]] baseband chip, same as in the [[N90ap|iPhone 4 GSM model]].

The [[K95ap|CDMA model]] uses Qualcomm's Gobi chipset, like the [[N90ap|iPhone 4 CDMA model]].

==Wireless==
The iPad 2 uses the [[BCM4329]] for [[Bluetooth]] and Wi-Fi communication.

== Specifications ==
* '''Screen:''' 9.7" 1024x768 LED-backlit IPS display at 132 ppi
* '''Size:''' 9.5 inches (241.2 mm) (height) x 7.31 inches (185.7 mm) (width) x 0.34 inch (8.8 mm) (depth)
* '''Weight:''' 1.33 pounds (601 g) [[K93ap|Wi-Fi model]]; 1.35 pounds (613 g) [[K94ap|GSM model]]; 1.34 pounds (607 g) [[K95ap|CDMA model]]
* '''Battery:''' Up to 10 hours of Internet use, one month of standby
* '''3G:''' UMTS/HSDPA/HSUPA (850, 900, 1900, 2100 MHz); GSM/EDGE (850, 900, 1800, 1900 MHz) [[K94ap|GSM model]]; CDMA EV-DO Rev. A (800, 1900 MHz) [[K95ap|CDMA model]]
* '''Rear camera''': 0.7MP, supporting HD video recording @ 30 FPS
* '''Front camera''': VGA photos and video @ 30 FPS, supporting [[FaceTime]] video calls

AES Keys

2011-05-26T08:08:37Z

Markcoker: /* Running The Engine */ openpwn link not valid anymore

The [http://en.wikipedia.org/wiki/System-on-a-chip SoC] in each device have an [http://en.wikipedia.org/wiki/Advanced_Encryption_Standard AES] coprocessor with the [[GID-key]] and [[UID-key]] built in.

==Running The Engine==
Currently, there are several ways to run the hardware AES engine:
* Use the [http://forums.openpwn.org/viewtopic.php?f=8&t=19&p=101#p101 AES payload] released on OpenPwn. (OpenPwn link not valid anymore)
* Patch [[iBoot (Bootloader)|iBoot]] to jump to aes_decrypt.
* Use [http://github.com/planetbeing/iphonelinux/tree/master OpenIBoot].
* Use the crypto bundle provided in [[XPwn]] to utilize it via userland. This method requires a kernel patch.
* Use [[Greenpois0n (toolkit)|Greenpois0n]] console.

If you want to decrypt [[IMG3 File Format|IMG3]] files you need to use this. The [[GID-key]] currently has not been extracted from the phone, so the only way to use it is on the phone itself.

See [[Easier method of getting Img3 Key / IV]] for an [[iBoot (Bootloader)|iBoot]] patch.

==Key 0x837==
Generated by encrypting 345A2D6C5050D058780DA431F0710E15 with the [[S5L8900]] [[GID-key]] to get 188458A6D15034DFE386F23B61D43774

It is used as the encryption key for [[S5L File Formats#IMG2|IMG2 files]]. With the introduction of [[IMG3 File Format|IMG3]] in 2.0, [[KBAG]]s are now used instead of the 0x837 key.

==Using [[Greenpois0n (toolkit)|greenpois0n]] to get the keys==
* Run steps 1 thru 5 from [[PwnStrap]]
* Use 'xpwntool file.img3 /dev/null' to extract the KBAG hex string from ''file.img3''
* Start greenpois0n console: irecovery -s
* Execute 'go aes dec _KBAG_STRING_' in irecovery console

==Resources==
[http://wikee.iphwn.org/s5l8900:encryption_keys Dev Team wiki]