The iPhone Wiki:Community portal/2011

From The iPhone Wiki
Jump to: navigation, search
This is an Archive Page
This page is meant for archiving purposes only, do not modify the contents of this page! To see the list of archive pages, go to the main page for this archive. If you have a reply for one of these discussion topics, move it back to the main discussion page and edit it there.
Other Archives • 2010 • 2011 • 2012 • 2013 • 2014 • 2015 • 2016 •

New Logos
New logo design
A new logo design
A new logo design with a By geohot
New logo design

with a new name

A new logo with a new name
A new logo with a new name and a By geohot

The Logo should be updated as the wiki is no longer iPhone only but (I think) all iOS devices (or a larger part of it). Possibly also a new URL? theioswiki (but i know this is not as easy) -- M2m 16:09, 14 September 2010 (UTC)

A new URL would be something that Geohot would have to do. But although this is not only about iPhones, that doesn't mean we have to change the logo or the URL. At the beginning there was the iPhone and the iPod touch. Now only the iPad has come to the family. Nothing really new. -- http 22:25, 14 September 2010 (UTC)
Isn't the new AppleTV said to be running iOS as well ? ;) --M2m 23:22, 14 September 2010 (UTC)
Yes --5urd 00:07, 31 October 2010 (UTC)
I could design a new logo that has all the iOS family on it including all generations of the phone and the ipod touch, ATV, and iPad if it is still wanted... --Locke
That won't be neccassary as I am already in the midst of creating one... --5urd 19:16, 5 November 2010 (UTC)
Done... --5urd 23:46, 5 November 2010 (UTC)
If anyone wants, I can shrink the Red apple down from 32x32 to 16x16 so it looks better... I just downloaded The iPhone Wiki favicon aqnd used Convert ICO to make it a png and it came out at 32x32, so I used that. If anyone wants, I can shrink the apple to 16x16... --5urd 02:40, 14 November 2010 (UTC)
Nice! Just a few things: I doubt the wiki will be renamed to "The iOS Wiki", and the "By geohot" line is inappropriate, as this wiki is edited/improved by all of us, he's just the guy who set it up. Nice though! Did you use GIMP by any chance? --The preceding unsigned comment was added by fike (talk) 18:02, 12 December 2010 (UTC). Please consult this page for more info on how to sign pages, and how to fix this.
Paint.NET :) --5urd 04:17, 8 January 2011 (UTC)

Useless Team Pages

I think we should remove all the team pages of users. Keep the Chronic and iPhone dev teams, but the rest that are just milking the wiki as a way to seek fame. There is no purpose for it and it just causes a large amount of useless edits and arguments. Instead of having a team page how about just add the software you make and use the credits part of it? Is there really a need for team pages? I am open to all discussions, just don't argue here. --JakeAnthraX 14:49, 7 November 2010 (UTC)

As long as the team in question is actually doing *something* I see no reason not to document them. MaybachMan 15:11, 7 November 2010 (UTC)
Well my counter to that is still there is no need for it. Maybe when you guys do something that is amazing or make something that isn't already out there. I don't want to fight, don't think I do. I just want the wiki to be peaceful and a place of knowledge. Not people gloating to be parts of groups and leech off of other people. Is the page really that important to you? --JakeAnthraX 15:14, 7 November 2010 (UTC)
My team made a jailbreak using usb control msg for iPodTouch2g MC. It was compatible with 4.0.2 and it was semitethered. Anyway I don't want it on theiphonewiki, because this wiki should NOT be TheTeamsWiki.--Qwertyoruiop 15:22, 7 November 2010 (UTC)
The page isn't for showing off, we made it so we can have a place to list all the projects the team makes, which I find useful. I don't want to fight over it, but I just think it has a use for organising knowledge on here, that's all. MaybachMan 15:19, 7 November 2010 (UTC)

Well I'm done arguing. I still say both be removed until a group release is made. Either way it doesn't matter much to me, but I had to make things fair between the groups. Let other people voice their opinions for a day or so and don't remove deletion request until it is decided as a community, okay? --JakeAnthraX 15:21, 7 November 2010 (UTC)

Until then, the deletion should be undone. I notice my team's page is already deleted for some reason. Or the content is, anyway. MaybachMan 15:23, 7 November 2010 (UTC)

Wait, i have an idea. A wiki for projects by secondary teams. If anyone wants, I can host it. :) --Qwertyoruiop 15:24, 7 November 2010 (UTC)

