Hacking SWITCH NOOB PARADISE - Ask questions here

[Got_Famous06]

I accidentally updated switch to 15.0, I have updated atmosphere and sig patches, but when trying to install the new tinfoil update using DBI i get this https://imgur.com/5Y5KQIP, and the home screen looks like this https://imgur.com/ejXhUhT. Im 99% sure ive deleted everything on my sd card for old tinfoil. Does anyone have any clue what i could be doing wrong ?

 

[binkinator]

I accidentally updated switch to 15.0, I have updated atmosphere and sig patches, but when trying to install the new tinfoil update using DBI i get this https://imgur.com/5Y5KQIP, and the home screen looks like this https://imgur.com/ejXhUhT. Im 99% sure ive deleted everything on my sd card for old tinfoil. Does anyone have any clue what i could be doing wrong ?

Sigpatches (GBATemp) — alternative Sigpatches for when others don’t seem to work.

Try using the self-installing tinfoil.nro file (put in /switch directory) from tinfoil.io and install using title override to start HBMenu.

Did you update your hekate?

If so do you still have:

kip1patch=nosigchk


…in your helate_ipl.ini?

 

[Got_Famous06]

Sigpatches (GBATemp) — alternative Sigpatches for when others don’t seem to work.

Try using the self-installing tinfoil.nro file (put in /switch directory) from tinfoil.io and install using title override to start HBMenu.

Did you update your hekate?

If so do you still have:

kip1patch=nosigchk


…in your helate_ipl.ini?

I tried those sigpatches and they didnt work, I got mine from JITS. I did update hekate and my file looks like this

