Hacking Kosmos 16 + patches = Corrupted card? Please help

[MushGuy]

Hello, so I'm currently having problems with updating Kosmos with patches. I try to update to Kosmos v16 and use the patches from this thread, but unfortunately, when it loads the CFW it gives me this error message:
A fatal error occurred when running Atmosphère
Title ID: 010041544d530000
Error Desc std: abort () called (0xffe)
Report saved to /atmosphere/ fatal_error/report_0000000005ca644a.bin

Press Power to reboot

Then when I load the card to my PC, it tells me that it's corrupted and that it needs to be reformated. Any help with this?

Also, I researched the error, and it seems that it's due to the PRODINFO, likely because of Incognito used on it. Should I restore the PRODINFO in order to make it work again? There was never this problem in previous versions of Atmosphère.

 

[Cyan]

I post it here for sake of gathering other similar case in the same thread.

@Clydefrosch had the same issue and it corrupted his SD card.
After trying to recover files it looks like corrupted FAT32 file table. but it was blank unrecognized first, like you.
https://gbatemp.net/threads/kosmos-a-hekate-cfw-package.506280/page-81#post-9039213

Hekate v5.2 with FW v9.1.0, AMS v??
(he said "latest hekate" on May 2nd, so I suppose he tried v5.2 released the day before)



@MushGuy, what's your SD card size?


Edit:
reading the issue on github, it seems it was because of using an incompatible partition table format.
Be sure your card is using MBR.
CTCaer said "FAT32 formatter.exe tool does not find any and it creates an SFD partition scheme."

It fixed the same problem other users had too.
I don't know anything about that SFD format, new things to learn for me!

 

[Clydefrosch]

Me included, using minitool to restore a MBR fixed this issue for a total of three people so far.

the steps in minitool were

1. Select your SD Card from the list at the bottom (and be very careful to not select your other drives)
2. in the left menu select delete partition, check again that this is your sd card and no other drive, because this will completely erase that drive and everything in it. if you're sure, click apply
3. next is rebuild MBR, apply again
4. finally, select create new partition (fat32 format , 32k) and apply again.

afterwards, put kosmos/atmosphere/whatever on the card and hekate shouldn't break anymore.


Fortunately for most users, this doesn't seem to be a very far spread issue. Only random cases here or there.

 

[MushGuy]

I post it here for sake of gathering other similar case in the same thread.

@Clydefrosch had the same issue and it corrupted his SD card.
After trying to recover files it looks like corrupted FAT32 file table. but it was blank unrecognized first, like you.
https://gbatemp.net/threads/kosmos-a-hekate-cfw-package.506280/page-81#post-9039213

Hekate v5.2 with FW v9.1.0, AMS v??
(he said "latest hekate" on May 2nd, so I suppose he tried v5.2 released the day before)



@MushGuy, what's your SD card size?


Edit:
reading the issue on github, it seems it was because of using an incompatible partition table format.
Be sure your card is using MBR.
CTCaer said "FAT32 formatter.exe tool does not find any and it creates an SFD partition scheme."

It fixed the same problem other users had too.
I don't know anything about that SFD format, new things to learn for me!

Hmm, usually I use Wii Backup Manager to format my card to fat32. I’ll have to check if it used MBR when I get home from work. Do I also have to restore the PRODINFO so that the error doesn’t happen again?

Me included, using minitool to restore a MBR fixed this issue for a total of three people so far.

the steps in minitool were

1. Select your SD Card from the list at the bottom (and be very careful to not select your other drives)
2. in the left menu select delete partition, check again that this is your sd card and no other drive, because this will completely erase that drive and everything in it. if you're sure, click apply
3. next is rebuild MBR, apply again
4. finally, select create new partition (fat32 format , 32k) and apply again.

afterwards, put kosmos/atmosphere/whatever on the card and hekate shouldn't break anymore.


Fortunately for most users, this doesn't seem to be a very far spread issue. Only random cases here or there.

Hmm, I’ll have to look up that tool. Let’s hope all this can fix my issue. Thanks for the advice.

 

[Clydefrosch]

