9.5.0-22: Difference between revisions
Jump to navigation
Jump to search
Created page with "The 9.5.0-22 system update was released on February 2, 2015. == Change-log == [http://en-americas-support.nintendo.com/app/answers/detail/a_id/231 Official] change-log: * Furthe..." |
|||
| Line 9: | Line 9: | ||
===NATIVE_FIRM=== | ===NATIVE_FIRM=== | ||
In Process9 only *one* u32 was changed: the address of the FIRM header used during FIRM launch. This fixes [[3DS_System_Flaws|firmlaunch-hax]]. | In Process9 only *one* u32 was changed: the address of the FIRM header used during FIRM launch. This fixes [[3DS_System_Flaws|firmlaunch-hax]]. | ||
===New3DS NATIVE_FIRM=== | |||
The ARM9-loader has added a new keyX with keyslot 0x16 that is generated on hard-boot. The ARM9 binary is now encrypted with this key. In order to decrypt it, you'll need arm9hax on firm > 9.4, or some form of bootromhax. | |||
=See Also= | =See Also= | ||
System update reports: <add later> | System update reports: <add later> | ||
Revision as of 04:01, 3 February 2015
The 9.5.0-22 system update was released on February 2, 2015.
Change-log
Official change-log:
- Further improvements to overall system stability and other minor adjustments have been made to enhance the user experience.
System Titles
NATIVE_FIRM
In Process9 only *one* u32 was changed: the address of the FIRM header used during FIRM launch. This fixes firmlaunch-hax.
New3DS NATIVE_FIRM
The ARM9-loader has added a new keyX with keyslot 0x16 that is generated on hard-boot. The ARM9 binary is now encrypted with this key. In order to decrypt it, you'll need arm9hax on firm > 9.4, or some form of bootromhax.
See Also
System update reports: <add later>