I have a question. Why is it that it is like you must be on a team to be on here, cuz you don't! --5urd 15:25, 7 November 2010 (UTC)

Well without the deletion tags people won't know to discuss it, but it is up to the sysops in the end. So Yeah. --JakeAnthraX 15:29, 7 November 2010 (UTC)

A Official hacking team is a team which is well-recognised among people. The team must have contributed to the Jailbreak Community. For example, the iPhone Dev Team found a number of exploits and made jailbreaks which were used by a large number of people. Take 0wnDev for example, they didnt do anything big and PwnPie was just a script making use of greenpois0n and iRecovery which were done by the official hacking teams afaik and they didnt find any exploits; Same for Maybach Dev Team. --Whiteshinyapple 13:01, 28 January 2011 (UTC)

REQUEST

Can somebody please make a wiki page on how to boot the device into Recovery mode via itunesmobiledevice? Thank you! --Johnnyfranks67 18:11, 18 October 2009 (UTC)

Check the MobileDevice Library page to use MobileDevice Framework --Whiteshinyapple 13:05, 28 January 2011 (UTC)

VFDecrypt GUIs

I don't mean to sound like a dictator, but I'd like to request for no more VFDecrypt GUIs to be added here. There are more than enough of them, so I feel there really isn't a need to add any more. Whenever a new one arises, an argument spews over about its usefulness, as well as whether it belongs on this wiki. These arguments clog up the Recent changes page, making it tougher to keep an eye on things with the wiki. So, once again, I'd like to ask for no more VFDecrypt GUIs to have a place on this wiki. As of now, this is NOT a rule that will be imposed. It's just a polite request, nothing more. --Dialexio 19:35, 30 October 2010 (UTC)

I'd ask for GUI's of all kinds, such as VFDecrypt, iRecovery, and so on. Anyone can make a GUI. It takes a real hacker to write a program. --dra1nerdrake 22:52, 30 October 2010 (UTC)
We only have 3 publiclly available ones + 2 in development --5urd 00:14, 31 October 2010 (UTC)
I saw this coming when the new page for GiRecovery (Zeratul) first appeared some months ago. This Wiki is not intended to promote these tools. I didn't want to just delete the page though. One way we could go: Make sure all applications (including highly recognized ones and jailbreak apps like Limera1n) will get listed on an overview Tools page. It should be categorized by tool purpose and operating system. Maybe also by related iOS firmware. As soon as this works well, we just have to assure that not anybody adds new tools there. For example by having two users request a new entry (without the author). We can start this Tools page in any case. Initially we can include all these useless GUI apps already existing here also. -- http 07:38, 31 October 2010 (UTC)
We could delete the original pages and merge them with the page of the original app in a subsection. To be honest, though, I still don't see the point of having 4 softwares that do the same thing with the same features. --Ryccardo 09:22, 31 October 2010 (UTC)
All of them just decrypt. But mine will have 7zip integration to extract it for you and possibly look up the key automatically based on the Dmg name... --5urd 14:28, 31 October 2010 (UTC)
The iPhone Wiki:Ground rules#No advertising your website/forum/wiki/etc - The iPhone Wiki is to help people understand the method and not just give people a GUI which can do those stuff.Take limera1n for example,they descibe about the software and their payload, method, explanation is over there which is what theiphonewiki wants and not just a GUI with the name over there and crediting their "own" team. --Whiteshinyapple.
To 5urd: Don't undo the stuff I did. The sysops will decide and it is their decision not yours. --Whiteshinyapple.
A GUI is not a wiki website or forum apple dude --5urd 03:51, 20 November 2010 (UTC)
Yup a GUI is a program not a website. Those VFDecrypt GUI's just basically call the real VFDecrypt Program which does the real work.It is the same as using a batch file to call a program.If we saw a iphone wiki page which is showing a batch file; wouldnt we delete that? Its the same for these GUI's. We got to delete them!They are just advertising their program so that people will download it and geohot doesnt want people to advertise their stuff,he didnt say about a program but im sure that he meant any type of advertising including this.--Whiteshinyapple 13:01, 28 January 2011 (UTC)
If you think geohot wouldn't like it, go ask him! --5urd 15:21, 28 January 2011 (UTC)

Hacking softwares which are fit to be in this wiki

Some people are just copying other jailbreaks source code/idea, renaming it and they are putting up a iphone wiki page.What to do with them? Seas0npass is an example which copied sn0wbreeze/PwnageTool idea. --Whiteshinyapple 13:37, 28 January 2011 (UTC)

