* Add includes for ctrtransfer steps
- Region changing and CTRTransfer uses this
- Also split HBL open options, it is also used by finalizing setup
* Commonize NAND backup steps
Finalizing Setup won't use this include for the time being. But we
should use it for GM9 usage as well as Region Changing.
* Commonize GM9 SD format steps
Pages using this include:
- godmode9-usage
- move-emunand
* remove usage of is-powered-off, just do that in the main page
* always power off after NAND backup, it's trivial to get back in
Trying to explain what "unmounting" is to a user is going to be
confusing anyway
* Unconditionally don't set up an emuNAND, also remove usage of is-powered-off
* Fix rendering
This is unnecessary and causes confusion for both the end user and the
helper, when one can just do another exploit if in such a situation
where these are necessary.
faq:
- add thing at the top about implications of eshop shutdown on installing cfw (spoiler: none)
- add "or newer" to 11.16 update notice (this should have been done a while ago)
- downgrade 11.16 update notice from warning to info
- Replace "use the eShop" with "play online" as an example feature after installing CFW
- Improve definition of difference between CFW and homebrew
- Reference that eShop has now shut down
region changing:
- Reword eshop access notice to account for games/DLC no longer being purchasable
This time, it's an HTML include, and not a relative include.
We can make use of the existing captures done for invalidVersion and
methodUnavailable by passing it to the include flag.
Move all HTML tags into the new HTML include so that it doesn't show on
Crowdin, this way translations aren't broken every time something in
the HTML tags change. One change will fix all of it.
Also, do not show the version selector if JS is not supported on the
browser. This can be done with a simple JS to display the script
automatically, which will by definition not show the selector when JS
isn't enabled as the JS to turn it on can't run.
I literally downloaded 14 korean updates, and wrote a script, to unzip, extract, ninfs, and print them, to get this done.
Co-authored-by: lifehackerhansol <lifehacker@hansol.ca>
- 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.
