Factory Setup - Revision history

Deadlock2896: /* CTRAging */

2024-05-28T14:57:31Z

CTRAging

← Older revision		Revision as of 18:57, 28 May 2024
Line 155:		Line 155:
	CTRAging appears to be a title used for hardware testing at the factory. This app also displays images, Chinese/Asian-language and text, both of which appear to be for system assembly/testing. CTRAging includes images for each 3DS model (which ones are included depends on the CTRAging version): original Old3DS, Old3DS XL, 2DS, regular New3DS, and New3DS XL. Some of the New3DS JPEG images have an EXIF last-modified timestamp of 2013, July-September.		CTRAging appears to be a title used for hardware testing at the factory. This app also displays images, Chinese/Asian-language and text, both of which appear to be for system assembly/testing. CTRAging includes images for each 3DS model (which ones are included depends on the CTRAging version): original Old3DS, Old3DS XL, 2DS, regular New3DS, and New3DS XL. Some of the New3DS JPEG images have an EXIF last-modified timestamp of 2013, July-September.

	Full dumps of CTRAging have only been possible on the N3DS. A menu can be pulled up by holding START. A video of the main testing routine is available at: https://www.youtube.com/watch?v=~~JsOhYqnW9Ww~~		Full dumps of CTRAging have only been possible on the N3DS. A menu can be pulled up by holding START. A video of the main testing routine is available at: https://www.youtube.com/watch?v=0nLiYZdn5Wg

	On O3DS, [[ExeFS]]:/.code is consistently corrupted. It is unknown whether this is coincidential or whether CTRAging is destroyed intentionally during any part of the factory setup.		On O3DS, [[ExeFS]]:/.code is consistently corrupted. It is unknown whether this is coincidential or whether CTRAging is destroyed intentionally during any part of the factory setup.

	The O3DS version has ''vastly'' more services access compared to the N3DS version.		The O3DS version has ''vastly'' more services access compared to the N3DS version.

Uyuiyu: Speculations (r)

2017-06-19T17:59:16Z

Speculations (r)

← Older revision		Revision as of 21:59, 19 June 2017
Line 3:		Line 3:
	[[Nandrw/sys/updater.log]], [[Twln/sys/log/inspect.log]] and [[Twln/sys/log/product.log]] get written during Factory Setup. CTRAging appears to do the product.log writing.		[[Nandrw/sys/updater.log]], [[Twln/sys/log/inspect.log]] and [[Twln/sys/log/product.log]] get written during Factory Setup. CTRAging appears to do the product.log writing.

	It is currently unknown how CTRAging is launched.		It is currently unknown how CTRAging is launched (Although they may use the ntrboot on the bootrom).

	== Titles ==		== Titles ==

Infinicore: /* CTRAging */ add PabloMK7's video

2016-07-03T10:07:50Z

CTRAging: add PabloMK7's video

← Older revision		Revision as of 14:07, 3 July 2016
Line 155:		Line 155:
	CTRAging appears to be a title used for hardware testing at the factory. This app also displays images, Chinese/Asian-language and text, both of which appear to be for system assembly/testing. CTRAging includes images for each 3DS model (which ones are included depends on the CTRAging version): original Old3DS, Old3DS XL, 2DS, regular New3DS, and New3DS XL. Some of the New3DS JPEG images have an EXIF last-modified timestamp of 2013, July-September.		CTRAging appears to be a title used for hardware testing at the factory. This app also displays images, Chinese/Asian-language and text, both of which appear to be for system assembly/testing. CTRAging includes images for each 3DS model (which ones are included depends on the CTRAging version): original Old3DS, Old3DS XL, 2DS, regular New3DS, and New3DS XL. Some of the New3DS JPEG images have an EXIF last-modified timestamp of 2013, July-September.

	Full dumps of CTRAging have only been possible on the N3DS.		Full dumps of CTRAging have only been possible on the N3DS. A menu can be pulled up by holding START. A video of the main testing routine is available at: https://www.youtube.com/watch?v=JsOhYqnW9Ww

	On O3DS, [[ExeFS]]:/.code is consistently corrupted. It is unknown whether this is coincidential or whether CTRAging is destroyed intentionally during any part of the factory setup.		On O3DS, [[ExeFS]]:/.code is consistently corrupted. It is unknown whether this is coincidential or whether CTRAging is destroyed intentionally during any part of the factory setup.

	The O3DS version has ''vastly'' more services access compared to the N3DS version.		The O3DS version has ''vastly'' more services access compared to the N3DS version.

