− | A "ns_workaround" was [[5.1.0-11|added]] in NS to workaround the flaw added with [[5.0.0-11]]. When NS is loading before launching any ARM11 processes and certain [[Configuration Memory]] flags are set, NS will launch [[Application_Manager_Services|AM]] then use command [[AM:InstallNATIVEFIRM]]. NS will then use [[Process_Manager_Ports|PMApp]] command 0x0009XXXX, then "ptm:sysm" service command 0x04090080. | + | A "ns_workaround" was [[5.1.0-11|added]] in NS to workaround the flaw added with [[5.0.0-11]]. When NS is loading before launching any ARM11 processes and certain [[Configuration Memory]] fields are set, NS will launch [[Application_Manager_Services|AM]] then use command [[AM:InstallNATIVEFIRM]]. NS will then use command [[PMApp:SetFIRMLaunchParams]], then "ptm:sysm" service command 0x04090080. On retail this [[Configuration Memory]] fields check will pass every time. |
− | Therefore, with [[5.1.0-11]] every time the system boots when the [[Configuration Memory]] flags checked by NS are set, with the system will install [[FIRM]] from the CTR-NAND NATIVE_FIRM title to the FIRM NAND partitions. | + | Therefore, with [[5.1.0-11]] every time the system boots when the [[Configuration Memory]] flags checked by NS are set, the system will install [[FIRM]] from the CTR-NAND NATIVE_FIRM title to the FIRM NAND partitions. |