Your call.I've backed up and restored NANDs on this DSi before, and it seemed fine.
Your call.I've backed up and restored NANDs on this DSi before, and it seemed fine.
I'll trim to 0EFFFFFF (the rest is 0000s anyway) and... well... I can hardmod it if it bricksYour call.
By looking at the code it doesn't seem to matter, it only reads the first 240MB anyway, also keeping the nocash footer shouldn't do any harm.I'll trim to 0EFFFFFF (the rest is 0000s anyway) and... well... I can hardmod it if it bricks
I'm going to remove it anywayBy looking at the code it doesn't seem to matter, it only reads the first 240MB anyway, also keeping the nocash footer shouldn't do any harm.
Worked like a charm. Now if only 4swordshax would work...I'm going to remove it anyway
Afaik tik is automatically generated by TWLnf.Can you remind me what 'format' the .app, .tik and .tmd need to be in? I've forgotten...
And the rest?Afaik tik is automatically generated by TWLnf.
That is... probably true.Why doesn't 4swordhax work? And the rest of your questions was answered in the OP.
Take a look at the script, it explains itself.That is... probably true.
I don't know, 4swordshax just whitescreens for me.
And... I don't need anything for the auto downgrader??
(You can tell at this point that I'm slightly confused)
So... I need the .app and .tmd files, .tmds trimmed or untrimmed (I'll probably not trim) or the downgrade and it does the rest. Great.Take a look at the script, it explains itself.
Did you track down when the bricking occurs? Immediately when exceeding the 1028 (?) block limit, or only when leaving something less than 1 Mbyte free space?
Some ideas/notes what might be going on:
Exceeding the limit could confuse the data managment screen in system settings, but might still work in launcher.
Some free space might be required when rewriting log files and config files (if the DSi is first writing the new file, and then deleting the old file).
More free space would be needed when installing system updates with bigger firmwares, probably including additional space for temporary files during installation.
Installing homebrew tools on internal eMMC memory would also reduce the available space.
The maths for used blocks should theoretically include a lot of stuff: The .app file, the .sav file(s), the .tmd file, the .tik file, and the various game folders (with file/folder sizes being rounded up to FAT cluster sizes).
The .tik files are kept on the system even when deleting titles in data managment screen, so they keep taking up space even if they are 'deleted'.
The "compute free/used blocks" formula could be quite difficult, and even if it's perfectly computed, it could still fail if the user has unexpectedly installed some extra files (either by mistake, like leaving old/backup files in the filesystem, or when intentionally adding some hacks/wifibootcode that works without SD card). Workaround would be to try to compute the used blocks for DSi titles, and additionally make sure that there are at least so and so many free megabytes.
So we can manipulate a Dsi Nand.bin on the 3ds?Just realized I can test NAND writing on 3DS, I have B9S!
update: it didn't brick my 2DS TWL, great.
update: document updated.
Write a script.@JimmyZ
Any chance to have a Whitelist dumper/flasher?