Advertisement
turkeli

Retard-proof Switch Hacking Guide (2019-08-25)

Aug 3rd, 2019
4,423
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 26.48 KB | None | 0 0
  1. Last updated 3rd Sep 2019
  2.  
  3. [Changelog]
  4. - 3rd Sep 2019
  5. * Updated instructions for installing Incognito, somebody reported that you need to launch fusee primary instead of Hekate CFW preset.
  6. - 25th Aug 2019
  7. * Added the section [Adding a Nintendo linked user account]
  8. - 4th Aug 2019
  9. * Cleanup and clarification of some sections, especially the intro according to feedback received.
  10. - 3rd Aug 2019
  11. * Initial release.
  12.  
  13. For non-retards: Use your own judgment when reading and applying any guide. If you have doubts about the validity
  14. of this (or any other) guide, cross check it with other guides on the internet and figure shit out for yourself.
  15.  
  16. [Intro and general information]
  17. - This guide is only for Switches with vulnerable hardware. Software exploits exist but are not covered here.
  18. * The hardware exploit is called fusée gelée, referred to as fusée in this guide.
  19. ~ See https://www.ktemkin.com/faq-fusee-gelee/ for a FAQ by the researcher who discovered it.
  20. * Fusée is a tethered, non-persistent exploit that can't be fixed without physical access to the device.
  21. ~ "Tethered, non-persistent" means that the custom bootloader is lost (non-persistent) when the device is completely
  22. turned off, requiring you to inject it again using a payload sender (tethered).
  23. ~ No coldboot solutions currently exist, but you can use AutoRCM to prevent the Switch from booting up without
  24. injecting a custom bootloader.
  25. * First patched Switches appeared around July 2018.
  26. * Check your serial at https://ismyswitchpatched.com/.
  27. * If your serial reports definitely patched, DO NOT use this guide and DO NOT update your firmware.
  28. ~ See https://switch.homebrew.guide/gettingstarted/choosinganexploit for software exploits.
  29. * If your serial reports unpatched or potentially unpatched, you may proceed to see if you can inject payloads.
  30. * Original thread for serial number ranges: https://gbatemp.net/threads/481215/
  31. - Firmware version does not matter if your Switch is fusée vulnerable. You can always smash
  32. the stack in RCM and completely take over the system.
  33. * There's one gotcha here if you ever plan on booting without a custom bootloader (i.e. not through RCM).
  34. Nintendo prevents downgrading the firmware by burning microscopic (non-replaceable) fuses inside the CPU
  35. (nearly) every time the firmware is updated. The number of fuses burnt determines the minimum version of the
  36. FW that Nintendo's bootloader will boot into, for example it expects 5 fuses to be burnt when you boot into
  37. 4.1. If less fuses are burnt at this point, it will burn as many as it needs to until 5 are burnt. If more than
  38. 5 fuses are burnt, it'll refuse to boot at all.
  39. * Knowing this, you may unknowingly render your NAND backup unusable by doing the following:
  40. ~ Make NAND backup of FW version 4.1, with 5 fuses burnt.
  41. ~ Update FW to 8.1.0 using ChoiDujourNX, which prevents burning fuses. Still 5 fuses burnt.
  42. ~ Disable AutoRCM and allow Nintendo's bootloader to load. At this point it will burn all of the fuses
  43. required by version 8.1.0.
  44. ~ Restore NAND backup of 4.1, thinking you can bring your Switch back to stock.
  45. ~ To your surprise, the device refuses to boot up.
  46. * Basically what this means is, if you care about ever returning your Switch back to its original state,
  47. you should keep AutoRCM enabled to avoid making this mistake.
  48. * Booting to stock using a custom bootloader such as Hekate will not burn your fuses.
  49.  
  50. [Physical stuff you will need]
  51. - An unpatched Switch. See the intro for checking your Switch. To be safe, charge it to 100% before proceeding.
  52. - Payload sender. Most likely you want this to be your computer, Windows/Linux/Mac/Android/iPhone (jailbroken) supported.
  53. You can also get a dedicated payload sending dongle if that's up your alley.
  54. - Micro SD(XC) card, minimum 64GB to properly back up your NAND.
  55. * Needs to be formatted either as FAT32 or exFAT. FAT32 is recommended.
  56. ~ FAT32 is the stabler option, but will not allow you to put files larger than ~4GB on the card.
  57. This usually isn't a problem unless you're storing media such as movies, as you can install
  58. large games using an USB connection.
  59. ~ exFAT allows for large files and may be very slightly faster (non-factor mostly), but is
  60. prone to corruption and can result in files getting lost. The Switch doesn't have exFAT drivers
  61. by default either, so unless you've updated your firmware to support it using either a game
  62. cartridge that contains the drivers or a system update, you will NOT be able to use an exFAT
  63. card until you do. So at the very least you will want to stick to FAT32 until you get your
  64. exFAT drivers sorted out.
  65. - Micro SD card reader. Required for formatting and partitioning your SD card. If your phone is
  66. rooted, you can use that, otherwise get a cheap USB reader.
  67. - USB-C cable for connecting your payload sender to your Switch. For a computer, get an USB-A
  68. to USB-C cable or an adapter.
  69. - A way to get your Switch into RCM mode. This is done by holding down Home + Vol Up while tapping
  70. the power button. But here's the catch, the Home button is NOT the one on your joy-con, but
  71. on the tablet itself. You can "hold it down" by grounding pin number 10 on the right joy-con rail.
  72. Ground can be found in pins 1 and 9 or, for example, the fan grill on top of the device.
  73. * There are a multitude of ways of getting your Switch into RCM mode. The easiest and safest way
  74. is to use a 3D printed "jig" you can insert into the joy-con rail.
  75. ~ One recommendation I've seen is https://switchjigs.com/
  76. ~ A dead easy alternative for a jig is to use a piece of tinfoil to bridge pins 9 and 10.
  77. Good demonstration, also introduces other methods: https://www.youtube.com/watch?v=3-UeB_enPrM&t=30s
  78. ~ For more methods, check https://gbatemp.net/threads/the-ultimate-list-of-mods-to-enter-rcm.502145/
  79.  
  80. [Glossary]
  81. - OFW: Official firmware, i.e. Nintendo supported.
  82. - CFW: Custom firmware, required for homebrewing.
  83. - NAND: Internal flash memory (i.e. file storage). Also also referred to as "sysNAND" to disambiguate with emuNAND.
  84. * Used interchangeably with eMMC. eMMC consists of the flash memory and its controller.
  85. - emuNAND: Emulated version of your sysNAND, running off of the SD card. Using this will leave your sysNAND
  86. untouched.
  87. * Mostly useful for quickly switching between CFW and OFW without having to restore backups.
  88. ~ Of course you can fuck around with your sysNAND and boot to stock without restoring the NAND backup,
  89. but this will most likely get you banned.
  90. * It's your choice if you want to use emuNAND. Be warned that using a shitty SD card will slow down your
  91. system. If you're not interested in playing games online (for which you want clean sysNAND), you can skip it.
  92. - emuMMC: Name of the implementation currently used for emulating NAND.
  93.  
  94. [Software used]
  95. - This is an overview of the most important software you'll be using.
  96. - You don't need to download most of these separately. See the next section for download instructions.
  97. - Kosmos: Compilation of almost everything needed to get your custom firmware up and running, and some extras.
  98. Made by team AtlasNX, who also host a homebrew guide at https://switch.homebrew.guide/.
  99. * Source: https://github.com/AtlasNX/Kosmos
  100. * Version used in guide: v13.0.1
  101. - Non-exhaustive list of essential homebrew components and tools:
  102. * Hekate: Open source custom bootloader. A bootloader instructs the hardware of your device on where to
  103. find the files necessary for bringing the system up, and also works as a security checkpoint.
  104. For example, if the bootloader detects that the firmware isn't properly signed, it can refuse
  105. to boot up the system. Required to boot into custom firmware.
  106. ~ Source: https://github.com/Joonie86/hekate
  107. ~ Version used in guide: v5.0.1pre6
  108. * TegraRcmGUI: Simple graphical user interface for TegraRcmSmash, which is a re-implementation of
  109. the original fusée launcher. Used to send payloads to your Switch in RCM mode.
  110. ~ Windows only, for other platforms there are alternatives in the "Software downloads" section.
  111. ~ Source: https://github.com/eliboa/TegraRcmGUI
  112. ~ Version used in guide: v2.6
  113. * Lockpick_RCM : Payload for dumping the encryption keys of your device. You will want to back these up.
  114. ~ Source: https://github.com/shchmue/Lockpick_RCM
  115. ~ Version used in guide: v1.3
  116. * Atmosphère: Open source custom firmware. Firmware works on the lowest levels of your device,
  117. bridging the gap between hardware and software. Required for running custom software.
  118. ~ Source: https://github.com/Atmosphere-NX/Atmosphere
  119. ~ Version used in guide: v0.9.2
  120. * Homebrew Loader: Facilitates launching custom NROs. NROs are Nintendo's version of executable files.
  121. ~ Source: https://github.com/switchbrew/nx-hbloader
  122. * Homebrew Menu: Frontend for launching custom NROs. Provides a nice interface for Homebrew Loader.
  123. ~ Source: https://github.com/switchbrew/nx-hbmenu
  124. - Essential tools for piracy:
  125. * Goldleaf: Multipurpose tool for homebrewing. Includes utilities such as a file manager (both for your
  126. SD card and your internal memory) and a manager for listing, installing, removing and exporting
  127. content (i.e. games). You will be using this to install your NSPs (Nintendo Submission Package, an
  128. archival format containing full game data). This is basically equivalent to downloading a game from the eShop
  129. and installing it to your system. NSPs can be installed either to system memory or an SD card.
  130. ~ NSPs can be installed from your SD card, but unless your SD card is in exFAT format, you will be unable
  131. to install anything larger than ~4GB using this method. The preferred method is to use GoldTree.
  132. ~ Source: https://github.com/XorTroll/Goldleaf
  133. ~ Version used in guide: v0.5 or v0.6
  134. * GoldTree: Windows companion executable for Goldleaf. Needs to be running on your computer for Goldleaf's
  135. PC browser to work. Using the PC browser you can install NSPs directly from your computer via USB.
  136. ~ PC browser is new in v0.6, v0.5 uses USB installations which are the same thing but the usage is a bit different.
  137. ~ Source: https://github.com/XorTroll/Goldleaf
  138.  
  139. [Software downloads]
  140. 1. Easy compilation: https://www.sdsetup.com/console?switch
  141. * You should go through everything available here to get an overview of what you can get.
  142. * For a piracy homebrew setup, use this: https://www.sdsetup.com/console?switch#atmosphere;atmos_musthave;atmos_bootlogo;kosmos_toolkit;kosmos_updater;atmos_sys-clk;appstorenx;hbmenu;goldleaf;hekate;lockpick_rcm;tegrarcmgui;goldtree;atmos_sigpatch;
  143. ~ Includes everything needed to run custom firmware and install NSPs.
  144. ~ Does not include any emulators.
  145. * You can also just click "Kosmos Defaults" at the top of the page to get some additional shit you probably won't use.
  146. ~ Also check "TegraRcmGUI" if on Windows and without a payload injector.
  147. ~ Also check "GoldTree" for USB installations.
  148. 2. Payload sender if not using Windows:
  149. * Android phone: https://github.com/DavidBuchanan314/NXLoader/releases
  150. * Mac OS/iPhone (Jailbroken): https://mologie.github.io/nxboot/
  151. * Linux PC: https://github.com/Cease-and-DeSwitch/fusee-launcher
  152. 3. (Optional) HacDiskMount: https://switchtools.sshnuke.net
  153. * Used for verifying your NAND backup. Recommended.
  154.  
  155. [Downloads for firmware update]
  156. - Skip these if not updating firmware.
  157. 1. OFW files: https://darthsternie.net/switch-firmwares/
  158. * There's no real downside to updating a patched Switch's firmware as long as you don't boot without RCM.
  159. * Current official firmware is version 8.1.0 and is supported. Once a newer firmware has been released,
  160. make sure all of the homebrew tools are updated to support it before updating to it.
  161. 2. ChoiDujourNX: https://switchtools.sshnuke.net
  162. * Used for updating your OFW without burning fuses.
  163.  
  164. [Setting up]
  165. - If you're not sure that your Switch supports the RCM exploit, you can skip this for now and come back once you've verified it.
  166. 1. Insert your SD card into your reader.
  167. 2. Decide whether or not you want to use emuNAND.
  168. * If not, simply format the card to FAT32 (unless you have exFAT drivers and want to use it).
  169. ~ Windows usually won't allow you to do this, you will need dedicated software for it. Check the FAQ.
  170. * If yes, partition your SD card into two FAT32 partitions.
  171. ~ This is outside the scope of this guide. See e.g. https://nh-server.github.io/switch-guide/user_guide/emummc/partitioning_sd/
  172. * Note that if you decide to use emuNAND, then every time you launch CFW from Hekate, you should select "CFW (emuNAND)".
  173. 3. Extract the homebrew compilation you downloaded. It should contain three folders:
  174. - payloads: Injectable using your payload sender.
  175. - pc: Any additional PC tools you selected (e.g. TegraRcmGUI, GoldTree).
  176. - android: Any Android tools you selected.
  177. - sd: Everything you need to put on your SD card, includes CWF and homebrew programs.
  178. 4. Move the *contents* of the sd folder to your SD card's root.
  179.  
  180. [Setup firmware update]
  181. - Skip these if not updating firmware.
  182. 1. Extract ChoiDujourNX.nro into the switch folder on the SD card.
  183. 2. Extract the firmware files you downloaded, create a folder on the SD card and copy them there.
  184.  
  185. [First time RCM]
  186. 1. Setup the payload sending program. For Windows:
  187. - Launch TegraRcmGUI.exe from the pc folder you extracted.
  188. - Go to "Settings" tab, click "Install driver" to install APX drivers required for the USB connection to work.
  189. 2. Delete your Switch's Wi-Fi settings and power it off completely. Insert your SD card.
  190. 3. Remove right joy-con and insert jig into the rail (or use another method).
  191. 4. Hold down the Volume Up button and *tap* the power button.
  192. - If nothing happens (screen stays black), you've successfully booted into RCM mode. You can remove your jig.
  193. - If your Switch starts up normally, turn it off and try again. This means pin 10 wasn't properly grounded.
  194. 5. Plug in Switch using USB-C cable.
  195. - TegraRcmGUI should indicate that an RCM device is detected.
  196. 6. If you aren't sure that your Switch is vulnerable, try to inject this test payload: https://drive.google.com/open?id=1Bzku9r9GJ4F_3BoCBa-9QsPUav2-_2V4
  197. - It will print some text on your Switch. If not, it's NOT vulnerable and you don't want to continue using this guide.
  198. - This will shutdown the device, requiring you to repeat steps 3 and 4 to get back into RCM.
  199. 7. Make a NAND backup and enable AutoRCM.
  200. - Inject "hekate.bin" (actual filename may differ) from the payloads folder.
  201. - Select "Tools" at the top of the screen.
  202. - Select "Backup eMMC".
  203. - Select "eMMC BOOT0 & BOOT1", then wait about half a minute until it says "Finished and verified!"
  204. - Close the screen, then select "eMMC RAW GPP". This will be nearly 30GB so it'll take a while.
  205. - Once finished, go back to the "Tools" menu and on the bottom select "Archive bit • AutoRCM".
  206. - Turn on AutoRCM. This allows you to enter RCM without having to use a jig and is highly recommended
  207. to avoid accidentally booting into OFW with a dirty sysNAND. Reversing AutoRCM is as simple as tapping
  208. the button again, so there's no risk.
  209. - Go back to the "Home" tab and select "Reboot > RCM" to get back to RCM mode.
  210. - Eject SD card and insert it into PC.
  211. - Copy the backup folder from the SD card to your PC. Name it "clean-backup-<firmware.version>"
  212. or something similar so you'll know what your original firmware was.
  213. - Delete the backup folder on the SD card.
  214. - Insert SD card back into your Switch.
  215. 8. (Optional) Verify your backup.
  216. - Open HacDiskMount -> File -> Open -> find your backup folder -> rawnand.bin.
  217. - If it loads without errors it should be good.
  218. 9. Inject "Lockpick_RCM.bin" from the payloads folder.
  219. - This backs up all of your encryption keys, including BIS keys which are useful in case your NAND backup gets
  220. lost or corrupted, as they can be used to reinstall any firmware version manually.
  221. - Press the power button to shutdown your Switch.
  222. - Eject SD card and insert it into PC.
  223. - Copy the /switch/prod.keys file to the same location where you copied your backup folder. Keep these together.
  224. 10. (Optional) Make backups of your backups in an external drive, a cloud service, where ever.
  225. - The NAND backup is your ticket to restoring your Switch to its original state before any homebrewing.
  226. 11. Insert SD card in Switch and inject Hekate again.
  227. 12. If you want to use emuNAND, set it up now. This is outside the scope of this guide, so google around.
  228. 13. Select Launch -> CFW (sysNAND or emuNAND) in Hekate to boot into Horizon OS.
  229. 14. Test the CFW: open up the Homebrew Menu by holding R while opening the Album.
  230.  
  231. [Updating firmware]
  232. - Skip this if you're not updating your firmware.
  233. 1. Open Homebrew Menu (hold R while opening the Album).
  234. 2. Select ChoiDujourNX.
  235. 3. Navigate to the directory where you placed the firmware files and tap the "Choose" button.
  236. 4. Choose the exFAT option, once it's done tap the Reboot button and wait for it to reboot.
  237. - exFAT simply includes the exFAT drivers. It's never a bad idea to install these even if you're using FAT32 right now.
  238. 5. Your console should be in RCM mode now, you can inject Hekate again and select Launch -> CFW.
  239.  
  240. Note: DO NOT disable AutoRCM if you update. Booting into OFW will burn your fuses, rendering you unable
  241. to restore your NAND backup if it was on a previous firmware version.
  242.  
  243. [Additional ban protection]
  244. - This clears the identity of your console, including its serial number.
  245. - The theory goes that Nintendo can't ban your Switch when they can't get your S/N.
  246. 1. Get into RCM, insert SD card into PC.
  247. 2. Download Incognito: https://github.com/blawar/incognito/releases
  248. 3. Put the NRO into the switch folder on the SD card.
  249. 4. Download ams-mitm: https://gbatemp.net/threads/a-custom-sysmodule-for-atmosphere-that-allows-writing-to-prodinfo.541609/
  250. - Atmosphere 0.92 blocks attempts to read/write prodinfo for security reasons, requiring you to temporarily
  251. bypass this security feature by using a sysmodule.
  252. 5. Extract "ams_mitm_8.1.0.zip" to your PC.
  253. 6. Move the file "ams_mitm.kip" into the "atmosphere/kips" folder. If the folder "kips" doesn't exist, create it.
  254. 7. Create a new folder in "atmosphere" called "flags".
  255. 8. Create an empty file called "hbl_cal_read.flag" in this folder and plug your SD card back into your Switch.
  256. 9. Inject Hekate, go into "Paylods" and select "fusee_primary.bin".
  257. 10. Open Homebrew menu (hold R while opening Album).
  258. 11. Select Incognito, press A to install it.
  259. 12. Turn off device, insert SD card into PC, copy prodinfo.bin to the same place where you keep your NAND backup.
  260. 13. On the SD card, delete everything you created in steps 6-8, delete incognito.nro, delete prodinfo.bin.
  261. 14. You can check that it worked by going to System Settings -> System -> Serial Numbers, your console S/N should be empty.
  262.  
  263. [USB installing NSPs]
  264. - You can install NSP files in any order (e.g. update before game itself).
  265. 1. Download the NSPs you want (for sources, see other pastebins).
  266. 2. Plug in Switch to PC using USB-C cable.
  267. 3. Install USB drivers (libusbK):
  268. - This just needs to be done once.
  269. - Download Zadig from https://zadig.akeo.ie/
  270. - Launch it, select Nintendo Switch from the dropdown menu.
  271. - Select libusbK as the driver, click install, wait for it to finish.
  272. 4. Figure out your Goldleaf version by launching it in Homebrew Menu.
  273. 5. For Goldleaf v0.5, do this:
  274. - Change your Switch's sleep settings so it doesn't interfere with installations, as they can take a while.
  275. - Open Homebrew Menu -> Goldleaf on the Switch.
  276. - Select USB installation.
  277. - Launch GoldTree on the PC (if you downloaded the compilation, it will be in the pc folder).
  278. - In the open file popup, select your NSP.
  279. - Follow the installation instructions on the Switch, do NOT press anything while installing.
  280. 6. For Goldleaf v0.6, do this:
  281. - v0.6 automatically keeps your device awake during installations, no need to modify settings.
  282. - Launch GoldTree on the PC (in the pc folder you extracted earlier).
  283. - Open Homebrew Menu -> Goldleaf on the Switch.
  284. - Select "Explore content -> Remote PC (via USB)".
  285. - Open folders with A, go back with B, Y for context sensitive options.
  286. - Find the NSP you want to install, press A, select "Install", follow instructions, do NOT press anything while installing.
  287. - If you want to install all NSPs in a folder, select the folder, press Y, select "Extra options -> Install all NSPs".
  288. ~ The installation prompt will still be shown for each NSP.
  289.  
  290. [Using internet while blocking Nintendo servers]
  291. - You can use a custom DNS for this: https://gbatemp.net/threads/516234/
  292. * Please note that there's inherent trust required for the person/people hosting the DNS servers,
  293. as they can not only monitor what URLs you're requesting but also redirect you maliciously.
  294. To safely use this solution, verify the source code and host the server yourself. Otherwise
  295. you'll just have to trust some random dudes on the internet.
  296.  
  297. [Adding a Nintendo linked user account]
  298. - This section is Windows specific and assumes you're using TegraRcmSmash.
  299. - Some games these days require a Nintendo account linked to your user. You also won't be able to
  300. view your play activity in your profile unless the user is linked.
  301. - You do not have to be/go online to play these games, a linked account is enough.
  302. - It's best to set this up as soon as you've hacked your Switch as it will override your current
  303. user account, meaning you'll lose your save games and you'll have to backup/restore them
  304. manually to the new account.
  305. - You'll need the prod.keys files you dumped earlier using Lockpick_RCM. If you didn't do it then,
  306. you'll have to do it now.
  307. - This assumes you have AutoRCM enabled as it requires you to inject payloads twice. If you don't,
  308. enter RCM manually each time.
  309. - If you've already played on your user, make backups of every save game you care about using
  310. Checkpoint: https://github.com/FlagBrew/Checkpoint/releases
  311. 1. Boot your Switch to RCM mode, remove SD card, don't inject anything.
  312. 2. Download a linked account from here: https://switch.customfw.xyz/files/8000000000000010
  313. * For ease of use, download it to the folder with your prod.keys files.
  314. 3. Download the latest version of hactoolnet from here: https://github.com/Thealexbarney/LibHac/releases/
  315. * For ease of use, download it to the folder with your prod.keys files.
  316. 4. Download memloader from here: https://switchtools.sshnuke.net/
  317. 5. If you didn't already, download HacDiskMount from here: https://switchtools.sshnuke.net/
  318. 6. Use hactoolnet to sign the account file using your keys:
  319. * Open command prompt/PowerShell in the folder where hactoolnet is located in.
  320. ~ You can easily open PowerShell in Explorer by shift-right clicking the folder background
  321. and selecting "Open PowerShell window here".
  322. * Run the following command: .\hactoolnet.exe -k .\prod.keys -t save .\8000000000000010 --sign
  323. ~ Adjust paths if your prod.keys and save file are in a different folder.
  324. * You'll see a few "Failed to match key" lines and information about the save file if
  325. it succeeded. Check the modification timestamp on the file 8000000000000010 to verify it was changed.
  326. 7. Unzip memloader.zip, copy the contents of the sample folder to the *root* if your SD card.
  327. 8. Insert SD card back into your Switch, open TegraRcmSmash, select memloader.bin as the payload and inject it.
  328. 9. Navigate using vol+ and vol- on your Switch, select "ums_emmc.ini", confirm using power button.
  329. The screen will go blank.
  330. 10. Connect your Switch to your PC.
  331. 11. Run HacDiskMount.exe with administrator privileges (right click, run as administrator).
  332. 12. Choose "File > Open Physical", select "UMS Linux Disk 0 (29.121GiB)"
  333. 13. From the list of partitions that opened, double click on SYSTEM.
  334. 14. Open your prod.keys file and look for the line beginning with "bis_key_02".
  335. 15. Take the first 32 characters of the hash after the equals sign and insert it in the "Crypto" input
  336. of HacDiskMount. Take the remaining 32 characters and insert them in the "Tweak" input.
  337. 16. Click the "Test" button, you'll get a green "OK!" if you did it correctly.
  338. 17. In the section labeled "Virtual drive", check if it says "Driver not installed", in which case click "Install".
  339. 18. Once the section says "Driver installed, service is running", select an unused drive letter and check the
  340. box "Passthrough zeroes", then click "Mount".
  341. 19. Press Win+E to open explorer, you should see the drive letter you selected. Open it.
  342. 20. Go to the "save" folder, find the file named 8000000000000010 and take a backup of it.
  343. 21. Overwrite the 8000000000000010 file in the "save" folder with the file we signed earlier.
  344. 22. Click "Unmount" in HacDiskMount to unmount the drive.
  345. 23. Hold the power button for a while to turn off the console, tap it to get into RCM mode.
  346. 24. Inject Hekate and boot into CFW, go to your profile to verify that it's linked.
  347. 25. Restore savegame backups using Checkpoint if you have them.
  348.  
  349. [General Use]
  350. - It's recommended to keep your switch in sleep mode instead of powering it off. Every time you power
  351. off you have to inject Hekate using a payload sender to boot back into CFW.
  352. - To get back into Hekate from Horizon without having to inject the payload again, open
  353. Homebrew Menu -> Kosmos Toolbox and select "Reboot to Hekate" -> "Reboot now!".
  354.  
  355. [FAQ]
  356. Q: Will I get banned if I follow this guide?
  357. A: Not necessarily, but going online with CFW/NSPs will likely flag your switch for a ban.
  358. If you want to go online and not be banned, restore the NAND backup you made at the start of this
  359. guide to wipe all traces of CFW and NSPs. If you're using emuNAND and are sure you haven't touched
  360. sysNAND, you won't need to restore backups when using OFW.
  361.  
  362. Q: Isn't AutoRCM dangerous? What if my battery is completely dead?
  363. A: No. AutoRCM is easily reversible. If your battery is completely dead, you'll need to charge it
  364. for several hours due to RCM having a slow charge speed. You just need enough of a charge to boot into Hekate.
  365.  
  366. Q: NSP files aren't installing or throwing me errors! What do?
  367. A: First check if you have enough space on your SD. If you do, try renaming the filename of the NSP to something shorter
  368. and without characters such as "é". If you've just updated your firmware, make sure you have the correct
  369. sigpatches.
  370.  
  371. Q: I keep getting prompts to update my joycons, is this safe?
  372. A: Yes, it's safe.
  373.  
  374. Q: I can't format my SD card to FAT32, what do I do?
  375. A: Use this program: http://www.ridgecrop.demon.co.uk/index.htm?guiformat.htm
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement