NS and APT Services: Difference between revisions
No edit summary  | 
				No edit summary  | 
				||
| Line 6: | Line 6: | ||
= Alternate menu =  | = Alternate menu =  | ||
When launching the regular menu fails, NS will then attempt to launch the alternate menu. This title could be used as a recovery process, however it's normally not used after the factory. This title is used at the factory for installing system titles, this title seems to be installed from a factory gamecard. This installer title likely deletes itself from NAND once it's finished installing titles.  | When launching the regular menu fails, NS will then attempt to launch the alternate menu. This title could be used as a recovery process, however it's normally not used after the factory. This title is used at the factory for installing system titles, this title seems to be installed from a factory gamecard. This installer title likely deletes itself from NAND once it's finished installing titles.  | ||
= NS Workaround =  | |||
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.  | |||
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.  | |||
= NS Service "ns:s" =  | = NS Service "ns:s" =  | ||