Hacking SWITCH NOOB PARADISE - Ask questions here

alcyppa

Member
Newcomer
Joined
Jul 15, 2018
Messages
11
Trophies
0
Age
33
XP
158
Country
Italy
If you have your sysNAND on 4.1.0 and your emuNAND on 8.1.0, you will not burn more than five fuses (4.1.0 = 5 fuses), with or without AutoRCM.

That means I could boot normally into 4.1 sysNAND without any more burned fuses than what I already have, right?
No interaction between emuNAND and sysNAND in that regard?


Since you're using only 4.1.0 and higher, you don't need to worry about it.

The gamecard slot can receive updates, which in some circumstances will cause it to not work (e.g. after a downgrade to a system version before the GC update, on a sysNAND lower than the version that updated the GC, etc.).


If I remember correctly, there hasn't been a GC update since 4.0.0, so updating your emuNAND to 8.1.0 will not update the GC.

That's clear, thanks.

  1. Why are you using an emuNAND?
  2. Why are you playing anything on your 4.1.0 sysNAND?

1. Right now basically for nothing.
I've recently started using the Switch that I've bought quite a while ago and decided to hack it. I'm planning on using sysNAND to play original games and to play online (but right now I've only got BOTW) and emuNAND for more shady stuff (homebrews, save editors, toying around and backups which mostly means testing stuff before buying it).

I think I'm gonna use mostly the sysNAND.

2. Because since I only have got BOTW I've had no reason to update. I'd like to play my original stuff on sysNAND since it is basically like playing on a vanilla Switch.
Also I'm not gonna hack the save or anything like that so I really don't have a reason to play it on emuNAND.
emuNAND will mostly be for toying around.

That begs the question: do I actually have any reason to not want to update my sysNAND?


Thanks for your time BTW... Really appreciated.
 

Lacius

Well-Known Member
Member
Joined
May 11, 2008
Messages
18,099
Trophies
3
XP
18,334
Country
United States
That means I could boot normally into 4.1 sysNAND without any more burned fuses than what I already have, right?
No interaction between emuNAND and sysNAND in that regard?
That is correct, assuming you have booted normally into your 4.1.0 sysNAND at least once before and already have five burnt fuses.

1. Right now basically for nothing.
I've recently started using the Switch that I've bought quite a while ago and decided to hack it. I'm planning on using sysNAND to play original games and to play online (but right now I've only got BOTW) and emuNAND for more shady stuff (homebrews, save editors, toying around and backups which mostly means testing stuff before buying it).

I think I'm gonna use mostly the sysNAND.

2. Because since I only have got BOTW I've had no reason to update. I'd like to play my original stuff on sysNAND since it is basically like playing on a vanilla Switch.
Also I'm not gonna hack the save or anything like that so I really don't have a reason to play it on emuNAND.
emuNAND will mostly be for toying around.

That begs the question: do I actually have any reason to not want to update my sysNAND?
  • If you don't plan on using online play, and your Switch is unpatched, then there is no real reason to use an emuNAND (unless you prefer using the warmboot browser exploit instead of using the RCM exploit).
  • If you plan on using your clean sysNAND for online play, you're going to have to update your clean sysnAND to the latest version (currently 8.1.0).
 

noctis90210

Well-Known Member
Member
Joined
Dec 24, 2013
Messages
969
Trophies
0
Age
36
XP
1,625
Country
i just updated to 8.1.0 (on ams 0.9.2)...
i just noticed that another bootlogo appears with a circle logo and a text "sept by atmosphere, free and open source"

this is not present on 6.2.0 even using atmosphere 0.9.2

is there a way to get rid of this logo?
here is what i mean... 5:25

cuz theres too much boot logo appearing upon turning on my switch:
1. the custom bootlogo
2. the "sept by atmosphere, free and open source" bootlogo
3. the main atmosphere logo on black background
4. the nintendo switch logo on black background

i only want to retain #3 and #4, is there a way to get rid the #2 cuz its like too much bootlogo since sept is also part of atmosphere which is already have its own bootlogo (#3)

#1 is easy to delete since its just a flag on a ini file or delete the picture

thanks...
 
Last edited by noctis90210,

alcyppa

Member
Newcomer
Joined
Jul 15, 2018
Messages
11
Trophies
0
Age
33
XP
158
Country
Italy
That is correct, assuming you have booted normally into your 4.1.0 sysNAND at least once before and already have five burnt fuses.


  • If you don't plan on using online play, and your Switch is unpatched, then there is no real reason to use an emuNAND (unless you prefer using the warmboot browser exploit instead of using the RCM exploit).
  • If you plan on using your clean sysNAND for online play, you're going to have to update your clean sysnAND to the latest version (currently 8.1.0).