{------ Atmosphere ------}
[Atmosphere FSS0 SYS]
fss0=atmosphere/package3
kip1=atmosphere/kips/*
emummc_force_disable=1
icon=bootloader/res/sys_cfw_boot.bmp
{}
{-------- Stock ---------}
[Stock SYS]
fss0=atmosphere/fusee-secondary.bin
stock=1
emummc_force_disable=1
icon=bootloader/res/stock_boot.bmp

I tried to drop the self installer and install using HBmenu but I get a screen " the use of online sevices on this console is currently resticted by nintendo" and doesnt do anything, I get the blank square on the home screen again

 

[binkinator]

I tried those sigpatches and they didnt work, I got mine from JITS. I did update hekate and my file looks like this

{------ Atmosphere ------}
[Atmosphere FSS0 SYS]
fss0=atmosphere/package3
kip1=atmosphere/kips/*
emummc_force_disable=1
icon=bootloader/res/sys_cfw_boot.bmp
{}
{-------- Stock ---------}
[Stock SYS]
fss0=atmosphere/fusee-secondary.bin
stock=1
emummc_force_disable=1
icon=bootloader/res/stock_boot.bmp

I tried to drop the self installer and install using HBmenu but I get a screen " the use of online sevices on this console is currently resticted by nintendo" and doesnt do anything, I get the blank square on the home screen again

You get a Nintendo error while trying to start up Tinfoil? That’s really sus.

Here is the stanza from my hekate_ipl.ini

[Atmosphere CFW]
payload=bootloader/payloads/fusee.bin
emummcforce=1
kip1patch=nosigchk
kip1=atmosphere/kip_patches/*
logopath=/graphics/splash/atmosphere.bmp
icon=/graphics/icons/current/atmosphere.bmp
id=atmo

See the kip1patch line? Try adding that one line.

 

[Got_Famous06]

You get a Nintendo error while trying to start up Tinfoil? That’s really sus.

Here is the stanza from my hekate_ipl.ini



See the kip1patch line? Try adding that one line.

OMG the patch line fixed it Thank you so much ! now i have to set up my shops lol Thanks so much !

 

[binkinator]

OMG the patch line fixed it Thank you so much ! now i have to set up my shops lol Thanks so much !

You bet. Enjoy your switch. For a good time check out Titz Pro or Teknik.

 

[elecu]

Hi guys! After transferring my data to a new SD using this tutorial https://nh-server.github.io/switch-guide/extras/transfer_sd/ I got the "A fatal error occurred when running fusee. Package2 meta is invalid!" error message. Any idea why it happened? I also tried to put in the old SD and still got this error.

I tried updating everything on the new SD using this tutorial https://rentry.org/MigrateToAtmosphere1_0_0 and still have the same issue.

 

[binkinator]

Hi guys! After transferring my data to a new SD using this tutorial https://nh-server.github.io/switch-guide/extras/transfer_sd/ I got the "A fatal error occurred when running fusee. Package2 meta is invalid!" error message. Any idea why it happened? I also tried to put in the old SD and still got this error.

I tried updating everything on the new SD using this tutorial https://rentry.org/MigrateToAtmosphere1_0_0 and still have the same issue.

Do you have backups of your Sysnand? (BOOT0/1+Rawnand)

What setup are you running:

• What versions of Firmware, Atmos and Hekate were you on before and what are you running now?
• Erista (V1) or Mariko (V2)?
• Sysnand or Emunand (and if emunand are you on Files or Partition based?
• Can you boot into OFW?

 

[elecu]

Do you have backups of your Sysnand? (BOOT0/1+Rawnand)

What setup are you running:

• What versions of Firmware, Atmos and Hekate were you on before and what are you running now?
• Erista (V1) or Mariko (V2)?
• Sysnand or Emunand (and if emunand are you on Files or Partition based?
• Can you boot into OFW?

Thanks for answering mate.
Yes, I have a full backup of my Sysnand.

• What versions of Firmware, Atmos and Hekate were you on before, and what are you running now? Firmware 15.0.0, Atmosphere 1.3.2, Hekate v5.9.0 & Nyx v1.4.0, I am not sure which Hekate I had, but after updating to 5.9.0 I have the same issue.
• Erista (V1) or Mariko (V2)? Erista
• Sysnand or Emunand (and if emunand are you on Files or Partition based? Emunand, Partition based.
• Can you boot into OFW? Yes, everything is working well there when I enter directly without RCM mode.

I just formatted the new SD again, made the partition using TegraExplorer, restored eMMC and nothing, same error message.

 

[binkinator]

Thanks for answering mate.
Yes, I have a full backup of my Sysnand.

• What versions of Firmware, Atmos and Hekate were you on before, and what are you running now? Firmware 15.0.0, Atmosphere 1.3.2, Hekate v5.9.0 & Nyx v1.4.0, I am not sure which Hekate I had, but after updating to 5.9.0 I have the same issue.
• Erista (V1) or Mariko (V2)? Erista
• Sysnand or Emunand (and if emunand are you on Files or Partition based? Emunand, Partition based.
• Can you boot into OFW? Yes, everything is working well there when I enter directly without RCM mode.

I just formatted the new SD again, made the partition using TegraExplorer, restored eMMC and nothing, same error message.

If you are running FW 15.0.0 you need Atmosphere 1.4.0. You can find it by tapping releases on the main site and look for the pre-release.

Look Here:

https://github.com/Atmosphere-NX/Atmosphere/releases

e: If you boot fusee.bin in your hekate_ipl.ini then grab the one from this issue on GitHub. Unzip it and pit the fusee.bin file under the /bootloader/payloads/ directory. If you don’t use fusee.bin don’t worry. Your package3 is fine.

 

[elecu]

If you are running FW 15.0.0 you need Atmosphere 1.4.0. You can find it by tapping releases on the main site and look for the pre-release.

Look Here:

https://github.com/Atmosphere-NX/Atmosphere/releases

e: If you boot fusee.bin in your hekate_ipl.ini then grab the one from this issue on GitHub. Unzip it and pit the fusee.bin file under the /bootloader/payloads/ directory. If you don’t use fusee.bin don’t worry. Your package3 is fine.

Thanks! I updated Atmosphere to 1.4.0. Now the error message is not shown, and the Atmosphere screen appears but after this just a black screen and nothing else. Nothing happens if I press the power button. I need to keep pushing the power button to reboot without RCM.
Do you think it's because the 1.4.0 is not a stable version or something like that?

 

[binkinator]

Thanks! I updated Atmosphere to 1.4.0. Now the error message is not shown, and the Atmosphere screen appears but after this just a black screen and nothing else. Nothing happens if I press the power button. I need to keep pushing the power button to reboot without RCM.
Do you think it's because the 1.4.0 is not a stable version or something like that?

Cool. We’re getting there.

A lot of folks are running 15.0.0 with 1.4.0 Atmos. It’s good even though marked pre.

Did you swap out your fusee.bin with the fusee.bin in the GitHub issue?

please post your hekate_ipl.ini file under the /bootloader/ directory.

 

[saunaiguana]

I know its not hacking related, but why on earth wont my joycons charge when hooked up on the main device (but not plugged in the dock) ?

Would drain the screen really quickly. I prefer it as is tbh

 

[elecu]

Cool. We’re getting there.

A lot of folks are running 15.0.0 with 1.4.0 Atmos. It’s good even though marked pre.

Did you swap out your fusee.bin with the fusee.bin in the GitHub issue?

please post your hekate_ipl.ini file under the /bootloader/ directory.

Good to know I didn't mess it up very much.

[config]
autoboot=0
autoboot_list=0
bootwait=3
backlight=100
autohosoff=0
autonogc=0
updater2p=0
bootprotect=0

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

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

Yeah, I replaced the old fusee.bin with the one from the 1.4.0 Atmo. I have this fusee.bin in the /bootloader/payloads/ and also in /atmosphere. When I have it only in /bootloader/payloads/ and I choose the CFW on Hekate, it says that the fusee.bin wasn't found in /atmosphere.

 

[binkinator]

Good to know I didn't mess it up very much.

[config]
autoboot=0
autoboot_list=0
bootwait=3
backlight=100
autohosoff=0
autonogc=0
updater2p=0
bootprotect=0

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

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

Yeah, I replaced the old fusee.bin with the one from the 1.4.0 Atmo. I have this fusee.bin in the /bootloader/payloads/ and also in /atmosphere. When I have it only in /bootloader/payloads/ and I choose the CFW on Hekate, it says that the fusee.bin wasn't found in /atmosphere.

That’s weird. Your payload specifically states it looks for it here:

payload=bootloader/payloads/fusee.bin

please be sure you downloaded the fusee.bin.zip file here:

https://github.com/Atmosphere-NX/Atmosphere/files/9793432/fusee.bin.zip

it corrects an issue that causes a black screen right after the atmosphere logo…

unzip this file and copy it to your /bootloader/payloads/ directory. Heck, put a copy of the same file in ’atmosphere/ directory as well just for fun.
(it won’t hurt anything so why not.)

Read more about the fix here:

https://github.com/Atmosphere-NX/Atmosphere/issues/1964

 

[elecu]

That’s weird. Your payload specifically states it looks for it here:

payload=bootloader/payloads/fusee.bin

please be sure you downloaded the fusee.bin.zip file here:

https://github.com/Atmosphere-NX/Atmosphere/files/9793432/fusee.bin.zip

it corrects an issue that causes a black screen right after the atmosphere logo…

unzip this file and copy it to your /bootloader/payloads/ directory. Heck, put a copy of the same file in ’atmosphere/ directory as well just for fun.
(it won’t hurt anything so why not.)

Read more about the fix here:

https://github.com/Atmosphere-NX/Atmosphere/issues/1964

Well, good news! The black screen is gone. Bad news, it started the SysNand instead of the Emunand and connected to the internet... I hope the system didn't notice. I'm double checking my hekate_ipl.ini, I guess there is something wrong with this.

 

[binkinator]

Well, good news! The black screen is gone. Bad news, it started the SysNand instead of the Emunand and connected to the internet... I hope the system didn't notice. I'm double checking my hekate_ipl.ini, I guess there is something wrong with this.

As long as you selected the Atmosphere CFW entry there’s no reason that config should have put you in Sysnand. You can force it to use the default emunand in that stanza by specifying it with a line like this:

emummcforce=1

As long as you don’t have any piracy installed on your Sysnand you’re fine. Booting w/ Atmosphere on Sysnand is done regularly by many folks w/o a ban.

 

[fatsquirrel]

Would drain the screen really quickly. I prefer it as is tbh

5 years ago dude

 

[Draxzelex]

Hello guys, I have a question.
Is it ok to play on cfw cysnand to activate translation games? All my games are legit, digital and physical, I dont pirate or install nsp stuff on my switch.
I only want to play in my mother language, going online as I do when on OFW.
Also is it ok to use themes or acessing homebrew?
I know that only have a software moded swith has a risk of ban, but I know there is some people that uses cfw on ssysnand and they still didnt got banned, I want to know from those people if they are still ok or got caught by nintendo ninjas.
Thanks

There is always a risk of getting banned when going online with CFW and/or homebrew. Those people who go online are aware of the risks and choose to accept to get banned at any point.

 

[Asia81]

Is there some ways to connect the switch to the PC using USB, but WHILE the switch is docked?
I tried to connect USB-C from my PC, to the USB on the dock, but it doesn't seems to work.

That would just avoid me to remove it from the dock and use the usb-c cable I want to install nsp over usb or transfer files using mtp, as I could just let the cable between the pc and the dock. I'm not sure if you got what I meant.