Hacking Corrupted data when installing games

[jamsplodge]

Hi all,

Hope somebody can help me. Every game I install, regardless of whether I dumped it myself, acquired it, or downloaded from one of the shops will crash saying that the game is corrupted, sometimes hours into a game, sometimes before starting. Check for corrupted data shows that my installs are corrupted immediately before even launching the game.

I used to run SXOS when everything was fine until a couple of months back when I decided to switch to Atmosphere. I'm running the latest version of Atmosphere launched directly with fusee.bin, without Hekate, and with up to date sigpatches.

Initially I thought it was a dodgy SD card so tried another and saw the same, tried both exFat and FAT32, then I thought it might be the SD reader but found that games installed to the NAND were showing as corrupted too.

I'm just not sure what else to try now, my Switch is effectively a paperweight. Am I missing something obvious?

 

[Hayato213]

Tested your card empty with H2testw (windows), F3X (Mac)?

 

[jamsplodge]

Tested your card empty with H2testw (windows), F3X (Mac)?

Yep, it's not the card, just spent 4 hours testing it with H2testw this morning, all good

 

[Hayato213]

https://github.com/ITotalJustice/patches/releases

I used these with FAT32, make sure your folder structure is correct for the patches.

 

[jamsplodge]

https://github.com/ITotalJustice/patches/releases

I used these with FAT32, make sure your folder structure is correct for the patches.

Yep, those are the sigpatches I'm using, tried installing both manually and with AOI updater. I'm at a bit of a dead end.

 

[Reploid]

I don't think it's actually corruption, more like sigpathes shenanigans. I had my share of headache with those when switched to atmosphere.
We have whole FAQ about it. https://gbatemp.net/threads/guide-how-to-fix-switch-games-not-booting-after-a-fw-cfw-update.563960/

I more or less solved it by using deepsea package with fusee sigpathes and booting using latest fusee payload, instead of hekate own routine. YOu can get those using the AIO updater.

 

[Hayato213]

Yep, those are the sigpatches I'm using, tried installing both manually and with AOI updater. I'm at a bit of a dead end.

Perhaps replaces all your files on the SD card manually, keep the Nintendo folder only, see if that help not just replacing the signature patches. You can use hekate usb mounting feature so you don't take out the SD card.

 

[jamsplodge]

Perhaps replaces all your files on the SD card manually, keep the Nintendo folder only, see if that help not just replacing the signature patches. You can use hekate usb mounting feature so you don't take out the SD card.

I've started from scratch several times over the weekend. All of these attempts to install games are fresh installations after having done this. I'm not using Hekate, couldn't get games to launch at all with chain loading.

 

[Hayato213]

I've started from scratch several times over the weekend. All of these attempts to install games are fresh installations after having done this. I'm not using Hekate, couldn't get games to launch at all with chain loading.

Chainloading isn't the issue here. How are you injecting your payload?

 

[jamsplodge]

Chainloading isn't the issue here. How are you injecting your payload?

I am injecting fusee.bin directly using an rcm loader, chain loading isn't the issue right now because I'm not doing that

 

[Hayato213]

What happen when you install game from a reputable uploader like CAF African?

 

[jamsplodge]

What happen when you install game from a reputable uploader like CAF African?

That's the thing, it will install, it will seemingly work, I'll play it for several hours, then it will crash and tell me the data is corrupt. I'm doing this with fresh dumps of my own cartridges and seeing exactly the same thing.

 

[Hayato213]

That's the thing, it will install, it will seemingly work, I'll play it for several hours, then it will crash and tell me the data is corrupt. I'm doing this with fresh dumps of my own cartridges and seeing exactly the same thing.

Sound like problem either with the card or the SD card flex if you do take them out alot.

 

[jamsplodge]

Sound like problem either with the card or the SD card flex if you do take them out alot.

If I install to NAND I see the same thing. It's definitely NOT the card, but unless installing to NAND copies to SD first and then to NAND, it can't be the reader either.

 

[linuxares]

hmm... very strange. Have you tried playing with a game cartridge and see if the same issue happens?

 

[jamsplodge]

hmm... very strange. Have you tried playing with a game cartridge and see if the same issue happens?

I haven't yet experienced a cartridge game crashing. But I really do sometimes have to play for several hours before it happens, so not sure whether cartridge is affected or not.

 

[linuxares]

I haven't yet experienced a cartridge game crashing. But I really do sometimes have to play for several hours before it happens, so not sure whether cartridge is affected or not.

I mean the Switch do crash randomly sometimes. I wonder if it's a heating issue? Can you run with Status Monitor Overlay and see if it's slowly climbing or if it stay stable?

 

[jamsplodge]

I mean the Switch do crash randomly sometimes. I wonder if it's a heating issue? Can you run with Status Monitor Overlay and see if it's slowly climbing or if it stay stable?

I'll try that yeah, I can feel the fan going and it's not spitting out what I would say is hot air. I can also get to the point in a game where it crashes, turn off the Switch, come back several hours later and load my save and it will still crash at the exact same stage.

 

[linuxares]

I'll try that yeah, I can feel the fan going and it's not spitting out what I would say is hot air. I can also get to the point in a game where it crashes, turn off the Switch, come back several hours later and load my save and it will still crash at the exact same stage.

same games or different once?

 

[jamsplodge]

same games or different once?

All games crash at some point, but they will always crash at the same point, but I'm reluctant to spend hours and hours on a game like Xenoblade Chronicles 2 if it's gonna crash when I'm 60 hours in, you know what I mean?