Homebrew DS(i) NOOB PARADISE - Ask questions here

[Kwyjor]

apps not opening via hbmenu. switch v1 20.1.1/ AMS 1.10.2/S

I don't think you're posting in the right thread.

 

[kyrusdemnati]

mig switch on siwtch 2 in eu
can you update games via nintendo if needed and also if i get botw/totk on mig can i pay for the switch 2 version via e shop? and will it work

 

[Kwyjor]

mig switch on siwtch 2 in eu
can you update games via nintendo if needed and also if i get botw/totk on mig can i pay for the switch 2 version via e shop? and will it work

Sir, you are posting in a thread about the Nintendo DS(i). If you have questions about the Switch, you should direct them elsewhere.

 

[KIlly728]

I have 3 DSi XL Motherboards with a similar issue. There is one exception, but I'll get to that later.

All three Japanese motherboards came to me Unlaunched with some English language patcher on them (They have 2 or 3 LAUNCHERS with one in English and one in Japanese). There are no NAND backups before the modding, as I got these as junk consoles.

When I try booting into the launchers, either of the two Launchers, they spit out "An error has occurred".

All consoles boot into Unlaunch and run applications without any issues, but they do not run their respective LAUNCHERS. Except for one motherboard, I cannot access the DSi vanilla menu, but I can enter the settings, Camera, SafeNAND manager, things of that sort.

The odd motherboard out has 3 LAUNCHERS, and I'm able to boot into one of the Japanese LAUNCHERS just fine (it may be the vanilla menu that wasn't added with a language patcher). The other two LAUNCHERS spit out the same error mentioned above.

I have the NAND dumps of the three consoles, but I am unable to attach them since they are too big.

I tried reinstalling UNLAUNCH and the DSi Language Patcher, but there was no change. On one of the motherboards, I reflowed the NAND and Wifi card plug, but there was no change.

What are my next steps?

If there is any information in the NAND dumps, which I suspect tells the whole story, I would be grateful to know how you found this out (What programs you used, what you were looking for, etc). I would like to have this troubleshooting method in my toolbelt.

 

[Flame]

mig switch on siwtch 2 in eu
can you update games via nintendo if needed and also if i get botw/totk on mig can i pay for the switch 2 version via e shop? and will it work

Post in the correct thread, please. You are more likely to get an answer.

 

[k66]

I have 3 DSi XL Motherboards with a similar issue. There is one exception, but I'll get to that later.

All three Japanese motherboards came to me Unlaunched with some English language patcher on them (They have 2 or 3 LAUNCHERS with one in English and one in Japanese). There are no NAND backups before the modding, as I got these as junk consoles.

When I try booting into the launchers, either of the two Launchers, they spit out "An error has occurred".

All consoles boot into Unlaunch and run applications without any issues, but they do not run their respective LAUNCHERS. Except for one motherboard, I cannot access the DSi vanilla menu, but I can enter the settings, Camera, SafeNAND manager, things of that sort.

The odd motherboard out has 3 LAUNCHERS, and I'm able to boot into one of the Japanese LAUNCHERS just fine (it may be the vanilla menu that wasn't added with a language patcher). The other two LAUNCHERS spit out the same error mentioned above.

I have the NAND dumps of the three consoles, but I am unable to attach them since they are too big.

I tried reinstalling UNLAUNCH and the DSi Language Patcher, but there was no change. On one of the motherboards, I reflowed the NAND and Wifi card plug, but there was no change.

What are my next steps?

If there is any information in the NAND dumps, which I suspect tells the whole story, I would be grateful to know how you found this out (What programs you used, what you were looking for, etc). I would like to have this troubleshooting method in my toolbelt.

I tried the DSi Language Patcher, it only adds one file (NAND:/launcher.dsi) and does not change anything else.

------------------
Restore NAND backup.
- If you have previously backed up the NAND, use safenandmanager to restore the NAND.

