* Update finalizing-setup.txt
* Update finalizing-setup.txt
* Update finalizing-setup.txt
* Update troubleshooting.txt
* Update troubleshooting.txt
* Update troubleshooting.txt
* Update finalizing-setup.txt
* Update troubleshooting.txt
* Update troubleshooting.txt
* Update finalizing-setup.txt
* Update troubleshooting.txt
* Update troubleshooting.txt
* Create troubleshooting.txt
* Update troubleshooting.txt
* Update troubleshooting.txt
* Update troubleshooting.txt
* Update troubleshooting.txt
Work in progress save
* Update finalizing-setup.txt
* Update finalizing-setup.txt
* Update troubleshooting.txt
* Update troubleshooting.txt
* Update troubleshooting.txt
* Update troubleshooting.txt
* Update troubleshooting.txt
* Update troubleshooting.txt
* Update troubleshooting.txt
* Update troubleshooting.txt
* Update troubleshooting.txt
change how the buttons are said to open safe mode to more match the rest of the guide
and reword the phrasing of "and following the prompts" to -----> "and following the on screen prompts". some people might get caught up on that so i changed it to be more clear
* Update troubleshooting.txt
* Update troubleshooting.txt
A few people have been confused about how to load GodMode9 in Section VI, and have accidentally pressed the button too late or tried to time the START button, etc. The fool-proof explanation on how to load GodMode9 or the chainloader menu appears to be to press and hold START, and keep holding the START button when powering on the console.
Section VI, step 2 makes this clearer.
I found someone who misspelled "payloads" as "playloads", causing
confusion for a while until I saw a directory listing. I don't know how
common exactly this is but I feel a note could be added here.
I'm not too happy about how this is worded though. Especially the path
which might need to be updated following #1829.
clarification added for screenshot. not sure removing the screenshot outright makes sense considering people get confused with too many words when pictures dont break it up.
* remove fred restoring from finalizing
* see desc
- remove the word "compatible", as all dsiwares are compatible with fredminer
- add `Nintendo 3DS` to the beginning of some paths; i believe its absence was just a typo/copypasta mistake
- specify that the bin file for ds internet will be named `42383841.bin` rather than just saying `<8-character-id>.bin`
- if multiple dsiware exports exist in the folder, it doesn't matter which the user uses. (all dsiware is compatible here; all that's needed out of the export is one hash from the header)
- move the restoration of ds internet from finalizing to here and add more specific steps for it to avoid confusion and save time
- minor wording changes to make things make more sense with the other changes
* hard to copy a file without the sd in the computer
* remove frogcert link, as it's not necessary for fredtool
additionally, remove support for n3ds ctrtransfered to 2.1.0 as instructions for doing that haven't been around for years and it's highly unlikely any 2.1.0 n3ds consoles are still around
I have changed my mind about sacrificing flexibility for convenience. OCS was too much of a black box which, while well intentioned, just didn't work very well in the environment we have available to us.
* Update move-emunand.txt
"Scripts" has been modified
* Update installing-boot9strap-(dsiware-save-injection).txt
* Update installing-boot9strap-(dsiware-game-injection).txt
* Another script dilemma
* Another script unturned
* some finishing touches
open source -> closed source, removed /all/ code contributed by other people for no reason other than to be legally able to do this
there's no good reason for free software to be closed source (especially after being previously open source!) other than wanting to hide the code that is containted in the software (which I do not trust, and will not compell my users to trust either)
