Hacking SWITCH NOOB PARADISE - Ask questions here

[bupeapoop]

.ini file has no changes so that’s not it.

• Someone else fixed this by using the "Fix Archive Bit" on hekate (tools -> Arch bit * RCM -> Fix Archive Bit

After trying this, all seemed to be well. Sadly though, whenever I attempt to boot into Atmosphere, I get the following error message:

A fatal error occurred when running Atmosphere.
Program ID: 010041544D530000
Error Desc: std::abort() called (0xffe)

Failed to save report to the SD card! (001b5802)

Press POWER to reboot.

• Try is to delete /atmosphere/010041544d530000 if it exists

Unfortunately this folder is not available. Even when enabling Hidden Files/Folders, this particular file/folder is unavailable for deletion.

-----------

My SD Card doesn't seem to be corruped though. Whenever I insert my SD Card to my Windows Laptop, everything can be accessed. Is there anything I can do before having to start from scratch?

If I have to start from scratch, where do I need to kick off from? Is it worth backing up any modules or anything to make my life that little bit easier when doing everything from square one again?

 

[donnyp]

you can set autoboot to the stanza you want to autoboot. 0 is off and 1-4 are for the 4 stanzas you have below. I would set it to 2 or 4.

bootwait can be reduced to 1 so you get a faster boot time. 1 second is plenty of time to press (vol -) to stop the boot and manually chose (kinda like F2 on your PC BIOS)

1) This one boots Atmosphere on your stock Sysnand

2) This one boots Atmosphere on your emulated nand. I would make this or 4 your autoboot=.

3) This one boots bone stock with no CFW on your stock Sysnand

4) This one boots CFW on emunand (implied). It‘s using fusee direct rather than fss0 mode. Otherwise identical to stanza 2. Make this or 2 your autoboot=.

perfect….good for a very long time.

4 options are fine…set autoboot=2 and you’ll skip right by this and boot up unless you press (vol -)

Nope, you’re good to go.

Perfect, thanks Bink!! I will make those changes and go from there. Instead of just calling it CFW for each line, should I change it to Atmosphere? Like Atmosphere sysmmc, Atmosphere emuMMC??

 

[donnyp]

There's actually no reason to use fusee unless you're a purist. Hekate not only works as well but is better than fusee. As long as you downloaded your patches from here, you will have patches for both Hekate & fusee. If you want less options, you will have to remove them from your hekate_ipl.ini file which you just listed.

Thanks Drax, I will look through that thread. Maybe I will just autoboot the second option from my .ini file and not worry about the other options until I need them.

 

[binkinator]

After trying this, all seemed to be well. Sadly though, whenever I attempt to boot into Atmosphere, I get the following error message:

A fatal error occurred when running Atmosphere.
Program ID: 010041544D530000
Error Desc: std::abort() called (0xffe)

Failed to save report to the SD card! (001b5802)

This is a fairly generic error. We really need the logs that are typically dropped in /atmosphere/fatal_errors/ to see what's really going on but that "Failed to save report to the SD card! (001b5802)" is screwing us over.

Press POWER to reboot.



Unfortunately this folder is not available. Even when enabling Hidden Files/Folders, this particular file/folder is unavailable for deletion.

-----------

My SD Card doesn't seem to be corruped though. Whenever I insert my SD Card to my Windows Laptop, everything can be accessed. Is there anything I can do before having to start from scratch?

If I have to start from scratch, where do I need to kick off from? Is it worth backing up any modules or anything to make my life that little bit easier when doing everything from square one again?

As a quick test simply rename /atmosphere/contents to /atmosphere/contents.bak and see if it will boot without any system modules. The last things you added might not work with 14.0.0 so let's remove that as a source of problems.

 

[donnyp]

you can set autoboot to the stanza you want to autoboot. 0 is off and 1-4 are for the 4 stanzas you have below. I would set it to 2 or 4.

bootwait can be reduced to 1 so you get a faster boot time. 1 second is plenty of time to press (vol -) to stop the boot and manually chose (kinda like F2 on your PC BIOS)

