Homebrew [Request] CTRAging (3ds debug app) research.

[PabloMK7]

When I ran the script, nothing was generated. Only that error.
So do I need to change the first 4 bytes in the nand image or the xorpad?
Also, I'm not too sure if they are decrypted. I have only just dumped them using Decrypt9, then copied them straight to my PC. Does D9 automatically decrypt them?

It's not your fault, just the program. You will need to extract the fat16 partition using the old tool, and then run fffuck on it.
EDIT: Download the tool again, it should fix the problem.

 

[NekoMichi]

I ran the ctraging file from the Pastebin via DevMenu, but it still hangs on the SD Wait screen with the notification LED lit blue. Holding the Start button doesn't seem to have any effect.
Specs: N3DS XL Luma3DS 5.5/A9LH/11.0 sysNAND

 

[Deleted User]

It's not your fault, just the program. You will need to extract the fat16 partition using the old tool, and then run fffuck on it.
EDIT: Download the tool again, it should fix the problem.

Okay, so I ran the new tool, and got this:

dumping & decrypting NAND.fat16.bin
from nand.bin
using fat16.xorpad

Dump contains encrypted FAT16 partition. Please supply xorpad.
Usage: fffuck nand_image [xorpad]
xorpad is only optional if nand_image is already decrypted.
Press any key to continue . . .

Sorry, I probably am doing something wrong. >_<
Any suggestions? It's telling me to supply the xorpad, but the xorpad is inside the folder and is properly named...

 

[PabloMK7]

Okay, so I ran the new tool, and got this:

dumping & decrypting NAND.fat16.bin
from nand.bin
using fat16.xorpad

Dump contains encrypted FAT16 partition. Please supply xorpad.
Usage: fffuck nand_image [xorpad]
xorpad is only optional if nand_image is already decrypted.
Press any key to continue . . .

Sorry, I probably am doing something wrong. >_<
Any suggestions? It's telling me to supply the xorpad, but the xorpad is inside the folder and is properly named...

Open the nand.fat16.bin in HxDand replace the first 4 bytes with 0, then usinng command line run fffuck.exe nand.fat16.bin

I ran the ctraging file from the Pastebin via DevMenu, but it still hangs on the SD Wait screen with the notification LED lit blue. Holding the Start button doesn't seem to have any effect.
Specs: N3DS XL Luma3DS 5.5/A9LH/11.0 sysNAND

Strange... try holding START on boot.

 

[Khangaroo]

try holding START on boot.

I ran the ctraging file from the Pastebin via DevMenu, but it still hangs on the SD Wait screen with the notification LED lit blue. Holding the Start button doesn't seem to have any effect.
Specs: N3DS XL Luma3DS 5.5/A9LH/11.0 sysNAND

 

[Deleted User]

Open the nand.fat16.bin in HxDand replace the first 4 bytes with 0, then usinng command line run fffuck.exe nand.fat16.bin

C:\Users\Nathe\Downloads\fffuck>fffuck.exe nand.fat16.bin
Dump contains encrypted FAT16 partition. Please supply xorpad.
Usage: fffuck.exe nand_image [xorpad]
xorpad is only optional if nand_image is already decrypted.

This is just terrible! I keep getting the same error...
Also, is it normal that my nand.fat16.bin is 560MB?

EDIT: this is what I did with the nand.fat16.bin:

 

[NekoMichi]

Strange... try holding START on boot.

Strange... try holding START on boot.

Thanks, it seems I needed to hold down Start as soon as it's launched through DevMenu rather than after, otherwise it would attempt to auto-load some test but fail and get stuck. Now I can access the menu.

Edit: The test doesn't automatically reset the date and time, which is great (if I recall correctly, running the auto-test on the NTR Aging did automatically reset your personal settings without warning). Some tests seem to crash back to the Home Menu.

Edit 2: Under the "Key Test" menu, there was a "Wifi Button Test" option. It's weird, considering the N3DS doesn't have a hardware Wi-Fi toggle switch any more. Maybe a remnant from the O3DS testing?

 

