Heh I bricked my DSi(it's headed to .NL for soldering+repair) by messing with writing minismarch savedata to NAND.(ran the app from sudokuhax, never soldered anything myself before) Sounds like my DSi displays the same screen except it
fails immediately after healthscreen instead of at title launching.
"but then i moved to Mexico and there is no number for Mexico." Why not call the USA phone-number? Or just contact NOA repair support via email or something.(I didn't bother with N at all /w my bricked DSi)
EDIT:
The NAND clk is horrid, it seemed to die while writing critical FS metadata. It died after writing only 0x18 clusters.(~98KB) Launcher/sysmenu accesses the data dir for bannersav(most titles including minismarch don't have that) might be related although launcher doesn't touch the savimage itself. My app didn't cause any brick until the third run, where I added a f_sync call for file flush/sync.
Edited 2 time(s). Last edit at 02/27/2011 09:13PM by yellowstar.