Hacking SWITCH NOOB PARADISE - Ask questions here

[Jakkal666]

https://nh-server.github.io/switch-guide/extras/updating/

Found this, scroll down towards the end. There's a table there. My situation would be On or above 9.0.0, but below 11.0.0
since I'm on 10.2.0, I gather there's atleast two updates to the cartridge slot should I upgrade to 13 (make that three if 13 contained an update to the slot).
But since I'm updating my emuNAND, which in theory is an emulated copy of the Switch software/os, does it still make changes to the actual hardware which both emu-/sysNAND share? I was thinking maybe Atmosphere had some kind of built-in countermeasures to keep the emuNAND separated on multiple levels, blocking hardware wide changes.

If the cartridge slot isn't updated on sysNAND if I update the emuNAND then there shouldn't be a problem right? I can always wipe the emuNAND and create a new one if I would like to downgrade? I've a backup of the NAND (10.2.0) and all my keys.

Not familiar with nogc.. I'll look into that.

Will also check out the converter you mentioned, thanks alot!

 

[Jakkal666]

. I don't believe there were any updates for the cartridge slot after firmware 10.2 so you should be fine. If not, you can always disable nogc but remember that you will not be able to downgrade your cartridge slot anymore nor use it on lower firmware versions

Sorry, messed up the quote function, browser on my phone is behaving odd..
Meant to put that quote at the start of my reply above.

 

[whiteglovian]

Is there a flash emulator for Switch? Is it possible to make?

 

[otaconn23]

You need patches to install and launch backups.

Thank you so much. I noticed that this won't work for all backups, specifically ones that say that my FW is too low, when trying to install with TinWoo. Is there any reason I should keep OFW and CFW at 9.0.1? Or would it be best to just update to 13.0 to make backup installs easier? I play backups on CFW - emuMMC while WiFi is off. I play my gamecards (like ACNH) online on OFW - stock. Ideas?

 

[Sekii]

Well hacking is already an action that risks a ban but unless you plan on going online with emuMMC, the risk seems moot. As for my title manager of choice, it has to be TinWoo Installer.

I don't plan to play online with emuMMC, in fact, I probably won't play any retail games on that Switch anymore, but I'd like to be able to use homebrew, that connects to the Internet. I read everywhere, that installing and running custom NSPs will get you banned. Does 90DNS not help in this case?
Thank you for the TinWoo suggestion, I'll check it out.

 

[Valkri599]

Is edizon/breeze supported in the newest builds? Or is there an update that is needed? Can't seem to get it to recognize any of my cheat lists after updating atmosphere to the latest build.

 

[SkyDX]

Question, I'm getting a new OLED Switch today and I want to transfer my old Switch's SysMMC via the build in tool, but beforehand I want to extract my saves and move them to the EmuMMC on my old Switch, how easy is that?

My nephew has some save games on my old Switch and I want him to be able to continue playing on my old Switch while I have my OLED Switch.

 

[Jakkal666]

2. Yes, you just have to convert the payload you use to launch Atmosphere to boot.dat. You can use this website to do that

Awesome, just tested it, works like a charm.

And to clarify, for future reference and those wondering. I went from SX OS PRO to Atmosphere. Didn't want to inject my fusee.bin payload using TegraRcmGUI when cold booting my Switch since I've got a SX PRO dongle.

Used the following website:
https://sx-boot-dat-creator.herokuapp.com/

Uploaded the fusee.bin which converted the payload into boot.dat (compatible with SX PRO dongle). Those familiar with SX OS knows that boot.dat should go into the root of the SD card. I can now cold boot my Switch into Atmosphere using SX OS PRO-peripherals (SX jig and SX dongle) - it's the same procedure as booting SX OS.

 

[mendezagus]

Hello everyone. Weird problem here: I just updated to the latest atmosphere (ofw 13.0) but the switch crashes every time i try to enter homebrewmenu with the R+A buttons on the album. I get a blue screen with the error codes and i´m asked to restart with the power button. Im using hekate and booting with fusee to start the switch. Why can this be? Is there something wrong with the nx-hbmenu.nro?

 

[Walo]

Hi, I've been trying to update Atmosphere so I can update my FW from 11.0.1 and get ready for Metroid, but I've been running into some issues and I need help.

I downloaded the lastest version of the All-inOne Switch Updater (2.15.0) and figured following the instructions would be easy enough.

Tried updating Atmosphere through the app and I'm going from version 0.16.2|S to the lastest 1.1.1 version. I downloaded, it asked if i wanted to replace the .ini files and then asked me if I wanted to download hekate to which I both agreed.

