Corrupted Data Error after Updating from AMS 1.7.0 and OFW 17.0.0 to latest versions

[lucky13]

So everything was working great until I updated from AMS 1.7.0 and OFW 17.0.0 to all the latest versions including the latest sigpatches from here but now when starting some games that were working before it says "corrupted data has been detected. please run a check for corrupted data"

I normally boot my switch using latest fusee.bin and Atmosphere and all works fine until I try to load up around 50% of my games when I get the error above.

Do I need to do something with Sys-Patch to fix this ? I cant really find any guides on what to do with this ? I've extracted the files to my SD card and restarted Atmosphere but can't see how I load up sys-patch to apply the patches.

Can anyone help point me in the right direction ?

 

[Deleted member 681324]

Try updating sigpatches if you haven't

 

[lucky13]

Try updating sigpatches if you haven't

as mentioned above I've done this already ..any other ideas ?

 

[Deleted member 681324]

Then it's the patches ini file that needs updating?

 

[lucky13]

I've copied everything from the Hekate+AMS-package3-sigpatches-1.7.1-cfw-18.1.0V2 folder which included the Hekate+AMS-package3-sigpatches-1.7.1-cfw-18.1.0V2\bootloader\patches.ini file

Any other ideas ?

 

[Deleted member 681324]

Your 18.1.0V2 is SD root of file structure?

SD CARD (drive letter): bootloader/patches.ini (and all the other good stuff)

 

[kidkat210]

its your boot method. since ams 1.7, ips patches no longer work with fuse.bin (Link scroll down to "fusee no longer supports applying IPS patches to KIPs."). thanks to that change not all the patches for sig patches get loaded. so you got some options to fix this.
1) use a modified version of fuse,bin that re enables ips patches.
2) use a fairly new sys-module called sys-patch (link to op for info) (since the dev of it got a C&D for the project, it got dropped but some members of the community keep it alive - Download Link
3) use hekate's fss0 method of booting atmosphere

 

[Ethariel]

Hi,
I've got the same problem, with latest sigpatch, latest Deepsea. Solution seems to be sys-patch. I tried it, but I'm not sure it's working. Where/how to install it and how to check it's on ?
Thks

 

[Badablek]

Hi,
I've got the same problem, with latest sigpatch, latest Deepsea. Solution seems to be sys-patch. I tried it, but I'm not sure it's working. Where/how to install it and how to check it's on ?
Thks

sys-patch comes with a menu overlay. So you can use tesla to see if it patched or not (tesla-menu + nx-ovlloader).
but :

1. sys-patch works wonderfully (unzip at root of microSD and relaunch atmosphere)
2. launch anything and you will see if it works
3. (yes, it works)

 

[Ethariel]

Thank you for answering.
I unzip (and merge as the zip contains atmosphere/contents/420000000000000B folder). Then I reboot (soft reboot and full turn-off/RCM mode) the console and nothing changed : some games are ok, and the newest ones (new or updated) display the corrupted message.
I install an overlay viewer and there are 4 sysmodules. Three dynamic and 1 static. All are on "off". When I switch sys-ftp-light to on (for example) it stays "on" until I switch it again to off.
sys-patch is on "off" with a small house close to it (auto-start ?) and when I move it to "on" it goes "off" automatically after 2 or 3 seconds.

Ok, I've got the sys-patch overlay working. And all is to "patched" (fs, ldr, es in yellow, nifm).
Version : 1.5.2
Build : 11.06.2024 17:18:47
fw version : 18.1.0
ams : 1.7.1

Still not ok for some games.

Post automatically merged: Oct 2, 2024

Last news : after sys-patch installation if I accept to search for corrupted data (and none where found ofc) then I can run the game.

Conclusion : sys-patch is ok, just need to check for corrupted data

Thks this forum for the help.

 

[Badablek]

in fact, any game you tried to launch without the good sigpatches (or by using latest fusee which doesn't support KIP patching), before putting sys-patch, were automatically flagged as "corrupted"

and as you already understood, this is easily fixable by rescanning the "corrupted" content

 

[miniadri]

its your boot method. since ams 1.7, ips patches no longer work with fuse.bin (Link scroll down to "fusee no longer supports applying IPS patches to KIPs."). thanks to that change not all the patches for sig patches get loaded. so you got some options to fix this.
1) use a modified version of fuse,bin that re enables ips patches.
2) use a fairly new sys-module called sys-patch (link to op for info) (since the dev of it got a C&D for the project, it got dropped but some members of the community keep it alive - Download Link
3) use hekate's fss0 method of booting atmosphere