They are all just GUIs for xpwn. They are all valid "hacking softwares". --Toddyt1 14:27, 28 January 2011 (UTC)
Well, recognized tools like PwnageTool and sn0wbreeze definitely belong in here, although they are also "just" GUI tools. For other tools we can discuss. Regarding Seas0npass, I think it should remain, as this is the only tool for Apple TV 2G. --http 18:37, 28 January 2011 (UTC)

Toolchain Status

It would be very worthwhile to post a current status of the Toolchain(s). It seems like the last work was a couple of years ago. There is no specific Linux (esp Fedora) section. The old llvm-svn revision in the tutorial won't compile (FC14) and the new llvm-svn compiles but is missing bits that the iphone-dev requires. I've cross-referenced to the work on the code.goole.com/p/iphone-dev wiki but no luck. It might very well be that the "Toolchain Concept" is an effort whose time has come and gone! tjames123 20:12, 29 January 2011 (UTC)

The iPhone Wiki app

Today I said to myself: "Why don't we create an iPhone app (for cydia) of the iPhone Wiki? Are you with me? Do you love this project? :-) Send me an email Umbi98 16:30, January 31, 2011 (UTC)

To do that, you need to access: http://theiphonewiki.com/wiki/index.php?title=(PAGENAME)&action=render and create a web control. --5urd 00:49, 1 February 2011 (UTC)

Phoenix 8E200 (iPhone 4 CDMA)

What are your thoughts on how to differentiate between key pages for the GSM and CDMA iPhone 4s? --Dialexio 03:20, 1 February 2011 (UTC)

I like (iPhone 4) and (iPhone 4 CDMA) --5urd 03:25, 1 February 2011 (UTC)
I suppose it sounds fine. I'd prefer to change the "(iPhone 4)" suffix to "(iPhone 4 GSM)" though (consistency and whatnot). Does that sound fine? --Dialexio 03:32, 1 February 2011 (UTC)
Hey, if you got time, do it. But there are a lot of links to change then. also, it would clog the Recent Changes --5urd 03:40, 1 February 2011 (UTC)
Indeed... It's probably gonna be a pain, but I suppose it could be done on a slow day. (I really have nothing better to do. :P) --Dialexio 03:43, 1 February 2011 (UTC)
Thinking internationally, 95% of iPhone 4's will probably be the GSM ones a year from now. The CDMA one will be the "weird one". I think it can be implied that just iPhone 4 means GSM/UMTS and unless otherwise specified it is for the CDMA version. Iemit737 04:27, 1 February 2011 (UTC)
I suppose we can stick with "(iPhone 4)" and "(iPhone 4 CDMA)" for now. Perhaps the idea of adding "GSM" can be revisited if there's a substantial amount of CDMA iPhones, and/or if it goes international. --Dialexio 05:42, 1 February 2011 (UTC)

Multilanguage Support?

I would be very happy if the Admins would implent something like [[1]] to make it easier for people who speak less english! --Pattyland 20:53, 5 April 2011 (UTC)

The problem with multilanguage is maintenance. We had or have a few pages in other languages, but nobody looks at them and far less maintain it. And how do you know if this new link to the russian site is spam or not? Actually all hackers and the jailbreak community is english speaking; this means you simply have to learn english. I can say that, because I'm not native english speaking either. For french language articles there are a lot of user guide sites etc. So overall, no, this won't happen unless we have a huge amount of hackers and users in another language. --http 07:43, 6 April 2011 (UTC)
Hm, do you have any links? The most pages are useless for normal Users, but Pages like Firmware or ITunes_Errors are so useful for people who are new to the Jailbeak-Szene or/and are not very good in English.--Pattyland 01:41, 17 April 2011 (UTC)
Maybe this helps: Useful Links --http 08:02, 17 April 2011 (UTC)

iPhone 4

Instead of explicitly mentioning the GSM and CDMA models (like "iPhone 4 (GSM model)" and "iPhone 4 (CDMA model)") all the time, can we just specify "iPhone 4" where applicable? I want to change how we talk about the iPhone 4 to something like how we currently mention the iPad 2 on wiki pages. --Dialexio 03:42, 19 April 2011 (UTC)

I actually find it odd that Apple implemented it the way they did, with two different models and firmwares. Seems like a lot for just a different baseband. --geohot 03:50, 19 April 2011 (UTC)
I think it's a bigger problem how they named the iPad 2, a different model for Wi-Fi, GSM and CDMA, while for the first generation they didn't differentiate it (see my new Models article). For the iPhone 4, it came out later and maybe has some more hardware changes, so I understand why it's different there. I wouldn't change all existing articles, especially because the iPhone 5 is not too far away anymore. But yes, for future articles we can use iPad 2 or iPhone 5. For the iPhone 4 we might change this when all future devices are handled this way. --http 05:12, 19 April 2011 (UTC)

