Hacking Setting up EmuNand with Atmosphere and keep SysNand Firmware Low ?

fluidmax · Feb 26, 2020

I soft moded my switch (Unpatched) about a year ago and currently on ReiNx with FM V.4.1.0. I am thinking of migrating to atmosphere so I can use emuNand/emuMMC to play latest games and not worry about burning fuses. is there a guide. What is the best method to eliminate risk of bricking my system while setting up EmuNand to V9.1.0 ?

I " Do Not" use this system to play online but I want to keep the firmware on sysNand low. I read some posts and am thinking doing the following.

1. Get Atmosphere to run on my existing firmware and use it to create EmuNand
2. Boot into EmuNand that I just created and Use ChoiDujourNX to update EmuNand to V.9.1.0

Now what I am confused about are

1. Do I enable AutoRCM if I am only updating EmuNand through ChoiDujourNX? or it doesn't matter?
2. I do have games installed currently on my SD card that I used ReiNx to install, will those games work after I launch EmuNand and updated it to V9.1.0? or Do i have to reinstall the games?
3. Does it matter if my current SD is formatted with fat32?
4. What backup loader do I use after I get EmuNand up and running with V9.1.0? I just want a basic one which does the job

Thanks in advance

leon315 · Feb 26, 2020

if ur goal is keep sysnand low, then you don't need emunand, just update through Choidoujour method, simple as that.

the meaning to have an emunand is u wish to play legit cards online.

OrGoN3 · Feb 26, 2020

leon315 said:
if ur goal is keep sysnand low, then you don't need emunand, just update through Choidoujour method, simple as that.

the meaning to have an emunand is u wish to play legit cards online.

If OP updates without preserving fuses (without enabling AutoRCM as well), then they will never be able to go back to the lower firmware.

OP:
You can keep updating your sysnand via ChoiDujourNX, while keeping the AutoRCM option enabled. You will have to inject to use your system, but your fuses would be preserved and you could revert back at any time, assuming you have a nand backup of 4.1.0. Emunand is not needed for this case, but can be used. The only question is, are you going to be using any physical game carts in the system? If yes, then you will be unable to use the game carts if you revert back to 4.1.0. That's the caveat regardless of your choice of sysnand vs emunand.

OP:
1. Yes it matters and you need AutoRCM so it doesn't burn the fuses after the updates.
2. No. They'll still work provided you are using your backup to create emunand.
3. Fat32 is the preferred format. however, you will need to partition the card
4. Backup loader? There is no such separate software for this. After you update your patches for 9.1.0, you will be able to play any game you install, as well as non-signed games such as homebrew. Aren't you currently using a modded Switch? It's the same, just instead of the dead ReiNX, you will be using atmosphere and their patches. https://github.com/Joonie86/hekate/releases
5. I highly recommend just using fusee-primary. Hekate causes issues. However, the link I linked to above is not really hekate, but the patches for hekate and for fusee-primary.

Again, you can use sysnand if you use ChoiDujourNX to update AND ENABLE AUTORCM SO YOU DO NOT BURN FUSES!

leon315 · Feb 26, 2020

I wrote Choidoujou method, jesus, dunno how to read?? guess this is what result you can get thanks to public school.

fluidmax · Feb 26, 2020

OrGoN3 said:
If OP updates without preserving fuses (without enabling AutoRCM as well), then they will never be able to go back to the lower firmware.

OP:
You can keep updating your sysnand via ChoiDujourNX, while keeping the AutoRCM option enabled. You will have to inject to use your system, but your fuses would be preserved and you could revert back at any time, assuming you have a nand backup of 4.1.0. Emunand is not needed for this case, but can be used. The only question is, are you going to be using any physical game carts in the system? If yes, then you will be unable to use the game carts if you revert back to 4.1.0. That's the caveat regardless of your choice of sysnand vs emunand.