1) This one boots Atmosphere on your stock Sysnand

2) This one boots Atmosphere on your emulated nand. I would make this or 4 your autoboot=.

3) This one boots bone stock with no CFW on your stock Sysnand

4) This one boots CFW on emunand (implied). It‘s using fusee direct rather than fss0 mode. Otherwise identical to stanza 2. Make this or 2 your autoboot=.

perfect….good for a very long time.

4 options are fine…set autoboot=2 and you’ll skip right by this and boot up unless you press (vol -)

Nope, you’re good to go.

This is where I got the information from when installing my sigpatches. This is also why I was asking about the payload with fusee.bin

Will the way I have it setup work fine without following below?

Supports HOS firmware 13.2.1 and AMS 1.2.6​

I pulled my sigpatches.zip file from above to match my firmware and AMS version. I know their is recently updated ones that are for firmware 14.0.0 an AMS 1.3.0 but I figured since I'm not running those version's, I wouldn't use those

Hekate Patches (EZ Mode)​

If you wish to start your CFW with Hekate, we highly suggest chainloading fusee. This is the best method to boot Atmosphere without directly pushing fusee.bin.


To chainload atmosphere place the latest fusee.bin in /bootloader/payloads/ then edit your hekate_ipl.ini to contain the following,


[Atmosphere CFW] payload=bootloader/payloads/fusee.bin

Hekate Patches (fss0 Hard Mode)​

I do not boot this way, and I suggest you don't either. Make sure that you edit your hekate_ipl.ini to contain kip1patch=nosigchk. Like this:

[CFW - FSS0 SYS] fss0=atmosphere/package3 kip1patch=nosigchk emummc_force_disable=1 [CFW - FSS0 EMU] fss0=atmosphere/package3 kip1patch=nosigchk emummcforce=1

 

[binkinator]

Perfect, thanks Bink!! I will make those changes and go from there. Instead of just calling it CFW for each line, should I change it to Atmosphere? Like Atmosphere sysmmc, Atmosphere emuMMC??

Your names are:
[CFW (sysMMC)]
[CFW (emuMMC)]
[Stock]
[Fusee]

Those are pretty descriptive already but feel free to change them to what makes sense to you...

[Atmosphere (sysMMC)]
[Atmosphere (emuMMC)]
[Stock]
[Atmosphere (emuMMC Fusee)]

??

I mean...really...it's up to you...

 

[binkinator]

This is where I got the information from when installing my sigpatches. This is also why I was asking about the payload with fusee.bin

Will the way I have it setup work fine without following below?

Supports HOS firmware 13.2.1 and AMS 1.2.6​

I pulled my sigpatches.zip file from above to match my firmware and AMS version. I know their is recently updated ones that are for firmware 14.0.0 an AMS 1.3.0 but I figured since I'm not running those version's, I wouldn't use those

Hekate Patches (EZ Mode)​

If you wish to start your CFW with Hekate, we highly suggest chainloading fusee. This is the best method to boot Atmosphere without directly pushing fusee.bin.


To chainload atmosphere place the latest fusee.bin in /bootloader/payloads/ then edit your hekate_ipl.ini to contain the following,


[Atmosphere CFW] payload=bootloader/payloads/fusee.bin

Hekate Patches (fss0 Hard Mode)​

I do not boot this way, and I suggest you don't either. Make sure that you edit your hekate_ipl.ini to contain kip1patch=nosigchk. Like this:

[CFW - FSS0 SYS] fss0=atmosphere/package3 kip1patch=nosigchk emummc_force_disable=1 [CFW - FSS0 EMU] fss0=atmosphere/package3 kip1patch=nosigchk emummcforce=1

fusee.bin vs fss0 is largely religion at this point. Use what you have working today.

 

[bupeapoop]

This is a fairly generic error. We really need the logs that are typically dropped in /atmosphere/fatal_errors/ to see what's really going on but that "Failed to save report to the SD card! (001b5802)" is screwing us over.