sys-patch comes with a menu overlay. So you can use tesla to see if it patched or not (tesla-menu + nx-ovlloader).
but :

1. sys-patch works wonderfully (unzip at root of microSD and relaunch atmosphere)
2. launch anything and you will see if it works
3. (yes, it works)

Hi, i'm having problems opening some games and getting them corrupted, i've double checked on getting sigpatches and sig-patch but they didn't run. I'm checking the sys-patch with tesla overlay and i've seen that it's OFF, i try to turn ON but suddenly it turns off again.
I have SX chip, hetake and atmos on last version, what can i do? I don't know how to do

modified version of fuse or

use hekate's fss0 method of booting

I launch Sys from Launch on hetake, have i to use from payloads?

 

[Badablek]

Hi, i'm having problems opening some games and getting them corrupted, i've double checked on getting sigpatches and sig-patch but they didn't run. I'm checking the sys-patch with tesla overlay and i've seen that it's OFF, i try to turn ON but suddenly it turns off again.
I have SX chip, hetake and atmos on last version, what can i do? I don't know how to do

I launch Sys from Launch on hetake, have i to use from payloads?

Hi,

sys-patch is a sysmodule which is loaded when Atmosphere starts, so there is no need to activate anything. And yes, you have to use Launch menu on Hekate (with correct hekate_ipl.ini file)

with a clean install (without any config file or tweak in sys-patch options), by default, all patches are ON and applied on both sysMMC and emuMMC. You have to go to the "Log" sub-menu to check the status of each patch (fs, ldr, es, acid, etc.), it must say "patched" (green) or "unpatched" (red).

And no need to use sigpatches at the same time...but if you do it, with fss0 method on hekate (with the line to load sigpatches, obviously), it must work (even if sys-patch does not work). sigpatches are not loaded only with fusee.


check your setup, something is wrong or missing.

 

[miniadri]

Hi,

sys-patch is a sysmodule which is loaded when Atmosphere starts, so there is no need to activate anything. And yes, you have to use Launch menu on Hekate (with correct hekate_ipl.ini file)

with a clean install (without any config file or tweak in sys-patch options), by default, all patches are ON and applied on both sysMMC and emuMMC. You have to go to the "Log" sub-menu to check the status of each patch (fs, ldr, es, acid, etc.), it must say "patched" (green) or "unpatched" (red).

And no need to use sigpatches at the same time...but if you do it, with fss0 method on hekate (with the line to load sigpatches, obviously), it must work (even if sys-patch does not work). sigpatches are not loaded only with fusee.


check your setup, something is wrong or missing.

