Hacking SWITCH NOOB PARADISE - Ask questions here

rsx · Jun 24, 2024

Draxzelex said:
Was it working before? If so, what was the last thing you did before it stopped working?

It never worked. I followed nh-server's guide, one day i tried to load it out of curiosity and nothing.

Zap2000 · Jun 25, 2024

Hi I want to do an update from old Atmosphere to the lastest.
Which firmware would I be best install to get most out of this update as I’m running on order firmware also

rsx · Jun 25, 2024

Big problem: I updated Atmosphere/Hekate through AIO, updated sigpatches (more than once) deleted Tinfoil and all its remnants. Ran the tinfoil installer and it still says "unable to start software" but adds a shortcut to the home menu. Same problem with retroarch, but it does start through the images folder when disabling applet.

RedColoredStars · Jun 25, 2024

Zap2000 said:
Hi I want to do an update from old Atmosphere to the lastest.
Which firmware would I be best install to get most out of this update as I’m running on order firmware also

The latest. 18.1.0

rsx said:
Big problem: I updated Atmosphere/Hekate through AIO, updated sigpatches (more than once) deleted Tinfoil and all its remnants. Ran the tinfoil installer and it still says "unable to start software" but adds a shortcut to the home menu. Same problem with retroarch, but it does start through the images folder when disabling applet.

Try updating everything manually and using sys-patch instead of sigpatches. Update Atmos, Hekate, and Fusee first. Then put Tesla Menu, ovlloader, and sys-patch files on your SD card. Then your fw if not already on the latest. Also want to make sure your payloads are up to date.

Zap2000 · Jun 25, 2024

RedColoredStars said:
The latest. 18.1.0

Try updating everything manually and using sys-patch instead of sigpatches. Update Atmos, Hekate, and Fusee first. Then put Tesla Menu, ovlloader, and sys-patch files on your SD card. Then your fw if not already on the latest. Also want to make sure your payloads are up to date.

Yeah that latest. But I was asking what verson of firmware is best to use at this minute in time ?

RedColoredStars · Jun 25, 2024

Zap2000 said:
Yeah that latest. But I was asking what verson of firmware is best to use at this minute in time ?

The latest is the best. Most every new game requires the latest and many older titles have received updates that require the latest. So 18.1.0 is the best firmware to use at this minute in time.

rsx · Jun 25, 2024

RedColoredStars said:
The latest. 18.1.0

Try updating everything manually and using sys-patch instead of sigpatches. Update Atmos, Hekate, and Fusee first. Then put Tesla Menu, ovlloader, and sys-patch files on your SD card. Then your fw if not already on the latest. Also want to make sure your payloads are up to date.

Everything is working from Atmosphere except homebrew apps (Tinfoil, Retroarch were the only two installed). Homebrew works from the photo menu (when disabling applet mode).

Retail games, all working fine. I haven't updated my OFW (still on 18.0.1), just CFW.
I'm not using fusee, I installed with the NH Switch Guide on github (emunand)
This problem didn't pop up until I used the AIO updater to update Hekate/Atmosphere.

RedColoredStars · Jun 25, 2024

rsx said:
Everything is working from Atmosphere except homebrew apps (Tinfoil, Retroarch were the only two installed). Homebrew works from the photo menu (when disabling applet mode).

Retail games, all working fine. I haven't updated my OFW (still on 18.0.1), just CFW.
I'm not using fusee, I installed with the NH Switch Guide on github (emunand)
This problem didn't pop up until I used the AIO updater to update Hekate/Atmosphere.

Did you try deleting what AIO updated and updating them manually? I think people run into problems sometimes using AIO. Or try reinstalling Tinfoil and Retroarch? Are you using sigpatches or sys-patch? Maybe post your hekate_ipl.ini contents.

rsx · Jun 25, 2024

RedColoredStars said:
Did you try deleting what AIO updated and updating them manually? I think people run into problems sometimes using AIO. Or try reinstalling Tinfoil and Retroarch? Are you using sigpatches or sys-patch? Maybe post your hekate_ipl.ini contents.

I manually updated Atmosphere, Hekate, Sigpatches. Then deleted Tinfoil and Retroarch through DBI. Everything works in picture menu EXCEPT installing Tinfoil. I havent tried Retroarch yet.