------------------
Situation of Launcher's title.tmd (Unlaunch) is corrupted:
This might be caused by a problem that occurred while installing/uninstalling Unlaunch.
Unlaunch may not work properly on DSi v1.4.2.

- Reinstall Unlaunch (Original Unlaunch)
DSi Unlaunch → TWiLightMenu++(Launcher Patchets: Default or Full) → install Unlaunch
If Launcher Patches: Off, it may cause the original system Launcher* to "An error has occurred".
*If the original system Launcher is v1024 (DSi system version 1.4.2J/U/E, 1.4.3C).
(If installing Unlaunch gives a 'mismatch in FAT copies' error, use any exploit to launch TWiLightMenu++, open NTM to 'Fix FAT copy mismatch'.)

- Or install 'safe' Unlaunch

If unable to install Unlaunch, or you unclear whether the TMD file is intact, it is recommended:
- Reinstall the Launcher using TDT, which will reinstall all Launcher files including title.tmd.
see "Situation of the Launcher problem"

------------------
Situation of the overflow title:
It might be that the user updated DSi system while using language patch(launcher.dsi), and the system update installed new(other region) Launcher and apps, this may caused all titles(apps) to exceed 39.
If the installed titles exceed 39, it will cause a DSi startup "An error has occurred".

1.Backup NAND first.
1a.Unlaunch → safenandmanager, dump NAND.
1b.ntrboot(godmode9i) → safenandmanager, dump NAND.
2.Delete dsiware.
2a.DSi Unlaunch → NTM/TDT → SysNAND → Titles → select dsiware → Backup(to SD card) → Delete.
2b.DSi ntrboot(godmode9i) → TDT → SysNAND → Titles → select dsiware → Backup(to SD card) → Delete.
2c.Edit NAND, manually delete the NAND:/title/00030004/ all folders (dsiware is here, backup before deleting), then Restore NAND.

------------------
Situation of the Launcher problem:
DSi Language Patcher: NAND:/launcher.dsi
Factory Launcher:NAND:/title/00030017/484e4141/, there generally won't be any app files in here. ('safe' Unlaunch tmd is here.)
DSi Launcher:NAND:/title/00030017/484e41**/content/0000000X.app, **=region code. (Original Unlaunch tmd is here.)
00000000.app=v0 (DSi ver 1.0 & 1.1)
00000001.app=v256 (DSi ver 1.2 & 1.3)
00000002.app=v512 (DSi ver 1.4)
00000003.app=v768 (DSi ver 1.4.1)
00000004.app=v1024 (DSi ver 1.4.2)
00000005.app=v1280 (DSi ver 1.4.3)
00000006.app=v1536 (DSi ver 1.4.4)
00000007.app=v1792 (DSi ver 1.4.5)

iQue and Korea DSi Launcher:
00000000.app=v512 (DSi ver 1.4 & 1.4.1)
00000001.app=v768 (DSi ver 1.4.2)
00000002.app=v1024 (DSi ver 1.4.3)
00000003.app=v1280 (DSi ver 1.4.4)
00000004.app=v1536 (DSi ver 1.4.5)
00000005.app=v1792 (DSi ver 1.4.6)

