Hacking SWITCH NOOB PARADISE - Ask questions here

  • Thread starter Thread starter APartOfMe
  • Start date Start date
  • Views Views 5,999,028
  • Replies Replies 47,915
  • Likes Likes 66
I am planning to switch from SXOS to atmosphere but I am concerned if I will be signifcantly more likely to be exposed to getting banned by installing NSPs. I'm a little out of the loop but last time i checked (around 2 years ago) installing NSPs to play a game are pretty much guaranteed to get you a ban. Has this change or will resorting to Atmosphere force me to accept getting banned immediately?

I still plan to play MHX Rise online so if thats the case, ill stay with my SXOS for awhile longer (i know that using sxos has an inherent risk of getting banned but after taking all precautions, i have avoid getting banned for several years).

If its possible to minimize a ban as much as possible like the sxos, any precautions before i start installing NSP?
 
I am planning to switch from SXOS to atmosphere but I am concerned if I will be signifcantly more likely to be exposed to getting banned by installing NSPs. I'm a little out of the loop but last time i checked (around 2 years ago) installing NSPs to play a game are pretty much guaranteed to get you a ban. Has this change or will resorting to Atmosphere force me to accept getting banned immediately?

I still plan to play MHX Rise online so if thats the case, ill stay with my SXOS for awhile longer (i know that using sxos has an inherent risk of getting banned but after taking all precautions, i have avoid getting banned for several years).

If its possible to minimize a ban as much as possible like the sxos, any precautions before i start installing NSP?

Installing arrrr-ware does increase your risk significantly, however, configuring exosphere.ini (similar to Incognito_RCM) and dns:mitm (similar to 90DNS but local) reduces the risk significantly as well. Most folks are caught either through ignorance or carelessness and even then, no plan is fool proof except for 100% abstinence, but what fun is that? At the end of the day you will need to make that call for you.
 
Hi I need big help yesterday I thought I had good progress updating installing atmosphere and updating firmware to lastest on emunand using daybreak
then today I log in to check and noticed my sysnand and emmunand where on the same versions from I updated from daybreak and I had tinfoil install both sysnand and emmunand!! What should I do?

Can someone please advise what happened? And what I should do?
 

Attachments

  • CBAC97D7-D2CE-4336-B3B3-AFBB0B4A3B26.jpeg
    CBAC97D7-D2CE-4336-B3B3-AFBB0B4A3B26.jpeg
    1.4 MB · Views: 72
  • D09BE5C0-B413-4D50-8E09-359F26480B7E.jpeg
    D09BE5C0-B413-4D50-8E09-359F26480B7E.jpeg
    1.4 MB · Views: 85
I’m also getting these messages if they mean anything I worried I messed up completely and if possible to fix my sysnand
 

Attachments

  • FC528CBC-67D2-4DA0-865A-69188992098F.jpeg
    FC528CBC-67D2-4DA0-865A-69188992098F.jpeg
    1.3 MB · Views: 64
  • DF777291-6586-491A-9CDF-7E1F79851AE0.jpeg
    DF777291-6586-491A-9CDF-7E1F79851AE0.jpeg
    1.4 MB · Views: 82
  • 1A8B4D44-BEFF-4F6B-B9E4-69D52AD8D6F8.jpeg
    1A8B4D44-BEFF-4F6B-B9E4-69D52AD8D6F8.jpeg
    1.2 MB · Views: 75
  • 3B20357A-5277-44DC-8544-773454C5615B.jpeg
    3B20357A-5277-44DC-8544-773454C5615B.jpeg
    1.3 MB · Views: 65
Does it seem I made sysnand and not emmunand??

Also I selected yesterday when doing this
  • To create a partition-based Emunand:
    • Move the emuMMC (RAW) slider until it says 29 full, then press Next Step and finally press Star

What can I do to recover this?
 
Hi I need big help yesterday I thought I had good progress updating installing atmosphere and updating firmware to lastest on emunand using daybreak
then today I log in to check and noticed my sysnand and emmunand where on the same versions from I updated from daybreak and I had tinfoil install both sysnand and emmunand!! What should I do?

Can someone please advise what happened? And what I should do?

No idea what you did. Having everything up to date isnt a bad thing. Just be more careful in the future.

I’m also getting these messages if they mean anything I worried I messed up completely and if possible to fix my sysnand

We’ve not talked about anything under More Configurations so Imwould expect it to be blank.

The fact that you’ve somehow lost your /bootloader/hekate_ipl.ini is concerning. Not much detail in this post so all I can recommend is that you go back into the instructions and create a new hekate_ipl.ini the same way we did yesterday.

Does it seem I made sysnand and not emmunand??

Sysnand always exists. You only ever create Emunand (as a copy of Sysnand.)

Also I selected yesterday when doing this
  • To create a partition-based Emunand:
    • Move the emuMMC (RAW) slider until it says 29 full, then press Next Step and finally press Star

What can I do to recover this?

No need to recover anything except for your hekate_ipl.ini which you can do from scratch based on the guide.
 
  • Like
Reactions: Blauhasenpopo
No idea what you did. Having everything up to date isnt a bad thing. Just be more careful in the future.



We’ve not talked about anything under More Configurations so Imwould expect it to be blank.

The fact that you’ve somehow lost your /bootloader/hekate_ipl.ini is concerning. Not much detail in this post so all I can recommend is that you go back into the instructions and create a new hekate_ipl.ini the same way we did yesterday.



Sysnand always exists. You only ever create Emunand (as a copy of Sysnand.)



No need to recover anything except for your hekate_ipl.ini which you can do from scratch based on the guide.


I think I didn’t launch emmunand and made a partition on my sysnand
Does the below photo mean sysnand not emunand
 

