Hacking SWITCH NOOB PARADISE - Ask questions here

[Hayato213]

ok. thank you


about this ?

If you had set up nogc with bct.ini previously, please ensure to check this guide. bct.ini is no longer present on the latest atmosphere version. ???

Follow the instruction on that link that you linked.

 

[0Futurisma0]

Follow the instruction on that link that you linked.

the guide sais to ----Before you upgrade Atmosphere, please ensure to delete your /contents/ folder located in /atmosphere/.


all i see in my atmosphere folder are these. do i leave them there and proceed ? or delete all these items and leave the atmosphere folder completely empty ?

 

[Hayato213]

the guide sais to ----Before you upgrade Atmosphere, please ensure to delete your /contents/ folder located in /atmosphere/.


all i see in my atmosphere folder are these. do i leave them there and proceed ? or delete all these items and leave the atmosphere folder completely empty ?

Please follow the instructions, delete the entire atmosphere folder and replace it with new one.

 

[0Futurisma0]

Please follow the instructions, delete the entire atmosphere folder and replace it with new one.

ok. i followed the guide. now what ?

 

[Dust2dust]

ok. i followed the guide. now what ?

Profit? What was your goal, anyway, before you started this process? If it was just to update your system, then you're done.

 

[0Futurisma0]

Profit? What was your goal, anyway, before you started this process? If it was just to update your system, then you're done.

so i inject fusseee bin and then update from online mode ?

 

[RedColoredStars]

The sigpatch.zip from the rentry guide contain a folder atmosphere\contents\420000000000000B

Inside of that folder are exefs.nsp, toolbox.json, and another folder titled flags. inside the flags folder is the file boot2.flag.

If I open the toolbox.json file it says:
"name" : "sys-patch",
"tid" : "420000000000000B",
"requires_reboot": false

The sigpatch folder from the thread linked below doesn't contain the "content" folder at all & I've seen many mentions of it being safe to delete if a person has no themes or game mods. I have no themes or mods so what are that folder/files doing? Why does the rentry guide include it but not the files from here? Can I delete or no?
https://gbatemp.net/threads/sigpatches-for-atmosphere-hekate-fss0-fusee-package3.571543/

 

[Blythe93]

So what are that folder/files doing? Why does the rentry guide include it but not the files from here? Can I delete or no?

It's a sys-patch module, an alternative to sigpatches. It's okay to have both of them at the same time. Sadly, sys-patch was recently taken down by Nintendo, so whether its development will continue remains to be seen. ghjfdtg uploaded the latest version before it was taken down along with its source code. impeeza uploaded it to the GBATemp's Downloads section as well (here and here).

 

[RedColoredStars]

It's a sys-patch module, an alternative to sigpatches. It's okay to have both of them at the same time. Sadly, sys-patch was recently taken down by Nintendo, so whether its development will continue remains to be seen. ghjfdtg uploaded the latest version before it was taken down along with its source code. impeeza uploaded it to the GBATemp's Downloads section as well (here and here).

Thanks. I am reading about that now. I noticed there was also a sigpatch updater nro file that was taken down/removed also. Is that of any benefit to have? And theoretically speaking, if a person wanted to only have the sys-patch module and not sigpatches... they could remove the line kip1patch=nosigchk (for fss0) or atmosphere=1 (for chainloading fusee) from their emuMCC booting options in the hekate ini file?

 

[Blythe93]

I noticed there was also a sigpatch updater nro file that was taken down/removed also. Is that of any benefit to have?

Other than getting the latest sigpatches from the website mentioned in the archived github page's description, I don't really see a point in having it. Neither app nor sys-patch module will be updated for the time being unless someone else takes over.

And theoretically speaking, if a person wanted to only have the sys-patch module and not sigpatches... they could remove the line kip1patch=nosigchk (for fss0) or atmosphere=1 (for chainloading fusee) from their emuMCC booting options in the hekate ini file?

I'm not familiar with how it actually works so I can't say for sure, but I believe that you're correct.

 

[RedColoredStars]

Other than getting the latest sigpatches from the website mentioned in the archived github page's description, I don't really see a point in having it. Neither app nor sys-patch module will be updated for the time being unless someone else takes over.

I'm not familiar with how it actually works so I can't say for sure, but I believe that you're correct.

Thanks again. I think I'll just delete the entire atmosphere\contents\420000000000000B folder. If the neither the module or updater nro have a whole lot of a chance to be updated I'll stick with sigpatches unless something should change in the future.

Post automatically merged: Mar 19, 2024

Does the rentry guide have a mistake then? It appears that booting emuMCC with fss0 is required for Hekates Auto NGC setting to work, but the rentry guide sets it up to sideload fusee. I do know for a fact that rentrys patches.ini file is unorganized and has some duplicate entries that could be cleaned up.

 

[Dust2dust]

so i inject fusseee bin and then update from online mode ?

