#define FUUUZAY_GELLAY_ATMOSPHERAY_STRATOSPHEREYYY printk("Note: Fus\e9e Gel\e9e Atmosph\e9re Stratosph\e9re \x13\x33\x37 is almost there! I want to give thanks to all contributors involved in making this happen!\n");
if(strcmpk(CFW, "CUSTOM FIRMWARÈE") == 0)
{
FUUUZAY_GELLAY_ATMOSPHERAY_STRATOSPHEREYYY //
}
Wait I don't understand french though, does the atmosphère and stratosphère because they have the accent like fusèe gelèe, are they pronounced in the same way? ^^above the pronunciation I think is maybe accurate. I mean no disrepect to french people for the above, just having fun with the pronunciation of the name, it is a cool name after all. I wasn't liking it at first, but it has grown on me and now I love it! And I'm being genuine about my thanks to every and all contributors to the exploit and cfw project!
Also I respond to the switch brickers, noting garyopa's response I'll say: You guys must believe the switch is so fragile, that you can so easily brick it. I'm trying to step into your thought process-> You must think that there's a million lines of code that will instantly brick the switch and make it totally unrecoverable from that brick while there's only 1 line of code that will do the right thing and not brick. That's not true actually though, that's not the way it works, that's not how any of this works. You could play around with code INTENTIONALLY trying to brick the switch and probably would have difficulty in even trying to purposely do it. And like garyopa said, you could remove the nand entirely and still have a functioning switch. Hell some people might remove their nands and once avail launch custom firmware directly from sd never needing the nand at all.(actually probably not any real good reason to lose the sysnand, but just exemplifying the point that the switch is an unbrickable system now that we have basically become the switch factory and have the same access to the system that they do, they are no longer above us, the playing field has been leveled.) Linux already works like this, it loads from the sd not the nand and unless you do the reverse dd command (with input file and output file [if/of] swapped from nand to disk to disk to nand) you still aren't touching the nand. So even if you wrecked the data on or removed the nand, you could still run linux on it, or custom firmware with emunand only with absent sysnand (well it depends on if they make the emunand dependent upon having a sysnand present). Do you guys know any other device that's also unbrickable like this? It's kind of a rare thing that we get this low level of access for any device. So low that nearly the only way to brick it, is to smash it with a real brick!
By the way for dd, if coreutils v8.24 or higher, you can add " status=progress" at the end of the command for progress indication instead of just a blank prompt until it's done, that's been helpful to me whenever using it, you use to have to use something like pipeviewer (pv) and pipe it to it to get the progress (which obviously slowed it down a bit in exchange for getting progress status, but with it built in that's no longer the case)