Hacking SWITCH NOOB PARADISE - Ask questions here

[godreborn]

thanks, man. I have a 1tb micro sd card in hand, but right now I'm backing up the old card to the computer.

 

[sallos9812]

If I update my Sysnand's firmware to 9.1.0 for online play, will I have a problem when I go into Emunand 9.0.1?

 

[ThePokemonFan25]

Ok I see, in fact it works as you said but the strange thing is that in my case, I don't use a jigg/dongle or autoRCM to activate RCMmode.
I just Link my switch with my PC and press Vol+, it's enough to activate RCM mode on TegraRCM software (green check).
That's why I don't understand the current situation.
If you want to launch CFW, you need : Injector (PC or smartphone) + jigg/dongle or AutoRCM On + usb cable (if you don't use a dongle).

However right now I only have to do : Injector (PC) + usb cable + Press Vol+.
I can do the following sequence : CFW -> turn off switch -> OFW -> turn off switch -> CFW -> turn off switch -> ...
All of this without a dongle/jigg or autoRCM On (when usually one of them is required to access CFW).

When i tried this it didnt work

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

Ok so I don't have any problems with my Switch (CFW & OFW are all good) but something weird is currently happening.
I can boot in CFW (Vol+ and TegraRCM payload inject with PC) then I turn off the console, boot up normally and it gives me OFW.

My point is that to achieve this, I don't use :
-AutoRCM
-a dongle/jigg (Joycon, tinfoil, paperclip, screwdiver etc)

Before I always used the Joycon + tinfoil trick to launch CFW but right now it seems like I can avoid that.
I did it several times and it works (launch CFW without a jigg, then once on CFW turn off the Switch and boot in OFW).

How is it possible?
Because if AutoRCM was indeed activated (to avoid the use of a jigg), I wouldn't be able to turn on OFW right?

Is it possible to make a video on how you did this?

 

[Loe7]

Ok well, yesterday I used this guide https://nh-server.github.io/switch-guide/user_guide/rcm/#emunand-cfw-recommended
To create an emuNAND so I can use cfw on it. Everything is fine but then I thought it would be a good idea to downgrade from 9.0.1 to 8.1.0. Then I saw that this was a bad idea and updated it back to 9.0.1 with choidujournx. I checked my burned fuses in hekate and it says burnt fuses odm 7/6. My console only boots now when I have my rcm loader attached or when I send a payload from pc which is basically the same.

When I'm in hekate and try to launch Atmosphere FSS0 EmuMMC I get straight back into the hekate main "menu".
Now my question, I have a clean 9.0.1 nand backup, is it save to restore it and do the tutorial again for setting up cfw? Help I'm so confused lol

 

[soul0war]

@Draxzelex Thanks for your answer.

found out a few things and here is the questions that remains.

When I launch in Hekate, I got 3 option "cfw sysnand - cfw emummc - stock sysnand"

AM I right in believing the following
CFw sysnand: is the one I have been using since I hacked my switch in 2018? So right now all my nsp are installed there and I need to extract my saves from that partition
CFW emummc: is the one I just created and should be the one I update with choixdujour and should be the one I use for all my homebrew from now on.
Stock (sysnand): is the one I need to use my clean backup on and will be the one I use for going online and using my purchased cartdridge and the eshop.

IF this is true which tutorial shoudl I follow to migrate my save and files from my old CFW to my new partition? How do I clean my stock to go online?

Thank you, you are very helpful like always.

 

[trakker1]

Quick one please guys,

On SX OS if I get banned will my Nintendo account with legit purchases get banned too?

Thanks in advance!

 

[Draxzelex]

If I update my Sysnand's firmware to 9.1.0 for online play, will I have a problem when I go into Emunand 9.0.1?

Nope.

@Draxzelex Thanks for your answer.

found out a few things and here is the questions that remains.

When I launch in Hekate, I got 3 option "cfw sysnand - cfw emummc - stock sysnand"

AM I right in believing the following
CFw sysnand: is the one I have been using since I hacked my switch in 2018? So right now all my nsp are installed there and I need to extract my saves from that partition
CFW emummc: is the one I just created and should be the one I update with choixdujour and should be the one I use for all my homebrew from now on.
Stock (sysnand): is the one I need to use my clean backup on and will be the one I use for going online and using my purchased cartdridge and the eshop.

IF this is true which tutorial shoudl I follow to migrate my save and files from my old CFW to my new partition? How do I clean my stock to go online?

Thank you, you are very helpful like always.

CFW SysNAND and Stock SysNAND refer to the same partition in the form of your SysNAND, they are just 2 different ways of launching SysNAND but you are correct in that this is what you have been using since 2018. And if by new partition you mean emuMMC, then the saves should be there because emuMMC is made by making a copy of your sysNAND. Lastly, to clean your SysNAND, you need to restore a clean NAND backup meaning a NAND dump made prior to ever running CFW & homebrew.

Quick one please guys,

On SX OS if I get banned will my Nintendo account with legit purchases get banned too?

Thanks in advance!

Nintendo accounts are very rarely, if ever, banned.

 

[CrazySquid]

Uh... Let's see if I did understand correctly.
I have hekate with AutoNoGC enabled (AutoRCM), also Atmosphere in it's latest version (I think).
If I update my Switch from OFW the update fixes my booting process so it will disable my AutoRCM install, right?. If I update using Atmosphere connecting to Nintendo servers to update then I will update without burning fusees? Even if after installing the update I boot into OFW instead CFW? the fusee burning process is only at install or is also everytime you boot the OFW?.
Also... Is this too risky to do? (I mean updating while running CFW).
Thank you.

 

[Draxzelex]

Uh... Let's see if I did understand correctly.
I have hekate with AutoNoGC enabled (AutoRCM), also Atmosphere in it's latest version (I think).
If I update my Switch from OFW the update fixes my booting process so it will disable my AutoRCM install, right?. If I update using Atmosphere connecting to Nintendo servers to update then I will update without burning fusees? Even if after installing the update I boot into OFW instead CFW? the fusee burning process is only at install or is also everytime you boot the OFW?.
Also... Is this too risky to do? (I mean updating while running CFW).
Thank you.

Yes and while updating with Atmosphere by connecting to Nintendo servers will update your firmware without burning fuses, after this update it will boot into CFW not OFW. More specifically, it will boot up whatever reboot_to_payload.bin file you have in your Atmosphere folder which boils down to either Fusee or Hekate depending on which one you use.

Fuses are burnt when you boot the console using the stock bootloader (i.e. normally/without RCM). Fuses are not burnt at the time of installation. This means its always possible to burn fuses however AutoRCM mitigates this risk to zero so long as its installed.

And while I would say it might be a little risky to update while running CFW, in order to mitigate the ban risk, you can download the update in Stock/OFW then install it in CFW while the console is offline.

 

[Poke_Rad]

I've been having some trouble setting up my emunand and backing up my keys, I've followed a few different guides online, I got the same result on these methods, I have my eMMC enabled, but when I launch CFW with Emunand it reloads Hekate.

As for Lockpick RCM I select dumping the keys from sysnand as a guide said, it shows a sept by atmosphere screen then the console turns off.

I only want EmuNand and my keys for safety measures as I do not mind if I get banned, but keeping my switch safe would be nice. I was considering using just my sysnand.

 

[soul0war]

Nope.

CFW SysNAND and Stock SysNAND refer to the same partition in the form of your SysNAND, they are just 2 different ways of launching SysNAND but you are correct in that this is what you have been using since 2018. And if by new partition you mean emuMMC, then the saves should be there because emuMMC is made by making a copy of your sysNAND. Lastly, to clean your SysNAND, you need to restore a clean NAND backup meaning a NAND dump made prior to ever running CFW & homebrew.

Nintendo accounts are very rarely, if ever, banned.

Ok so I copied over my sysnand to my emunand, normal that it want me to reinstall every game I had installed while on my emunand partition? Are all my save transferred or do I need to use checkpoint?

What should I do now to use my clean backup to install to sysnand?

When using choixdujour do I choose where I install the firmware file? I want to go online with my sysnand so I need to be on latest with 9.1.0 just released, I can't use hekate until it's fixed right?

I'm trying to follow your explanation you gave crazysquid, how important are fuse is I'm already out of pegascape range (5.1) guess that if I burn more fuse my clean 5.1 nand will be useless from that point on? Or will I be able to flash it but will need to update firmware right after?

Thanks
Sorry for all this I can't seem to find a tutorial to cover what I'm trying to do in one place ... should be the most frequent process I presume: ON CFW for a while, moving the cfw to emunand and cleaning sysnand with clean backup ... no?

 

[CrazySquid]

Yes and while updating with Atmosphere by connecting to Nintendo servers will update your firmware without burning fuses, after this update it will boot into CFW not OFW. More specifically, it will boot up whatever reboot_to_payload.bin file you have in your Atmosphere folder which boils down to either Fusee or Hekate depending on which one you use.

Fuses are burnt when you boot the console using the stock bootloader (i.e. normally/without RCM). Fuses are not burnt at the time of installation. This means its always possible to burn fuses however AutoRCM mitigates this risk to zero so long as its installed.

And while I would say it might be a little risky to update while running CFW, in order to mitigate the ban risk, you can download the update in Stock/OFW then install it in CFW while the console is offline.

Thanks! And how should I update my emuMMC? Because that runs Atmosphere and the risk of ban it's there.

 

[SAFN]

Everything has been working fine! I launched Hekate. Etc got in my system menu. Play games etc. Today when I started up Hekate and click launch and choose what to launch after the first logo screen I get taken back to Hekate. I reformated my SD card. Redid the files and everything else possible, but this still keeps happening. Does anyone know?

 

[CrazySquid]

Everything has been working fine! I launched Hekate. Etc got in my system menu. Play games etc. Today when I started up Hekate and click launch and choose what to launch after the first logo screen I get taken back to Hekate. I reformated my SD card. Redid the files and everything else possible, but this still keeps happening. Does anyone know?

Hm... I did update my Switch to 9.1.0 and the same is happening to me, I think Hekate and the CFWs needs to be updated to dupport 9.1.0.

 

[Draxzelex]

Ok so I copied over my sysnand to my emunand, normal that it want me to reinstall every game I had installed while on my emunand partition? Are all my save transferred or do I need to use checkpoint?

What should I do now to use my clean backup to install to sysnand?

When using choixdujour do I choose where I install the firmware file? I want to go online with my sysnand so I need to be on latest with 9.1.0 just released, I can't use hekate until it's fixed right?

I'm trying to follow your explanation you gave crazysquid, how important are fuse is I'm already out of pegascape range (5.1) guess that if I burn more fuse my clean 5.1 nand will be useless from that point on? Or will I be able to flash it but will need to update firmware right after?

Thanks
Sorry for all this I can't seem to find a tutorial to cover what I'm trying to do in one place ... should be the most frequent process I presume: ON CFW for a while, moving the cfw to emunand and cleaning sysnand with clean backup ... no?

Saves are stored in the console itself so like I said, emuMMC is just a copy of sysMMC.

Do not use ChoiDujour. Use ChoiDujourNX. Yes, there is a difference between the two tools despite the similar names. Anyway, you run ChoiDujourNX in the partition you want to update.

Pegascape will eventually support firmware 5.X however there is no ETA on when that support will come so I would say it is not pointless to burn fuses especially since there is no benefit in burning fuses.

Thanks! And how should I update my emuMMC? Because that runs Atmosphere and the risk of ban it's there.

You can use the homebrew application ChoiDujourNX to update your emuMMC.

 

[Zddddd]

Hi, I have a console that have many games installed on SD card, now I want to migrate them to another console, can I backup the nand and restore it on the another console through Hekate? Or the only way is to re-install them all over again?

Thanks in advance.

 

[LeoLeoSuper]

Hi, I have a console that have many games installed on SD card, now I want to migrate them to another console, can I backup the nand and restore it on the another console through Hekate? Or the only way is to re-install them all over again?

Thanks in advance.

IIRC NAND (including emuMMC) is encoded using your BIS keys. HacDiskMount might help, but that might be a bit complicated, so reinstalling and using a save manager is probably your best bet.

 

[Draxzelex]

Hi, I have a console that have many games installed on SD card, now I want to migrate them to another console, can I backup the nand and restore it on the another console through Hekate? Or the only way is to re-install them all over again?

Thanks in advance.

As the user above stated, your NAND is encrypted with console-specific keys known as biskeys. You will cause if a brick if you restore one console's NAND dump to another.

 

[Zddddd]

IIRC NAND (including emuMMC) is encoded using your BIS keys. HacDiskMount might help, but that might be a bit complicated, so reinstalling and using a save manager is probably your best bet.

I see, I will reinstall them then, thanks for the prompt reply!

 

[soul0war]

Saves are stored in the console itself so like I said, emuMMC is just a copy of sysMMC.

Do not use ChoiDujour. Use ChoiDujourNX. Yes, there is a difference between the two tools despite the similar names. Anyway, you run ChoiDujourNX in the partition you want to update.

Pegascape will eventually support firmware 5.X however there is no ETA on when that support will come so I would say it is not pointless to burn fuses especially since there is no benefit in burning fuses.
You can use the homebrew application ChoiDujourNX to update your emuMMC.

Thank you

So I restored my nand backup form pre-cfw on 5.1.0 on my sysnand and it went smoothly, but when I start it it says that I have corrupted data on my sd card and it will be deleted no other option? I rebooted in hekate without deleting anything ... what could be the problem?