Unfortunately, when accessing the SD via my Windows Laptop, there is no files contained within the /atmosphere/fatal_errors/ folder. That being said, there is 2 file logs within /atmosphere/fatal_reports. The contents of each file are as follows:

01646987937_01000000000000c.log

01646690419_01000000000000c.log

As a quick test simply rename /atmosphere/contents to /atmosphere/contents.bak and see if it will boot without any system modules. The last things you added might not work with 14.0.0 so let's remove that as a source of problems.

Following your instructions now @binkinator. Please the screenshot HERE. Went ahead and renamed contents to contents.bak. Going to boot up after responding to this post. Let me get back to you with an answer just shortly.

Thanks for all the help as always. You're the man @binkinator!

 

[bupeapoop]

UPDATE:

Even after renaming /atmosphere/contents to /atmosphere/contents.bak, I'm still getting the following error message:

A fatal error occurred when running Atmosphere.
Program ID: 010041544D530000
Error Desc: std::abort() called (0xffe)

Failed to save report to the SD card! (001b5802)

The SD Card is still accessible via my Windows Machine. The SD Card has been formatted to FAT32.

I've no idea why I'm unable to resolve this issue? Something tells me it has something to do with the Offline Fix whilst attempting to install Doom. Before this, all seemed to be working well. Below is the .NFO Instructions for the DOOM Offline Fix:

.
________. ________ :__________ karl* _____\___.
_\ |________/ /_________ | _/________\________ / \\ |
_\\ | / _/_\ _ \| / _ \ \ // \\ |
|\\ | _// ___/_\\ \ \ // | _\ \ \/ / _\\|
| \\ : / | \ \ _// : \\ \ /| \\_
|__\\__________/_______________\____|\_____/_______________\_____|\/ |_______\
<:-\-------------------------------------/--------------------------:------:-
. . |
| P r o u d l y P r e s e n t s |
| - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - |
| |
| Title : DOOM (1993) - Offline FIX *READNFO* |
| |
| Publisher : Bethesda Softworks Platform : Nintendo Switch |
| Developer : id Software Origin : Save |
| Genre : Action / First-Person Title ID : 010018900DD00000 |
: Date : July 2019 Format : 01x50MB / SAVE |
.__ //|
| /---------------------------------------------------------------------/_:
|// .
| R e l e a s e N o t e s |
| - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - |
| |
| Celebrate DOOM's 25th anniversary with the re-release of the |
| original DOOM (1993). First released in 1993, DOOM introduced |
| millions of gamers to the fast-paced, white-knuckle, demon-slaying |
| action the franchise is known for. |
| |
| Experience the classic demon-blasting fun that popularized the |
| genre home or on-the-go. |
| |
| DOOM (1993) includes: |
| |
| * The expansion, Episode IV: Thy Flesh Consumed, with 9 additional |
| action-packed levels |
| |
| * Local 4 player deathmatch |
| |
| * Local 4 player co-op |
| |
| READNFO Notes : |
| |
| It seems Bethesda had the smart idea to make a 1993 game online only. |
| Luckily for you, here is a modified savegame that skips the Bestheda |
| mandatory authentification. |
| |
| Extract and import 'PlayerData' into your current savegame with your |
| favorite savegame tool (Checkpoint or Devmenu can do it). |
| |
| This game does need to have your NSW account linked to Nintendo |
| (like some other games). You can skip that by either editing |
| control.nacp yourself or use that homebrew to add a default |
| linked account to your NSW. |
| |
| Enjoy! |
: |
.__ //|
| /---------------------------------------------------------------------/_:
|// .
| G r e e t i n g s |
| - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - |
| |
| Abstrakt . Anthrox . Capital . Caravan . Complex |
| Dual Crew Shining . Duplex . Echelon . Eurasia . Kalisto . Legacy |
| Lightforce . Menace . Miracle . Mode 7 . Money . Mystic . Napalm |
| Nightfall . Oldskool . Paradox . Premiere . Project X . Protocol |
| Quartex . Quasar . Rising Sun . Scoopex . Sneakers . Triforce |
| |
-:-------------------------------------------------------------------------:>
| |
. VENOM - DOOMed! Since 2001. .

 

