Temporary fix while working out a solution. The benefits of having this guide for the ~1% who have a HK/TW console are heavily outweighed by the negatives of people who get confused by this choice. (Admittedly, it could be better structured.)
My suggestion would be to set up the Crowdin translation so that this text is translated to the current structrue, but only for zh_** translations (like is done for the QQ group).
- 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
- Explicitly tell people not to uninstall CFW if they intend to reinstall CFW or if something is broken
- Be more clear about what actions will brick the console if CFW
- Move chainloader warning to where it's relevant
- Explain why broken Data Management is bad