- Splits Seedminer into 2 pages, using includes. Prevents people from clicking on the twn method if they don't have a taiwanese console
- Adds a new version of Soundhax, for cart-updated consoles, more include, troubleshooting should stay
Make version selectable
This happens in order (with if/else statements):
- People select other -> redirect to checking for cfw(Checking for cfw might have to be reworded, redirecting people to NH if they boot into the HOME menu with Sys/Emu yah)
- People select 11.3 or lower -> redirect to standard Soundhax
- People select 11.4 or higher but nver < 37 and System version isnt 11.16(universal-otherapp patch lol) -> new fancy Soundhax-sp page, adds instructions on what to choose in the what you need section
- Function is called to check if cver combined with nver is sslothable... feedback appreciated on the numbers etc
- People select T as region -> redirect to seedminer(twn)
- People select C as region -> Display message pointing at ntrboot
- If none of the things apply -> redirect to Seedminer
Co-authored-by: lifehackerhansol <lifehacker@hansol.ca>
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
- Reorganize into two sections: 3DS-specific information and computer terminology
- Combine SD card location/type and capacity sections
- Remove some information that's not as important
- Add infobox for error checking
- Remove "what do I need to know" from homepage pending discussion on how to use the new page
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>
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
- Cropped screenshots so that they take up less space.
- Fix the notices in Finalizing Setup (they got broken)
- censor id0 in most places as an additional measure to prevent people from using example id0/id1
- clarify that id0 is system-specific in seedminer
* bring back kartdlphax
kinda tested, last 2 sections untested, should work though
* whoops
* Update get-started.txt
* update visual representation link
* oopsie
* rework based on changes in #2095
* align unsafemode section with hbl-usm
changed https://uwuu.ca/images/safemode_highlighted.png to /images/safemode_highlighted.png I hope thats good
* correct section numbers(thanks @lifehackerhansol)
* Update installing-boot9strap-(kartdlphax).txt
* remove plugin is running thing
* use pablos suggestion
* small grammar fixes
Co-authored-by: lily <lily@uwuu.ca>
- Make it clear you need to keep holding while turning console on.
- Direct people to another method if broken buttons is are suspected
to be the cause of SAFE_MODE boot fail.
- Partially revert 01edecf0ac
to bring button red warning back on top of page.
b9s 1.4 may be causing safeb9sinstaller to hang on "checking" in the microsd card step.. User 3DSes will still end up on b9s 1.4 regardless as this change only affects b9s flashed to the flashcart so there is not really much downside to this change.
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™️
