cfw-guide / dsi.cfw.guide Goto Github PK

I think using diskpart on Windows would be the simplest way to avoid any issues regarding the SD card.

diskpart
list disk          (lists available disks, write down the correct number for your USB drive)
select disk N      (replace N with the USB drive number you wrote down)
clean
create partition primary
select partition 1
active
format unit=32k fs=fat32 quick
assign
exit

If any of those steps fail, the SD card cannot be used.

I did follow the guide to install Unlaunch then went to install Hiyacfw, i used the Hiya-helper correctly (it says "Done, eject your sd card" at the end of the process) but when i turn my dsi on and click on options (HiyaCFW activation part) there's no HiyaCFW in the menu, i reformatted my sd card multiple times without any luck, please help.
P.S: i'm using 8gb sd card.

Right now the Website of Unlaunch developer nocash returns 403. I noticed this two days ago when I set up my DSi for Homebrew.

I was able to get my hands on Unlaunch through the Wayback Machine. This also revealealed that the Website was still accessible last month.

If this is a permanent issue, it might be good to change the link in the guide to a Wayback-Machine-Link

The SD Card Setup page is nicely done but does not mention that the DSi strictly needs MBR formatted SD/microSD cards which I personally ran into. It would be nice if it included instructions for formatting an SD/microSD card from GPT to MBR.

https://dsi.cfw.guide/uninstalling-unlaunch currently instructs users to uninstall Unlaunch using its built-in uninstaller. This method is not as safe as using SafeNANDManager to restore a working NAND without Unlaunch on it, so it should be updated to use that.

The page should also link to https://wiki.ds-homebrew.com/ds-index/hardmod for bricked NANDs, instead of simply stating This page isn’t for you then, as it requires a working system in order to uninstall Unlaunch.

For users who lost their original pre-Unlaunch NAND backup, it might be worth suggesting setting up no$gba to uninstall Unlaunch from there.

I would like to write this myself, but I am not completely familiar with the process, so I'm not confident that I could write it will enough.

The menu appears to take a while to load for me, so I'd like to be able to see its progress.

This page of guide says unlaunch is not compatible with development units. Unlaunch works just fine on dev units, you just need to boot it from a homebrew app.

See here:
https://gbatemp.net/threads/install-unlaunch-on-development-units-pandas.648979/

I've tested this myself and can 100% say it works. Could a note/link be added for cool dev owners?

At the end, pointing to Replacing the System Menu with DSiMenu++

I just wanted to add my own experiences to the guide if anyone else has the Fat Mismatch error from using TWLnf you can fix it easily by deleting all the DSiware on your device and installing the 3ds transfer tool from the DSi e-Shop. This is ultimately what fixed the fat mismatch error for me when I tried to use unLaunch. Hope this helps!

