The iPhone Wiki:Community portal

See also: Unsolved problems

iPhone-Elite

I think we should include all this old stuff before it gets lost: 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. --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
• 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? --http (talk) 21:31, 13 February 2013 (UTC)

I like Boot Arguments. --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. --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 concept. --Jaggions (talk) 10:30, 14 June 2013 (UTC)

I disagree. If anything add an iPhone 5 to the logo but everything else is ok. --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.) --Dialexio (talk) 16:25, 14 June 2013 (UTC)

Can we not do flat? --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. --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. --iAdam1n (talk) 21:16, 14 June 2013 (UTC)

You may not want it like that. That's your opinion. --5urd (talk) 01:55, 15 June 2013 (UTC)

We could make a poll, and see if most users agree or disagree. --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. --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 (iOS6) and move the modifications (not general stuff) to Mediawiki:iOS6.css. Then we can do another verbatim copy to iOS7 and modify Mediawiki:iOS7.css. We could then set the default skin to either iOS6 or iOS7 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. --5urd (talk) 21:17, 15 June 2013 (UTC)

I like 5urd's suggestion. --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. Britta (talk) 00:11, 29 August 2013 (UTC)

Yeah removing the shadow will make everything seem more flat but like http I'm still using the classic MonoBook skin --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 in addition to my release of the Phoenix Semi-Untethered. --Ph0enix (talk) 18:36, 22 July 2013 (UTC)

Did you find any exploits? --Haifisch (talk) 18:54, 22 July 2013 (UTC)

No. phyrrus9, a team member found the vulnerability. I am the one who exploited it. --Ph0enix (talk)

