- Joined
- Jun 4, 2015
- Messages
- 1,441
- Trophies
- 1
- Location
- Minus World
- Website
- www.youtube.com
- XP
- 2,481
- Country
WHAT?!IIRC CTRAging may(?) factory reset the NAND once it's done. Make a backup
[frantically makes another NAND backup]
[frantically makes another NAND backup]
What qualifies as done? And well, no C-stick calibration then.IIRC CTRAging may(?) factory reset the NAND once it's done. Make a backup
EDIT: Only when not holding Start at launch, right?
Last edited by SomeGamer,
- Joined
- Jun 4, 2015
- Messages
- 1,441
- Trophies
- 1
- Location
- Minus World
- Website
- www.youtube.com
- XP
- 2,481
- Country
I found in the files the same instruction diagram is repeated several times, each is identical except for the depicted device (2DS, 3DS, N3DS, N3DS XL). The fact that it displayed the N3DS XL when I was testing the LED on a N3DS XL shows that the program is capable of detecting the current hardware model and behaving differently based on such. But oddly, I haven't found any tests specific to the N3DS hardware such as the extra buttons or the Super-Stable 3D sensor. The only thing was a pair of diagrams instructing the tester to cover and then release the SS3D sensor but I haven't found how to access that test through the menu yet.
But then again, the vast majority of menu items seem to crash the program. Maybe the additional tests are nested behind one of the broken menus?
But then again, the vast majority of menu items seem to crash the program. Maybe the additional tests are nested behind one of the broken menus?
Last edited by NekoMichi,
Rember that all the tests were planned to be made on factory titles/firmware, maybe using it on retail causes the crash.
- Joined
- Jun 4, 2015
- Messages
- 1,441
- Trophies
- 1
- Location
- Minus World
- Website
- www.youtube.com
- XP
- 2,481
- Country
That's possible. My build was from July 17th 2014, which was before the N3DS' release. Perhaps it's a combination of being run on a retail firmware and being an early build that it doesn't seem to run too well.
Interestingly enough, according to the production log my N3DS was first initialised in October 2014 (the fact that it came with System Menu 9.0.0 seems to support this date). I bought it brand new this year, so it must have been sitting on the shelf for more than a year untouched before it was powered on again since leaving the factory. Makes me a little sad.
On the plus side, it confirms that my model was a launch day unit. Not that it makes it any more special or anything...
Last edited by NekoMichi,
One of the menus let's you adjust the parameters of that test. I was able to make it run for less time before showing that pass screen.
Start Menu -> Checker Menu -> Change Configuration
The time limit is on Page 2 under 02-03 Aging Time and 02-04 Aging2 Time.
- Joined
- Jun 4, 2015
- Messages
- 1,441
- Trophies
- 1
- Location
- Minus World
- Website
- www.youtube.com
- XP
- 2,481
- Country
If anyone tried to launch CTR-AGING and got stuck at the "card wait" screen, try ejecting any game carts in slot 1. It seems the test was supposed to be run without anything in slot 1, so the error message is actually instructing the tester to check slot 1 for any devices. Without a cart in the slot, the program should launch to a black screen for about 10 seconds before starting the auto-test.
WARNING:
In the original NTR-AGING test for the DS, the program reset part of the NAND after testing completed without warning. I don't know if the CTR-AGING program also does this, so try auto-test at your own risk!
---
Among the romfs files I found a pair of images with Chinese labels. So now, it seems different parts of the program are in different languages: English, Japanese, and Chinese. My speculation is that the program serves as a universal test for factory units, units sent in for repair, and prototype units. One of the menus has options to switch testing between LINE (factory?), REPAIR, and some other modes. It's possible that in the factory the program was set to a specific mode that provided Chinese instructions to the factory employees (the 3DS appears to be assembled by Foxconn in China) while prototype units ran the same AGING test but in prototype mode which displayed Japanese instructions.
---
Some of the JPEG images from the romfs may have EXIF metadata still intact. Time for some deeper digging...
WARNING:
In the original NTR-AGING test for the DS, the program reset part of the NAND after testing completed without warning. I don't know if the CTR-AGING program also does this, so try auto-test at your own risk!
---
Among the romfs files I found a pair of images with Chinese labels. So now, it seems different parts of the program are in different languages: English, Japanese, and Chinese. My speculation is that the program serves as a universal test for factory units, units sent in for repair, and prototype units. One of the menus has options to switch testing between LINE (factory?), REPAIR, and some other modes. It's possible that in the factory the program was set to a specific mode that provided Chinese instructions to the factory employees (the 3DS appears to be assembled by Foxconn in China) while prototype units ran the same AGING test but in prototype mode which displayed Japanese instructions.
---
Some of the JPEG images from the romfs may have EXIF metadata still intact. Time for some deeper digging...
Last edited by NekoMichi,
This application is used to test & prepare 3ds units at the factory. Try using a blank sd card with it and you can go a couple steps further, but you won't still be able to complete it.
CTRAging doesn't simply format nand. It installs all the system titles (check the pre-title install log), then it deletes itself. If you are in DEBUG test mode, you can set CTRAging to not uninstall itself once it has ended
If you need to ask why you want to you don't need to.
ah nvm I think it's this thread that I'm after
https://gbatemp.net/threads/alternate-debug-test-menu-working-on-retail-3ds.428413/
https://gbatemp.net/threads/alternate-debug-test-menu-working-on-retail-3ds.428413/
There are stabilized 3D tests (in some 1st level submenu, QTM) but none of the 3 work...
I would guess it's the green "3D available" on the small O3DS, since that same test also supports controlling the not-anymore-existing camera light!
"Debug3" in the main menu tells you the brand of your screens, Sharp is TFT, the 3-letter brand is IPSWhere can you check out what screen you have?
The options directly below LogViewer replace your logs with customizable sample ones...
Was going through the menus, and noticed that there is an alarm under evaluation menu > mcu > show rtc. Not sure if there is a way to change that though...
Similar threads
-
- Article
-
The Real Jdbye
*is birb*
-
-
-
-
-
-
-
-
-
-
-
-
@
The Real Jdbye:
i have that stupid connector on my gpu luckily it's only a 300w gpu so i should(?) be fine since all the issues are with the quad 8pin->12pin and mine is only dual 8pin
-
-
-
@
The Real Jdbye:
quite a tight bend on that 8pin->12pin adapter in my case, which is the worst case scenario, but i made sure it was fully seated after plugging everything in and bending the cable so it shouldn't come unseated by itself since i pre-stressed the cable
-
-
-
-
-
@
The Real Jdbye:
@Psionic Roshambo i didn't go amd for one specific reason, the AI performance is way behind nvidia
-
-
@
The Real Jdbye:
oh yeah also DLSS is a pretty solid reason to go nvidia since fidelityfx is kinda crap
-
@
The Real Jdbye:
and now with the rtx video upscaling, and sdr->hdr conversion, even more reason to go nvidia
-
-