Zoogie recently released two improved pit.bin files that are confirmed to work with older camera versions and regions like Korea and China; this version should also be more stable, more info on the link below.
The guide should be updated to use these files, removing the need to update the consoles to the latest version (very important if the NUS servers shuts down, or if someone doesn't want the trouble of downgrading the whitelist to use its old flashcard).

Source and download: https://gbatemp.net/threads/memory-pit-a-new-dsi-exploit-for-dsi-camera.539432/page-18#post-8667941

Simple as that, add them to https://dsi.cfw.guide/credits

SD Association released a Linux version: https://www.sdcard.org/downloads/sd-memory-card-formatter-for-linux/
So this should probably be integrated into the Linux section of SD formatting guide, like it is for Windows/Mac (maybe leaving the built-in Linux tools as a alternative option).

If my understanding from an earlier conversation is correct, https://dsi.cfw.guide/sd-card-setup should be updated to use SDFormatter for 32GB and below, and GUIFormat for 64 and above.
The reason for this being that SDFormatter will automatically choose the best cluster size and whether it should use FAT16 or 32, while GUIFormat will always use FAT32, which is not optimal for 2GB and below.
SDFormatter is also known to fix SD cards that are problematic with Unlaunch.

FailZone has been published today, and is available on the DSi Homebrew discord. Can we have an update?

Hello, I noticed that there are two missing steps that are worth adding to the guide. At the Installing TwiLight Menu ++ page, I would recommend adding these steps:

Between steps 4 and 5, instruct the user to eject their sd card and insert it to their system. I know this is a bit nitpicky, but it will remain consistent with the rest of the guide.

In step 5, instruct the user to load Unlaunch (by holding the A button before powering on) and navigating to the Options menu in order to change the No_Button configuration from Hiya CFW to TwilightMenu++.

Thanks so much for the guide by the way, it was very useful!

While the majority of users have access to a Windows/macOS/Linux PC, some are using Android/iOS, so proper SD card formatting instructions for these devices would be great, especially for Unlaunch installation. This could be done in a couple of ways:

1. Adding the ability to properly format the SD card on the DSi itself, through an application such as GodMode9i
   • When formatting, the user would be prompted to temporarily store files in the 15 MB of RAM available (or a flashcard if accessible), so that things such as Memory Pit, GodMode9i itself, Unlaunch Installer, etc can be preserved
2. Using an Android/iOS app that is known to consistently properly format the SD card

While either of these solutions would work, I figure the latter would be better and easier.

I use a DSi XL.

I decided to use the same SD card used to mod my DSi to show people some photos I took. I named the folder with the photos 'THE PHOTOS ARE HERE', put my photos inside in jpeg format, then left. When I eventually made it there, I inserted the SD card into their computer.

The folder was gone. Back at home, it was gone as well. I tried to make a new folder called 'THE PHOTOS ARE HERE', but Windows told me there was already a folder of the same name.

So I used NitroEdit to see if I could mod MKDS a bit. I saw the 'THE PHOTOS ARE HERE' folder only when using NitroEdit. I have no idea why. It still had the jpegs inside.

I can't attach a .zip file of my SD card, because it's above the limit.

I don't know where else to post about this problem. How do I get the photos back?

https://dsi.cfw.guide/dumping-nand.html#section-ii-dumping-the-nand:~:text=the%20sha1%20hash%20of%20the%20nand.bin%20will%20not%20match%20the%20hash%20stored%20in%20nand.bin.sha1.%20this%20is%20because%20dumptool%20adds%20additional%20data%20known%20as%20a%20no%24gba%20footer%20to%20the%20nand.bin%20file%20after%20the%20sha1%20hash%20is%20calculated.%20you%20can%20use%20the%20hiyacfw%20helperopen recommends https://github.com/mondul/HiyaCFW-Helper/releases

The SHA1 hash of the nand.bin will not match the hash stored in nand.bin.sha1. This is because dumpTool adds additional data known as a no$gba footer to the nand.bin file after the SHA1 hash is calculated. You can use the hiyaCFW Helper to create a copy without the footer.

but https://github.com/mondul/HiyaCFW-Helper/ is archived.

On the "Installing HiyaCFW" page, at the SDNAND Creation section, fuse-3ds is not required because hiyacfw_helper creates a nand_dec.bin file that can be directly mounted with OSFMount, which will show some partitions to choose, and choosing the big one will give access to the files in twl_main.img.

On linux, the file can be read by creating loop devices from it with kpartx and mounting them with mount.

On macOS I did it by attaching it as a raw disk image using hdiutil and then mounting it with diskutil.

NEVER MIND!!!

The problem are

when i used NAND in HiyaCFW Helper and that show error

"Mounting Decrypted NAND....
ERROR : Mounter Failed"

I've tried reformat my SD Card and Reinstalling HiyaCFW, But it's still the same.
I just following the guide on Dsi Guide btw

Help me
Note: I used 32GB SD Card and full formatted fat32. I've install Twilight menu ++ to but i can't play DS Rom, it'll be freezes and keep white screen after loading screen.
Thanks

Tried to autoboot/launch supercard ds two plus from unlaunch but the cart appears with this name: "ooooooooooooooooo" and when selected to autoboot, it won't boot, just a blank screen.

There has been a few people with confusion as to whether the need for a partition table is there.

Specifically this line:
Take note of the device mount point. In our example above, it was mmcblk0

This can imply that the filesystem has to be placed on the disk, instead of on a partition; however, Unlaunch requires a partition table or it will complain. This should likely say in our example above, it was mmcblk0p1 since that would be a partition. (basically, this example is somewhat vague.) Then in the next line, mkdosfs /dev/(device mount point from above) would now be referencing mmcblk0p1 and not mmcblk0.

Though if an SD card somehow doesn't have a partition table to begin with, I don't know how I'd explain that via the guide (although if it's in this state they likely know how to make a partition table). I guess it can suggest looking at which TYPE each mount point is.

Was going to make a PR, but I can't think of a way to explain this, so made an issue instead.

At the moment, formatting the SD card is not part of the main guide, and is instead linked on the topbar and mentioned in Getting Started. It is not setup to continue into the main guide, either.

In my opinion, it should be integrated into the main guide as the first (or second, depending on how this will be setup) page in the guide.

Some reasons listed here:

• Unlaunch is incredibly picky about SD card formatting. It will not accept 64KB+ clusters, and will complain if it finds VBR/MBR errors, or will just inexplicably not load anything at all until formatted the way it likes it. The formatting guide will almost always take care of this, at least on Windows and macOS
• 64GB+ SD cards are very cheap now, and are typically formatted as exFAT by default. The default Windows formatter doesn't allow you to format SDXC cards as FAT32, so it is unlikely that the common user might have done this themselves
• Making sure the SD card uses 32KB clusters with FAT or FAT32 is best for an optimal experience across apps, including TWiLight Menu++

Suggestion: If you ask the user to download dumpTool and Unlaunch to their SD card before they launch the exploit, they can just follow along instead of turning off the system, swapping the SD card over to their computer and then back to the DSi, etc.
Not sure if this has been brought up before.