Question about wonky EmuMMC

xkoeckiiej

Well-Known Member
OP
Newcomer
Joined
Feb 24, 2020
Messages
53
Trophies
0
XP
789
Country
Netherlands
Hi!
The other day I updated Deepsea from V4.2.0 to V4.3.0 via Hekate -> UMS on Windows.
Since then atmosphere would no longer boot and gave me Error Code 2002-3502.
Lurking on the internet i've found out that it had to do with accessibility to the EmuMMC.
After running the Payload "Common Problem Resolver.bin" I was able to get the Switch up and running again, although booting to the OS takes about a minute or 2.
In the Common Problem Resolver.bin I've chosen the options "Disable sysmodules, Delete themes, Fix clingwrap, Fix switch aio update, remove special folders created by mac".
Now some of my own backups have been corrupted on the SD card, then upon a reboot the games might work again.
It's very very wonky as it depends on the reboot whether it works or not.

Since I am not feeling it to continuously backup my savegames as the OS might crash and or brick upon an OS update.
I was wondering what would be the smartest plan of action to get it properly functioning again.
Rebooting might also still create the error 2002-3502.

Other things I've tried to no avail:
Remove the folders "Atmosphere, bootloader, sept" and replace it with a clean Atmosphere copy.
Updating sigpatches (thanks for the program mr dude).


Would it be smart to completely start over again and recreate an emummc from scratch.
Or is there any way I can find the culprit?
 
Last edited by xkoeckiiej,

Site & Scene News

Popular threads in this forum

General chit-chat
Help Users
    Xdqwerty @ Xdqwerty: @K3Nv2, then stop living in maryland