Hacking SWITCH NOOB PARADISE - Ask questions here

  • Thread starter Thread starter APartOfMe
  • Start date Start date
  • Views Views 6,111,816
  • Replies Replies 47,954
  • Likes Likes 66
I updated the mainframe version with Daybreak.
I updated the switch ver to 18.0.0, but I selected “Install (FAT32+exFAT)” by mistake on Daybreak, and the data on the micro SD was backed up and changed to FAT32.
I started up the computer, but the error code 010041544D530000 came up.
I backed up the data in the micro SD and changed it to FAT32, but now I'm in this situation (T_T).
Thank you for moving the post.
Are you using a Mac?
 
I'm using Windows 11.
Well this still might be worth trying out. People have who reported that error code have also reported that using Hekate's archive bit fix resolved their issue which occurs when people use MacOS but I've seen it happen sometimes with Windows. Try running the archive bit fix via Hekate under Tools.
 
Hello everyone. Today I updated atmosphere to 1.7.1 and ofw to 18.1. After doing this second step, rebooting I got the following error: "Panic Occurred while running Atmosphere". I read online and here on the forum about possible solutions. The only one that allowed me to reboot the switch was to delete the error folder in atmosphere/contents but now no game works anymore! I got tired and would like to delete everything. What do I need to do for a full reset? I mean clean restore of atmosphere.
Thanks in advance!
 
Hello everyone,
I'm currently playing Prince of Persia : The Lost Crown in permadeath mode.
Unfortunately my character's life bar has reached zero, and the game mode starts from the very beginning.
I was more than 99% of the way through the game and didn't really want to start again.
Luckily I have a backup of my SD Card.
By the way, do you know where the game saves are stored?
I was about to use the latest version of JKSV, but, too late.
Thank you all for your help.
 
I might need some help. I have a Switch I bought in 2017 that is set to auto RCM. I followed a guide once Nintendo started to charge for online which I refuse to pay for. I've gotten by so far, I boot CFW EMUNAND whenever needed too (otherwise it stays docked in sleep mode).

It's currently running 16.1.0 AMS 1.6.2 S. I think the last time I updated my Switch was June 2023, but I could be wrong (which is not done through Nintendo's official server)

I was hoping to update to the most current firmware which I believe in 18.0.1 but I've heard ever since 17.0.0 was added there were complications with Homebrew and I always see topics say to not update even to 18.0.0. I typically use my Switch for the few games I have purchased (due to gamecard slot not being enabled I install them on my Switch) playing full games as "demos" that don't exist anymore to see if I actually enjoy them, and my daughter plays Animal Crossing. I'm hesitant to buy any new games because I know I won't be able to install them without an update.

What guide is the best to show how to update to OFW 17.0.0+ from 16.1.0? I'm weary of YouTube videos and now that SDsetup is done for I'm not sure what resources I'd need. Any help would be appreciated.
 
I might need some help. I have a Switch I bought in 2017 that is set to auto RCM. I followed a guide once Nintendo started to charge for online which I refuse to pay for. I've gotten by so far, I boot CFW EMUNAND whenever needed too (otherwise it stays docked in sleep mode).

It's currently running 16.1.0 AMS 1.6.2 S. I think the last time I updated my Switch was June 2023, but I could be wrong (which is not done through Nintendo's official server)

I was hoping to update to the most current firmware which I believe in 18.0.1 but I've heard ever since 17.0.0 was added there were complications with Homebrew and I always see topics say to not update even to 18.0.0. I typically use my Switch for the few games I have purchased (due to gamecard slot not being enabled I install them on my Switch) playing full games as "demos" that don't exist anymore to see if I actually enjoy them, and my daughter plays Animal Crossing. I'm hesitant to buy any new games because I know I won't be able to install them without an update.

What guide is the best to show how to update to OFW 17.0.0+ from 16.1.0? I'm weary of YouTube videos and now that SDsetup is done for I'm not sure what resources I'd need. Any help would be appreciated.
I've been on the latest (18.1.0) for a little while and it works perfectly. Use sys-patches instead of sigpatches and you should be golden. The rentry guide suggests to use an AIO to update, so I can't really recommend it. Actually, rentry guide is ok, just use the PC method, not the Switch method. It's normally just a matter of updating Hekate and Atmosphere (and sys-patches) before installing the new firmware with daybreak, a homebrew included with Atmosphere.
 
Last edited by Dust2dust,
  • Like