OP:
1. Yes it matters and you need AutoRCM so it doesn't burn the fuses after the updates.
2. No. They'll still work provided you are using your backup to create emunand.
3. Fat32 is the preferred format. however, you will need to partition the card
4. Backup loader? There is no such separate software for this. After you update your patches for 9.1.0, you will be able to play any game you install, as well as non-signed games such as homebrew. Aren't you currently using a modded Switch? It's the same, just instead of the dead ReiNX, you will be using atmosphere and their patches. https://github.com/Joonie86/hekate/releases
5. I highly recommend just using fusee-primary. Hekate causes issues. However, the link I linked to above is not really hekate, but the patches for hekate and for fusee-primary.

Again, you can use sysnand if you use ChoiDujourNX to update AND ENABLE AUTORCM SO YOU DO NOT BURN FUSES!

So are you saying regard less of me updating the SysNand or EmuNand as soon as I get to boot the higher firmware on the system, the game carts slot will no longer work when i revert back to 4.1.0? I thought Atmosphere automatically applies nogc patches when booting into 9.1.0 to prevent burning of lotus fuses for the game carts slot...so that if I do decide to downgrade I can still have my game carts slot work with lower firmware. I know by booting v9.1.0 from emunand, that will cause the game carts slot not to work with the new firmware but I can live with that knowing if I downgrade it will work again.

1. I was under the impression Auto RCM is only needed if I am booting the system from Sysnand, Atmosphere does not do system fuse checks when using it as a boot loader, so if I keep my SysNand low at 4.1.0 and get my switch into RCM and boot EmuNand to highter firmware (V9.1.0) it won't check for fuse burned right? or am I miss understanding something?
2. Can I just boot Atmosphere on my existing SysNand (4.1.0) and create EmuNand on to an SD card? or do I have to create emunand from my original Sysnand dump before i start using ReiNX?
3. is there a guide on how to do that before i setup my Emunand?

Thanks for the help

OrGoN3 · Feb 26, 2020

leon315 said:
I wrote Choidoujou method, jesus, dunno how to read?? guess this is what result you can get thanks to public school.

Rude much? I guess they never taught manners at your schools.

You completely left it the vital information that op has to have autorcm enabled or he'll burn fuses. If you're going to help people, that's great, but giving half an answer could easily have ended up with op burning fuses.

--------------------- MERGED ---------------------------

fluidmax said:
So are you saying regard less of me updating the SysNand or EmuNand as soon as I get to boot the higher firmware on the system, the game carts slot will no longer work when i revert back to 4.1.0? I thought Atmosphere automatically applies nogc patches when booting into 9.1.0 to prevent burning of lotus fuses for the game carts slot...so that if I do decide to downgrade I can still have my game carts slot work with lower firmware. I know by booting v9.1.0 from emunand, that will cause the game carts slot not to work with the new firmware but I can live with that knowing if I downgrade it will work again.

1. I was under the impression Auto RCM is only needed if I am booting the system from Sysnand, Atmosphere does not do system fuse checks when using it as a boot loader, so if I keep my SysNand low at 4.1.0 and get my switch into RCM and boot EmuNand to highter firmware (V9.1.0) it won't check for fuse burned right? or am I miss understanding something?
2. Can I just boot Atmosphere on my existing SysNand (4.1.0) and create EmuNand on to an SD card? or do I have to create emunand from my original Sysnand dump before i start using ReiNX?
3. is there a guide on how to do that before i setup my Emunand?

Thanks for the help

1. Autorcm is needed to prevent fuse burning. If you ever let the Nintendo boot loader to run, it'll burn the fuses. Is this something to want to risk?
2. If you want to keep your games installed, make an emunand from your current state. You still get to partition your sd card.
3. The guides were all incomplete last I looked. I'll try to find the one I used. I'm on my phone so it's hard to find. You can use hekate to create a new backup, and then one l once your sd card is properly formatted, you can use hekate to restore the backup to your emunand.