Im planning to do that.
Any real drawbacks to that?
(Also, do I need to just update regularly from the Nintendo server right?)
 

Lacius

Well-Known Member
Member
Joined
May 11, 2008
Messages
18,099
Trophies
3
XP
18,334
Country
United States
Im planning to do that.
Any real drawbacks to that?
(Also, do I need to just update regularly from the Nintendo server right?)
If you don't care about the warmboot browser exploit on 4.1.0, which is probably the best 4.1.0 is ever going to get, then there's really no reason not to update your sysNAND to 8.1.0. You can preserve your fuse count by installing AutoRCM so you can downgrade back to 4.1.0 later, but it's my opinion that there will never be any reason to downgrade to 4.1.0 if you don't care about the current warmboot browser exploit on 4.1.0.

(Also, do I need to just update regularly from the Nintendo server right?)
Yes, if your sysNAND is clean, you should update it normally in the system settings. If you care about preserving fuses (see above for why there might not be any reason to do so), you will have to do take some extra steps.
 

alcyppa

Member
Newcomer
Joined
Jul 15, 2018
Messages
11
Trophies
0
Age
33
XP
158
Country
Italy
If you don't care about the warmboot browser exploit on 4.1.0, which is probably the best 4.1.0 is ever going to get, then there's really no reason not to update your sysNAND to 8.1.0. You can preserve your fuse count by installing AutoRCM so you can downgrade back to 4.1.0 later, but it's my opinion that there will never be any reason to downgrade to 4.1.0 if you don't care about the current warmboot browser exploit on 4.1.0.


Yes, if your sysNAND is clean, you should update it normally in the system settings. If you care about preserving fuses (see above for why there might not be any reason to do so), you will have to do take some extra steps.

Thanks very much.
I think I'll update then, the warmboot exploit doesn't look it is worth the hassle.

Just another question: I've obviously made boot0/1 and rawNAND backups while on 4.1.
Should I make those again after updating to 8.1 or the ones I've already made will do just fine in case I'll need them?
 

Hayato213

Newcomer
Member
Joined
Dec 26, 2015
Messages
19,617
Trophies
1
XP
20,447
Country
United States
i just updated to 8.1.0 (on ams 0.9.2)...
i just noticed that another bootlogo appears with a circle logo and a text "sept by atmosphere, free and open source"

this is not present on 6.2.0 even using atmosphere 0.9.2

is there a way to get rid of this logo?
here is what i mean... 5:25

cuz theres too much boot logo appearing upon turning on my switch:
1. the custom bootlogo
2. the "sept by atmosphere, free and open source" bootlogo
3. the main atmosphere logo on black background
4. the nintendo switch logo on black background

i only want to retain #3 and #4, is there a way to get rid the #2 cuz its like too much bootlogo since sept is also part of atmosphere which is already have its own bootlogo (#3)

#1 is easy to delete since its just a flag on a ini file or delete the picture

thanks...


I believe you can but you need to need to edit the source code for the cfw pack, but then again it is only like 20 seconds to boot, leave it alone.
 
  • Like
Reactions: noctis90210

Lacius

Well-Known Member
Member
Joined
May 11, 2008
Messages
18,099
Trophies
3
XP
18,334
Country
United States
Thanks very much.
I think I'll update then, the warmboot exploit doesn't look it is worth the hassle.

Just another question: I've obviously made boot0/1 and rawNAND backups while on 4.1.
Should I make those again after updating to 8.1 or the ones I've already made will do just fine in case I'll need them?
Regarding brick-recovery, there's no real reason to make another NAND backup if you already have one. I highly recommend storing your NAND backup somewhere online, like Google Drive.
 
  • Like
Reactions: alcyppa

c0r

Member
Newcomer
Joined
Feb 24, 2019
Messages
9
Trophies
0
Age
42
XP
98
Country
Brazil
Hey guys, what should I do if I want to migrate from a SDCard to another?! I tried to copy the Nintendo folder from the old SDCard and place it on the new one with the newest Kosmos v13.0.2 files but some games won't boot... Any tips?! Thanks in advance! :-)

BTW, I'm using a Mac OSX to copy and paste the files.
 
Last edited by c0r,

Lacius

