Hacking Atmosphere-NX - Custom Firmware in development by SciresM

[proconsule54]

Always do a clean atmosphere setup as suggested by @Milenko when upgrading atmosphere.
this is the most secure way to get booting without problems!

 

[Gobracket]

i can go without problem with CFW emummc with firmware 13.0.0.
But get pkg2 decryption failed when loading OFW. anyone get the same?

CFW 13.0.0
OFW 13.0.0

sx core
chain via hekate
latest atmo + hekate
-------------------------
update:
I restored my NAND and it works.

 

[Rashed]

If you have a 0100000000000008 folder in contents, delete it

Otherwise do a clean atmosphere setup

thanks. Seems like that error is gone after I made a change in ini hekate ini file.

i am missing one option now. Previously when in Atmosphere I pressed power button and chose Restart the switch would restart into Hekate but now it restarts back into Atmosphere.

Any idea how can I get that back?

thanks

 

[M7L7NK7]

thanks. Seems like that error is gone after I made a change in ini hekate ini file.

i am missing one option now. Previously when in Atmosphere I pressed power button and chose Restart the switch would restart into Hekate but now it restarts back into Atmosphere.

Any idea how can I get that back?

thanks

You need to rename the hekate .bin you use inject to reboot_payload.bin and replace the one that is in the atmosphere folder

 

[Rashed]

You need to rename the hekate .bin you use inject to reboot_payload.bin and replace the one that is in the atmosphere folder

thank you so much. That did the trick.

 

[m3anmug]

How are you guys updating on Emunand? I usually download the latest firmware from darthsternie.net but it only has 12.1.0 as the latest release? Is there another place do download firmware?

 

[itchigo]

How are you guys updating on Emunand? I usually download the latest firmware from darthsternie.net but it only has 12.1.0 as the latest release? Is there another place do download firmware?

You can download fw 13 from AIO-Switch-Updater as it's available now

 

[m3anmug]

Alright thanks.


I have another question if anyone can help?

I was looking forward to using the new Bluetooth option and it works fine but it only works with the internet on. I always keep airplane mode on unless im using Tinfoil.

Is it ok to have the wifi on while playing games while using 90 DNS?

Edit: Well i just turned off auto connect on my wifi so there is no internet. I guess that will work.

 

[UnderJinx]

Hello hope someone can help here
A fatal error occurred when running fusee

Failed to run tsec_keygen firmware.
press power to reboot and games works anyway.

When im booting via Hekate launch emuMMC it says wron ini or missing/corrupt files.
Should i have deleted the old hekate ini upon the new install.

Sorry this is new for me how do i get rid of the errors.

Im running emunand 12.1.0 Atm 1.0.0 Hekate 5.6.2 and used to run Atm via hekate Fusee.
Anyone know what's wrong before i mess it up more.

 

[impeeza]

You didn't read the release of Hekate and you didn't update your hekate_ipl.ini, look at the text on release page:

Notice about Atmosphere 1.0.0 and up: The fss0=atmosphere/fusee-secondary.bin in hekate_ipl.ini must be changed to fss0=atmosphere/package3

 

[UnderJinx]

You didn't read the release of Hekate and you didn't update your hekate_ipl.ini, look at the text on release page:

Notice about Atmosphere 1.0.0 and up: The fss0=atmosphere/fusee-secondary.bin in hekate_ipl.ini must be changed to fss0=atmosphere/package3

Thanks for your input
Changed all the fss0=atmosphere/fusee-secondary.bin lines to fss0=atmosphere/package3.
But the error persists.

 

[Hayato213]

Thanks for your input
Changed all the fss0=atmosphere/fusee-secondary.bin lines to fss0=atmosphere/package3.
But the error persists.

What model you have? how are you injecting payload? via computer? via dongle?

 

[UnderJinx]

What model you have? how are you injecting payload? via computer? via dongle?

Model is Erista patched SXOS

 

[Hayato213]