I can back up this "claim". I was a part of it. --5urd (talk) 20:52, 28 July 2013 (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. Britta (talk) 05:57, 28 August 2013 (UTC)

Easy tasks for new editors

• Finish converting the remaining error codes listed here http://theiphonewiki.com/wiki/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) --Dirkg (talk) 22:40, 28 August 2013 (UTC)

Key page links for A5+

I was thinking, so we do not clog up wanted pages, I think we should not link to pages for A5+ that have not been created due to it is not possible so we could just use the black text. It is annoying to see all that red when you also click them accidentally. Of course IF ever an exploit is found, this can be changed. --iAdam1n (talk) 15:11, 30 August 2013 (UTC)

For me it doesn't matter if a few page links are red. We want to link and have them anyway some day in the future. But if you feel better when there are no links, I'm fine with that too. Wait for some other opinions before changing it. --http (talk) 23:09, 31 August 2013 (UTC)

I do prefer it. I will wait until the 7 days are up anyway. --iAdam1n (talk) 23:19, 31 August 2013 (UTC)

I personally don't mind seeing them. I vote to leave them. It would be a massive undertaking. As for the wanted pages list, I might be able to cook up some JavaScript to take care of it. --5urd (talk) 18:20, 4 September 2013 (UTC)

That could work. --iAdam1n (talk) 20:57, 4 September 2013 (UTC)

Changing "Build" on Firmware and Beta Firmware

I was going to post this on the talk page of "Firmware", but then I realized it would involve creation of many pages, so I'm posting here.
What I'm proposing is we change the Firmware's and Beta Firmware's device's "Build" column to look like this (iPhone 2G used) [links removed to save bytes]:

Version	Baseband	Codename	Build	Release Date	IPSW Download URL	SHA1 Hash	Comments	File Size
1.0	03.06.01_G	Alpine	1A420	?	iphoneproto.zip	6e798e906c6590a7521ef89b731569be6d05b3aa	Prototype; macrumors	109,813,128
	03.11.02_G	Heavenly	1A543a	29 Jun 2007	iPhone1,1_1.0_1A543a_Restore.ipsw	fb8bb3ee2e9a997affbb97868599f2995c78209c	Initial US shipment.	95,604,348
1.0.1	03.12.08_G	SUHeavenlyJuly	1C25	31 Jul 2007	iPhone1,1_1.0.1_1C25_Restore.ipsw	a00b85a7a55d62a94be5fbf5effbc42fd63f3097		95,627,958
1.0.2	03.14.08_G		1C28	21 Aug 2007	iPhone1,1_1.0.2_1C28_Restore.ipsw	7f5c0ff1f84a0202b75a55c3fcb362e415334d1e		95,627,324
1.1.1	04.01.13_G	Snowbird	3A109a	27 Sep 2007	iPhone1,1_1.1.1_3A109a_Restore.ipsw	d441dd1c71ce18f25d8fc4faa71c1e6eaa02d02c		159,668,150
1.1.2	04.02.13_G	Oktoberfest	3B48b	12 Nov 2007	iPhone1,1_1.1.2_3B48b_Restore.ipsw	797c02e7d660940e8d9a16cc7229ccf3f67dd8b1	Initial Euro shipment.	167,927,501
1.1.3	04.03.13_G	Little Bear	4A93	15 Jan 2008	iPhone1,1_1.1.3_4A93_Restore.ipsw	b3dec7580bd00dc4faf28449d9618ef40aeacc96		169,950,551
1.1.4	04.04.05_G		4A102	26 Feb 2008	iPhone1,1_1.1.4_4A102_Restore.ipsw	000811bac096011b50ebf6ec1ec2285b62fda4cb		169,946,442
2.0	04.05.04_G	Big Bear	5A347	11 Jul 2008	iPhone1,1_2.0_5A347_Restore.ipsw	9c510a3cfce789fa5f92a8f763c231bac82ff6d4		228,768,637
2.0.1			5B108	04 Aug 2008	iPhone1,1_2.0.1_5B108_Restore.ipsw	61de6a2bd6ceddc9ecabad1671b91a59b3824bc4		254,048,068
2.0.2			5C1	18 Aug 2008	iPhone1,1_2.0.2_5C1_Restore.ipsw	b84b57bea919bdc720287ec908c1378e7d7b5e1b		253,589,000
2.1		Sugar Bowl	5F136	12 Sep 2008	iPhone1,1_2.1_5F136_Restore.ipsw	353b7745767b85932e14e262e69463620939bdf7		242,171,241
2.2		Timberline	5G77	21 Nov 2008	iPhone1,1_2.2_5G77_Restore.ipsw	cbfc6ff886ce89868a55547b9fb980dbf92e6418		257,576,980
2.2.1		SUTimberline	5H11	27 Jan 2009	iPhone1,1_2.2.1_5H11_Restore.ipsw	43b95ebe1e51f8d30eae916053396595c08440d3		257,593,705
3.0		Kirkwood	7A341	17 Jun 2009	iPhone1,1_3.0_7A341_Restore.ipsw	2afd3f8ede17390737f508473ed205506a0bd23f		240,394,111
3.0.1			7A400	31 Jul 2009	iPhone1,1_3.0.1_7A400_Restore.ipsw	34c391fbbc7b31b159372766de39ce5c9cc26ebb	Hotfix for an SMS exploit.	240,439,502
3.1		Northstar	7C144	09 Sep 2009	iPhone1,1_3.1_7C144_Restore.ipsw	b7b5f436f81c6f855410e8b44a3d432ccaacd6fc		252,536,460
3.1.2			7D11	08 Oct 2009	iPhone1,1_3.1.2_7D11_Restore.ipsw	e4a1171542dbbd3093516d9c02047b9f7e143050		252,515,888
3.1.3		SUNorthstarTwo	7E18	02 Feb 2010	iPhone1,1_3.1.3_7E18_Restore.ipsw	eab23a7f8d2a17cb71046c50fc5f67ec390a3c2b		238,319,275

We would then at the respective pages, give an overview of the build train, like what firmwares it was used on? Maybe even a link to the Wikipedia article of the ski resort it's named after? In addition, we could replace the the links of modified build trains, like SUTimberline, with a link to a section on Timberline (i.e. [[SUTimberline]] to [[Timberline#SUTimberline|SUTimberline]])? --5urd (talk) 18:00, 7 September 2013 (UTC)

I would agree if we did not link to the codename pages, just have it as text. --iAdam1n (talk) 19:09, 7 September 2013 (UTC)

I would move the build number next to the firmware version, and as Adam said, don't link the codenames. (Actually, maybe the codenames could get dropped altogether? Or even moved to a brand new page?) --Dialexio (talk) 07:10, 8 September 2013 (UTC)

Hm actually, I like the idea of trashing the codenames and moving build before baseband. Although this would be a big task of moving pages but we could just move say 20 each per day. --iAdam1n (talk) 07:25, 8 September 2013 (UTC)

I'm against dropping the build train from the page names, but I'd be fine with removing the build train from the link text. --5urd (talk) 19:14, 8 September 2013 (UTC)

That would be just more complicated. We should either drop them on the key pages too, or better still, keep them here in a new column like you listed but without the linking to pages with [[]] and move it so that the build is next to version then codename then baseband. --iAdam1n (talk) 19:32, 8 September 2013 (UTC)

Yeah, that's what I was saying... --5urd (talk) 19:33, 8 September 2013 (UTC)

Version	Build	Codename	Baseband	Release Date	IPSW Download URL	SHA1 Hash	Comments	File Size
1.0	1A420	Alpine	03.06.01_G	?	iphoneproto.zip	6e798e906c6590a7521ef89b731569be6d05b3aa	Prototype; macrumors	109,813,128
	1A543a	Heavenly	03.11.02_G	29 Jun 2007	iPhone1,1_1.0_1A543a_Restore.ipsw	fb8bb3ee2e9a997affbb97868599f2995c78209c	Initial US shipment.	95,604,348
1.0.1	1C25	SUHeavenlyJuly	03.12.08_G	31 Jul 2007	iPhone1,1_1.0.1_1C25_Restore.ipsw	a00b85a7a55d62a94be5fbf5effbc42fd63f3097		95,627,958
1.0.2	1C28		03.14.08_G	21 Aug 2007	iPhone1,1_1.0.2_1C28_Restore.ipsw	7f5c0ff1f84a0202b75a55c3fcb362e415334d1e		95,627,324
1.1.1	3A109a	Snowbird	04.01.13_G	27 Sep 2007	iPhone1,1_1.1.1_3A109a_Restore.ipsw	d441dd1c71ce18f25d8fc4faa71c1e6eaa02d02c		159,668,150

For people who cannot visualise this. Are we all agreed? If so, I can start this due to it seems a few commented and like it. --iAdam1n (talk) 19:42, 8 September 2013 (UTC)