Attachments

  • 53C88291-6BF5-48A0-8CED-88A88495BF1B.png
    53C88291-6BF5-48A0-8CED-88A88495BF1B.png
    3.1 MB · Views: 62
I think I didn’t launch emmunand and made a partition on my sysnand
Does the below photo mean sysnand not emunand


Also is it bad that I have updated my whole system with daybreak? Made sysnand dirty?
If Launch without CFW I’m on latest firmware with tinfoil installed. And if I launch cfw im on that that firmware that I took picture of does that mean I sysnand?

I’m not sure what guide I should be following? because I’m not sure if I have sysnand or emunand running.
Should I post my sd card pictures for you to check my
hekate_ipl.ini?

Also when I hit launch I get nothing only that message that I posted on one of the photos is that normal?
 
Last edited by Zap2000,
Is this normal to have tinfoil installed without running cfw?

And under emu mmc is says disabled is that normal? See photo
 

Attachments

  • 35742754-A6F7-4F3F-B4C8-442D70708D98.jpeg
    35742754-A6F7-4F3F-B4C8-442D70708D98.jpeg
    1.5 MB · Views: 57
also go

hekatePublic​

Waarning: Nyx is missing​


last reboot gone now


also tinfoil is on my switch even without sd card in how is that??
 
Last edited by Zap2000,
also go

hekatePublic​

Waarning: Nyx is missing​


last reboot gone now


also tinfoil is on my switch even without sd card in how is that??
Post the text of your hekate_ipl.ini. It looks to me like you messed up the entries, and you've installed tinfoil onto your sysnand. If nyx says emummc is disabled, then it's disabled. You are missing /emuMMC/emummc.ini (or the entry in it is wrong).
 
Last edited by urherenow,
Is there a way to customise the album icon atmosphere? Hold L or R when pressing the icon to go in HBL?
https://github.com/WerWolv/Hekate-Toolbox will handle it for you via a GUI.

You can manually edit the file called:

/atmosphere/config/override_config.ini

This is how mine is set up…

add the following to make pressing “R” required to get to the hb menu

Code:
[hbl_config]
override_key=R
program_id=010000000000100d


to change it to L, well, you get the picture…

if you want to go back to the original way just put a “!” In front of the “R” like so

Code:
override_key=!R

* a blank template file can be found in /atmosphere/config_templates/
 
Post the text of your hekate_ipl.ini. It looks to me like you messed up the entries, and you've installed tinfoil onto your sysnand. If nyx says emummc is disabled, then it's disabled. You are missing /emuMMC/emummc.ini (or the entry in it is wrong).
i reformating my sd card my mistake i have to set everything up again and going to try again . i did notice i had a tinfoil installer in the root of my sd card
that text you asked for is as follows in my new sd card


[config]
autoboot=0
autoboot_list=0
bootwait=3
backlight=100
autohosoff=0
autonogc=1
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

can we check all my card again as im starting from start
 
i reformating my sd card my mistake i have to set everything up again and going to try again . i did notice i had a tinfoil installer in the root of my sd card
that text you asked for is as follows in my new sd card


[config]
autoboot=0
autoboot_list=0
bootwait=3
backlight=100
autohosoff=0
autonogc=1
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

can we check all my card again as im starting from start
Well, as you can see, there is nothing in here that says emuMMC which explains why you aren't booting emuMMC. If you want to boot emuMMC, you will need a profile in your hekate_ipl.ini file that can boot emuMMC. You can download one from here
 
Well, as you can see, there is nothing in here that says emuMMC which explains why you aren't booting emuMMC. If you want to boot emuMMC, you will need a profile in your hekate_ipl.ini file that can boot emuMMC. You can download one from here
Where are those "profiles"?
 
They're located in the hekate_ipl.ini file. This is what Hekate reads then displays under the Launch feature.
Sorry, my fault...i meant the hekate_ipl.ini file with said profiles ...are there place to download different ini files?
Ican't find the ini file on the sd setup page...
 
Where are those "profiles"?
You make them. Like:

[CFW - emuMMC]
fss0=atmosphere/package3
emummcforce=1
kip1patch=nosigchk
atmosphere=1
icon=bootloader/res/icon_payload.bmp

But you also need a proper emummc.ini, located in /emummc. Already forgot what kind you are using. It's easy if you're using file-based, just follow the readme. For my partition-based (first partition as it was originally created by SX):

[emummc]
enabled=1
sector=0x2
path=emuMMC/RAW1
id=0x0000
nintendo_path=Emutendo

Both of these things existing and proper, nyx should tell you that emummc is enabled. And although undesirable if you intend on using an old firmware (why? seriously?). autonogc=1 is undesirable and causes a black screen in MANY circumstances if you dare boot your console with a game cart in the slot. If your sysnand is like 4.0.1 and you want to keep it there, more power to you. If it's above 4.0.1 there is seriously no point. Change that to a 0.
 
i reformating my sd card my mistake i have to set everything up again and going to try again . i did notice i had a tinfoil installer in the root of my sd card
that text you asked for is as follows in my new sd card


[config]
autoboot=0
autoboot_list=0
bootwait=3
backlight=100
autohosoff=0
autonogc=1
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

can we check all my card again as im starting from start

edit: at this point I recommend you start from scratch…too many things have mysteriously changed Overnight.

your hekate_ipl.ini looks good. It must but that you’ve managed to corrupt your emmunand. It might be best to start from scratch at this point.

here it is from the docs.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
[config]
autoboot=0
autoboot_list=0
bootwait=3
backlight=100
autohosoff=0
autonogc=1
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


By default stock=0 emmunand_force_disable =0 so you don’t need to call them out specifically to boot into emunand.
 
Last edited by binkinator,

Site & Scene News

Popular threads in this forum