The iPhone Wiki - User contributions [en]

Chimera

2021-02-23T09:58:28Z

Beej: /* iOS */ fix table rendering

{{Infobox software
| name = Chimera
| title = Chimera
| developer = [https://twitter.com/electra_team Electra Team] [https://twitter.com/coolstarorg CoolStar]
| released = {{Start date|2019|04|30|df=yes}}
| latest release version = 1.6.2 (iOS) 1.3.9 (tvOS)
| latest release date = {{Start date and age|2021|02|07|df=yes}} (iOS) {{Start date and age|2019|10|09|df=yes}} (tvOS)
| operating system = iOS, tvOS
| language = English
| genre = Jailbreaking
| website = [https://chimera.sh Chimera.sh]
}}

'''Chimera''' is a [[semi-untethered jailbreak]] for A7-A11 devices running 12.0-12.5.1, A12 devices on 12.0-12.1.2, and tvOS 12.0-12.2 and 12.4. (Nonce setter only on 12.1.3-12.2, 12.4-12.4.1 for A12 devices.)

== Versions ==
=== iOS ===
{| class="wikitable"
|-
! Version
! Date
! Changes
|-
| 1.0
| rowspan="3" | {{date|2019|04|30}}
|
* Initial Release
|-
| 1.0.1
|
* Fix voucher_swap on betas
* Fix voucher_swap on some iPad Pros
* Reduce IPA size by 32%
|-
| 1.0.2
|
* Fixes issues with A12X iPad Pro's failing to jailbreak
|-
| 1.0.3
| rowspan="2" | {{date|2019|05|04}}
|
* Adds a fix for RocketBootstrap issues on certain devices and updates the bundled @GetSileo to version 1.0.5!
|-
| 1.0.4
|
* Removes the broken SSH toggle on 1.0.3 and fixes non-working SSH
|-
| 1.0.5
| {{date|2019|05|10}}
|
* Fixes Mail.app send bug.
* Updates Sileo to 1.0.6
* Attempts to fix A12-only Camera bug
* Fixes issues with the app occasionally black screening at step 2 and should improve success rate.
* Adds machswap2 for A12
|-
| 1.0.6
| {{date|2019|05|19}}
|
* Improves jailbreak success rate
* Fixes issue in 1.0.5 that would result in automatic rootfs restores
|-
| 1.0.7
| {{date|2019|05|26}}
|
* Makes re-jailbreaking significantly faster (4 seconds instead of 12 seconds on a device tested with mach_swap2)!
|-
| 1.0.8
| {{date|2019|06|09}}
|
* This fixes the issue where the Sileo icon wouldn't show up after jailbreaking with 1.0.7, 1.0.8 is otherwise identical to 1.0.7.
|-
| 1.0.9
| {{date|2019|07|02}}
|
* This includes a few stability fixes and optimizations, as well as updating the bundled Sileo to 1.1.2!
|-
| 1.1.0
| {{date|2019|07|08}}
|
* Updates bundled Sileo to 1.1.5
* Fixes Sileo icon not showing up after jailbreak
|-
| 1.2.0
| rowspan="3" | {{date|2019|07|12}}
|
* add support for A9 - A11 devices on iOS 12.1.3 - 12.2
|-
| 1.2.1
|
* This fixes issues that users were experiencing with the exploit failing on 12.2
|-
| 1.2.2
|
* This fixes an issue where 1.2.1 would fail to jailbreak A12 devices using voucher_swap
|-
| 1.2.3
| {{date|2019|07|14}}
|
* This adds support for some beta versions of iOS 12.3!
|-
| 1.2.4
| {{date|2019|07|15}}
|
* This adds support for A7 and A8 devices on 12.1.3 to 12.2 including certain 12.3 betas!
|-
| 1.2.5
| {{date|2019|07|23}}
|
* Improves stability significantly on iOS 12.2
* Fixes occasional freezes on 12.0 - 12.1.x
* Adds [https://twitter.com/NedWilliamson @NedWilliamson] to in-app credits for sockpuppet
|-
| 1.2.6
| {{date|2019|07|24}}
|
* This adds sockpuppet2 for devices on iOS 12.1 - 12.2, increasing reliability of the exploit!
* Note, 12.0/12.0.1 will get sockpuppet 1.5 instead; though they may use machswap(2) or voucher_swap
|-
| 1.2.7
| {{date|2019|07|26}}
|
* adds support for sockpuppet 1.5 on A12 devices on 12.0 - 12.1.2
|-
| 1.2.8
| rowspan="2" | {{date|2019|08|18}}
|
* Adds support for iOS 12.4 on A9 - A11 devices!
|-
| 1.2.9
|
* This bundles the package updates that were pushed after 1.2.8, and should fix issues with installing certain packages (such as NewTerm or Anemone 3)
|-
| 1.3.0
| {{date|2019|08|19}}
|
* adds support for A8 devices on 12.4
|-
| 1.3.3
| {{date|2019|08|20}}
|
* This replaces the sockpuppet 1.5 & sockpuppet2 exploits with the sockpuppet3 exploit (thanks to [https://twitter.com/umanghere @umanghere])
* This also adds support for A7 & A8X
|-
| 1.3.4
| {{date|2019|08|21}}
|
* This fixes the issue causing occasional reboots on 12.2 and 12.4.
* Fixes Sileo not installing correctly on iOS 12.0 - 12.1.4.
|-
| 1.3.6
| {{date|2019|08|23}}
|
*improvements to the SockPuppet exploit that increase reliability and fixes a rare crash that could happen rarely shortly after the jailbreak process.
|-
| 1.3.7
| {{date|2019|09|03}}
|
* Supports getting & setting generator on A12 on 12.1.3 - 12.2 and 12.4!
|-
| 1.3.8
| {{date|2019|09|04}}
|
* This fixes error handling of setting nonces on A12 12.1.3+, as well as fixing an issue with setting nonces on devices that haven't used `igetnonce` get.
|-
| 1.3.9
| {{date|2019|09|16}}
|
* This improves the success rate of sockpuppet3 (especially on 4K devices like the 5S and 6)
|-
| 1.4.0
| {{date|2020|03|14}}
|
* This uses libhooker internally instead of substitute to apply some patches.
|-
| 1.5.0
| rowspan="2" | {{date|2020|12|02}}
|
* Adds support for up to 12.4.9 on pre-A12 and nonce setter support for A12 on 12.4.1.
|-
| 1.5.1
|
* Rejailbreaking an existing Odysseyra1n installation with Chimera will no longer wipe packages database
* Rejailbreaking an existing Chimera installation with checkra1n (for Odysseyra1n) will have working read/write filesystem
* RocketBootstrap from the Odyssey repo will now work correctly on Chimera
* Exploit selector on iOS 12.2 & 12.4 now works correctly (to allow switching between sockpuppet and life_waste)
|-
| 1.6.0
| {{date|2020|12|25}}
|
* Officially verified to work on iOS 12.5 (Chimera 1.5.1 already worked on 12.5)
* Backports more of Odyssey's changes to Chimera
** the platform-application entitlement is now no longer required for binaries to run
** skip-library-validation entitlement is now no longer required for libraries to load into binaries
** improves efficiency and reliability of Chimera
* Note: These backported changes were adapted to use kexec [pac bypass], as such Chimera still only supports A12 devices up to iOS 12.1.2
* Fixes potential app black screen issue during the jailbreak process
* Fixes reliability issues with injecting into launchd during the jailbreak process
* Fixes potential post-jailbreak kernel panics on 4K devices (A7/A8) improving reliability of the jailbreak
* jailbreakd plist has been moved to improve compatibility with odysseyra1n (jailbreakd no longer runs or crashes when booted with odysseyra1n)
* Fixes memory leak and slow performance if jailbreakd is restarted
* Experimental support for full userspace reboot
** To test userspace reboot you can run launchctl reboot userspace
** Userspace reboot should complete in about 15 seconds
** Userspace reboot works about 50% of the time (hence the jailbreak itself is still using ldrestart as it's more reliable)
|-
| 1.6.1
| {{date|2021|01|16}}
|
* Userspace reboot is now fully completed and reliable
* Userspace reboot is now enabled by default and runs during the jailbreak process instead of ldrestart
* Officially validated for iOS 12.5.1
|-
| 1.6.2
| {{date|2021|02|07}}
|
* Fully reliable userspace reboot
* Sileo icon now shows up reliably on fresh bootstraps
* uicache runs on rootfs restore and removes jailbreak app icons
* New Chimera splash screen on userspace reboot
|}

=== tvOS ===
{| class="wikitable"
|-
! Version
! Date
! Changes
|-
| 1.0
| {{date|2019|04|30}}
|
* Initial Release
|-
| 1.0.2
| {{date|2019|05|04}}
|
* Fixes issues with Apple TV 4K failing to jailbreak
|-
| 1.0.6
| {{date|2019|05|20}}
|
* Improves jailbreak success rate
|-
| 1.0.7
| {{date|2019|05|28}}
|
* Makes re-jailbreaking significantly faster
|-
| 1.2.2
| {{date|2019|07|14}}
|
* This version adds support for tvOS 12.2 on the Apple TV 4K , 1080p Apple TV 4 is only supported up to 12.1.1
|-
| 1.2.5
| {{date|2019|07|23}}
|
* This brings all the stability fixes from Chimera 1.2.5 to ATV!
|-
| 1.2.6
| {{date|2019|07|26}}
|
* adds support for sockpuppet2 on the A10 Apple TV on 12.0 - 12.2
|-
| 1.3.4
| {{date|2019|08|21}}
|
* This fixes the issue causing occasional reboots on 12.2 and 12.4.
* Adds support for tvOS 12.2 & 12.4
|-
| 1.3.6
| {{date|2019|08|23}}
|
* improvements to the SockPuppet exploit that increase reliability and fixes a rare crash that could happen rarely shortly after the jailbreak process.
* bundles a new version of nitoTV that fixes a variety of bugs.
|-
| 1.3.9
| {{date|2019|10|09}}
|
* updated bootstrap, latest nitoTV and it will recover from running "reset settings" properly now as well.
|}

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

TotallyNotSpyware

2018-09-08T11:58:01Z

Beej: 1.13

{{Infobox software
| name = TotallyNotSpyware
| title = TotallyNotSpyware
| developer = [https://twitter.com/JakeBlair420 JakeBlair420]
| released = {{Start date|2018|09|03|df=yes}}
| latest release version = 1.13
| latest release date = {{Start date and age|2018|09|07|df=yes}}
| operating system = iOS
| language = English
| genre = Jailbreaking
| website = [https://totally-not.spyware.lol totally-not.spyware.lol]
}}
'''TotallyNotSpyware''' (also known by its domain name as '''spyware.lol''' or '''totally-not.spyware.lol''') is a [[semi-untethered jailbreak]] for all 64-bit devices running any version of iOS 10.

It uses a [[JailbreakMe]]-style WebKit exploit along with either the [[Meridian]] or [[doubleH3lix]] bootstraps to achieve the jailbreak.

== Contributors ==
The jailbreak was created under the team name [https://twitter.com/JakeBlair420 "JakeBlair420"].
*Active contributors: [https://twitter.com/FoxletFox FoxletFox], [https://twitter.com/iBSparkes iBSparkes], [https://twitter.com/littlelailo littlelailo], [https://twitter.com/s1guza s1guza], [https://twitter.com/stek29 stek29]
*Based on works by: [https://twitter.com/5aelo 5aelo], [https://twitter.com/i41nbeer i41nbeer], [https://twitter.com/_niklasb _niklasb], [https://twitter.com/nullriver nullriver], [https://twitter.com/qwertyoruiopz qwertyoruiopz], [https://twitter.com/REALKJCMEMBER REALKJCMEMBER], [https://twitter.com/sbingner sbingner], [https://twitter.com/sticktron sticktron], [https://twitter.com/theninjaprawn theninjaprawn], [https://twitter.com/tihmstar tihmstar], [https://twitter.com/xerub xerub]

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

Talk:TvOS

2016-07-20T15:27:49Z

Beej: Created page with "Pangu9 jailbreaks tvOS ~~~~"

Pangu9 jailbreaks tvOS [[User:Beej|beej]] ([[User talk:Beej|talk]]) 15:27, 20 July 2016 (UTC)

The iPhone Wiki:Community portal

2014-06-27T08:02:46Z

Beej: Email notifications?

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

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

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

==Hacker page==
I would like to be added to the list of hackers for my work with the Private Dev Team and the [[Chronic Dev (team)|Chronic Dev Team]] in addition to my release of the Phoenix Semi-Untethered. --[[User:Ph0enix|Ph0enix]] ([[User talk:Ph0enix|talk]]) 18:36, 22 July 2013 (UTC)
:Did you find any exploits? --[[User:Haifisch|Haifisch]] ([[User talk:Haifisch|talk]]) 18:54, 22 July 2013 (UTC)
::No. [[User:phyrrus9|phyrrus9]], a team member found the vulnerability. I am the one who exploited it. --[[User:Ph0enix|Ph0enix]] ([[User talk:Ph0enix|talk]])
:::I can back up this "claim". I was a part of it. --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 20:52, 28 July 2013 (UTC)
::::Whatever happened to this? --[[User:Phyrrus9|phyrrus9]]
:::::So this went cold and i am going to again request that this change be made. --[[User:Ph0enix|Ph0enix]] ([[User talk:Ph0enix|talk]]) 18:28, 13 January 2014 (UTC)
::::::I'm gonna say no. I don't see any notable accomplishments to merit this. --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 21:53, 13 January 2014 (UTC)
::::::'''No'''. The first step would be to get to the category [[:Category:Hackers|hackers]]. You can get there by finding a vulnerability that is used with an exploit in a jailbreak - or by writing a new exploit. Remember that it's not allowed to add yourself to that category. Instead of finding a vulnerability you could also be member of either The [[iPhone Dev Team]] or [[Chronic Dev]] or [[evad3rs]]. After being in that category, the next step would be that you're famous enough from all those hackers there to get to the main page. The people chosen are discussed here. --[[User:Http|http]] ([[User talk:Http|talk]]) 23:42, 13 January 2014 (UTC)

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

==Date Format==
I see that [[User:IAdam1n|iAdam1n]] started to unify the date formats in this wiki. While I like this to be consistent, actually we should've talked about what format to use before changing it. I like the d_mon_yyyy format though. I also saw that he removed the <code>&nbsp;</code> between the date parts on the [[iFaith]] page that I added once purposefully. The reason was that when making the browser window small (or on the iPhone) that the date wraps to two lines, which is almost always undesired. The question is if we should do that everywhere too? Additionally, as we now seem to have a "standard" here, we should document it, so that new users know what format to use. -- [[User:Http|http]] ([[User talk:Http|talk]]) 17:42, 30 December 2013 (UTC)
:I just made it consistent. If you want the <code>&nbsp;</code> back, feel free to add it. I removed it as it did nothing (previewing on OS X). We should use the format I used throughout the wiki and not Dec 23, 2013 etc. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 18:32, 30 December 2013 (UTC)
::<code>&nbsp;</code> stands for "'''n'''on-'''b'''reaking '''sp'''ace". It is essentially a space, but with a property that prevents word wrap from occurring between the two words it's between. Look at [[Firmware Keys]] on a small enough screen (1024 across should do it). Your browser should preserve the space between the date "words". Now, go into the edit page and remove the <code>&nbsp;</code> from everything in one table. Your browser will now word wrap the date "words". --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 00:04, 5 January 2014 (UTC)
:What I actually want to do is use <code>{{[[Template:Start date|start date]]}}</code> instead of plain dates in areas where dates are used as a statistic; for example, [[Firmware]], [[Firmware Keys]], [[SHSH]], [[Timeline]], etc. Places where dates are used to record when something happened, for example on [[evasi0n7]], "On 28 December 2013...", should use the date flat out in the source. --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 00:04, 5 January 2014 (UTC)

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

== Mainpage "iPhone Hackers" List ==

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

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

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

== Replacing old/broken download links ==

I have noticed on pages like [[evasi0n]] and [[p0sixspwn]] that some of the dwonlaod links no longer work because the developers have taken the revision of the software down. Rather than leave them there, I suggest we replace the links with ones that can be accessed (such as with ones in my MEGA). For example, version 1.0 of [[evasi0n]] was taken down from MEGA and no longer exists. However, I have version 1.0 saved in my MEGA Drive so I could replace the broken links with ones to downloads in my MEGA Drive. What do you guys think of this? — '''[[User:Spydar007|Spydar007]] [[User talk:Spydar007|(Talk)]]''' 10:07, 30 March 2014 (UTC)
:I do not like this idea as it breaks copyright. We normally just put a line through with <code>style="text-decoration: line-through;"</code>. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 10:18, 30 March 2014 (UTC)
::I know but I think that people should still be able to download the old versions. — '''[[User:Spydar007|Spydar007]] [[User talk:Spydar007|(Talk)]]''' 11:23, 30 March 2014 (UTC)
:::I disagree. Except for [[evasi0n7]], latest versions work best and with evasi0n7, all links work. We do not want unofficial links because of copyright. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 17:35, 30 March 2014 (UTC)
::::This contradicts your actions a bit— I've never seen official MEGA links for newer releases of evasi0n7, yet you filled it in for some of them. But I digress… In all honesty, I wouldn't mind, as long as no copyrights are violated. There should be some sort of distinction that it's not an official link though. --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 23:28, 30 March 2014 (UTC)
:::::The MEGA links that I have added myself have been from evasi0n.com with "view source" in a browser. The earlier releases, [[User:5urd|5urd]] added them so I don't know about those. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 07:23, 31 March 2014 (UTC)
::::::To be honest, it is only violating copyright if the jailbreak tools cost money. Since they are free, it is not violating copyright. — '''[[User:Spydar007|Spydar007]] [[User talk:Spydar007|(Talk)]]''' 15:11, 31 March 2014 (UTC)
:::::::Copyright laws are '''always''' in place, regardless of how much something costs, unless the creator waives their copyrights. --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 05:25, 1 April 2014 (UTC)
:::::So, should I go ahead a do it? I could put a warning triangle symbol before it so that it is shown to be an unofficial link. — '''[[User:Spydar007|Spydar007]] [[User talk:Spydar007|(Talk)]]''' 14:42, 31 March 2014 (UTC)
::::::I say no. On JailbreakQA, one moderator was told by MuscleNerd to remove a hosted version that included the edit for 7.0.6 before evasi0n7 1.0.7 was released. There is no need for older versions since the latest works, with the exception of evasi0n7 1.0.8 but 1.0.7 links are still valid. I strongly disagree to add this. Also it should have at least a week on discussion. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 15:59, 31 March 2014 (UTC)
:::::::That sounds more like MuscleNerd not wanting tampered copies of evasi0n7 to float around. That being said, I don't know whether he or the rest of the evad3rs would be fine with rehosting untouched copies of their files though. --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 05:25, 1 April 2014 (UTC)

== geeksn0w ==

I think we should make a page for geeksn0w. It is a jailbreak tool used by a significant amount of users who have iPhone 4's. I don't see why there isn't a page already. What do you guys think? — '''[[User:Spydar007|Spydar007]] [[User talk:Spydar007|(Talk)]]''' 15:07, 10 April 2014 (UTC)
:I personally like the idea. I would at least like to see it added to [[iPhone 4]] on [[Jailbreak|the jailbreak page]]. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 15:32, 10 April 2014 (UTC)
::Exactly, we should add it to the [[Jailbreak]] page and create a page on it. What do you think of creating a page for the developer/hacker, BlackGeekTutorial? He is just about to start working on [[iFaith]] for iOS 7.
:::Personally, we don't need a page on him I don't think until he has made a lot. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 15:52, 10 April 2014 (UTC)
::::On the page, I am thinking of having download links to previous versions (in my MEGA drive) since BlackGeek doesn't give out other links. What do you think? — '''[[User:Spydar007|Spydar007]] [[User talk:Spydar007|(Talk)]]''' 16:10, 10 April 2014 (UTC)
:::::I think we should only use official links but thats just me. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 22:56, 25 April 2014 (UTC)
::::::I know we should use official links, but BlackGeek doesn't keep the links active. Also, he doesn't use MEGA. He just hosts it in the portfolio for his website. But he uses Adfly links to host them too. Do we really want Adfly links here? — '''[[User:Spydar007|Spydar007]] [[User talk:Spydar007|(Talk)]]''' 12:10, 26 April 2014 (UTC)
:::::::If that is the official link, I would say yes. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 14:11, 26 April 2014 (UTC)

== Cyberelevat0r ==

I think we should make a page for Cyberelevat0r (i0n1c's 7.1.x Untethered Jailbreak). There is multiple proof that he might release it and we can fill it with information about all other hackers that have 7.1.x untethered jailbreaks as well. What do you think? — '''[[User:Spydar007|Spydar007]] [[User talk:Spydar007|(Talk)]]''' 05:40, 22 May 2014 (UTC)
:No. If (and it's a massive if) it gets released, then ok. Not until. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 08:01, 22 May 2014 (UTC)

== Email notifications? ==

is it currently possible to get emailed by the wiki when a watchlist page changes? i'd sure love that feature. https://www.mediawiki.org/wiki/Manual:Configuration_settings#Email_notification_.28Enotif.29_settings looks relevant? [[User:Beej|beej]] ([[User talk:Beej|talk]]) 08:02, 27 June 2014 (UTC)

Pangu

2014-06-27T07:52:08Z

Beej: s/English/Chinese/

{{other|untethered jailbreak for iOS 7.1.x|semi-tethered jailbreak for iOS 7.1.x|Geeksn0w}}
{{Infobox software
| name = Pangu
| title = Pangu
| author = Pangu Team
| developer = Pangu Team
| released = {{Start date|2014|06|23|df=yes}}
| discontinued =
| latest release version = 1.0.0
| latest release date = {{Start date and age|2014|06|23|df=yes}}
| latest preview version =
| latest preview date =
| programming language = C?
| operating system = [[wikipedia:Microsoft Windows|Windows]]
| size =
| platform =
| language = [[wikipedia:Chinese_language|Chinese]]
| status = Active
| genre = Jailbreaking
| license = [[wikipedia:Freeware|Freeware]]
| website = [http://pangu.io pangu.io]
}}

'''Pangu''' is a [[jailbreak]] program. It performs an [[untethered jailbreak]] for all devices on iOS 7.1.x, except the [[Apple TV]]. It was initially released on 23 June 2014, and became subject to [[#Controversy|controversy and criticism]].

== Controversy ==
Pangu installs 25PP, a Chinese cracked app store, if the user ticks the checkbox to install it. iH8sn0w confirmed that Pangu does not install spyware or phishing viruses onto the device.

Pangu also uses a revoked enterprise certificate in order to inject the jailbreak, which is removed after the jailbreak is complete.

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

== Download ==
{| class="wikitable"
! Version
! OS
! SHA-1 Hash
! Download
! Changes
|-
| 1.0.0
| [[wikipedia:Microsoft Windows|Windows]]
| <code>7d66f1f939cbf877f1e90480571f92b238245fab</code>
| [http://dl.pangu.25pp.com/jb/Pangu_v1.0.exe 25PP]
| Initial release
|}

[[Category:Jailbreaks]]

Category talk:Hackers

2014-06-25T15:19:16Z

Beej: /* Pangu team members */ new section

== Change display names here / discussion about using User:xx or xx directly ==
Is there a way to change the name of those User: prefixes? -- [[User:Http|http]] 10:03, 15 July 2010 (UTC)
:It appears that [http://www.mediawiki.org/wiki/Namespace_manager prefixes can be created by administrators]. --[[User:Dialexio|Dialexio]] 22:26, 16 July 2010 (UTC)
::Hmm. I didn't want to change the prefix as such. I just wanted to change how these users appear in this category list. For example if all had accounts here, then all would appear under the letter "U" (because they start with "User:"). Right now it's even mixed, planetbeing is under "U", but Comex under "C". And some others should have different case or otherwise some small changes how they appear in this list. Maybe there is an option to set on the respective page how they appear in category pages? And something else: I would prefer to have all these people with their own page (not the User:xx one). We could put a redirect on their User:xx page instead. Right now you decided to put it the other way round. But this results in this mixed list. Also all references have to be written like this then: <nowiki>"[[User:Geohot|geohot]]" instead of simply [[geohot]]</nowiki>. Also a simple Go in the search box for these names won't work now (will do a search and probably find them though). I think we should change that back and put planetbeing, geohot, Musclenerd and Westbaer to their xx page (instead of User:xx). What do you think? -- [[User:Http|http]] 22:48, 16 July 2010 (UTC)
:::Didn't notice this until now. :\ My thought is, if the person is a user here, their user page should contain the info about them. I just tested it out, and typing "[[Geohot]]" into the search box and hitting "Go" redirects to "[[User:Geohot]]" without a hitch. :) --[[User:Dialexio|Dialexio]] 03:09, 26 July 2010 (UTC)
::::That is because someone created a redirect as [[Geohot]] used to contain the info till it was moved to his own user page --[[User:5urd|5urd]] 19:31, 4 January 2011 (UTC)

== Wiki-Problem ==
Also I wanted to place a link on "exploits" pointing to Category:Exploits, but this disappears (at least in preview mode), so I didn't save. Any ideas? -- [[User:Http|http]] 10:03, 15 July 2010 (UTC)
:Redirects don't show in previews. Just created the page. --[[User:Dialexio|Dialexio]] 22:26, 16 July 2010 (UTC)
::Hmm. I meant something different. I wanted to put a link on the title, like this: "<nowiki>...finding new [[Category:Exploits|exploits]] or being...</nowiki>" but in Preview it just disappeared. But with the new redirect it should work. Maybe a bug in this Wiki. -- [[User:Http|http]] 22:48, 16 July 2010 (UTC)
:::Found the problem. If the link contains a colon, you have to prefix the link with a colon. --[[User:Http|http]] 18:12, 4 January 2011 (UTC)
::::Partly wrong, to link to an article at the root, you use <code>:(Article name)</code>. For example <code><nowiki>[[/Applications]]</nowiki></code> will link to <code>Category talk:Hackers/Applications</code>. <code><nowiki>[[:/Applications]]</nowiki></code> will like to the actual <tt>/Applications</tt> article. Also, to add a category you use a plain link and to link, you use the colon. Took me a while to figure that one out... --[[User:5urd|5urd]] 19:29, 4 January 2011 (UTC)

== Zibri ==
I just included Zibri as well. He is or was active in the scene and was member of the [[iPhone Dev Team]], so that should be reason enough to include him. I only know part of his exclusion story, but I think he still belongs into this category. -- [[User:Http|http]] 10:52, 15 July 2010 (UTC)

== Included all team members ==
I just included all members and ex-members of the [[iPhone Dev Team]] and [[Chronic Dev (team)|Chronic Dev]]. I think they are worth being mentioned here. If you think some do not belong in here, feel free to remove their Category tag. But better first discuss here, to make sure all agree with it. -- [[User:Http|http]] 22:06, 22 July 2010 (UTC)

== Pangu team members ==

as releasers of the first public untethered iOS 7.1 jailbreak, i think Pangu team members should get pages here. i know Twitter user @windknown is one of the primary ones. thoughts? [[User:Beej|beej]] ([[User talk:Beej|talk]]) 15:19, 25 June 2014 (UTC)

P0sixspwn

2014-06-25T07:48:20Z

Beej: now supports 6.1.6

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

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

==Download==
{| class="wikitable"
! Version
! OS
! SHA-1 Hash
! Download
! Changes
|-
! 1.0.0
| rowspan="3" | [[wikipedia:OS X|OS X]]
| <code>b5a66f4e58ab4c813fc851d479b28188eb5115ec</code>
| style="text-decoration: line-through;" | [https://MEGA.co.nz/#!0xtw0DAT!YVZmNXsn-kl1kH655zgpMGz8hSVVgk8FU3qlTPNfSdU MEGA]
|
* Initial release.
|-
! 1.0.1
| <code>ae5b3907660b161b2ff94a2e2cfef97195404a89</code>
| style="text-decoration: line-through;" | [https://MEGA.co.nz/#!l8lniKxL!ODQrFDGbOUpm2hvU-mQggm25IgNk3_TmSO1r7tlU178 MEGA]
|
* Resolves issues with [[iPod touch 5G]] not being detected.
|-
! 1.0.2
| <code>259e95fd16468260c8831ca17186f50b7d14ba41</code>
| [https://MEGA.co.nz/#!DVtmGLqa!BX2-OQUliBcfdlenMLa93mKxk244KpD9Z71p_DAeil8 MEGA]
|
* Resolves issues with LTE/data.
|-
! 1.0.3
| rowspan="2" | [[wikipedia:Microsoft Windows|Windows]]
| <code>060c95cda0e5ad861bd225ca19324e6ebd3c0a5d</code>
| style="text-decoration: line-through;" | [https://MEGA.co.nz/#!x0sk1SjB!S86WIGnifrgVhf5aoFQiPHl5aMJvS3miIeTTy9pLL_w MEGA]
|
* Initial release for Windows.
|-
! 1.0.4
| <code>0a40a9780ba0dd9f0476d12950b4fb0026c8559a</code>
| style="text-decoration: line-through;" | [https://MEGA.co.nz/#!Vl9zFJYC!JaCsqwnNNDJvj_4t0APjC2XPBg0ZuUwMSNNz2MGb4Xw MEGA]
|
* Added README and time adjustments for slow PC's.
|-
! rowspan="2" | 1.0.5
| [[wikipedia:OS X|OS X]]
| <code>b99fb1de846c406a15bbd710b623ddd78e139e5e</code>
| style="text-decoration: line-through;" | [https://MEGA.co.nz/#!B5lxxDLD!YrvjGhvVDxm2ah94hafI7TJWfm9EK0aWsh4_7YN78qE MEGA]
| rowspan="2" |
* Fixes some issues.
* Support for Mac OS X Snow Leopard.
|-
| [[wikipedia:Microsoft Windows|Windows]]
| <code>7c782a39ed123f70594e2438eaacc95340e363e3</code>
| style="text-decoration: line-through;" class="rborderplz nobrradiusplz" | [https://MEGA.co.nz/#!l1UFgJiA!Ogbi6Q1GsKZZMZzEhi8w1zvlHXEh0QuDBIGdjfktHb0 MEGA]
|-
! rowspan="2" | 1.0.7
| [[wikipedia:OS X|OS X]]
| <code>7f4f867a2e3739e8ee70f7bc7e47afe9871c69b6</code>
| [https://MEGA.co.nz/#!Y8M2VAiS!Bq4NRjrlZXE754uNqSJT90mUzwsSGMPVa2PWsp78344 MEGA]
| rowspan="2" |
* Fixes Cydia sometimes not showing up
|-
| [[wikipedia:Microsoft Windows|Windows]]
| <code>868a05ba26fd679a28c3eac0c4dc2c0cbb5e9529</code>
| class="rborderplz" | [https://MEGA.co.nz/#!E0sESCiC!c-ulVmjoa9qtPDe0MBIQgz9D2H03NgCxjBKZmAUPKRc MEGA]
|-
! rowspan="2" | 1.0.8
| [[wikipedia:OS X|OS X]]
| <code>aa20c28c2e052c08893fdbf49d16f084df2f46e6</code>
| [https://MEGA.co.nz/#!hptDFbzb!Dfa8Th7Ngw6PyDSnWDyMmzHbGYDrMqk64kRMB4MCv0c MEGA]
| rowspan="2" |
* Supports iOS 6.1.6
* Fixes iTunes 11.1+ crashes
|-
| [[wikipedia:Microsoft Windows|Windows]]
| <code>5d2711a99433daa1800d1327207bfc870cd16698 </code>
| class="rborderplz nobrradiusplz" | [https://MEGA.co.nz/#!Rp12yZrK!EhZjmllrpQ4JDC7VvHbcUEautLNBSSFUgBzKFzB20js MEGA]
|}

== Exploits ==
* [[posix_spawn kernel information leak]] (by [[i0n1c]]) (proof? what is it used for?)
* [[mach_msg_ool_descriptor_ts for heap shaping]] (proof/quotes? no information found)
* [[AMFID_code_signing_evasion]]
* [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-1273 CVE-2014-1273] (by [[planetbeing]]) (proof/quotes? no information found)
* [[DeveloperDiskImage race condition]] (by [[comex]]) (proof/quotes? no information found)
* [[Symbolic Link Vulnerability]]
* [[launchd.conf untether]]
* [[IOPlatfromArgs leak]] (by [[iH8sn0w]])

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

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

Opensn0w

2013-09-23T16:11:07Z

Beej: It's just winocm, these days

{{lowercase}}
{{Infobox software
| name = opensn0w
| title = opensn0w
| logo = 
| screenshot = 
| caption =
| collapsible =
| author = [[User:Winocm|winocm]]
| released = N/A
| latest release version = ?
| latest release date = 
| latest preview version = Pre-alpha
| latest preview date = {{Start date and age|2011|12|12}}
| frequently updated = 
| programming language = C, Objective-C
| operating system = Windows, Linux
| language = English
| status = WIP
| genre = Jailbreak Utility
| license = GPLv3
}}

'''opensn0w''' is an open source jailbreaking tool, intended to provide much of the functionality that is in redsn0w, be more developer friendly, and encourage more cooperation and sharing in the community. It is currently a work in progress. All code is available on github at https://github.com/winocm/opensn0w. You can tetherboot an iPhone 4 on iOS 7 with the Linux version of this.

{{Stub|software}}

Talk:Main Page

2013-04-29T22:38:16Z

Beej: /* 6.1.3 jailbreak */ new section

{{Talk Archive|2010|2011|2012|2013}}

== Baseband Chip Page Titles ==
For the baseband chip page titles, I think we should stick with the model number despite the marketing name. Pages:
* [[S-Gold 2|PMB8876]] marketed "S-Gold 2"
* [[X-Gold 608|PMB8878]] marketed "X-Gold 608"
* [[XMM 6180]] marketed "X-Gold 618"
* [[MDM6600]] (unknown marketing name)
* [[MDM6610]] (unknown marketing name)
* [[MDM9x00]] (unknown marketing name)
--[[User:5urd|5urd]] 21:35, 8 May 2012 (MDT)
:I'm leaning more towards the marketing names, since I think people are more familiar with them and they've been in use for a long time. We've always referred to the iPhone 2G's baseband as the "S-Gold 2" and the iPhone 3G/3GS's baseband as the "X-Gold 608." (By the way, it sounds like Qualcomm "markets" their chips by model number. [http://www.qualcomm.com/media/releases/2011/02/14/qualcomm-announces-commercial-availability-gobi3000-modules]) --[[User:Dialexio|Dialexio]] 00:11, 9 May 2012 (MDT)
:I created most of these newer pages and always used the model number (without space). So I agree with that in general. Changing old ones is a totally different story though, where we need more consent. I would be for it (and create a redirect on the marketing names). --[[User:Http|http]] 01:52, 9 May 2012 (MDT)

== Baseband downgrade possibility: Attempt for 04.11.08/04.12.01 to 04.10.01 ==
'''0x1''' There is no downgrade possibility; according to the most basis of fact in how baseband works as explained by dear MuscleNerd and there is signature checks as well as bootloader's chain of trust that I'm not going to repeat them again, but for this topic I start from iTunes error 1,-1,11

'''0x2''' iTunes error 1,-1,11 :
We will get this error whenever we want to do something with BB which is not allowed by apple. you can read about these error in detail from here[http://theiphonewiki.com/wiki/index.php?title=ITunes_Errors].
Going deeper, this error raise by baseband's bootloader whenever you attempt to downgrade BB (in this case), this happens inside the NOR so this is why we can not exploit it easily from the outside.
Another reason for this error (and in here the most important one that I wanted to discuss) is that apple no longer signing that firmware.

'''0x3''' The situation that there is no BB installed on iPhone! :
I could restore my iPhone4 in the case of there will be no BB at all. I called it reset my BB. There will be no Wifi, no BT.
At the first time (a few months since I've started to work on) I thought it is dead (as apple confirmed this also). But I could restore it only to stock firmware with the latest one.
So for who stays in 04.11.08 it may lead to do upgrade to 04.12.01 permanently with the latest iOS, now is 5.1.1 and before for me was 5.0.1, so be sure what you are doing and then go to reset the BB.
So back to the game, if there was no BB then there is no bootloeader inside the NOR to stuck BB update process but I do not know that in this case what happened to "sectable" also known as "locktable" which is the master accountable to unlock the carrier, any way I think so only firmware signature checking by apple will be remain in "restore verify process" by iTunes. because as mentioned earlier, "currentBB"(BB to be updated) is allowed to be update by "comingBB" (BB to be updating to) only if :
1. "currentBB" < "comingBB" (= are you the most recent/lastest BB?)
2. "comingBB" is now signing by apple (=if so, does apple sign you? Are you eligible?)
Huum... What happens if "currentBB"="null/zero/no matter"? Could we eliminate option (1) from the security check above in this case? So what next?

'''0x4''' Track back to the issue lead us inside the bbfw file (ICE3_04.11.08_BOOT_02.13.Release) which contains four .fls files inside, and the most important one is psi_flash.fls who is in charge of security checks before handover the routines to stack.fls which is responsible for updating the baseband. This file does like NOR bootloader but fortunately it's outside the device so it is accessible but not such easy format to be understand by programmers. They are raw ROM based images for XMM6180 chip, ARM based and programmed in Thread-X, but the compiler is unknown; I will write about some disassembly notes using ida pro 6.1; by the way I leave my iPhone with no BB trying to find out and break the trust chains in the above files in order to bypass the bootloader security checks which may let us to downgrade to 04.10.01 which is currently unlocked by Gevey.
Keep in mind that if this solution works..., it will need the SHSH for downgrading the iOS firmware to do reset the BB.
I heard that iPhoneDevTeam are going to release the new version of Redsn0w which there will be no need to restore by iTunes but I do not know if the baseband approaches supposed to be addressed or it will work like iFaith that is basically bypass (preserve) BB, any way if I found this article useful I will note about disassembly and possibility approach as well as BB reset to share with any followers.
'''--[[User:Kambiz|Kambiz]] 07:49, 13 May 2012 (MDT)K.N'''

== Bluetooth Chip on [[iPhone 5]] ==
Is there any confirmation of the Bluetooth chip used in the iPhone 5? If there is, can we edit this page and add it? --|[[User:5urd|5urd]] 10:04, 8 October 2012 (MDT)
:Chipworks [http://www.chipworks.com/blog/recentteardowns/2012/10/02/apple-iphone-5-the-rf/ analyzed the iPhone 5's Murata Wi-Fi module] and determined it uses the [[BCM4334]]. I'll add it to the Main Page now. --[[User:Dialexio|Dialexio]] 20:35, 8 October 2012 (MDT)

== Everything Else ==
Can we list the devices, instead of writing "Everything Else"? -- [[User:Http|http]] 16:15, 16 October 2012 (MDT)
:Yeah, that's a good idea. (Especially since the older devices have been removed!) --[[User:Dialexio|Dialexio]] 17:57, 16 October 2012 (MDT)
----
It looks like it's changed back to "Everything Else" again. :-( --[[User:Http|http]] ([[User talk:Http|talk]]) 22:39, 30 January 2013 (UTC)
:Oh, didn't notice there was a discussion. Well, my reasoning was: Why do we need to list the devices? People read left to right, so if they see that their device isn't on the column to the left of it, they can assume (correctly) that it's in that column. Besides, it just becomes a pain to list all the devices and have to update them when there is a firmware update. --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 23:17, 30 January 2013 (UTC)
:: We still should have devices listed. --[[User:Adaminsull|adaminsull]] ([[User talk:Adaminsull|talk]]) 23:33, 30 January 2013 (UTC)
:: Problem is that the iPhone 3G and other devices are not there. And even for newer devices, if you're looking for your device X, how can you be sure it's in the "Everything Else" column? But I agree that there are many devices now. Maybe we should find a way to group them better or something. Or make a note like (*) and list these "Else" devices below or something like that. --[[User:Http|http]] ([[User talk:Http|talk]]) 00:16, 31 January 2013 (UTC)
:::We could say "iPad 2 and newer / iPad mini 1G / iPhone 4S and newer / iPod touch 5G" instead of "Everything Else," like this. --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 04:07, 1 February 2013 (UTC)
{| class="wikitable" style="text-align:center; width:100%;"
|-
! style="width:15%;" | [[Models|Device]]
| style="width:20%;" | [[n88ap|iPhone 3GS]]
| style="width:15%;" | [[iPhone 4]] (GSM Models) [[n81ap|iPod touch 4G]]
| style="width:15%;" | [[k66ap|Apple TV 2G]]
| style="width:15%;" | [[Apple TV 3G]] (Both Models)
| style="width:20%;" | [[iPad 2]] and newer [[iPad mini 1G]] [[n94ap|iPhone 4S]] and newer [[n78ap|iPod touch 5G]]
|}
:::: This is better although I like stating all devices. --[[User:Adaminsull|adaminsull]] ([[User talk:Adaminsull|talk]]) 11:09, 1 February 2013 (UTC)

== [[iPad 4]] and [[iPad mini]] ==
Can we add the new iPads to the list? The A6X is 8955 as per the heat sink cover on it. --[[User:5urd|5urd]] 09:43, 25 October 2012 (MDT)
:If you mean [http://images.apple.com/ipad/specs/images/specs_chip.jpg the badge Apple depicts the A6X as], the depiction actually still says "APL5498" (which translates to the S5L8945/A5X… yeah, Apple got lazy with this badge as well). The A6X probably will be S5L8955, but I haven't seen any sort of confirmation yet. --[[User:Dialexio|Dialexio]] 09:56, 25 October 2012 (MDT)
::Yeah the badge. Derp. Anyways, the [[wikipedia:File:Apple A6X chip.jpg|A6X badge]] is <code>APL5598</code> which translates to <code>S5L8955/A6X</code>. Maybe it actually is 5598 (little endian?) but that is unlikely. --[[User:5urd|5urd]] 10:17, 25 October 2012 (MDT)
:::The description of that image clearly states that it's an enhanced version of the A5X image on Wikipedia (i.e. it's edited). --[[User:Dialexio|Dialexio]] 10:57, 25 October 2012 (MDT)
::::Oh derp. From the [http://cdn.arstechnica.net/wp-content/uploads/2012/10/apple_pschiller_a6.jpg keynote], it appears to be <code>APL5498</code> which is <code>8945</code> ([[S5L8945|A5X]]). But I am sure it will be <code>S5L8955</code>. The <code>[[S5L8942]]</code> was a revised A5, not A5X. It appears Apple just opened their Photoshop document and changed the <code>A5X</code> to <code>A6X</code>. Guess we'll find out for sure from a Geekbench or the teardown. We can at least for sure add the iPad mini to the page. --[[User:5urd|5urd]] 11:36, 25 October 2012 (MDT)

== Mirror sign ==
I would like to request that the mirror message is removed as its not needed. --[[User:Adaminsull|Adaminsull]] ([[User talk:Adaminsull|talk]]) 20:54, 23 December 2012 (UTC)
:I agree --[[User:Jaggions|Jaggions]] ([[User talk:Jaggions|talk]]) 08:06, 10 January 2013 (UTC)

== Jailbreak table ==
I saw it says iPad 4s this should be iPad 4's as it looks like a lazy way of iPad 4S. --[[User:Adaminsull|adaminsull]] ([[User talk:Adaminsull|talk]]) 16:35, 2 January 2013 (UTC)
:That would be improper grammar. I '''hate''' when people say "iPhone 3Gs" and mean the 3GS as well, but that's just how English is. Besides, at this time, an "iPad 4S" hasn't been released, so there's nothing to confuse it with. --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 18:37, 2 January 2013 (UTC)
:: I know that but it'd be better to be showing as iPad 4's --[[User:Adaminsull|adaminsull]] ([[User talk:Adaminsull|talk]]) 18:46, 2 January 2013 (UTC)
:Proper grammar for the iPad 4S would be iPad 4S''es''. --[[User:5urd|5urd]] ([[User talk:5urd|talk]]) 21:42, 2 January 2013 (UTC)

== iPad mini vs. iPad mini 1G ==
I see that here it says iPad mini 1G. Please correct this to [[iPad mini]]. I have updated the other pages to this due to we do not say iPad 1G. --[[User:Adaminsull|adaminsull]] ([[User talk:Adaminsull|talk]]) 15:56, 15 January 2013 (UTC)
:No. We decided on that already. I know we currently don't say "iPad mini 1G", but this is to differentiate this from further versions. In the same manner like we say iPod touch, we mean all versions of iPod touches (overview page), but if we mean the first generation we have to use iPod touch 1G, although nobody said it then. We discussed that already. So please, if you want to make such far reaching changes, please ask first if everybody agrees to this change. Thanks. In case [[User:5urd|5urd]] forgot to revert any of your changes, please revert back to original one. There were so many changes going on in the last 30 hours that I couldn't follow all details. --[[User:Http|http]] ([[User talk:Http|talk]]) 23:25, 15 January 2013 (UTC)

== 6.1.3 jailbreak ==

6.1.3 is jailbreakable on old-bootroom 3GS's with sn0wbreeze 2.9.14 and tethered jailbreakable on other A4 devices. [[User:Beej|beej]] ([[User talk:Beej|talk]]) 22:38, 29 April 2013 (UTC)

Talk:Ipt

2012-11-06T15:47:13Z

Beej:

I disagree with deleting the ipt and iptx and iptxg pages (x=1..5). I created them when I just learned what it meant. I'm sure there are other such users out there that want to know this. Also, it's a nice short form to jump to the iPod touch pages. --[[User:Http|http]] 23:27, 5 November 2012 (MST)
: But wanting to know what "ipt" means doesn't likely lead one to try going to an "ipt" page. There doesn't need to be a page for every abbreviation in use. That's what search is for. I say nuke 'em :) [[User:Beej|beej]] 08:47, 6 November 2012 (MST)

User talk:Beau

2012-10-03T21:45:38Z

Beej:

hi Beau, i'm thankful for your theiphonewiki twitter bot :) is it a known issue that it'll often post duplicates and updates out of order? --[[User:Beej|Beej]] 23:39, 28 December 2010 (UTC)
:Hey Beej! Sorry for the incredibly delayed reply, I've been lazy. I believe I've fixed the twitter bots now; originally it was a caching problem but now I believe I've fixed it. If there's any more problems, don't hesitate to shout! --[[User:Beau|Beau]] 11:23, 9 January 2011 (UTC)
::Hey. We are still getting duplicate tweets. --[[User:Toddyt1|Toddyt1]] 20:12, 9 January 2011 (UTC)
:::yep. i'm still seeing problems. eg: http://twitter.com/#!/theiphonewiki currently shows 2 tweets with different bit.ly shortened URL's for the same update: http://bit.ly/i4tasm and http://bit.ly/hEEX4i --[[User:Beej|Beej]] 00:06, 13 January 2011 (UTC)
:::: Hey ToddyT and Beej; this is by design. If a page has had multiple changes, there will be a separate tweet with a link pointing to that 'difference' of the wiki page. However, I did just notice thanks to you Beej, that there seems to be duplicate tweets with the different bit.ly URLS; one is www.theiphonewiki and the other is just theiphonewiki; I think this is due to whatever the editor was using to access the site and gets pushed through the RSS feed. I should be able to fix this.... 'should'! Bear with me. :) --[[User:Beau|Beau]] 00:13, 13 January 2011 (UTC)
::::: hi Beau. I still see occasional dupes. Also, yesterday, a few tweets went out with no links. Known issues? --[[User:Beej|beej]] 18:09, 24 February 2011 (UTC)
:::::Hi. There are still duplicates. Like this minor change I made that resulted in two tweets. Here the links to the tweets: [http://twitter.com/#!/theiphonewiki/status/74818641161502721] [http://twitter.com/#!/theiphonewiki/status/74828700956368896] As you can see they show both the same edit (''/wiki/index.php?title=Cmw&diff=18275&oldid=prev'') but once with domain ''<nowiki>http://www.theiphonewiki.com/</nowiki>'' and one with ''<nowiki>http://theiphonewiki.com/</nowiki>''. It would be great if you could fix that. -- [[User:Http|http]] 19:29, 29 May 2011 (UTC)
::::::I'll see what I can do; unfortunately this is how MediaWiki posts to the Recent Changes RSS Feed. Ragh!--[[User:Beau|Beau]] 07:49, 4 June 2011 (UTC)
:::::::Hi, Beau. Have you had a chance to take a look? If not, is the reason because you're out of cycles for this? If so, is there anyway somebody else could help? Cheers! [[User:Beej|beej]] 13:31, 9 July 2011 (UTC)
:::::::Do you use the ATOM or RSS feed. That might be the problem. --[[User:Balloonhead66|Balloonhead66]] 16:12, 9 July 2011 (UTC)
@Balloonhead66: Yeah I use the RSS feed (theiphonewiki.com/wiki/index.php?title=Special:RecentChanges&feed=atom); as far as I know there's no other public way to access the recent changes. If you know of a way, please do let me know! [[User:Beau|Beau]] 23:14, 17 July 2011 (MDT)
:It's okay, Beau. The emotional scars I have from having my questions ignored should eventually heal ;P The reason I asked them is that perhaps there are wikimedia devs who'd like to collaborate with you. What you created is obviously insanely useful or we wouldn't be having this discussion :) What say ye? [[User:Beej|beej]] 04:42, 19 July 2011 (MDT)
::Sorry. I suffer from lazy :-P Basically, that'd be nice if I had a nice way to pull data (in this case, recent changes) from sites and use it for Twitter, etc. If i wanted, it would be possible to perhaps do some filtering, e.g. skip all URLs containing www. But for whatever reason, maybe there'll only be an entry on www and not .theiphonewiki. So it's possible, but I wouldn't know if it might drop some entries, etc. Sigh! [[User:Beau|Beau]] 05:20, 19 July 2011 (MDT)
:::I think your pull hack has been very useful, but it's time to graduate to a real solution. I was hoping that you'd be interested in getting real push-based twitter feed support into the wikimedia tree. That clearer? :) [[User:Beej|beej]] 06:51, 19 July 2011 (MDT)
:::Beau: I see you made a recent wiki edit, so you're obviously still around. Just nod if you can hear me :) [[User:Beej|beej]] 12:23, 7 August 2011 (MDT)

== dead twitter bot ==

Beau: the bot seems to have died :( 19 days since last post. help? --[[User:Beej|beej]] 11:38, 11 May 2012 (MDT)
:Sorry for the delay in replying. I've been a little bit busy... and AWOL. The server that the script was running on died the other month, and I've been too scared to look at the backups to make sure I do actually have a copy that works of the script. I'll try and get around to looking this week. Sorry again --[[User:Beau|Beau]] 01:22, 12 June 2012 (MDT)
::The bot lives again! :D Thanks for fixing it. Care to respond to the other threads above? [[User:Beej|beej]] 15:45, 3 October 2012 (MDT)

User talk:Beau

2012-05-11T17:38:29Z

Beej: /* dead twitter bot */ new section

The iPhone Wiki:Community portal

2012-04-16T14:20:25Z

Beej: /* Site problems, part deux */

{{Talk Archive|2010|2011|2012}}
This is the place to post tasks that need to be done on the wiki. Also this is the place for proposed changes. I heard about people wanting a favicon and arranging the main page into categories.

== Site Related Requests ==
=== AcidSn0w ===
Can I propose a page for acidsn0w? I heard that there was stolen code, so I haven't posted. --[[User:Dylan Laws|Dylan Laws]] 17:02, 17 January 2012 (MST)
:The first beta did use stolen code, but the second beta fixed that. As it is still in beta, a page may not be a good idea. It does have a good user-base as shown in their blog comments, but it is up to the sysops. If you are in the Pwn Dev Team, then NO. --[[User:5urd|5urd]] 17:09, 17 January 2012 (MST)
:: I am not in their team. :P I'll wait till/if they release it. --[[User:Dylan Laws|Dylan Laws]] 17:37, 17 January 2012 (MST)
:::I want to make something clear about this wiki, it's called "The iPhone Wiki", not "The iPhone Community Wiki", or even "The Jailbreaking Wiki". This site exists to document the iPhone, not who made what GUI. A jailbreak tool that doesn't introduce exploits or isn't very widely used isn't notable. To clarify, the [[Limera1n_Exploit]] page is far more valuable than the [[limera1n]] page. Please focus on adding technical content instead of thinly veiled advertisements. For example, it's appalling we don't have a page documenting [[ASLR]] --[[User:Geohot|geohot]] 23:16, 17 January 2012 (MST)
:::I would also like to see the Baseband ticket system documented --[[User:Geohot|geohot]] 14:48, 18 January 2012 (MST)

=== 2.2b1 ===
Is 2.2b1 5G26 or 5G27, because on [[Beta Firmware]], it says 5G27 while on the previous revisions of [[VFDecrypt Keys]] is said 5G26 --[[User:balloonhead66|5urd]] 18:47, 14 January 2012 (MST)

=== IMG3 File Key Grabbing ===
How does one grab the keys for the IMG3 files if they have a decrypted ramdisk? I have genpass, xpwn, and vfdecrypt, but what do I use to get keys for IMG3 files? --[[User:5urd|5urd]] 17:17, 2 February 2012 (MST)
:Unlike the vfdecrypt key, the keys for decrypting the [[IMG3_File_Format#Tags | IMG3]] are stored encrypted in the [[KBAG]] section of the IMG3 file itself, not the ramdisk. These keys are encrypted using the [[GID-key]], so access to the AES engine is required. On a device compatible with greenpois0n or openiBoot, this process is (loosely) documented [[AES_Keys#Running_The_Engine | here]]. I am working on implementing a method that can be performed on a jailbroken 4S or iPad 2 (is that is what you're looking for?) and will release when finished --[[User:0x56|0x56]] 20:12, 1 March 2012 (MST)
::Yah, running greenpois0n is my problem. I cant find the program. --[[User:5urd|5urd]] 21:02, 1 March 2012 (MST)
:::I was mistaken, I won't be able to accomplish this for the 4S or iPad 2 due to a limitation that was not documented here --[[User:0x56|0x56]] 07:00, 5 March 2012 (MST)

=== iPad2,4 ===
Should we call it <code>iPad 2 Wi-Fi R2</code> or <code>iPad 2 Wi-Fi S5L8942</code> on the key pages? --[[User:5urd|5urd]] 18:59, 8 March 2012 (MST)
:Personally, I like how "iPad 2 Wi-Fi S5L8942" sounds more. It could be truncated to "iPad 2 S5L8942" or something if people think the name is too long. --[[User:Dialexio|Dialexio]] 20:07, 8 March 2012 (MST)
::I would not remove the Wi-Fi part, because if there's ever a 3G version, we would have to rename everything. I would prefer a shorter name like R2 or so. Also because S5L is the processor and not a public device name. Something official? Is there no statement from Apple yet? Maybe we should wait a few days until it's out? Or is there anything that can't wait so long? --[[User:Http|http]] 00:18, 9 March 2012 (MST)
:::Apple's marketing it as the same old iPad 2. (Interestingly, Apple's online store does suggest that the all flavors of the iPad 2 have new model numbers.) Apple will still sell 3G versions of the iPad 2, but we haven't seen any "iPad2,5" firmware or something… Just the "iPad2,4." If the 3G iPads were receiving the S5L8942, their unique firmwares probably would've been pushed on http://itunes.com/version on Wednesday like all of the other devices. --[[User:Dialexio|Dialexio]] 10:25, 9 March 2012 (MST)
::I personally like R2 as it is shorter and easier to remember. I will change [[Template:Keys]] accordingly. --[[User:5urd|5urd]] 16:21, 9 March 2012 (MST)

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

=== iPad 3 ===
I opened up the Build Manifest on the iPad3,2 firmware and it says it is j2ap. The iPad3,3 firmware says j2aap. j1ap is correct for the Wi-Fi version. So... what? --[[User:5urd|5urd]] 17:35, 9 March 2012 (MST)

=== Deletion Requests ===
Can we clean up the deletion requests category? --[[User:5urd|5urd]] 20:15, 10 March 2012 (MST)

=== Site problems, part deux ===
I'm noticing a lot of intermittent 500 errors again, anyone else notice this issue? [[User:Acfrazier|Austen Frazier]] 08:15, 13 March 2012 (MDT)
:Yep. The server is definitely choking, again. --[[User:Beej|beej]] 08:41, 13 March 2012 (MDT)
::It seems much better, now. Anybody know what changed? Maybe the vm was moved to different host or another busy vm sharing this host was moved off? --[[User:Beej|beej]] 08:20, 16 April 2012 (MDT)
:I think it's time to move skin assets to a cdn like Amazon for speed (like Wikipedia's bits.wikimedia.org) and use a better cache like [[mediawikiwiki:memcached|memcached]]. [[User:thekirbylover|the]][[User talk:thekirbylover|kirby]][[Special:Contributions/thekirbylover|lover]] 17:49, 13 March 2012 (MDT)

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

UDID

2012-03-23T19:25:53Z

Beej: s/my/a/

[[UDID]] is the short form for '''U'''nique '''D'''evice '''Id'''entifier. It is a 40-character long hex value (20 bytes). The [[UDID]] is being used by developers to register devices for testing their Apps. Only on registered devices developers can run Apps that are not in Apple's AppStore yet. Also, beta firmware can be installed only on registered devices. Developers currently have 100 [[UDID]]s they can register. The UDID can actually be changed and back again if you run this command followed by a DFU restore or else iTunes cannot read the device (corruption?). Keep a backup, you can always revert the change with the original MAC. As shown here on a iPod 4TH Gen; http://twitpic.com/9015lw Command:

nvram wifiaddr=ma:ca:dd:re:as
- User notice: This will change your UDID, anything UDID related will need to be re-"logined", Apple related apps will always need to be logined.

Instead of calculating the value, it can be read from [[iTunes]], when the device is connected, by clicking on the text '''Serial Number'''.

== Calculation ==
The [[UDID]] is being calculated like this:
*Create a 60-character long or 59-character long (on newer devices) text string (see below)
*Calculate the [[wikipedia:SHA-1|SHA1]] hash of the text string. The result is the [[UDID]].

To create the text string, append the following four strings:
*11-character long or 12-character long (on newer devices) '''serial number''' (exactly like it is written in the Settings app)
*15-character long '''IMEI number''' (without spaces); empty string for iPod touch and Wi-Fi model iPads (on older devices) OR on newer devices 13-character long "ECID" in decimal (like shown in Xcode)
*17-character long '''Wi-Fi MAC address''' (letters in lower case, including colons); for the [[N45ap|iPod touch first generation]] use "00:00:00:00:00:00"
*17-character long '''Bluetooth MAC address''' (letters in lower case, including colons)

== In short ==
For older devices:
UDID = SHA1($serial + $IMEI + $WiFiMac + $BluetoothMac)

On the [[N92ap|Verizon iPhone 4]] and newer it is instead computed with this formula:
UDID = SHA1($serial + $ECID + $WiFiMac + $BluetoothMac)

Talk:List of iPads

2012-03-21T21:42:22Z

Beej:

== Original iPad ==

Shouldn't we have two columns for the two original iPad models in the pursuit of consistency? --[[User:Beej|beej]] 07:32, 20 March 2012 (MDT)
:Both the Wi-Fi and 3G versions of the original iPad identified themselves as "iPad1,1" and "k48ap," which was why they shared the same column. I suppose it could be split into two different columns though. --[[User:Dialexio|Dialexio]] 14:12, 20 March 2012 (MDT)
::Thanks for doing the split. I like it :) --[[User:Beej|beej]] 15:42, 21 March 2012 (MDT)

== GPS ==

What's the reasoning behind two different rows for GPS and aGPS? It look like redundant info, no? --[[User:Beej|beej]] 15:42, 21 March 2012 (MDT)

Talk:Kernel Syscalls

2012-03-20T15:08:11Z

Beej: /* OS thinko? */ new section

i dont know if its right, pls correct me if im wrong :) --[[User:Zmaster|Zmaster]] 13:58, 29 November 2011 (MST)

<del>
HTTP/i0nic:
The following is hardly "bogus".
0x30d2ad54 <chown>: mov r12, #16 ; 0x10, being # of chown
0x30d2ad58 <chown+4>: svc 0x00000080
is a direct disassembly of libSystem. You can see that with gdb on a jb device.
</del>

<del>SVC is an ARM instruction to invoke a "supervisor call". The 0x80 is the call #, because the chip allows an interrupt vector, much like Intel's INT instruction. Then, you place the syscall # (in the above example, chown) in r12. [[User:morpheus|morpheus]] ||3/1/2012, 20:01 EST.
</del>

-- Edit:

OOOOOH. Now I get it. He meant the CPU syscalls, not the kernel syscalls. This needs more research (who originally put that part?) {{unsigned|morpheus|2 Mar 2012 02:04 UTC}}
:Look at page history. It seems like it came from [[User:ChronicDev|Chronic]]? Hardly imaginable he entered wrong infos. Maybe just very outdated? I have too few experience with ARM and kernel to contribute here. Feel free to remove wrong infos or just mention where it belongs to. --[[User:Http|http]] 01:14, 2 March 2012 (MST)

== OS thinko? ==

Morpheus: when you wrote "Most of these syscalls are the same as those of iOS" did you mean to write "Most of these syscalls are the same as those of OS X"? Weren't we already talking about iOS at the time? --[[User:Beej|beej]] 09:08, 20 March 2012 (MDT)

Talk:List of iPads

2012-03-20T13:32:57Z

Beej: Original iPad

== Original iPad ==

Shouldn't we have two columns for the two original iPad models in the pursuit of consistency? --[[User:Beej|beej]] 07:32, 20 March 2012 (MDT)

User talk:Dialexio

2012-03-20T13:31:12Z

Beej: Undo revision 25229 by Beej (talk)

{{float toc}}
'''If you have questions/concerns about an edit I made to an article, please use the talk page for the article in question.'''

==Baseband Help==
hey i need help {{unsigned|Leobruh|03:35, March 29, 2010 (UTC)}}
:with...? {{unsigned|Gojohnnyboi|04:00, March 29, 2010 (UTC)}}
::im trying to learn how to find baseband exploits but i need some PC friendly tools to find those baseband exploits [[User:Leobruh|Leobruh]]!
:::I can't help you there, sorry. --[[User:Dialexio|Dialexio]] 15:06, 24 June 2010 (UTC)

==Rant deletion==
alright i agree with what u did. [[User:Leobruh|Leobruh]] 04:39, 3 July 2010 (UTC)!

==Thanks==
Thanks for curating this wiki by wikifying paragraphs and adding tons of relevant, accurate, and grammatically correct info. :) [[User:Iemit737|Iemit737]] 01:00, 14 July 2010 (UTC)
:Thanks! You've done a pretty amazing job also. :D --[[User:Dialexio|Dialexio]] 02:50, 14 July 2010 (UTC)

==Presentation links==
Thanks for adding those HQ torrent links, probably better than my FLV anyway ;) [[User:MaybachMan|MaybachMan]] 22:06, 14 July 2010 (UTC)

... And once again for the Bluetooth additions. I'll shut up now ;) [[User:MaybachMan|MaybachMan]] 22:14, 14 July 2010 (UTC)

==Beta Firmwares==
should we start a beta firmwares page that contains a table with release dates, baseband versions, and iboot versions but without links? It might be interesting for reference purposes, and a good way to link to the decryption keys. [[User:Iemit737|Iemit737]] 03:53, 20 July 2010 (UTC)
:I suppose this could be done (at [[Firmware/Beta]]?). I don't think hashes should be provided, though. A hash will probably only serve to help idiots pirate, verify, and install a beta firmware. --[[User:Dialexio|Dialexio]] 04:57, 20 July 2010 (UTC)

==Sysop Status==
You are now a sysop. --[[User:Geohot|geohot]] 15:32, 21 July 2010 (UTC)
:Thanks geohot! I'll be sure to do the best I can. --[[User:Dialexio|Dialexio]] 21:48, 21 July 2010 (UTC)

==Q==
idc if the link is there or not
u can C&P my paragraph to keep people informed [[User:Leobruh|Leobruh]] 05:37, 25 August 2010 (UTC)!
:What do you mean with Q, idc, C&P? Ah, and yes, I agree that he deleted the advertisement page you made. It doesn't really belong into this wiki and the page had no content except the link to your blog. -- [[User:Http|http]] 10:34, 25 August 2010 (UTC)
::C&P is copy and paste :P if i just copy my post will that be okay? [[User:Leobruh|Leobruh]] 17:10, 25 August 2010 (UTC)!
::: I feel that there isn't much (if anything) to be concerned about, so I don't believe the article is needed. Those are just my thoughts, though. --[[User:Dialexio|Dialexio]] 15:24, 26 August 2010 (UTC)

== likes ==
i like you --[[User:Ifish|Ifish]] 03:39, 31 August 2010 (UTC)ifish

== :) ==
You're awesome! --[[User:desertsn0w|desertsn0w]] 17:57, 5 September 2010 (UTC)

== Twitter ==
Hey since weve had problems here, I sent you a Twitter request because we sortove know eachother. :D [[User:Balloonhead66|Balloonhead66]] 00:22, 7 October 2010 (UTC)

== Birthday ==

happy birthday [[User:Balloonhead66|Balloonhead66]] 22:48, 7 October 2010 (UTC)
:Thanks! ^_^ --[[User:Dialexio|Dialexio]] 23:42, 7 October 2010 (UTC)

Happy Birthday Buddy! <3 --[[User:Ifish|Ifish]] 18:20, 9 October 2010 (UTC)ifish

== Signing posts ==
Sorry if you get upse while seeing unsigned posts. I try my best -- Balloonhead66| 23:58, October 8, 2010 (UTC)
:I am not amused. :P --[[User:Dialexio|Dialexio]] 00:02, 9 October 2010 (UTC)
::OK, I did that on accident, but when you are also updating a page with a lot of posting like [[Talk:Limera1n|Limera1n Talk]] It is hard because 1 second could be the differance between yours getting accepted and another person beating you to the save button, sorry :( [[User:Balloonhead66|Balloonhead66]] 00:04, 9 October 2010 (UTC)

==PNG to IMG3==
Hey, Why did you remove my project PNG TO IMG3 Thanks --[[User:Seifhatem|Seifhatem]] 20:20, 10 February 2011 (UTC)
:There was no link to the program, and we've had some problems in the past when it came to program pages on The iPhone Wiki. If you feel your program is notable enough to be on the wiki, drop a note in the [[The iPhone Wiki:Community Portal|community portal]], and then any active community members will decide. --[[User:Dialexio|Dialexio]] 21:44, 10 February 2011 (UTC)
:I don't get why it is in the [[VFDecrypt]] section if it deals with PNG's and IMG3's as [[VFDecrypt]] only deals with FileVault encrypted files... --[[User:Balloonhead66|Balloonhead66]] 22:37, 10 February 2011 (UTC)
:Please see also the [[:Category:GUI Tools|new rules]] for such tools in this wiki. --[[User:Http|http]] 00:39, 11 February 2011 (UTC)
::there was a 4shared link for the program and i wrote credits for img3decrypt someone changed it to vfdecrypt i didn't announce before i release it.--[[User:Seifhatem|Seifhatem]] 13:12, 11 February 2011 (UTC)
:I apologize for hastily calling the program vaporware. The download link wasn't made available on the page, just the VFDecrypt page (on which it didn't quite belong, as Balloonhead66 mentioned). --[[User:Dialexio|Dialexio]] 15:22, 11 February 2011 (UTC)
::[http://theiphonewiki.com/wiki/index.php?title=VFDecrypt&diff=prev&oldid=15965 this edit] to [[VFDecrypt]] says that is is coded on VFDevcrypt, '''NOT''' img3decrypt {{unsigned|Balloonhead66|20:11, February 11, 2011 (UTC)}}
:::The PNG to IMG3 page stated it was based on img3decrypt. --[[User:Dialexio|Dialexio]] 20:34, 11 February 2011 (UTC)
::::I get that, but the edit said VFDecrypt, so it is confusing. --[[User:Balloonhead66|Balloonhead66]] 20:37, 11 February 2011 (UTC)

== Messed up emails ==
Why did you hide you email in some stuff. Is it to prevent spam? --[[User:Balloonhead66|Balloonhead66]] 17:18, 12 July 2011 (UTC)
:Yup. Spam bots will have a lot of fun trying to read the source code. ;) --[[User:Dialexio|Dialexio]] 17:19, 12 July 2011 (UTC)
::Makes sense. --[[User:Balloonhead66|Balloonhead66]] 17:21, 12 July 2011 (UTC)
:::Advanced spam bots just filter that stuff away, and even better ones also the visible:none parts, so you're not totally safe. Just as a warning. -- [[User:Http|http]] 19:24, 12 July 2011 (UTC)
::::I never expected it to be fool-proof. :P Oh well. --[[User:Dialexio|Dialexio]] 20:02, 12 July 2011 (UTC)

== Password ==
For the only user I created so far I have set a temp password, but he already changed it before I gave it to him, so I think we don't need to request a temp password, just set something. -- [[User:Http|http]] 19:24, 12 July 2011 (UTC)
:Got it. --[[User:Dialexio|Dialexio]] 20:02, 12 July 2011 (UTC)

== GenPass ==
You said to try it out yourself, but I don't have GenPass compiled and MinGW or Visual Studio won't compile it for me. Do you have a copy? --[[User:Balloonhead66|Balloonhead66]] 18:54, 16 December 2011 (MST)
:Nope. It should compile fine in a Linux VM, though. But take my word for it, the "x" is needed to get the correct VFDecrypt key. --[[User:Dialexio|Dialexio]] 19:26, 16 December 2011 (MST)

==CSS Change==
In chrome the bottom and sidebar are white and the side text is unreadable --[[User:Geohot|geohot]] 21:02, 8 January 2012 (MST)
:Sorry about that; I didn't pay enough attention to the CSS that was deleted. The links are readable once more, but the logo reflection in WebKit browsers is a bit off. --[[User:Dialexio|Dialexio]] 21:36, 8 January 2012 (MST)
::No problem, spotted the unmatched brace at the same time, went to edit, and saw it'd been fixed. At least I understand MW css a bit better. --[[User:Geohot|geohot]] 21:38, 8 January 2012 (MST)

User talk:Dialexio

2012-03-20T13:28:05Z

Beej: /* Original iPad */ new section

Bypassing Jailbreak Detection

2012-03-20T02:12:00Z

Beej: 5urd: it's been in Cydia for some time

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

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

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

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

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

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

== App Patching Status ==
''To-do''

The iPhone Wiki:Community portal

2012-03-17T23:38:58Z

Beej:

{{Talk Archive|2010|2011|2012}}
This is the place to post tasks that need to be done on the wiki. Also this is the place for proposed changes. I heard about people wanting a favicon and arranging the main page into categories.

== Site Related Requests ==
=== AcidSn0w ===
Can I propose a page for acidsn0w? I heard that there was stolen code, so I haven't posted. --[[User:Dylan Laws|Dylan Laws]] 17:02, 17 January 2012 (MST)
:The first beta did use stolen code, but the second beta fixed that. As it is still in beta, a page may not be a good idea. It does have a good user-base as shown in their blog comments, but it is up to the sysops. If you are in the Pwn Dev Team, then NO. --[[User:5urd|5urd]] 17:09, 17 January 2012 (MST)
:: I am not in their team. :P I'll wait till/if they release it. --[[User:Dylan Laws|Dylan Laws]] 17:37, 17 January 2012 (MST)
:::I want to make something clear about this wiki, it's called "The iPhone Wiki", not "The iPhone Community Wiki", or even "The Jailbreaking Wiki". This site exists to document the iPhone, not who made what GUI. A jailbreak tool that doesn't introduce exploits or isn't very widely used isn't notable. To clarify, the [[Limera1n_Exploit]] page is far more valuable than the [[limera1n]] page. Please focus on adding technical content instead of thinly veiled advertisements. For example, it's appalling we don't have a page documenting [[ASLR]] --[[User:Geohot|geohot]] 23:16, 17 January 2012 (MST)
:::I would also like to see the Baseband ticket system documented --[[User:Geohot|geohot]] 14:48, 18 January 2012 (MST)

=== 2.2b1 ===
Is 2.2b1 5G26 or 5G27, because on [[Beta Firmware]], it says 5G27 while on the previous revisions of [[VFDecrypt Keys]] is said 5G26 --[[User:balloonhead66|5urd]] 18:47, 14 January 2012 (MST)

=== IMG3 File Key Grabbing ===
How does one grab the keys for the IMG3 files if they have a decrypted ramdisk? I have genpass, xpwn, and vfdecrypt, but what do I use to get keys for IMG3 files? --[[User:5urd|5urd]] 17:17, 2 February 2012 (MST)
:Unlike the vfdecrypt key, the keys for decrypting the [[IMG3_File_Format#Tags | IMG3]] are stored encrypted in the [[KBAG]] section of the IMG3 file itself, not the ramdisk. These keys are encrypted using the [[GID-key]], so access to the AES engine is required. On a device compatible with greenpois0n or openiBoot, this process is (loosely) documented [[AES_Keys#Running_The_Engine | here]]. I am working on implementing a method that can be performed on a jailbroken 4S or iPad 2 (is that is what you're looking for?) and will release when finished --[[User:0x56|0x56]] 20:12, 1 March 2012 (MST)
::Yah, running greenpois0n is my problem. I cant find the program. --[[User:5urd|5urd]] 21:02, 1 March 2012 (MST)
:::I was mistaken, I won't be able to accomplish this for the 4S or iPad 2 due to a limitation that was not documented here --[[User:0x56|0x56]] 07:00, 5 March 2012 (MST)

=== iPad2,4 ===
Should we call it <code>iPad 2 Wi-Fi R2</code> or <code>iPad 2 Wi-Fi S5L8942</code> on the key pages? --[[User:5urd|5urd]] 18:59, 8 March 2012 (MST)
:Personally, I like how "iPad 2 Wi-Fi S5L8942" sounds more. It could be truncated to "iPad 2 S5L8942" or something if people think the name is too long. --[[User:Dialexio|Dialexio]] 20:07, 8 March 2012 (MST)
::I would not remove the Wi-Fi part, because if there's ever a 3G version, we would have to rename everything. I would prefer a shorter name like R2 or so. Also because S5L is the processor and not a public device name. Something official? Is there no statement from Apple yet? Maybe we should wait a few days until it's out? Or is there anything that can't wait so long? --[[User:Http|http]] 00:18, 9 March 2012 (MST)
:::Apple's marketing it as the same old iPad 2. (Interestingly, Apple's online store does suggest that the all flavors of the iPad 2 have new model numbers.) Apple will still sell 3G versions of the iPad 2, but we haven't seen any "iPad2,5" firmware or something… Just the "iPad2,4." If the 3G iPads were receiving the S5L8942, their unique firmwares probably would've been pushed on http://itunes.com/version on Wednesday like all of the other devices. --[[User:Dialexio|Dialexio]] 10:25, 9 March 2012 (MST)
::I personally like R2 as it is shorter and easier to remember. I will change [[Template:Keys]] accordingly. --[[User:5urd|5urd]] 16:21, 9 March 2012 (MST)

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

=== iPad 3 ===
I opened up the Build Manifest on the iPad3,2 firmware and it says it is j2ap. The iPad3,3 firmware says j2aap. j1ap is correct for the Wi-Fi version. So... what? --[[User:5urd|5urd]] 17:35, 9 March 2012 (MST)

=== Deletion Requests ===
Can we clean up the deletion requests category? --[[User:5urd|5urd]] 20:15, 10 March 2012 (MST)

=== Site problems, part deux ===
I'm noticing a lot of intermittent 500 errors again, anyone else notice this issue? [[User:Acfrazier|Austen Frazier]] 08:15, 13 March 2012 (MDT)
:Yep. The server is definitely choking, again. --[[User:Beej|beej]] 08:41, 13 March 2012 (MDT)
:I think it's time to move skin assets to a cdn like Amazon for speed (like Wikipedia's bits.wikimedia.org) and use a better cache like [[mediawikiwiki:memcached|memcached]]. [[User:thekirbylover|the]][[User talk:thekirbylover|kirby]][[Special:Contributions/thekirbylover|lover]] 17:49, 13 March 2012 (MDT)

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

The iPhone Wiki:Community portal

2012-03-13T14:41:49Z

Beej: /* Site problems, part deux */

{{Talk Archive|2010|2011|2012}}
This is the place to post tasks that need to be done on the wiki. Also this is the place for proposed changes. I heard about people wanting a favicon and arranging the main page into categories.

== Site Related Requests ==
=== AcidSn0w ===
Can I propose a page for acidsn0w? I heard that there was stolen code, so I haven't posted. --[[User:Dylan Laws|Dylan Laws]] 17:02, 17 January 2012 (MST)
:The first beta did use stolen code, but the second beta fixed that. As it is still in beta, a page may not be a good idea. It does have a good user-base as shown in their blog comments, but it is up to the sysops. If you are in the Pwn Dev Team, then NO. --[[User:5urd|5urd]] 17:09, 17 January 2012 (MST)
:: I am not in their team. :P I'll wait till/if they release it. --[[User:Dylan Laws|Dylan Laws]] 17:37, 17 January 2012 (MST)
:::I want to make something clear about this wiki, it's called "The iPhone Wiki", not "The iPhone Community Wiki", or even "The Jailbreaking Wiki". This site exists to document the iPhone, not who made what GUI. A jailbreak tool that doesn't introduce exploits or isn't very widely used isn't notable. To clarify, the [[Limera1n_Exploit]] page is far more valuable than the [[limera1n]] page. Please focus on adding technical content instead of thinly veiled advertisements. For example, it's appalling we don't have a page documenting [[ASLR]] --[[User:Geohot|geohot]] 23:16, 17 January 2012 (MST)
:::I would also like to see the Baseband ticket system documented --[[User:Geohot|geohot]] 14:48, 18 January 2012 (MST)

=== 2.2b1 ===
Is 2.2b1 5G26 or 5G27, because on [[Beta Firmware]], it says 5G27 while on the previous revisions of [[VFDecrypt Keys]] is said 5G26 --[[User:balloonhead66|5urd]] 18:47, 14 January 2012 (MST)

=== IMG3 File Key Grabbing ===
How does one grab the keys for the IMG3 files if they have a decrypted ramdisk? I have genpass, xpwn, and vfdecrypt, but what do I use to get keys for IMG3 files? --[[User:5urd|5urd]] 17:17, 2 February 2012 (MST)
:Unlike the vfdecrypt key, the keys for decrypting the [[IMG3_File_Format#Tags | IMG3]] are stored encrypted in the [[KBAG]] section of the IMG3 file itself, not the ramdisk. These keys are encrypted using the [[GID-key]], so access to the AES engine is required. On a device compatible with greenpois0n or openiBoot, this process is (loosely) documented [[AES_Keys#Running_The_Engine | here]]. I am working on implementing a method that can be performed on a jailbroken 4S or iPad 2 (is that is what you're looking for?) and will release when finished --[[User:0x56|0x56]] 20:12, 1 March 2012 (MST)
::Yah, running greenpois0n is my problem. I cant find the program. --[[User:5urd|5urd]] 21:02, 1 March 2012 (MST)
:::I was mistaken, I won't be able to accomplish this for the 4S or iPad 2 due to a limitation that was not documented here --[[User:0x56|0x56]] 07:00, 5 March 2012 (MST)

=== iPad2,4 ===
Should we call it <code>iPad 2 Wi-Fi R2</code> or <code>iPad 2 Wi-Fi S5L8942</code> on the key pages? --[[User:5urd|5urd]] 18:59, 8 March 2012 (MST)
:Personally, I like how "iPad 2 Wi-Fi S5L8942" sounds more. It could be truncated to "iPad 2 S5L8942" or something if people think the name is too long. --[[User:Dialexio|Dialexio]] 20:07, 8 March 2012 (MST)
::I would not remove the Wi-Fi part, because if there's ever a 3G version, we would have to rename everything. I would prefer a shorter name like R2 or so. Also because S5L is the processor and not a public device name. Something official? Is there no statement from Apple yet? Maybe we should wait a few days until it's out? Or is there anything that can't wait so long? --[[User:Http|http]] 00:18, 9 March 2012 (MST)
:::Apple's marketing it as the same old iPad 2. (Interestingly, Apple's online store does suggest that the all flavors of the iPad 2 have new model numbers.) Apple will still sell 3G versions of the iPad 2, but we haven't seen any "iPad2,5" firmware or something… Just the "iPad2,4." If the 3G iPads were receiving the S5L8942, their unique firmwares probably would've been pushed on http://itunes.com/version on Wednesday like all of the other devices. --[[User:Dialexio|Dialexio]] 10:25, 9 March 2012 (MST)
::I personally like R2 as it is shorter and easier to remember. I will change [[Template:Keys]] accordingly. --[[User:5urd|5urd]] 16:21, 9 March 2012 (MST)

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

=== iPad 3 ===
I opened up the Build Manifest on the iPad3,2 firmware and it says it is j2ap. The iPad3,3 firmware says j2aap. j1ap is correct for the Wi-Fi version. So... what? --[[User:5urd|5urd]] 17:35, 9 March 2012 (MST)

=== Deletion Requests ===
Can we clean up the deletion requests category? --[[User:5urd|5urd]] 20:15, 10 March 2012 (MST)

=== Site problems, part deux ===
I'm noticing a lot of intermittent 500 errors again, anyone else notice this issue? [[User:Acfrazier|Austen Frazier]] 08:15, 13 March 2012 (MDT)
:Yep. The server is definitely choking, again. --[[User:Beej|beej]] 08:41, 13 March 2012 (MDT)

Greenpois0n (jailbreak)

2012-03-13T14:35:04Z

Beej: /* Controversy */ Fixed thinko

{{lowercase}}
[[Image:gp.png|200px|right|greenpois0n]]
{{other|jailbreak|toolkit|greenpois0n (toolkit)}}
The downloads for greenpois0n can be found on http://www.greenpois0n.com/. It is available for Windows and Mac.

== History ==
=== RC1 - RC4 ===
Greenpois0n was originally written using two exploits: SHAtter (a [[bootrom]] [[exploit]]) as well as a userland [[kernel]] [[exploit]] provided by [[User:Comex|Comex]] to make the jailbreak [[untethered jailbreak|untethered]]. A release date of 10/10/10 10:10:10 AM (GMT) was announced, as well as the list of supported devices. Due to the nature of SHAtter, only iDevices using the [[S5L8930|A4 Processor]] were supported.
[[user:geohot|geohot]] later released another jailbreak ([[limera1n]] using a different [[bootrom]] [[exploit]]) on 9 October 2010, which led to a delay in greenpois0n's release (to implement geohot's exploit, not SHAtter).

=== RC5 ===
[[User:Posixninja|Posixninja]] and the rest of [[Chronic Dev (team)|Chronic Dev]] released a Mac-exclusive version of greenpois0n RC5 on 3 February 2011, which performs an [[untethered jailbreak]] on iOS 4.2.1 for most devices that support it. Instead of using the [[Packet Filter Kernel Exploit]] like RC4 and earlier, RC5 made use of the [[HFS Legacy Volume Name Stack Buffer Overflow]]. (This exploit wasn't saved for iOS 4.3 because it was already fixed in the betas with an implementation of [[wikipedia:Address space layout randomization|ASLR]].) Bugs were found, and fixed, in subsequent builds. Two days later, on 5 February 2011, Chronic Dev released a Windows version as well.

=== RC6 ===
Support for the [[k66ap|Apple TV 2G]] was added. This release was for both Windows and Mac.

== Controversy ==
There was much controversy surrounding the sudden release of [[limera1n]] and the motives behind it. The main reasons for the [[limera1n]] release were:
* Use an exploit that Apple already knew about (newer [[iBoot]]s shows the exploit patched)
* Supports more iDevices than [[SHA-1 Image Segment Overflow|SHAtter]]
* Save the [[SHA-1 Image Segment Overflow|SHAtter]] [[bootrom]] [[exploit]] for future devices
The reason for this is [[bootrom]] [[exploit]]s are not patchable with software updates. It requires new hardware to fix the security hole. Since the [[limera1n]] hole was already discovered and patched by Apple, it benefits the community if SHAtter is saved in hopes of using it with new hardware, like the [[n92ap|iPhone 4S]], iPod touch 5G, and the [[iPad 2]]. However, Apple, presumably through internal testing, found out about [[SHA-1 Image Segment Overflow|SHAtter]] and patched it in the [[S5L8940|A5]] chip released with the [[iPad 2]].

== Supported Devices ==
greenpois0n RC4 and earlier requires the device to be on either iOS 3.2.2 ([[K48ap|iPad 1G]]) or iOS 4.1 (all other devices). Of the devices that support these firmware revisions, the only one ''not'' supported is the [[N82ap|iPhone 3G]].

greenpois0n RC5 requires the device to be on iOS 4.2.1. It is compatible with every device that has 4.2.1, except for the iPhone 3G. It was released earlier than anticipated, because iOS 4.3 unintentionally blocked the [[HFS Legacy Volume Name Stack Buffer Overflow‎]] exploit.

== Output ==
[[N90ap|iPhone 4]] with [[Greenpois0n (toolkit)|greenpois0n]] output (via [[iRecovery]]):
Attempting to initialize greenpois0n
Initializing commands
Searching for cmd_ramdisk
Found cmd_ramdisk string at 0x8401c7ac
Found cmd_ramdisk reference at 0x84000d64
Found cmd_ramdisk function at 0x84000cd1
Initializing patches
Initializing memory
Initializing aes
Searching for aes_crypto_cmd
Found aes_crypto_cmd string at 0x84021a8c
Found aes_crypto_cmd reference at 0x84017bb8
Found aes_crypto_cmd fnction at 0x84017b51
Initializing bdev
Initializing image
Initializing nvram
Initializing kernel
Greenpois0n initialized

[[Category:Hacking Software]]
[[Category:greenpois0n|jailbreak]]

KBAG

2012-03-06T23:38:52Z

Beej: the architecture is LE, not the company

==Explanation==
In Apple's new [[IMG3 File Format|IMG3]] security scheme, they have used something called a KBAG. At the bottom of a firmware file, you will see something that will, on the ASCII side of your hex editor, see "GABK", which, as ARM is {{wp|little-endian}} based, is "KBAG" flipped. Look on the hex side and you will the KBAG according to this format:

==KBAG Format==
===KBAG128===
typedef struct Unparsed_KBAG_128 {
int magic; // string with bits flipped = "KBAG" (magic = 0x4741424B)
int fullSize; // size of KBAG from beyond that point to the end of it
int tagDataSize; // size of KBAG without this 0xC header
int cryptState; // 1 if the key and IV in the KBAG are encrypted with the [[GID-key]]
// 2 is used with a second KBAG for the [[S5L8920]], use is unknown.
int aesType; // 0x80 = aes128 / 0xc0 = aes192 / 0x100 = aes256
char EncIV[16]; // IV for the firmware file, encrypted with the [[GID-key]]
char EncKey[16]; // Key for the firmware file, encrypted with the [[GID-key]]
} Unparsed_KBAG_AES128;

===KBAG192===
typedef struct Unparsed_KBAG_AES192 {
int magic; // string with bits flipped = "KBAG" (magic = 0x4741424B)
int fullSize; // size of KBAG from beyond that point to the end of it
int tagDataSize; // size of KBAG without this 0xC header
int cryptState; // 1 if the key and IV in the KBAG are encrypted with the [[GID-key]]
// 2 is used with a second KBAG for the [[S5L8920]], use is unknown.
int aesType; // 0x80 = aes128 / 0xc0 = aes192 / 0x100 = aes256
char EncIV[16]; // IV for the firmware file, encrypted with the [[GID-key]]
char EncKey[24]; // Key for the firmware file, encrypted with the [[GID-key]]
} Unparsed_KBAG_AES192;

===KBAG256===
typedef struct Unparsed_KBAG_256 {
int magic; // string with bits flipped = "KBAG" (magic = 0x4741424B)
int fullSize; // size of KBAG from beyond that point to the end of it
int tagDataSize; // size of KBAG without this 0xC header
int cryptState; // 1 if the key and IV in the KBAG are encrypted with the [[GID-key]]
// 2 is used with a second KBAG for the [[S5L8920]], use is unknown.
int aesType; // 0x80 = aes-128, 0xc0 = aes-192, 0x100 = aes256
char EncIV[16]; // IV for the firmware file, encrypted with the [[GID-key]]
char EncKey[32]; // Key for the firmware file, encrypted with the [[GID-key]]
} Unparsed_KBAG_AES256;

==How it works==
Basically, it just boils down to using the [[GID-key]] to decrypt Enc_IV and Enc_Key, then using that key and IV to decrypt the DATA section of the file (the code itself).

As an interesting side note, because of the circumstances with the [[IMG3 File Format]], the kernel never needs to even touch the [[GID-key]] anymore, as it's job is to just flash the image to the [[NOR]] as is, with container and all.

in order to decrypt the [[KBAG]] you need to remove them from [[IMG3 File Format|IMG3]] using this command <code>dd if=IMG3_FILE bs=1 skip=4741424B count=0x70</code>

[[Category:Firmware Tags]]

Brick

2012-03-04T06:41:42Z

Beej: Undo revision 24726 by ARC rapture (talk)

The term "bricked" refers to nonfunctional device states. Though nominally meaning that the device is permanently damaged, in practice it includes conditions which range from trivially recoverable (a failed update) to completely unrecoverable (in certain cases involving damaged baseband memory). A phone may be referred to as "bricked" if it will not boot, will not respond to input, will not make calls, etc. Early unlock solutions frequently resulted in partially-bricked phones after firmware updates were applied. Generally speaking, the iPhone is quite difficult to brick permanently via software, and in almost all cases the damage can be reversed.

== Irreversible Software Bricking ==
The only way to irreversibly brick your iDevice in software is to flash an invalid [[Baseband Bootloader|baseband bootloader]], provided it has a baseband. All other bad flash scenarios are recoverable some way or another. It is impossible to brick your device simply by [[jailbreak]]ing it, since [[DFU Mode]] will still be available to recover from a bad flash.

If you purposefully erase / zero out your [[NOR]], then you will even have trouble doing a DFU restore because important information from the SysCfg section will not be available.

AES Keys

2012-03-03T14:20:14Z

Beej: /* Key 0x89B */

The {{wp|System-on-a-chip|SoC}} in each device have an {{wp|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:
* 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 [[Grabbing IMG3 Keys]] for an [[iBoot (Bootloader)|iBoot]] patch.

==Derived keys==

Some derived keys are computed by the IOAESAccelerator kernel service at boot. These keys are generated by encrypting static values either with the UID key (0x7D0 identifier) or the GID key (0x3E8 identifier). The values defined in the iPhone 4 5.0 kernel are :
<pre>
__text:807E3000 keys_to_compute DCD 0x835,0x7D0,0x1010101,0x1010101,0x1010101,0x1010101
__text:807E3018 DCD 0x899,0x7D0,0xB5FCE8D1,0x8DBF3739,0xD14CC7EF,0xB0D4F1D0
__text:807E3030 DCD 0x89B,0x7D0,0x67993E18,0x543CB06B,0xF568A46F,0x49BD0C1C
__text:807E3048 DCD 0x89A,0x7D0,0x335B1FDB,0x1C5F6C60,0x66AA3419,0x61069C58
</pre>

===Key 0x835===

Generated by encrypting 01010101010101010101010101010101 with the [[UID-key]]. Used for data protection.

===Key 0x837===
Generated by encrypting 345A2D6C5050D058780DA431F0710E15 with the [[S5L8900]] [[GID-key]], resulting in 188458A6D15034DFE386F23B61D43774.

It is used as the encryption key for [[S5L File Formats#IMG2|IMG2 files]]. With the introduction of [[IMG3 File Format|IMG3]] in iOS 2.0, [[KBAG]]s are now used instead of the 0x837 key. Because iOS versions 1.x were used only on the [[M68ap|iPhone]] and [[N45ap|iPod touch]] (both use the [[S5L8900]]) the encrypted values for other processors don't matter.

===Key 0x89A===
For A4 devices:
Generated by encrypting DB1F5B33606C5F1C1934AA66589C0661 with the [[UID-key]], getting a device-specific key.

It is used to encrypt the [[SHSH]] blobs on the device.

===Key 0x89B===

Generated by encrypting 183E99676BB03C546FA468F51C0CBD49 with the [[UID-key]]. It is used to encrypt the data partition key.

===Key 0x899===

Generated by encrypting D1E8FCB53937BF8DEFC74CD1D0F1D4B0 with the [[UID-key]]. Usage unknown.

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

Protoypes

2012-02-07T14:08:09Z

Beej: /* iPod touch 3rd Gen Prototype */ Relinkify

Many '''prototype''' devices have leaked from Apple. Some of them are listed below:

== iPhone Prototypes ==
=== MacRumors iPhone 2G ===
[[File:YM649_iPhone_2G.jpg|thumb|iPhone 2G Prototype]]

Jan 03, 2009:

Two iPhone 2G prototypes first reported by user [http://forums.macrumors.com/member.php?u=264715 Brooklyn8] on the [http://forums.macrumors.com/showthread.php?t=627449 MacRumors] forums.

{| class="wikitable" style="font-size:smaller;border-collapse:collapse;"
! style="background-color:#E9E9E9;text-align:center;width:100px;" |
! style="background-color:#E9E9E9;text-align:center;width:150px;" | Prototype
! style="background-color:#E9E9E9;text-align:center;" | Comment
|-
! Serial Number
| YM650xxxxxx, YM649xxxxxx
|
|-
! Modem Firmware
| [[03.06.01_G]]
| The firmware dump comes (in [[:/usr/local/standalone/firmware/]]) with [[03.06.00_G]]
|-
|}
{{clear}}

=== Gizmodo iPhone 4 ===
[[File:Gizmodo_iPhone4_01.jpg|thumb|Gizmodo iPhone 4 prototype in disguise case]]

Apr 19, 2010:

iPhone 4 prototype first reported by [http://gizmodo.com/5520164/this-is-apples-next-iphone Gizmodo]. Brian Hogan, a 21-year-old student at the time, admitted to finding the phone at the Gourmet Haus Staudt in Redwood City, California, after it was left behind by an Apple engineer named Gray Powell, and later selling it to Gizmodo [http://www.wired.com/threatlevel/2011/10/brian-hogan-sentenced/]. The iPhone's diguise case didn't seem to have any special features, just two bar codes stuck on its back: 8800601pex1 and N90_DVT_GE4X_0493. Next to the volume keys there was an additional marker: iPhone SWE-L200221.

{| class="wikitable" style="font-size:smaller;border-collapse:collapse;"
! style="background-color:#E9E9E9;text-align:center;width:100px;" |
! style="background-color:#E9E9E9;text-align:center;width:150px;" | Prototype
! style="background-color:#E9E9E9;text-align:center;" | Comment
|-
! Model (back)
| XXXXX
|
|-
! FCC ID
| BCGAXXXXX
|
|-
! IC ID
| 579C-AXXXXX
|
|-
|}
{{clear}}

=== N92 iPhone 4 CDMA ===
[[File:n92iPhone-CDMA-Verizon2.jpg|thumb|CDMA iPhone 4 prototype]]

Oct 19, 2010

CDMA iPhone 4 prototype first reported by [http://richyrich.net/exclusive-verizon-iphone-4-photos/ RichyRich.net] with further details [http://www.iphonehacks.com/2010/10/leaked-photos-of-verizon-iphone.html here] and [http://thetechjournal.com/electronics/iphone/some-prototype-model-of-upcoming-iphone-from-verizon-has-leaked.xhtml here].

{{clear}}

=== 64GB iPhone 4 ===
[[File:64GB_iPhone4_01.jpg|thumb|64GB iPhone 4 prototype]]

Mar 8, 2011:

An iPhone 4 (GSM) prototype first reported by [http://micgadget.com/11604/exclusive-64gb-iphone-4-hands-on-video/ micgadget.com]. Further details on [http://techmento.com/2011/03/10/iphone-prototype-64gb-memory-leaked/ techmento.com].

{| class="wikitable" style="font-size:smaller;border-collapse:collapse;"
! style="background-color:#E9E9E9;text-align:center;width:100px;" |
! style="background-color:#E9E9E9;text-align:center;width:150px;" | Prototype
! style="background-color:#E9E9E9;text-align:center;" | Comment
|-
! Model No. (back)
| XXXXX
| Same as the one from Gizmodo.
|-
! FCC ID
| BCGAXXXXX
| Same as the one from Gizmodo.
|-
! IC ID
| 579C-AXXXXX
| Same as the one from Gizmodo.
|-
! Capacity
| 59.1
| A 64GB iPhone 4 was never released.
|-
! Version
| [[Baker_8B117_(iPhone_4)|4.1 (8B117)]]
| The released iOS version comes with different Modem Firmware.
|-
! [[Carrier_bundle|Carrier]]
| SMC-Voda 8.0
|
|-
! [[Models|Model]] (in Settings)
| 995-6049LL
| Different to official numbering scheme of [[Models]].
|-
! Serial Number
| 8800902DEX3
|
|-
! Wi-Fi Address
| 00:25:00:FC:F6:9D
| 00-25-00 is a prefix registered to Apple at [http://standards.ieee.org/develop/regauth/oui/oui.txt IEEE].
|-
! Bluetooth
| 00:25:00:FC:F6:9C
|
|-
! IMEI
| 00 107200 281664 1
|
|-
! [[ICCID]]
|
| Empty ICCID is unusual
|-
! Modem Firmware
| [[01.59.00|01.59]]
| Based on the fact that prototype has the Modem Firmware for the XMM 6180 installed this defenitly is an 64GB iPhone 4 (GSM). However the iOS Version this device has installed (4.1) came oficially with Modem Firmware 02.10.04.
|-
|}
{{clear}}

=== White Vietnamese iPhone 4 ===
[[File:Viet_iPhone4_01.jpg|thumb|iPhone 4 prototype with Exposè-like multitasking]]

Apr 19, 2011:

First reported by [http://www.tinhte.vn/tin-tuc-gioi-thieu-118/tren-tay-giao-dien-da-nhiem-moi-tren-iphone-5-a-663854/ tinhte.vn] and further discussed on [http://www.macstories.net/news/vietnamese-videos-show-old-ios-4-build-with-several-unreleased-features/ macstories.net]. This prototype shows an alternative, Exposè-like interface for switching between applications. The Exposè design is very similar to jailbreak tweaks like Multifl0w in the way it displays apps in the background through a preview of their actual windows, rather than simple icons.

{| class="wikitable" style="font-size:smaller;border-collapse:collapse;"
! style="background-color:#E9E9E9;text-align:center;width:100px;" |
! style="background-color:#E9E9E9;text-align:center;width:150px;" | Prototype
! style="background-color:#E9E9E9;text-align:center;" | Comment
|-
! Capacity
| 58.2GB
| The released iPhone 4 has a lower available capacity due to iOS taking up more space.
|-
! Version
| 4.0 (8A216)
| Never officially released.
|-
|}
{{clear}}

=== US T-Mobile iPhone 4S ===
[[File:iPhone4S_N94proto_01.jpg|thumb|iPhone 4S prototype with N94 PROTO3 marking on the back]]

Apr 23, 2011:

This prototype first was reported by [http://www.bgr.com/2011/04/23/exclusive-apple-testing-iphone-4-for-t-mobile-usa/ BGR].

{| class="wikitable" style="font-size:smaller;border-collapse:collapse;"
! style="background-color:#E9E9E9;text-align:center;width:100px;" |
! style="background-color:#E9E9E9;text-align:center;width:150px;" | Prototype
! style="background-color:#E9E9E9;text-align:center;" | Comment
|-
! Internal Model No.
| N94
| Based on the N94 Sticker on the back this is an iPhone 4S, whose internal number is [[N94ap]].
|-
|}
{{clear}}

=== TD-SCDMA iPhone 4 ===

[[File:CM TDSCDMA iphone01.jpg|thumb|China Mobile TD-SCDMA Prototype.]]

Jul 07, 2011:

iPhone 4 prototype first mentioned by [http://news.mydrivers.com/1/198/198552.htm mydrivers.com] (in chinese).

{| class="wikitable" style="font-size:smaller;border-collapse:collapse;"
! style="background-color:#E9E9E9;text-align:center;width:100px;" |
! style="background-color:#E9E9E9;text-align:center;width:150px;" | Prototype
! style="background-color:#E9E9E9;text-align:center;" | Comment
|-
! [[Carrier_bundle|Carrier]]
| 中国移动 13.0
| China Mobile 13.0. Officially there is only 中国移动 11.0 (China Mobile 11.0) available.
|-
! [[Models|Model]] (in Settings)
| MC'''6?0?'''3CM
| Probably MC603 - black 16GB iPhone 4 would match, but CM is not officially designated [[Model Regions|Model Region]] code.
|-
! Serial Number
| 5K0????????
|
|-
! Wi-Fi Address
| 5C:49:48:??:??:?2
| 5C-49-48 is not a registered prefix at [http://standards.ieee.org/develop/regauth/oui/oui.txt IEEE].
|-
! Bluetooth
| 5C:49:48:??:??:?1
|
|-
! IMEI
| 00 000000 000000 0
| IMEI can't usually be 0.
|-
! [[ICCID]]
| 89'''8?6?''' '''0?0?'''10 8110 0136 3637
|
|-
! Modem Firmware
| [[06.10.01]]
| This Firmware was never released. Also it is unclear which baseband chip that prototype is using. The high version number suggest that possibly the [[X-Gold 608]] is used. However the [[X-Gold 608]] is not capable of CDMA.
|-
|}
{{clear}}

=== Early iPhone 4 ===
[[File:IDevice proto01.png|thumb|Prototype device image in iTunes]]

Jul 17, 2011:

Prototype device reported by [http://micgadget.com/13792/iphone-4s-prototype-leaked/ micgadget.com] which notably shows a different image when plugged into iTunes.

{| class="wikitable" style="font-size:smaller;border-collapse:collapse;"
! style="background-color:#E9E9E9;text-align:center;width:100px;" |
! style="background-color:#E9E9E9;text-align:center;width:150px;" | Prototype
! style="background-color:#E9E9E9;text-align:center;" | Comment
|-
! Capacity
| 28.60
|
|-
! Software Version
| 4.0
|
|-
! Serial Number
| 8894805????
|
|-
|}
{{clear}}

=== White iPhone 4 DF3184 ===
[[File:iPhone4_DF3184_01.jpg|thumb|iPhone 4 DF3184]]

Aug 22, 2011:

A white iPhone 4 prototype first reported by [http://www.flickr.com/photos/mars478/sets/72157627368941519/ Mathias Rios]. The iPhone has a DF3184 printing at the lower front right side. Mathias Rios purchased it from ebay where it was listed as broken. Compared to an original iPhone4 (black) this prototype has a smaller back camera and the flash is also slightly further away [http://www.flickr.com/photos/mars478/6069524165/in/set-72157627368941519/lightbox/]. In addition this protoype restore mode screen (Conncect to iTunes Screen) shows an old (iTunes9 - blue Note on CD) and pixalated iTunes icon [http://www.flickr.com/photos/mars478/6069517083/in/set-72157627368941519/lightbox/]. This prototype come with a sticker on the A4 denoting it as Design Verification Test Prototype (N90_DVT_I_0010). Appearently the A4 is marked differently than the actual A4 chip in shipping iPhone, and has the same marking as earlier iPod Touches and iPhones (the "K4X2G643GE" marking).

{| class="wikitable" style="font-size:smaller;border-collapse:collapse;"
! style="background-color:#E9E9E9;text-align:center;width:100px;" |
! style="background-color:#E9E9E9;text-align:center;width:150px;" | Prototype
! style="background-color:#E9E9E9;text-align:center;" | Comment
|-
! Model (back)
| XXXXX
| Same as the one from Gizmodo.
|-
! FCC ID
| BCGAXXXXX
| Same as the one from Gizmodo.
|-
! IC ID
| 579C-AXXXXX
| Same as the one from Gizmodo.
|-
|}
{{clear}}

=== San Francisco bar iPhone ===
Aug 31, 2011:

Probably an iPhone 4S prototype lost in a San Francisco bar first reported by [http://news.cnet.com/8301-13579_3-20099899-37/apple-loses-another-unreleased-iphone-exclusive/ CNET].
{{clear}}

=== Brazilian 8GB iPhone 4 ===
[[File:Brazil_8GB_iPhone4_01.jpg|thumb|Brazil 8GB iPhone 4]]

Nov 24, 2011:

An 8GB iPhone 4 prototype produced in Brazil. First reported by [http://macmagazine.com.br/2011/11/24/leitor-afirma-ter-posto-as-maos-num-iphone-4-de-8gb-brasileiro-e-manda-fotos-para-comprovar/ macmagazine.com.br]. This iPhone 4 also carries a Made in Bazil (Indústria Brasileira) and an [http://www.anatel.gov.br/Portal/exibirPortalInternet.do Anatel] marking (the Brazilian Telecom regulation body) with number 1465-10-1993 at its back.

{| class="wikitable" style="font-size:smaller;border-collapse:collapse;"
! style="background-color:#E9E9E9;text-align:center;width:100px;" |
! style="background-color:#E9E9E9;text-align:center;width:150px;" | Prototype
! style="background-color:#E9E9E9;text-align:center;" | Comment
|-
! Model (back)
| A1332
|
|-
! EMC (back)
| 380A
| EMC marking hasn't been seen before
|-
! FCC ID
| BCG-E2380A
|
|-
! Capacity
| 6.4GB
|
|-
! Version
| [[Telluride_9A334_(iPhone_4)|5.0 (9A334)]]
|
|-
! Carrier
| Claro Brazil 11.0
|
|-
! [[Models|Model]] (in Settings)
| MD198BR
|
|-
|}
{{clear}}

== iPod touch Prototypes ==

=== Early iPod touch 3rd Gen Prototype ===
[[File:IPod_Cam_01.jpg|thumb|iPod touch with Camera prototype]]

Apr 24, 2010

This iPod touch 3rd generarion prototypes where the first leaked ones to contains a camera (at that time iPod Touches did not). The prototypes where shortly available on eBay, but the listing (250617991364) was removed from eBay later. The devices contained DVT-1 and DVT-2 markings and also Apple Development Team barcode sticker with PT431668 numbering. At least one of the devices was running [[SwitchBoard.app]] and [[Inferno 7C1095a]]. Further information [http://www.gadgetsdna.com/ipod-touch-prototypes-with-camera-sticking-on-ebay/2515/ here].
{{clear}}

=== tinhte.vn iPod touch 3rd Gen Prototype ===
[[File:N18_DVTa_01.jpg|thumb|iPod touch with Camera prototype]]

May 19, 2010

iPod Touch Prototypes reported by [http://www.tinhte.vn/f118/tren-tay-ipod-touch-co-camera-410528/ tinhte.vn].

{| class="wikitable" style="font-size:smaller;border-collapse:collapse;"
! style="background-color:#E9E9E9;text-align:center;width:100px;" |
! style="background-color:#E9E9E9;text-align:center;width:150px;" | Prototype
! style="background-color:#E9E9E9;text-align:center;" | Comment
|-
! Model No. (back)
| A1318?
|
|-
! FCC ID
| ?
|
|-
! EMC
| XXXX
|
|-
! Capacity
| 64GB
|
|-
! Version
| 3.1
|
|-
! Serial Number
| ?
|
|-
|}

{{clear}}

=== iPod touch 3rd Gen Prototype ===
[[File:IPod3G N18-PreEVTb.jpg|thumb|iPod touch 3G prototype]]

Jan 24, 2012:

The iPod touch 3rd generation prototype was first reported by [[iOS]] hacker [[user:Sonny788|Sonny Dickson]], The iPod is running [[SwitchBoard.app]] and [[Inferno 7C1023e]]. It has a N18-PreEVTb marking at the back.

{| class="wikitable" style="font-size:smaller;border-collapse:collapse;"
! style="background-color:#E9E9E9;text-align:center;width:100px;" |
! style="background-color:#E9E9E9;text-align:center;width:150px;" | Prototype
! style="background-color:#E9E9E9;text-align:center;" | Comment
|-
! Model No.
| MC008
|
|-
! FCC ID
| BCGA1XX
|
|-
! Capacity
| 32GB
|
|-
! Version
| 3.1
|
|-
! Serial Number
| 8K91300XXXX
|
|-
! Wi-Fi Address
| 00:24:36:f2:87:b9
| 00-24-36 is a prefix registered to Apple at [http://standards.ieee.org/develop/regauth/oui/oui.txt IEEE].
|-
! Bluetooth
| 00:00:00:00:00:00
|
|-
! iBoot
| iBoot-583.4
|
|-
|}
{{clear}}

06.15.00

2012-02-05T03:18:43Z

Beej: basebands have, not basebands has

This is the [[X-Gold 608]] baseband firmware for the [[K48ap|Wi-Fi+3G iPad]] that Apple bundles with iOS 3.2-3.2.2.

==[[iPhone]] (3G and 3GS)==
Since all recent iPhone 3GS basebands (ie: [[05.14.02]], [[05.15.04]], [[05.16.01]], [[05.16.02]] and [[05.16.05]]) no longer have the [[AT+XAPP Vulnerability]], the [[iPhone Dev Team]] has released an update to its jailbreak tools ([[redsn0w]] 0.9.6b5 and [[PwnageTool]] 4.1.3) that allows one to install this iPad version which still is vulnerable. This works because part of Apple's security system is to only allow the installation of signed baseband firmware with a higher version number. Since this firmware has a higher version number, it can be installed even though it is older. The benefit is that it allows for unlocking the phone. The downside is that it breaks GPS functionality and there is no publically available way to go back to firmware with working GPS. The latest tool that is capable of installing iPad baseband is Redsn0w 0.9.9b8, on 4.1,4.2.1,4.3-4.3.5 and 5.0 betas and GM. This baseband works fine up to [[Durango 8L1 (iPhone 3GS)|iOS 4.3.5]] (except for GPS functionality) and on iOS 5.x it requires a fix, which is implemented in redsn0w 0.9.9b6+. This baseband can be downgraded from on iPhone 3G with 5.8 boot loader or by a baseband chip replacement. The only case of users upgrading from 05.xx.xx to 06.15.00 is for unlocking and the baseband is higher than [[05.13.04]]. The baseband [[04.26.08]] has much more issues than 06.15.00 on iOS 3.1+ but ultrasn0w can fix them up to iOS 5.0.1.

Absinthe

2012-01-30T17:01:24Z

Beej: Absinthe name origin

Absinthe is the [[S5L8940]] userland jailbreak tool for [[N94ap|iPhone 4S]] and [[iPad 2]] on iOS 5.0 (iPhone 4S only), 5.0.1 (9A405) and [[Telluride 9A406 (iPhone 4S)|iOS 5.0.1 build 9A406]] on iPhone 4S. This tool was released on January 20, 2012, and is available in three incarnations:
*A GUI tool with the same name, released by the [[Chronic Dev (team)|Chronic Dev Team]]
*A command-line version by the [[iPhone Dev Team]], in case troubleshooting is required
*A future integration with [[redsn0w]]

The name Absinthe was chosen as an homage to Greenp0ison, Chronic Dev Team's earlier jailbreak software. Absinthe is an alcoholic beverage that is often greenish in color and is poisonous in quantity. There is also a daemon named [[/usr/sbin/absinthed|absinthed.XXX]].

==Installation==
The jailbreak packs [[Corona]] for the [[S5L8940]] and the rest of the firmware patches in a regular [[iTunes]] backup and then restores this backup on to the device, which injects the required files. It is then completed by opening a web clip added to the [[SpringBoard|home screen]] by Absinthe. If this doesn't work, for example, because the [[greenpois0n]] website is down due to the number of people attempting to jailbreak, an alternative is to enable a specially crafted VPN connection in the [[/Applications/Preferences.app|Settings]] app.

==Exploit==
{{main|Corona}}

This jailbreak uses the [[Racoon String Format Overflow Exploit]] and [[HFS Heap Overflow]] from [[Corona]] for untether.
The exact exploit to jailbreak the two devices is not known yet, but it is assumed that the web clip loads a page that requires an IPsec VPN connection, which causes the [http://ipsec-tools.sourceforge.net racoon] daemon to start and run the jailbreak payload.

However, some poking reveals some unique means of injection. At some point in the jailbreak process, BackupAgent is intentionally crashed to produce a crash log. The jailbreak payload reads this crash log in order to obtain the memory address of libcopyfile.dylib to continue with the exploit.

Opening the <tt>webclip_Info.plist</tt> file included with the GUI tool, which is the definition file for the web clip, [http://cache.greenpois0n.com/abs0/index.html a URL to the greenpois0n website] is found, which shows a please wait message. The interesting part is the source code of this page has an image linked to http://127.0.0.1/trigger.png, meaning a web server is running on the device and requires the trigger image to be loaded to finish the process.

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

Talk:Bootchain

2012-01-28T22:33:34Z

Beej:

I don't think mentioning unlocking as an example is good. The baseband is a separate system with its own bootchain, right? --[[User:Beej|beej]] 16:20, 27 January 2012 (MST)
:Both bootchains are listed. Why would you break the baseband if not for unlocking? Do you know a better example? Or just leave that part away? --[[User:Http|http]] 00:47, 28 January 2012 (MST)
::Oops. Somehow I missed that the article was about both bootchains. I think maybe an example for why you'd want to break each might be an improvement? --[[User:Beej|beej]] 15:33, 28 January 2012 (MST)

Talk:Bootchain

2012-01-27T23:20:13Z

Beej: Created page with "I don't think mentioning unlocking as an example is good. The baseband is a separate system with its own bootchain, right? --~~~~"

I don't think mentioning unlocking as an example is good. The baseband is a separate system with its own bootchain, right? --[[User:Beej|beej]] 16:20, 27 January 2012 (MST)

SwitchBoard.app

2012-01-25T15:25:35Z

Beej: s/with/from a/

[[Image:SwitchBoard_4G.jpg|frame|right|SwitchBoard on [[iPhone]].]]

SwitchBoard.app is one of Apple's internal utilities. It's a simple launcher of other developer utilities. It's usually located in /AppleInternal/Applications folder along the other internal applications. Currently, there is no SwitchBoard binary available for public.

[[Image:Switchboard.jpg|frame|left|SwitchBoard from [[Sierra 7C108b]] on an [[N88ap|iPhone 3GS]].]]

SwitchBoard and diagnostic utilities are copied onto the device during restore from a special [[IPSW File Format|IPSW]] which is seeded only to Apple official service centers.

[[Category:Apple Internal Apps]]
[[Category:Software]]

[[Image:SwitchBoard_iPod.png|frame|right|SwitchBoard on [[iPod Touch]].]]

Talk:DFU Mode

2012-01-23T16:49:31Z

Beej:

== Definition ==
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''' {{unsigned|ChronicDev|20:48, July 31, 2008 (MST)}}

I would love to see some official Apple documentation backing that up... --Z00L
:Apple didn't invent DFU. [http://www.usb.org/developers/devclass_docs/DFU_1.1.pdf The USB Implementers Forum did.] --[[User:Dialexio|Dialexio]] 08:19, 11 December 2011 (MST)

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

== Recovery to DFU ==
I've been trying to get my program to make the iDevice go from Recovery to DFU. Any way I could do such a thing? Through uploading files? --[[User:Dylan Laws|Dylan Laws]] 20:11, 22 January 2012 (MST)
:: Could you please stop asking such questions?! If you can do it, do it, if you can't, leave it. And as far as I know you can't enter the real DFU Mode using a Computer, you always need to press buttons on the device. --[[User:Rud0lf77|rud0lf77]] 23:19, 22 January 2012 (MST)
::::Rud0lf77: Nobody's forcing you to read his posts. If you don't like his questions, stop reading them :P --[[User:Beej|beej]] 09:49, 23 January 2012 (MST)
:::How'd GeoHot make a one click jailbreak? --[[User:Dylan Laws|Dylan Laws]] 00:19, 23 January 2012 (MST)
:::: [[purplera1n]] and [[blackra1n]] used iBot exploits! No DFU was needed! Please read about these tools and exploits before posting such questions! --[[User:Rud0lf77|rud0lf77]] 04:05, 23 January 2012 (MST)
:::::I Knew that they did, but if you noticed the one click and then it puts the device into recovery and then, I think? DFU. I know that they used the limera1n exploit.--[[User:Dylan Laws|Dylan Laws]] 08:47, 23 January 2012 (MST)
::::::Not quite one-click, but as close as you'll likely get: http://is.gd/Iu2FZx --[[User:Beej|beej]] 09:49, 23 January 2012 (MST)

Talk:Racoon String Format Overflow Exploit

2012-01-21T16:33:14Z

Beej:

Format "Overflow" Exploit? It's not an overflow, it's a Format String Vulnerability. I think you should change this page's name. --[[User:Qwertyoruiop|Qwertyoruiop]] 07:28, 21 January 2012 (MST)
:Agreed. Nice catch :) --[[User:Beej|beej]] 09:33, 21 January 2012 (MST)

Talk:Corona

2012-01-17T01:15:10Z

Beej:

Who says the latest sandbox fixes are from Saffron? --[[User:Beej|beej]] 10:39, 16 January 2012 (MST)
:Sorry, forgot to reference the source, [https://twitter.com/MuscleNerd/status/158771869749751808 MuscleNerd tweeted about it]. [[User:thekirbylover|the]][[User talk:thekirbylover|kirby]][[Special:Contributions/thekirbylover|lover]] 10:49, 16 January 2012 (MST)
::What does that tweet have to do with Saffron? --[[User:Beej|beej]] 11:16, 16 January 2012 (MST)
:::Not much, but on [[User:Pod2g|pod2g's]] you can read that the sandbox patches of [[User:Comex|comex]] were integrated into Corona, so maybe we should change "sandbox patches from Saffron" to "sandbox patches from comex" --[[User:Rud0lf77|rud0lf77]] 11:21, 16 January 2012 (MST)
:::I do recall someone saying it was from saffron, just cant remember who. Plus the patches probably would have been in it anyway, considering it's his last jailbreak. [[User:thekirbylover|the]][[User talk:thekirbylover|kirby]][[Special:Contributions/thekirbylover|lover]] 11:22, 16 January 2012 (MST)
::::I think you're incorrect and should remove the assertion if you can't cite a reliable source for it. --[[User:Beej|beej]] 12:03, 16 January 2012 (MST)
:::Well, [[User:Comex|comex]] created a new set of patches, that everybody now relies on (see [[:Category:Kernel_Patches]]). It was me who has written that there, source was probably from [[i0n1c]]'s slides or so. But I also don't see the direct relation to [[Saffron]]. -- [[User:Http|http]] 15:05, 16 January 2012 (MST)
::::Oh, I see. I changed saffron to comex in the article. [[User:thekirbylover|the]][[User talk:thekirbylover|kirby]][[Special:Contributions/thekirbylover|lover]] 17:08, 16 January 2012 (MST)
:::::I still don't see what those old kernel patches have to do with this latest sandbox-related bug fix. What's wrong with the wording from the Devteam's blog update? --[[User:Beej|beej]] 18:15, 16 January 2012 (MST)

Talk:Corona

2012-01-16T19:03:38Z

Beej:

Talk:Corona

2012-01-16T18:16:05Z

Beej:

Talk:Corona

2012-01-16T17:39:57Z

Beej: Created page with "Who says the latest sandbox fixes are from Saffron? --~~~~"

Who says the latest sandbox fixes are from Saffron? --[[User:Beej|beej]] 10:39, 16 January 2012 (MST)

Pwnage 2.0

2012-01-14T15:52:46Z

Beej: /* Source code */

This exploit in the [[VROM (S5L8900)|S5L8900 bootrom]] is really the ultimate exploit, since it allows unsigned code to be run at the lowest level. It is available in all devices that use the [[S5L8900]] - the [[M68ap|iPhone]], [[N45ap|iPod Touch]] and [[N82ap|iPhone 3G]]. It is also available on some non-iOS iPods.
==Source code==
//----- Type defines ----------------------------------------------------------
typedef unsigned char byte; // Byte is a char
typedef unsigned short int word16; // 16-bit word is a short int
typedef unsigned int word32; // 32-bit word is an int
//----- Defines ---------------------------------------------------------------
#define POLYNOMIAL 0x04c11db7L // Standard CRC-32 ppolynomial
//----- Global variables ------------------------------------------------------
unsigned long crctable[256] =
{
0x00000000L, 0x77073096L, 0xEE0E612CL, 0x990951BAL,
0x076DC419L, 0x706AF48FL, 0xE963A535L, 0x9E6495A3L,
0x0EDB8832L, 0x79DCB8A4L, 0xE0D5E91EL, 0x97D2D988L,
0x09B64C2BL, 0x7EB17CBDL, 0xE7B82D07L, 0x90BF1D91L,
0x1DB71064L, 0x6AB020F2L, 0xF3B97148L, 0x84BE41DEL,
0x1ADAD47DL, 0x6DDDE4EBL, 0xF4D4B551L, 0x83D385C7L,
0x136C9856L, 0x646BA8C0L, 0xFD62F97AL, 0x8A65C9ECL,
0x14015C4FL, 0x63066CD9L, 0xFA0F3D63L, 0x8D080DF5L,
0x3B6E20C8L, 0x4C69105EL, 0xD56041E4L, 0xA2677172L,
0x3C03E4D1L, 0x4B04D447L, 0xD20D85FDL, 0xA50AB56BL,
0x35B5A8FAL, 0x42B2986CL, 0xDBBBC9D6L, 0xACBCF940L,
0x32D86CE3L, 0x45DF5C75L, 0xDCD60DCFL, 0xABD13D59L,
0x26D930ACL, 0x51DE003AL, 0xC8D75180L, 0xBFD06116L,
0x21B4F4B5L, 0x56B3C423L, 0xCFBA9599L, 0xB8BDA50FL,
0x2802B89EL, 0x5F058808L, 0xC60CD9B2L, 0xB10BE924L,
0x2F6F7C87L, 0x58684C11L, 0xC1611DABL, 0xB6662D3DL,
0x76DC4190L, 0x01DB7106L, 0x98D220BCL, 0xEFD5102AL,
0x71B18589L, 0x06B6B51FL, 0x9FBFE4A5L, 0xE8B8D433L,
0x7807C9A2L, 0x0F00F934L, 0x9609A88EL, 0xE10E9818L,
0x7F6A0DBBL, 0x086D3D2DL, 0x91646C97L, 0xE6635C01L,
0x6B6B51F4L, 0x1C6C6162L, 0x856530D8L, 0xF262004EL,
0x6C0695EDL, 0x1B01A57BL, 0x8208F4C1L, 0xF50FC457L,
0x65B0D9C6L, 0x12B7E950L, 0x8BBEB8EAL, 0xFCB9887CL,
0x62DD1DDFL, 0x15DA2D49L, 0x8CD37CF3L, 0xFBD44C65L,
0x4DB26158L, 0x3AB551CEL, 0xA3BC0074L, 0xD4BB30E2L,
0x4ADFA541L, 0x3DD895D7L, 0xA4D1C46DL, 0xD3D6F4FBL,
0x4369E96AL, 0x346ED9FCL, 0xAD678846L, 0xDA60B8D0L,
0x44042D73L, 0x33031DE5L, 0xAA0A4C5FL, 0xDD0D7CC9L,
0x5005713CL, 0x270241AAL, 0xBE0B1010L, 0xC90C2086L,
0x5768B525L, 0x206F85B3L, 0xB966D409L, 0xCE61E49FL,
0x5EDEF90EL, 0x29D9C998L, 0xB0D09822L, 0xC7D7A8B4L,
0x59B33D17L, 0x2EB40D81L, 0xB7BD5C3BL, 0xC0BA6CADL,
0xEDB88320L, 0x9ABFB3B6L, 0x03B6E20CL, 0x74B1D29AL,
0xEAD54739L, 0x9DD277AFL, 0x04DB2615L, 0x73DC1683L,
0xE3630B12L, 0x94643B84L, 0x0D6D6A3EL, 0x7A6A5AA8L,
0xE40ECF0BL, 0x9309FF9DL, 0x0A00AE27L, 0x7D079EB1L,
0xF00F9344L, 0x8708A3D2L, 0x1E01F268L, 0x6906C2FEL,
0xF762575DL, 0x806567CBL, 0x196C3671L, 0x6E6B06E7L,
0xFED41B76L, 0x89D32BE0L, 0x10DA7A5AL, 0x67DD4ACCL,
0xF9B9DF6FL, 0x8EBEEFF9L, 0x17B7BE43L, 0x60B08ED5L,
0xD6D6A3E8L, 0xA1D1937EL, 0x38D8C2C4L, 0x4FDFF252L,
0xD1BB67F1L, 0xA6BC5767L, 0x3FB506DDL, 0x48B2364BL,
0xD80D2BDAL, 0xAF0A1B4CL, 0x36034AF6L, 0x41047A60L,
0xDF60EFC3L, 0xA867DF55L, 0x316E8EEFL, 0x4669BE79L,
0xCB61B38CL, 0xBC66831AL, 0x256FD2A0L, 0x5268E236L,
0xCC0C7795L, 0xBB0B4703L, 0x220216B9L, 0x5505262FL,
0xC5BA3BBEL, 0xB2BD0B28L, 0x2BB45A92L, 0x5CB36A04L,
0xC2D7FFA7L, 0xB5D0CF31L, 0x2CD99E8BL, 0x5BDEAE1DL,
0x9B64C2B0L, 0xEC63F226L, 0x756AA39CL, 0x026D930AL,
0x9C0906A9L, 0xEB0E363FL, 0x72076785L, 0x05005713L,
0x95BF4A82L, 0xE2B87A14L, 0x7BB12BAEL, 0x0CB61B38L,
0x92D28E9BL, 0xE5D5BE0DL, 0x7CDCEFB7L, 0x0BDBDF21L,
0x86D3D2D4L, 0xF1D4E242L, 0x68DDB3F8L, 0x1FDA836EL,
0x81BE16CDL, 0xF6B9265BL, 0x6FB077E1L, 0x18B74777L,
0x88085AE6L, 0xFF0F6A70L, 0x66063BCAL, 0x11010B5CL,
0x8F659EFFL, 0xF862AE69L, 0x616BFFD3L, 0x166CCF45L,
0xA00AE278L, 0xD70DD2EEL, 0x4E048354L, 0x3903B3C2L,
0xA7672661L, 0xD06016F7L, 0x4969474DL, 0x3E6E77DBL,
0xAED16A4AL, 0xD9D65ADCL, 0x40DF0B66L, 0x37D83BF0L,
0xA9BCAE53L, 0xDEBB9EC5L, 0x47B2CF7FL, 0x30B5FFE9L,
0xBDBDF21CL, 0xCABAC28AL, 0x53B39330L, 0x24B4A3A6L,
0xBAD03605L, 0xCDD70693L, 0x54DE5729L, 0x23D967BFL,
0xB3667A2EL, 0xC4614AB8L, 0x5D681B02L, 0x2A6F2B94L,
0xB40BBE37L, 0xC30C8EA1L, 0x5A05DF1BL, 0x2D02EF8DL
};
//----- Prototypes ------------------------------------------------------------
word32 update_crc(word32 crc_accum, byte *data_blk_ptr, word32 data_blk_size);
//=============================================================================
//= CRC32 generation =
//=============================================================================
word32 update_crc(word32 crc, byte *data_blk_ptr, word32 data_blk_size)
{
register word32 i, j;
for (j = 0; j < data_blk_size; j++)
crc = crctable[(crc ^ data_blk_ptr[j]) & 0xFFL] ^ (crc >> 8);
}
return crc;
}

==Credit==
[[iPhone Dev Team]]

==Exploit==
There is a stack overflow in the certificate parsing code. By passing a malformed certificate, unsigned code can be run.

==Implementations==
*[[PwnageTool]]
*[[QuickPwn]]
*[[WinPwn]]
*[[redsn0w]]
*[[iran]]

[[Category:Bootrom Exploits]]

The iPhone Wiki:Community portal

2012-01-03T04:54:25Z

Beej: Corona

{{Talk Archive|2010|2011|2012}}
This is the place to post tasks that need to be done on the wiki. Also this is the place for proposed changes. I heard about people wanting a favicon and arranging the main page into categories.

== Site Related Requests ==
=== Corona Info ===
We need to get Corona info integrated into the wiki. There's good info here: http://pod2g-ios.blogspot.com/2012/01/details-on-corona.html [[User:Beej|beej]] 21:54, 2 January 2012 (MST)beej

=== 2.2b1 ===
Is 2.2b1 5G26 or 5G27, because on [[Beta Firmware]], it says 5G27... --[[User:Balloonhead66|Balloonhead66]] 19:48, 6 August 2011 (MDT)

=== Key pages ===
I would like to propose a new rule: Do not create a key page (e.g.- [[Jasper 8C148 (iPad)]]) unless you can also provide at least one key. Key pages are meant to share decryption keys with others. Copying and pasting from a template page provides us with no information whatsoever, and also wastes time (both the poster's and the administrators'). Thoughts on this? --[[User:Dialexio|Dialexio]] 21:50, 4 November 2011 (MDT)
:I'm against that. While I agree we shouldn't create all empty pages to fill out later, I don't see any reason to have a rule for that. Or was that a problem recently and I missed it? I also created pages with very few content (like [[Siri]]), that other users picked up or hopefully will pick up and enhanced. Key pages are a little different though. And the page you reference was never empty (but had wrong keys initially). So if you feel a big need to have such a rule, go on. -- [[User:Http|http]] 05:06, 5 November 2011 (MDT)
::I was simply using that page as an example of a key page, for those that had no clue what I was talking about. I think that posting an article with little content is a bit different from an empty key page; at least a small amount of information is being provided. In addition, it's easier to tell whether a key page needs to be filled out or not if the key page's link is red because the page was never created. I'll wait for additional feedback from anybody else before I decide on whether or not to add this to the rules. --[[User:Dialexio|Dialexio]] 11:31, 5 November 2011 (MDT)
:::Ok --[[User:Balloonhead66|Balloonhead66]] 16:58, 12 December 2011 (MST)

=== New Upper Left Image ===
If someone has a good one, I'll change it. Who still has an iPhone 2G? --[[User:Geohot|geohot]] 13:11, 12 December 2011 (MST)
:[[:File:NewLogo.png]]? Problem is one like that doesnt scale well. Maybe a rotated (like this) image of an [[n94ap|iPhone 4S]] or an [[iPad 2]]. I have an image of a rotated iPhone 4S if you want... --[[User:Balloonhead66|Balloonhead66]] 14:04, 12 December 2011 (MST)
:Something with an iPhone and the [[:File:Iptwiki.png|iPhone wiki logo]] from the main page would look good. I'll see if I can make one up. [[User:thekirbylover|the]][[User talk:thekirbylover|kirby]][[Special:Contributions/thekirbylover|lover]] 23:06, 17 December 2011 (MST)
:why not the [http://en.wikipedia.org/wiki/File:Apple_iOS.svg iOS logo]? --[[User:M2m|M2m]] 10:02, 18 December 2011 (MST)
::I don't think we can use that because it's a copyrighted logo. [[User:thekirbylover|the]][[User talk:thekirbylover|kirby]][[Special:Contributions/thekirbylover|lover]] 18:06, 18 December 2011 (MST)
::Agreed --[[User:Balloonhead66|Balloonhead66]] 18:15, 18 December 2011 (MST)
:Mine requires a bit of [[User:thekirbylover/skin.css|extra CSS]] for it too look good. This can be added to [[Mediawiki:skin.css]]. [[User:thekirbylover|the]][[User talk:thekirbylover|kirby]][[Special:Contributions/thekirbylover|lover]] 17:59, 19 December 2011 (MST)
:i have an iPhone 2G geohot! --[[User:Zmaster|Zmaster]] 12:08, 24 December 2011 (MST)
:Ok, I got something from @iSurenix. He says: "In case you don't like it, I can always fix it up etc. but I think it looks new, fresh and updated." -- [[User:Http|http]] 13:40, 25 December 2011 (MST)
::Excellent! --[[User:balloonhead66|Cole Johnson]] 14:54, 25 December 2011 (MST)
::I think it blends into the background too much because the iPhone is white. Thats just my opinion thought. Otherwise I like it. --[[User:JacobVengeance|Jacob]] 16:18, 25 December 2011 (MST)
:::Maybe a black one? --[[User:balloonhead66|Cole Johnson]] 17:14, 25 December 2011 (MST)
:::I got a resized version from him and uploaded it. Some Mediawiki documentation said ideal size is 135x135 (max 150x150). And about the white he commented: "I like how I've used the white iPhone. It's lie I've said "new and fresh". Not a lot places use white iPhones. Let alone in that specific position. I like it." (@iSurenix). -- [[User:Http|http]] 17:09, 26 December 2011 (MST)
::::We could put a background behind the page if it's staying white... maybe the iOS textured background? [[User:thekirbylover|the]][[User talk:thekirbylover|kirby]][[Special:Contributions/thekirbylover|lover]] 19:15, 26 December 2011 (MST)
::::[[User:thekirbylover/skin.css|Here's the css]] for the textured background I was talking about. To try it, copy and paste this to your address bar: <tt>javascript:void(importStylesheet("User:thekirbylover/skin.css"))</tt> [[User:thekirbylover|the]][[User talk:thekirbylover|kirby]][[Special:Contributions/thekirbylover|lover]] 18:31, 31 December 2011 (MST)
:I like both of these! The white one seems a bit more "professional" so that's nice, but the text is a little pale. They're both better than the existing logo though, so I'd be happy with either. [[User:Britta|Britta]] 18:17, 31 December 2011 (MST)
==== Proposed logos ====
These are thumbnails, click on them to view in normal size.
<gallery>
File:thekirbylover's iPhone Wiki logo.png|[[User:thekirbylover|thekirbylover]]
File:Theiphonewiki.png|{{twitter|iSurenix}}
</gallery>

=== Cydia links ===
Links to Cydia, such as cydia://package/com.example.test, don't seem to wanna be linkified by the wiki, but there's an internal setting you can change: <tt>$wgUrlProtocols[] = "cydia://";</tt>. You might also want to use [[MediaWiki:Vector.css]] to add a mini Cydia icon next to it. [[User:thekirbylover|the]][[User talk:thekirbylover|kirby]][[Special:Contributions/thekirbylover|lover]] 18:06, 18 December 2011 (MST)
:As for the ''localsettings.php'' change, this is [[user:geohot|geohot]]'s problem. As for the CSS change, we could use [http://theiphonewiki.com/wiki/images/thumb/9/91/Cydia.png/16px-Cydia.png Cydia.png@16px]. --[[User:Balloonhead66|Balloonhead66]] 18:15, 18 December 2011 (MST)
::Yep, I was gonna put that CSS in my [[User:thekirbylover/monobook.css]] after I posted that. Also, correct me if I'm wrong, but I think Monobook.css is used on Vector pages too. [[User:thekirbylover|the]][[User talk:thekirbylover|kirby]][[Special:Contributions/thekirbylover|lover]] 18:21, 18 December 2011 (MST)
:::I checked the source and the "/load.php?{CRAP}" are empty and for some reason, {{wp|Google Chrome}}'s "Inspect Element" show up styles... --[[User:Balloonhead66|Balloonhead66]] 18:29, 18 December 2011 (MST)
:::/skin.css is cross skin while /vector.css and /monobook.css are per-skin --[[User:Balloonhead66|Balloonhead66]] 18:31, 18 December 2011 (MST)

=== MD Bootrom ===
Editing the [[models]] page, I noticed that the new white [[iPod4,2|iPod touch 4]]s have MD bootroms. However, I'm not sure about the black models, so can someone with a black touch 4 bought after September please tell me which model is reported in Settings? Thanks. [[User:thekirbylover|the]][[User talk:thekirbylover|kirby]][[Special:Contributions/thekirbylover|lover]] 23:46, 22 December 2011 (MST)
:Those are not bootroms; those are model numbers. According to Apple's online store, the black iPod touch 4G still has the same "MC" model numbers as before. --[[User:Dialexio|Dialexio]] 10:27, 23 December 2011 (MST)
::Ah, I see. Thanks for checking. [[User:thekirbylover|the]][[User talk:thekirbylover|kirby]][[Special:Contributions/thekirbylover|lover]] 16:33, 23 December 2011 (MST)

S5L8930

2012-01-01T01:36:23Z

Beej: s/Apple/Apple's/

[[Image:A4.jpg|right]]
A {{wp|System on a chip|SoC}} ("System on a Chip") developed by Apple's in-house chip design department. It is currently used in [[k48ap|iPad]], both models of the iPhone 4 ([[n90ap|GSM]] and [[n92ap|CDMA]]), [[K66ap|Apple TV 2G]] and the [[N81ap|iPod touch 4G]]. Publicly, Apple refers to this chip as the '''A4'''.

== Exploits ==

=== [[S5L8930 (Bootrom)|Bootrom]] ===
* [[limera1n]]
* [[SHAtter]]

=== [[iBoot]] ===
* [http://www.youtube.com/watch?v=0NValNoW5Rc Unreleased Untethered iBoot Exploit]

=== [[Kernel]] ===
* [[BPF STX Kernel Write Exploit]] - Works up to [[iOS]] 3.2
* [[IOSurface Kernel Exploit]] - Works up to [[iOS]] 4.0.1 (excluding iOS 3.2.2)
* [[Packet Filter Kernel Exploit]] - Works up to [[iOS]] 4.1
* [[HFS Legacy Volume Name Stack Buffer Overflow]] - Works up to [[iOS]] 4.2.8
* [[ndrv_setspec() Integer Overflow]] - Works up to [[iOS]] 4.3.3

=== [[Userland]] ===
* [[MobileBackup Copy Exploit]] - Works up to [[iOS]] 3.2
* [[Malformed CFF Vulnerability]] - Works up to [[iOS]] 4.0.1 (excluding iOS 3.2.2)
*[[T1 Font Integer Overflow]]- Works up to [[iOS]] 4.3.3 (excluding 4.2.9 and 4.2.10)

== Boot Chain ==
[[S5L8930 (Bootrom)|Bootrom]]->[[LLB]]->[[iBoot]]->[[Kernel]]->[[Firmware|System Software]]

== Specifications ==
* '''CPU''': ARM Cortex-A8
* '''GPU''': PowerVR SGX 535
* '''A/V Playback''': PowerVR VXD
* '''RAM''': 256 MB ([[K66ap|Apple TV 2G]], [[K48ap|iPad]], and [[N81ap|iPod touch 4G]]) or 512 MB ([[iPhone 4]])

Aside from the [[iPhone 4]]'s additional RAM and an overall higher clock speed, these are the same specifications as the [[S5L8920]] and [[S5L8922]].

== See also ==
* [[S5L8930 (Bootrom)]]

== Links ==
* http://www.apple.com/ipad/specs/
* http://www.brightsideofnews.com/news/2010/1/27/apple-a4-soc-unveiled---its-an-arm-cpu-and-the-gpu!.aspx

Talk:04.26.08

2011-12-26T03:20:04Z

Beej:

Is it safe to use this baseband with iOS 5 on a 3Gs? I do not want to risk losing GPS. Thanks for any help. --[[User:Sammypwns|sammypwns]] 18:25, 25 December 2011 (MST)
:It says ultrasn0w only fixes the issues up to 4.0.2... --[[User:balloonhead66|Cole Johnson]] 19:05, 25 December 2011 (MST)
:It should be. It's supported. As long as you have SHSH's, you can always downgrade if you don't like it. Just be sure to preserve your baseband when you upgrade --[[User:Beej|beej]] 20:20, 25 December 2011 (MST)

Talk:Models

2011-12-23T16:24:37Z

Beej: My A1387

== Removed models ==
Dialexio, you removed some models. I created the list based on infos in this wiki. I didn't know though if every storage size exists with every color and every combination with both bootroms. Based on what info did you remove the non-existent rows? It seems you removed too many of them. I just saw that my old 3GS, black, new bootrom, 32GB, is a MC133 and is no more listed. Can you please re-check those you removed? Thanks. -- [[User:Http|http]] 07:43, 17 April 2011 (UTC)
:Whoops. For some reason, I was thinking that only 8 GB units had the new bootrom at that time. :s --[[User:Dialexio|Dialexio]] 15:37, 17 April 2011 (UTC)

== Another model number ==
I think on this page we should also add the other model numbers (like the A1332 for the iPhone 4 black) somehow. How are they related? -- [[User:Http|http]] 15:24, 13 October 2011 (MDT)

== iPhone 4S ==
According to the [http://www.ifixit.com/Teardown/iPhone-4S-Teardown/6610/1 iFitIt Teardown], the model number for the [[n92ap|iPhone 4S]] is A1387... --[[User:Balloonhead66|Balloonhead66]] 07:23, 14 October 2011 (MDT)
:For which 4S model? Color, memory? Or for all the same? Do you know more? -- [[User:Http|http]] 10:59, 14 October 2011 (MDT)
::Well, the teardown is black... I am guessing sinse they dont use the devices, it would be 8GB... But A1387 sounds like the hardware model, not the device model that starts with <code>MB</code> or <code>MC</code>... So all iPhone 4S's may be A1387... --[[User:Balloonhead66|Balloonhead66]] 15:37, 14 October 2011 (MDT)
:I also have an A1387. I would like to add this number in the list as well. But currently I have no infos. We don't know if this model is different for different memory, color, bootrom, production facility, or for what. Please post here, if you know more or if you have other numbers. This number is engraved on the phone itself (backside). There's also a code "EMC 2430". Let us know if you have a different number there. -- [[User:Http|http]] 05:05, 23 December 2011 (MST)
::My A1387 is also EMC 2430. It's a black AT&T 16GB [[User:Beej|beej]] 09:24, 23 December 2011 (MST)

Timeline

2011-10-30T14:38:44Z

Beej: Undo revision 22084 by Balloonhead66 (talk) how is what reagentx did newsworthy? They're way behind chpwn and stroughton-smith

{{float toc}}
== 2011 ==
=== October ===
*October 5 -- Steve Jobs dies
*October 4 -- Apple announces the new [[N94ap|iPhone 4S]]

=== September ===
*September 17 -- [[MyGreatFest]], first iCommunity and jailbreak centered convention occured
=== July ===
*July 15 -- Apple releases iOS 4.2.9 and 4.3.4, patching all jailbreaking-related vulnerabilities (aside from those in the [[bootrom]]).
*July 6 -- [[User:Comex|comex]] releases [[Saffron]], the first public jailbreak for the [[iPad 2]].
*July 2 -- A beta version of the upcoming jailbreak from [[User:comex|comex]] for the [[iPad 2]], making use of a PDF exploit, was leaked. A hotfix by Apple is expected very soon.
=== June ===
*June 1 -- [[User:ih8sn0w|iH8sn0w]] releases [[iFaith]] to dump SHSH blobs (similar to [[TinyUmbrella]])
=== May ===
*May 6 -- [[PwnageTool]], [[redsn0w]], and [[sn0wbreeze]] are updated for iOS 4.3.3 support (and in the case of sn0wbreeze, iOS 4.2.8 support as well).
*May 3 -- Apple releases iOS 4.2.8 and 4.3.3 to address the location-tracking controversy. Once more, current untethering vulnerabilities remained unpatched.
=== April ===
*April 24 -- [[PwnageTool]], [[redsn0w]], and [[sn0wbreeze]] are updated for iOS 4.3.2 support (and in the case of sn0wbreeze, iOS 4.2.7 support as well).
*April 14 -- Apple releases iOS 4.2.7 and 4.3.2 to fix security issues and connection issues for [[K95ap|iPad 2 CDMA model]], but leaves untethering vulnerabilities unpatched.
*April 3 -- All major jailbreak tools ([[redsn0w]], [[PwnageTool]], [[sn0wbreeze]]) get updated to includes [[i0n1c]]'s untether code to jailbreak devices compatible with iOS 4.3.1 except the [[iPad 2]].
=== March ===
*March 25 -- Apple releases iOS 4.3.1, properly blocking [[User:comex|comex]]'s [[IOSurface Kernel Exploit|exploit]].
*March 13 -- [[User:Comex|comex]] shows a remotely jailbroken [[K95ap|iPad 2 CDMA]].
*March 11 -- Release of the [[iPad 2]] in the USA. The exploits for [[limera1n]] ([[User:Geohot|geohot]]), [[SHAtter]] ([[User:posixninja|p0sixninja]]), and [[comex]]'s [[kernel]] exploit were closed by Apple.
*March 9 -- Apple releases iOS 4.3, fixing the [[HFS Legacy Volume Name Stack Buffer Overflow]] vulnerability.
=== February ===
*February 15 -- New version of both [[PwnageTool]] and [[sn0wbreeze]] were released to support 4.2.1 and untethered using the [[feedface]] exploit.
*February 7 -- The [[Chronic Dev (team)|Chronic Dev Team]] release a version of [[greenpois0n (jailbreak)|greenpois0n]] to jailbreak the [[N92ap|iPhone 4 CDMA model]] using the [[HFS Legacy Volume Name Stack Buffer Overflow]].
*February 3 -- [[User:Jaywalker|Jaywalker]] of the [[Chronic Dev (team)|Chronic Dev Team]] posts [http://www.youtube.com/watch?v=T3NYPVT13xw a video] of custom boot using a soon to be released version of [[Greenpois0n (jailbreak)|greenpois0n]].
=== January ===
*January 12 -- Apple discontinues iOS support for [[N82ap|iPhone 3G]] and [[N72ap|iPod touch 2G]] since today's beta release of iOS 4.3. Also first time a beta iOS for [[K66ap|Apple TV 2G]] is released.
*January 11 -- Verizon announces [[N92ap|CDMA version of iPhone 4]].

==2010==
===November===
*November 28 -- [[ultrasn0w]] 1.2 is released by the [[iPhone Dev Team]] to unlock [[N82ap|iPhone 3G]] and [[N88ap|iPhone 3GS]] on baseband 6.15.00
*November 22 -- Apple releases iOS 4.2.1 (respectively 4.2 for [[K66ap|Apple TV 2G]])

===October===
*October 31 -- The [[iPhone Dev Team|Dev Team]] releases [[redsn0w]] 0.9.6b2 which jailbreaks iOS 4.1, 4.2 and 3.2.2 on every device available at the time of release (except for iPT 2G MC). It also includes "DFU" button allowing to flash custom [[IPSW]] from Windows [http://blog.iphone-dev.org/post/1452044444/redsn0w-limera1n-fun (see blog post)].
*October 20 -- The [[iPhone Dev Team|Dev Team]] releases [[PwnageTool]] 4.1 which jailbreaks iOS 4.1 and 3.2.2 on every device available at the time of release. [http://blog.iphone-dev.org/post/1359246784/20102010-event (see blog post)]
*October 18 -- [[Chronic Dev (team)|Chronic Dev Team]] releases [[Greenpois0n (jailbreak)|greenpois0n]] RC4 which added support for iPod touch 2G (MC and MB) for an untethered jailbreak using [[User:comex|comex]]'s kernel exploit and the [[usb_control_msg(0xA1, 1) Exploit]].
*October 12 -- [[Chronic Dev (team)|Chronic Dev Team]] releases [[Greenpois0n (jailbreak)|greenpois0n]] after switching its exploit from [[SHAtter]] to [[limera1n]], in the hope that [[SHAtter]] remains for 5th generation devices. (The exploit [[limera1n]] uses was fixed in the [[iBoot (Bootloader)|iBoot]] revision found in iOS 4.2 beta 2, which means Apple knows about the vulnerability and the next [[bootrom]] revision may have it patched.)
*October 10 -- Following the first [[limera1n]] beta release, [[User:geohot|geohot]] released multiple versions, each fixing bugs affecting previous releases. [[Chronic Dev (team)|Chronic Dev Team]] officialy anounces that, in order to keep [[SHAtter]] undisclosed and possibly preserve it for 5th generation devices, [[Greenpois0n (jailbreak)|greenpois0n]] would be delayed in order to incorporate this new exploit [[limera1n]] uses.
*October 9 -- In order to push [[Chronic Dev (team)|Chronic Dev Team]] to change the exploit used on [[Greenpois0n (jailbreak)|greenpois0n]], [[User:geohot|geohot]] rushed out a beta version of [[limera1n]].
*October 8 -- [[User:Geohot|Geohot]] comes back to the scene with a new [[bootrom]] exploit believed to work on all devices, as shown on the resurrected [http://www.limera1n.com limera1n web site]. He prompts [[Chronic_Dev_(team)|Chronic Dev Team]] to use his exploit instead of [[SHAtter]], but, since [[Greenpois0n (jailbreak)|greenpois0n]] is already scheduled to October 10, it may be not possible. [[User:Geohot|Geohot]] ETA'd his [[limera1n]] release to October 11, if [[Greenpois0n (jailbreak)|greenpois0n]] can't be changed to use this new exploit. This decision, however, would burn 2 [[bootrom]] exploits: [[SHAtter]] itself and the one used by [[limera1n]], which is unpatchable by firmware updates.
*October 6 -- Chronic Dev Team issues expected ETA of [[Greenpois0n (jailbreak)|greenpois0n]] as October 10, featuring the new [[SHAtter]] exploit for devices with the [[S5L8930]].

===September===
*September 30 -- [[User:MuscleNerd|MuscleNerd]] of the [[iPhone Dev Team]] posts [http://www.youtube.com/watch?v=adVp-IxcDHI the first video] of an [[K66ap|Apple TV 2G]] jailbroken via [[SHAtter]].
*September 27 -- [[User:MuscleNerd|MuscleNerd]] of the [[iPhone Dev Team]] posts [http://www.youtube.com/watch?v=aoX1Q8ym2J8 the first video] of an [[N81ap|iPod touch 4G]] jailbroken via [[SHAtter]].
*September 20 -- [[User:pod2g|pod2g]] discloses details about the [[usb_control_msg(0xA1, 1) Exploit‎]] here at The iPhone Wiki. It was used in [[redsn0w]] the following day.
*September 9 -- The existence of [[SHAtter]] is revealed. Further details were not released, however.
*September 8 -- Apple releases the [[N81ap|iPod touch 4G]], and iOS 4.1, closing the [[AT+XAPP Vulnerability]].
*September 1 -- Apple event. They announced the new [[N81ap|iPod touch 4G]], [[K66ap|Apple TV 2G]], iOS 4.1, and [[iTunes]] 10.

===August===
*August 12 -- [[Saurik]] releases the first version of PDF Patcher, which installs Apple's patch for the FreeType vulnerability (used in conjunction with other exploits by [[Star]]). It works on firmwares as far back as 2.x, and renders iOS 3.2.2 and 4.0.2 useless for jailbreakers. Jailbreaking and installing this patch is currently the only way for users of first generation iPod touches and iPhones to protect themselves against malicious use of the exploit.
*August 11 -- Apple releases iOS 4.0.2 for [[iPhone]]/[[iPod touch]] and iOS 3.2.2 for [[K48ap|iPad]] as a hotfix for [[Star]]'s exploits. [[Ultrasn0w]]'s exploit remains, since there's no [[Baseband Firmware|baseband]] update on those versions.
*August 3 -- Just before midnight in [[User:planetbeing|planetbeing]]'s timezone [[ultrasn0w]] has been released by the [[iPhone Dev Team]] to [[unlock]] the [[N90ap|iPhone 4]].
*August 1 -- [[User:Comex|comex]] releases [[Star]], a [[jailbreak]] for all iDevices with iOS 3.1.2 through 4.0.1.

===July===
*July 30 -- [[N90ap|iPhone 4]] is released in major countries (second wave).
*July 26 -- Jailbreaking is now officially legal in the U.S.A.: [http://www.eff.org/press/archives/2010/07/26 EFF Wins New Legal Protections for Cell Phone Jailbreakers and Unlockers]
*July 15 -- Apple releases iOS 3.2.1 and 4.0.1.

===June===
*June 24 -- [[N90ap|iPhone 4]] is launched.
*June 22 -- [[iPhone Dev Team]] releases [[PwnageTool]] 4.0 and later 4.0.1 for all devices on 4.0 except those with newer bootroms (some [[N72ap|iPod touch 2G]] and [[N88ap|iPhone 3GS]] devices, and all [[N18ap|iPod touch 3G]] and newer devices).
*June 21 -- [[iPhone Dev Team]] releases [[redsn0w]] 0.9.5 to jailbreak 4.0 on [[N82ap|iPhone 3G]] and [[N72ap|iPhone touch 2G]] ([[iBoot-240.4|old bootrom]]).
*June 21 -- [[iPhone Dev Team]] releases [[ultrasn0w]] 0.93, an unlock for baseband firmwares [[4.26.08]], [[5.11.07]], [[5.12.01]], and [[5.13.04]].
*June 21 -- Apple releases iOS 4.0
*June 19 -- [[User:Geohot|geohot]] holds a speech at the [[Nuit du hack 2010|Nuit du Hack]]

===May===
*May 3 -- Windows version of [[Spirit]] has been updated to not require Windows 98 compatibility mode to run and fixed a photo deletion issue.
*May 2 -- [[User:Comex|comex]] releases [[Spirit]], an [[untethered jailbreak]] for all iDevices with iOS 3.1.2 through 3.2.

===April===
*April 3 -- Apple releases the [[K48ap|iPad]].

===Feb===
*Feb 12 -- [[User:sherif hashim|sherif_hashim]] discovers [[AT+XAPP Vulnerability]] and passes it to [[User:MuscleNerd|MuscleNerd]], an elite member of the [[iPhone Dev Team]]
*Feb 2 -- Apple releases iOS 3.1.3, closing [[usb_control_msg(0x21, 2) Exploit|usb_control_msg(0x21, 2)]] vulnerability used by [[blackra1n]], [[redsn0w]], et. al.

==2009==
===November===
*November 3 -- [[User:Geohot|geohot]] releases [[blackra1n]] RC3, a software jailbreak for all devices. Includes a new unlock for baseband [[5.11.07]] called [[blacksn0w]] and is also noticeably faster than previous versions.

===October===
*October 11 -- [[User:Geohot|geohot]] releases [[blackra1n]] RC1, a 30 second software jailbreak for all devices, including a [[tethered jailbreak]] for the [[N18ap|iPod touch 3G]], and [[N88ap|iPhone 3GS]] and [[N72ap|iPod touch 2G]] units with newer bootrom revisions.

===September===
* September 24 -- [[User:iH8sn0w|iH8sn0w]] discovers the [[AT+XEMN Heap Overflow|AT+XEMN]] crash independently.
* September 9 -- The [[N18ap|iPod touch 3G]] with [[S5L8922]] processor is released. [[N72ap|iPod touch 2G]] units continue shipping, but with [[iBoot-240.5.1|a new bootrom]]. [[N88ap|iPhone 3GS]] units also begin shipping with [[iBoot-359.3.2|a new bootrom]]. These are no longer vulnerable to the [[0x24000 Segment Overflow]].
* Apple releases iOS 3.1/3.1.1 (7C144/7C145), closing the [[iBoot Environment Variable Overflow]] and [[AT+XLOG Vulnerability|AT+XLOG]] + [[AT+FNS]] Baseband Exploits.

===July===
* July 14 -- [[User:Geohot|geohot]] releases [[purplesn0w]], a software unlock for the [[X-Gold 608]] using [[AT+XLOG Vulnerability|the same exploit as ultrasn0w]], but handled differently. Minutes later, an explanation and source code was posted.
* July 7 -- The [[iPhone Dev Team]] updates [[redsn0w]] and [[ultrasn0w]] to version 0.8, now with [[N88ap|iPhone 3GS]] support. Saurik also updates [[WinterBoard]] to support the [[N88ap|iPhone 3GS]].
* July 3 -- [[User:Geohot|geohot]] releases [[purplera1n]], a software jailbreak for the [[N88ap|iPhone 3GS]].

===June===
* June 28 -- [[User:Geohot|geohot]] posts pictures on his blog of the first fully jailbroken [[N88ap|iPhone 3GS]].
* June 25 -- It's discovered that [[N88ap|iPhone 3GS]] is vulnerable to the [[0x24000 Segment Overflow]].
* June 24 -- The [[iPhone Dev Team]] releases [[ultrasn0w]], an [[unlock]] for [[X-Gold 608]] thanks to [[AT+XLOG Vulnerability|a new exploit]] discovered by [[User:Oranav|Oranav]].
* June 23 -- [[User:Geohot|geohot]] announces he's found a new exploit in [[iBoot (Bootloader)|iBoot]] he calls [[purplera1n]].
* June 19 -- Release of [[N88ap|iPhone 3GS]] to the public and the release of [[PwnageTool]] 3.0 and [[redsn0w]] for jailbreaking devices running iOS 3.0
* June 17 -- Apple releases iOS 3.0.
* June 8 -- Apple announces the [[N88ap|iPhone 3GS]].

===March===
* March 10 -- Information about the [[0x24000 Segment Overflow]] exploit used for the [[N72ap|iPod touch 2G]] [[untethered jailbreak]] is released thanks to the combined work of [[chronic]], [[CPICH]], [[User:Posixninja|posixninja]], [[User:Pod2g|pod2g]], [[ius]], [[planetbeing]], [[User:MuscleNerd|MuscleNerd]], and co. after being leaked and sold by [[NitroKey]]. To prevent users wasting their money on a stolen exploit, the Hybrid DevTeam decided to release it immediately.

===January===
* January 31 -- The [[iPhone Dev Team]] released [[redsn0w Lite]], a [[tethered jailbreak|tethered]] [[N72ap|iPod touch 2G]] [[jailbreak]]. It combines the [[ARM7 Go]] vulnerability with the well-established [[pwnage]] flow for other Apple mobile devices. It was bundled in a way that allowed usage on iOS 2.2.1 by uploading [[iBoot (Bootloader)|iBoot]] from iOS 2.1.1, which is vulnerable to [[ARM7 Go]], to the device while in [[DFU Mode]].
* January 29 -- Apple releases iOS 2.2.1, closing the [[AT+stkprof]] exploit.
* January 25 -- [[0wnboot]] is released to [http://code.google.com/p/chronicdev/ chronicdev google code page], thanks to [[AriX]], [[User:ChronicDev|chronic]], [[CPICH]], [[westbaer]], [[ius]], [[User:Pod2g|pod2g]], the rest of the iPod devel crew on IRC, and to the #iphone-hax lab rats. Within days, [[AriX]] and the [[Chronic Dev (team)|Chronic Dev Team]] got a ramdisk booting for a [[tethered jailbreak]].
* January 17 -- [[User:MuscleNerd|MuscleNerd]] of the [[iPhone Dev Team]] [https://twitter.com/MuscleNerd/status/1127346766 shows a video demo] of the first jailbroken [[N72ap|iPod touch 2G]].
* January 16 -- [[ARM7 Go]] vulnerability disclosed where else but here on The iPhone Wiki, for developers to poke and prod at.
* January 15 -- The [[iPhone Dev Team]] [https://twitter.com/iphone_dev/status/1120595069 tweets the VFDecrypt key] for iOS 2.2 on [[N72ap|iPod touch 2G]], demonstrating for the first time that unsigned code can now be run on that device.
* January 1 -- The [[iPhone Dev Team]] releases [[yellowsn0w]] 0.9 beta for baseband [[2.28.00]].

==2008==
===December===
* December 27 -- [[25C3 presentation "Hacking the iPhone"]]
* December 21 -- [[User:MuscleNerd|MuscleNerd]], of the [[iPhone Dev Team]] does a live demo of the 3G unlock, dubbed as [[yellowsn0w]]: http://qik.com/video/729275

===November===
* November 21 -- Apple releases iOS 2.2.

===September===
* September 9 -- Apple releases iOS 2.1. [[N72ap|iPod touch 2G]], which no longer had the [[Pwnage 2.0]] exploit, is revealed.

===August===
* August 18 -- Apple releases 2.0.2 fimware. [[iPhone Dev Team]] releases [http://wikee.iphwn.org/news:pwnage20announcement QuickPwn], a 2.x [[pwnage]]/ramdisk combination exploit that allows jailbreaking without needing to create custom IPSWs.
* August 4 -- Apple releases 2.0.1 fimware

===July===
* July 22 -- [[TA_Mobile]] hardware dumps the 3G baseband (bootloader 5.8 & FW 1.45.00) by desoldering the [[NOR]].
* July 19 -- [[iPhone Dev Team]] releases [[PwnageTool]] 2.0, jailbreaking and unlocking the 2.0 software on the [[M68ap|iPhone 2G]] and jailbreaking iOS 2.0 on the [[N82ap|iPhone 3G]] and [[N45ap|iPod touch]].
* July 15 -- Apple releases iOS 1.1.5, the last of the 1.x firmwares
* July 11 -- [[N82ap|iPhone 3G]] is released. Apple releases iOS 2.0 and MobileMe on the same date, resulting in server issues.

===June===
* June 9 - [[N82ap|iPhone 3G]] is announced at [[WWDC]] '08.

===April===
* April 3 -- [[iPhone Dev Team]] releases [[PwnageTool]] 1.0, making use of the [[pmdx exploit]] (to patch RSA checks out of the [[kernel]], to write unsigned to [[NOR]])

===March===
* March 12 -- [[iPhone Dev Team|Dev team]] releases dual-boot jailbreak method, only to be silently fixed in 2.0.
* March 4 -- [[User:N000b|George Zhu (n000b)]] releases [[iLiberty / iLiberty+]].

===February===
* February 28 -- [[Cydia Application|Cydia]] is released as an open-source alternative to [[Installer.app]], and prepares to take over the jailbreak application scene upon 2.0's release.
* February 26 -- Apple releases iOS 1.1.4.
* February 11 -- [[User:Zibri|Zibri]] leaks the [[Ramdisk Hack]] in [[ZiPhone]], the first all-in-one unlock, activate, jailbreak solution.
* February 8 -- [[User:Geohot|geohot]] releases software unlock for 4.6. Apple states 25% of phones were never activated with AT&T.

===January===
* January 28 -- [[iPhone Dev Team]] releases [[Soft Upgrade]] jailbreak for 1.1.3.
* January 24 -- [[Nate True]] releases a version of [[iBrickr]] that used the [[Soft Upgrade]] method to jailbreak 1.1.3 for [[M68ap|iPhones]].
* January 18 -- [[User:Geohot|Geohot]] and his friends [http://iphonejtag.blogspot.com/2008/01/112-otb-unlocked.html unlocked 1.1.2 OTB 4.6 by test point], the unbeatable version at that time.
* January 18 -- [[iPhone Dev Team]] posts YouTube video of a jailbroken 1.1.3, which was made possible by the dual boot jailbreak from [[bgm]].
* January 15 -- Apple releases iOS 1.1.3, closing the [[Mknod]] exploit. In addition, everything now runs as "mobile" instead of "root."

== 2007 ==
===November===
* November 15 -- [[Baseband Bootloader|Baseband bootloader]] 4.6 is found on new [[M68ap|iPhone]]s, which initially had no [[unlock]].
* November 12 -- Apple releases iOS 1.1.2, closing the [[LibTiff]] and [[Symlinks]] exploits.
* November 2 -- [[JailbreakMe|AppSnapp]] is released, bringing jailbreaking to the mainstream iPhone user.

===October===
* October 23 -- iPhone-Elite Team releases the [[Virginizer]].
* October 14 -- [[User:AriX|AriX]] releases iJailBreak, the first automated [[n45ap|iPod touch]] jailbreak for the Mac.
* October 12 -- [[User:planetbeing|planetbeing]] releases [[touchFree]], the first automated [[N45ap|iPod touch]] jailbreak.
* October 10 -- [[cmw]] (aka Niacin) and Dre release the LibTiff exploit to jailbreak the [[N45ap|iPod touch]], which is later adapted for use in [[JailbreakMe|AppSnapp]].

===September===
* September 27 -- Apple releases iOS 1.1.1.
* September 11 -- [[iPhone Dev Team]] releases [[iUnlock]], first free software unlock.
* September 10 -- [[IPSF]] releases first paid software unlock.
* September 9 -- Apple announces the [[N45ap|iPod touch]] at a media event.

===August===
* August 23 -- [[User:Geohot|geohot]] and team release [[hardware unlock]] method.
* August 21 -- [[Installer.app]] is released by Nullriver, first GUI apps are distributed.

===July===
* July 23 -- First phones are used with other carriers by means of [[SIM hacks]].
* July 20 -- nightwatch adapts a [[toolchain]] to the iPhone. The first apps are compiled.
* July 9 -- [[iPhone Dev Team]] releases a [[jailbreak]] method. The first use of this is ringtones.
* July 3 -- DVD Jon first cracks [[activation]]. People can use the apps on the phone without a subscription.

===June===
* June 29 -- [[M68ap|iPhone]] is released. World's most hyped consumer product.
* June 26 -- The [[iPhone Dev Team]] was formed.

IOS

2011-10-30T14:35:55Z

Beej: Undo revision 22085 by Balloonhead66 (talk) Source?

{{lowercase}}
[[Image:iOS logo.png|150px|thumb|The iOS logo]]
'''iOS''', formerly known as iPhone OS, is the operating system for the [[iPhone]], [[iPod touch]], [[iPad]] and [[K66ap|Apple TV 2G]]. iOS has four abstraction layers: the Core OS layer, the Core Services layer, the Media layer, and the Cocoa Touch layer. The OS takes ~350MB of the device's total memory storage, this means that users will not get their full storage space.

In iOS 4.0+, it takes up ~800MB of space, changing the root partition from 500MB to 1000MB, due to the 2x graphics that have been added for the [[N90ap|iPhone 4]] and [[n81ap|iPod touch 4G]] retina displays.

In iOS 5.0, Apple began pushing towards a computer-less experience for iOS. (e.g.- Devices can be activated and updated over the air.) In addition, multitasking gestures are now enabled by default.[http://events.apple.com.edgesuite.net/11piubpwiqubf06/event]

== External Links ==
{{wp|iOS version history|Full version history}}

MDM6610

2011-10-23T15:15:18Z

Beej: s/file is a/files is an/

[[Image:MDM6610.jpg|thumb|MDM6610 in an iPhone 4S]]
This is the Qualcomm MDM6610 baseband chip used in the [[N94ap|iPhone 4S]].

== Baseband Firmware ==

The firmware for the baseband chip comes in Trek-X.X.XX.Release.bbfw files (with X being the version). The bbfw file is just a renamed standard ZIP archive and contains a couple of .mbn files which are all digitally signed with a certificate from Qualcomm. At least one of the .mbn files is an [http://en.wikipedia.org/wiki/Executable_and_Linkable_Format ELF] file. Qualcomm's Senior Engineer [http://www.linkedin.com/pub/shital-mehta/1/9a0/a58 Shital Mehta] is involved with the programming of the firmware.

== Known Versions ==

=== [[N94ap|iPhone 4S]] ===
[[1.0.11]] 5.0 (Build 9A334)

{{stub|firmware}}
[[Category:Baseband]]

MDM6610

2011-10-23T14:43:11Z

Beej: Add missing apostrophe

[[Image:MDM6610.jpg|thumb|MDM6610 in an iPhone 4S]]
This is the Qualcomm MDM6610 baseband chip used in the [[N94ap|iPhone 4S]].

== Baseband Firmware ==

The firmware for the baseband chip comes in Trek-X.X.XX.Release.bbfw files (with X being the version). The bbfw file is just a renamed standard ZIP archive. and contains a couple of .mbn files which are all digitally signed with a certificate from Qualcomm. At least one of the .mbn file is a ELF file. Qualcomm's Senior Engineer [http://www.linkedin.com/pub/shital-mehta/1/9a0/a58 Shital Mehta] is involved with the programming of the firmware.

== Known Versions ==

=== [[N94ap|iPhone 4S]] ===
[[1.0.11]] 5.0 (Build 9A334)

{{stub|firmware}}
[[Category:Baseband]]

Talk:Tethered jailbreak

2011-10-23T01:38:47Z

Beej: /* re-write */ new section

I suggest no work should be done on making it untethered until the iphone 3,1 is released. {{unsigned|Revolution|01:01, October 15, 2009 (EST)}}

No work done until iPhone3,1? That's a stretch. How about no public-work / for release until iPhone 3,1. If no jailbreakable iPhone3,1 in July, then no upgrade (for me) from iPhone2,1 :) . [[User:Iemit737|Iemit737]] 02:49, 16 October 2009 (UTC)

thats probably what revolution implied :P [[User:ChronicDev|ChronicDev]] 03:05, 16 October 2009 (UTC)

Really I think no work at all since nitrokey published the exploit being kept in secret I think no work should be done so there is no risk of any compromise. and secondly if nitrokey got access to an unpublished exploit twice I think that there should be more security about all of this. Since nitrokey stole the a baseband exploit and a bootrom exploit. Soz about my rambling Im very tired [[User:Revolution|Revolution]] 04:02, 16 October 2009 (UTC)

actually [[NitroKey]] stole 2 baseband exploits from devteam and then 1 boootrom exploit from us, so they burned a potential unlock vector making them bigger douches :P

anyway, info was a bit more "loose" at the time, and we have definitely taken measures to secure all of our private information. If you were implying that any new secret info that we find will be seen by nitrokey, then we are already screwed by that logic. [[User:ChronicDev|ChronicDev]] 05:02, 16 October 2009 (UTC)

== re-write ==

it looks to me like this whole page could use a re-write, but as i'm not offering to do it, i suppose i shouldn't complain ;) in any case, how should we incorporate info on BigBoss's new "semitethered jailbreak" package? see http://thebigboss.org/semitethered-jailbreak --[[User:Beej|beej]] 19:38, 22 October 2011 (MDT)

N90AP

2011-10-22T14:38:58Z

Beej: Undo revision 21943 by Ferrarix5a (talk) if you think having another place we have to maintain for various baseband versions is a good idea, please argue your case on the Talk page

[[Image:IPhone 4 GSM.png|right|thumb|iPhone 4 (GSM model)]]
This is the iPhone 4 (GSM model). Announced on WWDC keynote in June 2010. It features a new exterior design, 5-megapixel camera with LED flash, the 960x640 Retina display screen and [[Facetime|FaceTime]] Video Calls. It runs iOS 4.0 and later.

== [[S5L8900|Application Processor]] ==
It uses the [[S5L8930|Apple A4]] CPU, same as the [[k48ap|iPad]], [[n81ap|iPod touch 4G]], and [[k66ap|Apple TV 2G]]. However, it ships with 512 MB of RAM, double that of the other A4-based devices. [http://www.macrumors.com/2010/06/17/iphone-4-confirmed-to-have-512mb-of-ram-twice-the-ipad-and-3gs/]

== [[Baseband Device]] ==
It uses the [[X-Gold 618]].

== GPS ==
The iPhone 4 uses the [[Broadcom BCM4750]] single-chip GPS receiver, like the iPad. [http://www.ifixit.com/Teardown/iPhone-4-Teardown/3130/3]

== Specifications ==
'''Color:''' Black and White 
'''Size''': 115.2 mm (4.5 inches) (h), 58.6 mm (2.31 inches) (w), 9.3 mm (0.37 inches) (d) 
'''Weight''': 135 g (4.8 oz) 
'''Battery''': Standby up to 300 hours, talk time up to 7 hours on 3G and up to 14 hours on 2G 
'''Rear camera''': 5MP with Autofocus and manual focus (''Tap to focus''), supporting HD video recording @ 30FPS 
'''Front camera''': VGA photos and video @ 30 FPS, supporting [[FaceTime]] Video Calls

== Major Upgrades/Difference from [[N88ap|iPhone 3GS]] ==
[[Image:IPhone4Cameras.png|thumb|The iPhone 4 Cameras]]
* Retina display with 960x640 pixel at 326ppi
* New design
* [[S5L8930|A4 processor]]
* RAM upgrade to 512 MB
* [[Gyroscope]]
* Totally new baseband device, firmware, and bootloader
* Two cameras: front (640×480 VGA) and back (5 megapixel)
* Back camera also has a LED Flash. [http://www.apple.com/iphone/features/camera.html]
* WiFi support for 802.11n, but 2.4 GHz only

Talk:N94AP

2011-10-22T01:40:07Z

Beej:

@Beej, what do you mean by "not active" do you have any source to quote on this? --Rekoil 17:52, 20 October 2011 (MDT)
:Quoting from the Wikipedia article on ''GLONASS'' "By 2010, GLONASS had achieved 100% coverage of Russia's territory and in October 2011, the full orbital constellation of 24 satellites was restored, enabling full global coverage." --Rekoil 17:59, 20 October 2011 (MDT)
::Thanks for being vigilant. I sit corrected ;) --[[User:Beej|beej]] 19:40, 21 October 2011 (MDT)