[binkinator]

UPDATE:

Even after renaming /atmosphere/contents to /atmosphere/contents.bak, I'm still getting the following error message:



The SD Card is still accessible via my Windows Machine. The SD Card has been formatted to FAT32.

I've no idea why I'm unable to resolve this issue? Something tells me it has something to do with the Offline Fix whilst attempting to install Doom. Before this, all seemed to be working well. Below is the .NFO Instructions for the DOOM Offline Fix:

Do you have another card? You can set this one aside and do a quick deploy from scratch on the new one. Copy everything from current card to new one bit by bit until you find the bug. Then, once all is well, copy everything back over to the main card.

 

[bupeapoop]

Do you have another card? You can set this one aside and do a quick deploy from scratch on the new one. Copy everything from current card to new one bit by bit until you find the bug. Then, once all is well, copy everything back over to the main card.

Sadly not. If I knew now what I knew back then, I'd have ordered 2 SD Cards, and done what you do @binkinator and backed up[ everything from one to the other every 2 weeks or so. That way, I wouldn't have ran into the issues that I'm in now.

Every so often, these SD Cards go on sale though, so I'll hang tight, and the minute their back available on a new deal, I'll snap up another one

In the mean time though, with me only having this 1 SD, do you have any suggestions to get back up and running? It'll be a real bummer to start from scratch, but if I have to run through everything again, I guess I'm left with no choice...

 

[binkinator]

Sadly not. If I knew now what I knew back then, I'd have ordered 2 SD Cards, and done what you do @binkinator and backed up[ everything from one to the other every 2 weeks or so. That way, I wouldn't have ran into the issues that I'm in now.

Every so often, these SD Cards go on sale though, so I'll hang tight, and the minute their back available on a new deal, I'll snap up another one

In the mean time though, with me only having this 1 SD, do you have any suggestions to get back up and running? It'll be a real bummer to start from scratch, but if I have to run through everything again, I guess I'm left with no choice...

Unfortunately everything points back to this:

https://github.com/Atmosphere-NX/Atmosphere/issues/717

You should be able to rip through a format and reinstall.especially if you copy some key folders so yiu don’t have to recreate yiu hekate_ipl.ini for example…

I keep a switch folder with the software I pull down. Serves as a source of files and also a checklist of what needs to be put back.

 

[Gigadragon]

is it possible to be banned specifically for using

"CaVE Database Manager - A SNES, NES, N64, Genesis Switch Online modding App"​

in cfwsysnand. I know that using cfw sysnand in and of itself is a risk but there are types of cfw that are considered low risk like cosmetic mods in ssbu or mario kart 8, is this one of those mods? should i only be using this in emunand? And would keeping the atmosphere\content files on my sd card compromise something even when i don't have the NSO-N64 emulator installed on my sysnand?

 

[binkinator]

is it possible to be banned specifically for using

"CaVE Database Manager - A SNES, NES, N64, Genesis Switch Online modding App"​

in cfwsysnand. I know that using cfw sysnand in and of itself is a risk but there are types of cfw that are considered low risk like cosmetic mods in ssbu or mario kart 8, is this one of those mods? should i only be using this in emunand? And would keeping the atmosphere\content files on my sd card compromise something even when i don't have the NSO-N64 emulator installed on my sysnand?

Sure is possible. Also remember, because of constant telemetry, it’s not just the game you are playing at the moment, it can also be reporting other activities you have done in the past. Any type of piracy can leave a signature that your Switch can easily upload to Ninty if you allow it at any time. Atmosphere is really the only modern CFW game in town. It does a pretty good job offering tools to keep you safe in emunand. You also don’t want to be using your central Sysnand for shenanigans in case something goes wrong…yiu want that something to happen to a “disposable“ emunand instead. Having files on you SD card typically won’t get you in trouble…it would be bad form for a company to go through your personal files. Accessing a customers personal files is kinda foul and who knows, it might could get them in legal trouble as well so it’s probably not worth it to them even from just a PR perspective.

