Nintendo Switch Trinket Guide - Revision history

Ha1vorsen: /* Updating Horizon (Advanced Method) */

2022-04-20T19:15:33Z

Updating Horizon (Advanced Method)

← Older revision		Revision as of 14:15, 20 April 2022
Line 33:		Line 33:
	''If'' you require the update immediately, or you accidentally updated -- disable AutoRCM and boot into stock, in the meantime. Custom firmware will no longer work on the ''updated'' NAND, but if you have an emuMMC on an older software version that atmosphère supports, it will continue to boot custom firmware without issue.		''If'' you require the update immediately, or you accidentally updated -- disable AutoRCM and boot into stock, in the meantime. Custom firmware will no longer work on the ''updated'' NAND, but if you have an emuMMC on an older software version that atmosphère supports, it will continue to boot custom firmware without issue.

	For clarification, using custom firmware while online is ''not'' and never has been a bannable offense. Piracy~~, cheating~~, and creating unsafe environments online (i.e. custom profile pictures) ''are''. As long as you avoid these, then there is no issue with permanently booting into custom firmware and swapping between emuMMC and stock via the modchip. This is the configuration I have always used, and I have not used a stock firmware ever since 2019.		For clarification, using custom firmware while online is ''not'' and never has been a bannable offense. Piracy, and creating unsafe environments online (i.e. cheating, custom profile pictures) ''are''. As long as you avoid these, then there is no issue with permanently booting into custom firmware and swapping between emuMMC and stock via the modchip. This is the configuration I have always used, and I have not used a stock firmware ever since 2019.

	=== Updating RCMX86 software ===		=== Updating RCMX86 software ===

Ha1vorsen at 19:14, 20 April 2022

2022-04-20T19:14:00Z

