Difference between revisions of "Talk:Main Page"

From The iPhone Wiki
Jump to: navigation, search
(Seas0nPass)
(Eliminating the firmware key links on the device lists)
 
(246 intermediate revisions by 35 users not shown)
Line 1: Line 1:
{{Talk Archive|Start to November 12, 2010}}
+
{{Talk Archive}}
   
== Posting [[KBAG]]s ==
+
== Baseband Chip Page Titles ==
  +
For the baseband chip page titles, I think we should stick with the model number despite the marketing name. Pages:
Is there really a need to post [[KBAG]]s, if we already have decryption keys? Hell better yet instead of posting [[KBAG]]'s post missing keys. --[[User:GreySyntax|GreySyntax]] 16:57, 12 November 2010 (UTC)
 
  +
* [[S-Gold 2|PMB8876]] marketed "S-Gold 2"
: i agree, [[KBAG]]'s are practically useless after you have got the keys from them but [[User:liamchat|liamchat]] seems to post them anyway... --[[User:Cj|cj]] 17:01, 12 November 2010 (UTC)
 
  +
* [[X-Gold 608|PMB8878]] marketed "X-Gold 608"
:: i added them because i didn't have that device and on some pages the [[KBAG]]'s are there with the keys so why not do that on all pages --[[User:Liamchat|liamchat]] 20:38, 12 November 2010 (UTC)
 
  +
* [[XMM 6180]] marketed "X-Gold 618"
:::Posting the [[KBAG]] and not saying what there from is useless. --[[User:GreySyntax|GreySyntax]] 20:40, 12 November 2010 (UTC)
 
  +