I wanted to update my OFW but Rentry guide says to "Before you upgrade your devices firmware, please ensure to delete your /contents/ folder located in /atmosphere/."

I made a backup, deleted the files, then started atmosphere but now my themes are gone and nothing will load because it thinks everything is corrupt (except folder mode with applet).

ini is

[config]
updater2p=1

[Atmosphere FSS0 emuMMC]
fss0=atmosphere/package3
kip1=atmosphere/kips/*
emummcforce=1
icon=bootloader/res/emu_boot.bmp

[Atmosphere FSS0 sysMMC]
fss0=atmosphere/package3
kip1=atmosphere/kips/*
emummc_force_disable=1
icon=bootloader/res/sys_cfw_boot.bmp

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

Zap2000 · Jun 25, 2024

rsx said:
Everything is working from Atmosphere except homebrew apps (Tinfoil, Retroarch were the only two installed). Homebrew works from the photo menu (when disabling applet mode).

Retail games, all working fine. I haven't updated my OFW (still on 18.0.1), just CFW.
I'm not using fusee, I installed with the NH Switch Guide on github (emunand)
This problem didn't pop up until I used the AIO updater to update Hekate/Atmosphere.

I different guide I read advised me 17.0.1 that there was basic and bugs still on 18.0.1?

RedColoredStars · Jun 25, 2024

rsx said:
I manually updated Atmosphere, Hekate, Sigpatches. Then deleted Tinfoil and Retroarch through DBI. Everything works in picture menu EXCEPT installing Tinfoil. I havent tried Retroarch yet.

I wanted to update my OFW but Rentry guide says to "Before you upgrade your devices firmware, please ensure to delete your /contents/ folder located in /atmosphere/."

I made a backup, deleted the files, then started atmosphere but now my themes are gone and nothing will load because it thinks everything is corrupt (except folder mode with applet).

ini is

[config]
updater2p=1

[Atmosphere FSS0 emuMMC]
fss0=atmosphere/package3
kip1=atmosphere/kips/*
emummcforce=1
icon=bootloader/res/emu_boot.bmp

[Atmosphere FSS0 sysMMC]
fss0=atmosphere/package3
kip1=atmosphere/kips/*
emummc_force_disable=1
icon=bootloader/res/sys_cfw_boot.bmp

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

Try extracting this to root of your sd card, removing the kip1 lines from your ini file, reboot switch. See if things work then. https://gbatemp.net/threads/sigpatc...kate-fss0-fusee-package3.571543/post-10442256

rsx · Jun 25, 2024

RedColoredStars said:
Try extracting this to root of your sd card, removing the kip1 lines from your ini file, reboot switch. See if things work then. https://gbatemp.net/threads/sigpatc...kate-fss0-fusee-package3.571543/post-10442256

Homebrew works from the menu again, thank you!
Ok, what happened? What went wrong? Was I missing something, and am I safe to update my OFW?

RedColoredStars · Jun 25, 2024

rsx said:
Homebrew works from the menu again, thank you!
Ok, what happened? What went wrong? Was I missing something, and am I safe to update my OFW?

As long as everything is working, youre good to update ofw. It is recommended though, to update your emuMMC FW first, and then your sysMMC FW.

The problem was with sigpatches. It seems the latest are causing issues for some but not others. The solution was to use sys-patch instead of sigpatches. Glad it worked for you.

Edit: Or, your sigpatches were not up to date. Imo having you use sys-patch was the easier and better option.

rsx · Jun 25, 2024

RedColoredStars said:
As long as everything is working, youre good to update ofw. It is recommended though, to update your emuMMC FW first, and then your sysMMC FW.

The problem was with sigpatches. It seems the latest are causing issues for some but not others. The solution was to use sys-patch instead of sigpatches. Glad it worked for you.

Edit: Or, your sigpatches were not up to date. Imo having you use sys-patch was the easier and better option.

It had to be sigpatch issues on top of the latest cfw update because I installed 6.11.24 from sigma.
So onto this sys-patch, do I need to update those from a database like sigpatches?

I don't have emuMMC. It does not load anything and forces a hard reset. It says "Atmosphere FSS0 emuMMC" in hekate boot options but, goes nowhere. Only SysCFW (Atmosphere) and Stock sysMMC work.
Is there a way to fix that?

And assuming this all gets fixed, can you point me in the right direction for updating emuMMC and then sysMMC in that order? As I understand, just have to load daybreak then the ofw?

Post automatically merged: Jun 25, 2024

RedColoredStars said:
As long as everything is working, youre good to update ofw. It is recommended though, to update your emuMMC FW first, and then your sysMMC FW.

The problem was with sigpatches. It seems the latest are causing issues for some but not others. The solution was to use sys-patch instead of sigpatches. Glad it worked for you.

Edit: Or, your sigpatches were not up to date. Imo having you use sys-patch was the easier and better option.

Updated to 18.1, themes arent working and neither is tinfoil or anything else. Same problem. I'll revert to previous firmware with daybreak, what a headache.

RedColoredStars · Jun 26, 2024

rsx said:
It had to be sigpatch issues on top of the latest cfw update because I installed 6.11.24 from sigma.
So onto this sys-patch, do I need to update those from a database like sigpatches?

I don't have emuMMC. It does not load anything and forces a hard reset. It says "Atmosphere FSS0 emuMMC" in hekate boot options but, goes nowhere. Only SysCFW (Atmosphere) and Stock sysMMC work.
Is there a way to fix that?

And assuming this all gets fixed, can you point me in the right direction for updating emuMMC and then sysMMC in that order? As I understand, just have to load daybreak then the ofw?

Post automatically merged: Jun 25, 2024

Updated to 18.1, themes arent working and neither is tinfoil or anything else. Same problem. I'll revert to previous firmware with daybreak, what a headache.

You have to be missing something somewhere. Did you update your theme app and tinfoil? Is the theme iyself compatible? I dunno. Maybe someone else has some ideas.

hiberto · Jun 26, 2024

Was having problems with emuMMC and kept getting error when trying to boot atmosphere so created a new one on new sd card. Since I can't boot into the emuMMC, I can't use Checkpoint to back up my Animal Crossing save in Device Saves. I backed up the entire emuMMC on the "bad" card. I can access all the other saves by mounting the emuMMC partition of the "bad" card but don't know where the Device saves would be as Animal Crossing saves to that instead of the regular save folder in JKSV or Checkpoint. How can I access the Device save on the "bad" card so I can back it up and restore it to the new one?

testing123 · Jun 26, 2024

RedColoredStars said:
The latest. 18.1.0

Try updating everything manually and using sys-patch instead of sigpatches. Update Atmos, Hekate, and Fusee first. Then put Tesla Menu, ovlloader, and sys-patch files on your SD card. Then your fw if not already on the latest. Also want to make sure your payloads are up to date.

May I please ask how to actually update things? Assume I haven't updated my switch since the initial mod. I assume there's a guide somewhere that ELI5 step by step?

Dust2dust · Jun 26, 2024

testing123 said:
May I please ask how to actually update things? Assume I haven't updated my switch since the initial mod. I assume there's a guide somewhere that ELI5 step by step?

Manually updating is basically copying files to the SD card. You would download the latest versions of everything on your computer (usually zip files) then unzip to the root of your SD card. Do it in the same order that @RedColoredStars suggested. The final step would be to update the HOS firmware itself, to 18.1.0. You will do that with the Daybreak homebrew, already installed with Atmosphere.

KARRUB_ · Jun 26, 2024

beanz00_ said:
that fixed it, tysm i have been trying to fix this for so long and it finally works. I will restore my save data backup from JKSV now.

I encountered a similar problem but with the error code 2123-0001. when I open a game on emunand the console checks as if I were opening one of those online Nintendo emulators. I can't access any games this way... I tried updating the sigpatches but there seems to be nothing to do...

Zap2000 · Jun 26, 2024

How do I uninstall unwanted games updates and or DLC? But keep previous updates and base game?

Post automatically merged: Jun 26, 2024

from I updated my firmware CFW auto boots now when I inject payload
how do I boot hekate?

Hacking SWITCH NOOB PARADISE - Ask questions here

USA Modchip Installer

Well-Known Member

USA Modchip Installer

Well-Known Member

Well-Known Member

Well-Known Member

USA Modchip Installer

Well-Known Member

USA Modchip Installer

Well-Known Member

Well-Known Member

USA Modchip Installer

Well-Known Member

USA Modchip Installer

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

New Member

Well-Known Member

Similar threads

Popular threads in this forum