Model is Erista patched SXOS

You need to load up hekate then load Atmosphere that way. Also check your hekate_ipl.ini

 

[UnderJinx]

You need to load up hekate then load Atmosphere that way. Also check your hekate_ipl.ini

yes that's what i do booting via hekate fusee.
What's with the hekate ipl i thought it was enough to change the lines.
So i can not use an old ipl from a later Atm install.

 

[Hayato213]

yes that's what i do booting via hekate fusee.
What's with the hekate ipl i thought it was enough to change the lines.
So i can not use an old ipl from a later Atm install.

Atmosphere 1.0.0 change the line of fusee-primary.bin to fusee.bin and fusee-secondary.bin to package3 you need to adjust accordingly.

 

[UnderJinx]

Atmosphere 1.0.0 change the line of fusee-primary.bin to fusee.bin and fusee-secondary.bin to package3 you need to adjust accordingly.

yes i have the fusee bin in the payloads folder and package 3 in atmosphere folder
and i changed all the fss0=atmosphere/fusee-secondary.bin lines in hekate ipl to fss0=atmosphere/package3.
Is there something else i should do. Maybe do a clean install

 

[Hayato213]

yes i have the fusee bin in the payloads folder and package 3 in atmosphere folder
and i changed all the fss0=atmosphere/fusee-secondary.bin lines in hekate ipl to fss0=atmosphere/package3.
Is there something else i should do. Maybe do a clean install

[config]
autoboot=0
autoboot_list=0
bootwait=3
verification=1
backlight=100
autohosoff=0
autonogc=1
updater2p=1

{DeepSea}
{Github: https://github.com/orgs/Team-Neptune/}

{--- Custom Firmware ---}
[CFW (SYSNAND)]
emummc_force_disable=1
fss0=atmosphere/package3
atmosphere=1
logopath=bootloader/bootlogo.bmp
icon=bootloader/res/icon_payload.bmp
{}

[CFW (EMUMMC)]
emummcforce=1
fss0=atmosphere/package3
atmosphere=1
logopath=bootloader/bootlogo.bmp
icon=bootloader/res/icon_payload.bmp
{}

{--- Stock ---}
[Stock (SYSNAND)]
emummc_force_disable=1
fss0=atmosphere/package3
stock=1
icon=bootloader/res/icon_switch.bmp
{}

you need something like this, if you use emunand you need the emummcforce=1

Probably be best off if you get rid of old Atmosphere files and replace new 1.0.0 one.

 

[slaphappygamer]

Probably be best off if you get rid of old Atmosphere files and replace new 1.0.0 one.

I had some other errors and doing this worked for me. I’d see the atmosphere boot logo, then black screen. After deleting and replacing the atmosphere directory, everything worked.

 

[UnderJinx]

[config]
autoboot=0
autoboot_list=0
bootwait=3
verification=1
backlight=100
autohosoff=0
autonogc=1
updater2p=1

{DeepSea}
{Github: https://github.com/orgs/Team-Neptune/}

{--- Custom Firmware ---}
[CFW (SYSNAND)]
emummc_force_disable=1
fss0=atmosphere/package3
atmosphere=1
logopath=bootloader/bootlogo.bmp
icon=bootloader/res/icon_payload.bmp
{}

[CFW (EMUMMC)]
emummcforce=1
fss0=atmosphere/package3
atmosphere=1
logopath=bootloader/bootlogo.bmp
icon=bootloader/res/icon_payload.bmp
{}

{--- Stock ---}
[Stock (SYSNAND)]
emummc_force_disable=1
fss0=atmosphere/package3
stock=1
icon=bootloader/res/icon_switch.bmp
{}

you need something like this, if you use emunand you need the emummcforce=1

Probably be best off if you get rid of old Atmosphere files and replace new 1.0.0 one.

Okay i'll try with a clean install with the latest deepsea release if i use that everything should be ok right. But what's with the commonproblemresolver.bin in the deepsea payloads folder