Oh I didn't check the image posted... That's from atmosphere logo official, have always been like that when using fusee it uses the atmosphere boot logo B-)
A guy here seems to be facing the same problem, although on different OFW/CFW.
I usually don't file bug reports so lightly, but when I do it means I spent more hours than i can count troubleshooting the issue and I feel completely burnt out.
I...
The kip1 line is just for OC to load loader.kip OC settings, you don't use that line unless you use OC...
I also use exhospere to blank serial number like you and 90dns + I had a default.txt with the nintendo servers that we put in...
You are referring the to the splash screen being shown when launching a Hekate entry, and I indeed have a custom one, but the one I'm talking about is an atmosphere splash screen, unrelated to hekate. This used to be set by a BCT.ini file or...
I've done it already, multiple times, removing bit by bit until I completely emptied out these folders:
atmosphere/contents
atmosphere/exefs_patches
atmosphere/kip_patches
switch/.overlays
I reinstalled ams 1.6.2 and hekate 6.0.7 multiple times...
@SciresM would it be possible to ever add DDR200 support to HOS for much faster microSD speeds or just not possible hardware wise??
1715259819
Never had any problem...
Though I use fusee payload... But my FSS0 settings also work fine too:
Make...
if you like to have your serial blank (which really don't do anything today) you need to have your console completely offline of at least Atmosphère's DNSMiTM enabled.
Yeah, it is offline but I also have 90dns hosts loaded by exosphere when i turn wifi on for homebrews. This is just extra paranoid stuff, but I would like to keep it that way, unless the cal0blank is the only reason why it's crashing when booting...
Thanks! I understand you want me to remove emummcforce and atmosphere as they might be outdated (I guess), but will it still boot atmosphere from the emunand? I want to keep my sysnand as clean as possible, so I want to avoid accidentally booting...
Do you guys have any idea why i can boot Atmosphere on emunand via fusee.bin but not via hekate?
Since I updated firmware to 17.0.1 and atmosphere to 1.6.2 (hekate 6.0.7), I get the infamous Error 2162-0002 (0x4a2) on either program...