Hacking Custom Boot Logo for Switch

  • Thread starter Thread starter chronoss
  • Start date Start date
  • Views Views 219,217
  • Replies Replies 831
  • Likes Likes 17
View attachment 400625

my apologies, I misread it. This should be correct.
SMW5.png
SMW1.png
SMW2.png
SMW3.png
SMW4.png
SMW5.png
 

Attachments

Maybe this can help you:


How to create a file to change Atmosphère bin file and the build it:
https://gbatemp.net/threads/custom-boot-logo-for-switch.569031/post-9941051

How to build Atmosphère from Source Code:
https://gbatemp.net/threads/building-atmosphere-on-windows-using-msys2.613446/




Hekate Splash Screen:
https://gbatemp.net/blogs/splash-screens.19288/

First of all, thank you very much.

I followed the first link, all successfully. However, compiling then atmosphere... seems like a world to me. I have to dedicate more time.

On the other hand, I have seen that atmosphere includes a tool to patch Package3 and "inject" the splash into it.

I launch the script and although apparently the entire process is done, package3 is not modified since the default logo continues to appear. Could it be because you are using Mac Os? Thank you
 
  • Like
Reactions: impeeza
There is a Script for anybody, do not need to you install anything but can not use the "Original Logo" for create the smallest patches, so all patches created with it are the maximum size (570,042 bytes)

You can get it from:

https://github.com/StarDustCFW/Logo-para-switch.Palomitas/releases/

using the "Original Logo" you always get the smallest ips size.
 

Attachments

I have repeated the proccess so many times and no logo works.
The ones provided are working.

I have installed pythoon, ips.py, pillow and image are PNG with correct size.
Do I need to use any special software to generate the PNG?
 
I have repeated the proccess so many times and no logo works.
The ones provided are working.

I have installed pythoon, ips.py, pillow and image are PNG with correct size.
Do I need to use any special software to generate the PNG?
I can answer you but I am afraid to be censored by a Jurassic mod, because will be a copy and paste of some old threads.

for using the friedkeenan-Pythontool you don't need anymore you have, if you are more confortable you can use this other tool https://github.com/StarDustCFW/Logo-para-switch.Palomitas/releases/tag/1.7 is similar only generate a little bit bigger files but have everything encapsulated on an only package so is download and run.
 
  • Like
Reactions: crueI
I can answer you but I am afraid to be censored by a Jurassic mod, because will be a copy and paste of some old threads.

for using the friedkeenan-Pythontool you don't need anymore you have, if you are more confortable you can use this other tool https://github.com/StarDustCFW/Logo-para-switch.Palomitas/releases/tag/1.7 is similar only generate a little bit bigger files but have everything encapsulated on an only package so is download and run.
Thanks for your reply.
I'm an advanced user and I think I have found a bug somewhere.
I'm on 17.0.0 and using exfat.
When I copy the output folder to exefs_patches folder, sometimes it works and sometimes it doesn't.

What I tested:

1. I have deleted all ips files that are not needed for this FW version (only 5 are used).
Same weired result

2. I have injected multiple times the payload.
Same weired result

3. I tried renaming several times the output folder.
Same weired result

4. I was using sys-patch. I have disabled it.
Same weired result

So I think there is a bug on how ATM reads ips files on booting.
The only difference when you copy the same files multiple times are the metadata on the SD cache.
Someone need to make a debug to find why ATM are not loading the files.

*******************

UPDATE:

1. I tested the latest version of the software you provided, it works as a charm! The only issue is that it takes more time to show the logo, and the boot proccess is much more slow.

2. I found that I just need 1 file, instead of 5.
So, I dont know what these files generated by the script are used for, but I think the problem are on them. After deleting them, everythng works correctly:

# AM patches
"C79F22F18169FCD3B3698A881394F6240385CDB1": 1668164,
"01890C643E9D6E17B2CDA77A9749ECB9A4F676D6": 1962240,
"C088ADC91417EBAE6ADBDF3E47946858CAFE1A82": 1962240,
"3EC573CB22744A993DFE281701E9CBFE66C03ABD": 1716480,
 
Last edited by toxic9,

Site & Scene News

Popular threads in this forum