All in one Template:Keys

With parser functions installed. I was thinking about creating the ultimate key list things for the fw. I am awesome at parser functions and could do it. Because one edit would be spaces across all of the pages. Any thoughts? --5urd 01:28, 16 July 2011 (MDT)

For me it is not clear what you want to change exactly. Please explain in more detail. Thanks. --http 03:51, 16 July 2011 (MDT)
This... --5urd 21:22, 16 July 2011 (MDT)

Old software

There is a bit of old jailbreak and package managers that need to be added to the wiki just so it is more complete. For example there is touchFree, Rock.app, and iJailbreak are a few I know of that "should" be added. Anyone care to help? --JakeAnthraX 22:31, 16 July 2011 (MDT)

OK, you put touchFree up, when you put up Rock.app and iJailbreak, we need to go through and put them on Jailbreak --5urd 17:11, 17 July 2011 (MDT)

New rule proposal

I've discussed this with http, and we'd like to introduce a new rule. Once in a while, we all come across that time where somebody makes a bunch of consecutive changes (editing pages, uploading files, moving pages, etc.). It hinders everyone's ability to go through the recent changes to see or monitor newly-added information, and clogs up people's Twitter timelines. Therefore, http and I want to introduce a rule: be reasonable with the amount of changes you make in a day. I think about 20 changes per hour per user should be good. Of course, exceptions can always be made; simply drop a note explaining why ahead of time. Obviously, actions like reversing vandalism can be overlooked. Failure to abide by this rule can result in a warning (first offense), a one week ban (second offense), a two week ban (third offense), a month-long ban (fourth offense), or a permanent ban (fifth offense). Thoughts on this? I want to stress that this is just a proposal at the moment. This has not been made into an official rule yet. --Dialexio 19:50, 16 July 2011 (MDT)

Sorry about that. The 403 error is coming back to haunt me again, for me it affects external links and big edits, and once it errors me out on that page, it wont let me edit that page again... So I had to space it out. --5urd 20:07, 16 July 2011 (MDT)
Sounds good to me. --JakeAnthraX 20:11, 16 July 2011 (MDT)
I like it, again sorry. --5urd 20:17, 16 July 2011 (MDT)
I would set a limit per 24 hours and another per week. Or to make it easier to verify, a limit on the number that appears in the active users list (last 30 days). Also 5urd had the pre-approval to separate the firmware page (not the other ones though), so changes with exact pre-approvals wouldn't count towards this limit (or as 1). Maybe Talk page edits also shouldn't count? I think the main problem is flooding the timeline without having better content. I also sometimes make a lot of changes by fixing typos or double redirects. Should that count? I would also add a limit of 5 edits on the user page(s) per week. If you want, we can also leave it just as you proposed; any change counts, but max. 20/hour. But please also specify if you mean full hours or 60 minutes. That's a difference if s/o makes 15 changes at ten to five and another 15 changes at ten past five. Would that be over limit or not? And just to make it clear; having multiple accounts shouldn't help avoiding this rule. --http 02:31, 17 July 2011 (MDT)
I agree that minor edits like fixing typos shouldn't (and won't) apply to this rule, but it will still congest the change log. We could extend this rule to provide a separate limit for minor edits, or not impose a limit for minor edits altogether; I'm open to either one. (Don't even think about using the "minor edit" flag for gigantic section updates.) As for the limit, maybe we'll have a combination of the two: users can make up 20 edits per hour (I'm actually beginning to lean more towards a 15 edits/hour limit now, if that's fine), and no more than 50 edits per day. And nobody should even have multiple accounts on here to begin with. :P --Dialexio 11:58, 17 July 2011 (MDT)
I like that, but is it reset every hour on the hour or is it 60 minutes for the 15/20 edits? --5urd 13:37, 17 July 2011 (MDT)
I knew I forgot to cover something. v.v To make things simple, we'll make it on the hour, but it will be changed to 60 minutes if I see edits being clumped together (i.e.- Person A does 15 edits up to 11:58, and then another 15 between 12:00 and 12:03) constantly. And before it gets asked by anyone, the unused number of edits you make will not "roll over" to the next hour. --Dialexio 14:46, 17 July 2011 (MDT)
That makes sense. go on vacation for 5 days and you get 500+ edits. --5urd 14:50, 17 July 2011 (MDT)
Oh, forgot, is this going to be a PHP implementation that geohot will have to install, cuz I bet I could make one, or is this going to be a monitored "installation"? --5urd 14:51, 17 July 2011 (MDT)
Sorry for the late response. It'll be monitored for now; I don't think there will be a need to bother geohot to install a MediaWiki extension. If anyone never expressed his/her opinion on this, I'd like to wrap up discussions about the rule and finalize it by July 27. --Dialexio 18:47, 22 July 2011 (MDT)

