Anonymous
Not logged in
Talk
Contributions
Create account
Log in
Halcove
Search
Editing
Nintendo Switch (Homebrew)
(section)
From Halcove
Namespaces
Page
Discussion
More
More
Page actions
Read
Edit
Edit source
History
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
== First Usage Guides / Frequent Questions == === What is Atmosphère? === Atmosphère is the custom firmware that you're using on your console. Custom firmware handles all of the invisible patches that you use once you boot into the main Switch menus; it's the software that makes modding your Switch "useful". CFW has no visible menu, and there is '''no visible difference''' between a console simply using CFW and one using original firmware (OFW), unless you take advantage of the features in CFW to modify the appearance and functionality of your console. === What is Hekate? === Before the console turns on, there is (normally) invisible software that handles the startup of the console. This applies to most electronic devices. This invisible software software is called the '''bootloader''', and it handles the preparation of the device. When you hacked the Switch, you also gave it a custom bootloader menu named ''Hekate'' ("heh-KAH-tay"). This software serves to add flexibility to how the Nintendo Switch starts up, and provides an interface for you to select different payloads/OSes to launch upon startup, including OSes like Android and Linux. === What is Horizon? === Horizon is the Switch's native OS. Atmosphère applies customisations to this OS, and fully replaces some parts of it behind the scenes, even if you can't see those replacements. === Software === * '''Nintendo Switch does not boot past Nintendo Switch logo!''' One of these things are likely busted: PRODINFO, your USER partition, your SYSTEM partition, your partition table is messed up. If you run Atmosphère, a rogue sysmodule or corrupt microSD may also be to blame. * '''Nintendo Switch does not boot past Nintendo logo!''' You may have corrupted one of the boot stage slots. Restore a BCPKG2 backup. *'''After injecting a payload and booting, an error about an unknown package1 version appears!''' Your homebrew software does not support the Horizon firmware you are trying to run. Update your homebrew, or wait for a new release. *'''My homebrew software has a NOFAT error message!''' Your microSD is corrupt. Reformat it, or obtain a new card. === Hardware === * '''Nintendo Switch does not boot past Nintendo Switch logo, does not display on the dock, or does not charge!''' It is highly likely that the M92T36 chip has been blown out by overvoltage, or a physical short. Common causes are using an uncertified USB-A to USB-C cable to charge the unit, or using a third party dock. Third party AC adapters which don't utilise USB also can cause this. Your Switch will likely need to have the M92T36 replaced. A blown BQ24193 may also be the culprit. * '''Screen shows ink-like blotches that obstruct gameplay!''' Replace the screen. Duh. * '''Nintendo Switch emits a grinding or sawing noise when pressed together!''' This is the fan scraping against the console's metal backplate. Please do not press the console together. * '''Nintendo Switch turns off abruptly, even with remaining battery!''' The battery may be decalibrated. This can happen to any device with a battery. This occurs when the battery percentage is not synchronised with the physical amount of remaining power. This can be solved by charging the device for double the amount of time it normally takes to reach 100%, and draining it down to zero before fully charging it again. The battery is now calibrated. * '''Nintendo Switch does not turn on!''' Is the unit in RCM? Is the unit fully charged? Have you a modchip installed? If so, check the FAQ of the RCMX86 install guide. * '''Nintendo Switch does not enter RCM!''' All consoles can enter RCM, regardless of whether or not you're able to exploit RCM itself. If the console cannot enter RCM, it is never the fault of software. Instead, a dirty or defective bridging device ("jig"), a dirty or defective console-side slot, or torn ribbon cables will always be the culprit, if the user is following the correct steps to enter RCM (VOL+, Power, Home).
Summary:
Please note that all contributions to Halcove may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see
Halcove:Copyrights
for details).
Do not submit copyrighted work without permission!
Cancel
Editing help
(opens in new window)
Navigation
Navigation
Start Point
Contact
Projects
Random page
Outer Wall
Wiki tools
Wiki tools
Special pages
Page tools
Page tools
User page tools
More
What links here
Related changes
Page information
Page logs