It then rebooted me to the payload but when I launched it, it then gave me a small warning about something not being found (might've been sigpatches?) and to press volume to continue or power to restart normally. I continued and figure it's the sigpatches since I couldn't open the hbmenu through the override system and gave me the usual "corrupted game data". Hbmenu did launch through the photos folder and I booted up the All-in-One Updater to see what's up.

For some reason Atmosphere is still 0.16.2|S. I tried installing the sigpatches from the app and retrying the update process but it doesn't seem to actually update.

I figured I'd try replacing the atmosphere files from the pc but even when replacing them it still says I'm in the old Atmosphere version. And If I try relaunching updater I get an error screen with Error Code: 2349-0008 (0x115d). I can power off the console after that and turn it on by injecting the usual fusee-primary.bin payload. But I'm a bit stuck right now....

Please help this idiot.

 

[Waster]

It's been a while since I installed anything on my Switch, so I don't really remember everything. If I want to make all the updates required to play newer games, what would I need to update? I am using FW 9.0.1 and Atmosphere 0.9.4.

 

[Skeet1983]

Hi guys. I have a pre-order for the new Xbox at my local game store. Thing is, am thinking about getting the new oled switch that came out today. The store I pre-ordered Xbox at is not sure when they will get more of them in. Should I cancel my Xbox pre-order and get the new oled switch? I currently have 2 switches, one hacked and other legit. Thoughts and help appreciated [emoji846]

Sent from my SM-N981U using Tapatalk

 

[ganons]

Never bothered reading up emunand as SX was up until now. So can switch remain physically on 11.0 and then have 13.0 on the micro SD? If so what's the process?

 

[Jakkal666]

Hi, I've been trying to update Atmosphere so I can update my FW from 11.0.1 and get ready for Metroid

Supposedly, you can actually run the new Metroid on firmware 11. Just saying.

Edit: I can personally confirm that Metroid Dread runs on firmware 11.0.0.

Not really sure what happened to your setup when you started updating, not a fan of the all-in-one-bulk-solutions, too many variables..

 

[Walo]

Supposedly, you can actually run the new Metroid on firmware 11. Just saying.

Not really sure what happened to your setup when you started updating, not a fan of the all-in-one-bulk-solutions, too many variables..

Thanks for the heads up.

I did a little digging and decided to do a clean install from the pc. I was running into some issues since the SD card had some corrupted bits but after repairing it with the default Windows 10 repairing tool I was able to copy the Hekate and Nyx loaders.

So it managed to boot fine and lo and behold my Atmosphere updated fine and the payload is booting perfectly. I think going from such an old version of Atmosphere when they did major changes to the 1.0.0 release was causing issues with the auto updater.

I'm still gonna download the new 13.0 update since I couldn't play Axiom Verge 2 either and I'm sure later down the line I'll be needing the update. And since Atmosphere is compatible, it shouldn't be a problem

So TLDR; Just repair the SD card and do a clean install manually from PC

 

[Draxzelex]

https://nh-server.github.io/switch-guide/extras/updating/

Found this, scroll down towards the end. There's a table there. My situation would be On or above 9.0.0, but below 11.0.0
since I'm on 10.2.0, I gather there's atleast two updates to the cartridge slot should I upgrade to 13 (make that three if 13 contained an update to the slot).
But since I'm updating my emuNAND, which in theory is an emulated copy of the Switch software/os, does it still make changes to the actual hardware which both emu-/sysNAND share? I was thinking maybe Atmosphere had some kind of built-in countermeasures to keep the emuNAND separated on multiple levels, blocking hardware wide changes.

If the cartridge slot isn't updated on sysNAND if I update the emuNAND then there shouldn't be a problem right? I can always wipe the emuNAND and create a new one if I would like to downgrade? I've a backup of the NAND (10.2.0) and all my keys.

Not familiar with nogc.. I'll look into that.

Will also check out the converter you mentioned, thanks alot!

The answer to your first question is yes; even tho emuMMC and sysMMC are separate software, they share the same hardware and any changes any of those make to the hardware is shared between both. So if you update the emuMMC above firmware 11.0, it will update the cartridge slot for both sysMMC and emuMMC.

Thank you so much. I noticed that this won't work for all backups, specifically ones that say that my FW is too low, when trying to install with TinWoo. Is there any reason I should keep OFW and CFW at 9.0.1? Or would it be best to just update to 13.0 to make backup installs easier? I play backups on CFW - emuMMC while WiFi is off. I play my gamecards (like ACNH) online on OFW - stock. Ideas?

Since we can update the firmware without burning fuses, which is the biggest roadblock to downgrading, there isn't much reason to not update the firmware. And since there is no way around to making games work on lower firmware versions, updating the firmware is inevitable. You update the firmware to 13.0 but no games require that high of a firmware so anything in 12.X is just as good.

I don't plan to play online with emuMMC, in fact, I probably won't play any retail games on that Switch anymore, but I'd like to be able to use homebrew, that connects to the Internet. I read everywhere, that installing and running custom NSPs will get you banned. Does 90DNS not help in this case?
Thank you for the TinWoo suggestion, I'll check it out.

Being banned doesn't affect the ability to use homebrew applications that require Internet; bans only affect games and services that use Nintendo's servers like online play or NSO. That being said, 90DNS can help prevent an avoidable ban while still allowing non-Nintendo tools to use the Internet like homebrew apps.

Question, I'm getting a new OLED Switch today and I want to transfer my old Switch's SysMMC via the build in tool, but beforehand I want to extract my saves and move them to the EmuMMC on my old Switch, how easy is that?

My nephew has some save games on my old Switch and I want him to be able to continue playing on my old Switch while I have my OLED Switch.

Yep, its just as easy as using a save manager to dump and restore the save files. JKSV is currently the recommended homebrew save application.

Hello everyone. Weird problem here: I just updated to the latest atmosphere (ofw 13.0) but the switch crashes every time i try to enter homebrewmenu with the R+A buttons on the album. I get a blue screen with the error codes and i´m asked to restart with the power button. Im using hekate and booting with fusee to start the switch. Why can this be? Is there something wrong with the nx-hbmenu.nro?

Rename the nx-hbmenu.nro to just hbmenu.no meaning just remove the nx- in the name of the file.

It's been a while since I installed anything on my Switch, so I don't really remember everything. If I want to make all the updates required to play newer games, what would I need to update? I am using FW 9.0.1 and Atmosphere 0.9.4.

You need to update your firmware and CFW versions. Updating CFW is as simple as deleting the old CFW files/folders and placing the new ones on the SD card. As for updating your firmware, you can use the homebrew application Daybreak to do that which comes bundled with Atmosphere.

Never bothered reading up emunand as SX was up until now. So can switch remain physically on 11.0 and then have 13.0 on the micro SD? If so what's the process?

You boot up Hekate like you would any other payload then have it create an emuMMC on your SD card either as a partition or a file. Partition is the recommended choice. Then once emuMMC is setup, it will operate independently of sysMMC which is actual console's firmware. You boot up into either sysMMC or emuMMC at your disposal and update either one accordingly.

Hi guys. I have a pre-order for the new Xbox at my local game store. Thing is, am thinking about getting the new oled switch that came out today. The store I pre-ordered Xbox at is not sure when they will get more of them in. Should I cancel my Xbox pre-order and get the new oled switch? I currently have 2 switches, one hacked and other legit. Thoughts and help appreciated [emoji846]

Sent from my SM-N981U using Tapatalk

The new OLED Switch doesn't provide anything groundbreaking that normal Switches can already do. If you already have 2 Switches, you don't really need a third even if its the OLED model. But that is just my two cents.

 

[mendezagus]

Rename the nx-hbmenu.nro to just hbmenu.no meaning just remove the nx- in the name of the file.

It worked! I love you so much Drax!

 

[otaconn23]

Since we can update the firmware without burning fuses, which is the biggest roadblock to downgrading, there isn't much reason to not update the firmware. And since there is no way around to making games work on lower firmware versions, updating the firmware is inevitable. You update the firmware to 13.0 but no games require that high of a firmware so anything in 12.X is just as good.

Excellent thank you! Can I update with AIO Switch Updater? Before connecting to WiFi on CFW - emuMMC and updating FW, should I do anything to reduce the ban risk? Lastly, I started playing ACNH on Yuzu before getting the console. I then bought the console and game. I wish to transfer my Yuzu save to the console and play online on OFW - stock. Possible?

 

[Draxzelex]

Excellent thank you! Can I update with AIO Switch Updater? Before connecting to WiFi on CFW - emuMMC and updating FW, should I do anything to reduce the ban risk? Lastly, I started playing ACNH on Yuzu before getting the console. I then bought the console and game. I wish to transfer my Yuzu save to the console and play online on OFW - stock. Possible?

While you can use the AIO Switch Updater, I personally would have to recommend against using that app. The reason is because a lot of users end up running into issues when using it which is no surprise considering its an automated update process. Updating by manually changing the files will always be better because you have control over which files you are transferring. I'd also advise against updating the emuMMC via Wi-Fi. Instead, you should use the homebrew application Daybreak which comes bundled with Atmosphere so you can update offline. In order to update with Daybreak, you will need to download the Nintendo Switch firmware files separately and put them on your SD card to install with Daybreak. These cannot be linked nor shared here as they are copyrighted material but rest assured that they are available illegally on the Internet. Lastly, while you might be able to transfer the save from Yuzu to OFW, doing so is a ban risk since you need to use homebrew to implant the save file.

 

[PikachuPro]

I updated to 13.0 on emmu, now I get errors whenever I try to boot CFW emmu from Hekate:
Failed to identify kernel!
Failed to launch HOS!

Everything was perfectly fine before. I was on 10.something on emmu, I updated files on my SD card, updated to 13.0 using Daybreak, and now I get these errors.

But, at the end of the update I picked the restart option, but it hung for a long time at the black screen so I held down power for a forced power down to restart. that's the only odd thing that happened before these errors.