Key pages

Just a few things on my mind that I felt like sharing…

  1. I don't care if you use the template or not, as long as the pages look the same. (In other words, there's no need to convert pages if they will still look and smell the same.)
  2. Please don't create "blank" key pages. If you want to create the page, please supply at least one key. Posting just a "skeleton" of the page doesn't provide us any information.

I'm not hunting you down if you do either of those (yet), but it's something to keep in mind. :) --Dialexio 20:58, 6 August 2011 (MDT)

Integrating Info from i0nic

Stefan Esser's slides from his blackhat presentation have been published. There's lots of info in them that ought to be integrated in this wiki, but i'm currently slammed getting ready for Burning Man. anybody have the cycles (Slides) --beej 11:15, 25 August 2011 (MDT)

And now he's got a newer version here: http://www.slideshare.net/i0n1c/blackhat-usa-2011-stefan-esser-ios-kernel-exploitation

beej 10:58, 14 September 2011 (MDT)

Still slammed? I'll do it if you are --Haifisch
Yep. Just moved and slammed for the foreseeable future. Have at! BTW: You should indent your replies with colons and sign them with 4 tildes. -- beej 19:30, 26 September 2011 (MDT)

Baseband version numbers

From Itaiyz97 talk page

Maybe you havn't noticed, but our standard for baseband version numbers is #.##.## despite it being 0#.##.##. When it does reach 10.##.##, we will change it. But seeing as over 5 years they have only gone up to 7.##.##, it would've a while or possible not even at all... --5urd 06:48, 4 October 2011 (MDT)

Yes, please get informed about what is being used here before moving pages. But on the other hand, why remove the leading zero? Shouldn't we change this "standard" to the real version numbers? I personally would prefer this. -- http 07:33, 4 October 2011 (MDT)
Yes, I agree. A lot of times those basebands are referred to as 0#.##.## (ie. 04.26.08 instead of 4.26.08) --The preceding unsigned comment was added by Itaiyz97 (talk). Please consult this page for more info on how to sign pages, and how to fix this.
When have you ever seen that? --5urd 18:57, 4 October 2011 (MDT)
I would like that better because 10.##.## is coming soon (maybe a year), but by then it would be like the moving the Firmware Keys off of the bad pages flooding, not to mention editing the pages (especially the ones with {{keys}} and the baseband) --5urd 18:57, 4 October 2011 (MDT)

Further discussion

Before anyone moves the baseband pages again, I want to reach a consensus on this. Do we use #.##.## or 0#.##.## like the file name is? --5urd 08:28, 9 October 2011 (MDT)