[Khangaroo]

Thanks, it seems I needed to hold down Start as soon as it's launched through DevMenu rather than after, otherwise it would attempt to auto-load some test but fail and get stuck. Now I can access the menu.

Edit: The test doesn't automatically reset the date and time, which is great (if I recall correctly, running the auto-test on the DS Aging test did automatically reset your personal settings without warning). Some tests seem to crash back to the Home Menu.

Does a different dump work better?

 

[NekoMichi]

Does a different dump work better?

I haven't tried yet.

Also, here's an interesting tidbit under the debug menu:

The debug window outputs the LCD types. My model has an IPS upper display, could this be denoted as the 0x01 JDI type? Might be useful for identifying which models we have and diagnosing the scanline effect on some IPS units.

 

[OctopusRift]

I haven't tried yet.

Also, here's an interesting tidbit under the debug menu:

View attachment 51285​

The debug window outputs the LCD types. My model has an IPS upper display, could this be denoted as the 0x01 JDI type? Might be useful for identifying which models we have and diagnosing the scanline effect on some IPS units.

OOOH GOOD CATCH. IMMA CHECK.

 

[PabloMK7]

C:\Users\Nathe\Downloads\fffuck>fffuck.exe nand.fat16.bin
Dump contains encrypted FAT16 partition. Please supply xorpad.
Usage: fffuck.exe nand_image [xorpad]
xorpad is only optional if nand_image is already decrypted.

This is just terrible! I keep getting the same error...
Also, is it normal that my nand.fat16.bin is 560MB?

EDIT: this is what I did with the nand.fat16.bin:
View attachment 51284

You will have the search manually, then

 

[Deleted User]

You will have the search manually, then

Damn! >.>
I guess I can live with that...

Where do I start? Do I need to search for the titleID in the fat16 partition?

 

[Suiginou]

Also, is it normal that my nand.fat16.bin is 560MB?

No, it should be around 750MB.

 

[PabloMK7]

Edit 2: Under the "Key Test" menu, there was a "Wifi Button Test" option. It's weird, considering the N3DS doesn't have a hardware Wi-Fi toggle switch any more. Maybe a remnant from the O3DS testing?

There are also images in the romfs showing tests made to 2DSes and O3DSes. I still think there may be something somewhere that prevents it booting on O3DS

 

[Deleted User]

No, it should be around 750MB.

I just generated a nand.fat16.bin that is around 757MB; is that okay?

 

[PabloMK7]

Damn! >.>
I guess I can live with that...

Where do I start? Do I need to search for the titleID in the fat16 partition?

Search the TID in reverse.

 

[OctopusRift]

I haven't tried yet.

Also, here's an interesting tidbit under the debug menu:

View attachment 51285​

The debug window outputs the LCD types. My model has an IPS upper display, could this be denoted as the 0x01 JDI type? Might be useful for identifying which models we have and diagnosing the scanline effect on some IPS units.

I got. 0x0c (=SHARP) for both. JDI must be IPS.

 

[Suiginou]

There are also images in the romfs showing tests made to 2DSes and O3DSes. I still think there may be something somewhere that prevents it booting on O3DS

Likely. Note that N3DS CTRAging is -- if going only by the version in the ticket and TMD for it installed on the console -- a direct continuation of O3DS CTRAging development.

I just generated a nand.fat16.bin that is around 757MB; is that okay?

Yes, it is.

 

[Deleted User]

Ugh, I've had enough of this. I've either most likely screwed up right from the start, or I just don't have the ctr-aging in my fat16 partition (which is probably correct since my O3DS has gone through an update or two in the past...)
I sincerely hope someone manages to find an O3DS ctr-aging soon.

 

[Luigi64]

I got. 0x0c (=SHARP) for both. JDI must be IPS.

I have JDI too so watwas better JDI or SHARP?