|
The iPhone Wiki is no longer updated. Visit this article on The Apple Wiki for current information. |
Difference between revisions of "RecoveryMode"
(New page, like AppleLogo) |
m (small edit) |
||
| (4 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
| − | The '''RecoveryMode''' is located at <code>/Firmware/all_flash/all_flash.(MODEL-NAME).production/(RECOVERYMODE-IMG3-FILE-NAME).img3</code> in the [[IPSW File Format|IPSW]] |
+ | The '''RecoveryMode''' is located at <code>/Firmware/all_flash/all_flash.(MODEL-NAME).production/(RECOVERYMODE-IMG3-FILE-NAME).img3</code> in the [[IPSW File Format|IPSW]]. The RecoveryMode logo is flashed to [[NOR]] (or [[NAND|a functionally equivalent partition]]) and displayed when the device is in [[Recovery Mode]]. |
It is a PNG picture with an alpha channel packed into an [[IMG3 File Format|IMG3]] archive. |
It is a PNG picture with an alpha channel packed into an [[IMG3 File Format|IMG3]] archive. |
||
| − | Due to limited firmware storage space, any custom recovery mode logo must be exactly 320x480 |
+ | Due to limited firmware storage space, any custom recovery mode logo must be exactly 320x480 and under 100 KB. Custom Recovery Mode logos are not supported on devices not vulnerable to the [[0x24000 Segment Overflow]], [[Alloc8 Exploit]] or [[Pwnage 2.0]]. |
| − | |||
| − | |||
| − | <sup>1</sup>: Custom boot logos are not supported on devices not vulnerable to [[0x24000 Segment Overflow|24kpwn]] or [[Pwnage 2.0]]. |
||
Revision as of 14:55, 12 November 2020
The RecoveryMode is located at /Firmware/all_flash/all_flash.(MODEL-NAME).production/(RECOVERYMODE-IMG3-FILE-NAME).img3 in the IPSW. The RecoveryMode logo is flashed to NOR (or a functionally equivalent partition) and displayed when the device is in Recovery Mode.
It is a PNG picture with an alpha channel packed into an IMG3 archive.
Due to limited firmware storage space, any custom recovery mode logo must be exactly 320x480 and under 100 KB. Custom Recovery Mode logos are not supported on devices not vulnerable to the 0x24000 Segment Overflow, Alloc8 Exploit or Pwnage 2.0.