What I said about the gamecart is that if you want to use it on updated emunand, you'll have to update the lotus firmware and then you can't use it if you revert. If you don't plan to use any cart games on emunand, disregard this part.

fluidmax · Feb 26, 2020

OrGoN3 said:
1. Autorcm is needed to prevent fuse burning. If you ever let the Nintendo boot loader to run, it'll burn the fuses. Is this something to want to risk?
2. If you want to keep your games installed, make an emunand from your current state. You still get to partition your sd card.
3. The guides were all incomplete last I looked. I'll try to find the one I used. I'm on my phone so it's hard to find. You can use hekate to create a new backup, and then one l once your sd card is properly formatted, you can use hekate to restore the backup to your emunand.

What I said about the gamecart is that if you want to use it on updated emunand, you'll have to update the lotus firmware and then you can't use it if you revert. If you don't plan to use any cart games on emunand, disregard this part.

Thanks for the clarification, I will enable autoRCM just incase....any down side I need to be aware of for AutoRCM? I read some people experience issues like black screen and bricked system.

laz305 · Feb 27, 2020

I’m on Kosmos15.1 and the patches on the github link above there are 4 different zip files. How am I suppose to know which one I need to use? I am using a ns-loader to boot CFW and have already loaded every patch imaginable to try and get this too work. Now I need to know what I need to delete and install.

RandomUser · Feb 27, 2020

Or if you have patient, you could wait and see if at least one of these two projects gets developed for end users:

Then it could be possible to eliminate the need for emunand and perhaps you can use AutoRCM for at least one of the NAND slot for the DragonMMC. Although it may never come to fruition, so you will have to decide where or how to proceed.

OrGoN3 · Feb 27, 2020

laz305 said:
I’m on Kosmos15.1 and the patches on the github link above there are 4 different zip files. How am I suppose to know which one I need to use? I am using a ns-loader to boot CFW and have already loaded every patch imaginable to try and get this too work. Now I need to know what I need to delete and install.

Let's think this out loud. There are 3 files that explicitly state Kosmos in them. So now we've got it down to 3. One includes the words "tinfoilv8" and has the kip that must be used to Tinfoil 8+. Tinfoil 8+ will not be able to download the kip and apply it to your bootconfig, so Joonie did it for you.

Ok, there are 2 packs left. One is just the patches, and one is the patches plus a bootconfig. So it depends on what you need them for. If you don't use Tinfoil and already have all the bootconfigs from Kosmos, then just grab the regular Kosmos patches zip. If you need the bootconfig files from Kosmos (updated ones), then grab the one that includes them. If you need all of those AND Tinfoil 8.x+ support, grab the one saying it supports Tinfoil.

Edit: Kosmos itself does not come with the sigpatches required to play installed games that you didn't purchase. If you have everything set up and you aren't using Tinfoil, just grab the Kosmos_patches.

--------------------- MERGED ---------------------------

RandomUser said:
Or if you have patient, you could wait and see if at least one of these two projects gets developed for end users:

DragonMMC

ReLoad Modchip

Then it could be possible to eliminate the need for emunand and perhaps you can use AutoRCM for at least one of the NAND slot for the DragonMMC. Although it may never come to fruition, so you will have to decide where or how to proceed.

I would assume OP is waiting for a softboot method, even though they already exist. Maybe OP is waiting for an untethered, permanent soft hack? If one ever comes?

laz305 · Feb 28, 2020

Thanks finally got it all sorted out. It wasn’t the sigpatches. The games just needed to be updated. But all the warning says is you need a system update so......

Hacking Setting up EmuNand with Atmosphere and keep SysNand Firmware Low ?

Member

POWERLIFTER

Well-Known Member

POWERLIFTER

Member

Well-Known Member

Member

Well-Known Member

Rosalina in Plush Form

Well-Known Member

Well-Known Member

Similar threads

Popular threads in this forum