I'm not sure where you're standing right now. You said previously you followed the guide, yet you're now saying you're not updated. What did you do, exactly? Anyway, assuming you just want to update your console to the latest, follow the guide (PC method, not the Switch method). Always best to do it manually instead of using AIO. The general order to follow is to update Hekate, Atmosphere and sigpatches first, and once all this is done and tested working properly, then you update the firmware with daybreak (comes pre-installed with Atmosphere). The firmware files can be acquired with just a simple search on Google. Doing all this should result in your Switch fully updated and able to play the latest games. By the way, you should also update the payload you inject with TegraRCMGUI. If it's fusee.bin, then get the one from the latest Atmosphere.

 

[0Futurisma0]

I'm not sure where you're standing right now. You said previously you followed the guide, yet you're now saying you're not updated. What did you do, exactly? Anyway, assuming you just want to update your console to the latest, follow the guide (PC method, not the Switch method). Always best to do it manually instead of using AIO. The general order to follow is to update Hekate, Atmosphere and sigpatches first, and once all this is done and tested working properly, then you update the firmware with daybreak (comes pre-installed with Atmosphere). The firmware files can be acquired with just a simple search on Google. Doing all this should result in your Switch fully updated and able to play the latest games. By the way, you should also update the payload you inject with TegraRCMGUI. If it's fusee.bin, then get the one from the latest Atmosphere.

ok. so i am at the point where hekate and atmosphere is updated. i followed the guide for these two . there was nothing else in the guide. is there another guide from this point on so i dont mess up the switch. also i read that i should have deleted themes before anything else and that i didnt do it. i repeat i am at the point where i deleted last atmosphere added the new one and the same with hekate. i added the new one with new ini. file. what i do now ? the sd card is still in the pc and the switch is closed. thank you

 

[Dust2dust]

ok. so i am at the point where hekate and atmosphere is updated. i followed the guide for these two . there was nothing else in the guide. is there another guide from this point on so i dont mess up the switch. also i read that i should have deleted themes before anything else and that i didnt do it. i repeat i am at the point where i deleted last atmosphere added the new one and the same with hekate. i added the new one with new ini. file. what i do now ? the sd card is still in the pc and the switch is closed. thank you

Yes, themes should be removed before any updating process. I don't use themes, I consider them just a hindrance to a good working CFW Switch. But to each their own, of course. So delete any themes, remove old Atmosphere and Hekate (by deleting "atmosphere" folder and the contents of "bootloader" folder except hekate_ipl.ini and nyx.ini). and replace with new ones. Update your Sigpatches, and you should be ok to update the firmware then. Note that you can do all that without taking out the SD card from your Switch. Just use Hekate's USB feature. The Switch SD card slot is a bit flaky and can break easily, so it's better to not mess with it too much. My SD card hasn't moved from my Switch in years.

 

[enochlinux]

How does a modchip affect your switch? I'm considering installing one after having infinite trouble w mine. How hard are they to install compared to rebuilding a PC?

 

[Hayato213]

How does a modchip affect your switch? I'm considering installing one after having infinite trouble w mine. How hard are they to install compared to rebuilding a PC?

If you installed a modchip for like an unpatched/ RCM exploitable unit you won't have to use a computer/phone/payload dongle to inject payload. Patched unit above 4.1.0 needs modchip to access CFW, as for difficulty it come down to your soldering skills, if you can't solder then it ain't for you.

 

[Oriordan]

Hello
Can i install a chip in an unpatched switch ? I am tired of using rcm each time.

Post automatically merged: Mar 21, 2024

If you installed a modchip for like an unpatched/ RCM exploitable unit you won't have to use a computer/phone/payload dongle to inject payload. Patched unit above 4.1.0 needs modchip to access CFW, as for difficulty it come down to your soldering skills, if you can't solder then it ain't for you.

Does the chip on unpatched switch boot without problem ?

 

[Deleted member 678442]

Hello
Can i install a chip in an unpatched switch ? I am tired of using rcm each time.

Post automatically merged: Mar 21, 2024

Does the chip on unpatched switch boot without problem ?

Even if you use an RCMLoader? It doesn’t take that much time and effort.
But to answer your question. I don’t see why not? Just follow the guides for a patched console

 

[Oriordan]

Even if you use an RCMLoader? It doesn’t take that much time and effort.
But to answer your question. I don’t see why not? Just follow the guides for a patched console

Yes i know, i have rcm loader, but i want the automatic boot because the kids forget everytime to use the rcm loader and so they launch the games and they get corrupted and i have to reinstall them, i want to avoid all this trouble.

 

[Blythe93]

How to link proper NNID on emuNAND if sysNAND didn't previously had any accounts linked to it, without updating the stock firmware to the latest version?

I have a clean sysNAND (firmware 16.1.0) and I would like to keep its firmware the lowest possible, just in case an exploit gets released and work on that version of the firmware. Chances are probably slim, but I'd still like to have that option.

The game in question that I need it for is the Animal Crossing: New Horizons and, without a linked NNID account, you don't have an access to the Mario-themed promotional items. I've tried with linkalho by adding fake NNIDs but, sadly, that doesn't seem to work.

On another hacked Switch of mine, I do have a linked NNID on my emuNAND and, of course, Mario-themed items are available.

My second question is: Can I make a linkalho backup on the second Switch and restore that same backup on my first Switch? Is that a safe thing to do? Accounts have the same name, if that means anything?

Thank you for your time.