Unlaunch DSi | First public bootcode exploit for DSi

I have unlaunch 0.8 successfully installed on a DSI XL 1.4.5U and it boots hiyaCFW off the SD Card. I want to completely remove unlaunch so I can return the DSI XL. Do I need to figure out how to restore my NAND backup w/ NO$GBA footer, or is there some other way to remove unlaunch manually?

Edit: "format system memory" from the DSI settings (run on unmodified firmware) has no effect on unlaunch. Heck you can still run hiyacfw after doing so by putting your SD card back in.

Edit2: the Unlaunch installer suggests truncating the title.tmd for system menu, but I'm not sure what ds/i program will let me upload/overwrite files on the nand.

 

Woahhhhhhhhhhhh hold on there! Never restore a decrypted nand or one with the No$ fooster! You will need to restore a valid backup, unmodified. If you don't have one, you will need to replace the modded tmd.

 

The backup I made was the nand.bin file according to the HiyaCFW guide, made with twlnf. I'm assuming this is encrypted with a no$gba header?

Looking at the nand.bin in a hex editor, I'm guessing that the no$gba footer is the last x40 bytes of the file that begins with the ASCII "DSi eMMC CID/CPU" at x0F000000. If I delete those bytes, will I have a backup file that I can safely restore with fwtool?

 

Yeah, that guide really screws you. That has the fooster, and it really dissapoints me that such an unprofessional guide exists. Removing the fooster could work, but really don't try it. Download FWTool and backup your NAND. You will need to replace the tmd, and I will tell you how to when you have finished those steps.

 

Thanks for helping. I used the "safe" aug 17 2007 release of fwtool to dump dsi_nand.bin. It produced a file of 251,658,240 bytes. (Same size as a file where I chopped off the no$gba header, although the hashes don't match but I wouldn't expect them to.)

 

Great. You now need to decrypt your NAND with TWLTool, and you can find it in the downgrading guide. If you need my scripts, I will attach a whole kit that makes the whole process easier.

 

Is necessary Flipnote pre-installed?

 

yes

 

So I installed Unlaunch 0.8 on my DSi, but apparently it fails to start the "bootcode.dsi" file on my SD Card, regardless of what file I put there (Unlaunch 0.9 or HiyaCFW). When I boot my DSi, it displays a black screen, and only the power LED is turned on. If I hold A when powering it on, it boots normally though. Any idea on what may be causing this?

EDIT: Full formatting the SD Card solved this issue.

 

Hey! I used ugopwn and hbmenu and everything worked perfectly. You must note that. Thank you.

 

I used the automatic method on a European DSi.
Installed successfully, but, what is the purphose?
DSiGuide said it’s a proper brick protection, but how do I get to the menu to ‘recover’ from a previous NAND backup?

 

I think,main purpose of this is just loading bootcode.dsi. I think, it's just useful for USA region NDSes.

 

You can't restore your NAND dsi.cfw.guide doesn't make a NAND backup you can restore. Funny why people get mad at me when I say this, but it is true.

 

Oh,
had to read it twice, I guess.
What does bootcode.dsi even do because there is no purphose lmao

 

If you aren't using Hiya, it's useless.

 

I think it may be useful when flipnote lenny wasn't made. I thinked thos will be cool,because i'm not going to press paste for one hundred and even more times.

 

accidentally posted

 

Sort of...

 

I shouldn't even bother replying as I've tried to make you understand this multiple times, but I am against my better judgement.

Restoring a NAND backup is unsafe, and nobody should be doing it.

The bricks you're talking about is because people are using fwTool to restore. fwTool is a very unsafe tool for restores, the license for the program even says "don't use this", fwTool 2.0 removed the restore ability for good reason, and no safer tools exist.

If you really want to restore a NAND, you should at least have the technical understanding to check the sha1sum fwTool spits out against a backup with the footer removed manually. If users don't do this, it is entirely on them if they brick their system.

Furthermore, restoring an entire NAND backup just to remove a TMD file that's only a few kilobytes is absurd. I understand no uninstaller exists (besides TWLNF but that's unsafe in its own merit) but that doesn't make an entire restore a good idea.

 

I simply told someone that they had no luck, and you go and explain why! We might not agree, but COME ON, is it offensive to talk to me like I'm an idiot! It is very insulting to treat me like this! If I was someone you didn't know, you wouldn't say this at all! Nowhere in that post did I tell you to add a NAND backup in there! So why would you go and assume I did? You have done nothing productive, and you think you're so cool because you made a guide. Well, it's time someone tells you that. So before you go trying to tell me that I was wrong about something, TAKE THE TIME to read my post BEFORE you waste your time trying to prove a point that isn't necessary.

 

On the contrary, I'm quite calm. You seem to be the one who keeps saying the guide is unsafe because it doesn't make a "proper" and "safe" backup, when in actuality the backup is fine and fwTool is a dangerously unsafe power user tool that the common end-user shouldn't be using for restores.

I also recall being treated "like an idiot" when you kept showing users manual instructions on the Discord because they had an entirely unrelated issue that going through the old steps wouldn't have alleviated anyways.

But you certainly keep saying "dsi.cfw.guide can't make a NAND backup you can restore" and the like on other threads - when in actuality the NAND is perfectly restoreable once the footer is removed - and acting like restores are a perfectly safe process.

This is clearly bait, and I'm not even going to bother giving this a response.

I can say the same thing. What point are you trying to prove? Why are you continuously telling people that "no safe NAND backup is made" when no safe restore is possible? If "people gets mad" when you say this, have you considered the possibility that you're the one in the wrong?