Difference between revisions of "11.3.0-36"
(NS & GSP) |
m (Formatting) |
||
Line 13: | Line 13: | ||
Process9 now sets a global flag when starting applications (other than unique ID 0xF802A), and the firmlaunch function panics when attempting to launch SAFE_FIRM with if that flag has been set, to prevent safehax. | Process9 now sets a global flag when starting applications (other than unique ID 0xF802A), and the firmlaunch function panics when attempting to launch SAFE_FIRM with if that flag has been set, to prevent safehax. | ||
− | |||
===Modules=== | ===Modules=== | ||
− | No | + | No section0 module was changed. |
====NS==== | ====NS==== |
Revision as of 01:25, 7 February 2017
The Old3DS+New3DS 11.3.0-36 system update was released on February 6, 2017. This Old3DS update was released for the following regions: USA, EUR, JPN, CHN, KOR, and TWN. This New3DS update was released for the following regions: USA, EUR, JPN, CHN, KOR, and TWN.
Security flaws fixed: <fill this in manually later, see the updatedetails page from the ninupdates-report page(s) once available for now>.
Change-log
Official USA change-log:
- Further improvements to overall system stability and other minor adjustments have been made to enhance the user experience
System Titles
NATIVE_FIRM
Process9
Actual code changed in Process9 .text. 2 functions were updated, and 1 new function was added which is called by the first function(see below).
Process9 now sets a global flag when starting applications (other than unique ID 0xF802A), and the firmlaunch function panics when attempting to launch SAFE_FIRM with if that flag has been set, to prevent safehax.
Modules
No section0 module was changed.
NS
Only two constants were actually changed: the minimal value required for the kernel's minor version number (now 0x35, ie. 11.3 NFIRM, it used to be 0x23, ie. 5.0 NFIRM), and the version number used for FS:InitializeWithSdkVersion.
New_3DS GSP
At least the 3 following functions were updated (11.3 N3DS addresses):
- sub_102048: now writes 0 to LCD register 0x10202014 and ORs 0x1020200C with 0x10001
- sub_10B4F4
- sub_10B7DC
See Also
System update report(s):