so, if i do a clean install again without sigpatches, only sys-patch, i would be able to play as normal? I've checked and it says patched (orange).
Do you have one clean install to sent to me (by pm if this couldn't be shared) or some correct hekate file? Or with copy-paste from this topic will be enough: https://gbatemp.net/threads/sigpatches-for-atmosphere-hekate-fss0-fusee-package3.571543/

I'm a little bit lost with the fss0 and so many things, some time ago i downloaded, replaced and run hahaha.
I think i need a stept by stept from 0 and save it for future updates

 

[Badablek]

just use the latest sys-patch, you can download v1.5.2 here on GBAtemp (nothing against GBAtemp rules)

orange means you have both sigpatches and sys-patch, so patches are actually applied (twice)

with only syspatch, you don't have to add anything to hekate_ipl.ini
it's only needed with sigpatches (fss0 method). And as it's orange on the log, it means your hekate_ipl.ini is already good...and also means you're already using fss0 method (or patched fusee.bin)


ps : fss0 means hekate unpacks all the stuff from package3, without relying on fusee.
the other method is to chainload fusee from Hekate, but this means no KIP patching (sigpatches not applied)

 

[miniadri]

just use the latest sys-patch, you can download v1.5.2 here on GBAtemp (nothing against GBAtemp rules)

orange means you have both sigpatches and sys-patch, so patches are actually applied (twice)

with only syspatch, you don't have to add anything to hekate_ipl.ini
it's only needed with sigpatches (fss0 method). And as it's orange on the log, it means your hekate_ipl.ini is already good...and also means you're already using fss0 method (or patched fusee.bin)


ps : fss0 means hekate unpacks all the stuff from package3, without relying on fusee.
the other method is to chainload fusee from Hekate, but this means no KIP patching (sigpatches not applied)

yeah, i wanted to say to give to me a full copy of a SD with all working (atmos, hekate, sys-patch...) and see if it works and have it has one start point for next updates.
I have made a new "clean" install deleting atmosphere, bootloader, and something more, i put deepsea advance with the other things and the hekate file, i have turn on syscfw and get something about nosigchk missing in red. I pressed continue and still get the sys-patch orange but i have tried to install and test the new Zelda.xci with awoo (it didn't work before) and seems to be working. I have to do more testing.

 

[Badablek]

yeah, i wanted to say to give to me a full copy of a SD with all working (atmos, hekate, sys-patch...) and see if it works and have it has one start point for next updates.
I have made a new "clean" install deleting atmosphere, bootloader, and something more, i put deepsea advance with the other things and the hekate file, i have turn on syscfw and get something about nosigchk missing in red. I pressed continue and still get the sys-patch orange but i have tried to install and test the new Zelda.xci with awoo (it didn't work before) and seems to be working. I have to do more testing.

deepsea is not what we can define as "clean", beware of AIO pack. I'm not saying it's bad to use it, but this one adds a lot of uneeded stuff and seems to modify hekate_ipl.ini.
you must be aware of that !

a real clean install = vanilla Atmosphere + vanilla Hekate + vanilla sys-patch. Nothing else (except sysmodules you really need and use : Edizon, Tesla, missionControl, etc.).



nosigchk missing → hekate_ipl.ini still contains a line about nosigchk in [CONFIG] section, so it tries to load sigpatches (and as you use now sys-patch, Hekate is not able to load it). Remove any line that refers to "nosigchk".

 

[TomSwitch]

yeah, i wanted to say to give to me a full copy of a SD with all working (atmos, hekate, sys-patch...) and see if it works and have it has one start point for next updates.
I have made a new "clean" install deleting atmosphere, bootloader, and something more, i put deepsea advance with the other things and the hekate file, i have turn on syscfw and get something about nosigchk missing in red. I pressed continue and still get the sys-patch orange but i have tried to install and test the new Zelda.xci with awoo (it didn't work before) and seems to be working. I have to do more testing.

Check the date of whatever you are putting on your sd, when was deepsea last get an update? When there is a major atmosphere update everything that was released earlier than that should be treated with caution. It is like you ate expired food and was surprised you have upset stomach.

Just do clean atmosphere, host file if needed, matching fusee, sys-patch if needed then you should be good to go.

 

[maduro]

Thanks Sys-Patches linked above worked. As mentioned, anything that may still show as corrupted just re-run the check and it'll run after.

 

[GaaraPrime]

its your boot method. since ams 1.7, ips patches no longer work with fuse.bin (Link scroll down to "fusee no longer supports applying IPS patches to KIPs."). thanks to that change not all the patches for sig patches get loaded. so you got some options to fix this.
1) use a modified version of fuse,bin that re enables ips patches.
2) use a fairly new sys-module called sys-patch (link to op for info) (since the dev of it got a C&D for the project, it got dropped but some members of the community keep it alive - Download Link
3) use hekate's fss0 method of booting atmosphere

Thank you so much! I really appreciate this!

Been struggling a lot, trying to figure out what went wrong and how to make it work. I use Sysnand CFW and sigpatches, and I used to simply inject fusee.bin and directly boot into Atmosphere without Hekate, and it used to work great.

First had to figure out why this current method was not working. Found your post which stated the reason why (ams 1.7 sigpatches don't work with fusee.bin anymore).

Then after a shit ton of research, again found your post mentioning the three methods I can use to make it all work. For some reason, Step 1 doesn't work for me.

Step 2, I was mistakenly using sys-patch with ams 1.7. Later found out sys-patch only works with ams 1.8.

I fixed it and now it's working PERFECTLY! I'm currently on Firmware 18.1.0 and AMS 18 (pre-release) and using sys-patch 1.5.4.

Thanks a lot again! Couldn't have done it without you!