Hacking Atmosphere-NX - Custom Firmware in development by SciresM

[josete2k]

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 0100000000001000 or 010000000000100C (seems to be random) . I already knew these kind of programs referred to custom themes being installed and incompatible with the new release, although i've never been interested in themes and i don't have those folders in atmosphere/contents.

So far I've tried to clean up my atmosphere/contents folder and updating all tesla overlays but to no avail. I also removed tesla menu and the .overlays contents completely, but still getting a crash when loading Atmosphere.

I can boot into atmosphere only by loading fusee.bin from the hekate menu, and everything works as expected (even tesla and all overlays).

The moment I try to reboot and launch the emummc via hekate, I get the same error again and I have to reboot and load fusee.bin to boot into atmosphere.

The hekate_ipl.ini settings I'm trying to load (which worked on earlier atmosphere versions) is this:

[Atmosphere (emuMMC)]
fss0=atmosphere/package3
kip1patch=nosigchk
emummcforce=1
cal0blank=1
atmosphere=1
logopath=bootloader/res/bootlogo-emunand-f.bmp
icon=bootloader/res/icon_payload.bmp

Do you have any idea what might be wrong with the way I'm loading atmosphere via hekate?

Remove these lines

emummcforce=1
cal0blank=1
atmosphere=1

 

[Montblanc]

Remove these lines

emummcforce=1
cal0blank=1
atmosphere=1

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 cfw on sysnand.

Also, I used cal0blank=1 to hide my serial number, and I still plan on doing that. Is there a more recent way to hide it?

 

[impeeza]

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 cfw on sysnand.

Also, I used cal0blank=1 to hide my serial number, and I still plan on doing that. Is there a more recent way to hide it?

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.

 

[Montblanc]

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 via hekate.

 

[4d1xlaan]

unless the cal0blank is the only reason why it's crashing when booting via hekate

it's not, your crash isnt a nim crash

 

[Montblanc]

it's not, your crash isnt a nim crash

EDIT: I wasn't able to boot atmosphere with fss0 in any way, so I filed an issue on hekate repo.

 

[guily6669]

@SciresM would it be possible to ever add DDR200 support to HOS for much faster microSD speeds or just not possible hardware wise??

Post automatically merged: May 9, 2024

EDIT: I wasn't able to boot atmosphere with fss0 in any way, so I filed an issue on hekate repo.

Never had any problem...

Though I use fusee payload... But my FSS0 settings also work fine too:

Spoiler: hekate settings

[config]
autoboot=0
autoboot_list=0
bootwait=3
noticker=0
autohosoff=0
autonogc=1
updater2p=0
backlight=47

[Atmosphere CFW]
fss0=atmosphere/package3
kip1patch=nosigchk
kip1=atmosphere/kips/loader.kip
emummcforce=1
icon=bootloader/res/icon_payload.bmp

[Atmosphere SAFE MODE]
fss0=atmosphere/package3
kip1patch=nosigchk
emummcforce=1
icon=bootloader/res/icon_payload.bmp

[Stock - sysMMC]
fss0=atmosphere/package3
emummc_force_disable=1
stock=1
icon=bootloader/res/icon_switch.bmp

Make sure you have everything updated and using latest sigpatches or latest sys-patch and make sure it's not some module you have in atmosphere\contents that is causing the crash...

Do a full clean hekate+atmosphere 1.7.0 install.

 

[Montblanc]

Never had any problem...

I though I use fusee payload, this settings are my FSS0 and work fine too:

Spoiler: hekate settings

[config]
autoboot=0
autoboot_list=0
bootwait=3
noticker=0
autohosoff=0
autonogc=1
updater2p=0
backlight=47

[Atmosphere CFW]
fss0=atmosphere/package3
kip1patch=nosigchk
kip1=atmosphere/kips/loader.kip
emummcforce=1
icon=bootloader/res/icon_payload.bmp

[Atmosphere SAFE MODE]
fss0=atmosphere/package3
kip1patch=nosigchk
emummcforce=1
icon=bootloader/res/icon_payload.bmp

[Stock - sysMMC]
fss0=atmosphere/package3
emummc_force_disable=1
stock=1
icon=bootloader/res/icon_switch.bmp

