Difference between revisions of "5.1.0-11"
Jump to navigation
Jump to search
| Line 3: | Line 3: | ||
=== System Modules === | === System Modules === | ||
| − | [[NS]] was updated. A "ns_workaround" was added in NS to workaround the above flaw added with [[5.0.0-11]]. When certain [[Configuration Memory]] flags are set, NS will launch [[Application_Manager_Services|AM]] then use "am:u" command 0x040F0000. NS will then use [[Process_Manager_Ports|PMApp]] command 0x0009XXXX, then "ptm:sysm" service command 0x04090080. | + | [[NS]] was updated. A "ns_workaround" was added in NS to workaround the above flaw added with [[5.0.0-11]]. When NS is loading and certain [[Configuration Memory]] flags are set, NS will launch [[Application_Manager_Services|AM]] then use "am:u" command 0x040F0000. NS will then use [[Process_Manager_Ports|PMApp]] command 0x0009XXXX, then "ptm:sysm" service command 0x04090080. |
===NATIVE_FIRM and other titles=== | ===NATIVE_FIRM and other titles=== | ||
[[FIRM|NATIVE_FIRM]] and [[CVer]] were updated. The NATIVE_FIRM changes were minor. | [[FIRM|NATIVE_FIRM]] and [[CVer]] were updated. The NATIVE_FIRM changes were minor. | ||
Revision as of 23:47, 11 April 2013
Official Changelog
- "Resolves an issue that may prevent access to the System Settings or other features after a system update error."
System Modules
NS was updated. A "ns_workaround" was added in NS to workaround the above flaw added with 5.0.0-11. When NS is loading and certain Configuration Memory flags are set, NS will launch AM then use "am:u" command 0x040F0000. NS will then use PMApp command 0x0009XXXX, then "ptm:sysm" service command 0x04090080.
NATIVE_FIRM and other titles
NATIVE_FIRM and CVer were updated. The NATIVE_FIRM changes were minor.