You can open NAND:/sys/HWINFO_S.dat with a Hex editor to view the DSi serial number.
e.g. TW123456784, W=USA, Original region Launcher folder: NAND:/title/00030017/484e4145/
region code: region suffix
4a/J = Japan: J
4b/K = Korea: K
43/C = China: C
45/E = USA: W
50/P = Europe: E
55/U = Australia: A
41/A = All regions
45/E, Southeast Asia: S
45/E, Nintendo Zone Box: ZS
.
- Reinstall the Launcher using TDT
Do not attempt if you do not have an ntrboot cart.
(The prerequisite is that the DSi's hardware is functioning properly.)
1.Backup NAND first.
1a.Unlaunch → safenandmanager, dump NAND.
1b.ntrboot(godmode9i) → safenandmanager, dump NAND.
(Copy the NAND backup file of the SD card to your computer for safekeeping, in case the second backup overwrites it.)
2.Reinstall the Original region Launcher on the DSi using TDT's SysNAND mode.
2a.Unlaunch → TDT → SysNAND → Install → select tad file → Install.
2b.ntrboot(godmode9i) → TDT → SysNAND → Install → select tad file → Install.
(This will delete Original region Launcher's Unlaunch(Original Unlaunch, not 'safe' Unlaunch). )
(If the 'safe' Unlaunch is installed, it will also cause it to stop working.)
(Launchers and apps from other regions and language patch(launcher.dsi) are still in the NAND.)
(You can find files on @rvtr's website. Or search for 'DSi Firmware Versions'.)
Restart the DSi, it should start up normally, and apps from other regions will disappear.

------------------
Delete Launcher and apps from other regions:
(If you want to delete the Launcher and apps from other regions, please refer to 'Situation of the Launcher problem' to tell them apart.)
Backup NAND first.
a.DSi Unlaunch → NTM/TDT → SysNAND → Titles → select (Launcher and apps from other regions) → Backup(to SD card) → Delete.
b.DSi ntrboot(godmode9i) → TDT → SysNAND → Titles → select (Launcher and apps from other regions) → Backup(to SD card) → Delete.
c.Edit NAND, manually delete the NAND:/title/(Launcher and apps from other regions)folders, then Restore NAND.

Delete DSi Language Patcher: NAND:/launcher.dsi

------------------
If you encounter any problems:
- Use ntrboot cart to boot GodMode9i, then start SafeNANDManage to restore NAND backup.

 

[KIlly728]

I greatly appreciate the reply. I will have to read this a few times and give it a shot when I finish this New 3DS I am working on.

You can open NAND:/sys/HWINFO_S.dat with a Hex editor to view the DSi serial number.

4.Edit NAND, manually delete the Launcher and apps from other regions.

How do I navigate through and edit the NAND files? Is there a PC program to unpack and repack the NAND bin file?

 

[k66]

How do I navigate through and edit the NAND files? Is there a PC program to unpack and repack the NAND bin file?

You can refer to this, it mentions how to mount NAND.

 

[rvtr]

You can open NAND:/sys/HWINFO_S.dat with a Hex editor to view the DSi serial number.
e.g. TW123456784, W=USA, Original region Launcher folder: NAND:/title/00030017/484e4145/
region code: region suffix
4a/J = Japan: J
4b/K = Korea: K
43/C = China: C
45/E = USA: W
50/P = Europe: E
55/U = Australia: A
41/A = All regions

There's another! A serial with the second character as "S" will be southeast asia. ASI models are running USA firmware, but this may be confusing if you do not know.

There may also be a UAE specific serial? Not sure though as I haven't been able to confirm.

I keep a list of known serial values here:
https://wiki.raregamingdump.ca/index.php/DSi_Serial_Numbers

 

[KIlly728]

@k66

I began looking into it with one of my motherboards and ran into some issues.

When looking at HWINFO_S.dat I didn't find anything related to a DSi Serial Number using a "TW123456784" character system. I did, however, see the shell/house serial number. Was that what you meant?

I didn't know the shell/housing serial number was embedded into the NAND, so that is neat to see.

I can confirm that the shell/housing serial number matches the shell/housing the motherboard came from. In this case, it is a Japanese region DSi LL console.

Looking at the launcher file in Unlaunch, it was the 484e414a/content/00000004.app file, the console is running version 1.4.2J firmware listed on @rvtr's website. I can still open up the settings menu on this DSi motherboard, and it did say it is running that version.

After getting TAD Delivery Tool, and the Launcher_HNAJ_v1024.tad file over to the SD card, I tried to install the Launcher onto the sysNAND only to be met with an error saying "This title cannot be installed to the SysNAND". I don't know if it's because it cannot override an existing file, I am trying to install the wrong file, or something else.

I installed the Launcher onto my SD, and I was able to boot off of it (which I didn't know you could do), but it spat out "An error has occurred" in Japanese. I don't know if I was actually booting off of my SD card, or if it just defaulted back to the SysNAND.

I manually dragged the files that the TAD Delivery Tool created on my SD card and pasted them into the NAND, overriding the files, which I had mounted via ninfs and OSFMount, and restored the NAND on the motherboard. No luck as it still boots into "An error has occurred" in Japanese.

Am I missing something here?

 

[k66]

@k66

I began looking into it with one of my motherboards and ran into some issues.

When looking at HWINFO_S.dat I didn't find anything related to a DSi Serial Number using a "TW123456784" character system. I did, however, see the shell/house serial number. Was that what you meant?

I didn't know the shell/housing serial number was embedded into the NAND, so that is neat to see.

View attachment 560302

I can confirm that the shell/housing serial number matches the shell/housing the motherboard came from. In this case, it is a Japanese region DSi LL console.

Looking at the launcher file in Unlaunch, it was the 484e414a/content/00000004.app file, the console is running version 1.4.2J firmware listed on @rvtr's website. I can still open up the settings menu on this DSi motherboard, and it did say it is running that version.

After getting TAD Delivery Tool, and the Launcher_HNAJ_v1024.tad file over to the SD card, I tried to install the Launcher onto the sysNAND only to be met with an error saying "This title cannot be installed to the SysNAND". I don't know if it's because it cannot override an existing file, I am trying to install the wrong file, or something else.

View attachment 560303

I installed the Launcher onto my SD, and I was able to boot off of it (which I didn't know you could do), but it spat out "An error has occurred" in Japanese. I don't know if I was actually booting off of my SD card, or if it just defaulted back to the SysNAND.

I manually dragged the files that the TAD Delivery Tool created on my SD card and pasted them into the NAND, overriding the files, which I had mounted via ninfs and OSFMount, and restored the NAND on the motherboard. No luck as it still boots into "An error has occurred" in Japanese.

Am I missing something here?

TW123456784 is just an example.

Your operation is correct.
You can try using the TDT from the #6 of that post.
.
.
I just remembered, It may not be a problem with the Launcher.
If the installed titles exceed 39, it will cause a DSi startup "An error has occurred".
Due to user updated DSi system while using language patch(launcher.dsi), and the system update installed new(other region) Launcher and apps, caused all titles to exceed 39.

You can check NAND:/title/00030004/(dsiware is here), how many folders are inside? Try deleting all the folders in 00030004. Then just restore the NAND.
(If Unlaunch can be used, use NTM to delete all dsiware from the SysNAND.)
I updated #1686

 

[rvtr]

If there is a change needed for TDT, let me know. I know that the github releases are a bit behind.
I was waiting to push a new release until I could clean up the code... about a year and a half ago lmao

 

[KIlly728]

You can check NAND:/title/00030004/(dsiware is here), how many folders are inside? Try deleting all the folders in 00030004. Then just restore the NAND.

There were only 6 folders in that file directory, so I don't expect that to be the issue. I deleted them to see what happens.

Your operation is correct.
You can try using the TDT from the #6 of that post.

After restoring the NAND (the NAND that I cleared out the NAND:/title/00030004/ file)and using that updated TDT to install the correct launcher (it succeeded this time), I booted into the vanilla DSi menu. Success!!

I'll have to spend some time tomorrow cleaning out the NAND.

Thank you, I appreciate the help.

 

[k66]

There were only 6 folders in that file directory, so I don't expect that to be the issue. I deleted them to see what happens.

This is really a strange malfunction...I don't know what caused the Launcher malfunction.

00030017/484e41** System Menu (Launcher) may repeat

00030015/484e42** System Settings may repeat
00030015/484e46** DSi Shop may repeat
00030015/484e4f** Nintendo 3DS Transfer Tool

0003000f/484e4341 WiFi Firmware
0003000f/484e4841 Nintendo DS Cart Whitelist
0003000f/484e4c** Version Data may repeat

00030005/484e4441 DS Download Play
00030005/484e4541 Pictochat
00030005/484e49** DSi Camera may repeat
00030005/484e4a** Nintendo Zone may repeat
00030005/484e4b** DSi Sound may repeat

00030004/484e47** DSi Browser Pre-installed, will not update?
00030004/4b4755** Flipnote Studio Pre-installed, will not update?
00030004/4b3244** DSi + Internet Pre-installed, will not update?

If there are 3 Launchers(launcher.dsi + 2app) displayed in Unlaunch, it means it has been system updated once.
00030017: 2 app
00030015: 5 app
0003000f: 4 app
00030005: 8 app
00030004: 3+? , 6 app
2+5+4+8+6=25 app (titles)
.
.
It might be a bug in Language Patcher...
.
@KIlly728 Can you upload the contents of the 00030017 folder in the original NAND ?
(compressed as 00030017.zip , and upload attachment)

 

[KIlly728]

@KIlly728 Can you upload the contents of the 00030017 folder in the original NAND ?
(compressed as 00030017.zip , and upload attachment)

Here it is. This is the NAND backup that was made before I reinstalled the launcher. I would be very curious to know what you find out. If you need any more files from that NAND, let me know.

Post automatically merged: Mar 7, 2026

I'll have to spend some time tomorrow cleaning out the NAND.

I tinkered with this console a little more, and there were some weird things about it.

3.Backup NAND.
4.Edit NAND, manually delete the Launcher and apps from other regions.
(They are in the NAND:/title/ folders.)

I was on this step, and what stuck me immediately was that whatever ID the console tied to the NAND backup was now completely blank or defaulted to this DT0000000000000000 string. The file above is the NAND backup on the repaired console, and below was the one I originally pulled from the first NAND dump.

I assume this is because the Launcher file that I installed via TDT was a factory file that @rvtr extracted, and it didn't have a unique identifier on it. Or they were wiped intentionally. I am just guessing.

I tried mounting the NAND via ninfs, and got an error:

Command: ['C:\\Users\\DS\\AppData\\Local\\ninfs\\ninfs.exe',
 'nandtwl',
 'C:/Users/DS/Documents/NAND Saver Backups/13716012 U01576B '
 '-A26/DT0000000000000000/nand.bin',
 '-f',
 'C:/Users/DS/Documents/NAND Saver Backups/13716012 U01576B -A26/New '
 'folder']

MBR signature not found (expected "55aa", got "9cb6"). Make sure the provided Console ID and CID are correct.
Failed to do AttachConsole(35648): 0
(Note: this most likely isn't the cause of any other issues you might have!)
Console ID and CID read from nocash block.

Return code was 1

I also found that even if I was able to edit the NAND to remove traces of the language patcher, SafeNANDManager via NTR boot wasn't giving me the option to restore the NAND. I assume this is because the NAND I had was not named with that DT0000000000000000 string. If SafeNANDManager needs to verify the NAND backup file name before displaying the option to restore the NAND, not having a DT0000000000000000 file on my SD card meant I only had the option to back up the NAND.

I haven't tried to restore the NAND yet by renaming my original backup to that DT0000000000000000 string. I want to make sure that I didn't make a mistake here and do any irrerpairable damage.

I looked through the NAND on GodMode, and aside from the NAND:/launcher.dsiI couldn't find any of the 45/E = USA: W files that are on my NAND images before the TDT install.

The only thing I can think of is that installing the Launcher via TDT did a lot more than just replacing the 484e414a/content/00000004.app file. It seemed to have also cleared and reinstalled the title and ticket file directories as well. I am only basing this on what I see in GodMode, so that might not be true.

If this is how the console has to be for it to work, it is already in better shape than it was before. I wouldn't mind leaving it like this, but I don't know if it would cause any issues, like, for example, if I sell this motherboard to someone, and they try to reinstall Unlaunch and run into a crazy issue.

 

[rvtr]

I assume this is because the Launcher file that I installed via TDT was a factory file that @rvtr extracted, and it didn't have a unique identifier on it. Or they were wiped intentionally. I am just guessing.

The launcher has nothing to do with bad IDs. That would be an issue reading the keys from the CPU and NAND. Can happen if you're loading dump tools directly from ntrboot. Try chainloading ntrboot --> gm9i --> safenandmanager.
(also factory file? Only if you installed "HNAA.tad")

The only thing I can think of is that installing the Launcher via TDT did a lot more than just replacing the 484e414a/content/00000004.app file. It seemed to have also cleared and reinstalled the title and ticket file directories as well. I am only basing this on what I see in GodMode, so that might not be true.

TDT will update the TMD, app, and ticket files. Nothing else will be changed, especially not whole directories. For the ticket, updating only happens if you select the option to overwrite/replace it.

 

[k66]

DT0000000000000000

When dump NAND, verifying nocash_footer shows BAD, NAND backup will be exported to the DT000... folder, and the no$gba footer has no CID.
Back up NAND in these way, verifying nocash_footer BAD:
- DSi exploit → SafeNANDManager (SD:/boot.nds).
- DSi ntrboot (SafeNANDManager, SD:/ntrboot.nds).
- DSi ntrboot (HBmenu, SD:/ntrboot.nds) → SafeNANDManager .
X DSi's SD card files have errors, and after launching SafeNANDManager.
You just need to use the same method to restore the NAND.
.
I recommend backing up the NAND these way:
verifying nocash_footer GOOD, NAND backup in DT***(DSi CID)folder.
- Unlaunch → SafeNANDManager.
- DSi exploit → HBmenu or TWilightMeun++(SD:/boot.nds) → SafeNANDManager.
- DSi ntrboot (godmode9i, SD:/ntrboot.nds) → SafeNANDManager.

I tried mounting the NAND via ninfs, and got an error:

You can manually add the CID to nand.bin.

 

[KIlly728]

The launcher has nothing to do with bad IDs. That would be an issue reading the keys from the CPU and NAND. Can happen if you're loading dump tools directly from ntrboot. Try chainloading ntrboot --> gm9i --> safenandmanager.

Oh, I didn't think that mattered. I was under the assumption that NTRboot gave me, like, root/admin access to the whole console. I will have to try to make a backup through Godmode and see what happens.

(also factory file? Only if you installed "HNAA.tad")

I am speaking out of ignorance. I know you have factory tools on your website, so I wasn't sure if these firmwares were a part of it. Having that blank or defaulted string for a NAND backup was weird enough to me for that to be the only rational explination I had.

 

[rvtr]

I was under the assumption that NTRboot gave me, like, root/admin access to the whole console. I will have to try to make a backup through Godmode and see what happens.

ntrboot does give you greater access than other exploits (not really an exploit but still). The problem is just that a lot of homebrew doesn't load the keys properly on the first try. It's always troublesome. But usually chainloading will set up everything needed.

 

[k66]

Here it is. This is the NAND backup that was made before I reinstalled the launcher. I would be very curious to know what you find out. If you need any more files from that NAND, let me know.

Are you sure this is the file from the original faulty NAND?
title.tmd (192KB, with Unlaunch installed) is not read-only, it should be read-only.
title.tmd doesn't know why the read-only attribute was removed.

Solution: (If it is unclear whether the TMD file is intact, it is recommended.)
- Reinstall the Launcher using TDT, which will reinstall all files including title.tmd. #1686

Post automatically merged: Mar 7, 2026

It is indeed this problem, I verified it using the emulator.

Normal situation:
title.tmd (192KB, with Unlaunch installed) is read-only:

title.tmd (192KB, with Unlaunch installed) is not read-only:

Post automatically merged: Mar 7, 2026

@KIlly728
If I had asked you to upload the 00030017 folder from the start, it might have been solved in 2 seconds .
It could be encountering a rare bit-flip phenomenon?
But several of your DSi have the same problem, so I have to suspect that there is a bug in the DSi Language Patcher...
Or a problem occurred while uninstalling Unlaunch.