Hacking SWITCH NOOB PARADISE - Ask questions here

[Hayato213]

Useless post. I know what an emunand and sysnand is. Question is what the user below you answered.

Post automatically merged: Jan 10, 2023

So fusee.bin knows that when it is ran it has to check for emunand? If so that is absolutely amazing and whoever developed that payload is an intelligent individual. So I assume emummc_force_disable is what tells hekate to use the sysnand instead?

Is there any benefit to switching from what I have now:

[Atmosphere CFW]
payload=bootloader/payloads/fusee.bin
icon=bootloader/res/icon_payload.bmp

to this?:

[CFW - emuMMC]
fss0=atmosphere/package3
kip1patch=nosigchk
emummcforce=1
atmosphere=1
icon=bootloader/res/icon_payload.bmp

{--- Custom Firmware ---}
[CFW (SYSNAND)]
fss0=atmosphere/package3
kip1patch=nosigchk
emummc_force_disable=1
icon=bootloader/res/sysnand.bmp
{}

[CFW (EMUMMC)]
fss0=atmosphere/package3
kip1patch=nosigchk
emummcforce=1
icon=bootloader/res/emummc.bmp
{}

Based off this, if a user had a emunand, the top one allow the user to boot into CFW Sysnand, and the bottom one allow the user to boot into Emunand CFW,

If the person wanted to boot into stock OFW, no CFW

[Stock SYS]
fss0=atmosphere/package3
stock=1
emummc_force_disable=1
icon=bootloader/res/stock_boot.bmp

Really no major benefit, just the emummc_force and stock=1 tell hekate what to use.

 

[spiroid]

Hi everyone,

Thanks to all your kind replies I have now a working emunand with 15.0.1 firmware and game saves restored

The latest unpleasant surprise however is that the joycon are not working when detached. Tried several methods to resync but nothing worked si far. Any advice on this please ?

 

[Hayato213]

Hi everyone,

Thanks to all your kind replies I have now a working emunand with 15.0.1 firmware and game saves restored

The latest unpleasant surprise however is that the joycon are not working when detached. Tried several methods to resync but nothing worked si far. Any advice on this please ?

Update the joycon firmware.

 

[Blakejansen]

{--- Custom Firmware ---}
[CFW (SYSNAND)]
fss0=atmosphere/package3
kip1patch=nosigchk
emummc_force_disable=1
icon=bootloader/res/sysnand.bmp
{}

[CFW (EMUMMC)]
fss0=atmosphere/package3
kip1patch=nosigchk
emummcforce=1
icon=bootloader/res/emummc.bmp
{}

Based off this, if a user had a emunand, the top one allow the user to boot into CFW Sysnand, and the bottom one allow the user to boot into Emunand CFW,

If the person wanted to boot into stock OFW, no CFW

[Stock SYS]
fss0=atmosphere/package3
stock=1
emummc_force_disable=1
icon=bootloader/res/stock_boot.bmp

Really no major benefit, just the emummc_force and stock=1 tell hekate what to use.

[CFW (EMUMMC)]
fss0=atmosphere/package3
kip1patch=nosigchk
emummcforce=1
icon=bootloader/res/emummc.bmp

Is fusee.bin still used using this config?

Right now this is how I launch emunand

[Emunand CFW]
payload=bootloader/payloads/fusee.bin
icon=bootloader/res/icon_payload.bmp

 

[Hayato213]

[CFW (EMUMMC)]
fss0=atmosphere/package3
kip1patch=nosigchk
emummcforce=1
icon=bootloader/res/emummc.bmp

Is fusee.bin still used using this config?

Right now this is how I launch emunand

[Emunand CFW]
payload=bootloader/payloads/fusee.bin
icon=bootloader/res/icon_payload.bmp

Top part use hekate to launch package3 not fusee.bin

 

[Blakejansen]

Top part use hekate to launch package3 not fusee.bin

What is the difference between package3 and fusee.bin? I am a bit confused on that.

 

[Hayato213]

What is the difference between package3 and fusee.bin? I am a bit confused on that.

fusee.bin is atmosphere own bootloader, package3 just a payload, it use to be fusee-secondary.bin, it got renamed. As for how payload can be booted, hekate can boot fusee.bin that boot boot into package3, or hekate can boot package3 directly, fusee.bin just a bootloader like hekate.

 

[Draxzelex]

What is the difference between package3 and fusee.bin? I am a bit confused on that.