← Older revision		Revision as of 14:14, 20 April 2022
Line 3:		Line 3:
	The modchip consists of a Trinket M0-based device, usually the [https://github.com/euclala/RCM-X86 RCMX86], to serve as an auto-injector for RCM-vulnerable devices.		The modchip consists of a Trinket M0-based device, usually the [https://github.com/euclala/RCM-X86 RCMX86], to serve as an auto-injector for RCM-vulnerable devices.

	Generally, a modchip will inject a small prebootloader payload from onboard storage into the console, which then chainloads a payload from the microSD card. The software I install to the modchip to preform this task is [https://wiki.halcove.com/files/RCMX86.UF2 fusee-suite]. Its functions are documented below. These modchips are fully unrelated to [[Team Xecuter]] modchips for [[Nintendo Switch#Mariko (T214)\|Mariko]] units.		Generally, a modchip will inject a small prebootloader payload from onboard storage into the console, which then chainloads a payload from the microSD card. The software I install to the modchip to preform this task is [https://wiki.halcove.com/files/RCMX86.UF2 fusee-suite]. ([https://github.com/mattytrog/FUSEE_SUITE GitHub]) Its functions are documented below. These modchips are fully unrelated to [[Team Xecuter]] modchips for [[Nintendo Switch#Mariko (T214)\|Mariko]] units.

	The original repository for fusee-suite can be found on GitHub.		The original repository for fusee-suite can be found on GitHub.

	I whipped up a generic usage guide for users ~~and installers~~ here.		I whipped up a generic usage guide for users here.

	== Internal RCM-X86 usage guide ==		== Internal RCM-X86 usage guide ==

Ha1vorsen at 12:28, 23 March 2022

2022-03-23T12:28:09Z

← Older revision		Revision as of 07:28, 23 March 2022
Line 3:		Line 3:
	The modchip consists of a Trinket M0-based device, usually the [https://github.com/euclala/RCM-X86 RCMX86], to serve as an auto-injector for RCM-vulnerable devices.		The modchip consists of a Trinket M0-based device, usually the [https://github.com/euclala/RCM-X86 RCMX86], to serve as an auto-injector for RCM-vulnerable devices.

	Generally, a modchip will inject a small prebootloader payload from onboard storage into the console, which then chainloads a payload from the microSD card. The software I install to the modchip to preform this task is [https://wiki.halcove.com/files/RCMX86.UF2 fusee-suite]. Its functions are documented below. These modchips are fully unrelated to Team Xecuter modchips for Mariko units.		Generally, a modchip will inject a small prebootloader payload from onboard storage into the console, which then chainloads a payload from the microSD card. The software I install to the modchip to preform this task is [https://wiki.halcove.com/files/RCMX86.UF2 fusee-suite]. Its functions are documented below. These modchips are fully unrelated to [[Team Xecuter]] modchips for [[Nintendo Switch#Mariko (T214)\|Mariko]] units.

	The original repository for fusee-suite can be found on GitHub.		The original repository for fusee-suite can be found on GitHub.

Ha1vorsen at 12:27, 23 March 2022

2022-03-23T12:27:19Z

← Older revision		Revision as of 07:27, 23 March 2022
Line 3:		Line 3:
	The modchip consists of a Trinket M0-based device, usually the [https://github.com/euclala/RCM-X86 RCMX86], to serve as an auto-injector for RCM-vulnerable devices.		The modchip consists of a Trinket M0-based device, usually the [https://github.com/euclala/RCM-X86 RCMX86], to serve as an auto-injector for RCM-vulnerable devices.

	Generally, a modchip will inject a small prebootloader payload from onboard storage into the console, which then chainloads a payload from the microSD card. The software I install to the modchip to preform this task is [https://wiki.halcove.com/files/RCMX86.UF2 fusee-suite]. Its functions are documented below.		Generally, a modchip will inject a small prebootloader payload from onboard storage into the console, which then chainloads a payload from the microSD card. The software I install to the modchip to preform this task is [https://wiki.halcove.com/files/RCMX86.UF2 fusee-suite]. Its functions are documented below. These modchips are fully unrelated to Team Xecuter modchips for Mariko units.

			The original repository for fusee-suite can be found on GitHub.

	I whipped up a generic usage guide for users and installers here.		I whipped up a generic usage guide for users and installers here.

Ha1vorsen at 12:25, 23 March 2022

2022-03-23T12:25:52Z

← Older revision		Revision as of 07:25, 23 March 2022
Line 1:		Line 1:
	I completed an install of a modchip on about four different consoles, some of which I do not own.		I completed an install of a modchip on about four different consoles, some of which I do not own. The installation went fine on all of them!

	The modchip consists of a Trinket M0-based device, usually the [https://github.com/euclala/RCM-X86 RCMX86], to serve as an auto-injector for RCM-vulnerable devices.		The modchip consists of a Trinket M0-based device, usually the [https://github.com/euclala/RCM-X86 RCMX86], to serve as an auto-injector for RCM-vulnerable devices.

Ha1vorsen at 12:25, 23 March 2022

2022-03-23T12:25:05Z

← Older revision		Revision as of 07:25, 23 March 2022
Line 3:		Line 3:
	The modchip consists of a Trinket M0-based device, usually the [https://github.com/euclala/RCM-X86 RCMX86], to serve as an auto-injector for RCM-vulnerable devices.		The modchip consists of a Trinket M0-based device, usually the [https://github.com/euclala/RCM-X86 RCMX86], to serve as an auto-injector for RCM-vulnerable devices.

	Generally, ~~the~~ modchip will inject a payload to the console, which then chainloads a payload from the microSD card. The software I install to preform this task is [https://wiki.halcove.com/files/RCMX86.UF2 fusee-suite]~~, and its~~ functions ~~will be~~ documented below.		Generally, a modchip will inject a small prebootloader payload from onboard storage into the console, which then chainloads a payload from the microSD card. The software I install to the modchip to preform this task is [https://wiki.halcove.com/files/RCMX86.UF2 fusee-suite]. Its functions are documented below.

	I whipped up a generic usage guide for users and installers here.		I whipped up a generic usage guide for users and installers here.
Line 23:		Line 23:

	=== Updating Horizon (Advanced Method) ===		=== Updating Horizon (Advanced Method) ===
	If you'~~ve enabled~~ AutoRCM, ~~you now require~~ your console ~~to have a microSD to boot~~. If ~~your console does not have~~ a ~~microSD~~, you will ~~not~~ be able to ~~chainload~~ into ~~Hekate to boot neither~~ stock ~~firmware, nor custom firmware~~.		If you ''do not'' use AutoRCM, then this mod does not interrupt the normal usage of your console in any way. You can ignore the following lines safely. If a new update is released that atmosphère doesn't support, you will still be able to boot into stock just like any other Nintendo Switch.

	~~You~~ will ~~no longer~~ be able to boot ~~into a fully~~ stock ~~configuration until AutoRCM is disabled. ''This is generally not an issue unless Nintendo releases an update that atmosphère cannot boot~~.''		If you have enabled AutoRCM, you now require your console to have a microSD to boot at all. If your console does not have a microSD, you will not be able to chainload into Hekate to boot neither stock firmware, nor custom firmware.

	In ~~this~~ circumstance, ''you ~~need to~~ postpone the update~~'' ''~~until a new release of atmosphère~~'' ''~~is available to support it.''		You will no longer be able to boot into a truly stock configuration until AutoRCM is disabled. ''This is generally not an issue unless Nintendo releases an update that atmosphère cannot boot.'' In that circumstance, you should postpone the update until a new release of atmosphère is available to support it.

	If you require the update immediately -- disable AutoRCM and boot into stock, in the meantime. Custom firmware will no longer work on the ''updated'' NAND, but if you have an emuMMC on an older software version ~~(one~~ that atmosphère supports), it will continue to boot custom firmware.		''If'' you require the update immediately, or you accidentally updated -- disable AutoRCM and boot into stock, in the meantime. Custom firmware will no longer work on the ''updated'' NAND, but if you have an emuMMC on an older software version that atmosphère supports, it will continue to boot custom firmware without issue.

	For clarification, using custom firmware while online is ''not'' a bannable offense. Piracy, cheating, and creating unsafe environments online are. As long as you avoid these ~~(custom profile images also are filed under "creating unsafe environments online" as users have created NSFW profile art)~~, then there is no issue with permanently booting into custom firmware and swapping between emuMMC and stock via the modchip. This is the configuration I have always used.		For clarification, using custom firmware while online is ''not'' and never has been a bannable offense. Piracy, cheating, and creating unsafe environments online (i.e. custom profile pictures) ''are''. As long as you avoid these, then there is no issue with permanently booting into custom firmware and swapping between emuMMC and stock via the modchip. This is the configuration I have always used, and I have not used a stock firmware ever since 2019.

	~~If you ''do not'' use AutoRCM~~, ~~then this mod does~~ not ~~interrupt the normal usage of your console in any way~~.

	=== Updating RCMX86 software ===		=== Updating RCMX86 software ===
Line 79:		Line 77:
	== Troubleshooting ==		== Troubleshooting ==

	* Nintendo Switch does not boot		* I accidentally updated and my Switch receives an error when trying to boot! Disable autoRCM as mentioned in [[Nintendo Switch Trinket Guide#Updating Horizon (Advanced Method)\|this paragraph]].
			*Nintendo Switch does not boot and has a black screen

	The modchip is likely not attached correctly ~~with~~ AutoRCM enabled. Check one of the following straps: 3.3V, GND, or DATA+/DATA-.		The modchip is likely not attached correctly, while AutoRCM is enabled. Check one of the following straps: 3.3V, GND, or DATA+/DATA-.

	* Nintendo Switch boots stock, but not RCM		* Nintendo Switch boots stock, but not into RCM payloads

	One of the DATA+/- are not connected.		One of the DATA+/- are not connected.
Line 89:		Line 88:
	Alternatively, the modchip could be short-circuiting with the metal RF shield on the back of Nintendo Switch. Please make sure to properly shield the top of the modchip and the wires connected to it.		Alternatively, the modchip could be short-circuiting with the metal RF shield on the back of Nintendo Switch. Please make sure to properly shield the top of the modchip and the wires connected to it.

	* Nintendo Switch boots stock, ~~and only enters RCM without automatically injecting anything~~		Alternatively, the 3.3V line is not connected.

	~~The~~ 3.3V line is not connected.

	* Nintendo Switch does not enter RCM!		* Nintendo Switch does not enter RCM!

	Has the hardware been modified recently? Please check the Joy-Con's rails, both the inside and the outside. The outer parts may have dust or debris covering the metal contacts. If not, the user's jig may also be dirty. If both of these are correct, then it's likely that the ribbon cable of the Joy-Con slot may be slightly torn, making RCM entry impossible without removing the NAND.		Has the hardware been modified recently? Please check the Joy-Con's rails, both the inside and the outside. The outer parts may have dust or debris covering the metal contacts. If not, the user's jig may also be dirty. If both of these are correct, then it's likely that the ribbon cable of the Joy-Con slot may be slightly torn, making RCM entry impossible without removing the NAND.

Ha1vorsen: /* fusee-suite Settings */

2022-03-23T12:09:16Z

fusee-suite Settings

← Older revision		Revision as of 07:09, 23 March 2022
Line 51:		Line 51:
	Detects and manages payload slots in every valid payload directory (payload''x''.bin / bootloader/update.bin)		Detects and manages payload slots in every valid payload directory (payload''x''.bin / bootloader/update.bin)

	* -----Backup/Restore-----		<nowiki>-----</nowiki>Backup/Restore-----

	Options to back up and restore the console's raw physical NAND, specific partitions (SYS/USER/PRODINFO/BOOT0/BOOT1), or just BOOT0/BOOT1.		Options to back up and restore the console's raw physical NAND, specific partitions (SYS/USER/PRODINFO/BOOT0/BOOT1), or just BOOT0/BOOT1.
Line 69:		Line 69:
	<nowiki>-----</nowiki>Battery Calibration-----		<nowiki>-----</nowiki>Battery Calibration-----

	Accounts for and corrects uncalibrated batteries. Please also check the calibration FAQ. '''This occasionally requires the users to physically disconnect and reconnect the battery for the console to turn on once this action has been taken.'''		Accounts for and corrects uncalibrated batteries. Please also check the calibration FAQ.

			'''This occasionally requires the users to physically disconnect and reconnect the battery for the console to turn on once this action has been taken.'''

	<nowiki>-----</nowiki>Power-----		<nowiki>-----</nowiki>Power-----

Ha1vorsen at 12:08, 23 March 2022

2022-03-23T12:08:11Z

← Older revision		Revision as of 07:08, 23 March 2022
Line 3:		Line 3:
	The modchip consists of a Trinket M0-based device, usually the [https://github.com/euclala/RCM-X86 RCMX86], to serve as an auto-injector for RCM-vulnerable devices.		The modchip consists of a Trinket M0-based device, usually the [https://github.com/euclala/RCM-X86 RCMX86], to serve as an auto-injector for RCM-vulnerable devices.

	Generally, the modchip will inject a payload to the console, which then chainloads a payload from the microSD card. The software I ~~use~~ is [https://wiki.halcove.com/files/RCMX86.UF2 fusee-suite].		Generally, the modchip will inject a payload to the console, which then chainloads a payload from the microSD card. The software I install to preform this task is [https://wiki.halcove.com/files/RCMX86.UF2 fusee-suite], and its functions will be documented below.

	I whipped up a generic usage guide for users and installers here.		I whipped up a generic usage guide for users and installers here.
Line 38:		Line 38:
	This requires physical access to the modchip. This is more of a guide for the installer than the end-user.		This requires physical access to the modchip. This is more of a guide for the installer than the end-user.

	Once a SAMD21 update payload is sent via a PC, press the reset button on the modchip twice, until a Windows Explorer window appears on your desktop. Then drag the software's UF2 file to the root of the modchip, at which point the modchip will reset and start running the new software automatically.		Once a [https://wiki.halcove.com/files/Samd21Update.bin SAMD21 update payload] is sent via a PC, press the reset button on the modchip twice, until a Windows Explorer window appears on your desktop. Then drag the software's UF2 file to the root of the modchip, at which point the modchip will reset and start running the new software automatically.

	=== fusee-suite Settings ===		=== fusee-suite Settings ===

Ha1vorsen at 12:06, 23 March 2022

2022-03-23T12:06:37Z

← Older revision		Revision as of 07:06, 23 March 2022
Line 3:		Line 3:
	The modchip consists of a Trinket M0-based device, usually the [https://github.com/euclala/RCM-X86 RCMX86], to serve as an auto-injector for RCM-vulnerable devices.		The modchip consists of a Trinket M0-based device, usually the [https://github.com/euclala/RCM-X86 RCMX86], to serve as an auto-injector for RCM-vulnerable devices.

	Generally, the modchip will inject a payload to the console, which then chainloads a payload from the microSD card. The software I use is [https://halcove.com/files/RCMX86.UF2 fusee-suite].		Generally, the modchip will inject a payload to the console, which then chainloads a payload from the microSD card. The software I use is [https://wiki.halcove.com/files/RCMX86.UF2 fusee-suite].

	I whipped up a generic usage guide for users and installers here.		I whipped up a generic usage guide for users and installers here.

Ha1vorsen at 12:06, 23 March 2022

2022-03-23T12:06:23Z

← Older revision		Revision as of 07:06, 23 March 2022
Line 3:		Line 3:
	The modchip consists of a Trinket M0-based device, usually the [https://github.com/euclala/RCM-X86 RCMX86], to serve as an auto-injector for RCM-vulnerable devices.		The modchip consists of a Trinket M0-based device, usually the [https://github.com/euclala/RCM-X86 RCMX86], to serve as an auto-injector for RCM-vulnerable devices.

	Generally, the modchip will inject a payload to the console, which then chainloads a payload from the microSD card. The software I use is [https://halcove.com/files/~~rcmx86~~.~~uf2~~ fusee-suite].		Generally, the modchip will inject a payload to the console, which then chainloads a payload from the microSD card. The software I use is [https://halcove.com/files/RCMX86.UF2 fusee-suite].

	I whipped up a generic usage guide for users and installers here.		I whipped up a generic usage guide for users and installers here.