The iPhone Wiki is no longer updated. Visit this article on The Apple Wiki for current information.

Difference between revisions of "Firmware Keys"

From The iPhone Wiki
Jump to: navigation, search
(New page: == Introduction == These keys are for use with the 'vfdecrypt' tool to decrypt the main filesystem dmg found in every iPhone/iPhone3G/iPod Touch .ipsw file. Every key will work on the main...)
 
(→‎Firmware Versions: 16.x placeholder)
 
(847 intermediate revisions by 59 users not shown)
Line 1: Line 1:
  +
__NOTOC__
−
== Introduction ==
  
  +
'''Firmware Keys''' are keys which decrypt bootloaders, ramdisks, and [[:/|root filesystem]] of iOS [[firmware]], if those components are encrypted. Apple uses encryption to make it harder to analyze and modify them. Over time Apple changed the way they encrypt firmware files, hence the way to decrypt them and get decryption keys changed as well.
−
These keys are for use with the 'vfdecrypt' tool to decrypt the main filesystem dmg found in every iPhone/iPhone3G/iPod Touch .ipsw file. Every key will work on the main filesystem dmg for that build, regardless if it is for the iPhone or iPod Touch. The dmg that you are after is the bigger one, in the case of current builds of 2.0, it can sometimes be 200mb+!
  
   
−
== VFDecrypt Usage ==
 +
== History ==
  +
With the release of the iPhone came the [[S5L File Formats#IMG2|IMG2]] file format. They were used on all known [[iOS|iPhone OS]] [[#1.x|1.x]] firmwares. For the 1.1.x series, they were encrypted with the [[AES Keys#Key 0x837|0x837 key]]. The discovery of the 0x837 key led to the ability to decrypt ''any'' 1.x firmware.
−
./vfdecrypt -i <dmg> -o decrypted_fs.dmg -k <key>
  
   
  +
Following IMG2 came the [[IMG3 File Format|IMG3]] file format. They were introduced with iPhone OS [[#1.x.2F2.x|2.0 beta 4]], and have been in use ever since. In order to maintain their integrity, they use multiple layers of encryption. Apple took encryption seriously with IMG3 by utilizing [[wikipedia:Advanced Encryption Standard|AES]] (based on the [[wikipedia:Rijndael key schedule|Rinjndael key schedule]]). In terms of the pre-iPhone OS 3 [[VFDecrypt]] key, it is stored as plain-text in the "__restore" segment of the ASR image within the [[ramdisk]]s.
−
== Gaps ==
  
−
As you will notice, there may be a gap or two, or a key for a current build that is not there. Please feel free to add them, but please be sure that it is only the key for a User or Developer build, as if you gave the key for another type of build that might or may not be out there **people could gt in trouble, and we do not want that**. Thanks for contributing!
  
   
  +
The ramdisk keys can ''only'' be retrieved with the processor specific [[GID Key]]. The GID key is currently unretrievable and can only be utilized through the built-in [[AES Keys|AES engine]]. To complicate things ''even more'', the engine is only accessible through a special [[bootrom]] or [[iBoot]] exploit ([[jailbreak]]s typically expose it with [[/dev/aes_0]]). This makes usage of the key nearly impossible.
−
== Downloads ==
  
−
[[http://chronic-dev.org/tools/vfdecrypt Download VFDecrypt]]
  
   
  +
However, once you have access to the AES engine, the entire system falls apart. You are able to upload an encrypted ramdisk and grab the decryption keys for it. Once you manage to decrypt the ramdisk, you can run it through [[GenPass]] to decrypt the firmware key.
−
== 1.2 (Beta 1) (Build 5A147p) ==
  
−
86bec353ddfbe3fb750e9d7905801f79791e69acf65d16930d288e697644c76f16c4f16d
  
   
  +
To find the keys, you can either use the methods on [[AES Keys]] or the easier option for OS X, [[keylimepie]].
−
== 2.0 (Beta 2) (Build 5A225c) ==
  
−
ea14f3ec624c7fdbd52e108aa92d13b16f6b0b940c841f7bbc7792099dae45da928d13e7
  
   
  +
== Decrypting ==
−
== 2.0 (Beta 3) (Build 5A240d) ==
  
  +
{{main|Decrypting Firmwares}}
−
e24bfab40a2e5d3dc25e089291846e5615b640897ae8b424946c587bcf53b201a1041d36
  
  +
== Notes ==
  +
Certain files share the same key and IV per [[Application Processor|application processor]] (per build) provided the devices have the same pixel resolution:
  +
* [[Update Ramdisk]]
  +
* [[Restore Ramdisk]]
  +
* [[AppleLogo]]
  +
* [[BatteryCharging0]]
  +
* [[BatteryCharging1]]
  +
* [[BatteryFull]]
  +
* [[BatteryLow0]]
  +
* [[BatteryLow1]]
  +
* [[GlyphCharging]]
  +
* [[GlyphPlugin]]
  +
* [[Kernelcache]]
  +
* [[NeedService]]
  +
* [[RecoveryMode]]
  +
* [[SEP Firmware]]
  +
* [[WTF]]
   
  +
You can use [[img3decrypt]] or [[xpwntool]] to decrypt these files as described in [[Decrypting Firmwares]]. Once done, mount or extract using the tool of your choice.
−
== 2.0 (Beta 5) (Build 5a274d) ==
  
−
589df25eaa4ff0a5e29e1425fb99bf50957888ff098ba2fcb72cf130f40e15e00bcf2fc7
  
   
  +
The firmware version number for the [[List of Apple TVs|Apple TV]] builds are the ones that the Apple TV reports (also known as the "marketing version").
−
== 2.0 (Beta 6 Pre-Release) (Build 5a292g) ==
  
−
890b1fbf22975e0d4be2ea3f9bc5c87f38fd8158394fd31cf80a43ad25547573bbd0ec4e
  
   
  +
All dates are relative to [[wikipedia:Coordinated Universal Time|UTC]].
−
== 2.0 (Beta 6 Final) (Build 5a308) ==
  
−
3964ca8d8bf5d3715cdc172986f2d9606672c54d5e0aa3f3a892166b4e54e4cefef21279
  
   
  +
GID AES is used by iBoot to decrypt firmware images. When iBoot loads the kernelcache, GID AES is disabled. This means in order to get firmware keys, you must gain code execution in a setting where GID AES is still enabled. In most cases, this means exploiting iBoot itself, before the kernelcache is loaded.
−
== 2.0 (Beta 7) (Build 5a331) ==
  
−
3d9a9832a108fc5084fc9329d6e84e38edf06e380554c49376b70e951f8a8d1ed943f819
  
   
  +
==Firmware Versions==
−
== 2.0 (Build 5a347) ==
  
  +
{{see also|Prototypes}}
−
2cfca55aabb22fde7746e6a034f738b7795458be9902726002a8341995558990f41e3755
  
  +
This is a full and comprehensive list of all firmwares Apple Inc. has made available to the public in some way, be it the [[Apple Developer|dev center]] or [[iTunes]]. This list also contains a few firmwares for which there never was an IPSW (as far as can be told) such as 4.2.5 for the [[N92AP|CDMA iPhone 4]] (iPhone3,3). These few builds came preinstalled on the device, but are not available for download.
  +
  +
* [[Firmware Keys/1.x|1.x]]
  +
* [[Firmware Keys/2.x|2.x]]
  +
* [[Firmware Keys/3.x|3.x]]
  +
* [[Firmware Keys/4.x|4.x]]
  +
* [[Firmware Keys/5.x|5.x]]
  +
* [[Firmware Keys/6.x|6.x]]
  +
* [[Firmware Keys/7.x|7.x]]
  +
* [[Firmware Keys/8.x|8.x]]
  +
* [[Firmware Keys/9.x|9.x]]
  +
* [[Firmware Keys/10.x|10.x]]
  +
* [[Firmware Keys/11.x|11.x]]
  +
* [[Firmware Keys/12.x|12.x]]
  +
* [[Firmware Keys/13.x|13.x]]
  +
* [[Firmware Keys/14.x|14.x]]
  +
* [[Firmware Keys/15.x|15.x]]
  +
* [[Firmware Keys/16.x|16.x]]
  +
  +
== See also ==
  +
* [[Application Processor]]
  +
  +
[[Category:Decryption]]

Latest revision as of 10:42, 6 June 2022

Firmware Keys are keys which decrypt bootloaders, ramdisks, and root filesystem of iOS firmware, if those components are encrypted. Apple uses encryption to make it harder to analyze and modify them. Over time Apple changed the way they encrypt firmware files, hence the way to decrypt them and get decryption keys changed as well.

History

With the release of the iPhone came the IMG2 file format. They were used on all known iPhone OS 1.x firmwares. For the 1.1.x series, they were encrypted with the 0x837 key. The discovery of the 0x837 key led to the ability to decrypt any 1.x firmware.

Following IMG2 came the IMG3 file format. They were introduced with iPhone OS 2.0 beta 4, and have been in use ever since. In order to maintain their integrity, they use multiple layers of encryption. Apple took encryption seriously with IMG3 by utilizing AES (based on the Rinjndael key schedule). In terms of the pre-iPhone OS 3 VFDecrypt key, it is stored as plain-text in the "__restore" segment of the ASR image within the ramdisks.

The ramdisk keys can only be retrieved with the processor specific GID Key. The GID key is currently unretrievable and can only be utilized through the built-in AES engine. To complicate things even more, the engine is only accessible through a special bootrom or iBoot exploit (jailbreaks typically expose it with /dev/aes_0). This makes usage of the key nearly impossible.

However, once you have access to the AES engine, the entire system falls apart. You are able to upload an encrypted ramdisk and grab the decryption keys for it. Once you manage to decrypt the ramdisk, you can run it through GenPass to decrypt the firmware key.

To find the keys, you can either use the methods on AES Keys or the easier option for OS X, keylimepie.

Decrypting

Main article: Decrypting Firmwares

Notes

Certain files share the same key and IV per application processor (per build) provided the devices have the same pixel resolution:

You can use img3decrypt or xpwntool to decrypt these files as described in Decrypting Firmwares. Once done, mount or extract using the tool of your choice.

The firmware version number for the Apple TV builds are the ones that the Apple TV reports (also known as the "marketing version").

All dates are relative to UTC.

GID AES is used by iBoot to decrypt firmware images. When iBoot loads the kernelcache, GID AES is disabled. This means in order to get firmware keys, you must gain code execution in a setting where GID AES is still enabled. In most cases, this means exploiting iBoot itself, before the kernelcache is loaded.

Firmware Versions

See also: Prototypes

This is a full and comprehensive list of all firmwares Apple Inc. has made available to the public in some way, be it the dev center or iTunes. This list also contains a few firmwares for which there never was an IPSW (as far as can be told) such as 4.2.5 for the CDMA iPhone 4 (iPhone3,3). These few builds came preinstalled on the device, but are not available for download.

See also

Retrieved from "https://www.theiphonewiki.com/w/index.php?title=Firmware_Keys&oldid=122962"