Well-Known Member
Member
Joined
May 11, 2008
Messages
18,099
Trophies
3
XP
18,334
Country
United States
Hey guys, what should I do if I want to migrate from a SDCard to another?! I tried to copy the Nintendo folder from the old SDCard and place it on the new one with the newest Kosmos v13.0.2 files but some games won't boot... Any tips?! Thanks in advance! :-)

BTW, I'm using a Mac OSX to copy and paste the files.
If you don't have exFAT support installed on the Switch, then you need to either:
  1. Reformat the new SD card as FAT32.
  2. Install exFAT support to the Switch.
 
  • Like
Reactions: c0r

lettuce

Well-Known Member
Member
Joined
Jul 27, 2006
Messages
811
Trophies
0
XP
491
Country
So i was using Zadig to replace the drivers so i can use Tinfoil and Nut over usb but the driver installation failed and now when i remove or plug the usb back into the switch i no longer get the usb windows 10 sound and also in Zadig when i select show all device 'libnx USB comms' is no longer show!. How can i fix this issue please?

EDIT: Never mind got it work but trying a different USB C cable
 
Last edited by lettuce,

Draxzelex

Well-Known Member
Member
Joined
Aug 6, 2017
Messages
18,984
Trophies
2
Age
29
Location
New York City
XP
13,312
Country
United States
ok so i deleted my atmosphere folder, installed a fresh one, added just the kosmos patches, launch with hekate, same problem cart based nsp say they are corrupt.


this guys explains exactly whats happening to me, but i dont understand how he fixed it. just adding some lines of txt in a hekate.ini file?
Latest Kosmos has the kip1patch=nosigchk line in the CFW sections. Maybe you're not launching a profile with that line?

Hey all,

I have an unpatched Switch on Hekate with emuNAND / Atmosphere running as a hidden partion on my SD card and I want to switch to ReiNX ...

How do I do that?

Any good tutorials out there I could not find ...

Thanks,
Marius
https://reinx.guide/ although you will not be able to boot into emuMMC with ReiNX as ReiNX does not support emuMMC at the current time.

Can I just copy and paste the files 1:1 from one micro sd to another card if I want to upgrade the micro sd?
Yes unless you are using MacOS or certain builds of Windows 10 in which case you need to fix the archive bit after the transfer which can be done via Hekate.
 

CuriousTommy

Well-Known Member
Member
Joined
Jul 22, 2014
Messages
524
Trophies
0
Age
27
XP
647
Country
United States
I made an emunand partition on my switch and updated it to 8.1.0. However, I seem to have an issue with being able to read the card. When I use my sysnand on version 3.0.0, it works just fine.

Does anyone know what the issue may be?
 

THCsGameChannel

Active Member
Newcomer
Joined
Apr 19, 2015
Messages
36
Trophies
0
Age
32
XP
209
Country
Gambia, The
Latest Kosmos has the kip1patch=nosigchk line in the CFW sections. Maybe you're not launching a profile with that line?

https://reinx.guide/ although you will not be able to boot into emuMMC with ReiNX as ReiNX does not support emuMMC at the current time.

Yes unless you are using MacOS or certain builds of Windows 10 in which case you need to fix the archive bit after the transfer which can be done via Hekate.

Hm I coppied everything over but it doesnt work.

Failed to load hekate_ipl.ini
Could not identify package 1 version
Could not load firmware

Even if I insert the old card again this comes up ...

File structure
XJGUU2C.png
 
Last edited by THCsGameChannel,

heyoo

Member
Newcomer
Joined
Jun 20, 2018
Messages
6
Trophies
0
Age
23
XP
310
Country
United Kingdom
hey so I updated from 5.something to 8.1.0, it worked fine for around 20 mins and then it randomly kicked me out saying that the sd card had been removed. Now I cannot boot into either CFW or OFW via the sxos menu without getting stuck on a black screen. I tried re-seating the sd card reader, replacing the sd card reader, formatting to ex fat and fat 32, using a different sd. I checked hekate and not even that can read my sd card, I just get met with 'could not initiate sd card, make sure its inserted'. I thought it was a hardware issue however I am still able to boot into the sxos menu and make nand dumps from it, which implies that it can both read the boot.dat file on the sd card and write to the card without any apparent problems.

I (stupidly) booted into ofw without auto rcm ,which worked (burning all of my fuses), to try and format the card that way but not even the ofw could read the sd card. I tried booting another cfw (atmosphere, reinx) via the sxos menu but I was still met with a black screen.

Any help would be great, Thanks.
 

ataraxis

Active Member
Newcomer
Joined
Aug 3, 2007
Messages
44
Trophies
0
XP
531
Country
Malaysia
Hi, I have a clean 5.1.0 NAND backup before hacking my switch. My switch is currently running CFW 7.1.0 with Reinx

