Hacking SWITCH NOOB PARADISE - Ask questions here

  • Thread starter Thread starter APartOfMe
  • Start date Start date
  • Views Views 5,985,231
  • Replies Replies 47,910
  • Likes Likes 66
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.
 
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

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.
 
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 ?
 
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. :)
 
  • Like
Reactions: Blythe93
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.
 
Last edited by rsx,
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.
 
  • Like
Reactions: Blythe93
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
 
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?
 
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
 
  • Like
Reactions: Blythe93
  • Like
Reactions: RedColoredStars
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.
 
Last edited by RedColoredStars,
  • Like
Reactions: Blythe93
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:

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.
 
Last edited by rsx,
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:


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.
 
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?
 
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?
 
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.
 
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...
 
How do I uninstall unwanted games updates and or DLC? But keep previous updates and base game?
Post automatically merged:

from I updated my firmware CFW auto boots now when I inject payload
how do I boot hekate?
 
What which part of the system can detect and see is absolutely relevant, because nintendo can't ban people for something, if they don't receive the info that its happening.
So lets take your example with the fuses, in theory they can detect it, because we know the boot loader checks it, but has any system module access to the fuses?
If I remember it correctly, mostly the bootloader and trustzone use the fuses directly, while the rest doesn't use them directly. So if I'm correct, then one of the components we know 100% what it does handles this, and we know for certain that its not send to Nintendo.
So there is a big difference between things the console can actually detect, and what Nintendo can detect about you as a company with its current firmware.
About people playing backups, I actually mentioned before, that they don't need to directly lead to a quick ban, as long as you are not connecting to the online services for usage with the game. I even used game XCIs via emulation in SXOS in the past, but always offline, and pretty much only to play games I preordered early. One of the switch consoles from my family even had a game NSP installed in the past and is still going online. That's why I said they can lead to a ban, in case ticket data gets send. One of the cases where ticket info is send, is during moments where the game connects to online servers, but its possible that there are other triggers where tickets might be synchronized. Its also easy to accidentally connect online in a game if people use a mixed nand, which is a big potential error source thats mitigated via emunand for people using backups.

The questionaire being limtied to yes and no questions helps a bit with the answers the users can answer, but it also has the potential, that smaller but important things are still not reported by the users, because they are not in it.
For example if somethings like tinfoil installed itself, the user would not put it in as them installeing NSPs. Even just installing their self dumped XCIs, or for some installing NSZ (or what it was) files can lead to the users reporting this as no, since they might not understand that its all the same. So the user will still only report it based on their level of knowledge, which is to be expected, but limits the ability of this data telling us that just CFW is problematic. It can tell us on the other side that some specific thigns might be problematic through, especially when combined with analysis of the system.
And Your point about lying only is importent if we expect the user to lie, but I never said they intentionally lie, I said that some answers might be wrong because of their lack of knowledge in some areas, which is not lying.
Also when a user is unsure about something, even just the way a question is asked can lead to different answer, which is why an eyewitness might sometimes report wrong info.

And about the ban proof, its easy to use sysdvr to proof I'm currently online in CFW and can go online in a game by just streaming it and using tesla overlays.
For the past on the other side, the evidence is not 100% water tight, since I might regularly use different switches, but its more likely I'm telling the truth as you mentioned.
For example based on the Fuse count and system error log I can also give good evidence about the likely timeframe in which I already use CFW, and that I never did a normal stock bootloader boot since then.
Also the newest entry in the error History under Settigns->Error History is a 2124-3001 from march 2020, before that there where regularly new entries, and not a single one after it.
Based on the play history its also possible to at least give move evidence that I used a switch a lot since then. I also have a public playlist with unlisted streams of splatoon from after the last error log, that where made using sysdvr, and probably also some local recordings, with some recordings probably also showing the FPS counter or somethings else from tesla.
I mean many, and I mean many, people were banned when they used .XCI files explicitly offline but updated them online while not even being in SX OS. In fact, these so called believers thought it was safe because there was no way supposedly for Nintendo to tell the difference between an offline .XCI file and a cart that you borrowed from your friend one time. But they were also proven wrong once they were all banned and nearly all around the same time too. Some of those users were doing this practice for upwards of an entire year. So its not really a matter of how but a matter of when.

Whether the questionnaire is faulty or not again is all stemming from your opinion and not objective fact. If there was such an incidence of a user misreporting something or misunderstanding something, then you might have some ground to stand on. But your viewpoint is based entirely on conjecture. Also, it was not as if I transcribed everyone's answers without proofreading them. There have been some times when people reported conflicting answers that don't make sense but I either corrected them based on the existing info or consulted them for clarification. And while the Google Doc answers aren't viewable to the public, the ones in the thread certainly are so if there's any doubts about people's answers, anyone can read them.

Lastly, as I stated, you streaming that you are not banned only proves that you are not banned in the moment for whatever you are doing at that time. It doesn't prove any of the actions you may have taken previously. That doesn't even prove your friends and family are safe for the same reasons. If you want to prove without a shadow of a doubt that everything you say you did is safe, then you would have to perform them all in the same livestream. But can you or them even remember every single little action you have ever taken? Of course not, that isn't practical. Heck if I were to play devil's advocate at your level of mistrust, I can go so far to claim that you swapped out certificates or motherboards. The point is progress isn't made by doubting everything you see, especially if its based on an opinion. The issues with exFAT, AutoRCM, and patched units all started with similar user submitted reports that were found to be conclusive. So rather than try to dismantle years of work and the effort of hundreds of users, try to let go of your bias and establish a new conclusion for the evidence presented before you.
hello i got i small question i opent my cfw sysmmc and downloaded a pirate game
is there a way to restore your sysNAND with a back up i did right after i modded my switch (clean sysNAND)
to avoid a ban (i havent connected tho the internet yet)

sorry fore my English

this is the back up i have i hope i can save my switch
View attachment 443644
Place all of those files onto your SD card and restore them via Hekate.
How do I uninstall unwanted games updates and or DLC? But keep previous updates and base game?
Post automatically merged:

from I updated my firmware CFW auto boots now when I inject payload
how do I boot hekate?
I supposed you can use DBI to uninstall specific game updates/DLC while retaining other updates and the base game. To load Hekate when auto boot is enabled, hold volume - when you send the Hekate payload. If you want to avoid auto boot entirely, go into your hekate_ipl.ini file and change the autoboot setting to 0.
 
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.

Thanks for your reply.

Would you say doing it manually is better than doing it automatically? I don't even know which program (i.e. Atmosphere?) to run to upgrade the firmware, etc.
 

Site & Scene News

Popular threads in this forum