Hello there! I'm new to the HB scene so I'm not quite sure about what's going on. About a week or two ago I successfully ran Atmosphere and Hekate on my switch (Atmosphere 0.19.2 & Hekate 5.5.5, which are the versions I'm currently using.) I was following the "switch.homebrew.guide" and by the end, it was written that creating an EmuMMC was the safest way to get around bans and whatnot. Since I only had a 32gb card, I bought a 128gb SD Card. I tested it through h2testw and it seems like it's neither defective nor fakem but ever since partitioning it and trying to boot into emuMMC/Atmosphere, it simply won't work.
If I try to boot straight into Atmosphere through its payload on my PC, I just get the "Failed to mounnt emuMMC from sd card partition!" error. If I try to do it through Hekate, I get the "Unknown pkg1 Version. HOS version not supported! Or emuMMC corrupt! Trying backup bootloader...". It then says "Found pkg1 (´´)", then goes into "unknown pkg1 versoin. HOS version not supported! Or emuMMC corrupt! Failed to launch HOS!". Then if I press any key, it sends me back to Hekate.
Anybody got a clue as to what's possibly going on? I read about some people saying that they never really created an EmuMMC on their SD Cards and that it could be the key to solving this problem, but I never really understand how they ended up fixing it since they never give out the details proper. Could you guys please help? Thanks in advance.
If I try to boot straight into Atmosphere through its payload on my PC, I just get the "Failed to mounnt emuMMC from sd card partition!" error. If I try to do it through Hekate, I get the "Unknown pkg1 Version. HOS version not supported! Or emuMMC corrupt! Trying backup bootloader...". It then says "Found pkg1 (´´)", then goes into "unknown pkg1 versoin. HOS version not supported! Or emuMMC corrupt! Failed to launch HOS!". Then if I press any key, it sends me back to Hekate.
Anybody got a clue as to what's possibly going on? I read about some people saying that they never really created an EmuMMC on their SD Cards and that it could be the key to solving this problem, but I never really understand how they ended up fixing it since they never give out the details proper. Could you guys please help? Thanks in advance.
Last edited by Kunzel,