Hmm, usually I use Wii Backup Manager to format my card to fat32. I’ll have to check if I used MBR when I get home from work. Do I also have to restore the PRODINFO so that the error doesn’t happen again?

Hmm, I’ll have to look up that tool. Let’s hope all this can fix my issue. Thanks for the advice.

I would assume most other partition managers probably have these same functions, minitool was just the one ctcaer told me to get when he worked this thing out.

the problem seems to be that some microsd cards just come with this SFD filetable format from the manufacturer, which is supposedly ancient and has no place to even exist anymore. Though for most use cases, it probably doesn't make much of a difference.
And most of the dedicated fat32 formaters, as well as windows own formatting utility, just leave it like they find it, when apparently, it would make more sense to overwrite that with MBR as that's more modern and standard and such.
The latest hekate expects MBR to be around and when it isn't, it just murders the whole thing in a panic.
As ctcaer is aware of this now, there'll likely be a fix soon that at least prevents it from panicking, giving people the chance to backup sd card contents before fixing the root cause.

bottomline, we just won the bad luck lottery with this one and it shouldn't happen again once it's fixed.
on the plus side, it's a good chance to weed out some of those games you were never playing anyways

 

[Cyan]

Thank you for reporting it and working with CTcaer on the solution and bringing it to others
sorry if I quoted you before finding your other posts on github. but thank you for your input here too!

 

[MushGuy]

Ok, but the question remains about PRODINFO. Do I have to restore it, too?

 

[Clydefrosch]

Thank you for reporting it and working with CTcaer on the solution and bringing it to others
sorry if I quoted you before finding your other posts on github. but thank you for your input here too!

No it's fine, the more people find this solution quickly, the better.
but lol, 'working with' I really just followed his instructions, he did all work

 

[Clydefrosch]

Ok, but the question remains about PRODINFO. Do I have to restore it, too?

no, prodinfo shouldn't have anything to do with this.
it's just that this error is thrown out a lot in different circumstances.
for example, it also occurs when archive bits aren't set correctly

 

[MushGuy]

no, prodinfo shouldn't have anything to do with this.
it's just that this error is thrown out a lot in different circumstances.
for example, it also occurs when archive bits aren't set correctly

Are you sure? Because one of the comments that I linked had the same error problem that was resolved by restoring the PRODINFO.

Edit: Well, what do you know? Reformatting using minitool did solve the problem! Now it boots without corrupting the system. I'm still thinking about restoring PRODINFO so that Atmostphère can do its own Incognito, instead. Thanks for the help, guys!

 

[Cyan]

Thank you for reporting you fixed it, and that it was the same MBR issue

My own opinion about prodinfo (do what you think is best):
I would prefer to have prodinfo restored, and official.
because if you lose your backup you can't restore or fix it.

But, for now, using AMS prodinfo intercepting to clean it on demand is in very beta phase and not safe yet until properly tested.
There might be some cached data stored somewhere else before the AMS "mitm" (man in the middle) intercepts and sends empty data.

So, I would wait a little until AMS can confirm it's working as intended and safely, then restore your official one.

 

[Lucasrissi]

Hello, thanks for all your help.

I have a similar problem and have taken all the steps but the problem remains. I am at a point where if a format my card (126gb) to ExFat i get the error in the first comment, and if I format the card to Fat32, the payload runs fine but the nintendo switch tells me that it cant read my card, that i have to take it out and put it again (it doesnt soleve anything).

Anyone have any ideas on what may be causing the error? I am clueless to where the problem might be, i am searching on the internet but still havent got a solution.

Thank you in advance!

 

[Draxzelex]

Hello, thanks for all your help.

I have a similar problem and have taken all the steps but the problem remains. I am at a point where if a format my card (126gb) to ExFat i get the error in the first comment, and if I format the card to Fat32, the payload runs fine but the nintendo switch tells me that it cant read my card, that i have to take it out and put it again (it doesnt soleve anything).

Anyone have any ideas on what may be causing the error? I am clueless to where the problem might be, i am searching on the internet but still havent got a solution.

Thank you in advance!

Have you tried using other CFW such as ReiNX?