Skip to content

Commit

Permalink
Deploying to gh-pages from @ c001e8e 🚀
Browse files Browse the repository at this point in the history
  • Loading branch information
DefenderOfHyrule committed Jun 30, 2024
1 parent 7e28d09 commit ec581b8
Show file tree
Hide file tree
Showing 8 changed files with 64 additions and 36 deletions.
6 changes: 5 additions & 1 deletion extras/installing_android/index.html
Original file line number Diff line number Diff line change
Expand Up @@ -1662,7 +1662,7 @@


<h1 id="installing-android">Installing Android<a class="headerlink" href="#installing-android" title="Permanent link">&para;</a></h1>
<p>This page will detail the setup of the latest release of Switchroot Android (Android 11) for the Nintendo Switch.</p>
<p>This page will detail the setup of Switchroot Android (Android 11) for the Nintendo Switch.</p>
<div class="admonition warning">
<p class="admonition-title">Have you partitioned your microSD card?</p>
<p>This page assumes that you've followed our guide to set up Atmosphère. Before starting, your microSD card needs partitions for Android set up via Hekate.<br>
Expand All @@ -1673,6 +1673,10 @@ <h1 id="installing-android">Installing Android<a class="headerlink" href="#insta
<p class="admonition-title">Looking for Android 10?</p>
<p>An unfortunate bug with clocking on Android 11 results in degraded performance for Erista (v1) units on Android 11. Android 10 installation is not covered here, but there is a <a href="https://wiki.switchroot.org/wiki/android/10-q-setup-guide">guide</a> on the Switchroot Wiki. However, Android 11 is the currently supported version and uses much more updated drivers.</p>
</div>
<div class="admonition info">
<p class="admonition-title">Looking for Android 14?</p>
<p>Recently, Android 14 was released for the Switch. You can follow the official <a href="https://wiki.lineageos.org/devices/nx_tab/">LineageOS guide</a> to install Android 14.</p>
</div>
<p>The Switch lacks a cell modem; simply installing Android does not grant your Switch access to cell towers. This means, unlike most Android devices, you will not be able to make emergency phone calls, and you will still need Wi-Fi to access the Internet. You can, however, natively run Android programs and games.</p>
<p>This page will also <em>not</em> detail things such as rooting and overclocking; external links to these types of additions can be found in the <a href="#power-user-guides">Power User Guides</a> section at the bottom of this page.</p>
<h3 id="requirements"><strong>Requirements:</strong><a class="headerlink" href="#requirements" title="Permanent link">&para;</a></h3>
Expand Down
8 changes: 4 additions & 4 deletions extras/transfer_sd/index.html
Original file line number Diff line number Diff line change
Expand Up @@ -1650,7 +1650,7 @@ <h4 id="instructions"><strong>Instructions:</strong><a class="headerlink" href="
<p>You should first check whether you have a file or partition based emuMMC:</p>
<ol>
<li>Enter RCM and inject the Hekate payload.<ul>
<li>If you use a modchipped Switch, you can simply just turn your Switch on with the Hekate payload renamed to <code>payload.bin</code> on the root of your SD.</li>
<li>If you use a modchipped Switch, you can simply just turn your Switch on with the Hekate payload renamed to <code>payload.bin</code> on the root of your microSD card.</li>
</ul>
</li>
<li>Tap on the <code>emuMMC</code> button.</li>
Expand All @@ -1663,7 +1663,7 @@ <h4 id="instructions"><strong>Instructions:</strong><a class="headerlink" href="
<h3 id="if-you-are-using-a-file-based-emummc-or-are-using-no-emummc-at-all"><strong>If you are using a file based emuMMC or are using no emuMMC at all:</strong><a class="headerlink" href="#if-you-are-using-a-file-based-emummc-or-are-using-no-emummc-at-all" title="Permanent link">&para;</a></h3>
<ol>
<li>Enter RCM and inject the Hekate payload.<ul>
<li>If you use a modchipped Switch, you can simply just turn your Switch on with the Hekate payload renamed to <code>payload.bin</code> on the root of your SD.</li>
<li>If you use a modchipped Switch, you can simply just turn your Switch on with the Hekate payload renamed to <code>payload.bin</code> on the root of your microSD card.</li>
</ul>
</li>
<li>Navigate to <code>Tools</code> &gt; <code>USB Tools</code> &gt; <code>SD Card</code> and plug your Switch into your PC via USB.</li>
Expand All @@ -1690,7 +1690,7 @@ <h3 id="if-you-are-using-a-partition-based-emummc"><strong>If you are using a pa
<li>In the main menu, tap on <code>Tools</code>, then <code>Backup eMMC</code> and set <code>SD emuMMC Raw Partition</code> at the bottom of your screen to <code>ON</code>.</li>
<li>Backup both <code>SD emuMMC BOOT0 &amp; BOOT1</code> and <code>SD emuMMC RAW GPP</code> (Note: <code>SD emuMMC RAW GPP</code> may take a while).</li>
<li>Once both are done, go back to the main menu, navigate to <code>Tools</code> &gt; <code>USB Tools</code> &gt; <code>SD Card</code> and plug your Switch into your PC via USB.</li>
<li>If Windows asks you to format a drive, discard it and select the drive with your SD contents.</li>
<li>If Windows asks you to format a drive, discard it and open the accessible drive containing the contents of your microSD card.</li>
<li>Copy the contents of your old microSD card somewhere to your PC.</li>
<li>Follow the <code>Preparing Hekate</code> section at the bottom of <a href="../../user_guide/rcm/sending_payload/">this page</a> (Unpatched Switch users only) to prepare your new SD card with Hekate's files.<ul>
<li>If you have a modchipped Switch, follow <a href="../../user_guide/modchip/preparing_hekate/">this page</a> instead.</li>
Expand All @@ -1702,7 +1702,7 @@ <h3 id="if-you-are-using-a-partition-based-emummc"><strong>If you are using a pa
<li>Navigate to <code>/backup/&lt;some characters&gt;/emummc</code> on your microSD card and move <code>BOOT0</code>, <code>BOOT1</code> and the <code>rawnand.bin.xx</code> files to <code>/backup/&lt;some characters&gt;/restore/emummc</code>.</li>
<li>Eject the <code>UMS</code> device safely from within your computer's operating system.</li>
<li>Tap on <code>Tools</code>, <code>Restore eMMC</code>, set <code>SD emuMMC Raw Partition</code> at the bottom of your screen to <code>ON</code>.</li>
<li>Restore the backup by tapping on both <code>SD emuMMC BOOT0 &amp; BOOT1</code> and <code>SD emuMMC RAW GPP</code> (Note: `SD emuMMC RAW GPP may take a while).<ul>
<li>Restore the backup by tapping on both <code>SD emuMMC BOOT0 &amp; BOOT1</code> and <code>SD emuMMC RAW GPP</code> (Note: <code>SD emuMMC RAW GPP</code> may take a while).<ul>
<li>It is very important that for both of these the <code>SD emuMMC Raw Partition</code> option is enabled, otherwise you will be altering your sysMMC
which is not what you want.</li>
</ul>
Expand Down
15 changes: 7 additions & 8 deletions extras/updating/index.html
Original file line number Diff line number Diff line change
Expand Up @@ -1682,7 +1682,7 @@ <h3 id="updating-atmosphere"><strong>Updating Atmosphere</strong><a class="heade
<p>When a new version of Atmosphère releases, you can update Atmosphère by following these steps:</p>
<ol>
<li>Enter RCM and inject the Hekate payload.<ul>
<li>If you use a modchipped Switch, you can simply just turn your Switch on with the Hekate payload renamed to <code>payload.bin</code> on the root of your SD.</li>
<li>If you use a modchipped Switch, you can simply just turn your Switch on with the Hekate payload renamed to <code>payload.bin</code> on the root of your microSD card.</li>
</ul>
</li>
<li>Navigate to <code>Tools</code> &gt; <code>USB Tools</code> &gt; <code>SD Card</code> and plug your Switch into your PC via USB.</li>
Expand All @@ -1699,7 +1699,7 @@ <h3 id="updating-hekate"><strong>Updating Hekate</strong><a class="headerlink" h
<p>When a new version of Hekate releases, you can update by following these steps:</p>
<ol>
<li>Enter RCM and inject the Hekate payload.<ul>
<li>If you use a modchipped Switch, you can simply just turn your Switch on with the Hekate payload renamed to <code>payload.bin</code> on the root of your SD.</li>
<li>If you use a modchipped Switch, you can simply just turn your Switch on with the Hekate payload renamed to <code>payload.bin</code> on the root of your microSD card.</li>
</ul>
</li>
<li>Navigate to <code>Tools</code> &gt; <code>USB Tools</code> &gt; <code>SD Card</code> and plug your Switch into your PC via USB.</li>
Expand Down Expand Up @@ -1796,20 +1796,19 @@ <h4 id="what-you-need"><strong>What you need:</strong><a class="headerlink" href
</ul>
<h4 id="preparing-your-microsd-card"><strong>Preparing your microSD card</strong><a class="headerlink" href="#preparing-your-microsd-card" title="Permanent link">&para;</a></h4>
<ol>
<li>Load Hekate, start Hekate UMS by going to <code>Tools</code> &gt; <code>USB Tools</code> &gt; <code>SD Card</code></li>
<li>Connect your Switch to your PC via a USB cable. An Android phone may also work.</li>
<li>Download <code>TegraExplorer.bin</code> and place it somewhere on your device (A good idea is to put it where you keep all your Switch payloads like Hekate).</li>
<li>Update Atmosphère and Hekate by using the above guides.</li>
<li>If you haven't already, update the sysMMC to the latest firmware using the steps below.</li>
<li>Boot into Hekate.</li>
<li>Go to <code>Tools</code> &gt; <code>USB Tools</code> &gt; <code>SD Card</code> and connect your Switch to your PC via USB.</li>
<li>Download the latest release of <code>TegraExplorer.bin</code> and place it <code>sd:/bootloader/payloads</code>.</li>
</ol>
<p>Make sure your sysMMC is updated before moving onto the instructions below.</p>
<h4 id="dumping-your-sysmmc-firmware"><strong>Dumping your sysMMC firmware</strong><a class="headerlink" href="#dumping-your-sysmmc-firmware" title="Permanent link">&para;</a></h4>
<ol>
<li>Make sure your sysMMC is up to date. If your sysMMC is not up-to-date, boot into Stock or sysCFW and update it through the System Settings.<ul>
<li>sysCFW is recommended since it preserves e-fuses and preserves AutoRCM (if applicable).</li>
</ul>
</li>
<li>Inject <code>TegraExplorer.bin</code> using your favourite payload injector (Like you would with Hekate).<ul>
<li>If you are using a modchipped Switch, you can simply put <code>TegraExplorer.bin</code> in <code>sd:/bootloader/payloads</code> on your SD card, then turn on your console and load TegraExplorer via Hekate's payloads menu (<code>Payloads</code> &gt; <code>TegraExplorer.bin</code>).</li>
<li>If you are using a modchipped Switch, you can simply put <code>TegraExplorer.bin</code> in <code>sd:/bootloader/payloads</code> on your microSD card, then turn on your console and load TegraExplorer via Hekate's payloads menu (<code>Payloads</code> &gt; <code>TegraExplorer.bin</code>).</li>
</ul>
</li>
<li>Using the joystick and the A buttons, select <code>FirmwareDump.te</code>, then select <code>Dump sysmmc</code>.<ul>
Expand Down
35 changes: 19 additions & 16 deletions faq/index.html
Original file line number Diff line number Diff line change
Expand Up @@ -1585,9 +1585,9 @@
</li>

<li class="md-nav__item">
<a href="#how-do-i-use-the-exploit-how-can-i-boot-into-rcm" class="md-nav__link">
<a href="#how-do-i-use-fusee-gelee-how-can-i-boot-into-rcm" class="md-nav__link">
<span class="md-ellipsis">
How do I use the exploit? How can I boot into RCM?
How do I use fusee-gelee? How can I boot into RCM?
</span>
</a>

Expand Down Expand Up @@ -1657,9 +1657,9 @@
</li>

<li class="md-nav__item">
<a href="#my-homebrew-is-not-showing-up-on-the-menu" class="md-nav__link">
<a href="#my-homebrew-apps-are-not-showing-up-in-the-homebrew-menu" class="md-nav__link">
<span class="md-ellipsis">
My homebrew is not showing up on the menu
My Homebrew apps are not showing up in the Homebrew menu!
</span>
</a>

Expand Down Expand Up @@ -1722,10 +1722,10 @@ <h3 id="what-firmware-versions-are-currently-hackable"><strong>What firmware ver
Even with this exploit fixed, many Switch consoles on 8.0.1 and below will be hackable to some degree in the future (see <a href="#should-i-update-my-firmware">Should I update my Firmware?</a> for much more detailed information).
The serial number on the back of the box can possibly tell you which consoles are patched and which aren't.
See <a href="https://gbatemp.net/threads/switch-informations-by-serial-number.481215/" target="_blank">here</a> for an up to date list.</p>
<h3 id="how-do-i-use-the-exploit-how-can-i-boot-into-rcm"><strong>How do I use the exploit? How can I boot into RCM?</strong><a class="headerlink" href="#how-do-i-use-the-exploit-how-can-i-boot-into-rcm" title="Permanent link">&para;</a></h3>
<p>To launch CFW through the exploit, the Switch needs to be in "Recovery Mode"(RCM).
<h3 id="how-do-i-use-fusee-gelee-how-can-i-boot-into-rcm"><strong>How do I use fusee-gelee? How can I boot into RCM?</strong><a class="headerlink" href="#how-do-i-use-fusee-gelee-how-can-i-boot-into-rcm" title="Permanent link">&para;</a></h3>
<p>To launch CFW through the fusee-gelee, the Switch needs to be in "ReCovery Mode"(RCM).
The easiest way to enter RCM is by grounding pin 10 in the right joycon rail and holding VOL+ on boot.
Several methods and designs to do this exist, see <a href="https://nh-server.github.io/switch-guide/user_guide/emummc/entering_rcm">our guide</a> for more information.
Several methods and designs to do this exist, see <a href="../user_guide/rcm/entering_rcm/">our guide</a> for more information.
Once the Switch is in RCM it needs to be connected to either a computer, phone or dongle to send the exploit and the payload.</p>
<p>This procedure needs to happen every time the Switch boots from a completely "off" state, otherwise the Switch will boot into the stock firmware.</p>
<h3 id="what-makes-a-good-jig-good-can-i-use-a-paperclip"><strong>What makes a good jig good? Can I use a paperclip?</strong><a class="headerlink" href="#what-makes-a-good-jig-good-can-i-use-a-paperclip" title="Permanent link">&para;</a></h3>
Expand Down Expand Up @@ -1815,16 +1815,19 @@ <h3 id="fake-microsd-cards"><strong>Fake microSD cards</strong><a class="headerl
These microSD cards are often fake and do not have the advertised amount of storage and will result in data corruption if used.
Amazon has had some problems with fake microSD cards, so we recommend buying them at a physical store. Even on trustworthy sites, <em>always, always check reviews on a product before buying!!</em></p>
<p>If you suspect your microSD card is fake or damaged, see the instructions <a href="https://3ds.eiphax.tech/sd.html" target="_blank">here</a> to verify the integrity of your microSD card.</p>
<h3 id="my-homebrew-is-not-showing-up-on-the-menu"><strong>My homebrew is not showing up on the menu</strong><a class="headerlink" href="#my-homebrew-is-not-showing-up-on-the-menu" title="Permanent link">&para;</a></h3>
<p>This is an issue primarily affecting macOS users, but may occur on other devices as well. If you are able to launch the homebrew menu, but you are not seeing some or any of your homebrew, you may need to unset the archive bit with Hekate.</p>
<h3 id="my-homebrew-apps-are-not-showing-up-in-the-homebrew-menu"><strong>My Homebrew apps are not showing up in the Homebrew menu!</strong><a class="headerlink" href="#my-homebrew-apps-are-not-showing-up-in-the-homebrew-menu" title="Permanent link">&para;</a></h3>
<p>This is an issue primarily affecting macOS users, but may occur on other devices as well. If you are able to launch the homebrew menu, but you are not seeing some or any of your Homebrew apps, you may need to unset the archive bit with Hekate.</p>
<ol>
<li>Send the Hekate payload to your Switch by following these instructions: <a href="https://nh-server.github.io/switch-guide/user_guide/emummc/sending_payload/">here</a></li>
<li>Click on <code>Tools</code> on the top menu bar</li>
<li>In the bottom left corner click on <code>Arch Bit • AutoRCM • Touch • Pkg1/2</code></li>
<li>Click on <code>Fix Archive bit</code> - this might take a while</li>
<li>Press <code>Close</code> in the top right corner</li>
<li>Press <code>Home</code> in the top menu bar to get back from where you started</li>
<li>Follow the instructions at the Launching CFW page <a href="https://nh-server.github.io/switch-guide/user_guide/emummc/launching_cfw/">here</a> to launch Atmosphere.</li>
<li>Inject the Hekate payload using your favorite payload injector.<ul>
<li>If you have a modchipped Switch, place the Hekate payload on the root of your microSD card and rename it to payload.bin, reinsert your microSD card into your Switch and turn it on.</li>
</ul>
</li>
<li>Click on <code>Tools</code> on the top menu bar.</li>
<li>In the bottom left corner click on <code>Arch Bit • AutoRCM • Touch • Pkg1/2</code>.</li>
<li>Click on <code>Fix Archive bit</code> - this might take a while.</li>
<li>Press <code>Close</code> in the top right corner.</li>
<li>Press <code>Home</code> in the top menu bar to get back from where you started.</li>
<li>Follow the instructions at the Launching CFW page <a href="../user_guide/all/launching_cfw/">here</a> to launch Atmosphere.</li>
</ol>


Expand Down
2 changes: 1 addition & 1 deletion search/search_index.json

Large diffs are not rendered by default.

Binary file modified sitemap.xml.gz
Binary file not shown.
2 changes: 1 addition & 1 deletion user_guide/getting_started/index.html
Original file line number Diff line number Diff line change
Expand Up @@ -1821,7 +1821,7 @@ <h3 id="version-table"><strong>Version Table</strong><a class="headerlink" href=
</table>
<div class="admonition note">
<p class="admonition-title">About Mariko Switch models</p>
<p>All Mariko (V2) Switch models (<code>HAC-001(-01)</code>, <code>HDH-001</code>, <code>HEG-001</code>) are currently unhackable via software. If <strong>Modchip</strong> is listed as a method for your console model, then that means the device is currently unhackable without a hardware modification. If there are theoretical exploits that may lead to CFW or homebrew for that device, you also have the choice to "wait" for their release. These exploits may (and will likely) never launch and there is <strong>NO ETA</strong>, so what you choose to do is up to you. This guide assumes you have a functional modchip installation if you <em>do</em> have a Patched console.</p>
<p>All Mariko (V2) Switch models (<code>HAC-001(-01)</code>, <code>HDH-001</code>, <code>HEG-001</code>) are currently unhackable via software. If <strong>Modchip</strong> is listed as a method for your console model, then that means the device is currently unhackable without a hardware modification (modchip). If there are theoretical exploits that may lead to CFW or homebrew for that device, you also have the choice to "wait" for their release. These exploits may (and will likely) never launch and there is <strong>NO ETA</strong>, so what you choose to do is up to you. This guide assumes you have a functional modchip installation if you <em>do</em> have a Patched console.</p>
</div>
<h3 id="console-preparation"><strong>Console Preparation</strong><a class="headerlink" href="#console-preparation" title="Permanent link">&para;</a></h3>
<h4 id="important">Important<a class="headerlink" href="#important" title="Permanent link">&para;</a></h4>
Expand Down
Loading

0 comments on commit ec581b8

Please sign in to comment.