I would personally do the official update first. I don't think there is much to lose from 1.0, and it's incompatible with a lot of new games. Get a clean NAND on a higher firmware - I wish I had
The first step of hacking any console is making a NAND backup. The last thing anyone wants is to have wasted all of their money on a bricked console. Clean or not, the real purpose of a NAND backup is to restore from a brick. If you haven't made a NAND backup yet, do so immediately.
The point is, that I dont want to use cfw, yet. I would like to use it at a later point. I only would like to update right now for playing online. But should I make a backup of my 5.1.0 nand right now before updating or is it enough, when I backup my 6.2.0 nand later, right before I really want to hack my switch?
I've been reading a bunch of guides and threads and still a bit confused. My unit is patched according to this but it's on FW v4.1.0. Can I do anything right now?
okay
1) Backup Nand and biskeys
2) update firmware officially if you aren't banned and don't care about coldboot hax, else choidujourNX
3) Launch CFW, you can also take a second nand backup at this point
Alternatively, you can update then do nand and biskeys
I've been reading a bunch of guides and threads and still a bit confused. My unit is patched according to this but it's on FW v4.1.0. Can I do anything right now?
I would personally do the official update first. I don't think there is much to lose from 1.0, and it's incompatible with a lot of new games. Get a clean NAND on a higher firmware - I wish I had
Thanks for your fast reply. So you would do an official update fro m 1.0 to 6.2.0 and then Backup Nand and biskeys, right? What do you mean with a clean NAND on a higher firmware?
okay
1) Backup Nand and biskeys
2) update firmware officially if you aren't banned and don't care about coldboot hax, else choidujourNX
3) Launch CFW, you can also take a second nand backup at this point
Alternatively, you can update then do nand and biskeys
How soon though? Problem is all the games I own right now require updating, so the unit is being a paperweight. Isn't there an unofficial way to update that allows rolling back?
If you have 2 switches (both can launch cfw and have used before):
If you dump an xci from a cartridge that supports local multiplayer (from switch 1), transfer it to (switch 2 running sxos) and you launch the game on the second switch (using flight mode), then launch the cartridge from switch 1 running ofw, then proceed to connect both of them in local multiplayer, can nintendo detect your *completely clean* first switch is playing with a copy of its game on another switch and then ban you?
(can nintendo see that through local multiplayer, the other is using an exact copy of your game, then ban you?) (on the first switch)
The point is, that I dont want to use cfw, yet. I would like to use it at a later point. I only would like to update right now for playing online. But should I make a backup of my 5.1.0 nand right now before updating or is it enough, when I backup my 6.2.0 nand later, right before I really want to hack my switch?
It depends on what you use to backup the NAND. Hekate, as an example, is loaded before the NAND (more specifically, it is loaded in RCM) so there is nothing to trace back to. But if you use a homebrew application such as the ReiNX toolkit which requires CFW to run, then its possible the NAND backup will have CFW traces in it.
Regardless, a NAND backup should be made with or without CFW traces. A ban doesn't prevent you from using the console; a brick does.
If you have 2 switches (both can launch cfw and have used before):
If you dump an xci from a cartridge that supports local multiplayer (from switch 1), transfer it to (switch 2 running sxos) and you launch the game on the second switch (using flight mode), then launch the cartridge from switch 1 running ofw, then proceed to connect both of them in local multiplayer, can nintendo detect your *completely clean* first switch is playing with a copy of its game on another switch and then ban you?
(can nintendo see that through local multiplayer, the other is using an exact copy of your game, then ban you?) (on the first switch)
If its only local multiplayer, its fine. The real trouble you run into is bringing a .XCI dump online using its certificate which Nintendo can track across multiple consoles.
using Tinfoil to install Smash Ultimate to NAND via usb with Aluminum Foil on Win10. Downloads the large 14.5 gb file, & 2 more tiny files but then it gets to the fourth file and the download goes from 5 or 10 MB/s to 0.00 MB/s and stays there once it hits 100/105 MB. if i go to the home menu, smash ultimate is on the menu, but when i try to launch it an error occurs:2002-0001. please help.
using Tinfoil to install Smash Ultimate to NAND via usb with Aluminum Foil on Win10. Downloads the large 14.5 gb file, & 2 more tiny files but then it gets to the fourth file and the download goes from 5 or 10 MB/s to 0.00 MB/s and stays there once it hits 100/105 MB. if i go to the home menu, smash ultimate is on the menu, but when i try to launch it an error occurs:2002-0001. please help.
I'm sorry in advance for the longish post but I want to provide all the details so you don't have to ask me and show that I already did my research by outlining what I perceived to be the procedure. I'm not a noob when it comes to homebrews, I soft modded PS2 slim, PSP 2000, Wii (TwilightHax first, Letterbomb later), PS3 (downgrade+CFW and HAN), 3DS (Menuhax, then A9LoaderHax which was painstakingly long to setup then finally boot9strap) so I confide I'll be able to solve eventual problems on my own, I just need help to get started. With that said:
Hi there, I have a launch model (unpatched) Switch on 4.1.0. ; inside it is a 128 GB microSD formatted in exFAT (ouch, I know...) with a digital copy of Odyssey downloaded on it (my only Switch game).
My goal is to backup NAND, update without burning fuses, install SX OS on an EmuNAND (hidden microSD partition); at that point I want to be able to play my new copy of Smash ONLINE on SysNAND while playing OFFLINE modded Odyssey and eventually backups of other games on EmuNAND (SX OS).
I own a Ns-Atmosphere payload injector (the rectanglish white one which you can reprogram with your own payloads).
Basically this is what I understand I should do:
Put Hekate CTCaer payload on my injector, boot in RCM with the tool and backup my NAND.
Then run choidujournx (hope I got the name right) to update to latest firmware without burning fuses, but here comes my first doubt: I heard doing so installs AutoRCM, and I honestly don't know if that is going to cause me trouble later on (will it get me banned when I try to play my smash online on SysNAND?).
At this point, it is facultative but I really SHOULD reformat my SD to FAT32. I heard I need to do some magic with Hekate or the Nintendo folder won't be recognized or something like that (?)
After that I should install SX OS, I think by writing my payload file into my injector. Now, I don't want it writing ANYTHING on my SysNAND, I want it to be pristine , any heads up? Also, will it wipe my SD card since I want to get the hidden partition EmuNAND? If that's true then is the previous step of converting the SD to FAT32 even needed? I don't mind redownloading Odyssey from the eShop but I'd like NOT to lose my save). Should I have already purchased my SX license at this point? How do I activate it?
How soon though? Problem is all the games I own right now require updating, so the unit is being a paperweight. Isn't there an unofficial way to update that allows rolling back?
Thanks for your fast reply. So you would do an official update fro m 1.0 to 6.2.0 and then Backup Nand and biskeys, right? What do you mean with a clean NAND on a higher firmware?
i have a switch v4.1 with safe serial number and SXPRO. Now what should i do first?
i want to play offline games with the newest updates, so i guess i have to update to 6.2. but i am wondering if i should do that officially or with ChoiDujour. I do not understand that with burning fuses correctly. can someone explain that briefly?
is it still possible after a official update going back to 4.1 without limitations?
Recently i read something about releasing Deja Vu soon (v4.1-6.0), is that right? Therefore i don't like making errors
Man, coming from the 3DS Homebrew scene. Everything about the WII U and Switch has been a lot to take in.
Ended up getting an SX OS Pro and I've got a 3.0 Firmware Switch. Everything set up wise was easy. Made a NAND backup and and currently creating an emuNAND Partition. (These take so long, geez)
All the talk about AutoRCM and don't do this, don't do that, burned fuses. I'm taking in so much info and I feel like I'm even getting some of the Wii U stuff mixed in haha. But I suppose this is my question; When this emuNAND completes itself, do I need to use the AutoRCM function after ChoiDujourNX? From what I read I gather that it's necessity since a burned fuse from letting the regular nintendo bootloader would prevent you from using the older firmware on your normal nand? I can see the potential problem there but is it really that much of an issue if I don't plan on ever using online services ever again anyway? Should I just go ahead and let it update and burn fuses anyway? I see so many mixed opinions on everything. I don't mind using the AutoRCM but I keep seeing arguments over battery life or battery issues. Is it really that bad or risky?
Upon further research, would using NSC_BUILDER v0.79 be a better option? Just stay on 3.0 and just use this for bypassing firmware requirements entirely?
Just updated to 6.1 (without burning fuses), and now getting prompted to updated my joy-con firmware. I did a google but couldn't find out whether this is safe to do (in regards to downgrading back to 4.1 in the future). Just wanted to know if I should hold-off the update?
Man, coming from the 3DS Homebrew scene. Everything about the WII U and Switch has been a lot to take in.
Ended up getting an SX OS Pro and I've got a 3.0 Firmware Switch. Everything set up wise was easy. Made a NAND backup and and currently creating an emuNAND Partition. (These take so long, geez)
All the talk about AutoRCM and don't do this, don't do that, burned fuses. I'm taking in so much info and I feel like I'm even getting some of the Wii U stuff mixed in haha. But I suppose this is my question; When this emuNAND completes itself, do I need to use the AutoRCM function after ChoiDujourNX? From what I read I gather that it's necessity since a burned fuse from letting the regular nintendo bootloader would prevent you from using the older firmware on your normal nand? I can see the potential problem there but is it really that much of an issue if I don't plan on ever using online services ever again anyway? Should I just go ahead and let it update and burn fuses anyway? I see so many mixed opinions on everything. I don't mind using the AutoRCM but I keep seeing arguments over battery life or battery issues. Is it really that bad or risky?
Check out my post history and you will find the answers to many of your concerns, as I had the same doubts until very recently (the reason why I joined this forum).
My last couple of posts, in particular, address most of those issues, as they were in reply to two other users who were also new to the scene.
If you need anything else, please let us know. We’re glad to help!
Just updated to 6.1 (without burning fuses), and now getting prompted to updated my joy-con firmware. I did a google but couldn't find out whether this is safe to do (in regards to downgrading back to 4.1 in the future). Just wanted to know if I should hold-off the update?
last question: is it possible to update online via Nintendo and later if deja vu will be released downgrade to 4.1 (original nand backup)? i guess my cartridge slot will not work anymore or is it absolutely not possible to downgrade at 6.2?
i have a switch v4.1 with safe serial number and SXPRO. Now what should i do first?
i want to play offline games with the newest updates, so i guess i have to update to 6.2. but i am wondering if i should do that officially or with ChoiDujour. I do not understand that with burning fuses correctly. can someone explain that briefly?
is it still possible after a official update going back to 4.1 without limitations?
Recently i read something about releasing Deja Vu soon (v4.1-6.0), is that right? Therefore i don't like making errors
Fuses are designed to prevent downgrading. While you can theoretically downgrade with the current RCM exploit because all bootloaders bypass the fuse check (and now bypass the warmboot fuse check when waking up out of sleep mode), it becomes redundant to downgrade. The reason being is that the main purpose of downgrading in the first place is to take advantage of an alternative exploit that doesn't make use of a jig and USB cable.
Also what was recently released was a writeup on browserhax on 4.1-6.0 aka PegaSwitch which would only allow for homebrew. Deja Vu has still only been confirmed to work on 4.1 and below which would give rise to CFW.
Anyway, its up to you if you want to hold onto your fuses in case Deja Vu or another exploit comes out on lower firmwares. In order to prevent your fuses from being burnt, AutoRCM is used which prevents your console from booting up normally. The reason being is that booting the console up normally would burn fuses. Since it cannot boot up normally anymore, it can now only be turned on after sending a payload in RCM.
Lastly, ChoiDujour is a Windows program used for installing firmware updates via RCM but doesn't support firmware 6.2 and can take up to an hour. ChoiDujourNX is a homebrew application that has the same job as ChoiDujour but runs on your Switch and does support firmware 6.2 as well as taking a few minutes to do its job. Learn the differences and you can save yourself as well as others a lot of time down the road.
last question: is it possible to update online via Nintendo and later if deja vu will be released downgrade to 4.1 (original nand backup)? i guess my cartridge slot will not work anymore or is it absolutely not possible to downgrade at 6.2?
The cartridge slot is updated once you are running a firmware of 4.0 or higher. Once its updated, it will no longer work on firmwares below 4.0. If you've run a firmware of 4.0 or higher without the nogc patch (which breaks the cartridge slot thereby preventing it from being updated), then your slot has already been updated.
If you update online, you will burn fuses because after the system update is finished installing, it will reboot your console which will subsequently burn fuses. A risky option you can go for is trying to boot back into RCM when the console is rebooting by inserting a jig and holding volume + but of course the success of this would rest entirely upon the jig. You also would only have one shot at this as if the jig fails to short pin 10, then you will not enter RCM and burn fuses. Another alternative is to install the update while running a version of Atmosphere 0.8.0 or above with AutoRCM enabled. Atmosphere now prevents system updates from removing AutoRCM so if you download the system update onto your console then install it while Atmosphere is running and you have AutoRCM enabled, your console will reboot back into RCM and your fuses will be safe.
ReiNX is moving towards becoming the free version of SX OS so whatever features SX OS has will naturally become integrated into ReiNX as more progress is made on cracking it
Unfortunately there is not. What I recommend doing is by grabbing the Tinfoil build that ends in 883e from the bot that builds the commits which has the most success with Aluminum Foil
After a couple days of Nintendo releasing their 18.0.0 firmware update, @SciresM releases a brand new update to his Atmosphere NX custom firmware for the Nintendo...
Today, April 8th, 2024, at 4PM PT, marks the day in which Nintendo permanently ends support for both the 3DS and the Wii U online services, which include co-op play...
Hello, GBAtemp members! After a prolonged absence, I am delighted to announce my return and upgraded form to you today...
Introducing tempBOT AI 🤖
As the embodiment...
With Apple having recently updated their guidelines for the App Store, iOS users have been left to speculate on specific wording and whether retro emulators as we...
Yet another casualty goes down in the never-ending battle of copyright enforcement, and this time, it hit a big website which was the host for many fangames based and...
The highly popular and accurate FPGA hardware, MisterFGPA, has received today a brand new update with a long-awaited feature, or rather, a new core for hardcore...
The time has finally come, and after many, many years (if not decades) of Apple users having to side load emulator apps into their iOS devices through unofficial...
The romhacking community is always a source for new ways to play retro games, from completely new levels or stages, characters, quality of life improvements, to flat...
A new Nintendo Switch firmware update is here. System software version 18.0.1 has been released. This update offers the typical stability features as all other...
Retro handheld manufacturer Anbernic is releasing a refreshed model of its RG35XX handheld line. This new model, named RG35XX 2024 Edition, features the same...
Today, April 8th, 2024, at 4PM PT, marks the day in which Nintendo permanently ends support for both the 3DS and the Wii U online services, which include co-op play...
Hello, GBAtemp members! After a prolonged absence, I am delighted to announce my return and upgraded form to you today...
Introducing tempBOT AI 🤖
As the embodiment...
After a couple days of Nintendo releasing their 18.0.0 firmware update, @SciresM releases a brand new update to his Atmosphere NX custom firmware for the Nintendo...
Nintendo might just as well be a law firm more than a videogame company at this point in time, since they have yet again issued their now almost trademarked usual...
With Apple having recently updated their guidelines for the App Store, iOS users have been left to speculate on specific wording and whether retro emulators as we...
The time has finally come, and after many, many years (if not decades) of Apple users having to side load emulator apps into their iOS devices through unofficial...
A new Nintendo Switch firmware update is here. System software version 18.0.1 has been released. This update offers the typical stability features as all other...
Yet another casualty goes down in the never-ending battle of copyright enforcement, and this time, it hit a big website which was the host for many fangames based and...
The highly popular and accurate FPGA hardware, MisterFGPA, has received today a brand new update with a long-awaited feature, or rather, a new core for hardcore...
Two classic titles join the Nintendo Switch Online Expansion Pack game lineup. Available starting April 24th will be the motorcycle racing game Extreme G and another...