Fusee.bin is the primary payload and package3 is the secondary payload. They used to be called fusee_primary.bin and fusee_secondary.bin respectively which made it more intuitive what each one did. Basically, you send fusee.bin as your payload which chainloads into package3. The reason for this is because there is a size limit on payloads that you can send so in order to work around this, developers make payloads chain into bigger payloads to perform the hack.

 

[BruhGimmeName]

What is the SD seed vector and what does it mean if lockpick can't open it?

 

[Quattro74]

Anyone having luck on l4t ubuntu running n64 games? Do you use standalone mupen64plus or Retroarch? Care to share any config?

 

[WTG_Copycat]

hi guys,
I'm new at this "Hacking", I followed the guide of the nh-server.github site step by step, I did it twice but both times I get this error, I'm desperate, I created an account here just for this problem because I don't know what to do anymore xP

all files have been downloaded today, so all files are up to date, also the switch is up to the latest update

does anyone have any ideas?

 

[BruhGimmeName]

View attachment 346905
hi guys,
I'm new at this "Hacking", I followed the guide of the nh-server.github site step by step, I did it twice but both times I get this error, I'm desperate, I created an account here just for this problem because I don't know what to do anymore xP

all files have been downloaded today, so all files are up to date, also the switch is up to the latest update

does anyone have any ideas?

Hey I'm having the exact same error. What SD card are you using? Is that error from trying to boot into emuMMC?

 

[WTG_Copycat]

Hey I'm having the exact same error. What SD card are you using? Is that error from trying to boot into emuMMC?

Yes, the error appears when I try to start emuMMC, I'm using this sd card:

 

[BruhGimmeName]

Yes, the error appears when I try to start emuMMC, I'm using this sd card:View attachment 346916

Alright, I'm using a no-name 512gb sd myself, and I'm starting to think that might be the issue.
Do you perhaps have a smaller card you can try? Sadly I don't have anything but this one, and the replacement I ordered won't arrive until the 12th, so I can't test this theory myself.

 

[WTG_Copycat]

Alright, I'm using a no-name 512gb sd myself, and I'm starting to think that might be the issue.
Do you perhaps have a smaller card you can try? Sadly I don't have anything but this one, and the replacement I ordered won't arrive until the 12th, so I can't test this theory myself.

I never thought it might be the sd card the problem, tomorrow i'ill try to test on another sd

 

[impeeza]

When I started the scene, I did use a 64 GB, then migrated to a 400 GB and now using a 1TB, people reports using 2TB without problem.

be sure you test your card using H2TestW

 

[ganons]

Have an unpatched Switch on 5.1.0 fw. How do I go about installing the latest cfw? Update officially first or hack on this fw and then update?

 

[Hayato213]

Yes, the error appears when I try to start emuMMC, I'm using this sd card:View attachment 346916

Look quite cheap for a 512GB on Amazon, so you would wants to test the card as suggested. Doesn't look like a legit brand.

Post automatically merged: Jan 10, 2023

Have an unpatched Switch on 5.1.0 fw. How do I go about installing the latest cfw? Update officially first or hack on this fw and then update?

If you care about the fuse and keep it at a lower sysnand firmware then do a nand backup then use a emunand.

 

[Blakejansen]

fusee.bin is atmosphere own bootloader, package3 just a payload, it use to be fusee-secondary.bin, it got renamed. As for how payload can be booted, hekate can boot fusee.bin that boot boot into package3, or hekate can boot package3 directly, fusee.bin just a bootloader like hekate.

Thank you for the explanation. Your post was informative and I now know what I need to know in regards to the .ini file. Now I have to decide if it is worth burning fuses or if I should get autorcm.

 

[guily6669]

You should definitely always test your mSD card with H2testw like people always said here, if the mSD is fake or simply bad, it's a waste of time to try fixing problems when your mSD is the problem.

In fact you should stop buying strange named randomware mSD and buy a proper good fast one. I recommend Samsung Evo Select (the latest all blue A2) for example when it gets in promotion on amazon it has a good price-per-performance, I think it's the same as Samsung Evo Select but I heard it's exclusive to Amazon so you are even way less likely ever get a fake Evo Select buying from Amazon as seller than buying a Samsung Evo Plus from random ppl that if the price is too good to be true most likely it's going to be a fake one.

Also if you want emunand, a fast card makes a HUGE difference in speed and overall system smoothness, not to mention making huge backups and moving data on PC, like my friend 500GB he got cheap in a promotion here from a crap brand, I had to wait 2 hours to make a backup of like half it's GB at almost USB 2.0 low annoying garbage speeds while my mSD is around 80MB/s+...

For a Atmosphere tutorial I like this one: https://rentry.co/SwitchHackingIsEasy (It's the one I followed in the CFW guides).