Hacking Homebrew Remove Atmosphere splash screen

  • Thread starter Thread starter pausuri
  • Start date Start date
  • Views Views 21,602
  • Replies Replies 81
Can I ask how you open the insert_splash_screen script? When I double-click to run it, the terminal does not appear, but a black screen flashes by (*I know this question is stupid, I hope you can help me
That's a Python script, so you need a implementation of Python on your system
 
Hello there, looking on the source code we have:

  • "/img/Splash.bin" which is created by using originally this image:
This one can be replaced on a package3 file using the Script on the source code of Atmosphère, easy piece.​
also you can create a custom splash.bin and build Atmosphère, but is no just as easy.​

  • And "/stratosphere/boot/source/boot_splash_screen_notext.inc"
which originally is this image:​
This only can be changed by replacing the file on the source and building Atmosphère.​

Just writing this with the images I was aware I interchanged them on the previous post, sorry for the mixup.
Im trying to get rid of this black and white atmosphere splash screen. any guide to do it? just new with switch modding.
 
i have two screens in a row and im able to change only the first one with the pyton script is there an easy way to change the second one?
 
i have two screens in a row and im able to change only the first one with the pyton script is there an easy way to change the second one?
Booting atmosphère fusee.bin, there is no way way, that can be only changed by building the code.

If you boot hekate, you can change the splash as easy as coping a new file to your card
 
  • Like
Reactions: miola
Booting atmosphère fusee.bin, there is no way way, that can be only changed by building the code.

If you boot hekate, you can change the splash as easy as coping a new file to your card
is there a way to skip it maybe?
coz i had only one splash. but while i was trying to change it, it stats showing me two (mine and hardcoded)
but maybe i was seeing two identical initially, idk
 
is there a way to skip it maybe?
coz i had only one splash. but while i was trying to change it, it stats showing me two (mine and hardcoded)
but maybe i was seeing two identical initially, idk
Remember, booting Atmosphère using fusee.bin OR Hekate vía Fusee.bin payload chainload there are 3 images:
  • Sept Logo (seems this is NOT the sept logo), lets call it «the atmosphère's triangle» is displayed when fusee initialize the graphical screen, is hardcoded on the Package3 binary. only can be changed by building a new atmosphère from source code, by changing the file /stratosphere/boot/source/boot_splash_screen_notext.inc
    [ATTACH type="full" width="66px" size="210x172"]524450[/ATTACH]
  • Splash, is displayed by atmosphère when Package3 is full loaded, this image can be changed on a existing package3 file using the script /utilities/insert_splash_screen.py of the source code or building a new package3 from code by changing the file /img/splash.bin.
    1756246899385.png
  • Boot Logo,
  • displayed by original firmware once the screen is full initialized. Can be changed by IPS patches, you can generate that set of patches using the instructions on thread https://gbatemp.net/threads/custom-boot-logo-for-switch.569031/ also there is a big collection of premade patches on the post https://gbatemp.net/threads/custom-boot-logo-for-switch.569031/post-10662039

    1755624907318.webp

A example of the original logos is on the post https://gbatemp.net/threads/custom-boot-logo-for-switch.569031/post-10439867


If you boot via Hekate FSS0, the splash logo is not displayed and they are replaced by bootlogo which can be setup on the hekate_ipl.ini file by setting up the directive logopath=bootloader/bootlogo.bmp, this way you can change it by editing the hekate_ipl.ini or changing the file indicated on it.

By this and so many other advantages I really love to boot via Hekate's PKG3/FSS0, I do not need to mess around with Atmosphère's boot logo and mine is very easy set by changing a file on the SD Card.
 

Attachments

  • 1756246885084.png
    1756246885084.png
    1.4 KB · Views: 41
Last edited by impeeza,
Thanks for explanation - now it is clear.
and it is clear that i don't know what dopes it mean to boot via hekate fss0

my procces is following:
  • i have atmosphere with kefir.
  • i see hekate splash (progress bar) - where i can hold vol- to enter hekate
    • if go with CFW:
      • then i see splash i've added to using the py-script
      • then i see atmos splash.
      • then i see switch (modified) splash
So i assume accordign to you message that i go with Hekate vía Fusee.bin payload chainload

What should i change to boot via Hekate FSS0 every time i load CFW?
will it be the same CFW?
 
  • Like
Reactions: laz305
Thanks for explanation - now it is clear.
and it is clear that i don't know what dopes it mean to boot via hekate fss0

my procces is following:
  • i have atmosphere with kefir.
  • i see hekate splash (progress bar) - where i can hold vol- to enter hekate
    • if go with CFW:
      • then i see splash i've added to using the py-script
      • then i see atmos splash.
      • then i see switch (modified) splash
So i assume accordign to you message that i go with Hekate vía Fusee.bin payload chainload

What should i change to boot via Hekate FSS0 every time i load CFW?
will it be the same CFW?
If you like show us a copy of your SDMC:/bootloader/hekate_ipl.ini may be you are using FUSEE.BIN chainload,

Hekate's FSS0 is a method of loading Package3 where Hekate replace completely FUSEE.BIN, Hekate reads PACKAGE3 file extract the needed data and start the booting. so no Atmosphère's splash are shown.

To setup FSS0 you need to edit Hekate_ipl.ini file and add a section like:

Code:
[CFW (EMUMMC)]
id=EMUNAND
emummcforce=1
fss0=atmosphere/package3
atmosphere=1
logopath=bootloader/bootloader.bmp
icon=bootloader/res/payload_hue_nobox.bmp
kip1patch=nosigchk
usb3force=1



Also you can edit the first lines of the Hekate_ipl.ini to autoboot any of the sections of the file:

Code:
[config]
autoboot=2

in this case hekate is tell to boot the second entry on the file.
 
  • Like
Reactions: laz305 and miola
If you like show us a copy of your SDMC:/bootloader/hekate_ipl.ini may be you are using FUSEE.BIN chainload,
this is what i have in it

[config]
autoboot=2
autoboot_list=0
bootwait=3
backlight=40
noticker=0
autohosoff=2
autonogc=0
updater2p=0
bootprotect=0
{}

[Atmosphere]
payload=bootloader/payloads/fusee.bin
logopath=bootloader/bootlogo_kefir.bmp
icon=bootloader/res/atmosphere.bmp
{}
[Full Stock]
fss0=atmosphere/package3
emummc_force_disable=1
stock=1
logopath=bootloader/bootlogo_kefir.bmp
icon=bootloader/res/switch.bmp
{}
{-----------------------------------}
{}
 
this is what i have in it

[config]
autoboot=2
autoboot_list=0
bootwait=3
backlight=40
noticker=0
autohosoff=2
autonogc=0
updater2p=0
bootprotect=0
{}

[Atmosphere]
payload=bootloader/payloads/fusee.bin
logopath=bootloader/bootlogo_kefir.bmp
icon=bootloader/res/atmosphere.bmp
{}
[Full Stock]
fss0=atmosphere/package3
emummc_force_disable=1
stock=1
logopath=bootloader/bootlogo_kefir.bmp
icon=bootloader/res/switch.bmp
{}
{-----------------------------------}
{}
your hekate_ipl.ini have two entries the first chainload fusee.bin (the version on SDMC:/bootloader/payloads/fusee.bin) and the second loads Package3 using FSS0 method. and is setup to autoload last one. if you do not stop the loading of hekate and allows it to autoboot, which splash do you get?
 
your hekate_ipl.ini have two entries the first chainload fusee.bin (the version on SDMC:/bootloader/payloads/fusee.bin) and the second loads Package3 using FSS0 method. and is setup to autoload last one. if you do not stop the loading of hekate and allows it to autoboot, which splash do you get?
in normal load without interrupting OFW loads (and it is fine for me) i see nintendo splash (after hekate bootloader)

if i go to hekate and choose atmosphere i will see:
  • splash i've added using the py-script
  • atmos splash.
  • switch (modified) splash
 
Last edited by miola,
Hi all!
I want add aditional bootlogo to hekate. When I select CFW, first I watch hekate logo, in second position I watch a atmosphere logo and finally whatch a switch logo.
I want add a other one bettwen atmosphere logo and switch logo. I wan't change. I want add.
It's possible??

I have hekate and pakage3 but here only watch the logos of the Launch Menu. No bootlogos.

[config]
updater2p=1

[MAGIA]
pkg3=atmosphere/package3
kip1=atmosphere/kips/*
emummcforce=1
icon=bootloader/res/icon_switch.bmp

[OFICIAL NINTENDO]
pkg3=atmosphere/package3
emummc_force_disable=1
stock=1
icon=bootloader/res/icon_switch.bmp
 
Just tried the steps to change the Atmosphere logo and they are not working, at least on switches with modchip(no fusee).
Tried with png/bmp image in the correct res. and the python code executes successfully but then logo is still the same.
 
Just tried the steps to change the Atmosphere logo and they are not working, at least on switches with modchip(no fusee).
Tried with png/bmp image in the correct res. and the python code executes successfully but then logo is still the same.
Which one of the 4 logos are you trying to change?

Which sequence of boot do you have?
 

Site & Scene News

Popular threads in this forum