Infinicore: revamp page

2016-07-03T10:06:32Z

revamp page

@@ Line 1: / Line 1: @@
-With certain 3DS nandimages, the following NCCH can be recovered from NAND(in some cases these are somewhat corrupted). In some cases, only 000400000F980000 is left, in other cases the NCCH headers for all of these are overwritten. ''All'' of these use the retail NCCH secure-crypto mode, the NCCH accessdesc uses the retail pubk too.
+== Setup Process ==
-Note that [[Nandrw/sys/updater.log]], [[Twln/sys/log/inspect.log]], and [[Twln/sys/log/product.log]] gets written during Factory Setup. CTRAging appears to do the product.log writing.
+[[Nandrw/sys/updater.log]], [[Twln/sys/log/inspect.log]] and [[Twln/sys/log/product.log]] get written during Factory Setup. CTRAging appears to do the product.log writing.
-CTRAging appears to be an app which is used for hardware testing at the factory. This app also displays images(including Chinese/Asian-language text) which appear to be for system assembly/testing. CTRAging includes images for each 3DS model(which ones are included depends on the CTRAging version): original Old3DS, Old3DS XL, 2DS, regular New3DS, and New3DS XL. Some of the New3DS JPEG images have an EXIF last-modified timestamp of 2013, July-September.
+It is currently unknown how CTRAging is launched.
-Originally these titles(except for CTRAging) and the exheader dependency lists had TID-high 00040001, later that was changed to the [[Title_list|normal]] TID-highs.
+== Titles ==
 {| class="wikitable" border="1"
@@ Line 115: / Line 129: @@
 | 00040001
 | 00008102
-| TestMenu
+| TestMenu (O3DS)
 |-
 | 00040001
@@ Line 123: / Line 137: @@
 | 00040030
 | 00008102
-| TestMenu
+| TestMenu (some O3DS (?), all N3DS)
 |-
 |}

Normmatt at 07:24, 2 April 2016

2016-04-02T05:24:40Z

← Older revision		Revision as of 09:24, 2 April 2016
Line 28:		Line 28:
	\| 00000202		\| 00000202
	\| AGB_FIRM		\| AGB_FIRM
			\|-
			\| 00040001
			\| 00001802
			\| codec sysmodule
	\|-		\|-
	\| 00040001		\| 00040001
	\| 00001902		\| 00001902
	\| dmnt (Debugger sysmodule, see [[Title_list\|here]])		\| dmnt sysmodule (Debugger sysmodule, see [[Title_list\|here]])
			\|-
			\| 00040001
			\| 00001A02
			\| dsp sysmodule
	\|-		\|-
	\| 00040001		\| 00040001
Line 55:		Line 63:
	\| 00040001		\| 00040001
	\| 00002302		\| 00002302
	\| ~~(unknown, likely~~ spi sysmodule)		\| spi sysmodule
	\|-		\|-
	\| 00040001		\| 00040001
Line 80:		Line 88:
	\| 00002D02		\| 00002D02
	\| nwm sysmodule		\| nwm sysmodule
			\|-
			\| 00040001
			\| 00002E02
			\| socket sysmodule
	\|-		\|-
	\| 00040001		\| 00040001

Infinicore: Going by the pattern of the other titles, 0004000100002302 is very likely spi

2015-06-28T15:08:44Z

Going by the pattern of the other titles, 0004000100002302 is very likely spi

← Older revision		Revision as of 19:08, 28 June 2015
Line 55:		Line 55:
	\| 00040001		\| 00040001
	\| 00002302		\| 00002302
	\|		\| (unknown, likely spi sysmodule)
	\|-		\|-
	\| 00040001		\| 00040001

Infinicore: nwm found

