Most difficult/tedious process to install Unlaunch on a DSi. I know that flipnote lenny i think it was super annoying because i had to press the copy button like 126 times exactly, and then i had to do that 3 times because my dsi sd card slot is dead, now i do not have the dsi anymore.by bricking it I guess? Not sure what you mean by "worst possible way"
im risk tolerant.If you know how to do it, understanding that there are possible risks (but rare) such as bricking as mentioned, then you should be fine.
Perform the DSi Camera exploit instead.Most difficult/tedious process to install Unlaunch on a DSi. I know that flipnote lenny i think it was super annoying because i had to press the copy button like 126 times exactly, and then i had to do that 3 times because my dsi sd card slot is dead, now i do not have the dsi anymore.
all of them. Most chances of bricking and worst end results.Worst means many things in discussions like this.
Most aggravation to do.
Worst end results -- some of the earlier methods had limited abilities to access hardware. No great equivalents to some of the Switch things today where different firmwares might mean something, or like the 360 DVD vs JTAG/RGH, or 3ds firmware mods vs various flash cart offerings.
Most chance of bricking. Most of the time it is a short window in which you could screw something up if you tried hard.
What is needed to be installed, and what revisions of software are needed to be on could also factor into this. This would be older things like the cycloDS and older homebrew exploits in downloadable games that variously got blocked, patched or removed compared to modern stuff.
The most difficult way would definitely be via hardmodding, as that would require soldering directly to test points on the motherboard to read the NAND chip. But I wouldn't call it the "worst way" as, if you can successfully read/write to the NAND, you'll always be able to recover from a brick that corrupts sysNAND.Most difficult/tedious process to install Unlaunch on a DSi. I know that flipnote lenny i think it was super annoying because i had to press the copy button like 126 times exactly, and then i had to do that 3 times because my dsi sd card slot is dead, now i do not have the dsi anymore.
If you say so, but it does happen.im risk tolerant.
There's no need to act hostile.i do not have that fuc**** dsi anymore.
oh sorry, im a lilttle angry right now, i didn't sleep well but whatever, im bad mentally. Also i had a lot of problem with that DSiIf you say so, but it does happen.
Post automatically merged:
There's no need to act hostile.
That remembered me of someone hacking a gameboy with a silver play buttonWith a chainsaw?
ah yes, the most expensive, most difficult method to mod a dsi but it gives you full access over hardware.The most difficult way would definitely be via hardmodding, as that would require soldering directly to test points on the motherboard to read the NAND chip. But I wouldn't call it the "worst way" as, if you can successfully read/write to the NAND, you'll always be able to recover from a brick that corrupts sysNAND.
It's okay, I do feel for you. But just remember to take it easy and don't get angry over small things. We make mistakes all of time, especially me. If you feel like you can't get things right, such as the DSi you've just mentioned, then it's best to leave it and come back for it another day until you get it right.oh sorry, im a lilttle angry right now, i didn't sleep well but whatever, im bad mentally. Also i had a lot of problem with that DSi
Very much, as it is certainly not for the novice user. Softmodding is the way to go.Besides medieval physical tools style hacking, maybe install/uninstall an outdated unlaunch.
Hardmod is probably the riskiest serious answer.
That also doesn't mean it's the worst way, it's just not the right kind of exploit