Hey guys, just wanted to report in and say that changing the DS profile's colour may in fact cause the exploit to stick as well. I successfully installed the MSET exploit on my Australian n3DS (non-XL white model, sysnand 9.0.0-20E/emunand 9.5.0-23E, and with no NDS timewarp installed) a few days ago with no problems, and decided to test with my DSTwo whether or not I was one of the lucky ones with an exploit that stuck. That turned out to not be the case, however I noticed while in the DS profile settings that the colour was set to bright pink. Being one of those pathetic "eeeewwww! pink is a baby colour!1" types, I immediately changed it before reinstalling NVRAM, booting back into Gateway mode and leaving the n3DS alone.
After finding this thread today I decided to give the method on page 4 a try, booting back into sysnand and using my DSTwo to re-break the exploit in order to get back into the DS profile settings and change the name. Only I can't get the exploit to break now, having ended up back at the Gateway menu three times. Since the DSTwo wouldn't break it, I tested a handful of my retail NDS carts and the exploit has still stuck: out of six tests - loading an NDS game and rebooting before going into settings - five still worked and one gave a random black screen (rebooting the console and going straight back to settings > DS profile without reinstalling NVRAM caused it to load successfully next time, though).
EDIT: Accessing DS profile settings in emunand didn't break it either, though that may just be because my nands were unlinked before 3.2 came out.
After finding this thread today I decided to give the method on page 4 a try, booting back into sysnand and using my DSTwo to re-break the exploit in order to get back into the DS profile settings and change the name. Only I can't get the exploit to break now, having ended up back at the Gateway menu three times. Since the DSTwo wouldn't break it, I tested a handful of my retail NDS carts and the exploit has still stuck: out of six tests - loading an NDS game and rebooting before going into settings - five still worked and one gave a random black screen (rebooting the console and going straight back to settings > DS profile without reinstalling NVRAM caused it to load successfully next time, though).
EDIT: Accessing DS profile settings in emunand didn't break it either, though that may just be because my nands were unlinked before 3.2 came out.

















