- Convert FAQ and Troubleshooting pages to clickable dropdowns to improve readability.
- Add separate table of contents to Troubleshooting (for mobile users)
- Remove a couple of irrelevant troubleshooting
- Update pages that link to troubleshooting to use new headers
* faq+troubleshooting: dropdowns
- Convert FAQ and Troubleshooting pages to clickable dropdowns to improve readability.
- Add separate table of contents to Troubleshooting (for mobile users)
- Remove a couple of irrelevant troubleshooting
- Update pages that link to troubleshooting to use new headers
* a9lh-to-b9s: fix typo
readd screenshots that were lost when switching bb3
remove screenshots not used in years
add inline troubleshooting for red screen usm
fix language in troubleshooting
Restructure all BB3-related methods into a monolithic branch under
BannerBomb3, and use the multihax injector. (Manually fixed bb3.bin
by me to make things not confusing.)
Makes guide easier to maintain, and many other things cleaned up overall.
Co-authored-by: lifehackerhansol <lifehacker@hansol.ca>
add screenshot for boot9strap folder
add screenshot for 3ds folder
add file layout screenshots for hbl-pichaxx and hbl-usm
fix typo that breaks screenshot link in usm and hbl-usm
remove some unnecessary indenting
firwmare -> firmware
id1 folder consistency based on what people should have at that point of the guide
The troubleshooting overhaul changed troubleshoot titles, so they've been changed accordingly.
The troubleshooting page has been moved around a bit to make it easier for people to find the most likely issue (missing boot.firm).
Updates guide to support 11.15. In particular:
- Removal of browserhax as main guide path -- not completely removed/stubbed yet.
- Removal of Seedminer out-of-date warning.
- Addition of Seedminer to get-started and site-nav recommended.
This commit aims to make guide wording on some pages more consistent to make it easier to understand.
A warning has been added above each Legacy Method page, and the links to their respective tools have been fixed.
reworded the "create nintendo dsiware" to make it easier to see that it will have to be created if its not there
added some verbiage to the top of the what you need section to help remind (even after just 3 steps) that the file you need is probably on SD root
