Hacking SWITCH NOOB PARADISE - Ask questions here

  • Thread starter Thread starter APartOfMe
  • Start date Start date
  • Views Views 6,004,910
  • Replies Replies 47,917
  • Likes Likes 66
Hmmmm copied everything, booted in RCM with dongle and jig but SX says this icone with boot.dat ? https://www.google.com/search?q=sx+...UP4MWAMA&bih=962&biw=2560&client=firefox-b-lm

I have the SX pro (black dongle) and I took the SX gear files from rentry. No idea what is wrong but it was quick to reach the first error :D


I have formatted the SD one more time, put the files again and this time it worked... During the first try I booted in the normal firmware to charge the dongle and it told me that there was something with the SD card, maybe something went wrong when I started in normal firmware or before... let's continue
 
Last edited by Temaps,
  • Love
Reactions: binkinator
Ok, so basically the steps would be:
1. Transfer the user from Oled to modded swtich
2. Create the emuNAND
3. Back-up save files in emuNAND (for example) using jksv
4. Edit the save files
4. Restore the edited save files then transfer save files from emuNAND to sysNAND using the mehtod of this video by Reclaimer Shawn:
5. Transfer user from stock to Oled Model again

Ignoring what Nintendo considers cheating, the steps should be alright?
For example, doing this process to edit a weapon in Zelda BotW (I suppose it isn't an online game) wouldn't be a problem, right?

Well I wish there was a text-based guide that showed you how to move the save files from emuMMC to sysMMC but from what I can find, that video seems to be the only guide so I suppose its better than nothing. I would highly recommend backing up your eMMC and BOOT0/1 before following the video as many people have run into trouble after watching a YouTube video. Other than that potential safety hazard, the steps you outlined are fine.
 
  • Like
Reactions: binkinator
The ipl file configuration:

[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
[Warmboot Error Fix]
fss0=atmosphere/package3
stock=1
emummc_force_disable=1
icon=bootloader/res/icon_switch.bmp

Yes, I made sure to update fusee.bin according to each version attempted.
Don’t see anything that would stop you from booting. Please go into Hekate and tap the emuMMC tile and take a screen shot to post here. Looking to make sure you have emunand in place.
 
Well I wish there was a text-based guide that showed you how to move the save files from emuMMC to sysMMC but from what I can find, that video seems to be the only guide so I suppose its better than nothing. I would highly recommend backing up your eMMC and BOOT0/1 before following the video as many people have run into trouble after watching a YouTube video. Other than that potential safety hazard, the steps you outlined are fine.
I see.
I just tried it and it seems to work. I created a new user test it and then play Pokémon Brilliand Diamond and then I used Pkhex to put 1 potion and 1 pokédollar in my bag.
Now I don't know what else to do with a modded switch. I just did all this process to import the Platinum Style outfit that was available until February 21, 2022.
 
I see.
I just tried it and it seems to work. I created a new user test it and then play Pokémon Brilliand Diamond and then I used Pkhex to put 1 potion and 1 pokédollar in my bag.
Now I don't know what else to do with a modded switch. I just did all this process to import the Platinum Style outfit that was available until February 21, 2022.
What can't you do with a hacked console? Well, the answer is simply play online but given that the scene has been around for a few years, there's something for everyone. You can always mod your favorite games to change the experience. Or you can overclock the Switch to make games run smoother. There are also emulators you can boot up to run some of the older classics on the go. Alternatively, you can mess around with some of the homebrew games that people have either ported or developed themselves. Last but certainly not least is piracy which although we can't stop users from doing, it is an option that everyone is aware of. Even then, I bet there's one or two things I failed to mention that you can do now that your console is now modded.
 
  • Like
Reactions: PercuOcto
I have a black screen when I boot into atmosphere. I have all the spashscreen up to the nintendo splashscreen (including this last one)... but then black screen I have to keep the power off button for like 10 seconds to shut down the switch...
 
I have a black screen when I boot into atmosphere. I have all the spashscreen up to the nintendo splashscreen (including this last one)... but then black screen I have to keep the power off button for like 10 seconds to shut down the switch...
What does the contents of your /bootloader/hekate_ipl.ini look like?

Please post that and a screenshot of your emuMMC tab in Hekate so we can make sure your emunand is enabled
 
What can't you do with a hacked console? Well, the answer is simply play online but given that the scene has been around for a few years, there's something for everyone. You can always mod your favorite games to change the experience. Or you can overclock the Switch to make games run smoother. There are also emulators you can boot up to run some of the older classics on the go. Alternatively, you can mess around with some of the homebrew games that people have either ported or developed themselves. Last but certainly not least is piracy which although we can't stop users from doing, it is an option that everyone is aware of. Even then, I bet there's one or two things I failed to mention that you can do now that your console is now modded.
Oh yeah, that's right. I will try modding Pokémon Sw to scale Pokémons sizes and put some mods in SSBU.
 
hekate_ipl.ini is

[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

Also tried with the hekate_ipl.ini that is provided with the sigpatches on the gbatemp forum but same when I boot in emuMMC

emunand activated, picture to be uploaded soon => uploaded

SD root :
/atmosphere
/bootloader
/emuMMC
/firmware
/switch
boot.dat
boot.ini
hbmenu.nro
payload.bin

Hekate splashscreen = ok
Atmosphere splashscreen = ok (therer are 2, one full and one with only the logo with a black background)
Switch splashscreen = ok
Then... nothing

Found a comment on a random forum from someone saying that this could happen if the sysNAND has a higher version than the emuNAND but I don't know how this can be possible as I just made an emuNAND with hekate so I guess it has used the same firmware version as the sysNAND ?
To be honest I updated the emuNAND with SX OS but that was on the SX OS emunand and I booted couple hours ago in my sysNAND it is still v 5. sometohing (5.1.0). Anyway, this should not have an impact now, the SX OS emunand is removed

By the way, I am using the latest files : Atmosphere [v1.4.1] + hbl [v2.4.3] + hbmenu [3.5.1] from atmosphere github
sigpatches Hekate+AMS-package3-sigpatches-1.4.1-cfw-15.0.1 attached to the first post from https://gbatemp.net/threads/sigpatches-for-atmosphere-hekate-fss0-fusee-package3.571543/
Am I using the sigpatches for FW15.0.1 that ONLY works for 15.0.1 and I have to use the sigpatches for my switch emuNAND firmware 5.1.0 then update to 15.0.1 then put the new sigpatches (15.0.1) ? => looks like the sigpatches works from FW 2.0.0 to 15.0.1
 

Attachments

  • emuMMC.jpg
    emuMMC.jpg
    186.8 KB · Views: 56
Last edited by Temaps,
Hi!
I have a Switch v1 Erista with an SX Core installed, running SX OS 3.0.5 and EmuNAND enabled, system version 10.2.0.

After a long time of not using the console I wanted to go online, so I booted the OFW (or maybe even did a genuine boot, I can't remember), and when trying to go online I was prompted for a system update (I think 15.x).
I did not remember all the matters about system updates, so I accepted. After that, I'm unable to boot the OFW or do a genuine boot.
From what I'm reading around, I guess that the system update is not supported by the old version of the now-dead SX OS, or maybe it has something with blowing the fuses.

Is there any way to fix this? If it helps, I found on my PC a NAND backup that I did when I installed SX OS the first time (but I'm not sure if I did it before or after, it's been years).
p.s. I found installed Choidujournx, I don't remember if at some point I used it to update OFW/CFW.

Thank you!
 
Hi
what method would you recommend to be able to replace files, install update, firmwares or games without having to remove the SD card from the switch bring it over to the pc and bring it back, or pluging it into the computer, transfert files with a wifi connection, ftp or share
with the ntp mode of dbi is pretty simple but that would be great to do it over the air
I guess there are risk of removing the plane mode (wifi off)
 
Help.
i wanted to play a game in the stock nand and the console asked me to update the console in order to play tbe game,, so I did. But now when I try to go to emunand it says:

"A fatal error ocurred whe running Fusse.
Unable to identify package1!


Press POWER to reboot."
 
hekate_ipl.ini is

[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

Also tried with the hekate_ipl.ini that is provided with the sigpatches on the gbatemp forum but same when I boot in emuMMC

emunand activated, picture to be uploaded soon => uploaded

SD root :
/atmosphere
/bootloader
/emuMMC
/firmware
/switch
boot.dat
boot.ini
hbmenu.nro
payload.bin

Hekate splashscreen = ok
Atmosphere splashscreen = ok (therer are 2, one full and one with only the logo with a black background)
Switch splashscreen = ok
Then... nothing

Found a comment on a random forum from someone saying that this could happen if the sysNAND has a higher version than the emuNAND but I don't know how this can be possible as I just made an emuNAND with hekate so I guess it has used the same firmware version as the sysNAND ?
To be honest I updated the emuNAND with SX OS but that was on the SX OS emunand and I booted couple hours ago in my sysNAND it is still v 5. sometohing (5.1.0). Anyway, this should not have an impact now, the SX OS emunand is removed

By the way, I am using the latest files : Atmosphere [v1.4.1] + hbl [v2.4.3] + hbmenu [3.5.1] from atmosphere github
sigpatches Hekate+AMS-package3-sigpatches-1.4.1-cfw-15.0.1 attached to the first post from https://gbatemp.net/threads/sigpatches-for-atmosphere-hekate-fss0-fusee-package3.571543/
Am I using the sigpatches for FW15.0.1 that ONLY works for 15.0.1 and I have to use the sigpatches for my switch emuNAND firmware 5.1.0 then update to 15.0.1 then put the new sigpatches (15.0.1) ? => looks like the sigpatches works from FW 2.0.0 to 15.0.1

Temporarily move your /atmosphere/contents to /atmosphere/contents.bk and reboot to try again. This will make sure there are no themes or sysmodules in play. PLMk if this fixes things.
Post automatically merged:

Help.
i wanted to play a game in the stock nand and the console asked me to update the console in order to play tbe game,, so I did. But now when I try to go to emunand it says:

"A fatal error ocurred whe running Fusse.
Unable to identify package1!


Press POWER to reboot."
You upgraded to FW 16.0.0? You[ER going to have to wait until the new Atmosphere is released.

https://gbatemp.net/threads/nintend...eleased-atmosphere-update-coming-soon.626526/
Post automatically merged:

Hi
what method would you recommend to be able to replace files, install update, firmwares or games without having to remove the SD card from the switch bring it over to the pc and bring it back, or pluging it into the computer, transfert files with a wifi connection, ftp or share
with the ntp mode of dbi is pretty simple but that would be great to do it over the air
I guess there are risk of removing the plane mode (wifi off)
Yes there is risk but you can lessen it greatly by masking your Prodinfo (serial number) using exosphere.ini and blocking access to Ninty servers by configuring dns:mitm. Both come with Atmosphere. Here is a link on how to set it up.

https://rentry.org/ExosphereDNSMITM

Once that is complete, you can test everything is blocked with 90DNS tester.

  • 90DNSTester -- DNS tester to make sure Ninty can't find you while playing hide-n-seek!

At that point you can install sys-Ftpd-lite. It’s the one I use because it runs as a Sysmodule at boot up so you don’t have to turn it on/off.

Post automatically merged:

Hi!
I have a Switch v1 Erista with an SX Core installed, running SX OS 3.0.5 and EmuNAND enabled, system version 10.2.0.

After a long time of not using the console I wanted to go online, so I booted the OFW (or maybe even did a genuine boot, I can't remember), and when trying to go online I was prompted for a system update (I think 15.x).
I did not remember all the matters about system updates, so I accepted. After that, I'm unable to boot the OFW or do a genuine boot.
From what I'm reading around, I guess that the system update is not supported by the old version of the now-dead SX OS, or maybe it has something with blowing the fuses.

Is there any way to fix this? If it helps, I found on my PC a NAND backup that I did when I installed SX OS the first time (but I'm not sure if I did it before or after, it's been years).
p.s. I found installed Choidujournx, I don't remember if at some point I used it to update OFW/CFW.

Thank you!
Last working firmware for SXOS was 11.0.0. You will need to switch to Atmosphere to do this. Unfortunately if you just upgraded you will be on 16.0.0 which just came out. We are all waiting for the new compatible Atmosphere build to be released. It might take a few days so kick back and enjoy the ride. Here is some light reading on how to switch to Atmosphere while you wait.

https://rentry.org/mys8q
 
Last edited by binkinator,
  • Like
Reactions: fadafwet
When trying to Run FTP server through DBI, I get this error message:
Code:
Allocate socket failed: No buffer space available

Does anyone know how I might resolve the issue?
 
When trying to Run FTP server through DBI, I get this error message:
Code:
Allocate socket failed: No buffer space available

Does anyone know how I might resolve the issue?
Probably too many sys-modules running OR maybe you can start HBMenu in title override mode in order to start DBI.
 
Temporarily move your /atmosphere/contents to /atmosphere/contents.bk and reboot to try again. This will make sure there are no themes or sysmodules in play. PLMk if this fixes things.

I do not have a folder called /contents in /atmosphere. I have downloaded atmosphere again and this folder do not exist.
And I did not installed/used sysmodules nor themes.

PLMk if this fixes things
What is PLMk ?

edit : I have removed everything from the SD, removed the partition on the SD for emuNAND and doing everything all over again... Never thought Atmosphere was so difficult to setup
=> Emunand just finished... it is activated but still black screen after switch logo... I'm desperately lost

So basically :
- Atmosphere (from github) + hekate (from githuv) + sigpatches (from gbatemp)
- Switch on 5.1.0
- Hekate works perfectly, I made a partition emunand + nand backup
- Do not work to start the switch (black screen after nsw bootlogo)

- did the same with emunand on files
- This seems a bit slower when booting (the bootlogo stays longer like 1 sec more)
- It works... Wait WHAT ?????

How on earth can I be the only one having this issue and not being able to boot with emunand on partition ???
 
Last edited by Temaps,
I do not have a folder called /contents in /atmosphere. I have downloaded atmosphere again and this folder do not exist.
And I did not installed/used sysmodules nor themes.


What is PLMk ?
Apologies. It’s Please Let Me Know.
edit : I have removed everything from the SD, removed the partition on the SD for emuNAND and doing everything all over again... Never thought Atmosphere was so difficult to setup
=> Emunand just finished... it is activated but still black screen after switch logo... I'm desperately lost

So basically :
- Atmosphere (from github) + hekate (from githuv) + sigpatches (from gbatemp)
- Switch on 5.1.0
- Hekate works perfectly, I made a partition emunand + nand backup
- Do not work to start the switch (black screen after nsw bootlogo)

- did the same with emunand on files
- This seems a bit slower when booting (the bootlogo stays longer like 1 sec more)
- It works... Wait WHAT ?????

How on earth can I be the only one having this issue and not being able to boot with emunand on partition ???

Actually you’re not the only one this has happened to. There’s one other person w/ the exact same issue where they had to use files based emunand. Nothing we did would resolve it until we used files based on a whim.

What size SDCard are you using? 512G or higher perhaps?
 
Hello,
I hope I'm in the right place to ask this questions, and I do that after using the search bar and google too ^^

I was playing on my Switch patched/unbanned running SYSCFW (Atmosphere F550 SYS) fine until yesterday when I was ingame,
The screen showed this error from HEKATE : see attached file.
I was using :
the last Hekate release(hekate_ctcaer_6.0.1_Nyx_1.5.1.zip),
last bootloader (atmosphere-1.4.1-master-7a69f2f06+hbl-2.4.3+hbmenu-3.5.1.zip)
I tried to restore my backup, then restart a clean install.

It's still not working, is there a way to check the files or compatibility because my console may did an update ?
Then the issue is from Hekate or Atmosphere not working after an update ?
Can you help me please proceed to UPDATE the CFW (if that may solve ?) ?
Or should I dump my firmware ?

Sorry for all these questions, feel free to redirect me to your previous answer if you don't want to waste time
on another silly question from me :D

Thank you very much, have a nice day ! <3

Saion
 

Attachments

  • IMG_20230221_024825__01.jpg
    IMG_20230221_024825__01.jpg
    821.1 KB · Views: 57
Last edited by SaionWi,
Hello,
I hope I'm in the right place to ask this questions, and I do that after using the search bar and google too ^^

I was playing on my Switch patched/unbanned running SYSCFW (Atmosphere F550 SYS) fine until yesterday when I was ingame,
The screen showed this error from HEKATE : see attached file.
I was using :
the last Hekate release(hekate_ctcaer_6.0.1_Nyx_1.5.1.zip),
last bootloader (atmosphere-1.4.1-master-7a69f2f06+hbl-2.4.3+hbmenu-3.5.1.zip)
I tried to restore my backup, then restart a clean install.

It's still not working, is there a way to check the files or compatibility because my console may did an update ?
Then the issue is from Atmosphere not working after an update ?
Can you help me please proceed to UPDATE the CFW (if that may solve ?) ?
Or should I dump my firmware ?

Thank you very much, have a nice day ! <3

Saion
This is the perfect place. If you’ve updated your Firmware to the latest, there was a new FW just released that will require so,e work before a corresponding CFW is released. I’m hearing this one had some big changes so it might take longer than we would normally hope for. Watch this thread and any new ones that might come out on the topic.

https://gbatemp.net/threads/nintend...eleased-atmosphere-update-coming-soon.626526/

until then, we wait…
 
  • Love
Reactions: SaionWi
Don’t see anything that would stop you from booting. Please go into Hekate and tap the emuMMC tile and take a screen shot to post here. Looking to make sure you have emunand in place.
My SD card is 512G and partition based NAND at 29G if I recall correctly.

emuMMC screenshot.jpg
 

Site & Scene News

Popular threads in this forum