I would like to run Atmosphere with EmuMMC.

Do i need to restore my switch using my 5.1.0 backup or can I just restore factory settings and update my switch to 8.1.0?

If i restore to 5.1.0 I can save my fuses? Is there a benefit for keeping the fuses? if i were to play online games i would still need the latest firmware correct?

Kindly advise the best way to have SysNAND for online games and EmuNAND for CFW. Thanks so much in advance.
 

Draxzelex

Well-Known Member
Member
Joined
Aug 6, 2017
Messages
18,984
Trophies
2
Age
29
Location
New York City
XP
13,312
Country
United States
Hm I coppied everything over but it doesnt work.

Failed to load hekate_ipl.ini
Could not identify package 1 version
Could not load firmware

Even if I insert the old card again this comes up ...

File structure
XJGUU2C.png
You did not indicate whether you were using Windows 10 or not.

hey so I updated from 5.something to 8.1.0, it worked fine for around 20 mins and then it randomly kicked me out saying that the sd card had been removed. Now I cannot boot into either CFW or OFW via the sxos menu without getting stuck on a black screen. I tried re-seating the sd card reader, replacing the sd card reader, formatting to ex fat and fat 32, using a different sd. I checked hekate and not even that can read my sd card, I just get met with 'could not initiate sd card, make sure its inserted'. I thought it was a hardware issue however I am still able to boot into the sxos menu and make nand dumps from it, which implies that it can both read the boot.dat file on the sd card and write to the card without any apparent problems.

I (stupidly) booted into ofw without auto rcm ,which worked (burning all of my fuses), to try and format the card that way but not even the ofw could read the sd card. I tried booting another cfw (atmosphere, reinx) via the sxos menu but I was still met with a black screen.

Any help would be great, Thanks.
I think you require the help of an actual expert since it seems like you've tried the most common fixes for your situation and I cannot think of any other way to solve your problem.

Is there any way to delete a user on Atmosphere emuMMc?
Not that I know of but why would you want to delete a user in the first place?

Hi, I have a clean 5.1.0 NAND backup before hacking my switch. My switch is currently running CFW 7.1.0 with Reinx

I would like to run Atmosphere with EmuMMC.

Do i need to restore my switch using my 5.1.0 backup or can I just restore factory settings and update my switch to 8.1.0?

If i restore to 5.1.0 I can save my fuses? Is there a benefit for keeping the fuses? if i were to play online games i would still need the latest firmware correct?

Kindly advise the best way to have SysNAND for online games and EmuNAND for CFW. Thanks so much in advance.
You should probably setup the emuMMC first before restoring your NAND so that way the save data from sysMMC carries over to emuMMC. While I have not set it up myself, I think this is the best guide for it so far.

Once you have setup emuMMC, then you should restore your NAND. It has been proven that factory resets do not prevent bans as people have been banned even after performing them. It would also be very silly for Nintendo to implement a pro-hacker feature in their own console. Anyway, restoring the NAND is pretty simple since all you do is drop your NAND in the /backups/(eMMC serial number)/restore folder on your SD card but if you need a guide, you can follow this one.

Now you have to be on the latest firmware in order to play online but it is up to you if you want to burn fuses or not. The purpose behind fuses are to prevent downgrading and the reason someone may downgrade is in case a better exploit is released on a lower firmware version such as a hypothetical untethered coldboot hack (for reference, the current exploit Fusee Gelee is a tethered coldboot). If you are fine with using Fusee Gelee until the end of the Switch's life, then you can just update normally and burn fuses in the process making you lose out on some potential future features. However since it is not only simple to update without burning fuses but also not proven to invoke a ban on its own, I highly advise you update without burning fuses.

If you wish to update without burning fuses, you have 3 choices which I will list out in decreasing order of safety in terms of bans:
  1. Using the homebrew application ChoiDujourNX which not only requires CFW but homebrew as well so most people do not use it for updating their sysMMC for clean online play
  2. Installing system updates while running CFW and having AutoRCM enabled. Normally, AutoRCM is removed during a system update which prevents you from updating without burning fuses online but modern CFW prevent this allowing you to update normally with the console while preserving fuses. This is safer than using ChoiDujourNX as it just requires you to run a CFW. You don't even need CFW running to download the system update as you can boot Stock mode via Hekate to download it then delete Wi-Fi settings and reboot into CFW to install the update offline. This is what I personally do and I have not been banned yet. There is a way to update without burning fuses without CFW or homebrew but it is risky
  3. Rebooting into RCM after the system update is finished installing. Since fuses are burnt not when the system update is installed but when the console's stock bootloader detects a firmware version higher than the fuse count, one can easily bypass this by booting into RCM before the console's stock bootloader runs. This is a variation of the above method but instead of using CFW to maintain AutoRCM, we use a jig which is only as successful as the jig is at booting the console into RCM. If the console does not boot into RCM, fuses will be burnt so this method is not highly recommended. If you need a full guide, you can find one here
 
  • Like