I think that we should probably go with what iOS reports. (e.g.- 1.0.06 for the CDMA iPhone 4, 03.10.01 for the GSM iPhone 4…) --Dialexio 12:41, 9 October 2011 (MDT)
I fully agree with Dialexio (as mentioned earlier already), but I missed the CDMA part. And I do know that a lot of pages might be affected. -- http 14:52, 9 October 2011 (MDT)
I am also confused. Maybe we could do it based on the file name. Cuz what I am getting at from dialexio's post is that only GSM has the 0 in front of it and the CDMA has no zero. But the file name has a 0 in front (like Pheonix-03.00.03.zip). I may be wrong. But maybe we could just go with all are 2x2x2 page names instead of 1x2x2 or the file name... --5urd 16:08, 9 October 2011 (MDT)
I am requesting permission for mass editing. I will go through all the basebands with pages and move them to a prefix of 0 and go through all of the pages with links and fix them. The protected Main Page may need editing.. --5urd 19:35, 10 October 2011 (MDT)
I will do the key pages some other time as not to over flood... --5urd 19:46, 10 October 2011 (MDT)
I'm going to deny this request because while it's ideal to eliminate redirects, it's not a high priority to immediately move everything to the new naming format. It can be done over time. For the CDMA iPhone, neither the baseband file nor iOS's reported version number has a zero in the front. (I'm not too sure about the CDMA iPad, but I'm pretty sure it's in the same boat.) --Dialexio 21:24, 10 October 2011 (MDT)
How would you do this "over time"? I counted 38 baseband pages (maybe some less), so I would recommend to move all these at once and update just the baseband chip page too. Other references can be fixed over time. What do you think? --http 02:11, 11 October 2011 (MDT)
That is what I mean. Move all the BB pages and mod Firmware and Beta Firmware (and the BB Chip pages) and over time, do the other ones (like Firmware Keys) --5urd 17:42, 11 October 2011 (MDT)
All right, go for the move then. The references can be fixed "over time." --Dialexio 18:26, 11 October 2011 (MDT)
Kthx --5urd 20:45, 11 October 2011 (MDT)

More info from Esser

i0n1c's slides for his latest talk are here: HiTB-2011-KUL-D2T2.pdf. Tons of great info on his ARM emulator used for finding ROP gadgets. How do we integrate this into the wiki? --beej 06:19, 13 October 2011 (MDT)

kernelcache differences

What would you think of adding a section listing the differences of kernelcache.XYZ between different versions of iOS?
I came up with this because I've been trying to find out a way to re-enable the CameraConnectionKit support on iPhone 4 (according to this: http://www.youtube.com/watch?v=-e8xzqEZr5g it was working until iOS 5 beta 7, although I can't find any IPSW image for beta 6 or 7 anywhere on the internet). I have compared an iPad and iPhone4 rootfs for differences (using an old version, 4.2.1 I think) but there aren't many significant ones. It is my understanding that the kexts are linked with the kernel. The kernelcache between iPhone and iPad are different, so I figure there might be something there to investigate. I was thinking that an approach similar to this: http://www.glassechidna.com.au/2010/projects/i-phone/unpacking-ios/ would allow us to extract the kexts and restore USB host functionality.
Am I missing something? any pointers? --Nordpic 2:55, 9 November 2011 (PST)

Apple TV 2G versions (Part 34)

The firmware version numbers for the Apple TV 2G still doesn't seem to be standardized on this wiki. Which naming scheme should we use: the IPSW name, what the Apple TV 2G reports, or something else? --Dialexio 14:24, 18 October 2011 (MDT)

I would prefer the internal one as it matches better to the other devices' build (when more devices are listed). See also the discussion here: Firmware#Major_Resorting_Request -- http 16:29, 18 October 2011 (MDT)
Personally, I prefer what the Apple TV says. If we do it based on internal versions, then we will have 4 apple tv's underneath 4.3 final. Remember from before you separated by major version? --5urd 17:03, 18 October 2011 (MDT)
How did I neglect to drop my own two cents on the issue? :s Personally, I'd prefer getting the version from the IPSW name, but for the sake of simplicity on the wiki, the Apple TV-reported version would work best. --Dialexio 20:34, 24 October 2011 (MDT)
I like that. Because if we did it based on the IPSW, the 4.2 betas would be under 4.3 (what they are based on) while the 4.4 betas will stay under 4.4 despite the firmware being based on 5.0. --5urd 20:38, 24 October 2011 (MDT)
Where did (Part 34) come from? --5urd 20:38, 24 October 2011 (MDT)
It's just a number I threw into the title. --Dialexio 00:19, 13 November 2011 (MST)
I don't see any benefit in sticking with these arbitrary shown numbers. All 5.x firmwares are in the 4.x section and even the same version firmwares beside it (for other devices) are (functionally) totally different firmware versions. But if you all want to stick with it, I won't change it then. --http 06:06, 25 October 2011 (MDT)
But remember the three "4.3" ATV builds (4.2/4.2.1/4.2.2/4.3) (8F191m/8F202/8F305/8F455)? --5urd 14:10, 26 October 2011 (MDT)
I totally agree with you and I'd love to refer to the firmwares by what they're actually based on as well, but it's much easier to refer to a firmware as "4.2.2" instead of "4.3 Build 8F305." --Dialexio 00:19, 13 November 2011 (MST)

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? --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. -- 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. --Dialexio 11:31, 5 November 2011 (MDT)
Ok --5urd 16:58, 12 December 2011 (MST)

MD Bootrom

While editing the models page, I noticed that the new white 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. thekirbylover 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. --Dialexio 10:27, 23 December 2011 (MST)
Ah, I see. Thanks for checking. thekirbylover 16:33, 23 December 2011 (MST)