There's almost zero proper documentation on BCAT stuff but does it still need to be done in 2024 for the latest 2.0.6 update?
From my own testing, a handful of date events seem to be working just fine as long as in game prerequisites are met. There are a LOT of events once tied to BCAT files though, so I can't really check all of em.
One other point to note - in videos of players using legit switches and copies of the game, the version still seems to be 2.0.6 without a letter (and 🏠for HHA DLC)
Hi, Im new here, and ive wanted to start modding my switch and my 3ds. the 3ds is simple enough, however i have no experience with soldering or hardware knowhow, so i was wondering if there was any way i could pay someone to mod my switch for me?
Error: 2145-0001 (0x291) when installing Mario Kart 8 Deluxe NSP (or any game for that matter) I am certain I have installed sigpatches. Atmosphere 1.8.0, on firmware 19.0.1. I had no problems on 19.0.0. What could be wrong?
So, since very recently Nintendo decided to be a fuck and kill all emulator projects for the Switch, I finally decided to grab them and learn how to use them. I'm very much not new to emulation in general and where to find games, so I'm mostly good with that. Only thing is that I couldn't get the new Zelda game to run without stutters, but I guess that's the shaders compiling in real time. Unicorn Overlord plays absolutely flawlessly.
Anyway, I would like to go after more games, but all of the different file formats confuse me. Specifically, the NSZ format. None of my emulators are able of loading that, my other games are in NSP format and load just fine.
Okay, also. I own a 2019 model Switch Lite and would like to know how would I go about unlocking it. I guess I would need to install a modchip on it?
I haven't followed the Switch homebrewing scene for several years, and could use some help! I have a v1 Nintendo Switch that I originally homebrewed using SXOS + SXOS Pro dongle. I know that SXOS is dead now, so I'm looking to update my setup to the current Switch homebrew platform. Is that Atmosphere? What is the recommended path for updating my homebrew setup? Can I still use my SXOS pro dongle with the new setup to launch custom firmware?
I came across this guide for example, is this still up-to-date?
Hi all,
I have been a member of titz pro for a long time, but not been active on my switch for quite a while. Just booted it up and checked tinfoil and I’m not getting a success message from titz pro anymore. I’m wondering if there is a new host that someone can share or point me in the direct of it?
I'm looking to back up all my switch games using DBI MTP responder. In the installed games partition there is the folder containing the base, updates, and dic as separate files. Also in this folder is a single nsp b+ file containing base, updates, and dic. Which is better for external storage incase I need them? Also if I go with the b+ version and a new update or dlo comes out down the line. Will I be locked into what that one file contains only and can't be updated?
Atmosphère is a work-in-progress customized firmware for the Nintendo Switch. - Atmosphere-NX/Atmosphere
Link Actions
Interestingly the release notes include this section:
fusee no longer supports applying IPS patches to KIPs.
Followed up by:
The IPS subsystem was originally designed to make nogc patches work for FS, but these are now internal, and it appears the literal only kip patches that exist are for piracy.
Does this indicate Atmosphere is going to become more hostile for any form of piracy?
Hi all, I just finished making a newb friendly guide for CFW Switch.
You can find it here Rentry.co/SwitchCFW
I also made custom NRO forwarders for HBmenu, Haze, Tinwoo, Tinfoil and RetroArch.
Let me know what you think and what I should add next!
I have installed a Pico 2040 on my V1 patched Switch yesterday. It's an "easy install" hwfly pico clone with the CPU flex cable.
I copied my sysNAND to the SD card and I've had a warning saying that there may be memory issues wih the eMMC.
I booted emuNAND from SD card and it works fine.
My issue is that I cannot boot Original firmware from eMMC chip. I tried the "Reboot to OFW" option in Hekate and I also tried to boot holding vol+, vol-, clicking power and releasing volume buttons once Nintendo logo appears. The screen is always stuck on the "Nintendo SWITCH" logo.
I tried to boot holding the RESET button of the modchip while booting but I've had the same results. So I guess I can deduce it is not a firmware issue.
To troubleshoot the issue, I disconnected the modchip to connect the eMMC chip directly to the console and the original system firmawre does boot ! I guess I can deduce I did not cause any damage during installation.
I thought it would be as easy as plugging the Switch Lite or SD card into the Mac and moving the NSP files over into a folder. I have no idea what I'm doing obviously.
Edit: I attempted to transfer files over from my Mac using Android File Transfer and DB Installer. It looked very promising but AFT closes and reopens over and over again.
Recently got into the homebrew scene for switch. Migrating over from the 3ds. I plan on going the DDL route with jdownloader2 (unless someone has a better idea and can share lol). NSP vs XCI for base game files? What are the pros and cons of each? What do you use? I don’t plan on doing any online play or ever using stock FW ever again if that changes anything. Thanks.
Japanese Switch consoles (XAW, XKJ, XTJ) are unable to use higher 5GHz channels due to their WiFi chipsets being set to the JPN WiFI region in PRODINFO which restricts their use. You can manually change this region code to unlock the channels and use them in the USA or EU if you have an imported Japanese console.
This guide is meant for use with emuMMC, but it can be followed on sysMMC as well by mounting eMMC RAW GPP in Hekate to NxNandManager instead of the SD card's emuMMC. Be careful and keep PRODINFO backups if messing with PRODINFO on sysMMC.
Getting Started
We'll be using NxNandManager, and HxD to edit the PRODINFO. If you haven't dumped your console's prod.keys yet, you will also need to do that. Use your own console's prod.keys, this is important!