Reactions: geecat

geecat

Member
Newcomer
Joined
Jul 16, 2019
Messages
8
Trophies
0
Age
44
XP
68
Country
United States
So am due to receive a switch that should be unpatched later today.

My main goal is to transfer a WiiU BOTW save to Switch. I'd prefer to use the save with OFW, if possible, and am trying to figure out if there's a reasonable way to do that. I also want to play various online games on OFW (smash, DQ builders 2, etc), so I'm looking for the most careful method. I know there are no guarantees, but I'm willing to take the long way around for the best odds.

On the WiiU side, I've managed to get homebrew running in the WiiU and have exported my save. The BOTW converter ran successfully.

On the switch side, to get a general sense of the basics, I've reviewed a few guides for the RCM boot + Hekate + Atmosphere on EmuMMC setup, including those linked upthread here. I've prepared a microSD card for the Switch, formatted in FAT32 with Checkpoint preinstalled.

Although I wonder if I should use ExFAT instead, since I suppose I will have to let the console update (perhaps using the method described above to preserve fuses) to play online, even if booting OFW through Hekate to avoid the fuse check.

And I expect I also need to update the BOTW version to read the transferred save — which I am trying to figure out if I should do the normal way at the outset...

My impression is that the first thing I should do is make a complete backup of the Switch when it arrives, the Sysnand and the boot partitions, etc.

What I am trying to figure out is the proper sequence to do things in after that.

My tentative plan is:

-Receive switch, take modem offline, power on to check installed versions, verify functionality etc
-Perform RCM exploit test, verify unpatched
-Following guides, boot via RCM into Hekate, create an EmuMMC at the current version level and perform complete dump of system files. Archive as a ZIP.
-Still offline, Reboot normally into OFW, run BOTW from cartridge at whatever version it shipped as to create save folder structure in sysnand.
-Turn off switch. Take modem back online.
-Boot via RCM into Hekate and run OFW. Enable WiFi, permit Switch to download system updates, but do not to install them. Go offline again.
- Boot via RCM into Hekate, and create another archived dump with the system update files downloaded and the stock BOTW install and save present.
-Then use Hekate to install the system update. (Method 2 from the previous post upthread). All reboots from here will use RCM to avoid fuses being burned.
-Dump and archive again after the system update.
-Reboot into Hekate and run OFW, go back online and let BOTW update. Overwrite the save to bring it up to version level.
-Go back offline reboot and dump again.
-Now we can boot into either CFW or OFW and we have a clean backup NAND with updated firmware, game and placeholder save at current versions.

I know the above may involve more dumps than necessary but it's out of caution. Is there anything I'm missing there?

After that, the question is how to get the converted save into the game under OFW with the least risk.

After reading some other threads, is this the best way to go (adapted from a thread here called "how-can-i-move-saves-from-emunand-to-sysnand" that I can't link):

-Go offline, delete wifi etc.
-Boot into CFW, use Checkpoint to inject the WiiU save into BOTW's Sysnand storage.
-Presuming it loads successfully, update the save (wait for a blood moon and manually re-save?).
-Reboot into Hekate, make another dump.
-Using hacdiskmount, open the backup with the converted BOTW save and copy the save files
-Using hacdiskmount, open the clean backup at current version levels and overwrite the placeholder save with the converted save
-Restore the clean backup with the converted save files to sysnand
-Reboot back into OFW (via RCM as always), go online/enable wifi and play normally?!?

Is it correct that by doing the above there should be no evidence that CFW was ever run? Or is the ban risk no less than just running Checkpoint to inject the save just the once, and then running under OFW after that without the additional steps of copying the files to the older image offline and then restoring it?

Apologies if I've overlooked anything obvious, abused any terminology, or am mixing up older procedures with current advice.
 
Last edited by geecat,

Site & Scene News

Popular threads in this forum

General chit-chat
Help Users
  • No one is chatting at the moment.
    K3Nv2 @ K3Nv2: Sorry for accidentally bending over