bottom Line: stay on CFW on emunand and offline. If yiu need to use Internet and CFW, use exosphere and dns:mitm. To play games Online stick with pure Sysnand (no CFW). Deviations from this increase your risk of a ban.
…check out the dedicated Switch Ban Hub for more details.

 

[Rick Astley]

Hi everybody !
I'm back with another weird issue. Pretty much, I was able to grab my hand on another CFW Switch. I did the emummc setup etc earlier, no issue. I've put the sigpatches from the GBA Temp thread, no issue.

So I wanted to put my dumped Sword / Shield stuff to be able to have them digital (as always). The mistake i've done (i mean the only thing I can see) has been to install the DLC before installing the game.

I've dumped my game, installed everything, but every time I try to run the game, it does the check and say something installed is not valid (the DLC). I've no issue running the game, but no way to get the DLC to work. I've tried to clean the tickets, re-installing everything but no way.

Edit : For more infos, i'm running on 14.0.0

Any help ? Thanks o/

 

[MSco]

So, as I mentioned before, I would like to replace my V1 switch by a modded OLED switch.

What is the best way to transfer the custom firmware from V1 to OLED? Can I simply use the same SD card with the same files (so just use the old emunand for the OLED) or is this a bad idea?

I have made several backups from my cartridges on the V1 cfw. Will I have to make all those backups again or is there an easy way to transfer the installed titles from one console to another? And how about the savegames? WIll I have to export and import transfer every savegame seperately with JKSV?

 

[binkinator]

So, as I mentioned before, I would like to replace my V1 switch by a modded OLED switch.

What is the best way to transfer the custom firmware from V1 to OLED? Can I simply use the same SD card with the same files (so just use the old emunand for the OLED) or is this a bad idea?

Just re-download atmosphere, fusee.bin, Hekate and Sigpatches. Thise small zips are what makes it all work. Slightly different setup from V1 Erista to Chipped Aula so prolly just easier to start with a new sd card and leave the V1 alone.

I have made several backups from my cartridges on the V1 cfw. Will I have to make all those backups again or is there an easy way to transfer the installed titles from one console to another?

Just install the XCIs you extracted as backups on your new one using the installer of your choice.

And how about the savegames? WIll I have to export and import transfer every savegame seperately with JKSV?

You’ve nailed it. JKSV on both. Export on V1 and import on V3.

 

[MSco]

@binkinator Thanks for you help. However, I think you misunderstood my first question. Can you tell me, if I can just use the V1 emunand for the OLED cfw? Or will I have to setup a completely new emunand for the OLED?

 

[britain4]

Hey all, getting an error when booting Atmosphere 1.3.0 on my Switch through Hekate 5.7.2 -

Title ID 010041544D530000
Error std : abort (0xFFE)

Rolling back to Atmosphere 1.2.6 it all works normally again. Both sys and emuMMC are on 13.2.1

Have tried removing all files from my SD card apart from totally fresh copies of Hekate, Atmosphere and my emuMMC and it's still got the issue. Same thing happens on both sysMMC and emuMMC, fusee and FSS0.

I'm on FAT32 and this is the first time it's given me an issue with any updates. I know 1.3.0 is a pre-release just now so anyone else having the same problem with it?

Looking into it more, it looks like it's the presence of my emuMMC on the card that's causing the issues, whether it's enabled in Hekate or not. It also causes the above error when booting CFW on sysMMC.

It does still however work absolutely fine in AMS 1.2.6, which suggests an AMS issue or an issue with my emuMMC - I cleared the serial in Incognito on there when I first set the emuMMC up ages ago under SXOS, it's file based and also resized to about 8gb ish so plenty of potential to go wrong but nothing to explain why it still works fine under 1.2.6

 

[binkinator]

@binkinator Thanks for you help. However, I think you misunderstood my first question. Can you tell me, if I can just use the V1 emunand for the OLED cfw? Or will I have to setup a completely new emunand for the OLED?

Reusing an emunand from another machine will not be good. Recommend you copy directly from the OLED SysNand to create a new EmuNand.