Reactions: Blythe93
Hello everyone. Today I updated atmosphere to 1.7.1 and ofw to 18.1. After doing this second step, rebooting I got the following error: "Panic Occurred while running Atmosphere". I read online and here on the forum about possible solutions. The only one that allowed me to reboot the switch was to delete the error folder in atmosphere/contents but now no game works anymore! I got tired and would like to delete everything. What do I need to do for a full reset? I mean clean restore of atmosphere.
Thanks in advance!
I don't think you need to delete anything. In fact, I think you are missing something. See in order to run pirated games, you need patches. Now these patches are firmware specific so if you ever update your firmware, or even Atmosphere, you need to update them too. You can download the latest patches from this thread.
Hello everyone,
I'm currently playing Prince of Persia : The Lost Crown in permadeath mode.
Unfortunately my character's life bar has reached zero, and the game mode starts from the very beginning.
I was more than 99% of the way through the game and didn't really want to start again.
Luckily I have a backup of my SD Card.
By the way, do you know where the game saves are stored?
I was about to use the latest version of JKSV, but, too late.
Thank you all for your help.
Saves are not stored on the SD card. They are stored within the internal memory. However if you didn't make a backup of the save before you died with JKSV, then the save data is lost.
 
Last edited by Draxzelex,
Should I turn off “deep sea”?
What is the name of the deep sea-related file in the micro SD?
 
I don't think you need to delete anything. In fact, I think you are missing something. See in order to run pirated games, you need patches. Now these patches are firmware specific so if you ever update your firmware, or even Atmosphere, you need to update them too. You can download the latest patches from this thread.

Saves are not stored on the SD card. They are stored within the internal memory. However if you did make a backup of the save before you died with JKSV, then the save data is lost.
Hi Draxzelex, and thank you for your response!
Unfortunately, I updated sigpatches from the thread you mentioned, but it don't work!
But, you are right: in some way, the problem is there. In fact, when I try to install, or reinstall, a game, with dbi, I receive SIGNATURE: INVALID even for *.nca and *.cnmt.nca.

What I do wrong? I updated firmware as I did dozen of time!
 
Hi Draxzelex, and thank you for your response!
Unfortunately, I updated sigpatches from the thread you mentioned, but it don't work!
But, you are right: in some way, the problem is there. In fact, when I try to install, or reinstall, a game, with dbi, I receive SIGNATURE: INVALID even for *.nca and *.cnmt.nca.

What I do wrong? I updated firmware as I did dozen of time!
In my humble opinion, sigpatches are passé. You should try to install sys-patch instead. It's a sys-module that effectively replaces sigpatches, and it works very well. It can also be used with tesla. It's been downloaded 11,000 times so far. 11,000 users can't be wrong! :D
 
I updated the version of the main unit in Daybreak, installed (FAT32+exFAT) and tried to move a 15GB file, but it says the file is too big to move.
Post automatically merged:

Deep sea is a cfw pack.
Thank you cfw, I'm new to this, so that helps.
 
Last edited by yonofu,
In my humble opinion, sigpatches are passé. You should try to install sys-patch instead. It's a sys-module that effectively replaces sigpatches, and it works very well. It can also be used with tesla. It's been downloaded 11,000 times so far. 11,000 users can't be wrong! :D
Hi Dust2dust, I thank you too.
I did what you seggest and now games are returned to work!
I still receive signature error when I install from dbi, but they work, as said.
 
I don't think you need to delete anything. In fact, I think you are missing something. See in order to run pirated games, you need patches. Now these patches are firmware specific so if you ever update your firmware, or even Atmosphere, you need to update them too. You can download the latest patches from this thread.

Saves are not stored on the SD card. They are stored within the internal memory. However if you did make a backup of the save before you died with JKSV, then the save data is lost.
I did as you did and it worked.
 
I updated the version of the main unit in Daybreak, installed (FAT32+exFAT) and tried to move a 15GB file, but it says the file is too big to move.
Post automatically merged:


Thank you cfw, I'm new to this, so that helps.

FAT32 limit is 4GB, but you can actually do everything on FAT32.
 
Hi Dust2dust, I thank you too.
I did what you seggest and now games are returned to work!
I still receive signature error when I install from dbi, but they work, as said.
Out of curiosity, are you using the latest version of DBI? Some bugs were fixed recently, and maybe the errors you encounter are related? Note that the latest version is in russian. You should get familiar with how the app works in the older english versions before you attempt to navigate through the menus of the russian version. But it's manageable. If that doesn't solve the signature errors, then your nsp/xci files have probably been tempered with before you acquired them.
 
Out of curiosity, are you using the latest version of DBI? Some bugs were fixed recently, and maybe the errors you encounter are related? Note that the latest version is in russian. You should get familiar with how the app works in the older english versions before you attempt to navigate through the menus of the russian version. But it's manageable. If that doesn't solve the signature errors, then your nsp/xci files have probably been tempered with before you acquired them.
No, I didn't update dbi. I will try! Thank you!
 

Site & Scene News

Popular threads in this forum