can emuNAND access the sysNAND? I basically want to use checkpoint to pack up my save data. my plan would be to just play my real games on OFW and then when i want to back up the saves, boot into emuNAND to use checkpoint. is this possible?
Either there should be an option under System Settings or you can boot into Maintenance mode by holding volume + and - when turning the console on. If AutoRCM is enabled, you hold volume + and - after sending a payload that boots CFW/OFW.Thx Draxzelex.
What are the steps to perform factory reset?
On another note, since I'm on OFW 4.x when I try to download Fortnite using eshop, it keeps prompting me to upgrade the firmware. If I upgrade to 6.1 e.g., would that make that prompt go and let me download the game? Also is it possible to get Fortnite without installing it from eshop?
The whole purpose of EmuNAND is to run a completely separate NAND from SysNAND. You will have to dump the save file from EmuNAND and inject it into SysNAND.can emuNAND access the sysNAND? I basically want to use checkpoint to pack up my save data. my plan would be to just play my real games on OFW and then when i want to back up the saves, boot into emuNAND to use checkpoint. is this possible?
You can either use the payload Hekate or briccmii to display the current fuse count.Thanks again Draxzelex. I have read a bit about fuses getting burnt when you upgrade. How can I find the current number of fuses in my switch and how does auto rcm and upgrading the OFW affects the fuses?
Atmosphere: https://guide.sdsetup.com/#/Hi! I really want to homebrew my Switch, but I can't seem to find a simple guide on how to do so. I have firmware 6.1, which I think still works, so I think I'm good there. Does anybody have a simple (enough) guide on how to homebrew Switch?
Hey guys, I'm on 6.1 firmware and was playing arms. I went online to use the homebrew appstore and now I cant play arms because it wants the new update. Any way to fix this?
If that doesn't work, you can try using DevMenu's Reset Required Firmware Version feature. But since DevMenu isn't supported on firmware 6.X, you will have to downgrade to 5.X1. First make sure you cancel the upgrade!
2. Then press the power button and hold for about 5 seconds
3. Choose power off
4. Hold down VOL+ and VOL- and pres simultaneously the power button
5. Choose update but do not update... instead cancel the process!
6. Shut down the console and restart normally
You can't use CFW on firmware 6.2; if you update EmuNAND to firmware 6.2, it will become bricked.Hello there
I'm currently running a launchday switch with 6.1
My main goal is actually playing I'm not really interested into piracy but I want to have the option to still run homebrew maybe someday.
Therefore I haven't upgraded yet to 6.2 but I certainly have to for smash online I guess.
I read through some guides and as far as I understand what I need would be some kind of emunand which is right now only possible with sx os. Sx seems to have the issue to create the emunand partition too small that Nintendo could theoretically see this through telemetry and ban my console.
And I don't think thermosphere will be available until smash releases.
So what I thought of would be the following:
Leave sysnand on 6.1 and create a clean and backup then I could revert to it any time.
Then create a emunand with sx os because there is no other way at the moment.
Leave the emunand stock and update it to 6.2 and use it for online gaming.
But that would be kinda risky because nintendo could detect that i'm playing on a emunand and ban my console right?
Atmosphere doesn't support installed .XCI files; only ReiNX does.I've have Atmosphere running on 6.1 from the Kosmos sdsetup guide. I got a Labo Variety Kit XCI and installed it with ZeroTwoXCI. When launched, it says the game is corrupted.
Should it normally work on Atmosphere? Is there anything else it could be or is it a bad dump or something else (patch or update required??) (I would have thought installation would have failed if it were a bad dump.)
Thanks!!
Boot into maintenance mode by holding volume + and - when turning the console on. If you have AutoRCM enabled, which you should if you updated without burning fuses, hold volume + and - when sending the ReiNX payload.My switch came with OFW 4.x and I instaled ReiNX and updated do 6.0.1 (without burning fuses).
But now every time I wake up my console, a popup comes up saying that there is an update available and asks me if I want to update. I allways chose No because I dont know wich version it will update to or if it will burn any fuse while doing so.
Is there a way to stop this anoying popup?
I have a 6.1 switch that was never hacked before and I'm about to install SX OS in it, so I would like to ask a few newbie questions first.
1 - With the new way that Emunand is working (through SD) is it "safer" (I know I can't be completely safe) if I want to play online games like Warframe on my OFW? I remember seeing a thread clearly stating that it wasn't safe when the first Emunand came out but I don't see a clear answer this time. And by the way, I'm still being able to play Warframe online even without updating to 6.2, is it normal?
2 - I'm seeing a lot of warnings about 6.2 breaking CFW. In the case of SX OS + Emunand, should I only not update my Emunand or I can't update my OFW too?
3 - I already have a 64Gb Micro Sd installed on my Switch, will I need to format it before doing all SX OS stuff? Because I already have a good amount of original games installed in it.
4 - I was reading that the process to back up my "virgin" NAND that is available on SX OS tutorial not being ideal because it starts the CFW before the back up, so the NAND isn't totally clean anymore. What would be the best and noob-friendly process to do this initial back up?
Thanks!
I have some questions because everything is so confusing
1. Can i use ChoiDujournx instead of ChoiDujour? The normal version ist toooo long
2. Can I update with ChoiDujournx and restore with my clear nand to have my downgraded firmware?
3. If I only want to usw nsp games offline, why do I have to update? I thought reinx or tinfoil can bypass firmware?
4. is autorcm unsafe? Because I need it to safe my low firmware.
Just use Hekate to restore the boot0/boot1 AND eMMC RAW GPP of your firmware 6.1 NAND backup.Can someone please point me in the right direction for downgrading from 6.2.0 with a 6.1.0 backup. I will use SX if that matters
When you go to System Settings to check your current system firmware, if you cannot see the number, that means there is a pending system update.Is there a way to tell if the switch has downloaded an update but yet to install it?
Some .NSP files are converted from .XCI files hence the lack of a ticket during the installation which is expected. And for your other Switch, you can just format the SD card to FAT32 instead of using exFAT as we can do everything using FAT32. If the SD card is bigger than 32 GB, it will need to be formatted with a third-party tool such as GUIFormat. Regardless if you want to continue using FAT32 or use ChoiDujourNX to add the exFAT patch to any given firmware, the SD card must be FAT32.Hi,
im (technically) not new to this forum been checking it since a long time ago but this is my first qeustion to you guys. The new Nintendo switch exploit gave me reason to ask a qeustion(s) here to you guys.
I seem to have alot of trouble installing Pokemon eevee and DragonballZfighter on my switch. Both games I own (2 times actually) since I play alot with my kid on it. My boys 3 yrs old and often turns in the cardrige the wrong way and breaks. The Cardridge slots from our DS broke 2 times...(happened to our 3DSXL twice also lol). Loading it from a SD card seems to go a lot easier and safer!
Ive installed Reinx and Atmosphere on my switch just to try this exploit out and its working very well for me. Ive learned most things about the CFW spend hours reading and watching tuts on youtube and I enjoy it very much.
However with some games I get a ticket installation error and I have tried several NSP dumps (using all latest cfw and tinfoil off course). I also tried almost everything that should fix the problem (changed nsp into smaller name, used fat32 and a file splitter) still no succes.
I also want to install CFW on my other switch (this one still running ofw from ninty) but with the new update 6.2, if I put in the SD card it instantly asks for the new firmware update. And from what ive learned that this is not just a driver install or something, nintendo instantly throws in the 6.2 update!!
Is there any work-around? I was thinking to reformat the SD card into FAT32 and install CFW (its a SDXC I card does this matter?). Then upgrade with choidujour with ExFAT support to 6.0.1 or 6.1.0? Does anyone tried this and can confirm this is working for him/her?
Also thanks to all the people maintaining this forum ive been checking it out for years and always helped me out with my exploits! If theres a way I can tribute im happy to hear from someone!
Curious to your answers.
A humble Switch gamer..
Just use Hekate to restore the boot0/boot1 AND eMMC RAW GPP of your firmware 6.1 NAND backup
Thanks for the help, you da man!If that doesn't work, you can try using DevMenu's Reset Required Firmware Version feature. But since DevMenu isn't supported on firmware 6.X, you will have to downgrade to 5.X
You can't use CFW on firmware 6.2; if you update EmuNAND to firmware 6.2, it will become bricked.
Atmosphere doesn't support installed .XCI files; only ReiNX does.
Boot into maintenance mode by holding volume + and - when turning the console on. If you have AutoRCM enabled, which you should if you updated without burning fuses, hold volume + and - when sending the ReiNX payload.
- Safer, yes. And its normal to be able to play online on 6.2 however Nintendo may eventually change that due to 6.2 breaking CFW and they would want to promote a firmware that works against the scene
- If you update SysNAND to 6.2, you won't be able to use CFW on it but obviously OFW will work fine. If you update EmuNAND to 6.2, it will be bricked
- If its formatted to exFAT and you never downloaded the exFAT patch to your console, you may have to format it to FAT32. And since the SD card is bigger than 32 GB, it will need to be formatted with a third-party program such as GUIFormat. If you want the exFAT patch, you will have to use the homebrew application ChoiDujourNX.
- Use Hekate to backup the NAND.
Just use Hekate to restore the boot0/boot1 AND eMMC RAW GPP of your firmware 6.1 NAND backup.
- Yes
- You can use either ChoiDujourNX or your clean NAND to downgrade
- Tinfoil does not bypass all firmware requirements
- AutoRCM is 100% safe
When you go to System Settings to check your current system firmware, if you cannot see the number, that means there is a pending system update.
Some .NSP files are converted from .XCI files hence the lack of a ticket during the installation which is expected. And for your other Switch, you can just format the SD card to FAT32 instead of using exFAT as we can do everything using FAT32. If the SD card is bigger than 32 GB, it will need to be formatted with a third-party tool such as GUIFormat. Regardless if you want to continue using FAT32 or use ChoiDujourNX to add the exFAT patch to any given firmware, the SD card must be FAT32.
It should not unless SX OS does some funky thing to the NAND when dumping it (as far as I know, it doesn't even verify the dump which is worrisome to say the least). And if your fuse count is burnt to 8 for firmware 6.2, then the only way to boot up the console on a lower firmware is by going into RCM and using a bootloader that bypasses the fuse check.If I could vote for a most helpful temper that would be you my dude.
I backed up NAND with SX OS does that make any problems when restoring with Hekate?
Also I heard about burning fuses and that (as far as I know) I wont be able to boot normally again, it has to be via RCM everytime is that correct?