- Unable to mount CTRNAND or load the CTRNAND FIRM.
- Booted from CTRNAND via B9S (even if SD is inserted)
- "No accessible data in SD card" (BannerBomb3)
- Turning off parental controls
- No space for NAND backup
- More exception screens solutions (linking wiki)
if b9stool 7 was run and luma config did not boot, something unexpected and weird is going on. the old tactic of dry updating will not help, and manual assistance will be necessary to find a fix specific to what unexpected firm was installed.
- 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
It's actually usable now with a new, flashy, proxy server.
Steps more or less aligned with current state of guide.
Re-added most (if not all) troubleshooting from way back
when. (More accurately, stolen from Soundhax, because it
should behave nearly identically anyway.)
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>
By popular demand :D
Bring back Homebrew Launcher (PicHaxx) as well,and rewrite for modern
environment.
Add a warning for broken DSiWare issues in USM troubleshooting page,
and link that troubleshooting step directly in USM page.
Move hardware button warning to right under the relevant section,
just as an extra peace of mind.
Partial reverts to the 11.16 commit since PicHaxx is back™️
b9s-pichaxx: add link to troubleshooting page when launching picross
troubleshooting: shift black screen error to top of pichaxx header as it is the most common
b9s-*: remove "safety check" message because it is redundant (key combo will not appear until the necessary safety checks are complete)
b9s-picross: pokémon consistency (e -> é)
b9s-picross: account for top screen init fail
troubleshooting: re-word game starts normally troubleshooting to include movable.sed regeneration