Make sure you have everything updated and using latest sigpatches or latest sys-patch and make sure it's not some module you have in atmosphere\contents that is causing the crash...

Do a full clean hekate+atmosphere 1.7.0 install.

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 but the outcome is always the same: it only boots with fusee.bin and crashes with fss0.

I heard 17.0.0 had troubles with blanking out the prodinfo, which I've always been doing, so I ended up deleting exosphere.ini and related flags from hekate but the result was still the same. Eventually I found out that the PRODINFO blanking was fixed already with atmosphere 1.6.2 (and my serial is blank indeed). Also, I never used Incognito to erase the prodinfo, but always a combination of exosphere and 90dns hosts.

I was looking at your hekate_ipl.ini and did not recognize the kip1=atmosphere/kips/loader.kip line (which is the only thing beside a missing cal0blank to be different from mine), so I made a quick google search (where i figured out i don't need it) and stumbled upon this reddit post.

A guy in the comments also boots emuMMC with fusee.bin and has no entry in hekate_ipl.ini where they boot emunand with fss0.

Furthermore, I noticed that a custom bootlogo is showing up when launching ams this way (even after cleaning ams / config folders and copying original files over). I recall having this boot image back when I created my first emuMMC and installed a bundled cfw. I don't think that picture is supposed to be stock in ams 1.6.2 but there is no trace on my sdcard of any custom bootlogo file.

I guess the only solution would be to recreate my emuMMC and start fresh, but I'm too lazy for that.

Thanks for the tips anyways.

 

[guily6669]

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 but the outcome is always the same: it only boots with fusee.bin and crashes with fss0.

I heard 17.0.0 had troubles with blanking out the prodinfo, which I've always been doing, so I ended up deleting exosphere.ini and related flags from hekate but the result was still the same. Eventually I found out that the PRODINFO blanking was fixed already with atmosphere 1.6.2 (and my serial is blank indeed). Also, I never used Incognito to erase the prodinfo, but always a combination of exosphere and 90dns hosts.

I was looking at your hekate_ipl.ini and did not recognize the kip1=atmosphere/kips/loader.kip line (which is the only thing beside a missing cal0blank to be different from mine), so I made a quick google search (where i figured out i don't need it) and stumbled upon this reddit post.

A guy in the comments also boots emuMMC with fusee.bin and has no entry in hekate_ipl.ini where they boot emunand with fss0.

Furthermore, I noticed that a custom bootlogo is showing up when launching ams this way (even after cleaning ams / config folders and copying original files over). I recall having this boot image back when I created my first emuMMC and installed a bundled cfw. I don't think that picture is supposed to be stock in ams 1.6.2 but there is no trace on my sdcard of any custom bootlogo file.

I guess the only solution would be to recreate my emuMMC and start fresh, but I'm too lazy for that.

Thanks for the tips anyways.

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 atmosphere/hosts folder...

The bootlogo is likely from your Hekate settings, example: "icon=bootloader/res/icon_payload.bmp", you can even add your own images for the boot icons on Hekate.

 

[Montblanc]

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 atmosphere/hosts folder...

The bootlogo is likely from your Hekate settings, example: "icon=bootloader/res/icon_payload.bmp", you can even add your own images for the boot icons on Hekate.

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 something like that but i can't find any configuration file or image related to the one i posted above that is appearing when booting ams via fusee.bin.

Not that I really care, but this rang a bell that some ancient shenanigans might still be in place on my emuMMC, as it's always been the same image.

 

[guily6669]

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

 

[Montblanc]

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 could have formatted my sd card and remade everything from scratch, but that's not a solution and certainly I could not recreate the same environment to reproduce the crash and pinpoint the real cause.

I guess I'll be stuck with injecting fusee for the time being.

 

[NeoGranzon]

Sorry guys i have a doubt: iupdated a game and it asked me to update the firmware whem boot(i have OFW 18.0.0/AMS 17.0.0).
If i install the latest OFW on 18.0.1 do i have problems with AMS 17.0.0 or does it work without problems?

 

[impeeza]

Sorry guys i have a doubt: iupdated a game and it asked me to update the firmware whem boot(i have OFW 18.0.0/AMS 17.0.0).
If i install the latest OFW on 18.0.1 do i have problems with AMS 17.0.0 or does it work without problems?

for most people Atmosphère 1.07.0 works just fine.