Hacking SWITCH NOOB PARADISE - Ask questions here

NeoGranzon · 2024-11-23T11:42:33+0000

impeeza said:
I mean. NO! Any new model requiere hardware mod

i understanf perfectly!

cdogg · 2024-11-23T15:39:54+0000

Apologies if this has already been asked, but is 19.0.1 stable with latest Atmosphere/Hekate and sigpatches/sys-patch? I know the latest Atmosphere has basic support for 19.0.0, and I assume 19.0.1 isn't that big of a change, but I just want to be sure. I'm mainly asking because it seems things are starting to require 19.0.1, such as the 1.0.1 update for Yakuza Kiwami, but I've seen reports that some NSPs that get detected as needing 19.0.0/19.0.1 sometimes still work on 18.1.0 (which I am still using on my modded v1 Switch). Any insight would be appreciated. Thanks in advance.

laz305 · 2024-11-23T15:57:13+0000

impeeza said:
The ones you have defynied for Tesla Overlays, the defaults for TESLA are L+DUP+R and for UltraHand Overlay ZL + ZR + DUP

for me it is L+DDWN+R+R JOY CON IN
and what do you press again to get back into Hekate while it is booting? I'm trying to use Auto RCM now.

4d1xlaan · 2024-11-23T17:12:10+0000

cdogg said:
Apologies if this has already been asked, but is 19.0.1 stable with latest Atmosphere/Hekate and sigpatches/sys-patch? I know the latest Atmosphere has basic support for 19.0.0, and I assume 19.0.1 isn't that big of a change, but I just want to be sure. I'm mainly asking because it seems things are starting to require 19.0.1, such as the 1.0.1 update for Yakuza Kiwami, but I've seen reports that some NSPs that get detected as needing 19.0.0/19.0.1 sometimes still work on 18.1.0 (which I am still using on my modded v1 Switch). Any insight would be appreciated. Thanks in advance.

"required firmware version" only matters for actual eshop, and maybe console to console update transfers. nsp installers ignore it, at that point the only limiting factor is sdk version used for the title, or the master key used to encrypt it depending on if you use fusee or hekate to boot

even eshop wouldnt need to follow it, but by enforcing a newer firmware version to install or run updates it forces people to continue updating instead of staying behind

like, there's no technical reason that makes the newer firmware version "required". it's just a check that asks for firmware version, and the check just doesnt get done with most nsp installers

cdogg · 2024-11-23T17:28:57+0000

4d1xlaan said:
"required firmware version" only matters for actual eshop, and maybe console to console update transfers. nsp installers ignore it, at that point the only limiting factor is sdk version used for the title, or the master key used to encrypt it depending on if you use fusee or hekate to boot

even eshop wouldnt need to follow it, but by enforcing a newer firmware version to install or run updates it forces people to continue updating instead of staying behind

like, there's no technical reason that makes the newer firmware version "required". it's just a check that asks for firmware version, and the check just doesnt get done with most nsp installers

Oh nice. I'm still kinda weary about updating to FW 19. I figured if I installed a game/update that required 19 while I'm still on 18.1, it wouldn't boot after installing.

impeeza · 2024-11-23T18:55:10+0000

laz305 said:
for me it is L+DDWN+R+R JOY CON IN
and what do you press again to get back into Hekate while it is booting? I'm trying to use Auto RCM now.

if you have AutoRCM you can press VOL- while booting to open NYX (Hekate's GUI)

ShinLarc · 2024-11-23T23:06:33+0000

My game asks me to connect to the internet in order for it to start. This happens only after I restart the console after playing it initially. I will have to delete the ticket and re-install the game to play it every time. How can I fix this?

sley · 2024-11-24T13:21:29+0000

Can someone tell me what happened?

I updated my firmware and atmosphere to the newest version on emunand and then had trouble booting into it.
No problem maybe some sysmodules arent compatible so I deleted the entire atmosphere folder except the exosphere config because I blank my prodinfo to avoid connecting to the internet.

Afterwards I still had some trouble booting so I reconfigured my hekate ipl to instead of chainloading fusee to use this fss0 config:

Code:

[Atmosphere - SysNAND]
fss0=atmosphere/package3
kip1=atmosphere/kips/*
emummc_force_disable=1

[Atmosphere - EmuNAND]
fss0=atmosphere/package3
kip1=atmosphere/kips/*
emummcforce=1

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

Well that worked and it booted up again but for some reason I did not care about blanking my prodinfo and connected to the internet.
Also it started updating or downloading F Zero 99, a game that I only have installed on my clean Sysnand, casually alongside my forwarders and unsigned nsp homebrew.

Well if thats how I get banned after using cfw on this console since 2017 then so be it but what did I do wrong?

edit: okay I just noticed that I forgot to recreate the emummc.txt for blocking Nintendo servers, but even then why did exospheres settings get ignored?

THYPLEX · 2024-11-24T16:00:11+0000

I downloaded the HATS PACK on my switch and i use the overlay i see the color Orange on the syspatches , so It should be okay

impeeza · 2024-11-24T16:08:26+0000

THYPLEX said:
I downloaded the HATS PACK on my switch and i use the overlay i see the color Orange on the syspatches , so It should be okay

never use premade packages, READ AND LEARN what you put on your console.

AND PLEASE READ, READ, https://gbatemp.net/threads/sys-patch-sysmod-that-patches-on-boot.633517/post-10389798 THIS POST ON THE SYS-PATCH THREAD IS ONE OF THE TOO MUCH TIMES THE MEANING OF COLORS IS.

Hacking SWITCH NOOB PARADISE - Ask questions here

シュウ 「グラビトロンカノン 発射!」

Active Member

Well-Known Member

Well-Known Member

Active Member

¡Kabito!

Well-Known Member

Well-Known Member

I see what you did there

¡Kabito!

Similar threads

Popular threads in this forum

シュウ「グラビトロンカノン発射!」