2015-06-28T14:49:10Z

nwm found

← Older revision		Revision as of 18:49, 28 June 2015
Line 79:		Line 79:
	\| 00040001		\| 00040001
	\| 00002D02		\| 00002D02
	\|		\| nwm sysmodule
	\|-		\|-
	\| 00040001		\| 00040001

Yellows8 at 19:47, 5 May 2015

2015-05-05T17:47:08Z

← Older revision		Revision as of 21:47, 5 May 2015
Line 3:		Line 3:
	Note that [[Nandrw/sys/updater.log]], [[Twln/sys/log/inspect.log]], and [[Twln/sys/log/product.log]] gets written during Factory Setup. CTRAging appears to do the product.log writing.		Note that [[Nandrw/sys/updater.log]], [[Twln/sys/log/inspect.log]], and [[Twln/sys/log/product.log]] gets written during Factory Setup. CTRAging appears to do the product.log writing.

	CTRAging appears to be an app which is used for hardware testing at the factory. This app also displays images(including Chinese/Asian-language text) which appear to be for system assembly/testing.		CTRAging appears to be an app which is used for hardware testing at the factory. This app also displays images(including Chinese/Asian-language text) which appear to be for system assembly/testing. CTRAging includes images for each 3DS model(which ones are included depends on the CTRAging version): original Old3DS, Old3DS XL, 2DS, regular New3DS, and New3DS XL. Some of the New3DS JPEG images have an EXIF last-modified timestamp of 2013, July-September.

	Originally these titles(except for CTRAging) and the exheader dependency lists had TID-high 00040001, later that was changed to the [[Title_list\|normal]] TID-highs.		Originally these titles(except for CTRAging) and the exheader dependency lists had TID-high 00040001, later that was changed to the [[Title_list\|normal]] TID-highs.

Yellows8 at 16:53, 4 April 2015

2015-04-04T14:53:25Z

← Older revision		Revision as of 18:53, 4 April 2015
Line 1:		Line 1:
	With certain 3DS nandimages, the following NCCH can be recovered from NAND(in some cases these are somewhat corrupted). In some cases, only 000400000F980000 is left, in other cases the NCCH headers for all of these are overwritten. ''All'' of these use the retail NCCH secure-crypto mode, the NCCH accessdesc uses the retail pubk too.		With certain 3DS nandimages, the following NCCH can be recovered from NAND(in some cases these are somewhat corrupted). In some cases, only 000400000F980000 is left, in other cases the NCCH headers for all of these are overwritten. ''All'' of these use the retail NCCH secure-crypto mode, the NCCH accessdesc uses the retail pubk too.

	Note that [[Nandrw/sys/updater.log]], [[Twln/sys/log/inspect.log]], and [[Twln/sys/log/product.log]] gets written during Factory Setup. CTRAging ~~probably does~~ the product.log writing.		Note that [[Nandrw/sys/updater.log]], [[Twln/sys/log/inspect.log]], and [[Twln/sys/log/product.log]] gets written during Factory Setup. CTRAging appears to do the product.log writing.

			CTRAging appears to be an app which is used for hardware testing at the factory. This app also displays images(including Chinese/Asian-language text) which appear to be for system assembly/testing.

			Originally these titles(except for CTRAging) and the exheader dependency lists had TID-high 00040001, later that was changed to the [[Title_list\|normal]] TID-highs.

	{\| class="wikitable" border="1"		{\| class="wikitable" border="1"

Normmatt at 10:58, 25 March 2015

2015-03-25T09:58:41Z

← Older revision		Revision as of 12:58, 25 March 2015
Line 97:		Line 97:
	\| [[NS]]		\| [[NS]]
	\|-		\|-
	\| ~~00040030~~		\| 00040001
	\| 00008102		\| 00008102
	\| TestMenu		\| TestMenu
Line 104:		Line 104:
	\| 00008A02		\| 00008A02
	\| [[ErrDisp\|DevErrDi]]		\| [[ErrDisp\|DevErrDi]]
			\|-
			\| 00040030
			\| 00008102
			\| TestMenu
	\|-		\|-
	\|}		\|}