* [[MDM6600]] (unknown marketing name)
:::the layout was confusing i grab them in one big lump and it follows a generic system ( see [[User_talk:Liamchat#KBAGs|KBAG layout ]] ) --[[User:Liamchat|liamchat]] 20:45, 12 November 2010 (UTC)
 
  +
* [[MDM6610]] (unknown marketing name)
::::The least you could do is place them appropriately, and not force someone like me to clean up after you. --[[User:Dialexio|<span style="color:#C20; font-weight:normal;">Dialexio</span>]] 21:10, 12 November 2010 (UTC)
 
  +
* [[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|<span style="color:#C20; font-weight:normal;">Dialexio</span>]] 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 ==
== Protection ==
 
  +
'''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
Can someone inform me why the main page was protected from all users? Not just newly created users? Cheers. --[[User:Beau|Beau]] 03:19, 8 November 2010 (UTC)
 
  +
:An edit war took place earlier, and unfortunately there's no option to protect it from just newly created users. If you want to make a change, Http and I will be more than happy to carry it out (pending approval, but we're pretty reasonable). --[[User:Dialexio|<span style="color:#C20; font-weight:normal;">Dialexio</span>]] 03:46, 8 November 2010 (UTC)
 
  +
'''0x2''' iTunes error 1,-1,11 :
::There kindof is, you just need to update to 1.16, but i guess only geohot can do that... :( --[[User:Balloonhead66|Balloonhead66]] 03:49, 8 November 2010 (UTC)
 
  +
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].
:::What was the war about? --[[User:Balloonhead66|Balloonhead66]] 00:22, 17 November 2010 (UTC)
 
  +
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.
:::Thanks [[User:Dialexio|Dialexio]], just thought that it was strange that Wiki pages are starting to be put together for [[:/Applications]] yet there's no link present on the main page - if anything it might fit best atop the Software list. --[[User:Beau|Beau]] 03:58, 8 November 2010 (UTC)
 
  +
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.
::::It's actually already there, under the name "Filesystem" (which links to the root directory of iOS). :) --[[User:Dialexio|<span style="color:#C20; font-weight:normal;">Dialexio</span>]] 04:33, 8 November 2010 (UTC)
 
   
  +
'''0x3''' The situation that there is no BB installed on iPhone! :
== Protection on [[Main Page/Welcome]] ==
 
  +
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.
I think you should protect [[Main Page/Welcome]] as it is editable by anyone... That is how I added the info on an IRC chatroom... --[[User:Balloonhead66|Balloonhead66]] 18:51, 24 November 2010 (UTC)
 
  +
Keep in mind that if this solution works..., it will need the SHSH for downgrading the iOS firmware to do reset the BB.
:does this work on any other part's of this page and do we need an irc channel for a wiki --[[User:Liamchat|liamchat]] 23:18, 24 November 2010 (UTC)
 
  +
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.
::No reason not to have an IRC, just leave it be and people can go there to discuss things like formatting and what not. --[[User:JacobVengeance|JakeAnthraX]] 23:41, 24 November 2010 (UTC)
 
  +
'''--[[User:Kambiz|Kambiz]] 07:49, 13 May 2012 (MDT)K.N'''
:::It would be better to have it on a more iOS centered network such as Chronic's irc or OSx86. --[[User:GreySyntax|GreySyntax]] 23:52, 24 November 2010 (UTC)
 
:::i have just made a better one on irc.expl0it.com in the room theiphonewiki however we need a system if people decide to use this --[[User:Liamchat|liamchat]] 00:37, 25 November 2010 (UTC)
 
::The Main Page is protected for three years only because n00bs kept adding themselves as iPhone hackers. Otherwise, it'd be open for editing by users like you. I see no need to protect [[Main Page/Welcome]] as long as there's no edit war, vandalism, or spam. :) --[[User:Dialexio|<span style="color:#C20; font-weight:normal;">Dialexio</span>]] 23:27, 24 November 2010 (UTC)
 
:::Surely there is no way it'll stay protected for 3 years, right? Just until we can get the n00bs to stop being so ridiculous, I suppose. It doesn't really matter, as I don't actually edit the main page, but I think it's rather funny. :P --[[User:Dra1nerdrake|dra1nerdrake]] 00:00, 25 November 2010 (UTC)
 
::::Too bad people ignored [http://theiphonewiki.com/wiki/index.php?title=Special%3ALog&type=protect&user=Dialexio&page=Main+Page my warning from September]. :s ''Maybe'' I'll feel nice during the holidays? --[[User:Dialexio|<span style="color:#C20; font-weight:normal;">Dialexio</span>]] 00:19, 25 November 2010 (UTC)
 
:::::If I could 'Like', 'Favorite', or 'Retweet' that post, I'd do it in a heartbeat. --[[User:Dra1nerdrake|dra1nerdrake]] 16:56, 26 November 2010 (UTC)
 
   
  +
== Bluetooth Chip on [[iPhone 5]] ==
== Beta Firmware ==
 
  +
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|<span style="color:#C20; font-weight:normal;">Dialexio</span>]] 20:35, 8 October 2012 (MDT)
   
  +
== Adding vulnerability to main page ==
I'd like to add [[Beta Firmware]] to the list and thought of putting it on the same line as [[Firmware]], like this:
 
  +
The page [[CVE-2013-0964]] is currently orphaned. I think it would fit under the "Vulnerabilities and Exploits" subheading. Can someone with adequate permission make the change? [[User:0x56|0x56]] ([[User talk:0x56|talk]]) 03:52, 12 September 2013 (UTC)
*[[Firmware]] and [[Beta Firmware]]
 
  +
:Added. --[[User:Http|http]] ([[User talk:Http|talk]]) 00:53, 13 September 2013 (UTC)
Anybody against that? Because this page is protected I think it's polite to ask first. -- [[User:Http|http]] 18:44, 27 November 2010 (UTC)
 
:Sounds good to me, though I'd probably make it an indented bullet, like this:
 
:*[[Firmware]]
 
:**[[Beta Firmware]]
 
:Also, was that meant to be a jab at me? :s --[[User:Dialexio|<span style="color:#C20; font-weight:normal;">Dialexio</span>]] 19:17, 27 November 2010 (UTC)
 
::No jab. Sorry if it sounded so. I just don't want to play god here and make changes while all others have to ask. I expect the same from you, at least if it's something that could potentially be disputed. And regarding format, I still prefer one line, to make the main page a little more compact. It's too large to fit on one page already and I don't want to make that worse. --[[User:Http|http]] 20:06, 27 November 2010 (UTC)
 
:::No harm done. :) If the edit is disputable, I would definitely ask on the talk page first. But I digress... Back to the topic. I must agree that the Main Page is definitely getting big, so your proposal would probably work better. --[[User:Dialexio|<span style="color:#C20; font-weight:normal;">Dialexio</span>]] 21:08, 27 November 2010 (UTC)
 
::::Done. --[[User:Http|http]] 21:48, 27 November 2010 (UTC)
 
   
  +
==Update for new devices==
== M0nster (hactivate ONLY) By a iPhone Hacker age 13 ==
 
  +
Somebody should update the main page (table) for the 5s and 5c --[[User:Phyrrus9|Phyrrus9]] ([[User talk:Phyrrus9|talk]]) 21:14, 2 October 2013 (UTC)
  +
:No need. It says "iPhone 4S and newer". --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 22:01, 2 October 2013 (UTC)
   
  +
==Permission==
M0nster is a Hacktivate only programe, witch uses iPSW.exe on 3.1.2 iPhone 2G (Silver Back) only, i hope to add support for the iPod Touch 2G as soon as i can work out how to create firmwarebundles. The Programe has had a public beta realised witch the GUI is subject to change in a later date.
 
  +
Permission to add pangu8? Or should we wait until a Cydia version comes out? --[[User:Awesomebing1|Awesomebing1]] ([[User talk:Awesomebing1|talk]]) 15:52, 22 October 2014 (UTC)
  +
:It has already been added and is fine IMO. I would state that it's SSH only though. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 16:22, 22 October 2014 (UTC)
   
  +
== All of the Watch product images? ==
Log Updates to the Programe:
 
Public beta 1 Hacktivates 3.1.2 iPhone 2G/Very Basic GUI
 
   
  +
So I was looking for Apple product images and found this interesting [https://www.apple.com/shop/sitemaps/sitemap-buy-images.xml document] that has links to all of the (current) product images. Since the Apple Watch has so many models, editions, colors, etc., would it be worthwhile to upload all the images listed from the document? So far I've found [http://store.storeimages.cdn-apple.com/4711/as-images.apple.com/is/image/AppleInc/aos/published/images/w/42/w42ss/sbbk/w42ss-sbbk-detail this one]. (Apple Watch 42mm, Stainless Steel buckle) --[[User:Citrusui|Citrusui]] ([[User talk:Citrusui|talk]]) 18:01, 5 September 2015 (UTC)
{{unsigned|Greggturner98|21:10, 28 November 2010 (UTC)}}
 
:don't advertise your software on the wiki --[[User:Liamchat|liamchat]] 21:50, 28 November 2010 (UTC)
 
:Do we need one for 3.1.3? --[[User:Balloonhead66|Balloonhead66]] 00:49, 29 November 2010 (UTC)
 
   
  +
:It's not a great idea to upload images from Apple's website in general, since they're copyrighted by Apple, unless you can make a decent argument that using a copyrighted image in a particular article is [https://en.wikipedia.org/wiki/Fair_use#Fair_use_under_United_States_law is fair use]. [[User:Britta|Britta]] ([[User talk:Britta|talk]]) 09:01, 6 September 2015 (UTC)
== ABC order ==
 
   
  +
== Removal of Apple TV 3G from "Latest Firmware" Section? ==
I'd like to reorganize the links in alphabetical order, in an effort to curb my OCD-esque tendencies. Nobody has any aversions to this, right? --[[User:Dialexio|<span style="color:#C20; font-weight:normal;">Dialexio</span>]] 07:23, 31 December 2010 (UTC)
 
:What links do you want to sort? Example? Not that I want to do that (I work mostly from iPhone), but I'd like to know what you want to change. Or only on this page? --[[User:Http|http]] 08:07, 31 December 2010 (UTC)
 
::Sorry if I wasn't clear before. I was referring to some of the links on the Main Page. (Namely, the Hardware section, but there are other links that aren't arranged in alphabetical order either.) --[[User:Dialexio|<span style="color:#C20; font-weight:normal;">Dialexio</span>]] 08:41, 31 December 2010 (UTC)
 
:::I would prefer a chronological order. Mostly this order matches alphabetical order, but not always. This can apply also for the hardware list, like the compass being added to later devices. But you're right that there are totally unsorted areas. --[[User:Http|http]] 12:38, 31 December 2010 (UTC)
 
   
  +
Apparently, the Apple TV 3G has not received any updates from Apple for a long time and looks like it will not get any in the future. So, should we remove it from the "Latest Firmware" section on the Main Page? Any other thoughts? --[[User:Tp1194045441|Tp1194045441]] ([[User talk:Tp1194045441|talk]]) 03:51, 28 November 2015 (UTC)
==Hacker User Pages==
 
  +
:It's still been sold so it should stay as it's still "active" for this reason. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 22:34, 23 February 2016 (UTC)
   
  +
== Cleanup ==
Does anyone else think we should organize them so there is the piece at the top that says who they, what team they are/were in, and other basic info. Then have an Achievements section below it stating what they have found/released? Just a thought.
 
--[[User:JacobVengeance|JakeAnthraX]] 17:14, 4 January 2011 (UTC)
 
:Something like [[:Category:Hackers|this list]]? --[[User:Http|http]] 18:10, 4 January 2011 (UTC)
 
::I meant directly on the user pages, like [[User:pod2g]] and so on. So there is a uniform look to it all. --[[User:JacobVengeance|JakeAnthraX]] 18:30, 4 January 2011 (UTC)
 
   
  +
This page has a lot of links... It almost looks intimidating. That's not exactly an impression you want to leave on a first-time visitor. I'd like to clean it up, but I'm not entirely sure on what to cut out. I currently have everything in "Hardware" underneath the basebands in mind, and some of the definitions (be honest, how popular of a topic do you think iBEC is?). Any thoughts on what can or should not be cut? --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 21:09, 23 February 2016 (UTC)
== Processors ==
 
  +
:I think we should remove links to pages that have not been created yet. We can always add them back if/when made. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 22:33, 23 February 2016 (UTC)
   
  +
== KPP ==
We have a single entry here for [[Baseband Device]], but the three processors ([[S-Gold 2]], [[X-Gold 608]] and [[XMM 6180]]) are not listed. --[[User:Http|http]] 22:24, 12 January 2011 (UTC)
 
:Looks like nobody wanted to discuss this. I went ahead and changed it now. --[[User:Http|http]] 01:31, 15 January 2011 (UTC)
 
   
  +
Is there a reason why a KPP page has not been created? It would be useful to many...
== [[Seas0nPass]] ==
 
  +
--[[User:Detiac|Detiac]] 15:19, 9 October 2017 (UTC)
  +
:It would certainly be useful and something that should be on the wiki, but I don't think any active users are knowledgeable enough on the topic to provide a writeup. --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 02:23, 11 October 2017 (UTC)
   
  +
== Rename Bad Stuff section ==
Can we add it? --[[User:Balloonhead66|Balloonhead66]] 03:46, 18 January 2011 (UTC)
 
  +
:Sounds fine with me; it ''is'' pretty notable, after all. :) --[[User:Dialexio|<span style="color:#C20; font-weight:normal;">Dialexio</span>]] 03:54, 18 January 2011 (UTC)
 
  +
I don't know what we could rename it to, but it doesn't come off very well --[[User:Nullpixel|Nullpixel]] ([[User talk:Nullpixel|talk]]) 17:26, 10 October 2017 (UTC)
  +
:Although the name is accurate, "Bad Stuff" does sound a little... off-kilter. Maybe something like "Malicious/Cautionary Topics?" --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 02:23, 11 October 2017 (UTC)
  +
::Sorry for the late response. I agree, this is a better name. --[[User:Nullpixel|Nullpixel]] ([[User talk:Nullpixel|talk]]) 16:10, 23 May 2018 (UTC)
  +
  +
== Various Software ==
  +
  +
I feel like the Various Software section should either be segmented into smaller sections (Downgrading Utilities, Package Managers, etc.) or not exist at all -- and in the former case, would most likely not be under the section Various Software. Any thoughts? --[[User:Wxblank|wxblank]] ([[User talk:Wxblank|talk]]) 16:02, 21 June 2019 (UTC)
  +
  +
== Firmware Status style. ==
  +
  +
I am proposing a change to the firmware status table, to pack-in more info into a smaller space while also being more future-proof.
  +
  +
i believe having the table in this style will improve not only the aesthetic of the table, but also be able to handle more devices in the future.
  +
  +
===Exhibit A===
  +
'''This is what we have now:'''
  +
  +
{| class="wikitable" style="font-size:.95em; width:100%;"
  +
|-
  +
! style="height:3em;" | [[Models|Device]]
  +
! [[List of Apple TVs|Apple TV (4th generation)]] and newer
  +
! [[List of Apple Watches|Apple Watch Series 1]] and newer
  +
! [[HomePod]]
  +
! [[iPad (5th generation)]] and newer<br />[[iPad Air 2]]<br />[[iPad mini 4]]<br />[[List of iPad Pros|iPad Pro]] (12.9-inch, 9.7-inch, 12.9-inch 2nd generation, 10.5-inch)<br />[[iPhone 6s]] through [[iPhone X]]<br />[[iPod touch (7th generation)]]
  +
! [[iPad Air (3rd generation)]]<br />[[iPad mini (5th generation)]]<br />[[List of iPad Pros|iPad Pro (11-inch, 12.9-inch 3rd generation)]]<br />[[N841AP|iPhone XR]] and newer
  +
|-
  +
! style="height:3em;" | Latest<br />[[Firmware|Public Firmware]]
  +
| 13.4.6 <small>(17L570)</small>
  +
| 6.2.6 <small>(17T620)</small>
  +
| 13.4.6 <small>(17L570)</small>
  +
| colspan="2" | 13.5.1 <small>(17F80)</small>
  +
|-
  +
! Jailbreak available?
  +
| {{yes|Yes <br/><small>([[checkra1n]])<ref name="HD-only"></ref><ref name="untestedOS"></ref></small>}}
  +
| colspan="2" {{no}}
  +
| {{yes|Yes <br/><small>([[checkra1n]])</small>}}
  +
| {{No|No <br/><small>(N/A)</small>}}
  +
|-
  +
! style="height:3em;" | Latest<br />[[Beta Firmware|Beta Firmwares]]
  +
| 13.4.8 beta 3 <small>(17M5558b)</small><br/>14.0 beta <small>(18J5313t)</small>
  +
| 6.2.8 beta 3 <small>(17U5559d)</small><br/>7.0 beta (Series 3+) <small>(18R5310a)</small>
  +
| {{n/a}}
  +
| colspan="6" | 13.6 beta 3 <small>(17G5059c)</small><br/>14.0 beta <small>(18A5301v)</small>
  +
|}
  +
<references>
  +
<ref name="HD-only">Apple TV HD only but supports Apple TV 4K with hardware modfications</ref>
  +
<ref name="untestedOS">Check the "Allow untested iOS/iPadOS/tvOS versions" checkbox in the options view to bypass the version check.</ref>
  +
</references>
  +
  +
===Exhibit B===
  +
'''This is the style i propose we replace Exhibit A with:'''
  +
  +
{| class="wikitable" style="font-size:.95em; width:100%;"
  +
|-
  +
! style="height:3em;" | [[Models|Product Linup]]
  +
! [[List of Apple TVs|Apple TV]]
  +
! rowspan="2" | [[HomePod]]
  +
! [[List of Apple Watches|Apple Watch]]
  +
! [[List of iPhones|iPhone]]
  +
! [[List of iPads|iPad]]
  +
! [[List of iPad Airs|iPad Air]]
  +
! [[List of iPad Pros|iPad Pro]]
  +
! [[List of iPad minis|iPad mini]]
  +
! [[List of iPod touches|iPod touch]]
  +
|-
  +
! Supported
  +
! [[Apple TV (4th generation)|Apple TV HD]]<br>and newer
  +
! [[Apple Watch Series 1|Series 1]]<br>and newer
  +
! [[iPhone 6s]]<br>and newer
  +
! [[iPad (5th generation)|5th Generation]]<br>and newer
  +
! [[iPad Air 2]]<br>and newer
  +
! [[iPad Pro (12.9-inch)|12.9-inch (2016)]]<br>and newer
  +
! [[iPad mini 4]]<br>and newer
  +
! [[iPod touch (7th generation)|7th Generation]]
  +
|-
  +
! style="height:3em;" | Latest<br />[[Firmware|Public Firmwares]]
  +
| colspan="2" | 13.4.6 <small>(17L570)</small>
  +
| 6.2.6 <small>(17T620)</small>
  +
| colspan="6" | 13.5.1 <small>(17F80)</small>
  +
|-
  +
! Jailbreak availability
  +
| {{yes|Yes<br/><small>([[checkra1n]])<ref name="untestedOS"></ref><ref name="HD-only"></ref></small>}}
  +
| colspan="2" {{no}}
  +
| colspan="6" {{partial|Yes* <small>([[checkra1n]])<ref name="untestedOS"></ref></small><br><small>*except for devices with the [[T8020|A12]] or newer SoC's.}}
  +
|-
  +
! rowspan="2" style="height:3em;" | Latest<br />[[Beta Firmware|Beta Firmwares]]
  +
| 13.4.8 beta 3 <small>(17M5558b)</small>
  +
| {{n/a}}
  +
| 6.2.8 beta 3 <small>(17U5559d)</small>
  +
| colspan="6" | 13.6 beta 3 <small>(17G5059c)</small>
  +
|-
  +
| 14.0 beta <small>(18J5313t)</small>
  +
| {{n/a}}
  +
| 7.0 beta <small>(18R5310a)</small>*<br>*<small>[[Apple Watch Series 3|Series 3]] and newer only.</small>
  +
| colspan="6" | 14.0 beta <small>(18A5301v)</small>
  +
|}
  +
  +
<references>
  +
<ref name="HD-only">[[Apple TV (4th generation)|Apple TV HD]] only, but can support the [[Apple TV 4K]] with some hardware modifications.</ref>
  +
<ref name="untestedOS">Check the "Allow untested iOS/iPadOS/tvOS versions" checkbox in the options view to bypass the version check.</ref>
  +
</references>
  +
  +
I am open to comments or suggestions - [[User:DanTheMann15|DanTheMann15]] ([[User talk:DanTheMann15|talk]]) 23:11, 30 June 2020 (UTC)
  +
:I agree and prefer the new style. It sucks having devices listed twice but that would change once watchOS 7 is out of beta. Maybe though we could just add a note under the table that watchOS 7 beta’s require series 3 or newer and not have the second list. IMO that’d be better. —[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 00:16, 1 July 2020 (UTC)
  +
  +
That sounds like a good idea, and the note actually fits inside the table! i've changed Exhibit B to reflect this. - [[User:DanTheMann15|DanTheMann15]] ([[User talk:DanTheMann15|talk]]) 01:13, 1 July 2020 (UTC)
  +
  +
:I made the edit before seeing the talk page, oops. I'll leave it like that for now. [[User:Admanny|Admanny]] ([[User talk:Admanny|talk]]) 06:09, 1 July 2020 (UTC)
  +
  +
I like the "Jailbreak availability" text, but on the other hand though many people ask that question: is a "Jailbreak available?", i edited Exhibit B so everyone can see how it looks, get other opinions on it, but overall im down with either way. - [[User:DanTheMann15|DanTheMann15]] ([[User talk:DanTheMann15|talk]]) 08:00, 1 July 2020 (UTC)
  +
:I think "available?" makes more sense to be honest with the yes and no answers. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 13:10, 1 July 2020 (UTC)
  +
::I changed it because it's unconventional for labels in a chart to be written in the form of a question. But, this is a small wiki anyway, so if the consensus sways towards keeping the question, that's fine. I'm still with keeping it as "availability". [[User:Admanny|Admanny]] ([[User talk:Admanny|talk]]) 19:55, 1 July 2020 (UTC)
  +
  +
== Mac in the jailbreak table ==
  +
  +
Why is this in the table? Macs aren't exactly locked up in a BSD jail like iOS devices; they have security to prevent modifying system files by default, but Macs are a more open platform and SIP can be disabled to edit said files. You don't need to run some jailbreaking utility to e.g. change around some system icons in macOS. I presume the intent was to say bridgeOS on Macs with the T2 are susceptible to jailbreaking per the footnote, but the "Supported" row points to "All Macs with the M1". None of the M1 Macs have a T2 chip. The information provided is also for macOS, not bridgeOS. --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 08:24, 14 February 2021 (UTC)
  +
:That can be fixed but it was added as it's "firmware status" not just "jailbreak status" as should be there. --[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 11:40, 14 February 2021 (UTC)
  +
  +
== HTTPS links on firmwares and OTA's that are hosted on "updates.cdn-apple.com" ==
  +
  +
I'm writing this topic because [[User:Dialexio|Dialexio]] hasn't been using https. https has been used here on the wiki regularly since 2019 when adding new firmware links that are hosted on Apple's CDN, which host's all of Apple's firmwares released since April 2018, such as iOS 11.3.1 and newer.
  +
  +
back when apple was still using appldnld.apple.com, adding https (https://secure-appldnld.apple.com) would make the links unreliable or not work at all.
  +
  +
but now with http://updates-http.cdn-apple.com, it works just fine to switch to (https://updates.cdn-apple.com).
  +
  +
it is easy as pie to switch the links to use https by using a good text-editing program that has a "find and replace" function. like [https://notepad-plus-plus.org Notepad++] or [https://wiki.gnome.org/Apps/Gedit Gedit].
  +
  +
  +
is there any good reason we shouldn't be using https on the newer firmwares hosted on Apple's CDN?
  +
  +
- [[User:DanTheMann15|DanTheMann15]] ([[User talk:DanTheMann15|talk]]) 22:32, 5 May 2021 (UTC)
  +
:(This should probably be on [[The iPhone Wiki:Community portal]] instead, but oh well.) It kinda boils down to personal preference; to my understanding, there was never any sort of formal agreement on this. A user simply started converting some links to HTTPS, and I just let them do their thing since I do see benefits of using HTTPS. (At the end of the day though, you're still going to get the same file, especially if you verify its hash.) But personally, I'd rather keep the links the same way Apple provided them— if they gave us an HTTP link, that's what I'll add, and if they gave an HTTPS link, that's what I'll add. I'm not opposed to others changing the links I post to HTTPS as it's still Apple hosting and providing the download links, but I don't feel we should have to go out of our way to add one more step to an already tedious task. You can make an argument that it's for consistency, but that logic can also be used towards converting HTTPS links back to HTTP, and we would also trim the URLs for the older IPSWs so those look more consistent with newer, pre cdn-apple.com releases. --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 00:21, 6 May 2021 (UTC)
  +
  +
i understand where you are coming from, but i will continue to use https on the firmware links i post, since there are more advantages than the other way around, albeit the possible reason why apple gives us http links is likely because https requires valid certificates, which for some reason not everybody has. also it's important to note about HTTPS-Only on some major browsers so http links will not work for those who have that setting enabled. and like i said above, it takes me a fraction of a second to convert the links to https, thanks to Notepad++. perhaps you could add a setting that you can enable in the OTA Catalog Parser that would automatically convert links to https when parsing the links to save time. - [[User:DanTheMann15|DanTheMann15]] ([[User talk:DanTheMann15|talk]]) 18:47, 16 May 2021 (UTC)
  +
  +
well i'll be darned, apple started providing https links for OTA downloads through pallas now! that'll save time on links going forward, i wonder if they'll do the same on IPSW's, only time will tell. - [[User:DanTheMann15|DanTheMann15]] ([[User talk:DanTheMann15|talk]]) 21:27, 17 Jul 2021 (UTC)
  +
  +
== Cleanup ==
  +
  +
Can we clean up the front page? It feels like there's an unnecessary amount of jargon that we can afford to simplify. I don't think we need to link to, e.g. the S5L8947 or the MDM9625 on the front page— the links to the [[Application Processor]] [[Baseband Device]] pages should be sufficient. (We can also probably remove the listing of each and every device under "Hardware" to further save space, but I can understand keeping those.) We also don't need to list every IMG3 or IMG4 tag. --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 16:29, 14 June 2021 (UTC)
  +
  +
:Hey there Dialexio, yes i completely agree with cleaning up the front page, as it is full of repeated garbage. what we could do is consolidate the hardware links to the device lists, i'll make a concept on my [[User:DanTheMann15/Sandbox|Sandbox]] so i can fully show you what i mean. and yeah, we do not need to link the basebands and application processors in the front page, it'll be just fine contained in it's own page but have it's link on the main page be '''Bolded''' to make it easy enough to see. as for the stuff at the bottom of the page, i don't see any real need to change it, though i might see something that needs attention as i comb through it. but overall, after you see what i have in mind, you may make the changes as you wish upon the next beta day. - Cheers! --[[User:DanTheMann15|DanTheMann15]] ([[User talk:DanTheMann15|talk]]) 06:27, 20 June 2021 (UTC)
  +
  +
::I like the effort you made on [[User:DanTheMann15/Sandbox/Main Page|your sandbox page]]! I hope you don't mind that I made a couple of additional edits that I think we can make, with some comments on why I thought the amendment was for the better. (If you don't like it, feel free to revert it and/or say something here.) --[[User:Dialexio|Dialexio]] ([[User talk:Dialexio|talk]]) 01:23, 28 June 2021 (UTC)
  +
  +
:You have my approval on these changes, they look good, and the comments for anyone editing would be helpful to point them to the relevant page. once we are satisfied with the right Hardware side, we can turn on consolidating the left Software side so that the page is considerably shorter, as for the bottom of the page where Development and Help are, i don't see any immediate changes that i can suggest yet but if they come up i'll let you know, and feel free to make adjustments on the sandbox draft, it's what it's there for so we can see what the difference will look like. --[[User:DanTheMann15|DanTheMann15]] ([[User talk:DanTheMann15|talk]]) 03:12, 28 June 2021 (UTC)
  +
  +
== Eliminating the firmware key links on the device lists ==
  +
  +
I have a new change to propose,
  +
  +
Mind cutting the firmware key links from the device lists (e.g [[List of iPhones]], [[List of iPads|iPads]] etc...) and replacing those links with a "See also" section at the bottom of the pages that has a link to [[Firmware Keys]] instead?
  +
  +
I feel it would look MUCH cleaner since it looks messy having it tell the same firmware version twice on devices that have two or more identifiers.
  +
  +
like the iPhone 5s here for example, which has two identifiers:
  +
  +
==== CURRENT SETUP ====
  +
* Firmware:
  +
** Initial firmware: [[Innsbruck 11A466 (iPhone6,1)|7.0 (11A466)]], [[Innsbruck 11A466 (iPhone6,2)|7.0 (11A466)]]
  +
** Latest firmware: [[PeaceUpdate 16H62 (iPhone6,1)|12.5.5 (16H62)]], [[PeaceUpdate 16H62 (iPhone6,2)|12.5.5 (16H62)]]
  +
  +
==== MY SUGGESTION ====
  +
'''Firmwares:'''
  +
* Initial firmware: 7.0 (11A466)
  +
* Latest firmware: 12.5.5 (16H62)
  +
  +
====== See also ====== (AT BOTTOM OF THE PAGE)
  +
  +
[[Firmware Keys]]
  +
  +
  +
---- Notes:
  +
↓ we can also '''bold''' the versions and build numbers like this if we need to.
  +
  +
'''Firmwares:'''
  +
* Initial firmware: '''7.0 (11A466)'''
  +
* Latest firmware: '''12.5.5 (16H62)'''
  +
  +
let me know your thoughts, feedback is always good. --[[User:DanTheMann15|DanTheMann15]] ([[User talk:DanTheMann15|talk]]) [[User:DanTheMann15|DanTheMann15]] ([[User talk:DanTheMann15|talk]]) 07:52, 30 September 2021 (UTC)
  +
:I personally like the key page links as they are, but also see why it’d be cleaner. I suppose it would look better if it’s just one listing. —[[User:IAdam1n|iAdam1n]] ([[User talk:IAdam1n|talk]]) 11:31, 30 September 2021 (UTC)

Latest revision as of 11:31, 30 September 2021

Archives
 • 2009 • 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:

--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. [1]) --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). --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[2]. 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. --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? --5urd 10:04, 8 October 2012 (MDT)

Chipworks analyzed the iPhone 5's Murata Wi-Fi module and determined it uses the BCM4334. I'll add it to the Main Page now. --Dialexio 20:35, 8 October 2012 (MDT)

Adding vulnerability to main page

The page CVE-2013-0964 is currently orphaned. I think it would fit under the "Vulnerabilities and Exploits" subheading. Can someone with adequate permission make the change? 0x56 (talk) 03:52, 12 September 2013 (UTC)

Added. --http (talk) 00:53, 13 September 2013 (UTC)

Update for new devices

Somebody should update the main page (table) for the 5s and 5c --Phyrrus9 (talk) 21:14, 2 October 2013 (UTC)

No need. It says "iPhone 4S and newer". --iAdam1n (talk) 22:01, 2 October 2013 (UTC)

Permission

Permission to add pangu8? Or should we wait until a Cydia version comes out? --Awesomebing1 (talk) 15:52, 22 October 2014 (UTC)

It has already been added and is fine IMO. I would state that it's SSH only though. --iAdam1n (talk) 16:22, 22 October 2014 (UTC)

All of the Watch product images?

So I was looking for Apple product images and found this interesting document that has links to all of the (current) product images. Since the Apple Watch has so many models, editions, colors, etc., would it be worthwhile to upload all the images listed from the document? So far I've found this one. (Apple Watch 42mm, Stainless Steel buckle) --Citrusui (talk) 18:01, 5 September 2015 (UTC)

It's not a great idea to upload images from Apple's website in general, since they're copyrighted by Apple, unless you can make a decent argument that using a copyrighted image in a particular article is is fair use. Britta (talk) 09:01, 6 September 2015 (UTC)

Removal of Apple TV 3G from "Latest Firmware" Section?

Apparently, the Apple TV 3G has not received any updates from Apple for a long time and looks like it will not get any in the future. So, should we remove it from the "Latest Firmware" section on the Main Page? Any other thoughts? --Tp1194045441 (talk) 03:51, 28 November 2015 (UTC)

It's still been sold so it should stay as it's still "active" for this reason. --iAdam1n (talk) 22:34, 23 February 2016 (UTC)

Cleanup

This page has a lot of links... It almost looks intimidating. That's not exactly an impression you want to leave on a first-time visitor. I'd like to clean it up, but I'm not entirely sure on what to cut out. I currently have everything in "Hardware" underneath the basebands in mind, and some of the definitions (be honest, how popular of a topic do you think iBEC is?). Any thoughts on what can or should not be cut? --Dialexio (talk) 21:09, 23 February 2016 (UTC)

I think we should remove links to pages that have not been created yet. We can always add them back if/when made. --iAdam1n (talk) 22:33, 23 February 2016 (UTC)

KPP

Is there a reason why a KPP page has not been created? It would be useful to many... --Detiac 15:19, 9 October 2017 (UTC)

It would certainly be useful and something that should be on the wiki, but I don't think any active users are knowledgeable enough on the topic to provide a writeup. --Dialexio (talk) 02:23, 11 October 2017 (UTC)

Rename Bad Stuff section

I don't know what we could rename it to, but it doesn't come off very well --Nullpixel (talk) 17:26, 10 October 2017 (UTC)

Although the name is accurate, "Bad Stuff" does sound a little... off-kilter. Maybe something like "Malicious/Cautionary Topics?" --Dialexio (talk) 02:23, 11 October 2017 (UTC)
Sorry for the late response. I agree, this is a better name. --Nullpixel (talk) 16:10, 23 May 2018 (UTC)

Various Software

I feel like the Various Software section should either be segmented into smaller sections (Downgrading Utilities, Package Managers, etc.) or not exist at all -- and in the former case, would most likely not be under the section Various Software. Any thoughts? --wxblank (talk) 16:02, 21 June 2019 (UTC)

Firmware Status style.

I am proposing a change to the firmware status table, to pack-in more info into a smaller space while also being more future-proof.

i believe having the table in this style will improve not only the aesthetic of the table, but also be able to handle more devices in the future.

Exhibit A

This is what we have now:

Device Apple TV (4th generation) and newer Apple Watch Series 1 and newer HomePod iPad (5th generation) and newer
iPad Air 2
iPad mini 4
iPad Pro (12.9-inch, 9.7-inch, 12.9-inch 2nd generation, 10.5-inch)
iPhone 6s through iPhone X
iPod touch (7th generation)
iPad Air (3rd generation)
iPad mini (5th generation)
iPad Pro (11-inch, 12.9-inch 3rd generation)
iPhone XR and newer
Latest
Public Firmware
13.4.6 (17L570) 6.2.6 (17T620) 13.4.6 (17L570) 13.5.1 (17F80)
Jailbreak available? Yes
(checkra1n)[1][2]
No Yes
(checkra1n)
No
(N/A)
Latest
Beta Firmwares
13.4.8 beta 3 (17M5558b)
14.0 beta (18J5313t)
6.2.8 beta 3 (17U5559d)
7.0 beta (Series 3+) (18R5310a)
N/A 13.6 beta 3 (17G5059c)
14.0 beta (18A5301v)
  1. ^ Apple TV HD only but supports Apple TV 4K with hardware modfications
  2. ^ Check the "Allow untested iOS/iPadOS/tvOS versions" checkbox in the options view to bypass the version check.

Exhibit B

This is the style i propose we replace Exhibit A with:

Product Linup Apple TV HomePod Apple Watch iPhone iPad iPad Air iPad Pro iPad mini iPod touch
Supported Apple TV HD
and newer
Series 1
and newer
iPhone 6s
and newer
5th Generation
and newer
iPad Air 2
and newer
12.9-inch (2016)
and newer
iPad mini 4
and newer
7th Generation
Latest
Public Firmwares
13.4.6 (17L570) 6.2.6 (17T620) 13.5.1 (17F80)
Jailbreak availability Yes
(checkra1n)[1][2]
No Yes* (checkra1n)[1]
*except for devices with the A12 or newer SoC's.
Latest
Beta Firmwares
13.4.8 beta 3 (17M5558b) N/A 6.2.8 beta 3 (17U5559d) 13.6 beta 3 (17G5059c)
14.0 beta (18J5313t) N/A 7.0 beta (18R5310a)*
*Series 3 and newer only.
14.0 beta (18A5301v)
  1. ^ a b Check the "Allow untested iOS/iPadOS/tvOS versions" checkbox in the options view to bypass the version check.
  2. ^ Apple TV HD only, but can support the Apple TV 4K with some hardware modifications.

I am open to comments or suggestions - DanTheMann15 (talk) 23:11, 30 June 2020 (UTC)

I agree and prefer the new style. It sucks having devices listed twice but that would change once watchOS 7 is out of beta. Maybe though we could just add a note under the table that watchOS 7 beta’s require series 3 or newer and not have the second list. IMO that’d be better. —iAdam1n (talk) 00:16, 1 July 2020 (UTC)

That sounds like a good idea, and the note actually fits inside the table! i've changed Exhibit B to reflect this. - DanTheMann15 (talk) 01:13, 1 July 2020 (UTC)

I made the edit before seeing the talk page, oops. I'll leave it like that for now. Admanny (talk) 06:09, 1 July 2020 (UTC)

I like the "Jailbreak availability" text, but on the other hand though many people ask that question: is a "Jailbreak available?", i edited Exhibit B so everyone can see how it looks, get other opinions on it, but overall im down with either way. - DanTheMann15 (talk) 08:00, 1 July 2020 (UTC)

I think "available?" makes more sense to be honest with the yes and no answers. --iAdam1n (talk) 13:10, 1 July 2020 (UTC)
I changed it because it's unconventional for labels in a chart to be written in the form of a question. But, this is a small wiki anyway, so if the consensus sways towards keeping the question, that's fine. I'm still with keeping it as "availability". Admanny (talk) 19:55, 1 July 2020 (UTC)

Mac in the jailbreak table

Why is this in the table? Macs aren't exactly locked up in a BSD jail like iOS devices; they have security to prevent modifying system files by default, but Macs are a more open platform and SIP can be disabled to edit said files. You don't need to run some jailbreaking utility to e.g. change around some system icons in macOS. I presume the intent was to say bridgeOS on Macs with the T2 are susceptible to jailbreaking per the footnote, but the "Supported" row points to "All Macs with the M1". None of the M1 Macs have a T2 chip. The information provided is also for macOS, not bridgeOS. --Dialexio (talk) 08:24, 14 February 2021 (UTC)

That can be fixed but it was added as it's "firmware status" not just "jailbreak status" as should be there. --iAdam1n (talk) 11:40, 14 February 2021 (UTC)

HTTPS links on firmwares and OTA's that are hosted on "updates.cdn-apple.com"

I'm writing this topic because Dialexio hasn't been using https. https has been used here on the wiki regularly since 2019 when adding new firmware links that are hosted on Apple's CDN, which host's all of Apple's firmwares released since April 2018, such as iOS 11.3.1 and newer.

back when apple was still using appldnld.apple.com, adding https (https://secure-appldnld.apple.com) would make the links unreliable or not work at all.

but now with http://updates-http.cdn-apple.com, it works just fine to switch to (https://updates.cdn-apple.com).

it is easy as pie to switch the links to use https by using a good text-editing program that has a "find and replace" function. like Notepad++ or Gedit.


is there any good reason we shouldn't be using https on the newer firmwares hosted on Apple's CDN?

- DanTheMann15 (talk) 22:32, 5 May 2021 (UTC)

(This should probably be on The iPhone Wiki:Community portal instead, but oh well.) It kinda boils down to personal preference; to my understanding, there was never any sort of formal agreement on this. A user simply started converting some links to HTTPS, and I just let them do their thing since I do see benefits of using HTTPS. (At the end of the day though, you're still going to get the same file, especially if you verify its hash.) But personally, I'd rather keep the links the same way Apple provided them— if they gave us an HTTP link, that's what I'll add, and if they gave an HTTPS link, that's what I'll add. I'm not opposed to others changing the links I post to HTTPS as it's still Apple hosting and providing the download links, but I don't feel we should have to go out of our way to add one more step to an already tedious task. You can make an argument that it's for consistency, but that logic can also be used towards converting HTTPS links back to HTTP, and we would also trim the URLs for the older IPSWs so those look more consistent with newer, pre cdn-apple.com releases. --Dialexio (talk) 00:21, 6 May 2021 (UTC)

i understand where you are coming from, but i will continue to use https on the firmware links i post, since there are more advantages than the other way around, albeit the possible reason why apple gives us http links is likely because https requires valid certificates, which for some reason not everybody has. also it's important to note about HTTPS-Only on some major browsers so http links will not work for those who have that setting enabled. and like i said above, it takes me a fraction of a second to convert the links to https, thanks to Notepad++. perhaps you could add a setting that you can enable in the OTA Catalog Parser that would automatically convert links to https when parsing the links to save time. - DanTheMann15 (talk) 18:47, 16 May 2021 (UTC)

well i'll be darned, apple started providing https links for OTA downloads through pallas now! that'll save time on links going forward, i wonder if they'll do the same on IPSW's, only time will tell. - DanTheMann15 (talk) 21:27, 17 Jul 2021 (UTC)

Cleanup

Can we clean up the front page? It feels like there's an unnecessary amount of jargon that we can afford to simplify. I don't think we need to link to, e.g. the S5L8947 or the MDM9625 on the front page— the links to the Application Processor Baseband Device pages should be sufficient. (We can also probably remove the listing of each and every device under "Hardware" to further save space, but I can understand keeping those.) We also don't need to list every IMG3 or IMG4 tag. --Dialexio (talk) 16:29, 14 June 2021 (UTC)

Hey there Dialexio, yes i completely agree with cleaning up the front page, as it is full of repeated garbage. what we could do is consolidate the hardware links to the device lists, i'll make a concept on my Sandbox so i can fully show you what i mean. and yeah, we do not need to link the basebands and application processors in the front page, it'll be just fine contained in it's own page but have it's link on the main page be Bolded to make it easy enough to see. as for the stuff at the bottom of the page, i don't see any real need to change it, though i might see something that needs attention as i comb through it. but overall, after you see what i have in mind, you may make the changes as you wish upon the next beta day. - Cheers! --DanTheMann15 (talk) 06:27, 20 June 2021 (UTC)
I like the effort you made on your sandbox page! I hope you don't mind that I made a couple of additional edits that I think we can make, with some comments on why I thought the amendment was for the better. (If you don't like it, feel free to revert it and/or say something here.) --Dialexio (talk) 01:23, 28 June 2021 (UTC)
You have my approval on these changes, they look good, and the comments for anyone editing would be helpful to point them to the relevant page. once we are satisfied with the right Hardware side, we can turn on consolidating the left Software side so that the page is considerably shorter, as for the bottom of the page where Development and Help are, i don't see any immediate changes that i can suggest yet but if they come up i'll let you know, and feel free to make adjustments on the sandbox draft, it's what it's there for so we can see what the difference will look like. --DanTheMann15 (talk) 03:12, 28 June 2021 (UTC)

Eliminating the firmware key links on the device lists

I have a new change to propose,

Mind cutting the firmware key links from the device lists (e.g List of iPhones, iPads etc...) and replacing those links with a "See also" section at the bottom of the pages that has a link to Firmware Keys instead?

I feel it would look MUCH cleaner since it looks messy having it tell the same firmware version twice on devices that have two or more identifiers.

like the iPhone 5s here for example, which has two identifiers:

CURRENT SETUP

MY SUGGESTION

Firmwares:

  • Initial firmware: 7.0 (11A466)
  • Latest firmware: 12.5.5 (16H62)

====== See also ====== (AT BOTTOM OF THE PAGE)

Firmware Keys



Notes:

↓ we can also bold the versions and build numbers like this if we need to.

Firmwares:

  • Initial firmware: 7.0 (11A466)
  • Latest firmware: 12.5.5 (16H62)

let me know your thoughts, feedback is always good. --DanTheMann15 (talk) DanTheMann15 (talk) 07:52, 30 September 2021 (UTC)

I personally like the key page links as they are, but also see why it’d be cleaner. I suppose it would look better if it’s just one listing. —iAdam1n (talk) 11:31, 30 September 2021 (UTC)