* exchange fredtool-legacy for menuhax-uloader
* troubleshooting: add troubleshooting for menuhax67 leftover
* menuhax-uloader->menuhax
* fix wording of stuff
* make bb3 and uloader direct downloads
* add image for the home menu icon
* add commas
* wipe wipe and do do(usm -> menuhax)
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.
- 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>
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.)
bb3-fred-twn: new page
bb3: add redirect for twn consoles
seedminer: add bb3-fred-twn method with clear indication and separation to show it is for twn consoles only
main.js: add bb3-fred-twn route
en_us nav: add bb3-fred-twn page
site-nav: add bb3-fred-twn page
ALSO: Remove fading on dropdown menu click. This is also a bug on the actual upstream, when the cursor leaves the screen the menu disappears but the fading doesn't.
This causes things like the menu saying it's open when it's not and closed when open. I'm not dealing with an upstream bug.
* Restoring or updating CFW
* Checking for CFW
* Drop latest version notice on checking for CFW
* Inconsistent wording of new Restoring Updating CFW page name
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.
* Added F3
* Added guide
* Delete f3x-(mac).txt
* whoop
* Update _main.js
* Fixing mistakes part1
* Removed "The Latest Release of" text
* Reworded cd command
* Update f3-(mac).txt
* Make user move f3 folder to desktop
suggested by lilyuwuu so that way all users can be on the same page when doing the command line instructions.
* Made one line not sound as run on
* Changed “Run” to type
Decided to change it based off the command typing sections in the linux sd formatting guide
* Changed “F3X” to F3
How did i miss this
* Changed F3 again
I missed it again like how
* Add files via upload
* Not needed due to F3XSwift
* Rewritten for F3XSwift
* Update _main.js
* changed to F3XSwift
How did I miss this when I originally started it
* changed to F3XSwift
* corrected issues pointed out
* Changed to resolve conflict&readd sd notice
* fixed again
* Update get-started.txt
* made it appear once
accidentally cp'd it during editing
* readied for version issues
* Update get-started.txt
* Update f3x-(mac).txt
* F3XSwift-Mac: Add macOS compatibility warning; clarify instructions
* get-started: Switch link from F3X to F3XSwift
* site-nav: Add F3X to list
Co-authored-by: Lily <lily@uwuu.ca>
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.
The "if you get an error" line works under the assumption that no user error is happening. It is not possible to in-line troubleshoot all potential user error cases without increasing confusion.
The "No applications found" line has been modified to be more consistent with the rest of the guide.
The site navigation link to BrowserHax 2020 has also been renamed to be consistent with the name of the page.
